Bug 969688

Created attachment 755655 [details]
File: backtrace

Created attachment 755656 [details]
File: cgroup

Created attachment 755657 [details]
File: core_backtrace

Created attachment 755658 [details]
File: dso_list

Created attachment 755659 [details]
File: environ

Created attachment 755660 [details]
File: limits

Created attachment 755661 [details]
File: maps

Created attachment 755662 [details]
File: open_fds

Created attachment 755663 [details]
File: proc_pid_status

Created attachment 755664 [details]
File: var_log_messages

Are you running this test under gdb? If so, this is expected because this program implements a SIGSEGV handler and gdb is configured to stop on this signal by default.

(gdb) info signal SIGSEGV
Signal        Stop      Print   Pass to program Description
SIGSEGV       Yes       Yes     Yes             Segmentation fault
(gdb)

If you want to run this program under gdb, please configure gdb to *not* stop at this signal so that the signal is silently passed to the signal handler:

(gdb) handle SIGSEGV nostop noprint

No, I've don't run under gdb.

I installed FC 19 Beta build and I don't see any core dumps. If a FC 19 Beta install is causing it for you (without making any other changes to system) I would guess it to be some system configuration that is not letting the signal reach its handler.

Given that this process implements a SIGSEGV handler, may I request you to provide me the necessary steps to reproduce it on my system?

I don't know how reproduce this bug.
This bug have shown in ABRT without any my moves. While system boot.
I'm on vacation, away from the computer where the error appeared.

Given that you don't have a known way to reproduce this bug and I'm not seeing it on my system with Fedora 19 Beta, I think I will not be able to do much about it unless someone else hits this as well.

So far, no leads on this :-(

Would it be possible for you to provide the core dump for this crash? I believe it is going to be small enough to attach it here.

Created attachment 833002 [details]
core file

$ gdb /usr/bin/vmtoolsd 
GNU gdb (GDB) Fedora 7.6.1-46.fc19
Copyright (C) 2013 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 "i686-redhat-linux-gnu".
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>...
Reading symbols from /usr/bin/vmtoolsd...Reading symbols from /usr/lib/debug/usr/bin/vmtoolsd.debug...done.
done.
(gdb) handle SIGSEGV nostop noprint
Signal        Stop	Print	Pass to program	Description
SIGSEGV       No	No	Yes		Segmentation fault
(gdb) run -n vmusr
Starting program: /usr/bin/vmtoolsd -n vmusr
During startup program terminated with signal SIGSEGV, Segmentation fault.
(gdb)

I think that the nvidia proprietary drivers may have something to do with this crash.  Removing the nvidia driver resolves the issue.

(In reply to Mirko Predosin from comment #19)
> I think that the nvidia proprietary drivers may have something to do with
> this crash.  Removing the nvidia driver resolves the issue.

Thanks Mirko. I'm curious to know how did you zoom in on Nvidia drivers?

*** Bug 1029704 has been marked as a duplicate of this bug. ***

I noticed that VMWare Player stopped working after installing the nvidia drivers in package xorg-x11-drv-nvidia-331.20-4.fc19.i686.  The player would exit after attempting to start a vmware session.  I am able to get VMWare Player to work again if I remove the drivers.

I'm sorry for long silent. Computer with this bug moved from me.
I can not get the information from it.

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.

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
bug.

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