Ubuntu
redshift package

redshift-gtk crashed with SIGSEGV in start_thread() when choosing Quit from menu

Bug #1512705 reported by Thomas A. F. Thorne
This bug report is a duplicate of:  Edit Remove
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
redshift (Ubuntu)
New
Undecided
Unassigned

Bug Description

I chose to Quit from one screen and it didn't seem to work. I went to my second display to try the action from there and the app seemed to close while I had the menu open. Shortly after that I was presented with an error report.

ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: redshift-gtk 1.8-0ubuntu6
ProcVersionSignature: Ubuntu 3.16.0-51.69~14.04.1-generic 3.16.7-ckt17
Uname: Linux 3.16.0-51-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.18
Architecture: amd64
CurrentDesktop: Unity
Date: Tue Nov 3 13:36:48 2015
ExecutablePath: /usr/bin/redshift-gtk
InstallationDate: Installed on 2015-03-12 (235 days ago)
InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1)
InterpreterPath: /usr/bin/python2.7
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/redshift-gtk
SegvAnalysis:
 Segfault happened at: 0x47c525: subq $0x1,(%rdx)
 PC (0x0047c525) ok
 source "$0x1" ok
 destination "(%rdx)" (0x00000000) not located in a known VMA region (needed writable region)!
 Stack memory exhausted (SP below stack segment)
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: redshift
StacktraceTop:
 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 start_thread (arg=0x7fcc37fff700) at pthread_create.c:312
 clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111
Title: redshift-gtk crashed with SIGSEGV in start_thread()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dialout dip lpadmin mock plugdev sambashare sudo

Revision history for this message
Thomas A. F. Thorne (tafthorne) wrote :
Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

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 #1298139, 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.

information type: Private → Public
tags: removed: need-amd64-retrace
Revision history for this message
Thomas A. F. Thorne (tafthorne) wrote :

Oh great, another bug I have raised that is marked as a duplicate of something I cannot see. Hopefully someone on this list can see if bug #1298139 is or is not a valid suggestion as a duplicate. I cannot examine it to check.

Revision history for this message
Thomas A. F. Thorne (tafthorne) wrote :

Bug #1165031 may also be related to this bug. Perhaps Bug #1165031 is also a duplicate of #1298139 or perhaps #1298139 should be marked as a duplicate of Bug #1165031 as it was raised first and is public.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
  • Duplicate of a private bug Remove
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.