I am using Debian sid i686 with xorg server
libuim0 version 0.4.7-1
uim-m17nlib version 0.4.7-1
uim version 0.4.7-1
uim-common version 0.4.7-1
uim-utils version 0.4.7-1
uim-gtk2.0 version 0.4.7-1
uim-xim version 0.4.7-1
I have selected default input method m17n-zh-py for chinese piying input usi
Package: tuxeyes
Version: 0.0.3-7
Severity: normal
*** Please type your report below this line ***
[EMAIL PROTECTED]:~/tuxeyes-0.0.3$ tuxeyes -display 192.168.0.2:0
tuXeyes version 0.0.3 is (c) 1999 Ivo van der Wijk ([EMAIL PROTECTED])
Check http://vanderwijk.info/tuXeyes/ for more info and updat
I meant exporting DISPLAY=192.168.0.2:0 works of course.
DISPLAY=192.168.0.2 rightfully bring the error "tuxeyes: cannot connect to X
server 192.168.0.2"
Here's gdb output (after having blanked DISPLAY environnement variable)
Starting program: /mnt/hda3/home/nirgal/tuxeyes-0.
mory leak, but my guess is that the
whole latency computation is... let's say weird. Why are we timing
esd_get_server_info if we later use esd_get_latency? And why only when host is
remote?
-- Nirgal
vlc_0.8.6-svn20061012.debian-1.remoteesd.diff.gz
Description: GNU Zip compressed data
4 matches
Mail list logo