And more importantly, why is it having a cow with kernel 5.0.5 on one, just one, of my servers:
Apr 9 17:48:44 monster dbus-daemon[1223]: [system] Failed to activate service 'org.freedesktop.UDisks2': timed out (service_start_timeout=25000ms)
kernel 5.0.4 is ok. kernel 5.0.5 is ok on other machines. But on this machine, this mystery box fails to open. This is what's responsible for various silly things that Thunar was doing, on my XFCE desktop.
Googling brings up a bunch of stuff, but very vague, and doesn't really help me knowing where to look next. My only glimmer of hope, is that booting 5.1.0 from rawhide on the same server appears not to have this issue, so this is probably fixed already/maybe/perhaps/i-hope-so.
On 4/12/19 8:47 AM, Sam Varshavchik wrote:
And more importantly, why is it having a cow with kernel 5.0.5 on one, just one, of my servers:
Apr 9 17:48:44 monster dbus-daemon[1223]: [system] Failed to activate service 'org.freedesktop.UDisks2': timed out (service_start_timeout=25000ms)
kernel 5.0.4 is ok. kernel 5.0.5 is ok on other machines. But on this machine, this mystery box fails to open. This is what's responsible for various silly things that Thunar was doing, on my XFCE desktop.
Googling brings up a bunch of stuff, but very vague, and doesn't really help me knowing where to look next. My only glimmer of hope, is that booting 5.1.0 from rawhide on the same server appears not to have this issue, so this is probably fixed already/maybe/perhaps/i-hope-so.
Well....
The udisksd program provides the org.freedesktop.UDisks2 name on the system message bus.
So, it would seem to me that udisksd is failing to start or is otherwise failing?
On Thu, Apr 11, 2019 at 08:47:37PM -0400, Sam Varshavchik wrote:
And more importantly, why is it having a cow with kernel 5.0.5 on one, just one, of my servers:
Apr 9 17:48:44 monster dbus-daemon[1223]: [system] Failed to activate service 'org.freedesktop.UDisks2': timed out (service_start_timeout=25000ms)
Are there issues related to that error? Apart from usdisk* maybe not starting, forever ..?
You probably have some special angel around you, for the sake of the integrity of your hardware. For I'd consider that bug being a feature. At first sight, at least ... ;) See: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org/...
man usdisks*
F28 here: I usually stop that "service" completely. That is, after booting: systemctl stop udisks2
And then I check from time to time it never raised its ugly head again: something like: systemctl status udisks2
HTH,
Regards, Wolfgang
-- "When I see a giant crane passing on a flatbed truck, I pause in awe and reverence, as one would for a church procession. [ ... ] If civilization had been left in female hands, we would still be living in grass huts."
Camille Paglia: "Sexual Personae" p.38
Wolfgang Pfeiffer writes:
On Thu, Apr 11, 2019 at 08:47:37PM -0400, Sam Varshavchik wrote:
And more importantly, why is it having a cow with kernel 5.0.5 on one, just one, of my servers:
Apr 9 17:48:44 monster dbus-daemon[1223]: [system] Failed to activate service 'org.freedesktop.UDisks2': timed out (service_start_timeout=25000ms)
Are there issues related to that error? Apart from usdisk* maybe not starting, forever ..?
Oh, just the small inconvenience of plugging in my MP3 and not having it automount, any more.
On Fri, 12 Apr 2019 21:22:39 -0400 Sam Varshavchik wrote:
Oh, just the small inconvenience of plugging in my MP3 and not having it automount, any more.
I hate stuff automounting in random locations I don't know. I turn off all that stuff and use my "mountie" program to mount things I want mounted where I want them :-).
Background: https://tomhorsley.com/game/case-of-disks.html
The program: https://tomhorsley.com/software/software.html#mountie
On Fri, Apr 12, 2019 at 09:22:39PM -0400, Sam Varshavchik wrote:
Wolfgang Pfeiffer writes:
On Thu, Apr 11, 2019 at 08:47:37PM -0400, Sam Varshavchik wrote:
And more importantly, why is it having a cow with kernel 5.0.5 on one, just one, of my servers:
Apr 9 17:48:44 monster dbus-daemon[1223]: [system] Failed to activate service 'org.freedesktop.UDisks2': timed out (service_start_timeout=25000ms)
Are there issues related to that error? Apart from usdisk* maybe not starting, forever ..?
Oh, just the small inconvenience of plugging in my MP3 and not having it automount, any more.
If you like Gui mounts (via file manager etc) this might help:
---------- // Allow user 'xxx' to perform any operation on // drives without having to authenticate // polkit.addRule(function(action, subject) { if (action.id.indexOf("org.freedesktop.udisks2.") == 0 && subject.user == "xxx") { return polkit.Result.YES; } });
--------
You might want save it to sth. like: /etc/polkit-1/rules.d/90-xxx-disk.admin.rules
"xxx" above is a non-root username ...
But I'd suggest a manual mount anyways, not the gui routines ... "mount -v /mnt/mp3device"
But I'm old, so be free to ignore my control obsessions vs. stupid computers .. :)
Note that the polkit snippet above won't help, IIRC, for this last manual mount command: it probably only works for GUI mounts, and it might even start usdisks2. So, your choice ... :)
Best Regards, Wolfgang
-- "When I see a giant crane passing on a flatbed truck, I pause in awe and reverence, as one would for a church procession. [ ... ] If civilization had been left in female hands, we would still be living in grass huts."
Camille Paglia: "Sexual Personae" p.38
On Sat, Apr 13, 2019 at 06:36:06AM +0200, Wolfgang Pfeiffer wrote:
On Fri, Apr 12, 2019 at 09:22:39PM -0400, Sam Varshavchik wrote:
Wolfgang Pfeiffer writes:
On Thu, Apr 11, 2019 at 08:47:37PM -0400, Sam Varshavchik wrote:
And more importantly, why is it having a cow with kernel 5.0.5 on one, just one, of my servers:
Apr 9 17:48:44 monster dbus-daemon[1223]: [system] Failed to activate service 'org.freedesktop.UDisks2': timed out (service_start_timeout=25000ms)
Are there issues related to that error? Apart from usdisk* maybe not starting, forever ..?
Oh, just the small inconvenience of plugging in my MP3 and not having it automount, any more.
If you like Gui mounts (via file manager etc) this might help:
// Allow user 'xxx' to perform any operation on // drives without having to authenticate // polkit.addRule(function(action, subject) { if (action.id.indexOf("org.freedesktop.udisks2.") == 0 && subject.user == "xxx") { return polkit.Result.YES; } });
You might want save it to sth. like: /etc/polkit-1/rules.d/90-xxx-disk.admin.rules
I'm not sure tho' how safe such a script is regarding security for the machine where it's installed. If in doubt: don't install it.
Best Regards, Wolfgang
-
Ed Greshko -
Sam Varshavchik -
Tom Horsley -
Wolfgang Pfeiffer