[Desktop-packages] [Bug 2085772] Re: high cpu usage

[Matt Newbound]

Thanks for the response. 
How come I've only noticed this running Ubuntu 24 or Debian 12 with gnome and 
never on any version of windows I have ran on my mini server for the last 8 
years?

I would expect high CPU usage when doing complex operations or graphical
activities, but this is just the desktop and settings screens.

Anything I can do? Tried one pcie graphics card in there and it didn't
help.

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

Title:
  high cpu usage

Status in gnome-shell package in Ubuntu:
  Opinion

Bug description:
  gnome-shell is running high cpu on a new install either via ILO
  connection or RDP connection.

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: gnome-shell 46.0-0ubuntu6~24.04.4
  ProcVersionSignature: Ubuntu 6.8.0-47.47-generic 6.8.12
  Uname: Linux 6.8.0-47-generic x86_64
  ApportVersion: 2.28.1-0ubuntu3.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct 28 12:43:29 2024
  DisplayManager: gdm3
  InstallationDate: Installed on 2024-10-28 (0 days ago)
  InstallationMedia: Ubuntu 24.04.1 LTS "Noble Numbat" - Release amd64 
(20240827.1)
  RelatedPackageVersions: mutter-common 46.2-1ubuntu0.24.04.1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Desktop-packages] [Bug 2085772] [NEW] high cpu usage

[Matt Newbound]

Public bug reported:

gnome-shell is running high cpu on a new install either via ILO
connection or RDP connection.

ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: gnome-shell 46.0-0ubuntu6~24.04.4
ProcVersionSignature: Ubuntu 6.8.0-47.47-generic 6.8.12
Uname: Linux 6.8.0-47-generic x86_64
ApportVersion: 2.28.1-0ubuntu3.1
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Mon Oct 28 12:43:29 2024
DisplayManager: gdm3
InstallationDate: Installed on 2024-10-28 (0 days ago)
InstallationMedia: Ubuntu 24.04.1 LTS "Noble Numbat" - Release amd64 
(20240827.1)
RelatedPackageVersions: mutter-common 46.2-1ubuntu0.24.04.1
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug noble wayland-session

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

Title:
  high cpu usage

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  gnome-shell is running high cpu on a new install either via ILO
  connection or RDP connection.

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: gnome-shell 46.0-0ubuntu6~24.04.4
  ProcVersionSignature: Ubuntu 6.8.0-47.47-generic 6.8.12
  Uname: Linux 6.8.0-47-generic x86_64
  ApportVersion: 2.28.1-0ubuntu3.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct 28 12:43:29 2024
  DisplayManager: gdm3
  InstallationDate: Installed on 2024-10-28 (0 days ago)
  InstallationMedia: Ubuntu 24.04.1 LTS "Noble Numbat" - Release amd64 
(20240827.1)
  RelatedPackageVersions: mutter-common 46.2-1ubuntu0.24.04.1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Desktop-packages] [Bug 2055032] Re: SEG/11 in Wayland _st_theme_get_matched_properties()

[Matt Baker]

Thank you. It turned out to be faulty RAM.

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

Title:
  SEG/11 in Wayland _st_theme_get_matched_properties()

Status in gnome-shell package in Ubuntu:
  Invalid

Bug description:
  Crashed after unlocking session from being away for a couple days.

  Crash report ID is https://errors.ubuntu.com/oops/c81ddc34-d487-11ee-
  ba77-fa163e171f02

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


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

[Desktop-packages] [Bug 2055032] [NEW] SEG/11 in Wayland _st_theme_get_matched_properties()

[Matt Baker]

Public bug reported:

Crashed after unlocking session from being away for a couple days.

Crash report ID is c81ddc34-d487-11ee-ba77-fa163e171f02

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

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

Title:
  SEG/11 in Wayland _st_theme_get_matched_properties()

Status in mutter package in Ubuntu:
  New

Bug description:
  Crashed after unlocking session from being away for a couple days.

  Crash report ID is c81ddc34-d487-11ee-ba77-fa163e171f02

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


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

[Desktop-packages] [Bug 2028698] Re: desktop freezes when copying file to android phone

[Matt Raines]

Seems to be any file with a colon (:) character in the filename.

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

Title:
  desktop freezes when copying file to android phone

Status in gvfs package in Ubuntu:
  Confirmed

Bug description:
  If you try to copy a file named a:b.m4b using the nautilus file
  manager to a USB-connected Android phone in MTP mode, the desktop will
  freeze until you disconnect the USB cable. Then you'll get an error
  from nautilus:

  "Fehler beim Kopieren von »a:b.m4b«.
  Beim Kopieren der Datei nach mtp://Google_Pixel_7_291...
  mer%Speicher/Audiobooks ist ein Fehler aufgetreten

  libmtp-Fehler: Could not send object."

  This happens when the file to be copied contains the colon symbol :

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gvfs-backends 1.48.2-0ubuntu1
  ProcVersionSignature: Ubuntu 5.19.0-50.50-generic 5.19.17
  Uname: Linux 5.19.0-50-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jul 25 21:46:45 2023
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-focal-amd64-20200502-85
  InstallationDate: Installed on 2021-08-20 (704 days ago)
  InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 
20200502-05:58
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/zsh
  SourcePackage: gvfs
  UpgradeStatus: Upgraded to jammy on 2022-09-10 (318 days ago)

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


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

[Desktop-packages] [Bug 1961508] Re: Dock displaying over window after resuming from blank screen

[Matt Wette]

Adding screenshot from 23.04

** Attachment added: "evince_under_dock.png"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1961508/+attachment/5676341/+files/evince_under_dock.png

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

Title:
  Dock displaying over window after resuming from blank screen

Status in Dash to dock:
  Unknown
Status in Mutter:
  New
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  Won't Fix
Status in mutter package in Ubuntu:
  In Progress
Status in gnome-desktop package in Fedora:
  Confirmed

Bug description:
  I have Blank Screen set to happen after 2 minutes of inactivity.

  When resuming from a Blank Screen (by moving the mouse or touching the
  keyboard), the Dock is displayed over the top of the current program.

  To get it back to normal I need to click "Restore Down" on the current
  programs window and then "Maximize" so that the Dock no longer
  overlaps it.

  (Note: I have Auto-hide dock turned off.)

  This only happens sometimes. I can't reproduce the bug it every time.

  -

  1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> 
About Ubuntu
  - Ubuntu 21.10

  2) The version of the package you are using, via 'apt-cache policy pkgname' 
or by checking in Software Center
  - Not sure (I guess the Dock is part of the Gnome interface?)

  3) What you expected to happen
  - Dock should not overlap the current program on resume from screen blank.

  4) What happened instead
  - The Dock overlaps the current program on resume from screen blank.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 21.10
  InstallationDate: Installed on 2022-02-18 (24 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  Package: gnome-shell-extension-ubuntu-dock
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.13.0-35.40-generic 5.13.19
  RelatedPackageVersions: mutter-common 40.5-1ubuntu3~21.10.1
  Tags:  wayland-session impish
  Uname: Linux 5.13.0-35-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  --- 
  ProblemType: Bug
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 22.10
  InstallationDate: Installed on 2022-02-18 (328 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  Package: mutter
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.19.0-28.29-generic 5.19.17
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions: mutter-common 43.0-1ubuntu4
  Tags: wayland-session third-party-packages kinetic
  Uname: Linux 5.19.0-28-generic x86_64
  UpgradeStatus: Upgraded to kinetic on 2022-10-25 (79 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/dash-to-dock/+bug/1961508/+subscriptions


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

[Desktop-packages] [Bug 2021407] [NEW] maximized evince shadowed by dock

[Matt Wette]

Public bug reported:

Ubuntu 23.04, w/ wayland, evince 44.1, all updates applied to date
(05/27/2023)

I'm not sure what causes it but occasionally I find my maximized evince has 
expanded under the dock.
My current workaround is to un-maximize (i.e., double-click titlebar), then 
maximime (double-click titlebar).

I typically keep a maximized evince of certain document open all the
time.  This hiccup occurs maybe once or twice a day.

This occured with 22.10 also, btw.

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

** Description changed:

  Ubuntu 23.04, w/ wayland, evince 44.1, all updates applied to date
  (05/27/2023)
  
  I'm not sure what causes it but occasionally I find my maximized evince has 
expanded under the dock.
  My current workaround is to un-maximize (i.e., double-click titlebar), then 
maximime (double-click titlebar).
  
  I typically keep a maximized evince of certain document open all the
  time.  This hiccup occurs maybe once or twice a day.
  
- This occured with 22.10 also, bty.
+ This occured with 22.10 also, btw.

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

Title:
  maximized evince shadowed by dock

Status in mutter package in Ubuntu:
  New

Bug description:
  Ubuntu 23.04, w/ wayland, evince 44.1, all updates applied to date
  (05/27/2023)

  I'm not sure what causes it but occasionally I find my maximized evince has 
expanded under the dock.
  My current workaround is to un-maximize (i.e., double-click titlebar), then 
maximime (double-click titlebar).

  I typically keep a maximized evince of certain document open all the
  time.  This hiccup occurs maybe once or twice a day.

  This occured with 22.10 also, btw.

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


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

[Desktop-packages] [Bug 1816497] Re: [snap] vaapi chromium no video hardware decoding

[Matt Lee]

Hardware decode on candidate/hwacc worked out of the box for me, thanks!

- VaapiVideoDecoder
- Xorg
- VERSION="21.1 (Vera)"
- Intel Kabylake (Gen9)
- Intel(R) Core(TM) i7-8550U CPU @ 1.80GHz

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

Title:
  [snap] vaapi chromium no video hardware decoding

Status in chromium-browser package in Ubuntu:
  In Progress

Bug description:
  To test the snap with VA-API changes,

  1. Install the Chromium snap,

     sudo snap install --channel candidate/hwacc chromium

  2. Start Chromium,

     snap run chromium

  3. Open a video, e.g. one from https://github.com/chthomos/video-
  media-samples.

  4. Enter about:media-internals in the address bar, click the
  corresponding box (if the video is playing, it will have the "(kPlay)"
  identifier) and note if the page says VaapiVideoDecoder for
  kVideoDecoderName. You can alternatively check with intel_gpu_top
  (from intel-gpu-tools package) that the video engine bars are non zero
  during playback.

  --Original Bug report -

  Libva is no longer working for snap installed chromium 72.0.3626.109
  (Official Build) snap (64-bit)

  I followed this instruction
  sudo snap install --channel=candidate/vaapi chromium

  My amdgpu can use libva

  `vainfo: Driver version: Mesa Gallium driver 18.3.3 for AMD STONEY (DRM 
3.27.0, 4.20.0-10.1-liquorix-amd64, LLVM 7.0.1)
  vainfo: Supported profile and entrypoints
    VAProfileMPEG2Simple:   VAEntrypointVLD
    VAProfileMPEG2Main  :   VAEntrypointVLD
    VAProfileVC1Simple  :   VAEntrypointVLD
    VAProfileVC1Main:   VAEntrypointVLD
    VAProfileVC1Advanced:   VAEntrypointVLD
    VAProfileH264ConstrainedBaseline:   VAEntrypointVLD
    VAProfileH264ConstrainedBaseline:   VAEntrypointEncSlice
    VAProfileH264Main   :   VAEntrypointVLD
    VAProfileH264Main   :   VAEntrypointEncSlice
    VAProfileH264High   :   VAEntrypointVLD
    VAProfileH264High   :   VAEntrypointEncSlice
    VAProfileHEVCMain   :   VAEntrypointVLD
    VAProfileHEVCMain10 :   VAEntrypointVLD
    VAProfileJPEGBaseline   :   VAEntrypointVLD
    VAProfileNone   :   VAEntrypointVideoProc`

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


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

[Desktop-packages] [Bug 2017648] [NEW] package libreoffice-core 1:7.4.6-0ubuntu0.22.10.1 failed to install/upgrade: dpkg-deb --fsys-tarfile subprocess returned error exit status 2

[matt]

Public bug reported:

Error occurred during upgrade to 23.04

ProblemType: Package
DistroRelease: Ubuntu 23.04
Package: libreoffice-core 1:7.4.6-0ubuntu0.22.10.1
ProcVersionSignature: Ubuntu 5.19.0-40.41-generic 5.19.17
Uname: Linux 5.19.0-40-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.23.1-0ubuntu3.2
Architecture: amd64
CasperMD5CheckResult: pass
Date: Tue Apr 25 10:32:48 2023
ErrorMessage: dpkg-deb --fsys-tarfile subprocess returned error exit status 2
InstallationDate: Installed on 2022-11-02 (173 days ago)
InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
Python3Details: /usr/bin/python3.11, Python 3.11.2, python3-minimal, 3.11.2-1
PythonDetails: N/A
RebootRequiredPkgs: Error: path contained symlinks.
RelatedPackageVersions:
 dpkg 1.21.9ubuntu1
 apt  2.5.3
SourcePackage: libreoffice
Title: package libreoffice-core 1:7.4.6-0ubuntu0.22.10.1 failed to 
install/upgrade: dpkg-deb --fsys-tarfile subprocess returned error exit status 2
UpgradeStatus: Upgraded to lunar on 2023-04-25 (0 days ago)

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


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

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

Title:
  package libreoffice-core 1:7.4.6-0ubuntu0.22.10.1 failed to
  install/upgrade: dpkg-deb --fsys-tarfile subprocess returned error
  exit status 2

Status in libreoffice package in Ubuntu:
  New

Bug description:
  Error occurred during upgrade to 23.04

  ProblemType: Package
  DistroRelease: Ubuntu 23.04
  Package: libreoffice-core 1:7.4.6-0ubuntu0.22.10.1
  ProcVersionSignature: Ubuntu 5.19.0-40.41-generic 5.19.17
  Uname: Linux 5.19.0-40-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.23.1-0ubuntu3.2
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Tue Apr 25 10:32:48 2023
  ErrorMessage: dpkg-deb --fsys-tarfile subprocess returned error exit status 2
  InstallationDate: Installed on 2022-11-02 (173 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  Python3Details: /usr/bin/python3.11, Python 3.11.2, python3-minimal, 3.11.2-1
  PythonDetails: N/A
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions:
   dpkg 1.21.9ubuntu1
   apt  2.5.3
  SourcePackage: libreoffice
  Title: package libreoffice-core 1:7.4.6-0ubuntu0.22.10.1 failed to 
install/upgrade: dpkg-deb --fsys-tarfile subprocess returned error exit status 2
  UpgradeStatus: Upgraded to lunar on 2023-04-25 (0 days ago)

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


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

[Desktop-packages] [Bug 2013545] [NEW] /usr/sbin/apt-add-repository will not function with IPv6 proxies called by address

[Matt Clauson]

Public bug reported:

It appears that if one has an HTTP or HTTPS proxy called out
specifically by IPv6 address rather than hostname, it will fail.
Placing an entry in /etc/hosts, or the proxy into DNS (and calling by
hostname) will function.

failure steps:

1) set proxy environment variables
  export http_proxy="http://[2001:db8:f00::2]:3128/";
  export https_proxy="http://[2001:db8:f00::2]:3128/";

2) Attempt to add repository (in this case, a PPA):
  apt-add-repository ppa:ansible/ansible

3) Enjoy the resulting stack trace:
Traceback (most recent call last):
  File "/usr/bin/apt-add-repository", line 364, in 
sys.exit(0 if addaptrepo.main() else 1)
  File "/usr/bin/apt-add-repository", line 347, in main
shortcut = handler(source, **shortcut_params)
  File "/usr/lib/python3/dist-packages/softwareproperties/shortcuts.py", line 
40, in shortcut_handler
return handler(shortcut, **kwargs)
  File "/usr/lib/python3/dist-packages/softwareproperties/ppa.py", line 82, in 
__init__
if self.lpppa.publish_debug_symbols:
  File "/usr/lib/python3/dist-packages/softwareproperties/ppa.py", line 120, in 
lpppa
self._lpppa = self.lpteam.getPPAByName(name=self.ppaname)
  File "/usr/lib/python3/dist-packages/softwareproperties/ppa.py", line 107, in 
lpteam
self._lpteam = self.lp.people(self.teamname)
  File "/usr/lib/python3/dist-packages/softwareproperties/ppa.py", line 98, in 
lp
self._lp = login_func("%s.%s" % (self.__module__, self.__class__.__name__),
  File "/usr/lib/python3/dist-packages/launchpadlib/launchpad.py", line 494, in 
login_anonymously
return cls(
  File "/usr/lib/python3/dist-packages/launchpadlib/launchpad.py", line 230, in 
__init__
super(Launchpad, self).__init__(
  File "/usr/lib/python3/dist-packages/lazr/restfulclient/resource.py", line 
472, in __init__
self._wadl = self._browser.get_wadl_application(self._root_uri)
  File "/usr/lib/python3/dist-packages/lazr/restfulclient/_browser.py", line 
447, in get_wadl_application
response, content = self._request(url, media_type=wadl_type)
  File "/usr/lib/python3/dist-packages/lazr/restfulclient/_browser.py", line 
389, in _request
response, content = self._request_and_retry(
  File "/usr/lib/python3/dist-packages/lazr/restfulclient/_browser.py", line 
359, in _request_and_retry
response, content = self._connection.request(
  File "/usr/lib/python3/dist-packages/httplib2/__init__.py", line 1578, in 
request
conn = self.connections[conn_key] = connection_type(
  File "/usr/lib/python3/dist-packages/httplib2/__init__.py", line 1095, in 
__init__
self.proxy_info = proxy_info("https")
  File "/usr/lib/python3/dist-packages/httplib2/__init__.py", line 926, in 
proxy_info_from_environment
return proxy_info_from_url(url, method, noproxy=None)
  File "/usr/lib/python3/dist-packages/httplib2/__init__.py", line 950, in 
proxy_info_from_url
port = int(port)
ValueError: invalid literal for int() with base 10: 'db8:f00::2]:3128'

Ubuntu Release:
# lsb_release -rd
Description:Ubuntu 22.04.2 LTS
Release:22.04

Package version:
# apt-cache policy software-properties-common
software-properties-common:
  Installed: 0.99.22.6
  Candidate: 0.99.22.6
  Version table:
 *** 0.99.22.6 500
500 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages
100 /var/lib/dpkg/status
 0.99.22 500
500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages

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


** Tags: ipv6 proxy

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

Title:
  /usr/sbin/apt-add-repository will not function with IPv6 proxies
  called by address

Status in software-properties package in Ubuntu:
  New

Bug description:
  It appears that if one has an HTTP or HTTPS proxy called out
  specifically by IPv6 address rather than hostname, it will fail.
  Placing an entry in /etc/hosts, or the proxy into DNS (and calling by
  hostname) will function.

  failure steps:

  1) set proxy environment variables
export http_proxy="http://[2001:db8:f00::2]:3128/";
export https_proxy="http://[2001:db8:f00::2]:3128/";

  2) Attempt to add repository (in this case, a PPA):
apt-add-repository ppa:ansible/ansible

  3) Enjoy the resulting stack trace:
  Traceback (most recent call last):
File "/usr/bin/apt-add-repository", line 364, in 
  sys.exit(0 if addaptrepo.main() else 1)
File "/usr/bin/apt-add-repository", line 347, in main
  shortcut = handler(source, **shortcut_params)
File "/usr/lib/python3/dist-packages/softwareproperties/shortcuts.py", line 
40, in shortcut_handler
  return handler(shortcut, **kwargs)
File "/usr/lib/python3/dist-packages/softwareproperties/ppa.py", line 82, 
in __init__
  if self.lpppa.publish_debug_symbols:
File "/usr/lib/py

[Desktop-packages] [Bug 1977748] Re: Build Cairo with OpenGL support

[Matt Wette]

Here is a link for cairo/egl: https://jan.newmarch.name/Wayland/Cairo/

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

Title:
  Build Cairo with OpenGL support

Status in cairo package in Ubuntu:
  Triaged

Bug description:
  Instructed by "ask a question" I tried to file a wayland-targeted bug,
  but apport-bug thinks I'm running Xorg.  See
  https://answers.launchpad.net/ubuntu/+question/702075

  PRETTY_NAME="Ubuntu 22.04 LTS"
  NAME="Ubuntu"
  VERSION_ID="22.04"
  VERSION="22.04 LTS (Jammy Jellyfish)"
  VERSION_CODENAME=jammy

  $ ps -ef | grep Xwayland
  xx  24931685  0 Jun04 ?00:05:36 /usr/bin/Xwayland :0 
-rootless -noreset -accessx -core -auth 
/run/user/1001/.mutter-Xwaylandauth.5ZZYM1 -listen 4 -listen 5 -displayfd 6 
-initfd 7

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-35.36-generic 5.15.35
  Uname: Linux 5.15.0-35-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jun  6 06:40:48 2022
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation TigerLake-LP GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) 
(prog-if 00 [VGA controller])
 Subsystem: Dell TigerLake-LP GT2 [Iris Xe Graphics] [1028:0991]
  InstallationDate: Installed on 2021-10-02 (246 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  MachineType: Dell Inc. XPS 13 9310
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-35-generic 
root=UUID=c737013a-1cc7-494f-a1b7-a6efce6f09f7 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/17/2022
  dmi.bios.release: 3.6
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 3.6.0
  dmi.board.name: 0MK6WC
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr3.6.0:bd03/17/2022:br3.6:svnDellInc.:pnXPS139310:pvr:rvnDellInc.:rn0MK6WC:rvrA00:cvnDellInc.:ct10:cvr:sku0991:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9310
  dmi.product.sku: 0991
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.110-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

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


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

[Desktop-packages] [Bug 2004532] Re: Hardware acceleration broken for amdgpu/mesa in snap

[Matt Vickers]

I can confirm this under Gnome as well. Starting a Wayland session, all
works fine. Logging in under Xorg results in this graphical issue for
both Firefox and Chromium.

Same GPU as the initial reporter, however I am on 22.04 and kernel
5.15.0 (stock HWE).

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

Title:
  Hardware acceleration broken for amdgpu/mesa in snap

Status in chromium-browser package in Ubuntu:
  Triaged
Status in firefox package in Ubuntu:
  Confirmed
Status in snapd package in Ubuntu:
  Confirmed

Bug description:
  Snap packages which use hardware accelerated graphics are broken after
  the last routine system upgrade via apt. My system is using AMD Radeon
  RX 5500 XT graphics card from ASUS, with stock amdgpu kernel drivers.
  Two snap packages which are now unusable are Mozilla Firefox and
  Chromium browsers. Both display animated speckled color garbage inside
  their windows, overlayed with the correct image. Disabling hardware
  acceleration in the settings for the snap version of Firefox fixed it.
  Also, Firefox version installed from the original Mozilla tarball into
  /opt/ works just fine with the acceleration enabled on the same
  system, as well as glmark2 benchmark. Looks like the issue is only
  affecting snap packages.

  $ snap list firefox chromium
  Name  Version Rev   Tracking   Publisher   Notes
  chromium  109.0.5414.119  2295  latest/stable  canonical✓  -
  firefox   109.0.1-1   2311  latest/stable  mozilla✓-

  $ dpkg -l snapd|grep ^ii
  ii  snapd  2.58+22.10   amd64Daemon and tooling that enable 
snap packages

  $ dpkg -l mesa\* | grep ^ii
  ii  mesa-utils8.5.0-1   amd64Miscellaneous 
Mesa utilities -- symlinks
  ii  mesa-utils-bin:amd64  8.5.0-1   amd64Miscellaneous 
Mesa utilities -- native applications
  ii  mesa-va-drivers:amd64 22.2.5-0ubuntu0.1 amd64Mesa VA-API 
video acceleration drivers
  ii  mesa-vdpau-drivers:amd64  22.2.5-0ubuntu0.1 amd64Mesa VDPAU video 
acceleration drivers
  ii  mesa-vulkan-drivers:amd64 22.2.5-0ubuntu0.1 amd64Mesa Vulkan 
graphics drivers

  $ lsb_release -a
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:Ubuntu 22.10
  Release:22.10
  Codename:   kinetic

  $ uname -a
  Linux xx 5.19.0-29-generic #30-Ubuntu SMP PREEMPT_DYNAMIC Wed Jan 4 
12:14:09 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: snap (not installed)
  ProcVersionSignature: Ubuntu 5.19.0-29.30-generic 5.19.17
  Uname: Linux 5.19.0-29-generic x86_64
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  Date: Wed Feb  1 22:55:48 2023
  InstallationDate: Installed on 2020-08-02 (913 days ago)
  InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  SourcePackage: snap
  UpgradeStatus: Upgraded to kinetic on 2023-02-02 (0 days ago)
  --- 
  ProblemType: Bug
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  DRM.card0-DP-1:
   enabled: enabled
   dpms: On
   status: connected
   edid-base64: 
AP///wAebQd34yoBAAQcAQS1PCJ4nz4xrlBHrCcMUFQhCABxQIGAgcCpwNHAgQABAQEBTdAAoPBwPoAwIGUMWFQhAAAaKGgAoPBwPoAIkGUMWFQhAAAa/QAwPYeHOAEKICAgICAg/ABMRyBIRFIgNEsKICAgAfsCAxlxRJAEAwEjCQcHgwEAAOMFwADjBgUBAjqAGHE4LUBYLEUAWFQhAAAeVl4AoKCgKVAwIDUAWFQhAAAaKQ==
   modes: 3840x2160 3840x2160 3840x2160 3840x2160 3840x2160 2560x1440 1920x1200 
1920x1080 1920x1080 1920x1080 1600x1200 1680x1050 1600x900 1280x1024 1440x900 
1280x800 1152x864 1280x720 1280x720 1280x720 1024x768 800x600 720x480 720x480 
640x480 640x480 640x480
  DRM.card0-DP-2:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64: 
   modes:
  DRM.card0-DP-3:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64: 
   modes:
  DRM.card0-HDMI-A-1:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64: 
   modes:
  DiskUsage:
   Filesystem Type   Size  Used Avail Use% Mounted on
   /dev/nvme0n1p2 ext4   916G  222G  648G  26% /
   tmpfs  tmpfs   16G 0   16G   0% /dev/shm
   /dev/nvme0n1p2 ext4   916G  222G  648G  26% /
  DistroRelease: Ubuntu 22.10
  InstallationDate: Installed on 2020-08-02 (914 days ago)
  InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: ASUS System Product Name
  Package: chromium-browser 1:85.0.4183.83-0ubuntu2
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-29-generic 
root=UUID=1a37d538-d59f-477b-96f0-f949ce9b4553 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.19.0-29.30-generic 5.

[Desktop-packages] [Bug 2003406] Re: imap and smtp to outlook.office365.com over oauth2 problem

[Matt Blissett]

In case anyone else comes across this, the recommendation from the
Thunderbird developers is to downgrade:
https://blog.thunderbird.net/2023/01/important-message-for-microsoft-
office-365-enterprise-users/

e.g. sudo apt-get install thunderbird=1:102.4.2+build2-0ubuntu0.22.04.1


With 1:102.7.1+build1-0ubuntu0.22.04.1~mt1 I had different line numbers in the 
error:

JavaScript error: resource:///modules/OAuth2.jsm, line 170:
NS_ERROR_NOT_IMPLEMENTED: Component returned failure code: 0x80004001
(NS_ERROR_NOT_IMPLEMENTED) [nsIRequest.name]

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

Title:
  imap and smtp to outlook.office365.com over oauth2 problem

Status in thunderbird package in Ubuntu:
  Confirmed

Bug description:
  Good morning,

  Since yesterday january 18 2023 Thunderbird cannot connect to my
  company email anymore, both imap and smtp. Mail server for imap is
  outlook.office365.com, port 993, SSL/TLS, OAuth2. For smtp:
  smtp.office365.com port 587, STARTTLS, OAuth2.

  On january 17 and before, all was working well with the same settings.
  Thunderbird version is 102.7.0 (64-bit) on an up-to-date Ubuntu 22.10.
  When I start TB from a terminal, I get this:

  ```
  [ImapModuleLoader] Using nsImapService.cpp
  [NntpModuleLoader] Using NntpService.jsm
  [Pop3ModuleLoader] Using Pop3Service.jsm
  ATTENTION: default value of option mesa_glthread overridden by environment.
  ATTENTION: default value of option mesa_glthread overridden by environment.
  ATTENTION: default value of option mesa_glthread overridden by environment.
  ATTENTION: default value of option mesa_glthread overridden by environment.
  [calBackendLoader] Using Thunderbird's ical.js backend
  console.debug: "Successfully loaded OpenPGP library librnp.so version 
0.16.2+git20220922.298ad98b.MZLA from /usr/lib/thunderbird/librnp.so"
  console.debug: "Found 0 public keys and 0 secret keys (0 protected, 0 
unprotected)"
  console.debug: "Successfully loaded optional OpenPGP library libgpgme.so.11 
from system's standard library locations"
  console.debug: "gpgme version: 1.17.1"
  console.warn: services.settings: Failed to load last_modified.json: 
TypeError: NetworkError when attempting to fetch resource.
  console.debug: "Trying to load /usr/lib/thunderbird/libotr.so"
  console.debug: "Trying to load libotr.so from system's standard library 
locations"
  console.debug: "Trying to load libotr.so.5 from system's standard library 
locations"
  console.debug: "Trying to load libotr.so from system's standard library 
locations"
  console.log: (new Error("Cannot load required OTR library", 
"resource:///modules/OTRLib.jsm", 109))
  JavaScript error: resource:///modules/OAuth2.jsm, line 168: 
NS_ERROR_NOT_IMPLEMENTED: Component returned failure code: 0x80004001 
(NS_ERROR_NOT_IMPLEMENTED) [nsIRequest.name]
  JavaScript error: resource:///modules/OAuth2.jsm, line 168: 
NS_ERROR_NOT_IMPLEMENTED: Component returned failure code: 0x80004001 
(NS_ERROR_NOT_IMPLEMENTED) [nsIRequest.name]
  JavaScript error: resource:///modules/OAuth2.jsm, line 168: 
NS_ERROR_NOT_IMPLEMENTED: Component returned failure code: 0x80004001 
(NS_ERROR_NOT_IMPLEMENTED) [nsIRequest.name]
  ```

  That last bit (to me) seems to indicate a client side (TB) issue. If
  anybody knows or can make a fix, that would be great, I much prefer TB
  to the MS web interface.

  Best,

  Joolz.

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


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

[Desktop-packages] [Bug 1999086] [NEW] Livepatch attaches after a long time but indicates failure to attach to Ubuntu Advantage

[Matt Clapp]

Public bug reported:

It seems that attaching to Ubuntu Advantage takes a long time.  When I
tried to attach using my token in the GUI, it repeatedly told me that I
"failed to attach, try again".  Finally I gave up and canceled out of
the dialog, only to see that in the underlying UI for the Livepatch tab
it was successfully attached already.

It seems that it takes too long to attach and the token attach dialog
gets stuck thinking it will never attach, when either 1.) it's just
taking a while or 2.) it has already attached in the background but the
dialog doesn't understand.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: software-properties-gtk 0.99.22.3
ProcVersionSignature: Ubuntu 5.15.0-56.62-generic 5.15.64
Uname: Linux 5.15.0-56-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.11-0ubuntu82.2
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Wed Dec  7 12:44:30 2022
InstallationDate: Installed on 2022-11-14 (23 days ago)
InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
PackageArchitecture: all
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/usr/bin/zsh
SourcePackage: software-properties
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug jammy

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

Title:
  Livepatch attaches after a long time but indicates failure to attach
  to Ubuntu Advantage

Status in software-properties package in Ubuntu:
  New

Bug description:
  It seems that attaching to Ubuntu Advantage takes a long time.  When I
  tried to attach using my token in the GUI, it repeatedly told me that
  I "failed to attach, try again".  Finally I gave up and canceled out
  of the dialog, only to see that in the underlying UI for the Livepatch
  tab it was successfully attached already.

  It seems that it takes too long to attach and the token attach dialog
  gets stuck thinking it will never attach, when either 1.) it's just
  taking a while or 2.) it has already attached in the background but
  the dialog doesn't understand.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: software-properties-gtk 0.99.22.3
  ProcVersionSignature: Ubuntu 5.15.0-56.62-generic 5.15.64
  Uname: Linux 5.15.0-56-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu82.2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Dec  7 12:44:30 2022
  InstallationDate: Installed on 2022-11-14 (23 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/usr/bin/zsh
  SourcePackage: software-properties
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Desktop-packages] [Bug 1816497] Re: [snap] vaapi chromium no video hardware decoding

[Matt Lee]

Hardware decode on stable/hwacc worked out of the box for me, thanks!

- VDAVideoDecoder
- Xorg
- VERSION="21 (Vanessa)"
- Intel Kabylake (Gen9)
- Intel(R) Core(TM) i7-8550U CPU @ 1.80GHz

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

Title:
  [snap] vaapi chromium no video hardware decoding

Status in chromium-browser package in Ubuntu:
  In Progress

Bug description:
  To test the snap with VA-API changes,

  1. Install the Chromium snap,

     sudo snap install --channel stable/hwacc chromium

  2. Start Chromium,

     snap run chromium

  3. Open a video, e.g. one from https://github.com/chthomos/video-
  media-samples.

  4. Enter about:media-internals in the address bar, click the
  corresponding box (if the video is playing, it will have the "(kPlay)"
  identifier) and note what the page says for kVideoDecoderName.

  Please report

  - The value for kVideoDecoderName from step 4. Success is typically 
{Vaapi,VDA,Mojo}VideoDecoder while failure is {FFMpeg,Vpx,Dav1d}VideoDecoder;
  - Xorg or Wayland (`echo $WAYLAND_DISPLAY`);
  - Distro version (`grep VERSION= /etc/os_release`);
  - GPU (`lscpu`);
  - CPU generation (`lscpu`).

  Currently it seems to work for all reporters on Xorg.

  The version in stable/hwacc is fixed.

  Versions in other channels (edge/hwacc, beta/hwacc, candidate/hwacc)
  follow the Chromium release cycle (dev, beta and stable channels as in
  https://omahaproxy.appspot.com/all.json?os=linux).

  --Original Bug report -

  Libva is no longer working for snap installed chromium 72.0.3626.109
  (Official Build) snap (64-bit)

  I followed this instruction
  sudo snap install --channel=candidate/vaapi chromium

  My amdgpu can use libva

  `vainfo: Driver version: Mesa Gallium driver 18.3.3 for AMD STONEY (DRM 
3.27.0, 4.20.0-10.1-liquorix-amd64, LLVM 7.0.1)
  vainfo: Supported profile and entrypoints
    VAProfileMPEG2Simple:   VAEntrypointVLD
    VAProfileMPEG2Main  :   VAEntrypointVLD
    VAProfileVC1Simple  :   VAEntrypointVLD
    VAProfileVC1Main:   VAEntrypointVLD
    VAProfileVC1Advanced:   VAEntrypointVLD
    VAProfileH264ConstrainedBaseline:   VAEntrypointVLD
    VAProfileH264ConstrainedBaseline:   VAEntrypointEncSlice
    VAProfileH264Main   :   VAEntrypointVLD
    VAProfileH264Main   :   VAEntrypointEncSlice
    VAProfileH264High   :   VAEntrypointVLD
    VAProfileH264High   :   VAEntrypointEncSlice
    VAProfileHEVCMain   :   VAEntrypointVLD
    VAProfileHEVCMain10 :   VAEntrypointVLD
    VAProfileJPEGBaseline   :   VAEntrypointVLD
    VAProfileNone   :   VAEntrypointVideoProc`

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


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

[Desktop-packages] [Bug 1816497] Re: [snap] vaapi chromium no video hardware decoding

[Matt Lee]

For these description items:

- Distro version (`grep VERSION= /etc/os_release`);
- GPU (`lscpu`);

Do you mean?

- Distro version (`grep VERSION= /etc/os-release`);
- GPU (`lsgpu`);

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

Title:
  [snap] vaapi chromium no video hardware decoding

Status in chromium-browser package in Ubuntu:
  In Progress

Bug description:
  To test the snap with VA-API changes,

  1. Install the Chromium snap,

     sudo snap install --channel stable/hwacc chromium

  2. Start Chromium,

     snap run chromium

  3. Open a video, e.g. one from https://github.com/chthomos/video-
  media-samples.

  4. Enter about:media-internals in the address bar, click the
  corresponding box (if the video is playing, it will have the "(kPlay)"
  identifier) and note what the page says for kVideoDecoderName.

  Please report

  - The value for kVideoDecoderName from step 4. Success is typically 
{Vaapi,VDA,Mojo}VideoDecoder while failure is {FFMpeg,Vpx,Dav1d}VideoDecoder;
  - Xorg or Wayland (`echo $WAYLAND_DISPLAY`);
  - Distro version (`grep VERSION= /etc/os_release`);
  - GPU (`lscpu`);
  - CPU generation (`lscpu`).

  Currently it seems to work for all reporters on Xorg.

  The version in stable/hwacc is fixed.

  Versions in other channels (edge/hwacc, beta/hwacc, candidate/hwacc)
  follow the Chromium release cycle (dev, beta and stable channels as in
  https://omahaproxy.appspot.com/all.json?os=linux).

  --Original Bug report -

  Libva is no longer working for snap installed chromium 72.0.3626.109
  (Official Build) snap (64-bit)

  I followed this instruction
  sudo snap install --channel=candidate/vaapi chromium

  My amdgpu can use libva

  `vainfo: Driver version: Mesa Gallium driver 18.3.3 for AMD STONEY (DRM 
3.27.0, 4.20.0-10.1-liquorix-amd64, LLVM 7.0.1)
  vainfo: Supported profile and entrypoints
    VAProfileMPEG2Simple:   VAEntrypointVLD
    VAProfileMPEG2Main  :   VAEntrypointVLD
    VAProfileVC1Simple  :   VAEntrypointVLD
    VAProfileVC1Main:   VAEntrypointVLD
    VAProfileVC1Advanced:   VAEntrypointVLD
    VAProfileH264ConstrainedBaseline:   VAEntrypointVLD
    VAProfileH264ConstrainedBaseline:   VAEntrypointEncSlice
    VAProfileH264Main   :   VAEntrypointVLD
    VAProfileH264Main   :   VAEntrypointEncSlice
    VAProfileH264High   :   VAEntrypointVLD
    VAProfileH264High   :   VAEntrypointEncSlice
    VAProfileHEVCMain   :   VAEntrypointVLD
    VAProfileHEVCMain10 :   VAEntrypointVLD
    VAProfileJPEGBaseline   :   VAEntrypointVLD
    VAProfileNone   :   VAEntrypointVideoProc`

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


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

[Desktop-packages] [Bug 1988660] Re: snap doesn't map joystick buttons correctly

[Matt Reynolds]

Hi, I found this bug while investigating the Chromium bug
https://crbug.com/1359677

I'm guessing this is caused by Chromium's use of udev for device
enumeration. Gamepad API on Linux uses udev to enumerate devices in the
joydev, evdev, and hidraw subsystems.

flatpak has a similar problem:
https://github.com/flathub/org.chromium.Chromium/issues/40

"Unfortunately we're mostly stuck like this for now, since Chromium
expects to read devices from udev, which cannot be directly exposed into
the sandbox due to having an unstable ABI."

As noted up-thread, there's a flatpak workaround that involves
configuring the udev filesystem to be read-only.

I'd like to fix this by removing Chromium's dependency on udev. Is there
an alternative that plays nicely with snap/flatpak sandboxing?

** Bug watch added: github.com/flathub/org.chromium.Chromium/issues #40
   https://github.com/flathub/org.chromium.Chromium/issues/40

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

Title:
  snap doesn't map joystick buttons correctly

Status in chromium-browser package in Ubuntu:
  Incomplete

Bug description:
  I tested the deb version and works fine.

  Steps to reproduce the problem:
  1.Connect the PS4 joystick by Bluetooth in Linux
  2.Test mapping in a webpage like gamepad-tester.com
  3.Almost all buttons are incorrectly mapped

  Problem Description:
  The buttons of the joystick are incorrectly mapped in the browser and this 
makes impossible to play Stadia, even the right axis remain always pressed when 
you press R2 once, you can see the error by yourself at this short video: 
https://www.youtube.com/watch?v=VLPQkXyVAsM

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


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

[Desktop-packages] [Bug 1849880] Re: Mouse-Scrolling Changes Drop-Down Selections During Scroll Navigation

[Matt]

Is this issue just for the control center, or should it be a user-wide
setting? This behavior is infuriating and negatively affects me on
countless surfaces.

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

Title:
  Mouse-Scrolling Changes Drop-Down Selections During Scroll Navigation

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

Bug description:
  The Gnome Sound Settings tab contains enough options to where you have
  to scroll down to see them all.

  Since the scrollbar is so narrow, I use my mouse-scroll-wheel to
  achieve this scroll navigation.

  However, while scrolling with the intention of "navigation", if the
  mouse-cursor passes over the Output Device drop-down-menu, or any of
  the slider controls, it inadvertently changes those options.

  The ability to change drop-down-menu selections, using the mouse-
  scroll-wheel is convenient in some cases, but it becomes problematic
  when the user is simply intending to do scroll navigation.

  I can see a non-advance user accidentally changing sound settings that
  they had no intention of changing in this design. Plus, even if they
  do notice the inadvertent changes, they might not know "what to change
  it back to".

  It may be better to disable scroll driven option selection changes in
  these menus.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-control-center 1:3.34.1-1ubuntu2
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  Date: Fri Oct 25 12:29:32 2019
  InstallationDate: Installed on 2019-10-19 (6 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Desktop-packages] [Bug 1977748] Re: Build Cairo with OpenGL support

[Matt Wette]

I was looking to run cairo on wayland.  A web search led me to the EGL
device.  I'm guessing by buffer you mean IMAGE surface (after digging in
the headers a bit).   I am happy to try that.  But I'm guessing at some
point in the future peeps will want it.   Thanks for digging in.

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

Title:
  Build Cairo with OpenGL support

Status in cairo package in Ubuntu:
  Triaged

Bug description:
  Instructed by "ask a question" I tried to file a wayland-targeted bug,
  but apport-bug thinks I'm running Xorg.  See
  https://answers.launchpad.net/ubuntu/+question/702075

  PRETTY_NAME="Ubuntu 22.04 LTS"
  NAME="Ubuntu"
  VERSION_ID="22.04"
  VERSION="22.04 LTS (Jammy Jellyfish)"
  VERSION_CODENAME=jammy

  $ ps -ef | grep Xwayland
  xx  24931685  0 Jun04 ?00:05:36 /usr/bin/Xwayland :0 
-rootless -noreset -accessx -core -auth 
/run/user/1001/.mutter-Xwaylandauth.5ZZYM1 -listen 4 -listen 5 -displayfd 6 
-initfd 7

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-35.36-generic 5.15.35
  Uname: Linux 5.15.0-35-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jun  6 06:40:48 2022
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation TigerLake-LP GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) 
(prog-if 00 [VGA controller])
 Subsystem: Dell TigerLake-LP GT2 [Iris Xe Graphics] [1028:0991]
  InstallationDate: Installed on 2021-10-02 (246 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  MachineType: Dell Inc. XPS 13 9310
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-35-generic 
root=UUID=c737013a-1cc7-494f-a1b7-a6efce6f09f7 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/17/2022
  dmi.bios.release: 3.6
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 3.6.0
  dmi.board.name: 0MK6WC
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr3.6.0:bd03/17/2022:br3.6:svnDellInc.:pnXPS139310:pvr:rvnDellInc.:rn0MK6WC:rvrA00:cvnDellInc.:ct10:cvr:sku0991:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9310
  dmi.product.sku: 0991
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.110-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

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


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

[Desktop-packages] [Bug 1859033] Re: guile-2.2 installed but not guild-2.2

[Matt Wette]

FYI, the upstream debian package for guile has been updated (by rlb) to fix 
this.
I have no objection to closing this item.

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

Title:
  guile-2.2 installed but not guild-2.2

Status in guile-2.2 package in Ubuntu:
  New

Bug description:
  guile-2.2 package apparently installs guile, guile-2.2 and guild in
  /usr/bin, but not guild-2.2.  This causes packages using configure w/
  guile.m4 macros to fail: GUILE is defined but not GUILD.  So builds
  which use commands (in the Makefiles) of the form "$(GUILD) compile
  ..." will fail.

  Suggest adding guild-2.2 to the install process.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: guile-2.2 2.2.3+1-3ubuntu0.1
  ProcVersionSignature: Ubuntu 4.15.0-74.84-generic 4.15.18
  Uname: Linux 4.15.0-74-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jan  9 06:30:37 2020
  InstallationDate: Installed on 2019-02-03 (339 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: guile-2.2
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/guile-2.2/+bug/1859033/+subscriptions


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

[Desktop-packages] [Bug 1966921] Re: Display freezes after entering password from login screen

[Matt Austin]

Thanks Daniel.

You were right about the extensions, thank you for the suggestion.

It appears to be caused by the "Nothing to Say" gnome extension. I
uninstalled this, and can now use the wayland session again.

It looks like it's probably the same issue as reported here (by a user running 
20.04):
https://github.com/wbolster/nothing-to-say/issues/49

Thanks for your time, sorry if I wasted it by suggesting the bug was was
mutter-related.

** Bug watch added: github.com/wbolster/nothing-to-say/issues #49
   https://github.com/wbolster/nothing-to-say/issues/49

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

Title:
  Display freezes after entering password from login screen

Status in mutter package in Ubuntu:
  Incomplete

Bug description:
  The display freezes with the same background colour as the login
  screen. The mouse pointer no longer moves. I was unable to change to
  another VT when the display freezes. Only a press of the power button
  seemed to make the laptop respond by triggering a shutdown.

  I've had to switch to "GNOME on Xorg" to be able to login/see the
  desktop. Wayland was working fine until some time around the last
  week.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: mutter 42~beta-1ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Uname: Linux 5.15.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: GNOME
  Date: Tue Mar 29 18:34:41 2022
  InstallationDate: Installed on 2021-09-13 (196 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  SourcePackage: mutter
  UpgradeStatus: Upgraded to jammy on 2022-02-19 (38 days ago)

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


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

[Desktop-packages] [Bug 1966921] Re: Display freezes after entering password from login screen

[Matt Austin]

Thanks Daniel,

I have attached the requested output.

** Attachment added: "lspci.txt"
   
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1966921/+attachment/5574560/+files/lspci.txt

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

Title:
  Display freezes after entering password from login screen

Status in mutter package in Ubuntu:
  Incomplete

Bug description:
  The display freezes with the same background colour as the login
  screen. The mouse pointer no longer moves. I was unable to change to
  another VT when the display freezes. Only a press of the power button
  seemed to make the laptop respond by triggering a shutdown.

  I've had to switch to "GNOME on Xorg" to be able to login/see the
  desktop. Wayland was working fine until some time around the last
  week.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: mutter 42~beta-1ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Uname: Linux 5.15.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: GNOME
  Date: Tue Mar 29 18:34:41 2022
  InstallationDate: Installed on 2021-09-13 (196 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  SourcePackage: mutter
  UpgradeStatus: Upgraded to jammy on 2022-02-19 (38 days ago)

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


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

[Desktop-packages] [Bug 1966921] Re: Display freezes after entering password from login screen

[Matt Austin]

** Attachment added: "prevboot.txt"
   
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1966921/+attachment/5574561/+files/prevboot.txt

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

Title:
  Display freezes after entering password from login screen

Status in mutter package in Ubuntu:
  Incomplete

Bug description:
  The display freezes with the same background colour as the login
  screen. The mouse pointer no longer moves. I was unable to change to
  another VT when the display freezes. Only a press of the power button
  seemed to make the laptop respond by triggering a shutdown.

  I've had to switch to "GNOME on Xorg" to be able to login/see the
  desktop. Wayland was working fine until some time around the last
  week.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: mutter 42~beta-1ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Uname: Linux 5.15.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: GNOME
  Date: Tue Mar 29 18:34:41 2022
  InstallationDate: Installed on 2021-09-13 (196 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  SourcePackage: mutter
  UpgradeStatus: Upgraded to jammy on 2022-02-19 (38 days ago)

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


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

[Desktop-packages] [Bug 1966921] [NEW] Display freezes after entering password from login screen

[Matt Austin]

Public bug reported:

The display freezes with the same background colour as the login screen.
The mouse pointer no longer moves. I was unable to change to another VT
when the display freezes. Only a press of the power button seemed to
make the laptop respond by triggering a shutdown.

I've had to switch to "GNOME on Xorg" to be able to login/see the
desktop. Wayland was working fine until some time around the last week.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: mutter 42~beta-1ubuntu2
ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
Uname: Linux 5.15.0-23-generic x86_64
ApportVersion: 2.20.11-0ubuntu79
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: GNOME
Date: Tue Mar 29 18:34:41 2022
InstallationDate: Installed on 2021-09-13 (196 days ago)
InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
SourcePackage: mutter
UpgradeStatus: Upgraded to jammy on 2022-02-19 (38 days ago)

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


** Tags: amd64 apport-bug jammy

** Description changed:

- I was unable to change to another VT when the display freezes. Only a
- press of the power button seemed to make the laptop respond by
- triggering a shutdown.
+ The display freezes with the same background colour as the login screen.
+ The mouse pointer no longer moves. I was unable to change to another VT
+ when the display freezes. Only a press of the power button seemed to
+ make the laptop respond by triggering a shutdown.
  
  I've had to switch to "GNOME on Xorg" to be able to login/see the
  desktop. Wayland was working fine until some time around the last week.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: mutter 42~beta-1ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Uname: Linux 5.15.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: GNOME
  Date: Tue Mar 29 18:34:41 2022
  InstallationDate: Installed on 2021-09-13 (196 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  SourcePackage: mutter
  UpgradeStatus: Upgraded to jammy on 2022-02-19 (38 days ago)

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

Title:
  Display freezes after entering password from login screen

Status in mutter package in Ubuntu:
  New

Bug description:
  The display freezes with the same background colour as the login
  screen. The mouse pointer no longer moves. I was unable to change to
  another VT when the display freezes. Only a press of the power button
  seemed to make the laptop respond by triggering a shutdown.

  I've had to switch to "GNOME on Xorg" to be able to login/see the
  desktop. Wayland was working fine until some time around the last
  week.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: mutter 42~beta-1ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Uname: Linux 5.15.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: GNOME
  Date: Tue Mar 29 18:34:41 2022
  InstallationDate: Installed on 2021-09-13 (196 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  SourcePackage: mutter
  UpgradeStatus: Upgraded to jammy on 2022-02-19 (38 days ago)

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


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

[Desktop-packages] [Bug 1964506] [NEW] Ping: checks payloads incorrectly, ignores all mismatch replies

[Matt Whiteley]

Public bug reported:

Problematic commit reverted upstream causing incorrect behavior in
Ubuntu Focal.

Discussion: https://github.com/iputils/iputils/issues/320
Fix: https://github.com/iputils/iputils/pull/321
Release: https://github.com/iputils/iputils/releases/tag/20210722

Could this patch be added for a Focal update please?

1) Ubuntu 20.04.3 LTS
2) 3:20190709-3
3)

focal$ ping -c 1 -s 1200 8.8.8.8
PING 8.8.8.8 (8.8.8.8) 1200(1228) bytes of data.

--- 8.8.8.8 ping statistics ---
1 packets transmitted, 0 received, 100% packet loss, time 0ms

4)

xenial$ ping -c 1 -s 1200 8.8.8.8
PING 8.8.8.8 (8.8.8.8) 1200(1228) bytes of data.
76 bytes from 8.8.8.8: icmp_seq=1 ttl=61 (truncated)

--- 8.8.8.8 ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 0.284/0.284/0.284/0.000 ms

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

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

Title:
  Ping: checks payloads incorrectly, ignores all mismatch replies

Status in iputils package in Ubuntu:
  New

Bug description:
  Problematic commit reverted upstream causing incorrect behavior in
  Ubuntu Focal.

  Discussion: https://github.com/iputils/iputils/issues/320
  Fix: https://github.com/iputils/iputils/pull/321
  Release: https://github.com/iputils/iputils/releases/tag/20210722

  Could this patch be added for a Focal update please?

  1) Ubuntu 20.04.3 LTS
  2) 3:20190709-3
  3)

  focal$ ping -c 1 -s 1200 8.8.8.8
  PING 8.8.8.8 (8.8.8.8) 1200(1228) bytes of data.

  --- 8.8.8.8 ping statistics ---
  1 packets transmitted, 0 received, 100% packet loss, time 0ms

  4)

  xenial$ ping -c 1 -s 1200 8.8.8.8
  PING 8.8.8.8 (8.8.8.8) 1200(1228) bytes of data.
  76 bytes from 8.8.8.8: icmp_seq=1 ttl=61 (truncated)

  --- 8.8.8.8 ping statistics ---
  1 packets transmitted, 1 received, 0% packet loss, time 0ms
  rtt min/avg/max/mdev = 0.284/0.284/0.284/0.000 ms

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


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

[Desktop-packages] [Bug 1950461] Re: Installing vino does not expose the screen sharing slider in Gnome Control Center

[Matt Dale]

In that case, it's certainly the case that it's not installed in a
minimal install. I've come across this more than once.

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

Title:
  Installing vino does not expose the screen sharing slider in Gnome
  Control Center

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

Bug description:
  Ubuntu 21.10 - minimal install on a fresh machine

  apt install vino

  Open the gnome settings dialog and go to the Sharing tab. I would
  expect to see the screen sharing slider but it is not there.

  Searching around I found a suggestion to use Ubunutu with Xorg but
  this makes no difference.

  This behaviour is also present in 21.04.

  I have put gnome-control-center as the package at fault as this is
  ultimately where I observe the issue but it may be that during the
  install of vino makes the gnome configuration change and this step is
  missed.

  I have enquired on askubuntu and reddit but have not received a
  response so decided to report this

  gnome-control-center 1:40.0-1ubuntu5 is installed
  vino 3.22.0-6ubuntu3

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


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

[Desktop-packages] [Bug 1950461] Re: Installing vino does not expose the screen sharing slider in Gnome Control Center

[Matt Dale]

Thanks for getting back to me. I have never heard of gnome-remote-
desktop before. Installing it cures the issue that I've been having.

Yes, I meant the minimal install from ubiquity.

I would consider this lack of knowledge on my part but I will update the
threads on askubuntu and reddit with the solution as I'm sure others
will encounter the same.

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

Title:
  Installing vino does not expose the screen sharing slider in Gnome
  Control Center

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

Bug description:
  Ubuntu 21.10 - minimal install on a fresh machine

  apt install vino

  Open the gnome settings dialog and go to the Sharing tab. I would
  expect to see the screen sharing slider but it is not there.

  Searching around I found a suggestion to use Ubunutu with Xorg but
  this makes no difference.

  This behaviour is also present in 21.04.

  I have put gnome-control-center as the package at fault as this is
  ultimately where I observe the issue but it may be that during the
  install of vino makes the gnome configuration change and this step is
  missed.

  I have enquired on askubuntu and reddit but have not received a
  response so decided to report this

  gnome-control-center 1:40.0-1ubuntu5 is installed
  vino 3.22.0-6ubuntu3

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


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

[Desktop-packages] [Bug 1950461] [NEW] Installing vino does not expose the screen sharing slider in Gnome Control Center

[Matt Dale]

Public bug reported:

Ubuntu 21.10 - minimal install on a fresh machine

apt install vino

Open the gnome settings dialog and go to the Sharing tab. I would expect
to see the screen sharing slider but it is not there.

Searching around I found a suggestion to use Ubunutu with Xorg but this
makes no difference.

This behaviour is also present in 21.04.

I have put gnome-control-center as the package at fault as this is
ultimately where I observe the issue but it may be that during the
install of vino makes the gnome configuration change and this step is
missed.

I have enquired on askubuntu and reddit but have not received a response
so decided to report this

gnome-control-center 1:40.0-1ubuntu5 is installed
vino 3.22.0-6ubuntu3

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


** Tags: minimal screen sharing vino

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

Title:
  Installing vino does not expose the screen sharing slider in Gnome
  Control Center

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

Bug description:
  Ubuntu 21.10 - minimal install on a fresh machine

  apt install vino

  Open the gnome settings dialog and go to the Sharing tab. I would
  expect to see the screen sharing slider but it is not there.

  Searching around I found a suggestion to use Ubunutu with Xorg but
  this makes no difference.

  This behaviour is also present in 21.04.

  I have put gnome-control-center as the package at fault as this is
  ultimately where I observe the issue but it may be that during the
  install of vino makes the gnome configuration change and this step is
  missed.

  I have enquired on askubuntu and reddit but have not received a
  response so decided to report this

  gnome-control-center 1:40.0-1ubuntu5 is installed
  vino 3.22.0-6ubuntu3

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


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

[Desktop-packages] [Bug 1824874] Re: undismissable, unclickable authentication dialog left on screen (top-left corner) after policykit authentication [pushModal: invocation of begin_modal failed]

[Matt]

Just got this yet again. Looked it up before and waited because I saw
progress. Glad to see restarting WM wasn't the accepted "fix". Really
does come off as a shady auth prompt that end users shouldn't be faced
with.

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

Title:
  undismissable, unclickable authentication dialog left on screen (top-
  left corner) after policykit authentication [pushModal: invocation of
  begin_modal failed]

Status in GNOME Shell:
  Unknown
Status in gnome-shell package in Ubuntu:
  Fix Released

Bug description:
  In disco, when policykit prompted me for a password in order for
  update-manager to dispatch instructions to aptdaemon to perform
  package updates, the password dialog remained on the screen after I
  clicked 'authenticate'.

  The window is not clickable, it appears not to even be a window -
  mouse presses are received by the window underneath.  The exception is
  that the 'cancel' button is active and receives mouse events - but
  clicking it does nothing.

  This may be a gnome-shell issue rather than policykit.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: policykit-1 0.105-25
  ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1
  Uname: Linux 5.0.0-8-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr 15 13:14:33 2019
  InstallationDate: Installed on 2010-09-24 (3125 days ago)
  InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 
(20100816.1)
  SourcePackage: policykit-1
  UpgradeStatus: Upgraded to disco on 2019-04-11 (3 days ago)

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

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

[Desktop-packages] [Bug 1824874] Re: undismissable, unclickable authentication dialog left on screen (top-left corner) after policykit authentication [pushModal: invocation of begin_modal failed]

[Matt]

Just got this for the first time, 20.10. The cancel button reacts to
click but does not dismiss. Looks shady so I'm not going to try my
password. xkill has no effect. I see it's been nearly two years now.

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

Title:
  undismissable, unclickable authentication dialog left on screen (top-
  left corner) after policykit authentication [pushModal: invocation of
  begin_modal failed]

Status in GNOME Shell:
  Unknown
Status in gnome-shell package in Ubuntu:
  Fix Committed

Bug description:
  In disco, when policykit prompted me for a password in order for
  update-manager to dispatch instructions to aptdaemon to perform
  package updates, the password dialog remained on the screen after I
  clicked 'authenticate'.

  The window is not clickable, it appears not to even be a window -
  mouse presses are received by the window underneath.  The exception is
  that the 'cancel' button is active and receives mouse events - but
  clicking it does nothing.

  This may be a gnome-shell issue rather than policykit.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: policykit-1 0.105-25
  ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1
  Uname: Linux 5.0.0-8-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr 15 13:14:33 2019
  InstallationDate: Installed on 2010-09-24 (3125 days ago)
  InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 
(20100816.1)
  SourcePackage: policykit-1
  UpgradeStatus: Upgraded to disco on 2019-04-11 (3 days ago)

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

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

[Desktop-packages] [Bug 1816497] Re: [snap] vaapi chromium no video hardware decoding

[Matt Lee]

Hi Olivier,

Is this branch (and thread) dead? From your last comment, it sounds like
the VA-API code is getting merged into a more mainline branch

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

Title:
  [snap] vaapi chromium no video hardware decoding

Status in chromium-browser package in Ubuntu:
  In Progress

Bug description:
  News :

  - Candidate Chromium 83 Snap with vaapi enabled can be installed with
  :

  sudo snap install --channel=candidate/vaapi chromium

  Check that your vidéo is gpu decoded but checking "MojoVideoDecoder"
  in about:media-internals

  Widevine DRM streams will have DecryptingVideoDecoder

  Please report success/failure with

  - distro version
  - GPU Hardware used
  - Codec used

  --Original Bug report -

  Libva is no longer working for snap installed chromium 72.0.3626.109
  (Official Build) snap (64-bit)

  I followed this instruction
  sudo snap install --channel=candidate/vaapi chromium

  My amdgpu can use libva

  `vainfo: Driver version: Mesa Gallium driver 18.3.3 for AMD STONEY (DRM 
3.27.0, 4.20.0-10.1-liquorix-amd64, LLVM 7.0.1)
  vainfo: Supported profile and entrypoints
    VAProfileMPEG2Simple:   VAEntrypointVLD
    VAProfileMPEG2Main  :   VAEntrypointVLD
    VAProfileVC1Simple  :   VAEntrypointVLD
    VAProfileVC1Main:   VAEntrypointVLD
    VAProfileVC1Advanced:   VAEntrypointVLD
    VAProfileH264ConstrainedBaseline:   VAEntrypointVLD
    VAProfileH264ConstrainedBaseline:   VAEntrypointEncSlice
    VAProfileH264Main   :   VAEntrypointVLD
    VAProfileH264Main   :   VAEntrypointEncSlice
    VAProfileH264High   :   VAEntrypointVLD
    VAProfileH264High   :   VAEntrypointEncSlice
    VAProfileHEVCMain   :   VAEntrypointVLD
    VAProfileHEVCMain10 :   VAEntrypointVLD
    VAProfileJPEGBaseline   :   VAEntrypointVLD
    VAProfileNone   :   VAEntrypointVideoProc`

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

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

[Desktop-packages] [Bug 1816497] Re: [snap] vaapi chromium no video hardware decoding

[Matt Lee]

Hi Olivier,

Have you had a chance to look into why hardware decoding seems to broken
now?

Thanks, Matt.

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

Title:
  [snap] vaapi chromium no video hardware decoding

Status in chromium-browser package in Ubuntu:
  In Progress

Bug description:
  News :

  - Candidate Chromium 83 Snap with vaapi enabled can be installed with
  :

  sudo snap install --channel=candidate/vaapi chromium

  Check that your vidéo is gpu decoded but checking "MojoVideoDecoder"
  in about:media-internals

  Widevine DRM streams will have DecryptingVideoDecoder

  Please report success/failure with

  - distro version
  - GPU Hardware used
  - Codec used

  --Original Bug report -

  Libva is no longer working for snap installed chromium 72.0.3626.109
  (Official Build) snap (64-bit)

  I followed this instruction
  sudo snap install --channel=candidate/vaapi chromium

  My amdgpu can use libva

  `vainfo: Driver version: Mesa Gallium driver 18.3.3 for AMD STONEY (DRM 
3.27.0, 4.20.0-10.1-liquorix-amd64, LLVM 7.0.1)
  vainfo: Supported profile and entrypoints
    VAProfileMPEG2Simple:   VAEntrypointVLD
    VAProfileMPEG2Main  :   VAEntrypointVLD
    VAProfileVC1Simple  :   VAEntrypointVLD
    VAProfileVC1Main:   VAEntrypointVLD
    VAProfileVC1Advanced:   VAEntrypointVLD
    VAProfileH264ConstrainedBaseline:   VAEntrypointVLD
    VAProfileH264ConstrainedBaseline:   VAEntrypointEncSlice
    VAProfileH264Main   :   VAEntrypointVLD
    VAProfileH264Main   :   VAEntrypointEncSlice
    VAProfileH264High   :   VAEntrypointVLD
    VAProfileH264High   :   VAEntrypointEncSlice
    VAProfileHEVCMain   :   VAEntrypointVLD
    VAProfileHEVCMain10 :   VAEntrypointVLD
    VAProfileJPEGBaseline   :   VAEntrypointVLD
    VAProfileNone   :   VAEntrypointVideoProc`

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

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

[Desktop-packages] [Bug 1681290] Re: UI experiences delay when menu / tooltip disappears

[Matt]

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

Bug 1181666 does not at all describe the issue we are having here.

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

Title:
  UI experiences delay when menu / tooltip disappears

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  Sometimes the system will not respond to mouse clicks or keypresses.
  This appears to happen when I hold the mouse over an item and a pop-up
  tooltip appears, or when I click on a menu.  I believe it happens when
  the tooltip/menu is set to disappear.

  Steps to reproduce are:
   1) Select a menu item
   2) Click outside the menu
   3) The click won't register for around 7 or 8 seconds.  No other keypresses 
register immediately but will occur around 7 seconds later. 

  This occurs in GNOME, GNOME applications and also for non-GNOME
  applications such as Firefox and Chrome.

  
  lsb_release -rd:

  Description:  Ubuntu Zesty Zapus (development branch)
  Release:  17.04


  apt-cache policy gnome-session:

  gnome-session:
Installed: 3.24.0-0ubuntu1
Candidate: 3.24.0-0ubuntu1
Version table:
   *** 3.24.0-0ubuntu1 500
  500 http://nz.archive.ubuntu.com/ubuntu zesty/universe amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: gnome-shell 3.24.0-0ubuntu2
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic x86_64
  ApportVersion: 2.20.4-0ubuntu3
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Apr 10 11:39:40 2017
  DisplayManager: gdm3
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-05-12 (332 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Release amd64 
(20160421)
  ProcEnviron:
   LANGUAGE=en_NZ:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_NZ.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to zesty on 2017-04-08 (1 days ago)

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

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

[Desktop-packages] [Bug 1681290] Re: UI experiences delay when menu / tooltip disappears

[Matt]

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

Forgot to mention, menus in gnome-shell itself (top bar, dock, and other
panels) do not suffer from this delay. They close immediately. This
ticket is associated with gnome-shell, but the way the original author
describes it, the shell isn't affected for them either: "This occurs in
GNOME, GNOME applications and also for non-GNOME applications such as
Firefox and Chrome."

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

Title:
  UI experiences delay when menu / tooltip disappears

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  Sometimes the system will not respond to mouse clicks or keypresses.
  This appears to happen when I hold the mouse over an item and a pop-up
  tooltip appears, or when I click on a menu.  I believe it happens when
  the tooltip/menu is set to disappear.

  Steps to reproduce are:
   1) Select a menu item
   2) Click outside the menu
   3) The click won't register for around 7 or 8 seconds.  No other keypresses 
register immediately but will occur around 7 seconds later. 

  This occurs in GNOME, GNOME applications and also for non-GNOME
  applications such as Firefox and Chrome.

  
  lsb_release -rd:

  Description:  Ubuntu Zesty Zapus (development branch)
  Release:  17.04


  apt-cache policy gnome-session:

  gnome-session:
Installed: 3.24.0-0ubuntu1
Candidate: 3.24.0-0ubuntu1
Version table:
   *** 3.24.0-0ubuntu1 500
  500 http://nz.archive.ubuntu.com/ubuntu zesty/universe amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: gnome-shell 3.24.0-0ubuntu2
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic x86_64
  ApportVersion: 2.20.4-0ubuntu3
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Apr 10 11:39:40 2017
  DisplayManager: gdm3
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-05-12 (332 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Release amd64 
(20160421)
  ProcEnviron:
   LANGUAGE=en_NZ:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_NZ.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to zesty on 2017-04-08 (1 days ago)

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

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

[Desktop-packages] [Bug 1681290] Re: UI experiences delay when menu / tooltip disappears

[Matt]

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

I'm having this problem years later in Gnome 3.36.3, Ubuntu 20.04.1. It
also happened in 19.x. I don't think it's a duplicate of #1181666
because that states some interaction is still possible. In this issue,
the whole ui is stuck. Windows, shell, clock, video that's playing,
everything but the mouse cursor. Done a lot of searching for a newer
ticket but none is a dead ringer like this.

The problem develops a while (hours?) after a fresh start and seems to
get more exaggerated as time passes. On a larger scope, a fresh install
is free of this problem at first, and then it develops after days/weeks
of normal use. Had a hunch that it started after installing a particular
package, but I can't remember what it was for the life of me. Clutter?
Wxwidgets? Just a hunch anyway.

Closing of menus, tooltips, and to some degree open/save dialogs are
delayed up to many seconds. This makes interacting with file managers
and web pages infuriating. I have interface sounds on (smooth soundset,
which includes menu actions) and noticed that opening a window menu and
scrubbing the mouse over the other top level items (file, edit, etc.)
still produces sound while this is going on, and the total wait time
until the display unsticks is compounded with every one. ***To me this
says it's not "no click" so much as "can't see".*** After zigging back
and forth I can be waiting a minute or more, meanwhile I can still hear
music playing, etc.

Regarding comment 2, I've not yet tried deleting my gnome settings
because I didn't want to gum things up, but regardless I'm not sure how
that implies this should be closed or is invalid. Gnome shouldn't be
doing things to that file that interfere with its own operation, right?
Again, this is from everyday use, and I've not been messing around in
things.

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

Title:
  UI experiences delay when menu / tooltip disappears

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  Sometimes the system will not respond to mouse clicks or keypresses.
  This appears to happen when I hold the mouse over an item and a pop-up
  tooltip appears, or when I click on a menu.  I believe it happens when
  the tooltip/menu is set to disappear.

  Steps to reproduce are:
   1) Select a menu item
   2) Click outside the menu
   3) The click won't register for around 7 or 8 seconds.  No other keypresses 
register immediately but will occur around 7 seconds later. 

  This occurs in GNOME, GNOME applications and also for non-GNOME
  applications such as Firefox and Chrome.

  
  lsb_release -rd:

  Description:  Ubuntu Zesty Zapus (development branch)
  Release:  17.04


  apt-cache policy gnome-session:

  gnome-session:
Installed: 3.24.0-0ubuntu1
Candidate: 3.24.0-0ubuntu1
Version table:
   *** 3.24.0-0ubuntu1 500
  500 http://nz.archive.ubuntu.com/ubuntu zesty/universe amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: gnome-shell 3.24.0-0ubuntu2
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic x86_64
  ApportVersion: 2.20.4-0ubuntu3
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Apr 10 11:39:40 2017
  DisplayManager: gdm3
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-05-12 (332 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Release amd64 
(20160421)
  ProcEnviron:
   LANGUAGE=en_NZ:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_NZ.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to zesty on 2017-04-08 (1 days ago)

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

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

[Desktop-packages] [Bug 1816497] Re: [snap] vaapi chromium no video hardware decoding

[Matt Lee]

I'm seeing the same problem. Debug information below.

LIBVA_MESSAGING_LEVEL=2 snap run chromium
[20382:20382:0821/200854.560443:ERROR:sandbox_linux.cc(374)] 
InitializeSandbox() called with multiple threads in process gpu-process.
[20548:13:0821/200904.074169:ERROR:batching_media_log.cc(38)] MediaEvent: 
{"error":"{\"causes\":[{\"causes\":[],\"data\":{},\"stack\":[{\"file\":\"../../media/filters/decrypting_video_decoder.cc\",\"line\":53}],\"status_code\":264,\"status_message\":\"\"}],\"data\":{\"Decoder
 
name\":\"DecryptingVideoDecoder\"},\"stack\":[{\"file\":\"../../media/filters/decoder_selector.cc\",\"line\":172}],\"status_code\":265,\"status_message\":\"\"}"}
[20248:20383:0821/200904.173566:ERROR:object_proxy.cc(622)] Failed to call 
method: org.freedesktop.PowerManagement.Inhibit.Inhibit: object_path= 
/org/freedesktop/PowerManagement/Inhibit: 
org.freedesktop.DBus.Error.AccessDenied: An AppArmor policy prevents this 
sender from sending this message to this recipient; type="method_call", 
sender=":1.504" (uid=1000 pid=20248 
comm="/snap/chromium/1260/usr/lib/chromium-browser/chrom" 
label="snap.chromium.chromium (enforce)") 
interface="org.freedesktop.PowerManagement.Inhibit" member="Inhibit" error 
name="(unset)" requested_reply="0" 
destination="org.freedesktop.PowerManagement" (uid=1000 pid=1571 
comm="xfce4-power-manager " label="unconfined")
[20248:20383:0821/200904.173588:ERROR:power_save_blocker_linux.cc(373)] No 
response to Inhibit() request!
[20248:20383:0821/200904.379145:ERROR:object_proxy.cc(622)] Failed to call 
method: org.freedesktop.PowerManagement.Inhibit.Inhibit: object_path= 
/org/freedesktop/PowerManagement/Inhibit: 
org.freedesktop.DBus.Error.AccessDenied: An AppArmor policy prevents this 
sender from sending this message to this recipient; type="method_call", 
sender=":1.505" (uid=1000 pid=20248 
comm="/snap/chromium/1260/usr/lib/chromium-browser/chrom" 
label="snap.chromium.chromium (enforce)") 
interface="org.freedesktop.PowerManagement.Inhibit" member="Inhibit" error 
name="(unset)" requested_reply="0" 
destination="org.freedesktop.PowerManagement" (uid=1000 pid=1571 
comm="xfce4-power-manager " label="unconfined")
[20248:20383:0821/200904.379183:ERROR:power_save_blocker_linux.cc(373)] No 
response to Inhibit() request!
[20248:20248:0821/200913.822437:ERROR:event_router.cc(713)] Event dispatched 
while shutting down extensions browser client.

libva info: VA-API version 1.8.0
libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so
libva info: Found init function __vaDriverInit_1_8
libva info: va_openDriver() returns 0
vainfo: VA-API version: 1.8 (libva 2.1.0)
vainfo: Driver version: Intel iHD driver for Intel(R) Gen Graphics - 20.2.pre 
(f403839f)
vainfo: Supported profile and entrypoints
  VAProfileNone   : VAEntrypointVideoProc
  VAProfileNone   : VAEntrypointStats
  VAProfileMPEG2Simple: VAEntrypointVLD
  VAProfileMPEG2Simple: VAEntrypointEncSlice
  VAProfileMPEG2Main  : VAEntrypointVLD
  VAProfileMPEG2Main  : VAEntrypointEncSlice
  VAProfileH264Main   : VAEntrypointVLD
  VAProfileH264Main   : VAEntrypointEncSlice
  VAProfileH264Main   : VAEntrypointFEI
  VAProfileH264Main   : VAEntrypointEncSliceLP
  VAProfileH264High   : VAEntrypointVLD
  VAProfileH264High   : VAEntrypointEncSlice
  VAProfileH264High   : VAEntrypointFEI
  VAProfileH264High   : VAEntrypointEncSliceLP
  VAProfileVC1Simple  : VAEntrypointVLD
  VAProfileVC1Main: VAEntrypointVLD
  VAProfileVC1Advanced: VAEntrypointVLD
  VAProfileJPEGBaseline   : VAEntrypointVLD
  VAProfileJPEGBaseline   : VAEntrypointEncPicture
  VAProfileH264ConstrainedBaseline: VAEntrypointVLD
  VAProfileH264ConstrainedBaseline: VAEntrypointEncSlice
  VAProfileH264ConstrainedBaseline: VAEntrypointFEI
  VAProfileH264ConstrainedBaseline: VAEntrypointEncSliceLP
  VAProfileVP8Version0_3  : VAEntrypointVLD
  VAProfileVP8Version0_3  : VAEntrypointEncSlice
  VAProfileHEVCMain   : VAEntrypointVLD
  VAProfileHEVCMain   : VAEntrypointEncSlice
  VAProfileHEVCMain   : VAEntrypointFEI
  VAProfileHEVCMain10 : VAEntrypointVLD
  VAProfileHEVCMain10 : VAEntrypointEncSlice
  VAProfileVP9Profile0: VAEntrypointVLD
  VAProfileVP9Profile2: VAEntrypointVLD

audio_buffering_state   {"state":"BUFFERING_HAVE_ENOUGH"}
dimensions  "1920x988"
duration243.981
error   
"{\"causes\":[{\"causes\":[],\"data\":{},\"stack\":[{\"file\":\"../../media/filters/decrypting_video_decoder.cc\",\"line\":53}],\"status_code\":264,\"status_message\":\"\"}],\"data\":{\"Decoder
 
name\":\"DecryptingVideoDe

[Desktop-packages] [Bug 1874567] Re: [nvidia] Rotating secondary monitor to portrait fails, results in landscape

[Matt Austin]

Thank you for fixing this bug. Installing mutter 3.36.4-0ubuntu0.20.04.1
and libmutter 3.36.4-0ubuntu0.20.04.1 from focal-proposed has resolved
this issue for me.

Note: The updated libmutter from focal-proposed also had to be
explicitly installed by me, as it was not automatically pulled in when
updating mutter.

Steps:
1) Enabled focal-proposed
2) apt update
3) apt install mutter libmutter
4) Disabled focal-proposed
5) Removed ~/.config/monitors.xml and ~gdm/config/monitors.xml
6) Rebooted
7) After login, I successfully applied my desired monitor configuration 
(changing the primary monitor and setting other monitor to portrait 
orientation).


Side notes:
1) I still had to copy ~/.config/monitors.xml to ~gdm/.config/monitors.xml for 
the correct primary monitor and orientation to be set on the login screen.
2) After applying the display configuration, the icons in the top-right of the 
gnome panel appeared blured (network/bluetooth). This was resolved by applying 
150% fractional scaling and then applying 100% scaling again in the gnome 
display settings. I haven't had time to reproduce this to know if it's a 
one-off or ongoing bug.

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

Title:
  [nvidia] Rotating secondary monitor to portrait fails, results in
  landscape

Status in OEM Priority Project:
  New
Status in gnome-control-center package in Ubuntu:
  Won't Fix
Status in mutter package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Won't Fix
Status in nvidia-graphics-drivers-435 package in Ubuntu:
  Won't Fix
Status in nvidia-graphics-drivers-440 package in Ubuntu:
  Won't Fix
Status in gnome-control-center source package in Focal:
  Won't Fix
Status in mutter source package in Focal:
  Fix Committed
Status in nvidia-graphics-drivers-340 source package in Focal:
  Won't Fix
Status in nvidia-graphics-drivers-435 source package in Focal:
  Won't Fix
Status in nvidia-graphics-drivers-440 source package in Focal:
  Won't Fix

Bug description:
  [ Impact ]

  I have two monitors, with the secondary one rotated in a portrait
  orientation. Using the nvidia 440 drivers, the orientation is not
  applied when configuring in gnome settings (the displays go blank for
  a second, and then reappear in landscape orientation).

  Using nvidia settings, I can set the monitor rotation and offset
  correctly, however these settings do not persist on next boot (even
  when selecting to save to xorg.conf).

  When using the nouveau drivers, the orientation is applied correctly
  in gnome settings, and is persisted.

  [ Test case ]

  1. Install nvidia drivers
  2. Configure an external monitor to be in portrait mode in 
gnome-control-center
  3. Apply the configuration
  4. Expect configuration is properly working

  [ Regression potential ]

  Wrong screen size is set and panning is used.

  

  ProblemType: BugDistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-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  440.64  Fri Feb 21 01:17:26 
UTC 2020
   GCC version:  gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2)
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Fri Apr 24 08:30:41 2020
  DistUpgraded: 2020-04-20 18:27:13,972 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 440.64, 5.4.0-26-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation GK106 [GeForce GTX 660] [10de:11c0] (rev a1) (prog-if 00 
[VGA controller])
     Subsystem: Micro-Star International Co., Ltd. [MSI] GK106 [GeForce GTX 
660] [1462:2871]
  InstallationDate: Installed on 2018-05-01 (723 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: Shuttle Inc. SZ77
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic 
root=UUID=d2c17cee-7c37-429f-9cbb-9484a159f182 ro quiet splash 
vt.handoff=7SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to focal on 2020-04-20 (3 days ago)
  dmi.bios.date: 10/13/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bi

[Desktop-packages] [Bug 1870736] Re: [nvidia] Screen scaling 125% gives 200%

[Matt Hurd]

Confirmed bug on 20.04 with Nvidia 440 here too on 970M. Noveau works
fine but the tablet is pretty unusable slow, so have to use NV440 with
an uncomfortable resolution on the main screen :-(

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

Title:
  [nvidia] Screen scaling 125% gives 200%

Status in gnome-control-center package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  Procedure used:
  1.
  Fully updated system via apt update && apt upgrade

  2.
  Select the screen setup in gnome control center

  3. 
  Click the "Fractional scaling" toggle

  4. 
  Select 125% and click the green "use" button top right (it says "Anvend" in 
dansih)

  5.
  Observe that the window has grown a lot, click the "use new settings" button

  6.
  The window tells me, I am at 200% scaling. The "200%" option is now 
highlighted.

  7.
  Switch back to 100% and file this bug.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubuntu-release-upgrader-core 1:20.04.16
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr  4 09:42:34 2020
  InstallationDate: Installed on 2018-01-14 (810 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=da_DK.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-release-upgrader
  Symptom: release-upgrade
  UpgradeStatus: Upgraded to focal on 2020-04-03 (0 days ago)

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

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

[Desktop-packages] [Bug 1816497] Re: [snap] vaapi chromium no video hardware decoding

[Matt Lee]

Thanks Olivier. I'll keep my eye out for that, so I can test

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

Title:
  [snap] vaapi chromium no video hardware decoding

Status in chromium-browser package in Ubuntu:
  In Progress

Bug description:
  News :

  - Beta Chromium 80 Snap with vaapi enabled :

  https://code.launchpad.net/~chromium-team/+snap/chromium-snap-from-
  source-enable-
  vaapi/+build/918074/+files/chromium_81.0.4044.113_amd64.snap

  Install it with --devmode

  
  --Original Bug report -

  Libva is no longer working for snap installed chromium 72.0.3626.109
  (Official Build) snap (64-bit)

  I followed this instruction
  sudo snap install --channel=candidate/vaapi chromium

  My amdgpu can use libva

  `vainfo: Driver version: Mesa Gallium driver 18.3.3 for AMD STONEY (DRM 
3.27.0, 4.20.0-10.1-liquorix-amd64, LLVM 7.0.1)
  vainfo: Supported profile and entrypoints
    VAProfileMPEG2Simple:   VAEntrypointVLD
    VAProfileMPEG2Main  :   VAEntrypointVLD
    VAProfileVC1Simple  :   VAEntrypointVLD
    VAProfileVC1Main:   VAEntrypointVLD
    VAProfileVC1Advanced:   VAEntrypointVLD
    VAProfileH264ConstrainedBaseline:   VAEntrypointVLD
    VAProfileH264ConstrainedBaseline:   VAEntrypointEncSlice
    VAProfileH264Main   :   VAEntrypointVLD
    VAProfileH264Main   :   VAEntrypointEncSlice
    VAProfileH264High   :   VAEntrypointVLD
    VAProfileH264High   :   VAEntrypointEncSlice
    VAProfileHEVCMain   :   VAEntrypointVLD
    VAProfileHEVCMain10 :   VAEntrypointVLD
    VAProfileJPEGBaseline   :   VAEntrypointVLD
    VAProfileNone   :   VAEntrypointVideoProc`

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

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

[Desktop-packages] [Bug 1816497] Re: [snap] vaapi chromium no video hardware decoding

[Matt Lee]

HW acceleration doesn't work for me in the latest build. I noted that
Olivier was going to build with a newer version of libva so I went ahead
an installed the latest version, as per this guide:
https://github.com/intel/media-driver/wiki/How-to-build-and-use-media-
driver%3F. Unfortunately that did not change the behavior, so I still
see kVideoDecoderName="VpxVideoDecoder"

snap info --abs-time chromium & vainfo dumps below:

name:  chromium
summary:   Chromium web browser, open-source version of Chrome
publisher: Canonical*
store-url: https://snapcraft.io/chromium
contact:   
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bugs?field.tag=snap
license:   unset
description: |
  An open-source browser project that aims to build a safer, faster, and more 
stable way for all
  Internet users to experience the web.
commands:
  - chromium.chromedriver
  - chromium
snap-id:  XKEcBqPM06H1Z7zGOdG5fbICuf8NWK5R
tracking: latest/candidate/vaapi
refresh-date: 2020-05-17T17:46:48-07:00
channels:
  latest/stable:81.0.4044.138 2020-05-06T18:11:18Z (1143) 161MB -
  latest/candidate: 81.0.4044.138 2020-05-06T14:20:15Z (1143) 161MB -
  latest/beta:  83.0.4103.56  2020-05-15T02:46:16Z (1155) 163MB -
  latest/edge:  84.0.4143.2   2020-05-13T04:57:20Z (1154) 164MB -
installed:  81.0.4044.138  (1162) 162MB -

libva info: VA-API version 1.8.0
libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so
libva info: Found init function __vaDriverInit_1_8
libva info: va_openDriver() returns 0
vainfo: VA-API version: 1.8 (libva 2.1.0)
vainfo: Driver version: Intel iHD driver for Intel(R) Gen Graphics - 20.2.pre 
(f403839f)
vainfo: Supported profile and entrypoints
  VAProfileNone   : VAEntrypointVideoProc
  VAProfileNone   : VAEntrypointStats
  VAProfileMPEG2Simple: VAEntrypointVLD
  VAProfileMPEG2Simple: VAEntrypointEncSlice
  VAProfileMPEG2Main  : VAEntrypointVLD
  VAProfileMPEG2Main  : VAEntrypointEncSlice
  VAProfileH264Main   : VAEntrypointVLD
  VAProfileH264Main   : VAEntrypointEncSlice
  VAProfileH264Main   : VAEntrypointFEI
  VAProfileH264Main   : VAEntrypointEncSliceLP
  VAProfileH264High   : VAEntrypointVLD
  VAProfileH264High   : VAEntrypointEncSlice
  VAProfileH264High   : VAEntrypointFEI
  VAProfileH264High   : VAEntrypointEncSliceLP
  VAProfileVC1Simple  : VAEntrypointVLD
  VAProfileVC1Main: VAEntrypointVLD
  VAProfileVC1Advanced: VAEntrypointVLD
  VAProfileJPEGBaseline   : VAEntrypointVLD
  VAProfileJPEGBaseline   : VAEntrypointEncPicture
  VAProfileH264ConstrainedBaseline: VAEntrypointVLD
  VAProfileH264ConstrainedBaseline: VAEntrypointEncSlice
  VAProfileH264ConstrainedBaseline: VAEntrypointFEI
  VAProfileH264ConstrainedBaseline: VAEntrypointEncSliceLP
  VAProfileVP8Version0_3  : VAEntrypointVLD
  VAProfileVP8Version0_3  : VAEntrypointEncSlice
  VAProfileHEVCMain   : VAEntrypointVLD
  VAProfileHEVCMain   : VAEntrypointEncSlice
  VAProfileHEVCMain   : VAEntrypointFEI
  VAProfileHEVCMain10 : VAEntrypointVLD
  VAProfileHEVCMain10 : VAEntrypointEncSlice
  VAProfileVP9Profile0: VAEntrypointVLD
  VAProfileVP9Profile2: VAEntrypointVLD

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

Title:
  [snap] vaapi chromium no video hardware decoding

Status in chromium-browser package in Ubuntu:
  In Progress

Bug description:
  News :

  - Beta Chromium 80 Snap with vaapi enabled :

  https://code.launchpad.net/~chromium-team/+snap/chromium-snap-from-
  source-enable-
  vaapi/+build/918074/+files/chromium_81.0.4044.113_amd64.snap

  Install it with --devmode

  
  --Original Bug report -

  Libva is no longer working for snap installed chromium 72.0.3626.109
  (Official Build) snap (64-bit)

  I followed this instruction
  sudo snap install --channel=candidate/vaapi chromium

  My amdgpu can use libva

  `vainfo: Driver version: Mesa Gallium driver 18.3.3 for AMD STONEY (DRM 
3.27.0, 4.20.0-10.1-liquorix-amd64, LLVM 7.0.1)
  vainfo: Supported profile and entrypoints
    VAProfileMPEG2Simple:   VAEntrypointVLD
    VAProfileMPEG2Main  :   VAEntrypointVLD
    VAProfileVC1Simple  :   VAEntrypointVLD
    VAProfileVC1Main:   VAEntrypointVLD
    VAProfileVC1Advanced:   VAEntrypointVLD
    VAProfileH264ConstrainedBaseline:   VAEntrypointVLD
    VAProfileH264

[Desktop-packages] [Bug 1851621] Re: [snap] No KDE file dialogs

[Matt Papageorge]

+1 I am also being affected by this bug. It is very frustrating, so far
moving Chromium to snap on Kubuntu has caused lots of annoying issues
for me, definitely a step back.

I am a BIOS developer, willing to help out in any way I can. But this
may be too high up the stack for me to be able to fix in a reasonable
amount of time.

I guess how much I want to debug this myself directly correlates on how
annoyed by it I am. That annoyance is growing...

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

Title:
  [snap] No KDE file dialogs

Status in chromium-browser package in Ubuntu:
  Confirmed

Bug description:
  I upgraded from kubuntu 19.04 to 19.10 and noticed that chromium does
  not integrate anymore. Plasma integration Fails to connect to the
  native host (suggested google solutions didn't work), Kubuntu mouse
  pointers change to ugly ones (I bellive GTK fallback), no kde file
  dialog when opening/saving files.

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

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

[Desktop-packages] [Bug 1778592] Re: Tooltip not shown when hovering the mouse

[Matt Giuca]

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

** This bug has been marked a duplicate of bug 1768074
   Mouseover does not show folder names reliably

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

Title:
  Tooltip not shown when hovering the mouse

Status in baobab package in Ubuntu:
  Confirmed
Status in baobab package in Arch Linux:
  New

Bug description:
  Using baobab 3.28.0-1 in Ubuntu 18.04 LTS (tested in 2 different
  machines):

  When hovering the mouse over the ringschart or the treemap, it should
  show a tooltip with the name of the folders or files. Instead, it
  "glows" for a second and then goes back to original color, without
  showing the tooltip.

  A short video showing this behaviour is here:
  https://youtu.be/SCPcXak9d3E

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

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

[Desktop-packages] [Bug 1874567] Re: Secondary (rotated) monitor configuration is not applied correctly in gnome settings

[Matt Austin]

** Attachment added: "Screenshot from 2020-04-24 08-37-43.png"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1874567/+attachment/5358812/+files/Screenshot%20from%202020-04-24%2008-37-43.png

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

Title:
  Secondary (rotated) monitor configuration is not applied correctly in
  gnome settings

Status in xorg package in Ubuntu:
  New

Bug description:
  I have two monitors, with the secondary one rotated in a portrait
  orientation. Using the nvidia 440 drivers, the orientation is not
  applied when configuring in gnome settings (the displays go blank for
  a second, and then reappear in landscape orientation).

  Using nvidia settings, I can set the monitor rotation and offset
  correctly, however these settings do not persist on next boot (even
  when selecting to save to xorg.conf).

  
  When using the nouveau drivers, the orientation is applied correctly in gnome 
settings, and is persisted.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-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  440.64  Fri Feb 21 01:17:26 
UTC 2020
   GCC version:  gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2)
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Fri Apr 24 08:30:41 2020
  DistUpgraded: 2020-04-20 18:27:13,972 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 440.64, 5.4.0-26-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation GK106 [GeForce GTX 660] [10de:11c0] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Micro-Star International Co., Ltd. [MSI] GK106 [GeForce GTX 
660] [1462:2871]
  InstallationDate: Installed on 2018-05-01 (723 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: Shuttle Inc. SZ77
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic 
root=UUID=d2c17cee-7c37-429f-9cbb-9484a159f182 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to focal on 2020-04-20 (3 days ago)
  dmi.bios.date: 10/13/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.13
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: FZ77
  dmi.board.vendor: Shuttle Inc.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.13:bd10/13/2014:svnShuttleInc.:pnSZ77:pvr1.0:rvnShuttleInc.:rnFZ77:rvr1.0:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: SZ77
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 1.0
  dmi.sys.vendor: Shuttle Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
  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.8-2ubuntu2
  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+git20200226-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/1874567/+subscriptions

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

[Desktop-packages] [Bug 1874567] [NEW] Secondary (rotated) monitor configuration is not applied correctly in gnome settings

[Matt Austin]

Public bug reported:

I have two monitors, with the secondary one rotated in a portrait
orientation. Using the nvidia 440 drivers, the orientation is not
applied when configuring in gnome settings (the displays go blank for a
second, and then reappear in landscape orientation).

Using nvidia settings, I can set the monitor rotation and offset
correctly, however these settings do not persist on next boot (even when
selecting to save to xorg.conf).


When using the nouveau drivers, the orientation is applied correctly in gnome 
settings, and is persisted.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
Uname: Linux 5.4.0-26-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  440.64  Fri Feb 21 01:17:26 
UTC 2020
 GCC version:  gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2)
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: GNOME
Date: Fri Apr 24 08:30:41 2020
DistUpgraded: 2020-04-20 18:27:13,972 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
DistroCodename: focal
DistroVariant: ubuntu
DkmsStatus: nvidia, 440.64, 5.4.0-26-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
 NVIDIA Corporation GK106 [GeForce GTX 660] [10de:11c0] (rev a1) (prog-if 00 
[VGA controller])
   Subsystem: Micro-Star International Co., Ltd. [MSI] GK106 [GeForce GTX 660] 
[1462:2871]
InstallationDate: Installed on 2018-05-01 (723 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
MachineType: Shuttle Inc. SZ77
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_AU.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic 
root=UUID=d2c17cee-7c37-429f-9cbb-9484a159f182 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to focal on 2020-04-20 (3 days ago)
dmi.bios.date: 10/13/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1.13
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: FZ77
dmi.board.vendor: Shuttle Inc.
dmi.board.version: 1.0
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.13:bd10/13/2014:svnShuttleInc.:pnSZ77:pvr1.0:rvnShuttleInc.:rnFZ77:rvr1.0:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: SZ77
dmi.product.sku: To be filled by O.E.M.
dmi.product.version: 1.0
dmi.sys.vendor: Shuttle Inc.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.101-2
version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
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.8-2ubuntu2
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+git20200226-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


** Tags: amd64 apport-bug focal nvidia ubuntu

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

Title:
  Secondary (rotated) monitor configuration is not applied correctly in
  gnome settings

Status in xorg package in Ubuntu:
  New

Bug description:
  I have two monitors, with the secondary one rotated in a portrait
  orientation. Using the nvidia 440 drivers, the orientation is not
  applied when configuring in gnome settings (the displays go blank for
  a second, and then reappear in landscape orientation).

  Using nvidia settings, I can set the monitor rotation and offset
  correctly, however these settings do not persist on next boot (even
  when selecting to save to xorg.conf).

  
  When using the nouveau drivers, the orientation is applied correctly in gnome 
settings, and is persisted.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-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.

[Desktop-packages] [Bug 1866974] Re: The Diffie-Hellman prime sent by the server is not acceptable

[Matt Green]

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

Thank you Simon Déziel! That worked for me too.

I was all set to give up on ubuntu 20 because having a working
evolution-ews is a deal-breaker for me.

I wonder why the linked duplicate thread does not also contain your fix.

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

Title:
  The Diffie-Hellman prime sent by the server is not acceptable

Status in evolution package in Ubuntu:
  Confirmed
Status in gnome-online-accounts package in Ubuntu:
  New

Bug description:
  I can no longer connect to my ISP mail server.
  Works in previous version 19.10

  "The reported error was “Failed to get capabilities: Error performing
  TLS handshake: The Diffie-Hellman prime sent by the server is not
  acceptable (not long enough).”."

  I've tried finding a workaround but so far no luck.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: evolution 3.35.92-1
  ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
  Uname: Linux 5.4.0-18-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu20
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar 11 11:07:01 2020
  InstallationDate: Installed on 2020-03-03 (7 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200303)
  SourcePackage: evolution
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1872778] Re: update-crypto-policies not affecting Gnome Online Accounts

[Matt Green]

The following worked for me: see
https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1866974/comments/8

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

Title:
  update-crypto-policies not affecting Gnome Online Accounts

Status in gnome-online-accounts package in Ubuntu:
  Incomplete
Status in gnutls28 package in Ubuntu:
  Confirmed

Bug description:
  -crypto-policies 20190816git-1
  -gnome-online-accounts 3.36.0-1ubuntu1

  Changing between DEFAULT, LEGACY, and EMPTY has no affect on attempts
  to connect to accounts through Online Accounts.

  Changing to LEGACY or EMPTY should at least change the following
  error:

  Error performing TLS handshake: The Diffie-Hellman prime sent by the
  server is not acceptable (not long enough).

  Under either LEGACY or EMPTY the (not long enough) error is
  nonsensical. The persistence of the incorrect error message could
  imply that gnome-online-accounts is not respecting settings made by
  crypto-policies.

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

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

[Desktop-packages] [Bug 1816497] Re: [snap] vaapi chromium no video hardware decoding

[Matt Lee]

Hi Olivier,

Many thanks for starting that back up! I have install Chromium from the
candidate/vaapi channel and the HW acceleration is working for me.

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

Title:
  [snap] vaapi chromium no video hardware decoding

Status in chromium-browser package in Ubuntu:
  In Progress

Bug description:
  Libva is no longer working for snap installed chromium 72.0.3626.109
  (Official Build) snap (64-bit)

  I followed this instruction
  sudo snap install --channel=candidate/vaapi chromium

  My amdgpu can use libva

  `vainfo: Driver version: Mesa Gallium driver 18.3.3 for AMD STONEY (DRM 
3.27.0, 4.20.0-10.1-liquorix-amd64, LLVM 7.0.1)
  vainfo: Supported profile and entrypoints
VAProfileMPEG2Simple:   VAEntrypointVLD
VAProfileMPEG2Main  :   VAEntrypointVLD
VAProfileVC1Simple  :   VAEntrypointVLD
VAProfileVC1Main:   VAEntrypointVLD
VAProfileVC1Advanced:   VAEntrypointVLD
VAProfileH264ConstrainedBaseline:   VAEntrypointVLD
VAProfileH264ConstrainedBaseline:   VAEntrypointEncSlice
VAProfileH264Main   :   VAEntrypointVLD
VAProfileH264Main   :   VAEntrypointEncSlice
VAProfileH264High   :   VAEntrypointVLD
VAProfileH264High   :   VAEntrypointEncSlice
VAProfileHEVCMain   :   VAEntrypointVLD
VAProfileHEVCMain10 :   VAEntrypointVLD
VAProfileJPEGBaseline   :   VAEntrypointVLD
VAProfileNone   :   VAEntrypointVideoProc`

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

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

[Desktop-packages] [Bug 1816497] Re: [snap] vaapi chromium no video hardware decoding

[Matt Lee]

It does appear to be abandoned, unfortunately. I had hoped that the
official addition of VAAPI support to Firefox would be an alternative
but it is dependent on Wayland, which is not currently default supported
by Ubuntu.

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

Title:
  [snap] vaapi chromium no video hardware decoding

Status in chromium-browser package in Ubuntu:
  Confirmed

Bug description:
  Libva is no longer working for snap installed chromium 72.0.3626.109
  (Official Build) snap (64-bit)

  I followed this instruction
  sudo snap install --channel=candidate/vaapi chromium

  My amdgpu can use libva

  `vainfo: Driver version: Mesa Gallium driver 18.3.3 for AMD STONEY (DRM 
3.27.0, 4.20.0-10.1-liquorix-amd64, LLVM 7.0.1)
  vainfo: Supported profile and entrypoints
VAProfileMPEG2Simple:   VAEntrypointVLD
VAProfileMPEG2Main  :   VAEntrypointVLD
VAProfileVC1Simple  :   VAEntrypointVLD
VAProfileVC1Main:   VAEntrypointVLD
VAProfileVC1Advanced:   VAEntrypointVLD
VAProfileH264ConstrainedBaseline:   VAEntrypointVLD
VAProfileH264ConstrainedBaseline:   VAEntrypointEncSlice
VAProfileH264Main   :   VAEntrypointVLD
VAProfileH264Main   :   VAEntrypointEncSlice
VAProfileH264High   :   VAEntrypointVLD
VAProfileH264High   :   VAEntrypointEncSlice
VAProfileHEVCMain   :   VAEntrypointVLD
VAProfileHEVCMain10 :   VAEntrypointVLD
VAProfileJPEGBaseline   :   VAEntrypointVLD
VAProfileNone   :   VAEntrypointVideoProc`

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

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

[Desktop-packages] [Bug 1859123] [NEW] No global menus (panel-appmenu / dbus) in Firefox 72.0.1

[Matt Mayfield]

Public bug reported:

No global menus are displayed in latest Firefox 72.0.1 (possibly in a
slightly earlier version).

This issue was observed on three different systems all running Ubuntu
MATE 20.04 Focal (development), and I first noticed it on each system
upon updating to 72.0.1 today.

The symptoms are identical to https://bugs.launchpad.net/ubuntu-
mate/+bug/1743687 , but running `env UBUNTU_MENUPROXY=0 firefox` does
not resolve the issue. `env UBUNTU_MENUPROXY=1 firefox` does not resolve
the issue either.

My first guess is that the issue is a change in Firefox, due to how the
previous solution with the environment variable no longer works.
(Perhaps a change to the Unity menu patch?)

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

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

Title:
  No global menus (panel-appmenu / dbus) in Firefox 72.0.1

Status in firefox package in Ubuntu:
  New

Bug description:
  No global menus are displayed in latest Firefox 72.0.1 (possibly in a
  slightly earlier version).

  This issue was observed on three different systems all running Ubuntu
  MATE 20.04 Focal (development), and I first noticed it on each system
  upon updating to 72.0.1 today.

  The symptoms are identical to https://bugs.launchpad.net/ubuntu-
  mate/+bug/1743687 , but running `env UBUNTU_MENUPROXY=0 firefox` does
  not resolve the issue. `env UBUNTU_MENUPROXY=1 firefox` does not
  resolve the issue either.

  My first guess is that the issue is a change in Firefox, due to how
  the previous solution with the environment variable no longer works.
  (Perhaps a change to the Unity menu patch?)

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

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

[Desktop-packages] [Bug 1859033] Re: guile-2.2 installed but not guild-2.2

[Matt Wette]

As a test, download https://github.com/TaylanUB/scheme-
bytestructures/releases/download/v1.0.7/bytestructures-1.0.7.tar.gz,
unpack and run ./configure in the top directory.  Then check the
Makefile and notice that GUILE is defined but not GUILD.  "make" will
fail for that reason.

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

Title:
  guile-2.2 installed but not guild-2.2

Status in guile-2.2 package in Ubuntu:
  New

Bug description:
  guile-2.2 package apparently installs guile, guile-2.2 and guild in
  /usr/bin, but not guild-2.2.  This causes packages using configure w/
  guile.m4 macros to fail: GUILE is defined but not GUILD.  So builds
  which use commands (in the Makefiles) of the form "$(GUILD) compile
  ..." will fail.

  Suggest adding guild-2.2 to the install process.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: guile-2.2 2.2.3+1-3ubuntu0.1
  ProcVersionSignature: Ubuntu 4.15.0-74.84-generic 4.15.18
  Uname: Linux 4.15.0-74-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jan  9 06:30:37 2020
  InstallationDate: Installed on 2019-02-03 (339 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: guile-2.2
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/guile-2.2/+bug/1859033/+subscriptions

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

[Desktop-packages] [Bug 1859033] [NEW] guile-2.2 installed but not guild-2.2

[Matt Wette]

Public bug reported:

guile-2.2 package apparently installs guile, guile-2.2 and guild in
/usr/bin, but not guild-2.2.  This causes packages using configure w/
guile.m4 macros to fail: GUILE is defined but not GUILD.  So builds
which use commands (in the Makefiles) of the form "$(GUILD) compile ..."
will fail.

Suggest adding guild-2.2 to the install process.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: guile-2.2 2.2.3+1-3ubuntu0.1
ProcVersionSignature: Ubuntu 4.15.0-74.84-generic 4.15.18
Uname: Linux 4.15.0-74-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.9
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Thu Jan  9 06:30:37 2020
InstallationDate: Installed on 2019-02-03 (339 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
SourcePackage: guile-2.2
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: guile-2.2 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug bionic

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

Title:
  guile-2.2 installed but not guild-2.2

Status in guile-2.2 package in Ubuntu:
  New

Bug description:
  guile-2.2 package apparently installs guile, guile-2.2 and guild in
  /usr/bin, but not guild-2.2.  This causes packages using configure w/
  guile.m4 macros to fail: GUILE is defined but not GUILD.  So builds
  which use commands (in the Makefiles) of the form "$(GUILD) compile
  ..." will fail.

  Suggest adding guild-2.2 to the install process.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: guile-2.2 2.2.3+1-3ubuntu0.1
  ProcVersionSignature: Ubuntu 4.15.0-74.84-generic 4.15.18
  Uname: Linux 4.15.0-74-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jan  9 06:30:37 2020
  InstallationDate: Installed on 2019-02-03 (339 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: guile-2.2
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/guile-2.2/+bug/1859033/+subscriptions

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

[Desktop-packages] [Bug 1853094] Re: Screen tearing in xorg gnome session on Latitude 7480 with WD19TB Thunderbolt dock

[Matt Austin]

** Attachment added: "lspci -k"
   
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1853094/+attachment/5310908/+files/lspcik.txt

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

Title:
  Screen tearing in xorg gnome session on Latitude 7480 with WD19TB
  Thunderbolt dock

Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  I have the WD19TB Thunderbolt dock connected to a Dell Latitude 7480
  laptop with two external displays. The laptop itself is closed
  (internal display is not used).

  In a gnome xorg session, there is severe tearing on parts of the
  screen when dragging windows or scrolling content.

  Under a wayland session there is no screen tearing, but I have
  keyboard key repetition problems which make this mostly unusable day-
  to-day
  (https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1849405).

  I can supply short phone videos of tearing occurring on the screens if
  required.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: mutter 3.28.4-0ubuntu18.04.2
  ProcVersionSignature: Ubuntu 5.0.0-36.39~18.04.1-generic 5.0.21
  Uname: Linux 5.0.0-36-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Nov 19 14:02:09 2019
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  SourcePackage: mutter
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1853094] Re: Screen tearing in xorg gnome session on Latitude 7480 with WD19TB Thunderbolt dock

[Matt Austin]

** Attachment added: "Xorg.0.log"
   
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1853094/+attachment/5310910/+files/Xorg.0.log

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

Title:
  Screen tearing in xorg gnome session on Latitude 7480 with WD19TB
  Thunderbolt dock

Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  I have the WD19TB Thunderbolt dock connected to a Dell Latitude 7480
  laptop with two external displays. The laptop itself is closed
  (internal display is not used).

  In a gnome xorg session, there is severe tearing on parts of the
  screen when dragging windows or scrolling content.

  Under a wayland session there is no screen tearing, but I have
  keyboard key repetition problems which make this mostly unusable day-
  to-day
  (https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1849405).

  I can supply short phone videos of tearing occurring on the screens if
  required.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: mutter 3.28.4-0ubuntu18.04.2
  ProcVersionSignature: Ubuntu 5.0.0-36.39~18.04.1-generic 5.0.21
  Uname: Linux 5.0.0-36-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Nov 19 14:02:09 2019
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  SourcePackage: mutter
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1846398] Re: Fractional scaling has significant visible tearing in Xorg sessions

[Matt Austin]

Thanks for the feedback, but I don't believe I am using fractional
scaling. My scaling is set to 100%, but I have changed the font scaling
to 1.25.

If I set font scaling to 1.0, then I see the same tearing.

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

Title:
  Fractional scaling has significant visible tearing in Xorg sessions

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

Bug description:
  On my laptop, fractional scaling seems fine, including watching a
  YouTube video. It has a quad HD display.

  Enabling fractional scaling on my desktop which is attached to a
  single 4k display, fractional scaling isn't usable. The video appears
  to be constantly refreshing and not using the same acceleration as if
  I just run at 100% or 200%.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell 3.34.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0
  Uname: Linux 5.3.0-13-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct  2 14:23:33 2019
  DisplayManager: gdm3
  InstallationDate: Installed on 2018-07-24 (435 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180724)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 3.34.0-3ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to eoan on 2019-07-19 (74 days ago)

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

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

[Desktop-packages] [Bug 1853094] Re: Screen tearing in xorg gnome session on Latitude 7480 with WD19TB Thunderbolt dock

[Matt Austin]

** Attachment added: "tearing-1.mp4"
   
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1853094/+attachment/5307224/+files/tearing-1.mp4

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

Title:
  Screen tearing in xorg gnome session on Latitude 7480 with WD19TB
  Thunderbolt dock

Status in mutter package in Ubuntu:
  New

Bug description:
  I have the WD19TB Thunderbolt dock connected to a Dell Latitude 7480
  laptop with two external displays. The laptop itself is closed
  (internal display is not used).

  In a gnome xorg session, there is severe tearing on parts of the
  screen when dragging windows or scrolling content.

  Under a wayland session there is no screen tearing, but I have
  keyboard key repetition problems which make this mostly unusable day-
  to-day
  (https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1849405).

  I can supply short phone videos of tearing occurring on the screens if
  required.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: mutter 3.28.4-0ubuntu18.04.2
  ProcVersionSignature: Ubuntu 5.0.0-36.39~18.04.1-generic 5.0.21
  Uname: Linux 5.0.0-36-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Nov 19 14:02:09 2019
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  SourcePackage: mutter
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1853094] Re: Screen tearing in xorg gnome session on Latitude 7480 with WD19TB Thunderbolt dock

[Matt Austin]

** Attachment added: "tearing-2.mp4"
   
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1853094/+attachment/5307225/+files/tearing-2.mp4

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

Title:
  Screen tearing in xorg gnome session on Latitude 7480 with WD19TB
  Thunderbolt dock

Status in mutter package in Ubuntu:
  New

Bug description:
  I have the WD19TB Thunderbolt dock connected to a Dell Latitude 7480
  laptop with two external displays. The laptop itself is closed
  (internal display is not used).

  In a gnome xorg session, there is severe tearing on parts of the
  screen when dragging windows or scrolling content.

  Under a wayland session there is no screen tearing, but I have
  keyboard key repetition problems which make this mostly unusable day-
  to-day
  (https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1849405).

  I can supply short phone videos of tearing occurring on the screens if
  required.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: mutter 3.28.4-0ubuntu18.04.2
  ProcVersionSignature: Ubuntu 5.0.0-36.39~18.04.1-generic 5.0.21
  Uname: Linux 5.0.0-36-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Nov 19 14:02:09 2019
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  SourcePackage: mutter
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1853094] Re: Screen tearing in xorg gnome session on Latitude 7480 with WD19TB Thunderbolt dock

[Matt Austin]

** Attachment added: "modinfo-i915.txt"
   
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1853094/+attachment/5306547/+files/modinfo-i915.txt

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

Title:
  Screen tearing in xorg gnome session on Latitude 7480 with WD19TB
  Thunderbolt dock

Status in mutter package in Ubuntu:
  New

Bug description:
  I have the WD19TB Thunderbolt dock connected to a Dell Latitude 7480
  laptop with two external displays. The laptop itself is closed
  (internal display is not used).

  In a gnome xorg session, there is severe tearing on parts of the
  screen when dragging windows or scrolling content.

  Under a wayland session there is no screen tearing, but I have
  keyboard key repetition problems which make this mostly unusable day-
  to-day
  (https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1849405).

  I can supply short phone videos of tearing occurring on the screens if
  required.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: mutter 3.28.4-0ubuntu18.04.2
  ProcVersionSignature: Ubuntu 5.0.0-36.39~18.04.1-generic 5.0.21
  Uname: Linux 5.0.0-36-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Nov 19 14:02:09 2019
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  SourcePackage: mutter
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1853094] Re: Screen tearing in xorg gnome session on Latitude 7480 with WD19TB Thunderbolt dock

[Matt Austin]

*-display 
   description: VGA compatible controller
   product: HD Graphics 620
   vendor: Intel Corporation
   physical id: 2
   bus info: pci@:00:02.0
   version: 02
   width: 64 bits
   clock: 33MHz
   capabilities: pciexpress msi pm vga_controller bus_master cap_list rom
   configuration: driver=i915 latency=0
   resources: irq:140 memory:eb00-ebff memory:a000-afff 
ioport:f000(size=64) memory:c-d


The two monitors are 2560x1440, with no scaling. But I do use a 1.25
font scaling factor in gnome-tweaks.


I am using the ubuntu-x-swat ppa, which was an attempt to resolve some previous 
graphics issues, but I can try removing this again if you'd like me to test?

libdrm-amdgpu1: ubuntu-x-swat/updates/ubuntu
libdrm-common: ubuntu-x-swat/updates/ubuntu
libdrm-dev: ubuntu-x-swat/updates/ubuntu
libdrm-intel1: ubuntu-x-swat/updates/ubuntu
libdrm-nouveau2: ubuntu-x-swat/updates/ubuntu
libdrm-radeon1: ubuntu-x-swat/updates/ubuntu
libdrm2: ubuntu-x-swat/updates/ubuntu
libegl-mesa0: ubuntu-x-swat/updates/ubuntu
libegl1-mesa: ubuntu-x-swat/updates/ubuntu
libgbm1: ubuntu-x-swat/updates/ubuntu
libgl1-mesa-dev: ubuntu-x-swat/updates/ubuntu
libgl1-mesa-dri: ubuntu-x-swat/updates/ubuntu
libgl1-mesa-glx: ubuntu-x-swat/updates/ubuntu
libglapi-mesa: ubuntu-x-swat/updates/ubuntu
libglx-mesa0: ubuntu-x-swat/updates/ubuntu
libllvm9: ubuntu-x-swat/updates/ubuntu
libxatracker2: ubuntu-x-swat/updates/ubuntu
mesa-common-dev: ubuntu-x-swat/updates/ubuntu
mesa-va-drivers: ubuntu-x-swat/updates/ubuntu
mesa-vdpau-drivers: ubuntu-x-swat/updates/ubuntu


** Attachment added: "journalctl.txt"
   
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1853094/+attachment/5306546/+files/journalctl.txt

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

Title:
  Screen tearing in xorg gnome session on Latitude 7480 with WD19TB
  Thunderbolt dock

Status in mutter package in Ubuntu:
  New

Bug description:
  I have the WD19TB Thunderbolt dock connected to a Dell Latitude 7480
  laptop with two external displays. The laptop itself is closed
  (internal display is not used).

  In a gnome xorg session, there is severe tearing on parts of the
  screen when dragging windows or scrolling content.

  Under a wayland session there is no screen tearing, but I have
  keyboard key repetition problems which make this mostly unusable day-
  to-day
  (https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1849405).

  I can supply short phone videos of tearing occurring on the screens if
  required.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: mutter 3.28.4-0ubuntu18.04.2
  ProcVersionSignature: Ubuntu 5.0.0-36.39~18.04.1-generic 5.0.21
  Uname: Linux 5.0.0-36-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Nov 19 14:02:09 2019
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  SourcePackage: mutter
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1853094] [NEW] Screen tearing in xorg gnome session on Latitude 7480 with WD19TB Thunderbolt dock

[Matt Austin]

Public bug reported:

I have the WD19TB Thunderbolt dock connected to a Dell Latitude 7480
laptop with two external displays. The laptop itself is closed (internal
display is not used).

In a gnome xorg session, there is severe tearing on parts of the screen
when dragging windows or scrolling content.

Under a wayland session there is no screen tearing, but I have keyboard
key repetition problems which make this mostly unusable day-to-day
(https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1849405).

I can supply short phone videos of tearing occurring on the screens if
required.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: mutter 3.28.4-0ubuntu18.04.2
ProcVersionSignature: Ubuntu 5.0.0-36.39~18.04.1-generic 5.0.21
Uname: Linux 5.0.0-36-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.9
Architecture: amd64
CurrentDesktop: GNOME
Date: Tue Nov 19 14:02:09 2019
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_AU.UTF-8
 SHELL=/bin/bash
SourcePackage: mutter
UpgradeStatus: No upgrade log present (probably fresh install)

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


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

** Summary changed:

- Screen tearing in xorg gnome session on Latitude 7480 with WD19TB Thubderbolt 
dock
+ Screen tearing in xorg gnome session on Latitude 7480 with WD19TB Thunderbolt 
dock

** Description changed:

- I have the WD19TB Thubderbolt dock connected to a Dell Latitude 7480
+ I have the WD19TB Thunderbolt dock connected to a Dell Latitude 7480
  laptop with two external displays. The laptop itself is closed (internal
  display is not used).
  
  In a gnome xorg session, there is severe tearing on parts of the screen
  when dragging windows or scrolling content.
  
  Under a wayland session there is no screen tearing, but I have keyboard
  key repetition problems which make this mostly unusable day-to-day
  (#1849405).
  
  I can supply short phone videos of tearing occurring on the screens if
  required.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: mutter 3.28.4-0ubuntu18.04.2
  ProcVersionSignature: Ubuntu 5.0.0-36.39~18.04.1-generic 5.0.21
  Uname: Linux 5.0.0-36-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Nov 19 14:02:09 2019
  ProcEnviron:
-  TERM=xterm-256color
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=
-  LANG=en_AU.UTF-8
-  SHELL=/bin/bash
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=en_AU.UTF-8
+  SHELL=/bin/bash
  SourcePackage: mutter
  UpgradeStatus: No upgrade log present (probably fresh install)

** Description changed:

  I have the WD19TB Thunderbolt dock connected to a Dell Latitude 7480
  laptop with two external displays. The laptop itself is closed (internal
  display is not used).
  
  In a gnome xorg session, there is severe tearing on parts of the screen
  when dragging windows or scrolling content.
  
  Under a wayland session there is no screen tearing, but I have keyboard
  key repetition problems which make this mostly unusable day-to-day
- (#1849405).
+ (https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1849405).
  
  I can supply short phone videos of tearing occurring on the screens if
  required.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: mutter 3.28.4-0ubuntu18.04.2
  ProcVersionSignature: Ubuntu 5.0.0-36.39~18.04.1-generic 5.0.21
  Uname: Linux 5.0.0-36-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Nov 19 14:02:09 2019
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  SourcePackage: mutter
  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 mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1853094

Title:
  Screen tearing in xorg gnome session on Latitude 7480 with WD19TB
  Thunderbolt dock

Status in mutter package in Ubuntu:
  New

Bug description:
  I have the WD19TB Thunderbolt dock connected to a Dell Latitude 7480
  laptop with two external displays. The laptop itself is closed
  (internal display is not used).

  In a gnome xorg session, there is severe tearing on parts of the
  screen when dragging windows or scrolling content.

  Under a wayland session there is no screen tearing, but I have
  keyboard key repetition problems which make this mostly unusable day-
  to-day
  (https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1849405).

  I can supply short phone videos of tearing occurring on the screens if
  required.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: mutter 3.28.4-0ubuntu18.04.2
  ProcVersionSignature: Ubuntu 5.0.0-36.39~18.04.1-generic 5.0.21
  Uname: Linux 5.0.0-36-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  C

[Desktop-packages] [Bug 1849405] Re: Repeated keypresses from bluetooth keyboard

[Matt Austin]

I've now been using an Xorg session rather than Wayland and haven't seen
the repeated keys issue. I do get some very nasty screen tearing when
scrolling (e.g. websites) on Xorg however, so ideally I'd like to
continue using Wayland.

Does that mean that this is likely a mutter bug, rather than bluez?

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

Title:
  Repeated keypresses from bluetooth keyboard

Status in bluez package in Ubuntu:
  Incomplete
Status in mutter package in Ubuntu:
  Incomplete

Bug description:
  I have a Microsoft Surface bluetooth keyboard, and semi-frequently
  (e.g. around every 10-15mins) end up with repeated keypresses being
  made (e.g. apppt get update).

  This seems to happen when the machine is under slight stress, or when
  a new notification pops up in gnome, so it could be related to wayland
  possibly - but even if wayland or other processes are causing stress,
  I should imagine the bluetooth hid driver should not cause repeated
  key presses.

  Please let me know if you require further information about my
  environment, it's difficult to know where to begin with determining
  which process is the root cause of this.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: bluez 5.48-0ubuntu3.2
  ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21
  Uname: Linux 5.0.0-32-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  Date: Wed Oct 23 09:38:20 2019
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: Dell Inc. Latitude 7480
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-32-generic 
root=/dev/mapper/sarasota--kf--vg-root ro quiet splash vt.handoff=1
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/04/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.15.1
  dmi.board.name: 00F6D3
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.15.1:bd07/04/2019:svnDellInc.:pnLatitude7480:pvr:rvnDellInc.:rn00F6D3:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 7480
  dmi.product.sku: 07A0
  dmi.sys.vendor: Dell Inc.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: F8:63:3F:E9:51:8C  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING PSCAN 
RX bytes:1658613 acl:66750 sco:0 events:15708 errors:0
TX bytes:605292 acl:98 sco:0 commands:2484 errors:0

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

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

[Desktop-packages] [Bug 1839856] Re: Screen resolution on external monitor won't go above 2560 x 1080

[Matt White]

I went back pretty far, into the 4.x versions, and still had the same
results, so I'm guessing this isn't kernel-related. Any suggestion on
what else to try?

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

Title:
  Screen resolution on external monitor won't go above 2560 x 1080

Status in linux package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  New

Bug description:
  I have an external monitor capable of 3440 x 1440. I am using a
  Thinkpad T480s. Up until about 2 weeks ago, I could set the resolution
  of the monitor to 3440 x 1440 just fine. Now when I try, the screen
  goes black and I have to revert to a lower resolution. The highest it
  will go now is 2560 x 1080. Lower resolutions work fine as well.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 5.0.0-23.24~18.04.1-generic 5.0.15
  Uname: Linux 5.0.0-23-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.7
  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 Aug 12 08:56:25 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   acpi-call, 1.1.0, 4.18.0-25-generic, x86_64: installed
   acpi-call, 1.1.0, 5.0.0-23-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: Lenovo UHD Graphics 620 [17aa:2258]
  InstallationDate: Installed on 2019-02-19 (173 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  MachineType: LENOVO 20L7S01200
  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.0.0-23-generic 
root=UUID=471b6634-e334-44c7-b898-080ab93327e0 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/19/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N22ET53W (1.30 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20L7S01200
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN22ET53W(1.30):bd02/19/2019:svnLENOVO:pn20L7S01200:pvrThinkPadT480s:rvnLENOVO:rn20L7S01200:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T480s
  dmi.product.name: 20L7S01200
  dmi.product.sku: LENOVO_MT_20L7_BU_Think_FM_ThinkPad T480s
  dmi.product.version: ThinkPad T480s
  dmi.sys.vendor: LENOVO
  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.2-1ubuntu1.1~18.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.2-1ubuntu1.1~18.04.2
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

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

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

[Desktop-packages] [Bug 1839856] Re: Screen resolution on external monitor won't go above 2560 x 1080

[Matt White]

I tried both 5.2.11 and 5.3-rc6. Same result with both.

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

Title:
  Screen resolution on external monitor won't go above 2560 x 1080

Status in linux package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  New

Bug description:
  I have an external monitor capable of 3440 x 1440. I am using a
  Thinkpad T480s. Up until about 2 weeks ago, I could set the resolution
  of the monitor to 3440 x 1440 just fine. Now when I try, the screen
  goes black and I have to revert to a lower resolution. The highest it
  will go now is 2560 x 1080. Lower resolutions work fine as well.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 5.0.0-23.24~18.04.1-generic 5.0.15
  Uname: Linux 5.0.0-23-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.7
  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 Aug 12 08:56:25 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   acpi-call, 1.1.0, 4.18.0-25-generic, x86_64: installed
   acpi-call, 1.1.0, 5.0.0-23-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: Lenovo UHD Graphics 620 [17aa:2258]
  InstallationDate: Installed on 2019-02-19 (173 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  MachineType: LENOVO 20L7S01200
  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.0.0-23-generic 
root=UUID=471b6634-e334-44c7-b898-080ab93327e0 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/19/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N22ET53W (1.30 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20L7S01200
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN22ET53W(1.30):bd02/19/2019:svnLENOVO:pn20L7S01200:pvrThinkPadT480s:rvnLENOVO:rn20L7S01200:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T480s
  dmi.product.name: 20L7S01200
  dmi.product.sku: LENOVO_MT_20L7_BU_Think_FM_ThinkPad T480s
  dmi.product.version: ThinkPad T480s
  dmi.sys.vendor: LENOVO
  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.2-1ubuntu1.1~18.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.2-1ubuntu1.1~18.04.2
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

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

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

[Desktop-packages] [Bug 1839856] [NEW] Screen resolution on external monitor won't go above 2560 x 1080

[Matt White]

Public bug reported:

I have an external monitor capable of 3440 x 1440. I am using a Thinkpad
T480s. Up until about 2 weeks ago, I could set the resolution of the
monitor to 3440 x 1440 just fine. Now when I try, the screen goes black
and I have to revert to a lower resolution. The highest it will go now
is 2560 x 1080. Lower resolutions work fine as well.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 5.0.0-23.24~18.04.1-generic 5.0.15
Uname: Linux 5.0.0-23-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.9-0ubuntu7.7
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 Aug 12 08:56:25 2019
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
DkmsStatus:
 acpi-call, 1.1.0, 4.18.0-25-generic, x86_64: installed
 acpi-call, 1.1.0, 5.0.0-23-generic, x86_64: installed
ExtraDebuggingInterest: Yes, including running git bisection searches
GraphicsCard:
 Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
   Subsystem: Lenovo UHD Graphics 620 [17aa:2258]
InstallationDate: Installed on 2019-02-19 (173 days ago)
InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210)
MachineType: LENOVO 20L7S01200
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.0.0-23-generic 
root=UUID=471b6634-e334-44c7-b898-080ab93327e0 ro quiet splash vt.handoff=1
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/19/2019
dmi.bios.vendor: LENOVO
dmi.bios.version: N22ET53W (1.30 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20L7S01200
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40709 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias: 
dmi:bvnLENOVO:bvrN22ET53W(1.30):bd02/19/2019:svnLENOVO:pn20L7S01200:pvrThinkPadT480s:rvnLENOVO:rn20L7S01200:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad T480s
dmi.product.name: 20L7S01200
dmi.product.sku: LENOVO_MT_20L7_BU_Think_FM_ThinkPad T480s
dmi.product.version: ThinkPad T480s
dmi.sys.vendor: LENOVO
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.2-1ubuntu1.1~18.04.2
version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.2-1ubuntu1.1~18.04.2
version.xserver-xorg-core: xserver-xorg-core N/A
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

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


** Tags: amd64 apport-bug bionic resolution ubuntu

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

Title:
  Screen resolution on external monitor won't go above 2560 x 1080

Status in xorg package in Ubuntu:
  New

Bug description:
  I have an external monitor capable of 3440 x 1440. I am using a
  Thinkpad T480s. Up until about 2 weeks ago, I could set the resolution
  of the monitor to 3440 x 1440 just fine. Now when I try, the screen
  goes black and I have to revert to a lower resolution. The highest it
  will go now is 2560 x 1080. Lower resolutions work fine as well.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 5.0.0-23.24~18.04.1-generic 5.0.15
  Uname: Linux 5.0.0-23-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.7
  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 Aug 12 08:56:25 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   acpi-call, 1.1.0, 4.18.0-25-generic, x86_64: installed
   acpi-call, 1.1.0, 5.0.0-23-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: Lenovo UHD Graphics 620 [17aa:2258]
  InstallationDate: Installed on 2019-02-19 (173 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  MachineType: LENOVO 20L7S01200
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUN

[Desktop-packages] [Bug 1826604] Re: Extension causes saving files to desktop to be slow

[Matt Lu]

On my systems, this bug also affected saving files from firefox, regardless of 
the destination!
This is not about the time for downloading, I'm talking about ~1 kB files.

On one machine, it took 4-5 seconds saving such files to any location
(not just the desktop), on the other it took over 2 seconds. After
renaming the extension, saving from firefox happened instantly again on
both machines.

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

Title:
  Extension causes saving files to desktop to be slow

Status in gnome-shell-extension-desktop-icons:
  New
Status in gnome-shell-extension-desktop-icons package in Ubuntu:
  Triaged

Bug description:
  To reproduce:
  1. Create a text file (foo.txt) on the desktop and open in gedit.
  2. Type a few lines in the file and save it.

  Expected: the file saves more or less instantly.

  Observed:
  - The file takes several seconds to save.
  - The following lines appear in the journal:

  Apr 26 22:20:40 khaeru-laptop gnome-shell[3205]: JS ERROR: TypeError: 
fileItem is null
   
_updateDesktopIfChanged@/usr/share/gnome-shell/extensions/desktop-icons@csoriano/desktopManager.js:339:17
   
_monitorDesktopFolder/<@/usr/share/gnome-shell/extensions/desktop-icons@csoriano/desktopManager.js:299:89

  Notes:
  - Repeating #1 and #2 with a file that is in another folder (i.e., not on the 
desktop), the file saves instantly, and the log messages do not appear.
  - This might be a duplicate/alternate description of lp#1816205.
  - Discovered while trying to diagnose lp#1826219.

  $ lsb_release -rd && apt-cache policy gnome-shell-extension-desktop-icons
  Description:Ubuntu 19.04
  Release:19.04
  gnome-shell-extension-desktop-icons:
    Installed: 19.01.1-1
    Candidate: 19.01.1-1
    Version table:
   *** 19.01.1-1 500
  500 http://us.archive.ubuntu.com/ubuntu disco/main amd64 Packages
  500 http://us.archive.ubuntu.com/ubuntu disco/main i386 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gnome-shell-extension-desktop-icons 19.01.1-1
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 26 22:24:04 2019
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-10-11 (562 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  PackageArchitecture: all
  SourcePackage: gnome-shell-extension-desktop-icons
  UpgradeStatus: Upgraded to disco on 2019-04-22 (4 days ago)

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

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

[Desktop-packages] [Bug 1036236] Re: hpcups and hpijs driver use different rasterization

[Matt Whitlock]

While debugging an unrelated issue with printing to my HP LaserJet 1012,
I switched from the "hpcups" driver to the "hpijs" driver, and I am
**BLOWN AWAY** by the quality of its dithering. After seeing the
difference, I am absolutely appalled at how poorly the "hpcups" driver
dithers grayscales. I had no idea that my cheap little laser printer
could produce such great looking graphics until I discovered the "hpijs"
driver. The "hpcups" driver is garbage by comparison.

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

Title:
  hpcups and hpijs driver use different rasterization

Status in HPLIP:
  Confirmed
Status in hplip package in Ubuntu:
  Won't Fix

Bug description:
  HPLIP provides two drivers for the Laserjet 1515n: hpcups and hpijs:
  - hp-color_laserjet_cp1515n-hpijs-pcl3.ppd
  - hp-color_laserjet_cp1515n-pcl3.ppd

  The new hpcups shall replace the old hpijs, however, it produces very
  different rasterization results, resulting in a radically different
  visual impression. Differences are especially prominent for greyscale
  prints.

  Hpcups produces "amplitude modulation" halftones (dots of different
  sizes at fixed locations). When resolution is set to "Normal", the
  size of these dots is so large that contours cannot be reproduced with
  reasonable detail. Heavy aliasing  can be easily seen in the circle
  contours on the Ubuntu Printer test page. Printing photographs in
  greyscale mode yields badly rasterized images like those known from
  low-quality newspaper prints (dot pattern is so prominent it dominates
  image contours). Artifacts are reduced, but still visible at
  resolution "Best".

  In contrast, hpijs produces "frequency modulation" halftones with
  stochastic dithering (small-sized dots placed at varying densities).
  At resolution "Normal", it produces evenly colored areas with
  reasonably sharp edges. Circle contours on the Ubuntu Printer test
  page appear continuous. Photographs are reproduced at a a much higher
  fidelity as with the hpcups driver.

  Questions:
  1. Why do the two drivers use different rasterization?
  2. Why is the result of rasterization so bad in the hpcups driver, set at 
resolution "Normal, Greyscale"?

  Note:
  Both drivers produce acceptable color prints with much fewer artifacts 
visible, even at resolution "Normal".

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: hplip 3.12.2-1ubuntu3.1
  ProcVersionSignature: Ubuntu 3.2.0-29.46-generic 3.2.24
  Uname: Linux 3.2.0-29-generic i686
  ApportVersion: 2.0.1-0ubuntu12
  Architecture: i386
  CurrentDmesg: [   63.368304] init: plymouth-stop pre-start process (1700) 
terminated with status 1
  Date: Mon Aug 13 16:38:16 2012
  Lpstat: device for Farblaser: hp:/net/HP_Color_LaserJet_CP1515n?zc=NPIE56824
  MachineType: exone D156200
  Papersize: letter
  PpdFiles: Farblaser: HP Color LaserJet cp1515n pcl3, hpcups 3.12.2
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-29-generic 
root=/dev/mapper/lvmvg-Root ro quiet splash vt.handoff=7
  SourcePackage: hplip
  UpgradeStatus: Upgraded to precise on 2012-04-26 (108 days ago)
  dmi.bios.date: 04/23/2004
  dmi.bios.vendor: FUJITSU SIEMENS // Phoenix Technologies Ltd.
  dmi.bios.version: 4.06  Rev. 1.09.1562
  dmi.board.name: D1562
  dmi.board.vendor: FUJITSU SIEMENS
  dmi.board.version: S26361-D1562
  dmi.chassis.type: 6
  dmi.chassis.vendor: exone
  dmi.modalias: 
dmi:bvnFUJITSUSIEMENS//PhoenixTechnologiesLtd.:bvr4.06Rev.1.09.1562:bd04/23/2004:svnexone:pnD156200:pvr:rvnFUJITSUSIEMENS:rnD1562:rvrS26361-D1562:cvnexone:ct6:cvr:
  dmi.product.name: D156200
  dmi.sys.vendor: exone

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

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

[Desktop-packages] [Bug 1816497] Re: [snap] vaapi chromium no video hardware decoding

[Matt Lee]

The landing page for the build has disappeared:
https://code.launchpad.net/~osomon/+snap/chromium-snap-from-source-
enable-vaapi so it's possible that your installation has reverted to the
main branch again.

For what it's worth, there is another working option available that we
can try: https://launchpad.net/~saiarcot895/+archive/ubuntu/chromium-
beta

I'd honestly prefer to use an official Ubuntu build but the one above
has served me consistently well on previous system so I'll probably
stick with that until we see a main branch build with vaapi support.

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

Title:
  [snap] vaapi chromium no video hardware decoding

Status in chromium-browser package in Ubuntu:
  Confirmed

Bug description:
  Libva is no longer working for snap installed chromium 72.0.3626.109
  (Official Build) snap (64-bit)

  I followed this instruction
  sudo snap install --channel=candidate/vaapi chromium

  My amdgpu can use libva

  `vainfo: Driver version: Mesa Gallium driver 18.3.3 for AMD STONEY (DRM 
3.27.0, 4.20.0-10.1-liquorix-amd64, LLVM 7.0.1)
  vainfo: Supported profile and entrypoints
VAProfileMPEG2Simple:   VAEntrypointVLD
VAProfileMPEG2Main  :   VAEntrypointVLD
VAProfileVC1Simple  :   VAEntrypointVLD
VAProfileVC1Main:   VAEntrypointVLD
VAProfileVC1Advanced:   VAEntrypointVLD
VAProfileH264ConstrainedBaseline:   VAEntrypointVLD
VAProfileH264ConstrainedBaseline:   VAEntrypointEncSlice
VAProfileH264Main   :   VAEntrypointVLD
VAProfileH264Main   :   VAEntrypointEncSlice
VAProfileH264High   :   VAEntrypointVLD
VAProfileH264High   :   VAEntrypointEncSlice
VAProfileHEVCMain   :   VAEntrypointVLD
VAProfileHEVCMain10 :   VAEntrypointVLD
VAProfileJPEGBaseline   :   VAEntrypointVLD
VAProfileNone   :   VAEntrypointVideoProc`

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

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

[Desktop-packages] [Bug 1828401] Re: 9.26~dfsg+0-0ubuntu0.18.04.9 breaks cups printing of pdf

[Matt Walters]

Cups 1.20.2 resolved the issue on Bionic for me. Thank you.

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

Title:
  9.26~dfsg+0-0ubuntu0.18.04.9 breaks cups printing of pdf

Status in cups-filters package in Ubuntu:
  Fix Released
Status in cups-filters source package in Xenial:
  Fix Released
Status in cups-filters source package in Bionic:
  Fix Released
Status in cups-filters source package in Cosmic:
  Fix Released

Bug description:
  Distributor ID:   Ubuntu
  Description:  Ubuntu 18.04.2 LTS
  Release:  18.04
  Codename: bionic

  
  PROBLEM:
  9.26~dfsg+0-0ubuntu0.18.04.9 breaks printing pdf on cups

  error in cups logs:

  ...
  D [09/May/2019:13:44:33 +0200] [Job 68] GPL Ghostscript 9.26: Unrecoverable 
error, exit code 1
  D [09/May/2019:13:44:33 +0200] [Job 68] Process is dying with \"Unable to 
determine number of pages, page count: -1
  D [09/May/2019:13:44:33 +0200] [Job 68] \", exit stat 3
  ...

  details of this bug here: https://bugs.archlinux.org/task/62251

  POSSIBLE SOLUTION:
  release an update of cups-filters to 1.22.5

  WORKAROUND: 
  downgrade ghostscript to 9.22~dfsg+1-0ubuntu1

  sudo apt install ghostscript=9.22~dfsg+1-0ubuntu1
  libgs9=9.22~dfsg+1-0ubuntu1 libgs9-common=9.22~dfsg+1-0ubuntu1
  ghostscript-x=9.22~dfsg+1-0ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/1828401/+subscriptions

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

[Desktop-packages] [Bug 1828434] Re: Unable to print after libgs 9.26 installed

[Matt Walters]

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

installing cups-filter 1.20.2 resolved the issue. Thanks everyone!

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

Title:
  Unable to print after libgs 9.26 installed

Status in ghostscript package in Ubuntu:
  Confirmed

Bug description:
  I'm receiving the following error in the cups error_log after libgs
  was updated to 9.26:

  D [09/May/2019:11:19:22 -0400] [Job 6927] Filetype: PDF
  D [09/May/2019:11:19:22 -0400] [Job 6927] Storing temporary files in /tmp
  D [09/May/2019:11:19:22 -0400] [Job 6927] PID 28996 
(/usr/lib/cups/filter/pdftopdf) exited with no errors.
  D [09/May/2019:11:19:22 -0400] [Job 6927] GPL Ghostscript 9.26: Unrecoverable 
error, exit code 1
  D [09/May/2019:11:19:22 -0400] [Job 6927] Process is dying with \"Unable to 
determine number of pages, page count: -1
  D [09/May/2019:11:19:22 -0400] [Job 6927] \", exit stat 3
  D [09/May/2019:11:19:22 -0400] [Job 6927] Cleaning up...
  D [09/May/2019:11:19:22 -0400] [Job 6927] PID 28997 
(/usr/lib/cups/filter/foomatic-rip) stopped with status 3.
  D [09/May/2019:11:19:22 -0400] [Job 6927] prnt/backend/hp.c 919: ERROR: null 
print job total=0
  D [09/May/2019:11:19:22 -0400] [Job 6927] PID 28998 
(/usr/lib/cups/backend/hp) exited with no errors

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

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

[Desktop-packages] [Bug 1828434] Re: Unable to print after libgs 9.26 installed

[Matt Walters]

Some clarification. I'm using ubuntu 18.04 with an HP Laserjet 500 MFP
570dn... two servers, two of the same printer, and the same issue. It
appears to have occured after the following unattended upgrade:

Upgrade: libgs9:amd64 (9.26~dfsg+0-0ubuntu0.18.04.8,
9.26~dfsg+0-0ubuntu0.18.04.9), ghostscript:amd64
(9.26~dfsg+0-0ubuntu0.18.04.8, 9.26~dfsg+0-0ubuntu0.18.04.9),
ghostscript-x:amd64 (9.26~dfsg+0-0ubuntu0.18.04.8,
9.26~dfsg+0-0ubuntu0.18.04.9), libgs9-common:amd64
(9.26~dfsg+0-0ubuntu0.18.04.8, 9.26~dfsg+0-0ubuntu0.18.04.9)

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

Title:
  Unable to print after libgs 9.26 installed

Status in ghostscript package in Ubuntu:
  New

Bug description:
  I'm receiving the following error in the cups error_log after libgs
  was updated to 9.26:

  D [09/May/2019:11:19:22 -0400] [Job 6927] Filetype: PDF
  D [09/May/2019:11:19:22 -0400] [Job 6927] Storing temporary files in /tmp
  D [09/May/2019:11:19:22 -0400] [Job 6927] PID 28996 
(/usr/lib/cups/filter/pdftopdf) exited with no errors.
  D [09/May/2019:11:19:22 -0400] [Job 6927] GPL Ghostscript 9.26: Unrecoverable 
error, exit code 1
  D [09/May/2019:11:19:22 -0400] [Job 6927] Process is dying with \"Unable to 
determine number of pages, page count: -1
  D [09/May/2019:11:19:22 -0400] [Job 6927] \", exit stat 3
  D [09/May/2019:11:19:22 -0400] [Job 6927] Cleaning up...
  D [09/May/2019:11:19:22 -0400] [Job 6927] PID 28997 
(/usr/lib/cups/filter/foomatic-rip) stopped with status 3.
  D [09/May/2019:11:19:22 -0400] [Job 6927] prnt/backend/hp.c 919: ERROR: null 
print job total=0
  D [09/May/2019:11:19:22 -0400] [Job 6927] PID 28998 
(/usr/lib/cups/backend/hp) exited with no errors

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

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

[Desktop-packages] [Bug 1828434] [NEW] Unable to print after libgs 9.26 installed

[Matt Walters]

Public bug reported:

I'm receiving the following error in the cups error_log after libgs was
updated to 9.26:

D [09/May/2019:11:19:22 -0400] [Job 6927] Filetype: PDF
D [09/May/2019:11:19:22 -0400] [Job 6927] Storing temporary files in /tmp
D [09/May/2019:11:19:22 -0400] [Job 6927] PID 28996 
(/usr/lib/cups/filter/pdftopdf) exited with no errors.
D [09/May/2019:11:19:22 -0400] [Job 6927] GPL Ghostscript 9.26: Unrecoverable 
error, exit code 1
D [09/May/2019:11:19:22 -0400] [Job 6927] Process is dying with \"Unable to 
determine number of pages, page count: -1
D [09/May/2019:11:19:22 -0400] [Job 6927] \", exit stat 3
D [09/May/2019:11:19:22 -0400] [Job 6927] Cleaning up...
D [09/May/2019:11:19:22 -0400] [Job 6927] PID 28997 
(/usr/lib/cups/filter/foomatic-rip) stopped with status 3.
D [09/May/2019:11:19:22 -0400] [Job 6927] prnt/backend/hp.c 919: ERROR: null 
print job total=0
D [09/May/2019:11:19:22 -0400] [Job 6927] PID 28998 (/usr/lib/cups/backend/hp) 
exited with no errors

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

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

Title:
  Unable to print after libgs 9.26 installed

Status in ghostscript package in Ubuntu:
  New

Bug description:
  I'm receiving the following error in the cups error_log after libgs
  was updated to 9.26:

  D [09/May/2019:11:19:22 -0400] [Job 6927] Filetype: PDF
  D [09/May/2019:11:19:22 -0400] [Job 6927] Storing temporary files in /tmp
  D [09/May/2019:11:19:22 -0400] [Job 6927] PID 28996 
(/usr/lib/cups/filter/pdftopdf) exited with no errors.
  D [09/May/2019:11:19:22 -0400] [Job 6927] GPL Ghostscript 9.26: Unrecoverable 
error, exit code 1
  D [09/May/2019:11:19:22 -0400] [Job 6927] Process is dying with \"Unable to 
determine number of pages, page count: -1
  D [09/May/2019:11:19:22 -0400] [Job 6927] \", exit stat 3
  D [09/May/2019:11:19:22 -0400] [Job 6927] Cleaning up...
  D [09/May/2019:11:19:22 -0400] [Job 6927] PID 28997 
(/usr/lib/cups/filter/foomatic-rip) stopped with status 3.
  D [09/May/2019:11:19:22 -0400] [Job 6927] prnt/backend/hp.c 919: ERROR: null 
print job total=0
  D [09/May/2019:11:19:22 -0400] [Job 6927] PID 28998 
(/usr/lib/cups/backend/hp) exited with no errors

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

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

[Desktop-packages] [Bug 1816497] Re: [snap] vaapi chromium no video hardware decoding

[Matt Lee]

I have a slightly newer chipset (Kabylake) so VP9 is supported in my
case. Thanks for the suggestion though.

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

Title:
  [snap] vaapi chromium no video hardware decoding

Status in chromium-browser package in Ubuntu:
  Confirmed

Bug description:
  Libva is no longer working for snap installed chromium 72.0.3626.109
  (Official Build) snap (64-bit)

  I followed this instruction
  sudo snap install --channel=candidate/vaapi chromium

  My amdgpu can use libva

  `vainfo: Driver version: Mesa Gallium driver 18.3.3 for AMD STONEY (DRM 
3.27.0, 4.20.0-10.1-liquorix-amd64, LLVM 7.0.1)
  vainfo: Supported profile and entrypoints
VAProfileMPEG2Simple:   VAEntrypointVLD
VAProfileMPEG2Main  :   VAEntrypointVLD
VAProfileVC1Simple  :   VAEntrypointVLD
VAProfileVC1Main:   VAEntrypointVLD
VAProfileVC1Advanced:   VAEntrypointVLD
VAProfileH264ConstrainedBaseline:   VAEntrypointVLD
VAProfileH264ConstrainedBaseline:   VAEntrypointEncSlice
VAProfileH264Main   :   VAEntrypointVLD
VAProfileH264Main   :   VAEntrypointEncSlice
VAProfileH264High   :   VAEntrypointVLD
VAProfileH264High   :   VAEntrypointEncSlice
VAProfileHEVCMain   :   VAEntrypointVLD
VAProfileHEVCMain10 :   VAEntrypointVLD
VAProfileJPEGBaseline   :   VAEntrypointVLD
VAProfileNone   :   VAEntrypointVideoProc`

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

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

[Desktop-packages] [Bug 1748839] Re: Problem to connect to WPA2/PEAP WIFI - gnome-shell

[Matt Godin]

Nothing helpful in this post but can confirm this issue still exists in
19.04. :(

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

Title:
  Problem to connect to WPA2/PEAP WIFI  - gnome-shell

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  This problem is also happened on my desktop.

  After upgrading OS from Ubuntu 16.04 to Ubuntu 18.04.1 LTS, my PC
  could not connect and authenticate on WiFi with  WPA2/PEAP/MSCHAPv2/no
  CA certificate/true username and password.

  
  I tried to solve the  problem following URL link; however, it could not help 
me also. 
  
https://askubuntu.com/questions/279762/how-to-connect-to-wpa2-peap-mschapv2-enterprise-wifi-networks-that-dont-use-a-c
 

  
  My PC  is HP Compaq Pro 4300, CPU: Intel® Core™ i3-3220 CPU @ 3.30GHz × 4, 
OS: Ubuntu 18.04.1 (64-bit).

  root@joe-UBTPC:/root # lspci

  00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor 
DRAM Controller (rev 09)
  00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v2/3rd Gen 
Core processor Graphics Controller (rev 09)
  00:16.0 Communication controller: Intel Corporation 6 Series/C200 Series 
Chipset Family MEI Controller #1 (rev 04)
  00:1a.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family 
USB Enhanced Host Controller #2 (rev 05)
  00:1b.0 Audio device: Intel Corporation 6 Series/C200 Series Chipset Family 
High Definition Audio Controller (rev 05)
  00:1c.0 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI 
Express Root Port 1 (rev b5)
  00:1c.1 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI 
Express Root Port 2 (rev b5)
  00:1c.2 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI 
Express Root Port 3 (rev b5)
  00:1c.3 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI 
Express Root Port 4 (rev b5)
  00:1c.4 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI 
Express Root Port 5 (rev b5)
  00:1c.5 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI 
Express Root Port 6 (rev b5)
  00:1d.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family 
USB Enhanced Host Controller #1 (rev 05)
  00:1f.0 ISA bridge: Intel Corporation H61 Express Chipset Family LPC 
Controller (rev 05)
  00:1f.2 SATA controller: Intel Corporation 6 Series/C200 Series Chipset 
Family SATA AHCI Controller (rev 05)
  00:1f.3 SMBus: Intel Corporation 6 Series/C200 Series Chipset Family SMBus 
Controller (rev 05)
  03:00.0 Network controller: Ralink corp. RT5392 PCIe Wireless Network Adapter
  06:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. 
RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 07)

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

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

[Desktop-packages] [Bug 1816497] Re: [snap] vaapi chromium no video hardware decoding

[Matt Lee]

I wonder if my problem may be related to this error in the chrome://gpu
log:

- [20257:20257:0414/133034.932196:ERROR:gl_implementation.cc(280)] :
Failed to load /snap/chromium/686/usr/lib/chromium-browser/libGLESv2.so:
/snap/chromium/686/usr/lib/chromium-browser/libGLESv2.so: cannot open
shared object file: No such file or directory

Oddly I get this bug in both the main chromium snap and the vaapi
candidate snap. No problems in Chromium when installed via apt. Since
I'm not able to update the snap file, I can't correct this issue
unfortunately.

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

Title:
  [snap] vaapi chromium no video hardware decoding

Status in chromium-browser package in Ubuntu:
  Confirmed

Bug description:
  Libva is no longer working for snap installed chromium 72.0.3626.109
  (Official Build) snap (64-bit)

  I followed this instruction
  sudo snap install --channel=candidate/vaapi chromium

  My amdgpu can use libva

  `vainfo: Driver version: Mesa Gallium driver 18.3.3 for AMD STONEY (DRM 
3.27.0, 4.20.0-10.1-liquorix-amd64, LLVM 7.0.1)
  vainfo: Supported profile and entrypoints
VAProfileMPEG2Simple:   VAEntrypointVLD
VAProfileMPEG2Main  :   VAEntrypointVLD
VAProfileVC1Simple  :   VAEntrypointVLD
VAProfileVC1Main:   VAEntrypointVLD
VAProfileVC1Advanced:   VAEntrypointVLD
VAProfileH264ConstrainedBaseline:   VAEntrypointVLD
VAProfileH264ConstrainedBaseline:   VAEntrypointEncSlice
VAProfileH264Main   :   VAEntrypointVLD
VAProfileH264Main   :   VAEntrypointEncSlice
VAProfileH264High   :   VAEntrypointVLD
VAProfileH264High   :   VAEntrypointEncSlice
VAProfileHEVCMain   :   VAEntrypointVLD
VAProfileHEVCMain10 :   VAEntrypointVLD
VAProfileJPEGBaseline   :   VAEntrypointVLD
VAProfileNone   :   VAEntrypointVideoProc`

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

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

[Desktop-packages] [Bug 1816497] Re: [snap] vaapi chromium no video hardware decoding

[Matt Lee]

Interesting. Since I'm only getting VpxVideoDecoder decode, I guess I
have an installation issue of some kind.

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

Title:
  [snap] vaapi chromium no video hardware decoding

Status in chromium-browser package in Ubuntu:
  Confirmed

Bug description:
  Libva is no longer working for snap installed chromium 72.0.3626.109
  (Official Build) snap (64-bit)

  I followed this instruction
  sudo snap install --channel=candidate/vaapi chromium

  My amdgpu can use libva

  `vainfo: Driver version: Mesa Gallium driver 18.3.3 for AMD STONEY (DRM 
3.27.0, 4.20.0-10.1-liquorix-amd64, LLVM 7.0.1)
  vainfo: Supported profile and entrypoints
VAProfileMPEG2Simple:   VAEntrypointVLD
VAProfileMPEG2Main  :   VAEntrypointVLD
VAProfileVC1Simple  :   VAEntrypointVLD
VAProfileVC1Main:   VAEntrypointVLD
VAProfileVC1Advanced:   VAEntrypointVLD
VAProfileH264ConstrainedBaseline:   VAEntrypointVLD
VAProfileH264ConstrainedBaseline:   VAEntrypointEncSlice
VAProfileH264Main   :   VAEntrypointVLD
VAProfileH264Main   :   VAEntrypointEncSlice
VAProfileH264High   :   VAEntrypointVLD
VAProfileH264High   :   VAEntrypointEncSlice
VAProfileHEVCMain   :   VAEntrypointVLD
VAProfileHEVCMain10 :   VAEntrypointVLD
VAProfileJPEGBaseline   :   VAEntrypointVLD
VAProfileNone   :   VAEntrypointVideoProc`

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

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

[Desktop-packages] [Bug 1816497] Re: [snap] vaapi chromium no video hardware decoding

[Matt Lee]

Some updates:

- I can confirm that 'sudo snap install --channel=candidate/vaapi chromium' 
installs correctly, as of today, with the same version indicated in the build 
log. 
- HW accelerated decode is not available when I apply the 
'--ignore-gpu-blacklist' flag
- HW accelerated encode is available whether or not I apply 
'--ignore-gpu-blacklist' flag
- I've attached the following three files, in a tar.bz2 archive, to show my 
system config:
 1) vainfo output
 2) chrome://gpu default value
 3) chrome://gpu value after applying '--ignore-gpu-blacklist' flag

** Attachment added: "Chromium.tar.bz2"
   
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1816497/+attachment/5253547/+files/Chromium.tar.bz2

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

Title:
  [snap] vaapi chromium no video hardware decoding

Status in chromium-browser package in Ubuntu:
  Confirmed

Bug description:
  Libva is no longer working for snap installed chromium 72.0.3626.109
  (Official Build) snap (64-bit)

  I followed this instruction
  sudo snap install --channel=candidate/vaapi chromium

  My amdgpu can use libva

  `vainfo: Driver version: Mesa Gallium driver 18.3.3 for AMD STONEY (DRM 
3.27.0, 4.20.0-10.1-liquorix-amd64, LLVM 7.0.1)
  vainfo: Supported profile and entrypoints
VAProfileMPEG2Simple:   VAEntrypointVLD
VAProfileMPEG2Main  :   VAEntrypointVLD
VAProfileVC1Simple  :   VAEntrypointVLD
VAProfileVC1Main:   VAEntrypointVLD
VAProfileVC1Advanced:   VAEntrypointVLD
VAProfileH264ConstrainedBaseline:   VAEntrypointVLD
VAProfileH264ConstrainedBaseline:   VAEntrypointEncSlice
VAProfileH264Main   :   VAEntrypointVLD
VAProfileH264Main   :   VAEntrypointEncSlice
VAProfileH264High   :   VAEntrypointVLD
VAProfileH264High   :   VAEntrypointEncSlice
VAProfileHEVCMain   :   VAEntrypointVLD
VAProfileHEVCMain10 :   VAEntrypointVLD
VAProfileJPEGBaseline   :   VAEntrypointVLD
VAProfileNone   :   VAEntrypointVideoProc`

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

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

[Desktop-packages] [Bug 1816497] Re: [snap] vaapi chromium no video hardware decoding

[Matt Lee]

It appears that the candidate/vaapi channel has either been broken or
abandoned, since the last build was on February 15th:
https://code.launchpad.net/~osomon/+snap/chromium-snap-from-source-
enable-vaapi

Is it possible to get the channel added to the 'Built automatically'
build schedule since is currently set to the 'Built on request' build
schedule?

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

Title:
  [snap] vaapi chromium no video hardware decoding

Status in chromium-browser package in Ubuntu:
  Confirmed

Bug description:
  Libva is no longer working for snap installed chromium 72.0.3626.109
  (Official Build) snap (64-bit)

  I followed this instruction
  sudo snap install --channel=candidate/vaapi chromium

  My amdgpu can use libva

  `vainfo: Driver version: Mesa Gallium driver 18.3.3 for AMD STONEY (DRM 
3.27.0, 4.20.0-10.1-liquorix-amd64, LLVM 7.0.1)
  vainfo: Supported profile and entrypoints
VAProfileMPEG2Simple:   VAEntrypointVLD
VAProfileMPEG2Main  :   VAEntrypointVLD
VAProfileVC1Simple  :   VAEntrypointVLD
VAProfileVC1Main:   VAEntrypointVLD
VAProfileVC1Advanced:   VAEntrypointVLD
VAProfileH264ConstrainedBaseline:   VAEntrypointVLD
VAProfileH264ConstrainedBaseline:   VAEntrypointEncSlice
VAProfileH264Main   :   VAEntrypointVLD
VAProfileH264Main   :   VAEntrypointEncSlice
VAProfileH264High   :   VAEntrypointVLD
VAProfileH264High   :   VAEntrypointEncSlice
VAProfileHEVCMain   :   VAEntrypointVLD
VAProfileHEVCMain10 :   VAEntrypointVLD
VAProfileJPEGBaseline   :   VAEntrypointVLD
VAProfileNone   :   VAEntrypointVideoProc`

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

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

[Desktop-packages] [Bug 1810176] [NEW] libmtp error could not get object handles

[Matt Sandefur]

Public bug reported:

When connecting my android galaxy s7 phone via usb, I am unable to
access my Music folder, which contains 380 subfolders.  The file manager
is inactive for a long time, and finally displays the error:

Sorry, could not display all the contents of "Music": libmtp error:
could not get object handles.

Adding one more subfolder on the android side seems to work around the
issue, so the issue is related to the number of items.

Given this, my issue appears to be a specific example of the issue described in 
the link below.
https://sourceforge.net/p/libmtp/bugs/1808/

Observed in linux mint 18.3 64 bit / ubuntu 16.04

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

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

Title:
  libmtp error could not get object handles

Status in libmtp package in Ubuntu:
  New

Bug description:
  When connecting my android galaxy s7 phone via usb, I am unable to
  access my Music folder, which contains 380 subfolders.  The file
  manager is inactive for a long time, and finally displays the error:

  Sorry, could not display all the contents of "Music": libmtp error:
  could not get object handles.

  Adding one more subfolder on the android side seems to work around the
  issue, so the issue is related to the number of items.

  Given this, my issue appears to be a specific example of the issue described 
in the link below.
  https://sourceforge.net/p/libmtp/bugs/1808/

  Observed in linux mint 18.3 64 bit / ubuntu 16.04

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

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

[Desktop-packages] [Bug 1802680] Re: Adding keyboard layout broken without logout

[Matt Arsenault]

I mean to 18.10

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

Title:
  Adding keyboard layout broken without logout

Status in gnome-shell package in Ubuntu:
  Fix Committed

Bug description:
  On my system, the default keyboard layout is English (Colemak). I have
  English (US) as a secondary keyboard layout.

  I attempted to add Russian, which worked. However, when I switched to
  it using Super+Space, input was really done in Qwerty. Both Russian
  and English (US) were effectively qwerty options until I logged out
  and back in.

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

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

[Desktop-packages] [Bug 1802680] Re: Adding keyboard layout broken without logout

[Matt Arsenault]

This was after updating to 18.04

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

Title:
  Adding keyboard layout broken without logout

Status in gnome-shell package in Ubuntu:
  Fix Committed

Bug description:
  On my system, the default keyboard layout is English (Colemak). I have
  English (US) as a secondary keyboard layout.

  I attempted to add Russian, which worked. However, when I switched to
  it using Super+Space, input was really done in Qwerty. Both Russian
  and English (US) were effectively qwerty options until I logged out
  and back in.

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

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

[Desktop-packages] [Bug 1336924] Re: after a period I can't use the keyboard inside inkscape window

[Matt F]

I've had this same problem. Saving through the menu and restarting fixes
it for me, but when it happens every few minutes, even that becomes
annoying.

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

Title:
  after a period I can't use the keyboard inside inkscape window

Status in Inkscape:
  New
Status in inkscape package in Ubuntu:
  Confirmed

Bug description:
  It doesn't matter if it's for typing inside a box text, to change
  values in numeric boxes (for width, etc) or to write a filename when
  saving.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: inkscape 0.48.4-3ubuntu2
  ProcVersionSignature: Ubuntu 3.13.0-30.54-generic 3.13.11.2
  Uname: Linux 3.13.0-30-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  CurrentDesktop: LXDE
  Date: Wed Jul  2 22:09:33 2014
  InstallationDate: Installed on 2014-06-23 (9 days ago)
  InstallationMedia: Lubuntu 14.04 LTS "Trusty Tahr" - Release amd64 
(20140416.2)
  SourcePackage: inkscape
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1802680] [NEW] Adding keyboard layout broken without logout

[Matt Arsenault]

Public bug reported:

On my system, the default keyboard layout is English (Colemak). I have
English (US) as a secondary keyboard layout.

I attempted to add Russian, which worked. However, when I switched to it
using Super+Space, input was really done in Qwerty. Both Russian and
English (US) were effectively qwerty options until I logged out and back
in.

** 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/1802680

Title:
  Adding keyboard layout broken without logout

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

Bug description:
  On my system, the default keyboard layout is English (Colemak). I have
  English (US) as a secondary keyboard layout.

  I attempted to add Russian, which worked. However, when I switched to
  it using Super+Space, input was really done in Qwerty. Both Russian
  and English (US) were effectively qwerty options until I logged out
  and back in.

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

-- 
Mailing list: https://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 1747717] Re: package gnome-menus 3.13.3-11ubuntu1 failed to install/upgrade: triggers looping, abandoned - gnome-menus -> ufw

[Matt Quinn]

I am using a much more recent version of Ubuntu by now

On Mon, Nov 5, 2018, 10:01 AM Sebastien Bacher  That got no activity since june, is that still an issue? should it be
> closed?
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (1753367).
> https://bugs.launchpad.net/bugs/1747717
>
> Title:
>   package gnome-menus 3.13.3-11ubuntu1 failed to install/upgrade:
>   triggers looping, abandoned - gnome-menus -> ufw
>
> Status in dpkg package in Ubuntu:
>   Invalid
> Status in gnome-menus package in Ubuntu:
>   Incomplete
> Status in dpkg source package in Bionic:
>   Invalid
> Status in gnome-menus source package in Bionic:
>   Incomplete
>
> Bug description:
>   using the bionic beaver version
>
>   ProblemType: Package
>   DistroRelease: Ubuntu 18.04
>   Package: gnome-menus 3.13.3-11ubuntu1
>   Uname: Linux 4.15.1-041501-generic x86_64
>   ApportVersion: 2.20.8-0ubuntu8
>   Architecture: amd64
>   Date: Tue Feb  6 23:00:47 2018
>   Dependencies:
>
>   ErrorMessage: triggers looping, abandoned
>   Python3Details: /usr/bin/python3.6, Python 3.6.4, python3-minimal,
> 3.6.4-1
>   PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal,
> 2.7.14-4
>   RelatedPackageVersions:
>dpkg 1.19.0.5ubuntu1
>apt  1.6~alpha7ubuntu1
>   SourcePackage: gnome-menus
>   Title: package gnome-menus 3.13.3-11ubuntu1 failed to install/upgrade:
> triggers looping, abandoned
>   UpgradeStatus: No upgrade log present (probably fresh install)
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/1747717/+subscriptions
>

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

Title:
  package gnome-menus 3.13.3-11ubuntu1 failed to install/upgrade:
  triggers looping, abandoned - gnome-menus -> ufw

Status in dpkg package in Ubuntu:
  Invalid
Status in gnome-menus package in Ubuntu:
  Incomplete
Status in dpkg source package in Bionic:
  Invalid
Status in gnome-menus source package in Bionic:
  Incomplete

Bug description:
  using the bionic beaver version

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: gnome-menus 3.13.3-11ubuntu1
  Uname: Linux 4.15.1-041501-generic x86_64
  ApportVersion: 2.20.8-0ubuntu8
  Architecture: amd64
  Date: Tue Feb  6 23:00:47 2018
  Dependencies:
   
  ErrorMessage: triggers looping, abandoned
  Python3Details: /usr/bin/python3.6, Python 3.6.4, python3-minimal, 3.6.4-1
  PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu1
   apt  1.6~alpha7ubuntu1
  SourcePackage: gnome-menus
  Title: package gnome-menus 3.13.3-11ubuntu1 failed to install/upgrade: 
triggers looping, abandoned
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1754693] Re: Xwayland crashed with SIGABRT in st_renderbuffer_delete() [often when running Skype or Slack snaps]

[Matt Johnson]

I recently switched back to Ubuntu, only to find that Slack in a snap is
still crashing on Wayland! I previously reported what seems like a
related bug on snapcraft-- here's the link to the related bug with logs
and some details from experiences on Fedora28 and Arch.
https://forum.snapcraft.io/t/slack-for-linux-crash-on-wayland/5909

Currently still experiencing the issue with Ubuntu 18.10:

```
$ snap info slack
name: slack
summary: Team communication for the 21st century.
publisher: Slack✓
contact: https://get.slack.help/hc/en-us
license: Proprietary
description: |
  Caution: Slack for Linux is in beta. We’re still busy adding features and 
ironing out potential
  issues.

  Slack brings team communication and collaboration into one place so you can 
get more work done,
  whether you belong to a large enterprise or a small business. Check off your 
to-do list and move
  your projects forward by bringing the right people, conversations, tools, and 
information you need
  together. Slack is available on any device, so you can find and access your 
team and your work,
  whether you’re at your desk or on the go.

  Scientifically proven (or at least rumored) to make your working life 
simpler, more pleasant, and
  more productive. We hope you’ll give Slack a try.

  Stop by and learn more at: https://slack.com/
snap-id: JUJH91Ved74jd4ZgJCpzMBtYbPOzTlsD
channels:
  stable: 3.3.3 (9) 148MB classic
  candidate: ↑
  beta: ↑
  edge: 3.3.1 (8) 148MB classic
```

```
$ snap --version
snap 2.35.5+18.10
snapd 2.35.5+18.10
series 16
ubuntu 18.10
kernel 4.18.0-10-generic
```

I'm happy to provide any testing or log resources-- let me know if
there's anything I can help out with!

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

Title:
  Xwayland crashed with SIGABRT in st_renderbuffer_delete() [often when
  running Skype or Slack snaps]

Status in mesa package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  https://errors.ubuntu.com/problem/01a80d2110a46f6b6d857ce814079646e695f4ca

  ---

  Steps to reproduce:
  Install 'slack' snap:

     sudo snap install slack --classic

  Run slack:

     slack

  Instacrash.

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: xwayland 2:1.19.6-1ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  .tmp.unity_support_test.0:

  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,decor,mousepoll,grid,vpswitch,compiztoolbox,imgpng,gnomecompat,regex,move,place,resize,snap,unitymtgrabhandles,wall,animation,session,expo,workarounds,fade,ezoom,scale,unityshell]
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Fri Mar  9 10:31:06 2018
  DistUpgraded: 2018-03-06 13:58:47,853 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: bionic
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/Xwayland
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics 
Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller])
     Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v3/4th Gen Core Processor 
Integrated Graphics Controller [1043:8534]
  MachineType: ASUS All Series
  ProcCmdline: /usr/bin/Xwayland :0 -rootless -terminate -accessx -core -listen 
4 -listen 5 -displayfd 6
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic 
root=UUID=cd444f9d-672e-4d7b-aea8-657fff0ea1f4 ro quiet splash 
crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M nomdmonddf 
nomdmonisw crashkernel=384M-:128M nomdmonddf nomdmonisw crashkernel=384M-:128M 
nomdmonddf nomdmonisw crashkernel=384M-:128M nomdmonddf nomdmonisw 
crashkernel=384M-:128M nomdmonddf nomdmonisw crashkernel=384M-:128M nomdmonddf 
nomdmonisw crashkernel=384M-:128M nomdmonddf nomdmonisw crashkernel=384M-:128M 
crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M 
crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M 
crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M 
crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M 
crashkernel=384M-:128M vt.handoff=1
  Signal: 6
  SourcePackage: xorg-server
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so
  Title: Xwayland crashed with SIGABRT
  UpgradeStatus: Upgraded to bionic on 2018-03-06 (2 days ago)
  UserGroups: adm admin audio cdrom chroot-admin dialout dip egbuild fax floppy 
fuse libvirt libvirtd lpadmin lxd plugdev sambashare sud

[Desktop-packages] [Bug 1760252] Re: starting slack crashes xwayland on 18.04

[Matt Johnson]

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

I recently switched back to Ubuntu, only to find that Slack in a snap is
still crashing on Wayland! I previously reported what seems like a
related bug on snapcraft-- here's the link to the related bug with logs
and some details from experiences on Fedora28 and Arch.
https://forum.snapcraft.io/t/slack-for-linux-crash-on-wayland/5909

Currently still experiencing the issue with Ubuntu 18.10:

```
$ snap info slack
name:  slack
summary:   Team communication for the 21st century.
publisher: Slack✓
contact:   https://get.slack.help/hc/en-us
license:   Proprietary
description: |
  Caution: Slack for Linux is in beta. We’re still busy adding features and 
ironing out potential
  issues.
  
  Slack brings team communication and collaboration into one place so you can 
get more work done,
  whether you belong to a large enterprise or a small business. Check off your 
to-do list and move
  your projects forward by bringing the right people, conversations, tools, and 
information you need
  together. Slack is available on any device, so you can find and access your 
team and your work,
  whether you’re at your desk or on the go.
  
  Scientifically proven (or at least rumored) to make your working life 
simpler, more pleasant, and
  more productive. We hope you’ll give Slack a try.
  
  Stop by and learn more at: https://slack.com/
snap-id: JUJH91Ved74jd4ZgJCpzMBtYbPOzTlsD
channels:
  stable:3.3.3 (9) 148MB classic
  candidate: ↑   
  beta:  ↑   
  edge:  3.3.1 (8) 148MB classic
```

```
$ snap --version
snap2.35.5+18.10
snapd   2.35.5+18.10
series  16
ubuntu  18.10
kernel  4.18.0-10-generic
```

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

Title:
  starting slack crashes xwayland on 18.04

Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  steps to reproduce on 18.04:
  1. $ sudo snap install slack --classic
  2. $ slack
  3. the desktop env crashes with following trace, and need to login again:

  (EE)
  (EE) Backtrace:
  (EE) 0: /usr/bin/Xwayland (xorg_backtrace+0x4d) [0x56286f1996bd]
  (EE) 1: /usr/bin/Xwayland (0x56286eff1000+0x1ac459) [0x56286f19d459]
  (EE) 2: /lib/x86_64-linux-gnu/libpthread.so.0 (0x7fafb7322000+0x12890) 
[0x7fafb7334890]
  (EE) 3: /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so (0x7fafb0bd5000+0x24e9e3) 
[0x7fafb0e
  (EE) 4: /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so (0x7fafb0bd5000+0x1b3ed4) 
[0x7fafb0d
  (EE) 5: /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so (0x7fafb0bd5000+0x144c6a) 
[0x7fafb0d
  (EE) 6: /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so (0x7fafb0bd5000+0x144cae) 
[0x7fafb0d
  (EE) 7: /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so (0x7fafb0bd5000+0x144d1c) 
[0x7fafb0d
  (EE) 8: /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so (0x7fafb0bd5000+0xad4b2) 
[0x7fafb0c8
  (EE) 9: /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so (0x7fafb0bd5000+0x25b6db) 
[0x7fafb0e
  (EE) 10: /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so 
(0x7fafb0bd5000+0x3e2ae5) [0x7fafb0
  (EE) 11: /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so 
(0x7fafb0bd5000+0x3e1a13) [0x7fafb0
  (EE) 12: /usr/bin/Xwayland (0x56286eff1000+0xc8989) [0x56286f0b9989]
  (EE) 13: /usr/bin/Xwayland (0x56286eff1000+0xc7975) [0x56286f0b8975]
  (EE) 14: /usr/bin/Xwayland (0x56286eff1000+0x1969f2) [0x56286f1879f2]
  (EE) 15: /usr/bin/Xwayland (0x56286eff1000+0xcc5f7) [0x56286f0bd5f7]
  (EE) 16: /usr/bin/Xwayland (0x56286eff1000+0xc7c3c) [0x56286f0b8c3c]
  (EE) 17: /usr/bin/Xwayland (0x56286eff1000+0x171ec8) [0x56286f162ec8]
  (EE) 18: /usr/bin/Xwayland (0x56286eff1000+0x175f10) [0x56286f166f10]
  (EE) 19: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xe7) 
[0x7fafb6f52b97]
  (EE) 20: /usr/bin/Xwayland (_start+0x2a) [0x56286f02bada]
  (EE)
  (EE) Segmentation fault at address 0x68
  (EE)
  Fatal server error:
  (EE) Caught signal 11 (Segmentation fault). Server aborting
  (EE)

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

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

[Desktop-packages] [Bug 1797782] Re: evince immediately seg faults

[Matt Sienko]

I uploaded the sample pdf though the launchpad web instead of attaching
it to an email. evince crashes for me when I try to open it.

** Attachment added: "sample pdf for evince segmentation fault"
   
https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1797782/+attachment/5201784/+files/sample.pdf

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

Title:
  evince immediately seg faults

Status in evince package in Ubuntu:
  Incomplete

Bug description:
  
  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04

  evince:
Installed: 3.28.2-1
Candidate: 3.28.2-1
Version table:
   *** 3.28.2-1 500
  500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status

  Expected Behavior: evince opens and displays PDF document.

  What Happened: When launching evince, it crashes immediately with a
  segmentation fault. This happens every time. I have tried opening
  multiple PDF documents both from the command line and file browser.
  Launching evince from the command line without specifying a file also
  crashes. The PDF documents open fine in xpdf.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: evince 3.28.2-1
  ProcVersionSignature: Ubuntu 4.15.0-1021.24-oem 4.15.18
  Uname: Linux 4.15.0-1021-oem x86_64
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct 14 08:29:01 2018
  InstallationDate: Installed on 2018-09-23 (20 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: evince
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://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 1797782] Re: evince immediately seg faults

[Matt Sienko]

I tried to attach a file that was too big. Here is a smaller one that
also causes the crash.

On Sunday, October 14, 2018, 3:24:15 PM PDT, Matthew Sienko 
 wrote:  
 
  Christian,I attached a pdf that evince crashes trying to open, although every 
pdf I tried has caused a crash.
Here is the result of ls /var/crash:_usr_bin_evince.1001.crash   
_usr_bin_evince.1001.uploaded
_usr_bin_evince.1001.upload

Thanks,  -Matt

On Sunday, October 14, 2018, 11:15:37 AM PDT, Cristian Aravena Romero 
 wrote:  
 
 Hello,

Could you send a .pdf file to try to reproduce the error?

Best regards,
--
Cristian Aravena Romero (caravena)

-- 
You received this bug notification because you are subscribed to the bug
report.
https://bugs.launchpad.net/bugs/1797782

Title:
  evince immediately seg faults

Status in evince package in Ubuntu:
  Incomplete

Bug description:
  
  Description:    Ubuntu 18.04.1 LTS
  Release:    18.04

  evince:
    Installed: 3.28.2-1
    Candidate: 3.28.2-1
    Version table:
  *** 3.28.2-1 500
          500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages
          100 /var/lib/dpkg/status

  Expected Behavior: evince opens and displays PDF document.

  What Happened: When launching evince, it crashes immediately with a
  segmentation fault. This happens every time. I have tried opening
  multiple PDF documents both from the command line and file browser.
  Launching evince from the command line without specifying a file also
  crashes. The PDF documents open fine in xpdf.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: evince 3.28.2-1
  ProcVersionSignature: Ubuntu 4.15.0-1021.24-oem 4.15.18
  Uname: Linux 4.15.0-1021-oem x86_64
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct 14 08:29:01 2018
  InstallationDate: Installed on 2018-09-23 (20 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
  ProcEnviron:
  PATH=(custom, no user)
  XDG_RUNTIME_DIR=
  LANG=en_US.UTF-8
  SHELL=/bin/bash
  SourcePackage: evince
  UpgradeStatus: No upgrade log present (probably fresh install)

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

** Attachment added: "=?UTF-8?b?c2FtcGxlLnBkZg==?="
   
https://bugs.launchpad.net/bugs/1797782/+attachment/5200965/+files/%3D%3FUTF-8%3Fb%3Fc2FtcGxlLnBkZg%3D%3D%3F%3D

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

Title:
  evince immediately seg faults

Status in evince package in Ubuntu:
  Incomplete

Bug description:
  
  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04

  evince:
Installed: 3.28.2-1
Candidate: 3.28.2-1
Version table:
   *** 3.28.2-1 500
  500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status

  Expected Behavior: evince opens and displays PDF document.

  What Happened: When launching evince, it crashes immediately with a
  segmentation fault. This happens every time. I have tried opening
  multiple PDF documents both from the command line and file browser.
  Launching evince from the command line without specifying a file also
  crashes. The PDF documents open fine in xpdf.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: evince 3.28.2-1
  ProcVersionSignature: Ubuntu 4.15.0-1021.24-oem 4.15.18
  Uname: Linux 4.15.0-1021-oem x86_64
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct 14 08:29:01 2018
  InstallationDate: Installed on 2018-09-23 (20 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: evince
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://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 1797782] Re: evince immediately seg faults

[Matt Sienko]

I tried to a

On Sunday, October 14, 2018, 3:24:15 PM PDT, Matthew Sienko 
 wrote:  
 
  Christian,I attached a pdf that evince crashes trying to open, although every 
pdf I tried has caused a crash.
Here is the result of ls /var/crash:_usr_bin_evince.1001.crash   
_usr_bin_evince.1001.uploaded
_usr_bin_evince.1001.upload

Thanks,  -Matt

On Sunday, October 14, 2018, 11:15:37 AM PDT, Cristian Aravena Romero 
 wrote:  
 
 Hello,

Could you send a .pdf file to try to reproduce the error?

Best regards,
--
Cristian Aravena Romero (caravena)

-- 
You received this bug notification because you are subscribed to the bug
report.
https://bugs.launchpad.net/bugs/1797782

Title:
  evince immediately seg faults

Status in evince package in Ubuntu:
  Incomplete

Bug description:
  
  Description:    Ubuntu 18.04.1 LTS
  Release:    18.04

  evince:
    Installed: 3.28.2-1
    Candidate: 3.28.2-1
    Version table:
  *** 3.28.2-1 500
          500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages
          100 /var/lib/dpkg/status

  Expected Behavior: evince opens and displays PDF document.

  What Happened: When launching evince, it crashes immediately with a
  segmentation fault. This happens every time. I have tried opening
  multiple PDF documents both from the command line and file browser.
  Launching evince from the command line without specifying a file also
  crashes. The PDF documents open fine in xpdf.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: evince 3.28.2-1
  ProcVersionSignature: Ubuntu 4.15.0-1021.24-oem 4.15.18
  Uname: Linux 4.15.0-1021-oem x86_64
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct 14 08:29:01 2018
  InstallationDate: Installed on 2018-09-23 (20 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
  ProcEnviron:
  PATH=(custom, no user)
  XDG_RUNTIME_DIR=
  LANG=en_US.UTF-8
  SHELL=/bin/bash
  SourcePackage: evince
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

Title:
  evince immediately seg faults

Status in evince package in Ubuntu:
  Incomplete

Bug description:
  
  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04

  evince:
Installed: 3.28.2-1
Candidate: 3.28.2-1
Version table:
   *** 3.28.2-1 500
  500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status

  Expected Behavior: evince opens and displays PDF document.

  What Happened: When launching evince, it crashes immediately with a
  segmentation fault. This happens every time. I have tried opening
  multiple PDF documents both from the command line and file browser.
  Launching evince from the command line without specifying a file also
  crashes. The PDF documents open fine in xpdf.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: evince 3.28.2-1
  ProcVersionSignature: Ubuntu 4.15.0-1021.24-oem 4.15.18
  Uname: Linux 4.15.0-1021-oem x86_64
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct 14 08:29:01 2018
  InstallationDate: Installed on 2018-09-23 (20 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: evince
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1797782] [NEW] evince immediately seg faults

[Matt Sienko]

Public bug reported:


Description:Ubuntu 18.04.1 LTS
Release:18.04

evince:
  Installed: 3.28.2-1
  Candidate: 3.28.2-1
  Version table:
 *** 3.28.2-1 500
500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages
100 /var/lib/dpkg/status

Expected Behavior: evince opens and displays PDF document.

What Happened: When launching evince, it crashes immediately with a
segmentation fault. This happens every time. I have tried opening
multiple PDF documents both from the command line and file browser.
Launching evince from the command line without specifying a file also
crashes. The PDF documents open fine in xpdf.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: evince 3.28.2-1
ProcVersionSignature: Ubuntu 4.15.0-1021.24-oem 4.15.18
Uname: Linux 4.15.0-1021-oem x86_64
ApportVersion: 2.20.9-0ubuntu7.4
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sun Oct 14 08:29:01 2018
InstallationDate: Installed on 2018-09-23 (20 days ago)
InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: evince
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apparmor apport-bug bionic

** Attachment added: "Crash report from running evince on command line"
   
https://bugs.launchpad.net/bugs/1797782/+attachment/5200859/+files/_usr_bin_evince.1001.crash

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

Title:
  evince immediately seg faults

Status in evince package in Ubuntu:
  New

Bug description:
  
  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04

  evince:
Installed: 3.28.2-1
Candidate: 3.28.2-1
Version table:
   *** 3.28.2-1 500
  500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status

  Expected Behavior: evince opens and displays PDF document.

  What Happened: When launching evince, it crashes immediately with a
  segmentation fault. This happens every time. I have tried opening
  multiple PDF documents both from the command line and file browser.
  Launching evince from the command line without specifying a file also
  crashes. The PDF documents open fine in xpdf.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: evince 3.28.2-1
  ProcVersionSignature: Ubuntu 4.15.0-1021.24-oem 4.15.18
  Uname: Linux 4.15.0-1021-oem x86_64
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct 14 08:29:01 2018
  InstallationDate: Installed on 2018-09-23 (20 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: evince
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1778361] Re: The Processes tab only displays the current user's processes

[Matt]

This appears to be specific to packaging as a "snap" without appropriate 
privileges
Removing the default snap install and installing gnome-system-monitor via apt 
shows all processes, including root, as per expected operation

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

Title:
  The Processes tab only displays the current user's processes

Status in gnome-system-monitor package in Ubuntu:
  Confirmed

Bug description:
  ***
  *** Please attribute this bug to the correct package.
  ***

  ubuntu-bug -w failed.

  The "All Processes" option only displays the current user's processes.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gedit 3.28.1-1ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jun 23 17:02:00 2018
  InstallationDate: Installed on 2018-05-03 (50 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180425.1)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gedit
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1791481] [NEW] switch user appears to function, but machine is frozen. Logout also freezes with black screen

[matt scott]

Public bug reported:

9-8-018


I suspect this is a gdm3 bug as a similar bug was reported earlier with blank 
purple screen.  This is running a fully updated fresh install  september-8-018

some switch user operations function. Others result in a successful
appearance, but the machine is non-responsive. alt-f1 etc.  do nothing.
Also, logout results in hangup at black screen.

When the user switch works, the mouse pointer shows up bottom right.
When the switch appears to work, but doesn't, the mouse pointer shows up
at top right, but the machine is frozen. Also, the machine appears to
pick a favored user and an unfavored user .. freezing for one and
working for the other. In an earlier install, the original user was the
favored user ..  for current install, the second user seems to be
favored and the original user unfavored.  This may simply be caused by
some sort of toggling effect I suppose, and have nothing to do with the
user.

I am running a ubuntu 18.04 amd64 system on
Dell optiplex 745 with
core 2 duo 3.16 ghz
and an SSD

/var/crash folder is empty
/var/log/gdm3 is empty

matt@Wallace:~$ apt list gdm3
Listing... Done
gdm3/bionic-updates,bionic-security,now 3.28.2-0ubuntu1.4 amd64 [installed]
N: There is 1 additional version. Please use the '-a' switch to see it
matt@Wallace:~$ apt list gdm3 -a
Listing... Done
gdm3/bionic-updates,bionic-security,now 3.28.2-0ubuntu1.4 amd64 [installed]
gdm3/bionic 3.28.0-0ubuntu1 amd64

this appears to be regression of 1766137 from my perspective

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

** Description changed:

  I suspect this is a gdm3 bug as a similar bug was reported earlier with
  blank purple screen.  This is running a fully updated fresh install
  september-8-018
  
  some switch user operations function. Others result in a successful
  appearance, but the machine is non-responsive. alt-f1 etc.  do nothing.
  Also, logout results in hangup at black screen.
  
  When the user switch works, the mouse pointer shows up bottom right.
- When the login appears to work, but doesn't, the mouse pointer shows up
+ When the switch appears to work, but doesn't, the mouse pointer shows up
  at top right, but the machine is frozen. Also, the machine appears to
  pick a favored user and an unfavored user .. freezing for one and
  working for the other. In an earlier install, the original user was the
  favored user ..  for current install, the second user seems to be
  favored and the original user unfavored.  This may simply be caused by
  some sort of toggling effect I suppose, and have nothing to do with the
  user.
  
- I am running a ubuntu 18.04 amd64 system on 
- Dell optiplex 745 with 
+ I am running a ubuntu 18.04 amd64 system on
+ Dell optiplex 745 with
  core 2 duo 3.16 ghz
  and an SSD
  
  /var/crash folder is empty
  /var/log/gdm3 is empty
- 
  
  matt@Wallace:~$ apt list gdm3
  Listing... Done
  gdm3/bionic-updates,bionic-security,now 3.28.2-0ubuntu1.4 amd64 [installed]
  N: There is 1 additional version. Please use the '-a' switch to see it
  matt@Wallace:~$ apt list gdm3 -a
  Listing... Done
  gdm3/bionic-updates,bionic-security,now 3.28.2-0ubuntu1.4 amd64 [installed]
  gdm3/bionic 3.28.0-0ubuntu1 amd64
  
- 
  this appears to be regression of 1766137 from my perspective

** Description changed:

- I suspect this is a gdm3 bug as a similar bug was reported earlier with
- blank purple screen.  This is running a fully updated fresh install
- september-8-018
+ 9-8-018
+ 
+ 
+ I suspect this is a gdm3 bug as a similar bug was reported earlier with blank 
purple screen.  This is running a fully updated fresh install  september-8-018
  
  some switch user operations function. Others result in a successful
  appearance, but the machine is non-responsive. alt-f1 etc.  do nothing.
  Also, logout results in hangup at black screen.
  
  When the user switch works, the mouse pointer shows up bottom right.
  When the switch appears to work, but doesn't, the mouse pointer shows up
  at top right, but the machine is frozen. Also, the machine appears to
  pick a favored user and an unfavored user .. freezing for one and
  working for the other. In an earlier install, the original user was the
  favored user ..  for current install, the second user seems to be
  favored and the original user unfavored.  This may simply be caused by
  some sort of toggling effect I suppose, and have nothing to do with the
  user.
  
  I am running a ubuntu 18.04 amd64 system on
  Dell optiplex 745 with
  core 2 duo 3.16 ghz
  and an SSD
  
  /var/crash folder is empty
  /var/log/gdm3 is empty
  
  matt@Wallace:~$ apt list gdm3
  Listing... Done
  gdm3/bionic-updates,bionic-security,now 3.28.2-0ubuntu1.4 amd64 [installed]
  N: There is 1 additional version. Please use the '-a' switch to see it
  matt@Wallace:~$ apt list gdm3 -a
  Listing... Done
  gdm3/bionic-updates,bionic-security,now 3.28.2-0ubuntu1.4 amd

[Desktop-packages] [Bug 1766137] Re: [regression] Password accepted but login fails (blank purple screen and mouse pointer only)

[matt scott]

9-8-018 fresh install with updates .. some user switches work, some
don't logout is also crashing with irresponsive black screen. When the
user switch fails, the description is slightly different from above. If
the mouse pointer comes in at lower right, the user switch works. If it
comes in upper right, then the mouse fails, alt-F1 etc.  all do nothing,
and rather than blank purple screen, I have what appears to be a
successful login, but the system is completely non-responsive.

dell optiplex 755 
SSd
3.16 GHZ core 2 duo

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

Title:
  [regression] Password accepted but login fails (blank purple screen
  and mouse pointer only)

Status in gdm:
  Fix Released
Status in Release Notes for Ubuntu:
  Fix Released
Status in gdm3 package in Ubuntu:
  Fix Released
Status in gnome-shell package in Ubuntu:
  Invalid
Status in gdm3 source package in Bionic:
  Fix Released
Status in gnome-shell source package in Bionic:
  Invalid

Bug description:
  [ Description ]

  Due to a refcounting bug, a GDBusConnection was getting disposed when
  it was still required. The symptom of this was that you couldn't log
  in on the second attempt if you'd got your password wrong on the first
  attempt. All you'd see is a blank purple screen and mouse pointer
  only.

  [ Test case ]

  1. Boot to GDM
  2. Click your username
  3. Type the wrong password a couple of times, pressing enter after each time
  4. Type the right password

  If the bug is happening, after 4. the system hangs at a blank screen
  with the mouse cursor. If you then switch to a VT or otherwise connect
  to the machine, you can examine the journal and you'll see a
  G_IS_DBUS_CONNECTION failure.

  [ Fix ]

  Marco and I worked upstream on this fix. We found out that there was a
  problem like this-

  The GdmClient has a shared GDBusConnection for its operations. The
  first time  someone calls for it, it is created and stored in the
  object's private structure. Subsequent calls return *a new reference*
  to this same object. It turned out that the asynchronous method to get
  the connection was accidentally unreferencing its object before giving
  it to the caller if it was returning an already-existing connection.

  For this to work properly, we need to nullify the pointer we stored
  when the connection goes away, so we know when to make a new one.
  There were some cases where we didn't add the weak references required
  to do that. Those are also fixed.

  [ Regression potential ]

  Now we share connections more than we did before. We also more
  carefully track when to clear our object. If we got this wrong, we
  might end up leaking the connection or dropping it in even more cases.

  [ Original report ]

  WORKAROUND: After typing an incorrect password, click Cancel, then
  click your name, then enter your password again.

  ---

  Trying to log into my session (Gnome, Xorg), if I enter the wrong
  password before entering it correctly, the session doesn't load and I
  get a purple screen, a mouse cursor, and an invisible but clickable
  menu in the top right. If I enter it correctly the first time, there
  is no problem.

  I've replicated this from a fresh boot, after logging out and after
  'sudo service gdm restart' from the Ctrl-Alt-F4 console.

  This is a fresh install, and didn't occur when I was using a previous
  install of 18.04 (until Friday).

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gdm3 3.28.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 22 20:31:13 2018
  InstallationDate: Installed on 2018-04-22 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180421.1)
  SourcePackage: gdm3
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1766137] Re: [regression] Password accepted but login fails (blank purple screen and mouse pointer only)

[matt scott]

gdm3 info. for above comment


matt@Wallace:~$ apt list gdm3
Listing... Done
gdm3/bionic-updates,bionic-security,now 3.28.2-0ubuntu1.4 amd64 [installed]
N: There is 1 additional version. Please use the '-a' switch to see it
matt@Wallace:~$ apt list gdm3 -a
Listing... Done
gdm3/bionic-updates,bionic-security,now 3.28.2-0ubuntu1.4 amd64 [installed]
gdm3/bionic 3.28.0-0ubuntu1 amd64

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

Title:
  [regression] Password accepted but login fails (blank purple screen
  and mouse pointer only)

Status in gdm:
  Fix Released
Status in Release Notes for Ubuntu:
  Fix Released
Status in gdm3 package in Ubuntu:
  Fix Released
Status in gnome-shell package in Ubuntu:
  Invalid
Status in gdm3 source package in Bionic:
  Fix Released
Status in gnome-shell source package in Bionic:
  Invalid

Bug description:
  [ Description ]

  Due to a refcounting bug, a GDBusConnection was getting disposed when
  it was still required. The symptom of this was that you couldn't log
  in on the second attempt if you'd got your password wrong on the first
  attempt. All you'd see is a blank purple screen and mouse pointer
  only.

  [ Test case ]

  1. Boot to GDM
  2. Click your username
  3. Type the wrong password a couple of times, pressing enter after each time
  4. Type the right password

  If the bug is happening, after 4. the system hangs at a blank screen
  with the mouse cursor. If you then switch to a VT or otherwise connect
  to the machine, you can examine the journal and you'll see a
  G_IS_DBUS_CONNECTION failure.

  [ Fix ]

  Marco and I worked upstream on this fix. We found out that there was a
  problem like this-

  The GdmClient has a shared GDBusConnection for its operations. The
  first time  someone calls for it, it is created and stored in the
  object's private structure. Subsequent calls return *a new reference*
  to this same object. It turned out that the asynchronous method to get
  the connection was accidentally unreferencing its object before giving
  it to the caller if it was returning an already-existing connection.

  For this to work properly, we need to nullify the pointer we stored
  when the connection goes away, so we know when to make a new one.
  There were some cases where we didn't add the weak references required
  to do that. Those are also fixed.

  [ Regression potential ]

  Now we share connections more than we did before. We also more
  carefully track when to clear our object. If we got this wrong, we
  might end up leaking the connection or dropping it in even more cases.

  [ Original report ]

  WORKAROUND: After typing an incorrect password, click Cancel, then
  click your name, then enter your password again.

  ---

  Trying to log into my session (Gnome, Xorg), if I enter the wrong
  password before entering it correctly, the session doesn't load and I
  get a purple screen, a mouse cursor, and an invisible but clickable
  menu in the top right. If I enter it correctly the first time, there
  is no problem.

  I've replicated this from a fresh boot, after logging out and after
  'sudo service gdm restart' from the Ctrl-Alt-F4 console.

  This is a fresh install, and didn't occur when I was using a previous
  install of 18.04 (until Friday).

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gdm3 3.28.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 22 20:31:13 2018
  InstallationDate: Installed on 2018-04-22 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180421.1)
  SourcePackage: gdm3
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1725384] Re: On touch screens, the apps icon in the dock does not open when touched

[Matt Ellis]

The `gnome-shell --replace' workaround seems to fix this bug for me.
However, this causes a new bug when I lock the laptop. After locking I
cannot enter my password and it is as if someone is holding down the
enter key and the words 'Authentication Error' flashes up.

I am using a Dell Inspiron 17 and Ubuntu 18.04.1 LTS. The Gnome version
is GNOME Shell 3.28.2.

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

Title:
  On touch screens, the apps icon in the dock does not open when touched

Status in Dash to dock:
  New
Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  Confirmed

Bug description:
  I have an Bangho AERO 1104 with touch screen, when I try to open the
  application drawer from the applications icon in the dock, it does not
  open.

  1)- Ubuntu 17.10 Artful Aardvark 64 bit
  2)- gnome-shell-extension-ubuntu-dock_0.7
  3)- What should happen is that touching the applications icon in the dock, 
opens the application drawer.
  4)- Instead, what has happened is that absolutely nothing happened

To manage notifications about this bug go to:
https://bugs.launchpad.net/dash-to-dock/+bug/1725384/+subscriptions

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

[Desktop-packages] [Bug 660295] Re: Title bar: Hyphen not surrounded by spaces

[Matt Giuca]

This was fixed long, long ago.

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

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

Title:
  Title bar: Hyphen not surrounded by spaces

Status in firefox package in Ubuntu:
  Fix Released

Bug description:
  Binary package hint: firefox

  In the version of Firefox included with Maverick (3.6.10+build1
  +nobinonly-0ubuntu3), there are no spaces around the hyphen in the
  title bar.

  This means what used to display as, for example, "Gmail - Inbox -
  Mozilla Firefox" now displays as "Gmail - Inbox-Mozilla Firefox" which
  looks very strange (it looks as if there is some kind of "Inbox-
  Mozilla" version of Firefox).

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

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

[Desktop-packages] [Bug 884336]

[Matt Horan]

I'm seeing a similar issue with a similar setup.  I've got a media
center connected to a receiver via HDMI.  Sometimes when I'm playing
audio and power-cycle devices in the chain (TV, receiver, etc), pulse
will stop playing audio.  I don't get any errors or anything, and
issuing pulseaudio -k will bring it all back.

I tried commenting out the module-suspend-on-idle module.  It seemed to
work at first, but I eventually got into a state where PA applications
complained about not being able to play back, and audio went silent.

I think this could be an ALSA issue, but it's quite difficult to debug.
Has anyone else come up with a solution to this problem?

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

Title:
  [Oneiric] HDMI output does not work immediately

Status in PulseAudio:
  Unknown
Status in pulseaudio package in Ubuntu:
  Invalid

Bug description:
  In Oneiric, the output of 5.1 sound (not AC3 passthrough, but multi-
  channel PCM) via the HDMI connector of my onboard Intel graphics card
  is finally working. This is really great!

  For this to work, I have configured Pulseaudio to use the "Digital
  Surround 5.1 (HDMI) Output". The HDMI output of my computer is
  connected to a 5.1 receiver.

  However, there is one nuisance: Whenever I start playing sound on the
  computer (e.g., rhythmbox or VLC, both playing via PulseAudio), I hear
  no sound. On my receiver I have to re-select the input source for the
  computer, which seems to initiate a HDMI handshake (it lasts 3
  seconds). Only after this I am able to hear sound.

  If I press pause and continue in Rhythmbox, the sound continues fine.
  If I stop and restart Rhythmbox, I have to do the above procedure
  again. The same is true for VLC and probably for all other players.

  While playing around, I have noticed that sound is also working after
  killing pulseaudio while playing something in Rhythmbox. When the
  connection to Pulseaudio is killed, Rhythmbox tries a fallback to
  ALSA. As the Pulseaudio daemon was immediately restarted, this will
  result in Rhythmbox being connected via the ALSA plugin (before the
  connection was direct). It seems that Pulseaudio is doing the
  necessary things here, because after this I do hear sound (as long as
  Rhythmbox runs). However, this trick does not work for other players
  like VLC which don't fall back to ALSA.

  Note that while for me this is just a nuisance, it may be a real
  blocker for other users. As long as you don't try to fiddle with the
  receiver inputs while playing sound on the computer, you hear
  absolutely nothing via HDMI. This includes the sounds from the speaker
  test dialog of Pulseaudio. I guess a lot of users would give up and
  think that HDMI output is broken in Ubuntu.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: pulseaudio 1:1.0-0ubuntu3
  ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4
  Uname: Linux 3.0.0-12-generic x86_64
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  ApportVersion: 1.23-0ubuntu3
  Architecture: amd64
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: PCH [HDA Intel PCH], device 0: ALC892 Analog [ALC892 Analog]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  philipp7706 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'PCH'/'HDA Intel PCH at 0xfe52 irq 50'
 Mixer name : 'Intel CougarPoint HDMI'
 Components : 'HDA:10ec0892,80862002,00100302 
HDA:80862805,80862805,0010'
 Controls  : 31
 Simple ctrls  : 16
  Date: Mon Oct 31 18:07:22 2011
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110426)
  ProcEnviron:
   LANGUAGE=de:en
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
   LC_MESSAGES=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to oneiric on 2011-10-31 (0 days ago)
  dmi.bios.date: 11/15/2010
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: BLH6710H.86A.0076.2010.1115.1959
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: DH67BL
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAG10189-205
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrBLH6710H.86A.0076.2010.1115.1959:bd11/15/2010:svn:pn:pvr:rvnIntelCorporation:rnDH67BL:rvrAAG10189-205:cvn:ct3:cvr:

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

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

[Desktop-packages] [Bug 1767536] Re: Accessing the WIFI section of the "Settings" window causes massive freezes

[Matt Chapman]

Confirming I can reproduce this on my Dell Latitude E7470 in a clean
live-boot environment for Bionic. Attaching my backtrace.

** Attachment added: "gdb-program.txt"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1767536/+attachment/5139933/+files/gdb-program.txt

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

Title:
  Accessing the WIFI section of the "Settings" window causes massive
  freezes

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

Bug description:
  Accessing the Wi-Fi section of the "Settings" window causes huge, 5-20
  seconds freezes of the window. Nothing else seems to freeze. One
  core's utilization goes up during the freeze.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-control-center 1:3.28.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 27 17:23:34 2018
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2018-04-27 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  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/1767536/+subscriptions

-- 
Mailing list: https://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 1768306] Re: LibreOffice crash

[Matt]

Well it works perfectly after that !
It just outputs "Warning: failed to read path from javaldx" in bash.

Great work :)

2018-05-02 15:31 GMT+02:00 Olivier Tilloy
:

> > OS: Ubuntu Budgie 18.04 32-bit
>
> That's very likely a duplicate of bug #1699772.
>
> To confirm this, can you run the following command in a terminal:
>
> sed -i '/enabled/c\false<\/enabled>'
> ~/.config/libreoffice/4/user/config/javasettings_Linux_*.xml
>
> Then execute libreoffice writer and let me know if the crash is still
> happening? Thanks!
>
> ** Changed in: libreoffice (Ubuntu)
>Status: New => Incomplete
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1768306
>
> Title:
>   LibreOffice crash
>
> Status in Ubuntu Budgie:
>   New
> Status in libreoffice package in Ubuntu:
>   Incomplete
>
> Bug description:
>   Whenever LibreOffice Writer is launched, it does not load and a crash
> report appears.
>   And if it is launched via the command line, it doesn't even show any
> info or error message.
>
>   The LibreOffice base and Calc opens OK though.
>
>   System info:
>
>   OS: Ubuntu Budgie 18.04 32-bit
>   PC: Sony Vaio VGN-FE21H
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntubudgie/+bug/1768306/+subscriptions
>

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

Title:
  LibreOffice crash

Status in Ubuntu Budgie:
  New
Status in libreoffice package in Ubuntu:
  Incomplete

Bug description:
  Whenever LibreOffice Writer is launched, it does not load and a crash report 
appears.
  And if it is launched via the command line, it doesn't even show any info or 
error message.

  The LibreOffice base and Calc opens OK though.

  System info:

  OS: Ubuntu Budgie 18.04 32-bit
  PC: Sony Vaio VGN-FE21H

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

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

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

[Matt Mahin]

Seeing this issue on gnome shell after recent 17.10 upgrade from 16.04
LTS.  Anytime the screen turns off, my gnome session crashes.

// seems like everything up to date with these except for xorg
sudo apt-get update
sudo apt-get upgrade
sudo apt-get dist-upgrade

$ cat /proc/version
Linux version 4.13.0-37-generic (buildd@lcy01-amd64-026) (gcc version 7.2.0 
(Ubuntu 7.2.0-8ubuntu3.2)) #42-Ubuntu SMP Wed Mar 7 14:13:23 UTC 2018


[63316.108041] [drm] Reducing the compressed framebuffer size. This may lead to 
less power savings than a non-reduced-size. Try to increase stolen memory size 
if available in BIOS.
[81819.033174] [drm] Reducing the compressed framebuffer size. This may lead to 
less power savings than a non-reduced-size. Try to increase stolen memory size 
if available in BIOS.
[81828.179633] [drm:drm_scdc_set_high_tmds_clock_ratio [drm_kms_helper]] 
*ERROR* Failed to read tmds config, err=-6
[81828.179726] [drm:intel_hdmi_handle_sink_scrambling [i915]] *ERROR* Set TMDS 
ratio failed
[81828.208165] gnome-shell[2815]: segfault at 38 ip 7f039c0bac30 sp 
7ffcecb5f918 error 4 in libmutter-1.so.0.0.0[7f039c068000+141000]
[81828.318684] rfkill: input handler enabled
[81828.328347] [drm:drm_scdc_set_high_tmds_clock_ratio [drm_kms_helper]] 
*ERROR* Failed to read tmds config, err=-6
[81828.328387] [drm:intel_hdmi_handle_sink_scrambling [i915]] *ERROR* Set TMDS 
ratio failed
[81828.328392] [drm] Reducing the compressed framebuffer size. This may lead to 
less power savings than a non-reduced-size. Try to increase stolen memory size 
if available in BIOS.
[81828.382297] [drm:drm_scdc_set_high_tmds_clock_ratio [drm_kms_helper]] 
*ERROR* Failed to read tmds config, err=-6
[81828.382318] [drm:intel_hdmi_handle_sink_scrambling [i915]] *ERROR* Set TMDS 
ratio failed
[81831.917503] [drm:drm_add_edid_modes.part.27 [drm]] *ERROR* Unknown HDMI VIC: 0
[81831.984981] [drm] Reducing the compressed framebuffer size. This may lead to 
less power savings than a non-reduced-size. Try to increase stolen memory size 
if available in BIOS.
[81879.389515] [drm:drm_add_edid_modes.part.27 [drm]] *ERROR* Unknown HDMI VIC: 0
[81880.918441] rfkill: input handler disabled
--
[82380.490818] [drm:drm_scdc_set_high_tmds_clock_ratio [drm_kms_helper]] 
*ERROR* Failed to read tmds config, err=-6
[82380.490848] [drm:intel_hdmi_handle_sink_scrambling [i915]] *ERROR* Set TMDS 
ratio failed
[82380.522584] gnome-shell[26432]: segfault at 18 ip 7f433fedfd94 sp 
7fffac254b88 error 4 in libmutter-1.so.0.0.0[7f433fe41000+141000]
[82380.633077] rfkill: input handler enabled
[82384.241961] [drm:drm_add_edid_modes.part.27 [drm]] *ERROR* Unknown HDMI VIC: 0
[82384.319360] [drm] Reducing the compressed framebuffer size. This may lead to 
less power savings than a non-reduced-size. Try to increase stolen memory size 
if available in BIOS.
[82403.842828] [drm:drm_add_edid_modes.part.27 [drm]] *ERROR* Unknown HDMI VIC: 0
[82406.263963] rfkill: input handler disabled
--
[83520.980283] [drm:drm_scdc_set_high_tmds_clock_ratio [drm_kms_helper]] 
*ERROR* Failed to read tmds config, err=-6
[83520.980375] [drm:intel_hdmi_handle_sink_scrambling [i915]] *ERROR* Set TMDS 
ratio failed
[83521.030747] gnome-shell[28547]: segfault at 204 ip 0204 sp 
7fff0db270d8 error 14
[83521.142243] rfkill: input handler enabled
[83521.146802] [drm:drm_scdc_set_high_tmds_clock_ratio [drm_kms_helper]] 
*ERROR* Failed to read tmds config, err=-6
[83521.146837] [drm:intel_hdmi_handle_sink_scrambling [i915]] *ERROR* Set TMDS 
ratio failed
[83521.146842] [drm] Reducing the compressed framebuffer size. This may lead to 
less power savings than a non-reduced-size. Try to increase stolen memory size 
if available in BIOS.
[83521.200710] [drm:drm_scdc_set_high_tmds_clock_ratio [drm_kms_helper]] 
*ERROR* Failed to read tmds config, err=-6
[83521.200729] [drm:intel_hdmi_handle_sink_scrambling [i915]] *ERROR* Set TMDS 
ratio failed
[83524.729044] [drm:drm_add_edid_modes.part.27 [drm]] *ERROR* Unknown HDMI VIC: 0
[83524.791074] [drm] Reducing the compressed framebuffer size. This may lead to 
less power savings than a non-reduced-size. Try to increase stolen memory size 
if available in BIOS.
[83537.884721] [drm:drm_add_edid_modes.part.27 [drm]] *ERROR* Unknown HDMI VIC: 0
[83539.367993] rfkill: input handler disabled
[83545.807155] sd 2:0:0:0: [sda] tag#0 FAILED Result: hostbyte=DID_OK 
driverbyte=DRIVER_SENSE
[83545.807160] sd 2:0:0:0: [sda] tag#0 Sense Key : Not Ready [current] 
[83545.807164] sd 2:0:0:0: [sda] tag#0 Add. Sense: Medium not present
[83545.807169] sd 2:0:0:0: [sda] tag#0 CDB: Read(10) 28 00 00 00 20 00 00 00 01 
00
[83545.807171] print_req_error: I/O error, dev sda, sector 8192
[83545.807191] FAT-fs (sda1): unable to read boot sector

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

Title:
  Artful (17.10) Session 

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

[Matt Mahin]

Issue is mitigated by enabling Automatic screen lock when screen turns
off.

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

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

Status in GNOME Shell:
  Unknown
Status in gnome-shell package in Ubuntu:
  Invalid
Status in mutter package in Ubuntu:
  Invalid

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

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

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

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

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

[Matt Mahin]

Seeing this issue on gnome shell after recent 17.10 upgrade from 16.04
LTS.  Anytime the screen turns off, my gnome session crashes.

// seems like everything up to date with these except for xorg
sudo apt-get update
sudo apt-get upgrade
sudo apt-get dist-upgrade

$ cat /proc/version
Linux version 4.13.0-37-generic (buildd@lcy01-amd64-026) (gcc version 7.2.0 
(Ubuntu 7.2.0-8ubuntu3.2)) #42-Ubuntu SMP Wed Mar 7 14:13:23 UTC 2018


[63316.108041] [drm] Reducing the compressed framebuffer size. This may lead to 
less power savings than a non-reduced-size. Try to increase stolen memory size 
if available in BIOS.
[81819.033174] [drm] Reducing the compressed framebuffer size. This may lead to 
less power savings than a non-reduced-size. Try to increase stolen memory size 
if available in BIOS.
[81828.179633] [drm:drm_scdc_set_high_tmds_clock_ratio [drm_kms_helper]] 
*ERROR* Failed to read tmds config, err=-6
[81828.179726] [drm:intel_hdmi_handle_sink_scrambling [i915]] *ERROR* Set TMDS 
ratio failed
[81828.208165] gnome-shell[2815]: segfault at 38 ip 7f039c0bac30 sp 
7ffcecb5f918 error 4 in libmutter-1.so.0.0.0[7f039c068000+141000]
[81828.318684] rfkill: input handler enabled
[81828.328347] [drm:drm_scdc_set_high_tmds_clock_ratio [drm_kms_helper]] 
*ERROR* Failed to read tmds config, err=-6
[81828.328387] [drm:intel_hdmi_handle_sink_scrambling [i915]] *ERROR* Set TMDS 
ratio failed
[81828.328392] [drm] Reducing the compressed framebuffer size. This may lead to 
less power savings than a non-reduced-size. Try to increase stolen memory size 
if available in BIOS.
[81828.382297] [drm:drm_scdc_set_high_tmds_clock_ratio [drm_kms_helper]] 
*ERROR* Failed to read tmds config, err=-6
[81828.382318] [drm:intel_hdmi_handle_sink_scrambling [i915]] *ERROR* Set TMDS 
ratio failed
[81831.917503] [drm:drm_add_edid_modes.part.27 [drm]] *ERROR* Unknown HDMI VIC: 0
[81831.984981] [drm] Reducing the compressed framebuffer size. This may lead to 
less power savings than a non-reduced-size. Try to increase stolen memory size 
if available in BIOS.
[81879.389515] [drm:drm_add_edid_modes.part.27 [drm]] *ERROR* Unknown HDMI VIC: 0
[81880.918441] rfkill: input handler disabled
--
[82380.490818] [drm:drm_scdc_set_high_tmds_clock_ratio [drm_kms_helper]] 
*ERROR* Failed to read tmds config, err=-6
[82380.490848] [drm:intel_hdmi_handle_sink_scrambling [i915]] *ERROR* Set TMDS 
ratio failed
[82380.522584] gnome-shell[26432]: segfault at 18 ip 7f433fedfd94 sp 
7fffac254b88 error 4 in libmutter-1.so.0.0.0[7f433fe41000+141000]
[82380.633077] rfkill: input handler enabled
[82384.241961] [drm:drm_add_edid_modes.part.27 [drm]] *ERROR* Unknown HDMI VIC: 0
[82384.319360] [drm] Reducing the compressed framebuffer size. This may lead to 
less power savings than a non-reduced-size. Try to increase stolen memory size 
if available in BIOS.
[82403.842828] [drm:drm_add_edid_modes.part.27 [drm]] *ERROR* Unknown HDMI VIC: 0
[82406.263963] rfkill: input handler disabled
--
[83520.980283] [drm:drm_scdc_set_high_tmds_clock_ratio [drm_kms_helper]] 
*ERROR* Failed to read tmds config, err=-6
[83520.980375] [drm:intel_hdmi_handle_sink_scrambling [i915]] *ERROR* Set TMDS 
ratio failed
[83521.030747] gnome-shell[28547]: segfault at 204 ip 0204 sp 
7fff0db270d8 error 14
[83521.142243] rfkill: input handler enabled
[83521.146802] [drm:drm_scdc_set_high_tmds_clock_ratio [drm_kms_helper]] 
*ERROR* Failed to read tmds config, err=-6
[83521.146837] [drm:intel_hdmi_handle_sink_scrambling [i915]] *ERROR* Set TMDS 
ratio failed
[83521.146842] [drm] Reducing the compressed framebuffer size. This may lead to 
less power savings than a non-reduced-size. Try to increase stolen memory size 
if available in BIOS.
[83521.200710] [drm:drm_scdc_set_high_tmds_clock_ratio [drm_kms_helper]] 
*ERROR* Failed to read tmds config, err=-6
[83521.200729] [drm:intel_hdmi_handle_sink_scrambling [i915]] *ERROR* Set TMDS 
ratio failed
[83524.729044] [drm:drm_add_edid_modes.part.27 [drm]] *ERROR* Unknown HDMI VIC: 0
[83524.791074] [drm] Reducing the compressed framebuffer size. This may lead to 
less power savings than a non-reduced-size. Try to increase stolen memory size 
if available in BIOS.
[83537.884721] [drm:drm_add_edid_modes.part.27 [drm]] *ERROR* Unknown HDMI VIC: 0
[83539.367993] rfkill: input handler disabled
[83545.807155] sd 2:0:0:0: [sda] tag#0 FAILED Result: hostbyte=DID_OK 
driverbyte=DRIVER_SENSE
[83545.807160] sd 2:0:0:0: [sda] tag#0 Sense Key : Not Ready [current] 
[83545.807164] sd 2:0:0:0: [sda] tag#0 Add. Sense: Medium not present
[83545.807169] sd 2:0:0:0: [sda] tag#0 CDB: Read(10) 28 00 00 00 20 00 00 00 01 
00
[83545.807171] print_req_error: I/O error, dev sda, sector 8192
[83545.807191] FAT-fs (sda1): unable to read boot sector

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

Title:
  Artful (17.10) Session