This bug was fixed in the package whoopsie - 0.2.52.4
---------------
whoopsie (0.2.52.4) xenial-proposed; urgency=medium
[Brian Murray]
* src/connectivity.c: query the correct property when trying to
network-manager's state. (LP: #1697375)
* Modify the whoopsie service file to start after networking is on-line.
* src/whoopsie.c: Add HotspotError from the openjdk-8 package hook which can
be larger than 1KB to the list of accepted fields. (LP: #1696814)
-- Tiago Stürmer Daitx <tiago.da...@ubuntu.com> Wed, 19 Jul 2017
11:39:47 -0700
** Changed in: whoopsie (Ubuntu Xenial)
Status: Fix Committed => Fix Released
--
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/1697375
Title:
whoopsie's network-manager state querying is broken
Status in whoopsie package in Ubuntu:
Fix Released
Status in whoopsie source package in Xenial:
Fix Released
Status in whoopsie source package in Zesty:
Fix Released
Status in whoopsie source package in Artful:
Fix Released
Bug description:
[Impact]
whoopsie's querying of network-manager's state is broken and this results in
whoopsie only being able to detect if the system is on-line when network
manager's state changes. Subsequently, if one manually restarts whoopsie then
whoopsie will stay off-line until an n-m state change. This can result in
crashes not being uploaded. Additionally, whoopsie's systemd service file does
not start after networking which is incorrect since it initially needs to query
network-manager's state. (However, this ended up allowing crash reports to
still be submitted because whoopsie would start first then the n-m's state
would change and whoopsie would detect that.)
[Test Case] (state detection failure)
1) Manually restart the whoopsie service
2) Observe the following two messages:
"Jul 14 14:48:09 speedy whoopsie[14137]: [14:48:09] Could not get the Network
Manager state:
Jul 14 14:48:09 speedy whoopsie[14137]: [14:48:09]
GDBus.Error:org.freedesktop.DBus.Error.InvalidArgs: No such property 'state'"
with the version of network-manager from -proposed you will not see
these messages when restarting whoopsie.
[Test Case] (starting after network-manager0
1) Boot your system
2) Observe the following in syslog:
"Jul 17 06:46:47 speedy whoopsie[1156]: [06:46:47] Could not get the Network
Manager state:
Jul 17 06:46:47 speedy whoopsie[1156]: [06:46:47]
GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name
org.freedesktop.NetworkManager was not provided by any .service files
"
with the version of network-manager in -proposed you will not see the
"NetworkManager was not provided" messages.
[Regression Potential]
Its possible that systems that were not submitting crash reports suddenly
will and that will use some network bandwidth and Error Tracker resources.
- Original Description -
------------------------
On artful crash reports are not uploaded automatically (several .crash files
in /var/crash and no corresponding upload or .uploaded files)
ProblemType: BugDistroRelease: Ubuntu 17.10
Package: whoopsie 0.2.56
ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15
Uname: Linux 4.10.0-22-generic x86_64
ApportVersion: 2.20.5-0ubuntu4
Architecture: amd64
CurrentDesktop: GNOME
Date: Mon Jun 12 09:39:29 2017
InstallationDate: Installed on 2013-09-03 (1377 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902)
ProcEnviron:
TERM=screen-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=<set>
LANG=fr_FR.UTF-8
SHELL=/bin/bash
RelatedPackageVersions: apport-noui N/ASourcePackage: whoopsie
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/whoopsie/+bug/1697375/+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
