Bug 9248 - 3_b2: Several Freeing read locks for locker after kernel deletion by rpmdrake
Summary: 3_b2: Several Freeing read locks for locker after kernel deletion by rpmdrake
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: x86_64 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Thierry Vignaud
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-03-03 21:36 CET by Bit Twister
Modified: 2013-04-21 00:51 CEST (History)
1 user (show)

See Also:
Source RPM: urpmi
CVE:
Status comment:


Attachments

Description Bit Twister 2013-03-03 21:36:13 CET
Description of problem:

Several  Freeing read locks for locker after kernel deletion by rpmdrake
urpme --auto-orphans
BDB2053 Freeing read locks for locker 0x334c: 3809/139778753140480
BDB2053 Freeing read locks for locker 0x334e: 3809/139778753140480
BDB2053 Freeing read locks for locker 0x334f: 3809/139778753140480
BDB2053 Freeing read locks for locker 0x3350: 3809/139778753140480
BDB2053 Freeing read locks for locker 0x3351: 3809/139778753140480
BDB2053 Freeing read locks for locker 0x3352: 3809/139778753140480
BDB2053 Freeing read locks for locker 0x3353: 3809/139778753140480
BDB2053 Freeing read locks for locker 0x3354: 3809/139778753140480
BDB2053 Freeing read locks for locker 0x3355: 3809/139778753140480
BDB2053 Freeing read locks for locker 0x3356: 3809/139778753140480
BDB2053 Freeing read locks for locker 0x3357: 3809/139778753140480
BDB2053 Freeing read locks for locker 0x3358: 3809/139778753140480
BDB2053 Freeing read locks for locker 0x3359: 3809/139778753140480
writing /var/lib/rpm/installed-through-deps.list
No orphans to remove

Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
1. click up a root terminal
2. mcc->Software Management->Install & Remove Software
3. un-mark previous fglrx-kernel, fglrx-kernel-desktop-latest, kernel-desktop-latest, kernel-desktop-devel, kernel-desktop for uninstall
4. click Apply, OK
5. urpme --auto-orphans



Reproducible: 

Steps to Reproduce:
Bit Twister 2013-03-03 21:40:07 CET

Summary: 3_b3: Several Freeing read locks for locker after kernel deletion by rpmdrake => 3_b2: Several Freeing read locks for locker after kernel deletion by rpmdrake

Manuel Hiebel 2013-03-04 20:58:12 CET

Assignee: bugsquad => thierry.vignaud

Comment 1 Philippe Leblanc 2013-04-19 00:50:04 CEST
I'm seeing these types of messages for other types of urpm transactions.

[root@localhost ~]# urpmi --auto-update
le média « Core Release » est à jour
le média « Core Updates » est à jour
le média « Nonfree Release » est à jour
le média « Nonfree Updates » est à jour
le média « Core 32bit Release » est à jour
le média « Core 32bit Updates » est à jour
BDB2053 Freeing read locks for locker 0x61: 9369/139868743370496
BDB2053 Freeing read locks for locker 0x63: 9369/139868743370496
BDB2053 Freeing read locks for locker 0x64: 9369/139868743370496
BDB2053 Freeing read locks for locker 0x65: 9369/139868743370496
BDB2053 Freeing read locks for locker 0x66: 9369/139868743370496
BDB2053 Freeing read locks for locker 0x67: 9369/139868743370496
BDB2053 Freeing read locks for locker 0x68: 9369/139868743370496
BDB2053 Freeing read locks for locker 0x69: 9369/139868743370496
BDB2053 Freeing read locks for locker 0x6a: 9369/139868743370496
BDB2053 Freeing read locks for locker 0x6b: 9369/139868743370496
BDB2053 Freeing read locks for locker 0x6c: 9369/139868743370496
BDB2053 Freeing read locks for locker 0x6d: 9369/139868743370496
BDB2053 Freeing read locks for locker 0x6e: 9369/139868743370496
Les paquetages sont à jour

Here in this case it was an update. Is this just debugging information that will disappear once MGA3 final appears? Or is there some type of problem?

CC: (none) => philippe.l

Comment 2 Thierry Vignaud 2013-04-21 00:51:26 CEST
Fixed in SVN

Status: NEW => RESOLVED
Resolution: (none) => FIXED
Source RPM: rpmdrake-5.40.2-1.mga3.src.rpm => urpmi


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