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#41787 - [weston] Does not work in VirtualBox
Attached to Project:
Community Packages
Opened by Leonardo (pq) - Tuesday, 02 September 2014, 02:58 GMT
Last edited by Sébastien Luttringer (seblu) - Friday, 26 September 2014, 09:34 GMT
Opened by Leonardo (pq) - Tuesday, 02 September 2014, 02:58 GMT
Last edited by Sébastien Luttringer (seblu) - Friday, 26 September 2014, 09:34 GMT
|
DetailsDescription:
On a new install, (virtualbox virtual machine) weston-launch failing initialization with failed to load module: /usr/lib/gbm/gbm_gallium_drm.so: No such file or directory. Probably lacking some dependencies? I cannot find the package which should contain this file. Additional info: package version: weston 1.5.0-2 |
This task depends upon
Closed by Sébastien Luttringer (seblu)
Friday, 26 September 2014, 09:34 GMT
Reason for closing: Upstream
Friday, 26 September 2014, 09:34 GMT
Reason for closing: Upstream
I'll do more tests, to see if recompiling mesa with --enable-gallium-gbm will fix it, then eventually file a regression report against mesa
weston-launch -- --backend=fbdev-backend.so
but it's not working with drm backend. I have no trace of the galium stuff you're talking about.