date:20200207

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

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

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

Title:
  open new folder in tab should put new tab on top

Status in nautilus package in Ubuntu:
  Expired

Bug description:
  In the files menu if the user selects the option to open a folder in a
  new tab it seems obvious to me that the user wants to immediately
  start working in that folder.  However the new folder is opened behind
  the current folder, so the user must explicitly select the new folder
  to work on.  I cannot think of any logical situation in which after
  opening a new folder the user would prefer to continue working in
  whatever random folder currently happens to be on top.  I cannot find
  any tweak that controls this behavior.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: unity 7.3.2+15.04.20150420-0ubuntu1
  ProcVersionSignature: Ubuntu 3.19.0-22.22-generic 3.19.8-ckt1
  Uname: Linux 3.19.0-22-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.17.2-0ubuntu1.1
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
  CurrentDesktop: Unity
  Date: Wed Jul 22 18:15:22 2015
  ProcEnviron:
   LANGUAGE=en_CA:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1607919] Re: Nautilus complete freeze after 7zip extraction

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

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

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

Title:
  Nautilus complete freeze after 7zip extraction

Status in nautilus package in Ubuntu:
  Expired

Bug description:
  I've downloaded a .7z file containing an ISO. 
  I've Right clicked on the archive -> Extract here
  I did not have p7zip installed so Ubuntu asked me to install p7zip. I 
accepted.

  After the package manager finished the installation process, the 7zip
  archive has been extracted to my Dekstop and I selected the "show
  extracted files" option. In this moment Nautilus completely freezed. I
  can use all the other software but I cannot launch nautilus and my
  dekstop is freezed.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: nautilus 1:3.18.4.is.3.14.3-0ubuntu4
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  ApportVersion: 2.20.2-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Jul 29 20:42:52 2016
  GsettingsChanges:
   b'org.gnome.nautilus.window-state' b'geometry' b"'890x550+53+24'"
   b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 
'type', 'date_modified', 'date_accessed', 'owner', 'group', 'permissions', 
'mime_type', 'where']"
  InstallationDate: Installed on 2016-06-26 (33 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160623)
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1633382] Re: Windows leave traces when being moved on the main screen, when using two monitors (laptop + external screen)

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

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

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

Title:
  Windows leave traces when being moved on the main screen,when using
  two monitors (laptop + external screen)

Status in nautilus package in Ubuntu:
  Expired

Bug description:
  When I am moving windows on the main screen (when they are not
  maximized), they leave traces and flickering on the screen.

  When using another application on full-screen mode (e.g.: a browser
  window), I can move the windows without any flickering.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: nautilus 1:3.20.3-1ubuntu3
  ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
  Uname: Linux 4.8.0-22-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Oct 14 10:56:39 2016
  ExecutablePath: /usr/bin/nautilus
  GsettingsChanges:
   b'org.gnome.nautilus.window-state' b'geometry' b"'1662x675+258+24'"
   b'org.gnome.nautilus.list-view' b'default-visible-columns' b"['name', 
'size', 'type', 'date_modified']"
   b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 
'type', 'date_modified', 'date_accessed', 'owner', 'group', 'permissions', 
'mime_type', 'where']"
  InstallationDate: Installed on 2015-01-05 (647 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to yakkety on 2016-10-13 (0 days ago)
  usr_lib_nautilus: gnome-terminal 3.20.2-1ubuntu5

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

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

[Desktop-packages] [Bug 1855569] Re: The application does not open on the main monitor, but on the secondary one. Also, the text editor is incorrectly specified as the default application for the cale

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

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

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

Title:
  The application does not open on the main monitor, but on the
  secondary one. Also, the text editor is incorrectly specified as the
  default application for the calendar and cannot be changed.

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

Bug description:
  When you start the program runs on the second monitor, which is
  connected via HDMI. This is repeated all the time. Also, the
  application always opens in full screen.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-control-center 1:3.34.1-1ubuntu2
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Uname: Linux 5.3.0-24-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Dec  8 14:48:07 2019
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2019-12-06 (2 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  ProcEnviron:
   LANG=ru_RU.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  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/1855569/+subscriptions

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

[Desktop-packages] [Bug 1855576] Re: Changing character case when renaming doesn't persist

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

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

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

Title:
  Changing character case when renaming doesn't persist

Status in nautilus package in Ubuntu:
  Expired

Bug description:
  Ubuntu 19.10
  nautilus version: 1:3.34.1-1ubuntu1

  Upon pressing F2 to rename a file, if delete one of the characters and 
replace it with the same character, but a different case, and you click rename, 
the changes should save. 
  Instead they get discarded

  E.g. renaming foo.c -> Foo.c keeps it as foo.c instead of renaming it
  to Foo.c

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: nautilus 1:3.34.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Uname: Linux 5.3.0-24-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Dec  8 11:16:24 2019
  GsettingsChanges:
   b'org.gnome.nautilus.window-state' b'sidebar-width' b'187'
   b'org.gnome.nautilus.window-state' b'initial-size' b'(655, 700)'
   b'org.gnome.nautilus.window-state' b'maximized' b'true'
  InstallationDate: Installed on 2019-10-30 (38 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  ProcEnviron:
   LANGUAGE=en_ZA:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_ZA.UTF-8
   SHELL=/bin/bash
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_nautilus:

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

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

[Desktop-packages] [Bug 1862433] Re: The display collapses for a moment when the mouse moves on 20.20

screencast:
https://youtu.be/Hd0M2gQbEWI
https://youtu.be/8bmQwC0_OHM

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

Title:
  The display collapses for a moment when the mouse moves on 20.20

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  1)
  Description: Ubuntu Focal Fossa (development branch)
  Release: 20.04
  (2020/02/08 daily build)

  2)
  ~/$ apt-cache policy chromium-browser
  chromium-browser:
インストールされているバージョン: 79.0.3945.79-0ubuntu1
候補:   79.0.3945.79-0ubuntu1
バージョンテーブル:
   *** 79.0.3945.79-0ubuntu1 500
  500 http://jp.archive.ubuntu.com/ubuntu focal/universe amd64 Packages
  100 /var/lib/dpkg/status

  3)
  reproduce:

  - wakeup chromium-browser and open multi tab (about over 8 tab)
  - Move web pages to the end
  - mouse move on pages, chromium tab,url area

  reproduce is need running other GPU application? (visual studio code,
  blender ... etc)

  4)
  upon:
  The display collapses for a moment
  - display unknown rectangle. (add screenshot)
  - Page drawing swings from side to side.

  It does not always occur. Even if the phenomenon occurs, it will heal
  and will happen again.

  
  other)
  AMD® Ryzen 5 1600 six-core processor × 12 
  Memory 48GB
  Radeon RX 570 Series
  ~/$ lspci -nnk | grep VGA -A1
  09:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. 
[AMD/ATI] Ellesmere [Radeon RX 470/480/570/570X/580/580X/590] [1002:67df] (rev 
ef)
Subsystem: Sapphire Technology Limited Radeon RX 570 Pulse 4GB 
[1da2:e353]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1862433/+subscriptions

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

[Desktop-packages] [Bug 1862341] Re: Errors thrown at boot: Security

2020-02-07 Thread Rudra Saraswat

** Changed in: xorg (Ubuntu)
   Status: Incomplete => 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/1862341

Title:
  Errors thrown at boot: Security

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  DETAILS:

  Version:  Ubuntu Focal Fossa (development branch)
  Release:  20.04

  xorg:
Installed: 1:7.7+19ubuntu13
Candidate: 1:7.7+19ubuntu13
Version table:
   *** 1:7.7+19ubuntu13 500
  500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status

  Xorg, at boot, through a couple of errors:

  [ error ] display server started at tty -1

  For 20 seconds, the xorg server went on complaining the same issue. I
  tried to ssh into the virtual machine in VirtualBox, and it simply
  logged in without a password.

  Note:
Automatic Login was disabled.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu13
  ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3
  Uname: Linux 5.4.0-9-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu15
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperVersion: 1.438
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Feb  7 11:41:03 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller])
 Subsystem: VMware SVGA II Adapter [15ad:0405]
  LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200124)
  Lsusb:
   Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet
   Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Lsusb-t:
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ohci-pci/12p, 12M
   |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M
  MachineType: innotek GmbH VirtualBox
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: file=/cdrom/preseed/username.seed initrd=/casper/initrd 
quiet splash --- maybe-ubiquity
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.family: Virtual Machine
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.100-4
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.4-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.6-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Desktop-packages] [Bug 1862433] Re: The display collapses for a moment when the mouse moves on 20.20

** Attachment added: "screenshot on youtube"
   
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1862433/+attachment/5326415/+files/000812.jpg

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

Title:
  The display collapses for a moment when the mouse moves on 20.20

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  1)
  Description: Ubuntu Focal Fossa (development branch)
  Release: 20.04
  (2020/02/08 daily build)

  2)
  ~/$ apt-cache policy chromium-browser
  chromium-browser:
インストールされているバージョン: 79.0.3945.79-0ubuntu1
候補:   79.0.3945.79-0ubuntu1
バージョンテーブル:
   *** 79.0.3945.79-0ubuntu1 500
  500 http://jp.archive.ubuntu.com/ubuntu focal/universe amd64 Packages
  100 /var/lib/dpkg/status

  3)
  reproduce:

  - wakeup chromium-browser and open multi tab (about over 8 tab)
  - Move web pages to the end
  - mouse move on pages, chromium tab,url area

  reproduce is need running other GPU application? (visual studio code,
  blender ... etc)

  4)
  upon:
  The display collapses for a moment
  - display unknown rectangle. (add screenshot)
  - Page drawing swings from side to side.

  It does not always occur. Even if the phenomenon occurs, it will heal
  and will happen again.

  
  other)
  AMD® Ryzen 5 1600 six-core processor × 12 
  Memory 48GB
  Radeon RX 570 Series
  ~/$ lspci -nnk | grep VGA -A1
  09:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. 
[AMD/ATI] Ellesmere [Radeon RX 470/480/570/570X/580/580X/590] [1002:67df] (rev 
ef)
Subsystem: Sapphire Technology Limited Radeon RX 570 Pulse 4GB 
[1da2:e353]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1862433/+subscriptions

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

[Desktop-packages] [Bug 1862433] Re: The display collapses for a moment when the mouse moves on 20.20

** Attachment added: "lshw command output"
   
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1862433/+attachment/5326414/+files/lshw.log

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

Title:
  The display collapses for a moment when the mouse moves on 20.20

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  1)
  Description: Ubuntu Focal Fossa (development branch)
  Release: 20.04
  (2020/02/08 daily build)

  2)
  ~/$ apt-cache policy chromium-browser
  chromium-browser:
インストールされているバージョン: 79.0.3945.79-0ubuntu1
候補:   79.0.3945.79-0ubuntu1
バージョンテーブル:
   *** 79.0.3945.79-0ubuntu1 500
  500 http://jp.archive.ubuntu.com/ubuntu focal/universe amd64 Packages
  100 /var/lib/dpkg/status

  3)
  reproduce:

  - wakeup chromium-browser and open multi tab (about over 8 tab)
  - Move web pages to the end
  - mouse move on pages, chromium tab,url area

  reproduce is need running other GPU application? (visual studio code,
  blender ... etc)

  4)
  upon:
  The display collapses for a moment
  - display unknown rectangle. (add screenshot)
  - Page drawing swings from side to side.

  It does not always occur. Even if the phenomenon occurs, it will heal
  and will happen again.

  
  other)
  AMD® Ryzen 5 1600 six-core processor × 12 
  Memory 48GB
  Radeon RX 570 Series
  ~/$ lspci -nnk | grep VGA -A1
  09:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. 
[AMD/ATI] Ellesmere [Radeon RX 470/480/570/570X/580/580X/590] [1002:67df] (rev 
ef)
Subsystem: Sapphire Technology Limited Radeon RX 570 Pulse 4GB 
[1da2:e353]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1862433/+subscriptions

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

[Desktop-packages] [Bug 1862433] [NEW] The display collapses for a moment when the mouse moves on 20.20

Public bug reported:

1)
Description: Ubuntu Focal Fossa (development branch)
Release: 20.04
(2020/02/08 daily build)

2)
~/$ apt-cache policy chromium-browser
chromium-browser:
  インストールされているバージョン: 79.0.3945.79-0ubuntu1
  候補:   79.0.3945.79-0ubuntu1
  バージョンテーブル:
 *** 79.0.3945.79-0ubuntu1 500
500 http://jp.archive.ubuntu.com/ubuntu focal/universe amd64 Packages
100 /var/lib/dpkg/status

3)
reproduce:

- wakeup chromium-browser and open multi tab (about over 8 tab)
- Move web pages to the end
- mouse move on pages, chromium tab,url area

reproduce is need running other GPU application? (visual studio code,
blender ... etc)

4)
upon:
The display collapses for a moment
- display unknown rectangle. (add screenshot)
- Page drawing swings from side to side.

It does not always occur. Even if the phenomenon occurs, it will heal
and will happen again.


other)
AMD® Ryzen 5 1600 six-core processor × 12 
Memory 48GB
Radeon RX 570 Series
~/$ lspci -nnk | grep VGA -A1
09:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. 
[AMD/ATI] Ellesmere [Radeon RX 470/480/570/570X/580/580X/590] [1002:67df] (rev 
ef)
Subsystem: Sapphire Technology Limited Radeon RX 570 Pulse 4GB 
[1da2:e353]

** Affects: chromium-browser (Ubuntu)
 Importance: Undecided
 Status: New

** Attachment added: "screenshot"
   https://bugs.launchpad.net/bugs/1862433/+attachment/5326413/+files/000157.jpg

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

Title:
  The display collapses for a moment when the mouse moves on 20.20

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  1)
  Description: Ubuntu Focal Fossa (development branch)
  Release: 20.04
  (2020/02/08 daily build)

  2)
  ~/$ apt-cache policy chromium-browser
  chromium-browser:
インストールされているバージョン: 79.0.3945.79-0ubuntu1
候補:   79.0.3945.79-0ubuntu1
バージョンテーブル:
   *** 79.0.3945.79-0ubuntu1 500
  500 http://jp.archive.ubuntu.com/ubuntu focal/universe amd64 Packages
  100 /var/lib/dpkg/status

  3)
  reproduce:

  - wakeup chromium-browser and open multi tab (about over 8 tab)
  - Move web pages to the end
  - mouse move on pages, chromium tab,url area

  reproduce is need running other GPU application? (visual studio code,
  blender ... etc)

  4)
  upon:
  The display collapses for a moment
  - display unknown rectangle. (add screenshot)
  - Page drawing swings from side to side.

  It does not always occur. Even if the phenomenon occurs, it will heal
  and will happen again.

  
  other)
  AMD® Ryzen 5 1600 six-core processor × 12 
  Memory 48GB
  Radeon RX 570 Series
  ~/$ lspci -nnk | grep VGA -A1
  09:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. 
[AMD/ATI] Ellesmere [Radeon RX 470/480/570/570X/580/580X/590] [1002:67df] (rev 
ef)
Subsystem: Sapphire Technology Limited Radeon RX 570 Pulse 4GB 
[1da2:e353]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1862433/+subscriptions

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

[Desktop-packages] [Bug 1862341] Re: Errors thrown at boot: Security

2020-02-07 Thread Seth Arnold

Hello Rudra, can you please investigate your /var/log/auth.log file to
see how the ssh logins were logged?

Thanks

** Information type changed from Private Security to Public Security

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

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

Title:
  Errors thrown at boot: Security

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  DETAILS:

  Version:  Ubuntu Focal Fossa (development branch)
  Release:  20.04

  xorg:
Installed: 1:7.7+19ubuntu13
Candidate: 1:7.7+19ubuntu13
Version table:
   *** 1:7.7+19ubuntu13 500
  500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status

  Xorg, at boot, through a couple of errors:

  [ error ] display server started at tty -1

  For 20 seconds, the xorg server went on complaining the same issue. I
  tried to ssh into the virtual machine in VirtualBox, and it simply
  logged in without a password.

  Note:
Automatic Login was disabled.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu13
  ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3
  Uname: Linux 5.4.0-9-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu15
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperVersion: 1.438
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Feb  7 11:41:03 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller])
 Subsystem: VMware SVGA II Adapter [15ad:0405]
  LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200124)
  Lsusb:
   Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet
   Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Lsusb-t:
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ohci-pci/12p, 12M
   |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M
  MachineType: innotek GmbH VirtualBox
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: file=/cdrom/preseed/username.seed initrd=/casper/initrd 
quiet splash --- maybe-ubiquity
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.family: Virtual Machine
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.100-4
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.4-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.6-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Desktop-packages] [Bug 1862423] [NEW] Save directory for gnome-screenshots cannot be changed

2020-02-07 Thread Josja Van Bever

Public bug reported:

When taking a screenshot in Ubuntu 19.10 using the shortcuts (tested for
PrtScr and PrtScr + Shift), screenshots are saved to the Directory
'Pictures' even if the value of org.gnome.gnome-screenshot -> auto-save-
directory is changed to another directory. This issue occurs when the
value is set to an absolute path but also when the path is preceded by
'file://'. The error does not occur when using the command 'gnome-
screenshot' in the terminal or in the tab opened by 'f2 + alt' (though
the suggested directory in the interactive mode is 'Pictures' instead of
the modified value). Changing the value of the auto-save-directory was
done using either the terminal, the dconf-editor or the gnome-shell
extention 'Screenshot locations' as suggested at
https://askubuntu.com/questions/114429/default-save-directory-for-gnome-
screenshot.

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: gnome-screenshot 3.33.90-1ubuntu1
ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13
Uname: Linux 5.3.0-29-generic x86_64
ApportVersion: 2.20.11-0ubuntu8.2
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri Feb  7 22:40:50 2020
InstallationDate: Installed on 2020-01-29 (9 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
SourcePackage: gnome-screenshot
UpgradeStatus: Upgraded to eoan on 2020-01-31 (7 days ago)

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


** Tags: amd64 apport-bug eoan

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

Title:
  Save directory for gnome-screenshots cannot be changed

Status in gnome-screenshot package in Ubuntu:
  New

Bug description:
  When taking a screenshot in Ubuntu 19.10 using the shortcuts (tested
  for PrtScr and PrtScr + Shift), screenshots are saved to the Directory
  'Pictures' even if the value of org.gnome.gnome-screenshot -> auto-
  save-directory is changed to another directory. This issue occurs when
  the value is set to an absolute path but also when the path is
  preceded by 'file://'. The error does not occur when using the command
  'gnome-screenshot' in the terminal or in the tab opened by 'f2 + alt'
  (though the suggested directory in the interactive mode is 'Pictures'
  instead of the modified value). Changing the value of the auto-save-
  directory was done using either the terminal, the dconf-editor or the
  gnome-shell extention 'Screenshot locations' as suggested at
  https://askubuntu.com/questions/114429/default-save-directory-for-
  gnome-screenshot.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-screenshot 3.33.90-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13
  Uname: Linux 5.3.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Feb  7 22:40:50 2020
  InstallationDate: Installed on 2020-01-29 (9 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  SourcePackage: gnome-screenshot
  UpgradeStatus: Upgraded to eoan on 2020-01-31 (7 days ago)

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

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

[Desktop-packages] [Bug 1600622] Re: Screen doesn't lock or go to sleep when certain Chrome tabs are open

2020-02-07 Thread Dmitry Diskin

Why is it still "Low Importance"?

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

Title:
  Screen doesn't lock or go to sleep when certain Chrome tabs are open

Status in gnome-session package in Ubuntu:
  Confirmed

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

  $ apt-cache policy gnome-session-bin
  gnome-session-bin:
    Installed: 3.18.1.2-1ubuntu1.16.04.1
    Candidate: 3.18.1.2-1ubuntu1.16.04.1
    Version table:
   *** 3.18.1.2-1ubuntu1.16.04.1 500
  500 http://es.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   3.18.1.2-1ubuntu1 500
  500 http://es.archive.ubuntu.com/ubuntu xenial/main amd64 Packages

  I'm using gnome-session-flashback

  What happens:
  The screen doesn't lock when having certain pages in Chrome tabs

  Expected:
  The screen should lock after the configured timeout in settings.

  I've been having this issue sice before 14.04, which I recently
  upgraded (fresh install) to 16.04.

  After fresh install, the screen would turn down and lock the computer
  after 10 minutes (or whatever time I setup). At one point it stopped
  working. The screen never shuts down unless I manually lock the
  session with CTRL-ALT-L.

  I've followed the steps in
  https://wiki.ubuntu.com/DebuggingScreenLocking#Debugging_procedure

  The culprit seems to be that Chrome issues some suspend inhibitions
  through dbus when doing certain operations. Many people find this
  problem when using Yahoo Mail. I can reproduce it with Odoo. I'm
  pretty sure that Chrome is doing something else of what i've found
  out.

  1) Gnome screen saver works correctly. I can trigger it manually with:
  $ gnome-screensaver-command -a

  2) Gnome screen saver never receives the "session idle" status
  callback.

  3) When Chrome is not running, I can manually inhibit the idle status:
  $ gnome-session-inhibit --app-id test --reason "manual idle inhibit" 
--inhibit-only --inhibit idle:suspend
  Inhibiting until Ctrl+C is pressed...

  4) I can query the inhibitors:
  $ dbus-send --print-reply --dest=org.gnome.SessionManager 
/org/gnome/SessionManager org.gnome.SessionManager.GetInhibitorsmethod return 
time=1468170482.066533 sender=:1.19 -> destination=:1.1315311 serial=1329103 
reply_serial=2
     array [
    object path "/org/gnome/SessionManager/Inhibitor1686"
     ]
  $ gdbus call --session --dest org.gnome.SessionManager --object-path 
/org/gnome/SessionManager/Inhibitor1686 --method 
org.gnome.SessionManager.Inhibitor.GetAppId
  ('test',)
  $ gdbus call --session --dest org.gnome.SessionManager --object-path 
/org/gnome/SessionManager/Inhibitor1686 --method 
org.gnome.SessionManager.Inhibitor.GetReason
  ('manual idle inhibit',)
  $ gdbus call --session --dest org.gnome.SessionManager --object-path 
/org/gnome/SessionManager/Inhibitor1686 --method 
org.gnome.SessionManager.Inhibitor.GetFlags
  (uint32 12,)

  12=4(suspend) + 8(idle)

  5) When testing, I can inhibit for 70 seconds, idle timeout being 60
  (1 minute). After these 70 seconds pass, the screen locks.

  6) Regarding Chrome, this is the information I get when querying the 
inhibitor:
  GetAppId: ('/usr/bin/google-chrome-stable',)
  GetReason: ('Uploading data to 10.200.0.163',)
  GetFlags: (uint32 4,)

  The flags just inhibits suspend, not locking or entering powersaving
  mode.

  This inhibitor seems to stay for 10-15 seconds, then goes away for
  another 30-60 seconds. The screen NEVER locks when this tab is open.
  No matter the inhibitor is present or not.

  I'm not sure where to go on. If it's a Chrome bug it must be using
  other mechanisms to prevent the idle timeout. Any ideas on what to
  look for?

  Julian.

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

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

[Desktop-packages] [Bug 1862053] Re: Compiler gets stuck (or extremely slow) on ppc64el

2020-02-07 Thread Till Kamppeter

Debian is not using the exception rule for not using -O3 on ppc64el in
their Ghostscript package, simply due to the fact that the whole Debian
is done with -O2 by default, on all architectures.

Are there also problems with -O3 on ppc64el with other packages than
Ghostscript? Should we perhaps use -O2 as general default for ppc64el?

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

Title:
  Compiler gets stuck (or extremely slow) on ppc64el

Status in gcc package in Ubuntu:
  Confirmed
Status in ghostscript package in Ubuntu:
  Fix Committed

Bug description:
  I have uploaded Ghostscript 9.50 to focal and it built without any
  problem on all architectures but ppc64el. On ppc64el the compiler
  seems to get stuck (or extremely slow) on one of the files of
  Ghostscript (devices/vector/gdevpdfb.c, I tried twice). This leads to
  the build process being killed after 150 minutes.

  See

  https://launchpad.net/ubuntu/+source/ghostscript/9.50~dfsg-5/+build/18661407

  and

  https://launchpadlibrarian.net/463662514/buildlog_ubuntu-focal-
  ppc64el.ghostscript_9.50~dfsg-5_BUILDING.txt.gz

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

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

[Desktop-packages] [Bug 1702071] Re: Search spins forever, returns no results.

2020-02-07 Thread programmerplays

Still an issue on 19.10 and 20.04

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

Title:
  Search spins forever, returns no results.

Status in GNOME Software:
  Fix Released
Status in gnome-software package in Ubuntu:
  Triaged

Bug description:
  alan@gort:~$ apt-cache policy gnome-software
  gnome-software:
Installed: 3.20.5-0ubuntu0.16.04.1.1
Candidate: 3.20.5-0ubuntu0.16.04.1.1
Version table:
   *** 3.20.5-0ubuntu0.16.04.1.1 500
  500 http://ppa.launchpad.net/ubuntu-desktop/gnome-software/ubuntu 
xenial/main amd64 Packages
  100 /var/lib/dpkg/status
   3.20.1+git20170524.0.ea2fe2b0-0ubuntu0.16.04.1 500
  500 http://gb.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
   3.20.1+git20160420.1.ca63436.ubuntu-xenial-0ubuntu2 500
  500 http://gb.archive.ubuntu.com/ubuntu xenial/main amd64 Packages

  I mentioned to Robert last week that I keep getting the spinner and no
  results returned when searching in g-s on 16.04. He suggested I update
  to the version in the PPA and enable logging to capture what's
  happening. Log attached.

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

-- 
Mailing list: https://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 1825515] Re: Looping login cycle when trying to login to Ubuntu-Gnome (both X and Wayland). But logs in to Ubuntu with Budgie desktop okay.

2020-02-07 Thread Michael Young

Dear Balint,
Thankyou for your reply concerning my login bug. Fortunately the problem
has disappeared with installation of 19.10 which I am finding to be the
best Ubuntu release since the return to gnome desktop. Many thanks to all
working on desktop Ubuntu for making it so successful.
Cheers, Mike Young.

On Sat, 8 Feb 2020, 02:31 Balint Reczey 
wrote:

> Do you still observe the issue on 19.10 or later?
> I'm reassigning to a package more related to the potential bug.
>
> ** Package changed: shadow (Ubuntu) => gnome-shell (Ubuntu)
>
> ** Changed in: gnome-shell (Ubuntu)
>Status: New => Incomplete
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1825515
>
> Title:
>   Looping login cycle when trying to login to Ubuntu-Gnome (both X and
>   Wayland). But logs in to Ubuntu with Budgie desktop okay.
>
> Status in gnome-shell package in Ubuntu:
>   Incomplete
>
> Bug description:
>   Bug started immediately after upgrading to Ubuntu 19.04. Have tried
>   all the suggested work-arounds I can find on the web but none of them
>   has any effect on the problem.
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 19.04
>   Package: login 1:4.5-1.1ubuntu2
>   ProcVersionSignature: Ubuntu 4.18.0-17.18-generic 4.18.20
>   Uname: Linux 4.18.0-17-generic x86_64
>   NonfreeKernelModules: wl
>   ApportVersion: 2.20.10-0ubuntu27
>   Architecture: amd64
>   CurrentDesktop: Budgie:GNOME
>   Date: Fri Apr 19 22:39:45 2019
>   InstallationDate: Installed on 2018-10-22 (179 days ago)
>   InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64
> (20180426)
>   SourcePackage: shadow
>   UpgradeStatus: Upgraded to disco on 2019-04-18 (1 days ago)
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1825515/+subscriptions
>

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

Title:
  Looping login cycle when trying to login to Ubuntu-Gnome (both X and
  Wayland). But logs in to Ubuntu with Budgie desktop okay.

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Bug started immediately after upgrading to Ubuntu 19.04. Have tried
  all the suggested work-arounds I can find on the web but none of them
  has any effect on the problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: login 1:4.5-1.1ubuntu2
  ProcVersionSignature: Ubuntu 4.18.0-17.18-generic 4.18.20
  Uname: Linux 4.18.0-17-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: Budgie:GNOME
  Date: Fri Apr 19 22:39:45 2019
  InstallationDate: Installed on 2018-10-22 (179 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  SourcePackage: shadow
  UpgradeStatus: Upgraded to disco on 2019-04-18 (1 days ago)

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

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

[Desktop-packages] [Bug 1804568] Re: click position is flipped to cursor position when in tent mode

2020-02-07 Thread Imre Péntek

https://gitlab.gnome.org/GNOME/mutter/issues/1036
let's hope they fix it

** Bug watch added: gitlab.gnome.org/GNOME/mutter/issues #1036
   https://gitlab.gnome.org/GNOME/mutter/issues/1036

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

Title:
  click position is flipped to cursor position when in tent mode

Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  Hello,

  same bug is present 18.04 and 18.10:

  after I log in in tent mode the screen goes upside down, and after

  xrandr --output eDP-1 --rotate normal

  it goes back to normal however now the cursor is upside down, and
  click position and cursor position isnt the same, they are flipped

  thank you for the fix in advance

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: coreutils 8.28-1ubuntu2
  ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
  Uname: Linux 4.18.0-11-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Nov 22 04:28:21 2018
  ExecutablePath: /bin/sleep
  InstallationDate: Installed on 2018-11-22 (0 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  ProcEnviron:
   LANG=hu_HU.UTF-8
   TERM=xterm-256color
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
   PATH=(custom, no user)
  SourcePackage: coreutils
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  imi1950 F pulseaudio
   /dev/snd/controlC1:  imi1950 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.04
  InstallationDate: Installed on 2019-03-30 (0 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190329)
  MachineType: HP HP Spectre x360 Convertible 13-w0XX
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-8-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-8-generic N/A
   linux-backports-modules-5.0.0-8-generic  N/A
   linux-firmware   1.178
  Tags:  disco
  Uname: Linux 5.0.0-8-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/27/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F.31
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 827E
  dmi.board.vendor: HP
  dmi.board.version: 94.60
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF.31:bd04/27/2017:svnHP:pnHPSpectrex360Convertible13-w0XX:pvr:rvnHP:rn827E:rvr94.60:cvnHP:ct31:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=SPT
  dmi.product.name: HP Spectre x360 Convertible 13-w0XX
  dmi.product.sku: Z9E46EA#ABV
  dmi.sys.vendor: HP
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  imi1333 F pulseaudio
   /dev/snd/controlC1:  imi1333 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-09-23 (0 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190917)
  MachineType: HP HP Spectre x360 Convertible 13-w0XX
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-10-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-10-generic N/A
   linux-backports-modules-5.3.0-10-generic  N/A
   linux-firmware1.182
  Tags:  eoan
  Uname: Linux 5.3.0-10-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/03/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F.49
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 827E
  dmi.board.vendor: HP
  dmi.board.version: 94.71
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF.49:bd05/03/2019:svnHP:pnHPSpectrex360Convertible13-w0XX:pvr:rvnHP:rn827E:rvr94.71:cvnHP:ct31:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=SPT
  dmi.product.name: HP Spectre x360 Convertible 13-w0XX
  dmi.product.sku: Z9E46EA#ABV
  dmi.sys.vendor: HP
  ---

[Desktop-packages] [Bug 1804568] Re: click position is flipped to cursor position when in tent mode

2020-02-07 Thread Imre Péntek

Thanks @vanvugt, I'll do so :)

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

Title:
  click position is flipped to cursor position when in tent mode

Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  Hello,

  same bug is present 18.04 and 18.10:

  after I log in in tent mode the screen goes upside down, and after

  xrandr --output eDP-1 --rotate normal

  it goes back to normal however now the cursor is upside down, and
  click position and cursor position isnt the same, they are flipped

  thank you for the fix in advance

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: coreutils 8.28-1ubuntu2
  ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
  Uname: Linux 4.18.0-11-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Nov 22 04:28:21 2018
  ExecutablePath: /bin/sleep
  InstallationDate: Installed on 2018-11-22 (0 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  ProcEnviron:
   LANG=hu_HU.UTF-8
   TERM=xterm-256color
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
   PATH=(custom, no user)
  SourcePackage: coreutils
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  imi1950 F pulseaudio
   /dev/snd/controlC1:  imi1950 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.04
  InstallationDate: Installed on 2019-03-30 (0 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190329)
  MachineType: HP HP Spectre x360 Convertible 13-w0XX
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-8-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-8-generic N/A
   linux-backports-modules-5.0.0-8-generic  N/A
   linux-firmware   1.178
  Tags:  disco
  Uname: Linux 5.0.0-8-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/27/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F.31
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 827E
  dmi.board.vendor: HP
  dmi.board.version: 94.60
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF.31:bd04/27/2017:svnHP:pnHPSpectrex360Convertible13-w0XX:pvr:rvnHP:rn827E:rvr94.60:cvnHP:ct31:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=SPT
  dmi.product.name: HP Spectre x360 Convertible 13-w0XX
  dmi.product.sku: Z9E46EA#ABV
  dmi.sys.vendor: HP
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  imi1333 F pulseaudio
   /dev/snd/controlC1:  imi1333 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-09-23 (0 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190917)
  MachineType: HP HP Spectre x360 Convertible 13-w0XX
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-10-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-10-generic N/A
   linux-backports-modules-5.3.0-10-generic  N/A
   linux-firmware1.182
  Tags:  eoan
  Uname: Linux 5.3.0-10-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/03/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F.49
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 827E
  dmi.board.vendor: HP
  dmi.board.version: 94.71
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF.49:bd05/03/2019:svnHP:pnHPSpectrex360Convertible13-w0XX:pvr:rvnHP:rn827E:rvr94.71:cvnHP:ct31:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=SPT
  dmi.product.name: HP Spectre x360 Convertible 13-w0XX
  dmi.product.sku: Z9E46EA#ABV
  dmi.sys.vendor: HP
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate:

[Desktop-packages] [Bug 1853357] Re: display (whole computer?) hangs when I attempt to use DisplayLink with Wayland

2020-02-07 Thread Jonathan Kamens

You say that the library and kernel module in Ubuntu are older than the
ones from DisplayLink.com. Can you explain why the current versions of
the module and library aren't being shipped in Focal?

I'm afraid I can't test any further in 19.10 since I've already upgraded
both of my laptops to 20.04. :-(

And I can't test the kernel module and library from the DisplayLink.com
release in 20.04 because (as noted above) they don't build successfully.

I've been in contact with the DisplayLink.com folks and they say that
they are working on an updated release for 20.04. So perhaps at this
point all that I can do is wait for that to come out and then retest
eveything and we can figure out what to do from there if there are still
issues.

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

Title:
  display (whole computer?) hangs when I attempt to use DisplayLink with
  Wayland

Status in Mutter:
  New
Status in mutter package in Ubuntu:
  Incomplete
Status in mutter source package in Eoan:
  Confirmed
Status in mutter source package in Focal:
  Incomplete

Bug description:
  [ Impact ]

  I am using the DisplayLink driver for Ubuntu provided at
  https://www.displaylink.com/downloads/ubuntu

  DisplayLink is working under Xorg, but when I try to use it under
  Wayland my whole display hangs and I can't even switch to a different
  VT with Ctrl-Alt-F3 so I think maybe the whole computer is hung? Not
  certain.

  [ Test case ]

  - Install DisplayLink drivers
  - Start GNOME Shell in wayland mode
  - Connect to a display-link dock
  - Expect the shell to work properly and be visible in the external device

  [ Regression potential ]

  Wayland session won't work even for standard drm devices

  
  

  I am using the DisplayLink driver for Ubuntu provided at
  https://www.displaylink.com/downloads/ubuntu, which I think is the
  only way to get DisplayLink fully working under Ubuntu? That is,
  DisplayLink didn't work when I installed the evdi-dkms and libevdi0
  Ubuntu packages, and I couldn't find any other packages that might be
  relevant (did I miss something?) so as far as I can tell the only way
  to get everything that's needed is from displaylink.com.

  I'm reporting this issue while logged in under Xorg because I can't
  report it when logged in with my DisplayLink monitors plugged in under
  Wayland, for obvious reasons. :-/

  ProblemType: BugDistroRelease: Ubuntu 19.10
  Package: mutter 3.34.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7
  Uname: Linux 5.3.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Nov 20 14:08:21 2019
  InstallationDate: Installed on 2019-09-12 (69 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 
(20190416)SourcePackage: mutter
  UpgradeStatus: Upgraded to eoan on 2019-09-20 (61 days ago)
  modified.conffile..etc.apport.crashdb.conf: [modified]
  mtime.conffile..etc.apport.crashdb.conf: 2019-10-23T16:51:18.143596

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

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

[Desktop-packages] [Bug 1862229] Re: gnome session crash on boot with kernel 5.3.0-29-generic

2020-02-07 Thread giacof

Sorry, how can I get the ID of the newly-created bugs?

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

Title:
  gnome session crash on boot with kernel 5.3.0-29-generic

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  lsb_release -rd
  Description:  Ubuntu 19.10
  Release:  19.10

  apt-cache policy gnome-shell
  gnome-shell:
    Installato: 3.34.1+git20191024-1ubuntu1~19.10.1
    Candidato:  3.34.1+git20191024-1ubuntu1~19.10.1
    Tabella versione:
   *** 3.34.1+git20191024-1ubuntu1~19.10.1 500
  500 http://it.archive.ubuntu.com/ubuntu eoan-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   3.34.1-1ubuntu1 500
  500 http://it.archive.ubuntu.com/ubuntu eoan/main amd64 Packages

  First there was an issue with hibernation: after resuming, the gnome
  session was not restored and a new one was created (I had to login
  again from start). Here are some relevant log lines:

  [   21.375254] PM: Image signature found, resuming
  [   21.375255] PM: resume from hibernation
  [   21.375607] Freezing user space processes ... (elapsed 0.001 seconds) done.
  [   21.376719] OOM killer disabled.
  [   21.376832] PM: Marking nosave pages: [mem 0x-0x0fff]
  [   21.376834] PM: Marking nosave pages: [mem 0x0004f000-0x0004]
  [   21.376834] PM: Marking nosave pages: [mem 0x0009d000-0x0009efff]
  [   21.376835] PM: Marking nosave pages: [mem 0x000a-0x000f]
  [   21.376837] PM: Marking nosave pages: [mem 0xae7a8000-0xae7aefff]
  [   21.376838] PM: Marking nosave pages: [mem 0xaf18c000-0xaf66afff]
  [   21.376856] PM: Marking nosave pages: [mem 0xb7db3000-0xb7ff]
  [   21.376865] PM: Marking nosave pages: [mem 0xb8759000-0xb87f]
  [   21.376868] PM: Marking nosave pages: [mem 0xb8f9d000-0xb8ff]
  [   21.376870] PM: Marking nosave pages: [mem 0xba6f5000-0xba7f]
  [   21.376875] PM: Marking nosave pages: [mem 0xbbcec000-0x]
  [   21.377562] PM: Basic memory bitmaps created
  [   24.367114] PM: Using 3 thread(s) for decompression
  [   24.367115] PM: Loading and decompressing image data (1585416 pages)...
  [   24.367127] Hibernate inconsistent memory map detected!
  [   24.367138] fbcon: Taking over console
  [   24.367139] PM: Image mismatch: architecture specific data
  [   24.367141] PM: Read 6341664 kbytes in 0.01 seconds (634166.40 MB/s)
  [   24.368077] PM: Error -1 resuming
  [   24.368079] PM: Failed to load hibernation image, recovering.
  [   24.368347] PM: Basic memory bitmaps freed
  [   24.368347] OOM killer enabled.
  [   24.368347] Restarting tasks ... done.
  [   24.384357] Console: switching to colour frame buffer device 240x67
  [   24.404345] PM: resume from hibernation failed (-1)

  Then, since next restart I cannot login anymore, as the session keeps 
crashing immediately after entering user's password.
  The only way I could login back was by selecting the previous kernel version 
on boot (5.3.0-26-generic instead of 5.3.0-29-generic).

  I also noticed all gnome extensions (Applications Menu and Hibernate
  Status Button ) stopped working and were disabled.

  Boot journal attached.

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

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

[Desktop-packages] [Bug 1861481] Re: language-options causes live CD sessions to be untranslated

Related pull request: https://github.com/canonical/lightdm/pull/111

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

Title:
  language-options causes live CD sessions to be untranslated

Status in lightdm package in Ubuntu:
  In Progress

Bug description:
  Since Ubuntu 19.10, for all Ubuntu live CDs that use LightDM (e.g.
  MATE and Xubuntu), if a user selects a language in syslinux other than
  those with an included langpack, the session is then untranslated.

  For example, if one boots Ubuntu MATE 20.04 and selects Greek in
  syslinux, he ends up with LANGUAGE=en in the session.

  The chain of events is:
  LightDM has an Ubuntu-specific patch that makes it call 
/usr/share/language-tools/language-options instead of the upstream `locale -a`.
  `locale -a` does list el_GR as a supported locale because casper correctly 
updated the locales.
  But language-options doesn't list el_GR, so it fools LightDM into thinking 
that Greek aren't supported; while they're all there, since e.g. MATE doesn't 
rely on langpacks; mate-panel.mo and mate-calc.mo etc are all there.

  I believe the correct fix would be for language-options to list el_GR
  on live CDs (to merge the output of locale -a in its output).

  Thanks!

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

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

[Desktop-packages] [Bug 378783] Re: xdg-open *.desktop opens text editor

2020-02-07 Thread Kenneth Hanson

Bug still present in Kubuntu 19.10.

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

Title:
  xdg-open *.desktop opens text editor

Status in GLib:
  New
Status in gvfs:
  New
Status in glib2.0 package in Ubuntu:
  Triaged

Bug description:
  Binary package hint: xdg-utils

  In order to reproduce it execute "xdg-open *.desktop" (choose any
  .desktop file, e.g. one from /usr/share/applications). Actually your
  favorite text editor will open the file. Expected result: It'll be
  executed.

  Because of this bug, desktop entries with the new "#!/usr/bin/env xdg-
  open" shebang feature were opened in the text editor when executed
  from command line.

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

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

[Desktop-packages] [Bug 1862229] Re: gnome session crash on boot with kernel 5.3.0-29-generic

2020-02-07 Thread giacof

I did it for both _usr_bin_gnome-shell.1000.crash and _usr_lib_gnome-
session_gnome-session-binary.1000.crash.

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

Title:
  gnome session crash on boot with kernel 5.3.0-29-generic

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  lsb_release -rd
  Description:  Ubuntu 19.10
  Release:  19.10

  apt-cache policy gnome-shell
  gnome-shell:
    Installato: 3.34.1+git20191024-1ubuntu1~19.10.1
    Candidato:  3.34.1+git20191024-1ubuntu1~19.10.1
    Tabella versione:
   *** 3.34.1+git20191024-1ubuntu1~19.10.1 500
  500 http://it.archive.ubuntu.com/ubuntu eoan-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   3.34.1-1ubuntu1 500
  500 http://it.archive.ubuntu.com/ubuntu eoan/main amd64 Packages

  First there was an issue with hibernation: after resuming, the gnome
  session was not restored and a new one was created (I had to login
  again from start). Here are some relevant log lines:

  [   21.375254] PM: Image signature found, resuming
  [   21.375255] PM: resume from hibernation
  [   21.375607] Freezing user space processes ... (elapsed 0.001 seconds) done.
  [   21.376719] OOM killer disabled.
  [   21.376832] PM: Marking nosave pages: [mem 0x-0x0fff]
  [   21.376834] PM: Marking nosave pages: [mem 0x0004f000-0x0004]
  [   21.376834] PM: Marking nosave pages: [mem 0x0009d000-0x0009efff]
  [   21.376835] PM: Marking nosave pages: [mem 0x000a-0x000f]
  [   21.376837] PM: Marking nosave pages: [mem 0xae7a8000-0xae7aefff]
  [   21.376838] PM: Marking nosave pages: [mem 0xaf18c000-0xaf66afff]
  [   21.376856] PM: Marking nosave pages: [mem 0xb7db3000-0xb7ff]
  [   21.376865] PM: Marking nosave pages: [mem 0xb8759000-0xb87f]
  [   21.376868] PM: Marking nosave pages: [mem 0xb8f9d000-0xb8ff]
  [   21.376870] PM: Marking nosave pages: [mem 0xba6f5000-0xba7f]
  [   21.376875] PM: Marking nosave pages: [mem 0xbbcec000-0x]
  [   21.377562] PM: Basic memory bitmaps created
  [   24.367114] PM: Using 3 thread(s) for decompression
  [   24.367115] PM: Loading and decompressing image data (1585416 pages)...
  [   24.367127] Hibernate inconsistent memory map detected!
  [   24.367138] fbcon: Taking over console
  [   24.367139] PM: Image mismatch: architecture specific data
  [   24.367141] PM: Read 6341664 kbytes in 0.01 seconds (634166.40 MB/s)
  [   24.368077] PM: Error -1 resuming
  [   24.368079] PM: Failed to load hibernation image, recovering.
  [   24.368347] PM: Basic memory bitmaps freed
  [   24.368347] OOM killer enabled.
  [   24.368347] Restarting tasks ... done.
  [   24.384357] Console: switching to colour frame buffer device 240x67
  [   24.404345] PM: resume from hibernation failed (-1)

  Then, since next restart I cannot login anymore, as the session keeps 
crashing immediately after entering user's password.
  The only way I could login back was by selecting the previous kernel version 
on boot (5.3.0-26-generic instead of 5.3.0-29-generic).

  I also noticed all gnome extensions (Applications Menu and Hibernate
  Status Button ) stopped working and were disabled.

  Boot journal attached.

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

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

[Desktop-packages] [Bug 1828581] Re: /usr/bin/gnome-calendar:11:gtk_image_reset:gtk_image_clear:update_weather:update_no_events_page:gcal_year_view_component_removed

2020-02-07 Thread El jinete sin cabeza

** Tags added: focal

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

Title:
  /usr/bin/gnome-
  
calendar:11:gtk_image_reset:gtk_image_clear:update_weather:update_no_events_page:gcal_year_view_component_removed

Status in GNOME Calendar:
  New
Status in gnome-calendar package in Ubuntu:
  Triaged

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
gnome-calendar.  This problem was most recently seen with package version 
3.32.0-1, the problem page at 
https://errors.ubuntu.com/problem/c13a94eea4826eb85fc9ea3d284eaa906e646c07 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

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

-- 
Mailing list: https://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 1858280] Re: Firefox reports "cannot connect to internet" message

2020-02-07 Thread Joel Chosta

Thank you for your assistance, J. Chosta

On Thu, Feb 6, 2020 at 9:30 PM Daniel van Vugt <
daniel.van.v...@canonical.com> wrote:

> ** Summary changed:
>
> - Software mimics internet disconnect problem on startup
> + Firefox reports "cannot connect to internet" message
>
> ** Package changed: xorg (Ubuntu) => firefox (Ubuntu)
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1858280
>
> Title:
>   Firefox reports "cannot connect to internet" message
>
> Status in firefox package in Ubuntu:
>   New
>
> Bug description:
>   Upon initial start-up, when opening Firefox browser, a  "cannot
>   connect to internet message" is displayed on-screen. It suggest to
>   check wiring, but wiring is fine but I checked it still. I run the
>   diagnostics and go to submit trouble report and the bug clears out.
>   The diagnostics do a list of program files that I have submitted
>   numerous times alreadyToday the disconnect happened on 2nd startup
>   after computer was shut down for a bit. I always use Firefox browser,
>   and never had problems before these incidents. I am always able to
>   recover after diagnostics are run. Is there a bug clearing program
>   that I can run to clear out this nuisance problem??  Thank you for
>   your time, J. Chosta
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 18.04
>   Package: xorg 1:7.7+19ubuntu7.1
>   ProcVersionSignature: Ubuntu 4.15.0-72.81-generic 4.15.18
>   Uname: Linux 4.15.0-72-generic x86_64
>   .tmp.unity_support_test.0:
>
>   ApportVersion: 2.20.9-0ubuntu7.9
>   Architecture: amd64
>   CompizPlugins: No value set for
> `/apps/compiz-1/general/screen0/options/active_plugins'
>   CompositorRunning: None
>   Date: Sat Jan  4 10:33:13 2020
>   DistUpgraded: 2018-12-25 11:16:26,692 DEBUG icon theme changed,
> re-reading
>   DistroCodename: bionic
>   DistroVariant: ubuntu
>   DpkgLog:
>
>   ExtraDebuggingInterest: Yes
>   GraphicsCard:
>Advanced Micro Devices, Inc. [AMD/ATI] RV610 [Radeon HD 2400 PRO]
> [1002:94c3] (prog-if 00 [VGA controller])
>  Subsystem: Dell Radeon HD 2400 Pro [1028:0302]
>   InstallationDate: Installed on 2016-08-03 (1249 days ago)
>   InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64
> (20140722.2)
>   MachineType: Dell Inc. Dell XPS420
>   ProcEnviron:
>PATH=(custom, no user)
>LANG=en_US.UTF-8
>SHELL=/bin/bash
>   ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-72-generic
> root=UUID=e737e1ac-8869-44b7-a03f-477223f8 ro drm.debug=0xe
> plymouth:debug
>   SourcePackage: xorg
>   UpgradeStatus: Upgraded to bionic on 2018-12-25 (374 days ago)
>   dmi.bios.date: 03/27/2008
>   dmi.bios.vendor: Dell Inc.
>   dmi.bios.version: A04
>   dmi.board.name: 0TP406
>   dmi.board.vendor: Dell Inc.
>   dmi.chassis.type: 7
>   dmi.chassis.vendor: Dell Inc.
>   dmi.modalias:
> dmi:bvnDellInc.:bvrA04:bd03/27/2008:svnDellInc.:pnDellXPS420:pvr:rvnDellInc.:rn0TP406:rvr:cvnDellInc.:ct7:cvr:
>   dmi.product.name: Dell XPS420
>   dmi.sys.vendor: Dell Inc.
>   version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
>   version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1
>   version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.3
>   version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.3
>   version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3
>   version.xserver-xorg-input-evdev: xserver-xorg-input-evdev
> 1:2.10.5-1ubuntu1
>   version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
>   version.xserver-xorg-video-intel: xserver-xorg-video-intel
> 2:2.99.917+git20171229-1
>   version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
>   xserver.bootTime: Tue Dec 25 08:33:58 2018
>   xserver.configfile: default
>   xserver.devices:
>inputPower Button KEYBOARD, id 6
>inputPower Button KEYBOARD, id 7
>inputLogitech Logitech USB Speaker KEYBOARD, id 8
>inputLogitech USB-PS/2 Optical Mouse MOUSE, id 9
>inputDell Dell USB Keyboard KEYBOARD, id 10
>   xserver.errors:
>
>   xserver.logfile: /var/log/Xorg.0.log
>   xserver.version: 2:1.18.4-0ubuntu0.8
>   xserver.video_driver: radeon
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1858280/+subscriptions
>

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

Title:
  Firefox reports "cannot connect to internet" message

Status in firefox package in Ubuntu:
  New

Bug description:
  Upon initial start-up, when opening Firefox browser, a  "cannot
  connect to internet message" is displayed on-screen. It suggest to
  check wiring, but wiring is fine but I checked it still. I run the
  diagnostics and go to submit trouble report and the bug clears out.
  The diagnostics do a list of program files that I have

[Desktop-packages] [Bug 1862053] Re: Compiler gets stuck (or extremely slow) on ppc64el

2020-02-07 Thread Till Kamppeter

Found that Ubuntu's Ghostscript had already an exception rule for not
using -O3 on ppc64el which got lost with the sync. Re-introducing it and
reporting to Debian ...

** Changed in: ghostscript (Ubuntu)
   Status: Triaged => Fix Committed

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

Title:
  Compiler gets stuck (or extremely slow) on ppc64el

Status in gcc package in Ubuntu:
  Confirmed
Status in ghostscript package in Ubuntu:
  Fix Committed

Bug description:
  I have uploaded Ghostscript 9.50 to focal and it built without any
  problem on all architectures but ppc64el. On ppc64el the compiler
  seems to get stuck (or extremely slow) on one of the files of
  Ghostscript (devices/vector/gdevpdfb.c, I tried twice). This leads to
  the build process being killed after 150 minutes.

  See

  https://launchpad.net/ubuntu/+source/ghostscript/9.50~dfsg-5/+build/18661407

  and

  https://launchpadlibrarian.net/463662514/buildlog_ubuntu-focal-
  ppc64el.ghostscript_9.50~dfsg-5_BUILDING.txt.gz

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

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

[Desktop-packages] [Bug 1862053] Re: Compiler gets stuck (or extremely slow) on ppc64el

2020-02-07 Thread Till Kamppeter

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

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

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

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

Title:
  Compiler gets stuck (or extremely slow) on ppc64el

Status in gcc package in Ubuntu:
  Confirmed
Status in ghostscript package in Ubuntu:
  Triaged

Bug description:
  I have uploaded Ghostscript 9.50 to focal and it built without any
  problem on all architectures but ppc64el. On ppc64el the compiler
  seems to get stuck (or extremely slow) on one of the files of
  Ghostscript (devices/vector/gdevpdfb.c, I tried twice). This leads to
  the build process being killed after 150 minutes.

  See

  https://launchpad.net/ubuntu/+source/ghostscript/9.50~dfsg-5/+build/18661407

  and

  https://launchpadlibrarian.net/463662514/buildlog_ubuntu-focal-
  ppc64el.ghostscript_9.50~dfsg-5_BUILDING.txt.gz

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

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

[Desktop-packages] [Bug 1854485] Please test proposed package

2020-02-07 Thread Łukasz Zemczak

Hello Alberto, or anyone else affected,

Accepted nvidia-graphics-drivers-440 into bionic-proposed. The package
will build now and be available at https://launchpad.net/ubuntu/+source
/nvidia-graphics-drivers-440/440.59-0ubuntu0.18.04.1 in a few hours, and
then in the -proposed repository.

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

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

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

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

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

Title:
  Introduce the new NVIDIA 440 series, and add 5.4 Linux compatibility
  to the 340 and 390 series

Status in linux-restricted-modules package in Ubuntu:
  New
Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-440 package in Ubuntu:
  Fix Released
Status in nvidia-settings package in Ubuntu:
  Fix Released
Status in linux-restricted-modules source package in Bionic:
  New
Status in nvidia-graphics-drivers-340 source package in Bionic:
  Fix Committed
Status in nvidia-graphics-drivers-390 source package in Bionic:
  Fix Committed
Status in nvidia-graphics-drivers-440 source package in Bionic:
  Fix Committed
Status in nvidia-settings source package in Bionic:
  Fix Committed
Status in linux-restricted-modules source package in Eoan:
  New
Status in nvidia-graphics-drivers-340 source package in Eoan:
  Fix Committed
Status in nvidia-graphics-drivers-390 source package in Eoan:
  Fix Committed
Status in nvidia-graphics-drivers-440 source package in Eoan:
  Fix Committed
Status in nvidia-settings source package in Eoan:
  Fix Committed

Bug description:
  [Impact]
  These releases provide both bug fixes and new features, and we would like to
  make sure all of our users have access to these improvements.

  See the changelog entry below for a full list of changes and bugs.

  [Test Case]
  The following development and SRU process was followed:
  https://wiki.ubuntu.com/NVidiaUpdates

  Certification test suite must pass on a range of hardware:
  https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu

  The QA team that executed the tests will be in charge of attaching the
  artifacts and console output of the appropriate run to the bug. nVidia
  maintainers team members will not mark ‘verification-done’ until this
  has happened.

  [Regression Potential]
  In order to mitigate the regression potential, the results of the
  aforementioned system level tests are attached to this bug.

  [Discussion]

  440.40:
    * New upstream release:
  - Added support for the following GPU:
  Quadro T2000 with Max-Q Design
  - Added support for the __GL_SYNC_DISPLAY_DEVICE environment
    variable for Vulkan applications.
  - Fixed a bug that caused applications running directly on a
    display (such as VR HMDs) to tear when a G-SYNC or G-SYNC
    Compatible monitor is plugged in the system.
  - Fixed a bug in an error handling path that could cause a kernel
    crash while loading nvidia.ko.
  - Fixed driver installation failure on Oracle Linux 7.7 systems,
    where the NVIDIA kernel module failed to build with error
    "unknown type name 'vm_fault_t'".
    * Changes from the 440.36 series:
  - Added support for the following GPUs:
    o GeForce GTX 1650 SUPER
    o GeForce GTX 1660 SUPER
  - Fixed graphical corruption that can occur when using glslang
    SPIR-V Generator Version <= 2.
  - Fixed a bug that could cause the X server to crash when running
    applications using GLX indirect rendering.
  - Updated the Module.symvers sanity check, which is part of the
    NVIDIA kernel module build process, to accommodate the recent
    addition of a new field in the Module.symvers file format.
    This fixes the error "The Module.symvers file is missing [...]"
    seen during driver installation or DKMS rebuilds with Linux 5.4 RC
    kernels.
  -

[Desktop-packages] [Bug 1861358] Re: tracker search hangs and never returns results

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

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

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

Title:
  tracker search hangs and never returns results

Status in tracker package in Ubuntu:
  Confirmed

Bug description:
  When I run

  $ tracker search -f Bruni

  I see the following output on console
  -
  (tracker search:2): GLib-GObject-WARNING **: 00:31:10.761: cannot 
register existing type 'TrackerLanguage'

  (tracker search:2): GLib-GObject-WARNING **: 00:31:10.761: cannot
  add private field to invalid (non-instantiatable) type ''

  (tracker search:2): GLib-CRITICAL **: 00:31:10.761:
  g_once_init_leave: assertion 'result != 0' failed

  (tracker search:2): GLib-GObject-CRITICAL **: 00:31:10.761: 
g_object_new_valist: assertion 'G_TYPE_IS_OBJECT (object_type)' failed
  -

  The program hangs and never returns. Sending Control-C brings me back
  to prompt

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: tracker 2.3.0-1
  ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13
  Uname: Linux 5.3.0-29-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  Date: Thu Jan 30 00:31:59 2020
  ExecutablePath: /usr/bin/tracker
  InstallationDate: Installed on 2016-11-05 (1180 days ago)
  InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  SourcePackage: tracker
  UpgradeStatus: Upgraded to eoan on 2020-01-21 (8 days ago)

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

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

[Desktop-packages] [Bug 1862290] Re: Xorg restarts when locked

2020-02-07 Thread David Colborne

Here's the link from step 2:
https://errors.ubuntu.com/oops/bcf0b822-49ce-11ea-a811-fa163ee63de6

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

Title:
  Xorg restarts when locked

Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  My laptop is currently running Xubuntu 18.04.3. Whenever I lock or
  suspend my laptop, Xorg crashes and restarts, frequently bringing down
  whatever applications are running within it.

  Here's my light-locker --debug, just in case that helps:

  [gs_debug_init] gs-debug.c:106 (20:13:53): Debugging enabled
  [main] light-locker.c:142 (20:13:53):  initializing light-locker 1.8.0
  [main] light-locker.c:164 (20:13:53):  Platform:
  gtk:3
  systemd:yes
  ConsoleKit: yes
  UPower: yes
  [main] light-locker.c:196 (20:13:53):  Features:
  lock-after-screensaver: yes
  late-locking:   yes
  lock-on-suspend:yes
  lock-on-lid:yes
  settings backend:   GSETTINGS
  [main] light-locker.c:198 (20:13:53):  lock after screensaver 0
  [main] light-locker.c:199 (20:13:53):  late locking 0
  [main] light-locker.c:200 (20:13:53):  lock on suspend 0
  [main] light-locker.c:201 (20:13:53):  lock on lid 0
  [main] light-locker.c:202 (20:13:53):  idle hint 0
  [init_session_id] gs-listener-dbus.c:2193 (20:13:53):  Got session-id: 
/org/freedesktop/login1/session/c2
  [init_session_id] gs-listener-dbus.c:2198 (20:13:53):  Got sd-session-id: c2
  [init_seat_path] gs-listener-dbus.c:2279 (20:13:53):   Got seat: 
/org/freedesktop/DisplayManager/Seat0

  ** (light-locker:25569): WARNING **: 20:13:53.499: screensaver already
  running in this session

  And here's my /etc/systemd/logind.conf:

  [Login]
  #NAutoVTs=6
  #ReserveVT=6
  #KillUserProcesses=no
  #KillOnlyUsers=
  #KillExcludeUsers=root
  #InhibitDelayMaxSec=5
  #HandlePowerKey=poweroff
  #HandleSuspendKey=suspend
  #HandleHibernateKey=hibernate
  HandleLidSwitch=ignore
  HandleLidSwitchDocked=ignore
  #PowerKeyIgnoreInhibited=no
  #SuspendKeyIgnoreInhibited=no
  #HibernateKeyIgnoreInhibited=no
  #LidSwitchIgnoreInhibited=yes
  #HoldoffTimeoutSec=30s
  #IdleAction=ignore
  #IdleActionSec=30min
  #RuntimeDirectorySize=10%
  #RemoveIPC=yes
  #InhibitorsMax=8192
  #SessionsMax=8192
  #UserTasksMax=33%

  Additional info:

  Description:  Ubuntu 18.04.3 LTS
  Release:  18.04

  xorg:
Installed: 1:7.7+19ubuntu7.1
Candidate: 1:7.7+19ubuntu7.1
Version table:
   *** 1:7.7+19ubuntu7.1 500
  500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   1:7.7+19ubuntu7 500
  500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 5.3.0-28.30~18.04.1-generic 5.3.13
  Uname: Linux 5.3.0-28-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  435.21  Sun Aug 25 08:17:57 
CDT 2019
   GCC version:  gcc version 7.4.0 (Ubuntu 7.4.0-1ubuntu1~18.04.1)
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  CompositorRunning: None
  Date: Thu Feb  6 20:03:07 2020
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 435.21, 4.15.0-76-generic, x86_64: installed
   nvidia, 435.21, 5.0.0-37-generic, x86_64: installed
   nvidia, 435.21, 5.3.0-26-generic, x86_64: installed
   nvidia, 435.21, 5.3.0-28-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) 
(prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Skylake GT2 [HD Graphics 520] 
[103c:80e5]
 Subsystem: Hewlett-Packard Company GM107M [GeForce GTX 950M] [103c:80e5]
  InstallationDate: Installed on 2019-04-11 (301 days ago)
  InstallationMedia: Xubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 138a:0050 Validity Sensors, Inc. Swipe Fingerprint 
Sensor
   Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 002: ID 04f2:b50c Chicony Electronics Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP ENVY Notebook
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-28-generic 
root=/dev/mapper/xubuntu--vg-root ro

[Desktop-packages] [Bug 1854485] Please test proposed package

2020-02-07 Thread Łukasz Zemczak

Hello Alberto, or anyone else affected,

Accepted nvidia-graphics-drivers-440 into eoan-proposed. The package
will build now and be available at https://launchpad.net/ubuntu/+source
/nvidia-graphics-drivers-440/440.59-0ubuntu0.19.10.1 in a few hours, and
then in the -proposed repository.

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

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

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

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

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

Title:
  Introduce the new NVIDIA 440 series, and add 5.4 Linux compatibility
  to the 340 and 390 series

Status in linux-restricted-modules package in Ubuntu:
  New
Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-440 package in Ubuntu:
  Fix Released
Status in nvidia-settings package in Ubuntu:
  Fix Released
Status in linux-restricted-modules source package in Bionic:
  New
Status in nvidia-graphics-drivers-340 source package in Bionic:
  Fix Committed
Status in nvidia-graphics-drivers-390 source package in Bionic:
  Fix Committed
Status in nvidia-graphics-drivers-440 source package in Bionic:
  Fix Committed
Status in nvidia-settings source package in Bionic:
  Fix Committed
Status in linux-restricted-modules source package in Eoan:
  New
Status in nvidia-graphics-drivers-340 source package in Eoan:
  Fix Committed
Status in nvidia-graphics-drivers-390 source package in Eoan:
  Fix Committed
Status in nvidia-graphics-drivers-440 source package in Eoan:
  Fix Committed
Status in nvidia-settings source package in Eoan:
  Fix Committed

Bug description:
  [Impact]
  These releases provide both bug fixes and new features, and we would like to
  make sure all of our users have access to these improvements.

  See the changelog entry below for a full list of changes and bugs.

  [Test Case]
  The following development and SRU process was followed:
  https://wiki.ubuntu.com/NVidiaUpdates

  Certification test suite must pass on a range of hardware:
  https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu

  The QA team that executed the tests will be in charge of attaching the
  artifacts and console output of the appropriate run to the bug. nVidia
  maintainers team members will not mark ‘verification-done’ until this
  has happened.

  [Regression Potential]
  In order to mitigate the regression potential, the results of the
  aforementioned system level tests are attached to this bug.

  [Discussion]

  440.40:
    * New upstream release:
  - Added support for the following GPU:
  Quadro T2000 with Max-Q Design
  - Added support for the __GL_SYNC_DISPLAY_DEVICE environment
    variable for Vulkan applications.
  - Fixed a bug that caused applications running directly on a
    display (such as VR HMDs) to tear when a G-SYNC or G-SYNC
    Compatible monitor is plugged in the system.
  - Fixed a bug in an error handling path that could cause a kernel
    crash while loading nvidia.ko.
  - Fixed driver installation failure on Oracle Linux 7.7 systems,
    where the NVIDIA kernel module failed to build with error
    "unknown type name 'vm_fault_t'".
    * Changes from the 440.36 series:
  - Added support for the following GPUs:
    o GeForce GTX 1650 SUPER
    o GeForce GTX 1660 SUPER
  - Fixed graphical corruption that can occur when using glslang
    SPIR-V Generator Version <= 2.
  - Fixed a bug that could cause the X server to crash when running
    applications using GLX indirect rendering.
  - Updated the Module.symvers sanity check, which is part of the
    NVIDIA kernel module build process, to accommodate the recent
    addition of a new field in the Module.symvers file format.
    This fixes the error "The Module.symvers file is missing [...]"
    seen during driver installation or DKMS rebuilds with Linux 5.4 RC
    kernels.
  - Fixed

[Desktop-packages] [Bug 1855757] Re: [nvidia] Background image corrupted after standby

2020-02-07 Thread Dominik

Yeah, nouveau is not an option for me unfortunately, there are just too
many problems with it.

And the bug is still present for me as well.

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

Title:
  [nvidia] Background image corrupted after standby

Status in gnome-shell package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  Looks similar to
  https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1809407

  When the computer goes to standby, the background image becomes
  corrupted.

  I am able to fix by "killall Xorg" , change the background image
  (settings > background) and restart.  Haven't tried login logout.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Uname: Linux 5.3.0-24-generic x86_64
  NonfreeKernelModules: nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  340.107  Thu May 24 21:54:01 
PDT 2018
   GCC version:  gcc version 9.2.1 20191008 (Ubuntu 9.2.1-9ubuntu2)
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Dec  9 10:58:35 2019
  DistUpgraded: Fresh install
  DistroCodename: eoan
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia-340, 340.107, 5.3.0-23-generic, x86_64: installed
   nvidia-340, 340.107, 5.3.0-24-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation GT215M [GeForce GTS 360M] [10de:0cb1] (rev a2) (prog-if 
00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. GT215M [GeForce GTS 360M] [1043:203c]
  InstallationDate: Installed on 2019-11-29 (10 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: ASUSTek Computer Inc. G60JX
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic 
root=UUID=65117975-c95f-4406-a7cf-da912cda0e70 ro
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/25/2009
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 204
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: G60JX
  dmi.board.vendor: PEGATRON CORPORATION
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: PEGATRON Computer Inc.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr204:bd12/25/2009:svnASUSTekComputerInc.:pnG60JX:pvr1.0:rvnPEGATRONCORPORATION:rnG60JX:rvr1.0:cvnPEGATRONComputerInc.:ct10:cvr1.0:
  dmi.product.family: PEGA Family
  dmi.product.name: G60JX
  dmi.product.sku: 0
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTek Computer Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
  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 2:1.20.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Desktop-packages] [Bug 1861481] Re: language-options causes live CD sessions to be untranslated

On 2020-02-07 16:41, Alkis Georgopoulos wrote:
> I checked with 20.04 and it appears that recent Ubuntu live CDs
> don't have boot=casper anymore; they do still have
> initrd=/casper/initrd;

I also saw that /proc/cmdline contains BOOT_IMAGE=/casper/..., so the
approach would probably have worked with a minor modification.

> but anyway, ^/cow should be fine (sorry I hadn't noticed the ^ there
> before).

Ok, good, then I keep the debdiff for now, in the hope that some sponsor
will approve and upload it soon.

> Thank you for your work in this.

Thank you for reporting it. The current behavior in live sessions of the
flavors is indeed unintentional and unnecessary.

** No longer affects: accountsservice (Ubuntu)

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

Title:
  language-options causes live CD sessions to be untranslated

Status in lightdm package in Ubuntu:
  In Progress

Bug description:
  Since Ubuntu 19.10, for all Ubuntu live CDs that use LightDM (e.g.
  MATE and Xubuntu), if a user selects a language in syslinux other than
  those with an included langpack, the session is then untranslated.

  For example, if one boots Ubuntu MATE 20.04 and selects Greek in
  syslinux, he ends up with LANGUAGE=en in the session.

  The chain of events is:
  LightDM has an Ubuntu-specific patch that makes it call 
/usr/share/language-tools/language-options instead of the upstream `locale -a`.
  `locale -a` does list el_GR as a supported locale because casper correctly 
updated the locales.
  But language-options doesn't list el_GR, so it fools LightDM into thinking 
that Greek aren't supported; while they're all there, since e.g. MATE doesn't 
rely on langpacks; mate-panel.mo and mate-calc.mo etc are all there.

  I believe the correct fix would be for language-options to list el_GR
  on live CDs (to merge the output of locale -a in its output).

  Thanks!

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

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

[Desktop-packages] [Bug 1861481] Re: language-options causes live CD sessions to be untranslated

I checked with 20.04 and it appears that recent Ubuntu live CDs don't
have boot=casper anymore; they do still have initrd=/casper/initrd; but
anyway, ^/cow should be fine (sorry I hadn't noticed the ^ there
before).

Thank you for your work in this.

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

Title:
  language-options causes live CD sessions to be untranslated

Status in accountsservice package in Ubuntu:
  Confirmed
Status in lightdm package in Ubuntu:
  In Progress

Bug description:
  Since Ubuntu 19.10, for all Ubuntu live CDs that use LightDM (e.g.
  MATE and Xubuntu), if a user selects a language in syslinux other than
  those with an included langpack, the session is then untranslated.

  For example, if one boots Ubuntu MATE 20.04 and selects Greek in
  syslinux, he ends up with LANGUAGE=en in the session.

  The chain of events is:
  LightDM has an Ubuntu-specific patch that makes it call 
/usr/share/language-tools/language-options instead of the upstream `locale -a`.
  `locale -a` does list el_GR as a supported locale because casper correctly 
updated the locales.
  But language-options doesn't list el_GR, so it fools LightDM into thinking 
that Greek aren't supported; while they're all there, since e.g. MATE doesn't 
rely on langpacks; mate-panel.mo and mate-calc.mo etc are all there.

  I believe the correct fix would be for language-options to list el_GR
  on live CDs (to merge the output of locale -a in its output).

  Thanks!

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

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

[Desktop-packages] [Bug 1862229] Re: gnome session crash on boot with kernel 5.3.0-29-generic

2020-02-07 Thread giacof

Hi, in /var/crash I have the following files:

-rw-r-  1 giacof   whoopsie 188300182 feb  1 15:34 
_usr_bin_gnome-shell.1000.crash
-rw-r--r--  1 giacof   whoopsie 0 feb  1 15:38 
_usr_bin_gnome-shell.1000.upload
-rw---  1 whoopsie whoopsie37 feb  5 22:37 
_usr_bin_gnome-shell.1000.uploaded
-rw-r-  1 giacof   whoopsie961440 feb  6 14:24 
_usr_lib_gnome-session_gnome-session-binary.1000.crash

Which one shall I choose?
Many thanks.

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

Title:
  gnome session crash on boot with kernel 5.3.0-29-generic

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  lsb_release -rd
  Description:  Ubuntu 19.10
  Release:  19.10

  apt-cache policy gnome-shell
  gnome-shell:
    Installato: 3.34.1+git20191024-1ubuntu1~19.10.1
    Candidato:  3.34.1+git20191024-1ubuntu1~19.10.1
    Tabella versione:
   *** 3.34.1+git20191024-1ubuntu1~19.10.1 500
  500 http://it.archive.ubuntu.com/ubuntu eoan-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   3.34.1-1ubuntu1 500
  500 http://it.archive.ubuntu.com/ubuntu eoan/main amd64 Packages

  First there was an issue with hibernation: after resuming, the gnome
  session was not restored and a new one was created (I had to login
  again from start). Here are some relevant log lines:

  [   21.375254] PM: Image signature found, resuming
  [   21.375255] PM: resume from hibernation
  [   21.375607] Freezing user space processes ... (elapsed 0.001 seconds) done.
  [   21.376719] OOM killer disabled.
  [   21.376832] PM: Marking nosave pages: [mem 0x-0x0fff]
  [   21.376834] PM: Marking nosave pages: [mem 0x0004f000-0x0004]
  [   21.376834] PM: Marking nosave pages: [mem 0x0009d000-0x0009efff]
  [   21.376835] PM: Marking nosave pages: [mem 0x000a-0x000f]
  [   21.376837] PM: Marking nosave pages: [mem 0xae7a8000-0xae7aefff]
  [   21.376838] PM: Marking nosave pages: [mem 0xaf18c000-0xaf66afff]
  [   21.376856] PM: Marking nosave pages: [mem 0xb7db3000-0xb7ff]
  [   21.376865] PM: Marking nosave pages: [mem 0xb8759000-0xb87f]
  [   21.376868] PM: Marking nosave pages: [mem 0xb8f9d000-0xb8ff]
  [   21.376870] PM: Marking nosave pages: [mem 0xba6f5000-0xba7f]
  [   21.376875] PM: Marking nosave pages: [mem 0xbbcec000-0x]
  [   21.377562] PM: Basic memory bitmaps created
  [   24.367114] PM: Using 3 thread(s) for decompression
  [   24.367115] PM: Loading and decompressing image data (1585416 pages)...
  [   24.367127] Hibernate inconsistent memory map detected!
  [   24.367138] fbcon: Taking over console
  [   24.367139] PM: Image mismatch: architecture specific data
  [   24.367141] PM: Read 6341664 kbytes in 0.01 seconds (634166.40 MB/s)
  [   24.368077] PM: Error -1 resuming
  [   24.368079] PM: Failed to load hibernation image, recovering.
  [   24.368347] PM: Basic memory bitmaps freed
  [   24.368347] OOM killer enabled.
  [   24.368347] Restarting tasks ... done.
  [   24.384357] Console: switching to colour frame buffer device 240x67
  [   24.404345] PM: resume from hibernation failed (-1)

  Then, since next restart I cannot login anymore, as the session keeps 
crashing immediately after entering user's password.
  The only way I could login back was by selecting the previous kernel version 
on boot (5.3.0-26-generic instead of 5.3.0-29-generic).

  I also noticed all gnome extensions (Applications Menu and Hibernate
  Status Button ) stopped working and were disabled.

  Boot journal attached.

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

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

[Desktop-packages] [Bug 1861345] Re: Gigabyte x570 Aorus Master with ALC1220 and ESS SABRE 9118 DAC Muted Front speakers 5.1

2020-02-07 Thread Richard Anthony Horan

The kernel parameter "snd-hda-intel.model=dual-codecs" has no effect.

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

Title:
  Gigabyte x570 Aorus Master with ALC1220 and ESS SABRE 9118 DAC Muted
  Front speakers 5.1

Status in alsa-driver package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 18.04.3 LTS
  Kernel 5.5.0
  pulseaudio:
Installed: 1:11.1-1ubuntu7.4
  X570 Aorus Master Motherboard. ALC1220 ESS Sabre sound.

  I have surround 5.1 speakers and the Front Left and Right are Muted.  
  I have to unmute Headphones in alsamixer to hear sound from the front left 
and right speakers is the workaround.

  This step should not be required for speakers 5.1 to work.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  richard2533 F pulseaudio
   /dev/snd/controlC1:  richard2533 F pulseaudio
   /dev/snd/controlC0:  richard2533 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2020-01-28 (2 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  MachineType: Gigabyte Technology Co., Ltd. X570 AORUS MASTER
  Package: linux (not installed)
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-28-generic 
root=UUID=51fe9653-53b0-475f-836e-a1662c6d8b79 ro quiet splash amd_iommu=on 
vt.handoff=1
  ProcVersionSignature: Ubuntu 5.3.0-28.30~18.04.1-generic 5.3.13
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-28-generic N/A
   linux-backports-modules-5.3.0-28-generic  N/A
   linux-firmware1.173.14
  Tags:  bionic
  Uname: Linux 5.3.0-28-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip kvm libvirt lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/06/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F11
  dmi.board.asset.tag: Default string
  dmi.board.name: X570 AORUS MASTER
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF11:bd12/06/2019:svnGigabyteTechnologyCo.,Ltd.:pnX570AORUSMASTER:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570AORUSMASTER:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: X570 AORUS MASTER
  dmi.product.sku: Default string
  dmi.product.version: -CF
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1861345/+subscriptions

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

[Desktop-packages] [Bug 1825515] Re: Looping login cycle when trying to login to Ubuntu-Gnome (both X and Wayland). But logs in to Ubuntu with Budgie desktop okay.

2020-02-07 Thread Balint Reczey

Do you still observe the issue on 19.10 or later?
I'm reassigning to a package more related to the potential bug.

** Package changed: shadow (Ubuntu) => gnome-shell (Ubuntu)

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

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

Title:
  Looping login cycle when trying to login to Ubuntu-Gnome (both X and
  Wayland). But logs in to Ubuntu with Budgie desktop okay.

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Bug started immediately after upgrading to Ubuntu 19.04. Have tried
  all the suggested work-arounds I can find on the web but none of them
  has any effect on the problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: login 1:4.5-1.1ubuntu2
  ProcVersionSignature: Ubuntu 4.18.0-17.18-generic 4.18.20
  Uname: Linux 4.18.0-17-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: Budgie:GNOME
  Date: Fri Apr 19 22:39:45 2019
  InstallationDate: Installed on 2018-10-22 (179 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  SourcePackage: shadow
  UpgradeStatus: Upgraded to disco on 2019-04-18 (1 days ago)

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

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

[Desktop-packages] [Bug 1854485] Re: Introduce the new NVIDIA 440 series, and add 5.4 Linux compatibility to the 340 and 390 series

2020-02-07 Thread Alberto Milone

** Also affects: linux-restricted-modules (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  Introduce the new NVIDIA 440 series, and add 5.4 Linux compatibility
  to the 340 and 390 series

Status in linux-restricted-modules package in Ubuntu:
  New
Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-440 package in Ubuntu:
  Fix Released
Status in nvidia-settings package in Ubuntu:
  Fix Released
Status in linux-restricted-modules source package in Bionic:
  New
Status in nvidia-graphics-drivers-340 source package in Bionic:
  Fix Committed
Status in nvidia-graphics-drivers-390 source package in Bionic:
  Fix Committed
Status in nvidia-graphics-drivers-440 source package in Bionic:
  Fix Committed
Status in nvidia-settings source package in Bionic:
  Fix Committed
Status in linux-restricted-modules source package in Eoan:
  New
Status in nvidia-graphics-drivers-340 source package in Eoan:
  Fix Committed
Status in nvidia-graphics-drivers-390 source package in Eoan:
  Fix Committed
Status in nvidia-graphics-drivers-440 source package in Eoan:
  Fix Committed
Status in nvidia-settings source package in Eoan:
  Fix Committed

Bug description:
  [Impact]
  These releases provide both bug fixes and new features, and we would like to
  make sure all of our users have access to these improvements.

  See the changelog entry below for a full list of changes and bugs.

  [Test Case]
  The following development and SRU process was followed:
  https://wiki.ubuntu.com/NVidiaUpdates

  Certification test suite must pass on a range of hardware:
  https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu

  The QA team that executed the tests will be in charge of attaching the
  artifacts and console output of the appropriate run to the bug. nVidia
  maintainers team members will not mark ‘verification-done’ until this
  has happened.

  [Regression Potential]
  In order to mitigate the regression potential, the results of the
  aforementioned system level tests are attached to this bug.

  [Discussion]

  440.40:
    * New upstream release:
  - Added support for the following GPU:
  Quadro T2000 with Max-Q Design
  - Added support for the __GL_SYNC_DISPLAY_DEVICE environment
    variable for Vulkan applications.
  - Fixed a bug that caused applications running directly on a
    display (such as VR HMDs) to tear when a G-SYNC or G-SYNC
    Compatible monitor is plugged in the system.
  - Fixed a bug in an error handling path that could cause a kernel
    crash while loading nvidia.ko.
  - Fixed driver installation failure on Oracle Linux 7.7 systems,
    where the NVIDIA kernel module failed to build with error
    "unknown type name 'vm_fault_t'".
    * Changes from the 440.36 series:
  - Added support for the following GPUs:
    o GeForce GTX 1650 SUPER
    o GeForce GTX 1660 SUPER
  - Fixed graphical corruption that can occur when using glslang
    SPIR-V Generator Version <= 2.
  - Fixed a bug that could cause the X server to crash when running
    applications using GLX indirect rendering.
  - Updated the Module.symvers sanity check, which is part of the
    NVIDIA kernel module build process, to accommodate the recent
    addition of a new field in the Module.symvers file format.
    This fixes the error "The Module.symvers file is missing [...]"
    seen during driver installation or DKMS rebuilds with Linux 5.4 RC
    kernels.
  - Fixed kernel module build problems with Linux kernel 5.4.0 release
    candidates.
  - Updated nvidia-bug-report.sh to collect information about X server
    crashes from coredumpctl, when available.
  - Updated the nvidia-drm kernel module for compatibility with the
    removal of the DRIVER_PRIME flag in recent Linux kernel versions.
  - Enabled parallel GLSL shader linking by default; i.e., allow
    GL_ARB_parallel_shader_compile to work without first calling
    glMaxShaderCompilerThreadsARB().
  - Added support for HDMI 2.1 variable refresh rate (VRR) G-SYNC
    Compatible monitors on supported GPUs.For more details, see
    "Configuring Multiple Display Devices on One X Screen" in the README.
    Added support for the GLX_NV_multigpu_context and GL_NV_gpu_multicast
    extensions.For more details, see the "Configuring SLI and Multi-GPU
    FrameRendering" chapter of the README, and the extension specifications:
    
https://www.khronos.org/registry/OpenGL/extensions/NV/GLX_NV_multigpu_context.txt
    
https://www.khronos.org/registry/OpenGL/extensions/NV/NV_gpu_multicast.txt

[Desktop-packages] [Bug 1862377] [NEW] WXtoimg

2020-02-07 Thread Cees de Melker

Public bug reported:

No information

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3.1
Uname: Linux 4.16.8-xanmod9 x86_64
ApportVersion: 2.20.1-0ubuntu2.21
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
Date: Fri Feb  7 16:11:25 2020
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
DpkgLog:
 
ExtraDebuggingInterest: I just need to know a workaround
GraphicsCard:
 Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0106] (rev 09) (prog-if 00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. 2nd Generation Core Processor Family 
Integrated Graphics Controller [1043:13c7]
InstallationDate: Installed on 2019-08-19 (171 days ago)
InstallationMedia: Skywave Linux 3.1.1 - Release amd64 (20180606)
MachineType: ASUSTeK Computer Inc. K54L
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.16.8-xanmod9 
root=UUID=4fd4c874-6312-499d-b5b8-a0d6f67182bc ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/26/2011
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: K54L.208
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: K54L
dmi.board.vendor: ASUSTeK Computer Inc.
dmi.board.version: 1.0
dmi.chassis.asset.tag: ATN12345678901234567
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK Computer Inc.
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrK54L.208:bd09/26/2011:svnASUSTeKComputerInc.:pnK54L:pvr1.0:rvnASUSTeKComputerInc.:rnK54L:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:
dmi.product.family: K
dmi.product.name: K54L
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK Computer Inc.
version.compiz: compiz N/A
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.92+git1805251830.c1f2d9~oibaf~x
version.libgl1-mesa-dri: libgl1-mesa-dri 18.2~git1806011930.f00fcf~oibaf~x
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 18.2~git1806011930.f00fcf~oibaf~x
version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.8
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:18.0.1+git1805221933.65c9df~oibaf~x
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.15+git1805201934.ac8f7b~oibaf~x
xserver.bootTime: Fri Feb  7 16:04:35 2020
xserver.configfile: default
xserver.errors:
 Failed to load module "intel" (module does not exist, 0)
 Failed to load module "intel" (module does not exist, 0)
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.18.4-0ubuntu0.8
xserver.video_driver: modeset

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


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

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

Title:
  WXtoimg

Status in xorg package in Ubuntu:
  New

Bug description:
  No information

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3.1
  Uname: Linux 4.16.8-xanmod9 x86_64
  ApportVersion: 2.20.1-0ubuntu2.21
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Fri Feb  7 16:11:25 2020
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DpkgLog:
   
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0106] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. 2nd Generation Core Processor Family 
Integrated Graphics Controller [1043:13c7]
  InstallationDate: Installed on 2019-08-19 (171 days ago)
  InstallationMedia: Skywave Linux 3.1.1 - Release amd64 (20180606)
  MachineType: ASUSTeK Computer Inc. K54L
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.16.8-xanmod9 
root=UUID=4fd4c874-6312-499d-b5b8-a0d6f67182bc ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/26/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: K54L.208
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: K54L
  dmi.board.vendor: ASUSTeK Computer Inc.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK Computer Inc.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrK54L.208:bd09/26/2011:svnASUSTeKComputerInc.:pnK54L:pvr1.0:rvnASUSTeKComputerInc.:rnK54L:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:
  dmi.product.family: K
  dmi.product.name: K54L

[Desktop-packages] [Bug 1825515] [NEW] Looping login cycle when trying to login to Ubuntu-Gnome (both X and Wayland). But logs in to Ubuntu with Budgie desktop okay.

You have been subscribed to a public bug:

Bug started immediately after upgrading to Ubuntu 19.04. Have tried all
the suggested work-arounds I can find on the web but none of them has
any effect on the problem.

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: login 1:4.5-1.1ubuntu2
ProcVersionSignature: Ubuntu 4.18.0-17.18-generic 4.18.20
Uname: Linux 4.18.0-17-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.10-0ubuntu27
Architecture: amd64
CurrentDesktop: Budgie:GNOME
Date: Fri Apr 19 22:39:45 2019
InstallationDate: Installed on 2018-10-22 (179 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
SourcePackage: shadow
UpgradeStatus: Upgraded to disco on 2019-04-18 (1 days ago)

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


** Tags: amd64 apport-bug disco
-- 
Looping login cycle when trying to login to Ubuntu-Gnome (both X and Wayland). 
But logs in to Ubuntu with Budgie desktop okay.
https://bugs.launchpad.net/bugs/1825515
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to gnome-shell in Ubuntu.

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

[Desktop-packages] [Bug 1856861] Re: Firefox 73 require C++17, not available in xenial

2020-02-07 Thread Olivier Tilloy

** Changed in: firefox (Ubuntu)
   Status: Triaged => In Progress

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

Title:
  Firefox 73 require C++17, not available in xenial

Status in firefox package in Ubuntu:
  In Progress

Bug description:
  Firefox trunk, to become version 73.0 in February 2020, has bumped its
  C++ requirement to C++17
  (https://bugzilla.mozilla.org/show_bug.cgi?id=1560664).

  This requires a more recent version (>= 7) of libstdc++6 than what is
  currently available in xenial (5.4.0-6ubuntu1~16.04.12).

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

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

[Desktop-packages] [Bug 1861481] Re: language-options causes live CD sessions to be untranslated

On 2020-02-07 13:41, Alkis Georgopoulos wrote:
> The "grep cow" approach breaks the LTSP package and other software
> that uses a COW root.

Do those packages cause the file system /cow, listed by the df command,
to be mounted? If yes, I wouldn't mind to modify the debdiff. Please let
me know.

> To check for casper, please `grep -w boot=casper /proc/cmdline` or
> something casper-specific.

Thanks for the tip!

> In schools, we sometimes have students of various nationalities.
> They're not frequent enough to install whole langpacks for them, but
> they are frequent enough to configure locales for them (locale-gen).

It's unclear to me why it's more difficult to install language packs
than generating locales separately.

In any case, I would prefer to consider this aspect to be beyond the
scope of this bug report.

> Of course it's your call.

Yes. :)

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

Title:
  language-options causes live CD sessions to be untranslated

Status in accountsservice package in Ubuntu:
  Confirmed
Status in lightdm package in Ubuntu:
  In Progress

Bug description:
  Since Ubuntu 19.10, for all Ubuntu live CDs that use LightDM (e.g.
  MATE and Xubuntu), if a user selects a language in syslinux other than
  those with an included langpack, the session is then untranslated.

  For example, if one boots Ubuntu MATE 20.04 and selects Greek in
  syslinux, he ends up with LANGUAGE=en in the session.

  The chain of events is:
  LightDM has an Ubuntu-specific patch that makes it call 
/usr/share/language-tools/language-options instead of the upstream `locale -a`.
  `locale -a` does list el_GR as a supported locale because casper correctly 
updated the locales.
  But language-options doesn't list el_GR, so it fools LightDM into thinking 
that Greek aren't supported; while they're all there, since e.g. MATE doesn't 
rely on langpacks; mate-panel.mo and mate-calc.mo etc are all there.

  I believe the correct fix would be for language-options to list el_GR
  on live CDs (to merge the output of locale -a in its output).

  Thanks!

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

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

[Desktop-packages] [Bug 1853357] Re: display (whole computer?) hangs when I attempt to use DisplayLink with Wayland

Re: DisplayLink monitors not detected under Xorg, I wonder if that would
have to do with https://gitlab.freedesktop.org/xorg/xserver/issues/909 ?

But that's off-topic in this report too.

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

Title:
  display (whole computer?) hangs when I attempt to use DisplayLink with
  Wayland

Status in Mutter:
  New
Status in mutter package in Ubuntu:
  Incomplete
Status in mutter source package in Eoan:
  Confirmed
Status in mutter source package in Focal:
  Incomplete

Bug description:
  [ Impact ]

  I am using the DisplayLink driver for Ubuntu provided at
  https://www.displaylink.com/downloads/ubuntu

  DisplayLink is working under Xorg, but when I try to use it under
  Wayland my whole display hangs and I can't even switch to a different
  VT with Ctrl-Alt-F3 so I think maybe the whole computer is hung? Not
  certain.

  [ Test case ]

  - Install DisplayLink drivers
  - Start GNOME Shell in wayland mode
  - Connect to a display-link dock
  - Expect the shell to work properly and be visible in the external device

  [ Regression potential ]

  Wayland session won't work even for standard drm devices

  
  

  I am using the DisplayLink driver for Ubuntu provided at
  https://www.displaylink.com/downloads/ubuntu, which I think is the
  only way to get DisplayLink fully working under Ubuntu? That is,
  DisplayLink didn't work when I installed the evdi-dkms and libevdi0
  Ubuntu packages, and I couldn't find any other packages that might be
  relevant (did I miss something?) so as far as I can tell the only way
  to get everything that's needed is from displaylink.com.

  I'm reporting this issue while logged in under Xorg because I can't
  report it when logged in with my DisplayLink monitors plugged in under
  Wayland, for obvious reasons. :-/

  ProblemType: BugDistroRelease: Ubuntu 19.10
  Package: mutter 3.34.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7
  Uname: Linux 5.3.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Nov 20 14:08:21 2019
  InstallationDate: Installed on 2019-09-12 (69 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 
(20190416)SourcePackage: mutter
  UpgradeStatus: Upgraded to eoan on 2019-09-20 (61 days ago)
  modified.conffile..etc.apport.crashdb.conf: [modified]
  mtime.conffile..etc.apport.crashdb.conf: 2019-10-23T16:51:18.143596

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

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

[Desktop-packages] [Bug 1853357] Re: display (whole computer?) hangs when I attempt to use DisplayLink with Wayland

Then the main issue: freezes.

Do I understand correctly, that so far the freezes have only happened
when you have had two monitors attached to the DisplayLink dock? Never
with just one monitor?

Which DisplayLink dock do you have?

You said changing the display configuration is a sure way to freeze?
What do you do exactly, something in GNOME display settings or plugging
cables or?

I doubt the HDMI vs. DVI or monitor brand/model would have an effect
here, so I think you can leave testing those details for later.

For now, I would like us to concentrate on Ubuntu 19.10, and the full
DisplayLink driver package 5.2.14 which includes the EVDI kernel module
and libevdi0.

Verify what version of libmutter-5-0 package you have installed exactly.
If it's older than the one mentioned here to contain the fix I thought
would help, try to get that updated. Let me know what version you have,
I can have a go at reproducing the freeze.

When your machine freezes, can you access it from a remote, e.g. via
ssh?

If you can, you could first take a look at the process list: are gnome-
shell and DisplayLinkManager running? Do they consume CPU?

The next step would be installing a bunch of dbgsym packages and
attaching GDB to gnome-shell when it's frozen to see where it is at. Do
you know how to do that?

** Bug watch added: gitlab.freedesktop.org/xorg/xserver/issues #909
   https://gitlab.freedesktop.org/xorg/xserver/issues/909

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

Title:
  display (whole computer?) hangs when I attempt to use DisplayLink with
  Wayland

Status in Mutter:
  New
Status in mutter package in Ubuntu:
  Incomplete
Status in mutter source package in Eoan:
  Confirmed
Status in mutter source package in Focal:
  Incomplete

Bug description:
  [ Impact ]

  I am using the DisplayLink driver for Ubuntu provided at
  https://www.displaylink.com/downloads/ubuntu

  DisplayLink is working under Xorg, but when I try to use it under
  Wayland my whole display hangs and I can't even switch to a different
  VT with Ctrl-Alt-F3 so I think maybe the whole computer is hung? Not
  certain.

  [ Test case ]

  - Install DisplayLink drivers
  - Start GNOME Shell in wayland mode
  - Connect to a display-link dock
  - Expect the shell to work properly and be visible in the external device

  [ Regression potential ]

  Wayland session won't work even for standard drm devices

  
  

  I am using the DisplayLink driver for Ubuntu provided at
  https://www.displaylink.com/downloads/ubuntu, which I think is the
  only way to get DisplayLink fully working under Ubuntu? That is,
  DisplayLink didn't work when I installed the evdi-dkms and libevdi0
  Ubuntu packages, and I couldn't find any other packages that might be
  relevant (did I miss something?) so as far as I can tell the only way
  to get everything that's needed is from displaylink.com.

  I'm reporting this issue while logged in under Xorg because I can't
  report it when logged in with my DisplayLink monitors plugged in under
  Wayland, for obvious reasons. :-/

  ProblemType: BugDistroRelease: Ubuntu 19.10
  Package: mutter 3.34.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7
  Uname: Linux 5.3.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Nov 20 14:08:21 2019
  InstallationDate: Installed on 2019-09-12 (69 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 
(20190416)SourcePackage: mutter
  UpgradeStatus: Upgraded to eoan on 2019-09-20 (61 days ago)
  modified.conffile..etc.apport.crashdb.conf: [modified]
  mtime.conffile..etc.apport.crashdb.conf: 2019-10-23T16:51:18.143596

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

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

[Desktop-packages] [Bug 1862359] [NEW] Gnome Control Center doesn't open

2020-02-07 Thread Erick Major

Public bug reported:

When I try to open the Gnome Control Center application, it dies
silently. When I try to open it on the terminal, this error is displayed
on the terminal:

$ gnome-control-center --verbose
can't load /usr/lib/x86_64-linux-gnu/spa/support/libspa-support.so: 
/usr/lib/x86_64-linux-gnu/spa/support/libspa-support.so: cannot open shared 
object file: No such file or directory
Segmentation fault (core dumped)

I believe it is a problem with outdated dependencies (libspa-support).
Could you fix this bug, please?

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

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

Title:
  Gnome Control Center doesn't open

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

Bug description:
  When I try to open the Gnome Control Center application, it dies
  silently. When I try to open it on the terminal, this error is
  displayed on the terminal:

  $ gnome-control-center --verbose
  can't load /usr/lib/x86_64-linux-gnu/spa/support/libspa-support.so: 
/usr/lib/x86_64-linux-gnu/spa/support/libspa-support.so: cannot open shared 
object file: No such file or directory
  Segmentation fault (core dumped)

  I believe it is a problem with outdated dependencies (libspa-support).
  Could you fix this bug, please?

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

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

[Desktop-packages] [Bug 1862162] Re: Badly working video mode on the greeter

2020-02-07 Thread Jarno Suni

** Description changed:

  In the video mode there are moving stripes on the screen and monitor
  turns off occasionally. (Maybe this is just bad behaving monitor, an old
  Samsung TV) It became got good after I run
  
  xrandr --output HDMI-1 --mode 1920x1080
  
  (and --auto for each other video output) in /usr/local/bin/monitor-
  config.sh and I put
  
  display-setup-script=/usr/local/bin/monitor-config.sh
  
- in lightdm configuration, except that screens partly overlap even if the
+ in LightDM configuration, except that screens partly overlap even if the
  other monitor is right of other. Couldn't they be mirroring each other?
+ Anyway, I can make it work decently as extended desktop if I use --left-
+ of or --right-of.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: lightdm 1.30.0-0ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13
  Uname: Linux 5.3.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Thu Feb  6 13:35:12 2020
  InstallationDate: Installed on 2019-12-05 (62 days ago)
  InstallationMedia: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  LightdmConfig:
   [Seat:*]
   display-setup-script=/usr/local/bin/monitor-config.sh
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  Badly working video mode on the greeter

Status in lightdm package in Ubuntu:
  New

Bug description:
  In the video mode there are moving stripes on the screen and monitor
  turns off occasionally. (Maybe this is just bad behaving monitor, an
  old Samsung TV) It became got good after I run

  xrandr --output HDMI-1 --mode 1920x1080

  (and --auto for each other video output) in /usr/local/bin/monitor-
  config.sh and I put

  display-setup-script=/usr/local/bin/monitor-config.sh

  in LightDM configuration, except that screens partly overlap even if
  the other monitor is right of other. Couldn't they be mirroring each
  other? Anyway, I can make it work decently as extended desktop if I
  use --left-of or --right-of.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: lightdm 1.30.0-0ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13
  Uname: Linux 5.3.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Thu Feb  6 13:35:12 2020
  InstallationDate: Installed on 2019-12-05 (62 days ago)
  InstallationMedia: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  LightdmConfig:
   [Seat:*]
   display-setup-script=/usr/local/bin/monitor-config.sh
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1862162] Re: Badly working video mode on the greeter

2020-02-07 Thread Jarno Suni

** Description changed:

  In the video mode there are moving stripes on the screen and monitor
- turns off occasionally. (Maybe this is bad behaving monitor, an old
- Samsung TV) It got good after I run
+ turns off occasionally. (Maybe this is just bad behaving monitor, an old
+ Samsung TV) It became got good after I run
  
- xrandr --output HDMI-1 --auto
+ xrandr --output HDMI-1 --mode 1920x1080
  
- (and similar for each other video output) in /usr/local/bin/monitor-
+ (and --auto for each other video output) in /usr/local/bin/monitor-
  config.sh and I put
  
  display-setup-script=/usr/local/bin/monitor-config.sh
  
- in lightdm configuration.
+ in lightdm configuration, except that screens partly overlap even if the
+ other monitor is right of other. Couldn't they be mirroring each other?
  
  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: lightdm 1.30.0-0ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13
  Uname: Linux 5.3.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Thu Feb  6 13:35:12 2020
  InstallationDate: Installed on 2019-12-05 (62 days ago)
  InstallationMedia: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  LightdmConfig:
-  [Seat:*]
-  display-setup-script=/usr/local/bin/monitor-config.sh
+  [Seat:*]
+  display-setup-script=/usr/local/bin/monitor-config.sh
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  Badly working video mode on the greeter

Status in lightdm package in Ubuntu:
  New

Bug description:
  In the video mode there are moving stripes on the screen and monitor
  turns off occasionally. (Maybe this is just bad behaving monitor, an
  old Samsung TV) It became got good after I run

  xrandr --output HDMI-1 --mode 1920x1080

  (and --auto for each other video output) in /usr/local/bin/monitor-
  config.sh and I put

  display-setup-script=/usr/local/bin/monitor-config.sh

  in LightDM configuration, except that screens partly overlap even if
  the other monitor is right of other. Couldn't they be mirroring each
  other? Anyway, I can make it work decently as extended desktop if I
  use --left-of or --right-of.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: lightdm 1.30.0-0ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13
  Uname: Linux 5.3.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Thu Feb  6 13:35:12 2020
  InstallationDate: Installed on 2019-12-05 (62 days ago)
  InstallationMedia: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  LightdmConfig:
   [Seat:*]
   display-setup-script=/usr/local/bin/monitor-config.sh
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1853357] Re: display (whole computer?) hangs when I attempt to use DisplayLink with Wayland

What comes to the EVDI dkms version, the official DisplayLink driver
5.2.14 package contains EVDI 1.6.2. The release notes just write it out
as v1.5.0-r1-76 (a1e1135), but that sha1 refers to 1.6.2 and the code
between the official package and the 1.6.2 tag for the kernel module is
identical. So I think the ones shipped in Ubuntu/Debian are older than
the DisplayLink's own.

I see that the Ubuntu evdi 1.6.0+dfsg-1ubuntu2 (the version I see in
Ubuntu 19.10) contains some patches on top of 1.6.0, but none of those
are GNOME Wayland related fixes found in 1.6.2. OTOH, it seems 1.6.2
already contains all the patches that Ubuntu adds.

This probably makes no difference to your issues, but I'd prefer to
stick to the DisplayLink official version to avoid confusion on what is
actually being tested.

1.6.3 and 1.6.4 exist too, they have one patch each to libevdi0. I
cannot off-hand say if those might be relevant or not.

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

Title:
  display (whole computer?) hangs when I attempt to use DisplayLink with
  Wayland

Status in Mutter:
  New
Status in mutter package in Ubuntu:
  Incomplete
Status in mutter source package in Eoan:
  Confirmed
Status in mutter source package in Focal:
  Incomplete

Bug description:
  [ Impact ]

  I am using the DisplayLink driver for Ubuntu provided at
  https://www.displaylink.com/downloads/ubuntu

  DisplayLink is working under Xorg, but when I try to use it under
  Wayland my whole display hangs and I can't even switch to a different
  VT with Ctrl-Alt-F3 so I think maybe the whole computer is hung? Not
  certain.

  [ Test case ]

  - Install DisplayLink drivers
  - Start GNOME Shell in wayland mode
  - Connect to a display-link dock
  - Expect the shell to work properly and be visible in the external device

  [ Regression potential ]

  Wayland session won't work even for standard drm devices

  
  

  I am using the DisplayLink driver for Ubuntu provided at
  https://www.displaylink.com/downloads/ubuntu, which I think is the
  only way to get DisplayLink fully working under Ubuntu? That is,
  DisplayLink didn't work when I installed the evdi-dkms and libevdi0
  Ubuntu packages, and I couldn't find any other packages that might be
  relevant (did I miss something?) so as far as I can tell the only way
  to get everything that's needed is from displaylink.com.

  I'm reporting this issue while logged in under Xorg because I can't
  report it when logged in with my DisplayLink monitors plugged in under
  Wayland, for obvious reasons. :-/

  ProblemType: BugDistroRelease: Ubuntu 19.10
  Package: mutter 3.34.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7
  Uname: Linux 5.3.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Nov 20 14:08:21 2019
  InstallationDate: Installed on 2019-09-12 (69 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 
(20190416)SourcePackage: mutter
  UpgradeStatus: Upgraded to eoan on 2019-09-20 (61 days ago)
  modified.conffile..etc.apport.crashdb.conf: [modified]
  mtime.conffile..etc.apport.crashdb.conf: 2019-10-23T16:51:18.143596

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

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

[Desktop-packages] [Bug 1853768] Re: Qt apps, like kid3-qt, which uses legacy icons "document-*.png", show them as normal document icon under Yaru theme

2020-02-07 Thread Dmitry Shachnev

In Focal this is now fixed in yaru-theme 20.04.1.

** No longer affects: qtbase-opensource-src (Ubuntu)

** Also affects: yaru-theme (Ubuntu Eoan)
   Importance: Undecided
   Status: New

** Changed in: yaru-theme (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  Qt apps, like kid3-qt, which uses legacy icons "document-*.png", show
  them as normal document icon under Yaru theme

Status in Yaru Theme:
  Fix Released
Status in yaru-theme package in Ubuntu:
  Fix Released
Status in yaru-theme source package in Eoan:
  New

Bug description:
  Qt apps, like kid3-qt, which uses these legacy icons:

  document-open.png
  document-open-recent.png
  document-save.png
  document-save-as.png
  document-revert.png
  document-import.png
  document-export.png

  The icons are all shown as the same normal document icon under Yaru.

  Qt apps only have a problem with legacy icons starting with
  "document-*" and all other legacy icons are inherited from Humanity
  under Yaru.

  Is there a general solution to force Qt apps to choose the closest
  icon name from Yaru or Humanity?

  Should this bug be issued against upstream Qt?

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

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

[Desktop-packages] [Bug 1553669] Re: Annoying "call from" message when connecting Bose devices

2020-02-07 Thread joes

Can confirm the same behaviour. Using LE-Bose QC35 II on Ubuntu 18.04.4
LTS.

Switching to A2DP stops the "Call from.." prompts on the headphones but
it also then deselects it as an input device. (I think this is correct
for A2DP).

Selecting HSP/HFP or going back and selecting Bose QC35 II as an input
device (which has the effect of selecting HSP/HFP) means the "Call
from.." prompt comes back.

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

Title:
  Annoying "call from" message when connecting Bose devices

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

Bug description:
  I have a bluetooth Bose OE SoundLink working on Kubuntu 15.10 but each
  time I initially connect to listen to an audio or video, I hear an
  annoying "Call from" on my headset. My headset seems to think a
  connection to a phone call is taking place. This is annoying because
  the audio will start to play and after a little while the "call from"
  voice talks over the audio.

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

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

[Desktop-packages] [Bug 1861481] Re: language-options causes live CD sessions to be untranslated

I commented before I saw the previous reply; I'll reply to that now.

The "grep cow" approach breaks the LTSP package and other software that uses a 
COW root.
To check for casper, please `grep -w boot=casper /proc/cmdline` or something 
casper-specific.

In schools, we sometimes have students of various nationalities. They're
not frequent enough to install whole langpacks for them, but they are
frequent enough to configure locales for them (locale-gen).

I do not see any reason to keep the Ubuntu-specific
04_language_handling.patch, when we know that it's causing issues and we
do not know its benefit. Of course it's your call. :)

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

Title:
  language-options causes live CD sessions to be untranslated

Status in accountsservice package in Ubuntu:
  Confirmed
Status in lightdm package in Ubuntu:
  In Progress

Bug description:
  Since Ubuntu 19.10, for all Ubuntu live CDs that use LightDM (e.g.
  MATE and Xubuntu), if a user selects a language in syslinux other than
  those with an included langpack, the session is then untranslated.

  For example, if one boots Ubuntu MATE 20.04 and selects Greek in
  syslinux, he ends up with LANGUAGE=en in the session.

  The chain of events is:
  LightDM has an Ubuntu-specific patch that makes it call 
/usr/share/language-tools/language-options instead of the upstream `locale -a`.
  `locale -a` does list el_GR as a supported locale because casper correctly 
updated the locales.
  But language-options doesn't list el_GR, so it fools LightDM into thinking 
that Greek aren't supported; while they're all there, since e.g. MATE doesn't 
rely on langpacks; mate-panel.mo and mate-calc.mo etc are all there.

  I believe the correct fix would be for language-options to list el_GR
  on live CDs (to merge the output of locale -a in its output).

  Thanks!

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

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

[Desktop-packages] [Bug 1861481] Re: language-options causes live CD sessions to be untranslated

Btw, lightdm doesn't set LANGUAGE at all in Debian; it only sets LANG,
like GDM, and everything works fine.

Gunnar, do you see any issues with just completely dropping your 
04_language_handling.patch?
Or at least this line there:

+session_set_env (session, "LANGUAGE", language);

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

Title:
  language-options causes live CD sessions to be untranslated

Status in accountsservice package in Ubuntu:
  Confirmed
Status in lightdm package in Ubuntu:
  In Progress

Bug description:
  Since Ubuntu 19.10, for all Ubuntu live CDs that use LightDM (e.g.
  MATE and Xubuntu), if a user selects a language in syslinux other than
  those with an included langpack, the session is then untranslated.

  For example, if one boots Ubuntu MATE 20.04 and selects Greek in
  syslinux, he ends up with LANGUAGE=en in the session.

  The chain of events is:
  LightDM has an Ubuntu-specific patch that makes it call 
/usr/share/language-tools/language-options instead of the upstream `locale -a`.
  `locale -a` does list el_GR as a supported locale because casper correctly 
updated the locales.
  But language-options doesn't list el_GR, so it fools LightDM into thinking 
that Greek aren't supported; while they're all there, since e.g. MATE doesn't 
rely on langpacks; mate-panel.mo and mate-calc.mo etc are all there.

  I believe the correct fix would be for language-options to list el_GR
  on live CDs (to merge the output of locale -a in its output).

  Thanks!

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

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

[Desktop-packages] [Bug 1861481] Re: language-options causes live CD sessions to be untranslated

Not sure why you would want to uninstall the language packs for a
language you have configured. You are not supposed to do that. Please
use "Language Support" to manage your languages.

This special thing in LightDM is there for a reason (even if I don't
remember the reason exactly). I'm not ready to propose something which
might have adverse side effects.

Attached please find a debdiff which I think fixes it in live sessions.
The real test can be done only after the new version of lightdm has
reached the daily build ISOs. Would appreciate your confirmation when
that happens.

** Patch added: "lightdm_lp1861481.debdiff"

https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1861481/+attachment/5326214/+files/lightdm_lp1861481.debdiff

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

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

** Changed in: lightdm (Ubuntu)
Assignee: (unassigned) => Gunnar Hjalmarsson (gunnarhj)

** Tags added: patch

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

Title:
language-options causes live CD sessions to be untranslated

Status in accountsservice package in Ubuntu:
Confirmed
Status in lightdm package in Ubuntu:
In Progress

Bug description:
Since Ubuntu 19.10, for all Ubuntu live CDs that use LightDM (e.g.
MATE and Xubuntu), if a user selects a language in syslinux other than
those with an included langpack, the session is then untranslated.

For example, if one boots Ubuntu MATE 20.04 and selects Greek in
syslinux, he ends up with LANGUAGE=en in the session.

The chain of events is:
LightDM has an Ubuntu-specific patch that makes it call
/usr/share/language-tools/language-options instead of the upstream `locale -a`.
`locale -a` does list el_GR as a supported locale because casper correctly
updated the locales.
But language-options doesn't list el_GR, so it fools LightDM into thinking
that Greek aren't supported; while they're all there, since e.g. MATE doesn't
rely on langpacks; mate-panel.mo and mate-calc.mo etc are all there.

I believe the correct fix would be for language-options to list el_GR
on live CDs (to merge the output of locale -a in its output).

Thanks!

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

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

[Desktop-packages] [Bug 1853357] Re: display (whole computer?) hangs when I attempt to use DisplayLink with Wayland

Xorg cursor artifacts all over everywhere: "When I use the evdi module
and library shipped with Ubuntu in 20.04, then DisplayLink works in
Xorg, but it's very glitchy, with cursor artifacts showing up constantly
all over the place on all screens, both DisplayLink and non-
DisplayLink."

I've seen it, it is a know issue and has a workaround: setting "PageFlip" 
"false" in xorg.conf. This link is not exactly about cursor issues but explains 
how to set the PageFlip workaround:
https://support.displaylink.com/knowledgebase/articles/1181623-displaylink-ubuntu-driver-after-recent-x-upgrades

Anyway, that is off-topic too for this issue, so if you want to discuss
that, I again suggest a new report. I don't think I can help with that
though.

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

Title:
  display (whole computer?) hangs when I attempt to use DisplayLink with
  Wayland

Status in Mutter:
  New
Status in mutter package in Ubuntu:
  Incomplete
Status in mutter source package in Eoan:
  Confirmed
Status in mutter source package in Focal:
  Incomplete

Bug description:
  [ Impact ]

  I am using the DisplayLink driver for Ubuntu provided at
  https://www.displaylink.com/downloads/ubuntu

  DisplayLink is working under Xorg, but when I try to use it under
  Wayland my whole display hangs and I can't even switch to a different
  VT with Ctrl-Alt-F3 so I think maybe the whole computer is hung? Not
  certain.

  [ Test case ]

  - Install DisplayLink drivers
  - Start GNOME Shell in wayland mode
  - Connect to a display-link dock
  - Expect the shell to work properly and be visible in the external device

  [ Regression potential ]

  Wayland session won't work even for standard drm devices

  
  

  I am using the DisplayLink driver for Ubuntu provided at
  https://www.displaylink.com/downloads/ubuntu, which I think is the
  only way to get DisplayLink fully working under Ubuntu? That is,
  DisplayLink didn't work when I installed the evdi-dkms and libevdi0
  Ubuntu packages, and I couldn't find any other packages that might be
  relevant (did I miss something?) so as far as I can tell the only way
  to get everything that's needed is from displaylink.com.

  I'm reporting this issue while logged in under Xorg because I can't
  report it when logged in with my DisplayLink monitors plugged in under
  Wayland, for obvious reasons. :-/

  ProblemType: BugDistroRelease: Ubuntu 19.10
  Package: mutter 3.34.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7
  Uname: Linux 5.3.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Nov 20 14:08:21 2019
  InstallationDate: Installed on 2019-09-12 (69 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 
(20190416)SourcePackage: mutter
  UpgradeStatus: Upgraded to eoan on 2019-09-20 (61 days ago)
  modified.conffile..etc.apport.crashdb.conf: [modified]
  mtime.conffile..etc.apport.crashdb.conf: 2019-10-23T16:51:18.143596

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

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

[Desktop-packages] [Bug 1853357] Re: display (whole computer?) hangs when I attempt to use DisplayLink with Wayland

Hi Jonathan,

you seem to be having several different issues here, so I'll try to
address them individually.

First the slow updates, you wrote: "screen updates to the DisplayLink
monitor are Extremely Slow. Like I am typing in a terminal window and it
sometimes takes a second or two between when I type something and when
the results of the typing show up in the terminal. If I move the same
terminal window onto the built-in laptop display the lag goes away."

Slow updates could be one of two things: either the copying of content
to DisplayLink itself is slow, or DisplayLink is showing outdated
content. To understand which one it is, you could try running 'glxgears'
(or any program that animates continuously and reports fps) on the
DisplayLink output and then see if the same slowness with a terminal
still happens.

If the issue is outdated content, then 'glxgears' by forcing repeated
output updates should have the side-effect of making the slowness go
away. Also glxgears should report the expected monitor refresh rate as
fps (for a 60 Hz monitor I'd expect 58 - 60 fps). Your overall system
CPU consumption could be somewhat high, but I would not expect any CPU
core to be maxed out.

If the issue is bad performance in copying the content, then running
glxgears should not make the slowness disappear. Instead, glxgears
should report very low fps, and your system CPU usage may or may not be
high. It would be interesting to know if you have any CPU cores maxed
out busy.

In any case, I think we should talk about the slowness in a new bug
report. Please, point me to it, if you file one.

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

Title:
  display (whole computer?) hangs when I attempt to use DisplayLink with
  Wayland

Status in Mutter:
  New
Status in mutter package in Ubuntu:
  Incomplete
Status in mutter source package in Eoan:
  Confirmed
Status in mutter source package in Focal:
  Incomplete

Bug description:
  [ Impact ]

  I am using the DisplayLink driver for Ubuntu provided at
  https://www.displaylink.com/downloads/ubuntu

  DisplayLink is working under Xorg, but when I try to use it under
  Wayland my whole display hangs and I can't even switch to a different
  VT with Ctrl-Alt-F3 so I think maybe the whole computer is hung? Not
  certain.

  [ Test case ]

  - Install DisplayLink drivers
  - Start GNOME Shell in wayland mode
  - Connect to a display-link dock
  - Expect the shell to work properly and be visible in the external device

  [ Regression potential ]

  Wayland session won't work even for standard drm devices

  
  

  I am using the DisplayLink driver for Ubuntu provided at
  https://www.displaylink.com/downloads/ubuntu, which I think is the
  only way to get DisplayLink fully working under Ubuntu? That is,
  DisplayLink didn't work when I installed the evdi-dkms and libevdi0
  Ubuntu packages, and I couldn't find any other packages that might be
  relevant (did I miss something?) so as far as I can tell the only way
  to get everything that's needed is from displaylink.com.

  I'm reporting this issue while logged in under Xorg because I can't
  report it when logged in with my DisplayLink monitors plugged in under
  Wayland, for obvious reasons. :-/

  ProblemType: BugDistroRelease: Ubuntu 19.10
  Package: mutter 3.34.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7
  Uname: Linux 5.3.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Nov 20 14:08:21 2019
  InstallationDate: Installed on 2019-09-12 (69 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 
(20190416)SourcePackage: mutter
  UpgradeStatus: Upgraded to eoan on 2019-09-20 (61 days ago)
  modified.conffile..etc.apport.crashdb.conf: [modified]
  mtime.conffile..etc.apport.crashdb.conf: 2019-10-23T16:51:18.143596

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

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

[Desktop-packages] [Bug 1861345] Re: Gigabyte x570 Aorus Master with ALC1220 and ESS SABRE 9118 DAC Muted Front speakers 5.1

2020-02-07 Thread Kai-Heng Feng

Can you please try kernel parameter "snd-hda-intel.model=dual-codecs"?

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

Title:
  Gigabyte x570 Aorus Master with ALC1220 and ESS SABRE 9118 DAC Muted
  Front speakers 5.1

Status in alsa-driver package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 18.04.3 LTS
  Kernel 5.5.0
  pulseaudio:
Installed: 1:11.1-1ubuntu7.4
  X570 Aorus Master Motherboard. ALC1220 ESS Sabre sound.

  I have surround 5.1 speakers and the Front Left and Right are Muted.  
  I have to unmute Headphones in alsamixer to hear sound from the front left 
and right speakers is the workaround.

  This step should not be required for speakers 5.1 to work.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  richard2533 F pulseaudio
   /dev/snd/controlC1:  richard2533 F pulseaudio
   /dev/snd/controlC0:  richard2533 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2020-01-28 (2 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  MachineType: Gigabyte Technology Co., Ltd. X570 AORUS MASTER
  Package: linux (not installed)
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-28-generic 
root=UUID=51fe9653-53b0-475f-836e-a1662c6d8b79 ro quiet splash amd_iommu=on 
vt.handoff=1
  ProcVersionSignature: Ubuntu 5.3.0-28.30~18.04.1-generic 5.3.13
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-28-generic N/A
   linux-backports-modules-5.3.0-28-generic  N/A
   linux-firmware1.173.14
  Tags:  bionic
  Uname: Linux 5.3.0-28-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip kvm libvirt lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/06/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F11
  dmi.board.asset.tag: Default string
  dmi.board.name: X570 AORUS MASTER
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF11:bd12/06/2019:svnGigabyteTechnologyCo.,Ltd.:pnX570AORUSMASTER:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570AORUSMASTER:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: X570 AORUS MASTER
  dmi.product.sku: Default string
  dmi.product.version: -CF
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1861345/+subscriptions

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

[Desktop-packages] [Bug 1862331] [NEW] mozilla cert8.db and key3.db are denied by apparmor

2020-02-07 Thread dinar qurbanov

Public bug reported:

libreoffice accesses firefox's cert8.db and key3.db, i have found this from 
apparmor log messages.
i googled "libreoffice cert8.db key3.db" and have found out that seems 
libreoffice does this by design. see 
https://bugs.documentfoundation.org/show_bug.cgi?id=119811 , 
https://weekly-geekly.github.io/articles/357692/index.html . do you agree with 
this? then there should be allow rule, i think. if you do not, then should be a 
comment and / or deny rule.

does libreoffice really need write access to these files? i think it can
potentially add some bad certificates, and some sites would have
verified sign then, while user has not added it to exceptions.

i think if user have not secured his master password, it can be
considered it is ok if some app can access his passwords.

i think this pages also can be helpful:
https://stackoverflow.com/questions/45126738/what-is-cert8-db-and-key3
-db-file , https://developer.mozilla.org/en-
US/docs/Mozilla/Projects/NSS/tools/NSS_Tools_certutil , these are found
by googling "cert8.db key3.db". this also can be helpful:
https://en.wikipedia.org/wiki/Public_key_certificate .

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

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

Title:
  mozilla cert8.db and key3.db are denied by apparmor

Status in libreoffice package in Ubuntu:
  New

Bug description:
  libreoffice accesses firefox's cert8.db and key3.db, i have found this from 
apparmor log messages.
  i googled "libreoffice cert8.db key3.db" and have found out that seems 
libreoffice does this by design. see 
https://bugs.documentfoundation.org/show_bug.cgi?id=119811 , 
https://weekly-geekly.github.io/articles/357692/index.html . do you agree with 
this? then there should be allow rule, i think. if you do not, then should be a 
comment and / or deny rule.

  does libreoffice really need write access to these files? i think it
  can potentially add some bad certificates, and some sites would have
  verified sign then, while user has not added it to exceptions.

  i think if user have not secured his master password, it can be
  considered it is ok if some app can access his passwords.

  i think this pages also can be helpful:
  https://stackoverflow.com/questions/45126738/what-is-cert8-db-and-key3
  -db-file , https://developer.mozilla.org/en-
  US/docs/Mozilla/Projects/NSS/tools/NSS_Tools_certutil , these are
  found by googling "cert8.db key3.db". this also can be helpful:
  https://en.wikipedia.org/wiki/Public_key_certificate .

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

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

[Desktop-packages] [Bug 1855757] Re: [nvidia] Background image corrupted after standby

2020-02-07 Thread Julien Olivier

By the way, I don't know what happened but I don't have the bug any
more. Has there been any update recently?

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

Title:
  [nvidia] Background image corrupted after standby

Status in gnome-shell package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  Looks similar to
  https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1809407

  When the computer goes to standby, the background image becomes
  corrupted.

  I am able to fix by "killall Xorg" , change the background image
  (settings > background) and restart.  Haven't tried login logout.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Uname: Linux 5.3.0-24-generic x86_64
  NonfreeKernelModules: nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  340.107  Thu May 24 21:54:01 
PDT 2018
   GCC version:  gcc version 9.2.1 20191008 (Ubuntu 9.2.1-9ubuntu2)
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Dec  9 10:58:35 2019
  DistUpgraded: Fresh install
  DistroCodename: eoan
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia-340, 340.107, 5.3.0-23-generic, x86_64: installed
   nvidia-340, 340.107, 5.3.0-24-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation GT215M [GeForce GTS 360M] [10de:0cb1] (rev a2) (prog-if 
00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. GT215M [GeForce GTS 360M] [1043:203c]
  InstallationDate: Installed on 2019-11-29 (10 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: ASUSTek Computer Inc. G60JX
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic 
root=UUID=65117975-c95f-4406-a7cf-da912cda0e70 ro
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/25/2009
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 204
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: G60JX
  dmi.board.vendor: PEGATRON CORPORATION
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: PEGATRON Computer Inc.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr204:bd12/25/2009:svnASUSTekComputerInc.:pnG60JX:pvr1.0:rvnPEGATRONCORPORATION:rnG60JX:rvr1.0:cvnPEGATRONComputerInc.:ct10:cvr1.0:
  dmi.product.family: PEGA Family
  dmi.product.name: G60JX
  dmi.product.sku: 0
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTek Computer Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
  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 2:1.20.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Desktop-packages] [Bug 1856861] Re: Firefox 73 require C++17, not available in xenial

2020-02-07 Thread Olivier Tilloy

Bumping the importance as firefox 73.0 is now in release candidate
phase.

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

Title:
  Firefox 73 require C++17, not available in xenial

Status in firefox package in Ubuntu:
  Triaged

Bug description:
  Firefox trunk, to become version 73.0 in February 2020, has bumped its
  C++ requirement to C++17
  (https://bugzilla.mozilla.org/show_bug.cgi?id=1560664).

  This requires a more recent version (>= 7) of libstdc++6 than what is
  currently available in xenial (5.4.0-6ubuntu1~16.04.12).

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

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

[Desktop-packages] [Bug 1856861] Re: Firefox 73 require C++17, not available in xenial

2020-02-07 Thread Olivier Tilloy

Useful information that confirms that we definitely need gcc-7
backported to xenial: https://gcc.gnu.org/projects/cxx-
status.html#cxx17.

** Changed in: firefox (Ubuntu)
   Importance: High => Critical

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

Title:
  Firefox 73 require C++17, not available in xenial

Status in firefox package in Ubuntu:
  Triaged

Bug description:
  Firefox trunk, to become version 73.0 in February 2020, has bumped its
  C++ requirement to C++17
  (https://bugzilla.mozilla.org/show_bug.cgi?id=1560664).

  This requires a more recent version (>= 7) of libstdc++6 than what is
  currently available in xenial (5.4.0-6ubuntu1~16.04.12).

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

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

[Desktop-packages] [Bug 1745345] Re: Xorg assert failure: Xorg: /usr/include/xorg/privates.h:122: dixGetPrivateAddr: Assertion `key->initialized' failed.

2020-02-07 Thread intherye

This also happened on a 20.04 Xubuntu 64-bit VM in Qemu/KVM: Xorg
crashing at login, next login works.

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

Title:
  Xorg assert failure: Xorg: /usr/include/xorg/privates.h:122:
  dixGetPrivateAddr: Assertion `key->initialized' failed.

Status in gstreamer-vaapi package in Ubuntu:
  Invalid
Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  
  It happened after upgrade to bionic, in the first login, after logon screen.
  Instead of opening the desktop area, gave the error. I had to do hard reset 
to be able to use X.
  After hard reset showed the same error but after a while it entered desktop.

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: xserver-xorg-core 2:1.19.5-0ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-31.34-generic 4.13.13
  Uname: Linux 4.13.0-31-generic x86_64
  ApportVersion: 2.20.8-0ubuntu6
  Architecture: amd64
  AssertionMessage: Xorg: /usr/include/xorg/privates.h:122: dixGetPrivateAddr: 
Assertion `key->initialized' failed.
  CompositorRunning: None
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Thu Jan 25 10:09:41 2018
  DistUpgraded: 2018-01-25 02:34:06,581 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py ([Errno 2] Ficheiro ou directoria inexistente: 
'./xorg_fix_proprietary.py': './xorg_fix_proprietary.py')
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExecutablePath: /usr/lib/xorg/Xorg
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA 
controller])
 Subsystem: Toshiba America Info Systems HD Graphics 5500 [1179:f920]
 Subsystem: Toshiba America Info Systems Radeon R7 M260 [1179:f923]
  InstallationDate: Installed on 2018-01-07 (17 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: TOSHIBA SATELLITE L50-B
  ProcCmdline: /usr/lib/xorg/Xorg vt1 -displayfd 3 -auth 
/run/user/121/gdm/Xauthority -background none -noreset -keeptty -verbose 3
  ProcEnviron:
   LANGUAGE=pt:pt_BR:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pt_PT.UTF-8
   SHELL=/bin/false
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-31-generic 
root=UUID=7985a6e4-e304-4f48-97b5-9111dc373a81 ro quiet splash vt.handoff=7
  Signal: 6
  SourcePackage: xorg-server
  StacktraceTop:
   __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51
   __GI_abort () at abort.c:90
   __assert_fail_base (fmt=, 
assertion=assertion@entry=0x7f549469ed25 "key->initialized", 
file=file@entry=0x7f549469ed08 "/usr/include/xorg/privates.h", 
line=line@entry=122, function=function@entry=0x7f549469fd00 
"dixGetPrivateAddr") at assert.c:92
   __GI___assert_fail (assertion=0x7f549469ed25 "key->initialized", 
file=0x7f549469ed08 "/usr/include/xorg/privates.h", line=122, 
function=0x7f549469fd00 "dixGetPrivateAddr") at assert.c:101
   ?? () from /usr/lib/xorg/modules/drivers/amdgpu_drv.so
  Title: Xorg assert failure: Xorg: /usr/include/xorg/privates.h:122: 
dixGetPrivateAddr: Assertion `key->initialized' failed.
  UpgradeStatus: Upgraded to bionic on 2018-01-25 (0 days ago)
  UserGroups:
   
  dmi.bios.date: 01/21/2015
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 2.10
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Type2 - Board Product Name1
  dmi.board.vendor: Type2 - Board Vendor Name1
  dmi.board.version: Type2 - Board Version
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: OEM Chassis ManuFacturer
  dmi.chassis.version: OEM Chassis Version
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr2.10:bd01/21/2015:svnTOSHIBA:pnSATELLITEL50-B:pvrPSKTNE-01U011EP:rvnType2-BoardVendorName1:rnType2-BoardProductName1:rvrType2-BoardVersion:cvnOEMChassisManuFacturer:ct10:cvrOEMChassisVersion:
  dmi.product.family: INVALID
  dmi.product.name: SATELLITE L50-B
  dmi.product.version: PSKTNE-01U011EP
  dmi.sys.vendor: TOSHIBA
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.89-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu2
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu2
  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 N/A
  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/gstreamer-vaapi/+bug/1745345/+subscriptions

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

[Desktop-packages] [Bug 1861558] Re: Snap 'ed applicaitons have garbage on top of the window Close [x] button

2020-02-07 Thread Maciej Borzecki

Nonetheless it isn't clear whether it's a snapd problem or the actual
libraries. Switching to confirmed in snapd, but needs investigation from
desktop team too.

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

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

Title:
  Snap 'ed applicaitons have garbage on top of the window Close [x]
  button

Status in adwaita-icon-theme package in Ubuntu:
  New
Status in gnome-themes-extra package in Ubuntu:
  New
Status in humanity-icon-theme package in Ubuntu:
  New
Status in snapd package in Ubuntu:
  Confirmed
Status in ubuntu-mono package in Ubuntu:
  New

Bug description:
  Steps to reproduce:
  1. Have Ubuntu 19.10 installed
  2. Install GNOME application as a Snap - for example with

  sudo snap install gedit gnome-calculator

  3. Open GNOME Tweaks -> Appearance tab, then switch Icon set to the
  one of the following:

  * Adwaita
  * DMZ-Black
  * DMZ-White
  * hicolor
  * HighContrast
  * Humanity
  * Humanity-Dark
  * LoginIcons

  For example - Adwaita theme with Adwaita icon set.

  4. Open GNOME Calculator as a Snap application:

 /snap/bin/gnome-calculator

  Expected result:

  * GNOME Calculator looks as any other GTK application

  Actual result:

  * GNOME Calculator has garbage on top of the window Close [x] button

  ---

  Notes: 
  1. Problem was first seen on AskUbuntu - https://askubuntu.com/q/1206868
  2. one can use the script below to check all possible Theme<->Icon 
combinations:

  ```
  #!/bin/bash

  DISPLAY=:0

  for t in $(ls -1 /usr/share/themes/)
  do 
for i in $(ls -1 /usr/share/icons/)
do

  echo -e "\nTheme: $t, Icons: $i\n"

gsettings set org.gnome.desktop.interface gtk-theme "$t"
gsettings set org.gnome.desktop.interface icon-theme "$i"

  /snap/bin/gnome-calculator

#read -r -s -p "Press  for next theme"   
done
  done

  ```

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: snapd 2.41+19.10.1
  ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13
  Uname: Linux 5.3.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Feb  1 17:55:09 2020
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: snapd
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/adwaita-icon-theme/+bug/1861558/+subscriptions

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

[Desktop-packages] [Bug 1861558] Re: Snap 'ed applicaitons have garbage on top of the window Close [x] button

2020-02-07 Thread Maciej Borzecki

I've seen this happen occasionally with snaps on Arch too.

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

Title:
  Snap 'ed applicaitons have garbage on top of the window Close [x]
  button

Status in adwaita-icon-theme package in Ubuntu:
  New
Status in gnome-themes-extra package in Ubuntu:
  New
Status in humanity-icon-theme package in Ubuntu:
  New
Status in snapd package in Ubuntu:
  Confirmed
Status in ubuntu-mono package in Ubuntu:
  New

Bug description:
  Steps to reproduce:
  1. Have Ubuntu 19.10 installed
  2. Install GNOME application as a Snap - for example with

  sudo snap install gedit gnome-calculator

  3. Open GNOME Tweaks -> Appearance tab, then switch Icon set to the
  one of the following:

  * Adwaita
  * DMZ-Black
  * DMZ-White
  * hicolor
  * HighContrast
  * Humanity
  * Humanity-Dark
  * LoginIcons

  For example - Adwaita theme with Adwaita icon set.

  4. Open GNOME Calculator as a Snap application:

 /snap/bin/gnome-calculator

  Expected result:

  * GNOME Calculator looks as any other GTK application

  Actual result:

  * GNOME Calculator has garbage on top of the window Close [x] button

  ---

  Notes: 
  1. Problem was first seen on AskUbuntu - https://askubuntu.com/q/1206868
  2. one can use the script below to check all possible Theme<->Icon 
combinations:

  ```
  #!/bin/bash

  DISPLAY=:0

  for t in $(ls -1 /usr/share/themes/)
  do 
for i in $(ls -1 /usr/share/icons/)
do

  echo -e "\nTheme: $t, Icons: $i\n"

gsettings set org.gnome.desktop.interface gtk-theme "$t"
gsettings set org.gnome.desktop.interface icon-theme "$i"

  /snap/bin/gnome-calculator

#read -r -s -p "Press  for next theme"   
done
  done

  ```

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: snapd 2.41+19.10.1
  ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13
  Uname: Linux 5.3.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Feb  1 17:55:09 2020
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: snapd
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/adwaita-icon-theme/+bug/1861558/+subscriptions

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

[Desktop-packages] [Bug 1796437] Re: [nouveau] Xorg crashes with assertion failure "key->initialized" in dixGetPrivateAddr() from dixLookupPrivate() from DRI2Authenticate()

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

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

** Changed in: gstreamer-vaapi (Ubuntu)
   Status: New => Confirmed

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

Title:
  [nouveau] Xorg crashes with assertion failure "key->initialized" in
  dixGetPrivateAddr() from dixLookupPrivate() from DRI2Authenticate()

Status in gstreamer-vaapi package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  Went to the menu button in upper left corner. Attempted to open Budgie
  Welcome and the X11 session crashed. About 4 lines of error code were
  displayed for a few seconds then the login screen appeared.

  Description:  Ubuntu Cosmic Cuttlefish (development branch)
  Release:  18.10
  budgie-welcome:
Installed: (none)
Candidate: 0.6.1
Version table:
   0.6.1 500
  500 http://us.archive.ubuntu.com/ubuntu cosmic/universe amd64 Packages
  500 http://us.archive.ubuntu.com/ubuntu cosmic/universe i386 Packages

  Seems to not be installed on a fresh install. So solved but needs
  fixing?

  ProblemType: Crash
  DistroRelease: Ubuntu 18.10
  Package: xserver-xorg-core 2:1.20.1-3ubuntu2
  ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7
  Uname: Linux 4.18.0-8-generic x86_64
  ApportVersion: 2.20.10-0ubuntu11
  Architecture: amd64
  AssertionMessage: Xorg: ../../../../../../include/privates.h:121: 
dixGetPrivateAddr: Assertion `key->initialized' failed.
  BootLog:
   [[0;32m  OK  [0m] Stopped Snappy daemon.
Starting Snappy daemon...
  CompositorRunning: None
  CrashCounter: 1
  Date: Fri Oct  5 20:36:30 2018
  DistUpgraded: Fresh install
  DistroCodename: cosmic
  DistroVariant: ubuntu
  ExecutablePath: /usr/lib/xorg/Xorg
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] [10de:1b06] (rev a1) (prog-if 
00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. GP102 [GeForce GTX 1080 Ti] [1043:85e4]
  InstallationDate: Installed on 2018-10-06 (0 days ago)
  InstallationMedia: Ubuntu-Budgie 18.10 "Cosmic Cuttlefish" - Beta amd64 
(20181005)
  MachineType: System manufacturer System Product Name
  ProcCmdline: /usr/lib/xorg/Xorg -core :0 -seat seat0 -auth 
/var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
  ProcEnviron: PATH=(custom, no user)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-8-generic 
root=UUID=21545d40-8bcb-45b5-b710-8521590b95a5 ro quiet splash vt.handoff=1
  Signal: 6
  SourcePackage: xorg-server
  StacktraceTop:
   __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
   __GI_abort () at abort.c:79
   __assert_fail_base (fmt=0x7f29afb85858 "%s%s%s:%u: %s%sAssertion `%s' 
failed.\n%n", assertion=0x55c50dca64bb "key->initialized", file=0x55c50dcaa9b0 
"../../../../../../include/privates.h", line=121, function=) at 
assert.c:92
   __GI___assert_fail (assertion=0x55c50dca64bb "key->initialized", 
file=0x55c50dcaa9b0 "../../../../../../include/privates.h", line=121, 
function=0x55c50dccc0c0 "dixGetPrivateAddr") at assert.c:101
   ?? ()
  Title: Xorg assert failure: Xorg: ../../../../../../include/privates.h:121: 
dixGetPrivateAddr: Assertion `key->initialized' failed.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 03/14/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1301
  dmi.board.asset.tag: Default string
  dmi.board.name: MAXIMUS IX FORMULA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1301:bd03/14/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnMAXIMUSIXFORMULA:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.94-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.1-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1build1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gstreamer-vaapi/+bug/1796437/+subscriptions

-- 
Mailing

[Desktop-packages] [Bug 1861481] Re: language-options causes live CD sessions to be untranslated

I mean that if, on a normal 20.04 installation, I uninstall the el langpack, 
then
1) If I'm using GDM, universe apps show Greek,
2) If I'm using LightDM, universe apps show English (this one regressed in 
19.10).

If we're modifying LightDM, I suggest to modify LightDM to not set LANGUAGE at 
all, not just in live CDs.
This is what GDM does and it works fine everywhere.

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

Title:
  language-options causes live CD sessions to be untranslated

Status in accountsservice package in Ubuntu:
  Confirmed
Status in lightdm package in Ubuntu:
  New

Bug description:
  Since Ubuntu 19.10, for all Ubuntu live CDs that use LightDM (e.g.
  MATE and Xubuntu), if a user selects a language in syslinux other than
  those with an included langpack, the session is then untranslated.

  For example, if one boots Ubuntu MATE 20.04 and selects Greek in
  syslinux, he ends up with LANGUAGE=en in the session.

  The chain of events is:
  LightDM has an Ubuntu-specific patch that makes it call 
/usr/share/language-tools/language-options instead of the upstream `locale -a`.
  `locale -a` does list el_GR as a supported locale because casper correctly 
updated the locales.
  But language-options doesn't list el_GR, so it fools LightDM into thinking 
that Greek aren't supported; while they're all there, since e.g. MATE doesn't 
rely on langpacks; mate-panel.mo and mate-calc.mo etc are all there.

  I believe the correct fix would be for language-options to list el_GR
  on live CDs (to merge the output of locale -a in its output).

  Thanks!

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

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

[Desktop-packages] [Bug 1855757] Re: [nvidia] Background image corrupted after standby

2020-02-07 Thread Daniel van Vugt

Yeah I would usually recommend a supported Nvidia driver instead of
Nouveau. Just trying to avoid this bug...

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

Title:
  [nvidia] Background image corrupted after standby

Status in gnome-shell package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  Looks similar to
  https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1809407

  When the computer goes to standby, the background image becomes
  corrupted.

  I am able to fix by "killall Xorg" , change the background image
  (settings > background) and restart.  Haven't tried login logout.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Uname: Linux 5.3.0-24-generic x86_64
  NonfreeKernelModules: nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  340.107  Thu May 24 21:54:01 
PDT 2018
   GCC version:  gcc version 9.2.1 20191008 (Ubuntu 9.2.1-9ubuntu2)
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Dec  9 10:58:35 2019
  DistUpgraded: Fresh install
  DistroCodename: eoan
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia-340, 340.107, 5.3.0-23-generic, x86_64: installed
   nvidia-340, 340.107, 5.3.0-24-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation GT215M [GeForce GTS 360M] [10de:0cb1] (rev a2) (prog-if 
00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. GT215M [GeForce GTS 360M] [1043:203c]
  InstallationDate: Installed on 2019-11-29 (10 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: ASUSTek Computer Inc. G60JX
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic 
root=UUID=65117975-c95f-4406-a7cf-da912cda0e70 ro
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/25/2009
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 204
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: G60JX
  dmi.board.vendor: PEGATRON CORPORATION
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: PEGATRON Computer Inc.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr204:bd12/25/2009:svnASUSTekComputerInc.:pnG60JX:pvr1.0:rvnPEGATRONCORPORATION:rnG60JX:rvr1.0:cvnPEGATRONComputerInc.:ct10:cvr1.0:
  dmi.product.family: PEGA Family
  dmi.product.name: G60JX
  dmi.product.sku: 0
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTek Computer Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
  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 2:1.20.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Desktop-packages] [Bug 1861481] Re: language-options causes live CD sessions to be untranslated