After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 735447 - g_unix_mount_guess_should_display ignores mount
g_unix_mount_guess_should_display ignores mount
Status: RESOLVED OBSOLETE
Product: glib
Classification: Platform
Component: gio
2.38.x
Other Linux
: Normal normal
: ---
Assigned To: gtkdev
gtkdev
Depends on:
Blocks:
 
 
Reported: 2014-08-26 12:18 UTC by Marius Avram
Modified: 2018-05-24 16:56 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Marius Avram 2014-08-26 12:18:23 UTC 
First of all I'm not sure if the bug is in the selected component or somewhere else. Maybe I can get some help from somebody else regarding that.

I have a custom linux distribution where I use glib-2.38.1 and there seems to be an issue with the discovery of new mounted drives in a file manager using glib (pcmanfm). The function mentioned has not changed since then so the problem is still valid.

I've researched this issue a little bit and I discovered that the drive is mounted under /run/media/sdX. The drive is accessible with a root account but when I use the file manager the drive is not showing up. The main reason is that the above function is expecting a path which should looks something like this:
/run/media/<username>/sdX when in reality the username part is missing.

I could create a patch in which I could overlook the username part if the user_name is root. But is this the desired behavior ?

Otherwise how else can I solve the issue ?
Should I look to the component responsible for creating the mounting path prefix? If yes, which is that component as I'm a bit confused.
Comment 1 GNOME Infrastructure Team 2018-05-24 16:56:28 UTC 
-- GitLab Migration Automatic Message --

This bug has been migrated to GNOME's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/glib/issues/921.