1 |
> Using Windowmaker with Thunar as a file manager, with the volume manager |
2 |
> in place and that plugin is enabled. |
3 |
> |
4 |
> For some reason Thunar is now not seeing any USB device when plugged |
5 |
> in. I am not sure when this stopped working. |
6 |
> |
7 |
> My USB devices of keyboard, trackball, and webcam are working fine. |
8 |
> If I "lsusb" I can see the flash drive listed when inserted. |
9 |
> |
10 |
> I have tried re-emerging various items hoping that it would bring it |
11 |
> back to life. Obviously no luck since I am posting. |
12 |
> |
13 |
> Would anyone have any ideas on a possible cause and cure? |
14 |
|
15 |
I'm also using xfce & thunar, but I've not setup any auto-mounting |
16 |
yet. So, I don't have any wisdom on the ground of getting back your |
17 |
old functionality. |
18 |
|
19 |
However, there is a reasonable alternative solution that might be more |
20 |
elegant, and also not dependent on your desktop, which is to use udev. |
21 |
Generally speaking, for my approach here, this isn't good for |
22 |
automounting any random device. However, for your standard devices, |
23 |
you can do things like collecting the usb serial number. |
24 |
|
25 |
The upside of this (and the reason I use it), is that for your |
26 |
standard USB storage devices, you can mount each one uniquely to any |
27 |
specified mount point. This is useful for things like backup to USB |
28 |
harddisk that you want mounted to the same point for, in my case, |
29 |
rsnapshot. (This is otherwise more difficult, since automounting |
30 |
without serial ID will just take the first usb drive connected and |
31 |
mount it somewhere in /media usually.) |
32 |
|
33 |
My usb camera is also mounted in such a manner, so that will also |
34 |
work. I assume a keyboard could be done likewise. |
35 |
|
36 |
In case this route is of interest, I will syndicate parts of a post I |
37 |
made to the list in October: |
38 |
|
39 |
To get the serial of a device, for this example, the device node |
40 |
/dev/sdb (which might be a USB key considered as a SATA drive here): |
41 |
|
42 |
# udevadm info -a -p $(udevadm info -q path -n /dev/sdb) | grep ATTRS{serial} |
43 |
|
44 |
You might get more than one return on this command. Us the first |
45 |
serial, and it is also the one without colons or periods, just numbers |
46 |
and letters. |
47 |
|
48 |
I include my own configuration files. The .rules config files should |
49 |
go into /etc/udev/rules.d and the scripts should be made executable |
50 |
and go under /etc/udev/scripts/ |
51 |
|
52 |
For a harddrive, then, you can make the directory in /mnt and put it into fstab |
53 |
|
54 |
/dev/cyclops /mnt/cyclops ext3 rw,users 0 0 |
55 |
|
56 |
The system will complain on boot that it can't find the drive if it's |
57 |
not attached, but it won't do any harm as it's just a warning. |
58 |
|
59 |
PLEASE NOTE: For udev rules, each *new line* is considered as a *new |
60 |
rule*, thus for the same device, make sure there are no carriage |
61 |
returns. This could happen if you were Googling your hardware for |
62 |
udev rules and copy-pasting the udev rules from a web-browser (as not |
63 |
all sites will properly handle the carriage returns). |
64 |
|
65 |
Hope this helps, even if it is an alternative solution and doesn't |
66 |
tell you what happened to your system or why. |
67 |
|
68 |
~daid |