Bug 79262 - konqueror bluetooth:/ crashes very second time
Summary: konqueror bluetooth:/ crashes very second time
Status: RESOLVED DUPLICATE of bug 68528
Alias: None
Product: kde-bluetooth
Classification: Miscellaneous
Component: kbluetoothd (show other bugs)
Version: unspecified
Platform: unspecified Linux
: NOR crash
Target Milestone: ---
Assignee: Unassigned bugs mailing-list
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-04-07 23:12 UTC by Achim Bohnet
Modified: 2004-07-26 20:52 UTC (History)
0 users

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 Achim Bohnet 2004-04-07 23:12:30 UTC
Version:           3.2.90 (using KDE 3.2.1,  (testing/unstable))
Compiler:          gcc version 3.3.3 (Debian)
OS:          Linux (i686) release 2.6.3-laptop-1

Hi Fred,

yesterday with our 0.0.cvs20040331-1 build 
and my cvs build of today (debian testing + kde
from unstable)  kio_bluetooth daemon still crashes
konqueror very often

to reproduce: start konqueror bluetooth:/ vai kdebluetooth
kicker icon.  Wait until kio_bluetooth:/ stop searching.
Close konqueror window with x in upper right corner.
Konqueror window vanishes.  I can verify with ps that
konqueror bluetooth:/ is still running.

Start another konqueror via kdebluetooth kicker icon
--> crash

(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...[New Thread 1095239072 (LWP 9079)]
(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
0x40fb53ee in __waitpid_nocancel () from /lib/tls/libpthread.so.0
#0  0x40fb53ee in __waitpid_nocancel () from /lib/tls/libpthread.so.0
#1  0x40808b78 in lt_dlfree () from /usr/lib/libkdecore.so.4
#2  <signal handler called>
#3  0x40719621 in KIconLoader::loadIcon(QString const&, KIcon::Group, int, int, QString*, bool) const () from /usr/lib/libkdecore.so.4
#4  0x4071ca89 in KIconFactory::createPixmap(QIconSet const&, QIconSet::Size, QIconSet::Mode, QIconSet::State) () from /usr/lib/libkdecore.so.4
#5  0x40ad2494 in QIconSetPrivate::icon(QIconSet const*, QIconSet::Size, QIconSet::Mode, QIconSet::State) () from /usr/lib/libqt-mt.so.3
#6  0x40ad2e77 in QIconSet::pixmap(QIconSet::Size, QIconSet::Mode, QIconSet::State) const () from /usr/lib/libqt-mt.so.3
#7  0x4052534b in KToolBarButton::drawButton(QPainter*) ()
   from /usr/lib/libkdeui.so.4
#8  0x40b96835 in QButton::paintEvent(QPaintEvent*) ()
   from /usr/lib/libqt-mt.so.3
#9  0x40b3cecb in QWidget::event(QEvent*) () from /usr/lib/libqt-mt.so.3
#10 0x40aac47f in QApplication::internalNotify(QObject*, QEvent*) ()
   from /usr/lib/libqt-mt.so.3
#11 0x40aaba8b in QApplication::notify(QObject*, QEvent*) ()
   from /usr/lib/libqt-mt.so.3
#12 0x406b79ed in KApplication::notify(QObject*, QEvent*) ()
   from /usr/lib/libkdecore.so.4
#13 0x40a467e1 in QETWidget::translatePaintEvent(_XEvent const*) ()
   from /usr/lib/libqt-mt.so.3
#14 0x40a42501 in QApplication::x11ProcessEvent(_XEvent*) ()
   from /usr/lib/libqt-mt.so.3
#15 0x40a57f01 in QEventLoop::processEvents(unsigned) ()
   from /usr/lib/libqt-mt.so.3
#16 0x40abfce8 in QEventLoop::enterLoop() () from /usr/lib/libqt-mt.so.3
#17 0x40abfb98 in QEventLoop::exec() () from /usr/lib/libqt-mt.so.3
#18 0x40aac6d1 in QApplication::exec() () from /usr/lib/libqt-mt.so.3
#19 0x414d8c2c in kdemain () from /usr/lib/libkdeinit_konqueror.so
#20 0x40018866 in kdeinitmain () from /usr/lib/kde3/konqueror.so
#21 0x0804cc16 in strcpy ()
#22 0x0804e0fb in strcpy ()
#23 0x0804e6cd in strcpy ()
#24 0x0804f61d in strcpy ()
#25 0x4119f7b8 in __libc_start_main () from /lib/tls/libc.so.6
#26 0x00000000 in ?? ()

The kio_bluetooth process is still running (fine) but when
I start another konqueror kdebluetooth:/  the old kio_bluetooth
process exists and ps find a new one (strange I expected that
the kio client to be reused).


(Today) looks like that every running konqueror bluetooth:/
instance, with open or closed window, crashes as soon
another one is started via kbluetoothd.

Last night I was able start to several instances togehter
without problem as long as the already started instances
were still searching.  But from memory this behaviour
changes from working to crashing everyday.  Only the
first method described above crashed yesterday and today
(and as far as memory served everytime I tried in the
last weeks).

ii  bluez-hcidump               1.5-2                       Analyses Bluetooth HCI packets
ii  bluez-pan                   1.1rel-3                    Personal area networking for Bluetooth devices
ii  bluez-pin                   0.22-1                      Bluetooth PIN helper with D-BUS support
ii  bluez-sdp                   1.5-2                       BlueZ Bluetooth SDP daemon and tool
ii  bluez-utils                 2.4-6                       Utilities for controlling Bluetooth devices

Achim
Comment 1 Achim Bohnet 2004-04-08 01:08:17 UTC
FWIW I can start several instances of

	for x in 1 2 3 4 5; do konqueror bluetooth:/; sleep 1; done

without problems.  Maybe invokeBrowser does some magic
kio_bluetooth does not like.  Looks like the rest in
kdebluetooth suite uses proc << cmd ... to start
konqueror.  Too late to experiment ...

Achim
P.S. using proc has the advantage that I could hack
in --profile bluetooth (that's why I stumbled over
invokeBrowser ;)
Comment 2 Fred Schättgen 2004-04-08 03:43:00 UTC
On Wednesday 07 April 2004 23:12, Achim Bohnet wrote:
> yesterday with our 0.0.cvs20040331-1 build
> and my cvs build of today (debian testing + kde
>
> >from unstable)  kio_bluetooth daemon still crashes
>
> konqueror very often
>
> to reproduce: start konqueror bluetooth:/ vai kdebluetooth
> kicker icon.  Wait until kio_bluetooth:/ stop searching.
> Close konqueror window with x in upper right corner.
> Konqueror window vanishes.  I can verify with ps that
> konqueror bluetooth:/ is still running.

I can't reproduce that. When I close konqueror, then it's really gone. Only 
the kioslave stays alive for a while. What is konqueror or the kioslave 
waiting for? Can you do an strace -p <pid> and have a look at the debugging 
output of kio_bluetooth?
It's strace that konqueror crashes, since a crash of the kioslave doesn't 
affect konqueror usually.

regards
Fred

Comment 3 Stephan Kulow 2004-07-26 20:52:29 UTC

*** This bug has been marked as a duplicate of 68528 ***