OK, maybe it's my noobishment here, but after switching to udisks v1 instead of v2 the log-outs would only show xbps successfully installed xxx package.

No more udisks errors, all errors now come as successful install of xbps package which happened earlier during the day via the regular xbps-install -Su.

I can see I am talking to myself, does that mean nobody else ever experienced such behaviour ? 

On Monday, September 7, 2015 at 9:12:37 PM UTC+3, Frankie Wild wrote:
Hmmm I knew there is more to it. 

Check this out, to all interested in the saga:

https://igurublog.wordpress.com/2012/03/11/udisks2-another-loss-for-linux/

The plague is everywhere, if you are not yet affected, stay tuned. 

Might as well try the shift to PC-BSD and Lumina in the end.

https://www.youtube.com/watch?v=rRm0NDo1CiY

On Monday, September 7, 2015 at 8:02:58 PM UTC+3, Frankie Wild wrote:
Turns out to be more than that. I reinstalled udisks2 with external drive unplugged. Now the occasional log-outs happen with the notice udisks2 successfully reinstalled... 

It happens about 10-15 times a day, so I am at the point of reinstalling the whole system or trying out Manjaro OpenRC, although I like Void and am sure that udisks2 is used throughout all distributions nowaday, replacing the good old HAL.

On Sunday, September 6, 2015 at 8:37:26 PM UTC+3, Frankie Wild wrote:
The errors got more informative. It's definitely being caused by the external drive I am using from time to time. Obviously it's crashing due to the periodic nature of remounting the devices that udisks uses and happens when I unplugged the external hdd earlier, not quite sure why it's not event based rather than interval based.

On Sunday, September 6, 2015 at 1:07:52 PM UTC+3, Frankie Wild wrote:
dbus-monitor --system

dbus-monitor: unable to enable new-style monitoring: org.freedesktop.DBus.Error.AccessDenied: "Rejected send message, 1 matched rules; type="method_call", sender=":1.68" (uid=1000 pid=28279 comm="dbus-monitor --system ") interface="org.freedesktop.DBus.Monitoring" member="BecomeMonitor" error name="(unset)" requested_reply="0" destination="org.freedesktop.DBus" (bus)". Falling back to eavesdropping.
signal time=1441533725.361185 sender=org.freedesktop.DBus -> destination=:1.68 serial=2 path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; member=NameAcquired
   string ":1.68"

dbus-monitor --session
signal time=1441533710.331885 sender=org.freedesktop.DBus -> destination=:1.6 serial=2 path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; member=NameAcquired
   string ":1.6"
signal time=1441533710.331920 sender=org.freedesktop.DBus -> destination=:1.6 serial=4 path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; member=NameLost
   string ":1.6"


This might give some clue if someone else is experiencing a similar behavior. 

I have also tried to exclusively stop the remounting of the devices over a certain period of time, since I suspect this is the case when the crashes happen.

udisks --inhibit-all-polling

Or 

udisks2 --inhibit-all-polling


Both resulting in command not found. 


On Sunday, September 6, 2015 at 12:31:46 PM UTC+3, Frankie Wild wrote:
Interestingly enough it seems related to the udiskd daemon. At least this is what I am seeing for a second in the log upon crash before being presented with login screen.

Another thing I've noticed is that about the same time the crashes started a glitch in E19 appeared as well. Again random, when I am trying to close a window on the taskbar the mouse would move precisely to the center of the screen and does that constantly until reboot.

On Friday, September 4, 2015 at 6:50:49 PM UTC+3, Frankie Wild wrote:
I believe it's since I installed latest updates two days ago. 

At the time it occurs I get a black screen with a few lines of errors and then back to login screen.

I couldn't memorize what the errors were at the time. I have checked all logs in /var/log to no avail... 

Where could they be, so that I can post more info on the errors ?