Crash modifying GtkToolbar (g_utf8_normalize_wc)

[Vicente Ruiz]

Binary package hint: glade-3

I was modifying a Gtk.ToolBar when glade crashed it.

ProblemType: Crash
Architecture: amd64
Disassembly: 0x7f21e06108e9:
DistroRelease: Ubuntu 8.10
ExecutablePath: /usr/bin/glade-3
NonfreeKernelModules: nvidia
Package: glade-3 3.4.5-3ubuntu1
ProcAttrCurrent: unconfined
ProcCmdline: glade-3 /home/username/Lector/src/lector\ (copia).glade
ProcEnviron:
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=es_ES.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: glade-3
Stacktrace: #0 0x00007f21e06108e9 in ?? ()
StacktraceTop: ?? ()
ThreadStacktrace:

Title: glade-3 crashed with SIGSEGV
Uname: Linux 2.6.26-5-generic x86_64
UserGroups: adm admin audio cdrom dialout dip floppy fuse lpadmin plugdev sambashare video

[Apport retracing service (apport)]

StacktraceTop:?? ()

[Sebastien Bacher (seb128)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please 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.

[Vicente Ruiz (uve)]

it's dificult to reproduce! This error always doesn't happen. Is sufficient this backtrace?

[Sebastien Bacher (seb128)]

the log you got is not a crash

[Vicente Ruiz (uve)]

I'm sorry. I have been mistaken with the file.

I installed glade-3-dbgsym, glade-gnome-3-dbgsym and libglib2.0-0-dbgsym

[Sebastien Bacher (seb128)]

could you also install libgtk2.0-0-dbgsym and get a new stacktrace?

[Vicente Ruiz (uve)]

I uninstalled glade-gnome-3 and glade-gnome-3-dbgsym and this error continues happening. I installed libgtk2.0-0-dbgsym and I attach the new stacktrace.

[Pedro Villavicencio (pedro)]

Thanks for your bug report. This bug has been reported to the developers of the software. You can track it and make comments here: http://bugzilla.gnome.org/show_bug.cgi?id=550503

[Andreas Moog (ampelbein)]

Upstream closed the report as incomplete, do you still get the crash with a current version?

[Sebastien Bacher (seb128)]

We are closing this bug report as it lacks the information, described in the previous comments, we need to investigate the problem further. However, please reopen it if you can give us the missing information and don't hesitate to submit bug reports in the future.