In the menu spell checking enableing dutch crashes empathy

Bug #547096 reported by Ian Corne
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
empathy (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Binary package hint: empathy

Whenever I start typing it crashed empathy.

This only happens when enabling dutch;Flemish spellchecking.

ProblemType: Bug
Architecture: i386
Date: Thu Mar 25 18:18:46 2010
DistroRelease: Ubuntu 10.04
Package: empathy 2.29.93-0ubuntu2
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.32-17.26-generic 2.6.32.10+drm33.1
SourcePackage: empathy
Uname: Linux 2.6.32-17-generic i686

Revision history for this message
Ian Corne (icorne) wrote :
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 empathy (Ubuntu):
importance: Undecided → Medium
status: New → Invalid
Revision history for this message
Ian Corne (icorne) wrote :

I'm running 10.04

I will try to get apport to report it, but it crashed too, last time.

Revision history for this message
Ian Corne (icorne) wrote :

The program crashed on an assertion failure, but the message could not be retrieved. Apport does not support reporting these crashes.

What can i do to help now?

I have the _usr_bin_empathy.1000.crash file

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

did you read the previous comment? you can open a bug as described...

Revision history for this message
Ian Corne (icorne) wrote :

Did you read what I said?

Your method doesn't work, it returns:

"The problem cannot be reported:

The program crashed on an assertion failure, but the message could not be retrieved. Apport does not support reporting these crashes."

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

Could you try to obtain a backtrace following the instructions at http://wiki.ubuntu.com/DebuggingProgramCrash and upload the backtrace (as an attachment) to the bug report. This will greatly help us in tracking down your problem.

Changed in empathy (Ubuntu):
status: Invalid → Incomplete
Revision history for this message
Ian Corne (icorne) wrote :

Ok i'm trying that but if I follow the steps, gdb hangs too..

This is all I get, after that I have to try alot to get gdb to exit.

$ gdb empathy 2>&1 | tee ~/gdb-empathy.txt

(gdb) handle SIG33 pass nostop noprint
Signal Stop Print Pass to program Description
SIG33 No No Yes Real-time event 33
(gdb) set pagination 0
(gdb) run
Starting program: /usr/bin/empathy
[Thread debugging using libthread_db enabled]
terminate called after throwing an instance of 'std::length_error'
  what(): basic_string::assign

Program received signal SIGABRT, Aborted.
0x0012d422 in __kernel_vsyscall ()
(gdb)

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

the log seems about right, you just didn't type "backtrace" once you got the crash

Revision history for this message
Ian Corne (icorne) wrote :

That is because I couldn't do that anymore; like I said: gdb hangs too..

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

could be that gdb stops empathy while the focus is being locked, in which case it would require to be run in an another user session, the crash can also be used to get the details locally by somebody interested by doing the extra work there otherwise

Changed in empathy (Ubuntu):
status: Incomplete → New
Revision history for this message
Ian Corne (icorne) wrote :

I enabled the dutch spelling in maverick and it seems to works fine now.

Revision history for this message
Omer Akram (om26er) wrote :

closing this bug assuming it got fixed at its own. as in maverick we are still using 2.30.1 if you face this bug again feel free to open it again

Changed in empathy (Ubuntu):
status: New → Invalid
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.