various programs crashed with SIGSEGV in __xmlParserInputBufferCreateFilename()

Bug #149399 reported by HJMills
166
Affects Status Importance Assigned to Milestone
file-roller (Ubuntu)
Invalid
Undecided
Unassigned
libxml2 (Baltix)
Invalid
Undecided
Unassigned
libxml2 (Ubuntu)
Fix Released
Medium
Unassigned

Bug Description

Binary package hint: libxml2

This is the second crash today in __xmlParserInputBufferCreateFilename(), the first being in rhythmbox - could the latest update have fscked it up somehow?

UPDATE: After crashes from this all over the place I tracked it down to libxml2 which seems to be being called when a gnome program needs to access the filesystem for example in the file selection dialogue.

ProblemType: Crash
Architecture: amd64
Date: Fri Oct 5 13:07:21 2007
DistroRelease: Ubuntu 7.10
ExecutablePath: /usr/bin/file-roller
NonfreeKernelModules: nvidia
Package: file-roller 2.20.0-0ubuntu1
PackageArchitecture: amd64
ProcCmdline: /usr/bin/file-roller /tmp/templates.tar.bz2
ProcCwd: /home/harry
ProcEnviron:
 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: file-roller
StacktraceTop:
 __xmlParserInputBufferCreateFilename ()
 xmlNewTextReaderFilename ()
 ?? () from /usr/lib/libgnomevfs-2.so.0
 gnome_vfs_mime_get_value ()
 gnome_icon_lookup () from /usr/lib/libgnomeui-2.so.0
Title: file-roller crashed with SIGSEGV in __xmlParserInputBufferCreateFilename()
Uname: Linux vladimir 2.6.22-12-generic #1 SMP Sun Sep 23 20:03:18 GMT 2007 x86_64 GNU/Linux
UserGroups: adm admin audio cdrom dialout dip floppy lpadmin netdev plugdev powerdev scanner video

Revision history for this message
HJMills (hjmills) wrote :
Revision history for this message
HJMills (hjmills) wrote :

Third crash - this time in gnome-session-properties.

Something is definitely broken here.

It seems to happen when I change directory in the file picker dialogue (I was browsing for the program to run on startup) but the folder varies. Sometimes one breaks, next time it might be fine and its another one that crashes it out.

Now four - it just crashed again while I was posting this in gnome-session-properties again.

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

StacktraceTop:__xmlParserInputBufferCreateFilename () from /usr/lib/libxml2.so.2
xmlReaderForDoc () from /usr/lib/libxml2.so.2
?? ()
?? ()
?? ()

Revision history for this message
Apport retracing service (apport) wrote : Symbolic threaded stack trace
Revision history for this message
Apport retracing service (apport) wrote : Stack trace with source code
Revision history for this message
HJMills (hjmills) wrote : Re: file-roller crashed with SIGSEGV in __xmlParserInputBufferCreateFilename()

This is wrong - sorry but I didn't see I needed to change the distro

Revision history for this message
HJMills (hjmills) wrote :

Great- I really am messing this whole thing up now.

The correct package is libxml2 in Ubuntu (not from Baltix and not file-roller) but file-roller crashed when using libxml2 and other programs are also crashing and always give me the libxml2 stuff.

Sorry about the mess, I hope this helps sort this out.

description: updated
Revision history for this message
Pedro Villavicencio (pedro) wrote :

Thanks for your report, this is supposed to be fixed with libxml2 2.6.30.dfsg-2ubuntu1 once the package is available in the repositories may you check and confirm that it's fixed? thanks.

Changed in file-roller:
status: New → Invalid
Changed in libxml2:
importance: Undecided → Medium
status: New → Triaged
status: New → Invalid
Revision history for this message
João Pinto (joaopinto) wrote :

I can confirm that the libxml crashes have stopped after the latest upgrade.

Revision history for this message
Matthias Klose (doko) wrote :

>I can confirm that the libxml crashes have stopped after the latest upgrade.

closing

Changed in libxml2:
status: Triaged → Fix Released
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.