Dear John, thank you for your interest in Bug#940463.
I got no reply from Xeno Idaltu <xenoida...@gmail.com>, so I believe that either he is not using falkon again, or he installed falkon's new package and found the bug fixed. His only e-mail states that he made a fresh install, and gives version numbers for the distribution and dependencies. Sorry, I had no time to reproduce the same installation. As my last e-mail tells, I "Checked that falkon-3.1.0+dfsg1-3 does not crash", which can be considered as being unable to reproduce the bug. The issue seems to be fixed between two upstream releases (falkon 3.0 and falkon 3.1). John, if you want to help about packaging falkon for Debian, you are most welcome. By the way, were you able to reproduce the crash? Best regards, Georges. John Scott a écrit : > On Wed, 16 Oct 2019 10:00:15 +0000 Georges Khaznadar <georg...@debian.org> > wrote: > > Source: falkon > > Source-Version: 3.1.0+dfsg1-4 > > > > We believe that the bug you reported is fixed in the latest version of > > falkon, which is due to be installed in the Debian FTP archive. > > > > A summary of the changes between this version and the previous one is > > attached. > > > > Changes: > > falkon (3.1.0+dfsg1-4) unstable; urgency=medium > > . > > * Checked that falkon-3.1.0+dfsg1-3 does not crash. > > Closes: #940463 > > Did a change to Falkon fix the issue, or is 3.1.0+dfsg-1-4 the same as > 3.1.0+dfsg-1-3? Was the submitter's issue resolved or were you unable to > reproduce the crash? -- Georges KHAZNADAR et Jocelyne FOURNIER 22 rue des mouettes, 59240 Dunkerque France. Téléphone +33 (0)3 28 29 17 70
signature.asc
Description: PGP signature
