?

Log in

No account? Create an account
gtk lockup bug - LogJam [entries|archive|friends|userinfo]
LogJam

[ website | LogJam ]
[ userinfo | livejournal userinfo ]
[ archive | journal archive ]

gtk lockup bug [Sep. 13th, 2003|04:55 pm]
LogJam
logjam
[evan]
GTK versions around 2.2.2 (or is it 2.2.3?) have a bug in the text widget. It typically happens when you're typing an entry into LogJam and you get to the bottom of the visible space; GTK tries to add scroll bars (or something?), freaks out, and locks up.

I keep seeing friends having this problem, and it occurred to me that everyone else might like to know about this too. :) GTK 2.2.4, released maybe a week ago, fixed this bug, so be sure to upgrade, especially if you've encountered this problem.

(In general, you always want the "autosave drafts" option turned on in the LogJam settings. The only reason it's not on by default is privacy concerns, though I don't know how valid those are...)
LinkReply

Comments:
[User Picture]From: lyspeth
2003-09-13 06:01 pm (UTC)

Thanks for the heads-up...I have had that problem a few times, and the autosave drafts was a big help. :)
(Reply) (Thread)
[User Picture]From: draconid
2003-09-14 04:04 am (UTC)
Yes, I was having this problem. Although it doesn't seem to have happened this week despite the fact that I haven't upgraded yet. Anyway, thanks for the heads up, I shall upgrade immediately. :)
(Reply) (Thread)
From: inverted_tree
2003-09-14 06:54 am (UTC)
It's probably 2.2.2 which had the bug, since 2.2.4 is just an emergency release fixing two issues in 2.2.3 (basically I screwed something up in 2.2.3 and got to roll 2.2.4 :/).
(Reply) (Thread)
[User Picture]From: chirik
2003-09-15 11:27 am (UTC)
I've had this problem a few times, but I'd figured it was a library issue - I'm running debian unstable on my desktop, and it'd happen after I'd upgraded a bunch of libraries (pretty much all the GTK/gnome related libraries) but hadn't logged out yet. Once I would do so, it would go away.
(Reply) (Thread)
[User Picture]From: dataknife
2003-09-15 11:31 pm (UTC)

On a different note...

you might want to modify your autoconf script to add
-dy to the LDFLAGS directive which will enable ld's linking against so's ( at least, that's what it took to get this to build on my RH9 system, well that and symbolically linking libpspell.so.4 to libpspell.so)
(Reply) (Thread)
From: evan
2003-09-16 12:43 pm (UTC)

Re: On a different note...

What does -dy do? I've never heard of it, and I try to follow these sorts of things... And why hasn't anyone else on RH9 reported problems?

(I'm not questioning your report-- rather, I'm asking these questions to better learn what the issue is.)
(Reply) (Parent) (Thread)
[User Picture]From: dataknife
2003-09-16 11:20 pm (UTC)

Re: On a different note...

well, according to the man page for ld it allows the linker to link against the shared libraries. The problem that I ran into was that the linker couldn't find the pspell library, which was on my machine, but not in a statically linkable form. So I had to tell the linker to let it go. I imagine that many RH9 users either a) used the RPM, b) gave up when it couldn't link, or c) didn't attempt to add in spell checking.

Taking the steps that I mentioned earlier worked well for me, but you never know... they might break something for someone else.
(Reply) (Parent) (Thread)
From: evan
2003-09-17 11:54 am (UTC)

Re: On a different note...

Hm, from the manpage it seems that -dy is the default on platforms that support dynamic linking (which is pretty much any recent one and I assume Linux as well).

Did you install pspell/gtkspell from source? Did you run ldconfig afterwards?
(Reply) (Parent) (Thread)
[User Picture]From: dataknife
2003-09-17 02:01 pm (UTC)
I used up2date to get the latest gtkspell rpms and let it do it's thing. I did, however, use ldconfig after I first ran into the error... I'm not really too worried about it, since I did get it to link and execute.. I just added the not as a thought (as much for you as for others who might run into the same issues)
(Reply) (Thread)