search

L1L1 / cardpeek

Automatically exported from code.google.com/p/cardpeek
Other
454 stars 117 forks source link

Can't start on MacOS when built using GTK+ #50

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. Using MacOS, compile cardpeek using GTK+3 3.14.0
2. Launch cardpeek
3. See it fail

What is the expected output? What do you see instead?
cardpeek should start

What version of the product are you using? On what operating system?
MacOS 10.9.5, XQuartz 2.8.1_beta1, curl 7.38.0, lua 5.2.3, glib 2.42.0

Please provide any additional information below.
cardpeek was working fine using GTK+3 3.12.2

Original issue reported on code.google.com by mdeletr...@betomorrow.com on 26 Sep 2014 at 9:30

GoogleCodeExporter commented 9 years ago 
Ooops, sorry, a shortcut sent the issue before I finished typign the title 
which should be :

Can't start on MacOS when built using GTK+3 3.14.0

Original comment by mdeletr...@betomorrow.com on 26 Sep 2014 at 9:32

GoogleCodeExporter commented 9 years ago 
Here is console output, it may help you ;)

Original comment by mdeletr...@betomorrow.com on 26 Sep 2014 at 9:40

Attachments:

GoogleCodeExporter commented 9 years ago 
I was able to reproduce the issue after upgrading to GTK+ 3.14.0

It seems that this is caused by some GTK+ 2 code that has become obsolete in 
GTK+ 3.14.0. It's going to be a pain to fix :-(

Original comment by L...@gmx.com on 30 Sep 2014 at 7:40

GoogleCodeExporter commented 9 years ago 
Sorry about that !

Original comment by celine.d...@gmail.com on 1 Oct 2014 at 10:05

GoogleCodeExporter commented 9 years ago 
I have managed to get cardpeek working under GTK+ 3.14.0, with some changes in 
the source code. 

You can use the attached patch to try as well.

Also, for some reason, I got the following error while running cardpeek:
(cardpeek:6010): GLib-GIO-ERROR **: Settings schema 
'org.gtk.Settings.FileChooser' is not installed
To fix it I had to run "glib-compile-schemas" with the adequate path 
description. This was probably a configuration issue with my system, but I'm 
reporting it it here for completeness.

Original comment by L...@gmx.com on 1 Oct 2014 at 7:42

Attachments:

GoogleCodeExporter commented 9 years ago 
I will close this issue which seems to be fixed in the SVN now.

Original comment by L...@gmx.com on 16 Nov 2014 at 9:32