blur-my-shell
blur-my-shell copied to clipboard
bug on startup with multiple monitors with different resolutions
only occurs on 1440p from what I've seen
i think this issue caused by a delay in the startup of my main montior
enable() {
const checkMonitors = () => {
const allMonitorsConnected = Main.layoutManager.monitors.every(
monitor => monitor.is_connected() && monitor.is_primary()
);
if (!allMonitorsConnected) {
// If not all monitors are connected, wait and check again
this._log("Not all monitors are on and connected. Waiting...");
Mainloop.timeout_add_seconds(1, checkMonitors);
return;
}
// All monitors are on and connected, proceed with enabling the blur
this._log("All monitors are on and connected. Blurring top panel.");
// Rest of the enable method...
this.enabled = true;
};
// Start the initial check
checkMonitors();
}
something in panel.js like this might fix it
I am having the same issue on my 2560x1080 monitor
Is it connected to a laptop
Is it connected to a laptop
Nope, RTX 3060 Desktop. I have a secondary monitor running on 1920x1200.
One gpu ? Right and does the montior that has the problem turn on later
One gpu ? Right and does the montior that has the problem turn on later
2 GPUs, but only the RTX 3060 is used for displays, the GT 1030 is not used for driving the monitors.
I can't really tell, but my graphics card initializes the ultrawide monitor first, dunno about Linux
I'm starting to think this issue is related to having multiple montiors with different resolutions
I am also experiencing this issue on Fedora 39 with Gnome 45.2. And I can confirm that I'm on a dual screen setup (with my laptop and one external display). Display is connected to a dock, which in turn goes through Thunderbolt to the laptop.
Laptop: 2256x1504 Monitor: 1920x1080
It happens right after I login (on my main display, which is my external 1080p display), but will go away if I lock the screen and sign back in again.
I have 3 monitors ( 2 monitors 2560x1440, 1 monitor 1920x1200). If I have all three enabled, I have this issue. If I disable the smaller monitor, everything is ok.
following tickets are all related: #517 #513 #476
@aunetx not sure if you have seen this issue or not i mentioned this to you while 45 was being worked on
@RyzenDew yes, sorry for the silence... The problem is I don't have another monitor to test the changes I might do to correct this, but this week I may have one so if I find time, I will try to fix this (among other things)!
@aunetx I have this issue as well, should you need a tester, hmu :)
did some further testing with display arrangements while logging out to reset the extension
this arrangement results in an issue:
while this does not:
Hello, could you try runnning blur-my-shell from the PR #546? I changed the way multiple monitors are managed so it should be better (maybe, I couldn't test it on multiple monitors hehe)
pulled from master; reverted patch for gnome 46 as I run gnome 45; problem still exists as mentioned by OP
Yep. Having the same issue. I have the exact same setup as @coralof although I'm on Arch Linux + GNOME 46.1.
Happens to me as well on Gnome 46.1, latest version of the extension.
Here is my layout, main display is 3440x1440, secondary display is 1080x1920.
I'm also having this issue. I'm using Ubuntu 24.04 (GNOME 46). Using extension version 62. When I was using Ubuntu 22.04 (GNOME 42), extension version 47, this wasn't happening, if it helps at all. This is my layout:
I ran a few tests using different layouts, screenshots were taken from the primary monitor, hope it helps (and that GitHub doesn't destroy the table):
LAYOUT | RES 1 | RES 2 | RESULT |
---|---|---|---|
1080x1920 | 1920x1080 | ||
720x1280 | 1920x1080 | ||
1920x1080 | 1920x1080 | ||
1080x1920 | 1920x1080 | ||
1080x1920 | 1920x1080 |
Seems to me, at least on my 2 monitor setup, that the width info is always coming from the leftmost monitor. But I don't know the inner workings of the extension so can't say for sure.
A quick way I found to reproduce the issue (besides logging out and in again) is to switch which monitor is the primary. Whenever I go from (1) to (2) (in my case) the panel gets wonky again.
Also, like some of the others mentioned, the problem can be temporarily fixed by turning the extension off and on again.
the last update (v64) made this issue worse. It cannot be fixed by reloading the plugin anymore. It's now consistently broken