Using the group_kdesig-plasma-5-unstable repo.
I'm not sure when this started to happen since I don't normally login/logout very often. Today I tried logging out after a kernel update in order to reboot.
I'm unable to logout from the KDE launcher as I'm getting...
Executable: ksmserver-logout-greeter PID: 16432 Signal: Segmentation fault (11) Time: 10/24/16 17:44:47
I end up having to logout from the command line with "qdbus org.kde.ksmserver /KSMServer logout 0 3 3"
The crash dialog tells me I can't report it since ksmserver-logout-greeter "does not provide a bug reporting address".
Has anyone seen this?
Ed Greshko wrote:
Using the group_kdesig-plasma-5-unstable repo.
I'm not sure when this started to happen since I don't normally login/logout very often. Today I tried logging out after a kernel update in order to reboot.
I'm unable to logout from the KDE launcher as I'm getting...
Executable: ksmserver-logout-greeter PID: 16432 Signal: Segmentation fault (11) Time: 10/24/16 17:44:47
I end up having to logout from the command line with "qdbus org.kde.ksmserver /KSMServer logout 0 3 3"
The crash dialog tells me I can't report it since ksmserver-logout-greeter "does not provide a bug reporting address".
To bad, I take it then you don't get a chance to see the backtrace?
-- Rex
On 10/25/16 01:36, Rex Dieter wrote:
Ed Greshko wrote:
Using the group_kdesig-plasma-5-unstable repo.
I'm not sure when this started to happen since I don't normally login/logout very often. Today I tried logging out after a kernel update in order to reboot.
I'm unable to logout from the KDE launcher as I'm getting...
Executable: ksmserver-logout-greeter PID: 16432 Signal: Segmentation fault (11) Time: 10/24/16 17:44:47
I end up having to logout from the command line with "qdbus org.kde.ksmserver /KSMServer logout 0 3 3"
The crash dialog tells me I can't report it since ksmserver-logout-greeter "does not provide a bug reporting address".
To bad, I take it then you don't get a chance to see the backtrace?
Nope....
On 10/25/16 01:36, Rex Dieter wrote:
Ed Greshko wrote:
Using the group_kdesig-plasma-5-unstable repo.
I'm not sure when this started to happen since I don't normally login/logout very often. Today I tried logging out after a kernel update in order to reboot.
I'm unable to logout from the KDE launcher as I'm getting...
Executable: ksmserver-logout-greeter PID: 16432 Signal: Segmentation fault (11) Time: 10/24/16 17:44:47
I end up having to logout from the command line with "qdbus org.kde.ksmserver /KSMServer logout 0 3 3"
The crash dialog tells me I can't report it since ksmserver-logout-greeter "does not provide a bug reporting address".
To bad, I take it then you don't get a chance to see the backtrace?
It also crashes when run from within konsole.
So, is there a way to collect valuable information in that case in order to file a bugzilla?
Ed Greshko wrote:
Using the group_kdesig-plasma-5-unstable repo.
I'm not sure when this started to happen since I don't normally login/logout very often. Today I tried logging out after a kernel update in order to reboot.
What video driver are you using? (possibly nvidia, like other users have reported recently)?
-- Rex
On 10/25/16 09:22, Rex Dieter wrote:
Ed Greshko wrote:
Using the group_kdesig-plasma-5-unstable repo.
I'm not sure when this started to happen since I don't normally login/logout very often. Today I tried logging out after a kernel update in order to reboot.
What video driver are you using? (possibly nvidia, like other users have reported recently)?
Yes, nVidia.
Ed Greshko wrote:
On 10/25/16 09:22, Rex Dieter wrote:
Ed Greshko wrote:
Using the group_kdesig-plasma-5-unstable repo.
I'm not sure when this started to happen since I don't normally login/logout very often. Today I tried logging out after a kernel update in order to reboot.
What video driver are you using? (possibly nvidia, like other users have reported recently)?
Yes, nVidia.
Try downgrading the video driver (assuming you've received a recent update)?
-- Rex
Likely this bug: https://bugzilla.rpmfusion.org/show_bug.cgi?id=4303
On 24.10.2016 11:55, Ed Greshko wrote:
Using the group_kdesig-plasma-5-unstable repo.
I'm not sure when this started to happen since I don't normally login/logout very often. Today I tried logging out after a kernel update in order to reboot.
I'm unable to logout from the KDE launcher as I'm getting...
Executable: ksmserver-logout-greeter PID: 16432 Signal: Segmentation fault (11) Time: 10/24/16 17:44:47
I end up having to logout from the command line with "qdbus org.kde.ksmserver /KSMServer logout 0 3 3"
The crash dialog tells me I can't report it since ksmserver-logout-greeter "does not provide a bug reporting address".
Has anyone seen this?
On 10/25/16 17:02, Lukas Middendorf wrote:
Likely this bug: https://bugzilla.rpmfusion.org/show_bug.cgi?id=4303
Thanks. Yes, that would seem to fit the bill.
On 24.10.2016 11:55, Ed Greshko wrote:
Using the group_kdesig-plasma-5-unstable repo.
I'm not sure when this started to happen since I don't normally login/logout very often. Today I tried logging out after a kernel update in order to reboot.
I'm unable to logout from the KDE launcher as I'm getting...
Executable: ksmserver-logout-greeter PID: 16432 Signal: Segmentation fault (11) Time: 10/24/16 17:44:47
I end up having to logout from the command line with "qdbus org.kde.ksmserver /KSMServer logout 0 3 3"
The crash dialog tells me I can't report it since ksmserver-logout-greeter "does not provide a bug reporting address".
Has anyone seen this?
kde mailing list -- kde@lists.fedoraproject.org To unsubscribe send an email to kde-leave@lists.fedoraproject.org
-
Ed Greshko -
Lukas Middendorf -
Rex Dieter