From: ison <ison@airmail.cc>
To: bdju <bdju@tilde.team>
Cc: 50742@debbugs.gnu.org
Subject: bug#50742: spacefm crash on launch
Date: Mon, 18 Oct 2021 08:10:32 -0600 [thread overview]
Message-ID: <87wnma2yaz.fsf@airmail.cc> (raw)
In-Reply-To: <CEGNLVZQCH70.P2SPGEWBVK7J@masaki>
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.
next prev parent reply other threads:[~2021-10-18 14:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-22 19:17 bug#50742: spacefm crash on launch bdju via Bug reports for GNU Guix
2021-10-18 14:10 ` ison [this message]
2021-10-18 20:33 ` bdju via Bug reports for GNU Guix
2022-02-06 2:31 ` Maxim Cournoyer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87wnma2yaz.fsf@airmail.cc \
--to=ison@airmail.cc \
--cc=50742@debbugs.gnu.org \
--cc=bdju@tilde.team \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.