[Bug 206195] New: Keyboard stops responding after VNC configuration.
https://bugzilla.novell.com/show_bug.cgi?id=206195 Summary: Keyboard stops responding after VNC configuration. Product: SUSE LINUX 10.0 Version: unspecified Platform: x86 OS/Version: SLED 10 Status: NEW Severity: Normal Priority: P5 - None Component: X.Org AssignedTo: sndirsch@novell.com ReportedBy: swinn@novell.com QAContact: sndirsch@novell.com If this is not the correct place to enter this bug please help me out by either changing the product/components yourself or at least telling me rather explicitly where the bug should be filed. I tried reporting it on another keyboard related component and was simply told to open a new X11 bug. I don't know exactly which component to report against but I'm trying to bring a very serious problem to someone's attention. Thanks. I've seen this same problem on SLES 10 (x86-64) prior to GMC (gold master candidate, or final release) and SLED 10 (x86) GMC, under similar cirumstances, four times in the last five weeks, always associated with changes to VNC configurations. I'm not sure that it is 100% reproducible but there seems to be a high probablity that playing with VNC settings will cause the problem. I just installed SLED 10 GMC. I enabled VNC during installation. Because of my previous experience with SLES, immediately the install I added a couple of new users, changed screen resolution, used YAST->network services->network services (xinted) to enable all 6 of the VNC options: vnc1, vnc2, vnc3, httpvnc1, ..., and rebooted. (Enabling vnc during install or using remote admin seems to only configure vnc1.) On reboot the local mouse and keyboard are not responding at the GUI login: caps lock detected, alt-ctrl-f1, etc. work, but it doesn't respond to typing a user name or moving the mouse. When I first saw this problem on SLES 10 the helpdesk Linux guru examined the system and said xorg.conf was fouled up, so I have attached the file from this SLED 10 system while it was in a broken state. I have not determined the exact moment the keyboard stops responding but it has always been evident at the login screen. Once I had the local (attached to the machine) keyboard stop responding while I was actually using vnc to view the same session remotely. Once the keyboard/mouse is fouled up it can become increasingly difficult to do anything about it. Bypassing the GUI and running "sax2 -r" fixes the immediate problem but then leaves the system in a state where the vnc2, vnc3, etc. options cannot be used. On one occasion, with SLES 10, after getting the keyboard working again it eventually deteriorated to the point that I had to completely reinstall SLES 10 to recover the GUI funcitonality. The problem started with the GUI, but eventually even a failsafe boot did not recognize the keyboard! That's when I upgraded to SLES 10 FCS and (perhaps only by luck) have not had any more problems. SLED 10 FCS died within minutes of finising the install and seconds of enabling the vnc options. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=206195 ------- Comment #1 from swinn@novell.com 2006-09-15 13:12 MST ------- Created an attachment (id=98849) --> (https://bugzilla.novell.com/attachment.cgi?id=98849&action=view) xorg.conf while keyboard is not responding at GUI login -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=206195 sndirsch@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #98849|application/octet-stream |text/plain mime type| | -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=206195 sndirsch@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |WONTFIX ------- Comment #2 from sndirsch@novell.com 2006-09-17 22:43 MST ------- Another one, who accidentally configured VNC via SaX2. :-( Please don't do this, you simply don't want this. Instead you want to configure VNC via YaSt2 ("Remote administration"). -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=206195 sndirsch@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |ASSIGNED -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=206195 sndirsch@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |NEEDINFO Info Provider| |swinn@novell.com ------- Comment #4 from sndirsch@novell.com 2006-10-23 05:04 MST ------- Although you tell me, that you didn't use SaX2 to configure VNC I can see in the config file that it has been altered for a vnc configuration by SaX2. Yes, it's unfortunate, that there are two places to configure two complete different vnc configurations. Therefore we changed this for openSUSE 10.2 and no longer call it vnc configuration. Is this problem still reproducable after reconfiguring X11 without VNC? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=206195 swinn@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED Info Provider|swinn@novell.com | -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=206195 swinn@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |NEW ------- Comment #5 from swinn@novell.com 2006-10-23 09:40 MST ------- I'm not sure how to respond to your quetions about configuring X11 without VNC because, as far as I know, I've never tried it. My report is simpoly that, more than once, just after configuring VNC through the GUI utilities the keyboard and mouse stopped responding. Since it happened several times in the first few weeks that I used SLES 10, and within minutes of installing and configuring VNC on SLED 10, I filed my initial report. I do not know for certain which component is causing the problem, and I have no idea which components edit the configuraito file. But I am reasonably sure it is associated with enabling the various VNC screen resolutions. My goal was to enable VNC for normal and web access at all supported screen resolutions. To do that I used only the GUI utilities available under Yast. Since I must use my system for software development I am reluctant to experiment too much now that it is stable. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=206195 sndirsch@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |swinn@novell.com ------- Comment #6 from sndirsch@novell.com 2006-10-23 21:48 MST ------- I asked you to reconfigure X11 with SaX2, this time without enabling VNC inside SaX2. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=206195 swinn@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW Info Provider|swinn@novell.com | ------- Comment #7 from swinn@novell.com 2006-10-24 09:36 MST ------- I'm sorry, have deadlines to meet also. I assume that you have experienced testing personnel who know much more than I about Linux and what needs to be done to isolate the problem further. That's why I reported the bug. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=206195 sndirsch@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |WONTFIX ------- Comment #8 from sndirsch@novell.com 2006-10-24 09:42 MST ------- Ok. No problem. If you don't have the time to investigate this issue together with me (this is how reporting bugs work usually), we should better close this issue as WONTFIX. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=206195 ------- Comment #10 from sndirsch@novell.com 2006-10-26 17:56 MST -------
Steve doesn't know how to "reconfigure X11 with SaX2, this time without enabling VNC inside SaX2". That's what he was trying to tell you. Steve, just call "sax2" inside your favorite terminal - xterm, konsole, gnome-terminal or whatever you use. Hope this helps.
-- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
participants (1)
-
bugzilla_noreply＠novell.com