Description of problem: Doing a 702-package Grand Update of 32-bit Xfce/Kmail Mageia-6 behaved as if VirtualBox was installed when it was not! Version-Release number of selected component (if applicable): urpmi-8.110-2.mga6.src.rpm How reproducible: On a Samsung NC110 netbook on which 32-bit Xfce (+Kmail) Mageia-6 had been installed: Steps to Reproduce: 1. Execute 'urpmi --auto-update --auto' 2. During otherwise excellent uneventful update, noticed in log: ===================================================== 8/702: vboxadditions-kernel-4.9.56-desktop586-1.mga6 50/702: vboxadditions-kernel-4.14.44-desktop586-2.mga6 51/702: vboxadditions-kernel-desktop586-latest vboxguest.ko.xz: - Installation - Installing to /lib/modules/4.9.56-desktop586-1.mga6/dkms- binary/3rdparty/vbox/ vboxsf.ko.xz: - Installation - Installing to /lib/modules/4.9.56-desktop586-1.mga6/dkms- binary/3rdparty/vbox/ vboxvideo.ko.xz: - Installation - Installing to /lib/modules/4.9.56-desktop586-1.mga6/dkms- binary/3rdparty/vbox/ depmod......... DKMS: install Completed. vboxadditions, 5.2.2-1.mga6, 4.9.56-desktop586-1.mga6, i586: installed- binary from 4.9.56-desktop586-1.mga6 Creating: target|kernel|dracut args|basicmodules vboxguest.ko.xz: - Installation - Installing to /lib/modules/4.14.44-desktop586-2.mga6/dkms- binary/3rdparty/vbox/ vboxsf.ko.xz: - Installation - Installing to /lib/modules/4.14.44-desktop586-2.mga6/dkms- binary/3rdparty/vbox/ vboxvideo.ko.xz: - Installation - Installing to /lib/modules/4.14.44-desktop586-2.mga6/dkms- binary/3rdparty/vbox/ depmod.......... DKMS: install Completed. vboxadditions, 5.2.12-1.mga6, 4.14.44-desktop586-2.mga6, i586: installed- binary from 4.14.44-desktop586-2.mga6 701/702: x11-driver-video-vboxvideo ===================================================== 3. Above is puzzling as V'Box was not installed in this Mageia-6 install. Checked V'box situation: --------------------------------- # urpme virtualbox unknown package: virtualbox [root@netbook ~]# urpmi virtualbox Use of uninitialized value in null operation at /usr/lib/perl5/ vendor_perl/5.22.3/i386-linux-thread-multi/URPM/Resolve.pm line 1848. To satisfy dependencies, the following packages are going to be installed: Package Version Release Arch (medium "Core Updates") virtualbox 5.2.12 1.mga6 i586 virtualbox-doc 5.1.30 1.mga6 noarch (recommended) virtualbox-kernel-4.14.44-des> 5.2.12 2.mga6 i586 virtualbox-kernel-desktop586-> 5.2.12 2.mga6 i586 (recommended) 88MB of additional disk space will be used. 27MB of packages will be retrieved. Proceed with the installation of the 4 packages? (Y/n) n [root@netbook ~]# --------------------------------- N.B. There WAS a V'box RPM file in ~/Download, a relic of a previous install of a V'box install on an earlier version of Mageia (but where Vbox was abandoned as the netbook could not handle it) and visible here in it's cloned copy of earlier /home. Whilst the Urpmi action w.r.t. V'box has not caused any problem so far, I have raised this report to draw attention to this bizarre situation, as surely it should not have happened...
Most probably because of in mga6 libEGL.so.1 is incorrectly provided also by x11-driver-video-vboxvideo so it might get selected instead of mesa lib. $ urpmf --provides libEGL.so.1 | sort -u lib64mesaegl1:libEGL.so.1()(64bit) x11-driver-video-vboxvideo:libEGL.so.1()(64bit) libEGL.so.1 provides is filtered out from virtualbox, but only in pkg in updates. meta-task's prefer.vendor.list also has lib(64)mesaegl1 entry, but it's also only in updates.
(In reply to Jani Välimaa from comment #1) > Most probably because of in mga6 libEGL.so.1 is incorrectly provided also by > x11-driver-video-vboxvideo so it might get selected instead of mesa lib. > > $ urpmf --provides libEGL.so.1 | sort -u > lib64mesaegl1:libEGL.so.1()(64bit) > x11-driver-video-vboxvideo:libEGL.so.1()(64bit) > > libEGL.so.1 provides is filtered out from virtualbox, but only in pkg in > updates. meta-task's prefer.vendor.list also has lib(64)mesaegl1 entry, but > it's also only in updates. Thanks, wally. Assigning to the kernel & drivers maintainers, CC'ing the registered maintainer of x11-driver-video-vboxvideo
Summary: 'Urpmi --auto-update' thinks V'box is installed when it is not => 'Urpmi --auto-update' thinks V'box is installed when it is not (x11-driver-video-vboxvideo provides libEGL.so.1)Source RPM: urpmi-8.110-2.mga6.src.rpm => x11-driver-video-vboxvideoAssignee: bugsquad => kernelCC: (none) => marja11, thierry.vignaud
Was the xfce install from a live dvd ? In that case the vboxadditions was on the live media, and if you did not select to remove "un-needed" drivers, it would explain why it is there... Note, the vboxadditions are guest parts, so trying to check that virtualbox (wich is host part) is not installed does not mean anything in this context
CC: (none) => tmb
No, Xfce was a Classic .iso fresh Mageia-6 install.
Discussed on the usenet group alt.os.linux.mageia too. Virtualbox had previously been installed, which also installed the virtualbox-doc and virtualbox-kernel packages. Virtualbox was uninstalled. but those additional packages were not. The orphan packages were still installed. So when updates were available for those packages, they are included in the urpmi --auto-update selection. This is due to a misunderstanding of how dependency installation and removal are handled, not a bug. Maurice, When virtualbox was installed, the package virtualbox was installed, but also packages it requires such as virtualbox-doc were installed as dependencies. When virtualbox was uninstalled, the virtualbox-doc and virtualbox-kernel package were not uninstalled. They remained installed, though would be considered orphans. When an updated virtualbox package was available, the updates include updated virtualbox-doc and virtualbox-kernel packages. When urpmi checks for updates, it sees that you have the virtualbox-doc and kernel packages installed, and that new versions were available, so includes them when selecting all available updates. Closing the bug report as invalid.
Resolution: (none) => INVALIDStatus: NEW => RESOLVEDCC: (none) => davidwhodgins
But V'box was NEVER installed on this Mageia-6!
Reopening. Sorry for the mistake.
Status: RESOLVED => REOPENEDResolution: INVALID => (none)
Please run the command (as root) "journalctl -a|grep virtualbox>/tmp/journal.vb.txt" and then attach the /tmp/journal.vb.txt file to this bug report.
Created attachment 10250 [details] # journalctl -a|grep virtualbox>/tmp/journal.vb.txt
# rpm -qa | grep vbox vboxadditions-kernel-desktop586-latest-5.2.12-2.mga6 x11-driver-video-vboxvideo-5.2.12-1.mga6 vboxadditions-kernel-4.14.44-desktop586-2.mga6-5.2.12-2.mga6 vboxadditions-kernel-4.9.56-desktop586-1.mga6-5.2.2-1.mga6 vboxadditions-kernel-4.9.35-desktop586-1.mga6-5.1.22-20.mga6 [root@netbook ~]# rpm -qa | grep virtualbox [root@netbook ~]# # rpm -qa | grep vbox vboxadditions-kernel-desktop586-latest-5.2.12-2.mga6 x11-driver-video-vboxvideo-5.2.12-1.mga6 vboxadditions-kernel-4.14.44-desktop586-2.mga6-5.2.12-2.mga6 vboxadditions-kernel-4.9.56-desktop586-1.mga6-5.2.2-1.mga6 vboxadditions-kernel-4.9.35-desktop586-1.mga6-5.1.22-20.mga6 [root@netbook ~]# rpm -qa | grep virtualbox [root@netbook ~]#
That output turned out not to provide hoped for info, so leaving this to Jani to sort out.
Hi Maurice, Is this issue still valid for Mageia 7? If so, then please change "Version:" in the upper left of this report accordingly. If not, then please close this report as OLD (or, if you know it was fixed in Mageia 6, as FIXED). Thanks, Marja
A bizarre relic of Mageia-6 Vbox history. Hereby marked as OLD/RESOLVED. Hope have done right thing...
Status: REOPENED => RESOLVEDResolution: (none) => OLD