i too have been having issues with diablo and rdesktop. i tried truejournals version, and get same results - no screen.
but, i tried running from an xterm and here's what i get (does this help?):
BusyBox v1.6.1 (2008-05-22 10:32:35 EEST) Built-in shell (ash)
Enter 'help' for a list of built-in commands.
~ $ rdesktop
Autoselected keyboard map en-us
rdesktop[5161]: GLIB WARNING ** Gtk - gtk_widget_size_allocate(): attempt to allocate widget with width -24 and height 0
rdesktop[5161]: GLIB WARNING ** GLib-GObject - IA__g_object_set_valist: object class `GtkEntry' has no property named `autocap'
rdesktop[5161]: GLIB WARNING ** GLib-GObject - IA__g_object_set_valist: object class `GtkEntry' has no property named `autocap'
rdesktop[5161]: GLIB WARNING ** GLib-GObject - IA__g_object_set_valist: object class `GtkEntry' has no property named `autocap'
rdesktop[5161]: GLIB WARNING ** GLib-GObject - IA__g_object_set_valist: object class `GtkEntry' has no property named `autocap'
The program 'rdesktop' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadWindow (invalid Window parameter)'.
(Details: serial 19 error_code 3 request_code 12 minor_code 0)
(Note to programmers: normally, X errors are reported asynchronously;
that is, you will receive the error a while after causing it.
To debug your program, run it with the --sync command line
option to change this behavior. You can then get a meaningful
backtrace from your debugger if you break on the gdk_x_error() function.)
~ $
Yeah, this is the error I've noticed. My guess is that sometimes, the connection happens too fast, and rdesktop tries to update the window that shows the remote desktop before it's created. I don't know any C, though, so I have no idea if this is the actual cause, or how to fix it...
Hi, I tried the normal 0.4 version and it would not even open. So I tried true journal's version and after I hit ok it crashes. I'm running the newest version of diablo. Please help.
Try it on a LAN where there is low latency, then try it a few times. It should work then. Try to only fill in the IP address of the host, and nothing else (no username/password) this gave me more success than filling out everything in the config screen.
