Community Packages

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#69038 - [electron] cannot find libilbc.so.2 after major libilbc update.

Attached to Project: Community Packages
Opened by Lukas (klank123) - Sunday, 20 December 2020, 01:58 GMT
Last edited by Doug Newgard (Scimmia) - Sunday, 20 December 2020, 02:08 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To No-one
Architecture All
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
After updating libilbc from 2.0.2-5 to 3.0.3-1 both the electron(11.1.0-2) and electron9(9.4.0-2) packages stop working.
I'm suspecting this effects all versions of electron. Running two electron packages (discord & code) both exit with an error stating libilbc.so.2 doesn't exist.
Because of the major release of libilbc 3 /lib/libilbc.so.2 does no longer exist and is replaced by /lib/libilbc.so.3
I worked around the issue by symlinking /lib/libilbc.so.2 to /lib/libilbc.so.3 which seems to be working fine, but I do not know if this has any side effects yet.
I think a more appropriate work around would be the addition of a libilbc2 package and setting that as the dependency for electron and other affected packages.

Changelog from libilbc: https://github.com/TimothyGu/libilbc/releases/tag/v3.0.1 (This is for the breaking changes for the major release)

Additional info:
electron 11.1.0-2
electron9 9.4.0-2
libilbc 2.0.2-5 > libilbc 3.0.3-1

also: discord using electron & code using electron9

Steps to reproduce:
update libilbc from 2.0.2-5 to 3.0.3-1 and try to run any electron application.
This task depends upon

Closed by  Doug Newgard (Scimmia)
Sunday, 20 December 2020, 02:08 GMT
Reason for closing:  Duplicate
Additional comments about closing:   FS#69037 
Don't do that again

Loading...