[Touch-packages] [Bug 1671974] Re: CUPS - Excessive Amounts of UDP Multicast Traffic for BJNP

2019-02-06 Thread spm2011
See if you have any *cups* packages installed

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

Title:
  CUPS - Excessive Amounts of UDP Multicast Traffic for BJNP

Status in cups package in Ubuntu:
  Confirmed

Bug description:
  It appears that the cups-browsed service as of Xenial (version
  1.8.3-2ubuntu3.1) sends an excessive amount of UDP multicast requests
  for ports 8610 (Canon MFNP) and 8612 (Canon BJNP) under unexpected
  conditions and regardless of a presence or lack of Canon printer
  devices on the network.

  This is manifested by enabling UFW, and observing multicast requests being 
blocked that are sent from the host machine's network IPv4 or IPv6 address to 
the multicast address, e.g.
  [UFW BLOCK] IN=wlp3s0 OUT= MAC= SRC= 
DST=ff02:::::::0001 LEN=64 TC=0 HOPLIMIT=1 
FLOWLBL=96642 PROTO=UDP SPT=8612 DPT=8612 LEN=24

  IN= OUT=wlan0 SRC=192.168.90.45 DST=192.168.91.255 LEN=44 TOS=0x00
  PREC=0x00 TTL=64 ID=7742 DF PROTO=UDP SPT=8612 DPT=8610 LEN=24

  Users have observed that the requests can be reproduced when any USB device 
is plugged/unplugged into the computer, regardless of whether the device has 
anything to do with printing:
  https://twitter.com/gertvdijk/status/621790755758178304
  https://bugs.kali.org/view.php?id=3094

  Just Googling "udp 8612", shows are a large number of results on different 
websites of people who have observed this behaviour in firewall and traffic 
logs, and have noticed that it may contribute to network slowdown and latency:
  https://askubuntu.com/questions/867739/what-is-this-traffic/867786
  
https://serverfault.com/questions/667376/watchguard-blocking-internal-udp-packets

  https://jehurst.wordpress.com/2016/01/22/small-victories/ recommends 
disabling the cups-browsed service to stop these requests:
  systemctl stop cups-browsed.service
  systemctl disable cups-browsed.service

  There are probably two things to address here:
  1. Connecting any USB device should not cause these requests unless the 
device is actually a printer or directly related to printing.
  2. Requests independent of connecting USB devices should be rate limited to a 
degree and/or should be dependent on the actual presence of a Canon printer 
configured on the network.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1671974/+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 1808861] Re: chromium-browser crash Unreportable - Invalid core dump: BFD: warning: apport_core is truncated

2018-12-24 Thread spm2011
Just had this happen again with a systemd-journald system problem error
report.

/var/crash/_lib_systemd_systemd-journald.0.crash:
"Invalid core dump: BFD: warning: /tmp/apport_core_4z_uh8nz is truncated: 
expected core file size >= 18833408, found: 274432"

apport log:
ERROR: apport (pid 6651) Mon Dec 24 14:33:49 2018: called for pid 314, signal 
6, core limit 0, dump mode 1
ERROR: apport (pid 6651) Mon Dec 24 14:33:49 2018: executable: 
/lib/systemd/systemd-journald (command line "/lib/systemd/systemd-journald")
ERROR: apport (pid 6651) Mon Dec 24 14:33:50 2018: is_closing_session(): no 
DBUS_SESSION_BUS_ADDRESS in environment
ERROR: apport (pid 6651) Mon Dec 24 14:45:33 2018: wrote report 
/var/crash/_lib_systemd_systemd-journald.0.crash


** Summary changed:

- chromium-browser crash Unreportable - Invalid core dump: BFD: warning: 
apport_core is truncated
+ Problem crashes Unreportable - Invalid core dump: BFD: warning: apport_core 
is truncated

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

Title:
  Problem crashes Unreportable - Invalid core dump: BFD: warning:
  apport_core is truncated

Status in apport package in Ubuntu:
  New
Status in chromium-browser package in Ubuntu:
  Invalid

Bug description:
  Trying to report a crash in chromium-browser, get Unreportable reason
  Invalid core dump: BFD: warning apport_core is truncated (see
  screenshot, can't copy message from apport dialog - bug # 1273752).

  UnreportableReason:
   Invalid core dump: BFD: warning: /tmp/apport_core_6yb3cl_7 is truncated: 
expected core file size >= 1245646848, found: 760283136
   warning: core file may not match specified executable file.

  
  Expected: able to report ?

  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: apport 2.20.9-0ubuntu7.5
  ProcVersionSignature: User Name 4.15.0-42.45-generic 4.15.18
  Uname: Linux 4.15.0-42-generic x86_64
  ApportLog:
   ERROR: apport (pid 31805) Mon Dec 17 15:14:09 2018: called for pid 15848, 
signal 5, core limit 0, dump mode 1
   ERROR: apport (pid 31805) Mon Dec 17 15:14:09 2018: executable: 
/usr/lib/chromium-browser/chromium-browser (command line 
"/usr/lib/chromium-browser/chromium-browser\ --enable-pinch")
   ERROR: apport (pid 31805) Mon Dec 17 15:14:09 2018: is_closing_session(): no 
DBUS_SESSION_BUS_ADDRESS in environment
   ERROR: apport (pid 31805) Mon Dec 17 15:15:23 2018: wrote report 
/var/crash/_usr_lib_chromium-browser_chromium-browser.1000.crash
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Dec 17 15:30:28 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2018-09-12 (96 days ago)
  InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 
(20180731)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: apport
  UpgradeStatus: Upgraded to bionic on 2018-09-28 (80 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1808861/+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 1808861] Re: chromium-browser crash Unreportable - Invalid core dump: BFD: warning: apport_core is truncated

2018-12-24 Thread spm2011
Not much to go off of in the apport log

** Attachment added: "apport.log"
   
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1808861/+attachment/5224676/+files/apport.log

** Changed in: apport (Ubuntu)
   Status: Incomplete => New

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

Title:
  chromium-browser crash Unreportable - Invalid core dump: BFD: warning:
  apport_core is truncated

Status in apport package in Ubuntu:
  New
Status in chromium-browser package in Ubuntu:
  Invalid

Bug description:
  Trying to report a crash in chromium-browser, get Unreportable reason
  Invalid core dump: BFD: warning apport_core is truncated (see
  screenshot, can't copy message from apport dialog - bug # 1273752).

  UnreportableReason:
   Invalid core dump: BFD: warning: /tmp/apport_core_6yb3cl_7 is truncated: 
expected core file size >= 1245646848, found: 760283136
   warning: core file may not match specified executable file.

  
  Expected: able to report ?

  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: apport 2.20.9-0ubuntu7.5
  ProcVersionSignature: User Name 4.15.0-42.45-generic 4.15.18
  Uname: Linux 4.15.0-42-generic x86_64
  ApportLog:
   ERROR: apport (pid 31805) Mon Dec 17 15:14:09 2018: called for pid 15848, 
signal 5, core limit 0, dump mode 1
   ERROR: apport (pid 31805) Mon Dec 17 15:14:09 2018: executable: 
/usr/lib/chromium-browser/chromium-browser (command line 
"/usr/lib/chromium-browser/chromium-browser\ --enable-pinch")
   ERROR: apport (pid 31805) Mon Dec 17 15:14:09 2018: is_closing_session(): no 
DBUS_SESSION_BUS_ADDRESS in environment
   ERROR: apport (pid 31805) Mon Dec 17 15:15:23 2018: wrote report 
/var/crash/_usr_lib_chromium-browser_chromium-browser.1000.crash
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Dec 17 15:30:28 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2018-09-12 (96 days ago)
  InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 
(20180731)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: apport
  UpgradeStatus: Upgraded to bionic on 2018-09-28 (80 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1808861/+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 1801383] Re: the WifiSyslog apport hook (used in firefox/tb) includes SSID informations

2018-12-21 Thread spm2011
`apport-bug linux` uploads WifiSyslog.txt, so this also affects apport
hook for the linux package.

** Changed in: linux (Ubuntu)
   Status: Incomplete => Confirmed

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

Title:
  the WifiSyslog apport hook (used in firefox/tb) includes SSID
  informations

Status in apport package in Ubuntu:
  New
Status in firefox package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Confirmed
Status in thunderbird package in Ubuntu:
  New

Bug description:
  When I apport-bug certain packages such as firefox for example, it
  uploads the WifiSyslog.txt file.

  The WifiSyslog may contain a list of all system connections enumerated
  in /etc/NetworkManager/system-connections, i.e. all SSIDs the user has
  ever connected to that are found in the system-connections. This is a
  serious privacy risk and completely unnecessary information for most
  bug reports.

  Should either remove WifiSyslog as a requirement for packages that
  don't need it (should I report this to
  https://bugs.launchpad.net/ubuntu/+source/firefox/ ?), or redact
  information that may contain usernames and SSIDs from the log file.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: apport 2.20.9-0ubuntu7.4
  ProcVersionSignature: User Name 4.15.0-38.41-generic 4.15.18
  Uname: Linux 4.15.0-38-generic x86_64
  ApportLog:
   
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  CrashReports: 640:1000:117:62475:2018-11-01 19:17:29.982295751 
-0400:2018-11-01 19:17:30.982295751 
-0400:/var/crash/_usr_bin_gnome-screenshot.1000.crash
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Nov  2 11:24:20 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2018-09-12 (50 days ago)
  InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 
(20180731)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: apport
  UpgradeStatus: Upgraded to bionic on 2018-09-28 (34 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1801383/+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 1801383] Re: the WifiSyslog apport hook (used in firefox/tb) includes SSID informations

2018-12-20 Thread spm2011
** Also affects: linux (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  the WifiSyslog apport hook (used in firefox/tb) includes SSID
  informations

Status in apport package in Ubuntu:
  New
Status in firefox package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  New
Status in thunderbird package in Ubuntu:
  New

Bug description:
  When I apport-bug certain packages such as firefox for example, it
  uploads the WifiSyslog.txt file.

  The WifiSyslog may contain a list of all system connections enumerated
  in /etc/NetworkManager/system-connections, i.e. all SSIDs the user has
  ever connected to that are found in the system-connections. This is a
  serious privacy risk and completely unnecessary information for most
  bug reports.

  Should either remove WifiSyslog as a requirement for packages that
  don't need it (should I report this to
  https://bugs.launchpad.net/ubuntu/+source/firefox/ ?), or redact
  information that may contain usernames and SSIDs from the log file.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: apport 2.20.9-0ubuntu7.4
  ProcVersionSignature: User Name 4.15.0-38.41-generic 4.15.18
  Uname: Linux 4.15.0-38-generic x86_64
  ApportLog:
   
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  CrashReports: 640:1000:117:62475:2018-11-01 19:17:29.982295751 
-0400:2018-11-01 19:17:30.982295751 
-0400:/var/crash/_usr_bin_gnome-screenshot.1000.crash
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Nov  2 11:24:20 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2018-09-12 (50 days ago)
  InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 
(20180731)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: apport
  UpgradeStatus: Upgraded to bionic on 2018-09-28 (34 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1801383/+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 1808861] Re: chromium-browser crash Unreportable - Invalid core dump: BFD: warning: apport_core is truncated

2018-12-17 Thread spm2011
** Description changed:

  Trying to report a crash in chromium-browser, get Unreportable reason
  Invalid core dump: BFD: warning apport_core is truncated (see
  screenshot, can't copy message from apport dialog - bug # 1273752).
  
+ UnreportableReason:
+  Invalid core dump: BFD: warning: /tmp/apport_core_6yb3cl_7 is truncated: 
expected core file size >= 1245646848, found: 760283136
+  warning: core file may not match specified executable file.
+ 
+ 
  Expected: able to report ?
+ 
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: apport 2.20.9-0ubuntu7.5
  ProcVersionSignature: User Name 4.15.0-42.45-generic 4.15.18
  Uname: Linux 4.15.0-42-generic x86_64
  ApportLog:
-  ERROR: apport (pid 31805) Mon Dec 17 15:14:09 2018: called for pid 15848, 
signal 5, core limit 0, dump mode 1
-  ERROR: apport (pid 31805) Mon Dec 17 15:14:09 2018: executable: 
/usr/lib/chromium-browser/chromium-browser (command line 
"/usr/lib/chromium-browser/chromium-browser\ --enable-pinch")
-  ERROR: apport (pid 31805) Mon Dec 17 15:14:09 2018: is_closing_session(): no 
DBUS_SESSION_BUS_ADDRESS in environment
-  ERROR: apport (pid 31805) Mon Dec 17 15:15:23 2018: wrote report 
/var/crash/_usr_lib_chromium-browser_chromium-browser.1000.crash
+  ERROR: apport (pid 31805) Mon Dec 17 15:14:09 2018: called for pid 15848, 
signal 5, core limit 0, dump mode 1
+  ERROR: apport (pid 31805) Mon Dec 17 15:14:09 2018: executable: 
/usr/lib/chromium-browser/chromium-browser (command line 
"/usr/lib/chromium-browser/chromium-browser\ --enable-pinch")
+  ERROR: apport (pid 31805) Mon Dec 17 15:14:09 2018: is_closing_session(): no 
DBUS_SESSION_BUS_ADDRESS in environment
+  ERROR: apport (pid 31805) Mon Dec 17 15:15:23 2018: wrote report 
/var/crash/_usr_lib_chromium-browser_chromium-browser.1000.crash
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Dec 17 15:30:28 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2018-09-12 (96 days ago)
  InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 
(20180731)
  PackageArchitecture: all
  ProcEnviron:
-  TERM=xterm-256color
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=
-  LANG=en_US.UTF-8
-  SHELL=/bin/bash
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
  SourcePackage: apport
  UpgradeStatus: Upgraded to bionic on 2018-09-28 (80 days ago)

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

Title:
  chromium-browser crash Unreportable - Invalid core dump: BFD: warning:
  apport_core is truncated

Status in apport package in Ubuntu:
  New
Status in chromium-browser package in Ubuntu:
  New

Bug description:
  Trying to report a crash in chromium-browser, get Unreportable reason
  Invalid core dump: BFD: warning apport_core is truncated (see
  screenshot, can't copy message from apport dialog - bug # 1273752).

  UnreportableReason:
   Invalid core dump: BFD: warning: /tmp/apport_core_6yb3cl_7 is truncated: 
expected core file size >= 1245646848, found: 760283136
   warning: core file may not match specified executable file.

  
  Expected: able to report ?

  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: apport 2.20.9-0ubuntu7.5
  ProcVersionSignature: User Name 4.15.0-42.45-generic 4.15.18
  Uname: Linux 4.15.0-42-generic x86_64
  ApportLog:
   ERROR: apport (pid 31805) Mon Dec 17 15:14:09 2018: called for pid 15848, 
signal 5, core limit 0, dump mode 1
   ERROR: apport (pid 31805) Mon Dec 17 15:14:09 2018: executable: 
/usr/lib/chromium-browser/chromium-browser (command line 
"/usr/lib/chromium-browser/chromium-browser\ --enable-pinch")
   ERROR: apport (pid 31805) Mon Dec 17 15:14:09 2018: is_closing_session(): no 
DBUS_SESSION_BUS_ADDRESS in environment
   ERROR: apport (pid 31805) Mon Dec 17 15:15:23 2018: wrote report 
/var/crash/_usr_lib_chromium-browser_chromium-browser.1000.crash
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Dec 17 15:30:28 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2018-09-12 (96 days ago)
  InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 
(20180731)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: apport
  UpgradeStatus: Upgraded to bionic on 2018-09-28 (80 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1808861/+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 1808861] [NEW] chromium-browser crash Unreportable - Invalid core dump: BFD: warning: apport_core is truncated

2018-12-17 Thread spm2011
Public bug reported:

Trying to report a crash in chromium-browser, get Unreportable reason
Invalid core dump: BFD: warning apport_core is truncated (see
screenshot, can't copy message from apport dialog - bug # 1273752).

Expected: able to report ?

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: apport 2.20.9-0ubuntu7.5
ProcVersionSignature: User Name 4.15.0-42.45-generic 4.15.18
Uname: Linux 4.15.0-42-generic x86_64
ApportLog:
 ERROR: apport (pid 31805) Mon Dec 17 15:14:09 2018: called for pid 15848, 
signal 5, core limit 0, dump mode 1
 ERROR: apport (pid 31805) Mon Dec 17 15:14:09 2018: executable: 
/usr/lib/chromium-browser/chromium-browser (command line 
"/usr/lib/chromium-browser/chromium-browser\ --enable-pinch")
 ERROR: apport (pid 31805) Mon Dec 17 15:14:09 2018: is_closing_session(): no 
DBUS_SESSION_BUS_ADDRESS in environment
 ERROR: apport (pid 31805) Mon Dec 17 15:15:23 2018: wrote report 
/var/crash/_usr_lib_chromium-browser_chromium-browser.1000.crash
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Mon Dec 17 15:30:28 2018
EcryptfsInUse: Yes
InstallationDate: Installed on 2018-09-12 (96 days ago)
InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 (20180731)
PackageArchitecture: all
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: apport
UpgradeStatus: Upgraded to bionic on 2018-09-28 (80 days ago)

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

** Affects: chromium-browser (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug bionic

** Attachment added: "chromium-browser_invalid_core_dump.png"
   
https://bugs.launchpad.net/bugs/1808861/+attachment/5223066/+files/chromium-browser_invalid_core_dump.png

** Also affects: chromium-browser (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  chromium-browser crash Unreportable - Invalid core dump: BFD: warning:
  apport_core is truncated

Status in apport package in Ubuntu:
  New
Status in chromium-browser package in Ubuntu:
  New

Bug description:
  Trying to report a crash in chromium-browser, get Unreportable reason
  Invalid core dump: BFD: warning apport_core is truncated (see
  screenshot, can't copy message from apport dialog - bug # 1273752).

  Expected: able to report ?

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: apport 2.20.9-0ubuntu7.5
  ProcVersionSignature: User Name 4.15.0-42.45-generic 4.15.18
  Uname: Linux 4.15.0-42-generic x86_64
  ApportLog:
   ERROR: apport (pid 31805) Mon Dec 17 15:14:09 2018: called for pid 15848, 
signal 5, core limit 0, dump mode 1
   ERROR: apport (pid 31805) Mon Dec 17 15:14:09 2018: executable: 
/usr/lib/chromium-browser/chromium-browser (command line 
"/usr/lib/chromium-browser/chromium-browser\ --enable-pinch")
   ERROR: apport (pid 31805) Mon Dec 17 15:14:09 2018: is_closing_session(): no 
DBUS_SESSION_BUS_ADDRESS in environment
   ERROR: apport (pid 31805) Mon Dec 17 15:15:23 2018: wrote report 
/var/crash/_usr_lib_chromium-browser_chromium-browser.1000.crash
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Dec 17 15:30:28 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2018-09-12 (96 days ago)
  InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 
(20180731)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: apport
  UpgradeStatus: Upgraded to bionic on 2018-09-28 (80 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1808861/+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 1765285] Re: systemd-journald crashed with SIGABRT in __GI___pthread_timedjoin_ex()

2018-12-14 Thread spm2011
*** This bug is a duplicate of bug 1754214 ***
https://bugs.launchpad.net/bugs/1754214

I'm seeing this as well, after closing lid and resuming in an attempt to
reset an unresponsive, seemingly thrashing system with many tabs open in
Firefox.

Where is bug #1754214 ?

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

Title:
  systemd-journald crashed with SIGABRT in __GI___pthread_timedjoin_ex()

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  ???

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: systemd 237-3ubuntu8
  ProcVersionSignature: Ubuntu 4.15.0-17.18-generic 4.15.17
  Uname: Linux 4.15.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu5
  Architecture: amd64
  Date: Thu Apr 19 06:46:33 2018
  ExecutablePath: /lib/systemd/systemd-journald
  InstallationDate: Installed on 2018-03-21 (29 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180319)
  Lsusb:
   Bus 002 Device 002: ID 0781:5591 SanDisk Corp. 
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: innotek GmbH VirtualBox
  ProcCmdline: /lib/systemd/systemd-journald
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-17-generic 
root=UUID=624ad287-69d9-4615-a6a0-b840f3ff8c6d ro quiet splash
  Signal: 6
  SourcePackage: systemd
  StacktraceTop:
   __GI___pthread_timedjoin_ex (threadid=139717271447296, thread_return=0x0, 
abstime=0x0, block=) at pthread_join_common.c:89
   ?? () from /lib/systemd/libsystemd-shared-237.so
   ?? () from /lib/systemd/libsystemd-shared-237.so
   journal_file_append_object () from /lib/systemd/libsystemd-shared-237.so
   ?? () from /lib/systemd/libsystemd-shared-237.so
  SystemdDelta:
   [MASKED] /etc/systemd/system/samba-ad-dc.service → 
/lib/systemd/system/samba-ad-dc.service
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /lib/systemd/system/user@.service → 
/lib/systemd/system/user@.service.d/timeout.conf
   
   3 overridden configuration files found.
  Title: systemd-journald crashed with SIGABRT in __GI___pthread_timedjoin_ex()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.family: Virtual Machine
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1765285/+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 1273752] Re: Can't Copy Crash Report Details to Clipboard

2018-12-14 Thread spm2011
** Also affects: apport
   Importance: Undecided
   Status: New

** Changed in: apport
   Status: New => Confirmed

** Also affects: update-notifier (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  Can't Copy Crash Report Details to Clipboard

Status in Apport:
  Confirmed
Status in apport package in Ubuntu:
  Confirmed
Status in update-notifier package in Ubuntu:
  New

Bug description:
  Often times, after receiving a crash report, if I click the "Continue"
  button it doesn't launch the browser for me to submit my crash to
  launchpad.net.

  Because of this, I'd always like to copy the crash report to my
  clipboard before clicking the continue button, so that I can manually
  provide this information into a bug report to launchpad.net.

  However, this option is not available.

  More over, there is absolutely *no way* to copy any text from this
  crash report's dialog window!

  1) You cannot ctrl-a to select all.
  2) Ctrl-c doesn't copy anything
  3) Right-clicking doesn't produce a context menu where you can select "Copy".

  This is an unfinished design. You should always give the user the
  ability to copy any text displayed in the UI.

  Next to the "Show/Hide details" button, I suggest adding a "Copy to
  Clipboard" button. If not this, please offer some way to achieve this
  from the GUI.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: apport-gtk 2.13.2-0ubuntu2
  ProcVersionSignature: Ubuntu 3.13.0-5.20-generic 3.13.0
  Uname: Linux 3.13.0-5-generic x86_64
  NonfreeKernelModules: wl
  ApportLog:

  ApportVersion: 2.13.2-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Jan 28 10:21:00 2014
  InstallationDate: Installed on 2013-10-07 (113 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: Upgraded to trusty on 2014-01-08 (19 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/apport/+bug/1273752/+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 1805710] [NEW] apport-bug compiz incorrectly detects Unity is running on Ubuntu 18.04 GNOME

2018-11-28 Thread spm2011
Public bug reported:

Ubuntu 18.04 GNOME

To reproduce:
  - Reporting bug in compiz using apport-bug compiz

A dialog box pops up "Thanks for reporting this bug. It seems you have
Unity running." (see screenshot)

Unity desktop is not running or installed.

Expected: apport detects that Unity is not running, does not show the
dialog.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: apport 2.20.9-0ubuntu7.5
ProcVersionSignature: User Name 4.15.0-39.42-generic 4.15.18
Uname: Linux 4.15.0-39-generic x86_64
ApportLog:
 
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Wed Nov 28 16:13:45 2018
EcryptfsInUse: Yes
InstallationDate: Installed on 2018-09-12 (77 days ago)
InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 (20180731)
PackageArchitecture: all
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: apport
UpgradeStatus: Upgraded to bionic on 2018-09-28 (61 days ago)

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


** Tags: amd64 apport-bug bionic

** Attachment added: "apport_detects_unity.png"
   
https://bugs.launchpad.net/bugs/1805710/+attachment/5217085/+files/apport_detects_unity.png

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

Title:
  apport-bug compiz incorrectly detects Unity is running on Ubuntu 18.04
  GNOME

Status in apport package in Ubuntu:
  New

Bug description:
  Ubuntu 18.04 GNOME

  To reproduce:
- Reporting bug in compiz using apport-bug compiz

  A dialog box pops up "Thanks for reporting this bug. It seems you have
  Unity running." (see screenshot)

  Unity desktop is not running or installed.

  Expected: apport detects that Unity is not running, does not show the
  dialog.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: apport 2.20.9-0ubuntu7.5
  ProcVersionSignature: User Name 4.15.0-39.42-generic 4.15.18
  Uname: Linux 4.15.0-39-generic x86_64
  ApportLog:
   
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Nov 28 16:13:45 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2018-09-12 (77 days ago)
  InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 
(20180731)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: apport
  UpgradeStatus: Upgraded to bionic on 2018-09-28 (61 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1805710/+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 1801383] Re: the WifiSyslog apport hook (used in firefox/tb) includes SSID informations

2018-11-28 Thread spm2011
@osomon +1, thanks!

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

Title:
  the WifiSyslog apport hook (used in firefox/tb) includes SSID
  informations

Status in apport package in Ubuntu:
  New
Status in firefox package in Ubuntu:
  Fix Committed
Status in thunderbird package in Ubuntu:
  New

Bug description:
  When I apport-bug certain packages such as firefox for example, it
  uploads the WifiSyslog.txt file.

  The WifiSyslog may contain a list of all system connections enumerated
  in /etc/NetworkManager/system-connections, i.e. all SSIDs the user has
  ever connected to that are found in the system-connections. This is a
  serious privacy risk and completely unnecessary information for most
  bug reports.

  Should either remove WifiSyslog as a requirement for packages that
  don't need it (should I report this to
  https://bugs.launchpad.net/ubuntu/+source/firefox/ ?), or redact
  information that may contain usernames and SSIDs from the log file.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: apport 2.20.9-0ubuntu7.4
  ProcVersionSignature: User Name 4.15.0-38.41-generic 4.15.18
  Uname: Linux 4.15.0-38-generic x86_64
  ApportLog:
   
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  CrashReports: 640:1000:117:62475:2018-11-01 19:17:29.982295751 
-0400:2018-11-01 19:17:30.982295751 
-0400:/var/crash/_usr_bin_gnome-screenshot.1000.crash
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Nov  2 11:24:20 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2018-09-12 (50 days ago)
  InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 
(20180731)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: apport
  UpgradeStatus: Upgraded to bionic on 2018-09-28 (34 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1801383/+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 1697160] Re: add function to be able to copy text from error summary dialog

2018-08-23 Thread spm2011
*** This bug is a duplicate of bug 1273752 ***
https://bugs.launchpad.net/bugs/1273752

** This bug has been marked a duplicate of bug 1273752
   Can't Copy Crash Report Details to Clipboard

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

Title:
  add function to be able to copy text from error summary dialog

Status in apport package in Ubuntu:
  New

Bug description:
  It'd be nice to have a function to be able to copy text from the error
  summary dialog.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: apport-gtk 2.20.4-0ubuntu4.1
  ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15
  Uname: Linux 4.10.0-22-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.4-0ubuntu4.1
  Architecture: amd64
  CurrentDesktop: Unity:Unity7
  Date: Sat Jun 10 12:55:31 2017
  InstallationDate: Installed on 2015-12-12 (545 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: Upgraded to zesty on 2017-05-01 (39 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1697160/+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 1671974] Re: CUPS - Excessive Amounts of UDP Multicast Traffic for BJNP

2018-06-13 Thread spm2011
Still seeing CUPS related IPv6 multicast requests from my machine on 18.04 
bionic, right after plugging in a USB device:
[11593.578868] usb 2-1.1: new high-speed USB device number 4 using ehci-pci
[11593.693173] usb 2-1.1: New USB device found, idVendor=0e8d, idProduct=1807
[11593.693182] usb 2-1.1: New USB device strings: Mfr=1, Product=2, 
SerialNumber=3
[11593.693187] usb 2-1.1: Product: MT1807 
[11593.693192] usb 2-1.1: Manufacturer: MediaTek Inc
[11593.693196] usb 2-1.1: SerialNumber: 
[11594.085831] usb-storage 2-1.1:1.0: USB Mass Storage device detected
[11594.086113] scsi host6: usb-storage 2-1.1:1.0
[11594.086272] usbcore: registered new interface driver usb-storage
[11594.257746] [UFW BLOCK] IN=wlp2s0 OUT= MAC= SRC= 
DST=ff02:::::::0001 LEN=64 TC=0 HOPLIMIT=1 
FLOWLBL=659619 PROTO=UDP SPT=8612 DPT=8612 LEN=24 
[11594.257765] [UFW BLOCK] IN=wlp2s0 OUT= MAC= SRC= 
DST=ff02:::::::0001 LEN=64 TC=0 HOPLIMIT=1 
FLOWLBL=952340 PROTO=UDP SPT=8612 DPT=8610 LEN=24 
[11594.268122] [UFW BLOCK] IN=wlp2s0 OUT= MAC= SRC= 
DST=ff02:::::::0001 LEN=64 TC=0 HOPLIMIT=1 
FLOWLBL=659619 PROTO=UDP SPT=8612 DPT=8612 LEN=24 
[11594.268197] [UFW BLOCK] IN=wlp2s0 OUT= MAC= SRC= 
DST=ff02:::::::0001 LEN=64 TC=0 HOPLIMIT=1 
FLOWLBL=952340 PROTO=UDP SPT=8612 DPT=8610 LEN=24

No longer seeing IPv4 requests though

** Changed in: cups (Ubuntu)
   Status: Expired => Confirmed

** Tags added: bionic

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

Title:
  CUPS - Excessive Amounts of UDP Multicast Traffic for BJNP

Status in cups package in Ubuntu:
  Confirmed

Bug description:
  It appears that the cups-browsed service as of Xenial (version
  1.8.3-2ubuntu3.1) sends an excessive amount of UDP multicast requests
  for ports 8610 (Canon MFNP) and 8612 (Canon BJNP) under unexpected
  conditions and regardless of a presence or lack of Canon printer
  devices on the network.

  This is manifested by enabling UFW, and observing multicast requests being 
blocked that are sent from the host machine's network IPv4 or IPv6 address to 
the multicast address, e.g.
  [UFW BLOCK] IN=wlp3s0 OUT= MAC= SRC= 
DST=ff02:::::::0001 LEN=64 TC=0 HOPLIMIT=1 
FLOWLBL=96642 PROTO=UDP SPT=8612 DPT=8612 LEN=24

  IN= OUT=wlan0 SRC=192.168.90.45 DST=192.168.91.255 LEN=44 TOS=0x00
  PREC=0x00 TTL=64 ID=7742 DF PROTO=UDP SPT=8612 DPT=8610 LEN=24

  Users have observed that the requests can be reproduced when any USB device 
is plugged/unplugged into the computer, regardless of whether the device has 
anything to do with printing:
  https://twitter.com/gertvdijk/status/621790755758178304
  https://bugs.kali.org/view.php?id=3094

  Just Googling "udp 8612", shows are a large number of results on different 
websites of people who have observed this behaviour in firewall and traffic 
logs, and have noticed that it may contribute to network slowdown and latency:
  https://askubuntu.com/questions/867739/what-is-this-traffic/867786
  
https://serverfault.com/questions/667376/watchguard-blocking-internal-udp-packets

  https://jehurst.wordpress.com/2016/01/22/small-victories/ recommends 
disabling the cups-browsed service to stop these requests:
  systemctl stop cups-browsed.service
  systemctl disable cups-browsed.service

  There are probably two things to address here:
  1. Connecting any USB device should not cause these requests unless the 
device is actually a printer or directly related to printing.
  2. Requests independent of connecting USB devices should be rate limited to a 
degree and/or should be dependent on the actual presence of a Canon printer 
configured on the network.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1671974/+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 1580394] Re: [Latitude 3340, Realtek ALC3234] MATE - Headphone Static on Battery Power

2017-10-25 Thread spm2011
** Attachment removed: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1580394/+attachment/4660325/+files/CurrentDmesg.txt

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

Title:
  [Latitude 3340, Realtek ALC3234] MATE - Headphone Static on Battery
  Power

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  I have noticed that when I am on battery power on a Dell Latitude 3340
  laptop with headphones plugged in , and there is no audio playing on
  the computer, there is a consistent static sound that comes through
  the headphones at a constant volume that is not affected by changing
  the volume level. I think it may be picking up some kind of analog
  loopback signal because keyboard presses and disk activity seem to
  influence the noise. When I plug the power cable into the laptop , the
  static immediately goes away.

  I reported this earlier to the upstream Linux Kernel bug tracker, but
  it seems to be fixed in any distro running a 4.4 kernel or greater
  that I have tested , Except for Ubuntu MATE 16.04 LTS 64-bit. This
  make me think it is not a kernel level issue and is found somewhere
  either in the audio settings on Ubuntu MATE or a pulseaudio bug. I
  cannot reproduce it on any other 16.04 distro version, but it also
  affects all the 14.04.4 distros as well.

  Running amixer -c 1 set "Loopback Mixing" "Disabled" does not prevent
  the static.

  The BIOS Firmware version is up to date.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: pulseaudio 1:8.0-0ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  ubuntu-mate   1718 F pulseaudio
   /dev/snd/controlC0:  ubuntu-mate   1718 F pulseaudio
  CasperVersion: 1.376
  CurrentDesktop: MATE
  Date: Wed May 11 00:43:52 2016
  LiveMediaBuild: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/04/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A10
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA10:bd11/04/2015:svnDellInc.:pnLatitude3340:pvr00:rvnDellInc.:rn:rvr:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude 3340
  dmi.product.version: 00
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1580394/+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 1671974] Re: CUPS - Excessive Amounts of UDP Multicast Traffic for BJNP

2017-09-08 Thread spm2011
Moving this bug under cups package.

** Package changed: cups-filters (Ubuntu) => cups (Ubuntu)

** Changed in: cups (Ubuntu)
   Status: Incomplete => Confirmed

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

Title:
  CUPS - Excessive Amounts of UDP Multicast Traffic for BJNP

Status in cups package in Ubuntu:
  Confirmed

Bug description:
  It appears that the cups-browsed service as of Xenial (version
  1.8.3-2ubuntu3.1) sends an excessive amount of UDP multicast requests
  for ports 8610 (Canon MFNP) and 8612 (Canon BJNP) under unexpected
  conditions and regardless of a presence or lack of Canon printer
  devices on the network.

  This is manifested by enabling UFW, and observing multicast requests being 
blocked that are sent from the host machine's network IPv4 or IPv6 address to 
the multicast address, e.g.
  [UFW BLOCK] IN=wlp3s0 OUT= MAC= SRC= 
DST=ff02:::::::0001 LEN=64 TC=0 HOPLIMIT=1 
FLOWLBL=96642 PROTO=UDP SPT=8612 DPT=8612 LEN=24

  IN= OUT=wlan0 SRC=192.168.90.45 DST=192.168.91.255 LEN=44 TOS=0x00
  PREC=0x00 TTL=64 ID=7742 DF PROTO=UDP SPT=8612 DPT=8610 LEN=24

  Users have observed that the requests can be reproduced when any USB device 
is plugged/unplugged into the computer, regardless of whether the device has 
anything to do with printing:
  https://twitter.com/gertvdijk/status/621790755758178304
  https://bugs.kali.org/view.php?id=3094

  Just Googling "udp 8612", shows are a large number of results on different 
websites of people who have observed this behaviour in firewall and traffic 
logs, and have noticed that it may contribute to network slowdown and latency:
  https://askubuntu.com/questions/867739/what-is-this-traffic/867786
  
https://serverfault.com/questions/667376/watchguard-blocking-internal-udp-packets

  https://jehurst.wordpress.com/2016/01/22/small-victories/ recommends 
disabling the cups-browsed service to stop these requests:
  systemctl stop cups-browsed.service
  systemctl disable cups-browsed.service

  There are probably two things to address here:
  1. Connecting any USB device should not cause these requests unless the 
device is actually a printer or directly related to printing.
  2. Requests independent of connecting USB devices should be rate limited to a 
degree and/or should be dependent on the actual presence of a Canon printer 
configured on the network.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1671974/+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 1580394] Re: [Latitude 3340, Realtek ALC3234] MATE - Headphone Static on Battery Power

2017-09-01 Thread spm2011
** No longer affects: libmatemixer (Ubuntu)

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

Title:
  [Latitude 3340, Realtek ALC3234] MATE - Headphone Static on Battery
  Power

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  I have noticed that when I am on battery power on a Dell Latitude 3340
  laptop with headphones plugged in , and there is no audio playing on
  the computer, there is a consistent static sound that comes through
  the headphones at a constant volume that is not affected by changing
  the volume level. I think it may be picking up some kind of analog
  loopback signal because keyboard presses and disk activity seem to
  influence the noise. When I plug the power cable into the laptop , the
  static immediately goes away.

  I reported this earlier to the upstream Linux Kernel bug tracker, but
  it seems to be fixed in any distro running a 4.4 kernel or greater
  that I have tested , Except for Ubuntu MATE 16.04 LTS 64-bit. This
  make me think it is not a kernel level issue and is found somewhere
  either in the audio settings on Ubuntu MATE or a pulseaudio bug. I
  cannot reproduce it on any other 16.04 distro version, but it also
  affects all the 14.04.4 distros as well.

  Running amixer -c 1 set "Loopback Mixing" "Disabled" does not prevent
  the static.

  The BIOS Firmware version is up to date.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: pulseaudio 1:8.0-0ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  ubuntu-mate   1718 F pulseaudio
   /dev/snd/controlC0:  ubuntu-mate   1718 F pulseaudio
  CasperVersion: 1.376
  CurrentDesktop: MATE
  Date: Wed May 11 00:43:52 2016
  LiveMediaBuild: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/04/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A10
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA10:bd11/04/2015:svnDellInc.:pnLatitude3340:pvr00:rvnDellInc.:rn:rvr:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude 3340
  dmi.product.version: 00
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1580394/+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 1580394] Re: [Latitude 3340, Realtek ALC3234] MATE - Headphone Static on Battery Power

2017-08-06 Thread spm2011
** Also affects: libmatemixer (Ubuntu)
   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/1580394

Title:
  [Latitude 3340, Realtek ALC3234] MATE - Headphone Static on Battery
  Power

Status in alsa-driver package in Ubuntu:
  New
Status in libmatemixer package in Ubuntu:
  New

Bug description:
  I have noticed that when I am on battery power on a Dell Latitude 3340
  laptop with headphones plugged in , and there is no audio playing on
  the computer, there is a consistent static sound that comes through
  the headphones at a constant volume that is not affected by changing
  the volume level. I think it may be picking up some kind of analog
  loopback signal because keyboard presses and disk activity seem to
  influence the noise. When I plug the power cable into the laptop , the
  static immediately goes away.

  I reported this earlier to the upstream Linux Kernel bug tracker, but
  it seems to be fixed in any distro running a 4.4 kernel or greater
  that I have tested , Except for Ubuntu MATE 16.04 LTS 64-bit. This
  make me think it is not a kernel level issue and is found somewhere
  either in the audio settings on Ubuntu MATE or a pulseaudio bug. I
  cannot reproduce it on any other 16.04 distro version, but it also
  affects all the 14.04.4 distros as well.

  Running amixer -c 1 set "Loopback Mixing" "Disabled" does not prevent
  the static.

  The BIOS Firmware version is up to date.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: pulseaudio 1:8.0-0ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  ubuntu-mate   1718 F pulseaudio
   /dev/snd/controlC0:  ubuntu-mate   1718 F pulseaudio
  CasperVersion: 1.376
  CurrentDesktop: MATE
  Date: Wed May 11 00:43:52 2016
  LiveMediaBuild: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/04/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A10
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA10:bd11/04/2015:svnDellInc.:pnLatitude3340:pvr00:rvnDellInc.:rn:rvr:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude 3340
  dmi.product.version: 00
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1580394/+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 1580394] Re: [Latitude 3340, Realtek ALC3234] MATE - Headphone Static on Battery Power

2017-07-23 Thread spm2011
Possible duplicate of https://bugs.launchpad.net/ubuntu/+source/alsa-
driver/+bug/1547024

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

Title:
  [Latitude 3340, Realtek ALC3234] MATE - Headphone Static on Battery
  Power

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  I have noticed that when I am on battery power on a Dell Latitude 3340
  laptop with headphones plugged in , and there is no audio playing on
  the computer, there is a consistent static sound that comes through
  the headphones at a constant volume that is not affected by changing
  the volume level. I think it may be picking up some kind of analog
  loopback signal because keyboard presses and disk activity seem to
  influence the noise. When I plug the power cable into the laptop , the
  static immediately goes away.

  I reported this earlier to the upstream Linux Kernel bug tracker, but
  it seems to be fixed in any distro running a 4.4 kernel or greater
  that I have tested , Except for Ubuntu MATE 16.04 LTS 64-bit. This
  make me think it is not a kernel level issue and is found somewhere
  either in the audio settings on Ubuntu MATE or a pulseaudio bug. I
  cannot reproduce it on any other 16.04 distro version, but it also
  affects all the 14.04.4 distros as well.

  Running amixer -c 1 set "Loopback Mixing" "Disabled" does not prevent
  the static.

  The BIOS Firmware version is up to date.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: pulseaudio 1:8.0-0ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  ubuntu-mate   1718 F pulseaudio
   /dev/snd/controlC0:  ubuntu-mate   1718 F pulseaudio
  CasperVersion: 1.376
  CurrentDesktop: MATE
  Date: Wed May 11 00:43:52 2016
  LiveMediaBuild: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/04/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A10
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA10:bd11/04/2015:svnDellInc.:pnLatitude3340:pvr00:rvnDellInc.:rn:rvr:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude 3340
  dmi.product.version: 00
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1580394/+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 1580394] Re: [Latitude 3340, Realtek ALC3234] MATE - Headphone Static on Battery Power

2017-06-27 Thread spm2011
** Summary changed:

- [Latitude 3340, Realtek ALC3234, Headphone] Static in Headphones While on 
Battery Power
+ [Latitude 3340, Realtek ALC3234] MATE - Headphone Static on Battery Power

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

Title:
  [Latitude 3340, Realtek ALC3234] MATE - Headphone Static on Battery
  Power

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  I have noticed that when I am on battery power on a Dell Latitude 3340
  laptop with headphones plugged in , and there is no audio playing on
  the computer, there is a consistent static sound that comes through
  the headphones at a constant volume that is not affected by changing
  the volume level. I think it may be picking up some kind of analog
  loopback signal because keyboard presses and disk activity seem to
  influence the noise. When I plug the power cable into the laptop , the
  static immediately goes away.

  I reported this earlier to the upstream Linux Kernel bug tracker, but
  it seems to be fixed in any distro running a 4.4 kernel or greater
  that I have tested , Except for Ubuntu MATE 16.04 LTS 64-bit. This
  make me think it is not a kernel level issue and is found somewhere
  either in the audio settings on Ubuntu MATE or a pulseaudio bug. I
  cannot reproduce it on any other 16.04 distro version, but it also
  affects all the 14.04.4 distros as well.

  Running amixer -c 1 set "Loopback Mixing" "Disabled" does not prevent
  the static.

  The BIOS Firmware version is up to date.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: pulseaudio 1:8.0-0ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  ubuntu-mate   1718 F pulseaudio
   /dev/snd/controlC0:  ubuntu-mate   1718 F pulseaudio
  CasperVersion: 1.376
  CurrentDesktop: MATE
  Date: Wed May 11 00:43:52 2016
  LiveMediaBuild: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/04/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A10
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA10:bd11/04/2015:svnDellInc.:pnLatitude3340:pvr00:rvnDellInc.:rn:rvr:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude 3340
  dmi.product.version: 00
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1580394/+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 1583801] Re: No sound via headphones (headset) when Ubuntu boots with them plugged in

2017-06-19 Thread spm2011
Also affects ALC3234 on Dell Latitude 3340
See https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1670059

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

Title:
  No sound via headphones (headset) when Ubuntu boots with them plugged
  in

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  The bug is twofold, first when computer boots if the headset
  (headphones with built-in mic, one audio jack) is plugged in, then
  there is no sound (via headphones or otherwise). If you plug
  headphones out and back in, then it usually works as expected.

  The second scenario is the same, except that plugging out and back in
  again doesn't help. In that case, I just restart the laptop, then plug
  them back in again and it works.

  In all cases, microphone works.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  crunch 3248 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu May 19 22:13:20 2016
  InstallationDate: Installed on 2016-05-07 (12 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  crunch 3248 F pulseaudio
  Symptom_Jack: Black Headphone Out, Left
  Symptom_Type: No sound at all
  Title: [XPS 15 9550, Realtek ALC3266, Black Headphone Out, Left] No sound at 
all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/07/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 01.02.00
  dmi.board.name: 0N7TVV
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr01.02.00:bd04/07/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 15 9550
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1583801/+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 1670059] Re: [Latitude 3340, Realtek ALC3234] Headphones Not Detected if Plugged in before Boot

2017-05-26 Thread spm2011
See also https://bugs.launchpad.net/ubuntu/+source/alsa-
driver/+bug/1583801

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

Title:
  [Latitude 3340, Realtek ALC3234] Headphones Not Detected if Plugged in
  before Boot

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  When (re)booting with headphones in, audio won't play. Once the headphones 
are unplugged, it will start to come through the speakers and will work with 
the headphones when they are plugged back in.
  Expected headphones to be detected automatically even if plugged in before 
boot.

  This is on latest Xenial HWE kernel (4.8.0-39-generic x86_64).
  ALSA Info attached.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1670059/+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 1670059] Re: [Latitude 3340, Realtek ALC3234] Headphones Not Detected if Plugged in before Boot

2017-04-21 Thread spm2011
Headphones also stop working after logging out and back in, until they
are unplugged and plugged in again.

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

Title:
  [Latitude 3340, Realtek ALC3234] Headphones Not Detected if Plugged in
  before Boot

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  When (re)booting with headphones in, audio won't play. Once the headphones 
are unplugged, it will start to come through the speakers and will work with 
the headphones when they are plugged back in.
  Expected headphones to be detected automatically even if plugged in before 
boot.

  This is on latest Xenial HWE kernel (4.8.0-39-generic x86_64).
  ALSA Info attached.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1670059/+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 1567035] Re: Wi-Fi Completely Disabled after Lid Shut Suspend on Dell Latitude 3340

2017-03-27 Thread spm2011
Possible duplicate of
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1492850,
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1635907

Can't reproduce on latest Xenial HWE kernel.

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

Title:
  Wi-Fi Completely Disabled after Lid Shut Suspend on Dell Latitude 3340

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Wi-fi becomes disabled sometimes after the lid on the laptop is shut
  and the OS is suspended for a time. Bluetooth is turned off when this
  occurs.

  The network settings first reports "Wi-Fi is disabled" when the OS is 
resumed. If the user then disables and re-enables Networking or Wi-Fi via the 
menu option , the status of the Wi-Fi changes to say "Wi-Fi is disabled by 
hardware switch".
  Toggling the Fn-PrtScr keyboard hardware networking switch has no effect and 
does not actually re-enable the Wi-Fi. Running "sudo rfkill unblock wifi" also 
has no effect.

  The only known workaround is to restart the machine.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-4.2.0-34-generic 4.2.0-34.39~14.04.1
  ProcVersionSignature: Ubuntu 4.2.0-34.39~14.04.1-generic 4.2.8-ckt4
  Uname: Linux 4.2.0-34-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Apr  6 15:04:21 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-03-03 (33 days ago)
  InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release amd64 
(20160217.1)
  SourcePackage: linux-lts-wily
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1567035/+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 1670059] Re: [Latitude 3340, Realtek ALC3234] Headphones Not Detected if Plugged in before Boot

2017-03-04 Thread spm2011
** Description changed:

- When (re)booting with headphones in, audio won't play through headphones or 
speakers until the headphones are unplugged and plugged in again.
+ When (re)booting with headphones in, audio won't play. Once the headphones 
are unplugged, it will start to come through the speakers and will work with 
the headphones when they are plugged back in.
  Expected headphones to be detected automatically even if plugged in before 
boot.
  
- This is on latest Xenial HWE kernel (4.8.0-39-generic x86_64). ALSA Info
- attached.
+ This is on latest Xenial HWE kernel (4.8.0-39-generic x86_64).
+ ALSA Info attached.

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

Title:
  [Latitude 3340, Realtek ALC3234] Headphones Not Detected if Plugged in
  before Boot

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  When (re)booting with headphones in, audio won't play. Once the headphones 
are unplugged, it will start to come through the speakers and will work with 
the headphones when they are plugged back in.
  Expected headphones to be detected automatically even if plugged in before 
boot.

  This is on latest Xenial HWE kernel (4.8.0-39-generic x86_64).
  ALSA Info attached.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1670059/+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 1670059] [NEW] [Latitude 3340, Realtek ALC3234] Headphones Not Detected if Plugged in before Boot

2017-03-04 Thread spm2011
Public bug reported:

When (re)booting with headphones in, audio won't play through headphones or 
speakers until the headphones are unplugged and plugged in again.
Expected headphones to be detected automatically even if plugged in before boot.

This is on latest Xenial HWE kernel (4.8.0-39-generic x86_64). ALSA Info
attached.

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


** Tags: xenial

** Attachment added: "alsa-info.txt"
   
https://bugs.launchpad.net/bugs/1670059/+attachment/4831582/+files/alsa-info.txt

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

Title:
  [Latitude 3340, Realtek ALC3234] Headphones Not Detected if Plugged in
  before Boot

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  When (re)booting with headphones in, audio won't play through headphones or 
speakers until the headphones are unplugged and plugged in again.
  Expected headphones to be detected automatically even if plugged in before 
boot.

  This is on latest Xenial HWE kernel (4.8.0-39-generic x86_64). ALSA
  Info attached.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1670059/+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 1580394] Re: [Latitude 3340, Realtek ALC3234, Headphone] Static in Headphones While on Battery Power

2017-02-27 Thread spm2011
Still present in Ubuntu MATE 16.04.2 LTS 64-bit, not reproducible in any
other Xenial variant.

Similar to the issue described at https://askubuntu.com/questions/457910
/strange-noise-in-headphones-when-no-sound-is-played

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

Title:
  [Latitude 3340, Realtek ALC3234, Headphone] Static in Headphones While
  on Battery Power

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  I have noticed that when I am on battery power on a Dell Latitude 3340
  laptop with headphones plugged in , and there is no audio playing on
  the computer, there is a consistent static sound that comes through
  the headphones at a constant volume that is not affected by changing
  the volume level. I think it may be picking up some kind of analog
  loopback signal because keyboard presses and disk activity seem to
  influence the noise. When I plug the power cable into the laptop , the
  static immediately goes away.

  I reported this earlier to the upstream Linux Kernel bug tracker, but
  it seems to be fixed in any distro running a 4.4 kernel or greater
  that I have tested , Except for Ubuntu MATE 16.04 LTS 64-bit. This
  make me think it is not a kernel level issue and is found somewhere
  either in the audio settings on Ubuntu MATE or a pulseaudio bug. I
  cannot reproduce it on any other 16.04 distro version, but it also
  affects all the 14.04.4 distros as well.

  Running amixer -c 1 set "Loopback Mixing" "Disabled" does not prevent
  the static.

  The BIOS Firmware version is up to date.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: pulseaudio 1:8.0-0ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  ubuntu-mate   1718 F pulseaudio
   /dev/snd/controlC0:  ubuntu-mate   1718 F pulseaudio
  CasperVersion: 1.376
  CurrentDesktop: MATE
  Date: Wed May 11 00:43:52 2016
  LiveMediaBuild: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/04/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A10
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA10:bd11/04/2015:svnDellInc.:pnLatitude3340:pvr00:rvnDellInc.:rn:rvr:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude 3340
  dmi.product.version: 00
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1580394/+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 1580394] Re: Analog Loopback Static in Headphones while on Dell Latitude 3340 Battery Power

2017-02-27 Thread spm2011
** This bug is no longer a duplicate of bug 168
   [Inspiron 11 - 3147, Realtek ALC3234, Speaker, Internal] Has constant 
cracking sound, even when idel (no media playback). Muting and unmuting the 
sound seems to help for around half a minute...

** Summary changed:

- Analog Loopback Static in Headphones while on Dell Latitude 3340 Battery Power
+ [Latitude 3340, Realtek ALC3234, Headphone] Static in Headphones While on 
Battery Power

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

Title:
  [Latitude 3340, Realtek ALC3234, Headphone] Static in Headphones While
  on Battery Power

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  I have noticed that when I am on battery power on a Dell Latitude 3340
  laptop with headphones plugged in , and there is no audio playing on
  the computer, there is a consistent static sound that comes through
  the headphones at a constant volume that is not affected by changing
  the volume level. I think it may be picking up some kind of analog
  loopback signal because keyboard presses and disk activity seem to
  influence the noise. When I plug the power cable into the laptop , the
  static immediately goes away.

  I reported this earlier to the upstream Linux Kernel bug tracker, but
  it seems to be fixed in any distro running a 4.4 kernel or greater
  that I have tested , Except for Ubuntu MATE 16.04 LTS 64-bit. This
  make me think it is not a kernel level issue and is found somewhere
  either in the audio settings on Ubuntu MATE or a pulseaudio bug. I
  cannot reproduce it on any other 16.04 distro version, but it also
  affects all the 14.04.4 distros as well.

  Running amixer -c 1 set "Loopback Mixing" "Disabled" does not prevent
  the static.

  The BIOS Firmware version is up to date.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: pulseaudio 1:8.0-0ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  ubuntu-mate   1718 F pulseaudio
   /dev/snd/controlC0:  ubuntu-mate   1718 F pulseaudio
  CasperVersion: 1.376
  CurrentDesktop: MATE
  Date: Wed May 11 00:43:52 2016
  LiveMediaBuild: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/04/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A10
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA10:bd11/04/2015:svnDellInc.:pnLatitude3340:pvr00:rvnDellInc.:rn:rvr:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude 3340
  dmi.product.version: 00
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1580394/+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 1580394] Re: Analog Loopback Static in Headphones while on Dell Latitude 3340 Battery Power

2017-02-27 Thread spm2011
** Package changed: pulseaudio (Ubuntu) => alsa-driver (Ubuntu)

** This bug has been marked a duplicate of bug 168
   [Inspiron 11 - 3147, Realtek ALC3234, Speaker, Internal] Has constant 
cracking sound, even when idel (no media playback). Muting and unmuting the 
sound seems to help for around half a minute...

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

Title:
  [Latitude 3340, Realtek ALC3234, Headphone] Static in Headphones While
  on Battery Power

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  I have noticed that when I am on battery power on a Dell Latitude 3340
  laptop with headphones plugged in , and there is no audio playing on
  the computer, there is a consistent static sound that comes through
  the headphones at a constant volume that is not affected by changing
  the volume level. I think it may be picking up some kind of analog
  loopback signal because keyboard presses and disk activity seem to
  influence the noise. When I plug the power cable into the laptop , the
  static immediately goes away.

  I reported this earlier to the upstream Linux Kernel bug tracker, but
  it seems to be fixed in any distro running a 4.4 kernel or greater
  that I have tested , Except for Ubuntu MATE 16.04 LTS 64-bit. This
  make me think it is not a kernel level issue and is found somewhere
  either in the audio settings on Ubuntu MATE or a pulseaudio bug. I
  cannot reproduce it on any other 16.04 distro version, but it also
  affects all the 14.04.4 distros as well.

  Running amixer -c 1 set "Loopback Mixing" "Disabled" does not prevent
  the static.

  The BIOS Firmware version is up to date.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: pulseaudio 1:8.0-0ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  ubuntu-mate   1718 F pulseaudio
   /dev/snd/controlC0:  ubuntu-mate   1718 F pulseaudio
  CasperVersion: 1.376
  CurrentDesktop: MATE
  Date: Wed May 11 00:43:52 2016
  LiveMediaBuild: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/04/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A10
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA10:bd11/04/2015:svnDellInc.:pnLatitude3340:pvr00:rvnDellInc.:rn:rvr:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude 3340
  dmi.product.version: 00
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1580394/+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 1571882] Re: 5GHz Wi-Fi Intermittently Disconnects on Dell Latitude 3340

2017-02-18 Thread spm2011
** Package changed: linux-lts-wily (Ubuntu) => network-manager (Ubuntu)

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

Title:
  5GHz Wi-Fi Intermittently Disconnects on Dell Latitude 3340

Status in network-manager package in Ubuntu:
  New

Bug description:
  When connected to a 5GHz (802.11ac) WPA2 wireless network with UFW firewall 
enabled at system startup , I experience intermittent issues where the Wi-Fi 
completely disconnects and the 5G network is no longer displayed in the list of 
Wi-Fi Networks.
  Toggling the "Enable Wi-Fi" option resets the Wi-Fi and allows the user to 
reconnect.

  The latest A10 firmware version is installed on the laptop.

  I confirmed that the 5G network was still up and running , so the issue is 
most likely not on the router network end.
  I have no custom firewall rules that would cause this behaviour , but I do 
see a lot of multicast address resolution requests being blocked in the ufw 
logs.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-4.2.0-35-generic 4.2.0-35.40~14.04.1
  ProcVersionSignature: Ubuntu 4.2.0-35.40~14.04.1-generic 4.2.8-ckt5
  Uname: Linux 4.2.0-35-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Apr 18 18:32:30 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-03-03 (45 days ago)
  InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release amd64 
(20160217.1)
  SourcePackage: linux-lts-wily
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1571882/+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 1567035] Re: Wi-Fi Completely Disabled after Lid Shut Suspend on Dell Latitude 3340

2017-02-18 Thread spm2011
Moving this to NetworkManager so it gets triaged. I think this may be a
duplicate of an existing bug there.

** Package changed: linux-lts-wily (Ubuntu) => network-manager (Ubuntu)

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

Title:
  Wi-Fi Completely Disabled after Lid Shut Suspend on Dell Latitude 3340

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Wi-fi becomes disabled sometimes after the lid on the laptop is shut
  and the OS is suspended for a time. Bluetooth is turned off when this
  occurs.

  The network settings first reports "Wi-Fi is disabled" when the OS is 
resumed. If the user then disables and re-enables Networking or Wi-Fi via the 
menu option , the status of the Wi-Fi changes to say "Wi-Fi is disabled by 
hardware switch".
  Toggling the Fn-PrtScr keyboard hardware networking switch has no effect and 
does not actually re-enable the Wi-Fi. Running "sudo rfkill unblock wifi" also 
has no effect.

  The only known workaround is to restart the machine.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-4.2.0-34-generic 4.2.0-34.39~14.04.1
  ProcVersionSignature: Ubuntu 4.2.0-34.39~14.04.1-generic 4.2.8-ckt4
  Uname: Linux 4.2.0-34-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Apr  6 15:04:21 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-03-03 (33 days ago)
  InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release amd64 
(20160217.1)
  SourcePackage: linux-lts-wily
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1567035/+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 1580394] Re: Analog Loopback Static in Headphones while on Dell Latitude 3340 Battery Power

2016-05-11 Thread spm2011
** Also affects: ubuntu-mate
   Importance: Undecided
   Status: New

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

Title:
  Analog Loopback Static in Headphones while on Dell Latitude 3340
  Battery Power

Status in ubuntu-mate:
  New
Status in pulseaudio package in Ubuntu:
  New

Bug description:
  I have noticed that when I am on battery power on a Dell Latitude 3340
  laptop with headphones plugged in , and there is no audio playing on
  the computer, there is a consistent static sound that comes through
  the headphones at a constant volume that is not affected by changing
  the volume level. I think it may be picking up some kind of analog
  loopback signal because keyboard presses and disk activity seem to
  influence the noise. When I plug the power cable into the laptop , the
  static immediately goes away.

  I reported this earlier to the upstream Linux Kernel bug tracker, but
  it seems to be fixed in any distro running a 4.4 kernel or greater
  that I have tested , Except for Ubuntu MATE 16.04 LTS 64-bit. This
  make me think it is not a kernel level issue and is found somewhere
  either in the audio settings on Ubuntu MATE or a pulseaudio bug. I
  cannot reproduce it on any other 16.04 distro version, but it also
  affects all the 14.04.4 distros as well.

  Running amixer -c 1 set "Loopback Mixing" "Disabled" does not prevent
  the static.

  The BIOS Firmware version is up to date.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: pulseaudio 1:8.0-0ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  ubuntu-mate   1718 F pulseaudio
   /dev/snd/controlC0:  ubuntu-mate   1718 F pulseaudio
  CasperVersion: 1.376
  CurrentDesktop: MATE
  Date: Wed May 11 00:43:52 2016
  LiveMediaBuild: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/04/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A10
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA10:bd11/04/2015:svnDellInc.:pnLatitude3340:pvr00:rvnDellInc.:rn:rvr:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude 3340
  dmi.product.version: 00
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-mate/+bug/1580394/+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 1580394] [NEW] Analog Loopback Static in Headphones while on Dell Latitude 3340 Battery Power

2016-05-10 Thread spm2011
Public bug reported:

I have noticed that when I am on battery power on a Dell Latitude 3340
laptop with headphones plugged in , and there is no audio playing on the
computer, there is a consistent static sound that comes through the
headphones at a constant volume that is not affected by changing the
volume level. I think it may be picking up some kind of analog loopback
signal because keyboard presses and disk activity seem to influence the
noise. When I plug the power cable into the laptop , the static
immediately goes away.

I reported this earlier to the upstream Linux Kernel bug tracker, but it
seems to be fixed in any distro running a 4.4 kernel or greater that I
have tested , Except for Ubuntu MATE 16.04 LTS 64-bit. This make me
think it is not a kernel level issue and is found somewhere either in
the audio settings on Ubuntu MATE or a pulseaudio bug. I cannot
reproduce it on any other 16.04 distro version, but it also affects all
the 14.04.4 distros as well.

Running amixer -c 1 set "Loopback Mixing" "Disabled" does not prevent
the static.

The BIOS Firmware version is up to date.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: pulseaudio 1:8.0-0ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
Uname: Linux 4.4.0-21-generic x86_64
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  ubuntu-mate   1718 F pulseaudio
 /dev/snd/controlC0:  ubuntu-mate   1718 F pulseaudio
CasperVersion: 1.376
CurrentDesktop: MATE
Date: Wed May 11 00:43:52 2016
LiveMediaBuild: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: pulseaudio
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/04/2015
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A10
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvrA10:bd11/04/2015:svnDellInc.:pnLatitude3340:pvr00:rvnDellInc.:rn:rvr:cvnDellInc.:ct9:cvr:
dmi.product.name: Latitude 3340
dmi.product.version: 00
dmi.sys.vendor: Dell Inc.

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


** Tags: amd64 apport-bug trusty xenial

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

Title:
  Analog Loopback Static in Headphones while on Dell Latitude 3340
  Battery Power

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  I have noticed that when I am on battery power on a Dell Latitude 3340
  laptop with headphones plugged in , and there is no audio playing on
  the computer, there is a consistent static sound that comes through
  the headphones at a constant volume that is not affected by changing
  the volume level. I think it may be picking up some kind of analog
  loopback signal because keyboard presses and disk activity seem to
  influence the noise. When I plug the power cable into the laptop , the
  static immediately goes away.

  I reported this earlier to the upstream Linux Kernel bug tracker, but
  it seems to be fixed in any distro running a 4.4 kernel or greater
  that I have tested , Except for Ubuntu MATE 16.04 LTS 64-bit. This
  make me think it is not a kernel level issue and is found somewhere
  either in the audio settings on Ubuntu MATE or a pulseaudio bug. I
  cannot reproduce it on any other 16.04 distro version, but it also
  affects all the 14.04.4 distros as well.

  Running amixer -c 1 set "Loopback Mixing" "Disabled" does not prevent
  the static.

  The BIOS Firmware version is up to date.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: pulseaudio 1:8.0-0ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  ubuntu-mate   1718 F pulseaudio
   /dev/snd/controlC0:  ubuntu-mate   1718 F pulseaudio
  CasperVersion: 1.376
  CurrentDesktop: MATE
  Date: Wed May 11 00:43:52 2016
  LiveMediaBuild: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/04/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A10
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA10:bd11/04/2015:svnDellInc.:pnLatitude3340:pvr00:rvnDellInc.:rn:rvr:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude 3340
  dmi.product.version: 00
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to: