Re: Problem in which x-package?
I posted this to the list yesterday, but apparently it took a wrong
turn somewhere, because it's not in the archives. Apologies to anyone
who gets this twice.
On Mon, Aug 13, 2001 at 11:47:24AM -0400, David Z Maze <dmaze@debian.org> wrote:
> Tim van Erven <tripudium@chello.nl> writes:
> TvE> When I create the file ~/.xsession, X won't start anymore. I want to
> TvE> report this as a bug. Please advise on the relevant package.
>
> This is really not enough information to help figure out what's
> wrong.
I thought I'd be brief and then provide full info in the bugreport.
Sorry for ignoring your questions, but I've already found out the cause
of my problem. It was a minor bug in the windowmaker documentation that
confused me:
In /usr/doc/wmaker/README.Debian.gz:
"To run Window Maker put this at the end of ~/.xsession:
exec /usr/bin/X11/wmaker"
Because ~/.xsession didn't exist, I did:
cd; echo exec /usr/bin/X11/wmaker > .xsession
Now, the wmaker binary isn't in /usr/bin/X11/; it's in /usr/bin/. I'm
sure you can imagine the symptoms this would cause: X appears to be
starting normally, screen goes to black, sound of relay in monitor
switching resolution, back at the prompt. (Apparently my monitor
doesn't switch resolutions fast enough for me to catch the gray default
X screen flashing by.) I interpreted this as "X not starting anymore".
So I went looking for a cause. Here's a diff between the logfiles X
generated before and after my change:
--- XFree86.0.log-before Mon Aug 13 16:53:49 2001
+++ XFree86.0.log-after Mon Aug 13 16:54:27 2001
@@ -7,7 +7,7 @@
reporting problems. (See http://www.XFree86.Org/FAQ)
Operating System: Linux 2.2.19 i686 [ELF]
Module Loader present
-(==) Log file: "/var/log/XFree86.0.log", Time: Mon Aug 13 16:53:05
2001
+(==) Log file: "/var/log/XFree86.0.log", Time: Mon Aug 13 16:54:11
2001
(==) Using config file: "/etc/X11/XF86Config-4"
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
@@ -428,8 +428,8 @@
(==) TDFX(0): Write-combining range (0xe8000000,0x2000000)
(II) TDFX(0): Textures Memory 10.99 MB
(0): [drm] created "tdfx" driver at busid "PCI:1:0:0"
-(0): [drm] added 4096 byte SAREA at 0xc15cf000
-(0): [drm] mapped SAREA 0xc15cf000 to 0x40016000
+(0): [drm] added 4096 byte SAREA at 0xc1b20000
+(0): [drm] mapped SAREA 0xc1b20000 to 0x40016000
(0): [drm] framebuffer handle = 0xe8000000
(0): [drm] added 1 reserved context for kernel
(II) TDFX(0): [drm] Registers = 0xe4000000
@@ -474,4 +474,5 @@
(II) Keyboard "Keyboard1" handled by legacy driver
(II) XINPUT: Adding extended input device "Mouse1" (type: MOUSE)
(0): [drm] removed 1 reserved context for kernel
-(0): [drm] unmapping 4096 bytes of SAREA 0xc15cf000 at 0x40016000
+DRIUnlock called when not locked
+(0): [drm] unmapping 4096 bytes of SAREA 0xc1b20000 at 0x40016000
Notice the: '+DRIUnlock called when not locked'. This is at the end of
the 'after' logfile. So now I've got:
- X not starting anymore
- new line at end of log that looks like a serious error message
- XF86Config is fine, because it worked before
So I came to the wrong conclusion that it must be a bug in X. Next time
I'll have some coffee before running off to file bugreports. :)
--
Tim van Erven
tripudium@chello.nl
talerven@wins.uva.nl
Reply to: