[SOLVED] dbus-1.14.4-x86_64-1.txz possible bug ?

There seems to be bug in dbus-1.14.4-x86_64-1.txz

Been having a strange problem with thunar in xfce on slackware64-current.

The view settings would inexplicably reset to "factory default".

Set it to view hidden files, turn off the side pane, full date format, list view.

The next time thunar is pulled-up, hidden files are not showing,
side pane is on, back to icon view, date format is back to 'today/yesterday'
when switching to list view.

Simply reverting to dbus-1.12.20-x86_64-5.txz grabbed from slackware64-15.0
cured the problem and the view settings now stay where they've been set.

There might be other settings that are also not 'sticking' in addition to
what I've seen in thunar.

1.14.6 have been released yesterday
maybe you could wait and give it a try when we have it in Slackware

Shall do so and report-back.

No good.... bug still there in...

Thu Feb 9 22:39:11 UTC 2023
a/dbus-1.14.6-x86_64-1.txz: Upgraded.

Here's an SSR recording of it happening.

http://glennmcc.org/dbus-1.14.x-bug.webm

Does it still happen if you do this as a regular user rather than as root?

No, it does not happen to non-root users.

It only happens when I'm using the root account for administering
files & directories owned by root to-which non-root users have no permission to access.
___________________


http://mirrors.kernel.org/slackware/...obally.diff.gz

diff -Nur dbus-1.12.0.orig/bus/system.conf.in dbus-1.12.0/bus/system.conf.in
--- dbus-1.12.0.orig/bus/system.conf.in	2017-10-30 07:26:18.000000000 -0500
+++ dbus-1.12.0/bus/system.conf.in	2017-10-31 00:17:34.989634085 -0500
@@ -125,6 +125,14 @@
   <!-- <limit name="max_match_rules_per_connection">512</limit> -->
   <!-- <limit name="max_replies_per_connection">128</limit> -->
 
+  <!-- Allow root to do anything over the messagebus.
+       Don't whine about "security" - anyone with root privileges
+       can edit this file anyway, so -ENOHOLE here. -->
+  <policy user="root">
+    <allow send_destination="*"/>
+    <allow send_interface="*"/>
+  </policy>
+
   <!-- Config files are placed here that among other things, punch 
        holes in the above policy for specific services. -->
   <includedir>system.d</includedir>

Found and fixed the very STUPID mistake that I made.