You are not logged in.
I asked this in one of the threads, but I think it got buried. This is just for my own curiosity and general knowledge...
(I did have some automount problems that cropped up recently, but not sure whether they were a result of the hal/policykit thing, and they seem to have been resolved without much work on my part.)
There have been a slew of them, and it seems most of them are "automount used to work but now doesn't". Just for fun I looked at the wiki page for hal, and almost none of it applied to what I did when building my system (where I essentially just cookbooked the beginner's guid), but automount, except for briefly, has never been a problem.
So I'm trying to understand, is hal as recently updated broken, or has it been changed in a way (intentionally) such that these additional steps that were previously not required now are required, or were people getting lucky before with not having to do these steps in some cases, or what?
Just trying to understand...
Offline
PolicyKit is now part of the freedesktop.org specification and is part of HAL. Every distro is going to have to deal with this one way or another when they upgrade their version of X to anything current.
You're seeing a bunch of threads about this because users aren't using the search function, not reading documentation, and not searching the web. The answer to this problem was posted in the forums months ago. The current HAL has been in testing since December of last year.
Offline
You're seeing a bunch of threads about this because users aren't using the search function, not reading documentation, and not searching the web.
And because they are unconvinient with all these changes. Linux on the desktop? Great. Wake me up when its ready.
There shouldn't be any reason to learn more editor types than emacs or vi -- mg (1)
[You learn that sarcasm does not often work well in international forums. That is why we avoid it. -- ewaller (arch linux forum moderator)
Offline
PolicyKit is now part of the freedesktop.org specification and is part of HAL. Every distro is going to have to deal with this one way or another when they upgrade their version of X to anything current.
You're seeing a bunch of threads about this because users aren't using the search function, not reading documentation, and not searching the web. The answer to this problem was posted in the forums months ago. The current HAL has been in testing since December of last year.
But, and this is just to further my understanding, how come I'm not having to do this? None of the proposed solutions look like anything I remember doing when I built my system, yet I haven't had the problem.
Offline
skottish wrote:PolicyKit is now part of the freedesktop.org specification and is part of HAL. Every distro is going to have to deal with this one way or another when they upgrade their version of X to anything current.
You're seeing a bunch of threads about this because users aren't using the search function, not reading documentation, and not searching the web. The answer to this problem was posted in the forums months ago. The current HAL has been in testing since December of last year.
But, and this is just to further my understanding, how come I'm not having to do this? None of the proposed solutions look like anything I remember doing when I built my system, yet I haven't had the problem.
Are you psychic, or did you consult any before installation? Are you a member of the Illuminati? NSA? All of these things will prepare you for the "future".
The last three or four major problems have been blown way out of proportion. You may have skirted some of them simply by having a driver installed that others didn't. Maybe there are things that you don't use that others do.
When I upgraded to xorg-server 1.5.2, I lost my keyboard and mouse because they weren't defined in xorg.conf. I installed "xf86-input-evdev" and everything works. If I would have had these things set up in xorg.conf, I may not have even known that there was an issue until I read the 50 identical threads here.
Offline
I didn't edit Policykit.conf (still empty) . I just added to '/etc/pam.d/login'
session optional pam_ck_session.soand added 'ck-launch-session' before awesome in ~/.xinitrc and everything worked again(namely mounting usb) . Is that normal ?
I thought Consolekit was needed with the new 'hal' and now I see a lot of Policykit talk .
English is not my native language .
Offline
arch_nemesis wrote:skottish wrote:PolicyKit is now part of the freedesktop.org specification and is part of HAL. Every distro is going to have to deal with this one way or another when they upgrade their version of X to anything current.
You're seeing a bunch of threads about this because users aren't using the search function, not reading documentation, and not searching the web. The answer to this problem was posted in the forums months ago. The current HAL has been in testing since December of last year.
But, and this is just to further my understanding, how come I'm not having to do this? None of the proposed solutions look like anything I remember doing when I built my system, yet I haven't had the problem.
Are you psychic, or did you consult any before installation? Are you a member of the Illuminati? NSA? All of these things will prepare you for the "future".
The last three or four major problems have been blown way out of proportion. You may have skirted some of them simply by having a driver installed that others didn't. Maybe there are things that you don't use that others do.
LOL OK, OK. The tone of the threads I read led me to believe that this was a problem everyone should have been experiencing except those who had religously followed the HAL wiki page (I didn't) or knew enough about what was coming down the pipe to understand what the problem was immediately (I wouldn't), so that was the source of my question. I get it now. ![]()
Offline