Ubuntu
redshift package

gtk-redshift crashed with SIGSEGV in get_locale_info.part.3()

Bug #1165031 reported by Oweoqi on 2013-04-05

32

This bug affects 6 people

Affects		Status	Importance	Assigned to	Milestone
	redshift (Ubuntu)	Confirmed	Medium	Unassigned

Bug Description

occurred on exit

ProblemType: Crash
DistroRelease: Ubuntu 13.04
Package: gtk-redshift 1.7-2ubuntu1 [modified: usr/share/icons/ubuntu-mono-light/scalable/apps/redshift-status-off.svg usr/share/icons/ubuntu-mono-light/scalable/apps/redshift-status-on.svg]
ProcVersionSignature: Ubuntu 3.8.0-16.26-generic 3.8.5
Uname: Linux 3.8.0-16-generic x86_64
NonfreeKernelModules: fglrx
ApportVersion: 2.9.2-0ubuntu5
Architecture: amd64
CrashCounter: 1
Date: Fri Apr 5 22:07:08 2013
ExecutablePath: /usr/bin/gtk-redshift
InstallationDate: Installed on 2013-02-12 (52 days ago)
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
InterpreterPath: /usr/bin/python2.7
MarkForUpload: True
PackageArchitecture: all
ProcCmdline: python /usr/bin/gtk-redshift -l -31.9530044:115.8574693
ProcEnviron:
SHELL=/bin/bash
PATH=(custom, no user)
LANG=en_AU.UTF-8
LANGUAGE=en_AU:en
XDG_RUNTIME_DIR=<set>
SegvAnalysis:
Segfault happened at: 0x520c2c: subq $0x1,(%r9)
PC (0x00520c2c) ok
source "$0x1" ok
destination "(%r9)" (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
start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0
clone () from /lib/x86_64-linux-gnu/libc.so.6
Title: gtk-redshift crashed with SIGSEGV in start_thread()
UpgradeStatus: Upgraded to raring on 2013-03-28 (7 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Tags:

Revision history for this message

Oweoqi (oweoqi) wrote on 2013-04-05:

#1

Dependencies.txt Edit (5.4 KiB, text/plain; charset="utf-8")
Disassembly.txt Edit (580 bytes, text/plain; charset="utf-8")
ProcMaps.txt Edit (40.2 KiB, text/plain; charset="utf-8")
ProcStatus.txt Edit (824 bytes, text/plain; charset="utf-8")
Registers.txt Edit (714 bytes, text/plain; charset="utf-8")
Stacktrace.txt Edit (1.4 KiB, text/plain; charset="utf-8")
ThreadStacktrace.txt Edit (2.7 KiB, text/plain; charset="utf-8")

information type:

Private → Public

Revision history for this message

Launchpad Janitor (janitor) wrote on 2013-04-26:

#2

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in redshift (Ubuntu):
status:	New → Confirmed

Revision history for this message

Apport retracing service (apport) wrote on 2013-05-11:

#3

StacktraceTop:
get_locale_info.part.3 (locale_info=<optimized out>) at ../Python/../Objects/stringlib/formatter.h:642
get_locale_info.47522 (type=<optimized out>, locale_info=<optimized out>) at ../Python/../Objects/stringlib/formatter.h:637
?? ()
doc_unhexlify.66991.5230 ()
?? ()

Revision history for this message

Apport retracing service (apport) wrote on 2013-05-11: Stacktrace.txt

#4

Stacktrace.txt Edit (1.6 KiB, text/plain)

Revision history for this message

Apport retracing service (apport) wrote on 2013-05-11: ThreadStacktrace.txt

#5

ThreadStacktrace.txt Edit (2.3 KiB, text/plain)

Changed in redshift (Ubuntu):
importance:	Undecided → Medium
summary:	- gtk-redshift crashed with SIGSEGV in start_thread() + gtk-redshift crashed with SIGSEGV in get_locale_info.part.3()
tags:	removed: need-amd64-retrace

Revision history for this message

Thomas A. F. Thorne (tafthorne) wrote on 2015-11-03:

#6

This was suggested as a possible defect for a problem that I have hit twice today. The suggested title for my problem was "redshift-gtk crashed with SIGSEGV in start_thread()" and the first time I hit it I added "when selecting Quit". I have been able to reproduce the issue but was bought here and not to my first bug.

Bug #1512705 is the on I raised earlier today. That has now been marked as a duplicate of bug #1298139 by apport. All three may be related or the same.

That suggests the bug first occurred on Exit in Ubuntu 13.

Report a bug

This report contains Public information

Everyone can see this information.

You are

Subscribing...

Edit bug mail

Other bug subscribers

Bug attachments

Add attachment

Remote bug watches

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