redshift and gtk-redshift crash with memory violation error

Bug #919712 reported by Andreas
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Redshift
New
Undecided
Unassigned

Bug Description

When I try to start redshift without arguments, this happens:

andreas@localhost:~$ gtk-redshift
** Message: a new manager occured at org.globalmenu.manager, :1.6

(process:18561): GLib-GObject-CRITICAL **: g_type_instance_get_private: assertion `instance != NULL && instance->g_class != NULL' failed
andreas@localhost:~$ redshift

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

(Speicherzugriffsfehler = memory access violation)

So far I only tried the version available in the official repsoitories. I'm using 3.0.0-14-generic on Ubuntu 11.10, redshift 1.7.

OK, just found out, that the cl version works as soon as i provide lat/long informations with it. Same for the gtk version.
For new users it would probably be helpfull if above error message did'nt occur when not providing location information.

Andreas (andreas-weiden)
description: updated
description: updated
Revision history for this message
Jon Lund Steffensen (jonls) wrote :

This is probably not a bug in redshift. Can you compile redshift with debug information and get a proper backtrace?

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.