date:20180924

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

** This bug has been marked a duplicate of bug 1791542
   package libglvnd-dev 1.0.0-2ubuntu2.1 failed to upgrade: trying to overwrite 
'/usr/lib/x86_64-linux-gnu/libGLESv1_CM.so', which is also in package 
nvidia-340 340.107-0ubuntu0~gpu18.04.1

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

Title:
  package libgles1 (not installed) failed to install/upgrade: trying to
  overwrite '/usr/lib/x86_64-linux-gnu/libGLESv1_CM.so.1', which is also
  in package nvidia-340 340.106-0ubuntu3

Status in libglvnd package in Ubuntu:
  New

Bug description:
  Failure in the update process

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: libgles1 (not installed)
  ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18
  Uname: Linux 4.15.0-34-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  Date: Sun Sep 23 10:38:02 2018
  DuplicateSignature:
   package:libgles1:(not installed)
   Unpacking libglvnd-dev:amd64 (1.0.0-2ubuntu2.2) over (1.0.0-2ubuntu2.1) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-3RAkNn/20-libglvnd-dev_1.0.0-2ubuntu2.2_amd64.deb 
(--unpack):
trying to overwrite '/usr/lib/x86_64-linux-gnu/libGLESv1_CM.so', which is 
also in package nvidia-340 340.106-0ubuntu3
  ErrorMessage: trying to overwrite 
'/usr/lib/x86_64-linux-gnu/libGLESv1_CM.so.1', which is also in package 
nvidia-340 340.106-0ubuntu3
  InstallationDate: Installed on 2016-12-05 (656 days ago)
  InstallationMedia: Lubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.1)
  Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 
3.6.5-3ubuntu1
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.3ubuntu0.1
  SourcePackage: libglvnd
  Title: package libgles1 (not installed) failed to install/upgrade: trying to 
overwrite '/usr/lib/x86_64-linux-gnu/libGLESv1_CM.so.1', which is also in 
package nvidia-340 340.106-0ubuntu3
  UpgradeStatus: Upgraded to bionic on 2018-05-01 (144 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libglvnd/+bug/1793937/+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 1794007] Re: package libglvnd-dev 1.0.0-2ubuntu2.1 failed to install/upgrade: Versuch, »/usr/lib/x86_64-linux-gnu/libGLESv1_CM.so« zu überschreiben, welches auch in Paket nvidi

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

** This bug has been marked a duplicate of bug 1791542
   package libglvnd-dev 1.0.0-2ubuntu2.1 failed to upgrade: trying to overwrite 
'/usr/lib/x86_64-linux-gnu/libGLESv1_CM.so', which is also in package 
nvidia-340 340.107-0ubuntu0~gpu18.04.1

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

Title:
  package libglvnd-dev 1.0.0-2ubuntu2.1 failed to install/upgrade:
  Versuch, »/usr/lib/x86_64-linux-gnu/libGLESv1_CM.so« zu überschreiben,
  welches auch in Paket nvidia-340 340.106-0ubuntu3 ist

Status in libglvnd package in Ubuntu:
  New

Bug description:
  I wanted to install playonlinux and wine in Softwer Manager, but i have 
always error with lib... For example: libglib 2.0-0 and 
usr/lib/x86_64-linux-gnu/libGLESv1.
  I ran in Terminal: sudo apt install upgrade, and I became the massage on 
summary.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: libglvnd-dev 1.0.0-2ubuntu2.1
  ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18
  Uname: Linux 4.15.0-34-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.20.9-0ubuntu7.3
  Architecture: amd64
  Date: Mon Sep 24 05:43:32 2018
  ErrorMessage: Versuch, »/usr/lib/x86_64-linux-gnu/libGLESv1_CM.so« zu 
überschreiben, welches auch in Paket nvidia-340 340.106-0ubuntu3 ist
  InstallationDate: Installed on 2018-09-15 (8 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 
3.6.5-3ubuntu1
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.3ubuntu0.1
  SourcePackage: libglvnd
  Title: package libglvnd-dev 1.0.0-2ubuntu2.1 failed to install/upgrade: 
Versuch, »/usr/lib/x86_64-linux-gnu/libGLESv1_CM.so« zu überschreiben, welches 
auch in Paket nvidia-340 340.106-0ubuntu3 ist
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libglvnd/+bug/1794007/+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 1793853] Re: package libgles1 (not installed) failed to install/upgrade: trying to overwrite '/usr/lib/x86_64-linux-gnu/libGLESv1_CM.so.1', which is also in package nvidia-340

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

** This bug has been marked a duplicate of bug 1791542
   package libglvnd-dev 1.0.0-2ubuntu2.1 failed to upgrade: trying to overwrite 
'/usr/lib/x86_64-linux-gnu/libGLESv1_CM.so', which is also in package 
nvidia-340 340.107-0ubuntu0~gpu18.04.1

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

Title:
  package libgles1 (not installed) failed to install/upgrade: trying to
  overwrite '/usr/lib/x86_64-linux-gnu/libGLESv1_CM.so.1', which is also
  in package nvidia-340 340.106-0ubuntu3

Status in libglvnd package in Ubuntu:
  Confirmed

Bug description:
  Error

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: libgles1 (not installed)
  ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18
  Uname: Linux 4.15.0-34-generic x86_64
  NonfreeKernelModules: nvidia wl
  ApportVersion: 2.20.9-0ubuntu7.3
  Architecture: amd64
  Date: Sat Sep 22 18:10:09 2018
  DuplicateSignature:
   package:libgles1:(not installed)
   Unpacking libglvnd-dev:amd64 (1.0.0-2ubuntu2.2) over (1.0.0-2ubuntu2.1) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-AY1GH7/05-libglvnd-dev_1.0.0-2ubuntu2.2_amd64.deb 
(--unpack):
trying to overwrite '/usr/lib/x86_64-linux-gnu/libGLESv1_CM.so', which is 
also in package nvidia-340 340.106-0ubuntu3
  ErrorMessage: trying to overwrite 
'/usr/lib/x86_64-linux-gnu/libGLESv1_CM.so.1', which is also in package 
nvidia-340 340.106-0ubuntu3
  InstallationDate: Installed on 2018-06-30 (84 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 
3.6.5-3ubuntu1
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.3ubuntu0.1
  SourcePackage: libglvnd
  Title: package libgles1 (not installed) failed to install/upgrade: trying to 
overwrite '/usr/lib/x86_64-linux-gnu/libGLESv1_CM.so.1', which is also in 
package nvidia-340 340.106-0ubuntu3
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libglvnd/+bug/1793853/+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 1793942] Re: package libglvnd-dev 1.0.0-2ubuntu2.1 failed to install as ububtu 2.2 is installed

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

** This bug has been marked a duplicate of bug 1791542
   package libglvnd-dev 1.0.0-2ubuntu2.1 failed to upgrade: trying to overwrite 
'/usr/lib/x86_64-linux-gnu/libGLESv1_CM.so', which is also in package 
nvidia-340 340.107-0ubuntu0~gpu18.04.1

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

Title:
  package libglvnd-dev 1.0.0-2ubuntu2.1 failed to install as ububtu 2.2
  is installed

Status in libglvnd package in Ubuntu:
  Confirmed

Bug description:
  De afhankelijkheden van de volgende pakketten konden niet
  geïnstalleerd worden:

  libglvnd-dev: Depends: libglvnd0 (= 1.0.0-2ubuntu2.1) maar 1.0.0-2ubuntu2.2 
is geïnstalleerd
Depends: libglvnd-core-dev (= 1.0.0-2ubuntu2.1) maar 
1.0.0-2ubuntu2.2 is geïnstalleerd
Depends: libegl1 (= 1.0.0-2ubuntu2.1) maar 1.0.0-2ubuntu2.2 is 
geïnstalleerd
Depends: libgles2 (= 1.0.0-2ubuntu2.1) maar 1.0.0-2ubuntu2.2 is 
geïnstalleerd
Depends: libgl1 (= 1.0.0-2ubuntu2.1) maar 1.0.0-2ubuntu2.2 is 
geïnstalleerd
Depends: libglx0 (= 1.0.0-2ubuntu2.1) maar 1.0.0-2ubuntu2.2 is 
geïnstalleerd
Depends: libopengl0 (= 1.0.0-2ubuntu2.1) maar 1.0.0-2ubuntu2.2 
is geïnstalleerd

  dependent libxxx = ubuntu 2.1, installed 2.2

  Ubuntu 18.04.1 LTS
  GNOME 3.28.2

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: libglvnd-dev 1.0.0-2ubuntu2.1
  ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18
  Uname: Linux 4.15.0-34-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  Date: Sun Sep 23 09:55:27 2018
  DuplicateSignature:
   package:libglvnd-dev:1.0.0-2ubuntu2.1
   Unpacking libglvnd-dev:amd64 (1.0.0-2ubuntu2.2) over (1.0.0-2ubuntu2.1) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-SbaXU4/07-libglvnd-dev_1.0.0-2ubuntu2.2_amd64.deb 
(--unpack):
trying to overwrite '/usr/lib/x86_64-linux-gnu/libGLESv1_CM.so', which is 
also in package nvidia-340 340.106-0ubuntu3
  ErrorMessage: trying to overwrite 
'/usr/lib/x86_64-linux-gnu/libGLESv1_CM.so', which is also in package 
nvidia-340 340.106-0ubuntu3
  InstallationDate: Installed on 2018-01-29 (236 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 
3.6.5-3ubuntu1
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.3ubuntu0.1
  SourcePackage: libglvnd
  Title: package libglvnd-dev 1.0.0-2ubuntu2.1 failed to install/upgrade: 
trying to overwrite '/usr/lib/x86_64-linux-gnu/libGLESv1_CM.so', which is also 
in package nvidia-340 340.106-0ubuntu3
  UpgradeStatus: Upgraded to bionic on 2018-05-16 (129 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libglvnd/+bug/1793942/+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 1793689] Re: package libgles1 (not installed) failed to install/upgrade: intentando sobreescribir `/usr/lib/x86_64-linux-gnu/libGLESv1_CM.so.1', que está también en el paquete

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

** This bug has been marked a duplicate of bug 1791542
   package libglvnd-dev 1.0.0-2ubuntu2.1 failed to upgrade: trying to overwrite 
'/usr/lib/x86_64-linux-gnu/libGLESv1_CM.so', which is also in package 
nvidia-340 340.107-0ubuntu0~gpu18.04.1

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

Title:
  package libgles1 (not installed) failed to install/upgrade: intentando
  sobreescribir `/usr/lib/x86_64-linux-gnu/libGLESv1_CM.so.1', que está
  también en el paquete nvidia-340 340.106-0ubuntu3

Status in libglvnd package in Ubuntu:
  Confirmed

Bug description:
  Messages shown when I execute apt upgrade

  (Leyendo la base de datos ... 603320 ficheros o directorios instalados 
actualmente.)
  Preparando para desempaquetar .../libglvnd-dev_1.0.0-2ubuntu2.2_amd64.deb ...
  Desempaquetando libglvnd-dev:amd64 (1.0.0-2ubuntu2.2) sobre 
(1.0.0-2ubuntu2.1) ...
  dpkg: error al procesar el archivo 
/var/cache/apt/archives/libglvnd-dev_1.0.0-2ubuntu2.2_amd64.deb (--unpack):
   intentando sobreescribir `/usr/lib/x86_64-linux-gnu/libGLESv1_CM.so', que 
está también en el paquete nvidia-340 340.106-0ubuntu3
  Preparando para desempaquetar .../libgles1_1.0.0-2ubuntu2.2_amd64.deb ...
  Desempaquetando libgles1:amd64 (1.0.0-2ubuntu2.2) ...
  dpkg: error al procesar el archivo 
/var/cache/apt/archives/libgles1_1.0.0-2ubuntu2.2_amd64.deb (--unpack):
   intentando sobreescribir `/usr/lib/x86_64-linux-gnu/libGLESv1_CM.so.1', que 
está también en el paquete nvidia-340 340.106-0ubuntu3
  Se encontraron errores al procesar:
   /var/cache/apt/archives/libglvnd-dev_1.0.0-2ubuntu2.2_amd64.deb
   /var/cache/apt/archives/libgles1_1.0.0-2ubuntu2.2_amd64.deb
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: libgles1 (not installed)
  ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18
  Uname: Linux 4.15.0-34-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.20.9-0ubuntu7.3
  Architecture: amd64
  Date: Fri Sep 21 10:53:18 2018
  ErrorMessage: intentando sobreescribir 
`/usr/lib/x86_64-linux-gnu/libGLESv1_CM.so.1', que está también en el paquete 
nvidia-340 340.106-0ubuntu3
  InstallationDate: Installed on 2018-04-27 (146 days ago)
  InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 
(20180228)
  Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 
3.6.5-3ubuntu1
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.3ubuntu0.1
  SourcePackage: libglvnd
  Title: package libgles1 (not installed) failed to install/upgrade: intentando 
sobreescribir `/usr/lib/x86_64-linux-gnu/libGLESv1_CM.so.1', que está también 
en el paquete nvidia-340 340.106-0ubuntu3
  UpgradeStatus: Upgraded to bionic on 2018-09-17 (3 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libglvnd/+bug/1793689/+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 1793818] Re: package libglvnd-dev 1.0.0-2ubuntu2.1 failed to install/upgrade: trying to overwrite '/usr/lib/i386-linux-gnu/libGLESv1_CM.so', which is also in package nvidia-340

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

** This bug has been marked a duplicate of bug 1791542
   package libglvnd-dev 1.0.0-2ubuntu2.1 failed to upgrade: trying to overwrite 
'/usr/lib/x86_64-linux-gnu/libGLESv1_CM.so', which is also in package 
nvidia-340 340.107-0ubuntu0~gpu18.04.1

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

Title:
  package libglvnd-dev 1.0.0-2ubuntu2.1 failed to install/upgrade:
  trying to overwrite '/usr/lib/i386-linux-gnu/libGLESv1_CM.so', which
  is also in package nvidia-340 340.106-0ubuntu3

Status in libglvnd package in Ubuntu:
  Confirmed

Bug description:
  Error occurred during software update installing new packages

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: libglvnd-dev 1.0.0-2ubuntu2.1
  ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18
  Uname: Linux 4.15.0-34-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: i386
  Date: Fri Sep 21 13:39:17 2018
  DpkgTerminalLog:
   Preparing to unpack .../0-libglvnd-dev_1.0.0-2ubuntu2.2_i386.deb ...
   Unpacking libglvnd-dev:i386 (1.0.0-2ubuntu2.2) over (1.0.0-2ubuntu2.1) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-28PzbF/0-libglvnd-dev_1.0.0-2ubuntu2.2_i386.deb 
(--unpack):
trying to overwrite '/usr/lib/i386-linux-gnu/libGLESv1_CM.so', which is 
also in package nvidia-340 340.106-0ubuntu3
  DuplicateSignature:
   package:libglvnd-dev:1.0.0-2ubuntu2.1
   Unpacking libglvnd-dev:i386 (1.0.0-2ubuntu2.2) over (1.0.0-2ubuntu2.1) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-28PzbF/0-libglvnd-dev_1.0.0-2ubuntu2.2_i386.deb 
(--unpack):
trying to overwrite '/usr/lib/i386-linux-gnu/libGLESv1_CM.so', which is 
also in package nvidia-340 340.106-0ubuntu3
  ErrorMessage: trying to overwrite '/usr/lib/i386-linux-gnu/libGLESv1_CM.so', 
which is also in package nvidia-340 340.106-0ubuntu3
  InstallationDate: Installed on 2016-06-12 (831 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 
(20120423)
  Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 
3.6.5-3ubuntu1
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.3ubuntu0.1
  SourcePackage: libglvnd
  Title: package libglvnd-dev 1.0.0-2ubuntu2.1 failed to install/upgrade: 
trying to overwrite '/usr/lib/i386-linux-gnu/libGLESv1_CM.so', which is also in 
package nvidia-340 340.106-0ubuntu3
  UpgradeStatus: Upgraded to bionic on 2018-08-30 (21 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libglvnd/+bug/1793818/+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 1794018] Re: graphics problem

you're using the HWE stack, try x-x-v-intel-hwe-16.04 instead

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

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

Title:
  graphics problem

Status in xorg package in Ubuntu:
  Invalid

Bug description:
  when I type this
sudo apt-get install xserver-xorg-video-intel
  It's showing below results

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

  The following packages have unmet dependencies:
   xserver-xorg-video-intel : Depends: xorg-video-abi-20
  Depends: xserver-xorg-core (>= 2:1.17.99.902)
  E: Unable to correct problems, you have held broken packages.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3.1
  ProcVersionSignature: Ubuntu 4.15.0-34.37~16.04.1-generic 4.15.18
  Uname: Linux 4.15.0-34-generic x86_64
  NonfreeKernelModules: wl
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  BootLog:
   
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Mon Sep 24 11:53:44 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   bcmwl, 6.30.223.271+bdcom, 4.13.0-36-generic, x86_64: installed
   bcmwl, 6.30.223.271+bdcom, 4.15.0-34-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation Device [8086:5917] (rev 07) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Device [103c:832a]
  InstallationDate: Installed on 2018-02-07 (228 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0408:5180 Quanta Computer, Inc. 
   Bus 001 Device 002: ID 0bda:b009 Realtek Semiconductor Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP Laptop 15-bs1xx
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-34-generic 
root=UUID=7dedbb81-ba0d-434b-a5b4-8d89a4e31a00 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/23/2017
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.32
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 832A
  dmi.board.vendor: HP
  dmi.board.version: 23.46
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.32:bd11/23/2017:svnHP:pnHPLaptop15-bs1xx:pvrType1ProductConfigId:rvnHP:rn832A:rvr23.46:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Notebook
  dmi.product.name: HP Laptop 15-bs1xx
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP
  version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.91-2~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Mon Sep 24 11:07:41 2018
  xserver.configfile: default
  xserver.devices:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.19.6-1ubuntu4~16.04.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1794018/+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 1793837] Re: xorg gives low resolution on HDMI port

You probably need to file it upstream at bugs.freedesktop.org (DRI;
DRM/Intel)

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

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

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

Title:
  xorg gives low resolution on HDMI port

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This is a Zotac CI547 box. It has to video outputs: one HDMI and one
  DisplayPort. The HDMI port appears as DP-1 in the logs, the
  DisplayPort as DP-2. The hardware is Intel HD 620 and is allegedly
  able to run two displays simultaneously at 4K. I have one WQHD monitor
  (=2560x1440) and I get that full resolution over the DisplayPort.
  However, I would like to also get that resolution over the HDMI port
  (in order to connect two identical monitors), but over HDMI I only get
  1024x768. Updating the kernel to the latest 4.18.8 using UKUU made no
  difference.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  Uname: Linux 4.18.8-041808-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.3
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: X-Cinnamon
  Date: Sat Sep 22 00:21:15 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA 
controller])
 Subsystem: Intel Corporation HD Graphics 620 [8086:]
  InstallationDate: Installed on 2018-09-19 (2 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: ZOTAC ZBOX-CI527/CI547
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.8-041808-generic 
root=UUID=a3c0f54d-b5ae-4a0f-89ec-8e47ad34e2ef ro quiet splash 
acpi_backlight=native pci=nomsi 
resume=UUID=a3c0f54d-b5ae-4a0f-89ec-8e47ad34e2ef resume_offset=34816 
vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/25/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: B331P206
  dmi.board.asset.tag: NA
  dmi.board.name: ZBOX-CI527/CI547
  dmi.board.vendor: ZOTAC
  dmi.board.version: XX
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 9
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrB331P206:bd04/25/2017:svnZOTAC:pnZBOX-CI527/CI547:pvrXX:rvnZOTAC:rnZBOX-CI527/CI547:rvrXX:cvnDefaultstring:ct9:cvrDefaultstring:
  dmi.product.family: NA
  dmi.product.name: ZBOX-CI527/CI547
  dmi.product.sku: NA
  dmi.product.version: XX
  dmi.sys.vendor: ZOTAC
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1793837/+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 1605811] Re: x11 crashes

try 18.04 or newer, if you have issues file a new bug with 'ubuntu-bug
xorg'

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

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

Title:
  x11 crashes

Status in xorg package in Ubuntu:
  Invalid

Bug description:
  somehow during update or something we have like very unstable x11
  pulled in. also affects stretch upstream.

  the desire is for the video driver, open or else.ABOVE jessie or
  15.10. Well I had the else(force freeze x117), a kernel update to 4.6
  broke it, so I went open. hassle but not a big deal. Obviously this
  means reinstalling x118. Ok. -or so I thought.

  x118 with kernel 4.6 somehow breaks all of the x11 depends, so NO
  driver will load and x11 complains its (now bleeding) head off, and
  wont load. If it loads at all, im impressed.

  vesa-fail
  fbdev-fail
  ati-fail
  radeon-fail

  and a few other drivers --all depends of radeon ati...

  Its not ramdom gibberish to me but what it entails is that X11 CANT
  load as the video driver is broken at every depends level for the ati
  driver at least, mayhaps the entire x11 video driver subsystem.Its
  looks to someone like something didnt get linked correctly. Those
  sorts of errors.

  xyz missing from yada yada...

  X11 cant load...but CANT is never in programmer vocabulary..

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1605811/+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 1759158] Re: Improve Thunderbird notifications for Gnome Shell

2018-09-24 Thread MF

I also experience issue 2. (on bionic) of this bug: even though messages
are read and correctly marked as read in Thunderbird window, the red
notification on Thunderbird dock icon is not updated.

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

Title:
  Improve Thunderbird notifications for Gnome Shell

Status in thunderbird package in Ubuntu:
  New

Bug description:
  As Gnome Shell notification subsystem have more features than
  notifications in Unity, integration needs to be improved.

  Currently, in artful and bionic, Thunderbird notifications have two
  issues:

  1. On lock screen, Thunderbird always show "1 new notification" even
  multiple mails arrived while screen locked.

  2. Thunderbird should withdrawal notifications, if message was viewed
  and marked as read on another device (for IMAP only).

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: thunderbird 1:52.6.0+build1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-12-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.9-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  eugene 3929 F pulseaudio
  BuildID: 20180131200234
  Channel: Unavailable
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Mar 27 10:55:59 2018
  ForcedLayersAccel: False
  IfupdownConfig:
   auto lo
   iface lo inet loopback
  IncompatibleExtensions:
   English (GB) Language Pack - langpack-en...@thunderbird.mozilla.org
   Thunderbird (default) - {972ce4c6-7e08-4474-a285-3208198ce6fd}
  IwConfig:
   vboxnet0  no wireless extensions.
   
   enp5s0no wireless extensions.
   
   lono wireless extensions.
  MostRecentCrashID: bp-63008d16-a2d5-46b1-b9d2-3f3ef0180321
  Plugins: Shockwave Flash - /usr/lib/adobe-flashplugin/libflashplayer.so 
(adobe-flashplugin)
  PrefSources: prefs.js
  Profiles: Profile0 (Default) - LastVersion=52.6.0/20180131200234 (In use)
  RelatedPackageVersions: adobe-flashplugin 1:20180313.1-0ubuntu1
  RfKill:
   
  RunningIncompatibleAddons: True
  SourcePackage: thunderbird
  SubmittedCrashIDs: bp-63008d16-a2d5-46b1-b9d2-3f3ef0180321
  UpgradeStatus: Upgraded to bionic on 2017-10-24 (153 days ago)
  dmi.bios.date: 09/20/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2003
  dmi.board.asset.tag: Default string
  dmi.board.name: Z170-K
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2003:bd09/20/2016:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ170-K:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1759158/+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 1794033] [NEW] i965: Failed to submit batchbuffer: Bad address

2018-09-24 Thread themusicgod1

Public bug reported:

cpu: Intel® Core™ i5-7500 CPU @ 3.40GHz × 4 
gpu: Intel® HD Graphics 630 (Kaby Lake GT2)
00:00.0 Host bridge: Intel Corporation Intel Kaby Lake Host Bridge (rev 05)
00:02.0 VGA compatible controller: Intel Corporation HD Graphics 630 (rev 04)
00:08.0 System peripheral: Intel Corporation Skylake Gaussian Mixture Model
xserver-xorg-video-intel:
  Installed: 2:2.99.917+git20171229-1
  Candidate: 2:2.99.917+git20171229-1
ubuntu: 18.04 LTS bionic
gnome: 3.28.2
gdm3:
  Installed: 3.28.2-0ubuntu1.4
  Candidate: 3.28.2-0ubuntu1.4
os type: 64 bit
kernel: Linux eva1 4.15.0-30-generic #32-Ubuntu SMP Thu Jul 26 17:42:43 UTC 
2018 x86_64 x86_64 x86_64 GNU/Linux
mesa-va-drivers:
  Installed: 18.0.5-0ubuntu0~18.04.1
  Candidate: 18.0.5-0ubuntu0~18.04.1

from syslog:

Sep 24 04:08:16 eva /usr/lib/gdm3/gdm-x-session[1170]: i965: Failed to submit 
batchbuffer: Bad address
Sep 24 04:08:21 eva gnome-terminal-[2597]: gnome-terminal-server: Fatal IO 
error 11 (Resource temporarily unavailable) on X server :0.
Sep 24 04:08:22 eva [2541]: update-notifier: Fatal IO error 11 (Resource 
temporarily unavailable) on X server :0.
Sep 24 04:08:22 eva at-spi-bus-launcher[1274]: XIO:  fatal IO error 11 
(Resource temporarily unavailable) on X server ":0" 
 - but 
(followed by pages upon pages of applications within gnome failing.)

nothing in kern.log around that time.

Singular gnome crash, taking down all applications running within it.
Not yet reproduced. gdm successfully started a new session afterwards.
Was definitely in a palermoon session on some website or other.

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

** Affects: xserver-xorg-video-intel (Fedora)
 Importance: Unknown
 Status: Unknown

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

** Also affects: xserver-xorg-video-intel (Fedora) via
   https://bugs.freedesktop.org/show_bug.cgi?id=104778
   Importance: Unknown
   Status: Unknown

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

Title:
   i965: Failed to submit batchbuffer: Bad address

Status in xserver-xorg-video-intel package in Ubuntu:
  New
Status in xserver-xorg-video-intel package in Fedora:
  Unknown

Bug description:
  cpu: Intel® Core™ i5-7500 CPU @ 3.40GHz × 4 
  gpu: Intel® HD Graphics 630 (Kaby Lake GT2)
  00:00.0 Host bridge: Intel Corporation Intel Kaby Lake Host Bridge (rev 05)
  00:02.0 VGA compatible controller: Intel Corporation HD Graphics 630 (rev 04)
  00:08.0 System peripheral: Intel Corporation Skylake Gaussian Mixture Model
  xserver-xorg-video-intel:
Installed: 2:2.99.917+git20171229-1
Candidate: 2:2.99.917+git20171229-1
  ubuntu: 18.04 LTS bionic
  gnome: 3.28.2
  gdm3:
Installed: 3.28.2-0ubuntu1.4
Candidate: 3.28.2-0ubuntu1.4
  os type: 64 bit
  kernel: Linux eva1 4.15.0-30-generic #32-Ubuntu SMP Thu Jul 26 17:42:43 UTC 
2018 x86_64 x86_64 x86_64 GNU/Linux
  mesa-va-drivers:
Installed: 18.0.5-0ubuntu0~18.04.1
Candidate: 18.0.5-0ubuntu0~18.04.1

  from syslog:

  Sep 24 04:08:16 eva /usr/lib/gdm3/gdm-x-session[1170]: i965: Failed to submit 
batchbuffer: Bad address
  Sep 24 04:08:21 eva gnome-terminal-[2597]: gnome-terminal-server: Fatal IO 
error 11 (Resource temporarily unavailable) on X server :0.
  Sep 24 04:08:22 eva [2541]: update-notifier: Fatal IO error 11 (Resource 
temporarily unavailable) on X server :0.
  Sep 24 04:08:22 eva at-spi-bus-launcher[1274]: XIO:  fatal IO error 11 
(Resource temporarily unavailable) on X server ":0" 
   - but 
  (followed by pages upon pages of applications within gnome failing.)

  nothing in kern.log around that time.

  Singular gnome crash, taking down all applications running within it.
  Not yet reproduced. gdm successfully started a new session afterwards.
  Was definitely in a palermoon session on some website or other.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1794033/+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 1786265] Re: [SRU] Update to 0.4

This bug was fixed in the package bolt - 0.4-0ubuntu0.18.04.1

---
bolt (0.4-0ubuntu0.18.04.1) bionic; urgency=medium

  * New upstream version (lp: #1786265)
- should resolve issues with devices not being authorized on initial
  boot e.g in lightdm (lp: #1778020)

 -- Sebastien Bacher   Thu, 09 Aug 2018 16:20:08
+0200

** Changed in: bolt (Ubuntu Bionic)
   Status: Fix Committed => Fix Released

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

Title:
  [SRU] Update to 0.4

Status in bolt package in Ubuntu:
  Fix Released
Status in bolt source package in Bionic:
  Fix Released

Bug description:
  * Impact

  That's a new component and a piece of hardware enablement. The update
  is having dbus API changes and is not a bugfix only version, but we
  believe it's better to follow improvements in that new stack than stay
  on an early version which is incomplete and unmaintained.

  The service has no rdepends out of gnome-shell which already works
  fine with the new version

  The summary of the changes can be found there
  https://gitlab.freedesktop.org/bolt/bolt/tags/0.4

  * Test case
  - log into an Ubuntu session
  - connect a new Thunderbolt device
  - check that gnome-shell displays the request for authentication for the 
device and that the authentication can be validated/the device can be used

  * Regression potential

  There are quite some code changes but bolt is limited to
  authentication of Thunderbolt devices, we need to test that the
  boltctl command line and the GNOME integration keep working to
  auth/revoke devices.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bolt/+bug/1786265/+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 1785679] Re: [SRU] libreoffice 6.0.6 for bionic

This bug was fixed in the package libreoffice-l10n -
1:6.0.6-0ubuntu0.18.04.1

---
libreoffice-l10n (1:6.0.6-0ubuntu0.18.04.1) bionic; urgency=medium

  * New upstream release (LP: #1785679)

 -- Olivier Tilloy   Thu, 30 Aug 2018
11:49:15 +0200

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

Title:
  [SRU] libreoffice 6.0.6 for bionic

Status in libreoffice package in Ubuntu:
  Fix Released
Status in libreoffice-l10n package in Ubuntu:
  New
Status in libreoffice source package in Bionic:
  Fix Released
Status in libreoffice-l10n source package in Bionic:
  Fix Released

Bug description:
  [Impact]

   * LibreOffice 6.0.6 is the sixth bugfix release of the fresh 6.0 line. 
Version 6.0.3 is currently in bionic.
 For a list of fixed bugs compared to 6.0.3 see the list of bugs fixed in 
6.0.4, 6.0.5 and 6.0.6:
   https://wiki.documentfoundation.org/Releases/6.0.4/RC1#List_of_fixed_bugs
   https://wiki.documentfoundation.org/Releases/6.0.4/RC2#List_of_fixed_bugs
   https://wiki.documentfoundation.org/Releases/6.0.5/RC1#List_of_fixed_bugs
   https://wiki.documentfoundation.org/Releases/6.0.5/RC2#List_of_fixed_bugs
   https://wiki.documentfoundation.org/Releases/6.0.6/RC1#List_of_fixed_bugs
   https://wiki.documentfoundation.org/Releases/6.0.6/RC2#List_of_fixed_bugs
 (that's a total of 239 bugs)

   * Given the nature of the project, the complexity of the codebase and
  the high level of quality assurance upstream, it is preferable to SRU
  a minor release rather than cherry-pick selected bug fixes.

  [Test Case]

   * No specific test case, bugs fixed upstream hopefully come with
  unit/regression tests, and the release itself is extensively exercised
  upstream (both in an automated manner and manually) by a community of
  testers. Each minor release goes through two release candidates.

   * The libreoffice packages include autopkgtests, those should be run
  and verified to pass.

   * General smoke testing of all the applications in the office suite
  should be carried out.

  [Regression Potential]

   * A series of three minor releases with a total of 239 bug fixes
  always carries the potential for introducing regressions, even though
  they are bugfix-only releases, meaning that no new features were
  added, and no existing features were removed.

   * A combination of autopkgtests and careful smoke testing as
  described above should provide reasonable confidence that no
  regressions sneaked in.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1785679/+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 1792894] Re: Update to 6.1.1

This bug was fixed in the package libreoffice - 1:6.1.1-0ubuntu1

---
libreoffice (1:6.1.1-0ubuntu1) cosmic; urgency=medium

  * New upstream release (LP: #1792894)

 -- Olivier Tilloy   Thu, 20 Sep 2018
14:11:57 +0200

** Changed in: libreoffice (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  Update to 6.1.1

Status in libreoffice package in Ubuntu:
  Fix Released

Bug description:
  The update is targetted for cosmic, Olivier is working on it

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1792894/+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 1785679] Update Released

The verification of the Stable Release Update for libreoffice 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 libreoffice in Ubuntu.
https://bugs.launchpad.net/bugs/1785679

Title:
  [SRU] libreoffice 6.0.6 for bionic

Status in libreoffice package in Ubuntu:
  Fix Released
Status in libreoffice-l10n package in Ubuntu:
  New
Status in libreoffice source package in Bionic:
  Fix Released
Status in libreoffice-l10n source package in Bionic:
  Fix Released

Bug description:
  [Impact]

   * LibreOffice 6.0.6 is the sixth bugfix release of the fresh 6.0 line. 
Version 6.0.3 is currently in bionic.
 For a list of fixed bugs compared to 6.0.3 see the list of bugs fixed in 
6.0.4, 6.0.5 and 6.0.6:
   https://wiki.documentfoundation.org/Releases/6.0.4/RC1#List_of_fixed_bugs
   https://wiki.documentfoundation.org/Releases/6.0.4/RC2#List_of_fixed_bugs
   https://wiki.documentfoundation.org/Releases/6.0.5/RC1#List_of_fixed_bugs
   https://wiki.documentfoundation.org/Releases/6.0.5/RC2#List_of_fixed_bugs
   https://wiki.documentfoundation.org/Releases/6.0.6/RC1#List_of_fixed_bugs
   https://wiki.documentfoundation.org/Releases/6.0.6/RC2#List_of_fixed_bugs
 (that's a total of 239 bugs)

   * Given the nature of the project, the complexity of the codebase and
  the high level of quality assurance upstream, it is preferable to SRU
  a minor release rather than cherry-pick selected bug fixes.

  [Test Case]

   * No specific test case, bugs fixed upstream hopefully come with
  unit/regression tests, and the release itself is extensively exercised
  upstream (both in an automated manner and manually) by a community of
  testers. Each minor release goes through two release candidates.

   * The libreoffice packages include autopkgtests, those should be run
  and verified to pass.

   * General smoke testing of all the applications in the office suite
  should be carried out.

  [Regression Potential]

   * A series of three minor releases with a total of 239 bug fixes
  always carries the potential for introducing regressions, even though
  they are bugfix-only releases, meaning that no new features were
  added, and no existing features were removed.

   * A combination of autopkgtests and careful smoke testing as
  described above should provide reasonable confidence that no
  regressions sneaked in.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1785679/+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 1785679] Re: [SRU] libreoffice 6.0.6 for bionic

This bug was fixed in the package libreoffice - 1:6.0.6-0ubuntu0.18.04.1

---
libreoffice (1:6.0.6-0ubuntu0.18.04.1) bionic; urgency=medium

  * New upstream release (LP: #1785679)

 -- Olivier Tilloy   Thu, 30 Aug 2018
11:49:15 +0200

** Changed in: libreoffice (Ubuntu Bionic)
   Status: Fix Committed => Fix Released

** Changed in: libreoffice-l10n (Ubuntu Bionic)
   Status: Fix Committed => Fix Released

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

Title:
  [SRU] libreoffice 6.0.6 for bionic

Status in libreoffice package in Ubuntu:
  Fix Released
Status in libreoffice-l10n package in Ubuntu:
  New
Status in libreoffice source package in Bionic:
  Fix Released
Status in libreoffice-l10n source package in Bionic:
  Fix Released

Bug description:
  [Impact]

   * LibreOffice 6.0.6 is the sixth bugfix release of the fresh 6.0 line. 
Version 6.0.3 is currently in bionic.
 For a list of fixed bugs compared to 6.0.3 see the list of bugs fixed in 
6.0.4, 6.0.5 and 6.0.6:
   https://wiki.documentfoundation.org/Releases/6.0.4/RC1#List_of_fixed_bugs
   https://wiki.documentfoundation.org/Releases/6.0.4/RC2#List_of_fixed_bugs
   https://wiki.documentfoundation.org/Releases/6.0.5/RC1#List_of_fixed_bugs
   https://wiki.documentfoundation.org/Releases/6.0.5/RC2#List_of_fixed_bugs
   https://wiki.documentfoundation.org/Releases/6.0.6/RC1#List_of_fixed_bugs
   https://wiki.documentfoundation.org/Releases/6.0.6/RC2#List_of_fixed_bugs
 (that's a total of 239 bugs)

   * Given the nature of the project, the complexity of the codebase and
  the high level of quality assurance upstream, it is preferable to SRU
  a minor release rather than cherry-pick selected bug fixes.

  [Test Case]

   * No specific test case, bugs fixed upstream hopefully come with
  unit/regression tests, and the release itself is extensively exercised
  upstream (both in an automated manner and manually) by a community of
  testers. Each minor release goes through two release candidates.

   * The libreoffice packages include autopkgtests, those should be run
  and verified to pass.

   * General smoke testing of all the applications in the office suite
  should be carried out.

  [Regression Potential]

   * A series of three minor releases with a total of 239 bug fixes
  always carries the potential for introducing regressions, even though
  they are bugfix-only releases, meaning that no new features were
  added, and no existing features were removed.

   * A combination of autopkgtests and careful smoke testing as
  described above should provide reasonable confidence that no
  regressions sneaked in.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1785679/+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 1778020] Re: devices not authorized at lightdm on initial boot even if enrolled

This bug was fixed in the package bolt - 0.4-0ubuntu0.18.04.1

---
bolt (0.4-0ubuntu0.18.04.1) bionic; urgency=medium

  * New upstream version (lp: #1786265)
- should resolve issues with devices not being authorized on initial
  boot e.g in lightdm (lp: #1778020)

 -- Sebastien Bacher   Thu, 09 Aug 2018 16:20:08
+0200

** Changed in: bolt (Ubuntu Bionic)
   Status: Fix Committed => Fix Released

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

Title:
  devices not authorized at lightdm on initial boot even if enrolled

Status in bolt package in Ubuntu:
  Fix Released
Status in bolt source package in Bionic:
  Fix Released
Status in bolt package in Fedora:
  Unknown

Bug description:
  * Impact

  some devices can't be used on the login screen

  * Test case
  try using a mouse/keyboard connected to a thunderbolt dock, they should work 
on the login scren

  * Regression potential
  check that your thunderbolt devices keep working fine on the login screen and 
during the user session

  

  eg I can't use my keyboard to login, until I've logged in at least
  once.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: bolt 0.2-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jun 21 10:30:26 2018
  InstallationDate: Installed on 2018-05-30 (21 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  SourcePackage: bolt
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bolt/+bug/1778020/+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 1735529] Re: Firefox incorrectly blacklists system for WebGL

Thomas, can you share details of your graphics card and driver in use?

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

Title:
  Firefox incorrectly blacklists system for WebGL

Status in firefox package in Ubuntu:
  Invalid

Bug description:
  This is with Ubuntu 16.04.

  Using the Ubuntu-provided Firefox 57.0, if I go to
  https://get.webgl.org/ I get the message:

  "Hmm. While your browser seems to support WebGL, it is disabled or
  unavailable. If possible, please ensure that you are running the
  latest drivers for your video card."

  In the JavaScript developer console there are some messages,
  including:

  "Error: WebGL warning: Failed to create WebGL context: WebGL creation failed: 
  * Refused to create native OpenGL context because of blacklist entry: 
FEATURE_FAILURE_OPENGL_1
  * Exhausted GL driver options."

  There are similar messages for WebGL in about:support.

  However if I download Firefox 57.0 from
  https://ftp.mozilla.org/pub/firefox/releases/57.0/linux-x86_64/en-
  US/firefox-57.0.tar.bz2 and use that to go to https://get.webgl.org/ ,
  I get the message "Your browser supports WebGL".

  So it looks like Ubuntu-provided Firefox has a problem while Mozilla-
  provided Firefox doesn't. (FYI, I reported a similar problem in
  https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1724705 , where
  DRM-protected content doesn't work with Ubuntu-provided Firefox but
  does work with Mozilla-provided Firefox.)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1735529/+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 1748895] Re: LO unable to find a working email configuration

Re-opening per user comment and upstream report.

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

** Bug watch added: Document Foundation Bugzilla #116211
   https://bugs.documentfoundation.org/show_bug.cgi?id=116211

** Also affects: df-libreoffice via
   https://bugs.documentfoundation.org/show_bug.cgi?id=116211
   Importance: Unknown
   Status: Unknown

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

Title:
  LO unable to find a working email configuration

Status in LibreOffice:
  Unknown
Status in libreoffice package in Ubuntu:
  Confirmed

Bug description:
  Installed from PPA: ppa:libreoffice/ppa

  $ lsb_release -a
  LSB Version:  
core-9.20160110ubuntu0.2-amd64:core-9.20160110ubuntu0.2-noarch:printing-9.20160110ubuntu0.2-amd64:printing-9.20160110ubuntu0.2-noarch:security-9.20160110ubuntu0.2-amd64:security-9.20160110ubuntu0.2-noarch
  Distributor ID:   Ubuntu
  Description:  Ubuntu 16.04.3 LTS
  Release:  16.04
  Codename: xenial

  $ apt-cache policy libreoffice
  libreoffice:
Installed: 1:6.0.1~rc1-0ubuntu0.16.04.1~lo1
Candidate: 1:6.0.1~rc1-0ubuntu0.16.04.1~lo1
Version table:
   *** 1:6.0.1~rc1-0ubuntu0.16.04.1~lo1 500
  500 http://ppa.launchpad.net/libreoffice/ppa/ubuntu xenial/main amd64 
Packages
  100 /var/lib/dpkg/status
   1:5.1.6~rc2-0ubuntu1~xenial2 500
  500 http://archive.ubuntu.com/ubuntu xenial-updates/universe amd64 
Packages
  500 http://archive.ubuntu.com/ubuntu xenial-security/universe amd64 
Packages
   1:5.1.2-0ubuntu1 500
  500 http://archive.ubuntu.com/ubuntu xenial/universe amd64 Packages

  WHAT YOU EXPECT TO HAPPEN:

Should spawn an new Evolution eMAIL with attached ODF document

  WHAT HAPPENED INSTEAD:

Error Dialogue: LibreOffice is unable to find a working email
  configuration.  Please save your document locally and attached from
  within your eMAIL client.

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1748895/+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 1767564] Re: Ubuntu 18.04 Workspaces only change on primary monitor

2018-09-24 Thread AL

+1 for the thank to Bruce and for the willing to have this option as
default.

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

Title:
  Ubuntu 18.04 Workspaces only change on primary monitor

Status in gnome-shell package in Ubuntu:
  Invalid

Bug description:
  After connecting an external monitor to the laptop:

  - the 4 workspaces that I could access using keyboard shortcuts seem to have 
been reduced to only 2
  - the 'workspace' does not appear to be changeable on the external 
(secondary) monitor

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.1-0ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr 28 12:42:28 2018
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.shell' b'command-history' redacted by apport
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  InstallationDate: Installed on 2018-04-28 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1767564/+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 1574347] Re: WiFi networks list disappears (device type not reloaded)

2018-09-24 Thread loveme

wifi disconnects frequently

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

Title:
  WiFi networks list disappears (device type not reloaded)

Status in NetworkManager:
  Fix Released
Status in OEM Priority Project:
  Fix Released
Status in network-manager package in Ubuntu:
  Fix Released
Status in network-manager source package in Xenial:
  Fix Released

Bug description:
  
  💥 WARNING 💥
  
  If you are still experiencing this bug please don't comment here, but look at 
these: (https://goo.gl/LdPpYG)

  **
   HOW TO REPRODUCE
  **
  Boot the system.

  
   RESULT
  
  From time to time, some of these happen:
  - The applet doesn't list any wireless network.
  - The applet doesn't show the name of the current network.
  - The icon shows the wired connection symbol, instead of the wifi one.

  *
   WORK AROUND
  *
  (http://askubuntu.com/questions/762198/16-04-lts-wifi-connection-issues)

  *
   FIX
  *
  The applet needs to re-read the DEVTYPE after the device name changed.

  ***
   HOW TO TEST A FIX
  ***
  In the Terminal application enter:
  nmcli dev

  If it works, in the line for the wireless device, the TYPE column
  should be "wifi". If it doesn't it will be "ethernet".

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager/+bug/1574347/+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 1785679] Re: [SRU] libreoffice 6.0.6 for bionic

** Changed in: libreoffice-l10n (Ubuntu)
   Status: New => Fix Released

** Changed in: libreoffice-l10n (Ubuntu)
 Assignee: (unassigned) => Olivier Tilloy (osomon)

** Changed in: libreoffice-l10n (Ubuntu Bionic)
 Assignee: (unassigned) => Olivier Tilloy (osomon)

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

Title:
  [SRU] libreoffice 6.0.6 for bionic

Status in libreoffice package in Ubuntu:
  Fix Released
Status in libreoffice-l10n package in Ubuntu:
  Fix Released
Status in libreoffice source package in Bionic:
  Fix Released
Status in libreoffice-l10n source package in Bionic:
  Fix Released

Bug description:
  [Impact]

   * LibreOffice 6.0.6 is the sixth bugfix release of the fresh 6.0 line. 
Version 6.0.3 is currently in bionic.
 For a list of fixed bugs compared to 6.0.3 see the list of bugs fixed in 
6.0.4, 6.0.5 and 6.0.6:
   https://wiki.documentfoundation.org/Releases/6.0.4/RC1#List_of_fixed_bugs
   https://wiki.documentfoundation.org/Releases/6.0.4/RC2#List_of_fixed_bugs
   https://wiki.documentfoundation.org/Releases/6.0.5/RC1#List_of_fixed_bugs
   https://wiki.documentfoundation.org/Releases/6.0.5/RC2#List_of_fixed_bugs
   https://wiki.documentfoundation.org/Releases/6.0.6/RC1#List_of_fixed_bugs
   https://wiki.documentfoundation.org/Releases/6.0.6/RC2#List_of_fixed_bugs
 (that's a total of 239 bugs)

   * Given the nature of the project, the complexity of the codebase and
  the high level of quality assurance upstream, it is preferable to SRU
  a minor release rather than cherry-pick selected bug fixes.

  [Test Case]

   * No specific test case, bugs fixed upstream hopefully come with
  unit/regression tests, and the release itself is extensively exercised
  upstream (both in an automated manner and manually) by a community of
  testers. Each minor release goes through two release candidates.

   * The libreoffice packages include autopkgtests, those should be run
  and verified to pass.

   * General smoke testing of all the applications in the office suite
  should be carried out.

  [Regression Potential]

   * A series of three minor releases with a total of 239 bug fixes
  always carries the potential for introducing regressions, even though
  they are bugfix-only releases, meaning that no new features were
  added, and no existing features were removed.

   * A combination of autopkgtests and careful smoke testing as
  described above should provide reasonable confidence that no
  regressions sneaked in.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1785679/+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 1794035] [NEW] package libglvnd-dev 1.0.0-2ubuntu2.1 failed to install/upgrade: tries to overwrite «/usr/lib/x86_64-linux-gnu/libGLESv1_CM.so», which is present in package nvid

2018-09-24 Thread BSA

Public bug reported:

Error occurs while upgrading packages. Before libgles1 were not
installed (it is dependency).

Packages in the update list:
fonts-liberation ipxe-qemu libegl1 libgl1 libgl1:i386 libgles2 
libglvnd-core-dev libglvnd-dev libglvnd0 libglvnd0:i386 libglx0 libglx0:i386 
libopengl0 libpython3.6 libpython3.6-dev libpython3.6-minimal 
libpython3.6-stdlib python3.6 python3.6-dev python3.6-minimal

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: libglvnd-dev 1.0.0-2ubuntu2.1
ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18
Uname: Linux 4.15.0-34-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.20.9-0ubuntu7.3
Architecture: amd64
Date: Mon Sep 24 11:50:45 2018
ErrorMessage: попытка перезаписать «/usr/lib/x86_64-linux-gnu/libGLESv1_CM.so», 
который уже имеется в пакете nvidia-340 340.106-0ubuntu3
InstallationDate: Installed on 2017-02-10 (590 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 
3.6.5-3ubuntu1
PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu2
 apt  1.6.3ubuntu0.1
SourcePackage: libglvnd
Title: package libglvnd-dev 1.0.0-2ubuntu2.1 failed to install/upgrade: попытка 
перезаписать «/usr/lib/x86_64-linux-gnu/libGLESv1_CM.so», который уже имеется в 
пакете nvidia-340 340.106-0ubuntu3
UpgradeStatus: Upgraded to bionic on 2018-08-09 (45 days ago)

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


** Tags: amd64 apport-package bionic

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

Title:
  package libglvnd-dev 1.0.0-2ubuntu2.1 failed to install/upgrade: tries
  to overwrite «/usr/lib/x86_64-linux-gnu/libGLESv1_CM.so», which is
  present in package nvidia-340 340.106-0ubuntu3

Status in libglvnd package in Ubuntu:
  New

Bug description:
  Error occurs while upgrading packages. Before libgles1 were not
  installed (it is dependency).

  Packages in the update list:
  fonts-liberation ipxe-qemu libegl1 libgl1 libgl1:i386 libgles2 
libglvnd-core-dev libglvnd-dev libglvnd0 libglvnd0:i386 libglx0 libglx0:i386 
libopengl0 libpython3.6 libpython3.6-dev libpython3.6-minimal 
libpython3.6-stdlib python3.6 python3.6-dev python3.6-minimal

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: libglvnd-dev 1.0.0-2ubuntu2.1
  ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18
  Uname: Linux 4.15.0-34-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.20.9-0ubuntu7.3
  Architecture: amd64
  Date: Mon Sep 24 11:50:45 2018
  ErrorMessage: попытка перезаписать 
«/usr/lib/x86_64-linux-gnu/libGLESv1_CM.so», который уже имеется в пакете 
nvidia-340 340.106-0ubuntu3
  InstallationDate: Installed on 2017-02-10 (590 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 
3.6.5-3ubuntu1
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.3ubuntu0.1
  SourcePackage: libglvnd
  Title: package libglvnd-dev 1.0.0-2ubuntu2.1 failed to install/upgrade: 
попытка перезаписать «/usr/lib/x86_64-linux-gnu/libGLESv1_CM.so», который уже 
имеется в пакете nvidia-340 340.106-0ubuntu3
  UpgradeStatus: Upgraded to bionic on 2018-08-09 (45 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libglvnd/+bug/1794035/+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 1784514] Update Released

The verification of the Stable Release Update for evolution-data-server
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 evolution-data-server in Ubuntu.
https://bugs.launchpad.net/bugs/1784514

Title:
  Update evolution-data-server to 3.28.5

Status in evolution-data-server package in Ubuntu:
  Fix Released
Status in evolution-data-server source package in Bionic:
  Fix Released

Bug description:
  Impact
  ==
  3.28.5 is the final scheduled bug fix release in the 3.28 series.

  Updating e-d-s is required to update evolution to 3.28.5 (LP:
  #1784522)

  https://gitlab.gnome.org/GNOME/evolution-data-server/blob/gnome-3-28/NEWS
  https://gitlab.gnome.org/GNOME/evolution-data-server/commits/gnome-3-28

  Test Case
  =
  After installing the update, restart your computer.

  Run several eds-using apps like Evolution, GNOME Calendar and verify
  that they continue to run at least as well as before this update.

  Regression Potential
  
  GNOME 3.28 distros will be shipping this update.

  There is a micro-release exception for GNOME:
  https://wiki.ubuntu.com/StableReleaseUpdates#GNOME

  3.22.6 introduced a regression in pop3 support that was fixed within a
  week by 3.22.7.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1784514/+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 1792648] Re: Can't preview document in evince - Ubuntu 18.10 Failed to execute child process (Permission Denied)

Related bug for opening a hyperlink when the default browser is a snap:
bug #1794064.

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

Title:
  Can't preview document in evince - Ubuntu 18.10 Failed to execute
  child process (Permission Denied)

Status in evince package in Ubuntu:
  In Progress

Bug description:
  Ubuntu 18.10 Evince of a PDF

  Clicking PREVIEW I get busy awhile then

  Failed to print document
  Failed to execute child process 
"/usr/lib/x86_64-linux-gnu/glib-2.0/gio-launch-desktop" (Permissions denied)

  --

  I looked at this only because of https://community.ubuntu.com/t
  /failed-to-preview-print/7956 where a user "flaviosm" reported the
  same thing.

  In `dmesg` I noted the following

  [43361.474096] audit: type=1400 audit(1536710182.492:65):
  apparmor=“DENIED” operation=“exec” profile="/usr/bin/evince"
  name="/usr/lib/x86_64-linux-gnu/glib-2.0/gio-launch-desktop" pid=11840
  comm=“evince” requested_mask=“x” denied_mask=“x” fsuid=1000 ouid=0

  I rebooted and tried again,  (same result)

  [ 400.208807] audit: type=1400 audit(1536711261.421:51):
  apparmor=“DENIED” operation=“exec” profile="/usr/bin/evince"
  name="/usr/lib/x86_64-linux-gnu/glib-2.0/gio-launch-desktop" pid=5302
  comm=“evince” requested_mask=“x” denied_mask=“x” fsuid=1000 ouid=0

  Note:   I don't have a printer setup on my box (I don't print from
  it), so this could be the cause!  I don't know if this applies to
  "flaviosm" too..  I can connect & test after printer is setup if
  deemed helpful (headcold - so no motivation currently)

  Filed online as unsuccessful via via `ubuntu-bug` on actual box..

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1792648/+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 1784514] Re: Update evolution-data-server to 3.28.5

This bug was fixed in the package evolution-data-server -
3.28.5-0ubuntu0.18.04.1

---
evolution-data-server (3.28.5-0ubuntu0.18.04.1) bionic; urgency=medium

  * New upstream release (LP: #1784514)

 -- Jeremy Bicha   Tue, 31 Jul 2018 10:14:54 -0400

** Changed in: evolution-data-server (Ubuntu Bionic)
   Status: Fix Committed => Fix Released

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

Title:
  Update evolution-data-server to 3.28.5

Status in evolution-data-server package in Ubuntu:
  Fix Released
Status in evolution-data-server source package in Bionic:
  Fix Released

Bug description:
  Impact
  ==
  3.28.5 is the final scheduled bug fix release in the 3.28 series.

  Updating e-d-s is required to update evolution to 3.28.5 (LP:
  #1784522)

  https://gitlab.gnome.org/GNOME/evolution-data-server/blob/gnome-3-28/NEWS
  https://gitlab.gnome.org/GNOME/evolution-data-server/commits/gnome-3-28

  Test Case
  =
  After installing the update, restart your computer.

  Run several eds-using apps like Evolution, GNOME Calendar and verify
  that they continue to run at least as well as before this update.

  Regression Potential
  
  GNOME 3.28 distros will be shipping this update.

  There is a micro-release exception for GNOME:
  https://wiki.ubuntu.com/StableReleaseUpdates#GNOME

  3.22.6 introduced a regression in pop3 support that was fixed within a
  week by 3.22.7.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1784514/+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 1794064] [NEW] Clicking a hyperlink in a PDF fails to open it if the default browser is a snap

Public bug reported:

This is related to bug #1792648. After fixing that one (see discussion
at https://salsa.debian.org/gnome-team/evince/merge_requests/1),
clicking a hyperlink in a PDF opens it correctly if the default browser
is a well-known application (such as /usr/bin/firefox), but it fails to
do so if the default browser is a snap (e.g. the chromium snap).

This is not a recent regression, it's not working on bionic either.

ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: evince 3.30.0-2
ProcVersionSignature: Ubuntu 4.18.0-7.8-generic 4.18.5
Uname: Linux 4.18.0-7-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.10-0ubuntu11
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Mon Sep 24 12:28:06 2018
EcryptfsInUse: Yes
InstallationDate: Installed on 2016-07-02 (813 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
SourcePackage: evince
UpgradeStatus: Upgraded to cosmic on 2018-09-14 (9 days ago)
modified.conffile..etc.apparmor.d.abstractions.evince: [modified]
mtime.conffile..etc.apparmor.d.abstractions.evince: 2018-09-24T11:35:41.904158

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


** Tags: amd64 apport-bug cosmic

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

Title:
  Clicking a hyperlink in a PDF fails to open it if the default browser
  is a snap

Status in evince package in Ubuntu:
  New

Bug description:
  This is related to bug #1792648. After fixing that one (see discussion
  at https://salsa.debian.org/gnome-team/evince/merge_requests/1),
  clicking a hyperlink in a PDF opens it correctly if the default
  browser is a well-known application (such as /usr/bin/firefox), but it
  fails to do so if the default browser is a snap (e.g. the chromium
  snap).

  This is not a recent regression, it's not working on bionic either.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: evince 3.30.0-2
  ProcVersionSignature: Ubuntu 4.18.0-7.8-generic 4.18.5
  Uname: Linux 4.18.0-7-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.10-0ubuntu11
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Sep 24 12:28:06 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-07-02 (813 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: evince
  UpgradeStatus: Upgraded to cosmic on 2018-09-14 (9 days ago)
  modified.conffile..etc.apparmor.d.abstractions.evince: [modified]
  mtime.conffile..etc.apparmor.d.abstractions.evince: 2018-09-24T11:35:41.904158

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1794064/+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 1794064] Re: Clicking a hyperlink in a PDF fails to open it if the default browser is a snap

Note that this works with the evince snap, only the deb package is
affected.

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

Title:
  Clicking a hyperlink in a PDF fails to open it if the default browser
  is a snap

Status in evince package in Ubuntu:
  New

Bug description:
  This is related to bug #1792648. After fixing that one (see discussion
  at https://salsa.debian.org/gnome-team/evince/merge_requests/1),
  clicking a hyperlink in a PDF opens it correctly if the default
  browser is a well-known application (such as /usr/bin/firefox), but it
  fails to do so if the default browser is a snap (e.g. the chromium
  snap).

  This is not a recent regression, it's not working on bionic either.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: evince 3.30.0-2
  ProcVersionSignature: Ubuntu 4.18.0-7.8-generic 4.18.5
  Uname: Linux 4.18.0-7-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.10-0ubuntu11
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Sep 24 12:28:06 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-07-02 (813 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: evince
  UpgradeStatus: Upgraded to cosmic on 2018-09-14 (9 days ago)
  modified.conffile..etc.apparmor.d.abstractions.evince: [modified]
  mtime.conffile..etc.apparmor.d.abstractions.evince: 2018-09-24T11:35:41.904158

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1794064/+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 1794035] Re: package libglvnd-dev 1.0.0-2ubuntu2.1 failed to install/upgrade: tries to overwrite «/usr/lib/x86_64-linux-gnu/libGLESv1_CM.so», which is present in package nvidia

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

** This bug has been marked a duplicate of bug 1791542
   package libglvnd-dev 1.0.0-2ubuntu2.1 failed to upgrade: trying to overwrite 
'/usr/lib/x86_64-linux-gnu/libGLESv1_CM.so', which is also in package 
nvidia-340 340.107-0ubuntu0~gpu18.04.1

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

Title:
  package libglvnd-dev 1.0.0-2ubuntu2.1 failed to install/upgrade: tries
  to overwrite «/usr/lib/x86_64-linux-gnu/libGLESv1_CM.so», which is
  present in package nvidia-340 340.106-0ubuntu3

Status in libglvnd package in Ubuntu:
  New

Bug description:
  Error occurs while upgrading packages. Before libgles1 were not
  installed (it is dependency).

  Packages in the update list:
  fonts-liberation ipxe-qemu libegl1 libgl1 libgl1:i386 libgles2 
libglvnd-core-dev libglvnd-dev libglvnd0 libglvnd0:i386 libglx0 libglx0:i386 
libopengl0 libpython3.6 libpython3.6-dev libpython3.6-minimal 
libpython3.6-stdlib python3.6 python3.6-dev python3.6-minimal

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: libglvnd-dev 1.0.0-2ubuntu2.1
  ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18
  Uname: Linux 4.15.0-34-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.20.9-0ubuntu7.3
  Architecture: amd64
  Date: Mon Sep 24 11:50:45 2018
  ErrorMessage: попытка перезаписать 
«/usr/lib/x86_64-linux-gnu/libGLESv1_CM.so», который уже имеется в пакете 
nvidia-340 340.106-0ubuntu3
  InstallationDate: Installed on 2017-02-10 (590 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 
3.6.5-3ubuntu1
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.3ubuntu0.1
  SourcePackage: libglvnd
  Title: package libglvnd-dev 1.0.0-2ubuntu2.1 failed to install/upgrade: 
попытка перезаписать «/usr/lib/x86_64-linux-gnu/libGLESv1_CM.so», который уже 
имеется в пакете nvidia-340 340.106-0ubuntu3
  UpgradeStatus: Upgraded to bionic on 2018-08-09 (45 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libglvnd/+bug/1794035/+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 789032] Re: power CPU did not OFF when system shutdown

2018-09-24 Thread Juhani Numminen

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

** Package changed: gucharmap (Ubuntu) => ubuntu

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

Title:
  power CPU did not OFF when system shutdown

Status in Ubuntu:
  Invalid

Bug description:
  Binary package hint: gucharmap

  i am running ubuntu 11.04 live  on USB flash disk

  ProblemType: Bug
  DistroRelease: Ubuntu 11.04
  Package: gucharmap 1:2.32.1-0ubuntu2
  ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2
  Uname: Linux 2.6.38-8-generic i686
  Architecture: i386
  Date: Fri May 27 17:17:18 2011
  ExecutablePath: /usr/bin/gucharmap
  LiveMediaBuild: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1)
  LocalLibraries: /opt/eset/esets/lib/libesets_pac.so
  ProcEnviron:
   LANGUAGE=en_US:en
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gucharmap
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/789032/+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 1794064] Re: Clicking a hyperlink in a PDF fails to open it if the default browser is a snap

I can "fix" the issue if I add the following two lines to
/etc/apparmor.d/abstractions/ubuntu-browsers and reload the evince
profile:

  /usr/bin/env rmix,
  /usr/bin/snap Cx -> sanitized_helper,

Probably not acceptable as is because this would allow executing any
snap, not just chromium. And snaps are not guaranteed to be strictly
confined (e.g. classic/devmode).

But a rule on /snap/bin/chromium is not good enough as
/snap/bin/chromium is a symlink to /usr/bin/snap.

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

Title:
  Clicking a hyperlink in a PDF fails to open it if the default browser
  is a snap

Status in evince package in Ubuntu:
  New

Bug description:
  This is related to bug #1792648. After fixing that one (see discussion
  at https://salsa.debian.org/gnome-team/evince/merge_requests/1),
  clicking a hyperlink in a PDF opens it correctly if the default
  browser is a well-known application (such as /usr/bin/firefox), but it
  fails to do so if the default browser is a snap (e.g. the chromium
  snap).

  This is not a recent regression, it's not working on bionic either.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: evince 3.30.0-2
  ProcVersionSignature: Ubuntu 4.18.0-7.8-generic 4.18.5
  Uname: Linux 4.18.0-7-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.10-0ubuntu11
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Sep 24 12:28:06 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-07-02 (813 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: evince
  UpgradeStatus: Upgraded to cosmic on 2018-09-14 (9 days ago)
  modified.conffile..etc.apparmor.d.abstractions.evince: [modified]
  mtime.conffile..etc.apparmor.d.abstractions.evince: 2018-09-24T11:35:41.904158

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1794064/+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 1766495] Re: "your libfreerdp does not support h264"

2018-09-24 Thread Jeroen

Same here, Ubuntu 18.04.1 LTS (Lubuntu), latest Remmina version.
Workaround the same as above, changing color depth to True Color (32bpp) fixed 
it.

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

Title:
  "your libfreerdp does not support h264"

Status in remmina package in Ubuntu:
  Confirmed

Bug description:
  When I try to connect via RDP, Remmina gives this error:

  "You requested an h264 GFX mode for server , but your
  libfreerdp does not support h264. Please check color depth settings."

  However, (1) I don't see any color depth settings in Remmina GUI, and
  (2) ubuntu-restricted-extras is installed. I have libx264-152 version
  2:0.152.2854+gite9a5903-2.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: remmina 1.2.0-rcgit.29+dfsg-1ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu6
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Tue Apr 24 09:29:44 2018
  InstallationDate: Installed on 2018-03-23 (31 days ago)
  InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180306.1)
  SourcePackage: remmina
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/remmina/+bug/1766495/+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 1759158] Re: Improve Thunderbird notifications for Gnome Shell

2018-09-24 Thread Eugene Romanenko

MF, this issue about integration with Gnome Shell notification
subsystem.

Badge count on dock icon is another (much painful) subject (eg bug
#1756837).

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

Title:
  Improve Thunderbird notifications for Gnome Shell

Status in thunderbird package in Ubuntu:
  New

Bug description:
  As Gnome Shell notification subsystem have more features than
  notifications in Unity, integration needs to be improved.

  Currently, in artful and bionic, Thunderbird notifications have two
  issues:

  1. On lock screen, Thunderbird always show "1 new notification" even
  multiple mails arrived while screen locked.

  2. Thunderbird should withdrawal notifications, if message was viewed
  and marked as read on another device (for IMAP only).

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: thunderbird 1:52.6.0+build1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-12-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.9-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  eugene 3929 F pulseaudio
  BuildID: 20180131200234
  Channel: Unavailable
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Mar 27 10:55:59 2018
  ForcedLayersAccel: False
  IfupdownConfig:
   auto lo
   iface lo inet loopback
  IncompatibleExtensions:
   English (GB) Language Pack - langpack-en...@thunderbird.mozilla.org
   Thunderbird (default) - {972ce4c6-7e08-4474-a285-3208198ce6fd}
  IwConfig:
   vboxnet0  no wireless extensions.
   
   enp5s0no wireless extensions.
   
   lono wireless extensions.
  MostRecentCrashID: bp-63008d16-a2d5-46b1-b9d2-3f3ef0180321
  Plugins: Shockwave Flash - /usr/lib/adobe-flashplugin/libflashplayer.so 
(adobe-flashplugin)
  PrefSources: prefs.js
  Profiles: Profile0 (Default) - LastVersion=52.6.0/20180131200234 (In use)
  RelatedPackageVersions: adobe-flashplugin 1:20180313.1-0ubuntu1
  RfKill:
   
  RunningIncompatibleAddons: True
  SourcePackage: thunderbird
  SubmittedCrashIDs: bp-63008d16-a2d5-46b1-b9d2-3f3ef0180321
  UpgradeStatus: Upgraded to bionic on 2017-10-24 (153 days ago)
  dmi.bios.date: 09/20/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2003
  dmi.board.asset.tag: Default string
  dmi.board.name: Z170-K
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2003:bd09/20/2016:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ170-K:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1759158/+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 1778011] Re: SRU: PRIME Power Saving mode draws too much power

2018-09-24 Thread Alberto Milone

@Aurelijus: not yet. I am going to add support for lightdm and for sddm
in the next update.

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

Title:
  SRU: PRIME Power Saving mode draws too much power

Status in HWE Next:
  New
Status in gdm3 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Fix Released
Status in nvidia-prime package in Ubuntu:
  Fix Released
Status in nvidia-settings package in Ubuntu:
  Fix Released
Status in ubuntu-drivers-common package in Ubuntu:
  Fix Released
Status in gdm3 source package in Bionic:
  Fix Committed
Status in nvidia-graphics-drivers-390 source package in Bionic:
  Fix Committed
Status in nvidia-prime source package in Bionic:
  Fix Committed
Status in nvidia-settings source package in Bionic:
  Fix Committed
Status in ubuntu-drivers-common source package in Bionic:
  Fix Committed

Bug description:
  SRU Request:

  [Impact]
  Relying on the nouveau driver and on the vga switcheroo (to get around a 
change in systemd LP: #1777099) caused increased power consumption, and slowed 
down the switching process.

  Furthermore, if the main X/Xwayland session was started by Gdm when
  the nvidia driver was loaded, the session will keep the nvidia module
  loaded, and prevent the system from switching off the dGPU. Also, the
  nouveau driver will be loaded, if nvidia is not, and this can cause
  problems to unsupported NVIDIA GPUs.

  The solution involves the following changes:

  1) Solving the problem in systemd (LP: #1777099)

  2) Adding code in gpu-manager and in nvidia-prime to unload the nvidia
  modules, and to allow the PCI device to sleep.

  3) Making a slight change to the current patch in Gdm, used to call
  the PRIME scripts before and after a Gdm session (so that gpu-manager
  gets actually called on log out)

  4) Adding code in gpu-manager to kill the main X/Xwayland session on
  log out, if the session is preventing us from unloading the nvidia
  driver. A new X/Xwayland session will be created after unload the
  module.

  5) Removing the systemd service that loads nouveau from the nvidia
  packages.

  [Test Case]
  1) Enable the -proposed repository, and install the new 
"ubuntu-drivers-common", nvidia drivers, nvidia-prime, and gdm3 *

  2) Make sure the nvidia packages are installed, and enable performance mode 
(if it is already enabled, call "sudo prime-select intel" first):
  sudo prime-select nvidia

  3) Restart your computer and attach your /var/log/gpu-manager.log. see
  if the system boots correctly. If unsure, please attach your /var/log
  /gpu-manager.log and /var/log/Xorg.0.log

  4) Select power saving mode:
  sudo prime-select intel

  5) Log out and log back in

  6) Check if the nvidia driver is still loaded:
  lsmod | grep nvidia

  [Regression Potential]
  Low, as hybrid graphics support does not work correctly, and the changes only 
affect this use case.

  _
  * Steps to test the updates:

  1) Enable the bionic-proposed repositories

  2) Create /etc/apt/preferences.d/proposed-updates with the following
  content:

  Package: *
  Pin: release a=bionic-proposed
  Pin-Priority: 400

  3) Update the list of packages:

  sudo apt-get update

  4) Install the packages from -proposed using the following command:

  sudo apt install nvidia-driver-390/bionic-proposed gdm3/bionic-
  proposed ubuntu-drivers-common/bionic-proposed nvidia-prime/bionic-
  proposed nvidia-settings/bionic-proposed libnvidia-gl-390/bionic-
  proposed libnvidia-compute-390/bionic-proposed libnvidia-decode-390
  /bionic-proposed libnvidia-encode-390/bionic-proposed libnvidia-
  ifr1-390/bionic-proposed libnvidia-fbc1-390/bionic-proposed

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1778011/+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 1778011] Re: SRU: PRIME Power Saving mode draws too much power

2018-09-24 Thread Alberto Milone

@Arthur: you probably need to install the 32 bit libraries manually from 
-proposed. Try with the following command:
sudo apt install libnvidia-gl-390:i386/bionic-proposed

as for 2), I would need some logs such as /var/log/gpu-manager.log after
reproducing the problem.

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

Title:
  SRU: PRIME Power Saving mode draws too much power

Status in HWE Next:
  New
Status in gdm3 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Fix Released
Status in nvidia-prime package in Ubuntu:
  Fix Released
Status in nvidia-settings package in Ubuntu:
  Fix Released
Status in ubuntu-drivers-common package in Ubuntu:
  Fix Released
Status in gdm3 source package in Bionic:
  Fix Committed
Status in nvidia-graphics-drivers-390 source package in Bionic:
  Fix Committed
Status in nvidia-prime source package in Bionic:
  Fix Committed
Status in nvidia-settings source package in Bionic:
  Fix Committed
Status in ubuntu-drivers-common source package in Bionic:
  Fix Committed

Bug description:
  SRU Request:

  [Impact]
  Relying on the nouveau driver and on the vga switcheroo (to get around a 
change in systemd LP: #1777099) caused increased power consumption, and slowed 
down the switching process.

  Furthermore, if the main X/Xwayland session was started by Gdm when
  the nvidia driver was loaded, the session will keep the nvidia module
  loaded, and prevent the system from switching off the dGPU. Also, the
  nouveau driver will be loaded, if nvidia is not, and this can cause
  problems to unsupported NVIDIA GPUs.

  The solution involves the following changes:

  1) Solving the problem in systemd (LP: #1777099)

  2) Adding code in gpu-manager and in nvidia-prime to unload the nvidia
  modules, and to allow the PCI device to sleep.

  3) Making a slight change to the current patch in Gdm, used to call
  the PRIME scripts before and after a Gdm session (so that gpu-manager
  gets actually called on log out)

  4) Adding code in gpu-manager to kill the main X/Xwayland session on
  log out, if the session is preventing us from unloading the nvidia
  driver. A new X/Xwayland session will be created after unload the
  module.

  5) Removing the systemd service that loads nouveau from the nvidia
  packages.

  [Test Case]
  1) Enable the -proposed repository, and install the new 
"ubuntu-drivers-common", nvidia drivers, nvidia-prime, and gdm3 *

  2) Make sure the nvidia packages are installed, and enable performance mode 
(if it is already enabled, call "sudo prime-select intel" first):
  sudo prime-select nvidia

  3) Restart your computer and attach your /var/log/gpu-manager.log. see
  if the system boots correctly. If unsure, please attach your /var/log
  /gpu-manager.log and /var/log/Xorg.0.log

  4) Select power saving mode:
  sudo prime-select intel

  5) Log out and log back in

  6) Check if the nvidia driver is still loaded:
  lsmod | grep nvidia

  [Regression Potential]
  Low, as hybrid graphics support does not work correctly, and the changes only 
affect this use case.

  _
  * Steps to test the updates:

  1) Enable the bionic-proposed repositories

  2) Create /etc/apt/preferences.d/proposed-updates with the following
  content:

  Package: *
  Pin: release a=bionic-proposed
  Pin-Priority: 400

  3) Update the list of packages:

  sudo apt-get update

  4) Install the packages from -proposed using the following command:

  sudo apt install nvidia-driver-390/bionic-proposed gdm3/bionic-
  proposed ubuntu-drivers-common/bionic-proposed nvidia-prime/bionic-
  proposed nvidia-settings/bionic-proposed libnvidia-gl-390/bionic-
  proposed libnvidia-compute-390/bionic-proposed libnvidia-decode-390
  /bionic-proposed libnvidia-encode-390/bionic-proposed libnvidia-
  ifr1-390/bionic-proposed libnvidia-fbc1-390/bionic-proposed

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1778011/+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 1759158] Re: Improve Thunderbird notifications for Gnome Shell

Thanks for the update, MF. I will mark it as confirmed.
Have a great day.
:)
G

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

Title:
  Improve Thunderbird notifications for Gnome Shell

Status in thunderbird package in Ubuntu:
  Confirmed

Bug description:
  As Gnome Shell notification subsystem have more features than
  notifications in Unity, integration needs to be improved.

  Currently, in artful and bionic, Thunderbird notifications have two
  issues:

  1. On lock screen, Thunderbird always show "1 new notification" even
  multiple mails arrived while screen locked.

  2. Thunderbird should withdrawal notifications, if message was viewed
  and marked as read on another device (for IMAP only).

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: thunderbird 1:52.6.0+build1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-12-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.9-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  eugene 3929 F pulseaudio
  BuildID: 20180131200234
  Channel: Unavailable
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Mar 27 10:55:59 2018
  ForcedLayersAccel: False
  IfupdownConfig:
   auto lo
   iface lo inet loopback
  IncompatibleExtensions:
   English (GB) Language Pack - langpack-en...@thunderbird.mozilla.org
   Thunderbird (default) - {972ce4c6-7e08-4474-a285-3208198ce6fd}
  IwConfig:
   vboxnet0  no wireless extensions.
   
   enp5s0no wireless extensions.
   
   lono wireless extensions.
  MostRecentCrashID: bp-63008d16-a2d5-46b1-b9d2-3f3ef0180321
  Plugins: Shockwave Flash - /usr/lib/adobe-flashplugin/libflashplayer.so 
(adobe-flashplugin)
  PrefSources: prefs.js
  Profiles: Profile0 (Default) - LastVersion=52.6.0/20180131200234 (In use)
  RelatedPackageVersions: adobe-flashplugin 1:20180313.1-0ubuntu1
  RfKill:
   
  RunningIncompatibleAddons: True
  SourcePackage: thunderbird
  SubmittedCrashIDs: bp-63008d16-a2d5-46b1-b9d2-3f3ef0180321
  UpgradeStatus: Upgraded to bionic on 2017-10-24 (153 days ago)
  dmi.bios.date: 09/20/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2003
  dmi.board.asset.tag: Default string
  dmi.board.name: Z170-K
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2003:bd09/20/2016:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ170-K:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1759158/+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 1759158] Re: Improve Thunderbird notifications for Gnome Shell

Thanks for the update, MF. I will mark it as confirmed.
Have a great day.
:)
G



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

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

Title:
  Improve Thunderbird notifications for Gnome Shell

Status in thunderbird package in Ubuntu:
  Confirmed

Bug description:
  As Gnome Shell notification subsystem have more features than
  notifications in Unity, integration needs to be improved.

  Currently, in artful and bionic, Thunderbird notifications have two
  issues:

  1. On lock screen, Thunderbird always show "1 new notification" even
  multiple mails arrived while screen locked.

  2. Thunderbird should withdrawal notifications, if message was viewed
  and marked as read on another device (for IMAP only).

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: thunderbird 1:52.6.0+build1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-12-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.9-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  eugene 3929 F pulseaudio
  BuildID: 20180131200234
  Channel: Unavailable
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Mar 27 10:55:59 2018
  ForcedLayersAccel: False
  IfupdownConfig:
   auto lo
   iface lo inet loopback
  IncompatibleExtensions:
   English (GB) Language Pack - langpack-en...@thunderbird.mozilla.org
   Thunderbird (default) - {972ce4c6-7e08-4474-a285-3208198ce6fd}
  IwConfig:
   vboxnet0  no wireless extensions.
   
   enp5s0no wireless extensions.
   
   lono wireless extensions.
  MostRecentCrashID: bp-63008d16-a2d5-46b1-b9d2-3f3ef0180321
  Plugins: Shockwave Flash - /usr/lib/adobe-flashplugin/libflashplayer.so 
(adobe-flashplugin)
  PrefSources: prefs.js
  Profiles: Profile0 (Default) - LastVersion=52.6.0/20180131200234 (In use)
  RelatedPackageVersions: adobe-flashplugin 1:20180313.1-0ubuntu1
  RfKill:
   
  RunningIncompatibleAddons: True
  SourcePackage: thunderbird
  SubmittedCrashIDs: bp-63008d16-a2d5-46b1-b9d2-3f3ef0180321
  UpgradeStatus: Upgraded to bionic on 2017-10-24 (153 days ago)
  dmi.bios.date: 09/20/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2003
  dmi.board.asset.tag: Default string
  dmi.board.name: Z170-K
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2003:bd09/20/2016:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ170-K:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1759158/+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 1792873] Re: FFE: 18.2.x for cosmic

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

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

Title:
  FFE: 18.2.x for cosmic

Status in mesa package in Ubuntu:
  New

Bug description:
  Mesa 18.2.0 was recently released after several delays, but at least
  it doesn't have any known regressions on Intel hw. We tend to get the
  latest major version in the devel series ~2 weeks after FF, but since
  a month has passed now I thought it would be best to file an actual
  FFE request.

  We'd also build it against LLVM 7, which is about to be released.
  Together these provide support for AMD Vega20 (kernel support still
  needed) among other things.

  New features from mesa upstream reldocs:

  OpenGL 4.3 on virgl
  OpenGL 4.4 Compatibility profile on radeonsi
  OpenGL ES 3.2 on radeonsi and virgl
  GL_ARB_ES3_2_compatibility on radeonsi
  GL_ARB_fragment_shader_interlock on i965
  GL_ARB_sample_locations and GL_NV_sample_locations on nvc0 (GM200+)
  GL_ANDROID_extension_pack_es31a on radeonsi.
  GL_KHR_texture_compression_astc_ldr on radeonsi
  GL_NV_conservative_raster and GL_NV_conservative_raster_dilate on nvc0 
(GM200+)
  GL_NV_conservative_raster_pre_snap_triangles on nvc0 (GP102+)
  multisampled images on nvc0 (GM107+) (now supported on GF100+)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1792873/+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 1439478] Re: Copy and Paste not Working in 15.04, 15.10, 16.04

2018-09-24 Thread helix84

Upstream issue (source and bug tracker moved from GitHub to GitLab):

https://gitlab.com/Remmina/Remmina/issues/533

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

Title:
  Copy and Paste not Working in 15.04, 15.10, 16.04

Status in remmina:
  Fix Released
Status in remmina package in Ubuntu:
  Fix Released
Status in remmina source package in Xenial:
  Triaged

Bug description:
  Remmina is probably one of the top 3 Linux applications "I need
  working right" to efficiently complete my work day.

  So, I consider it a critical bug that "copy and pasting" between
  "local and remote desktops" is not working in the 15.04 beta 2.

  This is one of those things, where if this is not fixed, I will have
  to return to Ubuntu 14.04, or figure out a way to install a version of
  Remmina that actually works correctly in 15.04.

  This bug has reared its ugly head before:
  https://bugs.launchpad.net/remmina/+bug/937522

  However, the status of that bug seems to be practically closed, so
  that's the reason for this new posting. I want to do all I can to get
  this bug the attention it needs. Remmina is crucial for my work.

  I'm currently dealing with the fact that it crashes a few times a day,
  but this "copy and paste not working" is a real deal-breaker for me to
  stay on 15.04.

To manage notifications about this bug go to:
https://bugs.launchpad.net/remmina/+bug/1439478/+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 1794078] [NEW] Rebooting / booting and battery charging

2018-09-24 Thread hpk...@gmail.com

Public bug reported:

Does not reboot and battery does not charge fully.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18
Uname: Linux 4.15.0-34-generic x86_64
NonfreeKernelModules: wl
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.9-0ubuntu7.3
Architecture: amd64
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Mon Sep 24 08:41:54 2018
DistUpgraded: 2018-09-23 21:15:55,906 DEBUG icon theme changed, re-reading
DistroCodename: bionic
DistroVariant: ubuntu
DkmsStatus:
 bcmwl, 6.30.223.271+bdcom, 4.15.0-34-generic, x86_64: installed
 bcmwl, 6.30.223.271+bdcom, 4.4.0-135-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a26] (rev 
09) (prog-if 00 [VGA controller])
   Subsystem: Apple Inc. Haswell-ULT Integrated Graphics Controller [106b:011b]
InstallationDate: Installed on 2018-09-23 (0 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
MachineType: Apple Inc. MacBookAir6,2
ProcEnviron:
 LANGUAGE=en_US
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-34-generic 
root=UUID=4add3271-ffc7-4961-97a0-f796b33a7d0f ro quiet splash vt.handoff=1
SourcePackage: xorg
UpgradeStatus: Upgraded to bionic on 2018-09-24 (0 days ago)
dmi.bios.date: 04/11/2018
dmi.bios.vendor: Apple Inc.
dmi.bios.version: MBA61.88Z.0107.B00.180437
dmi.board.asset.tag: Base Board Asset Tag#
dmi.board.name: Mac-7DF21CB3ED6977E5
dmi.board.vendor: Apple Inc.
dmi.board.version: MacBookAir6,2
dmi.chassis.type: 10
dmi.chassis.vendor: Apple Inc.
dmi.chassis.version: Mac-7DF21CB3ED6977E5
dmi.modalias: 
dmi:bvnAppleInc.:bvrMBA61.88Z.0107.B00.180437:bd04/11/2018:svnAppleInc.:pnMacBookAir6,2:pvr1.0:rvnAppleInc.:rnMac-7DF21CB3ED6977E5:rvrMacBookAir6,2:cvnAppleInc.:ct10:cvrMac-7DF21CB3ED6977E5:
dmi.product.family: MacBook Air
dmi.product.name: MacBookAir6,2
dmi.product.version: 1.0
dmi.sys.vendor: Apple Inc.
version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
version.libdrm2: libdrm2 2.4.91-2
version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
xserver.bootTime: Mon Sep 24 08:29:25 2018
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.19.6-1ubuntu4
xserver.video_driver: modeset

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


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

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

Title:
  Rebooting / booting and battery charging

Status in xorg package in Ubuntu:
  New

Bug description:
  Does not reboot and battery does not charge fully.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18
  Uname: Linux 4.15.0-34-generic x86_64
  NonfreeKernelModules: wl
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.3
  Architecture: amd64
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Mon Sep 24 08:41:54 2018
  DistUpgraded: 2018-09-23 21:15:55,906 DEBUG icon theme changed, re-reading
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   bcmwl, 6.30.223.271+bdcom, 4.15.0-34-generic, x86_64: installed
   bcmwl, 6.30.223.271+bdcom, 4.4.0-135-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a26] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Apple Inc. Haswell-ULT Integrated Graphics Controller 
[106b:011b]
  InstallationDate: Installed on 2018-09-23 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Apple Inc. MacBookAir6,2
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-34-generic 
root=UUID=4add3271-ffc7-4961-97a0-f796b33a7d0f ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: Upgraded to bionic on 2018-09-24 (0 days ago)
  dmi.bios.date: 04/11/2018
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBA61.88Z.0107.B00.180437
  dmi.board.asset.tag: B

[Desktop-packages] [Bug 1794081] [NEW] Nautilus Freezes with High CPU and RAM

2018-09-24 Thread bananenkasper

Public bug reported:

When opening Nautilus with Icon View, it freezes and causing 100% CPU
load and accumulates RAM until the system is out of RAM.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: nautilus 1:3.26.3-0ubuntu4
ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18
Uname: Linux 4.15.0-34-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Mon Sep 24 14:44:58 2018
GsettingsChanges:
 b'org.gnome.nautilus.window-state' b'sidebar-width' b'226'
 b'org.gnome.nautilus.window-state' b'geometry' b"'1213x1094+62+186'"
 b'org.gnome.nautilus.icon-view' b'default-zoom-level' b"'larger'"
 b'org.gnome.nautilus.list-view' b'use-tree-view' b'true'
 b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 
'type', 'owner', 'group', 'permissions', 'mime_type', 'where', 'date_modified', 
'date_modified_with_time', 'date_accessed', 'recency']"
InstallationDate: Installed on 2017-12-15 (283 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
SourcePackage: nautilus
UpgradeStatus: Upgraded to bionic on 2018-08-22 (33 days ago)
usr_lib_nautilus: dropbox 2015.10.28

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


** Tags: amd64 apport-bug bionic

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

Title:
  Nautilus Freezes with High CPU and RAM

Status in nautilus package in Ubuntu:
  New

Bug description:
  When opening Nautilus with Icon View, it freezes and causing 100% CPU
  load and accumulates RAM until the system is out of RAM.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: nautilus 1:3.26.3-0ubuntu4
  ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18
  Uname: Linux 4.15.0-34-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Sep 24 14:44:58 2018
  GsettingsChanges:
   b'org.gnome.nautilus.window-state' b'sidebar-width' b'226'
   b'org.gnome.nautilus.window-state' b'geometry' b"'1213x1094+62+186'"
   b'org.gnome.nautilus.icon-view' b'default-zoom-level' b"'larger'"
   b'org.gnome.nautilus.list-view' b'use-tree-view' b'true'
   b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 
'type', 'owner', 'group', 'permissions', 'mime_type', 'where', 'date_modified', 
'date_modified_with_time', 'date_accessed', 'recency']"
  InstallationDate: Installed on 2017-12-15 (283 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to bionic on 2018-08-22 (33 days ago)
  usr_lib_nautilus: dropbox 2015.10.28

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1794081/+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 1794024] Re: Transition from communitheme snap session to ubuntu

This bug was fixed in the package gnome-session - 3.30.0-0ubuntu3

---
gnome-session (3.30.0-0ubuntu3) cosmic; urgency=medium

  * Introduce a communitheme-snap-session for people who want to test
the communitheme snap in cosmic and over. Moving them out of the
ubuntu-session package.
This split enables us to transition communitheme snap users to default
ubuntu session after upgrading from bionic to cosmic or next LTS.
(LP: #1794024)

 -- Didier Roche   Mon, 24 Sep 2018 09:30:46 +0200

** Changed in: gnome-session (Ubuntu)
   Status: New => Fix Released

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

Title:
  Transition from communitheme snap session to ubuntu

Status in gnome-session package in Ubuntu:
  Fix Released

Bug description:
  In Bionic, we ship a communitheme snap, which shows up an additional
  gdm entry named "ubuntu communitheme".

  We want those users on Bionic -> Cosmic upgrade (and later, bionic LTS
  -> f LTS) to fallback to the ubuntu session to not pick the theme in
  the snap.

  However, we still want a way for people to install the communitheme
  session for testing latest edge.

  Plan is:
  - remove from ubuntu-session package the communitheme .desktop session files. 
This way, people will be fallbacked to the ubuntu session.
  - readd another session package, like communitheme-session, containing those 
.desktop files. That will be the package that people can use to use the snap 
theme version.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1794024/+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 1791367] Re: Airplane mode key on Asus ZenBook Flip UX561UD laptop not working in gnome-shell (X or Wayland) but working on console (Cosmic 18.10)

2018-09-24 Thread Gunnar Hjalmarsson

Test build of xkeyboard-config available here:

https://launchpad.net/~gunnarhj/+archive/ubuntu/xkeyboard-config

Not sure it makes a difference wrt airplane mode, though. Please feel
free to test, Mario.

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

Title:
  Airplane mode key on Asus ZenBook Flip UX561UD laptop not working in
  gnome-shell (X or Wayland) but working on console (Cosmic 18.10)

Status in xkeyboard-config package in Ubuntu:
  Triaged

Bug description:
  Please forgive if filed for wrong package. Problem occurs in X and
  Wayland sessions but not on console, so does not seem to be kernel.

  Repro on Asus UX561UD with Ubuntu 18.10 up to date:
  1. Log into Gnome X or Gnome Wayland session
  2. Press Fn+F2 which is the airplane mode key

  -> Airplane mode should turn on but nothing happens

  3. Switch to console with Ctrl+Alt+F3
  4. Log into console
  5. Press Fn+F2 again
  6. Switch back to GUI session with Ctrl+Alt+F2

  -> Airplane mode is on, icon appeared in Gnome task bar

  Same for turning it off.

  No difference when booting 18.04.1 live image

  This laptop seems not the only one with this problem. I got the idea for 
trying the console trick from ArenaL5's answer on Askubuntu, but unfortunately 
there is no solution there:
  https://askubuntu.com/questions/972367/airplane-mode-switch-does-not-respond

  Please let me know whatever I can do to help debug this.

  All other Fn+Fx special keys on this laptop work (display brightness,
  touchpad off, sound etc.) except for keyboard backlight, but that
  works with Ubuntu 18.04.1 and I will file a separate bug for this

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: xorg 1:7.7+19ubuntu8
  ProcVersionSignature: Ubuntu 4.17.0-9.10-generic 4.17.17
  Uname: Linux 4.17.0-9-generic x86_64
  ApportVersion: 2.20.10-0ubuntu9
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep  7 21:37:01 2018
  DistUpgraded: Fresh install
  DistroCodename: cosmic
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 390.87, 4.17.0-9-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
     Subsystem: ASUSTeK Computer Inc. UHD Graphics 620 [1043:14ee]
     Subsystem: ASUSTeK Computer Inc. GP107M [GeForce GTX 1050 Mobile] 
[1043:14ee]
  InstallationDate: Installed on 2018-09-05 (1 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180822)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0a2b Intel Corp.
   Bus 001 Device 003: ID 13d3:5256 IMC Networks
   Bus 001 Device 002: ID 8644:800b Intenso GmbG Micro Line (4GB)
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. UX561UD
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.17.0-9-generic 
root=UUID=02bad6b5-ca8f-4184-b477-935995e14bdc ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/06/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX561UD.304
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX561UD
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX561UD.304:bd03/06/2018:svnASUSTeKCOMPUTERINC.:pnUX561UD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX561UD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct31:cvr1.0:
  dmi.product.family: ZenBook Flip
  dmi.product.name: UX561UD
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.94-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.1.5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.1.5-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1build1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1build1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xkeyboard-config/+bug/1791367/+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 1789924] Re: Missing Intel GPU pci-id's

Hello Timo, or anyone else affected,

Accepted xorg-server into bionic-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/xorg-
server/2:1.19.6-1ubuntu4.1 in a few hours, and then in the -proposed
repository.

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

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-bionic to verification-done-bionic. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-bionic. In either case, without details of
your testing we will not be able to proceed.

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

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: xorg-server (Ubuntu Bionic)
   Status: New => Fix Committed

** Tags added: verification-needed

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

Title:
  Missing Intel GPU pci-id's

Status in libdrm package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Committed
Status in mesa package in Ubuntu:
  New
Status in xorg-server package in Ubuntu:
  Fix Released
Status in libdrm source package in Bionic:
  New
Status in linux source package in Bionic:
  Fix Committed
Status in mesa source package in Bionic:
  New
Status in xorg-server source package in Bionic:
  Fix Committed

Bug description:
  [Impact]
  There are some new Intel GPU pci-id's that need to be added to several places:

  0x3E98
  0x87C0

  and to make future additions easier, add platform definitions for
  Whiskey Lake and Amber Lake too.

  [Test case]
  Check that the user session uses the proper driver on these systems.

  [Regression potential]
  none, these just add pci-id's and platform definitions

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1789924/+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 1789913] Re: X crashes with "randr: falling back to unsynchronized pixmap sharing" when connecting to an external monitor via HDMI (I+A)

Hello Timo, or anyone else affected,

Accepted xorg-server into bionic-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/xorg-
server/2:1.19.6-1ubuntu4.1 in a few hours, and then in the -proposed
repository.

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

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-bionic to verification-done-bionic. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-bionic. In either case, without details of
your testing we will not be able to proceed.

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

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: xorg-server (Ubuntu Bionic)
   Status: Triaged => Fix Committed

** Tags added: verification-needed verification-needed-bionic

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

Title:
  X crashes with "randr: falling back to unsynchronized pixmap sharing"
  when connecting to an external monitor via HDMI (I+A)

Status in xorg-server package in Ubuntu:
  Fix Released
Status in xorg-server-hwe-16.04 package in Ubuntu:
  Invalid
Status in xorg-server source package in Xenial:
  Won't Fix
Status in xorg-server-hwe-16.04 source package in Xenial:
  Triaged
Status in xorg-server source package in Bionic:
  Fix Committed
Status in xorg-server-hwe-16.04 source package in Bionic:
  Invalid

Bug description:
  [Impact]
  X server crashes in certain cases on I+A hybrid machines with 
modesetting+amdgpu drivers.

  [Test case]
  Connect an external monitor, check that it doesn't crash X.

  [Regression potential]
  This commit was provided by AMD and reviewed by an NVIDIA engineer, and after 
a few iterations it got applied upstream. We'll test it with many driver 
combinations (modesetting+amdgpu, m+nvidia, m+m...) to check that they all 
(still) work.

  
  --

  Copied from a private bug:

  - Steps to see the issue:
  1. Connect a monitor to UUT via HDMI port
  Expected Result:
    Video outputs successfully in the monitor
  Actual Result:
    X crashes into a login screen

  - BIOS: 0.7.3
  - AMD driver release: 18.10, 18.20RC8 and 18.20RC9

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1789913/+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 1791542] Re: package libglvnd-dev 1.0.0-2ubuntu2.1 failed to upgrade: trying to overwrite '/usr/lib/x86_64-linux-gnu/libGLESv1_CM.so', which is also in package nvidia-340 340.1

2018-09-24 Thread Wolf Geldmacher

Fixed it for me.

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

Title:
  package libglvnd-dev 1.0.0-2ubuntu2.1 failed to upgrade: trying to
  overwrite '/usr/lib/x86_64-linux-gnu/libGLESv1_CM.so', which is also
  in package nvidia-340 340.107-0ubuntu0~gpu18.04.1

Status in libglvnd package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Fix Released
Status in libglvnd source package in Bionic:
  Confirmed
Status in nvidia-graphics-drivers-340 source package in Bionic:
  Fix Committed

Bug description:
  SRU Request:

  [Impact]

  The new libgles1 conflicts with nvidia-340 which ships it's own copy
  of libGLESv1_CM.so

  [Test case]

  Enable proposed, install libgles1 and nvidia-340, they should install
  fine.

  [Regression potential]

  none, just fixes a file conflict

  --

  Looks like I had a similar problem on 18.04.1 than
  https://bugs.launchpad.net/ubuntu/+source/libglvnd/+bug/1728352, just
  with nvidia-340 from https://launchpad.net/~graphics-
  drivers/+archive/ubuntu/ppa .

  Apt output:
  ```
  $ sudo apt dist-upgrade
  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  Calculating upgrade... Done
  The following NEW packages will be installed:
    libgles1
  The following packages will be upgraded:
    libegl1 libgl1 libgles2 libglvnd-core-dev libglvnd-dev libglvnd0 libglx0 
libopengl0
  8 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
  Need to get 268 kB of archives.
  After this operation, 66,6 kB of additional disk space will be used.
  Do you want to continue? [Y/n]
  Get:1 http://archive.ubuntu.com/ubuntu bionic-proposed/main amd64 
libglvnd-dev amd64 1.0.0-2ubuntu2.2 [3 408 B]
  Get:2 http://archive.ubuntu.com/ubuntu bionic-proposed/main amd64 
libglvnd-core-dev amd64 1.0.0-2ubuntu2.2 [12,9 kB]
  Get:3 http://archive.ubuntu.com/ubuntu bionic-proposed/main amd64 libgles2 
amd64 1.0.0-2ubuntu2.2 [17,4 kB]
  Get:4 http://archive.ubuntu.com/ubuntu bionic-proposed/main amd64 libgl1 
amd64 1.0.0-2ubuntu2.2 [84,8 kB]
  Get:5 http://archive.ubuntu.com/ubuntu bionic-proposed/main amd64 libglx0 
amd64 1.0.0-2ubuntu2.2 [28,1 kB]
  Get:6 http://archive.ubuntu.com/ubuntu bionic-proposed/main amd64 libopengl0 
amd64 1.0.0-2ubuntu2.2 [31,3 kB]
  Get:7 http://archive.ubuntu.com/ubuntu bionic-proposed/main amd64 libegl1 
amd64 1.0.0-2ubuntu2.2 [31,9 kB]
  Get:8 http://archive.ubuntu.com/ubuntu bionic-proposed/main amd64 libglvnd0 
amd64 1.0.0-2ubuntu2.2 [46,6 kB]
  Get:9 http://archive.ubuntu.com/ubuntu bionic-proposed/main amd64 libgles1 
amd64 1.0.0-2ubuntu2.2 [11,2 kB]
  Fetched 268 kB in 0s (1 575 kB/s)
  (Reading database ... 141610 files and directories currently installed.)
  Preparing to unpack .../0-libglvnd-dev_1.0.0-2ubuntu2.2_amd64.deb ...
  Unpacking libglvnd-dev:amd64 (1.0.0-2ubuntu2.2) over (1.0.0-2ubuntu2.1) ...
  dpkg: error processing archive 
/tmp/apt-dpkg-install-Gq7kQI/0-libglvnd-dev_1.0.0-2ubuntu2.2_amd64.deb 
(--unpack):
   trying to overwrite '/usr/lib/x86_64-linux-gnu/libGLESv1_CM.so', which is 
also in package nvidia-340 340.107-0ubuntu0~gpu18.04.1
  Preparing to unpack .../1-libglvnd-core-dev_1.0.0-2ubuntu2.2_amd64.deb ...
  Unpacking libglvnd-core-dev:amd64 (1.0.0-2ubuntu2.2) over (1.0.0-2ubuntu2.1) 
...
  Preparing to unpack .../2-libgles2_1.0.0-2ubuntu2.2_amd64.deb ...
  Unpacking libgles2:amd64 (1.0.0-2ubuntu2.2) over (1.0.0-2ubuntu2.1) ...
  Preparing to unpack .../3-libgl1_1.0.0-2ubuntu2.2_amd64.deb ...
  Unpacking libgl1:amd64 (1.0.0-2ubuntu2.2) over (1.0.0-2ubuntu2.1) ...
  Preparing to unpack .../4-libglx0_1.0.0-2ubuntu2.2_amd64.deb ...
  Unpacking libglx0:amd64 (1.0.0-2ubuntu2.2) over (1.0.0-2ubuntu2.1) ...
  Preparing to unpack .../5-libopengl0_1.0.0-2ubuntu2.2_amd64.deb ...
  Unpacking libopengl0:amd64 (1.0.0-2ubuntu2.2) over (1.0.0-2ubuntu2.1) ...
  Preparing to unpack .../6-libegl1_1.0.0-2ubuntu2.2_amd64.deb ...
  Unpacking libegl1:amd64 (1.0.0-2ubuntu2.2) over (1.0.0-2ubuntu2.1) ...
  Preparing to unpack .../7-libglvnd0_1.0.0-2ubuntu2.2_amd64.deb ...
  Unpacking libglvnd0:amd64 (1.0.0-2ubuntu2.2) over (1.0.0-2ubuntu2.1) ...
  Selecting previously unselected package libgles1:amd64.
  Preparing to unpack .../8-libgles1_1.0.0-2ubuntu2.2_amd64.deb ...
  Unpacking libgles1:amd64 (1.0.0-2ubuntu2.2) ...
  dpkg: error processing archive 
/tmp/apt-dpkg-install-Gq7kQI/8-libgles1_1.0.0-2ubuntu2.2_amd64.deb (--unpack):
   trying to overwrite '/usr/lib/x86_64-linux-gnu/libGLESv1_CM.so.1', which is 
also in package nvidia-340 340.107-0ubuntu0~gpu18.04.1
  Errors were encountered while processing:
   /tmp/apt-dpkg-install-Gq7kQI/0-libglvnd-dev_1.0.0-2ubuntu2.2_amd64.deb
   /tmp/apt-dpkg-install-Gq7kQI/8-libgles1_1.0.0-2ubuntu2.2_amd64.deb
  E: Sub-process /usr/bin/dpkg returned an error code (1)
  ```

  ProblemType: Package
  DistroRelease:

[Desktop-packages] [Bug 435152] Re: [karmic]udev-configure-printer not add Cannon Printer/Scaner

Hello Sabsem,
Thank you for submitting this bug and reporting a problem with 
system-config-printer.  You made this bug report some time ago and Ubuntu has 
been updated since then. 
 
Could you confirm that this is no longer a problem and that we can close the 
bug report? 
If it is still a problem, are you still interested in finding a solution to 
this bug? 
If you are, could you let us know, and in the current version, run the 
following (only once): 
apport-collect BUGNUMBER
and upload the updated logs and and any other logs that are relevant for this 
particular issue.  

Thank you again for helping make Ubuntu better. 
G
[Ubuntu Bug Squad volunteer triager]

** Changed in: system-config-printer (Ubuntu)
   Status: New => Incomplete

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

Title:
  [karmic]udev-configure-printer not add Cannon Printer/Scaner

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

Bug description:
  Binary package hint: system-config-printer

  system-config-printer-udev 1.1.12+git20090826-0ubuntu2

  2009-09-23 13:46:53   ithome  kernel  [ 4888.350163] usb 1-10: configuration 
#1 chosen from 1 choice
  2009-09-23 13:46:53   ithome  kernel  [ 4954.852751] usb 1-10: USB 
disconnect, address 6
  2009-09-23 13:46:53   ithome  kernel  [ 4967.825047] usb 1-10: new high speed 
USB device using ehci_hcd and address 7
  2009-09-23 13:46:53   ithome  kernel  [ 4968.042016] usb 1-10: configuration 
#1 chosen from 1 choice
  2009-09-23 13:46:53   ithome  kernel  [ 5545.869552] usb 1-10: USB 
disconnect, address 7
  2009-09-23 13:46:53   ithome  kernel  [ 5549.648051] usb 1-10: new high speed 
USB device using ehci_hcd and address 8
  2009-09-23 13:46:53   ithome  kernel  [ 5549.865895] usb 1-10: configuration 
#1 chosen from 1 choice
  2009-09-23 13:46:53   ithome  kernel  [ 9686.730494] usb 1-10: USB 
disconnect, address 8
  2009-09-23 13:46:53   ithome  udev-configure-printer  add 
/devices/pci:00/:00:02.1/usb1/1-10/1-10:1.1
  2009-09-23 13:46:53   ithome  udev-configure-printer  parent devpath is 
/devices/pci:00/:00:02.1/usb1/1-10
  2009-09-23 13:46:53   ithome  udev-configure-printer  Device vendor/product 
is 04A9:26A3
  2009-09-23 13:46:53   ithome  udev-configure-printer  Failed to fetch Device 
ID
  2009-09-23 13:46:53   ithome  udev-configure-printer  invalid or missing IEEE 
1284 Device ID

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/system-config-printer/+bug/435152/+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 412336] Re: Crash while browsing smb printer shares

Hello Fuzzy,
Thank you for submitting this bug and reporting a problem with
system-config-printer. You made this bug report some time ago and Ubuntu has
been updated since then.

Could you confirm that this is no longer a problem and that we can close the
bug report?
If it is still a problem, are you still interested in finding a solution to
this bug?
If you are, could you let us know, and in the current version, run the
following (only once):
apport-collect BUGNUMBER
and upload the updated logs and and any other logs that are relevant for this
particular issue.

Thank you again for helping make Ubuntu better.
G
[Ubuntu Bug Squad volunteer triager]

** Changed in: system-config-printer (Ubuntu)
Status: New => Incomplete

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

Title:
Crash while browsing smb printer shares

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

Bug description:
I am not able to browse for printer shares exposed by a windows
machine at my mother-in-law's house. I can type the name in manually,
but browsing causes a crash of system-config-printer. This is an up-
to-date 32-bit i686 hardy laptop with wireless-only connectivity.

Method:
* Open System -> Administration -> Printing from the gnome panel
* Select New
* Network Printer -> Windows Printer via SAMBA
* Browse
* Two workgroups are shown: MSHOME and WORKGROUP. The linux machine is part
of WORKGROUP. The machine sharing the printer is part of MSHOME
* Open the MSHOME sub-tree (sometimes the dialogue will crash at this point)
* LLCAP01 and WRAY-PC are shown. The printer is shared from LLCAP01.
* Open the LLCAP01 sub-tree (sometimes the dialogue will crash at this point,
the attached wireshark output relates to a crash at this point)

I have attached a wireshark trace of this occuring. I'm not quite sure
how to get a stack trace out for you. If I start system-config-printer
from the command-line, I see a segmentation fault but no other output.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/system-config-printer/+bug/412336/+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 1794104] Re: Xorg crash on first boot after apt upgrade

2018-09-24 Thread Christian Kirbach

(gdb) bt full
#0  __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
set = {__val = {171515904, 0, 0, 0, 0, 94870821356889, 94870821322000, 
67108868, 140427223543248, 0, 0, 978464917824351488, 54, 94870838790880, 
140727493513216, 140427243872632}}
pid = 
tid = 
ret = 
#1  0x7fb7c2a90535 in __GI_abort () at abort.c:79
save_stage = 1
act = {__sigaction_handler = {sa_handler = 0x36, sa_sigaction = 0x36}, 
sa_mask = {__val = {94870838790880, 140727493513216, 140427243872632, 1, 384, 
0, 978464917824351488, 206158430256, 94870821333191, 
  171515904, 0, 0, 67108868, 140427223543248, 978464917824351488, 
0}}, sa_flags = -711032432, sa_restorer = 0x7ffdac42d0f0}
sigs = {__val = {32, 0 }}
#2  0x5648d59ae96a in OsAbort ()
No symbol table info available.
#3  0x5648d59b4473 in ?? ()
No symbol table info available.
#4  0x5648d59b52d9 in FatalError ()
No symbol table info available.
#5  0x5648d59abd81 in ?? ()
No symbol table info available.
#6  
No locals.
#7  __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
set = {__val = {0, 94870844899072, 0, 140427222016815, 
18446744073637036032, 94870844899072, 94870844899173, 94870844899072, 
94870844899072, 94870844899180, 94870844899372, 94870844899072, 94870844899372, 
0, 
0, 0}}
pid = 
tid = 
ret = 
#8  0x7fb7c2a90535 in __GI_abort () at abort.c:79
save_stage = 1
act = {__sigaction_handler = {sa_handler = 0x5648d72c5880, sa_sigaction 
= 0x5648d72c5880}, sa_mask = {__val = {0, 6, 5, 0, 0, 0, 140727493515688, 
21474836480, 140727493515536, 140427223237216, 
  140427223222360, 0, 978464917824351488, 140427223207162, 0, 
140427223222360}}, sa_flags = -711201992, sa_restorer = 0x5648d59beb7d}
sigs = {__val = {32, 0 }}
#9  0x7fb7c2a9040f in __assert_fail_base (fmt=0x7fb7c2c1c858 "%s%s%s:%u: 
%s%sAssertion `%s' failed.\n%n", assertion=0x5648d59beb7d 
"!global_keys[type].created", file=0x5648d59beb38 "../../../../dix/privates.c", 
line=384, function=) at assert.c:92
str = 0x5648d72c5880 ""
total = 4096
#10 0x7fb7c2aa0142 in __GI___assert_fail (assertion=0x5648d59beb7d 
"!global_keys[type].created", file=0x5648d59beb38 "../../../../dix/privates.c", 
line=384, function=0x5648d59bede0 "dixRegisterPrivateKey")
at assert.c:101
No locals.
#11 0x5648d586be89 in dixRegisterPrivateKey ()
No symbol table info available.
#12 0x7fb7b98bf529 in glamor_init () from 
/usr/lib/xorg/modules/libglamoregl.so
No symbol table info available.
#13 0x7fb7c14a4a2d in ?? () from 
/usr/lib/xorg/modules/drivers/modesetting_drv.so
No symbol table info available.
#14 0x7fb7c149cb97 in ?? () from 
/usr/lib/xorg/modules/drivers/modesetting_drv.so
No symbol table info available.
#15 0x5648d584dc90 in AddGPUScreen ()
No symbol table info available.
#16 0x5648d58a7d8c in ?? ()
No symbol table info available.
--Type  for more, q to quit, c to continue without paging--c
#17 0x5648d58ad5e1 in ?? ()
No symbol table info available.
#18 0x5648d58a9ec9 in ?? ()
No symbol table info available.
#19 0x5648d58aa340 in ?? ()
No symbol table info available.
#20 0x5648d59ac731 in ?? ()
No symbol table info available.
#21 0x5648d59a5983 in WaitForSomething ()
No symbol table info available.
#22 0x5648d584d64c in ?? ()
No symbol table info available.
#23 0x5648d5851846 in ?? ()
No symbol table info available.
#24 0x7fb7c2a9209b in __libc_start_main (main=0x5648d583b5c0, argc=11, 
argv=0x7ffdac42ebf8, init=, fini=, 
rtld_fini=, stack_end=0x7ffdac42ebe8) at ../csu/libc-start.c:308
self = 
result = 
unwind_buf = {cancel_jmp_buf = {{jmp_buf = {0, 5132712507193217625, 
94870819812816, 140727493520368, 0, 0, 1464229968777368153, 
1496638397908963929}, mask_was_saved = 0}}, priv = {pad = {0x0, 0x0, 
0x7ffdac42ec58, 0x7fb7c45ca190}, data = {prev = 0x0, cleanup = 0x0, canceltype 
= -1404900264}}}
not_first_call = 
#25 0x5648d583b5fa in _start ()
No symbol table info available.
(gdb)

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

Title:
  Xorg crash on first boot after apt upgrade

Status in xorg package in Ubuntu:
  New

Bug description:
  I installed a daily snapshot of 18.10 in a VM.
  After removing some unneccessary application, I ran

  apt update
  apt upgrade

  and rebooted. I noticed X crashing after the reboot, taking me back to the 
login manager. I have the option selected to automatically login without 
password. 
  X did not crash when coming up the second time, tough.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: xorg 1:7.7+19ubuntu8
  ProcVersionSignature: Ubuntu 4.18.0-7.8-generic 4.18.5
  Uname: Linux 4.18.0-7-generic x86_64
  ApportVersion: 2.20.10-0ubuntu11

[Desktop-packages] [Bug 1794104] [NEW] Xorg crash on first boot after apt upgrade

2018-09-24 Thread Christian Kirbach

Public bug reported:

I installed a daily snapshot of 18.10 in a VM.
After removing some unneccessary application, I ran

apt update
apt upgrade

and rebooted. I noticed X crashing after the reboot, taking me back to the 
login manager. I have the option selected to automatically login without 
password. 
X did not crash when coming up the second time, tough.

ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: xorg 1:7.7+19ubuntu8
ProcVersionSignature: Ubuntu 4.18.0-7.8-generic 4.18.5
Uname: Linux 4.18.0-7-generic x86_64
ApportVersion: 2.20.10-0ubuntu11
Architecture: amd64
BootLog:
 
CompositorRunning: None
Date: Mon Sep 24 15:54:18 2018
DistUpgraded: Fresh install
DistroCodename: cosmic
DistroVariant: ubuntu
DkmsStatus: virtualbox-guest, 5.2.18, 4.18.0-7-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard: InnoTek Systemberatung GmbH VirtualBox Graphics Adapter 
[80ee:beef] (prog-if 00 [VGA controller])
InstallationDate: Installed on 2018-09-14 (10 days ago)
InstallationMedia: Xubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180913)
Lsusb:
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: innotek GmbH VirtualBox
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-7-generic 
root=UUID=ecdea6ce-6b53-45e4-ac1e-1caae18058d5 ro quiet splash
SourcePackage: xorg
Symptom: display
Title: Xorg crash
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/01/2006
dmi.bios.vendor: innotek GmbH
dmi.bios.version: VirtualBox
dmi.board.name: VirtualBox
dmi.board.vendor: Oracle Corporation
dmi.board.version: 1.2
dmi.chassis.type: 1
dmi.chassis.vendor: Oracle Corporation
dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
dmi.product.family: Virtual Machine
dmi.product.name: VirtualBox
dmi.product.version: 1.2
dmi.sys.vendor: innotek GmbH
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.94-1
version.libgl1-mesa-dri: libgl1-mesa-dri 18.1.5-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 18.1.5-1ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-1ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1build1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3

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


** Tags: amd64 apport-bug cosmic crash regression single-occurrence ubuntu

** Attachment added: "core file"
   https://bugs.launchpad.net/bugs/1794104/+attachment/5192428/+files/core.xz

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

Title:
  Xorg crash on first boot after apt upgrade

Status in xorg package in Ubuntu:
  New

Bug description:
  I installed a daily snapshot of 18.10 in a VM.
  After removing some unneccessary application, I ran

  apt update
  apt upgrade

  and rebooted. I noticed X crashing after the reboot, taking me back to the 
login manager. I have the option selected to automatically login without 
password. 
  X did not crash when coming up the second time, tough.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: xorg 1:7.7+19ubuntu8
  ProcVersionSignature: Ubuntu 4.18.0-7.8-generic 4.18.5
  Uname: Linux 4.18.0-7-generic x86_64
  ApportVersion: 2.20.10-0ubuntu11
  Architecture: amd64
  BootLog:
   
  CompositorRunning: None
  Date: Mon Sep 24 15:54:18 2018
  DistUpgraded: Fresh install
  DistroCodename: cosmic
  DistroVariant: ubuntu
  DkmsStatus: virtualbox-guest, 5.2.18, 4.18.0-7-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard: InnoTek Systemberatung GmbH VirtualBox Graphics Adapter 
[80ee:beef] (prog-if 00 [VGA controller])
  InstallationDate: Installed on 2018-09-14 (10 days ago)
  InstallationMedia: Xubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180913)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: innotek GmbH VirtualBox
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-7-generic 
root=UUID=ecdea6ce-6b53-45e4-ac1e-1caae18058d5 ro quiet splash
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnote

[Desktop-packages] [Bug 459648] Re: udev-configure-printer /invalid or missing IEEE 1284 Device ID

Hello Starslights,
Thank you for submitting this bug and reporting a problem with 
system-config-printer.  You made this bug report some time ago and Ubuntu has 
been updated since then. 
 
Could you confirm that this is no longer a problem and that we can close the 
bug report? 
If it is still a problem, are you still interested in finding a solution to 
this bug? 
If you are, could you let us know, and in the current version, run the 
following (only once): 
apport-collect BUGNUMBER
and upload the updated logs and and any other logs that are relevant for this 
particular issue.  

Thank you again for helping make Ubuntu better. 
G
[Ubuntu Bug Squad volunteer triager]

** Changed in: system-config-printer (Ubuntu)
   Status: New => Incomplete

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

Title:
  udev-configure-printer /invalid or missing IEEE 1284 Device ID

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

Bug description:
  Binary package hint: udev

  Hello,

  I run Kubuntu Karmic 64 bits, on x86 64 and in my log i found a error
  about Udev.

  2009-10-24 09:47:34   udev-configure-printer  invalid or missing IEEE 1284 
Device ID
  2009-10-24 09:47:34   udev-configure-printer  Failed to get parent

  Best Regards

  ProblemType: Bug
  Architecture: amd64
  Date: Sat Oct 24 11:16:42 2009
  DistroRelease: Ubuntu 9.10
  MachineType: System manufacturer P5Q-E
  NonfreeKernelModules: nvidia
  Package: udev 147~-6
  ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.31-14-generic 
root=UUID=7e3e1cb1-a36d-4ad9-a5ce-5cc33e2d2ca5 ro quiet splash
  ProcEnviron:
   LANGUAGE=
   LANG=fr_CH.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
  SourcePackage: udev
  Uname: Linux 2.6.31-14-generic x86_64
  XsessionErrors:
   (polkit-gnome-authentication-agent-1:2995): GLib-CRITICAL **: 
g_once_init_leave: assertion `initialization_value != 0' failed
   (npviewer.bin:6107): Gtk-WARNING **: 
/usr/lib/gtk-2.0/2.10.0/engines/libqtcurve.so: mauvaise classe ELF: ELFCLASS64
  dmi.bios.date: 02/25/2009
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2001
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5Q-E
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2001:bd02/25/2009:svnSystemmanufacturer:pnP5Q-E:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5Q-E:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: P5Q-E
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/system-config-printer/+bug/459648/+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 1793937] Re: package libgles1 (not installed) failed to install/upgrade: trying to overwrite '/usr/lib/x86_64-linux-gnu/libGLESv1_CM.so.1', which is also in package nvidia-340

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

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

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

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

Title:
  package libgles1 (not installed) failed to install/upgrade: trying to
  overwrite '/usr/lib/x86_64-linux-gnu/libGLESv1_CM.so.1', which is also
  in package nvidia-340 340.106-0ubuntu3

Status in libglvnd package in Ubuntu:
  Confirmed

Bug description:
  Failure in the update process

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: libgles1 (not installed)
  ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18
  Uname: Linux 4.15.0-34-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  Date: Sun Sep 23 10:38:02 2018
  DuplicateSignature:
   package:libgles1:(not installed)
   Unpacking libglvnd-dev:amd64 (1.0.0-2ubuntu2.2) over (1.0.0-2ubuntu2.1) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-3RAkNn/20-libglvnd-dev_1.0.0-2ubuntu2.2_amd64.deb 
(--unpack):
trying to overwrite '/usr/lib/x86_64-linux-gnu/libGLESv1_CM.so', which is 
also in package nvidia-340 340.106-0ubuntu3
  ErrorMessage: trying to overwrite 
'/usr/lib/x86_64-linux-gnu/libGLESv1_CM.so.1', which is also in package 
nvidia-340 340.106-0ubuntu3
  InstallationDate: Installed on 2016-12-05 (656 days ago)
  InstallationMedia: Lubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.1)
  Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 
3.6.5-3ubuntu1
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.3ubuntu0.1
  SourcePackage: libglvnd
  Title: package libgles1 (not installed) failed to install/upgrade: trying to 
overwrite '/usr/lib/x86_64-linux-gnu/libGLESv1_CM.so.1', which is also in 
package nvidia-340 340.106-0ubuntu3
  UpgradeStatus: Upgraded to bionic on 2018-05-01 (144 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libglvnd/+bug/1793937/+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 499931] Re: system-config-printer-udev disables HP printers, again

Hello Alex,
Thank you for submitting this bug and reporting a problem with 
system-config-printer.  You made this bug report some time ago and Ubuntu has 
been updated since then. 
 
Could you confirm that this is no longer a problem and that we can close the 
bug report? 
If it is still a problem, are you still interested in finding a solution to 
this bug? 
If you are, could you let us know, and in the current version, run the 
following (only once): 
apport-collect BUGNUMBER
and upload the updated logs and and any other logs that are relevant for this 
particular issue.  

Thank you again for helping make Ubuntu better. 
G
[Ubuntu Bug Squad volunteer triager]

** Changed in: system-config-printer (Ubuntu)
   Status: New => Incomplete

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

Title:
  system-config-printer-udev disables HP printers, again

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

Bug description:
  Binary package hint: system-config-printer-udev

  Some time ago I filed a bug about HP printers and hal-cups-utils. I've
  been asked to use system-config-printer-udev instead of hal-cups-
  utils: https://bugs.launchpad.net/ubuntu/+source/hal-cups-
  utils/+bug/439652. Now I'm using system-config-printer-udev on my
  Debian Lenny box taken from Karmic (1.1.12+git20090826-0ubuntu8) and
  recompiled in Lenny environment. HPLIP is from Sid, version 3.9.10-4.
  The problem is the same - I've connected OfficeJet 3600, it has been
  recognized and added by system-config-printer-udev but in "stopped"
  state:

  $ lshal | grep printer.
info.product = 'Standard LPT printer port'  (string)
pnp.description = 'Standard LPT printer port'  (string)
  udi = 
'/org/freedesktop/Hal/devices/usb_device_3f0_3112_CN97L4P08W053D_if1_printer_CN97L4P08W053D'
info.capabilities = {'printer'} (string list)
info.category = 'printer'  (string)
info.udi = 
'/org/freedesktop/Hal/devices/usb_device_3f0_3112_CN97L4P08W053D_if1_printer_CN97L4P08W053D'
  (string)
printer.commandset = {'LDL', 'MLC', 'PML', 'DYN'} (string list)
printer.device = '/dev/usb/lp0'  (string)
printer.originating_device = 
'/org/freedesktop/Hal/devices/usb_device_3f0_3112_CN97L4P08W053D_if1'  (string)
printer.product = 'Officejet J3600 series'  (string)
printer.serial = 'CN97L4P08W053D'  (string)
printer.vendor = 'HP'  (string)

  $ cups-printers
  ...
  Found printer "Officejet-J3600-series", "(null)"
  Option "auth-info-required"="none"
  Option "copies"="1"
  Option 
"device-uri"="hp:/usb/Officejet_J3600_series?serial=CN97L4P08W053D"
  Option "finishings"="3"
  Option "job-hold-until"="no-hold"
  Option "job-priority"="50"
  Option "job-sheets"="none,none"
  Option "marker-change-time"="0"
  Option "media"="A4"
  Option "number-up"="1"
  Option "printer-info"="HP Officejet J3600 series"
  Option "printer-is-accepting-jobs"="true"
  Option "printer-is-shared"="true"
  Option "printer-location"="dbs"
  Option "printer-make-and-model"="HP Officejet j3600 series 
Foomatic/hpijs, hpijs 2.8.6b"
  Option "printer-state"="3"
  Option "printer-state-change-time"="1261229036"
  Option "printer-state-reasons"="none"
  Option "printer-type"="4108"
  Option 
"printer-uri-supported"="ipp://localhost:631/printers/Officejet-J3600-series"

  I've enabled it manually with cupsenable, but when I removed it from
  USB port, system-config-printer-udev didn't remove it from CUPS
  database, /etc/cups/printers.conf still contains a record for this
  printer (and it is marked as "online"):

  $ cat /etc/cups/printers.conf
  # Printer configuration file for CUPS v1.3.8
  # Written by cupsd on 2009-12-19 08:23
  ...
  
  Info HP Officejet J3600 series
  Location dbs
  DeviceURI hp:/usb/Officejet_J3600_series?serial=CN97L4P08W053D
  State Idle
  StateTime 1261229036
  Accepting Yes
  Shared Yes
  JobSheets none none
  QuotaPeriod 0
  PageLimit 0
  KLimit 0
  OpPolicy default
  ErrorPolicy stop-printer
  

  $ cups-printers
  ...
  Found printer "Officejet-J3600-series", "(null)"
  Option "auth-info-required"="none"
  Option "copies"="1"
  Option 
"device-uri"="hp:/usb/Officejet_J3600_series?serial=CN97L4P08W053D"
  Option "finishings"="3"
  Option "job-hold-until"="no-hold"
  Option "job-priority"="50"
  Option "job-sheets"="none,none"
  Option "marker-change-time"="0"
  Option "media"="A4"
  Option "number-up"="1"
  Option "printer-info"="HP Officejet J3600 series"
  Option "printer-is-accepting-jobs"="true"
  Option "printer-is-shar

[Desktop-packages] [Bug 493936] Re: unable to connect to windows printers with non-ascii names

Hello Simon,
Thank you for submitting this bug and reporting a problem with 
system-config-printer.  You made this bug report some time ago and Ubuntu has 
been updated since then. 
 
Could you confirm that this is no longer a problem and that we can close the 
bug report? 
If it is still a problem, are you still interested in finding a solution to 
this bug? 
If you are, could you let us know, and in the current version, run the 
following (only once): 
apport-collect BUGNUMBER
and upload the updated logs and and any other logs that are relevant for this 
particular issue.  

Thank you again for helping make Ubuntu better. 
G
[Ubuntu Bug Squad volunteer triager]

** Changed in: system-config-printer (Ubuntu)
   Status: New => Incomplete

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

Title:
  unable to connect to windows printers with non-ascii names

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

Bug description:
  Binary package hint: system-config-printer

  I can't connect to a windows (samba) printer queue whose name contains
  chinese characters.  My printer is called '5F網資室'.

  If I give the full name and path to the queue using the unicode
  charactes, system-config-printer dumps this to the console, and then
  just stalls forever:

  /usr/lib/python2.6/urllib.py:1223: UnicodeWarning: Unicode equal comparison 
failed to convert both arguments to Unicode - interpreting them as being unequal
res = map(safe_map.__getitem__, s)
  Traceback (most recent call last):
File "/usr/share/system-config-printer/system-config-printer.py", line 
4185, in on_btnNPForward_clicked
  self.nextNPTab()
File "/usr/share/system-config-printer/system-config-printer.py", line 
4203, in nextNPTab
  uri = SMBURI (uri=uri[6:]).sanitize_uri ()
File "/usr/share/system-config-printer/smburi.py", line 69, in sanitize_uri
  return self._construct (group, host, share)
File "/usr/share/system-config-printer/smburi.py", line 61, in _construct
  uri += "/" + _urlquote (share)
File "/usr/share/system-config-printer/smburi.py", line 26, in _urlquote
  q = urllib.quote (x)
File "/usr/lib/python2.6/urllib.py", line 1223, in quote
  res = map(safe_map.__getitem__, s)
  KeyError: u'\xe7'

  If I escape the name (i.e. "5F%E7%B6%B2%E8%B3%87%E5%AE%A4"), the error
  is the same, but the UnicodeWarning is not generated first.

  ProblemType: Bug
  Architecture: amd64
  CupsErrorLog:
   W [08/Dec/2009:15:20:02 +0800] [CGI] Unhandled message: 
interface=org.freedesktop.DBus.Introspectable, path=/, member=Introspect
   E [08/Dec/2009:15:20:17 +0800] [cups-driverd] Bad driver information file 
"/usr/share/cups/drv/sample.drv"!
   W [08/Dec/2009:15:27:09 +0800] [CGI] Unhandled message: 
interface=org.freedesktop.DBus.Introspectable, path=/, member=Introspect
   E [08/Dec/2009:15:27:25 +0800] [cups-driverd] Bad driver information file 
"/usr/share/cups/drv/sample.drv"!
  Date: Tue Dec  8 15:32:59 2009
  DistroRelease: Ubuntu 9.10
  InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
  Lpstat: device for HP-Color-LaserJet-1600: socket://172.30.101.245:9100
  MachineType: ASUSTeK Computer Inc. A8Fm
  Package: system-config-printer-common 1.1.12+git20090826-0ubuntu8
  PackageArchitecture: all
  Papersize: letter
  PpdFiles: HP-Color-LaserJet-1600: HP Color LaserJet 1600 Foomatic/foo2hp 
(recommended)
  ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.31-16-generic 
root=UUID=19e942df-bcab-41c0-9b76-eb0aca07f7c7 ro splash nomodeset quiet splash
  ProcEnviron:
   LANGUAGE=en_GB.UTF-8
   PATH=(custom, user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.31-16.52-generic
  SourcePackage: system-config-printer
  Uname: Linux 2.6.31-16-generic x86_64
  dmi.bios.date: 04/08/2008
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: A8FmAS.212
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: A8Fm
  dmi.board.vendor: ASUSTeK Computer Inc.
  dmi.board.version: 1.0
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK Computer Inc.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrA8FmAS.212:bd04/08/2008:svnASUSTeKComputerInc.:pnA8Fm:pvr1.0:rvnASUSTeKComputerInc.:rnA8Fm:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr:
  dmi.product.name: A8Fm
  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/system-config-printer/+bug/493936/+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 484201] Re: URI for JetDirect Works with XSane in 1.05(Intrepid) doesn't work in 1.1.12(Karmic)

Hello B. Brown,
Thank you for submitting this bug and reporting a problem with 
system-config-printer.  You made this bug report some time ago and Ubuntu has 
been updated since then. 
 
Could you confirm that this is no longer a problem and that we can close the 
bug report? 
If it is still a problem, are you still interested in finding a solution to 
this bug? 
If you are, could you let us know, and in the current version, run the 
following (only once): 
apport-collect BUGNUMBER
and upload the updated logs and and any other logs that are relevant for this 
particular issue.  

Thank you again for helping make Ubuntu better. 
G
[Ubuntu Bug Squad volunteer triager]

** Changed in: system-config-printer (Ubuntu)
   Status: New => Incomplete

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

Title:
  URI for JetDirect Works with XSane in 1.05(Intrepid) doesn't work in
  1.1.12(Karmic)

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

Bug description:
  Binary package hint: system-config-printer

  When I install my HP multi-function OfficeJet 7310 under Intrepid/8.10 with 
system-install-printer 1.0.5, the URI used for the printer is:
hp:/net/Officejet_7300_series?ip=THEPRINTER'SIPADDR

  When I install the same printer under Karmic/9.10 with system-install-printer 
1.1.12, the URI used for the printer is:
socket://THEPRINTERNAME:9100

  Both of these URI's work from the point of view of printing.  But, the
  new socket-based URI does not work with XSane.  So, XSane does not
  recognize the mult-function printer as capable of scanning with the
  use of the socket-based URI.

  There may be reasons for this change of which I am not aware.  But,
  for me, it meant that I had to dig into the config of the printer to
  try to figure out why things "just worked" in Intrepid(which is
  marvelous) and now, under Karmic, they don't.  I was lucky enough to
  recognize the difference in the config and try the "hp" URI on Karmic.
  A printer expert I am certainly not.

  With a change to the "hp-based" URI, all is now working on Karmic.
  So, there is certainly a work around.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/system-config-printer/+bug/484201/+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 1791542] Re: package libglvnd-dev 1.0.0-2ubuntu2.1 failed to upgrade: trying to overwrite '/usr/lib/x86_64-linux-gnu/libGLESv1_CM.so', which is also in package nvidia-340 340.1

2018-09-24 Thread BSA

2 errors (warnings) while install:

dpkg: error: version '-' has bad syntax: revision number is empty
dpkg: error: version '-' has bad syntax: revision number is empty

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

Title:
  package libglvnd-dev 1.0.0-2ubuntu2.1 failed to upgrade: trying to
  overwrite '/usr/lib/x86_64-linux-gnu/libGLESv1_CM.so', which is also
  in package nvidia-340 340.107-0ubuntu0~gpu18.04.1

Status in libglvnd package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Fix Released
Status in libglvnd source package in Bionic:
  Confirmed
Status in nvidia-graphics-drivers-340 source package in Bionic:
  Fix Committed

Bug description:
  SRU Request:

  [Impact]

  The new libgles1 conflicts with nvidia-340 which ships it's own copy
  of libGLESv1_CM.so

  [Test case]

  Enable proposed, install libgles1 and nvidia-340, they should install
  fine.

  [Regression potential]

  none, just fixes a file conflict

  --

  Looks like I had a similar problem on 18.04.1 than
  https://bugs.launchpad.net/ubuntu/+source/libglvnd/+bug/1728352, just
  with nvidia-340 from https://launchpad.net/~graphics-
  drivers/+archive/ubuntu/ppa .

  Apt output:
  ```
  $ sudo apt dist-upgrade
  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  Calculating upgrade... Done
  The following NEW packages will be installed:
    libgles1
  The following packages will be upgraded:
    libegl1 libgl1 libgles2 libglvnd-core-dev libglvnd-dev libglvnd0 libglx0 
libopengl0
  8 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
  Need to get 268 kB of archives.
  After this operation, 66,6 kB of additional disk space will be used.
  Do you want to continue? [Y/n]
  Get:1 http://archive.ubuntu.com/ubuntu bionic-proposed/main amd64 
libglvnd-dev amd64 1.0.0-2ubuntu2.2 [3 408 B]
  Get:2 http://archive.ubuntu.com/ubuntu bionic-proposed/main amd64 
libglvnd-core-dev amd64 1.0.0-2ubuntu2.2 [12,9 kB]
  Get:3 http://archive.ubuntu.com/ubuntu bionic-proposed/main amd64 libgles2 
amd64 1.0.0-2ubuntu2.2 [17,4 kB]
  Get:4 http://archive.ubuntu.com/ubuntu bionic-proposed/main amd64 libgl1 
amd64 1.0.0-2ubuntu2.2 [84,8 kB]
  Get:5 http://archive.ubuntu.com/ubuntu bionic-proposed/main amd64 libglx0 
amd64 1.0.0-2ubuntu2.2 [28,1 kB]
  Get:6 http://archive.ubuntu.com/ubuntu bionic-proposed/main amd64 libopengl0 
amd64 1.0.0-2ubuntu2.2 [31,3 kB]
  Get:7 http://archive.ubuntu.com/ubuntu bionic-proposed/main amd64 libegl1 
amd64 1.0.0-2ubuntu2.2 [31,9 kB]
  Get:8 http://archive.ubuntu.com/ubuntu bionic-proposed/main amd64 libglvnd0 
amd64 1.0.0-2ubuntu2.2 [46,6 kB]
  Get:9 http://archive.ubuntu.com/ubuntu bionic-proposed/main amd64 libgles1 
amd64 1.0.0-2ubuntu2.2 [11,2 kB]
  Fetched 268 kB in 0s (1 575 kB/s)
  (Reading database ... 141610 files and directories currently installed.)
  Preparing to unpack .../0-libglvnd-dev_1.0.0-2ubuntu2.2_amd64.deb ...
  Unpacking libglvnd-dev:amd64 (1.0.0-2ubuntu2.2) over (1.0.0-2ubuntu2.1) ...
  dpkg: error processing archive 
/tmp/apt-dpkg-install-Gq7kQI/0-libglvnd-dev_1.0.0-2ubuntu2.2_amd64.deb 
(--unpack):
   trying to overwrite '/usr/lib/x86_64-linux-gnu/libGLESv1_CM.so', which is 
also in package nvidia-340 340.107-0ubuntu0~gpu18.04.1
  Preparing to unpack .../1-libglvnd-core-dev_1.0.0-2ubuntu2.2_amd64.deb ...
  Unpacking libglvnd-core-dev:amd64 (1.0.0-2ubuntu2.2) over (1.0.0-2ubuntu2.1) 
...
  Preparing to unpack .../2-libgles2_1.0.0-2ubuntu2.2_amd64.deb ...
  Unpacking libgles2:amd64 (1.0.0-2ubuntu2.2) over (1.0.0-2ubuntu2.1) ...
  Preparing to unpack .../3-libgl1_1.0.0-2ubuntu2.2_amd64.deb ...
  Unpacking libgl1:amd64 (1.0.0-2ubuntu2.2) over (1.0.0-2ubuntu2.1) ...
  Preparing to unpack .../4-libglx0_1.0.0-2ubuntu2.2_amd64.deb ...
  Unpacking libglx0:amd64 (1.0.0-2ubuntu2.2) over (1.0.0-2ubuntu2.1) ...
  Preparing to unpack .../5-libopengl0_1.0.0-2ubuntu2.2_amd64.deb ...
  Unpacking libopengl0:amd64 (1.0.0-2ubuntu2.2) over (1.0.0-2ubuntu2.1) ...
  Preparing to unpack .../6-libegl1_1.0.0-2ubuntu2.2_amd64.deb ...
  Unpacking libegl1:amd64 (1.0.0-2ubuntu2.2) over (1.0.0-2ubuntu2.1) ...
  Preparing to unpack .../7-libglvnd0_1.0.0-2ubuntu2.2_amd64.deb ...
  Unpacking libglvnd0:amd64 (1.0.0-2ubuntu2.2) over (1.0.0-2ubuntu2.1) ...
  Selecting previously unselected package libgles1:amd64.
  Preparing to unpack .../8-libgles1_1.0.0-2ubuntu2.2_amd64.deb ...
  Unpacking libgles1:amd64 (1.0.0-2ubuntu2.2) ...
  dpkg: error processing archive 
/tmp/apt-dpkg-install-Gq7kQI/8-libgles1_1.0.0-2ubuntu2.2_amd64.deb (--unpack):
   trying to overwrite '/usr/lib/x86_64-linux-gnu/libGLESv1_CM.so.1', which is 
also in package nvidia-340 340.107-0ubuntu0~gpu18.04.1
  Errors were encountered while processing:
   /tmp/apt-dpkg-install-Gq7kQI/0-libglvnd-dev_1.0.0-2ubuntu2.2_amd64.deb
   /tmp/apt-dpkg-instal

[Desktop-packages] [Bug 526601] Re: printer applet does not show other user's jobs

Hello Leandro,
Thank you for submitting this bug and reporting a problem with
system-config-printer. You made this bug report some time ago and Ubuntu has
been updated since then.

Thank you again for helping make Ubuntu better.
G
[Ubuntu Bug Squad volunteer triager]

** Changed in: system-config-printer (Ubuntu)
Status: New => Incomplete

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

Title:
printer applet does not show other user's jobs

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

Bug description:

I share a local printer plugged in my machine through the network. When
I send a job, it appears in the printer-applet (the small printer on the
panel). If someone from the network has sent a job, however, his/her
job does not appear on the list, and my job appears as "Pending". No further
information is obtained on why the job is not being printed. Of course, one
can know that there are other jobs being print using "lpq" from the terminal
or by seeing the localhost:631 site provided by cups.

I think that the printer applet should show the same information provided
by the localhost:631, otherwise one does not know the actual status of
the printer unless we use these other commands which are not
immediately obvious to a new user.

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

[Desktop-packages] [Bug 1792873] Re: FFE: 18.2.x for cosmic

I would like to wait with this until the new 18.2.1 version builds.
Could you perform some upgrade testing on it and leave a comment about
how it went? I'll pick this up tomorrow and we'll decide then.

The LLVM 7 part seems like a separate thing though? Since it still
doesn't seem to be available, I guess it would require another FFe/NEW,
I suppose? Seems a bit bigger, especially so close to release.

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

Title:
  FFE: 18.2.x for cosmic

Status in mesa package in Ubuntu:
  New

Bug description:
  Mesa 18.2.0 was recently released after several delays, but at least
  it doesn't have any known regressions on Intel hw. We tend to get the
  latest major version in the devel series ~2 weeks after FF, but since
  a month has passed now I thought it would be best to file an actual
  FFE request.

  We'd also build it against LLVM 7, which is about to be released.
  Together these provide support for AMD Vega20 (kernel support still
  needed) among other things.

  New features from mesa upstream reldocs:

  OpenGL 4.3 on virgl
  OpenGL 4.4 Compatibility profile on radeonsi
  OpenGL ES 3.2 on radeonsi and virgl
  GL_ARB_ES3_2_compatibility on radeonsi
  GL_ARB_fragment_shader_interlock on i965
  GL_ARB_sample_locations and GL_NV_sample_locations on nvc0 (GM200+)
  GL_ANDROID_extension_pack_es31a on radeonsi.
  GL_KHR_texture_compression_astc_ldr on radeonsi
  GL_NV_conservative_raster and GL_NV_conservative_raster_dilate on nvc0 
(GM200+)
  GL_NV_conservative_raster_pre_snap_triangles on nvc0 (GP102+)
  multisampled images on nvc0 (GM107+) (now supported on GF100+)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1792873/+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 594543] Re: system-config-printer prompts for credentials when adding a new printer

Hello Scottuss,
Thank you for submitting this bug and reporting a problem with 
system-config-printer.  You made this bug report some time ago and Ubuntu has 
been updated since then. 
 
Could you confirm that this is no longer a problem and that we can close the 
bug report? 
If it is still a problem, are you still interested in finding a solution to 
this bug? 
If you are, could you let us know, and in the current version, run the 
following (only once): 
apport-collect BUGNUMBER
and upload the updated logs and and any other logs that are relevant for this 
particular issue.  

Thank you again for helping make Ubuntu better. 
G
[Ubuntu Bug Squad volunteer triager]

** Changed in: system-config-printer (Ubuntu)
   Status: New => Incomplete

** Changed in: system-config-printer (Debian)
   Status: New => Incomplete

** Changed in: system-config-printer
   Status: New => Incomplete

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

Title:
  system-config-printer prompts for credentials when adding a new
  printer

Status in System Config Printer:
  Incomplete
Status in system-config-printer package in Ubuntu:
  Incomplete
Status in system-config-printer package in Debian:
  Incomplete

Bug description:
  Binary package hint: system-config-printer

  When attempting to add a new printer (HP Photosmart 2575)  via system-
  config-printer, I get prompted for what appears to be Samba
  credentials (There is a field for username, password and workgroup)
  The printer does not require these credentials (I have tried different
  combinations, but clearly this prompt should not be displayed, there
  are absolutely no credentials required)

  Adding the printer via the CUPS interface works perfectly, without any
  prompt for non-existent credentials.

To manage notifications about this bug go to:
https://bugs.launchpad.net/system-config-printer/+bug/594543/+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 1503310] Re: window content doesn't refresh, only if window is moved

2018-09-24 Thread Philippe Coval

I see this bug is still unresolved, I am able to replicate the issue on
my current setup:

https://twitter.com/RzrFreeFr/status/1044227788444758016

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

Title:
  window content doesn't refresh, only if window is moved

Status in compiz package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Confirmed

Bug description:
  I suppose this is a bug with the nvidia driver, but I'm not sure.
  After the second-to-last routine software update (which I think
  updated the nvidia driver), changing window content is only refreshed
  if the window is moved.

  Ubuntu 12.04.5 LTS, kernel 3.2.0-91-generic,
  NVidia driver installed: 340.93-0ubuntu0.0.0.1,
  Thinkpad laptop with nvidia graphics card (see below),
  Window manager: Gnome Classic

  How to reproduce the bug: Log in under Gnome Classic. Open Gnome
  terminal. Execute some command (ls). Open new tab in terminal. Execute
  some other command (ps), just to have different tab contents. Switch
  back and forth between the tabs using the mouse. After some switches,
  neither the tab rider is activated nor the tab content is refreshed
  any longer. Only if you move the window, the tab rider gets activated
  and the tab content is refreshed. The same problem occurs in other
  applications (e.g. in thunderbird when selecting an email --- email
  list entry is not marked and email content is not shown, only if you
  move the window), so it is not application-specific.

  The bug disappears when using the window manager "Gnome Classic (no
  effects)" instead (which is "non-compositing" in contrast to "Gnome
  Classic"). The bug is also present in other window magagers
  ("Ubuntu").

  Side remark: I tried but failed to switch back to an earlier version
  of the nvidia driver (from 340 to 331) using synaptic: When
  deinstalling 340 and installing 331 instead, synaptic complains that
  it depends on 340. So I can only guess that the bug is caused by the
  nvidia driver.

  Any help would be highly appreciated as the bug is really annoying.

  % nvidia-smi 
  Tue Oct  6 16:13:30 2015   
  +--+  
 
  | NVIDIA-SMI 340.93 Driver Version: 340.93 |  
 
  
|---+--+--+
  | GPU  NamePersistence-M| Bus-IdDisp.A | Volatile Uncorr. ECC 
|
  | Fan  Temp  Perf  Pwr:Usage/Cap| Memory-Usage | GPU-Util  Compute M. 
|
  
|===+==+==|
  |   0  NVS 5400M   Off  | :01:00.0 N/A |  N/A 
|
  | N/A   44CP8N/A /  N/A |194MiB /  1023MiB | N/A  Default 
|
  
+---+--+--+

 
  
+-+
  | Compute processes:   GPU Memory 
|
  |  GPU   PID  Process name Usage  
|
  
|=|
  |0Not Supported   
|
  
+-+

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: nvidia-340 340.93-0ubuntu0.0.0.1
  ProcVersionSignature: Ubuntu 3.2.0-91.129-generic 3.2.71
  Uname: Linux 3.2.0-91-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.0.1-0ubuntu17.11
  Architecture: amd64
  Date: Tue Oct  6 16:10:32 2015
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=C
   SHELL=/bin/tcsh
  SourcePackage: nvidia-graphics-drivers-340
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/1503310/+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 1791670] [NEW] back button not working in software center ubuntu 18.04

You have been subscribed to a public bug:

in ubuntu software after installing any app the back button is not
working. i cannot go back.

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

-- 
back button not working in software center ubuntu 18.04
https://bugs.launchpad.net/bugs/1791670
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to gnome-software 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 1791670] Re: back button not working in software center ubuntu 18.04

2018-09-24 Thread Matthew Paul Thomas

** Package changed: software-center (Ubuntu) => gnome-software (Ubuntu)

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

Title:
  back button not working in software center ubuntu 18.04

Status in gnome-software package in Ubuntu:
  Incomplete

Bug description:
  in ubuntu software after installing any app the back button is not
  working. i cannot go back.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1791670/+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 1791670] Re: back button not working in software center ubuntu 18.04

I cannot reproduce the issue, neither in bionic nor in cosmic.

Please provide more information about your setup by running the
following command in a terminal:

apport-collect 1791670

Please also elaborate on what steps are needed to observe the problem.
Thanks!

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

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

Title:
  back button not working in software center ubuntu 18.04

Status in gnome-software package in Ubuntu:
  Incomplete

Bug description:
  in ubuntu software after installing any app the back button is not
  working. i cannot go back.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1791670/+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 1794139] [NEW] At random times, no warning when closing a file after it's been deleted

2018-09-24 Thread teo1978

Public bug reported:

See https://gitlab.gnome.org/GNOME/gedit/issues/73#note_331812

Closed upstream because gedit version too old.

It seem I never get it right. When I report an issue here I get told to
report it upstream, and viceversa.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: gedit 3.18.3-0ubuntu4
ProcVersionSignature: Ubuntu 4.4.0-135.161-generic 4.4.140
Uname: Linux 4.4.0-135-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: amd64
CurrentDesktop: Unity
Date: Mon Sep 24 17:46:45 2018
InstallationDate: Installed on 2013-10-11 (1808 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
SourcePackage: gedit
UpgradeStatus: No upgrade log present (probably fresh install)

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


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

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

Title:
  At random times, no warning when closing a file after it's been
  deleted

Status in gedit package in Ubuntu:
  New

Bug description:
  See https://gitlab.gnome.org/GNOME/gedit/issues/73#note_331812

  Closed upstream because gedit version too old.

  It seem I never get it right. When I report an issue here I get told
  to report it upstream, and viceversa.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gedit 3.18.3-0ubuntu4
  ProcVersionSignature: Ubuntu 4.4.0-135.161-generic 4.4.140
  Uname: Linux 4.4.0-135-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Sep 24 17:46:45 2018
  InstallationDate: Installed on 2013-10-11 (1808 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  SourcePackage: gedit
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1794139/+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 1681249] Re: tracker-extract crashed with signal 31 in chdir()

2018-09-24 Thread Piotr Kołaczkowski

It is happening for me in Ubuntu 18.10.

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

Title:
  tracker-extract crashed with signal 31 in chdir()

Status in tracker package in Ubuntu:
  Confirmed

Bug description:
  tracker crash while indexing my homedir

  ProblemType: Crash
  DistroRelease: Ubuntu 17.04
  Package: tracker-extract 1.12.0-0ubuntu1
  Uname: Linux 4.10.8-041008-generic x86_64
  ApportVersion: 2.20.4-0ubuntu3
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Sat Apr  8 14:00:45 2017
  EcryptfsInUse: Yes
  ExecutablePath: /usr/lib/tracker/tracker-extract
  ExecutableTimestamp: 1490023113
  JournalErrors:
   No journal files were found.
   -- No entries --
  ProcCmdline: /usr/lib/tracker/tracker-extract
  ProcCwd: /home/bonnaudl
  Signal: 31
  SourcePackage: tracker
  Title: tracker-extract crashed with signal 31 in chdir()
  UpgradeStatus: Upgraded to zesty on 2017-04-08 (0 days ago)
  UserGroups: adm cdrom dip fuse libvirt libvirtd lpadmin plugdev sambashare 
staff sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tracker/+bug/1681249/+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 1794146] Re: package ibus 1.5.17-3ubuntu4 failed to install/upgrade: installed ibus package pre-removal script subprocess returned error exit status 127

2018-09-24 Thread Apport retracing service

** Tags removed: need-duplicate-check

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

Title:
  package ibus 1.5.17-3ubuntu4 failed to install/upgrade: installed ibus
  package pre-removal script subprocess returned error exit status 127

Status in ibus package in Ubuntu:
  New

Bug description:
  error displays on login through xrdp using xfce4 desktop

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: ibus 1.5.17-3ubuntu4
  ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18
  Uname: Linux 4.15.0-34-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.3
  Architecture: amd64
  Date: Thu Sep 20 13:27:41 2018
  DuplicateSignature:
   package:ibus:1.5.17-3ubuntu4
   Removing ibus (1.5.17-3ubuntu4) ...
   /var/lib/dpkg/info/ibus.prerm: 7: /var/lib/dpkg/info/ibus.prerm: dconf: not 
found
   dpkg: error processing package ibus (--remove):
installed ibus package pre-removal script subprocess returned error exit 
status 127
  ErrorMessage: installed ibus package pre-removal script subprocess returned 
error exit status 127
  Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 
3.6.5-3ubuntu1
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.3ubuntu0.1
  SourcePackage: ibus
  Title: package ibus 1.5.17-3ubuntu4 failed to install/upgrade: installed ibus 
package pre-removal script subprocess returned error exit status 127
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1794146/+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 1794146] [NEW] package ibus 1.5.17-3ubuntu4 failed to install/upgrade: installed ibus package pre-removal script subprocess returned error exit status 127

2018-09-24 Thread Jack Gronke

Public bug reported:

error displays on login through xrdp using xfce4 desktop

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: ibus 1.5.17-3ubuntu4
ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18
Uname: Linux 4.15.0-34-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.3
Architecture: amd64
Date: Thu Sep 20 13:27:41 2018
DuplicateSignature:
 package:ibus:1.5.17-3ubuntu4
 Removing ibus (1.5.17-3ubuntu4) ...
 /var/lib/dpkg/info/ibus.prerm: 7: /var/lib/dpkg/info/ibus.prerm: dconf: not 
found
 dpkg: error processing package ibus (--remove):
  installed ibus package pre-removal script subprocess returned error exit 
status 127
ErrorMessage: installed ibus package pre-removal script subprocess returned 
error exit status 127
Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 
3.6.5-3ubuntu1
PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu2
 apt  1.6.3ubuntu0.1
SourcePackage: ibus
Title: package ibus 1.5.17-3ubuntu4 failed to install/upgrade: installed ibus 
package pre-removal script subprocess returned error exit status 127
UpgradeStatus: No upgrade log present (probably fresh install)

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


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

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

Title:
  package ibus 1.5.17-3ubuntu4 failed to install/upgrade: installed ibus
  package pre-removal script subprocess returned error exit status 127

Status in ibus package in Ubuntu:
  New

Bug description:
  error displays on login through xrdp using xfce4 desktop

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: ibus 1.5.17-3ubuntu4
  ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18
  Uname: Linux 4.15.0-34-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.3
  Architecture: amd64
  Date: Thu Sep 20 13:27:41 2018
  DuplicateSignature:
   package:ibus:1.5.17-3ubuntu4
   Removing ibus (1.5.17-3ubuntu4) ...
   /var/lib/dpkg/info/ibus.prerm: 7: /var/lib/dpkg/info/ibus.prerm: dconf: not 
found
   dpkg: error processing package ibus (--remove):
installed ibus package pre-removal script subprocess returned error exit 
status 127
  ErrorMessage: installed ibus package pre-removal script subprocess returned 
error exit status 127
  Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 
3.6.5-3ubuntu1
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.3ubuntu0.1
  SourcePackage: ibus
  Title: package ibus 1.5.17-3ubuntu4 failed to install/upgrade: installed ibus 
package pre-removal script subprocess returned error exit status 127
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1794146/+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 1793968] Re: Broken plugins

2018-09-24 Thread Victor Porton

The screenshot (without any menu to switch plugins) after turning the
Alternative Toolbar plugin off.

There is now no way to switch plugins.

** Attachment added: "The screenshot (without any menu to switch plugins) after 
turning the Alternative Toolbar plugin off"
   
https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1793968/+attachment/5192522/+files/Screenshot%20from%202018-09-24%2019-35-47.png

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

Title:
  Broken plugins

Status in rhythmbox package in Ubuntu:
  New

Bug description:
  Rhythmbox on Ubuntu goes with "Alternative Toolbar" enabled by
  default.

  This alternative toolbar is missing volume control!

  I disabled this plugin and now after I restarted Rhythmbox, I see no
  menu (and so no "Plugins" menu item to change it further).

  Sorry that I reported two bugs in one, but they need to be fixed
  together.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: rhythmbox 3.4.2-4ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18
  Uname: Linux 4.15.0-34-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Sep 23 18:06:07 2018
  InstallationDate: Installed on 2018-06-23 (91 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IL
   SHELL=/bin/bash
  SourcePackage: rhythmbox
  UpgradeStatus: No upgrade log present (probably fresh install)
  XorgLog: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log'

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1793968/+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 1794148] [NEW] Rebooting / booting and battery charging

2018-09-24 Thread hpk...@gmail.com

Public bug reported:

charging only to 85% and booting up slow after several trials.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18
Uname: Linux 4.15.0-34-generic x86_64
NonfreeKernelModules: wl
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.9-0ubuntu7.3
Architecture: amd64
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Mon Sep 24 12:38:18 2018
DistUpgraded: 2018-09-23 21:15:55,906 DEBUG icon theme changed, re-reading
DistroCodename: bionic
DistroVariant: ubuntu
DkmsStatus:
 bcmwl, 6.30.223.271+bdcom, 4.15.0-34-generic, x86_64: installed
 bcmwl, 6.30.223.271+bdcom, 4.4.0-135-generic, x86_64: installed
ExtraDebuggingInterest: Yes, including running git bisection searches
GraphicsCard:
 Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a26] (rev 
09) (prog-if 00 [VGA controller])
   Subsystem: Apple Inc. Haswell-ULT Integrated Graphics Controller [106b:011b]
InstallationDate: Installed on 2018-09-23 (0 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
MachineType: Apple Inc. MacBookAir6,2
ProcEnviron:
 LANGUAGE=en_US
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-34-generic 
root=UUID=4add3271-ffc7-4961-97a0-f796b33a7d0f ro drm.debug=0xe plymouth:debug 
nopat vesafb.invalid=1
SourcePackage: xorg
UpgradeStatus: Upgraded to bionic on 2018-09-24 (0 days ago)
dmi.bios.date: 04/11/2018
dmi.bios.vendor: Apple Inc.
dmi.bios.version: MBA61.88Z.0107.B00.180437
dmi.board.asset.tag: Base Board Asset Tag#
dmi.board.name: Mac-7DF21CB3ED6977E5
dmi.board.vendor: Apple Inc.
dmi.board.version: MacBookAir6,2
dmi.chassis.type: 10
dmi.chassis.vendor: Apple Inc.
dmi.chassis.version: Mac-7DF21CB3ED6977E5
dmi.modalias: 
dmi:bvnAppleInc.:bvrMBA61.88Z.0107.B00.180437:bd04/11/2018:svnAppleInc.:pnMacBookAir6,2:pvr1.0:rvnAppleInc.:rnMac-7DF21CB3ED6977E5:rvrMacBookAir6,2:cvnAppleInc.:ct10:cvrMac-7DF21CB3ED6977E5:
dmi.product.family: MacBook Air
dmi.product.name: MacBookAir6,2
dmi.product.version: 1.0
dmi.sys.vendor: Apple Inc.
version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
version.libdrm2: libdrm2 2.4.91-2
version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
xserver.bootTime: Mon Sep 24 12:33:15 2018
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.19.6-1ubuntu4
xserver.video_driver: modeset

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


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

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

Title:
  Rebooting / booting and battery charging

Status in xorg package in Ubuntu:
  New

Bug description:
  charging only to 85% and booting up slow after several trials.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18
  Uname: Linux 4.15.0-34-generic x86_64
  NonfreeKernelModules: wl
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.3
  Architecture: amd64
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Mon Sep 24 12:38:18 2018
  DistUpgraded: 2018-09-23 21:15:55,906 DEBUG icon theme changed, re-reading
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   bcmwl, 6.30.223.271+bdcom, 4.15.0-34-generic, x86_64: installed
   bcmwl, 6.30.223.271+bdcom, 4.4.0-135-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a26] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Apple Inc. Haswell-ULT Integrated Graphics Controller 
[106b:011b]
  InstallationDate: Installed on 2018-09-23 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Apple Inc. MacBookAir6,2
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-34-generic 
root=UUID=4add3271-ffc7-4961-97a0-f796b33a7d0f ro drm.debug=0xe plymouth:debug 
nopat vesafb.invalid=1
  SourcePackage: xorg
  UpgradeStatus: Upgraded to bion

[Desktop-packages] [Bug 1791367] Re: Airplane mode key on Asus ZenBook Flip UX561UD laptop not working in gnome-shell (X or Wayland) but working on console (Cosmic 18.10)

2018-09-24 Thread Mario Vukelic

Thanks, Gunnar. I could not test it yet on the Asus from this bugreport,
it will take a few days until I can get my hands on this one.

However, I tested with my own Dell XPS 15 9575 and it breaks the
Airplane mode switch there, which works perfectly with the standard xkb-
data=2.23.1-1ubuntu1 from Cosmic:

2.23.1-1ubuntu1:
1. Press Fn+Pos1
-> Works. Pop-up says "Airplane mode enabled", icon appears in panel, Wifi and
BT are off.
2. Press Fn+Pos1 again
-> Works. Pop-up says "Airplane mode disabled", icon disappears from panel,
Wifi and BT are on.

Updated 2.24-0ubuntu1, rebooted:
1. Press Fn+Pos1
-> Works same as before. Pop-up says "Airplane mode enabled", icon appears in
panel, Wifi and BT are off.
2. Press Fn+Pos1 again
-> Broken. Pop-up briefly says "Airplane mode disabled", then immediately
changes to "... enabled", icon remains in panel, Wifi and BT remain on.

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

Title:
[FFe]: Airplane mode key on Asus ZenBook Flip UX561UD laptop not
working in gnome-shell (X or Wayland) but working on console (Cosmic
18.10)

Status in xkeyboard-config package in Ubuntu:
Triaged

Bug description:
To the release team: Asking for FFe since it appears to be a good idea
to fix this bug through an upgrade to latest version of xkeyboard-
config rather than just patching a single upstream commit.

Proposal available at https://launchpad.net/~gunnarhj/+archive/ubuntu
/xkeyboard-config

[Original description]

Please forgive if filed for wrong package. Problem occurs in X and
Wayland sessions but not on console, so does not seem to be kernel.

Repro on Asus UX561UD with Ubuntu 18.10 up to date:
1. Log into Gnome X or Gnome Wayland session
2. Press Fn+F2 which is the airplane mode key

-> Airplane mode should turn on but nothing happens

3. Switch to console with Ctrl+Alt+F3
4. Log into console
5. Press Fn+F2 again
6. Switch back to GUI session with Ctrl+Alt+F2

-> Airplane mode is on, icon appeared in Gnome task bar

Same for turning it off.

No difference when booting 18.04.1 live image

This laptop seems not the only one with this problem. I got the idea for
trying the console trick from ArenaL5's answer on Askubuntu, but unfortunately
there is no solution there:
https://askubuntu.com/questions/972367/airplane-mode-switch-does-not-respond

Please let me know whatever I can do to help debug this.

All other Fn+Fx special keys on this laptop work (display brightness,
touchpad off, sound etc.) except for keyboard backlight, but that
works with Ubuntu 18.04.1 and I will file a separate bug for this

ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: xorg 1:7.7+19ubuntu8
ProcVersionSignature: Ubuntu 4.17.0-9.10-generic 4.17.17
Uname: Linux 4.17.0-9-generic x86_64
ApportVersion: 2.20.10-0ubuntu9
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Fri Sep 7 21:37:01 2018
DistUpgraded: Fresh install
DistroCodename: cosmic
DistroVariant: ubuntu
DkmsStatus: nvidia, 390.87, 4.17.0-9-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA
controller])
Subsystem: ASUSTeK Computer Inc. UHD Graphics 620 [1043:14ee]
Subsystem: ASUSTeK Computer Inc. GP107M [GeForce GTX 1050 Mobile]
[1043:14ee]
InstallationDate: Installed on 2018-09-05 (1 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180822)
Lsusb:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 004: ID 8087:0a2b Intel Corp.
Bus 001 Device 003: ID 13d3:5256 IMC Networks
Bus 001 Device 002: ID 8644:800b Intenso GmbG Micro Line (4GB)
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: ASUSTeK COMPUTER INC. UX561UD
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.17.0-9-generic
root=UUID=02bad6b5-ca8f-4184-b477-935995e14bdc ro quiet splash vt.handoff=1
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/06/2018
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: UX561UD.304
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: UX561UD
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 31
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvrUX561UD.304:bd03/06/2018:svnASUSTeKCOMPUTERINC.:pnUX561UD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX561UD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct31:cvr1.0:
dmi.product.family: ZenBook Flip
dmi.product.name: UX561UD
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK C

[Desktop-packages] [Bug 1791367] Re: Airplane mode key on Asus ZenBook Flip UX561UD laptop not working in gnome-shell (X or Wayland) but working on console (Cosmic 18.10)

2018-09-24 Thread Gunnar Hjalmarsson

** Description changed:

+ To the release team: Asking for FFe since it appears to be a good idea
+ to fix this bug through an upgrade to latest version of xkeyboard-config
+ rather than just patching a single upstream commit.
+ 
+ [Original description]
+ 
  Please forgive if filed for wrong package. Problem occurs in X and
  Wayland sessions but not on console, so does not seem to be kernel.
  
  Repro on Asus UX561UD with Ubuntu 18.10 up to date:
  1. Log into Gnome X or Gnome Wayland session
  2. Press Fn+F2 which is the airplane mode key
  
  -> Airplane mode should turn on but nothing happens
  
  3. Switch to console with Ctrl+Alt+F3
  4. Log into console
  5. Press Fn+F2 again
  6. Switch back to GUI session with Ctrl+Alt+F2
  
  -> Airplane mode is on, icon appeared in Gnome task bar
  
  Same for turning it off.
  
  No difference when booting 18.04.1 live image
  
  This laptop seems not the only one with this problem. I got the idea for 
trying the console trick from ArenaL5's answer on Askubuntu, but unfortunately 
there is no solution there:
  https://askubuntu.com/questions/972367/airplane-mode-switch-does-not-respond
  
  Please let me know whatever I can do to help debug this.
  
  All other Fn+Fx special keys on this laptop work (display brightness,
  touchpad off, sound etc.) except for keyboard backlight, but that works
  with Ubuntu 18.04.1 and I will file a separate bug for this
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: xorg 1:7.7+19ubuntu8
  ProcVersionSignature: Ubuntu 4.17.0-9.10-generic 4.17.17
  Uname: Linux 4.17.0-9-generic x86_64
  ApportVersion: 2.20.10-0ubuntu9
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep  7 21:37:01 2018
  DistUpgraded: Fresh install
  DistroCodename: cosmic
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 390.87, 4.17.0-9-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
     Subsystem: ASUSTeK Computer Inc. UHD Graphics 620 [1043:14ee]
     Subsystem: ASUSTeK Computer Inc. GP107M [GeForce GTX 1050 Mobile] 
[1043:14ee]
  InstallationDate: Installed on 2018-09-05 (1 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180822)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0a2b Intel Corp.
   Bus 001 Device 003: ID 13d3:5256 IMC Networks
   Bus 001 Device 002: ID 8644:800b Intenso GmbG Micro Line (4GB)
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. UX561UD
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.17.0-9-generic 
root=UUID=02bad6b5-ca8f-4184-b477-935995e14bdc ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/06/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX561UD.304
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX561UD
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX561UD.304:bd03/06/2018:svnASUSTeKCOMPUTERINC.:pnUX561UD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX561UD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct31:cvr1.0:
  dmi.product.family: ZenBook Flip
  dmi.product.name: UX561UD
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.94-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.1.5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.1.5-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1build1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1build1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3

** Summary changed:

- Airplane mode key on Asus ZenBook Flip UX561UD laptop not working in 
gnome-shell (X or Wayland) but working on console (Cosmic 18.10)
+ [FFe]: Airplane mode key on Asus ZenBook Flip UX561UD laptop not working in 
gnome-shell (X or Wayland) but working on console (Cosmic 18.10)

** Description changed:

  To the release team: Asking for FFe since it appears to be a good idea
  to fix this bug through an upgrade to latest version of xkeyboard-config
  rather than just patching a single upstream commit.
+ 
+ Proposal available at https://launchpad.net/~gunnarhj/+archive/ubuntu
+ /xkeyboard-config
  
  [Original description]
  
  Please forgive if filed for wrong package. Problem occurs in X and
  Wayland sessions but not on console, s

[Desktop-packages] [Bug 1786344] Re: Default IBus input method ignored in live session

2018-09-24 Thread Ping-Wu

Tested 0923 daily built. When booted under the "简体中文" （simplified
Chinese） locale, "汉语“ (Chinese) was shown as the default input method,
but still cannot input Chinese.

There is no option to select "智能拼音" (ibus-libpinyin) when I clicked on
汉语。

To use 智能拼音，I needed to go to "其它“ (Others）then made the selection.
This is very weird to say the least.

However, I think 18.10 looks bright. When this problem is getting
solved, I suggest that, as a default, we check all the dictionaries in
the ibus-libpinyin "dictionary option" ("字典“)。 Many decision makers (in
China at least) determine which Linux distro is better by how fast they
can type. Turning on the dictionaries makes a whole world difference.

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

Title:
Default IBus input method ignored in live session

Status in gnome-settings-daemon package in Ubuntu:
In Progress

Bug description:
Ubuntu 18.10 iso (2018.8.7), select Simplified Chinese for booting, can't
input Chinese character. From Settings -> Regions and Languages, selected
Intelligent Pinyin, also could not input Chinese.

---

18.10 镜像（2018.8.7）选择简体中文开机，无法输入中文。由 Settings -> Regions and
Languages，选择 智能拼音，也无法输入中文。

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

[Desktop-packages] [Bug 1791367] Re: [FFe]: Airplane mode key on Asus ZenBook Flip UX561UD laptop not working in gnome-shell (X or Wayland) but working on console (Cosmic 18.10)

2018-09-24 Thread Mario Vukelic

Sorry for typo in previous comment, should have been OFF at the end:

Updated 2.24-0ubuntu1, rebooted:
1. Press Fn+Pos1
-> Works same as before. Pop-up says "Airplane mode enabled", icon appears in 
panel, Wifi and BT are off.
2. Press Fn+Pos1 again
-> Broken. Pop-up briefly says "Airplane mode disabled", then immediately 
changes to "... enabled", icon remains in panel, Wifi and BT remain *OFF* [not 
"on"]

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

Title:
  [FFe]: Airplane mode key on Asus ZenBook Flip UX561UD laptop not
  working in gnome-shell (X or Wayland) but working on console (Cosmic
  18.10)

Status in xkeyboard-config package in Ubuntu:
  New

Bug description:
  To the release team: Asking for FFe since it appears to be a good idea
  to fix this bug through an upgrade to latest version of xkeyboard-
  config rather than just patching a single upstream commit.

  Proposal available at https://launchpad.net/~gunnarhj/+archive/ubuntu
  /xkeyboard-config

  [Original description]

  Please forgive if filed for wrong package. Problem occurs in X and
  Wayland sessions but not on console, so does not seem to be kernel.

  Repro on Asus UX561UD with Ubuntu 18.10 up to date:
  1. Log into Gnome X or Gnome Wayland session
  2. Press Fn+F2 which is the airplane mode key

  -> Airplane mode should turn on but nothing happens

  3. Switch to console with Ctrl+Alt+F3
  4. Log into console
  5. Press Fn+F2 again
  6. Switch back to GUI session with Ctrl+Alt+F2

  -> Airplane mode is on, icon appeared in Gnome task bar

  Same for turning it off.

  No difference when booting 18.04.1 live image

  This laptop seems not the only one with this problem. I got the idea for 
trying the console trick from ArenaL5's answer on Askubuntu, but unfortunately 
there is no solution there:
  https://askubuntu.com/questions/972367/airplane-mode-switch-does-not-respond

  Please let me know whatever I can do to help debug this.

  All other Fn+Fx special keys on this laptop work (display brightness,
  touchpad off, sound etc.) except for keyboard backlight, but that
  works with Ubuntu 18.04.1 and I will file a separate bug for this

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: xorg 1:7.7+19ubuntu8
  ProcVersionSignature: Ubuntu 4.17.0-9.10-generic 4.17.17
  Uname: Linux 4.17.0-9-generic x86_64
  ApportVersion: 2.20.10-0ubuntu9
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep  7 21:37:01 2018
  DistUpgraded: Fresh install
  DistroCodename: cosmic
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 390.87, 4.17.0-9-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
     Subsystem: ASUSTeK Computer Inc. UHD Graphics 620 [1043:14ee]
     Subsystem: ASUSTeK Computer Inc. GP107M [GeForce GTX 1050 Mobile] 
[1043:14ee]
  InstallationDate: Installed on 2018-09-05 (1 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180822)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0a2b Intel Corp.
   Bus 001 Device 003: ID 13d3:5256 IMC Networks
   Bus 001 Device 002: ID 8644:800b Intenso GmbG Micro Line (4GB)
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. UX561UD
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.17.0-9-generic 
root=UUID=02bad6b5-ca8f-4184-b477-935995e14bdc ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/06/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX561UD.304
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX561UD
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX561UD.304:bd03/06/2018:svnASUSTeKCOMPUTERINC.:pnUX561UD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX561UD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct31:cvr1.0:
  dmi.product.family: ZenBook Flip
  dmi.product.name: UX561UD
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.94-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.1.5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.1.5-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1build1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git

[Desktop-packages] [Bug 1791367] Re: [FFe]: Airplane mode key on Asus ZenBook Flip UX561UD laptop not working in gnome-shell (X or Wayland) but working on console (Cosmic 18.10)

2018-09-24 Thread Gunnar Hjalmarsson

Thanks Mario! That's bad news. Looks like there is more into it then.

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

Title:
  [FFe]: Airplane mode key on Asus ZenBook Flip UX561UD laptop not
  working in gnome-shell (X or Wayland) but working on console (Cosmic
  18.10)

Status in xkeyboard-config package in Ubuntu:
  New

Bug description:
  To the release team: Asking for FFe since it appears to be a good idea
  to fix this bug through an upgrade to latest version of xkeyboard-
  config rather than just patching a single upstream commit.

  Proposal available at https://launchpad.net/~gunnarhj/+archive/ubuntu
  /xkeyboard-config

  [Original description]

  Please forgive if filed for wrong package. Problem occurs in X and
  Wayland sessions but not on console, so does not seem to be kernel.

  Repro on Asus UX561UD with Ubuntu 18.10 up to date:
  1. Log into Gnome X or Gnome Wayland session
  2. Press Fn+F2 which is the airplane mode key

  -> Airplane mode should turn on but nothing happens

  3. Switch to console with Ctrl+Alt+F3
  4. Log into console
  5. Press Fn+F2 again
  6. Switch back to GUI session with Ctrl+Alt+F2

  -> Airplane mode is on, icon appeared in Gnome task bar

  Same for turning it off.

  No difference when booting 18.04.1 live image

  This laptop seems not the only one with this problem. I got the idea for 
trying the console trick from ArenaL5's answer on Askubuntu, but unfortunately 
there is no solution there:
  https://askubuntu.com/questions/972367/airplane-mode-switch-does-not-respond

  Please let me know whatever I can do to help debug this.

  All other Fn+Fx special keys on this laptop work (display brightness,
  touchpad off, sound etc.) except for keyboard backlight, but that
  works with Ubuntu 18.04.1 and I will file a separate bug for this

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: xorg 1:7.7+19ubuntu8
  ProcVersionSignature: Ubuntu 4.17.0-9.10-generic 4.17.17
  Uname: Linux 4.17.0-9-generic x86_64
  ApportVersion: 2.20.10-0ubuntu9
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep  7 21:37:01 2018
  DistUpgraded: Fresh install
  DistroCodename: cosmic
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 390.87, 4.17.0-9-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
     Subsystem: ASUSTeK Computer Inc. UHD Graphics 620 [1043:14ee]
     Subsystem: ASUSTeK Computer Inc. GP107M [GeForce GTX 1050 Mobile] 
[1043:14ee]
  InstallationDate: Installed on 2018-09-05 (1 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180822)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0a2b Intel Corp.
   Bus 001 Device 003: ID 13d3:5256 IMC Networks
   Bus 001 Device 002: ID 8644:800b Intenso GmbG Micro Line (4GB)
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. UX561UD
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.17.0-9-generic 
root=UUID=02bad6b5-ca8f-4184-b477-935995e14bdc ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/06/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX561UD.304
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX561UD
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX561UD.304:bd03/06/2018:svnASUSTeKCOMPUTERINC.:pnUX561UD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX561UD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct31:cvr1.0:
  dmi.product.family: ZenBook Flip
  dmi.product.name: UX561UD
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.94-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.1.5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.1.5-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1build1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1build1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3

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

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

[Desktop-packages] [Bug 1788364] Re: Terminal not working on Ubuntu 18.04

2018-09-24 Thread Luís de Sousa

Hi there,

for those seeking for a solution to this: removing the orca package
permanently solves this issue:

sudo apt purge orca

This has no visible impact on the functioning of the system, just a
slight increase of the overall fluidity of the DE.

Best.

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

Title:
  Terminal not working on Ubuntu 18.04

Status in gnome-terminal package in Ubuntu:
  Confirmed

Bug description:
  On Ubuntu 18.04 the terminal stops functioning after a few hours of
  work. In a fresh session the terminal works as expected, but after
  some time it becomes slow and finally unresponsive. After that, every
  time a new terminal window is launched it is greyed out and must be
  forcibly terminated. No keyboard input is ever shown in the terminal
  window. Things go back to normal if the  DE session is restarted.

  Thank you.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-terminal 3.28.2-1ubuntu1~18.04.1
  ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18
  Uname: Linux 4.15.0-32-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Wed Aug 22 11:04:37 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-11-15 (279 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  SourcePackage: gnome-terminal
  UpgradeStatus: Upgraded to bionic on 2018-08-17 (5 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1788364/+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 1792745] Re: NetworkManager crashed with SIGSEGV in _int_malloc()

2018-09-24 Thread Anders Kaseorg

** Patch added: "rebased on 1.12.2-0ubuntu5"
   
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1792745/+attachment/5192582/+files/network-manager_1.12.2-0ubuntu5_lp1792745.debdiff

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

Title:
  NetworkManager crashed with SIGSEGV in _int_malloc()

Status in NetworkManager:
  Unknown
Status in network-manager package in Ubuntu:
  New

Bug description:
  I’m seeing NetworkManager crash several times on startup and on resume
  from suspend. Apport doesn’t catch those for some reason, but this
  happened when I tried to reproduce by manually running NetworkManager
  --debug.

  (Different crash from bug 1792743?  Also apport-retrace didn’t seem to
  like that one.)

  ProblemType: Crash
  DistroRelease: Ubuntu 18.10
  Package: network-manager 1.12.2-0ubuntu4
  ProcVersionSignature: Ubuntu 4.18.0-7.8-generic 4.18.5
  Uname: Linux 4.18.0-7-generic x86_64
  NonfreeKernelModules: openafs
  ApportVersion: 2.20.10-0ubuntu9
  Architecture: amd64
  Date: Sat Sep 15 14:04:50 2018
  EcryptfsInUse: Yes
  ExecutablePath: /usr/sbin/NetworkManager
  IfupdownConfig: # ifupdown has been replaced by netplan(5) on this system.  
Do not edit.
  InstallationDate: Installed on 2016-02-19 (939 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 
(20160218)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=false
  ProcCmdline: NetworkManager --debug
  SegvAnalysis:
   Segfault happened at: 0x7f79966ea378 <_int_malloc+3352>: cmp
%rcx,0x18(%rdx)
   PC (0x7f79966ea378) ok
   source "%rcx" ok
   destination "0x18(%rdx)" (0x0018) not located in a known VMA region 
(needed writable region)!
  SegvReason: writing NULL VMA
  Signal: 11
  SourcePackage: network-manager
  StacktraceTop:
   _int_malloc (av=av@entry=0x7f799683ac40 , 
bytes=bytes@entry=4096) at malloc.c:4014
   __libc_calloc (n=, elem_size=) at malloc.c:3420
   g_malloc0 () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
   nlmsg_alloc_size (len=4096) at src/platform/nm-netlink.c:314
   _nl80211_alloc_msg (id=28, ifindex=2, phy=0, cmd=cmd@entry=32, 
flags=flags@entry=768) at src/platform/wifi/wifi-utils-nl80211.c:88
  Title: NetworkManager crashed with SIGSEGV in _int_malloc()
  UpgradeStatus: Upgraded to cosmic on 2018-08-17 (29 days ago)
  UserGroups:
   
  nmcli-con: Error: command ['nmcli', '-f', 'all', 'con'] failed with exit code 
8: Error: NetworkManager is not running.
  nmcli-dev: Error: command ['nmcli', '-f', 'all', 'dev'] failed with exit code 
8: Error: NetworkManager is not running.
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'gen'] failed with exit code 
8: Error: NetworkManager is not running.

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager/+bug/1792745/+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 1792085] Re: MTP no more working on Bionic

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

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

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

Title:
  MTP no more working on Bionic

Status in gvfs package in Ubuntu:
  Confirmed

Bug description:
  Hi, unfortunately (for me) MTP android devices no more work on Ubuntu
  18.04.

  I have used MTP on 16.04 without problems, but on 18.04 it does not
  work. When I connect my Android devices (Samsung A5 and Samsung J3)
  and I try to list directories with many files (e.g. /DCIM/Camera) the
  window hangs until I disconnect the device. Same issue if I try to
  post the command "ls /var/run/1000/gvfs/".

  I have installed Ubuntu 18.04 on two different machines - an older HP
  laptop and a recent DELL laptop - and the issue is present on the all
  of them.

  I suspect a defect on the "libmtp". I tried many alternative solutions
  suggested by the net (e.g. jmtpfs and so on) but anyone worked.

  That's all!

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gvfs-fuse 1.36.1-0ubuntu1.1
  ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
  Uname: Linux 4.15.0-29-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CasperVersion: 1.394
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Sep 12 06:20:07 2018
  LiveMediaBuild: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gvfs
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1792085/+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 1792085] Re: MTP no more working on Bionic

2018-09-24 Thread tomaskCZ

I just switched to Ubuntu 18.04 and I have the same problem. Unable to
list files on my android phone, specifically pictures from camera. It
just hangs after clicking the DCIM dir - there are no '(' file names. It
works without problem on Ubuntu 16.04.

It is broken, lots of similar reports over internet, no clear solution.

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

Title:
  MTP no more working on Bionic

Status in gvfs package in Ubuntu:
  Confirmed

Bug description:
  Hi, unfortunately (for me) MTP android devices no more work on Ubuntu
  18.04.

  I have used MTP on 16.04 without problems, but on 18.04 it does not
  work. When I connect my Android devices (Samsung A5 and Samsung J3)
  and I try to list directories with many files (e.g. /DCIM/Camera) the
  window hangs until I disconnect the device. Same issue if I try to
  post the command "ls /var/run/1000/gvfs/".

  I have installed Ubuntu 18.04 on two different machines - an older HP
  laptop and a recent DELL laptop - and the issue is present on the all
  of them.

  I suspect a defect on the "libmtp". I tried many alternative solutions
  suggested by the net (e.g. jmtpfs and so on) but anyone worked.

  That's all!

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gvfs-fuse 1.36.1-0ubuntu1.1
  ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
  Uname: Linux 4.15.0-29-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CasperVersion: 1.394
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Sep 12 06:20:07 2018
  LiveMediaBuild: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gvfs
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1792085/+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 1794178] [NEW] Install failure

2018-09-24 Thread Gourav Rattihalli

Public bug reported:

apt-get install libxext6
Reading package lists... Done
Building dependency tree   
Reading state information... Done
The following package was automatically installed and is no longer required:
  libxmuu1
Use 'apt autoremove' to remove it.
The following NEW packages will be installed:
  libxext6
0 upgraded, 1 newly installed, 0 to remove and 27 not upgraded.
Need to get 29.4 kB of archives.
After this operation, 125 kB of additional disk space will be used.
Err:1 http://xxx.xxx.xxx.xxx:80/data/040d470b23b0f368/archive.ubuntu.com/ubuntu 
xenial/main amd64 libxext6 amd64 2:1.3.3-1
  Unknown date format Bad header data
E: Failed to fetch 
http://xxx.xxx.xxx.xxx:80/data/040d470b23b0f368/archive.ubuntu.com/ubuntu/pool/main/libx/libxext/libxext6_1.3.3-1_amd64.deb
  Unknown date format Bad header data

E: Unable to fetch some archives, maybe run apt-get update or try with
--fix-missing?

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

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

Title:
  Install failure

Status in libxext package in Ubuntu:
  New

Bug description:
  apt-get install libxext6
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  The following package was automatically installed and is no longer required:
libxmuu1
  Use 'apt autoremove' to remove it.
  The following NEW packages will be installed:
libxext6
  0 upgraded, 1 newly installed, 0 to remove and 27 not upgraded.
  Need to get 29.4 kB of archives.
  After this operation, 125 kB of additional disk space will be used.
  Err:1 
http://xxx.xxx.xxx.xxx:80/data/040d470b23b0f368/archive.ubuntu.com/ubuntu 
xenial/main amd64 libxext6 amd64 2:1.3.3-1
Unknown date format Bad header data
  E: Failed to fetch 
http://xxx.xxx.xxx.xxx:80/data/040d470b23b0f368/archive.ubuntu.com/ubuntu/pool/main/libx/libxext/libxext6_1.3.3-1_amd64.deb
  Unknown date format Bad header data

  E: Unable to fetch some archives, maybe run apt-get update or try with
  --fix-missing?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libxext/+bug/1794178/+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 1794180] [NEW] gnome-control-center crashed with SIGABRT

2018-09-24 Thread Till Kamppeter

Public bug reported:

I tried to run g-c-c as root:

sudo gnome-control-center

and after some seconds it aborted, without opening its window.

If it is not made for running it as root it should exit with a decent
error message and not crash.

ProblemType: Crash
DistroRelease: Ubuntu 18.10
Package: gnome-control-center 1:3.30.0-0ubuntu1
ProcVersionSignature: Ubuntu 4.18.0-7.8-generic 4.18.5
Uname: Linux 4.18.0-7-generic x86_64
ApportVersion: 2.20.10-0ubuntu11
Architecture: amd64
Date: Mon Sep 24 21:31:33 2018
ExecutablePath: /usr/bin/gnome-control-center
InstallationDate: Installed on 2018-02-07 (229 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180207)
ProcCmdline: gnome-control-center
Signal: 6
SourcePackage: gnome-control-center
StacktraceTop:
 () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_assertion_message_expr () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
 cc_shell_model_set_panel_visibility ()
 ()
 cc_wifi_panel_static_init_func ()
Title: gnome-control-center crashed with SIGABRT
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

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


** Tags: amd64 apport-crash cosmic need-amd64-retrace

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

Title:
  gnome-control-center crashed with SIGABRT

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

Bug description:
  I tried to run g-c-c as root:

  sudo gnome-control-center

  and after some seconds it aborted, without opening its window.

  If it is not made for running it as root it should exit with a decent
  error message and not crash.

  ProblemType: Crash
  DistroRelease: Ubuntu 18.10
  Package: gnome-control-center 1:3.30.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.18.0-7.8-generic 4.18.5
  Uname: Linux 4.18.0-7-generic x86_64
  ApportVersion: 2.20.10-0ubuntu11
  Architecture: amd64
  Date: Mon Sep 24 21:31:33 2018
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2018-02-07 (229 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180207)
  ProcCmdline: gnome-control-center
  Signal: 6
  SourcePackage: gnome-control-center
  StacktraceTop:
   () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_assertion_message_expr () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
   cc_shell_model_set_panel_visibility ()
   ()
   cc_wifi_panel_static_init_func ()
  Title: gnome-control-center crashed with SIGABRT
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1794180/+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 1794180] Re: gnome-control-center crashed with SIGABRT

2018-09-24 Thread Apport retracing service

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

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

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

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

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

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

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

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

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

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

** Tags removed: need-amd64-retrace

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

Title:
  gnome-control-center crashed with SIGABRT

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

Bug description:
  I tried to run g-c-c as root:

  sudo gnome-control-center

  and after some seconds it aborted, without opening its window.

  If it is not made for running it as root it should exit with a decent
  error message and not crash.

  ProblemType: Crash
  DistroRelease: Ubuntu 18.10
  Package: gnome-control-center 1:3.30.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.18.0-7.8-generic 4.18.5
  Uname: Linux 4.18.0-7-generic x86_64
  ApportVersion: 2.20.10-0ubuntu11
  Architecture: amd64
  Date: Mon Sep 24 21:31:33 2018
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2018-02-07 (229 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180207)
  ProcCmdline: gnome-control-center
  Signal: 6
  SourcePackage: gnome-control-center
  StacktraceTop:
   () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_assertion_message_expr () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
   cc_shell_model_set_panel_visibility ()
   ()
   cc_wifi_panel_static_init_func ()
  Title: gnome-control-center crashed with SIGABRT
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1794180/+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 1792873] Re: FFE: 18.2.x for cosmic

LLVM 7 is the default in cosmic :)

and mesa 18.2.1 is built now, installs fine from the ppa

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

Title:
  FFE: 18.2.x for cosmic

Status in mesa package in Ubuntu:
  New

Bug description:
  Mesa 18.2.0 was recently released after several delays, but at least
  it doesn't have any known regressions on Intel hw. We tend to get the
  latest major version in the devel series ~2 weeks after FF, but since
  a month has passed now I thought it would be best to file an actual
  FFE request.

  We'd also build it against LLVM 7, which is about to be released.
  Together these provide support for AMD Vega20 (kernel support still
  needed) among other things.

  New features from mesa upstream reldocs:

  OpenGL 4.3 on virgl
  OpenGL 4.4 Compatibility profile on radeonsi
  OpenGL ES 3.2 on radeonsi and virgl
  GL_ARB_ES3_2_compatibility on radeonsi
  GL_ARB_fragment_shader_interlock on i965
  GL_ARB_sample_locations and GL_NV_sample_locations on nvc0 (GM200+)
  GL_ANDROID_extension_pack_es31a on radeonsi.
  GL_KHR_texture_compression_astc_ldr on radeonsi
  GL_NV_conservative_raster and GL_NV_conservative_raster_dilate on nvc0 
(GM200+)
  GL_NV_conservative_raster_pre_snap_triangles on nvc0 (GP102+)
  multisampled images on nvc0 (GM107+) (now supported on GF100+)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1792873/+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 1746856] Re: usb printer does not print (canon d530)

2018-09-24 Thread Alex Yasbek

Hi,

Thank you for the email. Prompted by your email I downloaded the latest
drivers from canon and installed them. Printer now works! I am so happy.
Thanks for checking in.

-Alex

On Fri, Aug 31, 2018 at 12:25 PM gf <1746...@bugs.launchpad.net> wrote:

> Hello Alex,
> Thank you for submitting this bug and reporting a problem with cups.  You
> made this bug report some time ago and Ubuntu and cups have been updated
> since then.
>
> Could you confirm that this is no longer a problem and that we can close
> the ticket?
> If it is still a problem, are you still interested in finding a solution
> to this bug?
> If you are, could you let us know and, in the current version, could you
> run the following (only once):
> apport-collect 1746856
> and upload the updated logs and and any other logs that are relevant for
> this particular issue.
>
> Thank you again for helping make Ubuntu and cups better.
> G
>
> ** Changed in: cups (Ubuntu)
>Status: New => Incomplete
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1746856
>
> Title:
>   usb printer does not print (canon d530)
>
> Status in cups package in Ubuntu:
>   Incomplete
>
> Bug description:
>   Bus 002 Device 005: ID 04a9:2775 Canon, Inc.
>   Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
>   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
>   Bus 001 Device 003: ID 04f2:b217 Chicony Electronics Co., Ltd Lenovo
> Integrated Camera (0.3MP)
>   Bus 001 Device 004: ID 1267:0201 Logic3 / SpectraVideo plc A4Tech SWOP-3
> Mouse
>   Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
>   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
>
>   Description:  Ubuntu 17.10
>   Release:  17.10
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 17.10
>   Package: cups 2.2.4-7ubuntu3
>   ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
>   Uname: Linux 4.13.0-32-generic x86_64
>   ApportVersion: 2.20.7-0ubuntu3.7
>   Architecture: amd64
>   CurrentDesktop: ubuntu:GNOME
>   Date: Thu Feb  1 19:14:46 2018
>   InstallationDate: Installed on 2018-01-22 (10 days ago)
>   InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64
> (20180105.1)
>   Lpstat: device for Canon_D530_D560: cnusb:/dev/usb/lp0
>   MachineType: LENOVO 4239CTO
>   Papersize: letter
>   PpdFiles: Error: command ['fgrep', '-H', '*NickName',
> '/etc/cups/ppd/Canon_D530_D560.ppd'] failed with exit code 2: grep:
> /etc/cups/ppd/Canon_D530_D560.ppd: Permission denied
>   ProcEnviron:
>TERM=xterm-256color
>PATH=(custom, no user)
>XDG_RUNTIME_DIR=
>LANG=en_US.UTF-8
>SHELL=/bin/bash
>   ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic
> root=UUID=1aa4feb1-4b49-43d5-bcce-25b90425a69e ro quiet splash vt.handoff=7
>   SourcePackage: cups
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   dmi.bios.date: 07/05/2012
>   dmi.bios.vendor: LENOVO
>   dmi.bios.version: 8AET58WW (1.38 )
>   dmi.board.asset.tag: Not Available
>   dmi.board.name: 4239CTO
>   dmi.board.vendor: LENOVO
>   dmi.board.version: Not Available
>   dmi.chassis.asset.tag: No Asset Information
>   dmi.chassis.type: 10
>   dmi.chassis.vendor: LENOVO
>   dmi.chassis.version: Not Available
>   dmi.modalias:
> dmi:bvnLENOVO:bvr8AET58WW(1.38):bd07/05/2012:svnLENOVO:pn4239CTO:pvrThinkPadT520:rvnLENOVO:rn4239CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
>   dmi.product.family: ThinkPad T520
>   dmi.product.name: 4239CTO
>   dmi.product.version: ThinkPad T520
>   dmi.sys.vendor: LENOVO
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1746856/+subscriptions
>


-- 
Alexander Yasbek, P.E. - Civil Engineer
831 334 9054
Wastewater and Water Treatment Projects

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

Title:
  usb printer does not print (canon d530)

Status in cups package in Ubuntu:
  Incomplete

Bug description:
  Bus 002 Device 005: ID 04a9:2775 Canon, Inc. 
  Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
  Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 001 Device 003: ID 04f2:b217 Chicony Electronics Co., Ltd Lenovo 
Integrated Camera (0.3MP)
  Bus 001 Device 004: ID 1267:0201 Logic3 / SpectraVideo plc A4Tech SWOP-3 Mouse
  Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

  Description:  Ubuntu 17.10
  Release:  17.10

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: cups 2.2.4-7ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Feb  1 19:14:4

[Desktop-packages] [Bug 1778011] Re: SRU: PRIME Power Saving mode draws too much power

2018-09-24 Thread Nikolaos Perrakis

Hello, I saw the request for testing from the article here:

http://albertomilone.com/blog/?p=670

I 'm running Ubuntu Mate 18.04 in a laptop with i5-7300hq and 1050ti.

I didn't know of the problems mentioned but I 'd taken to switching gpus
from the command line with prime-select and rebooting because of minor
problems with the nvidia application. I can run some tests and upload
logs if needed.

The drivers I use are:

$ apt policy nvidia-390
nvidia-390:
  Installed: 390.87-0ubuntu0~gpu18.04.1
  Candidate: 390.87-0ubuntu0~gpu18.04.1
  Version table:
 *** 390.87-0ubuntu0~gpu18.04.1 500
500 http://ppa.launchpad.net/graphics-drivers/ppa/ubuntu bionic/main 
amd64 Packages
100 /var/lib/dpkg/status

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

Title:
  SRU: PRIME Power Saving mode draws too much power

Status in HWE Next:
  New
Status in gdm3 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Fix Released
Status in nvidia-prime package in Ubuntu:
  Fix Released
Status in nvidia-settings package in Ubuntu:
  Fix Released
Status in ubuntu-drivers-common package in Ubuntu:
  Fix Released
Status in gdm3 source package in Bionic:
  Fix Committed
Status in nvidia-graphics-drivers-390 source package in Bionic:
  Fix Committed
Status in nvidia-prime source package in Bionic:
  Fix Committed
Status in nvidia-settings source package in Bionic:
  Fix Committed
Status in ubuntu-drivers-common source package in Bionic:
  Fix Committed

Bug description:
  SRU Request:

  [Impact]
  Relying on the nouveau driver and on the vga switcheroo (to get around a 
change in systemd LP: #1777099) caused increased power consumption, and slowed 
down the switching process.

  Furthermore, if the main X/Xwayland session was started by Gdm when
  the nvidia driver was loaded, the session will keep the nvidia module
  loaded, and prevent the system from switching off the dGPU. Also, the
  nouveau driver will be loaded, if nvidia is not, and this can cause
  problems to unsupported NVIDIA GPUs.

  The solution involves the following changes:

  1) Solving the problem in systemd (LP: #1777099)

  2) Adding code in gpu-manager and in nvidia-prime to unload the nvidia
  modules, and to allow the PCI device to sleep.

  3) Making a slight change to the current patch in Gdm, used to call
  the PRIME scripts before and after a Gdm session (so that gpu-manager
  gets actually called on log out)

  4) Adding code in gpu-manager to kill the main X/Xwayland session on
  log out, if the session is preventing us from unloading the nvidia
  driver. A new X/Xwayland session will be created after unload the
  module.

  5) Removing the systemd service that loads nouveau from the nvidia
  packages.

  [Test Case]
  1) Enable the -proposed repository, and install the new 
"ubuntu-drivers-common", nvidia drivers, nvidia-prime, and gdm3 *

  2) Make sure the nvidia packages are installed, and enable performance mode 
(if it is already enabled, call "sudo prime-select intel" first):
  sudo prime-select nvidia

  3) Restart your computer and attach your /var/log/gpu-manager.log. see
  if the system boots correctly. If unsure, please attach your /var/log
  /gpu-manager.log and /var/log/Xorg.0.log

  4) Select power saving mode:
  sudo prime-select intel

  5) Log out and log back in

  6) Check if the nvidia driver is still loaded:
  lsmod | grep nvidia

  [Regression Potential]
  Low, as hybrid graphics support does not work correctly, and the changes only 
affect this use case.

  _
  * Steps to test the updates:

  1) Enable the bionic-proposed repositories

  2) Create /etc/apt/preferences.d/proposed-updates with the following
  content:

  Package: *
  Pin: release a=bionic-proposed
  Pin-Priority: 400

  3) Update the list of packages:

  sudo apt-get update

  4) Install the packages from -proposed using the following command:

  sudo apt install nvidia-driver-390/bionic-proposed gdm3/bionic-
  proposed ubuntu-drivers-common/bionic-proposed nvidia-prime/bionic-
  proposed nvidia-settings/bionic-proposed libnvidia-gl-390/bionic-
  proposed libnvidia-compute-390/bionic-proposed libnvidia-decode-390
  /bionic-proposed libnvidia-encode-390/bionic-proposed libnvidia-
  ifr1-390/bionic-proposed libnvidia-fbc1-390/bionic-proposed

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1778011/+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 1767650] Re: Screen rotates upside-down when laptop is not flat

2018-09-24 Thread Scott Cantrell

Everything I have read points to the "3D Driveguard". I appreciate the feature 
and would not so much mind the screen auto-reorientation both
 a) the screen orientation would auto reset even when the screen is locked
 b) screen auto-reorientation could be controlled or disabled in the system 
display settings (not just for the user)

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

Title:
  Screen rotates upside-down when laptop is not flat

Status in iio-sensor-proxy package in Ubuntu:
  Confirmed

Bug description:
  HP Elitebook Folio 9470m.  This system is not a tablet or convertible,
  and does not have a touchscreen.

  If the laptop is sitting flat during boot, the display orientation is
  normal.

  If the laptop is not sitting flat during boot, or if it is moved out
  of flat, the display rotates and the orientation it rotates to is
  inverted upside-down.

  This happens at the login screen as well as after login.

  This laptop should really never have the screen rotate in the first
  place, as it's not a tablet or convertible, but in the event that
  rotation is happening it shouldn't be upside-down.

  
  I have locked the rotation in gnome shell and in the login screen using the 
rotation lock button in the respective system menus.  It would be nice if there 
was a system-wide setting & this didn't need to be done on a per-user basis.

  This gsettings command will also lock the gnome-shell rotation:

  gsettings set org.gnome.settings-daemon.peripherals.touchscreen
  orientation-lock true

  However the above key doesn't affect the login screen, which has its
  own separate rotation button in its own version of the system menu.

  $ lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 18.04 LTS
  Release:  18.04
  Codename: bionic
  $ apt-cache policy gdm3
  gdm3:
Installed: 3.28.0-0ubuntu1
Candidate: 3.28.0-0ubuntu1
Version table:
   *** 3.28.0-0ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status
  $ apt-cache policy gnome-shell
  gnome-shell:
Installed: 3.28.1-0ubuntu2
Candidate: 3.28.1-0ubuntu2
Version table:
   *** 3.28.1-0ubuntu2 500
  500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gdm3 3.28.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr 28 09:17:35 2018
  InstallationDate: Installed on 2018-04-27 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gdm3
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iio-sensor-proxy/+bug/1767650/+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 1793410] Re: [Acer Swift SF315-52, Realtek ALC256, Mic, Internal] Internal microphone not working

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

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

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

Title:
  [Acer Swift SF315-52, Realtek ALC256, Mic, Internal] Internal
  microphone not working

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Recently bought a new Acer Swift 3 laptop and installed Ubuntu 18.04
  on it. Everything works except the internal microphone. I have also
  tested with an external microphone and this didn't work either.

  I have worked my way through all the suggested solutions I could find,
  including trying to reconfigure the pins using hdajacketask. In
  pavucontrol I have options for Internal Microphone and Microphone
  (unplugged) but the internal mic only captures static noise.

  The latest HD-Audio Codec-Specific Models has configurations for
  alc255-acer and alc256 for some other models, but setting options snd-
  hda-intel model=MODEL in /etc/modprobe.d/alsa-base.conf does not solve
  the issue with any of these.

  Some info -

  lspci | grep -I audio:

  00:1f.3 Multimedia audio controller: Intel Corporation Sunrise Point-
  LP HD Audio (rev 21)

  
  cat /proc/asound/cards:

   0 [PCH ]: HDA-Intel - HDA Intel PCH
HDA Intel PCH at 0xdf1a8000 irq 127

  
  dmesg | grep snd:

  [3.944593] snd_hda_core: loading out-of-tree module taints kernel.
  [3.956337] snd_soc_skl: Unknown symbol snd_hdac_display_power (err 0)
  [3.956422] snd_soc_skl: Unknown symbol snd_hdac_i915_exit (err 0)
  [4.000880] snd_hda_intel :00:1f.3: Probing card using HDA DKMS, 
version 0.201808050301~ubuntu18.04.1
  [4.000895] snd_hda_intel :00:1f.3: enabling device ( -> 0002)
  [4.013061] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC256: 
line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:speaker
  [4.013063] snd_hda_codec_realtek hdaudioC0D0:speaker_outs=0 
(0x0/0x0/0x0/0x0/0x0)
  [4.013065] snd_hda_codec_realtek hdaudioC0D0:hp_outs=1 
(0x21/0x0/0x0/0x0/0x0)
  [4.013066] snd_hda_codec_realtek hdaudioC0D0:mono: mono_out=0x0
  [4.013066] snd_hda_codec_realtek hdaudioC0D0:inputs:
  [4.013068] snd_hda_codec_realtek hdaudioC0D0:  Mic=0x18
  [4.013069] snd_hda_codec_realtek hdaudioC0D0:  Internal Mic=0x12

  
  info on node 12 from cat /proc/asound/card*/codec\#*:

  Node 0x12 [Pin Complex] wcaps 0x40040b: Stereo Amp-In
Control: name="Internal Mic Boost Volume", index=0, device=0
  ControlAmp: chs=3, dir=In, idx=0, ofs=0
Amp-In caps: ofs=0x00, nsteps=0x03, stepsize=0x27, mute=0
Amp-In vals:  [0x02 0x02]
Pincap 0x0020: IN
Pin Default 0x4000: [N/A] Line Out at Ext N/A
  Conn = Unknown, Color = Unknown
  DefAssociation = 0x0, Sequence = 0x0
Pin-ctls: 0x20: IN
Power states:  D0 D1 D2 D3 EPSS
Power: setting=D0, actual=D0

  Let me know if you need any other information.

  James

  ---

  Tags:  bionic
  Uname: Linux 4.15.0-34-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  _MarkForUpload: True
  dmi.bios.date: 06/22/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V1.04
  dmi.board.asset.tag: Default string
  dmi.board.name: Erdinger_KL
  dmi.board.vendor: KBL
  dmi.board.version: V1.04
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.04
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV1.04:bd06/22/2018:svnAcer:pnSwiftSF315-52:pvrV1.04:rvnKBL:rnErdinger_KL:rvrV1.04:cvnAcer:ct10:cvrV1.04:
  dmi.product.family: Swift 3
  dmi.product.name: Swift SF315-52
  dmi.product.version: V1.04
  dmi.sys.vendor: Acer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1793410/+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 1790409] [NEW] All gnome apps text areas seem to get messy when using nemo-desktop for desktop icons

You have been subscribed to a public bug:

With nemo-desktop on open gedit or gnome-system-log and it will be
impossible to see any text whatsoever because the area is filled with
whatever the background was and continious rerenders.

I think this affect apps using a certain feature in gnome libraries so
only gnome apps are affected and often the ones with white text areas.
As an example of text area not affected I notice gnome-terminal seems
fine.

Details: 
I've followed 
https://www.linuxuprising.com/2018/07/how-to-replace-nautilus-with-nemo-file.html
and use nemo-desktop as my file manager. I've used nemo in 16.04 without 
problems. My other family members have users that use nautilus and they do not 
have the same problems as me.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: nemo 3.6.5-1
ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
Uname: Linux 4.15.0-33-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sun Sep  2 23:08:38 2018
EcryptfsInUse: Yes
InstallationDate: Installed on 2012-09-01 (2192 days ago)
InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 
(20120823.1)
ProcEnviron:
 LANGUAGE=nb_NO:nb:no_NO:no:nn_NO:nn:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=nb_NO.UTF-8
 SHELL=/usr/bin/fish
SourcePackage: nemo
UpgradeStatus: Upgraded to bionic on 2018-09-01 (1 days ago)

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


** Tags: amd64 apport-bug bionic third-party-packages
-- 
All gnome apps text areas seem to get messy when using nemo-desktop for desktop 
icons 
https://bugs.launchpad.net/bugs/1790409
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to gnome-shell 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 1793410] Re: [Acer Swift SF315-52, Realtek ALC256, Mic, Internal] Internal microphone not working

2018-09-24 Thread Justin

Hello I have the same issue. I tried for a couple days to fix it without
any results. I have the latest drivers installed
(https://wiki.ubuntu.com/Audio/UpgradingAlsa/DKMS). I then tried to set
all configurations to default and ran alsa-info. The ouput is located at
the following url and in the attached text document. I hope this is
helpful.

http://www.alsa-
project.org/db/?f=79aa0cb7023e375b7255e6789c7bd19c26a70d4f


thankyou

** Attachment added: "My Sound card information"
   
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1793410/+attachment/5192618/+files/alsa_info.txt

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

Title:
  [Acer Swift SF315-52, Realtek ALC256, Mic, Internal] Internal
  microphone not working

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Recently bought a new Acer Swift 3 laptop and installed Ubuntu 18.04
  on it. Everything works except the internal microphone. I have also
  tested with an external microphone and this didn't work either.

  I have worked my way through all the suggested solutions I could find,
  including trying to reconfigure the pins using hdajacketask. In
  pavucontrol I have options for Internal Microphone and Microphone
  (unplugged) but the internal mic only captures static noise.

  The latest HD-Audio Codec-Specific Models has configurations for
  alc255-acer and alc256 for some other models, but setting options snd-
  hda-intel model=MODEL in /etc/modprobe.d/alsa-base.conf does not solve
  the issue with any of these.

  Some info -

  lspci | grep -I audio:

  00:1f.3 Multimedia audio controller: Intel Corporation Sunrise Point-
  LP HD Audio (rev 21)

  
  cat /proc/asound/cards:

   0 [PCH ]: HDA-Intel - HDA Intel PCH
HDA Intel PCH at 0xdf1a8000 irq 127

  
  dmesg | grep snd:

  [3.944593] snd_hda_core: loading out-of-tree module taints kernel.
  [3.956337] snd_soc_skl: Unknown symbol snd_hdac_display_power (err 0)
  [3.956422] snd_soc_skl: Unknown symbol snd_hdac_i915_exit (err 0)
  [4.000880] snd_hda_intel :00:1f.3: Probing card using HDA DKMS, 
version 0.201808050301~ubuntu18.04.1
  [4.000895] snd_hda_intel :00:1f.3: enabling device ( -> 0002)
  [4.013061] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC256: 
line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:speaker
  [4.013063] snd_hda_codec_realtek hdaudioC0D0:speaker_outs=0 
(0x0/0x0/0x0/0x0/0x0)
  [4.013065] snd_hda_codec_realtek hdaudioC0D0:hp_outs=1 
(0x21/0x0/0x0/0x0/0x0)
  [4.013066] snd_hda_codec_realtek hdaudioC0D0:mono: mono_out=0x0
  [4.013066] snd_hda_codec_realtek hdaudioC0D0:inputs:
  [4.013068] snd_hda_codec_realtek hdaudioC0D0:  Mic=0x18
  [4.013069] snd_hda_codec_realtek hdaudioC0D0:  Internal Mic=0x12

  
  info on node 12 from cat /proc/asound/card*/codec\#*:

  Node 0x12 [Pin Complex] wcaps 0x40040b: Stereo Amp-In
Control: name="Internal Mic Boost Volume", index=0, device=0
  ControlAmp: chs=3, dir=In, idx=0, ofs=0
Amp-In caps: ofs=0x00, nsteps=0x03, stepsize=0x27, mute=0
Amp-In vals:  [0x02 0x02]
Pincap 0x0020: IN
Pin Default 0x4000: [N/A] Line Out at Ext N/A
  Conn = Unknown, Color = Unknown
  DefAssociation = 0x0, Sequence = 0x0
Pin-ctls: 0x20: IN
Power states:  D0 D1 D2 D3 EPSS
Power: setting=D0, actual=D0

  Let me know if you need any other information.

  James

  ---

  Tags:  bionic
  Uname: Linux 4.15.0-34-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  _MarkForUpload: True
  dmi.bios.date: 06/22/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V1.04
  dmi.board.asset.tag: Default string
  dmi.board.name: Erdinger_KL
  dmi.board.vendor: KBL
  dmi.board.version: V1.04
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.04
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV1.04:bd06/22/2018:svnAcer:pnSwiftSF315-52:pvrV1.04:rvnKBL:rnErdinger_KL:rvrV1.04:cvnAcer:ct10:cvrV1.04:
  dmi.product.family: Swift 3
  dmi.product.name: Swift SF315-52
  dmi.product.version: V1.04
  dmi.sys.vendor: Acer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1793410/+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 1790409] Re: All gnome apps text areas seem to get messy when using nemo-desktop for desktop icons

2018-09-24 Thread Sylwester

I'm no longer certain this is nemo related as I found one account with
Nemo and without the problem.


** Package changed: nemo (Ubuntu) => gnome-shell (Ubuntu)

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

Title:
  All gnome apps text areas seem to get messy when using nemo-desktop
  for desktop icons

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  With nemo-desktop on open gedit or gnome-system-log and it will be
  impossible to see any text whatsoever because the area is filled with
  whatever the background was and continious rerenders.

  I think this affect apps using a certain feature in gnome libraries so
  only gnome apps are affected and often the ones with white text areas.
  As an example of text area not affected I notice gnome-terminal seems
  fine.

  Details: 
  I've followed 
https://www.linuxuprising.com/2018/07/how-to-replace-nautilus-with-nemo-file.html
  and use nemo-desktop as my file manager. I've used nemo in 16.04 without 
problems. My other family members have users that use nautilus and they do not 
have the same problems as me.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: nemo 3.6.5-1
  ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
  Uname: Linux 4.15.0-33-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Sep  2 23:08:38 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2012-09-01 (2192 days ago)
  InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 
(20120823.1)
  ProcEnviron:
   LANGUAGE=nb_NO:nb:no_NO:no:nn_NO:nn:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=nb_NO.UTF-8
   SHELL=/usr/bin/fish
  SourcePackage: nemo
  UpgradeStatus: Upgraded to bionic on 2018-09-01 (1 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1790409/+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 1790409] Re: All gnome apps text areas seem to get messy when using nemo-desktop for desktop icons

2018-09-24 Thread Sylwester

I can also mention that changing my theme from Ambiance to Adwaita
removed the issue. All the other accounts use Ambiance so there must be
user level settings that is triggering this.

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

Title:
  All gnome apps text areas seem to get messy when using nemo-desktop
  for desktop icons

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  With nemo-desktop on open gedit or gnome-system-log and it will be
  impossible to see any text whatsoever because the area is filled with
  whatever the background was and continious rerenders.

  I think this affect apps using a certain feature in gnome libraries so
  only gnome apps are affected and often the ones with white text areas.
  As an example of text area not affected I notice gnome-terminal seems
  fine.

  Details: 
  I've followed 
https://www.linuxuprising.com/2018/07/how-to-replace-nautilus-with-nemo-file.html
  and use nemo-desktop as my file manager. I've used nemo in 16.04 without 
problems. My other family members have users that use nautilus and they do not 
have the same problems as me.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: nemo 3.6.5-1
  ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
  Uname: Linux 4.15.0-33-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Sep  2 23:08:38 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2012-09-01 (2192 days ago)
  InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 
(20120823.1)
  ProcEnviron:
   LANGUAGE=nb_NO:nb:no_NO:no:nn_NO:nn:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=nb_NO.UTF-8
   SHELL=/usr/bin/fish
  SourcePackage: nemo
  UpgradeStatus: Upgraded to bionic on 2018-09-01 (1 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1790409/+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 1588197] Re: Can't type anything in search box

2018-09-24 Thread Thomas Mayer

Right after upgrading from 16.04 to 18.04, I can't type in evince's
search field any more. Proposed packages where never installed on that
system.

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

Title:
  Can't type anything in search box

Status in evince package in Ubuntu:
  Invalid

Bug description:
  Since Ubuntu 16.04, I can't search strings in PDF using Evince viewer.
  Clicking search button or CTRL+F shows search box, but I can't type
  anything inside.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1588197/+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 1588197] Re: Can't type anything in search box

2018-09-24 Thread Thomas Mayer

For some PDFs I can type something in the search field. Seems to be
related to the PDF (if it contains text or not).

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

Title:
  Can't type anything in search box

Status in evince package in Ubuntu:
  Invalid

Bug description:
  Since Ubuntu 16.04, I can't search strings in PDF using Evince viewer.
  Clicking search button or CTRL+F shows search box, but I can't type
  anything inside.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1588197/+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 1790409] Re: All gnome apps text areas seem to get messy when using nemo-desktop for desktop icons

2018-09-24 Thread Jeremy Bicha

This sounds like a nemo issue since gnome-shell does not handle desktop
icons.

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

Title:
  All gnome apps text areas seem to get messy when using nemo-desktop
  for desktop icons

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  With nemo-desktop on open gedit or gnome-system-log and it will be
  impossible to see any text whatsoever because the area is filled with
  whatever the background was and continious rerenders.

  I think this affect apps using a certain feature in gnome libraries so
  only gnome apps are affected and often the ones with white text areas.
  As an example of text area not affected I notice gnome-terminal seems
  fine.

  Details: 
  I've followed 
https://www.linuxuprising.com/2018/07/how-to-replace-nautilus-with-nemo-file.html
  and use nemo-desktop as my file manager. I've used nemo in 16.04 without 
problems. My other family members have users that use nautilus and they do not 
have the same problems as me.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: nemo 3.6.5-1
  ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
  Uname: Linux 4.15.0-33-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Sep  2 23:08:38 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2012-09-01 (2192 days ago)
  InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 
(20120823.1)
  ProcEnviron:
   LANGUAGE=nb_NO:nb:no_NO:no:nn_NO:nn:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=nb_NO.UTF-8
   SHELL=/usr/bin/fish
  SourcePackage: nemo
  UpgradeStatus: Upgraded to bionic on 2018-09-01 (1 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1790409/+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 1791542] Re: package libglvnd-dev 1.0.0-2ubuntu2.1 failed to upgrade: trying to overwrite '/usr/lib/x86_64-linux-gnu/libGLESv1_CM.so', which is also in package nvidia-340 340.1

2018-09-24 Thread Bao Nguyen

It fixed the problem for me.

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

Title:
  package libglvnd-dev 1.0.0-2ubuntu2.1 failed to upgrade: trying to
  overwrite '/usr/lib/x86_64-linux-gnu/libGLESv1_CM.so', which is also
  in package nvidia-340 340.107-0ubuntu0~gpu18.04.1

Status in libglvnd package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Fix Released
Status in libglvnd source package in Bionic:
  Confirmed
Status in nvidia-graphics-drivers-340 source package in Bionic:
  Fix Committed

Bug description:
  SRU Request:

  [Impact]

  The new libgles1 conflicts with nvidia-340 which ships it's own copy
  of libGLESv1_CM.so

  [Test case]

  Enable proposed, install libgles1 and nvidia-340, they should install
  fine.

  [Regression potential]

  none, just fixes a file conflict

  --

  Looks like I had a similar problem on 18.04.1 than
  https://bugs.launchpad.net/ubuntu/+source/libglvnd/+bug/1728352, just
  with nvidia-340 from https://launchpad.net/~graphics-
  drivers/+archive/ubuntu/ppa .

  Apt output:
  ```
  $ sudo apt dist-upgrade
  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  Calculating upgrade... Done
  The following NEW packages will be installed:
    libgles1
  The following packages will be upgraded:
    libegl1 libgl1 libgles2 libglvnd-core-dev libglvnd-dev libglvnd0 libglx0 
libopengl0
  8 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
  Need to get 268 kB of archives.
  After this operation, 66,6 kB of additional disk space will be used.
  Do you want to continue? [Y/n]
  Get:1 http://archive.ubuntu.com/ubuntu bionic-proposed/main amd64 
libglvnd-dev amd64 1.0.0-2ubuntu2.2 [3 408 B]
  Get:2 http://archive.ubuntu.com/ubuntu bionic-proposed/main amd64 
libglvnd-core-dev amd64 1.0.0-2ubuntu2.2 [12,9 kB]
  Get:3 http://archive.ubuntu.com/ubuntu bionic-proposed/main amd64 libgles2 
amd64 1.0.0-2ubuntu2.2 [17,4 kB]
  Get:4 http://archive.ubuntu.com/ubuntu bionic-proposed/main amd64 libgl1 
amd64 1.0.0-2ubuntu2.2 [84,8 kB]
  Get:5 http://archive.ubuntu.com/ubuntu bionic-proposed/main amd64 libglx0 
amd64 1.0.0-2ubuntu2.2 [28,1 kB]
  Get:6 http://archive.ubuntu.com/ubuntu bionic-proposed/main amd64 libopengl0 
amd64 1.0.0-2ubuntu2.2 [31,3 kB]
  Get:7 http://archive.ubuntu.com/ubuntu bionic-proposed/main amd64 libegl1 
amd64 1.0.0-2ubuntu2.2 [31,9 kB]
  Get:8 http://archive.ubuntu.com/ubuntu bionic-proposed/main amd64 libglvnd0 
amd64 1.0.0-2ubuntu2.2 [46,6 kB]
  Get:9 http://archive.ubuntu.com/ubuntu bionic-proposed/main amd64 libgles1 
amd64 1.0.0-2ubuntu2.2 [11,2 kB]
  Fetched 268 kB in 0s (1 575 kB/s)
  (Reading database ... 141610 files and directories currently installed.)
  Preparing to unpack .../0-libglvnd-dev_1.0.0-2ubuntu2.2_amd64.deb ...
  Unpacking libglvnd-dev:amd64 (1.0.0-2ubuntu2.2) over (1.0.0-2ubuntu2.1) ...
  dpkg: error processing archive 
/tmp/apt-dpkg-install-Gq7kQI/0-libglvnd-dev_1.0.0-2ubuntu2.2_amd64.deb 
(--unpack):
   trying to overwrite '/usr/lib/x86_64-linux-gnu/libGLESv1_CM.so', which is 
also in package nvidia-340 340.107-0ubuntu0~gpu18.04.1
  Preparing to unpack .../1-libglvnd-core-dev_1.0.0-2ubuntu2.2_amd64.deb ...
  Unpacking libglvnd-core-dev:amd64 (1.0.0-2ubuntu2.2) over (1.0.0-2ubuntu2.1) 
...
  Preparing to unpack .../2-libgles2_1.0.0-2ubuntu2.2_amd64.deb ...
  Unpacking libgles2:amd64 (1.0.0-2ubuntu2.2) over (1.0.0-2ubuntu2.1) ...
  Preparing to unpack .../3-libgl1_1.0.0-2ubuntu2.2_amd64.deb ...
  Unpacking libgl1:amd64 (1.0.0-2ubuntu2.2) over (1.0.0-2ubuntu2.1) ...
  Preparing to unpack .../4-libglx0_1.0.0-2ubuntu2.2_amd64.deb ...
  Unpacking libglx0:amd64 (1.0.0-2ubuntu2.2) over (1.0.0-2ubuntu2.1) ...
  Preparing to unpack .../5-libopengl0_1.0.0-2ubuntu2.2_amd64.deb ...
  Unpacking libopengl0:amd64 (1.0.0-2ubuntu2.2) over (1.0.0-2ubuntu2.1) ...
  Preparing to unpack .../6-libegl1_1.0.0-2ubuntu2.2_amd64.deb ...
  Unpacking libegl1:amd64 (1.0.0-2ubuntu2.2) over (1.0.0-2ubuntu2.1) ...
  Preparing to unpack .../7-libglvnd0_1.0.0-2ubuntu2.2_amd64.deb ...
  Unpacking libglvnd0:amd64 (1.0.0-2ubuntu2.2) over (1.0.0-2ubuntu2.1) ...
  Selecting previously unselected package libgles1:amd64.
  Preparing to unpack .../8-libgles1_1.0.0-2ubuntu2.2_amd64.deb ...
  Unpacking libgles1:amd64 (1.0.0-2ubuntu2.2) ...
  dpkg: error processing archive 
/tmp/apt-dpkg-install-Gq7kQI/8-libgles1_1.0.0-2ubuntu2.2_amd64.deb (--unpack):
   trying to overwrite '/usr/lib/x86_64-linux-gnu/libGLESv1_CM.so.1', which is 
also in package nvidia-340 340.107-0ubuntu0~gpu18.04.1
  Errors were encountered while processing:
   /tmp/apt-dpkg-install-Gq7kQI/0-libglvnd-dev_1.0.0-2ubuntu2.2_amd64.deb
   /tmp/apt-dpkg-install-Gq7kQI/8-libgles1_1.0.0-2ubuntu2.2_amd64.deb
  E: Sub-process /usr/bin/dpkg returned an error code (1)
  ```

  ProblemType: Package
  Di

[Desktop-packages] [Bug 1779476] Re: Ubuntu 18.04: gdm3 does not switch to graphics after update

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

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

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

Title:
  Ubuntu 18.04: gdm3 does not switch to graphics after update

Status in gdm3 package in Ubuntu:
  Expired

Bug description:
  After update of gdm and kernel gdm3 no longer enables graphics.

  What happens:
  =
  With and without:
 WaylandEnable=false
  in /etc/gdm3/custom.conf
  gdm3 does not switch to graphics.
  In both cases I case the X process running (Xwayland or Xorg) but no vt has 
it.
  lightdm does work, but barely. It takes up to a minute to get to the login 
screen.

  What I expected to happen:
  ==
  gdm3 switching to graphics in ~20 after boot like pre-update.

  Release:
  
  $ lsb_release -rd
  Description:  Ubuntu 18.04 LTS
  Release:  18.04
  $ apt-cache policy kernel-common gdm3 lightdm xorg xwayland
  kernel-common:
Installed: (none)
Candidate: 13.018+nmu1
Version table:
   13.018+nmu1 500
  500 http://us.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages
  500 http://us.archive.ubuntu.com/ubuntu bionic/universe i386 Packages
  gdm3:
Installed: 3.28.2-0ubuntu1.3
Candidate: 3.28.2-0ubuntu1.3
Version table:
   *** 3.28.2-0ubuntu1.3 500
  500 http://us.archive.ubuntu.com/ubuntu bionic-proposed/main amd64 
Packages
  100 /var/lib/dpkg/status
   3.28.2-0ubuntu1.2 500
  500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
   3.28.0-0ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  lightdm:
Installed: 1.26.0-0ubuntu1
Candidate: 1.26.0-0ubuntu1
Version table:
   *** 1.26.0-0ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages
  100 /var/lib/dpkg/status
  xorg:
Installed: 1:7.7+19ubuntu7
Candidate: 1:7.7+19ubuntu7
Version table:
   *** 1:7.7+19ubuntu7 500
  500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status
  xwayland:
Installed: 2:1.19.6-1ubuntu4
Candidate: 2:1.19.6-1ubuntu4
Version table:
   *** 2:1.19.6-1ubuntu4 500
  500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status


  
  Attaching journalctl -b.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-08-27 (673 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  NonfreeKernelModules: wl
  Package: gdm3 3.28.2-0ubuntu1.3
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18
  Tags:  bionic package-from-proposed
  Uname: Linux 4.15.0-24-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2018-05-05 (58 days ago)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  mtime.conffile..etc.gdm3.custom.conf: 2018-06-30T11:12:29.280424
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-08-27 (674 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  NonfreeKernelModules: wl
  Package: linux
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18
  Tags:  bionic package-from-proposed
  Uname: Linux 4.15.0-24-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2018-05-05 (58 days ago)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  modified.conffile..etc.gdm3.custom.conf: [modified]
  mtime.conffile..etc.gdm3.custom.conf: 2018-06-30T11:12:29.280424

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1779476/+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 1618733] Re: firefox 46 crashes powerpc

[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/1618733

Title:
  firefox 46 crashes powerpc

Status in firefox package in Ubuntu:
  Expired

Bug description:
  I am running Ubuntu-MATE 16.10 PPC32. The browser keeps crashing upon
  startup. I am attching a backtrace I recieved from gdb.

  rican-linux@MATE-PPC:~$ lsb_release -rd
  Description:  Ubuntu Yakkety Yak (development branch)
  Release:  16.10
  rican-linux@MATE-PPC:~$ 

  rican-linux@MATE-PPC:~$ apt-cache policy firefox
  firefox:
Installed: 46.0.1+build1-0ubuntu1
Candidate: 46.0.1+build1-0ubuntu1
Version table:
   *** 46.0.1+build1-0ubuntu1 500
  500 http://us.ports.ubuntu.com/ubuntu-ports yakkety/main powerpc 
Packages
  100 /var/lib/dpkg/status
  rican-linux@MATE-PPC:~$ 

  
  rican-linux@MATE-PPC:~$ gdb /usr/lib/firefox/firefox
  GNU gdb (Ubuntu 7.11.90.20160824-0ubuntu2) 7.11.90.20160824-git
  Copyright (C) 2016 Free Software Foundation, Inc.
  License GPLv3+: GNU GPL version 3 or later 
  This is free software: you are free to change and redistribute it.
  There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
  and "show warranty" for details.
  This GDB was configured as "powerpc-linux-gnu".
  Type "show configuration" for configuration details.
  For bug reporting instructions, please see:
  .
  Find the GDB manual and other documentation resources online at:
  .
  For help, type "help".
  Type "apropos word" to search for commands related to "word"...
  Reading symbols from /usr/lib/firefox/firefox...Reading symbols from 
/usr/lib/debug//usr/lib/firefox/firefox...done.
  done.
  (gdb) run
  Starting program: /usr/lib/firefox/firefox 
  [Thread debugging using libthread_db enabled]
  Using host libthread_db library "/lib/powerpc-linux-gnu/libthread_db.so.1".
  [New Thread 0xb7aff450 (LWP 18560)]
  [New Thread 0xb71ff450 (LWP 18561)]
  [New Thread 0xb69ff450 (LWP 18562)]
  [New Thread 0xb60ff450 (LWP 18564)]
  [New Thread 0xb4489450 (LWP 18566)]
  [New Thread 0xb3c89450 (LWP 18567)]
  [New Thread 0xb32ff450 (LWP 18569)]
  [New Thread 0xb30ff450 (LWP 18570)]
  [New Thread 0xb2eff450 (LWP 18571)]
  [New Thread 0xb2cff450 (LWP 18572)]
  [New Thread 0xb2aff450 (LWP 18573)]
  [New Thread 0xb18ff450 (LWP 18574)]
  [New Thread 0xb0dff450 (LWP 18576)]
  [New Thread 0xb04f1450 (LWP 18578)]
  [New Thread 0xb00ff450 (LWP 18579)]
  [New Thread 0xaf7ff450 (LWP 18582)]
  [New Thread 0xaefff450 (LWP 18583)]
  [New Thread 0xae6ff450 (LWP 18584)]
  [Thread 0xae6ff450 (LWP 18584) exited]
  [New Thread 0xae6ff450 (LWP 18586)]
  [New Thread 0xadc76450 (LWP 18587)]
  [New Thread 0xaceff450 (LWP 18593)]
  [New Thread 0xac6ff450 (LWP 18594)]
  [New Thread 0xabeff450 (LWP 18595)]
  [New Thread 0xab6ff450 (LWP 18596)]
  [Thread 0xab6ff450 (LWP 18596) exited]
  [Thread 0xabeff450 (LWP 18595) exited]
  [Thread 0xaceff450 (LWP 18593) exited]
  [New Thread 0xab6ff450 (LWP 18599)]
  [New Thread 0xabeff450 (LWP 18600)]
  [New Thread 0xaceff450 (LWP 18601)]
  [New Thread 0xaa7ff450 (LWP 18602)]
  [New Thread 0xa9fff450 (LWP 18603)]
  [New Thread 0xa97ff450 (LWP 18604)]
  [New Thread 0xa8fff450 (LWP 18605)]
  [New Thread 0xa87ff450 (LWP 18606)]
  [New Thread 0xa7fff450 (LWP 18607)]
  [New Thread 0xa77ff450 (LWP 18608)]
  [New Thread 0xa6fff450 (LWP 18610)]
  [Thread 0xadc76450 (LWP 18587) exited]
  [Thread 0xa9fff450 (LWP 18603) exited]
  [Thread 0xa97ff450 (LWP 18604) exited]
  [Thread 0xa87ff450 (LWP 18606) exited]
  [New Thread 0xa66ff450 (LWP 18611)]
  [New Thread 0xa87ff450 (LWP 18612)]
  [New Thread 0xa97ff450 (LWP 18613)]
  [Thread 0xa8fff450 (LWP 18605) exited]
  [Thread 0xa97ff450 (LWP 18613) exited]
  [New Thread 0xa97ff450 (LWP 18616)]
  [New Thread 0xa8fff450 (LWP 18617)]
  [New Thread 0xa9fff450 (LWP 18618)]
  [New Thread 0xa59ff450 (LWP 18619)]
  [New Thread 0xadc76450 (LWP 18622)]
  [New Thread 0xa48ff450 (LWP 18623)]
  [New Thread 0xa40ff450 (LWP 18624)]
  [New Thread 0xa38ff450 (LWP 18625)]
  [Thread 0xa87ff450 (LWP 18612) exited]
  [Thread 0xa40ff450 (LWP 18624) exited]
  [New Thread 0xa40ff450 (LWP 18627)]
  Crash Annotation GraphicsCriticalError: |[0][GFX1]: Unknown image format 1 
(t=104.616)[GFX1]: Unknown image format 1
  Crash Annotation GraphicsCriticalError: |[0][GFX1]: Unknown image format 1 
(t=104.616)|[1][GFX1]: Unknown image format 0 (t=104.661)[GFX1]: Unknown image 
format 0
  Crash Annotation GraphicsCriticalError: |[0][GFX1]: Unknown image format 1 
(t=104.616)|[1][GFX1]: Unknown image format 0 (t=104.661)|[2][GFX1]: Unknown 
image format 0 (t=104.665)[GFX1]: Unknown image format 0
  Crash Annotation GraphicsCri

[Desktop-packages] [Bug 1373080] Re: sending mail in gmail leaves the sent message text selectede