Unclickable area in the screen - Solus 4.1 Budgie edition

GustiStereo

Hello, I have this weird problem that started a few days back. I reinstalled Solus 4.1 (upgraded the PC) last Friday (July 10th) and everything was going fine until Tuesday, when I first noticed it.

Somehow, there is an area in the screen that becomes "unclickable" (Don't know how to call it). The mouse won't interact with anything there, no right/left click, no scroll, no menus, no selection of objects, no drag-n-drop ( I tried to drag an icon of the desktop into that area).

I have attached a screen capture to show you the approximate area of where it happens. Note that it also affects a portion of the items in the menu-bar.

It seems to be like a layer that stays on top of everything. However, it will not affect the Budgie Menu because it stays on top level. So, I can click everywhere on it, drag or scroll in the menu over that "dead area" and it is not affected at all.

I haven't find a solution yet, but if I close the session and log in again, the problem is gone. Buuut... It could happen again, but not always.

Although I wasn't able to identify what may have trigger it yet, I’ve noticed there is one element that seems to be on top of everything (except the Budgie menu, of course) and it's the area for the notification messages, which happens to be in that corner.

Does anyone else had this problem (or similar) before? It may be really annoying after a while.

Please, let me know if you need further details that I can provide.

algent

I moved my panel on the right, and I don't have that strange behavior like you. Usually at that place I use conky, do you use any?

GustiStereo

algent Hi, I'm not using anything else besides the Budgie Menu with Icon Task List enabled. I have been using the panel in that position since Solus 3.8 (or 3.7, cannot remember) and after several updates it upgraded to Solus 4.1 with the current version of Budgie, I guess.

synth-ruiner Interesting because I reinstalled Solus due to a hardware change, so I will consider to check that.
That's mainly the current configuration:
AMD® Ryzen 3 3200g with radeon vega graphics × 4
Mother ASUS Prime B450M-A
Kingston DDR4 2x 8GB 2400 GHz

sangheeta I have to discard the option of Rhythmbox, dind't used it yet, although it's installed by default. However, I will have to check the behavior of the notifications for different apps. So long, most of the notifications came from the system, like available updates.

synth-ruiner

same problem here. I logged the issue a while ago: https://github.com/solus-project/budgie-desktop/issues/1956

I think it probably only affects particular hardware, since I've used Budgie on at least half-a-dozen computers and this one is the only one I've had this problem with...

I don't really have any suggestions- I've just switched to using Openbox instead of Budgie for the time being.

sangheeta

I've had this problem too, it looks like it's the notification area. It also seems that this problem appeared to me after Rythmbox opened. I don't use it anymore because I replaced it with GmusicBrowser, this dead zone doesn't manifest anymore since then.

synth-ruiner

sangheeta that's interesting, I'll have to try a different music player and see if the problem persists!

synth-ruiner

I've switched back to Budgie. yesterday I avoided Rhythmbox and I haven't encountered the problem so far. this computer is the only one I use Rhythmbox on, so perhaps it's that, rather than a hardware issue. I'll keep you posted.

GustiStereo

synth-ruiner Thanks for the update.

I have some new observations also. This morning when I logged in it started with the problem. That made me think that it may have no relation with notifications, because there wasn't any message, it just started with that.

So, I did the only solution I have so far which is log out / log in. However, after the second login I did have a system notification which was about available updates.

The thing is, the software updates were available yesterday also, but I only applied the required and security ones and let the others for later. It means that the notification should have been visible in the first login this morning, but it wasn't the case. So my best guess it that the problem is about a notification that popped out but wasn't displayed and since you cannot accept/dismiss the message that invisible layer will stays there, because it cannot be closed.