| Summary: | [abrt] gnome-shell-3.2.1-2.fc16: Process /usr/bin/gnome-shell was killed by signal 6 (SIGABRT) | ||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Gleb Sharkunov <nocountryman> | ||||||||||||||
| Component: | gnome-shell | Assignee: | Owen Taylor <otaylor> | ||||||||||||||
| Status: | CLOSED DUPLICATE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||||||||
| Severity: | unspecified | Docs Contact: | |||||||||||||||
| Priority: | unspecified | ||||||||||||||||
| Version: | 16 | CC: | maxamillion, otaylor, samkraju, stefw, walters | ||||||||||||||
| Target Milestone: | --- | ||||||||||||||||
| Target Release: | --- | ||||||||||||||||
| Hardware: | i686 | ||||||||||||||||
| OS: | Unspecified | ||||||||||||||||
| Whiteboard: | abrt_hash:b1670ee6320cae5a802bb18446f7127b3d598e62 | ||||||||||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||||||||||
| Doc Text: | Story Points: | --- | |||||||||||||||
| Clone Of: | Environment: | ||||||||||||||||
| Last Closed: | 2012-01-31 16:00:07 UTC | Type: | --- | ||||||||||||||
| Regression: | --- | Mount Type: | --- | ||||||||||||||
| Documentation: | --- | CRM: | |||||||||||||||
| Verified Versions: | Category: | --- | |||||||||||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||||||||||
| Attachments: |
|
||||||||||||||||
|
Description
Gleb Sharkunov
2012-01-11 11:10:15 UTC
Created attachment 552080 [details]
File: maps
Created attachment 552081 [details]
File: event_log
Created attachment 552082 [details]
File: dso_list
Created attachment 552083 [details]
File: build_ids
Created attachment 552084 [details]
File: var_log_messages
Created attachment 552085 [details]
File: backtrace
I can't reproduce this problem at this point.
But here's what looks really strange:
#4 0x43dce5a0 in g_assertion_message_expr (domain=0x4535bd12 "Gkr", file=0x4535c20e "gkr-operation.c", line=232, func=0x4535c870 "on_complete", expr=0x4535bd00 "cb") at gtestutils.c:1436
s = <optimized out>
#5 0x4534b414 in on_complete (op=<optimized out>) at gkr-operation.c:232
No locals.
#6 on_complete (op=0x90f18f0) at gkr-operation.c:225
cb = <optimized out>
#7 0x4534b471 in on_complete_later (data=0x90f18f0) at gkr-operation.c:250
op = 0x90f18f0
If you look at this code on_complete_later() is only calling on_complete() if there is stuff in the callbacks queue. on_complete() then asserts because there is nothing in the queue.
The obvious explanation would be if a NULL was pushed into the queue. But that shouldn't be possible given that gkr_operation_push() is the only place where pushing into the queue takes place and it unconditionally pushes the result of a g_slice_new().
So will need to reproduce or see more stack traces to explain this.
Confirming now: this bug is a duplicate of bug #757478 I may be missing something, but I can't make that change to this bug. *** This bug has been marked as a duplicate of bug 757478 *** |