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!
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!
FS#1679 - vino: linked against libXdamage
Attached to Project:
Arch Linux
Opened by Link Dupont (link) - Sunday, 24 October 2004, 19:42 GMT
Last edited by arjan timmerman (blaasvis) - Saturday, 20 November 2004, 12:57 GMT
Opened by Link Dupont (link) - Sunday, 24 October 2004, 19:42 GMT
Last edited by arjan timmerman (blaasvis) - Saturday, 20 November 2004, 12:57 GMT
|
Detailsvino-server is linked against the library libXdamage.so.1 & libXfixes.so.3. Neither of those libraries exist on my system. I do not run Xorg 6.8.1, and I suspect that vino was compiled on a system that does. If this is the case, vino should depend on xorg >= 6.8.0, since 6.7 doesn't provide those libraries. vino does compile against 6.7, and unless libXdamage is really needed, I'd look into finding a way to not link against those libraries.
|
This task depends upon
Comment by Dale Blount (dale) -
Monday, 25 October 2004, 12:13 GMT
Arjan, the description also seems to be incorrect for vino
Comment by arjan timmerman (blaasvis) -
Saturday, 20 November 2004, 12:57 GMT
updated the description, made a patch to make configure skip the libXdamage checking so it should work now again. please test it and give feedback.
Comment by arjan timmerman (blaasvis) -
Tuesday, 23 November 2004, 14:22 GMT
ok seems to be fixed