gtk-update-icon-cache crashed with SIGSEGV in free()

Bug #201719 reported by Ulf Andersson
6
Affects Status Importance Assigned to Milestone
gtk+2.0 (Ubuntu)
Invalid
Medium
Ubuntu Desktop Bugs

Bug Description

It crashes for some reason

ProblemType: Crash
Architecture: amd64
Date: Thu Mar 13 07:51:41 2008
DistroRelease: Ubuntu 8.04
ExecutablePath: /usr/lib/libgtk2.0-0/gtk-update-icon-cache
NonfreeKernelModules: snd_hda_intel snd_pcm_oss snd_mixer_oss snd_pcm snd_page_alloc snd_hwdep snd_seq_dummy snd_seq_oss snd_seq_midi snd_rawmidi snd_seq_midi_event snd_seq snd_timer snd_seq_device snd wmi_acer cdrom
Package: libgtk2.0-0 2.12.9-1
PackageArchitecture: amd64
ProcCmdline: gtk-update-icon-cache --force --quiet /usr/share/icons/hicolor
ProcEnviron:
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/X11R6/bin
 LANG=en_US.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: gtk+2.0
Stacktrace:
 #0 0x00007f8387b3bb29 in free () from /lib/libc.so.6
 #1 0x0000000000000000 in ?? ()
StacktraceTop:
 free () from /lib/libc.so.6
 ?? ()
ThreadStacktrace:
 .
 Thread 1 (process 21260):
 #0 0x00007f8387b3bb29 in free () from /lib/libc.so.6
 #1 0x0000000000000000 in ?? ()
Title: gtk-update-icon-cache crashed with SIGSEGV in free()
Uname: Linux 2.6.24-12-generic x86_64
UserGroups:

Revision history for this message
Ulf Andersson (uanderss) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:free () from /lib/libc.so.6
?? ()

Revision history for this message
Apport retracing service (apport) wrote : Symbolic threaded stack trace
Revision history for this message
Pedro Villavicencio (pedro) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please try to obtain a valgrind log following the instructions at https://wiki.ubuntu.com/Valgrind and attach the file to the bug report. This will greatly help us in tracking down your problem.

Changed in gtk+2.0:
assignee: nobody → desktop-bugs
importance: Undecided → Medium
status: New → Incomplete
Revision history for this message
Pedro Villavicencio (pedro) wrote :

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!.

Changed in gtk+2.0:
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.