FS#4946 - Elinks has graphical artifacts

Attached to Project: Arch Linux
Opened by Eugenia Loli-Queru (Eugenia) - Sunday, 02 July 2006, 23:09 GMT
Last edited by Tobias Powalowski (tpowa) - Tuesday, 04 July 2006, 07:24 GMT
Task Type Bug Report
Category System
Status Closed
Assigned To Damir Perisa (damir.perisa)
Architecture not specified
Severity Low
Priority Normal
Reported Version 0.7.2 Gimmick
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Elinks has many artifacts when it runs on the command line which uses vesa and XGA. When it runs via X11 it works perfectly. It only shows these artifacts (e.g. on osnews.com) when you load it on a tty with vga=791 passed to the kernel.
This task depends upon

Closed by  Damir Perisa (damir.perisa)
Monday, 04 September 2006, 10:22 GMT
Reason for closing:  Works for me
Comment by Damir Perisa (damir.perisa) - Saturday, 02 September 2006, 21:20 GMT
what do you mean by artefacts? for me elinks shows exactly the same when showing ownews.net in xterm and in vc (vga=791, on radeon firegl 7800)
Comment by Eugenia Loli-Queru (Eugenia) - Saturday, 02 September 2006, 21:26 GMT
On my laptop, there are lines of text that are duplicated, depending on the scrolling taking place or the link focusing. Please try to actually use the page and scroll up and down and view its lines of text for any changes/duplications rather than on how it looks on a first sight.
Comment by Damir Perisa (damir.perisa) - Saturday, 02 September 2006, 21:33 GMT
thanx for the quick reply!

i tried to scroll and browse the page. ... everything seems ok... i was looking for artefacts like wrong displaying or similar, but didnt find any.

i suppose this is the vc speed problem i experienced some time ago ... nothing to do with elinks.
i have this, when i run a driver for the framebuffer on vc, that is slow. try to do a "dmesg" in console and in xterm and compare the speed of displaying... the vc will be much slower than the xterm... this is the problem.
you have only vga=791 or some other parameters? if you specify a framebuffer driver that is slow with your hardware, try removing this option and let it use "vesa" instead

Loading...