redshift crashed with SIGSEGV in __libc_start_main()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
redshift (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Duplicate of bug #888661, but with the latest redshift package.
ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: redshift 1.8-0ubuntu6
ProcVersionSign
Uname: Linux 3.11.0-18-generic x86_64
ApportVersion: 2.12.5-0ubuntu2.2
Architecture: amd64
Date: Fri Apr 4 13:21:21 2014
ExecutablePath: /usr/bin/redshift
InstallationDate: Installed on 2012-05-28 (675 days ago)
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425)
MarkForUpload: True
ProcCmdline: redshift
SegvAnalysis:
Segfault happened at: 0x406bb3: mov 0x8(%rax),%rsi
PC (0x00406bb3) ok
source "0x8(%rax)" (0x00000008) not located in a known VMA region (needed readable region)!
destination "%rsi" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: redshift
StacktraceTop:
?? ()
?? ()
?? ()
__libc_start_main (main=0x402540, argc=1, ubp_av=
?? ()
Title: redshift crashed with SIGSEGV in __libc_start_main()
UpgradeStatus: Upgraded to saucy on 2013-10-08 (177 days ago)
UserGroups: adm cdrom davfs2 dip docker fuse lastfm libvirtd lpadmin plugdev sambashare sudo wireshark www-data
StacktraceTop:
?? ()
?? ()
?? ()