Bug 1085495 - gnome-shell hangs when gnome-settings-daemon crashes
Summary: gnome-shell hangs when gnome-settings-daemon crashes
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-shell
Version: 20
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Owen Taylor
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On: 1085116 1085493
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-04-08 17:55 UTC by Samuel Sieb
Modified: 2015-06-29 19:59 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2015-06-29 19:59:11 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Samuel Sieb 2014-04-08 17:55:40 UTC
gnome-settings-daemon crashes regularly on my system due to bug 1085493.  This causes gnome-shell to hit bug 1085116. I don't know if there is an actual bug in gnome-shell, but this bug will at least link the two issues.

Here is the stack trace:
Backtrace:
#0  g_hash_table_resize (hash_table=hash_table@entry=0x1e24f00) at ghash.c:554
#1  0x000000312ae3854e in g_hash_table_maybe_resize (hash_table=0x1e24f00) at ghash.c:594
#2  g_hash_table_remove_internal (hash_table=0x1e24f00, key=0x1, notify=1) at ghash.c:1277
#3  0x000000312cacb463 in do_call (client=client@entry=0x13f19c0, call_type=call_type@entry=CALL_TYPE_NAME_VANISHED) at gdbusnamewatching.c:216
#4  0x000000312cacb695 in call_vanished_handler (client=client@entry=0x13f19c0, ignore_cancelled=0) at gdbusnamewatching.c:242
#5  0x000000312cacb978 in on_name_owner_changed (connection=<optimized out>, sender_name=0x7fd3f8418200 "org.freedesktop.DBus", object_path=<optimized out>,
    interface_name=0x7fd3f8420400 "org.freedesktop.DBus", signal_name=<optimized out>, parameters=0x462ab80, user_data=0x13f19c0) at gdbusnamewatching.c:307
#6  0x000000312cabc435 in emit_signal_instance_in_idle_cb (data=0x7fd3f84292f0) at gdbusconnection.c:3743
#7  0x000000312ae492a6 in g_main_dispatch (context=0xef5880) at gmain.c:3066
#8  g_main_context_dispatch (context=context@entry=0xef5880) at gmain.c:3642
#9  0x000000312ae49628 in g_main_context_iterate (context=0xef5880, block=block@entry=1, dispatch=dispatch@entry=1, self=<optimized out>) at gmain.c:3713
#10 0x000000312ae49a3a in g_main_loop_run (loop=0xef8580) at gmain.c:3907
#11 0x0000003131e62ce8 in meta_run () at core/main.c:556
#12 0x0000000000402131 in main (argc=1, argv=0x7fff624ea5f8) at main.c:441

Comment 1 Fedora End Of Life 2015-05-29 11:30:44 UTC
This message is a reminder that Fedora 20 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 20. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '20'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 20 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 2 Fedora End Of Life 2015-06-29 19:59:11 UTC
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


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