You are not logged in.
Pages: 1
Hi,
I am running KDE and having problems mounting USB devices via the KDE Device Notifier in the task bar. When I insert the USB stick there is the normal little popup giving me the option to open the flash drive in dolphin. When I click it, I get the following error:
"Could not mount the following device"
Mounting the device via terminal works fine. I also put my user into the "storage" group like the wiki tells me. Still no change.
Any ideas?
Offline
I also put my user into the "storage" group like the wiki tells me.
Have you logged out and back in?
never trust a toad...
::Grateful ArchDonor::
::Grateful Wikipedia Donor::
Offline
i42n wrote:I also put my user into the "storage" group like the wiki tells me.
Have you logged out and back in?
I even did a reboot. Does not help.
Last edited by i42n (2012-02-28 13:16:54)
Offline
Do you have a /media folder? Mine got deleted somehow a few days ago. Same symptoms. Restoring it was a nice quick fix.
Offline
Do you have a /media folder? Mine got deleted somehow a few days ago. Same symptoms. Restoring it was a nice quick fix.
Yes I have a /media folder. Mounting in terminal to /media/usb works fine. Only the KDE menu seems to have problems.
Offline
I just tried to mount the USB stick directly via dolphin (so not in the kde taskbar popup). This produces a better error message. Maybe this helps:
An error occurred while accessing 'Removable Media', the system responded: An unspecified error has occurred.: Not Authorized
That would point to the access rights problem according to the storage group. Do not know what to do any further.
Offline
You might be interested in this thread. I have a feeling your answer lies within.
Offline
Same problem here, and I've edited usr/share/polkit-1/actions/org.freedesktop.udisks.policy, and I've changed it to <allow_active>yes</allow_active>under the filesystem internal mount and eject. Yet dolphin continues to pop up this message when I use my usual openbox + slim. my .xinitrc has ck-launch-session openbox-session, and if I simply run startx without running slim at all, I don't have this problem.... dolphin mounts normally
So, since slim was just updated, it appears to be the problem...; I haven't tried replacing it with the .pacnew file, but it looks the same as the slim.conf . Think I might just use startx for now on though...
Any society that would give up a little liberty to gain a little security will deserve neither and lose both.
-Benjamin Franklin
The reasonable man adapts himself to the world; the unreasonable one persists in trying to adapt the world to himself. Therefore all progress depends on the unreasonable man.
-George Bernard Shaw
Offline
https://wiki.archlinux.org/index.php/Op … d-alone_WM
If you also use PolicyKit and D-Bus (e.g. for automatically mounting drives in Nautilus/GNOME) use:
exec ck-launch-session dbus-launch openbox-session
Note: dbus-launch must be placed after ck-launch-session or you will experience mounting problems.
Is this how your ~/.xinitrc looks like?
I have made a personal commitment not to reply in topics that start with a lowercase letter. Proper grammar and punctuation is a sign of respect, and if you do not show any, you will NOT receive any help (at least not from me).
Offline
Note: slim is ConsoleKit capable since version 1.3.3. Unless you happen to run an old version, you must no longer include ck-launch-session in your .xinitrc or slim.conf login_cmd.
These kind of changes without notifications to users cause headaches. Someone was kind enough to update the wiki!
Offline
Note: slim is ConsoleKit capable since version 1.3.3. Unless you happen to run an old version, you must no longer include ck-launch-session in your .xinitrc or slim.conf login_cmd.
I've been running 1.3.3 as "exec ck-launch-session dbus-launch openbox-session" with no problems...
Offline
Note: slim is ConsoleKit capable since version 1.3.3. Unless you happen to run an old version, you must no longer include ck-launch-session in your .xinitrc or slim.conf login_cmd.
These kind of changes without notifications to users cause headaches. Someone was kind enough to update the wiki!
You are my personal hero for today, I was suffering the same problem. Manifests itself as 2 CK sessions listed by ck-launch-session, with the wrong session being marked as active.
Last edited by crobe2 (2012-06-11 14:28:12)
Offline
Pages: 1