Description of problem: After clean vm install from mga5b2 live kde dvd I ran urpme --auto-orphans which removed 40 packages, with no apparent ill-effects, testing FF, LibreOffice, Dolphin. I did not check mcc at this point. I then updated from current repos and then tried to use rpmdrake. It opens to a black screen. Running in a terminal: [baz@localhost ~]$ mcc "/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. Subroutine Gtk3::main redefined at /usr/lib/perl5/vendor_perl/5.20.1/Gtk3.pm line 296. getting exclusive lock on urpmi I will re-test later without running auto-orphans. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Reproducible: Steps to Reproduce:
Black screen is unrelated to auto-orphans or update. In clean VM install from live DVD without update rpmdrake has black screen.
Not sure if it is related, but I have always got DrakConf & rpmdrake black and mostly unusable screen after Mageia Cauldron minimal install with X. Workaround is to install oxygen-gtk3...
CC: (none) => jyri2000
(In reply to Jüri Ivask from comment #2) > Not sure if it is related, but I have always got DrakConf & rpmdrake black > and mostly unusable screen after Mageia Cauldron minimal install with X. > Workaround is to install oxygen-gtk3... Not helping here. I have it installed and still get the black screen when launched via mcc. Works fine if I launch rpmdrake from the command line. Since no one else complained about it, I assumed it was my fault for running with vendor files instead of Mageia VirtualBox packages in a guest. No problems running in the host.
CC: (none) => junknospam
Package oxygen-gtk3-1.4.1-2.mga5.x86_64 is already installed in my VM and this persists.
Duplicate of https://bugs.mageia.org/show_bug.cgi?id=11969 *** This bug has been marked as a duplicate of bug 11969 ***
Status: NEW => RESOLVEDResolution: (none) => DUPLICATE