date:20161212

This bug was fixed in the package xserver-xorg-video-openchrome -
1:0.5.0-1

---
xserver-xorg-video-openchrome (1:0.5.0-1) unstable; urgency=medium

  * New upstream release. (LP: #1640787)
  * Update VCS fields.
  * Update lintian overrides.
  * Add debian/source/format file.
  * Architectures:
 - Remove LPIA discontinued.
 - Add x32 (Closes: #775201).
  * Remove libdrm-dev from Build-Depend for Hurd (Closes: #672546).
  * Update debian/watch.
  * Bump Standards-Version to 3.9.8:
 - Remove DM-Upload-Allowed field.
  * Update and convert d/copyright to DEP5.
  * Bump debhelper compat to 10.
  * Add a patch to fix a spelling error.
  * Switch from -dbg to -dbgsym package.
  * Bump Build-Depends xserver-xorg-dev to >= 2:1.17.
  * Add a patch to enable reproducible build (Closes: #831405).
  * Enable hardened build (Closes: #734640).

 -- Dylan Aïssi   Thu, 01 Dec 2016 23:17:22 +0100

** Changed in: xserver-xorg-video-openchrome (Ubuntu)
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-video-openchrome in
Ubuntu.
https://bugs.launchpad.net/bugs/1640787

Title:
  update to 0.5

Status in xserver-xorg-video-openchrome package in Ubuntu:
  Fix Released

Bug description:
  the package 0.3.3 version of openchrome is too old
  please update this package to 0.5, less buggy and more feature

  https://lists.freedesktop.org/archives/openchrome-
  users/2016-July/007285.html

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-openchrome/+bug/1640787/+subscriptions

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

[Desktop-packages] [Bug 1648637] Re: handle interruped read and write calls

This bug was fixed in the package lightdm - 1.21.3-0ubuntu1

---
lightdm (1.21.3-0ubuntu1) zesty; urgency=medium

  * New upstream release:
- Fix crashes introduced in 1.21.2 due to environment variable changes
- Fix incorrect unref in XDMCP server code
- Fix logging warning

 -- Robert Ancell   Fri, 09 Dec 2016
14:04:49 +1300

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

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1648637

Title:
  handle interruped read and write calls

Status in Light Display Manager:
  Fix Released
Status in Light Display Manager 1.10 series:
  Fix Committed
Status in Light Display Manager 1.18 series:
  Fix Committed
Status in Light Display Manager 1.2 series:
  Fix Committed
Status in Light Display Manager 1.20 series:
  Fix Committed
Status in lightdm package in Ubuntu:
  Fix Released
Status in lightdm source package in Precise:
  New
Status in lightdm source package in Trusty:
  New
Status in lightdm source package in Xenial:
  New
Status in lightdm source package in Yakkety:
  New
Status in lightdm source package in Zesty:
  Fix Released

Bug description:
  Use SA_RESTART flag to make sure that interrupted calls to read and/or
  write are restarted.

  In my case read is interrupted when reading login1_session_id. Result
  of not handling EINTR error is that login1_session_id is set to NULL
  and console_kit_cookie gets login1 session id.

  Related warnings in lightdm.log:
  [+0.44s] WARNING: Session pid=617: Error reading from session: Interrupted 
system call
  [+0.70s] DEBUG: Activating VT 7
  [+0.70s] DEBUG: Activating ConsoleKit session c1
  [+0.70s] WARNING: Error getting ConsoleKit session: 
GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name 
org.freedesktop.ConsoleKit was not provided by any .service files

  And because login1_session_id is null fix for 1637758 bug does not
  work.

To manage notifications about this bug go to:
https://bugs.launchpad.net/lightdm/+bug/1648637/+subscriptions

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

[Desktop-packages] [Bug 1633075] Re: xkb configuration

[Expired for x11-xkb-utils (Ubuntu) because there has been no activity
for 60 days.]

** Changed in: x11-xkb-utils (Ubuntu)
   Status: Incomplete => Expired

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to x11-xkb-utils in Ubuntu.
https://bugs.launchpad.net/bugs/1633075

Title:
  xkb configuration

Status in x11-xkb-utils package in Ubuntu:
  Expired

Bug description:
   • xprop -root | grep XKB
   • gsettings get org.gnome.libgnomekbd.keyboard model
   • gsettings get org.gnome.libgnomekbd.keyboard layouts
   • gsettings get org.gnome.libgnomekbd.keyboard options

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/x11-xkb-utils/+bug/1633075/+subscriptions

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

[Desktop-packages] [Bug 1633824] Re: nautilus ignores trash on external drives

2016-12-12 Thread Mathew Hodson

** No longer affects: nautilus (Ubuntu Yakkety)

** No longer affects: nautilus (Ubuntu)

** Project changed: nautilus => ubuntu-translations

** Changed in: ubuntu-translations
   Importance: Medium => Undecided

** Changed in: ubuntu-translations
   Status: Invalid => New

** Changed in: ubuntu-translations
 Remote watch: GNOME Bug Tracker #773819 => None

** No longer affects: ubuntu-translations

** Changed in: glib2.0 (Ubuntu)
   Importance: Undecided => Medium

** Changed in: glib2.0 (Ubuntu Yakkety)
   Importance: Undecided => Medium

** Bug watch removed: GNOME Bug Tracker #773819
   https://bugzilla.gnome.org/show_bug.cgi?id=773819

** Tags removed: nautilus trash

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/1633824

Title:
  nautilus ignores trash on external drives

Status in GLib:
  Fix Released
Status in glib2.0 package in Ubuntu:
  Fix Released
Status in glib2.0 source package in Yakkety:
  Fix Committed

Bug description:
  Using nautilus 3.20 as included in Ubuntu 16.10, I can move files to
  trash in general. However only the items removed from permanently
  installed drives shows up in the trash virtual folder. In the case of
  usb removable drives, the .Trash-1000 folder is correctly created, and
  the files are in there but the nautilus GUI does not show those files
  in its virtual trash folder.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: nautilus 1:3.20.3-1ubuntu3
  ProcVersionSignature: Ubuntu 4.8.0-25.27-generic 4.8.1
  Uname: Linux 4.8.0-25-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Oct 16 11:48:03 2016
  InstallationDate: Installed on 2016-02-19 (239 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to yakkety on 2016-10-13 (2 days ago)
  usr_lib_nautilus: gnome-terminal 3.20.2-1ubuntu5

To manage notifications about this bug go to:
https://bugs.launchpad.net/glib/+bug/1633824/+subscriptions

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

[Desktop-packages] [Bug 1638846] Re: Update GLib to fix a bug with Trash in Nautilus

2016-12-12 Thread Mathew Hodson

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

** Project changed: glib => ubuntu

** Changed in: ubuntu
   Importance: High => Undecided

** Changed in: ubuntu
   Status: Fix Released => New

** Changed in: ubuntu
 Remote watch: GNOME Bug Tracker #662946 => None

** No longer affects: ubuntu

** Bug watch removed: GNOME Bug Tracker #662946
   https://bugzilla.gnome.org/show_bug.cgi?id=662946

** This bug has been marked a duplicate of bug 1633824
   nautilus ignores trash on external drives

** Tags removed: nautilus trash

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to glib2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1638846

Title:
  Update GLib to fix a bug with Trash in Nautilus

Status in glib2.0 package in Ubuntu:
  Confirmed

Bug description:
  As described here there is a bug in Ubuntu 16.10 with trash and
  external drives in Nautilus:
  https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1633824

  Seems that this has been fixed already with GLib 2.50.1 according to
  https://bugzilla.gnome.org/show_bug.cgi?id=773819#c3

  So updating the package for Ubuntu 16.10 would fix this bug.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1638846/+subscriptions

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

[Desktop-packages] [Bug 714908] Re: gnome-keyring reads unsafe SSH keys

2016-12-12 Thread Bug Watch Updater

** Changed in: gnome-keyring
   Status: New => Confirmed

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-keyring in Ubuntu.
https://bugs.launchpad.net/bugs/714908

Title:
  gnome-keyring reads unsafe SSH keys

Status in GNOME Keyring:
  Confirmed
Status in gnome-keyring package in Ubuntu:
  Invalid
Status in gnome-keyring source package in Natty:
  Invalid

Bug description:
  Binary package hint: gnome-keyring

  OpenSSH enforces that one's keys must be mode 0700 so that unsafe
  permissions do not go unnoticed. gnome-keyring should perform this
  check as well. It looks like pkcs11/ssh-store/gkm-ssh-private-key.c
  gkm_ssh_private_key_parse() is the place to do it, or possibly pkcs11
  /ssh-store/gkm-ssh-module.c file_load() since it checks some aspects
  of the files already.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.04
  Package: gnome-keyring 2.92.92.is.2.32.1-0ubuntu2
  ProcVersionSignature: Ubuntu 2.6.37-12.26-generic 2.6.37
  Uname: Linux 2.6.37-12-generic x86_64
  Architecture: amd64
  Date: Mon Feb  7 15:23:20 2011
  ProcEnviron:
   LANGUAGE=en_US:en
   PATH=(custom, user)
   LANG=en_US.UTF-8
   LC_MESSAGES=en_US.utf8
   SHELL=/bin/bash
  SourcePackage: gnome-keyring

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-keyring/+bug/714908/+subscriptions

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

[Desktop-packages] [Bug 1373136] Re: nvidia-331-uvm 331.38-0ubuntu7.1: nvidia-331-uvm kernel module failed to build [nvidia-modules-common.mk: No such file or directory]

2016-12-12 Thread Daniel van Vugt

** Changed in: nvidia-graphics-drivers-331-updates (Ubuntu)
   Importance: Undecided => High

** Changed in: nvidia-graphics-drivers-340-updates (Ubuntu)
   Importance: Undecided => High

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nvidia-graphics-drivers-331 in Ubuntu.
https://bugs.launchpad.net/bugs/1373136

Title:
  nvidia-331-uvm 331.38-0ubuntu7.1: nvidia-331-uvm kernel module failed
  to build [nvidia-modules-common.mk: No such file or directory]

Status in nvidia-graphics-drivers-331 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-331-updates package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-340-updates package in Ubuntu:
  Confirmed

Bug description:
  Automatically-generated bug report.
  Software Updater completed despite this issue.

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: nvidia-331-uvm 331.38-0ubuntu7.1
  ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6
  Uname: Linux 3.13.0-35-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.4
  Architecture: amd64
  DKMSBuildLog:
   DKMS make.log for nvidia-331-uvm-331.38 for kernel 3.13.0-36-generic (x86_64)
   Wed Sep 24 09:14:59 NZST 2014
   Makefile:215: 
/var/lib/dkms/nvidia-331/331.38/build/nvidia-modules-common.mk: No such file or 
directory
   make: *** No rule to make target 
`/var/lib/dkms/nvidia-331/331.38/build/nvidia-modules-common.mk'.  Stop.
  DKMSKernelVersion: 3.13.0-36-generic
  Date: Wed Sep 24 09:15:06 2014
  InstallationDate: Installed on 2014-07-31 (54 days ago)
  InstallationMedia: Lubuntu 14.04 LTS "Trusty Tahr" - Release amd64 
(20140416.2)
  PackageVersion: 331.38-0ubuntu7.1
  SourcePackage: nvidia-graphics-drivers-331
  Title: nvidia-331-uvm 331.38-0ubuntu7.1: nvidia-331-uvm kernel module failed 
to build
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1373136/+subscriptions

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

[Desktop-packages] [Bug 1649266] Re: nvidia-331-updates-uvm 331.113-0ubuntu0.0.4: nvidia-331-updates-uvm kernel module failed to build

2016-12-12 Thread Daniel van Vugt

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

Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1373136, so it 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. Feel free to continue to report any other bugs you may
find.


** This bug has been marked a duplicate of bug 1373136
   nvidia-331-uvm 331.38-0ubuntu7.1: nvidia-331-uvm kernel module failed to 
build [nvidia-modules-common.mk: No such file or directory]

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nvidia-graphics-drivers-331-updates in
Ubuntu.
https://bugs.launchpad.net/bugs/1649266

Title:
  nvidia-331-updates-uvm 331.113-0ubuntu0.0.4: nvidia-331-updates-uvm
  kernel module failed to build

Status in nvidia-graphics-drivers-331-updates package in Ubuntu:
  New

Bug description:
  i don't descrive it

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: nvidia-331-updates-uvm 331.113-0ubuntu0.0.4
  ProcVersionSignature: Ubuntu 3.13.0-45.74-generic 3.13.11-ckt13
  Uname: Linux 3.13.0-45-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.7
  Architecture: amd64
  DKMSBuildLog:
   DKMS make.log for nvidia-331-updates-uvm-331.113 for kernel 
3.13.0-105-generic (x86_64)
   lun 12 dic 2016, 13.42.52, CET
   Makefile:216: 
/var/lib/dkms/nvidia-331-updates/331.113/build/nvidia-modules-common.mk: File o 
directory non esistente
   make: ***  Nessuna regola per generare l'obiettivo 
"/var/lib/dkms/nvidia-331-updates/331.113/build/nvidia-modules-common.mk".  
Arresto.
  DKMSKernelVersion: 3.13.0-105-generic
  Date: Mon Dec 12 13:42:57 2016
  InstallationDate: Installed on 2015-01-04 (708 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  PackageVersion: 331.113-0ubuntu0.0.4
  SourcePackage: nvidia-graphics-drivers-331-updates
  Title: nvidia-331-updates-uvm 331.113-0ubuntu0.0.4: nvidia-331-updates-uvm 
kernel module failed to build
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331-updates/+bug/1649266/+subscriptions

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

[Desktop-packages] [Bug 1649437] Re: package libbrlapi0.6:amd64 5.3.1-2ubuntu2.1 failed to install/upgrade: package libbrlapi0.6:amd64 is already installed and configured

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

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 #1649438, 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 1649438
   package libbrlapi0.6:amd64 5.3.1-2ubuntu2.1 failed to install/upgrade: 
package libbrlapi0.6:amd64 is already installed and configured

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to brltty in Ubuntu.
https://bugs.launchpad.net/bugs/1649437

Title:
  package libbrlapi0.6:amd64 5.3.1-2ubuntu2.1 failed to install/upgrade:
  package libbrlapi0.6:amd64 is already installed and configured

Status in brltty package in Ubuntu:
  New

Bug description:
  I just read the mensage of error.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libbrlapi0.6:amd64 5.3.1-2ubuntu2.1
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.2
  AptdaemonVersion: 1.1.1+bzr982-0ubuntu14
  Architecture: amd64
  CrashReports:
   640:0:116:2422355:2016-12-12 23:14:40.401489019 -0200:2016-12-12 
23:14:43.001482647 -0200:/var/crash/initramfs-tools-bin.0.crash
   600:0:116:406103:2016-12-12 23:12:03.690696477 -0200:2016-12-12 
23:12:04.690696477 -0200:/var/crash/libbrlapi0.6:amd64.0.crash
   644:0:116:0:2016-12-12 23:14:43.001482647 -0200:2016-12-12 
23:14:43.001482647 -0200:/var/crash/initramfs-tools-bin.0.upload
   600:0:116:406100:2016-12-12 23:12:04.730698163 -0200:2016-12-12 
23:12:04.694696562 -0200:/var/crash/libdbus-1-3:amd64.0.crash
  Date: Mon Dec 12 23:12:04 2016
  Dependencies:
   gcc-6-base 6.0.1-0ubuntu1
   libc6 2.23-0ubuntu5
   libgcc1 1:6.0.1-0ubuntu1
  DuplicateSignature:
   package:libbrlapi0.6:amd64:5.3.1-2ubuntu2.1
   Processing triggers for desktop-file-utils (0.22-1ubuntu5) ...
   dpkg: error processing package libbrlapi0.6:amd64 (--configure):
package libbrlapi0.6:amd64 is already installed and configured
  ErrorMessage: package libbrlapi0.6:amd64 is already installed and configured
  InstallationDate: Installed on 2016-12-13 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.15
  SourcePackage: brltty
  Title: package libbrlapi0.6:amd64 5.3.1-2ubuntu2.1 failed to install/upgrade: 
package libbrlapi0.6:amd64 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/brltty/+bug/1649437/+subscriptions

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

[Desktop-packages] [Bug 1649437] [NEW] package libbrlapi0.6:amd64 5.3.1-2ubuntu2.1 failed to install/upgrade: package libbrlapi0.6:amd64 is already installed and configured

2016-12-12 Thread Michel

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

Public bug reported:

I just read the mensage of error.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: libbrlapi0.6:amd64 5.3.1-2ubuntu2.1
ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
Uname: Linux 4.4.0-21-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.2
AptdaemonVersion: 1.1.1+bzr982-0ubuntu14
Architecture: amd64
CrashReports:
 640:0:116:2422355:2016-12-12 23:14:40.401489019 -0200:2016-12-12 
23:14:43.001482647 -0200:/var/crash/initramfs-tools-bin.0.crash
 600:0:116:406103:2016-12-12 23:12:03.690696477 -0200:2016-12-12 
23:12:04.690696477 -0200:/var/crash/libbrlapi0.6:amd64.0.crash
 644:0:116:0:2016-12-12 23:14:43.001482647 -0200:2016-12-12 23:14:43.001482647 
-0200:/var/crash/initramfs-tools-bin.0.upload
 600:0:116:406100:2016-12-12 23:12:04.730698163 -0200:2016-12-12 
23:12:04.694696562 -0200:/var/crash/libdbus-1-3:amd64.0.crash
Date: Mon Dec 12 23:12:04 2016
Dependencies:
 gcc-6-base 6.0.1-0ubuntu1
 libc6 2.23-0ubuntu5
 libgcc1 1:6.0.1-0ubuntu1
DuplicateSignature:
 package:libbrlapi0.6:amd64:5.3.1-2ubuntu2.1
 Processing triggers for desktop-file-utils (0.22-1ubuntu5) ...
 dpkg: error processing package libbrlapi0.6:amd64 (--configure):
  package libbrlapi0.6:amd64 is already installed and configured
ErrorMessage: package libbrlapi0.6:amd64 is already installed and configured
InstallationDate: Installed on 2016-12-13 (0 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.1
 apt  1.2.15
SourcePackage: brltty
Title: package libbrlapi0.6:amd64 5.3.1-2ubuntu2.1 failed to install/upgrade: 
package libbrlapi0.6:amd64 is already installed and configured
UpgradeStatus: No upgrade log present (probably fresh install)

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


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

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to brltty in Ubuntu.
https://bugs.launchpad.net/bugs/1649437

Title:
  package libbrlapi0.6:amd64 5.3.1-2ubuntu2.1 failed to install/upgrade:
  package libbrlapi0.6:amd64 is already installed and configured

Status in brltty package in Ubuntu:
  New

Bug description:
  I just read the mensage of error.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libbrlapi0.6:amd64 5.3.1-2ubuntu2.1
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.2
  AptdaemonVersion: 1.1.1+bzr982-0ubuntu14
  Architecture: amd64
  CrashReports:
   640:0:116:2422355:2016-12-12 23:14:40.401489019 -0200:2016-12-12 
23:14:43.001482647 -0200:/var/crash/initramfs-tools-bin.0.crash
   600:0:116:406103:2016-12-12 23:12:03.690696477 -0200:2016-12-12 
23:12:04.690696477 -0200:/var/crash/libbrlapi0.6:amd64.0.crash
   644:0:116:0:2016-12-12 23:14:43.001482647 -0200:2016-12-12 
23:14:43.001482647 -0200:/var/crash/initramfs-tools-bin.0.upload
   600:0:116:406100:2016-12-12 23:12:04.730698163 -0200:2016-12-12 
23:12:04.694696562 -0200:/var/crash/libdbus-1-3:amd64.0.crash
  Date: Mon Dec 12 23:12:04 2016
  Dependencies:
   gcc-6-base 6.0.1-0ubuntu1
   libc6 2.23-0ubuntu5
   libgcc1 1:6.0.1-0ubuntu1
  DuplicateSignature:
   package:libbrlapi0.6:amd64:5.3.1-2ubuntu2.1
   Processing triggers for desktop-file-utils (0.22-1ubuntu5) ...
   dpkg: error processing package libbrlapi0.6:amd64 (--configure):
package libbrlapi0.6:amd64 is already installed and configured
  ErrorMessage: package libbrlapi0.6:amd64 is already installed and configured
  InstallationDate: Installed on 2016-12-13 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.15
  SourcePackage: brltty
  Title: package libbrlapi0.6:amd64 5.3.1-2ubuntu2.1 failed to install/upgrade: 
package libbrlapi0.6:amd64 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/brltty/+bug/1649437/+subscriptions

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

[Desktop-packages] [Bug 1649432] [NEW] is there an accidentally unpacked flashplugin-downloader package in the source packages?

2016-12-12 Thread Seth Arnold

Public bug reported:

After 'umt download flashplugin-nonfree ; cd flashplugin-nonfree' see
the following:

$ find . | grep flashplugin-downloader
./precise/flashplugin-nonfree-11.2.202.644ubuntu0.12.04.1/debian/flashplugin-downloader
./precise/flashplugin-nonfree-11.2.202.644ubuntu0.12.04.1/debian/flashplugin-downloader/usr
./precise/flashplugin-nonfree-11.2.202.644ubuntu0.12.04.1/debian/flashplugin-downloader/usr/share
./precise/flashplugin-nonfree-11.2.202.644ubuntu0.12.04.1/debian/flashplugin-downloader/usr/share/doc
./precise/flashplugin-nonfree-11.2.202.644ubuntu0.12.04.1/debian/flashplugin-downloader/usr/share/doc/flashplugin-downloader
./precise/flashplugin-nonfree-11.2.202.644ubuntu0.12.04.1/debian/flashplugin-downloader/usr/share/doc/flashplugin-downloader/copyright
./precise/flashplugin-nonfree-11.2.202.644ubuntu0.12.04.1/debian/flashplugin-downloader/usr/share/doc/flashplugin-downloader/changelog.gz
./precise/flashplugin-nonfree-11.2.202.644ubuntu0.12.04.1/debian/flashplugin-downloader/DEBIAN
./precise/flashplugin-nonfree-11.2.202.644ubuntu0.12.04.1/debian/flashplugin-downloader/DEBIAN/control
./precise/flashplugin-nonfree-11.2.202.644ubuntu0.12.04.1/debian/flashplugin-downloader/DEBIAN/md5sums
./precise/flashplugin-nonfree-11.2.202.644ubuntu0.12.04.1/debian/flashplugin-downloader.links
./precise/flashplugin-nonfree-11.2.202.644ubuntu0.12.04.1/debian/flashplugin-downloader.substvars
./yakkety/flashplugin-nonfree-11.2.202.644ubuntu0.16.10.1/debian/flashplugin-downloader
./yakkety/flashplugin-nonfree-11.2.202.644ubuntu0.16.10.1/debian/flashplugin-downloader/usr
./yakkety/flashplugin-nonfree-11.2.202.644ubuntu0.16.10.1/debian/flashplugin-downloader/usr/share
./yakkety/flashplugin-nonfree-11.2.202.644ubuntu0.16.10.1/debian/flashplugin-downloader/usr/share/doc
./yakkety/flashplugin-nonfree-11.2.202.644ubuntu0.16.10.1/debian/flashplugin-downloader/usr/share/doc/flashplugin-downloader
./yakkety/flashplugin-nonfree-11.2.202.644ubuntu0.16.10.1/debian/flashplugin-downloader/usr/share/doc/flashplugin-downloader/copyright
./yakkety/flashplugin-nonfree-11.2.202.644ubuntu0.16.10.1/debian/flashplugin-downloader/usr/share/doc/flashplugin-downloader/changelog.gz
./yakkety/flashplugin-nonfree-11.2.202.644ubuntu0.16.10.1/debian/flashplugin-downloader/DEBIAN
./yakkety/flashplugin-nonfree-11.2.202.644ubuntu0.16.10.1/debian/flashplugin-downloader/DEBIAN/control
./yakkety/flashplugin-nonfree-11.2.202.644ubuntu0.16.10.1/debian/flashplugin-downloader/DEBIAN/md5sums
./yakkety/flashplugin-nonfree-11.2.202.644ubuntu0.16.10.1/debian/flashplugin-downloader.links
./yakkety/flashplugin-nonfree-11.2.202.644ubuntu0.16.10.1/debian/flashplugin-downloader.substvars
./zesty/flashplugin-nonfree-11.2.202.644ubuntu1/debian/flashplugin-downloader
./zesty/flashplugin-nonfree-11.2.202.644ubuntu1/debian/flashplugin-downloader/usr
./zesty/flashplugin-nonfree-11.2.202.644ubuntu1/debian/flashplugin-downloader/usr/share
./zesty/flashplugin-nonfree-11.2.202.644ubuntu1/debian/flashplugin-downloader/usr/share/doc
./zesty/flashplugin-nonfree-11.2.202.644ubuntu1/debian/flashplugin-downloader/usr/share/doc/flashplugin-downloader
./zesty/flashplugin-nonfree-11.2.202.644ubuntu1/debian/flashplugin-downloader/usr/share/doc/flashplugin-downloader/copyright
./zesty/flashplugin-nonfree-11.2.202.644ubuntu1/debian/flashplugin-downloader/usr/share/doc/flashplugin-downloader/changelog.gz
./zesty/flashplugin-nonfree-11.2.202.644ubuntu1/debian/flashplugin-downloader/DEBIAN
./zesty/flashplugin-nonfree-11.2.202.644ubuntu1/debian/flashplugin-downloader/DEBIAN/control
./zesty/flashplugin-nonfree-11.2.202.644ubuntu1/debian/flashplugin-downloader/DEBIAN/md5sums
./zesty/flashplugin-nonfree-11.2.202.644ubuntu1/debian/flashplugin-downloader.links
./zesty/flashplugin-nonfree-11.2.202.644ubuntu1/debian/flashplugin-downloader.substvars
./xenial/flashplugin-nonfree-11.2.202.644ubuntu0.16.04.1/debian/flashplugin-downloader
./xenial/flashplugin-nonfree-11.2.202.644ubuntu0.16.04.1/debian/flashplugin-downloader/usr
./xenial/flashplugin-nonfree-11.2.202.644ubuntu0.16.04.1/debian/flashplugin-downloader/usr/share
./xenial/flashplugin-nonfree-11.2.202.644ubuntu0.16.04.1/debian/flashplugin-downloader/usr/share/doc
./xenial/flashplugin-nonfree-11.2.202.644ubuntu0.16.04.1/debian/flashplugin-downloader/usr/share/doc/flashplugin-downloader
./xenial/flashplugin-nonfree-11.2.202.644ubuntu0.16.04.1/debian/flashplugin-downloader/usr/share/doc/flashplugin-downloader/copyright
./xenial/flashplugin-nonfree-11.2.202.644ubuntu0.16.04.1/debian/flashplugin-downloader/usr/share/doc/flashplugin-downloader/changelog.gz
./xenial/flashplugin-nonfree-11.2.202.644ubuntu0.16.04.1/debian/flashplugin-downloader/DEBIAN
./xenial/flashplugin-nonfree-11.2.202.644ubuntu0.16.04.1/debian/flashplugin-downloader/DEBIAN/control
./xenial/flashplugin-nonfree-11.2.202.644ubuntu0.16.04.1/debian/flashplugin-downloader/DEBIAN/md5sums
./xenial/flashplugin-nonfree-11.2.202.644ubuntu0.16.04.1/debian/flashplugin-downloader.lin

[Desktop-packages] [Bug 1648616] Re: Firefox uses its own version of NSS, incompatible with system version

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

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

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to thunderbird in Ubuntu.
https://bugs.launchpad.net/bugs/1648616

Title:
  Firefox uses its own version of NSS, incompatible with system version

Status in firefox package in Ubuntu:
  Invalid
Status in thunderbird package in Ubuntu:
  Confirmed

Bug description:
  Because of bug 1647285 I need to install corporate SSL CAs into the
  database of each NSS-using application individually. Unfortunately it
  doesn't seem to work for Firefox. Not only does Firefox ship with its
  *own* version of NSS instead using the system's version, but it even
  seems to be configured very differently.

  Firefox appears to use the legacy Berkeley DB database for its
  softokn, in key3.db/cert8.db. However, the system's certutil won't
  work with that legacy format:

  $ certutil -d ~/.mozilla/firefox/default.default/ -L
  certutil: function failed: SEC_ERROR_LEGACY_DATABASE: The certificate/key 
database is in an old, unsupported format.

  I can force it to use the SQL database in key4.db/cert9.db by running
  with NSS_DEFAULT_DB_TYPE=sql, and then I *can* install trusted CAs
  with certutil. But actually, it's much simpler to just make a symlink
  from firefox's own special copy of the SSL trust roots in
  libnssckbi.so, to the system's p11-kit-trust.so — thus making Firefox
  honour the system trust configuration.

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

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

[Desktop-packages] [Bug 1649428] [NEW] Cannot open file from https location (URL)

2016-12-12 Thread Andreas Schildbach

*** This bug is a security vulnerability ***

Public security bug reported:

If I try, I get this GIMP message:

  Opening 'https://[...]' failed:

  Could not load 'https://[...]': Failed to open file 'https://[...]':
open() failed: No such file or directory

Most of the time, I can manually edit the URL to read http://[...] and I
can open the document as expected.

The bug is a security vulnerability because it forces users to use
unsecure communication.

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

$ apt-cache policy gimp
gimp:
  Installed: 2.8.16-1ubuntu1.1
  Candidate: 2.8.16-1ubuntu1.1
  Version table:
 *** 2.8.16-1ubuntu1.1 500
500 http://archive.ubuntu.com/ubuntu xenial-updates/universe amd64 
Packages
500 http://archive.ubuntu.com/ubuntu xenial-security/universe amd64 
Packages
100 /var/lib/dpkg/status
 2.8.16-1ubuntu1 500
500 http://archive.ubuntu.com/ubuntu xenial/universe amd64 Packages

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

** Information type changed from Private Security to Public Security

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gimp in Ubuntu.
https://bugs.launchpad.net/bugs/1649428

Title:
  Cannot open file from https location (URL)

Status in gimp package in Ubuntu:
  New

Bug description:
  If I try, I get this GIMP message:

Opening 'https://[...]' failed:

Could not load 'https://[...]': Failed to open file 'https://[...]':
  open() failed: No such file or directory

  Most of the time, I can manually edit the URL to read http://[...] and
  I can open the document as expected.

  The bug is a security vulnerability because it forces users to use
  unsecure communication.

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

  $ apt-cache policy gimp
  gimp:
Installed: 2.8.16-1ubuntu1.1
Candidate: 2.8.16-1ubuntu1.1
Version table:
   *** 2.8.16-1ubuntu1.1 500
  500 http://archive.ubuntu.com/ubuntu xenial-updates/universe amd64 
Packages
  500 http://archive.ubuntu.com/ubuntu xenial-security/universe amd64 
Packages
  100 /var/lib/dpkg/status
   2.8.16-1ubuntu1 500
  500 http://archive.ubuntu.com/ubuntu xenial/universe amd64 Packages

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

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

[Desktop-packages] [Bug 1546636] Re: Review "System Applications"

2016-12-12 Thread AsciiWolf

Any progress regarding this issue?

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-software in Ubuntu.
https://bugs.launchpad.net/bugs/1546636

Title:
  Review "System Applications"

Status in GNOME Software:
  Fix Released
Status in gnome-software package in Ubuntu:
  Triaged

Bug description:
  GNOME Software has a concept of "System Applications" that cannot be
  removed / installed. The current list was defined for GNOME, we should
  update it to be appropriate for Ubuntu.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-software/+bug/1546636/+subscriptions

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

[Desktop-packages] [Bug 1633162] Re: Files application throws an error 'Oops! Something went wrong' when clicked on 'Recents'

2016-12-12 Thread Bug Watch Updater

** Changed in: nautilus
   Status: Incomplete => Confirmed

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/1633162

Title:
  Files application throws an error 'Oops! Something went wrong' when
  clicked on 'Recents'

Status in Nautilus:
  Confirmed
Status in nautilus package in Ubuntu:
  Confirmed

Bug description:
  The application crashes every time I click on 'Recent' with this
  message in a pop-up window:

  "Unhandled error message: Message recipient disconnected from message
  bus without replying."

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: nautilus 1:3.20.3-1ubuntu3
  ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
  Uname: Linux 4.8.0-22-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Oct 13 22:34:57 2016
  ExecutablePath: /usr/bin/nautilus
  GsettingsChanges:
   b'org.gnome.nautilus.preferences' b'enable-interactive-search' b'false'
   b'org.gnome.nautilus.window-state' b'geometry' b"'890x550+476+24'"
  InstallationDate: Installed on 2016-10-13 (0 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_nautilus: gnome-terminal 3.20.2-1ubuntu5

To manage notifications about this bug go to:
https://bugs.launchpad.net/nautilus/+bug/1633162/+subscriptions

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

[Desktop-packages] [Bug 1640451] Re: ksplashqml crashed with SIGABRT in QMessageLogger::fatal()

2016-12-12 Thread Oleksandr Pikozh

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

I discovered this is duplicate of #1639180.

** This bug has been marked a duplicate of bug 1639180
   no login possible after update to nvidia 304.132

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nvidia-graphics-drivers-304 in Ubuntu.
https://bugs.launchpad.net/bugs/1640451

Title:
  ksplashqml crashed with SIGABRT in QMessageLogger::fatal()

Status in nvidia-graphics-drivers-304 package in Ubuntu:
  Confirmed
Status in plasma-workspace package in Ubuntu:
  Confirmed

Bug description:
  I'm unable to start plasma after nvidia nvidia-304 package upgrade
  (and reboot).

  The related KDE bug report is (at least, KDE crash handler (DrKonqi) 
considered my report a duplicate): https://bugs.kde.org/show_bug.cgi?id=372229.
  However, I discovered that the crash is caused by upgrade to 
nvidia-304=304.132-0ubuntu0.16.04.2 (with nvidia-304=304.131-0ubuntu3 it 
worked).

  Current version of packages make my system unusable at all:
  - With nvidia-304, nvidia-opencl-icd-304, nvidia-settings packages installed 
(and xserver-xorg-video-nouveau purged) I perceive the currently described bug.
  - With xserver-xorg-video-nouveau package installed (and nvidia-304, 
nvidia-opencl-icd-304, nvidia-settings purged) the video isn't working at all 
(colorful screen and system hang).
  - With all them purged session starts and seems to work fine, but them 
crashes every 5-20mins (probably, I'll fill a separate report for that).

  1) lsb_release -rd
  Description:Ubuntu 16.04.1 LTS
  Release:16.04

  2) apt-cache policy plasma-workspace nvidia-304 nvidia-opencl-icd-304 
nvidia-settings
  plasma-workspace:
    Installed: 4:5.5.5.2-0ubuntu1
    Candidate: 4:5.5.5.2-0ubuntu1
    Version table:
   *** 4:5.5.5.2-0ubuntu1 500
  500 http://ua.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages
  100 /var/lib/dpkg/status
  nvidia-304:
    Installed: 304.132-0ubuntu0.16.04.2
    Candidate: 304.132-0ubuntu0.16.04.2
    Version table:
   *** 304.132-0ubuntu0.16.04.2 500
  500 http://ua.archive.ubuntu.com/ubuntu xenial-updates/restricted 
amd64 Packages
  500 http://security.ubuntu.com/ubuntu xenial-security/restricted 
amd64 Packages
   304.131-0ubuntu3 500
  500 http://ua.archive.ubuntu.com/ubuntu xenial/restricted amd64 
Packages
  nvidia-opencl-icd-304:
    Installed: 304.132-0ubuntu0.16.04.2
    Candidate: 304.132-0ubuntu0.16.04.2
    Version table:
   *** 304.132-0ubuntu0.16.04.2 500
  500 http://ua.archive.ubuntu.com/ubuntu xenial-updates/restricted 
amd64 Packages
  500 http://security.ubuntu.com/ubuntu xenial-security/restricted 
amd64 Packages
   304.131-0ubuntu3 500
  500 http://ua.archive.ubuntu.com/ubuntu xenial/restricted amd64 
Packages
  nvidia-settings:
    Installed: 361.42-0ubuntu1
    Candidate: 361.42-0ubuntu1
    Version table:
   *** 361.42-0ubuntu1 500
  500 http://ua.archive.ubuntu.com/ubuntu xenial/main amd64 Packages

  3) I expected plasma to start normally on system start-up (I use
  autologin) and/or on manual execution of 'sudo service sddm start' in
  first console (assuming sddm was previously shut down).

  4) Black screen for a second, then 5 or more cascaded windows of KDE
  crash handler.

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: plasma-workspace 4:5.5.5.2-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21
  Uname: Linux 4.4.0-45-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Wed Nov  9 12:17:49 2016
  ExecutablePath: /usr/bin/ksplashqml
  ExecutableTimestamp: 1460701605
  InstallationDate: Installed on 2015-11-10 (364 days ago)
  InstallationMedia: Kubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151110)
  ProcCmdline: ksplashqml Breeze --pid
  ProcCwd: /home/user
  Signal: 6
  SourcePackage: plasma-workspace
  StacktraceTop:
   qt_message_fatal (context=..., message=) at 
global/qlogging.cpp:1578
   QMessageLogger::fatal (this=this@entry=0x7fffdc604b30, 
msg=msg@entry=0x7f92c2e932c5 "%s") at global/qlogging.cpp:781
   QSGRenderLoop::handleContextCreationFailure (this=this@entry=0xec5920, 
window=0xec8f40, isEs=isEs@entry=false) at scenegraph/qsgrenderloop.cpp:244
   QSGThreadedRenderLoop::handleExposure (this=this@entry=0xec5920, 
window=window@entry=0xec8f40) at scenegraph/qsgthreadedrenderloop.cpp:919
   QSGThreadedRenderLoop::exposureChanged (this=0xec5920, window=0xec8f40) at 
scenegraph/qsgthreadedrenderloop.cpp:857
  Title: ksplashqml crashed with SIGABRT in qt_message_fatal()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304/+bug/1640451/+subscriptions

--

[Desktop-packages] [Bug 1640451] Re: ksplashqml crashed with SIGABRT in QMessageLogger::fatal()

2016-12-12 Thread Oleksandr Pikozh

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

@frautukka, I'm not experienced in this...

Propositions:
(a) Report upstream? (I reported upstream to KDE, but they say it's not their 
issue; IMHO, they're right. We should report upstream to nvidia.)
(b) Publish 304.131 version until fixed 304.133 will be released upstream.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nvidia-graphics-drivers-304 in Ubuntu.
https://bugs.launchpad.net/bugs/1640451

Title:
  ksplashqml crashed with SIGABRT in QMessageLogger::fatal()

Status in nvidia-graphics-drivers-304 package in Ubuntu:
  Confirmed
Status in plasma-workspace package in Ubuntu:
  Confirmed

Bug description:
  I'm unable to start plasma after nvidia nvidia-304 package upgrade
  (and reboot).

  The related KDE bug report is (at least, KDE crash handler (DrKonqi) 
considered my report a duplicate): https://bugs.kde.org/show_bug.cgi?id=372229.
  However, I discovered that the crash is caused by upgrade to 
nvidia-304=304.132-0ubuntu0.16.04.2 (with nvidia-304=304.131-0ubuntu3 it 
worked).

  Current version of packages make my system unusable at all:
  - With nvidia-304, nvidia-opencl-icd-304, nvidia-settings packages installed 
(and xserver-xorg-video-nouveau purged) I perceive the currently described bug.
  - With xserver-xorg-video-nouveau package installed (and nvidia-304, 
nvidia-opencl-icd-304, nvidia-settings purged) the video isn't working at all 
(colorful screen and system hang).
  - With all them purged session starts and seems to work fine, but them 
crashes every 5-20mins (probably, I'll fill a separate report for that).

  1) lsb_release -rd
  Description:Ubuntu 16.04.1 LTS
  Release:16.04

  2) apt-cache policy plasma-workspace nvidia-304 nvidia-opencl-icd-304 
nvidia-settings
  plasma-workspace:
    Installed: 4:5.5.5.2-0ubuntu1
    Candidate: 4:5.5.5.2-0ubuntu1
    Version table:
   *** 4:5.5.5.2-0ubuntu1 500
  500 http://ua.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages
  100 /var/lib/dpkg/status
  nvidia-304:
    Installed: 304.132-0ubuntu0.16.04.2
    Candidate: 304.132-0ubuntu0.16.04.2
    Version table:
   *** 304.132-0ubuntu0.16.04.2 500
  500 http://ua.archive.ubuntu.com/ubuntu xenial-updates/restricted 
amd64 Packages
  500 http://security.ubuntu.com/ubuntu xenial-security/restricted 
amd64 Packages
   304.131-0ubuntu3 500
  500 http://ua.archive.ubuntu.com/ubuntu xenial/restricted amd64 
Packages
  nvidia-opencl-icd-304:
    Installed: 304.132-0ubuntu0.16.04.2
    Candidate: 304.132-0ubuntu0.16.04.2
    Version table:
   *** 304.132-0ubuntu0.16.04.2 500
  500 http://ua.archive.ubuntu.com/ubuntu xenial-updates/restricted 
amd64 Packages
  500 http://security.ubuntu.com/ubuntu xenial-security/restricted 
amd64 Packages
   304.131-0ubuntu3 500
  500 http://ua.archive.ubuntu.com/ubuntu xenial/restricted amd64 
Packages
  nvidia-settings:
    Installed: 361.42-0ubuntu1
    Candidate: 361.42-0ubuntu1
    Version table:
   *** 361.42-0ubuntu1 500
  500 http://ua.archive.ubuntu.com/ubuntu xenial/main amd64 Packages

  3) I expected plasma to start normally on system start-up (I use
  autologin) and/or on manual execution of 'sudo service sddm start' in
  first console (assuming sddm was previously shut down).

  4) Black screen for a second, then 5 or more cascaded windows of KDE
  crash handler.

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: plasma-workspace 4:5.5.5.2-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21
  Uname: Linux 4.4.0-45-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Wed Nov  9 12:17:49 2016
  ExecutablePath: /usr/bin/ksplashqml
  ExecutableTimestamp: 1460701605
  InstallationDate: Installed on 2015-11-10 (364 days ago)
  InstallationMedia: Kubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151110)
  ProcCmdline: ksplashqml Breeze --pid
  ProcCwd: /home/user
  Signal: 6
  SourcePackage: plasma-workspace
  StacktraceTop:
   qt_message_fatal (context=..., message=) at 
global/qlogging.cpp:1578
   QMessageLogger::fatal (this=this@entry=0x7fffdc604b30, 
msg=msg@entry=0x7f92c2e932c5 "%s") at global/qlogging.cpp:781
   QSGRenderLoop::handleContextCreationFailure (this=this@entry=0xec5920, 
window=0xec8f40, isEs=isEs@entry=false) at scenegraph/qsgrenderloop.cpp:244
   QSGThreadedRenderLoop::handleExposure (this=this@entry=0xec5920, 
window=window@entry=0xec8f40) at scenegraph/qsgthreadedrenderloop.cpp:919
   QSGThreadedRenderLoop::exposureChanged (this=0xec5920, window=0xec8f40) at 
scenegraph/qsgthreadedrenderloop.cpp:857
  Title: ksplashqml crashed with SIGABRT in qt_message_fatal()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo

To manage notificatio

[Desktop-packages] [Bug 1640451] Re: ksplashqml crashed with SIGABRT in QMessageLogger::fatal()

2016-12-12 Thread Frau Tukka

I experienced the same issue. The instructions in comment #11 helped to
resolve it for now. Not quite sure what to do for the future of this
package?

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nvidia-graphics-drivers-304 in Ubuntu.
https://bugs.launchpad.net/bugs/1640451

Title:
  ksplashqml crashed with SIGABRT in QMessageLogger::fatal()

Status in nvidia-graphics-drivers-304 package in Ubuntu:
  Confirmed
Status in plasma-workspace package in Ubuntu:
  Confirmed

Bug description:
  I'm unable to start plasma after nvidia nvidia-304 package upgrade
  (and reboot).

  The related KDE bug report is (at least, KDE crash handler (DrKonqi) 
considered my report a duplicate): https://bugs.kde.org/show_bug.cgi?id=372229.
  However, I discovered that the crash is caused by upgrade to 
nvidia-304=304.132-0ubuntu0.16.04.2 (with nvidia-304=304.131-0ubuntu3 it 
worked).

  Current version of packages make my system unusable at all:
  - With nvidia-304, nvidia-opencl-icd-304, nvidia-settings packages installed 
(and xserver-xorg-video-nouveau purged) I perceive the currently described bug.
  - With xserver-xorg-video-nouveau package installed (and nvidia-304, 
nvidia-opencl-icd-304, nvidia-settings purged) the video isn't working at all 
(colorful screen and system hang).
  - With all them purged session starts and seems to work fine, but them 
crashes every 5-20mins (probably, I'll fill a separate report for that).

  1) lsb_release -rd
  Description:Ubuntu 16.04.1 LTS
  Release:16.04

  2) apt-cache policy plasma-workspace nvidia-304 nvidia-opencl-icd-304 
nvidia-settings
  plasma-workspace:
    Installed: 4:5.5.5.2-0ubuntu1
    Candidate: 4:5.5.5.2-0ubuntu1
    Version table:
   *** 4:5.5.5.2-0ubuntu1 500
  500 http://ua.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages
  100 /var/lib/dpkg/status
  nvidia-304:
    Installed: 304.132-0ubuntu0.16.04.2
    Candidate: 304.132-0ubuntu0.16.04.2
    Version table:
   *** 304.132-0ubuntu0.16.04.2 500
  500 http://ua.archive.ubuntu.com/ubuntu xenial-updates/restricted 
amd64 Packages
  500 http://security.ubuntu.com/ubuntu xenial-security/restricted 
amd64 Packages
   304.131-0ubuntu3 500
  500 http://ua.archive.ubuntu.com/ubuntu xenial/restricted amd64 
Packages
  nvidia-opencl-icd-304:
    Installed: 304.132-0ubuntu0.16.04.2
    Candidate: 304.132-0ubuntu0.16.04.2
    Version table:
   *** 304.132-0ubuntu0.16.04.2 500
  500 http://ua.archive.ubuntu.com/ubuntu xenial-updates/restricted 
amd64 Packages
  500 http://security.ubuntu.com/ubuntu xenial-security/restricted 
amd64 Packages
   304.131-0ubuntu3 500
  500 http://ua.archive.ubuntu.com/ubuntu xenial/restricted amd64 
Packages
  nvidia-settings:
    Installed: 361.42-0ubuntu1
    Candidate: 361.42-0ubuntu1
    Version table:
   *** 361.42-0ubuntu1 500
  500 http://ua.archive.ubuntu.com/ubuntu xenial/main amd64 Packages

  3) I expected plasma to start normally on system start-up (I use
  autologin) and/or on manual execution of 'sudo service sddm start' in
  first console (assuming sddm was previously shut down).

  4) Black screen for a second, then 5 or more cascaded windows of KDE
  crash handler.

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: plasma-workspace 4:5.5.5.2-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21
  Uname: Linux 4.4.0-45-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Wed Nov  9 12:17:49 2016
  ExecutablePath: /usr/bin/ksplashqml
  ExecutableTimestamp: 1460701605
  InstallationDate: Installed on 2015-11-10 (364 days ago)
  InstallationMedia: Kubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151110)
  ProcCmdline: ksplashqml Breeze --pid
  ProcCwd: /home/user
  Signal: 6
  SourcePackage: plasma-workspace
  StacktraceTop:
   qt_message_fatal (context=..., message=) at 
global/qlogging.cpp:1578
   QMessageLogger::fatal (this=this@entry=0x7fffdc604b30, 
msg=msg@entry=0x7f92c2e932c5 "%s") at global/qlogging.cpp:781
   QSGRenderLoop::handleContextCreationFailure (this=this@entry=0xec5920, 
window=0xec8f40, isEs=isEs@entry=false) at scenegraph/qsgrenderloop.cpp:244
   QSGThreadedRenderLoop::handleExposure (this=this@entry=0xec5920, 
window=window@entry=0xec8f40) at scenegraph/qsgthreadedrenderloop.cpp:919
   QSGThreadedRenderLoop::exposureChanged (this=0xec5920, window=0xec8f40) at 
scenegraph/qsgthreadedrenderloop.cpp:857
  Title: ksplashqml crashed with SIGABRT in qt_message_fatal()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304/+bug/1640451/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.l

[Desktop-packages] [Bug 1629611] Re: dns server priority broken

2016-12-12 Thread Thomas M Steenholdt

Unfortunately not much traction here, and this appears to annoy people
across distros.

In the meantime, an ugly hack is to manually add all internal domains to
the NetworkManager VPN config file's dns-search= parameter:

dns-search=domain1.lan;domain2.lan;domain3.lan;example.com;

This causes NetworkManager to split DNS all lookups for these domains to
the VPN DNS server, but with the added overhead of searching through all
domains for non-existing hostname queries (make sure the primary
internal domains are mentioned first). Also, for a multi-city setup like
ours, I need to add A LOT of domains to get a functional DNS while on
VPN - Including in-addr.arpa specifications for all IP subnets.

So there's a way to sweeten the deal - but this is by no means anything
other than a hack.

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

Title:
  dns server priority broken

Status in NetworkManager-OpenVPN:
  New
Status in network-manager-vpnc:
  New
Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  network-manager: 1.2.4-0ubuntu1

  
  Yakkety appears to have switched back from resolved to dnsmasq, but it seems 
server priority/order is broken.

  Example: In split DNS setups, connecting to VPN will not cause us to
  query the DNS provided by the VPN first (or only), which should be the
  proper way to resolve names in that case.

  Say server.example.com in the public DNS resolves to a.a.a.a and in
  the private DNS resolves to b.b.b.b.

  Stuff would work from my normal internet-connection, but connection to
  VPN would cause stuff to misbehave. I expect to hit the b.b.b.b
  address but since my normal LAN DNS is being used first, I'm really
  hitting a.a.a.a.

  Please let me know how to proceed - Hopefully this can be fixed in
  time for release.

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager-openvpn/+bug/1629611/+subscriptions

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

[Desktop-packages] [Bug 1641380] Re: chromium-browser: ERR_CERTIFICATE_TRANSPARENCY_REQUIRED for Symantec certs

2016-12-12 Thread Eloquence

That did the trick. Thank you, Dandapani! For those still experiencing
the issue, try following the instructions in #11 / #82. This will fix it
for sites using the Symantec CA but not for the GeoTrust ones e.g. #32.
Does anyone have a link handy for importing the Geotrust CA?

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1641380

Title:
  chromium-browser: ERR_CERTIFICATE_TRANSPARENCY_REQUIRED for Symantec
  certs

Status in chromium-browser package in Ubuntu:
  In Progress

Bug description:
  Chromium browser in xenial no longer trusts Symantec issued
  certificates. See [1].

  1. https://bugs.chromium.org/p/chromium/issues/detail?id=664177

  Ubuntu release: 16.04
  chromium-browser: 53.0.2785.143-0ubuntu0.16.04.1.1254

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1641380/+subscriptions

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

[Desktop-packages] [Bug 998955] Re: Printer Window is corrupt.

2016-12-12 Thread Rodney Dawes

** Package changed: indicator-printers (Ubuntu) => system-config-printer
(Ubuntu)

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to system-config-printer in Ubuntu.
https://bugs.launchpad.net/bugs/998955

Title:
  Printer Window is corrupt.

Status in system-config-printer package in Ubuntu:
  New

Bug description:
  See file attached. My printer has plenty of ink. No problem in all
  previous versions of Ubuntu. I have six ink cartridges but see
  attachment how they are displayed. I use Unity 2D due to well known
  NVidia problem but same display appears in Unity 3D. I upgraded to
  12.04 from 11.10.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: indicator-printers 0.1.6-0ubuntu1
  ProcVersionSignature: Ubuntu 3.2.0-24.37-generic 3.2.14
  Uname: Linux 3.2.0-24-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.0.1-0ubuntu7
  Architecture: amd64
  Date: Mon May 14 12:34:45 2012
  ExecutablePath: /usr/lib/indicator-printers/indicator-printers-service
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
  ProcEnviron:
   SHELL=/bin/bash
   PATH=(custom, no user)
   LANG=en_AU.UTF-8
  SourcePackage: indicator-printers
  UpgradeStatus: Upgraded to precise on 2012-05-03 (10 days ago)
  XsessionErrors:
   (gnome-settings-daemon:30727): color-plugin-WARNING **: failed to get edid: 
unable to get EDID for output
   (gnome-settings-daemon:30727): color-plugin-WARNING **: unable to get EDID 
for xrandr-default: unable to get EDID for output
   (gnome-settings-daemon:30727): color-plugin-WARNING **: failed to reset 
xrandr-default gamma tables: gamma size is zero
   (gnome-settings-daemon:30727): color-plugin-WARNING **: unable to get EDID 
for xrandr-default: unable to get EDID for output
   (gnome-settings-daemon:30727): color-plugin-WARNING **: failed to reset 
xrandr-default gamma tables: gamma size is zero

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/system-config-printer/+bug/998955/+subscriptions

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

[Desktop-packages] [Bug 998955] [NEW] Printer Window is corrupt.

You have been subscribed to a public bug:

See file attached. My printer has plenty of ink. No problem in all
previous versions of Ubuntu. I have six ink cartridges but see
attachment how they are displayed. I use Unity 2D due to well known
NVidia problem but same display appears in Unity 3D. I upgraded to 12.04
from 11.10.

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: indicator-printers 0.1.6-0ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-24.37-generic 3.2.14
Uname: Linux 3.2.0-24-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.0.1-0ubuntu7
Architecture: amd64
Date: Mon May 14 12:34:45 2012
ExecutablePath: /usr/lib/indicator-printers/indicator-printers-service
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, no user)
 LANG=en_AU.UTF-8
SourcePackage: indicator-printers
UpgradeStatus: Upgraded to precise on 2012-05-03 (10 days ago)
XsessionErrors:
 (gnome-settings-daemon:30727): color-plugin-WARNING **: failed to get edid: 
unable to get EDID for output
 (gnome-settings-daemon:30727): color-plugin-WARNING **: unable to get EDID for 
xrandr-default: unable to get EDID for output
 (gnome-settings-daemon:30727): color-plugin-WARNING **: failed to reset 
xrandr-default gamma tables: gamma size is zero
 (gnome-settings-daemon:30727): color-plugin-WARNING **: unable to get EDID for 
xrandr-default: unable to get EDID for output
 (gnome-settings-daemon:30727): color-plugin-WARNING **: failed to reset 
xrandr-default gamma tables: gamma size is zero

** Affects: system-config-printer (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug precise
-- 
Printer Window is corrupt.
https://bugs.launchpad.net/bugs/998955
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to system-config-printer in Ubuntu.

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

[Desktop-packages] [Bug 1310594] Re: Lenovo Onelink Pro Dock - No audio via Dock-HDMI

2016-12-12 Thread Ray-Ven

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

** This bug has been marked a duplicate of bug 1467190
   No audio over DisplayPort MST

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

Title:
  Lenovo Onelink Pro Dock - No audio via Dock-HDMI

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Sound over Laptop HDMI works, but won't work over Dock with Kernels
  newer than 2.16 in all ubuntu releases since trusty. Persists with
  latest bios (state 16.08.16) Freshinstall makes no difference.

  
  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Mon Apr 21 14:23:10 2014
  PackageArchitecture: all
  SourcePackage: alsa-driver
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/26/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GQET34WW (1.14 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20C0S0AX00
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 Pro
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrGQET34WW(1.14):bd02/26/2014:svnLENOVO:pn20C0S0AX00:pvrThinkPadS1Yoga:rvnLENOVO:rn20C0S0AX00:rvrSDK0E50510Pro:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 20C0S0AX00
  dmi.product.version: ThinkPad S1 Yoga
  dmi.sys.vendor: LENOVO

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

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

[Desktop-packages] [Bug 1640971] Re: Evolution consumes a huge amount of ram even if it´s closed

2016-12-12 Thread Andre Klapper

Please provide steps to reproduce seeing the problem. 
When Evolution is closed and not running I don't know where I could see/check 
that it consumes 200MB...

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to evolution in Ubuntu.
https://bugs.launchpad.net/bugs/1640971

Title:
  Evolution consumes a huge amount of ram even if it´s closed

Status in evolution package in Ubuntu:
  Confirmed

Bug description:
  Evolution consumes a minimum of 200 MB even if its closed, that must
  be fixed.

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

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

[Desktop-packages] [Bug 1641380] Re: chromium-browser: ERR_CERTIFICATE_TRANSPARENCY_REQUIRED for Symantec certs

2016-12-12 Thread Dandapani

This cert is an Authorities Cert. Cut/paste into file and import as
Authorities:

https://knowledge.symantec.com/kb/index?page=content&actp=CROSSLINK&id=INFO2045

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1641380

Title:
  chromium-browser: ERR_CERTIFICATE_TRANSPARENCY_REQUIRED for Symantec
  certs

Status in chromium-browser package in Ubuntu:
  In Progress

Bug description:
  Chromium browser in xenial no longer trusts Symantec issued
  certificates. See [1].

  1. https://bugs.chromium.org/p/chromium/issues/detail?id=664177

  Ubuntu release: 16.04
  chromium-browser: 53.0.2785.143-0ubuntu0.16.04.1.1254

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1641380/+subscriptions

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

[Desktop-packages] [Bug 1310594] Re: Lenovo Onelink Pro Dock - No audio via Dock-HDMI

2016-12-12 Thread Ray-Ven

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

what a shame - still not working - tried it in xenial and yakkety again

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

Title:
  Lenovo Onelink Pro Dock - No audio via Dock-HDMI

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Sound over Laptop HDMI works, but won't work over Dock with Kernels
  newer than 2.16 in all ubuntu releases since trusty. Persists with
  latest bios (state 16.08.16) Freshinstall makes no difference.

  
  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Mon Apr 21 14:23:10 2014
  PackageArchitecture: all
  SourcePackage: alsa-driver
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/26/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GQET34WW (1.14 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20C0S0AX00
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 Pro
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrGQET34WW(1.14):bd02/26/2014:svnLENOVO:pn20C0S0AX00:pvrThinkPadS1Yoga:rvnLENOVO:rn20C0S0AX00:rvrSDK0E50510Pro:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 20C0S0AX00
  dmi.product.version: ThinkPad S1 Yoga
  dmi.sys.vendor: LENOVO

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

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

[Desktop-packages] [Bug 1590590] Re: Touchpad not recognized on Dell Latitude E7470 Ultrabook

I am using the newly released 4.9, but the same "feature"was present in
the previous rcX versions:

uname -a
Linux nbbag7 4.9.0-040900-generic #201612111631 SMP Sun Dec 11 21:33:00 UTC 
2016 x86_64 x86_64 x86_64 GNU/Linux

BTW,I am noticing now that tapping with a single finger on the lower-
right part of the trackpad is equivalent of a right-click.

So it seems that there are some default gestures on the upper/lower-right part 
that are not understood by the current driver and are enabled by default.
I don't know if this can be considered a bug

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-input-synaptics in Ubuntu.
https://bugs.launchpad.net/bugs/1590590

Title:
  Touchpad not recognized on Dell Latitude E7470 Ultrabook

Status in linux package in Ubuntu:
  Triaged
Status in xserver-xorg-input-synaptics package in Ubuntu:
  Confirmed

Bug description:
  Expected: Touchpad settings available in Mouse & Touchpad Settings
  dialog

  Actual result: Touchpad settings missing entirely

  
  Details:
  The touchpad on my Dell Ultrabook (Latitude E7470) functions mostly. 

  The settings for the touchpad are not available at all in the Mouse
  and Touchpad settings (see http://i.imgur.com/YRGiOrj.png).

  Two-finger scrolling works as expected except it's using "Natural
  Scrolling" by default and there is no way to change it.

  xinput list does not display a touchpad at all:

  ⎡ Virtual core pointerid=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ ELAN Touchscreenid=11   [slave  pointer 
 (2)]
  ⎜   ↳ ImPS/2 Generic Wheel Mouse  id=13   [slave  pointer 
 (2)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ Power Buttonid=6[slave  
keyboard (3)]
  ↳ Video Bus   id=7[slave  
keyboard (3)]
  ↳ Power Buttonid=8[slave  
keyboard (3)]
  ↳ Sleep Buttonid=9[slave  
keyboard (3)]
  ↳ Integrated_Webcam_FHD   id=10   [slave  
keyboard (3)]
  ↳ AT Translated Set 2 keyboardid=12   [slave  
keyboard (3)]
  ↳ Dell WMI hotkeysid=14   [slave  
keyboard (3)]
  ↳ DELL Wireless hotkeys   id=15   [slave  
keyboard (3)]

  
  /proc/bus/input/devices lists the device as a "Generic Wheel Mouse"

  Output of `lsb_release -rd`:
  Description:  Ubuntu 16.04 LTS
  Release:  16.04

  xserver-xorg-input-synaptics version information:
  xserver-xorg-input-synaptics:
Installed: 1.8.2-1ubuntu3
Candidate: 1.8.2-1ubuntu3
Version table:
   *** 1.8.2-1ubuntu3 500
  500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status

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

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

[Desktop-packages] [Bug 1636514] Re: nautilus crashed with SIGSEGV in gtk_tree_view_set_cursor_on_cell()

2016-12-12 Thread Kosmonaut

Similar here. Copied 2 files (2gb each) internally from folder to folder
then somehow nautilus crashed. 5min before I copied 3 files (à 2gb)
nautilus seemed to behave normally. But unfortunately cannot reproduce
this -> I restarted the PC and tried to copy the sames files again: all
worked fine.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/1636514

Title:
  nautilus crashed with SIGSEGV in gtk_tree_view_set_cursor_on_cell()

Status in Ubuntu GNOME:
  Invalid
Status in nautilus package in Ubuntu:
  Invalid

Bug description:
  This crash occurred just after I had asked Nautilus to move several
  large files (in groups) to several different locations. Then I believe
  that I minimized Nautilus and in a few minutes noticed the crash.

  ProblemType: Crash
  DistroRelease: Ubuntu 16.10
  Package: nautilus 1:3.22.1-1ubuntu0~yakkety2 [origin: 
LP-PPA-gnome3-team-gnome3-staging]
  ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0
  Uname: Linux 4.8.0-26-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Oct 25 13:52:09 2016
  ExecutablePath: /usr/bin/nautilus
  InstallationDate: Installed on 2016-05-15 (162 days ago)
  InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Release amd64 
(20151021)
  ProcCmdline: nautilus .
  Signal: 11
  SourcePackage: nautilus
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   gtk_tree_view_set_cursor_on_cell () from 
/usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? ()
   ?? ()
  Title: nautilus crashed with SIGSEGV in gtk_tree_view_set_cursor_on_cell()
  UpgradeStatus: Upgraded to yakkety on 2016-10-19 (5 days ago)
  UserGroups: adm cdrom dip libvirt libvirtd lpadmin plugdev sambashare sudo
  usr_lib_nautilus:
   dropbox2015.10.28
   gnome-terminal 3.20.2-1ubuntu5

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-gnome/+bug/1636514/+subscriptions

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

[Desktop-packages] [Bug 1590590] Re: Touchpad not recognized on Dell Latitude E7470 Ultrabook

2016-12-12 Thread Staffan Persson

I'm using rc5:
uname -a
Linux se5470 4.9.0-040900rc5-generic #201611131431 SMP Sun Nov 13 19:33:15 UTC 
2016 x86_64 x86_64 x86_64 GNU/Linux

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-input-synaptics in Ubuntu.
https://bugs.launchpad.net/bugs/1590590

Title:
  Touchpad not recognized on Dell Latitude E7470 Ultrabook

Status in linux package in Ubuntu:
  Triaged
Status in xserver-xorg-input-synaptics package in Ubuntu:
  Confirmed

Bug description:
  Expected: Touchpad settings available in Mouse & Touchpad Settings
  dialog

  Actual result: Touchpad settings missing entirely

  
  Details:
  The touchpad on my Dell Ultrabook (Latitude E7470) functions mostly. 

  The settings for the touchpad are not available at all in the Mouse
  and Touchpad settings (see http://i.imgur.com/YRGiOrj.png).

  Two-finger scrolling works as expected except it's using "Natural
  Scrolling" by default and there is no way to change it.

  xinput list does not display a touchpad at all:

  ⎡ Virtual core pointerid=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ ELAN Touchscreenid=11   [slave  pointer 
 (2)]
  ⎜   ↳ ImPS/2 Generic Wheel Mouse  id=13   [slave  pointer 
 (2)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ Power Buttonid=6[slave  
keyboard (3)]
  ↳ Video Bus   id=7[slave  
keyboard (3)]
  ↳ Power Buttonid=8[slave  
keyboard (3)]
  ↳ Sleep Buttonid=9[slave  
keyboard (3)]
  ↳ Integrated_Webcam_FHD   id=10   [slave  
keyboard (3)]
  ↳ AT Translated Set 2 keyboardid=12   [slave  
keyboard (3)]
  ↳ Dell WMI hotkeysid=14   [slave  
keyboard (3)]
  ↳ DELL Wireless hotkeys   id=15   [slave  
keyboard (3)]

  
  /proc/bus/input/devices lists the device as a "Generic Wheel Mouse"

  Output of `lsb_release -rd`:
  Description:  Ubuntu 16.04 LTS
  Release:  16.04

  xserver-xorg-input-synaptics version information:
  xserver-xorg-input-synaptics:
Installed: 1.8.2-1ubuntu3
Candidate: 1.8.2-1ubuntu3
Version table:
   *** 1.8.2-1ubuntu3 500
  500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status

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

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

Re: [Desktop-packages] [Bug 1583849] Re: Firefox > 44 is broken on all big-endian architectures

2016-12-12 Thread Fritz Hudnut

For my PPC machines I'm thinking Xenial is the "final destination" . . . on
my 933 MHz iBook, everything loads very slowly . . . not even thinking
about non-LTS options for them.

On Mon, Dec 12, 2016 at 10:36 AM, ernsteiswuerfel 
wrote:

> Yes, Firefox is in Xenial's repository but not in Yakkety's or Zesty's:
> http://packages.ubuntu.com/search?suite=zesty&arch=
> powerpc&mode=exactfilename&searchon=contents&keywords=firefox
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1583849
>
> Title:
>   Firefox > 44 is broken on all big-endian architectures
>
> Status in Mozilla Firefox:
>   Fix Released
> Status in firefox package in Ubuntu:
>   Confirmed
>
> Bug description:
>   OK, the reason I'm posting back here, running Lu 16.04 on an PPC
>   iBook, and MATE/XFCE 16.04 on a PM ST. . . did a dist-upgrade today,
>   so it now running the new "22" kernel and saw in the list of upgrades
>   new updates to FF and T-bird . . . on both machines after reboot FF
>   window frame loads . . . and then crashes . . . no data is ever filled
>   into the browser window.
>
>   The iBook error says it "doesn't have enough memory to report the
>   problem" . . . and on the PM . . . apparently it says the error report
>   was "corrupted" . . . no launchpad window opened in the browser when I
>   clicked on the "report the problem."
>
>   Tried to revert to the old kernel in the iBook several times,
>   seemingly failed to boot the old one . . . shut it down.
>
>   I went to the PM running 16.04 U-MATE and tried the same dist-upgrade
>   via console there, that upgrade was much larger than the Lu system,
>   but subsequently FF also then failed to launch w/o crashing . . .
>   installed Midori to make an apple user post, but when I tried to start
>   a new thread there Midori crashed as well.
>
>   I ran "apt-get -f install" in both the iBook & the PM . . . nothing
>   showed up. No "comment" in the terminal during the upgrade asking any
>   questions or reporting "problems" . . . but FF is kaput
>
>   I'm back in OSX 10.5 side until things cool down for the browsers in
>   16.04 PPC Lu & U-MATE/XFCE.
>
>   e...
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/firefox/+bug/1583849/+subscriptions
>

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.net/bugs/1583849

Title:
  Firefox > 44 is broken on all big-endian architectures

Status in Mozilla Firefox:
  Fix Released
Status in firefox package in Ubuntu:
  Confirmed

Bug description:
  OK, the reason I'm posting back here, running Lu 16.04 on an PPC
  iBook, and MATE/XFCE 16.04 on a PM ST. . . did a dist-upgrade today,
  so it now running the new "22" kernel and saw in the list of upgrades
  new updates to FF and T-bird . . . on both machines after reboot FF
  window frame loads . . . and then crashes . . . no data is ever filled
  into the browser window.

  The iBook error says it "doesn't have enough memory to report the
  problem" . . . and on the PM . . . apparently it says the error report
  was "corrupted" . . . no launchpad window opened in the browser when I
  clicked on the "report the problem."

  Tried to revert to the old kernel in the iBook several times,
  seemingly failed to boot the old one . . . shut it down.

  I went to the PM running 16.04 U-MATE and tried the same dist-upgrade
  via console there, that upgrade was much larger than the Lu system,
  but subsequently FF also then failed to launch w/o crashing . . .
  installed Midori to make an apple user post, but when I tried to start
  a new thread there Midori crashed as well.

  I ran "apt-get -f install" in both the iBook & the PM . . . nothing
  showed up. No "comment" in the terminal during the upgrade asking any
  questions or reporting "problems" . . . but FF is kaput

  I'm back in OSX 10.5 side until things cool down for the browsers in
  16.04 PPC Lu & U-MATE/XFCE.

  e...

To manage notifications about this bug go to:
https://bugs.launchpad.net/firefox/+bug/1583849/+subscriptions

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

[Desktop-packages] [Bug 1590590] Re: Touchpad not recognized on Dell Latitude E7470 Ultrabook

2016-12-12 Thread Adam

@p-staffan Are you also using the 4.9.x kernel (i.e. the one with the
patch so that the touchpad is recognized)?

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-input-synaptics in Ubuntu.
https://bugs.launchpad.net/bugs/1590590

Title:
  Touchpad not recognized on Dell Latitude E7470 Ultrabook

Status in linux package in Ubuntu:
  Triaged
Status in xserver-xorg-input-synaptics package in Ubuntu:
  Confirmed

Bug description:
  Expected: Touchpad settings available in Mouse & Touchpad Settings
  dialog

  Actual result: Touchpad settings missing entirely

  
  Details:
  The touchpad on my Dell Ultrabook (Latitude E7470) functions mostly. 

  The settings for the touchpad are not available at all in the Mouse
  and Touchpad settings (see http://i.imgur.com/YRGiOrj.png).

  Two-finger scrolling works as expected except it's using "Natural
  Scrolling" by default and there is no way to change it.

  xinput list does not display a touchpad at all:

  ⎡ Virtual core pointerid=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ ELAN Touchscreenid=11   [slave  pointer 
 (2)]
  ⎜   ↳ ImPS/2 Generic Wheel Mouse  id=13   [slave  pointer 
 (2)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ Power Buttonid=6[slave  
keyboard (3)]
  ↳ Video Bus   id=7[slave  
keyboard (3)]
  ↳ Power Buttonid=8[slave  
keyboard (3)]
  ↳ Sleep Buttonid=9[slave  
keyboard (3)]
  ↳ Integrated_Webcam_FHD   id=10   [slave  
keyboard (3)]
  ↳ AT Translated Set 2 keyboardid=12   [slave  
keyboard (3)]
  ↳ Dell WMI hotkeysid=14   [slave  
keyboard (3)]
  ↳ DELL Wireless hotkeys   id=15   [slave  
keyboard (3)]

  
  /proc/bus/input/devices lists the device as a "Generic Wheel Mouse"

  Output of `lsb_release -rd`:
  Description:  Ubuntu 16.04 LTS
  Release:  16.04

  xserver-xorg-input-synaptics version information:
  xserver-xorg-input-synaptics:
Installed: 1.8.2-1ubuntu3
Candidate: 1.8.2-1ubuntu3
Version table:
   *** 1.8.2-1ubuntu3 500
  500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status

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

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

[Desktop-packages] [Bug 1648982] Re: package cups-daemon 2.1.3-4 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting a removal

** Tags removed: need-duplicate-check

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1648982

Title:
  package cups-daemon 2.1.3-4 failed to install/upgrade: package is in a
  very bad inconsistent state; you should  reinstall it before
  attempting a removal

Status in cups package in Ubuntu:
  New

Bug description:
  not update successfully and package is bad

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: cups-daemon 2.1.3-4
  ProcVersionSignature: Ubuntu 4.4.0-53.74-generic 4.4.30
  Uname: Linux 4.4.0-53-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CupsErrorLog:
   
  Date: Sat Dec 10 20:41:21 2016
  DpkgHistoryLog:
   Start-Date: 2016-12-10  20:41:13
   Requested-By: ajinkya-im-possible (1000)
   Upgrade: apport:amd64 (2.20.1-0ubuntu2.1, 2.20.1-0ubuntu2.2), 
python3-apport:amd64 (2.20.1-0ubuntu2.1, 2.20.1-0ubuntu2.2), apport-gtk:amd64 
(2.20.1-0ubuntu2.1, 2.20.1-0ubuntu2.2), python3-problem-report:amd64 
(2.20.1-0ubuntu2.1, 2.20.1-0ubuntu2.2)
   Remove: printer-driver-splix:amd64 (2.0.0+svn315-4fakesync1), 
bluez-cups:amd64 (5.37-0ubuntu5), printer-driver-hpcups:amd64 
(3.16.3+repack0-1), printer-driver-postscript-hp:amd64 (3.16.3+repack0-1), 
hplip:amd64 (3.16.3+repack0-1), printer-driver-gutenprint:amd64 (5.2.11-1), 
cups-core-drivers:amd64 (2.1.3-4ubuntu0.1), cups-daemon:amd64 (2.1.3-4), 
cups:amd64 (2.1.3-4ubuntu0.1), indicator-printers:amd64 
(0.1.7+15.04.20150220-0ubuntu2)
  DuplicateSignature:
   package:cups-daemon:2.1.3-4
   Removing cups-core-drivers (2.1.3-4ubuntu0.1) ...
   dpkg: error processing package cups-daemon (--remove):
package is in a very bad inconsistent state; you should
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting a removal
  InstallationDate: Installed on 2016-12-03 (7 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No 
destinations added.
  MachineType: Sony Corporation VPCCB45FN
  Papersize: a4
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.4.0-53-generic 
root=UUID=e703e877-2af5-49c0-90d6-27a018ee1929 ro quiet splash vt.handoff=7
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-53-generic 
root=UUID=e703e877-2af5-49c0-90d6-27a018ee1929 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.15
  SourcePackage: cups
  Title: package cups-daemon 2.1.3-4 failed to install/upgrade: package is in a 
very bad inconsistent state; you should  reinstall it before attempting a 
removal
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/27/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: R2110V2
  dmi.board.asset.tag: N/A
  dmi.board.name: VAIO
  dmi.board.vendor: Sony Corporation
  dmi.board.version: N/A
  dmi.chassis.asset.tag: N/A
  dmi.chassis.type: 10
  dmi.chassis.vendor: Sony Corporation
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrR2110V2:bd09/27/2011:svnSonyCorporation:pnVPCCB45FN:pvrC60A1P3G:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A:
  dmi.product.name: VPCCB45FN
  dmi.product.version: C60A1P3G
  dmi.sys.vendor: Sony Corporation

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

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

[Desktop-packages] [Bug 1648982] Re: package cups-daemon 2.1.3-4 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting a removal

2016-12-12 Thread Emily Ratliff

** Information type changed from Private Security to Public

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1648982

Title:
  package cups-daemon 2.1.3-4 failed to install/upgrade: package is in a
  very bad inconsistent state; you should  reinstall it before
  attempting a removal

Status in cups package in Ubuntu:
  New

Bug description:
  not update successfully and package is bad

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: cups-daemon 2.1.3-4
  ProcVersionSignature: Ubuntu 4.4.0-53.74-generic 4.4.30
  Uname: Linux 4.4.0-53-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CupsErrorLog:
   
  Date: Sat Dec 10 20:41:21 2016
  DpkgHistoryLog:
   Start-Date: 2016-12-10  20:41:13
   Requested-By: ajinkya-im-possible (1000)
   Upgrade: apport:amd64 (2.20.1-0ubuntu2.1, 2.20.1-0ubuntu2.2), 
python3-apport:amd64 (2.20.1-0ubuntu2.1, 2.20.1-0ubuntu2.2), apport-gtk:amd64 
(2.20.1-0ubuntu2.1, 2.20.1-0ubuntu2.2), python3-problem-report:amd64 
(2.20.1-0ubuntu2.1, 2.20.1-0ubuntu2.2)
   Remove: printer-driver-splix:amd64 (2.0.0+svn315-4fakesync1), 
bluez-cups:amd64 (5.37-0ubuntu5), printer-driver-hpcups:amd64 
(3.16.3+repack0-1), printer-driver-postscript-hp:amd64 (3.16.3+repack0-1), 
hplip:amd64 (3.16.3+repack0-1), printer-driver-gutenprint:amd64 (5.2.11-1), 
cups-core-drivers:amd64 (2.1.3-4ubuntu0.1), cups-daemon:amd64 (2.1.3-4), 
cups:amd64 (2.1.3-4ubuntu0.1), indicator-printers:amd64 
(0.1.7+15.04.20150220-0ubuntu2)
  DuplicateSignature:
   package:cups-daemon:2.1.3-4
   Removing cups-core-drivers (2.1.3-4ubuntu0.1) ...
   dpkg: error processing package cups-daemon (--remove):
package is in a very bad inconsistent state; you should
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting a removal
  InstallationDate: Installed on 2016-12-03 (7 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No 
destinations added.
  MachineType: Sony Corporation VPCCB45FN
  Papersize: a4
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.4.0-53-generic 
root=UUID=e703e877-2af5-49c0-90d6-27a018ee1929 ro quiet splash vt.handoff=7
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-53-generic 
root=UUID=e703e877-2af5-49c0-90d6-27a018ee1929 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.15
  SourcePackage: cups
  Title: package cups-daemon 2.1.3-4 failed to install/upgrade: package is in a 
very bad inconsistent state; you should  reinstall it before attempting a 
removal
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/27/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: R2110V2
  dmi.board.asset.tag: N/A
  dmi.board.name: VAIO
  dmi.board.vendor: Sony Corporation
  dmi.board.version: N/A
  dmi.chassis.asset.tag: N/A
  dmi.chassis.type: 10
  dmi.chassis.vendor: Sony Corporation
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrR2110V2:bd09/27/2011:svnSonyCorporation:pnVPCCB45FN:pvrC60A1P3G:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A:
  dmi.product.name: VPCCB45FN
  dmi.product.version: C60A1P3G
  dmi.sys.vendor: Sony Corporation

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

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

[Desktop-packages] [Bug 1590590] Re: Touchpad not recognized on Dell Latitude E7470 Ultrabook

2016-12-12 Thread Staffan Persson

yes, I can reproduce it like this:
- open a text doc
- select some text in it
- tap in the top right corner of the touchpad
then the selected text gets pasted for every tap

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-input-synaptics in Ubuntu.
https://bugs.launchpad.net/bugs/1590590

Title:
  Touchpad not recognized on Dell Latitude E7470 Ultrabook

Status in linux package in Ubuntu:
  Triaged
Status in xserver-xorg-input-synaptics package in Ubuntu:
  Confirmed

Bug description:
  Expected: Touchpad settings available in Mouse & Touchpad Settings
  dialog

  Actual result: Touchpad settings missing entirely

  
  Details:
  The touchpad on my Dell Ultrabook (Latitude E7470) functions mostly. 

  The settings for the touchpad are not available at all in the Mouse
  and Touchpad settings (see http://i.imgur.com/YRGiOrj.png).

  Two-finger scrolling works as expected except it's using "Natural
  Scrolling" by default and there is no way to change it.

  xinput list does not display a touchpad at all:

  ⎡ Virtual core pointerid=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ ELAN Touchscreenid=11   [slave  pointer 
 (2)]
  ⎜   ↳ ImPS/2 Generic Wheel Mouse  id=13   [slave  pointer 
 (2)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ Power Buttonid=6[slave  
keyboard (3)]
  ↳ Video Bus   id=7[slave  
keyboard (3)]
  ↳ Power Buttonid=8[slave  
keyboard (3)]
  ↳ Sleep Buttonid=9[slave  
keyboard (3)]
  ↳ Integrated_Webcam_FHD   id=10   [slave  
keyboard (3)]
  ↳ AT Translated Set 2 keyboardid=12   [slave  
keyboard (3)]
  ↳ Dell WMI hotkeysid=14   [slave  
keyboard (3)]
  ↳ DELL Wireless hotkeys   id=15   [slave  
keyboard (3)]

  
  /proc/bus/input/devices lists the device as a "Generic Wheel Mouse"

  Output of `lsb_release -rd`:
  Description:  Ubuntu 16.04 LTS
  Release:  16.04

  xserver-xorg-input-synaptics version information:
  xserver-xorg-input-synaptics:
Installed: 1.8.2-1ubuntu3
Candidate: 1.8.2-1ubuntu3
Version table:
   *** 1.8.2-1ubuntu3 500
  500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status

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

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

[Desktop-packages] [Bug 1649373] [NEW] Evince cannot open HTTP link in Google Chrome or chromium-browser

2016-12-12 Thread Cerin

Public bug reported:

Links are unclickable in Evince. This is apparently the same bug as
#1282314 and #964510. This is reported fixed in every release, yet it
remains broken in every release.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: evince 3.18.2-1ubuntu4
ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24
Uname: Linux 4.4.0-47-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
CurrentDesktop: GNOME
Date: Mon Dec 12 13:31:05 2016
InstallationDate: Installed on 2015-10-20 (418 days ago)
InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
SourcePackage: evince
UpgradeStatus: Upgraded to xenial on 2016-09-16 (87 days ago)

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


** Tags: amd64 apport-bug xenial

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to evince in Ubuntu.
https://bugs.launchpad.net/bugs/1649373

Title:
  Evince cannot open HTTP link in Google Chrome or chromium-browser

Status in evince package in Ubuntu:
  New

Bug description:
  Links are unclickable in Evince. This is apparently the same bug as
  #1282314 and #964510. This is reported fixed in every release, yet it
  remains broken in every release.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: evince 3.18.2-1ubuntu4
  ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24
  Uname: Linux 4.4.0-47-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Dec 12 13:31:05 2016
  InstallationDate: Installed on 2015-10-20 (418 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  SourcePackage: evince
  UpgradeStatus: Upgraded to xenial on 2016-09-16 (87 days ago)

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

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

[Desktop-packages] [Bug 1583849] Re: Firefox > 44 is broken on all big-endian architectures

2016-12-12 Thread ernsteiswuerfel

Yes, Firefox is in Xenial's repository but not in Yakkety's or Zesty's:
http://packages.ubuntu.com/search?suite=zesty&arch=powerpc&mode=exactfilename&searchon=contents&keywords=firefox

--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.net/bugs/1583849

Title:
Firefox > 44 is broken on all big-endian architectures

Status in Mozilla Firefox:
Fix Released
Status in firefox package in Ubuntu:
Confirmed

Bug description:
OK, the reason I'm posting back here, running Lu 16.04 on an PPC
iBook, and MATE/XFCE 16.04 on a PM ST. . . did a dist-upgrade today,
so it now running the new "22" kernel and saw in the list of upgrades
new updates to FF and T-bird . . . on both machines after reboot FF
window frame loads . . . and then crashes . . . no data is ever filled
into the browser window.

The iBook error says it "doesn't have enough memory to report the
problem" . . . and on the PM . . . apparently it says the error report
was "corrupted" . . . no launchpad window opened in the browser when I
clicked on the "report the problem."

Tried to revert to the old kernel in the iBook several times,
seemingly failed to boot the old one . . . shut it down.

I went to the PM running 16.04 U-MATE and tried the same dist-upgrade
via console there, that upgrade was much larger than the Lu system,
but subsequently FF also then failed to launch w/o crashing . . .
installed Midori to make an apple user post, but when I tried to start
a new thread there Midori crashed as well.

I ran "apt-get -f install" in both the iBook & the PM . . . nothing
showed up. No "comment" in the terminal during the upgrade asking any
questions or reporting "problems" . . . but FF is kaput

I'm back in OSX 10.5 side until things cool down for the browsers in
16.04 PPC Lu & U-MATE/XFCE.

e...

To manage notifications about this bug go to:
https://bugs.launchpad.net/firefox/+bug/1583849/+subscriptions

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

[Desktop-packages] [Bug 1590590] Re: Touchpad not recognized on Dell Latitude E7470 Ultrabook

@pmonas triggered by your comment, I made some further investigation and it 
seems that the middle-click is alway triggered when I click with a single 
finger in the upper-right part of the trackpad
Please check if you find the same

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-input-synaptics in Ubuntu.
https://bugs.launchpad.net/bugs/1590590

Title:
  Touchpad not recognized on Dell Latitude E7470 Ultrabook

Status in linux package in Ubuntu:
  Triaged
Status in xserver-xorg-input-synaptics package in Ubuntu:
  Confirmed

Bug description:
  Expected: Touchpad settings available in Mouse & Touchpad Settings
  dialog

  Actual result: Touchpad settings missing entirely

  
  Details:
  The touchpad on my Dell Ultrabook (Latitude E7470) functions mostly. 

  The settings for the touchpad are not available at all in the Mouse
  and Touchpad settings (see http://i.imgur.com/YRGiOrj.png).

  Two-finger scrolling works as expected except it's using "Natural
  Scrolling" by default and there is no way to change it.

  xinput list does not display a touchpad at all:

  ⎡ Virtual core pointerid=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ ELAN Touchscreenid=11   [slave  pointer 
 (2)]
  ⎜   ↳ ImPS/2 Generic Wheel Mouse  id=13   [slave  pointer 
 (2)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ Power Buttonid=6[slave  
keyboard (3)]
  ↳ Video Bus   id=7[slave  
keyboard (3)]
  ↳ Power Buttonid=8[slave  
keyboard (3)]
  ↳ Sleep Buttonid=9[slave  
keyboard (3)]
  ↳ Integrated_Webcam_FHD   id=10   [slave  
keyboard (3)]
  ↳ AT Translated Set 2 keyboardid=12   [slave  
keyboard (3)]
  ↳ Dell WMI hotkeysid=14   [slave  
keyboard (3)]
  ↳ DELL Wireless hotkeys   id=15   [slave  
keyboard (3)]

  
  /proc/bus/input/devices lists the device as a "Generic Wheel Mouse"

  Output of `lsb_release -rd`:
  Description:  Ubuntu 16.04 LTS
  Release:  16.04

  xserver-xorg-input-synaptics version information:
  xserver-xorg-input-synaptics:
Installed: 1.8.2-1ubuntu3
Candidate: 1.8.2-1ubuntu3
Version table:
   *** 1.8.2-1ubuntu3 500
  500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status

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

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

[Desktop-packages] [Bug 1590590] Re: Touchpad not recognized on Dell Latitude E7470 Ultrabook

@pmonas yes, I think the singe tap is sometime interpreted as a middle-click. I 
can guarantee that I click with a single finger, though ...
Is someone else using the 4.9 kernel on the e7370 observing this ?

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-input-synaptics in Ubuntu.
https://bugs.launchpad.net/bugs/1590590

Title:
  Touchpad not recognized on Dell Latitude E7470 Ultrabook

Status in linux package in Ubuntu:
  Triaged
Status in xserver-xorg-input-synaptics package in Ubuntu:
  Confirmed

Bug description:
  Expected: Touchpad settings available in Mouse & Touchpad Settings
  dialog

  Actual result: Touchpad settings missing entirely

  
  Details:
  The touchpad on my Dell Ultrabook (Latitude E7470) functions mostly. 

  The settings for the touchpad are not available at all in the Mouse
  and Touchpad settings (see http://i.imgur.com/YRGiOrj.png).

  Two-finger scrolling works as expected except it's using "Natural
  Scrolling" by default and there is no way to change it.

  xinput list does not display a touchpad at all:

  ⎡ Virtual core pointerid=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ ELAN Touchscreenid=11   [slave  pointer 
 (2)]
  ⎜   ↳ ImPS/2 Generic Wheel Mouse  id=13   [slave  pointer 
 (2)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ Power Buttonid=6[slave  
keyboard (3)]
  ↳ Video Bus   id=7[slave  
keyboard (3)]
  ↳ Power Buttonid=8[slave  
keyboard (3)]
  ↳ Sleep Buttonid=9[slave  
keyboard (3)]
  ↳ Integrated_Webcam_FHD   id=10   [slave  
keyboard (3)]
  ↳ AT Translated Set 2 keyboardid=12   [slave  
keyboard (3)]
  ↳ Dell WMI hotkeysid=14   [slave  
keyboard (3)]
  ↳ DELL Wireless hotkeys   id=15   [slave  
keyboard (3)]

  
  /proc/bus/input/devices lists the device as a "Generic Wheel Mouse"

  Output of `lsb_release -rd`:
  Description:  Ubuntu 16.04 LTS
  Release:  16.04

  xserver-xorg-input-synaptics version information:
  xserver-xorg-input-synaptics:
Installed: 1.8.2-1ubuntu3
Candidate: 1.8.2-1ubuntu3
Version table:
   *** 1.8.2-1ubuntu3 500
  500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status

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

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

[Desktop-packages] [Bug 1649360] Re: identifying a partitition in fstab by PARTLABEL creates a second entry for the partition, for it's file system label

2016-12-12 Thread Dirk Bosmans

** Description changed:

  $ lsb_release -rd
  Description:  Ubuntu 16.04.1 LTS
  Release:  16.04
  
  Short story:
  When a partition has both a partition label and a filesystem label, and is 
identified in /etc/fstab by PARTLABEL= , both file manager's side pane (thunar 
on Xubuntu) and the desktop (with the setting 'icons/default icons/Removable 
Devices/Disk and Drives') show two shortcuts for the partition: one for the 
/etc/fstab entry, named as the last pathname component of the mount point in 
/etc/fstab, and a self-generated second shortcut, named after the filesystem 
label. By some seemingly random process either of both shortcuts is mounted at 
some point, preventing the other one to be mounted, EVEN when that one is 
marked as automount in /etc/fstab. If the mounted shortcut is /etc/fstab's 
PARTLABEL= entry, it is mounted to the provided /etc/fstab mount point. If the 
mounted shortcut is that for the filesystem label, it is mounted to a temporary 
directory under /media/myusername/. In either case, the other shortcut can't be 
mounted then.
  
  This behaviour makes it unpredictable through which path a partition can
  be reached. The problem is not present for partitions without a
  filesystem label, even if they are identified in /etc/fstab by
  PARTLABEL= .
  
  As a workaround I reverted back to identifying the partitions in
  /etc/fstab by UUID=, which if I am right, is a filesystem feature.
+ Identified as such, the destop and the file manager side bar show one
+ shortcut only, named after the file system label, and mounting it to the
+ /etc/fstab mount point.
  
  I read somewhere that the option to identify partitions by PARTLABEL=
  and PARTUUID= is a more recent addition to fstab-syntax, so my first
  guess is that the auto-mounting system isn't yet aware of these; it
  seems to collect and identify partitions by features (uuid or label) of
  the filesystems on them, and when comparing that to the /etc/fstab
  entries, it does not recognize them as being the same partition
  identified in /etc/fstab by it's features from the partition table.
  
  Long story:
  After using and learning linux (Xubuntu) for half a year, I decided to do the 
right thing and stop identifying partitions to be mounted by block special 
device node (/dev/sda1 to /dev/sdb4 for my setup), but by a persistent name. So 
I set out to change /etc/fstab to identify the partitions to mount by UUID=, 
and that went well and I felt safe. Only problem was that a week later, I had 
no clue which UUID is which partition, which made me uncomfortably uncertain.
  
  So I used 'parted' to name all my partitions with a meaningfull
  partition label (similar but not identical to the filesystem label that
  I had named them to with 'e2label', 'fatlabel' and 'ntfslabel'). I also
  changed /etc/fstab to reflect that, now identifying my partitions using
  the PARTLABEL= . I choose PARTLABEL= instead of LABEL=, because it
  requires more skill and privileges to change a partition label than to
  change a filesystem label.
  
  From then on, the automatic mounting behaviour became erratic. The
  desktop and the side pane of the file manager now showed 2 shortcuts for
  each partition: one named like the filesystem label, another named like
  the last path component of the mount point in /etc/fstab. When mounting
  the partition is triggered,by clicking one of both shortcuts in on
  desktop or in filemanager, or by some other process, and even with
  automount in /etc/fstab, one of the shortcuts is used for mounting the
  partition, preventing the other one to be mounted as well later.
  
  By this behaviour the same partition could be accessed at either but not
  both mount points. Either the mount point provided in /etc/fstab/, which
  is accessible in file manager under an entry named after the last path
  component of that mount point, which is linked to the full mount path.
  Either a temporary mount point which 'the system' creates in my user's
  /media/myusername/ directory, which is accessible in file manager under
  the name of the filesystem label, which again is linked to the full
  mount path.
  
  Because I find it a bit creepy to edit /etc/fstab, I did not go on to
  try identifying the partitions by LABEL= or by PARTUUID= . My guess is
  that PARTUUID= would exhibit the same problem, and LABEL= not.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: udisks2 2.1.7-1ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-53.74-generic 4.4.30
  Uname: Linux 4.4.0-53-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.2
  Architecture: amd64
  CurrentDesktop: XFCE
  CustomUdevRuleFiles: 56-hpmud.rules 60-vboxdrv.rules
  Date: Mon Dec 12 17:35:41 2016
  InstallationDate: Installed on 2016-04-07 (249 days ago)
  InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: MSI MS-7971
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-53-generic.efi.signed 
root=UUID=88e332dc-deb9-4c9c-9dfc-

[Desktop-packages] [Bug 1633824] Re: nautilus ignores trash on external drives

Hello Dylan, or anyone else affected,

Accepted glib2.0 into yakkety-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/glib2.0/2.50.2-2ubuntu1 in a few
hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Changed in: glib2.0 (Ubuntu Yakkety)
   Status: In Progress => Fix Committed

** Tags added: verification-needed

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/1633824

Title:
  nautilus ignores trash on external drives

Status in GLib:
  Fix Released
Status in Nautilus:
  Invalid
Status in glib2.0 package in Ubuntu:
  Fix Released
Status in nautilus package in Ubuntu:
  Invalid
Status in glib2.0 source package in Yakkety:
  Fix Committed
Status in nautilus source package in Yakkety:
  Invalid

Bug description:
  Using nautilus 3.20 as included in Ubuntu 16.10, I can move files to
  trash in general. However only the items removed from permanently
  installed drives shows up in the trash virtual folder. In the case of
  usb removable drives, the .Trash-1000 folder is correctly created, and
  the files are in there but the nautilus GUI does not show those files
  in its virtual trash folder.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: nautilus 1:3.20.3-1ubuntu3
  ProcVersionSignature: Ubuntu 4.8.0-25.27-generic 4.8.1
  Uname: Linux 4.8.0-25-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Oct 16 11:48:03 2016
  InstallationDate: Installed on 2016-02-19 (239 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to yakkety on 2016-10-13 (2 days ago)
  usr_lib_nautilus: gnome-terminal 3.20.2-1ubuntu5

To manage notifications about this bug go to:
https://bugs.launchpad.net/glib/+bug/1633824/+subscriptions

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

[Desktop-packages] [Bug 1638245] Re: Files in the root of a folder on another partition symlinked to user's home cannot be moved to trash because of a patch in this package

Hello Sadi, or anyone else affected,

Accepted glib2.0 into yakkety-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/glib2.0/2.50.2-2ubuntu1 in a few
hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Changed in: glib2.0 (Ubuntu Yakkety)
   Status: In Progress => Fix Committed

** Tags added: verification-needed

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to glib2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1638245

Title:
  Files in the root of a folder on another partition symlinked to user's
  home cannot be moved to trash because of a patch in this package

Status in glib2.0 package in Ubuntu:
  Fix Released
Status in glib2.0 source package in Xenial:
  New
Status in glib2.0 source package in Yakkety:
  Fix Committed

Bug description:
  [ Description ]

  Can't trash files if the directory they are in is a symlink to another
  device

  [ QA ]

  Steps:
  1. Install system and partition disk into root and data partitions
  2. create ~/Data folder, and mount data partition on it
  3. create symlinks for ~/whatever/ to ~/Data/something/
  4. delete files directly inside ~/whatever/

  What happen:
  Then Nautilus says: "File can't be put in the trash. Do you want to delete it 
immediately?".

  What should happen:
  The files moved into Trash.

  [ Regression potential ]

  The proposed fix uses g_stat instead of g_stat to follow symlinks, so
  we know where to place the trash (you can't rename() across
  filesystems). If that is wrong, then it could regress trashing other
  kinds of files.

  [ Original ]

  I'm on Ubuntu 16.10 64-bit with libglib2.0-0 version 2.50.0-1.

  I've reported this bug (or marked as "it affects me") in a couple of
  other places before I've finally discovered that this is the package
  that's causing this problem, which unfortunately has been around for a
  couple of years now.

  This bug has been reported upstream as well, but it's just taking very
  very long to arrive at a decision and take action it seems.

  Apparently one of the patches
  (https://sources.debian.net/patches/glib2.0/2.50.1-1/0001-Fix-
  trashing-on-overlayfs.patch/) which is here
  
(https://launchpad.net/ubuntu/+archive/primary/+files/glib2.0_2.50.0-1.debian.tar.xz)
  to the original package which is here
  
(https://launchpad.net/ubuntu/+archive/primary/+files/glib2.0_2.50.0.orig.tar.xz)
  is the root cause of this annoying problem.

  As I prefer keeping one patition for the root filesystem (/), one
  partition for user settings (/home) and one partition for user data
  (Documents, Downloads, Drive, Music, Pictures, Public, Videos) which
  are simply symlinked to my home folder for ease of use, I cannot move
  any file to the trash in the root of these folders when I access them
  from my home folder or nautilus sidebar.

  This problem doesn't affect folders at all, nor any other files in
  subfolders, etc.

  So I was wondering if Ubuntu devs can leave out that particular patch
  when building this package for Ubuntu - if it doesn't cause more harm,
  which I doubt.

  Otherwise, I would appreciate if I could learn how to do it myself:
  how can I (as an end-user) compile the contents of
  "glib2.0_2.50.0.orig.tar.xz" with all the patches, etc. in
  "glib2.0_2.50.0-1.debian.tar.xz" except "0001-Fix-trashing-on-
  overlayfs.patch"?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1638245/+subscriptions

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

[Desktop-packages] [Bug 1633824] Re: nautilus ignores trash on external drives

While I've accepted this into -proposed and the Test Case is rather
obvious it'd still be helpful if someone were to update the description
such that it follows the SRU template.

https://wiki.ubuntu.com/StableReleaseUpdates

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/1633824

Title:
  nautilus ignores trash on external drives

Status in GLib:
  Fix Released
Status in Nautilus:
  Invalid
Status in glib2.0 package in Ubuntu:
  Fix Released
Status in nautilus package in Ubuntu:
  Invalid
Status in glib2.0 source package in Yakkety:
  Fix Committed
Status in nautilus source package in Yakkety:
  Invalid

Bug description:
  Using nautilus 3.20 as included in Ubuntu 16.10, I can move files to
  trash in general. However only the items removed from permanently
  installed drives shows up in the trash virtual folder. In the case of
  usb removable drives, the .Trash-1000 folder is correctly created, and
  the files are in there but the nautilus GUI does not show those files
  in its virtual trash folder.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: nautilus 1:3.20.3-1ubuntu3
  ProcVersionSignature: Ubuntu 4.8.0-25.27-generic 4.8.1
  Uname: Linux 4.8.0-25-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Oct 16 11:48:03 2016
  InstallationDate: Installed on 2016-02-19 (239 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to yakkety on 2016-10-13 (2 days ago)
  usr_lib_nautilus: gnome-terminal 3.20.2-1ubuntu5

To manage notifications about this bug go to:
https://bugs.launchpad.net/glib/+bug/1633824/+subscriptions

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

[Desktop-packages] [Bug 1644320] Re: [SRU] New upstream release 2.50.1

Hello Iain, or anyone else affected,

Accepted glib2.0 into yakkety-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/glib2.0/2.50.2-2ubuntu1 in a few
hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Changed in: glib2.0 (Ubuntu Yakkety)
   Status: In Progress => Fix Committed

** Tags added: verification-needed

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to glib2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1644320

Title:
  [SRU] New upstream release 2.50.1

Status in glib2.0 package in Ubuntu:
  Fix Released
Status in glib2.0 source package in Yakkety:
  Fix Committed

Bug description:
  [ Description ]

  Upstream have released a new bugfix release.

  [ Changes ]

  From NEWS:

  Overview of changes in GLib 2.50.2
  ==

  * Bugs fixed:
   767882 Bit shift overflow (-Wshift-overflow) warning in gparam.h
   769135 External control for g_test_add/g_test_run
   769630 gfile: G_FILE_MONITOR_WATCH_MOVES was actually introduced in 2.46
   772054 Patch for glib/gspawn-win32-helper.c: unexpected behavior re 
CommandLineToArgvW()
   773303 GApplication leaks option_strings
   773344 glib-compile-resources: Fix creating depfile with other targets
  
  * Translation updates:
   French
   Galician
   German
   Lithuanian
   Norwegian bokmål
   Occitan
   Serbian
   Slovak

  
  Overview of changes in GLib 2.50.1
  ==

  * Update Unicode support to Unicode 9.0.0

  * Bugs fixed:
   662946 gunixmounts monitoring doesn't work correctly with libmount
   771591 Update to Unicode 9.0.0
   772054 glib/gspawn-win32-helper.c: unexpected behavior re 
CommandLineToArgvW()
   772255 gresolver: Mark GResolver as an abstract class
   772269 Add --version options to glib-compile-resources and 
glib-compile-schemas
   772297 completion: Complete gsettings describe
   772511 g_log_default_handler crashes windows apps with "Unspecified fatal 
err...

  * Translation updates: 
   Brazilian Portuguese
   Catalan
   Croatian
   Czech
   Danish
   Hungarian
   Italian
   Latvian 
   Polish
   Swedish

  
  [ QA, testing, regression potential ]

  Under the GNOME MRE, you can believe all bugs upstream says are fixed
  are really fixed. Just test the system and make sure there are no
  regressions (e.g. look at errors.ubuntu.com).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1644320/+subscriptions

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

[Desktop-packages] [Bug 1590590] Re: Touchpad not recognized on Dell Latitude E7470 Ultrabook

2016-12-12 Thread Adam

@bagl0312: both of those are what you'd expect from a "middle-click".
This seems somehow like a different bug (or perhaps you're inadvertently
tapping with two or three fingers and your system is set up to interpret
that as a middle-click)

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-input-synaptics in Ubuntu.
https://bugs.launchpad.net/bugs/1590590

Title:
  Touchpad not recognized on Dell Latitude E7470 Ultrabook

Status in linux package in Ubuntu:
  Triaged
Status in xserver-xorg-input-synaptics package in Ubuntu:
  Confirmed

Bug description:
  Expected: Touchpad settings available in Mouse & Touchpad Settings
  dialog

  Actual result: Touchpad settings missing entirely

  
  Details:
  The touchpad on my Dell Ultrabook (Latitude E7470) functions mostly. 

  The settings for the touchpad are not available at all in the Mouse
  and Touchpad settings (see http://i.imgur.com/YRGiOrj.png).

  Two-finger scrolling works as expected except it's using "Natural
  Scrolling" by default and there is no way to change it.

  xinput list does not display a touchpad at all:

  ⎡ Virtual core pointerid=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ ELAN Touchscreenid=11   [slave  pointer 
 (2)]
  ⎜   ↳ ImPS/2 Generic Wheel Mouse  id=13   [slave  pointer 
 (2)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ Power Buttonid=6[slave  
keyboard (3)]
  ↳ Video Bus   id=7[slave  
keyboard (3)]
  ↳ Power Buttonid=8[slave  
keyboard (3)]
  ↳ Sleep Buttonid=9[slave  
keyboard (3)]
  ↳ Integrated_Webcam_FHD   id=10   [slave  
keyboard (3)]
  ↳ AT Translated Set 2 keyboardid=12   [slave  
keyboard (3)]
  ↳ Dell WMI hotkeysid=14   [slave  
keyboard (3)]
  ↳ DELL Wireless hotkeys   id=15   [slave  
keyboard (3)]

  
  /proc/bus/input/devices lists the device as a "Generic Wheel Mouse"

  Output of `lsb_release -rd`:
  Description:  Ubuntu 16.04 LTS
  Release:  16.04

  xserver-xorg-input-synaptics version information:
  xserver-xorg-input-synaptics:
Installed: 1.8.2-1ubuntu3
Candidate: 1.8.2-1ubuntu3
Version table:
   *** 1.8.2-1ubuntu3 500
  500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status

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

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

[Desktop-packages] [Bug 1649360] [NEW] identifying a partitition in fstab by PARTLABEL creates a second entry for the partition, for it's file system label

2016-12-12 Thread Dirk Bosmans

Public bug reported:

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

Short story:
When a partition has both a partition label and a filesystem label, and is 
identified in /etc/fstab by PARTLABEL= , both file manager's side pane (thunar 
on Xubuntu) and the desktop (with the setting 'icons/default icons/Removable 
Devices/Disk and Drives') show two shortcuts for the partition: one for the 
/etc/fstab entry, named as the last pathname component of the mount point in 
/etc/fstab, and a self-generated second shortcut, named after the filesystem 
label. By some seemingly random process either of both shortcuts is mounted at 
some point, preventing the other one to be mounted, EVEN when that one is 
marked as automount in /etc/fstab. If the mounted shortcut is /etc/fstab's 
PARTLABEL= entry, it is mounted to the provided /etc/fstab mount point. If the 
mounted shortcut is that for the filesystem label, it is mounted to a temporary 
directory under /media/myusername/. In either case, the other shortcut can't be 
mounted then.

This behaviour makes it unpredictable through which path a partition can
be reached. The problem is not present for partitions without a
filesystem label, even if they are identified in /etc/fstab by
PARTLABEL= .

As a workaround I reverted back to identifying the partitions in
/etc/fstab by UUID=, which if I am right, is a filesystem feature.

I read somewhere that the option to identify partitions by PARTLABEL=
and PARTUUID= is a more recent addition to fstab-syntax, so my first
guess is that the auto-mounting system isn't yet aware of these; it
seems to collect and identify partitions by features (uuid or label) of
the filesystems on them, and when comparing that to the /etc/fstab
entries, it does not recognize them as being the same partition
identified in /etc/fstab by it's features from the partition table.

Long story:
After using and learning linux (Xubuntu) for half a year, I decided to do the 
right thing and stop identifying partitions to be mounted by block special 
device node (/dev/sda1 to /dev/sdb4 for my setup), but by a persistent name. So 
I set out to change /etc/fstab to identify the partitions to mount by UUID=, 
and that went well and I felt safe. Only problem was that a week later, I had 
no clue which UUID is which partition, which made me uncomfortably uncertain.

So I used 'parted' to name all my partitions with a meaningfull
partition label (similar but not identical to the filesystem label that
I had named them to with 'e2label', 'fatlabel' and 'ntfslabel'). I also
changed /etc/fstab to reflect that, now identifying my partitions using
the PARTLABEL= . I choose PARTLABEL= instead of LABEL=, because it
requires more skill and privileges to change a partition label than to
change a filesystem label.

>From then on, the automatic mounting behaviour became erratic. The
desktop and the side pane of the file manager now showed 2 shortcuts for
each partition: one named like the filesystem label, another named like
the last path component of the mount point in /etc/fstab. When mounting
the partition is triggered,by clicking one of both shortcuts in on
desktop or in filemanager, or by some other process, and even with
automount in /etc/fstab, one of the shortcuts is used for mounting the
partition, preventing the other one to be mounted as well later.

By this behaviour the same partition could be accessed at either but not
both mount points. Either the mount point provided in /etc/fstab/, which
is accessible in file manager under an entry named after the last path
component of that mount point, which is linked to the full mount path.
Either a temporary mount point which 'the system' creates in my user's
/media/myusername/ directory, which is accessible in file manager under
the name of the filesystem label, which again is linked to the full
mount path.

Because I find it a bit creepy to edit /etc/fstab, I did not go on to
try identifying the partitions by LABEL= or by PARTUUID= . My guess is
that PARTUUID= would exhibit the same problem, and LABEL= not.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: udisks2 2.1.7-1ubuntu1
ProcVersionSignature: Ubuntu 4.4.0-53.74-generic 4.4.30
Uname: Linux 4.4.0-53-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.2
Architecture: amd64
CurrentDesktop: XFCE
CustomUdevRuleFiles: 56-hpmud.rules 60-vboxdrv.rules
Date: Mon Dec 12 17:35:41 2016
InstallationDate: Installed on 2016-04-07 (249 days ago)
InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
MachineType: MSI MS-7971
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-53-generic.efi.signed 
root=UUID=88e332dc-deb9-4c9c-9dfc-e0afe7ad45bd ro quiet splash vt.handoff=7
SourcePackage: udisks2
Symptom: storage
Title: Internal hard disk partition cannot be mounted manually
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/25/2016
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: B.50
dmi.board.as

Re: [Desktop-packages] [Bug 1583849] Re: Firefox > 44 is broken on all big-endian architectures

2016-12-12 Thread Fritz Hudnut

Just checked my iBook/Lu 16.04, and Powermac/U-MATE 16.04, both have FF
47.0+build3-Oubur "installed" and shown as "latest version" . . . in my
MacPro/10.9 I have FF 50.0.2 "up to date."  Usually PPC is a couple
versions back, so, it looks like a tad bit more than that . . . it's fading
awaayy . . . .

F

On Sun, Dec 11, 2016 at 9:02 PM, Herminio 
wrote:

> On Monday, December 12, 2016 4:21:38 AM MST you wrote:
> > Nice to see that bug fixed upstream! Will there be new PPC-builds of
> > Firefox? ATM there are none in the repository...
> It would be nice!
>
> Herminio
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1583849
>
> Title:
>   Firefox > 44 is broken on all big-endian architectures
>
> Status in Mozilla Firefox:
>   Fix Released
> Status in firefox package in Ubuntu:
>   Confirmed
>
> Bug description:
>   OK, the reason I'm posting back here, running Lu 16.04 on an PPC
>   iBook, and MATE/XFCE 16.04 on a PM ST. . . did a dist-upgrade today,
>   so it now running the new "22" kernel and saw in the list of upgrades
>   new updates to FF and T-bird . . . on both machines after reboot FF
>   window frame loads . . . and then crashes . . . no data is ever filled
>   into the browser window.
>
>   The iBook error says it "doesn't have enough memory to report the
>   problem" . . . and on the PM . . . apparently it says the error report
>   was "corrupted" . . . no launchpad window opened in the browser when I
>   clicked on the "report the problem."
>
>   Tried to revert to the old kernel in the iBook several times,
>   seemingly failed to boot the old one . . . shut it down.
>
>   I went to the PM running 16.04 U-MATE and tried the same dist-upgrade
>   via console there, that upgrade was much larger than the Lu system,
>   but subsequently FF also then failed to launch w/o crashing . . .
>   installed Midori to make an apple user post, but when I tried to start
>   a new thread there Midori crashed as well.
>
>   I ran "apt-get -f install" in both the iBook & the PM . . . nothing
>   showed up. No "comment" in the terminal during the upgrade asking any
>   questions or reporting "problems" . . . but FF is kaput
>
>   I'm back in OSX 10.5 side until things cool down for the browsers in
>   16.04 PPC Lu & U-MATE/XFCE.
>
>   e...
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/firefox/+bug/1583849/+subscriptions
>

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.net/bugs/1583849

Title:
  Firefox > 44 is broken on all big-endian architectures

Status in Mozilla Firefox:
  Fix Released
Status in firefox package in Ubuntu:
  Confirmed

Bug description:
  OK, the reason I'm posting back here, running Lu 16.04 on an PPC
  iBook, and MATE/XFCE 16.04 on a PM ST. . . did a dist-upgrade today,
  so it now running the new "22" kernel and saw in the list of upgrades
  new updates to FF and T-bird . . . on both machines after reboot FF
  window frame loads . . . and then crashes . . . no data is ever filled
  into the browser window.

  The iBook error says it "doesn't have enough memory to report the
  problem" . . . and on the PM . . . apparently it says the error report
  was "corrupted" . . . no launchpad window opened in the browser when I
  clicked on the "report the problem."

  Tried to revert to the old kernel in the iBook several times,
  seemingly failed to boot the old one . . . shut it down.

  I went to the PM running 16.04 U-MATE and tried the same dist-upgrade
  via console there, that upgrade was much larger than the Lu system,
  but subsequently FF also then failed to launch w/o crashing . . .
  installed Midori to make an apple user post, but when I tried to start
  a new thread there Midori crashed as well.

  I ran "apt-get -f install" in both the iBook & the PM . . . nothing
  showed up. No "comment" in the terminal during the upgrade asking any
  questions or reporting "problems" . . . but FF is kaput

  I'm back in OSX 10.5 side until things cool down for the browsers in
  16.04 PPC Lu & U-MATE/XFCE.

  e...

To manage notifications about this bug go to:
https://bugs.launchpad.net/firefox/+bug/1583849/+subscriptions

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

[Desktop-packages] [Bug 1648568] Re: The 'Details' panel in unity-control-center fails to load, libicu52 not present

2016-12-12 Thread Marc Ordinas i Llopis

$ ldd /usr/lib/x86_64-linux-gnu/unity-control-center-1/panels/libinfo.so | grep 
webkit
libwebkit2gtk-4.0.so.37 => /usr/local/lib/libwebkit2gtk-4.0.so.37 
(0x7f279b2e5000)

And that was the problem, somehow I got a libwebkit2gtk in /usr/local. I
removed it and now everything works as expected.

Thanks for helping me debug it, and sorry I've wasted your time!

** Changed in: unity-control-center (Ubuntu)
   Status: Incomplete => Invalid

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to unity-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1648568

Title:
  The 'Details' panel in unity-control-center fails to load, libicu52
  not present

Status in unity-control-center package in Ubuntu:
  Invalid

Bug description:
  When clicking on the 'Details' button in unity-control-center, nothing
  happens. After that, trying to close the application just relaunches
  it.

  From the command line:
  $ unity-control-center 
  libicui18n.so.52: cannot open shared object file: No such file or directory
  Failed to load module: 
/usr/lib/x86_64-linux-gnu/unity-control-center-1/panels/libinfo.so

  (clicking on details)

  libicui18n.so.52: cannot open shared object file: No such file or directory
  Failed to load module: 
/usr/lib/x86_64-linux-gnu/unity-control-center-1/panels/libinfo.so
  libicui18n.so.52: cannot open shared object file: No such file or directory
  Failed to load module: 
/usr/lib/x86_64-linux-gnu/unity-control-center-1/panels/libinfo.so

  (repeated until killed)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-control-center/+bug/1648568/+subscriptions

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

[Desktop-packages] [Bug 1590590] Re: Touchpad not recognized on Dell Latitude E7470 Ultrabook

Hi,
I am using since a few weeks the kernel 4.9 with my dell e7370 abd the touchpad 
is recognized.

I have however an annoying problem which happens quite often.

With the "tap to click" option enabled, when I tap the touchpad sometime
the behavior is quite unreliable.

For example:

1) Tapping on a tab of the chrome browser close the tab (instead of selecting 
it)
2) Tapping on a text entering field works as a "paste", instead of simply 
activating the field 

Is someone else observing this problem?

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-input-synaptics in Ubuntu.
https://bugs.launchpad.net/bugs/1590590

Title:
  Touchpad not recognized on Dell Latitude E7470 Ultrabook

Status in linux package in Ubuntu:
  Triaged
Status in xserver-xorg-input-synaptics package in Ubuntu:
  Confirmed

Bug description:
  Expected: Touchpad settings available in Mouse & Touchpad Settings
  dialog

  Actual result: Touchpad settings missing entirely

  
  Details:
  The touchpad on my Dell Ultrabook (Latitude E7470) functions mostly. 

  The settings for the touchpad are not available at all in the Mouse
  and Touchpad settings (see http://i.imgur.com/YRGiOrj.png).

  Two-finger scrolling works as expected except it's using "Natural
  Scrolling" by default and there is no way to change it.

  xinput list does not display a touchpad at all:

  ⎡ Virtual core pointerid=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ ELAN Touchscreenid=11   [slave  pointer 
 (2)]
  ⎜   ↳ ImPS/2 Generic Wheel Mouse  id=13   [slave  pointer 
 (2)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ Power Buttonid=6[slave  
keyboard (3)]
  ↳ Video Bus   id=7[slave  
keyboard (3)]
  ↳ Power Buttonid=8[slave  
keyboard (3)]
  ↳ Sleep Buttonid=9[slave  
keyboard (3)]
  ↳ Integrated_Webcam_FHD   id=10   [slave  
keyboard (3)]
  ↳ AT Translated Set 2 keyboardid=12   [slave  
keyboard (3)]
  ↳ Dell WMI hotkeysid=14   [slave  
keyboard (3)]
  ↳ DELL Wireless hotkeys   id=15   [slave  
keyboard (3)]

  
  /proc/bus/input/devices lists the device as a "Generic Wheel Mouse"

  Output of `lsb_release -rd`:
  Description:  Ubuntu 16.04 LTS
  Release:  16.04

  xserver-xorg-input-synaptics version information:
  xserver-xorg-input-synaptics:
Installed: 1.8.2-1ubuntu3
Candidate: 1.8.2-1ubuntu3
Version table:
   *** 1.8.2-1ubuntu3 500
  500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status

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

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

[Desktop-packages] [Bug 1166529] Re: Creative Recon3d & Sound Blaster Z (CA0132), No Sound At All; Broken Beyond All Repair

2016-12-12 Thread Sean O'Donnell

This is affecting me.

Decided to give Ubuntu 16.04 a try and I cannot for the life of me get
Optical or the green, black and orange/brown cables working either (The
3.5mm jacks).

Audio works in windows fine, I did the echo "options snd-hda-intel
position_fix=1" | sudo tee -a /etc/modprobe.d/alsa-base.conf fix and it
worked for a day, when I restarted from windows to Linux it broke again.

Everything shows up. It should be working but sound does not play at
all.

HDMI Audio works fine via my monitor.

Motherboard: Gigabyte Gaming 7 Z170
Card: HDA Intel PCH 
Chip: Creative CA0132  

If I can do anything to help please let me know. I can't switch over
from windows if I don't have audio.

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

Title:
  Creative Recon3d & Sound Blaster Z (CA0132), No Sound At All; Broken
  Beyond All Repair

Status in ALSA driver:
  Unknown
Status in Skylinux:
  Confirmed
Status in alsa-driver package in Ubuntu:
  Confirmed
Status in alsa-driver package in Debian:
  New

Bug description:
  [WORKAROUND] Run the following command:

  echo "options snd-hda-intel position_fix=1" | sudo tee -a
  /etc/modprobe.d/alsa-base.conf

  [EDIT]
  Workaround doesn't work anymore for me at least. I assume it only has a small 
possibility of working due to a firmware bug.

  [ORIGINAL REPORT]
  No sound, no jacks; It is detected by Linux however.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.8.0-16.26-generic 3.8.5
  Uname: Linux 3.8.0-16-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.9.2-0ubuntu5
  Architecture: amd64
  Date: Mon Apr  8 18:56:44 2013
  InstallationDate: Installed on 2013-04-07 (1 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130402.1)
  MarkForUpload: True
  PackageArchitecture: all
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Creative failed
  Symptom_Card: HDA Creative - HDA Creative
  Symptom_Type: No sound at all
  Title: [To be filled by O.E.M., Creative CA0132, Green Line Out, Rear] No 
sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/12/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1102
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: SABERTOOTH 990FX
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1102:bd03/12/2012:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnSABERTOOTH990FX:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: To be filled by O.E.M.

To manage notifications about this bug go to:
https://bugs.launchpad.net/alsa-driver/+bug/1166529/+subscriptions

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

[Desktop-packages] [Bug 1629633] Re: evince displays blank thumbnails for some pages

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

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to evince in Ubuntu.
https://bugs.launchpad.net/bugs/1629633

Title:
  evince displays blank thumbnails for some pages

Status in Evince:
  Confirmed
Status in evince package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  To reproduce this bug:

   - load the attached PS file into evince
   - if thumbnails are not displayed then press F9 and choose to display 
thumbnails
   - evince displayd a blank thumbnail for pages 6 and 7

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: evince 3.22.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-19.21-lowlatency 4.8.0-rc8
  Uname: Linux 4.8.0-19-lowlatency x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Sun Oct  2 10:10:28 2016
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: evince
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/evince/+bug/1629633/+subscriptions

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

[Desktop-packages] [Bug 1641380] Re: chromium-browser: ERR_CERTIFICATE_TRANSPARENCY_REQUIRED for Symantec certs

2016-12-12 Thread Chad Miller

** Changed in: chromium-browser (Ubuntu)
   Status: Fix Released => In Progress

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1641380

Title:
  chromium-browser: ERR_CERTIFICATE_TRANSPARENCY_REQUIRED for Symantec
  certs

Status in chromium-browser package in Ubuntu:
  In Progress

Bug description:
  Chromium browser in xenial no longer trusts Symantec issued
  certificates. See [1].

  1. https://bugs.chromium.org/p/chromium/issues/detail?id=664177

  Ubuntu release: 16.04
  chromium-browser: 53.0.2785.143-0ubuntu0.16.04.1.1254

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1641380/+subscriptions

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

[Desktop-packages] [Bug 1050542] Re: soffice.bin crashed with SIGSEGV in SfxItemSet::~SfxItemSet()

2016-12-12 Thread Björn Michaelsen

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

** This bug has been marked a duplicate of bug 1045694
   soffice.bin crashed with SIGSEGV in SfxItemSet::~SfxItemSet()

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libreoffice in Ubuntu.
https://bugs.launchpad.net/bugs/1050542

Title:
  soffice.bin crashed with SIGSEGV in SfxItemSet::~SfxItemSet()

Status in libreoffice package in Ubuntu:
  Confirmed

Bug description:
  Just opened libreoffice calc and closed it. Got this error on close.

  ProblemType: Crash
  DistroRelease: Ubuntu 12.10
  Package: libreoffice-core 1:3.6.1~rc2-1ubuntu4
  ProcVersionSignature: Ubuntu 3.5.0-14.16-generic 3.5.3
  Uname: Linux 3.5.0-14-generic x86_64
  ApportVersion: 2.5.1-0ubuntu7
  Architecture: amd64
  Date: Thu Sep 13 11:12:37 2012
  Disassembly: => 0x0:  Cannot access memory at address 0x0
  ExecutablePath: /usr/lib/libreoffice/program/soffice.bin
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta amd64 (20110919)
  ProcCmdline: /usr/lib/libreoffice/program/soffice.bin --calc --splash-pipe=6
  SegvAnalysis:
   Segfault happened at: 0x0:   Cannot access memory at address 0x0
   PC (0x) not located in a known VMA region (needed executable region)!
  SegvReason: executing NULL VMA
  Signal: 11
  SourcePackage: libreoffice
  StacktraceTop:
   ?? ()
   SfxItemSet::~SfxItemSet() () from /usr/lib/libreoffice/program/libsvllo.so
   ?? () from /usr/lib/libreoffice/program/libsfxlo.so
   ?? () from /usr/lib/libreoffice/program/libsfxlo.so
   ?? () from /usr/lib/libreoffice/program/../program/libfwllo.so
  Title: soffice.bin crashed with SIGSEGV in SfxItemSet::~SfxItemSet()
  UpgradeStatus: Upgraded to quantal on 2012-07-23 (52 days ago)
  UserGroups: adm admin cdrom dialout libvirtd lpadmin plugdev sambashare

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

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

[Desktop-packages] [Bug 1562111] Re: network-manager no longer restarts dnsmasq

** Changed in: network-manager (Ubuntu)
   Importance: Undecided => Low

** Changed in: network-manager (Ubuntu)
   Status: New => Fix Released

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

Title:
  network-manager no longer restarts dnsmasq

Status in network-manager package in Ubuntu:
  Fix Released

Bug description:
  restarting Network Manager does not have any effect on it's child
  dnsmasq (nor does stopping and starting)

  ubuntu@ubuntu:~$ pidof dnsmasq
  2355
  ubuntu@ubuntu:~$ sudo systemctl restart NetworkManager
  ubuntu@ubuntu:~$ pidof dnsmasq
  2355

  This problem started in 15.10 and still exists in 16.04 beta2 - it
  works as expected in 14.04.

  The upshot is you cannot load any extra dnsmasq configuration set in
  the conf dir /etc/NetworkManager/dnsmasq.d/ because dnsmasq doesn't
  get restarted.

  
  (As a related issue dnsmasq is also running as 'nobody' and I don't think it 
should, Bug #1105493)

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.0.4-0ubuntu10
  ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6
  Uname: Linux 4.4.0-15-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Mar 25 18:13:33 2016
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IpRoute:
   default via 192.168.0.1 dev wlp4s0  proto static  metric 600 
   169.254.0.0/16 dev wlp4s0  scope link  metric 1000 
   192.168.0.0/24 dev wlp4s0  proto kernel  scope link  src 192.168.0.107  
metric 600
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAMEUUID  TYPE 
TIMESTAMP   TIMESTAMP-REAL   AUTOCONNECT  AUTOCONNECT-PRIORITY  
READONLY  DBUS-PATH   ACTIVE  DEVICE  STATE 
 ACTIVE-PATH
   Wired connection 1  53d8bcbd-4047-4705-904a-60eef9d821c1  802-3-ethernet   
1458929440  Fri 25 Mar 2016 06:10:40 PM UTC  yes  0 
no/org/freedesktop/NetworkManager/Settings/1  no  --  --
 -- 
   Mosquitoa88863fb-196e-4000-8103-880e0698d514  802-11-wireless  
1458929448  Fri 25 Mar 2016 06:10:48 PM UTC  yes  0 
no/org/freedesktop/NetworkManager/Settings/0  yes wlp4s0  activated 
 /org/freedesktop/NetworkManager/ActiveConnection/0
  nmcli-dev:
   DEVICE   TYPE  STATEDBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
   wlp4s0   wifi  connected/org/freedesktop/NetworkManager/Devices/1  
Mosquitoa88863fb-196e-4000-8103-880e0698d514  
/org/freedesktop/NetworkManager/ActiveConnection/0 
   enp0s25  ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/2  
--  ----
 
   lo   loopback  unmanaged/org/freedesktop/NetworkManager/Devices/0  
--  ----
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 
2: Error: Object 'nm' is unknown, try 'nmcli help'.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1562111/+subscriptions

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

[Desktop-packages] [Bug 1641380] Re: chromium-browser: ERR_CERTIFICATE_TRANSPARENCY_REQUIRED for Symantec certs

2016-12-12 Thread Jesse Glick

Confirmed that chromium-
browser_53.0.2785.143-0ubuntu2.16.10.1323_amd64.deb and the two others
mentioned in #77 fix a custom atlassian.net site.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1641380

Title:
  chromium-browser: ERR_CERTIFICATE_TRANSPARENCY_REQUIRED for Symantec
  certs

Status in chromium-browser package in Ubuntu:
  In Progress

Bug description:
  Chromium browser in xenial no longer trusts Symantec issued
  certificates. See [1].

  1. https://bugs.chromium.org/p/chromium/issues/detail?id=664177

  Ubuntu release: 16.04
  chromium-browser: 53.0.2785.143-0ubuntu0.16.04.1.1254

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1641380/+subscriptions

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

[Desktop-packages] [Bug 1648568] Re: The 'Details' panel in unity-control-center fails to load, libicu52 not present

what about "ldd /usr/lib/x86_64-linux-gnu/unity-control-
center-1/panels/libinfo.so | grep webkit"?

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to unity-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1648568

Title:
  The 'Details' panel in unity-control-center fails to load, libicu52
  not present

Status in unity-control-center package in Ubuntu:
  Incomplete

Bug description:
  When clicking on the 'Details' button in unity-control-center, nothing
  happens. After that, trying to close the application just relaunches
  it.

  From the command line:
  $ unity-control-center 
  libicui18n.so.52: cannot open shared object file: No such file or directory
  Failed to load module: 
/usr/lib/x86_64-linux-gnu/unity-control-center-1/panels/libinfo.so

  (clicking on details)

  libicui18n.so.52: cannot open shared object file: No such file or directory
  Failed to load module: 
/usr/lib/x86_64-linux-gnu/unity-control-center-1/panels/libinfo.so
  libicui18n.so.52: cannot open shared object file: No such file or directory
  Failed to load module: 
/usr/lib/x86_64-linux-gnu/unity-control-center-1/panels/libinfo.so

  (repeated until killed)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-control-center/+bug/1648568/+subscriptions

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

[Desktop-packages] [Bug 1649323] Re: package tex-common 4.04 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

2016-12-12 Thread Paul White

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

** This bug is no longer a duplicate of bug 1270410
   package tex-common 4.04 failed to install/upgrade: subprocess installed 
post-installation script returned error exit status 1
** This bug has been marked a duplicate of bug 1312204
   package tex-common 4.04 failed to install/upgrade

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to tex-common in Ubuntu.
https://bugs.launchpad.net/bugs/1649323

Title:
  package tex-common 4.04 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 1

Status in tex-common package in Ubuntu:
  New

Bug description:
  After upgrading, using 'update-manager', from 12.04.5 LTS to 14.04
  Trust Tahr LTS, I got an error message saying that tex-common could
  not be installed.

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: tex-common 4.04
  ProcVersionSignature: Ubuntu 3.13.0-105.152-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-105-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: amd64
  Date: Mon Dec 12 11:02:01 2016
  DuplicateSignature: package:tex-common:4.04:subprocess installed 
post-installation script returned error exit status 1
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2012-03-22 (1726 days ago)
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.7
   apt  1.0.1ubuntu2.15
  SourcePackage: tex-common
  Title: package tex-common 4.04 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
  UpgradeStatus: Upgraded to trusty on 2016-12-12 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tex-common/+bug/1649323/+subscriptions

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

[Desktop-packages] [Bug 1649323] Re: package tex-common 4.04 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

2016-12-12 Thread Ubuntu Foundations Team Bug Bot

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

** Attachment removed: "VarLogDistupgradeTermlog.gz"
   
https://bugs.launchpad.net/bugs/1649323/+attachment/4790758/+files/VarLogDistupgradeTermlog.gz

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to tex-common in Ubuntu.
https://bugs.launchpad.net/bugs/1649323

Title:
  package tex-common 4.04 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 1

Status in tex-common package in Ubuntu:
  New

Bug description:
  After upgrading, using 'update-manager', from 12.04.5 LTS to 14.04
  Trust Tahr LTS, I got an error message saying that tex-common could
  not be installed.

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: tex-common 4.04
  ProcVersionSignature: Ubuntu 3.13.0-105.152-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-105-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: amd64
  Date: Mon Dec 12 11:02:01 2016
  DuplicateSignature: package:tex-common:4.04:subprocess installed 
post-installation script returned error exit status 1
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2012-03-22 (1726 days ago)
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.7
   apt  1.0.1ubuntu2.15
  SourcePackage: tex-common
  Title: package tex-common 4.04 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
  UpgradeStatus: Upgraded to trusty on 2016-12-12 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tex-common/+bug/1649323/+subscriptions

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

[Desktop-packages] [Bug 1648905] Re: VPN username and settings not saved

the issue has been fixed in 1.2.6

https://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?h=nm-1-2&id=bb45adeda0bf427ada23b09daf970b0757e82d60

** Changed in: network-manager (Ubuntu)
   Importance: Undecided => Low

** Changed in: network-manager (Ubuntu)
   Status: New => Fix Committed

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

Title:
  VPN username and settings not saved

Status in network-manager package in Ubuntu:
  Fix Committed

Bug description:
  The OpenConnect VPN auth-dialog doesn't remember usernames and other
  settings.

  See discussion (and fix) in
  https://bugzilla.redhat.com/show_bug.cgi?id=1332491

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1648905/+subscriptions

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

[Desktop-packages] [Bug 1649151] Re: chromium-browser: ERR_CERTIFICATE_TRANSPARENCY_REQUIRED for Symantec certs on yakkety

2016-12-12 Thread Paul Dumais

I have this bug too. I can't connect securely to amazon.com or
amazon.ca.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1649151

Title:
  chromium-browser: ERR_CERTIFICATE_TRANSPARENCY_REQUIRED for Symantec
  certs on yakkety

Status in chromium-browser package in Ubuntu:
  Confirmed

Bug description:
  Bug #1641380 has now appeared for yakkety, chromium version:

  chromium-browser:
Installed: 53.0.2785.143-0ubuntu1.1307
Candidate: 53.0.2785.143-0ubuntu1.1307
Version table:
   *** 53.0.2785.143-0ubuntu1.1307 500
  500 http://no.archive.ubuntu.com/ubuntu yakkety/universe amd64 
Packages
  100 /var/lib/dpkg/status

  See comments #59+ on #1641380 for other affected users.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: chromium-browser 53.0.2785.143-0ubuntu1.1307
  ProcVersionSignature: Ubuntu 4.8.0-27.29-generic 4.8.1
  Uname: Linux 4.8.0-27-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: i3
  DRM.card0-HDMI-A-1:
   enabled: disabled
   dpms: On
   status: disconnected
   edid-base64: 
   modes:
  DRM.card0-LVDS-1:
   enabled: enabled
   dpms: On
   status: connected
   edid-base64: 
   modes: 1366x768 1280x720 1152x768 1024x768 800x600 848x480 720x480 640x480
  DRM.card0-VGA-1:
   enabled: disabled
   dpms: On
   status: disconnected
   edid-base64: 
   modes:
  Date: Sun Dec 11 22:55:57 2016
  Desktop-Session:
   'i3'
   '/etc/xdg/xdg-i3:/etc/xdg'
   '/usr/share/i3:/usr/local/share/:/usr/share/'
  DetectedPlugins:
   
  Env:
   'None'
   'None'
  InstallationDate: Installed on 2016-10-07 (65 days ago)
  InstallationMedia: Lubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20161007)
  InstalledPlugins:
   
  Load-Avg-1min: 0.59
  Load-Processes-Running-Percent:   0.1%
  MachineType: Hewlett-Packard HP G62 Notebook PC
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.8.0-27-generic 
root=UUID=d4ab73d9-2983-4a71-968a-93f46af6ba6b ro rootflags=subvol=@ noapic 
quiet splash vt.handoff=7
  SourcePackage: chromium-browser
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/10/2010
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.07
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 1426
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 54.13
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.07:bd02/10/2010:svnHewlett-Packard:pnHPG62NotebookPC:pvr049D102027102:rvnHewlett-Packard:rn1426:rvr54.13:cvnHewlett-Packard:ct10:cvrN/A:
  dmi.product.name: HP G62 Notebook PC
  dmi.product.version: 049D102027102
  dmi.sys.vendor: Hewlett-Packard
  gconf-keys: /desktop/gnome/applications/browser/exec = 
b'firefox\n'/desktop/gnome/url-handlers/https/command = b'sensible-browser 
%s\n'/desktop/gnome/url-handlers/https/enabled = 
b'true\n'/desktop/gnome/url-handlers/http/command = b'sensible-browser 
%s\n'/desktop/gnome/url-handlers/http/enabled = 
b'true\n'/desktop/gnome/session/required_components/windowmanager = 
b''/apps/metacity/general/compositing_manager = 
b''/desktop/gnome/interface/icon_theme = 
b'gnome\n'/desktop/gnome/interface/gtk_theme = b'Clearlooks\n'
  modified.conffile..etc.default.chromium-browser: [deleted]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1649151/+subscriptions

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

[Desktop-packages] [Bug 1647020] Re: Brightness resets to full when on/off battery

Thank you for your bug report. That's more likely to be a kernel issue
than a desktop one though, gnome-power-manager is only including a
frontend to see battery stats nowadays. Is there any chance you could
try with a xenial kernel to see if that works better?

Otherwise the desktop component handling screen settings is unity-
settings-daemon but that codebase didn't change much in recent cycles...
note that level changing when disc/connecting from/to a/c is an old
issue though it could depends of the driver.

Unassigning the desktop team since that doesn't seem like an high
priority issue nor a desktop regression.

** Changed in: gnome-power-manager (Ubuntu)
   Importance: Undecided => Low

** Changed in: gnome-power-manager (Ubuntu)
   Status: New => Incomplete

** Changed in: gnome-power-manager (Ubuntu)
 Assignee: Canonical Desktop Team (canonical-desktop-team) => (unassigned)

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-power-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1647020

Title:
  Brightness resets to full when on/off battery

Status in gnome-power-manager package in Ubuntu:
  Incomplete

Bug description:
  In yakkety, when my ThinkPad X250 goes on or off battery, the screen
  is reset to full brightness.  Xenial and before did not have this
  problem.  I have not found any other instances which trigger this (lid
  close, etc).

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: gnome-power-manager 3.22.0-1ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-28.30-generic 4.8.6
  Uname: Linux 4.8.0-28-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Dec  2 22:16:21 2016
  InstallationDate: Installed on 2015-03-07 (637 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  SourcePackage: gnome-power-manager
  UpgradeStatus: Upgraded to yakkety on 2016-12-01 (1 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/1647020/+subscriptions

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

[Desktop-packages] [Bug 1648925] Re: Accessibility menu not shown on lockscreen

** Package changed: unity-greeter (Ubuntu) => unity (Ubuntu)

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to unity-greeter in Ubuntu.
https://bugs.launchpad.net/bugs/1648925

Title:
  Accessibility menu not shown on lockscreen

Status in unity package in Ubuntu:
  New

Bug description:
  First off, I do not know for sure if this bug should be filed against
  "unity-greeter" package, so some guidance from someone more in the
  know would be appreciated.

  When I choose to lock my session, there is no "accessibility menu"
  (icon of person-figure in a circle) in the upper panel, like there is
  on the login screen that shows on a fresh boot. This means that I
  cannot manually turn on the onboard on-screen keyboard using only the
  touchscreen. This in turn means that I cannot log in without re-
  docking to my 2-in-1's keyboard.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.8.0-30.32~16.04.1-generic 4.8.6
  Uname: Linux 4.8.0-30-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Fri Dec  9 19:39:17 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Sky Lake Integrated Graphics [8086:191e] (rev 07) (prog-if 
00 [VGA controller])
 Subsystem: Lenovo Skylake Integrated Graphics [17aa:3812]
  InstallationDate: Installed on 2016-11-24 (16 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: LENOVO 80QL
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-30-generic 
root=UUID=7b55f366-118f-45eb-aba9-a81106cfb6a7 ro quiet splash 
usbcore.autosuspend=-1 vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/15/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: DFCN51WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Chelsea
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697WIN
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad MIIX 700-12ISK
  dmi.modalias: 
dmi:bvnLENOVO:bvrDFCN51WW:bd08/15/2016:svnLENOVO:pn80QL:pvrLenovoideapadMIIX700-12ISK:rvnLENOVO:rnChelsea:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrLenovoideapadMIIX700-12ISK:
  dmi.product.name: 80QL
  dmi.product.version: Lenovo ideapad MIIX 700-12ISK
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Fri Dec  9 19:34:07 2016
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   16708 
   vendor SDC
  xserver.version: 2:1.18.4-0ubuntu0.2

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

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

[Desktop-packages] [Bug 1649338] [NEW] /usr/bin/transmission-gtk:11:allocateBandwidth:allocateBandwidth:tr_bandwidthAllocate:bandwidthPulse:event_process_active_single_queue

2016-12-12 Thread errors.ubuntu.com bug bridge

Public bug reported:

The Ubuntu Error Tracker has been receiving reports about a problem regarding 
transmission.  This problem was most recently seen with package version 
2.84-3ubuntu3, the problem page at 
https://errors.ubuntu.com/problem/873e8ede845bec99330fddb6ed29097b72984a09 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
If you do not have access to the Ubuntu Error Tracker you can request it at 
http://forms.canonical.com/reports/.

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


** Tags: precise trusty utopic vivid wily xenial

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to transmission in Ubuntu.
https://bugs.launchpad.net/bugs/1649338

Title:
  /usr/bin/transmission-
  
gtk:11:allocateBandwidth:allocateBandwidth:tr_bandwidthAllocate:bandwidthPulse:event_process_active_single_queue

Status in transmission package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
transmission.  This problem was most recently seen with package version 
2.84-3ubuntu3, the problem page at 
https://errors.ubuntu.com/problem/873e8ede845bec99330fddb6ed29097b72984a09 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker you can request it at 
http://forms.canonical.com/reports/.

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

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

[Desktop-packages] [Bug 1641380] Re: chromium-browser: ERR_CERTIFICATE_TRANSPARENCY_REQUIRED for Symantec certs

2016-12-12 Thread gloonie

Agree with above: Build 54 worked for this bug, but Chromium is very
unstable in other respects.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1641380

Title:
  chromium-browser: ERR_CERTIFICATE_TRANSPARENCY_REQUIRED for Symantec
  certs

Status in chromium-browser package in Ubuntu:
  Fix Released

Bug description:
  Chromium browser in xenial no longer trusts Symantec issued
  certificates. See [1].

  1. https://bugs.chromium.org/p/chromium/issues/detail?id=664177

  Ubuntu release: 16.04
  chromium-browser: 53.0.2785.143-0ubuntu0.16.04.1.1254

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1641380/+subscriptions

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

[Desktop-packages] [Bug 1649187] Re: package libsane-common 1.0.25+git20150528-1ubuntu2 failed to install/upgrade: '/etc/sane.d/hp.conf' を上書きしようとしています。これはパッケージ libsane:amd64 1.0.23-3ubuntu3.1 にも存在します

** Tags removed: need-duplicate-check

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to sane-backends in Ubuntu.
https://bugs.launchpad.net/bugs/1649187

Title:
  package libsane-common 1.0.25+git20150528-1ubuntu2 failed to
  install/upgrade: '/etc/sane.d/hp.conf' を上書きしようとしています。これはパッケージ
  libsane:amd64 1.0.23-3ubuntu3.1 にも存在します

Status in sane-backends package in Ubuntu:
  New

Bug description:
  error apt-get

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libsane-common 1.0.25+git20150528-1ubuntu2
  ProcVersionSignature: Ubuntu 3.13.0-105.152-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-105-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: amd64
  Date: Mon Dec 12 14:01:06 2016
  DuplicateSignature: 
package:libsane-common:1.0.25+git20150528-1ubuntu2:'/etc/sane.d/hp.conf' 
を上書きしようとしています。これはパッケージ libsane:amd64 1.0.23-3ubuntu3.1 にも存在します
  ErrorMessage: '/etc/sane.d/hp.conf' を上書きしようとしています。これはパッケージ libsane:amd64 
1.0.23-3ubuntu3.1 にも存在します
  InstallationDate: Installed on 2012-09-12 (1552 days ago)
  InstallationMedia: Ubuntu 10.04.2 LTS "Lucid Lynx" - Release amd64 
(20110211.1)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.15
  SourcePackage: sane-backends
  Title: package libsane-common 1.0.25+git20150528-1ubuntu2 failed to 
install/upgrade: '/etc/sane.d/hp.conf' を上書きしようとしています。これはパッケージ libsane:amd64 
1.0.23-3ubuntu3.1 にも存在します
  UpgradeStatus: Upgraded to xenial on 2016-12-12 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1649187/+subscriptions

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

[Desktop-packages] [Bug 1647020] Re: Brightness resets to full when on/off battery

** Tags added: regression-release

** Changed in: gnome-power-manager (Ubuntu)
 Assignee: (unassigned) => Canonical Desktop Team (canonical-desktop-team)

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-power-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1647020

Title:
  Brightness resets to full when on/off battery

Status in gnome-power-manager package in Ubuntu:
  New

Bug description:
  In yakkety, when my ThinkPad X250 goes on or off battery, the screen
  is reset to full brightness.  Xenial and before did not have this
  problem.  I have not found any other instances which trigger this (lid
  close, etc).

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: gnome-power-manager 3.22.0-1ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-28.30-generic 4.8.6
  Uname: Linux 4.8.0-28-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Dec  2 22:16:21 2016
  InstallationDate: Installed on 2015-03-07 (637 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  SourcePackage: gnome-power-manager
  UpgradeStatus: Upgraded to yakkety on 2016-12-01 (1 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/1647020/+subscriptions

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

[Desktop-packages] [Bug 1649291] Re: Recent category doesn't work

Thank you for your bug report, that's a duplicate though and reported
upstream and on launchpad, see https://bugzilla.gnome.org/773300

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

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/1649291

Title:
  Recent category doesn't work

Status in nautilus package in Ubuntu:
  Invalid

Bug description:
  In nautilus doesn't work recent category.

  
  1) Ubuntu 16.10 x86_64
  2) 1:3.20.3-1ubuntu3.1
  3) Recent category displays last files
  4) Recent category doesn't work. I have the error when tried to use it (see 
screen above)

  Test case:

  Open the nautilus and click to recent category.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: nautilus 1:3.20.3-1ubuntu3.1
  ProcVersionSignature: Ubuntu 4.8.0-30.32-generic 4.8.6
  Uname: Linux 4.8.0-30-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Dec 12 17:37:43 2016
  ExecutablePath: /usr/bin/nautilus
  GsettingsChanges:
   b'org.gnome.nautilus.preferences' b'executable-text-activation' b"'launch'"
   b'org.gnome.nautilus.window-state' b'sidebar-width' b'205'
   b'org.gnome.nautilus.window-state' b'geometry' b"'890x550+65+502'"
  InstallationDate: Installed on 2016-12-11 (1 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  ProcEnviron:
   LANGUAGE=ru
   PATH=(custom, user)
   XDG_RUNTIME_DIR=
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_nautilus: gnome-terminal 3.20.2-1ubuntu5

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

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

[Desktop-packages] [Bug 859042] Re: Inplace file renaming lacks scrolling (compact and list views)

that's fixed in the current nautilus version which has a popover dialog
for renaming

** Changed in: nautilus (Ubuntu)
   Status: Triaged => Fix Released

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/859042

Title:
  Inplace file renaming lacks scrolling (compact and list views)

Status in Nautilus:
  Fix Released
Status in nautilus package in Ubuntu:
  Fix Released
Status in nautilus source package in Oneiric:
  Won't Fix
Status in nautilus source package in Precise:
  Triaged

Bug description:
  If I rename a file in-place (with the F2 key), and the name of the
  file is long enough to not fit in the window, it isn't scrolled when
  the cursor is beyond the window edge. So you basically don't see it
  and you can't see what you're editing.

  In the single-panel mode, it seems to happen in "Compact" view only, if you 
scroll the list horizontally so that the file name gets cropped by the window 
edge.
  In the dual-panel mode (Extra Pane is on), it happens in both panes, in 
"List" and "Compact" views.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: nautilus 1:3.1.92-0ubuntu3
  ProcVersionSignature: Ubuntu 3.0.0-11.18-generic-pae 3.0.4
  Uname: Linux 3.0.0-11-generic-pae i686
  ApportVersion: 1.23-0ubuntu1
  Architecture: i386
  Date: Sun Sep 25 19:06:32 2011
  ExecutablePath: /usr/bin/nautilus
  InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100427.1)
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to oneiric on 2011-09-24 (1 days ago)
  XsessionErrors:
   (update-manager:2405): Gtk-WARNING **: Attempting to add a widget with type 
aptdaemon+gtk3widgets+AptProgressDialog to a GtkWindow, but as a GtkBin 
subclass a GtkWindow can only contain one widget at a time; it already contains 
a widget of type GtkVBox
   (update-manager:2405): Gtk-WARNING **: Attempting to add a widget with type 
aptdaemon+gtk3widgets+AptProgressDialog to a GtkWindow, but as a GtkBin 
subclass a GtkWindow can only contain one widget at a time; it already contains 
a widget of type GtkVBox

To manage notifications about this bug go to:
https://bugs.launchpad.net/nautilus/+bug/859042/+subscriptions

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

[Desktop-packages] [Bug 1649323] Re: package tex-common 4.04 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

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

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 #1270410, 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 1270410
   package tex-common 4.04 failed to install/upgrade: subprocess installed 
post-installation script returned error exit status 1

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to tex-common in Ubuntu.
https://bugs.launchpad.net/bugs/1649323

Title:
  package tex-common 4.04 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 1

Status in tex-common package in Ubuntu:
  New

Bug description:
  After upgrading, using 'update-manager', from 12.04.5 LTS to 14.04
  Trust Tahr LTS, I got an error message saying that tex-common could
  not be installed.

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: tex-common 4.04
  ProcVersionSignature: Ubuntu 3.13.0-105.152-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-105-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: amd64
  Date: Mon Dec 12 11:02:01 2016
  DuplicateSignature: package:tex-common:4.04:subprocess installed 
post-installation script returned error exit status 1
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2012-03-22 (1726 days ago)
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.7
   apt  1.0.1ubuntu2.15
  SourcePackage: tex-common
  Title: package tex-common 4.04 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
  UpgradeStatus: Upgraded to trusty on 2016-12-12 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tex-common/+bug/1649323/+subscriptions

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

[Desktop-packages] [Bug 1543351] Re: Add on-screen-keyboard support for Xmir/Libertine apps

2016-12-12 Thread Lukáš Tinkl

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

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1543351

Title:
  Add on-screen-keyboard support for Xmir/Libertine apps

Status in Canonical System Image:
  Fix Released
Status in Canonical Pocket Desktop:
  Fix Committed
Status in Libertine:
  Fix Released
Status in Libertine devel series:
  Fix Released
Status in Libertine trunk series:
  Fix Released
Status in Ubuntu UX:
  New
Status in libertine package in Ubuntu:
  Fix Released
Status in unity8 package in Ubuntu:
  Fix Released
Status in xorg-server package in Ubuntu:
  Invalid

Bug description:
  From perspective of product management - this is currently not a
  requirement, just want to capture it for future

  we currently can't interact with puritine apps relying on the OSK

  to add this feature in where text-box selection on an xapp results in
  triggering the osk, in unity8 would be a very large/complicated
  effort. However, with a manual capability to trigger the OSK this
  could be achieved.

  For design team
  one idea was to add a show/hide button for the OSK.
  realizing this may be undesirable to add another indicator item - a follow-on 
idea might be to add an alpha button in the corner of the xmir-root window (the 
window that holds any xapp at the moment)
  this way the button presence would only be limited to the Xapp interaction.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1543351/+subscriptions

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

Re: [Desktop-packages] [Bug 1583849] Re: Firefox > 44 is broken on all big-endian architectures

2016-12-12 Thread Fritz Hudnut

I just updated/graded my PPC units yesterday, didn't look too closely over
the whole list, it was large, 60 packages plus a kernel.  Obviously since
this bug was posted FF was repaired, but, we know that the various ubuntu
distros are phasing PPC out . . . the browser is what needs the most
maintenance.

Don't know if it's possible to find a distro that is going to continue to
support PPC and get the FF package from there??  Most everybody uses
Debian, but the plan is for them to drop PPC as well.  Personally my PPC
computers are RAM challenged, as well as cpu challenged and my use is
intermittent; I spent a few minutes checking another distro a couple days
ago, but the "server was down" for downloads . . . after several tries I
moved on.

If I get a moment to boot my PPC computer I'll try to check what version of
FF I have; I definitely launched FF in both of them yesterday, and . . . it
worked, so did Qupzilla . . . .

F

On Sun, Dec 11, 2016 at 8:21 PM, ernsteiswuerfel 
wrote:

> Nice to see that bug fixed upstream! Will there be new PPC-builds of
> Firefox? ATM there are none in the repository...
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1583849
>
> Title:
>   Firefox > 44 is broken on all big-endian architectures
>
> Status in Mozilla Firefox:
>   Fix Released
> Status in firefox package in Ubuntu:
>   Confirmed
>
> Bug description:
>   OK, the reason I'm posting back here, running Lu 16.04 on an PPC
>   iBook, and MATE/XFCE 16.04 on a PM ST. . . did a dist-upgrade today,
>   so it now running the new "22" kernel and saw in the list of upgrades
>   new updates to FF and T-bird . . . on both machines after reboot FF
>   window frame loads . . . and then crashes . . . no data is ever filled
>   into the browser window.
>
>   The iBook error says it "doesn't have enough memory to report the
>   problem" . . . and on the PM . . . apparently it says the error report
>   was "corrupted" . . . no launchpad window opened in the browser when I
>   clicked on the "report the problem."
>
>   Tried to revert to the old kernel in the iBook several times,
>   seemingly failed to boot the old one . . . shut it down.
>
>   I went to the PM running 16.04 U-MATE and tried the same dist-upgrade
>   via console there, that upgrade was much larger than the Lu system,
>   but subsequently FF also then failed to launch w/o crashing . . .
>   installed Midori to make an apple user post, but when I tried to start
>   a new thread there Midori crashed as well.
>
>   I ran "apt-get -f install" in both the iBook & the PM . . . nothing
>   showed up. No "comment" in the terminal during the upgrade asking any
>   questions or reporting "problems" . . . but FF is kaput
>
>   I'm back in OSX 10.5 side until things cool down for the browsers in
>   16.04 PPC Lu & U-MATE/XFCE.
>
>   e...
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/firefox/+bug/1583849/+subscriptions
>

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.net/bugs/1583849

Title:
  Firefox > 44 is broken on all big-endian architectures

Status in Mozilla Firefox:
  Fix Released
Status in firefox package in Ubuntu:
  Confirmed

Bug description:
  OK, the reason I'm posting back here, running Lu 16.04 on an PPC
  iBook, and MATE/XFCE 16.04 on a PM ST. . . did a dist-upgrade today,
  so it now running the new "22" kernel and saw in the list of upgrades
  new updates to FF and T-bird . . . on both machines after reboot FF
  window frame loads . . . and then crashes . . . no data is ever filled
  into the browser window.

  The iBook error says it "doesn't have enough memory to report the
  problem" . . . and on the PM . . . apparently it says the error report
  was "corrupted" . . . no launchpad window opened in the browser when I
  clicked on the "report the problem."

  Tried to revert to the old kernel in the iBook several times,
  seemingly failed to boot the old one . . . shut it down.

  I went to the PM running 16.04 U-MATE and tried the same dist-upgrade
  via console there, that upgrade was much larger than the Lu system,
  but subsequently FF also then failed to launch w/o crashing . . .
  installed Midori to make an apple user post, but when I tried to start
  a new thread there Midori crashed as well.

  I ran "apt-get -f install" in both the iBook & the PM . . . nothing
  showed up. No "comment" in the terminal during the upgrade asking any
  questions or reporting "problems" . . . but FF is kaput

  I'm back in OSX 10.5 side until things cool down for the browsers in
  16.04 PPC Lu & U-MATE/XFCE.

  e...

To manage notifications about this bug go to:
https://bugs.launchpad.net/firefox/+bug/1583849/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https

[Desktop-packages] [Bug 1649291] Re: Recent category doesn't work

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

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/1649291

Title:
  Recent category doesn't work

Status in nautilus package in Ubuntu:
  Invalid

Bug description:
  In nautilus doesn't work recent category.

  
  1) Ubuntu 16.10 x86_64
  2) 1:3.20.3-1ubuntu3.1
  3) Recent category displays last files
  4) Recent category doesn't work. I have the error when tried to use it (see 
screen above)

  Test case:

  Open the nautilus and click to recent category.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: nautilus 1:3.20.3-1ubuntu3.1
  ProcVersionSignature: Ubuntu 4.8.0-30.32-generic 4.8.6
  Uname: Linux 4.8.0-30-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Dec 12 17:37:43 2016
  ExecutablePath: /usr/bin/nautilus
  GsettingsChanges:
   b'org.gnome.nautilus.preferences' b'executable-text-activation' b"'launch'"
   b'org.gnome.nautilus.window-state' b'sidebar-width' b'205'
   b'org.gnome.nautilus.window-state' b'geometry' b"'890x550+65+502'"
  InstallationDate: Installed on 2016-12-11 (1 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  ProcEnviron:
   LANGUAGE=ru
   PATH=(custom, user)
   XDG_RUNTIME_DIR=
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_nautilus: gnome-terminal 3.20.2-1ubuntu5

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

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

[Desktop-packages] [Bug 1649289] Re: LibreOffice Windows All Closing

thank you for your bug report, that seems like rather a gtk/wayland
/gnome-shell issue than a libreoffice one though

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

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libreoffice in Ubuntu.
https://bugs.launchpad.net/bugs/1649289

Title:
  LibreOffice Windows All Closing

Status in libreoffice package in Ubuntu:
  New

Bug description:
  Opened one additional Writer document. After several seconds of 100% copu, 
all LuvbreOffice windows disappears
  libreoffice process still running

  (soffice:3429): Gdk-ERROR **: Error reading events from display:
  Connection reset by peer

  
  Fatal exception: Signal 5
  Stack:
  /usr/lib/libreoffice/program/libuno_sal.so.3(+0x394a0)[0x7f72eb0a84a0]
  /usr/lib/libreoffice/program/libuno_sal.so.3(+0x39611)[0x7f72eb0a8611]
  /lib/x86_64-linux-gnu/libc.so.6(+0x35860)[0x7f72eacdd860]
  /lib/x86_64-linux-gnu/libglib-2.0.so.0(+0x50241)[0x7f72e965e241]
  
/lib/x86_64-linux-gnu/libglib-2.0.so.0(g_log_default_handler+0xc7)[0x7f72e965f297]
  /lib/x86_64-linux-gnu/libglib-2.0.so.0(g_logv+0x1e4)[0x7f72e965f5a4]
  /lib/x86_64-linux-gnu/libglib-2.0.so.0(g_log+0x8f)[0x7f72e965f7af]
  /usr/lib/x86_64-linux-gnu/libgdk-3.so.0(+0x84dd9)[0x7f72d68dadd9]
  
/lib/x86_64-linux-gnu/libglib-2.0.so.0(g_main_context_check+0x1d9)[0x7f72e96583c9]
  /lib/x86_64-linux-gnu/libglib-2.0.so.0(+0x4a974)[0x7f72e9658974]
  
/lib/x86_64-linux-gnu/libglib-2.0.so.0(g_main_context_iteration+0x2c)[0x7f72e9658aec]
  /usr/lib/libreoffice/program/libvclplug_gtk3lo.so(+0x3fbd3)[0x7f72d7463bd3]
  
/usr/lib/libreoffice/program/libmergedlo.so(_ZN11Application5YieldEv+0x51)[0x7f72eda16241]
  
/usr/lib/libreoffice/program/libmergedlo.so(_ZN11Application7ExecuteEv+0x45)[0x7f72eda186b5]
  /usr/lib/libreoffice/program/libmergedlo.so(+0x182f94c)[0x7f72ecaf494c]
  /usr/lib/libreoffice/program/libmergedlo.so(+0x2756f46)[0x7f72eda1bf46]
  /usr/lib/libreoffice/program/libmergedlo.so(_Z6SVMainv+0x22)[0x7f72eda1c042]
  /usr/lib/libreoffice/program/libmergedlo.so(soffice_main+0x8a)[0x7f72ecb1629a]
  /usr/lib/libreoffice/program/soffice.bin(+0x7ab)[0x55f5731e97ab]
  /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf1)[0x7f72eacc83f1]
  /usr/lib/libreoffice/program/soffice.bin(+0x7ea)[0x55f5731e97ea]

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: libreoffice 1:5.2.2-0ubuntu2
  ProcVersionSignature: Ubuntu 4.8.0-30.32-generic 4.8.6
  Uname: Linux 4.8.0-30-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Dec 12 06:38:40 2016
  SourcePackage: libreoffice
  UpgradeStatus: Upgraded to yakkety on 2016-11-16 (25 days ago)

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

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

[Desktop-packages] [Bug 1649187] Re: package libsane-common 1.0.25+git20150528-1ubuntu2 failed to install/upgrade: '/etc/sane.d/hp.conf' を上書きしようとしています。これはパッケージ libsane:amd64 1.0.23-3ubuntu3.1 にも存在します

2016-12-12 Thread Emily Ratliff

** Information type changed from Private Security to Public

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to sane-backends in Ubuntu.
https://bugs.launchpad.net/bugs/1649187

Title:
  package libsane-common 1.0.25+git20150528-1ubuntu2 failed to
  install/upgrade: '/etc/sane.d/hp.conf' を上書きしようとしています。これはパッケージ
  libsane:amd64 1.0.23-3ubuntu3.1 にも存在します

Status in sane-backends package in Ubuntu:
  New

Bug description:
  error apt-get

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libsane-common 1.0.25+git20150528-1ubuntu2
  ProcVersionSignature: Ubuntu 3.13.0-105.152-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-105-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: amd64
  Date: Mon Dec 12 14:01:06 2016
  DuplicateSignature: 
package:libsane-common:1.0.25+git20150528-1ubuntu2:'/etc/sane.d/hp.conf' 
を上書きしようとしています。これはパッケージ libsane:amd64 1.0.23-3ubuntu3.1 にも存在します
  ErrorMessage: '/etc/sane.d/hp.conf' を上書きしようとしています。これはパッケージ libsane:amd64 
1.0.23-3ubuntu3.1 にも存在します
  InstallationDate: Installed on 2012-09-12 (1552 days ago)
  InstallationMedia: Ubuntu 10.04.2 LTS "Lucid Lynx" - Release amd64 
(20110211.1)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.15
  SourcePackage: sane-backends
  Title: package libsane-common 1.0.25+git20150528-1ubuntu2 failed to 
install/upgrade: '/etc/sane.d/hp.conf' を上書きしようとしています。これはパッケージ libsane:amd64 
1.0.23-3ubuntu3.1 にも存在します
  UpgradeStatus: Upgraded to xenial on 2016-12-12 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1649187/+subscriptions

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

[Desktop-packages] [Bug 1649323] [NEW] package tex-common 4.04 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

2016-12-12 Thread Arjun Trivedi

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

Public bug reported:

After upgrading, using 'update-manager', from 12.04.5 LTS to 14.04 Trust
Tahr LTS, I got an error message saying that tex-common could not be
installed.

ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: tex-common 4.04
ProcVersionSignature: Ubuntu 3.13.0-105.152-generic 3.13.11-ckt39
Uname: Linux 3.13.0-105-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.21
Architecture: amd64
Date: Mon Dec 12 11:02:01 2016
DuplicateSignature: package:tex-common:4.04:subprocess installed 
post-installation script returned error exit status 1
ErrorMessage: subprocess installed post-installation script returned error exit 
status 1
InstallationDate: Installed on 2012-03-22 (1726 days ago)
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.17.5ubuntu5.7
 apt  1.0.1ubuntu2.15
SourcePackage: tex-common
Title: package tex-common 4.04 failed to install/upgrade: subprocess installed 
post-installation script returned error exit status 1
UpgradeStatus: Upgraded to trusty on 2016-12-12 (0 days ago)

** Affects: tex-common (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package dist-upgrade trusty

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to tex-common in Ubuntu.
https://bugs.launchpad.net/bugs/1649323

Title:
  package tex-common 4.04 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 1

Status in tex-common package in Ubuntu:
  New

Bug description:
  After upgrading, using 'update-manager', from 12.04.5 LTS to 14.04
  Trust Tahr LTS, I got an error message saying that tex-common could
  not be installed.

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: tex-common 4.04
  ProcVersionSignature: Ubuntu 3.13.0-105.152-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-105-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: amd64
  Date: Mon Dec 12 11:02:01 2016
  DuplicateSignature: package:tex-common:4.04:subprocess installed 
post-installation script returned error exit status 1
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2012-03-22 (1726 days ago)
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.7
   apt  1.0.1ubuntu2.15
  SourcePackage: tex-common
  Title: package tex-common 4.04 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
  UpgradeStatus: Upgraded to trusty on 2016-12-12 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tex-common/+bug/1649323/+subscriptions

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

[Desktop-packages] [Bug 1616397] Re: Adaptive theming like unity launcher/dash

2016-12-12 Thread Adolfo Jayme

** Changed in: gnome-terminal (Ubuntu)
   Importance: Undecided => Wishlist

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-terminal in Ubuntu.
https://bugs.launchpad.net/bugs/1616397

Title:
  Adaptive theming like unity launcher/dash

Status in gnome-terminal package in Ubuntu:
  New

Bug description:
  I usually find myself customizing my gnome-terminal to suit my
  wallpaper or the overall theme of my desktop.

  Unity has adaptive theming/blur which works great. gnome-terminal
  should have this feature too.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1616397/+subscriptions

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

[Desktop-packages] [Bug 1629855] Re: month names reversed (hebrew)

2016-12-12 Thread Adolfo Jayme

** Changed in: gnome-terminal (Ubuntu)
   Importance: Undecided => Medium

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-terminal in Ubuntu.
https://bugs.launchpad.net/bugs/1629855

Title:
  month names reversed (hebrew)

Status in gnome-terminal package in Ubuntu:
  New

Bug description:
  Month names appear in hebrew, after clean install.

  The problem is that the names are printed reveresed:
  This is what is printed in the terminal:

  לוי

  When copy and past a line from the terminal to the browser the Hebrew text 
appears correctly:
  drwxr-xr-x   2 root root4096 יול 19 23:49 rsyslog.d/
  d

  The problem seems like a rendering problem in the terminal

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gnome-terminal 3.18.3-1ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  Uname: Linux 4.4.0-38-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Oct  3 15:14:24 2016
  ExecutablePath: /usr/lib/gnome-terminal/gnome-terminal-server
  InstallationDate: Installed on 2016-10-03 (0 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  SourcePackage: gnome-terminal
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1629855/+subscriptions

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

[Desktop-packages] [Bug 1649305] Re: LibreOffice issues with HiDPI Low DPI GNOME/Wayland

Thank you for your bug report, that seems rather a gnome-shell issue
though, whatever libreoffice is doing the desktop environment shouldn't
stop working also rendering and resize are wm handled

** Package changed: libreoffice (Ubuntu) => gnome-shell (Ubuntu)

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libreoffice in Ubuntu.
https://bugs.launchpad.net/bugs/1649305

Title:
  LibreOffice issues with HiDPI Low DPI GNOME/Wayland

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Environment: MacBook Pro internal HiDPI display, two external low dpi
  displays

  SYMPTOM 1:
  If LibreOffice is launched on the internal display, it may halt the computer

  SYMPTOM 2:
  If a new LibreOffice Writer window is launched on the low dpi display, it 
only draws in the upper left 25%.
  Graphics in this state is fuzzy.

  GETAROUND
  a. LibreOffice in this state does not allow Window resize
  1. Click on another window
  2. Click back on the Writer Window
  - Resize is now available
  3. Resize the window at the bottom edge
  - Writer redraws using the full area, graphics go sharp

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: libreoffice 1:5.2.2-0ubuntu2
  ProcVersionSignature: Ubuntu 4.8.0-30.32-generic 4.8.6
  Uname: Linux 4.8.0-30-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Dec 12 07:04:47 2016
  SourcePackage: libreoffice
  UpgradeStatus: Upgraded to yakkety on 2016-11-16 (25 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1649305/+subscriptions

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

[Desktop-packages] [Bug 1649295] Re: LibreOffice Recovery docx lose styles 20%

Thank you for your bug report. Do you have steps to trigger the issue
and/or an example document which can be used? You said that before the
feature was not functional, do you know if there is a bug report about
that?

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

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libreoffice in Ubuntu.
https://bugs.launchpad.net/bugs/1649295

Title:
  LibreOffice Recovery docx lose styles 20%

Status in libreoffice package in Ubuntu:
  New

Bug description:
  On recovery, LibreOffice Recovery of docx format documents lose all styles in 
20% of cases.
  (this is improvement b/c in 16.04 recovery was not functional)

  Text Body style becomes Default Style
  All style information is reset and has to be reloaded using LibreOffice - 
Styles - Styles and Formatting F11 - Load Styles… - Overwrite, OK

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: libreoffice 1:5.2.2-0ubuntu2
  ProcVersionSignature: Ubuntu 4.8.0-30.32-generic 4.8.6
  Uname: Linux 4.8.0-30-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Dec 12 06:44:49 2016
  SourcePackage: libreoffice
  UpgradeStatus: Upgraded to yakkety on 2016-11-16 (25 days ago)

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

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

[Desktop-packages] [Bug 1642241] Re: nvidia-: nvidia- kernel module failed to build with kernel 4.9 [error: passing argument 5 of ‘get_user_pages’ from incompatible pointer type]

2016-12-12 Thread Robert Hooker

Fixed by

nvidia-graphics-drivers-304 (304.132-0ubuntu3) zesty; urgency=medium

nvidia-graphics-drivers-340 (340.98-0ubuntu2) zesty; urgency=medium

  * debian/templates/dkms_nvidia.conf.in,
debian/dkms_nvidia/patches/buildfix_kernel_4.9.patch:
- Add support for Linux 4.9. Credit goes to Michael Marley for
  finding out about the new required DRIVER_LEGACY flag.

** Changed in: nvidia-graphics-drivers-304 (Ubuntu)
   Status: Confirmed => Fix Released

** Changed in: nvidia-graphics-drivers-340 (Ubuntu)
   Status: Confirmed => Fix Released

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nvidia-graphics-drivers-304 in Ubuntu.
https://bugs.launchpad.net/bugs/1642241

Title:
  nvidia-*: nvidia-* kernel module failed to build with kernel 4.9
  [error: passing argument 5 of ‘get_user_pages’ from incompatible
  pointer type]

Status in nvidia-graphics-drivers-304 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-367 package in Ubuntu:
  Confirmed

Bug description:
  nvidia 340.98 is failed with kernel 4.9.x

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: nvidia-340 340.98-0ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-27.29-generic 4.8.1
  Uname: Linux 4.8.0-27-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] est un dossier: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  340.98  Mon Sep 19 17:31:03 
PDT 2016
   GCC version:  gcc version 6.2.0 20161109 (Ubuntu 6.2.0-13ubuntu1)
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.3-0ubuntu8
  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
  DKMSKernelVersion: 4.9.0-1-generic
  Date: Wed Nov 16 12:06:39 2016
  DistUpgraded: Fresh install
  DistroCodename: zesty
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.8.0-26-generic, x86_64: installed
   bbswitch, 0.8, 4.8.0-27-generic, x86_64: installed
   bbswitch, 0.8, 4.9.0-1-generic, x86_64: installed
   nvidia-340, 340.98, 4.8.0-26-generic, x86_64: installed
   nvidia-340, 340.98, 4.8.0-27-generic, x86_64: installed
  DuplicateSignature: 
dkms:nvidia-340:340.98-0ubuntu1:/var/lib/dkms/nvidia-340/340.98/build/os-mlock.c:49:55:
 error: passing argument 5 of ‘get_user_pages’ from incompatible pointer type 
[-Werror=incompatible-pointer-types]
  GraphicsCard:
   NVIDIA Corporation GT218 [GeForce G210] [10de:0a60] (rev a2) (prog-if 00 
[VGA controller])
 Subsystem: Pegatron GT218 [GeForce G210] [1b0a:9045]
  InstallationDate: Installed on 2016-11-13 (3 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20161112)
  MachineType: Hewlett-Packard HP Elite 7100 Microtower PC
  PackageVersion: 340.98-0ubuntu1
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-27-generic 
root=UUID=c7607fd8-02eb-40f0-b3fb-25acb82c79e2 ro quiet splash
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1
   apt  1.3.1
  SourcePackage: nvidia-graphics-drivers-340
  Title: nvidia-340 340.98-0ubuntu1: nvidia-340 kernel module failed to build
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/23/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5.19
  dmi.board.name: 2A9Ch
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: CZC0375QV2
  dmi.chassis.type: 3
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5.19:bd03/23/2011:svnHewlett-Packard:pnHPElite7100MicrotowerPC:pvrxxx0204GR0:rvnMSI:rn2A9Ch:rvr1.0:cvnHewlett-Packard:ct3:cvr:
  dmi.product.name: HP Elite 7100 Microtower PC
  dmi.product.version: xxx0204GR0
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.13.1+17.04.20161114.1-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.73-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.3-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.3-1ubuntu2
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160706-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.13-1
  xserver.bootTime: Wed Nov 16 12:16:34 2016
  xserver.configfile: default
  xserver.errors: open /dev/fb0: No such file or directory
  xserver.logfile: /var/l

[Desktop-packages] [Bug 1649316] [NEW] Thunderbird unignores threads when archiving

2016-12-12 Thread José Luis González

Public bug reported:

If I archive an ignored thread message the thread gets unignored without
asking. Since ignored threads are the ones that you are not interested
in it makes sense to archive them just after ignoring, however once you
do that the thread is no longer ignored defeating the purpose of the
feature.

I'm running xenial and thunderbird is version
45.4.0+build1-0ubuntu0.16.04.1.

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

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to thunderbird in Ubuntu.
https://bugs.launchpad.net/bugs/1649316

Title:
  Thunderbird unignores threads when archiving

Status in thunderbird package in Ubuntu:
  New

Bug description:
  If I archive an ignored thread message the thread gets unignored
  without asking. Since ignored threads are the ones that you are not
  interested in it makes sense to archive them just after ignoring,
  however once you do that the thread is no longer ignored defeating the
  purpose of the feature.

  I'm running xenial and thunderbird is version
  45.4.0+build1-0ubuntu0.16.04.1.

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

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

[Desktop-packages] [Bug 1649307] Re: LibreOffice Does Not Bring Windows to Front on GNOME/Wayland

thank you for your bug report, to be confirmed by somebody using wayland
but those could be gnome-shell issues since the wm handles the focus
usually

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

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libreoffice in Ubuntu.
https://bugs.launchpad.net/bugs/1649307

Title:
  LibreOffice  Does Not Bring Windows to Front on GNOME/Wayland

Status in libreoffice package in Ubuntu:
  New

Bug description:
  SYMPTOM 1:
  Have two Writer windows open
  In one of the Writer windows:
  LibreOffice Writer - Window - select the other Window

  BUG1
  The other Window is not brought to front.
  LibreOffice cannot do this anymore, it worked in 16.04

  GETAROUND1
  Use GNOME Overview (Super key) to pick the LibreOffice window

  SYMPTOM 2:
  In a Writer window, select LibreOffice - Styles - Styles and Formatting F11
  click on a non-LibreOffice window
  click back on the LibreOffice window
  BUG
  Styles and formatting is no longer shown, the dialog is gone

  GTEAROUND2
  Click on another LibreOffice window
  click back on the LibreOffice window
  - Styles and Formatti gdialog appears

  SYMPTOM 3
  In STyles and Formatting dialog, elect New Style… - Load Styles…
  BUG
  Load Styles dialog is a popunder appearing below Styles and Formatting

  GETAROUND3
  Click on a non-LibreOffice window
  Click back on the LibreOffice window
  - Load Styles is now at tnhe front
  (this is using BUG2 to hide Styles and Formatting dialog)

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: libreoffice 1:5.2.2-0ubuntu2
  ProcVersionSignature: Ubuntu 4.8.0-30.32-generic 4.8.6
  Uname: Linux 4.8.0-30-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Dec 12 06:54:51 2016
  SourcePackage: libreoffice
  UpgradeStatus: Upgraded to yakkety on 2016-11-16 (25 days ago)

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

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

[Desktop-packages] [Bug 1635988] Re: Update nautilus to 3.22

2016-12-12 Thread Jeremy Bicha

** Description changed:

  Notable new features and changes:
  - The view menu has been consolidated into a single "hamburger" menu with a 
separate toggle in the toolbar to switch between icon and list view.
  - Batch renaming is integrated. Just select multiple files then Rename.
- - File compression and decompression is integrated.
+ - File compression and decompression is integrated. This adds a dependency on 
gnome-autoar (approved MIR bug 1635991 )
  - Nautilus standardized its coding style. This means that every Ubuntu patch 
had to be rebased.
  
  https://csorianognome.wordpress.com/2016/08/31/nautilus-3-22-news-changes/
  https://git.gnome.org/browse/nautilus/tree/NEWS
  
  nautilus 3.22 is in the GNOME3 Staging PPA (currently for yakkety only)
  
  To Do
  =
- - The integrated compression feature requires gnome-autoar to be promoted to 
main ( bug 1635991 )
- 
- - The interactive-search feature drops the first character typed. To
- select the Downloads folder, I have to type 'ddow' instead of just
- 'dow'. The first 'd' opens the interactive-search edit field.
+ - The interactive-search feature drops the first character typed. To select 
the Downloads folder, I have to type 'ddow' instead of just 'dow'. The first 
'd' opens the interactive-search edit field.
  
  - 0001-Respect-gtk-dialogs-use-header-for-all-dialogs.patch needs to be 
updated. Currently, GNOME header bars are still used in these cases:
  + Batch Rename dialog
  + New Folder dialog
  
  - The "New Document" feature patch needs to be rewritten but this also
  affects Nautilus 3.20 in Ubuntu 16.10 "yakkety" (bug 1632027 )

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/1635988

Title:
  Update nautilus to 3.22

Status in Ubuntu GNOME:
  Triaged
Status in nautilus package in Ubuntu:
  Triaged

Bug description:
  Notable new features and changes:
  - The view menu has been consolidated into a single "hamburger" menu with a 
separate toggle in the toolbar to switch between icon and list view.
  - Batch renaming is integrated. Just select multiple files then Rename.
  - File compression and decompression is integrated. This adds a dependency on 
gnome-autoar (approved MIR bug 1635991 )
  - Nautilus standardized its coding style. This means that every Ubuntu patch 
had to be rebased.

  https://csorianognome.wordpress.com/2016/08/31/nautilus-3-22-news-changes/
  https://git.gnome.org/browse/nautilus/tree/NEWS

  nautilus 3.22 is in the GNOME3 Staging PPA (currently for yakkety
  only)

  To Do
  =
  - The interactive-search feature drops the first character typed. To select 
the Downloads folder, I have to type 'ddow' instead of just 'dow'. The first 
'd' opens the interactive-search edit field.

  - 0001-Respect-gtk-dialogs-use-header-for-all-dialogs.patch needs to be 
updated. Currently, GNOME header bars are still used in these cases:
  + Batch Rename dialog
  + New Folder dialog

  - The "New Document" feature patch needs to be rewritten but this also
  affects Nautilus 3.20 in Ubuntu 16.10 "yakkety" (bug 1632027 )

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-gnome/+bug/1635988/+subscriptions

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

[Desktop-packages] [Bug 1603024] Re: Battery drain (upowerd high CPU) on Nexus 4 when no network is available

2016-12-12 Thread Lukáš Tinkl

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

** This bug has been marked a duplicate of bug 1630382
   [mako] Awful life battery since OTA 13

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to upower in Ubuntu.
https://bugs.launchpad.net/bugs/1603024

Title:
  Battery drain (upowerd high CPU) on Nexus 4 when no network is
  available

Status in Canonical System Image:
  New
Status in repowerd:
  Incomplete
Status in The Ubuntu Power Consumption Project:
  New
Status in unity8 package in Ubuntu:
  New
Status in upower package in Ubuntu:
  New

Bug description:
  Nexus 4 connected to wifi but not logged in so no network available.
  Battery drained from full to empty in 6 hours, with no use.

  rc_proposed
  Image Part: 10160714
  Build No: R486
  Device Image Part: 20160404.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1603024/+subscriptions

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

[Desktop-packages] [Bug 1649307] [NEW] LibreOffice Does Not Bring Windows to Front on GNOME/Wayland

Public bug reported:

SYMPTOM 1:
Have two Writer windows open
In one of the Writer windows:
LibreOffice Writer - Window - select the other Window

BUG1
The other Window is not brought to front.
LibreOffice cannot do this anymore, it worked in 16.04

GETAROUND1
Use GNOME Overview (Super key) to pick the LibreOffice window

SYMPTOM 2:
In a Writer window, select LibreOffice - Styles - Styles and Formatting F11
click on a non-LibreOffice window
click back on the LibreOffice window
BUG
Styles and formatting is no longer shown, the dialog is gone

GTEAROUND2
Click on another LibreOffice window
click back on the LibreOffice window
- Styles and Formatti gdialog appears

SYMPTOM 3
In STyles and Formatting dialog, elect New Style… - Load Styles…
BUG
Load Styles dialog is a popunder appearing below Styles and Formatting

GETAROUND3
Click on a non-LibreOffice window
Click back on the LibreOffice window
- Load Styles is now at tnhe front
(this is using BUG2 to hide Styles and Formatting dialog)

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: libreoffice 1:5.2.2-0ubuntu2
ProcVersionSignature: Ubuntu 4.8.0-30.32-generic 4.8.6
Uname: Linux 4.8.0-30-generic x86_64
ApportVersion: 2.20.3-0ubuntu8
Architecture: amd64
CurrentDesktop: GNOME
Date: Mon Dec 12 06:54:51 2016
SourcePackage: libreoffice
UpgradeStatus: Upgraded to yakkety on 2016-11-16 (25 days ago)

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


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

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libreoffice in Ubuntu.
https://bugs.launchpad.net/bugs/1649307

Title:
  LibreOffice  Does Not Bring Windows to Front on GNOME/Wayland

Status in libreoffice package in Ubuntu:
  New

Bug description:
  SYMPTOM 1:
  Have two Writer windows open
  In one of the Writer windows:
  LibreOffice Writer - Window - select the other Window

  BUG1
  The other Window is not brought to front.
  LibreOffice cannot do this anymore, it worked in 16.04

  GETAROUND1
  Use GNOME Overview (Super key) to pick the LibreOffice window

  SYMPTOM 2:
  In a Writer window, select LibreOffice - Styles - Styles and Formatting F11
  click on a non-LibreOffice window
  click back on the LibreOffice window
  BUG
  Styles and formatting is no longer shown, the dialog is gone

  GTEAROUND2
  Click on another LibreOffice window
  click back on the LibreOffice window
  - Styles and Formatti gdialog appears

  SYMPTOM 3
  In STyles and Formatting dialog, elect New Style… - Load Styles…
  BUG
  Load Styles dialog is a popunder appearing below Styles and Formatting

  GETAROUND3
  Click on a non-LibreOffice window
  Click back on the LibreOffice window
  - Load Styles is now at tnhe front
  (this is using BUG2 to hide Styles and Formatting dialog)

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: libreoffice 1:5.2.2-0ubuntu2
  ProcVersionSignature: Ubuntu 4.8.0-30.32-generic 4.8.6
  Uname: Linux 4.8.0-30-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Dec 12 06:54:51 2016
  SourcePackage: libreoffice
  UpgradeStatus: Upgraded to yakkety on 2016-11-16 (25 days ago)

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

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

[Desktop-packages] [Bug 1649305] [NEW] LibreOffice issues with HiDPI Low DPI GNOME/Wayland

Public bug reported:

Environment: MacBook Pro internal HiDPI display, two external low dpi
displays

SYMPTOM 1:
If LibreOffice is launched on the internal display, it may halt the computer

SYMPTOM 2:
If a new LibreOffice Writer window is launched on the low dpi display, it only 
draws in the upper left 25%.
Graphics in this state is fuzzy.

GETAROUND
a. LibreOffice in this state does not allow Window resize
1. Click on another window
2. Click back on the Writer Window
- Resize is now available
3. Resize the window at the bottom edge
- Writer redraws using the full area, graphics go sharp

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: libreoffice 1:5.2.2-0ubuntu2
ProcVersionSignature: Ubuntu 4.8.0-30.32-generic 4.8.6
Uname: Linux 4.8.0-30-generic x86_64
ApportVersion: 2.20.3-0ubuntu8
Architecture: amd64
CurrentDesktop: GNOME
Date: Mon Dec 12 07:04:47 2016
SourcePackage: libreoffice
UpgradeStatus: Upgraded to yakkety on 2016-11-16 (25 days ago)

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


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

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libreoffice in Ubuntu.
https://bugs.launchpad.net/bugs/1649305

Title:
  LibreOffice issues with HiDPI Low DPI GNOME/Wayland

Status in libreoffice package in Ubuntu:
  New

Bug description:
  Environment: MacBook Pro internal HiDPI display, two external low dpi
  displays

  SYMPTOM 1:
  If LibreOffice is launched on the internal display, it may halt the computer

  SYMPTOM 2:
  If a new LibreOffice Writer window is launched on the low dpi display, it 
only draws in the upper left 25%.
  Graphics in this state is fuzzy.

  GETAROUND
  a. LibreOffice in this state does not allow Window resize
  1. Click on another window
  2. Click back on the Writer Window
  - Resize is now available
  3. Resize the window at the bottom edge
  - Writer redraws using the full area, graphics go sharp

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: libreoffice 1:5.2.2-0ubuntu2
  ProcVersionSignature: Ubuntu 4.8.0-30.32-generic 4.8.6
  Uname: Linux 4.8.0-30-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Dec 12 07:04:47 2016
  SourcePackage: libreoffice
  UpgradeStatus: Upgraded to yakkety on 2016-11-16 (25 days ago)

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

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

[Desktop-packages] [Bug 1649295] Re: LibreOffice Recovery docx lose styles 20%

Output during failing recovery:

(soffice:32742): GLib-GObject-WARNING **: /build/glib2.0-55kQfG/glib2.0-2.50.0/.
/gobject/gsignal.c:3492: signal name 'selection_changed' is invalid for instance
 '0x7fae58017860' of type 'OOoAtkObjCompTxt'

(soffice:32742): Gdk-WARNING **: Couldn't map as window 0x564402d83e60
as popup because it doesn't have a parent

(soffice:32742): GLib-GObject-WARNING **: g_object_weak_unref: couldn't
find weak ref 0x7fae80482d80(0x56440182e0f8)

(soffice:32742): Gdk-WARNING **: Couldn't map as window 0x564403f7a8a0
as popup because it doesn't have a parent

(soffice:32742): Gdk-WARNING **: Couldn't map as window 0x564404752e60
as popup because it doesn't have a parent

(soffice:32742): Gdk-WARNING **: Couldn't map as window 0x5644078b28a0
as popup because it doesn't have a parent

(soffice:32742): Gdk-WARNING **: Couldn't map as window 0x5644081522e0
as popup because it doesn't have a parent

(soffice:32742): Gdk-WARNING **: Couldn't map as window 0x564402d83e60
as popup because it doesn't have a parent

(soffice:32742): Gdk-WARNING **: Couldn't map as window 0x564403f7a8a0
as popup because it doesn't have a parent

(soffice:32742): Gdk-WARNING **: Couldn't map as window 0x564404752e60
as popup because it doesn't have a parent

(soffice:32742): Gdk-WARNING **: Couldn't map as window 0x5644078b28a0
as popup because it doesn't have a parent

(soffice:32742): Gdk-WARNING **: Couldn't map as window 0x5644081522e0
as popup because it doesn't have a parent

(soffice:32742): Gdk-WARNING **: No grabbed seat found, using the
default one in order to map popup window 0x5644081522e0. You may find
oddities ahead, gdk_seat_grab() should be used to simultaneously grab
input and show this popup

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libreoffice in Ubuntu.
https://bugs.launchpad.net/bugs/1649295

Title:
  LibreOffice Recovery docx lose styles 20%

Status in libreoffice package in Ubuntu:
  New

Bug description:
  On recovery, LibreOffice Recovery of docx format documents lose all styles in 
20% of cases.
  (this is improvement b/c in 16.04 recovery was not functional)

  Text Body style becomes Default Style
  All style information is reset and has to be reloaded using LibreOffice - 
Styles - Styles and Formatting F11 - Load Styles… - Overwrite, OK

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: libreoffice 1:5.2.2-0ubuntu2
  ProcVersionSignature: Ubuntu 4.8.0-30.32-generic 4.8.6
  Uname: Linux 4.8.0-30-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Dec 12 06:44:49 2016
  SourcePackage: libreoffice
  UpgradeStatus: Upgraded to yakkety on 2016-11-16 (25 days ago)

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

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

[Desktop-packages] [Bug 1649289] Re: LibreOffice Windows All Closing

Other Instance:
(soffice:23406): GLib-GObject-WARNING **: g_object_weak_unref: couldn't find 
weak ref 0x7f8457743d80(0x5587fa8970f8)

(soffice:23406): Gdk-WARNING **: Error 71 (Protocol error) dispatching
to Wayland display.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libreoffice in Ubuntu.
https://bugs.launchpad.net/bugs/1649289

Title:
  LibreOffice Windows All Closing

Status in libreoffice package in Ubuntu:
  New

Bug description:
  Opened one additional Writer document. After several seconds of 100% copu, 
all LuvbreOffice windows disappears
  libreoffice process still running

  (soffice:3429): Gdk-ERROR **: Error reading events from display:
  Connection reset by peer

  
  Fatal exception: Signal 5
  Stack:
  /usr/lib/libreoffice/program/libuno_sal.so.3(+0x394a0)[0x7f72eb0a84a0]
  /usr/lib/libreoffice/program/libuno_sal.so.3(+0x39611)[0x7f72eb0a8611]
  /lib/x86_64-linux-gnu/libc.so.6(+0x35860)[0x7f72eacdd860]
  /lib/x86_64-linux-gnu/libglib-2.0.so.0(+0x50241)[0x7f72e965e241]
  
/lib/x86_64-linux-gnu/libglib-2.0.so.0(g_log_default_handler+0xc7)[0x7f72e965f297]
  /lib/x86_64-linux-gnu/libglib-2.0.so.0(g_logv+0x1e4)[0x7f72e965f5a4]
  /lib/x86_64-linux-gnu/libglib-2.0.so.0(g_log+0x8f)[0x7f72e965f7af]
  /usr/lib/x86_64-linux-gnu/libgdk-3.so.0(+0x84dd9)[0x7f72d68dadd9]
  
/lib/x86_64-linux-gnu/libglib-2.0.so.0(g_main_context_check+0x1d9)[0x7f72e96583c9]
  /lib/x86_64-linux-gnu/libglib-2.0.so.0(+0x4a974)[0x7f72e9658974]
  
/lib/x86_64-linux-gnu/libglib-2.0.so.0(g_main_context_iteration+0x2c)[0x7f72e9658aec]
  /usr/lib/libreoffice/program/libvclplug_gtk3lo.so(+0x3fbd3)[0x7f72d7463bd3]
  
/usr/lib/libreoffice/program/libmergedlo.so(_ZN11Application5YieldEv+0x51)[0x7f72eda16241]
  
/usr/lib/libreoffice/program/libmergedlo.so(_ZN11Application7ExecuteEv+0x45)[0x7f72eda186b5]
  /usr/lib/libreoffice/program/libmergedlo.so(+0x182f94c)[0x7f72ecaf494c]
  /usr/lib/libreoffice/program/libmergedlo.so(+0x2756f46)[0x7f72eda1bf46]
  /usr/lib/libreoffice/program/libmergedlo.so(_Z6SVMainv+0x22)[0x7f72eda1c042]
  /usr/lib/libreoffice/program/libmergedlo.so(soffice_main+0x8a)[0x7f72ecb1629a]
  /usr/lib/libreoffice/program/soffice.bin(+0x7ab)[0x55f5731e97ab]
  /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf1)[0x7f72eacc83f1]
  /usr/lib/libreoffice/program/soffice.bin(+0x7ea)[0x55f5731e97ea]

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: libreoffice 1:5.2.2-0ubuntu2
  ProcVersionSignature: Ubuntu 4.8.0-30.32-generic 4.8.6
  Uname: Linux 4.8.0-30-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Dec 12 06:38:40 2016
  SourcePackage: libreoffice
  UpgradeStatus: Upgraded to yakkety on 2016-11-16 (25 days ago)

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

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

[Desktop-packages] [Bug 1649295] [NEW] LibreOffice Recovery docx lose styles 20%

Public bug reported:

On recovery, LibreOffice Recovery of docx format documents lose all styles in 
20% of cases.
(this is improvement b/c in 16.04 recovery was not functional)

Text Body style becomes Default Style
All style information is reset and has to be reloaded using LibreOffice - 
Styles - Styles and Formatting F11 - Load Styles… - Overwrite, OK

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: libreoffice 1:5.2.2-0ubuntu2
ProcVersionSignature: Ubuntu 4.8.0-30.32-generic 4.8.6
Uname: Linux 4.8.0-30-generic x86_64
ApportVersion: 2.20.3-0ubuntu8
Architecture: amd64
CurrentDesktop: GNOME
Date: Mon Dec 12 06:44:49 2016
SourcePackage: libreoffice
UpgradeStatus: Upgraded to yakkety on 2016-11-16 (25 days ago)

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


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

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libreoffice in Ubuntu.
https://bugs.launchpad.net/bugs/1649295

Title:
  LibreOffice Recovery docx lose styles 20%

Status in libreoffice package in Ubuntu:
  New

Bug description:
  On recovery, LibreOffice Recovery of docx format documents lose all styles in 
20% of cases.
  (this is improvement b/c in 16.04 recovery was not functional)

  Text Body style becomes Default Style
  All style information is reset and has to be reloaded using LibreOffice - 
Styles - Styles and Formatting F11 - Load Styles… - Overwrite, OK

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: libreoffice 1:5.2.2-0ubuntu2
  ProcVersionSignature: Ubuntu 4.8.0-30.32-generic 4.8.6
  Uname: Linux 4.8.0-30-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Dec 12 06:44:49 2016
  SourcePackage: libreoffice
  UpgradeStatus: Upgraded to yakkety on 2016-11-16 (25 days ago)

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

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

[Desktop-packages] [Bug 1649291] [NEW] Recent category doesn't work

2016-12-12 Thread CrazySky

Public bug reported:

In nautilus doesn't work recent category.


1) Ubuntu 16.10 x86_64
2) 1:3.20.3-1ubuntu3.1
3) Recent category displays last files
4) Recent category doesn't work. I have the error when tried to use it (see 
screen above)

Test case:

Open the nautilus and click to recent category.

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: nautilus 1:3.20.3-1ubuntu3.1
ProcVersionSignature: Ubuntu 4.8.0-30.32-generic 4.8.6
Uname: Linux 4.8.0-30-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.3-0ubuntu8
Architecture: amd64
CurrentDesktop: Unity
Date: Mon Dec 12 17:37:43 2016
ExecutablePath: /usr/bin/nautilus
GsettingsChanges:
 b'org.gnome.nautilus.preferences' b'executable-text-activation' b"'launch'"
 b'org.gnome.nautilus.window-state' b'sidebar-width' b'205'
 b'org.gnome.nautilus.window-state' b'geometry' b"'890x550+65+502'"
InstallationDate: Installed on 2016-12-11 (1 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
ProcEnviron:
 LANGUAGE=ru
 PATH=(custom, user)
 XDG_RUNTIME_DIR=
 LANG=ru_RU.UTF-8
 SHELL=/bin/bash
SourcePackage: nautilus
UpgradeStatus: No upgrade log present (probably fresh install)
usr_lib_nautilus: gnome-terminal 3.20.2-1ubuntu5

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


** Tags: amd64 apport-bug nautilus ui yakkety

** Attachment added: "Error after clicking to recent category"
   
https://bugs.launchpad.net/bugs/1649291/+attachment/4790710/+files/nautilus_error.png

** Tags added: nautilus ui

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/1649291

Title:
  Recent category doesn't work

Status in nautilus package in Ubuntu:
  New

Bug description:
  In nautilus doesn't work recent category.

  
  1) Ubuntu 16.10 x86_64
  2) 1:3.20.3-1ubuntu3.1
  3) Recent category displays last files
  4) Recent category doesn't work. I have the error when tried to use it (see 
screen above)

  Test case:

  Open the nautilus and click to recent category.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: nautilus 1:3.20.3-1ubuntu3.1
  ProcVersionSignature: Ubuntu 4.8.0-30.32-generic 4.8.6
  Uname: Linux 4.8.0-30-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Dec 12 17:37:43 2016
  ExecutablePath: /usr/bin/nautilus
  GsettingsChanges:
   b'org.gnome.nautilus.preferences' b'executable-text-activation' b"'launch'"
   b'org.gnome.nautilus.window-state' b'sidebar-width' b'205'
   b'org.gnome.nautilus.window-state' b'geometry' b"'890x550+65+502'"
  InstallationDate: Installed on 2016-12-11 (1 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  ProcEnviron:
   LANGUAGE=ru
   PATH=(custom, user)
   XDG_RUNTIME_DIR=
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_nautilus: gnome-terminal 3.20.2-1ubuntu5

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

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

[Desktop-packages] [Bug 1649288] [NEW] Unified ping doesn't support IPv4-mapped IPv6 addresses

2016-12-12 Thread Neil Wilson

Public bug reported:

ping to a mapped address


ping :::216.58.213.68

sends an ICMPv6 packet out onto the Internet with the mapped address in
the destination packet and the IPv6 address as the source. Mapped
addresses shouldn't appear on the public internet according to the RFC.

I would have expected this to use the IPv6 API to send an ICMP packet
over the v4 Internet on a dual stack machine in accordance with RFC4038.

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: iputils-ping 3:20150815-2ubuntu3
ProcVersionSignature: User Name 4.8.0-30.32-generic 4.8.6
Uname: Linux 4.8.0-30-generic x86_64
ApportVersion: 2.20.3-0ubuntu8
Architecture: amd64
Date: Mon Dec 12 14:27:34 2016
SourcePackage: iputils
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug uec-images zesty

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to iputils in Ubuntu.
https://bugs.launchpad.net/bugs/1649288

Title:
  Unified ping doesn't support IPv4-mapped IPv6 addresses

Status in iputils package in Ubuntu:
  New

Bug description:
  ping to a mapped address

  
  ping :::216.58.213.68

  sends an ICMPv6 packet out onto the Internet with the mapped address
  in the destination packet and the IPv6 address as the source. Mapped
  addresses shouldn't appear on the public internet according to the
  RFC.

  I would have expected this to use the IPv6 API to send an ICMP packet
  over the v4 Internet on a dual stack machine in accordance with
  RFC4038.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: iputils-ping 3:20150815-2ubuntu3
  ProcVersionSignature: User Name 4.8.0-30.32-generic 4.8.6
  Uname: Linux 4.8.0-30-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  Date: Mon Dec 12 14:27:34 2016
  SourcePackage: iputils
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1641380] Re: chromium-browser: ERR_CERTIFICATE_TRANSPARENCY_REQUIRED for Symantec certs

2016-12-12 Thread Bruce Steedman

+1 to #76, be nice to revert to stable Chromium ASAP though

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1641380

Title:
  chromium-browser: ERR_CERTIFICATE_TRANSPARENCY_REQUIRED for Symantec
  certs

Status in chromium-browser package in Ubuntu:
  Fix Released

Bug description:
  Chromium browser in xenial no longer trusts Symantec issued
  certificates. See [1].

  1. https://bugs.chromium.org/p/chromium/issues/detail?id=664177

  Ubuntu release: 16.04
  chromium-browser: 53.0.2785.143-0ubuntu0.16.04.1.1254

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1641380/+subscriptions

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

[Desktop-packages] [Bug 1647059] Re: On screen keyboard partially clipped or completely off screen

2016-12-12 Thread yoyoma2

** Description changed:

  The on screen keyboard is too low and partially clipped or completely
  off the bottom of the screen.
  
  On a laptop with a 2000 pixel high built-in screen with the lid closed
- and connected to a 1080p hdmi tv.
+ and connected to a 1080p hdmi tv.  The built-in screen is turned off in
+ the display settings in case that's relevant.
  
  Replication steps
  
  1) Turn on the on screen keyboard and log in using it
  2) Logout or reboot
  3) Lightdm remembers that the on screen keyboard is on and tries to display it
  
  = Lightdm displays the on screen keyboard using the size of the unused
  2000 pixel high screen for alignment instead of the 1080 high screen in
  use.  Only the top of the keyboard is visible at the bottom of the
  screen.  If lightdm is configured to use 720p then the on screen
  keyboard is completely clipped and invisible.
  
  The problem only occurs when lightdm remembers that the on screen
  keyboard is on.  Turning it on manually correctly displays it at the
  bottom of the screen.  Toggling a misplaced keyboard off and back on
  unfortunately doesn't fix the problem.
  
  Workaround 1
  
  When logging in, after typing password, turn off the on screen keyboard
  and click the small login arrow instead of clicking the on screen enter
  key.  Each time logging in you'll need to turn the on screen keyboard on
  and off again.  Turning off an invisible/clipped keyboard and rebooting
  will temporarily fix the problem.
  
  Workaround 2
  
  Dangerous hack.  Run a script to turn off the on screen keyboard in
  lightdm's dconf database.  To make this script run as a startup
  application the sudo commands need to be removed and the lightdm group
  membership given to the user running it as well as r/w access to
  /var/lib/lightdm/.config/dconf/user.
  
  #!/bin/bash
  sudo cp /var/lib/lightdm/.config/dconf/user ~/.config/dconf/lightdm
  printf %s\\n "user-db:lightdm" > ~/db_profile_lightdm
  export ONSCREEN_KBD=$(DCONF_PROFILE=~/db_profile_lightdm dconf read 
/com/canonical/unity-greeter/onscreen-keyboard)
  #echo 'ONSCREEN_KBD=' $ONSCREEN_KBD
  if [ "$ONSCREEN_KBD" != "false" ]; then
-DCONF_PROFILE=~/db_profile_lightdm dconf write 
/com/canonical/unity-greeter/onscreen-keyboard false
-sudo cp ~/.config/dconf/lightdm /var/lib/lightdm/.config/dconf/user
+    DCONF_PROFILE=~/db_profile_lightdm dconf write 
/com/canonical/unity-greeter/onscreen-keyboard false
+    sudo cp ~/.config/dconf/lightdm /var/lib/lightdm/.config/dconf/user
  fi
  rm -f ~/db_profile_lightdm ~/.config/dconf/lightdm
  exit 0
  
  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: lightdm 1.10.6-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7
  Uname: Linux 3.13.0-37-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Dec  3 09:16:31 2016
  InstallationDate: Installed on 2014-07-09 (877 days ago)
  InstallationMedia: sonar 13.10 - Release amd64
  SourcePackage: lightdm
  UpgradeStatus: Upgraded to trusty on 2014-07-09 (877 days ago)

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to unity-greeter in Ubuntu.
https://bugs.launchpad.net/bugs/1647059

Title:
  On screen keyboard partially clipped or completely off screen

Status in unity-greeter package in Ubuntu:
  New

Bug description:
  The on screen keyboard is too low and partially clipped or completely
  off the bottom of the screen.

  On a laptop with a 2000 pixel high built-in screen with the lid closed
  and connected to a 1080p hdmi tv.  The built-in screen is turned off
  in the display settings in case that's relevant.

  Replication steps

  1) Turn on the on screen keyboard and log in using it
  2) Logout or reboot
  3) Lightdm remembers that the on screen keyboard is on and tries to display it

  = Lightdm displays the on screen keyboard using the size of the unused
  2000 pixel high screen for alignment instead of the 1080 high screen
  in use.  Only the top of the keyboard is visible at the bottom of the
  screen.  If lightdm is configured to use 720p then the on screen
  keyboard is completely clipped and invisible.

  The problem only occurs when lightdm remembers that the on screen
  keyboard is on.  Turning it on manually correctly displays it at the
  bottom of the screen.  Toggling a misplaced keyboard off and back on
  unfortunately doesn't fix the problem.

  Workaround 1

  When logging in, after typing password, turn off the on screen
  keyboard and click the small login arrow instead of clicking the on
  screen enter key.  Each time logging in you'll need to turn the on
  screen keyboard on and off again.  Turning off an invisible/clipped
  keyboard and rebooting will temporarily fix the problem.

  Workaround 2

  Dangerous hack.  Run a script to turn off the on screen keyboard in
  lightdm's dconf database.  To make this script run as a

[Desktop-packages] [Bug 1649289] [NEW] LibreOffice Windows All Closing