Summary: | Kitchensync shows no configuration and kills it self | ||
---|---|---|---|
Product: | [Unmaintained] kitchensync | Reporter: | Rebecca Bock <Rebecca> |
Component: | general | Assignee: | Holger Freyther <zecke> |
Status: | RESOLVED WORKSFORME | ||
Severity: | crash | CC: | Stefan.Borggraefe |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Mandrake RPMs | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Hi, that seems to be a problem with your installation. Please check that $KDEDIRS and $KDEHOME points to the correct directories and no old libraries are lying around. This crash isn't reproducable with current version from CVS HEAD. Ciao, Tobias Could You point out which libraries might be in the way? I have tried both SuSE-Binary kdepim3-sync-3.3.3 and Source (from the SuSE-SRPM). In my case kitchensync reads the adresses from the zaurus, but does not sync them. Adresses are not read. When I chose the menuitem Settings / Configure kitchensync... it crashes. I guess, that old libs might be in the way. Can you give a hint for which libraries I should search? Or might it be a problem raised by SuSE's use of a different threadlibrary? P.S.: the konsole gives the following output kitchensync: KitchenSync::initProfiles() kitchensync: DESKTOP: restore kitchensync: xx: restore kitchensync: DESKTOP: backup kitchensync: xx: backup kitchensync: DESKTOP: viewer kitchensync: xx: viewer kitchensync: DESKTOP: overview kitchensync: xx: overview kitchensync: DESKTOP: debugger kitchensync: xx: debugger kitchensync: DESKTOP: syncerpart kitchensync: xx: syncerpart kitchensync: id: restore kitchensync: id: backup kitchensync: id: viewer kitchensync: id: overview kitchensync: id: restore kitchensync: id: backup kitchensync: id: restore kitchensync: id: backup kitchensync: id: viewer kitchensync: id: overview kitchensync: id: debugger kitchensync: id: syncerpart kitchensync: id: restore kitchensync: id: backup kitchensync: KitchenSync::activateProfile(): Syncing kitchensync: KitchenSync::addPart() OverView-Komponente kitchensync (KitchenSyncApp): Part has GUI (unnamed) kitchensync: KitchenSync::addPart() Konnector-Sicherung kitchensync (KitchenSyncApp): Part has GUI (unnamed) kitchensync: LOG: <b>14:11:52</b>: Ready. kitchensync: KitchenSync::addPart() Synchronizer-Komponente kitchensync (KitchenSyncApp): Part has GUI (unnamed) kitchensync (KitchenSyncApp): Profile changed kitchensync: KitchenSync::initProfiles() done kitchensync: KitchenSync::activateProfile(): Syncing kitchensync: Profile already active kitchensync (KitchenSyncApp): exec now taki@rivendell:/usr/src/packages/SOURCES/kdepim-3.3.0/kitchensync> kitchensync: ERROR: Received DCOP: resource added for unknown resource x4JMVnQIfl kitchensync: ERROR: Received DCOP: resource added for unknown resource x4JMVnQIfl AFTER CRASH: kitchensync: ERROR: Received DCOP: resource added for unknown resource x4JMVnQIfl kitchensync: ERROR: Received DCOP: resource added for unknown resource EJiiUwQuRy kitchensync: ERROR: Received DCOP: resource added for unknown resource EJiiUwQuRy kitchensync: ERROR: Received DCOP: resource added for unknown resource EJiiUwQuRy kitchensync: ERROR: Received DCOP: resource added for unknown resource EJiiUwQuRy KCrash: Application 'kitchensync' crashing... P.P.S.: The backtrace Using host libthread_db library "/lib/tls/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread 1100164672 (LWP 32373)] [KCrash handler] #7 0x403ef4d8 in KRES::Factory::resource () from /opt/kde3/lib/libkresources.so.1 #8 0x403ef818 in KRES::ManagerImpl::readResourceConfig () from /opt/kde3/lib/libkresources.so.1 #9 0x403efb36 in KRES::ManagerImpl::dcopKResourceAdded () from /opt/kde3/lib/libkresources.so.1 #10 0x403e9010 in KRES::ManagerIface::process () from /opt/kde3/lib/libkresources.so.1 #11 0x40c841c0 in DCOPClient::receive () from /opt/kde3/lib/libDCOP.so.4 #12 0x40c88bf3 in DCOPProcessInternal () from /opt/kde3/lib/libDCOP.so.4 #13 0x40c8924e in DCOPClient::processPostedMessagesInternal () from /opt/kde3/lib/libDCOP.so.4 #14 0x40c8a02a in DCOPClient::qt_invoke () from /opt/kde3/lib/libDCOP.so.4 #15 0x41021ecf in QObject::activate_signal () from /usr/lib/qt3/lib/libqt-mt.so.3 #16 0x41021d6f in QObject::activate_signal () from /usr/lib/qt3/lib/libqt-mt.so.3 #17 0x413868bc in QTimer::timeout () from /usr/lib/qt3/lib/libqt-mt.so.3 #18 0x410466ae in QTimer::event () from /usr/lib/qt3/lib/libqt-mt.so.3 #19 0x40fbecab in QApplication::internalNotify () from /usr/lib/qt3/lib/libqt-mt.so.3 #20 0x40fbdfd1 in QApplication::notify () from /usr/lib/qt3/lib/libqt-mt.so.3 #21 0x40bd8aee in KApplication::notify () from /opt/kde3/lib/libkdecore.so.4 #22 0x40f53c22 in QApplication::sendEvent () from /usr/lib/qt3/lib/libqt-mt.so.3 #23 0x40fad1ee in QEventLoop::activateTimers () from /usr/lib/qt3/lib/libqt-mt.so.3 #24 0x40f65edb in QEventLoop::processEvents () from /usr/lib/qt3/lib/libqt-mt.so.3 #25 0x40fd3141 in QEventLoop::enterLoop () from /usr/lib/qt3/lib/libqt-mt.so.3 #26 0x40fd305a in QEventLoop::exec () from /usr/lib/qt3/lib/libqt-mt.so.3 #27 0x40fbee17 in QApplication::exec () from /usr/lib/qt3/lib/libqt-mt.so.3 #28 0x0804c011 in main (argc=1, argv=0xbffff1c4) at main.cpp:61 I see the same backtrace with kitchensync 0.0.8 from http://handhelds.org/~zecke/downloads/kitchensync/kitchensync-kornholioa08.deb on a Debian Sarge system with KDE 3.3 from sid. This happens everytime when I select "Settings|Configure KitchenSync...". |
Version: (using KDE KDE 3.1.4) Installed from: Mandrake RPMs Compiler: gcc3 OS: Linux i did it start after compiling from the console and its shows the following messages: >kio (KMimeType): WARNING: KServiceType::offers : servicetype >KitchenSync/Manipulator not found >kitchensync (KitchenSyncApp): KonnectorProfileManager::load() >kitchensync (KitchenSyncApp): exec now The output on the desktop is red and only the help tab is avaible. I did it start as root.