Bug 691307 - [abrt] gnome-settings-daemon-2.28.2-11.el6: g_logv: Process /usr/libexec/gnome-settings-daemon was killed by signal 6 (SIGABRT)
Summary: [abrt] gnome-settings-daemon-2.28.2-11.el6: g_logv: Process /usr/libexec/gnom...
Keywords:
Status: CLOSED DUPLICATE of bug 657726
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: gnome-settings-daemon
Version: 6.0
Hardware: x86_64
OS: Unspecified
low
medium
Target Milestone: rc
: ---
Assignee: Bastien Nocera
QA Contact: desktop-bugs@redhat.com
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-03-28 07:00 UTC by prashant ingale
Modified: 2013-03-01 05:08 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-06-02 10:59:52 UTC
Target Upstream Version:

Attachments (Terms of Use)
backtrace (3.93 KB, application/octet-stream)
2011-03-28 07:00 UTC, prashant ingale 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Description prashant ingale 2011-03-28 07:00:41 UTC 
Created attachment 488087 [details]
backtrace

Description of problem:
 
Login via NX terminal server (freenx) which calls "gnome-session".
After GNOME desktop appears, immediately a popup in the notification area appears telling that gnome settings daemon has crashed
reason: Process /usr/libexec/gnome-settings-daemon was killed by signal 6 (SIGABRT)
cmdline: /usr/libexec/gnome-settings-daemon

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

architecture: x86_64
package: gnome-settings-daemon-2.28.2-11.el6
release: Red Hat Enterprise Linux Server release 6.0 (Santiago)


Steps to Reproduce:

1.Login via NX terminal server (freenx) which calls "gnome-session". 
2.After GNOME desktop appears, immediately a popup in the notification area appears telling that gnome settings daemon has crashed
3.
  
Actual results:

gnome-setting-daemon crashed.

Expected results:

gnome-setting-daemon should not crashed



Additional info:
Comment 3 ritz 2011-06-02 10:59:52 UTC 

*** This bug has been marked as a duplicate of bug 657726 ***
Note You need to log in before you can comment on or make changes to this bug.