On Sat, December 5, 2009 11:10 am, James D. Freels wrote: > Sorry it took me so long to send you this. Please find the traceback > output attached and inserted below; this time with the debugger packages > also installed. I get this on 3 separate computers running kde_3.5.10 > over karmic. > > [Thread debugging using libthread_db enabled] > [KCrash handler] > #6 KBackgroundManager (this=0x8de3210, desktop=0x0, > kwinModule=0x8dc2580, > __in_chrg=<value optimized out>, __vtt_parm=<value optimized out>) > at /build/buildd/kdebase-kde3-3.5.10/./kdesktop/bgmanager.cc:68 > #7 0x0349db32 in KDesktop::initRoot (this=0xbf9cb298) > at /build/buildd/kdebase-kde3-3.5.10/./kdesktop/desktop.cc:239 > #8 0x0349e1a5 in KDesktop (this=0xbf9cb298, x_root_hack=false, > wait_for_kded=false, __in_chrg=<value optimized out>, > __vtt_parm=<value optimized out>) > at /build/buildd/kdebase-kde3-3.5.10/./kdesktop/desktop.cc:194 > #9 0x0349f40a in kdemain (argc=1, argv=0x8d78098) > at /build/buildd/kdebase-kde3-3.5.10/./kdesktop/main.cc:208 > #10 0x004244d4 in kdeinitmain (argc=1, argv=0x8d78098) at > kdesktop_dummy.cc:3 > #11 0x0804ee24 in launch (argc=<value optimized out>, > _name=<value optimized out>, args=0xbf9cb6d4 "", cwd=0x0, envc=0, > envs=0x8d77d39 "", reset_env=false, tty=0x0, avoid_loops=false, > startup_id_str=0x805130d "0") > at /build/buildd/kdelibs-kde3-3.5.10/./kinit/kinit.cpp:673 > #12 0x0804f915 in handle_launcher_request (sock=9) > at /build/buildd/kdelibs-kde3-3.5.10/./kinit/kinit.cpp:1240 > #13 0x0805001e in handle_requests (waitForPid=<value optimized out>) > at /build/buildd/kdelibs-kde3-3.5.10/./kinit/kinit.cpp:1443 > #14 0x080509c0 in main (argc=5, argv=0xbf9cbc64, envp=0xbf9cbc7c) > at /build/buildd/kdelibs-kde3-3.5.10/./kinit/kinit.cpp:1908 > > > On Wed, 2009-12-02 at 15:52 -0600, Timothy Pearson wrote: > >> On Wed, December 2, 2009 3:00 pm, James D. Freels wrote: >> > I am using kde-3.5 from this PPA on karmic/koala (9.10) for amd64. I >> > upgraded from jaunty (9.04). I also have a i386 laptop and i386 >> desktop >> > with this same error. >> > >> > There were lots of problems with the upgrade, including some in the >> > kde-3.5 area. However, most of my problems have been resolved one way >> > or another. However, I have a nagging problem that I cannot seem to >> > resolve. I have 3 separate machines all with this same problem. >> > >> > when kde3.5 starts up, an error message box comes up with a traceback >> > (attached is an example). The desktop is not configurable, but I can >> > use all my virtual desktops and the panel otherwise. I cannot set a >> > screensaver, background, or any response from the right click on the >> > desktop screen. >> > >> > How can I fix this problem ? I have already removed all the kde4 >> > packages that I can from my system (at least that I am aware of). >> > >> > [Thread debugging using libthread_db enabled] >> > [KCrash handler] >> > #6 0x00db7ccc in KBackgroundManager::KBackgroundManager(QWidget*, >> > KWinModule*) () from /opt/kde3/lib/libkdeinit_kdesktop.so >> > #7 0x00dbeb32 in KDesktop::initRoot() () >> > from /opt/kde3/lib/libkdeinit_kdesktop.so >> > #8 0x00dbf1a5 in KDesktop::KDesktop(bool, bool) () >> > from /opt/kde3/lib/libkdeinit_kdesktop.so >> > #9 0x00dc040a in kdemain () from /opt/kde3/lib/libkdeinit_kdesktop.so >> > #10 0x00ea64d4 in kdeinitmain () from /opt/kde3/lib/kde3/kdesktop.so >> > #11 0x0804ee24 in ?? () >> > #12 0x0804f915 in ?? () >> > #13 0x0805001e in ?? () >> > #14 0x080509c0 in ?? () >> > #15 0x001ddb56 in __libc_start_main (main=0x8050120, argc=5, >> > ubp_av=0xbfbc3f34, init=0x80510b0, fini=0x80510a0, rtld_fini=0xf3bd20 >> > <_dl_fini>, stack_end=0xbfbc3f2c) at libc-start.c:220 >> > #16 0x0804ba51 in ?? () >> > >> > >> > >> > James D. Freels >> > freelsjd@... >> > >> >> Can you install the debugging symbols (kdebase-kde3-dbg and >> kdelibs-kde3-dbg) and post the new backtrace? >> >> Thanks! >> >> Tim >> > > > > James D. Freels > freelsjd@... > http://www.comsol.com/industry/htmlpaper/oakridge_nuclear_safety_related_procedures/ > > > That's OK; I was busy with the KMail bug anyway. I have created a new bug report so that you can track the status of this bug: http://bugs.pearsoncomputing.net/show_bug.cgi?id=137 Tim