This has been going on for a couple of weeks, but USB mass storage devices are no longer automatically mounting. Previously they would mount to /media/$BOOTLABEL/.
I have to manually do a: mount -o uid=500,gid=500 /dev/sdb1 /mnt
What package should I bugzilla this to?
-Paul
This has been going on for a couple of weeks, but USB mass storage devices are no longer automatically mounting. Previously they would mount to /media/$BOOTLABEL/.
I have to manually do a: mount -o uid=500,gid=500 /dev/sdb1 /mnt
What package should I bugzilla this to?
I've noticed that too. Pretty sure its been like this since Test1.
Peter
Paul Dickson wrote:
This has been going on for a couple of weeks, but USB mass storage devices are no longer automatically mounting. Previously they would mount to /media/$BOOTLABEL/.
I have to manually do a: mount -o uid=500,gid=500 /dev/sdb1 /mnt
What package should I bugzilla this to?
You havent specified any version or desktop environment information. The appropriate component depends on it.
Rahul
Paul Dickson wrote:
This has been going on for a couple of weeks, but USB mass storage devices are no longer automatically mounting. Previously they would mount to /media/$BOOTLABEL/.
I have to manually do a: mount -o uid=500,gid=500 /dev/sdb1 /mnt
What package should I bugzilla this to?
You havent specified any version or desktop environment information. The appropriate component depends on it.
For me at least its the latest rawhide.
Peter
On Mon, 24 Jul 2006 17:39:32 +0530, Rahul wrote:
Paul Dickson wrote:
This has been going on for a couple of weeks, but USB mass storage devices are no longer automatically mounting. Previously they would mount to /media/$BOOTLABEL/.
I have to manually do a: mount -o uid=500,gid=500 /dev/sdb1 /mnt
What package should I bugzilla this to?
You havent specified any version or desktop environment information. The appropriate component depends on it.
Sorry. Rawhide: latest. I'm using Gnome.
-Paul
Paul Dickson wrote:
On Mon, 24 Jul 2006 17:39:32 +0530, Rahul wrote:
Paul Dickson wrote:
This has been going on for a couple of weeks, but USB mass storage devices are no longer automatically mounting. Previously they would mount to /media/$BOOTLABEL/.
I have to manually do a: mount -o uid=500,gid=500 /dev/sdb1 /mnt
What package should I bugzilla this to?
You havent specified any version or desktop environment information. The appropriate component depends on it.
Sorry. Rawhide: latest. I'm using Gnome.
Latest is only latest for a day; also, mirrors are often delayed, and (don't frget timezones) so it would be useful to provide some actual versions... Perphaps this would be relevant ? # rpm -qa|grep -E 'gnome-mount|udev|kernel|gnome-volume-manager'|sort
DaveT.
This has been going on for a couple of weeks, but USB mass storage devices are no longer automatically mounting. Previously they would mount to /media/$BOOTLABEL/.
I have to manually do a: mount -o uid=500,gid=500 /dev/sdb1 /mnt
What package should I bugzilla this to?
You havent specified any version or desktop environment information. The appropriate component depends on it.
Sorry. Rawhide: latest. I'm using Gnome.
Latest is only latest for a day; also, mirrors are often delayed, and (don't frget timezones) so it would be useful to provide some actual versions... Perphaps this would be relevant ? # rpm -qa|grep -E 'gnome-mount|udev|kernel|gnome-volume-manager'|sort
Well given I've been having that issue since FC6T1 its probably all the 2.15 stuff but fyi
gnome-mount-0.4-8 gnome-volume-manager-1.5.15-4 kernel-2.6.17-1.2358.fc6 kernel-2.6.17-1.2432.fc6 udev-095-3
Pete
On Tue, 25 Jul 2006 00:18:30 +1000, David Timms wrote:
Paul Dickson wrote:
On Mon, 24 Jul 2006 17:39:32 +0530, Rahul wrote:
Paul Dickson wrote:
This has been going on for a couple of weeks, but USB mass storage devices are no longer automatically mounting. Previously they would mount to /media/$BOOTLABEL/.
I have to manually do a: mount -o uid=500,gid=500 /dev/sdb1 /mnt
What package should I bugzilla this to?
You havent specified any version or desktop environment information. The appropriate component depends on it.
Sorry. Rawhide: latest. I'm using Gnome.
Latest is only latest for a day; also, mirrors are often delayed, and (don't frget timezones) so it would be useful to provide some actual versions...
I posted my question here since I did not know which packages were involved.
Perphaps this would be relevant ? # rpm -qa|grep -E 'gnome-mount|udev|kernel|gnome-volume-manager'|sort
gnome-mount-0.4-8 gnome-volume-manager-1.5.15-4 kernel-2.6.17-1.2366.fc6 kernel-2.6.17-1.2396.fc6 kernel-2.6.17-1.2401.fc6 kernel-2.6.17-1.2405.fc6 kernel-2.6.17-1.2416.fc6 kernel-2.6.17-1.2431.fc6 kernel-2.6.17-1.2437.fc6 kernel-2.6.17-1.2439.fc6 kernel-devel-2.6.17-1.2366.fc6 kernel-devel-2.6.17-1.2396.fc6 kernel-devel-2.6.17-1.2401.fc6 kernel-devel-2.6.17-1.2405.fc6 kernel-devel-2.6.17-1.2416.fc6 kernel-devel-2.6.17-1.2437.fc6 kernel-devel-2.6.17-1.2439.fc6 kernel-doc-2.6.17-1.2439.fc6 udev-095-3
$uname -r 2.6.17-1.2437.fc6
-Paul
On Mon, 24 Jul 2006 07:40:00 -0700, Paul Dickson wrote:
On Tue, 25 Jul 2006 00:18:30 +1000, David Timms wrote:
Paul Dickson wrote:
On Mon, 24 Jul 2006 17:39:32 +0530, Rahul wrote:
Paul Dickson wrote:
This has been going on for a couple of weeks, but USB mass storage devices are no longer automatically mounting. Previously they would mount to /media/$BOOTLABEL/.
I have to manually do a: mount -o uid=500,gid=500 /dev/sdb1 /mnt
What package should I bugzilla this to?
You havent specified any version or desktop environment information. The appropriate component depends on it.
Sorry. Rawhide: latest. I'm using Gnome.
Latest is only latest for a day; also, mirrors are often delayed, and (don't frget timezones) so it would be useful to provide some actual versions...
I posted my question here since I did not know which packages were involved.
Perphaps this would be relevant ? # rpm -qa|grep -E 'gnome-mount|udev|kernel|gnome-volume-manager'|sort
gnome-mount-0.4-8 gnome-volume-manager-1.5.15-4 kernel-2.6.17-1.2437.fc6 kernel-devel-2.6.17-1.2437.fc6 kernel-doc-2.6.17-1.2439.fc6 udev-095-3
$uname -r 2.6.17-1.2437.fc6
I BZ'd this under gnome-volume-manger as:
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=200047
-Paul
On Mon, 24 Jul 2006 21:01:42 -0700, Paul Dickson wrote:
I BZ'd this under gnome-volume-manger as:
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=200047
This has since been moved to hal and it might have to be moved to udev...
I'm not specifically sure how udev works, but I'm getting a "Line too long" from udev on /etc/udev/rules.d/60-libsane.rules before rhgb runs. Would this error prevent 90-hal.hules from being loaded?
Anyone have debugging tips for udev?
-Paul
On Fri, Jul 28, 2006 at 08:52:46AM -0700, Paul Dickson wrote:
I'm not specifically sure how udev works, but I'm getting a "Line too long" from udev on /etc/udev/rules.d/60-libsane.rules before rhgb runs.
That particular causing complaints line happens to be a comment. It is over 500 characters long. You can easily split it or even remove from rules.
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=200324
Would this error prevent 90-hal.hules from being loaded?
I highly doubt it but some digging would be required for an absolute certainity. In any case this is a warning and not an error.
Michal
On Fri, 28 Jul 2006 10:33:21 -0600, Michal Jaegermann wrote:
On Fri, Jul 28, 2006 at 08:52:46AM -0700, Paul Dickson wrote:
I'm not specifically sure how udev works, but I'm getting a "Line too long" from udev on /etc/udev/rules.d/60-libsane.rules before rhgb runs.
That particular causing complaints line happens to be a comment. It is over 500 characters long. You can easily split it or even remove from rules.
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=200324
Would this error prevent 90-hal.hules from being loaded?
I highly doubt it but some digging would be required for an absolute certainity. In any case this is a warning and not an error.
I erased the sane-backends package and the error message went away, but my mass storage device still won't automatically mount.
-Paul
I think automagically is the key here. It did not work this morning. I ran yum and applied some updates. Then, just now, it worked.
Trouble is, I can't point to a package and say that fixed it, so it can still happen again.
Installing: kernel i686 2.6.17-1.2505.fc6 development 16 M kernel-devel i686 2.6.17-1.2505.fc6 development 4.4 M Updating: ekiga i386 2.0.2-3 development 5.1 M gnupg i386 1.4.5-3 development 1.8 M hal-cups-utils i386 0.6.2-3 development 26 k initscripts i386 8.38-1 development 1.2 M irda-utils i386 0.9.17-2.fc6 development 73 k java-1.4.2-gcj-compat i386 1.4.2.0-40jpp_100rh development 43 k kernel-doc noarch 2.6.17-1.2505.fc6 development 2.7 M libselinux i386 1.30.19-5 development 89 k libselinux-devel i386 1.30.19-5 development 126 k libselinux-python i386 1.30.19-5 development 50 k libtiff i386 3.8.2-5 development 312 k libtiff-devel i386 3.8.2-5 development 492 k lvm2 i386 2.02.06-3 development 1.0 M module-init-tools i386 3.3-0.pre1.4.15 development 397 k perl-IO-Socket-SSL noarch 0.994-1.fc6 development 47 k rhpxl i386 0.27-1 development 93 k selinux-policy noarch 2.3.3-17 development 290 k selinux-policy-targeted noarch 2.3.3-17 development 638 k xorg-x11-drv-ati i386 6.6.1-6.fc6 development 333 k Removing: kernel i686 2.6.17-1.2439.fc6 installed 44 M kernel-devel i686 2.6.17-1.2439.fc6 installed 14 M
-Paul
On Wed, 2 Aug 2006 11:49:54 -0700, Paul Dickson wrote:
I think automagically is the key here. It did not work this morning. I ran yum and applied some updates. Then, just now, it worked.
Well, I rebooted and it doesn't works again.
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=200047#c12
I added debugging output from udev and hald as an attachment to this BZ comment. It appears that nothing is registering to be passed the volume info. I'm not sure how gnome-mount gets invoked. Is it gnome-volume-manager?
-Paul
-
David Timms -
Michal Jaegermann -
Paul Dickson -
Peter Robinson -
Rahul Sundaram