Bug 442716

Summary: updater applet crashed
Product: [openSUSE] openSUSE 11.1 Reporter: Juergen Weigert <jw>
Component: Update ProblemsAssignee: Thomas Göttlicher <tgoettlicher>
Status: RESOLVED DUPLICATE QA Contact: Jiri Srain <jsrain>
Severity: Critical    
Priority: P5 - None CC: forgotten_XG9X5w8kVa
Version: Beta 4   
Target Milestone: ---   
Hardware: Other   
OS: Other   
Whiteboard:
Found By: --- Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---

Description Juergen Weigert 2008-11-07 14:35:13 UTC
A Fatal Error Occurred
The application Updater Applet (kupdateapplet) crashed and caused the signal 6 (SIGABRT).
Please help us improve the software you use by filing a report at http://bugs.kde.org. Useful details include how to reproduce the error, documents that were loaded, etc.

Application: Updater Applet (kupdateapplet), signal SIGABRT
[?1034h(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]
(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)
(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)
[KCrash handler]
#6  0xffffe430 in __kernel_vsyscall ()
#7  0xb65b99b0 in raise () from /lib/libc.so.6
#8  0xb65bb2e8 in abort () from /lib/libc.so.6
#9  0xb6347245 in ?? () from /lib/libdbus-1.so.3
#10 0xb6342c59 in ?? () from /lib/libdbus-1.so.3
#11 0xb632c804 in dbus_set_error () from /lib/libdbus-1.so.3
#12 0xb4a8a6fd in ?? () from /usr/lib/libpolkit-dbus.so.2
#13 0xb4a8a97b in polkit_auth_obtain () from /usr/lib/libpolkit-dbus.so.2
#14 0xb4ae63ec in ?? () from /usr/lib/kde4/kupdateapplet_packagekit.so
#15 0xb4ada98c in ?? () from /usr/lib/kde4/kupdateapplet_packagekit.so
#16 0xb4ad40e2 in ?? () from /usr/lib/kde4/kupdateapplet_packagekit.so
#17 0xb4ad76fc in ?? () from /usr/lib/kde4/kupdateapplet_packagekit.so
#18 0xb7ea0490 in QMetaObject::activate(QObject*, int, int, void**) ()
   from /usr/lib/libQtCore.so.4
#19 0xb7ea1212 in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib/libQtCore.so.4
#20 0x08056591 in _start ()



I was not aware that KDE4 even has an online update application before I saw this crash. There was no icon in the taskbar. I did my updates using zypper.
Comment 1 Andreas Jaeger 2008-11-07 16:54:02 UTC
crash -> critical
Comment 2 Forgotten User XG9X5w8kVa 2008-11-09 21:06:27 UTC
Confirmed. I got the crash on beta4 first run.
Comment 3 Thomas Göttlicher 2008-11-10 15:53:29 UTC

*** This bug has been marked as a duplicate of bug 441826 ***