MX Linux Forum

SwampRabbit wrote: Tue Oct 19, 2021 12:24 am

markol wrote: Sat Oct 09, 2021 5:47 am Spectacle in RC1 crashes every time I close it (verified on 2 machines)

baldyeti wrote: Wed Oct 13, 2021 5:37 am Sadly i can confirm that spectacle crashes (both under init and systemd)

On plain bullseye+KDE, it does not crash even though it seems to be using the exact same package version (20.12.3-1)

I sent up an updated kimageannotator 0.5.2-1, hopefully it fixes this segfault, if you get this update can you verify if it's fixed or not? Thanks

dolphin_oracle wrote: Tue Oct 19, 2021 9:08 am

jackdotnet wrote: Tue Oct 19, 2021 9:00 am @Adrian MX-21 KDE RC1 live usb 2.0 with persistence all runs as slow as molasses on my machine...the qsi I posted is from my machine I'm booting the live usb on which is normally running MX-19.3. I guess I could run qsi in MX-21 KDE RC1 live usb but all the hardware would be exactly the same. I bet if I put the RC on a live usb 3.0 I'd get molasses again.

probably if you are using the vesa graphics driver like your output above then yes, plasma will be dog slow.

when people talk about how light plasma has become, they don't really talk about the load placed on the graphics subsystem. they usually just think of ram. plasma has a lot of 3d acceleration going on, and vesa/llvmpipe isn't going to keep up.

Graphics:  Device-1: Advanced Micro Devices [AMD/ATI] Kaveri [Radeon R7 Graphics] vendor: Gigabyte driver: radeon v: kernel 
           bus ID: 00:01.0 chip ID: 1002:1313 
           Display: x11 server: X.Org 1.20.13 driver: ati,radeon unloaded: fbdev,modesetting,vesa compositor: kwin_x11 
           resolution: 1920x1080~60Hz 
           OpenGL: renderer: AMD KAVERI (DRM 2.50.0 5.10.0-9-amd64 LLVM 12.0.1) v: 4.5 Mesa 21.2.3 direct render: Yes 

richb wrote: Tue Oct 19, 2021 9:50 am

dolphin_oracle wrote: Tue Oct 19, 2021 9:08 am

jackdotnet wrote: Tue Oct 19, 2021 9:00 am @Adrian MX-21 KDE RC1 live usb 2.0 with persistence all runs as slow as molasses on my machine...the qsi I posted is from my machine I'm booting the live usb on which is normally running MX-19.3. I guess I could run qsi in MX-21 KDE RC1 live usb but all the hardware would be exactly the same. I bet if I put the RC on a live usb 3.0 I'd get molasses again.

probably if you are using the vesa graphics driver like your output above then yes, plasma will be dog slow.

when people talk about how light plasma has become, they don't really talk about the load placed on the graphics subsystem. they usually just think of ram. plasma has a lot of 3d acceleration going on, and vesa/llvmpipe isn't going to keep up.

@dolphin_oracle
Just curious. It appears I am using LLVM and the vesa compositor. I find MX KDE very fast with graphics. some other factors involved? I would think running from USB 2.0 would be a big factor for a slow system.

Code: Select all

Graphics:  Device-1: Advanced Micro Devices [AMD/ATI] Kaveri [Radeon R7 Graphics] vendor: Gigabyte driver: radeon v: kernel 
           bus ID: 00:01.0 chip ID: 1002:1313 
           Display: x11 server: X.Org 1.20.13 driver: ati,radeon unloaded: fbdev,modesetting,vesa compositor: kwin_x11 
           resolution: 1920x1080~60Hz 
           OpenGL: renderer: AMD KAVERI (DRM 2.50.0 5.10.0-9-amd64 LLVM 12.0.1) v: 4.5 Mesa 21.2.3 direct render: Yes 

you are not using LLVMPIPE, you are using direct rendering with the AMD Kaveri. loading off a usb2.0 device would be very slow too, you are right @richb

rainfox wrote: Tue Oct 19, 2021 5:05 pm Bluetooth is always switched on, even if switched off in last session. Shouldn't this setting be permanent?

A questions regarding the installer.
There is this page where you have to enter the Domain and the Windows Workgroup. These are mandatory fields. Why? During first install this really confused me since I did not know what to enter in the domain field and what side effects this could have. I now enter some random value there. But why can't it left blank?

SwampRabbit wrote: Tue Oct 19, 2021 5:15 pm

rainfox wrote: Tue Oct 19, 2021 5:05 pm Bluetooth is always switched on, even if switched off in last session. Shouldn't this setting be permanent?

A questions regarding the installer.
There is this page where you have to enter the Domain and the Windows Workgroup. These are mandatory fields. Why? During first install this really confused me since I did not know what to enter in the domain field and what side effects this could have. I now enter some random value there. But why can't it left blank?

You need those because Samba service needs them, which are default installed until later in the installer you have the ability to disable them. Just leave them the defaults, you don't have to enter anything.

rainfox wrote: Wed Oct 20, 2021 2:42 am What about Bluetooth, it is always on after reboot. Is there a special setting that I missed to permanently disable it or is it a bug?