Hi! 
I just tried a fresh Intrepid install (just for being sure), and I have a logout problem.
Normally, I can logout-restart-shutdown without any problems.
But, in the case I've given at konsole "sudo dolphin" and dealing with grub directory (mainly altering with kate the menu.lst), after saving the changes and closing kate, dolphin and console, I'm unable to logout.
KDE is trying to logout, I can hear the logout sound and after a while, I'm at the front of a black screen with the white cursor (that I can move across the screen).
Sometimes, the screen is white (instead of black), while some other I can also see at the background, kate with the menu.lst loaded.
At this moment, although I can move the cursor, there is nothing to click at.
Ctrl-alt-del and Alt-F combinations are inresponsible and the only solution I could think, is hitting ctrl-alt-backspace, that killed X and presented me the log on screen. There, I can restart or log on again (log on screen, is fully working).
Do you think this is a bug?
If so, do I have to report it, at bugs.kde.org?
I couldn't found, any related reports.
I just tried a fresh Intrepid install (just for being sure), and I have a logout problem.
Normally, I can logout-restart-shutdown without any problems.
But, in the case I've given at konsole "sudo dolphin" and dealing with grub directory (mainly altering with kate the menu.lst), after saving the changes and closing kate, dolphin and console, I'm unable to logout.
KDE is trying to logout, I can hear the logout sound and after a while, I'm at the front of a black screen with the white cursor (that I can move across the screen).
Sometimes, the screen is white (instead of black), while some other I can also see at the background, kate with the menu.lst loaded.
At this moment, although I can move the cursor, there is nothing to click at.
Ctrl-alt-del and Alt-F combinations are inresponsible and the only solution I could think, is hitting ctrl-alt-backspace, that killed X and presented me the log on screen. There, I can restart or log on again (log on screen, is fully working).
Do you think this is a bug?
If so, do I have to report it, at bugs.kde.org?
I couldn't found, any related reports.
Comment