Log inUsernamePassword
Log me on automatically each visit    
Register
Register
Log in to check your private messages
Log in to check your private messages
SMS Forum Index » General Discussion

Post new topic   Reply to topic
KDE issue when inserting a USB to the system
View previous topic :: View next topic  
Author Message
GCMartin
Junior Member


Joined: 20 Jun 2012
Posts: 14

PostPosted: Tue Jun 26, 2012 11:17 pm    Post subject: KDE issue when inserting a USB to the system Reply with quote

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

_________________
We are all related ...
Back to top
View user's profile Send private message
gerasimos_h
Site Admin


Joined: 09 Aug 2007
Posts: 1753
Location: Greece

PostPosted: Wed Jun 27, 2012 5:25 am    Post subject: Reply with quote

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

_________________
Superb! Mini Server Project Manager
http://sms.it-ccs.com
Back to top
View user's profile Send private message Visit poster's website
vivanguarda
Member


Joined: 01 May 2009
Posts: 98

PostPosted: Wed Aug 14, 2013 8:55 pm    Post subject: Reply with quote

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?
Back to top
View user's profile Send private message
gerasimos_h
Site Admin


Joined: 09 Aug 2007
Posts: 1753
Location: Greece

PostPosted: Wed Aug 14, 2013 9:07 pm    Post subject: Reply with quote

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

_________________
Superb! Mini Server Project Manager
http://sms.it-ccs.com
Back to top
View user's profile Send private message Visit poster's website
vivanguarda
Member


Joined: 01 May 2009
Posts: 98

PostPosted: Wed Aug 14, 2013 11:10 pm    Post subject: Reply with quote

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?
Back to top
View user's profile Send private message
gerasimos_h
Site Admin


Joined: 09 Aug 2007
Posts: 1753
Location: Greece

PostPosted: Thu Aug 15, 2013 2:19 am    Post subject: Reply with quote

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

_________________
Superb! Mini Server Project Manager
http://sms.it-ccs.com
Back to top
View user's profile Send private message Visit poster's website
vivanguarda
Member


Joined: 01 May 2009
Posts: 98

PostPosted: Tue Aug 20, 2013 5:24 am    Post subject: Reply with quote

Quote:
Is your SMS-2.0.5 an upgrade from an older version or a clean install?


I did a fresh SMS 2.0.5 install.

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


I can see hard disk partioned, but pendrive operates only if I had it attached after a reboot !
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic   Reply to topic    SMS Forum Index » General Discussion All times are GMT + 2 Hours
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You can attach files in this forum
You can download files in this forum

SMS - Superb! Mini Server Project © 2016
Powered by phpBB © 2001, 2002 phpBB Group
iCGstation v1.0 Template By Ray © 2003, 2004 iOptional