Hello
After booting, firefox and thunderbird are auto starting. If i switch to thunderbird (either by tab-key or by application menu) the window blinks up for a second, than vanishes. I can’t use firefox either, cause the input focus remains on Thunderbird (I think so, but obviously can’t test it). It is not a thunderbird problem, cause from time to time it’s the same with firefox.
Only help is to kill thunderbird in the application menu and start it over. Then everything is fine.
My system: updated Manjaro stable, GNOME Shell 46.4, Kernel 6.10.6-10, Thunderbird 115.14.0, firefox 130.0.
Any ideas?
Probably try to switch the backend renderer to OpenGL:
GSK_RENDERER=gl
1 Like
Hi Megavolt
Doesn’t help. Verified by ‘echo GSK_RENDERER’ that its switched to gl.
And verified by 'ctrl+tab’bing that the focus stays on thunderbird, despite not seeing its window.
But thanks für trying!
By vanishing, do you mean it’s invisible? I use Sway, which also works with Wayland. Firefox and Thunderbird become transparent/invisible for me after a long session or after a long suspending. It still takes up the space as if it were open. Sometimes it refreshes itself automatically and it appears again. So it seems to stop rendering to save cpu/gpu time. I have no tabbing function here, so cannot reproduce your problem with Gnome.
“Loosing” is not a word. It is spelled “losing.”
“Loose” is an adjective meaning the opposite of “tight.”
“Lose” is a verb that can mean to misplace, or the opposite of win.
2 Likes
Humour me for a moment…
Are you certain that you’re not simply shifting focus somehow and inadvertantly sending Thunderbird to another virtual desktop?
Thunderbird would then seem to vanish…
It also irks me when I see that something is… “stucked”.
Hi all
Vanishing means exactly “going invisible”. When i open the application menu, i see the thunderbird window next to the firefox window (so no virtual desktop problem ;o) )
With ctrl+tab i switch through the tabs inside thunderbird eg. calendar, mails in tabs. that works even if i can’t see the window. But I can see the result in the small thunderbird window inside the application menu.
so yes, it’s invisible, but still has the focus.
Window manager is standard, Mutter 46.4.
I’ve seen now: gdm is 46.2. Could this be the problem? pacman tells me it’s the newest version…
echo $XDG_SESSION_TYPE
echo $MOZ_ENABLE_WAYLAND
Probably try starting thunderbird/firefox with MOZ_ENABLE_WAYLAND=1 if Wayland is running, otherwise it will run with X-Wayland on Wayland.
$XDG_SESSION_TYPE
=> x11
$MOZ_ENABLE_WAYLAND
=> undefined
$MOZ_ENABLE_WAYLAND=1 changes nothing. XDG_SESSION_TYPE bleibt bei x11.
Sure, you have to switch the gnome-session to wayland on the login screen. It will just enable the possibility to use the native wayland compositor instead of Xorg only. But I guess you use an NVIDIA card or a virtual machine? If that is the case, then you are out of luck. Both are blocked for reasons.
Yes, i have an nvidia card.
I was giving your issue some more thought and remembered an issue I had once with a LibreOffice app, and with another that I don’t recall as I type.
I’ll preface this by saying I don’t know what caused it…
However, the app window wasn’t invisible at all; it was just ridiculously small. I noticed a brief flash of pixels on screen; only a few pixels wide and about 40/60px high.
The application window was indeed open and responding to all focus actions as expected – it was just too small to notice it.
I was able to use the mouse to select an edge of these pixels mentioned, and drag it until the entire application window was finally revealed.
This could well be what you are experiencing also, and seems to tick all the boxes of what you have described.
Open Thunderbird, and look for those pixels. Look carefully, as (at least for me) it was seriously difficult to recognise what I was seeing, at first.
I find nothing unusual in the Firefox Window. Also the thunderbird window is displayed in the application menu with its full content.
If you got an little window in the application menu, it should contain just the small content it has in real size, or no?
If you re-read my comments you will see that application window was mentioned and not application menu.
Again, the application window – the entire visible application – had shrunk almost to nothing; only a few pixels high/wide in dimensions.
I will not attempt to justify this beyond that which I have already described; and I do not know what caused it.
Once I had determined that I could simply drag the edges of the window to restore it to a usable (and visible) size, I then forgot to follow up on the issue.
Again, this had nothing to do with the application menu; but it does seem to fit your previous description.
If this is what is happening in your situation, only you can determine.
Cheers.
Did you use a multimonitor setup and stopped using the second monitor?
A long time ago I koticed that obe window disappeard after disconnecting a second monitor. And it seemed that it was outside the bounda of the monitor. I don’t remember how I solved it though
@soundofthunder: when i wrote “window”, i meant “application window”. I mentioned the application menu, because it seams to me, that its behavior makes your described error unprobably. (besides the fact, that i can’t find the small pixel area…)
@Erim: i never had a second monitor.
Today’s experience showed that it is no thunderbird Problem: this boot-up firefox shows the same behavior as thunderbird: the Desktop was empty, switching to firefox flashes the firefox-window to the screen and empty Desktop again.
After restarting both programs, everything is fine.
I’ll set further Programs to autostart for testing.
The problem left the building when i start more than two programs at boot-time. It didn’t occur the last three days with several bootings.
So everything is fine now, but i can’t find any sense in this…
Thanks for your help!
Should i mark this as a solution? Feels not apropriate…
It’s not, really, but in the absence of anything definitive there’s little choice. I’ve taken the liberty of marking it for you (which, of course, you can change if you wish).
I’m guessing (and it’s only a guess) that it may have been connected (but not directly related) to the issue in the recent Stable Update announcement, which Start with a new session seemed to solve. Subsequent reboots might have simply cured it.
Cheers.