This also happened on Ubuntu 16.04 in 2017.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1069350
Title:
suspicious /.rpmdb root directory
To manage notifications about this bug go to:
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: rpm (Ubuntu Trusty)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1069350
Title:
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: dkms (Ubuntu Trusty)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1069350
Title:
I am running Ubuntu 12.04 and also have an .rpmdb directory in my home
folder and in /root as well (both directories owned by root). It looks
like there hasn't been a fix for this? Although the time stamps on
them are from 5-6 months ago (5 mo's ago in /root and 6 mo's ago in my
home
** Bug watch removed: Debian Bug tracker #551669
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=551669
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1069350
Title:
suspicious /.rpmdb root
I can confirm that trusty 14.04.2 LTS is affected. I have this problem
on my xubuntu 14.04.2. Latest avaialable rpm package version is
4.11.1-3ubuntu0.1.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
It looks like the fix in rpm in Debian is to use bash instead of dash,
so the fallback from $HOME to ~ works if $HOME is not set.
I'm not sure if this particular fix is appropriate for Trusty as the rpm
package doesn't currently depend on bash. Incidentally, shouldn't the
fix in Debian have
The bash package is an Essential: yes package also in Trusty so no
dependency is necessary. The Debian patch should be appropriate for an
SRU.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1069350
Charles, if you think the small fix for rpm is worth being applied to
14.04, the proper procedure to follow is to request an SRU, see
https://wiki.ubuntu.com/StableReleaseUpdates.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Just found this same abovementioned /.rpmdb directory on my install. It
wasn't there before and hasn't ever been there before this morning. I
did not do anything involving a kernel. Although vmware player uses
dkms when a new kernel is installed, no new kernel was installed today.
When will
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: dkms (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1069350
Title:
This bug was fixed in the package rpm - 4.11.2-2.1
---
rpm (4.11.2-2.1) unstable; urgency=medium
* Non-maintainer upload.
* Use bash to expand ~ in %_dbpath (Closes: #741324)
-- Ben Hutchings b...@decadent.org.uk Sat, 22 Mar 2014 22:49:01 +
** Changed in: rpm (Ubuntu)
** Bug watch added: Debian Bug tracker #741399
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=741399
** Also affects: dkms (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=741399
Importance: Unknown
Status: Unknown
--
You received this bug notification because you
** Changed in: dkms (Debian)
Status: Unknown = New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1069350
Title:
suspicious /.rpmdb root directory
To manage notifications about this bug go
** Branch linked: lp:debian/rpm
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1069350
Title:
suspicious /.rpmdb root directory
To manage notifications about this bug go to:
Looks like DKMS (via kernel post-install hook, via dpkg, via apt-get) is
responsible for this:
root 18414 0.0 0.0 27848 3864 pts/12 S+ 22:35 0:00 /usr/bin/perl
/var/lib/dpkg/info/linux-image-3.13.0-8-generic.postinst configure 3.13.0-8.27
root 18422 0.0 0.0 4332 616
The attachment Disables RPM call for DKMS seems to be a patch. If it
isn't, please remove the patch flag from the attachment, remove the
patch tag, and if you are a member of the ~ubuntu-reviewers,
unsubscribe the team.
[This is an automated message performed by a Launchpad user owned by
It happened again. What I did:
- (it is a system with precise 12.04 LTS installed)
- removed /.rpmdb/ (I did it just for fun, without any reason)
- made sure /.rpmdb/ is not here
- installed updates with update-manager
- One day later, I checked /.rpmdb/ and it was there again.
ls
The final lines of my last comment in more details:
# rm -Rf /root/.rpmdb /.rpmdb
# ls -ld /root/.rpmdb /.rpmdb
ls: Zugriff auf /root/.rpmdb nicht möglich: Datei oder Verzeichnis nicht
gefunden
ls: Zugriff auf /.rpmdb nicht möglich: Datei oder Verzeichnis nicht gefunden
#
Ok, confirmed here that dkms does call rpm if it is installed and can
create an empty rpm database in / or /root as a side-effect of
installing or removing kernel drivers managed with dkms.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
First I want to know what creates this directory. And I hardly believe
it's one of the standard packages, so I also want to remove this issue.
What I recomment in Comment 2 is a way to report an error back from rpm
to the calling command or package. It could be very helpful to find the
real source
The bug is that I think it's a standard Ubuntu package which causes the
creation of all /root/.rpmdb/ /.rpmdb/ and ~/.rpmdb (i just checked
again I have all of them). The .rpmdb directories in the user
directories are ok (but I prefer them in a /tmp/ directory if they are
in fact temporary. But
Then again I just read your initial comment and it also sounds like you
just want a support answer for why this directory exists, posted in a
place where other users can find the answer as well. Is that accurate?
--
You received this bug notification because you are a member of Ubuntu
Bugs,
I am a strong believer in LSB as well. However this directory is not
created by the rpm package. I have a standard Ubuntu install plus lsb
and I do not see any of these directories. Would you be able to provide
steps to reproduce from a standard install including the lsb and rpm
packages?
--
You
These directories can indeed be safely removed.
On Ubuntu and other non-rpm-based systems, rpm is typically used to
build and inspect RPM packages, not to install them or manage a
database. The problem for non-rpm-based systems is that the rpm tool
cannot (currently) operate on package files
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: rpm (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1069350
Title:
I too have a ~/.rpmdb owned by root, which is why I visited this report.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1069350
Title:
suspicious /.rpmdb root directory
To manage notifications
** Also affects: rpm (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1069350
Title:
suspicious /.rpmdb root directory
To manage notifications
E.g. cron is well known to not set $HOME by default: I'd agree that the root
cause
for creating non-FHS /.rpmdb is due to $HOME not being set (and RPM patched
to use $HOME in essential/mandatory configuration like %_dbpath).
These issues are in a Debian patch to RPM and needs to be addressed
29 matches
Mail list logo
