Bug 991835 - gnome-settings-daemon-3.8.4-2.el7 crashes on starting of gnome-session
gnome-settings-daemon-3.8.4-2.el7 crashes on starting of gnome-session
Status: CLOSED CURRENTRELEASE
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: gnome-settings-daemon (Show other bugs)
7.0
Unspecified Unspecified
unspecified Severity high
: rc
: ---
Assigned To: Rui Matos
Desktop QE
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2013-08-04 16:44 EDT by Matěj Cepl
Modified: 2017-07-03 11:04 EDT (History)
4 users (show)

See Also:
Fixed In Version: gnome-settings-daemon-3.8.4-3.el6
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2014-06-13 07:05:15 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
backtrace (7.69 KB, text/plain)
2013-08-04 16:44 EDT, Matěj Cepl
no flags Details
backtrace (7.66 KB, text/plain)
2013-08-04 16:45 EDT, Matěj Cepl
no flags Details
Comment (67.76 KB, text/plain)
2013-08-22 17:01 EDT, Ray Strode [halfline]
no flags Details


External Trackers
Tracker ID Priority Status Summary Last Updated
GNOME Desktop 706620 None None None Never

  None (edit)
Description Matěj Cepl 2013-08-04 16:44:48 EDT
Created attachment 782586 [details]
backtrace

Description of problem:
Whenever I login to Gnome, I get "Whoops, something happened" screen. After analyzing journalctl (and looking at my $HOME) I found two coredumps from gnome-settings-daemon (see attached). When downgrading g-s-d to gnome-settings-daemon-3.8.4-1.el7 everything works.

Version-Release number of selected component (if applicable):
gnome-settings-daemon-3.8.4-2.el7

How reproducible:
100%

Steps to Reproduce:
1.login to Gnome
2.
3.

Actual results:
"Whoops, something happened" screen, restart of gnome-session (and everything repeats endlessly).

Expected results:
Working gnome session

Additional info:
Comment 1 Matěj Cepl 2013-08-04 16:45:45 EDT
Created attachment 782587 [details]
backtrace
Comment 3 Ray Strode [halfline] 2013-08-22 09:32:25 EDT
looking into it.
Comment 4 Ray Strode [halfline] 2013-08-22 10:15:12 EDT
can you attach your /root/anaconda-ks.cfg file and the output of rpm -qa?

can you run

 valgrind /usr/libexec/gnome-settings-daemon --replace --debug >& valgrind-and-debug.log

and then attach that?
Comment 5 Ray Strode [halfline] 2013-08-22 17:01:11 EDT
Created attachment 915751 [details]
Comment

(This comment was longer than 65,535 characters and has been moved to an attachment by Red Hat Bugzilla).
Comment 6 Ray Strode [halfline] 2013-08-22 17:42:10 EDT
hmm for some reason it's trying to load the softoken (see Activating driver 'NSS Internal Crypto Services') which doesn't have a dllName associated with it.  It shouldn't be trying to use that, so I need to figure out why it's tryin in the first place.
Comment 7 Matěj Cepl 2013-09-11 15:07:50 EDT
I don't think I should have needinfo here.
Comment 8 Bastien Nocera 2013-09-19 06:22:39 EDT
Bug in the smartcard support it seems, so reassigning to Ray.
Comment 9 Ray Strode [halfline] 2013-11-07 15:26:03 EST
fixed this a while ago.
Comment 13 Matěj Cepl 2014-03-05 08:03:21 EST
I haven't seen this for a long long time.
Comment 14 Ludek Smid 2014-06-13 07:05:15 EDT
This request was resolved in Red Hat Enterprise Linux 7.0.

Contact your manager or support representative in case you have further questions about the request.

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