Bugzilla – Bug 595096
kupdateapplet crash while installing updates
Last modified: 2010-04-22 10:14:01 UTC
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US) AppleWebKit/533.2 (KHTML, like Gecko) Chrome/5.0.342.9 Safari/533.2 kupdateapplet crash with following backtrace while installing available updates. Thread 2 (Thread 0x7f4b7da22910 (LWP 3908)): #0 0x00007f4b897813e2 in select () from /lib64/libc.so.6 #1 0x00007f4b8ad1a903 in ?? () from /usr/lib64/libQtCore.so.4 #2 0x00007f4b8ac49775 in ?? () from /usr/lib64/libQtCore.so.4 #3 0x00007f4b8a9ba65d in start_thread () from /lib64/libpthread.so.0 #4 0x00007f4b89787e1d in clone () from /lib64/libc.so.6 #5 0x0000000000000000 in ?? () Thread 1 (Thread 0x7f4b8c199750 (LWP 3861)): #0 0x00007f4b8977ed03 in poll () from /lib64/libc.so.6 #1 0x00007f4b866a04c9 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x00007f4b866a089c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x00007f4b8ad66eb3 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4 #4 0x00007f4b89f8c51e in ?? () from /usr/lib64/libQtGui.so.4 #5 0x00007f4b8ad3c2a2 in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4 #6 0x00007f4b8ad3c67c in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4 #7 0x00007f4b8ad403cb in QCoreApplication::exec() () from /usr/lib64/libQtCore.so.4 #8 0x0000000000408986 in _start () Reproducible: Always Steps to Reproduce: 1. Check for updates using kupdateapplet. 2. Select all updates. 3. Install Actual Results: Crash Expected Results: Updates should be installed.
According to the backtrace it crashes somewhere deep in libqt4. Dirk, do you have an idea what's wrong?
both threads are waiting (one in select(), the other in poll()). thats not the cause of the backtrace. can you reproduce it? try valgrind.
I can reproduce every time. Should I run in valgrind and post output?
(In reply to comment #3) > I can reproduce every time. Should I run in valgrind and post output? Yes, please. Thank you.
Created attachment 356151 [details] valgrind output.
there is no crash or anything in that valgrind output? did it "crash"?
I think it hanged at least. Not sure about crash. It didn't do anything and stayed in same status for long time. It never finished update of the package I selected.
(In reply to comment #7) > I think it hanged at least. Not sure about crash. It didn't do anything and > stayed in same status for long time. It never finished update of the package I > selected. Hanging progress sounds like bug #578988. *** This bug has been marked as a duplicate of bug 578988 ***