| Summary: | kdesktop crashes when screen size changes | ||
|---|---|---|---|
| Product: | TDE | Reporter: | Julius Schwartzenberg <julius.schwartzenberg> |
| Component: | tdebase | Assignee: | Timothy Pearson <kb9vqf> |
| Status: | RESOLVED FIXED | ||
| Severity: | enhancement | CC: | bugwatch, darrella |
| Priority: | P5 | ||
| Version: | 3.5.10 | ||
| Hardware: | Other | ||
| OS: | Linux | ||
| Compiler Version: | TDE Version String: | ||
| Application Version: | Application Name: | ||
|
Description
Julius Schwartzenberg
2009-11-17 12:47:36 CST
Here is the trace:
[Thread debugging using libthread_db enabled]
[KCrash handler]
#5 0x00007fb0cb7f5109 in KBackgroundRenderer::desktopResized() ()
from /opt/kde3/lib/libkdeinit_kdesktop.so
#6 0x00007fb0cb7ce3a8 in KBackgroundManager::desktopResized() ()
from /opt/kde3/lib/libkdeinit_kdesktop.so
#7 0x00007fb0cb7ce560 in KBackgroundManager::qt_invoke(int, QUObject*) ()
from /opt/kde3/lib/libkdeinit_kdesktop.so
#8 0x00007fb0c953cf20 in QObject::activate_signal(QConnectionList*, QUObject*) () from /usr/lib/libqt-mt.so.3
#9 0x00007fb0c953ec8a in QObject::activate_signal(int, int) ()
from /usr/lib/libqt-mt.so.3
#10 0x00007fb0c947ca9b in QApplication::x11ProcessEvent(_XEvent*) ()
from /usr/lib/libqt-mt.so.3
#11 0x00007fb0c948f7a2 in QEventLoop::processEvents(unsigned int) ()
from /usr/lib/libqt-mt.so.3
#12 0x00007fb0c94f55c1 in QEventLoop::enterLoop() ()
from /usr/lib/libqt-mt.so.3
#13 0x00007fb0c94f5472 in QEventLoop::exec() () from /usr/lib/libqt-mt.so.3
#14 0x00007fb0cb7db5e2 in kdemain () from /opt/kde3/lib/libkdeinit_kdesktop.so
#15 0x00007fb0cac72abd in __libc_start_main (main=<value optimized out>,
argc=<value optimized out>, ubp_av=<value optimized out>,
init=<value optimized out>, fini=<value optimized out>,
rtld_fini=<value optimized out>, stack_end=0x7fff90855ae8)
at libc-start.c:220
#16 0x00000000004005b9 in ?? ()
#17 0x00007fff90855ae8 in ?? ()
#18 0x000000000000001c in ?? ()
#19 0x0000000000000001 in ?? ()
#20 0x00007fff90857b68 in ?? ()
#21 0x0000000000000000 in ?? ()
Thank you for the backtrace. Unfortunately it is not very useful; could you install the kdebase-kde3-dbg package (the debugging symbols) and generate a new backtrace? After you do that the solution will most likely be trivial. Thanks! [Thread debugging using libthread_db enabled]
[KCrash handler]
#5 KBackgroundRenderer::desktopResized (this=0x0)
at /build/buildd/kdebase-kde3-3.5.10/./kcontrol/background/bgrender.cpp:88
#6 0x00007f4bf46253a8 in KBackgroundManager::desktopResized (this=0x11e7d50)
at /build/buildd/kdebase-kde3-3.5.10/./kdesktop/bgmanager.cc:759
#7 0x00007f4bf4625560 in KBackgroundManager::qt_invoke (this=0x11e7d50,
_id=7, _o=0x7fffdfd3ccc0) at ./bgmanager.moc:122
#8 0x00007f4bf2393f20 in QObject::activate_signal (this=0x10dbb40,
clist=<value optimized out>, o=0x7fffdfd3ccc0) at kernel/qobject.cpp:2383
#9 0x00007f4bf2395c8a in QObject::activate_signal (this=0x10dbb40,
signal=<value optimized out>, param=<value optimized out>)
at kernel/qobject.cpp:2452
#10 0x00007f4bf22d3a9b in QApplication::x11ProcessEvent (this=0x7fffdfd3d700,
event=0x7fffdfd3d030) at kernel/qapplication_x11.cpp:3497
#11 0x00007f4bf22e67a2 in QEventLoop::processEvents (this=0x10dbe10,
flags=<value optimized out>) at kernel/qeventloop_x11.cpp:195
#12 0x00007f4bf234c5c1 in QEventLoop::enterLoop (this=0x10dbe10)
at kernel/qeventloop.cpp:201
#13 0x00007f4bf234c472 in QEventLoop::exec (this=0x0)
at kernel/qeventloop.cpp:148
#14 0x00007f4bf46325e2 in kdemain (argc=<value optimized out>,
argv=<value optimized out>)
at /build/buildd/kdebase-kde3-3.5.10/./kdesktop/main.cc:214
#15 0x00007f4bf3ac9abd in __libc_start_main (main=<value optimized out>,
argc=<value optimized out>, ubp_av=<value optimized out>,
init=<value optimized out>, fini=<value optimized out>,
rtld_fini=<value optimized out>, stack_end=0x7fffdfd3d9c8)
at libc-start.c:220
#16 0x00000000004005b9 in _start () at ../sysdeps/x86_64/elf/start.S:113
Current language: auto
The current source language is "auto; currently c".
Thank you--that greatly aided debugging. I believe the problem is now fixed; can you upgrade to the latest version of kdebase-kde3 and verify? It's indeed fixed now! Thanks a lot! |