MX-21 beta 1 feedback thread

Message
Author
User avatar
asqwerth
Developer
Posts: 7804
Joined: Sun May 27, 2007 5:37 am

Re: MX-21 beta 1 feedback thread

#171 Post by asqwerth »

pianokeyjoe wrote: Sun Aug 01, 2021 12:07 am I have just had some fun with MX21 beta 1 64bit. So far everything looks to be like MX19.4 with a few differences which have already been discussed here. Now the thing that struck me almost instantly was the "window manager" themes setting in the XFCE settings panel. While you can see the selection of themes, when you click on one them or another you do not get a visual confirmation the theme is applied as any open windows do not get affected. Also, Thunar and Firefox so far as I know and noticed, stay with a thick tall GNOME like Window title bar style instead of the selected Window manager theme. So for instance, I select DEFAULT as my window manager theme, all newly opened apps like clementine and VLC player will have the new look but Firefox and Thunar are stuck with this thick tall top title bar, no change! That is not an MX issue but a XFCE 4.16 issue I am thinking..
...
From what I can see, this seems to be caused by the gtk-nocsd package, which gives users (under the MX tweak >> Others tab) the choice to add a xfwm theme window border around those unabashedly CSD gtk apps like Archive Manager, gthumb or Simple Scan.

I discovered this because I've been trying different themes in an alpha1 iso VM all this while (my PC is old school MBR legacy BIOS and installer testing for UEFI at this stage is not my focus) , which does not come with the gtk-nocsd package. Without it:

1. Thunar file manager main window will follow whatever xfwm theme you choose [the thunar preferences/settings windows though will not)
2. any other gtk3 app that still chooses to have a traditiional look (eg geany) and doesn't come with the hardcore CSD look (see the 3 programs I listed above) will follow xfwm theme.

Then I realised from this feedback thread that @dolphin_oracle had added the noCSD option to MX Tweak. So I installed the gtk-nocsd package to continue my trialing of themes so that my VM is more faithful to current beta.

That made a HUGE difference.

Say you stick to the default setting with gtk-nocsd package installed, ie for CSD apps to use their own CSD theming:

If a gtk theme - and most modern gtk themes do - includes a built-in "fake" version of the included xfwm theme (since their themes are used in other DEs besides XFCE), then switching the xfwm theme won't change the look of the gtk3 app. It'll still use the baked in gtk3 theme's window decorations. That's what happened to Thunar. The main window of Thunar is still using your current gtk theme's window borders that were made to appear to have a xfwm look. It's no longer using the xfwm theme you set. So it will get its window border look from the gtk3 theme and not the xfwm theme. This seems to be caused by the gtk-nocsd package being installed.

However, all your Qt apps (eg all the MX apps, clementine, etc) will change to the xfwm theme you choose, leaving to non-matching window decorations between gtk3 and Qt applications.

RAM usage of these themes also appeared to increase once I installed the no-csd package.


If you then choose to disable CSD themeing from MX-Tweak, so that noCSD is in use, yes, you get your xfwm borders back on Thunar main window and other gtk3 apps that allow you to do that, and for hardcore CSD apps you get the xfwm theme surrounding the existing CSD thick style window bar.

However from what I see, RAM consumption increases even more.

My view is that the gtk-nocsd package causes more problems than it solves.

Just having it on the system messes with xfwm choices for gtk3 apps that actually were allowing xfwm themes to be used. I think we should not have it preinstalled in MX21. That way, only hardcore CSD apps will have the thick window bar, and other gtk3 apps can still use xfwm themes of your choice, including Thunar main window and geany. Then there will be less change from MX19.

Things like Archive Manager and Simple scan have been default on MX since MX 16, I think, and have been hardcore CSD apps all this time. I don't see why users should suddenly be upset if they remain as that in MX21.
Desktop: Intel i5-4460, 16GB RAM, Intel integrated graphics
Clevo N130WU-based Ultrabook: Intel i7-8550U (Kaby Lake R), 16GB RAM, Intel integrated graphics (UEFI)
ASUS X42D laptop: AMD Phenom II, 6GB RAM, Mobility Radeon HD 5400

User avatar
JayM
Posts: 6796
Joined: Tue Jan 08, 2019 3:47 am

Re: MX-21 beta 1 feedback thread

#172 Post by JayM »

I finally got around to testing MX-21b1 on a live USB with persist_all. It's pretty snappy except for Firefox which is rather slow. A remaster and the subsequent rsync upon rebooting were also very slow, but then I am using one of my old 16GB USB2 sticks.

The default conky's hard to see against the default wallpaper (which I love BTW.) I suggest using MX Cowan more sys small instead as the colors are darker, even if they don't match the wallpaper.

It works OOTB on my Ryzen 7 system. PulseAudio even defaulted to my correct sound card, the one built in to the motherboard, rather than HDMI audio. Sound works, video's at the correct 1920x1080 resolution, Ethernet works. My RTL8821CU USB wifi dongle doesn't work though: lsusb shows it but Network Manager doesn't have wifi available. It still needs a driver installed.

At this point I wonder is a beta 2 will even be necessary. Good job, everyone!

Code: Select all

System:    Host: <filter> Kernel: 5.10.0-8-amd64 x86_64 bits: 64 compiler: N/A 
           parameters: BOOT_IMAGE=/antiX/vmlinuz quiet splasht nosplash lang=en_US kbd=us 
           tz=Asia/Manila persist_all 
           Desktop: Xfce 4.16.0 tk: Gtk 3.24.24 info: xfce4-panel wm: xfwm4 dm: LightDM 1.26.0 
           Distro: MX-21_beta1_x64 Wildflower July 27  2021 base: Debian GNU/Linux 11 (bullseye) 
Machine:   Type: Desktop Mobo: ASUSTeK model: TUF B450M-PRO GAMING v: Rev X.0x serial: <filter> 
           UEFI: American Megatrends v: 3002 date: 03/11/2021 
CPU:       Topology: 8-Core model: AMD Ryzen 7 3700X bits: 64 type: MT MCP arch: Zen 
           family: 17 (23) model-id: 71 (113) stepping: N/A microcode: 8701021 
           L2 cache: 4096 KiB 
           flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm 
           bogomips: 114982 
           Speed: 2196 MHz min/max: 2200/3600 MHz boost: enabled Core speeds (MHz): 1: 2195 
           2: 2195 3: 2195 4: 2195 5: 2195 6: 2195 7: 2195 8: 2196 9: 2194 10: 2196 11: 2195 
           12: 2196 13: 2196 14: 2196 15: 2191 16: 2197 
           Vulnerabilities: Type: itlb_multihit status: Not affected 
           Type: l1tf status: Not affected 
           Type: mds status: Not affected 
           Type: meltdown status: Not affected 
           Type: spec_store_bypass 
           mitigation: Speculative Store Bypass disabled via prctl and seccomp 
           Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization 
           Type: spectre_v2 
           mitigation: Full AMD retpoline, IBPB: conditional, STIBP: conditional, RSB filling 
           Type: srbds status: Not affected 
           Type: tsx_async_abort status: Not affected 
Graphics:  Device-1: AMD Baffin [Radeon RX 460/560D / Pro 450/455/460/555/555X/560/560X] 
           driver: amdgpu v: kernel bus ID: 07:00.0 chip ID: 1002:67ef 
           Display: x11 server: X.Org 1.20.11 driver: amdgpu,ati 
           unloaded: fbdev,modesetting,vesa tty: N/A 
           OpenGL: 
           renderer: Radeon RX 560 Series (POLARIS11 DRM 3.40.0 5.10.0-8-amd64 LLVM 11.0.1) 
           v: 4.6 Mesa 20.3.5 direct render: Yes 
Audio:     Device-1: AMD Baffin HDMI/DP Audio [Radeon RX 550 640SP / RX 560/560X] 
           driver: snd_hda_intel v: kernel bus ID: 07:00.1 chip ID: 1002:aae0 
           Device-2: AMD Starship/Matisse HD Audio vendor: ASUSTeK driver: snd_hda_intel 
           v: kernel bus ID: 09:00.4 chip ID: 1022:1487 
           Sound Server: ALSA v: k5.10.0-8-amd64 
Network:   Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet 
           vendor: ASUSTeK PRIME B450M-A driver: r8169 v: kernel port: f000 bus ID: 04:00.0 
           chip ID: 10ec:8168 
           IF: eth0 state: up speed: 1000 Mbps duplex: full mac: <filter> 
           Device-2: Realtek 802.11ac NIC type: USB driver: usb-network bus ID: 1-6:2 
           chip ID: 0bda:c811 serial: <filter> 
Drives:    Local Storage: total: 4.22 TiB used: 236.16 GiB (5.5%) 
           ID-1: /dev/nvme0n1 vendor: PNY model: CS3030 500GB SSD size: 465.76 GiB block size: 
           physical: 512 B logical: 512 B speed: 31.6 Gb/s lanes: 4 serial: <filter> 
           rev: CS303321 scheme: GPT 
           ID-2: /dev/sda vendor: Gigabyte model: GP-GSTFS31120GNTD size: 111.79 GiB block size: 
           physical: 512 B logical: 512 B speed: 6.0 Gb/s serial: <filter> rev: 61.3 scheme: GPT 
           ID-3: /dev/sdb vendor: Seagate model: ST4000DM004-2CV104 size: 3.64 TiB block size: 
           physical: 4096 B logical: 512 B speed: 6.0 Gb/s rotation: 5425 rpm serial: <filter> 
           rev: 0001 
           ID-4: /dev/sdc type: USB vendor: Toshiba model: TransMemory size: 14.45 GiB 
           block size: physical: 512 B logical: 512 B serial: <filter> rev: 1.00 scheme: GPT 
Partition: ID-1: / raw size: N/A size: 24.99 GiB used: 6.2 MiB (0.0%) fs: overlay 
           source: ERR-102 
Sensors:   System Temperatures: cpu: 45.4 C mobo: N/A gpu: amdgpu temp: 46 C 
           Fan Speeds (RPM): N/A 
Repos:     No active apt repos in: /etc/apt/sources.list 
           Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list 
           1: deb http://deb.debian.org/debian bullseye-updates main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/debian.list 
           1: deb http://deb.debian.org/debian bullseye main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/mx.list 
           1: deb https://mirror.pregi.net/mx-linux-packages/mx/repo/ bullseye main non-free
           No active apt repos in: /etc/apt/sources.list.d/various.list 
Info:      Processes: 338 Uptime: 17m Memory: 31.33 GiB used: 1.46 GiB (4.7%) Init: SysVinit 
           v: 2.96 runlevel: 5 default: 5 Compilers: gcc: 10.2.1 alt: 10 Shell: quick-system-in 
           running in: quick-system-in inxi: 3.0.36 
Next test: a frugal install.
Please read the Forum Rules, How To Ask For Help, How to Break Your System and Don't Break Debian. Always include your full Quick System Info (QSI) with each and every new help request.

SwampRabbit
Posts: 3602
Joined: Tue Jun 14, 2016 2:02 pm

Re: MX-21 beta 1 feedback thread

#173 Post by SwampRabbit »

agnivo007 wrote: Sun Aug 01, 2021 12:48 am Bug report 2: Weird vanishing panel:
Choose a menu item say brave browser from menu>rt click>add to panel. Then hover over added item in panel>rt click>remove (yes)>full panel vanishes. Relogin needed to get back panel.

Bug report 5: Whisker menu unusual backtracking movement:
When menu button clicked or activated by key, whisker menu appears, then shifts leftward a few pixels to "snap-on" to panel creating a backtracking movement that's weird to the eye.
Something with shadows/compositor setting? Visible delay on old systems in painting the menu, is this latency adjustable? Maybe saw this in MX19 too.

Bug? report 6: Hddtemp notice for sensors plugin:
Thought this was to be resolved on a default install as per earlier forum conversations, by changing hddtemp permissions. Adding sensors plugin to panel still throws up that old notice and suggests the dirty hack.
2) I can confirm something odd is happening when doing this, but for me it worked once, then the second time the panel froze. Already looking at updating Xfce components to hopefully fix some issues with the panel.

5) can't confirm this, no such issues using a mouse or via keyboard on my end, would like someone else to confirm

6) make sure you're updated, a update was pushed for the sensors plugin recently. I tested the sensors plugin on two systems without issue prior to sending the new version up
I can check again, but someone else will probably have the opportunity before I do

Also, please don't post just to link a updated post that's two posts up.... its just silly, it creates unneeded posts, and it makes the horrible process of tracking issues in a forum thread harder.


A side note for anyone testing.... please:
- keep your Beta install updated, not only are MX fixes coming down but Debian Bullseye fixes are coming down (there's technically 2 Betas being worked here)
- READ the whole thread, try not to post about issues already reported if you can
- if you're testing on hardware and have a hardware item to report, post your QSI and post anything relevant to it
- if you're testing in a VM, verify on hardware before you report
- you can also report bugs/issues here https://bugs.mxlinux.org/buglist.cgi?ch ... eldfrom=7d (noticed how many have NOT been reported in the last week?)
- feel free to also identify or find the solution/options for the item/issue you report (it isn't like dolphin_oracle fixes all this stuff as his full time job, doesn't have a family, and gets paid for it all ;) )
NEW USERS START HERE FAQS, MX Manual, and How to Break Your System - Don't use Ubuntu PPAs! Always post your Quick System Info (QSI) when asking for help.

User avatar
JayM
Posts: 6796
Joined: Tue Jan 08, 2019 3:47 am

Re: MX-21 beta 1 feedback thread

#174 Post by JayM »

Firefox is fast and fine on a frugal_static installation on my spare 120GB SATA SSD so the prior slowness was apparently due to the USB2.0 stick.

Code: Select all

System:    Host: <filter> Kernel: 5.10.0-8-amd64 x86_64 bits: 64 compiler: N/A 
           parameters: BOOT_IMAGE=/antiX/vmlinuz quiet splasht nosplash lang=en_US kbd=us 
           tz=Asia/Manila frugal_static gfxsave 
           Desktop: Xfce 4.16.0 tk: Gtk 3.24.24 info: xfce4-panel wm: xfwm4 dm: LightDM 1.26.0 
           Distro: MX-21_beta1_x64 Wildflower July 27  2021 base: Debian GNU/Linux 11 (bullseye) 
Machine:   Type: Desktop Mobo: ASUSTeK model: TUF B450M-PRO GAMING v: Rev X.0x serial: <filter> 
           UEFI: American Megatrends v: 3002 date: 03/11/2021 
CPU:       Topology: 8-Core model: AMD Ryzen 7 3700X bits: 64 type: MT MCP arch: Zen 
           family: 17 (23) model-id: 71 (113) stepping: N/A microcode: 8701021 
           L2 cache: 4096 KiB 
           flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm 
           bogomips: 114984 
           Speed: 2187 MHz min/max: 2200/3600 MHz boost: enabled Core speeds (MHz): 1: 2201 
           2: 2192 3: 2189 4: 2195 5: 2195 6: 2194 7: 2196 8: 2195 9: 2194 10: 2192 11: 2195 
           12: 2195 13: 2196 14: 2194 15: 2196 16: 2196 
           Vulnerabilities: Type: itlb_multihit status: Not affected 
           Type: l1tf status: Not affected 
           Type: mds status: Not affected 
           Type: meltdown status: Not affected 
           Type: spec_store_bypass 
           mitigation: Speculative Store Bypass disabled via prctl and seccomp 
           Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization 
           Type: spectre_v2 
           mitigation: Full AMD retpoline, IBPB: conditional, STIBP: conditional, RSB filling 
           Type: srbds status: Not affected 
           Type: tsx_async_abort status: Not affected 
Graphics:  Device-1: AMD Baffin [Radeon RX 460/560D / Pro 450/455/460/555/555X/560/560X] 
           driver: amdgpu v: kernel bus ID: 07:00.0 chip ID: 1002:67ef 
           Display: x11 server: X.Org 1.20.11 driver: amdgpu,ati 
           unloaded: fbdev,modesetting,vesa resolution: 1920x1080~60Hz 
           OpenGL: 
           renderer: Radeon RX 560 Series (POLARIS11 DRM 3.40.0 5.10.0-8-amd64 LLVM 11.0.1) 
           v: 4.6 Mesa 20.3.5 direct render: Yes 
Audio:     Device-1: AMD Baffin HDMI/DP Audio [Radeon RX 550 640SP / RX 560/560X] 
           driver: snd_hda_intel v: kernel bus ID: 07:00.1 chip ID: 1002:aae0 
           Device-2: AMD Starship/Matisse HD Audio vendor: ASUSTeK driver: snd_hda_intel 
           v: kernel bus ID: 09:00.4 chip ID: 1022:1487 
           Sound Server: ALSA v: k5.10.0-8-amd64 
Network:   Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet 
           vendor: ASUSTeK PRIME B450M-A driver: r8169 v: kernel port: f000 bus ID: 04:00.0 
           chip ID: 10ec:8168 
           IF: eth0 state: up speed: 1000 Mbps duplex: full mac: <filter> 
           Device-2: Realtek 802.11ac NIC type: USB driver: usb-network bus ID: 1-6:2 
           chip ID: 0bda:c811 serial: <filter> 
Drives:    Local Storage: total: 4.22 TiB used: 234.52 GiB (5.4%) 
           ID-1: /dev/nvme0n1 vendor: PNY model: CS3030 500GB SSD size: 465.76 GiB block size: 
           physical: 512 B logical: 512 B speed: 31.6 Gb/s lanes: 4 serial: <filter> 
           rev: CS303321 scheme: GPT 
           ID-2: /dev/sda vendor: Gigabyte model: GP-GSTFS31120GNTD size: 111.79 GiB block size: 
           physical: 512 B logical: 512 B speed: 6.0 Gb/s serial: <filter> rev: 61.3 scheme: GPT 
           ID-3: /dev/sdb vendor: Seagate model: ST4000DM004-2CV104 size: 3.64 TiB block size: 
           physical: 4096 B logical: 512 B speed: 6.0 Gb/s rotation: 5425 rpm serial: <filter> 
           rev: 0001 
           ID-4: /dev/sdc type: USB vendor: Toshiba model: TransMemory size: 14.45 GiB 
           block size: physical: 512 B logical: 512 B serial: <filter> rev: 1.00 scheme: GPT 
Partition: ID-1: / raw size: N/A size: 7.78 GiB used: 4.9 MiB (0.1%) fs: overlay source: ERR-102 
Sensors:   System Temperatures: cpu: 44.2 C mobo: N/A gpu: amdgpu temp: 45 C 
           Fan Speeds (RPM): N/A 
Repos:     No active apt repos in: /etc/apt/sources.list 
           Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list 
           1: deb http://deb.debian.org/debian bullseye-updates main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/debian.list 
           1: deb http://deb.debian.org/debian bullseye main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/mx.list 
           1: deb https://mirror.pregi.net/mx-linux-packages/mx/repo/ bullseye main non-free
           No active apt repos in: /etc/apt/sources.list.d/various.list 
Info:      Processes: 358 Uptime: 10m Memory: 31.33 GiB used: 1.29 GiB (4.1%) Init: SysVinit 
           v: 2.96 runlevel: 5 default: 5 Compilers: gcc: 10.2.1 alt: 10 Shell: quick-system-in 
           running in: quick-system-in inxi: 3.0.36 
EDIT: I just noticed that Window Buttons was missing from the panel, which I had moved to the bottom using MX Tweak. I could have sworn there were Window Buttons when I first booted and when the panel was on the left. I wonder what happened? What I've done so far: booted live with persist_all, changed my MX mirror to the LA MX one, checked for and installed updates, changed my conky, did a personal remaster, rebooted, posted my QSI from the persistent live USB, rebooted, did a frugal_static install. (Also my mirror change didn't survive and was set back to pregi.net in the Philippines, probably because a frugal install is, well, an install of sorts.)

EDIT 2: Another thing I noticed is that LUM wants to burn the MX-21 beta1 ISO in dd mode by default rather than in full-featured mode. I have to manually change it.
Last edited by JayM on Sun Aug 01, 2021 3:05 am, edited 3 times in total.
Please read the Forum Rules, How To Ask For Help, How to Break Your System and Don't Break Debian. Always include your full Quick System Info (QSI) with each and every new help request.

User avatar
agnivo007
Posts: 720
Joined: Mon May 04, 2020 11:39 pm

Re: MX-21 beta 1 feedback thread

#175 Post by agnivo007 »

Should I resubmit reports to the tracker? I aggregated and updated the issues to a single post as this thread will get long and will surely lose track. That's not good for you guys as it seems.

Yes, I keep things updated; thanks for mentioning. Yet, currently sensors plugin behave as I have reported.

Is it OK to report about missing wifi dongle support (RTL8811) that's very popular and sold in millions worldwide over last 7 years? Need to compile driver manually from git and install on MX19 too.
Ref: viewtopic.php?t=64013
- Roy, Kolkata, IN. "REDUCE-REUSE-RECYCLE-REPURPOSE"
MX-21-AHS-KDE on [ H110M-H : Modded BIOS | Core i3-9350K | 8GB DDR4 | SP A60 NVMe PCIe3x4 | Samsung Evo 870 SSD | WD Black Mobile HDD ]

SwampRabbit
Posts: 3602
Joined: Tue Jun 14, 2016 2:02 pm

Re: MX-21 beta 1 feedback thread

#176 Post by SwampRabbit »

@agnivo007 well what you got going on with that one post should be ok, it’s good the centralize it, but if it gets to huge maybe not… I guess just use your best judgement.

I don’t think you have to open bug reports now, honestly I should let d.o. or Adrian make that call.

I thought we took care of the RTL8811, obviously not though. Maybe that was for AHS… will follow up.

I just posted that list of stuff to try to remember when testing the Beta because we’re already 18 pages into it and some stuff people brought up aren’t bugs, can’t be confirmed, or are kinda vague. That’s all. :happy:
NEW USERS START HERE FAQS, MX Manual, and How to Break Your System - Don't use Ubuntu PPAs! Always post your Quick System Info (QSI) when asking for help.

User avatar
agnivo007
Posts: 720
Joined: Mon May 04, 2020 11:39 pm

Re: MX-21 beta 1 feedback thread

#177 Post by agnivo007 »

Praise the good time and effort of the team... I'm trying in my own way. Thanks for everything so far (and future too).
Yes, much of half baking will be done fully at the end I hope.
- Roy, Kolkata, IN. "REDUCE-REUSE-RECYCLE-REPURPOSE"
MX-21-AHS-KDE on [ H110M-H : Modded BIOS | Core i3-9350K | 8GB DDR4 | SP A60 NVMe PCIe3x4 | Samsung Evo 870 SSD | WD Black Mobile HDD ]

User avatar
chrispop99
Global Moderator
Posts: 3334
Joined: Tue Jan 27, 2009 2:07 pm

Re: MX-21 beta 1 feedback thread

#178 Post by chrispop99 »

JayM wrote: Sun Aug 01, 2021 2:39 am EDIT: I just noticed that Window Buttons was missing from the panel, which I had moved to the bottom using MX Tweak. I could have sworn there were Window Buttons when I first booted and when the panel was on the left. I wonder what happened?
Window Buttons have been replace by Doclike.

https://mxlinux.org/wiki/docklike-taskbar/

Chris
MX Facebook Group Administrator.
Home-built desktop - Core i5 9400, 970 EVO Plus, 8GB
DELL XPS 15
Lots of test machines

User avatar
JayM
Posts: 6796
Joined: Tue Jan 08, 2019 3:47 am

Re: MX-21 beta 1 feedback thread

#179 Post by JayM »

chrispop99 wrote: Sun Aug 01, 2021 3:21 am
JayM wrote: Sun Aug 01, 2021 2:39 am EDIT: I just noticed that Window Buttons was missing from the panel, which I had moved to the bottom using MX Tweak. I could have sworn there were Window Buttons when I first booted and when the panel was on the left. I wonder what happened?
Window Buttons have been replace by Doclike.

https://mxlinux.org/wiki/docklike-taskbar/

Chris
Oh, neat! From a quick glance I think I see how it works, kind of a combination of panel launchers and Window buttons? If one of the apps in Doclike is opened it adds a little blue doomaflotchy at the right of the icon. I'll have to play with it some more tomorrow and figure out how to add apps to it. :smile:
Please read the Forum Rules, How To Ask For Help, How to Break Your System and Don't Break Debian. Always include your full Quick System Info (QSI) with each and every new help request.

User avatar
asqwerth
Developer
Posts: 7804
Joined: Sun May 27, 2007 5:37 am

Re: MX-21 beta 1 feedback thread

#180 Post by asqwerth »

as usual, right click is your friend. :)
Desktop: Intel i5-4460, 16GB RAM, Intel integrated graphics
Clevo N130WU-based Ultrabook: Intel i7-8550U (Kaby Lake R), 16GB RAM, Intel integrated graphics (UEFI)
ASUS X42D laptop: AMD Phenom II, 6GB RAM, Mobility Radeon HD 5400

Locked

Return to “General”