On Sat, Oct 10, 2009 at 12:42:22AM +0200, Eduard Bloch wrote: > #include <hallo.h> > * Stanislav Maslovski [Sun, Sep 27 2009, 01:51:29PM]: > > > > Here you can see it: > > > > https://sourceforge.net/tracker/index.php?func=detail&aid=1878118&group_id=31&atid=100031 > > > > > > > > This bug also can be related: > > > > https://sourceforge.net/tracker/?func=detail&atid=100031&aid=1875387&group_id=31 > > > > > > Does not provide any (good) clue. > > > > I reported it to sourceforge long time ago, with a detailed log from > > IceWM compiled with enabled debug output, please have a look. When the > > problem appears IceWM spits out an internal error message. > > Heh? When I say "Not reproducible for me" than I mean it. Show a repro > which reliably "works". > > > http://sourceforge.net/tracker/?func=detail&aid=1878118&group_id=31&atid=100031 > > > > > The code seems to be ok, and your problem is not reproducible for me by > > > any means. > > > It is reproducible. First of all, there are bug reports on sourceforge > > You cannot proove anything by testing.
I just do not get it. Do you take bug reports so personally? Your reaction seems very strange. What kind of "proof" do you need? Is it not enough for you to have bugreports? Or do you think that we invent them to keep you entertained? You must be crazy then. Moreover, your logic is completely wrong here. _You_ can not prove that there is _no_ bug by testing and _not_ seeing it. > > about the same problem (not originated by me), second, I know several > > guys who experience the same bug. In fact, there is a discussion of > > this bug going on in debian-russian now. > > Ну тогда покажите наконец-то, что я как дурак должен искать? http://lists.debian.org/debian-russian/2009/09/msg00909.html http://lists.debian.org/debian-russian/2009/09/msg00912.html http://lists.debian.org/debian-russian/2009/09/msg01030.html http://lists.debian.org/debian-russian/2009/10/msg00109.html http://lists.debian.org/debian-russian/2009/10/msg00157.html http://lists.debian.org/debian-russian/2009/10/msg00670.html > > > Tried stable/unstable icewm and gajim packages in all > > > combinations, it works fine. > > > > It seems that this problem is a kind of race, so it does not appear > > every time and there must be some special conditions for it to appear. > > However, for me it appears too offten to be annoying. > > If that's a race then it should get a real fix. One where you can > explain where the race happened and why. I invested some time into it in the past. I can tell that the tray embedding code in IceWM is far from being straightforward. When I realized that going deeper would require too much time I just decided to use the simple solution I found earlier. > > * Reverted changes in icetray.cc from rev. 1.15.2.4 and 1.15.2.5. > > > > Those are CVS revisions. > > Не убеждает. I am just the maintainer, I do not like reverting upstream > changes just caused by the hope that if solves some bizzare problem. Well, it is up to you. As well as, it is up to us to keep our own versions of icewm in our personal repositories. I do not see however how the normal users would benefit from such a development. -- Stanislav -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
