[Bug 1050046] New: osc triggers abrot in kwalletd5 due missing DISPLAY
http://bugzilla.opensuse.org/show_bug.cgi?id=1050046 Bug ID: 1050046 Summary: osc triggers abrot in kwalletd5 due missing DISPLAY Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.2 Hardware: x86-64 OS: openSUSE 42.2 Status: NEW Severity: Normal Priority: P5 - None Component: KDE Workspace (Plasma) Assignee: opensuse-kde-bugs@opensuse.org Reporter: werner@suse.com QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- After using slogin/ssh without forwarding X11 and doing exec dbus-run-session -- unlock-keyring $SHELL to unlock my keyring I see on *every* execution of osc Activating service name='org.kde.kwalletd5' Activated service 'org.kde.kwalletd5' failed: Process org.kde.kwalletd5 received signal 6 also dosing /usr/bin/kwalletd5 QXcbConnection: Could not connect to display Abort (core dumped) first of all: I'm not using KDE but only the gnome keyring together with fvwm2. And indeed I see no reason for kwalletd(5) and even if there is no reason why kwalletd(5) does an abort() ... I guess this is Qt5 which does an stupid abort instead of handling this in a smart way. How to avoid starting kwalletd(5) at all without deinstalling KDE? Also kwalletd(5) should use a loging class on top of Qt5 to avoid qfatal() for not having a DISPLAY around. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1050046
Dr. Werner Fink
http://bugzilla.opensuse.org/show_bug.cgi?id=1050046
Dr. Werner Fink
http://bugzilla.opensuse.org/show_bug.cgi?id=1050046
http://bugzilla.opensuse.org/show_bug.cgi?id=1050046#c1
--- Comment #1 from Dr. Werner Fink
http://bugzilla.opensuse.org/show_bug.cgi?id=1050046
http://bugzilla.opensuse.org/show_bug.cgi?id=1050046#c2
--- Comment #2 from Dr. Werner Fink
http://bugzilla.opensuse.org/show_bug.cgi?id=1050046
http://bugzilla.opensuse.org/show_bug.cgi?id=1050046#c3
--- Comment #3 from Marcus Hüwe
After using slogin/ssh without forwarding X11 and doing
exec dbus-run-session -- unlock-keyring $SHELL
to unlock my keyring I see on *every* execution of osc
Activating service name='org.kde.kwalletd5' Activated service 'org.kde.kwalletd5' failed: Process org.kde.kwalletd5 received signal 6
Hrm yes, osc first tries to use the "python-keyring", which tries to init the kwallet backend (in your case) and fails. In case of a failure, osc tries to use the gnome-keyring, which seems to succeed (in your case). If you do not need the "python-keyring" package, you could remove it and the kwallet messages should be gone. Nevertheless, osc's "keyring selection strategy" could be improved as well...
also dosing
/usr/bin/kwalletd5 QXcbConnection: Could not connect to display Abort (core dumped)
first of all: I'm not using KDE but only the gnome keyring together with fvwm2.
See above - that's due to osc's keyring selection strategy... -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply@novell.com