imwheel crashed with SIGSEGV when starting with --config
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
imwheel (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
Fresh install, ran "imwheel", then "imwheel --config".
ProblemType: Crash
DistroRelease: Ubuntu 16.04
Package: imwheel 1.0.0pre12-12
ProcVersionSign
Uname: Linux 4.4.0-4-generic x86_64
ApportVersion: 2.20-0ubuntu3
Architecture: amd64
CurrentDesktop: XFCE
Date: Sat Feb 20 22:39:00 2016
ExecutablePath: /usr/bin/imwheel
InstallationDate: Installed on 2015-10-19 (125 days ago)
InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422.1)
ProcCmdline: imwheel --config
SegvAnalysis:
Segfault happened at: 0x563bb0ed8d99: mov 0x8(%rax),%rdx
PC (0x563bb0ed8d99) ok
source "0x8(%rax)" (0x00000008) not located in a known VMA region (needed readable region)!
destination "%rdx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: imwheel
StacktraceTop:
?? ()
?? ()
?? ()
?? ()
__libc_start_main (main=0x563bb0e
Title: imwheel crashed with SIGSEGV in __libc_start_main()
UpgradeStatus: Upgraded to xenial on 2015-12-30 (53 days ago)
UserGroups: adm cdrom dip fuse kvm lpadmin nopasswdlogin 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 #982432, 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.