[apport] scim-panel-gtk crashed with SIGSEGV in scim::PanelAgent::stop()

[Loïc Martin]

Binary package hint: scim

Just was informed after startx (had killed gdm to reconfigure xserver-xorg) that an application crashed, then arrived here thanks to the bug report tool.

Feisty daily build 15/03/07 with 16/03 updates

ProblemType: Crash
Architecture: i386
Date: Fri Mar 16 23:06:19 2007
DistroRelease: Ubuntu 7.04
ExecutablePath: /usr/lib/scim-1.0/scim-panel-gtk
Package: scim 1.4.4-7ubuntu1
PackageArchitecture: i386
ProcCmdline: /usr/lib/scim-1.0/scim-panel-gtk --display :0.0 -c socket -d --no-stay
ProcCwd: /home/t3g
ProcEnviron:
 LANGUAGE=fr_FR:fr:en_GB:en
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: scim
StacktraceTop:
 scim::PanelAgent::stop () from /usr/lib/libscim-1.0.so.8
 ?? ()

 ?? () from /usr/lib/libgdk-x11-2.0.so.0
 ?? ()
Uname: Linux t3g-laptop 2.6.20-11-generic #2 SMP Thu Mar 15 08:03:07 UTC 2007 i686 GNU/Linux
UserGroups: adm admin audio cdrom dialout dip floppy lpadmin netdev plugdev powerdev scanner video

[Apport retracing service (apport)]

StacktraceTop:signalhandler (sig=1) at scim_panel_gtk.cpp:3290
?? ()
?? ()
?? ()

[Sebastien Bacher (seb128)]

Thanks for your bug report. Please try to obtain a backtrace http://wiki.ubuntu.com/DebuggingProgramCrash and attach the file to the bug report. This will greatly help us in tracking down your problem.

[Loïc Martin (loic-martin3)]

I haven't been able to get the crash again, and with the constant updates I'm not sure it will reappear soon. I'll keep an eye on it though

[Masatoshi Itagaki (masatoshi)]

I'm experiencing same crash repeatedly.

[Loïc Martin (loic-martin3)]

Masatoshi, could you please try to obtain a backtrace using Sebastian's advices? I haven't encountered the crash anymore, so your help would be appreciated :)

[Loïc Martin (loic-martin3)]

Sorry, please disregard my above comment :)

[arno_b (arno.b)]

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!