After last update:
“Failed to Start Simple Desktop Display Manager”.
Using RX580 and Ryzen 5 3600X with KDE Plasma DE.
Re-installing SDDM - didn’t help.
Disconnecting my second monitor also comes with nothing - same error.
1 Like
KDE ryzen + nvidia (proprietary) system prompts the following when update tried.
resolving dependencies…
warning: cannot resolve “expat=2.4.1”, a dependency of “lib32-expat”
warning: cannot resolve “libcap=2.50”, a dependency of “lib32-libcap”
warning: cannot resolve “libelf=0.184”, a dependency of “lib32-libelf”
warning: cannot resolve “expat=2.4.1”, a dependency of “lib32-expat”
warning: cannot resolve “libelf=0.184”, a dependency of “lib32-libelf”
warning: cannot resolve “libelf=0.184”, a dependency of “lib32-libelf”
:: The following packages cannot be upgraded due to unresolvable dependencies:
lib32-expat lib32-libcap lib32-libelf
:: Do you want to skip the above packages for this upgrade? [y/N]
responding default N fails update. Dependency list seems weird.
Packages skipped. No problems so far
I’m getting this when updating:
==> dkms install --no-depmod -m rtbth -v 3.9.6.r8.g989b89b -k 5.12.8-1-MANJARO
Error! Bad return status for module build on kernel: 5.12.8-1-MANJARO (x86_64)
Consult /var/lib/dkms/rtbth/3.9.6.r8.g989b89b/build/make.log for more information.
==> Warning, `dkms install --no-depmod -m rtbth -v 3.9.6.r8.g989b89b -k 5.12.8-1-MANJARO' returned 10
EDIT : It doesn’t really cause any problems though. Bluetooth works just fine.
No problems here on three KDE computers 
regards
caho
1 Like
Check this out:
1 Like
That’s not a valid locale, the last part should be uppercase en_US.UTF-8 (and with a hyphen as @dolour spotted/posted below).
1 Like
I have an Dell XPS 9560 which has a NVIDIA GTX 1050 and I use a CallDigit TS3 dock connected to two DisplayPort connected LG 27UD69P 27" 4K monitors. One monitor is connected with a USB-C-DisplayPort cable and the other is connected with a DisplayPort to DisplayPort cable.
I have had no problems with the NVIDIA drivers in this update with kernel 5.11.22-2 and KDE.
Was expecting problems based on previous reports and had a TimeShift backup ready to go. Thankfully, I didn’t have to use it.
That links to manjaro’s gitlab which
- wants me to log in there
- produces a
404(not found) error
3 Likes
No problems with KDE version running at VMWare VM.
Kudos for awesome update.
Maybe this can help somebody considering the update:
I have the following setup and had no issues regarding the Nvidia drivers:
LG 27UD58P-B 4K monitor connected directly to DP
Samsung S24D300H 1080p monitor connected to DP with an HDMI adapter
NVIDIA RTX 2080 SUPER using proprietary drivers
1 Like
All those normal packages got updated as you can see in the list. Else it would have been reported earlier.
Always has been en_US.utf8 so far via Manjaro install. Dunno where you should get the upper case UTF8 version.
I dont think upper- or lowercase matters (although its consistently uppercase on my list, which also uses just defaults), but there seems to be a “-” missing. Afaik it should be “en_US.UTF-8”
1 Like
Weird, not on my machines:
$ grep en_US /etc/locale.gen
# en_US ISO-8859-1
# en_US.UTF-8 UTF-8
#en_US.UTF-8 UTF-8
#en_US ISO-8859-1
edit: /etc/locale.gen is owned by glibc package. Just extracted the last version in my package cache - it’s the same uppercase spelling there.
I experienced graphical glitches in applications that use OpenGL with my AMD R9 graphics card upon updating mesa to the version in this stable update (21.1.2-0). However, switching to unstable branch and updating just the mesa packages to version 21.1.2-1 seems to have corrected the graphical issue for me. I don’t know if this information is helpful to anybody else, but I thought I’d share it.
edit: Graphical glitches still appearing with mesa 21.1.2-1 even. I was wrong, they haven’t gone away. Ignore everything I have written here… my apologies…
The graphical glitches look like this–> https://bugs.archlinux.org/task/71015?getfile=20328
2 Likes
Maybe check in a live-session with a fresh 21.0.6 ISO if you have the same graphical glitches. They just finished building. Links are in the first post of this thread.
Smooth update on my Acer MM15 & on my Desktop 
Cutefish seems cool… but I think it’s more oriented to be used on a tablet.
I’ll give it a try!
Dunno. I have also
$ locale
LANG=en_US.utf8
LC_CTYPE="en_US.utf8"
LC_NUMERIC="en_US.utf8"
LC_TIME=et_EE.UTF-8
LC_COLLATE="en_US.utf8"
LC_MONETARY="en_US.utf8"
LC_MESSAGES="en_US.utf8"
LC_PAPER=et_EE.UTF-8
LC_NAME=et_EE.UTF-8
LC_ADDRESS=et_EE.UTF-8
LC_TELEPHONE=et_EE.UTF-8
LC_MEASUREMENT=et_EE.UTF-8
LC_IDENTIFICATION=et_EE.UTF-8
LC_ALL=
What’s with the new horribad Firefox? Why does it exist? Is this really “stable” or some horribly wrong gone alpha that accidentally got released to stable upstream?
edit:
As a quick partial fix go to about:config and set browser.proton.enabled to false but this setting will be removed soon. 