| Summary: | [abrt] evolution-3.2.2-1.fc16: idle_expand_row, "code should not be reached" | ||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | james.glenn | ||||||||||||||
| Component: | gtk3 | Assignee: | Matthias Clasen <mclasen> | ||||||||||||||
| Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||||||||
| Severity: | unspecified | Docs Contact: | |||||||||||||||
| Priority: | unspecified | ||||||||||||||||
| Version: | 16 | CC: | lucilanga, mbarnes, mclasen, mcrha | ||||||||||||||
| Target Milestone: | --- | ||||||||||||||||
| Target Release: | --- | ||||||||||||||||
| Hardware: | x86_64 | ||||||||||||||||
| OS: | Unspecified | ||||||||||||||||
| Whiteboard: | abrt_hash:8915dabd77406f55cbf3ddac4c541d9bae858380 | ||||||||||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||||||||||
| Doc Text: | Story Points: | --- | |||||||||||||||
| Clone Of: | Environment: | ||||||||||||||||
| Last Closed: | 2013-02-13 18:10:00 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
james.glenn
2011-12-07 15:46:51 UTC
Created attachment 542019 [details]
File: dso_list
Created attachment 542020 [details]
File: gconf_subtree
Created attachment 542021 [details]
File: build_ids
Created attachment 542022 [details]
File: smolt_data
Created attachment 542023 [details]
File: backtrace
Created attachment 542024 [details]
File: maps
Thanks for a bug report. This is crashing in the gtk3 code, thus I'm moving it there. From the file being involved (gtktreeviewaccessible.c) I suppose this has something to do with accessibility, maybe if you'll disable [1] it and relogin, then the issue will be gone. Maybe not. It will be better to get opinions from gtk developers. [1] gsettings set org.gnome.desktop.interface toolkit-accessibility false Thread 1 (Thread 0x7f1ca62f9980 (LWP 2501)):
#0 0x0000003027e36285 in __GI_raise (sig=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64
resultvar = 0
pid = <optimized out>
selftid = 2501
#1 0x0000003027e37b9b in __GI_abort () at abort.c:91
save_stage = 2
act = {__sigaction_handler = {sa_handler = 0, sa_sigaction = 0}, sa_mask = {__val = {206861371122, 46239776, 206861390193, 2048, 4294967296, 46239776, 46239776, 46242928, 46242928, 46242736, 46242928, 102, 1, 0, 206861285267, 46239776}}, sa_flags = 702971562, sa_restorer = 0}
sigs = {__val = {32, 0 <repeats 15 times>}}
#2 0x0000003029e683cd in g_assertion_message (domain=<optimized out>, file=<optimized out>, line=<optimized out>, func=0x30349b1b70 "idle_expand_row", message=0x3029eb8967 "code should not be reached") at gtestutils.c:1425
lstr = "1600\000\000\000\000`k\301\002\000\000\000\000\200\332\017\001\000\000\000\000\343b\215\064\060\000\000"
s = 0x2c19bb0 ""
#3 0x00000030348d68af in idle_expand_row (data=0x2438020) at gtktreeviewaccessible.c:1600
accessible = 0x2438020 [GtkTreeViewAccessible]
path = 0x2567770
tree_view = 0x2582b00 [EMailSidebar]
iter = {stamp = 835996051, user_data = 0x1e82d90, user_data2 = 0x0, user_data3 = 0x0}
tree_model = 0x15b98f0
n_inserted = 16
row = <optimized out>
__PRETTY_FUNCTION__ = "idle_expand_row"
#4 0x000000303421a35f in gdk_threads_dispatch (data=0x2559960) at gdk.c:754
dispatch = 0x2559960
ret = 0
#5 0x0000003029e44a7d in g_main_dispatch (context=0x10fda80) at gmain.c:2425
dispatch = 0x3029e408a0 <g_idle_dispatch>
was_in_call = 0
user_data = 0x2559960
callback = 0x303421a330 <gdk_threads_dispatch>
cb_funcs = 0x302a11e630
cb_data = 0x250b360
current_source_link = {data = 0x26c9fb0, next = 0x0}
need_destroy = <optimized out>
source = 0x26c9fb0
current = 0x122aca0
i = <optimized out>
#6 g_main_context_dispatch (context=0x10fda80) at gmain.c:2995
No locals.
#7 0x0000003029e45278 in g_main_context_iterate (context=0x10fda80, block=<optimized out>, dispatch=1, self=<optimized out>) at gmain.c:3073
max_priority = 200
timeout = 0
some_ready = 1
nfds = 6
allocated_nfds = <optimized out>
fds = <optimized out>
__PRETTY_FUNCTION__ = "g_main_context_iterate"
#8 0x0000003029e457c5 in g_main_loop_run (loop=0x167d4b0) at gmain.c:3281
self = 0x10b1150
__PRETTY_FUNCTION__ = "g_main_loop_run"
#9 0x00000030347516ad in gtk_main () at gtkmain.c:1362
loop = 0x167d4b0
#10 0x00000000004022e3 in main (argc=1, argv=0x7fffbbed7c08) at main.c:696
shell = 0x12030e0 [EShell]
client = <optimized out>
error = 0x0
Let me know if I can provide anything else. This message is a reminder that Fedora 16 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 16. 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 WONTFIX if it remains open with a Fedora 'version' of '16'. 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 prior to Fedora 16's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 16 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 to click on "Clone This Bug" and open it against that version of Fedora. 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. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 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. Thank you for reporting this bug and we are sorry it could not be fixed. |