Void Linux discussion
 help / color / mirror / Atom feed
From: Frankie Wild <green...@gmail.com>
To: voidlinux <void...@googlegroups.com>
Subject: Re: Random crashes and log-outs of E19
Date: Mon, 7 Sep 2015 10:02:58 -0700 (PDT)	[thread overview]
Message-ID: <9fc97550-d596-4848-829f-6f91727820b4@googlegroups.com> (raw)
In-Reply-To: <cceef9d9-740f-4b07-933d-b5628c304d83@googlegroups.com>


[-- Attachment #1.1: Type: text/plain, Size: 3424 bytes --]

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 ? 
>>>>
>>>

[-- Attachment #1.2: Type: text/html, Size: 4681 bytes --]

  reply	other threads:[~2015-09-07 17:02 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-04 15:50 Frankie Wild
2015-09-06  9:31 ` Frankie Wild
2015-09-06 10:07   ` Frankie Wild
2015-09-06 17:37     ` Frankie Wild
2015-09-07 17:02       ` Frankie Wild [this message]
2015-09-07 18:12         ` Frankie Wild
2015-09-08 20:42           ` Frankie Wild
2015-09-09 21:47             ` JD Robinson
2015-09-09 21:51             ` JD Robinson
2015-09-10  6:09               ` Frankie Wild
2015-09-10 11:54                 ` Frankie Wild
2015-09-10 21:07                   ` Frankie Wild
2015-09-15  7:31                     ` Juan RP
2015-10-03  5:55                       ` Frankie Wild
2015-10-08 15:37                         ` Frankie Wild
2015-10-09 14:41 ` Userx Xbw
2015-10-09 16:56   ` Frankie Wild

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=9fc97550-d596-4848-829f-6f91727820b4@googlegroups.com \
    --to="green..."@gmail.com \
    --cc="void..."@googlegroups.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).