bug#50742: spacefm crash on launch

bug#50742: spacefm crash on launch

[bdju via Bug reports for GNU Guix]

guix (GNU Guix) 9057035d892266c1b90242d06522a642e13b09d79
I am running Guix System

Here is the output after running `spacefm` from my terminal
------------------------------------------------------------------------

(spacefm:28620): SpaceFM-WARNING **: 13:43:17.110: No root settings
found in
/gnu/store/cb0mdkpb2a3x1sylfhkhb8g228hs43cp-spacefm-1.0.6/etc/spacefm/
Setting a root editor in Preferences should remove this warning on
startup.   Otherwise commands run as root may present a security risk.
**
GLib:ERROR:../glib-2.62.6/glib/ghash.c:472:g_hash_table_lookup_node:
assertion failed: (!g_atomic_ref_count_compare (&hash_table->ref_count,
0))
Bail out!
GLib:ERROR:../glib-2.62.6/glib/ghash.c:472:g_hash_table_lookup_node:
assertion failed: (!g_atomic_ref_count_compare (&hash_table->ref_count,
0))
zsh: abort      spacefm
------------------------------------------------------------------------

When launching with ‘guix environment --pure --ad-hoc spacefm --
spacefm’ instead, it appears successfully.

bug#50742: spacefm crash on launch

[ison]

Are you using Wayland? If so then there is a workaround. Try launching
it like "WAYLAND_DISPLAY= spacefm" (notice the space). Spacefm doesn't
support Wayland natively.
A similar file manager that does support Wayland is Thunar.

"bdju" via Bug reports for GNU Guix <bug-guix@gnu.org> writes:

> guix (GNU Guix) 9057035d892266c1b90242d06522a642e13b09d79
> I am running Guix System
>
> Here is the output after running `spacefm` from my terminal
> ------------------------------------------------------------------------
>
> (spacefm:28620): SpaceFM-WARNING **: 13:43:17.110: No root settings
> found in
> /gnu/store/cb0mdkpb2a3x1sylfhkhb8g228hs43cp-spacefm-1.0.6/etc/spacefm/
> Setting a root editor in Preferences should remove this warning on
> startup.   Otherwise commands run as root may present a security risk.
> **
> GLib:ERROR:../glib-2.62.6/glib/ghash.c:472:g_hash_table_lookup_node:
> assertion failed: (!g_atomic_ref_count_compare (&hash_table->ref_count,
> 0))
> Bail out!
> GLib:ERROR:../glib-2.62.6/glib/ghash.c:472:g_hash_table_lookup_node:
> assertion failed: (!g_atomic_ref_count_compare (&hash_table->ref_count,
> 0))
> zsh: abort      spacefm
> ------------------------------------------------------------------------
>
> When launching with ‘guix environment --pure --ad-hoc spacefm --
> spacefm’ instead, it appears successfully.

bug#50742: spacefm crash on launch

[bdju via Bug reports for GNU Guix]

On Mon Oct 18, 2021 at 9:10 AM CDT, ison wrote:
> Are you using Wayland?
Yes, I am on Sway.
> If so then there is a workaround. Try launching
> it like "WAYLAND_DISPLAY= spacefm" (notice the space). Spacefm doesn't
> support Wayland natively.
This works! Thanks.
> A similar file manager that does support Wayland is Thunar.
I'm all-set for a file manager. I just noticed this problem while
comparing several of them and their performance. I believe pcmanfm,
pcmanfm-qt, thunar, caja, and dolphin all worked okay on Wayland. At the
least they didn't crash on launch.

I guess it sounds like this is an upstream bug then. Not sure if this
should be closed or not. I'll leave that up to someone else to decide.

bug#50742: spacefm crash on launch

[Maxim Cournoyer]

Hello,

"bdju" <bdju@tilde.team> writes:

> On Mon Oct 18, 2021 at 9:10 AM CDT, ison wrote:
>> Are you using Wayland?
> Yes, I am on Sway.
>> If so then there is a workaround. Try launching
>> it like "WAYLAND_DISPLAY= spacefm" (notice the space). Spacefm doesn't
>> support Wayland natively.
> This works! Thanks.
>> A similar file manager that does support Wayland is Thunar.
> I'm all-set for a file manager. I just noticed this problem while
> comparing several of them and their performance. I believe pcmanfm,
> pcmanfm-qt, thunar, caja, and dolphin all worked okay on Wayland. At the
> least they didn't crash on launch.
>
> I guess it sounds like this is an upstream bug then. Not sure if this
> should be closed or not. I'll leave that up to someone else to decide.

I agree; it's an upstream bug.

Thanks for the report!

Closing.

Maxim