Crash in refresh_search

[akashashen]

Describe the bug

*** Actual Log ***

../src/exm-backtrace.c:107 'exm_backtrace_print'
../src/main.c:42 'handler'
2 frames omitted
../src/exm-browse-page.c:161 'refresh_search'
5 frames omitted
../src/local/exm-manager.c:778 'on_state_changed'
7 frames omitted
../src/local/shell-dbus-interface.c:2756 'shell_extensions_proxy_g_signal'
11 frames omitted
../src/main.c:110 'run_app'
2 frames omitted
../sysdeps/x86_64/start.S:115 '_start'

System Information:

Version: 0.5.1
Package Format: Flatpak
Status: Official
OS: GNOME 46 (Flatpak runtime)
GTK: 4.14.5
Libadwaita: 1.5.4

Additional context

Possibly related for environmental (and maybe bug) context:
For some reason, GDM has been making me login twice. I turn on the view password to make sure I didn't make a mistake, and when I hit enter, the login part disappears, but a two to three seconds later, GDM always restarts before letting me actually log in.
Since that started happening, I've always had to re-enable extensions after logging in.

[oscfdezdz]

Which distro and GNOME Shell version are you using?

If you have to re-enable the extensions after logging in, it is most likely that one of the extensions you have installed is causing the problem. Try disabling them one by one and reproduce the crash.

[akashashen]

Sorry, I didn't intend to take this long.
Gnome 47 on
Wayland on
Debian Sid with
kernel 6.10.12 amd64

At least, that's what I'm on at this moment. A similar error came up since this was true, but I didn't have time to follow up on it. I am still having to log into gdm3 at least twice. And on two occasions, it just kept resetting after multiple times. Logging in via a t2 terminal may have allowed a successful log in on both occasions. I purged gdm3, installed lightdm, purged lightdm and reinstalled gdm3, but I am still logging in twice after a boot (problem does not persist if I log out and log in.) Additionally, logging in usually means having to turn the extensions on after a boot (but again, not on a log out and log back in.)

Like I said before, I don't know how much of that might be related; so, I thought sharing it may help.

[akashashen]

I'm assuming this is related.
Minor note: So, having had success after logging in on a terminal, I did try doing so when the GDM3 restarted twice. But afterwards, I still had to do the gdm3 login twice (just in case they are related, which is my current theory, but it's not dev I'm familiar with in the modern gtk/gnome way...but, I'm pretty sure this is an authentication layer issue, at least, gdm-wise...which sets the environment that gnome yada yada yada.)

Like I said earlier,, I had an error that I didn't follow up on. This may be it. The difference is I'm on the the rt kernel amd64 6.10.11. It is a general kernel patch behind (12), but that one isn't loading sound, and switching kernels at reboot is just schway easier.

Error Log:

../src/exm-backtrace.c:107 'exm_backtrace_print'
../src/main.c:42 'handler'
2 frames omitted
../src/exm-browse-page.c:161 'refresh_search'
5 frames omitted
../src/local/exm-manager.c:778 'on_state_changed'
7 frames omitted
../src/local/shell-dbus-interface.c:2756 'shell_extensions_proxy_g_signal'
11 frames omitted
../src/main.c:110 'run_app'
2 frames omitted
../sysdeps/x86_64/start.S:115 '_start'

[oscfdezdz]

Is this crash still reproducible with version 0.6?

[akashashen]

I do not have access to this system at this time; so, I probably will not be able to test the setup for another month. I'll leave the email highlighted for when I can check.

On Wednesday, January 8, 2025, Óscar Fernández Díaz < ***@***.***> wrote: Is this crash still reproducible with version 0.6? — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread.<

https://ci3.googleusercontent.com/meips/ADKq_NZ7DCTxY4CnYtqWeSb808njIDyBT1H7Ah1ceWszxDBftpwtsLnQqbWLTt3P08h4xmIE8rzGT6x5yep2waQvFu23LTv-aDIARktmKkiE0c0wus9Z_g3KQ6fjpvF0cPYQZyKuyYSwORgbd3F76GJvM6L9JTrhCNy7fodFPgcRTBKewCjTfR4UdFEHPT5GZm0fFLXJyPJvDMfQdcTIaQzd0AJkj6TsVcJBRH3XdTkqkvdbXIwqJsUYGKc=s0-d-e1-ft#https://github.com/notifications/beacon/AFFQ3ZOA43YFJBROIO2PU2T2JWB5NA5CNFSM6AAAAABO7MGEICWGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTUZWH4B2.gif>Message ID: ***@***.***>