Evolution Crash in Ubuntu Karmic on hitting REPLY button

Bug #459929 reported by whiteblinder
26
This bug affects 4 people
Affects Status Importance Assigned to Milestone
evolution (Ubuntu)
Invalid
Medium
Ubuntu Desktop Bugs

Bug Description

Binary package hint: evolution

Hello:

I recently updated from Ubuntu 9.04 to 9.10. Evolution started to crash when I try to hit REPLY button.
I am runnig 2.6.31-14-generic kernel.
==================================
apt-cache policy evolution

evolution:

  Installed: 2.28.1-0ubuntu1

  Candidate: 2.28.1-0ubuntu1

  Version table:

 *** 2.28.1-0ubuntu1 0

        500 http://us.archive.ubuntu.com karmic/main Packages

        100 /var/lib/dpkg/status

====================================

ProblemType: Bug
Architecture: i386
Date: Sat Oct 24 11:05:07 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/evolution
NonfreeKernelModules: nvidia
Package: evolution 2.28.1-0ubuntu1
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
SourcePackage: evolution
Uname: Linux 2.6.31-14-generic i686

Revision history for this message
whiteblinder (whiteblinder) wrote :
Revision history for this message
whiteblinder (whiteblinder) wrote :
Download full text (3.5 KiB)

This is the output of CLI run, with “terminate called after throwing an instance of 'std::length_error'
 “, than I hit REPLY button:

v@comp1:/etc/apt$ evolution

** (evolution:7275): DEBUG: mailto URL command: evolution --component=mail %s

** (evolution:7275): DEBUG: mailto URL program: evolution

** (evolution:7275): CRITICAL **: atk_object_set_name: assertion `name != NULL' failed

** (evolution:7275): CRITICAL **: atk_object_set_name: assertion `name != NULL' failed

** (evolution:7275): CRITICAL **: atk_object_set_name: assertion `name != NULL' failed

** (evolution:7275): CRITICAL **: atk_object_set_name: assertion `name != NULL' failed

** (evolution:7275): CRITICAL **: atk_object_set_name: assertion `name != NULL' failed

** (evolution:7275): CRITICAL **: atk_object_set_name: assertion `name != NULL' failed

** (evolution:7275): CRITICAL **: atk_object_set_name: assertion `name != NULL' failed

** (evolution:7275): CRITICAL **: atk_object_set_name: assertion `name != NULL' failed

** (evolution:7275): CRITICAL **: atk_object_set_name: assertion `name != NULL' failed

** (evolution:7275): CRITICAL **: atk_object_set_name: assertion `name != NULL' failed

** (evolution:7275): CRITICAL **: atk_object_set_name: assertion `name != NULL' failed

** (evolution:7275): CRITICAL **: atk_object_set_name: assertion `name != NULL' failed

** (evolution:7275): CRITICAL **: atk_object_set_name: assertion `name != NULL' failed

** (evolution:7275): CRITICAL **: atk_object_set_name: assertion `name != NULL' failed

** (evolution:7275): CRITICAL **: atk_object_set_name: assertion `name != NULL' failed

** (evolution:7275): CRITICAL **: atk_object_set_name: assertion `name != NULL' failed

** (evolution:7275): CRITICAL **: atk_object_set_name: assertion `name != NULL' failed

** (evolution:7275): CRITICAL **: atk_object_set_name: assertion `name != NULL' failed

** (evolution:7275): CRITICAL **: atk_object_set_name: assertion `name != NULL' failed

** (evolution:7275): CRITICAL **: atk_object_set_name: assertion `name != NULL' failed

** (evolution:7275): CRITICAL **: atk_object_set_name: assertion `name != NULL' failed

** (evolution:7275): CRITICAL **: atk_object_set_name: assertion `name != NULL' failed

** (evolution:7275): CRITICAL **: atk_object_set_name: assertion `name != NULL' failed

** (evolution:7275): CRITICAL **: atk_object_set_name: assertion `name != NULL' failed

** (evolution:7275): CRITICAL **: atk_object_set_name: assertion `name != NULL' failed

** (evolution:7275): CRITICAL **: atk_object_set_name: assertion `name != NULL' failed

** (evolution:7275): CRITICAL **: atk_object_set_name: assertion `name != NULL' failed

** (evolution:7275): CRITICAL **: atk_object_set_name: assertion `name != NULL' failed

** (evolution:7275): CRITICAL **: atk_object_set_name: assertion `name != NULL' failed

** (evolution:7275): CRITICAL **: atk_object_set_name: assertion `name != NULL' failed

** (evolution:7275): CRITICAL **: atk_object_set_name: assertion `name != NULL' failed

** (evolution:7275): CRITICAL **: atk_object_set_name: assertion `name != NULL' failed

** (evolution:727...

Read more...

Revision history for this message
whiteblinder (whiteblinder) wrote :

Could you,please let me know what other report I can generate to help ?

Revision history for this message
whiteblinder (whiteblinder) wrote :

I am not an expert in reporting these bugs stuff, but I think this might help (backtrace):

gdb evolution

Attachment bug_report2.txt has an output of that bug in progress

Revision history for this message
jatin sachdeva (jatin-sachdeva) wrote :

I see this error all the time - running evolution with exchange on karmic rc

** (evolution:22159): CRITICAL **: atk_object_set_name: assertion `name != NULL' failed

Revision history for this message
Sebastien Bacher (seb128) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. However, your crash report is either missing or challenging to deal with as a '.crash' file. Please follow these instructions to have apport report a new bug about your crash that can be dealt with by the automatic retracer.

 If you are running the Ubuntu Stable Release you might need to enable apport in /etc/default/apport and restart.

 If you are using Ubuntu with the Gnome desktop environment - launch nautilus and navigate to your /var/crash directory and double click on the crash report you wish to submit.

 If you are using Kubuntu or Xubuntu you can file the crash using /usr/share/apport/apport-qt --crash-file=/var/crash/_my_crash_report.crash in a terminal - where _my_crash_report.crash is the crash you would like to report.
 I'm closing this bug report since the process outlined above will automatically open a new bug report which can then dealt with more efficiently. Thanks in advance for your cooperation and understanding.

Changed in evolution (Ubuntu):
assignee: nobody → Ubuntu Desktop Bugs (desktop-bugs)
importance: Undecided → Medium
status: New → Invalid
Revision history for this message
Julius Roberts (hooliowobbits) wrote :

I have this same issue. Initially it was caused by hitting reply, and now each time i try to start evo it starts and crashes out; the following being the output if invoked from the CLI:

** (evolution:5659): CRITICAL **: atk_object_set_name: assertion `name != NULL’ failed
(about 7 or 8 times, followed by the Evo window starting up, asking me if i want to attempt to recover from a crash and then half a second later it disappears)
** (evolution:5659): CRITICAL **: atk_object_set_name: assertion `name != NULL’ failed
(a few more times then)
Segmentation fault

..and i’m dumped back out at the CLI.

I guess there’s no point saying that this is kinda urgent ;)

Revision history for this message
Julius Roberts (hooliowobbits) wrote :

I've also submitted my bug via apport and attached it to this bug ticket.

Revision history for this message
Sebastien Bacher (seb128) wrote :

could you give the bug number for the apport submitted ticket?

Revision history for this message
Julius Roberts (hooliowobbits) wrote :

Thanks for helping :) I thought i had attached my apport output to this bug report?
Anyhow using my apport output I've created a new report https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/471825

Revision history for this message
lunomad (damon-metapaso) wrote :

I also get the

** (evolution:11352): CRITICAL **: atk_object_set_name: assertion `name != NULL' failed

when I run evolution from the CLI, but it doesn't bring evolution down. Evolution runs well with all POP and IMAP accounts (except google contact syncing, which is what I'm trying to fix). Perhaps with some instruction I could help locate the source of this bug?

Damon

Revision history for this message
Gabe Gorelick (gabegorelick) wrote :

The atk_object_set_name: assertion `name != NULL' messages are just warnings, and shouldn't cause any problems. See bug #475426 for details.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.