Arch Linux

pogeymanz

Member

Registered: 2008-03-11

Posts: 1,020

[SOLVED]Thunar can't mount stuff anymore...

This is what happens when I click my USB stick in Thunar:

Xlib:  extension "Generic Event Extension" missing on display ":0.0".
Xlib:  extension "Generic Event Extension" missing on display ":0.0".
Xlib:  extension "Generic Event Extension" missing on display ":0.0".
Xlib:  extension "Generic Event Extension" missing on display ":0.0".
Xlib:  extension "Generic Event Extension" missing on display ":0.0".
Xlib:  extension "Generic Event Extension" missing on display ":0.0".
org.freedesktop.hal.storage.mount-removable no <-- (action, result).

What gives?

EDIT: Thanks

Last edited by pogeymanz (2009-02-13 01:39:52)

Inxsible

Forum Fellow

From: Chicago

Registered: 2008-06-09

Posts: 9,183

Re: [SOLVED]Thunar can't mount stuff anymore...

Look up the HAL wiki and do what it says in the Troubleshoot section.

---

Forum Rules

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

dvh

Member

Registered: 2007-10-06

Posts: 41

Re: [SOLVED]Thunar can't mount stuff anymore...

I tried the fix...inserting this line:

<merge key="volume.ignore" type="bool">false</merge>

into file /etc/hal/fdi/policy/preferences.fdi,

but I still get the error shown above.  Are there some specific permissions that are required on the file?

-dvh

soupcan

Member

From: ?

Registered: 2008-10-25

Posts: 268

Re: [SOLVED]Thunar can't mount stuff anymore...

I tried the fix...inserting this line:

<merge key="volume.ignore" type="bool">false</merge>

into file /etc/hal/fdi/policy/preferences.fdi,

but I still get the error shown above.  Are there some specific permissions that are required on the file?

-dvh

Try what I did here.

dvh

Member

Registered: 2007-10-06

Posts: 41

Re: [SOLVED]Thunar can't mount stuff anymore...

Thanks, soupcan.  I tried the version of the PolicyKit file that you ultimately used, and it seems to work.   Strange thing is that i previously fixed this just a couple of days ago with a different recommended version, but that seemed to stop working after the next reboot.  Maybe it is the HAL restart sequence that makes it work?  I will try to reboot and see if the problem returns.

-dvh