[Touch-packages] [Bug 1556493] Re: package perl-modules 5.20.2-6ubuntu0.2 failed to install/upgrade: package perl-modules is already installed and configured

[dino99]

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

** This bug is no longer a duplicate of bug 1556491
   package perl-modules 5.20.2-6ubuntu0.2 failed to install/upgrade: package 
perl-modules is already installed and configured
** This bug has been marked a duplicate of bug 1407757
   multi-arch packages cannot be installed due to dpkg wrongly detecting them 
as already installed

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

Title:
  package perl-modules 5.20.2-6ubuntu0.2 failed to install/upgrade:
  package perl-modules is already installed and configured

Status in perl package in Ubuntu:
  New

Bug description:
  This is a stacionary computer, bug report when i try upgrade system

  ProblemType: Package
  DistroRelease: Ubuntu 15.10
  Package: perl-modules 5.20.2-6ubuntu0.2
  ProcVersionSignature: Ubuntu 4.2.0-30.36-generic 4.2.8-ckt3
  Uname: Linux 4.2.0-30-generic x86_64
  ApportVersion: 2.19.1-0ubuntu5
  AptdaemonVersion: 1.1.1+bzr982-0ubuntu14
  Architecture: amd64
  Date: Sat Mar 12 19:51:24 2016
  DuplicateSignature: package:perl-modules:5.20.2-6ubuntu0.2:package 
perl-modules is already installed and configured
  ErrorMessage: package perl-modules is already installed and configured
  InstallationDate: Installed on 2015-11-01 (132 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.2ubuntu5.1
   apt  1.0.10.2ubuntu1
  SourcePackage: perl
  Title: package perl-modules 5.20.2-6ubuntu0.2 failed to install/upgrade: 
package perl-modules is already installed and configured
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Re: [Touch-packages] [Bug 1556447] Re: lxc-start fails: lxc_cgfsng - cgfsng.c:all_controllers_found:430 - no systemd controller mountpoint found

[Serge Hallyn]

Do you know whether you are using lightdm?  Can you show your
/etc/pamd.d/common-session file?

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

Title:
  lxc-start fails: lxc_cgfsng - cgfsng.c:all_controllers_found:430 - no
  systemd controller mountpoint found

Status in lxc package in Ubuntu:
  New

Bug description:
  On Ubuntu Xenial pre-release, I see the following, so can't start a
  container:

  [swarren@sprint ~]$ lxc-create -t download -n t2 -- -d ubuntu -r trusty -a 
amd64
  Using image from local cache
  Unpacking the rootfs

  ---
  You just created an Ubuntu container (release=trusty, arch=amd64, 
variant=default)

  To enable sshd, run: apt-get install openssh-server

  For security reason, container images ship without user accounts
  and without a root password.

  Use lxc-attach or chroot directly into the rootfs to set a root password
  or create user accounts.

  
  swarren@sprint ~]$ lxc-start -n t2 -d
  lxc-start: lxc_start.c: main: 344 The container failed to start.
  lxc-start: lxc_start.c: main: 346 To get more details, run the container in 
foreground mode.
  lxc-start: lxc_start.c: main: 348 Additional information can be obtained by 
setting the --logfile and --logpriority options.

  
  [swarren@sprint ~]$ lxc-start -n t2 -d -o /dev/stdout -l debug -F
lxc-start 20160312101415.704 INFO lxc_start_ui - 
lxc_start.c:main:264 - using rcfile /home/swarren/.local/share/lxc/t2/config
lxc-start 20160312101415.705 WARN lxc_confile - 
confile.c:config_pivotdir:1859 - lxc.pivotdir is ignored.  It will soon become 
an error.
lxc-start 20160312101415.705 INFO lxc_confile - 
confile.c:config_idmap:1495 - read uid map: type u nsid 0 hostid 10 range 
65536
lxc-start 20160312101415.705 INFO lxc_confile - 
confile.c:config_idmap:1495 - read uid map: type g nsid 0 hostid 10 range 
65536
lxc-start 20160312101415.707 INFO lxc_lsm - lsm/lsm.c:lsm_init:48 - 
LSM security driver AppArmor
lxc-start 20160312101415.708 INFO lxc_seccomp - 
seccomp.c:parse_config_v2:342 - processing: .reject_force_umount  # comment 
this to allow umount -f;  not recommended.
lxc-start 20160312101415.708 INFO lxc_seccomp - 
seccomp.c:parse_config_v2:446 - Adding native rule for reject_force_umount 
action 0
lxc-start 20160312101415.708 INFO lxc_seccomp - 
seccomp.c:do_resolve_add_rule:216 - Setting seccomp rule to reject force umounts

lxc-start 20160312101415.708 INFO lxc_seccomp - 
seccomp.c:parse_config_v2:449 - Adding compat rule for reject_force_umount 
action 0
lxc-start 20160312101415.708 INFO lxc_seccomp - 
seccomp.c:do_resolve_add_rule:216 - Setting seccomp rule to reject force umounts

lxc-start 20160312101415.708 INFO lxc_seccomp - 
seccomp.c:parse_config_v2:342 - processing: .[all].
lxc-start 20160312101415.708 INFO lxc_seccomp - 
seccomp.c:parse_config_v2:342 - processing: .kexec_load errno 1.
lxc-start 20160312101415.708 INFO lxc_seccomp - 
seccomp.c:parse_config_v2:446 - Adding native rule for kexec_load action 327681
lxc-start 20160312101415.708 INFO lxc_seccomp - 
seccomp.c:parse_config_v2:449 - Adding compat rule for kexec_load action 327681
lxc-start 20160312101415.708 INFO lxc_seccomp - 
seccomp.c:parse_config_v2:342 - processing: .open_by_handle_at errno 1.
lxc-start 20160312101415.708 INFO lxc_seccomp - 
seccomp.c:parse_config_v2:446 - Adding native rule for open_by_handle_at action 
327681
lxc-start 20160312101415.708 INFO lxc_seccomp - 
seccomp.c:parse_config_v2:449 - Adding compat rule for open_by_handle_at action 
327681
lxc-start 20160312101415.708 INFO lxc_seccomp - 
seccomp.c:parse_config_v2:342 - processing: .init_module errno 1.
lxc-start 20160312101415.708 INFO lxc_seccomp - 
seccomp.c:parse_config_v2:446 - Adding native rule for init_module action 327681
lxc-start 20160312101415.708 INFO lxc_seccomp - 
seccomp.c:parse_config_v2:449 - Adding compat rule for init_module action 327681
lxc-start 20160312101415.708 INFO lxc_seccomp - 
seccomp.c:parse_config_v2:342 - processing: .finit_module errno 1.
lxc-start 20160312101415.708 INFO lxc_seccomp - 
seccomp.c:parse_config_v2:446 - Adding native rule for finit_module action 
327681
lxc-start 20160312101415.708 INFO lxc_seccomp - 
seccomp.c:parse_config_v2:449 - Adding compat rule for finit_module action 
327681
lxc-start 20160312101415.708 INFO lxc_seccomp - 
seccomp.c:parse_config_v2:342 - processing: .delete_module errno 1.
lxc-start 20160312101415.708 INFO lxc_seccomp - 
seccomp.c:parse_config_v2:446 - Adding native rule for delete_module action 
327681
lxc-start 20160312101415.708 INFO lxc_seccomp - 

[Touch-packages] [Bug 1551041] Re: snd_au8820 0000:01:04.0: BUG: , pos = 16386, buffer size = 16384, period size = 1024

[sudodus]

fixed typing error: please *tell* me what to do

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

Title:
  snd_au8820 :01:04.0: BUG: , pos = 16386, buffer size = 16384,
  period size = 1024

Status in alsa-driver package in Ubuntu:
  Triaged

Bug description:
  Kernel oops in a new installed system, that I configuring ...

  ProblemType: KernelOops
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-8-generic 4.4.0-8.23
  ProcVersionSignature: Ubuntu 4.4.0-8.23-generic 4.4.2
  Uname: Linux 4.4.0-8-generic i686
  NonfreeKernelModules: nvidia
  Annotation: Your system might become unstable now and might need to be 
restarted.
  ApportVersion: 2.20-0ubuntu3
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  olle   1606 F pulseaudio
   /dev/snd/controlC0:  olle   1606 F pulseaudio
  Date: Mon Feb 29 00:00:56 2016
  Failure: oops
  HibernationDevice: RESUME=UUID=03bed9e9-e39b-4107-8cd6-c2612af9a6aa
  InstallationDate: Installed on 2016-02-28 (0 days ago)
  InstallationMedia: Lubuntu 16.04 LTS "Xenial Xerus" - Alpha i386 (20160226)
  IwConfig:
   enp31s0   no wireless extensions.
   
   lono wireless extensions.
  MachineType: Hewlett-Packard HP xw8400 Workstation
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-8-generic 
root=UUID=2160f8ed-4aa3-4243-b5d6-f87c1967e253 ro quiet splash
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: kerneloops-daemon 0.12+git20090217-3ubuntu9
  RfKill:
   
  SourcePackage: linux
  Title: snd_au8820 :01:04.0: BUG: , pos = 16386, buffer size = 16384, 
period size = 1024
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/09/2009
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 786D5 v02.37
  dmi.board.name: 0A08h
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: NA
  dmi.chassis.asset.tag: CZC722497N
  dmi.chassis.type: 6
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr786D5v02.37:bd07/09/2009:svnHewlett-Packard:pnHPxw8400Workstation:pvr:rvnHewlett-Packard:rn0A08h:rvrNA:cvnHewlett-Packard:ct6:cvr:
  dmi.product.name: HP xw8400 Workstation
  dmi.sys.vendor: Hewlett-Packard

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1551041/+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 1551041] Re: snd_au8820 0000:01:04.0: BUG: , pos = 16386, buffer size = 16384, period size = 1024

[sudodus]

Raymond, do you need anything from me now? In that case, please me what
to do?

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

Title:
  snd_au8820 :01:04.0: BUG: , pos = 16386, buffer size = 16384,
  period size = 1024

Status in alsa-driver package in Ubuntu:
  Triaged

Bug description:
  Kernel oops in a new installed system, that I configuring ...

  ProblemType: KernelOops
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-8-generic 4.4.0-8.23
  ProcVersionSignature: Ubuntu 4.4.0-8.23-generic 4.4.2
  Uname: Linux 4.4.0-8-generic i686
  NonfreeKernelModules: nvidia
  Annotation: Your system might become unstable now and might need to be 
restarted.
  ApportVersion: 2.20-0ubuntu3
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  olle   1606 F pulseaudio
   /dev/snd/controlC0:  olle   1606 F pulseaudio
  Date: Mon Feb 29 00:00:56 2016
  Failure: oops
  HibernationDevice: RESUME=UUID=03bed9e9-e39b-4107-8cd6-c2612af9a6aa
  InstallationDate: Installed on 2016-02-28 (0 days ago)
  InstallationMedia: Lubuntu 16.04 LTS "Xenial Xerus" - Alpha i386 (20160226)
  IwConfig:
   enp31s0   no wireless extensions.
   
   lono wireless extensions.
  MachineType: Hewlett-Packard HP xw8400 Workstation
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-8-generic 
root=UUID=2160f8ed-4aa3-4243-b5d6-f87c1967e253 ro quiet splash
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: kerneloops-daemon 0.12+git20090217-3ubuntu9
  RfKill:
   
  SourcePackage: linux
  Title: snd_au8820 :01:04.0: BUG: , pos = 16386, buffer size = 16384, 
period size = 1024
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/09/2009
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 786D5 v02.37
  dmi.board.name: 0A08h
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: NA
  dmi.chassis.asset.tag: CZC722497N
  dmi.chassis.type: 6
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr786D5v02.37:bd07/09/2009:svnHewlett-Packard:pnHPxw8400Workstation:pvr:rvnHewlett-Packard:rn0A08h:rvrNA:cvnHewlett-Packard:ct6:cvr:
  dmi.product.name: HP xw8400 Workstation
  dmi.sys.vendor: Hewlett-Packard

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1551041/+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 1556552] Re: Sync 3.18.9 from Debian

[Egmont Koblinger]

A quick summary of how to reproduce the two gnome-terminal bugs which
are the consequence of the said Gtk+ bug:

Using Ubuntu's default Unity desktop, launch gnome-terminal and xterm.

Make xterm the focused window, but move the mouse to stay over gnome-
terminal. Press Ctrl+D to quit xterm.

The said gnome-terminal window will no longer change its cursor from
solid to outlined rectangle on focus out, and will also no longer stop
blinking the cursor then (note: blinking is subject to a Gnome-wide
setting, and still stops after a 10s timeout).

Continuing from here, right-click to open the context menu of gnome-
terminal, and then close this menu.

At this point, a keypress for gnome-terminal will hide the mouse
pointer, and moving the mouse doesn't redisplay it, you move the
invisible mouse pointer over gnome-terminal's area.

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

Title:
  Sync 3.18.9 from Debian

Status in gtk+3.0 package in Ubuntu:
  New

Bug description:
  Currently Xenial (beta) contains Gtk+ 3.18.8, whereas 3.18.9 has
  already arrived to Debian Unstable.

  Could you please sync 3.18.9 from Debian?

  It fixes Gnome #677329 (missing focus in/out events) which badly
  effects multiple apps, including at least gnome-terminal and evince.

  In gnome-terminal, the intended behavior is to hide the mouse pointer
  on keypress, and re-show when the mouse is moved. This bug causes the
  mouse pointer sometimes not to be re-shown on mouse move, which is a
  significant usability issue. (Gnome #725342).

  Also, as side effect of this bug, gnome-terminal sometimes fails to
  change the cursor's shape from solid rectangle to outlined rectangle
  and fails to stop it from blinking when the window loses focus. (LP
  #890784, Debian #679738, RedHat #947847).

  Thanks!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1556552/+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 1556552] [NEW] Sync 3.18.9 from Debian

[Egmont Koblinger]

Public bug reported:

Currently Xenial (beta) contains Gtk+ 3.18.8, whereas 3.18.9 has already
arrived to Debian Unstable.

Could you please sync 3.18.9 from Debian?

It fixes Gnome #677329 (missing focus in/out events) which badly effects
multiple apps, including at least gnome-terminal and evince.

In gnome-terminal, the intended behavior is to hide the mouse pointer on
keypress, and re-show when the mouse is moved. This bug causes the mouse
pointer sometimes not to be re-shown on mouse move, which is a
significant usability issue. (Gnome #725342).

Also, as side effect of this bug, gnome-terminal sometimes fails to
change the cursor's shape from solid rectangle to outlined rectangle and
fails to stop it from blinking when the window loses focus. (LP #890784,
Debian #679738, RedHat #947847).

Thanks!

** Affects: gtk+3.0 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: xenial

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

Title:
  Sync 3.18.9 from Debian

Status in gtk+3.0 package in Ubuntu:
  New

Bug description:
  Currently Xenial (beta) contains Gtk+ 3.18.8, whereas 3.18.9 has
  already arrived to Debian Unstable.

  Could you please sync 3.18.9 from Debian?

  It fixes Gnome #677329 (missing focus in/out events) which badly
  effects multiple apps, including at least gnome-terminal and evince.

  In gnome-terminal, the intended behavior is to hide the mouse pointer
  on keypress, and re-show when the mouse is moved. This bug causes the
  mouse pointer sometimes not to be re-shown on mouse move, which is a
  significant usability issue. (Gnome #725342).

  Also, as side effect of this bug, gnome-terminal sometimes fails to
  change the cursor's shape from solid rectangle to outlined rectangle
  and fails to stop it from blinking when the window loses focus. (LP
  #890784, Debian #679738, RedHat #947847).

  Thanks!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1556552/+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 1556433] Re: Booting is taking too long to start from grub

[Pavlushka]

** Attachment added: "systemd"
   
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1556433/+attachment/4597469/+files/systemd

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

Title:
  Booting is taking too long to start from grub

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  Booting takes to start almost three minutes  after selecting Xubuntu
  Xenial. But it does not happen for the Ubuntu 14.04 LTS listed in the
  same menu. Xubuntu is installed in a USB 3 external Harddisk and
  Ubuntu is installed in internal Harddisk, but it was not happening for
  other installations. Like to add, after the boot started, it loaded
  much quicker than Ubuntu, there is a chance that the logs were stuck
  and appeared all at a time but may be this is not the case.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1556433/+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 1556545] Re: wget crashed with SIGSEGV

[Apport retracing service]

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

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 #1546334, 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.

** Attachment removed: "CoreDump.gz"
   
https://bugs.launchpad.net/bugs/1556545/+attachment/4597450/+files/CoreDump.gz

** Attachment removed: "Disassembly.txt"
   
https://bugs.launchpad.net/bugs/1556545/+attachment/4597452/+files/Disassembly.txt

** Attachment removed: "ProcMaps.txt"
   
https://bugs.launchpad.net/bugs/1556545/+attachment/4597454/+files/ProcMaps.txt

** Attachment removed: "ProcStatus.txt"
   
https://bugs.launchpad.net/bugs/1556545/+attachment/4597455/+files/ProcStatus.txt

** Attachment removed: "Registers.txt"
   
https://bugs.launchpad.net/bugs/1556545/+attachment/4597456/+files/Registers.txt

** Attachment removed: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/1556545/+attachment/4597458/+files/Stacktrace.txt

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1556545/+attachment/4597459/+files/ThreadStacktrace.txt

** This bug has been marked a duplicate of private bug 1546334

** 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 wget in Ubuntu.
https://bugs.launchpad.net/bugs/1556545

Title:
  wget crashed with SIGSEGV

Status in wget package in Ubuntu:
  New

Bug description:
  xenial refuses yandex wget? yandex deb? conky? Conky manager? At the
  beginning It was not like that guys. See you soon.

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: wget 1.17.1-1ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-12.28-generic 4.4.4
  Uname: Linux 4.4.0-12-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CrashCounter: 1
  Date: Sun Mar 13 02:42:09 2016
  ExecutablePath: /usr/bin/wget
  InstallationDate: Installed on 2016-03-12 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160205)
  ProcCmdline: wget http://repo.yandex.ru/yandex-disk/YANDEX-DISK-KEY.GPG -O-
  ProcEnviron:
   SHELL=/bin/bash
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=pt_BR.UTF-8
   LANGUAGE=pt_BR:pt:en
  Signal: 11
  SourcePackage: wget
  StacktraceTop:
   ?? ()
   ?? ()
   ?? ()
   ?? ()
   ?? ()
  Title: wget crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/wget/+bug/1556545/+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 1556539] Re: package sysvinit-utils 2.88dsf-41ubuntu6.3 failed to install/upgrade: installing sysvinit-utils would break existing software

[Apport retracing service]

** Tags removed: need-duplicate-check

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

Title:
  package sysvinit-utils 2.88dsf-41ubuntu6.3 failed to install/upgrade:
  installing sysvinit-utils would break existing software

Status in sysvinit package in Ubuntu:
  New

Bug description:
  Error found while updating from  14.04.4 LTS to 16.04 dev release

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: sysvinit-utils 2.88dsf-41ubuntu6.3
  ProcVersionSignature: Ubuntu 3.13.0-79.123-generic 3.13.11-ckt33
  Uname: Linux 3.13.0-79-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  Date: Sun Mar 13 00:00:10 2016
  DuplicateSignature: package:sysvinit-utils:2.88dsf-41ubuntu6.3:installing 
sysvinit-utils would break existing software
  ErrorMessage: installing sysvinit-utils would break existing software
  InstallationDate: Installed on 2012-09-14 (1275 days ago)
  InstallationMedia: Ubuntu-Server 10.04 LTS "Lucid Lynx" - Release amd64 
(20100427)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1
   apt  1.0.1ubuntu2.11
  SourcePackage: sysvinit
  Title: package sysvinit-utils 2.88dsf-41ubuntu6.3 failed to install/upgrade: 
installing sysvinit-utils would break existing software
  UpgradeStatus: Upgraded to xenial on 2016-03-13 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sysvinit/+bug/1556539/+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 1556539] [NEW] package sysvinit-utils 2.88dsf-41ubuntu6.3 failed to install/upgrade: installing sysvinit-utils would break existing software

[Andrew Haynes]

Public bug reported:

Error found while updating from  14.04.4 LTS to 16.04 dev release

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: sysvinit-utils 2.88dsf-41ubuntu6.3
ProcVersionSignature: Ubuntu 3.13.0-79.123-generic 3.13.11-ckt33
Uname: Linux 3.13.0-79-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.19
Architecture: amd64
Date: Sun Mar 13 00:00:10 2016
DuplicateSignature: package:sysvinit-utils:2.88dsf-41ubuntu6.3:installing 
sysvinit-utils would break existing software
ErrorMessage: installing sysvinit-utils would break existing software
InstallationDate: Installed on 2012-09-14 (1275 days ago)
InstallationMedia: Ubuntu-Server 10.04 LTS "Lucid Lynx" - Release amd64 
(20100427)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1
 apt  1.0.1ubuntu2.11
SourcePackage: sysvinit
Title: package sysvinit-utils 2.88dsf-41ubuntu6.3 failed to install/upgrade: 
installing sysvinit-utils would break existing software
UpgradeStatus: Upgraded to xenial on 2016-03-13 (0 days ago)

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


** Tags: amd64 apport-package third-party-packages xenial

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

Title:
  package sysvinit-utils 2.88dsf-41ubuntu6.3 failed to install/upgrade:
  installing sysvinit-utils would break existing software

Status in sysvinit package in Ubuntu:
  New

Bug description:
  Error found while updating from  14.04.4 LTS to 16.04 dev release

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: sysvinit-utils 2.88dsf-41ubuntu6.3
  ProcVersionSignature: Ubuntu 3.13.0-79.123-generic 3.13.11-ckt33
  Uname: Linux 3.13.0-79-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  Date: Sun Mar 13 00:00:10 2016
  DuplicateSignature: package:sysvinit-utils:2.88dsf-41ubuntu6.3:installing 
sysvinit-utils would break existing software
  ErrorMessage: installing sysvinit-utils would break existing software
  InstallationDate: Installed on 2012-09-14 (1275 days ago)
  InstallationMedia: Ubuntu-Server 10.04 LTS "Lucid Lynx" - Release amd64 
(20100427)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1
   apt  1.0.1ubuntu2.11
  SourcePackage: sysvinit
  Title: package sysvinit-utils 2.88dsf-41ubuntu6.3 failed to install/upgrade: 
installing sysvinit-utils would break existing software
  UpgradeStatus: Upgraded to xenial on 2016-03-13 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sysvinit/+bug/1556539/+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 1556537] Re: wget crashed with SIGSEGV

[Apport retracing service]

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

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 #1546334, 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.

** Attachment removed: "CoreDump.gz"
   
https://bugs.launchpad.net/bugs/1556537/+attachment/4597410/+files/CoreDump.gz

** Attachment removed: "Disassembly.txt"
   
https://bugs.launchpad.net/bugs/1556537/+attachment/4597412/+files/Disassembly.txt

** Attachment removed: "ProcMaps.txt"
   
https://bugs.launchpad.net/bugs/1556537/+attachment/4597414/+files/ProcMaps.txt

** Attachment removed: "ProcStatus.txt"
   
https://bugs.launchpad.net/bugs/1556537/+attachment/4597415/+files/ProcStatus.txt

** Attachment removed: "Registers.txt"
   
https://bugs.launchpad.net/bugs/1556537/+attachment/4597416/+files/Registers.txt

** Attachment removed: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/1556537/+attachment/4597417/+files/Stacktrace.txt

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1556537/+attachment/4597418/+files/ThreadStacktrace.txt

** This bug has been marked a duplicate of private bug 1546334

** Information type changed from Private Security to Public Security

** Tags removed: need-amd64-retrace

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

Title:
  wget crashed with SIGSEGV

Status in wget package in Ubuntu:
  New

Bug description:
  prelink bug

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: wget 1.17.1-1ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-12.28-generic 4.4.4
  Uname: Linux 4.4.0-12-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  Date: Sun Mar 13 01:43:11 2016
  ExecutablePath: /usr/bin/wget
  InstallationDate: Installed on 2016-03-12 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160205)
  ProcCmdline: /usr/bin/wget --tries=3 --timeout=40 --read-timeout=40 
--continue -O libdvdcss_1.4.0.orig.tar.bz2 
http://download.videolan.org/pub/libdvdcss/1.4.0/libdvdcss-1.4.0.tar.bz2
  ProcEnviron:
   LANGUAGE=pt_BR:pt:en
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=pt_BR.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7f018b047370 <__memset_sse2+160>:movdqa 
%xmm8,(%rcx)
   PC (0x7f018b047370) ok
   source "%xmm8" ok
   destination "(%rcx)" (0x55e61de9a000) not located in a known VMA region 
(needed writable region)!
  SegvReason: writing unknown VMA
  Signal: 11
  SourcePackage: wget
  StacktraceTop:
   ?? ()
   ?? ()
   ?? ()
   ?? ()
   ?? ()
  Title: wget crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/wget/+bug/1556537/+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 1446571] Re: Playlist is emptied by itself

[Launchpad Bug Tracker]

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

** Changed in: mediaplayer-app (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  Playlist is emptied by itself

Status in mediaplayer-app package in Ubuntu:
  Expired

Bug description:
  When using the Music app on the Ubuntu Phone, I added some tracks to a
  playlist. The next day when trying to open the playlist, it was now
  empty -- all entries had gone. The playlist itself still existed, and
  the files were still on the phone, but the playlist had emptied
  itself.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mediaplayer-app/+bug/1446571/+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 1533421] Re: Mouse and keyboard unexpetted stop working.

[Launchpad Bug Tracker]

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

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

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

Title:
  Mouse and keyboard unexpetted stop working.

Status in xorg package in Ubuntu:
  Expired

Bug description:
  The mouse and keyboard stops working.  I have to use the computer
  power to shut down, then turn it on and it works again...for a while.
  I really like Ubuntu and trying to learn more about it.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: xorg 1:7.7+7ubuntu4
  ProcVersionSignature: Ubuntu 4.2.0-23.28-generic 4.2.6
  Uname: Linux 4.2.0-23-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Tue Jan 12 18:59:59 2016
  DistUpgraded: Fresh install
  DistroCodename: wily
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Wrestler [Radeon HD 6320] [1002:9806] 
(prog-if 00 [VGA controller])
 Subsystem: Acer Incorporated [ALI] Device [1025:0614]
  InstallationDate: Installed on 2016-01-03 (9 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: Acer Aspire 7250
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-23-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/02/2011
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.10
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: HMA71_BZ
  dmi.board.vendor: Acer
  dmi.board.version: Base Board Version
  dmi.chassis.type: 10
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.10:bd11/02/2011:svnAcer:pnAspire7250:pvrV1.10:rvnAcer:rnHMA71_BZ:rvrBaseBoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:
  dmi.product.name: Aspire 7250
  dmi.product.version: V1.10
  dmi.sys.vendor: Acer
  version.compiz: compiz 1:0.9.12.2+15.10.20151015-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.64-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.2-1ubuntu4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.2-1ubuntu4
  version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu9.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:7.5.0+git20150819-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20150808-0ubuntu4
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu3
  xserver.bootTime: Tue Jan 12 18:36:02 2016
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.17.2-1ubuntu9.1
  xserver.video_driver: radeon

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1533421/+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 1533162] Re: Librie office writer freezes system

[Launchpad Bug Tracker]

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

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

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

Title:
  Librie office writer freezes system

Status in xorg package in Ubuntu:
  Expired

Bug description:
  When Ctrl-C and Ctrl-V text

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 3.19.0-43.49~14.04.1-generic 3.19.8-ckt10
  Uname: Linux 3.19.0-43-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.19
  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: Tue Jan 12 14:34:39 2016
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus: bbswitch, 0.7, 3.19.0-43-generic, x86_64: installed
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   NVIDIA Corporation G84M [GeForce 8600M GT] [10de:0407] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: ASUSTeK Computer Inc. Device [1043:1515]
  InstallationDate: Installed on 2016-01-11 (0 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  MachineType: ASUSTeK Computer Inc. G2S
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-43-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/31/2007
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 300
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: G2S
  dmi.board.vendor: ASUSTeK Computer Inc.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK Computer Inc.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr300:bd12/31/2007:svnASUSTeKComputerInc.:pnG2S:pvr1.0:rvnASUSTeKComputerInc.:rnG2S:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:
  dmi.product.name: G2S
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK Computer Inc.
  version.compiz: compiz 1:0.9.11.3+14.04.20150313-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.60-2~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: Tue Jan 12 14:17:11 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)
   NOUVEAU(0): [COPY] failed to allocate class.
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.17.1-0ubuntu3~trusty1
  xserver.video_driver: nouveau

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1533162/+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 1553685] Re: Lenovo Y700-17ISK subwoofer doesn't work

[Raymond]

Node 0x0f [Audio Mixer] wcaps 0x20010a: Mono Amp-In Amp-In caps:
ofs=0x00, nsteps=0x00, stepsize=0x00, mute=1 Amp-In vals: [0x00 0x00]
Connection: 1 0x0d

This seem to be stereo to mono down mix widget since node 0x0d is stereo

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

Title:
  Lenovo Y700-17ISK subwoofer doesn't work

Status in alsa-driver package in Ubuntu:
  Incomplete

Bug description:
  Lenovo Y700-17ISK (Intel Core i7-6700HQ/RAM 16GB/SSD 512GB/Nvidia GTX960M 4GB)
  Operating system: Ubuntu 16.04 (xenial-desktop-amd64.iso 04-Mar-2016, kernel 
4.4.0-10-generic, nvidia 361.28)

  Problem: Notebook subwoofer doesn't work.

  Judging from alsa-info.sh output, there is no pin declared for the bass 
output by BIOS.
  Please find a zip file attached: 'alsa-info_hdajackretask-unconnected-pins'

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-10-generic 4.4.0-10.25
  ProcVersionSignature: Ubuntu 4.4.0-10.25-generic 4.4.3
  Uname: Linux 4.4.0-10-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  aljosa 1776 F pulseaudio
  CurrentDesktop: Unity
  Date: Sun Mar  6 11:02:21 2016
  HibernationDevice: RESUME=UUID=ac022671-63df-40ae-bffe-66fff3b35125
  InstallationDate: Installed on 2016-03-05 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160304)
  MachineType: LENOVO 80Q0
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-10-generic.efi.signed 
root=UUID=aa4325c4-4b4c-4372-b8ca-a66c3e5b2aa6 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-10-generic N/A
   linux-backports-modules-4.4.0-10-generic  N/A
   linux-firmware1.156
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/31/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: CDCN30WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: Allsparks 7A
  dmi.board.vendor: LENOVO
  dmi.board.version: NO DPK
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad Y700-17ISK
  dmi.modalias: 
dmi:bvnLENOVO:bvrCDCN30WW:bd01/31/2016:svnLENOVO:pn80Q0:pvrLenovoideapadY700-17ISK:rvnLENOVO:rnAllsparks7A:rvrNODPK:cvnLENOVO:ct10:cvrLenovoideapadY700-17ISK:
  dmi.product.name: 80Q0
  dmi.product.version: Lenovo ideapad Y700-17ISK
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1553685/+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 1553685] Re: Lenovo Y700-17ISK subwoofer doesn't work

[Raymond]

Simple mixer control 'Headphone',0 Capabilities: pvolume pswitch
Playback channels: Front Left - Front Right Limits: Playback 0 - 87
Mono: Front Left: Playback 0 [0%] [-65.25dB] [off] Front Right: Playback
0 [0%] [-65.25dB] [off]

Simple mixer control 'Speaker',0 Capabilities: pvolume pswitch Playback
channels: Front Left - Front Right Limits: Playback 0 - 87 Mono: Front
Left: Playback 87 [100%] [0.00dB] [on] Front Right: Playback 87 [100%]
[0.00dB] [on]

It is pulseaudio switch headphone playback volume to minimum and switch
to off


https://cgit.freedesktop.org/pulseaudio/pulseaudio/commit/src/modules/alsa/mixer/paths/analog-output-speaker.conf?id=22aac4e9fdb3786178f7815a0cb2150f588b1582

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

Title:
  Lenovo Y700-17ISK subwoofer doesn't work

Status in alsa-driver package in Ubuntu:
  Incomplete

Bug description:
  Lenovo Y700-17ISK (Intel Core i7-6700HQ/RAM 16GB/SSD 512GB/Nvidia GTX960M 4GB)
  Operating system: Ubuntu 16.04 (xenial-desktop-amd64.iso 04-Mar-2016, kernel 
4.4.0-10-generic, nvidia 361.28)

  Problem: Notebook subwoofer doesn't work.

  Judging from alsa-info.sh output, there is no pin declared for the bass 
output by BIOS.
  Please find a zip file attached: 'alsa-info_hdajackretask-unconnected-pins'

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-10-generic 4.4.0-10.25
  ProcVersionSignature: Ubuntu 4.4.0-10.25-generic 4.4.3
  Uname: Linux 4.4.0-10-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  aljosa 1776 F pulseaudio
  CurrentDesktop: Unity
  Date: Sun Mar  6 11:02:21 2016
  HibernationDevice: RESUME=UUID=ac022671-63df-40ae-bffe-66fff3b35125
  InstallationDate: Installed on 2016-03-05 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160304)
  MachineType: LENOVO 80Q0
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-10-generic.efi.signed 
root=UUID=aa4325c4-4b4c-4372-b8ca-a66c3e5b2aa6 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-10-generic N/A
   linux-backports-modules-4.4.0-10-generic  N/A
   linux-firmware1.156
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/31/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: CDCN30WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: Allsparks 7A
  dmi.board.vendor: LENOVO
  dmi.board.version: NO DPK
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad Y700-17ISK
  dmi.modalias: 
dmi:bvnLENOVO:bvrCDCN30WW:bd01/31/2016:svnLENOVO:pn80Q0:pvrLenovoideapadY700-17ISK:rvnLENOVO:rnAllsparks7A:rvrNODPK:cvnLENOVO:ct10:cvrLenovoideapadY700-17ISK:
  dmi.product.name: 80Q0
  dmi.product.version: Lenovo ideapad Y700-17ISK
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1553685/+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 1553685] Re: Lenovo Y700-17ISK subwoofer doesn't work

[Raymond]

Node 0x0f is connected to 0x03 through 0x0d

You have to check whether those amp out and mute switfch of the path
from node 3 to node 0x17 is not muted by pulseaudio (e.g. headphone
plasyback volume )


Node 0x02 [Audio Output] wcaps 0x41d: Stereo Amp-Out Control: name="Speaker 
Playback Volume", index=0, device=0 ControlAmp: chs=3, dir=Out, idx=0, ofs=0 
Amp-Out caps: ofs=0x57, nsteps=0x57, stepsize=0x02, mute=0 Amp-Out vals: [0x48 
0x48] Converter: stream=1, channel=0 PCM: rates [0x60]: 44100 48000 bits [0xe]: 
16 20 24 formats [0x1]: PCM Power states: D0 D1 D2 D3 EPSS Power: setting=D0, 
actual=D0 

Node 0x03 [Audio Output] wcaps 0x41d: Stereo Amp-Out Control:
name="Headphone Playback Volume", index=0, device=0 ControlAmp: chs=3,
dir=Out, idx=0, ofs=0 Device: name="ALC233 Analog", type="Audio",
device=0 Amp-Out caps: ofs=0x57, nsteps=0x57, stepsize=0x02, mute=0 Amp-
Out vals: [0x00 0x00] Converter: stream=1, channel=0 PCM: rates [0x60]:
44100 48000 bits [0xe]: 16 20 24 formats [0x1]: PCM Power states: D0 D1
D2 D3 EPSS Power: setting=D0, actual=D0

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

Title:
  Lenovo Y700-17ISK subwoofer doesn't work

Status in alsa-driver package in Ubuntu:
  Incomplete

Bug description:
  Lenovo Y700-17ISK (Intel Core i7-6700HQ/RAM 16GB/SSD 512GB/Nvidia GTX960M 4GB)
  Operating system: Ubuntu 16.04 (xenial-desktop-amd64.iso 04-Mar-2016, kernel 
4.4.0-10-generic, nvidia 361.28)

  Problem: Notebook subwoofer doesn't work.

  Judging from alsa-info.sh output, there is no pin declared for the bass 
output by BIOS.
  Please find a zip file attached: 'alsa-info_hdajackretask-unconnected-pins'

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-10-generic 4.4.0-10.25
  ProcVersionSignature: Ubuntu 4.4.0-10.25-generic 4.4.3
  Uname: Linux 4.4.0-10-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  aljosa 1776 F pulseaudio
  CurrentDesktop: Unity
  Date: Sun Mar  6 11:02:21 2016
  HibernationDevice: RESUME=UUID=ac022671-63df-40ae-bffe-66fff3b35125
  InstallationDate: Installed on 2016-03-05 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160304)
  MachineType: LENOVO 80Q0
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-10-generic.efi.signed 
root=UUID=aa4325c4-4b4c-4372-b8ca-a66c3e5b2aa6 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-10-generic N/A
   linux-backports-modules-4.4.0-10-generic  N/A
   linux-firmware1.156
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/31/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: CDCN30WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: Allsparks 7A
  dmi.board.vendor: LENOVO
  dmi.board.version: NO DPK
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad Y700-17ISK
  dmi.modalias: 
dmi:bvnLENOVO:bvrCDCN30WW:bd01/31/2016:svnLENOVO:pn80Q0:pvrLenovoideapadY700-17ISK:rvnLENOVO:rnAllsparks7A:rvrNODPK:cvnLENOVO:ct10:cvrLenovoideapadY700-17ISK:
  dmi.product.name: 80Q0
  dmi.product.version: Lenovo ideapad Y700-17ISK
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1553685/+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 1553685] Re: Lenovo Y700-17ISK subwoofer doesn't work

[Raymond]

The other output capable pin is node 0x1b,  do the driver connected this
node to node 0x02 or 0x03?

Node 0x1b [Pin Complex] wcaps 0x40058f: Stereo Amp-In Amp-Out Amp-In
caps: ofs=0x00, nsteps=0x03, stepsize=0x27, mute=0 Amp-In vals: [0x00
0x00] Amp-Out caps: ofs=0x00, nsteps=0x00, stepsize=0x00, mute=1 Amp-Out
vals: [0x80 0x80] Pincap 0x0001373c: IN OUT HP EAPD Detect Vref caps:
HIZ 50 GRD 80 100 EAPD 0x2: EAPD Pin Default 0x41f0: [N/A] Speaker
at Ext Rear Conn = 1/8, Color = Black DefAssociation = 0xf, Sequence =
0x0 Misc = NO_PRESENCE Pin-ctls: 0x20: IN VREF_HIZ Unsolicited: tag=00,
enabled=0 Power states: D0 D1 D2 D3 EPSS Power: setting=D3, actual=D3
Connection: 2 0x0c* 0x0d

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

Title:
  Lenovo Y700-17ISK subwoofer doesn't work

Status in alsa-driver package in Ubuntu:
  Incomplete

Bug description:
  Lenovo Y700-17ISK (Intel Core i7-6700HQ/RAM 16GB/SSD 512GB/Nvidia GTX960M 4GB)
  Operating system: Ubuntu 16.04 (xenial-desktop-amd64.iso 04-Mar-2016, kernel 
4.4.0-10-generic, nvidia 361.28)

  Problem: Notebook subwoofer doesn't work.

  Judging from alsa-info.sh output, there is no pin declared for the bass 
output by BIOS.
  Please find a zip file attached: 'alsa-info_hdajackretask-unconnected-pins'

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-10-generic 4.4.0-10.25
  ProcVersionSignature: Ubuntu 4.4.0-10.25-generic 4.4.3
  Uname: Linux 4.4.0-10-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  aljosa 1776 F pulseaudio
  CurrentDesktop: Unity
  Date: Sun Mar  6 11:02:21 2016
  HibernationDevice: RESUME=UUID=ac022671-63df-40ae-bffe-66fff3b35125
  InstallationDate: Installed on 2016-03-05 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160304)
  MachineType: LENOVO 80Q0
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-10-generic.efi.signed 
root=UUID=aa4325c4-4b4c-4372-b8ca-a66c3e5b2aa6 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-10-generic N/A
   linux-backports-modules-4.4.0-10-generic  N/A
   linux-firmware1.156
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/31/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: CDCN30WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: Allsparks 7A
  dmi.board.vendor: LENOVO
  dmi.board.version: NO DPK
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad Y700-17ISK
  dmi.modalias: 
dmi:bvnLENOVO:bvrCDCN30WW:bd01/31/2016:svnLENOVO:pn80Q0:pvrLenovoideapadY700-17ISK:rvnLENOVO:rnAllsparks7A:rvrNODPK:cvnLENOVO:ct10:cvrLenovoideapadY700-17ISK:
  dmi.product.name: 80Q0
  dmi.product.version: Lenovo ideapad Y700-17ISK
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1553685/+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 1556433] Re: Booting is taking too long to start from grub

[Pavlushka]

** Description changed:

  Booting takes to start almost three minutes  after selecting Xubuntu
  Xenial. But it does not happen for the Ubuntu 14.04 LTS listed in the
  same menu. Xubuntu is installed in a USB 3 external Harddisk and Ubuntu
  is installed in internal Harddisk, but it was not happening for other
  installations. Like to add, after the boot started, it loaded much
  quicker than Ubuntu, there is a chance that the logs were stuck and
- appeared all at a time.
+ appeared all at a time but may be this is not the case.

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

Title:
  Booting is taking too long to start from grub

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  Booting takes to start almost three minutes  after selecting Xubuntu
  Xenial. But it does not happen for the Ubuntu 14.04 LTS listed in the
  same menu. Xubuntu is installed in a USB 3 external Harddisk and
  Ubuntu is installed in internal Harddisk, but it was not happening for
  other installations. Like to add, after the boot started, it loaded
  much quicker than Ubuntu, there is a chance that the logs were stuck
  and appeared all at a time but may be this is not the case.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1556433/+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 1556527] Re: tzdate upgrade fails wih invalid format error during Xenial upgrade

[iMac]

Below is the output after I made the change and continued the 16.04
dist-upgrade process.

820 upgraded, 17 newly installed, 3 to remove and 144 not upgraded.
215 not fully installed or removed.
Need to get 0 B/494 MB of archives.
After this operation, 142 MB of additional disk space will be used.
Do you want to continue? [Y/n] 
Extracting templates from packages: 100%
Preconfiguring packages ...
Setting up tzdata (2016a-1) ...

Current default time zone: 'Etc/UTC'
Local time is now:  Sun Mar 13 02:49:09 UTC 2016.
Universal Time is now:  Sun Mar 13 02:49:09 UTC 2016.
Run 'dpkg-reconfigure tzdata' if you wish to change it.

(Reading database ... 398777 files and directories currently installed.)
Preparing to unpack .../python-cairo_1.8.8-2_amd64.deb ...

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

Title:
  tzdate upgrade fails wih invalid format error during Xenial upgrade

Status in tzdata package in Ubuntu:
  New

Bug description:
  Everything looks fine;  Not sure what is invalid about the format.  I
  am EST, the output is in UTC.

  Breaks the upgrade after from 15.05 at a point where is says it
  completed with errors, but some 200+ packages remaining.

  
  Setting up tzdata (2016a-1) ...

  Current default time zone: 'America/Toronto'
  date: invalid date 'Sun Mar 13 02:32:57 UTC 2016'
  dpkg: error processing package tzdata (--configure):
   subprocess installed post-installation script returned error exit status 1
  Errors were encountered while processing:
   tzdata
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: tzdata 2016a-1
  ProcVersionSignature: Ubuntu 4.2.0-30.36-generic 4.2.8-ckt3
  Uname: Linux 4.2.0-30-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  Date: Sat Mar 12 21:35:07 2016
  InstallationDate: Installed on 2014-10-22 (507 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=en_CA:en
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  SourcePackage: tzdata
  UpgradeStatus: Upgraded to xenial on 2016-03-13 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1556527/+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 1556527] Re: tzdate upgrade fails wih invalid format error during Xenial upgrade

[iMac]

So,

I have no idea what happened;  manual setting of localtime to UTC
(command below) fixed the configuration of the package, allowing the
upgrade to continue.

Anyway, I executed the following command to set to UTC, and then
proceeded to complete the dist-upgrade from 15.05, and the error from
tzdata was resolved;  I'll fix my timezone after the upgrade completes.

#ln -sf /usr/share/zoneinfo/UTC /etc/localtime

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

Title:
  tzdate upgrade fails wih invalid format error during Xenial upgrade

Status in tzdata package in Ubuntu:
  New

Bug description:
  Everything looks fine;  Not sure what is invalid about the format.  I
  am EST, the output is in UTC.

  Breaks the upgrade after from 15.05 at a point where is says it
  completed with errors, but some 200+ packages remaining.

  
  Setting up tzdata (2016a-1) ...

  Current default time zone: 'America/Toronto'
  date: invalid date 'Sun Mar 13 02:32:57 UTC 2016'
  dpkg: error processing package tzdata (--configure):
   subprocess installed post-installation script returned error exit status 1
  Errors were encountered while processing:
   tzdata
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: tzdata 2016a-1
  ProcVersionSignature: Ubuntu 4.2.0-30.36-generic 4.2.8-ckt3
  Uname: Linux 4.2.0-30-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  Date: Sat Mar 12 21:35:07 2016
  InstallationDate: Installed on 2014-10-22 (507 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=en_CA:en
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  SourcePackage: tzdata
  UpgradeStatus: Upgraded to xenial on 2016-03-13 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1556527/+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 1515816] Re: [messaging app] selected SIM hard for some people to see

[Selene Scriven]

Olga isn't with Canonical any more, and the theme has changed since I
filed this bug.  Needs re-testing and possibly re-assignment.

** Changed in: ubuntu-ux
   Status: Triaged => Incomplete

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

Title:
  [messaging app] selected SIM hard for some people to see

Status in Ubuntu UX:
  Incomplete
Status in messaging-app package in Ubuntu:
  Confirmed

Bug description:
  To indicate which SIM slot is active, the messaging-app changes the
  SIM label from black-on-white to dark-red-on-white.  For red-
  colorblind people, this highlight makes no significant difference.
  Studies estimate that this affects about 8% of the male population and
  about 0.5% of the female population.

  Could the visual change be made slightly more noticeable?  Perhaps
  only underline the active slot, or render the active slot in a bold
  font, or maybe change the color to something with higher contrast
  compared to the inactive slot?

  A screenshot is attached.  The top row shows no SIM selected, while
  the second row shows SIM 2 selected.  To red-colorblind people, they
  look nearly identical.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-ux/+bug/1515816/+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 1556527] [NEW] tzdate upgrade fails wih invalid format error during Xenial upgrade

[iMac]

Public bug reported:

Everything looks fine;  Not sure what is invalid about the format.  I am
EST, the output is in UTC.

Breaks the upgrade after from 15.05 at a point where is says it
completed with errors, but some 200+ packages remaining.


Setting up tzdata (2016a-1) ...

Current default time zone: 'America/Toronto'
date: invalid date 'Sun Mar 13 02:32:57 UTC 2016'
dpkg: error processing package tzdata (--configure):
 subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
 tzdata
E: Sub-process /usr/bin/dpkg returned an error code (1)

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: tzdata 2016a-1
ProcVersionSignature: Ubuntu 4.2.0-30.36-generic 4.2.8-ckt3
Uname: Linux 4.2.0-30-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.19.1-0ubuntu5
Architecture: amd64
Date: Sat Mar 12 21:35:07 2016
InstallationDate: Installed on 2014-10-22 (507 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2)
PackageArchitecture: all
ProcEnviron:
 LANGUAGE=en_CA:en
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=en_CA.UTF-8
 SHELL=/bin/bash
SourcePackage: tzdata
UpgradeStatus: Upgraded to xenial on 2016-03-13 (0 days ago)

** Affects: tzdata (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 tzdata in Ubuntu.
https://bugs.launchpad.net/bugs/1556527

Title:
  tzdate upgrade fails wih invalid format error during Xenial upgrade

Status in tzdata package in Ubuntu:
  New

Bug description:
  Everything looks fine;  Not sure what is invalid about the format.  I
  am EST, the output is in UTC.

  Breaks the upgrade after from 15.05 at a point where is says it
  completed with errors, but some 200+ packages remaining.

  
  Setting up tzdata (2016a-1) ...

  Current default time zone: 'America/Toronto'
  date: invalid date 'Sun Mar 13 02:32:57 UTC 2016'
  dpkg: error processing package tzdata (--configure):
   subprocess installed post-installation script returned error exit status 1
  Errors were encountered while processing:
   tzdata
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: tzdata 2016a-1
  ProcVersionSignature: Ubuntu 4.2.0-30.36-generic 4.2.8-ckt3
  Uname: Linux 4.2.0-30-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  Date: Sat Mar 12 21:35:07 2016
  InstallationDate: Installed on 2014-10-22 (507 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=en_CA:en
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  SourcePackage: tzdata
  UpgradeStatus: Upgraded to xenial on 2016-03-13 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1556527/+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 1556330] Re: upstream curl bug #1371: p12 client certificates code is broken

[Rolf Leggewie]

Thanks for the report, debdiff and update.

Quick comment, the upload should be to trusty-proposed, not trusty.  The
changelog would need to be adjusted accordingly once the FTBFS has been
ironed out.

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

Title:
  upstream curl bug #1371: p12 client certificates code is broken

Status in curl package in Ubuntu:
  Fix Released
Status in curl source package in Trusty:
  Triaged

Bug description:
  [Impact]

  The bug makes it impossible to use PKCS#12 secure storage of client
  certificates and private keys with any affected Ubuntu releases. The
  fix is one line fixing a broken switch statement and was already
  tested against Ubuntu 14.04 LTS with a rebuilt curl package.

  This was fixed in upstream libcurl in the following bug:

  https://sourceforge.net/p/curl/bugs/1371/

  The bug fix consists of one missing break statement at the end of a
  case in a switch statement.

  I personally patched the bug using source code release
  curl_7.35.0-1ubuntu2.6.dsc, used in Ubuntu 14.04 LTS, and verified it
  does indeed fix the bug and all of the package's tests still pass
  afterwards.

  [Test Case]

  The bug can be reproduced using the following libcurl parameters (even
  via CLI, pycurl, etc.).

  CURLOPT_SSLCERTTYPE == "P12"
  CURLOPT_SSLCERT = path to PKCS#12
  CURLOPT_SSLKEY = path to PKCS#12
  CURLOPT_SSLKEYPASSWD = key for PKCS#12 if needed

  Basically, just use a PKCS#12 format client certificate and private
  key against some certificate protected web server.

  [Regression Potential]

  If it could possibly break anything, which is extraordinarily
  unlikely, it would break one of the three client certificate formats
  (most likely PKCS#12 but also PEM or DER). Note 1/3 formats is already
  broken due to the bug. Client certificates of all three types could be
  checked to prevent this.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/curl/+bug/1556330/+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 1351534] Re: device doesn't detect current time zone

[Selene Scriven]

There was a branch linked in early December, but then holidays happened.
Is this still active?

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

Title:
  device doesn't detect current time zone

Status in Canonical System Image:
  In Progress
Status in unity8 package in Ubuntu:
  In Progress

Bug description:
  On first phone boot, or after flashing a new image, the user's time
  zone isn't auto-detected.  Instead, the system always defaults to UTC.

  It should probably default instead to checking the cell provider for
  time zone information, or GPS (if enabled), or if there is a network
  connection, get an approximate location from that (look up the current
  access point, in case it has been mapped).

  I'm not entirely sure which system component or launchpad project this
  belongs in, so some re-targeting help would be appreciated.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1351534/+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 1556524] Re: package linux-image-4.4.0-12-generic 4.4.0-12.28 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 2

[Apport retracing service]

** Tags removed: need-duplicate-check

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

Title:
  package linux-image-4.4.0-12-generic 4.4.0-12.28 failed to
  install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools
  exited with return code 2

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  Hi guys, this happens when I was trying to upgrade from 15.10

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-12-generic 4.4.0-12.28
  ProcVersionSignature: Ubuntu 4.4.0-12.28-generic 4.4.4
  Uname: Linux 4.4.0-12-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  xyh1581 F pulseaudio
  Date: Sat Mar 12 23:42:24 2016
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 2
  HibernationDevice: RESUME=UUID=f9051acb-2e83-48a9-baaf-c901618724b4
  InstallationDate: Installed on 2016-03-12 (0 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: LENOVO 4290AG3
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-12-generic 
root=UUID=492bb13e-1f78-46f4-bc1c-bec60bf5cd81 ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc 2.02~beta2-36
  SourcePackage: initramfs-tools
  Title: package linux-image-4.4.0-12-generic 4.4.0-12.28 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 2
  UpgradeStatus: Upgraded to xenial on 2016-03-13 (0 days ago)
  dmi.bios.date: 05/31/2011
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8DET47WW (1.17 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 4290AG3
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr8DET47WW(1.17):bd05/31/2011:svnLENOVO:pn4290AG3:pvrThinkPadX220:rvnLENOVO:rn4290AG3:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 4290AG3
  dmi.product.version: ThinkPad X220
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1556524/+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 1556524] [NEW] package linux-image-4.4.0-12-generic 4.4.0-12.28 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 2

[Youhua Xu]

Public bug reported:

Hi guys, this happens when I was trying to upgrade from 15.10

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-12-generic 4.4.0-12.28
ProcVersionSignature: Ubuntu 4.4.0-12.28-generic 4.4.4
Uname: Linux 4.4.0-12-generic x86_64
ApportVersion: 2.20-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  xyh1581 F pulseaudio
Date: Sat Mar 12 23:42:24 2016
ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 2
HibernationDevice: RESUME=UUID=f9051acb-2e83-48a9-baaf-c901618724b4
InstallationDate: Installed on 2016-03-12 (0 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
MachineType: LENOVO 4290AG3
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-12-generic 
root=UUID=492bb13e-1f78-46f4-bc1c-bec60bf5cd81 ro quiet splash vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions: grub-pc 2.02~beta2-36
SourcePackage: initramfs-tools
Title: package linux-image-4.4.0-12-generic 4.4.0-12.28 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 2
UpgradeStatus: Upgraded to xenial on 2016-03-13 (0 days ago)
dmi.bios.date: 05/31/2011
dmi.bios.vendor: LENOVO
dmi.bios.version: 8DET47WW (1.17 )
dmi.board.asset.tag: Not Available
dmi.board.name: 4290AG3
dmi.board.vendor: LENOVO
dmi.board.version: Not Available
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: 
dmi:bvnLENOVO:bvr8DET47WW(1.17):bd05/31/2011:svnLENOVO:pn4290AG3:pvrThinkPadX220:rvnLENOVO:rn4290AG3:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 4290AG3
dmi.product.version: ThinkPad X220
dmi.sys.vendor: LENOVO

** Affects: initramfs-tools (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 initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1556524

Title:
  package linux-image-4.4.0-12-generic 4.4.0-12.28 failed to
  install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools
  exited with return code 2

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  Hi guys, this happens when I was trying to upgrade from 15.10

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-12-generic 4.4.0-12.28
  ProcVersionSignature: Ubuntu 4.4.0-12.28-generic 4.4.4
  Uname: Linux 4.4.0-12-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  xyh1581 F pulseaudio
  Date: Sat Mar 12 23:42:24 2016
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 2
  HibernationDevice: RESUME=UUID=f9051acb-2e83-48a9-baaf-c901618724b4
  InstallationDate: Installed on 2016-03-12 (0 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: LENOVO 4290AG3
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-12-generic 
root=UUID=492bb13e-1f78-46f4-bc1c-bec60bf5cd81 ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc 2.02~beta2-36
  SourcePackage: initramfs-tools
  Title: package linux-image-4.4.0-12-generic 4.4.0-12.28 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 2
  UpgradeStatus: Upgraded to xenial on 2016-03-13 (0 days ago)
  dmi.bios.date: 05/31/2011
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8DET47WW (1.17 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 4290AG3
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr8DET47WW(1.17):bd05/31/2011:svnLENOVO:pn4290AG3:pvrThinkPadX220:rvnLENOVO:rn4290AG3:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 4290AG3
  dmi.product.version: ThinkPad X220
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1556524/+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 1556523] [NEW] Notifications are the wrong color in rc-proposed

[Michael Terry]

Public bug reported:

Screenshot attached. This just started happening after we landed silo
64.

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

** Attachment added: "screenshot20160312_205441913.png"
   
https://bugs.launchpad.net/bugs/1556523/+attachment/4597354/+files/screenshot20160312_205441913.png

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

Title:
  Notifications are the wrong color in rc-proposed

Status in unity8 package in Ubuntu:
  New

Bug description:
  Screenshot attached. This just started happening after we landed silo
  64.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1556523/+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 1551041] Re: snd_au8820 0000:01:04.0: BUG: , pos = 16386, buffer size = 16384, period size = 1024

[Raymond]

As there is no datasheet, we can only follow the patent description

https://git.kernel.org/cgit/linux/kernel/git/tiwai/sound.git/tree/sound/pci/au88x0/au8820.h#n26

FIG. 15c is a diagrammatic block diagram of a mode register 382 of sub-
buffer table 380(3) of FIG. 15b. Mode register 382 includes a check for
fault flag 382(a), a had fault flag 382(b), a data format register
382(c), a read/write flag 382(d), an interrupt enable flag 382(e) and a
current position register 382(f).


Based upon the current sub-buffer and information about the previous value of 
the current sub-buffer table the CPU can determine that the peripheral has 
moved on to the next data segment. CPU 210 may then update the sub-buffer table.


Current position register 382(f) is initially set by CPU 210 when the DMA 
channel is first established to indicate where to begin reading (or writing) 
data 150 from main memory 212 within the current data segment (e.g., 150(3)). 
During the process of retrieving data 150 from main memory 212, DMA engine 372 
keeps track of the next location to be read from in the current data segment 
(e.g., 150(3)). The location of the next piece of data is stored in current 
position register 382(f). Thus, current position register 382(f) typically 
contains an offset address relative to the address of the current data segment 
(e.g., 150(3)).

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

Title:
  snd_au8820 :01:04.0: BUG: , pos = 16386, buffer size = 16384,
  period size = 1024

Status in alsa-driver package in Ubuntu:
  Triaged

Bug description:
  Kernel oops in a new installed system, that I configuring ...

  ProblemType: KernelOops
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-8-generic 4.4.0-8.23
  ProcVersionSignature: Ubuntu 4.4.0-8.23-generic 4.4.2
  Uname: Linux 4.4.0-8-generic i686
  NonfreeKernelModules: nvidia
  Annotation: Your system might become unstable now and might need to be 
restarted.
  ApportVersion: 2.20-0ubuntu3
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  olle   1606 F pulseaudio
   /dev/snd/controlC0:  olle   1606 F pulseaudio
  Date: Mon Feb 29 00:00:56 2016
  Failure: oops
  HibernationDevice: RESUME=UUID=03bed9e9-e39b-4107-8cd6-c2612af9a6aa
  InstallationDate: Installed on 2016-02-28 (0 days ago)
  InstallationMedia: Lubuntu 16.04 LTS "Xenial Xerus" - Alpha i386 (20160226)
  IwConfig:
   enp31s0   no wireless extensions.
   
   lono wireless extensions.
  MachineType: Hewlett-Packard HP xw8400 Workstation
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-8-generic 
root=UUID=2160f8ed-4aa3-4243-b5d6-f87c1967e253 ro quiet splash
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: kerneloops-daemon 0.12+git20090217-3ubuntu9
  RfKill:
   
  SourcePackage: linux
  Title: snd_au8820 :01:04.0: BUG: , pos = 16386, buffer size = 16384, 
period size = 1024
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/09/2009
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 786D5 v02.37
  dmi.board.name: 0A08h
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: NA
  dmi.chassis.asset.tag: CZC722497N
  dmi.chassis.type: 6
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr786D5v02.37:bd07/09/2009:svnHewlett-Packard:pnHPxw8400Workstation:pvr:rvnHewlett-Packard:rn0A08h:rvrNA:cvnHewlett-Packard:ct6:cvr:
  dmi.product.name: HP xw8400 Workstation
  dmi.sys.vendor: Hewlett-Packard

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1551041/+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 1556521] Re: obex-check-device crashed with SIGSEGV in __GI_____strtoul_l_internal()

[Ralf Hildebrandt]

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

root@humbaba:~# gdb /usr/sbin/obex-check-device 
GNU gdb (Ubuntu 7.11-0ubuntu1) 7.11
Copyright (C) 2016 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from /usr/sbin/obex-check-device...Reading symbols from 
/usr/lib/debug//usr/sbin/obex-check-device...done.
done.
(gdb) set args 413c
(gdb) run
Starting program: /usr/sbin/obex-check-device 413c
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".

Program received signal SIGSEGV, Segmentation fault.
__GI_strtoul_l_internal (nptr=0x0, endptr=endptr@entry=0x0, 
base=base@entry=16, group=group@entry=0, 
loc=0x77bbc500 <_nl_global_locale>) at ../stdlib/strtol_l.c:297
297 ../stdlib/strtol_l.c: No such file or directory.
(gdb) bt full
#0  __GI_strtoul_l_internal (nptr=0x0, endptr=endptr@entry=0x0, 
base=base@entry=16, group=group@entry=0, 
loc=0x77bbc500 <_nl_global_locale>) at ../stdlib/strtol_l.c:297
negative = 
cutoff = 
cutlim = 
i = 
s = 0x0
c = 
save = 
end = 
overflow = 
cnt = 
current = 0x77bb7d80 <_nl_C_LC_NUMERIC>
thousands = 0x0
thousands_len = 0
grouping = 0x0
#1  0x77832172 in __strtoul (nptr=, 
endptr=endptr@entry=0x0, base=base@entry=16)
at ../stdlib/strtol.c:109
No locals.
#2  0x004018e9 in main (argc=, argv=0x7fffe628)
at /build/libopenobex-6W6LOb/libopenobex-1.7.1/udev/obex-check-device.c:69
vendor = 16700
product = 
(gdb)

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

Title:
  obex-check-device crashed with SIGSEGV in
  __GI_strtoul_l_internal()

Status in libopenobex package in Ubuntu:
  New

Bug description:
  This happens after the first login after a reboot

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: libopenobex2 1.7.1-4
  ProcVersionSignature: Ubuntu 4.4.0-12.28-generic 4.4.4
  Uname: Linux 4.4.0-8-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  Date: Sun Feb 28 11:36:29 2016
  Dependencies:
   gcc-6-base 6-20160227-0ubuntu1
   libc6 2.21-0ubuntu6
   libgcc1 1:6-20160227-0ubuntu1
   libudev1 229-2ubuntu1
   libusb-1.0-0 2:1.0.20-1
  ExecutablePath: /usr/sbin/obex-check-device
  InstallationDate: Installed on 2014-02-07 (764 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  ProcCmdline: /usr/sbin/obex-check-device 413c
  ProcEnviron:
   
  SegvAnalysis:
   Segfault happened at: 0x7f97ace9f674 <__GI_strtoul_l_internal+68>:   
movsbq (%r14),%rax
   PC (0x7f97ace9f674) ok
   source "(%r14)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%rax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: libopenobex
  StacktraceTop:
   __GI_strtoul_l_internal (nptr=0x0, endptr=0x0, base=16, group=, loc=0x7f97ad229500 <_nl_global_locale>) at ../stdlib/strtol_l.c:297
   main ()
  Title: obex-check-device crashed with SIGSEGV in __GI_strtoul_l_internal()
  UpgradeStatus: Upgraded to xenial on 2016-02-27 (14 days ago)
  UserGroups:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libopenobex/+bug/1556521/+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 1468027] Re: change default CJK fonts to Noto CJK

[Yuan Chao]

> BTW, may this be a related bug?
> https://bugs.launchpad.net/ubuntu-translations/+bug/1540063
It looks like some (traditional?) Chinese font (kai?) is picked up instead of 
the "Takao Pゴシック" Japanese font requested. Due to the lack of the glyphs, it's 
further fallbacked to other(?) "ゴシック" Japanese font. Should be due to some 
mis-configuration of the font alias. Doesn't look like a related bug to me.

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

Title:
  change default CJK fonts to Noto CJK

Status in Fontconfig:
  Confirmed
Status in fonts-noto-cjk package in Ubuntu:
  In Progress
Status in language-selector package in Ubuntu:
  Fix Released
Status in ubuntu-meta package in Ubuntu:
  In Progress

Bug description:
  just realize that fonts-noto-cjk is available in the repository, finally its 
packaged.
  i don't really know about korean community.
  But for Chinese and Japanese community, i think that the answer is clear.
  noto-cjk is definitely better what we had before, like fonts- wqy and 
fonts-droid.
  Android community had received these complains for years, finally they got 
them fixed on lollipop.
  Fedora also set it as default chinese font start from F21.
  and of course, i still hope that ubuntu could drop those 69-language-selector 
fontconfig files, just like what F13 did.

To manage notifications about this bug go to:
https://bugs.launchpad.net/fontconfig/+bug/1468027/+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 1556521] Re: obex-check-device crashed with SIGSEGV in __GI_____strtoul_l_internal()

[Apport retracing service]

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

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 #1553358, 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.

** Attachment removed: "CoreDump.gz"
   
https://bugs.launchpad.net/bugs/1556521/+attachment/4597333/+files/CoreDump.gz

** Attachment removed: "Disassembly.txt"
   
https://bugs.launchpad.net/bugs/1556521/+attachment/4597334/+files/Disassembly.txt

** Attachment removed: "ProcMaps.txt"
   
https://bugs.launchpad.net/bugs/1556521/+attachment/4597336/+files/ProcMaps.txt

** Attachment removed: "ProcStatus.txt"
   
https://bugs.launchpad.net/bugs/1556521/+attachment/4597337/+files/ProcStatus.txt

** Attachment removed: "Registers.txt"
   
https://bugs.launchpad.net/bugs/1556521/+attachment/4597338/+files/Registers.txt

** Attachment removed: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/1556521/+attachment/4597339/+files/Stacktrace.txt

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1556521/+attachment/4597340/+files/ThreadStacktrace.txt

** This bug has been marked a duplicate of private bug 1553358

** 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 libopenobex in Ubuntu.
https://bugs.launchpad.net/bugs/1556521

Title:
  obex-check-device crashed with SIGSEGV in
  __GI_strtoul_l_internal()

Status in libopenobex package in Ubuntu:
  New

Bug description:
  This happens after the first login after a reboot

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: libopenobex2 1.7.1-4
  ProcVersionSignature: Ubuntu 4.4.0-12.28-generic 4.4.4
  Uname: Linux 4.4.0-8-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  Date: Sun Feb 28 11:36:29 2016
  Dependencies:
   gcc-6-base 6-20160227-0ubuntu1
   libc6 2.21-0ubuntu6
   libgcc1 1:6-20160227-0ubuntu1
   libudev1 229-2ubuntu1
   libusb-1.0-0 2:1.0.20-1
  ExecutablePath: /usr/sbin/obex-check-device
  InstallationDate: Installed on 2014-02-07 (764 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  ProcCmdline: /usr/sbin/obex-check-device 413c
  ProcEnviron:
   
  SegvAnalysis:
   Segfault happened at: 0x7f97ace9f674 <__GI_strtoul_l_internal+68>:   
movsbq (%r14),%rax
   PC (0x7f97ace9f674) ok
   source "(%r14)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%rax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: libopenobex
  StacktraceTop:
   __GI_strtoul_l_internal (nptr=0x0, endptr=0x0, base=16, group=, loc=0x7f97ad229500 <_nl_global_locale>) at ../stdlib/strtol_l.c:297
   main ()
  Title: obex-check-device crashed with SIGSEGV in __GI_strtoul_l_internal()
  UpgradeStatus: Upgraded to xenial on 2016-02-27 (14 days ago)
  UserGroups:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libopenobex/+bug/1556521/+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 1539158] Re: Unable to pair with in-car hands-free system after OTA-9 update

[Stunts]

Humm... I guess I'll have to read a bit on how to do the reflashes.
Worst case scenario I'll have to wait until OTA10, which should be released 
somewhere in April IIRC.
I will report back if I make some progress on this front (hopefully with enough 
time before OTA10 lands for any further tweaking).

-- 
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:
  Invalid
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 1468027] Re: change default CJK fonts to Noto CJK

[Gunnar Hjalmarsson]

On 2016-03-13 00:46, Kenichi Ito wrote:
> BTW, may this be a related bug?
> https://bugs.launchpad.net/ubuntu-translations/+bug/1540063

Don't think so. One step in debugging bug #1540063 may be to run a live
session in Japanese, open a terminal window and run this command:

fc-match -s | head -10

The first font in the output ought to be "Takao Pゴシック" "Regular".

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

Title:
  change default CJK fonts to Noto CJK

Status in Fontconfig:
  Confirmed
Status in fonts-noto-cjk package in Ubuntu:
  In Progress
Status in language-selector package in Ubuntu:
  Fix Released
Status in ubuntu-meta package in Ubuntu:
  In Progress

Bug description:
  just realize that fonts-noto-cjk is available in the repository, finally its 
packaged.
  i don't really know about korean community.
  But for Chinese and Japanese community, i think that the answer is clear.
  noto-cjk is definitely better what we had before, like fonts- wqy and 
fonts-droid.
  Android community had received these complains for years, finally they got 
them fixed on lollipop.
  Fedora also set it as default chinese font start from F21.
  and of course, i still hope that ubuntu could drop those 69-language-selector 
fontconfig files, just like what F13 did.

To manage notifications about this bug go to:
https://bugs.launchpad.net/fontconfig/+bug/1468027/+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 1468027] Re: change default CJK fonts to Noto CJK

[Kenichi Ito]

BTW, may this be a related bug?
https://bugs.launchpad.net/ubuntu-translations/+bug/1540063

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

Title:
  change default CJK fonts to Noto CJK

Status in Fontconfig:
  Confirmed
Status in fonts-noto-cjk package in Ubuntu:
  In Progress
Status in language-selector package in Ubuntu:
  Fix Released
Status in ubuntu-meta package in Ubuntu:
  In Progress

Bug description:
  just realize that fonts-noto-cjk is available in the repository, finally its 
packaged.
  i don't really know about korean community.
  But for Chinese and Japanese community, i think that the answer is clear.
  noto-cjk is definitely better what we had before, like fonts- wqy and 
fonts-droid.
  Android community had received these complains for years, finally they got 
them fixed on lollipop.
  Fedora also set it as default chinese font start from F21.
  and of course, i still hope that ubuntu could drop those 69-language-selector 
fontconfig files, just like what F13 did.

To manage notifications about this bug go to:
https://bugs.launchpad.net/fontconfig/+bug/1468027/+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 1468027] Re: change default CJK fonts to Noto CJK

[Gunnar Hjalmarsson]

On 2016-03-12 18:46, Mingye Wang wrote:
> Let me file the fc demi report separately then. A fix is always
> better than a hack, and with Noto Sans CJK hacked there are still a
> whole bunch of Notos and other weight-rich fonts.

A separate fc demi report is a good idea IMO.

As regards other Notos: at the moment we have other default fonts in
Ubuntu for Japanese and Korean (may be changed in 16.04+), so that's not
an emergency for the 16.04 release.

> Can't see xenial on bzr...

Right, that is true for many packages. Don't know why. I have made
patches using diff in some cases.

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

Title:
  change default CJK fonts to Noto CJK

Status in Fontconfig:
  Confirmed
Status in fonts-noto-cjk package in Ubuntu:
  In Progress
Status in language-selector package in Ubuntu:
  Fix Released
Status in ubuntu-meta package in Ubuntu:
  In Progress

Bug description:
  just realize that fonts-noto-cjk is available in the repository, finally its 
packaged.
  i don't really know about korean community.
  But for Chinese and Japanese community, i think that the answer is clear.
  noto-cjk is definitely better what we had before, like fonts- wqy and 
fonts-droid.
  Android community had received these complains for years, finally they got 
them fixed on lollipop.
  Fedora also set it as default chinese font start from F21.
  and of course, i still hope that ubuntu could drop those 69-language-selector 
fontconfig files, just like what F13 did.

To manage notifications about this bug go to:
https://bugs.launchpad.net/fontconfig/+bug/1468027/+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 1556511] Re: package ibus 1.5.5-1ubuntu3 failed to install/upgrade: el subproceso script pre-removal nuevo devolvió el código de salida de error 127

[Apport retracing service]

** Tags removed: need-duplicate-check

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

Title:
  package ibus 1.5.5-1ubuntu3 failed to install/upgrade: el subproceso
  script pre-removal nuevo devolvió el código de salida de error 127

Status in ibus package in Ubuntu:
  New

Bug description:
  ok

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: ibus 1.5.5-1ubuntu3
  ProcVersionSignature: Ubuntu 3.19.0-49.55~14.04.1-generic 3.19.8-ckt12
  Uname: Linux 3.19.0-49-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.19
  AptOrdering:
   ibus: Install
   update-notifier-common: Configure
   ttf-mscorefonts-installer: Configure
   ibus: Configure
   python-ibus: Configure
  Architecture: amd64
  Date: Sat Mar 12 20:23:51 2016
  DpkgHistoryLog:
   Start-Date: 2016-03-12  20:23:45
   Commandline: apt-get install --yes --force-yes -f
   Upgrade: ibus:amd64 (1.5.5-1ubuntu3, 1.5.5-1ubuntu3.2)
  DuplicateSignature: package:ibus:1.5.5-1ubuntu3:el subproceso script 
pre-removal nuevo devolvió el código de salida de error 127
  ErrorMessage: el subproceso script pre-removal nuevo devolvió el código de 
salida de error 127
  InstallationDate: Installed on 2015-08-26 (199 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.5
   apt  1.0.1ubuntu2.11
  SourcePackage: ibus
  Title: package ibus 1.5.5-1ubuntu3 failed to install/upgrade: el subproceso 
script pre-removal nuevo devolvió el código de salida de error 127
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1556511/+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 1443290] Re: [Gallery] viewing pictures from the file browser creates duplicates

[Anupam]

** Summary changed:

- Gallery viewing pictures using the file browser
+ [Gallery] viewing pictures from the file browser creates duplicates

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

Title:
  [Gallery] viewing pictures from the file browser creates duplicates

Status in gallery-app package in Ubuntu:
  New

Bug description:
  if I use the file browser to locate images and then open them using
  the gallery app, it appears a copy of the image is created in my home
  directory. This copy then remains after tje gallery is closed, if the
  same process is carried out another copy appears, the file needs to be
  manually removed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gallery-app/+bug/1443290/+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 1556511] [NEW] package ibus 1.5.5-1ubuntu3 failed to install/upgrade: el subproceso script pre-removal nuevo devolvió el código de salida de error 127

[Javier Hernán Quiroz]

Public bug reported:

ok

ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: ibus 1.5.5-1ubuntu3
ProcVersionSignature: Ubuntu 3.19.0-49.55~14.04.1-generic 3.19.8-ckt12
Uname: Linux 3.19.0-49-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.19
AptOrdering:
 ibus: Install
 update-notifier-common: Configure
 ttf-mscorefonts-installer: Configure
 ibus: Configure
 python-ibus: Configure
Architecture: amd64
Date: Sat Mar 12 20:23:51 2016
DpkgHistoryLog:
 Start-Date: 2016-03-12  20:23:45
 Commandline: apt-get install --yes --force-yes -f
 Upgrade: ibus:amd64 (1.5.5-1ubuntu3, 1.5.5-1ubuntu3.2)
DuplicateSignature: package:ibus:1.5.5-1ubuntu3:el subproceso script 
pre-removal nuevo devolvió el código de salida de error 127
ErrorMessage: el subproceso script pre-removal nuevo devolvió el código de 
salida de error 127
InstallationDate: Installed on 2015-08-26 (199 days ago)
InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
RelatedPackageVersions:
 dpkg 1.17.5ubuntu5.5
 apt  1.0.1ubuntu2.11
SourcePackage: ibus
Title: package ibus 1.5.5-1ubuntu3 failed to install/upgrade: el subproceso 
script pre-removal nuevo devolvió el código de salida de error 127
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package trusty

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

Title:
  package ibus 1.5.5-1ubuntu3 failed to install/upgrade: el subproceso
  script pre-removal nuevo devolvió el código de salida de error 127

Status in ibus package in Ubuntu:
  New

Bug description:
  ok

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: ibus 1.5.5-1ubuntu3
  ProcVersionSignature: Ubuntu 3.19.0-49.55~14.04.1-generic 3.19.8-ckt12
  Uname: Linux 3.19.0-49-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.19
  AptOrdering:
   ibus: Install
   update-notifier-common: Configure
   ttf-mscorefonts-installer: Configure
   ibus: Configure
   python-ibus: Configure
  Architecture: amd64
  Date: Sat Mar 12 20:23:51 2016
  DpkgHistoryLog:
   Start-Date: 2016-03-12  20:23:45
   Commandline: apt-get install --yes --force-yes -f
   Upgrade: ibus:amd64 (1.5.5-1ubuntu3, 1.5.5-1ubuntu3.2)
  DuplicateSignature: package:ibus:1.5.5-1ubuntu3:el subproceso script 
pre-removal nuevo devolvió el código de salida de error 127
  ErrorMessage: el subproceso script pre-removal nuevo devolvió el código de 
salida de error 127
  InstallationDate: Installed on 2015-08-26 (199 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.5
   apt  1.0.1ubuntu2.11
  SourcePackage: ibus
  Title: package ibus 1.5.5-1ubuntu3 failed to install/upgrade: el subproceso 
script pre-removal nuevo devolvió el código de salida de error 127
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1556511/+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 1533965] Re: Each time of opening downloaded file with Gallery app will create a copy accordingly

[Anupam]

related to bug #1443290?

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

Title:
  Each time of opening downloaded file with Gallery app will create a
  copy accordingly

Status in gallery-app package in Ubuntu:
  New

Bug description:
  Test Environment:
  $ system-image-cli -i
  current build number: 228
  device name: krillin
  channel: ubuntu-touch/rc-proposed/bq-aquaris.en
  last update: 2016-01-13 07:38:39
  version version: 228
  version ubuntu: 20160113
  version device: 20160108-efc96d8
  version custom: 2015--36-46-vivid

  Steps:
  1.Launch browser app
  2.Access website: shop.ubuntu.com
  3.Tap and hold on an image to download it to Download directory
  4.Go to browser settings -> Downloads and tap on the downloaded image
  5.Select gallery to open
  6.Repeat step4~step5 3 times
  7.Back to gallery app and check

  Actual result:
  There are 3 copies of the same image displayed

  Expected result:
  End user may not want to create duplicate files and waste the storage space

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gallery-app/+bug/1533965/+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 1419495] Re: Need to share multiple photoes through content hub

[Anupam]

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

** This bug is no longer a duplicate of bug 1479279
   Cannot share more than one image at a time
** This bug has been marked a duplicate of bug 1523573
   Doesn't let you share several images

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

Title:
  Need to share multiple photoes through content hub

Status in gallery-app package in Ubuntu:
  New

Bug description:
  In galleray app, share button is disabled when multiple photoes are
  selected.

  I have a dropbox client that can do multiple photo upload in one
  contenthub exchange. I would like to use it to upload my photoes
  taken.

  And in upload mode, clicking date won't select all photos in that day.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gallery-app/+bug/1419495/+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 1479279] Re: Cannot share more than one image at a time

[Anupam]

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

** This bug has been marked a duplicate of bug 1523573
   Doesn't let you share several images

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

Title:
  Cannot share more than one image at a time

Status in gallery-app package in Ubuntu:
  Confirmed

Bug description:
  When multiple images are selected the Share option becomes greyed out
  making it impossible to share multiple images.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gallery-app/+bug/1479279/+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 1554616] Re: Shell and dash visual issues with new UITK and palette

[Michał Sawicz]

** Changed in: unity8 (Ubuntu)
   Status: Fix Released => In Progress

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

Title:
  Shell and dash visual issues with new UITK and palette

Status in Canonical System Image:
  In Progress
Status in Ubuntu UX:
  New
Status in unity8 package in Ubuntu:
  In Progress

Bug description:
  There is a set of UI issues with the new UITK and palette, I will
  attach screenshots for each of them with a comment.

  The new UITK is landing here: https://requests.ci-
  train.ubuntu.com/#/ticket/905

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: unity8 8.11+15.04.20160304-0ubuntu1 [origin: 
LP-PPA-ci-train-ppa-service-landing-050]
  Uname: Linux 3.4.67 armv7l
  ApportVersion: 2.17.2-0ubuntu1.3touch1
  Architecture: armhf
  Date: Tue Mar  8 17:59:10 2016
  InstallationDate: Installed on 2016-03-08 (0 days ago)
  InstallationMedia: Ubuntu 15.04 - armhf (20160308-020304)
  SourcePackage: unity8
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1554616/+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 1475084] Re: Gallery app appears to scan all folders for images

[Anupam]

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

** This bug has been marked a duplicate of bug 1445755
   Provide a way to hide images from a particular location

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

Title:
  Gallery app appears to scan all folders for images

Status in gallery-app package in Ubuntu:
  Confirmed

Bug description:
  The gallery app appears to scan all user folders for images, as a
  result album art for music collection is shown in the gallery. It
  should just show images in the 'Pictures' folder.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gallery-app/+bug/1475084/+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 1512485] Re: Support making a copy of a photo

[Launchpad Bug Tracker]

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

** Changed in: gallery-app (Ubuntu)
   Status: New => Confirmed

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

Title:
  Support making a copy of a photo

Status in gallery-app package in Ubuntu:
  Confirmed

Bug description:
  I may want to edit it into a new form say by cropping and rotating
  while retaining the original.

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

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

-- 
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 1534098] Re: Update to libsndfile version 1.0.26

[Sean M. Pappalardo]

This version of libsndfile also supports ALAC-encoded M4A files.

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

Title:
  Update to libsndfile version 1.0.26

Status in libsndfile package in Ubuntu:
  Confirmed

Bug description:
  Hi libsndfile version 1.0.26 has some new features in regards to
  reading and writing chunks from wav files. The previous versions have
  no access to the chunks.

  The specific api methods are here

  https://github.com/erikd/libsndfile/blob/master/src/sndfile.c#L3041

  They have released that version on their site and was wondering if
  it's possible to get it into an updated package ?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libsndfile/+bug/1534098/+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 1556507] [NEW] add the possibility to close the scope app

[Emanuele Antonio Faraone]

Public bug reported:

add the possibility to close the scope app, since now it is impossible
to do this thing and penalizes the screen, as well as performance

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

Title:
  add the possibility to close the scope app

Status in unity8 package in Ubuntu:
  New

Bug description:
  add the possibility to close the scope app, since now it is impossible
  to do this thing and penalizes the screen, as well as performance

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1556507/+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 1520512] Re: Feature: lighten image

[Launchpad Bug Tracker]

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

** Changed in: gallery-app (Ubuntu)
   Status: New => Confirmed

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

Title:
  Feature: lighten image

Status in gallery-app package in Ubuntu:
  Confirmed

Bug description:
  This is probably not as important as Bug #1520502 but after crop it's
  probably the most common thing people need to adjust in their photos.
  Should be possible to lighten an image.  Normally this is when you
  have a photo of someone that's backlit, you need to lighten the image
  until you can make out their faces.

  I imagine there's clever things that can be done to improve the
  dynamic range across the photo, and that would be great, but
  straightforward "make everything lighter" is most important.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gallery-app/+bug/1520512/+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 1553431] Re: Feature: clip video

[Launchpad Bug Tracker]

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

** Changed in: gallery-app (Ubuntu)
   Status: New => Confirmed

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

Title:
  Feature: clip video

Status in gallery-app package in Ubuntu:
  Confirmed

Bug description:
  The gallery currently allows editing photos by cropping them or
  rotating them.  By analogy, it should be possible to extract a short
  portion of a video clip and save it as a new video.  Note that saving
  as a new video is critical, do not overwrite the original.  This is
  because you might want to extract multiple clips from a single video.

  Justification for why this is important enough to add to a core app:

  A phone is a communications device.  The reason for adding a video
  camera to a phone is so that you can quickly share a moment with your
  friends, on the spot, immediately.  It's not really so that you can
  shoot footage for the feature film you're developing in your studio.

  You don't want to waste data and you don't want to waste your friends'
  time.  You want to send as short a clip as possible, normally just a
  few seconds.  But you have to shoot a fairly long video, several
  minutes, to be sure of capturing the right moment.  So without the
  ability to clip the video it's almost impossible to capture something
  worth sharing.

  Mucking around with a specialised video editing app is complicated and
  loses the spontaneity.  There is definitely a role for a feature-rich,
  sophisticated video-editing app.  I would certainly want this for more
  interesting cases.  But I would only resort to that on rare occasions.

  It could be argued that this is the responsibility of individual
  social media apps.  But if you use multiple social media apps that
  wastes time.  It also wastes developer time and increases the UI
  surface area.

  Adding a video clip feature would take the video recording
  functionality from a "maybe I would use that sometimes" to a
  "something I couldn't live without" level of usefulness.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gallery-app/+bug/1553431/+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 1455594] Re: downsize pictures before sharing

[Anupam]

** Also affects: gallery-app (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  downsize pictures before sharing

Status in camera-app:
  Confirmed
Status in camera-app package in Ubuntu:
  Confirmed
Status in gallery-app package in Ubuntu:
  New

Bug description:
  Well i was wondering if you guys can add a resize option to your
  gallery/camera app, so after taking a picture we can share it easily
  on social media or some forums that have a limit to the size of
  pictures that are allowed to be posted.

  Regards,

To manage notifications about this bug go to:
https://bugs.launchpad.net/camera-app/+bug/1455594/+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 1520502] Re: Feature: resize image

[Launchpad Bug Tracker]

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

** Changed in: gallery-app (Ubuntu)
   Status: New => Confirmed

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

Title:
  Feature: resize image

Status in gallery-app package in Ubuntu:
  Confirmed

Bug description:
  Gallery includes a crop feature, which is nice.  The other standard
  feature people need is resize.  This is especially true since the
  camera takes rather large photos unsuitable for sharing, but there's
  no way to shrink the files down.  See also Bug #1512651 to implement
  this in Dekko, but regardless of whether that's fixed this should be a
  feature in Gallery.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gallery-app/+bug/1520502/+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 1549455] Re: Unity 8/Mir doesn't load on Intel Pineview graphics

[Emanuele Antonio Faraone]

then?

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

Title:
  Unity 8/Mir doesn't load on Intel Pineview graphics

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

Bug description:
  This bug Makes the pc UNUSABLE
  when I try to launch Unity 8 and Mir, after writing the password on the login 
(in the image attached) the bar to enter the password disappears and my 
computer screen stays stuck without them let me do anything. the connection 
begins to separate and reattach alone and I can only move the cursor. it makes 
the computer unusable and I am forced to restart forced to then enter into 
Unity 7. represented in the screenshot is the lock status after entering the 
password.
  Version: unity8.11+16.04.201602.16.1
  Version of Mir : 0.20.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1549455/+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 1512290] Re: gnome-screenshot produces very low quality blurry screenshots

[Amr Ibrahim]

** Changed in: gtk+3.0 (Ubuntu)
   Status: Triaged => Fix Released

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

Title:
  gnome-screenshot produces very low quality blurry screenshots

Status in GTK+:
  Fix Released
Status in gtk+3.0 package in Ubuntu:
  Fix Released
Status in gtk+3.0 source package in Wily:
  Triaged

Bug description:
  I believe, this is because I am using a HiDPI display. Every time I
  take a screenshot, I get a blurry image. This is not what I want when
  making a screenshot. Everywhere else when I make a screenshot, I get a
  100% copy of my screen, pixel-perfect.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: gnome-screenshot 3.16.2-0ubuntu3
  ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
  Uname: Linux 4.2.0-16-generic x86_64
  ApportVersion: 2.19.1-0ubuntu4
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Nov  2 13:11:55 2015
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-10-22 (10 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: gnome-screenshot
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gtk/+bug/1512290/+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 1515810] Re: Doesn't merge into unity panel when maximized

[Amr Ibrahim]

Thanks for fixing this. A big inconsistency!

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

Title:
  Doesn't merge into unity panel when maximized

Status in gedit package in Ubuntu:
  Fix Released
Status in gtk+3.0 package in Ubuntu:
  In Progress

Bug description:
  In a ubuntu session open gedit, maximize.
  I guess because it doesn't use window deco (unity) when maximized you get 2 
sets of action buttons, one from gedit in toolbar, one from light-themes in 
unity panel

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gedit 3.18.2-1ubuntu1
  ProcVersionSignature: Ubuntu 4.2.0-17.21-generic 4.2.3
  Uname: Linux 4.2.0-17-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.19.2-0ubuntu5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Nov 12 19:04:02 2015
  InstallationDate: Installed on 2015-10-25 (18 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: gedit
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1515810/+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 1539158] Re: Unable to pair with in-car hands-free system after OTA-9 update

[Simon Fels]

@Stunts: Do the following on your HOST system:

$ sudo add-apt-repository ppa:phablet-team/ubuntu/tools
$ sudo apt-get install phablet-tools-citrain

Now connect the phone over adb (make sure developer mode is enabled):

Still from the HOST system:

$ citrain device-upgrade  

PLEASE KEEP IN MIND: This will change the content of the device rootfs
system. If you don't want to reflash via ubuntu-device-flash or don't
know how to do that it might be better to wait until this fix lands with
the next OTA.

-- 
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:
  Invalid
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 1556493] Re: package perl-modules 5.20.2-6ubuntu0.2 failed to install/upgrade: package perl-modules is already installed and configured

[Apport retracing service]

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

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 #1556491, 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.

** Tags removed: need-duplicate-check

** This bug has been marked a duplicate of bug 1556491
   package perl-modules 5.20.2-6ubuntu0.2 failed to install/upgrade: package 
perl-modules is already installed and configured

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

Title:
  package perl-modules 5.20.2-6ubuntu0.2 failed to install/upgrade:
  package perl-modules is already installed and configured

Status in perl package in Ubuntu:
  New

Bug description:
  This is a stacionary computer, bug report when i try upgrade system

  ProblemType: Package
  DistroRelease: Ubuntu 15.10
  Package: perl-modules 5.20.2-6ubuntu0.2
  ProcVersionSignature: Ubuntu 4.2.0-30.36-generic 4.2.8-ckt3
  Uname: Linux 4.2.0-30-generic x86_64
  ApportVersion: 2.19.1-0ubuntu5
  AptdaemonVersion: 1.1.1+bzr982-0ubuntu14
  Architecture: amd64
  Date: Sat Mar 12 19:51:24 2016
  DuplicateSignature: package:perl-modules:5.20.2-6ubuntu0.2:package 
perl-modules is already installed and configured
  ErrorMessage: package perl-modules is already installed and configured
  InstallationDate: Installed on 2015-11-01 (132 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.2ubuntu5.1
   apt  1.0.10.2ubuntu1
  SourcePackage: perl
  Title: package perl-modules 5.20.2-6ubuntu0.2 failed to install/upgrade: 
package perl-modules is already installed and configured
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/perl/+bug/1556493/+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 1549455] Re: Unity 8/Mir doesn't load on Intel Pineview graphics

[Andreas Pokorny]

Yes I believe there is still a problem setting up the rendering context. When I 
run unity8-dash in isolation I get this:
file:///usr/share/unity8//Dash/Dash.qml:39: ReferenceError: window is not 
defined
file:///usr/share/unity8//Dash/Dash.qml:265: ReferenceError: scopeStyle is not 
defined
ASSERT: "eglDestroyContext(mEglDisplay, mEglContext) == EGL_TRUE" in file 
../../../src/ubuntumirclient/glcontext.cpp, line 71

A failure there will affect all qt applications..

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

Title:
  Unity 8/Mir doesn't load on Intel Pineview graphics

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

Bug description:
  This bug Makes the pc UNUSABLE
  when I try to launch Unity 8 and Mir, after writing the password on the login 
(in the image attached) the bar to enter the password disappears and my 
computer screen stays stuck without them let me do anything. the connection 
begins to separate and reattach alone and I can only move the cursor. it makes 
the computer unusable and I am forced to restart forced to then enter into 
Unity 7. represented in the screenshot is the lock status after entering the 
password.
  Version: unity8.11+16.04.201602.16.1
  Version of Mir : 0.20.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1549455/+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 1556493] [NEW] package perl-modules 5.20.2-6ubuntu0.2 failed to install/upgrade: package perl-modules is already installed and configured

[Grzegorz]

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

Public bug reported:

This is a stacionary computer, bug report when i try upgrade system

ProblemType: Package
DistroRelease: Ubuntu 15.10
Package: perl-modules 5.20.2-6ubuntu0.2
ProcVersionSignature: Ubuntu 4.2.0-30.36-generic 4.2.8-ckt3
Uname: Linux 4.2.0-30-generic x86_64
ApportVersion: 2.19.1-0ubuntu5
AptdaemonVersion: 1.1.1+bzr982-0ubuntu14
Architecture: amd64
Date: Sat Mar 12 19:51:24 2016
DuplicateSignature: package:perl-modules:5.20.2-6ubuntu0.2:package perl-modules 
is already installed and configured
ErrorMessage: package perl-modules is already installed and configured
InstallationDate: Installed on 2015-11-01 (132 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.18.2ubuntu5.1
 apt  1.0.10.2ubuntu1
SourcePackage: perl
Title: package perl-modules 5.20.2-6ubuntu0.2 failed to install/upgrade: 
package perl-modules is already installed and configured
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: already-installed amd64 apport-package wily

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

Title:
  package perl-modules 5.20.2-6ubuntu0.2 failed to install/upgrade:
  package perl-modules is already installed and configured

Status in perl package in Ubuntu:
  New

Bug description:
  This is a stacionary computer, bug report when i try upgrade system

  ProblemType: Package
  DistroRelease: Ubuntu 15.10
  Package: perl-modules 5.20.2-6ubuntu0.2
  ProcVersionSignature: Ubuntu 4.2.0-30.36-generic 4.2.8-ckt3
  Uname: Linux 4.2.0-30-generic x86_64
  ApportVersion: 2.19.1-0ubuntu5
  AptdaemonVersion: 1.1.1+bzr982-0ubuntu14
  Architecture: amd64
  Date: Sat Mar 12 19:51:24 2016
  DuplicateSignature: package:perl-modules:5.20.2-6ubuntu0.2:package 
perl-modules is already installed and configured
  ErrorMessage: package perl-modules is already installed and configured
  InstallationDate: Installed on 2015-11-01 (132 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.2ubuntu5.1
   apt  1.0.10.2ubuntu1
  SourcePackage: perl
  Title: package perl-modules 5.20.2-6ubuntu0.2 failed to install/upgrade: 
package perl-modules is already installed and configured
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Re: [Touch-packages] [Bug 1556330] Re: upstream curl bug #1371: p12 client certificates code is broken

[Matthew Hall]

> On Mar 12, 2016, at 8:55 AM, LocutusOfBorg  
> wrote:
> 
> unfortunately it doesn't seem to build.

It built perfectly when I modified the source for 14.04 LTS.

Also thanks for the more detailed stable release diff procedures. I did
read the stable release update page to write the original report but it
didn't explain the commands to run as a community member. Who has access
to add the additional procedures you wrote into the page? This would be
very helpful for other technical users without knowledge of the special
Debian and Ubuntu processes.

Matthew.

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

Title:
  upstream curl bug #1371: p12 client certificates code is broken

Status in curl package in Ubuntu:
  Fix Released
Status in curl source package in Trusty:
  Triaged

Bug description:
  [Impact]

  The bug makes it impossible to use PKCS#12 secure storage of client
  certificates and private keys with any affected Ubuntu releases. The
  fix is one line fixing a broken switch statement and was already
  tested against Ubuntu 14.04 LTS with a rebuilt curl package.

  This was fixed in upstream libcurl in the following bug:

  https://sourceforge.net/p/curl/bugs/1371/

  The bug fix consists of one missing break statement at the end of a
  case in a switch statement.

  I personally patched the bug using source code release
  curl_7.35.0-1ubuntu2.6.dsc, used in Ubuntu 14.04 LTS, and verified it
  does indeed fix the bug and all of the package's tests still pass
  afterwards.

  [Test Case]

  The bug can be reproduced using the following libcurl parameters (even
  via CLI, pycurl, etc.).

  CURLOPT_SSLCERTTYPE == "P12"
  CURLOPT_SSLCERT = path to PKCS#12
  CURLOPT_SSLKEY = path to PKCS#12
  CURLOPT_SSLKEYPASSWD = key for PKCS#12 if needed

  Basically, just use a PKCS#12 format client certificate and private
  key against some certificate protected web server.

  [Regression Potential]

  If it could possibly break anything, which is extraordinarily
  unlikely, it would break one of the three client certificate formats
  (most likely PKCS#12 but also PEM or DER). Note 1/3 formats is already
  broken due to the bug. Client certificates of all three types could be
  checked to prevent this.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/curl/+bug/1556330/+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 1556488] Re: systemd crashed with SIGABRT when shutting down

[Apport retracing service]

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

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 #1547851, 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.

** Attachment removed: "CoreDump.gz"
   
https://bugs.launchpad.net/bugs/1556488/+attachment/4597215/+files/CoreDump.gz

** Attachment removed: "Disassembly.txt"
   
https://bugs.launchpad.net/bugs/1556488/+attachment/4597218/+files/Disassembly.txt

** Attachment removed: "ProcMaps.txt"
   
https://bugs.launchpad.net/bugs/1556488/+attachment/4597224/+files/ProcMaps.txt

** Attachment removed: "ProcStatus.txt"
   
https://bugs.launchpad.net/bugs/1556488/+attachment/4597226/+files/ProcStatus.txt

** Attachment removed: "Registers.txt"
   
https://bugs.launchpad.net/bugs/1556488/+attachment/4597227/+files/Registers.txt

** Attachment removed: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/1556488/+attachment/4597228/+files/Stacktrace.txt

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1556488/+attachment/4597229/+files/ThreadStacktrace.txt

** This bug has been marked a duplicate of private bug 1547851

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

Title:
  systemd crashed with SIGABRT when shutting down

Status in systemd package in Ubuntu:
  New

Bug description:
  Installed 16.04 daily build on my Dell XPS 12 (9250), system up to date when 
this happened.
  When my new  SATA to USB Type-C (Thunderbolt) adapter is plugged, shutting 
down the computer freezes on the Ubuntu... splash.
  Even if I boot with everything plugged in it still happens.
  Overall only the USB Type C (Thunderbolt) to USB3 adapter worked for me, but 
only if booted while plugged in, hot plugin not working.

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: systemd 229-2ubuntu1 [modified: 
usr/share/dbus-1/system-services/org.freedesktop.systemd1.service]
  ProcVersionSignature: Ubuntu 4.4.0-12.28-generic 4.4.4
  Uname: Linux 4.4.0-12-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  Date: Sat Mar 12 19:38:37 2016
  ExecutablePath: /lib/systemd/systemd
  InstallationDate: Installed on 2016-02-27 (14 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160226)
  MachineType: Dell Inc. XPS 12 9250
  ProcCmdline: /lib/systemd/systemd --user
  ProcEnviron:
   LANG=en_GB.UTF-8
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-12-generic.efi.signed 
root=UUID=5dd0bb11-5f5b-448e-886f-13658e54059f 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
   [EXTENDED]   /etc/systemd/system/display-manager.service → 
/lib/systemd/system/display-manager.service.d/xdiagnose.conf
   
   3 overridden configuration files found.
  SystemdFailedUnits: Error: command ['systemctl', 'status', '--full', 
'Error:'] failed with exit code 1: Failed to get properties: Failed to activate 
service 'org.freedesktop.systemd1': timed out
  Title: systemd crashed with SIGABRT
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  dmi.bios.date: 01/20/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 01.01.06
  dmi.board.name: 0XYRGN
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr01.01.06:bd01/20/2016:svnDellInc.:pnXPS129250:pvr:rvnDellInc.:rn0XYRGN:rvrA00:cvnDellInc.:ct8:cvr:
  dmi.product.name: XPS 12 9250
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1556488/+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 1553685] Re: Lenovo Y700-17ISK subwoofer doesn't work

[Jonas Frei]

Connecting 0x17 with hdajackretask doesn't seem to work either. It adds
a third channel which is called "subwoofer" in the sound settings, but
when testing the subwoofer there is still no sound...

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

Title:
  Lenovo Y700-17ISK subwoofer doesn't work

Status in alsa-driver package in Ubuntu:
  Incomplete

Bug description:
  Lenovo Y700-17ISK (Intel Core i7-6700HQ/RAM 16GB/SSD 512GB/Nvidia GTX960M 4GB)
  Operating system: Ubuntu 16.04 (xenial-desktop-amd64.iso 04-Mar-2016, kernel 
4.4.0-10-generic, nvidia 361.28)

  Problem: Notebook subwoofer doesn't work.

  Judging from alsa-info.sh output, there is no pin declared for the bass 
output by BIOS.
  Please find a zip file attached: 'alsa-info_hdajackretask-unconnected-pins'

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-10-generic 4.4.0-10.25
  ProcVersionSignature: Ubuntu 4.4.0-10.25-generic 4.4.3
  Uname: Linux 4.4.0-10-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  aljosa 1776 F pulseaudio
  CurrentDesktop: Unity
  Date: Sun Mar  6 11:02:21 2016
  HibernationDevice: RESUME=UUID=ac022671-63df-40ae-bffe-66fff3b35125
  InstallationDate: Installed on 2016-03-05 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160304)
  MachineType: LENOVO 80Q0
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-10-generic.efi.signed 
root=UUID=aa4325c4-4b4c-4372-b8ca-a66c3e5b2aa6 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-10-generic N/A
   linux-backports-modules-4.4.0-10-generic  N/A
   linux-firmware1.156
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/31/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: CDCN30WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: Allsparks 7A
  dmi.board.vendor: LENOVO
  dmi.board.version: NO DPK
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad Y700-17ISK
  dmi.modalias: 
dmi:bvnLENOVO:bvrCDCN30WW:bd01/31/2016:svnLENOVO:pn80Q0:pvrLenovoideapadY700-17ISK:rvnLENOVO:rnAllsparks7A:rvrNODPK:cvnLENOVO:ct10:cvrLenovoideapadY700-17ISK:
  dmi.product.name: 80Q0
  dmi.product.version: Lenovo ideapad Y700-17ISK
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1553685/+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 1327412] Re: Delay during PXE Boot, IP-Config gives up

[patpat]

This is an old bug never fixed by Ubuntu, never fixed by Debian either...
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=756633

You have to recompile ipconfig with the patch I wrote above and everything 
works OK.
Hopefully some day Ubuntu and/or Debian will fix this  ;-)

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

Title:
  Delay during PXE Boot, IP-Config gives up

Status in klibc package in Ubuntu:
  Confirmed
Status in klibc package in Debian:
  New

Bug description:
  Attempting to PXE boot both the 12.04.3 and 14.04 Live images.   PXE
  boot works normally (PXE Menu, select desired image, image begins
  loading), then the boot process hangs while IP-Config attempts to get
  an IP address:

  IP-Config: eth0 hardware address e0:db:55:0c:34:7e mtu 1500 DHCP
  IP-Config: eth1 hardware address e0:db:55:0c:34:80 mtu 1500 DHCP
  IP-Config: no response after 2 secs - giving up
  IP-Config: eth0 hardware address e0:db:55:0c:34:7e mtu 1500 DHCP
  IP-Config: eth1 hardware address e0:db:55:0c:34:80 mtu 1500 DHCP
  IP-Config: no response after 3 secs - giving up

  These lines appear very quickly (5 seconds has NOT elapsed), after
  about a minute, we get this:

  IP-Config: eth0 hardware address e0:db:55:0c:34:7e mtu 1500 DHCP
  IP-Config: eth1 hardware address e0:db:55:0c:34:80 mtu 1500 DHCP
  IP-Config: no response after 4 secs - giving up

  Some time later, this:

  IP-Config: eth0 hardware address e0:db:55:0c:34:7e mtu 1500 DHCP
  IP-Config: eth1 hardware address e0:db:55:0c:34:80 mtu 1500 DHCP
  IP-Config: no response after 6 secs - giving up

  Until finally, this:

  IP-Config: eth0 hardware address e0:db:55:0c:34:7e mtu 1500 DHCP
  IP-Config: eth1 hardware address e0:db:55:0c:34:80 mtu 1500 DHCP
  IP-Config: no response after 9 secs - giving up
  IP-Config: eth0 hardware address e0:db:55:0c:34:7e mtu 1500 DHCP
  IP-Config: eth1 hardware address e0:db:55:0c:34:80 mtu 1500 DHCP
  IP-Config: eth0 guessed broadcast address 172.25.11.31
  IP-Config: eth0 complete (dhcp from 172.25.10.20):
  (snip)

  While watching the DHCP server logs, Ubuntu is either not sending a
  DHCP Discover at times, or is not replying back with a DHCPRequest
  during these sessions, presumably ignoring an response from the DHCP
  server.  From the initial booting of the system via PXE, to when
  Ubuntu finally shows the desktop, almost 12 minutes will have elapsed.

  I am seeing this same behavior on both 12.04.3 and 14.04.  After
  finding a number of similar erros via Google and no real resolution, I
  have opened this bug.

  The system experiencing this issue has multiple ethernet interfaces
  (actual HW, not a VM), some Google found solutions suggest hard coding
  DEVICE=eth0 in /etc/initramfs-tools/initramfs.conf, however this isn't
  acceptable as a system attempting to PXE boot may be using an
  alternate port for the network.

  I have found what looks to be a very similar bug filed for Debian,
  #584583, which also contains a patch for this issue (under Debian).

  I have no problems in PXE booting to various Windows, RedHat, Centos,
  or Fedora OSs.  Ubuntu is the only Live OS that I'm attempting to boot
  at present.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: ubuntu-release-upgrader-core 1:0.220.2
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  CasperVersion: 1.340
  CrashDB: ubuntu
  CurrentDesktop: Unity
  Date: Fri Jun  6 20:22:09 2014
  LiveMediaBuild: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-release-upgrader
  Symptom: release-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/klibc/+bug/1327412/+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 1327412] Re: Delay during PXE Boot, IP-Config gives up

[Guga]

I'm hitting the same bug. It's a show-stopper when it comes down to
using PXE for network booting. I'm using Wily Werewolf and trying to
boot off PXE, but no dice. The DHCP server receives the request, OFFERs
an IP address and ipconfig (from klibc-utils) simply doesn't acknowledge
it.

I first ran across the bug while using Clonezilla (which runs off a live
Ubuntu 15.10 distro) booting off PXE. It turned the deployment into Hell
on Earth.

I've opened the initrd cpio+xv image, snatched the binaries and also
provided a bit more info about the system in which I performed the
tests. Let me know if you need further info.

Right now, this is a show-stopper for PXE deployments. Please assist us
with this issue.

Thanks!

** Attachment added: "Binaries and more info"
   
https://bugs.launchpad.net/ubuntu/+source/klibc/+bug/1327412/+attachment/4597191/+files/debug-klibc-ipconfig.tar.gz

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

Title:
  Delay during PXE Boot, IP-Config gives up

Status in klibc package in Ubuntu:
  Confirmed
Status in klibc package in Debian:
  New

Bug description:
  Attempting to PXE boot both the 12.04.3 and 14.04 Live images.   PXE
  boot works normally (PXE Menu, select desired image, image begins
  loading), then the boot process hangs while IP-Config attempts to get
  an IP address:

  IP-Config: eth0 hardware address e0:db:55:0c:34:7e mtu 1500 DHCP
  IP-Config: eth1 hardware address e0:db:55:0c:34:80 mtu 1500 DHCP
  IP-Config: no response after 2 secs - giving up
  IP-Config: eth0 hardware address e0:db:55:0c:34:7e mtu 1500 DHCP
  IP-Config: eth1 hardware address e0:db:55:0c:34:80 mtu 1500 DHCP
  IP-Config: no response after 3 secs - giving up

  These lines appear very quickly (5 seconds has NOT elapsed), after
  about a minute, we get this:

  IP-Config: eth0 hardware address e0:db:55:0c:34:7e mtu 1500 DHCP
  IP-Config: eth1 hardware address e0:db:55:0c:34:80 mtu 1500 DHCP
  IP-Config: no response after 4 secs - giving up

  Some time later, this:

  IP-Config: eth0 hardware address e0:db:55:0c:34:7e mtu 1500 DHCP
  IP-Config: eth1 hardware address e0:db:55:0c:34:80 mtu 1500 DHCP
  IP-Config: no response after 6 secs - giving up

  Until finally, this:

  IP-Config: eth0 hardware address e0:db:55:0c:34:7e mtu 1500 DHCP
  IP-Config: eth1 hardware address e0:db:55:0c:34:80 mtu 1500 DHCP
  IP-Config: no response after 9 secs - giving up
  IP-Config: eth0 hardware address e0:db:55:0c:34:7e mtu 1500 DHCP
  IP-Config: eth1 hardware address e0:db:55:0c:34:80 mtu 1500 DHCP
  IP-Config: eth0 guessed broadcast address 172.25.11.31
  IP-Config: eth0 complete (dhcp from 172.25.10.20):
  (snip)

  While watching the DHCP server logs, Ubuntu is either not sending a
  DHCP Discover at times, or is not replying back with a DHCPRequest
  during these sessions, presumably ignoring an response from the DHCP
  server.  From the initial booting of the system via PXE, to when
  Ubuntu finally shows the desktop, almost 12 minutes will have elapsed.

  I am seeing this same behavior on both 12.04.3 and 14.04.  After
  finding a number of similar erros via Google and no real resolution, I
  have opened this bug.

  The system experiencing this issue has multiple ethernet interfaces
  (actual HW, not a VM), some Google found solutions suggest hard coding
  DEVICE=eth0 in /etc/initramfs-tools/initramfs.conf, however this isn't
  acceptable as a system attempting to PXE boot may be using an
  alternate port for the network.

  I have found what looks to be a very similar bug filed for Debian,
  #584583, which also contains a patch for this issue (under Debian).

  I have no problems in PXE booting to various Windows, RedHat, Centos,
  or Fedora OSs.  Ubuntu is the only Live OS that I'm attempting to boot
  at present.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: ubuntu-release-upgrader-core 1:0.220.2
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  CasperVersion: 1.340
  CrashDB: ubuntu
  CurrentDesktop: Unity
  Date: Fri Jun  6 20:22:09 2014
  LiveMediaBuild: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-release-upgrader
  Symptom: release-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/klibc/+bug/1327412/+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 1556457] Re: [Resolved Upstream] Demilight (OS/2 weight=350) confuses fontconfig

[Mingye Wang]

** Also affects: fontconfig (Arch Linux)
   Importance: Undecided
   Status: New

** Description changed:

  See https://bugs.freedesktop.org/show_bug.cgi?id=81453 and bug 1468027.
  
  Fontconfig lacks support for many OpenType/TrueType OS/2 font weight
  values. This causes a bunch of problems, like mixing up Demilight
  (weight=350) and Regular (weight=400).
  
  Although it's possible to write (dirty?) hacks for deb-packed fonts,
  this still causes problems for otherwise sourced fonts.
+ 
+ Archlinux: https://bugs.archlinux.org/task/48550

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

Title:
  [Resolved Upstream] Demilight (OS/2 weight=350) confuses fontconfig

Status in Fontconfig:
  Unknown
Status in fontconfig package in Ubuntu:
  New
Status in fontconfig package in Arch Linux:
  New

Bug description:
  See https://bugs.freedesktop.org/show_bug.cgi?id=81453 and bug
  1468027.

  Fontconfig lacks support for many OpenType/TrueType OS/2 font weight
  values. This causes a bunch of problems, like mixing up Demilight
  (weight=350) and Regular (weight=400).

  Although it's possible to write (dirty?) hacks for deb-packed fonts,
  this still causes problems for otherwise sourced fonts.

  Archlinux: https://bugs.archlinux.org/task/48550

To manage notifications about this bug go to:
https://bugs.launchpad.net/fontconfig/+bug/1556457/+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 1556478] Re: unity-system-compositor crashed with SIGSEGV in __gxx_personality_v0()

[Apport retracing service]

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

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 #1553549, 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.

** Attachment removed: "CoreDump.gz"
   
https://bugs.launchpad.net/bugs/1556478/+attachment/4597163/+files/CoreDump.gz

** Attachment removed: "Disassembly.txt"
   
https://bugs.launchpad.net/bugs/1556478/+attachment/4597165/+files/Disassembly.txt

** Attachment removed: "ProcMaps.txt"
   
https://bugs.launchpad.net/bugs/1556478/+attachment/4597169/+files/ProcMaps.txt

** Attachment removed: "ProcStatus.txt"
   
https://bugs.launchpad.net/bugs/1556478/+attachment/4597170/+files/ProcStatus.txt

** Attachment removed: "Registers.txt"
   
https://bugs.launchpad.net/bugs/1556478/+attachment/4597171/+files/Registers.txt

** Attachment removed: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/1556478/+attachment/4597173/+files/Stacktrace.txt

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1556478/+attachment/4597174/+files/ThreadStacktrace.txt

** This bug has been marked a duplicate of private bug 1553549

** 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 unity-system-compositor in
Ubuntu.
https://bugs.launchpad.net/bugs/1556478

Title:
  unity-system-compositor crashed with SIGSEGV in __gxx_personality_v0()

Status in unity-system-compositor package in Ubuntu:
  New

Bug description:
  i log into ubuntu 16.04 only with gnome compiz - all other flavors just loop 
the login screen - mir, unity, gnome other variations, etc... they all go back 
to the login page after i enter my userid password...
  many thanks

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: unity-system-compositor 0.4.2+16.04.20160219.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-11.26-generic 4.4.4
  Uname: Linux 4.4.0-11-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CrashCounter: 1
  Date: Sun Mar 13 03:03:08 2016
  ExecutablePath: /usr/sbin/unity-system-compositor
  GraphicsCard:
   Intel Corporation Crystal Well Integrated Graphics Controller [8086:0d26] 
(rev 08) (prog-if 00 [VGA controller])
 Subsystem: Dell Crystal Well Integrated Graphics Controller [1028:0688]
 Subsystem: Dell GM204M [GeForce GTX 980M] [1028:0688]
  InstallationDate: Installed on 2015-09-16 (178 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  ProcCmdline: /usr/sbin/unity-system-compositor 
--disable-inactivity-policy=true --on-fatal-error-abort --file 
/run/lightdm-mir-0 --from-dm-fd 12 --to-dm-fd 21 --vt 8
  ProcEnviron:
   
  Signal: 11
  SourcePackage: unity-system-compositor
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
   __gxx_personality_v0 () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
   _Unwind_RaiseException (exc=0x10a6230) at ../../../src/libgcc/unwind.inc:113
   _Unwind_Resume_or_Rethrow (exc=0x10a6230) at 
../../../src/libgcc/unwind.inc:252
   __cxa_rethrow () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
  Title: unity-system-compositor crashed with SIGSEGV in __gxx_personality_v0()
  UpgradeStatus: Upgraded to xenial on 2016-03-07 (5 days ago)
  UserGroups:
   
  version.libdrm: libdrm2 2.4.67-1
  version.lightdm: lightdm 1.17.5-0ubuntu2
  version.mesa: libegl1-mesa-dev N/A

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-system-compositor/+bug/1556478/+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 1228567] Re: at-spi2 daemon error messages in .xsession-errors

[smile1324]

Not sure that this is fixed. I had the very same problem today and I am
using ubuntu 15.10 desktop.

After my wife tried to login an xOrg error was reported. After that my
unity desktop refused to load showing only the background image. I have
finally got it back running by renaming my ~/.config/dconf/user and
subsequently loose my desktop settings.

I think this is a very serious issue especially for I was not doing any
updates or driver changes before this error occured, it simply happend
out of the blue which is quite frightening.

Hopefully someone will find time to look into this.

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

Title:
  at-spi2 daemon error messages in .xsession-errors

Status in at-spi2-core package in Ubuntu:
  Fix Released

Bug description:
  Sometimes I get the following messages in .xsession-errors

  init: at-spi2-registryd main process ended, respawning
  init: at-spi2-registryd main process ended, respawning
  init: at-spi2-registryd main process ended, respawning
  init: at-spi2-registryd main process ended, respawning
  init: at-spi2-registryd main process ended, respawning
  init: at-spi2-registryd main process ended, respawning
  init: at-spi2-registryd main process ended, respawning
  init: at-spi2-registryd main process ended, respawning
  init: at-spi2-registryd main process ended, respawning
  init: at-spi2-registryd main process ended, respawning
  init: at-spi2-registryd respawning too fast, stopped

  I use a Lenovo Thinkpad Twist convertible with touch screen, using
  Onboard in tablet mode.

  Can perhaps have a relation with bug 1227173.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/at-spi2-core/+bug/1228567/+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 1545784] Re: Unity8 crashes with Intel Sandybridge on 16.04

[if.gnu.linux]

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

** This bug has been marked a duplicate of private bug 1556461

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

Title:
  Unity8 crashes with Intel Sandybridge on 16.04

Status in unity8 package in Ubuntu:
  Incomplete

Bug description:
  I can not log in to Unity8 session on Ubuntu 16.04. When I try to log
  in to Unity8 session, only a black screen is shown. And when I return
  to Unity7 session, I get a crash report from apport.

  To get to the default (unity7) session:
  1- CTRL+ALT+F1
  2- Log in
  3- sudo systemctrl restart lightdm
  ---
  ApportVersion: 2.20-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2016-01-16 (29 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160116)
  Package: unity8 8.11+16.04.20160208-0ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.4.0-4.19-generic 4.4.1
  Tags:  xenial
  Uname: Linux 4.4.0-4-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  --- 
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2016-01-16 (56 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160116)
  Package: unity8 8.11+16.04.20160310.4-0ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.4.0-12.28-generic 4.4.4
  Tags:  xenial
  Uname: Linux 4.4.0-12-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1545784/+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 1556433] Re: Booting is taking too long to start from grub

[Pavlushka]

** Attachment added: "sudo journalctl -b report"
   
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1556433/+attachment/4597130/+files/journal.txt

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

Title:
  Booting is taking too long to start from grub

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  Booting takes to start almost three minutes  after selecting Xubuntu
  Xenial. But it does not happen for the Ubuntu 14.04 LTS listed in the
  same menu. Xubuntu is installed in a USB 3 external Harddisk and
  Ubuntu is installed in internal Harddisk, but it was not happening for
  other installations. Like to add, after the boot started, it loaded
  much quicker than Ubuntu, there is a chance that the logs were stuck
  and appeared all at a time.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1556433/+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 1556464] Re: unity8-dash crashed with SIGABRT in QMessageLogger::fatal()

[Apport retracing service]

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

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 #1539614, 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.

** Attachment removed: "CoreDump.gz"
   
https://bugs.launchpad.net/bugs/1556464/+attachment/4597094/+files/CoreDump.gz

** Attachment removed: "Disassembly.txt"
   
https://bugs.launchpad.net/bugs/1556464/+attachment/4597096/+files/Disassembly.txt

** Attachment removed: "ProcMaps.txt"
   
https://bugs.launchpad.net/bugs/1556464/+attachment/4597099/+files/ProcMaps.txt

** Attachment removed: "ProcStatus.txt"
   
https://bugs.launchpad.net/bugs/1556464/+attachment/4597100/+files/ProcStatus.txt

** Attachment removed: "Registers.txt"
   
https://bugs.launchpad.net/bugs/1556464/+attachment/4597101/+files/Registers.txt

** Attachment removed: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/1556464/+attachment/4597102/+files/Stacktrace.txt

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1556464/+attachment/4597103/+files/ThreadStacktrace.txt

** This bug has been marked a duplicate of bug 1539614
   unity8-dash crashed with SIGABRT in QMessageLogger::fatal()

** 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 unity8 in Ubuntu.
https://bugs.launchpad.net/bugs/1556464

Title:
  unity8-dash crashed with SIGABRT in QMessageLogger::fatal()

Status in unity8 package in Ubuntu:
  New

Bug description:
  I can not log in to Unity8 session on Ubuntu 16.04. When I try to log
  in to Unity8 session, only a black screen is shown. And when I return
  to Unity7 session, I get a crash report from apport.

  To get to the default (unity7) session:
  1- CTRL+ALT+F1
  2- Log in
  3- sudo systemctrl restart lightdm

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: unity8 8.11+16.04.20160310.4-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-12.28-generic 4.4.4
  Uname: Linux 4.4.0-12-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  Date: Sat Mar 12 19:17:22 2016
  ExecutablePath: /usr/bin/unity8-dash
  InstallationDate: Installed on 2016-01-16 (56 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160116)
  ProcCmdline: unity8-dash 
--desktop_file_hint=/usr/share/applications/unity8-dash.desktop
  Signal: 6
  SourcePackage: unity8
  StacktraceTop:
   QMessageLogger::fatal(char const*, ...) const () from 
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
   ?? () from 
/usr/lib/x86_64-linux-gnu/qt5/plugins/platforms/libqpa-ubuntumirclient.so
   ?? () from 
/usr/lib/x86_64-linux-gnu/qt5/plugins/platforms/libqpa-ubuntumirclient.so
   QPlatformIntegrationFactory::create(QString const&, QStringList const&, 
int&, char**, QString const&) () from /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5
   QGuiApplicationPrivate::createPlatformIntegration() () from 
/usr/lib/x86_64-linux-gnu/libQt5Gui.so.5
  Title: unity8-dash crashed with SIGABRT in QMessageLogger::fatal()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1556464/+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 1468027] Re: change default CJK fonts to Noto CJK

[Mingye Wang]

** No longer affects: fontconfig (Ubuntu)

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

Title:
  change default CJK fonts to Noto CJK

Status in Fontconfig:
  Confirmed
Status in fonts-noto-cjk package in Ubuntu:
  In Progress
Status in language-selector package in Ubuntu:
  Fix Released
Status in ubuntu-meta package in Ubuntu:
  In Progress

Bug description:
  just realize that fonts-noto-cjk is available in the repository, finally its 
packaged.
  i don't really know about korean community.
  But for Chinese and Japanese community, i think that the answer is clear.
  noto-cjk is definitely better what we had before, like fonts- wqy and 
fonts-droid.
  Android community had received these complains for years, finally they got 
them fixed on lollipop.
  Fedora also set it as default chinese font start from F21.
  and of course, i still hope that ubuntu could drop those 69-language-selector 
fontconfig files, just like what F13 did.

To manage notifications about this bug go to:
https://bugs.launchpad.net/fontconfig/+bug/1468027/+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 1556459] Re: Regression: cannot set up 3 display configuration any more (Optimus)

[Paul Ortyl]

Seems to be similar to 
https://bugs.launchpad.net/ubuntu/+source/unity-control-center/+bug/1304627
but this one is regression, it worked already.

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

Title:
  Regression: cannot set up 3 display configuration any more (Optimus)

Status in xorg package in Ubuntu:
  New

Bug description:
  I cannot set up the third monitor any more (it was working beginning
  of March 2016 with Ubuntu 16.04).

  The configuration with NVIDIA Optimus starts with builtin display (of
  Thinkpad W530) and one of (3K) monitors, the second monitor is
  detected, but not used.

  The unity configuration tool shows me two message boxes:

  "The selected configuration for displays could not be applied
  could not set the configuration for CRTC 64"

  and

  "Failed to apply configuration: %s

  
GDBus.Error:org.gtk.GDBus.UnmappedGError.Quark._gsd_2drr_2derror_2dquark.Code2: 
could not set the configuration for CRTC 64
  "

  The first one I have seen at boot time on login screen (with 3
  displays) previously, the second one is new.

  The third monitor works if Optimus gets disabled in  BIOS and the
  machine runs with Nvidia only

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-12.28-generic 4.4.4
  Uname: Linux 4.4.0-12-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Sat Mar 12 18:44:54 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.0.16, 4.4.0-10-generic, x86_64: installed
   virtualbox, 5.0.16, 4.4.0-11-generic, x86_64: installed
   virtualbox, 5.0.16, 4.4.0-12-generic, x86_64: installed
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes, including running git bisection searches
  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 GK107GLM [Quadro K2000M] [10de:0ffb] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Lenovo GK107GLM [Quadro K2000M] [17aa:21f5]
  InstallationDate: Installed on 2016-02-25 (15 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160225)
  MachineType: LENOVO 2447MU0
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-12-generic 
root=UUID=c01ceec8-4b0c-447f-af8f-3e9c4ae90e15 ro rootflags=subvol=@ quiet 
splash
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/18/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G5ETA3WW (2.63 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2447MU0
  dmi.board.vendor: LENOVO
  dmi.board.version: 0B98401 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG5ETA3WW(2.63):bd09/18/2015:svnLENOVO:pn2447MU0:pvrThinkPadW530:rvnLENOVO:rn2447MU0:rvr0B98401WIN:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 2447MU0
  dmi.product.version: ThinkPad W530
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.12.2+16.04.20160209-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.1.2-1ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.1.2-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.1-1ubuntu4
  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.6.1-1ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160218-1ubuntu3
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Sat Mar 12 18:30:45 2016
  xserver.configfile: default
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.1-1ubuntu4

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1556459/+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 1556457] [NEW] [Resolved Upstream] Demilight (OS/2 weight=350) confuses fontconfig

[Mingye Wang]

Public bug reported:

See https://bugs.freedesktop.org/show_bug.cgi?id=81453 and bug 1468027.

Fontconfig lacks support for many OpenType/TrueType OS/2 font weight
values. This causes a bunch of problems, like mixing up Demilight
(weight=350) and Regular (weight=400).

Although it's possible to write (dirty?) hacks for deb-packed fonts,
this still causes problems for otherwise sourced fonts.

** Affects: fontconfig
 Importance: Unknown
 Status: Unknown

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


** Tags: patch patch-accepted-upstream

** Patch added: "Rebased upstream patch. Git am should know what to do."
   
https://bugs.launchpad.net/bugs/1556457/+attachment/4597026/+files/All_the_patches_cated_together.patch

** Bug watch added: freedesktop.org Bugzilla #81453
   https://bugs.freedesktop.org/show_bug.cgi?id=81453

** Also affects: fontconfig via
   https://bugs.freedesktop.org/show_bug.cgi?id=81453
   Importance: Unknown
   Status: Unknown

** Description changed:

  See https://bugs.freedesktop.org/show_bug.cgi?id=81453 and bug 1468027.
  
  Fontconfig lacks support for many OpenType/TrueType OS/2 font weight
  values. This causes a bunch of problems, like mixing up Demilight
  (weight=350) and Regular (weight=400).
+ 
+ Although it's possible to write (dirty?) hacks for deb-packed fonts,
+ this still causes problems for otherwise sourced packages.

** Description changed:

  See https://bugs.freedesktop.org/show_bug.cgi?id=81453 and bug 1468027.
  
  Fontconfig lacks support for many OpenType/TrueType OS/2 font weight
  values. This causes a bunch of problems, like mixing up Demilight
  (weight=350) and Regular (weight=400).
  
  Although it's possible to write (dirty?) hacks for deb-packed fonts,
- this still causes problems for otherwise sourced packages.
+ this still causes problems for otherwise sourced fonts.

** Summary changed:

- [Upstream] Demilight (OS/2 weight=350) confuses fontconfig 
+ [Resolved Upstream] Demilight (OS/2 weight=350) confuses fontconfig

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

Title:
  [Resolved Upstream] Demilight (OS/2 weight=350) confuses fontconfig

Status in Fontconfig:
  Unknown
Status in fontconfig package in Ubuntu:
  New

Bug description:
  See https://bugs.freedesktop.org/show_bug.cgi?id=81453 and bug
  1468027.

  Fontconfig lacks support for many OpenType/TrueType OS/2 font weight
  values. This causes a bunch of problems, like mixing up Demilight
  (weight=350) and Regular (weight=400).

  Although it's possible to write (dirty?) hacks for deb-packed fonts,
  this still causes problems for otherwise sourced fonts.

To manage notifications about this bug go to:
https://bugs.launchpad.net/fontconfig/+bug/1556457/+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 1184810] Re: [i18n] Plural form does not work as documented

[Rodney Dawes]

I think the documentation might need to be fixed, but the implementation
seems fine to me. For the general case, it's not possible to
automatically insert the "count", as the string may have multiple format
specifiers where the numeric value is not the first argument. For
instance, the following example would break, if the substitution was
done automatically:

tr("Folder %1 has %2 file", "Folder %1 has %2 files", count)

In this case, %1 is the name of the folder, while %2 is the count. If
the implementation were to return the result of the gettext call, as a
QString with .arg(count) applied to it first, the result would be
incorrect.

Maybe it should be made more explicit in the documentation that the API
follows the standard QString API expectations here, and does not
automatically insert count or contextual values in the string result of
tr() calls, but I don't think the implementation should be changed.

** Summary changed:

- [i18n] Plural form does not work as documented
+ [i18n] Confused about using plural forms

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

Title:
  [i18n] Confused about using plural forms

Status in ubuntu-ui-toolkit package in Ubuntu:
  Confirmed

Bug description:
  In the i18n component documentation the plural form should be used as:

   * Translate the given input string \a singular or \a plural (depending on 
the number of items \a n)
   * using gettext. Should be called like this:
   *  tr("%n file", "%n files", count)

  But this does not work as expected:

  The result string from this expression is:  ("%n file" or "%n files"
  with the "%n" instead the value)

  checking at the unit2d code I saw that the tr function automatically
  replaces the %n with the count value, but I am not sure if this is the
  correct solution.

  For now I am using  "tr("%1 file", "%1 files", count).arg(count)"

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1184810/+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 1184810] Re: [i18n] Confused about using plural forms

[Rodney Dawes]

I changed the title of this bug, because the implementation and
documentation are aligned. There is nothing in the documentation
implying that the "count" argument for plural forms will be
automatically replaced in a format string. It is up to the programmer to
finalize formatting of their strings properly.

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

Title:
  [i18n] Confused about using plural forms

Status in ubuntu-ui-toolkit package in Ubuntu:
  Confirmed

Bug description:
  In the i18n component documentation the plural form should be used as:

   * Translate the given input string \a singular or \a plural (depending on 
the number of items \a n)
   * using gettext. Should be called like this:
   *  tr("%n file", "%n files", count)

  But this does not work as expected:

  The result string from this expression is:  ("%n file" or "%n files"
  with the "%n" instead the value)

  checking at the unit2d code I saw that the tr function automatically
  replaces the %n with the count value, but I am not sure if this is the
  correct solution.

  For now I am using  "tr("%1 file", "%1 files", count).arg(count)"

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1184810/+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 1545784] upstart.unity8.log.txt

[if.gnu.linux]

apport information

** Attachment added: "upstart.unity8.log.txt"
   
https://bugs.launchpad.net/bugs/1545784/+attachment/4597057/+files/upstart.unity8.log.txt

** Tags removed: apport-collected
** Tags added: intel unity8

** Tags added: sandybridge

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

Title:
  Unity8 crashes with Intel Sandybridge on 16.04

Status in unity8 package in Ubuntu:
  Incomplete

Bug description:
  I can not log in to Unity8 session on Ubuntu 16.04. When I try to log
  in to Unity8 session, only a black screen is shown. And when I return
  to Unity7 session, I get a crash report from apport.

  To get to the default (unity7) session:
  1- CTRL+ALT+F1
  2- Log in
  3- sudo systemctrl restart lightdm
  ---
  ApportVersion: 2.20-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2016-01-16 (29 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160116)
  Package: unity8 8.11+16.04.20160208-0ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.4.0-4.19-generic 4.4.1
  Tags:  xenial
  Uname: Linux 4.4.0-4-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  --- 
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2016-01-16 (56 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160116)
  Package: unity8 8.11+16.04.20160310.4-0ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.4.0-12.28-generic 4.4.4
  Tags:  xenial
  Uname: Linux 4.4.0-12-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1545784/+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 1545784] upstart.unity8-dash.log.txt

[if.gnu.linux]

apport information

** Attachment added: "upstart.unity8-dash.log.txt"
   
https://bugs.launchpad.net/bugs/1545784/+attachment/4597056/+files/upstart.unity8-dash.log.txt

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

Title:
  Unity8 crashes with Intel Sandybridge on 16.04

Status in unity8 package in Ubuntu:
  Incomplete

Bug description:
  I can not log in to Unity8 session on Ubuntu 16.04. When I try to log
  in to Unity8 session, only a black screen is shown. And when I return
  to Unity7 session, I get a crash report from apport.

  To get to the default (unity7) session:
  1- CTRL+ALT+F1
  2- Log in
  3- sudo systemctrl restart lightdm
  ---
  ApportVersion: 2.20-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2016-01-16 (29 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160116)
  Package: unity8 8.11+16.04.20160208-0ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.4.0-4.19-generic 4.4.1
  Tags:  xenial
  Uname: Linux 4.4.0-4-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  --- 
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2016-01-16 (56 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160116)
  Package: unity8 8.11+16.04.20160310.4-0ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.4.0-12.28-generic 4.4.4
  Tags:  xenial
  Uname: Linux 4.4.0-12-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1545784/+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 1545784] ProcEnviron.txt

[if.gnu.linux]

apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1545784/+attachment/4597055/+files/ProcEnviron.txt

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

Title:
  Unity8 crashes with Intel Sandybridge on 16.04

Status in unity8 package in Ubuntu:
  Incomplete

Bug description:
  I can not log in to Unity8 session on Ubuntu 16.04. When I try to log
  in to Unity8 session, only a black screen is shown. And when I return
  to Unity7 session, I get a crash report from apport.

  To get to the default (unity7) session:
  1- CTRL+ALT+F1
  2- Log in
  3- sudo systemctrl restart lightdm
  ---
  ApportVersion: 2.20-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2016-01-16 (29 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160116)
  Package: unity8 8.11+16.04.20160208-0ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.4.0-4.19-generic 4.4.1
  Tags:  xenial
  Uname: Linux 4.4.0-4-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  --- 
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2016-01-16 (56 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160116)
  Package: unity8 8.11+16.04.20160310.4-0ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.4.0-12.28-generic 4.4.4
  Tags:  xenial
  Uname: Linux 4.4.0-12-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1545784/+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 1545784] JournalErrors.txt

[if.gnu.linux]

apport information

** Attachment added: "JournalErrors.txt"
   
https://bugs.launchpad.net/bugs/1545784/+attachment/4597054/+files/JournalErrors.txt

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

Title:
  Unity8 crashes with Intel Sandybridge on 16.04

Status in unity8 package in Ubuntu:
  Incomplete

Bug description:
  I can not log in to Unity8 session on Ubuntu 16.04. When I try to log
  in to Unity8 session, only a black screen is shown. And when I return
  to Unity7 session, I get a crash report from apport.

  To get to the default (unity7) session:
  1- CTRL+ALT+F1
  2- Log in
  3- sudo systemctrl restart lightdm
  ---
  ApportVersion: 2.20-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2016-01-16 (29 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160116)
  Package: unity8 8.11+16.04.20160208-0ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.4.0-4.19-generic 4.4.1
  Tags:  xenial
  Uname: Linux 4.4.0-4-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  --- 
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2016-01-16 (56 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160116)
  Package: unity8 8.11+16.04.20160310.4-0ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.4.0-12.28-generic 4.4.4
  Tags:  xenial
  Uname: Linux 4.4.0-12-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1545784/+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 1545784] Re: Unity8 crashes with Intel Sandybridge on 16.04

[if.gnu.linux]

apport information

** Description changed:

  I can not log in to Unity8 session on Ubuntu 16.04. When I try to log in
  to Unity8 session, only a black screen is shown. And when I return to
  Unity7 session, I get a crash report from apport.
  
  To get to the default (unity7) session:
  1- CTRL+ALT+F1
  2- Log in
  3- sudo systemctrl restart lightdm
  ---
  ApportVersion: 2.20-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2016-01-16 (29 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160116)
  Package: unity8 8.11+16.04.20160208-0ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.4.0-4.19-generic 4.4.1
  Tags:  xenial
  Uname: Linux 4.4.0-4-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
+ --- 
+ ApportVersion: 2.20-0ubuntu3
+ Architecture: amd64
+ DistroRelease: Ubuntu 16.04
+ InstallationDate: Installed on 2016-01-16 (56 days ago)
+ InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160116)
+ Package: unity8 8.11+16.04.20160310.4-0ubuntu1
+ PackageArchitecture: amd64
+ ProcVersionSignature: Ubuntu 4.4.0-12.28-generic 4.4.4
+ Tags:  xenial
+ Uname: Linux 4.4.0-12-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups:
+  
+ _MarkForUpload: True

** Attachment added: "Dependencies.txt"
   
https://bugs.launchpad.net/bugs/1545784/+attachment/4597053/+files/Dependencies.txt

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

Title:
  Unity8 crashes with Intel Sandybridge on 16.04

Status in unity8 package in Ubuntu:
  Incomplete

Bug description:
  I can not log in to Unity8 session on Ubuntu 16.04. When I try to log
  in to Unity8 session, only a black screen is shown. And when I return
  to Unity7 session, I get a crash report from apport.

  To get to the default (unity7) session:
  1- CTRL+ALT+F1
  2- Log in
  3- sudo systemctrl restart lightdm
  ---
  ApportVersion: 2.20-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2016-01-16 (29 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160116)
  Package: unity8 8.11+16.04.20160208-0ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.4.0-4.19-generic 4.4.1
  Tags:  xenial
  Uname: Linux 4.4.0-4-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  --- 
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2016-01-16 (56 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160116)
  Package: unity8 8.11+16.04.20160310.4-0ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.4.0-12.28-generic 4.4.4
  Tags:  xenial
  Uname: Linux 4.4.0-12-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1545784/+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 1556459] [NEW] Regression: cannot set up 3 display configuration any more (Optimus)

[Paul Ortyl]

Public bug reported:

I cannot set up the third monitor any more (it was working beginning of
March 2016 with Ubuntu 16.04).

The configuration with NVIDIA Optimus starts with builtin display (of
Thinkpad W530) and one of (3K) monitors, the second monitor is detected,
but not used.

The unity configuration tool shows me two message boxes:

"The selected configuration for displays could not be applied
could not set the configuration for CRTC 64"

and

"Failed to apply configuration: %s

GDBus.Error:org.gtk.GDBus.UnmappedGError.Quark._gsd_2drr_2derror_2dquark.Code2: 
could not set the configuration for CRTC 64
"

The first one I have seen at boot time on login screen (with 3 displays)
previously, the second one is new.

The third monitor works if Optimus gets disabled in  BIOS and the
machine runs with Nvidia only

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-12.28-generic 4.4.4
Uname: Linux 4.4.0-12-generic x86_64
.tmp.unity.support.test.0:
 
ApportVersion: 2.20-0ubuntu3
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Sat Mar 12 18:44:54 2016
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
DkmsStatus:
 virtualbox, 5.0.16, 4.4.0-10-generic, x86_64: installed
 virtualbox, 5.0.16, 4.4.0-11-generic, x86_64: installed
 virtualbox, 5.0.16, 4.4.0-12-generic, x86_64: installed
EcryptfsInUse: Yes
ExtraDebuggingInterest: Yes, including running git bisection searches
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 GK107GLM [Quadro K2000M] [10de:0ffb] (rev a1) (prog-if 00 
[VGA controller])
   Subsystem: Lenovo GK107GLM [Quadro K2000M] [17aa:21f5]
InstallationDate: Installed on 2016-02-25 (15 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160225)
MachineType: LENOVO 2447MU0
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-12-generic 
root=UUID=c01ceec8-4b0c-447f-af8f-3e9c4ae90e15 ro rootflags=subvol=@ quiet 
splash
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/18/2015
dmi.bios.vendor: LENOVO
dmi.bios.version: G5ETA3WW (2.63 )
dmi.board.asset.tag: Not Available
dmi.board.name: 2447MU0
dmi.board.vendor: LENOVO
dmi.board.version: 0B98401 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: 
dmi:bvnLENOVO:bvrG5ETA3WW(2.63):bd09/18/2015:svnLENOVO:pn2447MU0:pvrThinkPadW530:rvnLENOVO:rn2447MU0:rvr0B98401WIN:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 2447MU0
dmi.product.version: ThinkPad W530
dmi.sys.vendor: LENOVO
version.compiz: compiz 1:0.9.12.2+16.04.20160209-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.67-1
version.libgl1-mesa-dri: libgl1-mesa-dri 11.1.2-1ubuntu1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 11.1.2-1ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.18.1-1ubuntu4
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.6.1-1ubuntu2
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160218-1ubuntu3
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2
xserver.bootTime: Sat Mar 12 18:30:45 2016
xserver.configfile: default
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.18.1-1ubuntu4

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


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

** Attachment added: "Failure at trying to reenable the third monitor"
   
https://bugs.launchpad.net/bugs/1556459/+attachment/4597027/+files/Screenshot%20from%202016-03-12%2018-33-34.png

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

Title:
  Regression: cannot set up 3 display configuration any more (Optimus)

Status in xorg package in Ubuntu:
  New

Bug description:
  I cannot set up the third monitor any more (it was working beginning
  of March 2016 with Ubuntu 16.04).

  The configuration with NVIDIA Optimus starts with builtin display (of
  Thinkpad W530) and one of (3K) monitors, the second monitor is
  detected, but not used.

  The unity configuration tool shows me two message boxes:

  "The selected configuration for displays could not be applied
  could not set the configuration for CRTC 64"

  and

  "Failed to apply configuration: %s

  

[Touch-packages] [Bug 1468027] Re: change default CJK fonts to Noto CJK

[Mingye Wang]

Let me file the fc demi report separately then. A fix is always better
than a hack, and with Noto Sans CJK hacked there are still a whole bunch
of Notos and other weight-rich fonts.

Just realized my PPA pkg is based on 2.11.1-0ubuntu6 instead of current
ubuntu8, hmm. Can't see xenial on bzr... Whatever.

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

Title:
  change default CJK fonts to Noto CJK

Status in Fontconfig:
  Confirmed
Status in fontconfig package in Ubuntu:
  New
Status in fonts-noto-cjk package in Ubuntu:
  In Progress
Status in language-selector package in Ubuntu:
  Fix Released
Status in ubuntu-meta package in Ubuntu:
  In Progress

Bug description:
  just realize that fonts-noto-cjk is available in the repository, finally its 
packaged.
  i don't really know about korean community.
  But for Chinese and Japanese community, i think that the answer is clear.
  noto-cjk is definitely better what we had before, like fonts- wqy and 
fonts-droid.
  Android community had received these complains for years, finally they got 
them fixed on lollipop.
  Fedora also set it as default chinese font start from F21.
  and of course, i still hope that ubuntu could drop those 69-language-selector 
fontconfig files, just like what F13 did.

To manage notifications about this bug go to:
https://bugs.launchpad.net/fontconfig/+bug/1468027/+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 1556452] [NEW] 4K@60Hz DisplayPort 1.2 loses output modes

[Rodney Dawes]

Public bug reported:

I have a Dell UP2414Q 24" 4K display panel. The only way to achieve 60Hz
refresh on it, is to use DisplayPort 1.2 MST.

Due to MST, this results in two screens with 1920x2160 resolution being
exposed to X. In order to get back to a proper rendering where it looks
like a single display, one must either use Xinerama (with NVidia) or
Xorg 3.18 and the new xrandr with support for configuring monitors in
RandR 1.5 (with Intel). In both of these configurations, if the monitor
itself is powered off, the output modes will disappear from xrandr, and
when the monitor is powered back on, it behaves as though no output is
being sent to it over the DisplayPort connection. When connecting with
ssh to debug, running DISPLAY=:0 xrandr says that the two outputs exist,
but no modes are configured, and indeed it does not list any. If
however, instead of powering the monitor off, it is left on while away,
this does not occur upon return, and the display works normally as when
it was left.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-12.28-generic 4.4.4
Uname: Linux 4.4.0-12-generic x86_64
.tmp.unity.support.test.0:
 
ApportVersion: 2.20-0ubuntu3
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: Sat Mar 12 12:26:16 2016
DistUpgraded: 2016-03-10 16:26:10,719 DEBUG failed to SystemUnLock() (E:Not 
locked)
DistroCodename: xenial
DistroVariant: ubuntu
DkmsStatus:
 virtualbox, 5.0.16, 4.4.0-11-generic, x86_64: installed
 virtualbox, 5.0.16, 4.4.0-11-lowlatency, x86_64: installed
 virtualbox, 5.0.16, 4.4.0-12-generic, x86_64: installed
 virtualbox, 5.0.16, 4.4.0-12-lowlatency, x86_64: installed
GraphicsCard:
 Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics 
Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller])
   Subsystem: Micro-Star International Co., Ltd. [MSI] Xeon E3-1200 v3/4th Gen 
Core Processor Integrated Graphics Controller [1462:7919]
InstallationDate: Installed on 2012-10-21 (1237 days ago)
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
MachineType: MSI MS-7919
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-12-generic 
root=UUID=167bf6e1-727f-4db1-b2f9-c496700b301b ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: Upgraded to xenial on 2016-03-10 (1 days ago)
dmi.bios.date: 04/30/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: V1.0
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: Z97M GAMING (MS-7919)
dmi.board.vendor: MSI
dmi.board.version: 1.0
dmi.chassis.asset.tag: To be filled by O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: MSI
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV1.0:bd04/30/2014:svnMSI:pnMS-7919:pvr1.0:rvnMSI:rnZ97MGAMING(MS-7919):rvr1.0:cvnMSI:ct3:cvr1.0:
dmi.product.name: MS-7919
dmi.product.version: 1.0
dmi.sys.vendor: MSI
version.compiz: compiz 1:0.9.12.2+16.04.20160209-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.67-1
version.libgl1-mesa-dri: libgl1-mesa-dri 11.1.2-1ubuntu1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 11.1.2-1ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.18.1-1ubuntu4
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.6.1-1ubuntu2
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160218-1ubuntu3
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2
xserver.bootTime: Sat Mar 12 11:07:14 2016
xserver.configfile: default
xserver.devices:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 
xserver.version: 2:1.18.1-1ubuntu4

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

Title:
  4K@60Hz DisplayPort 1.2 loses output modes

Status in xorg package in Ubuntu:
  New

Bug description:
  I have a Dell UP2414Q 24" 4K display panel. The only way to achieve
  60Hz refresh on it, is to use DisplayPort 1.2 MST.

  Due to MST, this results in two screens with 1920x2160 resolution
  being exposed to X. In order to get back to a proper rendering where
  it looks like a single display, one must either use Xinerama (with
  NVidia) or Xorg 3.18 and the new xrandr with support for configuring
  monitors in RandR 1.5 (with Intel). In both of these configurations,
  if the monitor itself is powered off, the output modes will disappear
  from xrandr, and when the monitor is powered back 

[Touch-packages] [Bug 1528655] Re: Wily/15.10 - systemd hangs reboot + shutdown for long periods of time

[Martin Pitt]

So apparently you already identified some processes that hang on
shutdown. /usr/share/doc/systemd/README.Debian.gz describes how to find
and debug those.

If you want to keep this open against systemd, please attach
/var/log/syslog right after a reboot, which should still contain most of
the shutdown log from the previous boot (if that isn't sufficient, we'll
need a complete journal for shutdown, after enabling persistent journal
-- but let's get to that when we need it).

** Changed in: systemd (Ubuntu)
   Status: Confirmed => 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/1528655

Title:
  Wily/15.10 - systemd hangs reboot + shutdown for long periods of time

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  Yet another horrible bug related to systemd which delays shutdowns by
  minutes.

  https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1374759
  surfaces this problem + the bug I'm reporting here is a separate
  issue.

  Neither reboot or shutdown -r now work sensibly any more. Both rely on
  systemd, which appears to be the root of most Ubuntu instabilities
  now, reading the many reported systemd bugs.

  Both the reboot + shutdown -r now commands should do what the mean.
  Shutdown + Reboot now...

  Not 150-250 seconds after requested, which appears to be some
  arbitrary systemd timeout.

  Please fix this problem + update this ticket with some workaround to
  get an instant reboot, till fix is available.

  Thanks.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1528655/+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 1556453] [NEW] PyGIWarnings on start

[Rodney Dawes]

Public bug reported:

When apport starts (by running ubuntu-bug, or in case of a crash) the
following messages are printed to its stderr:

sys:1: PyGIWarning: Wnck was imported without specifying a version first. Use 
gi.require_version('Wnck', '3.0') before import to ensure that the right 
version gets loaded.
sys:1: PyGIWarning: GdkX11 was imported without specifying a version first. Use 
gi.require_version('GdkX11', '3.0') before import to ensure that the right 
version gets loaded.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: apport 2.20-0ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-12.28-generic 4.4.4
Uname: Linux 4.4.0-12-generic x86_64
ApportVersion: 2.20-0ubuntu3
Architecture: amd64
CrashReports:
 600:105:110:0:2016-03-12 11:08:46.905936282 -0500:2016-03-12 
11:08:46.905936282 -0500:/var/crash/_usr_lib_xorg_Xorg.0.uploaded
 640:0:110:5480073:2016-03-12 11:08:41.793873548 -0500:2016-03-12 
11:08:42.793873548 -0500:/var/crash/_usr_lib_xorg_Xorg.0.crash
 640:1047:110:339644:2016-03-12 11:07:14.474959555 -0500:2016-03-12 
11:07:47.304641255 -0500:/var/crash/_usr_bin_synergys.1047.crash
 644:0:110:0:2016-03-12 11:08:44.785904154 -0500:2016-03-12 11:08:44.785904154 
-0500:/var/crash/_usr_lib_xorg_Xorg.0.upload
CurrentDesktop: Unity
Date: Sat Mar 12 12:41:15 2016
InstallationDate: Installed on 2012-10-21 (1237 days ago)
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
PackageArchitecture: all
SourcePackage: apport
UpgradeStatus: Upgraded to xenial on 2016-03-10 (1 days ago)

** Affects: apport (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 apport in Ubuntu.
https://bugs.launchpad.net/bugs/1556453

Title:
  PyGIWarnings on start

Status in apport package in Ubuntu:
  New

Bug description:
  When apport starts (by running ubuntu-bug, or in case of a crash) the
  following messages are printed to its stderr:

  sys:1: PyGIWarning: Wnck was imported without specifying a version first. Use 
gi.require_version('Wnck', '3.0') before import to ensure that the right 
version gets loaded.
  sys:1: PyGIWarning: GdkX11 was imported without specifying a version first. 
Use gi.require_version('GdkX11', '3.0') before import to ensure that the right 
version gets loaded.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: apport 2.20-0ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-12.28-generic 4.4.4
  Uname: Linux 4.4.0-12-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CrashReports:
   600:105:110:0:2016-03-12 11:08:46.905936282 -0500:2016-03-12 
11:08:46.905936282 -0500:/var/crash/_usr_lib_xorg_Xorg.0.uploaded
   640:0:110:5480073:2016-03-12 11:08:41.793873548 -0500:2016-03-12 
11:08:42.793873548 -0500:/var/crash/_usr_lib_xorg_Xorg.0.crash
   640:1047:110:339644:2016-03-12 11:07:14.474959555 -0500:2016-03-12 
11:07:47.304641255 -0500:/var/crash/_usr_bin_synergys.1047.crash
   644:0:110:0:2016-03-12 11:08:44.785904154 -0500:2016-03-12 
11:08:44.785904154 -0500:/var/crash/_usr_lib_xorg_Xorg.0.upload
  CurrentDesktop: Unity
  Date: Sat Mar 12 12:41:15 2016
  InstallationDate: Installed on 2012-10-21 (1237 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: Upgraded to xenial on 2016-03-10 (1 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1556453/+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 1556433] Re: Booting is taking too long to start from grub

[Martin Pitt]

Please do "sudo journalctl -b > /tmp/journal.txt" and attach journal.txt
here.

** Changed in: systemd (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/1556433

Title:
  Booting is taking too long to start from grub

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  Booting takes to start almost three minutes  after selecting Xubuntu
  Xenial. But it does not happen for the Ubuntu 14.04 LTS listed in the
  same menu. Xubuntu is installed in a USB 3 external Harddisk and
  Ubuntu is installed in internal Harddisk, but it was not happening for
  other installations. Like to add, after the boot started, it loaded
  much quicker than Ubuntu, there is a chance that the logs were stuck
  and appeared all at a time.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1556433/+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 1556447] Re: lxc-start fails: lxc_cgfsng - cgfsng.c:all_controllers_found:430 - no systemd controller mountpoint found

[Stephen Warren]

Switching the linode system to the Ubuntu kernel (booted via pv-grub)
didn't make that system fail. Perhaps the difference is cgroup setup via
ssh vs XFCE/GUI login?

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

Title:
  lxc-start fails: lxc_cgfsng - cgfsng.c:all_controllers_found:430 - no
  systemd controller mountpoint found

Status in lxc package in Ubuntu:
  New

Bug description:
  On Ubuntu Xenial pre-release, I see the following, so can't start a
  container:

  [swarren@sprint ~]$ lxc-create -t download -n t2 -- -d ubuntu -r trusty -a 
amd64
  Using image from local cache
  Unpacking the rootfs

  ---
  You just created an Ubuntu container (release=trusty, arch=amd64, 
variant=default)

  To enable sshd, run: apt-get install openssh-server

  For security reason, container images ship without user accounts
  and without a root password.

  Use lxc-attach or chroot directly into the rootfs to set a root password
  or create user accounts.

  
  swarren@sprint ~]$ lxc-start -n t2 -d
  lxc-start: lxc_start.c: main: 344 The container failed to start.
  lxc-start: lxc_start.c: main: 346 To get more details, run the container in 
foreground mode.
  lxc-start: lxc_start.c: main: 348 Additional information can be obtained by 
setting the --logfile and --logpriority options.

  
  [swarren@sprint ~]$ lxc-start -n t2 -d -o /dev/stdout -l debug -F
lxc-start 20160312101415.704 INFO lxc_start_ui - 
lxc_start.c:main:264 - using rcfile /home/swarren/.local/share/lxc/t2/config
lxc-start 20160312101415.705 WARN lxc_confile - 
confile.c:config_pivotdir:1859 - lxc.pivotdir is ignored.  It will soon become 
an error.
lxc-start 20160312101415.705 INFO lxc_confile - 
confile.c:config_idmap:1495 - read uid map: type u nsid 0 hostid 10 range 
65536
lxc-start 20160312101415.705 INFO lxc_confile - 
confile.c:config_idmap:1495 - read uid map: type g nsid 0 hostid 10 range 
65536
lxc-start 20160312101415.707 INFO lxc_lsm - lsm/lsm.c:lsm_init:48 - 
LSM security driver AppArmor
lxc-start 20160312101415.708 INFO lxc_seccomp - 
seccomp.c:parse_config_v2:342 - processing: .reject_force_umount  # comment 
this to allow umount -f;  not recommended.
lxc-start 20160312101415.708 INFO lxc_seccomp - 
seccomp.c:parse_config_v2:446 - Adding native rule for reject_force_umount 
action 0
lxc-start 20160312101415.708 INFO lxc_seccomp - 
seccomp.c:do_resolve_add_rule:216 - Setting seccomp rule to reject force umounts

lxc-start 20160312101415.708 INFO lxc_seccomp - 
seccomp.c:parse_config_v2:449 - Adding compat rule for reject_force_umount 
action 0
lxc-start 20160312101415.708 INFO lxc_seccomp - 
seccomp.c:do_resolve_add_rule:216 - Setting seccomp rule to reject force umounts

lxc-start 20160312101415.708 INFO lxc_seccomp - 
seccomp.c:parse_config_v2:342 - processing: .[all].
lxc-start 20160312101415.708 INFO lxc_seccomp - 
seccomp.c:parse_config_v2:342 - processing: .kexec_load errno 1.
lxc-start 20160312101415.708 INFO lxc_seccomp - 
seccomp.c:parse_config_v2:446 - Adding native rule for kexec_load action 327681
lxc-start 20160312101415.708 INFO lxc_seccomp - 
seccomp.c:parse_config_v2:449 - Adding compat rule for kexec_load action 327681
lxc-start 20160312101415.708 INFO lxc_seccomp - 
seccomp.c:parse_config_v2:342 - processing: .open_by_handle_at errno 1.
lxc-start 20160312101415.708 INFO lxc_seccomp - 
seccomp.c:parse_config_v2:446 - Adding native rule for open_by_handle_at action 
327681
lxc-start 20160312101415.708 INFO lxc_seccomp - 
seccomp.c:parse_config_v2:449 - Adding compat rule for open_by_handle_at action 
327681
lxc-start 20160312101415.708 INFO lxc_seccomp - 
seccomp.c:parse_config_v2:342 - processing: .init_module errno 1.
lxc-start 20160312101415.708 INFO lxc_seccomp - 
seccomp.c:parse_config_v2:446 - Adding native rule for init_module action 327681
lxc-start 20160312101415.708 INFO lxc_seccomp - 
seccomp.c:parse_config_v2:449 - Adding compat rule for init_module action 327681
lxc-start 20160312101415.708 INFO lxc_seccomp - 
seccomp.c:parse_config_v2:342 - processing: .finit_module errno 1.
lxc-start 20160312101415.708 INFO lxc_seccomp - 
seccomp.c:parse_config_v2:446 - Adding native rule for finit_module action 
327681
lxc-start 20160312101415.708 INFO lxc_seccomp - 
seccomp.c:parse_config_v2:449 - Adding compat rule for finit_module action 
327681
lxc-start 20160312101415.708 INFO lxc_seccomp - 
seccomp.c:parse_config_v2:342 - processing: .delete_module errno 1.
lxc-start 20160312101415.708 INFO lxc_seccomp - 
seccomp.c:parse_config_v2:446 - Adding native rule for delete_module action 

[Touch-packages] [Bug 1556451] [NEW] xenial lvm2-monitor.service fails with lvm raid1 volumes

[Tero Marttila]

Public bug reported:

After installing xenial using the daily ubuntu-server installer,
creating an LVM volume for the root filesystem, I lvconverted it into a
raid1 mirror for redundancy over the pair of SSDs installed (as separate
LVM PVs):

sudo lvconvert -m 1 --type raid1 bonk/bonk1 /dev/sdc1 /dev/sdd1

After a reboot, the lvm2-monitor.service fails. Relevant lines from
journalctl:

$ sudo journalctl | grep -iE '(lvm|dmeventd)'
Mar 12 19:32:48 bonk1 systemd[1]: Listening on LVM2 metadata daemon 
socket.
Mar 12 19:32:48 bonk1 systemd[1]: Listening on LVM2 poll daemon socket.
Mar 12 19:32:48 bonk1 systemd[1]: Starting Monitoring of LVM2 mirrors, 
snapshots etc. using dmeventd or progress polling...
Mar 12 19:32:49 bonk1 systemd[1]: Started LVM2 metadata daemon.
Mar 12 19:32:52 bonk1 dmeventd[1039]: dmeventd 
libdevmapper-event-lvm2raid.so dlopen failed: libdevmapper-event-lvm2raid.so: 
cannot open shared object file: No such file or directory.
Mar 12 19:32:52 bonk1 dmeventd[1039]: dmeventd 
libdevmapper-event-lvm2raid.so dlopen failed: libdevmapper-event-lvm2raid.so: 
cannot open shared object file: No such file or directory.
Mar 12 19:32:52 bonk1 dmeventd[1039]: dmeventd 
libdevmapper-event-lvm2raid.so dlopen failed: libdevmapper-event-lvm2raid.so: 
cannot open shared object file: No such file or directory.
Mar 12 19:32:59 bonk1 lvm[556]:   Monitoring bonk/bonk1 failed.
Mar 12 19:32:59 bonk1 lvm[556]:   4 logical volume(s) in volume group 
"bonk" monitored
Mar 12 19:32:59 bonk1 systemd[1]: lvm2-monitor.service: Main process 
exited, code=exited, status=5/NOTINSTALLED
Mar 12 19:32:59 bonk1 systemd[1]: Failed to start Monitoring of LVM2 
mirrors, snapshots etc. using dmeventd or progress polling.
Mar 12 19:32:59 bonk1 systemd[1]: lvm2-monitor.service: Unit entered 
failed state.
Mar 12 19:32:59 bonk1 systemd[1]: lvm2-monitor.service: Failed with 
result 'exit-code'.
Mar 12 19:33:00 bonk1 dmeventd[1039]: dmeventd 
libdevmapper-event-lvm2raid.so dlopen failed: libdevmapper-event-lvm2raid.so: 
cannot open shared object file: No 
such file or directory.
Mar 12 19:33:08 bonk1 systemd-udevd[662]: Process 'watershed sh -c 
'/sbin/lvm vgscan; /sbin/lvm vgchange -a y'' failed with exit code 5.
Mar 12 19:33:08 bonk1 dmeventd[1039]: dmeventd 
libdevmapper-event-lvm2raid.so dlopen failed: libdevmapper-event-lvm2raid.so: 
cannot open shared object file: No such file or directory.
Mar 12 19:33:16 bonk1 systemd-udevd[655]: Process 'watershed sh -c 
'/sbin/lvm vgscan; /sbin/lvm vgchange -a y'' failed with exit code 5.

The .so file is present and installed as part of dmeventd:

$ dpkg -S libdevmapper-event-lvm2raid.so
dmeventd: 
/lib/x86_64-linux-gnu/device-mapper/libdevmapper-event-lvm2raid.so

This may be related to Debian's lvm2 2.02.133-2 change:

* Drop event plugin directory move.  This moves the plugins back into
 the main library path. (closes: #807279)

See:

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

--- 
$ apt-cache policy lvm2 dmeventd 
lvm2:
  Installed: 2.02.133-1ubuntu7
  Candidate: 2.02.133-1ubuntu7
  Version table:
 *** 2.02.133-1ubuntu7 500
500 http://fi.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
100 /var/lib/dpkg/status
dmeventd:
  Installed: 2:1.02.110-1ubuntu7
  Candidate: 2:1.02.110-1ubuntu7
  Version table:
 *** 2:1.02.110-1ubuntu7 500
500 http://fi.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
100 /var/lib/dpkg/status

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

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

Title:
  xenial lvm2-monitor.service fails with lvm raid1 volumes

Status in lvm2 package in Ubuntu:
  New

Bug description:
  After installing xenial using the daily ubuntu-server installer,
  creating an LVM volume for the root filesystem, I lvconverted it into
  a raid1 mirror for redundancy over the pair of SSDs installed (as
  separate LVM PVs):

  sudo lvconvert -m 1 --type raid1 bonk/bonk1 /dev/sdc1 /dev/sdd1

  After a reboot, the lvm2-monitor.service fails. Relevant lines from
  journalctl:

$ sudo journalctl | grep -iE '(lvm|dmeventd)'
Mar 12 19:32:48 bonk1 systemd[1]: Listening on LVM2 metadata daemon 
socket.
Mar 12 19:32:48 bonk1 systemd[1]: Listening on LVM2 poll daemon socket.
Mar 12 19:32:48 bonk1 systemd[1]: Starting Monitoring of LVM2 mirrors, 
snapshots etc. using dmeventd or progress polling...
Mar 12 19:32:49 bonk1 systemd[1]: Started LVM2 metadata daemon.
Mar 12 19:32:52 bonk1 dmeventd[1039]: dmeventd 
libdevmapper-event-lvm2raid.so dlopen failed: libdevmapper-event-lvm2raid.so: 
cannot open shared object file: No such file or 

[Touch-packages] [Bug 1556447] Re: lxc-start fails: lxc_cgfsng - cgfsng.c:all_controllers_found:430 - no systemd controller mountpoint found

[Stephen Warren]

I have 2 Xenial systems. They are both fully up-to-date as of 5 minutes
ago. The failing system is a laptop running XFCE GUI, and I'm attempting
to use LXC from a GUI terminal. The other system is a linode that I
access via ssh, and LXC works fine there. I believe I've configured the
two systems the same way w.r.t. lxc (e.g. /etc/subuid, /etx/lxc/lxc-
usernet, ~/.config/lxc/default.conf, etc.). The primary difference is
that the Linode system is running a Linode-provided kernel, whereas my
laptop is running an Ubuntu-provided kernel.

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

Title:
  lxc-start fails: lxc_cgfsng - cgfsng.c:all_controllers_found:430 - no
  systemd controller mountpoint found

Status in lxc package in Ubuntu:
  New

Bug description:
  On Ubuntu Xenial pre-release, I see the following, so can't start a
  container:

  [swarren@sprint ~]$ lxc-create -t download -n t2 -- -d ubuntu -r trusty -a 
amd64
  Using image from local cache
  Unpacking the rootfs

  ---
  You just created an Ubuntu container (release=trusty, arch=amd64, 
variant=default)

  To enable sshd, run: apt-get install openssh-server

  For security reason, container images ship without user accounts
  and without a root password.

  Use lxc-attach or chroot directly into the rootfs to set a root password
  or create user accounts.

  
  swarren@sprint ~]$ lxc-start -n t2 -d
  lxc-start: lxc_start.c: main: 344 The container failed to start.
  lxc-start: lxc_start.c: main: 346 To get more details, run the container in 
foreground mode.
  lxc-start: lxc_start.c: main: 348 Additional information can be obtained by 
setting the --logfile and --logpriority options.

  
  [swarren@sprint ~]$ lxc-start -n t2 -d -o /dev/stdout -l debug -F
lxc-start 20160312101415.704 INFO lxc_start_ui - 
lxc_start.c:main:264 - using rcfile /home/swarren/.local/share/lxc/t2/config
lxc-start 20160312101415.705 WARN lxc_confile - 
confile.c:config_pivotdir:1859 - lxc.pivotdir is ignored.  It will soon become 
an error.
lxc-start 20160312101415.705 INFO lxc_confile - 
confile.c:config_idmap:1495 - read uid map: type u nsid 0 hostid 10 range 
65536
lxc-start 20160312101415.705 INFO lxc_confile - 
confile.c:config_idmap:1495 - read uid map: type g nsid 0 hostid 10 range 
65536
lxc-start 20160312101415.707 INFO lxc_lsm - lsm/lsm.c:lsm_init:48 - 
LSM security driver AppArmor
lxc-start 20160312101415.708 INFO lxc_seccomp - 
seccomp.c:parse_config_v2:342 - processing: .reject_force_umount  # comment 
this to allow umount -f;  not recommended.
lxc-start 20160312101415.708 INFO lxc_seccomp - 
seccomp.c:parse_config_v2:446 - Adding native rule for reject_force_umount 
action 0
lxc-start 20160312101415.708 INFO lxc_seccomp - 
seccomp.c:do_resolve_add_rule:216 - Setting seccomp rule to reject force umounts

lxc-start 20160312101415.708 INFO lxc_seccomp - 
seccomp.c:parse_config_v2:449 - Adding compat rule for reject_force_umount 
action 0
lxc-start 20160312101415.708 INFO lxc_seccomp - 
seccomp.c:do_resolve_add_rule:216 - Setting seccomp rule to reject force umounts

lxc-start 20160312101415.708 INFO lxc_seccomp - 
seccomp.c:parse_config_v2:342 - processing: .[all].
lxc-start 20160312101415.708 INFO lxc_seccomp - 
seccomp.c:parse_config_v2:342 - processing: .kexec_load errno 1.
lxc-start 20160312101415.708 INFO lxc_seccomp - 
seccomp.c:parse_config_v2:446 - Adding native rule for kexec_load action 327681
lxc-start 20160312101415.708 INFO lxc_seccomp - 
seccomp.c:parse_config_v2:449 - Adding compat rule for kexec_load action 327681
lxc-start 20160312101415.708 INFO lxc_seccomp - 
seccomp.c:parse_config_v2:342 - processing: .open_by_handle_at errno 1.
lxc-start 20160312101415.708 INFO lxc_seccomp - 
seccomp.c:parse_config_v2:446 - Adding native rule for open_by_handle_at action 
327681
lxc-start 20160312101415.708 INFO lxc_seccomp - 
seccomp.c:parse_config_v2:449 - Adding compat rule for open_by_handle_at action 
327681
lxc-start 20160312101415.708 INFO lxc_seccomp - 
seccomp.c:parse_config_v2:342 - processing: .init_module errno 1.
lxc-start 20160312101415.708 INFO lxc_seccomp - 
seccomp.c:parse_config_v2:446 - Adding native rule for init_module action 327681
lxc-start 20160312101415.708 INFO lxc_seccomp - 
seccomp.c:parse_config_v2:449 - Adding compat rule for init_module action 327681
lxc-start 20160312101415.708 INFO lxc_seccomp - 
seccomp.c:parse_config_v2:342 - processing: .finit_module errno 1.
lxc-start 20160312101415.708 INFO lxc_seccomp - 
seccomp.c:parse_config_v2:446 - Adding native rule for finit_module action 
327681
lxc-start 20160312101415.708 INFO 

[Touch-packages] [Bug 1556433] Re: Booting is taking too long to start from grub

[Pavlushka]

** Description changed:

  Booting takes to start almost three minutes  after selecting Xubuntu
  Xenial. But it does not happen for the Ubuntu 14.04 LTS listed in the
  same menu. Xubuntu is installed in a USB 3 external Harddisk and Ubuntu
  is installed in internal Harddisk, but it was not happening for other
- installations.
+ installations. Like to add, after the boot started, it loaded much
+ quicker than Ubuntu, there is a chance that the logs were stuck and
+ appeared all at a time.

** Package changed: xubuntu-docs (Ubuntu) => systemd (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/1556433

Title:
  Booting is taking too long to start from grub

Status in systemd package in Ubuntu:
  New

Bug description:
  Booting takes to start almost three minutes  after selecting Xubuntu
  Xenial. But it does not happen for the Ubuntu 14.04 LTS listed in the
  same menu. Xubuntu is installed in a USB 3 external Harddisk and
  Ubuntu is installed in internal Harddisk, but it was not happening for
  other installations. Like to add, after the boot started, it loaded
  much quicker than Ubuntu, there is a chance that the logs were stuck
  and appeared all at a time.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1556433/+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 1556447] [NEW] lxc-start fails: lxc_cgfsng - cgfsng.c:all_controllers_found:430 - no systemd controller mountpoint found

[Stephen Warren]

Public bug reported:

On Ubuntu Xenial pre-release, I see the following, so can't start a
container:

[swarren@sprint ~]$ lxc-create -t download -n t2 -- -d ubuntu -r trusty -a amd64
Using image from local cache
Unpacking the rootfs

---
You just created an Ubuntu container (release=trusty, arch=amd64, 
variant=default)

To enable sshd, run: apt-get install openssh-server

For security reason, container images ship without user accounts
and without a root password.

Use lxc-attach or chroot directly into the rootfs to set a root password
or create user accounts.


swarren@sprint ~]$ lxc-start -n t2 -d
lxc-start: lxc_start.c: main: 344 The container failed to start.
lxc-start: lxc_start.c: main: 346 To get more details, run the container in 
foreground mode.
lxc-start: lxc_start.c: main: 348 Additional information can be obtained by 
setting the --logfile and --logpriority options.


[swarren@sprint ~]$ lxc-start -n t2 -d -o /dev/stdout -l debug -F
  lxc-start 20160312101415.704 INFO lxc_start_ui - lxc_start.c:main:264 
- using rcfile /home/swarren/.local/share/lxc/t2/config
  lxc-start 20160312101415.705 WARN lxc_confile - 
confile.c:config_pivotdir:1859 - lxc.pivotdir is ignored.  It will soon become 
an error.
  lxc-start 20160312101415.705 INFO lxc_confile - 
confile.c:config_idmap:1495 - read uid map: type u nsid 0 hostid 10 range 
65536
  lxc-start 20160312101415.705 INFO lxc_confile - 
confile.c:config_idmap:1495 - read uid map: type g nsid 0 hostid 10 range 
65536
  lxc-start 20160312101415.707 INFO lxc_lsm - lsm/lsm.c:lsm_init:48 - 
LSM security driver AppArmor
  lxc-start 20160312101415.708 INFO lxc_seccomp - 
seccomp.c:parse_config_v2:342 - processing: .reject_force_umount  # comment 
this to allow umount -f;  not recommended.
  lxc-start 20160312101415.708 INFO lxc_seccomp - 
seccomp.c:parse_config_v2:446 - Adding native rule for reject_force_umount 
action 0
  lxc-start 20160312101415.708 INFO lxc_seccomp - 
seccomp.c:do_resolve_add_rule:216 - Setting seccomp rule to reject force umounts

  lxc-start 20160312101415.708 INFO lxc_seccomp - 
seccomp.c:parse_config_v2:449 - Adding compat rule for reject_force_umount 
action 0
  lxc-start 20160312101415.708 INFO lxc_seccomp - 
seccomp.c:do_resolve_add_rule:216 - Setting seccomp rule to reject force umounts

  lxc-start 20160312101415.708 INFO lxc_seccomp - 
seccomp.c:parse_config_v2:342 - processing: .[all].
  lxc-start 20160312101415.708 INFO lxc_seccomp - 
seccomp.c:parse_config_v2:342 - processing: .kexec_load errno 1.
  lxc-start 20160312101415.708 INFO lxc_seccomp - 
seccomp.c:parse_config_v2:446 - Adding native rule for kexec_load action 327681
  lxc-start 20160312101415.708 INFO lxc_seccomp - 
seccomp.c:parse_config_v2:449 - Adding compat rule for kexec_load action 327681
  lxc-start 20160312101415.708 INFO lxc_seccomp - 
seccomp.c:parse_config_v2:342 - processing: .open_by_handle_at errno 1.
  lxc-start 20160312101415.708 INFO lxc_seccomp - 
seccomp.c:parse_config_v2:446 - Adding native rule for open_by_handle_at action 
327681
  lxc-start 20160312101415.708 INFO lxc_seccomp - 
seccomp.c:parse_config_v2:449 - Adding compat rule for open_by_handle_at action 
327681
  lxc-start 20160312101415.708 INFO lxc_seccomp - 
seccomp.c:parse_config_v2:342 - processing: .init_module errno 1.
  lxc-start 20160312101415.708 INFO lxc_seccomp - 
seccomp.c:parse_config_v2:446 - Adding native rule for init_module action 327681
  lxc-start 20160312101415.708 INFO lxc_seccomp - 
seccomp.c:parse_config_v2:449 - Adding compat rule for init_module action 327681
  lxc-start 20160312101415.708 INFO lxc_seccomp - 
seccomp.c:parse_config_v2:342 - processing: .finit_module errno 1.
  lxc-start 20160312101415.708 INFO lxc_seccomp - 
seccomp.c:parse_config_v2:446 - Adding native rule for finit_module action 
327681
  lxc-start 20160312101415.708 INFO lxc_seccomp - 
seccomp.c:parse_config_v2:449 - Adding compat rule for finit_module action 
327681
  lxc-start 20160312101415.708 INFO lxc_seccomp - 
seccomp.c:parse_config_v2:342 - processing: .delete_module errno 1.
  lxc-start 20160312101415.708 INFO lxc_seccomp - 
seccomp.c:parse_config_v2:446 - Adding native rule for delete_module action 
327681
  lxc-start 20160312101415.708 INFO lxc_seccomp - 
seccomp.c:parse_config_v2:449 - Adding compat rule for delete_module action 
327681
  lxc-start 20160312101415.708 INFO lxc_seccomp - 
seccomp.c:parse_config_v2:456 - Merging in the compat seccomp ctx into the main 
one
  lxc-start 20160312101415.708 DEBUGlxc_start - 
start.c:setup_signal_fd:289 - sigchild handler set
  lxc-start 20160312101415.708 DEBUGlxc_console - 
console.c:lxc_console_peer_default:437 - opening /dev/tty for console peer
  lxc-start 20160312101415.708 INFO lxc_caps 

[Touch-packages] [Bug 1556433] [NEW] Booting is taking too long to start from grub

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

Booting takes to start almost three minutes  after selecting Xubuntu
Xenial. But it does not happen for the Ubuntu 14.04 LTS listed in the
same menu. Xubuntu is installed in a USB 3 external Harddisk and Ubuntu
is installed in internal Harddisk, but it was not happening for other
installations. Like to add, after the boot started, it loaded much
quicker than Ubuntu, there is a chance that the logs were stuck and
appeared all at a time.

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


** Tags: boot grub xenial xubuntu
-- 
Booting is taking too long to start from grub
https://bugs.launchpad.net/bugs/1556433
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to systemd in Ubuntu.

-- 
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 1556330] Re: upstream curl bug #1371: p12 client certificates code is broken

[LocutusOfBorg]

unfortunately it doesn't seem to build.

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

Title:
  upstream curl bug #1371: p12 client certificates code is broken

Status in curl package in Ubuntu:
  Fix Released
Status in curl source package in Trusty:
  Triaged

Bug description:
  [Impact]

  The bug makes it impossible to use PKCS#12 secure storage of client
  certificates and private keys with any affected Ubuntu releases. The
  fix is one line fixing a broken switch statement and was already
  tested against Ubuntu 14.04 LTS with a rebuilt curl package.

  This was fixed in upstream libcurl in the following bug:

  https://sourceforge.net/p/curl/bugs/1371/

  The bug fix consists of one missing break statement at the end of a
  case in a switch statement.

  I personally patched the bug using source code release
  curl_7.35.0-1ubuntu2.6.dsc, used in Ubuntu 14.04 LTS, and verified it
  does indeed fix the bug and all of the package's tests still pass
  afterwards.

  [Test Case]

  The bug can be reproduced using the following libcurl parameters (even
  via CLI, pycurl, etc.).

  CURLOPT_SSLCERTTYPE == "P12"
  CURLOPT_SSLCERT = path to PKCS#12
  CURLOPT_SSLKEY = path to PKCS#12
  CURLOPT_SSLKEYPASSWD = key for PKCS#12 if needed

  Basically, just use a PKCS#12 format client certificate and private
  key against some certificate protected web server.

  [Regression Potential]

  If it could possibly break anything, which is extraordinarily
  unlikely, it would break one of the three client certificate formats
  (most likely PKCS#12 but also PEM or DER). Note 1/3 formats is already
  broken due to the bug. Client certificates of all three types could be
  checked to prevent this.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/curl/+bug/1556330/+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 1556412] Re: webappUrlPatterns does not work on multiple "radiofrance" sites

[Olivier Tilloy]

** Changed in: webbrowser-app (Ubuntu)
 Assignee: (unassigned) => Alexandre Abreu (abreu-alexandre)

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

Title:
  webappUrlPatterns does not work on multiple "radiofrance" sites

Status in webbrowser-app package in Ubuntu:
  New

Bug description:
  Hi,

  I do not manage to confine my webapp on its site, the "--webappUrlPatterns" 
just seems to be ignored.
  I tested on Ubuntu 15.10 and on Mako (up-to-date rc-proposed).

  Test case 1 (working):
  Run "webapp-container --webappUrlPatterns=http://foo.org/* 
http://www.google.com/;
  → As expected, any link clicked on this page is opened in the Web browser (as 
no URL match the pattern)

  Test case 2 (failure):
  Run "webapp-container --webappUrlPatterns=http://foo.org/* 
http://www.fipradio.fr/player;
  → All URLs are opened in the webapp. I can go to twitter, facebook... 
anywhere.

  I have the same issue on other Radio France sites, like:
  * http://www.franceculture.fr/
  * http://www.mouv.fr/
  * http://www.francebleu.fr/

  Strangely enough, everything seems to work on:
  * http://www.francemusique.fr/
  * http://www.franceinter.fr/

  If it can help, I noticed strange things on http://www.franceinfo.fr/:
  At the bottom of the page, the Twitter, Facebook and Dailymotion links are 
opened in the webapp whereas the "radiofrance.fr" link is opened in the web 
browser.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: webapp-container 0.23+15.10.20150929-0ubuntu1
  ProcVersionSignature: Ubuntu 4.2.0-34.39-generic 4.2.8-ckt4
  Uname: Linux 4.2.0-34-generic x86_64
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Mar 12 12:36:31 2016
  InstallationDate: Installed on 2015-10-19 (144 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20151017)
  SourcePackage: webbrowser-app
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1556412/+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 1556437] Re: unity8-dash crashed with SIGSEGV in QOpenGLContext::shareGroup()

[Apport retracing service]

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

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 #1541057, 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.

** Attachment removed: "CoreDump.gz"
   
https://bugs.launchpad.net/bugs/1556437/+attachment/4596905/+files/CoreDump.gz

** Attachment removed: "Disassembly.txt"
   
https://bugs.launchpad.net/bugs/1556437/+attachment/4596907/+files/Disassembly.txt

** Attachment removed: "ProcMaps.txt"
   
https://bugs.launchpad.net/bugs/1556437/+attachment/4596909/+files/ProcMaps.txt

** Attachment removed: "ProcStatus.txt"
   
https://bugs.launchpad.net/bugs/1556437/+attachment/4596910/+files/ProcStatus.txt

** Attachment removed: "Registers.txt"
   
https://bugs.launchpad.net/bugs/1556437/+attachment/4596911/+files/Registers.txt

** Attachment removed: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/1556437/+attachment/4596913/+files/Stacktrace.txt

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1556437/+attachment/4596914/+files/ThreadStacktrace.txt

** This bug has been marked a duplicate of private bug 1541057

** 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 unity8 in Ubuntu.
https://bugs.launchpad.net/bugs/1556437

Title:
  unity8-dash crashed with SIGSEGV in QOpenGLContext::shareGroup()

Status in unity8 package in Ubuntu:
  New

Bug description:
  unity8-dash crashes when I try to open any program

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: unity8 8.11+16.04.20160310.4-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-12.28-generic 4.4.4
  Uname: Linux 4.4.0-12-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CrashCounter: 1
  Date: Sat Mar 12 13:01:25 2016
  ExecutablePath: /usr/bin/unity8-dash
  InstallationDate: Installed on 2016-02-16 (25 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160215)
  ProcCmdline: unity8-dash 
--desktop_file_hint=/usr/share/applications/unity8-dash.desktop
  ProcEnviron:
   LANGUAGE=pt_BR:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pt_BR.UTF-8
   SHELL=/bin/bash
  Signal: 11
  SourcePackage: unity8
  StacktraceTop:
   QOpenGLContext::shareGroup() const () from 
/usr/lib/x86_64-linux-gnu/libQt5Gui.so.5
   ?? () from /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5
   ?? () from /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5
   ?? () from /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5
   ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
  Title: unity8-dash crashed with SIGSEGV in QOpenGLContext::shareGroup()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1556437/+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 1556330] Re: upstream curl bug #1371: p12 client certificates code is broken

[LocutusOfBorg]

build ongoing here
https://launchpad.net/~costamagnagianfranco/+archive/ubuntu/locutusofborg-ppa/

I'll leave for you, testing my ppa, and fille the paperwork
please read this, and convert this bug to look an SRU bug
https://wiki.ubuntu.com/StableReleaseUpdates
(section 3.1, but read all).

thanks for the patch :)

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

Title:
  upstream curl bug #1371: p12 client certificates code is broken

Status in curl package in Ubuntu:
  Fix Released
Status in curl source package in Trusty:
  Triaged

Bug description:
  [Impact]

  The bug makes it impossible to use PKCS#12 secure storage of client
  certificates and private keys with any affected Ubuntu releases. The
  fix is one line fixing a broken switch statement and was already
  tested against Ubuntu 14.04 LTS with a rebuilt curl package.

  This was fixed in upstream libcurl in the following bug:

  https://sourceforge.net/p/curl/bugs/1371/

  The bug fix consists of one missing break statement at the end of a
  case in a switch statement.

  I personally patched the bug using source code release
  curl_7.35.0-1ubuntu2.6.dsc, used in Ubuntu 14.04 LTS, and verified it
  does indeed fix the bug and all of the package's tests still pass
  afterwards.

  [Test Case]

  The bug can be reproduced using the following libcurl parameters (even
  via CLI, pycurl, etc.).

  CURLOPT_SSLCERTTYPE == "P12"
  CURLOPT_SSLCERT = path to PKCS#12
  CURLOPT_SSLKEY = path to PKCS#12
  CURLOPT_SSLKEYPASSWD = key for PKCS#12 if needed

  Basically, just use a PKCS#12 format client certificate and private
  key against some certificate protected web server.

  [Regression Potential]

  If it could possibly break anything, which is extraordinarily
  unlikely, it would break one of the three client certificate formats
  (most likely PKCS#12 but also PEM or DER). Note 1/3 formats is already
  broken due to the bug. Client certificates of all three types could be
  checked to prevent this.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/curl/+bug/1556330/+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 1556330] Re: upstream curl bug #1371: p12 client certificates code is broken

[LocutusOfBorg]

1) go there https://launchpad.net/ubuntu/+source/curl
2) find the dsc link
3) dget -u 
https://launchpad.net/ubuntu/+archive/primary/+files/curl_7.35.0-1ubuntu2.6.dsc
4) wget your patch 
https://bugs.launchpad.net/ubuntu/+source/curl/+bug/1556330/+attachment/4596446/+files/libcurl_broken_pkcs12.patch
5) check if xenial is fixed (yes)
6) add-patch libcurl_broken_pkcs12.patch
7) explain changes in changelog
8) upload to ppa (dpkg-buildpackage -S -d && dput ppa:blah/blah-ppa 
filename_source.changes)
9) dput ubuntu filename_source.changes


I'm not a core-dev, so I can't do "9"
but I did instead:
10) debdiff curl_7.35.0-1ubuntu2.*.dsc > debdiff

and attached here

** Attachment added: "debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/curl/+bug/1556330/+attachment/4596928/+files/debdiff

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

Title:
  upstream curl bug #1371: p12 client certificates code is broken

Status in curl package in Ubuntu:
  Fix Released
Status in curl source package in Trusty:
  Triaged

Bug description:
  [Impact]

  The bug makes it impossible to use PKCS#12 secure storage of client
  certificates and private keys with any affected Ubuntu releases. The
  fix is one line fixing a broken switch statement and was already
  tested against Ubuntu 14.04 LTS with a rebuilt curl package.

  This was fixed in upstream libcurl in the following bug:

  https://sourceforge.net/p/curl/bugs/1371/

  The bug fix consists of one missing break statement at the end of a
  case in a switch statement.

  I personally patched the bug using source code release
  curl_7.35.0-1ubuntu2.6.dsc, used in Ubuntu 14.04 LTS, and verified it
  does indeed fix the bug and all of the package's tests still pass
  afterwards.

  [Test Case]

  The bug can be reproduced using the following libcurl parameters (even
  via CLI, pycurl, etc.).

  CURLOPT_SSLCERTTYPE == "P12"
  CURLOPT_SSLCERT = path to PKCS#12
  CURLOPT_SSLKEY = path to PKCS#12
  CURLOPT_SSLKEYPASSWD = key for PKCS#12 if needed

  Basically, just use a PKCS#12 format client certificate and private
  key against some certificate protected web server.

  [Regression Potential]

  If it could possibly break anything, which is extraordinarily
  unlikely, it would break one of the three client certificate formats
  (most likely PKCS#12 but also PEM or DER). Note 1/3 formats is already
  broken due to the bug. Client certificates of all three types could be
  checked to prevent this.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/curl/+bug/1556330/+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 1539158] Re: Unable to pair with in-car hands-free system after OTA-9 update

[Marco Graziotti]

Thanks to the instruction provided by "Stunt" (
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1539158/comments/14
), I have generated a bluetooth log file that you can find attached at
this message.

My own hands free system it's a NISSAN CONNECT, I'm using a Meizu MX4
with OTA 9.1.

I hope that this log file contains what you need and let me know if you
require anything else.

Thank you.


P.S.:  I think I have removed any sensitive information from that log.


** Attachment added: "syslog_bluetooth pair_MX4.txt"
   
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1539158/+attachment/4596895/+files/syslog_bluetooth%20pair_MX4.txt

-- 
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:
  Invalid
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 1556419] Re: nf_conntrack: automatic helper assignment is deprecated

[dino99]

Kernel build settings & iptables entries:

http://www.odi.ch/weblog/posting.php?posting=663

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

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

Title:
   nf_conntrack: automatic helper assignment is deprecated

Status in iptables package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Get this logged into journalctl (since a moment):

   kernel: nf_conntrack: automatic helper assignment is deprecated and
  it will be removed soon. Use the iptables CT target to attach helpers
  instead.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-13-generic 4.4.0-13.29
  ProcVersionSignature: Ubuntu 4.4.0-13.29-generic 4.4.5
  Uname: Linux 4.4.0-13-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  oem1942 F pulseaudio
   /dev/snd/pcmC0D0p:   oem1942 F...m pulseaudio
   /dev/snd/controlC0:  oem1942 F pulseaudio
  CurrentDesktop: GNOME
  Date: Sat Mar 12 14:52:09 2016
  HibernationDevice: RESUME=UUID=0a9ca7f0-6eeb-4b21-b70f-670fa600de16
  IwConfig:
   eth0  no wireless extensions.
   
   eth1  no wireless extensions.
   
   lono wireless extensions.
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 003 Device 002: ID 046d:c062 Logitech, Inc. M-UAS144 [LS1 Laser Mouse]
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: ASUSTEK COMPUTER INC P5W DH Deluxe
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-13-generic 
root=UUID=7c755ed6-51cc-4b75-88ac-9c75acf82749 ro
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-13-generic N/A
   linux-backports-modules-4.4.0-13-generic  N/A
   linux-firmware1.156
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/22/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3002
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5W DH Deluxe
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3002:bd07/22/2010:svnASUSTEKCOMPUTERINC:pnP5WDHDeluxe:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5WDHDeluxe:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: P5W DH Deluxe
  dmi.product.version: System Version
  dmi.sys.vendor: ASUSTEK COMPUTER INC

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iptables/+bug/1556419/+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 1451728] Re: [master] kde-config-telepathy-accounts package install error

[Philip Muškovac]

** Also affects: kaccounts-integration (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: kaccounts-integration (Ubuntu)
   Importance: Undecided => Critical

** Changed in: kaccounts-integration (Ubuntu)
   Status: New => In Progress

** Changed in: kaccounts-integration (Ubuntu)
Milestone: None => ubuntu-16.04

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

Title:
  [master] kde-config-telepathy-accounts package install error

Status in Kubuntu PPA:
  Confirmed
Status in meta-telepathy:
  Fix Released
Status in kaccounts-integration package in Ubuntu:
  In Progress
Status in kaccounts-providers package in Ubuntu:
  Triaged
Status in ktp-accounts-kcm package in Ubuntu:
  Triaged
Status in libaccounts-glib package in Ubuntu:
  Fix Released
Status in kaccounts-providers source package in Wily:
  Triaged
Status in ktp-accounts-kcm source package in Wily:
  Triaged

Bug description:
  Installing from Kubuntu 15.04 backports:

  Unpacking kde-config-telepathy-accounts (15.04.0-0ubuntu1~ubuntu15.04~ppa1) 
over (0.9.0-0ubuntu1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/kde-config-telepathy-accounts_15.04.0-0ubuntu1~ubuntu15.04~ppa1_amd64.deb
 (--unpack):
   trying to overwrite '/usr/share/accounts/services/facebook-im.service', 
which is also in package account-plugin-facebook 0.12+15.04.20150415.1-0ubuntu1
  dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)

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