Jazz
13 February 2023 15:47
47
I tried to open LibreOffice Writer and it kept crashing each time. I renamed .cache, .config and ~/.local/share/kscreen, then rebooted - now everything works again, but I’m not able to use all my hard work adjusting Manjaro KDE Plasma (KWin) to suit my needs. This is not an acceptable solution for this issue. It’s just a dirty temporary workaround.
EDIT: I just restored my old .config only then rebooted. But the system behaves just as the same as right after the update. My applications and System Settings items keep crashing.
There is a package that does this
community/snap-pac 3.0.1-2 [Installiert]
Pacman hooks that use snapper to create pre/post btrfs snapshots like openSUSE's YaST
I just updated Thunderbird and Chromium after the restore, I’ll wait a few days … something doesn’t fit anymore (w/ latest mesa, x-org, KDE, QT … no idea)
Jazz
13 February 2023 16:50
52
Turned out the culprit is kvantum. It seems like updating to 1.0.9 fixes the issue.
opened 12:52PM - 10 Feb 23 UTC
closed 06:25PM - 10 Feb 23 UTC
# overview
After upgrading to kvantum 1.0.8-1 I experienced crashes of differ… ent applications.
## system info
arch linux, kernel 6.1.10-arch1-1
xorg-server 21.1.7-1
plasma 5.26.5-1
plasma-framework 5.102.0-1
qt5-base 5.15.8+kde+r181-1
qt6-base 6.4.2-1
kvantum 1.0.8-1
kvantum-themes: [Sweet KDE](https://store.kde.org/p/1294013/), [Monochrome KDE](https://store.kde.org/p/1279088) (other, built-in themes seemed not to cause any crashes)
## affected applications
- KDE Plasma System Settings
- [libreoffice](https://www.libreoffice.org/)
- [cool-retro-term](https://github.com/Swordfish90/cool-retro-term)
# steps-to-reproduce
## System settings
- 1. open system settings
- 2. navigate to applications > Default Applications --> crash
## libreoffice
- 1. start libreoffice (launcer, not any specific program like calc / writer)
- 2. open Tools > Options --> crash
OR
- 2. create new (calc / writer) document --> crash
## cool-retro-term
- 1. start cool-retro-term
- 2. rightclick > edit > settings
- 3. select tab "Terminal" --> crash
# details
I started all programs with gdb and found this:
```
Thread 1 "systemsettings" received signal SIGSEGV, Segmentation fault.
0x00007fffe80d5de1 in Kvantum::Style::drawComplexControl(QStyle::ComplexControl, QStyleOptionComplex const*, QPainter*, QWidget const*) const () from /usr/lib/qt/plugins/styles/libkvantum.so
```
```
Thread 1 "soffice.bin" received signal SIGSEGV, Segmentation fault.
0x00007fffe3f80de1 in Kvantum::Style::drawComplexControl(QStyle::ComplexControl, QStyleOptionComplex const*, QPainter*, QWidget const*) const () from /usr/lib/qt/plugins/styles/libkvantum.so
```
```
Thread 1 "cool-retro-term" received signal SIGSEGV, Segmentation fault.
0x00007fffe80d5de1 in Kvantum::Style::drawComplexControl(QStyle::ComplexControl, QStyleOptionComplex const*, QPainter*, QWidget const*) const () from /usr/lib/qt/plugins/styles/libkvantum.so
```
here is the complete steps + backtrace
```
$ gdb cool-retro-term
[...]
(gdb) run
[reproducing the steps mentioned above]
Thread 1 "cool-retro-term" received signal SIGSEGV, Segmentation fault.
0x00007fffe80d5de1 in Kvantum::Style::drawComplexControl(QStyle::ComplexControl, QStyleOptionComplex const*, QPainter*, QWidget const*) const () from /usr/lib/qt/plugins/styles/libkvantum.so
(gdb) backtrace
#0 0x00007fffe80d5de1 in Kvantum::Style::drawComplexControl(QStyle::ComplexControl, QStyleOptionComplex const*, QPainter*, QWidget const*) const () from /usr/lib/qt/plugins/styles/libkvantum.so
#1 0x00007fffd512154a in ?? ()
from /usr/lib/qt/qml/org/kde/qqc2desktopstyle/private/libqqc2desktopstyleplugin.so
#2 0x00007ffff104746a in ■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■ () from /usr/lib/libQt5Quick.so.5
#3 0x00007ffff100233b in ?? () from /usr/lib/libQt5Quick.so.5
#4 0x00007ffff1052739 in QQuickWindow::event(QEvent*) () from /usr/lib/libQt5Quick.so.5
#5 0x00007ffff7978b5c in QApplicationPrivate::notify_helper(QObject*, QEvent*) ()
from /usr/lib/libQt5Widgets.so.5
#6 0x00007ffff668df48 in QCoreApplication::notifyInternal2(QObject*, QEvent*) ()
from /usr/lib/libQt5Core.so.5
#7 0x00007ffff7133488 in QPlatformWindow::windowEvent(QEvent*) () from /usr/lib/libQt5Gui.so.5
#8 0x00007ffff797d041 in QApplication::notify(QObject*, QEvent*) () from /usr/lib/libQt5Widgets.so.5
#9 0x00007ffff668df48 in QCoreApplication::notifyInternal2(QObject*, QEvent*) ()
from /usr/lib/libQt5Core.so.5
#10 0x00007ffff66d84b3 in QTimerInfoList::activateTimers() () from /usr/lib/libQt5Core.so.5
#11 0x00007ffff66d8af2 in ?? () from /usr/lib/libQt5Core.so.5
#12 0x00007ffff591682b in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#13 0x00007ffff596dcc9 in ?? () from /usr/lib/libglib-2.0.so.0
#14 0x00007ffff59150e2 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#15 0x00007ffff66d8c6c in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) ()
from /usr/lib/libQt5Core.so.5
#16 0x00007ffff66866ec in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) ()
from /usr/lib/libQt5Core.so.5
#17 0x00007ffff6691219 in QCoreApplication::exec() () from /usr/lib/libQt5Core.so.5
#18 0x000055555555789e in ?? ()
#19 0x00007ffff6e3c790 in ?? () from /usr/lib/libc.so.6
#20 0x00007ffff6e3c84a in __libc_start_main () from /usr/lib/libc.so.6
#21 0x0000555555558165 in ?? ()
```
# possible workaround:
I temporarily downgrade to kvantum 1.0.7-1 and cannot reproduce the errors with it.
---
I hope the provided information helps, please tell me if you need anything else.
Hello this is the first time I had trouble after an update, but it’s a big one as it left my system completely inoperable.
I could luckily still start Yakuake and found the culprit to be plasmashell which was sitting at 28GB memory usage.
Only thing I could do was to revert the update via Timeshift.
EDIT:
Via binary search I found the package responsible for the issue.
1 Like
It will take some time before Manjaro team tags it as “LTS” and “Recommended”
2 Likes
Friendly piece of advise; avoid Wayland.
1 Like
Yochanan
13 February 2023 23:38
57
A post was split to a new topic: Pamac update fails
hmm, I don’t use KDE Wayland but I put glibc & lib32-glibc to the ignore list and restarted the upgrade, now everything worked without problems.
Do you think I should keep glibc & lib32-glibc on my ignore list or can they be updated after the main upgrade as well?
yt87
14 February 2023 04:35
59
Somewhat similar experience here. Yesterday I did get notification about upgrade from pamac-tray-plasma. pamac-manager displayed list of upgraded packages. Today when I tried to run update, the same widget told me that my system is up-to-date. I modified the list of mirrors as described here: How to Change Manjaro Mirrors List which solved the issue.
fsw
14 February 2023 08:02
61
The patched Pamac update with CLI auth works really well and I like it a lot, as I am always using the terminal to upgrade my 3 Manjaro boxes
Yochanan
14 February 2023 19:29
62
9 posts were split to a new topic: Still no fix to OBS
Gimp’s resynthesizer plugin didn’t appear when selected. Checking the log, I could see a message:
ImportError: /usr/lib/python2.7/site-packages/cairo/_cairo.so: undefined symbol: cairo_tee_surface_index
Solved by rebuilding python2-cairo from AUR.
1 Like
It works! I was so excited for the feature that i did upgrade pamac before the system, just so i could do the system upgrade with this new feature
So I’ve been told. I’m excited by it as well, but couldn’t use the feature this time. Next time, though…
yes, the KDE issues are definitely caused by these libraries:
if it’s in the ignore list everything works, as soon as 2.37-2 is installed plasma breaks
Glad you figured it out. But it is strange, especially seeing:
$ pamac list --installed | grep --ignore-case glibc
glibc 2.37-2 core 49.8 MB
lib32-glibc 2.37-2 core 18.9 MB
maybe you can downgrade both packages to v. 2.36-7 (not tested) e.g.
pacman -U https://archive.archlinux.org/packages/g/glibc/glibc-2.36-7-x86_64.pkg.tar.zst
pacman -U https://archive.archlinux.org/packages/l/lib32-glibc/lib32-glibc-2.36-7-x86_64.pkg.tar.zst
