No problem on the lots of bugs. It is good that we have lots of users to report things.
552896 may well be the same problem as 554174/573172. Soon I will go through the entire panel with grep and audit all the timer handling. 2.18.8 was a bad release also. I found and reported (and someone else reported) that Firefox and Thunderbird crashed immediately, and they shipped 2.18.9 two days later. It does not mean I will not work on LXTerminal. I don't feel the same ownership of it that I do of LXPanel, and I don't work on it very often. The way I do it is to leave bugs unassigned until someone decides they are actively working on one, and then they assign it to themselves and close it when they are confident it is fixed. The one about KBLED losing its configuration is puzzling. I can't make that happen and it should not be able to happen unless you were to leave the dialog open and log out. The dialogs don't write the configuration to disk until you click Close. On 03/20/2010 08:27 AM, Christoph Wickert wrote: > Am Freitag, den 19.03.2010, 22:57 -0400 schrieb Marty Jack: >> Fedora just filed a raft of bugs. > > Sorry for filing so many bugs at once, I had to clean up my queue. ;) > >> Using their bug numbers: >> >> 556979 and 575053 are duplicate. A change is checked in that I >> believe should fix it. It is a race condition, so cannot be directly >> verified. >> >> 554174 and 573172 are duplicate. A change is checked in that I >> believe should fix it. It is a race condition, so cannot be directly >> verified. > > I have closed the duplicates in our bugzilla, feel free to do the same @ > sf.net. I am about to build packages with your fixes and ask the bug > reporters for feedback. > >> 552896 is a timer expiration and a segv in widget-set-state out of the >> main loop. I have no idea how to get at this one. The logical >> explanation is there is some timer that is not being cleared before >> its structure is deleted. It could be any plugin even the ones I >> can't run on my system or never look at. > > As I was the one to report the bug I can at least tell you that it > doesn't happen that often, I think it only occurred once. > >> 552897 is in icon-grid after a configuration change. Again I have no >> idea how to get at this one. > > I haven't seen that one for a long time ether. IIRC this only happened > with GTK 2.18.6 and after upgrading to 2.18.7 I haven't hit it again. > IMHO 2.18.6 was a bad release, it caused me a lot of headache. I think > #552896 also appeared with 2.18.6. > >> There are also LXTerminal bugs. I am not thrilled about having those >> assigned to me since my only involvement was shipping the tarball, >> because no one else ever does it. If someone who actually changed the >> code could look at them, that would be great. > > Uh, I'm sorry, I thought you were maintaining lxterminal. Feel free to > reassign it to Fred. > > Regards, > Christoph > > > > ------------------------------------------------------------------------------ > Download Intel® Parallel Studio Eval > Try the new software tools for yourself. Speed compiling, find bugs > proactively, and fine-tune applications for parallel performance. > See why Intel Parallel Studio got high marks during beta. > http://p.sf.net/sfu/intel-sw-dev > _______________________________________________ > Lxde-list mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/lxde-list > ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ Lxde-list mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/lxde-list
