From mboxrd@z Thu Jan 1 00:00:00 1970 Date: Sun, 6 Sep 2015 03:07:52 -0700 (PDT) From: Frankie Wild To: voidlinux Message-Id: <2da6d03f-ec11-4c39-8f61-5210d5c643dd@googlegroups.com> In-Reply-To: References: Subject: Re: Random crashes and log-outs of E19 MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_Part_2360_971671227.1441534072369" ------=_Part_2360_971671227.1441534072369 Content-Type: multipart/alternative; boundary="----=_Part_2361_554831112.1441534072370" ------=_Part_2361_554831112.1441534072370 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit 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_2361_554831112.1441534072370 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable
dbus-monitor --system

dbus-m= onitor: unable to enable new-style monitoring: org.freedesktop.DBus.Error.A= ccessDenied: "Rejected send message, 1 matched rules; type=3D"met= hod_call", sender=3D":1.68" (uid=3D1000 pid=3D28279 comm=3D&= quot;dbus-monitor --system ") interface=3D"org.freedesktop.DBus.M= onitoring" member=3D"BecomeMonitor" error name=3D"(unse= t)" requested_reply=3D"0" destination=3D"org.freedeskto= p.DBus" (bus)". Falling back to eavesdropping.
signal t= ime=3D1441533725.361185 sender=3Dorg.freedesktop.DBus -> destination=3D:= 1.68 serial=3D2 path=3D/org/freedesktop/DBus; interface=3Dorg.freedesktop.D= Bus; member=3DNameAcquired
=C2=A0 =C2=A0string ":1.68"<= /div>

dbus-monitor --session
signal time= =3D1441533710.331885 sender=3Dorg.freedesktop.DBus -> destination=3D:1.6= serial=3D2 path=3D/org/freedesktop/DBus; interface=3Dorg.freedesktop.DBus;= member=3DNameAcquired
=C2=A0 =C2=A0string ":1.6"
=
signal time=3D1441533710.331920 sender=3Dorg.freedesktop.DBus -> de= stination=3D:1.6 serial=3D4 path=3D/org/freedesktop/DBus; interface=3Dorg.f= reedesktop.DBus; member=3DNameLost
=C2=A0 =C2=A0string ":1.6= "


This might give some c= lue if someone else is experiencing a similar behavior.=C2=A0
I have also tried to exclusively stop the remounting of the dev= ices over a certain period of time, since I suspect this is the case when t= he crashes happen.

udisks --inhibit-all-polling
=

Or=C2=A0

udisks2 --inhibit-all-polling
<= br>

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. A= t least this is what I am seeing for a second in the log upon crash before = being presented with login screen.

Another thing I'v= e noticed is that about the same time the crashes started a glitch in E19 a= ppeared as well. Again random, when I am trying to close a window on the ta= skbar the mouse would move precisely to the center of the screen and does t= hat 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.=C2=A0

At the time it occurs I get a black scre= en 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 could they be, so that I can post more info on the errors ?=C2=A0
------=_Part_2361_554831112.1441534072370-- ------=_Part_2360_971671227.1441534072369--