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 619892 - GVolumeMonitor takes down GVolumes with it
GVolumeMonitor takes down GVolumes with it
Status: RESOLVED OBSOLETE
Product: glib
Classification: Platform
Component: gio
2.25.x
Other Linux
: Normal normal
: ---
Assigned To: gtkdev
gtkdev
Depends on:
Blocks:
 
 
Reported: 2010-05-28 01:28 UTC by Michael Terry
Modified: 2018-05-24 12:20 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
Test program (791 bytes, text/x-csrc)
2010-05-28 01:28 UTC, Michael Terry 		Details

Description Michael Terry 2010-05-28 01:28:59 UTC 
Created attachment 162160 [details]
Test program

I had a nasty bug [1] appear in my program seemingly as a result of a change in GIO right before Ubuntu 10.04 was released.  I worked around it, but am following up with a GIO bug here.

It seems that when the global GVolumeMonitor is unref'd (as the documentation requests), it somehow partially invalidates GVolume objects it has handed out.  Specifically, the GVolume objects it gave out no longer give out GMount objects.

I'm not being very clear.  But the attached test program should be more obvious.

The test program searches for a GVolume from the Monitor.  Then it asks that GVolume for a GMount.  As expected, it works at first.  But then, if the GVolumeMonitor is unref'd, the GVolume no longer gives out a GMount object.  That is not something I would expect, and I assume it's a bug.

Compile the attached program like so:
gcc `pkg-config gio-2.0 --libs --cflags` test.c -o test

[1] https://bugs.launchpad.net/deja-dup/+bug/569418
Comment 1 GNOME Infrastructure Team 2018-05-24 12:20:22 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/304.