Milan Zamazal writes:
>> "DB" == David Bjergaard writes:
>
> DB> If you have time, open an issue on our github tracker so I don't
> DB> forget about this.
>
> Done.
>
> DB> I gather that you are running CLISP rather than SBCL? Do you
> DB> have any more information about t
> "DB" == David Bjergaard writes:
DB> If you have time, open an issue on our github tracker so I don't
DB> forget about this.
Done.
DB> I gather that you are running CLISP rather than SBCL? Do you
DB> have any more information about the user's configuration?
I personally
Milan Zamazal writes:
> I've received the following bug report from a Debian user:
>
> In my case I have the following in my ~/.emacs:
>
> (setq-default frame-title-format (list "" "Emacs Macht Alle Computer
> Sch\366n"))
>
> Eval this in an Emacs buffer an watch stumpwm crash:
>
>
I've received the following bug report from a Debian user:
In my case I have the following in my ~/.emacs:
(setq-default frame-title-format (list "" "Emacs Macht Alle Computer
Sch\366n"))
Eval this in an Emacs buffer an watch stumpwm crash:
*** - CONVERT-STRING-FROM-BYTES: Inva
ite do it, possibly because of that :key
> > clause.
> > I can help with testing in a bit, as I can reliably reproduce the
> > problem.
> >
> >
> >
> > > iii_...@aol.co.uk writes:
> > >
> > >> This one?
> > >>
> >>
> >>
>
> https://github.com/stumpwm/stumpwm/commit/8a59c96f340351559f87a39685268e8c15a98e0e
> >>
> >> iii_...@aim.com
> >>
> >>
> >> -Original Message-
> >> From: David Bjer
.co.uk writes:
> >
> >> This one?
> >>
> >>
> https://github.com/stumpwm/stumpwm/commit/8a59c96f340351559f87a39685268e8c15a98e0e
> >>
> >> iii_...@aim.com
> >>
> >>
> >> -Original Message-
mit/8a59c96f340351559f87a39685268e8c15a98e0e
>>
>> iii_...@aim.com
>>
>>
>> -Original Message-
>> From: David Bjergaard
>> To: Eric Abrahamsen
>> Cc: stumpwm-devel
>> Sent: Sun, Apr 27, 2014 5:22 am
>> Subject: Re: [STUMP] Crash R
is, but
there was something funky about the :key clause of the sort, and I
couldn't figure out how/why it was/wasn't working...
Eric
>
> iii_...@aim.com
>
>
> -Original Message-
> From: David Bjergaard
> To: Eric Abrahamsen
> Cc: stumpwm-devel
> Se
wm/commit/8a59c96f340351559f87a39685268e8c15a98e0e
>
> iii_...@aim.com
>
>
> -Original Message-
> From: David Bjergaard
> To: Eric Abrahamsen
> Cc: stumpwm-devel
> Sent: Sun, Apr 27, 2014 5:22 am
> Subject: Re: [STUMP] Crash Report
>
>
>
>
>
This one?
https://github.com/stumpwm/stumpwm/commit/8a59c96f340351559f87a39685268e8c15a98e0e
iii_...@aim.com
-Original Message-
From: David Bjergaard
To: Eric Abrahamsen
Cc: stumpwm-devel
Sent: Sun, Apr 27, 2014 5:22 am
Subject: Re: [STUMP] Crash Report
This appears related to
>> This appears related to https://github.com/stumpwm/stumpwm/issues/71.
>
> I'm pretty sure this is it, and pretty sure this is related to the bug
> where removing an external monitor causes the same error. As far as I
> know this was meant to be addressed by commit 8a59c9 "Head hotfix" on
> the
Joseph Mingrone writes:
> iii_...@aol.co.uk 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 st
quot;)
28: (STUMPWM ":0")
29: ((LAMBDA () :IN "/home/lg1/stumpwm/make-image.lisp"))
30: ((FLET #:WITHOUT-INTERRUPTS-BODY-54 :IN SB-EXT:SAVE-LISP-AND-DIE))
31: ((LABELS SB-IMPL::RESTART-LISP :IN SB-EXT:SAVE-LISP-AND-DIE))
iii_...@aim.com
-Original Message-
From: Shawn B
ahh shit never mind. I just pulled down new mail and saw all the other posts.
On Sat, Apr 26, 2014 at 12:33 PM, Shawn Betts wrote:
> Hi, you didn't paste enough of the backtrace! All we got is the
> function calls related to handling the error and printing the
> backtrace!
>
> -Shawn
>
> On Sat,
Hi, you didn't paste enough of the backtrace! All we got is the
function calls related to handling the error and printing the
backtrace!
-Shawn
On Sat, Apr 26, 2014 at 6:44 AM, wrote:
> 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 usin
I knew there was somewhere I had seen xrandr mentioned. I get this when
I launch an application with wine:
err:winediag:xrandr12_init_modes Broken NVIDIA RandR detected, falling
back to RandR 1.0. Please consider using the Nouveau driver instead.
The nouveau driver isn't an option though, it
: [STUMP] Crash Report
Hi can you also send the xrandr output when the external monitor is
connected?
Dave
iii_...@aol.co.uk 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
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
>
>
> iii_...@aim.com
>
>
> -Original Message-
> From: David Bjergaard
> To: Joseph Mingron
graphics driver for GeForce 8xxx and newer GPUs
The system is a laptop Intel(R) Core(TM)2 Duo CPU T7250 @ 2.00GHz
iii_...@aim.com
-Original Message-
From: David Bjergaard
To: Joseph Mingrone
Cc: stumpwm-devel
Sent: Sat, Apr 26, 2014 6:05 pm
Subject: Re: [STUMP] Crash Report
I
David Bjergaard writes:
> I agree. Can you send details about how you built stumpwm?
> Specifically which lisp version as well as what OS you are running?
>
> Dave
Perhaps this is relevant.
I have a laptop with FreeBSD 9.2-STABLE amd64 with sbcl-1.1.12,1
installed from the FreeBSD port. Fro
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 wrote:
>
> iii_...@aol.co.uk writes:
>
>> Hi, I have received a crash. I haven't pasted the whole thing as I
iii_...@aol.co.uk 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
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
On 04/16/2012 02:28 PM, Vitaly Mayatskikh wrote:
At Thu, 05 Apr 2012 18:10:40 -0700, Stephen Balousek wrote:
I managed to get a repeat of this crash - this time with more
information about the point of failure.
Judging from the functions involved, I am guessing this might be an
issue with CLX.
At Mon, 16 Apr 2012 20:56:42 -0400, David Bjergaard wrote:
> While I haven't experienced any show stopping crashes, I do use Stump
> with SBCL.
Yeah, we've spent enormous amount of efforts on that 2 or 3 years
ago. Though SBCL works for me too, I've noticed that StumpWM likes CCL
a bit more.
>
Hi Vitaly,
While I haven't experienced any show stopping crashes, I do use Stump
with SBCL.
Is there a way to get multi-threading with CCL? I want to be able to
connect with SWANK via emacs.
Dave
Vitaly Mayatskikh writes:
> At Thu, 05 Apr 2012 18:10:40 -0700, Stephen Balousek wrote:
At Thu, 05 Apr 2012 18:10:40 -0700, Stephen Balousek wrote:
> I managed to get a repeat of this crash - this time with more
> information about the point of failure.
>
> Judging from the functions involved, I am guessing this might be an
> issue with CLX. Any other ideas would be appreicated.
Hi,
I managed to get a repeat of this crash - this time with more
information about the point of failure.
Judging from the functions involved, I am guessing this might be an
issue with CLX. Any other ideas would be appreicated.
- Steve
Caught 'The value -25040316 is not of type UNSIGNED-B
It looks like the backtrace gets cut off before reaching the actually
relevant part. I'm not sure off the top of my head how to control the
length of backtraces being printed - is there anything like that in
the error handling of stumpwm?
Vladimir
On Tue, Feb 28, 2012 at 9:15 AM, Stephen Balousek
Hi,
I am getting a strange, intermittent crash of StumpWM and I am looking
for pointers on how to resolve it, or possible workarounds.
The relevant information from ~/.xsession-errors is:
Caught 'The value -28580123 is not of type UNSIGNED-BYTE.' at the
top level. Please report this.
Backtrace at http://paste.lisp.org/display/95662
I had VLC open, and then went to the Open File dialog. Then, while the dialog
was still open, I hit C-t C-t to switch windows, and poof.
Some thoughts that simias and I had in #stumpwm:
- Things seem doomed at (7F5B5001EA10) : 11 (TRANSIENTS-OF
At Sun, 08 Nov 2009 12:12:15 +0100, Mikael Jansson wrote:
>
> Heya,
>
> I've seen this crash quite often recently:
> http://paste.lisp.org/display/89980
>
> Ubuntu 9.04, 32-bit, SBCL-1.0.23
>
> Any ideas what's going on or how I can fix it?
Update to newer SBCL.
--
wbr, Vitaly
Heya,
I've seen this crash quite often recently:
http://paste.lisp.org/display/89980
Ubuntu 9.04, 32-bit, SBCL-1.0.23
Any ideas what's going on or how I can fix it?
--M
___
Stumpwm-devel mailing list
Stumpwm-devel@nongnu.org
http://lists.nongnu.org/
On Sat, Sep 5, 2009 at 9:06 PM, Philip M. White wrote:
> On Thu, Sep 03, 2009 at 12:07:20AM -0700, Shawn Betts wrote:
>> I bet if you went into modules/clx/new-clx/clx.f and changed:
>
> That fixed it! Thanks!
Excellent!
> I don't have a CVS client installed yet, so I don't know whether this is
On Thu, Sep 03, 2009 at 12:07:20AM -0700, Shawn Betts wrote:
> I bet if you went into modules/clx/new-clx/clx.f and changed:
That fixed it! Thanks!
I don't have a CVS client installed yet, so I don't know whether this is
fixed yet. Do you want to pursue this bug, or should I?
--
Philip
smim
Hi Philip,
It looks like it could be a bug in clisp's new-clx implementation. It
appears XFree is being called on an invalid pointer inside new-clx's
xlib:wm-hints function. Looking at the function, I don't see anything
obviously wrong with it. However, the hints variable is not
initialized and pe
Philip M. White wrote:
> What activities cause the crash? I cannot pinpoint the root cause, but
> there are at least four that do it for me:
>
> 1) Closing The GIMP (File -> Quit) while it has any images open. If
> there are no images open, The GIMP quits without an issue, but if any
> image win
Hello,
I've been using stumpwm for probably two years. For close to a year
now, I've been experiencing an occasional crash, but it hasn't bothered
me enough until now to report it. But now I'm annoyed enough to gather
some data and write this email.
I am using the latest stumpwm from git and co
Stanisław Halik writes:
> Oh hi,
>
> So stumpwm crashed only to reinitialize itself and crash again. Here's
> the backtrace:
>
> Caught 'The value 4294967295 is not of type (OR NULL (UNSIGNED-BYTE
> 16)).' at the top level. Please report this.
> 11: (XLIB::DECODE-WM-HINTS
> #(119 1 1 377495
Oh hi,
So stumpwm crashed only to reinitialize itself and crash again. Here's
the backtrace:
Caught 'The value 4294967295 is not of type (OR NULL (UNSIGNED-BYTE
16)).' at the top level. Please report this.
0: (SB-DEBUG::MAP-BACKTRACE #)[:EXTERNAL]
1: (SB-DEBUG:BACKTRACE 100 #)
2: (STUMPWM::BACKTR
AIL PROTECTED]> writes:
>
> > Oops, sry: I should have sent this to the whole list but only sent it to
> Yann:
> >
> > -- Forwarded message --
> > From: Pierre-Paul Paquin <[EMAIL PROTECTED]>
> > Date: 2008/8/13
> > Subject: Re: [STUMP] Cr
"Pierre-Paul Paquin" <[EMAIL PROTECTED]> writes:
> Oops, sry: I should have sent this to the whole list but only sent it to Yann:
>
> -- Forwarded message --
> From: Pierre-Paul Paquin <[EMAIL PROTECTED]>
> Date: 2008/8/13
> Subject: Re: [ST
Oops, sry: I should have sent this to the whole list but only sent it to
Yann:
-- Forwarded message --
From: Pierre-Paul Paquin <[EMAIL PROTECTED]>
Date: 2008/8/13
Subject: Re: [STUMP] Crash with some GTK apps
To: Yann Ramin <[EMAIL PROTECTED]>
I'm running t
I haven't had these issues gunning the Git version from gd745e76, though
I never had a chance to run 0.9.4. You could give that a try.
Pierre-Paul Paquin wrote:
> Hi,
>
> StumpWM crashes on me with certain programs that map new windows during
> use. Here are the three examples I have, with steps
Hi,
StumpWM crashes on me with certain programs that map new windows during use.
Here are the three examples I have, with steps to reproduce:
1. Pidgin
On start, maps one window (the "buddy list"). If I open the preferences
window and then quit pidgin (either by pressing C-q, or using StumpWM's s
Carlos Konstanski <[EMAIL PROTECTED]> writes:
> Wow, the new error handling is great! It took me a while to realize
> that I could recover from the crash and keep working. Here is the
> >
> Carlos Konstanski
>
>
>
> Recursive lock attempt #S(SB-THREAD:MUTEX
> :NAME "Sch
Wow, the new error handling is great! It took me a while to realize
that I could recover from the crash and keep working. Here is the
backtrace.
Carlos Konstanski
Recursive lock attempt #S(SB-THREAD:MUTEX
:NAME "Scheduler lock"
:%OWNER NIL
48 matches
Mail list logo
