|
Bugzilla – Full Text Bug Listing |
| Summary: | zypp: occasional crashes of packagekitd | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE 11.4 | Reporter: | Stanislav Brabec <sbrabec> |
| Component: | Basesystem | Assignee: | E-mail List <zypp-maintainers> |
| Status: | VERIFIED FIXED | QA Contact: | E-mail List <qa-bugs> |
| Severity: | Critical | ||
| Priority: | P2 - High | CC: | carlos.e.r, dmacvicar, forgotten_--EoyBps8f, heiko.rommel, linux, lnussel, meissner |
| Version: | Final | ||
| Target Milestone: | --- | ||
| Hardware: | Other | ||
| OS: | Other | ||
| Whiteboard: | maint:released:11.4:41044 | ||
| Found By: | --- | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Deadline: | 2011-05-26 | ||
|
Description
Stanislav Brabec
2011-04-07 11:32:00 UTC
I just fixed this crash. This deserves an online update. created request id 68513 home:dmacvicar:branches:openSUSE:11.4:Update:Test/PackageKit This is an autogenerated message for OBS integration: This bug (685831) was mentioned in https://build.opensuse.org/request/show/68513 As it is a softwaremgmt update, I think we should collect more zypper, libzypp and Packagekit bugs and then start a bundled update. For the moment: -1 I do not agree. This bug is triggered by attempt to call e. g. GNOME updat tool - I see that the GUI tool is checking for updates forever and then update icon disapears, i. e. it blocks all updates for not advanced users. Update itself may be not as easy as it seems, as the update tool itself crashes. I guess we need not only to update, but we have to find a safe way to update without seing this crash. (I guess that the GNOME update tool works only if the number of pending updates is very low, say <5. YaST2 online_update works and next day GNOME update tool works as well.) we can of course do it right now. but please elaborate, is GNOME updating via the update applet working at all? or not? or just failking randomly? It fails consistently, but only sometimes. Blindly guessing that it depends on the number of installable updates (and surely depends on updates available on the server and updates installed on the system). Some day it consistently failed. Then I called YaST2 online_update, installed updates, and next day it worked and was able to install updates. I did not mention it in the original report, because I found a relation between "GNOME update tool never finishes" and "packagekitd crashes" just today. This is an autogenerated message for OBS integration: This bug (685831) was mentioned in https://build.opensuse.org/request/show/68569 I can confirm that this bug is affecting me on KDE as well. kpackagekit did not report any updates for over a week. I finally got suspicious and looked with zypper to find that there were indeed updates to be applied. Once I installed these updates "manually" (with Yast online update), then kpackagekit began to work again. I saw this bug and now I periodically check dmesg to be sure that kpackagekit isn't getting fooled by the crash. A couple of days ago the backend was crashing again and I had to do a manual update--which again fixed the crashing. I don't know what conditions are causing the backend to crash, but it does appear to be blocking all updates by kpackagekit. (In reply to comment #7) > Blindly guessing that it depends on the number of installable updates (and > surely depends on updates available on the server and updates installed on the > system). Yes and no, the bug Duncan fixed yesterday is a programming error; the PKbackend code references temporary objects after they went out of scope. Thus it's a race between the loop computing the updates and the system reusing the free memory. This is undefined behavior and a crash is probably not the worst case. i would say lets do the update now and hope for the best. +1 it is probably quite impossible to have a always working update scenario here. Okay, Update started: SwampID: 40504 Be so kind and submit a patchinfo. The SWAMPID for this issue is 40504. This issue was rated as low. Please submit fixed packages until 2011-05-26. Also create a patchinfo file using this link: https://swamp.suse.de/webswamp/wf/40504 The SWAMPID for this issue is 40504. This issue was rated as low. Please submit fixed packages until 2011-05-26. Also create a patchinfo file using this link: https://swamp.suse.de/webswamp/wf/40504 The SWAMPID for this issue is 40504. This issue was rated as low. Please submit fixed packages until 2011-05-26. Also create a patchinfo file using this link: https://swamp.suse.de/webswamp/wf/40504 This is an autogenerated message for OBS integration: This bug (685831) was mentioned in https://build.opensuse.org/request/show/68819 *** Bug 693231 has been marked as a duplicate of this bug. *** *** Bug 681420 has been marked as a duplicate of this bug. *** How are users supposed to know that there are updates and how to install them? packagekit reproducibly segfaults here on a fresh install every time. Is there a way to modify the repo data in a way to avoid the segfault so packagekit could at least update itself? according to duncan when using a YOU patch, the crash does not happen. (perhaps the requirement "just a single YOU patch" thpoiugh?) nevertheless, we can start. (In reply to comment #20) > according to duncan when using a YOU patch, the crash does not happen. > > (perhaps the requirement "just a single YOU patch" thpoiugh?) > > nevertheless, we can start. I'm using KDE here. After initial 11.4 install the KDE "KPackagekit" applet was working when calling /usr/lib/packagekitd After some updates had been done (some weeks ago), the packagekitd daemon started to _always_ (!) segfault when the KDE applet was searching for updates: May 21 04:48:10 linux300 kernel: [42043.636187] packagekitd[26099]: segfault at b296d00f ip b6f30065 sp b3c31840 error 4 in libzypp.so.810.2.1[b6b5b000+4c2000] Today- this running box is on the latest update stage from Tumbleweed (21 May 2011): - Kernel 2.6.38.6-29-default - all other related updates _are_ installed I did all the updates using zypper inside a konsole. The segfault still appears! Cheers, Günter Btw - it seems to be not related to the number of outstanding updates, here the segfault is _always_ seen - even with "null" waiting updates. Thanks Guenter, but we already know that. The point we are focusing right now is if the updater crashes when there is an update marked as "restart suggested" (ie: package manager update), and it looks like it does not. Update released for: PackageKit, PackageKit-branding-upstream, PackageKit-browser-plugin, PackageKit-browser-plugin-debuginfo, PackageKit-debuginfo, PackageKit-debugsource, PackageKit-devel, PackageKit-doc, PackageKit-gstreamer-plugin, PackageKit-gstreamer-plugin-debuginfo, PackageKit-gtk-module, PackageKit-gtk-module-debuginfo, PackageKit-gtk3-module, PackageKit-gtk3-module-debuginfo, PackageKit-lang, libpackagekit-glib2-14, libpackagekit-glib2-14-debuginfo, libpackagekit-glib2-devel, libpackagekit-qt-devel, libpackagekit-qt14, libpackagekit-qt14-debuginfo, libpackagekit-qt2-2, libpackagekit-qt2-2-debuginfo, libpackagekit-qt2-devel Products: openSUSE 11.4 (debug, i586, x86_64) closing as fixed. |