vinagre crash with "BadRequest (invalid request code or no such operation)" when I try to connect to VNC server

Bug #287542 reported by liquidator87 on 2008-10-22
50
This bug affects 6 people
Affects Status Importance Assigned to Milestone
gtk-vnc (Ubuntu)
High
Unassigned

Bug Description

Binary package hint: vinagre

As the title says...

The program crashes with "BadRequest (invalid request code or no such operation)" when trying to connect to a VNC server... the same servers works good with other VNC clients

OS is Intrepid
Package version 2.24.0-0ubuntu1

kiko (buty12) wrote :

Same problem. I have updated from Hardy.

Emilio Pozuelo Monfort (pochu) wrote :

With what servers have you tried this? Does it happen with all of them?

Can you please get a backtrace?

https://wiki.ubuntu.com/Backtrace

Changed in vinagre:
importance: Undecided → High
kiko (buty12) wrote :
Download full text (7.5 KiB)

gdb vinagre 2>&1 | tee gdb-vinagre.txt
GNU gdb 6.8-debian
Copyright (C) 2008 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "i486-linux-gnu"...
(no debugging symbols found)
(gdb) handle SIG33 pass nostop noprint
Signal Stop Print Pass to program Description
SIG33 No No Yes Real-time event 33
(gdb) set pagination 0
(gdb) run vinagre
Starting program: /usr/bin/vinagre vinagre
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[New Thread 0xb6e00710 (LWP 31293)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols fo...

Read more...

kiko (buty12) wrote :

I' ve solved it. I have moved .gconf folder to gconf-old and now works fine. It isn't the best solution beacuse I have loosed gnome configuration. Regards,

kiko (buty12) wrote :

Lost, not loosed, sorry

Jools Wills (jools) wrote :

I am also getting this bug. the "fix" by starting a new config folder made no difference.

Changed in vinagre:
status: New → Confirmed
macro182 (macro182-gmail) wrote :

Ubuntu updated to Intrepid: Vinagre crashes all the times.

~$ vinagre
The program 'vinagre' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadRequest (invalid request code or no such operation)'.
  (Details: serial 1276 error_code 1 request_code 143 minor_code 19)
  (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.)

Matt Hulse (matt-hulse) wrote :

I am getting this same crash on Intrepid. It was working fine and then all of the sudden everytime I connect, the app just closes. If I run vinagre from the command line I get exactly the same output as macro182. I don't remember upgrading anything that would have broken this. It was working with a clean install of Intrepid so I assume it was an update that broke it. Very annoying. Now I'm stuck using xvnc4viewer so no saved sessions and handy interface. Please give me my vinagre back! :(

macro182 (macro182-gmail) wrote :

Try with:

sudo aptitude reinstall vinagre

or

sudo aptitude remove vinagre

Matt Hulse (matt-hulse) wrote :

Thanks for the suggestions but neither one did anything for me. I even tried purging and reinstalling. My bookmarks were still intact after all of that so I'm not completely confident that all the configuration files were purged. Any other ideas?

 I am on vinagre 2.24.1-0ubuntu1 in Intrepid.

mhulse@mhulse-laptop:~$ vinagre 192.168.241.9
The program 'vinagre' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadRequest (invalid request code or no such operation)'.
  (Details: serial 349 error_code 1 request_code 158 minor_code 19)
  (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.)

Emilio Pozuelo Monfort (pochu) wrote :

(to everyone affected) With what servers have you tried this? Does it happen with all of them?

Emilio Pozuelo Monfort (pochu) wrote :

BTW, from the backtrace in comment 3:

The program 'vinagre' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadRequest (invalid request code or no such operation)'.
  (Details: serial 353 error_code 1 request_code 143 minor_code 19)
  (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.)

Program exited with code 01.
(gdb)

Emilio Pozuelo Monfort (pochu) wrote :

Jonh: is this a vinagre bug or a libgtk-vnc bug?

>Details: serial 353 error_code 1 request_code 143 minor_code 19)

Matt Hulse (matt-hulse) wrote :

>(to everyone affected) With what servers have you tried this? Does it happen with all of them?

Before this started happening, I used vinagre to connect to around 10 different windows boxes running ultravnc server. I now get this error when trying to connect to any of them. It doesn't seem to matter what address I pass in. I get the same error if I pass in garbage as a parameter. I'm still able to connect to all of these servers using other vnc clients in ubuntu.

Avery (docaltmed) wrote :

Have tried this on two different servers. I have the same response as others have reported. Servers are readily available to other vnc clients.

Avery (docaltmed) wrote :

I don't know if this helps, but I get the same "BadRequest" message when I try to run gvncviewer.

Nelson Elhage (nelhage) wrote :

I get the same failure with all three of vinagre, gvncviewer, and gtkvncviewer, so I suspect this is a libgtk-vnc bug.

`aptititude reinstall libgtk-vnc-1.0-0` doesn't help.

I'm trying to run it under gdb to break on gdk_x_error, but I can't find that symbol either in in vinagre (rebuilt with debug symbols) or in any library in /usr/lib/ (and just asking gdb to put a breakpoint there doesn't work, either).

Emilio Pozuelo Monfort (pochu) wrote :

Thanks Nelson for your research. Reassigning to gtk-vnc as this happens with 3 different clients all using the gtk-vnc library.

Nelson Elhage (nelhage) wrote :

Fascinating. There's something weirder going on here, and it may
actually be the X server's fault.

So, vinagre was working fine for me, and then I rebooted into
"recovery mode" and selected "fix X server" (even though my X server
was working fine; I was testing something else…), and it was after
doing that that vinagre stopped working, even though I didn't make the
connection at the time. This occurred to me yesterday when another
program, mupen64plus (not in Ubuntu --
http://code.google.com/p/mupen64plus/) crashed with the exact same X
error.)

When that happened, I got suspicious and swapped in the X config from
before the "fix X server" (automatically backed up in /etc/X11/), and
now all three VNC viewers, as well as mupen64plus, work fine. I'm
attaching both X configs in the hope that someone else can figure
something out.

- Nelson

Emilio Pozuelo Monfort (pochu) wrote :

To everybody affected:

What video driver and hardware do you have?

What's the output of running "xrandr -q" ?

Thanks

Nelson Elhage (nelhage) wrote :

Graphics hardware:
01:00.0 VGA compatible controller: ATI Technologies Inc M52 [Mobility Radeon X1300]

My working configuration is using the fglrx driver. I didn't get information from the non-working configuration; I don't want to restart my X server at the moment, but if it'd be useful I can restart into the old configuration and collect data for you at some point.

Matt Hulse (matt-hulse) wrote :

I can't enable the FGLRX proprietary driver for some reason but the default driver with Intrepid is working fine for me. I have had problems and I've gone back and forth a few times experimenting with different options. My xorg.conf is very basic at this point. I just backed up the xorg.conf and restarted and it gave me a basic working xorg.conf.

Here is the other info requested:

mhulse@mhulse-laptop:~$ lspci | grep ATI
01:00.0 VGA compatible controller: ATI Technologies Inc M24 1P [Radeon Mobility X600]

mhulse@mhulse-laptop:~$ xrandr -q
Screen 0: minimum 320 x 200, current 3120 x 1050, maximum 3120 x 1442
VGA-0 connected 1440x900+0+0 (normal left inverted right x axis y axis) 410mm x 257mm
   1440x900 59.9*+ 75.0 59.9* 60.0
   1600x1024 60.2
   1400x1050 60.0
   1280x1024 75.0 60.0 60.0
   1280x960 60.0 60.0
   1360x768 59.8
   1152x864 75.0 75.0 75.0 70.0 60.0
   1024x768 75.1 75.0 70.1 60.0
   832x624 74.6
   800x600 72.2 75.0 60.3 56.2
   640x480 75.0 72.8 72.8 75.0 66.7 60.0 59.9
   720x400 70.1
   256x144 60.0
LVDS connected 1680x1050+1440+0 (normal left inverted right x axis y axis) 0mm x 0mm
   1680x1050 60.1*+
   1600x1024 60.2
   1280x1024 60.0
   1440x900 59.9
   1280x960 60.0
   1360x768 59.8
   1152x864 60.0
   1024x768 60.0
   800x600 60.3
   640x480 59.9
S-video disconnected (normal left inverted right x axis y axis)

Pavel Kaplin (pavel-kaplin) wrote :

Screen 0: minimum 320 x 200, current 1280 x 1024, maximum 1680 x 1200
VGA-0 connected 1280x1024+0+0 (normal left inverted right x axis y axis) 352mm x 264mm
   1280x1024 85.0*+ 85.0 85.0* 75.0 60.0
   1600x1200 85.0 75.0 75.0 70.0 65.0 60.0
   1680x1050 84.9 74.9 69.9 60.0
   1600x1024 60.2
   1400x1050 85.0 74.8 70.0 60.0
   1440x900 59.9
   1280x960 85.0 60.0
   1360x768 59.8
   1152x864 100.0 85.1 85.0 75.0 75.0 70.0 60.0
   1024x768 85.0 85.0 75.1 75.0 70.1 60.0 43.5
   832x624 74.6
   800x600 85.0 85.1 72.2 75.0 60.3 56.2
   640x480 85.0 85.0 75.0 72.8 72.8 75.0 66.7 60.0 59.9
   720x400 87.8 85.0 70.1
   640x400 85.1
   640x350 85.1
DVI-0 disconnected (normal left inverted right x axis y axis)
S-video disconnected (normal left inverted right x axis y axis)

Matt Hulse (matt-hulse) wrote :

I'm not sure what has changed but this is now working for me. I checked xrandr -q output and it is identical to my last post. Looking in recent updates in Synaptic I do see xserver-xorg-video-intel. Not sure if it's related. At any rate, it seems to be working fine now.

Emilio Pozuelo Monfort (pochu) wrote :

Anybody running Jaunty can confirm if this is still an issue with gtk-vnc 0.3.8?

macro182 (macro182-gmail) wrote :

Now I've this old problem with vinagre.
The first time I've resolved it just reinstalling package 'vinagre', now this trick doesn't work.

In these days I've upgrade my catalyst to 9.11, but Vinagre doesn't work even if I downgrade my video-card's driver.

Is there any work-around?

---------------------------
xrandr -q
Screen 0: minimum 320 x 200, current 1280 x 800, maximum 1280 x 800
default connected 1280x800+0+0 0mm x 0mm
   1280x800 60.0*
   1280x768 60.0
   1024x768 60.0
   1024x480 60.0
   848x480 60.0
   800x600 60.0
   720x576 60.0
   720x480 60.0
   640x480 60.0
   640x400 60.0
   512x384 60.0
   400x300 60.0
   320x240 60.0
   320x200 60.0

--------------------------------
lspci | grep ATI
01:00.0 VGA compatible controller: ATI Technologies Inc Radeon Mobility X700 (PCIE)

macro182 (macro182-gmail) wrote :

I've resolved uninstalling fglrx...

sudo sh /usr/share/ati/fglrx-uninstall.sh

then,

sudo apt-get install xserver-xorg-video-ati

rebooting my laptot Vinagre restart to work, and video in fullscreen doesn't jerk!

;)

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Duplicates of this bug

Other bug subscribers