Version: (using KDE 4.2.4) OS: Linux Installed from: Slackware Packages I open the system calendar, select the back arrow to navigate the month of January/2010. The window manager freezes and after a few seconds X is running by itself, no window manager, no response to kde commands like Alt+F2, etc
Unfortunately this report is missing a backtrace, so there is no way to investigate this issue. If you are able to reproduce, please have a look at http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports and attach a backtrace to this report. Thanks
Following the instructions on that document, I made it crash again but did not get the backtrace screen. I am at work(yes, KDE at work!) and time is short, I will do my best to improve the bug report, sorry about that. The issue is repeatable any time on my PC, I thought other users would be able to replicate it.
(In reply to comment #2) > The issue is repeatable any time on my PC, I thought other users would be able > to replicate it. You're aware that 4.2.4 is rather dated? :) Also what's the "system calendar" supposed to be? A plasmoid (on the desktop) or part of kontact (groupware app) or the date picker in systemsettings, or...
OK, this may be a funny way to describe which calendar, but I think it' s the quickest: http://i.imgur.com/jjewW.png If I click that left arrow pointed to it crashes KDE and I'm left with a gray graphical screen which to me seems like the raw X server console.
plasmoid, and it sounds as if entire KDE would go down. can you switch to VT1 (crtl+alt+f1), login and check whether processes like kded4 or the dbus session dameon are still up? ps -Af | grep kded ps -Af | grep dbus # this checks for all apps launched by kdeinit ps -Af | grep kdeinit4
Alright, I'm on a separate PC now. I've just crashed my linux station, the resulting screen is gray with white round spots, not that criss-cross raw X server screen I had suggested before. The windows that were running are still running but the window manager seems to be gone, Alt+f2 is dead, no KDE shortcuts work. Right-click is dead, no feedback. Going to text TTY. TTY1 seems to be stderr only, TTYs 2-5 are dead, TTY 6 is up, dunno if this is a Slackware thing. Kernel is 2.6.29-6-smp, 32 bits though this is a x86_64 cpu. I mailed myself these results: ps -Af | grep kded root 3447 1 0 12:41 ? 00:00:00 kded4 root 3756 3357 0 14:05 tty6 00:00:00 grep kded ps -Af | grep kdeinit4 root 3444 1 0 12:41 ? 00:00:00 kdeinit4: kdeinit4 Running... root 3742 3357 0 14:02 tty6 00:00:00 grep kdeinit4 ps -Af | grep dbus 81 3190 1 0 12:36 ? 00:00:00 /usr/bin/dbus-daemon --system root 3378 1 0 12:36 ? 00:00:00 dbus-launch --autolaunch daa8a409b55f786d8c4ff77a4ab93c4f --binary-syntax --close-stderr root 3379 1 0 12:36 ? 00:00:00 /usr/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session root 3438 1 0 12:41 ? 00:00:00 /usr/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session root 3439 1 0 12:41 ? 00:00:00 dbus-launch --sh-syntax --exit-with-session root 3735 3357 0 14:02 tty6 00:00:00 grep dbus --- header in /var/log/kdm.log (Does not show any error messages that I can see, added for precise versions only...) X.Org X Server 1.6.3 Release Date: 2009-7-31 X Protocol Version 11, Revision 0 Build Operating System: Slackware 13.0 Slackware Linux Project Current Operating System: Linux caravela 2.6.29.6-smp #2 SMP Mon Aug 17 00:52:54 CDT 2009 i686 Build Date: 03 August 2009 06:51:50PM Checked /var/log but could not find additional kwin or kde logs. If there are additional steps to send you a more useful report, please let me know.
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days, the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please set the bug status as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!