Bug 675928 - [abrt] gnome-settings-daemon-2.91.9-1.fc15: screen_info_free: Process /usr/libexec/gnome-settings-daemon was killed by signal 6 (SIGABRT)
Summary: [abrt] gnome-settings-daemon-2.91.9-1.fc15: screen_info_free: Process /usr/li...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-settings-daemon
Version: rawhide
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Bastien Nocera
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:0f460fa0ad479648735dc6939bd...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-02-08 09:59 UTC by Stefan Lehmann
Modified: 2012-06-14 21:08 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-06-14 21:08:04 UTC
Type: ---

Attachments (Terms of Use)
File: backtrace (21.82 KB, text/plain)
2011-02-08 09:59 UTC, Stefan Lehmann 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Description Stefan Lehmann 2011-02-08 09:59:15 UTC 
abrt version: 1.1.17
architecture: x86_64
Attached file: backtrace, 22342 bytes
cmdline: /usr/libexec/gnome-settings-daemon
component: gnome-settings-daemon
Attached file: coredump, 35545088 bytes
crash_function: screen_info_free
executable: /usr/libexec/gnome-settings-daemon
kernel: 2.6.38-0.rc3.git4.1.fc15.x86_64
package: gnome-settings-daemon-2.91.9-1.fc15
rating: 4
reason: Process /usr/libexec/gnome-settings-daemon was killed by signal 6 (SIGABRT)
release: Fedora release 15 (Rawhide)
time: 1297158588
uid: 500

comment
-----
nxnode-3.4.0-11.x86_64
nxserver-3.4.0-14.x86_64
nxclient-3.4.0-7.x86_64

How to reproduce
-----
1. started gnome session via nomachine nx
2.
3.
Comment 1 Stefan Lehmann 2011-02-08 09:59:18 UTC 
Created attachment 477586 [details]
File: backtrace
Comment 2 Bastien Nocera 2011-03-15 12:02:42 UTC 
This should have been fixed in more recent versions of gnome-desktop3. Please test and let us know whether the same problem still occurs.
Comment 3 Matthias Clasen 2012-06-14 21:08:04 UTC 
More than a year later, lets assume it is fixed.
Note You need to log in before you can comment on or make changes to this bug.