gnome-vfs2 should fall back to mount if it cannot execute pmount

[Mikel Ward]

After inserting then burning a CD-RW, GNOME still shows the drive containing a
blank CD in the "Computer" location of the file manager. When I try to click on
the drive to view the CD's contents, I get an error message box saying

Unable to mount the selected volume.
>More
Error: could not execute pmount

Yet I can still access the files on the disk using

mount /cdrom

It seems that Ubuntu Breezy now requires that desktop users belong to the
plugdev group to mount removable media. Since my passwords are on a remote
authentication/user directory server, I guess the upgrade to base-config etc.
didn't add me as I would have hoped.

This isn't documented anywhere I could find, so I thought I'd file it here.
Also added it to the BreezyUpgrade wiki.

[Martin Pitt (pitti)]

(In reply to comment #0)
> After inserting then burning a CD-RW, GNOME still shows the drive containing a
> blank CD in the "Computer" location of the file manager.

This is a known issue; many CD-ROMs don't automatically reload their status
after buring, and that is the reason why nautilus-cd-burner defaults to ejecting
the CD after buring.

> It seems that Ubuntu Breezy now requires that desktop users belong to the
> plugdev group to mount removable media.

This has been the case since Warty.

> Since my passwords are on a remote
> authentication/user directory server, I guess the upgrade to base-config etc.
> didn't add me as I would have hoped.

This is independent from the upgrade. plugdev and its semantics did not change
since Warty. Please change your authentication server to export correct group
memberships.

> This isn't documented anywhere I could find, so I thought I'd file it here.

The user administration tool, section "Privileges" has this item. It is also
part of the "Desktop" profile (which is the default for users created with
users-admin).

> Also added it to the BreezyUpgrade wiki.

That's inappropriate, it has nothing to do with the Breezy upgrade itself (see
above). However, I could not find anything related to this in the wiki anyway.

[Mikel Ward (mikelward)]

The CD's status was incorrect even after ejecting and reinserting!

I am sure user mounting of devices was working for me the last time I tried it,
which was probably only a week or two before upgrading. I had been tracking
Breezy, so it seems likely this was a recent change. My user was never in the
plugdev group until the problem occurred yesterday and I discovered I would need
to add it.

You seem adamant that this cannot have happened, but it did!

[Martin Pitt (pitti)]

(In reply to comment #2)
> The CD's status was incorrect even after ejecting and reinserting!
>
> I am sure user mounting of devices was working for me the last time I tried it,
> which was probably only a week or two before upgrading. I had been tracking
> Breezy, so it seems likely this was a recent change.

There indeed was; before that change, gnome-vfs incorrectly used mount instead
of pmount.

> My user was never in the
> plugdev group until the problem occurred yesterday and I discovered I would need
> to add it.

Ok, to clean this up:

 - Users who want to use removable devices are supposed to be in the plugdev
group. It just works (or rather worked) for CD-ROMs since /cdrom is usually in
the fstab.

 - I agree that this is a bit inconsistent, so I'll change gnome-vfs2 to fall
back to mount if it cannot execute pmount.

[Martin Pitt (pitti)]

*** Bug 23770 has been marked as a duplicate of this bug. ***

[azteech (stevep.)]

(In reply to comment #4)
> *** Bug 23770 has been marked as a duplicate of this bug. ***

Not sure how you can consider 17607 a duplicate of this bug report -

Specifically the part that I am concerned about is the reported error, which
definetly differs from that which is reported in 18394.

    Unable to mount the selected volume.
    Error: given UDI is not a mountable volume

Additionally, in Bug 23770, I reported I am able to automount and use a audio or
data CD in the CD-RW drive (master drive on IDE2), but when I place the same
disk(s) in the DVD-ROM drive, I always get the above error.

The fact that there is no problem with automounting CD-RW, yet the DVD-ROM can't
be automounted, and fact the error messages don't match, would seem to me to
indicate to entirely seperate, but (what may be) parallel issues.

And while I feel the original bug report(17607) got side tracked (hijacked) by
other, seperate issues, the fact remains I don't see the connection between
17607 and 18394.

And for my future knowledge, how can a higher reported bug #, cancel out a
earlier one. If a reported bug is to be considered a duplicate, shouldn't the
earlier reported one (in this case, 17607) be considered the valid one, and
follow-on reported bugs be considered duplicates?

[Martin Pitt (pitti)]

(In reply to comment #5)
> (In reply to comment #4)
> > *** Bug 23770 has been marked as a duplicate of this bug. ***
>
> Not sure how you can consider 17607 a duplicate of this bug report -

This was just a typo, sorry. I reopened #17607 a while ago.

> And for my future knowledge, how can a higher reported bug #, cancel out a
> earlier one. If a reported bug is to be considered a duplicate, shouldn't the
> earlier reported one (in this case, 17607) be considered the valid one, and
> follow-on reported bugs be considered duplicates?

I generally close the bug that has fewer information/log attachments to have the
most "useful" and general bug stay open. The bug number itself is rather
uninteresting.

[Martin Pitt (pitti)]

I will fix this in pmount-hal, thus this bug becomes a duplicate of bug 33232.