[Stable Update] 2021-01-19 - Kernels, XFCE, Plasma, PulseAudio, Pipewire, Mesa, Firefox, Thunderbird, KDE Apps

You can see what i’m talking about in my screenshot, because 5.10 has no additional Markers/Buttons like: Stable/Recommended/Experimental but this Version showed up just Empty in the list, looks atleast to me that someone forgot to signed it.

Every new release since i joined Manjaro Community had this little buttons/markers, thats the reason why im little confused.

The current stable kernel is not labeled as such. Everything else is. :wink:

None of the stable kernels are labeled “stable”. Basically if it is in that list of kernels and NOT marked experimental then it is a STABLE kernel. The one marked “experimental” is the newest Release Canidate kernel.

The other special labels are “real-time” for kernels that are tuned for "real-time"meaning they are designed to guarantee a maximum latency between an external interrupt and the start of the interrupt handler, typically they are used for doing work with audio processing or other timing sensitive applications. The last special label is “LTS” which of course means Long Term Support and as mentioned above it means that it will be supported for a period of 2-8 years that determination is made by the kernel developers and is published at The Linux Kernel Archives - Releases.

The final label “recommended” is the label the manjaro team applies to the latest couple of LTS kernels as they should work for most systems without any issues.

1 Like

As others already mentioned: WhiskerMenu favourites were removed, default filemanager ('im using pcmanfm instead of thunar) had been reset. So far the worst “Xfce4” update by now.
/etc/xdg/autostart/ *.desktop files: “OnlyShowIn” will be ignored. Example:
/etc/xdg/autostart/pamac-tray-budgie.desktop with entry:
OnlyShowIn=Budgie;
will be shown in XFCE
The next XFCE update will probably replace the icons in the panel’s “Power Plugin” (as seen on Arch Linux). These are minor nuisances, the basic manjaro update worked flawlessly as ever. Thanks to the great manjaro team!

Can you share a link about, for those that aren’t running Arch Linux? :slightly_smiling_face:

Yup-

philm seems to know about.

and:
https://forum.xfce.org/viewtopic.php?id=14578

Not a link but xfce4-panel was upgraded yesterday on unstable.

[2021-01-27T17:04:24-0500] [ALPM] upgraded xfce4-panel (4.16.0-1 -> 4.16.1-1)

https://archlinux.org/packages/?sort=&q=xfce4-panel&maintainer=&flagged=

You are mean the lowest latency… high latency is pretty bad :wink:

1 Like

If I’m not mistaken, when you guarantee a maximum latency, you are saying the latency will never be more than that, but it could be less.

1 Like

Happy to find out I’m not the only one coming to this conclusion.

Conflicting dependencies issue with update.

sudo pacman -Syyu for command line shows the following:

:: Starting full system upgrade…
:: Replace knetattach with extra/plasma-desktop? [Y/n] y
:: Replace knetattach with extra/plasma-desktop-primex? [Y/n] y
:: Replace python-pyqtwebengine with extra/python-pyqt5-webengine? [Y/n] y
:: Replace python-sip with extra/python-sip4? [Y/n] y
:: Replace sip with extra/sip4? [Y/n] y
resolving dependencies…
looking for conflicting packages…
warning: removing ‘plasma-desktop’ from target list because it conflicts with ‘plasma-desktop-primex’
:: plasma-desktop-primex and plasma-desktop are in conflict. Remove plasma-desktop? [y/N] n
error: unresolvable package conflicts detected
error: failed to prepare transaction (conflicting dependencies)
:: plasma-desktop-primex and plasma-desktop are in conflict

Searching for “plasma-desktop-primex” on the forum leads me to believe I need ‘plasma-desktop’ OR ‘plasma-desktop-primex’.

How do I get past this conflict?

Thanks for any assistance.

Hi, folks! Update went well; even a minor KDE annoyance (main audio muted every time I log in) seems to have gone away. :slight_smile:

One problem I have noticed: My second NIC is no longer recognized. On-board Ethernet works fine, and both NICs should be handled by the igb module.

Previous Boot
[carl@kotoko ~]$ journalctl -k -b -2 | grep igb
Jan 27 08:00:28 kotoko kernel: igb: Intel(R) Gigabit Ethernet Network Driver - version 5.6.0-k
Jan 27 08:00:28 kotoko kernel: igb: Copyright (c) 2007-2014 Intel Corporation.
Jan 27 08:00:28 kotoko kernel: igb 0000:05:00.0: enabling device (0000 -> 0002)
Jan 27 08:00:28 kotoko kernel: igb 0000:05:00.0: added PHC on eth0
Jan 27 08:00:28 kotoko kernel: igb 0000:05:00.0: Intel(R) Gigabit Ethernet Network Connection
Jan 27 08:00:28 kotoko kernel: igb 0000:05:00.0: eth0: (PCIe:5.0Gb/s:Width x1) 00:1b:21:d3:86:20
Jan 27 08:00:28 kotoko kernel: igb 0000:05:00.0: eth0: PBA No: Unknown
Jan 27 08:00:28 kotoko kernel: igb 0000:05:00.0: Using MSI-X interrupts. 8 rx queue(s), 8 tx queue(s)
[... 3 more entries like this, which are the add-in card ...]
Jan 27 08:00:29 kotoko kernel: igb 0000:06:00.0: added PHC on eth4
Jan 27 08:00:29 kotoko kernel: igb 0000:06:00.0: Intel(R) Gigabit Ethernet Network Connection
Jan 27 08:00:29 kotoko kernel: igb 0000:06:00.0: eth4: (PCIe:2.5Gb/s:Width x1) 04:d4:c4:4a:3c:57
Jan 27 08:00:29 kotoko kernel: igb 0000:06:00.0: eth4: PBA No: FFFFFF-0FF
Jan 27 08:00:29 kotoko kernel: igb 0000:06:00.0: Using MSI-X interrupts. 2 rx queue(s), 2 tx queue(s)
[The above 5 lines are for the on-board NIC.]
Current Boot
[carl@kotoko ~]$ journalctl -k | grep igb       
Jan 31 11:08:34 kotoko kernel: igb: Intel(R) Gigabit Ethernet Network Driver - version 5.6.0-k
Jan 31 11:08:34 kotoko kernel: igb: Copyright (c) 2007-2014 Intel Corporation.
Jan 31 11:08:34 kotoko kernel: igb 0000:06:00.0: added PHC on eth0
Jan 31 11:08:34 kotoko kernel: igb 0000:06:00.0: Intel(R) Gigabit Ethernet Network Connection
Jan 31 11:08:34 kotoko kernel: igb 0000:06:00.0: eth0: (PCIe:2.5Gb/s:Width x1) 04:d4:c4:4a:3c:57
Jan 31 11:08:34 kotoko kernel: igb 0000:06:00.0: eth0: PBA No: FFFFFF-0FF
Jan 31 11:08:34 kotoko kernel: igb 0000:06:00.0: Using MSI-X interrupts. 2 rx queue(s), 2 tx queue(s)
Jan 31 11:08:35 kotoko kernel: igb 0000:06:00.0 enp6s0: renamed from eth0
Jan 31 11:08:43 kotoko kernel: igb 0000:06:00.0 enp6s0: igb: enp6s0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX
Jan 31 11:08:47 kotoko kernel: igb 0000:06:00.0 enp6s0: igb: enp6s0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX

Considering the igb version is the same, I can only assume something has changed so that igb no longer recognizes the card. Previous kernel was 5.4.78-1-MANJARO so that would be my guess. Searching kernel log for the PCI device identifier (I may have that term wrong) shows that it was detected with the previous kernel but is not now:

Kernel log searches
journalctl -k -b -2 | grep "0000:05:00"
	Jan 27 08:00:28 kotoko kernel: pci 0000:05:00.0: [8086:150e] type 00 class 0x020000
	Jan 27 08:00:28 kotoko kernel: pci 0000:05:00.0: reg 0x10: [mem 0xfc500000-0xfc57ffff]
	Jan 27 08:00:28 kotoko kernel: pci 0000:05:00.0: reg 0x1c: [mem 0xfc58c000-0xfc58ffff]
	Jan 27 08:00:28 kotoko kernel: pci 0000:05:00.0: reg 0x30: [mem 0xfc480000-0xfc4fffff pref]
	Jan 27 08:00:28 kotoko kernel: pci 0000:05:00.0: PME# supported from D0 D3hot D3cold
	Jan 27 08:00:28 kotoko kernel: pci 0000:05:00.0: 4.000 Gb/s available PCIe bandwidth, limited by 5 GT/s x1 link at 0000:03:01.0 (capable of 16.000 Gb/s with 5 GT/s x4 link)

journalctl -k | grep "0000:05"
System Info
System:    Host: kotoko Kernel: 5.4.89-1-MANJARO x86_64 bits: 64 Desktop: KDE Plasma 5.20.5 Distro: Manjaro Linux 
Machine:   Type: Desktop Mobo: ASUSTeK model: ROG CROSSHAIR VII HERO v: Rev 1.xx serial: <superuser required> 
           UEFI: American Megatrends v: 2501 date: 07/12/2019 
CPU:       Info: 8-Core model: AMD Ryzen 7 2700X bits: 64 type: MT MCP L2 cache: 4 MiB 
           Speed: 4098 MHz min/max: 2200/3700 MHz Core speeds (MHz): 1: 4098 2: 2063 3: 2058 4: 2060 5: 3474 6: 2088 7: 2090 
           8: 2079 9: 2065 10: 2062 11: 3913 12: 2060 13: 2068 14: 2082 15: 4121 16: 2054 
Graphics:  Device-1: Advanced Micro Devices [AMD/ATI] Ellesmere [Radeon RX 470/480/570/570X/580/580X/590] driver: amdgpu 
           v: kernel 
           Display: x11 server: X.Org 1.20.10 driver: loaded: amdgpu,ati unloaded: modesetting resolution: 2560x1440 
           OpenGL: renderer: Radeon RX 580 Series v: 4.6.13572 Core Profile Context 
Audio:     Device-1: AMD Ellesmere HDMI Audio [Radeon RX 470/480 / 570/580/590] driver: snd_hda_intel 
           Device-2: Advanced Micro Devices [AMD] Family 17h HD Audio driver: snd_hda_intel 
           Device-3: Sunplus Innovation Full HD webcam type: USB driver: snd-usb-audio,uvcvideo 
           Sound Server: ALSA v: k5.4.89-1-MANJARO 
Network:   Device-1: Intel Wireless-AC 9260 driver: iwlwifi 
           IF: wlp4s0 state: down mac: 7e:84:cf:70:02:b4 
           Device-2: Intel I211 Gigabit Network driver: igb 
           IF: enp6s0 state: up speed: 1000 Mbps duplex: full mac: 04:d4:c4:4a:3c:57 
RAID:      Device-1: datastore type: zfs status: ONLINE size: 2.72 TiB free: 1.1 TiB 
           Components: Online: N/A 
Drives:    Local Storage: total: raw: 3.18 TiB usable: 5.9 TiB used: 1011.42 GiB (16.7%) 
           ID-1: /dev/nvme0n1 vendor: Western Digital model: WDS500G3X0C-00SJG0 size: 465.76 GiB 
           ID-2: /dev/sda vendor: Crucial model: CT1000MX500SSD1 size: 931.51 GiB 
           ID-3: /dev/sdb vendor: Crucial model: CT1000MX500SSD1 size: 931.51 GiB 
           ID-4: /dev/sdc vendor: Crucial model: CT1000MX500SSD1 size: 931.51 GiB 
Partition: ID-1: / size: 389.18 GiB used: 237.26 GiB (61.0%) fs: ext4 dev: /dev/nvme0n1p2 
           ID-2: /boot/efi size: 299.4 MiB used: 296 KiB (0.1%) fs: vfat dev: /dev/nvme0n1p1 
Swap:      ID-1: swap-1 type: partition size: 69.06 GiB used: 0 KiB (0.0%) dev: /dev/nvme0n1p3 
Sensors:   System Temperatures: cpu: 46.6 C mobo: N/A gpu: amdgpu temp: 61.0 C 
           Fan Speeds (RPM): N/A gpu: amdgpu fan: 785 
Info:      Processes: 477 Uptime: 10h 32m Memory: 62.78 GiB used: 13.16 GiB (21.0%) Shell: Bash inxi: 3.2.02

Update: The same behavior persists on kernel 5.10, leading me to believe it’s not a kernel issue. I guess I’ll go post in the Networking area.

This will become an urgent issue in a week, but for now it’s more of an interesting problem. Would anyone have some advice on how to fix it?

Well it took all night, but after missing, what, four updates? Five? Since it took my entire attention span to live through this year’s US election cycle plus post-election absurdities and since said attention span did not return until late last week, I hadn’t updated my Openbox Manjaro HP Elitebook since the end of October.

It only took hours because I first had to do my backup routine where I backup my home folder and then make a disk image of the current setup after archiving an older disk image to free up space on the SD card they live on and then it took some time to download some billions of GB of data and a couple of AUR packages needed rebuilding also and–

It all works. Ok the laptop boots and the WiFi connects as usual and the internet works fine. System sound is working but I have to nap before seeing if jack, alsa, and pulse are still playing well enough together that I can make music with them. But I am just happy that after updating almost 1000 packages, it starts up like nothing much happened at all!

This is the awesomest rolling release distro ever.

2 Likes

1 Like

That is correct.

A post was split to a new topic: “Something went wrong” after update

8 posts were split to a new topic: Help with checkrebuild results

Should i upgrade my kernel from 5.9.16-1 to 5.10.7-3?

Or its okay to stay till 5.10 goes LTSC?

5.10 is already marked as lts on kernel.org and 5.9 is EOL, so you should be ok updating.

In Manjaro however you don’t have to replace 5.9 with 5.10. Just install 5.10 and try it. If it acts strange on your system, choose 5.9 in grub at boot time and wait for next update.

3 Likes