[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [STUMP] Building StumpWM/CLisp on Ubuntu
From: |
Sébastien Vauban |
Subject: |
Re: [STUMP] Building StumpWM/CLisp on Ubuntu |
Date: |
Tue, 10 Nov 2009 13:56:35 +0100 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/23.1.50 (gnu/linux) |
Hi Vitaly,
Vitaly Mayatskikh wrote:
> At Mon, 09 Nov 2009 17:12:26 +0100, Sébastien Vauban wrote:
>
>> Though, I now have that file correctly written:
>>
>> --8<---------------cut here---------------start------------->8---
>> -rw------- 1 sva sva 0 2009-11-04 11:43 .Xauthority
>> -rw-r--r-- 1 sva sva 82 2009-11-09 15:08 .Xclients
>> -rw-r--r-- 1 sva sva 1339 2009-11-05 15:22 .Xdefaults
>> -rw-r--r-- 1 sva sva 553 2009-11-04 14:35 .Xmodmap
>> -rw-r--r-- 1 sva sva 82 2009-11-09 16:57 .xsession
>> --8<---------------cut here---------------end--------------->8---
>>
>> containing:
>>
>> --8<---------------cut here---------------start------------->8---
>> setxkbmap -model "pc105" -layout "fr,gb" -option
>> "grp:caps_toggle,grp_led:scroll"
>> --8<---------------cut here---------------end--------------->8---
>>
>> And it's still the same. Qwerty keyboard, not able to switch to Azerty.
>
> If you're still interested, try to run X under strace and see, what is going
> on with .xsession.
I don't know if this is the correct method, but here is what I did:
1. logged out of StumpWM, back to GDM
2. logged in, choosing xterm as Session
3. in xterm window, typed "script console.log"
4. typed "strace stumpwm"
Then I got a huge trace...
--8<---------------cut here---------------start------------->8---
Script started on Tue 10 Nov 2009 01:42:42 PM CET
[1m[7m%[27m[1m[0m
[0m[27m[24m[J
[1;address@hidden ~>[0m[Ksstrace stumpwm
execve("/usr/local/bin/stumpwm", ["stumpwm"], [/* 32 vars */]) = 0
brk(0) = 0x95bc000
access("/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or directory)
mmap2(NULL, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0xa0c000
access("/etc/ld.so.preload", R_OK) = -1 ENOENT (No such file or directory)
open("/etc/ld.so.cache", O_RDONLY) = 3
fstat64(3, {st_mode=S_IFREG|0644, st_size=77992, ...}) = 0
mmap2(NULL, 77992, PROT_READ, MAP_PRIVATE, 3, 0) = 0x178000
close(3) = 0
access("/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or directory)
open("/lib/tls/i686/cmov/libdl.so.2", O_RDONLY) = 3
read(3, "address@hidden"..., 512) = 512
fstat64(3, {st_mode=S_IFREG|0644, st_size=9736, ...}) = 0
mmap2(NULL, 12408, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) =
0x2a8000
mmap2(0x2aa000, 8192, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x1) = 0x2aa000
close(3) = 0
access("/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or directory)
[...]
--8<---------------cut here---------------end--------------->8---
... ending in a crash...
--8<---------------cut here---------------start------------->8---
rt_sigprocmask(SIG_BLOCK, [HUP INT QUIT USR2 PIPE ALRM TERM CHLD TSTP URG XCPU
XFSZ VTALRM PROF WINCH IO], [HUP INT QUIT USR2 PIPE ALRM TERM CHLD TSTP URG
XCPU XFSZ VTALRM PROF WINCH IO], 8) = 0
write(2, "CORRUPTION WARNING", 18CORRUPTION WARNING) = 18
write(2, " in SBCL pid 2391", 17 in SBCL pid 2391) = 17
write(2, "(tid 3085186752)", 16(tid 3085186752)) = 16
write(2, ":\n", 2:
) = 2
write(2, "Enabling blocked gc signals to a"..., 219Enabling blocked gc signals
to allow returning to Lisp without risking
gc deadlocks. Since GC signals are only blocked in signal handlers when
they are not safe to interrupt at all, this is a pretty severe occurrence.
) = 219
write(2, "\n", 1
) = 1
write(2, "The integrity of this image is p"..., 53The integrity of this image
is possibly compromised.
) = 53
write(2, "Continuing with fingers crossed."..., 33Continuing with fingers
crossed.
) = 33
rt_sigprocmask(SIG_SETMASK, [HUP INT QUIT USR2 PIPE ALRM TERM CHLD TSTP URG
XCPU XFSZ VTALRM PROF WINCH IO], NULL, 8) = 0
--- SIGSEGV (Segmentation fault) @ 0 (0) ---
--- SIGSEGV (Segmentation fault) @ 0 (0) ---
+++ killed by SIGSEGV +++
--8<---------------cut here---------------end--------------->8---
Then, I just typed "stumpwm", which has been launched normally!?
But I cannot find any reference, in the whole console.log file, to "rc", ".x",
"client", etc.
> Otherwise you can run setxkbmap from ~/.stumpwmrc ;)
That does work like a charm. Thanks a lot!
Though this does not seem to be related with that (?), I now have Num_Lock on
by default as soon as I enter the X session. I just have to disable it once
per session, but I wonder from where that comes...
Best regards,
Seb
--
Sébastien Vauban
- Re: [STUMP] Building StumpWM/CLisp on Ubuntu, (continued)
- Re: [STUMP] Building StumpWM/CLisp on Ubuntu, Sébastien Vauban, 2009/11/06
- Re: [STUMP] Building StumpWM/CLisp on Ubuntu, Vitaly Mayatskikh, 2009/11/06
- Re: [STUMP] Building StumpWM/CLisp on Ubuntu, Sébastien Vauban, 2009/11/09
- Re: [STUMP] Building StumpWM/CLisp on Ubuntu, Vitaly Mayatskikh, 2009/11/09
- Re: [STUMP] Building StumpWM/CLisp on Ubuntu, Sébastien Vauban, 2009/11/09
- Re: [STUMP] Building StumpWM/CLisp on Ubuntu, Vitaly Mayatskikh, 2009/11/09
- Re: [STUMP] Building StumpWM/CLisp on Ubuntu, Sébastien Vauban, 2009/11/09
- Re: [STUMP] Building StumpWM/CLisp on Ubuntu, Vitaly Mayatskikh, 2009/11/09
- Re: [STUMP] Building StumpWM/CLisp on Ubuntu,
Sébastien Vauban <=
- Re: [STUMP] Building StumpWM/CLisp on Ubuntu, Sébastien Vauban, 2009/11/10
- Re: [STUMP] Building StumpWM/CLisp on Ubuntu, Vitaly Mayatskikh, 2009/11/10
- Re: [STUMP] Building StumpWM/CLisp on Ubuntu, Sébastien Vauban, 2009/11/10
Re: [STUMP] Building StumpWM/CLisp on Ubuntu, Jay Belanger, 2009/11/01