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

Is the s2idle sleep fix implimented in 5.15.6? (Issue discussion)

Sorry I should be more specific. You can add a BTRFS partition but you have to go into manual partitioning to do it. I’ve done it before but the process (for me at least) has always been hit or miss. Where I will partition it with BTRFS and then black screen on boot. What I was asking is if there will be something like a drop down menu that will then auto do the partitioning for you.

At end of update I got following Warnings and Error:

(26/31) Configuring pacman-mirrors ...
::WARNING https://repo.manjaro.org 'Connection: HTTPSConnectionPool(host='repo.manjaro.org', port=443): Max retries exceeded with url: / (Caused by NewConnectionError('<urllib3.connection.HTTPSConnection object at 0x7f5383e7a2b0>: Failed to establish a new connection: [Errno -2] Name or service not known'))'
::WARNING https://repo.manjaro.org 'Connection: HTTPSConnectionPool(host='repo.manjaro.org', port=443): Max retries exceeded with url: / (Caused by NewConnectionError('<urllib3.connection.HTTPSConnection object at 0x7f5383e6cb50>: Failed to establish a new connection: [Errno -2] Name or service not known'))'
::WARNING https://wikipedia.org 'Connection: HTTPSConnectionPool(host='www.wikipedia.org', port=443): Max retries exceeded with url: / (Caused by NewConnectionError('<urllib3.connection.HTTPSConnection object at 0x7f5383e7a8e0>: Failed to establish a new connection: [Errno 101] Network is unreachable'))'
::INFO Downloading mirrors from Manjaro
::INFO => Mirror pool: https://repo.manjaro.org/mirrors.json


::ERROR Connection: HTTPSConnectionPool(host='repo.manjaro.org', port=443): Max retries exceeded with url: /mirrors.json (Caused by NewConnectionError('<urllib3.connection.HTTPSConnection object at 0x7f5383e7aaf0>: Failed to establish a new connection: [Errno -2] Name or service not known'))
::INFO => Mirror status: https://repo.manjaro.org/status.json


::ERROR Connection: HTTPSConnectionPool(host='repo.manjaro.org', port=443): Max retries exceeded with url: /status.json (Caused by NewConnectionError('<urllib3.connection.HTTPSConnection object at 0x7f5383e7a9d0>: Failed to establish a new connection: [Errno -2] Name or service not known'))
hint: use `pacman-mirrors` to generate and update your pacman mirrorlist.

Is executing $ pacman-mirrors enough to fix it?

We implemented fs selection support for autopartition in Calamares back in June and it’s already available since August in our ISOs.

1 Like

Now, I have removed the dustbin from the taskbar: the icon was grey on black background.

Is it possible to “refresh” or “set to defaults” the icons ?

Actually it should’ve been migrated from Breath2(+2021) to Breath automatically using kconf_update KDE utility. Only thing that cannot be changed this way is SDDM theme as it’s a system file and Konsole as we changed placement of profile files a bit.

It’s deprecated.

It leads to more eye stress and after some time with gray color I personally can’t stand white anymore.

It’s there from our latest July update so no it’s not a regression. You can switch to Breeze if you prefer that more.

For Manjaro the default is Breath.

1 Like

Hello,
after upgrade dolphin icon on task bar is blue, how can restore the original Manjaro Breath icons
thanks

You can’t. Breath icons got deprecated and we talked to KDE Developers to do this for Breeze icons.

Will be available soon …

2 Likes

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

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)

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

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

1 Like

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

1 Like

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

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

@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.

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?

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?

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.

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

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

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

2 Likes