foto doesn't start

[Tavecchio Luca]

here is from terminal:

luca@luca-K52F:~$ foto
[_LOG_LEVEL_INFO 14:58:27.897753] Application.vala:77: Foto version: 0.1
[_LOG_LEVEL_INFO 14:58:27.898028] Application.vala:79: Kernel version: 3.2.0-40-generic
[_LOG_LEVEL_FATAL 14:58:27.898133] [GLib-GIO] g_application_activate: assertion `application->priv->is_registered' failed
[_LOG_LEVEL_FATAL 14:58:27.898164] Foto will not function properly.
[_LOG_LEVEL_FATAL 14:58:27.957573] foto_album_manager_album_get_rating: assertion `self != NULL' failed
[_LOG_LEVEL_FATAL 14:58:27.957648] Foto will not function properly.
[_LOG_LEVEL_FATAL 14:58:27.961432] [Gtk] gtk_check_menu_item_set_active: assertion `GTK_IS_CHECK_MENU_ITEM (check_menu_item)' failed
[_LOG_LEVEL_FATAL 14:58:27.961477] Foto will not function properly.
Errore di segmentazione

last line means: segmentation error (or something similar)

i've tried to purge foto and reinstall it with no luck

[Mario (maxvogue)]

Stesso bug,trovata qualche soluzione?

[Erasmo Marín (erasmo-marin)]

It happened after an update... maybe it's a granite break... I have not had time to debug the app... it compile ok, but I get a segmention fault. Any help with this is welcome.

[Tavecchio Luca (tavecchio-luca)]

sorry i'm not a coder..anyway i shared the link to this bug in g+ elementary channel..hope some help will come from there!

[Carc (carcohoma)]

Could be something related to contractor/granite?

==1345== Process terminating with default action of signal 11 (SIGSEGV)
==1345== Access not within mapped region at address 0x0
==1345== at 0x72CB7B0: g_str_hash (in /lib/x86_64-linux-gnu/libglib-2.0.so.0.3200.3)
==1345== by 0x6946B2E: ??? (in /usr/lib/x86_64-linux-gnu/libgee.so.2.0.0)
==1345== by 0x6946E9B: ??? (in /usr/lib/x86_64-linux-gnu/libgee.so.2.0.0)
==1345== by 0x53CA5E1: ??? (in /usr/lib/libgranite.so.1.0.1)
==1345== by 0x53CA809: granite_widgets_contractor_menu_construct (in /usr/lib/libgranite.so.1.0.1)
==1345== by 0x437755: foto_widgets_foto_toolbar_construct (FotoToolbar.vala:128)
==1345== by 0x437C1F: foto_widgets_foto_toolbar_new (FotoToolbar.vala:47)
==1345== by 0x43920F: foto_widgets_main_window_construct (MainWindow.vala:79)
==1345== by 0x4396B1: foto_widgets_main_window_new (MainWindow.vala:54)
==1345== by 0x4125D1: foto_foto_app_real_activate (foto.vala:106)
==1345== by 0x7053EC9: ??? (in /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0.3200.3)
==1345== by 0x706C740: g_signal_emit_valist (in /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0.3200.3)
==1345== If you believe this happened as a result of a stack
==1345== overflow in your program's main thread (unlikely but
==1345== possible), you can try to increase the size of the
==1345== main thread stack using the --main-stacksize= flag.
==1345== The main thread stack size used in this run was 8388608.
==1345==
==1345== HEAP SUMMARY:
==1345== in use at exit: 16,298,247 bytes in 16,978 blocks
==1345== total heap usage: 398,092 allocs, 381,114 frees, 58,248,324 bytes allocated
==1345==
==1345== LEAK SUMMARY:
==1345== definitely lost: 7,246 bytes in 18 blocks
==1345== indirectly lost: 11,056 bytes in 346 blocks
==1345== possibly lost: 14,748,747 bytes in 6,234 blocks
==1345== still reachable: 1,531,198 bytes in 10,380 blocks
==1345== suppressed: 0 bytes in 0 blocks
==1345== Rerun with --leak-check=full to see details of leaked memory
==1345==
==1345== For counts of detected and suppressed errors, rerun with: -v
==1345== Use --track-origins=yes to see where uninitialised values come from
==1345== ERROR SUMMARY: 190 errors from 58 contexts (suppressed: 2 from 2)
fish: Job 1, “valgrind foto ” terminated by signal SIGKILL (Forced quit)

[Carc (carcohoma)]

Looks like that class(ContractorMenu) has been deprecated, not sure what's the alternative though.

http://bazaar.launchpad.net/~elementary-pantheon/granite/granite/view/head:/lib/Widgets/ContractorMenu.vala

[Erasmo Marín (erasmo-marin)]

If this is the problem, I will remove this menu for a fast fix. If there is no replacement, I will do my own menu in a popover as in mockups.

Thank you very much!!

[Tom Beckmann (tombeckmann)]

In case this didn't fix it, we had similar crashes with newer gtk versions already. Those were related to GtkApplication methods being called at the wrong place. Mostly set_application on the main window from the constructor instead of the activate callback. I haven't checked the code though.

[Erasmo Marín (erasmo-marin)]

The hot fix is already committed, I tried removing the contractor menu and it worked. The deb package is available now also. Please test it and tell me if you see any problem. Again, thanks for the help.

[Tavecchio Luca (tavecchio-luca)]

now it works!

[Tom Beckmann (tombeckmann)]

I guess that's not the best place to say this, but I now had a quick look at the code. You should remove the call to activate in the constructor, it may lead to crashes if the application is not registered fast enough and it generates this warning about the application_id. Apparently this is not related to this bug though ;)

[Erasmo Marín (erasmo-marin)]

Ok, thanks, I will open a new bug to remember fixing it :)