[Touch-packages] [Bug 1698083] Re: Maximize vertically/horizontally doesn't work (in some apps) if configured via middle-click

2022-10-04 Thread Joe Barnett
looks like https://gitlab.gnome.org/GNOME/gtk/-/merge_requests/5070
addresses this in gtk3 apps, can it (and/or the next gtk release) be
added to the ubuntu package and the snap package that contains gtk3
(gnome-* snap?)

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

Title:
  Maximize vertically/horizontally doesn't work (in some apps) if
  configured via middle-click

Status in GTK+:
  Fix Released
Status in gnome-control-center package in Ubuntu:
  Confirmed
Status in gtk+3.0 package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Triaged

Bug description:
  Upstream: https://gitlab.gnome.org/GNOME/gtk/issues/539

  In Gnome Tweak Tool you can configure vertical maximizing for:
    Windows > Titlebar Actions > Middle-Click
  However this feature seems to get ignored in Wayland sessions (it just 
maximizes fully instead). It only works correctly in Xorg Gnome sessions.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.24.2-0ubuntu6
  ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15
  Uname: Linux 4.10.0-22-generic x86_64
  ApportVersion: 2.20.5-0ubuntu4
  Architecture: amd64
  Date: Thu Jun 15 14:46:04 2017
  DisplayManager: lightdm
  InstallationDate: Installed on 2017-05-03 (43 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170502)
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gtk/+bug/1698083/+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 1986861] [NEW] pulseaudio stops accepting connections

2022-08-17 Thread Joe Barnett
Public bug reported:

After a while, pulseaudio clients get connections refused and are unable
to play audio / receive microphone input.

journalctl shows lots of messages like:

Aug 17 13:00:17 taplop pulseaudio[2244465]: [pulseaudio] native-common.c: 
Expected 1 memfd fd to be received over pipe; got 0
Aug 17 13:00:17 taplop pulseaudio[2244465]: [pulseaudio] native-common.c: Did 
we reach our open file descriptors limit?
Aug 17 13:00:17 taplop pulseaudio[2244465]: [pulseaudio] protocol-native.c: 
protocol error, kicking client


as well as 

Aug 17 13:03:52 taplop pulseaudio[2244465]: [pulseaudio] protocol-
native.c: Warning! Too many connections (64), dropping incoming
connection.


killing the pulseaudio daemon makes audio work for a little while until the 
same thing repeats.  not sure what's triggering it though, or how to best find 
out.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: pulseaudio 1:15.99.1+dfsg1-1ubuntu1
Uname: Linux 5.17.0-051700drmtip20220329-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  jbarnett  2265029 F pulseaudio
CasperMD5CheckResult: unknown
CurrentDesktop: GNOME
Date: Wed Aug 17 14:13:56 2022
InstallationDate: Installed on 2019-08-17 (1096 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305.1)
RebootRequiredPkgs: Error: path contained symlinks.
SourcePackage: pulseaudio
UpgradeStatus: Upgraded to jammy on 2022-03-18 (152 days ago)
dmi.bios.date: 03/25/2021
dmi.bios.release: 1.15
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.15.1
dmi.board.name: 0N338G
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 31
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.15.1:bd03/25/2021:br1.15:svnDellInc.:pnXPS159575:pvr:rvnDellInc.:rn0N338G:rvrA00:cvnDellInc.:ct31:cvr:sku080D:
dmi.product.family: XPS
dmi.product.name: XPS 15 9575
dmi.product.sku: 080D
dmi.sys.vendor: Dell Inc.

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


** Tags: amd64 apport-bug jammy wayland-session

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

Title:
  pulseaudio stops accepting connections

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  After a while, pulseaudio clients get connections refused and are
  unable to play audio / receive microphone input.

  journalctl shows lots of messages like:

  Aug 17 13:00:17 taplop pulseaudio[2244465]: [pulseaudio] native-common.c: 
Expected 1 memfd fd to be received over pipe; got 0
  Aug 17 13:00:17 taplop pulseaudio[2244465]: [pulseaudio] native-common.c: Did 
we reach our open file descriptors limit?
  Aug 17 13:00:17 taplop pulseaudio[2244465]: [pulseaudio] protocol-native.c: 
protocol error, kicking client

  
  as well as 

  Aug 17 13:03:52 taplop pulseaudio[2244465]: [pulseaudio] protocol-
  native.c: Warning! Too many connections (64), dropping incoming
  connection.

  
  killing the pulseaudio daemon makes audio work for a little while until the 
same thing repeats.  not sure what's triggering it though, or how to best find 
out.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: pulseaudio 1:15.99.1+dfsg1-1ubuntu1
  Uname: Linux 5.17.0-051700drmtip20220329-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jbarnett  2265029 F pulseaudio
  CasperMD5CheckResult: unknown
  CurrentDesktop: GNOME
  Date: Wed Aug 17 14:13:56 2022
  InstallationDate: Installed on 2019-08-17 (1096 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305.1)
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to jammy on 2022-03-18 (152 days ago)
  dmi.bios.date: 03/25/2021
  dmi.bios.release: 1.15
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.15.1
  dmi.board.name: 0N338G
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 31
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.15.1:bd03/25/2021:br1.15:svnDellInc.:pnXPS159575:pvr:rvnDellInc.:rn0N338G:rvrA00:cvnDellInc.:ct31:cvr:sku080D:
  dmi.product.family: XPS
  dmi.product.name: XPS 15 9575
  dmi.product.sku: 080D
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1986861/+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 1966571] Re: libva error: /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so init failed

2022-03-29 Thread Joe Barnett
seeing the same behavior with the -non-free version too, does it need a
separate rebuild?

** Also affects: intel-media-driver-non-free (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  libva error: /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so init
  failed

Status in intel-media-driver package in Ubuntu:
  Fix Committed
Status in intel-media-driver-non-free package in Ubuntu:
  New
Status in mesa package in Ubuntu:
  Invalid

Bug description:
  I noticed that it upgraded mesa to 22.x and now video acceleration is
  not working due to:

  ❯ vainfo 
  libva info: VA-API version 1.14.0
  libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so
  libva info: Found init function __vaDriverInit_1_14
  libva error: /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so init failed
  libva info: va_openDriver() returns 1
  libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so
  libva info: Found init function __vaDriverInit_1_10
  libva error: /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so init failed
  libva info: va_openDriver() returns -1
  vaInitialize failed with error code -1 (unknown libva error),exit
  ~/Desktop 
  ❯ inxi -G
  Graphics:
Device-1: Intel driver: i915 v: kernel
Device-2: Generalplus GENERAL WEBCAM type: USB
  driver: snd-usb-audio,uvcvideo
Display: x11 server: X.Org v: 1.21.1.3 driver: X: loaded: modesetting
  unloaded: fbdev,vesa gpu: i915 resolution: 3840x2160~60Hz
OpenGL: renderer: Mesa Intel UHD Graphics P630 (CML GT2)
  v: 4.6 Mesa 22.0.0

  I tried rebuilding the i965-va-driver, and it's still the same.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: mesa-vdpau-drivers 22.0.0-0ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Uname: Linux 5.15.0-23-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Mar 27 10:37:41 2022
  DistUpgraded: 2022-01-18 23:59:55,390 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
  DistroCodename: jammy
  DistroVariant: ubuntu
  DkmsStatus:
   rtl88x2bu/5.8.7.1, 5.15.0-18-generic, x86_64: installed
   rtl88x2bu/5.8.7.1, 5.15.0-22-generic, x86_64: installed
   rtl88x2bu/5.8.7.1, 5.15.0-23-generic, x86_64: installed
   rtl88x2bu/5.8.7.1, 5.17.0-xanmod1, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Device [8086:9bc6] (rev 05) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Device [1043:8694]
  InstallationDate: Installed on 2021-10-05 (172 days ago)
  InstallationMedia: Ubuntu-Server 21.10 "Impish Indri" - Beta amd64 (20211004)
  MachineType: ASUS System Product Name
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_PH.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-23-generic 
root=UUID=018d5b69-accd-451b-a6f7-2027f791ea0e ro quiet splash vt.handoff=7
  SourcePackage: mesa
  UpgradeStatus: Upgraded to jammy on 2022-01-18 (67 days ago)
  dmi.bios.date: 07/08/2021
  dmi.bios.release: 23.1
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2301
  dmi.board.asset.tag: Default string
  dmi.board.name: Pro WS W480-ACE
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2301:bd07/08/2021:br23.1:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnProWSW480-ACE:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.110-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.0-0ubuntu2
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/intel-media-driver/+bug/1966571/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@

[Touch-packages] [Bug 1965647] Re: pulseaudio gets stuck after launching firefox

2022-03-19 Thread Joe Barnett
seems like pulse was fighting with pipewire; not sure what I did to
clean it up but appears to be working better now

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

Title:
  pulseaudio gets stuck after launching firefox

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  after updating to jammy, pulseaudio appears to get stuck after opening
  firefox.

  I can play an audio file using mplayer fine, then I open firefox (either snap 
or deb version), then it fails to play the same audio file and prints out
  "Audio device got stuck!"

  killing pulseaudio (and having systemd user session restart it)
  restores sound in mplayer

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: pulseaudio 1:15.99.1+dfsg1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Uname: Linux 5.15.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  jbarnett   3283 F wireplumber
   /dev/snd/controlC0:  jbarnett   3283 F wireplumber
    jbarnett   7684 F pulseaudio
   /dev/snd/seq:jbarnett   3278 F pipewire
  CasperMD5CheckResult: unknown
  CurrentDesktop: GNOME
  Date: Sat Mar 19 15:29:11 2022
  InstallationDate: Installed on 2019-08-17 (945 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305.1)
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to jammy on 2022-03-18 (1 days ago)
  dmi.bios.date: 03/25/2021
  dmi.bios.release: 1.15
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.15.1
  dmi.board.name: 0N338G
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 31
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.15.1:bd03/25/2021:br1.15:svnDellInc.:pnXPS159575:pvr:rvnDellInc.:rn0N338G:rvrA00:cvnDellInc.:ct31:cvr:sku080D:
  dmi.product.family: XPS
  dmi.product.name: XPS 15 9575
  dmi.product.sku: 080D
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1965647/+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 1965647] [NEW] pulseaudio gets stuck after launching firefox

2022-03-19 Thread Joe Barnett
Public bug reported:

after updating to jammy, pulseaudio appears to get stuck after opening
firefox.

I can play an audio file using mplayer fine, then I open firefox (either snap 
or deb version), then it fails to play the same audio file and prints out
"Audio device got stuck!"

killing pulseaudio (and having systemd user session restart it) restores
sound in mplayer

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: pulseaudio 1:15.99.1+dfsg1-1ubuntu1
ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
Uname: Linux 5.15.0-23-generic x86_64
ApportVersion: 2.20.11-0ubuntu79
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  jbarnett   3283 F wireplumber
 /dev/snd/controlC0:  jbarnett   3283 F wireplumber
  jbarnett   7684 F pulseaudio
 /dev/snd/seq:jbarnett   3278 F pipewire
CasperMD5CheckResult: unknown
CurrentDesktop: GNOME
Date: Sat Mar 19 15:29:11 2022
InstallationDate: Installed on 2019-08-17 (945 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305.1)
SourcePackage: pulseaudio
UpgradeStatus: Upgraded to jammy on 2022-03-18 (1 days ago)
dmi.bios.date: 03/25/2021
dmi.bios.release: 1.15
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.15.1
dmi.board.name: 0N338G
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 31
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.15.1:bd03/25/2021:br1.15:svnDellInc.:pnXPS159575:pvr:rvnDellInc.:rn0N338G:rvrA00:cvnDellInc.:ct31:cvr:sku080D:
dmi.product.family: XPS
dmi.product.name: XPS 15 9575
dmi.product.sku: 080D
dmi.sys.vendor: Dell Inc.

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


** Tags: amd64 apport-bug jammy wayland-session

** Description changed:

  after updating to jammy, pulseaudio appears to get stuck after opening
  firefox.
  
- I can play an audio file using mplayer fine, then I open firefox, then it 
fails to play the same audio file and prints out
+ I can play an audio file using mplayer fine, then I open firefox (either snap 
or deb version), then it fails to play the same audio file and prints out
  "Audio device got stuck!"
  
  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: pulseaudio 1:15.99.1+dfsg1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Uname: Linux 5.15.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  AudioDevicesInUse:
-  USERPID ACCESS COMMAND
-  /dev/snd/controlC1:  jbarnett   3283 F wireplumber
-  /dev/snd/controlC0:  jbarnett   3283 F wireplumber
-   jbarnett   7684 F pulseaudio
-  /dev/snd/seq:jbarnett   3278 F pipewire
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC1:  jbarnett   3283 F wireplumber
+  /dev/snd/controlC0:  jbarnett   3283 F wireplumber
+   jbarnett   7684 F pulseaudio
+  /dev/snd/seq:jbarnett   3278 F pipewire
  CasperMD5CheckResult: unknown
  CurrentDesktop: GNOME
  Date: Sat Mar 19 15:29:11 2022
  InstallationDate: Installed on 2019-08-17 (945 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305.1)
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to jammy on 2022-03-18 (1 days ago)
  dmi.bios.date: 03/25/2021
  dmi.bios.release: 1.15
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.15.1
  dmi.board.name: 0N338G
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 31
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.15.1:bd03/25/2021:br1.15:svnDellInc.:pnXPS159575:pvr:rvnDellInc.:rn0N338G:rvrA00:cvnDellInc.:ct31:cvr:sku080D:
  dmi.product.family: XPS
  dmi.product.name: XPS 15 9575
  dmi.product.sku: 080D
  dmi.sys.vendor: Dell Inc.

** Description changed:

  after updating to jammy, pulseaudio appears to get stuck after opening
  firefox.
  
- I can play an audio file using mplayer fine, then I open firefox (either snap 
or deb version), then it fails to play the same audio file and prints out
+ I can play an audio file using mplayer fine, then I open firefox, then it 
fails to play the same audio file and prints out
  "Audio device got stuck!"
+ 
+ killing pulseaudio (and having systemd user session restart it) restores
+ sound in mplayer
  
  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: pulseaudio 1:15.99.1+dfsg1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Uname: Linux 5.15.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  jbarnett   3283 F wireplumber
   /dev/snd/controlC0:  jbarnett   3283 F wireplumber
    jbarnett   7684 F pulseaudio
   /dev/snd/seq:jbarnett   3278 F pipewire
  CasperMD5CheckResult: unknown
  CurrentDesktop: GNOME
  Date: Sat Mar 19 15:29:11 2022
  InstallationDate: Inst

[Touch-packages] [Bug 1916651] [NEW] asks about irc user home directory during upgrade

2021-02-23 Thread Joe Barnett
Public bug reported:

Upgrading from groovy to hirsuite, base-passwd asks if the `irc` user's
home directory should be moved from `/var/run/ircd` to `/run/ircd`.
Having no IRC server installed makes this very confusing, but appears
harmless (https://askubuntu.com/questions/876975/user-irc-inside-of-
default-ubuntu-16-04-server).  Possibly caused by
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=946884, but can this
not prompt the user for a decision?

ProblemType: Bug
DistroRelease: Ubuntu 21.04
Package: base-passwd 3.5.49
ProcVersionSignature: Ubuntu 5.8.0-44.50-generic 5.8.18
Uname: Linux 5.8.0-44-generic x86_64
ApportVersion: 2.20.11-0ubuntu59
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: GNOME
Date: Tue Feb 23 12:02:59 2021
InstallationDate: Installed on 2019-08-17 (556 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305.1)
RebootRequiredPkgs:
 libc6
 libc6
 libssl1.1
 libssl1.1
SourcePackage: base-passwd
UpgradeStatus: Upgraded to hirsute on 2021-02-23 (0 days ago)

** Affects: base-passwd (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug hirsute third-party-packages wayland-session

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

Title:
  asks about irc user home directory during upgrade

Status in base-passwd package in Ubuntu:
  New

Bug description:
  Upgrading from groovy to hirsuite, base-passwd asks if the `irc`
  user's home directory should be moved from `/var/run/ircd` to
  `/run/ircd`.  Having no IRC server installed makes this very
  confusing, but appears harmless
  (https://askubuntu.com/questions/876975/user-irc-inside-of-default-
  ubuntu-16-04-server).  Possibly caused by https://bugs.debian.org/cgi-
  bin/bugreport.cgi?bug=946884, but can this not prompt the user for a
  decision?

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: base-passwd 3.5.49
  ProcVersionSignature: Ubuntu 5.8.0-44.50-generic 5.8.18
  Uname: Linux 5.8.0-44-generic x86_64
  ApportVersion: 2.20.11-0ubuntu59
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: GNOME
  Date: Tue Feb 23 12:02:59 2021
  InstallationDate: Installed on 2019-08-17 (556 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305.1)
  RebootRequiredPkgs:
   libc6
   libc6
   libssl1.1
   libssl1.1
  SourcePackage: base-passwd
  UpgradeStatus: Upgraded to hirsute on 2021-02-23 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/base-passwd/+bug/1916651/+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 1884126] Re: Trying to add google account fails with AUTH-1140

2020-06-18 Thread Joe Barnett
** Bug watch added: gitlab.gnome.org/GNOME/gnome-online-accounts/-/issues #126
   https://gitlab.gnome.org/GNOME/gnome-online-accounts/-/issues/126

** Also affects: gnome-online-accounts via
   https://gitlab.gnome.org/GNOME/gnome-online-accounts/-/issues/126
   Importance: Unknown
   Status: Unknown

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

Title:
  Trying to add google account fails with AUTH-1140

Status in gnome-online-accounts:
  Unknown
Status in gnome-online-accounts package in Ubuntu:
  New

Bug description:
  Trying to add a google account that redirects to another site for sign
  in results in a window with the following error:

  {"status":"failed", "cause":[{"code":"AUTH-1140", "message": "There is
  an invalid header value that can't be parsed."}]}

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-online-accounts 3.36.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41
  Uname: Linux 5.4.0-37-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: GNOME
  Date: Thu Jun 18 11:41:17 2020
  InstallationDate: Installed on 2019-08-17 (306 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305.1)
  SourcePackage: gnome-online-accounts
  UpgradeStatus: Upgraded to focal on 2020-03-06 (104 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-online-accounts/+bug/1884126/+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 1884126] [NEW] Trying to add google account fails with AUTH-1140

2020-06-18 Thread Joe Barnett
Public bug reported:

Trying to add a google account that redirects to another site for sign
in results in a window with the following error:

{"status":"failed", "cause":[{"code":"AUTH-1140", "message": "There is
an invalid header value that can't be parsed."}]}

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gnome-online-accounts 3.36.0-1ubuntu1
ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41
Uname: Linux 5.4.0-37-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.3
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: GNOME
Date: Thu Jun 18 11:41:17 2020
InstallationDate: Installed on 2019-08-17 (306 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305.1)
SourcePackage: gnome-online-accounts
UpgradeStatus: Upgraded to focal on 2020-03-06 (104 days ago)

** Affects: gnome-online-accounts (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug focal wayland-session

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

Title:
  Trying to add google account fails with AUTH-1140

Status in gnome-online-accounts package in Ubuntu:
  New

Bug description:
  Trying to add a google account that redirects to another site for sign
  in results in a window with the following error:

  {"status":"failed", "cause":[{"code":"AUTH-1140", "message": "There is
  an invalid header value that can't be parsed."}]}

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-online-accounts 3.36.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41
  Uname: Linux 5.4.0-37-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: GNOME
  Date: Thu Jun 18 11:41:17 2020
  InstallationDate: Installed on 2019-08-17 (306 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305.1)
  SourcePackage: gnome-online-accounts
  UpgradeStatus: Upgraded to focal on 2020-03-06 (104 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1884126/+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 1546603] Re: Bluetooth mouse connects but doesn't work ("Unable to register GATT service")

2017-05-30 Thread Joe Barnett
the workaround works.  i haven't tried newer version w/out the
workaround.

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

Title:
  Bluetooth mouse connects but doesn't work ("Unable to register GATT
  service")

Status in bluez package in Ubuntu:
  Incomplete

Bug description:
  I have a bluetooth mouse that I can get to connect via the gnome
  bluetooth settings panel, but even after it's connected it doesn't
  move the pointer or register any clicks.

  the following shows up in the journal :

  $ $ journalctl -b 0 |grep bluetooth
  Feb 17 07:18:22 spiny bluetoothd[1009]: Bluetooth daemon 5.36
  Feb 17 07:18:22 spiny bluetoothd[1009]: Starting SDP server
  Feb 17 07:18:22 spiny bluetoothd[1009]: Bluetooth management interface 1.10 
initialized
  Feb 17 07:18:22 spiny bluetoothd[1009]: Failed to obtain handles for "Service 
Changed" characteristic
  Feb 17 07:18:22 spiny bluetoothd[1009]: Not enough free handles to register 
service
  Feb 17 07:18:22 spiny bluetoothd[1009]: Error adding Link Loss service
  Feb 17 07:18:22 spiny bluetoothd[1009]: Not enough free handles to register 
service
  Feb 17 07:18:22 spiny bluetoothd[1009]: Not enough free handles to register 
service
  Feb 17 07:18:22 spiny bluetoothd[1009]: Not enough free handles to register 
service
  Feb 17 07:18:22 spiny bluetoothd[1009]: Current Time Service could not be 
registered
  Feb 17 07:18:22 spiny bluetoothd[1009]: gatt-time-server: Input/output error 
(5)
  Feb 17 07:18:22 spiny bluetoothd[1009]: Not enough free handles to register 
service
  Feb 17 07:18:22 spiny bluetoothd[1009]: Not enough free handles to register 
service
  Feb 17 07:18:22 spiny bluetoothd[1009]: Sap driver initialization failed.
  Feb 17 07:18:22 spiny bluetoothd[1009]: sap-server: Operation not permitted 
(1)
  Feb 17 07:18:22 spiny NetworkManager[1062]:   Loaded device plugin: 
NMBluezManager 
(/usr/lib/x86_64-linux-gnu/NetworkManager/libnm-device-plugin-bluetooth.so)
  Feb 17 07:18:24 spiny bluetoothd[1009]: Endpoint registered: sender=:1.42 
path=/MediaEndpoint/A2DPSource
  Feb 17 07:18:24 spiny bluetoothd[1009]: Endpoint registered: sender=:1.42 
path=/MediaEndpoint/A2DPSink
  Feb 17 07:18:42 spiny bluetoothd[1009]: Endpoint registered: sender=:1.71 
path=/MediaEndpoint/A2DPSource
  Feb 17 07:18:42 spiny bluetoothd[1009]: Endpoint registered: sender=:1.71 
path=/MediaEndpoint/A2DPSink
  Feb 17 07:18:42 spiny bluetoothd[1009]: RFCOMM server failed for Headset 
Voice gateway: rfcomm_bind: Address already in use (98)
  Feb 17 07:18:52 spiny gnome-bluetooth-panel.desktop[2717]: ** 
(gnome-control-center.real:2717): WARNING **: Ignoring launcher gufw (missing 
desktop file)
  Feb 17 07:18:52 spiny gnome-bluetooth-panel.desktop[2717]: ** 
(gnome-control-center.real:2717): WARNING **: Ignoring launcher 
landscape-client-settings (missing desktop file)
  Feb 17 07:18:52 spiny gnome-bluetooth-panel.desktop[2717]: ** 
(gnome-control-center.real:2717): WARNING **: Ignoring launcher 
language-selector (missing desktop file)
  Feb 17 07:18:52 spiny gnome-bluetooth-panel.desktop[2717]: ** 
(gnome-control-center.real:2717): WARNING **: Ignoring launcher 
ubuntuone-installer (missing desktop file)
  Feb 17 07:19:00 spiny gnome-bluetooth-panel.desktop[2717]: 
(gnome-control-center.real:2717): GLib-CRITICAL **: g_ascii_strdown: assertion 
'str != NULL' failed
  Feb 17 07:19:01 spiny bluetoothd[1009]: No cache for F2:3F:5C:A1:F9:F7
  Feb 17 07:19:06 spiny bluetoothd[1009]: Unable to register GATT service with 
handle 0x000c for device F2:3F:5C:A1:F9:F7
  Feb 17 07:19:06 spiny bluetoothd[1009]: Unable to register GATT service with 
handle 0x001b for device F2:3F:5C:A1:F9:F7
  Feb 17 07:19:06 spiny bluetoothd[1009]: Unable to register GATT service with 
handle 0x003f for device F2:3F:5C:A1:F9:F7
  Feb 17 07:19:06 spiny bluetoothd[1009]: Report Map read failed: Attribute 
requires authentication before read/write
  Feb 17 07:19:06 spiny bluetoothd[1009]: Protocol Mode characteristic read 
failed: Attribute requires authentication before read/write
  Feb 17 07:19:06 spiny bluetoothd[1009]: HID Information read failed: 
Attribute requires authentication before read/write
  Feb 17 07:19:06 spiny bluetoothd[1009]: Read Report Reference descriptor 
failed: Attribute requires authentication before read/write
  Feb 17 07:19:06 spiny bluetoothd[1009]: Read Report Reference descriptor 
failed: Attribute requires authentication before read/write
  Feb 17 07:19:06 spiny bluetoothd[1009]: Read Report Reference descriptor 
failed: Attribute requires authentication before read/write
  Feb 17 07:19:06 spiny bluetoothd[1009]: Read Report Reference descriptor 
failed: Attribute requires authentication before read/write
  Feb 17 07:19:08 spiny gnome-bluetooth-panel.desktop[2717]: 
(gnome-control-center.real:2717): GLib-CRITICAL **: g_ascii_strdown: assertion 
'str 

[Touch-packages] [Bug 1629620] Re: DNS resolver stops accepting queries

2016-10-16 Thread Joe Barnett
this seems to be less of a problem after switching /etc/resolv.conf to
point to the systemd-resolved managed file instead of the resolvconf
managed file.  not sure exactly which package should be changed to have
this work automatically?

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

Title:
  DNS resolver stops accepting queries

Status in network-manager package in Ubuntu:
  New

Bug description:
  After a while / after resume from suspend, the system becomes unable
  to respond to DNS queries, with the following output for example:

  $ nslookup google.com 127.0.1.1
  Server:   127.0.1.1
  Address:  127.0.1.1#53

  ** server can't find google.com: REFUSED

  
  This is on an up to date yakkety install.  Changing resolv.conf to use 
8.8.8.8, or restarting network-manager appears to fix this, at least until it 
recurs again.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: network-manager 1.2.4-0ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-17.19-generic 4.8.0-rc7
  Uname: Linux 4.8.0-17-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sat Oct  1 21:28:51 2016
  EcryptfsInUse: Yes
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2015-08-21 (407 days ago)
  InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha amd64 (20150819)
  IpRoute:
   default via 192.168.1.1 dev wlp3s0  proto static  metric 600 
   169.254.0.0/16 dev docker0  scope link  metric 1000 linkdown 
   172.17.0.0/16 dev docker0  proto kernel  scope link  src 172.17.0.1 linkdown 
   192.168.1.0/24 dev wlp3s0  proto kernel  scope link  src 192.168.1.5  metric 
600
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to yakkety on 2016-09-29 (2 days ago)
  nmcli-dev:
   DEVICE TYPE  STATE DBUS-PATH 
 CONNECTION   CON-UUID  CON-PATH
   
   docker0bridgeconnected 
/org/freedesktop/NetworkManager/Devices/1  docker0  
63f0b05b-f699-4a68-81ce-f62d2c1a247d  
/org/freedesktop/NetworkManager/ActiveConnection/0 
   wlp3s0 wifi  connected 
/org/freedesktop/NetworkManager/Devices/4  HOME-1622-5  
6df3f2f0-fb86-43b5-802a-d59bc5734be3  
/org/freedesktop/NetworkManager/ActiveConnection/2 
   24:DA:9B:B9:09:0E  btdisconnected  
/org/freedesktop/NetworkManager/Devices/3  --   --  
  -- 
   lo loopback  unmanaged 
/org/freedesktop/NetworkManager/Devices/2  --   --  
  --
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.2.4connected  started  full  enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1629620/+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 1631980] Re: Steam not able to see network in yakkety

2016-10-10 Thread Joe Barnett
possibly caused by switch to systemd-resolved?

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

Title:
  Steam not able to see network in yakkety

Status in steam package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  New

Bug description:
  Steam is unable to see the network in yakkety.  Downloads stall and
  don't do anything; and trying to update steam results in a "Fatal
  Error: Steam needs to be online to update.  Please confirm your
  network connection and try again" dialog box.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: steam:i386 1:1.0.0.52-5ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-21.23-generic 4.8.0
  Uname: Linux 4.8.0-21-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Oct 10 07:43:55 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-08-21 (416 days ago)
  InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha amd64 (20150819)
  PackageArchitecture: i386
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: steam
  UpgradeStatus: Upgraded to yakkety on 2016-09-29 (10 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/steam/+bug/1631980/+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 1631980] [NEW] Steam not able to see network in yakkety

2016-10-10 Thread Joe Barnett
Public bug reported:

Steam is unable to see the network in yakkety.  Downloads stall and
don't do anything; and trying to update steam results in a "Fatal Error:
Steam needs to be online to update.  Please confirm your network
connection and try again" dialog box.

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: steam:i386 1:1.0.0.52-5ubuntu1
ProcVersionSignature: Ubuntu 4.8.0-21.23-generic 4.8.0
Uname: Linux 4.8.0-21-generic x86_64
ApportVersion: 2.20.3-0ubuntu7
Architecture: amd64
CurrentDesktop: GNOME
Date: Mon Oct 10 07:43:55 2016
EcryptfsInUse: Yes
InstallationDate: Installed on 2015-08-21 (416 days ago)
InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha amd64 (20150819)
PackageArchitecture: i386
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: steam
UpgradeStatus: Upgraded to yakkety on 2016-09-29 (10 days ago)

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

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


** Tags: apport-bug i386 yakkety

** Also affects: systemd (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  Steam not able to see network in yakkety

Status in steam package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  New

Bug description:
  Steam is unable to see the network in yakkety.  Downloads stall and
  don't do anything; and trying to update steam results in a "Fatal
  Error: Steam needs to be online to update.  Please confirm your
  network connection and try again" dialog box.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: steam:i386 1:1.0.0.52-5ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-21.23-generic 4.8.0
  Uname: Linux 4.8.0-21-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Oct 10 07:43:55 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-08-21 (416 days ago)
  InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha amd64 (20150819)
  PackageArchitecture: i386
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: steam
  UpgradeStatus: Upgraded to yakkety on 2016-09-29 (10 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/steam/+bug/1631980/+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 1629620] [NEW] DNS resolver stops accepting queries

2016-10-01 Thread Joe Barnett
Public bug reported:

After a while / after resume from suspend, the system becomes unable to
respond to DNS queries, with the following output for example:

$ nslookup google.com 127.0.1.1
Server: 127.0.1.1
Address:127.0.1.1#53

** server can't find google.com: REFUSED


This is on an up to date yakkety install.  Changing resolv.conf to use 8.8.8.8, 
or restarting network-manager appears to fix this, at least until it recurs 
again.

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: network-manager 1.2.4-0ubuntu1
ProcVersionSignature: Ubuntu 4.8.0-17.19-generic 4.8.0-rc7
Uname: Linux 4.8.0-17-generic x86_64
ApportVersion: 2.20.3-0ubuntu7
Architecture: amd64
CurrentDesktop: GNOME
Date: Sat Oct  1 21:28:51 2016
EcryptfsInUse: Yes
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
InstallationDate: Installed on 2015-08-21 (407 days ago)
InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha amd64 (20150819)
IpRoute:
 default via 192.168.1.1 dev wlp3s0  proto static  metric 600 
 169.254.0.0/16 dev docker0  scope link  metric 1000 linkdown 
 172.17.0.0/16 dev docker0  proto kernel  scope link  src 172.17.0.1 linkdown 
 192.168.1.0/24 dev wlp3s0  proto kernel  scope link  src 192.168.1.5  metric 
600
NetworkManager.state:
 [main]
 NetworkingEnabled=true
 WirelessEnabled=true
 WWANEnabled=true
 WimaxEnabled=true
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: network-manager
UpgradeStatus: Upgraded to yakkety on 2016-09-29 (2 days ago)
nmcli-dev:
 DEVICE TYPE  STATE DBUS-PATH   
   CONNECTION   CON-UUID  CON-PATH  
 
 docker0bridgeconnected 
/org/freedesktop/NetworkManager/Devices/1  docker0  
63f0b05b-f699-4a68-81ce-f62d2c1a247d  
/org/freedesktop/NetworkManager/ActiveConnection/0 
 wlp3s0 wifi  connected 
/org/freedesktop/NetworkManager/Devices/4  HOME-1622-5  
6df3f2f0-fb86-43b5-802a-d59bc5734be3  
/org/freedesktop/NetworkManager/ActiveConnection/2 
 24:DA:9B:B9:09:0E  btdisconnected  
/org/freedesktop/NetworkManager/Devices/3  --   --  
  -- 
 lo loopback  unmanaged 
/org/freedesktop/NetworkManager/Devices/2  --   --  
  --
nmcli-nm:
 RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  WIFI  
   WWAN-HW  WWAN
 running  1.2.4connected  started  full  enabled enabled  
enabled  enabled  enabled

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


** Tags: amd64 apport-bug yakkety

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

Title:
  DNS resolver stops accepting queries

Status in network-manager package in Ubuntu:
  New

Bug description:
  After a while / after resume from suspend, the system becomes unable
  to respond to DNS queries, with the following output for example:

  $ nslookup google.com 127.0.1.1
  Server:   127.0.1.1
  Address:  127.0.1.1#53

  ** server can't find google.com: REFUSED

  
  This is on an up to date yakkety install.  Changing resolv.conf to use 
8.8.8.8, or restarting network-manager appears to fix this, at least until it 
recurs again.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: network-manager 1.2.4-0ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-17.19-generic 4.8.0-rc7
  Uname: Linux 4.8.0-17-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sat Oct  1 21:28:51 2016
  EcryptfsInUse: Yes
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2015-08-21 (407 days ago)
  InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha amd64 (20150819)
  IpRoute:
   default via 192.168.1.1 dev wlp3s0  proto static  metric 600 
   169.254.0.0/16 dev docker0  scope link  metric 1000 linkdown 
   172.17.0.0/16 dev docker0  proto kernel  scope link  src 172.17.0.1 linkdown 
   192.168.1.0/24 dev wlp3s0  proto kernel  scope link  src 192.168.1.5  metric 
600
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to yakkety on 2016-09-29 (2 days ago)
  nmcli-dev:
   DEVICE TYPE  STATE DBUS-PATH 
 CONNECTION   CON-UUID   

[Touch-packages] [Bug 1546603] [NEW] Bluetooth mouse connects but doesn't work

2016-02-17 Thread Joe Barnett
Public bug reported:

I have a bluetooth mouse that I can get to connect via the gnome
bluetooth settings panel, but even after it's connected it doesn't move
the pointer or register any clicks.

the following shows up in the journal :

$ $ journalctl -b 0 |grep bluetooth
Feb 17 07:18:22 spiny bluetoothd[1009]: Bluetooth daemon 5.36
Feb 17 07:18:22 spiny bluetoothd[1009]: Starting SDP server
Feb 17 07:18:22 spiny bluetoothd[1009]: Bluetooth management interface 1.10 
initialized
Feb 17 07:18:22 spiny bluetoothd[1009]: Failed to obtain handles for "Service 
Changed" characteristic
Feb 17 07:18:22 spiny bluetoothd[1009]: Not enough free handles to register 
service
Feb 17 07:18:22 spiny bluetoothd[1009]: Error adding Link Loss service
Feb 17 07:18:22 spiny bluetoothd[1009]: Not enough free handles to register 
service
Feb 17 07:18:22 spiny bluetoothd[1009]: Not enough free handles to register 
service
Feb 17 07:18:22 spiny bluetoothd[1009]: Not enough free handles to register 
service
Feb 17 07:18:22 spiny bluetoothd[1009]: Current Time Service could not be 
registered
Feb 17 07:18:22 spiny bluetoothd[1009]: gatt-time-server: Input/output error (5)
Feb 17 07:18:22 spiny bluetoothd[1009]: Not enough free handles to register 
service
Feb 17 07:18:22 spiny bluetoothd[1009]: Not enough free handles to register 
service
Feb 17 07:18:22 spiny bluetoothd[1009]: Sap driver initialization failed.
Feb 17 07:18:22 spiny bluetoothd[1009]: sap-server: Operation not permitted (1)
Feb 17 07:18:22 spiny NetworkManager[1062]:   Loaded device plugin: 
NMBluezManager 
(/usr/lib/x86_64-linux-gnu/NetworkManager/libnm-device-plugin-bluetooth.so)
Feb 17 07:18:24 spiny bluetoothd[1009]: Endpoint registered: sender=:1.42 
path=/MediaEndpoint/A2DPSource
Feb 17 07:18:24 spiny bluetoothd[1009]: Endpoint registered: sender=:1.42 
path=/MediaEndpoint/A2DPSink
Feb 17 07:18:42 spiny bluetoothd[1009]: Endpoint registered: sender=:1.71 
path=/MediaEndpoint/A2DPSource
Feb 17 07:18:42 spiny bluetoothd[1009]: Endpoint registered: sender=:1.71 
path=/MediaEndpoint/A2DPSink
Feb 17 07:18:42 spiny bluetoothd[1009]: RFCOMM server failed for Headset Voice 
gateway: rfcomm_bind: Address already in use (98)
Feb 17 07:18:52 spiny gnome-bluetooth-panel.desktop[2717]: ** 
(gnome-control-center.real:2717): WARNING **: Ignoring launcher gufw (missing 
desktop file)
Feb 17 07:18:52 spiny gnome-bluetooth-panel.desktop[2717]: ** 
(gnome-control-center.real:2717): WARNING **: Ignoring launcher 
landscape-client-settings (missing desktop file)
Feb 17 07:18:52 spiny gnome-bluetooth-panel.desktop[2717]: ** 
(gnome-control-center.real:2717): WARNING **: Ignoring launcher 
language-selector (missing desktop file)
Feb 17 07:18:52 spiny gnome-bluetooth-panel.desktop[2717]: ** 
(gnome-control-center.real:2717): WARNING **: Ignoring launcher 
ubuntuone-installer (missing desktop file)
Feb 17 07:19:00 spiny gnome-bluetooth-panel.desktop[2717]: 
(gnome-control-center.real:2717): GLib-CRITICAL **: g_ascii_strdown: assertion 
'str != NULL' failed
Feb 17 07:19:01 spiny bluetoothd[1009]: No cache for F2:3F:5C:A1:F9:F7
Feb 17 07:19:06 spiny bluetoothd[1009]: Unable to register GATT service with 
handle 0x000c for device F2:3F:5C:A1:F9:F7
Feb 17 07:19:06 spiny bluetoothd[1009]: Unable to register GATT service with 
handle 0x001b for device F2:3F:5C:A1:F9:F7
Feb 17 07:19:06 spiny bluetoothd[1009]: Unable to register GATT service with 
handle 0x003f for device F2:3F:5C:A1:F9:F7
Feb 17 07:19:06 spiny bluetoothd[1009]: Report Map read failed: Attribute 
requires authentication before read/write
Feb 17 07:19:06 spiny bluetoothd[1009]: Protocol Mode characteristic read 
failed: Attribute requires authentication before read/write
Feb 17 07:19:06 spiny bluetoothd[1009]: HID Information read failed: Attribute 
requires authentication before read/write
Feb 17 07:19:06 spiny bluetoothd[1009]: Read Report Reference descriptor 
failed: Attribute requires authentication before read/write
Feb 17 07:19:06 spiny bluetoothd[1009]: Read Report Reference descriptor 
failed: Attribute requires authentication before read/write
Feb 17 07:19:06 spiny bluetoothd[1009]: Read Report Reference descriptor 
failed: Attribute requires authentication before read/write
Feb 17 07:19:06 spiny bluetoothd[1009]: Read Report Reference descriptor 
failed: Attribute requires authentication before read/write
Feb 17 07:19:08 spiny gnome-bluetooth-panel.desktop[2717]: 
(gnome-control-center.real:2717): GLib-CRITICAL **: g_ascii_strdown: assertion 
'str != NULL' failed
Feb 17 07:19:08 spiny gnome-bluetooth-panel.desktop[2717]: 
(gnome-control-center.real:2717): Bluetooth-WARNING **: Setting up 
/org/bluez/hci0/dev_F2_3F_5C_A1_F9_F7 failed: 
GDBus.Error:org.bluez.Error.InProgress: In Progress
Feb 17 07:19:08 spiny gnome-bluetooth-panel.desktop[2717]: 
(gnome-control-center.real:2717): GLib-CRITICAL **: g_ascii_strdown: assertion 
'str != NULL' failed
Feb 17 07:19:08 spiny gnome-bluetooth-panel.desktop[2717]: 
(gnome-contr

[Touch-packages] [Bug 1448566] Re: Ubuntu 15.04 - Macbook Pro Early 2015 (12, 1) Bluetooth disabled

2015-11-10 Thread Joe Barnett
this is also in the bluetooth (not bluetooth-next) repo:
https://git.kernel.org/cgit/linux/kernel/git/bluetooth/bluetooth.git/commit/?id=22f8e9dbf671a2f36d90d3d8723a2a0c5227fa4b
, would it be possible to include in the wily kernel as a SAUCE patch at
this point?

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

Title:
  Ubuntu 15.04 - Macbook Pro Early 2015 (12,1) Bluetooth disabled

Status in bluez package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Fresh install of 15.04 on a Macbook Pro 12,1.

  I get no Bluetooth icon in the status bar, and in System Settings >
  Bluetooth, everything is greyed out (i.e., can't turn it on).

  
  $lsusb; dmesg | grep -i bluetooth; dmesg | grep -i firmware; rfkill list all; 
lsmod | grep bluetooth; hciconfig -a; uname -a

  Bus 002 Device 002: ID 05ac:8406 Apple, Inc.
  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 001 Device 003: ID 05ac:0273 Apple, Inc.
  Bus 001 Device 004: ID 05ac:8290 Apple, Inc.
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  [ 32.369395] usb 1-3: Product: Bluetooth USB Host Controller
  [ 32.435743] input: Broadcom Corp. Bluetooth USB Host Controller as 
/devices/pci:00/:00:14.0/usb1/1-3/1-3:1.0/0003:05AC:8290.0006/input/input7
  [ 32.490662] hid-generic 0003:05AC:8290.0006: input,hidraw5: USB HID v1.11 
Keyboard [Broadcom Corp. Bluetooth USB Host Controller] on 
usb-:00:14.0-3/input0
  [ 32.490750] input: Broadcom Corp. Bluetooth USB Host Controller as 
/devices/pci:00/:00:14.0/usb1/1-3/1-3:1.1/0003:05AC:8290.0007/input/input8
  [ 32.490995] hid-generic 0003:05AC:8290.0007: input,hidraw6: USB HID v1.11 
Mouse [Broadcom Corp. Bluetooth USB Host Controller] on 
usb-:00:14.0-3/input1
  [ 34.866186] Bluetooth: Core ver 2.20
  [ 34.866205] Bluetooth: HCI device and connection manager initialized
  [ 34.866751] Bluetooth: HCI socket layer initialized
  [ 34.866754] Bluetooth: L2CAP socket layer initialized
  [ 34.866759] Bluetooth: SCO socket layer initialized
  [ 0.158493] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
  [ 0.168342] acpi PNP0A08:00: [Firmware Info]: MMCONFIG for domain  [bus 
00-9b] only partially covers this bridge
  [ 35.003383] brcmfmac :03:00.0: Direct firmware load for 
brcm/brcmfmac43602-pcie.txt failed with error -2
  [ 35.290656] brcmf_c_preinit_dcmds: Firmware version = wl0: Mar 13 2015 
08:11:08 version 7.35.177.36 (r540934) FWID 01-e4dc15b
  0: phy0: Wireless LAN
   Soft blocked: no
   Hard blocked: no
  bluetooth 491520 1 btusb
  Linux hxn-laptop-linux 3.19.0-15-generic #15-Ubuntu SMP Thu Apr 16 23:32:37 
UTC 2015 x86_64 x86_64 x86_64 GNU/Linux

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1448566/+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 1428712] Re: Screen turns green and locks out during apt full-upgrade

2015-04-20 Thread Joe Barnett
i actually haven't seen this since ~3/31...  fwiw

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

Title:
  Screen turns green and locks out during apt full-upgrade

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  Since updating to vivid, occasionally when doing an apt full-upgrade
  the screen will turn and stay bright green.  I can see and move the
  mouse cursor but nothing else, and no system keyboard shortcuts appear
  to do anything (ctrl-alt-f1 through ctrl-alt-f7, ctl-alt-backspace,
  ctl-alt-delete, etc).  Probably an issue with a specific package
  rather than apt, but not sure how to narrow it down.

  here's the list of packages that were upgraded the last time this
  happened, form /var/log/apt/history.log:

  Start-Date: 2015-03-05  07:47:15
  Commandline: apt full-upgrade
  Install: console-setup-linux:amd64 (1.108ubuntu3, automatic)
  Upgrade: python3-apparmor:amd64 (2.9.1-0ubuntu5, 2.9.1-0ubuntu6), 
apparmor-easyprof:amd64 (2.9.1-0ubuntu5, 2.9.1-0ubuntu6), 
glib-networking-common:amd64 (2.43.1-1, 2.43.91-1), libgail18:amd64 
(2.24.26-0ubuntu2, 2.24.27-0ubuntu1), libgail18:i386 (2.24.26-0ubuntu2, 
2.24.27-0ubuntu1), libsoup2.4-1:amd64 (2.49.1-1ubuntu1, 2.49.91.1-1), 
libsoup2.4-1:i386 (2.49.1-1ubuntu1, 2.49.91.1-1), libwagon-java:amd64 
(1.0.0-2ubuntu2, 1.0.0-5), libgeis1:amd64 (2.2.16+14.04.20140303-0ubuntu1, 
2.2.16+15.04.20150304-0ubuntu1), console-setup:amd64 (1.70ubuntu11, 
1.108ubuntu3), libsoup2.4-dev:amd64 (2.49.1-1ubuntu1, 2.49.91.1-1), 
libapparmor1:amd64 (2.9.1-0ubuntu5, 2.9.1-0ubuntu6), gtk2-engines-pixbuf:amd64 
(2.24.26-0ubuntu2, 2.24.27-0ubuntu1), gtk2-engines-pixbuf:i386 
(2.24.26-0ubuntu2, 2.24.27-0ubuntu1), libglib2.0-0:amd64 (2.43.90-1, 
2.43.91-1), libglib2.0-0:i386 (2.43.90-1, 2.43.91-1), libglib2.0-dev:amd64 
(2.43.90-1, 2.43.91-1), libgtk2.0-bin:amd64 (2.24.26-0ubuntu2, 
2.24.27-0ubuntu1), libgtk2.0-com
 mon:amd64 (2.24.26-0ubuntu2, 2.24.27-0ubuntu1), gir1.2-gtk-2.0:amd64 
(2.24.26-0ubuntu2, 2.24.27-0ubuntu1), libglib2.0-data:amd64 (2.43.90-1, 
2.43.91-1), libflac8:amd64 (1.3.0-3, 1.3.1-1ubuntu1), libflac8:i386 (1.3.0-3, 
1.3.1-1ubuntu1), libsoup-gnome2.4-1:amd64 (2.49.1-1ubuntu1, 2.49.91.1-1), 
libsoup-gnome2.4-1:i386 (2.49.1-1ubuntu1, 2.49.91.1-1), libnm-util2:amd64 
(0.9.10.0-4ubuntu8, 0.9.10.0-4ubuntu9), libapparmor-perl:amd64 (2.9.1-0ubuntu5, 
2.9.1-0ubuntu6), libnm-glib-vpn1:amd64 (0.9.10.0-4ubuntu8, 0.9.10.0-4ubuntu9), 
libdee-1.0-4:amd64 (1.2.7+14.04.20140324-0ubuntu1, 
1.2.7+15.04.20150304-0ubuntu1), libgtk2.0-0:amd64 (2.24.26-0ubuntu2, 
2.24.27-0ubuntu1), libgtk2.0-0:i386 (2.24.26-0ubuntu2, 2.24.27-0ubuntu1), 
libglib2.0-0-dbg:amd64 (2.43.90-1, 2.43.91-1), gir1.2-dee-1.0:amd64 
(1.2.7+14.04.20140324-0ubuntu1, 1.2.7+15.04.20150304-0ubuntu1), 
keyboard-configuration:amd64 (1.70ubuntu11, 1.108ubuntu3), kbd:amd64 
(1.15.5-1ubuntu1, 1.15.5-1ubuntu2), libx264-142:amd64 (0.142.2431+gita5831aa
 -1ubuntu1, 0.142.2495+git6a301b6-1ubuntu1), apparmor:amd64 (2.9.1-0ubuntu5, 
2.9.1-0ubuntu6), libglib2.0-bin:amd64 (2.43.90-1, 2.43.91-1), 
python3-libapparmor:amd64 (2.9.1-0ubuntu5, 2.9.1-0ubuntu6), 
network-manager:amd64 (0.9.10.0-4ubuntu8, 0.9.10.0-4ubuntu9), 
gir1.2-networkmanager-1.0:amd64 (0.9.10.0-4ubuntu8, 0.9.10.0-4ubuntu9), 
glib-networking-services:amd64 (2.43.1-1, 2.43.91-1), libgtk2.0-dev:amd64 
(2.24.26-0ubuntu2, 2.24.27-0ubuntu1), glib-networking:amd64 (2.43.1-1, 
2.43.91-1), glib-networking:i386 (2.43.1-1, 2.43.91-1), gir1.2-soup-2.4:amd64 
(2.49.1-1ubuntu1, 2.49.91.1-1), dh-apparmor:amd64 (2.9.1-0ubuntu5, 
2.9.1-0ubuntu6), libnm-glib4:amd64 (0.9.10.0-4ubuntu8, 0.9.10.0-4ubuntu9), 
libgail-common:amd64 (2.24.26-0ubuntu2, 2.24.27-0ubuntu1), libgail-common:i386 
(2.24.26-0ubuntu2, 2.24.27-0ubuntu1)

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: apt 1.0.9.3ubuntu1
  ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0
  Uname: Linux 3.19.0-7-generic x86_64
  NonfreeKernelModules: nvidia wl
  ApportVersion: 2.16.2-0ubuntu1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Mar  5 08:00:19 2015
  InstallationDate: Installed on 2014-02-24 (373 days ago)
  InstallationMedia: Ubuntu-GNOME 14.04 "Trusty Tahr" - Alpha amd64 (20140218)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: apt
  UpgradeStatus: Upgraded to vivid on 2015-02-04 (28 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1428712/+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 1428712] Re: Screen turns green and locks out during apt full-upgrade

2015-03-31 Thread Joe Barnett
sorry, it happens while upgrading non-systemd _packages_, still on
systemd systems.

still unclear to me which packages trigger it.  at one point systemd
appeared to be one that did, but apparently not always the case

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

Title:
  Screen turns green and locks out during apt full-upgrade

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  Since updating to vivid, occasionally when doing an apt full-upgrade
  the screen will turn and stay bright green.  I can see and move the
  mouse cursor but nothing else, and no system keyboard shortcuts appear
  to do anything (ctrl-alt-f1 through ctrl-alt-f7, ctl-alt-backspace,
  ctl-alt-delete, etc).  Probably an issue with a specific package
  rather than apt, but not sure how to narrow it down.

  here's the list of packages that were upgraded the last time this
  happened, form /var/log/apt/history.log:

  Start-Date: 2015-03-05  07:47:15
  Commandline: apt full-upgrade
  Install: console-setup-linux:amd64 (1.108ubuntu3, automatic)
  Upgrade: python3-apparmor:amd64 (2.9.1-0ubuntu5, 2.9.1-0ubuntu6), 
apparmor-easyprof:amd64 (2.9.1-0ubuntu5, 2.9.1-0ubuntu6), 
glib-networking-common:amd64 (2.43.1-1, 2.43.91-1), libgail18:amd64 
(2.24.26-0ubuntu2, 2.24.27-0ubuntu1), libgail18:i386 (2.24.26-0ubuntu2, 
2.24.27-0ubuntu1), libsoup2.4-1:amd64 (2.49.1-1ubuntu1, 2.49.91.1-1), 
libsoup2.4-1:i386 (2.49.1-1ubuntu1, 2.49.91.1-1), libwagon-java:amd64 
(1.0.0-2ubuntu2, 1.0.0-5), libgeis1:amd64 (2.2.16+14.04.20140303-0ubuntu1, 
2.2.16+15.04.20150304-0ubuntu1), console-setup:amd64 (1.70ubuntu11, 
1.108ubuntu3), libsoup2.4-dev:amd64 (2.49.1-1ubuntu1, 2.49.91.1-1), 
libapparmor1:amd64 (2.9.1-0ubuntu5, 2.9.1-0ubuntu6), gtk2-engines-pixbuf:amd64 
(2.24.26-0ubuntu2, 2.24.27-0ubuntu1), gtk2-engines-pixbuf:i386 
(2.24.26-0ubuntu2, 2.24.27-0ubuntu1), libglib2.0-0:amd64 (2.43.90-1, 
2.43.91-1), libglib2.0-0:i386 (2.43.90-1, 2.43.91-1), libglib2.0-dev:amd64 
(2.43.90-1, 2.43.91-1), libgtk2.0-bin:amd64 (2.24.26-0ubuntu2, 
2.24.27-0ubuntu1), libgtk2.0-com
 mon:amd64 (2.24.26-0ubuntu2, 2.24.27-0ubuntu1), gir1.2-gtk-2.0:amd64 
(2.24.26-0ubuntu2, 2.24.27-0ubuntu1), libglib2.0-data:amd64 (2.43.90-1, 
2.43.91-1), libflac8:amd64 (1.3.0-3, 1.3.1-1ubuntu1), libflac8:i386 (1.3.0-3, 
1.3.1-1ubuntu1), libsoup-gnome2.4-1:amd64 (2.49.1-1ubuntu1, 2.49.91.1-1), 
libsoup-gnome2.4-1:i386 (2.49.1-1ubuntu1, 2.49.91.1-1), libnm-util2:amd64 
(0.9.10.0-4ubuntu8, 0.9.10.0-4ubuntu9), libapparmor-perl:amd64 (2.9.1-0ubuntu5, 
2.9.1-0ubuntu6), libnm-glib-vpn1:amd64 (0.9.10.0-4ubuntu8, 0.9.10.0-4ubuntu9), 
libdee-1.0-4:amd64 (1.2.7+14.04.20140324-0ubuntu1, 
1.2.7+15.04.20150304-0ubuntu1), libgtk2.0-0:amd64 (2.24.26-0ubuntu2, 
2.24.27-0ubuntu1), libgtk2.0-0:i386 (2.24.26-0ubuntu2, 2.24.27-0ubuntu1), 
libglib2.0-0-dbg:amd64 (2.43.90-1, 2.43.91-1), gir1.2-dee-1.0:amd64 
(1.2.7+14.04.20140324-0ubuntu1, 1.2.7+15.04.20150304-0ubuntu1), 
keyboard-configuration:amd64 (1.70ubuntu11, 1.108ubuntu3), kbd:amd64 
(1.15.5-1ubuntu1, 1.15.5-1ubuntu2), libx264-142:amd64 (0.142.2431+gita5831aa
 -1ubuntu1, 0.142.2495+git6a301b6-1ubuntu1), apparmor:amd64 (2.9.1-0ubuntu5, 
2.9.1-0ubuntu6), libglib2.0-bin:amd64 (2.43.90-1, 2.43.91-1), 
python3-libapparmor:amd64 (2.9.1-0ubuntu5, 2.9.1-0ubuntu6), 
network-manager:amd64 (0.9.10.0-4ubuntu8, 0.9.10.0-4ubuntu9), 
gir1.2-networkmanager-1.0:amd64 (0.9.10.0-4ubuntu8, 0.9.10.0-4ubuntu9), 
glib-networking-services:amd64 (2.43.1-1, 2.43.91-1), libgtk2.0-dev:amd64 
(2.24.26-0ubuntu2, 2.24.27-0ubuntu1), glib-networking:amd64 (2.43.1-1, 
2.43.91-1), glib-networking:i386 (2.43.1-1, 2.43.91-1), gir1.2-soup-2.4:amd64 
(2.49.1-1ubuntu1, 2.49.91.1-1), dh-apparmor:amd64 (2.9.1-0ubuntu5, 
2.9.1-0ubuntu6), libnm-glib4:amd64 (0.9.10.0-4ubuntu8, 0.9.10.0-4ubuntu9), 
libgail-common:amd64 (2.24.26-0ubuntu2, 2.24.27-0ubuntu1), libgail-common:i386 
(2.24.26-0ubuntu2, 2.24.27-0ubuntu1)

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: apt 1.0.9.3ubuntu1
  ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0
  Uname: Linux 3.19.0-7-generic x86_64
  NonfreeKernelModules: nvidia wl
  ApportVersion: 2.16.2-0ubuntu1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Mar  5 08:00:19 2015
  InstallationDate: Installed on 2014-02-24 (373 days ago)
  InstallationMedia: Ubuntu-GNOME 14.04 "Trusty Tahr" - Alpha amd64 (20140218)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: apt
  UpgradeStatus: Upgraded to vivid on 2015-02-04 (28 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1428712/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://hel

[Touch-packages] [Bug 1431200] Re: daemon-reload runs alsa-restore.service and others

2015-03-31 Thread Joe Barnett
I still see the green screen problem (marked as dup of this bug).
although it happens on non-systemd upgrades...

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

Title:
  daemon-reload runs alsa-restore.service and others

Status in systemd package in Ubuntu:
  Incomplete
Status in systemd package in Debian:
  New

Bug description:
  When systemd is reloaded (manually, upgrades), the volume is reset,
  likely using alsa-restore.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1431200/+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 1430903] Re: Can't get plantronics headset buttons to work

2015-03-30 Thread Joe Barnett
** Changed in: systemd (Ubuntu)
   Status: Incomplete => New

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

Title:
  Can't get plantronics headset buttons to work

Status in systemd package in Ubuntu:
  New

Bug description:
  Instructions for ubuntu 13.10 in http://www.helplinux.ru/wiki/en:kb
  :ubuntu-plantronics worked great in utopic, but has stopped working
  since upgrading to vivid.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: udev 219-4ubuntu3
  ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0
  Uname: Linux 3.19.0-7-generic x86_64
  NonfreeKernelModules: nvidia wl
  ApportVersion: 2.16.2-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME
  CustomUdevRuleFiles: 59-plantronics.rules
  Date: Wed Mar 11 09:33:40 2015
  InstallationDate: Installed on 2014-02-24 (379 days ago)
  InstallationMedia: Ubuntu-GNOME 14.04 "Trusty Tahr" - Alpha amd64 (20140218)
  MachineType: Apple Inc. MacBookPro11,3
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-7-generic.efi.signed 
root=UUID=135fd833-3282-4f3b-8802-0a27ec2765b9 ro quiet splash vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: Upgraded to vivid on 2015-02-04 (34 days ago)
  dmi.bios.date: 10/18/2013
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBP112.88Z.0138.B02.1310181745
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-2BD1B31983FE1663
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookPro11,3
  dmi.chassis.type: 10
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-2BD1B31983FE1663
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMBP112.88Z.0138.B02.1310181745:bd10/18/2013:svnAppleInc.:pnMacBookPro11,3:pvr1.0:rvnAppleInc.:rnMac-2BD1B31983FE1663:rvrMacBookPro11,3:cvnAppleInc.:ct10:cvrMac-2BD1B31983FE1663:
  dmi.product.name: MacBookPro11,3
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1430903/+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 1430903] Re: Can't get plantronics headset buttons to work

2015-03-30 Thread Joe Barnett
Attached after plugging in headset.

$ lsusb |grep -i plantr
Bus 001 Device 027: ID 047f:c011 Plantronics, Inc. 


** Attachment added: "udev.txt"
   
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1430903/+attachment/4361019/+files/udev.txt

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

Title:
  Can't get plantronics headset buttons to work

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  Instructions for ubuntu 13.10 in http://www.helplinux.ru/wiki/en:kb
  :ubuntu-plantronics worked great in utopic, but has stopped working
  since upgrading to vivid.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: udev 219-4ubuntu3
  ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0
  Uname: Linux 3.19.0-7-generic x86_64
  NonfreeKernelModules: nvidia wl
  ApportVersion: 2.16.2-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME
  CustomUdevRuleFiles: 59-plantronics.rules
  Date: Wed Mar 11 09:33:40 2015
  InstallationDate: Installed on 2014-02-24 (379 days ago)
  InstallationMedia: Ubuntu-GNOME 14.04 "Trusty Tahr" - Alpha amd64 (20140218)
  MachineType: Apple Inc. MacBookPro11,3
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-7-generic.efi.signed 
root=UUID=135fd833-3282-4f3b-8802-0a27ec2765b9 ro quiet splash vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: Upgraded to vivid on 2015-02-04 (34 days ago)
  dmi.bios.date: 10/18/2013
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBP112.88Z.0138.B02.1310181745
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-2BD1B31983FE1663
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookPro11,3
  dmi.chassis.type: 10
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-2BD1B31983FE1663
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMBP112.88Z.0138.B02.1310181745:bd10/18/2013:svnAppleInc.:pnMacBookPro11,3:pvr1.0:rvnAppleInc.:rnMac-2BD1B31983FE1663:rvrMacBookPro11,3:cvnAppleInc.:ct10:cvrMac-2BD1B31983FE1663:
  dmi.product.name: MacBookPro11,3
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1430903/+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 1428712] Re: Screen turns green and locks out during apt full-upgrade

2015-03-13 Thread Joe Barnett
** Also affects: systemd (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  Screen turns green and locks out during apt full-upgrade

Status in apt package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  New

Bug description:
  Since updating to vivid, occasionally when doing an apt full-upgrade
  the screen will turn and stay bright green.  I can see and move the
  mouse cursor but nothing else, and no system keyboard shortcuts appear
  to do anything (ctrl-alt-f1 through ctrl-alt-f7, ctl-alt-backspace,
  ctl-alt-delete, etc).  Probably an issue with a specific package
  rather than apt, but not sure how to narrow it down.

  here's the list of packages that were upgraded the last time this
  happened, form /var/log/apt/history.log:

  Start-Date: 2015-03-05  07:47:15
  Commandline: apt full-upgrade
  Install: console-setup-linux:amd64 (1.108ubuntu3, automatic)
  Upgrade: python3-apparmor:amd64 (2.9.1-0ubuntu5, 2.9.1-0ubuntu6), 
apparmor-easyprof:amd64 (2.9.1-0ubuntu5, 2.9.1-0ubuntu6), 
glib-networking-common:amd64 (2.43.1-1, 2.43.91-1), libgail18:amd64 
(2.24.26-0ubuntu2, 2.24.27-0ubuntu1), libgail18:i386 (2.24.26-0ubuntu2, 
2.24.27-0ubuntu1), libsoup2.4-1:amd64 (2.49.1-1ubuntu1, 2.49.91.1-1), 
libsoup2.4-1:i386 (2.49.1-1ubuntu1, 2.49.91.1-1), libwagon-java:amd64 
(1.0.0-2ubuntu2, 1.0.0-5), libgeis1:amd64 (2.2.16+14.04.20140303-0ubuntu1, 
2.2.16+15.04.20150304-0ubuntu1), console-setup:amd64 (1.70ubuntu11, 
1.108ubuntu3), libsoup2.4-dev:amd64 (2.49.1-1ubuntu1, 2.49.91.1-1), 
libapparmor1:amd64 (2.9.1-0ubuntu5, 2.9.1-0ubuntu6), gtk2-engines-pixbuf:amd64 
(2.24.26-0ubuntu2, 2.24.27-0ubuntu1), gtk2-engines-pixbuf:i386 
(2.24.26-0ubuntu2, 2.24.27-0ubuntu1), libglib2.0-0:amd64 (2.43.90-1, 
2.43.91-1), libglib2.0-0:i386 (2.43.90-1, 2.43.91-1), libglib2.0-dev:amd64 
(2.43.90-1, 2.43.91-1), libgtk2.0-bin:amd64 (2.24.26-0ubuntu2, 
2.24.27-0ubuntu1), libgtk2.0-com
 mon:amd64 (2.24.26-0ubuntu2, 2.24.27-0ubuntu1), gir1.2-gtk-2.0:amd64 
(2.24.26-0ubuntu2, 2.24.27-0ubuntu1), libglib2.0-data:amd64 (2.43.90-1, 
2.43.91-1), libflac8:amd64 (1.3.0-3, 1.3.1-1ubuntu1), libflac8:i386 (1.3.0-3, 
1.3.1-1ubuntu1), libsoup-gnome2.4-1:amd64 (2.49.1-1ubuntu1, 2.49.91.1-1), 
libsoup-gnome2.4-1:i386 (2.49.1-1ubuntu1, 2.49.91.1-1), libnm-util2:amd64 
(0.9.10.0-4ubuntu8, 0.9.10.0-4ubuntu9), libapparmor-perl:amd64 (2.9.1-0ubuntu5, 
2.9.1-0ubuntu6), libnm-glib-vpn1:amd64 (0.9.10.0-4ubuntu8, 0.9.10.0-4ubuntu9), 
libdee-1.0-4:amd64 (1.2.7+14.04.20140324-0ubuntu1, 
1.2.7+15.04.20150304-0ubuntu1), libgtk2.0-0:amd64 (2.24.26-0ubuntu2, 
2.24.27-0ubuntu1), libgtk2.0-0:i386 (2.24.26-0ubuntu2, 2.24.27-0ubuntu1), 
libglib2.0-0-dbg:amd64 (2.43.90-1, 2.43.91-1), gir1.2-dee-1.0:amd64 
(1.2.7+14.04.20140324-0ubuntu1, 1.2.7+15.04.20150304-0ubuntu1), 
keyboard-configuration:amd64 (1.70ubuntu11, 1.108ubuntu3), kbd:amd64 
(1.15.5-1ubuntu1, 1.15.5-1ubuntu2), libx264-142:amd64 (0.142.2431+gita5831aa
 -1ubuntu1, 0.142.2495+git6a301b6-1ubuntu1), apparmor:amd64 (2.9.1-0ubuntu5, 
2.9.1-0ubuntu6), libglib2.0-bin:amd64 (2.43.90-1, 2.43.91-1), 
python3-libapparmor:amd64 (2.9.1-0ubuntu5, 2.9.1-0ubuntu6), 
network-manager:amd64 (0.9.10.0-4ubuntu8, 0.9.10.0-4ubuntu9), 
gir1.2-networkmanager-1.0:amd64 (0.9.10.0-4ubuntu8, 0.9.10.0-4ubuntu9), 
glib-networking-services:amd64 (2.43.1-1, 2.43.91-1), libgtk2.0-dev:amd64 
(2.24.26-0ubuntu2, 2.24.27-0ubuntu1), glib-networking:amd64 (2.43.1-1, 
2.43.91-1), glib-networking:i386 (2.43.1-1, 2.43.91-1), gir1.2-soup-2.4:amd64 
(2.49.1-1ubuntu1, 2.49.91.1-1), dh-apparmor:amd64 (2.9.1-0ubuntu5, 
2.9.1-0ubuntu6), libnm-glib4:amd64 (0.9.10.0-4ubuntu8, 0.9.10.0-4ubuntu9), 
libgail-common:amd64 (2.24.26-0ubuntu2, 2.24.27-0ubuntu1), libgail-common:i386 
(2.24.26-0ubuntu2, 2.24.27-0ubuntu1)

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: apt 1.0.9.3ubuntu1
  ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0
  Uname: Linux 3.19.0-7-generic x86_64
  NonfreeKernelModules: nvidia wl
  ApportVersion: 2.16.2-0ubuntu1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Mar  5 08:00:19 2015
  InstallationDate: Installed on 2014-02-24 (373 days ago)
  InstallationMedia: Ubuntu-GNOME 14.04 "Trusty Tahr" - Alpha amd64 (20140218)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: apt
  UpgradeStatus: Upgraded to vivid on 2015-02-04 (28 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1428712/+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 1428712] Re: Screen turns green and locks out during apt full-upgrade

2015-03-12 Thread Joe Barnett
and again today, though this time it appeared to happen as apt was
outputting :

Setting up systemd (219-4ubuntu5) ...

(though hard to tell if i blinked and missed more...)
following log lines are:

Setting up systemd (219-4ubuntu5) ...
Setting up libsasl2-modules-db:amd64 (2.1.26.dfsg1-13) ...
Setting up libsasl2-modules-db:i386 (2.1.26.dfsg1-13) ...
Setting up libsasl2-2:amd64 (2.1.26.dfsg1-13) ...
Setting up libsasl2-2:i386 (2.1.26.dfsg1-13) ...
Setting up libsasl2-dev (2.1.26.dfsg1-13) ...
Setting up chromium-codecs-ffmpeg-extra (41.0.2272.76-0ubuntu1.1134) ...
Setting up google-chrome-stable (41.0.2272.89-1) ...


and I was able to ssh in and restart gnome-shell in order to get the X session 
restored


Start-Date: 2015-03-11  12:26:06
Commandline: apt full-upgrade
Install: linux-image-3.19.0-8-generic:amd64 (3.19.0-8.8, automatic), 
linux-headers-3.19.0-8-generic:amd64 (3.19.0-8.8, automatic), 
linux-signed-image-3.19.0-8-generic:amd64 (3.19.0-8.8, automatic), 
linux-image-extra-3.19.0-8-generic:amd64 (3.19.0-8.8, automatic), 
linux-headers-3.19.0-8:amd64 (3.19.0-8.8, automatic)
Upgrade: libmono-i18n-west2.0-cil:amd64 (3.2.8+dfsg-4ubuntu2, 
3.2.8+dfsg-4ubuntu3), libreoffice-pdfimport:amd64 (4.4.0-1ubuntu1, 
4.4.1-0ubuntu1), libreoffice-base-core:amd64 (4.4.0-1ubuntu1, 4.4.1-0ubuntu1), 
gir1.2-evince-3.0:amd64 (3.14.1-0ubuntu5, 3.14.2-0ubuntu1), 
libsasl2-modules-db:amd64 (2.1.26.dfsg1-12, 2.1.26.dfsg1-13), 
libsasl2-modules-db:i386 (2.1.26.dfsg1-12, 2.1.26.dfsg1-13), 
linux-headers-generic:amd64 (3.19.0.7.6, 3.19.0.8.7), libpython2.7-stdlib:amd64 
(2.7.9-1ubuntu2, 2.7.9-2ubuntu1), gnome-session-common:amd64 (3.14.0-2ubuntu3, 
3.14.0-2ubuntu4~vivid1), ure:amd64 (4.4.0-1ubuntu1, 4.4.1-0ubuntu1), 
zeitgeist-core:amd64 (0.9.14-2.2ubuntu2, 0.9.14-2.2ubuntu3), evince:amd64 
(3.14.1-0ubuntu5, 3.14.2-0ubuntu1), gnome-session-bin:amd64 (3.14.0-2ubuntu3, 
3.14.0-2ubuntu4~vivid1), libreoffice-writer:amd64 (4.4.0-1ubuntu1, 
4.4.1-0ubuntu1), libmono-security2.0-cil:amd64 (3.2.8+dfsg-4ubuntu2, 
3.2.8+dfsg-4ubuntu3), lib32gcc1:amd64 (5-20150307-1ubuntu3, 
5-20150309-1ubuntu1), mono-gac:
 amd64 (3.2.8+dfsg-4ubuntu2, 3.2.8+dfsg-4ubuntu3), cgmanager:amd64 (0.36-2, 
0.36-2ubuntu1), google-chrome-stable:amd64 (41.0.2272.76-1, 41.0.2272.89-1), 
mono-runtime-common:amd64 (3.2.8+dfsg-4ubuntu2, 3.2.8+dfsg-4ubuntu3), 
libreoffice-impress:amd64 (4.4.0-1ubuntu1, 4.4.1-0ubuntu1), uno-libs3:amd64 
(4.4.0-1ubuntu1, 4.4.1-0ubuntu1), libreoffice-avmedia-backend-gstreamer:amd64 
(4.4.0-1ubuntu1, 4.4.1-0ubuntu1), libarchive13:amd64 (3.1.2-10, 3.1.2-11), 
libmono-i18n-west4.0-cil:amd64 (3.2.8+dfsg-4ubuntu2, 3.2.8+dfsg-4ubuntu3), 
libmono-data-tds4.0-cil:amd64 (3.2.8+dfsg-4ubuntu2, 3.2.8+dfsg-4ubuntu3), 
mono-runtime-sgen:amd64 (3.2.8+dfsg-4ubuntu2, 3.2.8+dfsg-4ubuntu3), 
gcc-5-base:amd64 (5-20150307-1ubuntu3, 5-20150309-1ubuntu1), gcc-5-base:i386 
(5-20150307-1ubuntu3, 5-20150309-1ubuntu1), console-setup:amd64 (1.108ubuntu3, 
1.108ubuntu4), console-setup-linux:amd64 (1.108ubuntu3, 1.108ubuntu4), 
libmono-system-core4.0-cil:amd64 (3.2.8+dfsg-4ubuntu2, 3.2.8+dfsg-4ubuntu3), 
libreoffice-draw:amd64 (4
 .4.0-1ubuntu1, 4.4.1-0ubuntu1), libzeitgeist-2.0-dev:amd64 (0.9.14-2.2ubuntu2, 
0.9.14-2.2ubuntu3), fonts-opensymbol:amd64 (102.6+LibO4.4.0-1ubuntu1, 
102.6+LibO4.4.1-0ubuntu1), gnome-session:amd64 (3.14.0-2ubuntu3, 
3.14.0-2ubuntu4~vivid1), numix-gtk-theme:amd64 (1.9.4-0ubuntu1, 
1.9.4-0ubuntu2), libreoffice-core:amd64 (4.4.0-1ubuntu1, 4.4.1-0ubuntu1), 
libgudev-1.0-0:amd64 (219-4ubuntu3, 219-4ubuntu5), libgudev-1.0-0:i386 
(219-4ubuntu3, 219-4ubuntu5), libreoffice-gnome:amd64 (4.4.0-1ubuntu1, 
4.4.1-0ubuntu1), ubuntu-release-upgrader-gtk:amd64 (15.04.10, 15.04.11), 
libcgmanager0:amd64 (0.36-2, 0.36-2ubuntu1), libgcc1:amd64 
(5-20150307-1ubuntu3, 5-20150309-1ubuntu1), libgcc1:i386 (5-20150307-1ubuntu3, 
5-20150309-1ubuntu1), libmono-security4.0-cil:amd64 (3.2.8+dfsg-4ubuntu2, 
3.2.8+dfsg-4ubuntu3), chromium-codecs-ffmpeg-extra:amd64 
(40.0.2214.111-0ubuntu1.1121, 41.0.2272.76-0ubuntu1.1134), 
libmono-corlib2.0-cil:amd64 (3.2.8+dfsg-4ubuntu2, 3.2.8+dfsg-4ubuntu3), 
libpam-systemd:amd64 (219-4ubu
 ntu3, 219-4ubuntu5), python2.7:amd64 (2.7.9-1ubuntu2, 2.7.9-2ubuntu1), 
evince-common:amd64 (3.14.1-0ubuntu5, 3.14.2-0ubuntu1), 
libmono-corlib4.5-cil:amd64 (3.2.8+dfsg-4ubuntu2, 3.2.8+dfsg-4ubuntu3), 
ubuntu-gnome-default-settings:amd64 (15.04.3, 15.04.5), udev:amd64 
(219-4ubuntu3, 219-4ubuntu5), libsasl2-dev:amd64 (2.1.26.dfsg1-12, 
2.1.26.dfsg1-13), zeitgeist-datahub:amd64 (0.9.14-2.2ubuntu2, 
0.9.14-2.2ubuntu3), libmono-system-drawing4.0-cil:amd64 (3.2.8+dfsg-4ubuntu2, 
3.2.8+dfsg-4ubuntu3), plymouth-theme-ubuntu-gnome-logo:amd64 (15.04.3, 
15.04.5), libunity-control-center1:amd64 (15.04.0+15.04.20150203.2-0ubuntu1, 
15.04.0+15.04.20150310-0ubuntu1), gir1.2-gudev-1.0:amd64 (219-4ubuntu3, 
219-4ubuntu5), mono-runtime:amd64 (3.2.8+dfsg-4ubuntu2, 3.2.8+dfsg-4ubuntu3), 
libmono-i18n4.0-cil:amd64 (3.2.8+dfsg-4ubuntu2, 3.2.8+dfsg-4ubuntu3), 
libu

[Touch-packages] [Bug 1430903] [NEW] Can't get plantronics headset buttons to work

2015-03-11 Thread Joe Barnett
Public bug reported:

Instructions for ubuntu 13.10 in http://www.helplinux.ru/wiki/en:kb
:ubuntu-plantronics worked great in utopic, but has stopped working
since upgrading to vivid.

ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: udev 219-4ubuntu3
ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0
Uname: Linux 3.19.0-7-generic x86_64
NonfreeKernelModules: nvidia wl
ApportVersion: 2.16.2-0ubuntu2
Architecture: amd64
CurrentDesktop: GNOME
CustomUdevRuleFiles: 59-plantronics.rules
Date: Wed Mar 11 09:33:40 2015
InstallationDate: Installed on 2014-02-24 (379 days ago)
InstallationMedia: Ubuntu-GNOME 14.04 "Trusty Tahr" - Alpha amd64 (20140218)
MachineType: Apple Inc. MacBookPro11,3
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-7-generic.efi.signed 
root=UUID=135fd833-3282-4f3b-8802-0a27ec2765b9 ro quiet splash vt.handoff=7
SourcePackage: systemd
UpgradeStatus: Upgraded to vivid on 2015-02-04 (34 days ago)
dmi.bios.date: 10/18/2013
dmi.bios.vendor: Apple Inc.
dmi.bios.version: MBP112.88Z.0138.B02.1310181745
dmi.board.asset.tag: Base Board Asset Tag#
dmi.board.name: Mac-2BD1B31983FE1663
dmi.board.vendor: Apple Inc.
dmi.board.version: MacBookPro11,3
dmi.chassis.type: 10
dmi.chassis.vendor: Apple Inc.
dmi.chassis.version: Mac-2BD1B31983FE1663
dmi.modalias: 
dmi:bvnAppleInc.:bvrMBP112.88Z.0138.B02.1310181745:bd10/18/2013:svnAppleInc.:pnMacBookPro11,3:pvr1.0:rvnAppleInc.:rnMac-2BD1B31983FE1663:rvrMacBookPro11,3:cvnAppleInc.:ct10:cvrMac-2BD1B31983FE1663:
dmi.product.name: MacBookPro11,3
dmi.product.version: 1.0
dmi.sys.vendor: Apple Inc.

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


** Tags: amd64 apport-bug vivid

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

Title:
  Can't get plantronics headset buttons to work

Status in systemd package in Ubuntu:
  New

Bug description:
  Instructions for ubuntu 13.10 in http://www.helplinux.ru/wiki/en:kb
  :ubuntu-plantronics worked great in utopic, but has stopped working
  since upgrading to vivid.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: udev 219-4ubuntu3
  ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0
  Uname: Linux 3.19.0-7-generic x86_64
  NonfreeKernelModules: nvidia wl
  ApportVersion: 2.16.2-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME
  CustomUdevRuleFiles: 59-plantronics.rules
  Date: Wed Mar 11 09:33:40 2015
  InstallationDate: Installed on 2014-02-24 (379 days ago)
  InstallationMedia: Ubuntu-GNOME 14.04 "Trusty Tahr" - Alpha amd64 (20140218)
  MachineType: Apple Inc. MacBookPro11,3
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-7-generic.efi.signed 
root=UUID=135fd833-3282-4f3b-8802-0a27ec2765b9 ro quiet splash vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: Upgraded to vivid on 2015-02-04 (34 days ago)
  dmi.bios.date: 10/18/2013
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBP112.88Z.0138.B02.1310181745
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-2BD1B31983FE1663
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookPro11,3
  dmi.chassis.type: 10
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-2BD1B31983FE1663
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMBP112.88Z.0138.B02.1310181745:bd10/18/2013:svnAppleInc.:pnMacBookPro11,3:pvr1.0:rvnAppleInc.:rnMac-2BD1B31983FE1663:rvrMacBookPro11,3:cvnAppleInc.:ct10:cvrMac-2BD1B31983FE1663:
  dmi.product.name: MacBookPro11,3
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1430903/+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 1428712] Re: Screen turns green and locks out during apt full-upgrade

2015-03-06 Thread Joe Barnett
once again today:

Start-Date: 2015-03-06  07:52:13
Commandline: apt full-upgrade
Install: libgnome-bluetooth13:amd64 (3.12.0-0ubuntu1, automatic)
Upgrade: initscripts:amd64 (2.88dsf-53.2ubuntu9, 2.88dsf-53.2ubuntu10), 
gir1.2-udisks-2.0:amd64 (2.1.4-1git3, 2.1.5-1), gnome-shell:amd64 
(3.14.3-0ubuntu2, 3.14.3-0ubuntu3), libgpg-error-dev:amd64 (1.17-3, 
1.17-3ubuntu1), libasan1:amd64 (4.9.2-10ubuntu7, 4.9.2-10ubuntu8), 
libquadmath0:amd64 (4.9.2-10ubuntu7, 4.9.2-10ubuntu8), virtualbox:amd64 
(4.3.22-dfsg-1, 4.3.24-dfsg-1), lib32stdc++6:amd64 (4.9.2-10ubuntu7, 
4.9.2-10ubuntu8), libubsan0:amd64 (4.9.2-10ubuntu7, 4.9.2-10ubuntu8), 
libbonoboui2-0:amd64 (2.24.5-0ubuntu3, 2.24.5-0ubuntu4), libcmis-0.5-5:amd64 
(0.5.0-1, 0.5.0-1ubuntu1), cpp-4.9:amd64 (4.9.2-10ubuntu7, 4.9.2-10ubuntu8), 
libstdc++-4.9-dev:amd64 (4.9.2-10ubuntu7, 4.9.2-10ubuntu8), libgomp1:amd64 
(4.9.2-10ubuntu7, 4.9.2-10ubuntu8), libvpx-dev:amd64 (1.3.0-3, 1.3.0-3ubuntu1), 
libtsan0:amd64 (4.9.2-10ubuntu7, 4.9.2-10ubuntu8), gnome-backgrounds:amd64 
(3.15.2-0ubuntu1, 3.15.91-0ubuntu1), libcilkrts5:amd64 (4.9.2-10ubuntu7, 
4.9.2-10ubuntu8), udisks2:amd64 (2.1.4-1git3, 2.1.5-1), l
 ibtag1c2a:amd64 (1.9.1-2.1build1, 1.9.1-2.1ubuntu1), libtag1c2a:i386 
(1.9.1-2.1build1, 1.9.1-2.1ubuntu1), libgudev-1.0-0:amd64 (219-4ubuntu1, 
219-4ubuntu3), libgudev-1.0-0:i386 (219-4ubuntu1, 219-4ubuntu3), 
libpam-systemd:amd64 (219-4ubuntu1, 219-4ubuntu3), 
gnome-control-center-shared-data:amd64 (3.14.2-2ubuntu2, 3.14.2-2ubuntu3), 
gnome-shell-common:amd64 (3.14.3-0ubuntu2, 3.14.3-0ubuntu3), libvpx1:amd64 
(1.3.0-3, 1.3.0-3ubuntu1), libvpx1:i386 (1.3.0-3, 1.3.0-3ubuntu1), 
libobjc4:amd64 (4.9.2-10ubuntu7, 4.9.2-10ubuntu8), gnome-control-center:amd64 
(3.14.2-2ubuntu2, 3.14.2-2ubuntu3), libbluetooth3:amd64 (4.101-0ubuntu22, 
5.23-1ubuntu1~mtrudel1), bluez-cups:amd64 (4.101-0ubuntu22, 
5.23-1ubuntu1~mtrudel1), udev:amd64 (219-4ubuntu1, 219-4ubuntu3), 
libgnome-control-center1:amd64 (3.14.2-2ubuntu2, 3.14.2-2ubuntu3), 
libpst4:amd64 (0.6.59-1build1, 0.6.59-1ubuntu1), libatomic1:amd64 
(4.9.2-10ubuntu7, 4.9.2-10ubuntu8), virtualbox-dkms:amd64 (4.3.22-dfsg-1, 
4.3.24-dfsg-1), baobab:amd64 (3.14.1-
 1ubuntu1~vivid2, 3.14.1-1ubuntu1~vivid3), gir1.2-gudev-1.0:amd64 
(219-4ubuntu1, 219-4ubuntu3), libgtksourceview-3.0-1:amd64 (3.14.1-1, 
3.14.3-1), g++-4.9:amd64 (4.9.2-10ubuntu7, 4.9.2-10ubuntu8), 
gnome-keyring:amd64 (3.14.0-1ubuntu2, 3.15.90-0ubuntu1), libbluetooth-dev:amd64 
(4.101-0ubuntu22, 5.23-1ubuntu1~mtrudel1), libudev1:amd64 (219-4ubuntu1, 
219-4ubuntu3), libudev1:i386 (219-4ubuntu1, 219-4ubuntu3), 
virtualbox-guest-additions-iso:amd64 (4.3.22-1, 4.3.24-1), virtualbox-qt:amd64 
(4.3.22-dfsg-1, 4.3.24-dfsg-1), gir1.2-gtksource-3.0:amd64 (3.14.1-1, 
3.14.3-1), libmessaging-menu0:amd64 (13.10.1+15.04.20150219-0ubuntu1, 
13.10.1+15.04.20150304-0ubuntu1), libbonoboui2-common:amd64 (2.24.5-0ubuntu3, 
2.24.5-0ubuntu4), bluez:amd64 (4.101-0ubuntu22, 5.23-1ubuntu1~mtrudel1), 
libtag1-vanilla:amd64 (1.9.1-2.1build1, 1.9.1-2.1ubuntu1), libtag1-vanilla:i386 
(1.9.1-2.1build1, 1.9.1-2.1ubuntu1), systemd-sysv:amd64 (219-4ubuntu1, 
219-4ubuntu3), gcc-4.9:amd64 (4.9.2-10ubuntu7, 4.9.2-10ubuntu8), sys
 v-rc:amd64 (2.88dsf-53.2ubuntu9, 2.88dsf-53.2ubuntu10), systemd:amd64 
(219-4ubuntu1, 219-4ubuntu3), libpam-gnome-keyring:amd64 (3.14.0-1ubuntu2, 
3.15.90-0ubuntu1), libgfortran3:amd64 (4.9.2-10ubuntu7, 4.9.2-10ubuntu8), 
libp11-kit-gnome-keyring:amd64 (3.14.0-1ubuntu2, 3.15.90-0ubuntu1), 
libgcc-4.9-dev:amd64 (4.9.2-10ubuntu7, 4.9.2-10ubuntu8), sysvinit-utils:amd64 
(2.88dsf-53.2ubuntu9, 2.88dsf-53.2ubuntu10), libgpg-error0:amd64 (1.17-3, 
1.17-3ubuntu1), libgpg-error0:i386 (1.17-3, 1.17-3ubuntu1), 
gnome-bluetooth:amd64 (3.8.2.1-0ubuntu11, 3.12.0-0ubuntu1), 
gir1.2-gnomebluetooth-1.0:amd64 (3.8.2.1-0ubuntu11, 3.12.0-0ubuntu1), 
libsystemd0:amd64 (219-4ubuntu1, 219-4ubuntu3), libsystemd0:i386 (219-4ubuntu1, 
219-4ubuntu3), liblsan0:amd64 (4.9.2-10ubuntu7, 4.9.2-10ubuntu8), 
libstdc++6:amd64 (4.9.2-10ubuntu7, 4.9.2-10ubuntu8), libstdc++6:i386 
(4.9.2-10ubuntu7, 4.9.2-10ubuntu8), libudisks2-0:amd64 (2.1.4-1git3, 2.1.5-1), 
libitm1:amd64 (4.9.2-10ubuntu7, 4.9.2-10ubuntu8), libgtksourceview-3.0-com
 mon:amd64 (3.14.1-1, 3.14.3-1), gcc-4.9-base:amd64 (4.9.2-10ubuntu7, 
4.9.2-10ubuntu8), gcc-4.9-base:i386 (4.9.2-10ubuntu7, 4.9.2-10ubuntu8), 
gnome-control-center-data:amd64 (3.14.2-2ubuntu2, 3.14.2-2ubuntu3)

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

Title:
  Screen turns green and locks out during apt full-upgrade

Status in apt package in Ubuntu:
  New

Bug description:
  Since updating to vivid, occasionally when doing an apt full-upgrade
  the screen will turn and stay bright green.  I can see and move the
  mouse cursor but nothing else, and no system keyboard shortcuts appear
  to do anything (ctrl-alt-f1 through ctrl-alt-f7, ctl-alt-backspace,
  ctl-a

[Touch-packages] [Bug 1428712] [NEW] Screen turns green and locks out during apt full-upgrade

2015-03-05 Thread Joe Barnett
Public bug reported:

Since updating to vivid, occasionally when doing an apt full-upgrade the
screen will turn and stay bright green.  I can see and move the mouse
cursor but nothing else, and no system keyboard shortcuts appear to do
anything (ctrl-alt-f1 through ctrl-alt-f7, ctl-alt-backspace, ctl-alt-
delete, etc).  Probably an issue with a specific package rather than
apt, but not sure how to narrow it down.

here's the list of packages that were upgraded the last time this
happened, form /var/log/apt/history.log:

Start-Date: 2015-03-05  07:47:15
Commandline: apt full-upgrade
Install: console-setup-linux:amd64 (1.108ubuntu3, automatic)
Upgrade: python3-apparmor:amd64 (2.9.1-0ubuntu5, 2.9.1-0ubuntu6), 
apparmor-easyprof:amd64 (2.9.1-0ubuntu5, 2.9.1-0ubuntu6), 
glib-networking-common:amd64 (2.43.1-1, 2.43.91-1), libgail18:amd64 
(2.24.26-0ubuntu2, 2.24.27-0ubuntu1), libgail18:i386 (2.24.26-0ubuntu2, 
2.24.27-0ubuntu1), libsoup2.4-1:amd64 (2.49.1-1ubuntu1, 2.49.91.1-1), 
libsoup2.4-1:i386 (2.49.1-1ubuntu1, 2.49.91.1-1), libwagon-java:amd64 
(1.0.0-2ubuntu2, 1.0.0-5), libgeis1:amd64 (2.2.16+14.04.20140303-0ubuntu1, 
2.2.16+15.04.20150304-0ubuntu1), console-setup:amd64 (1.70ubuntu11, 
1.108ubuntu3), libsoup2.4-dev:amd64 (2.49.1-1ubuntu1, 2.49.91.1-1), 
libapparmor1:amd64 (2.9.1-0ubuntu5, 2.9.1-0ubuntu6), gtk2-engines-pixbuf:amd64 
(2.24.26-0ubuntu2, 2.24.27-0ubuntu1), gtk2-engines-pixbuf:i386 
(2.24.26-0ubuntu2, 2.24.27-0ubuntu1), libglib2.0-0:amd64 (2.43.90-1, 
2.43.91-1), libglib2.0-0:i386 (2.43.90-1, 2.43.91-1), libglib2.0-dev:amd64 
(2.43.90-1, 2.43.91-1), libgtk2.0-bin:amd64 (2.24.26-0ubuntu2, 
2.24.27-0ubuntu1), libgtk2.0-commo
 n:amd64 (2.24.26-0ubuntu2, 2.24.27-0ubuntu1), gir1.2-gtk-2.0:amd64 
(2.24.26-0ubuntu2, 2.24.27-0ubuntu1), libglib2.0-data:amd64 (2.43.90-1, 
2.43.91-1), libflac8:amd64 (1.3.0-3, 1.3.1-1ubuntu1), libflac8:i386 (1.3.0-3, 
1.3.1-1ubuntu1), libsoup-gnome2.4-1:amd64 (2.49.1-1ubuntu1, 2.49.91.1-1), 
libsoup-gnome2.4-1:i386 (2.49.1-1ubuntu1, 2.49.91.1-1), libnm-util2:amd64 
(0.9.10.0-4ubuntu8, 0.9.10.0-4ubuntu9), libapparmor-perl:amd64 (2.9.1-0ubuntu5, 
2.9.1-0ubuntu6), libnm-glib-vpn1:amd64 (0.9.10.0-4ubuntu8, 0.9.10.0-4ubuntu9), 
libdee-1.0-4:amd64 (1.2.7+14.04.20140324-0ubuntu1, 
1.2.7+15.04.20150304-0ubuntu1), libgtk2.0-0:amd64 (2.24.26-0ubuntu2, 
2.24.27-0ubuntu1), libgtk2.0-0:i386 (2.24.26-0ubuntu2, 2.24.27-0ubuntu1), 
libglib2.0-0-dbg:amd64 (2.43.90-1, 2.43.91-1), gir1.2-dee-1.0:amd64 
(1.2.7+14.04.20140324-0ubuntu1, 1.2.7+15.04.20150304-0ubuntu1), 
keyboard-configuration:amd64 (1.70ubuntu11, 1.108ubuntu3), kbd:amd64 
(1.15.5-1ubuntu1, 1.15.5-1ubuntu2), libx264-142:amd64 (0.142.2431+gita5831aa-1
 ubuntu1, 0.142.2495+git6a301b6-1ubuntu1), apparmor:amd64 (2.9.1-0ubuntu5, 
2.9.1-0ubuntu6), libglib2.0-bin:amd64 (2.43.90-1, 2.43.91-1), 
python3-libapparmor:amd64 (2.9.1-0ubuntu5, 2.9.1-0ubuntu6), 
network-manager:amd64 (0.9.10.0-4ubuntu8, 0.9.10.0-4ubuntu9), 
gir1.2-networkmanager-1.0:amd64 (0.9.10.0-4ubuntu8, 0.9.10.0-4ubuntu9), 
glib-networking-services:amd64 (2.43.1-1, 2.43.91-1), libgtk2.0-dev:amd64 
(2.24.26-0ubuntu2, 2.24.27-0ubuntu1), glib-networking:amd64 (2.43.1-1, 
2.43.91-1), glib-networking:i386 (2.43.1-1, 2.43.91-1), gir1.2-soup-2.4:amd64 
(2.49.1-1ubuntu1, 2.49.91.1-1), dh-apparmor:amd64 (2.9.1-0ubuntu5, 
2.9.1-0ubuntu6), libnm-glib4:amd64 (0.9.10.0-4ubuntu8, 0.9.10.0-4ubuntu9), 
libgail-common:amd64 (2.24.26-0ubuntu2, 2.24.27-0ubuntu1), libgail-common:i386 
(2.24.26-0ubuntu2, 2.24.27-0ubuntu1)

ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: apt 1.0.9.3ubuntu1
ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0
Uname: Linux 3.19.0-7-generic x86_64
NonfreeKernelModules: nvidia wl
ApportVersion: 2.16.2-0ubuntu1
Architecture: amd64
CurrentDesktop: GNOME
Date: Thu Mar  5 08:00:19 2015
InstallationDate: Installed on 2014-02-24 (373 days ago)
InstallationMedia: Ubuntu-GNOME 14.04 "Trusty Tahr" - Alpha amd64 (20140218)
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: apt
UpgradeStatus: Upgraded to vivid on 2015-02-04 (28 days ago)

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


** Tags: amd64 apport-bug vivid

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

Title:
  Screen turns green and locks out during apt full-upgrade

Status in apt package in Ubuntu:
  New

Bug description:
  Since updating to vivid, occasionally when doing an apt full-upgrade
  the screen will turn and stay bright green.  I can see and move the
  mouse cursor but nothing else, and no system keyboard shortcuts appear
  to do anything (ctrl-alt-f1 through ctrl-alt-f7, ctl-alt-backspace,
  ctl-alt-delete, etc).  Probably an issue with a specific package
  rather than apt, but not sure how to narrow it down.

  here's the list of packages that were upgraded the last time this

[Touch-packages] [Bug 1378438] Re: Printer dialog stuck on "Getting printer information..."

2014-10-31 Thread Joe Barnett
As stated above, no symlinks in temp.  the only thing I do get when i
open a print dialog is an empty /tmp/systemd-cups.service-
RANDOMLETTERS/tmp directory.  This behavior started after upgrading from
trusty to utopic, before I switched to systemd.

/etc/cups/ppd is empty for me:
$ ls -ltra /etc/cups/ppd
total 8
drwxr-xr-x 2 root lp 4096 Sep 16 11:00 .
drwxr-xr-x 5 root lp 4096 Oct 23 10:28 ..

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

Title:
  Printer dialog stuck on "Getting printer information..."

Status in “cups” package in Ubuntu:
  Confirmed

Bug description:
  In GTK+3/gnome-3 apps (eg evince), when I select my network-discovered
  printer, the "Status" field changes to "Getting printer
  information..." and the mouse cursor goes into spinning icon, and the
  Print button stays disabled, so I cannot print.

  In Firefox, the status tells me the printer is low on toner, but
  allows me to print.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: cups 1.7.5-3ubuntu1
  ProcVersionSignature: Ubuntu 3.16.0-18.25-generic 3.16.3
  Uname: Linux 3.16.0-18-generic x86_64
  NonfreeKernelModules: nvidia wl
  ApportVersion: 2.14.7-0ubuntu2
  Architecture: amd64
  CupsErrorLog:
   E [01/Oct/2014:13:52:31 -0700] systemd_checkin: Unable to get local address 
- Permission denied
   E [02/Oct/2014:08:11:27 -0700] systemd_checkin: Unable to get local address 
- Permission denied
   E [03/Oct/2014:08:02:08 -0700] systemd_checkin: Unable to get local address 
- Permission denied
   E [03/Oct/2014:08:11:49 -0700] systemd_checkin: Unable to get local address 
- Permission denied
   E [03/Oct/2014:08:22:30 -0700] systemd_checkin: Unable to get local address 
- Permission denied
  CurrentDesktop: GNOME
  Date: Tue Oct  7 09:29:43 2014
  InstallationDate: Installed on 2014-02-24 (224 days ago)
  InstallationMedia: Ubuntu-GNOME 14.04 "Trusty Tahr" - Alpha amd64 (20140218)
  Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No 
destinations added.
  MachineType: Apple Inc. MacBookPro11,3
  Papersize: letter
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-18-generic.efi.signed 
root=UUID=135fd833-3282-4f3b-8802-0a27ec2765b9 ro quiet splash 
init=/lib/systemd/systemd vt.handoff=7
  SourcePackage: cups
  UpgradeStatus: Upgraded to utopic on 2014-08-17 (50 days ago)
  dmi.bios.date: 10/18/2013
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBP112.88Z.0138.B02.1310181745
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-2BD1B31983FE1663
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookPro11,3
  dmi.chassis.type: 10
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-2BD1B31983FE1663
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMBP112.88Z.0138.B02.1310181745:bd10/18/2013:svnAppleInc.:pnMacBookPro11,3:pvr1.0:rvnAppleInc.:rnMac-2BD1B31983FE1663:rvrMacBookPro11,3:cvnAppleInc.:ct10:cvrMac-2BD1B31983FE1663:
  dmi.product.name: MacBookPro11,3
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1378438/+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 1378438] Re: Printer dialog stuck on "Getting printer information..."

2014-10-31 Thread Joe Barnett
I had (and have) no scp-dbus-service.py running per `ps -ef` output.

trying to print from LibreOffice or okular doesn't show the network-
discovered printer at all, only print to pdf/file options are available
(with gtk3 / firefox print dialogs, initially only print to pdf/file is
shown, then the network-discovered printer appears a few seconds later)

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

Title:
  Printer dialog stuck on "Getting printer information..."

Status in “cups” package in Ubuntu:
  Confirmed

Bug description:
  In GTK+3/gnome-3 apps (eg evince), when I select my network-discovered
  printer, the "Status" field changes to "Getting printer
  information..." and the mouse cursor goes into spinning icon, and the
  Print button stays disabled, so I cannot print.

  In Firefox, the status tells me the printer is low on toner, but
  allows me to print.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: cups 1.7.5-3ubuntu1
  ProcVersionSignature: Ubuntu 3.16.0-18.25-generic 3.16.3
  Uname: Linux 3.16.0-18-generic x86_64
  NonfreeKernelModules: nvidia wl
  ApportVersion: 2.14.7-0ubuntu2
  Architecture: amd64
  CupsErrorLog:
   E [01/Oct/2014:13:52:31 -0700] systemd_checkin: Unable to get local address 
- Permission denied
   E [02/Oct/2014:08:11:27 -0700] systemd_checkin: Unable to get local address 
- Permission denied
   E [03/Oct/2014:08:02:08 -0700] systemd_checkin: Unable to get local address 
- Permission denied
   E [03/Oct/2014:08:11:49 -0700] systemd_checkin: Unable to get local address 
- Permission denied
   E [03/Oct/2014:08:22:30 -0700] systemd_checkin: Unable to get local address 
- Permission denied
  CurrentDesktop: GNOME
  Date: Tue Oct  7 09:29:43 2014
  InstallationDate: Installed on 2014-02-24 (224 days ago)
  InstallationMedia: Ubuntu-GNOME 14.04 "Trusty Tahr" - Alpha amd64 (20140218)
  Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No 
destinations added.
  MachineType: Apple Inc. MacBookPro11,3
  Papersize: letter
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-18-generic.efi.signed 
root=UUID=135fd833-3282-4f3b-8802-0a27ec2765b9 ro quiet splash 
init=/lib/systemd/systemd vt.handoff=7
  SourcePackage: cups
  UpgradeStatus: Upgraded to utopic on 2014-08-17 (50 days ago)
  dmi.bios.date: 10/18/2013
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBP112.88Z.0138.B02.1310181745
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-2BD1B31983FE1663
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookPro11,3
  dmi.chassis.type: 10
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-2BD1B31983FE1663
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMBP112.88Z.0138.B02.1310181745:bd10/18/2013:svnAppleInc.:pnMacBookPro11,3:pvr1.0:rvnAppleInc.:rnMac-2BD1B31983FE1663:rvrMacBookPro11,3:cvnAppleInc.:ct10:cvrMac-2BD1B31983FE1663:
  dmi.product.name: MacBookPro11,3
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1378438/+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 1378438] Re: Printer dialog stuck on "Getting printer information..."

2014-10-30 Thread Joe Barnett
the chmod -r did not fix the issue for me (original reporter).  In
addition, I don't see any ppd file links getting created in /tmp.


For now, my only workaround is to print to pdf file, then open the pdf using 
firefox's native pdf viewer and print from there

** 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/1378438

Title:
  Printer dialog stuck on "Getting printer information..."

Status in “cups” package in Ubuntu:
  Confirmed

Bug description:
  In GTK+3/gnome-3 apps (eg evince), when I select my network-discovered
  printer, the "Status" field changes to "Getting printer
  information..." and the mouse cursor goes into spinning icon, and the
  Print button stays disabled, so I cannot print.

  In Firefox, the status tells me the printer is low on toner, but
  allows me to print.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: cups 1.7.5-3ubuntu1
  ProcVersionSignature: Ubuntu 3.16.0-18.25-generic 3.16.3
  Uname: Linux 3.16.0-18-generic x86_64
  NonfreeKernelModules: nvidia wl
  ApportVersion: 2.14.7-0ubuntu2
  Architecture: amd64
  CupsErrorLog:
   E [01/Oct/2014:13:52:31 -0700] systemd_checkin: Unable to get local address 
- Permission denied
   E [02/Oct/2014:08:11:27 -0700] systemd_checkin: Unable to get local address 
- Permission denied
   E [03/Oct/2014:08:02:08 -0700] systemd_checkin: Unable to get local address 
- Permission denied
   E [03/Oct/2014:08:11:49 -0700] systemd_checkin: Unable to get local address 
- Permission denied
   E [03/Oct/2014:08:22:30 -0700] systemd_checkin: Unable to get local address 
- Permission denied
  CurrentDesktop: GNOME
  Date: Tue Oct  7 09:29:43 2014
  InstallationDate: Installed on 2014-02-24 (224 days ago)
  InstallationMedia: Ubuntu-GNOME 14.04 "Trusty Tahr" - Alpha amd64 (20140218)
  Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No 
destinations added.
  MachineType: Apple Inc. MacBookPro11,3
  Papersize: letter
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-18-generic.efi.signed 
root=UUID=135fd833-3282-4f3b-8802-0a27ec2765b9 ro quiet splash 
init=/lib/systemd/systemd vt.handoff=7
  SourcePackage: cups
  UpgradeStatus: Upgraded to utopic on 2014-08-17 (50 days ago)
  dmi.bios.date: 10/18/2013
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBP112.88Z.0138.B02.1310181745
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-2BD1B31983FE1663
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookPro11,3
  dmi.chassis.type: 10
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-2BD1B31983FE1663
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMBP112.88Z.0138.B02.1310181745:bd10/18/2013:svnAppleInc.:pnMacBookPro11,3:pvr1.0:rvnAppleInc.:rnMac-2BD1B31983FE1663:rvrMacBookPro11,3:cvnAppleInc.:ct10:cvrMac-2BD1B31983FE1663:
  dmi.product.name: MacBookPro11,3
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1378438/+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 1378438] [NEW] Printer dialog stuck on "Getting printer information..."

2014-10-07 Thread Joe Barnett
Public bug reported:

In GTK+3/gnome-3 apps (eg evince), when I select my network-discovered
printer, the "Status" field changes to "Getting printer information..."
and the mouse cursor goes into spinning icon, and the Print button stays
disabled, so I cannot print.

In Firefox, the status tells me the printer is low on toner, but allows
me to print.

ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: cups 1.7.5-3ubuntu1
ProcVersionSignature: Ubuntu 3.16.0-18.25-generic 3.16.3
Uname: Linux 3.16.0-18-generic x86_64
NonfreeKernelModules: nvidia wl
ApportVersion: 2.14.7-0ubuntu2
Architecture: amd64
CupsErrorLog:
 E [01/Oct/2014:13:52:31 -0700] systemd_checkin: Unable to get local address - 
Permission denied
 E [02/Oct/2014:08:11:27 -0700] systemd_checkin: Unable to get local address - 
Permission denied
 E [03/Oct/2014:08:02:08 -0700] systemd_checkin: Unable to get local address - 
Permission denied
 E [03/Oct/2014:08:11:49 -0700] systemd_checkin: Unable to get local address - 
Permission denied
 E [03/Oct/2014:08:22:30 -0700] systemd_checkin: Unable to get local address - 
Permission denied
CurrentDesktop: GNOME
Date: Tue Oct  7 09:29:43 2014
InstallationDate: Installed on 2014-02-24 (224 days ago)
InstallationMedia: Ubuntu-GNOME 14.04 "Trusty Tahr" - Alpha amd64 (20140218)
Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No 
destinations added.
MachineType: Apple Inc. MacBookPro11,3
Papersize: letter
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-18-generic.efi.signed 
root=UUID=135fd833-3282-4f3b-8802-0a27ec2765b9 ro quiet splash 
init=/lib/systemd/systemd vt.handoff=7
SourcePackage: cups
UpgradeStatus: Upgraded to utopic on 2014-08-17 (50 days ago)
dmi.bios.date: 10/18/2013
dmi.bios.vendor: Apple Inc.
dmi.bios.version: MBP112.88Z.0138.B02.1310181745
dmi.board.asset.tag: Base Board Asset Tag#
dmi.board.name: Mac-2BD1B31983FE1663
dmi.board.vendor: Apple Inc.
dmi.board.version: MacBookPro11,3
dmi.chassis.type: 10
dmi.chassis.vendor: Apple Inc.
dmi.chassis.version: Mac-2BD1B31983FE1663
dmi.modalias: 
dmi:bvnAppleInc.:bvrMBP112.88Z.0138.B02.1310181745:bd10/18/2013:svnAppleInc.:pnMacBookPro11,3:pvr1.0:rvnAppleInc.:rnMac-2BD1B31983FE1663:rvrMacBookPro11,3:cvnAppleInc.:ct10:cvrMac-2BD1B31983FE1663:
dmi.product.name: MacBookPro11,3
dmi.product.version: 1.0
dmi.sys.vendor: Apple Inc.

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


** Tags: amd64 apparmor apport-bug gnome3-ppa third-party-packages utopic

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

Title:
  Printer dialog stuck on "Getting printer information..."

Status in “cups” package in Ubuntu:
  New

Bug description:
  In GTK+3/gnome-3 apps (eg evince), when I select my network-discovered
  printer, the "Status" field changes to "Getting printer
  information..." and the mouse cursor goes into spinning icon, and the
  Print button stays disabled, so I cannot print.

  In Firefox, the status tells me the printer is low on toner, but
  allows me to print.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: cups 1.7.5-3ubuntu1
  ProcVersionSignature: Ubuntu 3.16.0-18.25-generic 3.16.3
  Uname: Linux 3.16.0-18-generic x86_64
  NonfreeKernelModules: nvidia wl
  ApportVersion: 2.14.7-0ubuntu2
  Architecture: amd64
  CupsErrorLog:
   E [01/Oct/2014:13:52:31 -0700] systemd_checkin: Unable to get local address 
- Permission denied
   E [02/Oct/2014:08:11:27 -0700] systemd_checkin: Unable to get local address 
- Permission denied
   E [03/Oct/2014:08:02:08 -0700] systemd_checkin: Unable to get local address 
- Permission denied
   E [03/Oct/2014:08:11:49 -0700] systemd_checkin: Unable to get local address 
- Permission denied
   E [03/Oct/2014:08:22:30 -0700] systemd_checkin: Unable to get local address 
- Permission denied
  CurrentDesktop: GNOME
  Date: Tue Oct  7 09:29:43 2014
  InstallationDate: Installed on 2014-02-24 (224 days ago)
  InstallationMedia: Ubuntu-GNOME 14.04 "Trusty Tahr" - Alpha amd64 (20140218)
  Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No 
destinations added.
  MachineType: Apple Inc. MacBookPro11,3
  Papersize: letter
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-18-generic.efi.signed 
root=UUID=135fd833-3282-4f3b-8802-0a27ec2765b9 ro quiet splash 
init=/lib/systemd/systemd vt.handoff=7
  SourcePackage: cups
  UpgradeStatus: Upgraded to utopic on 2014-08-17 (50 days ago)
  dmi.bios.date: 10/18/2013
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBP112.88Z.0138.B02.1310181745
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-2BD1B31983FE1663
  dmi.board.vendor: Apple Inc.
  dmi.b

[Touch-packages] [Bug 1358441] Re: HDMI output audio no longer working

2014-08-21 Thread Joe Barnett
*** This bug is a duplicate of bug 1358434 ***
https://bugs.launchpad.net/bugs/1358434

** This bug has been marked a duplicate of bug 1358434
   usb headset not available as microphone source

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

Title:
  HDMI output audio no longer working

Status in “pulseaudio” package in Ubuntu:
  Incomplete

Bug description:
  My laptop's HDMI output worked perfectly with both video and audio in
  trusty, but upon upgrade to utopic, the HDMI audio stopped working.
  It shows up as an option in gnome sound prefernces (under nvidia
  GK107), but selecting it keeps the audio output on the laptop
  speakers.  It does not show up as an option in the
  https://extensions.gnome.org/extension/751/audio-output-switcher/ list
  though.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: pulseaudio 1:4.0-0ubuntu18
  ProcVersionSignature: Ubuntu 3.16.0-9.14-generic 3.16.1
  Uname: Linux 3.16.0-9-generic x86_64
  NonfreeKernelModules: nvidia wl
  ApportVersion: 2.14.5-0ubuntu4
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Aug 18 11:37:09 2014
  InstallationDate: Installed on 2014-02-24 (175 days ago)
  InstallationMedia: Ubuntu-GNOME 14.04 "Trusty Tahr" - Alpha amd64 (20140218)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to utopic on 2014-08-17 (0 days ago)
  dmi.bios.date: 10/18/2013
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBP112.88Z.0138.B02.1310181745
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-2BD1B31983FE1663
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookPro11,3
  dmi.chassis.type: 10
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-2BD1B31983FE1663
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMBP112.88Z.0138.B02.1310181745:bd10/18/2013:svnAppleInc.:pnMacBookPro11,3:pvr1.0:rvnAppleInc.:rnMac-2BD1B31983FE1663:rvrMacBookPro11,3:cvnAppleInc.:ct10:cvrMac-2BD1B31983FE1663:
  dmi.product.name: MacBookPro11,3
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.
  modified.conffile..etc.pulse.default.pa: [modified]
  mtime.conffile..etc.pulse.default.pa: 2014-08-17T12:06:50.161248

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1358441/+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 1358434] Re: usb headset not available as microphone source

2014-08-21 Thread Joe Barnett
confirmed that 2 instances were running.  killling them both & starting
a new one fixed this as well as duplicate #1358441 -- but seems like
still a bug that 2 instances got instantiated.

** Changed in: pulseaudio (Ubuntu)
   Status: Incomplete => 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/1358434

Title:
  usb headset not available as microphone source

Status in “pulseaudio” package in Ubuntu:
  New

Bug description:
  I have a usb Plantronics .Audio 478 headset that I use for conference
  calls.  Works perfect in trusty, but upon upgrade to utopic the
  microphone is not available as an input in the gnome sound preferences
  or pavucontrol.  There appears to be an entry in alsamixer, and a
  source in pactl list.

  Source #9
State: SUSPENDED
Name: 
alsa_output.usb-Plantronics_Plantronics_.Audio_478_USB-00-USB.analog-stereo.monitor
Description: Monitor of Plantronics .Audio 478 USB Analog Stereo
Driver: module-alsa-card.c
Sample Specification: s16le 2ch 44100Hz
Channel Map: front-left,front-right
Owner Module: 29
Mute: no
Volume: 0: 100% 1: 100%
0: 0.00 dB 1: 0.00 dB
balance 0.00
Base Volume: 100%
 0.00 dB
Monitor of Sink: 
alsa_output.usb-Plantronics_Plantronics_.Audio_478_USB-00-USB.analog-stereo
Latency: 0 usec, configured 0 usec
Flags: DECIBEL_VOLUME LATENCY 
Properties:
device.description = "Monitor of Plantronics .Audio 478 USB 
Analog Stereo"
device.class = "monitor"
alsa.card = "3"
alsa.card_name = "Plantronics .Audio 478 USB"
alsa.long_card_name = "Plantronics Plantronics .Audio 478 USB 
at usb-:00:14.0-5.3.4, full speed"
alsa.driver_name = "snd_usb_audio"
device.bus_path = "pci-:00:14.0-usb-0:5.3.4:1.0"
sysfs.path = 
"/devices/pci:00/:00:14.0/usb1/1-5/1-5.3/1-5.3.4/1-5.3.4:1.0/sound/card3"
udev.id = "usb-Plantronics_Plantronics_.Audio_478_USB-00-USB"
device.bus = "usb"
device.vendor.id = "047f"
device.vendor.name = "Plantronics, Inc."
device.product.id = "c011"
device.product.name = "Plantronics .Audio 478 USB"
device.serial = "Plantronics_Plantronics_.Audio_478_USB"
device.string = "3"
module-udev-detect.discovered = "1"
device.icon_name = "audio-card-usb"
Formats:
pcm

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: pulseaudio 1:4.0-0ubuntu18
  ProcVersionSignature: Ubuntu 3.16.0-9.14-generic 3.16.1
  Uname: Linux 3.16.0-9-generic x86_64
  NonfreeKernelModules: nvidia wl
  ApportVersion: 2.14.5-0ubuntu4
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Aug 18 11:28:51 2014
  InstallationDate: Installed on 2014-02-24 (175 days ago)
  InstallationMedia: Ubuntu-GNOME 14.04 "Trusty Tahr" - Alpha amd64 (20140218)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to utopic on 2014-08-17 (0 days ago)
  dmi.bios.date: 10/18/2013
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBP112.88Z.0138.B02.1310181745
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-2BD1B31983FE1663
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookPro11,3
  dmi.chassis.type: 10
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-2BD1B31983FE1663
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMBP112.88Z.0138.B02.1310181745:bd10/18/2013:svnAppleInc.:pnMacBookPro11,3:pvr1.0:rvnAppleInc.:rnMac-2BD1B31983FE1663:rvrMacBookPro11,3:cvnAppleInc.:ct10:cvrMac-2BD1B31983FE1663:
  dmi.product.name: MacBookPro11,3
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.
  modified.conffile..etc.pulse.default.pa: [modified]
  mtime.conffile..etc.pulse.default.pa: 2014-08-17T12:06:50.161248

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1358434/+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 1358441] [NEW] HDMI output audio no longer working

2014-08-18 Thread Joe Barnett
Public bug reported:

My laptop's HDMI output worked perfectly with both video and audio in
trusty, but upon upgrade to utopic, the HDMI audio stopped working.  It
shows up as an option in gnome sound prefernces (under nvidia GK107),
but selecting it keeps the audio output on the laptop speakers.  It does
not show up as an option in the
https://extensions.gnome.org/extension/751/audio-output-switcher/ list
though.

ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: pulseaudio 1:4.0-0ubuntu18
ProcVersionSignature: Ubuntu 3.16.0-9.14-generic 3.16.1
Uname: Linux 3.16.0-9-generic x86_64
NonfreeKernelModules: nvidia wl
ApportVersion: 2.14.5-0ubuntu4
Architecture: amd64
CurrentDesktop: GNOME
Date: Mon Aug 18 11:37:09 2014
InstallationDate: Installed on 2014-02-24 (175 days ago)
InstallationMedia: Ubuntu-GNOME 14.04 "Trusty Tahr" - Alpha amd64 (20140218)
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: pulseaudio
UpgradeStatus: Upgraded to utopic on 2014-08-17 (0 days ago)
dmi.bios.date: 10/18/2013
dmi.bios.vendor: Apple Inc.
dmi.bios.version: MBP112.88Z.0138.B02.1310181745
dmi.board.asset.tag: Base Board Asset Tag#
dmi.board.name: Mac-2BD1B31983FE1663
dmi.board.vendor: Apple Inc.
dmi.board.version: MacBookPro11,3
dmi.chassis.type: 10
dmi.chassis.vendor: Apple Inc.
dmi.chassis.version: Mac-2BD1B31983FE1663
dmi.modalias: 
dmi:bvnAppleInc.:bvrMBP112.88Z.0138.B02.1310181745:bd10/18/2013:svnAppleInc.:pnMacBookPro11,3:pvr1.0:rvnAppleInc.:rnMac-2BD1B31983FE1663:rvrMacBookPro11,3:cvnAppleInc.:ct10:cvrMac-2BD1B31983FE1663:
dmi.product.name: MacBookPro11,3
dmi.product.version: 1.0
dmi.sys.vendor: Apple Inc.
modified.conffile..etc.pulse.default.pa: [modified]
mtime.conffile..etc.pulse.default.pa: 2014-08-17T12:06:50.161248

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


** Tags: amd64 apport-bug utopic

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

Title:
  HDMI output audio no longer working

Status in “pulseaudio” package in Ubuntu:
  New

Bug description:
  My laptop's HDMI output worked perfectly with both video and audio in
  trusty, but upon upgrade to utopic, the HDMI audio stopped working.
  It shows up as an option in gnome sound prefernces (under nvidia
  GK107), but selecting it keeps the audio output on the laptop
  speakers.  It does not show up as an option in the
  https://extensions.gnome.org/extension/751/audio-output-switcher/ list
  though.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: pulseaudio 1:4.0-0ubuntu18
  ProcVersionSignature: Ubuntu 3.16.0-9.14-generic 3.16.1
  Uname: Linux 3.16.0-9-generic x86_64
  NonfreeKernelModules: nvidia wl
  ApportVersion: 2.14.5-0ubuntu4
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Aug 18 11:37:09 2014
  InstallationDate: Installed on 2014-02-24 (175 days ago)
  InstallationMedia: Ubuntu-GNOME 14.04 "Trusty Tahr" - Alpha amd64 (20140218)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to utopic on 2014-08-17 (0 days ago)
  dmi.bios.date: 10/18/2013
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBP112.88Z.0138.B02.1310181745
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-2BD1B31983FE1663
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookPro11,3
  dmi.chassis.type: 10
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-2BD1B31983FE1663
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMBP112.88Z.0138.B02.1310181745:bd10/18/2013:svnAppleInc.:pnMacBookPro11,3:pvr1.0:rvnAppleInc.:rnMac-2BD1B31983FE1663:rvrMacBookPro11,3:cvnAppleInc.:ct10:cvrMac-2BD1B31983FE1663:
  dmi.product.name: MacBookPro11,3
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.
  modified.conffile..etc.pulse.default.pa: [modified]
  mtime.conffile..etc.pulse.default.pa: 2014-08-17T12:06:50.161248

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1358441/+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 1358434] [NEW] usb headset not available as microphone source

2014-08-18 Thread Joe Barnett
Public bug reported:

I have a usb Plantronics .Audio 478 headset that I use for conference
calls.  Works perfect in trusty, but upon upgrade to utopic the
microphone is not available as an input in the gnome sound preferences
or pavucontrol.  There appears to be an entry in alsamixer, and a source
in pactl list.

Source #9
State: SUSPENDED
Name: 
alsa_output.usb-Plantronics_Plantronics_.Audio_478_USB-00-USB.analog-stereo.monitor
Description: Monitor of Plantronics .Audio 478 USB Analog Stereo
Driver: module-alsa-card.c
Sample Specification: s16le 2ch 44100Hz
Channel Map: front-left,front-right
Owner Module: 29
Mute: no
Volume: 0: 100% 1: 100%
0: 0.00 dB 1: 0.00 dB
balance 0.00
Base Volume: 100%
 0.00 dB
Monitor of Sink: 
alsa_output.usb-Plantronics_Plantronics_.Audio_478_USB-00-USB.analog-stereo
Latency: 0 usec, configured 0 usec
Flags: DECIBEL_VOLUME LATENCY 
Properties:
device.description = "Monitor of Plantronics .Audio 478 USB 
Analog Stereo"
device.class = "monitor"
alsa.card = "3"
alsa.card_name = "Plantronics .Audio 478 USB"
alsa.long_card_name = "Plantronics Plantronics .Audio 478 USB 
at usb-:00:14.0-5.3.4, full speed"
alsa.driver_name = "snd_usb_audio"
device.bus_path = "pci-:00:14.0-usb-0:5.3.4:1.0"
sysfs.path = 
"/devices/pci:00/:00:14.0/usb1/1-5/1-5.3/1-5.3.4/1-5.3.4:1.0/sound/card3"
udev.id = "usb-Plantronics_Plantronics_.Audio_478_USB-00-USB"
device.bus = "usb"
device.vendor.id = "047f"
device.vendor.name = "Plantronics, Inc."
device.product.id = "c011"
device.product.name = "Plantronics .Audio 478 USB"
device.serial = "Plantronics_Plantronics_.Audio_478_USB"
device.string = "3"
module-udev-detect.discovered = "1"
device.icon_name = "audio-card-usb"
Formats:
pcm

ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: pulseaudio 1:4.0-0ubuntu18
ProcVersionSignature: Ubuntu 3.16.0-9.14-generic 3.16.1
Uname: Linux 3.16.0-9-generic x86_64
NonfreeKernelModules: nvidia wl
ApportVersion: 2.14.5-0ubuntu4
Architecture: amd64
CurrentDesktop: GNOME
Date: Mon Aug 18 11:28:51 2014
InstallationDate: Installed on 2014-02-24 (175 days ago)
InstallationMedia: Ubuntu-GNOME 14.04 "Trusty Tahr" - Alpha amd64 (20140218)
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: pulseaudio
UpgradeStatus: Upgraded to utopic on 2014-08-17 (0 days ago)
dmi.bios.date: 10/18/2013
dmi.bios.vendor: Apple Inc.
dmi.bios.version: MBP112.88Z.0138.B02.1310181745
dmi.board.asset.tag: Base Board Asset Tag#
dmi.board.name: Mac-2BD1B31983FE1663
dmi.board.vendor: Apple Inc.
dmi.board.version: MacBookPro11,3
dmi.chassis.type: 10
dmi.chassis.vendor: Apple Inc.
dmi.chassis.version: Mac-2BD1B31983FE1663
dmi.modalias: 
dmi:bvnAppleInc.:bvrMBP112.88Z.0138.B02.1310181745:bd10/18/2013:svnAppleInc.:pnMacBookPro11,3:pvr1.0:rvnAppleInc.:rnMac-2BD1B31983FE1663:rvrMacBookPro11,3:cvnAppleInc.:ct10:cvrMac-2BD1B31983FE1663:
dmi.product.name: MacBookPro11,3
dmi.product.version: 1.0
dmi.sys.vendor: Apple Inc.
modified.conffile..etc.pulse.default.pa: [modified]
mtime.conffile..etc.pulse.default.pa: 2014-08-17T12:06:50.161248

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


** Tags: amd64 apport-bug utopic

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

Title:
  usb headset not available as microphone source

Status in “pulseaudio” package in Ubuntu:
  New

Bug description:
  I have a usb Plantronics .Audio 478 headset that I use for conference
  calls.  Works perfect in trusty, but upon upgrade to utopic the
  microphone is not available as an input in the gnome sound preferences
  or pavucontrol.  There appears to be an entry in alsamixer, and a
  source in pactl list.

  Source #9
State: SUSPENDED
Name: 
alsa_output.usb-Plantronics_Plantronics_.Audio_478_USB-00-USB.analog-stereo.monitor
Description: Monitor of Plantronics .Audio 478 USB Analog Stereo
Driver: module-alsa-card.c
Sample Specification: s16le 2ch 44100Hz
Channel Map: front-left,front-right
Owner Module: 29
Mute: no
Volume: 0: 100% 1: 100%
0: 0.00 dB 1: 0.00 dB
balance 0.00
Base Volume: 100%
 0.00 dB
Monitor of Sink: 
alsa_output.usb-Plantronics_Plantronics_.Audio_478_USB-00-USB.analog-stereo
Latency: 0 usec, configured 0 usec