[SMS]

GCMartin · Junior Member Joined: 20 Jun 2012 Posts: 14

If USB storage is already plugged into the system When the system boots, the devices are usable.

BUT, should you plug a USB in after the system is running on the KDE desktop, the system cannot/will not produce the USE for system/desktop use. Is this a known problem?

Problem shown via an error message as follows when a USB storage device is plugged into system
Pop-up Window-box titled "Error - Konqueror" with text "Cannot obtain lock on /media/.hal-mtab" and has OK button to exit the error.

Please advise on a circumvention in the KDE process?

Please understand this: If I open a terminal, I can mount the /dev/USBdevice that the system assigned to the USB unit. And, I can use the unit's contents via its mount-point.
But, I cannot "dismount" the unit as its shown on my KDE desktop. I get a similar "lock" problem error message. Leaving me with the only way to remove the USB from the system is to open a terminal and umount the device mount-point.

Hope this helps

gerasimos_h · Posted: Wed Jun 27, 2012 5:25 am Post subject:

If you mount a device from terminal you can't unmount it from KDE with eject/safely remove.

Either mount them through KDE to be able to unmount them through KDE, or mount them through terminal, and unmount them through terminal.

gerasimos_h

vivanguarda · Member Joined: 01 May 2009 Posts: 98

I ´ll continue this topic so my problem is similar, then it can be a way to show you a regular issue. Sorry me if a fault!

I have another Slack 14 hd installed in this motherboard and udev is running perfectly. Besides it my root and normal group is enable. So usb is mounted only after a reboot.

Is it an issue caused in order of spliting any distro package or only a wrong fstab entry?

gerasimos_h · Posted: Wed Aug 14, 2013 9:07 pm Post subject:

There was an issue with hal which restored in SMS-2.0.5 after rebuilding hal package, so if you are on SMS-2.0.x (especially 2.0.4) you can try to upgrade hal package or the whole system and check if it's working...

gerasimos_h

vivanguarda · Member Joined: 01 May 2009 Posts: 98

Sorry, but in this system I am using SMS 2.0.5 and problem is occuring yet.

Besides it, I used to install slackpkg package, then if SMS is using the latest LTS linux kernel 3.4.55 should I config slackpkg for current or stable slackware version?

About upgrade whole sistem to solve an "automagic" mount issue cannot be a good idea so if SMS is using a kde 3.5.10 version at the moment of upgrading, kde4.X.X can conflict, was'n it?

gerasimos_h · Posted: Thu Aug 15, 2013 2:19 am Post subject:

When I said upgrading I meant SMS...
Is your SMS-2.0.5 an upgrade from an older version or a clean install?

Although SMS is based on slackware, I don't think slackpkg will help, as slackware ain't using 3.4.x kernel and current has a newer glibc....
In other words SMS has declined a lot from stable or current slackware tree...

So to confirm that's the same issue, when you open system:/media in konqueror is empty?

gerasimos_h

vivanguarda · Member Joined: 01 May 2009 Posts: 98