So I think I've got things sorted out by (a) switching to call
SetReportCrashes async to avoid blocking the UI, and (b) not calling
SetReportCrashes if we're asked to set it to the current (cached) value
of the property.
I've noticed that if whoopsie-preferences exits while the privacy panel
is open, I get a bit of a bounce when toggling the switch next. This
seems to be due to whoopsie-preferences sending out a stray change
notification signal on start up:
method call time=1507538340.672978 sender=:1.1499 ->
destination=com.ubuntu.WhoopsiePreferences serial=30
path=/com/ubuntu/WhoopsiePreferences; interface=com.ubuntu.WhoopsiePreferences;
member=SetReportCrashes
boolean false
signal time=1507538340.756225 sender=:1.1507 -> destination=(null
destination) serial=9 path=/com/ubuntu/WhoopsiePreferences;
interface=org.freedesktop.DBus.Properties; member=PropertiesChanged
string "com.ubuntu.WhoopsiePreferences"
array [
dict entry(
string "ReportMetrics"
variant boolean true
)
dict entry(
string "ReportCrashes"
variant boolean true
)
]
array [
]
method call time=1507538340.756590 sender=:1.1499 -> destination=:1.1507
serial=31 path=/com/ubuntu/WhoopsiePreferences;
interface=org.freedesktop.DBus.Properties; member=GetAll
string "com.ubuntu.WhoopsiePreferences"
method call time=1507538340.757395 sender=:1.1499 ->
destination=com.ubuntu.WhoopsiePreferences serial=32
path=/com/ubuntu/WhoopsiePreferences; interface=com.ubuntu.WhoopsiePreferences;
member=SetReportCrashes
boolean true
signal time=1507538341.034321 sender=:1.1507 -> destination=(null
destination) serial=14 path=/com/ubuntu/WhoopsiePreferences;
interface=org.freedesktop.DBus.Properties; member=PropertiesChanged
string "com.ubuntu.WhoopsiePreferences"
array [
dict entry(
string "ReportCrashes"
variant boolean false
)
]
array [
]
method call time=1507538341.035076 sender=:1.1499 -> destination=:1.1507
serial=33 path=/com/ubuntu/WhoopsiePreferences;
interface=com.ubuntu.WhoopsiePreferences; member=SetReportCrashes
boolean false
So essentially whoopsie-preferences is sending out an unsolicited
PropertiesChanged signal on startup with the initial values before
processing the SetReportCrashes method call. Then gnome-control-center
responds by trying to match the switch state leading to the bounce.
So I guess I'll have to dive into the whoopsie-preferences code to see
if I can silence the stray signal.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to whoopsie in Ubuntu.
https://bugs.launchpad.net/bugs/1720331
Title:
Whoopsie continually relaunching
Status in gnome-control-center package in Ubuntu:
Triaged
Status in whoopsie package in Ubuntu:
Invalid
Bug description:
Today for the first time, and coincidentally looking for a different
setting, I went to the Settings->Privacy dialogue. I was also
(coincidentally for a different reason, relating to #1720149) already
tailing /var/log/syslog to a terminal.
Immediately on opening that dialogue, the syslog tail flooded with
whoopsie continually relaunching, causing enough work to raise the fan
speeds. This is a representative section from towards the end of me
letting it, before I killed the service, with some necessary
viciousness. Specifically
systemctl stop whoopsie
(didn't stop it)
systemctl disable whoopsie
(didn't stop it)
(find pid for whoopsie's root process and kill it)
(that stopped it)
Also for good measure ensured the automatic bug reporting option in
the privacy settings dialog was set to manual, which I think was done
anyway when I disabled whoopsie, though the dialog wasn't on top at
the time for me to be sure. It had been set to automatic when I first
opened the dialog.
Snippet from syslog attached. It was just repeating this continually
for several minutes before I stopped it.
ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: whoopsie 0.2.58
ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
Uname: Linux 4.13.0-12-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.7-0ubuntu1
Architecture: amd64
CrashReports:
664:1000:119:0:2017-09-25 18:16:58.760134901 +0100:2017-09-25
18:16:58.760134901 +0100:/var/crash/_opt_google_chrome_chrome.1000.upload
640:1000:119:102847031:2017-09-27 20:28:45.352315425 +0100:2017-09-28
09:02:32.195212507 +0100:/var/crash/_usr_bin_gnome-shell.1000.crash
640:1000:119:34020328:2017-09-25 18:16:57.656132936 +0100:2017-09-25
18:16:58.760134901 +0100:/var/crash/_opt_google_chrome_chrome.1000.crash
600:111:119:0:2017-09-25 18:16:59.348145502 +0100:2017-09-25
18:16:59.348145502 +0100:/var/crash/_opt_google_chrome_chrome.1000.uploaded
CurrentDesktop: GNOME
Date: Fri Sep 29 10:00:34 2017
InstallationDate: Installed on 2017-07-30 (60 days ago)
InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
RelatedPackageVersions: apport-noui N/A
SourcePackage: whoopsie
UpgradeStatus: Upgraded to artful on 2017-08-22 (37 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1720331/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
