[Bug 1176361] Re: Launchpad crash reporting not yet enabled for saucy

2020-05-05 Thread Launchpad Bug Tracker
[Expired for apport (Ubuntu) because there has been no activity for 60 days.] ** Changed in: apport (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1176361

[Bug 1176361] Re: Launchpad crash reporting not yet enabled for saucy

2020-03-05 Thread Marcus Tomlinson
This release of Ubuntu is no longer receiving maintenance updates. If this is still an issue on a maintained version of Ubuntu please let us know. ** Changed in: apport (Ubuntu) Status: Triaged => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, wh

[Bug 1176361] Re: Launchpad crash reporting not yet enabled for saucy

2013-06-06 Thread Shahar Or
Thanks, Martin and Brian, also - I apologize - missed your name. So this is deliberate. So the issue here is that users like me, who had no idea that errors.ubuntu.com exists, and suddenly their apport seems to be not reporting at all. This is confusing. So there are now two reporting backends?

[Bug 1176361] Re: Launchpad crash reporting not yet enabled for saucy

2013-06-06 Thread Martin Pitt
As Brian already said in comment 5, we always send crashes to errors.ubuntu.com. We just haven't enabled sending them to Launchpad again yet, quite deliberately; we traditionally start after alpha-2 (or around the time that used to be), but that's of course subject to debate. ** Summary changed: