Bugs item #1358691, was opened at 2005-11-17 06:53
Message generated for change (Comment added) made by ikonst
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=381347&aid=1358691&group_id=24366
Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Dan Furlani (danfurlani)
>Assigned to: Ilya Konstantinov (ikonst)
Summary: Rdesktop client causes whole system to freeze
Initial Comment:
You're not gonna believe this one...
If I open "calc" over rdesktop my whole Linux box
freezes. The mouse cursor can be moved around the
screen but I can't click on anything. The keyboard is
completely unresponsive (num lock doesn't even toggle
the LED). The problem occurs whether the window is
full screen or not. When it is not full screen parts
of the Gnome desktop are visible (obviously) but not
responsive either. Rebooting is the only option.
I'm running Fedora Core 4 (kernel-2.6.13-1.1532_FC4),
rdesktop-1.4.0-2, connecting to Windows XP (without SP2
I think) over VPN ("Cisco Systems VPN Client Version
4.0.4 (B)").
There are other applications that cause the problem. I
have seen it happen twice with the task manager and
once with Excel, but it's extremely (always?)
reproducible using calc -- all I have to do is open it
and I'm hosed. Only half the buttons get drawn, I
think some show up as buttons with no label. I saw it
happen with a dialog in another application (Rational
Rose 2003) and the cancel button was the same way --
outlined but no text -- whereas the OK button was drawn
fine.
As far as I can tell the problem just started happening
one day, it wasn't after I installed or upgraded any
software on my Linux box. I had been using it just
fine for months. IT is in charge of my XP box so who
knows what happened there...
The command I'm using is:
rdesktop -u myNtUserId -a 16 -f myPC.myCompany.com
Once I reboot, relogin to Linux, reVPN, and
re-rdesktop, I can usually close the offending
application and get away with another half hour of work
before it bites me again.
Please tell me what to do! I'm going to try
downloading and compiling source for 1.4.1 and if that
doesn't work (and I get sufficiently frustrated) I'll
try CVS.
Thank you
-Dan Furlani
By the way, it's an excellent application, worked
wonderfully for a long time.
----------------------------------------------------------------------
>Comment By: Ilya Konstantinov (ikonst)
Date: 2005-12-04 22:57
Message:
Logged In: YES
user_id=335423
For now, I'll assign this bug to myself, although I see no
way to reproduce it: calc doesn't hang my session in any
way, not on my Windows XP Service Pack 2, at least.
Since you've managed to shut down your computer properly
after the hang happens and even inspected the kernel logs,
how about you also inspect the XFree86/Xorg logs (e.g.
/var/log/Xorg.0.log) to see what were the last lines written
to this log. You might even want to boot with "linux 3" on
your next boot to avoid booting into GUI and then see what
really was the last thing to be written to it. My guess is
that you'll see a message indicating your X server crashed.
----------------------------------------------------------------------
Comment By: Dan Furlani (danfurlani)
Date: 2005-11-26 03:18
Message:
Logged In: YES
user_id=33408
More info: I tried installing nvidia drivers using both
methods on fedorafaq.org (RPM and Nvidia's installer).
Horribly unstable - X would crash within a minute of logging
in no matter what applications I ran (or didn't). Even with
AGPGART disabled.
I ran FC1, 2, and 3 on the same hardware with no problems,
and was running FC4 for a while just fine -- so what's wrong
now??? This is driving me crazy.
I can start/stop X with telinit 3/5 when this happens now
instead of rebooting.
----------------------------------------------------------------------
Comment By: Dan Furlani (danfurlani)
Date: 2005-11-25 22:19
Message:
Logged In: YES
user_id=33408
I'm not certain, but I think the same sort of problem is
happening with my screensaver sometimes, so I disabled it
for now. It seems strange that a problem could happen
sporadically with one application (screensaver) and
predictably with another (rdesktop + calc).
'yum update' didn't help any, the problem still happens. I
guess I was hoping for an xfree update.
Last time it happened with rdesktop I got console access by
using some combo of Alt-Ctrl-SysRq-R, -S, -K, and Alt-F2 and
from there I could login and reboot (blind). Maybe next
time I can be smarted and just restart X somehow.
The kernel log looks like this:
kernel: SysRq : Keyboard mode set to XLATE
crond(pam_unix)[3286]: session opened for user root by (uid=0)
crond(pam_unix)[3286]: session closed for user root
kernel: SysRq : Emergency Sync
kernel: Emergency Sync complete
kernel: SysRq : Keyboard mode set to XLATE
kernel: SysRq : Emergency Sync
kernel: Emergency Sync complete
kernel: SysRq : Keyboard mode set to XLATE
kernel: SysRq : Keyboard mode set to XLATE
kernel: SysRq : Emergency Sync
kernel: Emergency Sync complete
kernel: SysRq : Emergency Sync
kernel: Emergency Sync complete
kernel: SysRq : SAK
gpm[1891]: *** info [mice.c(1766)]:
gpm[1891]: imps2: Auto-detected intellimouse PS/2
login(pam_unix)[2047]: session opened for user dan by (uid=0)
-- dan[2047]: LOGIN ON tty2 BY dan
shutdown: shutting down for system reboot
init: Switching to runlevel: 6
.....etc.....
----------------------------------------------------------------------
Comment By: Dan Furlani (danfurlani)
Date: 2005-11-21 15:54
Message:
Logged In: YES
user_id=33408
NumLock key has no effect after causing the bug, hitting
Alt-Ctrl-SysRq-R and then Alt-F1. I'm sure the magic gets
to the kernel because I can reboot using that mechanism, but
I don't think changing the keyboard mode (or whatever that
does) is enough to give me console access.
----------------------------------------------------------------------
Comment By: Dan Furlani (danfurlani)
Date: 2005-11-21 15:35
Message:
Logged In: YES
user_id=33408
Some magic works, some doesn't.
Without rdesktop running I tried Alt-Ctrl-SysRq-R in X and
that key combo did allow me to use just Alt-F1 to get to
console 1. When I switched back to X with Alt-F7 the magic
wore off, so I knew I'd need the magic key combo every time.
I rdesktop'd and made the bug happen. I hit
Alt-Ctrl-SysRq-R and then Alt-F1 and typed reboot (I had
already logged into console 1). Nothing. I didn't try
NumLock at that point but I bet it wouldn't have worked -- I
think something still had control of the keyboard. I'll try
that after I post this.
So after trying a few different ways (with/without Ctrl,
left/right modifiers, etc.) I gave up and hit
Alt-Ctrl-SysRq-B -- this rebooted immediately.
----------------------------------------------------------------------
Comment By: Ilya Konstantinov (ikonst)
Date: 2005-11-20 00:49
Message:
Logged In: YES
user_id=335423
Whoa. The way you describe it, it looks like your X server
crashed. You might be able to switch to console by using
Magic-SysRq in Linux (if Magic-SysRq is on in
/proc/sys/kernel/sysrq) by pressing Alt-Ctrl-SysRq-R.
Before we try this again, test this sequence while in the
console to make sure it works. It should print to console:
SysRq : Keyboard mode set to XLATE
Afterwards, when X crashes (but the entire system does not),
you can regain keyboard control with Alt-Ctrl-SysRq-R and
then switch to your console with Alt-F1 (not Alt-Ctrl-F1).
You might still have to do things "blind" at this point
cause following an X crash, your graphical video mode will
remain.
----------------------------------------------------------------------
Comment By: Dan Furlani (danfurlani)
Date: 2005-11-17 16:31
Message:
Logged In: YES
user_id=33408
The problem still happens with 1.4.1.
I tried the console idea:
1. Started rdesktop
2. Alt-Ctrl-F1 to console, logged in, su to root (maybe
makes kill work better?), ps aux|grep rdesk, typed "kill -9
8888" where 8888 was the rdesktop pid -- did not hit enter.
I set this up because I thought I might be trying to kill
it from the console "blind" later on.
3. Alt-F7, logged into XP, ran calc
4. Took a picture (not sure if this will help)
5. Alt-Ctrl-F1 (nothing visible happened)
6. Hit enter with intent to kill (nothing happened)
7. Typed "reboot" (nothing happened)
8. Typed "find /" to check for HD activity (nothing happened)
9. Tried switching consoles (F7, F2, F1, etc) trying to get
something to happen -- nothing.
I did notice that the hard drive light was still blinking
every 2 seconds (ext3) so I guess the whole system *isn't* dead.
I unplugged the mouse (ps2) and plugged it back in -- no
difference.
I did the same with the keyboard (ps2) -- no difference.
The LEDs did flash on/off when I plugged the keyboard back
in, which is normal.
The photo is crummy but you can see that the "F-E" key got
drawn (purple on gray is hell) and the next key below it
only got outlined but not labeled.
If the system is still up maybe I can turn on debug and log
something, but we'd have to be sure the log actually got
flushed to disk and sync'd before I reboot.
----------------------------------------------------------------------
Comment By: Ilya Konstantinov (ikonst)
Date: 2005-11-17 14:41
Message:
Logged In: YES
user_id=335423
What you describe sounds like rdesktop grabbing the mouse
and keyboard and not releasing them. At this point, you can
probably still switch to a textual console (with
Alt-Ctrl-F1) and kill rdesktop to avoid rebooting.
Of course, you should try the latest version (1.4.1) and
report if you still have the problem. I'll be setting the
bug report to be "pending for reply" -- please check it and
reply within this report.
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=381347&aid=1358691&group_id=24366
|