OK.... So I my F22 system is fully updated with the plasma, qt5, and kf5 packages.
My sessions are restarted from a saved session which consists of just a konsole window with 3 tabs. Upon login everything seems fine. I can move the mouse, I can issue commands in any konsole tab.
Then as soon as I launch something, such at Thunderbird, one of two things will occur. Either
A. Kwin will crash
or
B. The screen will semi-freeze. I can move the mouse around but the launched process will not appear and I can no longer type in the konsole. I also cannot bring switch to a VT as it seem the keyboard is not being recognized. I have to ssh in and issue a "killall -9 drkonqi".
After running into A or B, everything seems to work fine until the next time I logout/login. I don't logout very often so it isn't "serious" but it is annoying.
Not certain how to BZ this.
Ed Greshko wrote on 20.11.2015 06:07:07:
OK.... So I my F22 system is fully updated with the plasma, qt5, and kf5 packages.
My sessions are restarted from a saved session which consists of just a konsole window with 3 tabs. Upon login everything seems fine. I can move the mouse, I can issue commands in any konsole tab.
Then as soon as I launch something, such at Thunderbird, one of two things will occur. Either
A. Kwin will crash
or
B. The screen will semi-freeze. I can move the mouse around but the launched process will not appear and I can no longer type in the konsole. I also cannot bring switch to a VT as it seem the keyboard is not being recognized. I have to ssh in and issue a "killall -9 drkonqi".
Not sure what you mean by "my sessions are restarted from a saved session", but you could try and see if your Plasma 5.4.3 is working with a newly created user. If successful, try to hide away the KDE configuration of your existing user to a safe place.
In my case, Plasma 5.4.3 did not like my old KDE configuration (I don't know which part) -- I only got a stable desktop after doing a KDE config clean sweep.
Another idea is to install the kdebugsettings package from updates-testing (I believe), run the kdebugsettings app and remove the "global disable" rule. Then have a look at the errors in ~/.xsession-errors after login.
Cheers - Fredy
On 11/20/15 16:36, Fredy Neeser wrote:
Ed Greshko wrote on 20.11.2015 06:07:07:
OK.... So I my F22 system is fully updated with the plasma, qt5, and kf5 packages.
My sessions are restarted from a saved session which consists of just a konsole window with 3 tabs. Upon login everything seems fine. I can move the mouse, I can issue commands in any konsole tab.
Then as soon as I launch something, such at Thunderbird, one of two things will occur. Either
A. Kwin will crash
or
B. The screen will semi-freeze. I can move the mouse around but the launched process will not appear and I can no longer type in the konsole. I also cannot bring switch to a VT as it seem the keyboard is not being recognized. I have to ssh in and issue a "killall -9 drkonqi".
Not sure what you mean by "my sessions are restarted from a saved session", but you could try and see if your Plasma 5.4.3 is working with a newly created user. If successful, try to hide away the KDE configuration of your existing user to a safe place.
See "System Settings-->Workspace-->Startup and Shutdown-->Desktop Session" and the "On Login" section.
I already blew away all my settings and have started from scratch. See the "Fedora 22 updates for KDE Plasma 5.4.3 and KDE Frameworks 5.16.0" thread.
In my case, Plasma 5.4.3 did not like my old KDE configuration (I don't know which part) -- I only got a stable desktop after doing a KDE config clean sweep.
My current user is pretty much a "new user" after blowing away my configs. If the minimal changes result in this behavior I'm disappointed.
Another idea is to install the kdebugsettings package from updates-testing (I believe), run the kdebugsettings app and remove the "global disable" rule. Then have a look at the errors in ~/.xsession-errors after login.
You mean the custom rule "*.debug=false"?
I guess I can try that. Not sure how valuable the information in that file will be to me. :-)
Ed Greshko wrote on 20.11.2015 06:07:07:
Another idea is to install the kdebugsettings package from updates-testing (I believe), run the kdebugsettings app and remove the "global disable" rule. Then have a look at the errors in ~/.xsession-errors after login.
You mean the custom rule "*.debug=false"?
Yes, as it overrules the debug settings that are set for indididual kde modules.
I guess I can try that. Not sure how valuable the information in that file will be to me. :-)
Good luck :-)
On 11/20/15 18:36, Fredy Neeser wrote:
I guess I can try that. Not sure how valuable the information in that file will be to me. :-)
Good luck :-)
Thanks.
I'm beginning to think it may have some relationship with sddm. I have switched to kdm and have done several login/logout cycles. Aside from a kwin crash I've not had a lockup where I needed to kill drkonqi.
More testing tomorrow as it is "late" in the day for me.
Ed Greshko wrote:
B. The screen will semi-freeze. I can move the mouse around but the launched process will not appear and I can no longer type in the konsole. I also cannot bring switch to a VT as it seem the keyboard is not being recognized. I have to ssh in and issue a "killall -9 drkonqi".
It's currently a known issue that kwin crash + drkonqi launch can yield an unresponsive system.
You could consider uninstalling plasma-workspace-drkonqi in the meantime to avoid that situation.
-- Rex
On 11/20/15 21:31, Rex Dieter wrote:
Ed Greshko wrote:
B. The screen will semi-freeze. I can move the mouse around but the launched process will not appear and I can no longer type in the konsole. I also cannot bring switch to a VT as it seem the keyboard is not being recognized. I have to ssh in and issue a "killall -9 drkonqi".
It's currently a known issue that kwin crash + drkonqi launch can yield an unresponsive system.
You could consider uninstalling plasma-workspace-drkonqi in the meantime to avoid that situation.
OK, thanks for that tip.
I suppose now I'll just have to be content with kf5-kactivities, libkscreen-qt5, and kmix crashing on logout time as well as kwin and plasma-workspace crashing at login. At least, it seems, according to ABRT when trying to report, those may be known problems with existing BZ.
On 2015-11-20 06:31, Rex Dieter wrote:
Ed Greshko wrote:
B. The screen will semi-freeze. I can move the mouse around but the launched process will not appear and I can no longer type in the konsole. I also cannot bring switch to a VT as it seem the keyboard is not being recognized. I have to ssh in and issue a "killall -9 drkonqi".
It's currently a known issue that kwin crash + drkonqi launch can yield an unresponsive system.
You could consider uninstalling plasma-workspace-drkonqi in the meantime to avoid that situation.
-- Rex _______________________________________________ kde mailing list kde@lists.fedoraproject.org http://lists.fedoraproject.org/admin/lists/kde@lists.fedoraproject.org
I wonder if you have upgraded from a previous version and not a clean account.
I only have issues with an old account but not a newer account.
Part of the bug tracing process.
On one account, open Firefox, open a terminal and kill drkonqi. All works great.
On 11/27/15 11:55, Robin Laing wrote:
On 2015-11-20 06:31, Rex Dieter wrote:
Ed Greshko wrote:
B. The screen will semi-freeze. I can move the mouse around but the launched process will not appear and I can no longer type in the konsole. I also cannot bring switch to a VT as it seem the keyboard is not being recognized. I have to ssh in and issue a "killall -9 drkonqi".
It's currently a known issue that kwin crash + drkonqi launch can yield an unresponsive system.
You could consider uninstalling plasma-workspace-drkonqi in the meantime to avoid that situation.
I wonder if you have upgraded from a previous version and not a clean account.
Originally it was an old account. But somewhere along the line in another thread I mentioned I ended up blowing away all my configurations and starting from scratch but still had freezes.
I only have issues with an old account but not a newer account.
Lucky you. :-)
Part of the bug tracing process.
On one account, open Firefox, open a terminal and kill drkonqi. All works great.
I know/knew how to get out of the freeze as I mentioned above. But, that is the annoying part. I don't want to have to do that.
In any event, Rex's suggestion was the ticket to happiness in that respect. The other issue at login don't bother me too much I don't have to take any extra actions.