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: Thu, 8 Oct 2015 08:37:26 -0700 (PDT)	[thread overview]
Message-ID: <a4f701cf-b69e-402c-b324-698fe0f806bd@googlegroups.com> (raw)
In-Reply-To: <80889b44-d3c9-4a03-8e76-55393c9de345@googlegroups.com>


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

Update, interestingly enough the problem does not persist in KDE or Gnome. 
What's even more interesting is that the latter two run a bit faster than 
E19 which is hard to explain, given they are memory hogs. There were other 
glitches in E19 lately like flickering taskbar, Google Chrome menus 
sticking below all windows, and some recovery crashes. Staying with KDE for 
the time being as it performs brilliantly so far.

On Saturday, October 3, 2015 at 8:55:53 AM UTC+3, Frankie Wild wrote:
>
> Sorry to be responding a bit late. 
>
> Thanks for the advice Juan.
>
> I am also using e19 it was using udisks2 by default when the crashes 
> started.
>
> I then switched to udisks and the frequency of crashes somehow got lower 
> but didn't disappear. Probably 5 to 10 a day.
>
> I am not sure how to work with udisks although I went through their man 
> pages, especially how to collect a stack trace with gdb.
>
> Detailed instructions would be most welcome. 
>
> P.S. Congrats on the great distribution, something truly unique and new in 
> the sea of boring respins of major systemd distros.
>
>
> On Tuesday, September 15, 2015 at 10:31:43 AM UTC+3, Juan RP wrote:
>>
>>
>>
>> I fear that reinstalling the system won't make the issues go away 
>> magically.
>>
>> Note that I'm using udisks/udisks with e19 and never had a single crash.
>>
>> If you are really sure it's udisks2 fault, try to start it manually with 
>> debugging and then collect a stack trace with gdb.
>>
>

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

  reply	other threads:[~2015-10-08 15:37 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
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 [this message]
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=a4f701cf-b69e-402c-b324-698fe0f806bd@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).