Redshift crashes at startup

Bug #893654 reported by tdn
28
This bug affects 6 people
Affects Status Importance Assigned to Milestone
redshift (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

I have redshift start when I log in.
It always crashes:
2011-11-22T16:44:40.798380+01:00 malbec.vineyard.sikkerhed.org kernel: [ 71.730926] redshift[2688]: segfault at 0 ip 00007f215032e9c1 sp 00007fff1f69b490 error 4 in libgeoclue.so.0.0.0[7f2150324000+14000]

For some reason it keeps working though -- i.e. the redish color stays on the screen. (maybe because gtk-redshift stays up?)

ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: redshift 1.7-0ubuntu1
ProcVersionSignature: Ubuntu 3.0.0-13.22-generic 3.0.6
Uname: Linux 3.0.0-13-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 1.23-0ubuntu4
Architecture: amd64
Date: Tue Nov 22 16:46:03 2011
InstallationMedia: Kubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111011)
ProcEnviron:
 LANGUAGE=en_DK:en
 PATH=(custom, user)
 LANG=en_DK.UTF-8
 SHELL=/bin/zsh
SourcePackage: redshift
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
tdn (spam-thomasdamgaard) wrote :
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in redshift (Ubuntu):
status: New → Confirmed
Revision history for this message
Mélodie (meets) wrote :

Hi,

In Ubuntu 12.04.2 it also crashes at start.

***********

$ redshift

(process:2403): GLib-GObject-CRITICAL **: g_type_instance_get_private: assertion `instance != NULL && instance->g_class != NULL' failed
Erreur de segmentation (core dumped)

**********

$ gtk-redshift

(process:2739): GLib-GObject-CRITICAL **: g_type_instance_get_private: assertion `instance != NULL && instance->g_class != NULL' failed

**********

Thanks if it can be fixed.

Regards,
Mélodie

Revision history for this message
Daniel Hahler (blueyed) wrote :

You are probably missing the geoclue-hostip package.

See bug #868904.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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