Bug 143683 - It looks like gnome-vfs2 is causing troubles on a remote display
Summary: It looks like gnome-vfs2 is causing troubles on a remote display
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-vfs2 (Show other bugs)
(Show other bugs)
Version: rawhide
Hardware: All Linux
medium
medium
Target Milestone: ---
Assignee: Alexander Larsson
QA Contact:
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2004-12-24 01:30 UTC by Michal Jaegermann
Modified: 2007-11-30 22:10 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2006-09-01 14:59:40 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Michal Jaegermann 2004-12-24 01:30:09 UTC 
Description of problem:

Very recently various programs started doing that after attempts
to display on a remote X-server

$  gnome-terminal
The program 'gnome-terminal' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadImplementation (server does not implement operation)'.
  (Details: serial 658 error_code 17 request_code 155 minor_code 10)

This does not happen with all programs.  For example - mozilla,
firefox, xterm are not affected.  Also nothing like that shows
up with FC3 installation which is using gnome-vfs2-2.8.2-8.

gnome-vfs2-2.8.2-10 is a guess for two reasons.  One is that it
was recently updated and there was no such trouble a few days
ago and two - it seems that only programs which are using it show
such behaviour.

Version-Release number of selected component (if applicable):
gnome-vfs2-2.8.2-10
Comment 1 Alexander Larsson 2006-09-01 14:59:40 UTC 
gnome-vfs2 shouldn't affect X stuff at all, so I doubt this is related to it. 
Sorry for ignoring this bug so long, but I think this has been fixed by now
(haven't seen other reports), so I'm closing this.
Note You need to log in before you can comment on or make changes to this bug.