Bug 587111 - xorg-x11-drv-vmmouse collects segfaults
Summary: xorg-x11-drv-vmmouse collects segfaults
Alias: None
Product: Fedora
Classification: Fedora
Component: xorg-x11-drv-vmmouse
Version: 19
Hardware: x86_64
OS: Linux
Target Milestone: ---
Assignee: X/OpenGL Maintenance List
QA Contact: Fedora Extras Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2010-04-28 23:08 UTC by Michal Jaegermann
Modified: 2015-02-17 13:17 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2015-02-17 13:17:04 UTC
Type: ---

Attachments (Terms of Use)
results of poking with gdb at one of cores (2.57 KB, text/plain)
2010-04-28 23:09 UTC, Michal Jaegermann
no flags Details

Description Michal Jaegermann 2010-04-28 23:08:39 UTC
Description of problem:

I found recent core files in /.  A closer look revealed that all of them come from /usr/bin/vmmouse_detect. No idea what was running that and why. With a debuginfo package installed gdb seems to indicate that VMMouseProtoInOut
tries to dereference a null pointer (although that should cause a segfault
earlier).  See attached.

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

How reproducible:
I collected a few similar cores.

Additional info:
Running /usr/bin/vmmouse_detect in a shell simply returns with a status 1.
As this is a "leaf" package, and apparently not really used for anything on my test installation, the simplest way for me "to fix" that would be just to deinstall it.

Comment 1 Michal Jaegermann 2010-04-28 23:09:41 UTC
Created attachment 409983 [details]
results of poking with gdb at one of cores

Comment 2 Michel Dänzer 2010-06-18 15:54:14 UTC
Duplicate of bug 604660.

Comment 3 Bug Zapper 2010-07-30 11:30:21 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 14 development cycle.
Changing version to '14'.

More information and reason for this action is here:

Comment 4 Fedora End Of Life 2013-04-03 19:10:00 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 19 development cycle.
Changing version to '19'.

(As we did not run this process for some time, it could affect also pre-Fedora 19 development
cycle bugs. We are very sorry. It will help us with cleanup during Fedora 19 End Of Life. Thank you.)

More information and reason for this action is here:

Comment 5 Fedora End Of Life 2015-01-09 16:15:46 UTC
This message is a notice that Fedora 19 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 19. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained. Approximately 4 (four) weeks from now this bug will
be closed as EOL if it remains open with a Fedora 'version' of '19'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 19 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 6 Fedora End Of Life 2015-02-17 13:17:04 UTC
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this

Thank you for reporting this bug and we are sorry it could not be fixed.

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