date:20180222

Public bug reported:

The following unit test is failing:

subsequent_filters-test.cxx:2398:Assertion
Test name: ScFiltersTest::testOrcusODSStyleInterface
equality assertion failed
- Expected: Color: R:254 G:255 B: 204
- Actual  : Color: R:255 G:255 B: 255

This is most likely caused by that upstream change:
https://gitlab.com/orcus/orcus/commit/f821995022df8dd1e580dd22cf131584b2b1ac4f

** Affects: libreoffice (Ubuntu)
 Importance: High
 Assignee: Olivier Tilloy (osomon)
 Status: In Progress

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

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

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

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

Title:
  libreoffice FTBFS with liborcus 0.13.3

Status in libreoffice package in Ubuntu:
  In Progress

Bug description:
  The following unit test is failing:

  subsequent_filters-test.cxx:2398:Assertion
  Test name: ScFiltersTest::testOrcusODSStyleInterface
  equality assertion failed
  - Expected: Color: R:254 G:255 B: 204
  - Actual  : Color: R:255 G:255 B: 255

  This is most likely caused by that upstream change:
  https://gitlab.com/orcus/orcus/commit/f821995022df8dd1e580dd22cf131584b2b1ac4f

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

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

[Desktop-packages] [Bug 1750982] Re: libreoffice FTBFS with liborcus 0.13.3

Bug reported upstream:
https://bugs.documentfoundation.org/show_bug.cgi?id=115931

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

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

Title:
  libreoffice FTBFS with liborcus 0.13.3

Status in libreoffice package in Ubuntu:
  In Progress

Bug description:
  The following unit test is failing:

  subsequent_filters-test.cxx:2398:Assertion
  Test name: ScFiltersTest::testOrcusODSStyleInterface
  equality assertion failed
  - Expected: Color: R:254 G:255 B: 204
  - Actual  : Color: R:255 G:255 B: 255

  This is most likely caused by that upstream change:
  https://gitlab.com/orcus/orcus/commit/f821995022df8dd1e580dd22cf131584b2b1ac4f

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

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

[Desktop-packages] [Bug 1750937] Re: 14.04 Kernel update on 2/21 breaks Nvidia drivers

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

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

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

Title:
  14.04 Kernel update on 2/21 breaks Nvidia drivers

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  Running fine with nvidia-384 until this kernel update came along.
  When booted into the new kernel, got super low resolution and nvidia-
  settings was missing most of its functionality - could not change
  resolution.

  Rebooted into 4.4.0-112 kernel and all was well.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 4.4.0-112.135~14.04.1-generic 4.4.98
  Uname: Linux 4.4.0-112-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  384.111  Tue Dec 19 23:51:45 
PST 2017
   GCC version:  gcc version 4.8.4 (Ubuntu 4.8.4-2ubuntu1~14.04.3)
  ApportVersion: 2.14.1-0ubuntu3.27
  Architecture: amd64
  CurrentDesktop: LXDE
  Date: Wed Feb 21 19:23:39 2018
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.7, 4.4.0-112-generic, x86_64: installed
   bbswitch, 0.7, 4.4.0-116-generic, x86_64: installed
   nvidia-384, 384.111, 4.4.0-112-generic, x86_64: installed
   nvidia-384, 384.111, 4.4.0-116-generic, x86_64: installed
  GraphicsCard:
   NVIDIA Corporation Device [10de:1c82] (rev a1) (prog-if 00 [VGA controller])
 Subsystem: eVga.com. Corp. Device [3842:6253]
  InstallationDate: Installed on 2015-03-03 (1086 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  MachineType: ASUSTeK COMPUTER INC. M11AD
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-112-generic 
root=UUID=5a88d2a1-0a24-415b-adc2-28435b13248a ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/15/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0302
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: M11AD
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0302:bd08/15/2013:svnASUSTeKCOMPUTERINC.:pnM11AD:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnM11AD:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: M11AD
  dmi.product.version: System Version
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz 1:0.9.11.3+14.04.20160425-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.14.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri N/A
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Wed Feb 21 18:48:14 2018
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.18.3-1ubuntu2.3~trusty4

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

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

[Desktop-packages] [Bug 1750937] Re: 14.04 Kernel update on 2/21 breaks Nvidia drivers

2018-02-22 Thread mtron

same here on trusty with kernel 4.4.0-116-generic and NVIDIA Driver
340.102 on a GeForce GT 420

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

Title:
  14.04 Kernel update on 2/21 breaks Nvidia drivers

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  Running fine with nvidia-384 until this kernel update came along.
  When booted into the new kernel, got super low resolution and nvidia-
  settings was missing most of its functionality - could not change
  resolution.

  Rebooted into 4.4.0-112 kernel and all was well.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 4.4.0-112.135~14.04.1-generic 4.4.98
  Uname: Linux 4.4.0-112-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  384.111  Tue Dec 19 23:51:45 
PST 2017
   GCC version:  gcc version 4.8.4 (Ubuntu 4.8.4-2ubuntu1~14.04.3)
  ApportVersion: 2.14.1-0ubuntu3.27
  Architecture: amd64
  CurrentDesktop: LXDE
  Date: Wed Feb 21 19:23:39 2018
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.7, 4.4.0-112-generic, x86_64: installed
   bbswitch, 0.7, 4.4.0-116-generic, x86_64: installed
   nvidia-384, 384.111, 4.4.0-112-generic, x86_64: installed
   nvidia-384, 384.111, 4.4.0-116-generic, x86_64: installed
  GraphicsCard:
   NVIDIA Corporation Device [10de:1c82] (rev a1) (prog-if 00 [VGA controller])
 Subsystem: eVga.com. Corp. Device [3842:6253]
  InstallationDate: Installed on 2015-03-03 (1086 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  MachineType: ASUSTeK COMPUTER INC. M11AD
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-112-generic 
root=UUID=5a88d2a1-0a24-415b-adc2-28435b13248a ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/15/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0302
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: M11AD
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0302:bd08/15/2013:svnASUSTeKCOMPUTERINC.:pnM11AD:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnM11AD:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: M11AD
  dmi.product.version: System Version
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz 1:0.9.11.3+14.04.20160425-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.14.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri N/A
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Wed Feb 21 18:48:14 2018
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.18.3-1ubuntu2.3~trusty4

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

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

[Desktop-packages] [Bug 1750995] [NEW] Cannot logout live session

2018-02-22 Thread Jean-Baptiste Lallement

Public bug reported:

Bionic Desktop 20180221

Test Case
1. Start a live session
2. Logout

Expected result
the greeter is displayed

Actual result
A console is displayed and after a very long moment the greeter is finally 
showing up.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: ubuntu-session 3.26.1-0ubuntu9
ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
Uname: Linux 4.13.0-32-generic x86_64
ApportVersion: 2.20.8-0ubuntu10
Architecture: amd64
CasperVersion: 1.388
Date: Thu Feb 22 08:24:52 2018
LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180221)
ProcEnviron:
 TERM=linux
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=C.UTF-8
 SHELL=/bin/bash
SourcePackage: gnome-session
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug bionic rls-bb-incoming

** Attachment added: "journal.log"
   
https://bugs.launchpad.net/bugs/1750995/+attachment/5060179/+files/journal.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/1750995

Title:
  Cannot logout live session

Status in gnome-session package in Ubuntu:
  New

Bug description:
  Bionic Desktop 20180221

  Test Case
  1. Start a live session
  2. Logout

  Expected result
  the greeter is displayed

  Actual result
  A console is displayed and after a very long moment the greeter is finally 
showing up.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: ubuntu-session 3.26.1-0ubuntu9
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CasperVersion: 1.388
  Date: Thu Feb 22 08:24:52 2018
  LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180221)
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.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/1750995/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-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

This bug was fixed in the package pulseaudio - 1:8.0-0ubuntu3.8

---
pulseaudio (1:8.0-0ubuntu3.8) xenial; urgency=medium

  [Hui Wang]
  * Cherrypick fixes for supporting audio on Dell dock TB16:
- 60c0edd5: Add support for usb audio on the Dell dock TB16 (LP: #1718824)
- 2f1dcea3: build-sys: add the Dell dock TB16 configuration (LP: #1718824)

  [Daniel van Vugt]
  * Tidy up: Rename 0901-droid-fix-crash-on-module-load.patch to
0803-droid-fix-crash-on-module-load.patch

 -- Daniel van Vugt   Tue, 12 Dec 2017
11:44:08 +0800

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

-- 
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:
  Fix Released
Status in pulseaudio source package in Xenial:
  Fix Released
Status in pulseaudio source package in Artful:
  Fix Released

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 1718824] Re: The analogue audio does not work on the Dell USB Dock

This bug was fixed in the package pulseaudio - 1:10.0-2ubuntu3.1

---
pulseaudio (1:10.0-2ubuntu3.1) artful; urgency=medium

  * Cherrypick fixes for supporting audio on Dell dock TB16:
- 60c0edd5: Add support for usb audio on the Dell dock TB16 (LP: #1718824)
- 2f1dcea3: build-sys: add the Dell dock TB16 configuration (LP: #1718824)

 -- Hui Wang   Tue, 19 Dec 2017 15:16:57 +0800

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

-- 
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:
  Fix Released
Status in pulseaudio source package in Xenial:
  Fix Released
Status in pulseaudio source package in Artful:
  Fix Released

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 1718824] Update Released

2018-02-22 Thread Łukasz Zemczak

The verification of the Stable Release Update for pulseaudio has
completed successfully and the package has now been released to
-updates.  Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to 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:
  Fix Released
Status in pulseaudio source package in Xenial:
  Fix Released
Status in pulseaudio source package in Artful:
  Fix Released

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 1750995] Re: Logging out live session takes several minutes

2018-02-22 Thread Jean-Baptiste Lallement

** Summary changed:

- Cannot logout live session
+ Logging out live session takes several minutes

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

Title:
  Logging out live session takes several minutes

Status in gnome-session package in Ubuntu:
  New

Bug description:
  Bionic Desktop 20180221

  Test Case
  1. Start a live session
  2. Logout

  Expected result
  the greeter is displayed

  Actual result
  A console is displayed and after a very long moment the greeter is finally 
showing up.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: ubuntu-session 3.26.1-0ubuntu9
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CasperVersion: 1.388
  Date: Thu Feb 22 08:24:52 2018
  LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180221)
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.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/1750995/+subscriptions

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

[Desktop-packages] [Bug 1749585] Re: postgresql-client-common is not compatible with current postgresql-servers

2018-02-22 Thread Marc F. Neininger

Hello,

can anyone please tell me how to use pg_dump in Xenial with a postgresql Server 
9.6?
I would really appreciate any solution as I'm no more capable to dump any 
databases from 9.6 Servers :-/

TIA

Marc

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

Title:
  postgresql-client-common is not compatible with current postgresql-
  servers

Status in postgresql-common package in Ubuntu:
  New

Bug description:
  Hi,
  i'm using 16.04 xenial  as host for applications. Our DB-server was updated 
from 9.4 to 9.6 recently and I'm using pg_dump from time to time to clone 
databases. But I'm no more able to do that :-(

  Right now postgresql-client-common can connect to pg up to version 9.5 . I 
tried to install postgresql-client-9.6 manually but I failed because 
postgresql-client-9.6 depends on a newer version of libpg5.  As a workaround I 
tried to manually install the latest version of libpg5 (9.6.7) but another 
depenency (libgss...?) failed.
  Can you please have a look or even ask upstream about the possibility to 
provide postgresql-client for all current server versions (9.6,and 10.2??)

  Nevertheless thank you all for providing the software. It works like a
  charm

  Marc

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

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

[Desktop-packages] [Bug 1750982] Re: libreoffice FTBFS with liborcus 0.13.3

Tentative patch (untested):
https://git.launchpad.net/~libreoffice/ubuntu/+source/libreoffice/commit/?id=7104e5a4f84ed4ed396f390627d6122df686ac1f

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

Title:
  libreoffice FTBFS with liborcus 0.13.3

Status in libreoffice package in Ubuntu:
  In Progress

Bug description:
  The following unit test is failing:

  subsequent_filters-test.cxx:2398:Assertion
  Test name: ScFiltersTest::testOrcusODSStyleInterface
  equality assertion failed
  - Expected: Color: R:254 G:255 B: 204
  - Actual  : Color: R:255 G:255 B: 255

  This is most likely caused by that upstream change:
  https://gitlab.com/orcus/orcus/commit/f821995022df8dd1e580dd22cf131584b2b1ac4f

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

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

[Desktop-packages] [Bug 1750937] Re: 14.04 Kernel update on 2/21 breaks Nvidia drivers

2018-02-22 Thread Joakim Fogelström Hardingz

Same here with the 384.89 driver (Trusty with 4.4.0-166-generic kernel)

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

Title:
  14.04 Kernel update on 2/21 breaks Nvidia drivers

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  Running fine with nvidia-384 until this kernel update came along.
  When booted into the new kernel, got super low resolution and nvidia-
  settings was missing most of its functionality - could not change
  resolution.

  Rebooted into 4.4.0-112 kernel and all was well.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 4.4.0-112.135~14.04.1-generic 4.4.98
  Uname: Linux 4.4.0-112-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  384.111  Tue Dec 19 23:51:45 
PST 2017
   GCC version:  gcc version 4.8.4 (Ubuntu 4.8.4-2ubuntu1~14.04.3)
  ApportVersion: 2.14.1-0ubuntu3.27
  Architecture: amd64
  CurrentDesktop: LXDE
  Date: Wed Feb 21 19:23:39 2018
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.7, 4.4.0-112-generic, x86_64: installed
   bbswitch, 0.7, 4.4.0-116-generic, x86_64: installed
   nvidia-384, 384.111, 4.4.0-112-generic, x86_64: installed
   nvidia-384, 384.111, 4.4.0-116-generic, x86_64: installed
  GraphicsCard:
   NVIDIA Corporation Device [10de:1c82] (rev a1) (prog-if 00 [VGA controller])
 Subsystem: eVga.com. Corp. Device [3842:6253]
  InstallationDate: Installed on 2015-03-03 (1086 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  MachineType: ASUSTeK COMPUTER INC. M11AD
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-112-generic 
root=UUID=5a88d2a1-0a24-415b-adc2-28435b13248a ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/15/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0302
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: M11AD
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0302:bd08/15/2013:svnASUSTeKCOMPUTERINC.:pnM11AD:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnM11AD:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: M11AD
  dmi.product.version: System Version
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz 1:0.9.11.3+14.04.20160425-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.14.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri N/A
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Wed Feb 21 18:48:14 2018
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.18.3-1ubuntu2.3~trusty4

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

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

[Desktop-packages] [Bug 1750335] Re: LO 6.0 autopkgtest failures (uicheck: test_text_direction)

It turns out this is due to missing files in the l10n packages:

> I see (at least) /usr/lib/libreoffice/share/registry/ctl_he.xcd
> missing on a first glance.

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

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

Title:
  LO 6.0 autopkgtest failures (uicheck: test_text_direction)

Status in libreoffice package in Ubuntu:
  Confirmed

Bug description:
  autopkgtests for libreoffice 6.0.1-0ubuntu1 (currently in bionic-
  proposed) are consistently failing:

  ==
  ERROR: test_text_direction (pageDialog.WriterPageDialog)
  --
  Traceback (most recent call last):
File "/tmp/autopkgtest.zEJ7dp/build.U4P/src/uitest/uitest/framework.py", 
line 46, in tearDown
  self.connection.tearDown()
File 
"/tmp/autopkgtest.zEJ7dp/build.U4P/src/uitest/libreoffice/connection.py", line 
192, in tearDown
  self.connection.tearDown()
File 
"/tmp/autopkgtest.zEJ7dp/build.U4P/src/uitest/libreoffice/connection.py", line 
152, in tearDown
  raise Exception("Exit status indicates failure: " + str(ret))
  Exception: Exit status indicates failure: 1

  ==
  FAIL: test_text_direction (pageDialog.WriterPageDialog) (i=1)
  --
  Traceback (most recent call last):
File 
"/tmp/autopkgtest.zEJ7dp/build.U4P/src/uitest/writer_tests/pageDialog.py", line 
220, in test_text_direction
  get_state_as_dict(xTextDirectionList)["SelectEntryText"], 
lTextDirection[i])
  AssertionError: 'Left-to-right (horizontal)' != 'Right-to-left (horizontal)'
  - Left-to-right (horizontal)
  + Right-to-left (horizontal)

  
  ==
  FAIL: test_text_direction (pageDialog.WriterPageDialog) (i=2)
  --
  Traceback (most recent call last):
File 
"/tmp/autopkgtest.zEJ7dp/build.U4P/src/uitest/writer_tests/pageDialog.py", line 
220, in test_text_direction
  get_state_as_dict(xTextDirectionList)["SelectEntryText"], 
lTextDirection[i])
  AssertionError: 'Left-to-right (horizontal)' != 'Right-to-left (vertical)'
  - Left-to-right (horizontal)
  + Right-to-left (vertical)

  
  ==
  FAIL: test_text_direction (pageDialog.WriterPageDialog) (i=3)
  --
  Traceback (most recent call last):
File 
"/tmp/autopkgtest.zEJ7dp/build.U4P/src/uitest/writer_tests/pageDialog.py", line 
220, in test_text_direction
  get_state_as_dict(xTextDirectionList)["SelectEntryText"], 
lTextDirection[i])
  AssertionError: 'Left-to-right (horizontal)' != 'Left-to-right (vertical)'
  - Left-to-right (horizontal)
  ?^^  
  + Left-to-right (vertical)
  ?^^ + ^

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

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

[Desktop-packages] [Bug 1751005] [NEW] libreoffice cannot open a document not within $HOME

2018-02-22 Thread Mike Cornelison

Public bug reported:

Starting with today's update to LibreOffice 5.4.5.1 40m0(Build:1), files
not within the user $HOME directory cannot be opened. This has nothing
to do with ownership or permissions - the target document is owned by
the user with full permissions. Moving the file to ~/Desktop allows it
to be opened normally.

Error message in popup window:
  Access to /home2/mico/documents/personal/2018 lists.ods was denied.

Error message when launched from terminal:
$: localc "2018 lists.ods"
javaldx: Could not find a Java Runtime Environment!
Please ensure that a JVM and the package libreoffice-java-common is installed.
If it is already installed then try removing 
~/.libreoffice/3/user/config/javasettings_Linux_*.xml
Warning: failed to read path from javaldx

The file mentioned in the error message does not exist.
I removed the corresponding file under ~/.libreoffice/4/ but that makes no 
difference.

This but started in Ubuntu 18.04 (alpha) around Feb. 15, and with
today's update (Feb. 22) it appeared in Ubuntu 17.10.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: libreoffice-core 1:5.4.5-0ubuntu0.17.10.1
ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13
Uname: Linux 4.13.0-36-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.7
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Thu Feb 22 09:35:49 2018
InstallationDate: Installed on 2018-01-27 (25 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
SourcePackage: libreoffice
UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  libreoffice cannot open a document not within $HOME

Status in libreoffice package in Ubuntu:
  New

Bug description:
  Starting with today's update to LibreOffice 5.4.5.1 40m0(Build:1),
  files not within the user $HOME directory cannot be opened. This has
  nothing to do with ownership or permissions - the target document is
  owned by the user with full permissions. Moving the file to ~/Desktop
  allows it to be opened normally.

  Error message in popup window:
Access to /home2/mico/documents/personal/2018 lists.ods was denied.

  Error message when launched from terminal:
  $: localc "2018 lists.ods"
  javaldx: Could not find a Java Runtime Environment!
  Please ensure that a JVM and the package libreoffice-java-common is installed.
  If it is already installed then try removing 
~/.libreoffice/3/user/config/javasettings_Linux_*.xml
  Warning: failed to read path from javaldx

  The file mentioned in the error message does not exist.
  I removed the corresponding file under ~/.libreoffice/4/ but that makes no 
difference.

  This but started in Ubuntu 18.04 (alpha) around Feb. 15, and with
  today's update (Feb. 22) it appeared in Ubuntu 17.10.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: libreoffice-core 1:5.4.5-0ubuntu0.17.10.1
  ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13
  Uname: Linux 4.13.0-36-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Feb 22 09:35:49 2018
  InstallationDate: Installed on 2018-01-27 (25 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1721428] Re: Artful (17.10) Session logout after screen turned off

2018-02-22 Thread Craig Carnell

It's set to private at request

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

Title:
  Artful (17.10) Session logout after screen turned off

Status in GNOME Shell:
  Unknown
Status in Nouveau Xorg driver:
  New
Status in gnome-shell package in Ubuntu:
  Incomplete
Status in mutter package in Ubuntu:
  Incomplete

Bug description:
  Whenever I turn off my screen, the computer (a desktop PC) logs me out
  of my session.

  Here is a discussion thread with users of similar issue:
  
https://ubuntuforums.org/showthread.php?t=2372388&p=13694312&posted=1#post13694312

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

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

[Desktop-packages] [Bug 1750628] [NEW] "Insert Emoji" menu is untranslated

You have been subscribed to a public bug:

If you try to use the "Insert Emoji" menu from another application, it's
untranslated on non-English Ubuntu 18.04 system. See the attached
screenshots.

** Affects: ubuntu-translations
 Importance: Undecided
 Status: Incomplete

** Affects: gtk+3.0 (Ubuntu)
 Importance: Low
 Status: New


** Tags: bionic l10n
-- 
"Insert Emoji" menu is untranslated
https://bugs.launchpad.net/bugs/1750628
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to gtk+3.0 in Ubuntu.

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

[Desktop-packages] [Bug 1751005] Re: libreoffice cannot open a document not within $HOME

I get the problem with system complaining about permissions on
.config/libreoffice/4 since latest libreoffice upgrade on ubuntu 17.10.
This problem has arrived on 3 installs up to now. Only solution I have
found is to add the ppa on libreoffice and upgrade it to the latest
libreoffice 6. Then it starts without any problems. Which proves to me
that this is NOT a correct error description from libreoffice. The
problem is not about permissions at all.

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

Title:
  libreoffice cannot open a document not within $HOME

Status in libreoffice package in Ubuntu:
  New

Bug description:
  Starting with today's update to LibreOffice 5.4.5.1 40m0(Build:1),
  files not within the user $HOME directory cannot be opened. This has
  nothing to do with ownership or permissions - the target document is
  owned by the user with full permissions. Moving the file to ~/Desktop
  allows it to be opened normally.

  Error message in popup window:
Access to /home2/mico/documents/personal/2018 lists.ods was denied.

  Error message when launched from terminal:
  $: localc "2018 lists.ods"
  javaldx: Could not find a Java Runtime Environment!
  Please ensure that a JVM and the package libreoffice-java-common is installed.
  If it is already installed then try removing 
~/.libreoffice/3/user/config/javasettings_Linux_*.xml
  Warning: failed to read path from javaldx

  The file mentioned in the error message does not exist.
  I removed the corresponding file under ~/.libreoffice/4/ but that makes no 
difference.

  This but started in Ubuntu 18.04 (alpha) around Feb. 15, and with
  today's update (Feb. 22) it appeared in Ubuntu 17.10.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: libreoffice-core 1:5.4.5-0ubuntu0.17.10.1
  ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13
  Uname: Linux 4.13.0-36-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Feb 22 09:35:49 2018
  InstallationDate: Installed on 2018-01-27 (25 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1750628] Re: "Insert Emoji" menu is untranslated

** Package changed: language-pack-gnome-cs (Ubuntu) => gtk+3.0 (Ubuntu)

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

Title:
  "Insert Emoji" menu is untranslated

Status in Ubuntu Translations:
  Incomplete
Status in gtk+3.0 package in Ubuntu:
  New

Bug description:
  If you try to use the "Insert Emoji" menu from another application,
  it's untranslated on non-English Ubuntu 18.04 system. See the attached
  screenshots.

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

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

[Desktop-packages] [Bug 1750335] Re: LO 6.0 autopkgtest failures (uicheck: test_text_direction)

And manually installing the missing files makes the tests pass.

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

Title:
  LO 6.0 autopkgtest failures (uicheck: test_text_direction)

Status in libreoffice package in Ubuntu:
  Confirmed

Bug description:
  autopkgtests for libreoffice 6.0.1-0ubuntu1 (currently in bionic-
  proposed) are consistently failing:

  ==
  ERROR: test_text_direction (pageDialog.WriterPageDialog)
  --
  Traceback (most recent call last):
File "/tmp/autopkgtest.zEJ7dp/build.U4P/src/uitest/uitest/framework.py", 
line 46, in tearDown
  self.connection.tearDown()
File 
"/tmp/autopkgtest.zEJ7dp/build.U4P/src/uitest/libreoffice/connection.py", line 
192, in tearDown
  self.connection.tearDown()
File 
"/tmp/autopkgtest.zEJ7dp/build.U4P/src/uitest/libreoffice/connection.py", line 
152, in tearDown
  raise Exception("Exit status indicates failure: " + str(ret))
  Exception: Exit status indicates failure: 1

  ==
  FAIL: test_text_direction (pageDialog.WriterPageDialog) (i=1)
  --
  Traceback (most recent call last):
File 
"/tmp/autopkgtest.zEJ7dp/build.U4P/src/uitest/writer_tests/pageDialog.py", line 
220, in test_text_direction
  get_state_as_dict(xTextDirectionList)["SelectEntryText"], 
lTextDirection[i])
  AssertionError: 'Left-to-right (horizontal)' != 'Right-to-left (horizontal)'
  - Left-to-right (horizontal)
  + Right-to-left (horizontal)

  
  ==
  FAIL: test_text_direction (pageDialog.WriterPageDialog) (i=2)
  --
  Traceback (most recent call last):
File 
"/tmp/autopkgtest.zEJ7dp/build.U4P/src/uitest/writer_tests/pageDialog.py", line 
220, in test_text_direction
  get_state_as_dict(xTextDirectionList)["SelectEntryText"], 
lTextDirection[i])
  AssertionError: 'Left-to-right (horizontal)' != 'Right-to-left (vertical)'
  - Left-to-right (horizontal)
  + Right-to-left (vertical)

  
  ==
  FAIL: test_text_direction (pageDialog.WriterPageDialog) (i=3)
  --
  Traceback (most recent call last):
File 
"/tmp/autopkgtest.zEJ7dp/build.U4P/src/uitest/writer_tests/pageDialog.py", line 
220, in test_text_direction
  get_state_as_dict(xTextDirectionList)["SelectEntryText"], 
lTextDirection[i])
  AssertionError: 'Left-to-right (horizontal)' != 'Left-to-right (vertical)'
  - Left-to-right (horizontal)
  ?^^  
  + Left-to-right (vertical)
  ?^^ + ^

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

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

[Desktop-packages] [Bug 1750937] Re: 14.04 Kernel update on 2/21 breaks Nvidia drivers

2018-02-22 Thread nurgazy

Same here with 384.111 driver (Linux Mint with 4.4.0-116-generic
kernel).

Dmesg

[  119.939634] nvidia: version magic '4.4.0-116-generic SMP mod_unload 
modversions ' should be '4.4.0-116-generic SMP mod_unload modversions retpoline 
'
[  119.943728] nvidia: version magic '4.4.0-116-generic SMP mod_unload 
modversions ' should be '4.4.0-116-generic SMP mod_unload modversions retpoline 
'

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

Title:
  14.04 Kernel update on 2/21 breaks Nvidia drivers

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  Running fine with nvidia-384 until this kernel update came along.
  When booted into the new kernel, got super low resolution and nvidia-
  settings was missing most of its functionality - could not change
  resolution.

  Rebooted into 4.4.0-112 kernel and all was well.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 4.4.0-112.135~14.04.1-generic 4.4.98
  Uname: Linux 4.4.0-112-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  384.111  Tue Dec 19 23:51:45 
PST 2017
   GCC version:  gcc version 4.8.4 (Ubuntu 4.8.4-2ubuntu1~14.04.3)
  ApportVersion: 2.14.1-0ubuntu3.27
  Architecture: amd64
  CurrentDesktop: LXDE
  Date: Wed Feb 21 19:23:39 2018
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.7, 4.4.0-112-generic, x86_64: installed
   bbswitch, 0.7, 4.4.0-116-generic, x86_64: installed
   nvidia-384, 384.111, 4.4.0-112-generic, x86_64: installed
   nvidia-384, 384.111, 4.4.0-116-generic, x86_64: installed
  GraphicsCard:
   NVIDIA Corporation Device [10de:1c82] (rev a1) (prog-if 00 [VGA controller])
 Subsystem: eVga.com. Corp. Device [3842:6253]
  InstallationDate: Installed on 2015-03-03 (1086 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  MachineType: ASUSTeK COMPUTER INC. M11AD
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-112-generic 
root=UUID=5a88d2a1-0a24-415b-adc2-28435b13248a ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/15/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0302
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: M11AD
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0302:bd08/15/2013:svnASUSTeKCOMPUTERINC.:pnM11AD:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnM11AD:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: M11AD
  dmi.product.version: System Version
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz 1:0.9.11.3+14.04.20160425-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.14.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri N/A
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Wed Feb 21 18:48:14 2018
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.18.3-1ubuntu2.3~trusty4

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

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

[Desktop-packages] [Bug 1732704] Re: Window opened with shortcut custom global shortcut does not get focus

apport information

** Tags added: apport-collected artful

** Description changed:

  I have a custom shortcut set to open google translate in firefox.  If
  I'm using firefox already, this key combination will open a new firefox
  window with translate, yet it will not have focus.
  
  This is problematic in that I must then type  to focus the
  window.
  
  Steps:
  
  1. create a custom shortcut to the command "/usr/bin/firefox --browser
  --new-window translate.google.com"
  
  2. open a firefox window.
  3. type the shortcut.
  4. see that the window does not have focus (even if it may appear in front!)
+ --- 
+ ApportVersion: 2.20.7-0ubuntu3.7
+ Architecture: amd64
+ CurrentDesktop: ubuntu:GNOME
+ DisplayManager: gdm3
+ DistroRelease: Ubuntu 17.10
+ GsettingsChanges:
+  org.gnome.shell enabled-extensions 
['workspace-g...@mathematical.coffee.gmail.com', 'alt-tab-worksp...@kwalo.net', 
'system-moni...@paradoxxx.zero.gmail.com', 
'user-th...@gnome-shell-extensions.gcampax.github.com', 
'ubuntu-d...@ubuntu.com', 'ubuntu-appindicat...@ubuntu.com']
+  org.gnome.shell enable-hot-corners true
+  org.gnome.shell favorite-apps ['googleinbox.desktop', 
'googlecalendar.desktop', 'org.gnome.Nautilus.desktop', 'firefox.desktop']
+  org.gnome.desktop.interface gtk-im-module 'gtk-im-context-simple'
+  org.gnome.desktop.interface monospace-font-name 'Ubuntu Mono 11'
+ InstallationDate: Installed on 2018-01-05 (47 days ago)
+ InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
+ NonfreeKernelModules: wl
+ Package: gnome-shell 3.26.2-0ubuntu0.1
+ PackageArchitecture: amd64
+ ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
+ Tags:  artful
+ Uname: Linux 4.13.0-32-generic x86_64
+ UpgradeStatus: Upgraded to artful on 2018-01-05 (47 days ago)
+ UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
+ _MarkForUpload: True

** Attachment added: "Dependencies.txt"
   
https://bugs.launchpad.net/bugs/1732704/+attachment/5060227/+files/Dependencies.txt

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

Title:
  Window opened with shortcut custom global shortcut does not get focus

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  I have a custom shortcut set to open google translate in firefox.  If
  I'm using firefox already, this key combination will open a new
  firefox window with translate, yet it will not have focus.

  This is problematic in that I must then type  to focus the
  window.

  Steps:

  1. create a custom shortcut to the command "/usr/bin/firefox --browser
  --new-window translate.google.com"

  2. open a firefox window.
  3. type the shortcut.
  4. see that the window does not have focus (even if it may appear in front!)
  --- 
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 17.10
  GsettingsChanges:
   org.gnome.shell enabled-extensions 
['workspace-g...@mathematical.coffee.gmail.com', 'alt-tab-worksp...@kwalo.net', 
'system-moni...@paradoxxx.zero.gmail.com', 
'user-th...@gnome-shell-extensions.gcampax.github.com', 
'ubuntu-d...@ubuntu.com', 'ubuntu-appindicat...@ubuntu.com']
   org.gnome.shell enable-hot-corners true
   org.gnome.shell favorite-apps ['googleinbox.desktop', 
'googlecalendar.desktop', 'org.gnome.Nautilus.desktop', 'firefox.desktop']
   org.gnome.desktop.interface gtk-im-module 'gtk-im-context-simple'
   org.gnome.desktop.interface monospace-font-name 'Ubuntu Mono 11'
  InstallationDate: Installed on 2018-01-05 (47 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  NonfreeKernelModules: wl
  Package: gnome-shell 3.26.2-0ubuntu0.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Tags:  artful
  Uname: Linux 4.13.0-32-generic x86_64
  UpgradeStatus: Upgraded to artful on 2018-01-05 (47 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Desktop-packages] [Bug 1732704] ProcCpuinfoMinimal.txt

apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1732704/+attachment/5060229/+files/ProcCpuinfoMinimal.txt

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

Title:
  Window opened with shortcut custom global shortcut does not get focus

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  I have a custom shortcut set to open google translate in firefox.  If
  I'm using firefox already, this key combination will open a new
  firefox window with translate, yet it will not have focus.

  This is problematic in that I must then type  to focus the
  window.

  Steps:

  1. create a custom shortcut to the command "/usr/bin/firefox --browser
  --new-window translate.google.com"

  2. open a firefox window.
  3. type the shortcut.
  4. see that the window does not have focus (even if it may appear in front!)
  --- 
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 17.10
  GsettingsChanges:
   org.gnome.shell enabled-extensions 
['workspace-g...@mathematical.coffee.gmail.com', 'alt-tab-worksp...@kwalo.net', 
'system-moni...@paradoxxx.zero.gmail.com', 
'user-th...@gnome-shell-extensions.gcampax.github.com', 
'ubuntu-d...@ubuntu.com', 'ubuntu-appindicat...@ubuntu.com']
   org.gnome.shell enable-hot-corners true
   org.gnome.shell favorite-apps ['googleinbox.desktop', 
'googlecalendar.desktop', 'org.gnome.Nautilus.desktop', 'firefox.desktop']
   org.gnome.desktop.interface gtk-im-module 'gtk-im-context-simple'
   org.gnome.desktop.interface monospace-font-name 'Ubuntu Mono 11'
  InstallationDate: Installed on 2018-01-05 (47 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  NonfreeKernelModules: wl
  Package: gnome-shell 3.26.2-0ubuntu0.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Tags:  artful
  Uname: Linux 4.13.0-32-generic x86_64
  UpgradeStatus: Upgraded to artful on 2018-01-05 (47 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Desktop-packages] [Bug 1732704] ProcEnviron.txt

apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1732704/+attachment/5060230/+files/ProcEnviron.txt

** Changed in: gnome-shell (Ubuntu)
   Status: Expired => Confirmed

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

Title:
  Window opened with shortcut custom global shortcut does not get focus

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  I have a custom shortcut set to open google translate in firefox.  If
  I'm using firefox already, this key combination will open a new
  firefox window with translate, yet it will not have focus.

  This is problematic in that I must then type  to focus the
  window.

  Steps:

  1. create a custom shortcut to the command "/usr/bin/firefox --browser
  --new-window translate.google.com"

  2. open a firefox window.
  3. type the shortcut.
  4. see that the window does not have focus (even if it may appear in front!)
  --- 
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 17.10
  GsettingsChanges:
   org.gnome.shell enabled-extensions 
['workspace-g...@mathematical.coffee.gmail.com', 'alt-tab-worksp...@kwalo.net', 
'system-moni...@paradoxxx.zero.gmail.com', 
'user-th...@gnome-shell-extensions.gcampax.github.com', 
'ubuntu-d...@ubuntu.com', 'ubuntu-appindicat...@ubuntu.com']
   org.gnome.shell enable-hot-corners true
   org.gnome.shell favorite-apps ['googleinbox.desktop', 
'googlecalendar.desktop', 'org.gnome.Nautilus.desktop', 'firefox.desktop']
   org.gnome.desktop.interface gtk-im-module 'gtk-im-context-simple'
   org.gnome.desktop.interface monospace-font-name 'Ubuntu Mono 11'
  InstallationDate: Installed on 2018-01-05 (47 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  NonfreeKernelModules: wl
  Package: gnome-shell 3.26.2-0ubuntu0.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Tags:  artful
  Uname: Linux 4.13.0-32-generic x86_64
  UpgradeStatus: Upgraded to artful on 2018-01-05 (47 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Desktop-packages] [Bug 1732704] JournalErrors.txt

apport information

** Attachment added: "JournalErrors.txt"
   
https://bugs.launchpad.net/bugs/1732704/+attachment/5060228/+files/JournalErrors.txt

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

Title:
  Window opened with shortcut custom global shortcut does not get focus

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  I have a custom shortcut set to open google translate in firefox.  If
  I'm using firefox already, this key combination will open a new
  firefox window with translate, yet it will not have focus.

  This is problematic in that I must then type  to focus the
  window.

  Steps:

  1. create a custom shortcut to the command "/usr/bin/firefox --browser
  --new-window translate.google.com"

  2. open a firefox window.
  3. type the shortcut.
  4. see that the window does not have focus (even if it may appear in front!)
  --- 
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 17.10
  GsettingsChanges:
   org.gnome.shell enabled-extensions 
['workspace-g...@mathematical.coffee.gmail.com', 'alt-tab-worksp...@kwalo.net', 
'system-moni...@paradoxxx.zero.gmail.com', 
'user-th...@gnome-shell-extensions.gcampax.github.com', 
'ubuntu-d...@ubuntu.com', 'ubuntu-appindicat...@ubuntu.com']
   org.gnome.shell enable-hot-corners true
   org.gnome.shell favorite-apps ['googleinbox.desktop', 
'googlecalendar.desktop', 'org.gnome.Nautilus.desktop', 'firefox.desktop']
   org.gnome.desktop.interface gtk-im-module 'gtk-im-context-simple'
   org.gnome.desktop.interface monospace-font-name 'Ubuntu Mono 11'
  InstallationDate: Installed on 2018-01-05 (47 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  NonfreeKernelModules: wl
  Package: gnome-shell 3.26.2-0ubuntu0.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Tags:  artful
  Uname: Linux 4.13.0-32-generic x86_64
  UpgradeStatus: Upgraded to artful on 2018-01-05 (47 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Desktop-packages] [Bug 1616332] Re: gnome-software using hundreds of MB of memory when not in use

2018-02-22 Thread Pablo Catalina

Seems that it is could be a duplicated of #1723362

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

Title:
  gnome-software using hundreds of MB of memory when not in use

Status in gnome-software package in Ubuntu:
  Triaged

Bug description:
  It seems gnome-software is running in the background all the time. Not
  a big deal if it was lightweight, but it seems to use hundreds of MB
  (from smem output):

PID User Command Swap  USS  PSS  
RSS 
   2291 jan  /usr/bin/gnome-software --g   285436   112576   117982   
134036 

  A total of over 400MB in RAM and swap combined.

  After killing and restarting, it takes "only" a bit over 100MB.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gnome-software 
3.20.1+git20160617.1.0440874.ubuntu-xenial-0ubuntu1~16.04.1
  ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10
  Uname: Linux 4.4.0-24-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Aug 24 09:45:53 2016
  InstallationDate: Installed on 2012-11-10 (1382 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
  SourcePackage: gnome-software
  UpgradeStatus: Upgraded to xenial on 2016-06-19 (65 days ago)

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

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

[Desktop-packages] [Bug 1734545] Re: Translations not updated from upstream

This bug was fixed in the package gnome-sudoku - 1:3.27.3-1build2

---
gnome-sudoku (1:3.27.3-1build2) bionic; urgency=medium

  * Yet another no change rebuild after unsetting translations sharing on
launchpad, that should allow the translations to be imported
(lp: #1734545)

 -- Sebastien Bacher   Thu, 22 Feb 2018 10:25:46
+0100

** Changed in: gnome-sudoku (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  Translations not updated from upstream

Status in gnome-sudoku package in Ubuntu:
  Fix Released

Bug description:
  The Danish translation of gnome-sudoku lacks many strings as it has
  not been synchronized with upstream for years:

  https://translations.launchpad.net/ubuntu/+source/gnome-sudoku

  Meanwhile gnome-sudoku is and has always been completely translated
  upstream.  Indeed it has been fully translated for every release of
  GNOME ever since it forked out of gnome-games.  Take for example
  current master:

  https://l10n.gnome.org/vertimus/gnome-sudoku/master/po/da

  It seems there are rather grave problems with translation imports in
  Launchpad.  I reported a similar issue recently for util-linux:

  https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1730793

  Who knows how many other packages are affected, and in what languages.
  I think Launchpad translations should be disabled entirely for all
  source packages - the translations belong upstream, with the project.

  Thanks to scootergrisen for making me aware of this problem.

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

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

[Desktop-packages] [Bug 1245473] Re: Binding ctrl+shift, alt+shift, etc for switching keyboard layout makes shortcuts with ctrl+shift, etc not working in any program

2018-02-22 Thread cfontes

I am running 17.10 with MATE, and this bug is still happening, I report it was 
working in 16.04 with Mate and after upgrading I have a working layout switcher 
between 2 languages but all Shift+Alt derived shortcuts specially the ones in 
IDEA are not working anymore 

 User rant 

Well I will add my complain,

This is one of those "I fell like switching back to windows" kind of
bug, the kind that make you stop before recommending ubuntu to your
friends and family, the one when people point it out to you, you simply
lower your head and nod.

This is super old and terrible for any shortcut user in a multi language
setup, which are most of developers I know of.

In 17.10 not even the Xorg recompile is working anymore, for some
magical reason in 16.04 this was fixed maybe by Dell(I have a dell
ubuntu machine) or someone else, as soon as I updated to 17.10 it
appeared again.

It's really infuriating to start my IDE everyday with this on.

In my case, layout switcher for keyboards is working ( probably because
of some of config from 16.04) but all Shift+Alt derived shortcuts
specially the ones in IDEA are not. So no more fancy multi caret edit
for me, or fast renaming, or line switching I am basically missing some
of the  the good stuff IDEA provides and was payed for because of a 10
year old bug.

That disaster that was Unity was build and killed during the time bug
has been around.

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

Title:
  Binding ctrl+shift, alt+shift, etc for switching keyboard layout makes
  shortcuts with ctrl+shift, etc not working in any program

Status in GNOME Settings Daemon:
  Fix Released
Status in GNOME Shell:
  Won't Fix
Status in Unity:
  Confirmed
Status in X.Org X server:
  Confirmed
Status in firefox package in Ubuntu:
  Confirmed
Status in gnome-settings-daemon package in Ubuntu:
  Triaged
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in gnome-terminal package in Ubuntu:
  Confirmed
Status in unity package in Ubuntu:
  Triaged
Status in gnome-settings-daemon package in ALT Linux:
  Unknown
Status in gnome-settings-daemon package in Debian:
  New
Status in gnome-settings-daemon package in Fedora:
  In Progress
Status in gnome-settings-daemon package in openSUSE:
  Confirmed

Bug description:
  Tried only with ctrl+shift, maybe behaves the same for other modifier
  key combinations when used as shortcut for switching layouts.

  - Set ctrl+shift as shortcut for switching keyboard layouts
  - Try to use ctrl+shift+v, ctrl+shift+c in Terminal -- it doesn't work 
(actually Terminal window loses focus when ctrl+shift is pressed, and layout is 
switched)

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

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: gnome-settings-daemon 3.8.5-0ubuntu11.1
  ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6
  Uname: Linux 3.11.0-13-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2.1
  Architecture: amd64
  Date: Mon Oct 28 16:40:02 2013
  InstallationDate: Installed on 2013-10-23 (5 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  MarkForUpload: True
  SourcePackage: gnome-settings-daemon
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1751005] Re: libreoffice cannot open a document not within $HOME

The error message about
~/.libreoffice/{3,4}/user/config/javasettings_Linux_*.xml is unrelated,
it is simply telling you libreoffice cannot find a JRE (but it will work
fine without it, for the most part).

What you're seeing is apparmor confinement finally working as intended. The 
package had been shipping apparmor profiles for some time, but they were not 
functional, and they have been fixed.
Those profiles allow reading/writing office documents in $HOME, /mnt and /media 
(that excludes /home2/).

Can you try running the following command in a terminal, and confirm
that this "fixes" your issue:

sudo apparmor_parser -R
/etc/apparmor.d/usr.lib.libreoffice.program.*

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

Title:
  libreoffice cannot open a document not within $HOME

Status in libreoffice package in Ubuntu:
  New

Bug description:
  Starting with today's update to LibreOffice 5.4.5.1 40m0(Build:1),
  files not within the user $HOME directory cannot be opened. This has
  nothing to do with ownership or permissions - the target document is
  owned by the user with full permissions. Moving the file to ~/Desktop
  allows it to be opened normally.

  Error message in popup window:
Access to /home2/mico/documents/personal/2018 lists.ods was denied.

  Error message when launched from terminal:
  $: localc "2018 lists.ods"
  javaldx: Could not find a Java Runtime Environment!
  Please ensure that a JVM and the package libreoffice-java-common is installed.
  If it is already installed then try removing 
~/.libreoffice/3/user/config/javasettings_Linux_*.xml
  Warning: failed to read path from javaldx

  The file mentioned in the error message does not exist.
  I removed the corresponding file under ~/.libreoffice/4/ but that makes no 
difference.

  This but started in Ubuntu 18.04 (alpha) around Feb. 15, and with
  today's update (Feb. 22) it appeared in Ubuntu 17.10.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: libreoffice-core 1:5.4.5-0ubuntu0.17.10.1
  ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13
  Uname: Linux 4.13.0-36-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Feb 22 09:35:49 2018
  InstallationDate: Installed on 2018-01-27 (25 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1713323] Re: HiDPI support partially broken after upgrade to Gnome 3.25, 3.26

2018-02-22 Thread Kostiantyn Rybnikov

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

Fresh Ubuntu 17.10 has the issue of showing Qt apps non-scaled. Should
we reopen the
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1717272 issue,
continue here, or make a new one? What's the way to go?

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

Title:
  HiDPI support partially broken after upgrade to Gnome 3.25, 3.26

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  After an upgrade this morning that took in the new version of this
  package, and a suite of gnome-session/gnome-settings packages, which
  may also be implicated, support for scaling on HiDPI screens seems to
  have partially failed. Partially.

  BTW I invoked the bug reporter with "ubuntu-bug ubuntu-session" but
  when I got to the launchpad page it had pre-filled "gnome-session".
  One presumes there's a reason for that so I've left it, especially as
  this does affect "GNOME" as well as "Ubuntu" sessions. But I do note a
  settings migrations utility in ubuntu-session which I wonder if it
  might be implicated. (TBH looking at it it's not obvious why, though
  it does reset scaling - that's not the problem, the problem is that it
  can't be set back to a combination that works.)

  Reminder all the stuff I'm reporting below as being wrongly-scaled was
  scaled correctly before the update that just took place. Enpass got a
  little help from having some QT env variables set, but that's it.

  Logging in under session "Ubuntu" (Wayland - on a different machine as
  this one being nvidia doesn't support it) or session "Ubuntu on Xorg"
  - also affects GNOME sessions:

  * The fonts in the top bar, and the menus and indicators accessible
  from there, are unscaled. The indicator icons *are* scaled correctly.

  * The fonts in the applications view are unscaled, but the icons and
  layout *are* scaled correctly.

  * Menu titlebar *text* is unscaled. close/minimize/maximize widgets
  *are* scaled correctly, as is the titlebar's size itself.

  * The mouse pointer is unscaled.

  * Non-Gnome apps, either QT or GTK (examples: enpass, nextcloud-
  client, hexchat, sublime text 3) are unscaled, or in some cases are a
  bit confused, with some elements correctly scaled, but again fonts are
  not.

  * Also on a personal note, Java 9 JavaFX apps are no longer scaled.
  (In Java 8 it was already broken; I was targeting Java 9 with my
  development partly *because* its HiDPI support was working in Linux.)
  FYI Java 9 JavaFX uses GTK3, Java 8 uses GTK2.

  ## What is working:

  * Gnome apps (eg: Terminal, Transmission, Settings, Tweaks, Nautilus,
  Gedit etc. etc.) are all fine. Although note those that use a "normal"
  titlebar (eg: Terminal) rather than an integrated one (eg: Nautilus)
  show small titlebar text as mentioned above

  * Google Chrome, Thunderbird, Firefox are fine (although the latter
  two aren't being updated for Artful yet, just sayin' ;-)

  ## What happens if I try to fix it:

  gsettings org.gnome.desktop.interface scaling-factor appears to no
  longer be operational. Changing its value from 0 (default), 1 and 2
  appears to have no effect on anything any more. It used to be setting
  it to 2 fixed the few things that weren't right by having it set to
  0... Correction, that *does* fix it for Java 9 JavaFX, it must be
  reading that setting directly. But nothing else reported as broken
  above is affected by changing this setting. Nor in fact does setting
  it to 1 cause gnome apps to be unscaled.

  gsettings org.gnome.desktop.interface cursor-size is working. I can
  set it to 48, double its normal size, to get back normal-sized cursors
  when the pointer is over newly-launched applications. But that's
  obviously a workaround.

  gsettings org.gnome.desktop.interface text-scaling-factor set to 2.0,
  also exposed in Gnome Tweaks, unsurprisingly makes text twice as
  large. That "fixes" it for the applications that are reported as being
  unscaled above, but it also doubles the size of text in gnome apps as
  well, so those are now far too large for the windows they're in.
  Google Chrome is unaffected by this, as is Java 9 JavaFX, but
  Thunderbird *is* affected.

  I noticed a new gsetting: com.ubuntu.user-interface scale-factor, but
  it seems to have a nonsense-value "@a{si} {}". I have no idea if this
  is anything in use or if it was an intended Unity 8 thing. I didn't
  try anything with it.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: ubuntu-session 3.25.90-0ubuntu2
  ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
  Uname: Linux 4.12.0-11-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.6-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Aug 27 13:03:53 2017
  Inst

[Desktop-packages] [Bug 1750741] Re: Memory leak in g_dbus_proxy_new_for_bus_sync()

2018-02-22 Thread Seyeong Kim

Hello ddstreet

yep, it is tricky..

In the beginning, I added only one line but build failed.

3 commits for building, only one line is related to memroy leak
directly.

I retried it and attaching build link on lp

Thanks

https://launchpad.net/~xtrusia/+archive/ubuntu/sf160627-glib/+build/14383194/+files
/buildlog_ubuntu-trusty-
amd64.glib2.0_2.40.2-0ubuntu1+sf160627v20180222.0_BUILDING.txt.gz

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

Title:
  Memory leak in g_dbus_proxy_new_for_bus_sync()

Status in glib2.0 package in Ubuntu:
  Fix Released
Status in glib2.0 source package in Trusty:
  New

Bug description:
  [Impact]

  This issue is found while debugging pacemaker lrmd memory leak

  glib2.0 gio function g_dbus_proxy_new_for_bus_sync has leak as [1]
  said

  this is affected to Trusty

  [Test Case]

  https://pastebin.ubuntu.com/p/fqK6Cx3SKK/
  you can check memory leak with this script

  [Regression]
  This patch is affected to library pkg. so related daemon should be restarted 
after patching. patch itself is very simple and old. it seems verified for few 
years.

  [Others]

  original commit

  
https://gitlab.gnome.org/GNOME/glib/commit/db641e32920ee8b553ab6f2d318aafa156e4390c

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

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

[Desktop-packages] [Bug 1751005] Re: libreoffice cannot open a document not within $HOME

olivier: i read your answer and is a bit confused. why does upgrading to
libreoffice 6 not suffer from this problem?

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

Title:
  libreoffice cannot open a document not within $HOME

Status in libreoffice package in Ubuntu:
  New

Bug description:
  Starting with today's update to LibreOffice 5.4.5.1 40m0(Build:1),
  files not within the user $HOME directory cannot be opened. This has
  nothing to do with ownership or permissions - the target document is
  owned by the user with full permissions. Moving the file to ~/Desktop
  allows it to be opened normally.

  Error message in popup window:
Access to /home2/mico/documents/personal/2018 lists.ods was denied.

  Error message when launched from terminal:
  $: localc "2018 lists.ods"
  javaldx: Could not find a Java Runtime Environment!
  Please ensure that a JVM and the package libreoffice-java-common is installed.
  If it is already installed then try removing 
~/.libreoffice/3/user/config/javasettings_Linux_*.xml
  Warning: failed to read path from javaldx

  The file mentioned in the error message does not exist.
  I removed the corresponding file under ~/.libreoffice/4/ but that makes no 
difference.

  This but started in Ubuntu 18.04 (alpha) around Feb. 15, and with
  today's update (Feb. 22) it appeared in Ubuntu 17.10.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: libreoffice-core 1:5.4.5-0ubuntu0.17.10.1
  ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13
  Uname: Linux 4.13.0-36-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Feb 22 09:35:49 2018
  InstallationDate: Installed on 2018-01-27 (25 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1751029] Re: gnome-shell crashed with signal 5

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

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 #1748450, 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/1751029/+attachment/5060249/+files/CoreDump.gz

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

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

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

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

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

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

** This bug has been marked a duplicate of bug 1748450
   gnome-shell crashed with SIGTRAP in _g_log_abort() from 
g_log_default_handler() from default_log_handler(message="Connection to 
xwayland lost") from g_logv() from g_log() from 

** 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-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1751029

Title:
  gnome-shell crashed with signal 5

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Crash after login.

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.26.2-0ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Wed Feb 21 18:21:55 2018
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   
  InstallationDate: Installed on 2018-01-12 (41 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180111)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   LANGUAGE=pt_BR:pt:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pt_BR.UTF-8
   SHELL=/bin/false
  Signal: 5
  SourcePackage: gnome-shell
  StacktraceTop:
   () at /usr/lib/x86_64-linux-gnu/libmutter-1.so.0
   _XIOError () at /usr/lib/x86_64-linux-gnu/libX11.so.6
   _XEventsQueued () at /usr/lib/x86_64-linux-gnu/libX11.so.6
   XPending () at /usr/lib/x86_64-linux-gnu/libX11.so.6
   () at /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
  Title: gnome-shell crashed with signal 5
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

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

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

[Desktop-packages] [Bug 1751005] Re: libreoffice cannot open a document not within $HOME

Jan, if you installed LO 6 from the PPA, it might not have all the
required fixes for the apparmor profiles. But the version in the archive
(currently in bionic-proposed) will have them.

Can you please confirm that the command I suggested in comment #3
resolves your issue (that's temporary until the next reboot).

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

Title:
  libreoffice cannot open a document not within $HOME

Status in libreoffice package in Ubuntu:
  New

Bug description:
  Starting with today's update to LibreOffice 5.4.5.1 40m0(Build:1),
  files not within the user $HOME directory cannot be opened. This has
  nothing to do with ownership or permissions - the target document is
  owned by the user with full permissions. Moving the file to ~/Desktop
  allows it to be opened normally.

  Error message in popup window:
Access to /home2/mico/documents/personal/2018 lists.ods was denied.

  Error message when launched from terminal:
  $: localc "2018 lists.ods"
  javaldx: Could not find a Java Runtime Environment!
  Please ensure that a JVM and the package libreoffice-java-common is installed.
  If it is already installed then try removing 
~/.libreoffice/3/user/config/javasettings_Linux_*.xml
  Warning: failed to read path from javaldx

  The file mentioned in the error message does not exist.
  I removed the corresponding file under ~/.libreoffice/4/ but that makes no 
difference.

  This but started in Ubuntu 18.04 (alpha) around Feb. 15, and with
  today's update (Feb. 22) it appeared in Ubuntu 17.10.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: libreoffice-core 1:5.4.5-0ubuntu0.17.10.1
  ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13
  Uname: Linux 4.13.0-36-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Feb 22 09:35:49 2018
  InstallationDate: Installed on 2018-01-27 (25 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1751005] Re: libreoffice cannot open a document not within $HOME

i have to downgrade libreoffice first i guess.have no
installation left with libreoffice 5 for the moment

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

Title:
  libreoffice cannot open a document not within $HOME

Status in libreoffice package in Ubuntu:
  New

Bug description:
  Starting with today's update to LibreOffice 5.4.5.1 40m0(Build:1),
  files not within the user $HOME directory cannot be opened. This has
  nothing to do with ownership or permissions - the target document is
  owned by the user with full permissions. Moving the file to ~/Desktop
  allows it to be opened normally.

  Error message in popup window:
Access to /home2/mico/documents/personal/2018 lists.ods was denied.

  Error message when launched from terminal:
  $: localc "2018 lists.ods"
  javaldx: Could not find a Java Runtime Environment!
  Please ensure that a JVM and the package libreoffice-java-common is installed.
  If it is already installed then try removing 
~/.libreoffice/3/user/config/javasettings_Linux_*.xml
  Warning: failed to read path from javaldx

  The file mentioned in the error message does not exist.
  I removed the corresponding file under ~/.libreoffice/4/ but that makes no 
difference.

  This but started in Ubuntu 18.04 (alpha) around Feb. 15, and with
  today's update (Feb. 22) it appeared in Ubuntu 17.10.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: libreoffice-core 1:5.4.5-0ubuntu0.17.10.1
  ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13
  Uname: Linux 4.13.0-36-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Feb 22 09:35:49 2018
  InstallationDate: Installed on 2018-01-27 (25 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1685064] Re: package libreoffice-style-galaxy 1:5.1.6~rc2-0ubuntu1~xenial1 failed to install/upgrade: package libreoffice-style-galaxy is already installed and configured

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

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

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

Title:
  package libreoffice-style-galaxy 1:5.1.6~rc2-0ubuntu1~xenial1 failed
  to install/upgrade: package libreoffice-style-galaxy is already
  installed and configured

Status in libreoffice package in Ubuntu:
  Confirmed

Bug description:
  please help

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libreoffice-style-galaxy 1:5.1.6~rc2-0ubuntu1~xenial1
  ProcVersionSignature: Ubuntu 4.8.0-46.49~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-46-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  AptdaemonVersion: 1.1.1+bzr982-0ubuntu14
  Architecture: amd64
  Date: Fri Apr 21 11:45:07 2017
  DuplicateSignature:
   package:libreoffice-style-galaxy:1:5.1.6~rc2-0ubuntu1~xenial1
   Processing triggers for dbus (1.10.6-1ubuntu3.3) ...
   dpkg: error processing package libreoffice-common (--configure):
package libreoffice-common is already installed and configured
  ErrorMessage: package libreoffice-style-galaxy is already installed and 
configured
  InstallationDate: Installed on 2017-04-20 (0 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.19
  SourcePackage: libreoffice
  Title: package libreoffice-style-galaxy 1:5.1.6~rc2-0ubuntu1~xenial1 failed 
to install/upgrade: package libreoffice-style-galaxy is already installed and 
configured
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1751039] [NEW] Search results in finch updated incorrectly

Public bug reported:

Finch doesn't clear the previous search results when they are updated in
real time.

Fixed upstream by #17238: https://developer.pidgin.im/ticket/17238

Please could you pull this fix into the packages, even if 2.13 isn't
released in time.

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

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

Title:
  Search results in finch updated incorrectly

Status in pidgin package in Ubuntu:
  New

Bug description:
  Finch doesn't clear the previous search results when they are updated
  in real time.

  Fixed upstream by #17238: https://developer.pidgin.im/ticket/17238

  Please could you pull this fix into the packages, even if 2.13 isn't
  released in time.

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

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

[Desktop-packages] [Bug 1751037] [NEW] Mute status not updated

Public bug reported:

When I am on an audio call and the remote end mutes me, that is not
correctly displayed in the local UI. Fixed in Pidgin 2.13 by #17273:
https://developer.pidgin.im/ticket/17273

Please could you pull this fix into the packages, even if 2.13 isn't
released in time.

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

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

Title:
  Mute status not updated

Status in pidgin package in Ubuntu:
  New

Bug description:
  When I am on an audio call and the remote end mutes me, that is not
  correctly displayed in the local UI. Fixed in Pidgin 2.13 by #17273:
  https://developer.pidgin.im/ticket/17273

  Please could you pull this fix into the packages, even if 2.13 isn't
  released in time.

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

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

[Desktop-packages] [Bug 1751005] Re: libreoffice cannot open a document not within $HOME

okay. looks promising.

i did this:

sudo ppa-purge ppa:libreoffice/ppa. now libreoffice 5 installed again
and gives the error.

sudo apparmor_parser -R /etc/apparmor.d/usr.lib.libreoffice.program.*
libreoffice starts up and seems to be working..

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

Title:
  libreoffice cannot open a document not within $HOME

Status in libreoffice package in Ubuntu:
  New

Bug description:
  Starting with today's update to LibreOffice 5.4.5.1 40m0(Build:1),
  files not within the user $HOME directory cannot be opened. This has
  nothing to do with ownership or permissions - the target document is
  owned by the user with full permissions. Moving the file to ~/Desktop
  allows it to be opened normally.

  Error message in popup window:
Access to /home2/mico/documents/personal/2018 lists.ods was denied.

  Error message when launched from terminal:
  $: localc "2018 lists.ods"
  javaldx: Could not find a Java Runtime Environment!
  Please ensure that a JVM and the package libreoffice-java-common is installed.
  If it is already installed then try removing 
~/.libreoffice/3/user/config/javasettings_Linux_*.xml
  Warning: failed to read path from javaldx

  The file mentioned in the error message does not exist.
  I removed the corresponding file under ~/.libreoffice/4/ but that makes no 
difference.

  This but started in Ubuntu 18.04 (alpha) around Feb. 15, and with
  today's update (Feb. 22) it appeared in Ubuntu 17.10.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: libreoffice-core 1:5.4.5-0ubuntu0.17.10.1
  ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13
  Uname: Linux 4.13.0-36-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Feb 22 09:35:49 2018
  InstallationDate: Installed on 2018-01-27 (25 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1751038] [NEW] Labelled buttons missing from Pidgin search dialogs

Public bug reported:

Pidgin fails to display buttons with custom labels in search dialogs.

Fixed in 2.13 by #17188: https://developer.pidgin.im/ticket/17188
(by cherry-picking an existing fix from the master branch for #14821).

Please could you pull this fix into the packages, even if 2.13 isn't
released in time.

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

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

Title:
  Labelled buttons missing from Pidgin search dialogs

Status in pidgin package in Ubuntu:
  New

Bug description:
  Pidgin fails to display buttons with custom labels in search dialogs.

  Fixed in 2.13 by #17188: https://developer.pidgin.im/ticket/17188
  (by cherry-picking an existing fix from the master branch for #14821).

  Please could you pull this fix into the packages, even if 2.13 isn't
  released in time.

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

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

[Desktop-packages] [Bug 1751035] Re: gnome-shell crashed with signal 5 in g_log_default_handler()

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

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 #1748450, 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/1751035/+attachment/5060297/+files/CoreDump.gz

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

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

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

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

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

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

** This bug has been marked a duplicate of bug 1748450
   gnome-shell crashed with SIGTRAP in _g_log_abort() from 
g_log_default_handler() from default_log_handler(message="Connection to 
xwayland lost") from g_logv() from g_log() from 

** 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-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1751035

Title:
  gnome-shell crashed with signal 5 in g_log_default_handler()

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  i press SUPER button for open applications

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.26.2-0ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Wed Feb 21 23:36:06 2018
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   
  InstallationDate: Installed on 2018-02-21 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180221)
  ProcCmdline: /usr/bin/gnome-shell
  Signal: 5
  SourcePackage: gnome-shell
  StacktraceTop:
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_log_default_handler () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? ()
   g_logv () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_log () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: gnome-shell crashed with signal 5 in g_log_default_handler()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

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

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

[Desktop-packages] [Bug 1670933] Re: [PATCH] Accessibility partly broken due to X root window being kept from login session.

2018-02-22 Thread Sean Davis

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

** Changed in: lightdm-gtk-greeter (Ubuntu)
   Status: New => Fix Released

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

Title:
  [PATCH] Accessibility partly broken due to X root window being kept
  from login session.

Status in LightDM GTK+ Greeter:
  Fix Released
Status in lightdm-gtk-greeter package in Ubuntu:
  Fix Released
Status in unity-greeter package in Ubuntu:
  Confirmed

Bug description:
   affects lightdm

  Lightdm version 1.21.5, in 17.04. Some components of the Unity and
  Mate desktops are currently not accessible when logging in using
  lightdm. So far I've tested and reproduced this problem with both
  unity-greeter, and lightdm-gtk-greeter, so I suspect it is what I
  mentioned in the title, i.e the X root window is kept around.

  At-spi gets loaded in the greeter for use with Orca. At-spi ads a
  property atom, AT_SPI_BUS, to the root X window to allow software to
  be able to find the accessibility bus. If my understanding is correct,
  this root window is kept around for the user login session. What then
  happens is software either using Qt or Gtk loads its accessibility
  support code, which in turn looks for the AT_SPI_BUS property.
  Normally on session load, this property is not present, at which point
  the support code then connects to org.a11y.bus, which in turn via
  systemd loads the at-spi bus launcher and registry to respond to the
  bus activation/request. At-spi adds the AT_SPI_BUS property to the X
  root window at load.

  However the AT_SPI_BUS property is hanging around from the greeter
  session, which is confusing software. At-spi only then gets loaded
  from /etc/xdg/autostart/at-spi-dbus-bus.desktop by the mate or gnome
  session binaries, but this happens after unity-panel-service and mate-
  panel are loaded. As such they are inaccessible for the session, or
  until the user kills them and they get reloaded.

To manage notifications about this bug go to:
https://bugs.launchpad.net/lightdm-gtk-greeter/+bug/1670933/+subscriptions

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

[Desktop-packages] [Bug 1751005] Re: libreoffice cannot open a document not within $HOME

as you said: this is temporary. how do i make it permanent?

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

Title:
  libreoffice cannot open a document not within $HOME

Status in libreoffice package in Ubuntu:
  New

Bug description:
  Starting with today's update to LibreOffice 5.4.5.1 40m0(Build:1),
  files not within the user $HOME directory cannot be opened. This has
  nothing to do with ownership or permissions - the target document is
  owned by the user with full permissions. Moving the file to ~/Desktop
  allows it to be opened normally.

  Error message in popup window:
Access to /home2/mico/documents/personal/2018 lists.ods was denied.

  Error message when launched from terminal:
  $: localc "2018 lists.ods"
  javaldx: Could not find a Java Runtime Environment!
  Please ensure that a JVM and the package libreoffice-java-common is installed.
  If it is already installed then try removing 
~/.libreoffice/3/user/config/javasettings_Linux_*.xml
  Warning: failed to read path from javaldx

  The file mentioned in the error message does not exist.
  I removed the corresponding file under ~/.libreoffice/4/ but that makes no 
difference.

  This but started in Ubuntu 18.04 (alpha) around Feb. 15, and with
  today's update (Feb. 22) it appeared in Ubuntu 17.10.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: libreoffice-core 1:5.4.5-0ubuntu0.17.10.1
  ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13
  Uname: Linux 4.13.0-36-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Feb 22 09:35:49 2018
  InstallationDate: Installed on 2018-01-27 (25 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1750937] Re: 14.04 Kernel update on 2/21 breaks Nvidia drivers

2018-02-22 Thread reetp

Same here on a variety of machines

Nvidia 340.102 on Nvidia NVS 300

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

Title:
  14.04 Kernel update on 2/21 breaks Nvidia drivers

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  Running fine with nvidia-384 until this kernel update came along.
  When booted into the new kernel, got super low resolution and nvidia-
  settings was missing most of its functionality - could not change
  resolution.

  Rebooted into 4.4.0-112 kernel and all was well.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 4.4.0-112.135~14.04.1-generic 4.4.98
  Uname: Linux 4.4.0-112-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  384.111  Tue Dec 19 23:51:45 
PST 2017
   GCC version:  gcc version 4.8.4 (Ubuntu 4.8.4-2ubuntu1~14.04.3)
  ApportVersion: 2.14.1-0ubuntu3.27
  Architecture: amd64
  CurrentDesktop: LXDE
  Date: Wed Feb 21 19:23:39 2018
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.7, 4.4.0-112-generic, x86_64: installed
   bbswitch, 0.7, 4.4.0-116-generic, x86_64: installed
   nvidia-384, 384.111, 4.4.0-112-generic, x86_64: installed
   nvidia-384, 384.111, 4.4.0-116-generic, x86_64: installed
  GraphicsCard:
   NVIDIA Corporation Device [10de:1c82] (rev a1) (prog-if 00 [VGA controller])
 Subsystem: eVga.com. Corp. Device [3842:6253]
  InstallationDate: Installed on 2015-03-03 (1086 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  MachineType: ASUSTeK COMPUTER INC. M11AD
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-112-generic 
root=UUID=5a88d2a1-0a24-415b-adc2-28435b13248a ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/15/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0302
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: M11AD
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0302:bd08/15/2013:svnASUSTeKCOMPUTERINC.:pnM11AD:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnM11AD:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: M11AD
  dmi.product.version: System Version
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz 1:0.9.11.3+14.04.20160425-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.14.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri N/A
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Wed Feb 21 18:48:14 2018
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.18.3-1ubuntu2.3~trusty4

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

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

[Desktop-packages] [Bug 1751005] Re: libreoffice cannot open a document not within $HOME

think i understand now. i guess what the apparmor_parser command does is
to temporarily disable the profiles for libreoffice.

and disable it permanently does not sound like a good idea. i guess.

so: i guess the solution is to get a new version of libreoffice. right?

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

Title:
  libreoffice cannot open a document not within $HOME

Status in libreoffice package in Ubuntu:
  New

Bug description:
  Starting with today's update to LibreOffice 5.4.5.1 40m0(Build:1),
  files not within the user $HOME directory cannot be opened. This has
  nothing to do with ownership or permissions - the target document is
  owned by the user with full permissions. Moving the file to ~/Desktop
  allows it to be opened normally.

  Error message in popup window:
Access to /home2/mico/documents/personal/2018 lists.ods was denied.

  Error message when launched from terminal:
  $: localc "2018 lists.ods"
  javaldx: Could not find a Java Runtime Environment!
  Please ensure that a JVM and the package libreoffice-java-common is installed.
  If it is already installed then try removing 
~/.libreoffice/3/user/config/javasettings_Linux_*.xml
  Warning: failed to read path from javaldx

  The file mentioned in the error message does not exist.
  I removed the corresponding file under ~/.libreoffice/4/ but that makes no 
difference.

  This but started in Ubuntu 18.04 (alpha) around Feb. 15, and with
  today's update (Feb. 22) it appeared in Ubuntu 17.10.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: libreoffice-core 1:5.4.5-0ubuntu0.17.10.1
  ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13
  Uname: Linux 4.13.0-36-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Feb 22 09:35:49 2018
  InstallationDate: Installed on 2018-01-27 (25 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1751046] [NEW] Pidgin rewrites buddy icons on each startup

Public bug reported:

Every time Pidgin starts up, it rewrites all the buddy icon files for no
good reason.

Fixed in 2.13 by #17259: https://developer.pidgin.im/ticket/17259

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

** Description changed:

  Every time Pidgin starts up, it rewrites all the buddy icon files for no
  good reason.
  
- Fixed in 2.13 by #17259: https://developer.pidgin.im/ticket/17238
+ Fixed in 2.13 by #17259: https://developer.pidgin.im/ticket/17259

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

Title:
  Pidgin rewrites buddy icons on each startup

Status in pidgin package in Ubuntu:
  New

Bug description:
  Every time Pidgin starts up, it rewrites all the buddy icon files for
  no good reason.

  Fixed in 2.13 by #17259: https://developer.pidgin.im/ticket/17259

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

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

[Desktop-packages] [Bug 1751046] Re: Pidgin rewrites buddy icons on each startup

** Patch added: 
"0001-Do-not-rewrite-custom-buddy-icons-already-in-the-cac.patch"
   
https://bugs.launchpad.net/ubuntu/+source/pidgin/+bug/1751046/+attachment/5060328/+files/0001-Do-not-rewrite-custom-buddy-icons-already-in-the-cac.patch

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

Title:
  Pidgin rewrites buddy icons on each startup

Status in pidgin package in Ubuntu:
  New

Bug description:
  Every time Pidgin starts up, it rewrites all the buddy icon files for
  no good reason.

  Fixed in 2.13 by #17259: https://developer.pidgin.im/ticket/17259

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

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

[Desktop-packages] [Bug 1751039] Re: Search results in finch updated incorrectly

** Patch added: "0001-Fix-Finch-search-results-display-17238.patch"
   
https://bugs.launchpad.net/ubuntu/+source/pidgin/+bug/1751039/+attachment/5060327/+files/0001-Fix-Finch-search-results-display-17238.patch

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

Title:
  Search results in finch updated incorrectly

Status in pidgin package in Ubuntu:
  New

Bug description:
  Finch doesn't clear the previous search results when they are updated
  in real time.

  Fixed upstream by #17238: https://developer.pidgin.im/ticket/17238

  Please could you pull this fix into the packages, even if 2.13 isn't
  released in time.

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

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

[Desktop-packages] [Bug 1751038] Re: Labelled buttons missing from Pidgin search dialogs

** Patch added: 
"0001-Ensure-labelled-buttons-are-shown-for-search-results.patch"
   
https://bugs.launchpad.net/ubuntu/+source/pidgin/+bug/1751038/+attachment/5060326/+files/0001-Ensure-labelled-buttons-are-shown-for-search-results.patch

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

Title:
  Labelled buttons missing from Pidgin search dialogs

Status in pidgin package in Ubuntu:
  New

Bug description:
  Pidgin fails to display buttons with custom labels in search dialogs.

  Fixed in 2.13 by #17188: https://developer.pidgin.im/ticket/17188
  (by cherry-picking an existing fix from the master branch for #14821).

  Please could you pull this fix into the packages, even if 2.13 isn't
  released in time.

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

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

[Desktop-packages] [Bug 1751037] Re: Mute status not updated

** Patch added: 
"0001-Pidgin-Indicate-mute-unmute-status-when-changed-remo.patch"
   
https://bugs.launchpad.net/ubuntu/+source/pidgin/+bug/1751037/+attachment/5060325/+files/0001-Pidgin-Indicate-mute-unmute-status-when-changed-remo.patch

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

Title:
  Mute status not updated

Status in pidgin package in Ubuntu:
  New

Bug description:
  When I am on an audio call and the remote end mutes me, that is not
  correctly displayed in the local UI. Fixed in Pidgin 2.13 by #17273:
  https://developer.pidgin.im/ticket/17273

  Please could you pull this fix into the packages, even if 2.13 isn't
  released in time.

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

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

[Desktop-packages] [Bug 1751005] Re: libreoffice cannot open a document not within $HOME

No, that's not a solution, because as soon as libreoffice 6 is in the
ubuntu archive it will have the working apparmor profiles. If you want
to disable the apparmor profiles permanently, you can do the following:

sudo ln -s /etc/apparmor.d/usr.lib.libreoffice.program.*
/etc/apparmor.d/disable/

I'm going to mark this bug invalid as the apparmor profiles are working
as expected, but your setup (with a /home2 mount point) is rather
exotic.

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

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

Title:
  libreoffice cannot open a document not within $HOME

Status in libreoffice package in Ubuntu:
  Invalid

Bug description:
  Starting with today's update to LibreOffice 5.4.5.1 40m0(Build:1),
  files not within the user $HOME directory cannot be opened. This has
  nothing to do with ownership or permissions - the target document is
  owned by the user with full permissions. Moving the file to ~/Desktop
  allows it to be opened normally.

  Error message in popup window:
Access to /home2/mico/documents/personal/2018 lists.ods was denied.

  Error message when launched from terminal:
  $: localc "2018 lists.ods"
  javaldx: Could not find a Java Runtime Environment!
  Please ensure that a JVM and the package libreoffice-java-common is installed.
  If it is already installed then try removing 
~/.libreoffice/3/user/config/javasettings_Linux_*.xml
  Warning: failed to read path from javaldx

  The file mentioned in the error message does not exist.
  I removed the corresponding file under ~/.libreoffice/4/ but that makes no 
difference.

  This but started in Ubuntu 18.04 (alpha) around Feb. 15, and with
  today's update (Feb. 22) it appeared in Ubuntu 17.10.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: libreoffice-core 1:5.4.5-0ubuntu0.17.10.1
  ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13
  Uname: Linux 4.13.0-36-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Feb 22 09:35:49 2018
  InstallationDate: Installed on 2018-01-27 (25 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1751005] Re: libreoffice cannot open a document not within $HOME

2018-02-22 Thread Nick Butlin

Hi, I have the same issue - with a relatively new vanilla install of
17.10 - the last upgrade broke the ability to load the file with the
same permission denied

disabling the apparmor profile fixed the issue

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

Title:
  libreoffice cannot open a document not within $HOME

Status in libreoffice package in Ubuntu:
  Invalid

Bug description:
  Starting with today's update to LibreOffice 5.4.5.1 40m0(Build:1),
  files not within the user $HOME directory cannot be opened. This has
  nothing to do with ownership or permissions - the target document is
  owned by the user with full permissions. Moving the file to ~/Desktop
  allows it to be opened normally.

  Error message in popup window:
Access to /home2/mico/documents/personal/2018 lists.ods was denied.

  Error message when launched from terminal:
  $: localc "2018 lists.ods"
  javaldx: Could not find a Java Runtime Environment!
  Please ensure that a JVM and the package libreoffice-java-common is installed.
  If it is already installed then try removing 
~/.libreoffice/3/user/config/javasettings_Linux_*.xml
  Warning: failed to read path from javaldx

  The file mentioned in the error message does not exist.
  I removed the corresponding file under ~/.libreoffice/4/ but that makes no 
difference.

  This but started in Ubuntu 18.04 (alpha) around Feb. 15, and with
  today's update (Feb. 22) it appeared in Ubuntu 17.10.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: libreoffice-core 1:5.4.5-0ubuntu0.17.10.1
  ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13
  Uname: Linux 4.13.0-36-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Feb 22 09:35:49 2018
  InstallationDate: Installed on 2018-01-27 (25 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1751005] Re: libreoffice cannot open a document not within $HOME

setup is actually like this:

user data is on an extra disk. that disk is mounted in fstab

UUID=7707da2d-a878-40db-9311-f53ed74c821f /export ext4 defaults 0 1

then soft links for /home/janw to /export/home/janw is done.

yes that is not standard i know..

but it makes reinstallations of OS much easier..with user data
intact

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

Title:
  libreoffice cannot open a document not within $HOME

Status in libreoffice package in Ubuntu:
  Invalid

Bug description:
  Starting with today's update to LibreOffice 5.4.5.1 40m0(Build:1),
  files not within the user $HOME directory cannot be opened. This has
  nothing to do with ownership or permissions - the target document is
  owned by the user with full permissions. Moving the file to ~/Desktop
  allows it to be opened normally.

  Error message in popup window:
Access to /home2/mico/documents/personal/2018 lists.ods was denied.

  Error message when launched from terminal:
  $: localc "2018 lists.ods"
  javaldx: Could not find a Java Runtime Environment!
  Please ensure that a JVM and the package libreoffice-java-common is installed.
  If it is already installed then try removing 
~/.libreoffice/3/user/config/javasettings_Linux_*.xml
  Warning: failed to read path from javaldx

  The file mentioned in the error message does not exist.
  I removed the corresponding file under ~/.libreoffice/4/ but that makes no 
difference.

  This but started in Ubuntu 18.04 (alpha) around Feb. 15, and with
  today's update (Feb. 22) it appeared in Ubuntu 17.10.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: libreoffice-core 1:5.4.5-0ubuntu0.17.10.1
  ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13
  Uname: Linux 4.13.0-36-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Feb 22 09:35:49 2018
  InstallationDate: Installed on 2018-01-27 (25 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1750938] Re: Noto Chinese fonts won't print in Libreoffice

2018-02-22 Thread Gunnar Hjalmarsson

Thanks for head up, Ping-Wu.

** Changed in: ubuntukylin
   Status: New => Invalid

** Changed in: fonts-noto-cjk (Ubuntu)
   Status: New => Invalid

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

Title:
  Noto Chinese fonts won't print in Libreoffice

Status in Ubuntu Kylin:
  Invalid
Status in fonts-noto-cjk package in Ubuntu:
  Invalid

Bug description:
  LibreOffice won't print or export to pdf when document contains Noto
  fonts (both sans and serif).  Change to Source/Adobe (identical
  glyphs) solves the problem.  Also there is no problem in Fedora, which
  uses Source/Adobe cjk fonts. Ubuntu uses Noto, should switch to
  Source/Adobe.  This should be easily done.  See:

  https://www.libreofficechina.org/forum.php?mod=viewthread&tid=1928#lastpost

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

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

[Desktop-packages] [Bug 1734545] Re: Translations not updated from upstream

2018-02-22 Thread Gunnar Hjalmarsson

Seems not to have helped. Nothing new in the translation import queue.

** Changed in: gnome-sudoku (Ubuntu)
   Status: Fix Released => Confirmed

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

Title:
  Translations not updated from upstream

Status in gnome-sudoku package in Ubuntu:
  Confirmed

Bug description:
  The Danish translation of gnome-sudoku lacks many strings as it has
  not been synchronized with upstream for years:

  https://translations.launchpad.net/ubuntu/+source/gnome-sudoku

  Meanwhile gnome-sudoku is and has always been completely translated
  upstream.  Indeed it has been fully translated for every release of
  GNOME ever since it forked out of gnome-games.  Take for example
  current master:

  https://l10n.gnome.org/vertimus/gnome-sudoku/master/po/da

  It seems there are rather grave problems with translation imports in
  Launchpad.  I reported a similar issue recently for util-linux:

  https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1730793

  Who knows how many other packages are affected, and in what languages.
  I think Launchpad translations should be disabled entirely for all
  source packages - the translations belong upstream, with the project.

  Thanks to scootergrisen for making me aware of this problem.

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

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

[Desktop-packages] [Bug 1751005] Re: libreoffice cannot open a document not within $HOME

@Jan: if you mount your external disk under /mnt or /media (and change
your symlinks to point there), that should allow you to use libreoffice
confined, which IMHO is better than permanently disabling the apparmor
profiles.

@Nick: the files you're attempting to open are neither in your home
directory, nor under /mnt or /media, right?

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

Title:
  libreoffice cannot open a document not within $HOME

Status in libreoffice package in Ubuntu:
  Invalid

Bug description:
  Starting with today's update to LibreOffice 5.4.5.1 40m0(Build:1),
  files not within the user $HOME directory cannot be opened. This has
  nothing to do with ownership or permissions - the target document is
  owned by the user with full permissions. Moving the file to ~/Desktop
  allows it to be opened normally.

  Error message in popup window:
Access to /home2/mico/documents/personal/2018 lists.ods was denied.

  Error message when launched from terminal:
  $: localc "2018 lists.ods"
  javaldx: Could not find a Java Runtime Environment!
  Please ensure that a JVM and the package libreoffice-java-common is installed.
  If it is already installed then try removing 
~/.libreoffice/3/user/config/javasettings_Linux_*.xml
  Warning: failed to read path from javaldx

  The file mentioned in the error message does not exist.
  I removed the corresponding file under ~/.libreoffice/4/ but that makes no 
difference.

  This but started in Ubuntu 18.04 (alpha) around Feb. 15, and with
  today's update (Feb. 22) it appeared in Ubuntu 17.10.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: libreoffice-core 1:5.4.5-0ubuntu0.17.10.1
  ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13
  Uname: Linux 4.13.0-36-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Feb 22 09:35:49 2018
  InstallationDate: Installed on 2018-01-27 (25 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1685064] Re: package libreoffice-style-galaxy 1:5.1.6~rc2-0ubuntu1~xenial1 failed to install/upgrade: package libreoffice-style-galaxy is already installed and configured

2018-02-22 Thread dino99

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

** Package changed: libreoffice (Ubuntu) => dpkg (Ubuntu)

** This bug has been marked a duplicate of bug 545790
   package PACKAGE failed to install/upgrade: error writing to '': Success

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

Title:
  package libreoffice-style-galaxy 1:5.1.6~rc2-0ubuntu1~xenial1 failed
  to install/upgrade: package libreoffice-style-galaxy is already
  installed and configured

Status in dpkg package in Ubuntu:
  Confirmed

Bug description:
  please help

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libreoffice-style-galaxy 1:5.1.6~rc2-0ubuntu1~xenial1
  ProcVersionSignature: Ubuntu 4.8.0-46.49~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-46-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  AptdaemonVersion: 1.1.1+bzr982-0ubuntu14
  Architecture: amd64
  Date: Fri Apr 21 11:45:07 2017
  DuplicateSignature:
   package:libreoffice-style-galaxy:1:5.1.6~rc2-0ubuntu1~xenial1
   Processing triggers for dbus (1.10.6-1ubuntu3.3) ...
   dpkg: error processing package libreoffice-common (--configure):
package libreoffice-common is already installed and configured
  ErrorMessage: package libreoffice-style-galaxy is already installed and 
configured
  InstallationDate: Installed on 2017-04-20 (0 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.19
  SourcePackage: libreoffice
  Title: package libreoffice-style-galaxy 1:5.1.6~rc2-0ubuntu1~xenial1 failed 
to install/upgrade: package libreoffice-style-galaxy is already installed and 
configured
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1751068] [NEW] My Intel HD driver became VMvare driver after today`s update

2018-02-22 Thread Виктор Бутко

Public bug reported:

tamer@tamer-desktop:~$ lspci | grep -E "VGA|3D"
00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v3/4th Gen 
Core Processor Integrated Graphics Controller (rev 06)

tamer@tamer-desktop:~$ glxinfo -B 
name of display: :0
display: :0  screen: 0
direct rendering: Yes
Extended renderer info (GLX_MESA_query_renderer):
Vendor: VMware, Inc. (0x)
Device: llvmpipe (LLVM 5.0, 256 bits) (0x)
Version: 17.3.3
Accelerated: no
Video memory: 7390MB
Unified memory: no
Preferred profile: core (0x1)
Max core profile version: 3.3
Max compat profile version: 3.0
Max GLES1 profile version: 1.1
Max GLES[23] profile version: 3.0
OpenGL vendor string: VMware, Inc.
OpenGL renderer string: llvmpipe (LLVM 5.0, 256 bits)
OpenGL core profile version string: 3.3 (Core Profile) Mesa 17.3.3
OpenGL core profile shading language version string: 3.30
OpenGL core profile context flags: (none)
OpenGL core profile profile mask: core profile

OpenGL version string: 3.0 Mesa 17.3.3
OpenGL shading language version string: 1.30
OpenGL context flags: (none)

OpenGL ES profile version string: OpenGL ES 3.0 Mesa 17.3.3
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.00

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: libglu1-mesa 9.0.0-2.1build1
ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
Uname: Linux 4.13.0-32-generic x86_64
ApportVersion: 2.20.8-0ubuntu10
Architecture: amd64
CurrentDesktop: KDE
Date: Thu Feb 22 15:53:29 2018
InstallationDate: Installed on 2018-02-22 (0 days ago)
InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180206)
SourcePackage: libglu
UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  My Intel HD driver became VMvare driver after today`s update

Status in libglu package in Ubuntu:
  New

Bug description:
  tamer@tamer-desktop:~$ lspci | grep -E "VGA|3D"
  00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v3/4th Gen 
Core Processor Integrated Graphics Controller (rev 06)

  tamer@tamer-desktop:~$ glxinfo -B 
  name of display: :0
  display: :0  screen: 0
  direct rendering: Yes
  Extended renderer info (GLX_MESA_query_renderer):
  Vendor: VMware, Inc. (0x)
  Device: llvmpipe (LLVM 5.0, 256 bits) (0x)
  Version: 17.3.3
  Accelerated: no
  Video memory: 7390MB
  Unified memory: no
  Preferred profile: core (0x1)
  Max core profile version: 3.3
  Max compat profile version: 3.0
  Max GLES1 profile version: 1.1
  Max GLES[23] profile version: 3.0
  OpenGL vendor string: VMware, Inc.
  OpenGL renderer string: llvmpipe (LLVM 5.0, 256 bits)
  OpenGL core profile version string: 3.3 (Core Profile) Mesa 17.3.3
  OpenGL core profile shading language version string: 3.30
  OpenGL core profile context flags: (none)
  OpenGL core profile profile mask: core profile

  OpenGL version string: 3.0 Mesa 17.3.3
  OpenGL shading language version string: 1.30
  OpenGL context flags: (none)

  OpenGL ES profile version string: OpenGL ES 3.0 Mesa 17.3.3
  OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.00

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libglu1-mesa 9.0.0-2.1build1
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Thu Feb 22 15:53:29 2018
  InstallationDate: Installed on 2018-02-22 (0 days ago)
  InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180206)
  SourcePackage: libglu
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1750335] Re: LO 6.0 autopkgtest failures (uicheck: test_text_direction)

Patch:
https://git.launchpad.net/~libreoffice/ubuntu/+source/libreoffice/commit/?id=2c5e5ec91a12443806384aecd2abf9933c421356

** Changed in: libreoffice (Ubuntu)
 Assignee: Olivier Tilloy (osomon) => Rico Tzschichholz (ricotz)

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

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

Title:
  LO 6.0 autopkgtest failures (uicheck: test_text_direction)

Status in libreoffice package in Ubuntu:
  Fix Committed

Bug description:
  autopkgtests for libreoffice 6.0.1-0ubuntu1 (currently in bionic-
  proposed) are consistently failing:

  ==
  ERROR: test_text_direction (pageDialog.WriterPageDialog)
  --
  Traceback (most recent call last):
File "/tmp/autopkgtest.zEJ7dp/build.U4P/src/uitest/uitest/framework.py", 
line 46, in tearDown
  self.connection.tearDown()
File 
"/tmp/autopkgtest.zEJ7dp/build.U4P/src/uitest/libreoffice/connection.py", line 
192, in tearDown
  self.connection.tearDown()
File 
"/tmp/autopkgtest.zEJ7dp/build.U4P/src/uitest/libreoffice/connection.py", line 
152, in tearDown
  raise Exception("Exit status indicates failure: " + str(ret))
  Exception: Exit status indicates failure: 1

  ==
  FAIL: test_text_direction (pageDialog.WriterPageDialog) (i=1)
  --
  Traceback (most recent call last):
File 
"/tmp/autopkgtest.zEJ7dp/build.U4P/src/uitest/writer_tests/pageDialog.py", line 
220, in test_text_direction
  get_state_as_dict(xTextDirectionList)["SelectEntryText"], 
lTextDirection[i])
  AssertionError: 'Left-to-right (horizontal)' != 'Right-to-left (horizontal)'
  - Left-to-right (horizontal)
  + Right-to-left (horizontal)

  
  ==
  FAIL: test_text_direction (pageDialog.WriterPageDialog) (i=2)
  --
  Traceback (most recent call last):
File 
"/tmp/autopkgtest.zEJ7dp/build.U4P/src/uitest/writer_tests/pageDialog.py", line 
220, in test_text_direction
  get_state_as_dict(xTextDirectionList)["SelectEntryText"], 
lTextDirection[i])
  AssertionError: 'Left-to-right (horizontal)' != 'Right-to-left (vertical)'
  - Left-to-right (horizontal)
  + Right-to-left (vertical)

  
  ==
  FAIL: test_text_direction (pageDialog.WriterPageDialog) (i=3)
  --
  Traceback (most recent call last):
File 
"/tmp/autopkgtest.zEJ7dp/build.U4P/src/uitest/writer_tests/pageDialog.py", line 
220, in test_text_direction
  get_state_as_dict(xTextDirectionList)["SelectEntryText"], 
lTextDirection[i])
  AssertionError: 'Left-to-right (horizontal)' != 'Left-to-right (vertical)'
  - Left-to-right (horizontal)
  ?^^  
  + Left-to-right (vertical)
  ?^^ + ^

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

-- 
Mailing list: https://launchpad.net/~desktop-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

2018-02-22 Thread Johan Marius Wesselink

Tested the scilab 5.5.2 for ubuntu which works great. 
However, I did not test it before applying the jogl2 patch :-o.  

Had a look at the source and it seems that the Ubuntu version is patched to use 
the
generic version of jogl2. 

I would like to try and get this patch integrated in the Scilab source tree. 
Probably a difficult and slow process.

-- 
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:
  Fix Released
Status in mesa package in Ubuntu:
  Invalid
Status in scilab package in Ubuntu:
  Invalid
Status in libjogl2-java source package in Xenial:
  Fix Committed
Status in mesa source package in Xenial:
  Invalid
Status in scilab source package in Xenial:
  Invalid
Status in libjogl2-java source package in Artful:
  Fix Committed
Status in mesa source package in Artful:
  Invalid
Status in scilab source package in Artful:
  Invalid
Status in scilab package in Debian:
  Fix Released

Bug description:
  [Impact]

  Software that use libjogl2-java (Scilab, Matlab,...) fail to run,
  because Mesa dropped 'Gallium' from the renderer string.

  [Test case]
  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.

  [Regression potential]
  The fix is a simple oneliner that allows libjogl2-java to detect Mesa with 
both new and original version of Mesa.

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

2018-02-22 Thread Timo Aaltonen

sounds like artful is verified, same for xenial would be great

** Tags removed: verification-needed-artful
** Tags added: verification-done-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:
  Confirmed
Status in libjogl2-java package in Ubuntu:
  Fix Released
Status in mesa package in Ubuntu:
  Invalid
Status in scilab package in Ubuntu:
  Invalid
Status in libjogl2-java source package in Xenial:
  Fix Committed
Status in mesa source package in Xenial:
  Invalid
Status in scilab source package in Xenial:
  Invalid
Status in libjogl2-java source package in Artful:
  Fix Committed
Status in mesa source package in Artful:
  Invalid
Status in scilab source package in Artful:
  Invalid
Status in scilab package in Debian:
  Fix Released

Bug description:
  [Impact]

  Software that use libjogl2-java (Scilab, Matlab,...) fail to run,
  because Mesa dropped 'Gallium' from the renderer string.

  [Test case]
  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.

  [Regression potential]
  The fix is a simple oneliner that allows libjogl2-java to detect Mesa with 
both new and original version of Mesa.

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 1644662] Re: Icons missing when appearance setting is "high contrast"

** Branch linked: lp:~ubuntu-branches/debian/sid/gnome-themes-extra/sid

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

Title:
  Icons missing when appearance setting is "high contrast"

Status in gnome-themes-standard package in Ubuntu:
  Fix Released
Status in gnome-themes-standard source package in Xenial:
  Fix Committed
Status in gnome-themes-standard source package in Artful:
  Fix Committed

Bug description:
  [Impact]

   * Switching to HighContrast theme in System Settings/Appearance results in 
missing icons for some of the panels in System Settings.
   * Only Xenial is affected of the currently supported releases.
   * Current development release is not affected.

  [Test Case]

   * Open System Settings, select Appearance.
   * Choose the "High Contrast" theme.
   * Go back by selecting "All Settings".

  Expected result: there are icons to all items in the Settings window.
  Actual result: some items are missing icons.

  [Regression Potential]

   * There might be different icons used in some places depending on the
  fact that for Xenial HighContrast used Adwaita themes. Possibly icons
  may be missing in different places.

  [Other Info]
   * For some reason Trusty was using HighContrast icons and the change was 
made somewhere in between Trusty - Xenial.
   * Original bug description:

  To reproduce this:

  Open System Settings.

  Click Appearance

  Theme: High Contrast.

  Click All Settings tab:

  Many icons are missing.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: unity-control-center 15.04.0+16.04.20160705-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24
  Uname: Linux 4.4.0-47-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Nov 24 14:45:30 2016
  ExecutablePath: /usr/bin/unity-control-center
  InstallationDate: Installed on 2015-06-06 (537 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  ProcEnviron:
   PATH=(custom, user)
   SHELL=/bin/bash
   LANG=en_CA.UTF-8
   LANGUAGE=en_CA:en
   XDG_RUNTIME_DIR=
  SourcePackage: unity-control-center
  UpgradeStatus: Upgraded to xenial on 2016-08-28 (88 days ago)

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

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

[Desktop-packages] [Bug 1751068] Re: My Intel HD driver became VMvare driver after today`s update

2018-02-22 Thread Виктор Бутко

I repeated this bug by installing the system from scratch and updating
all the proposed packages

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

Title:
  My Intel HD driver became VMvare driver after today`s update

Status in libglu package in Ubuntu:
  New

Bug description:
  tamer@tamer-desktop:~$ lspci | grep -E "VGA|3D"
  00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v3/4th Gen 
Core Processor Integrated Graphics Controller (rev 06)

  tamer@tamer-desktop:~$ glxinfo -B 
  name of display: :0
  display: :0  screen: 0
  direct rendering: Yes
  Extended renderer info (GLX_MESA_query_renderer):
  Vendor: VMware, Inc. (0x)
  Device: llvmpipe (LLVM 5.0, 256 bits) (0x)
  Version: 17.3.3
  Accelerated: no
  Video memory: 7390MB
  Unified memory: no
  Preferred profile: core (0x1)
  Max core profile version: 3.3
  Max compat profile version: 3.0
  Max GLES1 profile version: 1.1
  Max GLES[23] profile version: 3.0
  OpenGL vendor string: VMware, Inc.
  OpenGL renderer string: llvmpipe (LLVM 5.0, 256 bits)
  OpenGL core profile version string: 3.3 (Core Profile) Mesa 17.3.3
  OpenGL core profile shading language version string: 3.30
  OpenGL core profile context flags: (none)
  OpenGL core profile profile mask: core profile

  OpenGL version string: 3.0 Mesa 17.3.3
  OpenGL shading language version string: 1.30
  OpenGL context flags: (none)

  OpenGL ES profile version string: OpenGL ES 3.0 Mesa 17.3.3
  OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.00

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libglu1-mesa 9.0.0-2.1build1
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Thu Feb 22 15:53:29 2018
  InstallationDate: Installed on 2018-02-22 (0 days ago)
  InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180206)
  SourcePackage: libglu
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1751076] [NEW] Xorg freeze when use mpv or cheese.

2018-02-22 Thread Ven

Public bug reported:

I have my new laptop, Lenovo 720s-13ARR shipped with the latest Ryzen 5 2500U, 
installed Ubuntu 17.10, it seems everything works except Wifi and GPU. After 
changing the wifi card with Intel 8265 and manually upgrading kernel with 
M-bab's build from 'https://github.com/M-Bab/linux-kernel-amdgpu-binaries'. 
Wifi and Gpu are working. But if I use mpv playing a video, when I try to 
resume the window from fullscreen, the screen freezes. Same thing happens when 
I use cheese, the camera app. Nothing I can do except a hard poweroff. After 
suffering that couple of times, I started to look for solutions from Internet. 
There are many error messages I can see if I use 'dmesg -l err' in the 
terminal. I cannot solve most of them, only use pci=noaer in the grub to 
suppress the "PCIe bus error", which keep increasing my "/var/log/kern.log" 
file size hundreds MB per hour before.
One more thing, if I start a reboot, the laptop might have a random hang on 
ubuntu logo screen. To avoid this, I have to poweroff first, then press power 
button to implement a 'reboot'. No idea for me in which part problem should be 
responsible for these failures.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: xorg 1:7.7+19ubuntu3
ProcVersionSignature:
 
Uname: Linux 4.15.4+ x86_64
ApportVersion: 2.20.7-0ubuntu3.7
Architecture: amd64
CompositorRunning: None
CurrentDesktop: ubuntu-communitheme:ubuntu:GNOME
Date: Thu Feb 22 21:53:01 2018
DistUpgraded: Fresh install
DistroCodename: artful
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GpuHangFrequency: I don't know
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Device [1002:15dd] (rev c4) (prog-if 00 
[VGA controller])
   Subsystem: Lenovo Device [17aa:380c]
InstallationDate: Installed on 2018-01-30 (22 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
MachineType: LENOVO 81BR
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.4+ 
root=UUID=399cfaf6-9c73-4786-8ef5-bd331d20aadc ro pci=noaer 
ivrs_ioapic[4]=00:14.0 ivrs_ioapic[5]=00:00.1 quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/19/2017
dmi.bios.vendor: LENOVO
dmi.bios.version: 6KCN28WW
dmi.board.asset.tag: NO Asset Tag
dmi.board.name: LNVNB161216
dmi.board.vendor: LENOVO
dmi.board.version: SDK0L77769 WIN
dmi.chassis.asset.tag: NO Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Lenovo ideapad 720S-13ARR
dmi.modalias: 
dmi:bvnLENOVO:bvr6KCN28WW:bd12/19/2017:svnLENOVO:pn81BR:pvrLenovoideapad720S-13ARR:rvnLENOVO:rnLNVNB161216:rvrSDK0L77769WIN:cvnLENOVO:ct10:cvrLenovoideapad720S-13ARR:
dmi.product.family: ideapad 720S-13ARR
dmi.product.name: 81BR
dmi.product.version: Lenovo ideapad 720S-13ARR
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.85-4~a~padoka0
version.libgl1-mesa-dri: libgl1-mesa-dri 1:17.3.2-0~a~padoka0
version.libgl1-mesa-glx: libgl1-mesa-glx 1:17.3.2-0~a~padoka0
version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
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

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


** Tags: amd64 apport-bug artful freeze third-party-packages ubuntu

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

Title:
  Xorg freeze when use mpv or cheese.

Status in xorg package in Ubuntu:
  New

Bug description:
  I have my new laptop, Lenovo 720s-13ARR shipped with the latest Ryzen 5 
2500U, installed Ubuntu 17.10, it seems everything works except Wifi and GPU. 
After changing the wifi card with Intel 8265 and manually upgrading kernel with 
M-bab's build from 'https://github.com/M-Bab/linux-kernel-amdgpu-binaries'. 
Wifi and Gpu are working. But if I use mpv playing a video, when I try to 
resume the window from fullscreen, the screen freezes. Same thing happens when 
I use cheese, the camera app. Nothing I can do except a hard poweroff. After 
suffering that couple of times, I started to look for solutions from Internet. 
There are many error messages I can see if I use 'dmesg -l err' in the 
terminal. I cannot solve most of them, only use pci=noaer in the grub to 
suppress the "PCIe bus error", which keep increasing my "/var/log/kern.log" 
file size hundreds MB per hour before.
  One more thing, if I start a reboot, the laptop might have a random hang on 
ubuntu logo screen. To avoid this, I have to poweroff first, then press power 
button to implement a 'reboot'. No idea for me in which part problem should be 
responsible for these failures.

[Desktop-packages] [Bug 1751075] [NEW] Xorg freeze when use mpv or cheese.

2018-02-22 Thread Ven

Public bug reported:

I have my new laptop, Lenovo 720s-13ARR shipped with the latest Ryzen 5 2500U, 
installed Ubuntu 17.10, it seems everything works except Wifi and GPU. After 
changing the wifi card with Intel 8265 and manually upgrading kernel with 
M-bab's build from 'https://github.com/M-Bab/linux-kernel-amdgpu-binaries'. 
Wifi and Gpu are working. But if I use mpv playing a video, when I try to 
resume the window from fullscreen, the screen freezes. Same thing happens when 
I use cheese, the camera app. Nothing I can do except a hard poweroff. After 
suffering that couple of times, I started to look for solutions from Internet. 
There are many error messages I can see if I use 'dmesg -l err' in the 
terminal. I cannot solve most of them, only use pci=noaer in the grub to 
suppress the "PCIe bus error", which keep increasing my "/var/log/kern.log" 
file size hundreds MB per hour before.
One more thing, if I start a reboot, the laptop might have a random hang on 
ubuntu logo screen. To avoid this, I have to poweroff first, then press power 
button to implement a 'reboot'. No idea for me in which part problem should be 
responsible for these failures.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: xorg 1:7.7+19ubuntu3
ProcVersionSignature:
 
Uname: Linux 4.15.4+ x86_64
ApportVersion: 2.20.7-0ubuntu3.7
Architecture: amd64
CompositorRunning: None
CurrentDesktop: ubuntu-communitheme:ubuntu:GNOME
Date: Thu Feb 22 21:53:01 2018
DistUpgraded: Fresh install
DistroCodename: artful
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GpuHangFrequency: I don't know
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Device [1002:15dd] (rev c4) (prog-if 00 
[VGA controller])
   Subsystem: Lenovo Device [17aa:380c]
InstallationDate: Installed on 2018-01-30 (22 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
MachineType: LENOVO 81BR
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.4+ 
root=UUID=399cfaf6-9c73-4786-8ef5-bd331d20aadc ro pci=noaer 
ivrs_ioapic[4]=00:14.0 ivrs_ioapic[5]=00:00.1 quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/19/2017
dmi.bios.vendor: LENOVO
dmi.bios.version: 6KCN28WW
dmi.board.asset.tag: NO Asset Tag
dmi.board.name: LNVNB161216
dmi.board.vendor: LENOVO
dmi.board.version: SDK0L77769 WIN
dmi.chassis.asset.tag: NO Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Lenovo ideapad 720S-13ARR
dmi.modalias: 
dmi:bvnLENOVO:bvr6KCN28WW:bd12/19/2017:svnLENOVO:pn81BR:pvrLenovoideapad720S-13ARR:rvnLENOVO:rnLNVNB161216:rvrSDK0L77769WIN:cvnLENOVO:ct10:cvrLenovoideapad720S-13ARR:
dmi.product.family: ideapad 720S-13ARR
dmi.product.name: 81BR
dmi.product.version: Lenovo ideapad 720S-13ARR
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.85-4~a~padoka0
version.libgl1-mesa-dri: libgl1-mesa-dri 1:17.3.2-0~a~padoka0
version.libgl1-mesa-glx: libgl1-mesa-glx 1:17.3.2-0~a~padoka0
version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
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

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


** Tags: amd64 apport-bug artful freeze third-party-packages ubuntu

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

Title:
  Xorg freeze when use mpv or cheese.

Status in xorg package in Ubuntu:
  New

Bug description:
  I have my new laptop, Lenovo 720s-13ARR shipped with the latest Ryzen 5 
2500U, installed Ubuntu 17.10, it seems everything works except Wifi and GPU. 
After changing the wifi card with Intel 8265 and manually upgrading kernel with 
M-bab's build from 'https://github.com/M-Bab/linux-kernel-amdgpu-binaries'. 
Wifi and Gpu are working. But if I use mpv playing a video, when I try to 
resume the window from fullscreen, the screen freezes. Same thing happens when 
I use cheese, the camera app. Nothing I can do except a hard poweroff. After 
suffering that couple of times, I started to look for solutions from Internet. 
There are many error messages I can see if I use 'dmesg -l err' in the 
terminal. I cannot solve most of them, only use pci=noaer in the grub to 
suppress the "PCIe bus error", which keep increasing my "/var/log/kern.log" 
file size hundreds MB per hour before.
  One more thing, if I start a reboot, the laptop might have a random hang on 
ubuntu logo screen. To avoid this, I have to poweroff first, then press power 
button to implement a 'reboot'. No idea for me in which part problem should be 
responsible for these failures.

[Desktop-packages] [Bug 1734586] Re: Merge NetworkManager with Debian 1.10.0-1

** Also affects: python-dbusmock (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: python-dbusmock (Ubuntu)
   Importance: Undecided => High

** Changed in: python-dbusmock (Ubuntu)
   Status: New => In Progress

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

Title:
  Merge NetworkManager with Debian 1.10.0-1

Status in network-manager package in Ubuntu:
  Fix Committed
Status in python-dbusmock package in Ubuntu:
  In Progress

Bug description:
  Debian has packaged the latest major release of NetworkManager, 1.10.
  We should update to this version for Ubuntu 18.04 "bionic".

  I have prepared the merge at
  https://git.launchpad.net/network-manager?h=bionic

  The only thing missing is that this patch needs to be rebased or dropped:
  
https://git.launchpad.net/network-manager/tree/debian/patches/dns-manager-don-t-merge-split-DNS-search-domains.patch?h=bionic

  Otherwise, the build will fail:

  src/.libs/libNetworkManagerTest.a(src_libNetworkManager_la-nm-dns-manager.o):
  In function `merge_one_ip_config_data':
  ./src/dns/nm-dns-manager.c:417: undefined reference to
  `nm_ip4_config_get_never_default'
  ./src/dns/nm-dns-manager.c:419: undefined reference to
  `nm_ip4_config_get_never_default'

  There's been a lot of refactoring, but this commit looks important:
  https://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=5c29945

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

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

[Desktop-packages] [Bug 1750379] Re: Distortion Realtek ALC887

2018-02-22 Thread fleamour

Can confirm kernel makes no difference.

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

Title:
  Distortion Realtek ALC887

Status in linux package in Ubuntu:
  Incomplete
Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  Sounds can distort even when not amplified. Amplification worked well
  for years before recent PulseAudio update. The audio is Realtek ALC887
  under an IntelG41 Chipset with GA-G41M-Combo main board;

  Description:  Ubuntu Bionic Beaver (development branch)
  Release:  18.04

  I am seeking to engage upstream for April LTS release. Windows have
  abandoned this esoteric hardware! Please Ubuntu! Keep a C2D user
  going!

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: pulseaudio 1:11.1-1ubuntu6
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  fleamour   1049 F pulseaudio
   /dev/snd/controlC2:  fleamour   1049 F pulseaudio
   /dev/snd/controlC0:  fleamour   1049 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Feb 19 13:54:33 2018
  InstallationDate: Installed on 2018-02-19 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180214)
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/25/2012
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: FB
  dmi.board.name: G41M-Combo
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrFB:bd10/25/2012:svnGigabyteTechnologyCo.,Ltd.:pnG41M-Combo:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnG41M-Combo:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: G41M-Combo
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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

[Desktop-packages] [Bug 1750162] Re: package gnome-menus 3.13.3-11ubuntu1 failed to install/upgrade: Trigger bilden eine Schleife, aufgegeben

2018-02-22 Thread LAZA

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

I did what i alwas do to update:

"sudo apt update && sudo apt upgrade && sudo apt dist-upgrade"

Finally i got this error(s) (got it twice)

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

Title:
  package gnome-menus 3.13.3-11ubuntu1 failed to install/upgrade:
  Trigger bilden eine Schleife, aufgegeben

Status in gnome-menus package in Ubuntu:
  New

Bug description:
  crashed while updating

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: gnome-menus 3.13.3-11ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  Date: Sat Feb 17 17:28:51 2018
  Dependencies:
   
  ErrorMessage: Trigger bilden eine Schleife, aufgegeben
  InstallationDate: Installed on 2017-10-31 (109 days ago)
  InstallationMedia: Xubuntu 17.10 "Artful Aardvark" - Release amd64 
(20171017.1)
  Python3Details: /usr/bin/python3.6, Python 3.6.4+, python3-minimal, 3.6.4-1
  PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu1
   apt  1.6~alpha7ubuntu1
  SourcePackage: gnome-menus
  Title: package gnome-menus 3.13.3-11ubuntu1 failed to install/upgrade: 
Trigger bilden eine Schleife, aufgegeben
  UpgradeStatus: Upgraded to bionic on 2017-11-16 (92 days ago)

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

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

[Desktop-packages] [Bug 1750937] Re: 14.04 Kernel update on 2/21 breaks Nvidia drivers

2018-02-22 Thread Bernhard

It affects me too:

Nvidia NVS 300 and GT 430 . Nvidia 340.x and 384.111

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

Title:
  14.04 Kernel update on 2/21 breaks Nvidia drivers

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  Running fine with nvidia-384 until this kernel update came along.
  When booted into the new kernel, got super low resolution and nvidia-
  settings was missing most of its functionality - could not change
  resolution.

  Rebooted into 4.4.0-112 kernel and all was well.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 4.4.0-112.135~14.04.1-generic 4.4.98
  Uname: Linux 4.4.0-112-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  384.111  Tue Dec 19 23:51:45 
PST 2017
   GCC version:  gcc version 4.8.4 (Ubuntu 4.8.4-2ubuntu1~14.04.3)
  ApportVersion: 2.14.1-0ubuntu3.27
  Architecture: amd64
  CurrentDesktop: LXDE
  Date: Wed Feb 21 19:23:39 2018
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.7, 4.4.0-112-generic, x86_64: installed
   bbswitch, 0.7, 4.4.0-116-generic, x86_64: installed
   nvidia-384, 384.111, 4.4.0-112-generic, x86_64: installed
   nvidia-384, 384.111, 4.4.0-116-generic, x86_64: installed
  GraphicsCard:
   NVIDIA Corporation Device [10de:1c82] (rev a1) (prog-if 00 [VGA controller])
 Subsystem: eVga.com. Corp. Device [3842:6253]
  InstallationDate: Installed on 2015-03-03 (1086 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  MachineType: ASUSTeK COMPUTER INC. M11AD
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-112-generic 
root=UUID=5a88d2a1-0a24-415b-adc2-28435b13248a ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/15/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0302
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: M11AD
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0302:bd08/15/2013:svnASUSTeKCOMPUTERINC.:pnM11AD:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnM11AD:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: M11AD
  dmi.product.version: System Version
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz 1:0.9.11.3+14.04.20160425-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.14.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri N/A
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Wed Feb 21 18:48:14 2018
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.18.3-1ubuntu2.3~trusty4

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

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

[Desktop-packages] [Bug 1751046] Re: Pidgin rewrites buddy icons on each startup

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

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

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

Title:
  Pidgin rewrites buddy icons on each startup

Status in pidgin package in Ubuntu:
  Confirmed

Bug description:
  Every time Pidgin starts up, it rewrites all the buddy icon files for
  no good reason.

  Fixed in 2.13 by #17259: https://developer.pidgin.im/ticket/17259

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

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

[Desktop-packages] [Bug 1751039] Re: Search results in finch updated incorrectly

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

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

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

Title:
  Search results in finch updated incorrectly

Status in pidgin package in Ubuntu:
  Confirmed

Bug description:
  Finch doesn't clear the previous search results when they are updated
  in real time.

  Fixed upstream by #17238: https://developer.pidgin.im/ticket/17238

  Please could you pull this fix into the packages, even if 2.13 isn't
  released in time.

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

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

[Desktop-packages] [Bug 1751046] Re: Pidgin rewrites buddy icons on each startup

The attachment "0001-Do-not-rewrite-custom-buddy-icons-already-in-the-
cac.patch" seems to be a patch.  If it isn't, please remove the "patch"
flag from the attachment, remove the "patch" tag, and if you are a
member of the ~ubuntu-reviewers, unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issues please contact him.]

** Tags added: patch

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

Title:
  Pidgin rewrites buddy icons on each startup

Status in pidgin package in Ubuntu:
  Confirmed

Bug description:
  Every time Pidgin starts up, it rewrites all the buddy icon files for
  no good reason.

  Fixed in 2.13 by #17259: https://developer.pidgin.im/ticket/17259

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

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

[Desktop-packages] [Bug 1750818] Re: Already installed deb packages not showing as installed when opened using GNOME Software

Thank you for your bug report, what Ubuntu serie and gnome-software
version are you using? On what deb did you try?

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

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

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

Title:
  Already installed deb packages not showing as installed when opened
  using GNOME Software

Status in gnome-software package in Ubuntu:
  Incomplete

Bug description:
  If you open an already installed local deb file using GNOME Software
  (Ubuntu Software), it shows "Install" instead of the correct "Remove"
  option.

  Steps to reproduce:
  1. Open and install any local deb file using GNOME Software.
  2. Close the GNOME Software window.
  3. Open the local deb file again in GNOME Software.

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

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

[Desktop-packages] [Bug 1751038] Re: Labelled buttons missing from Pidgin search dialogs

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

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

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

Title:
  Labelled buttons missing from Pidgin search dialogs

Status in pidgin package in Ubuntu:
  Confirmed

Bug description:
  Pidgin fails to display buttons with custom labels in search dialogs.

  Fixed in 2.13 by #17188: https://developer.pidgin.im/ticket/17188
  (by cherry-picking an existing fix from the master branch for #14821).

  Please could you pull this fix into the packages, even if 2.13 isn't
  released in time.

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

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

[Desktop-packages] [Bug 1751039] Re: Search results in finch updated incorrectly

The attachment "0001-Fix-Finch-search-results-display-17238.patch" seems
to be a patch.  If it isn't, please remove the "patch" flag from the
attachment, remove the "patch" tag, and if you are a member of the
~ubuntu-reviewers, unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issues please contact him.]

** Tags added: patch

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

Title:
  Search results in finch updated incorrectly

Status in pidgin package in Ubuntu:
  Confirmed

Bug description:
  Finch doesn't clear the previous search results when they are updated
  in real time.

  Fixed upstream by #17238: https://developer.pidgin.im/ticket/17238

  Please could you pull this fix into the packages, even if 2.13 isn't
  released in time.

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

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

[Desktop-packages] [Bug 1751037] Re: Mute status not updated

The attachment "0001-Pidgin-Indicate-mute-unmute-status-when-changed-
remo.patch" seems to be a patch.  If it isn't, please remove the "patch"
flag from the attachment, remove the "patch" tag, and if you are a
member of the ~ubuntu-reviewers, unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issues please contact him.]

** Tags added: patch

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

Title:
  Mute status not updated

Status in pidgin package in Ubuntu:
  Confirmed

Bug description:
  When I am on an audio call and the remote end mutes me, that is not
  correctly displayed in the local UI. Fixed in Pidgin 2.13 by #17273:
  https://developer.pidgin.im/ticket/17273

  Please could you pull this fix into the packages, even if 2.13 isn't
  released in time.

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

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

[Desktop-packages] [Bug 1751038] Re: Labelled buttons missing from Pidgin search dialogs

The attachment "0001-Ensure-labelled-buttons-are-shown-for-search-
results.patch" seems to be a patch.  If it isn't, please remove the
"patch" flag from the attachment, remove the "patch" tag, and if you are
a member of the ~ubuntu-reviewers, unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issues please contact him.]

** Tags added: patch

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

Title:
  Labelled buttons missing from Pidgin search dialogs

Status in pidgin package in Ubuntu:
  Confirmed

Bug description:
  Pidgin fails to display buttons with custom labels in search dialogs.

  Fixed in 2.13 by #17188: https://developer.pidgin.im/ticket/17188
  (by cherry-picking an existing fix from the master branch for #14821).

  Please could you pull this fix into the packages, even if 2.13 isn't
  released in time.

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

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

[Desktop-packages] [Bug 1751086] Re: Xorg assert failure: Xorg: ../src/evdev-mt-touchpad-tap.c:1002: tp_tap_handle_state: Assertion `tp->tap.nfingers_down > 0' failed.

thank for your bug report, that's a known libinput issue, a fix has been
commited upstream recently, see
https://bugs.freedesktop.org/show_bug.cgi?id=105160

** Information type changed from Private to Public

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

** Package changed: xorg-server (Ubuntu) => libinput (Ubuntu)

** Changed in: libinput (Ubuntu)
   Status: New => Fix Committed

** Changed in: libinput (Ubuntu)
   Importance: Medium => High

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

Title:
  Xorg assert failure: Xorg: ../src/evdev-mt-touchpad-tap.c:1002:
  tp_tap_handle_state: Assertion `tp->tap.nfingers_down > 0' failed.

Status in libinput package in Ubuntu:
  Fix Committed

Bug description:
  I found this bug while cleaning my touchpad. Pressing and moving it,
  it started to move cursor until it stopped moving for multitouch
  gestures. While pressing and moving my finger quickly, Xorg crashed
  and it showed some colored and short lines on the upper left part of
  the display. This, if done again, forces to crash.

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: xserver-xorg-core 2:1.19.6-1ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13
  Uname: Linux 4.13.0-36-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  AssertionMessage: Xorg: ../src/evdev-mt-touchpad-tap.c:1002: 
tp_tap_handle_state: Assertion `tp->tap.nfingers_down > 0' failed.
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Feb 22 16:42:55 2018
  DistUpgraded: 2018-02-22 16:14:14,915 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   r8168, 8.045.08, 4.13.0-32-generic, x86_64: installed
   r8168, 8.045.08, 4.13.0-36-generic, x86_64: installed
  ExecutablePath: /usr/lib/xorg/Xorg
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 520 [8086:1916] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: Hewlett-Packard Company HD Graphics 520 [103c:8136]
 Subsystem: Hewlett-Packard Company Radeon R5 M330 [103c:8136]
  InstallationDate: Installed on 2017-11-23 (90 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: HP HP Notebook
  ProcCmdline: /usr/lib/xorg/Xorg vt2 -displayfd 3 -auth 
/run/user/1000/gdm/Xauthority -background none -noreset -keeptty -verbose 3
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-36-generic.efi.signed 
root=UUID=b2348b07-e7c3-4656-8070-b4693379c731 ro quiet splash vt.handoff=1
  Signal: 6
  SourcePackage: xorg-server
  StacktraceTop:
   __assert_fail_base (fmt=, 
assertion=assertion@entry=0x7fa4955ef13b "tp->tap.nfingers_down > 0", 
file=file@entry=0x7fa4955ef178 "../src/evdev-mt-touchpad-tap.c", 
line=line@entry=1002, function=function@entry=0x7fa4955ef470 
"tp_tap_handle_state") at assert.c:92
   __GI___assert_fail (assertion=0x7fa4955ef13b "tp->tap.nfingers_down > 0", 
file=0x7fa4955ef178 "../src/evdev-mt-touchpad-tap.c", line=1002, 
function=0x7fa4955ef470 "tp_tap_handle_state") at assert.c:101
   () at /usr/lib/x86_64-linux-gnu/libinput.so.10
   () at /usr/lib/x86_64-linux-gnu/libinput.so.10
   () at /usr/lib/x86_64-linux-gnu/libinput.so.10
  Title: Xorg assert failure: Xorg: ../src/evdev-mt-touchpad-tap.c:1002: 
tp_tap_handle_state: Assertion `tp->tap.nfingers_down > 0' failed.
  UpgradeStatus: Upgraded to bionic on 2018-02-22 (0 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  dmi.bios.date: 12/25/2015
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.1E
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 8136
  dmi.board.vendor: HP
  dmi.board.version: 31.35
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.1E:bd12/25/2015:svnHP:pnHPNotebook:pvrType1ProductConfigId:rvnHP:rn8136:rvr31.35:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP
  dmi.product.name: HP Notebook
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.90-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.3.3-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.3.3-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  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+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

To manage notifications abo

[Desktop-packages] [Bug 1750953] Re: Selecting "Single Display" often dosn't show scaling options until the settings are applied.

Thank you for taking the time to report this bug and helping to make
Ubuntu better. The issue you are reporting is an upstream one and it
would be nice if somebody having it could send the bug to the developers
of the software by following the instructions at
https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please
tell us the number of the upstream bug (or the link), so we can add a
bugwatch that will inform us about its status. Thanks in advance.

** Changed in: gnome-control-center (Ubuntu)
Importance: Undecided => Low

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

Title:
Selecting "Single Display" often dosn't show scaling options until the
settings are applied.

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

Bug description:
# Release

Description: Ubuntu 17.10
Release: 17.10

# Package

Not sure how to check the version of the GNOME settings applet, sorry.

# Steps to reproduce

Connect an external monitor. Open the "Displays" section of the
Settings app. Select "Single Display" and select the currently
disabled monitor in preparation for switching to it.

# Expected

The "Scale" selection appears, as it does when the monitor is both
selected and "Apply" has been clicked.

# What happens instead

The "Scale" selection does not appear, and in fact only appears after
"Apply" has been clicked. This means that in order to switch to
another monitor, you have to first apply an incorrect setting (scaling
will be wrong), click "Keep Settings," find your way to the "Scale"
selection, select the correct scaling, click "Apply" again, then click
"Keep Settings" a final time.

This is really bad when switching between monitors. The worst part is
that whether or not the option is visible is inconsistent.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: gnome-control-center 1:3.26.2-0ubuntu0.2
ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13
Uname: Linux 4.13.0-36-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.7
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Wed Feb 21 23:17:17 2018
ExecutablePath: /usr/bin/gnome-control-center
InstallationDate: Installed on 2017-11-30 (83 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
ProcEnviron:
XDG_RUNTIME_DIR=
SHELL=/bin/zsh
PATH=(custom, user)
LANG=en_US.UTF-8
SourcePackage: gnome-control-center
UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1751037] Re: Mute status not updated

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

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

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

Title:
  Mute status not updated

Status in pidgin package in Ubuntu:
  Confirmed

Bug description:
  When I am on an audio call and the remote end mutes me, that is not
  correctly displayed in the local UI. Fixed in Pidgin 2.13 by #17273:
  https://developer.pidgin.im/ticket/17273

  Please could you pull this fix into the packages, even if 2.13 isn't
  released in time.

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

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

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

2018-02-22 Thread Tuomo Sipola

Still affects me. I have symlinked Deja Dup cache deja-dup ->
/media/username/Space/.deja-dup-cache

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

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

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

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

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

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

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

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

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

[Desktop-packages] [Bug 1751070] Re: mutter 3.28 transition

2018-02-22 Thread Jeremy Bicha

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

** Also affects: budgie-desktop (Ubuntu)
   Importance: Undecided
   Status: New

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

** Changed in: gnome-shell (Ubuntu)
   Status: New => Confirmed

** Changed in: budgie-desktop (Ubuntu)
   Importance: Undecided => Wishlist

** Changed in: budgie-desktop (Ubuntu)
   Status: New => Confirmed

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

Title:
  mutter 3.28 transition

Status in budgie-desktop package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  mutter/gnome-shell transition bug

  mutter's soname is being bumped (this will probably happen for every
  major new GNOME Shell series) so we'll need to update gnome-shell also
  and rebuild budgie-desktop.

  https://gitlab.gnome.org/GNOME/mutter/blob/master/NEWS
  https://gitlab.gnome.org/GNOME/gnome-shell/blob/master/NEWS

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/budgie-desktop/+bug/1751070/+subscriptions

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

[Desktop-packages] [Bug 1750818] Re: Already installed deb packages not showing as installed when opened using GNOME Software

The latest Ubuntu 18.04 build. (But I had the same issue on Ubuntu
17.04.) For example the Steam deb from:
http://store.steampowered.com/about/

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

Title:
  Already installed deb packages not showing as installed when opened
  using GNOME Software

Status in gnome-software package in Ubuntu:
  Incomplete

Bug description:
  If you open an already installed local deb file using GNOME Software
  (Ubuntu Software), it shows "Install" instead of the correct "Remove"
  option.

  Steps to reproduce:
  1. Open and install any local deb file using GNOME Software.
  2. Close the GNOME Software window.
  3. Open the local deb file again in GNOME Software.

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

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

[Desktop-packages] [Bug 1750818] Re: Already installed deb packages not showing as installed when opened using GNOME Software

Oops, s/17.04/17.10. :-)

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

Title:
  Already installed deb packages not showing as installed when opened
  using GNOME Software

Status in gnome-software package in Ubuntu:
  Incomplete

Bug description:
  If you open an already installed local deb file using GNOME Software
  (Ubuntu Software), it shows "Install" instead of the correct "Remove"
  option.

  Steps to reproduce:
  1. Open and install any local deb file using GNOME Software.
  2. Close the GNOME Software window.
  3. Open the local deb file again in GNOME Software.

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

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

[Desktop-packages] [Bug 1749199] Re: purge conf files on removal of upstart (was session fails to start after an upgrade from xenial to bionic)

2018-02-22 Thread Dimitri John Ledkov

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

** Changed in: upstart (Ubuntu Bionic)
   Status: Triaged => Won't Fix

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

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

Title:
  purge conf files on removal of upstart (was session fails to start
  after an upgrade from xenial to bionic)

Status in ubuntu-release-upgrader package in Ubuntu:
  Triaged
Status in xorg package in Ubuntu:
  Triaged
Status in ubuntu-release-upgrader source package in Bionic:
  Triaged
Status in xorg source package in Bionic:
  Triaged

Bug description:
  After an upgrade from Xenial to Bionic the session fails to start and
  returns immediately to the login screen.

  There is this line in the journal
  [...] /usr/lib/gdm3/gdm-x-session[3584]: 
/etc/X11/Xsession.d/99x11-common_start: ligne 5: /sbin/upstart: Aucun fichier 
ou dossier de ce type

  (full journal from a failed attempt attached)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: ubuntu-session 3.26.1-0ubuntu9
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.8-0ubuntu8
  Architecture: amd64
  Date: Tue Feb 13 15:11:12 2018
  InstallationDate: Installed on 2018-02-07 (6 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-session
  UpgradeStatus: Upgraded to bionic on 2018-02-13 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1749199/+subscriptions

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

[Desktop-packages] [Bug 1750818] Re: Already installed deb packages not showing as installed when opened using GNOME Software

(But it was happening on other deb packages as well.)

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

Title:
  Already installed deb packages not showing as installed when opened
  using GNOME Software

Status in gnome-software package in Ubuntu:
  Incomplete

Bug description:
  If you open an already installed local deb file using GNOME Software
  (Ubuntu Software), it shows "Install" instead of the correct "Remove"
  option.

  Steps to reproduce:
  1. Open and install any local deb file using GNOME Software.
  2. Close the GNOME Software window.
  3. Open the local deb file again in GNOME Software.

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

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

[Desktop-packages] [Bug 1751076] Re: Xorg freeze when use mpv or cheese.

2018-02-22 Thread Hans Joachim Desserud

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

** This bug has been marked a duplicate of bug 1751075
   Xorg freeze when use mpv or cheese.

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

Title:
  Xorg freeze when use mpv or cheese.

Status in xorg package in Ubuntu:
  New

Bug description:
  I have my new laptop, Lenovo 720s-13ARR shipped with the latest Ryzen 5 
2500U, installed Ubuntu 17.10, it seems everything works except Wifi and GPU. 
After changing the wifi card with Intel 8265 and manually upgrading kernel with 
M-bab's build from 'https://github.com/M-Bab/linux-kernel-amdgpu-binaries'. 
Wifi and Gpu are working. But if I use mpv playing a video, when I try to 
resume the window from fullscreen, the screen freezes. Same thing happens when 
I use cheese, the camera app. Nothing I can do except a hard poweroff. After 
suffering that couple of times, I started to look for solutions from Internet. 
There are many error messages I can see if I use 'dmesg -l err' in the 
terminal. I cannot solve most of them, only use pci=noaer in the grub to 
suppress the "PCIe bus error", which keep increasing my "/var/log/kern.log" 
file size hundreds MB per hour before.
  One more thing, if I start a reboot, the laptop might have a random hang on 
ubuntu logo screen. To avoid this, I have to poweroff first, then press power 
button to implement a 'reboot'. No idea for me in which part problem should be 
responsible for these failures.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu3
  ProcVersionSignature:
   
  Uname: Linux 4.15.4+ x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu-communitheme:ubuntu:GNOME
  Date: Thu Feb 22 21:53:01 2018
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GpuHangFrequency: I don't know
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Device [1002:15dd] (rev c4) (prog-if 
00 [VGA controller])
 Subsystem: Lenovo Device [17aa:380c]
  InstallationDate: Installed on 2018-01-30 (22 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  MachineType: LENOVO 81BR
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.4+ 
root=UUID=399cfaf6-9c73-4786-8ef5-bd331d20aadc ro pci=noaer 
ivrs_ioapic[4]=00:14.0 ivrs_ioapic[5]=00:00.1 quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/19/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6KCN28WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0L77769 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 720S-13ARR
  dmi.modalias: 
dmi:bvnLENOVO:bvr6KCN28WW:bd12/19/2017:svnLENOVO:pn81BR:pvrLenovoideapad720S-13ARR:rvnLENOVO:rnLNVNB161216:rvrSDK0L77769WIN:cvnLENOVO:ct10:cvrLenovoideapad720S-13ARR:
  dmi.product.family: ideapad 720S-13ARR
  dmi.product.name: 81BR
  dmi.product.version: Lenovo ideapad 720S-13ARR
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.85-4~a~padoka0
  version.libgl1-mesa-dri: libgl1-mesa-dri 1:17.3.2-0~a~padoka0
  version.libgl1-mesa-glx: libgl1-mesa-glx 1:17.3.2-0~a~padoka0
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  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

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

-- 
Mailing list: https://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 1751005] Re: libreoffice cannot open a document not within $HOME

2018-02-22 Thread Mike Cornelison

After getting over the confusion caused by your example, and inputting
the entire command on one line, it did solve the problem. Thanks. The
diagnostic could have been less cryptic. 

On 22.02.2018 12:06, Olivier Tilloy wrote:

> The error message about
> ~/.libreoffice/{3,4}/user/config/javasettings_Linux_*.xml is unrelated,
> it is simply telling you libreoffice cannot find a JRE (but it will work
> fine without it, for the most part).
> 
> What you're seeing is apparmor confinement finally working as intended. The 
> package had been shipping apparmor profiles for some time, but they were not 
> functional, and they have been fixed.
> Those profiles allow reading/writing office documents in $HOME, /mnt and 
> /media (that excludes /home2/).
> 
> Can you try running the following command in a terminal, and confirm
> that this "fixes" your issue:
> 
> sudo apparmor_parser -R
> /etc/apparmor.d/usr.lib.libreoffice.program.*
> 
> -- 
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1751005 [1]
> 
> Title:
> libreoffice cannot open a document not within $HOME
> 
> Status in libreoffice package in Ubuntu:
> New
> 
> Bug description:
> Starting with today's update to LibreOffice 5.4.5.1 40m0(Build:1),
> files not within the user $HOME directory cannot be opened. This has
> nothing to do with ownership or permissions - the target document is
> owned by the user with full permissions. Moving the file to ~/Desktop
> allows it to be opened normally.
> 
> Error message in popup window:
> Access to /home2/mico/documents/personal/2018 lists.ods was denied.
> 
> Error message when launched from terminal:
> $: localc "2018 lists.ods"
> javaldx: Could not find a Java Runtime Environment!
> Please ensure that a JVM and the package libreoffice-java-common is installed.
> If it is already installed then try removing 
> ~/.libreoffice/3/user/config/javasettings_Linux_*.xml
> Warning: failed to read path from javaldx
> 
> The file mentioned in the error message does not exist.
> I removed the corresponding file under ~/.libreoffice/4/ but that makes no 
> difference.
> 
> This but started in Ubuntu 18.04 (alpha) around Feb. 15, and with
> today's update (Feb. 22) it appeared in Ubuntu 17.10.
> 
> ProblemType: Bug
> DistroRelease: Ubuntu 17.10
> Package: libreoffice-core 1:5.4.5-0ubuntu0.17.10.1
> ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13
> Uname: Linux 4.13.0-36-generic x86_64
> ApportVersion: 2.20.7-0ubuntu3.7
> Architecture: amd64
> CurrentDesktop: ubuntu:GNOME
> Date: Thu Feb 22 09:35:49 2018
> InstallationDate: Installed on 2018-01-27 (25 days ago)
> InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
> SourcePackage: libreoffice
> UpgradeStatus: No upgrade log present (probably fresh install)
> 
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1751005/+subscriptions
>  [2]
 

Links:
--
[1] https://bugs.launchpad.net/bugs/1751005
[2]
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1751005/+subscriptions

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

Title:
  libreoffice cannot open a document not within $HOME

Status in libreoffice package in Ubuntu:
  Invalid

Bug description:
  Starting with today's update to LibreOffice 5.4.5.1 40m0(Build:1),
  files not within the user $HOME directory cannot be opened. This has
  nothing to do with ownership or permissions - the target document is
  owned by the user with full permissions. Moving the file to ~/Desktop
  allows it to be opened normally.

  Error message in popup window:
Access to /home2/mico/documents/personal/2018 lists.ods was denied.

  Error message when launched from terminal:
  $: localc "2018 lists.ods"
  javaldx: Could not find a Java Runtime Environment!
  Please ensure that a JVM and the package libreoffice-java-common is installed.
  If it is already installed then try removing 
~/.libreoffice/3/user/config/javasettings_Linux_*.xml
  Warning: failed to read path from javaldx

  The file mentioned in the error message does not exist.
  I removed the corresponding file under ~/.libreoffice/4/ but that makes no 
difference.

  This but started in Ubuntu 18.04 (alpha) around Feb. 15, and with
  today's update (Feb. 22) it appeared in Ubuntu 17.10.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: libreoffice-core 1:5.4.5-0ubuntu0.17.10.1
  ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13
  Uname: Linux 4.13.0-36-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Feb 22 09:35:49 2018
  InstallationDate: Installed on 2018-01-27 (25 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  SourcePackage: libreoffice
  UpgradeStatus: No

[Desktop-packages] [Bug 1749199] Re: purge conf files on removal of upstart (was session fails to start after an upgrade from xenial to bionic)

2018-02-22 Thread Steve Langasek

** No longer affects: upstart (Ubuntu)

** No longer affects: upstart (Ubuntu Bionic)

** Changed in: xorg (Ubuntu Bionic)
   Importance: Undecided => Critical

** Changed in: xorg (Ubuntu Bionic)
 Assignee: (unassigned) => Dimitri John Ledkov (xnox)

** Tags removed: rls-bb-incoming

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

Title:
  purge conf files on removal of upstart (was session fails to start
  after an upgrade from xenial to bionic)

Status in ubuntu-release-upgrader package in Ubuntu:
  Triaged
Status in xorg package in Ubuntu:
  Triaged
Status in ubuntu-release-upgrader source package in Bionic:
  Triaged
Status in xorg source package in Bionic:
  Triaged

Bug description:
  After an upgrade from Xenial to Bionic the session fails to start and
  returns immediately to the login screen.

  There is this line in the journal
  [...] /usr/lib/gdm3/gdm-x-session[3584]: 
/etc/X11/Xsession.d/99x11-common_start: ligne 5: /sbin/upstart: Aucun fichier 
ou dossier de ce type

  (full journal from a failed attempt attached)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: ubuntu-session 3.26.1-0ubuntu9
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.8-0ubuntu8
  Architecture: amd64
  Date: Tue Feb 13 15:11:12 2018
  InstallationDate: Installed on 2018-02-07 (6 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-session
  UpgradeStatus: Upgraded to bionic on 2018-02-13 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1749199/+subscriptions

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

[Desktop-packages] [Bug 1694004] Re: [RFE] Add pidgin-otr to Pidgin Addons in GNOME Software

This will hopefully be fixed with the new pidgin-otr package release.
But I think this probably won't happen before the Ubuntu 18.04 release.
:-(

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

Title:
  [RFE] Add pidgin-otr to Pidgin Addons in GNOME Software

Status in pidgin-otr:
  Confirmed
Status in pidgin package in Ubuntu:
  New
Status in pidgin-otr package in Ubuntu:
  New

Bug description:
  Please consider adding the pidgin-otr plugin to Pidgin Addons in GNOME
  Software. It would make installing this plugin a lot easier for end-
  users. Currently, there is only a SIPE plugin in the list.

To manage notifications about this bug go to:
https://bugs.launchpad.net/pidgin-otr/+bug/1694004/+subscriptions

-- 
Mailing list: https://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 1751005] Re: libreoffice cannot open a document not within $HOME

2018-02-22 Thread Mike Cornelison

Exotic? 
I am a developer and run several different flavors of Linux for testing.
I have done this for years for files accessible to all flavors.

If the file ownership and permissions are OK, I think I should be able 
to access them by default. Apparmor seems to be configured to 
another default - deny access to my owned files if not under $HOME.
Is this a good default?

On 22.02.2018 13:50, Olivier Tilloy wrote:

> No, that's not a solution, because as soon as libreoffice 6 is in the
> ubuntu archive it will have the working apparmor profiles. If you want
> to disable the apparmor profiles permanently, you can do the following:
> 
> sudo ln -s /etc/apparmor.d/usr.lib.libreoffice.program.*
> /etc/apparmor.d/disable/
> 
> I'm going to mark this bug invalid as the apparmor profiles are working
> as expected, but your setup (with a /home2 mount point) is rather
> exotic.
> 
> ** Changed in: libreoffice (Ubuntu)
> Status: New => Invalid
> 
> -- 
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1751005 [1]
> 
> Title:
> libreoffice cannot open a document not within $HOME
> 
> Status in libreoffice package in Ubuntu:
> Invalid
> 
> Bug description:
> Starting with today's update to LibreOffice 5.4.5.1 40m0(Build:1),
> files not within the user $HOME directory cannot be opened. This has
> nothing to do with ownership or permissions - the target document is
> owned by the user with full permissions. Moving the file to ~/Desktop
> allows it to be opened normally.
> 
> Error message in popup window:
> Access to /home2/mico/documents/personal/2018 lists.ods was denied.
> 
> Error message when launched from terminal:
> $: localc "2018 lists.ods"
> javaldx: Could not find a Java Runtime Environment!
> Please ensure that a JVM and the package libreoffice-java-common is installed.
> If it is already installed then try removing 
> ~/.libreoffice/3/user/config/javasettings_Linux_*.xml
> Warning: failed to read path from javaldx
> 
> The file mentioned in the error message does not exist.
> I removed the corresponding file under ~/.libreoffice/4/ but that makes no 
> difference.
> 
> This but started in Ubuntu 18.04 (alpha) around Feb. 15, and with
> today's update (Feb. 22) it appeared in Ubuntu 17.10.
> 
> ProblemType: Bug
> DistroRelease: Ubuntu 17.10
> Package: libreoffice-core 1:5.4.5-0ubuntu0.17.10.1
> ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13
> Uname: Linux 4.13.0-36-generic x86_64
> ApportVersion: 2.20.7-0ubuntu3.7
> Architecture: amd64
> CurrentDesktop: ubuntu:GNOME
> Date: Thu Feb 22 09:35:49 2018
> InstallationDate: Installed on 2018-01-27 (25 days ago)
> InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
> SourcePackage: libreoffice
> UpgradeStatus: No upgrade log present (probably fresh install)
> 
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1751005/+subscriptions
>  [2]
 

Links:
--
[1] https://bugs.launchpad.net/bugs/1751005
[2]
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1751005/+subscriptions

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

Title:
  libreoffice cannot open a document not within $HOME

Status in libreoffice package in Ubuntu:
  Invalid

Bug description:
  Starting with today's update to LibreOffice 5.4.5.1 40m0(Build:1),
  files not within the user $HOME directory cannot be opened. This has
  nothing to do with ownership or permissions - the target document is
  owned by the user with full permissions. Moving the file to ~/Desktop
  allows it to be opened normally.

  Error message in popup window:
Access to /home2/mico/documents/personal/2018 lists.ods was denied.

  Error message when launched from terminal:
  $: localc "2018 lists.ods"
  javaldx: Could not find a Java Runtime Environment!
  Please ensure that a JVM and the package libreoffice-java-common is installed.
  If it is already installed then try removing 
~/.libreoffice/3/user/config/javasettings_Linux_*.xml
  Warning: failed to read path from javaldx

  The file mentioned in the error message does not exist.
  I removed the corresponding file under ~/.libreoffice/4/ but that makes no 
difference.

  This but started in Ubuntu 18.04 (alpha) around Feb. 15, and with
  today's update (Feb. 22) it appeared in Ubuntu 17.10.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: libreoffice-core 1:5.4.5-0ubuntu0.17.10.1
  ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13
  Uname: Linux 4.13.0-36-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Feb 22 09:35:49 2018
  InstallationDate: Installed on 2018-01-27 (25 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  SourcePackage: libreoffice
  Upg

[Desktop-packages] [Bug 1751099] [NEW] Different bugs from what I saw (new linux user)

2018-02-22 Thread Enache Stefan

Public bug reported:

I had some errors for 2-3 days, but it resolved after I made an update, but I 
wanted to check if I still had some bugs,so I runned the command "ubuntu-bug 
cups" and I found a long row...
I would love some help if you can give it to me, I'm a new user and I don't 
know so much about Linux

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: cups 2.1.3-4ubuntu0.4
ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13
Uname: Linux 4.13.0-36-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.15
Architecture: amd64
CurrentDesktop: Unity
Date: Thu Feb 22 19:04:27 2018
InstallationDate: Installed on 2018-01-31 (22 days ago)
InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No 
destinations added.
MachineType: Dell Inc. Latitude D620
Papersize: letter
PccardctlIdent:
 Socket 0:
   no product info available
PccardctlStatus:
 Socket 0:
   no card
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-36-generic 
root=UUID=c5716610-bf00-4497-938c-dba51b08d432 ro quiet splash vt.handoff=7
SourcePackage: cups
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/18/2006
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A07
dmi.board.name: 0FT292
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvrA07:bd12/18/2006:svnDellInc.:pnLatitudeD620:pvr:rvnDellInc.:rn0FT292:rvr:cvnDellInc.:ct8:cvr:
dmi.product.name: Latitude D620
dmi.sys.vendor: Dell Inc.

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


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

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

Title:
  Different bugs from what I saw (new linux user)

Status in cups package in Ubuntu:
  New

Bug description:
  I had some errors for 2-3 days, but it resolved after I made an update, but I 
wanted to check if I still had some bugs,so I runned the command "ubuntu-bug 
cups" and I found a long row...
  I would love some help if you can give it to me, I'm a new user and I don't 
know so much about Linux

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: cups 2.1.3-4ubuntu0.4
  ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-36-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Feb 22 19:04:27 2018
  InstallationDate: Installed on 2018-01-31 (22 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No 
destinations added.
  MachineType: Dell Inc. Latitude D620
  Papersize: letter
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-36-generic 
root=UUID=c5716610-bf00-4497-938c-dba51b08d432 ro quiet splash vt.handoff=7
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/18/2006
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A07
  dmi.board.name: 0FT292
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA07:bd12/18/2006:svnDellInc.:pnLatitudeD620:pvr:rvnDellInc.:rn0FT292:rvr:cvnDellInc.:ct8:cvr:
  dmi.product.name: Latitude D620
  dmi.sys.vendor: Dell Inc.

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

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

[Desktop-packages] [Bug 1750937] Re: 14.04 Kernel update on 2/21 breaks Nvidia drivers

2018-02-22 Thread Tim Habigt

It seems to me that all modules that were re-built with DKMS are
affected by this. For example, I get the same error message when I try
to load the "vboxdrv" module from VirtualBox.

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

Title:
  14.04 Kernel update on 2/21 breaks Nvidia drivers

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  Running fine with nvidia-384 until this kernel update came along.
  When booted into the new kernel, got super low resolution and nvidia-
  settings was missing most of its functionality - could not change
  resolution.

  Rebooted into 4.4.0-112 kernel and all was well.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 4.4.0-112.135~14.04.1-generic 4.4.98
  Uname: Linux 4.4.0-112-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  384.111  Tue Dec 19 23:51:45 
PST 2017
   GCC version:  gcc version 4.8.4 (Ubuntu 4.8.4-2ubuntu1~14.04.3)
  ApportVersion: 2.14.1-0ubuntu3.27
  Architecture: amd64
  CurrentDesktop: LXDE
  Date: Wed Feb 21 19:23:39 2018
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.7, 4.4.0-112-generic, x86_64: installed
   bbswitch, 0.7, 4.4.0-116-generic, x86_64: installed
   nvidia-384, 384.111, 4.4.0-112-generic, x86_64: installed
   nvidia-384, 384.111, 4.4.0-116-generic, x86_64: installed
  GraphicsCard:
   NVIDIA Corporation Device [10de:1c82] (rev a1) (prog-if 00 [VGA controller])
 Subsystem: eVga.com. Corp. Device [3842:6253]
  InstallationDate: Installed on 2015-03-03 (1086 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  MachineType: ASUSTeK COMPUTER INC. M11AD
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-112-generic 
root=UUID=5a88d2a1-0a24-415b-adc2-28435b13248a ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/15/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0302
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: M11AD
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0302:bd08/15/2013:svnASUSTeKCOMPUTERINC.:pnM11AD:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnM11AD:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: M11AD
  dmi.product.version: System Version
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz 1:0.9.11.3+14.04.20160425-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.14.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri N/A
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Wed Feb 21 18:48:14 2018
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.18.3-1ubuntu2.3~trusty4

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

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

[Desktop-packages] [Bug 1749779] Re: System freeze when going back and forth fullscreen mode with Firefox

2018-02-22 Thread Hadrien

https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1751101
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1751102

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

Title:
  System freeze when going back and forth fullscreen mode with Firefox

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Use Ubuntu 17.10
  Open a Wayland session
  Start Firefox
  Press F11 repeatedly
  --> The System freezes

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.2-0ubuntu0.1
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Feb 15 20:09:27 2018
  DisplayManager: gdm3
  InstallationDate: Installed on 2017-10-02 (135 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.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/ubuntu/+source/gnome-shell/+bug/1749779/+subscriptions

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

[Desktop-packages] [Bug 1751102] Re: bug_1749779_Xwayland_crash

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

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 #1731911, 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/1751102/+attachment/5060515/+files/CoreDump.gz

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

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

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

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

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

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

** This bug has been marked a duplicate of bug 1731911
   Xwayland crashed with SIGABRT in OsAbort() from AbortServer() from 
FatalError() from xwl_read_events() from ospoll_wait()

** 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 xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1751102

Title:
  bug_1749779_Xwayland_crash

Status in xorg-server package in Ubuntu:
  New

Bug description:
  See comment #17 in bug 1749779

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: xwayland 2:1.19.5-0ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13
  Uname: Linux 4.13.0-36-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Feb 21 22:01:13 2018
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroVariant: ubuntu
  ExecutablePath: /usr/bin/Xwayland
  ExecutableTimestamp: 1508068793
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480] 
[1002:67df] (rev c7) (prog-if 00 [VGA controller])
 Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Radeon RX 480 [1002:0b37]
  InstallationDate: Installed on 2018-02-21 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 046d:c318 Logitech, Inc. Illuminated Keyboard
   Bus 001 Device 004: ID 1532:0101 Razer USA, Ltd Copperhead Mouse
   Bus 001 Device 002: ID 05e3:0610 Genesys Logic, Inc. 4-port hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: MSI MS-7971
  ProcCmdline: /usr/bin/Xwayland :0 -rootless -terminate -core -listen 4 
-listen 5 -displayfd 6
  ProcCwd: /home/hadrien
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-36-generic 
root=UUID=f4e55a5d-1fcc-4562-9837-fd222f0b19de ro quiet splash vt.handoff=7
  Signal: 6
  SourcePackage: xorg-server
  StacktraceTop:
   OsAbort ()
   ?? ()
   FatalError ()
   ?? ()
   ?? ()
  Title: Xwayland crashed with SIGABRT in OsAbort()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  dmi.bios.date: 12/21/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.H0
  dmi.board.asset.tag: Default string
  dmi.board.name: Z170-A PRO (MS-7971)
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.H0:bd12/21/2016:svnMSI:pnMS-7971:pvr1.0:rvnMSI:rnZ170-APRO(MS-7971):rvr1.0:cvnMSI:ct3:cvr1.0:
  dmi.product.family: Default string
  dmi.product.name: MS-7971
  dmi.product.version: 1.0
  dmi.sys.vendor: MSI
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.83-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~17.10.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~17.10.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  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.

[Desktop-packages] [Bug 1731911] Re: Xwayland crashed with SIGABRT in OsAbort() from AbortServer() from FatalError() from xwl_read_events() from ospoll_wait()