Bug#813497: closed by Bálint Réczey <bal...@balintreczey.hu> (reply to bal...@balintreczey.hu) (Re: Bug#813497: kodi: Segfault on Startup)

2016-02-11 Thread Bálint Réczey
Control: fixed -1 15.2+dfsg1-3 2016-02-11 1:53 GMT+01:00 Alessio Treglia : > Please close again this bug by specifying the version it is no longer > reproducible. Most probably it was current version. Please change it if that's not the case. Cheers, Balint

Processed: Re: Bug#813497: closed by Bálint Réczey <bal...@balintreczey.hu> (reply to bal...@balintreczey.hu) (Re: Bug#813497: kodi: Segfault on Startup)

2016-02-11 Thread Debian Bug Tracking System
Processing control commands: > fixed -1 15.2+dfsg1-3 Bug #813497 {Done: Bálint Réczey } [kodi] kodi: Segfault on StartUp Marked as fixed in versions kodi/15.2+dfsg1-3. -- 813497: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=813497 Debian Bug Tracking System Contact

Processed: Re: Bug#813497: closed by Bálint Réczey <bal...@balintreczey.hu> (reply to bal...@balintreczey.hu) (Re: Bug#813497: kodi: Segfault on Startup)

2016-02-11 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > notfound 813497 15.2+dfsg1-3 Bug #813497 {Done: Bálint Réczey } [kodi] kodi: Segfault on StartUp No longer marked as found in versions kodi/15.2+dfsg1-3. > thanks Stopping processing here. Please contact me if you need

Bug#813497: closed by Bálint Réczey <bal...@balintreczey.hu> (reply to bal...@balintreczey.hu) (Re: Bug#813497: kodi: Segfault on Startup)

2016-02-10 Thread Stephen Allen
Well, whatever it was, it's been fixed in a recent upgrade since. Perhaps just one of those things that happens when running SID. Thanks for your attention to this matter.

Bug#813497: closed by Bálint Réczey <bal...@balintreczey.hu> (reply to bal...@balintreczey.hu) (Re: Bug#813497: kodi: Segfault on Startup)

2016-02-10 Thread Alessio Treglia
Please close again this bug by specifying the version it is no longer reproducible. Cheers. On Thu, Feb 11, 2016 at 12:49 AM, Stephen Allen wrote: > > Well, whatever it was, it's been fixed in a recent upgrade since. > Perhaps just one of those things that happens