empathy crashed joining IRC channel without # before the channel name

[Maarten Jongepier]

Binary package hint: empathy

1.
Description: Ubuntu 9.10
Release: 9.10

2.
empathy:
  Installed: 2.28.1-1ubuntu1
  Candidate: 2.28.1-1ubuntu1
  Version table:
 *** 2.28.1-1ubuntu1 0
        500 http://nl.archive.ubuntu.com karmic/main Packages
        100 /var/lib/dpkg/status

3 and 4.
# Create IRC connect account,
# connect
# join group
# enter channel (instead of #channel)
# -crash-

ProblemType: Crash
Architecture: amd64
Date: Sun Nov 1 16:28:50 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/empathy
NonfreeKernelModules: nvidia
Package: empathy 2.28.1-1ubuntu1
ProcCmdline: empathy
ProcEnviron:
 SHELL=/bin/bash
 LANG=en_US.UTF-8
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
SegvAnalysis:
 Segfault happened at: 0x7fbe00c6dea5: mov 0x18(%rax),%rax
 PC (0x7fbe00c6dea5) ok
 source "0x18(%rax)" (0x00000018) not located in a known VMA region (needed readable region)!
 destination "%rax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: empathy
StacktraceTop:
 ?? () from /usr/lib/libempathy.so.30
 ?? () from /usr/lib/libtelepathy-glib.so.0
 ?? () from /usr/lib/libtelepathy-glib.so.0
 g_main_context_dispatch ()
 ?? () from /lib/libglib-2.0.so.0
Title: empathy crashed with SIGSEGV in g_main_context_dispatch()
Uname: Linux 2.6.31-14-generic x86_64
UserGroups: adm admin cdrom dialout dip disk fuse lpadmin plugdev sambashare vboxusers

[Apport retracing service (apport)]

StacktraceTop:empathy_dispatcher_create_channel ()
g_main_context_dispatch ()
?? () from /lib/libglib-2.0.so.0
g_main_loop_run () from /lib/libglib-2.0.so.0
gtk_main () from /usr/lib/libgtk-x11-2.0.so.0

[Victor Vargas (kamus)]

Please could you check if this issue is still affecting you under latest release included in Ubuntu Lucid? Thanks!

[Omer Akram (om26er)]

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!