pantheon-files crashed with SIGSEGV

StacktraceTop:
 _IO_vfprintf_internal (s=0xb6bbca20, format=<optimized out>, ap=0xbf934530 "\ba\247\t\b6\261\266\364\277Ӷ=\245̶\310֞\t(\212Ķ") at vfprintf.c:1624
 ___fprintf_chk (fp=0xb6bbca20, flag=1, format=0xb767dbec "") at fprintf_chk.c:37
 granite_services_logger_initialize (app_name=0x3 <Address 0x3 out of bounds>) at /build/buildd/granite-0.2/obj-i686-linux-gnu/lib/Services/Logger.c:249
 ?? () from /tmp/tmp_FGMCK/usr/lib/libgranite.so.0

This report is old and is not workable; marking invalid.

I just experienced this bug.

I experienced it today too

Please open new bugs for any crashes you experience.

All new bugs for this keep getting flagged as duplicates of this one? Is that still helpful or not?

Let's get a new report of this, I don't think this one is actionable and there are no recent duplicates.

I've been having this bug dozens of times, but once the bug reporting tool is done, rabbitbot insists on not taking my uploads because of incompatible dependencies. Beats me as to why they're incompatible, since Files installed and has been updating just fine. For what it's worth, I'm running Linux Mint 13 with just openbox. Attached is a crash file from Thursday. I hope that helps.

I'm trying to get a developer from my company to pitch in for Files, because this FM is awesome! Keep up the good work :)

Can we mark this bug as invalid? It doesn't seem to be any use to anyone any-more.

Actually, it's still affecting me, but the rabbit bug thing insists my
version of pantheon is old, so it won't take my bug files.

Every time pantheon crashes, this is the title the bug reporter gives.

What can I do to help with this?
On Jun 15, 2013 7:15 PM, "Ezra Sharp" <email address hidden> wrote:

> Can we mark this bug as invalid? It doesn't seem to be any use to anyone
> any-more.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1013395
>
> Title:
> pantheon-files crashed with SIGSEGV
>
> Status in Files:
> Incomplete
>
> Bug description:
> automated crash report from apport
>
> ProblemType: Crash
> DistroRelease: elementary 0.2
> Package: pantheon-files 0.1-0~r848+pkg7~precise1 [origin:
> LP-PPA-elementary-os-daily]
> ProcVersionSignature: Ubuntu 3.2.0-25.40-generic-pae 3.2.18
> Uname: Linux 3.2.0-25-generic-pae i686
> NonfreeKernelModules: wl
> ApportVersion: 2.0.1-0ubuntu8+elementary3~precise1
> Architecture: i386
> CrashCounter: 1
> CrashDB: pantheon_files
> Date: Thu Jun 14 13:50:06 2012
> ExecutablePath: /usr/bin/pantheon-files
> InstallationMedia: elementary OS 0.2 12.04 "Luna" - Build i386 LIVE
> Binary 20120501-22:56
> ProcCmdline: pantheon-files
> ProcEnviron:
> PATH=(custom, no user)
> LANG=en_US.UTF-8
> SHELL=/bin/bash
> SegvAnalysis:
> Segfault happened at: 0xb6a60b8e <vfprintf+21406>: repnz scas
> %es:(%edi),%al
> PC (0xb6a60b8e) ok
> source "%es:(%edi)" (0x20244506) not located in a known VMA region
> (needed readable region)!
> destination "%al" ok
> SegvReason: reading unknown VMA
> Signal: 11
> SourcePackage: pantheon-files
> StacktraceTop:
> ?? () from /usr/lib/i386-linux-gnu/libgtk-3.so.0
> ?? () from /usr/lib/i386-linux-gnu/libgtk-3.so.0
> ?? () from /usr/lib/i386-linux-gnu/libgtk-3.so.0
> ?? () from /usr/lib/i386-linux-gnu/libgtk-3.so.0
> ?? () from /usr/lib/i386-linux-gnu/libgtk-3.so.0
> SuspiciousXErrors:
>
> Title: pantheon-files crashed with SIGSEGV
> UpgradeStatus: No upgrade log present (probably fresh install)
> UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/pantheon-files/+bug/1013395/+subscriptions
>

Yeah and for me too, I've reported a new one here. https://bugs.launchpad.net/pantheon-files/+bug/1191446

I keep experiencing this bug and some variations of it. I wouldn't say it's invalid.

Unfortunately this crash report only says "Ooops, something went very wrong!" and does not provide any info on what exactly went wrong and how to fix that. So I'm closing this bug report; please file new reports if you encounter crashes.

So what are we supposed to do to report it properly?

This bug crashes files almost every day, usually twice a day, but I gave up on using apport to submit reports, since this is all the info it gives.

I honestly thinking of switching back to another file manager just because of this bug. It's quite irritating.

Well. It's the same bug i used to have in Luna Beta, as i see.
I'm trying to open files from the dock. (No instance is running). And it dosen't run. I click again on the icon, and the only thing i get is the Bug reporter. No more info than that.

Different hardware. Same old bug.

I had some problems with Scratch and after running command ~/.local/share$ sudo rm -R scratch-text-editor Pantheon crashed. "Share" -directory was open in Pantheon.