pantheon-files crashed with SIGSEGV in _IO_vfprintf_internal()

Bug #1129817 reported by Simeon
84
This bug affects 8 people
Affects Status Importance Assigned to Milestone
Files
Expired
High
Unassigned

Bug Description

STarted Elementary OS and plugged in a usb drive. Then Files crashed.

ProblemType: Crash
DistroRelease: elementary OS 0.2
Package: pantheon-files 0.1-0~r1107+pkg10~precise1 [origin: LP-PPA-elementary-os-daily]
ProcVersionSignature: Ubuntu 3.2.0-37.58-generic 3.2.35
Uname: Linux 3.2.0-37-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.0.1-0ubuntu17.1+elementary3~precise1
Architecture: amd64
CrashDB: pantheon_files
Date: Tue Feb 19 06:37:29 2013
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/pantheon-files
GsettingsChanges:

InstallationMedia: elementary OS 0.2 "Luna" - Beta 1 amd64 (20121114)
MarkForUpload: True
ProcCmdline: pantheon-files /media/SANSA\ CLIPP
ProcEnviron:
 PATH=(custom, no user)
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7fc84b0793b1 <vfprintf+10737>: repnz scas %es:(%rdi),%al
 PC (0x7fc84b0793b1) ok
 source "%es:(%rdi)" (0x0000006c) not located in a known VMA region (needed readable region)!
 destination "%al" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: pantheon-files
StacktraceTop:
 vfprintf () from /lib/x86_64-linux-gnu/libc.so.6
 __vsnprintf_chk () from /lib/x86_64-linux-gnu/libc.so.6
 ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3
 ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3
 dbus_set_error () from /lib/x86_64-linux-gnu/libdbus-1.so.3
Title: pantheon-files crashed with SIGSEGV in vfprintf()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
XsessionErrors: gnome-session[5624]: WARNING: Could not launch application 'gdu-notification-daemon-pantheon.desktop': Unable to start application: Kindprozess »/usr/lib/gnome-disk-utility/gdu-notification-daemon« konnte nicht ausgeführt werden (Datei oder Verzeichnis nicht gefunden)

Revision history for this message
Simeon (simeon5) wrote :
Revision history for this message
RabbitBot (rabbitbot-a) wrote :

StacktraceTop:
 _IO_vfprintf_internal (s=<optimized out>, format=<optimized out>, ap=<optimized out>) at vfprintf.c:1630
 ___vsnprintf_chk (s=0x7fffa4707710 "", maxlen=<optimized out>, flags=1, slen=<optimized out>, format=0x7fc84ac1bb7c "%s", args=0x7fffa4707bb8) at vsnprintf_chk.c:65
 ?? () from /tmp/apport_sandbox_Bn3tTG/lib/x86_64-linux-gnu/libdbus-1.so.3
 ?? () from /tmp/apport_sandbox_Bn3tTG/lib/x86_64-linux-gnu/libdbus-1.so.3
 dbus_set_error () from /tmp/apport_sandbox_Bn3tTG/lib/x86_64-linux-gnu/libdbus-1.so.3

Revision history for this message
RabbitBot (rabbitbot-a) wrote : Stacktrace.txt
Revision history for this message
RabbitBot (rabbitbot-a) wrote : ThreadStacktrace.txt
summary: - pantheon-files crashed with SIGSEGV in vfprintf()
+ pantheon-files crashed with SIGSEGV in _IO_vfprintf_internal()
tags: removed: need-amd64-retrace
Cody Garver (codygarver)
Changed in pantheon-files:
status: New → Confirmed
importance: Undecided → Medium
milestone: none → luna-beta3
information type: Private → Public
Cody Garver (codygarver)
Changed in pantheon-files:
importance: Medium → High
Revision history for this message
Julián Unrrein (junrrein) wrote :

This seems to have been retraced without having libdbus-glib-1-2-dbg installed.

A backtrace with the missing debug info would be more helpful.

Revision history for this message
Simeon (simeon5) wrote :

Is there a way to recreate the crash or rerun the backtrace?

Revision history for this message
Julián Unrrein (junrrein) wrote :

I cannot reproduce this crash. The only way to recreate this is to make Files crash under the same conditions.

It is not possible to rerun the backtrace. When the original backtracing was run, the CoreDump.gz file was removed from the bug report (this is done because it is a memory dump - it may contain confidential info). Without that file, there is no way to do it again.

Revision history for this message
Cody Garver (codygarver) wrote :

Needs a new report from Isis

Changed in pantheon-files:
milestone: isis-beta1 → none
status: Confirmed → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for Files because there has been no activity for 60 days.]

Changed in pantheon-files:
status: Incomplete → Expired
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.