Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 228207 - gvim spews lots of errors to terminal
gvim spews lots of errors to terminal
Status: CLOSED DUPLICATE of bug 217128
Product: Fedora
Classification: Fedora
Component: vim (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Karsten Hopp
David Lawrence
Depends On:
  Show dependency treegraph
Reported: 2007-02-11 11:21 EST by Josh Boyer
Modified: 2007-11-30 17:11 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2007-02-12 09:42:46 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Josh Boyer 2007-02-11 11:21:45 EST
Description of problem:

When starting a gvim instance from a terminal, I see output like the below:

[jwboyer@vader ubi-utils]$ gvim src/libubi.c 
GTK Accessibility Module initialized
[jwboyer@vader ubi-utils]$ 
** (gvim:21601): WARNING **: failure: no device event controller found.

** (gvim:21601): WARNING **: failure: no device event controller found.

** (gvim:21601): WARNING **: failure: no device event controller found.

Version-Release number of selected component (if applicable):

[jwboyer@vader ubi-utils]$ rpm -q vim-X11

How reproducible:


Steps to Reproduce:
1. Open a file in gvim
2. Hit pg down or perform some other kind of event
3. Look at terminal gvim was started from
Actual results:

Errors and warings spewed to terminal

Expected results:

Nothing in terminal window

Additional info:

All operations inside of gvim seem to function just fine.  It's highly annoying
to see these warning messages spewed out though.
Comment 1 Karsten Hopp 2007-02-12 09:42:46 EST

*** This bug has been marked as a duplicate of 217128 ***

Note You need to log in before you can comment on or make changes to this bug.