Ubuntu
gnome-utils package

Feisty Herd4: [apport] baobab crashed with SIGSEGV in pango_fc_font_lock_face()

Bug #85787 reported by moma on 2007-02-17

	Status	Importance	Assigned to
Pango	Fix Released	Critical	gnome-bugs #411867
baobab (Ubuntu)	Fix Released	Undecided	Unassigned
gnome-utils (Ubuntu)	Fix Released	Medium	Ubuntu Desktop Bugs

Bug Description

Binary package hint: gnome-utils

Baobab (disk usage analyzer app) in Feisty Herd4 crashed badly.

Clicked repeatedly menu selection Edit -> Expand All and Stop button + Scan Home button.

ProblemType: Crash
Date: Sat Feb 17 14:43:37 2007
DistroRelease: Ubuntu 7.04
ExecutablePath: /usr/bin/baobab
Package: gnome-utils 2.17.92-0ubuntu1
ProcCmdline: baobab
ProcCwd: /home/moma
ProcEnviron:
LANGUAGE=en_GB:en
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
LANG=en_GB.UTF-8
SHELL=/bin/bash
Signal: 11
SourcePackage: gnome-utils
StacktraceTop:
?? () from /usr/lib/libpangoft2-1.0.so.0
?? ()
?? ()
?? ()
pango_fc_font_lock_face ()
Uname: Linux moma-desktop 2.6.20-8-generic #2 SMP Tue Feb 13 05:18:42 UTC 2007 i686 GNU/Linux
UserGroups: adm admin audio cdrom dialout dip floppy lpadmin netdev plugdev powerdev scanner video

Revision history for this message

moma (osmoma) wrote on 2007-02-17:

Dependencies.txt Edit (4.0 KiB, text/plain; charset="utf-8")
Disassembly.txt Edit (782 bytes, text/plain; charset="utf-8")
ProcMaps.txt Edit (23.5 KiB, text/plain; charset="utf-8")
ProcStatus.txt Edit (662 bytes, text/plain; charset="utf-8")
Registers.txt Edit (510 bytes, text/plain; charset="utf-8")
Stacktrace.txt Edit (1.0 KiB, text/plain; charset="utf-8")
ThreadStacktrace.txt Edit (881 bytes, text/plain; charset="utf-8")

Revision history for this message

Sebastien Bacher (seb128) wrote on 2007-02-17:

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-utils:
assignee:	nobody → desktop-bugs
importance:	Undecided → Medium
status:	Unconfirmed → Needs Info

Revision history for this message

moma (osmoma) wrote on 2007-02-18:

valgrind -v --tool=memcheck --leak-check=full --num-callers=12 --log-file=valgrind.log baobab Edit (11.9 KiB, application/x-tar)

Rehello,
I have now run baobab with Valgrind. See the attachment.

As said earlier, just press Scan Home button, Stop button and Edit -> Expand All menu selection couple of times and it crashes (do not wait any of the actions to complete, just click on...)

// moma
http://www.futuredesktop.org

Revision history for this message

moma (osmoma) wrote on 2007-02-18:

2.: valgrind -v --tool=memcheck --leak-check=full --num-callers=20 --log-file=valgrind.log /usr/bin/baobab Edit (14.1 KiB, application/x-tar)

2. run with Valgrind memory sniffer.

$ rm valgrind.log.*

$ valgrind -v --tool=memcheck --leak-check=full --num-callers=20 --log-file=valgrind.log /usr/bin/baobab
Segmentation fault (core dumped)

Revision history for this message

Sebastien Bacher (seb128) wrote on 2007-02-24:

Thank you for your work on that. Could you get an another log with libglib2.0-0-dbg libgtk2.0-0-dbg libgpango1.0-0-dbg installed?

Revision history for this message

moma (osmoma) wrote on 2007-02-25:

valgrind -v --tool=memcheck --leak-check=full --num-callers=12 --log-file=valgrind.log baobab Edit (11.3 KiB, application/x-tar)

Do you mean "libpango1.0-0-dbg"?

$ sudo apt-get install libglib2.0-0-dbg libgtk2.0-0-dbg libpango1.0-0-dbg

It was slightly harder to crash now than previously.

$ valgrind -v --tool=memcheck --leak-check=full --num-callers=12 --log-file=valgrind.log baobab

(baobab:6227): GLib-GObject-CRITICAL **: g_object_ref: assertion `G_IS_OBJECT (object)' failed
Segmentation fault (core dumped)

See the attachment.

Revision history for this message

moma (osmoma) wrote on 2007-02-25:

valgrind -v --tool=memcheck --leak-check=full --num-callers=12 --log-file=valgrind.log baobab Edit (11.4 KiB, application/x-tar)

Second run of Baobab with libglib2.0-0-dbg libgtk2.0-0-dbg libpango1.0-0-dbg libraries.

$ valgrind -v --tool=memcheck --leak-check=full --num-callers=12 --log-file=valgrind.log baobab
Segmentation fault (core dumped)

Revision history for this message

Sebastien Bacher (seb128) wrote on 2007-02-25:

That looks better, could you do another one with num-callers=20?

Revision history for this message

Sebastien Bacher (seb128) wrote on 2007-02-25:

Confirmed, no need of the new log

Changed in gnome-utils:
status:	Needs Info → Confirmed

Revision history for this message

Sebastien Bacher (seb128) wrote on 2007-02-25:

#10

I've forwarded that upstream: http://bugzilla.gnome.org/show_bug.cgi?id=411867

Revision history for this message

Fabio Marzocca (thesaltydog) wrote on 2007-02-26:

#11

This bug has been fixed in upstream development version.
Thanks for reporting.
Fabio

Changed in pango1.0:
status:	Confirmed → Fix Committed

Bug Watch Updater (bug-watch-updater) on 2007-02-26

Changed in pango:
status:	Unknown → Fix Released

Revision history for this message

Sebastien Bacher (seb128) wrote on 2007-03-12:

#12

gnome-utils (2.18.0-0ubuntu1) feisty; urgency=low
.
   * New upstream version:
     Baobab:
     - Fix bug #411867 - baobab crashed with SIGSEGV in
       pango_fc_font_lock_face() (Ubuntu: #85787)
     - Resort when toggling "allocated space".
     Screenshot:
     - Fix bug #413019 - The effects in theinteractive dialog are not
       fully translated
     - Fix bug #411050 - With some window name, the screenshot tool
       will propose to replace ~/Desktop with the image
   * debian/patches/02_autoconf.patch:
     - updated

Changed in gnome-utils:
status:	Fix Committed → Fix Released

Fabio Marzocca (thesaltydog) on 2007-03-21

Changed in baobab:
status:	Unconfirmed → Fix Released

Revision history for this message

sukhamayganguly (sukhamayganguly) wrote on 2007-09-16:

#13

E: dpkg was interrupted, you must manually run 'dpkg --configure -a' to correct the problem.
E: _cache->open() failed, please report.
At the time opening the synaptic Package Manager above command shows.

Bug Watch Updater (bug-watch-updater) on 2010-09-16