Bug#369502: x11-common: /usr/bin/X doesn't start X anymore
Can you try: x11-common 7.1.0-1 X Window System (X.Org) infrastructure If this is not a problem, can someone close this? Thanks, Shawn. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#369502: x11-common: /usr/bin/X doesn't start X anymore
Package: x11-common Version: 1:7.0.20 Severity: important After an upgrade from xorg 6.9 to 7.0, startx and other scripts dont work anymore, because xorg isnt started by using X but by using Xorg. IMHO for compatibility and especialy during the transition X should be a wrapper around Xorg. Interestingly X itself doesn't print any error why it couldnt start x, it just exits. There is not even a warning. IMHO this should be fixed to, to avoid problems during and after upgrade Attila Kinali -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (990, 'unstable'), (500, 'testing') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.16.9 Locale: LANG=de_CH, LC_CTYPE=de_CH (charmap=ISO-8859-1) Versions of packages x11-common depends on: ii debconf [debconf-2.0] 1.5.1 Debian configuration management sy ii debianutils 2.16.1 Miscellaneous utilities specific t ii lsb-base 3.1-5 Linux Standard Base 3.1 init scrip x11-common recommends no packages. -- debconf information: * x11-common/xwrapper/allowed_users: Console Users Only x11-common/experimental_packages: x11-common/xwrapper/actual_allowed_users: console x11-common/xwrapper/nice_value/error: * x11-common/upgrade_issues: * x11-common/xwrapper/nice_value: -10 * x11-common/x11r6_bin_not_empty: -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#369502: x11-common: /usr/bin/X doesn't start X anymore
On Tue, 30 May 2006, Attila Kinali wrote: After an upgrade from xorg 6.9 to 7.0, startx and other scripts dont work anymore, because xorg isnt started by using X but by using Xorg. IMHO for compatibility and especialy during the transition X should be a wrapper around Xorg. Interestingly X itself doesn't print any error why it couldnt start x, it just exits. There is not even a warning. IMHO this should be fixed to, to avoid problems during and after upgrade Please check if your /etc/X11/X symlink points to /bin/true - for me this had happened on update 6.9-7.0 - this symlink needs to point to /usr/bin/Xorg for everything to work. c'ya sven -- The Internet treats censorship as a routing problem, and routes around it. (John Gilmore on http://www.cygnus.com/~gnu/) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#369502: x11-common: /usr/bin/X doesn't start X anymore
On Tue, 30 May 2006 11:24:23 +0200
Michel Dänzer [EMAIL PROTECTED] wrote:
On Tue, 2006-05-30 at 10:52 +0200, Attila Kinali wrote:
Package: x11-common
Version: 1:7.0.20
Severity: important
After an upgrade from xorg 6.9 to 7.0, startx and other scripts
dont work anymore, because xorg isnt started by using X but by using Xorg.
IMHO for compatibility and especialy during the transition X should be
a wrapper around Xorg.
That's exactly what /usr/bin/X in x11-common is. If this problem isn't
covered by #369504, please provide more details about what the problem
is.
For one, it doesn't do what it should do. If i run /usr/bin/X
the follwing happens:
---
jashugan:~# /usr/bin/X
jashugan:~#
---
/var/log/Xorg.0.log is not been touched at all. There is simply nothing
that would reveal anything.
Running an strace looks like this:
---
jashugan:~# strace -f /usr/bin/X
execve(/usr/bin/X, [/usr/bin/X], [/* 27 vars */]) = 0
uname({sys=Linux, node=jashugan, ...}) = 0
brk(0) = 0x804b000
access(/etc/ld.so.nohwcap, F_OK) = -1 ENOENT (No such file or directory)
mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0xb7f41000
access(/etc/ld.so.preload, R_OK) = -1 ENOENT (No such file or directory)
mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0xb7f4
open(/etc/ld.so.cache, O_RDONLY) = 3
fstat64(3, {st_mode=S_IFREG|0644, st_size=59503, ...}) = 0
mmap2(NULL, 59503, PROT_READ, MAP_PRIVATE, 3, 0) = 0xb7f31000
close(3)= 0
access(/etc/ld.so.nohwcap, F_OK) = -1 ENOENT (No such file or directory)
open(/lib/tls/libc.so.6, O_RDONLY)= 3
read(3, \177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0\3\0\1\0\0\0\260O\1..., 512) = 512
fstat64(3, {st_mode=S_IFREG|0755, st_size=1270928, ...}) = 0
mmap2(NULL, 1276892, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) =
0xb7df9000
mmap2(0xb7f27000, 32768, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x12e) = 0xb7f27000
mmap2(0xb7f2f000, 7132, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0xb7f2f000
close(3)= 0
mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0xb7df8000
mprotect(0xb7f27000, 20480, PROT_READ) = 0
set_thread_area({entry_number:-1 - 6, base_addr:0xb7df86c0, limit:1048575,
seg_32bit:1, contents:0, read_exec_only:0, limit_in_pages:1, seg_not_present:0,
useable:1}) = 0
munmap(0xb7f31000, 59503) = 0
brk(0) = 0x804b000
brk(0x806c000) = 0x806c000
open(/etc/X11/Xwrapper.config, O_RDONLY) = 3
fstat64(3, {st_mode=S_IFREG|0600, st_size=616, ...}) = 0
mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0xb7f3f000
read(3, # Xwrapper.config (Debian X Wind..., 4096) = 616
read(3, , 4096) = 0
close(3)= 0
munmap(0xb7f3f000, 4096)= 0
lstat64(/etc/X11/X, {st_mode=S_IFLNK|0777, st_size=9, ...}) = 0
readlink(/etc/X11/X, /bin/true, 1024) = 9
access(/etc/X11/X, X_OK) = 0
getuid32() = 0
umask(0)= 022
mkdir(/tmp/.X11-unix, 01777) = -1 EEXIST (File exists)
umask(022) = 0
lstat64(/tmp/.X11-unix, {st_mode=S_IFDIR|S_ISVTX|0777, st_size=4096, ...}) = 0
stat64(/dev/dri, {st_mode=S_IFDIR|0755, st_size=4096, ...}) = 0
setresuid32(-1, 0, -1) = 0
getpriority(PRIO_PROCESS, 0)= 20
setpriority(PRIO_PROCESS, 0, -10) = 0
getpriority(PRIO_PROCESS, 0)= 30
chdir(/etc/X11) = 0
execve(/bin/true, [/usr/bin/X], [/* 27 vars */]) = 0
uname({sys=Linux, node=jashugan, ...}) = 0
brk(0) = 0x804c000
access(/etc/ld.so.nohwcap, F_OK) = -1 ENOENT (No such file or directory)
mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0xb7f9a000
access(/etc/ld.so.preload, R_OK) = -1 ENOENT (No such file or directory)
mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0xb7f99000
open(/etc/ld.so.cache, O_RDONLY) = 3
fstat64(3, {st_mode=S_IFREG|0644, st_size=59503, ...}) = 0
mmap2(NULL, 59503, PROT_READ, MAP_PRIVATE, 3, 0) = 0xb7f8a000
close(3)= 0
access(/etc/ld.so.nohwcap, F_OK) = -1 ENOENT (No such file or directory)
open(/lib/tls/libc.so.6, O_RDONLY)= 3
read(3, \177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0\3\0\1\0\0\0\260O\1..., 512) = 512
fstat64(3, {st_mode=S_IFREG|0755, st_size=1270928, ...}) = 0
mmap2(NULL, 1276892, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) =
0xb7e52000
mmap2(0xb7f8, 32768, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x12e) = 0xb7f8
mmap2(0xb7f88000, 7132, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0xb7f88000
close(3)
Bug#369502: x11-common: /usr/bin/X doesn't start X anymore
On Tue, 2006-05-30 at 10:52 +0200, Attila Kinali wrote: Package: x11-common Version: 1:7.0.20 Severity: important After an upgrade from xorg 6.9 to 7.0, startx and other scripts dont work anymore, because xorg isnt started by using X but by using Xorg. IMHO for compatibility and especialy during the transition X should be a wrapper around Xorg. That's exactly what /usr/bin/X in x11-common is. If this problem isn't covered by #369504, please provide more details about what the problem is. -- Earthling Michel Dänzer | http://tungstengraphics.com Libre software enthusiast | Debian, X and DRI developer
Bug#369502: x11-common: /usr/bin/X doesn't start X anymore
On Tue, 30 May 2006 11:26:59 +0200 (CEST) Sven-Haegar Koch [EMAIL PROTECTED] wrote: Please check if your /etc/X11/X symlink points to /bin/true - for me this had happened on update 6.9-7.0 - this symlink needs to point to /usr/bin/Xorg for everything to work. Hmm.. Looks like that was it. Now the question is how did the symlink end up pointing to /bin/true? Attila Kinali -- 心をこめて聞け心をこめて話せ
Bug#369502: x11-common: /usr/bin/X doesn't start X anymore
On Tue, May 30, 2006 at 11:42:28AM +0200, Attila Kinali wrote: On Tue, 30 May 2006 11:26:59 +0200 (CEST) Sven-Haegar Koch [EMAIL PROTECTED] wrote: Please check if your /etc/X11/X symlink points to /bin/true - for me this had happened on update 6.9-7.0 - this symlink needs to point to /usr/bin/Xorg for everything to work. Hmm.. Looks like that was it. Now the question is how did the symlink end up pointing to /bin/true? Argh... that was supposed to have been fixed a while ago. I'll take a look and try and figure out what's wrong. - David Nusinow -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
