This bug [1] has been open for a very long time, and through the problem can be said to be easy to spot (flash), the reporter hasn't confirmed if this is indeed the cause of his problem, nor offer a clear way to reproduce the issue (the title, may suggest that there's something special that needs to be done, using JavaScript). Both possible packages involved have low/no priority for upstream and the fix possibly has been deployed in later versions.
What should be done in such cases? shirish suggest lower the priority, is this the best course of action? -- Braiam Peguero -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/CAG=7Bt9U-q8dv_DcLyB_nRXCUQjagHMCA+6wDd1MxB752f=t...@mail.gmail.com
