Scroll wheel doesn't scroll in AbiWord

[joehill]

I'm new to using AbiWord so I don't know if this is a new issue with Precise. Scrolling the scroll wheel has no effect except to focus the window if not already focused. My scroll wheel is pretty standard and works fine in other applications.

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: abiword 2.9.2+svn20120213-1
ProcVersionSignature: Ubuntu 3.2.0-19.30-generic 3.2.11
Uname: Linux 3.2.0-19-generic i686
ApportVersion: 1.94.1-0ubuntu2
Architecture: i386
Date: Tue Mar 20 12:53:39 2012
ProcEnviron:
 LANGUAGE=en_US:en
 TERM=xterm
 PATH=(custom, user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: abiword
UpgradeStatus: Upgraded to precise on 2012-03-19 (1 days ago)

[penalvch (penalvch)]

joehill, thank you for reporting this and helping make Ubuntu better. Please execute the following command, as it will automatically gather debugging information, in a terminal:
apport-collect 960089

As well, please attach all relevant information noted in https://wiki.ubuntu.com/DebuggingMouseDetection .

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Bryce Harrington (bryce)]

[misfiled]

[bugbot (bugbot)]

We're closing this bug since there has not been a response from the original reporter. However, the issue still exists please feel free to reopen with the requested information. If you're not the original reporter, we'd prefer you file a new bug report.

Some tips:

  * Report X.org bugs via the command: `ubuntu-bug xorg`

  * Test against the latest development Ubuntu. http://cdimage.ubuntu.com/daily-live/
    Bugs marked as affecting the development version tend to get priority attention.

  * The `xdiagnose` utility has functionality for enabling debugging and
    analyzing a few common X problems.

  * Tag your bugs with the Ubuntu versions you have reproduced the issue in.

  * See https://wiki.ubuntu.com/X/Reporting for tips on writing good bug reports.

[belovedmonster (jd-hartland)]

I've been trying out 12.04 in Virtualbox and this bug is very much real for me.

[IMBJR (imbjr)]

I've tried 12.04 via USB stick and can confirm that Abiword will not honour the scrollwheel input unless the mouse cursor is over the scrollbar.

[Raphael Isemann (teemperor)]

Same problem here with the two-finger-scrolling on a Touchpad with an Asus EEE R105.

[ReonToerien (rztrzt)]

Can confirm this in 12.04, using a wired usb mouse.

[dav2dev (dav2dev)]

this problem is very annoying, and it is not due to a specific mouse or touchpad, because if you hover over the scrollbar, you can then scroll the page.

Why is this bug set as Incomplete?

[msevior (msevior-gmail)]

Dear Christopher and canoncial,

It iflls me with frustration that Canonical chose to distribute our
development version of abiword, abiword-2.9.2 with your 12.04 LTS
distribution. This was done without any consultation with the abiword
community AT ALL. Please revert to version 2.8.6. Failing this please
advise how we will be able to support our users on Ubuntu as Canoncial
does not release updates either.

Best regards,

Martin Sevior

On Wed, Jun 27, 2012 at 9:58 PM, Christopher M. Penalver
<email address hidden> wrote:
> ** This bug is no longer a duplicate of bug 991399
> laptop touchpad vertical scrolling doesn't work in abiword
>
> ** Project changed: abiword => null
>
> ** Changed in: null
> Status: New => Invalid
>
> --
> You received this bug notification because you are a member of AbiWord
> Stable Builds, which is subscribed to AbiWord.
> https://bugs.launchpad.net/bugs/960089
>
> Title:
> Scroll wheel doesn't scroll in AbiWord
>
> Status in NULL Project:
> Invalid
> Status in “xserver-xorg-input-synaptics” package in Ubuntu:
> Incomplete
>
> Bug description:
> I'm new to using AbiWord so I don't know if this is a new issue with
> Precise. Scrolling the scroll wheel has no effect except to focus the
> window if not already focused. My scroll wheel is pretty standard and
> works fine in other applications.
>
> ProblemType: Bug
> DistroRelease: Ubuntu 12.04
> Package: abiword 2.9.2+svn20120213-1
> ProcVersionSignature: Ubuntu 3.2.0-19.30-generic 3.2.11
> Uname: Linux 3.2.0-19-generic i686
> ApportVersion: 1.94.1-0ubuntu2
> Architecture: i386
> Date: Tue Mar 20 12:53:39 2012
> ProcEnviron:
> LANGUAGE=en_US:en
> TERM=xterm
> PATH=(custom, user)
> LANG=en_US.UTF-8
> SHELL=/bin/bash
> SourcePackage: abiword
> UpgradeStatus: Upgraded to precise on 2012-03-19 (1 days ago)
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/null/+bug/960089/+subscriptions

[Jeremy Bícha (jbicha)]

 abiword (2.9.2+svn20120603-2) unstable; urgency=low

   * build verbosity increased with --disable-silent-rules
   * lintian-overrides:
     + 'hardening-no-fortify-functions' (false-positives).
     + 'dev-pkg-without-shlib-symlink' (libabiword-2.9.so is a library,
       not a symlink).
   * new patches:
     + format-hardening.patch to avoid FTBFS on --with-gtk2 build.
     + fix-wheel-scrolling.patch (Closes: #672149).
     + fix-paste.patch (backported) with fix for
       "Crash on unicode character paste" (Closes: #681060).
     + no-dbl-buf.patch to disable double buffering in order to prevent
       crash on 'Paste Unformatted'.

[Erick Brunzell (lbsolost)]

This really should reflect that the bug is fixed only in Quantal.

Precise is still using abiword '(2.9.2+svn20120213-1)' and is therefore still broken. (And the bug was originally filed against DistroRelease: Ubuntu 12.04).

I've tested the Quantal final version in both Ubuntu Precise and Xubuntu Precise using the procedure here:

http://ubuntuforums.org/showthread.php?t=2074321

But only experienced testers should try that because applying more than the abiword updates will undoubtedly blow up a users Precise :^(

Besides asking for help with this at the forums I've begged for help in bug 1069634 where I said, "I really need some dev help with this", and also here:

https://bugs.launchpad.net/ubuntu/+source/abiword/+bug/1019621/comments/36

I've been a dedicated iso/upgrade tester since 2008 but I'm in over my head here and really need some hands-on help, not just advice. I suffer from numerous medical deficits, but I'm not stupid - my abilities are just limited - like I cant use IRC chat.

In this case I recognize a need, and I have the will to try and fix the problem, but I lack the ability - so please help.

I think I could provide most of the info requested here:

https://wiki.ubuntu.com/StableReleaseUpdates#SRU_Bug_Template

Not so much about regression potential though, even though I see no problems with the Xubuntu and Ubuntu upgrades I mentioned previously, but maybe some package that's upgraded in that process effects an app that I don't use?

Anyway, I see that Jeremy Bicha is subscribed and I know from past experiences that he listens so hopefully he'll know how to change this to:

Precise >>> Confirmed
Quantal >>> Fix Released

Because that is accurate.

And I'm subscribing 'ubuntu-sru' because Ubuntu 12.04 is a 5 year LTS, Xubuntu 12.04 is a 3 year LTS which ships abiword as a native app, and we should not be shipping a broken app in our repos for that length of time unless upgrading to the Quantal version presents an actual regression potential.

I'll be glad to perform any requested tests, preferably with an actual written test-case, but I really need some hands-on help here ;^)

Rather off-topic but the current Quantal version of abiword also fixes bug 1019621 along with many upstream Debian bugs reflected in the Quantal abiword changelog - I'm just not smart enough to figure out exactly what upstream change fixed that bug.

[Erick Brunzell (lbsolost)]

Please see:

https://bugs.launchpad.net/ubuntu/+source/abiword/+bug/1019621/comments/39

While the two bugs are not true duplicates the testing procedure is identical and, long story short, using the Quantal version in Precise is IMHO not quite stable enough to be considered for an SRU :^(

[penalvch (penalvch)]

Marking Triaged for Precise, due to Quantal Fix Released.

[Steve Langasek (vorlon)]

The Precise Pangolin has reached end of life, so this bug will not be fixed for that release