| 2008-11-20 20:41:28 |
KevinM |
bug |
|
|
added bug |
| 2008-11-20 20:41:28 |
KevinM |
bug |
|
|
added attachment '.xsession-errors' (logfile) |
| 2008-11-22 00:08:41 |
Linuxfreak78 |
None: status |
New |
Confirmed |
|
| 2008-11-22 00:08:41 |
Linuxfreak78 |
None: statusexplanation |
|
|
|
| 2008-11-22 16:47:42 |
Kjell Braden |
None: importance |
Undecided |
Medium |
|
| 2008-11-22 16:47:42 |
Kjell Braden |
None: bugtargetdisplayname |
Ubuntu |
ntfs-3g (Ubuntu) |
|
| 2008-11-22 16:47:42 |
Kjell Braden |
None: bugtargetname |
ubuntu |
ntfs-3g (Ubuntu) |
|
| 2008-11-22 16:47:42 |
Kjell Braden |
None: statusexplanation |
|
Hal seems to reject the partition because the fstype is ntfs and gnome is trying to mount it via ntfs-3g.
The best solution to this would probably be adjusting /usr/share/hal/fdi/policy/10osvendor/20-ntfs-3g-policy.fdi to...
- append 'ntfs-3g' to volume.fstype.alternative
- append 'locale=' and 'exec' to volume.mount.ntfs-3g.valid_options
You can test that this works by running:
sudo hal-set-property --udi /your/UDI/to/your/ntfs/device --key volume.fstype.alternative --strlist-post ntfs-3g
sudo hal-set-property --udi /your/UDI/to/your/ntfs/device --key volume.mount.ntfs-3g.valid_options --strlist-post locale=
sudo hal-set-property --udi /your/UDI/to/your/ntfs/device --key volume.mount.ntfs-3g.valid_options --strlist-post exec
Since I'm rather unfamiliar with FDIs I suggest someone else should have a look at this. |
|
| 2008-11-22 16:47:42 |
Kjell Braden |
None: title |
Bug #300443 in Ubuntu: "[Jaunty] Unable to mount NTFS partitions" |
Bug #300443 in ntfs-3g (Ubuntu): "[Jaunty] Unable to mount NTFS partitions" |
|
| 2008-11-22 16:52:21 |
Kjell Braden |
description |
Using Jaunty kernel 2.6.27-7 64 bit with latest updates (but not Alpha1).
I'm able to access any ext3 and FAT32 partitions on my PC, but when I try to access NTFS partitions I get an error.
If I go to Places-Computer and select an NTFS drive I get "Cannot mount volume. Unable to mount the volume 'Data Drive'. Details Cannot get volume.fstype.alternative" followed by "Opening "Data Drive"" and then "DBus error org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken."
If I go to Places-Removable Media I get the first and last message but no "Opening "Data Drive".
This error occurs on all three of my NTFS partitions.
My ntfs drive files are as follows:
dpkg -l | grep ntfs
ii libntfs-3g28 1:1.2506-1ubuntu2 ntfs-3g filesystem in userspace (FUSE) libra
ii libntfs-3g31 1:1.2531-1.1ubuntu1 ntfs-3g filesystem in userspace (FUSE) libra
ii ntfs-3g 1:1.2531-1.1ubuntu1 read-write NTFS driver for FUSE
I include my .xsession-errors file as they seems to be problems reported there. |
TEST CASE:
gnome-mount -vnbtd /dev/your_ntfs_partition
fails with "Cannot get volume.fstype.alternative"
NEXT STEP:
Verify fix proposal in https://bugs.launchpad.net/ubuntu/+source/ntfs-3g/+bug/300443/comments/4
Fix "debian/20-ntfs-3g-policy.fdi".
--- old description follows ---
Using Jaunty kernel 2.6.27-7 64 bit with latest updates (but not Alpha1).
I'm able to access any ext3 and FAT32 partitions on my PC, but when I try to access NTFS partitions I get an error.
If I go to Places-Computer and select an NTFS drive I get "Cannot mount volume. Unable to mount the volume 'Data Drive'. Details Cannot get volume.fstype.alternative" followed by "Opening "Data Drive"" and then "DBus error org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken."
If I go to Places-Removable Media I get the first and last message but no "Opening "Data Drive".
This error occurs on all three of my NTFS partitions.
My ntfs drive files are as follows:
dpkg -l | grep ntfs
ii libntfs-3g28 1:1.2506-1ubuntu2 ntfs-3g filesystem in userspace (FUSE) libra
ii libntfs-3g31 1:1.2531-1.1ubuntu1 ntfs-3g filesystem in userspace (FUSE) libra
ii ntfs-3g 1:1.2531-1.1ubuntu1 read-write NTFS driver for FUSE
I include my .xsession-errors file as they seems to be problems reported there. |
|
| 2008-11-22 16:52:21 |
Kjell Braden |
title |
[Jaunty] Unable to mount NTFS partitions |
hal rejects to mount ntfs-3g partition |
|
| 2008-11-22 16:52:34 |
Kjell Braden |
ntfs-3g: status |
Confirmed |
Triaged |
|
| 2008-11-22 16:52:34 |
Kjell Braden |
ntfs-3g: statusexplanation |
Hal seems to reject the partition because the fstype is ntfs and gnome is trying to mount it via ntfs-3g.
The best solution to this would probably be adjusting /usr/share/hal/fdi/policy/10osvendor/20-ntfs-3g-policy.fdi to...
- append 'ntfs-3g' to volume.fstype.alternative
- append 'locale=' and 'exec' to volume.mount.ntfs-3g.valid_options
You can test that this works by running:
sudo hal-set-property --udi /your/UDI/to/your/ntfs/device --key volume.fstype.alternative --strlist-post ntfs-3g
sudo hal-set-property --udi /your/UDI/to/your/ntfs/device --key volume.mount.ntfs-3g.valid_options --strlist-post locale=
sudo hal-set-property --udi /your/UDI/to/your/ntfs/device --key volume.mount.ntfs-3g.valid_options --strlist-post exec
Since I'm rather unfamiliar with FDIs I suggest someone else should have a look at this. |
|
|
| 2008-12-12 20:23:04 |
Guy Thouret |
bug |
|
|
added attachment '20-ntfs-3g-policy.fdi' (20-ntfs-3g-policy.fdi) |
| 2008-12-28 16:00:34 |
Noel J. Bergman |
bug |
|
|
added attachment 'ntfs-fixed.patch' (diff between jaunty file and policy adjusted to support local NTFS partitions) |
| 2009-01-04 18:29:31 |
Chris Coulson |
ntfs-3g: status |
Triaged |
Incomplete |
|
| 2009-01-04 18:29:31 |
Chris Coulson |
ntfs-3g: statusexplanation |
|
It would be great if somebody experiencing this problem could attach the output of "lshal" to this bug report.
Thanks |
|
| 2009-01-04 22:10:49 |
Duncan Lithgow |
bug |
|
|
added attachment 'lshal.txt' (output of lshal) |
| 2009-01-04 23:40:32 |
Chris Coulson |
ntfs-3g: status |
Incomplete |
Triaged |
|
| 2009-01-04 23:40:32 |
Chris Coulson |
ntfs-3g: statusexplanation |
It would be great if somebody experiencing this problem could attach the output of "lshal" to this bug report.
Thanks |
|
|
| 2009-01-21 22:59:21 |
Chris Coulson |
ntfs-3g: status |
Triaged |
Incomplete |
|
| 2009-01-22 08:39:35 |
Chris Coulson |
ntfs-3g: status |
Incomplete |
In Progress |
|
| 2009-01-22 08:39:35 |
Chris Coulson |
ntfs-3g: assignee |
|
chrisccoulson |
|
| 2009-01-22 08:39:35 |
Chris Coulson |
ntfs-3g: statusexplanation |
|
Right, I think I understand why this is broken now. In Intrepid, gnome-mount is configured by default to mount any partitions with "volume.fstype=ntfs" with the ntfs-3g driver. In Jaunty this is the same, but it doesn't work because it appears that the alternative fstype needs to be specified in "volumes.fstype.alternative" when you are mounting a filesystem with a driver that is not the same as what is specified in volumes.fstype. This constraint doesn't appear to exist on Intrepid
So, this would have broken anyway with or without the ntfs-3g change from Debian. |
|
| 2009-01-27 10:00:06 |
Launchpad Janitor |
ntfs-3g: status |
In Progress |
Fix Released |
|
| 2009-05-03 20:28:49 |
dino99 |
attachment added |
|
lshal.log http://launchpadlibrarian.net/26290197/lshal.log |
|
| 2009-09-03 17:47:54 |
Pazkooda |
attachment added |
|
lshal.txt http://launchpadlibrarian.net/31279856/lshal.txt |
|
| 2009-09-19 02:04:25 |
L.D. Paniak |
attachment added |
|
lshal.txt http://launchpadlibrarian.net/32050093/lshal.txt |
|
| 2012-07-27 17:08:36 |
Kjell Braden |
removed subscriber Kjell Braden |
|
|
|
