Mailinglist Archive: opensuse-bugs (5295 mails)

< Previous Next >
[Bug 848901] New: Zypper usually doesn't manage to finish Packagekitd
  • From: bugzilla_noreply@xxxxxxxxxx
  • Date: Mon, 4 Nov 2013 19:57:31 +0000
  • Message-id: <bug-848901-21960@http.bugzilla.novell.com/>

https://bugzilla.novell.com/show_bug.cgi?id=848901

https://bugzilla.novell.com/show_bug.cgi?id=848901#c0


Summary: Zypper usually doesn't manage to finish Packagekitd
Classification: openSUSE
Product: openSUSE 13.1
Version: RC 2
Platform: Other
OS/Version: Other
Status: NEW
Severity: Normal
Priority: P5 - None
Component: libzypp
AssignedTo: zypp-maintainers@xxxxxxxxxxxxxxxxxxxxxx
ReportedBy: terje@xxxxxxxxxxxxxxxxxxx
QAContact: qa-bugs@xxxxxxx
Found By: ---
Blocker: ---


User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:25.0) Gecko/20100101
Firefox/25.0

Usually after login, starting 'zypper up' with root access in a terminal to
update the system, the operating stops and claims that Packagekitd is already
running. The Zypper dialogue asks to finish or quit packagekit, but even after
entering several 'Yes' as replies, zypper doesn't manage to quit packagekitd
and won't continue.

The normal workaround is to manually abort zypper, identfy the packagekitd
process id with 'ps -el' and kill it manually.

Then 'zypper up' can be started again and run as it should. This has happened
at least during the 12.3 period and 13.1 developement releases. For some
previous releases I think zypper had 'powerful rights' enough to manage this.


Reproducible: Always

Steps to Reproduce:
1.as described above
2.
3.
Actual Results:
as described above

Expected Results:
as described above

--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.

< Previous Next >