[Touch-packages] [Bug 1529910] Re: can't log whit my password on account

[Launchpad Bug Tracker]

[Expired for lightdm (Ubuntu) because there has been no activity for 60
days.]

** Changed in: lightdm (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  can't log whit my password on account

Status in lightdm package in Ubuntu:
  Expired

Bug description:
  when i try to log in on my acc whit my password i can't do it, i just
  get back to log in page and i need to type password again.. nothing
  seems to help..

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: lightdm 1.10.6-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-48.80-generic 3.13.11-ckt16
  Uname: Linux 3.13.0-48-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Dec 29 18:02:16 2015
  InstallationDate: Installed on 2015-02-12 (320 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1529910/+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 1392064] Re: lightdm ignores .conf file in /usr/share/lightdm/lightdm.conf

[Launchpad Bug Tracker]

[Expired for lightdm (Ubuntu) because there has been no activity for 60
days.]

** Changed in: lightdm (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  lightdm ignores .conf file in /usr/share/lightdm/lightdm.conf

Status in lightdm package in Ubuntu:
  Expired

Bug description:
  Setup:
  Ubuntu 14.04.1LTS
  IIyama 19" Pro-Lite Touchscreen
  Dell 17" regular monitor

  Due to another bug in the detection of input devices I had to write a
  script to tell Ubuntu which screen to use the touch from the
  touchscreen.

  so I put the following two entries into a basic bash script based on xinput 
list and xrandr -q 
  
  #!/bin/bash
  xinput map-to-output 12 DVI-I-1
  xrandr --output DVI-I-1 --primary
  =

  I added this script to 
/usr/share/lightdm/lightdm.conf.d/50-dualscreen-touch.conf
  and the contents look like this.
  
  [SeatDefaults]
  greeter-setup-script=/usr/local/bin/iiyama-touchscreen.sh
  session-setup-script=/usr/local/bin/iiyama-touchscreen.sh
  
  When I start a user session the touchscreen is calibrated and works normally 
with the touch happening on the touchscreen.
  As soon as I logoff into LightDM the touch calibration is off moving the 
pointer a logarithmic distance from the left of the touchscreen. 

  As soon as I log in again, no problems, touch works great, log back
  out into the lightDM greeter and boom touch is all crazy.

  Can lightdm please detect that a touchscreen can only accept touch input and 
output to the touchscreen device??
  Or at least have lightdm actually run the script when given?

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: lightdm 1.10.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8
  Uname: Linux 3.13.0-39-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Nov 12 22:11:38 2014
  InstallationDate: Installed on 2014-11-03 (8 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  LightdmConfig:
   [SeatDefaults]
   autologin-user=boerske
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1392064/+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 1564616] Re: detaching lightdm into background

[Launchpad Bug Tracker]

[Expired for lightdm (Ubuntu) because there has been no activity for 60
days.]

** Changed in: lightdm (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  detaching lightdm into background

Status in lightdm package in Ubuntu:
  Expired

Bug description:
  Hi

  When starting /etc/init.d/lightdm (either directly from root console
  or through SysV init), it will get stuck because lightdm doesn't fork
  into background when starting.

  Please could you add --background option to start-stop-daemon to fix
  this? (note: the debian lightdm package already does this)

  This change is needed for ubuntuBSD (which uses SysV init to manage
  system daemons).

  Thank you!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1564616/+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 1566979] Re: [Veriton T/M/S661; 461, Realtek ALC1200, Green Line Out, Rear] No sound at all

[Launchpad Bug Tracker]

[Expired for alsa-driver (Ubuntu) because there has been no activity for
60 days.]

** Changed in: alsa-driver (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  [Veriton T/M/S661;461, Realtek ALC1200, Green Line Out, Rear] No sound
  at all

Status in alsa-driver package in Ubuntu:
  Expired

Bug description:
  No sound at all

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.2.0-34.39-generic 4.2.8-ckt4
  Uname: Linux 4.2.0-34-generic i686
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  martha 1156 F pulseaudio
  CurrentDesktop: Unity
  Date: Wed Apr  6 11:52:56 2016
  InstallationDate: Installed on 2016-03-11 (26 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release i386 (20151021)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel failed
  Symptom_Card: Audio Interno - HDA Intel
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  martha 1156 F pulseaudio
  Symptom_Jack: Green Line Out, Rear
  Symptom_Type: No sound at all
  Title: [Veriton T/M/S661;461, Realtek ALC1200, Green Line Out, Rear] No sound 
at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/20/2008
  dmi.bios.vendor: Acer
  dmi.bios.version: R01-B4
  dmi.board.name: EQ35M
  dmi.board.vendor: Acer
  dmi.board.version: 1.0
  dmi.chassis.type: 3
  dmi.chassis.vendor: Acer
  dmi.modalias: 
dmi:bvnAcer:bvrR01-B4:bd10/20/2008:svnAcer:pnVeritonT/M/S661;461:pvr'R01-B4':rvnAcer:rnEQ35M:rvr1.0:cvnAcer:ct3:cvr:
  dmi.product.name: Veriton T/M/S661;461
  dmi.product.version: 'R01-B4'
  dmi.sys.vendor: Acer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1566979/+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 1589330] [NEW] Sync json-glib 1.2.0-1 (main) from Debian unstable (main)

[Logan Rosen]

Public bug reported:

Please sync json-glib 1.2.0-1 (main) from Debian unstable (main)

Explanation of the Ubuntu delta and why it can be dropped:
  * New upstream release
  * debian/libjson-glib-1.0-0.symbols:
- Updated
  * debian/patches/0001-tests-builder-Don-t-duplicate-test-names.patch:
- Applied upstream
All changes are in Debian, plus a new upstream release.

Changelog entries since current yakkety version 1.1.2-0ubuntu1:

json-glib (1.2.0-1) unstable; urgency=medium

  * New upstream release.
  * Bump Standards-Version to 3.9.7
  * Drop debian/patches/0001-tests-builder-Don-t-duplicate-test-names.patch
- merged upstream.
  * Updated debian/libjson-glib-1.0-0.symbols with many additions.

 -- Andreas Henriksson   Thu, 24 Mar 2016 16:26:57
+0100

** Affects: json-glib (Ubuntu)
 Importance: Wishlist
 Status: New

** Changed in: json-glib (Ubuntu)
   Importance: Undecided => Wishlist

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

Title:
  Sync json-glib 1.2.0-1 (main) from Debian unstable (main)

Status in json-glib package in Ubuntu:
  New

Bug description:
  Please sync json-glib 1.2.0-1 (main) from Debian unstable (main)

  Explanation of the Ubuntu delta and why it can be dropped:
* New upstream release
* debian/libjson-glib-1.0-0.symbols:
  - Updated
* debian/patches/0001-tests-builder-Don-t-duplicate-test-names.patch:
  - Applied upstream
  All changes are in Debian, plus a new upstream release.

  Changelog entries since current yakkety version 1.1.2-0ubuntu1:

  json-glib (1.2.0-1) unstable; urgency=medium

* New upstream release.
* Bump Standards-Version to 3.9.7
* Drop debian/patches/0001-tests-builder-Don-t-duplicate-test-names.patch
  - merged upstream.
* Updated debian/libjson-glib-1.0-0.symbols with many additions.

   -- Andreas Henriksson   Thu, 24 Mar 2016 16:26:57
  +0100

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/json-glib/+bug/1589330/+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 1585020] Re: Bluetooth does not work

[Christopher M. Penalver]

Guilherme José Resende Albuquerque, could you please provide the output of the 
following terminal command:
sudo cat /sys/kernel/debug/usb/devices

** Tags added: latest-bios-r0180d5

** No longer affects: bluez (Ubuntu)

** Changed in: linux (Ubuntu)
   Importance: High => Medium

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

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

Title:
  Bluetooth does not work

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  My bluetooth not work, before update incremental of ubuntu 16.04

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-22-generic 4.4.0-22.40
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  guilherme   1588 F pulseaudio
   /dev/snd/controlC1:  guilherme   1588 F pulseaudio
  CurrentDesktop: Unity
  Date: Mon May 23 23:46:56 2016
  HibernationDevice: RESUME=UUID=a6865d25-3156-437d-aacf-017df3a88e6b
  InstallationDate: Installed on 2016-05-14 (9 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Sony Corporation SVE14125CBB
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic.efi.signed 
root=UUID=2db3f6c7-ed97-44fd-8953-a7fb072c28a1 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-22-generic N/A
   linux-backports-modules-4.4.0-22-generic  N/A
   linux-firmware1.157
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/19/2013
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: R0180D5
  dmi.board.asset.tag: N/A
  dmi.board.name: VAIO
  dmi.board.vendor: Sony Corporation
  dmi.board.version: N/A
  dmi.chassis.asset.tag: N/A
  dmi.chassis.type: 10
  dmi.chassis.vendor: Sony Corporation
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrR0180D5:bd03/19/2013:svnSonyCorporation:pnSVE14125CBB:pvrC800D43W:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A:
  dmi.product.name: SVE14125CBB
  dmi.product.version: C800D43W
  dmi.sys.vendor: Sony Corporation

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1585020/+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 1241241] Re: German translation of the command "free" (procps) damages text alignment

[Christian Kroll]

Still present in xenial. Unbelievable.

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

Title:
  German translation of the command "free" (procps) damages text
  alignment

Status in language-pack-de-base package in Ubuntu:
  Confirmed

Bug description:
  The German translation of the "free" command's output (part of the
  procps package) looks distorted. The output is meant to be aligned to
  resemble a table like appearance. See attached file for examples.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/language-pack-de-base/+bug/1241241/+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 1588287] Re: util-linux breaks xenial installation

[Bug Watch Updater]

** Changed in: util-linux (Debian)
   Status: Unknown => Fix Released

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

Title:
  util-linux breaks xenial installation

Status in util-linux package in Ubuntu:
  Fix Released
Status in util-linux source package in Trusty:
  Incomplete
Status in util-linux package in Debian:
  Fix Released

Bug description:
  Attempting to install xenial from an alternate install image xenial-
  alternate-amd64.iso triggered the bug reported at:

  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=823665

  and fixed by the patch at:

  https://anonscm.debian.org/cgit/collab-maint/pkg-util-
  linux.git/commit/?id=49a9f9ff0cdb64c02b12c2a00af30472305bc377

  The patch was made on util-linux-2.28-2 but can be applied easily to
  2.27.1-6ubuntu3 as found in xenial, so I back-ported the patch onto my
  local copy of the iso and can confirm that the installation got past
  the installation of util-linux.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1588287/+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 1589317] [NEW] Upgrading to Xenial leaves empty /usr/lib/x86_64-linux-gnu/pango/ hierarchy

[Christian Reis]

Public bug reported:

During an upgrade from a Trusty system to Xenial, I ended up with the
following problem:

Removing linux-image-extra-3.13.0-85-generic (3.13.0-85.129) ...
depmod: FATAL: could not load /boot/System.map-3.13.0-85-generic: No such file 
or directory
run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 3.13.0-85-generic 
/boot/vmlinuz-3.13.0-85-generic
run-parts: executing /etc/kernel/postinst.d/initramfs-tools 3.13.0-85-generic 
/boot/vmlinuz-3.13.0-85-generic
update-initramfs: Generating /boot/initrd.img-3.13.0-85-generic
WARNING: missing /lib/modules/3.13.0-85-generic
Ensure all necessary drivers are built into the linux image!
depmod: ERROR: could not open directory /lib/modules/3.13.0-85-generic: No such 
file or directory
depmod: FATAL: could not search modules: No such file or directory
cryptsetup: WARNING: failed to detect canonical device of /dev/nfs
cryptsetup: WARNING: could not determine root device from /etc/fstab
cp: cannot stat 
'/usr/lib/x86_64-linux-gnu/pango/1.6.0/module-files.d/libpango1.0-0.modules': 
No such file or directory
E: /usr/share/initramfs-tools/hooks/plymouth failed with return 1.
update-initramfs: failed for /boot/initrd.img-3.13.0-85-generic with 1.
run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
dpkg: error processing package linux-image-extra-3.13.0-85-generic (--remove):
 subprocess installed post-removal script returned error exit status 1
Errors were encountered while processing:
 linux-image-extra-3.13.0-85-generic
E: Sub-process /usr/bin/dpkg returned an error code (1)

Turns out this was directly caused by simplistic checking in the
plymouth initramfs-tools hook:

# wheezy
if ls /usr/lib/x86_64-linux-gnu/pango/1* > /dev/null 2>&1

I want back and checked a backup of my original Trusty filesystem, and
it indeed has an empty hierarchy here:

  kiko@gasolinux:/usr/lib/x86_64-linux-gnu/pango$ ls -lR
  .:
  total 4
  drwxr-xr-x 3 root root 4096 Feb 26  2014 1.6.0/

  ./1.6.0:
  total 4
  drwxr-xr-x 2 root root 4096 Feb 27  2014 modules/

  ./1.6.0/modules:
  total 0

This may be better handled by smarter code in the plymouth hook, or if
the empty directory may have further consequences, by making the pango
upgrade really clean up that directory.

I solved the problem by removing the hierarchy and re-running apt-get -f
install.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: libpango1.0-0 1.36.3-1ubuntu1.1
ProcVersionSignature: Ubuntu 3.13.0-87.133-generic 3.13.11-ckt39
Uname: Linux 3.13.0-87-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.21
Architecture: amd64
CurrentDesktop: Unity
Date: Sun Jun  5 20:45:27 2016
SourcePackage: pango1.0
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: pango1.0 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug trusty ubuntu-une

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

Title:
  Upgrading to Xenial leaves empty /usr/lib/x86_64-linux-gnu/pango/
  hierarchy

Status in pango1.0 package in Ubuntu:
  New

Bug description:
  During an upgrade from a Trusty system to Xenial, I ended up with the
  following problem:

  Removing linux-image-extra-3.13.0-85-generic (3.13.0-85.129) ...
  depmod: FATAL: could not load /boot/System.map-3.13.0-85-generic: No such 
file or directory
  run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 
3.13.0-85-generic /boot/vmlinuz-3.13.0-85-generic
  run-parts: executing /etc/kernel/postinst.d/initramfs-tools 3.13.0-85-generic 
/boot/vmlinuz-3.13.0-85-generic
  update-initramfs: Generating /boot/initrd.img-3.13.0-85-generic
  WARNING: missing /lib/modules/3.13.0-85-generic
  Ensure all necessary drivers are built into the linux image!
  depmod: ERROR: could not open directory /lib/modules/3.13.0-85-generic: No 
such file or directory
  depmod: FATAL: could not search modules: No such file or directory
  cryptsetup: WARNING: failed to detect canonical device of /dev/nfs
  cryptsetup: WARNING: could not determine root device from /etc/fstab
  cp: cannot stat 
'/usr/lib/x86_64-linux-gnu/pango/1.6.0/module-files.d/libpango1.0-0.modules': 
No such file or directory
  E: /usr/share/initramfs-tools/hooks/plymouth failed with return 1.
  update-initramfs: failed for /boot/initrd.img-3.13.0-85-generic with 1.
  run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
  dpkg: error processing package linux-image-extra-3.13.0-85-generic (--remove):
   subprocess installed post-removal script returned error exit status 1
  Errors were encountered while processing:
   linux-image-extra-3.13.0-85-generic
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  Turns out this was directly caused by simplistic checking in the
  plymouth initramfs-tools hook:

  # wheezy
  if ls 

[Touch-packages] [Bug 1589316] [NEW] Audio keeps muting. Compaq nc2400. Ubuntu 16.04

[Tony Walker]

Public bug reported:

The audio keeps muting on a Compaq nc2400. In running Ubuntu 16.04.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
Uname: Linux 4.4.0-22-generic i686
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: i386
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  tony   1594 F pulseaudio
CurrentDesktop: Unity
Date: Mon Jun  6 00:25:27 2016
InstallationDate: Installed on 2016-06-05 (0 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel failed
Symptom_Card: Built-in Audio - HDA Intel
Symptom_Jack: Green Speaker, Internal
Symptom_Type: None of the above
Title: [HP Compaq nc2400(#ABU), Analog Devices AD1981, Green Speaker, Internal] 
Playback problem
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/22/2006
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: 68YOP Ver. F.06
dmi.board.name: 30A1
dmi.board.vendor: Hewlett-Packard
dmi.board.version: KBC Version 53.13
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68YOPVer.F.06:bd09/22/2006:svnHewlett-Packard:pnHPCompaqnc2400(#ABU):pvrF.06:rvnHewlett-Packard:rn30A1:rvrKBCVersion53.13:cvnHewlett-Packard:ct10:cvr:
dmi.product.name: HP Compaq nc2400(#ABU)
dmi.product.version: F.06
dmi.sys.vendor: Hewlett-Packard

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


** Tags: apport-bug i386 xenial

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

Title:
  Audio keeps muting. Compaq nc2400. Ubuntu 16.04

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  The audio keeps muting on a Compaq nc2400. In running Ubuntu 16.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic i686
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tony   1594 F pulseaudio
  CurrentDesktop: Unity
  Date: Mon Jun  6 00:25:27 2016
  InstallationDate: Installed on 2016-06-05 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel failed
  Symptom_Card: Built-in Audio - HDA Intel
  Symptom_Jack: Green Speaker, Internal
  Symptom_Type: None of the above
  Title: [HP Compaq nc2400(#ABU), Analog Devices AD1981, Green Speaker, 
Internal] Playback problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/22/2006
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68YOP Ver. F.06
  dmi.board.name: 30A1
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 53.13
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68YOPVer.F.06:bd09/22/2006:svnHewlett-Packard:pnHPCompaqnc2400(#ABU):pvrF.06:rvnHewlett-Packard:rn30A1:rvrKBCVersion53.13:cvnHewlett-Packard:ct10:cvr:
  dmi.product.name: HP Compaq nc2400(#ABU)
  dmi.product.version: F.06
  dmi.sys.vendor: Hewlett-Packard

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1589316/+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 1578927] Re: idle crashes on configure through menu

[Launchpad Bug Tracker]

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: python2.7 (Ubuntu Xenial)
   Status: New => Confirmed

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

Title:
  idle crashes on configure through menu

Status in Python:
  Fix Released
Status in python2.7 package in Ubuntu:
  Fix Released
Status in python2.7 source package in Xenial:
  Confirmed

Bug description:
  IDLE crashes when "Configure IDLE" is selected through "Options".
  Terminal output is as follows:

  Exception in Tkinter callback
  Traceback (most recent call last):
File "/usr/lib/python2.7/lib-tk/Tkinter.py", line 1540, in __call__
  return self.func(*args)
File "/usr/lib/python2.7/idlelib/EditorWindow.py", line 543, in 
config_dialog
  configDialog.ConfigDialog(self.top,'Settings')
File "/usr/lib/python2.7/idlelib/configDialog.py", line 72, in __init__
  self.LoadConfigs()
File "/usr/lib/python2.7/idlelib/configDialog.py", line 1103, in LoadConfigs
  self.LoadFontCfg()
File "/usr/lib/python2.7/idlelib/configDialog.py", line 1005, in LoadFontCfg
  self.SetFontSample()
File "/usr/lib/python2.7/idlelib/configDialog.py", line 883, in 
SetFontSample
  self.labelFontSample.config(font=newFont)
File "/usr/lib/python2.7/lib-tk/Tkinter.py", line 1329, in configure
  return self._configure('configure', cnf, kw)
File "/usr/lib/python2.7/lib-tk/Tkinter.py", line 1320, in _configure
  self.tk.call(_flatten((self._w, cmd)) + self._options(cnf))
  TclError: expected integer but got ""

  1) Ubuntu 16.04 LTS
  2) Package idle 2.7.11-1
  3) Expected Options Menu
  4) Instead nothing happened.

To manage notifications about this bug go to:
https://bugs.launchpad.net/python/+bug/1578927/+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 1582461] Re: IDLE crashes when "Configure IDLE" is selected through "Options". Terminal output is as follows:

[Matthias Klose]

*** This bug is a duplicate of bug 1578927 ***
https://bugs.launchpad.net/bugs/1578927

** Also affects: python2.7 (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** This bug has been marked a duplicate of bug 1578927
   idle crashes on configure through menu

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

Title:
  IDLE crashes when "Configure IDLE" is selected through "Options".
  Terminal output is as follows:

Status in python2.7 package in Ubuntu:
  New
Status in python2.7 source package in Xenial:
  New

Bug description:
  using xubuntu 16.04 LTS

  IDLE3 crashes when "Configure IDLE" is selected through "Options".
  Terminal output is as follows:

  Exception in Tkinter callback
  Traceback (most recent call last):
File "/usr/lib/python3.5/tkinter/__init__.py", line 1553, in __call__
  return self.func(*args)
File "/usr/lib/python3.5/idlelib/EditorWindow.py", line 516, in 
config_dialog
  configDialog.ConfigDialog(self.top,'Settings')
File "/usr/lib/python3.5/idlelib/configDialog.py", line 74, in __init__
  self.LoadConfigs()
File "/usr/lib/python3.5/idlelib/configDialog.py", line 1086, in LoadConfigs
  self.LoadFontCfg()
File "/usr/lib/python3.5/idlelib/configDialog.py", line 988, in LoadFontCfg
  self.SetFontSample()
File "/usr/lib/python3.5/idlelib/configDialog.py", line 866, in 
SetFontSample
  self.labelFontSample.config(font=newFont)
File "/usr/lib/python3.5/tkinter/__init__.py", line 1333, in configure
  return self._configure('configure', cnf, kw)
File "/usr/lib/python3.5/tkinter/__init__.py", line 1324, in _configure
  self.tk.call(_flatten((self._w, cmd)) + self._options(cnf))
  _tkinter.TclError: expected integer but got ""

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/1582461/+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 1580577] Re: python2.7 crashes with SegFault when running Zope

[Matthias Klose]

looks to be fixed in yakkety

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

Title:
  python2.7 crashes with SegFault when running Zope

Status in python2.7 package in Ubuntu:
  Confirmed

Bug description:
  Source package / Package:

  python2.7_2.7.11-7ubuntu1

  System:

  Description:  Ubuntu 16.04 LTS
  Release:  16.04

  
  This is a bug report originating from the findings documented in

  https://github.com/zopefoundation/Zope/issues/56

  
  The expected behaviour is this:
  - Upon installing Zope2 in a virtualenv a default instance should work with 
no issues.

  What happens instead:
  - The freshly installed Zope instance causes Python to SegFault after only a 
few requests.

  But Python should never SegFault.

  
  The following program produces the error:

  
  #!/bin/bash
  set -e

  # Call this testing script with an argument "setup" for the first time
  # to build the testing case
  #
  # After that, the script only performs the test as described below.
  #
  # Requirements: apt-get install virtualenv python2.7-dbg
  #
  # This script needs internet access when running.

  # The python version to test:
  python=/usr/bin/python2.7-dbg

  # This part builds the testing environment

  if [ "$1" == "setup" ] ; then
  # Virtual environment with the chosen python 
  virtualenv --python ${python} --no-site-packages zope-virtualenv
  cd zope-virtualenv
  # Basic Zope installation
  ./bin/easy_install -i http://download.zope.org/Zope2/index/2.13.24 Zope2
  # Simplest possible Zope instance
  ./bin/mkzopeinstance --dir instance --user admin:admin
  cd ..
  fi

  # THE TEST

  # Run Zope instance in the background
  zope-virtualenv/instance/bin/runzope &

  # Give Zope some time to start up
  sleep 3

  # Call a few management URLs, nothing too fancy...
  urls="
  http://admin:admin@localhost:8080/Control_Panel/manage_main
  http://admin:admin@localhost:8080/Control_Panel/Database/main/manage_main
  http://admin:admin@localhost:8080/Control_Panel/Database/manage_main
  http://admin:admin@localhost:8080/Control_Panel/Database/main/manage_activity
  http://admin:admin@localhost:8080/manage
  http://admin:admin@localhost:8080/acl_users/manage_main
  http://admin:admin@localhost:8080/acl_users/manage_access
  "

  while true ; do
  for url in ${urls} ; do 
echo ${url}
  curl -s $url -o /dev/null
  done
  done

  # This test fails after about 10 requests with
  # Fatal Python error: ../Objects/descrobject.c:10 object at 0x??? has 
negative ref count -1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/1580577/+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 1589288] Re: python3.4 package missing threading module in trusty-security

[Mathew Hodson]

** Changed in: python3.4 (Ubuntu)
   Importance: Undecided => High

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

Title:
  python3.4 package missing threading module in trusty-security

Status in python3.4 package in Ubuntu:
  New

Bug description:
  Someone forgot to add threading.py module in
  libpython3.4-mininal_3.4.0-2ubuntu1.1 package. I fail when trying to
  work with python3.4 in trusty-security environment.

  How to reproduce:
  1. Install new Ubuntu Trusty WITHOUT online updates or downgrade all packages 
to trusty-security.
  2. Disable *-updates repositories, update apt cache:
  # sed -i -e'/-updates/s/^/# /' /etc/apt/sources.list && apt-get update
  3. Upgrade python3 packages:
  # apt-get install python3 python3-minimal python3.4 python3.4-minimal 
libpython3.4-minimal libpython3.4-stdlib
  4. Try to import threading module (will fail):
  # python3 -c 'import threading'
  Traceback (most recent call last):
    File "", line 1, in 
  ImportError: No module named 'threading'

  Without threading.py `pip3 install` and `add-apt-repository` will
  fail. Extended terminal output (including apt-cache policy) is in
  python3.4_trusty_bug_terminal_output.txt . This problem has occured in
  https://bugs.launchpad.net/ubuntu/+source/python3.4/+bug/1503382/comments/4
  , but hasn't been articulated or resolved.

  I compared packages in security and updates and found significant 
differencies:
  1. [debian/pymindeps.py] subprocess key in excluded_imports is threading in 
security and dummy_threading in updates.
  2. [debian/PVER-minimal.README.Debian.in] Information about threading module 
differs.

  I make patch libpython3.4-minimal_3.4.0-2ubuntu1.1custompatch1.patch
  and applied to python3.4_3.4.0-2ubuntu1.1 . The result is available in
  https://launchpad.net/~bugchecker/+archive/ubuntu/python3-threading-
  trusty-sec . This patch may be incorrect but it works for me.

  Also I attached docker context for any experiments.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python3.4/+bug/1589288/+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 1503382] Re: unable to install python3.4 dev on fresh ubuntu cloud image

[Mathew Hodson]

** Information type changed from Public Security to Public

** No longer affects: amulet (Ubuntu)

** Changed in: python3.4 (Ubuntu)
   Importance: Undecided => High

** Tags added: regression-update

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

Title:
  unable to install python3.4 dev on fresh ubuntu cloud image

Status in python3.4 package in Ubuntu:
  Confirmed

Bug description:
  Latest cloud ubuntu trusty image (06-Oct-2015 10:34)  https://cloud-
  images.ubuntu.com/trusty/current/

  apt-get update && apt-get upgrade # works fine

  # apt-get install python3.4-dev
  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  Some packages could not be installed. This may mean that you have
  requested an impossible situation or if you are using the unstable
  distribution that some required packages have not yet been created
  or been moved out of Incoming.
  The following information may help to resolve the situation:

  The following packages have unmet dependencies:
   python3.4-dev : Depends: python3.4 (= 3.4.0-2ubuntu1.1) but 
3.4.3-1ubuntu1~14.04.1 is to be installed
   Depends: libpython3.4-dev (= 3.4.0-2ubuntu1.1) but it is not 
going to be installed
   Depends: libpython3.4 (= 3.4.0-2ubuntu1.1) but it is not 
going to be installed
  E: Unable to correct problems, you have held broken packages.

  # apt-get install libpython3.4-dev
  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  Some packages could not be installed. This may mean that you have
  requested an impossible situation or if you are using the unstable
  distribution that some required packages have not yet been created
  or been moved out of Incoming.
  The following information may help to resolve the situation:

  The following packages have unmet dependencies:
   libpython3.4-dev : Depends: libpython3.4-stdlib (= 3.4.0-2ubuntu1.1) but 
3.4.3-1ubuntu1~14.04.1 is to be installed
  Depends: libpython3.4 (= 3.4.0-2ubuntu1.1) but it is not 
going to be installed
  E: Unable to correct problems, you have held broken packages.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: python3.4-dev (not installed)
  ProcVersionSignature: Ubuntu 3.13.0-65.105-generic 3.13.11-ckt26
  Uname: Linux 3.13.0-65-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.15
  Architecture: amd64
  Date: Tue Oct  6 17:36:17 2015
  SourcePackage: python3.4
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python3.4/+bug/1503382/+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 1493999] Re: xz-utils package is really, really old and should be updated to 5.2.2 with multi-core support

[Mathew Hodson]

** Bug watch removed: Debian Bug tracker #777267
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=777267

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

Title:
  xz-utils package is really, really old and should be updated to 5.2.2
  with multi-core support

Status in xz-utils package in Ubuntu:
  Triaged
Status in xz-utils package in Debian:
  New

Bug description:
  Willy is currently using a really old version of xz-utils. The latest
  version at this time is 5.2.2, released in September 2015.  With
  multi-core support it adds an important feature for xz.

  http://git.tukaani.org/?p=xz.git;a=blob;f=NEWS;hb=HEAD

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xz-utils/+bug/1493999/+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 1585710] Re: package libsystemd0:amd64 229-4ubuntu6 failed to install/upgrade: Paket libsystemd0:amd64 kann nicht konfiguriert werden, da libsystemd0:i386 nicht bereit ist (aktue

[Julian Andres Klode]

I think the bug submitter just broke his system, the log just started
with the error message; and it was perfectly fine in the previous run,
just look a few lines above and you see:

Setting up libsystemd0:amd64 (229-4ubuntu6) ...
Setting up libsystemd0:i386 (229-4ubuntu6) ...
Setting up systemd (229-4ubuntu6) ...

So, without further input, I can't say anything about this.

Furthermore, apt's history log only shows the command and what started
it, but does not get any further.

It would be a good idea to get the dpkg.log file, that contains the
actual dpkg logs (status changes, etc). Then we can see when it broke,
but it does not look like apt broke it.

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

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

Title:
  package libsystemd0:amd64 229-4ubuntu6 failed to install/upgrade:
  Paket libsystemd0:amd64 kann nicht konfiguriert werden, da
  libsystemd0:i386 nicht bereit ist (aktueller Status »half-installed«)

Status in apt package in Ubuntu:
  Incomplete

Bug description:
  Error occurred while apt upgrade

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libsystemd0:amd64 229-4ubuntu6
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  AptOrdering:
   libsystemd0: Configure
   libsystemd0: Configure
   NULL: ConfigurePending
  Architecture: amd64
  Date: Wed May 25 18:33:53 2016
  ErrorMessage: Paket libsystemd0:amd64 kann nicht konfiguriert werden, da 
libsystemd0:i386 nicht bereit ist (aktueller Status »half-installed«)
  InstallationDate: Installed on 2016-04-29 (26 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.10ubuntu1
  SourcePackage: systemd
  Title: package libsystemd0:amd64 229-4ubuntu6 failed to install/upgrade: 
Paket libsystemd0:amd64 kann nicht konfiguriert werden, da libsystemd0:i386 
nicht bereit ist (aktueller Status »half-installed«)
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1585710/+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 1357093] Re: Kernels not autoremoving, causing out of space error on LVM or Encrypted installation or on any installation, when /boot partition gets full

[Jarno Suni]

50unattended-upgrades does not contain mention for Unattended-Upgrade
::Remove-New-Unused-Dependencies, but the default value is true.
Automatic installing of security updates is enabled by default in
Xenial.

** Attachment added: "Default /eta/apt//apt.conf.d/50unattended-upgrades for 
Xenial"
   
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1357093/+attachment/4677670/+files/50unattended-upgrades

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

Title:
  Kernels not autoremoving, causing out of space error on LVM or
  Encrypted installation or on any installation, when /boot partition
  gets full

Status in unattended-upgrades package in Ubuntu:
  Fix Committed

Bug description:
  Currently if one chooses to use LVM or encrypted install, a /boot
  partition is created of 236Mb

  Once kernel updates start being released this partition soon fills
  until people are left unable to upgrade.

  While you and I might know that we need to watch partition space, many
  of the people we have installing think that a windows disk is a disk
  and not a partition, education is probably the key - but in the
  meantime support venues keep needing to deal with the fact the
  partition is too small and/or old kernels are not purged as new ones
  install.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1357093/+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 1589310] [NEW] dhcp6 renewing lease every 10 to 15 seconds

[James Bainter]

Public bug reported:

Ubuntu 16.04 Desktop Linux 4.2.0-22-generic #27-Ubuntu SMP Thu Dec 17
22:57:08 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux

I would expect dhcp6 to act the same as dhcp (ip4) and not have such a
short lease period.

Following from /var/log/syslog

Jun  5 15:13:44 powder dbus[777]: [system] Activating via systemd: service 
name='org.freedesktop.nm_dispatcher' 
unit='dbus-org.freedesktop.nm-dispatcher.service'
Jun  5 15:13:44 powder systemd[1]: Starting Network Manager Script Dispatcher 
Service...
Jun  5 15:13:44 powder dbus[777]: [system] Successfully activated service 
'org.freedesktop.nm_dispatcher'
Jun  5 15:13:44 powder systemd[1]: Started Network Manager Script Dispatcher 
Service.
Jun  5 15:13:44 powder nm-dispatcher: req:1 'dhcp6-change' [eth0]: new request 
(1 scripts)
Jun  5 15:13:44 powder nm-dispatcher: req:1 'dhcp6-change' [eth0]: start 
running ordered scripts...
Jun  5 15:13:59 powder dhclient[1112]: PRC: Renewing lease on eth0.
Jun  5 15:13:59 powder dhclient[1112]: XMT: Renew on eth0, interval 9200ms.
Jun  5 15:13:59 powder dhclient[1112]: RCV: Reply message on eth0 from 
fe80::a62b:8cff:fe27:64b3.
Jun  5 15:13:59 powder NetworkManager[876]:   [1465164839.6471]   
valid_lft 60
Jun  5 15:13:59 powder NetworkManager[876]:   [1465164839.6471]   
preferred_lft 30
Jun  5 15:13:59 powder NetworkManager[876]:   [1465164839.6471]   address 
2600:8800:6202:6000:4637:e6ff:fe76:ed7b
Jun  5 15:13:59 powder NetworkManager[876]:   [1465164839.6472]   
nameserver '2001:578:3f::30'
Jun  5 15:13:59 powder NetworkManager[876]:   [1465164839.6472]   
nameserver '2001:578:3f:1::30'
Jun  5 15:13:59 powder NetworkManager[876]:   [1465164839.6472] dhcp6 
(eth0): state changed bound -> bound, event ID="e6:76:ed:7b|1465164839"
Jun  5 15:13:59 powder dbus[777]: [system] Activating via systemd: service 
name='org.freedesktop.nm_dispatcher' 
unit='dbus-org.freedesktop.nm-dispatcher.service'
Jun  5 15:13:59 powder systemd[1]: Starting Network Manager Script Dispatcher 
Service...
Jun  5 15:13:59 powder dbus[777]: [system] Successfully activated service 
'org.freedesktop.nm_dispatcher'
Jun  5 15:13:59 powder systemd[1]: Started Network Manager Script Dispatcher 
Service.
Jun  5 15:13:59 powder nm-dispatcher: req:1 'dhcp6-change' [eth0]: new request 
(1 scripts)
Jun  5 15:13:59 powder nm-dispatcher: req:1 'dhcp6-change' [eth0]: start 
running ordered scripts...
Jun  5 15:14:14 powder dhclient[1112]: PRC: Renewing lease on eth0.
Jun  5 15:14:14 powder dhclient[1112]: XMT: Renew on eth0, interval 9340ms.
Jun  5 15:14:14 powder dhclient[1112]: RCV: Reply message on eth0 from 
fe80::a62b:8cff:fe27:64b3.
Jun  5 15:14:14 powder NetworkManager[876]:   [1465164854.7043]   
valid_lft 60
Jun  5 15:14:14 powder NetworkManager[876]:   [1465164854.7044]   
preferred_lft 30
Jun  5 15:14:14 powder NetworkManager[876]:   [1465164854.7044]   address 
2600:8800:6202:6000:4637:e6ff:fe76:ed7b
Jun  5 15:14:14 powder NetworkManager[876]:   [1465164854.7044]   
nameserver '2001:578:3f::30'
Jun  5 15:14:14 powder NetworkManager[876]:   [1465164854.7044]   
nameserver '2001:578:3f:1::30'
Jun  5 15:14:14 powder NetworkManager[876]:   [1465164854.7044] dhcp6 
(eth0): state changed bound -> bound, event ID="e6:76:ed:7b|1465164854"
Jun  5 15:14:14 powder dbus[777]: [system] Activating via systemd: service 
name='org.freedesktop.nm_dispatcher' 
unit='dbus-org.freedesktop.nm-dispatcher.service'
Jun  5 15:14:14 powder systemd[1]: Starting Network Manager Script Dispatcher 
Service...
Jun  5 15:14:14 powder dbus[777]: [system] Successfully activated service 
'org.freedesktop.nm_dispatcher'

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

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

Title:
  dhcp6 renewing lease every 10 to 15 seconds

Status in network-manager package in Ubuntu:
  New

Bug description:
  Ubuntu 16.04 Desktop Linux 4.2.0-22-generic #27-Ubuntu SMP Thu Dec 17
  22:57:08 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux

  I would expect dhcp6 to act the same as dhcp (ip4) and not have such a
  short lease period.

  Following from /var/log/syslog

  Jun  5 15:13:44 powder dbus[777]: [system] Activating via systemd: service 
name='org.freedesktop.nm_dispatcher' 
unit='dbus-org.freedesktop.nm-dispatcher.service'
  Jun  5 15:13:44 powder systemd[1]: Starting Network Manager Script Dispatcher 
Service...
  Jun  5 15:13:44 powder dbus[777]: [system] Successfully activated service 
'org.freedesktop.nm_dispatcher'
  Jun  5 15:13:44 powder systemd[1]: Started Network Manager Script Dispatcher 
Service.
  Jun  5 15:13:44 powder nm-dispatcher: req:1 'dhcp6-change' [eth0]: new 
request (1 scripts)
  Jun  5 15:13:44 powder nm-dispatcher: req:1 'dhcp6-change' [eth0]: start 
running ordered scripts...
  Jun  5 15:13:59 powder dhclient[1112]: PRC: Renewing lease on 

[Touch-packages] [Bug 1539158] Re: Unable to pair with in-car hands-free system after OTA-9 update

[Stunts]

I didn't get to try the silo.
After your comment, I found this very strange and took a better look:

Before, I used to wait for the car to find the phone, and after being
found the car requested me to enter  in the phone for pairing (which
failed immediately).

What is occurring now, is that the car is asking me to use the phone to
find the bluetooth system, which the phone does without any trouble, and
after that, the pairing is automatic.

I will try to reproduce the previous conditions and report back.

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

Title:
  Unable to pair with in-car hands-free system after OTA-9 update

Status in Canonical System Image:
  In Progress
Status in bluez package in Ubuntu:
  Confirmed
Status in ubuntu-system-settings package in Ubuntu:
  In Progress

Bug description:
  After OTA-9 I started having trouble with my bluetooth connection to the car 
hands-free system (no sound, and incoming calls no longer displayed the 
number), so I have reset both the car and the phone connections (eg. forgot the 
devices).
  Now I can't even pair the phone with the car's system. 
  The car finds the phone, and then asks me to enter the code "" to pair 
the device, but after a few moments, it just says the connection failed and 
asks me to try again. Which fails again.

  It was working fine just before the update.

  Any logs I should post to help debug?

  PS - The car is a 2015 Honda Civic Tourer, if that matters.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1539158/+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 1586223] Re: Xorg crash in Ubuntu 16.04 with Nvidia driver

[Lanoxx]

I have the same issue, about every second time when I resume from
suspend then Xorg crashes and I am returned to the ligthdm login screen.
I have alle the recent updates and I also already upgraded to the latest
nvidia driver without success. This is really annoying because every
time this happens I am loosing my session state.

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

Title:
  Xorg crash in Ubuntu 16.04 with Nvidia driver

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  The crash seems to be happening when waking up from sleep.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  361.42  Tue Mar 22 18:10:58 
PDT 2016
   GCC version:  gcc version 5.3.1 20160413 (Ubuntu 5.3.1-14ubuntu2)
  .tmp.unity_support_test.0:

  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Fri May 27 07:15:29 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.4.0-21-generic, x86_64: installed
   bbswitch, 0.8, 4.4.0-22-generic, x86_64: installed
   nvidia-361, 361.42, 4.4.0-21-generic, x86_64: installed
   nvidia-361, 361.42, 4.4.0-22-generic, x86_64: installed
   vboxhost, 5.0.20, 4.4.0-22-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
     Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:21f5]
   NVIDIA Corporation GF108M [NVS 5400M] [10de:0def] (rev a1) (prog-if 00 [VGA 
controller])
     Subsystem: Lenovo GF108M [NVS 5400M] [17aa:21f5]
  InstallationDate: Installed on 2016-04-22 (34 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: LENOVO 2394EL9
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic.efi.signed 
root=UUID=7c2f9dd3-98f1-4414-8d69-2a7921ebceb8 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/31/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G4ETA4WW (2.64 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2394EL9
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG4ETA4WW(2.64):bd03/31/2015:svnLENOVO:pn2394EL9:pvrThinkPadT530:rvnLENOVO:rn2394EL9:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 2394EL9
  dmi.product.version: ThinkPad T530
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Thu May 26 22:55:53 2016
  xserver.configfile: /etc/X11/xorg.conf
  xserver.errors:

  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.3-1ubuntu2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1586223/+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 1586223] Re: Xorg crash in Ubuntu 16.04 with Nvidia driver

[Launchpad Bug Tracker]

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: xorg (Ubuntu)
   Status: New => Confirmed

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

Title:
  Xorg crash in Ubuntu 16.04 with Nvidia driver

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  The crash seems to be happening when waking up from sleep.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  361.42  Tue Mar 22 18:10:58 
PDT 2016
   GCC version:  gcc version 5.3.1 20160413 (Ubuntu 5.3.1-14ubuntu2)
  .tmp.unity_support_test.0:

  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Fri May 27 07:15:29 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.4.0-21-generic, x86_64: installed
   bbswitch, 0.8, 4.4.0-22-generic, x86_64: installed
   nvidia-361, 361.42, 4.4.0-21-generic, x86_64: installed
   nvidia-361, 361.42, 4.4.0-22-generic, x86_64: installed
   vboxhost, 5.0.20, 4.4.0-22-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
     Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:21f5]
   NVIDIA Corporation GF108M [NVS 5400M] [10de:0def] (rev a1) (prog-if 00 [VGA 
controller])
     Subsystem: Lenovo GF108M [NVS 5400M] [17aa:21f5]
  InstallationDate: Installed on 2016-04-22 (34 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: LENOVO 2394EL9
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic.efi.signed 
root=UUID=7c2f9dd3-98f1-4414-8d69-2a7921ebceb8 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/31/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G4ETA4WW (2.64 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2394EL9
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG4ETA4WW(2.64):bd03/31/2015:svnLENOVO:pn2394EL9:pvrThinkPadT530:rvnLENOVO:rn2394EL9:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 2394EL9
  dmi.product.version: ThinkPad T530
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Thu May 26 22:55:53 2016
  xserver.configfile: /etc/X11/xorg.conf
  xserver.errors:

  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.3-1ubuntu2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1586223/+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 1589255] Re: Double login screen In desktop

[kevin gunn]

we're aware, it's a feature being worked on

** No longer affects: mir

** Also affects: canonical-devices-system-image
   Importance: Undecided
   Status: New

** Changed in: canonical-devices-system-image
   Importance: Undecided => High

** Changed in: unity8 (Ubuntu)
   Importance: Undecided => High

** Changed in: unity8 (Ubuntu)
 Assignee: (unassigned) => Michael Terry (mterry)

** Changed in: canonical-devices-system-image
 Assignee: (unassigned) => Michał Sawicz (saviq)

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

Title:
  Double login screen In desktop

Status in Canonical System Image:
  New
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  when I turn on the PC and choose unity8 from the login screen I enter the 
password, once entered the password and after that it is loaded unity8 I again 
put the password in the login screen unity8. It should happen as in Unity 7 in 
which you enter directly without having to put your password
  Ubuntu 16.10(daily build)
  Unity8.12+16.10.20160527

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1589255/+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 1586379] Re: Microphone not working on MacBookpro 15 (version 8.2) and Xubuntu 16.04

[Alejandro Comisario]

Hi, any help ?

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

Title:
  Microphone not working on MacBookpro 15 (version 8.2) and Xubuntu
  16.04

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  I have a Macbook pro 15 (version 8.2) with Xubuntu 14.04 the mic
  worked out of the box, with xubuntu 16.04

  * upgraded from 14.04
  * fresh install

  The mic does'nt get any signal, i have tried these:
  
http://askubuntu.com/questions/482626/microphone-not-working-on-ubuntu-14-04-on-macbookpro10-2

  with no luck.

  the output of the command:
  wget -O alsa-info.sh http://www.alsa-project.org/alsa-info.sh && chmod +x 
./alsa-info.sh && ./alsa-info.sh

  is here:
  http://www.alsa-project.org/db/?f=1a18a2a3188be0c68d960ae4e6d8ec2ccacb994d

  if please can anyone help me ? 
  not being able to use the microphone is killing me.

  thank you !

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1586379/+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 1581270] Re: Hybrid Graphics: [drm:si_resume [radeon]] *ERROR* si startup failed on resume

[Levente Ábrók]

Don't know if it helps, but I ran DRI_PRIME=1 glxinfo|grep "OpenGL renderer". 
Seems like the only way to get some reaction from the dedicated one other than 
black screen.
Attached dmesg output about this.

** Attachment added: "dmesg.txt"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1581270/+attachment/4677612/+files/dmesg.txt

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

Title:
  Hybrid Graphics: [drm:si_resume [radeon]] *ERROR* si startup failed on
  resume

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  dmesg shows issues with being able to use the discrete graphics card
  (relevant dmesg lines attached).

  Grub does pass "radeon.modeset=1" but it doesn't seem to make a
  difference. If I pass both "radeon.modeset=1" and "radeon.startpm=1"to
  the kernel, then it does not error (except for the VCE error -110,
  which is probably harmless).

  Running `DRI_PRIME=1 glxgears`:
  - with "radeon.modeset=1" and "radeon.startpm=1", no error but only a black 
window with a visible top bar.
  - with just "radeon.modeset=1", error (attached as 'glxgears').

  Results are similar on Ubuntu GNOME 16.04, except with
  "radeon.modeset=1" and "radeon.startpm=1" set. It works, but lots of
  screen tearing.

  Attached are relevant dmesg lines, grep'd with 'drm'. I'll also be
  attaching entire contents of dmesg, /var/log/syslog, etc., but TLDR:

  [   22.916285] [drm] ring test on 0 succeeded in 2 usecs
  [   22.916289] [drm] ring test on 1 succeeded in 1 usecs
  [   22.916292] [drm] ring test on 2 succeeded in 1 usecs
  [   22.916299] [drm] ring test on 3 succeeded in 3 usecs
  [   22.916304] [drm] ring test on 4 succeeded in 3 usecs
  [   23.092271] [drm] ring test on 5 succeeded in 2 usecs
  [   23.092276] [drm] UVD initialized successfully.
  [   23.092311] [drm] ib test on ring 0 succeeded in 0 usecs
  [   23.092349] [drm] ib test on ring 1 succeeded in 0 usecs
  [   23.092375] [drm] ib test on ring 2 succeeded in 0 usecs
  [   23.092392] [drm] ib test on ring 3 succeeded in 0 usecs
  [   23.092407] [drm] ib test on ring 4 succeeded in 0 usecs
  [   33.241928] [drm:uvd_v1_0_ib_test [radeon]] *ERROR* radeon: fence wait 
failed (-35).
  [   33.241948] [drm:radeon_ib_ring_tests [radeon]] *ERROR* radeon: failed 
testing IB on ring 5 (-35).

  lsb_release -rd:
  Description:  Ubuntu 16.04 LTS
  Release:  16.04

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  .tmp.unity_support_test.0:

  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Thu May 12 20:43:03 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
     Subsystem: Samsung Electronics Co Ltd 3rd Gen Core processor Graphics 
Controller [144d:c0e6]
     Subsystem: Samsung Electronics Co Ltd Mars [Radeon HD 8670A/8670M/8750M] 
[144d:c0e6]
  InstallationDate: Installed on 2016-05-13 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 870Z5E/880Z5E/680Z5E
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic.efi.signed 
root=UUID=644ba363-51c7-419c-8544-2ff7be960f21 ro quiet splash radeon.modeset=1 
vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/21/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P05ADH.017.140421.SH
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: NP680Z5E-X01US
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: SEC_SW_REVISION_1234567890ABCD
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP05ADH.017.140421.SH:bd04/21/2014:svnSAMSUNGELECTRONICSCO.,LTD.:pn870Z5E/880Z5E/680Z5E:pvrP05ADH:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP680Z5E-X01US:rvrSEC_SW_REVISION_1234567890ABCD:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvrN/A:
  dmi.product.name: 870Z5E/880Z5E/680Z5E
  dmi.product.version: P05ADH
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
  version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
  

[Touch-packages] [Bug 1582823] Re: Text not rendering correctly after resume from suspend

[Christopher M. Penalver]

hackel, as per
http://support.toshiba.com/support/modelHome?freeText=127479 an
update to your computer's buggy, insecure, and outdated BIOS is
available (1.60). If you update to this following
https://help.ubuntu.com/community/BIOSUpdate does it change anything?

For more on BIOS updates and linux, please see
https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette
.

Please note your current BIOS is already in the Bug Description, so
posting this on the old BIOS would not be helpful.

Also, you don't have to create a new bug report.

Once the BIOS is updated, if the problem is still reproducible:
1) Please provide the output of the following terminal command (not perform an 
apport-collect):
sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date
2) Please make a comment specifically advising on if there was an improvement 
or not.
3) Please mark this report Status Confirmed.

If it's not reproducible, please mark this as Invalid.

Thank you for your understanding.

** No longer affects: gtk+3.0 (Ubuntu)

** Tags added: bios-outdated-1.60

** Changed in: linux (Ubuntu)
   Importance: High => Medium

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

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

Title:
  Text not rendering correctly after resume from suspend

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Since upgrading to 16.04, I've been experiencing frequent difficulties
  resuming from suspend, causing text not to be displayed at all, or
  wrong characters to be displayed.  Please see the attached
  screenshots.

  I don't know what part of the system this lies in.  It seems to affect
  all gtk apps at least.  Chromium renders just fine when this happens,
  other than the titlebar.  Similarly, Cool Retro Term renders
  correctly, which obviously doesn't use gtk, while Gnome Terminal and
  Guake do not.

  This suggests it could be related to framebuffer corruption, but this
  report was made with a much earlier kernel, and I had no such problems
  under 15.10.  http://askubuntu.com/questions/688306/text-missing-
  garbled-after-laptop-resumes-from-sleep-mode

  libgtk-3-0 3.18.9-1ubuntu3
  linux-image-4.4.0-22-generic 4.4.0-22.40
  xserver-xorg-core 2:1.18.3-1ubuntu2
  xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1

  lshw -c video
    *-display
     description: VGA compatible controller
     product: 4th Gen Core Processor Integrated Graphics Controller
     vendor: Intel Corporation
     physical id: 2
     bus info: pci@:00:02.0
     version: 06
     width: 64 bits
     clock: 33MHz
     capabilities: msi pm vga_controller bus_master cap_list rom
     configuration: driver=i915 latency=0
     resources: irq:30 memory:b200-b23f memory:a000-afff 
ioport:5000(size=64)

  dmesg | grep i915
  [1.383957] [drm] Initialized i915 1.6.0 20151010 for :00:02.0 on 
minor 0
  [1.534467] i915 :00:02.0: fb0: inteldrmfb frame buffer device
  [2.718041] [drm:intel_set_pch_fifo_underrun_reporting [i915]] *ERROR* 
uncleared pch fifo underrun on pch transcoder A
  [2.718060] [drm:intel_pch_fifo_underrun_irq_handler [i915]] *ERROR* PCH 
transcoder A FIFO underrun
  [2.733438] [drm:intel_set_cpu_fifo_underrun_reporting [i915]] *ERROR* 
uncleared fifo underrun on pipe B
  [2.733460] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU 
pipe B FIFO underrun
  [4.137698] snd_hda_intel :00:03.0: bound :00:02.0 (ops 
i915_audio_component_bind_ops [i915])
  [   66.585338] [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update 
failure on pipe A (start=4267 end=4268) time 282 us, min 1073, max 1079, 
scanline start 1059, end 1090
  [  277.577183] [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update 
failure on pipe B (start=16480 end=16481) time 363 us, min 894, max 899, 
scanline start 875, end 900
  [  284.581315] [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update 
failure on pipe B (start=16900 end=16901) time 358 us, min 894, max 899, 
scanline start 891, end 905
  [  300.589410] [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update 
failure on pipe A (start=18424 end=18425) time 210 us, min 1073, max 1079, 
scanline start 1070, end 1084
  [  302.574085] [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update 
failure on pipe A (start=18544 end=18545) time 338 us, min 1073, max 1079, 
scanline start 1061, end 1078
  [  470.560521] [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update 
failure on pipe A (start=28707 end=28708) time 301 us, min 1073, max 1079, 
scanline start 1071, end 1091
  [  595.553386] [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update 
failure on pipe A (start=36269 end=36270) time 107 us, min 1073, max 1079, 
scanline start 1056, end 1083
  [ 

[Touch-packages] [Bug 919801] Re: Unity dash file search is extremely slow

[Lars Ola Liavåg]

At last, a new Ubuntu release seems to have made a difference. With
Xenial, I'm down to a couple of seconds or less populating the Dash
first time on first login. I'm not sure if it's down to the new release
since I already had a startup command to preload selected scopes
according to Bruno Nova's suggestion under bug #1061852, and I guess the
startup job may hve survuved the upgrade:

/usr/bin/unity-scope-loader applications/applications.scope
applications/scopes.scope commands.scope

Nonetheless, under 15.10, this didn't work anywhere nearly as well as it
does in 16.04, so I guess the underlying problem has benefited from some
of the groundwork in the new release. Just out of curiosity, I'll
probably deactivate the startup job above to see what difference it
makes.

Anyway, having scope access times of less than two seconds on first
login has not happened to me since before 12.04, so finally, Unity 7
seems to reach its full potential - just in time for it to be replaced
by Unity 8...

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

Title:
  Unity dash file search is extremely slow

Status in unity-lens-files:
  Incomplete
Status in Zeitgeist Framework:
  Incomplete
Status in unity-lens-files package in Ubuntu:
  Confirmed
Status in zeitgeist package in Ubuntu:
  Fix Released

Bug description:
  When I try to use the Unity dash search feature to navigate to files
  and folders, it is extremely slow. For example, if I hit the super
  button to launch the search and then type "Pictures" to get my
  pictures directory, it takes almost 5 seconds for the folder icon to
  show. In comparison, if I use Gnome-Do to navigate to my Pictures
  folder, it's basically instant.

  I have attached a video screencast so that you can see the problem for 
yourself.
  --- 
  ApportVersion: 1.23-0ubuntu4
  Architecture: i386
  CompizPlugins: 
[core,bailer,detection,composite,opengl,compiztoolbox,decor,move,vpswitch,place,session,imgpng,mousepoll,resize,gnomecompat,regex,snap,grid,wall,unitymtgrabhandles,animation,expo,ezoom,workarounds,fade,scale,unityshell]
  DistroRelease: Ubuntu 11.10
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Beta i386 (20110413)
  NonfreeKernelModules: nvidia
  Package: unity 5.0.0~+bzr1825ubuntu0+611
  PackageArchitecture: i386
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 3.0.0-14.23-generic 3.0.9
  Tags:  oneiric running-unity
  Uname: Linux 3.0.0-14-generic i686
  UnreportableReason: This is not a genuine Ubuntu package
  UpgradeStatus: Upgraded to oneiric on 2011-10-14 (99 days ago)
  UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity-lens-files/+bug/919801/+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 1565100] Re: Support slovak language

[Launchpad Bug Tracker]

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: ubuntu-keyboard (Ubuntu)
   Status: New => Confirmed

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

Title:
  Support slovak language

Status in Canonical System Image:
  Triaged
Status in ubuntu-keyboard:
  New
Status in ubuntu-keyboard package in Ubuntu:
  Confirmed

Bug description:
  Please support to input slovak language from ubuntu-keyboard.

  can you review https://code.launchpad.net/~peto-bena/+junk/sk-keyboard
  ?

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1565100/+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 1589288] Re: python3.4 package missing threading module in trusty-security

[Ubuntu Foundations Team Bug Bot]

The attachment "libpython3.4-minimal_3.4.0-2ubuntu1.1custompatch1.patch"
seems to be a debdiff.  The ubuntu-sponsors team has been subscribed to
the bug report so that they can review and hopefully sponsor the
debdiff.  If the attachment isn't a patch, please remove the "patch"
flag from the attachment, remove the "patch" tag, and if you are member
of the ~ubuntu-sponsors, unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issue please contact him.]

** Tags added: patch

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

Title:
  python3.4 package missing threading module in trusty-security

Status in python3.4 package in Ubuntu:
  New

Bug description:
  Someone forgot to add threading.py module in
  libpython3.4-mininal_3.4.0-2ubuntu1.1 package. I fail when trying to
  work with python3.4 in trusty-security environment.

  How to reproduce:
  1. Install new Ubuntu Trusty WITHOUT online updates or downgrade all packages 
to trusty-security.
  2. Disable *-updates repositories, update apt cache:
  # sed -i -e'/-updates/s/^/# /' /etc/apt/sources.list && apt-get update
  3. Upgrade python3 packages:
  # apt-get install python3 python3-minimal python3.4 python3.4-minimal 
libpython3.4-minimal libpython3.4-stdlib
  4. Try to import threading module (will fail):
  # python3 -c 'import threading'
  Traceback (most recent call last):
    File "", line 1, in 
  ImportError: No module named 'threading'

  Without threading.py `pip3 install` and `add-apt-repository` will
  fail. Extended terminal output (including apt-cache policy) is in
  python3.4_trusty_bug_terminal_output.txt . This problem has occured in
  https://bugs.launchpad.net/ubuntu/+source/python3.4/+bug/1503382/comments/4
  , but hasn't been articulated or resolved.

  I compared packages in security and updates and found significant 
differencies:
  1. [debian/pymindeps.py] subprocess key in excluded_imports is threading in 
security and dummy_threading in updates.
  2. [debian/PVER-minimal.README.Debian.in] Information about threading module 
differs.

  I make patch libpython3.4-minimal_3.4.0-2ubuntu1.1custompatch1.patch
  and applied to python3.4_3.4.0-2ubuntu1.1 . The result is available in
  https://launchpad.net/~bugchecker/+archive/ubuntu/python3-threading-
  trusty-sec . This patch may be incorrect but it works for me.

  Also I attached docker context for any experiments.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python3.4/+bug/1589288/+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 1301015] Re: Networking does not restart

[Hayjumper]

Additionally, the ifdown/ifup method does not load certain changes (e.g.
IP address) properly, and often breaks networking when such changes are
made.

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

Title:
  Networking does not restart

Status in ifupdown package in Ubuntu:
  Confirmed

Bug description:
  In Ubuntu Server 14.04 it appears it is not possible to restart
  networking. This is fresh install from ISO.

  wirehive@ubuntu:~$ sudo /etc/init.d/networking restart
  wirehive@ubuntu:~$ echo $?
  1
  wirehive@ubuntu:~$ sudo service networking restart
  stop: Job failed while stopping
  start: Job is already running: networking
  wirehive@ubuntu:~$ sudo bash -x /etc/init.d/networking restart
  + PATH=/sbin:/bin
  + RUN_DIR=/run/network
  + IFSTATE=/run/network/ifstate
  + STATEDIR=/run/network/state
  + '[' -x /sbin/ifup ']'
  + '[' -x /sbin/ifdown ']'
  + . /lib/lsb/init-functions
  +++ run-parts --lsbsysinit --list /lib/lsb/init-functions.d
  ++ for hook in '$(run-parts --lsbsysinit --list /lib/lsb/init-functions.d 
2>/dev/null)'
  ++ '[' -r /lib/lsb/init-functions.d/20-left-info-blocks ']'
  ++ . /lib/lsb/init-functions.d/20-left-info-blocks
  ++ for hook in '$(run-parts --lsbsysinit --list /lib/lsb/init-functions.d 
2>/dev/null)'
  ++ '[' -r /lib/lsb/init-functions.d/50-ubuntu-logging ']'
  ++ . /lib/lsb/init-functions.d/50-ubuntu-logging
  +++ LOG_DAEMON_MSG=
  ++ FANCYTTY=
  ++ '[' -e /etc/lsb-base-logging.sh ']'
  ++ true
  + CONFIGURE_INTERFACES=yes
  + EXCLUDE_INTERFACES=
  + VERBOSE=no
  + '[' -f /etc/default/networking ']'
  + verbose=
  + '[' no = yes ']'
  + case "$1" in
  + init_is_upstart
  + '[' -x /sbin/initctl ']'
  + /bin/grep -q upstart
  + /sbin/initctl version
  + return 0
  + exit 1
  wirehive@ubuntu:~$ sudo bash -x service networking restart
  ++ basename service
  + VERSION='service ver. 0.91-ubuntu1'
  ++ basename service
  + USAGE='Usage: service < option > | --status-all | [ service_name [ command 
| --full-restart ] ]'
  + SERVICE=
  + ACTION=
  + SERVICEDIR=/etc/init.d
  + OPTIONS=
  + '[' 2 -eq 0 ']'
  + cd /
  + '[' 2 -gt 0 ']'
  + case "${1}" in
  + '[' -z '' -a 2 -eq 1 -a networking = --status-all ']'
  + '[' 2 -eq 2 -a restart = --full-restart ']'
  + '[' -z '' ']'
  + SERVICE=networking
  + shift
  + '[' 1 -gt 0 ']'
  + case "${1}" in
  + '[' -z networking -a 1 -eq 1 -a restart = --status-all ']'
  + '[' 1 -eq 2 -a '' = --full-restart ']'
  + '[' -z networking ']'
  + '[' -z '' ']'
  + ACTION=restart
  + shift
  + '[' 0 -gt 0 ']'
  + '[' -r /etc/init/networking.conf ']'
  + which initctl
  + grep -q upstart
  + initctl version
  + case "${ACTION}" in
  + stop networking
  stop: Job failed while stopping
  + :
  + exec start networking
  start: Job is already running: networking
  wirehive@ubuntu:~$

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1301015/+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 1581270] Re: Hybrid Graphics: [drm:si_resume [radeon]] *ERROR* si startup failed on resume

[Levente Ábrók]

Would like to join in on this bug.
I have a laptop with Intel Haswell and AMD Radeon HD 8850M / R9 M265X. I can't 
change to the dedicated GPU no matter how I try. My error messages in dmesg are 
basically the same as mentioned above.
Also, when I stop lightdm I get the title error: [drm:si_resume [radeon]] 
*ERROR* si startup failed on resume.
Using DIS on vgaswitcheroo file just gives me a black screen. I am on Ubuntu 
16.04.
Tried with the Grub parameters mentioned and without them. Still have the issue.

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

Title:
  Hybrid Graphics: [drm:si_resume [radeon]] *ERROR* si startup failed on
  resume

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  dmesg shows issues with being able to use the discrete graphics card
  (relevant dmesg lines attached).

  Grub does pass "radeon.modeset=1" but it doesn't seem to make a
  difference. If I pass both "radeon.modeset=1" and "radeon.startpm=1"to
  the kernel, then it does not error (except for the VCE error -110,
  which is probably harmless).

  Running `DRI_PRIME=1 glxgears`:
  - with "radeon.modeset=1" and "radeon.startpm=1", no error but only a black 
window with a visible top bar.
  - with just "radeon.modeset=1", error (attached as 'glxgears').

  Results are similar on Ubuntu GNOME 16.04, except with
  "radeon.modeset=1" and "radeon.startpm=1" set. It works, but lots of
  screen tearing.

  Attached are relevant dmesg lines, grep'd with 'drm'. I'll also be
  attaching entire contents of dmesg, /var/log/syslog, etc., but TLDR:

  [   22.916285] [drm] ring test on 0 succeeded in 2 usecs
  [   22.916289] [drm] ring test on 1 succeeded in 1 usecs
  [   22.916292] [drm] ring test on 2 succeeded in 1 usecs
  [   22.916299] [drm] ring test on 3 succeeded in 3 usecs
  [   22.916304] [drm] ring test on 4 succeeded in 3 usecs
  [   23.092271] [drm] ring test on 5 succeeded in 2 usecs
  [   23.092276] [drm] UVD initialized successfully.
  [   23.092311] [drm] ib test on ring 0 succeeded in 0 usecs
  [   23.092349] [drm] ib test on ring 1 succeeded in 0 usecs
  [   23.092375] [drm] ib test on ring 2 succeeded in 0 usecs
  [   23.092392] [drm] ib test on ring 3 succeeded in 0 usecs
  [   23.092407] [drm] ib test on ring 4 succeeded in 0 usecs
  [   33.241928] [drm:uvd_v1_0_ib_test [radeon]] *ERROR* radeon: fence wait 
failed (-35).
  [   33.241948] [drm:radeon_ib_ring_tests [radeon]] *ERROR* radeon: failed 
testing IB on ring 5 (-35).

  lsb_release -rd:
  Description:  Ubuntu 16.04 LTS
  Release:  16.04

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  .tmp.unity_support_test.0:

  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Thu May 12 20:43:03 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
     Subsystem: Samsung Electronics Co Ltd 3rd Gen Core processor Graphics 
Controller [144d:c0e6]
     Subsystem: Samsung Electronics Co Ltd Mars [Radeon HD 8670A/8670M/8750M] 
[144d:c0e6]
  InstallationDate: Installed on 2016-05-13 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 870Z5E/880Z5E/680Z5E
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic.efi.signed 
root=UUID=644ba363-51c7-419c-8544-2ff7be960f21 ro quiet splash radeon.modeset=1 
vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/21/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P05ADH.017.140421.SH
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: NP680Z5E-X01US
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: SEC_SW_REVISION_1234567890ABCD
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP05ADH.017.140421.SH:bd04/21/2014:svnSAMSUNGELECTRONICSCO.,LTD.:pn870Z5E/880Z5E/680Z5E:pvrP05ADH:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP680Z5E-X01US:rvrSEC_SW_REVISION_1234567890ABCD:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvrN/A:
  dmi.product.name: 870Z5E/880Z5E/680Z5E
  dmi.product.version: P05ADH
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
  version.compiz: compiz 

[Touch-packages] [Bug 1581719] Re: banshee aborts on horse-poo

[Martin Pitt]

** Package changed: systemd (Ubuntu) => banshee (Ubuntu)

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

Title:
  banshee aborts on horse-poo

Status in banshee package in Ubuntu:
  New

Bug description:
  plugging in a i(phone in this case) anything while listening to
  banshee causes internal failure, removal of device and banshee to
  abort.

  iirc, banshee should pick up the device.

  its a 5s.
  I have force disabled pulse and am on alsa. instructions for this are 
elsewhere. touche for this but pulse is as busted as gnome3.

  THIS SHOULD NOT HAPPEN.
  hardware is internal to the motherboard and REMOVAL NOTICES are beligerent 
and acinine and NONSENSE.
  NOTHING is REMOVED.
  ALC 889 INTEL driver on CrossHairV(mind you a known SIN board but..) MUST 
certainly be broken.

  also whist reporting this one:

  Unhandled Exception:
  System.ExecutionEngineException: Couldn't create thread
at (wrapper managed-to-native) 
System.Threading.ThreadPool:RequestWorkerThread ()
at System.Threading.ThreadPoolWorkQueue.EnsureThreadRequested () 
<0x7f8adf834790 + 0x00044> in :0 
at System.Threading.ThreadPoolWorkQueue.Dispatch () <0x7f8adf834cc0 + 
0x000fc> in :0 
at System.Threading._ThreadPoolWaitCallback.PerformWaitCallback () 
<0x7f8adf836530 + 0x8> in :0 

  Unhandled Exception:
  System.ExecutionEngineException: Couldn't create thread
at (wrapper managed-to-native) 
System.Threading.ThreadPool:RequestWorkerThread ()
at System.Threading.ThreadPoolWorkQueue.EnsureThreadRequested () 
<0x7f8adf834790 + 0x00044> in :0 
at System.Threading.ThreadPoolWorkQueue.Dispatch () <0x7f8adf834cc0 + 
0x000fc> in :0 
at System.Threading._ThreadPoolWaitCallback.PerformWaitCallback () 
<0x7f8adf836530 + 0x8> in :0 

  yes I have caps (500) but if your threading over 500 we have an issue.
  you are trying to forkbomb the system. only fedora as native
  prevention and mitigation techniques that work OOBE.YOu have to force
  them on debian based systems.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/banshee/+bug/1581719/+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 1470030] Re: "gpg-agent --daemon" stays after login, causing ecryptfs to not get unmounted

[Martin Pitt]

For the record, you can enable KillUserProcesses=yes in
/etc/systemd/logind.conf to automatically clean up processes which don't
properly terminate upon session stop. It has been tried to make this the
default, but it met heavy opposition, so we won't do that by default.
Reassigning to gnupg2 for now, as gpg-agent needs to properly stop on
logout. systemd --user will stop when the last "real" session is gone,
and so will lightdm's session child.

** Summary changed:

- encrypted home is not being unmounted upon logout
+ "gpg-agent --daemon" stays after login, causing ecryptfs to not get unmounted

** Package changed: systemd (Ubuntu) => gnupg2 (Ubuntu)

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

Title:
  "gpg-agent --daemon" stays after login, causing ecryptfs to not get
  unmounted

Status in eCryptfs:
  Confirmed
Status in gnupg2 package in Ubuntu:
  Confirmed
Status in ecryptfs-utils package in Debian:
  New

Bug description:
  
  Tested:

  (ok)  Xubuntu 14 LTS - 14.04.2 - desktop amd64
  (bug) Ubuntu GNOME 15.04 - desktop i386
  (bug) Ubuntu MATE 15.04 - desktop i386
  (bug) Lubuntu 15.04 - desktop i386
  (bug) Xubuntu 16.04 (fully upgraded on 2016-04-03T10:56:53+02:00) - amd64

  
  How do I test:

  Installation - default with option to encrypt Home folder during
  installation

  I shutdown the machine. Start it.

  If I first login with root, root cannot see my user's HOME
  folder/files/ they are encrypted.

  
  * However, what happens on Ubuntu 15.04 and 16.04 (bug):

  If I login to my user, check files, then log off fully, eventually
  login with root, root can see my user's files because
  /home/_user_/.Private is still mounted.

  
  * What happens on Xubuntu 14.04 (expected behaviour):

  If I login to my user, then I log off, eventually login with root,
  root CANNOT read my user's home dir/files.


  I can replicate this very easily and with no problem. I really
  appreciate everyone's opinion and expert words. Thank you!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ecryptfs/+bug/1470030/+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 1584491] Re: Starting DHCPv6 client on NDisc request failed: Invalid argument

[Martin Pitt]

Yakkety has v230, closing that task and keeping a xenial one open.
Updating wholesale to 230 isn't an option. But if you find the commit
that fixes that, we can backport that.

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

** Changed in: systemd (Ubuntu)
   Status: New => Fix Released

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

Title:
  Starting DHCPv6 client on NDisc request failed: Invalid argument

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Xenial:
  New

Bug description:
  I've experiencing constant issues when using systemd-networkd daemon
  to handle my network interfaces.

  Everything seems to be working as it should, but i keep getting this
  spammed in the syslog.

  I see this message in syslog:
  systemd-networkd[623]: enp0s25: Starting DHCPv6 client on NDisc request 
failed: Invalid argument

  This is fixed, as well as a couple of other IPv6 related issues in
  systemd version 230.

  https://lists.freedesktop.org/archives/systemd-
  devel/2016-May/036583.html

  Is updating to 230 for 16.04 on the table or is a backport for this
  bug a more appropriate way to do this?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1584491/+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 1584759] Re: masking NetworkManager ineffective without also masking network-manager

[Martin Pitt]

Correct, network-manager is the canonical name that init.d scripts refer
to.

** Package changed: systemd (Ubuntu) => network-manager (Ubuntu)

** Changed in: network-manager (Ubuntu)
   Status: New => Won't Fix

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

Title:
  masking NetworkManager ineffective without also masking network-
  manager

Status in network-manager package in Ubuntu:
  Won't Fix

Bug description:
  On xenial (systemd 229), 'systemctl mask NetworkManager' is
  ineffective; I can still start the service (and in fact it starts on
  boot). This may be due to an interaction with an init.d script with a
  different name ("network-manager").

  root@test-paniikki:~# systemctl is-enabled NetworkManager network-manager
  enabled
  enabled
  root@test-paniikki:~# systemctl mask NetworkManager
  Created symlink from /etc/systemd/system/NetworkManager.service to 
/dev/null.
  root@test-paniikki:~# systemctl is-enabled NetworkManager network-manager
  masked
  masked
  root@test-paniikki:~# systemctl start NetworkManager; echo $?
  0
  root@test-paniikki:~# systemctl status --no-pager NetworkManager
  ● NetworkManager.service - Network Manager
 Loaded: loaded (/lib/systemd/system/NetworkManager.service; masked; 
vendor preset: enabled)
 Active: active (running) since Mon 2016-05-23 15:39:09 EEST; 9s ago
   Main PID: 6155 (NetworkManager)
  Tasks: 6 (limit: 512)
 CGroup: /system.slice/NetworkManager.service
 ├─6155 /usr/sbin/NetworkManager --no-daemon
 ├─6167 /sbin/dhclient -d -q -sf 
/usr/lib/NetworkManager/nm-dhcp-helper -pf /va...
 └─6182 /usr/sbin/dnsmasq --no-resolv --keep-in-foreground 
--no-hosts --bind-in...

  
  Only if 'network-manager' is also masked will the service fail to start:

  root@test-paniikki:~# systemctl mask network-manager
  Created symlink from /etc/systemd/system/network-manager.service to 
/dev/null.
  root@test-paniikki:~# systemctl stop NetworkManager
  root@test-paniikki:~# systemctl start NetworkManager
  Failed to start NetworkManager.service: Unit NetworkManager.service is 
masked.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1584759/+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 1584910] Re: package udev 229-4ubuntu5 failed to install/upgrade: il sottoprocesso installato script di post-installation ha restituito lo stato di errore 1

[Martin Pitt]

A lot of packages are broken on your system with a message like

insserv: Starting .depend.boot depends on plymouth and therefore on system 
facility `$all' which can not be true!
insserv: Starting .depend.boot depends on plymouth and therefore on system 
facility `$all' which can not be true!
insserv: Starting .depend.boot depends on plymouth and therefore on system 
facility `$all' which can not be true!
insserv: Max recursions depth 99 reached
insserv:  loop involving service gdm3 at depth 2
insserv:  loop involving service .depend.boot at depth 1
insserv: There is a loop between service .depend.boot and dns-clean if started
insserv:  loop involving service dns-clean at depth 1
insserv: exiting now without changing boot order!
update-rc.d: error: insserv rejected the script header
dpkg: error processing package brltty (--configure):

Supposedly you changed something in the init scripts, plymouth and dns-
clean don't do this in a default installation.

** Package changed: systemd (Ubuntu) => plymouth (Ubuntu)

** Summary changed:

- package udev 229-4ubuntu5 failed to install/upgrade: il sottoprocesso 
installato script di post-installation ha restituito lo stato di errore 1
+ upgrade failure: loop between service .depend.boot and dns-clean if started

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

Title:
  upgrade failure: loop between service .depend.boot and dns-clean if
  started

Status in plymouth package in Ubuntu:
  New

Bug description:
  errore nello spostare sulla scrivania un programma exe. Utilizzo
  ubuntu 16.04

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: udev 229-4ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  Date: Mon May 23 18:30:13 2016
  ErrorMessage: il sottoprocesso installato script di post-installation ha 
restituito lo stato di errore 1
  InstallationDate: Installed on 2016-04-23 (30 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: Acer Aspire 6930G
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic 
root=UUID=93a96fcf-ed64-40ef-9fae-a391e4f5c948 ro drm.debug=0xe plymouth:debug
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.10ubuntu1
  SourcePackage: systemd
  Title: package udev 229-4ubuntu5 failed to install/upgrade: il sottoprocesso 
installato script di post-installation ha restituito lo stato di errore 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/25/2008
  dmi.bios.vendor: Acer
  dmi.bios.version: v0.3204
  dmi.board.name: Makalu
  dmi.board.vendor: Acer
  dmi.board.version: Not Applicable
  dmi.chassis.type: 1
  dmi.chassis.vendor: Acer
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAcer:bvrv0.3204:bd09/25/2008:svnAcer:pnAspire6930G:pvrNotApplicable:rvnAcer:rnMakalu:rvrNotApplicable:cvnAcer:ct1:cvrN/A:
  dmi.product.name: Aspire 6930G
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Acer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1584910/+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 1585406] Re: package udev 225-1ubuntu9.1 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1

[Martin Pitt]

This affects trusty → xenial upgrades only, not yakkety, closing
floating task.

** Changed in: systemd (Ubuntu)
   Status: New => Invalid

** Summary changed:

- package udev 225-1ubuntu9.1 failed to install/upgrade: subprocess new 
pre-removal script returned error exit status 1
+ package udev 225-1ubuntu9.1 failed to install/upgrade: 
dpkg-maintscript-helper: error: command symlink_to_dir is unknown

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

Title:
  package udev 225-1ubuntu9.1 failed to install/upgrade: dpkg-
  maintscript-helper: error: command symlink_to_dir is unknown

Status in systemd package in Ubuntu:
  Invalid
Status in systemd source package in Xenial:
  In Progress

Bug description:
  Died during upgrade from 15.10 x86-64.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: udev 225-1ubuntu9.1
  ProcVersionSignature: Ubuntu 4.2.0-37.43-generic 4.2.8-ckt10
  Uname: Linux 4.2.0-37-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  CustomUdevRuleFiles: 60-vboxdrv.rules 51-android.rules 99-lexscan.rules
  Date: Tue May 24 16:29:40 2016
  DuplicateSignature: package:udev:225-1ubuntu9.1:subprocess new pre-removal 
script returned error exit status 1
  ErrorMessage: subprocess new pre-removal script returned error exit status 1
  InstallationDate: Installed on 2013-05-02 (1118 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MachineType: System76, Inc. Serval WS
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-37-generic 
root=UUID=1fc67f3a-3070-4bdf-b16d-81d1e5d68535 ro
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: systemd
  Title: package udev 225-1ubuntu9.1 failed to install/upgrade: subprocess new 
pre-removal script returned error exit status 1
  UpgradeStatus: Upgraded to xenial on 2016-05-24 (0 days ago)
  dmi.bios.date: 10/26/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.05.04RS76
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: Serval WS
  dmi.board.vendor: System76, Inc.
  dmi.board.version: serw9
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: System76, Inc.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.05.04RS76:bd10/26/2015:svnSystem76,Inc.:pnServalWS:pvrserw9:rvnSystem76,Inc.:rnServalWS:rvrserw9:cvnSystem76,Inc.:ct10:cvrN/A:
  dmi.product.name: Serval WS
  dmi.product.version: serw9
  dmi.sys.vendor: System76, Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1585406/+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 1585406] Re: package udev 225-1ubuntu9.1 failed to install/upgrade: dpkg-maintscript-helper: error: command symlink_to_dir is unknown

[Martin Pitt]

Fix: http://anonscm.debian.org/cgit/pkg-systemd/systemd.git/commit/?h
=ubuntu-xenial=89d0fb2a6a

** Changed in: systemd (Ubuntu Xenial)
   Status: New => In Progress

** Tags added: upgrade-software-version

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

Title:
  package udev 225-1ubuntu9.1 failed to install/upgrade: dpkg-
  maintscript-helper: error: command symlink_to_dir is unknown

Status in systemd package in Ubuntu:
  Invalid
Status in systemd source package in Xenial:
  In Progress

Bug description:
  Died during upgrade from 15.10 x86-64.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: udev 225-1ubuntu9.1
  ProcVersionSignature: Ubuntu 4.2.0-37.43-generic 4.2.8-ckt10
  Uname: Linux 4.2.0-37-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  CustomUdevRuleFiles: 60-vboxdrv.rules 51-android.rules 99-lexscan.rules
  Date: Tue May 24 16:29:40 2016
  DuplicateSignature: package:udev:225-1ubuntu9.1:subprocess new pre-removal 
script returned error exit status 1
  ErrorMessage: subprocess new pre-removal script returned error exit status 1
  InstallationDate: Installed on 2013-05-02 (1118 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MachineType: System76, Inc. Serval WS
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-37-generic 
root=UUID=1fc67f3a-3070-4bdf-b16d-81d1e5d68535 ro
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: systemd
  Title: package udev 225-1ubuntu9.1 failed to install/upgrade: subprocess new 
pre-removal script returned error exit status 1
  UpgradeStatus: Upgraded to xenial on 2016-05-24 (0 days ago)
  dmi.bios.date: 10/26/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.05.04RS76
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: Serval WS
  dmi.board.vendor: System76, Inc.
  dmi.board.version: serw9
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: System76, Inc.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.05.04RS76:bd10/26/2015:svnSystem76,Inc.:pnServalWS:pvrserw9:rvnSystem76,Inc.:rnServalWS:rvrserw9:cvnSystem76,Inc.:ct10:cvrN/A:
  dmi.product.name: Serval WS
  dmi.product.version: serw9
  dmi.sys.vendor: System76, Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1585406/+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 1585406] Re: package udev 225-1ubuntu9.1 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1

[Martin Pitt]

De-configuring udev (225-1ubuntu9.1) ...
dpkg-maintscript-helper: error: command symlink_to_dir is unknown
Hint: upgrading dpkg to a newer version might help.

Seems we need a versioned dpkg pre-dependency here.

** Also affects: systemd (Ubuntu Xenial)
   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/1585406

Title:
  package udev 225-1ubuntu9.1 failed to install/upgrade: dpkg-
  maintscript-helper: error: command symlink_to_dir is unknown

Status in systemd package in Ubuntu:
  Invalid
Status in systemd source package in Xenial:
  In Progress

Bug description:
  Died during upgrade from 15.10 x86-64.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: udev 225-1ubuntu9.1
  ProcVersionSignature: Ubuntu 4.2.0-37.43-generic 4.2.8-ckt10
  Uname: Linux 4.2.0-37-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  CustomUdevRuleFiles: 60-vboxdrv.rules 51-android.rules 99-lexscan.rules
  Date: Tue May 24 16:29:40 2016
  DuplicateSignature: package:udev:225-1ubuntu9.1:subprocess new pre-removal 
script returned error exit status 1
  ErrorMessage: subprocess new pre-removal script returned error exit status 1
  InstallationDate: Installed on 2013-05-02 (1118 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MachineType: System76, Inc. Serval WS
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-37-generic 
root=UUID=1fc67f3a-3070-4bdf-b16d-81d1e5d68535 ro
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: systemd
  Title: package udev 225-1ubuntu9.1 failed to install/upgrade: subprocess new 
pre-removal script returned error exit status 1
  UpgradeStatus: Upgraded to xenial on 2016-05-24 (0 days ago)
  dmi.bios.date: 10/26/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.05.04RS76
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: Serval WS
  dmi.board.vendor: System76, Inc.
  dmi.board.version: serw9
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: System76, Inc.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.05.04RS76:bd10/26/2015:svnSystem76,Inc.:pnServalWS:pvrserw9:rvnSystem76,Inc.:rnServalWS:rvrserw9:cvnSystem76,Inc.:ct10:cvrN/A:
  dmi.product.name: Serval WS
  dmi.product.version: serw9
  dmi.sys.vendor: System76, Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1585406/+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 1585464] Re: package udev 225-1ubuntu9.1 [modified: lib/systemd/system/lvm2.service] failed to install/upgrade: subprocess new pre-removal script returned error exit status 1

[Martin Pitt]

*** This bug is a duplicate of bug 1585406 ***
https://bugs.launchpad.net/bugs/1585406

** This bug has been marked a duplicate of bug 1585406
   package udev 225-1ubuntu9.1 failed to install/upgrade: 
dpkg-maintscript-helper: error: command symlink_to_dir is unknown

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

Title:
  package udev 225-1ubuntu9.1 [modified:
  lib/systemd/system/lvm2.service] failed to install/upgrade: subprocess
  new pre-removal script returned error exit status 1

Status in systemd package in Ubuntu:
  New

Bug description:
  Mysterious death during upgrade from 15.10 to 16.04.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: udev 225-1ubuntu9.1 [modified: lib/systemd/system/lvm2.service]
  ProcVersionSignature: Ubuntu 4.2.0-37.43-generic 4.2.8-ckt10
  Uname: Linux 4.2.0-37-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  CustomUdevRuleFiles: 60-vboxdrv.rules 51-android.rules 99-lexscan.rules
  Date: Tue May 24 17:52:48 2016
  DuplicateSignature: package:udev:225-1ubuntu9.1 [modified: 
lib/systemd/system/lvm2.service]:subprocess new pre-removal script returned 
error exit status 1
  ErrorMessage: subprocess new pre-removal script returned error exit status 1
  InstallationDate: Installed on 2013-05-02 (1118 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MachineType: System76, Inc. Serval WS
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-37-generic 
root=UUID=1fc67f3a-3070-4bdf-b16d-81d1e5d68535 ro
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: systemd
  Title: package udev 225-1ubuntu9.1 [modified: 
lib/systemd/system/lvm2.service] failed to install/upgrade: subprocess new 
pre-removal script returned error exit status 1
  UpgradeStatus: Upgraded to xenial on 2016-05-25 (0 days ago)
  dmi.bios.date: 10/26/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.05.04RS76
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: Serval WS
  dmi.board.vendor: System76, Inc.
  dmi.board.version: serw9
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: System76, Inc.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.05.04RS76:bd10/26/2015:svnSystem76,Inc.:pnServalWS:pvrserw9:rvnSystem76,Inc.:rnServalWS:rvrserw9:cvnSystem76,Inc.:ct10:cvrN/A:
  dmi.product.name: Serval WS
  dmi.product.version: serw9
  dmi.sys.vendor: System76, Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1585464/+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 1585710] Re: package libsystemd0:amd64 229-4ubuntu6 failed to install/upgrade: Paket libsystemd0:amd64 kann nicht konfiguriert werden, da libsystemd0:i386 nicht bereit ist (aktue

[Martin Pitt]

This is a bug in apt, not systemd. I'm not sure how to debug this,
though. Julien, Michael, any idea?

** Package changed: systemd (Ubuntu) => apt (Ubuntu)

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

Title:
  package libsystemd0:amd64 229-4ubuntu6 failed to install/upgrade:
  Paket libsystemd0:amd64 kann nicht konfiguriert werden, da
  libsystemd0:i386 nicht bereit ist (aktueller Status »half-installed«)

Status in apt package in Ubuntu:
  New

Bug description:
  Error occurred while apt upgrade

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libsystemd0:amd64 229-4ubuntu6
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  AptOrdering:
   libsystemd0: Configure
   libsystemd0: Configure
   NULL: ConfigurePending
  Architecture: amd64
  Date: Wed May 25 18:33:53 2016
  ErrorMessage: Paket libsystemd0:amd64 kann nicht konfiguriert werden, da 
libsystemd0:i386 nicht bereit ist (aktueller Status »half-installed«)
  InstallationDate: Installed on 2016-04-29 (26 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.10ubuntu1
  SourcePackage: systemd
  Title: package libsystemd0:amd64 229-4ubuntu6 failed to install/upgrade: 
Paket libsystemd0:amd64 kann nicht konfiguriert werden, da libsystemd0:i386 
nicht bereit ist (aktueller Status »half-installed«)
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1585710/+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 1587009] Re: hvc0 not present

[Martin Pitt]

Do you actually have a /dev/hvc0 device? Device nodes are being created
by the kernel, not userspace, thus reassigning.

** Package changed: systemd (Ubuntu) => linux (Ubuntu)

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

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

Title:
  hvc0 not present

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  i have installed Ubuntu 16.04 with debootstrap on a XenServer 6.2.

  i have also installed xe-guest-utilities, grub-xen and linux-image-
  virtual.

  when booting the VM, i don't see anything in the XenCenter console.

  i think this is because there is no hvc0 tty.

  as written here, it should start automatically:
  http://0pointer.de/blog/projects/serial-console.html

  > lscpu
  Hypervisor vendor: Microsoft
  Virtualization type:   full

  maybe Ubuntu don't recognize Xen?

  how can i get this working?

  229-4ubuntu4

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1587009/+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 1588287] Re: util-linux breaks xenial installation

[Martin Pitt]

Fixed in yakkety. Can you please describe how this is being triggered?
Perhaps attach /var/log/installer/* ? We can't fix this in stables
without knowing how to reproduce the bug and verify that this fixes it.
Thanks!

** Bug watch added: Debian Bug tracker #823665
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=823665

** Also affects: util-linux (Debian) via
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=823665
   Importance: Unknown
   Status: Unknown

** Changed in: util-linux (Ubuntu)
   Status: New => Fix Released

** Also affects: util-linux (Ubuntu Trusty)
   Importance: Undecided
   Status: New

** Changed in: util-linux (Ubuntu Trusty)
   Status: New => Incomplete

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

Title:
  util-linux breaks xenial installation

Status in util-linux package in Ubuntu:
  Fix Released
Status in util-linux source package in Trusty:
  Incomplete
Status in util-linux package in Debian:
  Unknown

Bug description:
  Attempting to install xenial from an alternate install image xenial-
  alternate-amd64.iso triggered the bug reported at:

  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=823665

  and fixed by the patch at:

  https://anonscm.debian.org/cgit/collab-maint/pkg-util-
  linux.git/commit/?id=49a9f9ff0cdb64c02b12c2a00af30472305bc377

  The patch was made on util-linux-2.28-2 but can be applied easily to
  2.27.1-6ubuntu3 as found in xenial, so I back-ported the patch onto my
  local copy of the iso and can confirm that the installation got past
  the installation of util-linux.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1588287/+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 1589015] Re: Printer bug adds code into /var/tmp endlessly

[Martin Pitt]

I suppose you are talking abou the cnij* files which aren't being
cleaned up? That's what your link refers to. I'm not entirely sure which
driver is doing this, but tentatively assigning to the Canon one.

** Package changed: systemd (Ubuntu) => cjet (Ubuntu)

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

** Summary changed:

- Printer bug adds code into /var/tmp endlessly
+ Printer bug adds cnij* into /var/tmp endlessly

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

Title:
  Printer bug adds cnij* into /var/tmp endlessly

Status in cjet package in Ubuntu:
  Incomplete

Bug description:
  Canon Maxify MB2320 printer (all-in-one) causes or systemd causes
  lines to be added to /var/tmp/ continuously. By constant, I mean
  whenever the printer, or scanner, or copier function. I reported a bug
  at the Canon Printer Community Forum for it's writing massively large
  files (starting cnij) and filling /var/tmp to the point where / was
  complaining of no space remaining. As these two problems may be linked
  I'm posting a little about the cnij files, too. Please bear with me.

  http://community.usa.canon.com/t5/Office-Printers/Maxify-MB2320-and-
  driver/td-p/165313

  The next problem occurs after I start a weekly removal of those cnij
  files. When the device (printer) was first installed there were but 3
  or 4 files in /var/tmp, no including the cnij-s.

  That has now grown to 70+ lines. I append a few here, as they are
  somewhat similar. If you wish to see all 70, they are at
  https://paste.ubuntu.com/16968056/

  Representative sample:

  mark@Lexington:/var/tmp$ ls
  canon_sgmp2_setting.ini
  kdecache-mark
  mkinitramfs-FW_mgeshg
  systemd-private-273505a4cf664ff0af6e81870ea6665a-colord.service-hk7T18
  systemd-private-273505a4cf664ff0af6e81870ea6665a-rtkit-daemon.service-Lv8yQF
  
systemd-private-273505a4cf664ff0af6e81870ea6665a-systemd-timesyncd.service-Fizgv4
  systemd-private-29b03f52b21d493abf1e8ea22b6b7adc-colord.service-WLN1p1
  systemd-private-29b03f52b21d493abf1e8ea22b6b7adc-rtkit-daemon.service-ghG257
  
systemd-private-29b03f52b21d493abf1e8ea22b6b7adc-systemd-timesyncd.service-BuNOet

  While trying to run Ubuntu's (badly named app) "Backup", I received
  the following error message:

  
  Backup Failed

  Giving up after 5 attempts. Error: g-io-error-quark: Error opening
  file: '/media/mark/80cb5313-35a0-432b-9250-4cc62d79a3c8/duplicity-
  inc.20160528T201042Z.to.20160603T203335Z.vol2.diff tar.gpg': Read-only
  file system (21)

  I have asked for help at AskUbuntu and the Ubuntu Forums. At AskU I
  was directed to report the bug here. Following the Launchpad reporting
  guidelines:

  Description:  Ubuntu 16.04 LTS
  Release:  16.04

  mark@Lexington:/var/tmp$ apt-cache policy backups
  N: Unable to locate package backups

  I expected the backup to run as it has for years and years.

  Backup reports fail message.

  I am not aware of whether this is a security bug. I have left that box
  unchecked.

  There has been no response at Ubuntu Forums as yet. If there is one I
  will add the relevant information as it becomes available.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cjet/+bug/1589015/+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 1589288] Re: python3.4 package missing threading module in trusty-security

[bugchecker]

** Description changed:

  Someone forgot to add threading.py module in
  libpython3.4-mininal_3.4.0-2ubuntu1.1 package. I fail when trying to
  work with python3.4 in trusty-security environment.
  
  How to reproduce:
  1. Install new Ubuntu Trusty WITHOUT online updates or downgrade all packages 
to trusty-security.
  2. Disable *-updates repositories, update apt cache:
  # sed -i -e'/-updates/s/^/# /' /etc/apt/sources.list && apt-get update
  3. Upgrade python3 packages:
  # apt-get install python3 python3-minimal python3.4 python3.4-minimal 
libpython3.4-minimal libpython3.4-stdlib
  4. Try to import threading module (will fail):
  # python3 -c 'import threading'
  Traceback (most recent call last):
    File "", line 1, in 
  ImportError: No module named 'threading'
  
- Without threading.py will fail `pip3 install` and `add-apt-repository`.
+ Without threading.py `pip3 install` and `add-apt-repository` will fail.
  Extended terminal output (including apt-cache policy) is in
  python3.4_trusty_bug_terminal_output.txt . This problem has occured in
  https://bugs.launchpad.net/ubuntu/+source/python3.4/+bug/1503382/comments/4
  , but hasn't been articulated or resolved.
  
  I compared packages in security and updates and found significant 
differencies:
  1. [debian/pymindeps.py] subprocess key in excluded_imports is threading in 
security and dummy_threading in updates.
  2. [debian/PVER-minimal.README.Debian.in] Information about threading module 
differs.
  
  I make patch libpython3.4-minimal_3.4.0-2ubuntu1.1custompatch1.patch and
  applied to python3.4_3.4.0-2ubuntu1.1 . The result is available in
  https://launchpad.net/~bugchecker/+archive/ubuntu/python3-threading-
  trusty-sec . This patch may be incorrect but it works for me.
  
  Also I attached docker context for any experiments.

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

Title:
  python3.4 package missing threading module in trusty-security

Status in python3.4 package in Ubuntu:
  New

Bug description:
  Someone forgot to add threading.py module in
  libpython3.4-mininal_3.4.0-2ubuntu1.1 package. I fail when trying to
  work with python3.4 in trusty-security environment.

  How to reproduce:
  1. Install new Ubuntu Trusty WITHOUT online updates or downgrade all packages 
to trusty-security.
  2. Disable *-updates repositories, update apt cache:
  # sed -i -e'/-updates/s/^/# /' /etc/apt/sources.list && apt-get update
  3. Upgrade python3 packages:
  # apt-get install python3 python3-minimal python3.4 python3.4-minimal 
libpython3.4-minimal libpython3.4-stdlib
  4. Try to import threading module (will fail):
  # python3 -c 'import threading'
  Traceback (most recent call last):
    File "", line 1, in 
  ImportError: No module named 'threading'

  Without threading.py `pip3 install` and `add-apt-repository` will
  fail. Extended terminal output (including apt-cache policy) is in
  python3.4_trusty_bug_terminal_output.txt . This problem has occured in
  https://bugs.launchpad.net/ubuntu/+source/python3.4/+bug/1503382/comments/4
  , but hasn't been articulated or resolved.

  I compared packages in security and updates and found significant 
differencies:
  1. [debian/pymindeps.py] subprocess key in excluded_imports is threading in 
security and dummy_threading in updates.
  2. [debian/PVER-minimal.README.Debian.in] Information about threading module 
differs.

  I make patch libpython3.4-minimal_3.4.0-2ubuntu1.1custompatch1.patch
  and applied to python3.4_3.4.0-2ubuntu1.1 . The result is available in
  https://launchpad.net/~bugchecker/+archive/ubuntu/python3-threading-
  trusty-sec . This patch may be incorrect but it works for me.

  Also I attached docker context for any experiments.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python3.4/+bug/1589288/+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 1574324] Re: pulseaudio crashes when connecting to bluetooth headphones

[Joakim Koed]

I can also confirm this, see:
http://askubuntu.com/questions/779892/16-04-cant-use-bluetooth-a2dp-
headphones-pairs-but-does-not-connect-logs-insi

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

Title:
  pulseaudio crashes when connecting to bluetooth headphones

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  When I attempt to connect my Jaybird Bluebuds X to Ubuntu 16.04
  pulseaudio crashes, this does *NOT* happen with a Jambox which leads
  me to believe it's an intermittent problem with some hardware. This
  did not happen on Ubuntu 15.10 (which was an upgrade of 15.04).

  Ubuntu Release:

  Description:  Ubuntu 16.04 LTS
  Release:  16.04

  Pulseaudio Version:

  pulseaudio:
Installed: 1:8.0-0ubuntu3
Candidate: 1:8.0-0ubuntu3
Version table:
   *** 1:8.0-0ubuntu3 500
  500 http://gb.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status

  Device info:

  [bluetooth]# info 44:5E:F3:B4:07:29 
  Device 44:5E:F3:B4:07:29
Name: BlueBuds X
Alias: BlueBuds X
Class: 0x240404
Icon: audio-card
Paired: yes
Trusted: yes
Blocked: no
Connected: no
LegacyPairing: no
UUID: Headset   (1108--1000-8000-00805f9b34fb)
UUID: Audio Sink(110b--1000-8000-00805f9b34fb)
UUID: A/V Remote Control Target (110c--1000-8000-00805f9b34fb)
UUID: A/V Remote Control(110e--1000-8000-00805f9b34fb)
UUID: Handsfree (111e--1000-8000-00805f9b34fb)
UUID: Unknown   (80ff--1000-8000-00805f9b34fb)

  I have also attached a debug dump of Pulseaudio when attempting to
  connect to the headphones.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1574324/+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 1589288] Re: python3.4 package missing threading module in trusty-security

[bugchecker]

** Description changed:

  Someone forgot to add threading.py module in
  libpython3.4-mininal_3.4.0-2ubuntu1.1 package. I fail when trying to
  work with python3.4 in trusty-security environment.
  
  How to reproduce:
  1. Install new Ubuntu Trusty WITHOUT online updates or downgrade all packages 
to trusty-security.
  2. Disable *-updates repositories, update apt cache:
  # sed -i -e'/-updates/s/^/# /' /etc/apt/sources.list && apt-get update
  3. Upgrade python3 packages:
  # apt-get install python3 python3-minimal python3.4 python3.4-minimal 
libpython3.4-minimal libpython3.4-stdlib
  4. Try to import threading module (will fail):
  # python3 -c 'import threading'
  Traceback (most recent call last):
    File "", line 1, in 
  ImportError: No module named 'threading'
  
  Without threading.py will fail `pip3 install` and `add-apt-repository`.
- Extended terminal output (including apt-cache policy) in
+ Extended terminal output (including apt-cache policy) is in
  python3.4_trusty_bug_terminal_output.txt . This problem has occured in
  https://bugs.launchpad.net/ubuntu/+source/python3.4/+bug/1503382/comments/4
  , but hasn't been articulated or resolved.
  
  I compared packages in security and updates and found significant 
differencies:
  1. [debian/pymindeps.py] subprocess key in excluded_imports is threading in 
security and dummy_threading in updates.
  2. [debian/PVER-minimal.README.Debian.in] Information about threading module 
differs.
  
  I make patch libpython3.4-minimal_3.4.0-2ubuntu1.1custompatch1.patch and
  applied to python3.4_3.4.0-2ubuntu1.1 . The result is available in
  https://launchpad.net/~bugchecker/+archive/ubuntu/python3-threading-
  trusty-sec . This patch may be incorrect but it works for me.
  
  Also I attached docker context for any experiments.

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

Title:
  python3.4 package missing threading module in trusty-security

Status in python3.4 package in Ubuntu:
  New

Bug description:
  Someone forgot to add threading.py module in
  libpython3.4-mininal_3.4.0-2ubuntu1.1 package. I fail when trying to
  work with python3.4 in trusty-security environment.

  How to reproduce:
  1. Install new Ubuntu Trusty WITHOUT online updates or downgrade all packages 
to trusty-security.
  2. Disable *-updates repositories, update apt cache:
  # sed -i -e'/-updates/s/^/# /' /etc/apt/sources.list && apt-get update
  3. Upgrade python3 packages:
  # apt-get install python3 python3-minimal python3.4 python3.4-minimal 
libpython3.4-minimal libpython3.4-stdlib
  4. Try to import threading module (will fail):
  # python3 -c 'import threading'
  Traceback (most recent call last):
    File "", line 1, in 
  ImportError: No module named 'threading'

  Without threading.py will fail `pip3 install` and `add-apt-
  repository`. Extended terminal output (including apt-cache policy) is
  in python3.4_trusty_bug_terminal_output.txt . This problem has occured
  in
  https://bugs.launchpad.net/ubuntu/+source/python3.4/+bug/1503382/comments/4
  , but hasn't been articulated or resolved.

  I compared packages in security and updates and found significant 
differencies:
  1. [debian/pymindeps.py] subprocess key in excluded_imports is threading in 
security and dummy_threading in updates.
  2. [debian/PVER-minimal.README.Debian.in] Information about threading module 
differs.

  I make patch libpython3.4-minimal_3.4.0-2ubuntu1.1custompatch1.patch
  and applied to python3.4_3.4.0-2ubuntu1.1 . The result is available in
  https://launchpad.net/~bugchecker/+archive/ubuntu/python3-threading-
  trusty-sec . This patch may be incorrect but it works for me.

  Also I attached docker context for any experiments.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python3.4/+bug/1589288/+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 1589288] Re: python3.4 package missing threading module in trusty-security

[bugchecker]

** Description changed:

  Someone forgot to add threading.py module in
  libpython3.4-mininal_3.4.0-2ubuntu1.1 package. I fail when trying to
  work with python3.4 in trusty-security environment.
  
  How to reproduce:
  1. Install new Ubuntu Trusty WITHOUT online updates or downgrade all packages 
to trusty-security.
  2. Disable *-updates repositories, update apt cache:
  # sed -i -e'/-updates/s/^/# /' /etc/apt/sources.list && apt-get update
  3. Upgrade python3 packages:
  # apt-get install python3 python3-minimal python3.4 python3.4-minimal 
libpython3.4-minimal libpython3.4-stdlib
  4. Try to import threading module (will be failed):
  # python3 -c 'import threading'
  Traceback (most recent call last):
    File "", line 1, in 
  ImportError: No module named 'threading'
  
- Extended terminal output (including apt-cache policy) in
+ Without threading.py will be fail `pip3 install` and `add-apt-
+ repository`. Extended terminal output (including apt-cache policy) in
  python3.4_trusty_bug_terminal_output.txt . This problem has occured in
  https://bugs.launchpad.net/ubuntu/+source/python3.4/+bug/1503382/comments/4
  , but hasn't been articulated or resolved.
  
  I compared packages in security and updates and found significant 
differencies:
  1. [debian/pymindeps.py] subprocess key in excluded_imports is threading in 
security and dummy_threading in updates.
  2. [debian/PVER-minimal.README.Debian.in] Information about threading module 
differs.
  
  I make patch libpython3.4-minimal_3.4.0-2ubuntu1.1custompatch1.patch and
  applied to python3.4_3.4.0-2ubuntu1.1 . The result is available in
  https://launchpad.net/~bugchecker/+archive/ubuntu/python3-threading-
  trusty-sec . This patch may be incorrect but it works for me.
  
  Also I attached docker context for any experiments.

** Description changed:

  Someone forgot to add threading.py module in
  libpython3.4-mininal_3.4.0-2ubuntu1.1 package. I fail when trying to
  work with python3.4 in trusty-security environment.
  
  How to reproduce:
  1. Install new Ubuntu Trusty WITHOUT online updates or downgrade all packages 
to trusty-security.
  2. Disable *-updates repositories, update apt cache:
  # sed -i -e'/-updates/s/^/# /' /etc/apt/sources.list && apt-get update
  3. Upgrade python3 packages:
  # apt-get install python3 python3-minimal python3.4 python3.4-minimal 
libpython3.4-minimal libpython3.4-stdlib
- 4. Try to import threading module (will be failed):
+ 4. Try to import threading module (will fail):
  # python3 -c 'import threading'
  Traceback (most recent call last):
    File "", line 1, in 
  ImportError: No module named 'threading'
  
- Without threading.py will be fail `pip3 install` and `add-apt-
- repository`. Extended terminal output (including apt-cache policy) in
+ Without threading.py will fail `pip3 install` and `add-apt-repository`.
+ Extended terminal output (including apt-cache policy) in
  python3.4_trusty_bug_terminal_output.txt . This problem has occured in
  https://bugs.launchpad.net/ubuntu/+source/python3.4/+bug/1503382/comments/4
  , but hasn't been articulated or resolved.
  
  I compared packages in security and updates and found significant 
differencies:
  1. [debian/pymindeps.py] subprocess key in excluded_imports is threading in 
security and dummy_threading in updates.
  2. [debian/PVER-minimal.README.Debian.in] Information about threading module 
differs.
  
  I make patch libpython3.4-minimal_3.4.0-2ubuntu1.1custompatch1.patch and
  applied to python3.4_3.4.0-2ubuntu1.1 . The result is available in
  https://launchpad.net/~bugchecker/+archive/ubuntu/python3-threading-
  trusty-sec . This patch may be incorrect but it works for me.
  
  Also I attached docker context for any experiments.

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

Title:
  python3.4 package missing threading module in trusty-security

Status in python3.4 package in Ubuntu:
  New

Bug description:
  Someone forgot to add threading.py module in
  libpython3.4-mininal_3.4.0-2ubuntu1.1 package. I fail when trying to
  work with python3.4 in trusty-security environment.

  How to reproduce:
  1. Install new Ubuntu Trusty WITHOUT online updates or downgrade all packages 
to trusty-security.
  2. Disable *-updates repositories, update apt cache:
  # sed -i -e'/-updates/s/^/# /' /etc/apt/sources.list && apt-get update
  3. Upgrade python3 packages:
  # apt-get install python3 python3-minimal python3.4 python3.4-minimal 
libpython3.4-minimal libpython3.4-stdlib
  4. Try to import threading module (will fail):
  # python3 -c 'import threading'
  Traceback (most recent call last):
    File "", line 1, in 
  ImportError: No module named 'threading'

  Without threading.py will fail `pip3 install` and `add-apt-
  repository`. Extended terminal output (including apt-cache policy) in
  

[Touch-packages] [Bug 1589293] [NEW] Boot sequence errors found.

[Hadid]

Public bug reported:

Ordering cycle found, skipping show Plymouth Boot Screen.
Then computer became very slow

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-23.41-generic 4.4.10
Uname: Linux 4.4.0-23-generic x86_64
NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Sun Jun  5 21:12:24 2016
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
GraphicsCard:
 Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 
09) (prog-if 00 [VGA controller])
   Subsystem: Toshiba America Info Systems Haswell-ULT Integrated Graphics 
Controller [1179:f920]
InstallationDate: Installed on 2016-04-25 (40 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
MachineType: TOSHIBA SATELLITE S50-B
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-23-generic.efi.signed 
root=UUID=82ec02f7-5477-48db-a3f6-8e5b1f24343f ro quiet splash
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/14/2014
dmi.bios.vendor: INSYDE Corp.
dmi.bios.version: 1.70
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: Type2 - Board Product Name1
dmi.board.vendor: Type2 - Board Vendor Name1
dmi.board.version: Type2 - Board Version
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: OEM Chassis ManuFacturer
dmi.chassis.version: OEM Chassis Version
dmi.modalias: 
dmi:bvnINSYDECorp.:bvr1.70:bd08/14/2014:svnTOSHIBA:pnSATELLITES50-B:pvrPSPQ6E-00Q008GR:rvnType2-BoardVendorName1:rnType2-BoardProductName1:rvrType2-BoardVersion:cvnOEMChassisManuFacturer:ct10:cvrOEMChassisVersion:
dmi.product.name: SATELLITE S50-B
dmi.product.version: PSPQ6E-00Q008GR
dmi.sys.vendor: TOSHIBA
version.compiz: compiz 1:0.9.12.2+16.04.20160526-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2
version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2
xserver.bootTime: Sun Jun  5 20:45:28 2016
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id1096 
 vendor LGD
xserver.version: 2:1.18.3-1ubuntu2.2

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


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

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

Title:
  Boot sequence errors found.

Status in xorg package in Ubuntu:
  New

Bug description:
  Ordering cycle found, skipping show Plymouth Boot Screen.
  Then computer became very slow

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-23.41-generic 4.4.10
  Uname: Linux 4.4.0-23-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Sun Jun  5 21:12:24 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Toshiba America Info Systems Haswell-ULT Integrated Graphics 
Controller [1179:f920]
  InstallationDate: Installed on 2016-04-25 (40 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: TOSHIBA SATELLITE S50-B
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-23-generic.efi.signed 
root=UUID=82ec02f7-5477-48db-a3f6-8e5b1f24343f ro quiet splash
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/14/2014
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 1.70
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Type2 

[Touch-packages] [Bug 1589288] Re: python3.4 package missing threading module in trusty-security

[bugchecker]

** Summary changed:

- python-3.4 package missing threading module in trusty-security
+ python3.4 package missing threading module in trusty-security

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

Title:
  python3.4 package missing threading module in trusty-security

Status in python3.4 package in Ubuntu:
  New

Bug description:
  Someone forgot to add threading.py module in
  libpython3.4-mininal_3.4.0-2ubuntu1.1 package. I fail when trying to
  work with python3.4 in trusty-security environment.

  How to reproduce:
  1. Install new Ubuntu Trusty WITHOUT online updates or downgrade all packages 
to trusty-security.
  2. Disable *-updates repositories, update apt cache:
  # sed -i -e'/-updates/s/^/# /' /etc/apt/sources.list && apt-get update
  3. Upgrade python3 packages:
  # apt-get install python3 python3-minimal python3.4 python3.4-minimal 
libpython3.4-minimal libpython3.4-stdlib
  4. Try to import threading module (will be failed):
  # python3 -c 'import threading'
  Traceback (most recent call last):
    File "", line 1, in 
  ImportError: No module named 'threading'

  Extended terminal output (including apt-cache policy) in
  python3.4_trusty_bug_terminal_output.txt . This problem has occured in
  https://bugs.launchpad.net/ubuntu/+source/python3.4/+bug/1503382/comments/4
  , but hasn't been articulated or resolved.

  I compared packages in security and updates and found significant 
differencies:
  1. [debian/pymindeps.py] subprocess key in excluded_imports is threading in 
security and dummy_threading in updates.
  2. [debian/PVER-minimal.README.Debian.in] Information about threading module 
differs.

  I make patch libpython3.4-minimal_3.4.0-2ubuntu1.1custompatch1.patch
  and applied to python3.4_3.4.0-2ubuntu1.1 . The result is available in
  https://launchpad.net/~bugchecker/+archive/ubuntu/python3-threading-
  trusty-sec . This patch may be incorrect but it works for me.

  Also I attached docker context for any experiments.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python3.4/+bug/1589288/+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 1589288] [NEW] python-3.4 package missing threading module in trusty-security

[bugchecker]

Public bug reported:

Someone forgot to add threading.py module in
libpython3.4-mininal_3.4.0-2ubuntu1.1 package. I fail when trying to
work with python3.4 in trusty-security environment.

How to reproduce:
1. Install new Ubuntu Trusty WITHOUT online updates or downgrade all packages 
to trusty-security.
2. Disable *-updates repositories, update apt cache:
# sed -i -e'/-updates/s/^/# /' /etc/apt/sources.list && apt-get update
3. Upgrade python3 packages:
# apt-get install python3 python3-minimal python3.4 python3.4-minimal 
libpython3.4-minimal libpython3.4-stdlib
4. Try to import threading module (will be failed):
# python3 -c 'import threading'
Traceback (most recent call last):
  File "", line 1, in 
ImportError: No module named 'threading'

Extended terminal output (including apt-cache policy) in
python3.4_trusty_bug_terminal_output.txt . This problem has occured in
https://bugs.launchpad.net/ubuntu/+source/python3.4/+bug/1503382/comments/4
, but hasn't been articulated or resolved.

I compared packages in security and updates and found significant differencies:
1. [debian/pymindeps.py] subprocess key in excluded_imports is threading in 
security and dummy_threading in updates.
2. [debian/PVER-minimal.README.Debian.in] Information about threading module 
differs.

I make patch libpython3.4-minimal_3.4.0-2ubuntu1.1custompatch1.patch and
applied to python3.4_3.4.0-2ubuntu1.1 . The result is available in
https://launchpad.net/~bugchecker/+archive/ubuntu/python3-threading-
trusty-sec . This patch may be incorrect but it works for me.

Also I attached docker context for any experiments.

** Affects: python3.4 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: python3.4 trusty

** Attachment added: "python3.4_trusty_bug_terminal_output.txt"
   
https://bugs.launchpad.net/bugs/1589288/+attachment/4677549/+files/python3.4_trusty_bug_terminal_output.txt

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

Title:
  python-3.4 package missing threading module in trusty-security

Status in python3.4 package in Ubuntu:
  New

Bug description:
  Someone forgot to add threading.py module in
  libpython3.4-mininal_3.4.0-2ubuntu1.1 package. I fail when trying to
  work with python3.4 in trusty-security environment.

  How to reproduce:
  1. Install new Ubuntu Trusty WITHOUT online updates or downgrade all packages 
to trusty-security.
  2. Disable *-updates repositories, update apt cache:
  # sed -i -e'/-updates/s/^/# /' /etc/apt/sources.list && apt-get update
  3. Upgrade python3 packages:
  # apt-get install python3 python3-minimal python3.4 python3.4-minimal 
libpython3.4-minimal libpython3.4-stdlib
  4. Try to import threading module (will be failed):
  # python3 -c 'import threading'
  Traceback (most recent call last):
    File "", line 1, in 
  ImportError: No module named 'threading'

  Extended terminal output (including apt-cache policy) in
  python3.4_trusty_bug_terminal_output.txt . This problem has occured in
  https://bugs.launchpad.net/ubuntu/+source/python3.4/+bug/1503382/comments/4
  , but hasn't been articulated or resolved.

  I compared packages in security and updates and found significant 
differencies:
  1. [debian/pymindeps.py] subprocess key in excluded_imports is threading in 
security and dummy_threading in updates.
  2. [debian/PVER-minimal.README.Debian.in] Information about threading module 
differs.

  I make patch libpython3.4-minimal_3.4.0-2ubuntu1.1custompatch1.patch
  and applied to python3.4_3.4.0-2ubuntu1.1 . The result is available in
  https://launchpad.net/~bugchecker/+archive/ubuntu/python3-threading-
  trusty-sec . This patch may be incorrect but it works for me.

  Also I attached docker context for any experiments.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python3.4/+bug/1589288/+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 1589288] Re: python-3.4 package missing threading module in trusty-security

[bugchecker]

** Patch added: "libpython3.4-minimal_3.4.0-2ubuntu1.1custompatch1.patch"
   
https://bugs.launchpad.net/ubuntu/+source/python3.4/+bug/1589288/+attachment/4677550/+files/libpython3.4-minimal_3.4.0-2ubuntu1.1custompatch1.patch

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

Title:
  python-3.4 package missing threading module in trusty-security

Status in python3.4 package in Ubuntu:
  New

Bug description:
  Someone forgot to add threading.py module in
  libpython3.4-mininal_3.4.0-2ubuntu1.1 package. I fail when trying to
  work with python3.4 in trusty-security environment.

  How to reproduce:
  1. Install new Ubuntu Trusty WITHOUT online updates or downgrade all packages 
to trusty-security.
  2. Disable *-updates repositories, update apt cache:
  # sed -i -e'/-updates/s/^/# /' /etc/apt/sources.list && apt-get update
  3. Upgrade python3 packages:
  # apt-get install python3 python3-minimal python3.4 python3.4-minimal 
libpython3.4-minimal libpython3.4-stdlib
  4. Try to import threading module (will be failed):
  # python3 -c 'import threading'
  Traceback (most recent call last):
    File "", line 1, in 
  ImportError: No module named 'threading'

  Extended terminal output (including apt-cache policy) in
  python3.4_trusty_bug_terminal_output.txt . This problem has occured in
  https://bugs.launchpad.net/ubuntu/+source/python3.4/+bug/1503382/comments/4
  , but hasn't been articulated or resolved.

  I compared packages in security and updates and found significant 
differencies:
  1. [debian/pymindeps.py] subprocess key in excluded_imports is threading in 
security and dummy_threading in updates.
  2. [debian/PVER-minimal.README.Debian.in] Information about threading module 
differs.

  I make patch libpython3.4-minimal_3.4.0-2ubuntu1.1custompatch1.patch
  and applied to python3.4_3.4.0-2ubuntu1.1 . The result is available in
  https://launchpad.net/~bugchecker/+archive/ubuntu/python3-threading-
  trusty-sec . This patch may be incorrect but it works for me.

  Also I attached docker context for any experiments.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python3.4/+bug/1589288/+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 1589288] Re: python-3.4 package missing threading module in trusty-security

[bugchecker]

** Attachment added: "docker_python3.4_trusty_bug.tar.gz"
   
https://bugs.launchpad.net/ubuntu/+source/python3.4/+bug/1589288/+attachment/4677551/+files/docker_python3.4_trusty_bug.tar.gz

** Description changed:

  Someone forgot to add threading.py module in
  libpython3.4-mininal_3.4.0-2ubuntu1.1 package. I fail when trying to
  work with python3.4 in trusty-security environment.
  
  How to reproduce:
  1. Install new Ubuntu Trusty WITHOUT online updates or downgrade all packages 
to trusty-security.
  2. Disable *-updates repositories, update apt cache:
  # sed -i -e'/-updates/s/^/# /' /etc/apt/sources.list && apt-get update
  3. Upgrade python3 packages:
  # apt-get install python3 python3-minimal python3.4 python3.4-minimal 
libpython3.4-minimal libpython3.4-stdlib
  4. Try to import threading module (will be failed):
  # python3 -c 'import threading'
  Traceback (most recent call last):
-   File "", line 1, in 
+   File "", line 1, in 
  ImportError: No module named 'threading'
  
  Extended terminal output (including apt-cache policy) in
  python3.4_trusty_bug_terminal_output.txt . This problem has occured in
  https://bugs.launchpad.net/ubuntu/+source/python3.4/+bug/1503382/comments/4
  , but hasn't been articulated or resolved.
  
  I compared packages in security and updates and found significant 
differencies:
  1. [debian/pymindeps.py] subprocess key in excluded_imports is threading in 
security and dummy_threading in updates.
  2. [debian/PVER-minimal.README.Debian.in] Information about threading module 
differs.
  
  I make patch libpython3.4-minimal_3.4.0-2ubuntu1.1custompatch1.patch and
  applied to python3.4_3.4.0-2ubuntu1.1 . The result is available in
  https://launchpad.net/~bugchecker/+archive/ubuntu/python3-threading-
  trusty-sec . This patch may be incorrect but it works for me.
  
- I attached docker context for any experiments.
+ Also I attached docker context for any experiments.

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

Title:
  python-3.4 package missing threading module in trusty-security

Status in python3.4 package in Ubuntu:
  New

Bug description:
  Someone forgot to add threading.py module in
  libpython3.4-mininal_3.4.0-2ubuntu1.1 package. I fail when trying to
  work with python3.4 in trusty-security environment.

  How to reproduce:
  1. Install new Ubuntu Trusty WITHOUT online updates or downgrade all packages 
to trusty-security.
  2. Disable *-updates repositories, update apt cache:
  # sed -i -e'/-updates/s/^/# /' /etc/apt/sources.list && apt-get update
  3. Upgrade python3 packages:
  # apt-get install python3 python3-minimal python3.4 python3.4-minimal 
libpython3.4-minimal libpython3.4-stdlib
  4. Try to import threading module (will be failed):
  # python3 -c 'import threading'
  Traceback (most recent call last):
    File "", line 1, in 
  ImportError: No module named 'threading'

  Extended terminal output (including apt-cache policy) in
  python3.4_trusty_bug_terminal_output.txt . This problem has occured in
  https://bugs.launchpad.net/ubuntu/+source/python3.4/+bug/1503382/comments/4
  , but hasn't been articulated or resolved.

  I compared packages in security and updates and found significant 
differencies:
  1. [debian/pymindeps.py] subprocess key in excluded_imports is threading in 
security and dummy_threading in updates.
  2. [debian/PVER-minimal.README.Debian.in] Information about threading module 
differs.

  I make patch libpython3.4-minimal_3.4.0-2ubuntu1.1custompatch1.patch
  and applied to python3.4_3.4.0-2ubuntu1.1 . The result is available in
  https://launchpad.net/~bugchecker/+archive/ubuntu/python3-threading-
  trusty-sec . This patch may be incorrect but it works for me.

  Also I attached docker context for any experiments.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python3.4/+bug/1589288/+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 1589289] [NEW] fstrim: cannot open /dev/.lxd-mounts: Permission denied

[Tamas Papp]

Public bug reported:

fstrun daily cronjob output in an unprivileged LXD container:

/etc/cron.weekly/fstrim:
fstrim: cannot open /dev/.lxd-mounts: Permission denied
fstrim: /dev/fuse: not a directory
fstrim: /dev/lxd: FITRIM ioctl failed: Operation not permitted


There is a github issue:

https://github.com/lxc/lxd/issues/2030


The outcome is that it's purely an fstrim misbehaviour, it could be smarter.


Stephane Graber comment:


As all of this is handled by the kernel, there isn't anything we can do
about it in LXD.

I think fstrim should be made slightly more clever:

* Don't run on bind-mounts (you can detect bind-mounts by parsing 
/proc/self/mountinfo instead of /proc/mounts)
* Maybe not be as noisy on expected errors like EACCES, EPERM and ENOENT, only 
log actual failures which would likely be EINVAL or memory related errors.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: util-linux 2.27.1-6ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
Uname: Linux 4.4.0-21-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
Date: Sun Jun  5 19:49:04 2016
ProcEnviron:
 LANGUAGE=en_US:en
 TERM=xterm
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: util-linux
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: util-linux (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug xenial

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

Title:
  fstrim: cannot open /dev/.lxd-mounts: Permission denied

Status in util-linux package in Ubuntu:
  New

Bug description:
  fstrun daily cronjob output in an unprivileged LXD container:

  /etc/cron.weekly/fstrim:
  fstrim: cannot open /dev/.lxd-mounts: Permission denied
  fstrim: /dev/fuse: not a directory
  fstrim: /dev/lxd: FITRIM ioctl failed: Operation not permitted

  
  There is a github issue:

  https://github.com/lxc/lxd/issues/2030

  
  The outcome is that it's purely an fstrim misbehaviour, it could be smarter.

  
  Stephane Graber comment:


  
  As all of this is handled by the kernel, there isn't anything we can do about 
it in LXD.

  I think fstrim should be made slightly more clever:

  * Don't run on bind-mounts (you can detect bind-mounts by parsing 
/proc/self/mountinfo instead of /proc/mounts)
  * Maybe not be as noisy on expected errors like EACCES, EPERM and ENOENT, 
only log actual failures which would likely be EINVAL or memory related errors.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: util-linux 2.27.1-6ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Sun Jun  5 19:49:04 2016
  ProcEnviron:
   LANGUAGE=en_US:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: util-linux
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1589289/+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 1589286] [NEW] When boot process everything stays black

[salvatore tornetta]

Public bug reported:

  $ Ubuntu-bug xorg


PC boots only at 2 times ?
Main board model
top left and unreadable

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: xorg 1:7.7+1ubuntu8.1
ProcVersionSignature: Ubuntu 3.19.0-59.66~14.04.1-generic 3.19.8-ckt19
Uname: Linux 3.19.0-59-generic x86_64
.tmp.unity.support.test.0:
 
ApportVersion: 2.14.1-0ubuntu3.21
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Sun Jun  5 19:05:34 2016
DistUpgraded: Fresh install
DistroCodename: trusty
DistroVariant: ubuntu
GraphicsCard: NVIDIA Corporation G92 [GeForce 9800 GTX+] [10de:0613] (rev a2) 
(prog-if 00 [VGA controller])
InstallationDate: Installed on 2016-05-14 (22 days ago)
InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
LightdmGreeterLog:
 ** (lightdm-gtk-greeter:1690): WARNING **: [PIDs] Failed to execute command: 
upstart
 
 ** (lightdm-gtk-greeter:1690): WARNING **: Failed to load user image: Datei 
»/home/schmetterling/.face« konnte nicht geöffnet werden: Datei oder 
Verzeichnis nicht gefunden
LightdmGreeterLogOld:
 ** (lightdm-gtk-greeter:1684): WARNING **: [PIDs] Failed to execute command: 
upstart
 
 ** (lightdm-gtk-greeter:1684): WARNING **: Failed to load user image: Datei 
»/home/schmetterling/.face« konnte nicht geöffnet werden: Datei oder 
Verzeichnis nicht gefunden
 g_dbus_connection_real_closed: Remote peer vanished with error: Underlying 
GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting.
MachineType: Gigabyte Technology Co., Ltd. EP35-DS4
ProcEnviron:
 LANGUAGE=de_DE
 PATH=(custom, no user)
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-59-generic 
root=UUID=aafa789b-2ab0-4c2c-9b2e-17bf91e70f40 ro quiet splash
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/27/2008
dmi.bios.vendor: Award Software International, Inc.
dmi.bios.version: F3
dmi.board.name: EP35-DS4
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF3:bd02/27/2008:svnGigabyteTechnologyCo.,Ltd.:pnEP35-DS4:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnEP35-DS4:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
dmi.product.name: EP35-DS4
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
version.compiz: compiz 1:0.9.11.3+14.04.20160425-0ubuntu1.1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.64-1~ubuntu14.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri N/A
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core N/A
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
xserver.bootTime: Sun Jun  5 19:02:17 2016
xserver.configfile: default
xserver.devices:
 inputPower Button KEYBOARD, id 6
 inputPower Button KEYBOARD, id 7
 inputPIXART USB OPTICAL MOUSE MOUSE, id 8
 inputAT Translated Set 2 keyboard KEYBOARD, id 9
 inputPIXART USB OPTICAL MOUSE MOUSE, id 8
xserver.errors:
 Failed to load module "nvidia" (module does not exist, 0)
 Failed to load module "nvidia" (module does not exist, 0)
 NOUVEAU(0): [COPY] failed to allocate class.
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.17.1-0ubuntu3.1~trusty1
xserver.video_driver: nouveau

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


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

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

Title:
  When boot process everything stays black

Status in xorg package in Ubuntu:
  New

Bug description:
$ Ubuntu-bug xorg

  
  PC boots only at 2 times ?
  Main board model
  top left and unreadable

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 3.19.0-59.66~14.04.1-generic 3.19.8-ckt19
  Uname: Linux 3.19.0-59-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Sun Jun  5 19:05:34 2016
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  GraphicsCard: NVIDIA Corporation G92 [GeForce 9800 GTX+] 

[Touch-packages] [Bug 1589279] [NEW] Gps not working! Meizu mx4 ubuntu

[dawid wysocki]

Public bug reported:

Completely not working gps. Not working with any app. Cant find location
etc

** Affects: indicator-location (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  Gps not working! Meizu mx4 ubuntu

Status in indicator-location package in Ubuntu:
  New

Bug description:
  Completely not working gps. Not working with any app. Cant find
  location etc

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-location/+bug/1589279/+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 1589278] [NEW] package ca-certificates 20160104ubuntu1 failed to install/upgrade: triggers looping, abandoned

[Douglas Hunter]

Public bug reported:

upgrade from 14.04 to 16.04;

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: ca-certificates 20160104ubuntu1
ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
Uname: Linux 4.4.0-22-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
Date: Sun Jun  5 15:32:31 2016
ErrorMessage: triggers looping, abandoned
InstallationDate: Installed on 2015-12-09 (178 days ago)
InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1)
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.1
 apt  1.2.12~ubuntu16.04.1
SourcePackage: ca-certificates
Title: package ca-certificates 20160104ubuntu1 failed to install/upgrade: 
triggers looping, abandoned
UpgradeStatus: Upgraded to xenial on 2016-06-05 (0 days ago)

** Affects: ca-certificates (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package xenial

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

Title:
  package ca-certificates 20160104ubuntu1 failed to install/upgrade:
  triggers looping, abandoned

Status in ca-certificates package in Ubuntu:
  New

Bug description:
  upgrade from 14.04 to 16.04;

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: ca-certificates 20160104ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Sun Jun  5 15:32:31 2016
  ErrorMessage: triggers looping, abandoned
  InstallationDate: Installed on 2015-12-09 (178 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: ca-certificates
  Title: package ca-certificates 20160104ubuntu1 failed to install/upgrade: 
triggers looping, abandoned
  UpgradeStatus: Upgraded to xenial on 2016-06-05 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ca-certificates/+bug/1589278/+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 1551122] Re: Crash on screen power save

[xapient]

sorry... the repository is offline by now so i tried this one

deb http://archive.neon.kde.org/dev/unstable xenial main

kde 5.6.99
qt 5.6

status report:

the bug is still here but in a weird way..   plasma starts with one
screen black.. deactivating/activating it in kscreen systemsettings
brings it back to life..

powermanagment sleep  "killed" the other display (black) but panel and 
rightclick remained active..
i could change the wallpaper and revived it by that action..


so it seems the new plasma is not segfaulting anymore but still doesn't know 
how to handle the situation

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

Title:
  Crash on screen power save

Status in qtbase-opensource-src package in Ubuntu:
  Fix Released

Bug description:
  Continuation to bug #1548766 to consider another upstream fix from
  https://codereview.qt-project.org/#/c/138681/

  The fix could affect both monitor power saving or attaching/detaching
  cycles.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1551122/+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 1589277] [NEW] package ca-certificates 20160104ubuntu1 failed to install/upgrade: triggers looping, abandoned

[Douglas Hunter]

Public bug reported:

upgrade from 14.04

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: ca-certificates 20160104ubuntu1
ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
Uname: Linux 4.4.0-22-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
Date: Sun Jun  5 15:32:31 2016
ErrorMessage: triggers looping, abandoned
InstallationDate: Installed on 2015-12-09 (178 days ago)
InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1)
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.1
 apt  1.2.12~ubuntu16.04.1
SourcePackage: ca-certificates
Title: package ca-certificates 20160104ubuntu1 failed to install/upgrade: 
triggers looping, abandoned
UpgradeStatus: Upgraded to xenial on 2016-06-05 (0 days ago)

** Affects: ca-certificates (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package xenial

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

Title:
  package ca-certificates 20160104ubuntu1 failed to install/upgrade:
  triggers looping, abandoned

Status in ca-certificates package in Ubuntu:
  New

Bug description:
  upgrade from 14.04

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: ca-certificates 20160104ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Sun Jun  5 15:32:31 2016
  ErrorMessage: triggers looping, abandoned
  InstallationDate: Installed on 2015-12-09 (178 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: ca-certificates
  Title: package ca-certificates 20160104ubuntu1 failed to install/upgrade: 
triggers looping, abandoned
  UpgradeStatus: Upgraded to xenial on 2016-06-05 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ca-certificates/+bug/1589277/+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 1539957] Re: [enhancement] Allow files and links to be put on the Unity8 desktop

[Emanuele Antonio Faraone]

when?

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

Title:
  [enhancement] Allow files and links to be put on the Unity8 desktop

Status in Mir:
  Invalid
Status in Ubuntu UX:
  Triaged
Status in unity8 package in Ubuntu:
  Incomplete

Bug description:
  enable the use of the desktop as in unity 7 . then adding the
  possibility to put files on the desktop

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1539957/+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 1589255] Re: Double login screen In desktop

[Emanuele Antonio Faraone]

** Also affects: mir
   Importance: Undecided
   Status: New

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

Title:
  Double login screen In desktop

Status in Mir:
  New
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  when I turn on the PC and choose unity8 from the login screen I enter the 
password, once entered the password and after that it is loaded unity8 I again 
put the password in the login screen unity8. It should happen as in Unity 7 in 
which you enter directly without having to put your password
  Ubuntu 16.10(daily build)
  Unity8.12+16.10.20160527

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1589255/+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 1551122] Re: Crash on screen power save

[xapient]

i use this repo (kde neon) http://archive.neon.kde.org/tmp/testing
which delivers an up2date plasma 5.6.4 and Qt 5.6 and the bug is still there.. 
sometimes the display configurations is messed up and if i disconnect (sleep or 
power off) one of my screens, plasma is gone :(

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

Title:
  Crash on screen power save

Status in qtbase-opensource-src package in Ubuntu:
  Fix Released

Bug description:
  Continuation to bug #1548766 to consider another upstream fix from
  https://codereview.qt-project.org/#/c/138681/

  The fix could affect both monitor power saving or attaching/detaching
  cycles.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1551122/+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 1589242] Re: Turning the mouse on or off unlocks the greeter

[Guillaume F]

** Description changed:

  Steps to reproduce:
  - Ensure you have "no security/swiping" enabled for unlocking.
  - Switch the screen off and on, you get the greeter.
  - If your bluetooth mouse in off, turn it on. If it's on, turn it off.
  
  Expected result:
  Nothing in particular, the UX of the greeter does not change between desktop 
and staged mode.
  
  What actually happens:
  The greeter unlocks.
+ 
+ Note that this doesn't happen if there is a security in place (Pin or
+ password) so it's not really a security issue. It also does not happen
+ every time, apparently.

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

Title:
  Turning the mouse on or off unlocks the greeter

Status in unity8 package in Ubuntu:
  New

Bug description:
  Steps to reproduce:
  - Ensure you have "no security/swiping" enabled for unlocking.
  - Switch the screen off and on, you get the greeter.
  - If your bluetooth mouse in off, turn it on. If it's on, turn it off.

  Expected result:
  Nothing in particular, the UX of the greeter does not change between desktop 
and staged mode.

  What actually happens:
  The greeter unlocks.

  Note that this doesn't happen if there is a security in place (Pin or
  password) so it's not really a security issue. It also does not happen
  every time, apparently.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1589242/+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 1584151] Re: When 'apt-get -y dist-upgrade' error: E: Sub-process /usr/bin/dpkg returned an error code (1)

[grofaty]

I was unable to solve this problem and trying to fix this looking around
the web and finally I have manage to broke my system to the
unrecoverable state and so was force to wipe out Ubuntu 14.04 and I
decided to fresh install Ubuntu 16.04.

This bug report can be closed down, because I no longer need help. If
you think it is a bug, you can still leave it open, but I will not be
able to provide any useful info anymore.

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

Title:
  When 'apt-get -y dist-upgrade' error: E: Sub-process /usr/bin/dpkg
  returned an error code (1)

Status in binutils package in Ubuntu:
  New

Bug description:
  After executing: sudo apt-get update && sudo apt-get -y dist-upgrade
  I got bellow error and I just can't get out of it. Trying million of things.

  
  Fetched 132 kB in 12s (10,7 kB/s) 
 
  Reading package lists... Done
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  Calculating upgrade... Done
  The following packages will be upgraded:
binutils
  1 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
  Need to get 0 B/2120 kB of archives.
  After this operation, 8192 B of additional disk space will be used.
  (Reading database ... 432717 files and directories currently installed.)
  Preparing to unpack .../binutils_2.24-5ubuntu14.1_i386.deb ...
  Unpacking binutils (2.24-5ubuntu14.1) over (2.24-5ubuntu14) ...
  dpkg: error processing archive 
/var/cache/apt/archives/binutils_2.24-5ubuntu14.1_i386.deb (--unpack):
   unable to install new version of `/usr/bin/c++filt': Device or resource busy
  Processing triggers for man-db (2.6.7.1-1ubuntu1) ...
  Errors were encountered while processing:
   /var/cache/apt/archives/binutils_2.24-5ubuntu14.1_i386.deb
  E: Sub-process /usr/bin/dpkg returned an error code (1)
  I currently don't have any PPA installed.
  

  I tried bellow commands, but the problem is the same.

  sudo apt-get -f install
  sudo apt-get autoremove
  sudo apt-get clean
  sudo apt-get autoclean
  sudo apt-get update
  sudo apt-get upgrade
  sudo apt-get dist-upgrade

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: binutils 2.24-5ubuntu14
  ProcVersionSignature: Ubuntu 3.13.0-86.131-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-86-generic i686
  ApportVersion: 2.14.1-0ubuntu3.20
  Architecture: i386
  CurrentDesktop: Unity
  Date: Fri May 20 19:14:51 2016
  Dependencies:
   gcc-4.9-base 4.9.3-0ubuntu4
   libc6 2.19-0ubuntu6.7
   libgcc1 1:4.9.3-0ubuntu4
   multiarch-support 2.19-0ubuntu6.7
   zlib1g 1:1.2.8.dfsg-1ubuntu1
  InstallationDate: Installed on 2014-05-23 (728 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140417)
  SourcePackage: binutils
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1584151/+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 1589255] Re: Double login screen In desktop

[Launchpad Bug Tracker]

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: unity8 (Ubuntu)
   Status: New => Confirmed

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

Title:
  Double login screen In desktop

Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  when I turn on the PC and choose unity8 from the login screen I enter the 
password, once entered the password and after that it is loaded unity8 I again 
put the password in the login screen unity8. It should happen as in Unity 7 in 
which you enter directly without having to put your password
  Ubuntu 16.10(daily build)
  Unity8.12+16.10.20160527

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1589255/+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 1589263] [NEW] Xorg freeze

[Anupam Datta]

Public bug reported:

it shows :
acpi failed to set initial power state
drm : pointer to tdms table invalid
drm : pointer to flat panel table invalid

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
Uname: Linux 4.5.2-040502-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
BootLog:
 
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity
Date: Sun Jun  5 20:50:08 2016
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, including running git bisection searches
GpuHangFrequency: This is the first time
GraphicsCard:
 Intel Corporation Broadwell-U Integrated Graphics [8086:1616] (rev 09) 
(prog-if 00 [VGA controller])
   Subsystem: Hewlett-Packard Company Broadwell-U Integrated Graphics 
[103c:80dd]
   Subsystem: Hewlett-Packard Company GM107M [GeForce GTX 950M] [103c:80dd]
InstallationDate: Installed on 2016-02-21 (104 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160214)
MachineType: Hewlett-Packard HP ENVY Notebook
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.5.2-040502-generic 
root=UUID=00a78db6-4e85-4827-a204-386b28d7f737 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/03/2016
dmi.bios.vendor: Insyde
dmi.bios.version: F.35
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: 80DD
dmi.board.vendor: Hewlett-Packard
dmi.board.version: 64.36
dmi.chassis.asset.tag: Chassis Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnInsyde:bvrF.35:bd03/03/2016:svnHewlett-Packard:pnHPENVYNotebook:pvrType1ProductConfigId:rvnHewlett-Packard:rn80DD:rvr64.36:cvnHewlett-Packard:ct10:cvrChassisVersion:
dmi.product.name: HP ENVY Notebook
dmi.product.version: Type1ProductConfigId
dmi.sys.vendor: Hewlett-Packard
version.compiz: compiz 1:0.9.12.2+16.04.20160526-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2
version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2
xserver.bootTime: Mon Jun  6 02:18:14 2016
xserver.configfile: default
xserver.errors:
 Failed to load module "nvidia" (module does not exist, 0)
 Failed to load module "nvidia" (module does not exist, 0)
 Unknown chipset: NV117
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id   14573 
 vendor AUO
xserver.version: 2:1.18.3-1ubuntu2.2

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


** Tags: amd64 apport-bug compiz-0.9 freeze ubuntu xenial

** Attachment added: "dmesg output for better understability"
   
https://bugs.launchpad.net/bugs/1589263/+attachment/4677397/+files/bug_report_dmesg.txt

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

Title:
  Xorg freeze

Status in xorg package in Ubuntu:
  New

Bug description:
  it shows :
  acpi failed to set initial power state
  drm : pointer to tdms table invalid
  drm : pointer to flat panel table invalid

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  Uname: Linux 4.5.2-040502-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  BootLog:
   
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Sun Jun  5 20:50:08 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GpuHangFrequency: This is the first time
  GraphicsCard:
   Intel Corporation Broadwell-U Integrated Graphics [8086:1616] (rev 09) 
(prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Broadwell-U Integrated Graphics 
[103c:80dd]
 Subsystem: Hewlett-Packard Company GM107M [GeForce GTX 950M] [103c:80dd]
  InstallationDate: Installed on 2016-02-21 (104 days 

[Touch-packages] [Bug 1589263] Re: Xorg freeze

[Anupam Datta]

This is problem is persistent even after newer releases. And NVIDIA for
god's sake work with ubuntu. I can not use any GPU inbuilt. Such a
frustrating condition

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

Title:
  Xorg freeze

Status in xorg package in Ubuntu:
  New

Bug description:
  it shows :
  acpi failed to set initial power state
  drm : pointer to tdms table invalid
  drm : pointer to flat panel table invalid

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  Uname: Linux 4.5.2-040502-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  BootLog:
   
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Sun Jun  5 20:50:08 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GpuHangFrequency: This is the first time
  GraphicsCard:
   Intel Corporation Broadwell-U Integrated Graphics [8086:1616] (rev 09) 
(prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Broadwell-U Integrated Graphics 
[103c:80dd]
 Subsystem: Hewlett-Packard Company GM107M [GeForce GTX 950M] [103c:80dd]
  InstallationDate: Installed on 2016-02-21 (104 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160214)
  MachineType: Hewlett-Packard HP ENVY Notebook
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.5.2-040502-generic 
root=UUID=00a78db6-4e85-4827-a204-386b28d7f737 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/03/2016
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.35
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 80DD
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 64.36
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.35:bd03/03/2016:svnHewlett-Packard:pnHPENVYNotebook:pvrType1ProductConfigId:rvnHewlett-Packard:rn80DD:rvr64.36:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.name: HP ENVY Notebook
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.12.2+16.04.20160526-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Mon Jun  6 02:18:14 2016
  xserver.configfile: default
  xserver.errors:
   Failed to load module "nvidia" (module does not exist, 0)
   Failed to load module "nvidia" (module does not exist, 0)
   Unknown chipset: NV117
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   14573 
   vendor AUO
  xserver.version: 2:1.18.3-1ubuntu2.2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1589263/+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 1467930] Re: 0cf3:3004 bluetooth not working atheros 10

[Launchpad Bug Tracker]

*** This bug is a duplicate of bug 1451689 ***
https://bugs.launchpad.net/bugs/1451689

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: bluez (Ubuntu)
   Status: New => Confirmed

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

Title:
  0cf3:3004 bluetooth not working atheros 10

Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  see original bug.
  reported this because the bug also affects me and on apport-collect launchpad 
told me to create a new bug report and mark it as clone.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: bluetooth (not installed)
  ProcVersionSignature: Ubuntu 3.19.0-21.21-generic 3.19.8
  Uname: Linux 3.19.0-21-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.17.2-0ubuntu1.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Jun 23 14:31:15 2015
  InstallationDate: Installed on 2015-06-19 (3 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  InterestingModules: btusb bluetooth
  MachineType: Micro-Star International Co., Ltd. GT72 2QE
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-21-generic 
root=UUID=4fabaada-02c5-4230-a634-0b88cf228b5f ro quiet splash
  SourcePackage: bluez
  UdevLog: Error: [Errno 2] Aucun fichier ou dossier de ce type: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/21/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E1781IMS.10H
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: MS-1781
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: REV:0.C
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE1781IMS.10H:bd11/21/2014:svnMicro-StarInternationalCo.,Ltd.:pnGT722QE:pvrREV0.C:rvnMicro-StarInternationalCo.,Ltd.:rnMS-1781:rvrREV0.C:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrToBeFilledByO.E.M.:
  dmi.product.name: GT72 2QE
  dmi.product.version: REV:0.C
  dmi.sys.vendor: Micro-Star International Co., Ltd.
  hciconfig:
   
  rfkill:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1467930/+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 1589255] [NEW] Double login screen In desktop

[Emanuele Antonio Faraone]

Public bug reported:

when I turn on the PC and choose unity8 from the login screen I enter the 
password, once entered the password and after that it is loaded unity8 I again 
put the password in the login screen unity8. It should happen as in Unity 7 in 
which you enter directly without having to put your password
Ubuntu 16.10(daily build)
Unity8.12+16.10.20160527

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

** Description changed:

  when I turn on the PC and choose unity8 from the login screen I enter the 
password, once entered the password and after that it is loaded unity8 I again 
put the password in the login screen unity8. It should happen as in Unity 7 in 
which you enter directly without having to put your password
  Ubuntu 16.10(daily build)
- Unity8.12
+ Unity8.12+16.10.20160527

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

Title:
  Double login screen In desktop

Status in unity8 package in Ubuntu:
  New

Bug description:
  when I turn on the PC and choose unity8 from the login screen I enter the 
password, once entered the password and after that it is loaded unity8 I again 
put the password in the login screen unity8. It should happen as in Unity 7 in 
which you enter directly without having to put your password
  Ubuntu 16.10(daily build)
  Unity8.12+16.10.20160527

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1589255/+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 1589249] This bug is a duplicate

[Apport retracing service]

*** This bug is a duplicate of bug 1587740 ***
https://bugs.launchpad.net/bugs/1587740

Thank you for taking the time to report this crash and helping to make
this software better.  This particular crash has already been reported
and is a duplicate of bug #1587740, so is being marked as such.  Please
look at the other bug report to see if there is any missing information
that you can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report.  Please continue to report any other bugs you may
find.

** This bug has been marked a duplicate of bug 1587740
   systemd-resolved crashed: Assertion '*_head == _item' failed at 
../src/resolve/resolved-dns-transaction.c:94, function dns_transaction_free().

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  systemd-resolved crashed with SIGABRT

Status in systemd package in Ubuntu:
  New

Bug description:
  previous bugs of this appear to be fix released

  ProblemType: Crash
  DistroRelease: Ubuntu 16.10
  Package: systemd 230-2git1
  ProcVersionSignature: Ubuntu 4.4.0-23.41-generic 4.4.10
  Uname: Linux 4.4.0-23-generic x86_64
  ApportVersion: 2.20.1-0ubuntu4
  Architecture: amd64
  CrashCounter: 1
  Date: Sun Jun  5 15:13:59 2016
  ExecutablePath: /lib/systemd/systemd-resolved
  InstallationDate: Installed on 2016-01-11 (145 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160111)
  MachineType: NOVATECH LTD MBB-44608
  ProcCmdline: /lib/systemd/systemd-resolved
  ProcEnviron:
   LANG=en_GB.UTF-8
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-23-generic 
root=UUID=0e76f726-36fe-4fff-b2aa-bc812147b087 ro quiet splash vt.handoff=7
  Signal: 6
  SourcePackage: systemd
  StacktraceTop:
   ?? ()
   ?? ()
   ?? ()
   ?? ()
   ?? ()
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/systemd-timesyncd.service → 
/lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   
   2 overridden configuration files found.
  Title: systemd-resolved crashed with SIGABRT
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 06/19/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F5
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H81M-DS2V
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: To be filled by O.E.M.
  dmi.chassis.asset.tag: 7383241-001
  dmi.chassis.type: 3
  dmi.chassis.vendor: NOVATECH LTD
  dmi.chassis.version: V1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF5:bd06/19/2014:svnNOVATECHLTD:pnMBB-44608:pvrV1.0:rvnGigabyteTechnologyCo.,Ltd.:rnH81M-DS2V:rvrTobefilledbyO.E.M.:cvnNOVATECHLTD:ct3:cvrV1.0:
  dmi.product.name: MBB-44608
  dmi.product.version: V1.0
  dmi.sys.vendor: NOVATECH LTD

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1589249/+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 1350993] Re: [Dash] Support link should be clickable, app preview shows mailto links with "mailto" text

[padraic]

Still exists in OTA-11. Makes researching apps from appstore
surprisingly tedious and laborious.

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

Title:
  [Dash] Support link should be clickable, app preview shows mailto
  links with "mailto" text

Status in Ubuntu UX:
  In Progress
Status in unity-scope-click package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Incomplete

Bug description:
  When uploading an app to the store we're given a field to put a
  support link in. It's recommended to put an http or mailto link in. I
  have put mailto: links in mine. With the latest click scope I now see
  some details about the app, and the support link actually says
  "mailto:a...@popey.com; when it probably should be clickable whether
  it's a mailto link or an http* link.

  -- UX Comment --

  This is part of a bigger redesign project (Scopes toolkit and scopes
  previews) and it can't be fixed as problem specific to the store app
  preview card, it should take into consideration all card types and
  preview widgets. The desired resolution and specs will be updated as
  soon as they are available.

  As we've already done some work on this project, we are planning to
  support embbeded links in cards preview widgets.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-ux/+bug/1350993/+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 1438510] Re: [REGRESSION] bluetooth headset no longer supports a2dp

[Alexander Menk]

Same problem here. The workaround partially fixes it, but still I have
sometimes problems to connect. Is it dependent on the bluetooth adapter,
headset or both? Are there know-to-work adapters?

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

Title:
  [REGRESSION] bluetooth headset no longer supports a2dp

Status in bluez package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed
Status in bluez source package in Vivid:
  Confirmed
Status in pulseaudio source package in Vivid:
  Confirmed

Bug description:
  Just installed 15.04 fresh from the latest ISO (beta2).

  I'm bummed to see my bluetooth headset (Bose Soundlink overear) seems
  to have regressed in functionality.

  In 14.10, I was able to set the output profile either to a2dp or
  hsp/hfp (telephony duplex).

  In 15.04, it only works in telephony duplex mode.  I can't get high
  fidelity sound playback to work at all.

  This thread seems to be related, though the workaround within did not solve 
the problem for me:
  https://bbs.archlinux.org/viewtopic.php?id=194006

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1438510/+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 1583802] Re: Keyboard layout is not respected in some places

[Guillaume F]

I've just realised that this is extremely problematic on the tablet:
when you set a password to unlock, it will seem to not work in the
greeter because the greeter is stuck in QWERTY...

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

Title:
  Keyboard layout is not respected in some places

Status in Mir:
  New
Status in mir package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Confirmed
Status in unity8-desktop-session package in Ubuntu:
  Incomplete

Bug description:
  I'm trying Unity8 on my desktop (and reporting bugs from there,
  cool!), I've followed Michael Hall's how to, so I have the same PPAs
  on my system.

  The keyboard layout is not the same everywhere in the OS. I switched
  to French and it works in most places, but in some others, an English
  keyboard persists. These other places include the greeter and the
  Online Accounts (the rest of the System Settings app seems fine). I'm
  not sure where else but I'll keep searching.

  I have to say, it has its advantages, since alt-gr does not work and I
  have to copy/paste things like "@"!

  Thanks for your great work, it's really exciting to see the progress!

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1583802/+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 1589242] [NEW] Turning the mouse on or off unlocks the greeter

[Guillaume F]

Public bug reported:

Steps to reproduce:
- Ensure you have "no security/swiping" enabled for unlocking.
- Switch the screen off and on, you get the greeter.
- If your bluetooth mouse in off, turn it on. If it's on, turn it off.

Expected result:
Nothing in particular, the UX of the greeter does not change between desktop 
and staged mode.

What actually happens:
The greeter unlocks.

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

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

Title:
  Turning the mouse on or off unlocks the greeter

Status in unity8 package in Ubuntu:
  New

Bug description:
  Steps to reproduce:
  - Ensure you have "no security/swiping" enabled for unlocking.
  - Switch the screen off and on, you get the greeter.
  - If your bluetooth mouse in off, turn it on. If it's on, turn it off.

  Expected result:
  Nothing in particular, the UX of the greeter does not change between desktop 
and staged mode.

  What actually happens:
  The greeter unlocks.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1589242/+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 1440065] Re: [Address book] Contacts with accent on first letter are not ordered properly

[Guillaume F]

Any news on this? This bug has been present for more than a year and
still no news.

I have no idea how difficult it is to implement, but an address-book
which is incapable of alphabetically sorting contacts is not a very
useful address-book. I understand that in English, this bug might seem
of low priority, but not in other languages!

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

Title:
  [Address book] Contacts with accent on first letter are not ordered
  properly

Status in Ubuntu UX:
  Fix Committed
Status in address-book-app package in Ubuntu:
  New

Bug description:
  My contact list is a bit strange when it comes to the "E" letter. I
  have six different categories, three "E"s and three "É"s. Also, when I
  search for a contact, "E" and "É" are not the same, which is
  inconvenient.

  My contacts come from two Google accounts but it does not seem to be
  the problem, since contacts from both accounts may appear under one
  "E" occurrence.

  This is on the retail bq phone, r20, French locale.

  UX comment--

  My recommendation is not to create new sections for the accent letters but 
accommodate them under their parent letter. This would mean:
  - "É," is in the "E" section, "Ç" is under the "C", "Å" is under the "A" 
section and so on.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-ux/+bug/1440065/+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 1576864] Re: No UMS support in radeon module

[Christopher M. Penalver]

Cgiraud, thank you for reporting this and helping make Ubuntu better.

Could you please run the following command once from a terminal by ensuring you 
have the package xdiagnose installed, and that you click the Yes button for 
attaching additional debugging information:
apport-collect -p xorg 1576864

When reporting xorg related bugs in the future, please do so via the
above method. You can learn more about this functionality at
https://wiki.ubuntu.com/ReportingBugs.

** Changed in: xorg (Ubuntu)
   Importance: Undecided => Low

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

** Summary changed:

- No UMS support in radeon module
+ Unable to extend to second display

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

Title:
  Unable to extend to second display

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Upgrading from UbuntuStudio 15.10 to 16.04, my 2nd display is a no
  more a 1st display extension and only a clone. xrand detects only one
  display.

  $ xrandr
  xrandr: Failed to get size of gamma for output default
  Screen 0: minimum 1400 x 1050, current 1400 x 1050, maximum 1400 x 1050
  default connected 1400x1050+0+0 0mm x 0mm
 1400x1050 77.00* 
  $ lspci -nn | grep VGA
  00:01.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. 
[AMD/ATI] Sumo [Radeon HD 6410D] [1002:9644]
  $ dmesg | egrep 'drm|radeon'
  [1.293303] [drm] Initialized drm 1.1.0 20060810
  [1.328085] [drm] VGACON disable radeon kernel modesetting.
  [1.328109] [drm:radeon_init [radeon]] *ERROR* No UMS support in radeon 
module!
  [   12.801460] [drm] VGACON disable radeon kernel modesetting.
  [   12.801484] [drm:radeon_init [radeon]] *ERROR* No UMS support in radeon 
module!
  $ uname -r 
  4.4.0-21-lowlatency
  $ 

  Seems same than bug 1407505, but apport-bug failed, so I created a new
  bug.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-21.37-lowlatency 4.4.6
  Uname: Linux 4.4.0-21-lowlatency x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Fri Apr 29 23:19:49 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-08-21 (252 days ago)
  InstallationMedia: Ubuntu-Studio 15.04 "Vivid Vervet" - Release amd64 
(20150422)
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to xenial on 2016-04-24 (5 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1576864/+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 919801] Re: Unity dash file search is extremely slow

[Lars Ola Liavåg]

At last, a new Ubuntu release seems to have made a difference. With
Xenial, I'm down to a couple of seconds or less populating the Dash
first time on first login. I'm not sure if it's down to the new release
since I already had a startup command to preload selected scopes
according to Bruno Nova's suggestion under bug #1061852, and I guess the
startup job may hve survuved the upgrade:

/usr/bin/unity-scope-loader applications/applications.scope
applications/scopes.scope commands.scope

Nonetheless, under 15.10, this didn't work anywhere nearly as well as it
does in 16.04, so I guess the underlying problem has benefited from some
of the groundwork in the new release. Just out of curiosity, I'll
probably deactivate the startup job above to see what difference it
makes.

Anyway, having scope access times of less than two seconds on first
login has not happened to me since before 12.04, so finally, Unity 7
seems to reach its full potential - just in time for it to be replaced
by Unity 8...

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

Title:
  Unity dash file search is extremely slow

Status in unity-lens-files:
  Incomplete
Status in Zeitgeist Framework:
  Incomplete
Status in unity-lens-files package in Ubuntu:
  Confirmed
Status in zeitgeist package in Ubuntu:
  Fix Released

Bug description:
  When I try to use the Unity dash search feature to navigate to files
  and folders, it is extremely slow. For example, if I hit the super
  button to launch the search and then type "Pictures" to get my
  pictures directory, it takes almost 5 seconds for the folder icon to
  show. In comparison, if I use Gnome-Do to navigate to my Pictures
  folder, it's basically instant.

  I have attached a video screencast so that you can see the problem for 
yourself.
  --- 
  ApportVersion: 1.23-0ubuntu4
  Architecture: i386
  CompizPlugins: 
[core,bailer,detection,composite,opengl,compiztoolbox,decor,move,vpswitch,place,session,imgpng,mousepoll,resize,gnomecompat,regex,snap,grid,wall,unitymtgrabhandles,animation,expo,ezoom,workarounds,fade,scale,unityshell]
  DistroRelease: Ubuntu 11.10
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Beta i386 (20110413)
  NonfreeKernelModules: nvidia
  Package: unity 5.0.0~+bzr1825ubuntu0+611
  PackageArchitecture: i386
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 3.0.0-14.23-generic 3.0.9
  Tags:  oneiric running-unity
  Uname: Linux 3.0.0-14-generic i686
  UnreportableReason: This is not a genuine Ubuntu package
  UpgradeStatus: Upgraded to oneiric on 2011-10-14 (99 days ago)
  UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity-lens-files/+bug/919801/+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 1575516] Re: Mir is just a black screen and mouse cursor on Nvidia GTX 900

[Launchpad Bug Tracker]

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: mir (Ubuntu)
   Status: New => Confirmed

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

Title:
  Mir is just a black screen and mouse cursor on Nvidia GTX 900

Status in Mir:
  New
Status in mesa package in Ubuntu:
  Invalid
Status in mir package in Ubuntu:
  Confirmed

Bug description:
  Nvidia (using nouveau not binary drivers): Mir servers freeze on
  start-up for 30 seconds, and then you get just a black screen and
  mouse cursor (which at least moves).

  Using lp:mir r3480 ...

  [2016-04-27 15:20:19.369559] mirserver: Selected driver: mir:mesa-kms 
(version 0.22.0)
  nvc0_screen_create:762 - Error allocating PGRAPH context for M2MF: -22
  [2016-04-27 15:20:51.934145] mirserver: Using hardware cursor
  [2016-04-27 15:20:51.937691] mirserver: Initial display configuration:
  [2016-04-27 15:20:51.937703] mirserver:   0.36: unused DVI-I
  [2016-04-27 15:20:51.937713] mirserver:   0.39: DVI-D 24.0" 520x320mm
  [2016-04-27 15:20:51.937722] mirserver: Current mode 1920x1200 59.95Hz
  [2016-04-27 15:20:51.937731] mirserver: Preferred mode 1920x1200 
59.95Hz
  [2016-04-27 15:20:51.937740] mirserver: Logical position +0+0
  [2016-04-27 15:20:51.937781] mirserver:   0.41: unused HDMI-A
  [2016-04-27 15:20:51.937799] mirserver:   0.43: unused DisplayPort
  [2016-04-27 15:20:51.937972] mircommon: Loading modules from: 
bin/../lib/server-modules/
  [2016-04-27 15:20:51.938015] mircommon: Loading module: 
bin/../lib/server-modules/graphics-android.so.9
  [2016-04-27 15:20:51.938107]  mircommon: Failed to load module: 
bin/../lib/server-modules/graphics-android.so.9 (error was:libhardware.so.2: 
cannot open shared object file: No such file or directory)
  [2016-04-27 15:20:51.938119] mircommon: Loading module: 
bin/../lib/server-modules/graphics-mesa-kms.so.9
  [2016-04-27 15:20:51.938142] mircommon: Loading module: 
bin/../lib/server-modules/server-mesa-x11.so.9
  [2016-04-27 15:20:51.938536] mircommon: Loading module: 
bin/../lib/server-modules/input-evdev.so.5
  [2016-04-27 15:20:51.955316] mirserver: Selected input driver: 
mir:evdev-input (version: 0.22.0)
  [2016-04-27 15:20:51.955500] mirserver: Mir version 0.22.0
  [2016-04-27 15:20:51.962627] GLRenderer: EGL vendor: Mesa Project
  [2016-04-27 15:20:51.962645] GLRenderer: EGL version: 1.4 (DRI2)
  [2016-04-27 15:20:51.962651] GLRenderer: EGL client APIs: OpenGL OpenGL_ES 
OpenGL_ES2 OpenGL_ES3
  [2016-04-27 15:20:51.962657] GLRenderer: EGL extensions: EGL_EXT_buffer_age 
EGL_EXT_image_dma_buf_import EGL_KHR_create_context 
EGL_KHR_get_all_proc_addresses EGL_KHR_gl_renderbuffer_image 
EGL_KHR_gl_texture_2D_image EGL_KHR_gl_texture_cubemap_image EGL_KHR_image 
EGL_KHR_image_base EGL_KHR_image_pixmap EGL_KHR_surfaceless_context 
EGL_MESA_configless_context EGL_MESA_image_dma_buf_export
  [2016-04-27 15:20:51.962670] GLRenderer: GL vendor: VMware, Inc.
  [2016-04-27 15:20:51.962679] GLRenderer: GL renderer: Gallium 0.4 on llvmpipe 
(LLVM 3.8, 256 bits)
  [2016-04-27 15:20:51.962688] GLRenderer: GL version: OpenGL ES 3.0 Mesa 11.2.0
  [2016-04-27 15:20:51.962697] GLRenderer: GLSL version: OpenGL ES GLSL ES 3.00

  lspci:
  01:00.0 VGA compatible controller: NVIDIA Corporation GM204 [GeForce GTX 970] 
(rev a1)

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1575516/+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 1118903] Re: [enhancement] Mir lacks a software rendering backend (and doesn't work in virtual machines)

[Emanuele Antonio Faraone]

news?

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

Title:
  [enhancement] Mir lacks a software rendering backend (and doesn't work
  in virtual machines)

Status in Mir:
  Triaged
Status in mesa package in Ubuntu:
  Confirmed
Status in mir package in Ubuntu:
  Triaged

Bug description:
  As always, it's a critical requirement for Ubuntu to be able to render
  the same thing on any machine (metal or virtual), regardless of the
  availability of hardware acceleration.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1118903/+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 1576032] Re: Software compositing of EGL clients is much slower than software compositing of software clients

[Launchpad Bug Tracker]

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: mir (Ubuntu)
   Status: New => Confirmed

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

Title:
  Software compositing of EGL clients is much slower than software
  compositing of software clients

Status in Mir:
  New
Status in mesa package in Ubuntu:
  Confirmed
Status in mir package in Ubuntu:
  Confirmed

Bug description:
  Software compositing of EGL clients is much slower than software
  clients. Even when the EGL client is allowed to render in hardware.
  There is something weirdly slow about our EGL texture binding compared
  to software textures...

  Start the server with software rendering:
  $ sudo env GBM_ALWAYS_SOFTWARE=1 mir_proving_server --compositor-report=log

  Now start a fullscreen client (even with hardware rendering enabled)
  and drag the window around (so it's no longer bypassed).

  Compositor performance:
  7 FPS with mir_demo_client_eglflash (rendered in hardware, only rendering 1 
FPS)
  7 FPS with mir_demo_client_egltriangle (rendered in hardware)
  30 FPS with mir_demo_client_fingerpaint (not redrawing at all)
  30 FPS with 'mir_demo_client_progressbar 1' (rendered in software at 1 FPS)
  30 FPS with 'mir_demo_client_progressbar 60' (rendered in software at 60 FPS)
  30 FPS with 'mir_demo_client_flicker' (rendered in software at 60 FPS)

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1576032/+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 1576032] Re: Software compositing of EGL clients is much slower than software compositing of software clients

[Launchpad Bug Tracker]

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: mesa (Ubuntu)
   Status: New => Confirmed

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

Title:
  Software compositing of EGL clients is much slower than software
  compositing of software clients

Status in Mir:
  New
Status in mesa package in Ubuntu:
  Confirmed
Status in mir package in Ubuntu:
  Confirmed

Bug description:
  Software compositing of EGL clients is much slower than software
  clients. Even when the EGL client is allowed to render in hardware.
  There is something weirdly slow about our EGL texture binding compared
  to software textures...

  Start the server with software rendering:
  $ sudo env GBM_ALWAYS_SOFTWARE=1 mir_proving_server --compositor-report=log

  Now start a fullscreen client (even with hardware rendering enabled)
  and drag the window around (so it's no longer bypassed).

  Compositor performance:
  7 FPS with mir_demo_client_eglflash (rendered in hardware, only rendering 1 
FPS)
  7 FPS with mir_demo_client_egltriangle (rendered in hardware)
  30 FPS with mir_demo_client_fingerpaint (not redrawing at all)
  30 FPS with 'mir_demo_client_progressbar 1' (rendered in software at 1 FPS)
  30 FPS with 'mir_demo_client_progressbar 60' (rendered in software at 60 FPS)
  30 FPS with 'mir_demo_client_flicker' (rendered in software at 60 FPS)

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1576032/+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 978604] Re: Banshee/Rhythmbox regularly stop playing audio when left on in the background

[Otto Rask]

Happening here on Rhythmbox 3.0.2 and Ubuntu 14.04. Packages have been
kept up to date via `apt-get update/upgrade` procedures.

I've installed a PulseAudio Equalizer and set echo cancellation module
on to (try) fix my noisy microphone, but no other "audio mods" are used.

Enabling track crossfade and setting the amount to 0.1s "fixed" this
issue for me.

`syslog` mentions the same message most have been seeing: `Failed to
push data into queue`.

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

Title:
  Banshee/Rhythmbox regularly stop playing audio when left on in the
  background

Status in pulseaudio package in Ubuntu:
  Confirmed
Status in pulseaudio source package in Precise:
  Confirmed

Bug description:
  If Banshee or Rhythmbox is left playing in the background they will
  randomly stop playing in the latest builds of Ubuntu 12.04. Starting a
  new piece of music usually fixes the problem. If left to its own
  devices, the music will start playing again at some random time, at
  some random position. This problem exists on both my desktop machine
  (custom built Intel machine) and my laptop (Macbook 5,1). It has been
  happening for several months now.

  I became frustrated enough to load up pulseaudio in debugging mode.
  The log shows that when the music player just finishes playing one
  piece, and tries to start the next piece, you see something like this:

  ---
  ( 335.399|  34.388) D: [alsa-sink] sink-input.c: Requesting rewind due to 
corking
  ( 335.400|   0.001) D: [alsa-sink] alsa-sink.c: Requested to rewind 65536 
bytes.
  ( 335.400|   0.000) D: [alsa-sink] alsa-sink.c: Limited to 14820 bytes.
  ( 335.400|   0.000) D: [alsa-sink] alsa-sink.c: before: 3705
  ( 335.400|   0.000) D: [alsa-sink] alsa-sink.c: after: 3705
  ( 335.400|   0.000) D: [alsa-sink] alsa-sink.c: Rewound 14820 bytes.
  ( 335.400|   0.000) D: [alsa-sink] sink.c: Processing rewind...
  ( 335.400|   0.000) D: [alsa-sink] sink.c: latency = 1643
  ( 335.400|   0.000) D: [alsa-sink] sink-input.c: Have to rewind 14820 bytes 
on render memblockq.
  ( 335.400|   0.000) D: [alsa-sink] sink-input.c: Have to rewind 14820 bytes 
on implementor.
  ( 335.400|   0.000) D: [alsa-sink] source.c: Processing rewind...
  ( 335.400|   0.000) D: [pulseaudio] module-suspend-on-idle.c: Sink 
alsa_output.pci-_00_1b.0.analog-stereo becomes idle, timeout in 5 seconds.
  ( 335.402|   0.001) D: [alsa-sink] alsa-sink.c: hwbuf_unused=0
  ( 335.402|   0.000) D: [alsa-sink] alsa-sink.c: setting avail_min=15502
  ( 335.402|   0.000) D: [alsa-sink] alsa-sink.c: Requested volume: 0:  34% 1:  
34%
  ( 335.402|   0.000) D: [alsa-sink] alsa-sink.c:in dB: 0: -28.11 
dB 1: -28.11 dB
  ( 335.402|   0.000) D: [alsa-sink] alsa-sink.c: Got hardware volume: 0:  34% 
1:  34%
  ( 335.402|   0.000) D: [alsa-sink] alsa-sink.c:   in dB: 0: 
-28.00 dB 1: -28.00 dB
  ( 335.402|   0.000) D: [alsa-sink] alsa-sink.c: Calculated software volume: 
0: 100% 1: 100% (accurate-enough=yes)
  ( 335.402|   0.000) D: [alsa-sink] alsa-sink.c:  in dB: 
0: -0.11 dB 1: -0.11 dB
  ( 335.402|   0.000) D: [alsa-sink] sink.c: Volume not changing
  ( 335.402|   0.000) D: [alsa-sink] alsa-sink.c: Requested to rewind 65536 
bytes.
  ( 335.402|   0.000) D: [alsa-sink] alsa-sink.c: Limited to 15300 bytes.
  ( 335.402|   0.000) D: [pulseaudio] module-suspend-on-idle.c: Sink 
alsa_output.pci-_00_1b.0.analog-stereo becomes idle, timeout in 5 seconds.
  ( 335.402|   0.000) D: [alsa-sink] alsa-sink.c: before: 3825
  ( 335.402|   0.000) D: [pulseaudio] core.c: Hmm, no streams around, trying to 
vacuum.
  ( 335.402|   0.000) D: [alsa-sink] alsa-sink.c: after: 3825
  ( 335.402|   0.000) D: [alsa-sink] alsa-sink.c: Rewound 15300 bytes.
  ( 335.402|   0.000) D: [alsa-sink] sink.c: Processing rewind...
  ( 335.402|   0.000) D: [alsa-sink] sink.c: latency = 1402
  ( 335.402|   0.000) D: [alsa-sink] source.c: Processing rewind...
  ( 335.402|   0.000) I: [pulseaudio] sink-input.c: Freeing input 3 
"'zero-project - 05 - Forest of the unicorns' by 'zero-project'"
  ( 335.402|   0.000) D: [pulseaudio] module-stream-restore.c: Not restoring 
device for stream sink-input-by-media-role:music, because already set to 
'alsa_output.pci-_00_1b.0.analog-stereo'.
  ( 335.403|   0.000) D: [pulseaudio] module-intended-roles.c: Not setting 
device for stream Playback Stream, because already set.
  ( 335.403|   0.000) I: [pulseaudio] module-stream-restore.c: Restoring volume 
for sink input sink-input-by-media-role:music.
  ( 335.403|   0.000) I: [pulseaudio] module-stream-restore.c: Restoring mute 
state for sink input sink-input-by-media-role:music.
  ( 335.403|   0.000) D: [pulseaudio] module-suspend-on-idle.c: Sink 
alsa_output.pci-_00_1b.0.analog-stereo becomes busy.
  ( 335.403|   0.000) I: 

[Touch-packages] [Bug 1589234] [NEW] Items in the launcher don't move with the mouse

[Guillaume F]

Public bug reported:

When in desktop mode with a mouse and a launcher full of apps, hovering
the cursor on top of the launcher doesn't do anything. It should reveal
stacked icons top and bottom, just like in Unity7.

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

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

Title:
  Items in the launcher don't move with the mouse

Status in unity8 package in Ubuntu:
  New

Bug description:
  When in desktop mode with a mouse and a launcher full of apps,
  hovering the cursor on top of the launcher doesn't do anything. It
  should reveal stacked icons top and bottom, just like in Unity7.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1589234/+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 1589209] Re: package libc6-dev 2.19-0ubuntu6.7 failed to install/upgrade: cannot copy extracted data for './usr/include/elf.h' to '/usr/include/elf.h.dpkg-new': unexpected end of

[Ubuntu Foundations Team Bug Bot]

Thank you for taking the time to report this bug and helping to make
Ubuntu better.  It seems that there was an error on your system when
trying to install a particular package.  Please execute the following
command, as it will clear your package cache, in a terminal:

sudo apt-get clean

Then try performing the update again.  This will likely resolve your
issue, but the failure could be caused by filesystem or memory
corruption.  So please also run a fsck on your filesystem(s) and a
memory test.  Thanks in advance!

[This is an automated message.  I apologize if it reached you
inappropriately; please just reply to this message indicating so.]

** Tags added: corrupted-package

** Changed in: eglibc (Ubuntu)
   Status: New => Invalid

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

Title:
  package libc6-dev 2.19-0ubuntu6.7 failed to install/upgrade: cannot
  copy extracted data for './usr/include/elf.h' to '/usr/include/elf.h
  .dpkg-new': unexpected end of file or stream

Status in eglibc package in Ubuntu:
  Invalid

Bug description:
  Just doing an update

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: libc6-dev 2.19-0ubuntu6.7
  ProcVersionSignature: Ubuntu 3.13.0-83.127-generic 3.13.11-ckt35
  Uname: Linux 3.13.0-83-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  Date: Sun Jun  5 11:09:38 2016
  DuplicateSignature: package:libc6-dev:2.19-0ubuntu6.7:cannot copy extracted 
data for './usr/include/elf.h' to '/usr/include/elf.h.dpkg-new': unexpected end 
of file or stream
  ErrorMessage: cannot copy extracted data for './usr/include/elf.h' to 
'/usr/include/elf.h.dpkg-new': unexpected end of file or stream
  InstallationDate: Installed on 2015-01-24 (497 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.6
   apt  1.0.1ubuntu2.11
  SourcePackage: eglibc
  Title: package libc6-dev 2.19-0ubuntu6.7 failed to install/upgrade: cannot 
copy extracted data for './usr/include/elf.h' to '/usr/include/elf.h.dpkg-new': 
unexpected end of file or stream
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/eglibc/+bug/1589209/+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 1490349] Re: 15:10: bluetoothd reports "Not enough handles to register service" at start

[maarten derksen]

I switched to Gnome, where I do not have this problem. Apparently it has
something to do with Unity.

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

Title:
  15:10: bluetoothd reports "Not enough handles to register service" at
  start

Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  On 15:10 after the bluetooth service has been stopped and restarted it
  is not possible to scan or connect to devices:

  $ sudo systemctl start bluetooth
  $ journalctl --unit=bluetooth | tail -n 19 | awk '{$1="";$2="";$4="";print 
$0}'
23:31:53  systemd[1]: Starting Bluetooth service...
23:31:53  bluetoothd[16647]: Bluetooth daemon 5.33
23:31:53  systemd[1]: Started Bluetooth service.
23:31:53  bluetoothd[16647]: Starting SDP server
23:31:53  bluetoothd[16647]: Bluetooth management interface 1.9 initialized
23:31:53  bluetoothd[16647]: Failed to obtain handles for "Service Changed" 
characteristic
23:31:53  bluetoothd[16647]: Not enough free handles to register service
23:31:53  bluetoothd[16647]: Error adding Link Loss service
23:31:53  bluetoothd[16647]: Not enough free handles to register service
23:31:53  bluetoothd[16647]: Not enough free handles to register service
23:31:53  bluetoothd[16647]: Not enough free handles to register service
23:31:53  bluetoothd[16647]: Current Time Service could not be registered
23:31:53  bluetoothd[16647]: gatt-time-server: Input/output error (5)
23:31:53  bluetoothd[16647]: Not enough free handles to register service
23:31:53  bluetoothd[16647]: Not enough free handles to register service
23:31:53  bluetoothd[16647]: Sap driver initialization failed.
23:31:53  bluetoothd[16647]: sap-server: Operation not permitted (1)
23:31:53  bluetoothd[16647]: Endpoint registered: sender=:1.440 
path=/MediaEndpoint/A2DPSource
23:31:53  bluetoothd[16647]: Endpoint registered: sender=:1.440 
path=/MediaEndpoint/A2DPSink

  And

  $ bluetoothctl
  [NEW] Controller 00:1F:3A:E0:0A:AF hephaestion.lan.iam.tj [default]
  [NEW] Device 00:0A:95:4B:BD:C2 Apple Wireless Keyboard
  [NEW] Device 00:07:61:3B:86:98 Bluetooth Travel Mouse
  [bluetooth]# scan on
  Failed to start discovery: org.bluez.Error.NotReady

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1490349/+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 1413818] Re: Notification sounds aren't being played back on E4.5 (ubuntu-push restricts directories and block custom sounds)

[groby]

Thanks Viktor!

After restarting the phone, it plays the notification sounds again. I
think the problem depends on uRadio. I opened the app and changed a
channel, the sound of uRadio stopped and Telegram doesn't play the
notification sounds anymore, until restarting the phone. Then the same
game again. So it must be a bug in uRadio.

Regards,
Groby

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

Title:
  Notification sounds aren't being played back on E4.5 (ubuntu-push
  restricts directories and block custom sounds)

Status in Canonical System Image:
  Fix Released
Status in The Savilerow project:
  Invalid
Status in ubuntu-push package in Ubuntu:
  Fix Released
Status in ubuntu-touch-session package in Ubuntu:
  Fix Released
Status in ubuntu-touch-session package in Ubuntu RTM:
  Fix Released

Bug description:
  This affects mostly the push notifications based alerts, SMS et.al.
  work fine.

  With export PULSE_PROP='media.role=alert'

  This has no audible output: paplay 
/usr/share/sounds/ubuntu/notifications/Slick.ogg
  This does:  paplay /usr/share/sounds/ubuntu/ringtones/Soul.ogg

  $ system-image-cli -i
  current build number: 14
  device name: mako
  channel: ubuntu-touch/stable
  alias: ubuntu-touch/ubuntu-rtm/14.09
  last update: 2015-01-16 13:12:29
  version version: 14
  version ubuntu: 20150116
  version device: 20141119
  version custom: mako-1.1

  The hunch is some buffering going on on the android side for short
  sound bytes.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1413818/+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 1094744] Re: MS Sculpt Touch Mouse needs to be re-paired periodically

[nathan]

** Changed in: blueman (Ubuntu Quantal)
   Status: New => Invalid

** Changed in: blueman (Ubuntu Raring)
   Status: New => Invalid

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

Title:
  MS Sculpt Touch Mouse needs to be re-paired periodically

Status in GNOME Bluetooth:
  Fix Released
Status in blueman package in Ubuntu:
  New
Status in bluez package in Ubuntu:
  Confirmed
Status in gnome-bluetooth package in Ubuntu:
  Fix Released
Status in blueman source package in Precise:
  New
Status in bluez source package in Precise:
  Confirmed
Status in gnome-bluetooth source package in Precise:
  Fix Released
Status in blueman source package in Quantal:
  Invalid
Status in bluez source package in Quantal:
  Won't Fix
Status in gnome-bluetooth source package in Quantal:
  Fix Released
Status in blueman source package in Raring:
  Invalid
Status in bluez source package in Raring:
  Won't Fix
Status in gnome-bluetooth source package in Raring:
  Won't Fix
Status in bluez package in Fedora:
  Unknown

Bug description:
  [Impact] The patch makes Microsoft Wedge/Sculpt Touch mice stay connected.
  [Test Case] Get a Microsoft Wedge/Sculpt Touch mouse, pair it, restart 
session, watch it automatically re-pair.
  [Regression Potential] Little. The patched piece of XML is only relevant to 
hardware having the same ID.

  When you don't use the mouse for a long enough time, the mouse
  disconnects and won't reconnect. I have to go into bluetooth settings,
  remove it, and re-pair it.

  1)
  ~ % lsb_release -rd
  Description:  Ubuntu 12.04.1 LTS
  Release:  12.04

  2)
  ~ % apt-cache policy bluez
  bluez:
    Installed: 4.98-2ubuntu7
    Candidate: 4.98-2ubuntu7
    Version table:
   *** 4.98-2ubuntu7 0
  500 http://us.archive.ubuntu.com/ubuntu/ precise/main amd64 Packages
  100 /var/lib/dpkg/status

  3)
  I expected the mouse to reconnect automatically, or at least after I try to 
reconnect manually through the bluetooth settings.

  4)
  I have to re-pair the mouse in order to use it again. Turning the mouse off 
and on doesn't work either.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-bluetooth/+bug/1094744/+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 1094744] Re: MS Sculpt Touch Mouse needs to be re-paired periodically

[Martin Wimpress]

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

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

Title:
  MS Sculpt Touch Mouse needs to be re-paired periodically

Status in GNOME Bluetooth:
  Fix Released
Status in blueman package in Ubuntu:
  New
Status in bluez package in Ubuntu:
  Confirmed
Status in gnome-bluetooth package in Ubuntu:
  Fix Released
Status in blueman source package in Precise:
  New
Status in bluez source package in Precise:
  Confirmed
Status in gnome-bluetooth source package in Precise:
  Fix Released
Status in blueman source package in Quantal:
  New
Status in bluez source package in Quantal:
  Won't Fix
Status in gnome-bluetooth source package in Quantal:
  Fix Released
Status in blueman source package in Raring:
  New
Status in bluez source package in Raring:
  Won't Fix
Status in gnome-bluetooth source package in Raring:
  Won't Fix
Status in bluez package in Fedora:
  Unknown

Bug description:
  [Impact] The patch makes Microsoft Wedge/Sculpt Touch mice stay connected.
  [Test Case] Get a Microsoft Wedge/Sculpt Touch mouse, pair it, restart 
session, watch it automatically re-pair.
  [Regression Potential] Little. The patched piece of XML is only relevant to 
hardware having the same ID.

  When you don't use the mouse for a long enough time, the mouse
  disconnects and won't reconnect. I have to go into bluetooth settings,
  remove it, and re-pair it.

  1)
  ~ % lsb_release -rd
  Description:  Ubuntu 12.04.1 LTS
  Release:  12.04

  2)
  ~ % apt-cache policy bluez
  bluez:
    Installed: 4.98-2ubuntu7
    Candidate: 4.98-2ubuntu7
    Version table:
   *** 4.98-2ubuntu7 0
  500 http://us.archive.ubuntu.com/ubuntu/ precise/main amd64 Packages
  100 /var/lib/dpkg/status

  3)
  I expected the mouse to reconnect automatically, or at least after I try to 
reconnect manually through the bluetooth settings.

  4)
  I have to re-pair the mouse in order to use it again. Turning the mouse off 
and on doesn't work either.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-bluetooth/+bug/1094744/+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 1589060] Re: Refresh Scopes in landscape mode not possible

[Alan Pope ]

It is actually possible, but really hard. You have to pull down from
right at the top of the screen to the very bottom.

** Also affects: canonical-devices-system-image
   Importance: Undecided
   Status: New

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

Title:
  Refresh Scopes in landscape mode not possible

Status in Canonical System Image:
  New
Status in unity-scopes-shell package in Ubuntu:
  Confirmed

Bug description:
  On bq Aquaris E4.5 one cannot refresh scopes in landscape mode since
  the scree is too small. There is not enough screen to pull down in
  order to refresh.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1589060/+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 1589220] [NEW] Launching a sidestage app in portrait and spreading, app won't focus

[Guillaume F]

Public bug reported:

Steps to reproduce:
- tablet in portrait view
- launch an app that you know to be in sidestage mode
- spread apps with a right swipe
- turn the tablet back in landscape view
- try to focus on the recently opened sidestage app

Expected result:
The app goes in the foreground, in sidestage.

Current result:
I don't know exactly: if you spread slowly, you can glimpse the "use three 
fingers" screen that you get when no app is in sidestage, and selecting the 
newly opened app won't work and focuses on another one. Switching to yet 
another app, the sidestage app finally shows.

Not sure my description is very clear but hopefully it will be easy to
reproduce!

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

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

Title:
  Launching a sidestage app in portrait and spreading, app won't focus

Status in unity8 package in Ubuntu:
  New

Bug description:
  Steps to reproduce:
  - tablet in portrait view
  - launch an app that you know to be in sidestage mode
  - spread apps with a right swipe
  - turn the tablet back in landscape view
  - try to focus on the recently opened sidestage app

  Expected result:
  The app goes in the foreground, in sidestage.

  Current result:
  I don't know exactly: if you spread slowly, you can glimpse the "use three 
fingers" screen that you get when no app is in sidestage, and selecting the 
newly opened app won't work and focuses on another one. Switching to yet 
another app, the sidestage app finally shows.

  Not sure my description is very clear but hopefully it will be easy to
  reproduce!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1589220/+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 1574347] Re: [SRU] Re-read the link type if the name changed

[Hansen]

Could someone with a bit of technical insight open a new bug please.

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

Title:
  [SRU] Re-read the link type if the name changed

Status in NetworkManager:
  Fix Released
Status in OEM Priority Project:
  New
Status in network-manager package in Ubuntu:
  Fix Released
Status in network-manager source package in Xenial:
  Fix Released

Bug description:
  [Impact]
  NM needs to re-read the DEVTYPE after the device name changed, an example is 
that WiFi network list disappears from network manager applet

  [Testcase]
  1. Boot the system. It should include a wireless device.
  2. In a terminal, run 'nmcli dev'.
  3. In the correct case, the line for the wireless device should read "wifi" 
under the TYPE column. In a failure case, it will read "ethernet".

  After upgrading to the new version, the repeating the above steps
  should give expected behavior.

  [Regression Potential]
  Potential of causing regression is relatively small for a one line change to 
re-read a value to be known.

  ---

  Problems:-

  1. The network manager applet does not show the list of WiFI APs it can find.
  2. The network manager applet does not the name of the AP to which it is 
connected
  3. The icon of the applet shows two vertical arrows in opposite direction - 
the wired connection symbol and NOT the wifi connected icon.

  Temporary Workaround:-
  Log out and again log back in.

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager/+bug/1574347/+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 1575604] Re: Fast repeated scrolling with a finger changes direction of the scrolling

[Harry Chapman]

This bug is really annoying. I get it on my MX5 (15.04, OTA 11) and
makes reading things on the internet a frustrating experience.

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

Title:
  Fast repeated scrolling with a finger changes direction of the
  scrolling

Status in Oxide:
  Triaged
Status in webbrowser-app package in Ubuntu:
  Confirmed

Bug description:
  When scrolling on a page with repeated gestures with the finger on the
  screen, it often changes the direction of the scrolling and scrolls
  super fast.  So if I am far down on a page and scrolls a few times
  with  the finger, it suddenly start to scroll upwards super fast to
  the top.

  It seems like it happens if it lags while scrolling and it misses part
  of the gesture.

  Experienced on an M10 with OTA-10.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/oxide/+bug/1575604/+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 1589089] Re: Impossible to use webbrowser for anything that uses a popup

[Launchpad Bug Tracker]

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: webbrowser-app (Ubuntu)
   Status: New => Confirmed

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

Title:
  Impossible to use webbrowser for anything that uses a popup

Status in webbrowser-app package in Ubuntu:
  Confirmed

Bug description:
  today I wanted to configure a WiFi router with the Ubuntu browser.
  Turns out that's not possible because the router's webinterface uses
  popups to ask the user for selecting something. The popups are opened
  as new tabs. When I switch to them, and then click on the selection
  the popup closes again and I end up on the original page, however, the
  page reloads and all the previous state is lost.

  => The webbrowser should not reload the page when switching to a tab.

  (I presume the reason is that it actually unloads the page as soon as
  one switches away in order to save some memory, but still this is too
  intrusive. It will break too much and needs to be turned off again -
  It kinda makes the webbrowser useless as it is right now.)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1589089/+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 1574347] Re: [SRU] Re-read the link type if the name changed

[Aron Xu]

Please open another report if there is other (probably looks the same)
issues because this update has released which indeed fixes the problem
in current description, but there might be other bugs that may result
into similar behavior.

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

Title:
  [SRU] Re-read the link type if the name changed

Status in NetworkManager:
  Fix Released
Status in OEM Priority Project:
  New
Status in network-manager package in Ubuntu:
  Fix Released
Status in network-manager source package in Xenial:
  Fix Released

Bug description:
  [Impact]
  NM needs to re-read the DEVTYPE after the device name changed, an example is 
that WiFi network list disappears from network manager applet

  [Testcase]
  1. Boot the system. It should include a wireless device.
  2. In a terminal, run 'nmcli dev'.
  3. In the correct case, the line for the wireless device should read "wifi" 
under the TYPE column. In a failure case, it will read "ethernet".

  After upgrading to the new version, the repeating the above steps
  should give expected behavior.

  [Regression Potential]
  Potential of causing regression is relatively small for a one line change to 
re-read a value to be known.

  ---

  Problems:-

  1. The network manager applet does not show the list of WiFI APs it can find.
  2. The network manager applet does not the name of the AP to which it is 
connected
  3. The icon of the applet shows two vertical arrows in opposite direction - 
the wired connection symbol and NOT the wifi connected icon.

  Temporary Workaround:-
  Log out and again log back in.

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager/+bug/1574347/+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 1342400] Re: avahi-daemon constantly reporting "Invalid response packet from host"

[clement.analogue]

Hello,

I am affected by this bug on Ubuntu 14.04. I am working in a scientific
institute with almost a thousand computers. I received 48 millions
entries in syslog the last 48 hours, making a 4.4GB file :/

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

Title:
  avahi-daemon constantly reporting "Invalid response packet from host"

Status in avahi package in Ubuntu:
  Confirmed

Bug description:
  After installing Ubuntu 14.04 (Release: 14.04) and looking for other
  information in /var/log/syslog, I see that syslog is being flooded by
  "Invalid response packet from host" messages from avahi-daemon.

  I searched around to see why this might be and ran across the following avahi 
mailing list post along with a patch to fix it:
  http://lists.freedesktop.org/archives/avahi/2012-July/002171.html

  >>>
  I would say you can safely ignore it, since any machine on your
  network running a recent OSX version will cause these messages.
  Here's a patch with what we change to avoid these messages flooding
  syslog.

  -Justin
  <<<

  The patch which fixes this is here:
  
http://lists.freedesktop.org/archives/avahi/attachments/20120719/1e71846e/attachment.obj

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1342400/+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 1589204] Re: apt-get dist-upgrade and apt full-upgrade not reporting held back package

[Colin Law]

Sorry, it is apt-get upgrade that shows 1 not to upgrade.
Description corrected.

** Description changed:

  I have the situation where a package cannot be upgraded because of missing 
dependencies.  However
  sudo apt-get dist-upgrade
  and
  sudo apt full-upgrade
  and
  sudo apt upgrade
  all show
  0 to upgrade, 0 to newly install, 0 to remove and 0 not to upgrade.
  
  Only
- sudo apt upgrade
+ sudo apt-get upgrade
  shows
  0 to upgrade, 0 to newly install, 0 to remove and 1 not to upgrade.
  
  I believe all of the above commands should show that 1 cannot be
  upgraded.
  
  This bug is not about the particular package I am trying to install, but 
about the way apt reports the problem.
  The details, for reference, are that I am trying to upgrade mosquitto from 
the mosquitto ppa.  After apt-get update I see
  $ apt-cache policy mosquitto
  mosquitto:
-   Installed: 1.4.8-1build1
-   Candidate: 1.4.9-0mosquitto1
-   Version table:
-  1.4.9-0mosquitto1 500
- 500 http://ppa.launchpad.net/mosquitto-dev/mosquitto-ppa/ubuntu 
xenial/main amd64 Packages
-  *** 1.4.8-1build1 500
- 500 http://gb.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages
- 100 /var/lib/dpkg/status
+   Installed: 1.4.8-1build1
+   Candidate: 1.4.9-0mosquitto1
+   Version table:
+  1.4.9-0mosquitto1 500
+ 500 http://ppa.launchpad.net/mosquitto-dev/mosquitto-ppa/ubuntu 
xenial/main amd64 Packages
+  *** 1.4.8-1build1 500
+ 500 http://gb.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages
+ 100 /var/lib/dpkg/status
  
  but if I try to manually install mosquitto I get
  
  The following packages have unmet dependencies.
-  mosquitto : Depends: libwebsockets3 (>= 1.2) but it is not installable
+  mosquitto : Depends: libwebsockets3 (>= 1.2) but it is not installable
  
  and
  
  $ apt-cache policy libwebsockets3
  libwebsockets3:
-   Installed: (none)
-   Candidate: (none)
+   Installed: (none)
+   Candidate: (none)
  Due to the fact that libwebsockets3 is not available for Xenial.
  As I said this bug is not about the problem with this particular package but 
about the fact that apt does not report that there is a package to be upgraded, 
but it cannot be done.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: apt 1.2.12~ubuntu16.04.1
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Jun  5 08:45:33 2016
  InstallationDate: Installed on 2014-10-21 (592 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20141017)
  SourcePackage: apt
  UpgradeStatus: Upgraded to xenial on 2016-03-06 (90 days ago)

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

Title:
  apt-get dist-upgrade and apt full-upgrade not reporting held back
  package

Status in apt package in Ubuntu:
  New

Bug description:
  I have the situation where a package cannot be upgraded because of missing 
dependencies.  However
  sudo apt-get dist-upgrade
  and
  sudo apt full-upgrade
  and
  sudo apt upgrade
  all show
  0 to upgrade, 0 to newly install, 0 to remove and 0 not to upgrade.

  Only
  sudo apt-get upgrade
  shows
  0 to upgrade, 0 to newly install, 0 to remove and 1 not to upgrade.

  I believe all of the above commands should show that 1 cannot be
  upgraded.

  This bug is not about the particular package I am trying to install, but 
about the way apt reports the problem.
  The details, for reference, are that I am trying to upgrade mosquitto from 
the mosquitto ppa.  After apt-get update I see
  $ apt-cache policy mosquitto
  mosquitto:
    Installed: 1.4.8-1build1
    Candidate: 1.4.9-0mosquitto1
    Version table:
   1.4.9-0mosquitto1 500
  500 http://ppa.launchpad.net/mosquitto-dev/mosquitto-ppa/ubuntu 
xenial/main amd64 Packages
   *** 1.4.8-1build1 500
  500 http://gb.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages
  100 /var/lib/dpkg/status

  but if I try to manually install mosquitto I get

  The following packages have unmet dependencies.
   mosquitto : Depends: libwebsockets3 (>= 1.2) but it is not installable

  and

  $ apt-cache policy libwebsockets3
  libwebsockets3:
    Installed: (none)
    Candidate: (none)
  Due to the fact that libwebsockets3 is not available for Xenial.
  As I said this bug is not about the problem with this particular package but 
about the fact that apt does not report that there is a package to be upgraded, 
but it cannot be done.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: apt 1.2.12~ubuntu16.04.1
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Jun  5 08:45:33 2016
  

[Touch-packages] [Bug 874535] Re: Volume Slider Jumps, due to rapidly changing hardware jack sense state

[ST.Pottie]

I've also got this problem in 16.04...

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

Title:
  Volume Slider Jumps, due to rapidly changing hardware jack sense state

Status in alsa-driver package in Ubuntu:
  Triaged

Bug description:
  In Oneiric Release,  The volume slider randomly jump down a notch or
  two for fraction of  a second, even when there is no audio playing on
  the system.  If mute is selected, the menu will quickly flip out of
  mute mode and back again.  This change actually affects the audio
  output, resulting in pops correlated with the volume changes.

  nVidia GF106 Audio Controller
  --- 
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  ApportVersion: 1.23-0ubuntu4
  Architecture: amd64
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: Intel [HDA Intel], device 0: ALC892 Analog [ALC892 Analog]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jfrorie9959 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xfb9f8000 irq 54'
 Mixer name : 'Realtek ALC892'
 Components : 'HDA:10ec0892,1462522c,00100302'
 Controls  : 35
 Simple ctrls  : 20
  Card2.Amixer.info:
   Card hw:2 'Generic'/'HD-Audio Generic at 0xfbcf8000 irq 55'
 Mixer name : 'ATI R6xx HDMI'
 Components : 'HDA:1002aa01,00aa0100,00100200'
 Controls  : 4
 Simple ctrls  : 1
  Card2.Amixer.values:
   Simple mixer control 'IEC958',0
 Capabilities: pswitch pswitch-joined penum
 Playback channels: Mono
 Mono: Playback [on]
  DistroRelease: Ubuntu 11.10
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
  Package: pulseaudio 1:1.0-0ubuntu3.1
  PackageArchitecture: amd64
  ProcEnviron:
   PATH=(custom, user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 3.0.0-14.23-generic 3.0.9
  Tags:  oneiric running-unity
  Uname: Linux 3.0.0-14-generic x86_64
  UpgradeStatus: Upgraded to oneiric on 2011-10-14 (82 days ago)
  UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
  dmi.bios.date: 11/16/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V25.0
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: X58A-GD45 (MS-7522)
  dmi.board.vendor: MSI
  dmi.board.version: 5.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MICRO-STAR INTERNATIONAL CO.,LTD
  dmi.chassis.version: 5.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV25.0:bd11/16/2010:svnMSI:pnMS-7522:pvr5.0:rvnMSI:rnX58A-GD45(MS-7522):rvr5.0:cvnMICRO-STARINTERNATIONALCO.,LTD:ct3:cvr5.0:
  dmi.product.name: MS-7522
  dmi.product.version: 5.0
  dmi.sys.vendor: MSI

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/874535/+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 1574347] Re: [SRU] Re-read the link type if the name changed

[Hansen]

I'm not a specialist in these procedures, but it's easy enough to change the 
status of the bug, the problem are getting the attention of the proper people. 
In my experience it's not easy getting them back when the have left already.
I think the best way are if we make a new bug, have have as many people as 
possible to subscribe to it at possible.
A key part are to report it right.

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

Title:
  [SRU] Re-read the link type if the name changed

Status in NetworkManager:
  Fix Released
Status in OEM Priority Project:
  New
Status in network-manager package in Ubuntu:
  Fix Released
Status in network-manager source package in Xenial:
  Fix Released

Bug description:
  [Impact]
  NM needs to re-read the DEVTYPE after the device name changed, an example is 
that WiFi network list disappears from network manager applet

  [Testcase]
  1. Boot the system. It should include a wireless device.
  2. In a terminal, run 'nmcli dev'.
  3. In the correct case, the line for the wireless device should read "wifi" 
under the TYPE column. In a failure case, it will read "ethernet".

  After upgrading to the new version, the repeating the above steps
  should give expected behavior.

  [Regression Potential]
  Potential of causing regression is relatively small for a one line change to 
re-read a value to be known.

  ---

  Problems:-

  1. The network manager applet does not show the list of WiFI APs it can find.
  2. The network manager applet does not the name of the AP to which it is 
connected
  3. The icon of the applet shows two vertical arrows in opposite direction - 
the wired connection symbol and NOT the wifi connected icon.

  Temporary Workaround:-
  Log out and again log back in.

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager/+bug/1574347/+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 1589209] [NEW] package libc6-dev 2.19-0ubuntu6.7 failed to install/upgrade: cannot copy extracted data for './usr/include/elf.h' to '/usr/include/elf.h.dpkg-new': unexpected end

[smogol]

Public bug reported:

Just doing an update

ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: libc6-dev 2.19-0ubuntu6.7
ProcVersionSignature: Ubuntu 3.13.0-83.127-generic 3.13.11-ckt35
Uname: Linux 3.13.0-83-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.14.1-0ubuntu3.19
Architecture: amd64
Date: Sun Jun  5 11:09:38 2016
DuplicateSignature: package:libc6-dev:2.19-0ubuntu6.7:cannot copy extracted 
data for './usr/include/elf.h' to '/usr/include/elf.h.dpkg-new': unexpected end 
of file or stream
ErrorMessage: cannot copy extracted data for './usr/include/elf.h' to 
'/usr/include/elf.h.dpkg-new': unexpected end of file or stream
InstallationDate: Installed on 2015-01-24 (497 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2)
RelatedPackageVersions:
 dpkg 1.17.5ubuntu5.6
 apt  1.0.1ubuntu2.11
SourcePackage: eglibc
Title: package libc6-dev 2.19-0ubuntu6.7 failed to install/upgrade: cannot copy 
extracted data for './usr/include/elf.h' to '/usr/include/elf.h.dpkg-new': 
unexpected end of file or stream
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package need-duplicate-check trusty

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

Title:
  package libc6-dev 2.19-0ubuntu6.7 failed to install/upgrade: cannot
  copy extracted data for './usr/include/elf.h' to '/usr/include/elf.h
  .dpkg-new': unexpected end of file or stream

Status in eglibc package in Ubuntu:
  New

Bug description:
  Just doing an update

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: libc6-dev 2.19-0ubuntu6.7
  ProcVersionSignature: Ubuntu 3.13.0-83.127-generic 3.13.11-ckt35
  Uname: Linux 3.13.0-83-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  Date: Sun Jun  5 11:09:38 2016
  DuplicateSignature: package:libc6-dev:2.19-0ubuntu6.7:cannot copy extracted 
data for './usr/include/elf.h' to '/usr/include/elf.h.dpkg-new': unexpected end 
of file or stream
  ErrorMessage: cannot copy extracted data for './usr/include/elf.h' to 
'/usr/include/elf.h.dpkg-new': unexpected end of file or stream
  InstallationDate: Installed on 2015-01-24 (497 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.6
   apt  1.0.1ubuntu2.11
  SourcePackage: eglibc
  Title: package libc6-dev 2.19-0ubuntu6.7 failed to install/upgrade: cannot 
copy extracted data for './usr/include/elf.h' to '/usr/include/elf.h.dpkg-new': 
unexpected end of file or stream
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/eglibc/+bug/1589209/+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 1316634] Re: Does not automatically reconnect to hidden WiFi network

[Alf Haakon Lund]

Running Ubuntu Studio (Xubuntu) 14.04 I had this or a very similar
problem when I changed name and hid the SSID on my wifi.

nm-manager kept looking for the old SSID and would not connect to the
hidden network - I had to connect manually on boot.

When I told nm-manager to forget the old wifi the problem disappeared.
My computer now connects to the hidden SSID and networking is OK.

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

Title:
  Does not automatically reconnect to hidden WiFi network

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Running Lubuntu 14.04 32-bit on a Lenovo 3000 C200 laptop with an
  integrated Broadcom network adapter, I installed
  firmware-b43-installer and then successfully connected to my hidden
  (SSID not broadcast) WiFi net.

  But I see that it will not automatically reconnect.  I don't have to
  re-enter the password, but I do have to click the nm-applet indicator,
  choose 'Connect to Hidden Wi-Fi Network' and then choose my already-
  defined connection, which indeed has been saved but not used to
  automatically reconnect.

  If I edit the connection, I see that on the General tab it is already
  set to 'Automatically connect to this network when it is available.'

  The only way I can get automatic reconnection is to enable SSID
  Broadcast.

  And a similar effect: If I am connected to the network while SSID
  Broadcast is in effect and then disable SSID Broadcast, network-
  manager immediately loses the connection.

  Someone suggested that network-manager would find the hidden network
  if I just waited, but after waiting 15 minutes it had still not
  connected.

  Dual-booting this same laptop with Windows Vista, I see that Windows
  knows how to automatically reconnect to the hidden net.

  I see that https://bugs.launchpad.net/ubuntu/+source/network-
  manager/+bug/295796 describes similar behavior, but that was reported
  back in 2008 and I'm imagining that there should be a separate report
  for the new release.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: network-manager 0.9.8.8-0ubuntu7
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic i686
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: i386
  CRDA: Error: [Errno 2] No such file or directory: 'iw'
  CurrentDesktop: LXDE
  Date: Tue May  6 10:24:32 2014
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2014-04-25 (10 days ago)
  InstallationMedia: Lubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140416.2)
  IpRoute:
   default via 192.168.1.1 dev wlan0  proto static 
   192.168.1.0/24 dev wlan0  proto kernel  scope link  src 192.168.1.118  
metric 9
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAME  UUID   TYPE
  TIMESTAMPTIMESTAMP-REAL AUTOCONNECT   READONLY   
DBUS-PATH 
   Wired connection 1ac7ba941-660f-40c5-9b1f-4d24accc6225   
802-3-ethernet1399385892   Tue 06 May 2014 10:18:12 AM EDTyes   
no /org/freedesktop/NetworkManager/Settings/1
   PRP   d25473c0-98d8-4d93-ab37-3dd070bbd34b   
802-11-wireless   1399386192   Tue 06 May 2014 10:23:12 AM EDTyes   
no /org/freedesktop/NetworkManager/Settings/0
  nmcli-dev:
   DEVICE TYPE  STATE DBUS-PATH 
 
   eth0   802-3-ethernetunavailable   
/org/freedesktop/NetworkManager/Devices/1  
   wlan0  802-11-wireless   connected 
/org/freedesktop/NetworkManager/Devices/0
  nmcli-nm:
   RUNNING VERSIONSTATE   NET-ENABLED   WIFI-HARDWARE   
WIFI   WWAN-HARDWARE   WWAN  
   running 0.9.8.8connected   enabled   enabled 
enabledenabled disabled

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