Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Issues with 'sway: error while loading shared libraries: libopenh264.so.4: cannot open shared object file: No such file or directory' #4633

Open
stratosgear opened this issue Oct 14, 2019 · 3 comments

Comments

@stratosgear
Copy link

@stratosgear stratosgear commented Oct 14, 2019

➜ swaymsg -t get_version
sway version 4.17.1 (2019-08-30)

Can someone suggest a debug/investigation process for an error of:

➜ sway
sway: error while loading shared libraries: libopenh264.so.4: cannot open shared object file: No such file or directory

I just rebooted and my sway session failed and it silently restarts the login process. I can logon with a separate .i3 session, but I really want my sway session back, please.

I'm on X1 carbon thinkpad (3rd gen).

Thanks

@stratosgear

This comment has been minimized.

Copy link
Author

@stratosgear stratosgear commented Oct 14, 2019

Hmmm that sway version doesn't look right. That's my i3 version.

sway -v also exits with the same error as above.

Trying to remove and reinstall openh264 results in:

➜ yay -R openh264
checking dependencies...
error: failed to prepare transaction (could not satisfy dependencies)
:: freerdp-git: removing openh264 breaks dependency 'openh264'

09:23:18 in ~ 
➜ yay -R freerdp-git 
checking dependencies...
error: failed to prepare transaction (could not satisfy dependencies)
:: wlroots: removing freerdp-git breaks dependency 'freerdp'

Is this a wlroots issue then? Should I report there?

I'm on latest arch, btw.

@stratosgear

This comment has been minimized.

Copy link
Author

@stratosgear stratosgear commented Oct 14, 2019

Fixing it manually with:

sudo su
cd /usr/lib
ln -s libopenh264.so.2.0.0 libopenh264.so.4

and rebooting. Now it works.

No idea why things like these break sometimes. I do all my package upgrades through yay!

Leaving this open, in case there is a possible/reasonable explanation.

Feel free to close otherwise!

@rkanati

This comment has been minimized.

Copy link
Contributor

@rkanati rkanati commented Oct 19, 2019

I'd guess this is an arch packaging issue, but I'm not sure.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
2 participants
You can’t perform that action at this time.