konqueror error with adept

Bug #91343 reported by Stefan Wunder
4
Affects Status Importance Assigned to Milestone
adept (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

adept manager dont start. Konqueror error!

(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
(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)
[Thread debugging using libthread_db enabled]
[New Thread -1233582384 (LWP 9359)]
(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)
[KCrash handler]
#6 0xb7f71410 in __kernel_vsyscall ()
#7 0xb6803df0 in raise () from /lib/tls/i686/cmov/libc.so.6
#8 0xb6805641 in abort () from /lib/tls/i686/cmov/libc.so.6
#9 0xb683999b in ?? () from /lib/tls/i686/cmov/libc.so.6
#10 0x0000000b in ?? ()
#11 0xbfe2a4fc in ?? ()
#12 0x00000400 in ?? ()
#13 0x00000020 in ?? ()
#14 0xb6918130 in ?? () from /lib/tls/i686/cmov/libc.so.6
#15 0xb6900628 in ?? () from /lib/tls/i686/cmov/libc.so.6
#16 0x00000017 in ?? ()
#17 0xbfe2cbc4 in ?? ()
#18 0x0000000d in ?? ()
#19 0xb6900641 in ?? () from /lib/tls/i686/cmov/libc.so.6
#20 0x00000002 in ?? ()
#21 0xb68fd50a in ?? () from /lib/tls/i686/cmov/libc.so.6
#22 0x0000001c in ?? ()
#23 0xb6900645 in ?? () from /lib/tls/i686/cmov/libc.so.6
#24 0x00000004 in ?? ()
#25 0xbfe2aa5f in ?? ()
#26 0x00000008 in ?? ()
#27 0xb690064b in ?? () from /lib/tls/i686/cmov/libc.so.6
#28 0x00000005 in ?? ()
#29 0xb68418c1 in ?? () from /lib/tls/i686/cmov/libc.so.6
#30 0xb69e0a0b in std::string::_Rep::_S_create () from /usr/lib/libstdc++.so.6
#31 0xb683fb9b in ?? () from /lib/tls/i686/cmov/libc.so.6
#32 0x00000002 in ?? ()
#33 0xb6900628 in ?? () from /lib/tls/i686/cmov/libc.so.6
#34 0xbfe2cbc4 in ?? ()
#35 0xb68fd50a in ?? () from /lib/tls/i686/cmov/libc.so.6
#36 0xbfe2aa5f in ?? ()
#37 0xb68fd50a in ?? () from /lib/tls/i686/cmov/libc.so.6
#38 0xbfe2aa5f in ?? ()
#39 0xb68fd50a in ?? () from /lib/tls/i686/cmov/libc.so.6
#40 0xb6918120 in ?? () from /lib/tls/i686/cmov/libc.so.6
#41 0x00000011 in ?? ()
#42 0xb6918128 in ?? () from /lib/tls/i686/cmov/libc.so.6
#43 0xb6918144 in ?? () from /lib/tls/i686/cmov/libc.so.6
#44 0x0842e8a0 in ?? ()
#45 0xb6918150 in ?? () from /lib/tls/i686/cmov/libc.so.6
#46 0x00000050 in ?? ()
#47 0x00000000 in ?? ()

ProblemType: Bug
Date: Sun Mar 11 11:20:24 2007
DistroRelease: Ubuntu 7.04
Uname: Linux stefan-laptop 2.6.20-8-generic #2 SMP Tue Feb 13 05:18:42 UTC 2007 i686 GNU/Linux

Revision history for this message
Rich Johnson (nixternal) wrote :

I cannot confirm this. Adept opens fine here. Is there anything I should do in order to cause this crash?

Changed in adept:
status: Unconfirmed → Needs Info
Revision history for this message
Richard Birnie (rbirnie-deactivatedaccount) wrote :

Stefan,

Just following up on this bug. Are you still having problems with adept? What steps should we take to reproduce the crash. Actually it's a little confusing, the title of this bug specifies a Konqueror error with adept but the report doesn't mention Konqueror anywhere. Could you explain in a bit more detail what happened.

thanks
Richard

Changed in adept:
assignee: nobody → rbirnie
Revision history for this message
Richard Birnie (rbirnie-deactivatedaccount) wrote :

Closing this bug due to incomplete information and inability to reproduce. If the extra information can be supplied the bug can be reopened

Changed in adept:
assignee: rbirnie → nobody
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.