Geeqie crashes like this immediately after opening whether or not I pass it any arguments. I tried removing ~/.config/geeqie, but this didn't help.
ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: geeqie 1:1.0-10.1build1
ProcVersionSignature: Ubuntu 3.5.0-15.23-generic 3.5.4
Uname: Linux 3.5.0-15-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.5.2-0ubuntu4
Architecture: amd64
CrashCounter: 1
Date: Thu Sep 27 21:22:18 2012
ExecutablePath: /usr/bin/geeqie-standard
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425)
ProcCmdline: geeqie wut.png
ProcEnviron:
SHELL=/bin/bash
TERM=screen
PATH=(custom, user)
LANG=en_US.UTF-8
SegvAnalysis:
Segfault happened at: 0x44734a: movsbl 0x0(%rbp),%edx
PC (0x0044734a) ok
source "0x0(%rbp)" (0x00000000) not located in a known VMA region (needed readable region)!
destination "%edx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: geeqie
StacktraceTop:
?? ()
?? ()
?? ()
g_main_dispatch (context=0x18c6050) at /build/buildd/glib2.0-2.33.14/./glib/gmain.c:2715
g_main_context_dispatch (context=context@entry=0x18c6050) at /build/buildd/glib2.0-2.33.14/./glib/gmain.c:3219
Title: geeqie-standard crashed with SIGSEGV in g_main_dispatch()
UpgradeStatus: Upgraded to quantal on 2012-09-19 (9 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1056532, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.