one problem occured when I start it #1

Closed
reverland opened this Issue May 14, 2012 · 19 comments

Projects

None yet

4 participants

@reverland

I following the recommended instruction on https://wiki.archlinux.org/index.php/Stumpwm#Happy_hacking.21
but when I start ./stupwm,It returns the following lines in sbcl:

debugger invoked on a SB-INT:SIMPLE-PARSE-ERROR in thread
#<THREAD "initial thread" RUNNING {1003AE1143}>:
no non-whitespace characters in string "".

Type HELP for debugger help, or (SB-EXT:QUIT) to exit from SBCL.

(no restarts: If you didn't do this on purpose, please report it as a bug.)

(PARSE-INTEGER "" :START 0 :END NIL :RADIX 10 :JUNK-ALLOWED NIL)

I tred to find some idea in google but failed.So,Is there any idea on this problem?
However,I once tried another commonlisp wm named clfswm,It has the same problem as well..

I've seen someone else had the same problem but he finally succeded on debian.

@sabetts
Collaborator
sabetts commented May 14, 2012

On Sun, May 13, 2012 at 10:09 PM, reverland
reply@reply.github.com
wrote:

I following the recommended instruction on https://wiki.archlinux.org/index.php/Stumpwm#Happy_hacking.21
but when I start ./stupwm,It returns the following lines in sbcl:

debugger invoked on a SB-INT:SIMPLE-PARSE-ERROR in thread
     #<THREAD "initial thread" RUNNING {1003AE1143}>:
    no non-whitespace characters in string "".

Type HELP for debugger help, or (SB-EXT:QUIT) to exit from SBCL.

(no restarts: If you didn't do this on purpose, please report it as a bug.)

(PARSE-INTEGER "" :START 0 :END NIL :RADIX 10 :JUNK-ALLOWED NIL)

Have you started the x server? What version of stumpwm?

-Shawn

@reverland

I started it directly in kde,just type it in the terminal.

./stupmwm

stumpwm was just cloned from here yesterday! So It should be the newest.

when I used startx in the console,It returns

X.Org X Server 1.12.1
Release Date: 2012-04-13
X Protocol Version 11, Revision 0
Build Operating System: Linux 3.3.1-1-ARCH x86_64
Current Operating System: Linux arch 3.3.5-1-ARCH #1 SMP PREEMPT Mon May 7 19:57:51 CEST 2012 x86_64
Kernel command line: root=/dev/disk/by-uuid/1a452b5f-e60d-4823-bedf-c89cbfd450e2 ro initrd=../initramfs-linux.img BOOT_IMAGE=../vmlinuz-linux
Build Date: 14 April 2012 07:09:45AM

Current version of pixman: 0.24.4
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.1.log", Time: Tue May 15 08:26:45 2012
(==) Using config file: "/etc/X11/xorg.conf"
(==) Using config directory: "/etc/X11/xorg.conf.d"

debugger invoked on a SB-INT:SIMPLE-PARSE-ERROR in thread
#<THREAD "initial thread" RUNNING {1003AE1043}>:
no non-whitespace characters in string "".

Type HELP for debugger help, or (SB-EXT:QUIT) to exit from SBCL.

(no restarts: If you didn't do this on purpose, please report it as a bug.)

(PARSE-INTEGER "" :START 0 :END NIL :RADIX 10 :JUNK-ALLOWED NIL)
0]

@sabetts
Collaborator
sabetts commented May 15, 2012

On Mon, May 14, 2012 at 5:28 PM, reverland
reply@reply.github.com
wrote:

I started it directly in kde,just type it in the terminal.

./stupmwm
stumpwm was just cloned from here yesterday! So It should be the newest.

(PARSE-INTEGER "" :START 0 :END NIL :RADIX 10 :JUNK-ALLOWED NIL)

Sounds like maybe it's borking trying to parse the DISPLAY environment
variable. Can you post what it is?

-Shawn

@reverland

sorry,I can't figure out what you meant.what does borking mean?
if you means $DISPLAY,its

echo $DISPLAY
:0

@sabetts
Collaborator
sabetts commented May 16, 2012

On Tue, May 15, 2012 at 4:30 PM, reverland
reply@reply.github.com
wrote:

sorry,I can't figure out what you meant.what does borking mean? and -Shawn?
if you means $DISPLAY,its

echo $DISPLAY
     :0

Sounds like it isn't a problem with $DISPLAY. When you ran ./stumpwm
in your initial report it looks like it dropped to the interactive
debugger. Can you run it again as you did before and then type:

backtrace

and post the output. That should narrow down where it's borking.

@reverland

0] backtrace

0: (PARSE-INTEGER "" :START 0 :END NIL :RADIX 10 :JUNK-ALLOWED NIL)
1: (XLIB::READ-XAUTH-ENTRY
#<SB-SYS:FD-STREAM for "file /home/lyy/.Xauthority" {1003C10EA3}>)
2: (XLIB::GET-BEST-AUTHORIZATION "" 0 :LOCAL)
3: (XLIB:OPEN-DISPLAY
""
:DISPLAY
0
:PROTOCOL
:LOCAL
:AUTHORIZATION-NAME
NIL
:AUTHORIZATION-DATA
NIL)
4: (STUMPWM::STUMPWM-INTERNAL ":0")
5: (STUMPWM:STUMPWM ":0")
6: ((LAMBDA () :IN "/home/lyy/Downloads/stumpwm/make-image.lisp"))
7: ((FLET #:WITHOUT-INTERRUPTS-BODY-235639 :IN SAVE-LISP-AND-DIE))
8: ((LABELS SB-IMPL::RESTART-LISP :IN SAVE-LISP-AND-DIE))

junkallowed NIL??

@sabetts
Collaborator
sabetts commented May 16, 2012

On Tue, May 15, 2012 at 9:51 PM, reverland
reply@reply.github.com
wrote:

0] backtrace

0: (PARSE-INTEGER "" :START 0 :END NIL :RADIX 10 :JUNK-ALLOWED NIL)
1: (XLIB::READ-XAUTH-ENTRY
   #<SB-SYS:FD-STREAM for "file /home/lyy/.Xauthority" {1003C10EA3}>)
2: (XLIB::GET-BEST-AUTHORIZATION "" 0 :LOCAL)

looks like you've found a bug in CLX. Did you install clx through AUR
or quicklisp? If AUR, it looks like the CLX package is a bit old:
http://aur.archlinux.org/packages.php?ID=12084 maybe try clx-git?
http://aur.archlinux.org/packages.php?ID=58665 I don't use archlinux
so I'm just guessing.

But if you got clx from quicklisp, then that's a different story since
that's pretty up to date. You should make sure your copy of quicklisp
is up to date. Maybe this bug has been recently fixed.

If all that fails then post a copy of your .Xauthority file and I can
try and reproduce and fix the issue.

@reverland

Thank you for your detailed and warmful help!
I got clx from quicklisp,and I just got all updated the day before yesterday.
Then I delete the .Xauthority,It finally works.
but I don't know whether the file is still useful for you?
and ...how can I post it?

@reverland

Thank you for your detailed and warmful help!
I got clx from quicklisp,and I just got all updated the day before yesterday.
Then I delete the .Xauthority,It finally works.
but I don't know whether the file is still useful for you?
and ...how can I post it?

@reverland

Thank you for your detailed and warmful help!
I got clx from quicklisp,and I just got all updated the day before yesterday.
Then I delete the .Xauthority,It finally works.
but I don't know whether the file is still useful for you?
and ...how can I post it?

@sabetts
Collaborator
sabetts commented May 16, 2012

On Wed, May 16, 2012 at 12:56 AM, reverland
reply@reply.github.com
wrote:

Thank you for your detailed and warmful help!
I got clx from quicklisp,and I just got all updated the day before yesterday.
Then I delete the .Xauthority,It finally works.

Excellent!

but I don't know whether the file is still useful for you?
and ...how can I post it?

Yeah that's a problem with github. You could upload it to a file
hosting service and post the link here. Or base64 encode it and
include it in your message. Or email it to me directly; My email
address is the first entry in the AUTHORS file. Or post it as a bug to
stumpwm's savannah project:
http://savannah.nongnu.org/bugs/?group=stumpwm

-Shawn

@reverland

I've sent it to you via email.Thanks, the wm is amazing.

@sabetts
Collaborator
sabetts commented May 18, 2012

On Wed, May 16, 2012 at 10:22 PM, reverland
reply@reply.github.com
wrote:

I've sent it to you via email.Thanks, the wm is amazing.

Thanks! I tried parsing it with clx-20111203-git that I got from
quicklisp. Here's what I get:

CL-USER> (ql:quickload 'clx)

CL-USER> (with-open-file (s #p"~/downloads/Xauthority.old"
:element-type '(unsigned-byte 8)) (xlib::read-xauth-entry s))

(:INTERNET (172 17 170 110) 0 "MIT-MAGIC-COOKIE-1" #(21 15 96 33 241
121 180 150 43 54 246 190 195 147 80 148))

But this is on a mac running Clozure CL. I didn't have sbcl installed.
If you try the above commands from a fresh SBCL repl, does it break
for you?

-Shawn

@reverland

Thats what I got on Archlinux x86_64 sbcl 1.0.56

(with-open-file (s #p"~/downloads/Xauthority.old" :element-type '(unsigned-byte 8)) (xlib::read-xauth-entry s))

(:INTERNET (172 17 170 110) 0 "MIT-MAGIC-COOKIE-1"
#(21 15 96 33 241 121 180 150 43 54 246 190 195 147 80 148))

@sabetts
Collaborator
sabetts commented May 18, 2012

On Thu, May 17, 2012 at 10:06 PM, reverland
reply@reply.github.com
wrote:

Thats what I got on Archlinux x86_64 sbcl 1.0.56

Ok, it's the 4th entry that breaks CLX. I've reported here:

sharplispers/clx#4

You can wait until it gets fixed and works its way back to you or
apply my quick and dirty fix:

The file is ~/quicklisp/dists/quicklisp/software/clx-20111203-git/display.lisp

--- display.lisp 2012-05-17 23:39:15.000000000 -0700
+++ fixedish-display.lisp 2012-05-17 23:38:43.000000000 -0700
@@ -61,7 +61,7 @@
(if (null family-id)
(list nil nil nil nil nil)
(let* ((address-data (read-short-length-vector stream))

  •             (number (parse-integer (read-short-length-string stream)))
    
  •             (number (parse-integer (read-short-length-string
    
    stream :junk-allowed t)))
    (name (read-short-length-string stream))
    (data (read-short-length-vector stream))
    (family (car (rassoc family-id protocol-families))))

This is quite a terrible fix and I really don't know what that number
field is for in the .xauthority file. So...use at your own risk :).

-Shawn

@reverland

Thankyou,However, when my archlinux was reinstalled yesterday,all is right now...There is no need to delete .Xauthority before start stumpwm.It might be some configuration about kde cause the issue,I think.

@sabetts
Collaborator
sabetts commented May 18, 2012

Good to hear! It looks like this issue has been resolved.

@sabetts sabetts closed this May 18, 2012
@ghost Unknown referenced this issue Jul 18, 2012
Closed

system time update crashes stumpwm #7

@vegard
vegard commented Jul 28, 2014

I had a similar problem as this, the backtrace was basically identical (barfing while reading integer from .Xauthority). Deleting .Xauthority solved the issue when invoking via LISP=sbcl stumpwm in .xinitrc and startx -- :1.

@dbjergaard
Collaborator

This issue was closed 2 years ago. @vegard can you check that this is documented on our wiki? That way it will be more visible to uses who may be plagued by this issue since the problem was ultimately upstream of stumpwm.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment