[Touch-packages] [Bug 1778694] Re: In autoreport mode in whoopsie-preferences API, reports are not sent by whoopsie

2018-09-06 Thread Launchpad Bug Tracker
This bug was fixed in the package apport - 2.20.9-0ubuntu7.3 --- apport (2.20.9-0ubuntu7.3) bionic; urgency=medium [ Didier Roche ] * Add a remember option to whoopsie so that users can diminish crash interactions (LP: #1778497) * Move apport autoreport service files to

[Touch-packages] [Bug 1778694] Re: In autoreport mode in whoopsie-preferences API, reports are not sent by whoopsie

2018-08-27 Thread Jean-Baptiste Lallement
SRU verification for Bionic: I have reproduced the problem on Ubuntu Desktop with apport 2.20.9-0ubuntu7.2 in bionic-updates and have verified that the version of apport 2.20.9-0ubuntu7.3 in -proposed fixes the issue. Marking as verification-done ** Tags removed: verification-needed

[Touch-packages] [Bug 1778694] Re: In autoreport mode in whoopsie-preferences API, reports are not sent by whoopsie

2018-08-03 Thread Brian Murray
When is the apport-autoreport.path service started? I was testing this and noticed that when switching the mode to automatic in g-c-c the file /var/lib/apport/autoreport is created but apport-autoreport.path does not seem to be started so crash reports would sit around until the next reboot when

[Touch-packages] [Bug 1778694] Re: In autoreport mode in whoopsie-preferences API, reports are not sent by whoopsie

2018-07-31 Thread Launchpad Bug Tracker
** Branch linked: lp:~ubuntu-core-dev/ubuntu/cosmic/apport/ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1778694 Title: In autoreport mode in whoopsie-preferences

[Touch-packages] [Bug 1778694] Re: In autoreport mode in whoopsie-preferences API, reports are not sent by whoopsie

2018-07-19 Thread Brian Murray
Hello Didier, or anyone else affected, Accepted apport into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/apport/2.20.9-0ubuntu7.3 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See

[Touch-packages] [Bug 1778694] Re: In autoreport mode in whoopsie-preferences API, reports are not sent by whoopsie

2018-07-17 Thread Didier Roche
Thanks! I indeed didn't try the server side, I don't see how this is a new issue though compared to apport-noui.service? The same service files start/restart/stop rules are just moved to apport package via apport- autoreport.service. So, if there is a race on install until the next reboot, the

[Touch-packages] [Bug 1778694] Re: In autoreport mode in whoopsie-preferences API, reports are not sent by whoopsie

2018-07-16 Thread Brian Murray
sil2100 asked me to look at the SRU of this for Ubuntu 18.04 and I tested something in Cosmic that I have a concern about. On a cosmic server I installed apport-noui, which also installed whoopsie, I then used kill -11 and a .crash file was created in /var/crash but no .upload and .uploaded file

[Touch-packages] [Bug 1778694] Re: In autoreport mode in whoopsie-preferences API, reports are not sent by whoopsie

2018-07-10 Thread Didier Roche
** Also affects: apport (Ubuntu Bionic) Importance: Undecided Status: New ** Description changed: - The goal for autoreporting via whoopsie is to have a silent mode where whoopsie automatically reports crashes. However, this one requires apport-noui to be installed, which we don't by

[Touch-packages] [Bug 1778694] Re: In autoreport mode in whoopsie-preferences API, reports are not sent by whoopsie

2018-07-06 Thread Launchpad Bug Tracker
This bug was fixed in the package apport - 2.20.10-0ubuntu5 --- apport (2.20.10-0ubuntu5) cosmic; urgency=medium * Assume if no whoopsie that crash reporting is enabled: As the old configuration that was a whoopsie configuration file that was that was never updated by

[Touch-packages] [Bug 1778694] Re: In autoreport mode in whoopsie-preferences API, reports are not sent by whoopsie

2018-06-29 Thread Sebastien Bacher
The changes described make sense to me, thanks. I'm not convinced that "apport-noui" is right/makes sense (if you install it and use the API to disable autoreporting you end up with the package installed but the service no started which is inconsistent with the definition) but it's a different

[Touch-packages] [Bug 1778694] Re: In autoreport mode in whoopsie-preferences API, reports are not sent by whoopsie

2018-06-29 Thread Didier Roche
FTR, discussed with Brian, my proposed solution sounds to make sense, keeping an unseeded apport-noui: - have the systemd units (path and service) moved to apport binary package - let apport-noui only touching/remove in maintainerscript script the autoreport file (this is the same file created

[Touch-packages] [Bug 1778694] Re: In autoreport mode in whoopsie-preferences API, reports are not sent by whoopsie

2018-06-29 Thread Sebastien Bacher
It's not clear from the changelog/package history why -noui was a split package. It does depends on "apport" so doesn't pull in less components, if there is a config API and a way to use/not use the service I don't see the point of splitting the binary, I would just merge it back with apport.

[Touch-packages] [Bug 1778694] Re: In autoreport mode in whoopsie-preferences API, reports are not sent by whoopsie

2018-06-26 Thread Didier Roche
** Description changed: The goal for autoreporting via whoopsie is to have a silent mode where whoopsie automatically reports crashes. However, this one requires apport-noui to be installed, which we don't by default. apport-noui is just a set of systemd unit starting whoopsie-upload-all