Bug 158224

Summary:	Adept Installer Database Lock Crash
Product:	[Unmaintained] adept	Reporter:	Thomas Christy <thomchristy>
Component:	general	Assignee:	Peter Rockai <me>
Status:	RESOLVED WORKSFORME
Severity:	crash	CC:	solarmind
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	Ubuntu
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Thomas Christy 2008-02-22 14:40:36 UTC

Version:            (using KDE 4.0.1)
Installed from:    Ubuntu Packages
OS:                Linux

Upon fresh install of KDE Kubuntu, I attempt download and install of all available updates. About half-way thru, the downloader stops, saying some available downloads may cause others to crash, and begins installing what it has downloaded so far. At the end of the install, a prompt appears that "A new KDE Desktop is available, would you like to install?" - At this point, no matter what I do (accept or quit) the Adept Installer will no longer work. An error page appears suggesting that I file a Bug Report.  When I click "backtrack" the following log entries appear: "(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)
[Thread debugging using libthread_db enabled]
[New Thread -1235843392 (LWP 7501)]
(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  0xffffe410 in __kernel_vsyscall ()
#7  0xb76b6875 in raise () from /lib/tls/i686/cmov/libc.so.6
#8  0xb76b8201 in abort () from /lib/tls/i686/cmov/libc.so.6
#9  0xb78c26e0 in __gnu_cxx::__verbose_terminate_handler ()
   from /usr/lib/libstdc++.so.6
#10 0xb78bff65 in ?? () from /usr/lib/libstdc++.so.6
#11 0xb78bffa2 in std::terminate () from /usr/lib/libstdc++.so.6
#12 0xb78c00ca in __cxa_throw () from /usr/lib/libstdc++.so.6
#13 0x0814d9a6 in ?? ()
#14 0x0814df1a in ?? ()
#15 0x0814df78 in ?? ()
#16 0x0814e7c5 in ?? ()
#17 0x0814c2bd in ?? ()
#18 0x08135ef9 in ?? ()
#19 0x0809ad6d in ?? ()
#20 0x0807349f in ?? ()
#21 0x080755d5 in ?? ()
#22 0xb6c76893 in QObject::activate_signal () from /usr/lib/libqt-mt.so.3
#23 0xb70028ec in QSignal::signal () from /usr/lib/libqt-mt.so.3
#24 0xb6c96842 in QSignal::activate () from /usr/lib/libqt-mt.so.3
#25 0xb6c9e258 in QSingleShotTimer::event () from /usr/lib/libqt-mt.so.3
#26 0xb6c0daf0 in QApplication::internalNotify () from /usr/lib/libqt-mt.so.3
#27 0xb6c0f91f in QApplication::notify () from /usr/lib/libqt-mt.so.3
#28 0xb7315cd2 in KApplication::notify () from /usr/lib/libkdecore.so.4
#29 0xb6ba0209 in QApplication::sendEvent () from /usr/lib/libqt-mt.so.3
#30 0xb6c0053b in QEventLoop::activateTimers () from /usr/lib/libqt-mt.so.3
#31 0xb6bb4d49 in QEventLoop::processEvents () from /usr/lib/libqt-mt.so.3
#32 0xb6c281ce in QEventLoop::enterLoop () from /usr/lib/libqt-mt.so.3
#33 0xb6c27fde in QEventLoop::exec () from /usr/lib/libqt-mt.so.3
#34 0xb6c0f699 in QApplication::exec () from /usr/lib/libqt-mt.so.3
#35 0x08070345 in ?? ()
#36 0xb76a2050 in __libc_start_main () from /lib/tls/i686/cmov/libc.so.6
#37 0x08070091 in ?? ()

====================

IS THERE A WAY TO FIX THIS?  I need to use Adept Installer, it seems under "Add or Remove Programs" to obtain the programs I need to use, and to simply keep my machine updated.  

The only way I have found to get out of the situation is to totally reinstall Kubuntu, but that is a hassle, and there is "no guarantee" that this same "new desktop available" prompt will not reappear and screw things up all over again even after I reinstall.

I am all for progress, and would perhaps like to use the new KDE desktop, as long as it doesn't mess up the rest of your fine software.

Meanwhile, I would like to be able to get out of this "dilemma" if you can offer any good work-arounds or fixes ASAP

Thanks for your help; please reply! thomchristy@gmail.com

Comment 1 Thomas Christy 2008-02-22 14:50:25 UTC

The "Short Description" reads: "The application Adept installer (adept_installer) crashed and caused the signal 6 (SIGABRT).

The first prompt - when Adept Installer stops - reads: "Database Locked - Adpept Installer  Another process is using the packaging system database (probably some other Adept application or apt-get or aptitude). Would you like to attempt to resolve this problem? No will enter read-only mode and Cancel to quit and resolve this issue yourself."

=============

Hope this helps! - thomchristy@gmail.com

Comment 2 Thomas Christy 2008-02-24 14:57:40 UTC

respondents supplied information on what to type into type into terminal window to fix the problem.  I came back here to find the thread of what they had responded, so as to apply the same solution to home computer, but - alas - once again - "complexity rules," and that discussion track was not appended to this entry.  Thanks.  I will have to look elsewhere. ~ TC

Comment 3 Kaspars Birnzieks 2008-02-27 23:33:03 UTC

Exactly the same thing for me! Don't know what to do. Strange.