If I plug in a USB key, Thunar shows it fine in its side pane, but if I click on it, it says"Failed to mount. Not Authorized".
Mountbox works OK, but I don't want to be root just to access my USB devices.

Funny thing is that Thunar mounts CDs and DVDs just fine, but then it is unable to eject them, giving the same error as above mentioned. While the eject command in a terminal works fine without root privileges.

So recapitulating... In Thunar, I can mount CDs and DVDs, but I can't eject them. While USB's I can not even mount. All giving the same error message:"Failed to mount/eject. Not Authorized."

Now, I guess I should adjust some user/group permissions to make this work, but I don't know which... Any idea?

No idea about thunar and such, but with something like users can mount and umount.
Another workaround would be using pmount.
I would check for plugdev group, but really am not sure.

Thank you for your response.

plugdev group seems setup fine to me... I have pmount installed, but don't know what to do with it... And I am not sure it is a good idea to use fstab for mounting pluggable devices...

hm... I did a search around in Google and it seems like it is an issue between Slim and PolicyKit... In Debian, some people solved the problem by replacing it with gdm3. I still didn't try it, as it brings a lot of Gnome dependencies along with it... And I still haven't found a way to fix it with slim.

And it really is the truth!

According to
========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"http://forum.xfce.org/viewtopic.php?id=7149"
linktext was:"this thread"
====================================
, Slim doesn't say to PolicyKit that the logged in user is an active user, hence the"not authorized" error.
So I tried to install LightDM, as suggested in the same thread, and now everything works just as it should.

I think this fact makes Slim a really bad choise for a DM. Are there any plans to replace it with something else in the future?

"I have pmount installed, but don't know what to do with it..."

just like mount:
pmount /dev/sdc1 /media/disk
pumount /media/disk

" And I am not sure it is a good idea to use fstab for mounting pluggable devices..."

Why that?

nadir wrote:

"I have pmount installed, but don't know what to do with it..."

just like mount:
pmount /dev/sdc1 /media/disk
pumount /media/disk

Yes, but I want a quick and easy GUI solution...

nadir wrote:

" And I am not sure it is a good idea to use fstab for mounting pluggable devices..."

Why that?

Well, I am not really that tehcnical (I am just a literature student :-p), but it is stated even in fstab itself... I guess because those devs don't have a fixed dev name or something.

Anyway, I fixed this by changing the DM. Which is why I hope the next version of antiX will have something else than Slim, by default.

franko, the next version of antiX will not have thunar, but spacefm and we will keep slim.

If users decide to install thunar, they should also install LightDM if thunar still gives the errors you got.

No PolicyKit, too?

As I already said, I am not all that technical... But I always thought of PolicyKit as an important part of a modern GNU/Linux system. So I still feel a bit concerned about Slim not talking to it correctly (if at all). And the Ironic thing is that SLiM declares itself to be a"desktop-independent graphical login manager", and yet it is obviously a really bad choice for users of the most popular DEs, like Gnome or Xfce... or even for anyone using Thunar (and who knows what other FMs, too) inside any other desktop, not necessarily Xfce.

I also think the DM is an important part of a distro. And it is crazy to expect the users to change the DM, just to be able to use a different file manager.

Sorry for the off topic...

"but it is stated even in fstab itself..."

I ain't got it stated in my fstab(s).

changing dev's? Well: probably. But i can't say that i got a problem with that.

PolicyKit will be included on antiX-full (but not base). IMO the problem lies with thunar (and the latest pcmanfm) 'forcing' policykit usage. Thunar used to work fine on antiX using slim until fairly recently.

BTW on my box, lightdm has issues in causing a black screen at login when running live.

anticapitalista wrote: BTW on my box, lightdm has issues in causing a black screen at login when running live.

I can seccond this for remasters that I have done. I am not exactly sure of the cause yet, however removing all grub cheat codes allow lightdm to display properly

nadir wrote:"but it is stated even in fstab itself..."

I ain't got it stated in my fstab(s).

changing dev's? Well: probably. But i can't say that i got a problem with that.

The first line in my fstab file states:"# Pluggable devices are handled by uDev, they are not in fstab"
But I must confess I never really tested it... __{{emoticon}}__
But maybe naming the devices by UUID (like in Ubuntu, for example) would be a safer way to do it in fstab?

@anticapitalista

Slim on base and LigtDM (or whatever else) on full?
It has no sense adding PolicyKit along with a DM unable to talk to it.

It is obvious that both DMs have their issues... Are there no third options? Except GDM and KDM, as I guess they are pretty much not in line with the antiX concepts... Maybe choosing one and then trying to fix all the known issues would be best. I really see no reason why Slim wouldn't communicate to PolicyKit, but then again, I am not a coder and am therefore unable to intervene directly in it. :-/

Dave wrote: I can seccond this for remasters that I have done. I am not exactly sure of the cause yet, however removing all grub cheat codes allow lightdm to display properly

Lightdm needs dbus running (unlike slim) so you cannot use the antiX=D cheat (using antiX=LMX is ok).