FS#10843 - bug with xf86-video-vesa
Attached to Project:
Arch Linux
Opened by christopher rogers (godane) - Monday, 07 July 2008, 05:08 GMT
Last edited by Jan de Groot (JGC) - Friday, 18 July 2008, 20:56 GMT
Opened by christopher rogers (godane) - Monday, 07 July 2008, 05:08 GMT
Last edited by Jan de Groot (JGC) - Friday, 18 July 2008, 20:56 GMT
|
Details
Description:
there is a bug in the new xf86-video-vesa 2.0.0 that cause virtualbox not to be able to work in Xwindow. Since virtualbox uses vesa for video it will cause a lot problems with developers like me that use virtualbox almost everyday. there is a patch at the bottom of the page. The patch is for vesa.c file. debian-bugs-dist@lists.debian.org/msg538868.html"> http://www.mail-archive.com/debian-bugs-dist@lists.debian.org/msg538868.html I also have a patch that will be add to this bug report. xf86-video-vesa 2.0.0 virtualbox-modules and virtualbox-ose 1.6.2 Steps to reproduce: Have xf86-video-vesa installed on host machine. Start virtualbox and use a livecd or something with a graphical login. Aand wait for graphical login that never will come. It will just go black. |
This task depends upon
Closed by Jan de Groot (JGC)
Friday, 18 July 2008, 20:56 GMT
Reason for closing: Fixed
Additional comments about closing: Reverted to 1.3.0.
Friday, 18 July 2008, 20:56 GMT
Reason for closing: Fixed
Additional comments about closing: Reverted to 1.3.0.
debian-bugs-dist@lists.debian.org/msg538868.html"> http://www.mail-archive.com/debian-bugs-dist@lists.debian.org/msg538868.html
The bug report has been made upstream. The link's date is 06/05/2008. This bug may not get fix in awhile cause some projects are not updated for one bug. Even if its causing problems with virtualbox.
I was using vesa on the guest, and I indeed ran into this problem, but then I switched to use the virtualbox driver, and it works perfectly fine :
http://aur.archlinux.org/packages.php?ID=11816
But does this bug really happen only inside virtualbox?
FS#10855answers my question, this problem does not only exist inside virtualbox, but I am still a bit confused about the situation in this bug report.FS#10855broke with vesa 2.0. I'm running a S3 virge 4Mb video card (yes, old...)
it was working with vesa 1.3
same problem
/usr/bin/xorg: symbol lookup error: /usr/lib/xorg/modules/drivers//vesa_drv.so: undefined symbol: xf86GTFMode
Dont know if its the patch or the updated driver...