[Desktop-packages] [Bug 1743018] Re: Unable to install mesa-opencl-icd because of unmet dependencies on Xenial

[Timo Aaltonen]

affects only xenial, the dependency should be relaxed

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

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

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

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

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

Title:
  Unable to install mesa-opencl-icd because of unmet dependencies on
  Xenial

Status in mesa package in Ubuntu:
  Invalid
Status in mesa source package in Xenial:
  In Progress

Bug description:
  Steps to reproduce:
  1. Install Ubuntu 16.04 LTS
  2. Try to install `mesa-opencl-icd` with

  $ sudo apt-get install mesa-opencl-icd
  [sudo] password for user: 
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done

  
  Expected results:
  * mesa-opencl-icd is installed successfully

  Actual results:
  * got errors as follow

  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:
   mesa-opencl-icd : Depends: libclc-r600 (>= 0.2.0+git20170330-3) but it is 
not going to be installed
 Depends: libclc-amdgcn (>= 0.2.0+git20170330-3) but it is 
not going to be installed
  E: Unable to correct problems, you have held broken packages.

  
  Note: inspired by this AskUbuntu question - 
https://askubuntu.com/q/995274/66509 .

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: mesa-opencl-icd (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-109.132-generic 4.4.98
  Uname: Linux 4.4.0-109-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,mousepoll,move,gnomecompat,wall,regex,place,resize,snap,session,imgpng,vpswitch,grid,unitymtgrabhandles,animation,expo,workarounds,ezoom,staticswitcher,fade,scale,unityshell]
  CompositorRunning: None
  CurrentDesktop: MATE
  Date: Fri Jan 12 21:22:22 2018
  DistUpgraded: 2017-04-16 02:19:02,541 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: xenial
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. 3rd Gen Core processor Graphics 
Controller [1043:2135]
  InstallationDate: Installed on 2014-02-07 (1434 days ago)
  InstallationMedia: Ubuntu 12.04.4 LTS "Precise Pangolin" - Release amd64 
(20140204)
  MachineType: ASUSTeK COMPUTER INC. UX32A
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-109-generic 
root=UUID=1e3c78e2-1a6e-4afe-8249-40fe7fa81a86 ro quiet splash vt.handoff=7
  SourcePackage: mesa
  UpgradeStatus: Upgraded to xenial on 2017-04-15 (271 days ago)
  dmi.bios.date: 02/12/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX32A.216
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX32A
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX32A.216:bd02/12/2014:svnASUSTeKCOMPUTERINC.:pnUX32A:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX32A:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: UX32A
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.83-1~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu1~16.04.2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~16.04.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Fri Jan 12 20:32:41 2018
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.4-0ubuntu0.7
  xserver.video_driver: intel

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

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

[Desktop-packages] [Bug 1741671] Re: nvidia-340 340.102-0ubuntu0.16.04.2: nvidia-340 kernel module failed to build [nv-linux.h:199:2: error: #error "This driver requires the ability to change memory t

[Matt Austin]

Thank you - I can confirm that installing nvidia-340 from xenial-
proposed resolved this 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/1741671

Title:
  nvidia-340 340.102-0ubuntu0.16.04.2: nvidia-340 kernel module failed
  to build [nv-linux.h:199:2: error: #error "This driver requires the
  ability to change memory types!"]

Status in linux-hwe package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Confirmed

Bug description:
  not compiling after installation of linux-image-4.13.0-21-generic

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: nvidia-340 340.102-0ubuntu0.16.04.2
  ProcVersionSignature: Ubuntu 4.4.0-97.120-generic 4.4.87
  Uname: Linux 4.4.0-97-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  340.102  Mon Jan 16 13:06:29 
PST 2017
   GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.5)
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  DKMSKernelVersion: 4.13.0-21-generic
  Date: Sat Jan  6 18:36:58 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DuplicateSignature: 
dkms:nvidia-340:340.102-0ubuntu0.16.04.2:/var/lib/dkms/nvidia-340/340.102/build/nv-linux.h:199:2:
 error: #error "This driver requires the ability to change memory types!"
  GraphicsCard:
   NVIDIA Corporation GT216M [GeForce GT 230M] [10de:0a28] (rev a2) (prog-if 00 
[VGA controller])
 Subsystem: Hewlett-Packard Company GT216M [GeForce GT 230M] [103c:363c]
  InstallationDate: Installed on 2016-04-26 (619 days ago)
  InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release amd64 
(20160217.1)
  MachineType: Hewlett-Packard HP Pavilion dv7 Notebook PC
  PackageVersion: 340.102-0ubuntu0.16.04.2
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-97-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.3
   apt  1.2.24
  SourcePackage: nvidia-graphics-drivers-340
  Title: nvidia-340 340.102-0ubuntu0.16.04.2: nvidia-340 kernel module failed 
to build
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/05/2010
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.1D
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 363C
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 32.25
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.1D:bd10/05/2010:svnHewlett-Packard:pnHPPaviliondv7NotebookPC:pvr039E202413102:rvnHewlett-Packard:rn363C:rvr32.25:cvnHewlett-Packard:ct10:cvrN/A:
  dmi.product.name: HP Pavilion dv7 Notebook PC
  dmi.product.version: 039E202413102
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.83-1~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu1~16.04.2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~16.04.2
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Sat Jan  6 18:17:29 2018
  xserver.configfile: default
  xserver.errors: open /dev/fb0: No such file or directory
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.18.4-0ubuntu0.7

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

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

[Desktop-packages] [Bug 1741671] Re: nvidia-340 340.102-0ubuntu0.16.04.2: nvidia-340 kernel module failed to build [nv-linux.h:199:2: error: #error "This driver requires the ability to change memory t

[Matt Austin]

Possible duplicate of #1724872.

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

Title:
  nvidia-340 340.102-0ubuntu0.16.04.2: nvidia-340 kernel module failed
  to build [nv-linux.h:199:2: error: #error "This driver requires the
  ability to change memory types!"]

Status in linux-hwe package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Confirmed

Bug description:
  not compiling after installation of linux-image-4.13.0-21-generic

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: nvidia-340 340.102-0ubuntu0.16.04.2
  ProcVersionSignature: Ubuntu 4.4.0-97.120-generic 4.4.87
  Uname: Linux 4.4.0-97-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  340.102  Mon Jan 16 13:06:29 
PST 2017
   GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.5)
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  DKMSKernelVersion: 4.13.0-21-generic
  Date: Sat Jan  6 18:36:58 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DuplicateSignature: 
dkms:nvidia-340:340.102-0ubuntu0.16.04.2:/var/lib/dkms/nvidia-340/340.102/build/nv-linux.h:199:2:
 error: #error "This driver requires the ability to change memory types!"
  GraphicsCard:
   NVIDIA Corporation GT216M [GeForce GT 230M] [10de:0a28] (rev a2) (prog-if 00 
[VGA controller])
 Subsystem: Hewlett-Packard Company GT216M [GeForce GT 230M] [103c:363c]
  InstallationDate: Installed on 2016-04-26 (619 days ago)
  InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release amd64 
(20160217.1)
  MachineType: Hewlett-Packard HP Pavilion dv7 Notebook PC
  PackageVersion: 340.102-0ubuntu0.16.04.2
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-97-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.3
   apt  1.2.24
  SourcePackage: nvidia-graphics-drivers-340
  Title: nvidia-340 340.102-0ubuntu0.16.04.2: nvidia-340 kernel module failed 
to build
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/05/2010
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.1D
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 363C
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 32.25
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.1D:bd10/05/2010:svnHewlett-Packard:pnHPPaviliondv7NotebookPC:pvr039E202413102:rvnHewlett-Packard:rn363C:rvr32.25:cvnHewlett-Packard:ct10:cvrN/A:
  dmi.product.name: HP Pavilion dv7 Notebook PC
  dmi.product.version: 039E202413102
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.83-1~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu1~16.04.2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~16.04.2
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Sat Jan  6 18:17:29 2018
  xserver.configfile: default
  xserver.errors: open /dev/fb0: No such file or directory
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.18.4-0ubuntu0.7

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

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

[Desktop-packages] [Bug 1743078] [NEW] package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to install/upgrade: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is different from o

[John Morgan]

Public bug reported:

This crash happened after the installation of wine, during the initial
running of "winecfg. Wine was installed from this source:
https://wiki.winehq.org/Ubuntu

ProblemType: Package
DistroRelease: Ubuntu 17.10
Package: libsane1 1.0.27-1~experimental2ubuntu2.1
ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
Uname: Linux 4.13.0-25-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.7
Architecture: amd64
Date: Fri Jan 12 23:57:40 2018
DuplicateSignature:
 package:libsane1:1.0.27-1~experimental2ubuntu2.1
 Unpacking libsane1:i386 (1.0.27-1~experimental2ubuntu2.1) ...
 dpkg: error processing archive 
/tmp/apt-dpkg-install-NwGq9n/137-libsane1_1.0.27-1~experimental2ubuntu2.1_i386.deb
 (--unpack):
  trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is 
different from other instances of package libsane1:i386
ErrorMessage: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which 
is different from other instances of package libsane1:i386
InstallationDate: Installed on 2017-12-20 (23 days ago)
InstallationMedia: Lubuntu 17.10 "Artful Aardvark" - Release amd64 (20171017.1)
Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
RelatedPackageVersions:
 dpkg 1.18.24ubuntu1
 apt  1.5.1
SourcePackage: sane-backends
Title: package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to 
install/upgrade: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', 
which is different from other instances of package libsane1:i386
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: sane-backends (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package artful package-conflict

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

Title:
  package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to
  install/upgrade: trying to overwrite shared
  '/lib/udev/hwdb.d/20-sane.hwdb', which is different from other
  instances of package libsane1:i386

Status in sane-backends package in Ubuntu:
  New

Bug description:
  This crash happened after the installation of wine, during the initial
  running of "winecfg. Wine was installed from this source:
  https://wiki.winehq.org/Ubuntu

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: libsane1 1.0.27-1~experimental2ubuntu2.1
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  Uname: Linux 4.13.0-25-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  Date: Fri Jan 12 23:57:40 2018
  DuplicateSignature:
   package:libsane1:1.0.27-1~experimental2ubuntu2.1
   Unpacking libsane1:i386 (1.0.27-1~experimental2ubuntu2.1) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-NwGq9n/137-libsane1_1.0.27-1~experimental2ubuntu2.1_i386.deb
 (--unpack):
trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is 
different from other instances of package libsane1:i386
  ErrorMessage: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', 
which is different from other instances of package libsane1:i386
  InstallationDate: Installed on 2017-12-20 (23 days ago)
  InstallationMedia: Lubuntu 17.10 "Artful Aardvark" - Release amd64 
(20171017.1)
  Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
  RelatedPackageVersions:
   dpkg 1.18.24ubuntu1
   apt  1.5.1
  SourcePackage: sane-backends
  Title: package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to 
install/upgrade: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', 
which is different from other instances of package libsane1:i386
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1743078] Re: package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to install/upgrade: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is different from oth

[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 sane-backends in Ubuntu.
https://bugs.launchpad.net/bugs/1743078

Title:
  package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to
  install/upgrade: trying to overwrite shared
  '/lib/udev/hwdb.d/20-sane.hwdb', which is different from other
  instances of package libsane1:i386

Status in sane-backends package in Ubuntu:
  New

Bug description:
  This crash happened after the installation of wine, during the initial
  running of "winecfg. Wine was installed from this source:
  https://wiki.winehq.org/Ubuntu

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: libsane1 1.0.27-1~experimental2ubuntu2.1
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  Uname: Linux 4.13.0-25-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  Date: Fri Jan 12 23:57:40 2018
  DuplicateSignature:
   package:libsane1:1.0.27-1~experimental2ubuntu2.1
   Unpacking libsane1:i386 (1.0.27-1~experimental2ubuntu2.1) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-NwGq9n/137-libsane1_1.0.27-1~experimental2ubuntu2.1_i386.deb
 (--unpack):
trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is 
different from other instances of package libsane1:i386
  ErrorMessage: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', 
which is different from other instances of package libsane1:i386
  InstallationDate: Installed on 2017-12-20 (23 days ago)
  InstallationMedia: Lubuntu 17.10 "Artful Aardvark" - Release amd64 
(20171017.1)
  Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
  RelatedPackageVersions:
   dpkg 1.18.24ubuntu1
   apt  1.5.1
  SourcePackage: sane-backends
  Title: package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to 
install/upgrade: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', 
which is different from other instances of package libsane1:i386
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1743074] Re: package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to install/upgrade: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is different from oth

[dino99]

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

** This bug is no longer a duplicate of bug 1743073
   package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to install/upgrade: 
trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is different 
from other instances of package libsane1:i386
** This bug has been marked a duplicate of bug 1725928
   package libsane1 1.0.27-1~experimental2ubuntu1: multiarch packages with 
differing files

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

Title:
  package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to
  install/upgrade: trying to overwrite shared
  '/lib/udev/hwdb.d/20-sane.hwdb', which is different from other
  instances of package libsane1:i386

Status in sane-backends package in Ubuntu:
  New

Bug description:
  package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to
  install/upgrade: trying to overwrite shared
  '/lib/udev/hwdb.d/20-sane.hwdb', which is different from other
  instances of package libsane1:i386

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: libsane1 1.0.27-1~experimental2ubuntu2.1
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  Uname: Linux 4.13.0-25-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  Date: Fri Jan 12 20:19:24 2018
  DuplicateSignature:
   package:libsane1:1.0.27-1~experimental2ubuntu2.1
   Unpacking libsane1:i386 (1.0.27-1~experimental2ubuntu2.1) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-IlNQjb/137-libsane1_1.0.27-1~experimental2ubuntu2.1_i386.deb
 (--unpack):
trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is 
different from other instances of package libsane1:i386
  ErrorMessage: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', 
which is different from other instances of package libsane1:i386
  InstallationDate: Installed on 2018-01-12 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
  RelatedPackageVersions:
   dpkg 1.18.24ubuntu1
   apt  1.5.1
  SourcePackage: sane-backends
  Title: package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to 
install/upgrade: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', 
which is different from other instances of package libsane1:i386
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1743073] Re: package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to install/upgrade: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is different from oth

[dino99]

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

** This bug has been marked a duplicate of bug 1725928
   package libsane1 1.0.27-1~experimental2ubuntu1: multiarch packages with 
differing files

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

Title:
  package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to
  install/upgrade: trying to overwrite shared
  '/lib/udev/hwdb.d/20-sane.hwdb', which is different from other
  instances of package libsane1:i386

Status in sane-backends package in Ubuntu:
  New

Bug description:
  package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to
  install/upgrade: trying to overwrite shared
  '/lib/udev/hwdb.d/20-sane.hwdb', which is different from other
  instances of package libsane1:i386

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: libsane1 1.0.27-1~experimental2ubuntu2.1
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  Uname: Linux 4.13.0-25-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  Date: Fri Jan 12 20:19:24 2018
  DuplicateSignature:
   package:libsane1:1.0.27-1~experimental2ubuntu2.1
   Unpacking libsane1:i386 (1.0.27-1~experimental2ubuntu2.1) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-IlNQjb/137-libsane1_1.0.27-1~experimental2ubuntu2.1_i386.deb
 (--unpack):
trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is 
different from other instances of package libsane1:i386
  ErrorMessage: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', 
which is different from other instances of package libsane1:i386
  InstallationDate: Installed on 2018-01-12 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
  RelatedPackageVersions:
   dpkg 1.18.24ubuntu1
   apt  1.5.1
  SourcePackage: sane-backends
  Title: package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to 
install/upgrade: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', 
which is different from other instances of package libsane1:i386
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1743073] Re: package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to install/upgrade: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is different from oth

[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 sane-backends in Ubuntu.
https://bugs.launchpad.net/bugs/1743073

Title:
  package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to
  install/upgrade: trying to overwrite shared
  '/lib/udev/hwdb.d/20-sane.hwdb', which is different from other
  instances of package libsane1:i386

Status in sane-backends package in Ubuntu:
  New

Bug description:
  package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to
  install/upgrade: trying to overwrite shared
  '/lib/udev/hwdb.d/20-sane.hwdb', which is different from other
  instances of package libsane1:i386

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: libsane1 1.0.27-1~experimental2ubuntu2.1
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  Uname: Linux 4.13.0-25-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  Date: Fri Jan 12 20:19:24 2018
  DuplicateSignature:
   package:libsane1:1.0.27-1~experimental2ubuntu2.1
   Unpacking libsane1:i386 (1.0.27-1~experimental2ubuntu2.1) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-IlNQjb/137-libsane1_1.0.27-1~experimental2ubuntu2.1_i386.deb
 (--unpack):
trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is 
different from other instances of package libsane1:i386
  ErrorMessage: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', 
which is different from other instances of package libsane1:i386
  InstallationDate: Installed on 2018-01-12 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
  RelatedPackageVersions:
   dpkg 1.18.24ubuntu1
   apt  1.5.1
  SourcePackage: sane-backends
  Title: package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to 
install/upgrade: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', 
which is different from other instances of package libsane1:i386
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1743074] Re: package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to install/upgrade: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is different from oth

[Apport retracing service]

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

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 #1743073, so is being marked as such.  Please
look at the other bug report to see if there is any missing information
that you can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report.  Please continue to report any other bugs you may
find.

** Tags removed: need-duplicate-check

** This bug has been marked a duplicate of bug 1743073
   package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to install/upgrade: 
trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is different 
from other instances of package libsane1:i386

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

Title:
  package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to
  install/upgrade: trying to overwrite shared
  '/lib/udev/hwdb.d/20-sane.hwdb', which is different from other
  instances of package libsane1:i386

Status in sane-backends package in Ubuntu:
  New

Bug description:
  package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to
  install/upgrade: trying to overwrite shared
  '/lib/udev/hwdb.d/20-sane.hwdb', which is different from other
  instances of package libsane1:i386

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: libsane1 1.0.27-1~experimental2ubuntu2.1
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  Uname: Linux 4.13.0-25-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  Date: Fri Jan 12 20:19:24 2018
  DuplicateSignature:
   package:libsane1:1.0.27-1~experimental2ubuntu2.1
   Unpacking libsane1:i386 (1.0.27-1~experimental2ubuntu2.1) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-IlNQjb/137-libsane1_1.0.27-1~experimental2ubuntu2.1_i386.deb
 (--unpack):
trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is 
different from other instances of package libsane1:i386
  ErrorMessage: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', 
which is different from other instances of package libsane1:i386
  InstallationDate: Installed on 2018-01-12 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
  RelatedPackageVersions:
   dpkg 1.18.24ubuntu1
   apt  1.5.1
  SourcePackage: sane-backends
  Title: package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to 
install/upgrade: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', 
which is different from other instances of package libsane1:i386
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1743073] [NEW] package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to install/upgrade: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is different from o

[mohammad raufzahed]

Public bug reported:

package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to
install/upgrade: trying to overwrite shared
'/lib/udev/hwdb.d/20-sane.hwdb', which is different from other instances
of package libsane1:i386

ProblemType: Package
DistroRelease: Ubuntu 17.10
Package: libsane1 1.0.27-1~experimental2ubuntu2.1
ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
Uname: Linux 4.13.0-25-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.7-0ubuntu3.7
Architecture: amd64
Date: Fri Jan 12 20:19:24 2018
DuplicateSignature:
 package:libsane1:1.0.27-1~experimental2ubuntu2.1
 Unpacking libsane1:i386 (1.0.27-1~experimental2ubuntu2.1) ...
 dpkg: error processing archive 
/tmp/apt-dpkg-install-IlNQjb/137-libsane1_1.0.27-1~experimental2ubuntu2.1_i386.deb
 (--unpack):
  trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is 
different from other instances of package libsane1:i386
ErrorMessage: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which 
is different from other instances of package libsane1:i386
InstallationDate: Installed on 2018-01-12 (0 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
RelatedPackageVersions:
 dpkg 1.18.24ubuntu1
 apt  1.5.1
SourcePackage: sane-backends
Title: package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to 
install/upgrade: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', 
which is different from other instances of package libsane1:i386
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: sane-backends (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package artful package-conflict

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

Title:
  package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to
  install/upgrade: trying to overwrite shared
  '/lib/udev/hwdb.d/20-sane.hwdb', which is different from other
  instances of package libsane1:i386

Status in sane-backends package in Ubuntu:
  New

Bug description:
  package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to
  install/upgrade: trying to overwrite shared
  '/lib/udev/hwdb.d/20-sane.hwdb', which is different from other
  instances of package libsane1:i386

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: libsane1 1.0.27-1~experimental2ubuntu2.1
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  Uname: Linux 4.13.0-25-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  Date: Fri Jan 12 20:19:24 2018
  DuplicateSignature:
   package:libsane1:1.0.27-1~experimental2ubuntu2.1
   Unpacking libsane1:i386 (1.0.27-1~experimental2ubuntu2.1) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-IlNQjb/137-libsane1_1.0.27-1~experimental2ubuntu2.1_i386.deb
 (--unpack):
trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is 
different from other instances of package libsane1:i386
  ErrorMessage: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', 
which is different from other instances of package libsane1:i386
  InstallationDate: Installed on 2018-01-12 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
  RelatedPackageVersions:
   dpkg 1.18.24ubuntu1
   apt  1.5.1
  SourcePackage: sane-backends
  Title: package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to 
install/upgrade: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', 
which is different from other instances of package libsane1:i386
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1743074] [NEW] package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to install/upgrade: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is different from o

[mohammad raufzahed]

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

Public bug reported:

package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to
install/upgrade: trying to overwrite shared
'/lib/udev/hwdb.d/20-sane.hwdb', which is different from other instances
of package libsane1:i386

ProblemType: Package
DistroRelease: Ubuntu 17.10
Package: libsane1 1.0.27-1~experimental2ubuntu2.1
ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
Uname: Linux 4.13.0-25-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.7-0ubuntu3.7
Architecture: amd64
Date: Fri Jan 12 20:19:24 2018
DuplicateSignature:
 package:libsane1:1.0.27-1~experimental2ubuntu2.1
 Unpacking libsane1:i386 (1.0.27-1~experimental2ubuntu2.1) ...
 dpkg: error processing archive 
/tmp/apt-dpkg-install-IlNQjb/137-libsane1_1.0.27-1~experimental2ubuntu2.1_i386.deb
 (--unpack):
  trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is 
different from other instances of package libsane1:i386
ErrorMessage: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which 
is different from other instances of package libsane1:i386
InstallationDate: Installed on 2018-01-12 (0 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
RelatedPackageVersions:
 dpkg 1.18.24ubuntu1
 apt  1.5.1
SourcePackage: sane-backends
Title: package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to 
install/upgrade: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', 
which is different from other instances of package libsane1:i386
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: sane-backends (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package artful package-conflict

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

Title:
  package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to
  install/upgrade: trying to overwrite shared
  '/lib/udev/hwdb.d/20-sane.hwdb', which is different from other
  instances of package libsane1:i386

Status in sane-backends package in Ubuntu:
  New

Bug description:
  package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to
  install/upgrade: trying to overwrite shared
  '/lib/udev/hwdb.d/20-sane.hwdb', which is different from other
  instances of package libsane1:i386

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: libsane1 1.0.27-1~experimental2ubuntu2.1
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  Uname: Linux 4.13.0-25-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  Date: Fri Jan 12 20:19:24 2018
  DuplicateSignature:
   package:libsane1:1.0.27-1~experimental2ubuntu2.1
   Unpacking libsane1:i386 (1.0.27-1~experimental2ubuntu2.1) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-IlNQjb/137-libsane1_1.0.27-1~experimental2ubuntu2.1_i386.deb
 (--unpack):
trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is 
different from other instances of package libsane1:i386
  ErrorMessage: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', 
which is different from other instances of package libsane1:i386
  InstallationDate: Installed on 2018-01-12 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
  RelatedPackageVersions:
   dpkg 1.18.24ubuntu1
   apt  1.5.1
  SourcePackage: sane-backends
  Title: package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to 
install/upgrade: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', 
which is different from other instances of package libsane1:i386
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1742867] Re: Screen blank, audio choppy, system locked

[clickwir]

Happened again after just a few minutes of watching. Tried not watching
YouTube for a while and it was fine for about 20 mins.


 dmesg 

[ 2441.656816] clocksource: timekeeping watchdog on CPU2: Marking clocksource 
'tsc' as unstable because the skew is too large:
[ 2441.656819] clocksource:   'hpet' wd_now: 23e5cdb2 
wd_last: 2300b853 mask: 
[ 2441.656820] clocksource:   'tsc' cs_now: 7e4398e6b37 
cs_last: 7e389faed6b mask: 
[ 2441.656822] tsc: Marking TSC unstable due to clocksource watchdog
[ 2446.689848] hrtimer: interrupt took 1048512639 ns
[ 2450.464784] nfs: server 10.1.0.4 not responding, still trying
[ 2461.579468] sched: RT throttling activated
[ 2462.627985] INFO: NMI handler (perf_ibs_nmi_handler) took too long to run: 
419.422 msecs
[ 2462.627988] INFO: NMI handler (perf_event_nmi_handler) took too long to run: 
838.852 msecs
[ 2462.627990] perf: interrupt took too long (6553849 > 4096258), lowering 
kernel.perf_event_max_sample_rate to 250
[ 2464.305681] watchdog: BUG: soft lockup - CPU#2 stuck for 23s! 
[kworker/u16:1:4770]
[ 2464.305684] Modules linked in: xt_CHECKSUM iptable_mangle ipt_MASQUERADE 
nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 nf_nat nf_conntrack_ipv4 
nf_defrag_ipv4 xt_conntrack nf_conntrack libcrc32c ipt_REJECT nf_reject_ipv4 
xt_tcpudp bridge stp llc ebtable_filter ebtables ip6table_filter ip6_tables 
iptable_filter nfsv3 nfs_acl cfg80211 rpcsec_gss_krb5 auth_rpcgss nfsv4 nfs 
lockd grace fscache zram binfmt_misc nls_iso8859_1 snd_hda_codec_hdmi 
edac_mce_amd kvm_amd kvm irqbypass crct10dif_pclmul crc32_pclmul 
ghash_clmulni_intel pcbc input_leds aesni_intel aes_x86_64 crypto_simd 
glue_helper cryptd eeepc_wmi asus_wmi sparse_keymap video snd_hda_intel 
snd_ctxfi snd_hda_codec k10temp snd_hda_core wmi_bmof snd_hwdep fam15h_power 
snd_pcm snd_seq_midi snd_seq_midi_event i2c_piix4 snd_rawmidi snd_seq 
snd_seq_device
[ 2464.305717]  snd_timer snd soundcore shpchp mac_hid bonding parport_pc ppdev 
sunrpc lp parport ip_tables x_tables autofs4 btrfs xor raid6_pq hid_generic 
usbhid hid amdkfd amd_iommu_v2 radeon i2c_algo_bit ttm drm_kms_helper e1000e 
syscopyarea sysfillrect firewire_ohci sysimgblt ptp fb_sys_fops pps_core 
firewire_core crc_itu_t drm ahci r8169 libahci mii wmi
[ 2464.305738] CPU: 2 PID: 4770 Comm: kworker/u16:1 Not tainted 
4.13.0-25-generic #29-Ubuntu
[ 2464.305739] Hardware name: To be filled by O.E.M. To be filled by 
O.E.M./M5A97 EVO, BIOS 1604 10/16/2012
[ 2464.305765] Workqueue: events_power_efficient radeon_fence_check_lockup 
[radeon]
[ 2464.305766] task: 9a5eeb535d00 task.stack: b3d203218000
[ 2464.305788] RIP: 0010:evergreen_is_display_hung+0x125/0x1b0 [radeon]
[ 2464.305789] RSP: 0018:b3d20321bd80 EFLAGS: 0286 ORIG_RAX: 
ff10
[ 2464.305791] RAX:  RBX: 0001 RCX: 
[ 2464.305792] RDX:  RSI: 6ea0 RDI: 000550ba
[ 2464.305792] RBP: b3d20321bdd8 R08: 0001 R09: 
[ 2464.305793] R10: 9a5f18678000 R11:  R12: 9a5f18678000
[ 2464.305794] R13: 0004 R14: 003f R15: 0001
[ 2464.305795] FS:  () GS:9a5f3ec8() 
knlGS:
[ 2464.305796] CS:  0010 DS:  ES:  CR0: 80050033
[ 2464.305797] CR2: 7faff1182000 CR3: 00061a4ca000 CR4: 000406e0
[ 2464.305798] Call Trace:
[ 2464.305822]  evergreen_gpu_check_soft_reset+0xc5/0x120 [radeon]
[ 2464.305843]  evergreen_gfx_is_lockup+0x17/0x40 [radeon]
[ 2464.305859]  radeon_fence_check_lockup+0x93/0x180 [radeon]
[ 2464.305862]  process_one_work+0x1e7/0x410
[ 2464.305864]  worker_thread+0x4b/0x420
[ 2464.305866]  kthread+0x125/0x140
[ 2464.305868]  ? process_one_work+0x410/0x410
[ 2464.305869]  ? kthread_create_on_node+0x70/0x70
[ 2464.305872]  ret_from_fork+0x1f/0x30
[ 2464.305873] Code: ca 8b 04 95 40 50 6d c0 05 a0 6e 00 00 49 3b 84 24 b0 01 
00 00 48 89 c6 72 07 3d ff ff 00 00 77 41 49 03 84 24 e8 01 00 00 8b 00 <39> 44 
95 b8 74 05 f7 d3 41 21 de 83 c1 01 41 39 8c 24 98 26 00 
[ 2466.612565] watchdog: BUG: soft lockup - CPU#7 stuck for 25s! 
[kworker/7:1:79]
[ 2466.612569] Modules linked in: xt_CHECKSUM iptable_mangle ipt_MASQUERADE 
nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 nf_nat nf_conntrack_ipv4 
nf_defrag_ipv4 xt_conntrack nf_conntrack libcrc32c ipt_REJECT nf_reject_ipv4 
xt_tcpudp bridge stp llc ebtable_filter ebtables ip6table_filter ip6_tables 
iptable_filter nfsv3 nfs_acl cfg80211 rpcsec_gss_krb5 auth_rpcgss nfsv4 nfs 
lockd grace fscache zram binfmt_misc nls_iso8859_1 snd_hda_codec_hdmi 
edac_mce_amd kvm_amd kvm irqbypass crct10dif_pclmul crc32_pclmul 
ghash_clmulni_intel pcbc input_leds aesni_intel aes_x86_64 crypto_simd 
glue_helper cryptd eeepc_wmi asus_wmi sparse_keymap video snd_hda_intel 
snd_ctxfi snd_hda_codec k10temp snd_hda_core wmi_bmof snd_hwdep fam15h_power 

[Desktop-packages] [Bug 1726262] Re: 17.10 - flickering overlay patterns in gnome-terminal

[Todd Ross]

This is happening to me too.  It's HUGELY distracting when trying to use
2, 3, or more terminal windows.

I have 3x U2711 monitors hooked up via display port to a R9 Fury, so
hardware doesn't seem to be a commonality.

Thanks for the Gnome Profile Terminal transparency workaround.

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

Title:
  17.10 - flickering overlay patterns in gnome-terminal

Status in gnome-terminal package in Ubuntu:
  Confirmed

Bug description:
  Clean install of Ubuntu 17.10.

  For gnome-terminal select color-scheme "black on light yellow".

  Overlay partly with e.g. Chrome (Browser) or Geany (editor). Then the
  border shadow of the e.g. Geany produces flickering extended shadows
  in the gnome-terminal. Foto with the extended shadows is attached.

  This bug was introduced with 17.10. This flickering didn't appear in
  17.04, 16.10, 16.04...

  Working as a developer with several open terminal windows on the
  desktop, this produces a disturbing desktop environment and mitigated
  by covering not used terminal windows complete with other apps.

  Haven't reproduced with other apps than gnome-terminal.

  Hardware
  Lenovo Thinkpad e330, cpu : Intel(R) Core(TM) i5-3210M CPU @ 2.50GHz
  gpu Builtin : HD 4000

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

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

[Desktop-packages] [Bug 1742867] Re: Screen blank, audio choppy, system locked

[clickwir]

Happened again after watching about 7-9 minutes of YouTube.

 syslog 

Jan 12 21:38:57 mach kernel: [  569.724268] sched: RT throttling activated  
 
Jan 12 21:38:59 mach kernel: [  571.401961] clocksource: timekeeping watchdog 
on CPU2: Marking clocksource 'tsc' as unstable because the skew is too large:   


Jan 12 21:38:59 mach kernel: [  571.401981] clocksource:   
'hpet' wd_now: e7f33546 wd_last: e543f369 mask: 

   
Jan 12 21:38:59 mach kernel: [  571.401986] clocksource:   
'tsc' cs_now: 1ea1fa20651 cs_last: 1e7e50167fd mask:    

   
Jan 12 21:38:59 mach kernel: [  571.401991] tsc: Marking TSC unstable due to 
clocksource watchdog
Jan 12 21:38:59 mach kernel: [  571.403034] TSC found unstable after boot, most 
likely due to broken BIOS. Use 'tsc=unstable'.   
Jan 12 21:38:59 mach kernel: [  571.403037] sched_clock: Marking unstable 
(571388047245, 14818071)<-(571736398266, -66693)   
Jan 12 21:39:06 mach kernel: [  576.435061] INFO: NMI handler 
(nmi_cpu_backtrace_handler) took too long to run: 209.713 msecs
Jan 12 21:39:06 mach kernel: [  576.435064] INFO: NMI handler 
(perf_event_nmi_handler) took too long to run: 1258.275 msecs  
Jan 12 21:39:06 mach kernel: [  576.435065] perf: interrupt took too long 
(9830397 > 2500), lowering kernel.perf_event_max_sample_rate to 250 


Jan 12 21:39:06 mach rtkit-daemon[2525]: The canary thread is apparently 
starving. Taking action.
Jan 12 21:39:06 mach rtkit-daemon[2525]: Demoting known real-time threads.  
 
Jan 12 21:39:06 mach rtkit-daemon[2525]: Successfully demoted thread 2555 of 
process 2523 (n/a). 
Jan 12 21:39:06 mach rtkit-daemon[2525]: Successfully demoted thread 2554 of 
process 2523 (n/a). 
Jan 12 21:39:06 mach rtkit-daemon[2525]: Successfully demoted thread 2523 of 
process 2523 (n/a). 
Jan 12 21:39:06 mach rtkit-daemon[2525]: Demoted 3 threads. 
 
Jan 12 21:39:43 mach kernel: [  594.681033] INFO: NMI handler 
(nmi_cpu_backtrace_handler) took too long to run: 419.422 msecs
Jan 12 21:39:43 mach kernel: [  597.617006] hrtimer: interrupt took 1258213518 
ns
Jan 12 21:39:43 mach kernel: [  604.118141] watchdog: BUG: soft lockup - CPU#7 
stuck for 21s! [ksoftirqd/7:52]   
Jan 12 21:39:43 mach kernel: [  604.118144] Modules linked in: xt_CHECKSUM 
iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 
nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack libcrc32c 
ipt_REJECT nf_reject_ipv4 xt_tcpudp bridge stp llc ebtable_filter ebtables 
ip6table_filter ip6_tables iptable_filter nfsv3 nfs_acl cfg80211 
rpcsec_gss_krb5 auth_rpcgss nfsv4 nfs lockd grace fscache zram binfmt_misc 
nls_iso8859_1 edac_mce_amd kvm_amd snd_hda_codec_hdmi kvm irqbypass 
crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc input_leds eeepc_wmi 
asus_wmi sparse_keymap aesni_intel aes_x86_64 crypto_simd glue_helper cryptd 
video wmi_bmof k10temp fam15h_power snd_hda_intel snd_hda_codec snd_hda_core 
snd_hwdep snd_ctxfi snd_pcm snd_seq_midi i2c_piix4 snd_seq_midi_event 
snd_rawmidi snd_seq snd_seq_device
Jan 12 21:39:43 mach kernel: [  604.118183]  snd_timer snd soundcore shpchp 
mac_hid bonding parport_pc ppdev lp parport sunrpc ip_tables x_tables autofs4 
btrfs xor raid6_pq hid_generic amdkfd usbhid hid amd_iommu_v2 radeon 
i2c_algo_bit ttm firewire_ohci drm_kms_helper e1000e syscopyarea sysfillrect 
sysimgblt firewire_core fb_sys_fops ptp crc_itu_t drm pps_core ahci r8169 
libahci mii wmi
Jan 12 21:39:43 mach kernel: [  604.118205] CPU: 7 PID: 52 Comm: ksoftirqd/7 
Not tainted 4.13.0-25-generic #29-Ubuntu
Jan 12 21:39:43 mach kernel: [  604.118206] Hardware name: To be filled by 
O.E.M. To be filled by O.E.M./M5A97 EVO, BIOS 1604 10/16/2012
Jan 12 21:39:43 mach kernel: [  604.118207] task: 90bda2925d00 task.stack: 
a067c330
Jan 12 21:39:43 mach kernel: [  604.118212] RIP: 
0010:_raw_spin_unlock_irqrestore+0x15/0x20
Jan 12 21:39:43 mach kernel: [  604.118213] RSP: 0018:a067c3303d40 EFLAGS: 
0286 ORIG_RAX: ff10

[Desktop-packages] [Bug 1731460] Re: Click on desktop folders

[Launchpad Bug Tracker]

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

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

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

Title:
  Click on desktop folders

Status in nautilus package in Ubuntu:
  Expired

Bug description:
  On my Ubuntu 17.10, sometimes when I click (double click) on a folder
  on the gnome desktop, nautilus doesn't start showing the directory
  content.

  Nautilus version is 1:3.26.0-0ubuntu1

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

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

[Desktop-packages] [Bug 1731428] Re: gnome-session-binary: Unrecoverable failure in required component org.gnome.SettingsDaemon.Color.desktop

[Launchpad Bug Tracker]

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

** Changed in: gnome-session (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  gnome-session-binary: Unrecoverable failure in required component
  org.gnome.SettingsDaemon.Color.desktop

Status in gnome-session package in Ubuntu:
  Expired

Bug description:
  On Ubuntu 17.10 artful
  gnome-session 3.26.1-0ubuntu6
  gnome-settings-daemon 3.26.1-0ubuntu5

  Nov 10 09:18:44 samsung-ubuntu gnome-session[6947]: 
gnome-session-binary[6947]: WARNING: Application 
'org.gnome.SettingsDaemon.Color.desktop' failed to register before timeout
  Nov 10 09:18:44 samsung-ubuntu gnome-session-binary[6947]: WARNING: 
Application 'org.gnome.SettingsDaemon.Color.desktop' failed to register before 
timeout
  Nov 10 09:18:44 samsung-ubuntu gnome-session-binary[6947]: Unrecoverable 
failure in required component org.gnome.SettingsDaemon.Color.desktop
  Nov 10 09:18:44 samsung-ubuntu gnome-session[6947]: 
gnome-session-binary[6947]: CRITICAL: We failed, but the fail whale is dead. 
Sorry
  Nov 10 09:18:44 samsung-ubuntu gnome-session-binary[6947]: CRITICAL: We 
failed, but the fail whale is dead. Sorry

  There is no other mention of org.gnome.SettingsDaemon.Color.desktop
  before in syslog and kern.log, which is odd.

  However, I found the following lines earlier in syslog regarding 
gnome-settings-daemon:
  Nov 10 09:17:12 samsung-ubuntu gnome-session[6947]: 
gnome-session-binary[6947]: WARNING: Could not parse desktop file 
gnome-settings-daemon.desktop or it references a not found TryExec binary
  Nov 10 09:17:12 samsung-ubuntu gnome-session-binary[6947]: WARNING: Could not 
parse desktop file gnome-settings-daemon.desktop or it references a not found 
TryExec binary

  I'll try to reinstall gnome-settings-daemon.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-settings-daemon 3.26.1-0ubuntu5
  Uname: Linux 4.13.0-16-generic x86_64
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Nov 10 09:18:44 2017

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

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

[Desktop-packages] [Bug 1735594] Re: [regression] compiz crashes after Mesa upgrade

[MeanJim]

As per XXX, after temporarily removing /etc/apt/preferences.d/proposed-
updates, the update installed and so far it seems to be working.  It
still takes a very long time to get to the desktop after logging in
though.

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

Title:
  [regression] compiz crashes after Mesa upgrade

Status in mesa package in Ubuntu:
  Fix Committed
Status in mesa source package in Xenial:
  Fix Committed
Status in mesa source package in Artful:
  Fix Committed

Bug description:
  [Impact]
  When I use the Unity session I automatically get logged out under these 
conditions:

  When I hover with my mouse over any icon of the sidebar.
  When I press the alt key.
  When I press the super key.

  running dmesg after this unwanted logout happens I get following
  information:

  compiz[10616]: segfault at 0 ip 7fbca309feeb sp 7fff5f59a4d0
  error 4 in i965_dri.so[7fbca2af6000+7e4000]

  This is caused by a mesa upgrade, which added a patch for bug #1727401. The 
crasher is reproduced on:
  - gen4 / gen5 Intel
  - if using modesetting X driver, like when xserver-xorg-video-intel is not 
installed, or the HWE stack is installed (xserver-xorg-core-hwe-16.04 defaults 
to modesetting)

  [Test case]
  Log in to Unity, open the dash or try to log out etc. Compiz shouldn't crash.

  [Regression potential]
  The backported patches need to be tested, here for regressions and on 1727401 
that they fix the original bug (again).

  Best to test on a wide array of Intel HW:
  gen4 (965GM/GM45/G45)
  gen5 (Ironlake)
  gen6 (Sandy Bridge)
  gen7 (Bay Trail, Ivy Bridge, Haswell)
  gen8 (Braswell, Broadwell)
  gen9 (Apollo Lake, Skylake, Gemini Lake, Kaby Lake, Coffee Lake)

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

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

[Desktop-packages] [Bug 1735594] Re: [regression] compiz crashes after Mesa upgrade

[Tom Juhasz]

Proposed update fixed issue on gen5 Ironlake hardware (Dell Inspiron
N5040).

libgl1-mesa-dri:
  Installed: 17.2.4-0ubuntu1~16.04.3
  Candidate: 17.2.4-0ubuntu1~16.04.3
  Version table:
 *** 17.2.4-0ubuntu1~16.04.3 400
400 http://us.archive.ubuntu.com/ubuntu xenial-proposed/main amd64 
Packages
100 /var/lib/dpkg/status
 17.2.4-0ubuntu1~16.04.2 500
500 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
 11.2.0-1ubuntu2 500
500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages

Thanks for the quick fix.

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

Title:
  [regression] compiz crashes after Mesa upgrade

Status in mesa package in Ubuntu:
  Fix Committed
Status in mesa source package in Xenial:
  Fix Committed
Status in mesa source package in Artful:
  Fix Committed

Bug description:
  [Impact]
  When I use the Unity session I automatically get logged out under these 
conditions:

  When I hover with my mouse over any icon of the sidebar.
  When I press the alt key.
  When I press the super key.

  running dmesg after this unwanted logout happens I get following
  information:

  compiz[10616]: segfault at 0 ip 7fbca309feeb sp 7fff5f59a4d0
  error 4 in i965_dri.so[7fbca2af6000+7e4000]

  This is caused by a mesa upgrade, which added a patch for bug #1727401. The 
crasher is reproduced on:
  - gen4 / gen5 Intel
  - if using modesetting X driver, like when xserver-xorg-video-intel is not 
installed, or the HWE stack is installed (xserver-xorg-core-hwe-16.04 defaults 
to modesetting)

  [Test case]
  Log in to Unity, open the dash or try to log out etc. Compiz shouldn't crash.

  [Regression potential]
  The backported patches need to be tested, here for regressions and on 1727401 
that they fix the original bug (again).

  Best to test on a wide array of Intel HW:
  gen4 (965GM/GM45/G45)
  gen5 (Ironlake)
  gen6 (Sandy Bridge)
  gen7 (Bay Trail, Ivy Bridge, Haswell)
  gen8 (Braswell, Broadwell)
  gen9 (Apollo Lake, Skylake, Gemini Lake, Kaby Lake, Coffee Lake)

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

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

[Desktop-packages] [Bug 1681202] Re: bbswitch-dkms 0.8-4ubuntu1: bbswitch kernel module failed to build

[Stickles01]

Happened to me during 'sudo apt update && sudo apt upgrade'

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

Title:
  bbswitch-dkms 0.8-4ubuntu1: bbswitch kernel module failed to build

Status in bbswitch package in Ubuntu:
  Confirmed

Bug description:
  bug error, after computer on

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: bbswitch-dkms 0.8-4ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-46.49-generic 4.8.17
  Uname: Linux 4.8.0-46-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  DKMSKernelVersion: 4.8.0-46-generic
  Date: Fri Apr  7 08:24:25 2017
  DuplicateSignature: dkms:bbswitch-dkms:0.8-4ubuntu1:cc1: error: unrecognized 
command line option "-fstack-protector-strong"
  InstallationDate: Installed on 2017-01-07 (92 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  PackageVersion: 0.8-4ubuntu1
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1
   apt  1.3.4
  SourcePackage: bbswitch
  Title: bbswitch-dkms 0.8-4ubuntu1: bbswitch kernel module failed to build
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1743063] [NEW] package libreoffice-style-galaxy 1:5.4.2-0ubuntu0.17.10.1 failed to install/upgrade: El paquete está en un estado grave de inconsistencia - debe reinstalarlo an

[Santiago]

Public bug reported:

trying to install nestopia

ProblemType: Package
DistroRelease: Ubuntu 17.10
Package: libreoffice-style-galaxy 1:5.4.2-0ubuntu0.17.10.1
ProcVersionSignature: Ubuntu 4.13.0-19.22-lowlatency 4.13.13
Uname: Linux 4.13.0-19-lowlatency x86_64
ApportVersion: 2.20.7-0ubuntu3.7
AptOrdering:
 nestopia:amd64: Install
 NULL: ConfigurePending
Architecture: amd64
Date: Fri Jan 12 22:20:26 2018
ErrorMessage: El paquete está en un estado grave de inconsistencia - debe 
reinstalarlo  antes de intentar su configuración.
InstallationDate: Installed on 2017-12-12 (31 days ago)
InstallationMedia: Ubuntu-Studio 17.10 "Artful Aardvark" - Release amd64 
(20171017.1)
PackageArchitecture: all
Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
RelatedPackageVersions:
 dpkg 1.18.24ubuntu1
 apt  1.5.1
SourcePackage: libreoffice
Title: package libreoffice-style-galaxy 1:5.4.2-0ubuntu0.17.10.1 failed to 
install/upgrade: El paquete está en un estado grave de inconsistencia - debe 
reinstalarlo  antes de intentar su configuración.
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package artful

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

Title:
  package libreoffice-style-galaxy 1:5.4.2-0ubuntu0.17.10.1 failed to
  install/upgrade: El paquete está en un estado grave de inconsistencia
  - debe reinstalarlo  antes de intentar su configuración.

Status in libreoffice package in Ubuntu:
  New

Bug description:
  trying to install nestopia

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: libreoffice-style-galaxy 1:5.4.2-0ubuntu0.17.10.1
  ProcVersionSignature: Ubuntu 4.13.0-19.22-lowlatency 4.13.13
  Uname: Linux 4.13.0-19-lowlatency x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  AptOrdering:
   nestopia:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  Date: Fri Jan 12 22:20:26 2018
  ErrorMessage: El paquete está en un estado grave de inconsistencia - debe 
reinstalarlo  antes de intentar su configuración.
  InstallationDate: Installed on 2017-12-12 (31 days ago)
  InstallationMedia: Ubuntu-Studio 17.10 "Artful Aardvark" - Release amd64 
(20171017.1)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
  RelatedPackageVersions:
   dpkg 1.18.24ubuntu1
   apt  1.5.1
  SourcePackage: libreoffice
  Title: package libreoffice-style-galaxy 1:5.4.2-0ubuntu0.17.10.1 failed to 
install/upgrade: El paquete está en un estado grave de inconsistencia - debe 
reinstalarlo  antes de intentar su configuración.
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1743063] Re: package libreoffice-style-galaxy 1:5.4.2-0ubuntu0.17.10.1 failed to install/upgrade: El paquete está en un estado grave de inconsistencia - debe reinstalarlo ante

[Santiago]

e

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

Title:
  package libreoffice-style-galaxy 1:5.4.2-0ubuntu0.17.10.1 failed to
  install/upgrade: El paquete está en un estado grave de inconsistencia
  - debe reinstalarlo  antes de intentar su configuración.

Status in libreoffice package in Ubuntu:
  New

Bug description:
  trying to install nestopia

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: libreoffice-style-galaxy 1:5.4.2-0ubuntu0.17.10.1
  ProcVersionSignature: Ubuntu 4.13.0-19.22-lowlatency 4.13.13
  Uname: Linux 4.13.0-19-lowlatency x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  AptOrdering:
   nestopia:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  Date: Fri Jan 12 22:20:26 2018
  ErrorMessage: El paquete está en un estado grave de inconsistencia - debe 
reinstalarlo  antes de intentar su configuración.
  InstallationDate: Installed on 2017-12-12 (31 days ago)
  InstallationMedia: Ubuntu-Studio 17.10 "Artful Aardvark" - Release amd64 
(20171017.1)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
  RelatedPackageVersions:
   dpkg 1.18.24ubuntu1
   apt  1.5.1
  SourcePackage: libreoffice
  Title: package libreoffice-style-galaxy 1:5.4.2-0ubuntu0.17.10.1 failed to 
install/upgrade: El paquete está en un estado grave de inconsistencia - debe 
reinstalarlo  antes de intentar su configuración.
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1742243] Re: Please merge with Debian unstable 2.2.0-11.1

[Nish Aravamudan]

** Changed in: openexr (Ubuntu)
   Status: In Progress => Fix Committed

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

Title:
  Please merge with Debian unstable 2.2.0-11.1

Status in openexr package in Ubuntu:
  Fix Committed

Bug description:
  TBD

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

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

[Desktop-packages] [Bug 1742243] Re: Please merge with Debian unstable 2.2.0-11.1

[Nish Aravamudan]

openexr (2.2.0-11.1ubuntu1) bionic; urgency=medium

  * Merge with Debian unstable (LP: #1742243). Remaining changes:
- Add ppc64el to the archs where to ignore test results.

 -- Nishanth Aravamudan   Tue, 09 Jan
2018 10:49:25 -0800


** Merge proposal linked:
   
https://code.launchpad.net/~nacc/ubuntu/+source/openexr/+git/openexr/+merge/335904

** Changed in: openexr (Ubuntu)
 Assignee: (unassigned) => Nish Aravamudan (nacc)

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

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

Title:
  Please merge with Debian unstable 2.2.0-11.1

Status in openexr package in Ubuntu:
  In Progress

Bug description:
  TBD

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

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

[Desktop-packages] [Bug 1743058] [NEW] In multiple apps, the input field "jumps"

[Dimitri John Ledkov]

Public bug reported:

It appears there is the font/height rendering issue in multiple places.
With the textentry "jumping" in height slightly upon entering anything.

I have observed this on the login screen password entry screen,
lockscreen entry, and the gnome pin entry for my ssh/gpg smartcard.

It almost feels as if the "dots" of the hidden password are either of
larger font size and/or bold, whilst an empty text field and/or
unfocused text field font is either smaller and or regular (non-bold).
Resulting in a rendering / layout jiggles.

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

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

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


** Tags: regression-release

** Also affects: gnome-shell (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: gnome-keyring (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  In multiple apps, the input field "jumps"

Status in gdm3 package in Ubuntu:
  New
Status in gnome-keyring package in Ubuntu:
  New
Status in gnome-shell package in Ubuntu:
  New

Bug description:
  It appears there is the font/height rendering issue in multiple
  places. With the textentry "jumping" in height slightly upon entering
  anything.

  I have observed this on the login screen password entry screen,
  lockscreen entry, and the gnome pin entry for my ssh/gpg smartcard.

  It almost feels as if the "dots" of the hidden password are either of
  larger font size and/or bold, whilst an empty text field and/or
  unfocused text field font is either smaller and or regular (non-bold).
  Resulting in a rendering / layout jiggles.

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

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

[Desktop-packages] [Bug 1743055] [NEW] Show dock on all screens, should also show the top bar on all screens

[Dimitri John Ledkov]

Public bug reported:

Show dock on all screens settings, should also show the top bar on all
screens (ie the activities, calendar settings bar).

As otherwise I cannot display aps / terminals side by side on two
screens and have them match vertically for comparison etc.

This is a regression from xenial, were in dual-monitor setup both
screens had identical vertical height space.

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


** Tags: regression-release

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

Title:
  Show dock on all screens, should also show the top bar on all screens

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Show dock on all screens settings, should also show the top bar on all
  screens (ie the activities, calendar settings bar).

  As otherwise I cannot display aps / terminals side by side on two
  screens and have them match vertically for comparison etc.

  This is a regression from xenial, were in dual-monitor setup both
  screens had identical vertical height space.

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

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

[Desktop-packages] [Bug 1743054] [NEW] Notifications - disappear, regression since xenial

[Dimitri John Ledkov]

Public bug reported:

In xenial, messenging menu would display hexchat irc highlights e.g.
"#channel1 #channel2 nick1 nick2". Upon clicking one of them, the rest
were preserved.

Now, in gnome-shell, all notifications are cleared. A number bubble
remains, and highlighted channels remain, but it is a lot more difficult
to jump to each highlight, as previously I could could go back to the
messaging menu and click #channel2 to open that hightlight.

I'm not sure if this is a bug in hexchat, gnome-shell, or both.

Is there an IRC client with better / preserving capacity of the
highlights and gnome-shell integration?

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

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


** Tags: regression-release

** Tags added: regression-release

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

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

Title:
  Notifications - disappear, regression since xenial

Status in gnome-shell package in Ubuntu:
  New
Status in hexchat package in Ubuntu:
  New

Bug description:
  In xenial, messenging menu would display hexchat irc highlights e.g.
  "#channel1 #channel2 nick1 nick2". Upon clicking one of them, the rest
  were preserved.

  Now, in gnome-shell, all notifications are cleared. A number bubble
  remains, and highlighted channels remain, but it is a lot more
  difficult to jump to each highlight, as previously I could could go
  back to the messaging menu and click #channel2 to open that
  hightlight.

  I'm not sure if this is a bug in hexchat, gnome-shell, or both.

  Is there an IRC client with better / preserving capacity of the
  highlights and gnome-shell integration?

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

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

[Desktop-packages] [Bug 1741671] Re: nvidia-340 340.102-0ubuntu0.16.04.2: nvidia-340 kernel module failed to build [nv-linux.h:199:2: error: #error "This driver requires the ability to change memory t

[Martin Segado]

Looks like it's already been fixed in xenial-proposed**. As a workaround
until the new version appears in the main repos, open a terminal (Ctrl +
Alt + T) and type:

# Add xenial-proposed source:
echo "deb http://archive.ubuntu.com/ubuntu/ xenial-proposed restricted main 
multiverse universe" \
  | sudo tee /etc/apt/sources.list.d/xenial-proposed.list
sudo apt update

# Install the updated package:
sudo apt -t xenial-proposed install nvidia-340

# Remove xenial-proposed source:
sudo rm /etc/apt/sources.list.d/xenial-proposed.list
sudo apt update

Hope that helps,
Martin

** see https://launchpad.net/ubuntu/+source/nvidia-graphics-
drivers-340/340.104-0ubuntu0.16.04.1

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

Title:
  nvidia-340 340.102-0ubuntu0.16.04.2: nvidia-340 kernel module failed
  to build [nv-linux.h:199:2: error: #error "This driver requires the
  ability to change memory types!"]

Status in linux-hwe package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Confirmed

Bug description:
  not compiling after installation of linux-image-4.13.0-21-generic

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: nvidia-340 340.102-0ubuntu0.16.04.2
  ProcVersionSignature: Ubuntu 4.4.0-97.120-generic 4.4.87
  Uname: Linux 4.4.0-97-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  340.102  Mon Jan 16 13:06:29 
PST 2017
   GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.5)
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  DKMSKernelVersion: 4.13.0-21-generic
  Date: Sat Jan  6 18:36:58 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DuplicateSignature: 
dkms:nvidia-340:340.102-0ubuntu0.16.04.2:/var/lib/dkms/nvidia-340/340.102/build/nv-linux.h:199:2:
 error: #error "This driver requires the ability to change memory types!"
  GraphicsCard:
   NVIDIA Corporation GT216M [GeForce GT 230M] [10de:0a28] (rev a2) (prog-if 00 
[VGA controller])
 Subsystem: Hewlett-Packard Company GT216M [GeForce GT 230M] [103c:363c]
  InstallationDate: Installed on 2016-04-26 (619 days ago)
  InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release amd64 
(20160217.1)
  MachineType: Hewlett-Packard HP Pavilion dv7 Notebook PC
  PackageVersion: 340.102-0ubuntu0.16.04.2
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-97-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.3
   apt  1.2.24
  SourcePackage: nvidia-graphics-drivers-340
  Title: nvidia-340 340.102-0ubuntu0.16.04.2: nvidia-340 kernel module failed 
to build
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/05/2010
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.1D
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 363C
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 32.25
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.1D:bd10/05/2010:svnHewlett-Packard:pnHPPaviliondv7NotebookPC:pvr039E202413102:rvnHewlett-Packard:rn363C:rvr32.25:cvnHewlett-Packard:ct10:cvrN/A:
  dmi.product.name: HP Pavilion dv7 Notebook PC
  dmi.product.version: 039E202413102
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.83-1~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu1~16.04.2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~16.04.2
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Sat Jan  6 18:17:29 2018
  xserver.configfile: default
  xserver.errors: open /dev/fb0: No such file or directory
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  

[Desktop-packages] [Bug 1167492] Re: Editing connections in Network Manager does not update list in nm-applet

[Alex Bigelow]

For any other n00bs like me tearing their hair out, here's a workaround:

cd /etc/NetworkManager/system-connections
rm -rf *
sudo service network-manager restart

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

Title:
  Editing connections in Network Manager does not update list in nm-
  applet

Status in network-manager-applet package in Ubuntu:
  Confirmed

Bug description:
  After deleting connections in Network Manager using "Edit
  Connections..." the list of available networks doesn't update in
  Network Manager.

  For example, if I create multiple Ethernet networks they show up
  immediately in the nm-applet list. However, if I delete them again,
  they don't disappear from the list.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: network-manager-gnome 0.9.8.0-1ubuntu2
  ProcVersionSignature: Ubuntu 3.8.0-17.27-generic 3.8.6
  Uname: Linux 3.8.0-17-generic x86_64
  ApportVersion: 2.9.2-0ubuntu5
  Architecture: amd64
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  Date: Wed Apr 10 14:16:03 2013
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2013-04-10 (0 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130410)
  IpRoute:
   default via 10.142.78.1 dev eth0  proto static 
   10.142.78.0/24 dev eth0  proto kernel  scope link  src 10.142.78.132  metric 
1 
   169.254.0.0/16 dev eth0  scope link  metric 1000
  IwConfig:
   eth0  no wireless extensions.
   
   lono wireless extensions.
  MarkForUpload: True
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  SourcePackage: network-manager-applet
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAME  UUID   TYPE
  TIMESTAMPTIMESTAMP-REAL AUTOCONNECT   READONLY   
DBUS-PATH 
   Auto Wiredee87fc34-fcb5-44d3-bbc8-7e3c126793b8   
802-3-ethernet1365617793   Wed 10 Apr 2013 02:16:33 PM EDTyes   
no /org/freedesktop/NetworkManager/Settings/2
  nmcli-dev:
   DEVICE TYPE  STATE DBUS-PATH 
 
   eth0   802-3-ethernetconnected 
/org/freedesktop/NetworkManager/Devices/0
  nmcli-nm:
   RUNNING VERSIONSTATE   NET-ENABLED   WIFI-HARDWARE   
WIFI   WWAN-HARDWARE   WWAN  
   running 0.9.8.0connected   enabled   enabled 
enabledenabled disabled

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

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

[Desktop-packages] [Bug 1742852] Re: [hostname, Realtek ALC294, Speaker, Internal] No sound at all after windows update

[gabriel]

the sound came back 24h after with no changes done... I have no clue...

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

Title:
  [hostname, Realtek ALC294, Speaker, Internal] No sound at all after
  windows update

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  After a windows update I lost all the sound on my ubuntu machine. It's the 
second time that this happends.
  My sound is unmuted and at a loud level and nothing is comming out of my 
speakers.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.13.0-26.29~16.04.2-generic 4.13.13
  Uname: Linux 4.13.0-26-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gbergeron   2408 F pulseaudio
gbergeron   3656 F alsamixer
  CurrentDesktop: Unity
  Date: Thu Jan 11 22:21:23 2018
  InstallationDate: Installed on 2017-11-29 (43 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   gbergeron   2408 F...m pulseaudio
   /dev/snd/controlC0:  gbergeron   2408 F pulseaudio
gbergeron   3656 F alsamixer
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [hostname, Realtek ALC294, Speaker, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/23/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX430UAR.203
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX430UAR
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX430UAR.203:bd08/23/2017:svnASUSTeKCOMPUTERINC.:pnUX430UAR:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX430UAR:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: UX
  dmi.product.name: UX430UAR
  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/alsa-driver/+bug/1742852/+subscriptions

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

[Desktop-packages] [Bug 1181666] Re: gnome-shell randomly blocks mouse clicks from working in app windows

[Greg]

I have the same issue as well, and the same result as LuisC when I run
`gnome-shell -r`. I also have a touch screen, and interestingly, the
windows still accept input from the touchscreen even when the mouse
point does not work.

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

Title:
  gnome-shell randomly blocks mouse clicks from working in app windows

Status in GNOME Shell:
  Confirmed
Status in Ubuntu GNOME:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  Under GNOME 3, the use of the mouse-click stops occasionally, though I
  can still move the mouse around and can still click on items in the
  Activities screen and the top-bar.

  I can use alt-tab to cycle windows and can still type into already-
  active textboxes in windows, but I cannot click within the windows,
  and the mouse is not picked up at all by the windows.

  I can open the alt-f2 "run command" dialogue, but cannot type into it.

  The workaround I'm using is to open terminal (ctrl-alt-T) and run
  "gnome-shell -r", and restarting that command every time I have the
  problem again.

  Please ask if there's anything I forgot to mention.

  ADDITIONAL: The error tends to happen randomly, but it seems to happen
  upon opening a new window, changing windows, closing windows, or
  opening the activities pane (whether a change of window is thus
  instigated or not)

  ADDITIONAL 2: (sorry, it's early) The other workaround is to log out
  and to log in again, but that is also less than ideal

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: gnome-shell 3.6.3.1-0ubuntu6
  ProcVersionSignature: Ubuntu 3.8.0-22.33-generic 3.8.11
  Uname: Linux 3.8.0-22-generic x86_64
  ApportVersion: 2.9.2-0ubuntu8
  Architecture: amd64
  Date: Sun May 19 07:02:18 2013
  DisplayManager: gdm
  GsettingsChanges:
   b'org.gnome.desktop.interface' b'clock-show-date' b'true'
   b'org.gnome.desktop.interface' b'clock-show-seconds' b'true'
   b'org.gnome.desktop.interface' b'document-font-name' b"'Sans 10'"
   b'org.gnome.desktop.interface' b'font-name' b"'Cantarell 10'"
   b'org.gnome.desktop.interface' b'monospace-font-name' b"'Ubuntu Mono 12'"
  InstallationDate: Installed on 2013-05-04 (14 days ago)
  InstallationMedia: Ubuntu-GNOME 13.04 "Raring Ringtail" - Release amd64 
(20130424)
  MarkForUpload: True
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1661486] Re: nouveau write fault, CTXSW_TIMEOUT, hangs the display

[Konstantin Janojlic]

Has anyone managed to solve this?

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

Title:
  nouveau write fault, CTXSW_TIMEOUT, hangs the display

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

Bug description:
  A few hours after upgrading to the latest kernel and plasma (using apt
  upgrade) in Xenial 16.04LTS, my computer display hung with:

  Feb  2 20:36:16 snorkack kernel: [83600.290217] nouveau :01:00.0: fifo: 
write fault at 27c000 engine 00 [GR] client 0e [GPC0/GPCCS] reason 02 [PTE] 
on channel 2 [007f9a3000 Xorg[1501]]
  Feb  2 20:36:16 snorkack kernel: [83600.290221] nouveau :01:00.0: fifo: 
gr engine fault on channel 2, recovering...
  Feb  2 20:33:42 snorkack colord[1394]: (colord:1394): Cd-WARNING **: failed 
to get session [pid 27934]: No such device or address
  Feb  2 20:36:19 snorkack vmnet-dhcpd: DHCPREQUEST for 192.168.50.128 from 
00:0c:29:d5:2d:15 via vmnet8
  Feb  2 20:36:19 snorkack vmnet-dhcpd: DHCPACK on 192.168.50.128 to 
00:0c:29:d5:2d:15 via vmnet8
  Feb  2 20:36:20 snorkack kernel: [83604.585547] nouveau :01:00.0: fifo: 
SCHED_ERROR 0a [CTXSW_TIMEOUT]
  Feb  2 20:36:20 snorkack kernel: [83604.585553] nouveau :01:00.0: fifo: 
sw engine fault on channel 8, recovering...
  Feb  2 20:36:22 snorkack kernel: [83606.583732] nouveau :01:00.0: fifo: 
runlist 0 update timeout
  Feb  2 20:36:24 snorkack kernel: [83608.880576] nouveau :01:00.0: fifo: 
SCHED_ERROR 0a [CTXSW_TIMEOUT]
  Feb  2 20:36:29 snorkack kernel: [83613.175601] nouveau :01:00.0: fifo: 
SCHED_ERROR 0a [CTXSW_TIMEOUT]
  Feb  2 20:36:33 snorkack kernel: [83617.470624] nouveau :01:00.0: fifo: 
SCHED_ERROR 0a [CTXSW_TIMEOUT]
  Feb  2 20:36:37 snorkack kernel: [83621.765648] nouveau :01:00.0: fifo: 
SCHED_ERROR 0a [CTXSW_TIMEOUT]
  Feb  2 20:36:42 snorkack kernel: [83626.060672] nouveau :01:00.0: fifo: 
SCHED_ERROR 0a [CTXSW_TIMEOUT]
  ...repeats many times...

  I could still log in via SSH but could not unhang the system, so I
  rebooted.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xserver-xorg-video-nouveau 1:1.0.12-1build2
  ProcVersionSignature: Ubuntu 4.4.0-62.83-generic 4.4.40
  Uname: Linux 4.4.0-62-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Thu Feb  2 23:20:22 2017
  InstallationDate: Installed on 2016-09-25 (131 days ago)
  InstallationMedia: Kubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  SourcePackage: xserver-xorg-video-nouveau
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1741902] Re: Drag and drop state may be freezed by rogue application

[dronus]

As I already mentioned, I am aware that nautilus is triggering the
problem. However, no program should be able to bring down the desktop by
doing bad UI operations. Period.

So wether metacity or Xorg or anything I never even heard of is the
right space to solve this issue is out of my reach, because I don't know
their parts in handling drag and drop operations. The developers would
know.

If you tell me "metacity has no part in drag and drop at all", I guess
Xorg is to blame, so you maybe move the bug there?

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

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

Title:
  Drag and drop state may be freezed by rogue application

Status in metacity package in Ubuntu:
  New
Status in nautilus package in Ubuntu:
  New

Bug description:
  I had some issues with nautlilus in the past time, that of cause need
  to be resolved by the nautlilus devs, but it turns out that IO freezes
  (eg. dropped sftp connections) may freeze nautlilus while drag and
  drop operations, and hence freeze metacity in some kind, as d seems
  to lock some control to the participating applications.

  What I do:

  Drag a file from nautilus.

  What happens:

  Nautilus blocks for some reason, eg. dropped sftp connection. The
  mouse pointer stays in dragging state after releasing the mouse
  button. No drop action is executed. Windows can still be bought to
  front by clicking them, but never gain focus and no application
  (besides nautlilus I guess, which is stalled) receives clicks or
  keystrokes. If at some point nautilus crashes in turn, the system
  usability is fully restored. If not, a restart by hard shutdown is
  needed to regain control.

  What should happen:

  If an application fails to commence it's drag and drop interaction,
  the action should be canceled on metacity's behalf. Otherwise any
  rogue application can stop user interaction down to moving the pointer
  around, requiring hard reboot.

  Security considerations:

  Low. The freezed state seems to block screen locking, and may reveal
  an unprotected desktop if the rogue application releases control at
  some point, eg. by crashing.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: metacity 1:3.18.7-0ubuntu0.3
  ProcVersionSignature: Ubuntu 4.4.0-105.128-generic 4.4.98
  Uname: Linux 4.4.0-105-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CurrentDesktop: GNOME-Flashback:Unity
  Date: Mon Jan  8 14:52:41 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-08-23 (503 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  SourcePackage: metacity
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1742894] Re: Scilab does not start after some upgrades on Ubuntu Xenial

[Timo Aaltonen]

Bionic should be affected, but I've pushed a fixed libjogl2-java to
Debian now and it'll get synced later. Next will be SRU uploads to
artful and xenial.

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

Title:
  Scilab does not start after some upgrades on Ubuntu Xenial

Status in Mesa:
  Confirmed
Status in libjogl2-java package in Ubuntu:
  Triaged
Status in mesa package in Ubuntu:
  New
Status in scilab package in Ubuntu:
  New
Status in libjogl2-java source package in Xenial:
  New
Status in mesa source package in Xenial:
  New
Status in scilab source package in Xenial:
  New
Status in libjogl2-java source package in Artful:
  New
Status in mesa source package in Artful:
  New
Status in scilab source package in Artful:
  New
Status in scilab package in Debian:
  New

Bug description:
  Steps to reproduce:
  1. have installed Scilab on Ubuntu Xenial system
  2. install system updates
  3. try to launch Scilab from GUI - it does not start
  4. try to launch Scilab from terminal - it does not start with the following 
output in the terminal:

  $ scilab
  Could not create a Scilab main class. Error:
  Exception in thread "main" java.lang.InternalError: XXX0 profile[1]: GL3bc -> 
profileImpl GL4bc !!! not mapped 
at com.jogamp.opengl.GLProfile.computeProfileMap(GLProfile.java:2071)
at 
com.jogamp.opengl.GLProfile.initProfilesForDeviceCritical(GLProfile.java:1954)
at 
com.jogamp.opengl.GLProfile.initProfilesForDevice(GLProfile.java:1875)
at 
com.jogamp.opengl.GLProfile.initProfilesForDefaultDevices(GLProfile.java:1842)
at com.jogamp.opengl.GLProfile.access$000(GLProfile.java:80)
at com.jogamp.opengl.GLProfile$1.run(GLProfile.java:230)
at java.security.AccessController.doPrivileged(Native Method)
at com.jogamp.opengl.GLProfile.initSingleton(GLProfile.java:216)
at com.jogamp.opengl.GLProfile.getProfileMap(GLProfile.java:2297)
at com.jogamp.opengl.GLProfile.get(GLProfile.java:988)
at com.jogamp.opengl.GLProfile.getDefault(GLProfile.java:722)
at com.jogamp.opengl.GLProfile.getDefault(GLProfile.java:733)
at org.scilab.modules.gui.SwingView.(Unknown Source)
at org.scilab.modules.gui.SwingView.registerSwingView(Unknown Source)
at org.scilab.modules.core.Scilab.(Unknown Source)

  Scilab cannot create Scilab Java Main-Class (we have not been able to
  find the main Scilab class. Check if the Scilab and thirdparty
  packages are available).

  
  Expected results:
  Scilab works normally on Ubuntu 16.04 LTS system.

  Actual results:
  see error above.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: scilab 5.5.2-2ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-104.127-generic 4.4.98
  Uname: Linux 4.4.0-104-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Fri Jan 12 12:02:32 2018
  PackageArchitecture: all
  SourcePackage: scilab
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1743043] Re: Evince sometimes fails to open under Wayland (Protocol error)

[Rasmus Underbjerg Pinnerup]

** Description changed:

  Under Ubuntu 17.10 I find that Evince (3.26.0-1) often fails to open
  when I'm logged on using Wayland. There's no problem using X.
  
  The error is very simple. I double click a PDF file in my file manager
  and expect it to open in Evince (Document Viewer). And mostly that's
  what happens, but after having opened a few files, it just stops working
  for some files.
  
  The error seldom occurs with the first PDF file I open after a reboot,
  but after I've opened a few files, the error pops up, but only for some
  files. Some files I can click and they open in Evince each time, whereas
  other files will never open in Evince. They open fine in other
  applications and under X.
  
  When I try to open the file from the command line, I get the following
  error message:
  
- pinnerup@ergi:~$ evince Dropbox/Litteratur/Sprog/Græsk/Beekes\ \&\ van\ Beek\ 
–\ Etymological\ Dictionary\ of\ Greek.pdf 
+ pinnerup@ergi:~$ evince Dropbox/Litteratur/Sprog/Græsk/Beekes\ \&\ van\ Beek\ 
–\ Etymological\ Dictionary\ of\ Greek.pdf
  Gdk-Message: Error 71 (Protocol error) dispatching to Wayland display.
  
  If I rename the file (e.g. by adding the number "2" to the file name) or
- move it to another dictionary, it opens without problems.
+ move it to another directory, it opens without problems.

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

Title:
  Evince sometimes fails to open under Wayland (Protocol error)

Status in evince package in Ubuntu:
  New

Bug description:
  Under Ubuntu 17.10 I find that Evince (3.26.0-1) often fails to open
  when I'm logged on using Wayland. There's no problem using X.

  The error is very simple. I double click a PDF file in my file manager
  and expect it to open in Evince (Document Viewer). And mostly that's
  what happens, but after having opened a few files, it just stops
  working for some files.

  The error seldom occurs with the first PDF file I open after a reboot,
  but after I've opened a few files, the error pops up, but only for
  some files. Some files I can click and they open in Evince each time,
  whereas other files will never open in Evince. They open fine in other
  applications and under X.

  When I try to open the file from the command line, I get the following
  error message:

  pinnerup@ergi:~$ evince Dropbox/Litteratur/Sprog/Græsk/Beekes\ \&\ van\ Beek\ 
–\ Etymological\ Dictionary\ of\ Greek.pdf
  Gdk-Message: Error 71 (Protocol error) dispatching to Wayland display.

  If I rename the file (e.g. by adding the number "2" to the file name)
  or move it to another directory, it opens without problems.

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

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

[Desktop-packages] [Bug 1743043] [NEW] Evince sometimes fails to open under Wayland (Protocol error)

[Rasmus Underbjerg Pinnerup]

Public bug reported:

Under Ubuntu 17.10 I find that Evince (3.26.0-1) often fails to open
when I'm logged on using Wayland. There's no problem using X.

The error is very simple. I double click a PDF file in my file manager
and expect it to open in Evince (Document Viewer). And mostly that's
what happens, but after having opened a few files, it just stops working
for some files.

The error seldom occurs with the first PDF file I open after a reboot,
but after I've opened a few files, the error pops up, but only for some
files. Some files I can click and they open in Evince each time, whereas
other files will never open in Evince. They open fine in other
applications and under X.

When I try to open the file from the command line, I get the following
error message:

pinnerup@ergi:~$ evince Dropbox/Litteratur/Sprog/Græsk/Beekes\ \&\ van\ Beek\ 
–\ Etymological\ Dictionary\ of\ Greek.pdf 
Gdk-Message: Error 71 (Protocol error) dispatching to Wayland display.

If I rename the file (e.g. by adding the number "2" to the file name) or
move it to another dictionary, it opens without problems.

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

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

Title:
  Evince sometimes fails to open under Wayland (Protocol error)

Status in evince package in Ubuntu:
  New

Bug description:
  Under Ubuntu 17.10 I find that Evince (3.26.0-1) often fails to open
  when I'm logged on using Wayland. There's no problem using X.

  The error is very simple. I double click a PDF file in my file manager
  and expect it to open in Evince (Document Viewer). And mostly that's
  what happens, but after having opened a few files, it just stops
  working for some files.

  The error seldom occurs with the first PDF file I open after a reboot,
  but after I've opened a few files, the error pops up, but only for
  some files. Some files I can click and they open in Evince each time,
  whereas other files will never open in Evince. They open fine in other
  applications and under X.

  When I try to open the file from the command line, I get the following
  error message:

  pinnerup@ergi:~$ evince Dropbox/Litteratur/Sprog/Græsk/Beekes\ \&\ van\ Beek\ 
–\ Etymological\ Dictionary\ of\ Greek.pdf 
  Gdk-Message: Error 71 (Protocol error) dispatching to Wayland display.

  If I rename the file (e.g. by adding the number "2" to the file name)
  or move it to another dictionary, it opens without problems.

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

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

[Desktop-packages] [Bug 1736011] Re: CRITICAL: Unable to create a DBus proxy for GnomeScreensaver: Error calling StartServiceByName for org.gnome.ScreenSaver: GDBus.Error:org.freedesktop.DBus.Error.Sp

[hamid]

I too have the error displayed in the original bug.

I intentionally waited a good few seconds before logging in to help with
the log timestamps, my machine boots in ~3-5 seconds. No matter how long
I wait after boot before logging in, it always takes the same time to
show the desktop.

My login delay appears to be at this point.

Jan 12 20:53:53 Freyja rtkit-daemon[1975]: Successfully made thread 2798 of 
process 2798 (n/a) owned by '1000' high priority at nice level -11.
Jan 12 20:53:53 Freyja rtkit-daemon[1975]: Supervising 1 threads of 1 processes 
of 2 users.
Jan 12 20:54:07 Freyja rtkit-daemon[1975]: Supervising 1 threads of 1 processes 
of 2 users.


Just before all this, there is a lot of logging from gdm-x-session 
"configuring" my displays or something.

Those ~200 lines of gdm-x-session occur within about a 2 second period
(not much), just before this delay seen here. To my untrained eye it's
hard to see where the log relates to the login delay, but if it looks
like

As with yolen, I am also running "high res" displays, 3 x 3840x2160, 2 x
DP, 1 x HDMI and the Nvidia drivers and related hog a good proportion of
the log.

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

Title:
  CRITICAL: Unable to create a DBus proxy for GnomeScreensaver: Error
  calling StartServiceByName for org.gnome.ScreenSaver:
  GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process
  org.gnome.ScreenSaver exited with status 1

Status in gnome-session package in Ubuntu:
  Confirmed

Bug description:
  That error is logged:

  gnome-session[895]: gnome-session-binary[895]: CRITICAL: Unable to
  create a DBus proxy for GnomeScreensaver: Error calling
  StartServiceByName for org.gnome.ScreenSaver:
  GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process
  org.gnome.ScreenSaver exited with status 1

  oem@ubuntu:~$ localectl
     System Locale: LANG=en_US.UTF-8
     VC Keymap: n/a
    X11 Layout: fr
     X11 Model: pc105
   X11 Variant: oss

  So, with googling help (https://bbs.archlinux.org/viewtopic.php?id=180103), 
i've edited /etc/locale-gen (as user) and uncommented the line: fr_FR.UTF-8
   and then ran 'sudo locale-gen' and finally rebooted.

  But the error is still logged after reboot: either i need to set also
  'VC Keymap', but how ?, or it is related to the vte version actually
  used (and need an upgrade)
  (https://bugs.launchpad.net/ubuntu/+source/vte2.91/+bug/1721412)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-session 3.26.1-0ubuntu7
  ProcVersionSignature: Ubuntu 4.13.0-18.21-generic 4.13.13
  Uname: Linux 4.13.0-18-generic x86_64
  ApportVersion: 2.20.8-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sun Dec  3 17:17:45 2017
  EcryptfsInUse: Yes
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-session
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1725432] [deja-dup/artful] possible regression found

[Ubuntu Foundations Team Bug Bot]

As a part of the Stable Release Updates quality process a search for
Launchpad bug reports using the version of deja-dup from artful-proposed
was performed and bug 1743013 was found.  Please investigate this bug
report to ensure that a regression will not be created by this SRU. In
the event that this is not a regression remove the "verification-failed"
tag from this bug report and add the tag "bot-stop-nagging" to bug
1743013 (not this bug). Thanks!

** Tags added: verification-failed

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

Title:
  Restore failed due to missing source option

Status in Déjà Dup:
  Fix Released
Status in deja-dup package in Ubuntu:
  Fix Released
Status in deja-dup source package in Artful:
  Fix Committed

Bug description:
  [ Impact ]

  Users can't restore a backup on a fresh install from the deja-dup UI.

  [ Test Case ]

  Open "Backups" (or run 'deja-dup') and click the "Restore..." button.

  You should see a dropdown with options for a location, but instead
  with this bug, you see an empty dialog.

  [ Regression Potential ]

  Pretty small.  The proposed patch just moves some widget
  initialization earlier.

  [ Original Bug Description ]

  Installed a new Ubuntu 17.10, created my user and tried to restore the 
backups from the server.
  Pressed Overview, Restore and get an empty dialog. From screen shots I found 
I assume there should be some drop downs or buttons etc. but my dialog is empty.

To manage notifications about this bug go to:
https://bugs.launchpad.net/deja-dup/+bug/1725432/+subscriptions

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

[Desktop-packages] [Bug 1729728] Re: window picker is broken in 3.26

[Sebastian Geiger]

I have tested on Artful with proposed enabled and can confirm that this
fixes the issue. The schema is now being installed and I can add the
applet to the panel without the panel crashing.

Thanks alot for uploading this fix.

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

Title:
  window picker is broken in 3.26

Status in gnome-applets package in Ubuntu:
  Fix Released
Status in gnome-applets source package in Artful:
  Fix Committed

Bug description:
  [Impact]
  One of the applets shipped in gnome-applets package is broken. It crashes on 
startup because of missing GSettings schema file.

  [Test Case]
  * Log into GNOME Flashback session.
  * Try to add the “Window picker” applet to the panel.

  Expected result: panel does not crash, applet is added.

  [Proposed Fix]
  The proposed fix just makes the gsettings schema installed:

  https://git.gnome.org/browse/gnome-applets/commit/?id=6aedbc3a6af54190

  [Regression Potential]
  None, as the fix just adds a missing file.

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

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

[Desktop-packages] [Bug 1742894] Re: Scilab does not start after some upgrades on Ubuntu Xenial

[Norbert]

I do not know about Bionic, it maybe affected too.

I'll be watching this bug-report and re-enable `radeon` driver on my
machine after fix.

Thank you for quick reaction, Timo!

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

Title:
  Scilab does not start after some upgrades on Ubuntu Xenial

Status in Mesa:
  Confirmed
Status in libjogl2-java package in Ubuntu:
  Triaged
Status in mesa package in Ubuntu:
  New
Status in scilab package in Ubuntu:
  New
Status in libjogl2-java source package in Xenial:
  New
Status in mesa source package in Xenial:
  New
Status in scilab source package in Xenial:
  New
Status in libjogl2-java source package in Artful:
  New
Status in mesa source package in Artful:
  New
Status in scilab source package in Artful:
  New
Status in scilab package in Debian:
  New

Bug description:
  Steps to reproduce:
  1. have installed Scilab on Ubuntu Xenial system
  2. install system updates
  3. try to launch Scilab from GUI - it does not start
  4. try to launch Scilab from terminal - it does not start with the following 
output in the terminal:

  $ scilab
  Could not create a Scilab main class. Error:
  Exception in thread "main" java.lang.InternalError: XXX0 profile[1]: GL3bc -> 
profileImpl GL4bc !!! not mapped 
at com.jogamp.opengl.GLProfile.computeProfileMap(GLProfile.java:2071)
at 
com.jogamp.opengl.GLProfile.initProfilesForDeviceCritical(GLProfile.java:1954)
at 
com.jogamp.opengl.GLProfile.initProfilesForDevice(GLProfile.java:1875)
at 
com.jogamp.opengl.GLProfile.initProfilesForDefaultDevices(GLProfile.java:1842)
at com.jogamp.opengl.GLProfile.access$000(GLProfile.java:80)
at com.jogamp.opengl.GLProfile$1.run(GLProfile.java:230)
at java.security.AccessController.doPrivileged(Native Method)
at com.jogamp.opengl.GLProfile.initSingleton(GLProfile.java:216)
at com.jogamp.opengl.GLProfile.getProfileMap(GLProfile.java:2297)
at com.jogamp.opengl.GLProfile.get(GLProfile.java:988)
at com.jogamp.opengl.GLProfile.getDefault(GLProfile.java:722)
at com.jogamp.opengl.GLProfile.getDefault(GLProfile.java:733)
at org.scilab.modules.gui.SwingView.(Unknown Source)
at org.scilab.modules.gui.SwingView.registerSwingView(Unknown Source)
at org.scilab.modules.core.Scilab.(Unknown Source)

  Scilab cannot create Scilab Java Main-Class (we have not been able to
  find the main Scilab class. Check if the Scilab and thirdparty
  packages are available).

  
  Expected results:
  Scilab works normally on Ubuntu 16.04 LTS system.

  Actual results:
  see error above.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: scilab 5.5.2-2ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-104.127-generic 4.4.98
  Uname: Linux 4.4.0-104-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Fri Jan 12 12:02:32 2018
  PackageArchitecture: all
  SourcePackage: scilab
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1735594] Re: [regression] compiz crashes after Mesa upgrade

[Leo Pilachowski]

I did not realize that the -dev packages were also updated and in the
proposed repository.  I understood from a post above that everything
would be pulled in when the libgl1-mesa-dri package was updated.  I did
look for -dev updates but I could not find a way to see any of the
packages themselves on archive.ubuntu.com

Everything installs with no dependency issues now although working the
mesa based graphics hard can still cause some problems, but no more than
on other systems built before 1/4/2018.

Thanks, LP

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

Title:
  [regression] compiz crashes after Mesa upgrade

Status in mesa package in Ubuntu:
  Fix Committed
Status in mesa source package in Xenial:
  Fix Committed
Status in mesa source package in Artful:
  Fix Committed

Bug description:
  [Impact]
  When I use the Unity session I automatically get logged out under these 
conditions:

  When I hover with my mouse over any icon of the sidebar.
  When I press the alt key.
  When I press the super key.

  running dmesg after this unwanted logout happens I get following
  information:

  compiz[10616]: segfault at 0 ip 7fbca309feeb sp 7fff5f59a4d0
  error 4 in i965_dri.so[7fbca2af6000+7e4000]

  This is caused by a mesa upgrade, which added a patch for bug #1727401. The 
crasher is reproduced on:
  - gen4 / gen5 Intel
  - if using modesetting X driver, like when xserver-xorg-video-intel is not 
installed, or the HWE stack is installed (xserver-xorg-core-hwe-16.04 defaults 
to modesetting)

  [Test case]
  Log in to Unity, open the dash or try to log out etc. Compiz shouldn't crash.

  [Regression potential]
  The backported patches need to be tested, here for regressions and on 1727401 
that they fix the original bug (again).

  Best to test on a wide array of Intel HW:
  gen4 (965GM/GM45/G45)
  gen5 (Ironlake)
  gen6 (Sandy Bridge)
  gen7 (Bay Trail, Ivy Bridge, Haswell)
  gen8 (Braswell, Broadwell)
  gen9 (Apollo Lake, Skylake, Gemini Lake, Kaby Lake, Coffee Lake)

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

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

[Desktop-packages] [Bug 1742894] Re: Scilab does not start after some upgrades on Ubuntu Xenial

[Timo Aaltonen]

yes I had a look at the code, it's just radeon and swrast which are
busted because they no longer have "Gallium" in the renderer string

** Changed in: libjogl2-java (Ubuntu)
   Status: New => Triaged

** Changed in: libjogl2-java (Ubuntu)
 Assignee: (unassigned) => Timo Aaltonen (tjaalton)

** Also affects: mesa (Ubuntu Artful)
   Importance: Undecided
   Status: New

** Also affects: scilab (Ubuntu Artful)
   Importance: Undecided
   Status: New

** Also affects: libjogl2-java (Ubuntu Artful)
   Importance: Undecided
   Status: New

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

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

** Also affects: libjogl2-java (Ubuntu Xenial)
   Importance: Undecided
   Status: 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/1742894

Title:
  Scilab does not start after some upgrades on Ubuntu Xenial

Status in Mesa:
  Confirmed
Status in libjogl2-java package in Ubuntu:
  Triaged
Status in mesa package in Ubuntu:
  New
Status in scilab package in Ubuntu:
  New
Status in libjogl2-java source package in Xenial:
  New
Status in mesa source package in Xenial:
  New
Status in scilab source package in Xenial:
  New
Status in libjogl2-java source package in Artful:
  New
Status in mesa source package in Artful:
  New
Status in scilab source package in Artful:
  New
Status in scilab package in Debian:
  New

Bug description:
  Steps to reproduce:
  1. have installed Scilab on Ubuntu Xenial system
  2. install system updates
  3. try to launch Scilab from GUI - it does not start
  4. try to launch Scilab from terminal - it does not start with the following 
output in the terminal:

  $ scilab
  Could not create a Scilab main class. Error:
  Exception in thread "main" java.lang.InternalError: XXX0 profile[1]: GL3bc -> 
profileImpl GL4bc !!! not mapped 
at com.jogamp.opengl.GLProfile.computeProfileMap(GLProfile.java:2071)
at 
com.jogamp.opengl.GLProfile.initProfilesForDeviceCritical(GLProfile.java:1954)
at 
com.jogamp.opengl.GLProfile.initProfilesForDevice(GLProfile.java:1875)
at 
com.jogamp.opengl.GLProfile.initProfilesForDefaultDevices(GLProfile.java:1842)
at com.jogamp.opengl.GLProfile.access$000(GLProfile.java:80)
at com.jogamp.opengl.GLProfile$1.run(GLProfile.java:230)
at java.security.AccessController.doPrivileged(Native Method)
at com.jogamp.opengl.GLProfile.initSingleton(GLProfile.java:216)
at com.jogamp.opengl.GLProfile.getProfileMap(GLProfile.java:2297)
at com.jogamp.opengl.GLProfile.get(GLProfile.java:988)
at com.jogamp.opengl.GLProfile.getDefault(GLProfile.java:722)
at com.jogamp.opengl.GLProfile.getDefault(GLProfile.java:733)
at org.scilab.modules.gui.SwingView.(Unknown Source)
at org.scilab.modules.gui.SwingView.registerSwingView(Unknown Source)
at org.scilab.modules.core.Scilab.(Unknown Source)

  Scilab cannot create Scilab Java Main-Class (we have not been able to
  find the main Scilab class. Check if the Scilab and thirdparty
  packages are available).

  
  Expected results:
  Scilab works normally on Ubuntu 16.04 LTS system.

  Actual results:
  see error above.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: scilab 5.5.2-2ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-104.127-generic 4.4.98
  Uname: Linux 4.4.0-104-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Fri Jan 12 12:02:32 2018
  PackageArchitecture: all
  SourcePackage: scilab
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1743018] Re: Unable to install mesa-opencl-icd because of unmet dependencies on Xenial

[Launchpad Bug Tracker]

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

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

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

Title:
  Unable to install mesa-opencl-icd because of unmet dependencies on
  Xenial

Status in mesa package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce:
  1. Install Ubuntu 16.04 LTS
  2. Try to install `mesa-opencl-icd` with

  $ sudo apt-get install mesa-opencl-icd
  [sudo] password for user: 
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done

  
  Expected results:
  * mesa-opencl-icd is installed successfully

  Actual results:
  * got errors as follow

  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:
   mesa-opencl-icd : Depends: libclc-r600 (>= 0.2.0+git20170330-3) but it is 
not going to be installed
 Depends: libclc-amdgcn (>= 0.2.0+git20170330-3) but it is 
not going to be installed
  E: Unable to correct problems, you have held broken packages.

  
  Note: inspired by this AskUbuntu question - 
https://askubuntu.com/q/995274/66509 .

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: mesa-opencl-icd (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-109.132-generic 4.4.98
  Uname: Linux 4.4.0-109-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,mousepoll,move,gnomecompat,wall,regex,place,resize,snap,session,imgpng,vpswitch,grid,unitymtgrabhandles,animation,expo,workarounds,ezoom,staticswitcher,fade,scale,unityshell]
  CompositorRunning: None
  CurrentDesktop: MATE
  Date: Fri Jan 12 21:22:22 2018
  DistUpgraded: 2017-04-16 02:19:02,541 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: xenial
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. 3rd Gen Core processor Graphics 
Controller [1043:2135]
  InstallationDate: Installed on 2014-02-07 (1434 days ago)
  InstallationMedia: Ubuntu 12.04.4 LTS "Precise Pangolin" - Release amd64 
(20140204)
  MachineType: ASUSTeK COMPUTER INC. UX32A
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-109-generic 
root=UUID=1e3c78e2-1a6e-4afe-8249-40fe7fa81a86 ro quiet splash vt.handoff=7
  SourcePackage: mesa
  UpgradeStatus: Upgraded to xenial on 2017-04-15 (271 days ago)
  dmi.bios.date: 02/12/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX32A.216
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX32A
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX32A.216:bd02/12/2014:svnASUSTeKCOMPUTERINC.:pnUX32A:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX32A:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: UX32A
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.83-1~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu1~16.04.2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~16.04.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Fri Jan 12 20:32:41 2018
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.4-0ubuntu0.7
  xserver.video_driver: intel

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

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

[Desktop-packages] [Bug 1729728] Re: window picker is broken in 3.26

[Eugene San]

Hello Brian,

I am running Bionic where the bug is fixed (gnome-applets - 3.26.0-3).

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

Title:
  window picker is broken in 3.26

Status in gnome-applets package in Ubuntu:
  Fix Released
Status in gnome-applets source package in Artful:
  Fix Committed

Bug description:
  [Impact]
  One of the applets shipped in gnome-applets package is broken. It crashes on 
startup because of missing GSettings schema file.

  [Test Case]
  * Log into GNOME Flashback session.
  * Try to add the “Window picker” applet to the panel.

  Expected result: panel does not crash, applet is added.

  [Proposed Fix]
  The proposed fix just makes the gsettings schema installed:

  https://git.gnome.org/browse/gnome-applets/commit/?id=6aedbc3a6af54190

  [Regression Potential]
  None, as the fix just adds a missing file.

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

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

[Desktop-packages] [Bug 1743018] [NEW] Unable to install mesa-opencl-icd because of unmet dependencies on Xenial

[Norbert]

Public bug reported:

Steps to reproduce:
1. Install Ubuntu 16.04 LTS
2. Try to install `mesa-opencl-icd` with

$ sudo apt-get install mesa-opencl-icd
[sudo] password for user: 
Reading package lists... Done
Building dependency tree   
Reading state information... Done


Expected results:
* mesa-opencl-icd is installed successfully

Actual results:
* got errors as follow

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:
 mesa-opencl-icd : Depends: libclc-r600 (>= 0.2.0+git20170330-3) but it is not 
going to be installed
   Depends: libclc-amdgcn (>= 0.2.0+git20170330-3) but it is 
not going to be installed
E: Unable to correct problems, you have held broken packages.


Note: inspired by this AskUbuntu question - 
https://askubuntu.com/q/995274/66509 .

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: mesa-opencl-icd (not installed)
ProcVersionSignature: Ubuntu 4.4.0-109.132-generic 4.4.98
Uname: Linux 4.4.0-109-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.15
Architecture: amd64
CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,mousepoll,move,gnomecompat,wall,regex,place,resize,snap,session,imgpng,vpswitch,grid,unitymtgrabhandles,animation,expo,workarounds,ezoom,staticswitcher,fade,scale,unityshell]
CompositorRunning: None
CurrentDesktop: MATE
Date: Fri Jan 12 21:22:22 2018
DistUpgraded: 2017-04-16 02:19:02,541 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
DistroCodename: xenial
DistroVariant: ubuntu
GraphicsCard:
 Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 
09) (prog-if 00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. 3rd Gen Core processor Graphics Controller 
[1043:2135]
InstallationDate: Installed on 2014-02-07 (1434 days ago)
InstallationMedia: Ubuntu 12.04.4 LTS "Precise Pangolin" - Release amd64 
(20140204)
MachineType: ASUSTeK COMPUTER INC. UX32A
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-109-generic 
root=UUID=1e3c78e2-1a6e-4afe-8249-40fe7fa81a86 ro quiet splash vt.handoff=7
SourcePackage: mesa
UpgradeStatus: Upgraded to xenial on 2017-04-15 (271 days ago)
dmi.bios.date: 02/12/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: UX32A.216
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: UX32A
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX32A.216:bd02/12/2014:svnASUSTeKCOMPUTERINC.:pnUX32A:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX32A:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.name: UX32A
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.
version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.83-1~16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu1~16.04.2
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~16.04.2
version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2
xserver.bootTime: Fri Jan 12 20:32:41 2018
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.18.4-0ubuntu0.7
xserver.video_driver: intel

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


** Tags: apport-bug xenial

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

Title:
  Unable to install mesa-opencl-icd because of unmet dependencies on
  Xenial

Status in mesa package in Ubuntu:
  New

Bug description:
  Steps to reproduce:
  1. Install Ubuntu 16.04 LTS
  2. Try to install `mesa-opencl-icd` with

  $ sudo apt-get install mesa-opencl-icd
  [sudo] password for user: 
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done

  
  Expected results:
  * mesa-opencl-icd is installed successfully

  Actual results:
  * got errors as follow

  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 

[Desktop-packages] [Bug 1742816] Re: compiz crashing

[Borislav]

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

** This bug has been marked a duplicate of bug 1735594
   [regression] compiz crashes after Mesa upgrade

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

Title:
  compiz crashing

Status in nautilus package in Ubuntu:
  New

Bug description:
  Compiz is crashing dash
  WIN Key not working
  Dash not working
  No panel
  launcher disappears
  sidebar disappears
  alt tab not working

  Any ideas for a solution?
  I'll use lubuntu for workaround so i can use my system properly its fresh 
installed because of the but and thought that i F up  something and i pre 
installed ubuntu 16.04LTS but after some update i've got same problem.
  I'm sorry for my bad English

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: nautilus 1:3.18.4.is.3.14.3-0ubuntu6
  ProcVersionSignature: Ubuntu 4.13.0-26.29~16.04.2-generic 4.13.13
  Uname: Linux 4.13.0-26-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Jan 12 01:04:08 2018
  ExecutablePath: /usr/bin/nautilus
  GsettingsChanges:

  InstallationDate: Installed on 2018-01-10 (1 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1720364] Re: Unable to use <Ctrl+Shift+key> shortcuts with <Ctrl+Shift> keyboard layout switcher on Ubuntu MATE, 16.04 (with HWE), 17.10 and 18.04 LTS

[Norbert]

** Tags added: xenial

** Also affects: xorg-hwe-16.04 (Ubuntu)
   Importance: Undecided
   Status: New

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

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

Title:
  Unable to use  shortcuts with  keyboard
  layout switcher on Ubuntu MATE, 16.04 (with HWE), 17.10 and 18.04 LTS

Status in MATE Desktop:
  New
Status in ubuntu-mate:
  New
Status in X.Org X server:
  Confirmed
Status in marco package in Ubuntu:
  New
Status in xorg package in Ubuntu:
  New
Status in xorg-hwe-16.04 package in Ubuntu:
  New

Bug description:
  Steps to reproduce:
  1. Install ubuntu-mate-desktop on Ubuntu 17.10.
  2. Set-up two keyboard layouts - English and Russian
  3. Set  as keyboard layout switcher
  4. Try to use shortcuts starting from :
  4.1. Open Firefox, open new tab, go to some site in it, close tab, try to 
click  to restore closed tab.
  4.2. Open mate-terminal, try to open new tab with , or copy 
(), or paste ().
  4.3. Open pluma, write some text, try to navigate in it with 
.

  Expected results:
   switches keyboard layout, shortcuts starting from  
work normally.

  Actual results:
   switches keyboard layout, shortcuts starting from  
do not work.

  Notes:
  1. Ubuntu 16.04 LTS with Marco and Compton work normally with  
keyboard layout switcher.
  2. This problem was discovered before on 13.10, 14.04 and other modern 
versions with GNOME desktop (Metacity and Compiz) - see bug 1245473.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: marco 1.18.1-3ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic i686
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: i386
  CurrentDesktop: MATE
  Date: Fri Sep 29 16:18:02 2017
  InstallationDate: Installed on 2017-08-26 (33 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha i386 (20170826)
  SourcePackage: marco
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/mate-desktop/+bug/1720364/+subscriptions

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

[Desktop-packages] [Bug 1742894] Re: Scilab does not start after some upgrades on Ubuntu Xenial

[Norbert]

I saw this jogl bug (https://jogamp.org/bugzilla/show_bug.cgi?id=1357) today. 
Potentially other programs are affected too 
(https://www.google.ru/search?q=GL3bc+->+profileImpl+GL4bc+!!!+not+mapped+com.jogamp.opengl.GLProfile.computeProfileMap(GLProfile.java%3A2071)=GL3bc+->+profileImpl+GL4bc+!!!+not+mapped+com.jogamp.opengl.GLProfile.computeProfileMap(GLProfile.java%3A2071)).

With newest Mesa Scilab works normally on i915 and nvidia_340 drivers.

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

Title:
  Scilab does not start after some upgrades on Ubuntu Xenial

Status in Mesa:
  Confirmed
Status in libjogl2-java package in Ubuntu:
  New
Status in mesa package in Ubuntu:
  New
Status in scilab package in Ubuntu:
  New
Status in scilab package in Debian:
  New

Bug description:
  Steps to reproduce:
  1. have installed Scilab on Ubuntu Xenial system
  2. install system updates
  3. try to launch Scilab from GUI - it does not start
  4. try to launch Scilab from terminal - it does not start with the following 
output in the terminal:

  $ scilab
  Could not create a Scilab main class. Error:
  Exception in thread "main" java.lang.InternalError: XXX0 profile[1]: GL3bc -> 
profileImpl GL4bc !!! not mapped 
at com.jogamp.opengl.GLProfile.computeProfileMap(GLProfile.java:2071)
at 
com.jogamp.opengl.GLProfile.initProfilesForDeviceCritical(GLProfile.java:1954)
at 
com.jogamp.opengl.GLProfile.initProfilesForDevice(GLProfile.java:1875)
at 
com.jogamp.opengl.GLProfile.initProfilesForDefaultDevices(GLProfile.java:1842)
at com.jogamp.opengl.GLProfile.access$000(GLProfile.java:80)
at com.jogamp.opengl.GLProfile$1.run(GLProfile.java:230)
at java.security.AccessController.doPrivileged(Native Method)
at com.jogamp.opengl.GLProfile.initSingleton(GLProfile.java:216)
at com.jogamp.opengl.GLProfile.getProfileMap(GLProfile.java:2297)
at com.jogamp.opengl.GLProfile.get(GLProfile.java:988)
at com.jogamp.opengl.GLProfile.getDefault(GLProfile.java:722)
at com.jogamp.opengl.GLProfile.getDefault(GLProfile.java:733)
at org.scilab.modules.gui.SwingView.(Unknown Source)
at org.scilab.modules.gui.SwingView.registerSwingView(Unknown Source)
at org.scilab.modules.core.Scilab.(Unknown Source)

  Scilab cannot create Scilab Java Main-Class (we have not been able to
  find the main Scilab class. Check if the Scilab and thirdparty
  packages are available).

  
  Expected results:
  Scilab works normally on Ubuntu 16.04 LTS system.

  Actual results:
  see error above.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: scilab 5.5.2-2ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-104.127-generic 4.4.98
  Uname: Linux 4.4.0-104-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Fri Jan 12 12:02:32 2018
  PackageArchitecture: all
  SourcePackage: scilab
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1743013] [NEW] deja-dup fails when launched automatically

[Wolf Rogner]

Public bug reported:

In #1727653 an error was reported that stated that backup using
duplicity failed.

However, the error only manifests in duplicity but is triggered by the
calling Deja-Dup.

Launching Deja-Dup automatically will ALWAYS lead to the error.

Launching Deja-Dup from the console/bash will NEVER lead to the error.

Any attempts to set number of open file limits do not remedy the issue.

Please refer to #1727653 and associated errors as all analysis have gone
into duplicity so far.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: deja-dup 36.3-0ubuntu0.1
ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
Uname: Linux 4.13.0-25-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.7
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri Jan 12 18:55:12 2018
InstallationDate: Installed on 2017-10-20 (84 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
SourcePackage: deja-dup
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug artful package-from-proposed wayland-session

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

Title:
  deja-dup fails when launched automatically

Status in deja-dup package in Ubuntu:
  New

Bug description:
  In #1727653 an error was reported that stated that backup using
  duplicity failed.

  However, the error only manifests in duplicity but is triggered by the
  calling Deja-Dup.

  Launching Deja-Dup automatically will ALWAYS lead to the error.

  Launching Deja-Dup from the console/bash will NEVER lead to the error.

  Any attempts to set number of open file limits do not remedy the
  issue.

  Please refer to #1727653 and associated errors as all analysis have
  gone into duplicity so far.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: deja-dup 36.3-0ubuntu0.1
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  Uname: Linux 4.13.0-25-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jan 12 18:55:12 2018
  InstallationDate: Installed on 2017-10-20 (84 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  SourcePackage: deja-dup
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/1743013/+subscriptions

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

[Desktop-packages] [Bug 1742894] Re: Scilab does not start after some upgrades on Ubuntu Xenial

[Norbert]

** Bug watch added: jogamp.org/bugzilla/ #1357
   https://jogamp.org/bugzilla/show_bug.cgi?id=1357

** Also affects: scilab via
   https://jogamp.org/bugzilla/show_bug.cgi?id=1357
   Importance: Unknown
   Status: Unknown

** No longer affects: scilab

** Also affects: libjogl2-java (Ubuntu)
   Importance: Undecided
   Status: 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/1742894

Title:
  Scilab does not start after some upgrades on Ubuntu Xenial

Status in Mesa:
  Confirmed
Status in libjogl2-java package in Ubuntu:
  New
Status in mesa package in Ubuntu:
  New
Status in scilab package in Ubuntu:
  New
Status in scilab package in Debian:
  New

Bug description:
  Steps to reproduce:
  1. have installed Scilab on Ubuntu Xenial system
  2. install system updates
  3. try to launch Scilab from GUI - it does not start
  4. try to launch Scilab from terminal - it does not start with the following 
output in the terminal:

  $ scilab
  Could not create a Scilab main class. Error:
  Exception in thread "main" java.lang.InternalError: XXX0 profile[1]: GL3bc -> 
profileImpl GL4bc !!! not mapped 
at com.jogamp.opengl.GLProfile.computeProfileMap(GLProfile.java:2071)
at 
com.jogamp.opengl.GLProfile.initProfilesForDeviceCritical(GLProfile.java:1954)
at 
com.jogamp.opengl.GLProfile.initProfilesForDevice(GLProfile.java:1875)
at 
com.jogamp.opengl.GLProfile.initProfilesForDefaultDevices(GLProfile.java:1842)
at com.jogamp.opengl.GLProfile.access$000(GLProfile.java:80)
at com.jogamp.opengl.GLProfile$1.run(GLProfile.java:230)
at java.security.AccessController.doPrivileged(Native Method)
at com.jogamp.opengl.GLProfile.initSingleton(GLProfile.java:216)
at com.jogamp.opengl.GLProfile.getProfileMap(GLProfile.java:2297)
at com.jogamp.opengl.GLProfile.get(GLProfile.java:988)
at com.jogamp.opengl.GLProfile.getDefault(GLProfile.java:722)
at com.jogamp.opengl.GLProfile.getDefault(GLProfile.java:733)
at org.scilab.modules.gui.SwingView.(Unknown Source)
at org.scilab.modules.gui.SwingView.registerSwingView(Unknown Source)
at org.scilab.modules.core.Scilab.(Unknown Source)

  Scilab cannot create Scilab Java Main-Class (we have not been able to
  find the main Scilab class. Check if the Scilab and thirdparty
  packages are available).

  
  Expected results:
  Scilab works normally on Ubuntu 16.04 LTS system.

  Actual results:
  see error above.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: scilab 5.5.2-2ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-104.127-generic 4.4.98
  Uname: Linux 4.4.0-104-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Fri Jan 12 12:02:32 2018
  PackageArchitecture: all
  SourcePackage: scilab
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1727653] Re: error: can't start new thread

[Wolf Rogner]

@Kenneth #17:

I verified that the settings recommended in comment #17 change nothing
(several kernel updates later)

a) if anything, it should be nofile and not nfile
b) /etc/security/limits.conf may be altered but any settings there are ignored
c) ulimit is a bash parameter and cannot be applied system-wide.
d) even when called from the command line with as little as soft limit of 1024 
(the default) Deja-Dup/duplicity works fine.

@abautu #19:

Nice try, nevertheless, it does not make Deja-Dup work either.

As I mentioned before: It's not a problem of duplicity but of Deja-Dup.

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

Title:
  error: can't start new thread

Status in Duplicity:
  In Progress
Status in duplicity package in Ubuntu:
  In Progress

Bug description:
  $ uname -a
  Linux mbpr13b 4.13.0-16-generic #19-Ubuntu SMP Wed Oct 11 18:35:14 UTC 2017 
x86_64 x86_64 x86_64 GNU/Linux

  duplicity gets started daily via deja-dup automatically.

  Every now and then (approx. every third time) I get the following
  error:

  --

  Failed with an unknown error.

  Traceback (most recent call last):
File "/usr/bin/duplicity", line 1546, in 
  with_tempdir(main)
File "/usr/bin/duplicity", line 1540, in with_tempdir
  fn()
File "/usr/bin/duplicity", line 1391, in main
  do_backup(action)
File "/usr/bin/duplicity", line 1468, in do_backup
  restore(col_stats)
File "/usr/bin/duplicity", line 731, in restore
  restore_get_patched_rop_iter(col_stats)):
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 560, in 
Write_ROPaths
  for ropath in rop_iter:
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 523, in 
integrate_patch_iters
  for patch_seq in collated:
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 389, in 
yield_tuples
  setrorps(overflow, elems)
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 378, in 
setrorps
  elems[i] = iter_list[i].next()
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 107, in 
filter_path_iter
  for path in path_iter:
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 121, in 
difftar2path_iter
  tarinfo_list = [tar_iter.next()]
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 339, in 
next
  self.set_tarfile()
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 333, in 
set_tarfile
  self.current_fp = self.fileobj_iter.next()
File "/usr/bin/duplicity", line 768, in get_fileobj_iter
  manifest.volume_info_dict[vol_num])
File "/usr/bin/duplicity", line 811, in restore_get_enc_fileobj
  fileobj = tdp.filtered_open_with_delete("rb")
File "/usr/lib/python2.7/dist-packages/duplicity/dup_temp.py", line 119, in 
filtered_open_with_delete
  fh = FileobjHooked(path.DupPath.filtered_open(self, mode))
File "/usr/lib/python2.7/dist-packages/duplicity/path.py", line 778, in 
filtered_open
  return gpg.GPGFile(False, self, gpg_profile)
File "/usr/lib/python2.7/dist-packages/duplicity/gpg.py", line 202, in 
__init__
  'logger': self.logger_fp})
File "/usr/lib/python2.7/dist-packages/duplicity/gpginterface.py", line 
374, in run
  create_fhs, attach_fhs)
File "/usr/lib/python2.7/dist-packages/duplicity/gpginterface.py", line 
420, in _attach_fork_exec
  process.thread.start()
File "/usr/lib/python2.7/threading.py", line 736, in start
  _start_new_thread(self.__bootstrap, ())
  error: can't start new thread

  --

  Restarting deja-dup manually fixes the problem and the next few days,
  automatic backup will run correctly until (see above).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: duplicity 0.7.12-1ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 26 10:49:45 2017
  InstallationDate: Installed on 2017-10-20 (5 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  SourcePackage: duplicity
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1743003] [NEW] no audio via internal laptop speakers; reporting via ubuntu-bug results in pulseaudio crash

[Casper]

Public bug reported:

No sound at all via internal laptop speakers.
Tried to report via ubuntu-bug, but get an error "pulseaudio has crashed."

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: pulseaudio 1:8.0-0ubuntu3.7
ProcVersionSignature: Ubuntu 4.13.0-26.29~16.04.2-generic 4.13.13
Uname: Linux 4.13.0-26-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.1-0ubuntu2.15
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/pcmC0D0p:   cc16   2679 F...m pulseaudio
 /dev/snd/controlC0:  cc16   2679 F pulseaudio
 /dev/snd/controlC1:  cc16   2679 F pulseaudio
Date: Fri Jan 12 17:21:02 2018
InstallationDate: Installed on 2017-08-22 (143 days ago)
InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
ProcEnviron:
 LANGUAGE=en_GB:en
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
PulseList:
 Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
 No PulseAudio daemon running, or not running as session daemon.
SourcePackage: pulseaudio
Symptom: audio
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/29/2017
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1.05.02
dmi.board.asset.tag: Tag 12345
dmi.board.name: P95_HR
dmi.board.vendor: CLEVO
dmi.board.version: Not Applicable
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Notebook
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.05.02:bd06/29/2017:svnPCSpecialistLimited:pnP95_HR:pvrNotApplicable:rvnCLEVO:rnP95_HR:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
dmi.product.family: Not Applicable
dmi.product.name: P95_HR
dmi.product.version: Not Applicable
dmi.sys.vendor: PC Specialist Limited

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


** Tags: amd64 apport-bug xenial

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

Title:
  no audio via internal laptop speakers; reporting via ubuntu-bug
  results in pulseaudio crash

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  No sound at all via internal laptop speakers.
  Tried to report via ubuntu-bug, but get an error "pulseaudio has crashed."

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: pulseaudio 1:8.0-0ubuntu3.7
  ProcVersionSignature: Ubuntu 4.13.0-26.29~16.04.2-generic 4.13.13
  Uname: Linux 4.13.0-26-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  AudioDevicesInUse:
   USER PID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   cc16   2679 F...m pulseaudio
   /dev/snd/controlC0:  cc16   2679 F pulseaudio
   /dev/snd/controlC1:  cc16   2679 F pulseaudio
  Date: Fri Jan 12 17:21:02 2018
  InstallationDate: Installed on 2017-08-22 (143 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  ProcEnviron:
   LANGUAGE=en_GB:en
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  Symptom: audio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/29/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.05.02
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: P95_HR
  dmi.board.vendor: CLEVO
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.05.02:bd06/29/2017:svnPCSpecialistLimited:pnP95_HR:pvrNotApplicable:rvnCLEVO:rnP95_HR:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: P95_HR
  dmi.product.version: Not Applicable
  dmi.sys.vendor: PC Specialist Limited

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

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

[Desktop-packages] [Bug 1735594] Re: [regression] compiz crashes after Mesa upgrade

[Timo Aaltonen]

no it isn't, you just happen to have -dev packages installed too

sudo apt install libgl1-mesa-dri libegl1-mesa-dev/xenial-proposed

or something. Figure it out, this is not related to the update but
something on your system.

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

Title:
  [regression] compiz crashes after Mesa upgrade

Status in mesa package in Ubuntu:
  Fix Committed
Status in mesa source package in Xenial:
  Fix Committed
Status in mesa source package in Artful:
  Fix Committed

Bug description:
  [Impact]
  When I use the Unity session I automatically get logged out under these 
conditions:

  When I hover with my mouse over any icon of the sidebar.
  When I press the alt key.
  When I press the super key.

  running dmesg after this unwanted logout happens I get following
  information:

  compiz[10616]: segfault at 0 ip 7fbca309feeb sp 7fff5f59a4d0
  error 4 in i965_dri.so[7fbca2af6000+7e4000]

  This is caused by a mesa upgrade, which added a patch for bug #1727401. The 
crasher is reproduced on:
  - gen4 / gen5 Intel
  - if using modesetting X driver, like when xserver-xorg-video-intel is not 
installed, or the HWE stack is installed (xserver-xorg-core-hwe-16.04 defaults 
to modesetting)

  [Test case]
  Log in to Unity, open the dash or try to log out etc. Compiz shouldn't crash.

  [Regression potential]
  The backported patches need to be tested, here for regressions and on 1727401 
that they fix the original bug (again).

  Best to test on a wide array of Intel HW:
  gen4 (965GM/GM45/G45)
  gen5 (Ironlake)
  gen6 (Sandy Bridge)
  gen7 (Bay Trail, Ivy Bridge, Haswell)
  gen8 (Braswell, Broadwell)
  gen9 (Apollo Lake, Skylake, Gemini Lake, Kaby Lake, Coffee Lake)

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

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

[Desktop-packages] [Bug 1742997] [NEW] Newly installed applications are not showing in "Installed"

[AsciiWolf]

Public bug reported:

If you install any application using GNOME Software (Ubuntu Software),
the newly installed application is not displayed on the "Installed" tab.
It starts showing after the next system reboot.

Steps to Reproduce:
1. Find any application that is not installed and install it.
2. Switch to the "Installed" tab and try to find the newly installed 
application.

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


** Tags: bionic

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

Title:
  Newly installed applications are not showing in "Installed"

Status in gnome-software package in Ubuntu:
  New

Bug description:
  If you install any application using GNOME Software (Ubuntu Software),
  the newly installed application is not displayed on the "Installed"
  tab. It starts showing after the next system reboot.

  Steps to Reproduce:
  1. Find any application that is not installed and install it.
  2. Switch to the "Installed" tab and try to find the newly installed 
application.

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

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

[Desktop-packages] [Bug 1735594] Re: [regression] compiz crashes after Mesa upgrade

[Leo Pilachowski]

Already tried that:

***
sudo apt -f install libegl1-mesa-dev
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:
 libegl1-mesa-dev : Depends: libegl1-mesa (= 17.2.4-0ubuntu1~16.04.2) but 
17.2.4-0ubuntu1~16.04.3 is to be installed
Depends: libwayland-egl1-mesa (= 17.2.4-0ubuntu1~16.04.2) 
but 17.2.4-0ubuntu1~16.04.3 is to be installed
E: Unable to correct problems, you have held broken packages.
***

Trying with aptitude to get a solution gives:

***
The following actions will resolve these dependencies:

 Downgrade the following packages:  
1) libegl1-mesa [17.2.4-0ubuntu1~16.04.3 (now) -> 17.2.4-0ubuntu1~16.04.2 (x
2) libgbm1 [17.2.4-0ubuntu1~16.04.3 (now) -> 17.2.4-0ubuntu1~16.04.2 (xenial
3) libgl1-mesa-dri [17.2.4-0ubuntu1~16.04.3 (now) -> 17.2.4-0ubuntu1~16.04.2
4) libwayland-egl1-mesa [17.2.4-0ubuntu1~16.04.3 (now) -> 17.2.4-0ubuntu1~16
***

The solution is to downgrade the 4 packages that fixed the graphics
problem!

So, the proposed fix is somehow incomplete.

LeoP

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

Title:
  [regression] compiz crashes after Mesa upgrade

Status in mesa package in Ubuntu:
  Fix Committed
Status in mesa source package in Xenial:
  Fix Committed
Status in mesa source package in Artful:
  Fix Committed

Bug description:
  [Impact]
  When I use the Unity session I automatically get logged out under these 
conditions:

  When I hover with my mouse over any icon of the sidebar.
  When I press the alt key.
  When I press the super key.

  running dmesg after this unwanted logout happens I get following
  information:

  compiz[10616]: segfault at 0 ip 7fbca309feeb sp 7fff5f59a4d0
  error 4 in i965_dri.so[7fbca2af6000+7e4000]

  This is caused by a mesa upgrade, which added a patch for bug #1727401. The 
crasher is reproduced on:
  - gen4 / gen5 Intel
  - if using modesetting X driver, like when xserver-xorg-video-intel is not 
installed, or the HWE stack is installed (xserver-xorg-core-hwe-16.04 defaults 
to modesetting)

  [Test case]
  Log in to Unity, open the dash or try to log out etc. Compiz shouldn't crash.

  [Regression potential]
  The backported patches need to be tested, here for regressions and on 1727401 
that they fix the original bug (again).

  Best to test on a wide array of Intel HW:
  gen4 (965GM/GM45/G45)
  gen5 (Ironlake)
  gen6 (Sandy Bridge)
  gen7 (Bay Trail, Ivy Bridge, Haswell)
  gen8 (Braswell, Broadwell)
  gen9 (Apollo Lake, Skylake, Gemini Lake, Kaby Lake, Coffee Lake)

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

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

[Desktop-packages] [Bug 1735594] Re: [regression] compiz crashes after Mesa upgrade

[Timo Aaltonen]

run 'sudo apt -f install' to fix that

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

Title:
  [regression] compiz crashes after Mesa upgrade

Status in mesa package in Ubuntu:
  Fix Committed
Status in mesa source package in Xenial:
  Fix Committed
Status in mesa source package in Artful:
  Fix Committed

Bug description:
  [Impact]
  When I use the Unity session I automatically get logged out under these 
conditions:

  When I hover with my mouse over any icon of the sidebar.
  When I press the alt key.
  When I press the super key.

  running dmesg after this unwanted logout happens I get following
  information:

  compiz[10616]: segfault at 0 ip 7fbca309feeb sp 7fff5f59a4d0
  error 4 in i965_dri.so[7fbca2af6000+7e4000]

  This is caused by a mesa upgrade, which added a patch for bug #1727401. The 
crasher is reproduced on:
  - gen4 / gen5 Intel
  - if using modesetting X driver, like when xserver-xorg-video-intel is not 
installed, or the HWE stack is installed (xserver-xorg-core-hwe-16.04 defaults 
to modesetting)

  [Test case]
  Log in to Unity, open the dash or try to log out etc. Compiz shouldn't crash.

  [Regression potential]
  The backported patches need to be tested, here for regressions and on 1727401 
that they fix the original bug (again).

  Best to test on a wide array of Intel HW:
  gen4 (965GM/GM45/G45)
  gen5 (Ironlake)
  gen6 (Sandy Bridge)
  gen7 (Bay Trail, Ivy Bridge, Haswell)
  gen8 (Braswell, Broadwell)
  gen9 (Apollo Lake, Skylake, Gemini Lake, Kaby Lake, Coffee Lake)

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

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

[Desktop-packages] [Bug 1742961] Re: Inkscape crashes when opening a pdf file

[WildWeasel]

Attached another strace log, manually opening the file


** Attachment added: "strace log"
   
https://bugs.launchpad.net/ubuntu/+source/inkscape/+bug/1742961/+attachment/5035863/+files/inkscape.trace.txt

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

Title:
  Inkscape crashes when opening a pdf file

Status in inkscape package in Ubuntu:
  New

Bug description:
  I'm trying to open a PDF file (https://arxiv.org/pdf/1605.07678) but
  Inkscape 0.92 crashed with a "Inkscape encountered an internal error
  and will now close" message. The same was happening with Inkscape
  0.91.

  Ubuntu: 16.04
  updates: all
  Inkscape versions:0.91 and 0.92
  Inkspace PPA used to instal 0.92: ppa:inkscape.dev/stable
  How to reproduce bug: Open Inkscape and select the PDF file.

  I've attached the strace log:

  # inkscape -f Canziani\,\ Paszke\,\ Culurciello\ -\ 2016\ -\ An\
  Analysis\ of\ Deep\ Neural\ Network\ Models\ for\ Practical\
  Applications.pdf &> inkscape.trace.txt

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

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

[Desktop-packages] [Bug 1742961] [NEW] Inkscape crashes when opening a pdf file

[WildWeasel]

Public bug reported:

I'm trying to open a PDF file (https://arxiv.org/pdf/1605.07678) but
Inkscape 0.92 crashed with a "Inkscape encountered an internal error and
will now close" message. The same was happening with Inkscape 0.91.

Ubuntu: 16.04
updates: all
Inkscape versions:0.91 and 0.92
Inkspace PPA used to instal 0.92: ppa:inkscape.dev/stable
How to reproduce bug: Open Inkscape and select the PDF file.

I've attached the strace log:

# inkscape -f Canziani\,\ Paszke\,\ Culurciello\ -\ 2016\ -\ An\
Analysis\ of\ Deep\ Neural\ Network\ Models\ for\ Practical\
Applications.pdf &> inkscape.trace.txt

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


** Tags: inkscape

** Attachment added: "inkscape.trace.txt"
   
https://bugs.launchpad.net/bugs/1742961/+attachment/5035862/+files/inkscape.trace.txt

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

Title:
  Inkscape crashes when opening a pdf file

Status in inkscape package in Ubuntu:
  New

Bug description:
  I'm trying to open a PDF file (https://arxiv.org/pdf/1605.07678) but
  Inkscape 0.92 crashed with a "Inkscape encountered an internal error
  and will now close" message. The same was happening with Inkscape
  0.91.

  Ubuntu: 16.04
  updates: all
  Inkscape versions:0.91 and 0.92
  Inkspace PPA used to instal 0.92: ppa:inkscape.dev/stable
  How to reproduce bug: Open Inkscape and select the PDF file.

  I've attached the strace log:

  # inkscape -f Canziani\,\ Paszke\,\ Culurciello\ -\ 2016\ -\ An\
  Analysis\ of\ Deep\ Neural\ Network\ Models\ for\ Practical\
  Applications.pdf &> inkscape.trace.txt

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

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

[Desktop-packages] [Bug 1735594] Re: [regression] compiz crashes after Mesa upgrade

[Leo Pilachowski]

proposed did not fix

The compiz issue is resolved but the fix breaks other dependencies and
software (ROS for example)

Just upgrading libgl1-mesa-dri from ...16.04.2 to ...16.04.3 gives
dependency errors when installing other packages such as libegl1-mesa-
dev:

The following packages have unmet dependencies:
 libegl1-mesa-dev : Depends: libegl1-mesa (= 17.2.4-0ubuntu1~16.04.2) but 
17.2.4-0ubuntu1~16.04.3 is to be installed
Depends: libwayland-egl1-mesa (= 17.2.4-0ubuntu1~16.04.2) 
but 17.2.4-0ubuntu1~16.04.3 is to be installed
E: Unable to correct problems, you have held broken packages.

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

Title:
  [regression] compiz crashes after Mesa upgrade

Status in mesa package in Ubuntu:
  Fix Committed
Status in mesa source package in Xenial:
  Fix Committed
Status in mesa source package in Artful:
  Fix Committed

Bug description:
  [Impact]
  When I use the Unity session I automatically get logged out under these 
conditions:

  When I hover with my mouse over any icon of the sidebar.
  When I press the alt key.
  When I press the super key.

  running dmesg after this unwanted logout happens I get following
  information:

  compiz[10616]: segfault at 0 ip 7fbca309feeb sp 7fff5f59a4d0
  error 4 in i965_dri.so[7fbca2af6000+7e4000]

  This is caused by a mesa upgrade, which added a patch for bug #1727401. The 
crasher is reproduced on:
  - gen4 / gen5 Intel
  - if using modesetting X driver, like when xserver-xorg-video-intel is not 
installed, or the HWE stack is installed (xserver-xorg-core-hwe-16.04 defaults 
to modesetting)

  [Test case]
  Log in to Unity, open the dash or try to log out etc. Compiz shouldn't crash.

  [Regression potential]
  The backported patches need to be tested, here for regressions and on 1727401 
that they fix the original bug (again).

  Best to test on a wide array of Intel HW:
  gen4 (965GM/GM45/G45)
  gen5 (Ironlake)
  gen6 (Sandy Bridge)
  gen7 (Bay Trail, Ivy Bridge, Haswell)
  gen8 (Braswell, Broadwell)
  gen9 (Apollo Lake, Skylake, Gemini Lake, Kaby Lake, Coffee Lake)

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

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

[Desktop-packages] [Bug 1742894] Re: Scilab does not start after some upgrades on Ubuntu Xenial

[Bug Watch Updater]

** Changed in: mesa
   Status: Unknown => Confirmed

** Changed in: mesa
   Importance: Unknown => High

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

Title:
  Scilab does not start after some upgrades on Ubuntu Xenial

Status in Mesa:
  Confirmed
Status in mesa package in Ubuntu:
  New
Status in scilab package in Ubuntu:
  New
Status in scilab package in Debian:
  New

Bug description:
  Steps to reproduce:
  1. have installed Scilab on Ubuntu Xenial system
  2. install system updates
  3. try to launch Scilab from GUI - it does not start
  4. try to launch Scilab from terminal - it does not start with the following 
output in the terminal:

  $ scilab
  Could not create a Scilab main class. Error:
  Exception in thread "main" java.lang.InternalError: XXX0 profile[1]: GL3bc -> 
profileImpl GL4bc !!! not mapped 
at com.jogamp.opengl.GLProfile.computeProfileMap(GLProfile.java:2071)
at 
com.jogamp.opengl.GLProfile.initProfilesForDeviceCritical(GLProfile.java:1954)
at 
com.jogamp.opengl.GLProfile.initProfilesForDevice(GLProfile.java:1875)
at 
com.jogamp.opengl.GLProfile.initProfilesForDefaultDevices(GLProfile.java:1842)
at com.jogamp.opengl.GLProfile.access$000(GLProfile.java:80)
at com.jogamp.opengl.GLProfile$1.run(GLProfile.java:230)
at java.security.AccessController.doPrivileged(Native Method)
at com.jogamp.opengl.GLProfile.initSingleton(GLProfile.java:216)
at com.jogamp.opengl.GLProfile.getProfileMap(GLProfile.java:2297)
at com.jogamp.opengl.GLProfile.get(GLProfile.java:988)
at com.jogamp.opengl.GLProfile.getDefault(GLProfile.java:722)
at com.jogamp.opengl.GLProfile.getDefault(GLProfile.java:733)
at org.scilab.modules.gui.SwingView.(Unknown Source)
at org.scilab.modules.gui.SwingView.registerSwingView(Unknown Source)
at org.scilab.modules.core.Scilab.(Unknown Source)

  Scilab cannot create Scilab Java Main-Class (we have not been able to
  find the main Scilab class. Check if the Scilab and thirdparty
  packages are available).

  
  Expected results:
  Scilab works normally on Ubuntu 16.04 LTS system.

  Actual results:
  see error above.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: scilab 5.5.2-2ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-104.127-generic 4.4.98
  Uname: Linux 4.4.0-104-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Fri Jan 12 12:02:32 2018
  PackageArchitecture: all
  SourcePackage: scilab
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1742894] Re: Scilab does not start after some upgrades on Ubuntu Xenial

[Timo Aaltonen]

this is actually a bug in jogl which seems to be doing stupid string
checking to see if the driver is Mesa, and fails now that GL_RENDERER
string doesn't have "Gallium" in it (wonder what happens with intel..)

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

Title:
  Scilab does not start after some upgrades on Ubuntu Xenial

Status in Mesa:
  Confirmed
Status in mesa package in Ubuntu:
  New
Status in scilab package in Ubuntu:
  New
Status in scilab package in Debian:
  New

Bug description:
  Steps to reproduce:
  1. have installed Scilab on Ubuntu Xenial system
  2. install system updates
  3. try to launch Scilab from GUI - it does not start
  4. try to launch Scilab from terminal - it does not start with the following 
output in the terminal:

  $ scilab
  Could not create a Scilab main class. Error:
  Exception in thread "main" java.lang.InternalError: XXX0 profile[1]: GL3bc -> 
profileImpl GL4bc !!! not mapped 
at com.jogamp.opengl.GLProfile.computeProfileMap(GLProfile.java:2071)
at 
com.jogamp.opengl.GLProfile.initProfilesForDeviceCritical(GLProfile.java:1954)
at 
com.jogamp.opengl.GLProfile.initProfilesForDevice(GLProfile.java:1875)
at 
com.jogamp.opengl.GLProfile.initProfilesForDefaultDevices(GLProfile.java:1842)
at com.jogamp.opengl.GLProfile.access$000(GLProfile.java:80)
at com.jogamp.opengl.GLProfile$1.run(GLProfile.java:230)
at java.security.AccessController.doPrivileged(Native Method)
at com.jogamp.opengl.GLProfile.initSingleton(GLProfile.java:216)
at com.jogamp.opengl.GLProfile.getProfileMap(GLProfile.java:2297)
at com.jogamp.opengl.GLProfile.get(GLProfile.java:988)
at com.jogamp.opengl.GLProfile.getDefault(GLProfile.java:722)
at com.jogamp.opengl.GLProfile.getDefault(GLProfile.java:733)
at org.scilab.modules.gui.SwingView.(Unknown Source)
at org.scilab.modules.gui.SwingView.registerSwingView(Unknown Source)
at org.scilab.modules.core.Scilab.(Unknown Source)

  Scilab cannot create Scilab Java Main-Class (we have not been able to
  find the main Scilab class. Check if the Scilab and thirdparty
  packages are available).

  
  Expected results:
  Scilab works normally on Ubuntu 16.04 LTS system.

  Actual results:
  see error above.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: scilab 5.5.2-2ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-104.127-generic 4.4.98
  Uname: Linux 4.4.0-104-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Fri Jan 12 12:02:32 2018
  PackageArchitecture: all
  SourcePackage: scilab
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1742894] Re: Scilab does not start after some upgrades on Ubuntu Xenial

[Timo Aaltonen]

actually that LIBGL_ALWAYS_SOFTWARE=1 won't work either with current
mesa

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

Title:
  Scilab does not start after some upgrades on Ubuntu Xenial

Status in Mesa:
  Confirmed
Status in mesa package in Ubuntu:
  New
Status in scilab package in Ubuntu:
  New
Status in scilab package in Debian:
  New

Bug description:
  Steps to reproduce:
  1. have installed Scilab on Ubuntu Xenial system
  2. install system updates
  3. try to launch Scilab from GUI - it does not start
  4. try to launch Scilab from terminal - it does not start with the following 
output in the terminal:

  $ scilab
  Could not create a Scilab main class. Error:
  Exception in thread "main" java.lang.InternalError: XXX0 profile[1]: GL3bc -> 
profileImpl GL4bc !!! not mapped 
at com.jogamp.opengl.GLProfile.computeProfileMap(GLProfile.java:2071)
at 
com.jogamp.opengl.GLProfile.initProfilesForDeviceCritical(GLProfile.java:1954)
at 
com.jogamp.opengl.GLProfile.initProfilesForDevice(GLProfile.java:1875)
at 
com.jogamp.opengl.GLProfile.initProfilesForDefaultDevices(GLProfile.java:1842)
at com.jogamp.opengl.GLProfile.access$000(GLProfile.java:80)
at com.jogamp.opengl.GLProfile$1.run(GLProfile.java:230)
at java.security.AccessController.doPrivileged(Native Method)
at com.jogamp.opengl.GLProfile.initSingleton(GLProfile.java:216)
at com.jogamp.opengl.GLProfile.getProfileMap(GLProfile.java:2297)
at com.jogamp.opengl.GLProfile.get(GLProfile.java:988)
at com.jogamp.opengl.GLProfile.getDefault(GLProfile.java:722)
at com.jogamp.opengl.GLProfile.getDefault(GLProfile.java:733)
at org.scilab.modules.gui.SwingView.(Unknown Source)
at org.scilab.modules.gui.SwingView.registerSwingView(Unknown Source)
at org.scilab.modules.core.Scilab.(Unknown Source)

  Scilab cannot create Scilab Java Main-Class (we have not been able to
  find the main Scilab class. Check if the Scilab and thirdparty
  packages are available).

  
  Expected results:
  Scilab works normally on Ubuntu 16.04 LTS system.

  Actual results:
  see error above.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: scilab 5.5.2-2ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-104.127-generic 4.4.98
  Uname: Linux 4.4.0-104-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Fri Jan 12 12:02:32 2018
  PackageArchitecture: all
  SourcePackage: scilab
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1742894] Re: Scilab does not start after some upgrades on Ubuntu Xenial

[Timo Aaltonen]

from https://wiki.scilab.org/Graphical%20issues%20with%20Scilab%205.X

try adding LIBGL_ALWAYS_SOFTWARE=1 in front of the scilab command

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

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

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

Title:
  Scilab does not start after some upgrades on Ubuntu Xenial

Status in Mesa:
  Confirmed
Status in mesa package in Ubuntu:
  New
Status in scilab package in Ubuntu:
  New
Status in scilab package in Debian:
  New

Bug description:
  Steps to reproduce:
  1. have installed Scilab on Ubuntu Xenial system
  2. install system updates
  3. try to launch Scilab from GUI - it does not start
  4. try to launch Scilab from terminal - it does not start with the following 
output in the terminal:

  $ scilab
  Could not create a Scilab main class. Error:
  Exception in thread "main" java.lang.InternalError: XXX0 profile[1]: GL3bc -> 
profileImpl GL4bc !!! not mapped 
at com.jogamp.opengl.GLProfile.computeProfileMap(GLProfile.java:2071)
at 
com.jogamp.opengl.GLProfile.initProfilesForDeviceCritical(GLProfile.java:1954)
at 
com.jogamp.opengl.GLProfile.initProfilesForDevice(GLProfile.java:1875)
at 
com.jogamp.opengl.GLProfile.initProfilesForDefaultDevices(GLProfile.java:1842)
at com.jogamp.opengl.GLProfile.access$000(GLProfile.java:80)
at com.jogamp.opengl.GLProfile$1.run(GLProfile.java:230)
at java.security.AccessController.doPrivileged(Native Method)
at com.jogamp.opengl.GLProfile.initSingleton(GLProfile.java:216)
at com.jogamp.opengl.GLProfile.getProfileMap(GLProfile.java:2297)
at com.jogamp.opengl.GLProfile.get(GLProfile.java:988)
at com.jogamp.opengl.GLProfile.getDefault(GLProfile.java:722)
at com.jogamp.opengl.GLProfile.getDefault(GLProfile.java:733)
at org.scilab.modules.gui.SwingView.(Unknown Source)
at org.scilab.modules.gui.SwingView.registerSwingView(Unknown Source)
at org.scilab.modules.core.Scilab.(Unknown Source)

  Scilab cannot create Scilab Java Main-Class (we have not been able to
  find the main Scilab class. Check if the Scilab and thirdparty
  packages are available).

  
  Expected results:
  Scilab works normally on Ubuntu 16.04 LTS system.

  Actual results:
  see error above.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: scilab 5.5.2-2ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-104.127-generic 4.4.98
  Uname: Linux 4.4.0-104-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Fri Jan 12 12:02:32 2018
  PackageArchitecture: all
  SourcePackage: scilab
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1731102] Re: Poor performance with Wayland

[Jean-Baptiste Lallement]

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

** Changed in: wayland (Ubuntu)
   Importance: Undecided => High

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

Title:
  Poor performance with Wayland

Status in wayland package in Ubuntu:
  Confirmed

Bug description:
  When running Gnome 3 in Wayland mode (confirmed with XDG_SESSION_TYPE
  env var) I see the following issues on this hardware:

  * Jerky animations (glxgears stutters noticably)
  * Mouse cursor sometimes updated at a reduced framerate, usualy when CPU is 
under load, appearing to worsen over time (> 8 hours uptime)
  * High CPU usage when mousing over icons in left-hand side Unity dock 
(20-30%), also causing mouse cursor to stutter
  * 15fps in Kodi and poor video playback framerate
  * 30-40% CPU usage in Kodi when program idle
  * Gnome shell frequently using 25% of CPU or more

  All issues disappear when using x11 mode (again confirmed with
  XDG_SESSION_TYPE env var). Performance in that case seems as good as
  17.04

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  BootLog:
   * Setting up X socket directories...    
[ OK ]
* Restoring resolver state...    
[ OK ]
   Starting jabber server: ejabberd
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Nov  9 13:03:08 2017
  DistUpgraded: 2017-11-07 09:38:15,448 DEBUG icon theme changed, re-reading
  DistroCodename: artful
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.1.30, 4.10.0-37-generic, x86_64: installed
   virtualbox, 5.1.30, 4.13.0-16-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Wrestler [Radeon HD 6310] [1002:9802] 
(prog-if 00 [VGA controller])
 Subsystem: ZOTAC International (MCO) Ltd. Wrestler [Radeon HD 6310] 
[19da:a191]
  InstallationDate: Installed on 2011-12-05 (2165 days ago)
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=e1bf9820-e70e-4e84-9037-621437cc90f1 ro radeon.audio=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to artful on 2017-11-06 (2 days ago)
  dmi.bios.date: 10/28/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.4
  dmi.board.name: AMD HUDSON-M1
  dmi.board.vendor: ZOTAC
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.4:bd10/28/2011:svn:pn:pvr:rvnZOTAC:rnAMDHUDSON-M1:rvr:cvn:ct3:cvr:
  version.compiz: compiz 1:0.9.13.1+17.10.20170901-0ubuntu1
  version.libdrm2: libdrm2 2.4.83-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Wed Oct 18 20:39:16 2017
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputRiitek Micro Keyboard KEYBOARD, id 8
   inputRiitek Micro Keyboard MOUSE, id 9
   inputRiitek Micro Keyboard KEYBOARD, id 10
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.3-1ubuntu1.3
  xserver.video_driver: radeon

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

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

[Desktop-packages] [Bug 1742894] Re: Scilab does not start after some upgrades on Ubuntu Xenial

[Timo Aaltonen]

that's a bad workaround if your gfx card is radeon..

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

Title:
  Scilab does not start after some upgrades on Ubuntu Xenial

Status in mesa package in Ubuntu:
  New
Status in scilab package in Ubuntu:
  New
Status in scilab package in Debian:
  New

Bug description:
  Steps to reproduce:
  1. have installed Scilab on Ubuntu Xenial system
  2. install system updates
  3. try to launch Scilab from GUI - it does not start
  4. try to launch Scilab from terminal - it does not start with the following 
output in the terminal:

  $ scilab
  Could not create a Scilab main class. Error:
  Exception in thread "main" java.lang.InternalError: XXX0 profile[1]: GL3bc -> 
profileImpl GL4bc !!! not mapped 
at com.jogamp.opengl.GLProfile.computeProfileMap(GLProfile.java:2071)
at 
com.jogamp.opengl.GLProfile.initProfilesForDeviceCritical(GLProfile.java:1954)
at 
com.jogamp.opengl.GLProfile.initProfilesForDevice(GLProfile.java:1875)
at 
com.jogamp.opengl.GLProfile.initProfilesForDefaultDevices(GLProfile.java:1842)
at com.jogamp.opengl.GLProfile.access$000(GLProfile.java:80)
at com.jogamp.opengl.GLProfile$1.run(GLProfile.java:230)
at java.security.AccessController.doPrivileged(Native Method)
at com.jogamp.opengl.GLProfile.initSingleton(GLProfile.java:216)
at com.jogamp.opengl.GLProfile.getProfileMap(GLProfile.java:2297)
at com.jogamp.opengl.GLProfile.get(GLProfile.java:988)
at com.jogamp.opengl.GLProfile.getDefault(GLProfile.java:722)
at com.jogamp.opengl.GLProfile.getDefault(GLProfile.java:733)
at org.scilab.modules.gui.SwingView.(Unknown Source)
at org.scilab.modules.gui.SwingView.registerSwingView(Unknown Source)
at org.scilab.modules.core.Scilab.(Unknown Source)

  Scilab cannot create Scilab Java Main-Class (we have not been able to
  find the main Scilab class. Check if the Scilab and thirdparty
  packages are available).

  
  Expected results:
  Scilab works normally on Ubuntu 16.04 LTS system.

  Actual results:
  see error above.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: scilab 5.5.2-2ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-104.127-generic 4.4.98
  Uname: Linux 4.4.0-104-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Fri Jan 12 12:02:32 2018
  PackageArchitecture: all
  SourcePackage: scilab
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1742954] [NEW] glib-pacrunner crashed on PAC file - proxy settingy and environment settings remain unset

[Qaxi]

Public bug reported:

# lsb_release -rd
Description:Ubuntu Bionic Beaver (development branch)
Release:18.04

$ LANG=C apt-cache policy glib-networking
glib-networking:
  Installed: 2.54.1-2
  Candidate: 2.54.1-2
  Version table:
 *** 2.54.1-2 500
500 http://cz.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
100 /var/lib/dpkg/status


Expected behavoir:
Setting "Proxy Automatic" or "Proxy Automatic with PAC file URL" in Network 
manager should result in setting HTTP (and others) proxy for GNOME and 
environment variables for terminal applications.


What happened: 
When I set network manager for using Automatic settings 
(Automatic proxy settings with PAC file URL or without URL). 

glib-pacrunner is crashing every time i reconnect network interface to
LAN or WiFi with PAC


It is probably the same bug reported a repaired HERE: 
https://codereview.qt-project.org/#/c/200463/

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: glib-networking-services 2.54.1-2
ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
Uname: Linux 4.13.0-25-generic x86_64
ApportVersion: 2.20.8-0ubuntu6
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri Jan 12 14:39:47 2018
InstallationDate: Installed on 2018-01-06 (5 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=cs_CZ.UTF-8
 SHELL=/bin/bash
SourcePackage: glib-networking
UpgradeStatus: Upgraded to bionic on 2018-01-12 (0 days ago)

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

Title:
  glib-pacrunner crashed on PAC file - proxy settingy and environment
  settings remain unset

Status in glib-networking package in Ubuntu:
  New

Bug description:
  # lsb_release -rd
  Description:  Ubuntu Bionic Beaver (development branch)
  Release:  18.04

  $ LANG=C apt-cache policy glib-networking
  glib-networking:
Installed: 2.54.1-2
Candidate: 2.54.1-2
Version table:
   *** 2.54.1-2 500
  500 http://cz.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status

  
  Expected behavoir:
  Setting "Proxy Automatic" or "Proxy Automatic with PAC file URL" in Network 
manager should result in setting HTTP (and others) proxy for GNOME and 
environment variables for terminal applications.

  
  What happened: 
  When I set network manager for using Automatic settings 
  (Automatic proxy settings with PAC file URL or without URL). 

  glib-pacrunner is crashing every time i reconnect network interface to
  LAN or WiFi with PAC


  It is probably the same bug reported a repaired HERE: 
  https://codereview.qt-project.org/#/c/200463/

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: glib-networking-services 2.54.1-2
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  Uname: Linux 4.13.0-25-generic x86_64
  ApportVersion: 2.20.8-0ubuntu6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jan 12 14:39:47 2018
  InstallationDate: Installed on 2018-01-06 (5 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=cs_CZ.UTF-8
   SHELL=/bin/bash
  SourcePackage: glib-networking
  UpgradeStatus: Upgraded to bionic on 2018-01-12 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib-networking/+bug/1742954/+subscriptions

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

[Desktop-packages] [Bug 1742950] [NEW] Snap sections are not shown in GNOME Software

[Evan]

Public bug reported:

The Snap Store maintains app sections:

$ snap find --section=games
NameVersionDeveloper   Notes  Summary
boa 0.3njmcphail   -  WolfenDoom: Blade of 
Agony
pin-town2.0.79 failsafegames   -  Help the Pin Pals in 
this physics puzzle game, inspired by Pachinko
…

However, GNOME Software does not make use of these. It should be taught
to display these and their contents when snap support is enabled.

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

** Attachment added: "Snap sections not shown in GNOME Software"
   
https://bugs.launchpad.net/bugs/1742950/+attachment/5035852/+files/VirtualBox_Ubuntu%2016.04_12_01_2018_16_01_14.png

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

Title:
  Snap sections are not shown in GNOME Software

Status in gnome-software package in Ubuntu:
  New

Bug description:
  The Snap Store maintains app sections:

  $ snap find --section=games
  NameVersionDeveloper   Notes  Summary
  boa 0.3njmcphail   -  WolfenDoom: Blade 
of Agony
  pin-town2.0.79 failsafegames   -  Help the Pin Pals 
in this physics puzzle game, inspired by Pachinko
  …

  However, GNOME Software does not make use of these. It should be
  taught to display these and their contents when snap support is
  enabled.

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

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

[Desktop-packages] [Bug 875676] Re: Backing up fails with 'IOError CRC check failed'.

[Kenneth Loafman]

** Changed in: duplicity
Milestone: 0.7.16 => 0.7.17

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

Title:
  Backing up fails with 'IOError CRC check failed'.

Status in Duplicity:
  In Progress
Status in duplicity package in Ubuntu:
  Confirmed

Bug description:
  For 4 days déjà dup hasn't been able to perform a backup. It fails
  with the error

  Failed to read /tmp/duplicity-lJcUDl-tempdir/mktemp-o4LYSJ-1: (, IOError('CRC check failed 0x8434f7d2L !=
  0x3d503338L',), )

  There is another similar bug #676767 where deleting ~/.cache/deja-dup
  helps. In this case it doesn't.

  I'm quite certain that my backup drive isn't corrupted. (It's a
  raid5.) I'd be happy to provide any additional information needed.

  --

  System information:
  Ubuntu 11.10
  deja-dup 20.0-0ubuntu3
  duplicity 0.6.15-0ubuntu2

  Logs:
  deja-dup.log: http://pastie.org/2705320
  deja-dup.gsettings: http://pastie.org/2705322

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

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

[Desktop-packages] [Bug 1731631] Re: KeyError: 56

[Kenneth Loafman]

** Changed in: duplicity
Milestone: 0.7.16 => 0.7.17

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

Title:
   KeyError: 56

Status in Duplicity:
  In Progress
Status in duplicity package in Ubuntu:
  New

Bug description:
  Last run of Deja-dup has ended up with the following error:

  Traceback (innermost last):
File "/usr/bin/duplicity", line 1559, in 
  with_tempdir(main)
File "/usr/bin/duplicity", line 1545, in with_tempdir
  fn()
File "/usr/bin/duplicity", line 1394, in main
  do_backup(action)
File "/usr/bin/duplicity", line 1473, in do_backup
  restore(col_stats)
File "/usr/bin/duplicity", line 729, in restore
  restore_get_patched_rop_iter(col_stats)):
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 558, in 
Write_ROPaths
  for ropath in rop_iter:
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 521, in 
integrate_patch_iters
  for patch_seq in collated:
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 389, in 
yield_tuples
  setrorps(overflow, elems)
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 378, in 
setrorps
  elems[i] = iter_list[i].next()
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 107, in 
filter_path_iter
  for path in path_iter:
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 121, in 
difftar2path_iter
  tarinfo_list = [tar_iter.next()]
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 339, in 
next
  self.set_tarfile()
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 333, in 
set_tarfile
  self.current_fp = self.fileobj_iter.next()
File "/usr/bin/duplicity", line 765, in get_fileobj_iter
  backup_set.volume_name_dict[vol_num],
   KeyError: 56

  This is with 0.7.14+bzr1336-0ubuntu3~ubuntu17.10.1.

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

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

[Desktop-packages] [Bug 1742946] [NEW] "gio monitor" does not work

[Michael Albinus]

Public bug reported:

# ls -l /etc/adduser.conf
-rw-r--r-- 1 root root 2981 Mar 11  2012 /etc/adduser.conf
# gio monitor file:///etc/adduser.conf
gio: No locations given

Usage:
  gio monitor [OPTION…] [LOCATION...]

Monitor files or directories for changes.

Options:
  -d, --dir=LOCATIONMonitor a directory (default: depends on type)
  -f, --file=LOCATION   Monitor a file (default: depends on type)
  -D, --direct=LOCATION Monitor a file directly (notices changes made via 
hardlinks)
  -s, --silent=LOCATION Monitors a file directly, but doesn’t report changes
  -n, --no-movesReport moves and renames as simple deleted/created 
events
  -m, --mounts  Watch for mount events

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: libglib2.0-bin 2.54.1-1ubuntu1
ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13
Uname: Linux 4.13.0-21-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.7
Architecture: amd64
Date: Fri Jan 12 14:29:42 2018
InstallationDate: Installed on 2012-03-12 (2131 days ago)
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (20120311)
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/usr/bin/tcsh
SourcePackage: glib2.0
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: glib2.0 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug artful

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

Title:
  "gio monitor" does not work

Status in glib2.0 package in Ubuntu:
  New

Bug description:
  # ls -l /etc/adduser.conf
  -rw-r--r-- 1 root root 2981 Mar 11  2012 /etc/adduser.conf
  # gio monitor file:///etc/adduser.conf
  gio: No locations given

  Usage:
gio monitor [OPTION…] [LOCATION...]

  Monitor files or directories for changes.

  Options:
-d, --dir=LOCATIONMonitor a directory (default: depends on type)
-f, --file=LOCATION   Monitor a file (default: depends on type)
-D, --direct=LOCATION Monitor a file directly (notices changes made via 
hardlinks)
-s, --silent=LOCATION Monitors a file directly, but doesn’t report 
changes
-n, --no-movesReport moves and renames as simple 
deleted/created events
-m, --mounts  Watch for mount events

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: libglib2.0-bin 2.54.1-1ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13
  Uname: Linux 4.13.0-21-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  Date: Fri Jan 12 14:29:42 2018
  InstallationDate: Installed on 2012-03-12 (2131 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 
(20120311)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/usr/bin/tcsh
  SourcePackage: glib2.0
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

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

[Paul White]

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

** This bug has been marked a duplicate of bug 1514474
   package tex-common 6.04 failed to install/upgrade: subprocess installed 
post-installation script returned error exit status 1

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

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

Status in tex-common package in Ubuntu:
  New

Bug description:
  No actualiza

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: tex-common 6.04
  ProcVersionSignature: Ubuntu 4.4.0-104.127-generic 4.4.98
  Uname: Linux 4.4.0-104-generic i686
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: i386
  Date: Tue Jan  9 23:37:29 2018
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2012-11-01 (1896 days ago)
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.3
   apt  1.2.24
  SourcePackage: tex-common
  Title: package tex-common 6.04 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
  UpgradeStatus: Upgraded to xenial on 2018-01-10 (0 days ago)

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

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

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

[Paul White]

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

** This bug has been marked a duplicate of bug 1514474
   package tex-common 6.04 failed to install/upgrade: subprocess installed 
post-installation script returned error exit status 1

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

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

Status in tex-common package in Ubuntu:
  New

Bug description:
  System initiated bug report, after automatic upgrade from 14.04 to
  16.04 reported problems.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: tex-common 6.04
  ProcVersionSignature: Ubuntu 4.4.0-109.132-generic 4.4.98
  Uname: Linux 4.4.0-109-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  Date: Thu Jan 11 20:15:07 2018
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2011-07-01 (2386 days ago)
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.3
   apt  1.2.24
  SourcePackage: tex-common
  Title: package tex-common 6.04 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
  UpgradeStatus: Upgraded to xenial on 2018-01-11 (0 days ago)

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

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

[Desktop-packages] [Bug 1675935] Re: Cheese crashes on startup with (cheese:18946): GLib-CRITICAL **: g_strsplit: assertion 'string != NULL' failed Segmentation fault (core dumped)

[Falak]

Tried reporting as you suggested but that too crashed. So, attaching the
crash report here

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

Title:
  Cheese crashes on startup with (cheese:18946): GLib-CRITICAL **:
  g_strsplit: assertion 'string != NULL' failed Segmentation fault (core
  dumped)

Status in cheese package in Ubuntu:
  Invalid

Bug description:
  
  cheese

  (cheese:18946): GLib-CRITICAL **: g_strsplit: assertion 'string != NULL' 
failed
  Segmentation fault (core dumped)

  No video is ever produced

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: cheese 3.22.0-1ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-41.44-generic 4.8.17
  Uname: Linux 4.8.0-41-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Fri Mar 24 21:29:59 2017
  InstallationDate: Installed on 2016-08-03 (233 days ago)
  InstallationMedia: Kubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  JournalErrors:
   Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] 
failed with exit code 1: Hint: You are currently not seeing messages from other 
users and the system.
 Users in the 'systemd-journal' group can see all messages. Pass -q to
 turn off this notice.
   No journal files were opened due to insufficient permissions.
  MachineType: OEGStone P9X79 LE
  RelatedPackageVersions:
   cheese3.22.0-1ubuntu1
   cheese-common 3.22.0-1ubuntu1
  SourcePackage: cheese
  UpgradeStatus: Upgraded to yakkety on 2017-01-04 (79 days ago)
  dmi.bios.date: 04/27/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 9505
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P9X79 LE
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr9505:bd04/27/2013:svnOEGStone:pnP9X79LE:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP9X79LE:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: P9X79 LE
  dmi.product.version: System Version
  dmi.sys.vendor: OEGStone

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

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

[Desktop-packages] [Bug 1675935] Re: Cheese crashes on startup with (cheese:18946): GLib-CRITICAL **: g_strsplit: assertion 'string != NULL' failed Segmentation fault (core dumped)

[Falak]

** Attachment added: "Crash report"
   
https://bugs.launchpad.net/ubuntu/+source/cheese/+bug/1675935/+attachment/5035839/+files/_usr_bin_cheese.1000.crash

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

Title:
  Cheese crashes on startup with (cheese:18946): GLib-CRITICAL **:
  g_strsplit: assertion 'string != NULL' failed Segmentation fault (core
  dumped)

Status in cheese package in Ubuntu:
  Invalid

Bug description:
  
  cheese

  (cheese:18946): GLib-CRITICAL **: g_strsplit: assertion 'string != NULL' 
failed
  Segmentation fault (core dumped)

  No video is ever produced

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: cheese 3.22.0-1ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-41.44-generic 4.8.17
  Uname: Linux 4.8.0-41-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Fri Mar 24 21:29:59 2017
  InstallationDate: Installed on 2016-08-03 (233 days ago)
  InstallationMedia: Kubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  JournalErrors:
   Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] 
failed with exit code 1: Hint: You are currently not seeing messages from other 
users and the system.
 Users in the 'systemd-journal' group can see all messages. Pass -q to
 turn off this notice.
   No journal files were opened due to insufficient permissions.
  MachineType: OEGStone P9X79 LE
  RelatedPackageVersions:
   cheese3.22.0-1ubuntu1
   cheese-common 3.22.0-1ubuntu1
  SourcePackage: cheese
  UpgradeStatus: Upgraded to yakkety on 2017-01-04 (79 days ago)
  dmi.bios.date: 04/27/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 9505
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P9X79 LE
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr9505:bd04/27/2013:svnOEGStone:pnP9X79LE:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP9X79LE:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: P9X79 LE
  dmi.product.version: System Version
  dmi.sys.vendor: OEGStone

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

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

[Desktop-packages] [Bug 1742932] Re: gnome-screenshot crashed with signal 5

[Apport retracing service]

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

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 #1725383, 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/1742932/+attachment/5035812/+files/CoreDump.gz

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

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

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

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

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

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

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

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  gnome-screenshot crashed with signal 5

Status in gnome-screenshot package in Ubuntu:
  New

Bug description:
  Ubuntu screencapture on 18.04-beta crashed unexpectedly, but the
  screen capture shift+PrtScn did work and produce the highlighted
  area_box.png

  Not really sure why the system reported an unexpected closure. I was
  somewhat surprised but the error/warning box popped up just after the
  screen capture.png appeared in the pictures directory as it
  should..with no apparent artifacts or problems.

  This appears to be  like a relatively  "minor"issue to me?
  Sorry I am running a Cinnamon desktop not gnome as I should..in xorg, X-11 
not Wayland and I am using most current Nvidia drivers on a Titan / dual 
monitor DVI system rather than HDMI  because of the dual monitor default choice 
problem with GDM/gnome/wayland

  Don / w9dki
  Hilbert Space Technical Arts
  w: www.hspacetech.com
  e: dlwalt...@hspacetech.com

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-screenshot 3.25.0-0ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  Uname: Linux 4.13.0-17-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.8-0ubuntu6
  Architecture: amd64
  CurrentDesktop: X-Cinnamon
  Date: Fri Jan 12 04:34:46 2018
  ExecutablePath: /usr/bin/gnome-screenshot
  InstallationDate: Installed on 2017-12-22 (21 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171221)
  ProcCmdline: gnome-screenshot --area
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Signal: 5
  SourcePackage: gnome-screenshot
  StacktraceTop:
   () at /usr/lib/x86_64-linux-gnu/libX11.so.6
   () at /usr/lib/x86_64-linux-gnu/libX11.so.6
   _XReply () at /usr/lib/x86_64-linux-gnu/libX11.so.6
   XInternAtom () at /usr/lib/x86_64-linux-gnu/libX11.so.6
   gdk_x11_atom_to_xatom_for_display () at 
/usr/lib/x86_64-linux-gnu/libgdk-3.so.0
  Title: gnome-screenshot crashed with signal 5
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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

[Desktop-packages] [Bug 1742894] Re: Scilab does not start after some upgrades on Ubuntu Xenial

[Norbert]

Asked question on AskUbuntu (https://askubuntu.com/q/995093/66509).

Fixed by blacklisting `radeon`:

cat  
profileImpl GL4bc !!! not mapped 
at com.jogamp.opengl.GLProfile.computeProfileMap(GLProfile.java:2071)
at 
com.jogamp.opengl.GLProfile.initProfilesForDeviceCritical(GLProfile.java:1954)
at 
com.jogamp.opengl.GLProfile.initProfilesForDevice(GLProfile.java:1875)
at 
com.jogamp.opengl.GLProfile.initProfilesForDefaultDevices(GLProfile.java:1842)
at com.jogamp.opengl.GLProfile.access$000(GLProfile.java:80)
at com.jogamp.opengl.GLProfile$1.run(GLProfile.java:230)
at java.security.AccessController.doPrivileged(Native Method)
at com.jogamp.opengl.GLProfile.initSingleton(GLProfile.java:216)
at com.jogamp.opengl.GLProfile.getProfileMap(GLProfile.java:2297)
at com.jogamp.opengl.GLProfile.get(GLProfile.java:988)
at com.jogamp.opengl.GLProfile.getDefault(GLProfile.java:722)
at com.jogamp.opengl.GLProfile.getDefault(GLProfile.java:733)
at org.scilab.modules.gui.SwingView.(Unknown Source)
at org.scilab.modules.gui.SwingView.registerSwingView(Unknown Source)
at org.scilab.modules.core.Scilab.(Unknown Source)

  Scilab cannot create Scilab Java Main-Class (we have not been able to
  find the main Scilab class. Check if the Scilab and thirdparty
  packages are available).

  
  Expected results:
  Scilab works normally on Ubuntu 16.04 LTS system.

  Actual results:
  see error above.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: scilab 5.5.2-2ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-104.127-generic 4.4.98
  Uname: Linux 4.4.0-104-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Fri Jan 12 12:02:32 2018
  PackageArchitecture: all
  SourcePackage: scilab
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1573959] Re: On-screen text disappears after suspend

[Sven Eppler]

Affected by this bug too. Almost daily when coming back from the lunch
break i have to logoff and login to have my fonts back...

My System:
$ lspci -nn | grep VGA
00:02.0 VGA compatible controller [0300]: Intel Corporation Crystal Well 
Integrated Graphics Controller [8086:0d26] (rev 08)

$ uname -a
Linux epplersv-tuxedo 4.4.0-108-generic #131-Ubuntu SMP Sun Jan 7 14:34:49 UTC 
2018 x86_64 x86_64 x86_64 GNU/Linux

$ cat /etc/issue.net 
Ubuntu 16.04.3 LTS

Going to test the workaround and install Kernel 4.8 and will be
reporting back.

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

Title:
  On-screen text disappears after suspend

Status in linux-lts-xenial package in Ubuntu:
  Confirmed
Status in xserver-xorg-video-intel package in Ubuntu:
  Confirmed

Bug description:
  After resuming from a suspend, almost all text on screen is not
  visible.  This includes menu items, text in all three boxes (list of
  folders, list of e-mails, e-mail body) in Thunderbird (with the
  curious exception of "ffl" in the File menu), top menu in Chromium
  (but not the menu obtained by pressing the hamburger button), and the
  menus produced by clicking items in the system tray.  Also, the apport
  dialog had no text except for a few capital letters.

  WORKAROUND / 'FIX' (added on March 9, 2017)
  Several people have mentioned upgrading to kernel 4.8 or higher solves the 
issue. As per #81, you can easily install kernel 4.8 (if you're on Ubuntu 
16.04, that is) by running

  sudo apt install linux-generic-hwe-16.04

  If you are still experiencing this issue after upgrading to kernel
  4.8, please share your system details in the comments.

  ADDITIONAL INFORMATION:
  * initctl restart unity-panel-service restarts the panel, but the text is 
still missing
  * suspend and resume does not fix the issue
  * Logging out fixes the issue
  * Other affected applications:
  ** Chromium file select dialog
  ** Terminal (entire window)
  ** ttys 1-6 (Ctrl+Alt+F1, etc.)
  ** Document viewer (menus)
  ** Software Updater
  ** Rhythmbox
  ** The dialog that appears when you take a screenshot with Ctrl+Alt+PrtSc
  ** ubuntu-bug
  ** Nautilus
  ** LibreOffice Calc (spreadsheet text contents)
  ** Firefox
  * Unity dash is not affected.
  * Skype is not affected.
  * Mousing over a button in a dialog correctly shows the text.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: unity 7.4.0+16.04.20160415-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  .tmp.unity_support_test.0:

  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  BootLog:

  CompizPlugins: 
[core,bailer,detection,composite,opengl,compiztoolbox,decor,gnomecompat,imgpng,place,move,resize,vpswitch,snap,regex,grid,mousepoll,unitymtgrabhandles,animation,session,wall,workarounds,expo,fade,ezoom,scale,unityshell]
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Sat Apr 23 12:04:57 2016
  DistUpgraded: 2016-04-22 09:22:44,147 DEBUG icon theme changed, re-reading
  DistroCodename: xenial
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 09) (prog-if 00 [VGA controller])
     Subsystem: COMPAL Electronics Inc Haswell-ULT Integrated Graphics 
Controller [14c0:0075]
  InstallationDate: Installed on 2015-01-21 (457 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  MachineType: Compal VAW70
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic 
root=UUID=8f4bd759-42d2-4828-8470-2aaf6fcb75ff ro quiet splash vt.handoff=7
  SourcePackage: unity
  UpgradeStatus: Upgraded to xenial on 2016-04-22 (1 days ago)
  dmi.bios.date: 07/31/2013
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.01T01
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Type2 - Board Product Name1
  dmi.board.vendor: Compal
  dmi.board.version: V1.01T01
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.01T01:bd07/31/2013:svnCompal:pnVAW70:pvrV1.01T01:rvnCompal:rnType2-BoardProductName1:rvrV1.01T01:cvnChassisManufacturer:ct10:cvrChassisVersion:
  dmi.product.name: VAW70
  dmi.product.version: V1.01T01
  dmi.sys.vendor: Compal
  upstart.unity-panel-service-lockscreen.log:
   (unity-panel-service:14416): GLib-CRITICAL **: Source ID 4294967295 was not 
found when attempting to remove it

   (unity-panel-service:26413): GLib-CRITICAL **: Source ID 4294967295 was not 
found when attempting to remove it
  version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  

[Desktop-packages] [Bug 1742894] Re: Scilab does not start after some upgrades on Ubuntu Xenial

[Bug Watch Updater]

** Changed in: scilab (Debian)
   Status: Unknown => 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/1742894

Title:
  Scilab does not start after some upgrades on Ubuntu Xenial

Status in mesa package in Ubuntu:
  New
Status in scilab package in Ubuntu:
  New
Status in scilab package in Debian:
  New

Bug description:
  Steps to reproduce:
  1. have installed Scilab on Ubuntu Xenial system
  2. install system updates
  3. try to launch Scilab from GUI - it does not start
  4. try to launch Scilab from terminal - it does not start with the following 
output in the terminal:

  $ scilab
  Could not create a Scilab main class. Error:
  Exception in thread "main" java.lang.InternalError: XXX0 profile[1]: GL3bc -> 
profileImpl GL4bc !!! not mapped 
at com.jogamp.opengl.GLProfile.computeProfileMap(GLProfile.java:2071)
at 
com.jogamp.opengl.GLProfile.initProfilesForDeviceCritical(GLProfile.java:1954)
at 
com.jogamp.opengl.GLProfile.initProfilesForDevice(GLProfile.java:1875)
at 
com.jogamp.opengl.GLProfile.initProfilesForDefaultDevices(GLProfile.java:1842)
at com.jogamp.opengl.GLProfile.access$000(GLProfile.java:80)
at com.jogamp.opengl.GLProfile$1.run(GLProfile.java:230)
at java.security.AccessController.doPrivileged(Native Method)
at com.jogamp.opengl.GLProfile.initSingleton(GLProfile.java:216)
at com.jogamp.opengl.GLProfile.getProfileMap(GLProfile.java:2297)
at com.jogamp.opengl.GLProfile.get(GLProfile.java:988)
at com.jogamp.opengl.GLProfile.getDefault(GLProfile.java:722)
at com.jogamp.opengl.GLProfile.getDefault(GLProfile.java:733)
at org.scilab.modules.gui.SwingView.(Unknown Source)
at org.scilab.modules.gui.SwingView.registerSwingView(Unknown Source)
at org.scilab.modules.core.Scilab.(Unknown Source)

  Scilab cannot create Scilab Java Main-Class (we have not been able to
  find the main Scilab class. Check if the Scilab and thirdparty
  packages are available).

  
  Expected results:
  Scilab works normally on Ubuntu 16.04 LTS system.

  Actual results:
  see error above.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: scilab 5.5.2-2ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-104.127-generic 4.4.98
  Uname: Linux 4.4.0-104-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Fri Jan 12 12:02:32 2018
  PackageArchitecture: all
  SourcePackage: scilab
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1718824] Re: The analogue audio does not work on the Dell USB Dock

[Hui Wang]

@Alex,

1:11.1-1ubuntu4 is ready for bionic, when you have time, please help
test it.

thx.

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

Title:
  The analogue audio does not work on the Dell USB Dock

Status in HWE Next:
  In Progress
Status in OEM Priority Project:
  Triaged
Status in pulseaudio package in Ubuntu:
  In Progress
Status in pulseaudio source package in Xenial:
  New
Status in pulseaudio source package in Artful:
  New

Bug description:
  SRU Document:

  [Impact]

  If users use the latest Dell USB Dock, e.g. TB16, they will found the
  analog audio (lineout jack) can't work under ubuntu linux

  [Test Case]

  After applying the fix, users can play sound via analog speaker or
  lineout freely. Without the fix, users can't play sound from lineout
  jack.

  [Regression Potential]

  No any possibility to introduce regression since this fix just adding
  a new dock's support, it does not change any existing code.

  [Other Info]

  No more info here

  Steps:
  1. Cold boot system with BME/IE connected
  2. Plug in a speaker to Line-out jack
  3. Set Analog Stereo Output from Sound settings

  Expected results: Line-out port can work

  Actual results: Line-out port not work

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1718824/+subscriptions

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

[Desktop-packages] [Bug 1742894] Re: Scilab does not start after some upgrades on Ubuntu Xenial

[Timo Aaltonen]

does it work on artful?

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

Title:
  Scilab does not start after some upgrades on Ubuntu Xenial

Status in mesa package in Ubuntu:
  New
Status in scilab package in Ubuntu:
  New
Status in scilab package in Debian:
  Unknown

Bug description:
  Steps to reproduce:
  1. have installed Scilab on Ubuntu Xenial system
  2. install system updates
  3. try to launch Scilab from GUI - it does not start
  4. try to launch Scilab from terminal - it does not start with the following 
output in the terminal:

  $ scilab
  Could not create a Scilab main class. Error:
  Exception in thread "main" java.lang.InternalError: XXX0 profile[1]: GL3bc -> 
profileImpl GL4bc !!! not mapped 
at com.jogamp.opengl.GLProfile.computeProfileMap(GLProfile.java:2071)
at 
com.jogamp.opengl.GLProfile.initProfilesForDeviceCritical(GLProfile.java:1954)
at 
com.jogamp.opengl.GLProfile.initProfilesForDevice(GLProfile.java:1875)
at 
com.jogamp.opengl.GLProfile.initProfilesForDefaultDevices(GLProfile.java:1842)
at com.jogamp.opengl.GLProfile.access$000(GLProfile.java:80)
at com.jogamp.opengl.GLProfile$1.run(GLProfile.java:230)
at java.security.AccessController.doPrivileged(Native Method)
at com.jogamp.opengl.GLProfile.initSingleton(GLProfile.java:216)
at com.jogamp.opengl.GLProfile.getProfileMap(GLProfile.java:2297)
at com.jogamp.opengl.GLProfile.get(GLProfile.java:988)
at com.jogamp.opengl.GLProfile.getDefault(GLProfile.java:722)
at com.jogamp.opengl.GLProfile.getDefault(GLProfile.java:733)
at org.scilab.modules.gui.SwingView.(Unknown Source)
at org.scilab.modules.gui.SwingView.registerSwingView(Unknown Source)
at org.scilab.modules.core.Scilab.(Unknown Source)

  Scilab cannot create Scilab Java Main-Class (we have not been able to
  find the main Scilab class. Check if the Scilab and thirdparty
  packages are available).

  
  Expected results:
  Scilab works normally on Ubuntu 16.04 LTS system.

  Actual results:
  see error above.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: scilab 5.5.2-2ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-104.127-generic 4.4.98
  Uname: Linux 4.4.0-104-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Fri Jan 12 12:02:32 2018
  PackageArchitecture: all
  SourcePackage: scilab
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1727401] Re: Corruption on windowed 3D apps running on dGPU (Intel/AMD)

[Emmanuel Grumbach]

Thanks, I'll get to this on Sunday.

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

Title:
  Corruption on windowed 3D apps running on dGPU (Intel/AMD)

Status in Mesa:
  In Progress
Status in OEM Priority Project:
  Triaged
Status in mesa package in Ubuntu:
  Fix Committed
Status in mesa source package in Xenial:
  Fix Committed
Status in mesa source package in Artful:
  Fix Committed

Bug description:
  [Impact]

  Corruption is seen on windowed 3D apps running on dGPU

  [Test case]

  Get a certain Intel/AMD hybrid machine, run 'DRI_PRIME=1 glxgears',
  see how the window has corrupted gfx.

  The fix is to patch Intel i965_dri driver.

  [Regression potential]

  There could be a slight loss of performance, but corruption free
  behaviour.

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

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

[Desktop-packages] [Bug 1742894] Re: Scilab does not start after some upgrades on Ubuntu Xenial

[Timo Aaltonen]

same bug on Debian, so probably doesn't work in artful either (nor
bionic)

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

Title:
  Scilab does not start after some upgrades on Ubuntu Xenial

Status in mesa package in Ubuntu:
  New
Status in scilab package in Ubuntu:
  New
Status in scilab package in Debian:
  Unknown

Bug description:
  Steps to reproduce:
  1. have installed Scilab on Ubuntu Xenial system
  2. install system updates
  3. try to launch Scilab from GUI - it does not start
  4. try to launch Scilab from terminal - it does not start with the following 
output in the terminal:

  $ scilab
  Could not create a Scilab main class. Error:
  Exception in thread "main" java.lang.InternalError: XXX0 profile[1]: GL3bc -> 
profileImpl GL4bc !!! not mapped 
at com.jogamp.opengl.GLProfile.computeProfileMap(GLProfile.java:2071)
at 
com.jogamp.opengl.GLProfile.initProfilesForDeviceCritical(GLProfile.java:1954)
at 
com.jogamp.opengl.GLProfile.initProfilesForDevice(GLProfile.java:1875)
at 
com.jogamp.opengl.GLProfile.initProfilesForDefaultDevices(GLProfile.java:1842)
at com.jogamp.opengl.GLProfile.access$000(GLProfile.java:80)
at com.jogamp.opengl.GLProfile$1.run(GLProfile.java:230)
at java.security.AccessController.doPrivileged(Native Method)
at com.jogamp.opengl.GLProfile.initSingleton(GLProfile.java:216)
at com.jogamp.opengl.GLProfile.getProfileMap(GLProfile.java:2297)
at com.jogamp.opengl.GLProfile.get(GLProfile.java:988)
at com.jogamp.opengl.GLProfile.getDefault(GLProfile.java:722)
at com.jogamp.opengl.GLProfile.getDefault(GLProfile.java:733)
at org.scilab.modules.gui.SwingView.(Unknown Source)
at org.scilab.modules.gui.SwingView.registerSwingView(Unknown Source)
at org.scilab.modules.core.Scilab.(Unknown Source)

  Scilab cannot create Scilab Java Main-Class (we have not been able to
  find the main Scilab class. Check if the Scilab and thirdparty
  packages are available).

  
  Expected results:
  Scilab works normally on Ubuntu 16.04 LTS system.

  Actual results:
  see error above.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: scilab 5.5.2-2ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-104.127-generic 4.4.98
  Uname: Linux 4.4.0-104-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Fri Jan 12 12:02:32 2018
  PackageArchitecture: all
  SourcePackage: scilab
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1719038] Re: X Server crashes during log in VM starting from Kubuntu 16.04.2

[Gannet]

Any updates?

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

Title:
  X Server crashes during log in VM starting from Kubuntu 16.04.2

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

Bug description:
  If I change screen resolution in my VM with Kubuntu 16.04.3 and then
  make log off and then log on X server is crashes doesn't able me to
  log in.

  Please, look in Xorg.0.log.old for backtrace.

  Also the appropriate report on freedesktop.org:
  https://bugs.freedesktop.org/show_bug.cgi?id=102554

  Host:
  Kubuntu 17.04
  Linux 4.13.2
  libvirt-bin 3.6.0
  qemu 2.10

  
  Guest:
  Kubuntu 16.04.3
  Linux 4.10.0-35-generic
  xserver-xorg-video-qxl 0.1.4-3ubuntu3
  xserver-common 1.18.4-0ubuntu0.3

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xserver-xorg (not installed)
  ProcVersionSignature: Ubuntu 4.10.0-35.39~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-35-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Sat Sep 23 01:27:49 2017
  InstallationDate: Installed on 2016-09-16 (371 days ago)
  InstallationMedia: Kubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  JournalErrors:
   Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] 
failed with exit code 1: Hint: You are currently not seeing messages from other 
users and the system.
 Users in the 'systemd-journal' group can see all messages. Pass -q to
 turn off this notice.
   No journal files were opened due to insufficient permissions.
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1742894] Re: Scilab does not start after some upgrades on Ubuntu Xenial

[Timo Aaltonen]

also, you could try ppa:canonical-x/x-staging which has 17.2.8

** Bug watch added: Debian Bug tracker #880924
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=880924

** Also affects: scilab (Debian) via
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=880924
   Importance: Unknown
   Status: Unknown

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

Title:
  Scilab does not start after some upgrades on Ubuntu Xenial

Status in mesa package in Ubuntu:
  New
Status in scilab package in Ubuntu:
  New
Status in scilab package in Debian:
  Unknown

Bug description:
  Steps to reproduce:
  1. have installed Scilab on Ubuntu Xenial system
  2. install system updates
  3. try to launch Scilab from GUI - it does not start
  4. try to launch Scilab from terminal - it does not start with the following 
output in the terminal:

  $ scilab
  Could not create a Scilab main class. Error:
  Exception in thread "main" java.lang.InternalError: XXX0 profile[1]: GL3bc -> 
profileImpl GL4bc !!! not mapped 
at com.jogamp.opengl.GLProfile.computeProfileMap(GLProfile.java:2071)
at 
com.jogamp.opengl.GLProfile.initProfilesForDeviceCritical(GLProfile.java:1954)
at 
com.jogamp.opengl.GLProfile.initProfilesForDevice(GLProfile.java:1875)
at 
com.jogamp.opengl.GLProfile.initProfilesForDefaultDevices(GLProfile.java:1842)
at com.jogamp.opengl.GLProfile.access$000(GLProfile.java:80)
at com.jogamp.opengl.GLProfile$1.run(GLProfile.java:230)
at java.security.AccessController.doPrivileged(Native Method)
at com.jogamp.opengl.GLProfile.initSingleton(GLProfile.java:216)
at com.jogamp.opengl.GLProfile.getProfileMap(GLProfile.java:2297)
at com.jogamp.opengl.GLProfile.get(GLProfile.java:988)
at com.jogamp.opengl.GLProfile.getDefault(GLProfile.java:722)
at com.jogamp.opengl.GLProfile.getDefault(GLProfile.java:733)
at org.scilab.modules.gui.SwingView.(Unknown Source)
at org.scilab.modules.gui.SwingView.registerSwingView(Unknown Source)
at org.scilab.modules.core.Scilab.(Unknown Source)

  Scilab cannot create Scilab Java Main-Class (we have not been able to
  find the main Scilab class. Check if the Scilab and thirdparty
  packages are available).

  
  Expected results:
  Scilab works normally on Ubuntu 16.04 LTS system.

  Actual results:
  see error above.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: scilab 5.5.2-2ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-104.127-generic 4.4.98
  Uname: Linux 4.4.0-104-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Fri Jan 12 12:02:32 2018
  PackageArchitecture: all
  SourcePackage: scilab
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1742894] Re: Scilab does not start after some upgrades on Ubuntu Xenial

[Norbert]

Upgrading to HWE does not help.

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

Title:
  Scilab does not start after some upgrades on Ubuntu Xenial

Status in mesa package in Ubuntu:
  New
Status in scilab package in Ubuntu:
  New

Bug description:
  Steps to reproduce:
  1. have installed Scilab on Ubuntu Xenial system
  2. install system updates
  3. try to launch Scilab from GUI - it does not start
  4. try to launch Scilab from terminal - it does not start with the following 
output in the terminal:

  $ scilab
  Could not create a Scilab main class. Error:
  Exception in thread "main" java.lang.InternalError: XXX0 profile[1]: GL3bc -> 
profileImpl GL4bc !!! not mapped 
at com.jogamp.opengl.GLProfile.computeProfileMap(GLProfile.java:2071)
at 
com.jogamp.opengl.GLProfile.initProfilesForDeviceCritical(GLProfile.java:1954)
at 
com.jogamp.opengl.GLProfile.initProfilesForDevice(GLProfile.java:1875)
at 
com.jogamp.opengl.GLProfile.initProfilesForDefaultDevices(GLProfile.java:1842)
at com.jogamp.opengl.GLProfile.access$000(GLProfile.java:80)
at com.jogamp.opengl.GLProfile$1.run(GLProfile.java:230)
at java.security.AccessController.doPrivileged(Native Method)
at com.jogamp.opengl.GLProfile.initSingleton(GLProfile.java:216)
at com.jogamp.opengl.GLProfile.getProfileMap(GLProfile.java:2297)
at com.jogamp.opengl.GLProfile.get(GLProfile.java:988)
at com.jogamp.opengl.GLProfile.getDefault(GLProfile.java:722)
at com.jogamp.opengl.GLProfile.getDefault(GLProfile.java:733)
at org.scilab.modules.gui.SwingView.(Unknown Source)
at org.scilab.modules.gui.SwingView.registerSwingView(Unknown Source)
at org.scilab.modules.core.Scilab.(Unknown Source)

  Scilab cannot create Scilab Java Main-Class (we have not been able to
  find the main Scilab class. Check if the Scilab and thirdparty
  packages are available).

  
  Expected results:
  Scilab works normally on Ubuntu 16.04 LTS system.

  Actual results:
  see error above.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: scilab 5.5.2-2ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-104.127-generic 4.4.98
  Uname: Linux 4.4.0-104-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Fri Jan 12 12:02:32 2018
  PackageArchitecture: all
  SourcePackage: scilab
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://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 1742750] Re: [bionic-proposed] Pulseaudio 1:11.1-1ubuntu3 will not start due to invalid /etc/pulse/default.pa file

[Stephen Allen]

Fix works here! Thank-you.

On Fri, Jan 12, 2018 at 12:05 AM Daniel van Vugt <
daniel.van.v...@canonical.com> wrote:

> pulseaudio (1:11.1-1ubuntu4) bionic; urgency=high
>
>   * 0030-load-module-switch-on-connect.patch: Correct typo in default.pa
> causing pulseaudio startup failure. (LP: #1742750, LP: #1732629)
>   * Refresh patches to apply more cleanly:
> - 0802-alsa-mixer-Add-support-for-usb-audio-in-the-Dell-doc.patch
> - 0803-build-sys-add-the-Dell-dock-TB16-configuration.patch
>
>  -- Daniel van Vugt   Fri, 12 Jan 2018
> 10:23:11 +0800
>
> ** Changed in: pulseaudio (Ubuntu)
>Status: In Progress => Fix Released
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (1742769).
> https://bugs.launchpad.net/bugs/1742750
>
> Title:
>   [bionic-proposed] Pulseaudio 1:11.1-1ubuntu3 will not start due to
>   invalid /etc/pulse/default.pa file
>
> Status in pulseaudio package in Ubuntu:
>   Fix Released
>
> Bug description:
>   Version 1:11.1-1ubuntu3 added 0030-load-module-switch-on-
>   connect.patch, which changes line 38 of /etc/pulse/default.pa to read
>   ".endif### Load audio drivers statically".  It appears that there are
>   a couple of line feeds missing here, and having the comment on the
>   same line as the endif causes pulseaudio not to start.
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1742750/+subscriptions
>


-- 

This email is printed from 100% recycled electrons.

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

Title:
  [bionic-proposed] Pulseaudio 1:11.1-1ubuntu3 will not start due to
  invalid /etc/pulse/default.pa file

Status in pulseaudio package in Ubuntu:
  Fix Released

Bug description:
  Version 1:11.1-1ubuntu3 added 0030-load-module-switch-on-
  connect.patch, which changes line 38 of /etc/pulse/default.pa to read
  ".endif### Load audio drivers statically".  It appears that there are
  a couple of line feeds missing here, and having the comment on the
  same line as the endif causes pulseaudio not to start.

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

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

[Desktop-packages] [Bug 1663157] Re: Guest session processes are not confined in 16.10 and newer releases

[Balint Reczey]

@tyhicks I just opened LP #1742912 for tracking the confinement fix.

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

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

Title:
  Guest session processes are not confined in 16.10 and newer releases

Status in Light Display Manager:
  New
Status in lightdm package in Ubuntu:
  Fix Released
Status in lightdm source package in Yakkety:
  Fix Released
Status in lightdm source package in Zesty:
  Fix Released
Status in lightdm source package in Artful:
  Fix Released

Bug description:
  Processes launched under a lightdm guest session are not confined by
  the /usr/lib/lightdm/lightdm-guest-session AppArmor profile in Ubuntu
  16.10, Ubuntu 17.04, and Ubuntu Artful (current dev release). The
  processes are unconfined.

  The simple test case is to log into a guest session, launch a terminal
  with ctrl-alt-t, and run the following command:

   $ cat /proc/self/attr/current

  Expected output, as seen in Ubuntu 16.04 LTS, is:

   /usr/lib/lightdm/lightdm-guest-session (enforce)

  Running the command inside of an Ubuntu 16.10 and newer guest session
  results in:

   unconfined

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

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

[Desktop-packages] [Bug 1742912] [NEW] Please confine guest sessions again

[Balint Reczey]

Public bug reported:

This is a continuation of LP: #1663157 where as a workaround for the
guest session not being confined the session got disabled. This bug
tracks the fix for proper confinement.

Original bug report text:


Processes launched under a lightdm guest session are not confined by the 
/usr/lib/lightdm/lightdm-guest-session AppArmor profile in Ubuntu 16.10, Ubuntu 
17.04, and Ubuntu Artful (current dev release). The processes are unconfined.

The simple test case is to log into a guest session, launch a terminal
with ctrl-alt-t, and run the following command:

 $ cat /proc/self/attr/current

Expected output, as seen in Ubuntu 16.04 LTS, is:

 /usr/lib/lightdm/lightdm-guest-session (enforce)

Running the command inside of an Ubuntu 16.10 and newer guest session
results in:

 unconfined

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

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

Title:
  Please confine guest sessions again

Status in lightdm package in Ubuntu:
  New

Bug description:
  This is a continuation of LP: #1663157 where as a workaround for the
  guest session not being confined the session got disabled. This bug
  tracks the fix for proper confinement.

  Original bug report text:

  
  Processes launched under a lightdm guest session are not confined by the 
/usr/lib/lightdm/lightdm-guest-session AppArmor profile in Ubuntu 16.10, Ubuntu 
17.04, and Ubuntu Artful (current dev release). The processes are unconfined.

  The simple test case is to log into a guest session, launch a terminal
  with ctrl-alt-t, and run the following command:

   $ cat /proc/self/attr/current

  Expected output, as seen in Ubuntu 16.04 LTS, is:

   /usr/lib/lightdm/lightdm-guest-session (enforce)

  Running the command inside of an Ubuntu 16.10 and newer guest session
  results in:

   unconfined

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

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

[Desktop-packages] [Bug 1642965] Comment bridged from LTC Bugzilla

[bugproxy]

--- Comment From heinz-werner_se...@de.ibm.com 2018-01-12 05:35 EDT---
IBM bugzilla status -> closed, current out-of-sope for s390x. If this will 
change, a new bugzilla be created.

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

Title:
  Firefox crashes - Error loading theme icon

Status in firefox package in Ubuntu:
  Won't Fix

Bug description:
  Linux lnx 4.4.0-45-generic #66-Ubuntu SMP Wed Oct 19 14:14:35 UTC 2016 s390x 
s390x s390x GNU/Linux
  Firefox:
  firefox   47.0+build3-0ubuntu0.16.04.1

  Description:
  Firefox crashes when trying to start it on the server and display on the 
local client.
  Other X application can be displayed.

  Reproduction:
  Login to the server: ssh -X lnxserver
  Start firefox: firefox --no-remote

  Error Message:
  (firefox:39655): Gtk-WARNING **: Error loading theme icon 'list-add' for 
stock: Icon 'list-add' not present in theme System
  Segmentation fault (core dumped)

  == Comment: #6 - Thorsten Diehl  - 2016-11-16 
11:50:35 ==
  I can confirm this.

  I installed Ubuntu 16.04.1 on s390x (z13 machine) and installed updates, then 
x11-apps, which were working fine (xclock, xeyes).
  I installed firefox and started it:
  firefox --no-remote 
  it created tons of messages, all complaing about an unknown image format.
  Any subsequent start does not create that many messages. But even with 
--safe-mode I can't get it started:
  root@s8330009:~# firefox --no-remote --safe-mode

  (firefox:1487): Gtk-WARNING **: Locale not supported by C library.
Using the fallback 'C' locale.
  Crash Annotation GraphicsCriticalError: |[0][GFX1]: Unknown image format 1 
(t=0.627128) [GFX1]: Unknown image format 1
  Crash Annotation GraphicsCriticalError: |[0][GFX1]: Unknown image format 1 
(t=0.627128) |[1][GFX1]: Unknown image format 0 (t=0.631695) [GFX1]: Unknown 
image format 0
  [1487] ###!!! ABORT: X_ShmAttach: BadAccess (attempt to access private 
resource denied); 3 requests ago: file 
/build/firefox-xMihVX/firefox-47.0+build3/toolkit/xre/nsX11ErrorHandler.cpp, 
line 157
  [1487] ###!!! ABORT: X_ShmAttach: BadAccess (attempt to access private 
resource denied); 3 requests ago: file 
/build/firefox-xMihVX/firefox-47.0+build3/toolkit/xre/nsX11ErrorHandler.cpp, 
line 157

  Perhaps a graphics library (gtklib?) has a problem?

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

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

[Desktop-packages] [Bug 1735594] Re: [regression] compiz crashes after Mesa upgrade

[Janghou]

And see:
https://askubuntu.com/questions/992571/gui-unity-crashing-in-16-04-lts-after-updates-2018-01-04-compiz-segfaults/993205

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

Title:
  [regression] compiz crashes after Mesa upgrade

Status in mesa package in Ubuntu:
  Fix Committed
Status in mesa source package in Xenial:
  Fix Committed
Status in mesa source package in Artful:
  Fix Committed

Bug description:
  [Impact]
  When I use the Unity session I automatically get logged out under these 
conditions:

  When I hover with my mouse over any icon of the sidebar.
  When I press the alt key.
  When I press the super key.

  running dmesg after this unwanted logout happens I get following
  information:

  compiz[10616]: segfault at 0 ip 7fbca309feeb sp 7fff5f59a4d0
  error 4 in i965_dri.so[7fbca2af6000+7e4000]

  This is caused by a mesa upgrade, which added a patch for bug #1727401. The 
crasher is reproduced on:
  - gen4 / gen5 Intel
  - if using modesetting X driver, like when xserver-xorg-video-intel is not 
installed, or the HWE stack is installed (xserver-xorg-core-hwe-16.04 defaults 
to modesetting)

  [Test case]
  Log in to Unity, open the dash or try to log out etc. Compiz shouldn't crash.

  [Regression potential]
  The backported patches need to be tested, here for regressions and on 1727401 
that they fix the original bug (again).

  Best to test on a wide array of Intel HW:
  gen4 (965GM/GM45/G45)
  gen5 (Ironlake)
  gen6 (Sandy Bridge)
  gen7 (Bay Trail, Ivy Bridge, Haswell)
  gen8 (Braswell, Broadwell)
  gen9 (Apollo Lake, Skylake, Gemini Lake, Kaby Lake, Coffee Lake)

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

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

[Desktop-packages] [Bug 1735594] Re: [regression] compiz crashes after Mesa upgrade

[Janghou]

@Emmanuel
If you get an error installing sudo apt-get install 
libgl1-mesa-dri/xenial-proposed, temporarily remove the file 
`/etc/apt/preferences.d/proposed-updates`

Add that file again afterwards to prevent upgrading all packages in proposed.
Package: *
Pin: release a=xenial-proposed
Pin-Priority: 400

See https://wiki.ubuntu.com/Testing/EnableProposed

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

Title:
  [regression] compiz crashes after Mesa upgrade

Status in mesa package in Ubuntu:
  Fix Committed
Status in mesa source package in Xenial:
  Fix Committed
Status in mesa source package in Artful:
  Fix Committed

Bug description:
  [Impact]
  When I use the Unity session I automatically get logged out under these 
conditions:

  When I hover with my mouse over any icon of the sidebar.
  When I press the alt key.
  When I press the super key.

  running dmesg after this unwanted logout happens I get following
  information:

  compiz[10616]: segfault at 0 ip 7fbca309feeb sp 7fff5f59a4d0
  error 4 in i965_dri.so[7fbca2af6000+7e4000]

  This is caused by a mesa upgrade, which added a patch for bug #1727401. The 
crasher is reproduced on:
  - gen4 / gen5 Intel
  - if using modesetting X driver, like when xserver-xorg-video-intel is not 
installed, or the HWE stack is installed (xserver-xorg-core-hwe-16.04 defaults 
to modesetting)

  [Test case]
  Log in to Unity, open the dash or try to log out etc. Compiz shouldn't crash.

  [Regression potential]
  The backported patches need to be tested, here for regressions and on 1727401 
that they fix the original bug (again).

  Best to test on a wide array of Intel HW:
  gen4 (965GM/GM45/G45)
  gen5 (Ironlake)
  gen6 (Sandy Bridge)
  gen7 (Bay Trail, Ivy Bridge, Haswell)
  gen8 (Braswell, Broadwell)
  gen9 (Apollo Lake, Skylake, Gemini Lake, Kaby Lake, Coffee Lake)

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

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

[Desktop-packages] [Bug 1735594] Re: [regression] compiz crashes after Mesa upgrade

[Janghou]

Proposed fixed it.

$ apt policy libgl1-mesa-dri
libgl1-mesa-dri:
  Installed: 17.2.4-0ubuntu1~16.04.3
  Candidate: 17.2.4-0ubuntu1~16.04.3
  Version table:
 *** 17.2.4-0ubuntu1~16.04.3 500
500 http://archive.ubuntu.com/ubuntu xenial-proposed/main amd64 Packages
100 /var/lib/dpkg/status
 17.2.4-0ubuntu1~16.04.2 -1
500 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages
 11.2.0-1ubuntu2 500
500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages

product: Mobile 4 Series Chipset Integrated Graphics Controller
vendor: Intel Corporation

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

Title:
  [regression] compiz crashes after Mesa upgrade

Status in mesa package in Ubuntu:
  Fix Committed
Status in mesa source package in Xenial:
  Fix Committed
Status in mesa source package in Artful:
  Fix Committed

Bug description:
  [Impact]
  When I use the Unity session I automatically get logged out under these 
conditions:

  When I hover with my mouse over any icon of the sidebar.
  When I press the alt key.
  When I press the super key.

  running dmesg after this unwanted logout happens I get following
  information:

  compiz[10616]: segfault at 0 ip 7fbca309feeb sp 7fff5f59a4d0
  error 4 in i965_dri.so[7fbca2af6000+7e4000]

  This is caused by a mesa upgrade, which added a patch for bug #1727401. The 
crasher is reproduced on:
  - gen4 / gen5 Intel
  - if using modesetting X driver, like when xserver-xorg-video-intel is not 
installed, or the HWE stack is installed (xserver-xorg-core-hwe-16.04 defaults 
to modesetting)

  [Test case]
  Log in to Unity, open the dash or try to log out etc. Compiz shouldn't crash.

  [Regression potential]
  The backported patches need to be tested, here for regressions and on 1727401 
that they fix the original bug (again).

  Best to test on a wide array of Intel HW:
  gen4 (965GM/GM45/G45)
  gen5 (Ironlake)
  gen6 (Sandy Bridge)
  gen7 (Bay Trail, Ivy Bridge, Haswell)
  gen8 (Braswell, Broadwell)
  gen9 (Apollo Lake, Skylake, Gemini Lake, Kaby Lake, Coffee Lake)

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

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

[Desktop-packages] [Bug 1742894] Re: Scilab does not start after some upgrades on Ubuntu Xenial

[Norbert]

Installed `vainfo` and `mesa-va-drivers`
`sudo apt-get install mesa-va-drivers vainfo`

Here is my output of `vainfo`:


$ vainfo 
libva info: VA-API version 0.39.0
libva info: va_getDriverName() returns 0
libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/r600_drv_video.so
libva info: Found init function __vaDriverInit_0_39
libva info: va_openDriver() returns 0
vainfo: VA-API version: 0.39 (libva 1.7.0)
vainfo: Driver version: mesa gallium vaapi
vainfo: Supported profile and entrypoints
  VAProfileMPEG2Simple: VAEntrypointVLD
  VAProfileMPEG2Main  : VAEntrypointVLD
  VAProfileVC1Simple  : VAEntrypointVLD
  VAProfileVC1Main: VAEntrypointVLD
  VAProfileVC1Advanced: VAEntrypointVLD
  VAProfileH264ConstrainedBaseline: VAEntrypointVLD
  VAProfileH264ConstrainedBaseline: VAEntrypointEncSlice
  VAProfileH264Main   : VAEntrypointVLD
  VAProfileH264Main   : VAEntrypointEncSlice
  VAProfileH264High   : VAEntrypointVLD
  VAProfileH264High   : VAEntrypointEncSlice
  VAProfileNone   : VAEntrypointVideoProc

$ lspci -knn | grep -A3 VGA
00:01.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. 
[AMD/ATI] Trinity [Radeon HD 7480D] [1002:9993]
Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD 7480D] 
[1002:0123]
Kernel driver in use: radeon
Kernel modules: radeon


$ cat /proc/cmdline 
BOOT_IMAGE=/boot/vmlinuz-4.4.0-109-generic root=UUID=... ro splash quiet 
vt.handoff=7


$ glxinfo | grep -i 'direct\|vendor\|opengl'
direct rendering: Yes
server glx vendor string: SGI
client glx vendor string: Mesa Project and SGI
Vendor: X.Org (0x1002)
OpenGL vendor string: X.Org
OpenGL renderer string: AMD ARUBA (DRM 2.43.0 / 4.4.0-109-generic, LLVM 5.0.0)
OpenGL core profile version string: 4.1 (Core Profile) Mesa 17.2.4
OpenGL core profile shading language version string: 4.10
OpenGL core profile context flags: (none)
OpenGL core profile profile mask: core profile
OpenGL core profile extensions:
GL_ARB_direct_state_access, GL_ARB_draw_buffers, 
GL_ARB_draw_indirect, GL_ARB_draw_instanced, 
GL_ARB_map_buffer_range, GL_ARB_multi_bind, GL_ARB_multi_draw_indirect, 
OpenGL version string: 3.0 Mesa 17.2.4
OpenGL shading language version string: 1.30
OpenGL context flags: (none)
OpenGL extensions:
OpenGL ES profile version string: OpenGL ES 3.0 Mesa 17.2.4
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.00
OpenGL ES profile extensions:

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

Title:
  Scilab does not start after some upgrades on Ubuntu Xenial

Status in mesa package in Ubuntu:
  New
Status in scilab package in Ubuntu:
  New

Bug description:
  Steps to reproduce:
  1. have installed Scilab on Ubuntu Xenial system
  2. install system updates
  3. try to launch Scilab from GUI - it does not start
  4. try to launch Scilab from terminal - it does not start with the following 
output in the terminal:

  $ scilab
  Could not create a Scilab main class. Error:
  Exception in thread "main" java.lang.InternalError: XXX0 profile[1]: GL3bc -> 
profileImpl GL4bc !!! not mapped 
at com.jogamp.opengl.GLProfile.computeProfileMap(GLProfile.java:2071)
at 
com.jogamp.opengl.GLProfile.initProfilesForDeviceCritical(GLProfile.java:1954)
at 
com.jogamp.opengl.GLProfile.initProfilesForDevice(GLProfile.java:1875)
at 
com.jogamp.opengl.GLProfile.initProfilesForDefaultDevices(GLProfile.java:1842)
at com.jogamp.opengl.GLProfile.access$000(GLProfile.java:80)
at com.jogamp.opengl.GLProfile$1.run(GLProfile.java:230)
at java.security.AccessController.doPrivileged(Native Method)
at com.jogamp.opengl.GLProfile.initSingleton(GLProfile.java:216)
at com.jogamp.opengl.GLProfile.getProfileMap(GLProfile.java:2297)
at com.jogamp.opengl.GLProfile.get(GLProfile.java:988)
at com.jogamp.opengl.GLProfile.getDefault(GLProfile.java:722)
at com.jogamp.opengl.GLProfile.getDefault(GLProfile.java:733)
at org.scilab.modules.gui.SwingView.(Unknown Source)
at org.scilab.modules.gui.SwingView.registerSwingView(Unknown Source)
at org.scilab.modules.core.Scilab.(Unknown Source)

  Scilab cannot create Scilab Java Main-Class (we have not been able to
  find the main Scilab class. Check if the Scilab and thirdparty
  packages are available).

  
  Expected results:
  Scilab works normally on Ubuntu 16.04 LTS system.

  Actual results:
  see error above.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: scilab 5.5.2-2ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-104.127-generic 4.4.98
  Uname: Linux 4.4.0-104-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  

[Desktop-packages] [Bug 1742740] Re: Vulnerable to Spectre

[Olivier Tilloy]

More info at https://www.chromium.org/Home/chromium-security/ssca:

 « Chrome's JavaScript engine, V8, will include mitigations starting
with Chrome 64, which will be released on or around January 23rd 2018.
Future Chrome releases will include additional mitigations and hardening
measures which will further reduce the impact of this class of attack.
Additionally, the SharedArrayBuffer feature is being disabled by
default. The mitigations may incur a performance penalty.

   In line with other browsers, Chrome has disabled SharedArrayBuffer on
Chrome 63 starting on Jan 5th, and will modify the behavior of other
APIs such as performance.now, to help reduce the efficacy of speculative
side-channel attacks. This is intended as a temporary measure until
other mitigations are in place. »


I tested chromium 64.0.3282.39 against the Tencent tool, and it is reported as 
NOT VULNERABLE.

There's a build of chromium 63.0.3239.132 currently going, I will test
it and report here as soon as it's completed.

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

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

** Changed in: chromium-browser (Ubuntu)
 Assignee: (unassigned) => Olivier Tilloy (osomon)

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

Title:
  Vulnerable to Spectre

Status in chromium-browser package in Ubuntu:
  Confirmed

Bug description:
  Hi Folks,

  Chromium is still vulnerable to Spectre. You can check it:

   http://xlab.tencent.com/special/spectre/spectre_check.html

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: chromium-browser 63.0.3239.108-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  Uname: Linux 4.13.0-25-generic x86_64
  NonfreeKernelModules: nvidia_uvm wl nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.8-0ubuntu6
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Jan 11 17:45:51 2018
  DetectedPlugins:
   
  InstallationDate: Installed on 2018-01-01 (9 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171221)
  SourcePackage: chromium-browser
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.default.chromium-browser: [deleted]

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

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

[Desktop-packages] [Bug 1160569] Re: GLib-CRITICAL **: g_slice_set_config: assertion 'sys_page_size == 0' failed

[Max]

It seems a Glib issue, I see this example:
console-kit-daemon[2448]: (process:13258): GLib-CRITICAL **: 
g_slice_set_config: assertion 'sys_page_size == 0' failed

Ubuntu :: 16.04.3
consolekit :: 0.4.6-5
libglib2.0-0:i386 :: 2.48.2-0ubuntu1

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

Title:
  GLib-CRITICAL **: g_slice_set_config: assertion 'sys_page_size == 0'
  failed

Status in Mozilla Firefox:
  Fix Released
Status in firefox package in Ubuntu:
  Fix Released
Status in thunderbird package in Ubuntu:
  Triaged

Bug description:
  Have a look at the screen-shot for more details.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: firefox 19.0.2+build1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.8.0-14.24-generic 3.8.4
  Uname: Linux 3.8.0-14-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.9.2-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  BuildID: 20130308124351
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  Channel: Unavailable
  Date: Tue Mar 26 21:48:57 2013
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2013-03-26 (0 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64+mac (20130326)
  IpRoute:
   default via 10.0.1.1 dev eth0  proto static
   10.0.1.0/24 dev eth0  proto kernel  scope link  src 10.0.1.16  metric 1
   169.254.0.0/16 dev eth0  scope link  metric 1000
  IwConfig:
   eth0  no wireless extensions.

   lono wireless extensions.
  MarkForUpload: True
  Plugins:
   Windows Media Player Plug-in 10 (compatible; Videos) - 
/usr/lib/mozilla/plugins/libtotem-gmp-plugin.so (totem-mozilla)
   VLC Multimedia Plugin (compatible Videos 3.6.3) - 
/usr/lib/mozilla/plugins/libtotem-cone-plugin.so (totem-mozilla)
   DivX® Web Player - /usr/lib/mozilla/plugins/libtotem-mully-plugin.so 
(totem-mozilla)
   QuickTime Plug-in 7.6.6 - 
/usr/lib/mozilla/plugins/libtotem-narrowspace-plugin.so (totem-mozilla)
   iTunes Application Detector - 
/usr/lib/mozilla/plugins/librhythmbox-itms-detection-plugin.so 
(rhythmbox-mozilla)
  PrefSources: prefs.js
  Profiles: Profile0 (Default) - LastVersion=19.0.2/20130308124351
  RelatedPackageVersions:
   totem-mozilla 3.6.3-0ubuntu4
   rhythmbox-mozilla 2.98-0ubuntu3
  RfKill:

  RunningIncompatibleAddons: False
  SourcePackage: firefox
  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.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH

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

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

[Desktop-packages] [Bug 1742901] Re: package cups-daemon 2.1.3-4ubuntu0.3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[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 cups in Ubuntu.
https://bugs.launchpad.net/bugs/1742901

Title:
  package cups-daemon 2.1.3-4ubuntu0.3 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 1

Status in cups package in Ubuntu:
  New

Bug description:
  i don't know

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: cups-daemon 2.1.3-4ubuntu0.3
  ProcVersionSignature: Ubuntu 4.4.0-104.127-generic 4.4.98
  Uname: Linux 4.4.0-104-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CupsErrorLog:
   E [12/Jan/2018:11:32:20 +0200] HP-DeskJet-4670-series: File 
\"/usr/lib/cups/filter/hpcups\" not available: No such file or directory
   E [12/Jan/2018:11:32:20 +0200] HP-DeskJet-4670-series: File 
\"/usr/lib/cups/filter/hpcups\" not available: No such file or directory
  Date: Fri Jan 12 11:43:52 2018
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2017-01-03 (373 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  Lpstat:
   device for EPSON-AL-CX16NF: 
dnssd://EPSON%20AL-CX16NF-5FD934._pdl-datastream._tcp.local/
   device for HP-DeskJet-4670-series: 
dnssd://HP%20DeskJet%204670%20series%20%5B22083D%5D._ipp._tcp.local/?uuid=1c852a4d-b800-1f08-abcd-f430b922083d
   device for OKI-DATA-CORP-C301: 
dnssd://OKI-C301-ACD8ED._pdl-datastream._tcp.local/
  MachineType: LENOVO 42334AG
  Papersize: a4
  PpdFiles:
   OKI-DATA-CORP-C301: Oki C301dn Foomatic/foo2hiperc (recommended)
   HP-DeskJet-4670-series: HP Deskjet 4670 Series, hpcups 3.16.3
   EPSON-AL-CX16NF: KONICA MINOLTA magicolor 1600W Foomatic/foo2lava 
(recommended)
  ProcCmdline: BOOT_IMAGE=/vmlinuz-4.4.0-104-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-104-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.3
   apt  1.2.24
  SourcePackage: cups
  Title: package cups-daemon 2.1.3-4ubuntu0.3 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/22/2009
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6GET18WW(V1.09)
  dmi.board.name: KIWDX
  dmi.board.vendor: LENOVO
  dmi.board.version: REFERENCE
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnLENOVO:bvr6GET18WW(V1.09):bd05/22/2009:svnLENOVO:pn42334AG:pvrLenovo3000N500:rvnLENOVO:rnKIWDX:rvrREFERENCE:cvnNoEnclosure:ct10:cvrN/A:
  dmi.product.name: 42334AG
  dmi.product.version: Lenovo 3000 N500
  dmi.sys.vendor: LENOVO
  mtime.conffile..etc.init.d.cups: 2017-12-06T20:23:04.314671

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

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

[Desktop-packages] [Bug 1742901] [NEW] package cups-daemon 2.1.3-4ubuntu0.3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[Makis Dimi]

Public bug reported:

i don't know

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: cups-daemon 2.1.3-4ubuntu0.3
ProcVersionSignature: Ubuntu 4.4.0-104.127-generic 4.4.98
Uname: Linux 4.4.0-104-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.15
Architecture: amd64
CupsErrorLog:
 E [12/Jan/2018:11:32:20 +0200] HP-DeskJet-4670-series: File 
\"/usr/lib/cups/filter/hpcups\" not available: No such file or directory
 E [12/Jan/2018:11:32:20 +0200] HP-DeskJet-4670-series: File 
\"/usr/lib/cups/filter/hpcups\" not available: No such file or directory
Date: Fri Jan 12 11:43:52 2018
ErrorMessage: subprocess installed post-installation script returned error exit 
status 1
InstallationDate: Installed on 2017-01-03 (373 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
Lpstat:
 device for EPSON-AL-CX16NF: 
dnssd://EPSON%20AL-CX16NF-5FD934._pdl-datastream._tcp.local/
 device for HP-DeskJet-4670-series: 
dnssd://HP%20DeskJet%204670%20series%20%5B22083D%5D._ipp._tcp.local/?uuid=1c852a4d-b800-1f08-abcd-f430b922083d
 device for OKI-DATA-CORP-C301: 
dnssd://OKI-C301-ACD8ED._pdl-datastream._tcp.local/
MachineType: LENOVO 42334AG
Papersize: a4
PpdFiles:
 OKI-DATA-CORP-C301: Oki C301dn Foomatic/foo2hiperc (recommended)
 HP-DeskJet-4670-series: HP Deskjet 4670 Series, hpcups 3.16.3
 EPSON-AL-CX16NF: KONICA MINOLTA magicolor 1600W Foomatic/foo2lava (recommended)
ProcCmdline: BOOT_IMAGE=/vmlinuz-4.4.0-104-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-104-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.3
 apt  1.2.24
SourcePackage: cups
Title: package cups-daemon 2.1.3-4ubuntu0.3 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/22/2009
dmi.bios.vendor: LENOVO
dmi.bios.version: 6GET18WW(V1.09)
dmi.board.name: KIWDX
dmi.board.vendor: LENOVO
dmi.board.version: REFERENCE
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: No Enclosure
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnLENOVO:bvr6GET18WW(V1.09):bd05/22/2009:svnLENOVO:pn42334AG:pvrLenovo3000N500:rvnLENOVO:rnKIWDX:rvrREFERENCE:cvnNoEnclosure:ct10:cvrN/A:
dmi.product.name: 42334AG
dmi.product.version: Lenovo 3000 N500
dmi.sys.vendor: LENOVO
mtime.conffile..etc.init.d.cups: 2017-12-06T20:23:04.314671

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


** Tags: amd64 apport-package xenial

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

Title:
  package cups-daemon 2.1.3-4ubuntu0.3 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 1

Status in cups package in Ubuntu:
  New

Bug description:
  i don't know

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: cups-daemon 2.1.3-4ubuntu0.3
  ProcVersionSignature: Ubuntu 4.4.0-104.127-generic 4.4.98
  Uname: Linux 4.4.0-104-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CupsErrorLog:
   E [12/Jan/2018:11:32:20 +0200] HP-DeskJet-4670-series: File 
\"/usr/lib/cups/filter/hpcups\" not available: No such file or directory
   E [12/Jan/2018:11:32:20 +0200] HP-DeskJet-4670-series: File 
\"/usr/lib/cups/filter/hpcups\" not available: No such file or directory
  Date: Fri Jan 12 11:43:52 2018
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2017-01-03 (373 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  Lpstat:
   device for EPSON-AL-CX16NF: 
dnssd://EPSON%20AL-CX16NF-5FD934._pdl-datastream._tcp.local/
   device for HP-DeskJet-4670-series: 
dnssd://HP%20DeskJet%204670%20series%20%5B22083D%5D._ipp._tcp.local/?uuid=1c852a4d-b800-1f08-abcd-f430b922083d
   device for OKI-DATA-CORP-C301: 
dnssd://OKI-C301-ACD8ED._pdl-datastream._tcp.local/
  MachineType: LENOVO 42334AG
  Papersize: a4
  PpdFiles:
   OKI-DATA-CORP-C301: Oki C301dn Foomatic/foo2hiperc (recommended)
   HP-DeskJet-4670-series: HP Deskjet 4670 Series, hpcups 3.16.3
   EPSON-AL-CX16NF: KONICA MINOLTA magicolor 1600W Foomatic/foo2lava 
(recommended)
  ProcCmdline: BOOT_IMAGE=/vmlinuz-4.4.0-104-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-104-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.3
   apt  1.2.24
  SourcePackage: cups
  Title: package cups-daemon 2.1.3-4ubuntu0.3 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 

[Desktop-packages] [Bug 1264368] Re: GLib-CRITICAL **: Source ID was not found when attempting to remove it - warning when leaving Network menu of g-c-c

[Max]

Ubuntu:: 16.04.3
gnome-screensaver :: 3.6.1-7ubuntu4
libglib2.0-0:i386 :: 2.48.2-0ubuntu1

Another example:
org.gnome.ScreenSaver[1963]: (gnome-screensaver:2131): GLib-CRITICAL **: Source 
ID 4988 was not found when attempting to remove it

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

Title:
  GLib-CRITICAL **: Source ID was not found when attempting to remove it
  - warning when leaving Network menu of g-c-c

Status in AndroidSDK:
  New
Status in Banshee:
  New
Status in gnome-control-center:
  Incomplete
Status in GParted:
  Unknown
Status in notification-daemon:
  New
Status in anjuta package in Ubuntu:
  Confirmed
Status in consolekit package in Ubuntu:
  Confirmed
Status in f-spot package in Ubuntu:
  Confirmed
Status in gnome-control-center package in Ubuntu:
  Triaged
Status in gnome-mplayer package in Ubuntu:
  Confirmed
Status in putty package in Ubuntu:
  Confirmed

Bug description:
  Steps to recreate:
  1. Open gnome-control-center in terminal.
  2. Go to Network.
  3. Go back to All preferences.
  4. Notice that in terminal there is a warning:

  $ gnome-control-center

  (gnome-control-center:13519): GLib-CRITICAL **: Source ID 166 was not
  found when attempting to remove it

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: gnome-control-center 1:3.6.3-0ubuntu49
  ProcVersionSignature: Ubuntu 3.12.0-7.15-generic 3.12.4
  Uname: Linux 3.12.0-7-generic x86_64
  ApportVersion: 2.12.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Dec 26 21:03:52 2013
  InstallationDate: Installed on 2013-10-15 (71 days ago)
  InstallationMedia: Ubuntu-GNOME 13.10 "Saucy Salamander" - Release amd64 
(20131015)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pl_PL.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to trusty on 2013-11-05 (51 days ago)

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

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

[Desktop-packages] [Bug 1742894] Re: Scilab does not start after some upgrades on Ubuntu Xenial

[Norbert]

According to scilab changelog it does not changed since

scilab (5.5.2-2ubuntu3) xenial; urgency=medium

  * Enable debian/patches/fop-2.0.diff again to avoid a FTBFS
since fop 2.0 is now in Ubuntu.

 -- Graham Inggs   Wed, 06 Apr 2016 18:32:35 +0200


So it is graphics issue. Possible related to bug 1741447.

** Also affects: mesa (Ubuntu)
   Importance: Undecided
   Status: 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/1742894

Title:
  Scilab does not start after some upgrades on Ubuntu Xenial

Status in mesa package in Ubuntu:
  New
Status in scilab package in Ubuntu:
  New

Bug description:
  Steps to reproduce:
  1. have installed Scilab on Ubuntu Xenial system
  2. install system updates
  3. try to launch Scilab from GUI - it does not start
  4. try to launch Scilab from terminal - it does not start with the following 
output in the terminal:

  $ scilab
  Could not create a Scilab main class. Error:
  Exception in thread "main" java.lang.InternalError: XXX0 profile[1]: GL3bc -> 
profileImpl GL4bc !!! not mapped 
at com.jogamp.opengl.GLProfile.computeProfileMap(GLProfile.java:2071)
at 
com.jogamp.opengl.GLProfile.initProfilesForDeviceCritical(GLProfile.java:1954)
at 
com.jogamp.opengl.GLProfile.initProfilesForDevice(GLProfile.java:1875)
at 
com.jogamp.opengl.GLProfile.initProfilesForDefaultDevices(GLProfile.java:1842)
at com.jogamp.opengl.GLProfile.access$000(GLProfile.java:80)
at com.jogamp.opengl.GLProfile$1.run(GLProfile.java:230)
at java.security.AccessController.doPrivileged(Native Method)
at com.jogamp.opengl.GLProfile.initSingleton(GLProfile.java:216)
at com.jogamp.opengl.GLProfile.getProfileMap(GLProfile.java:2297)
at com.jogamp.opengl.GLProfile.get(GLProfile.java:988)
at com.jogamp.opengl.GLProfile.getDefault(GLProfile.java:722)
at com.jogamp.opengl.GLProfile.getDefault(GLProfile.java:733)
at org.scilab.modules.gui.SwingView.(Unknown Source)
at org.scilab.modules.gui.SwingView.registerSwingView(Unknown Source)
at org.scilab.modules.core.Scilab.(Unknown Source)

  Scilab cannot create Scilab Java Main-Class (we have not been able to
  find the main Scilab class. Check if the Scilab and thirdparty
  packages are available).

  
  Expected results:
  Scilab works normally on Ubuntu 16.04 LTS system.

  Actual results:
  see error above.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: scilab 5.5.2-2ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-104.127-generic 4.4.98
  Uname: Linux 4.4.0-104-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Fri Jan 12 12:02:32 2018
  PackageArchitecture: all
  SourcePackage: scilab
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1742443] Re: Ubuntu 18.04: PrtSc doesn't trigger gnome-screenshot

[Launchpad Bug Tracker]

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

** Changed in: gnome-screenshot (Ubuntu)
   Status: New => Confirmed

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

Title:
  Ubuntu 18.04: PrtSc doesn't trigger gnome-screenshot

Status in gnome-screenshot package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 18.04
  gnome-screenshot v 3.25.0-0ubuntu2 (amd64)

  Using the PrtSc button, alone or in combination with shift, alt or
  ctrl, doesn't trigger the gnome-screenshot window that asks to save
  the image.

  The screen blinks (so the button is intercepted) but no window is
  triggered.

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

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

[Desktop-packages] [Bug 1742443] Re: Ubuntu 18.04: PrtSc doesn't trigger gnome-screenshot

[Paul White]

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

** Tags added: bionic

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

Title:
  Ubuntu 18.04: PrtSc doesn't trigger gnome-screenshot

Status in gnome-screenshot package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 18.04
  gnome-screenshot v 3.25.0-0ubuntu2 (amd64)

  Using the PrtSc button, alone or in combination with shift, alt or
  ctrl, doesn't trigger the gnome-screenshot window that asks to save
  the image.

  The screen blinks (so the button is intercepted) but no window is
  triggered.

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

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