# Issue after gexiv upgrade

**URL:** <https://gramps.discourse.group/t/issue-after-gexiv-upgrade/9458>\
**Category:** Development\
**Created:** [May 6, 2026, 10:46am UTC](https://gramps.discourse.group/t/issue-after-gexiv-upgrade/9458 "2026-05-06T10:46:42Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![hamkg](https://yyz2.discourse-cdn.com/free1/user_avatar/gramps.discourse.group/hamkg/32/5784_2.png) [@hamkg](https://gramps.discourse.group/u/hamkg)\
**Post date:** [May 6, 2026, 10:46am UTC](https://gramps.discourse.group/t/issue-after-gexiv-upgrade/9458/1 "2026-05-06T10:46:42Z")

</div>

Gramps-6.0.8 on Slackware -current. Slackware’s gexiv2 package was recently upgraded to version 0.16.0. When I launch Gramps after that upgrade, I get a warning that the gexiv module hasn’t been loaded (see attached).

Recompiled Gramps, hoping that it would pick up the new libraries, but no change

Not particularly important, I have never tried to access exiv data from within Gramps. I guess that a simple editing of some source file could fix it, but don’t know where to look (checked a few \__init_\_.py files but couldn’t find anything related to gexiv).

 ![Screenshot at 2026-05-06 10-38-14](https://global.discourse-cdn.com/free1/uploads/gramps/original/2X/d/d839b447867a51b292830c986457c32b83245858.png)

---

<div class="post-metadata">

**Author:** ![roptat](https://avatars.discourse-cdn.com/v4/letter/r/51bf81/32.png) [@roptat](https://gramps.discourse.group/u/roptat)\
**Post date:** [May 6, 2026, 11:07am UTC](https://gramps.discourse.group/t/issue-after-gexiv-upgrade/9458/2 "2026-05-06T11:07:45Z")

</div>

I’ve had a similar issue in a different distribution. This is because gramps requires version 0.10, but the distribution does not provide it (only a newer version):

```python
gi.require_version("GExiv2", "0.10")

```

This pattern is present in `gramps/grampsapp.py`, `gramps/plugins/lib/libmetadata.py` and `gramps/plugins/gramplet/gramplet.gpr.py`. Providing GExiv2 0.10 should fix the issue.

---

<div class="post-metadata">

**Author:** ![hamkg](https://yyz2.discourse-cdn.com/free1/user_avatar/gramps.discourse.group/hamkg/32/5784_2.png) [@hamkg](https://gramps.discourse.group/u/hamkg)\
**Post date:** [May 6, 2026, 12:30pm UTC](https://gramps.discourse.group/t/issue-after-gexiv-upgrade/9458/3 "2026-05-06T12:30:41Z")

</div>

Thanks a lot, @roptat , for giving me the relevant source files. Rather than downgrading (creating issues with other applications) or keeping two versions installed, I patched those files so that they have

`gi.require_version("GExiv2", "0.16")`  
Rebuilt gramps, no more warning about unloaded module.

---

<div class="post-metadata">

**Author:** ![Nick-Hall](https://yyz2.discourse-cdn.com/free1/user_avatar/gramps.discourse.group/nick-hall/32/95_2.png) [@Nick-Hall](https://gramps.discourse.group/u/Nick-Hall)\
**Post date:** [May 6, 2026, 1:41pm UTC](https://gramps.discourse.group/t/issue-after-gexiv-upgrade/9458/4 "2026-05-06T13:41:51Z")

</div>

This was fixed in pull request [#2271](https://github.com/gramps-project/gramps/pull/2271) which has been merged and will be available in v6.1.0-beta2.

---

<div class="post-metadata">

**Author:** ![hamkg](https://yyz2.discourse-cdn.com/free1/user_avatar/gramps.discourse.group/hamkg/32/5784_2.png) [@hamkg](https://gramps.discourse.group/u/hamkg)\
**Post date:** [May 6, 2026, 3:10pm UTC](https://gramps.discourse.group/t/issue-after-gexiv-upgrade/9458/5 "2026-05-06T15:10:42Z")

</div>

Rebuilt v6.0.8 with the changes in pull request [#2271](https://github.com/gramps-project/gramps/pull/2271)

Works fine.

Thanks to the devs!

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/free1/uploads/gramps/original/1X/2ac1e712b7adf612e31ca08a55419f4cf37c0158.png) [@system](https://gramps.discourse.group/u/system)\
**Post date:** [June 5, 2026, 3:11pm UTC](https://gramps.discourse.group/t/issue-after-gexiv-upgrade/9458/6 "2026-06-05T15:11:23Z")

</div>

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.
