By default, Bugzilla does not search the list of RESOLVED bugs.
You can force it to do so by putting the upper-case word ALL in front of your search query, e.g.: ALL tdelibs
We recommend searching for bugs this way, as you may discover that your bug has already been resolved and fixed in a later release.
Bug 2429 - tdeio_media_mounthelper missing mountpoint in error dialog
Summary: tdeio_media_mounthelper missing mountpoint in error dialog
Status: NEW
Alias: None
Product: TDE
Classification: Unclassified
Component: tdebase (show other bugs)
Version: R14.0.x [Trinity]
Hardware: Other Linux
: P5 trivial
Assignee: Timothy Pearson
URL:
Depends on:
Blocks: 2968
  Show dependency tree / graph
 
Reported: 2015-04-23 19:02 CDT by Kristopher
Modified: 2018-08-30 02:52 CDT (History)
3 users (show)

See Also:
Compiler Version:
TDE Version String:
Application Version:
Application Name:

Attachments
Screenshot of bug being reported (21.28 KB, image/png)
2015-04-23 19:02 CDT, Kristopher 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Kristopher 2015-04-23 19:02:34 CDT 
Created attachment 2487 [details]
Screenshot of bug being reported

When unmounting/safely removing a media device that fails, I see a dialog that says:

Unfortunately, the device system:/media/<devicenode> (/dev/<device node>) name '<device name>' and currently mounted at could not be unmounted.

(second part omitted because it's not important to the bug)

The error is in the sentence: according to the dialog, the device is currently mounted at "could not be unmounted.", which is obviously not a valid mount point.
Comment 1 Slávek Banko 2015-04-23 19:13:19 CDT 
I believe that this is a typo and instead of "at could not be unmounted" should be "and could not be unmounted".
Comment 2 Kristopher 2015-04-23 19:47:31 CDT 
That would change it to say:

Unfortunately, the device system:/media/<devicenode> (/dev/<device node>) name '<device name>' and currently mounted and could not be unmounted.

IIRC, it actually put the mount point between "and currently mount at" and "could not be unmounted" in 3.5.13.x (though it's been awhile since I used the old 3.5 branch, so my memory may be accurate).