Re: kwin-x11 lock-ups
Arthur, On Samstag, 20. Februar 2016 20:29:27 CET Arthur Marsh wrote: > After upgrading libc6 to 2.21-9, my lock-ups with kwin-x11 4:5.4.3-1.1 > have gone, perhaps due to the fix of Debian bug #814958 in libc6. > > However, kwin-x11 4:5.5.4-2 locked up when starting iceweasel that > restored multiple windows. > > At least I have a working set-up, but was wondering if kwin_x11 should > have provided any more diagnostic information that could have helped > track down bugs like #814958? did you make sure you have installed all of kwin from experimental that you can get? For me kwin_x11 crashed repeatedly when using GLX + OpenGL 3.1 as compositor until I made sure libkwin4-effect-builtins1 is also at version 5.5.4-1. Also preferable do not enable DRI 3 at the moment in X.org configuration, at least not when using two Plasma sessions and switch between them., Now I have: merkaba:~#1> apt list 2>/dev/null | grep kwin kwin-addons/unstable,now 4:5.4.3-1 amd64 [installiert] kwin-common/experimental,now 4:5.5.4-2 amd64 [installiert] kwin-data/experimental,experimental,now 4:5.5.4-2 all [installiert] kwin-dbg/experimental,now 4:5.5.4-2 amd64 [installiert] kwin-decoration-oxygen/unstable,now 4:5.4.3-1 amd64 [installiert] kwin-dev/unstable 4:5.4.3-1.1 amd64 kwin-style-breeze/experimental,now 4:5.5.4-1 amd64 [installiert] kwin-style-oxygen-transparent/experimental 0~20130220-1+b1 amd64 kwin-wayland/experimental,now 4:5.5.4-2 amd64 [installiert] kwin-wayland-backend-drm/unstable,now 4:5.4.3-1.1 amd64 [Installiert,automatisch] kwin-wayland-backend-fbdev/unstable 4:5.4.3-1.1 amd64 kwin-wayland-backend-virtual/experimental 4:5.5.4-2 amd64 kwin-wayland-backend-wayland/unstable 4:5.4.3-1.1 amd64 kwin-wayland-backend-x11/unstable 4:5.4.3-1.1 amd64 kwin-x11/experimental,now 4:5.5.4-2 amd64 [installiert] libkwin4-effect-builtins1/experimental,now 4:5.5.4-2 amd64 [installiert] libkwineffects6/unstable,now 4:5.4.3-1.1 amd64 [installiert] libkwineffects7/experimental,now 4:5.5.4-2 amd64 [installiert] libkwinglutils6/unstable,now 4:5.4.3-1.1 amd64 [installiert] libkwinglutils7/experimental,now 4:5.5.4-2 amd64 [installiert] libkwinxrenderutils6/unstable,now 4:5.4.3-1.1 amd64 [installiert] libkwinxrenderutils7/experimental,now 4:5.5.4-2 amd64 [installiert] and this appears to work okayish so far. But… … I now use this on top of self-compiled KDE Frameworks from Git master, so I can´t say whether this can work for you. kde-addons is not yet available in experimental. So I now have a somewhat 5.5.4 + parts of KF 5.18 / 5.19 setup. Not all of KF 5.18 / 5.19 is installable yet since some packages depend on Qt 5.6 currently. I think its important to just stuff all the new stuff into unstable so it gets compiled properly with Qt 5.5. Or get Qt 5.6 into unstable. This libkwin4-effect-builtins 5.4.3 I got this backtrace, I read the backtrace and found the library name in it, this is how I found that it was still at 5.4.3 on my system: Application: KWin (kwin_x11), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f5ecd32b940 (LWP 18519))] Thread 5 (Thread 0x7f5ec4ce1700 (LWP 18522)): #0 0x7f5ee4e1d963 in select () at ../sysdeps/unix/syscall-template.S:81 #1 0x7f5ee341293f in qt_safe_select(int, fd_set*, fd_set*, fd_set*, timespec const*) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x7f5ee341443e in QEventDispatcherUNIXPrivate::doSelect(QFlags, timespec*) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #3 0x7f5ee341496e in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f5ee33be2ea in QEventLoop::exec(QFlags) () at /usr/lib/x86_64- linux-gnu/libQt5Core.so.5 #5 0x7f5ee31da8d4 in QThread::exec() () at /usr/lib/x86_64-linux-gnu/ libQt5Core.so.5 #6 0x7f5eddef9105 in () at /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #7 0x7f5ee31df88e in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f5ee4438284 in start_thread (arg=0x7f5ec4ce1700) at pthread_create.c:333 #9 0x7f5ee4e24a4d in clone () at ../sysdeps/unix/sysv/linux/x86_64/ clone.S:109 Thread 4 (Thread 0x7f5ebeffe700 (LWP 18524)): #0 0x7f5ee443d8cf in pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/ unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f5ee236d1c4 in () at /usr/lib/x86_64-linux-gnu/libQt5Script.so.5 #2 0x7f5ee236d209 in () at /usr/lib/x86_64-linux-gnu/libQt5Script.so.5 #3 0x7f5ee4438284 in start_thread (arg=0x7f5ebeffe700) at pthread_create.c:333 #4 0x7f5ee4e24a4d in clone () at ../sysdeps/unix/sysv/linux/x86_64/ clone.S:109 Thread 3 (Thread 0x7f5ebf7ff700 (LWP 18543)): #0 0x7f5ee443dc78 in pthread_cond_timedwait@@GLIBC_2.3.2 () at ../ sysdeps/unix/sysv/linux/x86_64/pthread_cond_timedwait.S:238 #1 0x7f5ee31e0a66 in QWaitCondition::wait(QMutex*, unsigned long) () at / usr/lib/x86_64-linux-gnu/libQt5Core.so
Re: kwin-x11 lock-ups
Reply accidentally sent to sender only instead of to list at first, resending to list: Martin Steigerwald wrote on 25/02/16 21:40: > Arthur, > > On Samstag, 20. Februar 2016 20:29:27 CET Arthur Marsh wrote: >> After upgrading libc6 to 2.21-9, my lock-ups with kwin-x11 4:5.4.3-1.1 >> have gone, perhaps due to the fix of Debian bug #814958 in libc6. >> >> However, kwin-x11 4:5.5.4-2 locked up when starting iceweasel that >> restored multiple windows. >> >> At least I have a working set-up, but was wondering if kwin_x11 should >> have provided any more diagnostic information that could have helped >> track down bugs like #814958? > > did you make sure you have installed all of kwin from experimental that you > can get? > > For me kwin_x11 crashed repeatedly when using GLX + OpenGL 3.1 as compositor > until I made sure libkwin4-effect-builtins1 is also at version 5.5.4-1. > > Also preferable do not enable DRI 3 at the moment in X.org configuration, at > least not when using two Plasma sessions and switch between them., I think that was the clue that I needed - if it were easier to see what versions of packages I had installed that shared a common source package with kwin-x11 and plasma-desktop packages that may have helped me identify and upgrade the related packages. I was using an on-board Radeon 3200HD (RS780) when I first encountered the problems and upgraded to a Radeon HD5450 (CEDAR) part way through. Neither support OpenGL 3.1: OpenGL vendor string: X.Org OpenGL renderer string: Gallium 0.4 on AMD CEDAR (DRM 2.43.0, LLVM 3.7.1) OpenGL core profile version string: 3.3 (Core Profile) Mesa 11.1.2 OpenGL core profile shading language version string: 3.30 OpenGL core profile context flags: (none) OpenGL core profile profile mask: core profile OpenGL core profile extensions: OpenGL version string: 3.0 Mesa 11.1.2 OpenGL shading language version string: 1.30 OpenGL context flags: (none) OpenGL extensions: OpenGL ES profile version string: OpenGL ES 3.0 Mesa 11.1.2 OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.00 OpenGL ES profile extensions: Upgrades just performed: [UPGRADE] kwrited:amd64 4:5.4.3-1 -> 4:5.5.4-1 [UPGRADE] libkf5activitiesexperimentalstats1:amd64 4:5.4.3-1 -> 4:5.5.4-1 [UPGRADE] libkf5sysguard-bin:amd64 4:5.4.3-1 -> 4:5.5.4-1 [UPGRADE] libkf5sysguard-data:amd64 4:5.4.3-1 -> 4:5.5.4-1 [UPGRADE] libkfontinst5:amd64 4:5.4.3-1 -> 4:5.5.4-1 [UPGRADE] libkfontinstui5:amd64 4:5.4.3-1 -> 4:5.5.4-1 [UPGRADE] libksgrd7:amd64 4:5.4.3-1 -> 4:5.5.4-1 [UPGRADE] libksignalplotter7:amd64 4:5.4.3-1 -> 4:5.5.4-1 [UPGRADE] libkwin4-effect-builtins1:amd64 4:5.4.3-1.1 -> 4:5.5.4-2 [UPGRADE] libkworkspace5-5:amd64 4:5.4.3-2 -> 4:5.5.4-1 [UPGRADE] liboxygenstyle5-5:amd64 4:5.4.3-1 -> 4:5.5.4-1 [UPGRADE] liboxygenstyleconfig5-5:amd64 4:5.4.3-1 -> 4:5.5.4-1 [UPGRADE] libpam-kwallet5:amd64 5.4.3-1 -> 5.5.4-1 [UPGRADE] libprocesscore7:amd64 4:5.4.3-1 -> 4:5.5.4-1 [UPGRADE] libprocessui7:amd64 4:5.4.3-1 -> 4:5.5.4-1 [UPGRADE] libtaskmanager5:amd64 4:5.4.3-2 -> 4:5.5.4-1 [UPGRADE] libweather-ion7:amd64 4:5.4.3-2 -> 4:5.5.4-1 [UPGRADE] milou:amd64 4:5.4.3-1 -> 4:5.5.4-1 [UPGRADE] plasma-desktop:amd64 4:5.4.3-1 -> 4:5.5.4-1 [UPGRADE] plasma-desktop-data:amd64 4:5.4.3-1 -> 4:5.5.4-1 [UPGRADE] polkit-kde-agent-1:amd64 4:5.4.3-1 -> 4:5.5.4-1 [UPGRADE] systemsettings:amd64 4:5.4.3-1 -> 4:5.5.4-1 [UPGRADE] systemsettings-dbg:amd64 4:5.4.3-1 -> 4:5.5.4-1 [UPGRADE] plasma-desktop:amd64 4:5.4.3-1 -> 4:5.5.4-1 [UPGRADE] plasma-desktop-data:amd64 4:5.4.3-1 -> 4:5.5.4-1 [UPGRADE] kwrited:amd64 4:5.4.3-1 -> 4:5.5.4-1 [UPGRADE] libkf5activitiesexperimentalstats1:amd64 4:5.4.3-1 -> 4:5.5.4-1 [UPGRADE] libkf5sysguard-bin:amd64 4:5.4.3-1 -> 4:5.5.4-1 [UPGRADE] libkf5sysguard-data:amd64 4:5.4.3-1 -> 4:5.5.4-1 [UPGRADE] libkfontinst5:amd64 4:5.4.3-1 -> 4:5.5.4-1 [UPGRADE] libkfontinstui5:amd64 4:5.4.3-1 -> 4:5.5.4-1 [UPGRADE] libksgrd7:amd64 4:5.4.3-1 -> 4:5.5.4-1 [UPGRADE] libksignalplotter7:amd64 4:5.4.3-1 -> 4:5.5.4-1 [UPGRADE] libkwin4-effect-builtins1:amd64 4:5.4.3-1.1 -> 4:5.5.4-2 [UPGRADE] libkworkspace5-5:amd64 4:5.4.3-2 -> 4:5.5.4-1 [UPGRADE] liboxygenstyle5-5:amd64 4:5.4.3-1 -> 4:5.5.4-1 [UPGRADE] liboxygenstyleconfig5-5:amd64 4:5.4.3-1 -> 4:5.5.4-1 [UPGRADE] libpam-kwallet5:amd64 5.4.3-1 -> 5.5.4-1 [UPGRADE] libprocesscore7:amd64 4:5.4.3-1 -> 4:5.5.4-1 [UPGRADE] libprocessui7:amd64 4:5.4.3-1 -> 4:5.5.4-1 [UPGRADE] libtaskmanager5:amd64 4:5.4.3-2 -> 4:5.5.4-1 [UPGRADE] libweather-ion7:amd64 4:5.4.3-2 -> 4:5.5.4-1 [UPGRADE] milou:amd64 4:5.4.3-1 -> 4:5.5.4-1 [UPGRADE] plasma-desktop:amd64 4:5.4.3-1 -> 4:5.5.4-1 [UPGRADE] plasma-desktop-data:amd64 4:5.4.3-1 -> 4:5.5.4-1 [UPGRADE] polkit-kde-agent-1:amd64 4:5.4.3-1 -> 4:5.5.4-1 [UPGRADE] systemsettings:amd64 4:5.4.3-1 -> 4:5.5.4-1 [UPGRADE] systemsettings-dbg:amd64 4:5.4.3-1 -> 4:5.5.4-1 [UPGRADE] plasma-desktop:amd64 4:5.4.3-1 -> 4:5.5.4-1 [UPGRADE] plasma-desktop-data:amd64 4:5.4.3-1 -> 4:5.5.4-1 I gave this a try with using org.kde.breez
Re: kwin-x11 lock-ups
Arthur Marsh wrote on 25/02/16 23:14: ... it turned out that I had not applied this upgrade: [UPGRADE] kwrited:amd64 4:5.4.3-1 -> 4:5.5.4-1 I gave this a try with using org.kde.breeze again after rebooting, then set the window decoration back to Plastik and rebooted again, and started fine. After upgrading kwrited to 4:5.5.4-1 and logging out and logging back in again and starting iceweasel with Plastik window decoration, I again had a kwin_x11 lock-up again (no usable back-trace). I set the window decoration back to org.kde.breeze, rebooted and restarted iceweasel fine, then set the window decoration back to Plastik, rebooted and restarted iceweasel fine. So a problem still exists but it doesn't happen as often. Arthur.
kwalletmanager5 cannot open a wallet with experimental stuff installed
Hi!
I sometimes manually open a wallet with kwalletmanager5 to look up a password,
yet with the current package mix from sid + experimental, it doesn´t open a
wallet anymore.
1) I go to Wallet Manager in Systray
2) I select a wallet.
3) I click Open
4) Nothing seems to happen
in ~/.xsession-errors I get:
process 7172: arguments to dbus_connection_send_with_reply() were incorrect,
assertion "timeout_milliseconds >= 0 || timeout_milliseconds == -1" failed in
file ../../dbus/dbus-connection.c line 3410.
This is normally a bug in some application using the D-Bus library.
Invalid DBus reply: QDBusError("org.freedesktop.DBus.Error.NoMemory", "Out of
memory")
[…]
process 7172: arguments to dbus_connection_send_with_reply() were incorrect,
assertion "timeout_milliseconds >= 0 || timeout_milliseconds == -1" failed in
file ../../dbus/dbus-connection.c line 3410.
This is normally a bug in some application using the D-Bus library.
Invalid DBus reply: QDBusError("org.freedesktop.DBus.Error.NoMemory", "Out of
memory")
martin@merkaba:~> ps aux | head -1 ; ps aux | grep "[7]172"
USER PID %CPU %MEMVSZ RSS TTY STAT START TIME COMMAND
martin7172 0.1 0.3 489256 59200 ?Sl 14:04 0:01 /usr/bin/
kwalletmanager5
Anyone an idea about this one?
I have this with kwalletmanager5 from unstable and from experimental.
I think it may be due to libkf5wallet5:amd64 + libkwalletbackend5-5:amd64
still at 5.16, but 5.19 are not installable due to Qt 5.6.
I would like to unbreak this.
I can report a bug about this if desired.
Applications using kwallet still seem to work. Just manually open a wallet
seems broke.
Thanks,
--
Martin
Re: kwalletmanager5 cannot open a wallet with experimental stuff installed
On Donnerstag, 25. Februar 2016 14:18:54 CET Martin Steigerwald wrote:
> Hi!
>
> I sometimes manually open a wallet with kwalletmanager5 to look up a
> password, yet with the current package mix from sid + experimental, it
> doesn´t open a wallet anymore.
>
> 1) I go to Wallet Manager in Systray
>
> 2) I select a wallet.
>
> 3) I click Open
>
> 4) Nothing seems to happen
>
>
> in ~/.xsession-errors I get:
>
> process 7172: arguments to dbus_connection_send_with_reply() were incorrect,
> assertion "timeout_milliseconds >= 0 || timeout_milliseconds == -1" failed
> in file ../../dbus/dbus-connection.c line 3410.
> This is normally a bug in some application using the D-Bus library.
> Invalid DBus reply: QDBusError("org.freedesktop.DBus.Error.NoMemory", "Out
> of memory")
> […]
> process 7172: arguments to dbus_connection_send_with_reply() were incorrect,
> assertion "timeout_milliseconds >= 0 || timeout_milliseconds == -1" failed
> in file ../../dbus/dbus-connection.c line 3410.
> This is normally a bug in some application using the D-Bus library.
> Invalid DBus reply: QDBusError("org.freedesktop.DBus.Error.NoMemory", "Out
> of memory")
>
>
> martin@merkaba:~> ps aux | head -1 ; ps aux | grep "[7]172"
> USER PID %CPU %MEMVSZ RSS TTY STAT START TIME COMMAND
> martin7172 0.1 0.3 489256 59200 ?Sl 14:04 0:01 /usr/bin/
> kwalletmanager5
>
>
>
> Anyone an idea about this one?
>
> I have this with kwalletmanager5 from unstable and from experimental.
I solved this by upgrading kde-runtime 15.08 in unstable to 15.12.1 in
experimental.
Come on, stuff all the things into unstable already :)
> I think it may be due to libkf5wallet5:amd64 + libkwalletbackend5-5:amd64
> still at 5.16, but 5.19 are not installable due to Qt 5.6.
Ciao,
--
Martin
Re: kwalletmanager5 cannot open a wallet with experimental stuff installed
On Thursday 25 February 2016 14:29:18 Martin Steigerwald wrote: > I solved this by upgrading kde-runtime 15.08 in unstable to 15.12.1 in > experimental. > > Come on, stuff all the things into unstable already :) How did you 'overcome' https://bugs.debian.org/814526 ? Did you force the installation of plasma-desktop-data? signature.asc Description: This is a digitally signed message part.
Re: kwalletmanager5 cannot open a wallet with experimental stuff installed
On 25 February 2016 at 15:36, Diederik de Haas wrote: > On Thursday 25 February 2016 14:29:18 Martin Steigerwald wrote: > > I solved this by upgrading kde-runtime 15.08 in unstable to 15.12.1 in > > experimental. > > > > Come on, stuff all the things into unstable already :) > > How did you 'overcome' https://bugs.debian.org/814526 ? > Did you force the installation of plasma-desktop-data? You don't have to 'overcome' that bug if you don't have any kde-l10n-* packages installed
Re: kwalletmanager5 cannot open a wallet with experimental stuff installed
On Thursday 25 February 2016 16:00:09 Sami Erjomaa wrote: > > How did you 'overcome' https://bugs.debian.org/814526 ? > > Did you force the installation of plasma-desktop-data? > > You don't have to 'overcome' that bug if you don't have any kde-l10n-* > packages installed Damn, referenced the wrong bug. I meant this one: https://bugs.debian.org/814152 ([libkscreenlocker5] Conflict with plasma-workspace) signature.asc Description: This is a digitally signed message part.
Re: kwalletmanager5 cannot open a wallet with experimental stuff installed
On 25 February 2016 at 16:23, Diederik de Haas wrote: > On Thursday 25 February 2016 16:00:09 Sami Erjomaa wrote: > > > How did you 'overcome' https://bugs.debian.org/814526 ? > > > Did you force the installation of plasma-desktop-data? > > > > You don't have to 'overcome' that bug if you don't have any kde-l10n-* > > packages installed > > Damn, referenced the wrong bug. > I meant this one: https://bugs.debian.org/814152 > ([libkscreenlocker5] Conflict with plasma-workspace) update plasma-workspace to 4:5.5.4-1
