I'd suggest attaching turning on core files, attaching gdb, and doing
a stack trace tomorrow morning with the inevitable core file that
shows up. It looks like the log files aren't going to be useful here.
On Thu, Oct 27, 2011 at 11:03 AM, Adam Jimerson wrote:
> In my /etc/X11/xorg.conf.d/10-moni
In my /etc/X11/xorg.conf.d/10-monitor.conf I am telling it not to use
TwinView, instead I am using Xinerama.
Option"TwinView" "0"
Option"Xinerama" "1"
I guess it wouldn't hurt to remove the TwinView option line for my screens
On Thu, Oct 27, 2011 at 11:05 AM, Josh
On Thu, Oct 27, 2011 at 11:27 AM, Paweł Rumian wrote:
> Have you checked uptime and/or dmesg? Maybe the machine reboots?
>
>
>
Uptime is what I would expect it to be, been up for 2 days, dmesg doesn't
have anything in it that looks like the system rebooted but it does look
like the GPU freaked o
Have you checked uptime and/or dmesg? Maybe the machine reboots?
--
To unsubscribe, send mail to awesome-unsubscr...@naquadah.org.
I don't think ATI uses TwinView...
On Thu, Oct 27, 2011 at 7:18 AM, Adam Jimerson wrote:
> I am running Awesome 3.4.10 on an Arch Linux box that I leave on over night
> locked with Xscreensaver. By morning I come in and get on the computer to
> find that it is sitting at SLiM login screen instea
I am running Awesome 3.4.10 on an Arch Linux box that I leave on over night
locked with Xscreensaver. By morning I come in and get on the computer to
find that it is sitting at SLiM login screen instead of the xscreensaver, I
tried looking through Xorgs logs to see if I can find what might be
happ
