date:20161113

Thanks. Yes indeed package nvidia-graphics-drivers-340 for Ubuntu 14.04
got updated on 4th November so let's focus on that.

As a possible workaround you can download the previous version of that driver 
before the November 4th update here:
   https://launchpad.net/~ubuntu-security/+archive/ubuntu/ppa/+build/8305883

Now assigning the bug to the correct project (I think).

** Package changed: nvidia-graphics-drivers-331 (Ubuntu) => nvidia-
graphics-drivers-340 (Ubuntu)

** No longer affects: freecad (Ubuntu)

** No longer affects: nvidia-graphics-drivers-367 (Ubuntu)

** No longer affects: scilab (Ubuntu)

** No longer affects: xorg-server (Ubuntu)

** Changed in: nvidia-graphics-drivers-340 (Ubuntu)
 Assignee: (unassigned) => Alberto Milone (albertomilone)

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

Title:
  OpenGL Graphics broken on November 4th upgrades

Status in nvidia-graphics-drivers-340 package in Ubuntu:
  New

Bug description:
  First: I don't know if I'm reporting this against the correct package.
  The bug report system needs a "unknown package" reporting system, for
  people who aren't freaking IT experts yet who are still smart enough
  to notice a real live problem.

  I have a Radeon card, but things most definitely broke TODAY
  immediately after I did a software upgrade.

  I use Scilab, which uses OpenGL heavily.  After today's upgrade, it
  was unable to display graphics, reporting

  "Caused by: javax.media.opengl.GLException: Profile GL_DEFAULT is not
  available on X11GraphicsDevice[type .x11, connection :0.0"

  The symptom in Scilab was that the graphics window opened, but no
  graph was drawn upon it.  glxinfo is unable to find an RGB visual; I
  assume that means that GL is broken -- glxinfo certainly works just
  fine on another machine upon which Scilab also works just fine.

  ubuntu-drivers devices returns

  == /sys/devices/pci:00/:00:01.0 ==
  modalias : pci:v1002d130Fsv1043sd85CBbc03sc00i00
  vendor   : Advanced Micro Devices, Inc. [AMD/ATI]
  driver   : fglrx-updates - distro non-free
  driver   : xserver-xorg-video-ati - distro free builtin recommended
  driver   : fglrx - distro non-free

  As near as I can tell, the xserver-xorg-video-ati is installed.  I
  have not attempted to change over to fglrx.

  glxinfo returns:
  name of display: :0.0
  Error: couldn't find RGB GLX visual or fbconfig
  Error: couldn't find RGB GLX visual or fbconfig

  lspci | grep VGA returns
  00:01.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] 
Kaveri [Radeon R7 Graphics]
  --- 
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: amd64
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 14.04
  InstallationDate: Installed on 2015-06-04 (524 days ago)
  InstallationMedia: Xubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  Package: xorg-server
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.4.0-45.66~14.04.1-generic 4.4.21
  Tags: trusty third-party-packages
  Uname: Linux 4.4.0-45-generic x86_64
  UnreportableReason: This is not an official Ubuntu package. Please remove any 
third party package and try again.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm bluetooth cdrom dialout dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1639371/+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-11-13 Thread Timothy Pearson

Just hit this on a Trusty machine.

-- 
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:
  Confirmed

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 1641380] Re: chromium-browser: ERR_CERTIFICATE_TRANSPARENCY_REQUIRED for Symantec certs

2016-11-13 Thread bob

Same error for me as well.
The Symantec Class 3 Secure Server CA - G4 is not in the chrome certificate 
store.

As a temporary fix, I just saved the cert to disc and imported it into chrome. 
You can get it here:
https://knowledge.symantec.com/kb/index?page=content&actp=CROSSLINK&id=INFO2045
Advanced Settings -> Https/SSL "Manage certificates"

I just hope Symantec hasn't been compromised or something...

Version 53.0.2785.143 Built on Ubuntu , running on LinuxMint 17.3
(64-bit)

-- 
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:
  Confirmed

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 1573508] Re: nvidia-: nvidia- kernel module failed to build [error: too many arguments to function ‘get_user_pages’]

** Summary changed:

- nvidia-361 361.42-0ubuntu2: nvidia-361 kernel module failed to build [error: 
too many arguments to function ‘get_user_pages’]
+ nvidia-*: nvidia-* kernel module failed to build [error: too many arguments 
to function ‘get_user_pages’]

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

Title:
  nvidia-*: nvidia-* kernel module failed to build [error: too many
  arguments to function ‘get_user_pages’]

Status in nvidia-graphics-drivers-304 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-361 package in Ubuntu:
  Confirmed

Bug description:
  NA

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: nvidia-361 361.42-0ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  DKMSKernelVersion: 4.6.0-040600rc4-lowlatency
  Date: Fri Apr 22 15:43:10 2016
  DuplicateSignature: 
dkms:nvidia-361:361.42-0ubuntu2:/var/lib/dkms/nvidia-361/361.42/build/nvidia/os-mlock.c:119:11:
 error: too many arguments to function ‘get_user_pages’
  InstallationDate: Installed on 2016-04-22 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PackageVersion: 361.42-0ubuntu2
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1
   apt  1.2.10ubuntu1
  SourcePackage: nvidia-graphics-drivers-361
  Title: nvidia-361 361.42-0ubuntu2: nvidia-361 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-304/+bug/1573508/+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 1641475] [NEW] Why can't I scroll while selecting a text in LibreOffice

2016-11-13 Thread Irishbandit

Public bug reported:

Description:Ubuntu 16.10
Release:16.10

Cant select text and scroll mouse wheel. Works in all other apllications just
not Libreoffice.
To duplicate left click and try and scroll mouse.

Works as it should in lxde.. but not in gnome xfce or cinnamon.
After removing the PPA version and installing
LibreOfficeDev_5.3.0.0.alpha1_Linux_x86-64_deb.tar.gz
its working as excpected.

Seems to be ubuntu ppa specific.. ??

see:
https://ask.libreoffice.org/en/question/78941/why-cant-i-scroll-while-selecting-a-text-in-libreoffice-writer/
https://bugs.documentfoundation.org/show_bug.cgi?id=103594

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

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

Title:
Why can't I scroll while selecting a text in LibreOffice

Status in libreoffice package in Ubuntu:
New

Bug description:
Description: Ubuntu 16.10
Release: 16.10

Cant select text and scroll mouse wheel. Works in all other apllications just
not Libreoffice.
To duplicate left click and try and scroll mouse.

Works as it should in lxde.. but not in gnome xfce or cinnamon.
After removing the PPA version and installing
LibreOfficeDev_5.3.0.0.alpha1_Linux_x86-64_deb.tar.gz
its working as excpected.

Seems to be ubuntu ppa specific.. ??

see:

https://ask.libreoffice.org/en/question/78941/why-cant-i-scroll-while-selecting-a-text-in-libreoffice-writer/
https://bugs.documentfoundation.org/show_bug.cgi?id=103594

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1641475/+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 1641233] Re: nvidia-304 (not installed): nvidia-304 kernel module failed to build

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

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 1573508, 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 1573508
   nvidia-361 361.42-0ubuntu2: nvidia-361 kernel module failed to build [error: 
too many arguments to function ‘get_user_pages’]

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

Title:
  nvidia-304 (not installed): nvidia-304 kernel module failed to build

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

Bug description:
  I had used nvidia-304 successfully in Lubuntu 16.04.

  With Lubuntu 16.10, it would not load into the kernel.

  I just recently downloaded a fixed 304.132 version, which loaded into the 
kernel, and was
  usable, but a program (Hugin) which had started up fine under nouveau (but 
during the use of which nouveau had screen-crashed, forcing hard-shutdown), 
failed to start, with the following terminal output:
  "
  The program 'hugin' received an X Window System error.
  This probably reflects a bug in the program.
  The error was 'BadValue (integer parameter out of range for operation)'.
(Details: serial 541 error_code 2 request_code 154 minor_code 24)
(Note to programmers: normally, X errors are reported asynchronously;
 that is, you will receive the error a while after causing it.
 To debug your program, run it with the --sync command line
 option to change this behavior. You can then get a meaningful
 backtrace from your debugger if you break on the gdk_x_error() function.)
  "
  Since Hugin had worked fine in Lubuntu 16.04 with nvidia-304 - 304.131, 
  I found a version of that for Xenial Xerus (304.131-0ubuntu3) at
  https://launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304, and tried 
to install that.

  It failed to install, however...
  "Building initial module for 4.8.0-27-generic
  Error! Bad return status for module build on kernel: 4.8.0-27-generic (x86_64)
  Consult /var/lib/dkms/nvidia-304/304.131/build/make.log for more information."

  I will (try to) attach the log file for the install 
("/var/lib/dkms/nvidia-304/304.131/build/make.log"), but here are the lines 
containing the word "error":
  "echo >&2 "  ERROR: Kernel configuration is invalid.";\
  echo >&2 " include/generated/autoconf.h or include/config/auto.conf 
are missing.";\
  echo >&2 " Run 'make oldconfig && make prepare' on kernel src to fix 
it.";\

  ...

  /var/lib/dkms/nvidia-304/304.131/build/nv-mlock.c:52:11: error: too many 
arguments to function ‘get_user_pages’
   ret = get_user_pages(current, mm, (unsigned long)address,
 ^~
  In file included from /var/lib/dkms/nvidia-304/304.131/build/nv-linux.h:82:0,
   from /var/lib/dkms/nvidia-304/304.131/build/nv-mlock.c:15:
  ./include/linux/mm.h:1315:6: note: declared here
   long get_user_pages(unsigned long start, unsigned long nr_pages,
^~
  /var/lib/dkms/nvidia-304/304.131/build/nv-mlock.c:65:13: error: implicit 
declaration of function ‘page_cache_release’ 
[-Werror=implicit-function-declaration]
   page_cache_release(user_pages[i]);
   ^~
  cc1: some warnings being treated as errors
  scripts/Makefile.build:289: recipe for target 
'/var/lib/dkms/nvidia-304/304.131/build/nv-mlock.o' failed
  make[3]: *** [/var/lib/dkms/nvidia-304/304.131/build/nv-mlock.o] Error 1
  Makefile:1489: recipe for target 
'_module_/var/lib/dkms/nvidia-304/304.131/build' failed
  make[2]: *** [_module_/var/lib/dkms/nvidia-304/304.131/build] Error 2
  NVIDIA: left KBUILD.
  nvidia.ko failed to build!
  Makefile:255: recipe for target 'module' failed
  make[1]: *** [module] Error 1
  makefile:59: recipe for target 'module' failed
  make: *** [module] Error 2

  "

  I am hoping that there is some simple way to get this older version to 
load/work,
  as I am running out of options for being able to run Hugin:
  1: nouveau screen-crashes in Hugin (which starts up fine) when I try to open 
the images from which to make the panorama
  2: the fixed nvidia-304.132 loads in the kernal, but Hugin crashes upon 
starting up
  3: the older nvidia-304.131 fails to install
  4: I would consider going back to 16.04 (which is in one of 5 partitions 
which I reserve for different Lubuntu versions as they come along), but grub, 
in install

[Desktop-packages] [Bug 1196239] Re: Add support for fake modes on laptop screens which only have one

Absolutely. I was already thinking that but thanks for pointing it out.

Although the implementations may turn out to be directly related we're
keeping separate bugs in case they turn out to not be related, and
because implementing bug 1639226 it seems is more important than
resolving this one by itself (see above comments).

** Changed in: mir
   Importance: High => Low

** Changed in: mir
   Importance: Low => Wishlist

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

Title:
  Add support for fake modes on laptop screens which only have one

Status in Canonical System Image:
  Triaged
Status in Mir:
  Incomplete
Status in xorg-server package in Ubuntu:
  Won't Fix

Bug description:
  Reproduce:
  run mirout

  What happens:
  I only see one resolution supported.

  What should happen:
  I should see more resolutions, like I do on unity7.

  I guess, if in doubt, “support” the same ones as xrandr.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1196239/+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 1641470] [NEW] package libcuda1-340 340.98-0ubuntu0.16.04.1 failed to install/upgrade: package libcuda1-340 is not ready for configuration cannot configure (current status 'hal

2016-11-13 Thread Endolith

Public bug reported:

latest nvidia drivers cause  Address Boundary Error so i tried an older
one

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: libcuda1-340 340.98-0ubuntu0.16.04.1
ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24
Uname: Linux 4.4.0-47-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia
.proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  340.98  Mon Sep 19 17:31:03 
PDT 2016
 GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.4)
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.1
AptOrdering:
 libcuda1-340: Configure
 NULL: ConfigurePending
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Sun Nov 13 20:15:37 2016
Dependencies:
 gcc-6-base 6.0.1-0ubuntu1
 libc6 2.23-0ubuntu4
 libgcc1 1:6.0.1-0ubuntu1
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
DkmsStatus:
 bbswitch, 0.8, 4.4.0-47-generic, x86_64: installed
 nvidia-340, 340.98, 4.4.0-47-generic, x86_64: installed
DpkgTerminalLog:
 dpkg: error processing package libcuda1-340 (--configure):
  package libcuda1-340 is not ready for configuration
  cannot configure (current status 'half-installed')
ErrorMessage: package libcuda1-340 is not ready for configuration  cannot 
configure (current status 'half-installed')
GraphicsCard:
 NVIDIA Corporation GF108 [GeForce GT 630] [10de:0f00] (rev a1) (prog-if 00 
[VGA controller])
   Subsystem: Palit Microsystems Inc. GF108 [GeForce GT 630] [1569:0f00]
InstallationDate: Installed on 2016-09-14 (60 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
MachineType: Shuttle Inc. SZ87R
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-47-generic 
root=UUID=a10124cb-548c-4587-986c-7186b2dc9bf5 ro quiet splash
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.1
 apt  1.2.12~ubuntu16.04.1
SourcePackage: nvidia-graphics-drivers-340
Title: package libcuda1-340 340.98-0ubuntu0.16.04.1 failed to install/upgrade: 
package libcuda1-340 is not ready for configuration  cannot configure (current 
status 'half-installed')
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/04/2016
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 2.05
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: FZ87
dmi.board.vendor: Shuttle Inc.
dmi.board.version: 1.0
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.:bvr2.05:bd01/04/2016:svnShuttleInc.:pnSZ87R:pvrV1.0:rvnShuttleInc.:rnFZ87:rvr1.0:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: SZ87R
dmi.product.version: V1.0
dmi.sys.vendor: Shuttle Inc.
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.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.1
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: Sun Nov 13 18:52:59 2016
xserver.configfile: default
xserver.devices:
 inputPower Button KEYBOARD, id 6
 inputPower Button KEYBOARD, id 7
 inputLogitech USB Receiver KEYBOARD, id 8
 inputLogitech USB Receiver KEYBOARD, id 9
 inputRDing TEMPERHUM1V1.3 KEYBOARD, id 10
xserver.errors: open /dev/fb0: No such file or directory
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 
xserver.version: 2:1.18.4-0ubuntu0.1

** Affects: nvidia-graphics-drivers-340 (Ubuntu)
 Importance: Undecided
 Status: New


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

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

Title:
  package libcuda1-340 340.98-0ubuntu0.16.04.1 failed to
  install/upgrade: package libcuda1-340 is not ready for configuration
  cannot configure (current status 'half-installed')

Status in nvidia-graphics-drivers-340 package in Ubuntu:
  New

Bug description:
  latest nvidia drivers

[Desktop-packages] [Bug 1558768] Re: gvfsd-trash causing high CPU-load when try to empty trash with thousands of files

2016-11-13 Thread bb

This persists - big nuisance. 
1. Create an empty folder
2. Execute "touch bspl{0001..7000}.c" (simply crates 7000 empty files)
3. Move the files to trash
The system consumed 8GB RAM and 8GB SWAP - heavy usage of CPU - you can monitor 
with top
If I am to wait a few min it will resolve and both RAM and SWAP would go down 
to 1.5GB
If I want to get out of it somehow - I can killall gvfsd-trash and killall 
nautilus
Then go to ~/.local/share/Trash/files$ and empty the content and also
go to ~/.local/share/Trash/info$ and empty the content

I use Darktable (beautiful RAW image manipulation program). Often I have to 
delete thousands of files that take a few GB of space. Having a trash is 
desirable feature as it gives safety net for few days.
However this behaviour (consuming all the resources of the system) is more than 
an inconvenience - it makes the trash unusable.  

If somebody knows how to workaround this please advise.

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

Title:
  gvfsd-trash causing high CPU-load when try to empty trash with
  thousands of files

Status in gvfs package in Ubuntu:
  Confirmed

Bug description:
  - Ubuntu 16.04 (Xenial Xerus) Daily Build
  - AMD64
  - Unity

  Steps to reproduce:
  - a folder with thousands of files (here about 15000 files with a overall 
size of 1.5 GB)
  - delete files to trash
  - right-click at the trash icon
  - click empty trash

  A dialog "Dateioperationen" shows "vorbereiten" (it's German, I think
  in English the dialog has the title "file operations" and shows the
  text "prepare").

  This happens at this point:
  - the dialog remains unchanged
  - the process gvfsd-trash consumes up to 75% CPU, see output of top

  After 30 minutes of waiting for any reaction I killed the process. The
  trash still contains all the files.

  jan@janvm160464:~$ top

  top - 20:17:24 up 31 min,  1 user,  load average: 1,94, 1,97, 1,68
  Tasks: 244 gesamt,   5 laufend, 239 schlafend,   0 gestoppt,   0 Zombie
  %CPU(s): 85,1 be, 14,6 sy,  0,0 ni,  0,0 un,  0,0 wa,  0,0 hi,  0,3 si,  0,0 
st
  KiB Spch :  4037984 gesamt,  2142152 frei,   900784 belegt,   995048 
Puff/Cache
  KiB Swap:0 gesamt,0 frei,0 belegt.  3028940 verfü 
Spch 

PID USER  PR  NIVIRTRESSHR S %CPU %MEM ZEIT+ BEFEHL 
  
   1760 jan   20   0  454696  24448   7840 R 69,1  0,6  20:05.18 
gvfsd-trash  
   1690 jan   20   0  781012  71096  36440 S 12,0  1,8   6:13.42 nautilus   
  
   2649 jan   20   0  660088  41700  30328 S 10,3  1,0   0:04.29 gedit  
  
315 root  20   0   32236   2936   2500 R  3,3  0,1   1:06.21 
systemd-jou+ 
825 root  20   0  383184  77448  31492 S  1,3  1,9   0:15.84 Xorg   
  
   1543 jan   20   0 1254876 189468  65780 S  1,3  4,7   0:19.38 compiz 
  
641 syslog20   0  256380   3364   2684 S  1,0  0,1   0:16.81 rsyslogd   
  
   1521 jan   20   0  567508  32776  25756 S  0,7  0,8   0:01.16 
unity-panel+ 
   1448 jan   20   0   39728316 12 S  0,3  0,0   0:00.13 
upstart-dbu+ 
   2258 root  20   0   0  0  0 S  0,3  0,0   0:00.23 
kworker/u12+ 
   2695 jan   20   0   48912   3868   3136 R  0,3  0,1   0:00.01 top
  
  1 root  20   0  119720   5664   3780 S  0,0  0,1   0:02.72 systemd
  
  2 root  20   0   0  0  0 S  0,0  0,0   0:00.00 kthreadd   
  
  3 root  20   0   0  0  0 R  0,0  0,0   0:01.45 
ksoftirqd/0  
  5 root   0 -20   0  0  0 S  0,0  0,0   0:00.00 
kworker/0:0H 
  7 root  20   0   0  0  0 R  0,0  0,0   0:06.15 rcu_sched  
  
  8 root  20   0   0  0  0 S  0,0  0,0   0:00.00 rcu_bh

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1558768/+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 1631191] Re: Display backlight won't turn on after screen timeout

2016-11-13 Thread Chris Fernandez

I also have this issue with Oryx Pro from system76
please fix is annoying!!!

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

Title:
Display backlight won't turn on after screen timeout

Status in nvidia-graphics-drivers-367 package in Ubuntu:
Confirmed

Bug description:
Using nVidia driver 367.44 on Skylake Intel Processors, with 1000
series graphics, the backlight won't turn on after turned off by gnome
session idle delay (org.gnome.desktop.session idle-delay). or by `xset
dpms force off`

Resume from suspend is unaffected.

This is on a clean install of 16.10 with the 367.44 nVidia driver.
This is a regression from the 367.35 driver. 367.48 and 370.28 also
exhibit this behavior.

This is confirmed on the following hardware:

Oryx Pro 2 (oryp2) i7-6700HQ with 1070
Serval 10 (serw10) i7-6700 with 1060
Bonobo 11 (bonw11) i7-6700K with dual 1070

Steps to reproduce:

1. Install a fresh image of Yakkety and 367.44 from the graphics driver
team's PPA.
2. Log in to Unity shell
3. Lock screen and wait for dimming.
4. Move the mouse to 'resume'
5. The screen will turn on, but the backlight is still off

The current workaround:

1. Hit tty1 (Ctrl+Alt+F1)
2. Hit tty7 (Ctrl+Alt+F7)

This will bring Unity back to life.

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: nvidia-367 367.44-0ubuntu3
ProcVersionSignature: Ubuntu 4.8.0-19.21-generic 4.8.0-rc8
Uname: Linux 4.8.0-19-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.3-0ubuntu7
Architecture: amd64
CurrentDesktop: Unity
Date: Thu Oct 6 16:17:11 2016
SourcePackage: nvidia-graphics-drivers-367
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-367/+bug/1631191/+subscriptions

[Desktop-packages] [Bug 1558768] Re: gvfsd-trash causing high CPU-load when try to empty trash with thousands of files

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

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

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

Title:
  gvfsd-trash causing high CPU-load when try to empty trash with
  thousands of files

Status in gvfs package in Ubuntu:
  Confirmed

Bug description:
  - Ubuntu 16.04 (Xenial Xerus) Daily Build
  - AMD64
  - Unity

  Steps to reproduce:
  - a folder with thousands of files (here about 15000 files with a overall 
size of 1.5 GB)
  - delete files to trash
  - right-click at the trash icon
  - click empty trash

  A dialog "Dateioperationen" shows "vorbereiten" (it's German, I think
  in English the dialog has the title "file operations" and shows the
  text "prepare").

  This happens at this point:
  - the dialog remains unchanged
  - the process gvfsd-trash consumes up to 75% CPU, see output of top

  After 30 minutes of waiting for any reaction I killed the process. The
  trash still contains all the files.

  jan@janvm160464:~$ top

  top - 20:17:24 up 31 min,  1 user,  load average: 1,94, 1,97, 1,68
  Tasks: 244 gesamt,   5 laufend, 239 schlafend,   0 gestoppt,   0 Zombie
  %CPU(s): 85,1 be, 14,6 sy,  0,0 ni,  0,0 un,  0,0 wa,  0,0 hi,  0,3 si,  0,0 
st
  KiB Spch :  4037984 gesamt,  2142152 frei,   900784 belegt,   995048 
Puff/Cache
  KiB Swap:0 gesamt,0 frei,0 belegt.  3028940 verfü 
Spch 

PID USER  PR  NIVIRTRESSHR S %CPU %MEM ZEIT+ BEFEHL 
  
   1760 jan   20   0  454696  24448   7840 R 69,1  0,6  20:05.18 
gvfsd-trash  
   1690 jan   20   0  781012  71096  36440 S 12,0  1,8   6:13.42 nautilus   
  
   2649 jan   20   0  660088  41700  30328 S 10,3  1,0   0:04.29 gedit  
  
315 root  20   0   32236   2936   2500 R  3,3  0,1   1:06.21 
systemd-jou+ 
825 root  20   0  383184  77448  31492 S  1,3  1,9   0:15.84 Xorg   
  
   1543 jan   20   0 1254876 189468  65780 S  1,3  4,7   0:19.38 compiz 
  
641 syslog20   0  256380   3364   2684 S  1,0  0,1   0:16.81 rsyslogd   
  
   1521 jan   20   0  567508  32776  25756 S  0,7  0,8   0:01.16 
unity-panel+ 
   1448 jan   20   0   39728316 12 S  0,3  0,0   0:00.13 
upstart-dbu+ 
   2258 root  20   0   0  0  0 S  0,3  0,0   0:00.23 
kworker/u12+ 
   2695 jan   20   0   48912   3868   3136 R  0,3  0,1   0:00.01 top
  
  1 root  20   0  119720   5664   3780 S  0,0  0,1   0:02.72 systemd
  
  2 root  20   0   0  0  0 S  0,0  0,0   0:00.00 kthreadd   
  
  3 root  20   0   0  0  0 R  0,0  0,0   0:01.45 
ksoftirqd/0  
  5 root   0 -20   0  0  0 S  0,0  0,0   0:00.00 
kworker/0:0H 
  7 root  20   0   0  0  0 R  0,0  0,0   0:06.15 rcu_sched  
  
  8 root  20   0   0  0  0 S  0,0  0,0   0:00.00 rcu_bh

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1558768/+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-11-13 Thread calexil

confirming on mint 18 mate.

-- 
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:
  Confirmed

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

Re: [Desktop-packages] [Bug 1613863] Fails to power off monitor when locking screen

2016-11-13 Thread Anders Magnus Andersen

Problem exists upstream, I have done as instructed and will continue to do so 
until other instructions are given.
--
Vennlig hilsen / Best regards


Anders Magnus Andersen
a.m.ander...@me.com


> 12. nov. 2016 kl. 14.15 skrev Christopher M. Penalver 
> :
> 
> Anders Magnus Andersen, in order to allow additional upstream developers to 
> examine the issue, at your earliest convenience, could you please test the 
> latest upstream kernel available from 
> http://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D ? Please keep in mind 
> the following:
> 1) The one to test is at the very top line at the top of the page (not the 
> daily folder).
> 2) The release names are irrelevant.
> 3) The folder time stamps aren't indicative of when the kernel actually was 
> released upstream.
> 4) Install instructions are available at 
> https://wiki.ubuntu.com/Kernel/MainlineBuilds .
> 
> If testing on your main install would be inconvenient, one may:
> 1) Install Ubuntu to a different partition and then test this there.
> 2) Backup, or clone the primary install.
> 
> If the latest kernel did not allow you to test to the issue (ex. you couldn't 
> boot into the OS) please make a comment in your report about this, and 
> continue to test the next most recent kernel version until you can test to 
> the issue. Once you've tested the upstream kernel, please comment on which 
> kernel version specifically you tested. If this issue is fixed in the 
> mainline kernel, please add the following tags by clicking on the yellow 
> circle with a black pencil icon, next to the word Tags, located at the bottom 
> of the report description:
> kernel-fixed-upstream
> kernel-fixed-upstream-X.Y-rcZ
> 
> Where X, and Y are the first two numbers of the kernel version, and Z is
> the release candidate number if it exists.
> 
> If the mainline kernel does not fix the issue, please add the following tags:
> kernel-bug-exists-upstream
> kernel-bug-exists-upstream-X.Y-rcZ
> 
> Please note, an error to install the kernel does not fit the criteria of
> kernel-bug-exists-upstream.
> 
> Also, you don't need to apport-collect further unless specifically
> requested to do so.
> 
> It is most helpful that after testing of the latest upstream kernel is
> complete, you mark this report Status Confirmed.
> 
> Lastly, to keep this issue relevant to upstream, please continue to test
> the latest mainline kernel as it becomes available.
> 
> Thank you for your help.
> 
> ** Tags added: zesty
> 
> ** Description changed:
> 
>  Screen left black with only the cursor showing.
> + 
> + WORKAROUND: Use nvidia 361 drivers.
> 
>  ProblemType: Bug
>  DistroRelease: Ubuntu 16.04
>  Package: xserver-xorg-video-nouveau 1:1.0.12-1build2
>  Uname: Linux 4.5.7-040507-generic x86_64
>  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
>  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
> '/proc/driver/nvidia/gpus/:01:00.0'
>  .proc.driver.nvidia.registry: Binary: ""
>  .proc.driver.nvidia.version:
> -  NVRM version: NVIDIA UNIX x86_64 Kernel Module  361.42  Tue Mar 22 
> 18:10:58 PDT 2016
> -  GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.2)
> +  NVRM version: NVIDIA UNIX x86_64 Kernel Module  361.42  Tue Mar 22 
> 18:10:58 PDT 2016
> +  GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.2)
>  .proc.driver.nvidia.warnings.fbdev:
> -  Your system is not currently configured to drive a VGA console
> -  on the primary VGA device. The NVIDIA Linux graphics driver
> -  requires the use of a text-mode VGA console. Use of other console
> -  drivers including, but not limited to, vesafb, may result in
> -  corruption and stability problems, and is not supported.
> +  Your system is not currently configured to drive a VGA console
> +  on the primary VGA device. The NVIDIA Linux graphics driver
> +  requires the use of a text-mode VGA console. Use of other console
> +  drivers including, but not limited to, vesafb, may result in
> +  corruption and stability problems, and is not supported.
>  .tmp.unity_support_test.0:
> -  
> + 
>  ApportVersion: 2.20.1-0ubuntu2.1
>  Architecture: amd64
>  BootLog:
> -  
> + 
>  CompizPlugins: No value set for 
> `/apps/compiz-1/general/screen0/options/active_plugins'
>  CompositorRunning: compiz
>  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
>  CompositorUnredirectFSW: true
>  CurrentDesktop: Unity
>  Date: Tue Aug 16 21:37:46 2016
>  DistUpgraded: Fresh install
>  DistroCodename: xenial
>  DistroVariant: ubuntu
>  DkmsStatus: nvidia-361, 361.42, 4.5.7-040507-generic, x86_64: installed
>  GraphicsCard:
> -  NVIDIA Corporation GK107 [GeForce GTX 650] [10de:0fc6] (rev a1) (prog-if 
> 00 [VGA controller])
> -Subsystem: Micro-Star International Co., Ltd. [MSI] GK107 [GeForce GTX 
> 650] [1462:2809]
> +  NVIDIA Corporation GK107 [GeForce GTX 650] [10de:0fc6] (rev a1) (prog-if 
> 00 [VGA controller])
> +Subsystem: Micro-Star International Co., Ltd. [

[Desktop-packages] [Bug 1613863] Re: Fails to power off monitor when locking screen

2016-11-13 Thread Anders Magnus Andersen

** Tags added: kernel-bug-exists-upstream kernel-bug-exists-
upstream-4.9.rc5

** Changed in: xserver-xorg-video-nouveau (Ubuntu)
   Status: Expired => Confirmed

** Description changed:

- Screen left black with only the cursor showing.
+ Screen left black with only the cursor showing / Screen goes black then
+ returns to lock-screen. (Never powers off)
  
  WORKAROUND: Use nvidia 361 drivers.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xserver-xorg-video-nouveau 1:1.0.12-1build2
  Uname: Linux 4.5.7-040507-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  361.42  Tue Mar 22 18:10:58 
PDT 2016
   GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.2)
  .proc.driver.nvidia.warnings.fbdev:
   Your system is not currently configured to drive a VGA console
   on the primary VGA device. The NVIDIA Linux graphics driver
   requires the use of a text-mode VGA console. Use of other console
   drivers including, but not limited to, vesafb, may result in
   corruption and stability problems, and is not supported.
  .tmp.unity_support_test.0:
  
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  BootLog:
  
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Tue Aug 16 21:37:46 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus: nvidia-361, 361.42, 4.5.7-040507-generic, x86_64: installed
  GraphicsCard:
   NVIDIA Corporation GK107 [GeForce GTX 650] [10de:0fc6] (rev a1) (prog-if 00 
[VGA controller])
     Subsystem: Micro-Star International Co., Ltd. [MSI] GK107 [GeForce GTX 
650] [1462:2809]
  InstallationDate: Installed on 2016-08-14 (2 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: LENOVO 10120
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.5.7-040507-generic 
root=UUID=79953082-1ec8-42c2-b754-bcb468e0c457 ro rootflags=subvol=@
  SourcePackage: xserver-xorg-video-nouveau
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/24/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: I1KT24AUS
  dmi.board.vendor: LENOVO
  dmi.board.version: 3193 STD
  dmi.chassis.type: 3
  dmi.chassis.vendor: LENOVO
  dmi.modalias: 
dmi:bvnLENOVO:bvrI1KT24AUS:bd07/24/2013:svnLENOVO:pn10120:pvrIdeaCentreK450:rvnLENOVO:rn:rvr3193STD:cvnLENOVO:ct3:cvr:
  dmi.product.name: 10120
  dmi.product.version: IdeaCentre K450
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.12.2+16.04.20160801.3-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.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.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.3
  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: Tue Aug 16 19:35:02 2016
  xserver.configfile: default
  xserver.errors:
  
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
  
  xserver.version: 2:1.18.3-1ubuntu2.3

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

Title:
  Fails to power off monitor when locking screen

Status in xserver-xorg-video-nouveau package in Ubuntu:
  Confirmed

Bug description:
  Screen left black with only the cursor showing / Screen goes black
  then returns to lock-screen. (Never powers off)

  WORKAROUND: Use nvidia 361 drivers.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xserver-xorg-video-nouveau 1:1.0.12-1build2
  Uname: Linux 4.5.7-040507-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  361.42  Tue Mar 22 18:10:58 
PDT 2016
   GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.2)
  .proc.driver.nvidia.warnings.fbdev:
   Your sys

[Desktop-packages] [Bug 1641467] [NEW] Mouse flickering and disappearing near the top of screen

2016-11-13 Thread Marko

Public bug reported:

So I'm not sure this is an xorg bug, I couldn't figure out what xorg is.
But I recently upgraded to ubuntu 16.10 and started seeing this bug
where my mouse will flicker and disappear when near the top of the
screen. It still works clicking-wise. It also seems to be especially
severe when using Google Chrome, where it completely disappears and
flickers the entire time while mousing over the menu uptions (i.e the
close button, the tabs etc...). However recently I noticed this also
happens when google chrome is off, though it flickers much less.

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: xorg 1:7.7+13ubuntu4
ProcVersionSignature: Ubuntu 4.8.0-27.29-generic 4.8.1
Uname: Linux 4.8.0-27-generic x86_64
.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
CurrentDesktop: Unity
Date: Mon Nov 14 00:01:59 2016
DistUpgraded: 2016-11-11 16:58:41,906 DEBUG icon theme changed, re-reading
DistroCodename: yakkety
DistroVariant: ubuntu
GraphicsCard:
 Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
   Subsystem: Samsung Electronics Co Ltd 2nd Generation Core Processor Family 
Integrated Graphics Controller [144d:c0a5]
   Subsystem: Samsung Electronics Co Ltd GF108M [GeForce GT 540M] [144d:c0a5]
InstallationDate: Installed on 2016-08-30 (74 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
MachineType: SAMSUNG ELECTRONICS CO., LTD. RF511/RF411/RF711
ProcEnviron:
 LANGUAGE=en_GB:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-27-generic 
root=UUID=8efe8f71-2303-4aff-921a-1f80026e1b6e ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to yakkety on 2016-11-11 (2 days ago)
dmi.bios.date: 03/02/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 15HX.M042.20120302.SSH
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: RF511/RF411/RF711
dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.board.version: 15HX
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 9
dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr15HX.M042.20120302.SSH:bd03/02/2012:svnSAMSUNGELECTRONICSCO.,LTD.:pnRF511/RF411/RF711:pvr15HX:rvnSAMSUNGELECTRONICSCO.,LTD.:rnRF511/RF411/RF711:rvr15HX:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvrN/A:
dmi.product.name: RF511/RF411/RF711
dmi.product.version: 15HX
dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu2
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.70-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.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1
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.12-2
xserver.bootTime: Sun Nov 13 17:46:35 2016
xserver.configfile: default
xserver.errors:
 Failed to load module "nvidia" (module does not exist, 0)
 Failed to load module "nvidia" (module does not exist, 0)
 NOUVEAU(G0): [XvMC] Failed to initialize extension.
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.18.4-1ubuntu6
xserver.video_driver: modeset

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


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

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

Title:
  Mouse flickering and disappearing near the top of screen

Status in xorg package in Ubuntu:
  New

Bug description:
  So I'm not sure this is an xorg bug, I couldn't figure out what xorg
  is. But I recently upgraded to ubuntu 16.10 and started seeing this
  bug where my mouse will flicker and disappear when near the top of the
  screen. It still works clicking-wise. It also seems to be especially
  severe when using Google Chrome, where it completely disappears and
  flickers the entire time while mousing over the menu uptions (i.e the
  close button, the tabs etc...). However recently I noticed this also
  happens when google chrome is off, though it flickers much less.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: xorg 1:7.7+13ubuntu4
  ProcVersionSignature: Ubuntu 4.8.0-27.29-generic

[Desktop-packages] [Bug 1639533] Re: Failure to update ~/.xsession-errors

** Branch linked: lp:lightdm

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

Title:
  Failure to update ~/.xsession-errors

Status in lightdm package in Ubuntu:
  In Progress

Bug description:
  When there is an error in e.g. ~/.profile or /etc/profile, a zenity
  warning dialog is shown at login which calls the user's attention to
  the error. The error message should also be appended to ~/.xsession-
  errors, but currently it's not.

  Changing the line

  cat "$ERR" >>/dev/stderr

  in /usr/sbin/lightdm-session to

  cat "$ERR" >&2

  fixes it. (It used to work in trusty, but not any longer, so in part
  it appears to be some SRU regression.)

  Since possible error messages are shown in the zenity dialog, I don't
  think this is important enough to backport. Prepared an MP for zesty.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1639533/+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 1612367] Re: [Touch] Incoming call gets silent randomly

2016-11-13 Thread Andrea Simonetti

This affects me too on my E5. When it happens not only the ring of the call is 
muted but all application can't play sounds trough the bigger speaker. 
Please we must find a fix. I notice this since ota 11.

Can someone tell me which app manages all sounds and speakers? Is it
media-hub?

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

Title:
  [Touch] Incoming call gets silent randomly

Status in Canonical System Image:
  Confirmed
Status in media-hub package in Ubuntu:
  Confirmed
Status in ofono package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  I've experienced this strange issue 4-5 times after OTA-12. It seems pretty 
random and is hard to reproduce.
  When I get an incoming call, the screen turns on, the incoming call pop up 
appears, but there is no sound at all even though the phone is not in silent 
mode (and also the speaker volume is not set too low). I can accept this call 
and keep conversing as usual.
  Once I asked the same caller to call me once again after a few minutes, that 
time the phone rang as expected.

  Device: E5, OTA-12, stable channel

  I can provide necessary logs if this happens again. Which ones should
  I gather?

  Possibly related to bug #1614943.

  UPDATE: As mentioned in comment #7, it seems the phone rings for a
  fraction of a second and then the sound pauses abruptly.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1612367/+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 1640558] Re: 16.10 Backup Failure.

2016-11-13 Thread Tommy Pollák

~$ duplicity --version
duplicity 0.7.06

duplicity -v4 --log-file /home/tpollak/backupIncrLog --volsize 1000 --exclude /b
oot --exclude /cdrom --exclude /dev --exclude /proc --exclude /sys --exclude /tm
p --exclude /home/tpollak/.gvfs --exclude /home/tpollak/Downloads --exclude /hom
e/tpollak/Trash --exclude /media / ftp://Tommy@192.168.1.100/Tommy/for_duplicity

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

Title:
  16.10 Backup Failure.

Status in duplicity package in Ubuntu:
  Incomplete

Bug description:
  A daily backup job run by corn invokes a script that runs duplicity. Since I 
have upgraded to 16.10 from 16.04 duplicity crashes with the message "killed". 
It seems that the real problem is in the NVIDIA driver for my screen.
  The machine does not crash in other situations.

  Some info
  Dell XPS 15 L502X, 15,6" FHD, NVIDIA GEFORCE GT 540M GR 2 GB
  NVIDIA driver version 367.57
  X server version 11.0, server vendor version 1.18.4, NV-control version 1.29

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/duplicity/+bug/1640558/+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 1640558] Re: 16.10 Backup Failure.

2016-11-13 Thread Kenneth Loafman

What version of duplicity?  What command line?


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

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

Title:
  16.10 Backup Failure.

Status in duplicity package in Ubuntu:
  Incomplete

Bug description:
  A daily backup job run by corn invokes a script that runs duplicity. Since I 
have upgraded to 16.10 from 16.04 duplicity crashes with the message "killed". 
It seems that the real problem is in the NVIDIA driver for my screen.
  The machine does not crash in other situations.

  Some info
  Dell XPS 15 L502X, 15,6" FHD, NVIDIA GEFORCE GT 540M GR 2 GB
  NVIDIA driver version 367.57
  X server version 11.0, server vendor version 1.18.4, NV-control version 1.29

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/duplicity/+bug/1640558/+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 1641451] [NEW] 'ALPS Touchpad incorrectly detected as PS/2 mouse in Dell Latitude 7370

2016-11-13 Thread Michael Doube

Public bug reported:

Touchpad is detected but appears to be running some generic drivers
which mean the full suite of multi-touch controls and disabling touchpad
while typing are missing.

Laptop model directly from the sticker of the computer.
Dell Latitude 7370
Reg Model P67G

Manufacturer of the Touchpad.
Alps

When the symptom first appeared.
Since installing Ubuntu

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xserver-xorg-input-synaptics 1.8.2-1ubuntu3
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
Date: Sun Nov 13 20:08:03 2016
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
InstallationDate: Installed on 2016-05-15 (182 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
MachineType: Dell Inc. Latitude 7370
ProcEnviron:
 LANGUAGE=en_GB:en
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-47-generic.efi.signed 
root=UUID=d96256e6-13a6-46a5-ba80-2e121d8f8dab ro quiet splash vt.handoff=7
SourcePackage: xserver-xorg-input-synaptics
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/14/2016
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 01.05.03
dmi.board.name: 0MMWGJ
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr01.05.03:bd07/14/2016:svnDellInc.:pnLatitude7370:pvr:rvnDellInc.:rn0MMWGJ:rvrA00:cvnDellInc.:ct9:cvr:
dmi.product.name: Latitude 7370
dmi.sys.vendor: Dell Inc.
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.1
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: Sat Nov 12 17:24:12 2016
xserver.configfile: default
xserver.errors:

xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id5217
 vendor SHP
xserver.version: 2:1.18.4-0ubuntu0.1

** Affects: xserver-xorg-input-synaptics (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug ubuntu xenial

** Attachment added: "Windows device data"
   
https://bugs.launchpad.net/bugs/1641451/+attachment/4776962/+files/LatitudeTouchpadWindowsDiagnostics.txt

** Description changed:

+ Touchpad is detected but appears to be running some generic drivers
+ which mean the full suite of multi-touch controls and disabling touchpad
+ while typing are missing.
+ 
  Laptop model directly from the sticker of the computer.
  Dell Latitude 7370
  Reg Model P67G
  
  Manufacturer of the Touchpad.
  Alps
  
- When the symptom first appeared. 
+ When the symptom first appeared.
  Since installing Ubuntu
  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xserver-xorg-input-synaptics 1.8.2-1ubuntu3
  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
  Date: Sun Nov 13 20:08:03 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  InstallationDate: Installed on 2016-05-15 (182 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Dell Inc. Latitude 7370
  ProcEnviron:
-  LANGUAGE=en_GB:en
-  TERM=xterm-256color
-  PATH=(custom, no user)
-  LANG=en_GB.UTF-8
-  SHELL=/bin/bash
+  LANGUAGE=en_GB:en
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  LANG=en_GB.UTF-8
+  SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-47-generic.efi.signed 
root=UUID=d96256e6-13a6-46a5-ba80-2e121d8f8dab ro quiet splash vt.handoff=7
  SourcePackage: xserver-xorg-input-synaptics
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/14/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 01.05.03
  dmi.board.name: 0MMWGJ
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr01.05.03:bd07/14/2016:svnDellInc.:pnLatitude7370:pvr:rvnDellInc.:rn0MMWGJ:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude 7370
  dmi.sys.vendor: Dell Inc.
  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

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

2016-11-13 Thread Andrew

If you're in need of an immediate workaround, it's possible to disable
this check for individual sites by e.g.:

$ echo '{"CertificateTransparencyEnforcementDisabledForUrls": ["weebly.com"]}' \
| sudo tee /etc/chromium-browser/policies/recommended/workaround_1641380.json

Details: https://www.chromium.org/administrators/policy-
list-3#CertificateTransparencyEnforcementDisabledForUrls

-- 
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:
  Confirmed

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 1641450] [NEW] libxml2 requires libiconv for static build

2016-11-13 Thread Erwan Georget

Public bug reported:

Hi.

I tried to build a software (Ryzomcore, an MMO framework), as a static
build, but we are facing some unexpected issues :

https://git.khaganat.net/khaganat/khanat-code/builds/504

Seems like the static library still search for libiconv, which seems to
have been retired.

Regards,

Erwan "Dremor" Georget

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

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

Title:
  libxml2 requires libiconv for static build

Status in libxml2 package in Ubuntu:
  New

Bug description:
  Hi.

  I tried to build a software (Ryzomcore, an MMO framework), as a static
  build, but we are facing some unexpected issues :

  https://git.khaganat.net/khaganat/khanat-code/builds/504

  Seems like the static library still search for libiconv, which seems
  to have been retired.

  Regards,

  Erwan "Dremor" Georget

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libxml2/+bug/1641450/+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 1623666] Re: iOS10 will not connect to Ubuntu

2016-11-13 Thread Sam Gleske

J McDonald, I recommend you learning more about public key
infrastructure.  Essentially, encryption and security have different
options available to it (called algorithms and parameters to said
algorithms).  libimobiledevice, using the GnuTLS library, specified
incompatible options for it to work in iOS 10.  When it was built with
another library (OpenSSL instead of GnuTLS), it worked.

TL;DR Ubuntu used GnuTLS version of libimobiledevice which had the bug
and said bug has was fixed in libimobiledevice.

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

Title:
  iOS10 will not connect to Ubuntu

Status in gnutls28 package in Ubuntu:
  Confirmed
Status in libimobiledevice package in Ubuntu:
  Confirmed

Bug description:
  Plug in iOS10 device, and it doesn't show the documents on it.

  Please package the recent fix in libimobiledevice:

  https://github.com/libimobiledevice/libimobiledevice/issues/327

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnutls28/+bug/1623666/+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-11-13 Thread Azusa

You can start chromium with --allow-running-insecure-content option,
this will allow to view sites with not valid certificates.

-- 
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:
  Confirmed

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 1641447] [NEW] Empty marker list in stroke style

2016-11-13 Thread Julien

Public bug reported:

Hello,

I'm using Inkscape 0.91-11 r13725 on Ubuntu 16.10.
The list of markers is empty in stroke style dialog.

I looked at /usr/share/inkscape/markers/markers.svg and found that the
file contains only comments but no svg code.

Getting the file from
 
http://bazaar.launchpad.net/~inkscape.dev/inkscape/trunk/view/head:/share/markers/markers.svg
solved the problem.

Regards.

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

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

Title:
  Empty marker list in stroke style

Status in inkscape package in Ubuntu:
  New

Bug description:
  Hello,

  I'm using Inkscape 0.91-11 r13725 on Ubuntu 16.10.
  The list of markers is empty in stroke style dialog.

  I looked at /usr/share/inkscape/markers/markers.svg and found that the
  file contains only comments but no svg code.

  Getting the file from
   
http://bazaar.launchpad.net/~inkscape.dev/inkscape/trunk/view/head:/share/markers/markers.svg
  solved the problem.

  Regards.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/inkscape/+bug/1641447/+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 1641446] [NEW] gnome-software asks for Ubuntu One SSO authentication for gratis software

2016-11-13 Thread Cryptie

Public bug reported:

What I expected to happen:
Finding the "Nextcloud"" application, clicking on "install" would install 
directly the application without any authentication step.

What actually happened:
a windows prompted asking for Ubuntu One SSO authentication.

Minimal series of steps necessary to make it happen:
- start gnome-software
- search for Nextcloud
- click install

If it can helps: 
This happened in my classical Ubuntu 16.04 LTS and has been reproduced on a 
16.10.
Does not work on my Ubuntu Gnome 16.04.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: gnome-software 3.20.1+git20160923.2.7374bdc-0ubuntu1~xenial1
ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24
Uname: Linux 4.4.0-47-generic i686
NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: i386
CurrentDesktop: Unity
Date: Sun Nov 13 19:52:12 2016
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/gnome-software
InstallationDate: Installed on 2016-01-16 (302 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140417)
ProcEnviron:
 LANGUAGE=fr_FR
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
SourcePackage: gnome-software
UpgradeStatus: Upgraded to xenial on 2016-11-11 (2 days ago)

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


** Tags: apport-bug i386 xenial

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

Title:
  gnome-software asks for Ubuntu One SSO authentication for gratis
  software

Status in gnome-software package in Ubuntu:
  New

Bug description:
  What I expected to happen:
  Finding the "Nextcloud"" application, clicking on "install" would install 
directly the application without any authentication step.

  What actually happened:
  a windows prompted asking for Ubuntu One SSO authentication.

  Minimal series of steps necessary to make it happen:
  - start gnome-software
  - search for Nextcloud
  - click install

  If it can helps: 
  This happened in my classical Ubuntu 16.04 LTS and has been reproduced on a 
16.10.
  Does not work on my Ubuntu Gnome 16.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gnome-software 3.20.1+git20160923.2.7374bdc-0ubuntu1~xenial1
  ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24
  Uname: Linux 4.4.0-47-generic i686
  NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: i386
  CurrentDesktop: Unity
  Date: Sun Nov 13 19:52:12 2016
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/gnome-software
  InstallationDate: Installed on 2016-01-16 (302 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140417)
  ProcEnviron:
   LANGUAGE=fr_FR
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-software
  UpgradeStatus: Upgraded to xenial on 2016-11-11 (2 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1641446/+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-11-13 Thread _omega_

it seems you can also open developer tools and find a direct link to one of the 
rejected URLs, if you then attempt to directly access that link you will be 
given the option to temporarily allow the URL, at which point you will be able 
to view pages that contain the rejected certificate. 
a horrible workaround as well

-- 
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:
  Confirmed

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 1641380] Re: chromium-browser: ERR_CERTIFICATE_TRANSPARENCY_REQUIRED for Symantec certs

2016-11-13 Thread Guanhao Yin

A dirty workaround: disable NTP and set system date a few days back.

-- 
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:
  Confirmed

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 1639180] Re: no login possible after update to nvidia 304.132

2016-11-13 Thread Christian Kroll

Even a tool as innocent as glxinfo fails with an Xsession error similar
to that of the original post. As I am on a Quadro NVS 110M, upgrading to
a newer driver series is not an option. At least non-composited
X-Sessions (e.g. Xfce) still work.

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

Title:
  no login possible after update to nvidia 304.132

Status in nvidia-graphics-drivers-304 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-legacy-304xx package in Debian:
  Confirmed

Bug description:
  Ubuntu 16.04 LTS

  NVIDIA driver:
  - nvidia-graphics-drivers-304
  - update to version 304.132

  dpkg.log:
  upgrade nvidia-304-updates:amd64 304.131-0ubuntu3 304.132-0ubuntu0.16.04.2

  - reboot
  - lightdm login screen
  - login
  - a few seconds some flickering
  - and the lightdm login screen appears again

  It is not possible to login. Unity is not loading.

  .xsession-errors:
  X Error of failed request:  BadValue (integer parameter out of range for 
operation)
Major opcode of failed request:  155 (GLX)
Minor opcode of failed request:  3 (X_GLXCreateContext)
Value in failed request:  0x0
Serial number of failed request:  34
Current serial number in output stream:  35

  See also bug 1634802

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304/+bug/1639180/+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-11-13 Thread Jakob Oswald

Same here, is there a workaround (disable transparency checking in
chrome for now)?

-- 
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:
  Confirmed

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 1641442] [NEW] Import with reneg-sec larger than 65535 fails

2016-11-13 Thread Nick Allen

Public bug reported:

Attempting to import a .ovpn config file with a reneg-sec option larger
than 65535 through the gnome network manager causes the following error
message:


The file 'config.ovpn' could not be read or does not contain recognized VPN 
connection information

Error: configuration error: invalid 1th argument to 'reneg-sec' where
number expected (line 54).

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

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

Title:
  Import with reneg-sec larger than 65535 fails

Status in network-manager-openvpn package in Ubuntu:
  New

Bug description:
  Attempting to import a .ovpn config file with a reneg-sec option
  larger than 65535 through the gnome network manager causes the
  following error message:

  
  The file 'config.ovpn' could not be read or does not contain recognized VPN 
connection information

  Error: configuration error: invalid 1th argument to 'reneg-sec' where
  number expected (line 54).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager-openvpn/+bug/1641442/+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 1641414] Re: ERR_INSECURE_RESPONSE because of BUILD_NOT_TIMELY on many SSL certs which are public

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

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

** Changed in: chromium-browser (Ubuntu)
   Status: New => Confirmed

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

Title:
  ERR_INSECURE_RESPONSE because of BUILD_NOT_TIMELY on many SSL certs
  which are public

Status in chromium-browser package in Ubuntu:
  Confirmed

Bug description:
  Bug filed upstream at
  https://bugs.chromium.org/p/chromium/issues/detail?id=664798# -- added
  here in case the issue is to do with Ubuntu packaging of chromium
  rather than an upstream bug.

  UserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML,
  like Gecko) Ubuntu Chromium/53.0.2785.143 Chrome/53.0.2785.143
  Safari/537.36

  Example URL:
  
https://ir.ebaystatic.com/rtm/3/RTMS/Image/9739_UK_Retail_Q2_RefurbishedTechHub_BREC_300x130.jpg

  Steps to reproduce the problem:
  1. Visit 
https://ir.ebaystatic.com/rtm/3/RTMS/Image/9739_UK_Retail_Q2_RefurbishedTechHub_BREC_300x130.jpg
  2. Observe the Chromium "Your connection is not private" window is shown; 
under advanced, it says "The server presented a certificate that was not 
publicly disclosed using the Certificate Transparency policy. This is a 
requirement for some certificates, to ensure that they are trustworthy and 
protect against attackers."

  What is the expected behavior?
  The image is displayed

  What went wrong?
  chrome://net-internals for this request shows:
  CERT_CT_COMPLIANCE_CHECKED
  build_timely = false
  certificate = (snip)
  ct_compliance_status = "BUILD_NOT_TIMELY"

  The cert for this page seems to be publicly transparent: see
  
https://crt.sh/?q=8E+31+45+71+77+40+9F+31+FC+CE+26+09+25+8B+E7+26+8E+A2+3C+9F+D3+77+80+A2+5B+10+3E+A4+68+DD+32+E1

  Did this work before? Yes don't know; recently

  Chrome version: 53.0.2785.143  Channel: stable
  OS Version: Ubuntu 16.04
  Flash Version: Shockwave Flash 22.0 r0

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: chromium-browser 53.0.2785.143-0ubuntu0.16.04.1.1254
  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: Unity
  DRM.card0-DP-1:
   edid-base64: 
   dpms: Off
   modes: 
   enabled: disabled
   status: disconnected
  DRM.card0-HDMI-A-1:
   edid-base64: 
   dpms: Off
   modes: 
   enabled: disabled
   status: disconnected
  DRM.card0-HDMI-A-2:
   edid-base64: 
   dpms: Off
   modes: 
   enabled: disabled
   status: disconnected
  DRM.card0-HDMI-A-3:
   edid-base64: 
AP///wAEaaMnMvwCAC8XAQOAPCJ4KqWVqlRPoSYKUFS37wDRwLMAlQCBgIFAgQCBwHFPVl4AoKCgKVAwIDUAVVAhAAAa/wBEQkxNVEYxOTU2MzQK/QAYTBhjIQAKICAgICAg/ABBU1VTIFBCMjc4CiAgAQkCAyVxUgECAxESEwQUBQ4PHR4fkCAhIiMJFweDAQAAZQMMABAAjArQiiDgLRAQPpYAVVAhAAAYAR0AclHQHiBuKFUAVVAhAAAeAR0AvFLQHiC4KFVAVVAhAAAejArQkCBAMSAMQFUAVVAhAAAYmA==
   dpms: On
   modes: 2560x1440 1920x1080 1920x1080 1920x1080 1920x1080i 1920x1080i 
1920x1080 1920x1080i 1920x1080 1920x1080 1920x1080 1920x1080 1920x1080 
1680x1050 1280x1024 1280x1024 1440x900 1280x960 1280x800 1152x864 1280x720 
1280x720 1280x720 1440x576 1024x768 1024x768 1024x768 1440x480 1440x480 832x624 
800x600 800x600 800x600 800x600 720x576 720x480 720x480 640x480 640x480 640x480 
640x480 720x400
   enabled: enabled
   status: connected
  DRM.card0-VGA-1:
   edid-base64: 
   dpms: Off
   modes: 
   enabled: disabled
   status: disconnected
  Date: Sun Nov 13 14:43:20 2016
  Desktop-Session:
   'ubuntu'
   '/etc/xdg/xdg-ubuntu:/usr/share/upstart/xdg:/etc/xdg'
   
'/usr/share/ubuntu:/usr/share/gnome:/usr/local/share/:/usr/share/:/var/lib/snapd/desktop'
  Env:
   'None'
   'None'
  InstallationDate: Installed on 2014-04-07 (951 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  Load-Avg-1min: 1.54
  Load-Processes-Running-Percent:   0.1%
  MachineType: ASUS All Series
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-47-generic.efi.signed 
root=UUID=ad1b3110-ee9a-4dac-839d-604080e0020d ro quiet splash vt.handoff=7
  SourcePackage: chromium-browser
  UpgradeStatus: Upgraded to xenial on 2016-08-04 (101 days ago)
  dmi.bios.date: 12/13/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1707
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z87-A
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: PCS
  dmi.chassis.type: 3
  dmi.chassis.vendor: PC SPECIALIST
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1707:bd12/13/2013:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ87-A:rvrRev1.xx:cvnPCSPECIALIST:ct3:cvrChassisVersion:
  dmi.product.name: All Series
  dmi.product.v

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

2016-11-13 Thread Chad Miller

** Changed in: chromium-browser (Ubuntu)
 Assignee: (unassigned) => Chad Miller (cmiller)

** Changed in: chromium-browser (Ubuntu)
   Importance: Undecided => Critical

-- 
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:
  Confirmed

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 1641414] Re: ERR_INSECURE_RESPONSE because of BUILD_NOT_TIMELY on many SSL certs which are public

2016-11-13 Thread Chad Miller

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

** This bug has been marked a duplicate of bug 1641380
   chromium-browser: ERR_CERTIFICATE_TRANSPARENCY_REQUIRED for Symantec certs

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

Title:
  ERR_INSECURE_RESPONSE because of BUILD_NOT_TIMELY on many SSL certs
  which are public

Status in chromium-browser package in Ubuntu:
  Confirmed

Bug description:
  Bug filed upstream at
  https://bugs.chromium.org/p/chromium/issues/detail?id=664798# -- added
  here in case the issue is to do with Ubuntu packaging of chromium
  rather than an upstream bug.

  UserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML,
  like Gecko) Ubuntu Chromium/53.0.2785.143 Chrome/53.0.2785.143
  Safari/537.36

  Example URL:
  
https://ir.ebaystatic.com/rtm/3/RTMS/Image/9739_UK_Retail_Q2_RefurbishedTechHub_BREC_300x130.jpg

  Steps to reproduce the problem:
  1. Visit 
https://ir.ebaystatic.com/rtm/3/RTMS/Image/9739_UK_Retail_Q2_RefurbishedTechHub_BREC_300x130.jpg
  2. Observe the Chromium "Your connection is not private" window is shown; 
under advanced, it says "The server presented a certificate that was not 
publicly disclosed using the Certificate Transparency policy. This is a 
requirement for some certificates, to ensure that they are trustworthy and 
protect against attackers."

  What is the expected behavior?
  The image is displayed

  What went wrong?
  chrome://net-internals for this request shows:
  CERT_CT_COMPLIANCE_CHECKED
  build_timely = false
  certificate = (snip)
  ct_compliance_status = "BUILD_NOT_TIMELY"

  The cert for this page seems to be publicly transparent: see
  
https://crt.sh/?q=8E+31+45+71+77+40+9F+31+FC+CE+26+09+25+8B+E7+26+8E+A2+3C+9F+D3+77+80+A2+5B+10+3E+A4+68+DD+32+E1

  Did this work before? Yes don't know; recently

  Chrome version: 53.0.2785.143  Channel: stable
  OS Version: Ubuntu 16.04
  Flash Version: Shockwave Flash 22.0 r0

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: chromium-browser 53.0.2785.143-0ubuntu0.16.04.1.1254
  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: Unity
  DRM.card0-DP-1:
   edid-base64: 
   dpms: Off
   modes: 
   enabled: disabled
   status: disconnected
  DRM.card0-HDMI-A-1:
   edid-base64: 
   dpms: Off
   modes: 
   enabled: disabled
   status: disconnected
  DRM.card0-HDMI-A-2:
   edid-base64: 
   dpms: Off
   modes: 
   enabled: disabled
   status: disconnected
  DRM.card0-HDMI-A-3:
   edid-base64: 
AP///wAEaaMnMvwCAC8XAQOAPCJ4KqWVqlRPoSYKUFS37wDRwLMAlQCBgIFAgQCBwHFPVl4AoKCgKVAwIDUAVVAhAAAa/wBEQkxNVEYxOTU2MzQK/QAYTBhjIQAKICAgICAg/ABBU1VTIFBCMjc4CiAgAQkCAyVxUgECAxESEwQUBQ4PHR4fkCAhIiMJFweDAQAAZQMMABAAjArQiiDgLRAQPpYAVVAhAAAYAR0AclHQHiBuKFUAVVAhAAAeAR0AvFLQHiC4KFVAVVAhAAAejArQkCBAMSAMQFUAVVAhAAAYmA==
   dpms: On
   modes: 2560x1440 1920x1080 1920x1080 1920x1080 1920x1080i 1920x1080i 
1920x1080 1920x1080i 1920x1080 1920x1080 1920x1080 1920x1080 1920x1080 
1680x1050 1280x1024 1280x1024 1440x900 1280x960 1280x800 1152x864 1280x720 
1280x720 1280x720 1440x576 1024x768 1024x768 1024x768 1440x480 1440x480 832x624 
800x600 800x600 800x600 800x600 720x576 720x480 720x480 640x480 640x480 640x480 
640x480 720x400
   enabled: enabled
   status: connected
  DRM.card0-VGA-1:
   edid-base64: 
   dpms: Off
   modes: 
   enabled: disabled
   status: disconnected
  Date: Sun Nov 13 14:43:20 2016
  Desktop-Session:
   'ubuntu'
   '/etc/xdg/xdg-ubuntu:/usr/share/upstart/xdg:/etc/xdg'
   
'/usr/share/ubuntu:/usr/share/gnome:/usr/local/share/:/usr/share/:/var/lib/snapd/desktop'
  Env:
   'None'
   'None'
  InstallationDate: Installed on 2014-04-07 (951 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  Load-Avg-1min: 1.54
  Load-Processes-Running-Percent:   0.1%
  MachineType: ASUS All Series
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-47-generic.efi.signed 
root=UUID=ad1b3110-ee9a-4dac-839d-604080e0020d ro quiet splash vt.handoff=7
  SourcePackage: chromium-browser
  UpgradeStatus: Upgraded to xenial on 2016-08-04 (101 days ago)
  dmi.bios.date: 12/13/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1707
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z87-A
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: PCS
  dmi.chassis.type: 3
  dmi.chassis.vendor: PC SPECIALIST
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1707:bd12/13/2013:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ87-A:rvrRev1.xx:cvnPCSPECIALIST:ct3:cvrChassisVersion:
  dmi.product.name: All Series
  dmi.product.version: Sys

[Desktop-packages] [Bug 1632027] Re: New Document feature missing from Nautilus 3.20+

2016-11-13 Thread StefG BZ

To have the "New Document" menu item back in the mean time, just add an
empty file named "empty" for example in ~/Templates.

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

Title:
  New Document feature missing from Nautilus 3.20+

Status in nautilus package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu has a patch ( 16_unity_new_documents.patch ) to enable a 'New
  Document' function in the right-click context menu. This patch was not
  ported to Nautilus 3.20 so this Ubuntu-specific feature is missing in
  Ubuntu 16.10.

  While this patch being disabled is noted in the debian/changelog,
  here's a formal bug to document the issue and maybe give it a bit more
  visibility so that it will be fixed.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: nautilus 1:3.20.3-1ubuntu3
  ProcVersionSignature: Ubuntu 4.8.0-17.19-generic 4.8.0-rc7
  Uname: Linux 4.8.0-17-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Oct 10 12:54:50 2016
  EcryptfsInUse: Yes
  GsettingsChanges:
   b'org.gnome.nautilus.preferences' b'open-folder-on-dnd-hover' b'false'
   b'org.gnome.nautilus.window-state' b'sidebar-width' b'171'
   b'org.gnome.nautilus.window-state' b'geometry' b"'1106x542+436+438'"
   b'org.gnome.nautilus.icon-view' b'default-zoom-level' b"'small'"
  InstallationDate: Installed on 2016-08-11 (59 days ago)
  InstallationMedia: Ubuntu-GNOME 16.10 "Yakkety Yak" - Alpha amd64 (20160811)
  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/1632027/+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 665233] Re: Ubuntu Maverick with ATI RADEON screen corruption

2016-11-13 Thread Hervé Fache

To be complete, I only need to add nomodeset to
GRUB_CMDLINE_LINUX_DEFAULT to get rid of the flicker.

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

Title:
  Ubuntu Maverick with ATI RADEON screen corruption

Status in xserver-xorg-video-ati package in Ubuntu:
  Expired

Bug description:
  Binary package hint: xorg

  Since Maverick my screen looks like the file attached. With lucid lynx
  I had no problems.

  The kernel http://kernel.ubuntu.com/~kernel-ppa/mainline/v2.6.34-lucid
  solves the problem, but it is not an official one.

  Also, but I don't know if it is related, I can't resume the computer
  after suspension or hibernation.

  Thanks!

  ProblemType: Bug
  DistroRelease: Ubuntu 10.10
  Package: xorg 1:7.5+6ubuntu3
  ProcVersionSignature: Ubuntu 2.6.35-22.35-generic 2.6.35.4
  Uname: Linux 2.6.35-22-generic x86_64
  Architecture: amd64
  DRM.card0.HDMI_Type_A.1:
   status: disconnected
   enabled: disabled
   dpms: On
   modes: 
   edid-base64:
  DRM.card0.LVDS.1:
   status: connected
   enabled: enabled
   dpms: On
   modes: 1280x800 1280x720 1152x768 1024x768 800x600 848x480 720x480 640x480
   edid-base64: 
AP///wAGEF6cAAkQAQOAHRN4CmUhn1hVhyopUFQBAQEBAQEBAQEBAQEBAQEBvBsAoFAgFzAwIDYAHrIQAAAYAQAGECog/gBOMTMzSTEtTDAxCiAg/ABDb2xvciBMQ0QKICAgAGE=
  DRM.card0.VGA.1:
   status: disconnected
   enabled: disabled
   dpms: On
   modes: 
   edid-base64:
  Date: Fri Oct 22 14:20:32 2010
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
  MachineType: Micro-Star International PR310
  ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.35-22-generic 
root=UUID=ae104f9b-e117-484b-a5fa-8b5098e8b5c4 ro quiet splash
  ProcEnviron:
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: xorg
  Symptom: display
  dmi.bios.date: 12/05/2007
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: A1335AMS V3.07
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: MS-1335
  dmi.board.vendor: MSI
  dmi.board.version: Ver 1.000
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 10
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrA1335AMSV3.07:bd12/05/2007:svnMicro-StarInternational:pnPR310:pvrMS-1335X:rvnMSI:rnMS-1335:rvrVer1.000:cvnToBeFilledByO.E.M.:ct10:cvrToBeFilledByO.E.M.:
  dmi.product.name: PR310
  dmi.product.version: MS-1335X
  dmi.sys.vendor: Micro-Star International
  glxinfo: Error: [Errno 2] No such file or directory
  system:
   distro: Ubuntu
   codename:   maverick
   architecture:   x86_64
   kernel: 2.6.35-22-generic

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/665233/+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 1623666] Re: iOS10 will not connect to Ubuntu

2016-11-13 Thread J. McDonald

So if this is resolved, could someone provide an answer that doesn't
require a PhD in computer science to figure out?

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

Title:
  iOS10 will not connect to Ubuntu

Status in gnutls28 package in Ubuntu:
  Confirmed
Status in libimobiledevice package in Ubuntu:
  Confirmed

Bug description:
  Plug in iOS10 device, and it doesn't show the documents on it.

  Please package the recent fix in libimobiledevice:

  https://github.com/libimobiledevice/libimobiledevice/issues/327

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnutls28/+bug/1623666/+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 665233] Re: Ubuntu Maverick with ATI RADEON screen corruption

2016-11-13 Thread Hervé Fache

5 and a half years later, and comment #7 fixed the issue on my DM1Z
running yakkety.

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

Title:
  Ubuntu Maverick with ATI RADEON screen corruption

Status in xserver-xorg-video-ati package in Ubuntu:
  Expired

Bug description:
  Binary package hint: xorg

  Since Maverick my screen looks like the file attached. With lucid lynx
  I had no problems.

  The kernel http://kernel.ubuntu.com/~kernel-ppa/mainline/v2.6.34-lucid
  solves the problem, but it is not an official one.

  Also, but I don't know if it is related, I can't resume the computer
  after suspension or hibernation.

  Thanks!

  ProblemType: Bug
  DistroRelease: Ubuntu 10.10
  Package: xorg 1:7.5+6ubuntu3
  ProcVersionSignature: Ubuntu 2.6.35-22.35-generic 2.6.35.4
  Uname: Linux 2.6.35-22-generic x86_64
  Architecture: amd64
  DRM.card0.HDMI_Type_A.1:
   status: disconnected
   enabled: disabled
   dpms: On
   modes: 
   edid-base64:
  DRM.card0.LVDS.1:
   status: connected
   enabled: enabled
   dpms: On
   modes: 1280x800 1280x720 1152x768 1024x768 800x600 848x480 720x480 640x480
   edid-base64: 
AP///wAGEF6cAAkQAQOAHRN4CmUhn1hVhyopUFQBAQEBAQEBAQEBAQEBAQEBvBsAoFAgFzAwIDYAHrIQAAAYAQAGECog/gBOMTMzSTEtTDAxCiAg/ABDb2xvciBMQ0QKICAgAGE=
  DRM.card0.VGA.1:
   status: disconnected
   enabled: disabled
   dpms: On
   modes: 
   edid-base64:
  Date: Fri Oct 22 14:20:32 2010
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
  MachineType: Micro-Star International PR310
  ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.35-22-generic 
root=UUID=ae104f9b-e117-484b-a5fa-8b5098e8b5c4 ro quiet splash
  ProcEnviron:
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: xorg
  Symptom: display
  dmi.bios.date: 12/05/2007
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: A1335AMS V3.07
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: MS-1335
  dmi.board.vendor: MSI
  dmi.board.version: Ver 1.000
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 10
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrA1335AMSV3.07:bd12/05/2007:svnMicro-StarInternational:pnPR310:pvrMS-1335X:rvnMSI:rnMS-1335:rvrVer1.000:cvnToBeFilledByO.E.M.:ct10:cvrToBeFilledByO.E.M.:
  dmi.product.name: PR310
  dmi.product.version: MS-1335X
  dmi.sys.vendor: Micro-Star International
  glxinfo: Error: [Errno 2] No such file or directory
  system:
   distro: Ubuntu
   codename:   maverick
   architecture:   x86_64
   kernel: 2.6.35-22-generic

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/665233/+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 1638177] Re: libimobiledevice: GnuTLS does not work with iOS10

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

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

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

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

Title:
  libimobiledevice: GnuTLS does not work with iOS10

Status in libimobiledevice package in Ubuntu:
  Confirmed

Bug description:
  Problem:
  The libimobiledevice package for Ubuntu was built with --disable-openssl 
which forces GnuTLS.  GnuTLS does not work with the recent iOS10 update.

  Solution: rebuild the package so that it links against OpenSSL again.
  This will resolve issues connecting to iOS 10 devices.

  I tested the latest development version of GnuTLS (@ commit
  1e84b90feed97ee458b7113665300e6bc444798f of master HEAD) and it does
  not work with iOS 10 devices.

  Upstream issue reference:
  https://github.com/libimobiledevice/ifuse/issues/32

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libimobiledevice/+bug/1638177/+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 1625819] Re: gedit is stuck starting, no window is shown

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

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

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

Title:
  gedit is stuck starting, no window is shown

Status in gedit package in Ubuntu:
  Confirmed

Bug description:
  I use VPN to log to my workplace which uses proxy.
  I don't know if the proxy is an issue, but with or without $http_proxy set, 
gedit won't start properly.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gedit 3.18.3-0ubuntu4
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  Uname: Linux 4.4.0-38-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Sep 20 22:10:49 2016
  InstallationDate: Installed on 2016-06-26 (86 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: gedit
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1625819/+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 1641417] [NEW] Ubuntu 16.04 unable to detect/connect to and work properly with iPhone 4.

2016-11-13 Thread SunBear

Public bug reported:


Action 1: Plug an iPhone 4 to a just booted up Ubuntu 16.04 workstation. 
Result 1: 2 iPhone connections appear in Nautilus. 1st connect is mount via 
gphoto2, where access is limited to viewing and copying photos and videos. The 
2nd connection that is mounted via afc fail to work, hence other folders in 
iPhone are not accessible.

Action 2: Unplugged and re-plugged iPhone 4 to the workstation.
Result 2: iPhone 4 does not reappear in Nautilus at all. No iPhone mount point 
appear.

Checks and Remedy used: 
1. "ideviceinfo" and lsusb command show iPhone 4 is connected.
2. "idevicepair validate" command shows "SUCCESS: Validated pairing with device 
[UDID]"
3. After running "ifuse /media/iPhone" command, iPhone 4 reappears in Nautilus 
as mounted in /media/iPhone. Furthermore, all folders of iPhone 4 appears and 
are accessible.

I believe the 1st mounting of iPhone 4 on Nautilus is due to the "gvfs-
backends" package. W/o it, auto detection/connection of iPhone 4 would
not occur and appear in Nautilus. However, the afc mount failed to work

The 2nd mounting is caused by ifuse. This works perfectly but requires
manual mounting and unmounting.


Questions: 
1. How to overcome issues/failures mentioned in Result 1 & 2? 
2. Ideally, i would like the automatic detection-connection between Ubuntu and 
iPhone to work. If not, is there a way to automate connection via ifuse? 


System and package info:

$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 16.04.1 LTS
Release:16.04
Codename:   xenial

$ uname -or
4.4.0-47-generic GNU/Linux

$ dpkg -l | grep iPhone
ii  ifuse1.1.2-0.1build3 amd64  FUSE module for 
iPhone and iPod Touch devices
ii  libimobiledevice-utils   1.2.0+dfsg-3~ubuntu0.2  amd64  Library for 
communicating with iPhone and iPod Touch devices
ii  libimobiledevice6:amd64  1.2.0+dfsg-3~ubuntu0.2  amd64  Library for 
communicating with the iPhone and iPod Touch
ii  libusbmuxd-tools 1.0.10-2ubuntu0.1   amd64  USB multiplexor 
daemon for iPhone and iPod Touch devices - tools
ii  libusbmuxd4:amd641.0.10-2ubuntu0.1   amd64  USB multiplexor 
daemon for iPhone and iPod Touch devices - library
ii  usbmuxd  1.1.0-2 amd64  USB multiplexor 
daemon for iPhone and iPod Touch devices

$ dpkg -l | grep libusb
ii  libgusb2:amd64   0.2.9-0ubuntu1  amd64   GLib wrapper around 
libusb1
ii  libusb-0.1-4:amd64   2:0.1.12-28 amd64   userspace USB 
programming library
ii  libusb-1.0-0:amd64   2:1.0.20-1  amd64   userspace USB 
programming library
ii  libusb-1.0-0:i3862:1.0.20-1  i386userspace USB 
programming library
ii  libusbmuxd-tools 1.0.10-2ubuntu0.1   amd64   USB multiplexor daemon 
for iPhone and iPod Touch devices - tools
ii  libusbmuxd4:amd641.0.10-2ubuntu0.1   amd64   USB multiplexor daemon 
for iPhone and iPod Touch devices - library
ii  libusbredirhost1:amd64   0.7.1-1 amd64   Implementing the 
usb-host (*) side of a usbredir connection (runtime)
ii  libusbredirparser1:amd64 0.7.1-1 amd64   Parser for the 
usbredir protocol (runtime)

$ dpkg -l | grep gvfs
ii  gvfs:amd64  1.28.2-1ubuntu1~16.04.1amd64  userspace virtual 
filesystem - GIO module
ii  gvfs-backends   1.28.2-1ubuntu1~16.04.1amd64  userspace virtual 
filesystem - backends
ii  gvfs-bin1.28.2-1ubuntu1~16.04.1amd64  userspace virtual 
filesystem - binaries
ii  gvfs-common 1.28.2-1ubuntu1~16.04.1alluserspace virtual 
filesystem - common data files
ii  gvfs-daemons1.28.2-1ubuntu1~16.04.1amd64  userspace virtual 
filesystem - servers
ii  gvfs-fuse   1.28.2-1ubuntu1~16.04.1amd64  userspace virtual 
filesystem - fuse server
ii  gvfs-libs:amd64 1.28.2-1ubuntu1~16.04.1amd64  userspace virtual 
filesystem - private libraries

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

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

Title:
  Ubuntu 16.04 unable to detect/connect  to and work properly with
  iPhone 4.

Status in libimobiledevice package in Ubuntu:
  New

Bug description:
  
  Action 1: Plug an iPhone 4 to a just booted up Ubuntu 16.04 workstation. 
  Result 1: 2 iPhone connections appear in Nautilus. 1st connect is mount via 
gphoto2, where access is limited to viewing and copying photos and videos. The 
2nd connection that is mounted via afc fail to work, hence other folders in 
iPhone are not accessible.

  Action 2: Unplugged and re-plugged iPhone 4 to the workstation.
  Result 2: iPhone 4 does not reappear in Nautilus at all. No iPhone mount 
point appear.

  Checks and Remedy used: 
  1. "ideviceinfo" and lsusb command show iPhone 4 is connected.
  2. "idevicepair validate" comman

[Desktop-packages] [Bug 1641416] [NEW] A core of the CPU always reloaded after restart

2016-11-13 Thread Piotr

Public bug reported:

When the computer is started or rebooted, a core of the CPU is always at least 
90% loaded. When the Xorg process is terminated via the system monitor, 
everything is fine.
A complete new installation did not fix the problem either.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24
Uname: Linux 4.4.0-47-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
Date: Sun Nov 13 15:33:11 2016
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
GraphicsCard:
 Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0156] (rev 
09) (prog-if 00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. 3rd Gen Core processor Graphics Controller 
[1043:14c7]
InstallationDate: Installed on 2016-11-13 (0 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
MachineType: ASUSTeK COMPUTER INC. X75A1
ProcEnviron:
 LANGUAGE=de_DE
 PATH=(custom, no user)
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-47-generic 
root=UUID=c1ff67b4-45e1-49de-ad32-9a1d8766b6b7 ro drm.debug=0xe plymouth:debug
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/26/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: X75A1.410
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: X75A1
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX75A1.410:bd12/26/2012:svnASUSTeKCOMPUTERINC.:pnX75A1:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX75A1:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.name: X75A1
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.
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.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
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: Sun Nov 13 15:31:47 2016
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id   12623 
 vendor SEC
xserver.version: 2:1.18.4-0ubuntu0.1

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


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

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

Title:
  A core of the CPU always reloaded after restart

Status in xorg package in Ubuntu:
  New

Bug description:
  When the computer is started or rebooted, a core of the CPU is always at 
least 90% loaded. When the Xorg process is terminated via the system monitor, 
everything is fine.
  A complete new installation did not fix the problem either.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24
  Uname: Linux 4.4.0-47-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
  Date: Sun Nov 13 15:33:11 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0156] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. 3rd Gen Core processor Graphics 
Controller [1043:14c7]
  InstallationDate: Installed on 2016-11-13 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: ASUSTeK COMPUTER INC. X75A1
  ProcEnviron:
   LANGUAGE=de_DE
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-47-generic 
root=UUID=c1ff67b4-45e1-49de-ad32-9a1d8766b6b7 ro drm.de

[Desktop-packages] [Bug 1641415] [NEW] screen dimmed after suspend

2016-11-13 Thread veddox

Public bug reported:

Often, waking the computer up from suspend will cause the screen
brightness to be set right down (was 100% before suspend, becomes ~ 20%
after waking). This happens during 40-70% of all suspends. I have not
yet been able to figure out any correlations with previous activity, so
the behaviour seems random.

(I assume this is a LightDM problem, because it first manifests itself
in the login screen, but I'm not sure.)

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: lightdm 1.18.3-0ubuntu1
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: Unity
Date: Sun Nov 13 15:39:26 2016
InstallationDate: Installed on 2016-07-15 (120 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
SourcePackage: lightdm
UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  screen dimmed after suspend

Status in lightdm package in Ubuntu:
  New

Bug description:
  Often, waking the computer up from suspend will cause the screen
  brightness to be set right down (was 100% before suspend, becomes ~
  20% after waking). This happens during 40-70% of all suspends. I have
  not yet been able to figure out any correlations with previous
  activity, so the behaviour seems random.

  (I assume this is a LightDM problem, because it first manifests itself
  in the login screen, but I'm not sure.)

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: lightdm 1.18.3-0ubuntu1
  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: Unity
  Date: Sun Nov 13 15:39:26 2016
  InstallationDate: Installed on 2016-07-15 (120 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1641415/+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 1641414] [NEW] ERR_INSECURE_RESPONSE because of BUILD_NOT_TIMELY on many SSL certs which are public

2016-11-13 Thread Stuart Langridge

Public bug reported:

Bug filed upstream at
https://bugs.chromium.org/p/chromium/issues/detail?id=664798# -- added
here in case the issue is to do with Ubuntu packaging of chromium rather
than an upstream bug.

UserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML,
like Gecko) Ubuntu Chromium/53.0.2785.143 Chrome/53.0.2785.143
Safari/537.36

Example URL:
https://ir.ebaystatic.com/rtm/3/RTMS/Image/9739_UK_Retail_Q2_RefurbishedTechHub_BREC_300x130.jpg

Steps to reproduce the problem:
1. Visit 
https://ir.ebaystatic.com/rtm/3/RTMS/Image/9739_UK_Retail_Q2_RefurbishedTechHub_BREC_300x130.jpg
2. Observe the Chromium "Your connection is not private" window is shown; under 
advanced, it says "The server presented a certificate that was not publicly 
disclosed using the Certificate Transparency policy. This is a requirement for 
some certificates, to ensure that they are trustworthy and protect against 
attackers."

What is the expected behavior?
The image is displayed

What went wrong?
chrome://net-internals for this request shows:
CERT_CT_COMPLIANCE_CHECKED
build_timely = false
certificate = (snip)
ct_compliance_status = "BUILD_NOT_TIMELY"

The cert for this page seems to be publicly transparent: see
https://crt.sh/?q=8E+31+45+71+77+40+9F+31+FC+CE+26+09+25+8B+E7+26+8E+A2+3C+9F+D3+77+80+A2+5B+10+3E+A4+68+DD+32+E1

Did this work before? Yes don't know; recently

Chrome version: 53.0.2785.143  Channel: stable
OS Version: Ubuntu 16.04
Flash Version: Shockwave Flash 22.0 r0

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: chromium-browser 53.0.2785.143-0ubuntu0.16.04.1.1254
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: Unity
DRM.card0-DP-1:
 edid-base64: 
 dpms: Off
 modes: 
 enabled: disabled
 status: disconnected
DRM.card0-HDMI-A-1:
 edid-base64: 
 dpms: Off
 modes: 
 enabled: disabled
 status: disconnected
DRM.card0-HDMI-A-2:
 edid-base64: 
 dpms: Off
 modes: 
 enabled: disabled
 status: disconnected
DRM.card0-HDMI-A-3:
 edid-base64: 
AP///wAEaaMnMvwCAC8XAQOAPCJ4KqWVqlRPoSYKUFS37wDRwLMAlQCBgIFAgQCBwHFPVl4AoKCgKVAwIDUAVVAhAAAa/wBEQkxNVEYxOTU2MzQK/QAYTBhjIQAKICAgICAg/ABBU1VTIFBCMjc4CiAgAQkCAyVxUgECAxESEwQUBQ4PHR4fkCAhIiMJFweDAQAAZQMMABAAjArQiiDgLRAQPpYAVVAhAAAYAR0AclHQHiBuKFUAVVAhAAAeAR0AvFLQHiC4KFVAVVAhAAAejArQkCBAMSAMQFUAVVAhAAAYmA==
 dpms: On
 modes: 2560x1440 1920x1080 1920x1080 1920x1080 1920x1080i 1920x1080i 1920x1080 
1920x1080i 1920x1080 1920x1080 1920x1080 1920x1080 1920x1080 1680x1050 
1280x1024 1280x1024 1440x900 1280x960 1280x800 1152x864 1280x720 1280x720 
1280x720 1440x576 1024x768 1024x768 1024x768 1440x480 1440x480 832x624 800x600 
800x600 800x600 800x600 720x576 720x480 720x480 640x480 640x480 640x480 640x480 
720x400
 enabled: enabled
 status: connected
DRM.card0-VGA-1:
 edid-base64: 
 dpms: Off
 modes: 
 enabled: disabled
 status: disconnected
Date: Sun Nov 13 14:43:20 2016
Desktop-Session:
 'ubuntu'
 '/etc/xdg/xdg-ubuntu:/usr/share/upstart/xdg:/etc/xdg'
 
'/usr/share/ubuntu:/usr/share/gnome:/usr/local/share/:/usr/share/:/var/lib/snapd/desktop'
Env:
 'None'
 'None'
InstallationDate: Installed on 2014-04-07 (951 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1)
Load-Avg-1min: 1.54
Load-Processes-Running-Percent:   0.1%
MachineType: ASUS All Series
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-47-generic.efi.signed 
root=UUID=ad1b3110-ee9a-4dac-839d-604080e0020d ro quiet splash vt.handoff=7
SourcePackage: chromium-browser
UpgradeStatus: Upgraded to xenial on 2016-08-04 (101 days ago)
dmi.bios.date: 12/13/2013
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1707
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: Z87-A
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: PCS
dmi.chassis.type: 3
dmi.chassis.vendor: PC SPECIALIST
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1707:bd12/13/2013:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ87-A:rvrRev1.xx:cvnPCSPECIALIST:ct3:cvrChassisVersion:
dmi.product.name: All Series
dmi.product.version: System Version
dmi.sys.vendor: ASUS
etcconfigcpepperflashpluginnonfree:
 flashso="/usr/lib/pepperflashplugin-nonfree/libpepflashplayer.so"
 flashversion=`strings $flashso 2> /dev/null | grep LNX | cut -d ' ' -f 2 | sed 
-e "s/,/./g"`
 CHROMIUM_FLAGS="$CHROMIUM_FLAGS --ppapi-flash-path=$flashso 
--ppapi-flash-version=$flashversion"
gconf-keys: /desktop/gnome/applications/browser/exec = 
b'/usr/bin/chromium-browser\n'/desktop/gnome/url-handlers/https/command = 
b'/usr/bin/chromium-browser %s\n'/desktop/gnome/url-handlers/https/enabled = 
b'true\n'/desktop/gnome/url-handlers/http/command = b'/usr/bin/chromium-browser 
%s\n'/desktop/gnome/url-handlers/http/enabled = 
b'true\n'/desktop/gnome/session/required_components/windowmanager = 
b''/app

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

2016-11-13 Thread Guanhao Yin

** Description changed:

- Chromium browser in xenial no longer trusts Symantec or Geotrust issued
+ 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

-- 
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:
  Confirmed

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 1641380] Re: chromium-browser: ERR_CERTIFICATE_TRANSPARENCY_REQUIRED for Symantec certs

2016-11-13 Thread Guanhao Yin

** Summary changed:

- Xenial: ERR_CERTIFICATE_TRANSPARENCY_REQUIRED for Symantec and Geotrust certs
+ chromium-browser: ERR_CERTIFICATE_TRANSPARENCY_REQUIRED for Symantec certs

-- 
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:
  Confirmed

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 1226962] Re: Hotkeys not functional in non-latin keyboard layout

2016-11-13 Thread ZoLToR

Just use another keyboard switcher (e.g., gxkb) and keep only one
English layout in system layout switcher. I tried gxkb and all worked
fine but some another issues appeared, which specific to gxkb (e.g.,
when laptop was waking up from the sleep mode, gxkb settings were
resetting. Also, I didn't see gxkb indicator on the lock screen, so
sometime I entered the password on wrong layout). But I almost didn't
notice this gxkb-specific issues in comparison with this idiotic
annoying issue in unity-settings-daemon, which cannot be fixed so long
time (wtf? Developers are fixing the result of this issue by adding some
"bicycles" to software where this issue is persist, but they aren't
fixing the ROOT CAUSE in unity-setting-daemon -_-" )

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

Title:
  Hotkeys not functional in non-latin keyboard layout

Status in aptana-studio-installer:
  New
Status in Default settings and artwork for Baltix OS:
  New
Status in LibreOffice:
  Fix Released
Status in ibus:
  New
Status in Indicator keyboard:
  Fix Released
Status in Inkscape:
  New
Status in Intellij Idea:
  New
Status in monodevelop:
  New
Status in mutter:
  Fix Released
Status in okular:
  New
Status in OpenOffice:
  New
Status in sigram:
  New
Status in Unity:
  Fix Released
Status in gnome-settings-daemon package in Ubuntu:
  Triaged
Status in gnome-terminal package in Ubuntu:
  Triaged
Status in kdevelop package in Ubuntu:
  Confirmed
Status in openjdk-7 package in Ubuntu:
  Incomplete
Status in unity package in Ubuntu:
  Fix Released
Status in unity-settings-daemon package in Ubuntu:
  In Progress
Status in gnome-settings-daemon source package in Xenial:
  Triaged
Status in gnome-terminal source package in Xenial:
  Triaged
Status in kdevelop source package in Xenial:
  Confirmed
Status in openjdk-7 source package in Xenial:
  Incomplete
Status in unity source package in Xenial:
  Fix Released
Status in unity-settings-daemon source package in Xenial:
  In Progress
Status in gnome-shell package in Fedora:
  Unknown
Status in openoffice package in Fedora:
  Unknown

Bug description:
  New keyboard layout changer in Ubuntu 13.10 introduce  old-new bug. Any 
system or application hotkey witch use char (for example: ctrl+alt+t for 
terminal or ctrl+t for new tab in browser) become unfunctional when selected 
non-latin keyboard layout.
  Hotkeys with F1-12, numbers and other non-character buttons works perfectly.

  Window manager hotkeys not affected by this bug. All hotkeys in system
  parameters->keyboard->hotkeys->windows works perfect with any keyboard
  layout.

  Workaround for some system hotkeys and two layouts (english and non-
  latin): rebind all hotkeys in your local layout. For example instead
  of ctrl+alt+t use ctrl+alt+τ (greek tau). That hotkey still work with
  english layout.  If you use english and two different non-latin
  layouts this workaround helps only with one of them.


  Dear Ubuntu users and developers! 
  Please include the following information to your comment about non-latin 
shortcuts problems:
  1. What Ubuntu version do you have (Ubuntu 13.10, Ubuntu 13.10 GNOME, Ubuntu 
14.04, Ubuntu 14.04 GNOME and so on), upgraded (describe version) or clean 
installed
  2. What keyboard layout do you have
  3. What shortcut for keyboard layout switching do you use 
  4. On which session you have problems - that is one from Unity, GNOME Shell, 
GNOME FlashBack/Fallback (Metacity), GNOME FlashBack/Fallback (Compiz)
  5. With which program and its version and origin (Ubuntu repositories, PPA, 
non-deb binary package from some website) you have problems.

  By providing this information you can make bug-fixing much simpler and
  may be faster.

  --
  For other layout switching problems introduced in Ubuntu 13.10 you can see 
bug 1218322.
  --

To manage notifications about this bug go to:
https://bugs.launchpad.net/aptana-studio-installer/+bug/1226962/+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 1622730] Re: No sound on headphones after suspend

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

** Changed in: alsa-driver (Ubuntu)
   Status: New => Confirmed

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

Title:
  No sound on headphones after suspend

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  This seems to be a common problem on XMG Clevo W230SS there is no
  output on the headphone jack after suspend. The headphones are
  detected and the speakers are muted, but there is no output to the
  headphones. Init-headphones does not help:

  sudo init-headphone 
  WARNING:root:Kernel parameter is missing: acpi_enforce_resources=lax
  WARNING:root:Module is not loaded: i2c_dev
  ERROR:root:Can't find i2c bus
  ERROR:root:Operation failed

  Any workaround beside reboot?

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
  Uname: Linux 4.4.0-36-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USER PID ACCESS COMMAND
   /dev/snd/controlC1:  pia   23276 F pulseaudio
   /dev/snd/controlC0:  pia   23276 F pulseaudio
  CurrentDesktop: GNOME-Classic:GNOME
  Date: Mon Sep 12 21:56:08 2016
  InstallationDate: Installed on 2015-11-05 (312 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/15/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.5
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: W230SS
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd04/15/2014:svnNotebook:pnW230SS:pvrNotApplicable:rvnNotebook:rnW230SS:rvrNotApplicable:cvnNotebook:ct9:cvrN/A:
  dmi.product.name: W230SS
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook
  modified.conffile..etc.modprobe.d.alsa-base.conf: [modified]
  mtime.conffile..etc.modprobe.d.alsa-base.conf: 2016-02-15T00:43:38.504815

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1622730/+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: Xenial: ERR_CERTIFICATE_TRANSPARENCY_REQUIRED for Symantec and Geotrust certs

2016-11-13 Thread Michael Löffler

>From one day to another it tells me half of my websites would use
invalid certificates. The bug report for chrome describes it quite well
as a ticking time bomb. Would be great to see 53 replaced quickly with
54 in mainline ubuntu.

-- 
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:
  Xenial: ERR_CERTIFICATE_TRANSPARENCY_REQUIRED for Symantec and
  Geotrust certs

Status in chromium-browser package in Ubuntu:
  Confirmed

Bug description:
  Chromium browser in xenial no longer trusts Symantec or Geotrust
  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 1641393] Re: 'Elan Touchpad' not detected in Ubuntu 16.04.1 Gigabyte P57K-965-603S Fresh install

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

Title:
  'Elan Touchpad' not detected in Ubuntu 16.04.1 Gigabyte P57K-965-603S
  Fresh install

Status in xserver-xorg-video-sis package in Ubuntu:
  New

Bug description:
  On a fresh install of Ubuntu 16.04.1 (July 27 2016, downloaded
  November 13 2016 from the official site) on the above machine, the
  Elan touchpad was not detected at all.  An external mouse works
  perfectly.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-sis/+bug/1641393/+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 1641393] Re: 'Elan Touchpad' not detected in Ubuntu 16.04.1 Gigabyte P57K-965-603S Fresh install

** Attachment added: "lsmod"
   
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-sis/+bug/1641393/+attachment/4776796/+files/lsmod

** Description changed:

- On a fresh install of Ubuntu 16.04.1 (July 27 2016) on the above
- machine, the Elan touchpad was not detected at all.  An external mouse
- works perfectly.
+ On a fresh install of Ubuntu 16.04.1 (July 27 2016, downloaded November
+ 13 2016 from the official site) on the above machine, the Elan touchpad
+ was not detected at all.  An external mouse works perfectly.

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

Title:
  'Elan Touchpad' not detected in Ubuntu 16.04.1 Gigabyte P57K-965-603S
  Fresh install

Status in xserver-xorg-video-sis package in Ubuntu:
  New

Bug description:
  On a fresh install of Ubuntu 16.04.1 (July 27 2016, downloaded
  November 13 2016 from the official site) on the above machine, the
  Elan touchpad was not detected at all.  An external mouse works
  perfectly.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-sis/+bug/1641393/+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 1641393] Re: 'Elan Touchpad' not detected in Ubuntu 16.04.1 Gigabyte P57K-965-603S Fresh install

** Attachment added: "lspci"
   
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-sis/+bug/1641393/+attachment/4776792/+files/lspci

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

Title:
  'Elan Touchpad' not detected in Ubuntu 16.04.1 Gigabyte P57K-965-603S
  Fresh install

Status in xserver-xorg-video-sis package in Ubuntu:
  New

Bug description:
  On a fresh install of Ubuntu 16.04.1 (July 27 2016, downloaded
  November 13 2016 from the official site) on the above machine, the
  Elan touchpad was not detected at all.  An external mouse works
  perfectly.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-sis/+bug/1641393/+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: Xenial: ERR_CERTIFICATE_TRANSPARENCY_REQUIRED for Symantec and Geotrust certs

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

** Changed in: chromium-browser (Ubuntu)
   Status: New => Confirmed

-- 
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:
  Xenial: ERR_CERTIFICATE_TRANSPARENCY_REQUIRED for Symantec and
  Geotrust certs

Status in chromium-browser package in Ubuntu:
  Confirmed

Bug description:
  Chromium browser in xenial no longer trusts Symantec or Geotrust
  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 1641393] Re: 'Elan Touchpad' not detected in Ubuntu 16.04.1 Gigabyte P57K-965-603S Fresh install

** Attachment added: "Xorg.0.log_diff"
   
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-sis/+bug/1641393/+attachment/4776779/+files/Xorg.0.log_diff

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

Title:
  'Elan Touchpad' not detected in Ubuntu 16.04.1 Gigabyte P57K-965-603S
  Fresh install

Status in xserver-xorg-video-sis package in Ubuntu:
  New

Bug description:
  On a fresh install of Ubuntu 16.04.1 (July 27 2016) on the above
  machine, the Elan touchpad was not detected at all.  An external mouse
  works perfectly.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-sis/+bug/1641393/+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 1641393] Re: 'Elan Touchpad' not detected in Ubuntu 16.04.1 Gigabyte P57K-965-603S Fresh install

** Attachment added: "dmesg"
   
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-sis/+bug/1641393/+attachment/4776781/+files/dmesg

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

Title:
  'Elan Touchpad' not detected in Ubuntu 16.04.1 Gigabyte P57K-965-603S
  Fresh install

Status in xserver-xorg-video-sis package in Ubuntu:
  New

Bug description:
  On a fresh install of Ubuntu 16.04.1 (July 27 2016) on the above
  machine, the Elan touchpad was not detected at all.  An external mouse
  works perfectly.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-sis/+bug/1641393/+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 1641393] Re: 'Elan Touchpad' not detected in Ubuntu 16.04.1 Gigabyte P57K-965-603S Fresh install

** Attachment added: "Xorg.0.log_tmp"
   
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-sis/+bug/1641393/+attachment/4776780/+files/Xorg.0.log_tmp

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

Title:
  'Elan Touchpad' not detected in Ubuntu 16.04.1 Gigabyte P57K-965-603S
  Fresh install

Status in xserver-xorg-video-sis package in Ubuntu:
  New

Bug description:
  On a fresh install of Ubuntu 16.04.1 (July 27 2016) on the above
  machine, the Elan touchpad was not detected at all.  An external mouse
  works perfectly.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-sis/+bug/1641393/+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 1641393] [NEW] 'Elan Touchpad' not detected in Ubuntu 16.04.1 Gigabyte P57K-965-603S Fresh install

Public bug reported:

On a fresh install of Ubuntu 16.04.1 (July 27 2016) on the above
machine, the Elan touchpad was not detected at all.  An external mouse
works perfectly.

** Affects: xserver-xorg-video-sis (Ubuntu)
 Importance: Undecided
 Status: New

** Attachment added: "Info"
   https://bugs.launchpad.net/bugs/1641393/+attachment/4776777/+files/devices

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

Title:
  'Elan Touchpad' not detected in Ubuntu 16.04.1 Gigabyte P57K-965-603S
  Fresh install

Status in xserver-xorg-video-sis package in Ubuntu:
  New

Bug description:
  On a fresh install of Ubuntu 16.04.1 (July 27 2016) on the above
  machine, the Elan touchpad was not detected at all.  An external mouse
  works perfectly.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-sis/+bug/1641393/+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 1641393] Re: 'Elan Touchpad' not detected in Ubuntu 16.04.1 Gigabyte P57K-965-603S Fresh install