forwarded 635644 https://sourceforge.net/tracker/?func=detail&atid=757308&aid=3381993&group_id=143975 tags 635644 upstream thanks
On Thu, Jul 28, 2011 at 12:00 PM, Francesco Poli <invernom...@paranoici.org> wrote: > [please remember to Cc: me, otherwise I will only be able to see your > replies on the BTS web interface] Sorry, will do! > Maybe the first time Fluxbox is started, it is not fast enough to do > something that is needed by Conky, and the latter fails to start > because of this. The next times Fluxbox is started (without rebooting > the box), it is faster to load, due to memory caches and similar tricks > performed by the kernel: as a consequence, Conky finds Fluxbox fully > initialized (or more initialized, anyway) and is able to start > properly. > This is all I can imagine, as a guessed explanation... > Could it be? Or am I completely off-track? At the moment, that sounds like the most reasonable explanation for this bug... > Well, I think it *is* a bug, even though we *may* have found a way to > work around it. > Hence, it would be very nice of you, if you could forward the bug > report upstream... I've just forwarded the bug upstream; see https://sourceforge.net/tracker/?func=detail&atid=757308&aid=3381993&group_id=143975 (if there's anything I've overlooked, feel free to add a comment). - Vincent -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
