From: Ricardo Wurmus <rekado@elephly.net>
To: Christopher Baines <mail@cbaines.net>
Cc: 34124@debbugs.gnu.org
Subject: bug#34124: gnome-shell crash when opening the activities overview
Date: Tue, 23 Apr 2019 14:10:09 +0200 [thread overview]
Message-ID: <87sgu86hy6.fsf@elephly.net> (raw)
In-Reply-To: <874la6mb0u.fsf@cbaines.net>
Christopher Baines <mail@cbaines.net> writes:
> On one system running GuixSD, Gnome Shell crashes when opening the
> activities overview (super key, or clicking on the activities button in
> the top left).
>
>
> (.gnome-shell-real:2471): GLib-GIO-CRITICAL **: 10:36:30.639: g_file_new_for_path: assertion 'path != NULL' failed
>
> (.gnome-shell-real:2471): GLib-GIO-CRITICAL **: 10:36:30.639: g_loadable_icon_load: assertion 'G_IS_LOADABLE_ICON (icon)' failed
>
> (.gnome-shell-real:2471): Gtk-WARNING **: 10:36:30.639: Could not load a pixbuf from icon theme.
> This may indicate that pixbuf loaders or the mime database could not be found.
> **
> Gtk:ERROR:gtkicontheme.c:4261:gtk_icon_info_load_icon_finish: assertion failed: (icon_info_get_pixbuf_ready (icon_info))
Could you try to see if setting LD_LIBRARY_PATH in the environment where
GNOME Shell is launched to the lib directory of the “gdk-pixbuf+svg” (or
“gdk-pixbuf”) package makes any difference?
You may need to do this in ~/.xsession and launch the gnome-session
manually.
--
Ricardo
next prev parent reply other threads:[~2019-04-23 12:24 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-18 11:59 bug#34124: gnome-shell crash when opening the activities overview Christopher Baines
2019-04-23 12:01 ` Ben Sturmfels
2019-04-23 12:10 ` Ricardo Wurmus [this message]
2019-04-23 20:33 ` Christopher Baines
2019-04-24 4:07 ` Ben Sturmfels
2019-04-24 6:47 ` Christopher Baines
2019-04-24 11:34 ` Ben Sturmfels
2019-04-25 13:20 ` Ricardo Wurmus
2019-04-25 13:23 ` Ben Sturmfels
2019-04-28 10:28 ` swedebugia
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=87sgu86hy6.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=34124@debbugs.gnu.org \
--cc=mail@cbaines.net \
/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.