| Summary: | polkit won't start | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Pierre Fortin <pf> |
| Component: | RPM Packages | Assignee: | Mageia Bug Squad <bugsquad> |
| Status: | RESOLVED OLD | QA Contact: | |
| Severity: | normal | ||
| Priority: | Normal | CC: | mageia |
| Version: | Cauldron | ||
| Target Milestone: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | CVE: | ||
| Status comment: | |||
| Attachments: |
polkit.service
dbus.service |
||
|
Description
Pierre Fortin
2013-12-30 15:50:58 CET
Pierre Fortin
2013-12-30 15:51:53 CET
CC:
(none) =>
mageia Seems there is a bit of a problem on your machine relating to dbus or polkit in some capacity. It seems that while the polkit binary itself starts OK, and it acquires the name on the system bus, it seems that it doesn't actually show up ON the system bus. At least not according to systemd. Can you: 1. Reboot with " systemd.log_level=debug" on the kernel command line. 2. Provide the output of: journalctl -a -b -u polkit.service 3. Provide the output of: journalctl -a -b -u dbus.service (the latter two as text/plain attachments please) Sorry for the delay... hope the debug kernel option doesn't change the system dynamics... rebooted when I couldn't start polkit and I got to a point where it was needed. Attaching files. Created attachment 5091 [details]
polkit.service
Created attachment 5092 [details]
dbus.service
(In reply to Pierre Fortin from comment #3) > Created attachment 5091 [details] > polkit.service This shows things working correctly and even shows an authorisation agent (i.e. the graphical bit that loads when you start a graphical session) attaching to it. This doesn't show the service failure as reported in the original bug report, so it looks very much like it's working as intended here according to this output. (In reply to Pierre Fortin from comment #4) > Created attachment 5092 [details] > dbus.service Likewise this looks OK, and verifies the polkit name on the bus. Sadly I can't see any bug in the latest output :s By some unknown stroke of luck, are things operating as expected for you now? Hi Colin, Sorry. Should have been clearer... I've been running with polkit down and unable to [re]start it. Since I HATE rebooting, I procrastinated. After a reboot, polkit works for an undetermined time. Uploaded the output files as a reminder what they should look like. Hopefully, polkit will mess up soon and I'll be able to get the failure outputs. Not seen in mga5 Status:
NEW =>
RESOLVED |