From: paper42 <paper42@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: GLIB problems
Date: Thu, 06 Oct 2022 11:31:26 +0200 [thread overview]
Message-ID: <20221006093126.HOxsoDRpIlRhxPpI4wqxuZ642bvE0A1yPYd_5MbPnKY@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-39752@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1344 bytes --]
New comment by paper42 on void-packages repository
https://github.com/void-linux/void-packages/issues/39752#issuecomment-1269681090
Comment:
> ### gvfs
>
> thunar report the gvfs was not work currectly, and there's no vols appear in left panel of thunar. for tracering the issue, all of them report an GLIB error. for example , this is the report of gvfs debug , using comomand `GVFS_DEBUG=1 $(find /usr/lib* -name gvfsd 2>/dev/null) --replace 2>&1 | tee gvfsd.log ` :
>
> ```
>
> (process:14320): GLib-GObject-CRITICAL **: 11:21:21.921: g_object_new_with_properties: assertion 'G_TYPE_IS_OBJECT (object_type)' failed
>
> (process:14320): GLib-GIO-CRITICAL **: 11:21:21.924: g_volume_monitor_get_mounts: assertion 'G_IS_VOLUME_MONITOR (volume_monitor)' failed
>
> (process:14320): GLib-GObject-WARNING **: 11:21:21.924: invalid (NULL) pointer instance
>
> (process:14320): GLib-GObject-CRITICAL **: 11:21:21.924: g_signal_connect_data: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed
>
> (process:14320): GLib-GObject-WARNING **: 11:21:21.924: invalid (NULL) pointer instance
>
> (process:14320): GLib-GObject-CRITICAL **: 11:21:21.924: g_signal_connect_data: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed
> ```
These errors seem to only be because you forgot to set GIO_MODULE_DIR=/usr/lib/gio/modules.
next prev parent reply other threads:[~2022-10-06 9:31 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-06 5:04 [ISSUE] " superiums
2022-10-06 6:06 ` sgn
2022-10-06 6:07 ` sgn
2022-10-06 8:11 ` oreo639
2022-10-06 8:12 ` oreo639
2022-10-06 8:12 ` sgn
2022-10-06 8:12 ` oreo639
2022-10-06 8:13 ` oreo639
2022-10-06 8:13 ` oreo639
2022-10-06 8:14 ` oreo639
2022-10-06 8:15 ` oreo639
2022-10-06 8:15 ` oreo639
2022-10-06 8:17 ` oreo639
2022-10-06 8:22 ` oreo639
2022-10-06 8:22 ` oreo639
2022-10-06 9:31 ` paper42 [this message]
2022-10-06 11:56 ` superiums
2022-10-08 12:09 ` superiums
2022-10-21 10:17 ` superiums
2022-10-22 4:32 ` superiums
2022-10-22 4:35 ` superiums
2022-12-13 7:11 ` sgn
2022-12-13 7:12 ` sgn
2022-12-13 7:14 ` sgn
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=20221006093126.HOxsoDRpIlRhxPpI4wqxuZ642bvE0A1yPYd_5MbPnKY@z \
--to=paper42@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).