Skip to content

one problem occured when I start it #1

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

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
#:
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
@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
#:
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
@reverland

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

echo $DISPLAY
:0

@sabetts
@reverland

0] backtrace

0: (PARSE-INTEGER "" :START 0 :END NIL :RADIX 10 :JUNK-ALLOWED NIL)
1: (XLIB::READ-XAUTH-ENTRY
#)
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
@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
@reverland

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

@sabetts
@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
@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
sabetts commented May 18, 2012

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

@sabetts sabetts closed this May 18, 2012
@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

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
Something went wrong with that request. Please try again.