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#21983 - Add new dependency for chromium (avahi)

Attached to Project: Arch Linux
Opened by Ivan Sichmann Freitas (ISF) - Saturday, 04 December 2010, 20:48 GMT
Last edited by Ionut Biru (wonder) - Sunday, 05 December 2010, 18:06 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:

Chromium fails to start if avahi isn't installed, thus it should be added as a explicit dependency.

Additional info:

Chromium 8.0.552.215-1 from extra.

Steps to reproduce:

Start chromium with avahi uninstalled. It will give the following error in a terminal:
/usr/lib/chromium/chromium: error while loading shared libraries: libavahi-common.so.3: cannot open shared object file: No such file or directory

(Re)installing avahi solves the problem.
(Note that avahi isn't a explicit dependency of chromium)
This task depends upon

Closed by  Ionut Biru (wonder)
Sunday, 05 December 2010, 18:06 GMT
Reason for closing:  Not a bug
Comment by Kevin (anonymous_user) - Sunday, 05 December 2010, 01:43 GMT
Confirmed.
Comment by Ionut Biru (wonder) - Sunday, 05 December 2010, 01:48 GMT
chromium doesn't link directly to avahi.

do LD_DEBUG=files chromium > log 2>&1 and pasthe the log
Comment by Ivan Sichmann Freitas (ISF) - Sunday, 05 December 2010, 01:54 GMT
Well, aparently, yes, see line 458 of the attached log.
   chromium_log (73.6 KiB)
Comment by Attila (attila) - Sunday, 05 December 2010, 08:52 GMT
I have taken a look in my build log of chromium and there is no entry about avahi instead ldd shows that libavahi-common.so.3 and libavahi-client.so.3 be there. Therefore another option could be to rethink about why at example cups and sane (and/or other packages) has to be compiled with avahi and than see if chromium can be compiled without avahi.
Comment by Ionut Biru (wonder) - Sunday, 05 December 2010, 12:17 GMT
so all of you guys have been removing avahi from the system intentionally with pacman -Rd avahi?

the dependencies are right->gconf->gtk2->libcups->avahi
Comment by Attila (attila) - Sunday, 05 December 2010, 15:12 GMT
@Ionut The problem be not the deps for avahi.

If i do a look with ldd at chromium under opensuse than i don't see a line with avahi and it sounds funny that a browser needs avahi to work. For me therefore this is more a build than a dependency problem.
Comment by Ionut Biru (wonder) - Sunday, 05 December 2010, 15:19 GMT
@Attila do not use ldd because ldd will print soname that link to soname too

chromium doesn't not link to avahi. it does link to libcups which links to avahi.

readelf -d /usr/lib/chromium/chromium
Comment by Attila (attila) - Sunday, 05 December 2010, 17:28 GMT
@Ionut Thanks for exposing this.
Comment by Ivan Sichmann Freitas (ISF) - Sunday, 05 December 2010, 17:47 GMT
@Ionut
So it seems that it's my fault then. Sorry.

Loading...