edfedf
23rd April 2010, 02:39 PM
Hi - F13 kept up to date with test updates. Today did the following updates:
Apr 23 07:11:14 Updated: tigervnc-server-1.0.90-0.9.20100420svn4030.fc13.x86_64
Apr 23 07:11:17 Updated: tigervnc-1.0.90-0.9.20100420svn4030.fc13.x86_64
Apr 23 07:11:17 Updated: tigervnc-server-module-1.0.90-0.9.20100420svn4030.fc13.x86_64
If I start a VNC server (X display :1), I can start a session, bring up a gnome-terminal, but as soon as I hit a keyboard key (any key), the Xvnc disappears; nothing written to system log or the .vnc session log. This just began this morning.
Prior to this morning, I was having a vnc problem where the up-arrow key on a standard 105 key PC keyboard would echo as "A" and not have the desired effect. I'd tried xev on a gnome-terminal session, and discovered that pressing the up-arrow (0x62 keycode) key would transmit a press of Shift_L as well as Up.
SHould I be filing a bug on this? If so, where do I do that?
Thanks,
Eric Frey
NVIDIDA
Apr 23 07:11:14 Updated: tigervnc-server-1.0.90-0.9.20100420svn4030.fc13.x86_64
Apr 23 07:11:17 Updated: tigervnc-1.0.90-0.9.20100420svn4030.fc13.x86_64
Apr 23 07:11:17 Updated: tigervnc-server-module-1.0.90-0.9.20100420svn4030.fc13.x86_64
If I start a VNC server (X display :1), I can start a session, bring up a gnome-terminal, but as soon as I hit a keyboard key (any key), the Xvnc disappears; nothing written to system log or the .vnc session log. This just began this morning.
Prior to this morning, I was having a vnc problem where the up-arrow key on a standard 105 key PC keyboard would echo as "A" and not have the desired effect. I'd tried xev on a gnome-terminal session, and discovered that pressing the up-arrow (0x62 keycode) key would transmit a press of Shift_L as well as Up.
SHould I be filing a bug on this? If so, where do I do that?
Thanks,
Eric Frey
NVIDIDA
