Auto Bug reporting tool in KDE-4.7

Kevin Kofler kevin.kofler at chello.at
Mon Jan 30 23:54:08 UTC 2012


Kaushik Guha wrote:
> *google-chrome-stable  Process /opt/google/chrome/chrome was killed by
> signal 11(SIGSEGV) 2012-01-29 22:25
> 
> The installed google-chrome  *is of version * 16.0.912.77

We do not support Google Chrome, a proprietary application not shipped by 
Fedora. This also has nothing to do with KDE.

> This type of message also occurs while I run "vlc" mediaplayer  *which is
> of version *1.1.13* The Luggage

We do not officially support VLC either, as it's in RPM Fusion, not in 
Fedora itself. This also has very little to do with KDE, unless your issue 
is a Qt bug.

In addition, we cannot possibly help you without at least a stack backtrace 
of each crash. What you told us is basically just that it crashed (with a 
segmentation fault, but that's the most common cause of a crash and doesn't 
say anything specific either).

Now if you happen to use the proprietary NVidia driver, you may be seeing:
https://bugzilla.redhat.com/show_bug.cgi?id=751891
a known issue, for which the only known workaround is to use Nouveau instead 
(something I'd recommend to all owners of NVidia graphics hardware anyway). 
But that's just a wild guess (it's the most common segmentation fault crash 
hitting more than one application reported against Fedora 16); without a 
backtrace, I cannot know more.

        Kevin Kofler



More information about the kde mailing list