From mboxrd@z Thu Jan 1 00:00:00 1970 Date: Mon, 7 Sep 2015 11:12:37 -0700 (PDT) From: Frankie Wild To: voidlinux Message-Id: <047765c9-93b8-4c79-a282-1c34298c3941@googlegroups.com> In-Reply-To: <9fc97550-d596-4848-829f-6f91727820b4@googlegroups.com> References: <2da6d03f-ec11-4c39-8f61-5210d5c643dd@googlegroups.com> <9fc97550-d596-4848-829f-6f91727820b4@googlegroups.com> Subject: Re: Random crashes and log-outs of E19 MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_Part_4040_390833176.1441649557273" ------=_Part_4040_390833176.1441649557273 Content-Type: multipart/alternative; boundary="----=_Part_4041_1345729774.1441649557274" ------=_Part_4041_1345729774.1441649557274 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit 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 ? >>>>> >>>> ------=_Part_4041_1345729774.1441649557274 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable
Hmmm I knew there is more to it.=C2=A0

= Check this out, to all interested in the saga:

htt= ps://igurublog.wordpress.com/2012/03/11/udisks2-another-loss-for-linux/

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

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

https://www.youtube= .com/watch?v=3DrRm0NDo1CiY

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

It happens ab= out 10-15 times a day, so I am at the point of reinstalling the whole syste= m or trying out Manjaro OpenRC, although I like Void and am sure that udisk= s2 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 wro= te:
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 unplu= gged 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.Ac= cessDenied: "Rejected send message, 1 matched rules; type=3D"meth= od_call", sender=3D":1.68" (uid=3D1000 pid=3D28279 comm=3D&q= uot;dbus-monitor --system ") interface=3D"org.freedesktop.DB= us.Monitoring" member=3D"BecomeMonitor" error name=3D"(= unset)" requested_reply=3D"0" destination=3D"org.freede= sktop.DBus" (bus)". Falling back to eavesdropping.
signal time=3D1441533725.361185 sender=3Dorg.freedesktop.DBus -> destin= ation=3D:1.68 serial=3D2 path=3D/org/freedesktop/DBus; interface=3Dorg.free= desktop.DBus; member=3DNameAcquired
=C2=A0 =C2=A0string &quo= t;:1.68"

dbus-monitor --session
signal time=3D1441533710.331885 sender=3Dorg.freedesktop.DBus -> desti= nation=3D:1.6 serial=3D2 path=3D/org/freedesktop/DBus; interface=3Dorg.free= desktop.DBus; member=3DNameAcquired
=C2=A0 =C2=A0string &quo= t;:1.6"
signal time=3D1441533710.331920 sender=3Dorg.freedes= ktop.DBus -> destination=3D:1.6 serial=3D4 path=3D/org/freedesktop/DBus;= interface=3Dorg.freedesktop.DBus; member=3DNameLost
=C2=A0 = =C2=A0string ":1.6"


This might give some clue if someone else is experiencing a similar behavi= or.=C2=A0

I have also tried to exclusively stop th= e 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=C2=A0

udisks2 --inhibit-all-polling


Both resulting in command not found.=C2=A0


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 th= is is what I am seeing for a second in the log upon crash before being pres= ented 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 consta= ntly 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.= =C2=A0

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...=C2=A0

Where co= uld they be, so that I can post more info on the errors ?=C2=A0
=
------=_Part_4041_1345729774.1441649557274-- ------=_Part_4040_390833176.1441649557273--