I've been having problems with lopster ever since I emerged it of it randomly segfaulting once every few hours or so, and, less frequently, hanging taking up 99% of the CPU. This problem makes lopster significantly less useful. I had originally believed this was just poor code on lopster's part, but I no longer believe that because I downloaded the latest CVS snapshot of lopster, built it and installed it in /usr/local - and have not had the problem since. I'm not completely sure if it's due to improvements in the CVS version of lopster or if it's simply because I built it myself and not from ebuild. Either way Gentoo Linux needs an updated lopster ebuild. I didn't do anything special when building lopster myself. I just did the generic autogen.sh ; ./configure ; make ; make install.
Same problem Here what i get when it die Lopster started at Tue Dec 2 01:39:55 2003 sigseg: segmentation fault: 11 sigseg: rc-file was read sigseg: geometry was read sigseg: access list was read sigseg: search patterns were read sigseg: please report the reason if you know -------------------------------------------------- sigseg: trying to do normal exit sigseg: normal exit failed sigseg: trying to save geometry sigseg: geometry saved sigseg: trying to save rc-file sigseg: rc-file saved sigseg: trying to log statistic sigseg: statistic logged, exiting... Regards N.
Using CVS lopster still crashes. Gdk-CRITICAL **: file gdkwindow.c: line 727 (gdk_window_unref): assertion `private->ref_count > 0' failed. sigseg: segmentation fault: 11 sigseg: rc-file was read sigseg: geometry was read sigseg: access list was read sigseg: search patterns were read sigseg: please report the reason if you know -------------------------------------------------- sigseg: trying to do normal exit I've also found other lopster's users with the same problem on different distributions, so definitely seems not an ebuild problem. N.
Are you still having this problem? If so, what version do you have installed? Does using a different version corect the problem? If so, in what version does the regression or fix appear? Please provide the output of 'emerge info'
I do not know the answer to whether or not there's still a problem since I've been using the latest cvs (alpha) version of lopster (compiled by me) without a problem since the time I opened this bug. If there hasn't been any changes to the lopster version in portage nor its ebuild, then the problem should still be there. Since there hasn't been a release of lopster since 1.2.0, which is known to be unstable on multiple distros, I'd recommend putting the latest cvs version in portage, which I can vouch that it is more stable than the 1.2.0 version that's currently there. Other than that I don't know what should be done.
bouncing back to herd... still no new release...
lopster-1.2.1 now in portage- do you still have trouble with this version?
closing bug; newest lopster has been up and works for me just fine
I have verified that lopster has now been going for several days without crashing. Looks like a winner!
