Bug 402433

Summary: PolicyKit 0.8 breaks hal 0.5.9 after 2008-06-21 GNOME STABLE update
Product: [openSUSE] openSUSE 10.3 Reporter: Gilles Sabourin <sabourin.gilles>
Component: GNOMEAssignee: Stanislav Brabec <sbrabec>
Status: RESOLVED FIXED QA Contact: E-mail List <qa-bugs>
Severity: Major    
Priority: P5 - None    
Version: Final   
Target Milestone: ---   
Hardware: x86   
OS: openSUSE 10.3   
Whiteboard:
Found By: Beta-Customer Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---

Description Gilles Sabourin 2008-06-20 23:39:15 UTC
Please provide hal 0.5.11 in GNOME repository since hal 0.5.9 from official oss repository is broken after this update, and as a result, many other things like : notification, sound, automounter, CpuFreq ...
Comment 1 Stanislav Brabec 2008-06-23 12:42:13 UTC
Well, GNOME:STABLE was repopulated few days ago and dependencies may be imcomplete.

But update of a base package like hal is a very fragile issue, so I would prefer to fix problems caused by GNOME update, if it is possible.

Could you be more specific, how other stuff was broken by not updating hal?
Comment 2 Gilles Sabourin 2008-06-23 18:00:04 UTC
stuff that is relying on notification messages from hal does not work since it does not receive hal messages anymore.

Hence you can put a dvd, an USB memory stick, they won't be automounted anymore. CpuFreq is also relying on HAL and does not work : kpowersave is greyed and CPU speed is blocked at slow speed.

HAL is Hardware Abstraction Layer. It works with dbus and hotplug to enable plug-and-play to work well. Missing HAL implies that sound card are not detected and that you won't have sound.

I suggest you to read more about Linux architecture.
Comment 3 Gilles Sabourin 2008-06-23 18:03:01 UTC
I have manually upgraded to hal 0.5.11 with one click install from Kukawka repository and this have solved all theses problems.
Comment 4 Stanislav Brabec 2008-06-24 11:37:56 UTC
I know, what HAL is. I don't understand, how GNOME:STABLE can break hal, if it does not touch it in any way.

Could it be caused by PolicyKit? If yes, will reverting of PolicyKit to distro version fix the problem?
Comment 5 Stanislav Brabec 2008-06-24 12:09:16 UTC
Ah, sorry. It is mentioned directly in the summary.

Instead of update of hal (which could have tons of side effects, I removed PolicyKit from repositories. It was added in past to allow build on 10.1 and it was disabled for later versions.

During GNOME:STABLE clean-up, disabled flag was lost, and all packages were enabled again for all distros.

I reviewed the package list and disabled a several more packages.

I would prefer even more strict policy for GNOME:STABLE - allow only GNOME packages there.
Comment 6 Gilles Sabourin 2008-06-25 18:41:16 UTC
PolicyKit 0.8 removed from GNOME:STABLE for openSUSE 10.3? Not at all! Take your webpin page and query for it...

Comment 7 Gilles Sabourin 2008-06-27 15:52:16 UTC
PolicyKit 0.8 has been removed today. Bug report closed.
Comment 8 Anja Stock 2008-07-07 15:38:21 UTC
released