file crashed with SIGSEGV

Bug #164858 reported by Aurel Branzeanu
8
Affects Status Importance Assigned to Milestone
file (Ubuntu)
Invalid
Medium
Basilio Kublik

Bug Description

Binary package hint: file

found this crash in /var/crash after a freeze

ProblemType: Crash
Architecture: i386
Date: Sat Nov 24 15:24:26 2007
Dependencies:
 libgcc1 1:4.2.1-5ubuntu4
 libmagic1 4.21-1
 gcc-4.2-base 4.2.1-5ubuntu4
 zlib1g 1:1.2.3.3.dfsg-5ubuntu2
 libc6 2.6.1-1ubuntu10
DistroRelease: Ubuntu 7.10
ExecutablePath: /usr/bin/file
NonfreeKernelModules: cdrom
Package: file 4.21-1
PackageArchitecture: i386
ProcCmdline: file /home/thunder/Desktop/Drivers/CUPS/cups-1.3.3/templates/et/trailer.tmpl
ProcCwd: /
ProcEnviron:
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=en_US.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: file
StacktraceTop:
 ?? () from /lib/tls/i686/cmov/libc.so.6
 ?? ()
 ?? ()
 ?? ()
 ?? ()
Title: file crashed with SIGSEGV
Uname: Linux thunder-mobile 2.6.22-14-generic #1 SMP Sun Oct 14 23:05:12 GMT 2007 i686 GNU/Linux
UserGroups: adm admin audio cdrom dialout dip fax floppy fuse lpadmin netdev plugdev powerdev scanner tape users video

Revision history for this message
Aurel Branzeanu (thunder-riscom) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:?? () from /lib/tls/i686/cmov/libc.so.6
?? ()
?? ()
?? ()
?? ()

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
Basilio Kublik (sourcercito) wrote :

Hi there
Thanks for your bug report. Please try to obtain a backtrace http://wiki.ubuntu.com/DebuggingProgramCrash and attach the file to the bug report. This will greatly help us in tracking down your problem.

Thanks in advance

Changed in file:
assignee: nobody → sourcercito
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 file:
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.