[Touch-packages] [Bug 1654448] Re: XPS 13 9360, Realtek ALC3246, Headphone audio hiss

2017-05-08 Thread Jared Dominguez
@frail-knight, the right people are already subscribed to this bug.
Please *stop* changing bugs to affect dell-sputnik

** Changed in: dell-sputnik
   Status: New => Incomplete

** Changed in: dell-sputnik
   Status: Incomplete => Invalid

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

Title:
  XPS 13 9360, Realtek ALC3246, Headphone audio hiss

Status in Dell Sputnik:
  Invalid
Status in alsa-driver package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  Pertaining to 16.04 on a dell XPS 13 9360

  ii  alsa-base 1.0.25+dfsg-0ubuntu5

  Advanced Linux Sound Architecture Driver Version k4.4.0-57-generic.

  
  When headphones are plugged in, there is a clearly audible hiss (white 
noise). This is present as soon as the headphones are plugged in, whether 
'headphones' or 'headset' are selected from the pop-up box. 

  Using alsamixer to debug the issue reveals that it is related to
  "Headphone Mic Boost" - the default setting is: dB gain 0.00, 0.00. If
  this is changed to:

  10.00, 10.00 (one notch up) the hiss disappears. 
  20.00, 20.00 cause a louder hiss and 
  30.00, 30.00 causes an even louder hiss with high frequency audio artifacts. 

  When the headphones are removed and plugged back in the Headphone Mic
  Boost setting returns to dB gain 0 and the problem also returns.

  This (problem and workaround) has been reported in the wild:
  https://news.ycombinator.com/item?id=13050843 and
  
https://www.reddit.com/r/Dell/comments/4j1zz4/headphones_have_static_noise_with_ubuntu_1604_on/
  for example

To manage notifications about this bug go to:
https://bugs.launchpad.net/dell-sputnik/+bug/1654448/+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 1515513] Re: /boot/initrd.img-*.old-dkms files left behind

2017-05-08 Thread Jared Dominguez
DKMS is a Dell project but not Project Sputnik. Marking as invalid for
dell-sputnik.

** Changed in: dell-sputnik
   Status: New => Invalid

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

Title:
  /boot/initrd.img-*.old-dkms files left behind

Status in Dell Sputnik:
  Invalid
Status in dkms package in Ubuntu:
  Confirmed
Status in initramfs-tools package in Ubuntu:
  Confirmed
Status in dkms package in Debian:
  New

Bug description:
  One notices *.old-dkms files being left behind still sitting on the
  disk after purging the related kernel. This can cause /boot to become
  full, and when it gets really bad, even sudo apt-get autoremove won't
  fix the problem - only deleting the old-dkms files manually solves the
  problem.

  Note:  Filling up the /boot partition causes updates to fail.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: dkms 2.2.0.3-2ubuntu3.3
  ProcVersionSignature: Ubuntu 3.19.0-28.30-generic 3.19.8-ckt5
  Uname: Linux 3.19.0-28-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.7
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Thu Nov 12 08:17:10 2015
  InstallationDate: Installed on 2015-05-05 (190 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  PackageArchitecture: all
  SourcePackage: dkms
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/dell-sputnik/+bug/1515513/+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 1688317] Re: PCI/internal sound card not detected

2017-05-08 Thread Jared Dominguez
You're running a non-OEM version of Ubuntu 16.04.1, which is too old to
fully support this platform. Canonical maintains driver backports for
this platform only for factory-installed Ubuntu 16.04, and that includes
backport DKMS packages. Either wait until this is backported to a later
Ubuntu 16.04 point release, use a later version of Ubuntu or purchase
with Ubuntu pre-installed instead of Windows.

** Changed in: dell-sputnik
   Status: New => Invalid

** Changed in: alsa-driver (Ubuntu)
   Status: New => Invalid

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

Title:
  PCI/internal sound card not detected

Status in Dell Sputnik:
  Invalid
Status in alsa-driver package in Ubuntu:
  Invalid

Bug description:
  No sound card detected at all, no sound for laptop/bluetooth
  headphones

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-77.98-generic 4.4.59
  Uname: Linux 4.4.0-77-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: Unity
  Date: Thu May  4 10:41:20 2017
  InstallationDate: Installed on 2017-01-25 (98 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Title: PCI/internal sound card not detected
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/18/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.3.2
  dmi.board.name: 0T3FTF
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.3.2:bd01/18/2017:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn0T3FTF:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 13 9360
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/dell-sputnik/+bug/1688317/+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 1650259] Re: [XPS 13 9350, Realtek ALC3246, Speaker, Internal] No sound at all from the headphone jack

2017-05-08 Thread Jared Dominguez
Have you checked in the system settings GUI whether the headphone jack
shows as an output option?

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

Title:
  [XPS 13 9350, Realtek ALC3246, Speaker, Internal] No sound at all from
  the headphone jack

Status in Dell Sputnik:
  New
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  The problem is that there is no sound at the jack for the headphones.

  Internal speaker are silenced when inserted a headphone jack but there is no 
sound output.
  Tested a live MS windows and sound worked!

  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: pulseaudio 1:8.0-0ubuntu3.1
  ProcVersionSignature: Ubuntu 4.4.0-53.74-generic 4.4.30
  Uname: Linux 4.4.0-53-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jaki   2355 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu Dec 15 12:41:55 2016
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-trusty-amd64-osp1-20150720-0
  InstallationDate: Installed on 2016-06-25 (173 days ago)
  InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 
20150720-04:06
  ProcEnviron:
   LANGUAGE=it
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
  Symptom_Card: Audio interno - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jaki   2355 F pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_PulsePlaybackTest: PulseAudio playback test failed
  Symptom_Type: No sound at all
  Title: [XPS 13 9350, Realtek ALC3246, Speaker, Internal] No sound at all
  UpgradeStatus: Upgraded to xenial on 2016-09-07 (98 days ago)
  dmi.bios.date: 06/14/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.4.4
  dmi.board.name: 0H67KH
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A03
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.4.4:bd06/14/2016:svnDellInc.:pnXPS139350:pvr:rvnDellInc.:rn0H67KH:rvrA03:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 13 9350
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/dell-sputnik/+bug/1650259/+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 1651433] Re: bluetooth mouse random disconnects

2017-01-03 Thread Jared Dominguez
It looks like on OEM systems, we tweak /etc/bluetooth/main.conf by
adding "AutoEnable=true". Can you check what that's set to on your
system?

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

Title:
  bluetooth mouse random disconnects

Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  I received the Dell XPS 13 DE (9350) accompanied by the WD15 docking station 
last September. Ever since I used it with my Logitech MX Master bluetooth mouse.
  This worked very well and reliably for September through November.
  But Since about start of December, it disconnects frequently and without any 
apparent reason.
  I can get it back to order by disabling and re-enabling the bluetooth radio 
of the notebook. After I re-enable the bt radio and move the mouse it work 
immediately without any delay.
  Sometimes it disconnects after 10 seconds. Sometimes I can work for 10 hours 
without any disconnect.
  For the entire lifetime the device has been running xenial. Currently I'm on 
kernel Linux XPS13ulr 4.4.0-53-generic #74-Ubuntu SMP
  Because the issue started happening at a certain date, I strongly believe 
that it was caused by and upgrade, possibly kernel.

  I wanted to see if the same disconnects also happen with other BT devices. 
But for as long as I had the Jabra Halo 2 headset connected, also the mouse 
worked reliably. 
  The mouse is my only BT LE device. Maybe that makes a difference.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1651433/+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 1550538] Re: periodically after suspend/resume wpasupplicant fails to authenticate

2016-02-29 Thread Jared Dominguez
Also tracked at https://bugs.launchpad.net/somerville/+bug/1551518

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

Title:
  periodically after suspend/resume wpasupplicant fails to authenticate

Status in wpa package in Ubuntu:
  New

Bug description:
  After suspending and resuming, periodically wpasupplicant fails to
  reauthenticate. I'm prompted for a password to reconnect. I enabled
  debugging for wpasupplicant. Something that draws attention is seeing
  "wlan0: WPA: 4-Way Handshake failed - pre-shared key may be
  incorrect". This is with the Ubuntu 14.04 OEM image for the Dell
  Precision 5510. All updates have been installed.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: wpasupplicant 2.1-0ubuntu1.4 [modified: 
usr/share/dbus-1/system-services/fi.w1.wpa_supplicant1.service]
  ProcVersionSignature: Ubuntu 3.19.0-33.38~14.04.1-generic 3.19.8-ckt7
  Uname: Linux 3.19.0-33-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Feb 26 13:38:06 2016
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-trusty-amd64-osp1-20150721-1
  InstallationDate: Installed on 2016-02-25 (1 days ago)
  InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 
20150721-23:28
  SourcePackage: wpa
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1550538/+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 1550504] Re: lightdm unresponsive after suspend

2016-02-29 Thread Jared Dominguez
Also tracked at https://bugs.launchpad.net/somerville/+bug/1551514

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

Title:
  lightdm unresponsive after suspend

Status in lightdm package in Ubuntu:
  New

Bug description:
  I'm using an Ubuntu OEM image on the Dell Precision 5510. After
  unboxing and applying all updates (running apt-get update/upgrade
  multiple times), if I suspend the system, when it comes back (or also
  after failing to suspend), lightdm does not show a password field, and
  selecting my username does not bring up a password field. If I click
  on the gear in the upper right corner, I can choose to switch
  accounts; doing that, after several seconds, lightdm comes back, and I
  can unlock the user session.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: lightdm 1.10.6-0ubuntu1
  ProcVersionSignature: Ubuntu 3.19.0-33.38~14.04.1-generic 3.19.8-ckt7
  Uname: Linux 3.19.0-33-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Feb 26 11:53:36 2016
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-trusty-amd64-osp1-20150721-1
  InstallationDate: Installed on 2016-02-25 (1 days ago)
  InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 
20150721-23:28
  LightdmConfig:
   [SeatDefaults]
   autologin-guest=false
   autologin-user-timeout=0
   autologin-session=lightdm-autologin
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1550504/+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 1550490] Re: network-manager unresponsive after suspend

2016-02-29 Thread Jared Dominguez
Also tracked at https://bugs.launchpad.net/somerville/+bug/1551516

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

Title:
  network-manager unresponsive after suspend

Status in network-manager package in Ubuntu:
  New

Bug description:
  I'm using an Ubuntu OEM image on the Dell Precision 5510. After
  unboxing and applying all updates (running apt-get update/upgrade
  multiple times), if I suspend the system, when it comes back,
  networking shows as "disabled". The network interfaces however are
  still up. Once I kill the NetworkManager process, networking comes
  back.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: network-manager 0.9.8.8-0ubuntu7.2
  ProcVersionSignature: Ubuntu 3.19.0-33.38~14.04.1-generic 3.19.8-ckt7
  Uname: Linux 3.19.0-33-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Feb 26 11:43:28 2016
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-trusty-amd64-osp1-20150721-1
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2016-02-25 (1 days ago)
  InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 
20150721-23:28
  IpRoute:
   default via 172.24.64.1 dev wlan0  proto static 
   172.24.64.0/19 dev wlan0  proto kernel  scope link  src 172.24.67.197  
metric 9
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAME  UUID   TYPE
  TIMESTAMPTIMESTAMP-REAL AUTOCONNECT   READONLY   
DBUS-PATH 
   sfo3  aa8c189d-e8dd-429b-948f-025579dfbe33   
802-11-wireless   1456515772   Fri 26 Feb 2016 11:42:52 AM PSTyes   
no /org/freedesktop/NetworkManager/Settings/0
  nmcli-dev:
   DEVICE TYPE  STATE DBUS-PATH 
 
   wlan0  802-11-wireless   connected 
/org/freedesktop/NetworkManager/Devices/0
  nmcli-nm:
   RUNNING VERSIONSTATE   NET-ENABLED   WIFI-HARDWARE   
WIFI   WWAN-HARDWARE   WWAN  
   running 0.9.8.8connected   enabled   enabled 
enabledenabled disabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1550490/+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 1550490] Re: network-manager unresponsive after suspend

2016-02-29 Thread Jared Dominguez
Note that trying to turn on and off the wireless card using the wireless
hotkey did not help. As can be seen from the logs, NM reports wifi's
killswitch status change but still does not see any APs or try
reconnecting.

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

Title:
  network-manager unresponsive after suspend

Status in network-manager package in Ubuntu:
  New

Bug description:
  I'm using an Ubuntu OEM image on the Dell Precision 5510. After
  unboxing and applying all updates (running apt-get update/upgrade
  multiple times), if I suspend the system, when it comes back,
  networking shows as "disabled". The network interfaces however are
  still up. Once I kill the NetworkManager process, networking comes
  back.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: network-manager 0.9.8.8-0ubuntu7.2
  ProcVersionSignature: Ubuntu 3.19.0-33.38~14.04.1-generic 3.19.8-ckt7
  Uname: Linux 3.19.0-33-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Feb 26 11:43:28 2016
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-trusty-amd64-osp1-20150721-1
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2016-02-25 (1 days ago)
  InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 
20150721-23:28
  IpRoute:
   default via 172.24.64.1 dev wlan0  proto static 
   172.24.64.0/19 dev wlan0  proto kernel  scope link  src 172.24.67.197  
metric 9
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAME  UUID   TYPE
  TIMESTAMPTIMESTAMP-REAL AUTOCONNECT   READONLY   
DBUS-PATH 
   sfo3  aa8c189d-e8dd-429b-948f-025579dfbe33   
802-11-wireless   1456515772   Fri 26 Feb 2016 11:42:52 AM PSTyes   
no /org/freedesktop/NetworkManager/Settings/0
  nmcli-dev:
   DEVICE TYPE  STATE DBUS-PATH 
 
   wlan0  802-11-wireless   connected 
/org/freedesktop/NetworkManager/Devices/0
  nmcli-nm:
   RUNNING VERSIONSTATE   NET-ENABLED   WIFI-HARDWARE   
WIFI   WWAN-HARDWARE   WWAN  
   running 0.9.8.8connected   enabled   enabled 
enabledenabled disabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1550490/+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 1550538] Re: periodically after suspend/resume wpasupplicant fails to authenticate

2016-02-29 Thread Jared Dominguez
The failure was seen with WPA2 Personal with an Aruba access point.

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

Title:
  periodically after suspend/resume wpasupplicant fails to authenticate

Status in wpa package in Ubuntu:
  New

Bug description:
  After suspending and resuming, periodically wpasupplicant fails to
  reauthenticate. I'm prompted for a password to reconnect. I enabled
  debugging for wpasupplicant. Something that draws attention is seeing
  "wlan0: WPA: 4-Way Handshake failed - pre-shared key may be
  incorrect". This is with the Ubuntu 14.04 OEM image for the Dell
  Precision 5510. All updates have been installed.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: wpasupplicant 2.1-0ubuntu1.4 [modified: 
usr/share/dbus-1/system-services/fi.w1.wpa_supplicant1.service]
  ProcVersionSignature: Ubuntu 3.19.0-33.38~14.04.1-generic 3.19.8-ckt7
  Uname: Linux 3.19.0-33-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Feb 26 13:38:06 2016
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-trusty-amd64-osp1-20150721-1
  InstallationDate: Installed on 2016-02-25 (1 days ago)
  InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 
20150721-23:28
  SourcePackage: wpa
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1550538/+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 1550490] Re: network-manager unresponsive after suspend

2016-02-29 Thread Jared Dominguez
This occurred about every five to ten reboots.

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

Title:
  network-manager unresponsive after suspend

Status in network-manager package in Ubuntu:
  New

Bug description:
  I'm using an Ubuntu OEM image on the Dell Precision 5510. After
  unboxing and applying all updates (running apt-get update/upgrade
  multiple times), if I suspend the system, when it comes back,
  networking shows as "disabled". The network interfaces however are
  still up. Once I kill the NetworkManager process, networking comes
  back.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: network-manager 0.9.8.8-0ubuntu7.2
  ProcVersionSignature: Ubuntu 3.19.0-33.38~14.04.1-generic 3.19.8-ckt7
  Uname: Linux 3.19.0-33-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Feb 26 11:43:28 2016
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-trusty-amd64-osp1-20150721-1
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2016-02-25 (1 days ago)
  InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 
20150721-23:28
  IpRoute:
   default via 172.24.64.1 dev wlan0  proto static 
   172.24.64.0/19 dev wlan0  proto kernel  scope link  src 172.24.67.197  
metric 9
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAME  UUID   TYPE
  TIMESTAMPTIMESTAMP-REAL AUTOCONNECT   READONLY   
DBUS-PATH 
   sfo3  aa8c189d-e8dd-429b-948f-025579dfbe33   
802-11-wireless   1456515772   Fri 26 Feb 2016 11:42:52 AM PSTyes   
no /org/freedesktop/NetworkManager/Settings/0
  nmcli-dev:
   DEVICE TYPE  STATE DBUS-PATH 
 
   wlan0  802-11-wireless   connected 
/org/freedesktop/NetworkManager/Devices/0
  nmcli-nm:
   RUNNING VERSIONSTATE   NET-ENABLED   WIFI-HARDWARE   
WIFI   WWAN-HARDWARE   WWAN  
   running 0.9.8.8connected   enabled   enabled 
enabledenabled disabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1550490/+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 1550504] Re: lightdm unresponsive after suspend

2016-02-29 Thread Jared Dominguez
I can't reproduce on a system with the FHD panel. It may be restricted
to the UHD model.

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

Title:
  lightdm unresponsive after suspend

Status in lightdm package in Ubuntu:
  New

Bug description:
  I'm using an Ubuntu OEM image on the Dell Precision 5510. After
  unboxing and applying all updates (running apt-get update/upgrade
  multiple times), if I suspend the system, when it comes back (or also
  after failing to suspend), lightdm does not show a password field, and
  selecting my username does not bring up a password field. If I click
  on the gear in the upper right corner, I can choose to switch
  accounts; doing that, after several seconds, lightdm comes back, and I
  can unlock the user session.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: lightdm 1.10.6-0ubuntu1
  ProcVersionSignature: Ubuntu 3.19.0-33.38~14.04.1-generic 3.19.8-ckt7
  Uname: Linux 3.19.0-33-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Feb 26 11:53:36 2016
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-trusty-amd64-osp1-20150721-1
  InstallationDate: Installed on 2016-02-25 (1 days ago)
  InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 
20150721-23:28
  LightdmConfig:
   [SeatDefaults]
   autologin-guest=false
   autologin-user-timeout=0
   autologin-session=lightdm-autologin
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1550504/+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 1550490] Re: network-manager unresponsive after suspend

2016-02-29 Thread Jared Dominguez
The failure was seen with WPA2 Personal with an Aruba access point.

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

Title:
  network-manager unresponsive after suspend

Status in network-manager package in Ubuntu:
  New

Bug description:
  I'm using an Ubuntu OEM image on the Dell Precision 5510. After
  unboxing and applying all updates (running apt-get update/upgrade
  multiple times), if I suspend the system, when it comes back,
  networking shows as "disabled". The network interfaces however are
  still up. Once I kill the NetworkManager process, networking comes
  back.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: network-manager 0.9.8.8-0ubuntu7.2
  ProcVersionSignature: Ubuntu 3.19.0-33.38~14.04.1-generic 3.19.8-ckt7
  Uname: Linux 3.19.0-33-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Feb 26 11:43:28 2016
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-trusty-amd64-osp1-20150721-1
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2016-02-25 (1 days ago)
  InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 
20150721-23:28
  IpRoute:
   default via 172.24.64.1 dev wlan0  proto static 
   172.24.64.0/19 dev wlan0  proto kernel  scope link  src 172.24.67.197  
metric 9
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAME  UUID   TYPE
  TIMESTAMPTIMESTAMP-REAL AUTOCONNECT   READONLY   
DBUS-PATH 
   sfo3  aa8c189d-e8dd-429b-948f-025579dfbe33   
802-11-wireless   1456515772   Fri 26 Feb 2016 11:42:52 AM PSTyes   
no /org/freedesktop/NetworkManager/Settings/0
  nmcli-dev:
   DEVICE TYPE  STATE DBUS-PATH 
 
   wlan0  802-11-wireless   connected 
/org/freedesktop/NetworkManager/Devices/0
  nmcli-nm:
   RUNNING VERSIONSTATE   NET-ENABLED   WIFI-HARDWARE   
WIFI   WWAN-HARDWARE   WWAN  
   running 0.9.8.8connected   enabled   enabled 
enabledenabled disabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1550490/+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 1550538] [NEW] periodically after suspend/resume wpasupplicant fails to authenticate

2016-02-26 Thread Jared Dominguez
Public bug reported:

After suspending and resuming, periodically wpasupplicant fails to
reauthenticate. I'm prompted for a password to reconnect. I enabled
debugging for wpasupplicant. Something that draws attention is seeing
"wlan0: WPA: 4-Way Handshake failed - pre-shared key may be incorrect".
This is with the Ubuntu 14.04 OEM image for the Dell Precision 5510. All
updates have been installed.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: wpasupplicant 2.1-0ubuntu1.4 [modified: 
usr/share/dbus-1/system-services/fi.w1.wpa_supplicant1.service]
ProcVersionSignature: Ubuntu 3.19.0-33.38~14.04.1-generic 3.19.8-ckt7
Uname: Linux 3.19.0-33-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.19
Architecture: amd64
CurrentDesktop: Unity
Date: Fri Feb 26 13:38:06 2016
DistributionChannelDescriptor:
 # This is a distribution channel descriptor
 # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor
 canonical-oem-somerville-trusty-amd64-osp1-20150721-1
InstallationDate: Installed on 2016-02-25 (1 days ago)
InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 
20150721-23:28
SourcePackage: wpa
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug trusty

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

Title:
  periodically after suspend/resume wpasupplicant fails to authenticate

Status in wpa package in Ubuntu:
  New

Bug description:
  After suspending and resuming, periodically wpasupplicant fails to
  reauthenticate. I'm prompted for a password to reconnect. I enabled
  debugging for wpasupplicant. Something that draws attention is seeing
  "wlan0: WPA: 4-Way Handshake failed - pre-shared key may be
  incorrect". This is with the Ubuntu 14.04 OEM image for the Dell
  Precision 5510. All updates have been installed.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: wpasupplicant 2.1-0ubuntu1.4 [modified: 
usr/share/dbus-1/system-services/fi.w1.wpa_supplicant1.service]
  ProcVersionSignature: Ubuntu 3.19.0-33.38~14.04.1-generic 3.19.8-ckt7
  Uname: Linux 3.19.0-33-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Feb 26 13:38:06 2016
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-trusty-amd64-osp1-20150721-1
  InstallationDate: Installed on 2016-02-25 (1 days ago)
  InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 
20150721-23:28
  SourcePackage: wpa
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1550538/+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 1550504] [NEW] lightdm unresponsive after suspend

2016-02-26 Thread Jared Dominguez
Public bug reported:

I'm using an Ubuntu OEM image on the Dell Precision 5510. After unboxing
and applying all updates (running apt-get update/upgrade multiple
times), if I suspend the system, when it comes back (or also after
failing to suspend), lightdm does not show a password field, and
selecting my username does not bring up a password field. If I click on
the gear in the upper right corner, I can choose to switch accounts;
doing that, after several seconds, lightdm comes back, and I can unlock
the user session.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: lightdm 1.10.6-0ubuntu1
ProcVersionSignature: Ubuntu 3.19.0-33.38~14.04.1-generic 3.19.8-ckt7
Uname: Linux 3.19.0-33-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.19
Architecture: amd64
CurrentDesktop: Unity
Date: Fri Feb 26 11:53:36 2016
DistributionChannelDescriptor:
 # This is a distribution channel descriptor
 # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor
 canonical-oem-somerville-trusty-amd64-osp1-20150721-1
InstallationDate: Installed on 2016-02-25 (1 days ago)
InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 
20150721-23:28
LightdmConfig:
 [SeatDefaults]
 autologin-guest=false
 autologin-user-timeout=0
 autologin-session=lightdm-autologin
SourcePackage: lightdm
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug third-party-packages trusty

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

Title:
  lightdm unresponsive after suspend

Status in lightdm package in Ubuntu:
  New

Bug description:
  I'm using an Ubuntu OEM image on the Dell Precision 5510. After
  unboxing and applying all updates (running apt-get update/upgrade
  multiple times), if I suspend the system, when it comes back (or also
  after failing to suspend), lightdm does not show a password field, and
  selecting my username does not bring up a password field. If I click
  on the gear in the upper right corner, I can choose to switch
  accounts; doing that, after several seconds, lightdm comes back, and I
  can unlock the user session.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: lightdm 1.10.6-0ubuntu1
  ProcVersionSignature: Ubuntu 3.19.0-33.38~14.04.1-generic 3.19.8-ckt7
  Uname: Linux 3.19.0-33-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Feb 26 11:53:36 2016
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-trusty-amd64-osp1-20150721-1
  InstallationDate: Installed on 2016-02-25 (1 days ago)
  InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 
20150721-23:28
  LightdmConfig:
   [SeatDefaults]
   autologin-guest=false
   autologin-user-timeout=0
   autologin-session=lightdm-autologin
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1550504/+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 1550490] [NEW] network-manager unresponsive after suspend

2016-02-26 Thread Jared Dominguez
Public bug reported:

I'm using an Ubuntu OEM image on the Dell Precision 5510. After unboxing
and applying all updates (running apt-get update/upgrade multiple
times), if I suspend the system, when it comes back, networking shows as
"disabled". The network interfaces however are still up. Once I kill the
NetworkManager process, networking comes back.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: network-manager 0.9.8.8-0ubuntu7.2
ProcVersionSignature: Ubuntu 3.19.0-33.38~14.04.1-generic 3.19.8-ckt7
Uname: Linux 3.19.0-33-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.19
Architecture: amd64
CurrentDesktop: Unity
Date: Fri Feb 26 11:43:28 2016
DistributionChannelDescriptor:
 # This is a distribution channel descriptor
 # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor
 canonical-oem-somerville-trusty-amd64-osp1-20150721-1
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
InstallationDate: Installed on 2016-02-25 (1 days ago)
InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 
20150721-23:28
IpRoute:
 default via 172.24.64.1 dev wlan0  proto static 
 172.24.64.0/19 dev wlan0  proto kernel  scope link  src 172.24.67.197  metric 9
NetworkManager.state:
 [main]
 NetworkingEnabled=true
 WirelessEnabled=true
 WWANEnabled=true
 WimaxEnabled=true
SourcePackage: network-manager
UpgradeStatus: No upgrade log present (probably fresh install)
nmcli-con:
 NAME  UUID   TYPE  
TIMESTAMPTIMESTAMP-REAL AUTOCONNECT   READONLY   
DBUS-PATH 
 sfo3  aa8c189d-e8dd-429b-948f-025579dfbe33   
802-11-wireless   1456515772   Fri 26 Feb 2016 11:42:52 AM PSTyes   
no /org/freedesktop/NetworkManager/Settings/0
nmcli-dev:
 DEVICE TYPE  STATE DBUS-PATH   
   
 wlan0  802-11-wireless   connected 
/org/freedesktop/NetworkManager/Devices/0
nmcli-nm:
 RUNNING VERSIONSTATE   NET-ENABLED   WIFI-HARDWARE   WIFI  
 WWAN-HARDWARE   WWAN  
 running 0.9.8.8connected   enabled   enabled 
enabledenabled disabled

** Affects: network-manager (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug trusty

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

Title:
  network-manager unresponsive after suspend

Status in network-manager package in Ubuntu:
  New

Bug description:
  I'm using an Ubuntu OEM image on the Dell Precision 5510. After
  unboxing and applying all updates (running apt-get update/upgrade
  multiple times), if I suspend the system, when it comes back,
  networking shows as "disabled". The network interfaces however are
  still up. Once I kill the NetworkManager process, networking comes
  back.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: network-manager 0.9.8.8-0ubuntu7.2
  ProcVersionSignature: Ubuntu 3.19.0-33.38~14.04.1-generic 3.19.8-ckt7
  Uname: Linux 3.19.0-33-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Feb 26 11:43:28 2016
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-trusty-amd64-osp1-20150721-1
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2016-02-25 (1 days ago)
  InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 
20150721-23:28
  IpRoute:
   default via 172.24.64.1 dev wlan0  proto static 
   172.24.64.0/19 dev wlan0  proto kernel  scope link  src 172.24.67.197  
metric 9
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAME  UUID   TYPE
  TIMESTAMPTIMESTAMP-REAL AUTOCONNECT   READONLY   
DBUS-PATH 
   sfo3  aa8c189d-e8dd-429b-948f-025579dfbe33   
802-11-wireless   1456515772   Fri 26 Feb 2016 11:42:52 AM PSTyes   
no /org/freedesktop/NetworkManager/Settings/0
  nmcli-dev:
   DEVICE TYPE  STATE DBUS-PATH 
 
   wlan0  802-11-wireless   connected 
/org/freedesktop/NetworkManager/Devices/0
  nmcli-nm:
   RUNNING VERSIONSTATE   NET-ENABLED   WIFI-HARDWARE   
WIFI   WWAN-HARDWARE   WWAN  
   running 

[Touch-packages] [Bug 1510339] Re: 5GHz network is not available after suspend by closing lid

2015-10-26 Thread Jared Dominguez
** Also affects: dell-sputnik
   Importance: Undecided
   Status: New

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

Title:
  5GHz network is not available after suspend by closing lid

Status in Dell Sputnik:
  New
Status in network-manager package in Ubuntu:
  New

Bug description:
  Model: Dell XPS 13 - 9343
  Network controller: Broadcom Corporation BCM4352 802.11ac Wireless Network 
Adapter (rev 03)

  Action: close lid of laptop to suspend, open lid to resume

  Expected behavior: Wireless would resume with access to 2.4Ghz and
  5Ghz networks

  Actual Behavior: Wireless resumes, but 5Ghz networks are not detected

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: network-manager 0.9.10.0-4ubuntu15.3
  ProcVersionSignature: Ubuntu 3.19.0-31.36-generic 3.19.8-ckt7
  Uname: Linux 3.19.0-31-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.17.2-0ubuntu1.5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Oct 26 21:08:17 2015
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2015-10-25 (1 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  IpRoute:
   default via 192.168.1.1 dev eth0  proto static  metric 100 
   169.254.0.0/16 dev eth0  scope link  metric 1000 
   192.168.1.0/24 dev eth0  proto kernel  scope link  metric 100
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAMEUUID  TYPE
TIMESTAMP   TIMESTAMP-REAL   AUTOCONNECT  READONLY  DBUS-PATH   
ACTIVE  DEVICE  STATE  ACTIVE-PATH  
  
   Wired connection 1  6c91668c-4496-4a76-b636-2aba7ee0fdac  802-3-ethernet  
1445907849  Mon 26 Oct 2015 09:04:09 PM EDT  yes  no
/org/freedesktop/NetworkManager/Settings/0  yes eth0activated  
/org/freedesktop/NetworkManager/ActiveConnection/3 
   Nexus 4 Network 4c6152f2-6c3a-425e-a91d-13faad5ed602  bluetooth   0  
 neverno   no
/org/freedesktop/NetworkManager/Settings/3  no  --  -- --
  nmcli-dev:
   DEVICE TYPE  STATE DBUS-PATH 
 CONNECTION  CON-UUID  CON-PATH 
  
   eth0   ethernet  connected 
/org/freedesktop/NetworkManager/Devices/2  Wired connection 1  
6c91668c-4496-4a76-b636-2aba7ee0fdac  
/org/freedesktop/NetworkManager/ActiveConnection/3 
   98:D6:F7:2E:39:53  btdisconnected  
/org/freedesktop/NetworkManager/Devices/5  --  --   
 -- 
   wlan0  wifi  disconnected  
/org/freedesktop/NetworkManager/Devices/1  --  --   
 -- 
   lo loopback  unmanaged 
/org/freedesktop/NetworkManager/Devices/0  --  --   
 --
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 
2: Error: Object 'nm' is unknown, try 'nmcli help'.

To manage notifications about this bug go to:
https://bugs.launchpad.net/dell-sputnik/+bug/1510339/+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 1500387] Re: System boots to a black screen and the customer has to close the lid and reopen it to trigger a DPMS event and then video is restored

2015-10-18 Thread Daniel Jared Dominguez
** Also affects: dell-sputnik
   Importance: Undecided
   Status: New

-- 
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/1500387

Title:
  System boots to a black screen and the customer has to close the lid
  and reopen it to trigger a DPMS event and then video is restored

Status in Dell Sputnik:
  New
Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  [Summary]
  System boots to a black screen and the customer has to close the lid and 
reopen it to trigger a DPMS event and then video is restored

  [Reproduce Steps]
  1. System boots to a black screen
  2. Close the lid and reopen it

  [Results]
  Expected: Normal boot
  Actual: Blank screen

  [Additional Information]
  CID:
  Base Image:
  Product Name: "Ubuntu 14.04.3 LTS" on Dell XPS 13 9343
  BIOS Version: A05
  Kernel Version: 3.13.0-63-generic
  CPU: Intel(R) Core(TM) i5-5200U CPU @ 2.20GHz
  GPU: Intel Corporation Broadwell-U Integrated Graphics (rev 09)

To manage notifications about this bug go to:
https://bugs.launchpad.net/dell-sputnik/+bug/1500387/+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 1423415] Re: [XPS 13 9343, Realtek ALC3263, Speaker, Internal] Volume hotkeys stopped working in Ubuntu 15.04

2015-02-19 Thread Daniel Jared Dominguez
** Summary changed:

- [XPS 13 9343, Realtek ALC3263, Speaker, Internal] Volume hotkeys stopped 
working in Ubuntu 15.10
+ [XPS 13 9343, Realtek ALC3263, Speaker, Internal] Volume hotkeys stopped 
working in Ubuntu 15.04

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

Title:
  [XPS 13 9343, Realtek ALC3263, Speaker, Internal] Volume hotkeys
  stopped working in Ubuntu 15.04

Status in Dell Sputnik:
  New
Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Volume hotkeys were working and now they're not. A coworker has
  another 2015 XPS 13 (model 9343) with Ubuntu 15.04. He hasn't updated
  in a week, and the hotkeys function, so it seems like the bug came up
  sometime in the past week.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.18.0-13.14-generic 3.18.5
  Uname: Linux 3.18.0-13-generic x86_64
  ApportVersion: 2.16.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D0c:   jared  4299 F...m arecord
   /dev/snd/controlC1:  jared  2929 F pulseaudio
   /dev/snd/controlC0:  jared  2929 F pulseaudio
  CurrentDesktop: Unity
  Date: Wed Feb 18 19:49:30 2015
  InstallationDate: Installed on 2014-11-03 (107 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 
(20140722.2)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Speaker, Internal
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: None of the above
  Title: [XPS 13 9343, Realtek ALC3263, Speaker, Internal] Playback problem
  UpgradeStatus: Upgraded to vivid on 2015-01-08 (41 days ago)
  dmi.bios.date: 02/03/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A01
  dmi.board.name: 0144PA
  dmi.board.vendor: Dell Inc.
  dmi.board.version: X04
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA01:bd02/03/2015:svnDellInc.:pnXPS139343:pvr01:rvnDellInc.:rn0144PA:rvrX04:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 13 9343
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/dell-sputnik/+bug/1423415/+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 1423415] [NEW] [XPS 13 9343, Realtek ALC3263, Speaker, Internal] Volume hotkeys stopped working in Ubuntu 15.10

2015-02-18 Thread Daniel Jared Dominguez
Public bug reported:

Volume hotkeys were working and now they're not. A coworker has another
2015 XPS 13 (model 9343) with Ubuntu 15.04. He hasn't updated in a week,
and the hotkeys function, so it seems like the bug came up sometime in
the past week.

ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: alsa-base 1.0.25+dfsg-0ubuntu4
ProcVersionSignature: Ubuntu 3.18.0-13.14-generic 3.18.5
Uname: Linux 3.18.0-13-generic x86_64
ApportVersion: 2.16.1-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/pcmC1D0c:   jared  4299 F...m arecord
 /dev/snd/controlC1:  jared  2929 F pulseaudio
 /dev/snd/controlC0:  jared  2929 F pulseaudio
CurrentDesktop: Unity
Date: Wed Feb 18 19:49:30 2015
InstallationDate: Installed on 2014-11-03 (107 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
Symptom_Card: Built-in Audio - HDA Intel PCH
Symptom_Jack: Speaker, Internal
Symptom_PulsePlaybackTest: PulseAudio playback test successful
Symptom_Type: None of the above
Title: [XPS 13 9343, Realtek ALC3263, Speaker, Internal] Playback problem
UpgradeStatus: Upgraded to vivid on 2015-01-08 (41 days ago)
dmi.bios.date: 02/03/2015
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A01
dmi.board.name: 0144PA
dmi.board.vendor: Dell Inc.
dmi.board.version: X04
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvrA01:bd02/03/2015:svnDellInc.:pnXPS139343:pvr01:rvnDellInc.:rn0144PA:rvrX04:cvnDellInc.:ct9:cvr:
dmi.product.name: XPS 13 9343
dmi.product.version: 01
dmi.sys.vendor: Dell Inc.

** Affects: dell-sputnik
 Importance: Undecided
 Status: New

** Affects: alsa-driver (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug vivid

** Also affects: dell-sputnik
   Importance: Undecided
   Status: New

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

Title:
  [XPS 13 9343, Realtek ALC3263, Speaker, Internal] Volume hotkeys
  stopped working in Ubuntu 15.10

Status in Dell Sputnik:
  New
Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Volume hotkeys were working and now they're not. A coworker has
  another 2015 XPS 13 (model 9343) with Ubuntu 15.04. He hasn't updated
  in a week, and the hotkeys function, so it seems like the bug came up
  sometime in the past week.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.18.0-13.14-generic 3.18.5
  Uname: Linux 3.18.0-13-generic x86_64
  ApportVersion: 2.16.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D0c:   jared  4299 F...m arecord
   /dev/snd/controlC1:  jared  2929 F pulseaudio
   /dev/snd/controlC0:  jared  2929 F pulseaudio
  CurrentDesktop: Unity
  Date: Wed Feb 18 19:49:30 2015
  InstallationDate: Installed on 2014-11-03 (107 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 
(20140722.2)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Speaker, Internal
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: None of the above
  Title: [XPS 13 9343, Realtek ALC3263, Speaker, Internal] Playback problem
  UpgradeStatus: Upgraded to vivid on 2015-01-08 (41 days ago)
  dmi.bios.date: 02/03/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A01
  dmi.board.name: 0144PA
  dmi.board.vendor: Dell Inc.
  dmi.board.version: X04
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA01:bd02/03/2015:svnDellInc.:pnXPS139343:pvr01:rvnDellInc.:rn0144PA:rvrX04:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 13 9343
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/dell-sputnik/+bug/1423415/+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 1423413] [NEW] [XPS 13 9343, Realtek ALC3263, Mic, Internal] No sound at all

2015-02-18 Thread Daniel Jared Dominguez
Public bug reported:

Note that I am forcing the audio into HDA mode. (It has two modes: HDA
and I2S.) In HDA mode, audio out works. The mic is known with a previous
version of ALSA (Sept 3 2014 snapshot).

ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: alsa-base 1.0.25+dfsg-0ubuntu4
ProcVersionSignature: Ubuntu 3.18.0-13.14-generic 3.18.5
Uname: Linux 3.18.0-13-generic x86_64
ApportVersion: 2.16.1-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/pcmC1D0c:   jared  4299 F...m arecord
 /dev/snd/pcmC1D0p:   jared  2929 F...m pulseaudio
 /dev/snd/controlC1:  jared  2929 F pulseaudio
 /dev/snd/controlC0:  jared  2929 F pulseaudio
CurrentDesktop: Unity
Date: Wed Feb 18 19:40:01 2015
InstallationDate: Installed on 2014-11-03 (107 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaRecordingPlaybackStderr: o p e n ( ) :   N o   s u c h   f i l e   
o r   d i r e c t o r y
Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed
Symptom_AlsaRecordingTestStderr: a r e c o r d :   m a i n : 7 2 2 :   a u d i 
o   o p e n   e r r o r :   D e v i c e   o r   r e s o u r c e   b u s y
Symptom_Card: Built-in Audio - HDA Intel PCH
Symptom_DevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/pcmC1D0c:   jared  4299 F...m arecord
 /dev/snd/controlC1:  jared  2929 F pulseaudio
 /dev/snd/controlC0:  jared  2929 F pulseaudio
Symptom_Jack: Mic, Internal
Symptom_Type: No sound at all
Title: [XPS 13 9343, Realtek ALC3263, Mic, Internal] No sound at all
UpgradeStatus: Upgraded to vivid on 2015-01-08 (41 days ago)
dmi.bios.date: 02/03/2015
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A01
dmi.board.name: 0144PA
dmi.board.vendor: Dell Inc.
dmi.board.version: X04
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvrA01:bd02/03/2015:svnDellInc.:pnXPS139343:pvr01:rvnDellInc.:rn0144PA:rvrX04:cvnDellInc.:ct9:cvr:
dmi.product.name: XPS 13 9343
dmi.product.version: 01
dmi.sys.vendor: Dell Inc.

** Affects: dell-sputnik
 Importance: Undecided
 Status: New

** Affects: alsa-driver (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug vivid

** Also affects: dell-sputnik
   Importance: Undecided
   Status: New

** Description changed:

  Note that I am forcing the audio into HDA mode. (It has two modes: HDA
  and I2S.) In HDA mode, audio out works. The mic is known with a previous
- version of ALSA.
+ version of ALSA (Sept 3 2014 snapshot).
  
  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.18.0-13.14-generic 3.18.5
  Uname: Linux 3.18.0-13-generic x86_64
  ApportVersion: 2.16.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
-  USERPID ACCESS COMMAND
-  /dev/snd/pcmC1D0c:   jared  4299 F...m arecord
-  /dev/snd/pcmC1D0p:   jared  2929 F...m pulseaudio
-  /dev/snd/controlC1:  jared  2929 F pulseaudio
-  /dev/snd/controlC0:  jared  2929 F pulseaudio
+  USERPID ACCESS COMMAND
+  /dev/snd/pcmC1D0c:   jared  4299 F...m arecord
+  /dev/snd/pcmC1D0p:   jared  2929 F...m pulseaudio
+  /dev/snd/controlC1:  jared  2929 F pulseaudio
+  /dev/snd/controlC0:  jared  2929 F pulseaudio
  CurrentDesktop: Unity
  Date: Wed Feb 18 19:40:01 2015
  InstallationDate: Installed on 2014-11-03 (107 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 
(20140722.2)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingPlaybackStderr: o p e n ( ) :   N o   s u c h   f i l e  
 o r   d i r e c t o r y
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed
  Symptom_AlsaRecordingTestStderr: a r e c o r d :   m a i n : 7 2 2 :   a u d 
i o   o p e n   e r r o r :   D e v i c e   o r   r e s o u r c e   b u s y
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
-  USERPID ACCESS COMMAND
-  /dev/snd/pcmC1D0c:   jared  4299 F...m arecord
-  /dev/snd/controlC1:  jared  2929 F pulseaudio
-  /dev/snd/controlC0:  jared  2929 F pulseaudio
+  USERPID ACCESS COMMAND
+  /dev/snd/pcmC1D0c:   jared  4299 F...m arecord
+  /dev/snd/controlC1:  jared  2929 F pulseaudio
+  /dev/snd/controlC0:  jared  2929 F pulseaudio
  Symptom_Jack: Mic, Internal
  Symptom_Type: No sound at all
  Title: [XPS 13 9343, Realtek ALC3263, Mic, Internal] No sound at all
  UpgradeStatus: Upgraded to vivid on 2015-01-08 (41 days ago)
  dmi.bios.date: 02/03/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A01
  dmi.board.name: 0144PA
  dmi.board.vendor: Dell Inc.
  dmi.board.version: X04
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 

[Touch-packages] [Bug 1315770] Re: [Dell Precision M3800, Realtek ALC668, Black Headphone Out, Left] Strong background noise

2014-11-20 Thread Daniel Jared Dominguez
** Also affects: dell-sputnik
   Importance: Undecided
   Status: New

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

Title:
  [Dell Precision M3800, Realtek ALC668, Black Headphone Out, Left]
  Strong background noise

Status in Dell Sputnik:
  New
Status in “alsa-driver” package in Ubuntu:
  Confirmed
Status in Fedora:
  New

Bug description:
  When I connect the headphones, there is a strong hissing in both left
  and right side. It does not amplify or reduce along with the master
  volume. Instead, if I completely mute the master volume, the hissing
  disappears. It comes back as soon as I unmute the master volume.

  The internal speakers of the laptop are not affected: when headphones
  are not connected, there is no background hissing noise.

  Standard four questions:
  1) Ubuntu release: 14.04 LTS
  2) Package affected: kernel? (linux-image-3.13.0-24-generic) or maybe 
alsa-driver?
  3) Unless I play music, I expect no to hear anything in the headphones
  4) I get a background hissing noise in the headphones

  Thanks!

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  sun1875 F pulseaudio
   /dev/snd/controlC1:  sun1875 F pulseaudio
  CurrentDesktop: Unity
  Date: Sun May  4 02:46:01 2014
  InstallationDate: Installed on 2014-05-02 (1 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
  Symptom_Card: Audio interne - HDA Intel PCH
  Symptom_Jack: Black Headphone Out, Left
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: High background noise, or volume is too low
  Title: [Dell Precision M3800, Realtek ALC668, Black Headphone Out, Left] 
Background noise or low volume
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/06/2014
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A03
  dmi.board.name: Dell Precision M3800
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A03
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvrA03:bd02/06/2014:svnDellInc.:pnDellPrecisionM3800:pvrA03:rvnDellInc.:rnDellPrecisionM3800:rvrA03:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: Dell Precision M3800
  dmi.product.version: A03
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/dell-sputnik/+bug/1315770/+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 1347859] Re: Introduction of Predictable Network Interface Names (aka biosdevname) breaks working systems

2014-07-28 Thread Daniel Jared Dominguez
** Changed in: biosdevname (Ubuntu)
   Status: New = Opinion

** Changed in: systemd (Ubuntu)
   Status: New = Opinion

** Changed in: udev (Ubuntu)
   Status: New = Opinion

-- 
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/1347859

Title:
  Introduction of Predictable Network Interface Names (aka biosdevname)
  breaks working systems

Status in “biosdevname” package in Ubuntu:
  Opinion
Status in “systemd” package in Ubuntu:
  Opinion
Status in “udev” package in Ubuntu:
  Opinion

Bug description:
  Relatively recent linux distribution upgrades have been causing
  computers' ethernet devices to be unexpectedly renamed. While I
  understand that consistent device naming solves problems on some
  systems (mostly multi-NIC servers and a few specialty embedded
  devices), unilaterally forcing these changes on everyone is causing a
  lot of frustration. Here are some of the problems I've encountered:

  Interface names that were easily recognized as abbreviations for their
  device type have been replaced by cryptic names that have no obvious
  meaning whatsoever. It's easy to guess that eth0 is short for ethernet
  #0. What the heck is p4p1 supposed to mean? How is a human supposed to
  guess that the first p stands for PCI slot, that the second p stands
  for port number, and that the whole mysterious string represents an
  ethernet interface? This new naming convention is inferior to the old
  one in at least one significant respect: it makes things more
  difficult to understand.

  One of the more useful examples of consistency that unix-like systems
  have enjoyed for decades has been thrown out: the extremely well-known
  ethernet device names. This creates yet another hurtle for users and
  admins when switching between different operating systems or trying to
  apply general-purpose unix knowledge.

  A lot of documentation has been broken. I have no idea how many
  manuals, forum posts, bug reports, printed instructions, email
  messages, personal notes, books, and other forms of documentation in
  the world refer to a unix ethernet device as eth0, but I'll bet the
  number is huge. All that valuable guidance has just been rendered
  misleading or even useless to anyone who doesn't keep up with the
  latest distribution-specific device naming experiments; in other
  words: the people who need it most.

  Well-established workflows have been broken. The change trips up users
  and admins who have for years been getting tasks done quickly with
  commands that they could recall and execute without a second thought.
  They are suddenly finding that their workflows no longer work. This
  interrupts tasks that should have been quick and easy, forcing people
  figure out why known-good procedures are broken, think about how to
  modify their memorized commands to work on the affected systems, and
  train their fingers to type those new commands as quickly as they did
  the old ones. Beyond being irritating, it can eat up a bunch of time
  that some of us don't have to spare.

  Working systems have been broken. Tools and automation scripts,
  especially those developed for site-specific use, often make the
  difference between a computer that does real work and a useless
  generic OS installation. Sometimes they even make the difference
  between a malfunctioning headless box that can be fixed over the
  network and an expensive brick. It is quite common for such software
  to make some minimal assumptions about its runtime environment, like
  assuming that the name of the only network device that has ever been
  or will ever be present will not suddenly change after being stable
  for months or years. There are also applications (e.g. Matlab) and
  configuration files (e.g. smb.conf, dhclient.conf, isc-dhcp-server)
  that might depend on references to eth0. Renaming a critical and
  ubiquitous device like this is so very likely to cause problems that
  it should never, ever be done in an upgrade without the admin's
  explicit consent.

  Sufficient warning of the change was not given. On one of my machines,
  eth0 was renamed to p4p1 when I upgraded to Ubuntu 14.04 (trusty), yet
  I don't see any mention of it in the Trusty release notes, nor in any
  of the notes for releases of the previous several years. Is it buried
  in fine print someplace that I missed? Having to figure out for myself
  what changed, why, and how to revert it (in multiple ways on each
  machine) was a significant waste of my time. Multiply that by all the
  other people who were affected similarly, and I'll bet we'd get an
  embarrassing number of needlessly wasted person-months that could have
  been saved with a simple announcement and link to documentation.

  In short, the way this feature was forced on the world was an
  irresponsible blunder. It doesn't matter that the change was meant to