** Changed in: gnome-mount
Status: Confirmed = Expired
** Changed in: gnome-mount
Importance: Unknown = Critical
--
Setting an invalid mount point can make a removeable media unaccessible
https://bugs.launchpad.net/bugs/107668
You received this bug notification because you are a
** Branch linked: lp:ubuntu/gnome-mount
--
Setting an invalid mount point can make a removeable media unaccessible
https://bugs.launchpad.net/bugs/107668
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-volume-manager in ubuntu.
--
** Changed in: gnome-mount
Status: New = Confirmed
--
Setting an invalid mount point can make a removeable media unaccessible
https://bugs.launchpad.net/bugs/107668
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
Can the same fix go into intrepid, and/or hardy if it's affected as
well?
--
Setting an invalid mount point can make a removeable media unaccessible
https://bugs.launchpad.net/bugs/107668
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
OK, I got the patch perfect now. It avoids string changes and error
dialogs, adds the /media/ prefix in glade, and dynamically replaces '/'
with '_'.
** Attachment added: jaunty patch
http://launchpadlibrarian.net/24517846/03_mount_point_configuration.patch
--
Setting an invalid mount point
This bug was fixed in the package gnome-mount - 0.8-1ubuntu5
---
gnome-mount (0.8-1ubuntu5) jaunty; urgency=low
* 02_typos.patch: Add ubuntu/upstream tags.
* Add 03_mount_point_configuration.patch: Point out that mount point is
relative to /media, and replace '/' with '_' in
What about the same problem with mount OPTIONS?
Is that fixed also?
Or should we file a new bug for that?
--
Setting an invalid mount point can make a removeable media unaccessible
https://bugs.launchpad.net/bugs/107668
You received this bug notification because you are a member of Ubuntu
Bazon [2009-03-30 14:03 -]:
What about the same problem with mount OPTIONS?
Is that fixed also?
No, it's not. Writing a validity checker for mount options is a much
bigger task.
Or should we file a new bug for that?
It probably needs to be fixed in an entirely different way, such as
Hi.
I have kindda fixed it. Interpid 64 bit here, changed a bit the glade
xml file to add an icon with a tooltip explaining the mount point is
based on /media/ and changed the code to display an error message if the
user enters a '/' in the Mount Point edit box.
Not sure how to proceed
Will take a look at it soon.
** Changed in: gnome-mount (Ubuntu Jaunty)
Assignee: Ubuntu Desktop Bugs (desktop-bugs) = Martin Pitt (pitti)
Status: Confirmed = In Progress
** Changed in: gnome-mount (Ubuntu Jaunty)
Target: ubuntu-9.04-beta = None
--
Setting an invalid mount
that's not a gnome-volume-manager bug
** Changed in: gnome-mount (Ubuntu)
Importance: Undecided = High
** Changed in: gnome-volume-manager
Importance: Unknown = Undecided
Bugwatch: GNOME Bug Tracker #473492 = None
** Also affects: gnome-mount via
** Changed in: gnome-mount
Status: Unknown = New
--
Setting an invalid mount point can make a removeable media unaccessible
https://bugs.launchpad.net/bugs/107668
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs
Why the hell do maintainers still ignore this bug? There are many
patches attached, plethora of confirmations, but maintainers seem not
to give a damn :-(
On Fri, Feb 13, 2009 at 4:19 PM, Bazon bazonbl...@arcor.de wrote:
Just letting you know:
I also fell into this trap by mis-typing mount
Why the hell do maintainers still ignore this bug? There are many
patches attached, plethora of confirmations, but maintainers seem not
to give a damn :-(
--
Setting an invalid mount point can make a removeable media unaccessible
https://bugs.launchpad.net/bugs/107668
You received this bug
Lukas: I'll prepare a debdiff for a sponsor to upload.
--
Setting an invalid mount point can make a removeable media unaccessible
https://bugs.launchpad.net/bugs/107668
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-volume-manager
thanks luke :-)
--
Setting an invalid mount point can make a removeable media unaccessible
https://bugs.launchpad.net/bugs/107668
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-volume-manager in ubuntu.
--
desktop-bugs mailing
I have no gconf key system/storage/drives/ because I have never changed mount
point of any of drives. But I also have this problem, when I insert ANY usb
flash drive or even SD card, gnome invokes autostart and displays Invalid
mount option when attempting to mount the volume. Note that it does
To fix, open up gconf-editor. The key is under systemvolumes
Remove the trouble key and you will be functioning.
--
Setting an invalid mount point can make a removeable media unaccessible
https://bugs.launchpad.net/bugs/107668
You received this bug notification because you are a member of
Another one who have just fallen into the trap here. This really isn't a
big bug, why not fixing it pronto?
--
Setting an invalid mount point can make a removeable media unaccessible
https://bugs.launchpad.net/bugs/107668
You received this bug notification because you are a member of Ubuntu
Bug still exists in Ubuntu 8.10
--
Setting an invalid mount point can make a removeable media unaccessible
https://bugs.launchpad.net/bugs/107668
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-volume-manager in ubuntu.
--
Running Hardy (8.04) and problem still exists for me.
Thankfully, the solution of editing
/system/storage/volumes/_org_freedesktop_Hal_devices_... and deleting
the stuff worked.
Note: I actually had a slightly different problem than the original bug
report - I put the wrong mount options.
--
Hi,
the attached patch won't let a user set an invalid location. But it need to be
polished a little and localization support should be added (now, the info text
is hardcoded).
** Attachment added: gnome-mount-properties-view-mount-point.patch
Yes, I can confirm the bug in intrepid.
The a problem seems very easy to fix.
btw. another workaround:
1) mount it manually
mkdir /media/tmp
mount /dev/sdletternumeral /media/tmp (e.g. mount /dev/sdb1 /media/tmp)
2) correct the mount point
3) umount/mount using gnome
--
Setting an invalid
Sigh... I was just bitten in the butt by this retardiness ... I
changed my volume mount point to 'XP_HDD' for my Windows mount, umounted
and tried to remount only to be told mount_point cannot contain the
following characters: newline, G_DIR_SEPERATOR (usually /)...
I'm pretty disappointed on 2
I'm on Intrepid and the bug still exists.
Fix the gfconf key wfm
Giovanni
--
Setting an invalid mount point can make a removeable media unaccessible
https://bugs.launchpad.net/bugs/107668
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
I fixed mine by editing /etc/fstab -- it had some permanent entry for
the usb stick. I removed that (sudo gedit /etc/fstab) and that fixed it.
I recommend the above GUI options if you want to be safe. :)
--
Setting an invalid mount point can make a removeable media unaccessible
IF YOU CAN'T ACCESS YOUR EXTERNAL STORAGE DEVICE BECAUSE OF THIS . . .
You are a dopey. Kidding, happend to me as well just now.
Here's what you do;
- Open a terminal.
- Type sudo fdisk -l, and try to recognize what the path to your device is.
HINT : If you just inserted it, it should be the
many thanks to cdaringe (and all those who helped ).
cleared that one up for me!
:D
--
Setting an invalid mount point can make a removeable media unaccessible
https://bugs.launchpad.net/bugs/107668
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
Thanks for starting this. I found this problem difficult to solve and
poorly documented. After spending a good bit of time working out a
couple of approaches to solving the problem I've posted what I think is
a best workaround / solution in the Ubuntu forums at:
Thankyou so much for this post. This bug is so badly documented and
there's so little info on the problem. I'll write a post on my blog and
reference this post when I get a second. Thanks once again.
--
Setting an invalid mount point can make a removeable media unaccessible
I'm hitting this error when mounting one particular USB thumb drive.
However, gconf-editor shows only system|storage||default_options no matter how
I run it.
Is there an alternative method?
--
Setting an invalid mount point can make a removeable media unaccessible
Resolved. dmesg|tail showed a failure on 'check'. I looked at fstab,
found the entry, removed the check instruction. Now it mounts properly
I can access the data on it. Sorry, I forgot about dmesg output sigh
/.
--
Setting an invalid mount point can make a removeable media unaccessible
Looks like something changed... all I have under my /system/storage key
is default_options, and this has nothing that seems to refer to the
problem. Searching in gconf-editor have so far turned up zilch.
Anybody have an idea?
--
Setting an invalid mount point can make a removeable media
OK, nevermind. I assumed you had to be root to do this, but actually
the volumes settings will NOT show up unless you run as user.
--
Setting an invalid mount point can make a removeable media unaccessible
https://bugs.launchpad.net/bugs/107668
You received this bug notification because you are
I've got the same problem. I don't know what I did, but a fat32 partition
became impossible to mount, as described above. I'v followed your advices and
now everything is ok.
Being a recent user of linux, I must say that I'm very impressed with the way
you face problems. Thank you very much!
OK, this last comment from cdaringe on 2008-05-09 fixed my problem -
thank you! I'm an Ubuntu noob trying to do some, what I thought were,
simplistic things. I got trapped by attempting to change the volume
mount point, as described. Then spent the better part of a day, reading
forum posts,
Hi fellers,
To baby those who are onlookers in desperate search of a solution (i'm
running Hardy)...
open a terminal.
type gconf-editor
click your way to /system/storage/volumes/_org_freedesktop_Hal_devices_...
you should now see mount point, and its value
You can do something here and get your
Hi,
I am also facing this problem with the Huawei E270 device after
upgrading to Ubuntu 8.04 LTS.
However, I am not sure what I should do after reading Joachim's
solution... do I simply delete the whole key and replace it with the
word, foo? Or just replace the phrase, /mount_point, with foo?
Thanks to everyone on the post who helped me work around the same issue
(using Ubuntu 8.04 LTS), particularly Joachim and Bhavash.
--
Setting an invalid mount point can make a removeable media unaccessible
https://bugs.launchpad.net/bugs/107668
You received this bug notification because you are
I confirm this bug un Ubuntu 8.04 LTS.
For those who can't mount any drive i suggest editing with gconf the key
/system/storage/volumes/_org_freedesktop_Hal_devices_voume_uuid_*/mount_point
as stated by Joachim Sauer
--
Setting an invalid mount point can make a removeable media unaccessible
I confirm this bug in Ubuntu 8.04-beta
--
Setting an invalid mount point can make a removeable media unaccessible
https://bugs.launchpad.net/bugs/107668
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-volume-manager in ubuntu.
--
fillibar, the _ issue you mention is bug 101845 (most likely).
--
Setting an invalid mount point can make a removeable media unaccessible
https://bugs.launchpad.net/bugs/107668
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
I was able to restore access to my drive, but noticed something that is
still an issue... When I enter disk (no quotes) in gconf it appears as
disk_... There is no /, and no end of line characters...
--
Setting an invalid mount point can make a removeable media unaccessible
** Changed in: gnome-volume-manager
Status: Unknown = New
--
Setting an invalid mount point can make a removeable media unaccessible
https://bugs.launchpad.net/bugs/107668
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
Not a g-v-m bug.
** Changed in: gnome-volume-manager (Ubuntu)
Status: New = Invalid
** Bug watch added: GNOME Bug Tracker #473492
http://bugzilla.gnome.org/show_bug.cgi?id=473492
** Also affects: gnome-volume-manager via
http://bugzilla.gnome.org/show_bug.cgi?id=473492
Another way to correct the mount point, apart from using gconf-editor,
is to manually mount the partition from the command line, so that the
drive and volume properties are accessible from nautilus again via right
clicking.
--
Setting an invalid mount point can make a removeable media
Hey Alex Wilkes,
A little late for you, but hopefully it will help other people.
If you can't find the key
/system/storage/volumes/_org_freedesktop_Hal_devices_voume_uuid_*/mount_point
You are running 'gconf-editor' as root. (it doesn't exist if you run it as
root).
Run 'gconf-editor' as
That shouldn't happen. Mounting a disk twice is very evil, and it shuold
not be possible with the GUI tools. You can do it manually as root, of
course, but then you are on your own.
--
Setting an invalid mount point can make a removeable media unaccessible
https://bugs.launchpad.net/bugs/107668
thanks Martin Pitt,
if the USB disk mounted twice i.e on /media and /home/blah-blah/usb, is the
program work corectly??
--
Setting an invalid mount point can make a removeable media unaccessible
https://bugs.launchpad.net/bugs/107668
You received this bug notification because you are a member
hi,
Mahyuddin Susanto [2007-07-23 13:39 -]:
so if we can unmount volume we must close all apps from system??
No, you just need to close all files which are stored on the volume
you are going to unmount.
--
Setting an invalid mount point can make a removeable media unaccessible
Hi Tolan,
Tolan Blundell [2007-07-22 12:50 -]:
Do these changes only take effect after the drive is manually remounted
(via hotplug for USB devices I presume)?
Yes. Changing the mount point on the fly is tricky at best, and could
confuse/crash applications.
--
Setting an invalid mount
hi Martin Pitt,
so if we can unmount volume we must close all apps from system??
--
Setting an invalid mount point can make a removeable media unaccessible
https://bugs.launchpad.net/bugs/107668
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug
Do these changes only take effect after the drive is manually remounted
(via hotplug for USB devices I presume)? If so this should probably be
made clear also. The layout of the tab implied to me that gnome would do
whatever was necessary to make the change when I close the dialogue.
--
Setting
I can't locate this key:
/system/storage/volumes/_org_freedesktop_Hal_devices_voume_uuid_*/mount_point
gconf in root or my user doesnt show the volumes folder, only default
options.
any ideas?
--
Setting an invalid mount point can make a removeable media unaccessible
I have the same problem, when I insert a DVD disc. This is the error
message: Cannot mount volume. Invalid mount option when attempting to
mount the volume 'Lemezem'.
How can I use the patch for it? THANKS.
-phoenix-
--
Setting an invalid mount point can make a removeable media unaccessible
Nicolas,
thanks for your initial work. First, some comments to the patch so far:
- gtk_editable_get_chars() (just like all glib/gtk functions) already
return a copy of the string, no need to copy it again. So you can
simplify the loop like Mikele said.
Just for some bikeshedding, I think
First i have change the Mount Point: label to be clear im attaching
the patch for the .glade
It use to say: Mount point:
Now it says: Mount point in /media:
** Attachment added: E:\gnome-mount-0.5-glade.patch
http://launchpadlibrarian.net/8153081/E%3A%5Cgnome-mount-0.5-glade.patch
--
thanks to nicolas for trying to make the interface less misleading; while you
are at it, if you discover why specifying additional mount options causes the
mount to fail, no matter what the option format, please post it here! (I
understand that probably this would be a bit more hard than
ok, i will check it, now i'm trying to check the string, and if it has
/ send a warning and replace it with _.
--
Setting an invalid mount point can make a removeable media unaccessible
https://bugs.launchpad.net/bugs/107668
You received this bug notification because you are a member of Ubuntu
i'm attaching a new patch, i'm not sure about it, please check it and
correct. I'm not really comfortable with C
** Attachment added: patch
http://launchpadlibrarian.net/8156007/gnome-mount-0.5.patch
--
Setting an invalid mount point can make a removeable media unaccessible
seems fine. is there a reason why you create a copy of the string?
text = gtk_editable_get_chars (editable, 0, -1);
char *p;
p=text;
while (*p) { if (*p=='/') *p='_'; ++p; }
should work as well, if textorig is not needed anywhere else
cheers
michele
On Thu, 2007-06-21 at 22:50 +, Nicolas
I will try to make a patch to validate the data and not to permit /
values when i have my ubuntu on hands :D
--
Setting an invalid mount point can make a removeable media unaccessible
https://bugs.launchpad.net/bugs/107668
You received this bug notification because you are a member of Ubuntu
i think gnome-volume-manager isn't the right package, the properties
menu is from other package i think nautilus i will keep searching
--
Setting an invalid mount point can make a removeable media unaccessible
https://bugs.launchpad.net/bugs/107668
You received this bug notification because you
** Changed in: gnome-mount (Ubuntu)
Sourcepackagename: gnome-volume-manager = gnome-mount
--
Setting an invalid mount point can make a removeable media unaccessible
https://bugs.launchpad.net/bugs/107668
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
I'm kinda new around here, can anyone help me to fix this bug?
Thanks,
HA
--
Setting an invalid mount point can make a removeable media unaccessible
https://bugs.launchpad.net/bugs/107668
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug contact
** Tags added: bitesize
--
Setting an invalid mount point can make a removeable media unaccessible
https://bugs.launchpad.net/bugs/107668
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug contact for gnome-volume-manager in ubuntu.
--
with me its not an external drive but an internal one and it shows in the ls:
[EMAIL PROTECTED]:~$ ls -l /dev/disk/by-id
insgesamt 0
lrwxrwxrwx 1 root root 9 2007-05-29 12:21
ata-HL-DT-ST_DVDRAM_GSA-H10A_B272E4589C57 -
../../hdc
lrwxrwxrwx 1 root root 9
Same as above gconf-editor corrected this as discribed
--
Setting an invalid mount point can make a removeable media unaccessible
https://bugs.launchpad.net/bugs/107668
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug contact for
I confirm the bug on Feisty. I regard this as a serious problem. I also
agree that the Settings section of the Drive and Volume tabs is
unusable. What does File System stand for?
--
Setting an invalid mount point can make a removeable media unaccessible
https://bugs.launchpad.net/bugs/107668
You
I confirm the bug on Feisty.
I can add that the whole volume properties dialog is prone to lock up the
drive, and
poorly documented at best.
I tried to change the default mount options
(it is mounting my ext3-formatted external HD noexec, and that's definitely
not what I'd want to),
I cannot
I confirm the bug on Feisty.
I can add that the whole volume properties dialog is prone to lock up the
drive, and
poorly documented at best.
I tried to change the default mount options
(it is mounting my ext3-formatted external HD noexec, and that's definitely
not what I'd want to),
I cannot
I've noticed this behavior on my Feisty 7.04 install. To recreate this
problem for yourself, do the following:
1) Connect a USB storage device (or any device that creates a drive icon on
the desktop)
2) Right-click the desktop icon for the device once the system has mounted it
and click
Thanks,
That fixed it for me. Plus, now that I know about gconf-editor, I've
got a new toy to mess with.
Jim Montgomery
2nd BCT FSR, Ft Stewart, GA
912-313-5978
[EMAIL PROTECTED]
Joachim Sauer wrote:
It's a gconf key. You'll have to use a tool such as gconf-editor to find
and edit it.
Where's the referenced key?
/system/storage/volumes/_org_freedesktop_Hal_devices_voume_uuid_*/mount_point
I've been digging through my system looking for it but not having any luck.
I've got an external harddrive that's pretty much useless right now because I
tried to change it's mount point.
It's a gconf key. You'll have to use a tool such as gconf-editor to find
and edit it.
--
Setting an invalid mount point can make a removeable media unaccessible
https://bugs.launchpad.net/bugs/107668
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a
Thank you for your report. I can confirm this at an up-to-date feisty amd64.
I think the first point you mentioned is a bug(if you aren't familiar
computers, you wouldn't be able to solve it)
The second point is more a wish list, although it is a sort of backup safety.
** Changed in:
76 matches
Mail list logo
