| Summary: | sys-apps/hal-0.5.12_rc1-r5 conf changes break X | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Mark Nowiasz <mark+gentoobugs> |
| Component: | [OLD] Core system | Assignee: | Daniel Gryniewicz (RETIRED) <dang> |
| Status: | RESOLVED FIXED | ||
| Severity: | critical | CC: | alessandro.rosetti, daggs, dawnstyle, Dessa, freedesktop-bugs, howard_b_golden, jcallen, jeremy.william.murphy, mitaspiotr, nick.novikov, rb6, sysrqalt |
| Priority: | High | Keywords: | PMASKED |
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Bug Depends on: | |||
| Bug Blocks: | 271833 | ||
| Attachments: |
old (-r4) hal.conf
r5 hal config new patch |
||
|
Description
Mark Nowiasz
2009-05-30 07:33:28 UTC
Similaly. x11-base/xorg-server-r6, nvidia-drivers-180.60, ~amd64... I have the same problem with hal -r5! ~amd64, nvidiadrivers-185.18.10, xorg-server-1.6.1.901-r3 &co same here xorg 1.5.3-r6, amd, ati radeon svn. I think it is related to the conf file which has couple of lines removed from *** Bug 271851 has been marked as a duplicate of this bug. *** Created attachment 192992 [details]
old (-r4) hal.conf
for those who want their keyboard back without waiting a patch/update, here is attached my /etc/dbus-1/system.d/hal.conf otherwise, you may also want to emerge =sys-apps/hal-0.5.12_rc1-r4 etc-update and merge conf file as suggested emerge hal etc-update and refuse the update. Could someone with this problem please post the USE flags they have set on hal, and the hal.conf that got installed? This is working fine for me. Created attachment 193031 [details]
r5 hal config
USE="X acpi crypt -apm -consolekit -debug -dell -disk-partition -doc -laptop -policykit (-selinux)
Okay, next question: Are you all in the plugdev group? -r4 was mistakenly letting everyone access HAL. -r5 is back to allowing only plugdev. (In reply to comment #9) > Okay, next question: Are you all in the plugdev group? -r4 was mistakenly > letting everyone access HAL. -r5 is back to allowing only plugdev. > Keyboard and mouse stops working yet when xdm starting... yep, I'm in plugdev and have the same issue. User root should be in group plugdev too, so xdm will start without problems Is this bug only about keyboard/mouse not working? If so, why was 271851 marked as duplicate of it? It seems to me as these are two separate issues (but I'm not an expert ;) ). (In reply to comment #13) > Is this bug only about keyboard/mouse not working? If so, why was 271851 marked > as duplicate of it? It seems to me as these are two separate issues (but I'm > not an expert ;) ). No, this bug is about all issues with X caused by the new hal.conf changes. Summary adjusted. (In reply to comment #12) > User root should be in group plugdev too, so xdm will start without problems > Does putting root in plugdev actually fix it? I'm in the process of setting up a -policykit test box to see if I can reproduce this. (In reply to comment #15) > > User root should be in group plugdev too, so xdm will start without problems > Does putting root in plugdev actually fix it? Yes it does, xdm starts normally. Hi On my computer (x86 ~arch) X and gdm launch 10 seconds and after crash, and put this error in "/var/log/Xorg.0.log" : Backtrace: 0: /usr/bin/X(xorg_backtrace+0x37) [0x812744f] 1: [0x8510ec0] Fatal server error: Caught signal 11. Server aborting ------------------------------------------------- But root was not in plugdev group. Now I put it in !! I've keep sys-apps/hal-0.5.12_rc1-r4 for the moment because everything works. (In reply to comment #16) > (In reply to comment #15) > > > User root should be in group plugdev too, so xdm will start without problems > > Does putting root in plugdev actually fix it? > > Yes it does, xdm starts normally. > IMO, this is a workaround for a bug. Requiring root to be in _any_ group for things to work makes no sense. I believe the code should be fixed to require group plugdev OR root. Until this is changed, I request that this version stay masked. Thanks. Created attachment 193100 [details, diff] new patch (In reply to comment #18) > (In reply to comment #16) > > (In reply to comment #15) > > > > User root should be in group plugdev too, so xdm will start without > > > > problems > > > Does putting root in plugdev actually fix it? > > > > Yes it does, xdm starts normally. > > > IMO, this is a workaround for a bug. Requiring root to be in _any_ group for > things to work makes no sense. I believe the code should be fixed to require > group plugdev OR root. Until this is changed, I request that this version stay > masked. Thanks. > Attached is a new, untested, version of 0001-plugdev-dbus-policy.patch that should make things Just Work™ by explicitly giving user="root" all the permissions given to group="plugdev". This is untested because I have USE=policykit set on my machine, which was *not* broken by this update. This is an ugly hack, but it should work. Okay, I've committed hal-0.5.12_rc1-r6 (also masked for now) that fixes this issue on all my systems. Could people try it, and make sure it works for them as well? (In reply to comment #20) > Okay, I've committed hal-0.5.12_rc1-r6 (also masked for now) that fixes this > issue on all my systems. Could people try it, and make sure it works for them > as well? > Thanks. It fixed the issue for my ~amd64 system, too. Now I have keyboard, mouse and touchpad working again. Thanks. I've unmasked -r6. Whatever you have done I have the same problem as before, my X won't start. Oh sorry. Nevermind. That was not hal causing the problem now. |
