Bug 124197 - Crash after using net:any in settings and application restart and going to settings again
Summary: Crash after using net:any in settings and application restart and going to se...
Status: RESOLVED FIXED
Alias: None
Product: kpilot
Classification: Applications
Component: General (show other bugs)
Version: unspecified
Platform: Gentoo Packages Linux
: NOR crash
Target Milestone: ---
Assignee: groot
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-03-24 18:36 UTC by gmud
Modified: 2007-04-16 17:37 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description gmud 2006-03-24 18:36:21 UTC
Version:           4.6.0 (using KDE KDE 3.5.1)
Installed from:    Gentoo Packages
OS:                Linux

When using net:any as connection-setting kpilot crashes when goging to settings menu again.
Comment 1 Philip Rodrigues 2006-03-25 15:13:39 UTC
Do you get a backtrace? If so, please paste it here. If not, please consider rebuilding KDE with debugging enabled so you can get one
Comment 2 gmud 2006-03-29 23:38:53 UTC
I am sorry, actually it doesn't crash, it just doesn't respond anymore and I have to kill it and restart it.
Comment 3 Tobias Ussing 2006-05-10 14:09:36 UTC
I just got meself a lifedrive. and becuase it is stupid it is easier to do hotsync over ppp with net:any than with /dev/pilot. So doing that i can confirm this bug.

I just got the svn version of kpilot, once i get it compiled i'll try to track this down.

No promises though.
Comment 4 Philip Rodrigues 2007-01-29 22:51:14 UTC
You might be able to get a backtrace by killing kpilot with "kill -SEGV <pid-of-kpilot>"
Comment 5 gmud 2007-01-30 17:55:14 UTC
It just freezes when I want to go to the settings dialog (only when "net:any" is set as connection). I have to manually remove net:any from the config file to be able to go to the settings dialog again (before that I have to kill kpilot). Here is the backtrace when killing it (I don't know if this helps, I'll try again with debug switched on and report back here).

Kpilot application:
Using host libthread_db library "/lib/libthread_db.so.1".
(no debugging symbols found)
[...]
[Thread debugging using libthread_db enabled]
[New Thread -1236273488 (LWP 13423)]
[KCrash handler]
#9  0xb7f0440e in ?? ()
#10 0xbfd409b8 in ?? ()
#11 0x00000008 in ?? ()
#12 0x080ab1d8 in ?? ()
#13 0xb690cff3 in __read_nocancel () from /lib/libpthread.so.0
#14 0xb7284d5e in _kde_IceTransFreeConnInfo ()
   from /usr/kde/3.5/lib/libDCOP.so.4
#15 0xb72851af in _kde_IceTransRead () from /usr/kde/3.5/lib/libDCOP.so.4
#16 0xb727da5c in _kde_IceRead () from /usr/kde/3.5/lib/libDCOP.so.4
#17 0xb727e087 in KDE_IceProcessMessages () from /usr/kde/3.5/lib/libDCOP.so.4
#18 0xb726a1dc in DCOPClient::callInternal ()
   from /usr/kde/3.5/lib/libDCOP.so.4
#19 0xb726a6e1 in DCOPClient::callInternal ()
   from /usr/kde/3.5/lib/libDCOP.so.4
#20 0xb726facc in DCOPClient::call () from /usr/kde/3.5/lib/libDCOP.so.4
#21 0xb726fb38 in DCOPClient::call () from /usr/kde/3.5/lib/libDCOP.so.4
#22 0x080813d4 in QValueList<int>::detachInternal ()
#23 0x0805cd14 in ?? ()
#24 0x081e8070 in ?? ()
#25 0xbfd41120 in ?? ()
#26 0xbfd40e30 in ?? ()
#27 0x011ebb40 in ?? ()
#28 0x080e99b8 in ?? ()
#29 0x00000000 in ?? ()


Daemon:

Using host libthread_db library "/lib/libthread_db.so.1".
(no debugging symbols found)
[...]
[Thread debugging using libthread_db enabled]
[New Thread -1235269968 (LWP 13431)]
[KCrash handler]
#9  0xb7f9440e in ?? ()
#10 0xbfe0a8c8 in ?? ()
#11 0xb7f55140 in ?? () from /usr/lib/libpisock.so.8
#12 0xbfe0a8b0 in ?? ()
#13 0xb6a02201 in accept () from /lib/libpthread.so.0
#14 0xb7f4588f in pi_inet_device () from /usr/lib/libpisock.so.8
#15 0xb7f50190 in pi_accept () from /usr/lib/libpisock.so.8
#16 0xb7f74229 in KPilotDeviceLink::acceptDevice ()
   from /usr/kde/3.5/lib/libkpilot.so.0
#17 0xb7f76aeb in KPilotDeviceLink::qt_invoke ()
   from /usr/kde/3.5/lib/libkpilot.so.0
#18 0xb6e75464 in QObject::activate_signal () from /usr/qt/3/lib/libqt-mt.so.3
#19 0xb6e75a8b in QObject::activate_signal () from /usr/qt/3/lib/libqt-mt.so.3
#20 0xb71d87c0 in QSocketNotifier::activated ()
   from /usr/qt/3/lib/libqt-mt.so.3
#21 0xb6e92360 in QSocketNotifier::event () from /usr/qt/3/lib/libqt-mt.so.3
#22 0xb6e0fb4f in QApplication::internalNotify ()
   from /usr/qt/3/lib/libqt-mt.so.3
#23 0xb6e0fcfc in QApplication::notify () from /usr/qt/3/lib/libqt-mt.so.3
#24 0xb75271b5 in KApplication::notify ()
   from /usr/kde/3.5/lib/libkdecore.so.4
#25 0xb6e02f73 in QEventLoop::activateSocketNotifiers ()
   from /usr/qt/3/lib/libqt-mt.so.3
#26 0xb6dbae82 in QEventLoop::processEvents ()
   from /usr/qt/3/lib/libqt-mt.so.3
#27 0xb6e26511 in QEventLoop::enterLoop () from /usr/qt/3/lib/libqt-mt.so.3
#28 0xb6e26456 in QEventLoop::exec () from /usr/qt/3/lib/libqt-mt.so.3
#29 0xb6e0ecaf in QApplication::exec () from /usr/qt/3/lib/libqt-mt.so.3
#30 0x0805a725 in ?? ()
#31 0xbfe0b1c0 in ?? ()
#32 0x0807d59c in typeinfo name for QGList ()
#33 0x00000001 in ?? ()
#34 0x00000000 in ?? ()
Comment 6 Jason 'vanRijn' Kasper 2007-04-16 17:37:16 UTC
Hi guys.  This should be fixed now.  The not-yet-released version of kpilot from /branches/KDE/3.5/kdepim/kpilot should resolve this problem.  Please test with that version (kpilot 4.9.1) and re-open this if you still have this problem.

Thanks!!  =:)