Announcement

Collapse
No announcement yet.

Adept Manager problems

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

    Adept Manager problems

    I was trying to follow some advice in the forums about fixing hal-storage-fixed mount problems when I was told to open Adept Manager and I couldn't! I checked no other program was using the system (only firefox open) The backtrace said:

    (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)
    (no debugging symbols found)
    [Thread debugging using libthread_db enabled]
    [New Thread -1235478848 (LWP 13579)]
    (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 0xb661c875 in raise () from /lib/tls/i686/cmov/libc.so.6
    #8 0xb661e201 in abort () from /lib/tls/i686/cmov/libc.so.6
    #9 0xb68286e0 in __gnu_cxx::__verbose_terminate_handler ()
    from /usr/lib/libstdc++.so.6
    #10 0xb6825f65 in ?? () from /usr/lib/libstdc++.so.6
    #11 0xb6825fa2 in std::terminate () from /usr/lib/libstdc++.so.6
    #12 0xb68260ca in __cxa_throw () from /usr/lib/libstdc++.so.6
    #13 0x0812b916 in ?? ()
    #14 0x0812be8a in ?? ()
    #15 0x0812bee8 in ?? ()
    #16 0x0812c735 in ?? ()
    #17 0x0812a22d in ?? ()
    #18 0x08114379 in ?? ()
    #19 0x080951ed in ?? ()
    #20 0x0807378d in ?? ()
    #21 0x0807408e in ?? ()
    #22 0xb6e6c893 in QObject::activate_signal () from /usr/lib/libqt-mt.so.3
    #23 0xb71f88ec in QSignal::signal () from /usr/lib/libqt-mt.so.3
    #24 0xb6e8c842 in QSignal::activate () from /usr/lib/libqt-mt.so.3
    #25 0xb6e94258 in QSingleShotTimer::event () from /usr/lib/libqt-mt.so.3
    #26 0xb6e03af0 in QApplication::internalNotify () from /usr/lib/libqt-mt.so.3
    #27 0xb6e0591f in QApplication::notify () from /usr/lib/libqt-mt.so.3
    #28 0xb75c9cd2 in KApplication::notify () from /usr/lib/libkdecore.so.4
    #29 0xb6d96209 in QApplication::sendEvent () from /usr/lib/libqt-mt.so.3
    #30 0xb6df653b in QEventLoop::activateTimers () from /usr/lib/libqt-mt.so.3
    #31 0xb6daad49 in QEventLoop:rocessEvents () from /usr/lib/libqt-mt.so.3
    #32 0xb6e1e1ce in QEventLoop::enterLoop () from /usr/lib/libqt-mt.so.3
    #33 0xb6e1dfde in QEventLoop::exec () from /usr/lib/libqt-mt.so.3
    #34 0xb6e05699 in QApplication::exec () from /usr/lib/libqt-mt.so.3
    #35 0x0806f75e in ?? ()
    #36 0xb6608050 in __libc_start_main () from /lib/tls/i686/cmov/libc.so.6
    #37 0x0806f401 in ?? ()
    Kubuntu 7.10<br />Desperate for KDE4

    #2
    Re: Adept Manager problems

    Close Adept Manager, and open the Konsole. Enter

    Code:
    sudo dpkg --configure -a
    then

    Code:
    sudo apt-get update
    then
    Code:
    sudo apt-get install
    And close the Konsole. Adept should work correctly afterwards.

    Comment


      #3
      Re: Adept Manager problems

      O fiddle I'm having problems with Adept Manager again but this time this won't work because it says that it is locked by another process using it. I closed the konsole window where I was looking at things so how do I unlock it now, or do I do a Win style reboot?

      Thanks

      I'm loosing patience with trying to install my scanner but very grateful for all the kind people advising me and in general I love the software so much that I'll forgive the teething problems.

      Susan
      Kubuntu 7.10<br />Desperate for KDE4

      Comment


        #4
        Re: Adept Manager problems

        Fixed! I did a search for my problem and found help on the Ubuntu forum. Sorry I really should do that first rather than re-asking old questions.

        8)
        Kubuntu 7.10<br />Desperate for KDE4

        Comment


          #5
          Re: Adept Manager problems

          Having trouble in Linux can be both fun and frustrating.....

          The only diff between windblows and linux is that.....when you're stuck in Linux....You can actually do something about it yourself

          Ain't it fun living in a free world, where you can actually do something about your own problemsto solve them, without having to rely on those computerstores who will charge you and drain your livesavings ?
          Acer Aspire 5100<br />Kubuntu Hardy 8.04

          Comment

          Working...
          X