Void Linux discussion
 help / color / mirror / Atom feed
From: Donald Allen <donald...@gmail.com>
To: voidlinux <void...@googlegroups.com>
Subject: Re: Seg-faults in the X server
Date: Thu, 1 Oct 2015 13:31:36 -0700 (PDT)	[thread overview]
Message-ID: <932abbb6-5d0c-4172-a3bc-8d40f91aae92@googlegroups.com> (raw)
In-Reply-To: <b17e5e42-8848-4338-9473-9f1af5660792@googlegroups.com>

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

Just had another one. Photo of the screen attached. I'm going to have to 
move back to Arch; this is too disruptive. I'll check back again with Void 
when I see signs that this and the other issues I've mentioned have been 

On Thursday, October 1, 2015 at 11:19:32 AM UTC-4, Donald Allen wrote:
> I have seen a few seg-faults in the X server during the time I've been 
> using Void on one machine (a few weeks). It happened again a while ago and 
> I was in the middle of something pressing and didn't write down the 
> traceback info. I'll report it next time it happens. I've never seen this 
> on my other machines, which run Arch and Arch (and OpenBSD) have run 
> reliably on the machine where I'm running Void. I note that pacman reports 
> the server version as xorg-server 1.17.2-4 on one of my Arch boxes, whereas 
> xbps shows xorg-server-1.17.2_5, so Void may be a little newer and perhaps 
> the Xorg guys broke something in the server itself or the driver I'm using 
> (video hardware on this machine is 'VGA compatible controller: Advanced 
> Micro Devices, Inc. [AMD/ATI] Caicos [Radeon HD 6450/7450/8450 / R5 230 
> OEM]').

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

[-- Attachment #2: IMG_20151001_161412.jpg --]
[-- Type: image/jpeg, Size: 801870 bytes --]

  reply	other threads:[~2015-10-01 20:31 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-01 15:19 Donald Allen
2015-10-01 20:31 ` Donald Allen [this message]
2015-10-03 13:32   ` Christian Neukirchen
2015-10-16  9:43     ` Juan RP
2015-10-16 11:05       ` Donald Allen

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:

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

  git send-email \
    --in-reply-to=932abbb6-5d0c-4172-a3bc-8d40f91aae92@googlegroups.com \
    --to="donald..."@gmail.com \
    --cc="void..."@googlegroups.com \


* 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).