Bugzilla – Bug 575843
[kupdateapplet] checks for updates indefinitely
Last modified: 2010-04-07 14:12:22 UTC
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US) AppleWebKit/532.5 (KHTML, like Gecko) Chrome/4.0.249.43 Safari/532.5 Qt: 4.6.1 KDE Development Platform: 4.3.95 (KDE 4.3.95 (KDE 4.4 RC2)) "release 214" Updater Applet: 0.9.5 Recently kupdate applet keeps checking for updates for indefinite time when we select check for updates. It freezes at 100% and does nothing. We need to quit it and start again. Reproducible: Always Steps to Reproduce: 1. Start kupdate applet. 2. Check for updates. Actual Results: it checks for updates indefinitely. Expected Results: It should finish checking for updates and update status accordingly.
I just noticed that it actually hangs with below backtrace. Thread 1 (Thread 0x7f52e41627f0 (LWP 2746)): #0 0x00007f52e1753ff8 in poll () from /lib64/libc.so.6 #1 0x00007f52de4726f9 in g_main_context_poll (n_fds=<value optimized out>, fds=<value optimized out>, priority=<value optimized out>, timeout=<value optimized out>, context=<value optimized out>) at gmain.c:2904 #2 g_main_context_iterate (n_fds=<value optimized out>, fds=<value optimized out>, priority=<value optimized out>, timeout=<value optimized out>, context=<value optimized out>) at gmain.c:2586 #3 0x00007f52de472acc in IA__g_main_context_iteration (context=0x650120, may_block=1) at gmain.c:2654 #4 0x00007f52e2d39323 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4 #5 0x00007f52e1f60dce in ?? () from /usr/lib64/libQtGui.so.4 #6 0x00007f52e2d0e712 in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4 #7 0x00007f52e2d0eaec in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4 #8 0x00007f52e2d1283b in QCoreApplication::exec() () from /usr/lib64/libQtCore.so.4 #9 0x0000000000408506 in _start ()
Further I noticed that it hangs only when using packagekit plugin. With zypp plugin it works fine.
duplicate of #578988 *** This bug has been marked as a duplicate of bug 578988 ***