Bug 177856
Summary: | Evolution crash when clicking sort header buton | ||||||
---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Erwin Rol <redhatbugs> | ||||
Component: | evolution | Assignee: | Dave Malcolm <dmalcolm> | ||||
Status: | CLOSED UPSTREAM | QA Contact: | |||||
Severity: | medium | Docs Contact: | |||||
Priority: | medium | ||||||
Version: | rawhide | CC: | bojan, jlaska, nicolas.mailhot | ||||
Target Milestone: | --- | ||||||
Target Release: | --- | ||||||
Hardware: | x86_64 | ||||||
OS: | Linux | ||||||
Whiteboard: | |||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | Environment: | ||||||
Last Closed: | 2006-01-27 18:16:08 UTC | Type: | --- | ||||
Regression: | --- | Mount Type: | --- | ||||
Documentation: | --- | CRM: | |||||
Verified Versions: | Category: | --- | |||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
Cloudforms Team: | --- | Target Upstream Version: | |||||
Embargoed: | |||||||
Bug Depends On: | |||||||
Bug Blocks: | 150222 | ||||||
Attachments: |
|
Description
Erwin Rol
2006-01-15 18:22:21 UTC
Me too. This is on an P4 based machine, so the arch is more than just x86_64. Created attachment 123237 [details]
gdb backtrace
Attaching gdb backtrace. Please advise if there are additional debuginfo
packages you'd like applied when generating the backtrace.
I've been seeing crashes in 2.5.x on rawhide after around 5 minutes of it running using evo and evo-connector for exchange. I filed the included (linked below) backtrace with debuginfo installed on b.g.o, not sure if its related. Thanks for this bug report. I believe that this is a long-standing source of a "critical" glib warning from the ETable code. Recent gnome-session changes have made this level of warning be fatal. I believe we're going to revert this. This has already been filed upstream here: http://bugzilla.gnome.org/show_bug.cgi?id=327035 With the last 20060118 rawhide update the crash went away. Ray, given that this is a "critical warning" bug, and filed upstream, should we just close this UPSTREAM ? Matthias, sounds reasonable |