Learn how easy it is to sync an existing GitHub or Google Code repo to a SourceForge project! See Demo

Close

#171 Rdesktop client causes whole system to freeze

open
None
5
2005-12-04
2005-11-17
Dan Furlani
No

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.

Discussion

    • status: open --> pending
     
  • 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.

     
  • Dan Furlani
    Dan Furlani
    2005-11-17

    • status: pending --> open
     
  • Dan Furlani
    Dan Furlani
    2005-11-17

    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.

     
  • Dan Furlani
    Dan Furlani
    2005-11-17

    Picture of calc.exe drawing halfway over rdesktop

     
    Attachments
  • 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.

     
  • Dan Furlani
    Dan Furlani
    2005-11-21

    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.

     
  • Dan Furlani
    Dan Furlani
    2005-11-21

    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.

     
  • Dan Furlani
    Dan Furlani
    2005-11-25

    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.....

     
  • Dan Furlani
    Dan Furlani
    2005-11-26

    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.

     
    • assigned_to: nobody --> ikonst
     
  • 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.

     
  • Logged In: NO

    I'm bit late to the party, but similar thing is happening to
    me - connecting from FBSD (+X+Gnome) to W2k3 server, the
    session sometimes hangs in that users can't click anything.
    I have a temporary fix for this - our users have set
    CTRL+ALT+DEL shortcut to lock the session(monitor) as they
    were used in Windows. Hitting ctrl+alt+del while the rdp
    session is hanging (ie. can't click anything, but see the
    mouse pointer moving around) works - it locks the screen,
    then logging back fixes the problem and they can work again.
    Any chance this will be fixed in future versions of rdesktop?

     
  • Rajan
    Rajan
    2006-07-10

    Logged In: YES
    user_id=1190349

    I am able to reproduce this consistently after leaving the
    machine idle for about 15 minutes while a remote desktop
    session is open (i.e the currently focused window). When I
    come back, I see that the remote desktop window is blank,
    once I move the mouse it refreshes the display. After that
    my keyboard and mouse are not responding. The only
    workaround I found was to switch to tty1 (using Ctrl + Alt +
    1) and restarting gdm (gnome). Please let me know if you
    need more information.

    I use Ubuntu Dapper 6.06 LTS gnome rdesktop version 1.4.1.
    Intel 915 graphics card. I suspect that this has to do with
    Xscreensaver.

     
  • Logged In: NO

    I can force this happening with the screensaver. I set the
    screensaver activation time to 1 minute, and after that, all
    I can do is move the mouse around.

    This may be of some help if you don't want to lose any
    unsaved data: When i clicked on another workspace in the
    workspace-switcher, and waited for the screensaver to start
    again, the problem was gone.

    I use Ubuntu 6.06 LTS AMD 64 with rdesktop 1.4.1
    I alse had the "lock screen when screensaver is active"
    option enabled.

    Now I have turned off the scrensaver.

     
  • Logged In: NO

    I can force this happening with the screensaver. I set the
    screensaver activation time to 1 minute, and after that, all
    I can do is move the mouse around.

    This may be of some help if you don't want to lose any
    unsaved data: When i clicked on another workspace in the
    workspace-switcher, and waited for the screensaver to start
    again, the problem was gone.

    I use Ubuntu 6.06 LTS AMD 64 with rdesktop 1.4.1
    I alse had the "lock screen when screensaver is active"
    option enabled.

    Now I have turned off the scrensaver.

     
  • bparnell
    bparnell
    2006-10-13

    Logged In: YES
    user_id=1110189

    Hi there,

    Hate to say this but the problem is still happening!

    Description of problem:
    When using rdesktop, everything works fine! I have
    gnome-screensaver configured to lock the screen after x
    minutes of inactivity. If the rdesktop session is in focus
    and gnome-screensaver activates and deactivates (more
    commonly because the mouse is moved) the click events of the
    mouse are now not recognised by any application. The only
    way to deal with it is to restart gnome. The mouse cursor
    moves around as you would expect.

    Software versions:
    Ubuntu Linux - 6.06 LTS (Dapper Drake)
    rdesktop - 1.4.1-1.1
    tsclient - 0.140-3ubuntu1
    gnome-screensaver - 2.14.3-0ubuntu1

    There is nothing in the log files to state that there was a
    problem.

    Best Regards,
    Bill.

     
  • jared jennings
    jared jennings
    2006-10-16

    Logged In: YES
    user_id=249160

    Possible workaround: Try hitting Alt-F2 to pop up GNOME's
    Run dialog (or use another means of running things if you're
    not in GNOME), and typing "xscreensaver-command
    -deactivate", or "xscreensaver-command -exit". I bet it'll
    unfreeze the mouse. We have this all the time in my office.

    It also might work to just hit Ctrl-Alt-F1 (switch to a text
    VC) and Ctrl-Alt-F7 (switch back to X): you probably don't
    have to actually kill X.

    Somebody else was talking about this in another bug but I
    can't remember which. I guess you can search by my name

     
  • Kevin DeKorte
    Kevin DeKorte
    2006-10-16

    Logged In: YES
    user_id=685413

    today, I had to kill gnome-screensaver to get my buttons
    back. I could move the cursor but could not click on
    anything. After I came back to machine where the screensaver
    had kicked in. So I moved the mouse, typed in my password
    and then could not click on anything. Killed
    gnome-screensaver and then everything started working again.
    So when the screen saver is kicking in rdesktop is not
    properly releasing the mouse input.

     
  • NeoMatrixJR
    NeoMatrixJR
    2006-12-05

    Logged In: YES
    user_id=1661433
    Originator: NO

    Ubuntu 6.10
    rdesktop 1.5.0

    I have the same problem, but I don't believe an app or screen saver is causing mine. If my rdesktop session looses connection to the host computer it will freeze and within a few seconds GNOME will also lockup. I can move the mouse, and many menus and buttons will still have their rollover effects, but I can't click anything or type at all until I do a CTRL-ALT-BKSP and restart the X session. Any ways to prevent this? I'm often working over the cisco VPN client, however this is not always the case and it has locked up with or without it.

     
  • Nickleus
    Nickleus
    2007-03-01

    Logged In: YES
    user_id=1365643
    Originator: NO

    i'm running ubuntu 6.06 LTS, with kernel 2.6.15-28-386 and rdesktop 1.5.0.

    i logged into a winxp machine and ran calc and the whole system froze. keyboard and mouse input were not read, i couldn't do anything but reboot. what could be the problem?