** Attachment removed: CoreDump.gz
http://launchpadlibrarian.net/7098632/CoreDump.gz
--
[apport] charpick_applet2 crashed with SIGSEGV in pango_layout_get_iter()
https://bugs.launchpad.net/bugs/99705
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
closing then, feel free to reopen if you get the bug again and can get a
debug log
** Changed in: gnome-applets (Ubuntu)
Status: Needs Info = Rejected
--
[apport] charpick_applet2 crashed with SIGSEGV in pango_layout_get_iter()
https://bugs.launchpad.net/bugs/99705
You received this bug
you can remove the applet, run it on a command line with valgrind and
then add it to the gnome-panel again
--
[apport] charpick_applet2 crashed with SIGSEGV in pango_layout_get_iter()
https://bugs.launchpad.net/bugs/99705
You received this bug notification because you are a member of Ubuntu
Dnia 05-04-2007, czw o godzinie 14:41 +, Sebastien Bacher
napisał(a):
you can remove the applet, run it on a command line with valgrind and
then add it to the gnome-panel again
A did what you asked me about. Nothing happened then.
The problem haven't appeared anymore.
--
Piotr Szczygieł
** Attachment added: CoreDump.gz
http://librarian.launchpad.net/7098632/CoreDump.gz
** Attachment added: Dependencies.txt
http://librarian.launchpad.net/7098633/Dependencies.txt
** Attachment added: Disassembly.txt
http://librarian.launchpad.net/7098634/Disassembly.txt
** Attachment
StacktraceTop:pango_renderer_draw_layout (renderer=0x81cf028, layout=0x81c9b68,
x=165888, y=3072) at /build/buildd/pango1.0-1.16.1/./pango/pango-renderer.c:171
IA__gdk_draw_layout_with_colors (drawable=0x807a160, gc=0x8073ad8, x=162, y=3,
layout=0x81c9b68, foreground=0x0, background=0x0) at
Thanks for your bug report. The crash looks like a memory corruption.
Could you try to get a valgrind log for it (you can follow the
instructions from https://wiki.ubuntu.com/Valgrind for that)?
** Changed in: gnome-applets (Ubuntu)
Importance: Undecided = Medium
Assignee: (unassigned) =
Dnia 01-04-2007, nie o godzinie 10:50 +, Sebastien Bacher
napisał(a):
Thanks for your bug report. The crash looks like a memory corruption.
Could you try to get a valgrind log for it (you can follow the
instructions from https://wiki.ubuntu.com/Valgrind for that)?
I've tried but I think
