Re: [STUMP] Crash Report

[email protected]
Newsgroups gmane.comp.window-managers.stumpwm.devel
Message-ID <[email protected]>
This is as it was when it crashed (again). Actually it left the system 
a bit messed up, so had to restart X.

xrandr --verbose
Screen 0: minimum 8 x 8, current 1024 x 768, maximum 8192 x 8192
VGA-0 disconnected primary (normal left inverted right x axis y axis)
Identifier: 0x249
Timestamp:  3222902
Subpixel:   unknown
Clones:
CRTCs:      0 1
Transform:  1.000000 0.000000 0.000000
            0.000000 1.000000 0.000000
            0.000000 0.000000 1.000000
           filter:
BorderDimensions: 4
supported: 4
Border: 0 0 0 0
range: (0, 65535)
SignalFormat: VGA
supported: VGA
ConnectorType: VGA
ConnectorNumber: 1
_ConnectorLocation: 1
TV-0 connected 1024x768+0+0 (0x24b) normal (normal left inverted right 
x axis y axis) 0mm x 0mm
Identifier: 0x24a
Timestamp:  3222902
Subpixel:   unknown
Gamma:      1.0:1.0:1.0
Brightness: 1.0
Clones:
CRTC:       1
CRTCs:      0 1
Transform:  1.000000 0.000000 0.000000
            0.000000 1.000000 0.000000
            0.000000 0.000000 1.000000
           filter:
BorderDimensions: 4
supported: 4
Border: 0 0 0 0
range: (0, 65535)
SignalFormat: unknown
supported: unknown
ConnectorType: TV
ConnectorNumber: 2
_ConnectorLocation: 3
  1024x768 (0x24b)   64.1MHz -HSync +VSync *current +preferred
         h: width  1024 start 1080 end 1184 total 1344 skew    0 clock   
47.7KHz
         v: height  768 start  769 end  772 total  795           clock   
60.0Hz
  800x600 (0x24c)   38.2MHz -HSync +VSync
         h: width   800 start  832 end  912 total 1024 skew    0 clock   
37.3KHz
         v: height  600 start  601 end  604 total  622           clock   
60.0Hz
  720x480 (0x24d)   26.7MHz -HSync +VSync
         h: width   720 start  736 end  808 total  896 skew    0 clock   
29.8KHz
         v: height  480 start  481 end  484 total  497           clock   
60.0Hz
  640x480 (0x24e)   23.9MHz -HSync +VSync
         h: width   640 start  656 end  720 total  800 skew    0 clock   
29.8KHz
         v: height  480 start  481 end  484 total  497           clock   
60.0Hz
  640x400 (0x24f)   19.5MHz -HSync +VSync
         h: width   640 start  648 end  712 total  784 skew    0 clock   
24.9KHz
         v: height  400 start  401 end  404 total  415           clock   
60.0Hz
  512x384 (0x250)   14.9MHz -HSync +VSync
         h: width   512 start  520 end  568 total  624 skew    0 clock   
23.9KHz
         v: height  384 start  385 end  388 total  398           clock   
60.0Hz
LVDS-0 connected 1024x768+0+0 (0x252) normal (normal left inverted 
right x axis y axis) 367mm x 230mm
Identifier: 0x251
Timestamp:  3222902
Subpixel:   unknown
Gamma:      1.0:1.0:1.0
Brightness: 1.0
Clones:
CRTC:       0
CRTCs:      0 1
Transform:  1.000000 0.000000 0.000000
            0.000000 1.000000 0.000000
            0.000000 0.000000 1.000000
           filter:
EDID:
00ffffffffffff004ca3553100000000
00110103802517780a87f594574f8c27
27505400000001010101010101010101
0101010101014f40803471b020403020
36006fe6100000190000000f00000000
000000000046d2026400000000fe0047
523433330431373055310a20000000fe
00202d383e5a80aeff02010a20200093
BorderDimensions: 4
supported: 4
Border: 160 0 160 0
range: (0, 65535)
SignalFormat: LVDS
supported: LVDS
ConnectorType: Panel
ConnectorNumber: 0
_ConnectorLocation: 0
  1920x1200 (0x252)  164.6MHz -HSync -VSync *current +preferred
         h: width  1920 start 1968 end 2000 total 2228 skew    0 clock   
73.9KHz
         v: height 1200 start 1203 end 1209 total 1232           clock   
60.0Hz


[email protected]


-----Original Message-----
From: David Bjergaard <[email protected]>
To: iii_iii <[email protected]>
Cc: Stumpwm-devel <[email protected]>
Sent: Sat, Apr 26, 2014 7:21 pm
Subject: Re: [STUMP] Crash Report


Hi can you also send the xrandr output when the external monitor is
connected?

    Dave

[email protected] writes:

> I am using Opensuse 12.3
>
> The kernel is 3.7.10-1.28-desktop #1 SMP PREEMPT Mon Feb 3 14:11:15 
UTC
> 2014 (c9a2c6c) x86_64 x86_64 x86_64 GNU/Linux
>
> Name        : sbcl
> Version     : 1.1.2
> Release     : 2.1.1
> Architecture: x86_64
> Install Date: Thu 20 Mar 2014 18:45:37 GMT
> Group       : Development/Languages/Other
> Size        : 68065565
> License     : SUSE-Public-Domain and BSD-3-Clause
> Signature   : RSA/SHA256, Mon 28 Jan 2013 07:18:41 GMT, Key ID
> b88b2fd43dbdc284
> Source RPM  : sbcl-1.1.2-2.1.1.src.rpm
> Build Date  : Mon 28 Jan 2013 07:16:56 GMT
> Build Host  : build09
> Relocations : (not relocatable)
> Packager    : http://bugs.opensuse.org
> Vendor      : openSUSE
> URL         : http://www.sbcl.org/
> Summary     : Steel Bank Common Lisp
>
> To build, I followed the instructions in README.md. It was
> straight-forward as far as I remember. I was not able to build with
> clisp though.
>
> As I said I think it is quite likely that the nvidia driver is the
> culprit.
>
> Name        : x11-video-nvidiaG03
> Version     : 331.49
> Release     : 29.1
> Architecture: x86_64
> Install Date: Sat 01 Mar 2014 16:30:24 GMT
> Group       : System/Libraries
> Size        : 89789946
> License     : PERMISSIVE-OSI-COMPLIANT
> Signature   : DSA/SHA1, Mon 24 Feb 2014 14:07:43 GMT, Key ID
> f5113243c66b6eae
> Source RPM  : x11-video-nvidiaG03-331.49-29.1.nosrc.rpm
> Build Date  : Tue 25 Feb 2014 12:48:04 GMT
> Build Host  : nagios-abuild
> Relocations : (not relocatable)
> Vendor      : obs://build.suse.de/home:sndirsch:drivers
> Summary     : NVIDIA graphics driver for GeForce 8xxx and newer GPUs
>
> The system is a laptop Intel(R) Core(TM)2 Duo CPU     T7250  @ 2.00GHz
>
>
> [email protected]
>
>
> -----Original Message-----
> From: David Bjergaard <[email protected]>
> To: Joseph Mingrone <[email protected]>
> Cc: stumpwm-devel <[email protected]>
> Sent: Sat, Apr 26, 2014 6:05 pm
> Subject: Re: [STUMP] Crash Report
>
>
> I agree. Can you send details about how you built stumpwm? 
Specifically
> which
> lisp version as well as what OS you are running?
>
>    Dave
>
>> On Apr 26, 2014, at 12:31 PM, Joseph Mingrone <[email protected]> wrote:
>>
>> [email protected] writes:
>>
>>> Hi, I have received a crash. I haven't pasted the whole thing as I
> am not
> sure
>>> if it is worth it. I am using an nvidia driver, and I was trying to
> clone the
>>> display onto tv-out. There are warnings about the nvidia driver when
> I start
> the
>>> system but it works ok most of the time. I usually extend the
> desktop rather
>>> than clone.
>>>
>>>
> 
_________________________________________________________________________

>
>
>>> ________
>>>
>>> The value NIL is not of type STUMPWM::FRAME.
>>> 0: (SB-DEBUG::MAP-BACKTRACE
>>>   #<CLOSURE (LAMBDA # :IN SB-DEBUG:BACKTRACE) {10082AF3EB}>
>>>   :START
>>>   0
>>>   :COUNT
>>>   100)
>>> 1: (SB-DEBUG:BACKTRACE 100 #<SB-IMPL::STRING-OUTPUT-STREAM
> {10082AF313}>)
>>> 2: (STUMPWM::BACKTRACE-STRING)
>>> 3: (STUMPWM::PERFORM-TOP-LEVEL-ERROR-ACTION
>>>   #<TYPE-ERROR expected-type: STUMPWM::FRAME datum: NIL>)
>>> 4: (SIGNAL #<TYPE-ERROR expected-type: STUMPWM::FRAME datum: NIL>)
>>> 5: (ERROR TYPE-ERROR :DATUM NIL :EXPECTED-TYPE STUMPWM::FRAME)
>>> 6: (SB-KERNEL::OBJECT-NOT-TYPE-ERROR-HANDLER
>>>   #<unavailable argument>
>>>   #.(SB-SYS:INT-SAP #X7FFFF6E1ED80)
>>>   #<SB-ALIEN-INTERNALS:ALIEN-VALUE :SAP #X7FFFF6E1E900 :TYPE (*
>>>
> (SB-ALIEN:STRUCT
>>>
> SB-VM::OS-CONTEXT-T-STRUCT))>
>>>   (149 21))
>>>
> ______________________________________________________________________
>>>
>>> [email protected]
>>
>> This appears related to https://github.com/stumpwm/stumpwm/issues/71.
>>
>>
>> _______________________________________________
>> Stumpwm-devel mailing list
>> [email protected]
>> https://lists.nongnu.org/mailman/listinfo/stumpwm-devel
>
> _______________________________________________
> Stumpwm-devel mailing list
> [email protected]
> https://lists.nongnu.org/mailman/listinfo/stumpwm-devel
>
>
>
>
> _______________________________________________
> Stumpwm-devel mailing list
> [email protected]
> https://lists.nongnu.org/mailman/listinfo/stumpwm-devel
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.