Adept Manager crashes around "reading state information" -- possibly related to CreatePkgParser?

Bug #88256 reported by Mark Philpot
82
This bug affects 1 person
Affects Status Importance Assigned to Milestone
adept (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

Binary package hint: adept-manager

Running Fiesty Herd 4 -- After performing latest upgrade which did contain changes to adept, "Adept Manager" crashes every time. Trace below (removed "no debugging symbols found" lines):

Initial guess is a change to debIFTypeStatus::CreatePkgParser () is misbehaving

[KCrash handler]
#6 0xb688e9f6 in ?? () from /lib/tls/i686/cmov/libc.so.6
#7 0xb7fc1f42 in ?? () from /lib/ld-linux.so.2
#8 0xb6890e18 in ?? () from /lib/tls/i686/cmov/libc.so.6
#9 0xb7eedb42 in ?? () from /usr/lib/libapt-pkg-libc6.4-6.so.3.53
#10 0xb7ee5f9c in ?? () from /usr/lib/libapt-pkg-libc6.4-6.so.3.53
#11 0xb7ee256c in ?? () from /usr/lib/libapt-pkg-libc6.4-6.so.3.53
#12 0x00000001 in ?? ()
#13 0xb7fd2ff4 in ?? () from /lib/ld-linux.so.2
#14 0xb7fb7a18 in ?? ()
#15 0xbf8917b8 in ?? ()
#16 0xbf8917d4 in ?? ()
#17 0xb7fc2103 in ?? () from /lib/ld-linux.so.2
#18 0xb68925ee in malloc () from /lib/tls/i686/cmov/libc.so.6
#19 0xb6a541e7 in operator new () from /usr/lib/libstdc++.so.6
#20 0xb7f81d45 in debIFTypeStatus::CreatePkgParser ()
   from /usr/lib/libapt-pkg-libc6.4-6.so.3.53
#21 0xb7f2a2c6 in pkgRecords::pkgRecords ()
   from /usr/lib/libapt-pkg-libc6.4-6.so.3.53
#22 0x08136fce in ?? ()
#23 0x0812d104 in ?? ()
#24 0x08128fec in ?? ()
#25 0x08129ece in ?? ()
#26 0x0807ae7c in ?? ()
#27 0x0807bd64 in ?? ()
#28 0x080768fd in ?? ()
#29 0x0807722e in ?? ()
#30 0xb7085813 in QObject::activate_signal () from /usr/lib/libqt-mt.so.3
#31 0xb741191c in QSignal::signal () from /usr/lib/libqt-mt.so.3
#32 0xb70a57a6 in QSignal::activate () from /usr/lib/libqt-mt.so.3
#33 0xb70ad1bc in QSingleShotTimer::event () from /usr/lib/libqt-mt.so.3
#34 0xb701c9e8 in QApplication::internalNotify () from /usr/lib/libqt-mt.so.3
#35 0xb701e817 in QApplication::notify () from /usr/lib/libqt-mt.so.3
#36 0xb77e1d52 in KApplication::notify () from /usr/lib/libkdecore.so.4
#37 0xb6faf1e9 in QApplication::sendEvent () from /usr/lib/libqt-mt.so.3
#38 0xb700f433 in QEventLoop::activateTimers () from /usr/lib/libqt-mt.so.3
#39 0xb6fc3d25 in QEventLoop::processEvents () from /usr/lib/libqt-mt.so.3
#40 0xb70370be in QEventLoop::enterLoop () from /usr/lib/libqt-mt.so.3
#41 0xb7036ece in QEventLoop::exec () from /usr/lib/libqt-mt.so.3
#42 0xb701e591 in QApplication::exec () from /usr/lib/libqt-mt.so.3
#43 0x08073225 in ?? ()
#44 0xb683eebc in __libc_start_main () from /lib/tls/i686/cmov/libc.so.6
#45 0x08072f51 in ?? ()

ProblemType: Bug
Date: Mon Feb 26 22:07:24 2007
DistroRelease: Ubuntu 7.04
Uname: Linux mphilpot-laptop 2.6.20-8-generic #2 SMP Tue Feb 13 05:18:42 UTC 2007 i686 GNU/Linux

Revision history for this message
Bruno (bruno666-666) wrote :

I confirm this bug.
I had exactly the same problem (same trace in Kcrash handler) after upgrading from adept-2.1.2ubuntu17 to adept-2.1.2ubuntu18

Changed in adept:
status: Unconfirmed → Confirmed
Revision history for this message
Gabriel Ambuehl (gabriel-ambuehl) wrote :
Download full text (3.9 KiB)

I can also confirm this, here's my backtrace.

(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 -1233459504 (LWP 9145)]
(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 0xb685d9f6 in ?? () from /lib/tls/i686/cmov/libc.so.6
#7 0xb7f9bf42 in ?? () from /lib/ld-linux.so.2
#8 0xb685fe18 in ?? () from /lib/tls/i686/cmov/libc.so.6
#9 0xb7ebcb42 in ?? () from /usr/lib/libapt-pkg-libc6.4-6.so.3.53
#10 0xb7eb4f9c in ?? () from /usr/lib/libapt-pkg-libc6.4-6.so.3.53
#11 0xb7eb156c in ?? () from /usr/lib/libapt-pkg-libc6.4-6.so.3.53
#12 0x00000001 in ?? ()
#13 0xb7facff4 in ?? () from /lib/ld-linux.so.2
#14 0xb7f91a18 in ?? ()
#15 0xbf963848 in ?? ()
#16 0xbf963864 in ?? ()
#17 0xb7f9c103 in ?? () from /lib/ld-linux.so.2
#18 0xb68615ee in malloc () from /lib/tls/i686/cmov/libc.so.6
#19 0xb6a231e7 in operator new () from /usr/lib/libstdc++.so.6
#20 0xb7f50d45 in debIFTypeStatus::CreatePkgParser ()
   from /usr/lib/libapt-pkg-libc6.4-6.so.3.53
#21 0xb7ef92c6 in pkgRecords::pkgRecords ()
   from /usr/lib/libapt-pkg-libc6.4-6.so.3.53
#22 0x08136fce in ?? ()
#23 0x0812d104 in ?? ()
#24 0x08128fec in ?? ()
#25 0x08129ece in ?? ()
#26 0x0807ae7c in ?? ()
#27 0x0807bd64 in ?? ()
#28 0x080768fd in ?? ()
#29 0x0807722e in ?? ()
#30 0xb7054813 in QObject::activate_signal () from /usr/lib/libqt-mt.so.3
#31 0xb73e091c in QSignal::signal () from /usr/lib/libqt-mt.so.3
#32 0xb70747a6 in QSignal::activate () from /usr/lib/libqt-mt.so.3
#33 0xb707c1bc in QSingleShotTimer::event () from /usr/lib/...

Read more...

Revision history for this message
Amine (amine-triki) wrote :
Download full text (3.9 KiB)

Having the same Bug during last upgrade
Here is the report :

(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)
[Thread debugging using libthread_db enabled]
[New Thread -1233262288 (LWP 9567)]
(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)
[KCrash handler]
#6 0xb796a9f6 in ?? () from /lib/tls/i686/cmov/libc.so.6
#7 0xb7fbff42 in ?? () from /lib/ld-linux.so.2
#8 0xb796ce18 in ?? () from /lib/tls/i686/cmov/libc.so.6
#9 0xb7eecb42 in ?? () from /usr/lib/libapt-pkg-libc6.4-6.so.3.53
#10 0xb7ee4f9c in ?? () from /usr/lib/libapt-pkg-libc6.4-6.so.3.53
#11 0xb7ee156c in ?? () from /usr/lib/libapt-pkg-libc6.4-6.so.3.53
#12 0x00000001 in ?? ()
#13 0xb7fd0ff4 in ?? () from /lib/ld-linux.so.2
#14 0xb7fb5a18 in ?? ()
#15 0xbf9e3998 in ?? ()
#16 0xbf9e39b4 in ?? ()
#17 0xb7fc0103 in ?? () from /lib/ld-linux.so.2
#18 0xb796e5ee in malloc () from /lib/tls/i686/cmov/libc.so.6
#19 0xb7b301e7 in operator new () from /usr/lib/libstdc++.so.6
#20 0xb7f80d45 in debIFTypeStatus::CreatePkgParser ()
   from /usr/lib/libapt-pkg-libc6.4-6.so.3.53
#21 0xb7f292c6 in pkgRecords::pkgRecords ()
   from /usr/lib/libapt-pkg-libc6.4-6.so.3.53
#22 0x0815843e in ?? ()
#23 0x0814e7b4 in ?? ()
#24 0x0814a77c in ?? ()
#25 0x0814b65e in ?? ()
#26 0x0808ac0c in ?? ()
#27 0x0808baf4 in ?? ()
#28 0x0807662a in ?? ()
#29 0x080789f5 in ?? ()
#30 0xb6ef6813 in QObject::activate_signal () from /usr/lib/libqt-mt.so.3
#31 0xb728291c in QSignal::signal () from /usr/lib/libqt-mt.so.3
#32 0xb6f167a6 in QSignal::activate () from /usr/lib/libqt-mt.so.3
#33 0xb6f1e1bc...

Read more...

Revision history for this message
Bruno (bruno666-666) wrote :

This seems to be solved now with the latest upgrade to adept 2.1.2ubuntu19 packages.

Changed in adept:
status: Confirmed → Fix Released
Revision history for this message
Gabriel Ambuehl (gabriel-ambuehl) wrote :

I can confirm that it doesnt occur for me anymore after today's update.

Revision history for this message
cowboy777 (kharris) wrote : Re: [Bug 88256] Re: Adept Manager crashes around "reading stateinformation" -- possibly related to CreatePkgParser?

Me too. Thanks for getting this resolved. I was able to get most of what I
needed installed using aptitutude from konsole, but adept is a much easier
interface to work with.

On Thursday 01 March 2007 07:20:29 Gabriel Ambuehl wrote:
> I can confirm that it doesnt occur for me anymore after today's update.

Revision history for this message
jeroenl (jeroenl) wrote :

Works again. Thanks for the fix.

Revision history for this message
bi-abba (l-epa-m-inonda) wrote :

After last package update, bug is re-presenting itself.
Reported also in kde bug: 200840.
Version: Adept: 3.0 Beta 4 (Sheldon) (using KDE 4.2.2)
Compiler: gcc (Ubuntu 4.3.3-5ubuntu4) 4.3.3
OS: Linux
Installed from: Ubuntu Packages

That's what it reports, during "packet analyse", after downloaded "list
updates" from internet: Segmentation fault during packet analyse.

---

Applicazione: Adept (adept), segnale SIGSEGV
[Current thread is 0 (LWP 9833)]

Thread 2 (Thread 0xb44e8b90 (LWP 9841)):
#0 0xb7f0e430 in __kernel_vsyscall ()
#1 0xb72a87b1 in select () from /lib/tls/i686/cmov/libc.so.6
#2 0xb70b3380 in ?? () from /usr/lib/libQtCore.so.4
#3 0xb6fe196e in ?? () from /usr/lib/libQtCore.so.4
#4 0xb65894ff in start_thread () from /lib/tls/i686/cmov/libpthread.so.0
#5 0xb72b049e in clone () from /lib/tls/i686/cmov/libc.so.6

Thread 1 (Thread 0xb5cb2b50 (LWP 9833)):
[KCrash Handler]
#6 0xb72435eb in strlen () from /lib/tls/i686/cmov/libc.so.6
#7 0xb73fab33 in std::string::compare () from /usr/lib/libstdc++.so.6
#8 0xb7e601df in debPackagesIndex::FindInCache () from /usr/lib/libapt-pkg-libc6.9-6.so.4.7
#9 0xb7e27372 in ?? () from /usr/lib/libapt-pkg-libc6.9-6.so.4.7
#10 0xb7e27ae0 in pkgMakeStatusCache () from /usr/lib/libapt-pkg-libc6.9-6.so.4.7
#11 0x080b2f69 in ?? ()
#12 0x080b3309 in ?? ()
#13 0x080be4b0 in ?? ()
#14 0x080c043f in ?? ()
#15 0x08094355 in _start ()

---

ProblemType: Bug
Date: Mon Jul 20 10:07:24 2009
DistroRelease: Ubuntu 9.04
Uname: Linux 2.6.28-14-generic #46-Ubuntu SMP Wed Jul 8 07:21:34 UTC 2009 i686 GNU/Linux

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.