You are not logged in.

#1 2012-07-17 05:15:15

Ryan
Member
From: UK
Registered: 2012-07-17
Posts: 27

[SOLVED] Automount Problem

Hi. I have just tried Arch Linux for the first time. There are various minor tweaks and configurations I have dealt with but one seems to be unsolvable at this stage. I can't get automount of USB drives to work. In the wiki it says udisks should be all you need for this. I can manually mount drives without any problems but this obviously isn't convenient. The system sees the drives but no automount. I've been through a lot forum threads but haven't been able to solve this. USB drives do not show up at boot either. I do have a Wacom Cintiq which has it's tablet part connected via USB. That does work. My main reason for testing out Arch is that it happens to be a good distribution for graphics work if you want to always be up to date with the apps so as to be able to report any problems. Also, the closed code graphics drivers are there and up to date - very important if you do any 3D.

One more point is that I installed from the CD. Next install will be from net. I don't know whether that could solve the above described problem but from what I've read it seems that it does solve a few problems. However, first, I'm just using this install as a playground to check everything out.

Last edited by Ryan (2012-07-21 10:40:56)

Offline

#2 2012-07-17 05:22:15

ewaller
Administrator
From: Pasadena, CA
Registered: 2009-07-13
Posts: 20,727

Re: [SOLVED] Automount Problem

Are you using a desktop environment yet? Or are you working with a CLI on a console?
If you are using a DE, which one?  How are you starting it?
Is the Dbus daemon running? (Is it it your DAEMONS array in /etc/rc.conf ?)

Oh, and welcome to Archlinux smile


Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
The shortest way to ruin a country is to give power to demagogues.— Dionysius of Halicarnassus
---
How to Ask Questions the Smart Way

Offline

#3 2012-07-17 05:26:40

Inxsible
Forum Fellow
From: Chicago
Registered: 2008-06-09
Posts: 9,183

Re: [SOLVED] Automount Problem

try a helper like udiskie or devmon


Forum Rules

There's no such thing as a stupid question, but there sure are a lot of inquisitive idiots !

Offline

#4 2012-07-17 07:49:30

uzsolt
Member
Registered: 2012-06-13
Posts: 56

Re: [SOLVED] Automount Problem

I prefer udisks-glue.

Offline

#5 2012-07-17 07:52:48

DSpider
Member
From: Romania
Registered: 2009-08-23
Posts: 2,273

Re: [SOLVED] Automount Problem

Those external drives were formatted as NTFS, weren't they?

Install ntfs-3g and reboot.


"How to Succeed with Linux"

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

#6 2012-07-17 10:45:52

Ryan
Member
From: UK
Registered: 2012-07-17
Posts: 27

Re: [SOLVED] Automount Problem

Thanks for the replies. I've used KDE and LXDE. External drives are all fat32. Ideally I would like to try Gnome 3 but that's no go at the moment - I need to test that further. KDE and LXDE are working fine apart from the automounting problem. dbus is in daemons array in /etc/rc.conf. I've tried various ways of starting the desktop environments. I'm now doing it from /etc/rc.conf. The other ways of starting the desktops cause different problems for the desktops. rc.conf always works, at least for KDE and LXDE.

It seems dbus is starting then failing at the moment. Before I go any further trying to pinpoint the problem, is there any order in which dbus should be entered within the Daemons array in rc.conf? Also, I notice there are two versions of Udisks - Udisks and Udisks2. I have both of these installed.

Another point worth mentioning is that I'm running the NVidia driver 302.17-2. Maybe I should drop out of using that before I go any further but I've not noticed any problems with it. Possibly the problem with Gnome 3 though.

Last edited by Ryan (2012-07-17 10:51:19)

Offline

#7 2012-07-17 11:06:25

Ryan
Member
From: UK
Registered: 2012-07-17
Posts: 27

Re: [SOLVED] Automount Problem

OK, I'm going to have to look into this further. It seems that the Udisks situation is not good.

As far as what I want. I actually quite like Gnome 3 but wouldn't miss it. I'm not keen on KDE. It seems a bit buggy and messy. I like LXDE. I run a Debian system for audio production with LXDE. It's nice and simple. All I need. If I can set up an Arch system with LXDE without these problems (it's looking like a udisks issue) then I'd be happy.

Offline

#8 2012-07-17 11:49:16

lemons
Member
Registered: 2012-07-15
Posts: 19

Re: [SOLVED] Automount Problem

I had this problem for a while, XFCE automounts my USB's, but as far as something like DWM or Awesome, it's a no-go.

Offline

#9 2012-07-17 13:36:33

Ryan
Member
From: UK
Registered: 2012-07-17
Posts: 27

Re: [SOLVED] Automount Problem

It seems there are no problems with dbus here. Something else is causing the problem. I have no relevant eror messages or anything to post because I haven't really found anything yet.

I might try xfce. I never realised what a mess all these bloated desktop environments have become until I installed Arch to get back into the guts of things. I've been using a Debian system for audio with a simple setup of LXDE and Ardour as the DAW. Just alsa and jack handling audio. Not all this bloated DE dependency hell. My previous system for graphics was also Debian until Gnome 3 arrived in an update. Worked for a bit but then I ran into problems. As for Ubuntu, I ditched that a while back.

Offline

#10 2012-07-17 14:24:19

Trilby
Inspector Parrot
Registered: 2011-11-29
Posts: 30,554
Website

Re: [SOLVED] Automount Problem

I don't think you can launch DE's from rc.conf.  There are several display managers you can run from rc.conf's daemon array that will - in turn - launch your DE.  But which DM are you using? (ie, what's in your daemons array).

Also, to be sure dbus is running properly check top or htop once you are in your DE.  You should see three dbus processes: one "dbus-daemon" each for 'root' and 'dbus' users, and one "dbus-launch" for your user.  The daemons array of rc.conf only launches one of these.  Your display manager will/should launch the other two by using either the `dbus-launch` command with  your DE or by calling ck-launch-session which in turn calls dbus-launch.


"UNIX is simple and coherent" - Dennis Ritchie; "GNU's Not Unix" - Richard Stallman

Offline

#11 2012-07-17 16:12:39

Ryan
Member
From: UK
Registered: 2012-07-17
Posts: 27

Re: [SOLVED] Automount Problem

OK. Thanks for that.

Htop shows me what you say - there is only one dbus process running. However, I get problems trying to start any desktop environment if I don't have dbus in the rc.conf array. Slim is at the end of the array but the rest is just as it was originally.

ck-launch-session appears to be working as far as I can see but I'm not sure exactly what I'm looking for anyway.

The same scenario seems to be happening no matter what DM or DE I use, except anything to do with Gnome. None of that works at all. Currently I'm using Slim and Xfce. Xfce is the desktop I want now, after having tried it. It fits my needs. I've seen that Kde and Xfce allow me to control auto-mounting of external media but that's not my problem.

I can't really find many errors that show me anything either. Another problem is that I've had a lot of random stuff which I've never seen before. I boot the computer and a DM fails. I boot again, it doesn't etc. This isn't a hardware problem. It's only Arch at the moment that is doing this.

I think I need to drop out of using the Nvidia driver before I go further to simplify things down.

If I can't get further I'll eventually try a reinstall from net but I'm not so bothered looking into all this anyway. That way I learn.

Last edited by Ryan (2012-07-17 16:17:53)

Offline

#12 2012-07-17 16:24:26

ewaller
Administrator
From: Pasadena, CA
Registered: 2009-07-13
Posts: 20,727

Re: [SOLVED] Automount Problem

Ryan wrote:

...Currently I'm using Slim and Xfce. Xfce is the desktop I want now, after having tried it. It fits my needs. I've seen that Kde and Xfce allow me to control auto-mounting of external media but that's not my problem.

Wait, maybe I have misunderstood. 
You say you can auto-mount external media.  Do you mean Data CDs and DVDs, or do you mean things like USB thumb drives.
Assumed you meant that, if you plug in a thumb drive, it does not automount.

Are you, perhaps, describing problems with fixed, partitioned disks that happen to have a USB interface?


-----



Failing all of that, if you are having trouble mounting USB thumb drives (as I originally thought), please post your ~/.xinitrc


Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
The shortest way to ruin a country is to give power to demagogues.— Dionysius of Halicarnassus
---
How to Ask Questions the Smart Way

Offline

#13 2012-07-17 16:52:11

Ryan
Member
From: UK
Registered: 2012-07-17
Posts: 27

Re: [SOLVED] Automount Problem

Hi.

Probably my description wasn't too clear there. What I meant was that I see those controls in Kde and Xfce to allow or disallow auto-mounting of various devices but those settings have no effect. I still can't auto-mount any external storage devices that are connected via usb. I can manually mount them though. The problem applies to devices whether CD/DVD (I have a USB DVD drive), thumb drives or standard external USB drives. Basically any drive that gets connected via USB. It's not a USB problem though. My computer is quite simple. I have no internal drives except two SSD drives as system drives. Only one is currently attached.

I'll spend some time looking into the various ways of starting the desktop but I've been through a lot of that already. I think this is where the problem lies though.

I've also cleaned out everything I don't want. There is no Gnome or Kde packages at all now.

When I first installed. I used the CD install. I looked at the news section on this site and as far as I know I went through the various updating problems correctly because you get these when you use the CD install.

Offline

#14 2012-07-17 18:09:01

Trilby
Inspector Parrot
Registered: 2011-11-29
Posts: 30,554
Website

Re: [SOLVED] Automount Problem

Ryan, this is not likely a problem with the installation process.  Arch does not automount media by default.  There are a number of ways to set up automounting (and a good wiki article on them), but this must be configured.

Most of those methods require a dbus-session to be running, some also require console-kit.  I thought the latter started the former, but I could be wrong on that: I don't use console kit, so I wouldn't really know.

I think your suspicion is correct that the problem lies in how the DE is started.  This is where ewaller's request for your .xinitrc comes in, as this is the first file to check.


"UNIX is simple and coherent" - Dennis Ritchie; "GNU's Not Unix" - Richard Stallman

Offline

#15 2012-07-17 18:57:21

Ryan
Member
From: UK
Registered: 2012-07-17
Posts: 27

Re: [SOLVED] Automount Problem

Hi Trilby.

I've tried a lot of .xinitric variations that I'm reading about. I haven't got one particular one I'm sticking with so I haven't posted what's in that. This file is obviously key though. I realize that. If I get further with that I'll post about it.

Offline

#16 2012-07-17 21:46:09

Ryan
Member
From: UK
Registered: 2012-07-17
Posts: 27

Re: [SOLVED] Automount Problem

The problem is described here:

https://bbs.archlinux.org/viewtopic.php?id=144566

It appears this person has been using Arch for years but the problem only occured with a fresh install. I get the same results from commands to test things and the DM or DE you use is irrelevant. Another person on this thread said they got this problem after a fresh install. It doesn't sound like they were new to Arch either so it seems the problem was new to them.

I haven't been able to find any solution.

Offline

#17 2012-07-20 08:48:30

Ryan
Member
From: UK
Registered: 2012-07-17
Posts: 27

Re: [SOLVED] Automount Problem

An update on this problem.

I'm updated with systemd. I've looked through some of the wiki about systemd.

I can start dbus from rc.conf array and I can start it manually. In htop I see /usr/bin/dbus/daemon.

If I try to perform any udisks command I get:

(udisks:2118): udisks-WARNING **: Couldn't connect to system bus: Failed to connect to socket /run/dbus/system_bus_socket: No such file or directory

If I do systemd-analyze I get the output below so what is the problem here? It seems to be with systemd:

Traceback (most recent call last):
  File "/usr/bin/systemd-analyze", line 284, in <module>
    bus = dbus.SystemBus()
  File "/usr/lib/python3.2/site-packages/dbus/_dbus.py", line 194, in __new__
    private=private)
  File "/usr/lib/python3.2/site-packages/dbus/_dbus.py", line 100, in __new__
    bus = BusConnection.__new__(subclass, bus_type, mainloop=mainloop)
  File "/usr/lib/python3.2/site-packages/dbus/bus.py", line 122, in __new__
    bus = cls._new_for_bus(address_or_type, mainloop=mainloop)
dbus.exceptions.DBusException: org.freedesktop.DBus.Error.FileNotFound: Failed to connect to socket /run/dbus/system_bus_socket: No such file or directory

Last edited by Ryan (2012-07-20 08:49:50)

Offline

#18 2012-07-20 12:06:18

mariusmeyer
Member
From: Norway
Registered: 2009-04-25
Posts: 244

Re: [SOLVED] Automount Problem

Do you actually have a /run folder? Is it a symlink to /var/run?

Also, the way you start your DE in .xinitrc REALLY matters, for example you need ck-launch-session before dbus-launch and no if-else block before it etc etc. If you do this right then it will work, and there are many threads on these boards that contain the "right way" to do it smile

Last edited by mariusmeyer (2012-07-20 12:07:43)

Offline

#19 2012-07-20 12:47:07

Ryan
Member
From: UK
Registered: 2012-07-17
Posts: 27

Re: [SOLVED] Automount Problem

I have a run folder and there is no simlink.

I'm actually getting different results from those previous commands. Possibly I started dbus manually last time when I ran those tests. Can't remember but now I get this from udisks commands or at least similar Message did not recieve a reply depending on what command I did:

(udisks:753): udisks-WARNING **: Couldn't enumerate devices: Message did not recieve a reply (timeout by message bus)

And with systemd-analyze I get what this person here describes:

https://bbs.archlinux.org/viewtopic.php?id=144396

ck-launch-session and dbus-launch do nothing in .xinitrc. dbus can only be launched from the rc.conf or manually and console kit gets launched anyway without it being in .xinitrc.

Last edited by Ryan (2012-07-20 12:48:01)

Offline

#20 2012-07-20 13:03:57

Trilby
Inspector Parrot
Registered: 2011-11-29
Posts: 30,554
Website

Re: [SOLVED] Automount Problem

Ryan, dbus must be launched from rc.conf and from .xinitrc as I have mentioned above.

You should have three dbus processes running (as I have mentioned above).

If you want to solve this, don't be so secretive about what's in your .xinitrc.

Last edited by Trilby (2012-07-20 13:04:55)


"UNIX is simple and coherent" - Dennis Ritchie; "GNU's Not Unix" - Richard Stallman

Offline

#21 2012-07-20 13:19:40

Ryan
Member
From: UK
Registered: 2012-07-17
Posts: 27

Re: [SOLVED] Automount Problem

Trilby. I have already tried that. What exactly should be in my .xinitrc to confirm this?

My debian system only ever has one dbus process running same with a Ubuntu system.

Offline

#22 2012-07-20 13:26:28

Trilby
Inspector Parrot
Registered: 2011-11-29
Posts: 30,554
Website

Re: [SOLVED] Automount Problem

Ryan wrote:

Trilby. I have already tried that. What exactly should be in my .xinitrc to confirm this?

You have tried it, but aparently not correctly as it did not work.  I don't know exactly what should be in your xinitrc until I see what is currently there.

You should use some form of "dbus-launch" on the line that launches your WM.  But when people unfamiliar with the process try this, they often do it wrong at first.

But if you are sure you haven't done anything wrong and you don't want to be forthcoming with specifics on what you have in your xinitrc, then all I can do is wish you luck.


"UNIX is simple and coherent" - Dennis Ritchie; "GNU's Not Unix" - Richard Stallman

Offline

#23 2012-07-20 13:49:45

Lennie
Member
From: Sweden
Registered: 2011-10-12
Posts: 146

Re: [SOLVED] Automount Problem

Wiki wrote:

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. You should still have dbus-launch in your login_cmd,

According to the wiki page about Slim you should have this line in your .xinitrc: (If you're still using Slim and Xfce.)

exec dbus-launch startxfce4

Delete everything else (after the line #!/bin/bash) to see that this works, before adding anything back.

This is just to start your DE in the correct way. Automounting doesn't happen automatic because of this. For automounting I think you need to change the rules for udisks2. (I don't know about Xfce, I have Openbox.)

Offline

#24 2012-07-20 14:40:33

Ryan
Member
From: UK
Registered: 2012-07-17
Posts: 27

Re: [SOLVED] Automount Problem

I've seen that in the Slim wiki.

However, I also notice that in the xfce wiki it has what I've added below. If I use this .xinitrc, I get to the desktop and I have three dbus processes. However, I still have no automount and get those last errors I mentioned. I have also looked at the rules for udisks2 and tried changing those to what I've read - in particular from info linked to from the xfce wiki but no change to the problem. If I remove the "--with-ck-launch" I end up at a blank screen after logging into Slim and an empty .xinitrc file:



"Note: dbus-launch should actually be called after launching ConsoleKit, otherwise there will be authorization problems when mounting disks as a regular user, see FS#25031. For a temporary workaround you can edit the xinitrc.d script at the beginning of the file as follows, and keep an eye on the evolution of the bug report (and possibly vote it):

~/.xinitrc [temporary workaround]

#!/bin/sh

if [ -d /etc/X11/xinit/xinitrc.d ]; then
  for f in /etc/X11/xinit/xinitrc.d/*; do
    # Do not launch dbus before ConsoleKit (FS#25031)
    #[ -x "$f" ] && . "$f"
    [ "$f" -ne "/etc/X11/xinit/xinitrc.d/30-dbus" ] && [ -x "$f" ] && . "$f"
  done
  unset f
fi

exec startxfce4 --with-ck-launch

There is still no need to start dbus-launch explicitly since startxfce4 takes care of doing that anyway."

Last edited by Ryan (2012-07-20 14:51:11)

Offline

#25 2012-07-20 15:50:56

Lennie
Member
From: Sweden
Registered: 2011-10-12
Posts: 146

Re: [SOLVED] Automount Problem

From Wiki about Xfce, just above your quote:

SLiM is also ConsoleKit capable since version 1.3.3. Unless you happen to run an old version, you must not use --with-ck-launch from your .xinitrc or slim.conf login_cmd.

So delete --with-ck-launch, otherwise Consolekit is started twice, and that gives permission problems.

If that doesn't work I think you should try to get it working without Slim, in case Slim is the problem...

Offline

Board footer

Powered by FluxBB