shotwell crashed with SIGSEGV in g_signal_emit_valist()
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| shotwell (Ubuntu) |
New
|
Undecided
|
Unassigned | ||
Bug Description
opening a picture!
ProblemType: Crash
DistroRelease: Ubuntu 15.04
Package: shotwell 0.20.2-0ubuntu3
ProcVersionSign
Uname: Linux 3.19.0-10-generic x86_64
ApportVersion: 2.17-0ubuntu1
Architecture: amd64
CurrentDesktop: Unity
Date: Tue Mar 31 22:11:45 2015
ExecutablePath: /usr/bin/shotwell
InstallationDate: Installed on 2014-09-16 (196 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
ProcCmdline: shotwell /home/username/
ProcEnviron:
LANGUAGE=it
PATH=(custom, no user)
XDG_RUNTIME_
LANG=it_IT.UTF-8
SHELL=/bin/bash
SegvAnalysis:
Segfault happened at: 0x7f4c5ef7ea40: mov (%rdi),%rax
PC (0x7f4c5ef7ea40) ok
source "(%rdi)" (0x00000000) not located in a known VMA region (needed readable region)!
destination "%rax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: shotwell
StacktraceTop:
?? () from /usr/lib/
?? () from /usr/lib/
?? () from /usr/lib/
?? () from /usr/lib/
g_signal_
Title: shotwell crashed with SIGSEGV in g_signal_
UpgradeStatus: Upgraded to vivid on 2015-03-11 (20 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
| Fabio Monteverde (fabiomonteverde) wrote | #1 |
| Apport retracing service (apport) wrote This bug is a duplicate | #2 |
| information type: | Private → Public |
| tags: | removed: need-amd64-retrace |
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 #1431121, 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.