[Hardy Alpha 2] Scroll Wheel problems

Bug #178199 reported by jerrylamos
This bug report is a duplicate of:  Bug #177492: EXA is balls-achingly slow. Edit Remove
2
Affects Status Importance Assigned to Milestone
Ubuntu
New
Undecided
Unassigned

Bug Description

Scrolling with mouse wheel on Hardy Alpha 2 so extremely slow nearly unusable. This is an IBM Netvista 2 gHz Pentium 4, 512mb memory. Same results on IBM Thinkpad R31 laptop.

With Gutsy, Feisty, Edgy, Dapper on this same system long screens such as internet BBC News or ABC News, scroll wheel the screen window moves up and down in sync with the wheel.

With Hardy Alpha 2, scroll the wheel. Put the mouse down. The screen moves flick......flick........flick taking nearly one second per screen update. With previous Ubuntus the update is too fast to measure. A long scroll, the screen fades to gray like when the pc is very busy.

I inadvertently moved the wheel on Desktop. The display went nuts, flashing back and forth in sections. Tried the same thing with Feisty. Nothing happens, as expected.

Is there anything I can provide? I saw /var/log/scrollkeeper.log with some strange entries, will attach.

Thanks, Jerry

Tags: likely-dup
Revision history for this message
jerrylamos (jerrylamos) wrote :

scrollkeeper log from Hardy Alpha2 showing some messages that may/may not be of use.

Jerry

Revision history for this message
jerrylamos (jerrylamos) wrote :

Noticed a whole bunch of error messages in /var/log/user.log that seem to coincide with the time for the scroll wheel actions. Attached is the log.

Also note, scrolling up and down on this launchpad bug moves in jumps spaced nearly a second apart. Gutsy scrolls evenly in sync with the wheel.

Jerry

Revision history for this message
jerrylamos (jerrylamos) wrote :

Hardy Forum to the rescue. ronacc posted "jerry look and see what video driver the DB is dumping you into , the vesa driver is a real slug about scrollling even on a fast system".

The Hardy Heron installer chose "intel" for a driver and "configured monitor" option DPMS for the screen.

Looking at /etc/X11/xorg.conf, it said to try: sudo dpkg-reconfigure -phigh xserver-xorg which doesn't work, drops right out of the procedure no matter whether "yes" or "no" is chosen on the first screen. Also tried without the -phigh whereupon the procedure drops out during the keyboard selection routine before being able to define monitor. That's a "bug", xorg.conf instructions don't work.

So I went back to what previous Ubuntu on this processor (nice being multi booted) and plugged in what previous Ubuntu installs used to use instead of Hardy installs of driver "intel" and "configured monitor":

Identifier "Intel Corporation 82845G/GL[Brookdale-G]/GE Chipset Integrated Graphics Device"
Driver "i810"

Device "Intel Corporation 82845G/GL[Brookdale-G]/GE Chipset Integrated Graphics Device"
Monitor "Hanns.G HC17"
DefaultDepth 24
SubSection "Display"
Modes "1280x1024" "1280x960" "1280x800" "1152x864" "1024x768" "832x624" "800x600" "720x400" "640x480"
EndSubSection

Voila! Screen scrolling very livable instead of useless. Video performance noticeably better. Keyboard response noticeably better.

Bug: the Ubuntu Hardy install choices use gigacycles of overhead to accomplish what previous install choices did in megacycles.

Still existing bug: On desktop, scroll wheel should just shuttle back and forth between workspaces, however whole screen jumps all over the place.

So now I have a usable Hardy Alpha 2, given manually editing xorg.conf and previous xorg.conf to copy.

However as far as testing Hardy Alpha 2, with present state of Hardy install an "ordinary user" on a pc like this one in my opinion would not use Hardy with its sluggish performance.

My current concern is that xorg.conf might be removed or that the existing driver i810 might be dropped, or that the explicit "screen" definitions not be used.

Jerry

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.