[Touch-packages] [Bug 1547611] Re: Response from pinging broadcast address does not reflect the actual sender address.

2018-08-08 Thread Edo
After more than 2 Years registering this bug, not a single person
Canonical care to take care of this?

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to iputils in Ubuntu.
https://bugs.launchpad.net/bugs/1547611

Title:
  Response from pinging broadcast address does not reflect the actual
  sender address.

Status in iputils package in Ubuntu:
  New

Bug description:
  In Ubuntu 14.04 Desktop, when I ping the broadcast address (in my case the 
eth1 is 172.22.1.65/16):
ping -Ieth1 -b 255.255.255.255
  OR
ping -b 172.22.255.255

  The response from multiple host are NOT reflected properly. Intead the
  subsequent response are marked (DUP!) BUT stamped with the same
  address of the first received response.

  Ex:
  rtp-lab@wks65lnx:~$ ping -Ieth1 -bc2 255.255.255.255
  WARNING: pinging broadcast address
  PING 255.255.255.255 (255.255.255.255) from 172.22.1.65 eth1: 56(84) bytes of 
data.
  64 bytes from 172.22.0.10: icmp_seq=1 ttl=64 time=0.634 ms
  64 bytes from 172.22.0.10: icmp_seq=1 ttl=255 time=0.647 ms (DUP!)
  64 bytes from 172.22.0.10: icmp_seq=1 ttl=63 time=0.648 ms (DUP!)
  64 bytes from 172.22.0.10: icmp_seq=1 ttl=64 time=1.83 ms (DUP!)
  64 bytes from 172.22.0.10: icmp_seq=2 ttl=64 time=0.566 ms

  From wireshark/tcpdump, I can confirmed that those 3 duplicates
  packets are coming from different hosts: 172.22.2.1, 172.22.0.10 (2
  replies, not sure why, but not important in this case), and
  172.22.1.65 (itself, I allow the node to answer broadcasted ping for
  this test).

  rtp-lab@wks65lnx:~$ sudo tcpdump -ni eth1
  tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
  listening on eth1, link-type EN10MB (Ethernet), capture size 65535 bytes
  12:49:08.471063 IP 172.23.0.1.123 > 172.23.255.255.123: NTPv4, Broadcast, 
length 48
  12:49:09.000925 IP 172.22.1.65 > 255.255.255.255: ICMP echo request, id 
21934, seq 1, length 64
  12:49:09.001424 IP 172.22.0.10 > 172.22.1.65: ICMP echo reply, id 21934, seq 
1, length 64
  12:49:09.001437 IP 172.22.255.1 > 172.22.1.65: ICMP echo reply, id 21934, seq 
1, length 64
  12:49:09.003996 IP 172.22.0.10 > 172.22.1.65: ICMP echo reply, id 21934, seq 
1, length 64
  12:49:09.004006 IP 172.22.2.1 > 172.22.1.65: ICMP echo reply, id 21934, seq 
1, length 64
  12:49:10.001551 IP 172.22.1.65 > 255.255.255.255: ICMP echo request, id 
21934, seq 2, length 64
  12:49:10.002093 IP 172.22.0.10 > 172.22.1.65: ICMP echo reply, id 21934, seq 
2, length 64
  12:49:10.002106 IP 172.22.255.1 > 172.22.1.65: ICMP echo reply, id 21934, seq 
2, length 64
  12:49:10.002107 IP 172.22.0.10 > 172.22.1.65: ICMP echo reply, id 21934, seq 
2, length 64
  12:49:10.003683 IP 172.22.2.1 > 172.22.1.65: ICMP echo reply, id 21934, seq 
2, length 64

  The issue was NOT see in Ubuntu 12.04 Server. While those replies are
  marked (DUP!) HOWEVER the 'from' address are correct.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iputils/+bug/1547611/+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


[Touch-packages] [Bug 1664818] Re: Not possible to render pre-up, pre-down, post-up, or post-down snippets

2018-08-08 Thread Edo
I too have special action rely on these commands, mainly
inserting/removing iptables rule and/or creating virtual sub-interfaces.
While this most likely able to be achieved by systemd, but learning
systemd itself requires time. It will be wise for netplan to incorporate
these functionality generate the appropriate drop-in snippets, otherwise
I will have to fallback to ifupdown instead.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1664818

Title:
  Not possible to render pre-up, pre-down, post-up, or post-down
  snippets

Status in netplan:
  New
Status in systemd package in Ubuntu:
  Triaged

Bug description:
  Many configurations require scripts to run before or after an
  interface comes up or down.

  Example: I had a situation where I needed to render a post-up script
  to monitor an interface with ifupdown (and with the interface set to
  manual mode, because if the link was down I didn't want to require
  DHCP to run before the system continued booting). This is similar to
  what NetworkManager does in order to launch (or kill) a DHCP client.

  Other use cases involve setting up custom routes (such as when complex
  logic involving metrics or source routing is required) or anything
  else the designers of the netplan rendering engine didn't think of,
  such as invoking workarounds or special settings required for a
  particular NIC or environment, iptables rules that should be added or
  removed, etc.

  A follow-on issue is, it should be possible to ask that custom scripts
  run if the *link* is detected to come up or down. But I'll be happy if
  netplan first can simply replicate the custom-script-invoking behavior
  of ifupdown.

To manage notifications about this bug go to:
https://bugs.launchpad.net/netplan/+bug/1664818/+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


[Touch-packages] [Bug 1574096] [NEW] Asus's touchpad does't work

2016-04-23 Thread EDO
Public bug reported:

in these pc touchpad doesn't work

ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: xorg 1:7.7+1ubuntu8.1
ProcVersionSignature: Ubuntu 3.19.0-59.65~14.04.1-generic 3.19.8-ckt19
Uname: Linux 3.19.0-59-generic x86_64
.tmp.unity.support.test.0:
 
ApportVersion: 2.19.1-0ubuntu5
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Sat Apr 23 21:33:21 2016
DistUpgraded: 2016-04-23 18:07:02,116 DEBUG failed to SystemUnLock() (E:Non 
bloccato)
DistroCodename: wily
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation Device [8086:191b] (rev 06) (prog-if 00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. Device [1043:1c5d]
   Subsystem: ASUSTeK Computer Inc. Device [1043:1c5d]
InstallationDate: Installed on 2016-02-17 (65 days ago)
InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 004: ID 8087:0a2a Intel Corp. 
 Bus 001 Device 005: ID 045e:00e1 Microsoft Corp. Wireless Laser Mouse 6000 
Reciever
 Bus 001 Device 002: ID 04f2:b424 Chicony Electronics Co., Ltd 
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: ASUSTeK COMPUTER INC. GL552VW
ProcEnviron:
 LANGUAGE=it
 PATH=(custom, no user)
 LANG=it_IT.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-59-generic 
root=UUID=559bd433-509b-42a7-8e2e-179b5e7b0feb ro i8042.reset i8042.nomux 
i8042.nopnp i8042.noloop quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: Upgraded to wily on 2016-04-23 (0 days ago)
dmi.bios.date: 10/22/2015
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: GL552VW.213
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: GL552VW
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: ATN12345678901234567
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrGL552VW.213:bd10/22/2015:svnASUSTeKCOMPUTERINC.:pnGL552VW:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL552VW:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.name: GL552VW
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.
version.compiz: compiz 1:0.9.12.2+15.10.20151202-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.65+git20151026.c745e541-0ubuntu0ricotz~trusty
version.libgl1-mesa-dri: libgl1-mesa-dri N/A
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core N/A
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
xserver.bootTime: Sat Apr 23 20:59:28 2016
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id1135 
 vendor LGD
xserver.version: 2:1.17.1-0ubuntu3.1~trusty1

** Affects: xorg (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug compiz-0.9 ubuntu wily

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1574096

Title:
  Asus's touchpad  does't work

Status in xorg package in Ubuntu:
  New

Bug description:
  in these pc touchpad doesn't work

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 3.19.0-59.65~14.04.1-generic 3.19.8-ckt19
  Uname: Linux 3.19.0-59-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Sat Apr 23 21:33:21 2016
  DistUpgraded: 2016-04-23 18:07:02,116 DEBUG failed to SystemUnLock() (E:Non 
bloccato)
  DistroCodename: wily
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Device [8086:191b] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Device [1043:1c5d]
 Subsystem: ASUSTeK Computer Inc. Device [1043:1c5d]
  InstallationDate: Installed on 2016-02-17 (65 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 005: ID 045e:00e1 Microsoft Corp. 

[Touch-packages] [Bug 1547611] [NEW] Response from pinging broadcast address does not reflect the actual sender address.

2016-02-22 Thread Edo
Public bug reported:

In Ubuntu 14.04 Desktop, when I ping the broadcast address (in my case the eth1 
is 172.22.1.65/16):
  ping -Ieth1 -b 255.255.255.255
OR
  ping -b 172.22.255.255

The response from multiple host are NOT reflected properly. Intead the
subsequent response are marked (DUP!) BUT stamped with the same address
of the first received response.

Ex:
rtp-lab@wks65lnx:~$ ping -Ieth1 -bc2 255.255.255.255
WARNING: pinging broadcast address
PING 255.255.255.255 (255.255.255.255) from 172.22.1.65 eth1: 56(84) bytes of 
data.
64 bytes from 172.22.0.10: icmp_seq=1 ttl=64 time=0.634 ms
64 bytes from 172.22.0.10: icmp_seq=1 ttl=255 time=0.647 ms (DUP!)
64 bytes from 172.22.0.10: icmp_seq=1 ttl=63 time=0.648 ms (DUP!)
64 bytes from 172.22.0.10: icmp_seq=1 ttl=64 time=1.83 ms (DUP!)
64 bytes from 172.22.0.10: icmp_seq=2 ttl=64 time=0.566 ms

>From wireshark/tcpdump, I can confirmed that those 3 duplicates packets
are coming from different hosts: 172.22.2.1, 172.22.0.10 (2 replies, not
sure why, but not important in this case), and 172.22.1.65 (itself, I
allow the node to answer broadcasted ping for this test).

rtp-lab@wks65lnx:~$ sudo tcpdump -ni eth1
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on eth1, link-type EN10MB (Ethernet), capture size 65535 bytes
12:49:08.471063 IP 172.23.0.1.123 > 172.23.255.255.123: NTPv4, Broadcast, 
length 48
12:49:09.000925 IP 172.22.1.65 > 255.255.255.255: ICMP echo request, id 21934, 
seq 1, length 64
12:49:09.001424 IP 172.22.0.10 > 172.22.1.65: ICMP echo reply, id 21934, seq 1, 
length 64
12:49:09.001437 IP 172.22.255.1 > 172.22.1.65: ICMP echo reply, id 21934, seq 
1, length 64
12:49:09.003996 IP 172.22.0.10 > 172.22.1.65: ICMP echo reply, id 21934, seq 1, 
length 64
12:49:09.004006 IP 172.22.2.1 > 172.22.1.65: ICMP echo reply, id 21934, seq 1, 
length 64
12:49:10.001551 IP 172.22.1.65 > 255.255.255.255: ICMP echo request, id 21934, 
seq 2, length 64
12:49:10.002093 IP 172.22.0.10 > 172.22.1.65: ICMP echo reply, id 21934, seq 2, 
length 64
12:49:10.002106 IP 172.22.255.1 > 172.22.1.65: ICMP echo reply, id 21934, seq 
2, length 64
12:49:10.002107 IP 172.22.0.10 > 172.22.1.65: ICMP echo reply, id 21934, seq 2, 
length 64
12:49:10.003683 IP 172.22.2.1 > 172.22.1.65: ICMP echo reply, id 21934, seq 2, 
length 64

The issue was NOT see in Ubuntu 12.04 Server. While those replies are
marked (DUP!) HOWEVER the 'from' address are correct.

** Affects: iputils (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to iputils in Ubuntu.
https://bugs.launchpad.net/bugs/1547611

Title:
  Response from pinging broadcast address does not reflect the actual
  sender address.

Status in iputils package in Ubuntu:
  New

Bug description:
  In Ubuntu 14.04 Desktop, when I ping the broadcast address (in my case the 
eth1 is 172.22.1.65/16):
ping -Ieth1 -b 255.255.255.255
  OR
ping -b 172.22.255.255

  The response from multiple host are NOT reflected properly. Intead the
  subsequent response are marked (DUP!) BUT stamped with the same
  address of the first received response.

  Ex:
  rtp-lab@wks65lnx:~$ ping -Ieth1 -bc2 255.255.255.255
  WARNING: pinging broadcast address
  PING 255.255.255.255 (255.255.255.255) from 172.22.1.65 eth1: 56(84) bytes of 
data.
  64 bytes from 172.22.0.10: icmp_seq=1 ttl=64 time=0.634 ms
  64 bytes from 172.22.0.10: icmp_seq=1 ttl=255 time=0.647 ms (DUP!)
  64 bytes from 172.22.0.10: icmp_seq=1 ttl=63 time=0.648 ms (DUP!)
  64 bytes from 172.22.0.10: icmp_seq=1 ttl=64 time=1.83 ms (DUP!)
  64 bytes from 172.22.0.10: icmp_seq=2 ttl=64 time=0.566 ms

  From wireshark/tcpdump, I can confirmed that those 3 duplicates
  packets are coming from different hosts: 172.22.2.1, 172.22.0.10 (2
  replies, not sure why, but not important in this case), and
  172.22.1.65 (itself, I allow the node to answer broadcasted ping for
  this test).

  rtp-lab@wks65lnx:~$ sudo tcpdump -ni eth1
  tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
  listening on eth1, link-type EN10MB (Ethernet), capture size 65535 bytes
  12:49:08.471063 IP 172.23.0.1.123 > 172.23.255.255.123: NTPv4, Broadcast, 
length 48
  12:49:09.000925 IP 172.22.1.65 > 255.255.255.255: ICMP echo request, id 
21934, seq 1, length 64
  12:49:09.001424 IP 172.22.0.10 > 172.22.1.65: ICMP echo reply, id 21934, seq 
1, length 64
  12:49:09.001437 IP 172.22.255.1 > 172.22.1.65: ICMP echo reply, id 21934, seq 
1, length 64
  12:49:09.003996 IP 172.22.0.10 > 172.22.1.65: ICMP echo reply, id 21934, seq 
1, length 64
  12:49:09.004006 IP 172.22.2.1 > 172.22.1.65: ICMP echo reply, id 21934, seq 
1, length 64
  12:49:10.001551 IP 172.22.1.65 > 255.255.255.255: ICMP echo request, id 
21934, seq 2, length 64
  12:49:10.002093 IP 172.22.0.10 > 172.22.1.65: ICMP echo reply, id 21934, seq 
2, length 64
  12:49:10.002106 IP 172.22.255.1 > 

[Touch-packages] [Bug 1467583] [NEW] PROBLEM

2015-06-22 Thread EDO
Public bug reported:

---

ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: xorg 1:7.7+7ubuntu4
ProcVersionSignature: Ubuntu 3.19.0-21.21-generic 3.19.8
Uname: Linux 3.19.0-21-generic x86_64
NonfreeKernelModules: wl
.tmp.unity.support.test.0:
 
ApportVersion: 2.17.2-0ubuntu1.1
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
Date: Mon Jun 22 17:56:13 2015
DistUpgraded: Fresh install
DistroCodename: vivid
DistroVariant: ubuntu
DkmsStatus:
 bcmwl, 6.30.223.248+bdcom, 3.19.0-15-generic, x86_64: installed
 bcmwl, 6.30.223.248+bdcom, 3.19.0-21-generic, x86_64: installed
 tp-smapi, 0.41, 3.19.0-21-generic, x86_64: installed
GraphicsCard:
 Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
   Subsystem: Apple Inc. Device [106b:00ea]
InstallationDate: Installed on 2015-06-20 (1 days ago)
InstallationMedia: Ubuntu 15.04 Vivid Vervet - Release amd64 (20150422)
MachineType: Apple Inc. MacBookAir4,1
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-21-generic.efi.signed 
root=UUID=69f19b32-45d5-4cae-a423-e9801940319b ro quiet splash vt.handoff=7
SourcePackage: xorg
UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/24/2012
dmi.bios.vendor: Apple Inc.
dmi.bios.version: MBA41.88Z.0077.B0F.1201241549
dmi.board.asset.tag: Base Board Asset Tag#
dmi.board.name: Mac-C08A6BB70A942AC2
dmi.board.vendor: Apple Inc.
dmi.board.version: MacBookAir4,1
dmi.chassis.type: 10
dmi.chassis.vendor: Apple Inc.
dmi.chassis.version: Mac-C08A6BB70A942AC2
dmi.modalias: 
dmi:bvnAppleInc.:bvrMBA41.88Z.0077.B0F.1201241549:bd01/24/2012:svnAppleInc.:pnMacBookAir4,1:pvr1.0:rvnAppleInc.:rnMac-C08A6BB70A942AC2:rvrMacBookAir4,1:cvnAppleInc.:ct10:cvrMac-C08A6BB70A942AC2:
dmi.product.name: MacBookAir4,1
dmi.product.version: 1.0
dmi.sys.vendor: Apple Inc.
version.compiz: compiz 1:0.9.12.1+15.04.20150410.1-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.60-2
version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.2-0ubuntu1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.2-0ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0-1ubuntu2
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917-1~exp1ubuntu2.2
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu2build1
xserver.bootTime: Mon Jun 22 17:41:56 2015
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id   40179 
 vendor APP
xserver.version: 2:1.17.1-0ubuntu3

** Affects: xorg (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug ubuntu vivid

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1467583

Title:
  PROBLEM

Status in xorg package in Ubuntu:
  New

Bug description:
  ---

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: xorg 1:7.7+7ubuntu4
  ProcVersionSignature: Ubuntu 3.19.0-21.21-generic 3.19.8
  Uname: Linux 3.19.0-21-generic x86_64
  NonfreeKernelModules: wl
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.17.2-0ubuntu1.1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Mon Jun 22 17:56:13 2015
  DistUpgraded: Fresh install
  DistroCodename: vivid
  DistroVariant: ubuntu
  DkmsStatus:
   bcmwl, 6.30.223.248+bdcom, 3.19.0-15-generic, x86_64: installed
   bcmwl, 6.30.223.248+bdcom, 3.19.0-21-generic, x86_64: installed
   tp-smapi, 0.41, 3.19.0-21-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Apple Inc. Device [106b:00ea]
  InstallationDate: Installed on 2015-06-20 (1 days ago)
  InstallationMedia: Ubuntu 15.04 Vivid Vervet - Release amd64 (20150422)
  MachineType: Apple Inc. MacBookAir4,1
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-21-generic.efi.signed 
root=UUID=69f19b32-45d5-4cae-a423-e9801940319b ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/24/2012
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBA41.88Z.0077.B0F.1201241549
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-C08A6BB70A942AC2
  dmi.board.vendor: Apple Inc.