Summary: | Kde freezes when loading up a session with a shaded window | ||
---|---|---|---|
Product: | [Unmaintained] arts | Reporter: | David Hubner <hubn3rd> |
Component: | knotify | Assignee: | Multimedia Developers <kde-multimedia> |
Status: | RESOLVED DUPLICATE | ||
Severity: | normal | CC: | l.lunak |
Priority: | NOR | ||
Version: | 0.1 | ||
Target Milestone: | --- | ||
Platform: | Compiled Sources | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: | |||
Attachments: | xsessions log |
Description
David Hubner
2005-04-23 01:26:48 UTC
It works just fine here. Is the problem specific to some application or can you reproduce it with any of them? Can you reproduce the problem with a fresh KDE account? Can you attach to the frozen kwin and provide the backtrace? It seems to be linked to this problem.. http://bugs.kde.org/show_bug.cgi?id=96602 Any window that has problem with size when shaded. The application was X-Chat. I shall attach and backtrace when i get home... Waiting for the requested information. Created attachment 11369 [details]
xsessions log
Sorry forgot about this. It does not crash KDE but freezes X. It only happens when Xchat is set to shaded in the session. I have attached the Xsessions-errors log. Need more info? I was wrong it does not look like kwin.. i have attached to it and it does not freeze on its own. Looks like ksmserver. That log file doesn't seem to contain any useful information. Backtrace from the frozen application would be useful. Sorry work has been killing me :) Backtraces follow.... Xchat: #0 0x40596932 in select () at regex_internal.h:758 #1 0x406c0428 in __JCR_LIST__ () from /usr/X11R6/lib/libX11.so.6 #2 0x080bc1e0 in ?? () #3 0x00000000 in ?? () #4 0x4062aa02 in _XWaitForReadable () from /usr/X11R6/lib/libX11.so.6 #5 0x4062b921 in _XRead () from /usr/X11R6/lib/libX11.so.6 #6 0x4062c4a3 in _XReply () from /usr/X11R6/lib/libX11.so.6 #7 0x40613083 in XGetAtomName () from /usr/X11R6/lib/libX11.so.6 #8 0x4032f3f1 in IA__gdk_x11_xatom_to_atom_for_display (display=0x0, xatom=134988256) at gdkproperty-x11.c:306 #9 0x4032334a in gdk_event_translate (display=0x80c0c28, event=0x8100a78, xevent=0xbffffa20, return_exposes=0) at gdkevents-x11.c:1834 #10 0x4032399d in _gdk_events_queue (display=0x80c0c28) at gdkevents-x11.c:2154 #11 0x40323b31 in gdk_event_dispatch (source=0xfffffdfe, callback=0, user_data=0x0) at gdkevents-x11.c:2214 #12 0x40465de2 in g_main_dispatch (context=0x80e67b0) at gmain.c:1947 #13 0x40466e48 in IA__g_main_context_dispatch (context=0x80e67b0) at gmain.c:2497 #14 0x40467180 in g_main_context_iterate (context=0x80e67b0, block=1, dispatch=1, self=0x80e7a98) at gmain.c:2578 #15 0x40467723 in IA__g_main_loop_run (loop=0x80fb2d0) at gmain.c:2782 #16 0x4012ba43 in IA__gtk_main () at gtkmain.c:963 #17 0x080580eb in fe_main () at fe-gtk.c:269 #18 0x08093569 in main (argc=-514, argv=0xfffffdfe) at xchat.c:1114 kwin: #0 0xb6ad8e38 in read () from /lib/libpthread.so.0 #1 0xb76b297c in __JCR_LIST__ () from /usr/lib/./libDCOP.so.4 #2 0xb76ad600 in _kde_IceTransSocketRead () from /usr/lib/./libDCOP.so.4 #3 0xb76ae26f in _kde_IceTransRead () from /usr/lib/./libDCOP.so.4 #4 0xb76a5cae in _kde_IceRead () from /usr/lib/./libDCOP.so.4 #5 0xb76a62c7 in KDE_IceProcessMessages () from /usr/lib/./libDCOP.so.4 #6 0xb769d644 in DCOPClient::callInternal () from /usr/lib/./libDCOP.so.4 #7 0xb769d08c in DCOPClient::callInternal () from /usr/lib/./libDCOP.so.4 #8 0xb769cb4c in DCOPClient::call () from /usr/lib/./libDCOP.so.4 #9 0xb769c99a in DCOPClient::call () from /usr/lib/./libDCOP.so.4 #10 0xb776f226 in startServiceInternal () from /usr/lib/./libkdecore.so.4 #11 0xb776fd10 in KApplication::startServiceByDesktopName () from /usr/lib/./libkdecore.so.4 #12 0xb7852f20 in KNotifyClient::startDaemon () from /usr/lib/./libkdecore.so.4 #13 0xb7852383 in sendNotifyEvent () from /usr/lib/./libkdecore.so.4 #14 0xb78527dd in KNotifyClient::event () from /usr/lib/./libkdecore.so.4 #15 0xb5f7dbfd in KWinInternal::Notify::raise () from /usr//lib/libkdeinit_kwin.so #16 0xb5f55116 in KWinInternal::Client::setShade () from /usr//lib/libkdeinit_kwin.so #17 0xb5f7bf9c in KWinInternal::Client::manage () from /usr//lib/libkdeinit_kwin.so #18 0xb5f464b9 in KWinInternal::Workspace::createClient () from /usr//lib/libkdeinit_kwin.so #19 0xb5f6f013 in KWinInternal::Workspace::workspaceEvent () from /usr//lib/libkdeinit_kwin.so #20 0xb5f647be in KWinInternal::Application::x11EventFilter () from /usr//lib/libkdeinit_kwin.so #21 0xb6f54c08 in qt_x11EventFilter () from /usr/qt/lib/libqt-mt.so.3 #22 0xb6f5f72b in QApplication::x11ProcessEvent () from /usr/qt/lib/libqt-mt.so.3 #23 0xb6f78667 in QEventLoop::processEvents () from /usr/qt/lib/libqt-mt.so.3 #24 0xb6fed348 in QEventLoop::enterLoop () from /usr/qt/lib/libqt-mt.so.3 #25 0xb6fed1f8 in QEventLoop::exec () from /usr/qt/lib/libqt-mt.so.3 #26 0xb6fd86a1 in QApplication::exec () from /usr/qt/lib/libqt-mt.so.3 #27 0xb5f64c2c in kdemain () from /usr//lib/libkdeinit_kwin.so #28 0xb5fac906 in kdeinitmain () from /usr/lib/kde3/kwin.so #29 0x0804cdd2 in launch () #30 0x0804e471 in handle_launcher_request () #31 0x0804e9bd in handle_requests () #32 0x0804fb12 in main () ksmserver: #0 0xb696e932 in select () at regex_internal.h:758 #1 0xb7610114 in __JCR_LIST__ () from /usr/qt/lib/libqt-mt.so.3 #2 0x00000014 in ?? () #3 0x00000013 in ?? () #4 0xb6f77fb1 in QEventLoop::processEvents () from /usr/qt/lib/libqt-mt.so.3 #5 0xb6fed348 in QEventLoop::enterLoop () from /usr/qt/lib/libqt-mt.so.3 #6 0xb6fed1f8 in QEventLoop::exec () from /usr/qt/lib/libqt-mt.so.3 #7 0xb6fd86a1 in QApplication::exec () from /usr/qt/lib/libqt-mt.so.3 #8 0xb5f91c5a in kdemain () from /usr//lib/libkdeinit_ksmserver.so #9 0xb5fac8f6 in kdeinitmain () from /usr/lib/kde3/ksmserver.so #10 0x0804cdd2 in launch () #11 0x0804e471 in handle_launcher_request () #12 0x0804ea9a in handle_requests () #13 0x0804fb12 in main () When i do a PS -A.. kde has started two Xchat instances and one is <defunct> Can you reproducibly get the kwin backtrace with "KNotifyClient::startDaemon ()"? If yes, the problem might be with KNotify, or perhaps your sound system. Do you use arts (and start the soundserver)? Can you see knotify in the process list? Can you provide a backtrace from knotify? Yep.. everytime i reproduce it i get KNotifyClient::startDaemon () I use arts, i tried to turn off the soundsystem but i could still reproduce the bug. There is no knotify process running. PS -A: PID TTY TIME CMD 1 ? 00:00:10 init 2 ? 00:00:00 ksoftirqd/0 3 ? 00:00:00 events/0 4 ? 00:00:00 khelper 5 ? 00:00:00 kthread 6 ? 00:00:00 kblockd/0 7 ? 00:00:00 khubd 9 ? 00:00:00 pdflush 10 ? 00:00:02 pdflush 12 ? 00:00:00 aio/0 8 ? 00:00:00 kapmd 11 ? 00:00:03 kswapd0 15 ? 00:00:00 kseriod 16 ? 00:00:00 scsi_eh_0 19 ? 00:00:00 reiserfs/0 102 ? 00:00:00 syslogd 105 ? 00:00:00 klogd 125 ? 00:00:00 mount.smbfs 127 ? 00:00:00 smbiod 130 ? 00:00:00 mount.smbfs 134 ? 00:00:00 mount.smbfs 151 ? 00:00:00 qmail-send 160 ? 00:00:00 splogger 161 ? 00:00:00 qmail-lspawn 162 ? 00:00:00 qmail-rspawn 163 ? 00:00:00 qmail-clean 164 ? 00:00:00 cupsd 183 ? 00:00:00 kdm 185 tty1 00:00:00 bash 186 tty2 00:00:00 agetty 187 tty3 00:00:00 agetty 188 tty4 00:00:00 agetty 189 tty5 00:00:00 agetty 190 tty6 00:00:00 agetty 1086 ? 00:00:02 X 1089 ? 00:00:00 kdm 1102 ? 00:00:00 startkde 1127 ? 00:00:00 ksplash 1129 ? 00:00:00 kdeinit 1132 ? 00:00:00 dcopserver 1134 ? 00:00:00 klauncher 1137 ? 00:00:00 kded 1146 ? 00:00:00 kaccess 1147 ? 00:00:00 kded 1148 ? 00:00:00 kded 1149 ? 00:00:00 kded 1150 ? 00:00:00 kwrapper 1152 ? 00:00:00 ksmserver 1153 ? 00:00:00 kwin 1155 ? 00:00:00 kdesktop 1157 ? 00:00:00 kicker 1159 ? 00:00:00 gkrellm 1162 ? 00:00:00 gaim 1163 ? 00:00:00 gkrellm 1165 ? 00:00:00 gaim 1166 ? 00:00:00 gaim 1168 ? 00:00:00 kwalletmanager 1170 ? 00:00:00 kmix 1171 ? 00:00:00 kio_file 1172 ? 00:00:00 kmix 1173 ? 00:00:00 amarokapp 1174 ? 00:00:00 kio_media 1175 ? 00:00:00 kio_file 1176 ? 00:00:00 Eterm 1177 ? 00:00:00 xchat 1178 pts/1 00:00:00 bash 1179 ? 00:00:00 amarokapp 1180 ? 00:00:00 xchat <defunct> 1184 tty1 00:00:00 ps I confirm this bug. I have made some test and it seems that problem is indeed with sound system. When you restore any window maximized/shaded etc. and the maximize/shade action produces any sound the KDE startup hangs on "Restoring session". It is enough to turn of the sound to have good behavior. *** This bug has been marked as a duplicate of 102046 *** |