Description of problem: If you go to MCC/Hardware/Printer configuration, the window shows as black on one of my computers. Drop-down menus appear normal, and if you can get it started, printer configuration will work. But when working with the main window, you are working blind. Problem shows with homemade desktop computer, Fujitsu D1711 (Asus number K8V-MX/s) motherboard, Sempron 3100+ processor, 2GB RAM, nVidia Geforce 6200OC AGP video card, using the server kernel, KDE, and proprietary video card driver. Turning off the KDE special effects makes no difference. Changing to the non-proprietary video card driver makes no difference. Mageia 4 installed from the 4.1 classical DVD, and fully updated. Problem does NOT occur with a Dell Dimension E310 desktop, P4 processor, 2GB RAM, on-board Intel graphics, desktop kernel. Mageia 4 installed from the same DVD as above, and is also fully updated. Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: 1. Use MCC to try to configure a printer. 2. 3. Reproducible: Steps to Reproduce:
It shouldn't make any difference with this window, but the printers I was trying to configure, on both the computer that works properly and the one that doesn't, were an HP Deskjet 5650 and an HP Officejet 6110.
OK, now I'm thoroughly confused. I just went to MCC to get a screenshot of the problem window to post here, and it's now working normally! No idea what happened, or why.
Severity: major => minor
Created attachment 5073 [details] Screenshot of drakclock I have the same problem in all mcc modules [root@localhost ~]# drakclock Subroutine Gtk3::main redefined at /usr/lib/perl5/vendor_perl/5.18.2/Gtk3.pm line 293. (drakclock:4117): Gtk-CRITICAL **: _gtk_css_provider_load_named: assertion '!g_str_equal (name, DEFAULT_THEME_NAME)' failed I can reproduce it any time
CC: (none) => dglent
Sorry i have Cauldron (5)
(In reply to Thomas Andrews from comment #2) > OK, now I'm thoroughly confused. I just went to MCC to get a screenshot of > the problem window to post here, and it's now working normally! No idea what > happened, or why. Today I discovered that if I call MCC from the command line as root, the printer configuration window looks as it should. (I did not try sudo.) But, if I call MCC as an ordinary user, either through the command line or the panel icon or the KDE menu, thus invoking the dialog box asking for the root password, the printer configuration window is black. This happens every time on this machine, never on my other one. Whether I use the command "mcc" or /usr/bin/drakconf doesn't seem to matter.
Created attachment 5085 [details] screenshot of black printer configuration window
Both of you don't have same version so please don't mix issue. Thomas, you are using same theme ?
Call me Tom. It's friendlier. I'm using the "Air" theme on all desktops, including the ones that show the problem and the one that doesn't. I am one of the volunteers that are helping to test the upcoming Mageia 4.1 Classic i586 DVD iso, as I have one of the machines that refused to boot the 4.0 DVD. For what it's worth, the Dell computer that wouldn't boot the original 4.0 DVD is also the one that DOESN'T show this bug. The other desktops have shown the problem in all test installs of Mageia 4.1. I believe the one install I performed with Mageia 4.0 also showed the problem, but I can't be sure any more now. I can say that now, with that install being fully updated including the latest kernel update, the bug still shows.
CC: dglent => (none)
Hi Same problem on a fresh 5 beta installed on VirtualBox (but the same problem appear even on all my physical Cauldron installations). The most part of MCC commands show a black windows, sometime with the header and the menu bar. Some commands, like invictus, work correctly the first time I launch it, but after stop working. All the drak* commands work properly if launched outside mcc. Bye Bye, Moreno
CC: (none) => moreno-mg
Hi The problem appear only with KDE4. Installing task-gnome and making login with Gnome, MCC work properly. Bye Bye, Moreno
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/
As announced over a month ago, 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. This issue may have been fixed in a later Mageia release, so, if you still see it and didn't already do so: please upgrade to Mageia 5 (or, if you read this much later than this is written: make sure you run a currently maintained Mageia version) If you are able to reproduce it against a maintained version of Mageia, you are encouraged to 1. reopen this bug report, by changing the "Status" from "RESOLVED - OLD" to "REOPENED" 2. click on "Version" and change it against that version of Mageia. If you know 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. 3. give as much relevant information as possible. If you're not an experienced bug reporter and have some time: please read this page: https://wiki.mageia.org/en/How_to_report_a_bug_properly If you see a similar issue, but are _not_sure_ it is the same, with the same cause, then please file a new bug report and mention this one in it (please include the bug number, too). 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/
Status: NEW => RESOLVEDResolution: (none) => OLD