| Summary: | konqueror bluetooth:/ crashes very second time | ||
|---|---|---|---|
| Product: | [Unmaintained] kde-bluetooth | Reporter: | Achim Bohnet <ach> |
| Component: | kbluetoothd | Assignee: | Unassigned bugs mailing-list <unassigned-bugs> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | crash | ||
| Priority: | NOR | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | unspecified | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
|
Description
Achim Bohnet
2004-04-07 23:12:30 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 ;) 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 |