Yes, that's what I thought at first. But then I noticed three things:
1) Gnome, KDE, xfce4 all run fine from the console. It's only when over vnc (started by user) 2) Gnome and xfce4 both show almost the exact same error (different apps, same error) in the vnc session log file. KDE seems to work alright, but then I get the same error when I run apps. The error I'm mentioning is " 'BadMatch (invalid parameter attributes)'. (Details: serial ### error_code 8 request_code 72 minor_code 0) " 3) Everything works fine if I start it as root instead of the user. That is, if root does: "/etc/init.d/vncserver start" then things work fine. Note that I am not starting an Xvnc session for root, the init.d script starts Xvnc sessions for all users spec'd in /etc/sysconfig/vncservers Since I have a workaround, this is not critical, just an irritant. Users should be able to start their own Xvnc session from the command line w/o root having to intervene. This has to be some settings or security quirk new to FC5, as I've not had this problem on FC4, ubuntu 6, RH7*, CentOS4, or any other *nix I've used. I don't think it's a "vnc" problem as vnc is obviously working. Please consider this an FYI rather than a complaint, but if anyone has any suggestions, I would be all ears. thanx, -charlie redditt On 10/2/06, James Weatherall <[EMAIL PROTECTED]> wrote:
Hi Charles, The error messages: --- SESSION_MANAGER=local/km400mlv:/tmp/.ICE-unix/2651 The program 'gnome_segv2' received an X Window System error. This probably reflects a bug in the program. The error was 'BadMatch (invalid parameter attributes)'. (Details: serial 466 error_code 8 request_code 72 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.) Window manager warning: Log level 32: could not find XKB extension. --- All appear to relate to your session-manager, and not to VNC. You may want to contact the maintainers of the session-manager for support. Regards, Wez @ RealVNC Ltd. > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Charles Redditt > Sent: 02 October 2006 03:29 > To: [email protected] > Subject: vnc not working with Fedora Core 5 > > Note: I've figured out the solution, see below. > But I thought I'd share this with the vnc mail list in case anyone > else had similar trouble with Fedora Core 5. Evidently one can no > longer run the vncserver command as a regular user. I can only get it > to work as root. > > (see post at > http://www.fedoraforum.org/forum/showthread.php?p=618166) > > I am having trouble getting vnc to work on Fedora Core 5. > Contents of my vnc log file: > > Sun Oct 1 17:33:25 2006 > vncext: VNC extension running! > > vncext: Listening for VNC connections on port 5904 > vncext: created VNC server for screen 0 > SESSION_MANAGER=local/km400mlv:/tmp/.ICE-unix/2651 > The program 'gnome_segv2' received an X Window System error. > > This probably reflects a bug in the program. > The error was 'BadMatch (invalid parameter attributes)'. > (Details: serial 466 error_code 8 request_code 72 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.) > > Window manager warning: Log level 32: could not find XKB extension. > > This is on two different new installs of FC5, one on an ECS k7som+5c > 1Ghz duron, 384MB 100Mhz SDRAM (kernel 2.6.15-1.2054_FC5), the other > on a DFI KM400MLV 1800Ghz Athlon XP (Barton) with 512 MB 333DDR > (kernel 2.6.17-1.2187_FC5) > > I've had this problem from the start. vnc has never worked for me > on FC5 (vnc works fine for me on FC4). I first tried vnc with xfce > instead of gnome or kde. Whatever the case, nothing works completely > (gnome or xfce are useless, kde and fluxbox work but apps fail). > > I also get this error when I use the vncserver command to start the > Xvnc server: > > > xauth: (stdin):1: bad display name "km400mlv:4" in "add" command > If I try xfce (using "startxfce4" in my .vnc/xstartup ) I get this > in the log file: > > > (xfce-mcs-manager:2845): libxfce4mcs-CRITICAL **: > mcs_manager_add_channel_from_file: > assertion `filename != NULL && strlen (filename) > 0' failed > The program 'xfce4-session' received an X Window System error. > This probably reflects a bug in the program. > The error was 'BadMatch (invalid parameter attributes)'. > (Details: serial 1831 error_code 8 request_code 72 minor_code 0) > > I've tried turning off the firewall and SELinux, but nothing seems to > have any effect. > > The fluxbox and KDE sorta work, but a lot of X11 apps mysteriously > fail (like firefox (exit code 139), or system-config-* scripts) > > Funny thing is, say I run KDE over vnc, and in a console do: > > [EMAIL PROTECTED] ~]$ system-config-services > The program 'system-config-services' received an X Window > System error. > > This probably reflects a bug in the program. > The error was 'BadMatch (invalid parameter attributes)'. > (Details: serial 939 error_code 8 request_code 72 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.) > > [EMAIL PROTECTED] ~]$ firefox > [EMAIL PROTECTED] ~]$ echo $? > 139 > > Again, this is almost exactly the same as what I'm seeing with Gnome > or xfce in my vnclog file, but using KDE I'm just getting this error > for applications, not for the desktop itself (and the firefox exit > code of 139 is the same as I get when I try running it under fluxbox). > > To be clear, KDE, Gnome, Xfce all run fine on the console. My > troubles are just with VNC. > > Note I have fixed this: > solution: > as root, do the following two things : > 1) edit /etc/sysconfig/vncservers > specify vncserver parameters for each vncserver that you want > to start (at boot) > > 2) run /etc/init.d/vncserver start > > voila, you're in business > > (And then run system-config-services and make sure vncserver is > checked to run at boot so you don't have to do the above every time) > > a quick scan of /etc/init.d/vncserver just shows that it runs > vncserver for the users specified with the parameters specified, so I > don't know what the difference is between that and the user just > running vncserver on the command line. But obviously there is > something special that is done by the init.d script. > > I'm able to run vncserver from the commandline as the user in FC4, > ubuntu 6.06, debian, CentOS4, etc. First time I've had this particular > issue. > > I found this post to give me the clue: > http://www.realvnc.com/pipermail/vn...ber/052743.html > _______________________________________________ > VNC-List mailing list > [email protected] > To remove yourself from the list visit: > http://www.realvnc.com/mailman/listinfo/vnc-list
_______________________________________________ VNC-List mailing list [email protected] To remove yourself from the list visit: http://www.realvnc.com/mailman/listinfo/vnc-list
