Hi Richard, on Saturday, 2006-05-13 at 10:29:53, you wrote: > Well the building of static libraries is on a per package basis, so I > guess your fastest option here is to copy the qt ebuild to your > overlay directory and modify it to make a static library. You could > also file a bug report on bugzilla requesting the change for qt, if > there isn't already an existing report for this.
OK, I'll try the local ebuild first.
> However, my guess is that you are on the wrong track. It really
> sounds like the DISPLAY environment variable is not set correctly, or
> possibly the program is modifying it's own environment for some
> reason....maybe an strace of the program would reveal more.
Well, other X programs work just fine from the same ssh session, so it
can't be the environment. The program doesn't modify anything in it
either, I checked that much. But the strace I hadn't tried yet---here's
the halfway interesting bit:
| access("/usr/lib/qt3//plugins", F_OK) = -1 ENOENT (No such file or
directory)
| access("/root/.qt", F_OK) = 0
| lstat64("/root/.qt", {st_mode=S_IFDIR|0755, st_size=4096, ...}) = 0
| brk(0x868a000) = 0x868a000
| access("/etc/X11//qtrc", F_OK) = -1 ENOENT (No such file or
directory)
| access("/root/.qt/qtrc", F_OK) = 0
| [trying to read empty qtrc]
| munmap(0x40000000, 4096) = 0
| fcntl64(3, F_SETLKW64, {type=F_UNLCK, whence=SEEK_SET, start=0, len=0},
0xbf9dbe60) = 0
| close(3) = 0
| write(2, "usrmgr: cannot connect to X serv"..., 35usrmgr: cannot connect to X
server ) = 35
It doesn't matter if the plugins dir ot /root/.qt/qtrc is there or not.
I can even put the old server's /etc/X11/qtrc in place, no difference.
I'll play with strace some more, looks like the program used some call
that's not traced by default because it's not even trying to read
$DISPLAY; the error seems to be something generic.
cheers!
Matthias
--
I prefer encrypted and signed messages. KeyID: FAC37665
Fingerprint: 8C16 3F0A A6FC DF0D 19B0 8DEF 48D9 1700 FAC3 7665
pgpuk1Hq2ehBK.pgp
Description: PGP signature
