blur-my-shell icon indicating copy to clipboard operation
blur-my-shell copied to clipboard

Published 20 hours ago • verified publisher icon aunetx

Instability and gnome-shell crashing on log-in and when starting blur my shell Gnome 44 - Fedora 38

Open brend-an opened this issue 2 years ago • 5 comments
trafficstars

Blur my Shell is causing instability on Gnome 44 in Fedora 38, launching the extension causes a log-out and gnome-shell crash. I'm not sure how to find this information in the logs. Even starting the extension in Extension Manager causes a shell crash.

gnome-shell[4389]: segfault at 5584ff09c000 ip 00007fc9699da675 sp 00007fff8d458e40 error 4 in libst-12.so[7fc9699a3000+5a000] likely on CPU 0 (core 0, socket 0)

brend-an avatar May 13 '23 13:05 brend-an

log messages.txt Here are the logs on boot. It seems to hang a bit while it tries to find the background.

brend-an avatar May 14 '23 01:05 brend-an

I came here to report the same issue. It started happening to me in Fedora 37 and has persisted in 38. It only happens to me when logging in though.

stpnwf avatar May 14 '23 20:05 stpnwf

I'm also getting this issue too, when I change my wallpaper to one prepackaged with gnome it seems to go away. Perhaps it has something to do with the dynamic wallpaper?

EDIT: nevermind that doesn't fix it.

melody-rs avatar Jun 07 '23 21:06 melody-rs

Same issue here. Random crashes while logging in w/ gnome 44.2 wayland on arch. I disabled the extension and have had no crashes.

EDIT: I've re-installed the extension, and disabled everything except for the overview blur. I haven't noticed a crash yet, but I'll update if I do.

EDIT (sequel): Still facing occasional crashes on X11 (nvidia). Much less than before though. Loads just fine without extensions

KCGD avatar Jun 12 '23 00:06 KCGD

I just wanted to chime in and say that I've experienced instability and crashes as well. I can live with it being (momentarily) unstable when enabling. However, being forced to logout after a screen lock and then to be met with all my extensions being disabled is a bit much.

At first I didn't even know which of the extensions was causing it, the first time I was suspicious of blur-my-shell was when I disabled all my extensions and proceeded to enable them one-by-one. Everything was fine until I enabled the blur-my-shell extension. While this was suspicious, it could be that another one only started acting up randomly and it happened to be triggered when I enabled the blur-my-shell extension. However, the past two-weeks I've been using all my other extensions without the blur-my-shell extension and my experience has been flawless.

throwaway43 avatar Sep 22 '23 15:09 throwaway43