Application: muon-updater (2.0.65) KDE Platform Version: 4.10.90 Qt Version: 4.8.4 Operating System: Linux 3.10.0-2-generic x86_64 Distribution: Ubuntu Saucy Salamander (development branch) -- Information about the crash: - What I was doing when the application crashed: This was a hang - I triggered this report by using ubuntu-bug with a pid to report the hang. I opened muon when I was notified there were some updates, I opened it, let it download and install all the updates, and then it returned to a screen with a single progress bar and a title like 'Downloading software list' (sorry I didn't expect the window to disappear when I hit the report-bug so don't have the exact text). It showed a download speed of some 700kB/s, for many minutes, however I verfied with iftop that there wasn't anything being transferred. The crash can be reproduced every time. -- Backtrace: Application: Muon Update Manager (muon-updater), signal: Aborted Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f0f5f5967c0 (LWP 4317))] Thread 3 (Thread 0x7f0f4c346700 (LWP 4318)): #0 0x00007f0f5cc143cd in poll () at ../sysdeps/unix/syscall-template.S:81 #1 0x00007f0f59f9b394 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x00007f0f59f9b49c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x00007f0f5d39aa76 in QEventDispatcherGlib::processEvents (this=0x7f0f440008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:426 #4 0x00007f0f5d36c5ef in QEventLoop::processEvents (this=this@entry=0x7f0f4c345d70, flags=...) at kernel/qeventloop.cpp:149 #5 0x00007f0f5d36c8e5 in QEventLoop::exec (this=this@entry=0x7f0f4c345d70, flags=...) at kernel/qeventloop.cpp:204 #6 0x00007f0f5d26b88f in QThread::exec (this=this@entry=0x154a3c0) at thread/qthread.cpp:542 #7 0x00007f0f5d34dd13 in QInotifyFileSystemWatcherEngine::run (this=0x154a3c0) at io/qfilesystemwatcher_inotify.cpp:256 #8 0x00007f0f5d26df2f in QThreadPrivate::start (arg=0x154a3c0) at thread/qthread_unix.cpp:338 #9 0x00007f0f5a472f8e in start_thread (arg=0x7f0f4c346700) at pthread_create.c:311 #10 0x00007f0f5cc20e1d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:113 Thread 2 (Thread 0x7f0f38eff700 (LWP 4545)): #0 0x00007f0f5cc143cd in poll () at ../sysdeps/unix/syscall-template.S:81 #1 0x00007f0f59f9b394 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x00007f0f59f9b49c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x00007f0f5d39aa76 in QEventDispatcherGlib::processEvents (this=0x7f0f2c0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:426 #4 0x00007f0f5d36c5ef in QEventLoop::processEvents (this=this@entry=0x7f0f38efed70, flags=...) at kernel/qeventloop.cpp:149 #5 0x00007f0f5d36c8e5 in QEventLoop::exec (this=this@entry=0x7f0f38efed70, flags=...) at kernel/qeventloop.cpp:204 #6 0x00007f0f5d26b88f in QThread::exec (this=this@entry=0x32d3420) at thread/qthread.cpp:542 #7 0x00007f0f5d34dd13 in QInotifyFileSystemWatcherEngine::run (this=0x32d3420) at io/qfilesystemwatcher_inotify.cpp:256 #8 0x00007f0f5d26df2f in QThreadPrivate::start (arg=0x32d3420) at thread/qthread_unix.cpp:338 #9 0x00007f0f5a472f8e in start_thread (arg=0x7f0f38eff700) at pthread_create.c:311 #10 0x00007f0f5cc20e1d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:113 Thread 1 (Thread 0x7f0f5f5967c0 (LWP 4317)): [KCrash Handler] #6 0x00007f0f5cc143cd in poll () at ../sysdeps/unix/syscall-template.S:81 #7 0x00007f0f59f9b394 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #8 0x00007f0f59f9b49c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #9 0x00007f0f5d39aa76 in QEventDispatcherGlib::processEvents (this=0x12b3de0, flags=...) at kernel/qeventdispatcher_glib.cpp:426 #10 0x00007f0f5ddff9d6 in QGuiEventDispatcherGlib::processEvents (this=<optimized out>, flags=...) at kernel/qguieventdispatcher_glib.cpp:204 #11 0x00007f0f5d36c5ef in QEventLoop::processEvents (this=this@entry=0x7fff4ad505b0, flags=...) at kernel/qeventloop.cpp:149 #12 0x00007f0f5d36c8e5 in QEventLoop::exec (this=this@entry=0x7fff4ad505b0, flags=...) at kernel/qeventloop.cpp:204 #13 0x00007f0f5d371e5b in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1218 #14 0x00007f0f5dd5c34c in QApplication::exec () at kernel/qapplication.cpp:3828 #15 0x000000000040cdb1 in main (argc=1, argv=0x7fff4ad507e8) at /build/buildd/muon-2.0.65/updater/main.cpp:59 Possible duplicates by query: bug 322181, bug 322049, bug 321758, bug 321713, bug 321690. Reported using DrKonqi
This seems to have fixed itself in one of the updates in the last couple of days.
This has reappeared again, so it's not as simple.
I'd like to confirm this. Hasn't gone away for me. Every couple of days I get a notice of security updates. When I click on the notice, Muon Updater comes up and hangs with the little spinning dots in the middle of the dialog. I don't even get the "Loading Software List" or the progress bar at the bottom. Once (only) the list of packages came up and I clicked Install Updates. It got to 33% and then said "Finished" and then gave me the same updates to install. I clicked Install Updates again and it hung "Loading Software List". I waited over 10 minutes. I clicked the X at top right: wouldn't close. I tried Ctrl-Alt-Esc: It closed but when I opened it again, I got the spinning dots again. This has been going on for a couple of weeks.
https://bugs.launchpad.net/ubuntu/+source/muon/+bug/1239328 was confirmed but then they said that it was something KDE had to handle.
I am also seeing everything describe in the original bug report description. This is a fairly serious regression and should be fixed. Is there anything I can contribute?
Work-around: go into Muon Package Manager, click on "Upgradeable" in the list on the left, and you can manually update components. After this, Muon Update Manager tells me I have to update one (1) package, which I'd already updates in the Package Manager. When I click Install Updates, it immediately tells me that the software on my system is up to date. Muon Update Manager now does this same thing, for this same package, each time I bring it up.
I can confirm this bug. It happens everytime muo-update rans. But has happened only since the Kubuntu 13.10 update.
I can confirm this issue as well. It's loading the software list for about 5 minutes now as we speak. This also happens since the upgrade to kubuntu 13.10.
I confirm the issue. Why is this issue a KDE bug?
In support of the issue. My update hangs every single time. Kubuntu 13.10 x86_64
Interestingly, when muon-updater hangs, it will not close by clicking the X at the top right. (And plasma never offers to close it for me either.) The only way to close it is to kill it from the command line.
Hangs every time for me too, after an update with the progress slider moving back and forth. Kubuntu 13.10 64-bit.
the issue on my end seems to be that it hangs up on prompting for authentication. The password input box never comes up. Also, most of my wine dependent programs quit working as well. I am considering backing up all of my data on an external and downgrading to 13.04 or 12.10. Those releases seemed to work flawless.
Still happening, even after updates yesterday. Have let it run for up to an hour, still no list of updates, no error message. I can quit & restart but no change. Muon Package Manager shows correct files & allows update. Software Updater still hangs after letting Package Manager do Updater's job.
Can you still reproduce this with the most recent version (2.1.3)?
I haven't seen any hangs for quite a while.
Neither have I. Things look stable for now.
Yeh, I've not seen it in ages - closing as works-for-me
Seems to be fine.