Debian Bug report logs - #219131
w3m crashes when trying to access mouse device

Toggle useless messages

Message #5 received at submit@bugs.debian.org (full text, mbox, reply):

From: Joachim Durchholz <joachim.durchholz@web.de>

To: submit@bugs.debian.org

Subject: w3m crashes when trying to access mouse device

Date: Tue, 04 Nov 2003 14:18:56 +0100

Package: w3m
Version: 0.3-2.4

Relevant configuration:
Kernel: 2.4.20
Libc version:  2.2.5-11.5
/dev hierarchy was trimmed down to those devices that actually exist.
Since the machine in question is a colocated server with no mouse or
keyboard, the mouse and keyboard nodes were removed.

Recursive /dev listing from "ls -R /dev":
--- snip ---
/dev:
MAKEDEV  hda11  hda19  hda8     loop1  null   ram11  ram4    stderr
console  hda12  hda2   hda9     loop2  port   ram12  ram5    stdin
core     hda13  hda20  initctl  loop3  ptmx   ram13  ram6    stdout
fd       hda14  hda3   initrd   loop4  pts    ram14  ram7    tty
full     hda15  hda4   ipsec    loop5  ram    ram15  ram8    urandom
hda      hda16  hda5   kmem     loop6  ram0   ram16  ram9    xconsole
hda1     hda17  hda6   log      loop7  ram1   ram2   random  zero
hda10    hda18  hda7   loop0    mem    ram10  ram3   rtc

/dev/pts:
0  1  2
--- snip ---

Connection to the machine is done via SSH exclusively.

The problem might be related to a fresh Cyrus installation. Cyrus 
depends on Tcl/Tk, which in turn installs a mouse library (GPM I think, 
though I'm not too sure). I'm not sure how this would affect w3m, 
though, since that was installed earlier and worked before the Cyrus 
installation.

Problem:
Running w3m as installed from the Debian distribution will make w3m
crash with a segmentation violation.
As far as I could tell from gdb output, the crash is due to trying to
dereference a null pointer taken from a data structure, in function
Gpm_Open(). (I didn't install sources for w3m, so this information may
be misleading.)

Workaround:
Find a .html file somewhere on disk and run
  w3m -no-mouse <whatever HTML file>
Press "o" to get the options screen; it will already have "Mouse
support: Off" listed. Tab to the OK button at the bottom of the form and
press the Enter key.
The above makes sure that w3m will start with no mouse support by default.

HTH
Jo

Message #10 received at 219131@bugs.debian.org (full text, mbox, reply):

From: Fumitoshi UKAI <ukai@debian.or.jp>

To: Joachim Durchholz <joachim.durchholz@web.de>

Cc: 219131@bugs.debian.org

Subject: Re: Bug#219131: w3m crashes when trying to access mouse device

Date: Tue, 04 Nov 2003 23:47:26 +0900

What version of libgpmg1 are you using?
I'm afraid this is the same bug as Bug#166912

Regards,
Fumitoshi UKAI

At Tue, 04 Nov 2003 14:18:56 +0100,
Joachim Durchholz wrote:
> 
> Package: w3m
> Version: 0.3-2.4
> 
> Relevant configuration:
> Kernel: 2.4.20
> Libc version:  2.2.5-11.5
> /dev hierarchy was trimmed down to those devices that actually exist.
> Since the machine in question is a colocated server with no mouse or
> keyboard, the mouse and keyboard nodes were removed.
> 
> Recursive /dev listing from "ls -R /dev":
> --- snip ---
> /dev:
> MAKEDEV  hda11  hda19  hda8     loop1  null   ram11  ram4    stderr
> console  hda12  hda2   hda9     loop2  port   ram12  ram5    stdin
> core     hda13  hda20  initctl  loop3  ptmx   ram13  ram6    stdout
> fd       hda14  hda3   initrd   loop4  pts    ram14  ram7    tty
> full     hda15  hda4   ipsec    loop5  ram    ram15  ram8    urandom
> hda      hda16  hda5   kmem     loop6  ram0   ram16  ram9    xconsole
> hda1     hda17  hda6   log      loop7  ram1   ram2   random  zero
> hda10    hda18  hda7   loop0    mem    ram10  ram3   rtc
> 
> /dev/pts:
> 0  1  2
> --- snip ---
> 
> Connection to the machine is done via SSH exclusively.
> 
> The problem might be related to a fresh Cyrus installation. Cyrus 
> depends on Tcl/Tk, which in turn installs a mouse library (GPM I think, 
> though I'm not too sure). I'm not sure how this would affect w3m, 
> though, since that was installed earlier and worked before the Cyrus 
> installation.
> 
> Problem:
> Running w3m as installed from the Debian distribution will make w3m
> crash with a segmentation violation.
> As far as I could tell from gdb output, the crash is due to trying to
> dereference a null pointer taken from a data structure, in function
> Gpm_Open(). (I didn't install sources for w3m, so this information may
> be misleading.)
> 
> Workaround:
> Find a .html file somewhere on disk and run
>    w3m -no-mouse <whatever HTML file>
> Press "o" to get the options screen; it will already have "Mouse
> support: Off" listed. Tab to the OK button at the bottom of the form and
> press the Enter key.
> The above makes sure that w3m will start with no mouse support by default.
> 
> HTH
> Jo
> 
> 

Message #15 received at 219131@bugs.debian.org (full text, mbox, reply):

From: Joachim Durchholz <joachim.durchholz@web.de>

To: Fumitoshi UKAI <ukai@debian.or.jp>

Cc: 219131@bugs.debian.org

Subject: Re: Bug#219131: w3m crashes when trying to access mouse device

Date: Tue, 04 Nov 2003 18:31:19 +0100

Fumitoshi UKAI wrote:
> What version of libgpmg1 are you using?
> I'm afraid this is the same bug as Bug#166912

Yes, the stack trace in that bug looks very similar to the one that I saw.

The bug was marked as "closed" on 2002-Feb-11, I would have thought 
that's enough time for the patch to take the round trip from upstream to 
the woody distribution. However, I still experience the crash, so I 
assume that the patch was held up somewhere since I'm still experiencing 
the crash.
dselect tells me that my GPM is version 1.19.6-12, the close message in 
bugs.debian.org says the new version is ...-12.1, so I assume that the 
woody distribution indeed contains a stale GPM. Anything that should be 
done about that?

Regards,
Jo

Message #20 received at 219131-done@bugs.debian.org (full text, mbox, reply):

From: d+deb@vdr.jp

To: 219131-done@bugs.debian.org

Subject: Re: w3m crashes when trying to access mouse device

Date: Sat, 24 Jul 2010 03:08:49 +0900

[Message part 1 (text/plain, inline)]

It may be ok to close this bug.
If this problem still exists, please reopen it.
-- 
Regards,
	dai

GPG Fingerprint = 0B29 D88E 42E6 B765 B8D8 EA50 7839 619D D439 668E

[signature.asc (application/pgp-signature, inline)]

Send a report that this bug log contains spam.