After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 610304 - extension renaming is causing crashes
extension renaming is causing crashes
Status: RESOLVED OBSOLETE
Product: gthumb
Classification: Other
Component: general
2.11.x
Other Linux
: Normal normal
: ---
Assigned To: Paolo Bacchilega
Paolo Bacchilega
: 610810 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2010-02-17 20:37 UTC by Michael Chudobiak
Modified: 2015-12-17 15:31 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Michael Chudobiak 2010-02-17 20:37:36 UTC
I think some extensions were renamed or moved recently.

Now in my extensions menu, I see TWO entries for "Audio/Video support". This happens with the "EXIF" one too.

I disabled all possible extensions, and then started re-enabling "Audio/Video support". Enabling it once is OK, but enabling both entries causes a crash (backtrace below). Enabling the EXIF extension twice is OK, oddly.

I deleted and re-cloned my git repo, so it is fresh.

Something needs to check the validity of the enabled extensions, I guess.


Thread 1 (Thread 0x7ffff7fc17e0 (LWP 9406))

  • #0 gth_type_spec_create_object
    at gth-main.c line 82
  • #1 gth_main_get_registered_objects
    at gth-main.c line 968
  • #2 file_metadata_ready_cb
    at gth-browser.c line 4461
  • #3 qam_metadata_ready_cb
    at gth-metadata-provider.c line 461
  • #4 query_metadata_done
    at gth-metadata-provider.c line 171
  • #5 check_read_metadata_thread
    at gth-metadata-provider.c line 248
  • #6 ??
    from /lib64/libglib-2.0.so.0
  • #7 g_main_context_dispatch
    from /lib64/libglib-2.0.so.0
  • #8 ??
    from /lib64/libglib-2.0.so.0
  • #9 g_main_loop_run
    from /lib64/libglib-2.0.so.0
  • #10 gtk_main
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #11 main
    at main.c line 438


- Mike
Comment 1 Paolo Bacchilega 2010-02-18 10:50:48 UTC
you have to delete /usr/lib/gthumb/extensions and reinstall again.
Comment 2 Michael Chudobiak 2010-02-18 12:49:34 UTC
OK, that fixes it - but won't this causes problems for anyone who upgrades from 2.11.1 to 2.11.2?

- Mike
Comment 3 Paolo Bacchilega 2010-02-19 09:41:15 UTC
(In reply to comment #2)
> OK, that fixes it - but won't this causes problems for anyone who upgrades from
> 2.11.1 to 2.11.2?
> 
> - Mike

You are right.  

This could be avoided in three ways

1) adding the version in the installation folder, for example /usr/lib/gthumb/extensions/2.11.2, 

2) adding a new field in the .extension file that describes the required gthumb version, 

3) adding a note in the release notes that the user has to delete the extensions folder before installing again.  

At the moment I'm not sure which strategy is the best.
Comment 4 Michael Chudobiak 2010-02-19 12:56:00 UTC
I would suggest a different approach, adding 2 fields to the .extension files:


1) In the gstreamer plugin file you could have:

permanently_replaces = gstreamer_original, gstreamer_prototype, mplayer_plugin

This could be used in the case of renamed extensions, or where one plugin totally replaces another. This would hide the old extensions in the extension list, permanently.


2) In the "mikes_folder_centric_photo_importer" plugin file you could have

optionally_replaces = photo_importer

In this case, if the user enabled mikes_folder_centric_photo_importer, the standard photo_importer would be disabled (but still appear in the extensions list). It would also disable any other plugins with "optionally_replaces = photo_importer", like bobs_super_simple_importer.

This allows several different plugins to cover the same function. A maximum of 1 of these plugins would be enabled at a time.


- Mike
Comment 5 Michael Chudobiak 2010-02-23 14:55:03 UTC
*** Bug 610810 has been marked as a duplicate of this bug. ***
Comment 6 Michael Chudobiak 2015-12-17 15:31:01 UTC
Marking as obsolete, as this was reported for a now-unsupported version and no recent activity has occurred. 

Please feel free to reopen this bug report if the problem still occurs with a current version of gThumb.