that python guide is ridiculously complex, what are my chances if i just run the update, and re-install all packages i use?
we can easily bypass it ! we can change a package for another 
for zsh is in post #4 (edit: or ok for use old profil)
1 Like
Yes, there might be slow starts of applications when a certain package got installed as dependency. See troubleshoots for help.
1 Like
It’s useful if you have too many (AUR and pip) packages to remember.
No problem.
If you have so few python (AUR and pip) packages you can remember them all, that’s the easy way.
EDIT: added “(AUR and pip)”
3 Likes
Will be a fix for zsh, or will stay as it is??
I dont see speed issues so far
It doesn’t fix Dolphin
1 Like
I changed the text a little to hopefully make it clear that the guide is for 3rd party packages like from the AUR. With the system update regular packages provided by use have been updated against python 3.11 already.
@philm Any chance that dolphin 23.04.1-2 will be brought in soon?
@papajoke Thanks for the warning.
I keep about 24 Dolphin windows open, across 6 desktops,
with about 10 tabs in each, and they re-open automatically when I log on.
It’s how I easily find the various things I’m working on,
coz I couldn’t figure out how to use KDE tools that say they do this kind of thing.
That is why we have the testing branch and rely on community feedback. Some issues only get detected in the stable branch as more people use it. The dolphin issue should been fixed with dolphin-23.04.1-1.1. Regarding ZSH we are still working on a proper fix.
3 Likes
But these are noticeable, albeit minor, bugs in popular applications 
1 Like
I am experiencing problems with tuxedo-control-center especially its dkms kernel modules with gcc version 13:
DKMS make.log for tuxedo-keyboard-3.2.3 for kernel 5.15.114-1-MANJARO (x86_64)
So 04 Jun 2023 10:13:29 CEST
make -C /lib/modules/5.15.114-1-MANJARO/build M=/var/lib/dkms/tuxedo-keyboard/3.2.3/build modules
warning: the compiler differs from the one used to build the kernel
The kernel was built by: gcc (GCC) 12.2.1 20230201
You are using: gcc (GCC) 13.1.1 20230429
CC [M] /var/lib/dkms/tuxedo-keyboard/3.2.3/build/./src/clevo_wmi.o
CC [M] /var/lib/dkms/tuxedo-keyboard/3.2.3/build/./src/tuxedo_keyboard.o
CC [M] /var/lib/dkms/tuxedo-keyboard/3.2.3/build/./src/clevo_acpi.o
CC [M] /var/lib/dkms/tuxedo-keyboard/3.2.3/build/./src/tuxedo_io/tuxedo_io.o
CC [M] /var/lib/dkms/tuxedo-keyboard/3.2.3/build/./src/uniwill_wmi.o
cc1: error: cannot load plugin ./scripts/gcc-plugins/structleak_plugin.so: ./scripts/gcc-plugins/structleak_plugin.so: undefined symbol: tree_code_type
cc1: error: cannot load plugin ./scripts/gcc-plugins/structleak_plugin.so: ./scripts/gcc-plugins/structleak_plugin.so: undefined symbol: tree_code_type
cc1: error: cannot load plugin ./scripts/gcc-plugins/structleak_plugin.so: ./scripts/gcc-plugins/structleak_plugin.so: undefined symbol: tree_code_type
Maybe this is related to:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108634
I installed the previous gcc-12 and tried to install the dkms kernel modules again with:
export CC=gcc-12
dkms autoinstall
But it also failed with the same error as before.
Does anybody know how to switch the gcc-version for dkms make?
Telegram-desktop stopped working/launching.
What else, the tray no longer displays charging correctly, the icon is superimposed on the font (in i3wm, I use it by default.)
Well there is no bug with DKMS nor the kernel. We simply didn’t compile our kernels against the new toolchain, hence dkms is currently broken. Wait for kernel updates.
Gnome. Brave and Badwolf browsers not working properly.
2 Likes
After upgrading to Plasma, at the ejectur konsole, I get this message:
bash: /home/mlpdel/.bashrc: line 139: syntax error: end of file not expected
And my baschrc file has 138 lines.
In addition, the brave browser does not work very well, because the images appear on top of each other and some blink and the text is not visible.
KDE reset the adaptive mouse speed settings, went into settings and returned them to what they were.
2 Likes
Thanks for your quick reply.
A possible workaround might be to somehow configure DKMS to use gcc-12 for compiling kernel modules right?
Anyways, it’s okay for me to wait till the next update.
It’s just the keyboard light and fan-control which is not working at the moment.
The emoji display is broken, although there were problems with it before 
Not really, though, it breaks if it’s not UTF-8
Another one with zsh broken, and chsh doesn’t change to zsh again. As I see there are several issues, I restored system state with timeshift to the copy made just before (zsh is back again) and I’ll wait some days to repeat the update.
2 Likes
Hey,
after having this update installed, the entire X server collapsed on me, causing my gnome session to restart. All I could get from the system logs is this
Jun 04 10:55:57 karolyi-desktop gnome-shell[1503]: Received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadMatch (invalid parameter attributes)'.
(Details: serial 33231 error_code 8 request_code 147 (unknown) minor_code 6)
(Note to programmers: normally, X errors are reported asynchronously;
that is, you will receive the error a while after causing it.
To debug your program, run it with the MUTTER_SYNC environment
variable to change this behavior. You can then get a meaningful
backtrace from your debugger if you break on the meta_x_error() function.)
Jun 04 10:55:59 karolyi-desktop systemd-coredump[14208]: [🡕] Process 1503 (gnome-shell) of user 1000 dumped core.
Stack trace of thread 1503:
#0 0x00007fbfcd69f26c n/a (libc.so.6 + 0x8926c)
#1 0x00007fbfcd64fa08 raise (libc.so.6 + 0x39a08)
#2 0x000055d0010fcf19 n/a (gnome-shell + 0x3f19)
#3 0x00007fbfcd64fab0 n/a (libc.so.6 + 0x39ab0)
#4 0x00007fbfcde99408 g_log_structured_array (libglib-2.0.so.0 + 0x5e408)
#5 0x00007fbfcde99703 g_log_default_handler (libglib-2.0.so.0 + 0x5e703)
#6 0x00007fbfcde99975 g_logv (libglib-2.0.so.0 + 0x5e975)
#7 0x00007fbfcde99c64 g_log (libglib-2.0.so.0 + 0x5ec64)
#8 0x00007fbfcd917bc7 n/a (libmutter-12.so.0 + 0x117bc7)
#9 0x00007fbfcd27b3dc _XError (libX11.so.6 + 0x443dc)
#10 0x00007fbfcd27b4e8 n/a (libX11.so.6 + 0x444e8)
#11 0x00007fbfcd27b585 n/a (libX11.so.6 + 0x44585)
#12 0x00007fbfcd27b63a _XEventsQueued (libX11.so.6 + 0x4463a)
#13 0x00007fbfcd269c48 XPending (libX11.so.6 + 0x32c48)
#14 0x00007fbfcde95a0f g_main_context_check (libglib-2.0.so.0 + 0x5aa0f)
#15 0x00007fbfcdef2078 n/a (libglib-2.0.so.0 + 0xb7078)
#16 0x00007fbfcde94c7f g_main_loop_run (libglib-2.0.so.0 + 0x59c7f)
#17 0x00007fbfcd8cdc5b meta_context_run_main_loop (libmutter-12.so.0 + 0xcdc5b)
#18 0x000055d0010fc526 n/a (gnome-shell + 0x3526)
#19 0x00007fbfcd639850 n/a (libc.so.6 + 0x23850)
#20 0x00007fbfcd63990a __libc_start_main (libc.so.6 + 0x2390a)
#21 0x000055d0010fc835 n/a (gnome-shell + 0x3835)
Stack trace of thread 1508:
#0 0x00007fbfcd713c0f __poll (libc.so.6 + 0xfdc0f)
#1 0x00007fbfcdef217f n/a (libglib-2.0.so.0 + 0xb717f)
#2 0x00007fbfcde94c7f g_main_loop_run (libglib-2.0.so.0 + 0x59c7f)
#3 0x00007fbfce0f5d3c n/a (libgio-2.0.so.0 + 0x10ed3c)
#4 0x00007fbfcdec2315 n/a (libglib-2.0.so.0 + 0x87315)
#5 0x00007fbfcd69d44b n/a (libc.so.6 + 0x8744b)
#6 0x00007fbfcd720e40 n/a (libc.so.6 + 0x10ae40)
Stack trace of thread 1509:
#0 0x00007fbfcd713c0f __poll (libc.so.6 + 0xfdc0f)
#1 0x00007fbfcdef217f n/a (libglib-2.0.so.0 + 0xb717f)
#2 0x00007fbfcde941a2 g_main_context_iteration (libglib-2.0.so.0 + 0x591a2)
#3 0x00007fbfce1f6fde n/a (libdconfsettings.so + 0x5fde)
#4 0x00007fbfcdec2315 n/a (libglib-2.0.so.0 + 0x87315)
#5 0x00007fbfcd69d44b n/a (libc.so.6 + 0x8744b)
#6 0x00007fbfcd720e40 n/a (libc.so.6 + 0x10ae40)
Stack trace of thread 1505:
#0 0x00007fbfcd7192ed syscall (libc.so.6 + 0x1032ed)
#1 0x00007fbfcdeeb7b5 g_cond_wait (libglib-2.0.so.0 + 0xb07b5)
#2 0x00007fbfcde5ffb4 n/a (libglib-2.0.so.0 + 0x24fb4)
#3 0x00007fbfcdec6f9e n/a (libglib-2.0.so.0 + 0x8bf9e)
#4 0x00007fbfcdec2315 n/a (libglib-2.0.so.0 + 0x87315)
#5 0x00007fbfcd69d44b n/a (libc.so.6 + 0x8744b)
#6 0x00007fbfcd720e40 n/a (libc.so.6 + 0x10ae40)
Stack trace of thread 1511:
#0 0x00007fbfcd699f0e n/a (libc.so.6 + 0x83f0e)
#1 0x00007fbfcd69c7a0 pthread_cond_wait (libc.so.6 + 0x867a0)
#2 0x00007fbfcc395291 _ZN7mozilla6detail21ConditionVariableImpl8wait_forERNS0_9MutexImplERKNS_16BaseTimeDurationINS_27TimeDurationValueCalculatorEEE (libmozjs-102.so + 0x1595291)
#3 0x00007fbfcc395192 n/a (libmozjs-102.so + 0x1595192)
#4 0x00007fbfcc54e4be n/a (libmozjs-102.so + 0x174e4be)
#5 0x00007fbfcd69d44b n/a (libc.so.6 + 0x8744b)
#6 0x00007fbfcd720e40 n/a (libc.so.6 + 0x10ae40)
Stack trace of thread 1512:
#0 0x00007fbfcd699f0e n/a (libc.so.6 + 0x83f0e)
#1 0x00007fbfcd69c7a0 pthread_cond_wait (libc.so.6 + 0x867a0)
#2 0x00007fbfcc395291 _ZN7mozilla6detail21ConditionVariableImpl8wait_forERNS0_9MutexImplERKNS_16BaseTimeDurationINS_27TimeDurationValueCalculatorEEE (libmozjs-102.so + 0x1595291)
#3 0x00007fbfcc395192 n/a (libmozjs-102.so + 0x1595192)
#4 0x00007fbfcc54e4be n/a (libmozjs-102.so + 0x174e4be)
#5 0x00007fbfcd69d44b n/a (libc.so.6 + 0x8744b)
#6 0x00007fbfcd720e40 n/a (libc.so.6 + 0x10ae40)
Stack trace of thread 1513:
#0 0x00007fbfcd699f0e n/a (libc.so.6 + 0x83f0e)
#1 0x00007fbfcd69c7a0 pthread_cond_wait (libc.so.6 + 0x867a0)
#2 0x00007fbfcc395291 _ZN7mozilla6detail21ConditionVariableImpl8wait_forERNS0_9MutexImplERKNS_16BaseTimeDurationINS_27TimeDurationValueCalculatorEEE (libmozjs-102.so + 0x1595291)
#3 0x00007fbfcc395192 n/a (libmozjs-102.so + 0x1595192)
#4 0x00007fbfcc54e4be n/a (libmozjs-102.so + 0x174e4be)
#5 0x00007fbfcd69d44b n/a (libc.so.6 + 0x8744b)
#6 0x00007fbfcd720e40 n/a (libc.so.6 + 0x10ae40)
Stack trace of thread 1514:
#0 0x00007fbfcd699f0e n/a (libc.so.6 + 0x83f0e)
#1 0x00007fbfcd69c7a0 pthread_cond_wait (libc.so.6 + 0x867a0)
#2 0x00007fbfcc395291 _ZN7mozilla6detail21ConditionVariableImpl8wait_forERNS0_9MutexImplERKNS_16BaseTimeDurationINS_27TimeDurationValueCalculatorEEE (libmozjs-102.so + 0x1595291)
#3 0x00007fbfcc395192 n/a (libmozjs-102.so + 0x1595192)
#4 0x00007fbfcc54e4be n/a (libmozjs-102.so + 0x174e4be)
#5 0x00007fbfcd69d44b n/a (libc.so.6 + 0x8744b)
#6 0x00007fbfcd720e40 n/a (libc.so.6 + 0x10ae40)
Stack trace of thread 1516:
#0 0x00007fbfcd699f0e n/a (libc.so.6 + 0x83f0e)
#1 0x00007fbfcd69c7a0 pthread_cond_wait (libc.so.6 + 0x867a0)
#2 0x00007fbfcc395291 _ZN7mozilla6detail21ConditionVariableImpl8wait_forERNS0_9MutexImplERKNS_16BaseTimeDurationINS_27TimeDurationValueCalculatorEEE (libmozjs-102.so + 0x1595291)
#3 0x00007fbfcc395192 n/a (libmozjs-102.so + 0x1595192)
#4 0x00007fbfcc54e4be n/a (libmozjs-102.so + 0x174e4be)
#5 0x00007fbfcd69d44b n/a (libc.so.6 + 0x8744b)
#6 0x00007fbfcd720e40 n/a (libc.so.6 + 0x10ae40)
Stack trace of thread 1517:
#0 0x00007fbfcd699f0e n/a (libc.so.6 + 0x83f0e)
#1 0x00007fbfcd69c7a0 pthread_cond_wait (libc.so.6 + 0x867a0)
#2 0x00007fbfcc395291 _ZN7mozilla6detail21ConditionVariableImpl8wait_forERNS0_9MutexImplERKNS_16BaseTimeDurationINS_27TimeDurationValueCalculatorEEE (libmozjs-102.so + 0x1595291)
#3 0x00007fbfcc395192 n/a (libmozjs-102.so + 0x1595192)
#4 0x00007fbfcc54e4be n/a (libmozjs-102.so + 0x174e4be)
#5 0x00007fbfcd69d44b n/a (libc.so.6 + 0x8744b)
#6 0x00007fbfcd720e40 n/a (libc.so.6 + 0x10ae40)
Stack trace of thread 1518:
#0 0x00007fbfcd699f0e n/a (libc.so.6 + 0x83f0e)
#1 0x00007fbfcd69c7a0 pthread_cond_wait (libc.so.6 + 0x867a0)
#2 0x00007fbfcc395291 _ZN7mozilla6detail21ConditionVariableImpl8wait_forERNS0_9MutexImplERKNS_16BaseTimeDurationINS_27TimeDurationValueCalculatorEEE (libmozjs-102.so + 0x1595291)
#3 0x00007fbfcc395192 n/a (libmozjs-102.so + 0x1595192)
#4 0x00007fbfcc54e4be n/a (libmozjs-102.so + 0x174e4be)
#5 0x00007fbfcd69d44b n/a (libc.so.6 + 0x8744b)
#6 0x00007fbfcd720e40 n/a (libc.so.6 + 0x10ae40)
Stack trace of thread 1515:
#0 0x00007fbfcd699f0e n/a (libc.so.6 + 0x83f0e)
#1 0x00007fbfcd69c7a0 pthread_cond_wait (libc.so.6 + 0x867a0)
#2 0x00007fbfcc395291 _ZN7mozilla6detail21ConditionVariableImpl8wait_forERNS0_9MutexImplERKNS_16BaseTimeDurationINS_27TimeDurationValueCalculatorEEE (libmozjs-102.so + 0x1595291)
#3 0x00007fbfcc395192 n/a (libmozjs-102.so + 0x1595192)
#4 0x00007fbfcc54e4be n/a (libmozjs-102.so + 0x174e4be)
#5 0x00007fbfcd69d44b n/a (libc.so.6 + 0x8744b)
#6 0x00007fbfcd720e40 n/a (libc.so.6 + 0x10ae40)
Stack trace of thread 4714:
#0 0x00007fbfcd7192ed syscall (libc.so.6 + 0x1032ed)
#1 0x00007fbfcdeebd03 g_cond_wait_until (libglib-2.0.so.0 + 0xb0d03)
#2 0x00007fbfcde5ff83 n/a (libglib-2.0.so.0 + 0x24f83)
#3 0x00007fbfcdec79fb n/a (libglib-2.0.so.0 + 0x8c9fb)
#4 0x00007fbfcdec2315 n/a (libglib-2.0.so.0 + 0x87315)
#5 0x00007fbfcd69d44b n/a (libc.so.6 + 0x8744b)
#6 0x00007fbfcd720e40 n/a (libc.so.6 + 0x10ae40)
Stack trace of thread 8202:
#0 0x00007fbfcd713c0f __poll (libc.so.6 + 0xfdc0f)
#1 0x00007fbfa11ab8c7 n/a (libpulse.so.0 + 0x338c7)
#2 0x00007fbfa119546c pa_mainloop_poll (libpulse.so.0 + 0x1d46c)
#3 0x00007fbfa119f42c pa_mainloop_iterate (libpulse.so.0 + 0x2742c)
#4 0x00007fbfa119f4e1 pa_mainloop_run (libpulse.so.0 + 0x274e1)
#5 0x00007fbfa11afc02 n/a (libpulse.so.0 + 0x37c02)
#6 0x00007fbfa114cc67 n/a (libpulsecommon-16.1.so + 0x5bc67)
#7 0x00007fbfcd69d44b n/a (libc.so.6 + 0x8744b)
#8 0x00007fbfcd720e40 n/a (libc.so.6 + 0x10ae40)
Stack trace of thread 1506:
#0 0x00007fbfcd713c0f __poll (libc.so.6 + 0xfdc0f)
#1 0x00007fbfcdef217f n/a (libglib-2.0.so.0 + 0xb717f)
#2 0x00007fbfcde941a2 g_main_context_iteration (libglib-2.0.so.0 + 0x591a2)
#3 0x00007fbfcde941f2 n/a (libglib-2.0.so.0 + 0x591f2)
#4 0x00007fbfcdec2315 n/a (libglib-2.0.so.0 + 0x87315)
#5 0x00007fbfcd69d44b n/a (libc.so.6 + 0x8744b)
#6 0x00007fbfcd720e40 n/a (libc.so.6 + 0x10ae40)
ELF object binary architecture: AMD x86-64
░░ Subject: Process 1503 (gnome-shell) dumped core
It happened when I went on to install the python3.10 package, that started to compile itself. Weird.
Also, I have strange artifacts appearing around my thunderbird window:
Make that all Qt-based applications. (jackd kit, keepassxc, etc).
2 Likes