Announcement

Collapse
No announcement yet.

Adept Manager/Updater crash

Collapse
This topic is closed.
X
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    Adept Manager/Updater crash

    On a fresh install of Hardy Heron, I opened the updater, clicked to see info on one item then when I hit the X on the top right to close it, adept crashed.

    Rebooted the system and now I'm getting the KDE crash handler window when I load up and whenever I try and load Adept.

    Any advice for getting it back? I'm fresh to Linux so newbie friendly explanations are greatly appreciated

    The short description reads:

    "The application Adept Manager (adept_manager) crashed and caused the signal 11 (SIGSEGV).

    Here's the Backtrade stuff:

    (no debugging symbols found)
    Using host libthread_db library "/lib/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)
    (no debugging symbols found)
    (no debugging symbols found)
    (no debugging symbols found)
    (no debugging symbols found)
    [Thread debugging using libthread_db enabled]
    [New Thread 0x7facf25ed6f0 (LWP 6261)]
    (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]
    #5 0x00007facf1d54aa0 in debPackagesIndex::FindInCache ()
    from /usr/lib/libapt-pkg-libc6.7-6.so.4.6
    #6 0x00007facf1d1c054 in ?? () from /usr/lib/libapt-pkg-libc6.7-6.so.4.6
    #7 0x00007facf1d1c732 in pkgMakeStatusCache ()
    from /usr/lib/libapt-pkg-libc6.7-6.so.4.6
    #8 0x00000000004b607a in ?? ()
    #9 0x00000000004b6b58 in ?? ()
    #10 0x000000000043d89e in ?? ()
    #11 0x0000000000437c93 in ?? ()
    #12 0x0000000000438794 in ?? ()
    #13 0x00007facef3e1ff8 in QObject::activate_signal ()
    from /usr/lib/libqt-mt.so.3
    #14 0x00007facef759c99 in QSignal::signal () from /usr/lib/libqt-mt.so.3
    #15 0x00007facef4001cb in QSignal::activate () from /usr/lib/libqt-mt.so.3
    #16 0x00007facef407a0c in QSingleShotTimer::event ()
    from /usr/lib/libqt-mt.so.3
    #17 0x00007facef37a33a in QApplication::internalNotify ()
    from /usr/lib/libqt-mt.so.3
    #18 0x00007facef37c093 in QApplication::notify () from /usr/lib/libqt-mt.so.3
    #19 0x00007facf069747d in KApplication::notify ()
    from /usr/lib/libkdecore.so.4
    #20 0x00007facef30b1fa in QApplication::sendEvent ()
    from /usr/lib/libqt-mt.so.3
    #21 0x00007facef36dabc in QEventLoop::activateTimers ()
    from /usr/lib/libqt-mt.so.3
    #22 0x00007facef3200f3 in QEventLoop:rocessEvents ()
    from /usr/lib/libqt-mt.so.3
    #23 0x00007facef3945c3 in QEventLoop::enterLoop () from /usr/lib/libqt-mt.so.3
    #24 0x00007facef3942af in QEventLoop::exec () from /usr/lib/libqt-mt.so.3
    #25 0x00007facef37be00 in QApplication::exec () from /usr/lib/libqt-mt.so.3
    #26 0x0000000000433f96 in ?? ()
    #27 0x00007faceb3831c4 in __libc_start_main () from /lib/libc.so.6
    #28 0x0000000000433c89 in ?? ()
    #29 0x00007ffffa610c98 in ?? ()
    #30 0x0000000000000000 in ?? ()

    #2
    Re: Adept Manager/Updater crash

    Usually the lines toward the end of the backtrace, and immediately preceding "error" or "? ? ?" are the best clues:

    Code:
    #23 0x00007facef3945c3 in QEventLoop::enterLoop () from /usr/lib/libqt-mt.so.3
    #24 0x00007facef3942af in QEventLoop::exec () from /usr/lib/libqt-mt.so.3
    #25 0x00007facef37be00 in QApplication::exec () from /usr/lib/libqt-mt.so.3
    I searched Launchpad here: https://bugs.launchpad.net/ubuntu/hardy/

    for "libqt-mt-so.3" and did not find any reported bugs. So I ran a Google search, and (of course) found a Launchpad report!

    https://answers.launchpad.net/ubuntu/+question/4006

    But not an answer. :P

    Here's kind of a generic thing to do when things related to Adept or package installation seem to be going wrong. Open the Konsole and enter the following series of commands, while watching for any error messages;

    Code:
    sudo dpkg --configure -a
    Code:
    sudo apt-get update
    Code:
    sudo apt-get upgrade
    Code:
    sudo apt-get install
    Then try Adept Manager again and see what you get. Quite a few Kubuntu users report that the have fewer problems by installing and using Synaptic for the GUI interface to package management.

    Comment


      #3
      Re: Adept Manager/Updater crash

      Oki, I tried using Synaptic yesterday and reinstalled all the adept "bits" which seemed to help it back to life a bit. I've run the commands you suggested which all went fine with no errors. So far, *touch wood* it's been well enough behaved. Thank you

      I've started to get braver using terminal and Synaptic now I've got a wee clue what I'm doing. Synaptic gave me way too many more options than I could understand at first :P

      Wenchy

      Comment


        #4
        Re: Adept Manager/Updater crash

        My problem was not quite the same as wenchkin's but it was close; I had requested an upgrade on the 183 packages shown in the little updates available triangle. Adept started off fine and downloaded all of them, but then crashed after only installing 14 with that little notice that says something to the effect of "we had to stop because otherwise something might break."

        I followed the steps in dibl's post and everything except one update is now installed. I'm going to go check, but I'm guessing that this might be the one update that caused the trouble.

        Thanks a lot, dibl.

        Comment


          #5
          Re: Adept Manager/Updater crash

          I am having some problems with adept as well and thought I might jump on this post.

          When I try to
          Code:
          sudo dpkg --configure -a
          I get this error message:
          drizzt@ubuntu:~$ sudo dpkg --configure -a
          Setting up initramfs-tools (0.85eubuntu36) ...
          update-initramfs: deferring update (trigger activated)

          Processing triggers for initramfs-tools ...
          update-initramfs: Generating /boot/initrd.img-2.6.24-17-generic

          gzip: stdout: No space left on device
          update-initramfs: failed for /boot/initrd.img-2.6.24-17-generic
          dpkg: subprocess post-installation script returned error exit status 1
          Any Ideas??

          Comment


            #6
            Re: Adept Manager/Updater crash

            Open a console and type:
            Code:
            df -hTxtmpfs
            This will report the amount of space available/used for each partition. Look at what is reported for your root ( / ) partition as well as your /home (if you have a separate partition for /home). If either are reporting Use% at/near 100% then you need to do some house cleaning and remove files that are no longer needed.
            Windows no longer obstructs my view.
            Using Kubuntu Linux since March 23, 2007.
            "It is a capital mistake to theorize before one has data." - Sherlock Holmes

            Comment


              #7
              Re: Adept Manager/Updater crash

              I seem to have more than enough space. Here is the output

              Code:
              drizzt@ubuntu:~$ df -hTxtmpfs /root
              Filesystem  Type  Size Used Avail Use% Mounted on
              /dev/sda5   ext3   35G 4.8G  28G 15% /
              drizzt@ubuntu:~$ df -hTxtmpfs /home
              Filesystem  Type  Size Used Avail Use% Mounted on
              /dev/sda6   ext3   14G 4.0G 9.1G 31% /home

              Comment


                #8
                Re: Adept Manager/Updater crash

                Any ideas? If possible I'd like to avoid re-installing the OS, but right now that is the only thing that I can think of to try to correct the situation.

                Comment


                  #9
                  Re: Adept Manager/Updater crash

                  Originally posted by BostonBrother

                  drizzt@ubuntu:~$ sudo dpkg --configure -a
                  Setting up initramfs-tools (0.85eubuntu36) ...
                  update-initramfs: deferring update (trigger activated)

                  Processing triggers for initramfs-tools ...
                  update-initramfs: Generating /boot/initrd.img-2.6.24-17-generic

                  gzip: stdout: No space left on device
                  update-initramfs: failed for /boot/initrd.img-2.6.24-17-generic
                  dpkg: subprocess post-installation script returned error exit status 1
                  Any Ideas??
                  I'm a little mystified by all of that output. Here's what happens on my rig:

                  Code:
                  dibl@cville:~$ sudo dpkg --configure -a
                  dibl@cville:~$
                  Yep, you're seeing it right -- nothing at all. So I Googled "update-initramfs failed". Hmmmmm

                  http://www.mail-archive.com/debian-k.../msg32310.html

                  https://bugs.launchpad.net/ubuntu/+s...ols/+bug/45225

                  http://ubuntuforums.org/showthread.php?t=534758

                  That last one suggests you can get back to a healthy system by booting an older kernel (hopefully you have one) and updating/upgrading back to where you are. It appears you either deleted your current kernel's initramfs, or it got corrupted somehow.

                  Comment


                    #10
                    Re: Adept Manager/Updater crash

                    Thank you for your help, I really appreciate it.

                    Comment

                    Working...
                    X