You are not logged in.
after disabling krunner dropbox crashes. so i removed dropbox but plasmashell keeps crashing
Jan 14 13:23:04 kiste signond[2340]: Couldn't start kwalletd: QDBusError("org.freedesktop.DBus.Error.Disconnected", "Not connected to D-Bus server")
Jan 14 13:23:04 kiste signond[2340]: Couldn't start kwalletd: QDBusError("org.freedesktop.DBus.Error.Disconnected", "Not connected to D-Bus server")
Jan 14 13:23:04 kiste signond[2340]: Challenge produces CRASH!
Jan 14 13:23:04 kiste signond[2340]: Challenge produces CRASH!
Jan 14 13:22:48 kiste systemd-coredump[2259]: Process 2243 (plasmashell) of user 1000 dumped core.
Stack trace of thread 2243:
#0 0x00007f21d0dd5289 n/a (n/a)
Offline
After updating to frameworks 5.30 all crashes are gone but the screen stays black.
Offline
@MrPeacock
Does it still happen if you use fresh Plasma and KWin config? Also, try deleting KDE specific files from ~/.cache, logout and log back in, as they can cause weird issues after upgrades.
Last edited by QuartzDragon (2017-01-14 16:19:13)
Offline
@Arojas: shouldn't be there a krunner plugin that offers to install software if an app is not found on system? Or am I wrong? I'm pretty sure i read about that on plasma-devel ML.
And i can't see any interactive preview in notifications (eg: trying to get a screenshot with spectacle, i can't see the new gorgeous-looking notification!)
Offline
@QuartzDragon this only happens on wayland session. I'll give it a try and delete .cache dir
EDIT: No success with deleted cache dir
Last edited by MrPeacock (2017-01-14 16:34:37)
Offline
@Arojas: shouldn't be there a krunner plugin that offers to install software if an app is not found on system? Or am I wrong? I'm pretty sure i read about that on plasma-devel ML.
And i can't see any interactive preview in notifications (eg: trying to get a screenshot with spectacle, i can't see the new gorgeous-looking notification!)
If you mean https://aur.archlinux.org/packages/appstreamrunner-git/ no, it didn't make it to 5.9
And for the notification preview think you need spectacle-git (what will become 17.04). Plasma guys have an unfortunate tendency to use not-yet-available features without warning in their release notes screenshots...
Offline
@QuartzDragon this only happens on wayland session. I'll give it a try and delete .cache dir
EDIT: No success with deleted cache dir
Try backing your Plasma and KWin configs anyway, and see if that changes anything. Just to see what happens. Sometimes, it helps.
I've had weird effects on my kdeglobals config in Wayland that cause them to stop working in X11 while they work fine in the Wayland session.
Offline
@Arojas, you're right: https://mail.kde.org/pipermail/plasma-d … 64670.html .
Thanks for the info!
Offline
So, I created a new user to try plasmawayland with fresh configs and caches. There are still the same problems so I guess this is an upstream bug with the beta release...
P
Offline
So, I created a new user to try plasmawayland with fresh configs and caches. There are still the same problems so I guess this is an upstream bug with the beta release...
P
So far everything points to an incompatibility with Qt 5.8. This needs to be reported upstream with a proper backtrace, but that requires compiling Qt with debug symbols.
Offline
Hello Arojas,
which qt packages needs to be compiled with debugging symbols? Can you provide the current PKGBUILD files for qt5.8rc? I want to compile and track down the bug.
Last edited by MrPeacock (2017-01-16 19:51:16)
Offline
Hello Arojas,
which qt packages needs to be compiled with debugging symbols? Can you provide the current PKGBUILD files for qt5.8rc? I want to compile and track down the bug.
Check the backtrace for the plasmashell segfault, and see which libraries appear. The packages that contain those libraries are the ones that need to be rebuilt (at least qt5-base and qt5-wayland).
You can get the PKGBUILDs from abs:
$ abs kde-unstable/qt5-base
Offline
Hi Arojas,
after recompiling wayland (libwayland-client) i get a crash displayed. kcrash now shows some information. it seems i am affected by this bug
https://bugs.kde.org/show_bug.cgi?id=372597
Application: KDE Accessibility Tool (kaccess), signal: Segmentation fault
Using host libthread_db library "/usr/lib/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f99811d1840 (LWP 1980))]
Thread 2 (Thread 0x7f996e3ad700 (LWP 1982)):
#0 0x00007f9980c1248d in poll () from /usr/lib/libc.so.6
#1 0x00007f99761c4786 in ?? () from /usr/lib/libglib-2.0.so.0
#2 0x00007f99761c489c in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#3 0x00007f997d2583eb in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQt5Core.so.5
#4 0x00007f997d201c1a in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQt5Core.so.5
#5 0x00007f997d0239f3 in QThread::exec() () from /usr/lib/libQt5Core.so.5
#6 0x00007f9979cd00c5 in ?? () from /usr/lib/libQt5DBus.so.5
#7 0x00007f997d028658 in ?? () from /usr/lib/libQt5Core.so.5
#8 0x00007f9977c88454 in start_thread () from /usr/lib/libpthread.so.0
#9 0x00007f9980c1b7df in clone () from /usr/lib/libc.so.6
Thread 1 (Thread 0x7f99811d1840 (LWP 1980)):
[KCrash Handler]
#6 0x00007f996d163138 in wl_map_insert_at (map=<optimized out>, flags=flags@entry=0, i=<optimized out>, data=<optimized out>) at src/wayland-util.c:249
#7 0x00007f996d15efbe in proxy_destroy (proxy=0x25c5cf0) at src/wayland-client.c:411
#8 wl_proxy_destroy (proxy=0x25c5cf0) at src/wayland-client.c:442
#9 0x00007f996c2891e5 in KWayland::Client::Registry::release() () from /usr/lib/libKF5WaylandClient.so.5
#10 0x00007f996c28920e in KWayland::Client::Registry::~Registry() () from /usr/lib/libKF5WaylandClient.so.5
#11 0x00007f996c2892e9 in KWayland::Client::Registry::~Registry() () from /usr/lib/libKF5WaylandClient.so.5
#12 0x00007f997d22d791 in QObjectPrivate::deleteChildren() () from /usr/lib/libQt5Core.so.5
#13 0x00007f997d2370ef in QObject::~QObject() () from /usr/lib/libQt5Core.so.5
#14 0x00007f99660fe393 in ?? () from /usr/lib/qt/plugins/kf5/org.kde.kwindowsystem.platforms/KF5WindowSystemKWaylandPlugin.so
#15 0x00007f9980b68990 in __run_exit_handlers () from /usr/lib/libc.so.6
#16 0x00007f9980b689ea in exit () from /usr/lib/libc.so.6
#17 0x00007f9980b53298 in __libc_start_main () from /usr/lib/libc.so.6
#18 0x000000000040066a in _start ()
Offline
Just curious...
With a week until the Plasma 5.9 release, can't we just have the Arch Linux packages based on Qt 5.7?
Qt5.8 is supposed to be released some time in January and if it is breaking the plasmawayland session, isn't that a quite serious problem?
P
Offline
Hi Arojas,
after recompiling wayland (libwayland-client) i get a crash displayed. kcrash now shows some information. it seems i am affected by this bug
This seems to be unrelated to the other issue, the backtrace is quite different and it's also reproducible on Qt 5.7
Offline
Just curious...
With a week until the Plasma 5.9 release, can't we just have the Arch Linux packages based on Qt 5.7?Qt5.8 is supposed to be released some time in January and if it is breaking the plasmawayland session, isn't that a quite serious problem?
P
Qt 5.8 is expected to be released tomorrow. We won't hold back the update because of Plasma Wayland, which is not yet considered stable even by upstream.
This doesn't mean that we won't do our best to apply the necessary fixes as soon as they are available.
Last edited by arojas (2017-01-22 10:05:44)
Offline
Qt 5.8 is expected to be released tomorrow. We won't hold back the update because of Plasma Wayland, which is not yet considered stable even by upstream.
This doesn't mean that we won't do our best to apply the necessary fixes as soon as they are available.
Fair enough. plasmawayland seemed OK to me before this problem (using AUR packages). Any regressions vs X11 (no taskbar thumbnails, not retaining minimised window sizes), were to me, not a problem considering the improvements in video smoothness with wayland,
Offline
Well I hope Plasma Wayland and QT5.8 compatibility problems get fixed soon (can't wait to try Wayland again !).
Offline
In good news, plasmashell in wayland seems to be running fine again with Qt 5.8 in testing, as well as wayland programs disconnecting from kwin constantly.
However the window management is a bit "interesting" at the moment, basically kwin seems to treat all wayland clients the same, no decorations, no proper placement and one can drag them around, including panels and the desktop from plasmashell...
The decorations did not show before this update either, so probably just plasmashell does not crash anymore and everything else stayed as is.
Also, krunner seems to be running, but it immediatly closes itself for me. (no crash though)
Offline
For me plasmashell under wayland still crashes but I can launch it from Yakuake which I have set to autostart. Then it is the same as described above. Xwayland applications have decorations and can be managed by Kwin (Chrome, VLC). Wayland applications have no window decorations and can't be minimised even from the task manager.
Offline
The plasma wayland session does not actually enforce the qt platform to be wayland on programs launched in the terminal, only qt programs launched from the application menu etc. start using wayland.
Running plasmashell from the terminal will therefore by default launch it as an X11 program, making things like the task manager not work correctly.
If plasmashell fails to starts on login, it will probably not work when using 'QT_QPA_PLATFORM=wayland plasmashell' either
One thing I might want to point out is that I had plasmashell crashing a few months back when using some custom plasma themes in wayland, if you happen to use any, you might want to try with the breeze one
Offline
I noticed too that Plasma on Wayland in previous vesions (5.7 / 5.8) used to only work with the Breeze theme.
Offline
In good news, plasmashell in wayland seems to be running fine again with Qt 5.8 in testing, as well as wayland programs disconnecting from kwin constantly.
However the window management is a bit "interesting" at the moment, basically kwin seems to treat all wayland clients the same, no decorations, no proper placement and one can drag them around, including panels and the desktop from plasmashell...
The decorations did not show before this update either, so probably just plasmashell does not crash anymore and everything else stayed as is.
Also, krunner seems to be running, but it immediatly closes itself for me. (no crash though)
Have you reported these bugs to the KDE bugtracker? Always useful.
Offline
Have you reported these bugs to the KDE bugtracker? Always useful.
Filed a report describing the issues with kwin:
https://bugs.kde.org/show_bug.cgi?id=375559
Offline
QuartzDragon wrote:Have you reported these bugs to the KDE bugtracker? Always useful.
Filed a report describing the issues with kwin:
https://bugs.kde.org/show_bug.cgi?id=375559
375539 - [Qt 5.8] Plasmashell windows are not marked as Desktop
https://bugs.kde.org/show_bug.cgi?id=375539
[QTBUG-58423] For desktop windows wl_surface is not created
https://bugreports.qt.io/browse/QTBUG-58423
Edit:
Added https://bugs.archlinux.org/task/52728
Last edited by QuartzDragon (2017-01-27 03:49:26)
Offline