After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 314940 - best crashes on entering a running VMware session
best crashes on entering a running VMware session
Status: RESOLVED NOTGNOME
Product: beagle
Classification: Other
Component: General
0.0.x
Other All
: High critical
: ---
Assigned To: Beagle Bugs
Beagle Bugs
Depends on:
Blocks:
 
 
Reported: 2005-08-31 10:48 UTC by Holger Leskien
Modified: 2005-09-03 17:16 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Holger Leskien 2005-08-31 10:48:37 UTC 
Steps to reproduce:
1. start best (icon shows up in the notification area)
2. start VMware
3. start a VM session
4. switch session to fullscreen (ctrl-alt-enter) or enter by clicking into it

Stack trace:
tried to generate a backtrace...

Other information:
error message:

The program 'best' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadValue (integer parameter out of range for operation)'.
  (Details: serial 537 error_code 2 request_code 34 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.)
Comment 1 Jon Trowbridge 2005-08-31 19:54:02 UTC 
This is almost certainly not a beagle bug --- it probably has something to do
with X or Gtk.  Or maybe VMWare.  I'm going to close it as NOTGNOME, but please
re-open it if you have further information suggesting that it is
beagle-specific.  Thanks.
Comment 2 Holger Leskien 2005-09-03 17:16:14 UTC 
beagle CVS 2005-09-01 is not affected anymore