Description of problem: Hi! Fresh install of Mageia 9 (Gnome). All looks very nice, i like it. But when i open a window related with mcc, it is totally in black. Thank you very much, in advance. Version-Release number of selected component (if applicable): Mageia 9 How reproducible: Openining any window related with the package managing Steps to Reproduce: 1. tiping rpmdrake from the terminal 2. clicking "Install apps..." icon on the Apps menu. 3.
Created attachment 14377 [details] screenshot showing the bug
Are you using the standard theme for the Desktop Environment? Can you recreate the issue with a new user account that also logs in to the same DE?
CC: (none) => lovaren
(In reply to Kristoffer Grundström from comment #2) > Are you using the standard theme for the Desktop Environment? Can you > recreate the issue with a new user account that also logs in to the same DE? 1- Yes. I'm using the standard theme for Mageia 9 Gnome. 2- New user account created, and the bug reproduces equally. Thanks, very much.
After the Kristoffer questión i'd remain thinking... than i always did login this the default session, Gnome (Wayland). So, i did a try the Gnome Xorg posibility, and Voila!!!, all windows working perfectly without problems. Anyway, still a bug to resolv in Xwayland, i think. Hoping be useful with the developing of the distro. Regards and Thanks.
This is maybe an item for errata. Thank you reporting and for the workaround. Yes we should try to fix this for Wayland anyway. Have you updated your system? What GPU and driver? - please post the output of $ inxi -G
Keywords: (none) => FOR_ERRATA9CC: (none) => fri
(In reply to Morgan Leijström from comment #5) > This is maybe an item for errata. > Thank you reporting and for the workaround. > Yes we should try to fix this for Wayland anyway. > > Have you updated your system? > I do 2 or 3 sudo urpmi --auto-update per day. > What GPU and driver? - please post the output of > $ inxi -G $ inxi -G Graphics: Device-1: VMware SVGA II Adapter driver: vmwgfx v: 2.20.0.0 Display: wayland server: X.Org v: 22.1.9 with: Xwayland v: 22.1.9 compositor: gnome-shell v: 44.2 driver: X: loaded: v4l,vmware dri: vmwgfx gpu: vmwgfx resolution: 1920x1080~60Hz API: OpenGL v: 4.1 Mesa 23.3.3 renderer: SVGA3D; build: RELEASE; LLVM; $
Does this also happen on bare metal or only in this Virtualbox installation?
(In reply to sturmvogel from comment #7) > Does this also happen on bare metal or only in this Virtualbox installation? The only Linux that i can get for now is this virtual installation. No othe way.
I wonder if this may be a variant of Bug 32185, which is in https://wiki.mageia.org/en/Mageia_9_Errata#Mageia_tools It is seen on some systems (i.e my workstion occasionally) cause not known... --- I dont know if it may help graphics, but anyway: is virtualbox-guest-additions installed? https://wiki.mageia.org/en/VirtualBox#On_guests That page also say "Starting with Mageia 9, for Plasma systems the 3D acceleration must be enabled. " - Even this is not Plasma, maybe try that? And increase graphics memory to max.
Summary: Totally black window for the Mageia Control Center => Totally black window for the Mageia Control Center in Gnome on VirtualBoxSee Also: (none) => https://bugs.mageia.org/show_bug.cgi?id=32185
I use Plasma with Mageia 8. Quite often I get a totally black window for a number of apps. The remedy then has been just to minimize it and then maximize it. When that happens to a menu instigated by right click, just click elsewhere and redo. Worse is it when the wallpaper turns totally black. In that case I could not think of anything but re-login or reboot, but instead I wanted to see what would happen, and after 2-3 days the wallpaper all of a sudden just came back by itself after a lock screen, which was not the first lock screen. As time passed about a short week later, without reboot nor re-login, the wallpaper for the same one of my four displays turn all black again.
CC: (none) => ole.reier.ulland
Reconfiguring the wallpaper makes no difference.
@Ole: would be interesting to see if still so on your system if upgraded to mga9. And mga9 is getting a Plasma update soon. @Jose: As I wrote in the referenced bug, I occasionally get MCC right panel white, but that is often remedied by closing firefox (I often have a hundred tabs...) and/or thunderbird or more, then mcc display correctly, so maybe it is a side effect of scarce resource of some kind. Does closing apps help in your case?
(In reply to Morgan Leijström from comment #12) > @Ole: would be interesting to see if still so on your system if upgraded to > mga9. And mga9 is getting a Plasma update soon. > > @Jose: As I wrote in the referenced bug, I occasionally get MCC right panel > white, but that is often remedied by closing firefox (I often have a hundred > tabs...) and/or thunderbird or more, then mcc display correctly, so maybe > it is a side effect of scarce resource of some kind. Does closing apps help > in your case? Hi Morgan, Good day!. My problem must be different than yours. If you see the image attached to the bug report, i get a window almost totally in black. Plus, i don't have Firefox or any other window open, i run the program directly from the grid of apps, clicking the icon. Plus, my problem occurs only with the Wayland session, and not occurs with Xorg, i think this can be important for solve it. You are very kind, Man. Thank you very much.
There are many informations and reports available (Virtualbox upstream) regarding Wayland support. Host with Wayland is no problem. But guest with wayland still leads often to graphic issues ...
Entered at https://wiki.mageia.org/en/Mageia_9_Errata#As_a_VirtualBox_Guest together with other edits regarding Wayland there above. I think we can close this bug as wontfix - meaning not solving for VB Guest + Wayland problems.
Keywords: FOR_ERRATA9 => IN_ERRATA9, UPSTREAMStatus comment: (none) => It is known to be issues with Wayland in VB guests
Eventually the area on my displays that turned all black came to be the panel. In that situation it was impossible to keep operating the computer of course. It so happened that I did not need the computer for a few days, so I shut it down. Since I turned it back on about four days ago I have not seen the problem manifest itself. I hope it just was a random error. If it was not the only thing I can think of that may have cause it is the same that generated this message that I never understood, "Inotify Instance Capacity Low - You have too many applications wanting to monitor file changes! When the capacity is exhausted it will prevent further file monitoring from working correctly. Either close some applications or increase the limit. Currently using 93% of instances and 0% of watches."
(In reply to Ole Reier Ulland from comment #16) > Eventually the area on my displays that turned all black came to be the > panel. In that situation it was impossible to keep operating the computer of > course. It so happened that I did not need the computer for a few days, so I > shut it down. Since I turned it back on about four days ago I have not seen > the problem manifest itself. I hope it just was a random error. Likely just restarting X would have fixed it. > If it was not the only thing I can think of that may have cause it is the > same that generated this message that I never understood, "Inotify Instance > Capacity Low - You have too many applications wanting to monitor file > changes! When the capacity is exhausted it will prevent further file > monitoring from working correctly. Either close some applications or > increase the limit. Currently using 93% of instances and 0% of watches." I've never seen that. [dave@x3 ~]$ ll /proc/sys/fs/inotify/max* -rw-r--r-- 1 root root 0 Feb 23 10:47 /proc/sys/fs/inotify/max_queued_events -rw-r--r-- 1 root root 0 Feb 23 10:47 /proc/sys/fs/inotify/max_user_instances -rw-r--r-- 1 root root 0 Feb 22 12:33 /proc/sys/fs/inotify/max_user_watches [dave@x3 ~]$ cat /proc/sys/fs/inotify/max* 16384 128 524288 # sysctl -a|grep inotify fs.inotify.max_queued_events = 16384 fs.inotify.max_user_instances = 128 fs.inotify.max_user_watches = 524288 user.max_inotify_instances = 128 user.max_inotify_watches = 524288 You can probably increase those limits if needed with a new file in /etc/sysctl.d/ that sets the values to higher numbers.
CC: (none) => davidwhodgins
By me it says now "256" in the three places where it says "128" by Dave Hodgins. But that is after I selected the "Increase Instance Limit" option underneath the message I quoted above.
It's probably showing up now due to a large number of tabs open in firefox or another browser. With 17 tabs open, I currently have 23 threads running firefox due to it's sandboxing each tab.
What is the current status after updates? See bug 32185 Comment 53