FS#392 - w3m giving errors in X

Attached to Project: Arch Linux
Opened by Scott Robbins (scottro111) - Sunday, 18 January 2004, 22:37 GMT
Last edited by dorphell (dorphell) - Sunday, 18 January 2004, 23:43 GMT
Task Type Bug Report
Category Packages: Current
Status Closed
Assigned To dorphell (dorphell)
Architecture not specified
Severity Very Low
Priority Normal
Reported Version 0.6 Widget
Due in Version Undecided
Due Date Undecided
Percent Complete 10%
Votes 0
Private No

Details

There was a similar issue with this some time ago in Gentoo Linux.
If one starts w3m in an Xterminal the following appears

***debug [lib/liblow.c(204];
VC: 0
*** err [lib/liblow.c(372)];
Oh oh, it's an error! possibly I die!

If one pages down, this is repeated and the text becomes garbled.

Running it with the -no-mouse option works. It also works in console.

In Gentoo it turned out to be connected with GPM. I don't know how it was solved, however.

This task depends upon

Closed by  dorphell (dorphell)
Tuesday, 27 January 2004, 22:40 GMT
Reason for closing:  Deferred
Comment by dorphell (dorphell) - Sunday, 18 January 2004, 23:42 GMT
Yes gpm is annoying. The current release builds improperly. If we want to resolve this issue we can do 1 of 2 things.

a. downgrade gpm to 1.19.x (not a nice option though)
b. just compile pkgs without gpm support for now.

Last I looked into this issue, I couldn't find a patch for gpm. I'll look again now and see but I've tried at least 4 patches in the past for this release and none solved this problem.
Comment by dorphell (dorphell) - Sunday, 18 January 2004, 23:46 GMT
Humm, we are compiling w3m with --disable-mouse.

Did you compile w3m yourself, Scott?
Comment by Scott Robbins (scottro111) - Sunday, 18 January 2004, 23:58 GMT
Not at first. I also noticed that it's marked --disable-mouse so I tried doing --disable-gpm, however I still have the same issue.

(For the heck of it, I did it one more time, removing --disable-mouse with the same result)

However, (again going from memory with Gentoo) despite the fact that -no-mouse was a temporary workaround, the problem was with gpm.


Comment by dorphell (dorphell) - Thursday, 22 January 2004, 03:17 GMT
Yeah, I've been aware of it for long and the there's no 1 patch for it as they don't have a gernal fix out yet. Not all mice cause this problem.

Loading...