Bug 675187 - [abrt] control-center-1:2.91.6-4.fc15: Process /usr/bin/gnome-control-center was killed by signal 11 (SIGSEGV)
[abrt] control-center-1:2.91.6-4.fc15: Process /usr/bin/gnome-control-center ...
Status: CLOSED RAWHIDE
Product: Fedora
Classification: Fedora
Component: control-center (Show other bugs)
rawhide
x86_64 Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: Control Center Maintainer
Fedora Extras Quality Assurance
abrt_hash:eb19d24c523910e86689c28a5a2...
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2011-02-04 10:08 EST by David Juran
Modified: 2011-02-04 22:15 EST (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2011-02-04 22:15:37 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:


Attachments (Terms of Use)
File: backtrace (40.13 KB, text/plain)
2011-02-04 10:09 EST, David Juran
no flags Details

  None (edit)
Description David Juran 2011-02-04 10:08:58 EST
abrt version: 1.1.14
architecture: x86_64
Attached file: backtrace
cmdline: gnome-control-center --overview
comment: Testing with the Gnome3 test day livecd I noticed that gnome-control center crashes as soon as one tries to change the display settings
component: control-center
executable: /usr/bin/gnome-control-center
kernel: 2.6.38-0.rc3.git0.1.fc15.x86_64
package: control-center-1:2.91.6-4.fc15
reason: Process /usr/bin/gnome-control-center was killed by signal 11 (SIGSEGV)
release: Fedora release 15 (Rawhide)
time: 1296846264
uid: 500

How to reproduce
-----
1.  start the displays application
2.  ucheck  "mirror displays" and set up resoltions as neede
3. Apply
4. watch abrtd report that gnome-control-center crashed

Do note that the display does get set correctly.
Comment 1 David Juran 2011-02-04 10:09:01 EST
Created attachment 477037 [details]
File: backtrace
Comment 2 Bastien Nocera 2011-02-04 22:15:37 EST
Should be fixed in gnome-desktop3 2.91.6-2

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