|
Bugzilla – Full Text Bug Listing |
| Summary: | hal-storage-mount-removable no <-- (action, result) | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE 10.3 | Reporter: | darren winter <sgt-d> |
| Component: | KDE | Assignee: | E-mail List <kde-maintainers> |
| Status: | RESOLVED DUPLICATE | QA Contact: | E-mail List <qa-bugs> |
| Severity: | Major | ||
| Priority: | P2 - High | CC: | hatono, hugo.costelha |
| Version: | Beta 3 | ||
| Target Milestone: | --- | ||
| Hardware: | 64bit | ||
| OS: | openSUSE 10.3 | ||
| Whiteboard: | |||
| Found By: | --- | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
|
Description
darren winter
2007-09-08 18:00:05 UTC
my brother's devices all seem to work fine in gnome. so, this problem is definitely related to kde or one of its components. after my brother's gnome session, all devices work now in gnome and kde. It happens to me too. Try the following. Boot normally into KDE and check if it works. Also check for instance if you can "Set CPU frequency policy" in kpowersave (I can't). If nothing works, logout, restart your XServer (not sure this is needed), and login again. Check if it works now. In my case, it works if I restart X. It seems that some boot dependency is missing and KDE/KDM?! cannot live with it. My case is a 32bit installation/pc. It happens to me too, and I also found the devices mounted find in root.
I guess this problem is related to permission in handling devices in hal deaemon.
In my system, everything has become working fine after setting as follows in /etc/Policykit/Policykt.conf.
<config version="0.1">
<match user="userid">
<return result="yes"/>
</match>
</config>
Notes: userid is your user ID in your system.
But everything is permitted by this setting includeing suspend2disk.
Some limitation may be required to normal users.
good information here. in my brother's case, all he had to do was login to gnome and access all of his devices one time. after that he rebooted and they have all been working fine in kde ever since that. very weird. Regarding Comment #3, there is no need to restart X, logging out and logging in to KDE makes it all work. #4 (above) - Itsuo Hatono, thank you! tonight i got hit with this stupid HAL problem and the only thing that worked was what you had suggested, followed by a reboot. thanks! technical note, the correct "case" of this file is: /etc/PolicyKit/PolicyKit.conf thanks again! -d Might it have something to do with autologin? Beacause it seems to me that without auto-login it works allways. Then again, without auto-login, kde itself is started later (since the user has to type his password) giving more time to the boot process. I updated to the latest factory, rebooted once, and it has not happend, under the same conditions as when happened previously. I will try a few more boots and reboots during the day and see if it still happens. Sounds like a duplicate of #309171 *** This bug has been marked as a duplicate of bug 309171 *** so far, this problem seems fixed with rc1. i have been seeing some weirdness for the last few releases tho... and it may still affect rc1, i will know more in the next day or so. so, the possible "new" problem... when i boot up, i auto login to kde, then i go to work. from there i use freenx to connect to my box at home, well, when the bosses aren't looking. so i work remotely for awhile... when i'm done, i tell it to terminate the connection. when i get home, i can't access any of my media, rom or usb. the only thing that seems to get me back to normal it is to reboot. anyone else seeing this problem? i will search bugzilla and possibly open a new report. reported as bug 327614. |