void-linux / void-linux/void-packages

dino 0.4.2_2 fails to start with a missing symbolic link for a dependency on libgee-0.8.so.2

Open
#44,317 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug needs-testing
Dominant language
Shell
Stars
3.4k
Forks
2.8k
Avg merge
2d 5h
Merged PRs (30d)
299

Description

Is this a new report?

Yes

System Info

Void 6.1.29_1 x86_64 GenuineIntel uptodate hold rrFFFF

Package(s) Affected

dino-0.4.2_2

Does a report exist for this bug with the project's home (upstream) and/or another distro?

I did find the following issue for libgee, but it appears to be several years old and resolved: https://github.com/void-linux/void-packages/issues/18105

If I manually create the symbolic link, dino starts:

root@oystelle ~# cd /usr/lib
root@oystelle /u/lib# ln -s libgee-0.8.so.2.6.1 libgee-0.8.so.2
Expected behaviour

dino application should start

Actual behaviour

When I try to run dino, I get the following error for a missing library:

dino: error while loading shared libraries: libgee-0.8.so.2: cannot open shared object file: No such file or directory
Steps to reproduce

My package versions for dino and libgee:

vpm search libgee
[vpm]  Searching for: libgee (xbps-query -v -Rs libgee) 
[*] libgee-0.20.6_1         GObject collection library
[-] libgee-devel-0.20.6_1   GObject collection library - development files
[*] libgee08-0.20.6_1       GObject collection library - transitional dummy package
[-] libgee08-devel-0.20.6_1 GObject collection library - transitional dummy package
[vpm]  [xbps-query -v -Rs libgee] return code: 0 
╭─ ~ ··························································· ✔  ⬢ 18.16.0  12:38:58 
╰─ vpm search dino
[vpm]  Searching for: dino (xbps-query -v -Rs dino) 
[*] dino-0.4.2_2 Modern XMPP ("Jabber") Chat Client using GTK+/Vala
[vpm]  [xbps-query -v -Rs dino] return code: 0 

I preformed and update and still see to have the issue. Creating the symbolic link to the library manually resolves the issue.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Reproduce the failure by running dino and inspect the installed dino, libgee, and libgee08 package metadata after the reported versions are installed. Verify the dependency provides libgee-0.8.so.2 without a manual link, then confirm that dino starts normally.

Written by the indexing model from the issue text.

Assessment

Tech stack
linux
Domain
operating-systems
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.