Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#80121 - [pdfpc] PLEASE ENTER SUMMARY

Attached to Project: Arch Linux
Opened by Artemis (Artemis) - Tuesday, 31 October 2023, 17:08 GMT
Last edited by Antonio Rojas (arojas) - Tuesday, 31 October 2023, 19:29 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To No-one
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
pdfpc does not start with this error message:
pdfpc: error while loading shared libraries: libmarkdown.so.2: cannot open shared object file: No such file or directory

I just ran a full upgrade.

Additional info:
* package version: pdfpc 4.6.0-2
This task depends upon

Closed by  Antonio Rojas (arojas)
Tuesday, 31 October 2023, 19:29 GMT
Reason for closing:  Not a bug
Comment by Artemis (Artemis) - Tuesday, 31 October 2023, 17:09 GMT
I'm sorry, I forgot to provide a title for the bug report.
Comment by Artemis (Artemis) - Tuesday, 31 October 2023, 18:28 GMT
I seems that the problem was that I had the package `discount` (a Markdown implementation) installed which provides libmarkdown.so.3.

Since nothing depended on `discount` I uninstalled it and now pdfpc runs fine.
Comment by loqs (loqs) - Tuesday, 31 October 2023, 18:36 GMT
> I seems that the problem was that I had the package `discount` (a Markdown implementation) installed which provides libmarkdown.so.3.
That should have been fixed in pdfpc 4.6.0-2 by statically linking to discount 2 [1]?

[1]: https://gitlab.archlinux.org/archlinux/packaging/packages/pdfpc/-/commit/aa30f751916e71d422424495a361f34f35555cd2
Comment by Artemis (Artemis) - Tuesday, 31 October 2023, 18:40 GMT
It is weird. I just checked and I installed 4.6.0-2 in the end of August (and had not used it since).
For testing I installed discount again and the issue does not reappear, so maybe some stale configuration or something like that, that was fixed by removing discount.

Loading...