gedit failed to install/upgrade: gconftool-2: free(): invalid next size (fast): 0x00000000030d7fb0

Bug #297278 reported by Click
14
Affects Status Importance Assigned to Milestone
gconf2 (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Binary package hint: gedit

gedit upgrade

ProblemType: Package
Architecture: amd64
DistroRelease: Ubuntu 8.10
ErrorMessage: подпроцесс post-installation script возвратил код ошибки 250
Package: gedit 2.24.1-0ubuntu1
SourcePackage: gedit
Title: package gedit 2.24.1-0ubuntu1 failed to install/upgrade: подпроцесс post-installation script возвратил код ошибки 250
Uname: Linux 2.6.27-7-generic x86_64

Revision history for this message
Click (clicky-mail) wrote :
Revision history for this message
Jean-Baptiste Lallement (jibel) wrote :

Thanks for your report

The cause of the failure is
=====
Настраивается пакет gedit (2.24.1-0ubuntu1) ...
*** glibc detected *** gconftool-2: free(): invalid next size (fast): 0x00000000030d7fb0 ***
======= Backtrace: =========
/lib/libc.so.6[0x7f0dadddb938]
/lib/libc.so.6(cfree+0x76)[0x7f0daddddf86]
/usr/lib/libgconf-2.so.4(gconf_schema_free+0x28)[0x7f0dae7d1c18]
gconftool-2[0x404102]
/usr/lib/libglib-2.0.so.0(g_hash_table_foreach+0x4d)[0x7f0dae31bc4d]
gconftool-2[0x406d75]
gconftool-2[0x406e98]
gconftool-2(main+0x1ca0)[0x408e20]
/lib/libc.so.6(__libc_start_main+0xe6)[0x7f0dadd80466]
gconftool-2[0x4039e9]
=====
Affecting to gconf2

This particular bug has already been reported and is a duplicate of bug 297091, so it is being marked as such.

Could you please try to obtain a valgrind log following the instructions at https://wiki.ubuntu.com/Valgrind and attach the file to
the bug report and attach it to the duplicate report.

This will greatly help us in tracking down your problem.

Changed in gedit:
status: New → Incomplete
Revision history for this message
Jean-Baptiste Lallement (jibel) wrote :

Unmarking duplicate of bug 297091. In fact, this is not the same crash. Could you still provide the valgrind trace. thanks.

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 gconf2 (Ubuntu):
importance: Undecided → Medium
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

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