Puppy Linux Discussion Forum

Béèm · Posted: Tue 04 Nov 2008, 17:06 Post subject:

I remark that in fact nobody had the idea to ask the question in a mozilla support group.
So I did now in news:news.mozilla.org group mozilla.support.seamonkey.
For those who want to follow use Mozilla news to login to the server, but beware don't use the insert key. Wink

Béèm · Posted: Wed 05 Nov 2008, 18:57 Post subject:

I got one reply from someone using fedora and 1.1.12. He don't have he issue.
I installed 1.1.12 in puppy and still have the issue.
Maybe not a SeaMonkey issue?
Maybe something weird in puppy or in the forum?

Béèm · Posted: Wed 05 Nov 2008, 19:31 Post subject:

I tried another forum and have the same issue still.
Leaves puppy itself then, altho other applications like swrite/geany work correctly.

Flash · Posted: Wed 05 Nov 2008, 22:52 Post subject:

Thanks, Béèm. Does it also happen to you in, say, Yahoo's mail compose window?

Pizzasgood · Posted: Wed 05 Nov 2008, 23:06 Post subject:

Béèm · Posted: Thu 06 Nov 2008, 16:13 Post subject:

Béèm · Posted: Thu 06 Nov 2008, 16:19 Post subject:

disciple · Posted: Mon 10 Nov 2008, 05:53 Post subject:

I just tried Thunderbird, and it crashes it too (e.g. the compose window). And the help browser in Dingo. So I guess it crashes everything Mozilla.

IIRC, muppy has an updated GTK/Glib - we could test with them.
I thought MU had posted packages, but I can't find them. Does anyone else remember this?

thekevinday · Joined: 31 Oct 2008 Posts: 3

I have partially identified and partially solved (more like worked around) the problem.

I recently noticed that by adding the compile time option "--enable-debug=yes" to glib caused some glib related segfaults and crashes to stop. This in itself did not solve the INSERT key issue.

Naturally, I decided to also compile gtk+ with the option "--enable-debug=yes" and success, the problem goes away; I can now press the insert key!

This completely solves the problem from the end-user's perspective.

EDIT: I almost forgot to mention, i did not need to recompile anything other than glib and gtk+, seamonkey was left untouched.

Béèm · Posted: Mon 10 Nov 2008, 20:03 Post subject:

thekevinday · Joined: 31 Oct 2008 Posts: 3

I was referring to more on the terms of the distributors being able to supply a recompiled work around version until such a time that the real problem gets fixed.

disciple · Posted: Mon 10 Nov 2008, 20:32 Post subject:

Béèm · Posted: Mon 10 Nov 2008, 21:19 Post subject:

Pizzasgood · Posted: Mon 10 Nov 2008, 21:51 Post subject:

Cool. I'll take care of it tomorrow.

Pizzasgood · Posted: Tue 11 Nov 2008, 18:17 Post subject:

Well, I though I had it working fine, but I think it broke Geany now, so I just took down my package before anybody borks themselves (hopefully they haven't already...).

I will test further.