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 722692 - g_volume_mount() on non-mountable entry from /etc/fstab causes 100% CPU load.
g_volume_mount() on non-mountable entry from /etc/fstab causes 100% CPU load.
Status: RESOLVED DUPLICATE of bug 724916
Product: glib
Classification: Platform
Component: gio
2.38.x
Other Linux
: Normal major
: ---
Assigned To: gtkdev
gtkdev
Depends on:
Blocks:
 
 
Reported: 2014-01-21 13:30 UTC by A.G.
Modified: 2014-04-10 19:09 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
Test application. (1.50 KB, text/x-csrc)
2014-01-21 13:31 UTC, A.G. 		Details

Description A.G. 2014-01-21 13:30:08 UTC 
The attached file is a GTK application source to help testing the issue. After pressing "test" button it will try to mount all unmounted volumes. If volume cannot be mounted (the simplest example is an entry for /dev/cdrom without medium inserted) then g_volume_mount_finish() should return FALSE and finish the operation. But it returns TRUE instead and leaves pipes open which causes unstoppable loop in g_main_loop_run(). Tested with GLib 2.36.4, 2.38.2, and GVFS 1.12.3, 1.16.3, 1.18.3 on Debian testing and on FC20, the same issue was reported on Arch and on Ubuntu as well:
https://bbs.archlinux.org/viewtopic.php?pid=1268411
https://bugs.launchpad.net/ubuntu/+source/pcmanfm/+bug/913273
Comment 1 A.G. 2014-01-21 13:31:10 UTC 
Created attachment 266868 [details]
Test application.
Comment 2 Ross Lagerwall 2014-04-10 19:09:40 UTC 
Glib handles mounting stuff from fstab, not gvfs.

This has actually been fixed now in bug 724916.
Also see bug 726122.

Thanks!

*** This bug has been marked as a duplicate of bug 724916 ***