Re: Xvnc working?
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Don Hayward wrote:
| On Sat, 6 Nov 2004, Harald Dunkel wrote:
|
|> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 > Hi folks, > Did
|> anybody succeed in running Xvnc on a Debian amd64 box? Or do I have
|> to use the 32bit version?
|
|
| I'm running the packages (xvncserver,xvncviewer) from the gcc-3.4
| archive without problems.
|
I am on gcc-3.4, too. But on my PC 'Xvnc :1' dies with SEGV.
Both tightvnc and vncserver.
It happens during initalization. strace says (vncerver 3.3.7):
:
:
bind(1, {sa_family=AF_FILE, path="/tmp/.X11-unix/X1"}, 19) = 0
listen(1, 128) = 0
umask(022) = 0
ioctl(0, SIOCGIFCONF, {80, {{"lo", {AF_INET, inet_addr("127.0.0.1")}}, {"eth0", {AF_INET, inet_addr("192.168.1.10")}}}}) = 0
ioctl(0, SIOCGIFFLAGS, 0x7fbfffeed0) = 0
ioctl(0, SIOCGIFBRDADDR, 0x7fbfffeed0) = 0
rt_sigaction(SIGPIPE, {SIG_IGN}, {SIG_DFL}, 8) = 0
rt_sigaction(SIGHUP, {0x431d20, [HUP], 0x4000000}, {SIG_DFL}, 8) = 0
rt_sigaction(SIGINT, {0x431d30, [INT], 0x4000000}, {SIG_DFL}, 8) = 0
rt_sigaction(SIGTERM, {0x431d30, [TERM], 0x4000000}, {SIG_DFL}, 8) = 0
open("/etc/X1.hosts", O_RDONLY) = -1 ENOENT (No such file or directory)
rt_sigaction(SIGUSR1, {SIG_IGN}, {SIG_DFL}, 8) = 0
getppid() = 5990
open("/etc/localtime", O_RDONLY) = 3
fstat(3, {st_mode=S_IFREG|0644, st_size=837, ...}) = 0
mmap(NULL, 131072, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x2a9556c000
read(3, "TZif\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\10\0\0\0\10"..., 131072) = 837
close(3) = 0
munmap(0x2a9556c000, 131072) = 0
- --- SIGSEGV (Segmentation fault) @ 0 (0) ---
+++ killed by SIGSEGV (core dumped) +++
Seems that the last step is to read some timezone information,
then it dies.
Does anybody know where to find some vncserver 4.0 debs?
Regards
Harri
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (GNU/Linux)
Comment: Using GnuPG with Debian - http://enigmail.mozdev.org
iD8DBQFBjRePUTlbRTxpHjcRAmdmAKCI7VcT34LVOHWPCkPwf1PfMW9o+ACffCsk
H+18RWMjpxHEJp839qNFlmo=
=mPoh
-----END PGP SIGNATURE-----
Reply to: