[Desktop-packages] [Bug 1648713] Re: Key file does not start with a group

[Sebastien Bacher]

Thank you for your issue report, could you add your configuration file
to the bug?

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

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

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

Title:
  Key file does not start with a group

Status in lightdm package in Ubuntu:
  Incomplete

Bug description:
  And I study your program and decided to set up a configuration file.
  Version of my program lightdm 1.10.3
  After changing the parameter in the file /etc/lightdm/lightdm.conf 
start-default-seat, I was given an error:
  Failed to load configuration from /etc/lightdm/lightdm.conf: Key file does 
not start with a group
  Line I did this: start-default-seat=true
  I enter commands: lightdm --show-config
  Help me, I will be grateful!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1648713/+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 1648713] [NEW] Key file does not start with a group

[nequx]

Public bug reported:

And I study your program and decided to set up a configuration file.
Version of my program lightdm 1.10.3
After changing the parameter in the file /etc/lightdm/lightdm.conf 
start-default-seat, I was given an error:
Failed to load configuration from /etc/lightdm/lightdm.conf: Key file does not 
start with a group
Line I did this: start-default-seat=true
I enter commands: lightdm --show-config
Help me, I will be grateful!

** Affects: lightdm (Ubuntu)
 Importance: Undecided
 Assignee: nequx (nequx)
 Status: New


** Tags: lightdm

** Tags added: lightdm

** Changed in: lightdm (Ubuntu)
 Assignee: (unassigned) => nequx (nequx)

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

Title:
  Key file does not start with a group

Status in lightdm package in Ubuntu:
  New

Bug description:
  And I study your program and decided to set up a configuration file.
  Version of my program lightdm 1.10.3
  After changing the parameter in the file /etc/lightdm/lightdm.conf 
start-default-seat, I was given an error:
  Failed to load configuration from /etc/lightdm/lightdm.conf: Key file does 
not start with a group
  Line I did this: start-default-seat=true
  I enter commands: lightdm --show-config
  Help me, I will be grateful!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1648713/+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 1639337] Re: Ubuntu 16.10 Abs_pressure not reported from kernel evdev to xserver-xorg-evdev

[vasdi]

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

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

Title:
  Ubuntu 16.10 Abs_pressure not reported from kernel evdev to xserver-
  xorg-evdev

Status in xserver-xorg-input-evdev:
  Unknown
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Please refer to bug filed with freedesktop.org:

  https://bugs.freedesktop.org/show_bug.cgi?id=98575

  I modified a driver for the Bosto Tablet 22HD and others, this has
  been working without problems across the last several releases and
  continues to work with 16.04.1 LTS.

  When I upgraded to 16.10, pressure readings are lost from all
  applications, X & Y data still visible.

  evtest shows correct EV_ data for ABS_X ABS_Y and ABS_PRESSURE, but
  when xinput is used.

  xinput --list --long 

  The Valuator for pressure is listed, but no changes occur as the tool
  is used. The parameters of the Valuator can still be modified using
  xinput tweaking tools, but no pressure reported.

  All X apps requiring pressure data fail.

  I made a fresh install of 16.10, loaded the driver  same issue.

  I run 16.04.1 LTS, everything fine.
  I have others users of my driver code also using 16.04.1 without issue.

To manage notifications about this bug go to:
https://bugs.launchpad.net/evdev/+bug/1639337/+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 792085]

[Swamp-a]

SUSE-SU-2016:2976-1: An update that solves 13 vulnerabilities and has 87
fixes is now available.

Category: security (important)
Bug References: 
1000189,1001419,1002165,1003077,1003344,1003568,1003677,1003866,1003925,1004517,1004520,1005857,1005896,1005903,1006917,1006919,1007944,763198,771065,799133,803320,839104,843236,860441,863873,865783,871728,907611,908458,908684,909077,909350,909484,909618,909994,911687,915183,920016,922634,922947,928138,929141,934760,951392,956514,960689,963655,967716,968010,968014,971975,971989,973203,974620,976867,977687,979514,979595,979681,980371,982218,982783,983535,983619,984102,984194,984992,985206,986337,986362,986365,986445,987565,988440,989152,989261,989764,989779,991608,991665,991923,992566,993127,993890,993891,994296,994436,994618,994759,994926,995968,996329,996664,997708,998399,998689,999584,999600,07,32
CVE References: 
CVE-2013-4312,CVE-2015-7513,CVE-2015-8956,CVE-2016-0823,CVE-2016-3841,CVE-2016-4998,CVE-2016-5696,CVE-2016-6480,CVE-2016-6828,CVE-2016-7042,CVE-2016-7097,CVE-2016-7117,CVE-2016-7425
Sources used:
SUSE Linux Enterprise Software Development Kit 11-SP4 (src):
kernel-docs-3.0.101-88.3
SUSE Linux Enterprise Server 11-SP4 (src):kernel-bigmem-3.0.101-88.1, 
kernel-default-3.0.101-88.1, kernel-ec2-3.0.101-88.1, kernel-pae-3.0.101-88.1, 
kernel-ppc64-3.0.101-88.1, kernel-source-3.0.101-88.1, 
kernel-syms-3.0.101-88.1, kernel-trace-3.0.101-88.1, kernel-xen-3.0.101-88.1
SUSE Linux Enterprise Server 11-EXTRA (src):kernel-default-3.0.101-88.1, 
kernel-pae-3.0.101-88.1, kernel-ppc64-3.0.101-88.1, kernel-trace-3.0.101-88.1, 
kernel-xen-3.0.101-88.1
SUSE Linux Enterprise Debuginfo 11-SP4 (src):kernel-bigmem-3.0.101-88.1, 
kernel-default-3.0.101-88.1, kernel-ec2-3.0.101-88.1, kernel-pae-3.0.101-88.1, 
kernel-ppc64-3.0.101-88.1, kernel-trace-3.0.101-88.1, kernel-xen-3.0.101-88.1

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

Title:
  Automatic remount of safely removed USB 3.0 drive

Status in Nautilus:
  New
Status in thunar:
  Unknown
Status in linux package in Ubuntu:
  Confirmed
Status in nautilus package in Ubuntu:
  Confirmed
Status in thunar package in Ubuntu:
  Confirmed
Status in udev package in Ubuntu:
  Confirmed
Status in Fedora:
  Unknown
Status in openSUSE:
  Fix Released

Bug description:
  Binary package hint: nautilus

  When I choose "Safely remove drive" context menu entry for an external
  USB drive within a nautilus window or directly clicking on the desktop
  icon, after about 10 seconds the drive is automatically remounted and
  a Nautilus window showing the root folder opens.

  I have noticed that similar already happened with a very old Ubuntu
  version - Bug #110589 and as that is so long time ago I thought it is
  better to open a new bug. Reason of the problem might even be
  completely different.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.04
  Package: nautilus 1:2.32.2.1-0ubuntu13
  ProcVersionSignature: Ubuntu 2.6.38-8.42-generic-pae 2.6.38.2
  Uname: Linux 2.6.38-8-generic-pae i686
  Architecture: i386
  Date: Thu Jun  2 23:40:08 2011
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1)
  ProcEnviron:
   LANGUAGE=en_US:en
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/nautilus/+bug/792085/+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 792085]

[Swamp-a]

openSUSE-SU-2016:3021-1: An update that solves 12 vulnerabilities and
has 118 fixes is now available.

Category: security (important)
Bug References: 
1000189,1000287,1000304,1000776,1001419,1001486,1002165,1003079,1003153,1003400,1003568,1003866,1003925,1004252,1004418,1004462,1004517,1004520,1005666,1006691,1007615,1007886,744692,772786,789311,799133,857397,860441,865545,866130,868923,874131,875631,876145,876463,898675,904489,909994,911687,915183,921338,921784,922064,922634,924381,924384,930399,931454,934067,937086,937888,940545,941420,946309,954986,955446,956514,959463,961257,962846,963655,963767,966864,967640,970943,971975,971989,974406,974620,975596,975772,976195,977687,978094,979451,979681,979928,982783,983619,984194,984419,984779,984992,985562,986445,987192,987333,987542,987565,987621,987805,988440,988617,988715,989152,989953,990245,991247,991608,991665,992244,992555,992591,992593,992712,993392,993841,993890,993891,994296,994438,994520,994748,994758,995153,995968,996664,997059,997299,997708,997896,998689,998795,998825,999577,999584,999600,999779,07,32
CVE References: 
CVE-2013-5634,CVE-2015-8956,CVE-2016-2069,CVE-2016-5696,CVE-2016-6130,CVE-2016-6327,CVE-2016-6480,CVE-2016-6828,CVE-2016-7042,CVE-2016-7097,CVE-2016-7425,CVE-2016-8658
Sources used:
openSUSE 13.1 (src):cloop-2.639-11.36.1, crash-7.0.2-2.36.1, 
hdjmod-1.28-16.36.1, ipset-6.21.1-2.40.1, iscsitarget-1.4.20.3-13.36.1, 
kernel-debug-3.12.67-58.1, kernel-default-3.12.67-58.1, 
kernel-desktop-3.12.67-58.1, kernel-docs-3.12.67-58.2, kernel-ec2-3.12.67-58.1, 
kernel-pae-3.12.67-58.1, kernel-source-3.12.67-58.1, kernel-syms-3.12.67-58.1, 
kernel-trace-3.12.67-58.1, kernel-vanilla-3.12.67-58.1, 
kernel-xen-3.12.67-58.1, ndiswrapper-1.58-37.1, openvswitch-1.11.0-0.43.1, 
pcfclock-0.44-258.37.1, vhba-kmp-20130607-2.36.1, virtualbox-4.2.36-2.68.1, 
xen-4.3.4_10-69.1, xtables-addons-2.3-2.35.1

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

Title:
  Automatic remount of safely removed USB 3.0 drive

Status in Nautilus:
  New
Status in thunar:
  Unknown
Status in linux package in Ubuntu:
  Confirmed
Status in nautilus package in Ubuntu:
  Confirmed
Status in thunar package in Ubuntu:
  Confirmed
Status in udev package in Ubuntu:
  Confirmed
Status in Fedora:
  Unknown
Status in openSUSE:
  Fix Released

Bug description:
  Binary package hint: nautilus

  When I choose "Safely remove drive" context menu entry for an external
  USB drive within a nautilus window or directly clicking on the desktop
  icon, after about 10 seconds the drive is automatically remounted and
  a Nautilus window showing the root folder opens.

  I have noticed that similar already happened with a very old Ubuntu
  version - Bug #110589 and as that is so long time ago I thought it is
  better to open a new bug. Reason of the problem might even be
  completely different.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.04
  Package: nautilus 1:2.32.2.1-0ubuntu13
  ProcVersionSignature: Ubuntu 2.6.38-8.42-generic-pae 2.6.38.2
  Uname: Linux 2.6.38-8-generic-pae i686
  Architecture: i386
  Date: Thu Jun  2 23:40:08 2011
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1)
  ProcEnviron:
   LANGUAGE=en_US:en
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/nautilus/+bug/792085/+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 792085] Re: Automatic remount of safely removed USB 3.0 drive

[Bug Watch Updater]

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2013-4312

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2016-3841

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2016-4998

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2013-5634

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2016-2069

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

Title:
  Automatic remount of safely removed USB 3.0 drive

Status in Nautilus:
  New
Status in thunar:
  Unknown
Status in linux package in Ubuntu:
  Confirmed
Status in nautilus package in Ubuntu:
  Confirmed
Status in thunar package in Ubuntu:
  Confirmed
Status in udev package in Ubuntu:
  Confirmed
Status in Fedora:
  Unknown
Status in openSUSE:
  Fix Released

Bug description:
  Binary package hint: nautilus

  When I choose "Safely remove drive" context menu entry for an external
  USB drive within a nautilus window or directly clicking on the desktop
  icon, after about 10 seconds the drive is automatically remounted and
  a Nautilus window showing the root folder opens.

  I have noticed that similar already happened with a very old Ubuntu
  version - Bug #110589 and as that is so long time ago I thought it is
  better to open a new bug. Reason of the problem might even be
  completely different.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.04
  Package: nautilus 1:2.32.2.1-0ubuntu13
  ProcVersionSignature: Ubuntu 2.6.38-8.42-generic-pae 2.6.38.2
  Uname: Linux 2.6.38-8-generic-pae i686
  Architecture: i386
  Date: Thu Jun  2 23:40:08 2011
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1)
  ProcEnviron:
   LANGUAGE=en_US:en
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/nautilus/+bug/792085/+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 405294] Re: a2dp skips terribly

[Filip]

One thing which I have notices just now, when I start downloading
something it get's much worse

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

Title:
  a2dp skips terribly

Status in PulseAudio:
  Confirmed
Status in bluez package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  As I upgraded to the Karmic alpha, bluetooth audio (via a2dp) stopped
  working properly. It was working fine in Jaunty.

  My headphones are detected and configured by pulse, but the audio
  skips as if it's spending half of each second paused. Music is
  buffered so that after I click stop on rhythmbox (or whatever--it
  happens with whatever player I use) the audio continues until it's
  caught up.

  syslog is full of the following lines:
  Jul 27 08:55:45 carlin1 pulseaudio[3218]: alsa-source.c: Increasing minimal 
latency to 1.00 ms
  Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 
15128 us (= 2668 bytes) in audio stream
  Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 
36586 us (= 6452 bytes) in audio stream
  Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 
35593 us (= 6276 bytes) in audio stream
  Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 
36597 us (= 6452 bytes) in audio stream
  Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 
32601 us (= 5748 bytes) in audio stream
  Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 
32589 us (= 5748 bytes) in audio stream

  This is with
  bluez 4.45-0ubuntu4
  pulseaudio1:0.9.15-4ubuntu2 0

  pulseaudio version 1:0.9.16~test2-0ubuntu1~ppa3 from ubuntu-audio-dev
  didn't help.

To manage notifications about this bug go to:
https://bugs.launchpad.net/pulseaudio/+bug/405294/+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 405294] Re: a2dp skips terribly

[Filip]

Can confirm for ubuntu 16.04.1, have same issue as Dan, tried everything
from previous posts but nothing works..

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

Title:
  a2dp skips terribly

Status in PulseAudio:
  Confirmed
Status in bluez package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  As I upgraded to the Karmic alpha, bluetooth audio (via a2dp) stopped
  working properly. It was working fine in Jaunty.

  My headphones are detected and configured by pulse, but the audio
  skips as if it's spending half of each second paused. Music is
  buffered so that after I click stop on rhythmbox (or whatever--it
  happens with whatever player I use) the audio continues until it's
  caught up.

  syslog is full of the following lines:
  Jul 27 08:55:45 carlin1 pulseaudio[3218]: alsa-source.c: Increasing minimal 
latency to 1.00 ms
  Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 
15128 us (= 2668 bytes) in audio stream
  Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 
36586 us (= 6452 bytes) in audio stream
  Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 
35593 us (= 6276 bytes) in audio stream
  Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 
36597 us (= 6452 bytes) in audio stream
  Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 
32601 us (= 5748 bytes) in audio stream
  Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 
32589 us (= 5748 bytes) in audio stream

  This is with
  bluez 4.45-0ubuntu4
  pulseaudio1:0.9.15-4ubuntu2 0

  pulseaudio version 1:0.9.16~test2-0ubuntu1~ppa3 from ubuntu-audio-dev
  didn't help.

To manage notifications about this bug go to:
https://bugs.launchpad.net/pulseaudio/+bug/405294/+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 1598411] Re: failed to download repository information

[Launchpad Bug Tracker]

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

** Changed in: software-center (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  failed to download repository information

Status in software-center package in Ubuntu:
  Expired

Bug description:
  sir,
  I am using ubuntu11.10[oneiric ocelot]. It was released on october 2011.My 
version of ubuntu software center is 5.0.1.4 My ubuntu software center does not 
shows install button and and when I press 'Use This Source' button It shows 
network connection error and fails to download repository information. While I 
am connected to Internet via mobile broadband. I expected for ubuntu software 
center to show install button. But It does not show install button and fails to 
download repository information and shows network connection error.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: software-center 5.0.1.4
  ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4
  Uname: Linux 3.0.0-12-generic i686
  ApportVersion: 1.23-0ubuntu3
  Architecture: i386
  Date: Sat Jul  2 16:04:51 2016
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012)
  PackageArchitecture: all
  SourcePackage: software-center
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-center/+bug/1598411/+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 1296860] Re: firefox hangs up compete laptop for no apparent reason

[Launchpad Bug Tracker]

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

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

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

Title:
  firefox hangs up compete laptop for no apparent reason

Status in firefox package in Ubuntu:
  Expired

Bug description:
  At various occasions the firefox browser just hangs and not even the mouse 
pointer responds.
  Sometimes after some time there is a message about an irresponsive script. 
  Mostly after waiting a lot of minutes and closing firefox it works again.
  I do not have this problem on other machines or other os'es.
  Don't seem to have the problem in Chromium either.
  Seems like a firefox bug to me

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: firefox 28.0+build2-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-19.39-generic 3.13.6
  Uname: Linux 3.13.0-19-generic x86_64
  NonfreeKernelModules: wl
  AddonCompatCheckDisabled: False
  ApportVersion: 2.13.3-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 1932 F pulseaudio
  BuildID: 20140317144912
  Channel: Unavailable
  CurrentDesktop: Unity
  Date: Mon Mar 24 18:35:37 2014
  Extensions: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  InstallationDate: Installed on 2014-03-04 (20 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140303)
  IpRoute:
   default via 192.168.1.1 dev wlan0  proto static 
   192.168.1.0/24 dev wlan0  proto kernel  scope link  src 192.168.1.108  
metric 9
  Locales: extensions.sqlite corrupt or missing
  PrefSources: prefs.js
  Profiles: Profile0 (Default) - LastVersion=28.0/20140317144912
  RelatedPackageVersions:
   rhythmbox-mozilla 3.0.1-1ubuntu16
   totem-mozilla 3.10.1-1ubuntu3
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  Themes: extensions.sqlite corrupt or missing
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/26/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 92CN26WW(V1.06)
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: AIUU1
  dmi.board.vendor: LENOVO
  dmi.board.version: 31900042STD
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Yoga 2 11
  dmi.modalias: 
dmi:bvnLENOVO:bvr92CN26WW(V1.06):bd12/26/2013:svnLENOVO:pn20332:pvrLenovoYoga211:rvnLENOVO:rnAIUU1:rvr31900042STD:cvnLENOVO:ct10:cvrLenovoYoga211:
  dmi.product.name: 20332
  dmi.product.version: Lenovo Yoga 2 11
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1296860/+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 1617777] Re: HPLIP applet does not show window when clicking on it

[Launchpad Bug Tracker]

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

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

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

Title:
  HPLIP applet does not show window when clicking on it

Status in HPLIP:
  Incomplete
Status in hplip package in Ubuntu:
  Expired

Bug description:
  The taskbar applet for HP printers does not show an information window
  when its icon is pressed – the icon is briefly highlighted and nothing
  else happens.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hplip/+bug/161/+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 1563229] Re: Touchpad recognised as mouse FTE1000

[Benny]

Same Problem here (Asus X206h)

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

Title:
  Touchpad recognised as mouse FTE1000

Status in linux package in Ubuntu:
  Triaged
Status in xinput package in Ubuntu:
  Confirmed
Status in linux source package in Trusty:
  Triaged
Status in xinput source package in Trusty:
  Confirmed
Status in linux source package in Wily:
  Triaged
Status in xinput source package in Wily:
  Confirmed
Status in linux source package in Xenial:
  Triaged
Status in xinput source package in Xenial:
  Confirmed

Bug description:
  In my Asus e200ha touchpad is recognized as mouse, only one click, no
  two finger click and scrolling

  Xinput say:
  FTE1000:00 0B05:0101   id=12[slave pointer (2)]

  i've tried:
  - ubuntu 14.04 with stock kernel
  - ubuntu 14.04 with 4.6rc1 kernel
  - Linux mint 17.3 with stock kernel
  --- 
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=7b77dc46-7d5b-4869-83dd-739980736c3a
  InstallationDate: Installed on 2016-03-28 (0 days ago)
  InstallationMedia: Linux Mint 17.3 "Rosa" - Release amd64 20160105
  Lsusb:
   Bus 002 Device 002: ID 0781:5583 SanDisk Corp. 
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 13d3:3496 IMC Networks 
   Bus 001 Device 002: ID 04f2:b54b Chicony Electronics Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. E200HA
  Package: xinput 1.6.1-1
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-32-generic 
root=UUID=50fb13c0-a8cd-441d-a38b-c0295c1b9a15 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.19.0-32.37~14.04.1-generic 3.19.8-ckt7
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-32-generic N/A
   linux-backports-modules-3.19.0-32-generic  N/A
   linux-firmware 1.127.16
  Tags:  rosa rosa
  Uname: Linux 3.19.0-32-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/26/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E200HA.203
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: E200HA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE200HA.203:bd11/26/2015:svnASUSTeKCOMPUTERINC.:pnE200HA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnE200HA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: E200HA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1563229/+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 1217959] Re: 'metadata' file not found when creating backup ("Could not restore ‘/home/user /.cache/deja-dup/metadata’: File not found in backup"

[Dabo Ross]

I've worked around this by using a bind mount instead of a symlink.
Something like 'sudo mount --rbind /run/media/daboross/external/deja-
dup-cache ~/.cache/deja-dup' works. While I do have to re-do this every
time I mount the external drive and start a backup, it at least works.

If you also do a `chmod 500 ~/.cache/deja-dup` when it's unmounted,
deja-dup will be unable to write any files to the unmounted directory
and it will fail early - so you can then mount it and re-start the
backup.

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

Title:
  'metadata' file not found when creating backup ("Could not restore
  ‘/home/user /.cache/deja-dup/metadata’: File not found in backup"

Status in Déjà Dup:
  Confirmed
Status in duplicity package in Ubuntu:
  Incomplete

Bug description:
  Linux release: Ubuntu 13.04 64bit
  Kernel: 3.8.0-29-generic
  Python: 2.7.4
  Deja Dup: 26.0
  Duplicity: 0.6.21

  Hi. I've tried to do my monthly or so backup recently, but Deja Dup
  crashed after trying to backup a very large file (VM disk with Windows
  7, 50GB or so). I tried to do another one, this time excluding all my
  large VM's. However, now when trying to do a backup I'm getting the
  following error a few seconds after inputting my encryption password:

  Could not restore ‘/home/tom/.cache/deja-dup/metadata’: File not found
  in backup

  I've tried reinstalling both deja-dup and duplicity, purging
  duplicity, deleting deja-dup and duplicity from /home/tom/.cache,
  deleting the backup files on the external drive, deleting it's config
  as described here http://askubuntu.com/questions/53980/how-to-delete-
  all-the-settings-for-deja-dup. I know (well, I have some evidence
  supporting this) that the drive itself isn't faulty as I managed to
  backup my old laptop to the drive using duplicity and it worked fine
  (Fedora 19, deja dup 26.0 I think). I will upload the appropriate logs
  momentarily.

To manage notifications about this bug go to:
https://bugs.launchpad.net/deja-dup/+bug/1217959/+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 1445543] Re: Multi-window GTK apps in Mir are randomly unresponsive, seem to freeze

[Daniel van Vugt]

Does Mir have the required client API functions for those yet?

** Package changed: ubuntu => gtk+3.0 (Ubuntu)

** Changed in: mir
   Status: Invalid => Incomplete

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

Title:
  Multi-window GTK apps in Mir are randomly unresponsive, seem to freeze

Status in GTK+:
  New
Status in Mir:
  Incomplete
Status in gtk+3.0 package in Ubuntu:
  Confirmed

Bug description:
  GTK apps on Mir: Input focus is unreliable and sporadic. Background
  windows ignore input and/or focus switches apparently randomly.

  Example:

  $ GDK_BACKEND=mir mir_demo_server --launch gnome-mahjongg

  Show the "Scores" - you can switch focus between this and the main
  window with Alt+` but doesn't respond to input.

  Other dialogs (e.g. "About") work fine. From the Mir side there's no
  obvious difference between these windows.

  In this example, MIR_CLIENT_INPUT_RECEIVER_REPORT=log shows the input
  events being correctly received on the client side. That shows most of
  the Mir stack is working correctly.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gtk/+bug/1445543/+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 893024] Re: Support 802.1x auth requirement detection and fallback

[dwmw2]

https://bugzilla.gnome.org/show_bug.cgi?id=723084


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

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

Title:
  Support 802.1x auth requirement detection and fallback

Status in network-manager package in Ubuntu:
  Triaged

Bug description:
  NetworkManager asks for 802.1x user name and password when there is no
  802.1x support on switch port.

  Background:

  We use 802.1x wired authentication on our campus network.
  NetworkManager does not fall back nicely when connecting to a non-
  authenticated switch.

  What happens:

  NetworkManager asks for user name and password when "Use 802.1x
  security" is selected in the connection editor and the computer is
  connected to an unauthenticated port.

  What should happen:

  Network manager should notice that the port is not access-controlled
  and do one of the following: (1) ask for connecting unauthenticated or
  (2) connect unauthenticated without asking.

  There should be a setting for selecting #1 or #2.

  Now the user is asked about information which has no effect on
  completing the connection.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/893024/+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 1445543] [NEW] Multi-window GTK apps in Mir are randomly unresponsive, seem to freeze

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

GTK apps on Mir: Input focus is unreliable and sporadic. Background
windows ignore input and/or focus switches apparently randomly.

Example:

$ GDK_BACKEND=mir mir_demo_server --launch gnome-mahjongg

Show the "Scores" - you can switch focus between this and the main
window with Alt+` but doesn't respond to input.

Other dialogs (e.g. "About") work fine. From the Mir side there's no
obvious difference between these windows.

In this example, MIR_CLIENT_INPUT_RECEIVER_REPORT=log shows the input
events being correctly received on the client side. That shows most of
the Mir stack is working correctly.

** Affects: gtk
 Importance: Undecided
 Assignee: Andreas Pokorny (andreas-pokorny)
 Status: New

** Affects: mir
 Importance: High
 Status: Invalid

** Affects: gtk+3.0 (Ubuntu)
 Importance: High
 Assignee: Andreas Pokorny (andreas-pokorny)
 Status: Confirmed


** Tags: gtk-mir mir snappyrdp
-- 
Multi-window GTK apps in Mir are randomly unresponsive, seem to freeze
https://bugs.launchpad.net/bugs/1445543
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to gtk+3.0 in Ubuntu.

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

[Desktop-packages] [Bug 1217959] Re: 'metadata' file not found when creating backup ("Could not restore ‘/home/user /.cache/deja-dup/metadata’: File not found in backup"

[Felipe Castillo]

I have this exact same problem. I tried creating an empty metadata file so it 
can write over it, but that didn't work.
I decided to symlink only the folder inside '.cache/deja-dup', the folder named 
6724d3f170e0390931977a130c2b7632. I thought by leaving the deja-dup folder, it 
will be able to write the metadata file but still have everything else symlink 
somewhere else. It didn't work, and it was nasty. As soon as I tried to ran a 
manual backup (from the GUI, of course) I saw this error:

"Specified archive directory '/home/[user]/.cache/deja-
dup/6724d3f170e0390931977a130c2b7632' does not exist, or is not a
directory"

Well, I guess it's technically not a directory, it's a symlink to one.

Has anybody come up with a workaround for this? Anything?

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

Title:
  'metadata' file not found when creating backup ("Could not restore
  ‘/home/user /.cache/deja-dup/metadata’: File not found in backup"

Status in Déjà Dup:
  Confirmed
Status in duplicity package in Ubuntu:
  Incomplete

Bug description:
  Linux release: Ubuntu 13.04 64bit
  Kernel: 3.8.0-29-generic
  Python: 2.7.4
  Deja Dup: 26.0
  Duplicity: 0.6.21

  Hi. I've tried to do my monthly or so backup recently, but Deja Dup
  crashed after trying to backup a very large file (VM disk with Windows
  7, 50GB or so). I tried to do another one, this time excluding all my
  large VM's. However, now when trying to do a backup I'm getting the
  following error a few seconds after inputting my encryption password:

  Could not restore ‘/home/tom/.cache/deja-dup/metadata’: File not found
  in backup

  I've tried reinstalling both deja-dup and duplicity, purging
  duplicity, deleting deja-dup and duplicity from /home/tom/.cache,
  deleting the backup files on the external drive, deleting it's config
  as described here http://askubuntu.com/questions/53980/how-to-delete-
  all-the-settings-for-deja-dup. I know (well, I have some evidence
  supporting this) that the drive itself isn't faulty as I managed to
  backup my old laptop to the drive using duplicity and it worked fine
  (Fedora 19, deja dup 26.0 I think). I will upload the appropriate logs
  momentarily.

To manage notifications about this bug go to:
https://bugs.launchpad.net/deja-dup/+bug/1217959/+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 1648649] Re: Ubufox is broken in Firefox Nightly, due to using no-longer-supported "for each" syntax. Error console now shows "SyntaxError: missing ( after for UpdateNotifier.j

[Daniel Holbert]

I'm using Ubuntu 16.10 with latest Firefox & ubufox.

Package versions:
$ apt-cache show xul-ext-ubufox | grep Version
Version: 3.2-0ubuntu1

$ apt-cache show firefox | grep Version
Version: 50.0.2+build1-0ubuntu0.16.10.1

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

Title:
  Ubufox is broken in Firefox Nightly, due to using no-longer-supported
  "for each" syntax.  Error console now shows "SyntaxError: missing (
  after for  UpdateNotifier.js:217:8"

Status in ubufox package in Ubuntu:
  New

Bug description:
  Firefox Nightly (53) no longer supports the non-standard "for each"
  looping construct, as of
  https://bugzilla.mozilla.org/show_bug.cgi?id=1293305

  Unfortunately, ubufox uses this construct, which causes problems as shown in 
the error console at startup:
  > SyntaxError: missing ( after for UpdateNotifier.js:217:8
  > SyntaxError: missing ( after for utils.jsm:217:8

  
  Fortunately, it's easy to fix! Just replace code like this...
  > for each (let k in [...])
  ...with code like this:
  > for (let k of [...])

  Note: I also filed this in Mozilla's bug-tracker (under Tech Evangelism | 
Add-ons) here:
   https://bugzilla.mozilla.org/show_bug.cgi?id=1322551

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubufox/+bug/1648649/+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 1648649] [NEW] Ubufox is broken in Firefox Nightly, due to using no-longer-supported "for each" syntax. Error console now shows "SyntaxError: missing ( after for UpdateNotifier

[Daniel Holbert]

Public bug reported:

Firefox Nightly (53) no longer supports the non-standard "for each"
looping construct, as of
https://bugzilla.mozilla.org/show_bug.cgi?id=1293305

Unfortunately, ubufox uses this construct, which causes problems as shown in 
the error console at startup:
> SyntaxError: missing ( after for UpdateNotifier.js:217:8
> SyntaxError: missing ( after for utils.jsm:217:8


Fortunately, it's easy to fix! Just replace code like this...
> for each (let k in [...])
...with code like this:
> for (let k of [...])

Note: I also filed this in Mozilla's bug-tracker (under Tech Evangelism | 
Add-ons) here:
 https://bugzilla.mozilla.org/show_bug.cgi?id=1322551

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

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

Title:
  Ubufox is broken in Firefox Nightly, due to using no-longer-supported
  "for each" syntax.  Error console now shows "SyntaxError: missing (
  after for  UpdateNotifier.js:217:8"

Status in ubufox package in Ubuntu:
  New

Bug description:
  Firefox Nightly (53) no longer supports the non-standard "for each"
  looping construct, as of
  https://bugzilla.mozilla.org/show_bug.cgi?id=1293305

  Unfortunately, ubufox uses this construct, which causes problems as shown in 
the error console at startup:
  > SyntaxError: missing ( after for UpdateNotifier.js:217:8
  > SyntaxError: missing ( after for utils.jsm:217:8

  
  Fortunately, it's easy to fix! Just replace code like this...
  > for each (let k in [...])
  ...with code like this:
  > for (let k of [...])

  Note: I also filed this in Mozilla's bug-tracker (under Tech Evangelism | 
Add-ons) here:
   https://bugzilla.mozilla.org/show_bug.cgi?id=1322551

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

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

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

[Launchpad Bug Tracker]

** Branch linked: lp:lightdm/1.2

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

Title:
  handle interruped read and write calls

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

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

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

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

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

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

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

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

[Robert Ancell]

** Changed in: lightdm/1.2
   Importance: Undecided => High

** Changed in: lightdm/1.2
   Status: New => Fix Committed

** Changed in: lightdm/1.2
Milestone: None => 1.2.12

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

Title:
  handle interruped read and write calls

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

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

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

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

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

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

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

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

[Robert Ancell]

** Changed in: lightdm/1.10
   Importance: Undecided => High

** Changed in: lightdm/1.10
   Status: New => Fix Committed

** Changed in: lightdm/1.10
Milestone: None => 1.10.7

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

Title:
  handle interruped read and write calls

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

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

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

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

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

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

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

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

[Launchpad Bug Tracker]

** Branch linked: lp:lightdm/1.10

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

Title:
  handle interruped read and write calls

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

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

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

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

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

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

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

[Desktop-packages] [Bug 1648644] [NEW] XE500C13-K02US Samsung Chromebook 3 Ubuntu 16.04.1 touchpad and keyboard not responsive, also no audio

[Robert Sloboda]

Public bug reported:

16.04.1 image has no native keyboard or mouse interaction. I'm writing
this bug report on the affected platform, a new Samsung Chromebook 3,
XE500C13-K02US. In order to get Ubuntu to recognize keyboard and mouse
input, I needed to use an external USB keyboard-mouse.

Let me know if this platform has been tested. I'm assuming this newer
Samsung platform is not yet tested with Ubuntu and that there are some
issues to work through. This is a fantastic platform for Ubuntu use -
R, Edu, Software Development, General Linux use. I hope we can find a
fix to the problem.

Let me know what I can do to help. I've seen this issue since previous
Samsung Chromebook models and since Ubuntu 14 LTS, so I'm assuming
someone has already taken the lead on this issue?

Thanks again, let me know what I can do to help test any proposed fixes.
I have plenty of MAC, PC, and Chromebook platforms available for
testing, but to this point haven't before volunteered for Ubuntu
testing-debugging :)

As a side note, the audio also isn't working which seems to be a common
problem with Ubuntu on several Chromebook platforms, including Acer and
Samsung.

** Affects: kernel-package (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: audio chromebook keyboard mouse samsung xe500c13-k02us

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

Title:
  XE500C13-K02US Samsung Chromebook 3 Ubuntu 16.04.1 touchpad and
  keyboard not responsive, also no audio

Status in kernel-package package in Ubuntu:
  New

Bug description:
  16.04.1 image has no native keyboard or mouse interaction. I'm writing
  this bug report on the affected platform, a new Samsung Chromebook 3,
  XE500C13-K02US. In order to get Ubuntu to recognize keyboard and mouse
  input, I needed to use an external USB keyboard-mouse.

  Let me know if this platform has been tested. I'm assuming this newer
  Samsung platform is not yet tested with Ubuntu and that there are some
  issues to work through. This is a fantastic platform for Ubuntu use -
  R, Edu, Software Development, General Linux use. I hope we can find
  a fix to the problem.

  Let me know what I can do to help. I've seen this issue since previous
  Samsung Chromebook models and since Ubuntu 14 LTS, so I'm assuming
  someone has already taken the lead on this issue?

  Thanks again, let me know what I can do to help test any proposed
  fixes. I have plenty of MAC, PC, and Chromebook platforms available
  for testing, but to this point haven't before volunteered for Ubuntu
  testing-debugging :)

  As a side note, the audio also isn't working which seems to be a
  common problem with Ubuntu on several Chromebook platforms, including
  Acer and Samsung.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kernel-package/+bug/1648644/+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 1648644] Re: XE500C13-K02US Samsung Chromebook 3 Ubuntu 16.04.1 touchpad and keyboard not responsive, also no audio

[Robert Sloboda]

Not sure which package needs updating, or if this is an interaction
between packages. I'll leave that judgment to the experts. Maybe some
additional debugging is needed (special kernel) to log the functionality
and package interactions and help narrow down the problem?  This problem
has been around at least since Ubuntu 14 LTS and previous model Samsung
Chromebooks, according to my web research.

** Package changed: pulseaudio (Ubuntu) => kernel-package (Ubuntu)

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

Title:
  XE500C13-K02US Samsung Chromebook 3 Ubuntu 16.04.1 touchpad and
  keyboard not responsive, also no audio

Status in kernel-package package in Ubuntu:
  New

Bug description:
  16.04.1 image has no native keyboard or mouse interaction. I'm writing
  this bug report on the affected platform, a new Samsung Chromebook 3,
  XE500C13-K02US. In order to get Ubuntu to recognize keyboard and mouse
  input, I needed to use an external USB keyboard-mouse.

  Let me know if this platform has been tested. I'm assuming this newer
  Samsung platform is not yet tested with Ubuntu and that there are some
  issues to work through. This is a fantastic platform for Ubuntu use -
  R, Edu, Software Development, General Linux use. I hope we can find
  a fix to the problem.

  Let me know what I can do to help. I've seen this issue since previous
  Samsung Chromebook models and since Ubuntu 14 LTS, so I'm assuming
  someone has already taken the lead on this issue?

  Thanks again, let me know what I can do to help test any proposed
  fixes. I have plenty of MAC, PC, and Chromebook platforms available
  for testing, but to this point haven't before volunteered for Ubuntu
  testing-debugging :)

  As a side note, the audio also isn't working which seems to be a
  common problem with Ubuntu on several Chromebook platforms, including
  Acer and Samsung.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kernel-package/+bug/1648644/+subscriptions

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

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

[Robert Ancell]

** Changed in: lightdm/1.18
   Importance: Undecided => High

** Changed in: lightdm/1.18
   Status: New => Fix Committed

** Changed in: lightdm/1.18
Milestone: None => 1.18.4

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

Title:
  handle interruped read and write calls

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

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

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

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

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

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

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

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

[Launchpad Bug Tracker]

** Branch linked: lp:lightdm/1.18

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

Title:
  handle interruped read and write calls

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

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

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

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

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

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

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

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

[Robert Ancell]

** Changed in: lightdm/1.20
   Importance: Undecided => High

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

Title:
  handle interruped read and write calls

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

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

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

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

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

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

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

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

[Launchpad Bug Tracker]

** Branch linked: lp:lightdm/1.20

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

Title:
  handle interruped read and write calls

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

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

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

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

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

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

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

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

[Robert Ancell]

** Changed in: lightdm
   Status: Fix Committed => Fix Released

** Changed in: lightdm
Milestone: None => 1.21.2

** Changed in: lightdm/1.20
   Status: New => Fix Committed

** Changed in: lightdm/1.20
Milestone: None => 1.20.1

** Also affects: lightdm (Ubuntu Zesty)
   Importance: Undecided
   Status: New

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

Title:
  handle interruped read and write calls

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

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

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

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

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

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

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

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

[dwmw2]

Setting aside the wisdom of that response, and my surprise at
discovering that the distribution even *permits* you to ship your own
copy of certain libraries — *especially* security-critical libraries —
in your own package instead of using the system's version doesn't
that mean you should be shipping your own version of things like
certutil and modutil, given that you now not only have your own copy of
the libraries, but you even have a speshul different database format to
the one that the system NSS uses, so you aren't even compatible with
/usr/bin/certtool.

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

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

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

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

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

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

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

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

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

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

[Alberts Muktupāvels]

** Description changed:

  Use SA_RESTART flag to make sure that interrupted calls to read and/or
  write are restarted.
  
  In my case read is interrupted when reading login1_session_id. Result of
  not handling EINTR error is that login1_session_id is set to NULL and
  console_kit_cookie gets login1 session id.
+ 
+ Related warnings in lightdm.log:
+ [+0.44s] WARNING: Session pid=617: Error reading from session: Interrupted 
system call
+ [+0.70s] DEBUG: Activating VT 7
+ [+0.70s] DEBUG: Activating ConsoleKit session c1
+ [+0.70s] WARNING: Error getting ConsoleKit session: 
GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name 
org.freedesktop.ConsoleKit was not provided by any .service files
+ 
+ And because login1_session_id is null fix for 1637758 bug does not work.

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

Title:
  handle interruped read and write calls

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

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

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

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

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

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

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

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

[Robert Ancell]

** Changed in: lightdm
   Status: Triaged => Fix Committed

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

Title:
  handle interruped read and write calls

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

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

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

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

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

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

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

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

[Robert Ancell]

** Also affects: lightdm/1.10
   Importance: Undecided
   Status: New

** Also affects: lightdm/1.20
   Importance: Undecided
   Status: New

** Also affects: lightdm/1.18
   Importance: Undecided
   Status: New

** Also affects: lightdm/1.2
   Importance: Undecided
   Status: New

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

** Also affects: lightdm (Ubuntu Yakkety)
   Importance: Undecided
   Status: New

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

** Also affects: lightdm (Ubuntu Trusty)
   Importance: Undecided
   Status: New

** Also affects: lightdm (Ubuntu Precise)
   Importance: Undecided
   Status: New

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

Title:
  handle interruped read and write calls

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

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

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

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

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

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

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

[Desktop-packages] [Bug 1648633] [NEW] Password error

[John Keenan]

Public bug reported:

I believe I have uncovered an error with Archive Manager (file-roller).

  1) From Files, right-click on a single file and select context menu item 
"Compress...".
  2) Modify the archive filename as desired. Select archive type .zip. Do not 
specify a password. Click the "Create" button.
  3) Open the newly created archive and delete the single file it contains.
  4) Select Archive manager menu item Edit > Set Password...
  5) Enter the desired password and click the "Save" button. At this point a 
dialog appears with the following error message:

Could not create the archive

Error when getting information for file
'/home/John/Documents/Personal/.fr-Gr7BGf/junk.zip': No such file or
directory

The file '/home/John/Documents/Personal/junk.zip' does exist and is
open. The "/.fr-Gr7BGf" part has been mistakenly put into the file path
resulting in the error message. (The password did not contain "/.fr-
Gr7BGf".)

I realize it is not common to ask for a password protected archive with
no contents. But to me this error indicates a string over running its
intended memory which should probably be corrected.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: file-roller 3.16.5-0ubuntu1.2
ProcVersionSignature: Ubuntu 4.4.0-53.74-generic 4.4.30
Uname: Linux 4.4.0-53-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.2
Architecture: amd64
CurrentDesktop: Unity
Date: Thu Dec  8 15:25:03 2016
ExecutablePath: /usr/bin/file-roller
InstallationDate: Installed on 2016-11-06 (31 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
ProcEnviron:
 PATH=(custom, user)
 SHELL=/bin/bash
 LANG=en_US.UTF-8
 LANGUAGE=en_US
 XDG_RUNTIME_DIR=
SourcePackage: file-roller
UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  Password error

Status in file-roller package in Ubuntu:
  New

Bug description:
  I believe I have uncovered an error with Archive Manager (file-
  roller).

1) From Files, right-click on a single file and select context menu item 
"Compress...".
2) Modify the archive filename as desired. Select archive type .zip. Do not 
specify a password. Click the "Create" button.
3) Open the newly created archive and delete the single file it contains.
4) Select Archive manager menu item Edit > Set Password...
5) Enter the desired password and click the "Save" button. At this point a 
dialog appears with the following error message:

  Could not create the archive

  Error when getting information for file
  '/home/John/Documents/Personal/.fr-Gr7BGf/junk.zip': No such file or
  directory

  The file '/home/John/Documents/Personal/junk.zip' does exist and is
  open. The "/.fr-Gr7BGf" part has been mistakenly put into the file
  path resulting in the error message. (The password did not contain
  "/.fr-Gr7BGf".)

  I realize it is not common to ask for a password protected archive
  with no contents. But to me this error indicates a string over running
  its intended memory which should probably be corrected.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: file-roller 3.16.5-0ubuntu1.2
  ProcVersionSignature: Ubuntu 4.4.0-53.74-generic 4.4.30
  Uname: Linux 4.4.0-53-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Dec  8 15:25:03 2016
  ExecutablePath: /usr/bin/file-roller
  InstallationDate: Installed on 2016-11-06 (31 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  ProcEnviron:
   PATH=(custom, user)
   SHELL=/bin/bash
   LANG=en_US.UTF-8
   LANGUAGE=en_US
   XDG_RUNTIME_DIR=
  SourcePackage: file-roller
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/file-roller/+bug/1648633/+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 1563229] Re: Touchpad recognised as mouse FTE1000

[Benny]

sorry, forgot to list xinput --list

⎡ Virtual core pointer  id=2[master pointer  (3)]
⎜   ↳ Virtual core XTEST pointerid=4[slave  pointer  (2)]
⎜   ↳ PDEC3393:00 0B05:8585 id=12   [slave  pointer  (2)]
⎜   ↳ FTE1000:00 0B05:0101  id=13   [slave  pointer  (2)]

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

Title:
  Touchpad recognised as mouse FTE1000

Status in linux package in Ubuntu:
  Triaged
Status in xinput package in Ubuntu:
  Confirmed
Status in linux source package in Trusty:
  Triaged
Status in xinput source package in Trusty:
  Confirmed
Status in linux source package in Wily:
  Triaged
Status in xinput source package in Wily:
  Confirmed
Status in linux source package in Xenial:
  Triaged
Status in xinput source package in Xenial:
  Confirmed

Bug description:
  In my Asus e200ha touchpad is recognized as mouse, only one click, no
  two finger click and scrolling

  Xinput say:
  FTE1000:00 0B05:0101   id=12[slave pointer (2)]

  i've tried:
  - ubuntu 14.04 with stock kernel
  - ubuntu 14.04 with 4.6rc1 kernel
  - Linux mint 17.3 with stock kernel
  --- 
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=7b77dc46-7d5b-4869-83dd-739980736c3a
  InstallationDate: Installed on 2016-03-28 (0 days ago)
  InstallationMedia: Linux Mint 17.3 "Rosa" - Release amd64 20160105
  Lsusb:
   Bus 002 Device 002: ID 0781:5583 SanDisk Corp. 
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 13d3:3496 IMC Networks 
   Bus 001 Device 002: ID 04f2:b54b Chicony Electronics Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. E200HA
  Package: xinput 1.6.1-1
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-32-generic 
root=UUID=50fb13c0-a8cd-441d-a38b-c0295c1b9a15 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.19.0-32.37~14.04.1-generic 3.19.8-ckt7
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-32-generic N/A
   linux-backports-modules-3.19.0-32-generic  N/A
   linux-firmware 1.127.16
  Tags:  rosa rosa
  Uname: Linux 3.19.0-32-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/26/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E200HA.203
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: E200HA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE200HA.203:bd11/26/2015:svnASUSTeKCOMPUTERINC.:pnE200HA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnE200HA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: E200HA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1563229/+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 1633499] Re: [SRU] Update to 9.20 in Trusty

[Amr Ibrahim]

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

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

Title:
  [SRU] Update to 9.20 in Trusty

Status in libav package in Ubuntu:
  Fix Released

Bug description:
  https://git.libav.org/?p=libav.git;a=shortlog;h=refs/heads/release/9

  version 9.20:
   - avcodec: bump micro version

  version 9.19:
   - h264: deMpegEncContextize
   - h264: remove silly macros
   - mpegvideo: split ff_draw_horiz_band().
   - error_resilience: add required headers.
   - error_resilience: decouple ER from MpegEncContext
   - h264: remove a pointless if()
   - h264: simplify calls to ff_er_add_slice().
   - tls: Use the right return value for breaking out due to the interrupt 
callback
   - rtmpcrypt: Do the xtea decryption in little endian mode

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libav/+bug/1633499/+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 1648616] Re: Firefox uses its own version of NSS, incompatible with system version

[Chris Coulson]

The Firefox we ship is deliberately as close as possible to what Mozilla
provides, so this isn't going to change

** Changed in: firefox (Ubuntu)
   Status: Confirmed => Invalid

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

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

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

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

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

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

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

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

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

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

[dwmw2]

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

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

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

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

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

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

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

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

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

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

[Desktop-packages] [Bug 1646611] Re: mission-control should use different paths when in a snap environment

[Renato Araujo Oliveira Filho]

** Branch linked: lp:~renatofilho/unity8-session-snap/fix-1646611

** Also affects: unity8-session-snap
   Importance: Undecided
   Status: New

** Changed in: unity8-session-snap
 Assignee: (unassigned) => Renato Araujo Oliveira Filho (renatofilho)

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

Title:
  mission-control should use different paths when in a snap environment

Status in Canonical System Image:
  Confirmed
Status in Unity8 Session Snap:
  New
Status in telepathy-mission-control-5 package in Ubuntu:
  New

Bug description:
  When running confined into a snap environment, mission-control needs
  to use different paths for its files:

  Sep 30 05:31:22 localhost org.freedesktop.Telepathy.AccountManager[4688]: 
(process:4767): mcd-WARNING **: Unable to create directory 
'/snap/unity8-session/x1/usr/share/telepathy/mission-control': Read-only file 
system
  Sep 30 05:31:22 localhost org.freedesktop.Telepathy.AccountManager[4688]: 
(process:4767): mcd-WARNING **: Failed to create file 
'/snap/unity8-session/x1/usr/share/telepathy/mission-control/accounts.cfg.CC7LOY':
 No such file or directory
  Sep 30 05:31:22 localhost org.freedesktop.Telepathy.AccountManager[4688]: 
(process:4767): mcd-WARNING **: Unable to create directory 
'/snap/unity8-session/x1/usr/share/telepathy/mission-control': Read-only file 
system
  Sep 30 05:31:22 localhost org.freedesktop.Telepathy.AccountManager[4688]: 
(process:4767): mcd-WARNING **: Failed to create file 
'/snap/unity8-session/x1/usr/share/telepathy/mission-control/accounts.cfg.7I1LOY':
 No such file or

  Instead of using $SNAP, it probably should use $SNAP_DATA

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1646611/+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 1648616] Re: Firefox uses its own version of NSS, incompatible with system version

[Matteo Croce]

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

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

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

Status in firefox package in Ubuntu:
  Confirmed

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

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

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

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

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

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

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

[dwmw2]

Public bug reported:

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

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

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

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

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

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

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

Status in firefox package in Ubuntu:
  New

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

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

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

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

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

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

[Desktop-packages] [Bug 207135] Re: pulseaudio uses too much CPU

[Francis Chin]

Still a problem in 16.04 LTS - constantly burning 20% CPU on idle.

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

Title:
  pulseaudio uses too much CPU

Status in pulseaudio package in Ubuntu:
  Fix Released

Bug description:
  Binary package hint: pulseaudio

  Pulseaudio uses between 6 and 8% of my CPU (AMD Athlon(tm) 64
  Processor 3500+) when I'm just listening music using Rhythmbox. Seems
  too much IMHO.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/207135/+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 1489483] Comment bridged from LTC Bugzilla

[bugproxy]

--- Comment From bren...@br.ibm.com 2016-12-08 14:42 EDT---
THis problem is now fixed with Ubuntu 17.04

llvm-3.8-dev (>= 1:3.8) [amd64 i386 kfreebsd-amd64 kfreebsd-i386 arm64
armhf ppc64el],

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

Title:
  Enable llvmpipe on libgl-mesa-dri

Status in mesa package in Ubuntu:
  Triaged

Bug description:
  == Comment: #0 - Gabriel Krisman Bertazi  - 2015-08-12 
09:53:27 ==
  The llvmpipe software renderer is disabled in the mesa (libgl1-mesa-dri) 
package for ppc64le, even though llvmpipe is fully supported on this 
architecture.  We need this feature enabled in order to run Unity with video 
cards lacking 3D Hardware Acceleration.

  Please enable it and, if possible, backport this change to 14.04.3.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1489483/+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 1648578] Re: Details view does not expand to full height of window

[Vej]

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

** Also affects: deja-dup
   Importance: Undecided
   Status: New

** This bug has been marked a duplicate of bug 1612506
   backup details field is too tiny

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

Title:
  Details view does not expand to full height of window

Status in Déjà Dup:
  New
Status in deja-dup package in Ubuntu:
  New

Bug description:
  The screenshot says it all.  The details are unreadable.  When I hover
  over it, I still get overlay scrollbars appearing and I can scroll the
  tiny viewport.

  Running deja-dup 34.2-0ubuntu3 on Ubuntu 16.10.

To manage notifications about this bug go to:
https://bugs.launchpad.net/deja-dup/+bug/1648578/+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 1648578] [NEW] Details view does not expand to full height of window

[hackel]

Public bug reported:

The screenshot says it all.  The details are unreadable.  When I hover
over it, I still get overlay scrollbars appearing and I can scroll the
tiny viewport.

Running deja-dup 34.2-0ubuntu3 on Ubuntu 16.10.

** Affects: deja-dup (Ubuntu)
 Importance: Undecided
 Status: New

** Attachment added: "Screenshot from 2016-12-08 12-52-49.png"
   
https://bugs.launchpad.net/bugs/1648578/+attachment/4789160/+files/Screenshot%20from%202016-12-08%2012-52-49.png

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

Title:
  Details view does not expand to full height of window

Status in deja-dup package in Ubuntu:
  New

Bug description:
  The screenshot says it all.  The details are unreadable.  When I hover
  over it, I still get overlay scrollbars appearing and I can scroll the
  tiny viewport.

  Running deja-dup 34.2-0ubuntu3 on Ubuntu 16.10.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/1648578/+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 1531224] Re: lightdm-gtk-greeter flickers once little after lightdm starts

[RonaldvZ]

I believe I'm experiencing this issue as well. If lightdm loads up, I
enter half my password and the flickering happens, I type the rest of my
password and am not able to login. I believe the flickering interrupts
my typing somehow. When I retype my password entirely after the
flickering, it works fine.

Ubuntu MATE 16.04
Ubuntu MATE desktop 1.12.1
CPU: Intel Core i7-6500U CPU @ 3.1GHz
GPU: Mesa DRI Intel(R) HD Graphics 520 (Skylake GT2)

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

Title:
  lightdm-gtk-greeter flickers once little after lightdm starts

Status in LightDM GTK+ Greeter:
  New
Status in xserver-xorg-video-intel package in Ubuntu:
  Confirmed

Bug description:
  Bug context:
   · Arch Linux x86_64 4.3.3-2-ARCH
   · systemd 228-3 (using lightdm-plymouth.service)
   · plymouth 0.9.2-8 (compiled from AUR)
   · lightdm 1:1.16.6-2
   · lightdm-gtk-greeter 1:2.0.1-2

  At the end of boot process, right after plymouth splash, lightdm starts 
normally and the GTK+ greeter login screen is shown for about 1 second, but 
then the screen instantly flickers (goes black) and the greeter is redrawn. 
From here on, everything works flawlessly, but the brief flickering is 
certainly annoying.
  This happens every time and no other greeter I have tried presents this 
issue, so I can confirm it is lightdm-gtk-greeter-related.

To manage notifications about this bug go to:
https://bugs.launchpad.net/lightdm-gtk-greeter/+bug/1531224/+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 1589401] Re: cannot view wifi networks after re-enabling wifi

[Peter S]

@anders-frisk650

Well done! Now we're getting somewhere.

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

Title:
  cannot view wifi networks after re-enabling wifi

Status in NetworkManager:
  Confirmed
Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  after re enabling wifi, up-down arrows just like wired network. cannot
  see any wifi ssid.

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

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

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

[Marc Ordinas i Llopis]

Public bug reported:

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

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

(clicking on details)

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

(repeated until killed)

** Affects: unity-control-center (Ubuntu)
 Importance: Undecided
 Status: New

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

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

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

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

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

  (clicking on details)

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

  (repeated until killed)

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

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

[Desktop-packages] [Bug 1239087]

[Swamp-a]

SUSE-SU-2016:2976-1: An update that solves 13 vulnerabilities and has 87
fixes is now available.

Category: security (important)
Bug References: 
1000189,1001419,1002165,1003077,1003344,1003568,1003677,1003866,1003925,1004517,1004520,1005857,1005896,1005903,1006917,1006919,1007944,763198,771065,799133,803320,839104,843236,860441,863873,865783,871728,907611,908458,908684,909077,909350,909484,909618,909994,911687,915183,920016,922634,922947,928138,929141,934760,951392,956514,960689,963655,967716,968010,968014,971975,971989,973203,974620,976867,977687,979514,979595,979681,980371,982218,982783,983535,983619,984102,984194,984992,985206,986337,986362,986365,986445,987565,988440,989152,989261,989764,989779,991608,991665,991923,992566,993127,993890,993891,994296,994436,994618,994759,994926,995968,996329,996664,997708,998399,998689,999584,999600,07,32
CVE References: 
CVE-2013-4312,CVE-2015-7513,CVE-2015-8956,CVE-2016-0823,CVE-2016-3841,CVE-2016-4998,CVE-2016-5696,CVE-2016-6480,CVE-2016-6828,CVE-2016-7042,CVE-2016-7097,CVE-2016-7117,CVE-2016-7425
Sources used:
SUSE Linux Enterprise Software Development Kit 11-SP4 (src):
kernel-docs-3.0.101-88.3
SUSE Linux Enterprise Server 11-SP4 (src):kernel-bigmem-3.0.101-88.1, 
kernel-default-3.0.101-88.1, kernel-ec2-3.0.101-88.1, kernel-pae-3.0.101-88.1, 
kernel-ppc64-3.0.101-88.1, kernel-source-3.0.101-88.1, 
kernel-syms-3.0.101-88.1, kernel-trace-3.0.101-88.1, kernel-xen-3.0.101-88.1
SUSE Linux Enterprise Server 11-EXTRA (src):kernel-default-3.0.101-88.1, 
kernel-pae-3.0.101-88.1, kernel-ppc64-3.0.101-88.1, kernel-trace-3.0.101-88.1, 
kernel-xen-3.0.101-88.1
SUSE Linux Enterprise Debuginfo 11-SP4 (src):kernel-bigmem-3.0.101-88.1, 
kernel-default-3.0.101-88.1, kernel-ec2-3.0.101-88.1, kernel-pae-3.0.101-88.1, 
kernel-ppc64-3.0.101-88.1, kernel-trace-3.0.101-88.1, kernel-xen-3.0.101-88.1

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

Title:
  Safely remove is not working (or broken) in Gnome Disks

Status in GNOME Disks:
  Fix Released
Status in udisks:
  Confirmed
Status in gnome-disk-utility package in Ubuntu:
  Fix Released
Status in gnome-disk-utility package in Fedora:
  Unknown
Status in gnome-disk-utility package in openSUSE:
  Invalid
Status in oem-workaround-xhci-quirk-dkms package in openSUSE:
  Fix Released

Bug description:
  In 12.04 I was able to safely remove USB-stick (make its LED off) and USB-HDD 
(do a spin down).
  In 13.04 this option is missed.

  In 13.10 it is appeared again, but not working as expected:
  +Gnome Disks normally powers off the USB flash (tested on 4 different 
flashes and 2 USB cardreaders).
  - Gnome Disks does not spin down USB HDD (but udisks --detach does)

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: gnome-disk-utility 3.8.2-1ubuntu2
  ProcVersionSignature: Ubuntu 3.10.0-1.8-generic 3.10.0-rc7
  Uname: Linux 3.10.0-1-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.12.5-0ubuntu2
  Architecture: i386
  Date: Sat Oct 12 13:39:21 2013
  InstallationDate: Installed on 2013-03-06 (219 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha i386 (20130306)
  MarkForUpload: True
  SourcePackage: gnome-disk-utility
  UpgradeStatus: Upgraded to saucy on 2013-06-23 (110 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-disk-utility/+bug/1239087/+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 1239087] Re: Safely remove is not working (or broken) in Gnome Disks

[Bug Watch Updater]

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2013-4312

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2016-3841

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2016-4998

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2013-5634

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2016-2069

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

Title:
  Safely remove is not working (or broken) in Gnome Disks

Status in GNOME Disks:
  Fix Released
Status in udisks:
  Confirmed
Status in gnome-disk-utility package in Ubuntu:
  Fix Released
Status in gnome-disk-utility package in Fedora:
  Unknown
Status in gnome-disk-utility package in openSUSE:
  Invalid
Status in oem-workaround-xhci-quirk-dkms package in openSUSE:
  Fix Released

Bug description:
  In 12.04 I was able to safely remove USB-stick (make its LED off) and USB-HDD 
(do a spin down).
  In 13.04 this option is missed.

  In 13.10 it is appeared again, but not working as expected:
  +Gnome Disks normally powers off the USB flash (tested on 4 different 
flashes and 2 USB cardreaders).
  - Gnome Disks does not spin down USB HDD (but udisks --detach does)

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: gnome-disk-utility 3.8.2-1ubuntu2
  ProcVersionSignature: Ubuntu 3.10.0-1.8-generic 3.10.0-rc7
  Uname: Linux 3.10.0-1-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.12.5-0ubuntu2
  Architecture: i386
  Date: Sat Oct 12 13:39:21 2013
  InstallationDate: Installed on 2013-03-06 (219 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha i386 (20130306)
  MarkForUpload: True
  SourcePackage: gnome-disk-utility
  UpgradeStatus: Upgraded to saucy on 2013-06-23 (110 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-disk-utility/+bug/1239087/+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 1239087]

[Swamp-a]

openSUSE-SU-2016:3021-1: An update that solves 12 vulnerabilities and
has 118 fixes is now available.

Category: security (important)
Bug References: 
1000189,1000287,1000304,1000776,1001419,1001486,1002165,1003079,1003153,1003400,1003568,1003866,1003925,1004252,1004418,1004462,1004517,1004520,1005666,1006691,1007615,1007886,744692,772786,789311,799133,857397,860441,865545,866130,868923,874131,875631,876145,876463,898675,904489,909994,911687,915183,921338,921784,922064,922634,924381,924384,930399,931454,934067,937086,937888,940545,941420,946309,954986,955446,956514,959463,961257,962846,963655,963767,966864,967640,970943,971975,971989,974406,974620,975596,975772,976195,977687,978094,979451,979681,979928,982783,983619,984194,984419,984779,984992,985562,986445,987192,987333,987542,987565,987621,987805,988440,988617,988715,989152,989953,990245,991247,991608,991665,992244,992555,992591,992593,992712,993392,993841,993890,993891,994296,994438,994520,994748,994758,995153,995968,996664,997059,997299,997708,997896,998689,998795,998825,999577,999584,999600,999779,07,32
CVE References: 
CVE-2013-5634,CVE-2015-8956,CVE-2016-2069,CVE-2016-5696,CVE-2016-6130,CVE-2016-6327,CVE-2016-6480,CVE-2016-6828,CVE-2016-7042,CVE-2016-7097,CVE-2016-7425,CVE-2016-8658
Sources used:
openSUSE 13.1 (src):cloop-2.639-11.36.1, crash-7.0.2-2.36.1, 
hdjmod-1.28-16.36.1, ipset-6.21.1-2.40.1, iscsitarget-1.4.20.3-13.36.1, 
kernel-debug-3.12.67-58.1, kernel-default-3.12.67-58.1, 
kernel-desktop-3.12.67-58.1, kernel-docs-3.12.67-58.2, kernel-ec2-3.12.67-58.1, 
kernel-pae-3.12.67-58.1, kernel-source-3.12.67-58.1, kernel-syms-3.12.67-58.1, 
kernel-trace-3.12.67-58.1, kernel-vanilla-3.12.67-58.1, 
kernel-xen-3.12.67-58.1, ndiswrapper-1.58-37.1, openvswitch-1.11.0-0.43.1, 
pcfclock-0.44-258.37.1, vhba-kmp-20130607-2.36.1, virtualbox-4.2.36-2.68.1, 
xen-4.3.4_10-69.1, xtables-addons-2.3-2.35.1

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

Title:
  Safely remove is not working (or broken) in Gnome Disks

Status in GNOME Disks:
  Fix Released
Status in udisks:
  Confirmed
Status in gnome-disk-utility package in Ubuntu:
  Fix Released
Status in gnome-disk-utility package in Fedora:
  Unknown
Status in gnome-disk-utility package in openSUSE:
  Invalid
Status in oem-workaround-xhci-quirk-dkms package in openSUSE:
  Fix Released

Bug description:
  In 12.04 I was able to safely remove USB-stick (make its LED off) and USB-HDD 
(do a spin down).
  In 13.04 this option is missed.

  In 13.10 it is appeared again, but not working as expected:
  +Gnome Disks normally powers off the USB flash (tested on 4 different 
flashes and 2 USB cardreaders).
  - Gnome Disks does not spin down USB HDD (but udisks --detach does)

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: gnome-disk-utility 3.8.2-1ubuntu2
  ProcVersionSignature: Ubuntu 3.10.0-1.8-generic 3.10.0-rc7
  Uname: Linux 3.10.0-1-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.12.5-0ubuntu2
  Architecture: i386
  Date: Sat Oct 12 13:39:21 2013
  InstallationDate: Installed on 2013-03-06 (219 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha i386 (20130306)
  MarkForUpload: True
  SourcePackage: gnome-disk-utility
  UpgradeStatus: Upgraded to saucy on 2013-06-23 (110 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-disk-utility/+bug/1239087/+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 1465721] Re: Package configuration should fail if the download fails

[Launchpad Bug Tracker]

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

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

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

Title:
  Package configuration should fail if the download fails

Status in flashplugin-nonfree package in Ubuntu:
  Confirmed
Status in msttcorefonts package in Ubuntu:
  Confirmed

Bug description:
  I'm using Ubuntu 15.10 dev with flashplugin-installer
  11.2.202.466ubuntu1 and if the package got successfully downloaded but
  on configuring it fails to download the flash player an error is shown
  but the configuring does not fail. This could lead to a broken flash
  player setup while the user might think all is fine as apt doesn't
  really claim anything.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/flashplugin-nonfree/+bug/1465721/+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 1465721] Re: Package configuration should fail if the download fails

[Launchpad Bug Tracker]

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

** Changed in: flashplugin-nonfree (Ubuntu)
   Status: New => Confirmed

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

Title:
  Package configuration should fail if the download fails

Status in flashplugin-nonfree package in Ubuntu:
  Confirmed
Status in msttcorefonts package in Ubuntu:
  Confirmed

Bug description:
  I'm using Ubuntu 15.10 dev with flashplugin-installer
  11.2.202.466ubuntu1 and if the package got successfully downloaded but
  on configuring it fails to download the flash player an error is shown
  but the configuring does not fail. This could lead to a broken flash
  player setup while the user might think all is fine as apt doesn't
  really claim anything.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/flashplugin-nonfree/+bug/1465721/+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 1647148] Re: Implement CUPS server snapd interface

[Launchpad Bug Tracker]

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

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

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

Title:
  Implement CUPS server snapd interface

Status in Canonical System Image:
  In Progress
Status in cups package in Ubuntu:
  Confirmed

Bug description:
  The CUPS server is an helpful feature, needed if you want to get
  convergence. Thanks for all your work, see you.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1647148/+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 1434591] Re: [mako] Cannot connect to a secure, shared "ap" hotspot

[Jose' Belmar]

What's the latest on this issue? When i flashed touch onto my nexus 4 i saw the 
hotspot menu item for the first boot, but afterward it disappeared. So does 
this mean that the hotspot bug will never be fixed for Nexus 4?
I have one slightlty off-topic question:
Is bluetooth file sharing also missing for similar reasons?

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

Title:
  [mako] Cannot connect to a secure, shared "ap" hotspot

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  $ system-image-cli -i
  current build number: 138
  device name: mako
  channel: ubuntu-touch/devel-proposed
  alias: ubuntu-touch/vivid-proposed
  last update: 2015-03-17 15:04:46
  version version: 138
  version ubuntu: 20150317.1
  version device: 20150210
  version custom: 20150317.1

  I have tried most types of security, but the spec [2] says for maximum
  compatibility, most of the options should be left blank. Blank
  settings failed on both a and bg bands.

  How to reproduce:
  1. Create a secure hotspot (I am using this [1] script)
  2. Confirm that the hotspot is active and appears secured for other devices

  What happens:
  Connecting to it fails.

  What should have happened:
  Connecting to it should not fail.

  Excerpt from syslog
  http://pastebin.ubuntu.com/10627959/

  Insecure hotspots should work using this [3] script.

  [1] http://pastebin.ubuntu.com/10683465/
  [2] https://developer.gnome.org/NetworkManager/stable/ref-settings.html
  [3] 
http://bazaar.launchpad.net/~mathieu-tl/+junk/touch-hotspot/view/head:/hotspot.py

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1434591/+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 1579415] Re: Ubuntu Software Center does not display third party apps or all installed apps

[avinas]

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

16.10 gnome - I have installed vlc. Installed it using cli. Software
center not showing it as installed app

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

Title:
  Ubuntu Software Center does not display third party apps or all
  installed apps

Status in gnome-software package in Ubuntu:
  Opinion

Bug description:
  Description:  Ubuntu 16.04 LTS
  Release:  16.04

  gnome-software:
    Installed: 3.20.1+git20160426.1.a976144-ubuntu-xenial-0ubuntu1
    Candidate: 3.20.1+git20160426.1.a976144-ubuntu-xenial-0ubuntu1
    Version table:
   *** 3.20.1+git20160426.1.a976144-ubuntu-xenial-0ubuntu1 500
  500 http://gb.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   3.20.1+git20160420.1.ca63436.ubuntu-xenial-0ubuntu2 500
  500 http://gb.archive.ubuntu.com/ubuntu xenial/main amd64 Packages

  The new Ubuntu Software Center does not display all software. For
  example no third party repo applications are displayed.

  Search for example:

  Ubuntu-restricted-extras - no results
  muon - no results
  krita - no results
  samba - no results

  These do not show under installed either, though they are installed.

  However, all are shown in Synaptic Package Manager and MUON

  Additional:

  I have installed the old Ubuntu Software Center and can confirm that
  ALL applications are correctly listed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1579415/+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 1647133] Re: dns=dnsmasq does not work any more

[Harry]

First of all,
If NM 1.4.2-2ubuntu4 needs the package resolvconf in order to function 
properly, it should depend on it.

Secondly,
NM 1.4.2-2ubuntu3 works perfectly, like all earlier versions, without the 
package resolvconf.

Thirdly,
after installing resolvconf with NM 1.4.2-2ubuntu4, NM still does not work 
properly. It is not OK.

And here are some test results.

With NM 1.4.2-2ubuntu3: "systemd-resolve --status"
Global
 DNS Servers: 127.0.1.1
  DNS Domain: dhcp.inet.fi
  DNSSEC NTA: 10.in-addr.arpa
  home
  internal
  intranet
  lan
  local
  private
  test
Link 2 (eth0)
  Current Scopes: LLMNR/IPv4 LLMNR/IPv6
   LLMNR setting: yes
MulticastDNS setting: no
  DNSSEC setting: allow-downgrade
DNSSEC supported: yes

With NM 1.4.2-2ubuntu4: "systemd-resolve --status"
Global
  DNSSEC NTA: 10.in-addr.arpa
  corp
  d.f.ip6.arpa
  home
  internal
  intranet
  lan
  local
  private
  test
Link 2 (eth0)
  Current Scopes: DNS LLMNR/IPv4 LLMNR/IPv6
   LLMNR setting: yes
MulticastDNS setting: no
  DNSSEC setting: allow-downgrade
DNSSEC supported: yes
 DNS Servers: 193.210.18.18
  193.210.19.19
  DNS Domain: dhcp.inet.fi

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

Title:
  dns=dnsmasq does not work any more

Status in network-manager package in Ubuntu:
  Triaged

Bug description:
  Network-manager will make my network connection immediately lost after 
updating to the newest version 1.4.2-2ubuntu4.
  However, downgrading to the previous version 1.4.2-2ubuntu3 the network 
connection is back again and fine. If, with this version, I remove the file 
(link) /etc/resolv.conf the network is broken again. Rebooting solves this, as 
network-manager creates a new resolv.conf file.

  The newest version 1.4.2-2ubuntu4 also creates the very same kind of
  file, but no network.

  I have the latest (Gnome-shell DE) updates installed and of course all 
packages that network-manager depends on. But not the ones it only recommends 
or suggests.
  Should I have resolvconf installed? I think not, as isc-dhcp-client only 
suggests it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1647133/+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 1646611] Re: mission-control should use different paths when in a snap environment

[Renato Araujo Oliveira Filho]

** Changed in: telepathy-mission-control-5 (Ubuntu)
 Assignee: (unassigned) => Renato Araujo Oliveira Filho (renatofilho)

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

Title:
  mission-control should use different paths when in a snap environment

Status in Canonical System Image:
  Confirmed
Status in telepathy-mission-control-5 package in Ubuntu:
  New

Bug description:
  When running confined into a snap environment, mission-control needs
  to use different paths for its files:

  Sep 30 05:31:22 localhost org.freedesktop.Telepathy.AccountManager[4688]: 
(process:4767): mcd-WARNING **: Unable to create directory 
'/snap/unity8-session/x1/usr/share/telepathy/mission-control': Read-only file 
system
  Sep 30 05:31:22 localhost org.freedesktop.Telepathy.AccountManager[4688]: 
(process:4767): mcd-WARNING **: Failed to create file 
'/snap/unity8-session/x1/usr/share/telepathy/mission-control/accounts.cfg.CC7LOY':
 No such file or directory
  Sep 30 05:31:22 localhost org.freedesktop.Telepathy.AccountManager[4688]: 
(process:4767): mcd-WARNING **: Unable to create directory 
'/snap/unity8-session/x1/usr/share/telepathy/mission-control': Read-only file 
system
  Sep 30 05:31:22 localhost org.freedesktop.Telepathy.AccountManager[4688]: 
(process:4767): mcd-WARNING **: Failed to create file 
'/snap/unity8-session/x1/usr/share/telepathy/mission-control/accounts.cfg.7I1LOY':
 No such file or

  Instead of using $SNAP, it probably should use $SNAP_DATA

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1646611/+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 1646611] Re: mission-control should use different paths when in a snap environment

[Bill Filler]

** Changed in: telepathy-mission-control-5 (Ubuntu)
   Importance: Undecided => Medium

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

Title:
  mission-control should use different paths when in a snap environment

Status in Canonical System Image:
  Confirmed
Status in telepathy-mission-control-5 package in Ubuntu:
  New

Bug description:
  When running confined into a snap environment, mission-control needs
  to use different paths for its files:

  Sep 30 05:31:22 localhost org.freedesktop.Telepathy.AccountManager[4688]: 
(process:4767): mcd-WARNING **: Unable to create directory 
'/snap/unity8-session/x1/usr/share/telepathy/mission-control': Read-only file 
system
  Sep 30 05:31:22 localhost org.freedesktop.Telepathy.AccountManager[4688]: 
(process:4767): mcd-WARNING **: Failed to create file 
'/snap/unity8-session/x1/usr/share/telepathy/mission-control/accounts.cfg.CC7LOY':
 No such file or directory
  Sep 30 05:31:22 localhost org.freedesktop.Telepathy.AccountManager[4688]: 
(process:4767): mcd-WARNING **: Unable to create directory 
'/snap/unity8-session/x1/usr/share/telepathy/mission-control': Read-only file 
system
  Sep 30 05:31:22 localhost org.freedesktop.Telepathy.AccountManager[4688]: 
(process:4767): mcd-WARNING **: Failed to create file 
'/snap/unity8-session/x1/usr/share/telepathy/mission-control/accounts.cfg.7I1LOY':
 No such file or

  Instead of using $SNAP, it probably should use $SNAP_DATA

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1646611/+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 1633838] Re: Garbled display after resuming from suspend

[Adam Andersson]

Same gpu and same problem after resuming from suspend. 
Running ubuntu 14.04 Uname 4.4.0-53-generic

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

Title:
  Garbled display after resuming from suspend

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

Bug description:
  Every time I resume from suspend, my display is garbled (looks a bit
  like the loading screen from a Commodore 64). A "sudo service lightdm
  restart" from a different console (Ctrl+Alt+F1) fixes the issue, but
  logs me out of the session as well. I get past the login screen, and
  sometimes the display is fine for about a minute or so, but it
  inevitably garbles up. The artifacts shift when I move my mouse, and
  will occasionally have a clear picture for a frame or two, or if my
  mouse is in a specific point, and not moving. This error was not
  present before I upgraded my system from an AMD RadeonHD 6870 to an
  Nvidia GeForce GTX 1060, and I therefore believe this is a bug in the
  nvidia drivers, rather than lightdm itself.

  Ubuntu 16.10
  nvidia-367:
Installed: 367.57-0ubuntu3
Candidate: 367.57-0ubuntu3
Version table:
   *** 367.57-0ubuntu3 500
  500 http://no.archive.ubuntu.com/ubuntu yakkety/restricted amd64 
Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: nvidia-367 367.57-0ubuntu3
  ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
  Uname: Linux 4.8.0-22-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  Date: Sun Oct 16 13:01:14 2016
  InstallationDate: Installed on 2016-07-20 (88 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  SourcePackage: nvidia-graphics-drivers-367
  UpgradeStatus: Upgraded to yakkety on 2016-10-13 (2 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-367/+bug/1633838/+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 1648538] [NEW] Custom keyboard shortcuts not work

[Luca Ciavatta]

Public bug reported:

1) Description: Ubuntu 16.04.1 LTS
   Release: 16.04

2) ubuntu-settings:
   Installed: 15.10.8
   Candidate: 15.10.8
   Version table:
   *** 15.10.8 500
   500 http://it.archive.ubuntu.com/ubuntu xenial/main amd64 
Packages
   500 http://it.archive.ubuntu.com/ubuntu xenial/main i386 Packages
   100 /var/lib/dpkg/status

3) I made some custom keyboard shortcuts under All Settings > Keyboard > 
Shortcuts
   In particular, I made these:
   CTRL+SHIFT+S - Custom screenshot - gnome-screenshot -f 
"$HOME/Pictures/Screenshots/$(date +%F_%H:%M:%S).png"
   CTRL+SHIFT+A - Custom screenshot area - gnome-screenshot -a -f 
"$HOME/Pictures/Screenshots/$(date +%F_%H:%M:%S).png"
   CTRL+SHIFT+W - Custom screenshot window - gnome-screenshot -w -f 
"$HOME/Pictures/Screenshots/$(date +%F_%H:%M:%S).png"

   I expected the shortcuts working when I press the right keys
combination.

4) Custom keyboard shortcuts not work.

   The shortcuts worked only one time and after never worked. If I use
the commands directly in a terminal window, the commands work fine.

** Affects: ubuntu-settings (Ubuntu)
 Importance: Undecided
 Status: New

** Package changed: gnome-settings-daemon (Ubuntu) => ubuntu-settings
(Ubuntu)

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

Title:
  Custom keyboard shortcuts not work

Status in ubuntu-settings package in Ubuntu:
  New

Bug description:
  1) Description:   Ubuntu 16.04.1 LTS
 Release:   16.04

  2) ubuntu-settings:
 Installed: 15.10.8
 Candidate: 15.10.8
 Version table:
 *** 15.10.8 500
 500 http://it.archive.ubuntu.com/ubuntu xenial/main amd64 
Packages
 500 http://it.archive.ubuntu.com/ubuntu xenial/main i386 
Packages
 100 /var/lib/dpkg/status

  3) I made some custom keyboard shortcuts under All Settings > Keyboard > 
Shortcuts
 In particular, I made these:
 CTRL+SHIFT+S - Custom screenshot - gnome-screenshot -f 
"$HOME/Pictures/Screenshots/$(date +%F_%H:%M:%S).png"
 CTRL+SHIFT+A - Custom screenshot area - gnome-screenshot -a -f 
"$HOME/Pictures/Screenshots/$(date +%F_%H:%M:%S).png"
 CTRL+SHIFT+W - Custom screenshot window - gnome-screenshot -w -f 
"$HOME/Pictures/Screenshots/$(date +%F_%H:%M:%S).png"

 I expected the shortcuts working when I press the right keys
  combination.

  4) Custom keyboard shortcuts not work.

 The shortcuts worked only one time and after never worked. If I use
  the commands directly in a terminal window, the commands work fine.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/1648538/+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 918489] Re: duplicity allows bad passphrase on full backup if archive cache exists

[Michael Terry]

I uploaded an update to trusty and yakkety.

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

Title:
  duplicity allows bad passphrase on full backup if archive cache exists

Status in Déjà Dup:
  Fix Released
Status in Duplicity:
  New
Status in deja-dup package in Ubuntu:
  Fix Released
Status in deja-dup source package in Trusty:
  New
Status in deja-dup source package in Xenial:
  Fix Committed
Status in deja-dup source package in Yakkety:
  Triaged

Bug description:
  when doing a backup for the first time, dejadup verifies your
  passphrase by having you enter it twice.

  on future incremental backups it doesn't need to do this because
  entering the wrong password will result in the backup failing.

  with the periodic 'full' backups that happen from time to time,
  however, any password will be accepted.

  this can lead to a situation where you accidentally type the wrong
  password once and are left in a situation where you don't know what
  you typed and have no way to get your files (or do another incremental
  backup on top of it).

  i think this is what happened to me recently.

  clearly, the fix is to explicitly verify the passphrase is correct
  when doing a new full backup.  this may be a duplicity bug.

  === Ubuntu deja-dup SRU information ===

  [impact]
  Users may unwittingly re-set their backup password and not be able to restore 
their data.

  [test case]
  - $ deja-dup-preferences # set up a dummy backup
  - $ deja-dup --backup # complete first encrypted full backup
  - $ rename 's/\.2016/\.2000/' /path/to/test/backup/*
  - $ rename 's/\.2016/\.2000/' ~/.cache/deja-dup/*/*
  - $ deja-dup --backup # second backup, enter the wrong password
  - $ deja-dup --restore # try to restore with original password

  [regression potential]
  Should be limited?  The fix is to delete the duplicity cache files, which 
ought to be safe to delete.

  It's possible if a full backup is being resumed, we might delete the
  current progress.  That is a better bug to have than this bug, though.
  A more complicated patch would need to be investigated to prevent
  that.

To manage notifications about this bug go to:
https://bugs.launchpad.net/deja-dup/+bug/918489/+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 1648531] [NEW] package gconf2 3.2.6-3ubuntu7 failed to install/upgrade: problém se závislostmi - nechávám spouštěče nezpracované

[Jan Machač]

Public bug reported:

...

ProblemType: Package
DistroRelease: Ubuntu 17.04
Package: gconf2 3.2.6-3ubuntu7
ProcVersionSignature: Ubuntu 4.8.0-30.32-generic 4.8.6
Uname: Linux 4.8.0-30-generic x86_64
ApportVersion: 2.20.3-0ubuntu8
Architecture: amd64
Date: Thu Dec  8 15:51:28 2016
ErrorMessage: problém se závislostmi - nechávám spouštěče nezpracované
InstallationDate: Installed on 2016-08-14 (115 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
RelatedPackageVersions:
 dpkg 1.18.10ubuntu1
 apt  1.3.1
SourcePackage: gconf
Title: package gconf2 3.2.6-3ubuntu7 failed to install/upgrade: problém se 
závislostmi - nechávám spouštěče nezpracované
UpgradeStatus: Upgraded to zesty on 2016-12-08 (0 days ago)

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


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

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

Title:
  package gconf2 3.2.6-3ubuntu7 failed to install/upgrade: problém se
  závislostmi - nechávám spouštěče nezpracované

Status in gconf package in Ubuntu:
  New

Bug description:
  ...

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: gconf2 3.2.6-3ubuntu7
  ProcVersionSignature: Ubuntu 4.8.0-30.32-generic 4.8.6
  Uname: Linux 4.8.0-30-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  Date: Thu Dec  8 15:51:28 2016
  ErrorMessage: problém se závislostmi - nechávám spouštěče nezpracované
  InstallationDate: Installed on 2016-08-14 (115 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1
   apt  1.3.1
  SourcePackage: gconf
  Title: package gconf2 3.2.6-3ubuntu7 failed to install/upgrade: problém se 
závislostmi - nechávám spouštěče nezpracované
  UpgradeStatus: Upgraded to zesty on 2016-12-08 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1648531/+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 1648533] [NEW] package libgl1-mesa-dri:amd64 11.2.0-1ubuntu2.2 failed to install/upgrade: problemas com dependências - a deixar por configurar

[Simão Pedro]

Public bug reported:

I don't know

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: libgl1-mesa-dri:amd64 11.2.0-1ubuntu2.2
ProcVersionSignature: Ubuntu 4.4.0-53.74-generic 4.4.30
Uname: Linux 4.4.0-53-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
BootLog:
 
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Tue Dec  6 17:50:32 2016
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
ErrorMessage: problemas com dependências - a deixar por configurar
GraphicsCard:
 Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
   Subsystem: Micro-Star International Co., Ltd. [MSI] 4th Gen Core Processor 
Integrated Graphics Controller [1462:1109]
   Subsystem: Micro-Star International Co., Ltd. [MSI] GM107M [GeForce GTX 
860M] [1462:1109]
InstallationDate: Installed on 2016-11-15 (22 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
MachineType: Micro-Star International Co., Ltd. GE70 2PE
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-53-generic 
root=UUID=14471d52-d1c0-4adc-b139-2067cc55be55 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.1
 apt  1.2.15
SourcePackage: mesa
Title: package libgl1-mesa-dri:amd64 11.2.0-1ubuntu2.2 failed to 
install/upgrade: problemas com dependências - a deixar por configurar
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/28/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: E1759IMS.515
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: MS-1759
dmi.board.vendor: Micro-Star International Co., Ltd.
dmi.board.version: REV:0.B
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Micro-Star International Co., Ltd.
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE1759IMS.515:bd03/28/2014:svnMicro-StarInternationalCo.,Ltd.:pnGE702PE:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-1759:rvrREV0.B:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A:
dmi.product.name: GE70 2PE
dmi.product.version: REV:1.0
dmi.sys.vendor: Micro-Star International Co., Ltd.
version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2
version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2
version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2
xserver.bootTime: Thu Dec  8 15:03:05 2016
xserver.configfile: default
xserver.errors:
 Failed to load module "nvidia" (module does not exist, 0)
 Failed to load module "nvidia" (module does not exist, 0)
 Unknown chipset: NV117
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id5941 
 vendor CMN
xserver.version: 2:1.18.4-0ubuntu0.2

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

Title:
  package libgl1-mesa-dri:amd64 11.2.0-1ubuntu2.2 failed to
  install/upgrade: problemas com dependências - a deixar por configurar

Status in mesa package in Ubuntu:
  New

Bug description:
  I don't know

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libgl1-mesa-dri:amd64 11.2.0-1ubuntu2.2
  ProcVersionSignature: Ubuntu 4.4.0-53.74-generic 4.4.30
  Uname: Linux 4.4.0-53-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  BootLog:
   
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Tue Dec  6 17:50:32 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ErrorMessage: problemas com dependências - a deixar por configurar
  GraphicsCard:
   Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: Micro-Star International Co., Ltd. [MSI] 4th Gen Core Processor 
Integrated Graphics Controller [1462:1109]

[Desktop-packages] [Bug 1648534] [NEW] /usr/bin/gnome-software:5:g_wakeup_new:g_main_context_new:g_dbus_connection_send_message_with_reply_sync:g_dbus_connection_call_sync_internal:g_dbus_connection_c

[errors.ubuntu.com bug bridge]

Public bug reported:

The Ubuntu Error Tracker has been receiving reports about a problem regarding 
gnome-software.  This problem was most recently seen with package version 
3.20.1+git20161013.0.d77d6cf-0ubuntu2~xenial1, the problem page at 
https://errors.ubuntu.com/problem/70c23d0f4e2be24b26672427d4218dc8f0823597 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
If you do not have access to the Ubuntu Error Tracker you can request it at 
http://forms.canonical.com/reports/.

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


** Tags: trusty xenial yakkety zesty

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

Title:
  /usr/bin/gnome-
  
software:5:g_wakeup_new:g_main_context_new:g_dbus_connection_send_message_with_reply_sync:g_dbus_connection_call_sync_internal:g_dbus_connection_call_sync

Status in gnome-software package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
gnome-software.  This problem was most recently seen with package version 
3.20.1+git20161013.0.d77d6cf-0ubuntu2~xenial1, the problem page at 
https://errors.ubuntu.com/problem/70c23d0f4e2be24b26672427d4218dc8f0823597 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker you can request it at 
http://forms.canonical.com/reports/.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1648534/+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 918489] Re: duplicity allows bad passphrase on full backup if archive cache exists

[Michael Terry]

** Tags removed: verification-needed
** Tags added: verification-needed-xenial

** Description changed:

  when doing a backup for the first time, dejadup verifies your passphrase
  by having you enter it twice.
  
  on future incremental backups it doesn't need to do this because
  entering the wrong password will result in the backup failing.
  
  with the periodic 'full' backups that happen from time to time, however,
  any password will be accepted.
  
  this can lead to a situation where you accidentally type the wrong
  password once and are left in a situation where you don't know what you
  typed and have no way to get your files (or do another incremental
  backup on top of it).
  
  i think this is what happened to me recently.
  
  clearly, the fix is to explicitly verify the passphrase is correct when
  doing a new full backup.  this may be a duplicity bug.
  
  === Ubuntu deja-dup SRU information ===
  
  [impact]
  Users may unwittingly re-set their backup password and not be able to restore 
their data.
  
  [test case]
  - $ deja-dup-preferences # set up a dummy backup
  - $ deja-dup --backup # complete first encrypted full backup
  - $ rename 's/\.2016/\.2000/' /path/to/test/backup/*
  - $ rename 's/\.2016/\.2000/' ~/.cache/deja-dup/*/*
  - $ deja-dup --backup # second backup, enter the wrong password
  - $ deja-dup --restore # try to restore with original password
  
  [regression potential]
  Should be limited?  The fix is to delete the duplicity cache files, which 
ought to be safe to delete.
+ 
+ It's possible if a full backup is being resumed, we might delete the
+ current progress.  That is a better bug to have than this bug, though.
+ A more complicated patch would need to be investigated to prevent that.

** No longer affects: deja-dup (Ubuntu Precise)

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

Title:
  duplicity allows bad passphrase on full backup if archive cache exists

Status in Déjà Dup:
  Fix Released
Status in Duplicity:
  New
Status in deja-dup package in Ubuntu:
  Fix Released
Status in deja-dup source package in Trusty:
  New
Status in deja-dup source package in Xenial:
  Fix Committed
Status in deja-dup source package in Yakkety:
  Triaged

Bug description:
  when doing a backup for the first time, dejadup verifies your
  passphrase by having you enter it twice.

  on future incremental backups it doesn't need to do this because
  entering the wrong password will result in the backup failing.

  with the periodic 'full' backups that happen from time to time,
  however, any password will be accepted.

  this can lead to a situation where you accidentally type the wrong
  password once and are left in a situation where you don't know what
  you typed and have no way to get your files (or do another incremental
  backup on top of it).

  i think this is what happened to me recently.

  clearly, the fix is to explicitly verify the passphrase is correct
  when doing a new full backup.  this may be a duplicity bug.

  === Ubuntu deja-dup SRU information ===

  [impact]
  Users may unwittingly re-set their backup password and not be able to restore 
their data.

  [test case]
  - $ deja-dup-preferences # set up a dummy backup
  - $ deja-dup --backup # complete first encrypted full backup
  - $ rename 's/\.2016/\.2000/' /path/to/test/backup/*
  - $ rename 's/\.2016/\.2000/' ~/.cache/deja-dup/*/*
  - $ deja-dup --backup # second backup, enter the wrong password
  - $ deja-dup --restore # try to restore with original password

  [regression potential]
  Should be limited?  The fix is to delete the duplicity cache files, which 
ought to be safe to delete.

  It's possible if a full backup is being resumed, we might delete the
  current progress.  That is a better bug to have than this bug, though.
  A more complicated patch would need to be investigated to prevent
  that.

To manage notifications about this bug go to:
https://bugs.launchpad.net/deja-dup/+bug/918489/+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 918489] Re: duplicity allows bad passphrase on full backup if archive cache exists

[Michael Terry]

** Also affects: deja-dup (Ubuntu Precise)
   Importance: Undecided
   Status: New

** Also affects: deja-dup (Ubuntu Trusty)
   Importance: Undecided
   Status: New

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

Title:
  duplicity allows bad passphrase on full backup if archive cache exists

Status in Déjà Dup:
  Fix Released
Status in Duplicity:
  New
Status in deja-dup package in Ubuntu:
  Fix Released
Status in deja-dup source package in Trusty:
  New
Status in deja-dup source package in Xenial:
  Fix Committed
Status in deja-dup source package in Yakkety:
  Triaged

Bug description:
  when doing a backup for the first time, dejadup verifies your
  passphrase by having you enter it twice.

  on future incremental backups it doesn't need to do this because
  entering the wrong password will result in the backup failing.

  with the periodic 'full' backups that happen from time to time,
  however, any password will be accepted.

  this can lead to a situation where you accidentally type the wrong
  password once and are left in a situation where you don't know what
  you typed and have no way to get your files (or do another incremental
  backup on top of it).

  i think this is what happened to me recently.

  clearly, the fix is to explicitly verify the passphrase is correct
  when doing a new full backup.  this may be a duplicity bug.

  === Ubuntu deja-dup SRU information ===

  [impact]
  Users may unwittingly re-set their backup password and not be able to restore 
their data.

  [test case]
  - $ deja-dup-preferences # set up a dummy backup
  - $ deja-dup --backup # complete first encrypted full backup
  - $ rename 's/\.2016/\.2000/' /path/to/test/backup/*
  - $ rename 's/\.2016/\.2000/' ~/.cache/deja-dup/*/*
  - $ deja-dup --backup # second backup, enter the wrong password
  - $ deja-dup --restore # try to restore with original password

  [regression potential]
  Should be limited?  The fix is to delete the duplicity cache files, which 
ought to be safe to delete.

  It's possible if a full backup is being resumed, we might delete the
  current progress.  That is a better bug to have than this bug, though.
  A more complicated patch would need to be investigated to prevent
  that.

To manage notifications about this bug go to:
https://bugs.launchpad.net/deja-dup/+bug/918489/+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 1580123] Re: xrandr --scale (again) confines mouse to native solution

[Paul Donohue]

As noted in https://bugs.launchpad.net/xorg-
server/+bug/883319/comments/62 , the fix for #883319 requires --panning
to be specified with --scaling in order to disable the mouse constraints
when scaling.

Ideally, xorg should be modified such that the mouse constraints are
calculated based on the --scaling and --panning settings, rather than
being disabled when --panning is enabled.  Short of that, it would be
nice if xorg was modified to disable the mouse constraints when
--scaling is enabled (in addition to when --panning is enabled).  If
neither of those can be accomplished, it would probably be sufficient to
simply document (in the man page?) that --panning may be needed to
disable the mouse constraints when using --scaling.

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

Title:
  xrandr --scale (again) confines mouse to native solution

Status in X.Org X server:
  Unknown
Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  This might be a regression where the original issue is:
  https://bugs.launchpad.net/xorg-server/+bug/883319

  It can be easily reproduced by doing something like:

  xrandr --output DP1 --scale 1.25x1.25

  The mouse will be still constrained to the native solution (aka you
  can't move the mouse outside a box of whatever DP1 had as resolution
  before.

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

  $ xrandr --version
  xrandr program version   1.5.0
  Server reports RandR version 1.5

  $ apt-cache policy xserver-xorg-core
  xserver-xorg-core:
Installed: 2:1.18.3-1ubuntu2

To manage notifications about this bug go to:
https://bugs.launchpad.net/xorg-server/+bug/1580123/+subscriptions

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

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

[Launchpad Bug Tracker]

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

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

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

Title:
  evince displays blank thumbnails for some pages

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

Bug description:
  Hi,

  To reproduce this bug:

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

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

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

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

[Desktop-packages] [Bug 1648107] Re: $XAUTHORITY should move into $XDG_RUNTIME_DIR

[Markus Kuhn]

As a workaround, install the attached shell script as

  /etc/X11/Xsession.d/10local-xauthority

It uses xauth to merge ~/.Xauthority into $XDG_RUNTIME_DIR/xauthority
and then updates XAUTHORITY to point at that location.

(Note that the "xauth merge" command will leave a warning such as
"xauth:  file /run/user/1597/xauthority does not exist" in ~/.xsession-
errors.)

In the long run, it would of course be more elegant if LightDM (and
other display managers) created the X authority file there in the first
place.


** Attachment added: "/etc/X11/Xsession.d/10local-xauthority"
   
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1648107/+attachment/4789021/+files/local-xauthority

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

Title:
  $XAUTHORITY should move into $XDG_RUNTIME_DIR

Status in lightdm package in Ubuntu:
  Triaged

Bug description:
  Historically, the X authority file was placed into $HOME/.Xauthority
  such that X11 clients on remote servers could access it in
  environments in which $HOME is located on a network file system.

  Today, this practice has become an anachronism that causes far more
  problems than it solves:

  a) Remote X11 clients are typically started today via "ssh -X", which
  emulates its own X11 server port $DISPLAY and therefore always creates
  its own X authority file entry on the remote server. Therefore, there
  is no longer any practical benefit from having the X authority file
  located in $HOME.

  b) If $HOME is on a network file system that implements "root squash",
  then commands such as "sudo xterm" or "sudo wireshark" won't work to
  start an X client with root privileges, as root is not able to read
  ~/.Xauthority via NFS. :-(

  c) If $HOME is on a network file system with Kerberos authentication,
  then users can easily get locked out by their screensavers once the
  Kerberos ticket expires. This is because some screen lockers (e.g.,
  gnome-screensaver) invoke a separate utility (e.g., /usr/lib/gnome-
  screensaver/gnome-screensaver-dialog) in order to ask the user of a
  locked screen for their password. Such a tool needs to access
  $XAUTHORITY right before it can display the password prompt, which
  will fail if the user's Kerberos ticket has expired (e.g. because a
  machine was suspended for 24 hours and therefore the ticket was not
  refreshed automatically on time). Without the ability to ask for a
  password, the screensaver then cannot call pam_krb5 to renew the
  user's Kerberos ticket, and the user remains locked out in a deadlock
  situation. :-(

  Both b) and c) are regular reasons for support requests in
  educational/corporate Linux environments with $HOME on Kerberized NFS.

  The solution is simple. Instead of $HOME/.Xauthority, just use in
  future $XDG_RUNTIME_DIR/xauthority as the location of the X authority
  file. (In case $XDG_RUNTIME_DIR/ does not exist, /tmp/xauthority-$USER
  might be a suitable fallback option.)

  According to https://standards.freedesktop.org/basedir-spec/basedir-
  spec-latest.html the $XDG_RUNTIME_DIR has all the right properties for
  holding the X authority file: it is always located in a local tmpfs
  filesystem, guaranteed to be accessible only to the current user, and
  will be wiped when the user has closed all sessions.

  On modern Linux systems, pam_systemd usually creates
  XDG_RUNTIME_DIR=/run/user/$UID, and wipes it in the end.

  (Note that according to https://standards.freedesktop.org/basedir-spec
  /basedir-spec-latest.html you should set the "sticky bit" on any files
  created in $XDG_RUNTIME_DIR whose timestamp is not updated regularly.)

  Feature request: please provide an option for LightDM to do the
  equivalent of

export XAUTHORITY=$XDG_RUNTIME_DIR/xauthority
chmod +t $XAUTHORITY

  and encourage Linux distribution maintainers to set this option by
  default, such that ~/.Xauthority is no longer used.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1648107/+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 1442649] Re: nautilus trash doesn't include btrfs and zfs subvolumes

[Ken Mollerup]

The problem manifest itself on ext4 formated volumes, and Thunar!

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

Title:
  nautilus trash doesn't include btrfs and zfs subvolumes

Status in GLib:
  Confirmed
Status in glib2.0 package in Ubuntu:
  Triaged
Status in gvfs package in Ubuntu:
  Triaged
Status in nautilus package in Ubuntu:
  Triaged

Bug description:
  Files in `/path/to/subvolume/.Trash-1000` aren't listed in the global
  trash.

  Comment by bug triage team: comment 4 has a spot-on analysis of where
  this issue is coming from, an inconsistency between trash handling in
  gvfs and glib/gio.  The problem has been around for quite a while.

To manage notifications about this bug go to:
https://bugs.launchpad.net/glib/+bug/1442649/+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 1647600] Re: Xvfb fails with new mesa, results in ubiquity FTBFS

[Timo Aaltonen]

this bug is in libepoxy

https://bugzilla.redhat.com/show_bug.cgi?id=1395366

** Bug watch added: Red Hat Bugzilla #1395366
   https://bugzilla.redhat.com/show_bug.cgi?id=1395366

** Package changed: mesa (Ubuntu) => libepoxy (Ubuntu)

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

** Changed in: libepoxy (Ubuntu)
 Assignee: (unassigned) => Timo Aaltonen (tjaalton)

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

Title:
  Xvfb fails with new mesa, results in ubiquity FTBFS

Status in libepoxy package in Ubuntu:
  In Progress

Bug description:
  Expectation:

  fakeroot ./debian/rules tests

  from ubiquity 17.04.1 package, from zesty-proposed to build
  successfully.

  It does in zesty-release. It does in zesty-proposed too, if one
  downgrades: libgl1-mesa-glx libglapi-mesa

  If one uses libgl1-mesa-glx libglapi-mesa from zesty-proposed, the
  Xvfb fails to spawn and thus tests fail, and the build fails.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libepoxy/+bug/1647600/+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 1643467] Re: Firefox 50 blocks Ubuntu 12.04 and 14.04 LTS's version of libavcodec

[Marc Deslauriers]

** Changed in: firefox (Ubuntu Trusty)
   Status: Confirmed => Fix Released

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

Title:
  Firefox 50 blocks Ubuntu 12.04 and 14.04 LTS's version of libavcodec

Status in libav:
  Unknown
Status in firefox package in Ubuntu:
  Confirmed
Status in libav package in Ubuntu:
  Invalid
Status in firefox source package in Precise:
  Confirmed
Status in libav source package in Precise:
  Confirmed
Status in firefox source package in Trusty:
  Fix Released
Status in libav source package in Trusty:
  Fix Released

Bug description:
  Whenever it tries to play a video, Firefox 50 displays this message at the 
top of every page:
  "libavcodec may be vulnerable or is not supported, and should be updated to 
play video"

  https://dxr.mozilla.org/mozilla-central/source/browser/locales/en-
  
US/chrome/browser/browser.properties?q=%22libavcodec+may+be+vulnerable%22_type=single#742

  Firefox refuses any libavcodec version prior to 54.35.1 (unless
  media.libavcodec.allow-obsolete==true).

  https://dxr.mozilla.org/mozilla-
  central/source/dom/media/platforms/ffmpeg/FFmpegLibWrapper.cpp#60

  Users should not be subjected to this warning, as it is vague (does not 
instruct them how to fix it).
  Ubuntu 14.04 LTS should ship with an updated version of libavcodec.

  DistroRelease: Ubuntu 14.04
  Package: firefox 50.0+build2-0ubuntu0.14.04.2

To manage notifications about this bug go to:
https://bugs.launchpad.net/libav/+bug/1643467/+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 1574667] Re: Mouse pointer occasionally jumps to the bottom-left corner

[Noah Johnson]

I also have this same problem. My trackpad is unusable. Ubuntu 16.04
LTS, Lenovo IdeaPad Y700.

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

Title:
  Mouse pointer occasionally jumps to the bottom-left corner

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  Sometimes the mouse pointer jumps directly to the bottom-left corner
  of the screen, which results in opening the trash window when
  clicking.

  This seems to be related: https://ubuntu-mate.community/t/mouse-
  pointer-jumps-on-clicking-touchpad/2932.

  Thanks,
  MZ

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  BootLog: /dev/sda6: clean, 276587/40779776 files, 15261626/163117056 blocks
  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 Apr 25 15:55:54 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Sky Lake Integrated Graphics [8086:1916] (rev 07) (prog-if 
00 [VGA controller])
 Subsystem: Dell Skylake Integrated Graphics [1028:06b2]
  InstallationDate: Installed on 2016-04-23 (2 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:07dc Intel Corp. 
   Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 002: ID 064e:920b Suyin Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 5559
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic.efi.signed 
root=UUID=c5bc0a1d-3fe9-4ae5-81e9-de7d141b419c ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/21/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.1.5
  dmi.board.name: 06CMH7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.1.5:bd12/21/2015:svnDellInc.:pnInspiron5559:pvr:rvnDellInc.:rn06CMH7:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Inspiron 5559
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Mon Apr 25 13:43:44 2016
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id1156 
   vendor LGD
  xserver.version: 2:1.18.3-1ubuntu2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1574667/+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 1643467] Re: Firefox 50 blocks Ubuntu 12.04 and 14.04 LTS's version of libavcodec

[Launchpad Bug Tracker]

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

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

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

Title:
  Firefox 50 blocks Ubuntu 12.04 and 14.04 LTS's version of libavcodec

Status in libav:
  Unknown
Status in firefox package in Ubuntu:
  Confirmed
Status in libav package in Ubuntu:
  Invalid
Status in firefox source package in Precise:
  Confirmed
Status in libav source package in Precise:
  Confirmed
Status in firefox source package in Trusty:
  Confirmed
Status in libav source package in Trusty:
  Fix Released

Bug description:
  Whenever it tries to play a video, Firefox 50 displays this message at the 
top of every page:
  "libavcodec may be vulnerable or is not supported, and should be updated to 
play video"

  https://dxr.mozilla.org/mozilla-central/source/browser/locales/en-
  
US/chrome/browser/browser.properties?q=%22libavcodec+may+be+vulnerable%22_type=single#742

  Firefox refuses any libavcodec version prior to 54.35.1 (unless
  media.libavcodec.allow-obsolete==true).

  https://dxr.mozilla.org/mozilla-
  central/source/dom/media/platforms/ffmpeg/FFmpegLibWrapper.cpp#60

  Users should not be subjected to this warning, as it is vague (does not 
instruct them how to fix it).
  Ubuntu 14.04 LTS should ship with an updated version of libavcodec.

  DistroRelease: Ubuntu 14.04
  Package: firefox 50.0+build2-0ubuntu0.14.04.2

To manage notifications about this bug go to:
https://bugs.launchpad.net/libav/+bug/1643467/+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 1643467] Re: Firefox 50 blocks Ubuntu 12.04 and 14.04 LTS's version of libavcodec

[Launchpad Bug Tracker]

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

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

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

Title:
  Firefox 50 blocks Ubuntu 12.04 and 14.04 LTS's version of libavcodec

Status in libav:
  Unknown
Status in firefox package in Ubuntu:
  Confirmed
Status in libav package in Ubuntu:
  Invalid
Status in firefox source package in Precise:
  Confirmed
Status in libav source package in Precise:
  Confirmed
Status in firefox source package in Trusty:
  Confirmed
Status in libav source package in Trusty:
  Fix Released

Bug description:
  Whenever it tries to play a video, Firefox 50 displays this message at the 
top of every page:
  "libavcodec may be vulnerable or is not supported, and should be updated to 
play video"

  https://dxr.mozilla.org/mozilla-central/source/browser/locales/en-
  
US/chrome/browser/browser.properties?q=%22libavcodec+may+be+vulnerable%22_type=single#742

  Firefox refuses any libavcodec version prior to 54.35.1 (unless
  media.libavcodec.allow-obsolete==true).

  https://dxr.mozilla.org/mozilla-
  central/source/dom/media/platforms/ffmpeg/FFmpegLibWrapper.cpp#60

  Users should not be subjected to this warning, as it is vague (does not 
instruct them how to fix it).
  Ubuntu 14.04 LTS should ship with an updated version of libavcodec.

  DistroRelease: Ubuntu 14.04
  Package: firefox 50.0+build2-0ubuntu0.14.04.2

To manage notifications about this bug go to:
https://bugs.launchpad.net/libav/+bug/1643467/+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 1648441] [NEW] Touchpad is not detected by Ubuntu 14.04 (ASUS UX501VW)

[OliverE]

Public bug reported:

I followed instructions and this is my Xorg.0.log:
The touchpad works for clicking (as a basic mouse) but is not able to perform 
advanced features (multitouch, scrolling,..).

System:
Description:Ubuntu 14.04.5 LTS
Release:14.04

Xorg.0.log:

[ 3.368]
X.Org X Server 1.17.2
Release Date: 2015-06-16
[ 3.368] X Protocol Version 11, Revision 0
[ 3.368] Build Operating System: Linux 3.19.0-43-generic x86_64 Ubuntu
[ 3.368] Current Operating System: Linux OliverUbuntu 4.2.0-42-generic 
#49~14.04.1-Ubuntu SMP Wed Jun 29 20:22:11 UTC 2016 x86_64
[ 3.368] Kernel command line: 
BOOT_IMAGE=/boot/vmlinuz-4.2.0-42-generic.efi.signed 
root=UUID=2c78f064-bf47-445e-87f2-2ddc519024ff ro quiet splash vt.handoff=7
[ 3.368] Build Date: 15 January 2016  10:17:33PM
[ 3.368] xorg-server 2:1.17.2-1ubuntu9.1~trusty1 (For technical support 
please see http://www.ubuntu.com/support)
[ 3.368] Current version of pixman: 0.30.2
[ 3.368]Before reporting problems, check http://wiki.x.org
 to make sure that you have the latest version.
[ 3.368] Markers: (--) probed, (**) from config file, (==) default setting,
 (++) from command line, (!!) notice, (II) informational,
 (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[ 3.368] (==) Log file: "/var/log/Xorg.0.log", Time: Thu Dec  8 11:49:49 
2016
[ 3.369] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[ 3.372] (==) No Layout section.  Using the first Screen section.
[ 3.372] (==) No screen section available. Using defaults.
[ 3.372] (**) |-->Screen "Default Screen Section" (0)
[ 3.372] (**) |   |-->Monitor ""
[ 3.372] (==) No monitor specified for screen "Default Screen Section".
 Using a default monitor configuration.
[ 3.372] (==) Automatically adding devices
[ 3.372] (==) Automatically enabling devices
[ 3.372] (==) Automatically adding GPU devices
[ 3.372] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist.
[ 3.372]Entry deleted from font path.
[ 3.372] (WW) The directory "/usr/share/fonts/X11/100dpi/" does not exist.
[ 3.372]Entry deleted from font path.
[ 3.372] (WW) The directory "/usr/share/fonts/X11/75dpi/" does not exist.
[ 3.372]Entry deleted from font path.
[ 3.373] (WW) The directory "/usr/share/fonts/X11/100dpi" does not exist.
[ 3.373]Entry deleted from font path.
[ 3.373] (WW) The directory "/usr/share/fonts/X11/75dpi" does not exist.
[ 3.373]Entry deleted from font path.
[ 3.373] (==) FontPath set to:
 /usr/share/fonts/X11/misc,
 /usr/share/fonts/X11/Type1,
 built-ins
[ 3.373] (==) ModulePath set to 
"/usr/lib/x86_64-linux-gnu/xorg/extra-modules,/usr/lib/xorg/extra-modules,/usr/lib/xorg/modules"
[ 3.373] (II) The server relies on udev to provide the list of input 
devices.
 If no devices become available, reconfigure udev or disable AutoAddDevices.
[ 3.373] (II) Loader magic: 0x558d0863cc80
[ 3.373] (II) Module ABI versions:
[ 3.373]X.Org ANSI C Emulation: 0.4
[ 3.373]X.Org Video Driver: 19.0
[ 3.373]X.Org XInput driver : 21.0
[ 3.373]X.Org Server Extension : 9.0
[ 3.373] (II) xfree86: Adding drm device (/dev/dri/card0)
[ 3.477] (--) PCI:*(0:0:2:0) 8086:191b:1043:1080 rev 6, Mem @ 
0xdb00/16777216, 0x7000/268435456, I/O @ 0xf000/64
[ 3.477] (--) PCI: (0:1:0:0) 10de:139b:1043:1080 rev 162, Mem @ 
0xdc00/16777216, 0xb000/268435456, 0xc000/33554432, I/O @ 
0xe000/128, BIOS @ 0x/524288
[ 3.478] (II) LoadModule: "glx"
[ 3.478] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[ 3.490] (II) Module glx: vendor="X.Org Foundation"
[ 3.490]compiled for 1.17.2, module version = 1.0.0
[ 3.490]ABI class: X.Org Server Extension, version 9.0
[ 3.490] (==) AIGLX enabled
[ 3.490] (==) Matched intel as autoconfigured driver 0
[ 3.490] (==) Matched intel as autoconfigured driver 1
[ 3.490] (==) Matched modesetting as autoconfigured driver 2
[ 3.490] (==) Matched fbdev as autoconfigured driver 3
[ 3.490] (==) Matched vesa as autoconfigured driver 4
[ 3.490] (==) Assigned the driver to the xf86ConfigLayout
[ 3.490] (II) LoadModule: "intel"
[ 3.491] (II) Loading /usr/lib/xorg/modules/drivers/intel_drv.so
[ 3.496] (II) Module intel: vendor="X.Org Foundation"
[ 3.496]compiled for 1.17.2, module version = 2.99.917
[ 3.496]Module class: X.Org Video Driver
[ 3.496]ABI class: X.Org Video Driver, version 19.0
[ 3.496] (II) LoadModule: "modesetting"
[ 3.496] (II) Loading /usr/lib/xorg/modules/drivers/modesetting_drv.so
[ 3.497] (II) Module modesetting: vendor="X.Org Foundation"
[ 3.497]compiled for 1.17.2, module version = 1.17.2
[ 3.497]Module class: X.Org Video Driver
[ 3.497]ABI class: X.Org Video Driver, version 19.0
[ 3.497] (II) LoadModule: 

[Desktop-packages] [Bug 1237999] Re: Amazon webapp always going to amazon.com

[Will Cooke]

Still a problem today in 16.04.

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

Title:
  Amazon webapp always going to amazon.com

Status in webapps-applications package in Ubuntu:
  Confirmed

Bug description:
  On up to date Saucy Beta the amazon webapp always goes to amazon.com rather 
than amazon.co.uk
  When I run
  unity-webapps-runner --amazon --app-id=ubuntu-amazon-default
  I see
  ** (unity-webapps-runner:4259): WARNING **: Could not get a proper accuracy 
from Geoclue (NONE)
  which I guess may be the problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: unity-webapps-common 2.4.17+13.10.20130924.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
  Uname: Linux 3.11.0-12-generic i686
  ApportVersion: 2.12.5-0ubuntu1
  Architecture: i386
  Date: Thu Oct 10 13:53:52 2013
  InstallationDate: Installed on 2012-08-01 (434 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha i386 (20120730.1)
  MarkForUpload: True
  PackageArchitecture: all
  SourcePackage: webapps-applications
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/webapps-applications/+bug/1237999/+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 712829] Re: Evolution - Message sort order by time incorrect

[Launchpad Bug Tracker]

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

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

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

Title:
  Evolution - Message sort order by time incorrect

Status in evolution package in Ubuntu:
  Confirmed
Status in evolution package in Fedora:
  New

Bug description:
  Binary package hint: evolution

  Evolution 2.30.3
  Email messages sorted by date & time, with most recent at the top of list.

  Problem: Several messages received during day show time only. The time
  shown is in reverse order than expected. Emails received early in the
  day at the top of the list.

  Example: In the date column
  Today 15:29
  Today 15:39
  Today 16:08
  Today 16:48

  The Emails are sorted properly by date, but "mess up" for those
  received within a particular day

  ProblemType: Bug
  DistroRelease: Ubuntu 10.10
  Package: evolution 2.30.3-1ubuntu7.3
  ProcVersionSignature: Ubuntu 2.6.35-25.44-generic 2.6.35.10
  Uname: Linux 2.6.35-25-generic i686
  Architecture: i386
  Date: Thu Feb  3 18:54:28 2011
  ExecutablePath: /usr/bin/evolution
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007)
  ProcEnviron:
   SHELL=/bin/bash
   LANG=en_CA.utf8
  SourcePackage: evolution

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/712829/+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 712829] Re: Evolution - Message sort order by time incorrect

[Simon Brandner]

** Also affects: evolution (Fedora)
   Importance: Undecided
   Status: New

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

Title:
  Evolution - Message sort order by time incorrect

Status in evolution package in Ubuntu:
  Confirmed
Status in evolution package in Fedora:
  New

Bug description:
  Binary package hint: evolution

  Evolution 2.30.3
  Email messages sorted by date & time, with most recent at the top of list.

  Problem: Several messages received during day show time only. The time
  shown is in reverse order than expected. Emails received early in the
  day at the top of the list.

  Example: In the date column
  Today 15:29
  Today 15:39
  Today 16:08
  Today 16:48

  The Emails are sorted properly by date, but "mess up" for those
  received within a particular day

  ProblemType: Bug
  DistroRelease: Ubuntu 10.10
  Package: evolution 2.30.3-1ubuntu7.3
  ProcVersionSignature: Ubuntu 2.6.35-25.44-generic 2.6.35.10
  Uname: Linux 2.6.35-25-generic i686
  Architecture: i386
  Date: Thu Feb  3 18:54:28 2011
  ExecutablePath: /usr/bin/evolution
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007)
  ProcEnviron:
   SHELL=/bin/bash
   LANG=en_CA.utf8
  SourcePackage: evolution

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/712829/+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 899878] Re: Software center have hardcoded colors and shows white font on white bg

[Launchpad Bug Tracker]

This bug was fixed in the package software-center - 13.10-0ubuntu4.2

---
software-center (13.10-0ubuntu4.2) trusty; urgency=low

  * debian/patches/07_lp899878.patch
- Added support for Adwaita Dark theme variant to fix LP: #899878
-- Added new softwarecenter.adwaita-dark.css file
-- Added detection for adwaita and dark theme setting
-- Adjusted transparency drawing of stipple by 20%

 -- Bruce Pieterse   Sun, 30 Oct 2016 19:42:26 +0200

** Changed in: software-center (Ubuntu Trusty)
   Status: Fix Committed => Fix Released

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

Title:
  Software center have hardcoded colors and shows white font on white bg

Status in Ubuntu GNOME:
  Fix Released
Status in software-center package in Ubuntu:
  Fix Released
Status in software-center source package in Trusty:
  Fix Released

Bug description:
  [Impact]

   * A user is unable to view the text within the software center
  application which makes the application almost unusable.

   * Ubuntu GNOME users that are currently using a dark theme with an
  LTS release requested that the fix be backported to trusty from wily.

   * This fix applies a custom style sheet for the dark variant of
  Ubuntu GNOME Adwaita theme.

  [Test Case]

   * In Ubuntu GNOME open Gnome Tweak Tool
   * Enable the Global Dark Theme option under Appearances
   * Launch Software Center
   * You will find that text is translucent which is hard to read on the home 
page.
   * Click on any package. The package text is the same color as the background.
   * Apply the fix
   * Open software center and all text is now legible.

  [Regression Potential]

   * None. This fix was applied in Wily.
   * Fix for trusty was tested with both dark and light themes for both Ubuntu 
Gnome and Ubuntu Unity. 
  

  When using dark theme

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: software-center 5.0.2ubuntu0.1
  ProcVersionSignature: Ubuntu 3.0.0-13.22-generic 3.0.6
  Uname: Linux 3.0.0-13-generic i686
  ApportVersion: 1.23-0ubuntu4
  Architecture: i386
  Date: Sun Dec  4 15:28:41 2011
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007)
  PackageArchitecture: all
  ProcEnviron:
   PATH=(custom, user)
   LANG=en_US.UTF-8
   SHELL=/bin/zsh
  SourcePackage: software-center
  UpgradeStatus: Upgraded to oneiric on 2011-10-16 (48 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-gnome/+bug/899878/+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 1640755] Re: backport SNA render backend for gen9

[Launchpad Bug Tracker]

This bug was fixed in the package xserver-xorg-video-intel -
2:2.99.917+git20160325-1ubuntu1.2

---
xserver-xorg-video-intel (2:2.99.917+git20160325-1ubuntu1.2) xenial; 
urgency=medium

  * Backport sna render backend for gen9. (LP: #1640755)

 -- Timo Aaltonen   Thu, 10 Nov 2016 12:31:32 +0200

** Changed in: xserver-xorg-video-intel (Ubuntu Xenial)
   Status: Fix Committed => Fix Released

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

Title:
  backport SNA render backend for gen9

Status in xserver-xorg-video-intel package in Ubuntu:
  Invalid
Status in xserver-xorg-video-intel source package in Xenial:
  Fix Released

Bug description:
  [Impact]
  Hybrid setups with KBL/BXT + AMD need gen9 sna backend backported to fix bugs 
that prevent using the discrete GPU via DRI_PRIME=1 envvar.

  [Test case]

  Run 'DRI_PRIME=1 glxgears'

  [Regression potential]

  Minimal, as the commits mostly touch the new backend, apart from two
  commits that are fixes for other generations too.

  [Other info]

  backported commits are:

  15c5ff12459a034 sna: Clear damage tracking when marking as all-clear
  205146b0fdc8db0 sna/gen9: Fix Kabylake typo
  ebc066c1ece2db2 sna: Add missing GT info for bxt,kbl
  c28e62f94f15c9f sna/gen2+: Do not force migration to GPU for very large 
objects
  81029be07380090 sna/gen8+: Flush pipecontrols when forcing a pipeline stall
  0d38419cbeaae5f sna/gen9: Update mocs selection
  e783ffa4977ae63 sna/gen9: Bias GT for pipeline selection
  4e172a38e170746 sna/gen9: Quick and dirty implementation

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1640755/+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 1640755] Update Released

[Brian Murray]

The verification of the Stable Release Update for xserver-xorg-video-
intel has completed successfully and the package has now been released
to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is
being unsubscribed and will not receive messages about this bug report.
In the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  backport SNA render backend for gen9

Status in xserver-xorg-video-intel package in Ubuntu:
  Invalid
Status in xserver-xorg-video-intel source package in Xenial:
  Fix Released

Bug description:
  [Impact]
  Hybrid setups with KBL/BXT + AMD need gen9 sna backend backported to fix bugs 
that prevent using the discrete GPU via DRI_PRIME=1 envvar.

  [Test case]

  Run 'DRI_PRIME=1 glxgears'

  [Regression potential]

  Minimal, as the commits mostly touch the new backend, apart from two
  commits that are fixes for other generations too.

  [Other info]

  backported commits are:

  15c5ff12459a034 sna: Clear damage tracking when marking as all-clear
  205146b0fdc8db0 sna/gen9: Fix Kabylake typo
  ebc066c1ece2db2 sna: Add missing GT info for bxt,kbl
  c28e62f94f15c9f sna/gen2+: Do not force migration to GPU for very large 
objects
  81029be07380090 sna/gen8+: Flush pipecontrols when forcing a pipeline stall
  0d38419cbeaae5f sna/gen9: Update mocs selection
  e783ffa4977ae63 sna/gen9: Bias GT for pipeline selection
  4e172a38e170746 sna/gen9: Quick and dirty implementation

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1640755/+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 1619142] Re: [MRE] Update to 1.18.4

[Timo Aaltonen]

indeed, pushed a synced version now

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

Title:
  [MRE] Update to 1.18.4

Status in xorg-server package in Ubuntu:
  Invalid
Status in xorg-server-lts-xenial package in Ubuntu:
  Invalid
Status in xorg-server source package in Trusty:
  Invalid
Status in xorg-server-lts-xenial source package in Trusty:
  New
Status in xorg-server source package in Xenial:
  Fix Released
Status in xorg-server-lts-xenial source package in Xenial:
  Invalid

Bug description:
  Update xserver to new minor release 1.18.4 in order to gain bugfixes
  from upstream.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1619142/+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 1643200] Re: After updating to firefox 50.0, tab goes black instead of showing web pages

[Nik Mitev]

Hi,

I had the same issue, and 'ubuntu modifications' did resolve it so
thanks!

A couple of things to add in case they help:

For me the issue was not triggered by the update itself, but by me
disabling an addon I had installed. Removing or reinstalling/reenabling
the addon after that made no difference. What did help (temporarily) was
removing all profiles.

If Firefox could find no saved profiles when it launches, it worked -
until the next restart of course, because then a profile was already saved.
As for your workaround (thanks again), I'll only add it is a
'recommended package' for me, I cannot install it from within Firefox.
Once installed with 'apt-get install xul-ext-ubufox' it appears as an
installed extension and can be disabled (didn't try) from within Firefox.

Regards,
Nik Mitev

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

Title:
  After updating to firefox 50.0, tab goes black instead of showing web
  pages

Status in Mozilla Firefox:
  Confirmed
Status in firefox package in Ubuntu:
  New

Bug description:
  Today, I updated firefox to version 50.0. This update was offered to
  me via the official updates I got for ubuntu 16.04.

  After restarting firefox, I get a black tab content when I "open" a
  web page. For demonstration, see the screen shot attached.

  Note that I still can edit preferences or "about:config". Tabs only go
  black for web pages.

  I get the black tabs after installing firefox together with this set of 
updates:
isc-dhcp-client 4.3.3-5ubuntu12.4
isc-dhcp-common 4.3.3-5ubuntu12.4
libfcitx-config4 1:4.2.9.1-1ubuntu1.16.04.1
libfcitx-gclient0 1:4.2.9.1-1ubuntu1.16.04.1
libfcitx-utils0 1:4.2.9.1-1ubuntu1.16.04.1
libprocps4 2:3.3.10-4ubuntu2.2
linux-firmware 1.157.5
procps 2:3.3.10-4ubuntu2.2
python3-distupgrade 1:16.04.18
ubuntu-release-upgrader-core 1:16.04.18
ubuntu-release-upgrader-gtk 1:16.04.18
unattended-upgrades 0.90ubuntu0.2
xserver-common 2:1.18.4-0ubuntu0.2
xserver-xorg-core 2:1.18.4-0ubuntu0.2

  Please not that xserver got updated, too.

  The behaviour also remains after a reboot.

  Other applications, including Thunderbird, do not show similar
  behaviour.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: firefox 50.0+build2-0ubuntu0.16.04.2
  ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24
  Uname: Linux 4.4.0-47-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  thomas 3212 F pulseaudio
  BuildID: 20161114144739
  Channel: Unavailable
  CurrentDesktop: GNOME-Flashback:Unity
  Date: Sat Nov 19 15:57:33 2016
  Extensions: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  InstallationDate: Installed on 2014-11-29 (721 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  Locales: extensions.sqlite corrupt or missing
  PrefSources: prefs.js
  Profiles: Profile0 (Default) - LastVersion=50.0/20161114144739 (In use)
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  Themes: extensions.sqlite corrupt or missing
  UpgradeStatus: Upgraded to xenial on 2016-06-15 (156 days ago)
  dmi.bios.date: 12/06/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A16
  dmi.board.name: 023HKR
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA16:bd12/06/2013:svnDellInc.:pnLatitudeE5510:pvr0001:rvnDellInc.:rn023HKR:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E5510
  dmi.product.version: 0001
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/firefox/+bug/1643200/+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 1647133] Re: dns=dnsmasq does not work any more

[Steve Langasek]

On Wed, Dec 07, 2016 at 09:34:43PM -, Martin Pitt wrote:
> Ah, so you didn't have resolvconf installed (and therefore also not
> ubuntu-minimal), that's a good data point, thank you! This should be
> part of this bug -- NM should get along with this better.

Removing ubuntu-minimal is always unsupported.

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

Title:
  dns=dnsmasq does not work any more

Status in network-manager package in Ubuntu:
  Triaged

Bug description:
  Network-manager will make my network connection immediately lost after 
updating to the newest version 1.4.2-2ubuntu4.
  However, downgrading to the previous version 1.4.2-2ubuntu3 the network 
connection is back again and fine. If, with this version, I remove the file 
(link) /etc/resolv.conf the network is broken again. Rebooting solves this, as 
network-manager creates a new resolv.conf file.

  The newest version 1.4.2-2ubuntu4 also creates the very same kind of
  file, but no network.

  I have the latest (Gnome-shell DE) updates installed and of course all 
packages that network-manager depends on. But not the ones it only recommends 
or suggests.
  Should I have resolvconf installed? I think not, as isc-dhcp-client only 
suggests it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1647133/+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 1575614] Re: [SRU]Can't select p12 secret key for TLS auth for 802.1X authentication

[Tim Wahrendorff]

The bug still occures within my machine. Wlan can not connect to WPA2
Enterprise. I got lots of "Unencrypted private keys are not secure."-
messages, though my private key is encrypted. Network-manager is version
1.2.2-0ubuntu0.16.04.1.

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

Title:
  [SRU]Can't select p12 secret key for TLS auth for 802.1X
  authentication

Status in NetworkManager:
  Fix Released
Status in network-manager package in Ubuntu:
  Fix Released
Status in network-manager-applet package in Ubuntu:
  Fix Released
Status in network-manager source package in Xenial:
  Fix Released
Status in network-manager-applet source package in Xenial:
  Fix Released

Bug description:
  [Impact]

  Users cannot select TLS certificate when connecting to a network that
  requires TLS type 802.1X authentication

  [Test case]
  STR:
  1. Click on Connections icon in status panel
  2. Click on Edit connections
  3. Select Wired connection
  4. Go to 802.1x tab
  5. Check the Use 802.1X checkbox
  6. Choose TLS
  7. Click on Secret key button
  8. In file chooser navigate to the folder where key is located and try to 
select key file - the list is empty

  For wifi connection:
  1. Click on Connections icon in status panel
  2. Click on Edit connections
  3. Select Wi-Fi connection
  4. Go to Wi-Fi Security tab
  5. Select WPA & WPA2 Enterprise in the drop-down list
  6. Choose TLS
  7. Click on (None) next to Private key
  8. In file chooser navigate to the folder where key is located and try to 
select key file - the list is empty

  [Regression Potential]
  The fix is quite straight forward and the possibility of causing regression 
is limited.

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager/+bug/1575614/+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 1648337] [NEW] There's no way to launch terminal tab under chosen profile

[Konstantin Boyandin]

Public bug reported:

In Ubuntu 14.04, gnome-terminal had menu item, allowing to launch
terminal tab using selected profile (from File menu). Thus one can
quickly organize tabs  as I wish.

In Ubuntu 16.04, latest update, gnome-terminal has lost (among other
features, compared to 14.04) this menu item. I can only open new
terminal with new profile.

This menu item should definitely be restored.

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


** Tags: menu

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

Title:
  There's no way to launch terminal tab under chosen profile

Status in gnome-terminal package in Ubuntu:
  New

Bug description:
  In Ubuntu 14.04, gnome-terminal had menu item, allowing to launch
  terminal tab using selected profile (from File menu). Thus one can
  quickly organize tabs  as I wish.

  In Ubuntu 16.04, latest update, gnome-terminal has lost (among other
  features, compared to 14.04) this menu item. I can only open new
  terminal with new profile.

  This menu item should definitely be restored.

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