Bugzilla – Bug 297569
USB stick seems to be not recognized
Last modified: 2008-02-20 07:33:42 UTC
When I connect an USB stick to my computer, the drive seems to be not recognized by openSUSE. When I open "My computer" (KDE), the device isn't listed. Also accessing "/media" via the command line doesn't help: there is no folder for the USB stick. The USB stick itself however seems to be recognized for some way. I attach a screenshot of the hardware information of KDE.
Created attachment 155601 [details] snapshot1.png
Created attachment 155602 [details] snapshot2.png Something interesting: I also attach snapshot2.png, which I have made when no USB stick was connected. Note that in this screenshot, there is an entry for my (USB) keyboad. When I connect an USB stick, the entry of the keyboard gets replaced by the entry of the USB stick (see snapshot1.png, however, the keyboard continues working while the USB stick doesn't work). When I remove the USB stick, the USB stick entry is replaced by the keyboard entry (snapshot2.png).
Created attachment 155603 [details] snapshot3.png Or is the reason that the hole HAL isn't running at all? I don't know how to test this, but at least, when trying to access the floppy drive via sysinfo:/ in Konqueror, then I get the error "Feature only avaible with HAL" (snapshot3.png).
Then please check if HAL is running via 'rchal status' or 'lshal' please check also if dbus is running (rcdbus status). If both is running please do the same as in: https://bugzilla.novell.com/show_bug.cgi?id=297548#c1 and attach your logs here as attachment.
please follow also: http://rudin.suse.de:8888/show_bug.cgi?id=297548#c2
Created attachment 155674 [details] log.txt Yes, both is running (log.txt).
Created attachment 155676 [details] messages The log for the instructions from https://bugzilla.novell.com/show_bug.cgi?id=297548#c1 (messages).
The link http://rudin.suse.de:8888/show_bug.cgi?id=297548#c2 isn't working for me.
Sorry, replace 'http://rudin.suse.de:8888' with https://bugzilla.novell.com Please try to reproduce with beta1. I could not reproduce the problem here on Beta1
Created attachment 156599 [details] udevmonitor --env Here is the result of 'udevmonitor --env' using alpha7. I've installed 10.3 alpha 7 on two computers, and only one of them has this problem. So maybe with a new installation of beta 1 the problem doesn't show up anymore on my computer but isn't really solved. However, after installing beta 1, I'll test this. But this may take some days...
Report for beta1 (attention: here I'm using another computer!) 'rchal status' or 'lshal': working fine, HAL is running.
Created attachment 156607 [details] messages_beta1
Created attachment 156608 [details] udevmonitor --env_beta1
Is also a test with your new HAL version in Factory avaible at http://download.opensuse.org/repositories/home:/dkukawka:/hal-beta/openSUSE_Factory/ nessesary?
One thing that is unclear for me atm: Does it work for you with beta1 or is the problem present (if there are problems, please attach lshal output with the USB stick in your machine). You can also try the HAL/PolicyKit/ConsoleKit packages from the repo, but you have to be sure that consolekit is running before HAL and you should know that there are currently some problems with KDE. (you can't mount a media, but you could test if the dialog for the media popup (if the USB-Stick get detected)).
Created attachment 156690 [details] log.txt_beta1 Sorry, I forgot to mention: Also in beta1, there is the same problem. (I'm testing beta1 on another computer than alpha7). As I don't know what consolekit is nor how running it befor HAL, I won't try it with the Factory version for the moment.
Sorry, but I'm confused now. The log show that there was a USB Stick (/dev/sdb1 and udi = '/org/freedesktop/Hal/devices/volume_uuid_132F_705D') detected. Wasn't there a popup in KDE about the detected volume/media. What is the exact problem with Beta1? That there was no popup or that the mount from KDE fail?
That's it: There wasn't a popup in KDE about the detected volume/media. And, as described in "Description": > When I open "My computer" (KDE), the device isn't listed. Also > accessing "/media" via the command line doesn't help: there is no > folder for the USB stick. So, there is no Pop-up, "sysinfo:/" doesn't know about the USB stick and also in "/media" there isn't a directory created for the USB stick. So I don't know how to access the USB stick.
This appears to be a duplicate of closed bug 298943. the solution given add XDG_SESSION_COOKIE to the line env_keep= in /etc/sudoers (edited as root with visudo) works for me in beta1. You will have to restart the session.
Hm, I'm not shure. Bug 298943 seems to be about a KDE problem, right? (I haven't tryied the workarround so far...) But with my problem, there is even not a folder created in /media (like /media/disk or whatever), so also using the console I don't get access to the USB stick.
You plug in your usb device, no popup appears and nothing is created under /media. It's the same as far as I can see. Try it.
Created attachment 157751 [details] etc_sudoers - the new /etc/sudoers I've edited /etc/sudoers with 'kdesu kwrite /etc/sudoers' - the result is attached. It didn't help. The USB stick don't get mounted in /media and also KDE doesn't notice about the USB stick.
You don't say if you restarted the X server. If you did the the bugs reports are not the same. One other thought, from /etc/sudores # This file MUST be edited with the 'visudo' command as root. although I can't see this making a difference.
please stop this sudo/XDG_SESSION_COOKIE discussion. This has nothing to do with the problem in this bug. The USB stick get not recognized, this is something different to: 'missing permissions to mount the USB stick'.
Hm, I remember that in the first boot after the installation, the USB stick mounting was working fine. From the next boot on it was no longer working. Now I've made a new installation of Beta1 and I could see the same: This time on the second boot I plugged in the USB stick and it worked. After a new reboot, USB stickes were not recognized anymore. So it seems to my that USB sticks are working only one time after the installation. Up from the next shoutdown, the won't work anymore...
I seem to be experiencing the same problem. I installed Beta 1, and USB drives worked fine. Shortly after, they stopped working. (I don't know if it was immediately after the first restart though.) hald-addon-storage immediately begins polling the device, and root can mount it manually, but nothing else happens automatically. I'm using KDE as well; I can try installing GNOME later to see if that makes a difference.
(In reply to comment #18 from Tim Fechtner) > That's it: There wasn't a popup in KDE about the detected volume/media. And, > as described in "Description": Could you start 'lshal -m' on a Beta1 or Beta2 and insert the USB stick, wait 5 seconds and attach the output to the bug.
Well, I still don't know if my problem was the same as the reporter's, but I've just fixed mine. I was getting ready to nuke my /usr/share/hal directory, and in the process of figuring out which packages put files there so I could know what to reinstall, I found a file /usr/share/hal/fdi/policy/gparted-disable-automount.fdi -- I had run gparted not too long ago, and I guess it crashed on exit or forgot to delete the file for some other reason. After removing this file, everything appears to be working fine. So, try looking for this file (or any other non-default files in /usr/share/hal that contain the string "volume.ignore")
Created attachment 161359 [details] lshal -m_beta1 To comment #27: Done. I've plugged the USB stick (14:01:28 - 14:01:30) and then removed it (14:01:36).
I can't see any problems within HAL, the partition on the stick get detected correctly as log.txt_beta1 show and also correct announced as the lshal -m log show. I assume there is a problem with your KDE installation. I reassign the bug to the KDE maintainers.
reopen if you think that uninstalling device mapper does not fix it. *** This bug has been marked as a duplicate of bug 306288 ***
Reopening. Bug 306288 is fixed in 10.3 beta 3? This bug I could reproduce on beta 3. BTW: /dev/sdb and /dev/sdb1 is shown well when USB stick is plugged. It's possible to mount is manually. But it doesn't get mounted automaticly and KDE doesn't show any reaction...
what is the new behaviour? do you see something in lshal --monitor?
Just what's described in comment #32 a little bit to short: I plug in the USB stick. At /dev/ there get created sdb and sdb1. At /media, no folder gets created and the stick also don't get mounted at another place. It is possible to mount the USB stick manually. KDE doesn't show any reaction. No popup window. Also at sysinfo:/ the USB stick doesn't appear.
is your kded still running ? we have another bugreport that causes kded to crash, which would explain why you don't see any reaction.
Sorry, actually on all my installations this is working. I'll do a new installation of RC1 later this week and I'll see if the bug is still there...
Could no longer reproduce this behavior on 10.3 final. For the moment I close this bug as WORKSFORME.
Reopening. Could now reproduce it in 10.3 (DVD x32) final. In reply to comment #35: Yes. (At least, when I call ksysguard, a process named kded is displayed. It's owner is the user currently logged in in KDE.) Just some addititional informations: I had booted the PC then the USB stick was yet plugged in and KDE didn't display him. So I plugged him out and then plugged him in - no reaction like described below. Also after mounting the USB stick manually, sysinfo:/ didn't display him.
this is possible a duplicate of Bug 331054. can you please do the following (as root). /* no usbstick , use shell */ 1. rchal stop 2. /usr/sbin/hald --daemon=no /* insert usbstick */ note: hald will generate a lot of noise. please post what happens after inserting the stick.
For the moment, USB sticks are working fine on all my systems. I really don't understand _when_ this bus appears and when it disappears - and why? However, when the described behavior occures next time, I'll provide the information requested in Comment #39.
I can fully reproduce the issue. It happens for me in about 4 of 5 times I boot the machine. Each time when the issue appears, ConsoleKit is not running (according to "service consolekit status"). If I start ConsoleKit and logout and login again, everything is fine. The problem stems from the fact, that ConsoleKit needs DBUS. Well, while DBUS is actually STARTED before ConsoleKit, it is not UP in all cases! So ConsoleKit goes down due to missing DBUS and is not able to give the user the correct rightswhen he logs in. I solved this issue by patching /etc/init.d/consolekit . If DBUS is not up. wait for it. The attached patch file consolekit-initd.patch is quite straightforward. Since I patched it, it has never been a problem for me anymore. It would be nice if the patch could be added to 10.3 and upcoming 11.0. Christian
Created attachment 193482 [details] Patch for /etc/init.d/consolekit
This should actually be fixed by a dbus update some time ago? You're sure you have all online updates installed?
I fixed this on my local box on Nov, 4th 2007, so it might have been fixed in the meantime by an online update (I have all online updates installed, and see a /etc/init.d/dbus file with a modification date of Nov, 8th 2007). I thought it wasn't fixed, because it was reopened on 2007-10-13, and was not closed since then. Should this bug report be closed then?
worksforme. reopen if problem persists after online update *** This bug has been marked as a duplicate of bug 332845 ***
Does *NOT* work for me using fvwm2 as WM, latest update yesterday (07.02.08). the stick shows up in dmesg as expected. I have restarted ivman and checked again, no success. Mounting manualy works fine. Due to lack of time i have not checked hald reactions,
good news: it works for me, too. The reason it did not work before seems that one of my usb-ports (i have 4) does not work with the usb-stick i used to test. I noticed this only when i started hald in debug mode and i could not see any event. mea culpa,
i am sorry but after the good news yesterday i updated a workstation and the result was nothing (see log from hald below). Instead it shows this error again. ** (process:5246): CRITICAL **: polkit_session_get_ck_objref: assertion For total confusion i tested the stick on the note (where is was working yesterday). the log is attached. 09:35:25.212 [I] hald_dbus.c:5244: *************************** 09:35:25.212 [I] hald_dbus.c:5245: ********* got a connection 8103b10 09:35:25.212 [I] hald_dbus.c:5246: *************************** [5689]: 09:35:25.214 [D] probe-volume.c:383: volume.block_size = 512 [5689]: 09:35:25.215 [D] probe-volume.c:387: volume.size = 2029502464 [5689]: 09:35:25.216 [I] probe-volume.c:616: invoking volume_id_probe_all, offset=0, size=0 5689: 09:35:25.217: volume_id.c:351 probing at offset 0x0, size 0x78f7c000 5689: 09:35:25.218: linux_raid.c:70 probing at offset 0x78f60000, size 0x78f7c000 5689: 09:35:25.218: util.c:342 get buffer off 0x78f60000(2029387776), len 0x800 5689: 09:35:25.219: util.c:391 read seekbuf off:0x78f60000 len:0x800 5689: 09:35:25.221: linux_raid.c:124 probing at offset 0x78f60000, size 0x78f7c000 5689: 09:35:25.222: util.c:342 get buffer off 0x78f60000(2029387776), len 0x800 5689: 09:35:25.223: linux_raid.c:124 probing at offset 0x0, size 0x78f7c000 5689: 09:35:25.223: util.c:342 get buffer off 0x0(0), len 0x800 5689: 09:35:25.224: util.c:355 read sbbuf len:0x800 5689: 09:35:25.226: linux_raid.c:124 probing at offset 0x1000, size 0x78f7c000 5689: 09:35:25.227: util.c:342 get buffer off 0x1000(4096), len 0x800 5689: 09:35:25.227: util.c:355 read sbbuf len:0x1800 5689: 09:35:25.229: ddf_raid.c:49 probing at offset 0x0, size 0x78f7c000 5689: 09:35:25.229: util.c:342 get buffer off 0x78f7be00(2029501952), len 0x200 5689: 09:35:25.230: util.c:391 read seekbuf off:0x78f7be00 len:0x200 5689: 09:35:25.233: isw_raid.c:47 probing at offset 0x0, size 0x78f7c000 5689: 09:35:25.234: util.c:342 get buffer off 0x78f7bc00(2029501440), len 0x200 5689: 09:35:25.235: util.c:391 read seekbuf off:0x78f7bc00 len:0x200 5689: 09:35:25.239: lsi_raid.c:42 probing at offset 0x0, size 0x78f7c000 5689: 09:35:25.243: util.c:342 get buffer off 0x78f7be00(2029501952), len 0x200 5689: 09:35:25.247: util.c:391 read seekbuf off:0x78f7be00 len:0x200 5689: 09:35:25.251: util.c:342 get buffer off 0x78f7be00(2029501952), len 0x200 5689: 09:35:25.255: silicon_raid.c:57 probing at offset 0x0, size 0x78f7c000 5689: 09:35:25.259: util.c:342 get buffer off 0x78f7be00(2029501952), len 0x200 5689: 09:35:25.263: nvidia_raid.c:45 probing at offset 0x0, size 0x78f7c000 5689: 09:35:25.267: util.c:342 get buffer off 0x78f7bc00(2029501440), len 0x200 5689: 09:35:25.271: util.c:391 read seekbuf off:0x78f7bc00 len:0x200 5689: 09:35:25.275: promise_raid.c:46 probing at offset 0x0, size 0x78f7c000 5689: 09:35:25.279: util.c:342 get buffer off 0x78f74200(2029470208), len 0x200 5689: 09:35:25.286: util.c:391 read seekbuf off:0x78f74200 len:0x200 5689: 09:35:25.291: util.c:342 get buffer off 0x78f5c200(2029371904), len 0x200 5689: 09:35:25.294: util.c:391 read seekbuf off:0x78f5c200 len:0x200 5689: 09:35:25.299: util.c:342 get buffer off 0x78f5c000(2029371392), len 0x200 5689: 09:35:25.302: util.c:391 read seekbuf off:0x78f5c000 len:0x200 5689: 09:35:25.306: util.c:342 get buffer off 0x78f7a000(2029494272), len 0x200 5689: 09:35:25.310: util.c:391 read seekbuf off:0x78f7a000 len:0x200 5689: 09:35:25.314: util.c:342 get buffer off 0x78f4a200(2029298176), len 0x200 5689: 09:35:25.317: util.c:391 read seekbuf off:0x78f4a200 len:0x200 5689: 09:35:25.322: util.c:342 get buffer off 0x78f7aa00(2029496832), len 0x200 5689: 09:35:25.328: util.c:391 read seekbuf off:0x78f7aa00 len:0x200 5689: 09:35:25.330: adaptec_raid.c:90 probing at offset 0x0, size 0x78f7c000 5689: 09:35:25.333: util.c:342 get buffer off 0x78f7be00(2029501952), len 0x200 5689: 09:35:25.337: util.c:391 read seekbuf off:0x78f7be00 len:0x200 5689: 09:35:25.341: jmicron_raid.c:43 probing at offset 0x0, size 0x78f7c000 5689: 09:35:25.345: util.c:342 get buffer off 0x78f7be00(2029501952), len 0x200 5689: 09:35:25.349: lvm.c:49 probing at offset 0x0 5689: 09:35:25.356: util.c:342 get buffer off 0x400(1024), len 0x800 5689: 09:35:25.357: util.c:342 get buffer off 0x0(0), len 0x800 5689: 09:35:25.365: highpoint.c:52 probing at offset 0x0 5689: 09:35:25.369: util.c:342 get buffer off 0x1200(4608), len 0x200 5689: 09:35:25.373: volume_id.c:382 probing at offset 0x0, size 0x78f7c000 5689: 09:35:25.377: fat.c:273 probing at offset 0x0 5689: 09:35:25.381: util.c:342 get buffer off 0x0(0), len 0x400 5689: 09:35:25.384: util.c:342 get buffer off 0x200(512), len 0x200 5689: 09:35:25.388: util.c:342 get buffer off 0x0(0), len 0x200 5689: 09:35:25.392: util.c:342 get buffer off 0x3ca000(3973120), len 0x1000 5689: 09:35:25.396: util.c:391 read seekbuf off:0x3ca000 len:0x1000 5689: 09:35:25.398: util.c:342 get buffer off 0x0(0), len 0x200 [5689]: 09:35:25.404 [I] probe-volume.c:618: volume_id_probe_all returned 0 [5689]: 09:35:25.408 [D] probe-volume.c:107: volume.fsusage = 'filesystem' [5689]: 09:35:25.412 [D] probe-volume.c:113: volume.fstype = 'vfat' [5689]: 09:35:25.417 [D] probe-volume.c:118: volume.fsversion = 'FAT32' [5689]: 09:35:25.418 [D] probe-volume.c:123: volume.uuid = '3462-414A' [5689]: 09:35:25.424 [D] probe-volume.c:135: volume.label = 'LG' [5689]: 09:35:25.428 [I] probe-volume.c:690: Loading part table [5689]: 09:35:25.439 [I] partutil.c:860: MSDOS partition table detected [5689]: 09:35:25.440 [I] probe-volume.c:696: Looking at part table [5689]: 09:35:25.441 [I] probe-volume.c:769: Done looking at part table 09:35:25.444 [I] hald_dbus.c:1261: volume.block_size -> 512 09:35:25.444 [I] hald_dbus.c:1269: volume.size -> 2029502464 09:35:25.444 [I] hald_dbus.c:1253: volume.fsusage -> filesystem 09:35:25.444 [I] hald_dbus.c:1253: volume.fstype -> vfat 09:35:25.444 [I] hald_dbus.c:1253: volume.fsversion -> FAT32 09:35:25.444 [I] hald_dbus.c:1253: volume.uuid -> 3462-414A 09:35:25.444 [I] hald_dbus.c:1253: volume.label -> LG 09:35:25.444 [I] hald_dbus.c:1253: info.product -> LG 09:35:25.444 [I] hald_dbus.c:1253: volume.partition.scheme -> mbr 09:35:25.444 [I] hald_dbus.c:1253: volume.partition.type -> 0x0b 09:35:25.444 [I] hald_dbus.c:1253: volume.partition.label -> 09:35:25.444 [I] hald_dbus.c:1253: volume.partition.uuid -> 09:35:25.444 [I] hald_dbus.c:1239: strlist elem volume.partition.flags -> boot 09:35:25.448 [I] hald_dbus.c:5186: ************************ 09:35:25.448 [I] hald_dbus.c:5187: Client to local_server was disconnected for 8103b10 09:35:25.448 [I] hald_dbus.c:5188: ************************ 09:35:25.448 [I] hald_dbus.c:5230: *************************** 09:35:25.448 [I] hald_dbus.c:5231: ********* unregistered 8103b10 09:35:25.448 [I] hald_dbus.c:5232: *************************** /usr/lib/hal/hald-probe-volume exited 09:35:25.452 [I] blockdev.c:379: entering; exit_type=0, return_code=0 09:35:25.462 [I] blockdev.c:133: Add callouts completed udi=/org/freedesktop/Hal/devices/volume_uuid_3462_414A 09:35:25.462 [I] hald.c:108: Added device to GDL; udi=/org/freedesktop/Hal/devices/volume_uuid_3462_414A 09:35:26.177 [W] ci-tracker.c:366: Error doing GetSessionForUnixProcess on ConsoleKit: org.freedesktop.DBus.GLib.UnmappedError.CkManagerError.Code0: Unable to lookup session information for process '5691' 09:35:26.177 [I] hald_dbus.c:5037: OK for method 'Mount' with signature 'ssas' on interface 'org.freedesktop.Hal.Device.Volume' for UDI '/org/freedesktop/Hal/devices/volume_uuid_3462_414A' and execpath 'hal-storage-mount' 09:35:26.177 [I] hald_dbus.c:3938: no need to enqueue Run started hal-storage-mount (0) (1) ! full path is '/usr/lib/hal/hal-storage-mount', program_dir is '/usr/lib/hal' 5692: XYA attempting to get lock on /media/.hal-mtab-lock 5692: XYA got lock on /media/.hal-mtab-lock 09:35:26.182 [I] hald_dbus.c:5244: *************************** 09:35:26.182 [I] hald_dbus.c:5245: ********* got a connection 810d070 09:35:26.182 [I] hald_dbus.c:5246: *************************** device = /dev/sdc1 invoked by uid = 1000 invoked by system bus connection = :1.42 label 'LG' uuid '3462-414A' Looking at /etc/fstab entry '/dev/sda1' /etc/fstab: device /dev/sda1 -> /dev/sda1 Looking at /etc/fstab entry '/dev/sda2' /etc/fstab: device /dev/sda2 -> /dev/sda2 Looking at /etc/fstab entry '/dev/sda7' /etc/fstab: device /dev/sda7 -> /dev/sda7 Looking at /etc/fstab entry '/dev/sda6' /etc/fstab: device /dev/sda6 -> /dev/sda6 Looking at /etc/fstab entry '/dev/sda5' /etc/fstab: device /dev/sda5 -> /dev/sda5 Looking at /etc/fstab entry '/dev/sda3' /etc/fstab: device /dev/sda3 -> /dev/sda3 Looking at /etc/fstab entry 'proc' /etc/fstab: device proc -> proc Looking at /etc/fstab entry 'sysfs' /etc/fstab: device sysfs -> sysfs Looking at /etc/fstab entry 'debugfs' /etc/fstab: device debugfs -> debugfs Looking at /etc/fstab entry 'usbfs' /etc/fstab: device usbfs -> usbfs Looking at /etc/fstab entry 'devpts' /etc/fstab: device devpts -> devpts mount_point = 'LG' mount_fstype = '' mount_options = 'uid=1000 ' trying dir /media/LG given_options[0] = 'uid=1000' allowed_options[0] = 'ro' allowed_options[1] = 'sync' allowed_options[2] = 'dirsync' allowed_options[3] = 'noatime' allowed_options[4] = 'nodiratime' allowed_options[5] = 'noexec' allowed_options[6] = 'quiet' allowed_options[7] = 'remount' allowed_options[8] = 'exec' allowed_options[9] = 'utf8' allowed_options[10] = 'shortname=' allowed_options[11] = 'codepage=' allowed_options[12] = 'iocharset=' allowed_options[13] = 'umask=' allowed_options[14] = 'dmask=' allowed_options[15] = 'fmask=' allowed_options[16] = 'uid=' allowed_options[17] = 'flush' uid= with uid 1000 using action hal-storage-mount-removable for uid 1000, system_bus_connection :1.42 ** (process:5246): CRITICAL **: polkit_session_get_ck_objref: assertion `session != NULL' failed /usr/lib/hal/hal-storage-mount exited 09:35:26.245 [I] device.c:1845: Removing locks from ':1.43' 09:35:26.245 [I] hald_dbus.c:3962: No more methods in queue 09:35:26.245 [I] hald_dbus.c:4025: failed with 'org.freedesktop.Hal.Device.PermissionDeniedByPolicy' 'hal-storage-mount-removable no <-- (action, result)' 09:35:26.245 [I] hald_dbus.c:5186: ************************ 09:35:26.245 [I] hald_dbus.c:5187: Client to local_server was disconnected for 810d070 09:35:26.245 [I] hald_dbus.c:5188: ************************ 09:35:26.245 [I] hald_dbus.c:5230: *************************** 09:35:26.245 [I] hald_dbus.c:5231: ********* unregistered 810d070 09:35:26.245 [I] hald_dbus.c:5232: *************************** 09:35:26.260 [I] ci-tracker.c:212: Removing CICallerInfo object for :1.42 09:35:26.260 [I] device.c:1845: Removing locks from ':1.42' [5304]: 09:35:32.052 [I] addon-storage.c:346: Checking whether device /dev/sr0 is locked on HAL [5304]: 09:35:32.054 [I] addon-storage.c:354: ... device /dev/sr0 is not locked on HAL [5688]: 09:35:41.108 [I] addon-storage.c:346: Checking whether device /dev/sdc is locked on HAL [5688]: 09:35:41.109 [I] addon-storage.c:354: ... device /dev/sdc is not locked on HAL [5688]: 09:35:41.109 [D] addon-storage.c:514: Media insertion detected on /dev/sdc 09:35:41.110 [D] hald_dbus.c:1571: udi=/org/freedesktop/Hal/devices/storage_serial_LG_USB_Drive_AA17071300007835_0_0, key=storage.removable.media_available 09:35:41.110 [I] hald_dbus.c:2971: entering, local_interface=1 09:35:41.110 [D] hald_dbus.c:2980: udi=/org/freedesktop/Hal/devices/storage_serial_LG_USB_Drive_AA17071300007835_0_0 09:35:41.110 [I] blockdev.c:1627: blockdev_rescan_device: udi=/org/freedesktop/Hal/devices/storage_serial_LG_USB_Drive_AA17071300007835_0_0 Run started hald-probe-storage (10000) (0) ! full path is '/usr/lib/hal/hald-probe-storage', program_dir is '/usr/lib/hal' woohoo [5694]: 09:35:41.114 [D] probe-storage.c:155: Doing probe-storage for /dev/sdc (bus usb) (drive_type disk) (udi=/org/freedesktop/Hal/devices/storage_serial_LG_USB_Drive_AA170713 00007835_0_0) (--only-check-for-fs==1) [5694]: 09:35:41.114 [D] probe-storage.c:395: Checking for file system on /dev/sdc [5694]: 09:35:41.114 [D] probe-storage.c:401: Doing open ("/dev/sdc", O_RDONLY) 09:35:41.114 [I] hald_dbus.c:5244: *************************** 09:35:41.114 [I] hald_dbus.c:5245: ********* got a connection 80b7048 09:35:41.114 [I] hald_dbus.c:5246: *************************** [5694]: 09:35:41.114 [D] probe-storage.c:409: Returned from open(2) [5694]: 09:35:41.114 [D] probe-storage.c:425: look for existing partitions for sdc [5694]: 09:35:41.114 [D] probe-storage.c:435: partition sdc1 found, skip probing for filesystem [5694]: 09:35:41.119 [I] partutil.c:860: MSDOS partition table detected 09:35:41.119 [I] hald_dbus.c:1285: storage.removable.media_available -> True 09:35:41.119 [I] hald_dbus.c:1269: storage.removable.media_size -> 2029518848 09:35:41.119 [I] hald_dbus.c:1253: storage.partitioning_scheme -> mbr 09:35:41.120 [I] hald_dbus.c:5186: ************************ 09:35:41.120 [I] hald_dbus.c:5187: Client to local_server was disconnected for 80b7048 09:35:41.120 [I] hald_dbus.c:5188: ************************ 09:35:41.120 [I] hald_dbus.c:5230: *************************** 09:35:41.120 [I] hald_dbus.c:5231: ********* unregistered 80b7048 09:35:41.120 [I] hald_dbus.c:5232: *************************** /usr/lib/hal/hald-probe-storage exited 09:35:41.120 [I] blockdev.c:1583: hald-probe-storage --only-check-for-media returned 0 (exit_type=0)
Created attachment 194094 [details] hald logfile of the detected but not mounted usb stick I have cliped that this together that may result in dublicated lines. the important parts should be ok. the usb stick is the same as used for testing the other workstation