Hal-storage-mount-removable No <-- (action, Result)

Hi,

For reason un-known to me, after using a freshly install OpenSuSE 10.3 (64bit) for almost a week, my DVD and USB devices no longer accessible, but with a "cryptic" KDE error message:
hal-storage-mount-removable no <-- (action, result)

After some search, I found this:
http://www.suseforums.net/index.php?showtopic=39451

and applied this:
http://download.opensuse.org/repositories/...Factory/x86_64/

rebooted my system but still fails.


What's next? Please help!

Thanks.

I am also getting the same message when trying to access USB disks, I haven't tried a DVD/CD yet,

hal-storage-mount-removable no <-- (action, result)

Has anyone found a fix ? My USB disks were working before, USB disks mounted by FSTAB do not display the error message.

Mike

I am also getting the same message when trying to access USB disks, I haven't tried a DVD/CD yet,

hal-storage-mount-removable no <-- (action, result)

Has anyone found a fix ? My USB disks were working before, USB disks mounted by FSTAB do not display the error message.

Mike
[/b]

Posted the bug here:
https://bugzilla.novell.com/show_bug.cgi?id=333706

But I am very disappointed with OpenSuSE 10.3 64bit. I'm giving up, going to 32bit version.

Posted the bug here:
https://bugzilla.novell.com/show_bug.cgi?id=333706

But I am very disappointed with OpenSuSE 10.3 64bit. I'm giving up, going to 32bit version.[/b]

I don't think this is 64-bit specific .... ie ... I think the same problem exists in the 32-bit version.

I don't think this is 64-bit specific .... ie ... I think the same problem exists in the 32-bit version. [/b]

I had this problem in 32 bit. I read about a work-around and have applied it - so far, I have not had recurrence of the problem. Basically, I would get that hal error when trying to access data on usb, digital camera, cd/dvd media...

Unfortunately, I don't remember the source of this fix.

But, anyway, the suggestion was that starting services in parallel at boot time (as per default) may be causing the problem because certain dependencies are not being met correctly. The workaround is to turn off parallel loading.

Yast -> System -> /etc/sysconfig editor -> System -> Boot -> RUN_PARALLEL = no

Try it. There's nothing to lose, and it's safe.

Paul

I don't think this is 64-bit specific .... ie ... I think the same problem exists in the 32-bit version.
[/b]

Hi,

I have two machines in office with similar spec, the one that gives the same problem is the machine that install with the 10.3 64bit version. So is my notebook.

Whereas the machines installed with 10.3 32bit are working fine ... and much better than when they were in Kubuntu :lol:

possible resolution:
http://suseforums.net/index.php?showtopic=39451

quote name='Frasir' date='Oct 16 2007, 12:36 AM' post='249995'


But I am very disappointed with OpenSuSE 10.3 64bit. I'm giving up, going to 32bit version.
endquote
----------------------------------snip the partial quote
Had the same error after a fresh install of 10.3 64bit but I am glad to say I did a re-install slightly changing the install. I didn't request the repository(?) to be updated until after the install. There was a failure during the re-install but was able to recover and move forward. Now the users group and not just root has access to the plugin devices as I had in 10.2. I don't know what caused it the first time, but perhaps the extra step of loading the repositories other than those on the DVD confused Suse and mucked up the install. Go for a default install and add extra packages after.

OOPS: spoke too soon. I had a system lock running Azureus for an hour. Rebooting brought me to a crippled system which I then had to re-install update from 10.3 to 10.3. This brought me the same problem everybody else is having.

I noticed that the /etc/group file now has a polkituser:!:105: which did not exist in 10.2. I wonder if this has anything to do with the problem. I have doggedly tried to find the solution as this problem is widespread but I might just default to 10.2 until 10.3 has a solution or switch to Debian. Perhaps the solution is to install 10.3 without doing the updates. I think this is where I got to when the hotplug worked but the lockup rescue did the update and thus ruined what I had. I will try once more without an update then do them one at a time to try to narrow the problem. If not then onto debian which I'm sure has its set of problems.

It is possible to uninstall my updates?

Hi to All,

It seems to be a misconfigured (unconfigured) policy.

The file /etc/PolicyKit/PolicyKit.conf is empty!!!

I've added the following code:

<match action="org.freedesktop.hal.storage.mount-removable">
<match group="users">
<return result="yes" />
</match>
</match>

within the element <config>.

This means "permit the action org.freedesktop.hal.storage.mount-removable to everyone who belongs to the group "users"".

Now it works but not with NTFS disks, I suspect there is some other thing to tune with HAL configuration.

Good luck

Damiano

But I am very disappointed with OpenSuSE 10.3 64bit. I'm giving up, going to 32bit version.
[/b]

Come on, this is not a big problem ... just a little bit of patience.

I remember in the '94 I lost months to configure an X server on a pentium 60 (bugged!) with an old S3 Card... (without Internet forums!!!).