After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 546741 - Evolution Mail and Calendar: when trying to save a ta...
Evolution Mail and Calendar: when trying to save a ta...
Status: RESOLVED DUPLICATE of bug 544187
Product: evolution
Classification: Applications
Component: BugBuddyBugs
2.22.x (obsolete)
Other All
: High critical
: ---
Assigned To: Evolution Triage Team
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2008-08-07 08:40 UTC by prestocaso
Modified: 2008-08-08 08:21 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22

Attachments
crash details that i was able to capture (10.54 KB, application/vnd.oasis.opendocument.text)
2008-08-07 22:10 UTC, prestocaso 		Details
back trace from evolution crash (22.63 KB, text/plain)
2008-08-08 00:28 UTC, prestocaso 		Details
here's the new crash report (31.03 KB, text/plain)
2008-08-08 01:32 UTC, prestocaso 		Details

Description prestocaso 2008-08-07 08:40:24 UTC 
when trying to save a task it freezes then chrashes to desktop


Distribution: Fedora release 9 (Sulphur)
Gnome Release: 2.22.3 2008-07-01 (Red Hat, Inc)
BugBuddy Version: 2.22.0
Comment 1 André Klapper 2008-08-07 16:28:08 UTC 
Thanks for taking the time to report this bug.
Without a stack trace from the crash it's very hard to determine what caused it.
Can you get us a stack trace? Please see http://live.gnome.org/GettingTraces for more information on how to do so. Thanks in advance!
Comment 2 prestocaso 2008-08-07 19:37:23 UTC 
(In reply to comment #1)
> Thanks for taking the time to report this bug.
> Without a stack trace from the crash it's very hard to determine what caused
> it.
> Can you get us a stack trace? Please see http://live.gnome.org/GettingTraces
> for more information on how to do so. Thanks in advance!
> 

sorry I thought the crash report was sent, I will try to get that information to you
Comment 3 prestocaso 2008-08-07 22:10:23 UTC 
Created attachment 116103 [details]
crash details that i was able to capture

for some reason when I try to send a crash report i get a network failure so i had to recreate the crash and copy and paste
Comment 4 André Klapper 2008-08-07 22:50:15 UTC 
There is no stacktrace at all in that attachment, please get us one of the crash. See the link I had provided.
And please, for the sake of network traffic, please attach plain simple textfiles as plain simple textfiles (and not as open office documents). Don't make things complicated, and I can't see any text colors or different fonts used in that document... ;-)
Comment 5 prestocaso 2008-08-08 00:18:32 UTC 
ok, installed what i beleive was needed to do a backtrace. I am new to this so forgive my misunderstanding
Comment 6 prestocaso 2008-08-08 00:28:37 UTC 
Created attachment 116109 [details]
back trace from evolution crash

hopefully i have given you the information correctly this time. If there is a preferred text app. of format let me know
Comment 7 André Klapper 2008-08-08 01:11:32 UTC 
Ah, better. Thanks. :-)
Looks a bit like bug 335618, but the stacktrace is missing lots of so-called symbols. Can you please install debug packages by running
       debuginfo-install evolution.i386
while being root and reproduce?
Comment 8 prestocaso 2008-08-08 01:32:50 UTC 
Created attachment 116110 [details]
here's the new crash report 

ok here is the updated info with all the additional stuff installed. Hope this gives you the additional information you need. Also let me know if there is anything else I can do
Comment 9 André Klapper 2008-08-08 08:21:31 UTC 
Thanks! This is the same as bug 544187. See comment 6 other there for a workaround.

*** This bug has been marked as a duplicate of 544187 ***