Announcement

Collapse
No announcement yet.

Discover CRASHED during update

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

    Discover CRASHED during update

    I just installed from disc to get a fresh install. When running discover to update 91 Packages it crashed during the update. It went to the bug reporting utility but apparently its missing some packages since the back trace doesn't have all the information to be useful. Here is what it said...

    Code:
    Application: Discover (plasma-discover), signal: Segmentation fault
    Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
    [Current thread is 1 (Thread 0x7f441b8748c0 (LWP 9567))]
    
    Thread 7 (Thread 0x7f43d67fc700 (LWP 9581)):
    #0  0x00007ffc26ff4b12 in clock_gettime ()
    #1  0x00007f4416e26906 in __GI___clock_gettime (clock_id=1, tp=0x7f43d67fba60) at ../sysdeps/unix/clock_gettime.c:115
    #2  0x00007f44178b9f71 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
    #3  0x00007f4417a36ba9 in QTimerInfoList::updateCurrentTime() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
    #4  0x00007f4417a37155 in QTimerInfoList::timerWait(timespec&) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
    #5  0x00007f4417a384fe in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
    #6  0x00007f4411abda6d in g_main_context_prepare () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
    #7  0x00007f4411abe49b in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
    #8  0x00007f4411abe68c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
    #9  0x00007f4417a38f2b in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
    #10 0x00007f44179e288a in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
    #11 0x00007f441780ffe3 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
    #12 0x00007f4417814c98 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
    #13 0x00007f4413bef6da in start_thread (arg=0x7f43d67fc700) at pthread_create.c:456
    #14 0x00007f4416e1817f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:105
    
    Thread 6 (Thread 0x7f43e6a75700 (LWP 9575)):
    #0  0x00007ffc26ff4b12 in clock_gettime ()
    #1  0x00007f4416e26906 in __GI___clock_gettime (clock_id=1, tp=0x7f43e6a74a60) at ../sysdeps/unix/clock_gettime.c:115
    #2  0x00007f44178b9f71 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
    #3  0x00007f4417a36ba9 in QTimerInfoList::updateCurrentTime() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
    #4  0x00007f4417a37155 in QTimerInfoList::timerWait(timespec&) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
    #5  0x00007f4417a384fe in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
    #6  0x00007f4411abda6d in g_main_context_prepare () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
    #7  0x00007f4411abe49b in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
    #8  0x00007f4411abe68c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
    #9  0x00007f4417a38f2b in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
    #10 0x00007f44179e288a in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
    #11 0x00007f441780ffe3 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
    #12 0x00007f4417814c98 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
    #13 0x00007f4413bef6da in start_thread (arg=0x7f43e6a75700) at pthread_create.c:456
    #14 0x00007f4416e1817f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:105
    
    Thread 5 (Thread 0x7f43fcbc6700 (LWP 9572)):
    #0  0x00007f441780bdf9 in QMutex::lock() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
    #1  0x00007f4417a3869f in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
    #2  0x00007f4411abda6d in g_main_context_prepare () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
    #3  0x00007f4411abe49b in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
    #4  0x00007f4411abe68c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
    #5  0x00007f4417a38f2b in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
    #6  0x00007f44179e288a in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
    #7  0x00007f441780ffe3 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
    #8  0x00007f441abec4c6 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
    #9  0x00007f4417814c98 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
    #10 0x00007f4413bef6da in start_thread (arg=0x7f43fcbc6700) at pthread_create.c:456
    #11 0x00007f4416e1817f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:105
    
    Thread 4 (Thread 0x7f43febe4700 (LWP 9570)):
    #0  0x00007f4411b03ef4 in g_mutex_unlock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
    #1  0x00007f4411abdf81 in g_main_context_check () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
    #2  0x00007f4411abe514 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
    #3  0x00007f4411abe68c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
    #4  0x00007f4417a38f2b in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
    #5  0x00007f44179e288a in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
    #6  0x00007f441780ffe3 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
    #7  0x00007f4418399df5 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
    #8  0x00007f4417814c98 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
    #9  0x00007f4413bef6da in start_thread (arg=0x7f43febe4700) at pthread_create.c:456
    #10 0x00007f4416e1817f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:105
    
    Thread 3 (Thread 0x7f43ffdf5700 (LWP 9569)):
    #0  0x00007ffc26ff4b12 in clock_gettime ()
    #1  0x00007f4416e26906 in __GI___clock_gettime (clock_id=1, tp=0x7f43ffdf4a30) at ../sysdeps/unix/clock_gettime.c:115
    #2  0x00007f44178b9f71 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
    #3  0x00007f4417a36ba9 in QTimerInfoList::updateCurrentTime() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
    #4  0x00007f4417a37155 in QTimerInfoList::timerWait(timespec&) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
    #5  0x00007f4417a384fe in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
    #6  0x00007f4411abda6d in g_main_context_prepare () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
    #7  0x00007f4411abe49b in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
    #8  0x00007f4411abe68c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
    #9  0x00007f4417a38f2b in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
    #10 0x00007f44179e288a in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
    #11 0x00007f441780ffe3 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
    #12 0x00007f441966e5c5 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5
    #13 0x00007f4417814c98 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
    #14 0x00007f4413bef6da in start_thread (arg=0x7f43ffdf5700) at pthread_create.c:456
    #15 0x00007f4416e1817f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:105
    
    Thread 2 (Thread 0x7f44085c2700 (LWP 9568)):
    #0  0x00007f4416e0c18d in poll () at ../sysdeps/unix/syscall-template.S:84
    #1  0x00007f4411653c62 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1
    #2  0x00007f44116558d7 in xcb_wait_for_event () from /usr/lib/x86_64-linux-gnu/libxcb.so.1
    #3  0x00007f440ab19ed9 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
    #4  0x00007f4417814c98 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
    #5  0x00007f4413bef6da in start_thread (arg=0x7f44085c2700) at pthread_create.c:456
    #6  0x00007f4416e1817f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:105
    
    Thread 1 (Thread 0x7f441b8748c0 (LWP 9567)):
    [KCrash Handler]
    #6  0x00007f441a8ad480 in UpdateItem::setProgress(double) () from /usr/lib/x86_64-linux-gnu/plasma-discover/libDiscoverCommon.so
    #7  0x00007f441a8ae1ec in UpdateModel::resourceHasProgressed(AbstractResource*, double) () from /usr/lib/x86_64-linux-gnu/plasma-discover/libDiscoverCommon.so
    #8  0x00007f4417a1081e in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
    #9  0x00007f441a8c8dac in ResourcesUpdatesModel::resourceProgressed(AbstractResource*, double) () from /usr/lib/x86_64-linux-gnu/plasma-discover/libDiscoverCommon.so
    #10 0x00007f4417a1081e in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
    #11 0x00007f441a8c83cc in AbstractBackendUpdater::resourceProgressed(AbstractResource*, double) () from /usr/lib/x86_64-linux-gnu/plasma-discover/libDiscoverCommon.so
    #12 0x00007f43e90c7d49 in ?? () from /usr/lib/x86_64-linux-gnu/qt5/plugins/discover/packagekit-backend.so
    #13 0x00007f4417a1081e in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
    #14 0x00007f43e8e74104 in PackageKit::Transaction::itemProgress(QString const&, PackageKit::Transaction::Status, unsigned int) () from /usr/lib/x86_64-linux-gnu/libpackagekitqt5.so.0
    #15 0x00007f43e8e75f69 in ?? () from /usr/lib/x86_64-linux-gnu/libpackagekitqt5.so.0
    #16 0x00007f4417a104a9 in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
    #17 0x00007f43e8e84361 in ?? () from /usr/lib/x86_64-linux-gnu/libpackagekitqt5.so.0
    #18 0x00007f43e8e84b50 in ?? () from /usr/lib/x86_64-linux-gnu/libpackagekitqt5.so.0
    #19 0x00007f4419678650 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5
    #20 0x00007f4417a11359 in QObject::event(QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
    #21 0x00007f4418f4e35c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
    #22 0x00007f4418f55b11 in QApplication::notify(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
    #23 0x00007f44179e48a0 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
    #24 0x00007f44179e702d in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
    #25 0x00007f4417a38b03 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
    #26 0x00007f4411abe377 in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
    #27 0x00007f4411abe5e0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
    #28 0x00007f4411abe68c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
    #29 0x00007f4417a38f2b in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
    #30 0x00007f44179e288a in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
    #31 0x00007f44179eaffc in QCoreApplication::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
    #32 0x0000559127e2ab16 in ?? ()
    #33 0x00007f4416d303f1 in __libc_start_main (main=0x559127e2a410, argc=3, argv=0x7ffc26fecb58, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7ffc26fecb48) at ../csu/libc-start.c:291
    #34 0x0000559127e2ad5a in _start ()
    Any ideas?
    Just to remind users and devs that Ubuntu and its flavors have a long way to go to be as usr friendly as they should be.

    http://www.kubuntu.org/getkubuntu

    #2
    Open a konsole and issue

    sudo apt-get update
    sudo apt-get dist-upgrade

    If you get an error msg again then do
    apt-get -f install
    followed by
    dpkg --configure -a

    Repeat those two until things clear up or you get the same error msg over and over. If the "apt-get update" returns a msg about being locked you'll have to delete the lock file (called "lock") in /var/lib/dpkg
    sudo rm
    /var/lib/dpkg/lock
    Then begin again with the update command and continue on.

    I always use the konsole to do
    sudo apt-get update
    sudo apt-get dist-upgrade




    "A nation that is afraid to let its people judge the truth and falsehood in an open market is a nation that is afraid of its people.”
    – John F. Kennedy, February 26, 1962.

    Comment


      #3
      Originally posted by GreyGeek View Post
      Open a konsole and issue

      sudo apt-get update
      sudo apt-get dist-upgrade

      If you get an error msg again then do
      apt-get -f install
      followed by
      dpkg --configure -a

      Repeat those two until things clear up or you get the same error msg over and over. If the "apt-get update" returns a msg about being locked you'll have to delete the lock file (called "lock") in /var/lib/dpkg
      sudo rm
      /var/lib/dpkg/lock
      Then begin again with the update command and continue on.

      I always use the konsole to do
      sudo apt-get update
      sudo apt-get dist-upgrade



      vince@vince-HP-Pavilion-dv6-Notebook-PC:~$ sudo apt-get update
      [sudo] password for vince:
      Hit:1 http://us.archive.ubuntu.com/ubuntu zesty InRelease
      Get:2 http://us.archive.ubuntu.com/ubuntu zesty-updates InRelease [89.2 kB]
      Get:3 http://security.ubuntu.com/ubuntu zesty-security InRelease [89.2 kB]
      Get:4 http://us.archive.ubuntu.com/ubuntu zesty-backports InRelease [89.2 kB]
      Get:5 http://us.archive.ubuntu.com/ubuntu zesty-updates/main amd64 DEP-11 Metadata [36.5 kB]
      Get:6 http://us.archive.ubuntu.com/ubuntu zesty-updates/universe amd64 DEP-11 Metadata [39.4 kB]
      Get:7 http://us.archive.ubuntu.com/ubuntu zesty-updates/universe DEP-11 64x64 Icons [32.6 kB]
      Get:8 http://us.archive.ubuntu.com/ubuntu zesty-updates/universe DEP-11 128x128 Icons [85.5 kB]
      Get:9 http://us.archive.ubuntu.com/ubuntu zesty-backports/universe amd64 DEP-11 Metadata [3,980 B]
      Get:10 http://security.ubuntu.com/ubuntu zesty-security/main amd64 DEP-11 Metadata [204 B]
      Get:11 http://security.ubuntu.com/ubuntu zesty-security/universe amd64 DEP-11 Metadata [4,208 B]
      Fetched 470 kB in 1s (375 kB/s)
      Reading package lists... Done
      vince@vince-HP-Pavilion-dv6-Notebook-PC:~$ sudo apt-get dist-upgrade
      Reading package lists... Done
      Building dependency tree
      Reading state information... Done
      Calculating upgrade... Done
      0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
      vince@vince-HP-Pavilion-dv6-Notebook-PC:~$

      Thats weird because discovery was updating 91 packages when it Seg faulted.
      Last edited by steve7233; May 20, 2017, 11:22 PM. Reason: added last sentence
      Just to remind users and devs that Ubuntu and its flavors have a long way to go to be as usr friendly as they should be.

      http://www.kubuntu.org/getkubuntu

      Comment


        #4
        I just found this: on launchpad.net bug number 1674760. So this has been happening for a while.
        Last edited by steve7233; May 21, 2017, 02:12 AM.
        Just to remind users and devs that Ubuntu and its flavors have a long way to go to be as usr friendly as they should be.

        http://www.kubuntu.org/getkubuntu

        Comment


          #5
          You should still run the apt-get -f install and the dpkg --configure -a commands to be sure all 91 of the files were installed and configured.


          Sent from my iPhone using Tapatalk
          "A nation that is afraid to let its people judge the truth and falsehood in an open market is a nation that is afraid of its people.”
          – John F. Kennedy, February 26, 1962.

          Comment


            #6
            Originally posted by GreyGeek View Post
            You should still run the apt-get -f install and the dpkg --configure -a commands to be sure all 91 of the files were installed and configured.

            Sent from my iPhone using Tapatalk
            vince@vince-HP-Pavilion-dv6-Notebook-PC:~$ sudo apt-get -f install
            [sudo] password for vince:
            Reading package lists... Done
            Building dependency tree
            Reading state information... Done
            0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
            vince@vince-HP-Pavilion-dv6-Notebook-PC:~$ sudo dpkg --config -a
            dpkg: error: unknown option --config

            Type dpkg --help for help about installing and deinstalling packages[*];
            Use 'apt' or 'aptitude' for user-friendly package management;
            Type dpkg -Dhelp for a list of dpkg debug flag values;
            Type dpkg --force-help for a list of forcing options;
            Type dpkg-deb --help for help about manipulating *.deb files;

            Options marked[*] produce a lot of output - pipe it through 'less' or 'more' !
            vince@vince-HP-Pavilion-dv6-Notebook-PC:~$ sudo dpkg --configure -a
            vince@vince-HP-Pavilion-dv6-Notebook-PC:~$
            Just to remind users and devs that Ubuntu and its flavors have a long way to go to be as usr friendly as they should be.

            http://www.kubuntu.org/getkubuntu

            Comment


              #7
              It appears that all your packages were installed and configured before Discover segfaulted, so the problem appears to be with Discover. You could purge Discover, do an autoremove and then reinstall it. Or, just work with muon or synaptic.
              "A nation that is afraid to let its people judge the truth and falsehood in an open market is a nation that is afraid of its people.”
              – John F. Kennedy, February 26, 1962.

              Comment


                #8
                Originally posted by GreyGeek View Post
                It appears that all your packages were installed and configured before Discover segfaulted, so the problem appears to be with Discover. You could purge Discover, do an autoremove and then reinstall it. Or, just work with muon or synaptic.
                I will just use synaptic for now. Since Launch pad has known about this bug for several months then I am sure there will be a patch at some point to fix the segfault. I clicked on the 'This effects me to' link.
                Just to remind users and devs that Ubuntu and its flavors have a long way to go to be as usr friendly as they should be.

                http://www.kubuntu.org/getkubuntu

                Comment


                  #9
                  I just recently installed Kubuntu 17.04 for the first time on a fresh install discover crashed for me. I had not only discover crash but somehow had removed itself completely from system. I know for myself I had to reinstall and do the above mentioned apt-get update and apt-get upgrade until it finished all the updates for the entire system to be stable.

                  Comment

                  Working...
                  X