segfault/assertion fail on Ubuntu 10.10/amd64 redshift 1.7

[adamski]

I have downloaded source package (.dsc and the two tarballs), and built a 1.7 package for my ubuntu 10.10 amd64 using dpkg-buildpackage. When I try and run redshift:

 GLib-GObject-CRITICAL **: g_type_instance_get_private: assertion `instance != NULL && instance->g_class != NULL' failed
Segmentation fault

gtk-redshift fails with the same assertion error, but no segfault.

[Jani Välimaa (wally-mageia)]

I'm getting exactly the same errors with redshift 1.7 on my Mageia Cauldron (with GLib 2.29.10 and GTK3 3.1.8).

[Jon Lund Steffensen (jonls)]

2011/7/12 Jani Välimaa <email address hidden>:
> I'm getting exactly the same errors with redshift 1.7 on my Mageia
> Cauldron (with GLib 2.29.10 and GTK3 3.1.8).

Would it be possible for one of you to provide a full back trace from gdb?

[Jani Välimaa (wally-mageia)]

Here's backtrace..

[Jani Välimaa (wally-mageia)]

Noticed that I had only geoclue libs installed, installed also other geoclue packages and after that I'm getting this:

[wally@mandi ~]$ LC_ALL=C redshift

** (process:26911): WARNING **: Metadata for error domain "geoclue-error-quark" already registered

Started Geoclue provider `Geoclue Master'.
Using provider `geoclue'.
Could not get location: Geoclue master client has no usable Position providers.
Unable to get location from provider.

[Jon Lund Steffensen (jonls)]

2011/7/12 Jani Välimaa <email address hidden>:
> Noticed that I had only geoclue libs installed, installed also other
> geoclue packages and after that I'm getting this:
>
> [wally@mandi ~]$ LC_ALL=C redshift
>
> ** (process:26911): WARNING **: Metadata for error domain "geoclue-
> error-quark" already registered
>
> Started Geoclue provider `Geoclue Master'.
> Using provider `geoclue'.
> Could not get location: Geoclue master client has no usable Position providers.
> Unable to get location from provider.

Hi Jani, thank you for the backtrace, it's very helpful. Redshift
makes a call to geoclue which fails when there are no position
provider available. However, the current redshift code does not check
for this failure which results in the segfault. I'm working on a fix
for this.
Now, for your second problem I don't have a solution right now. Others
have reported similar output in
https://bugs.launchpad.net/redshift/+bug/808006 .