| Summary: | When selecting text and click reply evolution crashes. | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Jóhann B. Guðmundsson <johannbg> |
| Component: | evolution | Assignee: | Matthew Barnes <mbarnes> |
| Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 15 | CC: | lucilanga, mbarnes, mcrha |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2012-08-07 17:03:13 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
|
Description
Jóhann B. Guðmundsson
2011-02-17 23:45:41 UTC
Looks like an X11 or GDK issue. Thanks for a bug report. Could you get a backtrace of the crash as described in the error message, please? There is an upstream bug [1] which can be similar to yours, but I want to be sure before I move this upstream. Thanks in advance. [1] https://bugzilla.gnome.org/show_bug.cgi?id=641969 Am already working on getting you an usable backtrace :) Sorry about the late response but I'm having a bit of hard time getting the --sync option to be accepted so any help on proceeding would be appreciated.. $ evolution --sync Unknown option --sync $ evolution -c mail --sync Unknown option --sync $ gdb evolution GNU gdb (GDB) Fedora (7.2.50.20110218-24.fc15) Copyright (C) 2011 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-redhat-linux-gnu". For bug reporting instructions, please see: <http://www.gnu.org/software/gdb/bugs/>... Reading symbols from /usr/bin/evolution...Reading symbols from /usr/lib/debug/usr/bin/evolution.debug...done. done. (gdb) set logging on Copying output to gdb.txt. (gdb) break gdk_x_error Function "gdk_x_error" not defined. Make breakpoint pending on future shared library load? (y or [n]) y Breakpoint 1 (gdk_x_error) pending. (gdb) run -c mail --sync Starting program: /usr/bin/evolution -c mail --sync [Thread debugging using libthread_db enabled] Unknown option --sync Program exited with code 01. (gdb) ??? Oh, they removed the --sync option, but didn't update description. Please run it like this: $ GDK_SYNCHRONIZE=1 gdb evolution --ex "r -c mail" Does not work I still get.. (evolution:19567): Gdk-WARNING **: The program 'evolution' received an X Window System error. This probably reflects a bug in the program. The error was 'BadWindow (invalid Window parameter)'. (Details: serial 82130 error_code 3 request_code 42 minor_code 0) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the --sync command line option to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.) And nothing usable.. Err, my fault, it might be that I forgot to add proper commands there too, the full gdb command should look like this:
$ GDK_SYNCHRONIZE=1 gdb evolution --ex "b gdk_x_error" --ex "r -c mail" \
--ex "t a a bt" --ex q
you should be asked whether you want to add a breakpoint to an unknown location (as a pending breakpoint). Answer 'y' for it (the default value is 'no').
I dont think that will help I think the problem is that "GDK_SYNCHRONIZE=1" or --sync is not working with evolution. This is how you debug Gnome-Shell gnome-shell --replace --sync -g and as you can see the Gnome shell is using sync... + La ultimate gdb cli magic for this looks like this GDK_SYNCHRONIZE=1 gdb evolution -q --ex "set logging on" --ex "set breakpoint pending on" --ex "b gdk_x_error" --ex "r -c mail" --ex "t a a bt full" And Attach gdb.txt to the report :=) I'll test the ultimate gdb cli $foo but i'm pretty sure it wont do any good. This message is a notice that Fedora 15 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 15. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At this time, all open bugs with a Fedora 'version' of '15' have been closed as WONTFIX. (Please note: Our normal process is to give advanced warning of this occurring, but we forgot to do that. A thousand apologies.) Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, feel free to reopen this bug and simply change the 'version' to a later Fedora version. Bug Reporter: Thank you for reporting this issue and we are sorry that we were unable to fix it before Fedora 15 reached 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" (top right of this page) 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 |