GNOME Bugzilla – Bug 600753
After clearing chat screen a couple of times and closing chat-empathy will crash when reopening chat with that person
Last modified: 2010-04-19 08:07:51 UTC
I originally posted this on bugs.launchpad.com who suggested that this bug posting would be more appropriate. I am pasting exactly as it was over there. If there is any more information I can provide: Please let me know. Ubuntu 9.10 empathy: Installed: 2.28.1-1ubuntu1 Candidate: 2.28.1.1-0ubuntu1 Version table: 2.28.1.1-0ubuntu1 0 500 http://us.archive.ubuntu.com karmic-updates/main Packages *** 2.28.1-1ubuntu1 0 500 http://us.archive.ubuntu.com karmic/main Packages 100 /var/lib/dpkg/status This is a fairly clean install, less than a week old with minimal additional packages added (so far) Description: 3) When clearing chat the expected function is for the chat history to be removed and not restored when a new chat to that person is started. Second: It isn't supposed to crash :P When pasting links Empathy will occasionally doublepost and then crash. The same issue can be seen after a chat window has been open for awhile-such as an hour+ then an attempt to clear the chat history followed by more typing-will occasionally crash Empathy. Second to this, on clears and reopens the chat window has the 'cleared' chat still in place and commonly shows the last message twice. When intentionally trying: I have replicated the issue with limited success. Usually by a combination of clearing text then closing the chat and reopening chat to the same person. ProblemType: Bug Architecture: i386 Date: Wed Nov 4 14:40:51 2009 DistroRelease: Ubuntu 9.10 ExecutablePath: /usr/bin/empathy InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5) NonfreeKernelModules: nvidia Package: empathy 2.28.1-1ubuntu1 ProcEnviron: SHELL=/bin/bash LANG=en_US.UTF-8 ProcVersionSignature: Ubuntu 2.6.31-14.48-generic SourcePackage: empathy Uname: Linux 2.6.31-14-generic i686
I think this is not an issue anymore with empathy 2.30
Please reopen if you reproduced this bug with 2.30.x or master.