This bug was fixed in the package whoopsie - 0.2.34
---
whoopsie (0.2.34) utopic; urgency=medium
[ John Lenton ]
* Obtain a MAC address for system identifier generation even if the network
is not up. (LP: #1328285)
-- Brian MurrayMon, 07 Jul 2014 11:44:26 -0700
** Change
** Branch linked: lp:ubuntu/utopic-proposed/whoopsie
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1328285
Title:
can not find hardware address
To manage notifications about this bug go to:
https:/
** Branch linked: lp:whoopsie
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1328285
Title:
can not find hardware address
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubu
** Tags added: rls-u-incoming
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1328285
Title:
can not find hardware address
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubu
** Branch linked: lp:~chipaca/whoopsie/no-moar-siocyadda
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1328285
Title:
can not find hardware address
To manage notifications about this bug go to:
htt
** Changed in: whoopsie (Ubuntu)
Assignee: (unassigned) => John Lenton (chipaca)
** Changed in: whoopsie (Ubuntu)
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bu
The above more directly addresses the root cause here, which is that
whoopsie is starting up and trying to find a mac address before the
interface is up, and SIOCGIFCONF only returns the list of interfaces
that are up and have ipv4 addresses associated with them. The system
identifier generation s
I'm not convinced this (the message in the log file) is actually an
issue as I quickly ran the following command after booting up and did
have a system identifier.
root@ubuntu-phablet:~# /home/phablet/system-id.sh
('79493b50adc9aac91c09a65a7a5c145b5c4de51a33c5c63bd6ebfd9859d2f16792300ee3c95db7730
stgraber: do you know a proper way to programmatically get a list
of all network interfaces on a system, including those that are currently down?
http://linux.die.net/man/7/netdevice documents that SIOCGIFCONF doesn't
include down interfaces, and recommends /proc/net/dev instead
slangasek: I
I tested a fix using the following change:
=== modified file 'data/whoopsie.conf'
--- data/whoopsie.conf 2013-02-20 18:26:14 +
+++ data/whoopsie.conf 2014-06-09 22:15:18 +
@@ -2,7 +2,7 @@
description"crash report submission daemon"
-start on runlevel [2345]
+start on runlevel [2
** Tags added: utopic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1328285
Title:
can not find hardware address
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+sou
11 matches
Mail list logo
