Bug 14616 - Attempt to use mcc to manage disk partitions fails
Summary: Attempt to use mcc to manage disk partitions fails
Status: RESOLVED INVALID
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 5
Hardware: x86_64 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords: NEEDINFO
Depends on:
Blocks:
 
Reported: 2014-11-20 16:53 CET by Jim Beard
Modified: 2016-06-05 14:16 CEST (History)
3 users (show)

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


Attachments
Current error output to cli (1.10 KB, text/plain)
2015-11-18 16:44 CET, Jim Beard
Details

Description Jim Beard 2014-11-20 16:53:11 CET
Attempt to use mcc > local disks > manage disk partitions fails with a Warning, This program has exited abnormally.

Mcc run from the command line as root yields the following after manage disk partitions is clicked on in the gui:

[root@jdb ~]# LC_ALL=C
[root@jdb ~]# mcc
LOG **: NP_Initialize at /usr/lib/libDrakX/mygtk2.pm line 589.
LOG **: NP_Initialize succeeded at /usr/lib/libDrakX/mygtk2.pm line 589.
LOG **: NP_Initialize at /usr/lib/libDrakX/mygtk2.pm line 589.
LOG **: NP_Initialize succeeded at /usr/lib/libDrakX/mygtk2.pm line 589.
LOG **: NP_Initialize at /usr/lib/libDrakX/mygtk2.pm line 589.
LOG **: NP_Initialize succeeded at /usr/lib/libDrakX/mygtk2.pm line 589.
LOG **: NP_Initialize at /usr/lib/libDrakX/mygtk2.pm line 589.
LOG **: NP_Initialize succeeded at /usr/lib/libDrakX/mygtk2.pm line 589.
java version "1.7.0_71"
OpenJDK Runtime Environment (mageia-2.5.3.1.mga4-x86_64 u71-b14)
OpenJDK 64-Bit Server VM (build 24.65-b04, mixed mode)
"/usr/sbin/drakmenustyle" is not executable [Menus] at /usr/libexec/drakconf line 831.
"/usr/sbin/drakbackup" is not executable [Backups] at /usr/libexec/drakconf line 831.
"/usr/sbin/tomoyo-gui" is not executable [Tomoyo Policy] at /usr/libexec/drakconf line 831.
"/usr/sbin/drakguard" is not executable [Parental Controls] at /usr/libexec/drakconf line 831.
Too late to run INIT block at /usr/lib/perl5/vendor_perl/5.18.1/x86_64-linux-thread-multi/Glib/Object/Introspection.pm line 257.
Subroutine Gtk3::main redefined at /usr/lib/perl5/vendor_perl/5.18.1/Gtk3.pm line 296.
mkdir: error creating directory /proc/bus/usb: No such file or directory

This may be related to Bug 10062, which also involved /proc/bus/usb.

System is Mageia 4.1 newly installed over Mageia 3 on a generic desktop with cpu an Intel i7 870.
urpmq --not-available turns up 74 rpm packages, mostly /lib64 rpms and old kernels.
urpmq --auto-orphans turns up 156 rpm packages, including most or maybe all of the lib64 and kernel rpms, plus a duplicate:
 lib64llvmradeon9.1.3-9.1.3-1.1.mga3.tainted.x86_64
 lib64llvmradeon9.1.7-9.1.7-1.1.mga3.tainted.x86_64

Months ago I installed Mageia 4 as a clean install on a Gateway with an AMD Athlon dual-core cpu, and that system fully updated is working fine when I use mcc to manage disk partitions.
Comment 1 Rémi Verschelde 2014-12-01 20:07:12 CET
CC'ing Thierry.

CC: (none) => remi, thierry.vignaud
Component: New RPM package request => RPM Packages
Source RPM: (none) => drakxtools

Comment 2 Thierry Vignaud 2015-05-19 14:26:43 CEST
Please attach (not paste) the "mga3.txt" file resulting from running the following command:
rpm -qa |grep -v mga4|sort > /tmp/mga3.txt

Keywords: (none) => NEEDINFO

Comment 3 Samuel Verschelde 2015-09-21 13:21:53 CEST
Mageia 4 changed to end-of-life (EOL) status on 2015-09-19. It is is no longer 
maintained, which means that it will not receive any further security or bug 
fix updates.

Package Maintainer: If you wish for this bug to remain open because you plan to 
fix it in a currently maintained version, simply change the 'version' to a later 
Mageia version.

Bug Reporter: Thank you for reporting this issue and we are sorry that we weren't 
able to fix it before Mageia 4's end of life. If you are able to reproduce it 
against a later version of Mageia, you are encouraged to click on "Version" and 
change it against that version of Mageia. If it's valid in several versions, 
select the highest and add MGAxTOO in whiteboard for each other valid release.
Example: it's valid in cauldron and Mageia 5, set to cauldron and add MGA5TOO.

Although we aim to fix as many bugs as possible during every release's lifetime, 
sometimes those efforts are overtaken by events. Often a more recent Mageia 
release includes newer upstream software that fixes bugs or makes them obsolete.

If you would like to help fixing bugs in the future, don't hesitate to join the
packager team via our mentoring program [1] or join the teams that fit you 
most [2].

[1] https://wiki.mageia.org/en/Becoming_a_Mageia_Packager
[2] http://www.mageia.org/contribute/
Jim Beard 2015-09-21 17:35:50 CEST

Version: 4 => 5
Whiteboard: (none) => MGA4TOO

Comment 4 Jim Beard 2015-11-18 16:44:23 CET
Created attachment 7209 [details]
Current error output to cli
Comment 5 Marja Van Waes 2016-02-17 20:56:22 CET
(In reply to Thierry Vignaud from comment #2)
> Please attach (not paste) the "mga3.txt" file resulting from running the
> following command:
> rpm -qa |grep -v mga4|sort > /tmp/mga3.txt

@ Jim

It seems you missed that request. Please do it now, but slightly different:

Please attach (not paste) the "mga-not5.txt" file resulting from running the following command:
rpm -qa |grep -v mga5|sort > /tmp/mga-not5.txt

CC: (none) => marja11
Whiteboard: MGA4TOO => (none)

Comment 6 Marja Van Waes 2016-06-05 14:16:26 CEST
Closing as invalid, because the requested information has not been given.

Sorry Jim :-(

Please reopen and supply that informtion, if this bug is still valid in Mageia 5,

Status: NEW => RESOLVED
Resolution: (none) => INVALID


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