875457 – Installing a package with zypper leaves a stale .rpm.lock in /var/lib/rpm/

Bug 875457 - Installing a package with zypper leaves a stale .rpm.lock in /var/lib/rpm/

Summary: Installing a package with zypper leaves a stale .rpm.lock in /var/lib/rpm/

Status:	RESOLVED DUPLICATE of bug 855993

Alias:	None

Product:	openSUSE 13.1
Classification:	openSUSE
Component:	libzypp (show other bugs)
Version:	Final
Hardware:	Other openSUSE 13.1

Priority:	P5 - None Severity: Normal (vote)
Target Milestone:	---
Assignee:	E-mail List
QA Contact:	E-mail List

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Clone This Bug

Reported:	2014-04-28 11:33 UTC by Stefan Brüns
Modified:	2014-04-28 11:57 UTC (History)
CC List:	1 user (show)

See Also:
Found By:	---
Services Priority:
Business Priority:
Blocker:	---
Marketing QA Status:	---
IT Deployment:	---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Stefan Brüns 2014-04-28 11:33:53 UTC

User-Agent:       Mozilla/5.0 (Windows NT 6.1; WOW64; rv:22.0) Gecko/20100101 Firefox/22.0

Whenever I install a package with zypper, there is an empty /var/lib/rpm/.rpm.lock file afterwards.

This at least breaks packagekit access to the rpm db (not able to fetch info)



Reproducible: Always

Steps to Reproduce:
1. make sure there is no .rpm.lock
2. install a package, e.g. "zypper in xinput"

Actual Results:  
After the installation, the .rpm.lock is not removed.

If there is a .rpm.lock zypper seems to be unaffected. Apper is not able to access update details.


i | PackageKit-backend-zypp | package | 0.8.11-2.3.1 | x86_64 | openSUSE-13.1-Oss   
i | libzypp                 | package | 13.9.0-13.1  | x86_64 | openSUSE-13.1-Update
i | snapper-zypp-plugin     | package | 0.1.7-1.1    | x86_64 | openSUSE-13.1-Oss   
i | zypp-plugin-python      | package | 0.3-10.1.2   | x86_64 | openSUSE-13.1-Oss   
i | zypper                  | package | 1.9.12-16.1  | x86_64 | openSUSE-13.1-Update
i | zypper-aptitude         | package | 1.9.12-16.1  | noarch | openSUSE-13.1-Update
i | zypper-log              | package | 1.9.12-16.1  | noarch | openSUSE-13.1-Update

i | build-mkdrpms      | package | 20131015-1.1 | noarch | openSUSE-13.1-Oss   
i | deltarpm           | package | 3.6-2.1.2    | x86_64 | openSUSE-13.1-Oss   
i | rpm                | package | 4.11.1-6.5.1 | x86_64 | openSUSE-13.1-Update
i | rpm-32bit          | package | 4.11.1-6.5.1 | x86_64 | openSUSE-13.1-Update
i | rpm-build          | package | 4.11.1-6.5.1 | x86_64 | openSUSE-13.1-Update
i | rpm-python         | package | 4.11.1-6.5.1 | x86_64 | openSUSE-13.1-Update
i | systemd-rpm-macros | package | 2-19.1       | noarch | openSUSE-13.1-Update

Comment 1 Wolfgang Bauer 2014-04-28 11:47:36 UTC

(In reply to comment #0)
> If there is a .rpm.lock zypper seems to be unaffected. Apper is not able to
> access update details.

That Apper cannot access update details has nothing to do with that .rpm.lock file.
It's rather related to packagekitd's ShutdownTimeout, and already reported here:
https://bugzilla.novell.com/show_bug.cgi?id=855993

Comment 2 Michael Andres 2014-04-28 11:57:52 UTC

closing as duplicate

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