awn-applet-activation crashed with SIGSEGV in g_utf8_validate()

[Thomas Novin]

Binary package hint: avant-window-navigator

I think by adding the Places applet, awn-applet-activation crashes during startup.

ProblemType: Crash
Architecture: i386
CrashCounter: 1
DistroRelease: Ubuntu 8.10
ExecutablePath: /usr/bin/awn-applet-activation
NonfreeKernelModules: nvidia
Package: avant-window-navigator 0.2.6-7
ProcAttrCurrent: unconfined
ProcCmdline: Places let-activation -p /usr/share/awn/applets/places.desktop -u 1221248709 -w 35651642 -o 0 -h 40
ProcEnviron:
 PATH=/home/username/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=en_DK.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: avant-window-navigator
StacktraceTop:
 g_utf8_validate () from /usr/lib/libglib-2.0.so.0
 ?? () from /usr/lib/libglib-2.0.so.0
 g_filename_from_utf8 () from /usr/lib/libglib-2.0.so.0
 ?? () from /usr/lib/awn/applets/places/places.so
 g_cclosure_marshal_VOID__VOID ()
Title: awn-applet-activation crashed with SIGSEGV in g_utf8_validate()
Uname: Linux 2.6.27-3-generic i686
UserGroups: adm admin audio cdrom dialout dip floppy fuse lpadmin plugdev sambashare uml-net vboxusers video

[Apport retracing service (apport)]

StacktraceTop:IA__g_utf8_validate (str=0x0, max_len=-1, end=0x0)
strdup_len (string=0x0, len=-1, bytes_written=0x0,
IA__g_filename_from_utf8 (utf8string=0x0, len=-1,
_bloody_thing_has_style (widget=0x98a5028, places=0x989bac8)
IA__g_cclosure_marshal_VOID__VOID (closure=0x99071a8,

[Thomas Novin (thomasn80)]

I think this happens when I add the 'Places' applet.

[Julien Lavergne (gilir)]

Thanks for your bug report.

Could you still reproduce the problem with the 0.3.2 release ? You can download the release using the awn-core PPA for Intrepid (https://launchpad.net/~awn-core/+archive/ppa) or directly in the official repository if you are using Jaunty.

[Thomas Novin (thomasn80)]

Ok, I have that version and I cannot reproduce. Howver IIRC I don't think I had this problem before I switched either (the problem was already fixed or something else made the problem go away).

[Julien Lavergne (gilir)]

Thanks for the testing.
Many things was fixed since the 0.2.6, I guess this bug was one of them.