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#39732 - [chromium] depends on libsystemd-journal.so.0

Attached to Project: Arch Linux
Opened by kozec (kozec) - Thursday, 03 April 2014, 20:30 GMT
Last edited by Gerardo Exequiel Pozzi (djgera) - Friday, 04 April 2014, 03:16 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To No-one
Architecture x86_64
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:

/usr/lib/chromium/chromium: error while loading shared libraries: libsystemd-journal.so.0: cannot open shared object file: No such file or directory

Additional info:
33.0.1750.152-1 x86_64

So, are you people having some weird deviation, making everything dependant on Systemd? Chromium sudently depends on logging system. That doesn't even make any sense...
This task depends upon

Closed by  Gerardo Exequiel Pozzi (djgera)
Friday, 04 April 2014, 03:16 GMT
Reason for closing:  Not a bug
Comment by Dave Reisner (falconindy) - Thursday, 03 April 2014, 20:39 GMT
No, it doesn't depend directly on the journal. It's a transitive dependency that you seem to have broken. You can run 'LD_DEBUG=files chromium' to figure out what's requesting libsystemd-journal.so.

> So, are you people having some weird deviation, making everything dependant on Systemd?
This really isn't necessary.
Comment by kozec (kozec) - Thursday, 03 April 2014, 20:58 GMT
> This really isn't necessary.
I know it sounded harsh, but since that catastrophe, *every* *single* update left my system partially or complete unusable. This time it was complete and I spent my evening on it.

Anyway, thanks for your tip. With it, i found that problem is actually in pulseaudio client library, what makes even less sense.
But knowing this, I can see that I filled bug on wrong package, for what I'm sorry.

Loading...