Bug 19400 - M5.1 removal of orphans causes system not to boot (many not found and unselected packages during install)
Summary: M5.1 removal of orphans causes system not to boot (many not found and unselec...
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 5
Hardware: All Linux
Priority: Normal major
Target Milestone: ---
Assignee: ISO building group
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on: 19518
Blocks:
  Show dependency tree / graph
 
Reported: 2016-09-17 20:03 CEST by William Kenney
Modified: 2016-12-17 09:56 CET (History)
2 users (show)

See Also:
Source RPM:
CVE:
Status comment:

Attachments
Orphan boot error message (5.43 KB, image/png)
2016-09-17 20:06 CEST, William Kenney 		Details
report.bug.xz zipped (279.39 KB, application/zip)
2016-09-21 19:00 CEST, William Kenney 		Details
Orphans list (5.63 KB, text/plain)
2016-11-08 04:52 CET, William Kenney 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Description William Kenney 2016-09-17 20:03:19 CEST 
Description of problem:

After install system reports 32 orphans.
Removal of all causes the system to no longer boot.
See screenshot.

Orphans reported:

[root@localhost wilcal]# urpme --auto-orphans
To satisfy dependencies, the following 32 packages will be removed (163MB):
  
(orphan packages)
  apache-commons-codec-1.9-2.mga5.noarch
  apache-commons-lang-2.6-15.mga5.noarch
  apache-commons-logging-1.1.3-8.mga5.noarch
  dkms-2.0.19-34.1.mga5.noarch
  dkms-minimal-2.0.19-34.1.mga5.noarch
  dkms-vboxadditions-5.1.2-1.mga5.noarch
  gcc-4.9.2-4.1.mga5.i586
  gcc-cpp-4.9.2-4.1.mga5.i586
  geronimo-jms-1.1.1-16.mga5.noarch
  glibc-devel-2.20-23.mga5.i586
  jakarta-commons-httpclient-3.1-15.1.mga5.noarch
  java-1.8.0-openjdk-1.8.0.101-1.b14.1.mga5.i586
  javamail-1.5.1-1.mga5.noarch
  kernel-desktop-devel-4.4.16-1.mga5-1-1.mga5.i586
  kernel-desktop-devel-latest-4.4.16-1.mga5.i586
  kernel-desktop586-devel-4.4.16-1.mga5-1-1.mga5.i586
  kernel-userspace-headers-4.4.16-1.mga5.i586
  libabw1-0.1.1-2.mga5.i586
  libboost_iostreams1.55.0-1.55.0-8.mga5.i586
  libe-book0.1_1-0.1.1-3.mga5.i586
  liblog4j12-java-1.2.17-7.mga5.noarch
  libmpc3-1.0.2-4.mga5.i586
  libncurses-devel-5.9-21.mga5.i586
  liborcus0.8_0-0.7.0-4.mga5.i586
  libstdc++-devel-4.9.2-4.1.mga5.i586
  libwps0.3_3-0.3.1-8.mga5.i586
  lpsolve-5.5.2.0-7.mga5.i586
  make-4.0-6.mga5.i586
  postgresql-jdbc-9.4.1200-1.mga5.noarch
  x11-driver-video-vboxvideo-5.1.2-1.mga5.i586
  x11-font-type1-1.0.0-12.mga5.noarch
  x11-font-xfree86-type1-1.0.4-5.mga5.noarch
Comment 1 William Kenney 2016-09-17 20:03:44 CEST 
In VirtualBox, M5, KDE, 32-bit

Install media:

Mageia-5.1-i586-DVD.iso
md5sum: 819b10abe4736876df6f1e201e5bd279
Comment 2 William Kenney 2016-09-17 20:06:26 CEST 
Created attachment 8424 [details]
Orphan boot error message
Comment 3 William Kenney 2016-09-18 18:19:25 CEST 
On Real Hardware, M5, KDE, 64-bit

[root@localhost wilcal]# urpme --auto-orphans
To satisfy dependencies, the following 20 packages will be removed (8.3MB):
  
(orphan packages)
  apache-commons-codec-1.9-2.mga5.noarch
  apache-commons-lang-2.6-15.mga5.noarch
  apache-commons-logging-1.1.3-8.mga5.noarch
  geronimo-jms-1.1.1-16.mga5.noarch
  jakarta-commons-httpclient-3.1-15.1.mga5.noarch
  java-1.8.0-openjdk-1.8.0.101-1.b14.1.mga5.x86_64
  javamail-1.5.1-1.mga5.noarch
  lib64abw1-0.1.1-2.mga5.x86_64
  lib64cdr0.1_1-0.1.2-1.mga5.x86_64
  lib64e-book0.1_1-0.1.1-3.mga5.x86_64
  lib64etonyek0.1_1-0.1.1-4.mga5.x86_64
  lib64freehand1-0.1.0-4.mga5.x86_64
  lib64mspub0.1_1-0.1.2-2.mga5.x86_64
  lib64pagemaker0-0.0.2-2.mga5.x86_64
  lib64visio0.1_1-0.1.5-1.mga5.x86_64
  lib64wpd0.10_10-0.10.1-1.mga5.x86_64
  lib64wpg0.3_3-0.3.0-3.mga5.x86_64
  liblog4j12-java-1.2.17-7.mga5.noarch
  x11-font-type1-1.0.0-12.mga5.noarch
  x11-font-xfree86-type1-1.0.4-5.mga5.noarch
  
After orphans are removed system reboots successfully
to a working desktop.
Comment 4 William Kenney 2016-09-18 18:20:49 CEST 
Bottom line here. There should be no orphans immediately
after the install of CI iso.
Comment 5 Marja Van Waes 2016-09-21 16:36:53 CEST 
(In reply to William Kenney from comment #4)
> Bottom line here. There should be no orphans immediately
> after the install of CI iso.

Please attach your /root/drakx/report.bug.xz from that install

Keywords: (none) => NEEDINFO
CC: (none) => marja11

Comment 6 William Kenney 2016-09-21 19:00:49 CEST 
Created attachment 8436 [details]
report.bug.xz zipped
Comment 7 Marja Van Waes 2016-09-22 13:35:31 CEST 
(In reply to William Kenney from comment #6)
> Created attachment 8436 [details]
> report.bug.xz zipped

Thanks (going by the logs, this is from the VBox install - so the one that would no longer boot after removing orphans - and you did no updates at the end of install)

Maybe related (from your logs):

$ grep unselecting report.bug.xz.txt | wc -l
28
$ grep "ERROR: selection failed" report.bug.xz.txt | wc -l
5
$ grep "unknown package" report.bug.xz.txt | wc -l
306

Assigning to the isobuilders

Keywords: NEEDINFO => (none)
Assignee: bugsquad => isobuild
Summary: M5.1 removal of orphans causes system not to boot => M5.1 removal of orphans causes system not to boot (many not found and unselected packages during install)

Comment 8 William Kenney 2016-11-08 04:52:00 CET 
Created attachment 8633 [details]
Orphans list
Comment 9 William Kenney 2016-11-08 04:52:26 CET 
This situation continues but only seems to effect a Vbox client.
I have attached the list of orphans from that client.
Comment 10 Martin Whitaker 2016-11-08 10:14:01 CET 
I suspect this is caused by the missing pre-built vboxvideo kernel modules Thomas mentioned on qa-discuss. Looking in your older ddebug.log, virtualbox-guest-additions gets deselected because of a mismatch between the kernel version and the available pre-built kernel modules, thus orphaning the vboxvideo driver.

CC: (none) => mageia

Comment 11 Martin Whitaker 2016-11-15 23:38:19 CET 
I think this is covered by Luc's list in bug 19518

Keywords: (none) => 5.1
Depends on: (none) => 19518

Comment 12 Martin Whitaker 2016-12-17 09:56:21 CET 
I believe this was fixed in the final release. Please change the resolution if you disagree.

Status: NEW => RESOLVED
Resolution: (none) => FIXED
Note You need to log in before you can comment on or make changes to this bug.