[Stable Update] 2021-12-10 - Kernels, Systemd, LibreOffice, Plasma, Browser, Thunderbird

[xD0135]

Thank you everyone for the solid work making this upgrade painless. I did encounter the following issues:

Fixed:

• Login screen had reset
• The theme for konsole also reset
• The launcher icon reset to the default KDE

Need help:

• Sleep (suspend to RAM) no longer works as the computer wakes up right after it goes to sleep.

Below is the output of the sleep/wake cycle from dmesg:

[24259.934114] PM: suspend entry (deep)
[24259.941897] Filesystems sync: 0.007 seconds
[24260.050706] Freezing user space processes ... (elapsed 0.002 seconds) done.
[24260.052802] OOM killer disabled.
[24260.052802] Freezing remaining freezable tasks ... (elapsed 6.859 seconds) done.
[24266.912340] printk: Suspending console(s) (use no_console_suspend to debug)
[24266.916629] e1000e: EEE TX LPI TIMER: 00000011
[24266.943626] sd 4:0:0:0: [sdd] Synchronizing SCSI cache
[24266.950323] sd 1:0:0:0: [sda] Synchronizing SCSI cache
[24266.953743] sd 1:0:0:0: [sda] Stopping disk
[24266.957157] sd 2:0:0:0: [sdb] Synchronizing SCSI cache
[24266.959895] sd 2:0:0:0: [sdb] Stopping disk
[24266.970318] sd 3:0:0:0: [sdc] Synchronizing SCSI cache
[24266.973719] sd 3:0:0:0: [sdc] Stopping disk
[24267.418289] ACPI: PM: Preparing to enter system sleep state S3
[24268.702496] ACPI: PM: Saving platform NVS memory
[24268.702564] Disabling non-boot CPUs ...
[24268.706037] smpboot: CPU 1 is now offline
[24268.707988] smpboot: CPU 2 is now offline
[24268.709922] smpboot: CPU 3 is now offline
[24268.711804] smpboot: CPU 4 is now offline
[24268.713635] smpboot: CPU 5 is now offline
[24268.715505] smpboot: CPU 6 is now offline
[24268.717416] smpboot: CPU 7 is now offline
[24268.719572] smpboot: CPU 8 is now offline
[24268.721186] smpboot: CPU 9 is now offline
[24268.722698] smpboot: CPU 10 is now offline
[24268.724243] smpboot: CPU 11 is now offline
[24268.725775] smpboot: CPU 12 is now offline
[24268.727305] smpboot: CPU 13 is now offline
[24268.728988] smpboot: CPU 14 is now offline
[24268.730581] smpboot: CPU 15 is now offline
[24268.732955] ACPI: PM: Low-level resume complete
[24268.732998] ACPI: PM: Restoring platform NVS memory
[24268.734689] Enabling non-boot CPUs ...
[24268.734820] x86: Booting SMP configuration:
[24268.734821] smpboot: Booting Node 0 Processor 1 APIC 0x2
[24268.737023] CPU1 is up
[24268.737129] smpboot: Booting Node 0 Processor 2 APIC 0x4
[24268.738741] CPU2 is up
[24268.738845] smpboot: Booting Node 0 Processor 3 APIC 0x6
[24268.740462] CPU3 is up
[24268.740567] smpboot: Booting Node 0 Processor 4 APIC 0x8
[24268.742202] CPU4 is up
[24268.742312] smpboot: Booting Node 0 Processor 5 APIC 0xa
[24268.743960] CPU5 is up
[24268.744074] smpboot: Booting Node 0 Processor 6 APIC 0xc
[24268.745753] CPU6 is up
[24268.745867] smpboot: Booting Node 0 Processor 7 APIC 0xe
[24268.747582] CPU7 is up
[24268.747697] smpboot: Booting Node 0 Processor 8 APIC 0x1
[24268.748558] CPU8 is up
[24268.748674] smpboot: Booting Node 0 Processor 9 APIC 0x3
[24268.749467] CPU9 is up
[24268.749586] smpboot: Booting Node 0 Processor 10 APIC 0x5
[24268.750376] CPU10 is up
[24268.750491] smpboot: Booting Node 0 Processor 11 APIC 0x7
[24268.751323] CPU11 is up
[24268.751439] smpboot: Booting Node 0 Processor 12 APIC 0x9
[24268.752307] CPU12 is up
[24268.752423] smpboot: Booting Node 0 Processor 13 APIC 0xb
[24268.753325] CPU13 is up
[24268.753440] smpboot: Booting Node 0 Processor 14 APIC 0xd
[24268.754396] CPU14 is up
[24268.754526] smpboot: Booting Node 0 Processor 15 APIC 0xf
[24268.755510] CPU15 is up
[24268.759822] ACPI: PM: Waking up from system sleep state S3
[24268.875401] sd 1:0:0:0: [sda] Starting disk
[24268.875404] sd 2:0:0:0: [sdb] Starting disk
[24268.875439] sd 3:0:0:0: [sdc] Starting disk
[24268.878360] nvme nvme0: Shutdown timeout set to 8 seconds
[24268.879615] nvme nvme1: Shutdown timeout set to 8 seconds
[24268.900693] nvme nvme0: 16/0/0 default/read/poll queues
[24268.903418] nvme nvme1: 16/0/0 default/read/poll queues
[24269.004474] [drm] PCIE GART of 256M enabled (table at 0x000000F400000000).
[24269.203060] ata3: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[24269.203077] ata4: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[24269.203116] ata2: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[24269.203332] ata3.00: supports DRM functions and may not be fully accessible
[24269.203441] ata4.00: supports DRM functions and may not be fully accessible
[24269.203530] ata2.00: supports DRM functions and may not be fully accessible
[24269.204300] ata4.00: disabling queued TRIM support
[24269.205783] ata3.00: disabling queued TRIM support
[24269.206883] ata2.00: disabling queued TRIM support
[24269.207565] ata4.00: supports DRM functions and may not be fully accessible
[24269.207906] ata3.00: supports DRM functions and may not be fully accessible
[24269.208418] ata4.00: disabling queued TRIM support
[24269.208568] ata3.00: disabling queued TRIM support
[24269.210730] ata3.00: configured for UDMA/133
[24269.210737] ahci 0000:00:17.0: port does not support device sleep
[24269.210819] ata2.00: supports DRM functions and may not be fully accessible
[24269.211578] ata4.00: configured for UDMA/133
[24269.211605] ahci 0000:00:17.0: port does not support device sleep
[24269.211804] ata2.00: disabling queued TRIM support
[24269.211877] ata4.00: Enabling discard_zeroes_data
[24269.215559] ata2.00: configured for UDMA/133
[24269.215565] ahci 0000:00:17.0: port does not support device sleep
[24269.216067] ata2.00: Enabling discard_zeroes_data
[24269.351442] [drm] UVD and UVD ENC initialized successfully.
[24269.452434] [drm] VCE initialized successfully.
[24269.461506] OOM killer enabled.
[24269.461506] Restarting tasks ... done.
[24269.464413] PM: suspend exit

Edit: ahci 00:17:0 is the following:

00:17.0 SATA controller: Intel Corporation Cannon Lake PCH SATA AHCI Controller (rev 10) (prog-if 01 [AHCI 1.0])
        DeviceName: Onboard - SATA
        Subsystem: Gigabyte Technology Co., Ltd Device b005
        Flags: bus master, 66MHz, medium devsel, latency 0, IRQ 130
        Memory at 96234000 (32-bit, non-prefetchable) [size=8K]
        Memory at 9623a000 (32-bit, non-prefetchable) [size=256]
        I/O ports at 5050 [size=8]
        I/O ports at 5040 [size=4]
        I/O ports at 5020 [size=32]
        Memory at 96239000 (32-bit, non-prefetchable) [size=2K]
        Capabilities: [80] MSI: Enable+ Count=1/1 Maskable- 64bit-
        Capabilities: [70] Power Management version 3
        Capabilities: [a8] SATA HBA v1.0
        Kernel driver in use: ahci

[rykemasters]

I think I may have found something related to the bluetooth problems that started with this update, looking into fixing it:

#sudo dmesg | grep Blue                                                                                                                                                                                                    
[    4.528803] Bluetooth: Core ver 2.22
[    4.528827] Bluetooth: HCI device and connection manager initialized
[    4.528831] Bluetooth: HCI socket layer initialized
[    4.528832] Bluetooth: L2CAP socket layer initialized
[    4.528834] Bluetooth: SCO socket layer initialized
[    4.742575] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[    4.742581] Bluetooth: BNEP filters: protocol multicast
[    4.742586] Bluetooth: BNEP socket layer initialized
[    6.767895] Bluetooth: hci0: command 0xfc05 tx timeout
[    6.767897] Bluetooth: hci0: Reading Intel version command failed (-110)

[papajoke]

For me, with new theme Breath not possible to update …
Remove before manjaro-kde-settings-19.0 and after update, install manjaro-kde-settings

[ghostwind]

were you able to get bash running again? I’ve tried switching default shells from zsh and back to bash, and it didn’t affect anything.

Update: manually changing /usr/share/konsole/Breath.profile with root permissions fixes the issue

[LordTermor]

Better make your own profile with bash, system one could be overwritten with the next update

[philm]

There was an issue with Dash-to-Dock extension which will be also fixed in an ISO rebuild. Dash to Dock not working after update

[mamantoja]

After this update, any chromium-based browser doesn’t show on Wayland.

chromium --enable-features=UseOzonePlatform --ozone-platform=wayland

It’s started but I can’t open it from the taskbar.

---

Update

This is wayland issue in kwin 445259 – Several Chromium-based browsers suddenly fail to bring up their browser windows on Wayland

---

DE: Plasma 5.23.4
WM: kwin

[ruziel]

@joemaro - That makes sense - run stable until you are past your busy period @ Uni & can deal with any issues that come up with testing. More power to you.

[Algo]

@LordTermor

It’s deprecated.

Well ok then i will use Breeze(-Dark) instead? Well a pity but the blue Dolphin icon is OK i guess.

Another change i made is changing Konsole back to use bash (using my own profile) because i had a special script in .bashrc to make it more pleasing ;). Any reservations against that? Or can i do a similar styling with zsh?

[dobedobedo]

The update changes the login splash, and need to apply this measure to solve the issue.
rm ~/.config/ksplashrc
PS: Is Breath-icon removed? Is it okay to install it back?

[LordTermor]

@Algo

Well a pity but the blue Dolphin icon is OK i guess.

We’ve worked with KDE on that and now Breeze system settings and file manager icons will be colored to your accent theme. Will be available in KDE Frameworks 5.90.

@dobedobedo

Is Breath-icon removed? Is it okay to install it back?

I will release Breath Classic eventually with those icons and old theme; for now you need install it manually. What’s wrong with Breeze?

@Algo

Another change i made is changing Konsole back to use bash (using my own profile) because i had a special script in .bashrc to make it more pleasing ;). Any reservations against that? Or can i do a similar styling with zsh?

No, no problem. It’s just about defaults change. You can use whatever you want, we don’t force you to use zsh . But I’m more than sure that you can do the same styling for it.

[philm]

We just pushed some more package updates for Breath theme to our repos. Those should also fix issues with SDDM.

[Kenny.ch]

Okay, but if kconf_update should fix the issues from Breath2 to Breath, then I can say its broken.
Because I did just Upgrade and let pacman/Pamac do everything (did not change anything from on the themes before upgrading) → everything was “soft broken” on my system and had reset SDDM Lockscreen, Theme/Console Profiles etc pp to have a “usable” system as before (with Breath Dark)

also after first boot the Lockscreen was so bright - like a Light theme active, was a pain to get it back to the default one (Lockscreen was a easy fix but not startup loging screen)

[LordTermor]

@Kenny.ch

then I can say its broken

But it worked for most of people. I can’t assume all configurations…

@Kenny.ch

SDDM

SDDM wasn’t updated as it’s a part of system config.

@Kenny.ch

Console Profiles

Also cannot be changed via kconf_update in a reasonable way.

@Kenny.ch

also after first boot the Lockscreen was so bright

It was an oversight and the latest update mentioned by @philm should fix it.

[Kenny.ch]

Mostly “your config” just had breath2-dark active (just switched it in the quick settings so no custom) and jep it did not “upgraded” it correctly but now (as I fixed everything) I cant retest it so - It maybe fixed now.
My bad to say just SDDM → meant Loging Screen (SDDM) Theme → had to Apply Plasma Settings + Apply Breath Theme (after enabling Breeze) to “reset” my lock screen to the correct one

[LordTermor]

Yes, there were some reports that it’s not changed, don’t really know what’s wrong here, maybe some configuration glitches? If it’s not done automatically you can always do it by hand. It all was needed to ease future updates so hopefully we won’t have such big changes any time soon.

[fhonb]

So, the system itself seems to be working after the update, but for some reason, since the update CS:GO is broken. Character and weapon models are horribly warped (see image below) and certain things that should be red are now blue, i.e. blood is blue and red text outputs, for, say, packet loss, etc. are blue instead of red as well.

I don’t know how the update is responsible for this, but it was not the case beforehand.

Edit: Some more “testing”: Other games I own are working fine it seems. Linux-native titles like Valheim and Dota 2 are still working flawlessly, and even Proton games like Dead Space are unaffected by whatever is happening to CS:GO. Even a non-Steam title running through WINE is still fine. It seems like it’s only CS:GO that doesn’t like something that was included in this update.

[ceres]

Instead of my username I have funny characters in konsole. Cannot find a way to fix it.

[LordTermor]

Can you provide a screenshot?

[Zesko]

@fhonb

since the update CS:GO is broken. Character and weapon models are horribly warped

This is the duplicate:

CSGO has weird artifiacting since the update

I’m using stable branch. Game was running fine on 470 driver before the large patch. Now I get graphical artifacts in game and the colors aren’t right either. For example the molotov has an odd green tinge to it’s flames. My crosshair which was pale light blue is now yellow. The NetGraph output is an odd blue color when it used to be somewhere between pale orange or pale yellow. I uploaded a couple of Images here: h**ps://imgur.com/a/QlWfrl5