date:20220329

** Bug watch added: github.com/ubuntu/yaru/issues #3087
   https://github.com/ubuntu/yaru/issues/3087

** Also affects: yaru via
   https://github.com/ubuntu/yaru/issues/3087
   Importance: Unknown
   Status: Unknown

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

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

Title:
  Ubuntu Dock changes look/breaks in High Contrast

Status in Yaru Theme:
  Unknown
Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  Won't Fix
Status in yaru-theme package in Ubuntu:
  Fix Released

Bug description:
  When switching to High Contrast on Ubuntu Impish, the Ubuntu Dock
  detaches from the margin, changes look and expands. The expansion
  pushes the "Show Applications" button half-way outside the
  shell/display.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: gnome-shell 40.5-1ubuntu1
  Uname: Linux 5.14.9-xanmod2 x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu69
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct  5 01:49:19 2021
  DisplayManager: gdm3
  InstallationDate: Installed on 2021-04-03 (184 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Beta amd64 (20210402)
  RelatedPackageVersions: mutter-common 40.5-1ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Desktop-packages] [Bug 1725486] Re: tracker-miner-fs crashed with SIGSEGV in g_type_check_instance_is_a()

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

** Changed in: tracker-miners (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  tracker-miner-fs crashed with SIGSEGV in g_type_check_instance_is_a()

Status in tracker-miners package in Ubuntu:
  Expired

Bug description:
  I was navigating in the file system and expanded a folder. I was
  playing with the settings of the file manager during that time.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: tracker-miner-fs 2.0.2-1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct 20 17:16:00 2017
  ExecutablePath: /usr/lib/tracker/tracker-miner-fs
  InstallationDate: Installed on 2017-10-19 (1 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  ProcCmdline: /usr/lib/tracker/tracker-miner-fs
  ProcEnviron:
   LANGUAGE=en_CA:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7fb3202e177e :
testb  $0x4,0x16(%rdx)
   PC (0x7fb3202e177e) ok
   source "$0x4" ok
   destination "0x16(%rdx)" (0x656572662e677282) not located in a known VMA 
region (needed writable region)!
  SegvReason: writing unknown VMA
  Signal: 11
  SourcePackage: tracker-miners
  StacktraceTop:
   g_type_check_instance_is_a () from 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_file_equal () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   ?? ()
   ?? ()
   ?? () from /usr/lib/x86_64-linux-gnu/libtracker-miner-2.0.so.0
  Title: tracker-miner-fs crashed with SIGSEGV in g_type_check_instance_is_a()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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


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

[Desktop-packages] [Bug 1724971] Re: tracker-extract crashed with SIGSEGV in g_str_hash()

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

** Changed in: tracker-miners (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  tracker-extract crashed with SIGSEGV in g_str_hash()

Status in tracker-miners package in Ubuntu:
  Expired

Bug description:
  I recently updated from ubuntu-gnome 17.04 to ubuntu 17.10. Now I'm
  getting this error all the time!

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: tracker-extract 2.0.2-1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: GNOME-Classic:GNOME
  Date: Thu Oct 19 22:31:53 2017
  ExecutablePath: /usr/lib/tracker/tracker-extract
  InstallationDate: Installed on 2017-04-30 (172 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
  ProcCmdline: /usr/lib/tracker/tracker-extract
  ProcEnviron:
   LANGUAGE=de_AT:de
   PATH=(custom, user)
   XDG_RUNTIME_DIR=
   LANG=de_AT.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7facf7fd41f0 :   movsbl (%rdi),%edx
   PC (0x7facf7fd41f0) ok
   source "(%rdi)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%edx" ok
   Stack memory exhausted (SP below stack segment)
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: tracker-miners
  StacktraceTop:
   g_str_hash () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_hash_table_lookup () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   osinfo_db_identify_media () from /usr/lib/x86_64-linux-gnu/libosinfo-1.0.so.0
   tracker_extract_get_metadata () from 
/usr/lib/x86_64-linux-gnu/tracker-miners-2.0/extract-modules/libextract-iso.so
   ?? ()
  Title: tracker-extract crashed with SIGSEGV in g_str_hash()
  UpgradeStatus: Upgraded to artful on 2017-10-19 (0 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev roccat sambashare sudo

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


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

[Desktop-packages] [Bug 1726541] Re: tracker-miner-fs crashed with signal 7 in tracker_ontologies_get_class_value_gvdb()

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

** Changed in: tracker-miners (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  tracker-miner-fs crashed with signal 7 in
  tracker_ontologies_get_class_value_gvdb()

Status in tracker-miners package in Ubuntu:
  Expired

Bug description:
  Ubuntu17.10 New bug.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: tracker-miner-fs 2.0.2-1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct 23 11:54:07 2017
  EcryptfsInUse: Yes
  ExecutablePath: /usr/lib/tracker/tracker-miner-fs
  InstallationDate: Installed on 2016-11-04 (353 days ago)
  InstallationMedia: Ubuntu-GNOME 14.04 LTS "Trusty Tahr" - Beta amd64 
(20140326.1)
  ProcCmdline: /usr/lib/tracker/tracker-miner-fs
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Signal: 7
  SourcePackage: tracker-miners
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/tracker-2.0/libtracker-data.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/tracker-2.0/libtracker-data.so.0
   tracker_ontologies_get_class_value_gvdb () from 
/usr/lib/x86_64-linux-gnu/tracker-2.0/libtracker-data.so.0
   tracker_ontologies_get_class_string_gvdb () from 
/usr/lib/x86_64-linux-gnu/tracker-2.0/libtracker-data.so.0
   tracker_ontologies_get_class_by_uri () from 
/usr/lib/x86_64-linux-gnu/tracker-2.0/libtracker-data.so.0
  Title: tracker-miner-fs crashed with signal 7 in 
tracker_ontologies_get_class_value_gvdb()
  UpgradeStatus: Upgraded to artful on 2017-10-23 (0 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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


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

[Desktop-packages] [Bug 1780296] Re: [SRU] Update to bugfix 2.0.5 in Bionic

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

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

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

Title:
  [SRU] Update to bugfix 2.0.5 in Bionic

Status in tracker package in Ubuntu:
  Invalid
Status in tracker-miners package in Ubuntu:
  Invalid
Status in tracker source package in Bionic:
  Expired
Status in tracker-miners source package in Bionic:
  Expired

Bug description:
  Upstream released bugfix version 2.0.5. Please SRU to Bionic.

  https://gitlab.gnome.org/GNOME/tracker-miners/blob/2.0.5/NEWS

  NEW in 2.0.5 - 2018-06-25
  =

* tracker-extract: Made daemon able to shutdown on inactivity, lifetime
  will be managed by tracker-miner-fs
* tracker-stract: Fixes in generated SPARQL for geolocation data
* build: Multiple improvements and library detection fixes

  Translations: el, en_GB, hr, ro, ru
  --

  https://gitlab.gnome.org/GNOME/tracker/blob/2.0.5/NEWS

  NEW in 2.0.5 - 2018-07.22
  =

    * build: Make tarballs able to build with meson. Future releases will
  eventually phase out Autotools
    * build: Various meson build fixes
    * tests: Many fixes to functional tests
    * libtracker-miner: Fixed race conditions that may result in spurious
  "parent not indexed yet" warnings.
    * libtracker-direct: Majorly rewritten
    * tracker-store: Streamlined to use a libtracker-direct connection
  instead of reimplementing most of it.

  NEW in 2.0.4 - 2018-06-25
  =

    * libtracker-miner: Fix event emission order of the root folder when
  a recursive directory is found through monitor events.
    * libtracker-data: Perform VACUUM only past a database file size limit
    * libtracker-miner: Improvements to attribute-only update handling
    * build: Improvements in meson support
    * build: Fix build with --disable-fts
    * build: Drop automatic versioning of parser files, only showstopper
  for meson adoption
    * build: Fixes when building tracker-miners as subproject
    * build: Vala compiler warning fixes
    * build: Update sqlite dep to reflect practical reality

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


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

[Desktop-packages] [Bug 1780296] Re: [SRU] Update to bugfix 2.0.5 in Bionic

[Expired for tracker-miners (Ubuntu Bionic) because there has been no
activity for 60 days.]

** Changed in: tracker-miners (Ubuntu Bionic)
   Status: Incomplete => Expired

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

Title:
  [SRU] Update to bugfix 2.0.5 in Bionic

Status in tracker package in Ubuntu:
  Invalid
Status in tracker-miners package in Ubuntu:
  Invalid
Status in tracker source package in Bionic:
  Expired
Status in tracker-miners source package in Bionic:
  Expired

Bug description:
  Upstream released bugfix version 2.0.5. Please SRU to Bionic.

  https://gitlab.gnome.org/GNOME/tracker-miners/blob/2.0.5/NEWS

  NEW in 2.0.5 - 2018-06-25
  =

* tracker-extract: Made daemon able to shutdown on inactivity, lifetime
  will be managed by tracker-miner-fs
* tracker-stract: Fixes in generated SPARQL for geolocation data
* build: Multiple improvements and library detection fixes

  Translations: el, en_GB, hr, ro, ru
  --

  https://gitlab.gnome.org/GNOME/tracker/blob/2.0.5/NEWS

  NEW in 2.0.5 - 2018-07.22
  =

    * build: Make tarballs able to build with meson. Future releases will
  eventually phase out Autotools
    * build: Various meson build fixes
    * tests: Many fixes to functional tests
    * libtracker-miner: Fixed race conditions that may result in spurious
  "parent not indexed yet" warnings.
    * libtracker-direct: Majorly rewritten
    * tracker-store: Streamlined to use a libtracker-direct connection
  instead of reimplementing most of it.

  NEW in 2.0.4 - 2018-06-25
  =

    * libtracker-miner: Fix event emission order of the root folder when
  a recursive directory is found through monitor events.
    * libtracker-data: Perform VACUUM only past a database file size limit
    * libtracker-miner: Improvements to attribute-only update handling
    * build: Improvements in meson support
    * build: Fix build with --disable-fts
    * build: Drop automatic versioning of parser files, only showstopper
  for meson adoption
    * build: Fixes when building tracker-miners as subproject
    * build: Vala compiler warning fixes
    * build: Update sqlite dep to reflect practical reality

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


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

[Desktop-packages] [Bug 1967030] Re: [NUC11PAHi7, Realtek ALC256, Mic, Internal] Behringer 1202USB mixer's default usb audio driver clicks

2022-03-29 Thread Ubuntu Foundations Team Bug Bot

** Package changed: ubuntu => alsa-driver (Ubuntu)

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

Title:
  [NUC11PAHi7, Realtek ALC256, Mic, Internal] Behringer 1202USB mixer's
  default usb audio driver clicks

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  maybe pulseaudio, maybe alsa, i don't know.

  I have a stock kubuntu 21.10 (except for 2 files where i used a "too
  old" fix that didn't work)

  Any audio going to my Behringer 1202USB mixer has clicks about 2 per second. 
  That mixer is crackly on startup and shutdown but is new.
  Could be something to do with powersaving?

  This is a fresh install of kubuntu on my ibm nuc11i7.
  I've tried Fedora kde and no repeated clicking.
  Windows doesn't click.
  But Fedora kde is junk - can't even connect to github :(

  Other devices going thru the mixer don't click.  Just the usb audio.
  Other audio devices on kubuntu like hdmi or bluetooth audio work fine.

  This is maddening :)  click click click click...

  others have the issue too.  See...
  
https://www.reddit.com/r/linuxaudio/comments/tko0i6/sudden_issue_with_audio_interface_clicking_at/i2ntx7s/?context=3

  please help me :)

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu7
  ProcVersionSignature: Ubuntu 5.13.0-39.44-generic 5.13.19
  Uname: Linux 5.13.0-39-generic x86_64
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  sh  988 F pulseaudio
   /dev/snd/controlC2:  sh  988 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: KDE
  Date: Tue Mar 29 18:54:40 2022
  InstallationDate: Installed on 2022-03-27 (2 days ago)
  InstallationMedia: Kubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Mic, Internal
  Symptom_PulseAudioLog:
   
  Symptom_Type: Volume slider, or mixer problems
  Title: [NUC11PAHi7, Realtek ALC256, Mic, Internal] volume slider problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/13/2020
  dmi.bios.release: 0.35
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: PATGL357.0035.2020.1113.1353
  dmi.board.name: NUC11PABi7
  dmi.board.vendor: Intel Corporation
  dmi.board.version: K90104-302
  dmi.chassis.type: 35
  dmi.chassis.vendor: Intel Corporation
  dmi.chassis.version: 2.0
  dmi.ec.firmware.release: 3.1
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrPATGL357.0035.2020.1113.1353:bd11/13/2020:br0.35:efr3.1:svnIntel(R)ClientSystems:pnNUC11PAHi7:pvrM15513-302:rvnIntelCorporation:rnNUC11PABi7:rvrK90104-302:cvnIntelCorporation:ct35:cvr2.0:skuRNUC11PAHi7000:
  dmi.product.family: PA
  dmi.product.name: NUC11PAHi7
  dmi.product.sku: RNUC11PAHi7000
  dmi.product.version: M15513-302
  dmi.sys.vendor: Intel(R) Client Systems
  modified.conffile..etc.default.apport:
   # set this to 0 to disable apport, or to 1 to enable it
   # you can temporarily override this with
   # sudo service apport start force_start=1
   enabled=0
  mtime.conffile..etc.default.apport: 2022-03-27T14:12:12.368562
  mtime.conffile..etc.modprobe.d.alsa-base.conf: 2022-03-27T16:41:56.751936

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


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

[Desktop-packages] [Bug 1967030] [NEW] [NUC11PAHi7, Realtek ALC256, Mic, Internal] Behringer 1202USB mixer's default usb audio driver clicks

You have been subscribed to a public bug:

maybe pulseaudio, maybe alsa, i don't know.

I have a stock kubuntu 21.10 (except for 2 files where i used a "too
old" fix that didn't work)

Any audio going to my Behringer 1202USB mixer has clicks about 2 per second. 
That mixer is crackly on startup and shutdown but is new.
Could be something to do with powersaving?

This is a fresh install of kubuntu on my ibm nuc11i7.
I've tried Fedora kde and no repeated clicking.
Windows doesn't click.
But Fedora kde is junk - can't even connect to github :(

Other devices going thru the mixer don't click.  Just the usb audio.
Other audio devices on kubuntu like hdmi or bluetooth audio work fine.

This is maddening :)  click click click click...

others have the issue too.  See...
https://www.reddit.com/r/linuxaudio/comments/tko0i6/sudden_issue_with_audio_interface_clicking_at/i2ntx7s/?context=3

please help me :)

ProblemType: Bug
DistroRelease: Ubuntu 21.10
Package: alsa-base 1.0.25+dfsg-0ubuntu7
ProcVersionSignature: Ubuntu 5.13.0-39.44-generic 5.13.19
Uname: Linux 5.13.0-39-generic x86_64
ApportVersion: 2.20.11-0ubuntu71
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  sh  988 F pulseaudio
 /dev/snd/controlC2:  sh  988 F pulseaudio
CasperMD5CheckResult: pass
CurrentDesktop: KDE
Date: Tue Mar 29 18:54:40 2022
InstallationDate: Installed on 2022-03-27 (2 days ago)
InstallationMedia: Kubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_Card: Built-in Audio - HDA Intel PCH
Symptom_Jack: Mic, Internal
Symptom_PulseAudioLog:
 
Symptom_Type: Volume slider, or mixer problems
Title: [NUC11PAHi7, Realtek ALC256, Mic, Internal] volume slider problem
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/13/2020
dmi.bios.release: 0.35
dmi.bios.vendor: Intel Corp.
dmi.bios.version: PATGL357.0035.2020.1113.1353
dmi.board.name: NUC11PABi7
dmi.board.vendor: Intel Corporation
dmi.board.version: K90104-302
dmi.chassis.type: 35
dmi.chassis.vendor: Intel Corporation
dmi.chassis.version: 2.0
dmi.ec.firmware.release: 3.1
dmi.modalias: 
dmi:bvnIntelCorp.:bvrPATGL357.0035.2020.1113.1353:bd11/13/2020:br0.35:efr3.1:svnIntel(R)ClientSystems:pnNUC11PAHi7:pvrM15513-302:rvnIntelCorporation:rnNUC11PABi7:rvrK90104-302:cvnIntelCorporation:ct35:cvr2.0:skuRNUC11PAHi7000:
dmi.product.family: PA
dmi.product.name: NUC11PAHi7
dmi.product.sku: RNUC11PAHi7000
dmi.product.version: M15513-302
dmi.sys.vendor: Intel(R) Client Systems
modified.conffile..etc.default.apport:
 # set this to 0 to disable apport, or to 1 to enable it
 # you can temporarily override this with
 # sudo service apport start force_start=1
 enabled=0
mtime.conffile..etc.default.apport: 2022-03-27T14:12:12.368562
mtime.conffile..etc.modprobe.d.alsa-base.conf: 2022-03-27T16:41:56.751936

** Affects: alsa-driver (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug impish
-- 
[NUC11PAHi7, Realtek ALC256, Mic, Internal] Behringer 1202USB mixer's default 
usb audio driver clicks
https://bugs.launchpad.net/bugs/1967030
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to alsa-driver in Ubuntu.

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

[Desktop-packages] [Bug 1967037] [NEW] gnome-calculator crash during session login (misclassified?)

2022-03-29 Thread Jerry Quinn

Public bug reported:

Hi maintainers,

It is likely this report is misclassified, but I haven't been able to
trace it back to the real source.

When I log into a gnome session, I see the following warning in the
system log:

Mar 29 21:54:01 thinkpad3 dbus-daemon[1476]: [session uid=1000 pid=1476] 
Activating service name='org.gnome.ControlCenter.SearchProvider' requeste>
Mar 29 21:54:01 thinkpad3 dbus-daemon[1476]: [session uid=1000 pid=1476] 
Activating service name='org.gnome.Nautilus' requested by ':1.37' (uid=10>
Mar 29 21:54:01 thinkpad3 dbus-daemon[1476]: [session uid=1000 pid=1476] 
Activating service name='org.gnome.Calculator.SearchProvider' requested b>
Mar 29 21:54:01 thinkpad3 dbus-daemon[1476]: [session uid=1000 pid=1476] 
Activating service name='org.gnome.Calendar' requested by ':1.37' (uid=10>
Mar 29 21:54:01 thinkpad3 dbus-daemon[1476]: [session uid=1000 pid=1476] 
Activating service name='org.gnome.Characters.BackgroundService' requeste>
Mar 29 21:54:01 thinkpad3 dbus-daemon[1476]: [session uid=1000 pid=1476] 
Activating service name='org.gnome.seahorse.Application' requested by ':1>
Mar 29 21:54:01 thinkpad3 dbus-daemon[1476]: [session uid=1000 pid=1476] 
Activating via systemd: service name='org.gnome.Terminal' unit='gnome-ter>
Mar 29 21:54:01 thinkpad3 systemd[1465]: Created slice apps.slice.
Mar 29 21:54:01 thinkpad3 systemd[1465]: Created slice 
apps-org.gnome.Terminal.slice.
Mar 29 21:54:01 thinkpad3 systemd[1465]: Starting GNOME Terminal Server...
Mar 29 21:54:01 thinkpad3 dbus-daemon[1476]: [session uid=1000 pid=1476] 
Successfully activated service 'org.gnome.ControlCenter.SearchProvider'
Mar 29 21:54:01 thinkpad3 dbus-daemon[1476]: [session uid=1000 pid=1476] 
Successfully activated service 'org.gnome.seahorse.Application'
Mar 29 21:54:01 thinkpad3 dbus-daemon[776]: [system] Activating via systemd: 
service name='org.freedesktop.timedate1' unit='dbus-org.freedesktop.t>
Mar 29 21:54:01 thinkpad3 systemd[1]: Starting Time & Date Service...
Mar 29 21:54:01 thinkpad3 dbus-daemon[1476]: [session uid=1000 pid=1476] 
Successfully activated service 'org.gnome.Characters.BackgroundService'
Mar 29 21:54:01 thinkpad3 dbus-daemon[1476]: [session uid=1000 pid=1476] 
Successfully activated service 'org.gnome.Terminal'
Mar 29 21:54:01 thinkpad3 systemd[1465]: Started GNOME Terminal Server.
Mar 29 21:54:01 thinkpad3 dbus-daemon[776]: [system] Successfully activated 
service 'org.freedesktop.timedate1'
Mar 29 21:54:01 thinkpad3 systemd[1]: Started Time & Date Service.
Mar 29 21:54:01 thinkpad3 dbus-daemon[1476]: [session uid=1000 pid=1476] 
Successfully activated service 'org.gnome.Calendar'
Mar 29 21:54:01 thinkpad3 dbus-daemon[1476]: [session uid=1000 pid=1476] 
Successfully activated service 'org.gnome.Calculator.SearchProvider'
Mar 29 21:54:01 thinkpad3 gnome-calculato[2141]: search-provider.vala:140: 
Failed to spawn Calculator: Child process killed by signal 9


I'm having trouble tracing what is going on here, other than there
appears to be a segfault related to gnome-calculator.

The following appears relevant:
/usr/share/gnome-shell/search-providers/org.gnome.Calculator-search-provider.ini


This may be related to 
https://bugs.launchpad.net/ubuntu/+source/gnome-calculator/+bug/1795399

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gnome-calculator 1:3.36.0-1ubuntu1
ProcVersionSignature: Ubuntu 5.4.0-105.119-generic 5.4.174
Uname: Linux 5.4.0-105-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.21
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Tue Mar 29 21:57:31 2022
InstallationDate: Installed on 2018-12-01 (1214 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: gnome-calculator
UpgradeStatus: Upgraded to focal on 2021-12-14 (105 days ago)

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


** Tags: amd64 apport-bug focal

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

Title:
  gnome-calculator  crash during session login (misclassified?)

Status in gnome-calculator package in Ubuntu:
  New

Bug description:
  Hi maintainers,

  It is likely this report is misclassified, but I haven't been able to
  trace it back to the real source.

  When I log into a gnome session, I see the following warning in the
  system log:

  Mar 29 21:54:01 thinkpad3 dbus-daemon[1476]: [session uid=1000 pid=1476] 
Activating service name='org.gnome.ControlCenter.SearchProvider' requeste>
  Mar 29 21:54:01 thinkpad3 dbus-daemon[1476]: [session uid=1000 pid=1476] 
Activating service name='org.gnome.Nautilus' requested by ':1.37' (uid=10>
  Mar 29 21:54:01 thinkpad3 dbus-daemon[1476]: [session uid=1000 pid=1476] 
Activating service name='org

[Desktop-packages] [Bug 1966808] Re: [amdgpu][radeon] gnome-shell Wayland sessions fail to start (Failed to lock front buffer on /dev/dri/card1: drmModeAddFB2WithModifiers failed: Invalid argument)

The middle line "libmutter-10-0" is the important one for gnome-shell,
but all three of the packages shown in comment #12 need to keep the same
version number to function correctly.

The package named "mutter" and the "mutter" binary are confusingly not
relevant here. It's not used in Ubuntu and not installed by default.

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

Title:
  [amdgpu][radeon] gnome-shell Wayland sessions fail to start (Failed to
  lock front buffer on /dev/dri/card1: drmModeAddFB2WithModifiers
  failed: Invalid argument)

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

Bug description:
  Wayland started crashing for me on upgrade to Jammy, which I'm aware
  is currently in alpha.

  gdm was crashing, and changing to lightdm addressed this issue.  If I
  select 'Ubuntu on Xorg' - I can login without problems.

  If I select Wayland instead, I just get a black screen, and I have to
  kill gnome-session from a virtual console.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 42~beta-1ubuntu3
  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: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Mar 28 15:23:51 2022
  DisplayManager: lightdm
  InstallationDate: Installed on 2022-03-19 (9 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220318)
  RelatedPackageVersions: mutter-common 42~beta-1ubuntu2
  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/1966808/+subscriptions


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

Thanks for the bug report. Next time it happens, please press the power
button as usual and after the system has restarted run:

  lspci -k > lspci.txt
  journalctl -b-1 > prevboot.txt

and attach the resulting text files here.

Please also check for crashes by:
https://wiki.ubuntu.com/Bugs/Responses#Missing_a_crash_report_or_having_a_.crash_attachment

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

-- 
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 1966334] Re: GLVND: Set current thread state to NULL in teardown

2022-03-29 Thread Aidan Foster

The bug was observed running the Vulkan CTS on an Nvidia Jetson AGX Xavier 
Developer Kit and on a Jetson AGX Orin Developer Kit. Running the testcase 
dEQP-VK.api.object_management.alloc_callback_fail.instance without an X display 
should cause the double free to occur.
I confirmed that this is a GLVND issue, as when I built libglvnd with small fix 
that was merged and used it instead of the provided libs, the issue went away.

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

Title:
  GLVND: Set current thread state to NULL in teardown

Status in libglvnd package in Ubuntu:
  Confirmed

Bug description:
  A new fix has been merged into the libglvnd repo at
  https://gitlab.freedesktop.org/glvnd/libglvnd

  This change fixes an issue where if eglReleaseThread gets externally called 
after the EGL destructor, a  double free occurs due to the threadState that 
eglReleaseThread checks is not null being not null despite being freed by the 
destuctor.
  The change makes the threadState null in the destructor to fix this.

  Can this make it into the libs in 20.04 LTS?

  Source package where the issue is encountered:
  https://launchpad.net/ubuntu/+source/libglvnd/1.3.2-1~ubuntu0.20.04.2

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


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

[Desktop-packages] [Bug 1966808] Re: [amdgpu][radeon] gnome-shell Wayland sessions fail to start (Failed to lock front buffer on /dev/dri/card1: drmModeAddFB2WithModifiers failed: Invalid argument)

Noted, thank you.  I'll check after 42.0-1ubuntu1 is released.  I am a
bit unsure of this though, this is what I currently see:

$# dpkg -l|grep -i mutter
ii  gir1.2-mutter-10:amd6442~beta-1ubuntu2  
  amd64GObject introspection data for Mutter
ii  libmutter-10-0:amd64  42~beta-1ubuntu2  
  amd64window manager library from the Mutter window manager
ii  mutter-common 42~beta-1ubuntu2  
  all  shared files for the Mutter window manager

Out of these, should I be looking at the mutter-common (or libmutter?)
version to change to 42.0-1ubuntu1?

Thanks

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

Title:
  [amdgpu][radeon] gnome-shell Wayland sessions fail to start (Failed to
  lock front buffer on /dev/dri/card1: drmModeAddFB2WithModifiers
  failed: Invalid argument)

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

Bug description:
  Wayland started crashing for me on upgrade to Jammy, which I'm aware
  is currently in alpha.

  gdm was crashing, and changing to lightdm addressed this issue.  If I
  select 'Ubuntu on Xorg' - I can login without problems.

  If I select Wayland instead, I just get a black screen, and I have to
  kill gnome-session from a virtual console.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 42~beta-1ubuntu3
  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: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Mar 28 15:23:51 2022
  DisplayManager: lightdm
  InstallationDate: Installed on 2022-03-19 (9 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220318)
  RelatedPackageVersions: mutter-common 42~beta-1ubuntu2
  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/1966808/+subscriptions


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

[Desktop-packages] [Bug 1966808] Re: [amdgpu][radeon] gnome-shell Wayland sessions fail to start (Failed to lock front buffer on /dev/dri/card1: drmModeAddFB2WithModifiers failed: Invalid argument)

I also *just* installed mutter, as it seems there was a package that
provides a mutter binary, that seems to have a similar version
(42~beta-1ubuntu):

$ mutter --version
mutter 42.beta

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

Title:
  [amdgpu][radeon] gnome-shell Wayland sessions fail to start (Failed to
  lock front buffer on /dev/dri/card1: drmModeAddFB2WithModifiers
  failed: Invalid argument)

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

Bug description:
  Wayland started crashing for me on upgrade to Jammy, which I'm aware
  is currently in alpha.

  gdm was crashing, and changing to lightdm addressed this issue.  If I
  select 'Ubuntu on Xorg' - I can login without problems.

  If I select Wayland instead, I just get a black screen, and I have to
  kill gnome-session from a virtual console.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 42~beta-1ubuntu3
  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: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Mar 28 15:23:51 2022
  DisplayManager: lightdm
  InstallationDate: Installed on 2022-03-19 (9 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220318)
  RelatedPackageVersions: mutter-common 42~beta-1ubuntu2
  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/1966808/+subscriptions


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

[Desktop-packages] [Bug 1967011] Re: Unable to Share Screen via PipeWire in OBS Studio

That fix is in mutter version "42.rc", which is already in the proposed
pocket as "42.0-1ubuntu1"

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

** Also affects: mutter via
   https://gitlab.gnome.org/GNOME/mutter/-/issues/2155
   Importance: Unknown
   Status: Unknown

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

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

** Tags added: amdgpu fixed-in-42 fixed-upstream jammy

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

Title:
  Unable to Share Screen via PipeWire in OBS Studio

Status in Mutter:
  Unknown
Status in mutter package in Ubuntu:
  Fix Committed

Bug description:
  Hello,

  please pull in this change:
  https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2322

  This is the relevant bug in the mutter repo:
  https://gitlab.gnome.org/GNOME/mutter/-/issues/2155

  as it blocks OBS / Telegram from receiving screen sharing on AMD GPUs.

  Mär 29 23:32:24 egal-12 gnome-shell[3219]: setup_framebuffers: assertion 
'width > 0' failed
  Mär 29 23:32:26 egal-12 com.obsproject.Studio.desktop[55756]: info: 
[pipewire] desktop selected, setting up screencast
  Mär 29 23:32:26 egal-12 com.obsproject.Studio.desktop[55756]: info: 
[pipewire] server version: 0.3.48
  Mär 29 23:32:26 egal-12 com.obsproject.Studio.desktop[55756]: info: 
[pipewire] library version: 0.3.48
  Mär 29 23:32:26 egal-12 com.obsproject.Studio.desktop[55756]: info: 
[pipewire] header version: 0.3.48
  Mär 29 23:32:26 egal-12 com.obsproject.Studio.desktop[55756]: info: 
[pipewire] created stream 0x564c4e1f7480
  Mär 29 23:32:26 egal-12 com.obsproject.Studio.desktop[55756]: info: 
[pipewire] playing stream…
  Mär 29 23:32:26 egal-12 gnome-shell[3219]: No supported PipeWire stream 
buffer data type could be negotiated
  Mär 29 23:32:26 egal-12 gnome-shell[3219]: No supported PipeWire stream 
buffer data type could be negotiated
  Mär 29 23:32:26 egal-12 gnome-shell[3219]: No supported PipeWire stream 
buffer data type could be negotiated
  Mär 29 23:32:26 egal-12 gnome-shell[3219]: No supported PipeWire stream 
buffer data type could be negotiated
  Mär 29 23:32:26 egal-12 gnome-shell[3219]: No supported PipeWire stream 
buffer data type could be negotiated
  Mär 29 23:32:26 egal-12 gnome-shell[3219]: No supported PipeWire stream 
buffer data type could be negotiated
  Mär 29 23:32:26 egal-12 gnome-shell[3219]: No supported PipeWire stream 
buffer data type could be negotiated
  Mär 29 23:32:26 egal-12 gnome-shell[3219]: No supported PipeWire stream 
buffer data type could be negotiated
  Mär 29 23:32:26 egal-12 gnome-shell[3219]: No supported PipeWire stream 
buffer data type could be negotiated
  Mär 29 23:32:26 egal-12 gnome-shell[3219]: No supported PipeWire stream 
buffer data type could be negotiated
  Mär 29 23:32:26 egal-12 gnome-shell[3219]: No supported PipeWire stream 
buffer data type could be negotiated
  Mär 29 23:32:26 egal-12 gnome-shell[3219]: No supported PipeWire stream 
buffer data type could be negotiated
  Mär 29 23:32:26 egal-12 gnome-shell[3219]: No supported PipeWire stream 
buffer data type could be negotiated
  Mär 29 23:32:26 egal-12 gnome-shell[3219]: No supported PipeWire stream 
buffer data type could be negotiated
  Mär 29 23:32:26 egal-12 gnome-shell[3219]: No supported PipeWire stream 
buffer data type could be negotiated
  Mär 29 23:32:26 egal-12 gnome-shell[3219]: No supported PipeWire stream 
buffer data type could be negotiated
  Mär 29 23:32:26 egal-12 gnome-shell[3219]: pipewire remote error: id:0 
connection error
  Mär 29 23:32:26 egal-12 pipewire[2993]: spa.v4l2: wanted XR24 2560x1440, got 
YUYV 2304x1536
  Mär 29 23:32:26 egal-12 pipewire[2993]: pw.link: tried to set output format:
  Mär 29 23:32:26 egal-12 pipewire[2993]: default: Object: size 320, type 
Spa:Pod:Object:Param:Format (262147), id Spa:Enum:ParamId:Format (4)
  Mär 29 23:32:26 egal-12 pipewire[2993]: default:   Prop: key 
Spa:Pod:Object:Param:Format:mediaType (1), flags 
  Mär 29 23:32:26 egal-12 pipewire[2993]: default: Choice: type 
Spa:Enum:Choice:None, flags  20 4

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


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

[Desktop-packages] [Bug 1966808] Re: [amdgpu][radeon] gnome-shell Wayland sessions fail to start (Failed to lock front buffer on /dev/dri/card1: drmModeAddFB2WithModifiers failed: Invalid argument)

You don't need to, but we would like to know if that fix removes the
need for the workaround MUTTER_DEBUG_USE_KMS_MODIFIERS=0

If you still need MUTTER_DEBUG_USE_KMS_MODIFIERS=0 after mutter
42.0-1ubuntu1 is released then we should open a new bug in
https://gitlab.gnome.org/GNOME/mutter/-/issues

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

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

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

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

Title:
  [amdgpu][radeon] gnome-shell Wayland sessions fail to start (Failed to
  lock front buffer on /dev/dri/card1: drmModeAddFB2WithModifiers
  failed: Invalid argument)

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

Bug description:
  Wayland started crashing for me on upgrade to Jammy, which I'm aware
  is currently in alpha.

  gdm was crashing, and changing to lightdm addressed this issue.  If I
  select 'Ubuntu on Xorg' - I can login without problems.

  If I select Wayland instead, I just get a black screen, and I have to
  kill gnome-session from a virtual console.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 42~beta-1ubuntu3
  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: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Mar 28 15:23:51 2022
  DisplayManager: lightdm
  InstallationDate: Installed on 2022-03-19 (9 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220318)
  RelatedPackageVersions: mutter-common 42~beta-1ubuntu2
  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/1966808/+subscriptions


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

[Desktop-packages] [Bug 1966786] Re: login screen shown twice

** Changed in: gdm3 (Ubuntu)
   Status: Incomplete => Confirmed

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

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

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

Title:
  login screen shown twice

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

Bug description:
  The login screen is shown twice and I have to supply the password
  twice. The system works normally afterwards.  When I select auto-login
  in the settings still one login screen is shown.

  gdm.service - GNOME Display Manager
   Loaded: loaded (/lib/systemd/system/gdm.service; static)
   Active: active (running) since Mon 2022-03-28 11:47:32 AST; 6min ago
  Process: 1885 ExecStartPre=/usr/share/gdm/generate-config (code=exited, 
status=0/SUCCESS)
 Main PID: 1915 (gdm3)
Tasks: 3 (limit: 2291)
   Memory: 5.0M
  CPU: 125ms
   CGroup: /system.slice/gdm.service
   └─1915 /usr/sbin/gdm3

  mar 28 11:47:32 vm-ubuntu-2204 systemd[1]: Starting GNOME Display Manager...
  mar 28 11:47:32 vm-ubuntu-2204 systemd[1]: Started GNOME Display Manager.
  mar 28 11:47:32 vm-ubuntu-2204 gdm-launch-environment][1921]: 
pam_unix(gdm-launch-environment:session): session opened for user gdm(uid=125) 
by (uid=0)
  mar 28 11:47:40 vm-ubuntu-2204 gdm-password][2290]: gkr-pam: unable to locate 
daemon control file
  mar 28 11:47:40 vm-ubuntu-2204 gdm-password][2290]: gkr-pam: stashed password 
to try later in open session
  mar 28 11:47:40 vm-ubuntu-2204 gdm-password][2290]: 
pam_unix(gdm-password:session): session opened for user bertadmin(uid=1000) by 
(uid=0)
  mar 28 11:47:40 vm-ubuntu-2204 gdm-password][2290]: gkr-pam: 
gnome-keyring-daemon started properly and unlocked keyring
  mar 28 11:47:57 vm-ubuntu-2204 gdm3[1915]: Gdm: Child process -1937 was 
already dead.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gdm3 42.0-1ubuntu1
  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: ubuntu:GNOME
  Date: Mon Mar 28 11:48:17 2022
  InstallationDate: Installed on 2020-01-25 (793 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200124)
  SourcePackage: gdm3
  UpgradeStatus: Upgraded to jammy on 2022-03-23 (4 days ago)

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


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

[Desktop-packages] [Bug 1967025] Re: Double login screen

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

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


** This bug has been marked a duplicate of bug 1966786
   login screen shown twice

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

Title:
  Double login screen

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Installed 22.04 daily (march 29) in VirtualBox.
  Selected "auto login" with user creation.
  After installation and update was greeted with a login screen.
  Disabling the "auto login" for the user in Gnome settings gave me two 
different successive login screens.
  Re-enabling the "auto login" gave me one login screen, where non would be 
expected.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 42~beta-1ubuntu3
  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: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar 30 02:22:26 2022
  DisplayManager: gdm3
  InstallationDate: Installed on 2022-03-29 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=nl_NL.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 42~beta-1ubuntu2
  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/1967025/+subscriptions


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

[Desktop-packages] [Bug 1497593] Re: [nouveau] Programs crash with SIGABRT in nouveau_pushbuf_data: Assertion `kref' failed.

** Tags removed: hirsute
** Tags added: jammy

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

Title:
  [nouveau] Programs crash with SIGABRT in nouveau_pushbuf_data:
  Assertion `kref' failed.

Status in Mesa:
  Unknown
Status in libdrm package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  Confirmed

Bug description:
  Programs crash with SIGABRT in nouveau_pushbuf_data: Assertion `kref'
  failed. Because nouveau is not thread safe(?)

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


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

[Desktop-packages] [Bug 1553328] Re: Mir/Unity8/USC crashes/freezes on nouveau (nv50) in pushbuf_kref() especially with multiple monitors, webbrowser-app or system settings

This should probably be tracked in bug 1497593 now.

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

Title:
  Mir/Unity8/USC crashes/freezes on nouveau (nv50) in pushbuf_kref()
  especially with multiple monitors, webbrowser-app or system settings

Status in Canonical System Image:
  Triaged
Status in Mesa:
  Unknown
Status in Mir:
  Triaged
Status in Nouveau Xorg driver:
  Unknown
Status in Unity System Compositor:
  Triaged
Status in libdrm package in Ubuntu:
  Triaged
Status in mesa package in Ubuntu:
  Triaged
Status in mir package in Ubuntu:
  Triaged
Status in qtmir package in Ubuntu:
  In Progress
Status in qtubuntu package in Ubuntu:
  In Progress

Bug description:
  Unit8 froze up while I was trying to open system settings.

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: unity8 8.11+16.04.20160216.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-9.24-generic 4.4.3
  Uname: Linux 4.4.0-9-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  Date: Fri Mar  4 19:12:54 2016
  ExecutablePath: /usr/bin/unity8
  InstallationDate: Installed on 2015-05-10 (299 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  ProcCmdline: unity8
  SegvAnalysis:
   Segfault happened at: 0x7f58d568706c:mov0x8(%rsi),%edx
   PC (0x7f58d568706c) ok
   source "0x8(%rsi)" (0x0008) not located in a known VMA region (needed 
readable region)!
   destination "%edx" ok
   Stack memory exhausted (SP below stack segment)
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: unity8
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libdrm_nouveau.so.2
   ?? () from /usr/lib/x86_64-linux-gnu/libdrm_nouveau.so.2
   ?? () from /usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1
  Title: unity8 crashed with SIGSEGV
  UpgradeStatus: Upgraded to xenial on 2015-11-07 (118 days ago)
  UserGroups: adm autopilot cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1553328/+subscriptions


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

[Desktop-packages] [Bug 1966552] Re: IBus input method candidate box cannot follow the cursor

** Bug watch added: github.com/ibus/ibus/issues #2391
   https://github.com/ibus/ibus/issues/2391

** Also affects: ibus via
   https://github.com/ibus/ibus/issues/2391
   Importance: Unknown
   Status: Unknown

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

Title:
  IBus input method candidate box cannot follow the cursor

Status in ibus:
  Unknown
Status in ibus package in Ubuntu:
  New
Status in ibus-libpinyin package in Ubuntu:
  New

Bug description:
  I have tested it in some software, such as Microsoft Edge, Onlyoffice,
  and it does not follow the cursor position correctly, but always at
  the bottom left of the application window. However, in some
  applications such as Gedit, it works fine.

  Pictures are here：https://i.bmp.ovh/imgs/2022/03/34ebb5158ceeedfc.png

  OS: Ubuntu Jammy Jellyfish
  Kernel: 5.15.0-23-generic
  on Wayland

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: ibus-libpinyin 1.12.1-2ubuntu2
  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: ubuntu:GNOME
  Date: Sat Mar 26 23:59:28 2022
  InstallationDate: Installed on 2022-02-09 (45 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  SourcePackage: ibus-libpinyin
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Desktop-packages] [Bug 1051952] Re: libgio's move-to-trash funciton freezes system when trashing files in kerberized, NFS mounted filesystems

2022-03-29 Thread Sean Davis

Expiring due to lack of confirmation.

** Changed in: glib2.0 (Ubuntu)
   Status: Incomplete => Invalid

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

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

Title:
  libgio's move-to-trash funciton freezes system when trashing files in
  kerberized, NFS mounted filesystems

Status in glib2.0 package in Ubuntu:
  Invalid
Status in nautilus package in Ubuntu:
  Invalid
Status in thunar package in Ubuntu:
  Invalid

Bug description:
  Description:Ubuntu 12.04.1 LTS
  Release:12.04

  nautilus:
Installed: 1:3.4.2-0ubuntu4
Candidate: 1:3.4.2-0ubuntu4
Version table:
   *** 1:3.4.2-0ubuntu4 0
  500 http://de.archive.ubuntu.com/ubuntu/ precise-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   1:3.4.1-0ubuntu1 0
  500 http://de.archive.ubuntu.com/ubuntu/ precise/main amd64 Packages

  thunar:
Installed: 1.2.3-3ubuntu2
Candidate: 1.2.3-3ubuntu2
Version table:
   *** 1.2.3-3ubuntu2 0
  500 http://de.archive.ubuntu.com/ubuntu/ precise/universe amd64 
Packages
  100 /var/lib/dpkg/status


  The setting is:

  - the user joeuser has a home directory which is mounted via NFS Version 4
  - the NFS4 mount uses Kerberos (-o sec=krb5) for authentication, which is the 
only non-default mount option
  - the user uses either Nautilus or Thunar as a graphical file manager
  - the user moves a small number of files to trash using either Thunar or 
Nautilus, after at most 20 times (independent on uptime or login time) the bug 
emerges: when the user moves file ~/foobar_21 to trash the operation takes a 
very long time (30 secs and longer)
  - during the wait we have observerd that nautious/thunar and other 
applications freeze or will not start
  -- top, as joeuser, will not start until the file ~/foobar_21 has been moved 
to trash
  -- cat ~/myfile.txt does not work until the file has been moved to trash
  -- the Thunar and Nautilus windows are not redrawn
  - ls does work and we can see that the original file ~/foobar_21 is deleted 
shortly before the end of the wait time

  The file managers Dolphin and Xfe work as expected taking well under a second 
to trash files.
  Other file managers have not been tested.

  
  FTR:
  dolphin:
Installed: 4:4.8.4-0ubuntu0.1
Candidate: 4:4.8.4-0ubuntu0.1
Version table:
   *** 4:4.8.4-0ubuntu0.1 0
  500 http://de.archive.ubuntu.com/ubuntu/ precise-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   4:4.8.2-0ubuntu2 0
  500 http://de.archive.ubuntu.com/ubuntu/ precise/main amd64 Packages

  xfe:
Installed: 1.32.4-3
Candidate: 1.32.4-3
Version table:
   *** 1.32.4-3 0
  500 http://de.archive.ubuntu.com/ubuntu/ precise/universe amd64 
Packages
  100 /var/lib/dpkg/status

  nfs-common:
Installed: 1:1.2.5-3ubuntu3
Candidate: 1:1.2.5-3ubuntu3
Version table:
   *** 1:1.2.5-3ubuntu3 0
  500 http://de.archive.ubuntu.com/ubuntu/ precise/main amd64 Packages
  100 /var/lib/dpkg/status

  krb5-user:
Installed: 1.10+dfsg~beta1-2ubuntu0.3
Candidate: 1.10+dfsg~beta1-2ubuntu0.3
Version table:
   *** 1.10+dfsg~beta1-2ubuntu0.3 0
  500 http://de.archive.ubuntu.com/ubuntu/ precise-updates/universe 
amd64 Packages
  500 http://security.ubuntu.com/ubuntu/ precise-security/universe 
amd64 Packages
  100 /var/lib/dpkg/status
   1.10+dfsg~beta1-2 0
  500 http://de.archive.ubuntu.com/ubuntu/ precise/universe amd64 
Packages

  Linux HOSTNAME 3.2.0-30-generic #48-Ubuntu SMP Fri Aug 24 16:52:48 UTC
  2012 x86_64 x86_64 x86_64 GNU/Linux

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


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

[Desktop-packages] [Bug 1967025] Re: Double login screen

2022-03-29 Thread Tim Blokdijk

After installation I also added the VB Guest Additions.
`sudo ./VBoxLinuxAdditions.run`
and for that to work I had to run
`sudo apt install build-essential dkms`

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

Title:
  Double login screen

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Installed 22.04 daily (march 29) in VirtualBox.
  Selected "auto login" with user creation.
  After installation and update was greeted with a login screen.
  Disabling the "auto login" for the user in Gnome settings gave me two 
different successive login screens.
  Re-enabling the "auto login" gave me one login screen, where non would be 
expected.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 42~beta-1ubuntu3
  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: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar 30 02:22:26 2022
  DisplayManager: gdm3
  InstallationDate: Installed on 2022-03-29 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=nl_NL.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 42~beta-1ubuntu2
  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/1967025/+subscriptions


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

[Desktop-packages] [Bug 1967025] [NEW] Double login screen

2022-03-29 Thread Tim Blokdijk

Public bug reported:

Installed 22.04 daily (march 29) in VirtualBox.
Selected "auto login" with user creation.
After installation and update was greeted with a login screen.
Disabling the "auto login" for the user in Gnome settings gave me two different 
successive login screens.
Re-enabling the "auto login" gave me one login screen, where non would be 
expected.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: gnome-shell 42~beta-1ubuntu3
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: pass
CurrentDesktop: ubuntu:GNOME
Date: Wed Mar 30 02:22:26 2022
DisplayManager: gdm3
InstallationDate: Installed on 2022-03-29 (0 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=nl_NL.UTF-8
 SHELL=/bin/bash
RelatedPackageVersions: mutter-common 42~beta-1ubuntu2
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug jammy 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/1967025

Title:
  Double login screen

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Installed 22.04 daily (march 29) in VirtualBox.
  Selected "auto login" with user creation.
  After installation and update was greeted with a login screen.
  Disabling the "auto login" for the user in Gnome settings gave me two 
different successive login screens.
  Re-enabling the "auto login" gave me one login screen, where non would be 
expected.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 42~beta-1ubuntu3
  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: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar 30 02:22:26 2022
  DisplayManager: gdm3
  InstallationDate: Installed on 2022-03-29 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=nl_NL.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 42~beta-1ubuntu2
  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/1967025/+subscriptions


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

[Desktop-packages] [Bug 1967011] Re: Unable to Share Screen via PipeWire in OBS Studio

2022-03-29 Thread Ubuntu Foundations Team Bug Bot

The attachment "change which fixed the issue taken from upstream" seems
to be a patch.  If it isn't, please remove the "patch" flag from the
attachment, remove the "patch" tag, and if you are a member of the
~ubuntu-reviewers, unsubscribe the team.

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

** Tags added: patch

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

Title:
  Unable to Share Screen via PipeWire in OBS Studio

Status in mutter package in Ubuntu:
  New

Bug description:
  Hello,

  please pull in this change:
  https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2322

  This is the relevant bug in the mutter repo:
  https://gitlab.gnome.org/GNOME/mutter/-/issues/2155

  as it blocks OBS / Telegram from receiving screen sharing on AMD GPUs.

  Mär 29 23:32:24 egal-12 gnome-shell[3219]: setup_framebuffers: assertion 
'width > 0' failed
  Mär 29 23:32:26 egal-12 com.obsproject.Studio.desktop[55756]: info: 
[pipewire] desktop selected, setting up screencast
  Mär 29 23:32:26 egal-12 com.obsproject.Studio.desktop[55756]: info: 
[pipewire] server version: 0.3.48
  Mär 29 23:32:26 egal-12 com.obsproject.Studio.desktop[55756]: info: 
[pipewire] library version: 0.3.48
  Mär 29 23:32:26 egal-12 com.obsproject.Studio.desktop[55756]: info: 
[pipewire] header version: 0.3.48
  Mär 29 23:32:26 egal-12 com.obsproject.Studio.desktop[55756]: info: 
[pipewire] created stream 0x564c4e1f7480
  Mär 29 23:32:26 egal-12 com.obsproject.Studio.desktop[55756]: info: 
[pipewire] playing stream…
  Mär 29 23:32:26 egal-12 gnome-shell[3219]: No supported PipeWire stream 
buffer data type could be negotiated
  Mär 29 23:32:26 egal-12 gnome-shell[3219]: No supported PipeWire stream 
buffer data type could be negotiated
  Mär 29 23:32:26 egal-12 gnome-shell[3219]: No supported PipeWire stream 
buffer data type could be negotiated
  Mär 29 23:32:26 egal-12 gnome-shell[3219]: No supported PipeWire stream 
buffer data type could be negotiated
  Mär 29 23:32:26 egal-12 gnome-shell[3219]: No supported PipeWire stream 
buffer data type could be negotiated
  Mär 29 23:32:26 egal-12 gnome-shell[3219]: No supported PipeWire stream 
buffer data type could be negotiated
  Mär 29 23:32:26 egal-12 gnome-shell[3219]: No supported PipeWire stream 
buffer data type could be negotiated
  Mär 29 23:32:26 egal-12 gnome-shell[3219]: No supported PipeWire stream 
buffer data type could be negotiated
  Mär 29 23:32:26 egal-12 gnome-shell[3219]: No supported PipeWire stream 
buffer data type could be negotiated
  Mär 29 23:32:26 egal-12 gnome-shell[3219]: No supported PipeWire stream 
buffer data type could be negotiated
  Mär 29 23:32:26 egal-12 gnome-shell[3219]: No supported PipeWire stream 
buffer data type could be negotiated
  Mär 29 23:32:26 egal-12 gnome-shell[3219]: No supported PipeWire stream 
buffer data type could be negotiated
  Mär 29 23:32:26 egal-12 gnome-shell[3219]: No supported PipeWire stream 
buffer data type could be negotiated
  Mär 29 23:32:26 egal-12 gnome-shell[3219]: No supported PipeWire stream 
buffer data type could be negotiated
  Mär 29 23:32:26 egal-12 gnome-shell[3219]: No supported PipeWire stream 
buffer data type could be negotiated
  Mär 29 23:32:26 egal-12 gnome-shell[3219]: No supported PipeWire stream 
buffer data type could be negotiated
  Mär 29 23:32:26 egal-12 gnome-shell[3219]: pipewire remote error: id:0 
connection error
  Mär 29 23:32:26 egal-12 pipewire[2993]: spa.v4l2: wanted XR24 2560x1440, got 
YUYV 2304x1536
  Mär 29 23:32:26 egal-12 pipewire[2993]: pw.link: tried to set output format:
  Mär 29 23:32:26 egal-12 pipewire[2993]: default: Object: size 320, type 
Spa:Pod:Object:Param:Format (262147), id Spa:Enum:ParamId:Format (4)
  Mär 29 23:32:26 egal-12 pipewire[2993]: default:   Prop: key 
Spa:Pod:Object:Param:Format:mediaType (1), flags 
  Mär 29 23:32:26 egal-12 pipewire[2993]: default: Choice: type 
Spa:Enum:Choice:None, flags  20 4

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


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

[Desktop-packages] [Bug 1967020] WebKitWebProcess crashed with SIGSEGV

2022-03-29 Thread Apport retracing service

StacktraceTop:
 WebKit::LayerTreeHost::LayerTreeHost () at 
./Source/WebKit/WebProcess/WebPage/CoordinatedGraphics/LayerTreeHost.cpp:77
 std::make_unique () at 
/usr/include/c++/11/bits/unique_ptr.h:962
 WTF::makeUnique () at 
./build-soup2/WTF/Headers/wtf/StdLibExtras.h:540
 WebKit::DrawingAreaCoordinatedGraphics::enterAcceleratedCompositingMode () at 
./Source/WebKit/WebProcess/WebPage/CoordinatedGraphics/DrawingAreaCoordinatedGraphics.cpp:641
 WebKit::WebPage::WebPage () at 
./Source/WebKit/WebProcess/WebPage/WebPage.cpp:792


** Tags removed: need-amd64-retrace

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

Title:
  WebKitWebProcess crashed with SIGSEGV

Status in webkit2gtk package in Ubuntu:
  New

Bug description:
  Evolution, when launched with Wayland, suddenly closes. When launched
  from the command line, it displays this:

  Gdk-Message: 16:42:11.320: Error flushing display: Protocol error

  If forced with --display=:0, it works, but an obvious crash in
  WebKitWebProcess occurs, hence I believe the issue lies within that.

  ProblemType: Crash
  DistroRelease: Ubuntu 22.04
  Package: libwebkit2gtk-4.0-37 2.35.90-1ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-22.22-lowlatency 5.15.19
  Uname: Linux 5.15.0-22-lowlatency x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Mar 29 16:45:19 2022
  ExecutablePath: /usr/lib/x86_64-linux-gnu/webkit2gtk-4.0/WebKitWebProcess
  InstallationDate: Installed on 2021-08-19 (222 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210818)
  ProcCmdline: /usr/lib/x86_64-linux-gnu/webkit2gtk-4.0/WebKitWebProcess 13 43
  ProcEnviron:
   SHELL=/bin/bash
   LANG=en_US.UTF-8
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
   PATH=(custom, user)
  SegvAnalysis:
   Segfault happened at: 0x7fd90adae773:mov(%rdi),%rax
   PC (0x7fd90adae773) ok
   source "(%rdi)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%rax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: webkit2gtk
  StacktraceTop:
   () at /lib/x86_64-linux-gnu/libwebkit2gtk-4.0.so.37
   () at /lib/x86_64-linux-gnu/libwebkit2gtk-4.0.so.37
   () at /lib/x86_64-linux-gnu/libwebkit2gtk-4.0.so.37
   () at /lib/x86_64-linux-gnu/libwebkit2gtk-4.0.so.37
   () at /lib/x86_64-linux-gnu/libwebkit2gtk-4.0.so.37
  Title: WebKitWebProcess crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dip lpadmin lxd plugdev sambashare sudo
  separator:

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


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

[Desktop-packages] [Bug 1967020] [NEW] WebKitWebProcess crashed with SIGSEGV

2022-03-29 Thread Erich Eickmeyer 

Public bug reported:

Evolution, when launched with Wayland, suddenly closes. When launched
from the command line, it displays this:

Gdk-Message: 16:42:11.320: Error flushing display: Protocol error

If forced with --display=:0, it works, but an obvious crash in
WebKitWebProcess occurs, hence I believe the issue lies within that.

ProblemType: Crash
DistroRelease: Ubuntu 22.04
Package: libwebkit2gtk-4.0-37 2.35.90-1ubuntu1
ProcVersionSignature: Ubuntu 5.15.0-22.22-lowlatency 5.15.19
Uname: Linux 5.15.0-22-lowlatency x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu79
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Tue Mar 29 16:45:19 2022
ExecutablePath: /usr/lib/x86_64-linux-gnu/webkit2gtk-4.0/WebKitWebProcess
InstallationDate: Installed on 2021-08-19 (222 days ago)
InstallationMedia: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210818)
ProcCmdline: /usr/lib/x86_64-linux-gnu/webkit2gtk-4.0/WebKitWebProcess 13 43
ProcEnviron:
 SHELL=/bin/bash
 LANG=en_US.UTF-8
 TERM=xterm-256color
 XDG_RUNTIME_DIR=
 PATH=(custom, user)
SegvAnalysis:
 Segfault happened at: 0x7fd90adae773:  mov(%rdi),%rax
 PC (0x7fd90adae773) ok
 source "(%rdi)" (0x) not located in a known VMA region (needed 
readable region)!
 destination "%rax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: webkit2gtk
StacktraceTop:
 () at /lib/x86_64-linux-gnu/libwebkit2gtk-4.0.so.37
 () at /lib/x86_64-linux-gnu/libwebkit2gtk-4.0.so.37
 () at /lib/x86_64-linux-gnu/libwebkit2gtk-4.0.so.37
 () at /lib/x86_64-linux-gnu/libwebkit2gtk-4.0.so.37
 () at /lib/x86_64-linux-gnu/libwebkit2gtk-4.0.so.37
Title: WebKitWebProcess crashed with SIGSEGV
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm audio cdrom dip lpadmin lxd plugdev sambashare sudo
separator:

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


** Tags: amd64 apport-crash jammy need-amd64-retrace wayland-session

** Information type changed from Private to Public

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

Title:
  WebKitWebProcess crashed with SIGSEGV

Status in webkit2gtk package in Ubuntu:
  New

Bug description:
  Evolution, when launched with Wayland, suddenly closes. When launched
  from the command line, it displays this:

  Gdk-Message: 16:42:11.320: Error flushing display: Protocol error

  If forced with --display=:0, it works, but an obvious crash in
  WebKitWebProcess occurs, hence I believe the issue lies within that.

  ProblemType: Crash
  DistroRelease: Ubuntu 22.04
  Package: libwebkit2gtk-4.0-37 2.35.90-1ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-22.22-lowlatency 5.15.19
  Uname: Linux 5.15.0-22-lowlatency x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Mar 29 16:45:19 2022
  ExecutablePath: /usr/lib/x86_64-linux-gnu/webkit2gtk-4.0/WebKitWebProcess
  InstallationDate: Installed on 2021-08-19 (222 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210818)
  ProcCmdline: /usr/lib/x86_64-linux-gnu/webkit2gtk-4.0/WebKitWebProcess 13 43
  ProcEnviron:
   SHELL=/bin/bash
   LANG=en_US.UTF-8
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
   PATH=(custom, user)
  SegvAnalysis:
   Segfault happened at: 0x7fd90adae773:mov(%rdi),%rax
   PC (0x7fd90adae773) ok
   source "(%rdi)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%rax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: webkit2gtk
  StacktraceTop:
   () at /lib/x86_64-linux-gnu/libwebkit2gtk-4.0.so.37
   () at /lib/x86_64-linux-gnu/libwebkit2gtk-4.0.so.37
   () at /lib/x86_64-linux-gnu/libwebkit2gtk-4.0.so.37
   () at /lib/x86_64-linux-gnu/libwebkit2gtk-4.0.so.37
   () at /lib/x86_64-linux-gnu/libwebkit2gtk-4.0.so.37
  Title: WebKitWebProcess crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dip lpadmin lxd plugdev sambashare sudo
  separator:

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


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

[Desktop-packages] [Bug 1965219] Re: gnome lock screen does not permit reentering password

2022-03-29 Thread Jeff Burdges

It's growing kinda worst with 5.14.0-1031-oem in that gnome-shell now
more reliably fails unsleep, but I've not yet seen any real crash under
5.14.0-1031-oem.

I've still not tried non OWM kernels.

** Attachment added: "black_screen_with_mouse-29_march-b.txt"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1965219/+attachment/5574448/+files/black_screen_with_mouse-29_march-b.txt

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

Title:
  gnome lock screen does not permit reentering password

Status in gnome-shell package in Ubuntu:
  Incomplete
Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  Initially, only the mouse works in the gnome lock screen, without any
  way to get a password prompt.  It's likely only happening when
  returning from suspend with lid open.

  It's possible to ssh into the machine or to press Fn+Ctrl+Alt+F?? and
  login without gnome.  After this, Fn+Ctrl+Alt+F1 brings up a purple
  ubuntu login screen, but then after login you simply return to the
  lock screen with no working keyboard.  I never found any method to
  force unlock from ssh or another vt though, so this always still
  required a reboot, or killing all of gnome.

  I've randomly tried some solutions from
  https://askubuntu.com/questions/1242110/after-upgrading-to-
  ubuntu-20-04-lockscreen-not-working  including reinstalling many gnome
  components.  After this, the behavior initially disappeared by
  returning from suspend merely took a long time, like 30 seconds or 1
  minute.  It's possible the delay stems from memory size, but a
  previous identical lenovo x1 had no such problems.

  I've now a worse problem just a few hours later where unsuspend went
  directly to a purple ubuntu login screen, but neither the mouse nor
  keyboard worked.  I've not yet been able to test ssh on this problem.

  It's possibly all connected to recent firmware upgrades, so I'm happy
  to try downgrading the firmware, but I've not found any instructions
  on doing so, or even identifying the firmware upgrade log.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.14.0-1027.30-oem 5.14.21
  Uname: Linux 5.14.0-1027-oem x86_64
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Mar 17 03:44:49 2022
  DistUpgraded: Fresh install
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-sutton-focal-amd64-20210412-218+sutton-newell-focal-amd64+X00
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: Several times a day
  GpuHangReproducibility: Occurs more often under certain circumstances
  GpuHangStarted: Within the last week or two
  GraphicsCard:
   Intel Corporation Device [8086:9a49] (rev 01) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Device [17aa:22d5]
  InstallationDate: Installed on 2021-04-15 (335 days ago)
  InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 
20210412-22:07
  MachineType: LENOVO 20XWCTO1WW
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.14.0-1027-oem 
root=UUID=6a411137-06bb-4de1-be93-c2fcd4f44a5a ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/02/2021
  dmi.bios.release: 1.51
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N32ET75W (1.51 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20XWCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.32
  dmi.modalias: 
dmi:bvnLENOVO:bvrN32ET75W(1.51):bd12/02/2021:br1.51:efr1.32:svnLENOVO:pn20XWCTO1WW:pvrThinkPadX1CarbonGen9:rvnLENOVO:rn20XWCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20XW_BU_Think_FM_ThinkPadX1CarbonGen9:
  dmi.product.family: ThinkPad X1 Carbon Gen 9
  dmi.product.name: 20XWCTO1WW
  dmi.product.sku: LENOVO_MT_20XW_BU_Think_FM_ThinkPad X1 Carbon Gen 9
  dmi.product.version: ThinkPad X1 Carbon Gen 9
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.107-8ubuntu1~20.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.2
  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-vid

[Desktop-packages] [Bug 1965062] Re: [snap] firefox crash: adding native font failed: file=/usr/share/fonts/truetype/ubuntu/Ubuntu-R.ttf err=1

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

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

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

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

Title:
  [snap] firefox crash: adding native font failed:
  file=/usr/share/fonts/truetype/ubuntu/Ubuntu-R.ttf err=1

Status in firefox package in Ubuntu:
  Confirmed

Bug description:
  Hello,

  I'm having regular snap packaged Firefox crashes since 2022-03-14
  (Nightly from upstream is stable).

  According to the Mozilla crash report service, Firefox cannot find 
Ubuntu-R.ttf font file:
  MOZ_CRASH Reason (Sanitized): adding native font failed: 
file=/usr/share/fonts/truetype/ubuntu/Ubuntu-R.ttf err=1

  Affected Firefox versions: 97.0.1, 97.0.2, 98.0, 98.0.1

  snap info firefox:
  snap-id:  3wdHCAVyZEmYsCMFDE9qt92UV8rC8Wdk
  tracking: latest/stable
  refresh-date: yesterday at 13:31 CET
  installed:  98.0.1-2   (1115) 162MB -

  lsb_release -a:
  Distributor ID:   Ubuntu
  Description:  Ubuntu Jammy Jellyfish (development branch)
  Release:  22.04
  Codename: jammy

  Mozilla crash reports:
  - 
https://crash-stats.mozilla.org/report/index/c04b40e7-04fc-4c62-9e76-b651d0220314
  - 
https://crash-stats.mozilla.org/report/index/980ff557-a770-44e4-b735-f09260220314
  - 
https://crash-stats.mozilla.org/report/index/980ff557-a770-44e4-b735-f09260220314
  - 
https://crash-stats.mozilla.org/report/index/35fcad7b-9e1f-41fa-9c35-02eaa0220314
  - 
https://crash-stats.mozilla.org/report/index/547b9770-3211-43c3-8251-d105f0220315

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


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

[Desktop-packages] [Bug 1965062] Re: [snap] firefox crash: adding native font failed: file=/usr/share/fonts/truetype/ubuntu/Ubuntu-R.ttf err=1

2022-03-29 Thread sir phobos

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

i believe it's not a duplicate
this exact crash happend to me 2 times on snap 98.0.1-2
first time firefox crashed after ~2 days of work
second time - after around 5 days of work
no clear way to reproduce the crash found.

there were no snap updates during the work of firefox both times.
currently switched to snap 98.0.2-1, waiting to see if crash happens again

ubuntu 20.04.4 LTS
5.13.0-35-generic

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

Title:
  [snap] firefox crash: adding native font failed:
  file=/usr/share/fonts/truetype/ubuntu/Ubuntu-R.ttf err=1

Status in firefox package in Ubuntu:
  Confirmed

Bug description:
  Hello,

  I'm having regular snap packaged Firefox crashes since 2022-03-14
  (Nightly from upstream is stable).

  According to the Mozilla crash report service, Firefox cannot find 
Ubuntu-R.ttf font file:
  MOZ_CRASH Reason (Sanitized): adding native font failed: 
file=/usr/share/fonts/truetype/ubuntu/Ubuntu-R.ttf err=1

  Affected Firefox versions: 97.0.1, 97.0.2, 98.0, 98.0.1

  snap info firefox:
  snap-id:  3wdHCAVyZEmYsCMFDE9qt92UV8rC8Wdk
  tracking: latest/stable
  refresh-date: yesterday at 13:31 CET
  installed:  98.0.1-2   (1115) 162MB -

  lsb_release -a:
  Distributor ID:   Ubuntu
  Description:  Ubuntu Jammy Jellyfish (development branch)
  Release:  22.04
  Codename: jammy

  Mozilla crash reports:
  - 
https://crash-stats.mozilla.org/report/index/c04b40e7-04fc-4c62-9e76-b651d0220314
  - 
https://crash-stats.mozilla.org/report/index/980ff557-a770-44e4-b735-f09260220314
  - 
https://crash-stats.mozilla.org/report/index/980ff557-a770-44e4-b735-f09260220314
  - 
https://crash-stats.mozilla.org/report/index/35fcad7b-9e1f-41fa-9c35-02eaa0220314
  - 
https://crash-stats.mozilla.org/report/index/547b9770-3211-43c3-8251-d105f0220315

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


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

[Desktop-packages] [Bug 1966556] Re: gjs-console crashed with SIGSEGV in g_main_dispatch()

2022-03-29 Thread Martin Wimpress 

** Information type changed from Private to Public

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

Title:
  gjs-console crashed with SIGSEGV in g_main_dispatch()

Status in gjs package in Ubuntu:
  Confirmed

Bug description:
  gjs-console crashed with SIGSEGV in g_main_context_dispatch()

  ProblemType: Crash
  DistroRelease: Ubuntu 22.04
  Package: gjs 1.72.0-1
  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: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Mar 26 13:33:01 2022
  Disassembly: => 0x0:  Não é possível acessar a memória no endereço 0x0
  ExecutablePath: /usr/bin/gjs-console
  InstallationDate: Installed on 2022-03-20 (6 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220319)
  ProcCmdline: /usr/bin/gjs /usr/share/gnome-maps/org.gnome.Maps 
--gapplication-service
  SegvAnalysis:
   Segfault happened at: 0x0:   Não é possível acessar a memória no endereço 0x0
   PC (0x) not located in a known VMA region (needed executable region)!
   source "0x0" (0x) not located in a known VMA region (needed readable 
region)!
  SegvReason:
   executing NULL VMA
   reading NULL VMA
  Signal: 11
  SourcePackage: gjs
  StacktraceTop:
   ?? ()
   g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libedataserver-1.2.so.26
  Title: gjs-console crashed with SIGSEGV in g_main_context_dispatch()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  separator:

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


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

[Desktop-packages] [Bug 1966589] Re: Upgrader unable to contact snap store

** Changed in: ubuntu-release-upgrader (Ubuntu)
Milestone: None => ubuntu-22.04

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

Title:
  Upgrader unable to contact snap store

Status in firefox package in Ubuntu:
  New
Status in ubuntu-release-upgrader package in Ubuntu:
  New

Bug description:
  Upgrading from Lubuntu Focal 20.04.4 to Lubuntu Jammy 22.04 (date
  27.03.2022)

  The upgrader was unable to connect to the snap store in order to
  install the firefox snap

  The upgrade was performed with GUI - do-release-upgrade -d -m desktop
  -f DistUpgradeViewKDE

  The error "could not install the upgrades" was received.
  I closed the error and then received th dialog box message "upgrade complete 
but there were errors during the upgrade process"

  After rebooting I received an upgrade notification and the Firefox
  snap was installed.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: ubuntu-release-upgrader-core 1:22.04.7
  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
  CrashDB: ubuntu
  CurrentDesktop: LXQt
  Date: Sun Mar 27 13:08:26 2022
  InstallationDate: Installed on 2022-03-27 (0 days ago)
  InstallationMedia: Lubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 
(20220223)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: ubuntu-release-upgrader
  UpgradeStatus: Upgraded to jammy on 2022-03-27 (0 days ago)
  VarLogDistupgradeXorgFixuplog:
   INFO:root:/usr/bin/do-release-upgrade running
   INFO:root:No xorg.conf, exiting

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


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

[Desktop-packages] [Bug 1965661] Re: software-properties-gtk crashed with AttributeError in packages_for_modalias(): 'Cache' object has no attribute 'packages'

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

** This bug has been marked a duplicate of bug 1964880
   software-properties-gtk crashed with AttributeError in 
packages_for_modalias(): 'Cache' object has no attribute 'packages'

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

Title:
  software-properties-gtk crashed with AttributeError in
  packages_for_modalias(): 'Cache' object has no attribute 'packages'

Status in software-properties package in Ubuntu:
  Confirmed

Bug description:
  software-properties-gtk crashed with AttributeError in
  packages_for_modalias(): 'Cache' object has no attribute 'packages'

  ProblemType: Crash
  DistroRelease: Ubuntu 22.04
  Package: software-properties-gtk 0.99.19
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Uname: Linux 5.15.0-23-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  CasperMD5CheckResult: pass
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Mar 20 03:33:53 2022
  ExecutablePath: /usr/bin/software-properties-gtk
  InstallationDate: Installed on 2022-03-20 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220319)
  InterpreterPath: /usr/bin/python3.10
  PackageArchitecture: all
  ProcCmdline: /usr/bin/python3 /usr/bin/software-properties-gtk --open-tab 2
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Python3Details: /usr/bin/python3.10, Python 3.10.2+, python3-minimal, 
3.10.1-0ubuntu2
  PythonArgs: ['/usr/bin/software-properties-gtk', '--open-tab', '2']
  PythonDetails: N/A
  SourcePackage: software-properties
  Title: software-properties-gtk crashed with AttributeError in 
packages_for_modalias(): 'Cache' object has no attribute 'packages'
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo

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


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

[Desktop-packages] [Bug 1964541] Re: Cannot rearrange Firefox (snap) browser tabs/bookmarks in Wayland sessions

** Summary changed:

- Cannot rearrange Firefox (snap) browser tabs in Wayland sessions
+ Cannot rearrange Firefox (snap) browser tabs/bookmarks in Wayland sessions

** Tags added: snap

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

Title:
  Cannot rearrange Firefox (snap) browser tabs/bookmarks in Wayland
  sessions

Status in Mozilla Firefox:
  New
Status in firefox package in Ubuntu:
  Confirmed

Bug description:
  Since 42~beta-1ubuntu1, and still present in 42~beta-1ubuntu2,
  attempting to re-arrange tabs in Firefox fails. Click and drag the tab
  and release, nothing changes. The next click to the tab is ignored.

  syslog has the following:

  Mar 11 13:06:47 desktop firefox[2192]: Attempting to add a widget with type 
GtkWindow to a container of type GtkWindow, but the widget is already inside a 
container of type GtkWindow, please remove the widget from its existing 
container first.
  Mar 11 13:06:48 desktop firefox[2192]: Attempting to add a widget with type 
GtkWindow to a container of type GtkWindow, but the widget is already inside a 
container of type GtkWindow, please remove the widget from its existing 
container first.
  Mar 11 13:06:50 desktop firefox[2192]: Attempting to add a widget with type 
GtkWindow to a container of type GtkWindow, but the widget is already inside a 
container of type GtkWindow, please remove the widget from its existing 
container first.
  Mar 11 13:06:51 desktop firefox[2192]: Attempting to add a widget with type 
GtkWindow to a container of type GtkWindow, but the widget is already inside a 
container of type GtkWindow, please remove the widget from its existing 
container first.

  gnome-shell 42~beta-1ubuntu2
  Firefox Snap 98.0-3 (1073)

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


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

[Desktop-packages] [Bug 1967011] Re: Unable to Share Screen via PipeWire in OBS Studio

2022-03-29 Thread Timo Witte

Just tried it out locally and rebuild the mutter package, worked like a
charm.

** Patch added: "change which fixed the issue taken from upstream"
   
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1967011/+attachment/5574433/+files/fix_pipewire_on_amdgpu.patch

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

Title:
  Unable to Share Screen via PipeWire in OBS Studio

Status in mutter package in Ubuntu:
  New

Bug description:
  Hello,

  please pull in this change:
  https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2322

  This is the relevant bug in the mutter repo:
  https://gitlab.gnome.org/GNOME/mutter/-/issues/2155

  as it blocks OBS / Telegram from receiving screen sharing on AMD GPUs.

  Mär 29 23:32:24 egal-12 gnome-shell[3219]: setup_framebuffers: assertion 
'width > 0' failed
  Mär 29 23:32:26 egal-12 com.obsproject.Studio.desktop[55756]: info: 
[pipewire] desktop selected, setting up screencast
  Mär 29 23:32:26 egal-12 com.obsproject.Studio.desktop[55756]: info: 
[pipewire] server version: 0.3.48
  Mär 29 23:32:26 egal-12 com.obsproject.Studio.desktop[55756]: info: 
[pipewire] library version: 0.3.48
  Mär 29 23:32:26 egal-12 com.obsproject.Studio.desktop[55756]: info: 
[pipewire] header version: 0.3.48
  Mär 29 23:32:26 egal-12 com.obsproject.Studio.desktop[55756]: info: 
[pipewire] created stream 0x564c4e1f7480
  Mär 29 23:32:26 egal-12 com.obsproject.Studio.desktop[55756]: info: 
[pipewire] playing stream…
  Mär 29 23:32:26 egal-12 gnome-shell[3219]: No supported PipeWire stream 
buffer data type could be negotiated
  Mär 29 23:32:26 egal-12 gnome-shell[3219]: No supported PipeWire stream 
buffer data type could be negotiated
  Mär 29 23:32:26 egal-12 gnome-shell[3219]: No supported PipeWire stream 
buffer data type could be negotiated
  Mär 29 23:32:26 egal-12 gnome-shell[3219]: No supported PipeWire stream 
buffer data type could be negotiated
  Mär 29 23:32:26 egal-12 gnome-shell[3219]: No supported PipeWire stream 
buffer data type could be negotiated
  Mär 29 23:32:26 egal-12 gnome-shell[3219]: No supported PipeWire stream 
buffer data type could be negotiated
  Mär 29 23:32:26 egal-12 gnome-shell[3219]: No supported PipeWire stream 
buffer data type could be negotiated
  Mär 29 23:32:26 egal-12 gnome-shell[3219]: No supported PipeWire stream 
buffer data type could be negotiated
  Mär 29 23:32:26 egal-12 gnome-shell[3219]: No supported PipeWire stream 
buffer data type could be negotiated
  Mär 29 23:32:26 egal-12 gnome-shell[3219]: No supported PipeWire stream 
buffer data type could be negotiated
  Mär 29 23:32:26 egal-12 gnome-shell[3219]: No supported PipeWire stream 
buffer data type could be negotiated
  Mär 29 23:32:26 egal-12 gnome-shell[3219]: No supported PipeWire stream 
buffer data type could be negotiated
  Mär 29 23:32:26 egal-12 gnome-shell[3219]: No supported PipeWire stream 
buffer data type could be negotiated
  Mär 29 23:32:26 egal-12 gnome-shell[3219]: No supported PipeWire stream 
buffer data type could be negotiated
  Mär 29 23:32:26 egal-12 gnome-shell[3219]: No supported PipeWire stream 
buffer data type could be negotiated
  Mär 29 23:32:26 egal-12 gnome-shell[3219]: No supported PipeWire stream 
buffer data type could be negotiated
  Mär 29 23:32:26 egal-12 gnome-shell[3219]: pipewire remote error: id:0 
connection error
  Mär 29 23:32:26 egal-12 pipewire[2993]: spa.v4l2: wanted XR24 2560x1440, got 
YUYV 2304x1536
  Mär 29 23:32:26 egal-12 pipewire[2993]: pw.link: tried to set output format:
  Mär 29 23:32:26 egal-12 pipewire[2993]: default: Object: size 320, type 
Spa:Pod:Object:Param:Format (262147), id Spa:Enum:ParamId:Format (4)
  Mär 29 23:32:26 egal-12 pipewire[2993]: default:   Prop: key 
Spa:Pod:Object:Param:Format:mediaType (1), flags 
  Mär 29 23:32:26 egal-12 pipewire[2993]: default: Choice: type 
Spa:Enum:Choice:None, flags  20 4

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


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

[Desktop-packages] [Bug 1967011] [NEW] Unable to Share Screen via PipeWire in OBS Studio

2022-03-29 Thread Timo Witte

Public bug reported:

Hello,

please pull in this change:
https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2322

This is the relevant bug in the mutter repo:
https://gitlab.gnome.org/GNOME/mutter/-/issues/2155

as it blocks OBS / Telegram from receiving screen sharing on AMD GPUs.

Mär 29 23:32:24 egal-12 gnome-shell[3219]: setup_framebuffers: assertion 'width 
> 0' failed
Mär 29 23:32:26 egal-12 com.obsproject.Studio.desktop[55756]: info: [pipewire] 
desktop selected, setting up screencast
Mär 29 23:32:26 egal-12 com.obsproject.Studio.desktop[55756]: info: [pipewire] 
server version: 0.3.48
Mär 29 23:32:26 egal-12 com.obsproject.Studio.desktop[55756]: info: [pipewire] 
library version: 0.3.48
Mär 29 23:32:26 egal-12 com.obsproject.Studio.desktop[55756]: info: [pipewire] 
header version: 0.3.48
Mär 29 23:32:26 egal-12 com.obsproject.Studio.desktop[55756]: info: [pipewire] 
created stream 0x564c4e1f7480
Mär 29 23:32:26 egal-12 com.obsproject.Studio.desktop[55756]: info: [pipewire] 
playing stream…
Mär 29 23:32:26 egal-12 gnome-shell[3219]: No supported PipeWire stream buffer 
data type could be negotiated
Mär 29 23:32:26 egal-12 gnome-shell[3219]: No supported PipeWire stream buffer 
data type could be negotiated
Mär 29 23:32:26 egal-12 gnome-shell[3219]: No supported PipeWire stream buffer 
data type could be negotiated
Mär 29 23:32:26 egal-12 gnome-shell[3219]: No supported PipeWire stream buffer 
data type could be negotiated
Mär 29 23:32:26 egal-12 gnome-shell[3219]: No supported PipeWire stream buffer 
data type could be negotiated
Mär 29 23:32:26 egal-12 gnome-shell[3219]: No supported PipeWire stream buffer 
data type could be negotiated
Mär 29 23:32:26 egal-12 gnome-shell[3219]: No supported PipeWire stream buffer 
data type could be negotiated
Mär 29 23:32:26 egal-12 gnome-shell[3219]: No supported PipeWire stream buffer 
data type could be negotiated
Mär 29 23:32:26 egal-12 gnome-shell[3219]: No supported PipeWire stream buffer 
data type could be negotiated
Mär 29 23:32:26 egal-12 gnome-shell[3219]: No supported PipeWire stream buffer 
data type could be negotiated
Mär 29 23:32:26 egal-12 gnome-shell[3219]: No supported PipeWire stream buffer 
data type could be negotiated
Mär 29 23:32:26 egal-12 gnome-shell[3219]: No supported PipeWire stream buffer 
data type could be negotiated
Mär 29 23:32:26 egal-12 gnome-shell[3219]: No supported PipeWire stream buffer 
data type could be negotiated
Mär 29 23:32:26 egal-12 gnome-shell[3219]: No supported PipeWire stream buffer 
data type could be negotiated
Mär 29 23:32:26 egal-12 gnome-shell[3219]: No supported PipeWire stream buffer 
data type could be negotiated
Mär 29 23:32:26 egal-12 gnome-shell[3219]: No supported PipeWire stream buffer 
data type could be negotiated
Mär 29 23:32:26 egal-12 gnome-shell[3219]: pipewire remote error: id:0 
connection error
Mär 29 23:32:26 egal-12 pipewire[2993]: spa.v4l2: wanted XR24 2560x1440, got 
YUYV 2304x1536
Mär 29 23:32:26 egal-12 pipewire[2993]: pw.link: tried to set output format:
Mär 29 23:32:26 egal-12 pipewire[2993]: default: Object: size 320, type 
Spa:Pod:Object:Param:Format (262147), id Spa:Enum:ParamId:Format (4)
Mär 29 23:32:26 egal-12 pipewire[2993]: default:   Prop: key 
Spa:Pod:Object:Param:Format:mediaType (1), flags 
Mär 29 23:32:26 egal-12 pipewire[2993]: default: Choice: type 
Spa:Enum:Choice:None, flags  20 4

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

** Description changed:

  Hello,
  
  please pull in this change:
  https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2322
  
+ This is the relevant bug in the mutter repo:
+ https://gitlab.gnome.org/GNOME/mutter/-/issues/2155
+ 
  as it blocks OBS / Telegram from receiving screen sharing on AMD GPUs.
- 
  
  Mär 29 23:32:24 egal-12 gnome-shell[3219]: setup_framebuffers: assertion 
'width > 0' failed
  Mär 29 23:32:26 egal-12 com.obsproject.Studio.desktop[55756]: info: 
[pipewire] desktop selected, setting up screencast
  Mär 29 23:32:26 egal-12 com.obsproject.Studio.desktop[55756]: info: 
[pipewire] server version: 0.3.48
  Mär 29 23:32:26 egal-12 com.obsproject.Studio.desktop[55756]: info: 
[pipewire] library version: 0.3.48
  Mär 29 23:32:26 egal-12 com.obsproject.Studio.desktop[55756]: info: 
[pipewire] header version: 0.3.48
  Mär 29 23:32:26 egal-12 com.obsproject.Studio.desktop[55756]: info: 
[pipewire] created stream 0x564c4e1f7480
  Mär 29 23:32:26 egal-12 com.obsproject.Studio.desktop[55756]: info: 
[pipewire] playing stream…
  Mär 29 23:32:26 egal-12 gnome-shell[3219]: No supported PipeWire stream 
buffer data type could be negotiated
  Mär 29 23:32:26 egal-12 gnome-shell[3219]: No supported PipeWire stream 
buffer data type could be negotiated
  Mär 29 23:32:26 egal-12 gnome-shell[3219]: No supported PipeWire stream 
buffer data type could be negotiated
  Mär 29 23:32:26 egal-12 gnome-shell[3219]: No supported PipeWire stream 
buffer data type could be negotiated
  Mär 2

[Desktop-packages] [Bug 1965085] Re: Login screen sometimes unresponsive to mouse clicks (after waking from sleep)

Just an update to my comment #2.

Changing to a single monitor set-up I'm seeing the reported problem
without any of the side effects that I reported while using dual
monitors.

I don't see this as an issue that is related to a PC being put into
sleep mode as any short or long duration of the lock screen being
invoked for has, on my laptop, seen this bug make an appearance.

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

Title:
  Login screen sometimes unresponsive to mouse clicks (after waking from
  sleep)

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

Bug description:
  The login screen is sometimes unresponsive to mouse clicks (after
  waking from sleep).

  I can generally get it working again either by hitting Tab, or by
  switching VTs.

  Seems to happen with either Wayland or Xorg greeters.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 42~beta-1ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19
  Uname: Linux 5.15.0-22-generic x86_64
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Wed Mar 16 14:07:16 2022
  DisplayManager: gdm3
  InstallationDate: Installed on 2021-11-05 (130 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211103)
  RelatedPackageVersions: mutter-common 42~beta-1ubuntu2
  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/gdm3/+bug/1965085/+subscriptions


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

[Desktop-packages] [Bug 1964541] Re: Cannot rearrange Firefox (snap) browser tabs in Wayland sessions

2022-03-29 Thread Bug Watch Updater

Launchpad has imported 5 comments from the remote bug at
https://bugzilla.mozilla.org/show_bug.cgi?id=1760449.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.

On 2022-03-19T16:38:59+00:00 Jeremie Tamburini wrote:

User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:98.0) Gecko/20100101
Firefox/98.0

Steps to reproduce:

Fresh installed Ubuntu 22.04 (still development version) with Firefox snap
version 98.0.1
(Also tried version 99 and 100 available on https://snapcraft.io/firefox same
behavior).

1. Right click on toolbar
2. Select "Customise Toolbar"
3. Tried to remove items from the toolbar and add items on it via "drag and
drop".

Actual results:

Nothing happens. It looks like drag and drop doesn't work.
While trying to move items, they simply disappear.
You can see a short video: https://www.youtube.com/watch?v=vsnr8O5EgFk

(Also tried to run Firefox from the terminal, but I didn't receive any
warning while trying to customize the toolbar).

Expected results:

What should have happened is that every items should be moved between the
toolbar and the list of items as shown in the official documentation:
https://support.mozilla.org/en-US/kb/customize-firefox-controls-buttons-and-toolbars

Reply at:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1964541/comments/12

On 2022-03-19T17:17:53+00:00 Release-mgmt-account-bot wrote:

The [Bugbug](https://github.com/mozilla/bugbug/) bot thinks this bug
should belong to the 'Firefox::Toolbars and Customization' component,
and is moving the bug to that component. Please correct in case you
think the bot is wrong.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1964541/comments/13

On 2022-03-19T21:36:29+00:00 Jeremie Tamburini wrote:

I've realized 2 new things:
1. this problem is related to the **Wayland** session
2. drag and drop doesn't work also with tabs

No problem at all selecting the xorg session at login, and this actually works
as workaround.
I have seen other bug report mentioning similar problems. So my bug report
could be a duplicated of
[1739981](https://bugzilla.mozilla.org/show_bug.cgi?id=1739981) and
[1739970](https://bugzilla.mozilla.org/show_bug.cgi?id=1739970)

I'm going to update the first post.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1964541/comments/14

On 2022-03-23T13:17:23+00:00 Stransky wrote:

Can you try plain Mozilla nightly binary?
https://fedoraproject.org/wiki/How_to_debug_Firefox_problems?rd=Bug_info_Firefox#Testing_Mozilla_binaries
Thanks.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1964541/comments/17

On 2022-03-23T15:59:04+00:00 Jeremie Tamburini wrote:

Thanks @Martin Stránský

I've run the test with Firefox *nightly* using the `MOZ_ENABLE_WAYLAND=1
./firefox -ProfileManager -no-remote` parameters and everything works as
expected.

The problem seems to be confined to **snap** version of Firefox in
**Wayland** session (snap nightly version included). The snap package
works fine with the old X11 session.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1964541/comments/18

** Changed in: firefox
Status: Unknown => New

** Bug watch added: Mozilla Bugzilla #1739981
https://bugzilla.mozilla.org/show_bug.cgi?id=1739981

** Bug watch added: Mozilla Bugzilla #1739970
https://bugzilla.mozilla.org/show_bug.cgi?id=1739970

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

Title:
Cannot rearrange Firefox (snap) browser tabs in Wayland sessions

Status in Mozilla Firefox:
New
Status in firefox package in Ubuntu:
Confirmed

Bug description:
Since 42~beta-1ubuntu1, and still present in 42~beta-1ubuntu2,
attempting to re-arrange tabs in Firefox fails. Click and drag the tab
and release, nothing changes. The next click to the tab is ignored.

syslog has the following:

Mar 11 13:06:47 desktop firefox[2192]: Attempting to add a widget with type
GtkWindow to a container of type GtkWindow, but the widget is already inside a
container of type GtkWindow, please remove the widget from its existing
container first.
Mar 11 13:06:48 desktop firefox[2192]: Attempting to add a widget with type
GtkWindow to a container of type GtkWindow, but the widget is already inside a
container of type GtkWindow, please remove the widget from its existing
container first.
Mar 11 13:06:5

[Desktop-packages] [Bug 1947210] Re: Firefox Snap can't copy&paste or drag&drop in Wayland

2022-03-29 Thread cesar

btw, in esr firefox all working... so, something else is making this
kind of thing in firefox snap.

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

Title:
  Firefox Snap can't copy&paste or drag&drop in Wayland

Status in Mozilla Firefox:
  Confirmed
Status in firefox package in Ubuntu:
  Fix Released

Bug description:
  I just upgraded to 21.10 Impish which supplies Firefox 93.0-1 via
  snap. I could not copy and paste to and from the browser. I logged out
  of Wayland and into Xorg and copy & paste works.

  Already reported at
  https://bugzilla.mozilla.org/show_bug.cgi?id=1729901 so it's a known
  issue.

  I wanted to report it here so it gets into the Impish release notes or
  wherever along with the workaround.

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


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

[Desktop-packages] [Bug 1963628] Re: Force IIO_SENSOR_PROXY_TYPE to iio-buffer-als for some Dell models

** Also affects: iio-sensor-proxy (Ubuntu Focal)
   Importance: Undecided
   Status: New

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

Title:
  Force IIO_SENSOR_PROXY_TYPE to iio-buffer-als for some Dell models

Status in OEM Priority Project:
  New
Status in iio-sensor-proxy package in Ubuntu:
  Fix Released
Status in iio-sensor-proxy source package in Focal:
  New

Bug description:
  We are encountering issues, that when enabling some Dell laptops, the readings
  from iio-poll-als are unstable, or could freeze on certain value.  On these
  systems they have ENV{IIO_SENSOR_PROXY_TYPE}="iio-poll-als iio-buffer-als", 
and
  removing iio-poll-als makes reading stable.

  This adds workaround to the affected Dell laptop models which may equip with
  ALS.

  [Impact]

   * Only models matching the same device BIOS IDs are affected.

  [Test Plan]

   * Pick devices which BIOS IDs are listed in the patch, and test
  whether it's ambient light sensors are working properly without
  unexpected brightness flickers.

  [Where problems could occur]

   * Machines matching the same BIOS ID, either having ALS built-in or
  not, but attached ambient light sensors externally (for example,
  ColorHug ALS) might experience failures.

  [Other Info]
   
   * Upstream merge request: 
https://gitlab.freedesktop.org/hadess/iio-sensor-proxy/-/merge_requests/352

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1963628/+subscriptions


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

[Desktop-packages] [Bug 1910421] Re: Evince crashes on an unreadable nonempty postscript file owned by root

Thank you for reporting this bug to Ubuntu.

We are sorry that we do not always have the capacity to look at all
reported bugs in a timely manner. You reported this bug some time ago
and there have been many changes in Ubuntu since that time. Your problem
may have been fixed with some of the updates.

Ubuntu 20.10 (groovy) reached end-of-life on July 22, 2021.

If this bug is still present in a currently supported release of Ubuntu
then please add a comment here telling us which new version it is in and
change the bug status to 'New'.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases


** Tags added: groovy

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

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

Title:
  Evince crashes on an unreadable nonempty postscript file owned by root

Status in evince package in Ubuntu:
  Incomplete

Bug description:
  Package: evince
  Version: 3.38.0-1

  I run an up-to-date groovy 20.10.

  This is how to reproduce the segfault:

  root@host:/tmp# rm mwe.ps
  root@host:/tmp# echo "test" > mwe.ps
  root@host:/tmp# chmod g-rwx,o-rwx mwe.ps
  root@host:/tmp# exit
  logout
  user@host:/tmp$ evince mwe.ps
  Segmentation fault (core dumped)

  An expected outcome would be a meaningful error message instead of a
  crash.  Thanks in advance for repairing this bug.

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


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

[Desktop-packages] [Bug 1931494] Re: Wrong scaling

Thank you for taking the time to report this bug and helping to make
Ubuntu better.

Please execute the following command only once, as it will automatically
gather debugging information, in a terminal:

  apport-collect 1931494

When reporting bugs in the future please use apport by using 'ubuntu-
bug' and the name of the package affected. You can learn more about this
functionality at https://wiki.ubuntu.com/ReportingBugs.

** Tags added: focal

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

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

Title:
  Wrong scaling

Status in evince package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 20.04
  Evince 3.36.10

  If I set the scale to 100% the document on display is twice the real size.
  To see the document at the correct size I have to set the scale to 50%.
  Evince 3.36.7 does not have this bug.

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


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

[Desktop-packages] [Bug 1964747] Re: [Jammy][regression] u-d-c default to use 470 instead of 510

@Alberto - the fix for bug 1958488 was released yesterday so the
verifications can be uncoupled now. Will you please reupload ubuntu-
drivers-common to -proposed with a source.changes file that doesn't
reference the previous bug anymore? Thanks in advance.

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

Title:
  [Jammy][regression] u-d-c default to use 470 instead of 510

Status in OEM Priority Project:
  Confirmed
Status in ubuntu-drivers-common package in Ubuntu:
  Fix Released
Status in ubuntu-drivers-common source package in Bionic:
  In Progress
Status in ubuntu-drivers-common source package in Focal:
  In Progress
Status in ubuntu-drivers-common source package in Impish:
  In Progress

Bug description:
  [Impact]

   * In Ubuntu 22.04, ubuntu-drivers install will install nvidia-470 instead of 
510. (the ubuntu-drivers install is the best and recommended way to install 
nvidia driver).
   * nvidia-470 is LTSB (although webpage shows PB) and nvidia-510 is PB, in 
this case, we need to chose the newer version since the support is fair in both 
version.
   * Also, 22.04 announces Wayland supports but nvidia-470 doesn't support in 
Wayland scope at least from gdm upstream.

  [Test Plan]

   * Call "ubuntu-drivers debug" and check that 510 is marked as 
"(auto-install)"
  ```
  ...
  === matching driver packages ===
  nvidia-driver-510: installed:available: 510.54-0ubuntu2  [distro]  
non-free  modalias: pci:v10DEd25A0sv1028sd0A61bc03sc02i00  
path: /sys/devices/pci:00/:00:01.0/:01:00.0  vendor: NVIDIA 
Corporation  model: GA107M [GeForce RTX 3050 Ti Mobile]
  ...
  nvidia-driver-470: installed:available: 470.103.01-0ubuntu2 
(auto-install)  [distro]  non-free  modalias: 
pci:v10DEd25A0sv1028sd0A61bc03sc02i00  path: 
/sys/devices/pci:00/:00:01.0/:01:00.0  vendor: NVIDIA Corporation  
model: GA107M [GeForce RTX 3050 Ti Mobile]  support level: LTSB
  ...
  ```
   * As you can see, "(auto-install)" points to 470 because it owns LTSB tag.

  [Fix]
   * Adjust the priority in UbuntuDrivers/detect.py, if the PB and LTSB 
versions found, then it needs to pick the newer version one.

  [Where problems could occur]
   * It has less possible to introduce regression since the patch only changes 
_cmp_gfx_alternatives() which counts the priority of nvidia drivers be 
installed.
   * In Ubuntu, we have nvidia-390, 470 and 510 so far as I known and these 
cases are listed in test_system_driver_packages_chroot_support_branch_pb.

  ---

  + nvidia-graphics-drivers-510 (510.54-0ubuntu0.20.04.1)
  +
  +   * New upstream release (LP: #1961075):
  + - Fixed a bug that could cause GPU exceptions when minimizing a
  +   fullscreen Vulkan application on certain desktops, such as
  +   Plasma.
  +   * debian/templates/control.in:
  + - Set XB-Support to PB (production branch).
  +   * debian/rules.defs:
  + - Add support for video ABI 25.

  ---

  Since
    * debian/templates/control.in:
  - Set XB-Support to PB (production branch).

  The u-d-c will choose LTS branch instead of PB branch.

  because `def _cmp_gfx_alternatives(x, y):` doesn't define PB.

  [Additional information]
  If installed 470 instead of 510, then it will cause
  https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1963701

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1964747/+subscriptions


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

[Desktop-packages] [Bug 1966418] Re: [jammy regression] Evolution does not display message content anymore

2022-03-29 Thread Bug Watch Updater

Launchpad has imported 4 comments from the remote bug at
https://bugs.webkit.org/show_bug.cgi?id=238513.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2022-03-29T18:10:40+00:00 Jeremy Bicha wrote:

webkit2gtk 2.35.90-1ubuntu1
Ubuntu 22.04 Beta

I am reporting this Ubuntu bug here for tracking.

All webkitgtk using apps just show a blank webview (either light with a
light theme or dark with a dark theme). The cursor does change when
hovering over invisible links.

When run from the command line this shows:
EGLDisplay Initialization failed: EGL_NOT_INITIALIZED
Cannot create EGL context: invalid display (last error: EGL_SUCCESS)

This only happens when logged into a GNOME/Ubuntu on Wayland session.
Either running in an Xorg session or with the
WEBKIT_DISABLE_COMPOSITING_MODE=1 prefix works around the problem.

Other Information
=
I believe this bug was triggered by the recent upgrade to mesa 22.0.

I think it might only affect Intel graphics.

My system according to GNOME has
Intel® Core™ i5-10310U CPU
Mesa Intel® UHD Graphics (CML GT2)

Reply at:
https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1966418/comments/36


On 2022-03-29T18:51:21+00:00 Michael Catanzaro wrote:

> I believe this bug was triggered by the recent upgrade to mesa 22.0.

Huh, here on Fedora 36 I only have mesa 21.3.8.

Is it possible to downgrade mesa to confirm that the mesa upgrade is to
blame? That would help a lot.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1966418/comments/37


On 2022-03-29T19:04:56+00:00 Jeremy Bicha wrote:

Yes, the bug went away when I downgraded the mesa packages to
21.3.5-1ubuntu2

Reply at:
https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1966418/comments/38


On 2022-03-29T20:10:05+00:00 Adrian Perez wrote:

Further trying to help narrow down: I have Mesa 22.0 here and things
work fine, but my GPU is different (Intel HD Graphics 520 SKL GT2),
so this points towards either device-specific code, or towards the
Mesa driver chosen by the Mesa loader.

Note that there are two drivers: the traditional “i965” and the new
“iris” driver. Here I am using “iris” (and there is not even the other
installed).

You can set “MESA_LOADER_DRIVER_OVERRIDE=iris” if your GPU is supported
by the new driver and if things then work that will mean that the issue
is most likely the i965 driver. Alternatively, if Iris driver does not
support your GPU but Vulkan is supported, you can try the “zink” driver,
which implements OpenGL and GLES on top of Vulkan (and again, if that
works, then there is some bug in the Intel driver you are using :D)

I hope this helps!

Reply at:
https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1966418/comments/39


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

** Changed in: webkit
   Importance: Unknown => Medium

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

Title:
  [jammy regression] Evolution does not display message content anymore

Status in Webkit:
  Confirmed
Status in epiphany-browser package in Ubuntu:
  Confirmed
Status in evolution package in Ubuntu:
  Confirmed
Status in liferea package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  Confirmed
Status in webkit2gtk package in Ubuntu:
  Confirmed

Bug description:
  Impact
  --
  All webkit using apps for affected users display a blank screen.

  Original Bug Report
  ---
  Evolution has suddenly stopped displaying message contents on the last 24h. 
Starting it up from the command line shows this output:

  ```
  EGLDisplay Initialization failed: EGL_NOT_INITIALIZED
  Cannot create EGL context: invalid display (last error: EGL_SUCCESS)
  ```

  I don't know if it's related, but googling around shows some webkitgtk
  hits on this error.

  The email contents are however clickable. They're just not rendered to
  screen (see attached file).

  Deleting the evolution folders from `~/.config`, `~/.cache` and
  `~/.local/share` does not help.

  Email accounts are all google, configured through gnome online
  accounts.

  Workaround #1
  -
  You can run the app from the command line with
  WEBKIT_DISABLE_COMPOSITING_MODE=1 evolution
  (Replace evolution with the name of the webkit app you are trying to use)

  Workaround #2
  -
  Log out.
  Select your name on the login screen.
  Click the gear button and choose Ubuntu on Xorg.
  Enter your passw

[Desktop-packages] [Bug 1966418] Re: [jammy regression] Evolution does not display message content anymore

2022-03-29 Thread Jeremy Bicha

** Bug watch added: bugs.webkit.org/ #238513
   https://bugs.webkit.org/show_bug.cgi?id=238513

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

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

** Changed in: webkit
 Remote watch: bugs.webkit.org/ #238244 => bugs.webkit.org/ #238513

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

Title:
  [jammy regression] Evolution does not display message content anymore

Status in Webkit:
  Unknown
Status in epiphany-browser package in Ubuntu:
  Confirmed
Status in evolution package in Ubuntu:
  Confirmed
Status in liferea package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  Confirmed
Status in webkit2gtk package in Ubuntu:
  Confirmed

Bug description:
  Impact
  --
  All webkit using apps for affected users display a blank screen.

  Original Bug Report
  ---
  Evolution has suddenly stopped displaying message contents on the last 24h. 
Starting it up from the command line shows this output:

  ```
  EGLDisplay Initialization failed: EGL_NOT_INITIALIZED
  Cannot create EGL context: invalid display (last error: EGL_SUCCESS)
  ```

  I don't know if it's related, but googling around shows some webkitgtk
  hits on this error.

  The email contents are however clickable. They're just not rendered to
  screen (see attached file).

  Deleting the evolution folders from `~/.config`, `~/.cache` and
  `~/.local/share` does not help.

  Email accounts are all google, configured through gnome online
  accounts.

  Workaround #1
  -
  You can run the app from the command line with
  WEBKIT_DISABLE_COMPOSITING_MODE=1 evolution
  (Replace evolution with the name of the webkit app you are trying to use)

  Workaround #2
  -
  Log out.
  Select your name on the login screen.
  Click the gear button and choose Ubuntu on Xorg.
  Enter your password to finish logging in.

  
  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: evolution 3.44.0-1
  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: sway
  Date: Fri Mar 25 10:55:49 2022
  SourcePackage: evolution
  UpgradeStatus: Upgraded to jammy on 2022-03-01 (24 days ago)

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


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

[Desktop-packages] [Bug 1192795] Re: manpage says scripts are in XDG_DATA_DIR/session-migration/scripts but they aren't

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

** Changed in: session-migration (Ubuntu)
   Status: New => Confirmed

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

Title:
  manpage says scripts are in XDG_DATA_DIR/session-migration/scripts but
  they aren't

Status in session-migration package in Ubuntu:
  Confirmed

Bug description:
  According to the manpage[1], scripts are executable files located in
  XDG_DATA_DIR/session-migration/scripts.

  When I look in ~/.local/share/ I don't see a session-migration/
  directory but I do see several files:

  session_migration-gnome
  session_migration-gnome-classic
  session_migration-gnome-fallback
  session_migration-gnome-fallback-compiz
  session_migration-gnome-flashback
  session_migration-gnome-flashback-compiz
  session_migration-(null)
  session_migration-ubuntu
  session_migration-ubuntu2

  These files aren't marked as executable and aren't scripts.  I guess
  those files indicate that the scripts have been run.

  Recommendations
  1. Store those files in their own directory so that the root XDG_DATA_DIR 
directory isn't cluttered with them.
  2. Please update the manpage to explain what's going on here. I'm guessing 
that the script might be deleted after they are ran?

  [1] http://manpages.ubuntu.com/manpages/raring/man1/session-
  migration.1.html

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: session-migration 0.2
  ProcVersionSignature: Ubuntu 3.9.0-6.13-generic 3.9.6
  Uname: Linux 3.9.0-6-generic x86_64
  ApportVersion: 2.10.2-0ubuntu1
  Architecture: amd64
  Date: Wed Jun 19 23:20:45 2013
  InstallationDate: Installed on 2013-06-14 (5 days ago)
  InstallationMedia: Ubuntu-GNOME 13.10 "Saucy Salamander" - Alpha amd64 
(20130613)
  MarkForUpload: True
  SourcePackage: session-migration
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Desktop-packages] [Bug 1947210] Re: Firefox Snap can't copy&paste or drag&drop in Wayland

2022-03-29 Thread cesar

i install the ubuntu 22.04 last nite and firefox have a very bad problem
with the drag and drop, specially in customize toolbar... i cant arrange
nothing, and worst the icon of the extension, disappear, and the only
way to put again in place is reinstall the extension...  i think really,
install the esr version of firefox...

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

Title:
  Firefox Snap can't copy&paste or drag&drop in Wayland

Status in Mozilla Firefox:
  Confirmed
Status in firefox package in Ubuntu:
  Fix Released

Bug description:
  I just upgraded to 21.10 Impish which supplies Firefox 93.0-1 via
  snap. I could not copy and paste to and from the browser. I logged out
  of Wayland and into Xorg and copy & paste works.

  Already reported at
  https://bugzilla.mozilla.org/show_bug.cgi?id=1729901 so it's a known
  issue.

  I wanted to report it here so it gets into the Impish release notes or
  wherever along with the workaround.

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


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

[Desktop-packages] [Bug 1927100] Re: Slow file dialogs, open and save

2022-03-29 Thread buck2202

This sounds fine to me--sorry that it has ended up this way, but thanks
for offering this compromise.

Let me just first confirm that I can still reproduce it on my Mint
install--I've been running from my locally-patched gvfs since October,
so I should be sure it hasn't changed with any subsequent Mint/Nemo
updates. I'll report back after that.

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

Title:
  Slow file dialogs, open and save

Status in gvfs package in Ubuntu:
  Fix Released
Status in gvfs source package in Focal:
  Incomplete

Bug description:
  [Description/Impact]
  glib GFileMonitors can cause deadlocks if not explicitly cancelled before 
unref-ing (as of Dec 2021; see 
https://gitlab.gnome.org/GNOME/glib/-/issues/1941). In gvfs <1.46.2, 
gvfsd-trash can cause this deadlock, leading to 25s delays in spawning gtk+ 
dialogs system-wide. The best userspace workaround is explicitly pkill-ing 
gvfsd-trash at a sometimes frequent interval.

  This issue was reported and fixed in gvfs
  issue: https://gitlab.gnome.org/GNOME/gvfs/-/issues/485
  commit: 
https://gitlab.gnome.org/GNOME/gvfs/-/commit/dc21a0948bcbe8a6d79d674bd1e4d63ded57d340
  merge: https://gitlab.gnome.org/GNOME/gvfs/-/merge_requests/96

  [Test Case]
  To my knowledge, there is not a 100% reproducer for gvfs from userspace as 
this is a probable lock-ordering issue in lower-level code. 
https://gitlab.gnome.org/GNOME/glib/-/issues/1941 contains a reproducer for the 
underlying glib issue.

  User reports of gvfsd-trash manifesting this deadlock exist for Focal and 
Focal-based distributions, and it has been acknowledged and worked-around in 
gvfs. See:
  https://forums.linuxmint.com/viewtopic.php?f=47&t=328966 (Linux Mint forums)
  https://github.com/linuxmint/nemo/issues/2497 (Linux Mint nemo -- file 
manager)
  https://gitlab.gnome.org/GNOME/gvfs/-/issues/485 (gvfs bug report, includes 
diagnosis and stacktrace showing the gvfsd-trash thread)

  The code change patched-in here has propagated to various other projects. See:
  https://bugs.launchpad.net/ubuntu/+source/libxmlb/+bug/1890313
  https://github.com/fwupd/fwupd/issues/2350

  [Regression Potential]
  This patch explicitly cancels GFileMonitors before "unreferencing" them to 
workaround a known glib issue. Absent any currently-unknown issues with the 
GFileMonitor framework, code added by this patch should be entirely within 
valid usage of GFileMonitors, is already present in gvfs releases in wide 
distribution, and, at worst, should become superfluous if/when the underlying 
glib issue is fixed.

  In the event that gvfsd-trash had some (currently unknown)
  mismanagement of its file watchers, it's possible that attempting to
  cancel an invalid monitor might behave differently than unref-ing it
  (which was already happening), but, this scenario would likely be bad
  either way.

  [Original Description]

  On Ubuntu Mate 20.04.

  Sometime the Open and Save dialogs in GTK applications will over 20
  seconds to display.

  I found https://gitlab.gnome.org/GNOME/gvfs/-/issues/485 , which
  suggested this due to gvfsd-trash, and running `killall gvfsd-trash`
  which does temporary solve the problem.

  The issue is apparently fixed in gvfs 1.46.2

  Please could 1.46.2 or the fix
  https://gitlab.gnome.org/GNOME/gvfs/-/merge_requests/96 be backported
  to Ubuntu 20.04

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


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

[Desktop-packages] [Bug 1966571] Re: libva error: /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so init failed

2022-03-29 Thread Joe Barnett

seeing the same behavior with the -non-free version too, does it need a
separate rebuild?

** Also affects: intel-media-driver-non-free (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  libva error: /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so init
  failed

Status in intel-media-driver package in Ubuntu:
  Fix Committed
Status in intel-media-driver-non-free package in Ubuntu:
  New
Status in mesa package in Ubuntu:
  Invalid

Bug description:
  I noticed that it upgraded mesa to 22.x and now video acceleration is
  not working due to:

  ❯ vainfo 
  libva info: VA-API version 1.14.0
  libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so
  libva info: Found init function __vaDriverInit_1_14
  libva error: /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so init failed
  libva info: va_openDriver() returns 1
  libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so
  libva info: Found init function __vaDriverInit_1_10
  libva error: /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so init failed
  libva info: va_openDriver() returns -1
  vaInitialize failed with error code -1 (unknown libva error),exit
  ~/Desktop 
  ❯ inxi -G
  Graphics:
Device-1: Intel driver: i915 v: kernel
Device-2: Generalplus GENERAL WEBCAM type: USB
  driver: snd-usb-audio,uvcvideo
Display: x11 server: X.Org v: 1.21.1.3 driver: X: loaded: modesetting
  unloaded: fbdev,vesa gpu: i915 resolution: 3840x2160~60Hz
OpenGL: renderer: Mesa Intel UHD Graphics P630 (CML GT2)
  v: 4.6 Mesa 22.0.0

  I tried rebuilding the i965-va-driver, and it's still the same.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: mesa-vdpau-drivers 22.0.0-0ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Uname: Linux 5.15.0-23-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Mar 27 10:37:41 2022
  DistUpgraded: 2022-01-18 23:59:55,390 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
  DistroCodename: jammy
  DistroVariant: ubuntu
  DkmsStatus:
   rtl88x2bu/5.8.7.1, 5.15.0-18-generic, x86_64: installed
   rtl88x2bu/5.8.7.1, 5.15.0-22-generic, x86_64: installed
   rtl88x2bu/5.8.7.1, 5.15.0-23-generic, x86_64: installed
   rtl88x2bu/5.8.7.1, 5.17.0-xanmod1, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Device [8086:9bc6] (rev 05) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Device [1043:8694]
  InstallationDate: Installed on 2021-10-05 (172 days ago)
  InstallationMedia: Ubuntu-Server 21.10 "Impish Indri" - Beta amd64 (20211004)
  MachineType: ASUS System Product Name
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_PH.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-23-generic 
root=UUID=018d5b69-accd-451b-a6f7-2027f791ea0e ro quiet splash vt.handoff=7
  SourcePackage: mesa
  UpgradeStatus: Upgraded to jammy on 2022-01-18 (67 days ago)
  dmi.bios.date: 07/08/2021
  dmi.bios.release: 23.1
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2301
  dmi.board.asset.tag: Default string
  dmi.board.name: Pro WS W480-ACE
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2301:bd07/08/2021:br23.1:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnProWSW480-ACE:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.110-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.0-0ubuntu2
  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/intel-media-driver/+bug/1966571/+subscriptions


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

[Desktop-packages] [Bug 1782984] Re: Assertion `!xcb_xlib_threads_sequence_lost' failed with multiple applications

2022-03-29 Thread Timo Aaltonen

or do as advised in comment #106

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

Title:
  Assertion `!xcb_xlib_threads_sequence_lost' failed with multiple
  applications

Status in libx11 package in Ubuntu:
  Fix Released
Status in libx11 source package in Bionic:
  Fix Committed
Status in libx11 source package in Focal:
  Fix Committed
Status in libx11 source package in Groovy:
  Won't Fix

Bug description:
  [Impact]

  There is a race in libx11 causing applications to randomly abort. It's
  not trivial to reproduce, but there are enough duplicates that this
  deserves an SRU to bionic & focal.

  [Fix]

  Backport a commit from upstream:

  From dbb55e1a5e82870466b095097d9e46046680ec25 Mon Sep 17 00:00:00 2001
  From: Frediano Ziglio 
  Date: Wed, 29 Jan 2020 09:06:54 +
  Subject: [PATCH] Fix poll_for_response race condition

  In poll_for_response is it possible that event replies are skipped
  and a more up to date message reply is returned.
  This will cause next poll_for_event call to fail aborting the program.

  This was proved using some slow ssh tunnel or using some program
  to slow down server replies (I used a combination of xtrace and strace).

  How the race happens:
  - program enters into poll_for_response;
  - poll_for_event is called but the server didn't still send the reply;
  - pending_requests is not NULL because we send a request (see call
to  append_pending_request in _XSend);
  - xcb_poll_for_reply64 is called from poll_for_response;
  - xcb_poll_for_reply64 will read from server, at this point
server reply with an event (say sequence N) and the reply to our
last request (say sequence N+1);
  - xcb_poll_for_reply64 returns the reply for the request we asked;
  - last_request_read is set to N+1 sequence in poll_for_response;
  - poll_for_response returns the response to the request;
  - poll_for_event is called (for instance from another poll_for_response);
  - event with sequence N is retrieved;
  - the N sequence is widen, however, as the "new" number computed from
last_request_read is less than N the number is widened to N + 2^32
(assuming last_request_read is still contained in 32 bit);
  - poll_for_event enters the nested if statement as req is NULL;
  - we compare the widen N (which now does not fit into 32 bit) with
request (which fits into 32 bit) hitting the throw_thread_fail_assert.

  To avoid the race condition and to avoid the sequence to go back
  I check again for new events after getting the response and
  return this last event if present saving the reply to return it
  later.

  To test the race and the fix it's helpful to add a delay (I used a
  "usleep(5000)") before calling xcb_poll_for_reply64.

  Original patch written by Frediano Ziglio, see
  https://gitlab.freedesktop.org/xorg/lib/libx11/-/merge_requests/34

  Reworked primarily for readability by Peter Hutterer, see
  https://gitlab.freedesktop.org/xorg/lib/libx11/-/merge_requests/53

  Signed-off-by: Peter Hutterer 

  bionic needs another commit so that the real fix applies.

  [Test case]

  It's a race condition, the SRU sponsor (tjaalton) does not have a test
  case for this, but the bug subscribers seem to.

  
  [Where things could go wrong]

  In theory there might be a case where a race still happens, but since
  this has been upstream for a year now with no follow-up commits, it's
  safe to assume that there are no regressions.

  
  --

  STEPS TO REPRODUCE
  ==
  The bug seems to occur when clicking on a file or folder. It is random and 
difficult to provide clear steps to reproduce. It is, however, a common 
situation.

  EXPECTED RESULTS
  
  pcmanfm works without problem.

  ACTUAL RESULTS
  ==
  All pcmanfm windows become unresponsive, though background processes (e.g. 
copying) may continue without problem. with the same error message in 
~/.cache/lxsession/LXDE/run.log:

  [xcb] Unknown sequence number while processing queue
  [xcb] Most likely this is a multi-threaded client and XInitThreads has not 
been called
  [xcb] Aborting, sorry about that.
  pcmanfm: xcb_io.c:259: poll_for_event: Assertion 
`!xcb_xlib_threads_sequence_lost' failed.
  ** Message: 19:58:49.267: app.vala:130: pcmanfm exit with this type of exit: 6
  ** Message: 19:58:49.268: app.vala:148: Exit not normal, try to reload

  (note the timestamp on the message will vary)

  AFFECTED VERSIONS
  =
  1.2.5-3ubuntu1
  NOT 1.2.4-1ubuntu0.1

  UPSTREAM BUG
  
  https://sourceforge.net/p/pcmanfm/bugs/1089/

  ADDITIONAL NOTES
  
  Other GTK2 file managers (e.g. Thunar) and applications (e.g. GIMP, Leafpad) 
seem to have the same problems. This is probably at least rooted in a GTK2 bug:
  https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1808710

  To further assert this, note that there i

[Desktop-packages] [Bug 1915910] Re: evince does not print (apparmor, pxgsettings)

2022-03-29 Thread jbfoley

Same issue, 21,10 using Unity, and the apparmor workaround fixes it for
me as well.

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

Title:
  evince does not print (apparmor, pxgsettings)

Status in evince package in Ubuntu:
  Confirmed
Status in libproxy package in Ubuntu:
  Confirmed
Status in evince package in Debian:
  New

Bug description:
  audit: type=1400 audit(1613557537.646:81): apparmor="DENIED"
  operation="exec" profile="/usr/bin/evince"
  name="/usr/lib/x86_64-linux-gnu/libproxy/0.4.17/pxgsettings" pid=3500
  comm="sh" requested_mask="x" denied_mask="x" fsuid=1000 ouid=0

  It seems that evince has no rights to print if I understand this
  correctly

  Printing the same pdf-file from the same origin/folder works with
  OCULAR

  The error is reproduceable

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


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

[Desktop-packages] [Bug 1782984] Re: Assertion `!xcb_xlib_threads_sequence_lost' failed with multiple applications

2022-03-29 Thread Timo Aaltonen

echo 'deb http://archive.ubuntu.com/ubuntu/ focal-proposed main restricted' >> 
/etc/apt/sources.list
apt update
apt install libx11-6

verify with 'apt-cache policy libx11-6' that you have the correct
version (from proposed), and run your tests.

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

Title:
  Assertion `!xcb_xlib_threads_sequence_lost' failed with multiple
  applications

Status in libx11 package in Ubuntu:
  Fix Released
Status in libx11 source package in Bionic:
  Fix Committed
Status in libx11 source package in Focal:
  Fix Committed
Status in libx11 source package in Groovy:
  Won't Fix

Bug description:
  [Impact]

  There is a race in libx11 causing applications to randomly abort. It's
  not trivial to reproduce, but there are enough duplicates that this
  deserves an SRU to bionic & focal.

  [Fix]

  Backport a commit from upstream:

  From dbb55e1a5e82870466b095097d9e46046680ec25 Mon Sep 17 00:00:00 2001
  From: Frediano Ziglio 
  Date: Wed, 29 Jan 2020 09:06:54 +
  Subject: [PATCH] Fix poll_for_response race condition

  In poll_for_response is it possible that event replies are skipped
  and a more up to date message reply is returned.
  This will cause next poll_for_event call to fail aborting the program.

  This was proved using some slow ssh tunnel or using some program
  to slow down server replies (I used a combination of xtrace and strace).

  How the race happens:
  - program enters into poll_for_response;
  - poll_for_event is called but the server didn't still send the reply;
  - pending_requests is not NULL because we send a request (see call
to  append_pending_request in _XSend);
  - xcb_poll_for_reply64 is called from poll_for_response;
  - xcb_poll_for_reply64 will read from server, at this point
server reply with an event (say sequence N) and the reply to our
last request (say sequence N+1);
  - xcb_poll_for_reply64 returns the reply for the request we asked;
  - last_request_read is set to N+1 sequence in poll_for_response;
  - poll_for_response returns the response to the request;
  - poll_for_event is called (for instance from another poll_for_response);
  - event with sequence N is retrieved;
  - the N sequence is widen, however, as the "new" number computed from
last_request_read is less than N the number is widened to N + 2^32
(assuming last_request_read is still contained in 32 bit);
  - poll_for_event enters the nested if statement as req is NULL;
  - we compare the widen N (which now does not fit into 32 bit) with
request (which fits into 32 bit) hitting the throw_thread_fail_assert.

  To avoid the race condition and to avoid the sequence to go back
  I check again for new events after getting the response and
  return this last event if present saving the reply to return it
  later.

  To test the race and the fix it's helpful to add a delay (I used a
  "usleep(5000)") before calling xcb_poll_for_reply64.

  Original patch written by Frediano Ziglio, see
  https://gitlab.freedesktop.org/xorg/lib/libx11/-/merge_requests/34

  Reworked primarily for readability by Peter Hutterer, see
  https://gitlab.freedesktop.org/xorg/lib/libx11/-/merge_requests/53

  Signed-off-by: Peter Hutterer 

  bionic needs another commit so that the real fix applies.

  [Test case]

  It's a race condition, the SRU sponsor (tjaalton) does not have a test
  case for this, but the bug subscribers seem to.

  
  [Where things could go wrong]

  In theory there might be a case where a race still happens, but since
  this has been upstream for a year now with no follow-up commits, it's
  safe to assume that there are no regressions.

  
  --

  STEPS TO REPRODUCE
  ==
  The bug seems to occur when clicking on a file or folder. It is random and 
difficult to provide clear steps to reproduce. It is, however, a common 
situation.

  EXPECTED RESULTS
  
  pcmanfm works without problem.

  ACTUAL RESULTS
  ==
  All pcmanfm windows become unresponsive, though background processes (e.g. 
copying) may continue without problem. with the same error message in 
~/.cache/lxsession/LXDE/run.log:

  [xcb] Unknown sequence number while processing queue
  [xcb] Most likely this is a multi-threaded client and XInitThreads has not 
been called
  [xcb] Aborting, sorry about that.
  pcmanfm: xcb_io.c:259: poll_for_event: Assertion 
`!xcb_xlib_threads_sequence_lost' failed.
  ** Message: 19:58:49.267: app.vala:130: pcmanfm exit with this type of exit: 6
  ** Message: 19:58:49.268: app.vala:148: Exit not normal, try to reload

  (note the timestamp on the message will vary)

  AFFECTED VERSIONS
  =
  1.2.5-3ubuntu1
  NOT 1.2.4-1ubuntu0.1

  UPSTREAM BUG
  
  https://sourceforge.net/p/pcmanfm/bugs/1089/

  ADDITIONAL NOTES
  
  Other GTK2 file managers (e.g. Thunar) and application

[Desktop-packages] [Bug 1965558] Re: Cannot change wallpaper by right-clicking image in dark theme

This bug was fixed in the package nautilus - 1:42.0-1ubuntu2

---
nautilus (1:42.0-1ubuntu2) jammy; urgency=medium

  * Cherry-pick patch to set the dark wallpaper when setting the
desktop wallpaper (LP: #1965558)

 -- Jeremy Bicha   Fri, 25 Mar 2022 09:55:21 -0400

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

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

Title:
  Cannot change wallpaper by right-clicking image in dark theme

Status in nautilus package in Ubuntu:
  Fix Released
Status in nautilus source package in Jammy:
  Fix Released

Bug description:
  With the light theme enabled, you can set the desktop wallpaper by
  right-clicking on an image file's icon in the file manager and
  selecting "Set As Wallpaper". When you do this the Desktop wallpaper
  changes straight away.

  Now change to dark theme and repeat the above steps. The wallpaper
  never changes. You can however change the wallpaper fine using Gnome
  settings -> Appearance.

  Thanks
  Nick

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-control-center 1:41.4-1ubuntu6
  ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19
  Uname: Linux 5.15.0-22-generic x86_64
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar 18 16:14:38 2022
  InstallationDate: Installed on 2022-02-28 (18 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220228)
  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/nautilus/+bug/1965558/+subscriptions


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

[Desktop-packages] [Bug 1962761] Re: nautilus crashed with SIGSEGV in gtk_widget_get_ancestor()

This bug was fixed in the package nautilus - 1:42.0-1ubuntu2

---
nautilus (1:42.0-1ubuntu2) jammy; urgency=medium

  * Cherry-pick patch to set the dark wallpaper when setting the
desktop wallpaper (LP: #1965558)

 -- Jeremy Bicha   Fri, 25 Mar 2022 09:55:21 -0400

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

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

Title:
  nautilus crashed with SIGSEGV in gtk_widget_get_ancestor()

Status in nautilus package in Ubuntu:
  Fix Released

Bug description:
  It's part of a chain of bugs that come one after another as I try to
  report each one of them.

  Never saw this behavior before

  ProblemType: Crash
  DistroRelease: Ubuntu 22.04
  Package: nautilus 1:42~beta-1ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12
  Uname: Linux 5.15.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu78
  Architecture: amd64
  CasperMD5CheckResult: pass
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Feb 25 20:32:37 2022
  ExecutablePath: /usr/bin/nautilus
  GsettingsChanges:
   b'org.gnome.nautilus.icon-view' b'default-zoom-level' b"'larger'"
   b'org.gnome.nautilus.window-state' b'maximized' b'true'
  InstallationDate: Installed on 2022-01-03 (58 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211230)
  ProcCmdline: /usr/bin/nautilus --gapplication-service
  ProcEnviron:
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
   PATH=(custom, no user)
   LANG=ro_RO.UTF-8
  SegvAnalysis:
   Segfault happened at: 0x7f5f445b49a8 :   cmp
%rax,(%rbx)
   PC (0x7f5f445b49a8) ok
   source "%rax" ok
   destination "(%rbx)" (0x71818181c7808080) not located in a known VMA region 
(needed writable region)!
  SegvReason: writing unknown VMA
  Signal: 11
  SourcePackage: nautilus
  StacktraceTop:
   gtk_widget_get_ancestor () at /lib/x86_64-linux-gnu/libgtk-3.so.0
   ()
   g_closure_invoke () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0
   () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_signal_emit_valist () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: nautilus crashed with SIGSEGV in gtk_widget_get_ancestor()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  separator:
   
  usr_lib_nautilus:
   evince41.3-3
   file-roller   3.41.90-1
   nautilus-extension-gnome-terminal 3.43.90-1ubuntu1
   nautilus-share0.7.3-2ubuntu4

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


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

[Desktop-packages] [Bug 1966979] [NEW] Firefox says one of it's files is in use after new installation

2022-03-29 Thread Luzemário

Public bug reported:

Steps to reproduce:

- Make a full backup of Firefox user data;
- rm -rf /home//.mozilla;
- apt purge firefox;
- apt install firefox;

On first run, Firefox Says "The bookmarks and history system will not be
functional because one of Firefox's files is in use by another
application. Some security software can cause this problem"

Trying to enter sync is not possible because Firefox says coookies are
disabled, despite it being enabled.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: firefox 98.0.2+build1-0ubuntu0.20.04.1
ProcVersionSignature: Ubuntu 5.13.0-37.42~20.04.1-generic 5.13.19
Uname: Linux 5.13.0-37-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
AddonCompatCheckDisabled: False
ApportVersion: 2.20.11-0ubuntu27.21
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  luzemario   1437 F pulseaudio
 /dev/snd/controlC1:  luzemario   1437 F pulseaudio
BuildID: 20220322144853
CasperMD5CheckResult: skip
Channel: Unavailable
CurrentDesktop: KDE
Date: Tue Mar 29 12:48:28 2022
DefaultProfileExtensions: extensions.sqlite corrupt or missing
DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
DefaultProfileLocales: extensions.sqlite corrupt or missing
DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:364
DefaultProfileThemes: extensions.sqlite corrupt or missing
ExecutablePath: /usr/lib/firefox/firefox
ForcedLayersAccel: False
InstallationDate: Installed on 2021-01-23 (429 days ago)
InstallationMedia: Kubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
IpRoute:
 default via 192.168.1.1 dev enp4s0 proto static metric 100 
 169.254.0.0/16 dev virbr0 scope link metric 1000 
 192.168.1.0/24 dev enp4s0 proto kernel scope link src 192.168.1.20 metric 100 
 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1
ProcEnviron:
 LANGUAGE=pt_BR:en_US
 PATH=(custom, user)
 XDG_RUNTIME_DIR=
 LANG=pt_BR.UTF-8
 SHELL=/bin/bash
Profile0Extensions: extensions.sqlite corrupt or missing
Profile0IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
Profile0Locales: extensions.sqlite corrupt or missing
Profile0PrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:364
Profile0PrefSources: prefs.js
Profile0Themes: extensions.sqlite corrupt or missing
Profiles:
 Profile1 (Default) - LastVersion=None/None (Out of date)
 Profile0 - LastVersion=98.0.2/20220322144853 (In use)
RunningIncompatibleAddons: False
SourcePackage: firefox
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/18/2016
dmi.bios.release: 8.15
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0502
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: M5A78L-M PLUS/USB3
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0502:bd11/18/2016:br8.15:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM5A78L-MPLUS/USB3:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:skuToBeFilledByO.E.M.:
dmi.product.family: To Be Filled By O.E.M.
dmi.product.name: System Product Name
dmi.product.sku: To Be Filled By O.E.M.
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer

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


** Tags: amd64 apport-bug focal

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

Title:
  Firefox says one of it's files is in use after new installation

Status in firefox package in Ubuntu:
  New

Bug description:
  Steps to reproduce:

  - Make a full backup of Firefox user data;
  - rm -rf /home//.mozilla;
  - apt purge firefox;
  - apt install firefox;

  On first run, Firefox Says "The bookmarks and history system will not
  be functional because one of Firefox's files is in use by another
  application. Some security software can cause this problem"

  Trying to enter sync is not possible because Firefox says coookies are
  disabled, despite it being enabled.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: firefox 98.0.2+build1-0ubuntu0.20.04.1
  ProcVersionSignature: Ubuntu 5.13.0-37.42~20.04.1-generic 5.13.19
  Uname: Linux 5.13.0-37-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  luzemario   1437 F pulseaudio
   /dev/snd/controlC1:  luzemario   1437 F pulseaudio
  BuildID: 20220322144

[Desktop-packages] [Bug 1966065] Re: firefox package stealh installs snapd via apt not a DEB

2022-03-29 Thread rec9140

This is not the process for apt, apt-get, synaptic. 
If user selects package via these then it should install a DEB based package.

If the USER selects to install via what ever programs/tools exist for
snaps etc. then its should follow suit to respect that format and
install a snap or what ever.

USER CHOICE SHOULD BE RESPECTED in apt/apt-get/syanptic to use DEB.

This is STEALTHY AND SNEAKS In a DIFFERING PACKAGE format via a DEB.
Which is not correct, or warranted.

Tools should respect the packaging format that is being used via the
tool being used, apt etc. means the user wants a DEB, not some other
format.

This is valid security violation.

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

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

Title:
  firefox package stealh installs snapd via apt not a DEB

Status in firefox package in Ubuntu:
  Confirmed

Bug description:
   What happened instead
  Upgrades or new installs for *bunutus on 22.04 Jammy Jellyfish install snapd 
when using apt to install or update the firefox browser. 

  For those which have removed and purged snapd, the new package will
  stealth sneak attack a snapd setup in place of a DEB based, unless
  snapd is specifically blacklisted and blocked.

  Should not use snpad for installs which have been done via apt to
  install a DEB package by USER CHOICE OVERRIDING the current
  development default of installing a snapd based setup.

   What you expected to happen
  Should install a DEB package and install the browser via the method the USER 
DESIRES. 

  Package management should respect USER CHOICE AND DESIRES to USE THE
  PACKAGING OF ***USER*** CHOICE if via apt, then DEB should be used, be
  it firefox or any other package. If the USER DESIRES/CHOOSES to use a
  snap based version via that packaging system/tools then go with that.

  apt tools including synaptic should NOT sneak or even change packaging
  methodology ie: snap in place of a DEB when using
  apt/synaptic/discover/muon etc. tools.

  Description:Ubuntu Jammy Jellyfish (development branch)
  Release:22.04

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


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

[Desktop-packages] [Bug 1958267] Re: "Connection failed" for WPA Enterprise network eduroam

2022-03-29 Thread Alexander Browne

I've opened a ticket with my University's IT dept with the suggestion.

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

Title:
  "Connection failed" for WPA Enterprise network eduroam

Status in wpa package in Ubuntu:
  Confirmed
Status in wpa source package in Jammy:
  Confirmed

Bug description:
  With the current jammy version of wpasupplicant (2:2.10-1), I cannot
  connect to the WPA Enterprise network eduroam, which is used by
  Universities worldwide. I get a "Connection failed" message or a
  request to re-enter the password.

  - I've re-tried the credentials: no fix ;-)

  - Tried a 21.10 live session on the same machine: works fine!

  - Manually downgraded wpasupplicant to the impish version
  (2:2.9.0-21build1): connected normally.

  - Upgraded wpasupplicant to the latest version: fails to connect
  again.

  
  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: wpasupplicant 2:2.10-1
  ProcVersionSignature: Ubuntu 5.15.0-17.17-generic 5.15.12
  Uname: Linux 5.15.0-17-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu75
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 18 09:56:23 2022
  InstallationDate: Installed on 2021-11-30 (48 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211130)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: wpa
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Desktop-packages] [Bug 1958267] Re: "Connection failed" for WPA Enterprise network eduroam

2022-03-29 Thread Hans Schulz

@Sebastian, I have this issue with the EAP-TLS protected network of at
work, its not eduroam. I'll see if I can reach any of the network
admins.

However, I doubt that the servers are configured to use insecure
methods; there were lots of security related changes done in the past
year to the wifi infrastructure, including the roll out of EAP-TLS over
PEAP. There is basically zero legacy support in this wifi currently.

Can you tell me how to check what insecure configuration is actually the
problem here?

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

Title:
  "Connection failed" for WPA Enterprise network eduroam

Status in wpa package in Ubuntu:
  Confirmed
Status in wpa source package in Jammy:
  Confirmed

Bug description:
  With the current jammy version of wpasupplicant (2:2.10-1), I cannot
  connect to the WPA Enterprise network eduroam, which is used by
  Universities worldwide. I get a "Connection failed" message or a
  request to re-enter the password.

  - I've re-tried the credentials: no fix ;-)

  - Tried a 21.10 live session on the same machine: works fine!

  - Manually downgraded wpasupplicant to the impish version
  (2:2.9.0-21build1): connected normally.

  - Upgraded wpasupplicant to the latest version: fails to connect
  again.

  
  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: wpasupplicant 2:2.10-1
  ProcVersionSignature: Ubuntu 5.15.0-17.17-generic 5.15.12
  Uname: Linux 5.15.0-17-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu75
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 18 09:56:23 2022
  InstallationDate: Installed on 2021-11-30 (48 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211130)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: wpa
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Desktop-packages] [Bug 1871538] Autopkgtest regression report (systemd/248.3-1ubuntu8.4)

2022-03-29 Thread Ubuntu SRU Bot

All autopkgtests for the newly accepted systemd (248.3-1ubuntu8.4) for impish 
have finished running.
The following regressions have been reported in tests triggered by the package:

systemd/248.3-1ubuntu8.4 (arm64, ppc64el)
debspawn/0.5.0-1 (s390x)
diaspora-installer/0.7.15.0+debian1 (s390x, arm64)
swupdate/2020.11-2 (ppc64el)
snapd/2.54.3+21.10.1ubuntu0.2 (s390x, ppc64el)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/impish/update_excuses.html#systemd

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  dbus timeout-ed during an upgrade, taking services down including gdm

Status in D-Bus:
  Unknown
Status in systemd:
  New
Status in accountsservice package in Ubuntu:
  Invalid
Status in dbus package in Ubuntu:
  Invalid
Status in gnome-shell package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Fix Released
Status in accountsservice source package in Focal:
  Invalid
Status in dbus source package in Focal:
  Invalid
Status in gnome-shell source package in Focal:
  Invalid
Status in systemd source package in Focal:
  Fix Committed
Status in accountsservice source package in Groovy:
  Invalid
Status in dbus source package in Groovy:
  Invalid
Status in gnome-shell source package in Groovy:
  Invalid
Status in accountsservice source package in Hirsute:
  Invalid
Status in dbus source package in Hirsute:
  Won't Fix
Status in gnome-shell source package in Hirsute:
  Invalid
Status in accountsservice source package in Impish:
  Invalid
Status in dbus source package in Impish:
  Invalid
Status in gnome-shell source package in Impish:
  Invalid
Status in systemd source package in Impish:
  Fix Committed
Status in accountsservice source package in Jammy:
  Invalid
Status in dbus source package in Jammy:
  Invalid
Status in gnome-shell source package in Jammy:
  Invalid
Status in systemd source package in Jammy:
  Fix Released

Bug description:
  [Impact]

   * There's currently a deadlock between PID 1 and dbus-daemon: in some
  cases dbus-daemon will do NSS lookups (which are blocking) at the same
  time PID 1 synchronously blocks on some call to dbus-daemon (e.g. 
`GetConnectionUnixUser` DBus call). Let's break
  that by setting SYSTEMD_NSS_DYNAMIC_BYPASS=1 env var for dbus-daemon,
  which will disable synchronously blocking varlink calls from nss-systemd
  to PID 1.

   * This can lead to delayed boot times

   * It can also lead to dbus-daemon being killed/re-started, taking
  down other services with it, like GDM, killing user sessions on the
  way (e.g. on installing updates)

  [Test Plan]

   * This bug is really hard to reproduce, as can be seen from the
  multi-year long discussion at
  https://github.com/systemd/systemd/issues/15316

   * Canonical's CPC team has the ability to reproduce  this issue (with
  a relatively high probability) in their Azure test environment, due to
  the specific setup they are using

   * So our test plan is to ask CPC (@gjolly) for confirmation if the
  issue is fixed.

  [Where problems could occur]

   * This fix touches the communication between systemd and dbus daemon,
  especially the NSS lookup, so if something is broken the (user-)name
  resolution could be broken.

   * As a workaround dbus-daemon could be replaced by dbus-broker, which
  never showed this issue or the behaviour could be changed back by
  using the `SYSTEMD_NSS_DYNAMIC_BYPASS` env variable, like this:

  #/etc/systemd/system/dbus.service.d/override.conf
  [Service]
  Environment=SYSTEMD_NSS_DYNAMIC_BYPASS=0

  [Other Info]
   
   * Fixed upstream (v251) in https://github.com/systemd/systemd/pull/22552

  
  === Original Description ===


  
  This morning I found my computer on the login screen.
  But not the one of the screen log, no a new one - so something must have 
crashed.

  Logging in again confirmed that all apps were gone and the gnome shell
  was brought down what seems like triggered by a background update o
  accountsservice.

  As always things are not perfectly clear :-/
  The following goes *back* in time through my logs one by one.

  Multiple apps crashed at 06:09, but we will find later that this is a follow 
on issue of the underlying gnome/X/... recycling.
  -rw-r-  1 paelzer  whoopsie 52962868 Apr  8 06:09 
_usr_bin_konversation.1000.crash
  -rw-r-  1 paelzer  whoopsie   986433 Apr  8 06:09 
_usr_lib_x86_64-linux-gnu_libexec_drkonqi.1000.crash

  rdkit was failing fast and giving up (that will be a different bug, it just 
seems broken on my system):
  Apr 08 06:10:13 Keschdeichel systemd[1]: Started RealtimeKit Scheduling 
Policy Service.
  Apr 08

[Desktop-packages] [Bug 1958267] Re: "Connection failed" for WPA Enterprise network eduroam

2022-03-29 Thread Sebastien Bacher

@Hans, @Alexander, could any of you contact one of the eduroam admins to
report the issue? Ideally they would just fix their servers, currently
the fact that it works under windows doesn't resolve the fact that they
are using an insecure configuration and should be fixed

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

Title:
  "Connection failed" for WPA Enterprise network eduroam

Status in wpa package in Ubuntu:
  Confirmed
Status in wpa source package in Jammy:
  Confirmed

Bug description:
  With the current jammy version of wpasupplicant (2:2.10-1), I cannot
  connect to the WPA Enterprise network eduroam, which is used by
  Universities worldwide. I get a "Connection failed" message or a
  request to re-enter the password.

  - I've re-tried the credentials: no fix ;-)

  - Tried a 21.10 live session on the same machine: works fine!

  - Manually downgraded wpasupplicant to the impish version
  (2:2.9.0-21build1): connected normally.

  - Upgraded wpasupplicant to the latest version: fails to connect
  again.

  
  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: wpasupplicant 2:2.10-1
  ProcVersionSignature: Ubuntu 5.15.0-17.17-generic 5.15.12
  Uname: Linux 5.15.0-17-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu75
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 18 09:56:23 2022
  InstallationDate: Installed on 2021-11-30 (48 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211130)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: wpa
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Desktop-packages] [Bug 1958267] Re: "Connection failed" for WPA Enterprise network eduroam

2022-03-29 Thread Alexander Browne

The workaround also does work for me. (For the record, I appended those
lines at the end of the config file.)

I see the openssl bug is marked wontfix. I think this is unfortunate,
since it means that eduroam (maybe poorly configured, but still) will
work out of the box for Windows and Mac (and Android and iOS) but not
Ubuntu 22.10 LTS.

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

Title:
  "Connection failed" for WPA Enterprise network eduroam

Status in wpa package in Ubuntu:
  Confirmed
Status in wpa source package in Jammy:
  Confirmed

Bug description:
  With the current jammy version of wpasupplicant (2:2.10-1), I cannot
  connect to the WPA Enterprise network eduroam, which is used by
  Universities worldwide. I get a "Connection failed" message or a
  request to re-enter the password.

  - I've re-tried the credentials: no fix ;-)

  - Tried a 21.10 live session on the same machine: works fine!

  - Manually downgraded wpasupplicant to the impish version
  (2:2.9.0-21build1): connected normally.

  - Upgraded wpasupplicant to the latest version: fails to connect
  again.

  
  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: wpasupplicant 2:2.10-1
  ProcVersionSignature: Ubuntu 5.15.0-17.17-generic 5.15.12
  Uname: Linux 5.15.0-17-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu75
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 18 09:56:23 2022
  InstallationDate: Installed on 2021-11-30 (48 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211130)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: wpa
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Desktop-packages] [Bug 1966571] Re: libva error: /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so init failed

2022-03-29 Thread Sebastien Bacher

@Lennart, thanks for the information, I uploaded a rebuild now, it's a
bit disturbing that it is needed though

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

** Changed in: intel-media-driver (Ubuntu)
   Status: Confirmed => Fix Committed

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

Title:
  libva error: /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so init
  failed

Status in intel-media-driver package in Ubuntu:
  Fix Committed
Status in mesa package in Ubuntu:
  Invalid

Bug description:
  I noticed that it upgraded mesa to 22.x and now video acceleration is
  not working due to:

  ❯ vainfo 
  libva info: VA-API version 1.14.0
  libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so
  libva info: Found init function __vaDriverInit_1_14
  libva error: /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so init failed
  libva info: va_openDriver() returns 1
  libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so
  libva info: Found init function __vaDriverInit_1_10
  libva error: /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so init failed
  libva info: va_openDriver() returns -1
  vaInitialize failed with error code -1 (unknown libva error),exit
  ~/Desktop 
  ❯ inxi -G
  Graphics:
Device-1: Intel driver: i915 v: kernel
Device-2: Generalplus GENERAL WEBCAM type: USB
  driver: snd-usb-audio,uvcvideo
Display: x11 server: X.Org v: 1.21.1.3 driver: X: loaded: modesetting
  unloaded: fbdev,vesa gpu: i915 resolution: 3840x2160~60Hz
OpenGL: renderer: Mesa Intel UHD Graphics P630 (CML GT2)
  v: 4.6 Mesa 22.0.0

  I tried rebuilding the i965-va-driver, and it's still the same.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: mesa-vdpau-drivers 22.0.0-0ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Uname: Linux 5.15.0-23-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Mar 27 10:37:41 2022
  DistUpgraded: 2022-01-18 23:59:55,390 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
  DistroCodename: jammy
  DistroVariant: ubuntu
  DkmsStatus:
   rtl88x2bu/5.8.7.1, 5.15.0-18-generic, x86_64: installed
   rtl88x2bu/5.8.7.1, 5.15.0-22-generic, x86_64: installed
   rtl88x2bu/5.8.7.1, 5.15.0-23-generic, x86_64: installed
   rtl88x2bu/5.8.7.1, 5.17.0-xanmod1, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Device [8086:9bc6] (rev 05) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Device [1043:8694]
  InstallationDate: Installed on 2021-10-05 (172 days ago)
  InstallationMedia: Ubuntu-Server 21.10 "Impish Indri" - Beta amd64 (20211004)
  MachineType: ASUS System Product Name
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_PH.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-23-generic 
root=UUID=018d5b69-accd-451b-a6f7-2027f791ea0e ro quiet splash vt.handoff=7
  SourcePackage: mesa
  UpgradeStatus: Upgraded to jammy on 2022-01-18 (67 days ago)
  dmi.bios.date: 07/08/2021
  dmi.bios.release: 23.1
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2301
  dmi.board.asset.tag: Default string
  dmi.board.name: Pro WS W480-ACE
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2301:bd07/08/2021:br23.1:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnProWSW480-ACE:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.110-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.0-0ubuntu2
  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/intel-media-driver/+bug/1966571/+subscriptions


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

[Desktop-packages] [Bug 1966635] Re: can't move file/directory by drag and drop by using touch monitor

2022-03-29 Thread Sebastien Bacher

https://gitlab.gnome.org/GNOME/gtk/-/issues/2649 seems to describe a
similar issue

** Bug watch added: gitlab.gnome.org/GNOME/gtk/-/issues #2649
   https://gitlab.gnome.org/GNOME/gtk/-/issues/2649

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

Title:
  can't move file/directory by drag and drop by using touch monitor

Status in OEM Priority Project:
  New
Status in nautilus package in Ubuntu:
  Incomplete

Bug description:
  Can't move file/directory by drag and drop by using a touch monitor

  OS: 22.04, up to date @ Mar 28, 2022.
  nautilus: 1:42~rc-1-ubuntu1
  mode: wayland

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1966635/+subscriptions


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

[Desktop-packages] [Bug 1871538] Autopkgtest regression report (systemd/245.4-4ubuntu3.16)

2022-03-29 Thread Ubuntu SRU Bot

All autopkgtests for the newly accepted systemd (245.4-4ubuntu3.16) for focal 
have finished running.
The following regressions have been reported in tests triggered by the package:

gvfs/1.44.1-1ubuntu1 (arm64, ppc64el, amd64)
linux-aws-5.13/5.13.0-1019.21~20.04.1 (arm64)
snapd/2.54.3+20.04.1ubuntu0.2 (arm64, ppc64el, s390x)
docker.io/20.10.7-0ubuntu5~20.04.2 (s390x)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/focal/update_excuses.html#systemd

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  dbus timeout-ed during an upgrade, taking services down including gdm

Status in D-Bus:
  Unknown
Status in systemd:
  New
Status in accountsservice package in Ubuntu:
  Invalid
Status in dbus package in Ubuntu:
  Invalid
Status in gnome-shell package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Fix Released
Status in accountsservice source package in Focal:
  Invalid
Status in dbus source package in Focal:
  Invalid
Status in gnome-shell source package in Focal:
  Invalid
Status in systemd source package in Focal:
  Fix Committed
Status in accountsservice source package in Groovy:
  Invalid
Status in dbus source package in Groovy:
  Invalid
Status in gnome-shell source package in Groovy:
  Invalid
Status in accountsservice source package in Hirsute:
  Invalid
Status in dbus source package in Hirsute:
  Won't Fix
Status in gnome-shell source package in Hirsute:
  Invalid
Status in accountsservice source package in Impish:
  Invalid
Status in dbus source package in Impish:
  Invalid
Status in gnome-shell source package in Impish:
  Invalid
Status in systemd source package in Impish:
  Fix Committed
Status in accountsservice source package in Jammy:
  Invalid
Status in dbus source package in Jammy:
  Invalid
Status in gnome-shell source package in Jammy:
  Invalid
Status in systemd source package in Jammy:
  Fix Released

Bug description:
  [Impact]

   * There's currently a deadlock between PID 1 and dbus-daemon: in some
  cases dbus-daemon will do NSS lookups (which are blocking) at the same
  time PID 1 synchronously blocks on some call to dbus-daemon (e.g. 
`GetConnectionUnixUser` DBus call). Let's break
  that by setting SYSTEMD_NSS_DYNAMIC_BYPASS=1 env var for dbus-daemon,
  which will disable synchronously blocking varlink calls from nss-systemd
  to PID 1.

   * This can lead to delayed boot times

   * It can also lead to dbus-daemon being killed/re-started, taking
  down other services with it, like GDM, killing user sessions on the
  way (e.g. on installing updates)

  [Test Plan]

   * This bug is really hard to reproduce, as can be seen from the
  multi-year long discussion at
  https://github.com/systemd/systemd/issues/15316

   * Canonical's CPC team has the ability to reproduce  this issue (with
  a relatively high probability) in their Azure test environment, due to
  the specific setup they are using

   * So our test plan is to ask CPC (@gjolly) for confirmation if the
  issue is fixed.

  [Where problems could occur]

   * This fix touches the communication between systemd and dbus daemon,
  especially the NSS lookup, so if something is broken the (user-)name
  resolution could be broken.

   * As a workaround dbus-daemon could be replaced by dbus-broker, which
  never showed this issue or the behaviour could be changed back by
  using the `SYSTEMD_NSS_DYNAMIC_BYPASS` env variable, like this:

  #/etc/systemd/system/dbus.service.d/override.conf
  [Service]
  Environment=SYSTEMD_NSS_DYNAMIC_BYPASS=0

  [Other Info]
   
   * Fixed upstream (v251) in https://github.com/systemd/systemd/pull/22552

  
  === Original Description ===


  
  This morning I found my computer on the login screen.
  But not the one of the screen log, no a new one - so something must have 
crashed.

  Logging in again confirmed that all apps were gone and the gnome shell
  was brought down what seems like triggered by a background update o
  accountsservice.

  As always things are not perfectly clear :-/
  The following goes *back* in time through my logs one by one.

  Multiple apps crashed at 06:09, but we will find later that this is a follow 
on issue of the underlying gnome/X/... recycling.
  -rw-r-  1 paelzer  whoopsie 52962868 Apr  8 06:09 
_usr_bin_konversation.1000.crash
  -rw-r-  1 paelzer  whoopsie   986433 Apr  8 06:09 
_usr_lib_x86_64-linux-gnu_libexec_drkonqi.1000.crash

  rdkit was failing fast and giving up (that will be a different bug, it just 
seems broken on my system):
  Apr 08 06:10:13 Keschdeichel systemd[1]: Started RealtimeKit Scheduling 
Policy Service.
  Apr 08 06:10:1

[Desktop-packages] [Bug 1965535] Re: Stop recommending snap

2022-03-29 Thread Ivan

> Judging by the size of this other thread [1], I'd venture many other
users feel equally about this.

Indeed. Just so that we are clear about the importance of this:

At present, the bug linked to by @guiambros, which triggered opening
this bug in ubuntu-meta as well, is the 3rd highest by heat *for all
bugs recorded in launchpad in all ubuntu packages*:

https://bugs.launchpad.net/ubuntu/+bugs?orderby=-heat&start=0

I think that says something.

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

Title:
  Stop recommending snap

Status in ubuntu-meta package in Ubuntu:
  Opinion

Bug description:
  Currently, ubuntu recommends installing snap by default, and some apps
  are slowly transitioning from DEB-based installation to Snap-based
  installation.

  APT is great, and facilitates having a clean, maintainable system.

  The snap project is not very well designed or engineered (just
  changing the location of where snap data is located is taking the
  project more than 5 years because it was hardcoded:
  https://bugs.launchpad.net/snapd/+bug/1575053). Snaps are large and
  VERY slow. The design of snap, as well as the way that decisions are
  made, are very questionable, and are receiving increasing amounts of
  criticism.

  I'd like to request that Ubuntu stops recommending snap, stops
  transitioning towards snaps, and we come back to defaulting to
  DEB/APT-based installation for all apps.

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


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

[Desktop-packages] [Bug 1966221] Re: gnome-extensions-app crashes with "Segmentation fault (core dumped)"

2022-03-29 Thread Zhang

.-/+oooo+/-.   xiaozhangup@xiaozhangup 
`:+ss+:`   --- 
  -+ssyy+- OS: Ubuntu Jammy Jellyfish (developm 
.ossdMMMNyo.   Kernel: 5.15.0-23-generic 
   /ssshdmmNNmmyNhss/  Uptime: 1 hour, 32 mins 
  +shmydMMMNy+ Packages: 2135 (dpkg), 15 (snap) 
 /hNMMMyhhhmNMMMNh/Shell: bash 5.1.16 
.dMMMNhsshNMMMd.   Resolution: 1600x900 
+hhhyNMMNyyNMMMysss+   DE: GNOME 
ossyNMMMNyMMhsshmmmhssso   WM: Mutter 
ossyNMMMNyMMhsshmmmhssso   WM Theme: Adwaita 
+hhhyNMMNyyNMMMysss+   Theme: Yaru-prussiangreen-dark [GTK2 
.dMMMNhsshNMMMd.   Icons: Yaru-prussiangreen [GTK2/3] 
 /hNMMMyhhhdNMMMNh/Terminal: gnome-terminal 
  +sdmydy+ CPU: Intel i3-3220 (4) @ 3.300GHz 
   /ssshdmmyNhss/  GPU: Intel HD Graphics 
.ossdMMMNyo.   Memory: 2799MiB / 7627MiB 
  -+syyy+-
`:+ss+:`   
.-/+oooo+/-.   


My computer information, maybe it helps?

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

Title:
  gnome-extensions-app crashes with "Segmentation fault (core dumped)"

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

Bug description:
  when I use the command "gnome-extensions-app" in command line ,it will
  crash and report "Segmentation fault (core dumped)"

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell-extension-prefs 42~beta-1ubuntu3
  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: ubuntu:GNOME
  Date: Thu Mar 24 22:32:21 2022
  DisplayManager: gdm3
  InstallationDate: Installed on 2022-02-09 (42 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  RelatedPackageVersions: mutter-common 42~beta-1ubuntu2
  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/1966221/+subscriptions


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

[Desktop-packages] [Bug 1966635] Re: can't move file/directory by drag and drop by using touch monitor

2022-03-29 Thread Yuan-Chen Cheng

Yes, it's not working in Wayland mode, and that's the issue.

I don't know if gnome/nautilus have this feature (dnd file to move it by
using touch monitor)

Maybe it's not and just happened to partially work on x11 mode (if you
check the video I upload, which is x11 mode)

If gnome/nautilus does not have this feature, I think this is a good
feature to have. (May need to think the proper way to)

For the context menu in Wayland mode for the directory, I create
lp:1964091.

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

Title:
  can't move file/directory by drag and drop by using touch monitor

Status in OEM Priority Project:
  New
Status in nautilus package in Ubuntu:
  Incomplete

Bug description:
  Can't move file/directory by drag and drop by using a touch monitor

  OS: 22.04, up to date @ Mar 28, 2022.
  nautilus: 1:42~rc-1-ubuntu1
  mode: wayland

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1966635/+subscriptions


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

[Desktop-packages] [Bug 1966880] Re: Autopkgtest fails on ppc64el with sane-backends 1.1.1-5

On 2022-03-29 14:49, Gunnar Hjalmarsson wrote:
> Triggered another retry — maybe better luck fourth time?

Success! :) Closing this bug.

** Changed in: gscan2pdf (Ubuntu)
   Status: New => Fix Released

** Changed in: sane-backends (Ubuntu)
   Status: New => Fix Released

** Tags removed: update-excuse

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

Title:
  Autopkgtest fails on ppc64el with sane-backends 1.1.1-5

Status in gscan2pdf package in Ubuntu:
  Fix Released
Status in sane-backends package in Ubuntu:
  Fix Released

Bug description:
  Hi Jeffrey,

  Now it happens again. This time only in Ubuntu, for some reason:

  https://autopkgtest.ubuntu.com/packages/g/gscan2pdf/jammy/ppc64el

  Can you please take a look?

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


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

[Desktop-packages] [Bug 1966949] Re: gvfsd-mtp crashed with SIGSEGV in ___pthread_mutex_lock()

2022-03-29 Thread Apport retracing service

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

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

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

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

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

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

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

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

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

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

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  gvfsd-mtp crashed with SIGSEGV in ___pthread_mutex_lock()

Status in gvfs package in Ubuntu:
  New

Bug description:
  I tried to unmount my old Android tablet after successfully copying
  files from it with Nautilus in 22.04 and got this crash.

  ProblemType: Crash
  DistroRelease: Ubuntu 22.04
  Package: gvfs-backends 1.48.1-4
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Uname: Linux 5.15.0-23-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  CasperMD5CheckResult: pass
  CrashCounter: 1
  Date: Tue Mar 29 15:54:17 2022
  ExecutablePath: /usr/libexec/gvfsd-mtp
  InstallationDate: Installed on 2021-11-14 (135 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  ProcCmdline: /usr/libexec/gvfsd-mtp --spawner :1.3 /org/gtk/gvfs/exec_spaw/9
  SegvAnalysis:
   Segfault happened at: 0x7fdd49a16f74 <___pthread_mutex_lock+4>:  mov
0x10(%rdi),%eax
   PC (0x7fdd49a16f74) ok
   source "0x10(%rdi)" (0x01b8) not located in a known VMA region (needed 
readable region)!
   destination "%eax" ok
   Stack memory exhausted (SP below stack segment)
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gvfs
  StacktraceTop:
   ___pthread_mutex_lock (mutex=0x1a8) at ./nptl/pthread_mutex_lock.c:80
   libusb_interrupt_event_handler () from /lib/x86_64-linux-gnu/libusb-1.0.so.0
   ?? ()
   ?? () from /usr/lib/x86_64-linux-gnu/gvfs/libgvfsdaemon.so
   g_vfs_job_run () from /usr/lib/x86_64-linux-gnu/gvfs/libgvfsdaemon.so
  Title: gvfsd-mtp crashed with SIGSEGV in ___pthread_mutex_lock()
  UpgradeStatus: Upgraded to jammy on 2022-03-21 (7 days ago)
  UserGroups: adm cdrom dip docker libvirt lpadmin lxd plugdev sambashare sudo
  separator:

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


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

[Desktop-packages] [Bug 1966947] Re: nautilus crashed with SIGSEGV in gtk_widget_get_ancestor()

2022-03-29 Thread Apport retracing service

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

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

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

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

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

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

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

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

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

** This bug has been marked a duplicate of bug 1962761
   nautilus crashed with SIGSEGV in gtk_widget_get_ancestor()

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  nautilus crashed with SIGSEGV in gtk_widget_get_ancestor()

Status in nautilus package in Ubuntu:
  New

Bug description:
  i just closed the nautilus and it appeared. Non reproduce able.

  ProblemType: Crash
  DistroRelease: Ubuntu 22.04
  Package: nautilus 1:42~rc-1ubuntu1
  Uname: Linux 5.16.1-051601-generic x86_64
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Mar 29 17:39:48 2022
  ExecutablePath: /usr/bin/nautilus
  GsettingsChanges:
   b'org.gnome.nautilus.icon-view' b'default-zoom-level' b"'standard'"
   b'org.gnome.nautilus.window-state' b'initial-size' b'(1013, 584)'
   b'org.gnome.nautilus.window-state' b'maximized' b'true'
  InstallationDate: Installed on 2021-12-23 (96 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  ProcCmdline: /usr/bin/nautilus --gapplication-service
  SegvAnalysis:
   Segfault happened at: 0x7f8af523aa88 :   cmp
%rax,(%rbx)
   PC (0x7f8af523aa88) ok
   source "%rax" ok
   destination "(%rbx)" (0xbffb1f6f6f6) not located in a known VMA region 
(needed writable region)!
  SegvReason: writing unknown VMA
  Signal: 11
  SourcePackage: nautilus
  StacktraceTop:
   gtk_widget_get_ancestor () from /lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? ()
   g_closure_invoke () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_signal_emit_valist () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: nautilus crashed with SIGSEGV in gtk_widget_get_ancestor()
  UpgradeStatus: Upgraded to jammy on 2022-01-14 (73 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  separator:
   
  usr_lib_nautilus:
   evince42.1-1
   file-roller   3.42.0-1
   nautilus-extension-gnome-terminal 3.43.90-1ubuntu1
   nautilus-share0.7.3-2ubuntu5

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


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

[Desktop-packages] [Bug 1966880] Re: Autopkgtest fails on ppc64el with sane-backends 1.1.1-5

Saw that libsane 1.1.1-4 was used for the successful graphicsmagick run,
though.

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

Title:
  Autopkgtest fails on ppc64el with sane-backends 1.1.1-5

Status in gscan2pdf package in Ubuntu:
  New
Status in sane-backends package in Ubuntu:
  New

Bug description:
  Hi Jeffrey,

  Now it happens again. This time only in Ubuntu, for some reason:

  https://autopkgtest.ubuntu.com/packages/g/gscan2pdf/jammy/ppc64el

  Can you please take a look?

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


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

[Desktop-packages] [Bug 1966418] Re: [jammy regression] Evolution does not display message content anymore

2022-03-29 Thread Luis Alberto Pabón

`WEBKIT_DISABLE_COMPOSITING_MODE=1 evolution` works around the issue for
me on a Sway wayland session and running evolution in native wayland
mode.

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

Title:
  [jammy regression] Evolution does not display message content anymore

Status in Webkit:
  Confirmed
Status in epiphany-browser package in Ubuntu:
  Confirmed
Status in evolution package in Ubuntu:
  Confirmed
Status in liferea package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  Confirmed
Status in webkit2gtk package in Ubuntu:
  Confirmed

Bug description:
  Impact
  --
  All webkit using apps for affected users display a blank screen.

  Original Bug Report
  ---
  Evolution has suddenly stopped displaying message contents on the last 24h. 
Starting it up from the command line shows this output:

  ```
  EGLDisplay Initialization failed: EGL_NOT_INITIALIZED
  Cannot create EGL context: invalid display (last error: EGL_SUCCESS)
  ```

  I don't know if it's related, but googling around shows some webkitgtk
  hits on this error.

  The email contents are however clickable. They're just not rendered to
  screen (see attached file).

  Deleting the evolution folders from `~/.config`, `~/.cache` and
  `~/.local/share` does not help.

  Email accounts are all google, configured through gnome online
  accounts.

  Workaround #1
  -
  You can run the app from the command line with
  WEBKIT_DISABLE_COMPOSITING_MODE=1 evolution
  (Replace evolution with the name of the webkit app you are trying to use)

  Workaround #2
  -
  Log out.
  Select your name on the login screen.
  Click the gear button and choose Ubuntu on Xorg.
  Enter your password to finish logging in.

  
  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: evolution 3.44.0-1
  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: sway
  Date: Fri Mar 25 10:55:49 2022
  SourcePackage: evolution
  UpgradeStatus: Upgraded to jammy on 2022-03-01 (24 days ago)

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


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

[Desktop-packages] [Bug 1966880] Re: Autopkgtest fails on ppc64el with sane-backends 1.1.1-5

Hmm.. It failed three times for sane-backends, and then it passed for
graphicsmagick. Triggered another retry — maybe better luck fourth time?

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

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

Title:
  Autopkgtest fails on ppc64el with sane-backends 1.1.1-5

Status in gscan2pdf package in Ubuntu:
  New
Status in sane-backends package in Ubuntu:
  New

Bug description:
  Hi Jeffrey,

  Now it happens again. This time only in Ubuntu, for some reason:

  https://autopkgtest.ubuntu.com/packages/g/gscan2pdf/jammy/ppc64el

  Can you please take a look?

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


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

[Desktop-packages] [Bug 1966808] Re: [amdgpu][radeon] gnome-shell Wayland sessions fail to start (Failed to lock front buffer on /dev/dri/card1: drmModeAddFB2WithModifiers failed: Invalid argument)

Thank you for the quick investigation into this.  Once the patch you
listed: https://gitlab.gnome.org/GNOME/mutter/-/commit/690b8806d is
available, would I have to comment out the KMS_MODIFIERS line for
completeness?

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

Title:
  [amdgpu][radeon] gnome-shell Wayland sessions fail to start (Failed to
  lock front buffer on /dev/dri/card1: drmModeAddFB2WithModifiers
  failed: Invalid argument)

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

Bug description:
  Wayland started crashing for me on upgrade to Jammy, which I'm aware
  is currently in alpha.

  gdm was crashing, and changing to lightdm addressed this issue.  If I
  select 'Ubuntu on Xorg' - I can login without problems.

  If I select Wayland instead, I just get a black screen, and I have to
  kill gnome-session from a virtual console.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 42~beta-1ubuntu3
  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: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Mar 28 15:23:51 2022
  DisplayManager: lightdm
  InstallationDate: Installed on 2022-03-19 (9 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220318)
  RelatedPackageVersions: mutter-common 42~beta-1ubuntu2
  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/1966808/+subscriptions


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

[Desktop-packages] [Bug 1966930] Re: Cannot drag tabs with mouse

2022-03-29 Thread Olivier Tilloy

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

** This bug has been marked a duplicate of bug 1964541
   Cannot rearrange Firefox (snap) browser tabs in Wayland sessions

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

Title:
  Cannot drag tabs with mouse

Status in firefox package in Ubuntu:
  New

Bug description:
  When testing firefox 98.0.2 from the snap on the Ubuntu for Raspberry
  Pi pre-installed desktop image (using Wayland), I noted that I'm
  unable to drag'n'drop tabs to re-order them, or detach them into
  separate windows. I can re-order tabs with the Ctrl+Shift+Pg{Up,Dn}
  keyboard short-cuts, but not with the mouse.

  This occurred both in the default configuration (with tabs in the
  title bar's area), and in my preferred configuration (with the title
  bar displayed above the tabs bar).

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


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

[Desktop-packages] [Bug 1966808] Re: [amdgpu][radeon] gnome-shell Wayland sessions fail to start (Failed to lock front buffer on /dev/dri/card1: drmModeAddFB2WithModifiers failed: Invalid argument)

MUTTER_DEBUG_USE_KMS_MODIFIERS=0

fixes the issue.  gdm3 also works now.

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

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

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

Title:
  [amdgpu][radeon] gnome-shell Wayland sessions fail to start (Failed to
  lock front buffer on /dev/dri/card1: drmModeAddFB2WithModifiers
  failed: Invalid argument)

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

Bug description:
  Wayland started crashing for me on upgrade to Jammy, which I'm aware
  is currently in alpha.

  gdm was crashing, and changing to lightdm addressed this issue.  If I
  select 'Ubuntu on Xorg' - I can login without problems.

  If I select Wayland instead, I just get a black screen, and I have to
  kill gnome-session from a virtual console.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 42~beta-1ubuntu3
  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: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Mar 28 15:23:51 2022
  DisplayManager: lightdm
  InstallationDate: Installed on 2022-03-19 (9 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220318)
  RelatedPackageVersions: mutter-common 42~beta-1ubuntu2
  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/1966808/+subscriptions


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

[Desktop-packages] [Bug 1965696] Re: Shell keyboard navigation (after pressing Ctrl+Alt+Tab) doesn't work in Xorg sessions

2022-03-29 Thread Jeremy Lincicome

** Also affects: gnome-shell via
   https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/5270
   Importance: Unknown
   Status: Unknown

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

Title:
  Shell keyboard navigation (after pressing Ctrl+Alt+Tab) doesn't work
  in Xorg sessions

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

Bug description:
  As of 2 days ago, I can no longer quickly get to system controls such
  as the Top Bar using the keyboard.  According to the keyboard
  shortcuts settings window, I should be able to press "CTRL+Alt+Tab" to
  access these controls.  When I press this key combination, I'm told by
  the Orca screen reader that I'm on the Top Bar. When I release the
  keys, focus jumps back to the window I was in before. I do not know if
  this is the case without Orca running. I'm unable to test without Orca
  running. I've reset Gnome settings, with no change.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 42~beta-1ubuntu3
  Uname: Linux 5.16.11-76051611-generic x86_64
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Mar 20 13:01:07 2022
  DisplayManager: gdm3
  InstallationDate: Installed on 2018-04-30 (1420 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180425.1)
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 42~beta-1ubuntu2
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Desktop-packages] [Bug 1966418]

2022-03-29 Thread Michael Catanzaro

OK, then for sure this bug is not the problem that Ubuntu users are
seeing. Hi Ubuntu, please file a separate bug. Thanks!

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

Title:
  [jammy regression] Evolution does not display message content anymore

Status in Webkit:
  Confirmed
Status in epiphany-browser package in Ubuntu:
  Confirmed
Status in evolution package in Ubuntu:
  Confirmed
Status in liferea package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  Confirmed
Status in webkit2gtk package in Ubuntu:
  Confirmed

Bug description:
  Impact
  --
  All webkit using apps for affected users display a blank screen.

  Original Bug Report
  ---
  Evolution has suddenly stopped displaying message contents on the last 24h. 
Starting it up from the command line shows this output:

  ```
  EGLDisplay Initialization failed: EGL_NOT_INITIALIZED
  Cannot create EGL context: invalid display (last error: EGL_SUCCESS)
  ```

  I don't know if it's related, but googling around shows some webkitgtk
  hits on this error.

  The email contents are however clickable. They're just not rendered to
  screen (see attached file).

  Deleting the evolution folders from `~/.config`, `~/.cache` and
  `~/.local/share` does not help.

  Email accounts are all google, configured through gnome online
  accounts.

  Workaround #1
  -
  You can run the app from the command line with
  WEBKIT_DISABLE_COMPOSITING_MODE=1 evolution
  (Replace evolution with the name of the webkit app you are trying to use)

  Workaround #2
  -
  Log out.
  Select your name on the login screen.
  Click the gear button and choose Ubuntu on Xorg.
  Enter your password to finish logging in.

  
  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: evolution 3.44.0-1
  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: sway
  Date: Fri Mar 25 10:55:49 2022
  SourcePackage: evolution
  UpgradeStatus: Upgraded to jammy on 2022-03-01 (24 days ago)

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


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

[Desktop-packages] [Bug 1966418]

2022-03-29 Thread Cgarcia-f

If works with x11 enabled, that's probably because we messed it up with
the gl platform includes in the gl detection patches.

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

Title:
  [jammy regression] Evolution does not display message content anymore

Status in Webkit:
  Confirmed
Status in epiphany-browser package in Ubuntu:
  Confirmed
Status in evolution package in Ubuntu:
  Confirmed
Status in liferea package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  Confirmed
Status in webkit2gtk package in Ubuntu:
  Confirmed

Bug description:
  Impact
  --
  All webkit using apps for affected users display a blank screen.

  Original Bug Report
  ---
  Evolution has suddenly stopped displaying message contents on the last 24h. 
Starting it up from the command line shows this output:

  ```
  EGLDisplay Initialization failed: EGL_NOT_INITIALIZED
  Cannot create EGL context: invalid display (last error: EGL_SUCCESS)
  ```

  I don't know if it's related, but googling around shows some webkitgtk
  hits on this error.

  The email contents are however clickable. They're just not rendered to
  screen (see attached file).

  Deleting the evolution folders from `~/.config`, `~/.cache` and
  `~/.local/share` does not help.

  Email accounts are all google, configured through gnome online
  accounts.

  Workaround #1
  -
  You can run the app from the command line with
  WEBKIT_DISABLE_COMPOSITING_MODE=1 evolution
  (Replace evolution with the name of the webkit app you are trying to use)

  Workaround #2
  -
  Log out.
  Select your name on the login screen.
  Click the gear button and choose Ubuntu on Xorg.
  Enter your password to finish logging in.

  
  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: evolution 3.44.0-1
  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: sway
  Date: Fri Mar 25 10:55:49 2022
  SourcePackage: evolution
  UpgradeStatus: Upgraded to jammy on 2022-03-01 (24 days ago)

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


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

[Desktop-packages] [Bug 1966418]

2022-03-29 Thread Michael Catanzaro

(In reply to seb128 from comment #12)
> The issue also got reported on launchpad for the incoming Ubuntu
> https://bugs.launchpad.net/webkit/+bug/1966418
> 
> It is only an issue under wayland, login into an x11 session makes things
> work again

You have different/additional information in that downstream bug. I'm
not convinced that it's the same as this issue. In your downstream bug,
you are seeing:

EGLDisplay Initialization failed: EGL_NOT_INITIALIZED
Cannot create EGL context: invalid display (last error: EGL_SUCCESS)

But Adrian has not reported this error. Adrian, do you see that
anywhere? If not, we'll need a separate bug report for them.

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

Title:
  [jammy regression] Evolution does not display message content anymore

Status in Webkit:
  Confirmed
Status in epiphany-browser package in Ubuntu:
  Confirmed
Status in evolution package in Ubuntu:
  Confirmed
Status in liferea package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  Confirmed
Status in webkit2gtk package in Ubuntu:
  Confirmed

Bug description:
  Impact
  --
  All webkit using apps for affected users display a blank screen.

  Original Bug Report
  ---
  Evolution has suddenly stopped displaying message contents on the last 24h. 
Starting it up from the command line shows this output:

  ```
  EGLDisplay Initialization failed: EGL_NOT_INITIALIZED
  Cannot create EGL context: invalid display (last error: EGL_SUCCESS)
  ```

  I don't know if it's related, but googling around shows some webkitgtk
  hits on this error.

  The email contents are however clickable. They're just not rendered to
  screen (see attached file).

  Deleting the evolution folders from `~/.config`, `~/.cache` and
  `~/.local/share` does not help.

  Email accounts are all google, configured through gnome online
  accounts.

  Workaround #1
  -
  You can run the app from the command line with
  WEBKIT_DISABLE_COMPOSITING_MODE=1 evolution
  (Replace evolution with the name of the webkit app you are trying to use)

  Workaround #2
  -
  Log out.
  Select your name on the login screen.
  Click the gear button and choose Ubuntu on Xorg.
  Enter your password to finish logging in.

  
  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: evolution 3.44.0-1
  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: sway
  Date: Fri Mar 25 10:55:49 2022
  SourcePackage: evolution
  UpgradeStatus: Upgraded to jammy on 2022-03-01 (24 days ago)

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


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

[Desktop-packages] [Bug 1966418]

2022-03-29 Thread Adrian Vovk

I don't compile WebKit w/ X11 support so I can't tell you if running
epiphany w/ GDK_BACKEND=x11 helps anything

---

I do not see those EGL errors when I run epiphany on the host. However,
if I run the Epiphany flatpak with FLATPAK_GL_DRIVERS=host, I get

EGLDisplay Initialization failed: EGL_BAD_PARAMETER
Cannot create EGL context: invalid display (last error: EGL_SUCCESS)

but the webviews still show up (they're just sluggish). When running
with FLATPAK_GL_DRIVERS=host, the epiphany flatpak starts crashing when
opening about:gpu

---

Downgrading to Mesa 21.3.8 on the host does not solve the issue for me.
Not sure what's going on here, because Epiphany from Flathub (using Mesa
21.3.8, WebKitGTK 2.36.0) works perfectly fine in my environment

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

Title:
  [jammy regression] Evolution does not display message content anymore

Status in Webkit:
  Confirmed
Status in epiphany-browser package in Ubuntu:
  Confirmed
Status in evolution package in Ubuntu:
  Confirmed
Status in liferea package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  Confirmed
Status in webkit2gtk package in Ubuntu:
  Confirmed

Bug description:
  Impact
  --
  All webkit using apps for affected users display a blank screen.

  Original Bug Report
  ---
  Evolution has suddenly stopped displaying message contents on the last 24h. 
Starting it up from the command line shows this output:

  ```
  EGLDisplay Initialization failed: EGL_NOT_INITIALIZED
  Cannot create EGL context: invalid display (last error: EGL_SUCCESS)
  ```

  I don't know if it's related, but googling around shows some webkitgtk
  hits on this error.

  The email contents are however clickable. They're just not rendered to
  screen (see attached file).

  Deleting the evolution folders from `~/.config`, `~/.cache` and
  `~/.local/share` does not help.

  Email accounts are all google, configured through gnome online
  accounts.

  Workaround #1
  -
  You can run the app from the command line with
  WEBKIT_DISABLE_COMPOSITING_MODE=1 evolution
  (Replace evolution with the name of the webkit app you are trying to use)

  Workaround #2
  -
  Log out.
  Select your name on the login screen.
  Click the gear button and choose Ubuntu on Xorg.
  Enter your password to finish logging in.

  
  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: evolution 3.44.0-1
  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: sway
  Date: Fri Mar 25 10:55:49 2022
  SourcePackage: evolution
  UpgradeStatus: Upgraded to jammy on 2022-03-01 (24 days ago)

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


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

[Desktop-packages] [Bug 1966418]

2022-03-29 Thread Adrian Vovk

OK I found a way to fix it @ package time! I previously built webkitgtk
with -DENABLE_X11_TARGET=OFF. I tried building with
-DENABLE_X11_TARGET=ON (since this is the major difference between my
build and the gnome-build-meta build, aside from Mesa version), and now
it works properly

Seems like disabling the x11 backend also accidentally disables parts of
the Wayland backend somewhere

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

Title:
  [jammy regression] Evolution does not display message content anymore

Status in Webkit:
  Confirmed
Status in epiphany-browser package in Ubuntu:
  Confirmed
Status in evolution package in Ubuntu:
  Confirmed
Status in liferea package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  Confirmed
Status in webkit2gtk package in Ubuntu:
  Confirmed

Bug description:
  Impact
  --
  All webkit using apps for affected users display a blank screen.

  Original Bug Report
  ---
  Evolution has suddenly stopped displaying message contents on the last 24h. 
Starting it up from the command line shows this output:

  ```
  EGLDisplay Initialization failed: EGL_NOT_INITIALIZED
  Cannot create EGL context: invalid display (last error: EGL_SUCCESS)
  ```

  I don't know if it's related, but googling around shows some webkitgtk
  hits on this error.

  The email contents are however clickable. They're just not rendered to
  screen (see attached file).

  Deleting the evolution folders from `~/.config`, `~/.cache` and
  `~/.local/share` does not help.

  Email accounts are all google, configured through gnome online
  accounts.

  Workaround #1
  -
  You can run the app from the command line with
  WEBKIT_DISABLE_COMPOSITING_MODE=1 evolution
  (Replace evolution with the name of the webkit app you are trying to use)

  Workaround #2
  -
  Log out.
  Select your name on the login screen.
  Click the gear button and choose Ubuntu on Xorg.
  Enter your password to finish logging in.

  
  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: evolution 3.44.0-1
  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: sway
  Date: Fri Mar 25 10:55:49 2022
  SourcePackage: evolution
  UpgradeStatus: Upgraded to jammy on 2022-03-01 (24 days ago)

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


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

[Desktop-packages] [Bug 1966418]

2022-03-29 Thread Jeremy Bicha

I believe the Ubuntu bug I'm experiencing was triggered by the update to
mesa 22.0. I am using Intel graphics.

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

Title:
  [jammy regression] Evolution does not display message content anymore

Status in Webkit:
  Confirmed
Status in epiphany-browser package in Ubuntu:
  Confirmed
Status in evolution package in Ubuntu:
  Confirmed
Status in liferea package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  Confirmed
Status in webkit2gtk package in Ubuntu:
  Confirmed

Bug description:
  Impact
  --
  All webkit using apps for affected users display a blank screen.

  Original Bug Report
  ---
  Evolution has suddenly stopped displaying message contents on the last 24h. 
Starting it up from the command line shows this output:

  ```
  EGLDisplay Initialization failed: EGL_NOT_INITIALIZED
  Cannot create EGL context: invalid display (last error: EGL_SUCCESS)
  ```

  I don't know if it's related, but googling around shows some webkitgtk
  hits on this error.

  The email contents are however clickable. They're just not rendered to
  screen (see attached file).

  Deleting the evolution folders from `~/.config`, `~/.cache` and
  `~/.local/share` does not help.

  Email accounts are all google, configured through gnome online
  accounts.

  Workaround #1
  -
  You can run the app from the command line with
  WEBKIT_DISABLE_COMPOSITING_MODE=1 evolution
  (Replace evolution with the name of the webkit app you are trying to use)

  Workaround #2
  -
  Log out.
  Select your name on the login screen.
  Click the gear button and choose Ubuntu on Xorg.
  Enter your password to finish logging in.

  
  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: evolution 3.44.0-1
  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: sway
  Date: Fri Mar 25 10:55:49 2022
  SourcePackage: evolution
  UpgradeStatus: Upgraded to jammy on 2022-03-01 (24 days ago)

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


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

[Desktop-packages] [Bug 1966007] Re: Flood of Bluetooth Malicious advertisind data

2022-03-29 Thread Andras Tim

The `gnome-terminal` is not affected by the kernel's Bluetooth issue...

** Package changed: gnome-terminal (Ubuntu) => linux-signed (Ubuntu)

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

Title:
  Flood of Bluetooth Malicious advertisind data

Status in linux-signed package in Ubuntu:
  Confirmed

Bug description:
  This problem occurred with the  ugrade of the kernel to patch level
  105.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-terminal 3.36.2-1ubuntu1~20.04
  ProcVersionSignature: Ubuntu 5.4.0-105.119-generic 5.4.174
  Uname: Linux 5.4.0-105-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar 23 12:48:22 2022
  ExecutablePath: /usr/libexec/gnome-terminal-server
  InstallationDate: Installed on 2018-06-21 (1370 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcEnviron:
   LANG=en_AU.UTF-8
   PATH=(custom, user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  SourcePackage: gnome-terminal
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Desktop-packages] [Bug 1965696] Re: Shell keyboard navigation (after pressing Ctrl+Alt+Tab) doesn't work in Xorg sessions

2022-03-29 Thread Jeremy Lincicome

Bug filed upstream. 

** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/-/issues #5270
   https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/5270

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

Title:
  Shell keyboard navigation (after pressing Ctrl+Alt+Tab) doesn't work
  in Xorg sessions

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  As of 2 days ago, I can no longer quickly get to system controls such
  as the Top Bar using the keyboard.  According to the keyboard
  shortcuts settings window, I should be able to press "CTRL+Alt+Tab" to
  access these controls.  When I press this key combination, I'm told by
  the Orca screen reader that I'm on the Top Bar. When I release the
  keys, focus jumps back to the window I was in before. I do not know if
  this is the case without Orca running. I'm unable to test without Orca
  running. I've reset Gnome settings, with no change.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 42~beta-1ubuntu3
  Uname: Linux 5.16.11-76051611-generic x86_64
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Mar 20 13:01:07 2022
  DisplayManager: gdm3
  InstallationDate: Installed on 2018-04-30 (1420 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180425.1)
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 42~beta-1ubuntu2
  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/1965696/+subscriptions


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

[Desktop-packages] [Bug 1966221] Re: gnome-extensions-app crashes with "Segmentation fault (core dumped)"

2022-03-29 Thread Timo Aaltonen

gnome-chess fails to start as well, but it's crashing also on newer gen
chips (tested on Alder Lake) with the iris driver. What's common is that
it is also fine on wayland.

upstream had a look at the backtrace, but said that there's nothing that
would explain why it fails on xorg

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

Title:
  gnome-extensions-app crashes with "Segmentation fault (core dumped)"

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

Bug description:
  when I use the command "gnome-extensions-app" in command line ,it will
  crash and report "Segmentation fault (core dumped)"

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell-extension-prefs 42~beta-1ubuntu3
  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: ubuntu:GNOME
  Date: Thu Mar 24 22:32:21 2022
  DisplayManager: gdm3
  InstallationDate: Installed on 2022-02-09 (42 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  RelatedPackageVersions: mutter-common 42~beta-1ubuntu2
  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/1966221/+subscriptions


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

[Desktop-packages] [Bug 1966808] Re: [amdgpu][radeon] gnome-shell Wayland sessions fail to start (Failed to lock front buffer on /dev/dri/card1: drmModeAddFB2WithModifiers failed: Invalid argument)

Please wait until you receive mutter version 42.0-1ubuntu1 in updates
and then try adding this to /etc/environment:

  MUTTER_DEBUG_DISABLE_TRIPLE_BUFFERING=1
  MUTTER_DEBUG_USE_KMS_MODIFIERS=0

and then reboot.

If that fixes the bug then please try each line separately to identify
which one has fixed it.

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

** Changed in: mutter (Ubuntu)
   Status: Confirmed => Incomplete

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

Title:
  [amdgpu][radeon] gnome-shell Wayland sessions fail to start (Failed to
  lock front buffer on /dev/dri/card1: drmModeAddFB2WithModifiers
  failed: Invalid argument)

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

Bug description:
  Wayland started crashing for me on upgrade to Jammy, which I'm aware
  is currently in alpha.

  gdm was crashing, and changing to lightdm addressed this issue.  If I
  select 'Ubuntu on Xorg' - I can login without problems.

  If I select Wayland instead, I just get a black screen, and I have to
  kill gnome-session from a virtual console.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 42~beta-1ubuntu3
  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: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Mar 28 15:23:51 2022
  DisplayManager: lightdm
  InstallationDate: Installed on 2022-03-19 (9 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220318)
  RelatedPackageVersions: mutter-common 42~beta-1ubuntu2
  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/1966808/+subscriptions


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

[Desktop-packages] [Bug 1965627] Re: Unlock screen password is barely visible/contrasting

This bug was fixed in the package yaru-theme - 22.04.3.1

---
yaru-theme (22.04.3.1) jammy; urgency=medium

  [ Marco Trevisan (Treviño) ]
  * gtk: Do not use shell scss sources to define accent colors used by icons
  * github: Generate rendered icons and symlinks automatically
  * icons: Use more predicibile rendering target names
  * meson: Render each icon separately to use multi-process rendering
  * render-bitmaps: Fail in case no SVG is rendered
  * meson: Allow to render one icon across all the flavours separately
  * render-bitmaps: Support searching for icons by category
  * github: Add automated workflow to optimize SVG
  * github: Do a full icons rebuild if the renderer script changes
  * icons/generate-symlinks.sh: Ignore empty lines on list file
  * icons/phosh.list: Remove trailing empty line
  * CI: Split build workflow in multiple steps
  * icons: Add tests to try generating symlinks
  * meson: Use more fs filename modifications functions
  * Revert "icons: modify meson and deb files (LP: #1965649)
  * github: Fix Links on generated PRs
  * meson: Bump dependency to 0.59 as per fs.parent() usage
  * icons: Install panel icons only if mate or unity are enabled
  * icons: Ensure symlinks are all generated from symlink script
  * icons/scalable: Remove icons that are already handled via symlinks
  * icons: Remove all the links in source dirs, they should be handled via lists
  * CI: Recreate symlinks removing old ones
  * CI: Detect changes on all symlinks files
  * CI: Ensure that no symlinks are used in icon sources
  * CI: Use inverse logic, we don't want symlinks :)
  * CI: Cleanup rendered icons before render them again
  * icons/accented: Remove software store from accented icons
  * gnome-shell: Use correct syntax for or'ed find
  * CI: Archive meson logs
  * generate-index-theme: Support excluding a specific icons directory
  * icons: Also generate symlinks for 22x22 icons
  * icons: Generate panel symlinks, and install them only when needed
  * generate-index-theme: Handle the scalable min/max size cases
  * generate-index-theme: Use proper context names when not computable
  * icons: Auto-generate index.theme for default and mate icon themes
  * generate-index-theme: Support excluding elements by context
  * generate-index-theme: Support providing custom parameters for a folder
  * icons: Replicate symlinks in installed folder when using meson >= 0.61
  * icons: Use nicer way to compute find command for excluded folders
  * gnome-shell: Use native meson symlink installer when possible
  * icons, gnome-shell: Use python-computed relative paths
  * CI: Make meson options more readable in full build
  * gnome-shell: Add further option to toggle UserThemes support
  * debian/rules: Enable user themes support in packages
  * icons: Add more accented icons
  * icons: Use better name for rendered icon target
  * gtk, gnome-shell: Only generate Yaru-$accent-dark themes if `dark` is set
  * icons: Generate dark variants of the icons theme
  * CI: Also consider untracked changes on rendering/optimizing icons
  * CI: Use proper syntax to check on rendered icons changes
  * icons: Install icons symlinks as such also with older meson versions
  * icons: Inherit dark accented variants from Yaru-dark as primary choice
  * yaru-colors-defs: Use a map to define colors so we can avoid repetitions
  * yaru-colors-defs: Ensure we always generate opaque colors
  * yaru-colors-defs: Use more css-style generated definitions
  * gnome-shell: Use proper name for generated target output name
  * gnome-shell: Define custom checkbox bg color and expose bg-color as such
  * icons/symlinks: avoid using symlinks to symlinks not to confuse generator
  * icons: Add speaker icons for mate
  * debian: Include new installed files to proper package

  [ Martin Wimpress ]
  * metacity: Correct Metacity theme contrast so they match GNOME/CSD windows
  * gtk: Add MetacityThemeName to index.theme
  * metacity: Correct titlebar contrast for default and dark themes
  * mate: Restore MATE icons
  * icons: Remove Humanity icons languishing in legacy
  * mate: Drop unnecessary MATE variations of GtkSourceView and Metacity themes
  * icons: Add ulauncher panel icons
  * metacity: Add window buttons to modal windows (LP: #1917185)
  * icons: Add symlinks for fullcolor printer and printers icons
  * icons: Add symlinks for more MATE apps
  * icons: Fix preferences-system.png collision and add more MATE symlinks
  * icons: Add redshift and steam panel icons
  * icons: Add symlink for preferences-desktop-default-applications.png
  * gtk: Add gtk-2.0 themes for color accents (LP: #1965659)
  * icons: Create dark theme subfolders and symlink categories
  * icons: Add Dropbox, Remmina, Transmission & audacious panel icons
(LP: #964518, LP: #1949312)

  [ Lyubomir Popov ]
  * accent colours: subtler purple, magenta and red
  * accent colours: adjust hue of the red color
  * adjust hue of magenta so it corresponds better t

[Desktop-packages] [Bug 1917185] Re: Nextcloud settings window does not get decorated with window control buttons

This bug was fixed in the package yaru-theme - 22.04.3.1

---
yaru-theme (22.04.3.1) jammy; urgency=medium

  [ Marco Trevisan (Treviño) ]
  * gtk: Do not use shell scss sources to define accent colors used by icons
  * github: Generate rendered icons and symlinks automatically
  * icons: Use more predicibile rendering target names
  * meson: Render each icon separately to use multi-process rendering
  * render-bitmaps: Fail in case no SVG is rendered
  * meson: Allow to render one icon across all the flavours separately
  * render-bitmaps: Support searching for icons by category
  * github: Add automated workflow to optimize SVG
  * github: Do a full icons rebuild if the renderer script changes
  * icons/generate-symlinks.sh: Ignore empty lines on list file
  * icons/phosh.list: Remove trailing empty line
  * CI: Split build workflow in multiple steps
  * icons: Add tests to try generating symlinks
  * meson: Use more fs filename modifications functions
  * Revert "icons: modify meson and deb files (LP: #1965649)
  * github: Fix Links on generated PRs
  * meson: Bump dependency to 0.59 as per fs.parent() usage
  * icons: Install panel icons only if mate or unity are enabled
  * icons: Ensure symlinks are all generated from symlink script
  * icons/scalable: Remove icons that are already handled via symlinks
  * icons: Remove all the links in source dirs, they should be handled via lists
  * CI: Recreate symlinks removing old ones
  * CI: Detect changes on all symlinks files
  * CI: Ensure that no symlinks are used in icon sources
  * CI: Use inverse logic, we don't want symlinks :)
  * CI: Cleanup rendered icons before render them again
  * icons/accented: Remove software store from accented icons
  * gnome-shell: Use correct syntax for or'ed find
  * CI: Archive meson logs
  * generate-index-theme: Support excluding a specific icons directory
  * icons: Also generate symlinks for 22x22 icons
  * icons: Generate panel symlinks, and install them only when needed
  * generate-index-theme: Handle the scalable min/max size cases
  * generate-index-theme: Use proper context names when not computable
  * icons: Auto-generate index.theme for default and mate icon themes
  * generate-index-theme: Support excluding elements by context
  * generate-index-theme: Support providing custom parameters for a folder
  * icons: Replicate symlinks in installed folder when using meson >= 0.61
  * icons: Use nicer way to compute find command for excluded folders
  * gnome-shell: Use native meson symlink installer when possible
  * icons, gnome-shell: Use python-computed relative paths
  * CI: Make meson options more readable in full build
  * gnome-shell: Add further option to toggle UserThemes support
  * debian/rules: Enable user themes support in packages
  * icons: Add more accented icons
  * icons: Use better name for rendered icon target
  * gtk, gnome-shell: Only generate Yaru-$accent-dark themes if `dark` is set
  * icons: Generate dark variants of the icons theme
  * CI: Also consider untracked changes on rendering/optimizing icons
  * CI: Use proper syntax to check on rendered icons changes
  * icons: Install icons symlinks as such also with older meson versions
  * icons: Inherit dark accented variants from Yaru-dark as primary choice
  * yaru-colors-defs: Use a map to define colors so we can avoid repetitions
  * yaru-colors-defs: Ensure we always generate opaque colors
  * yaru-colors-defs: Use more css-style generated definitions
  * gnome-shell: Use proper name for generated target output name
  * gnome-shell: Define custom checkbox bg color and expose bg-color as such
  * icons/symlinks: avoid using symlinks to symlinks not to confuse generator
  * icons: Add speaker icons for mate
  * debian: Include new installed files to proper package

  [ Martin Wimpress ]
  * metacity: Correct Metacity theme contrast so they match GNOME/CSD windows
  * gtk: Add MetacityThemeName to index.theme
  * metacity: Correct titlebar contrast for default and dark themes
  * mate: Restore MATE icons
  * icons: Remove Humanity icons languishing in legacy
  * mate: Drop unnecessary MATE variations of GtkSourceView and Metacity themes
  * icons: Add ulauncher panel icons
  * metacity: Add window buttons to modal windows (LP: #1917185)
  * icons: Add symlinks for fullcolor printer and printers icons
  * icons: Add symlinks for more MATE apps
  * icons: Fix preferences-system.png collision and add more MATE symlinks
  * icons: Add redshift and steam panel icons
  * icons: Add symlink for preferences-desktop-default-applications.png
  * gtk: Add gtk-2.0 themes for color accents (LP: #1965659)
  * icons: Create dark theme subfolders and symlink categories
  * icons: Add Dropbox, Remmina, Transmission & audacious panel icons
(LP: #964518, LP: #1949312)

  [ Lyubomir Popov ]
  * accent colours: subtler purple, magenta and red
  * accent colours: adjust hue of the red color
  * adjust hue of magenta so it corresponds better t

[Desktop-packages] [Bug 964518] Re: remmina should get a monochrome indicator icon

This bug was fixed in the package yaru-theme - 22.04.3.1

---
yaru-theme (22.04.3.1) jammy; urgency=medium

  [ Marco Trevisan (Treviño) ]
  * gtk: Do not use shell scss sources to define accent colors used by icons
  * github: Generate rendered icons and symlinks automatically
  * icons: Use more predicibile rendering target names
  * meson: Render each icon separately to use multi-process rendering
  * render-bitmaps: Fail in case no SVG is rendered
  * meson: Allow to render one icon across all the flavours separately
  * render-bitmaps: Support searching for icons by category
  * github: Add automated workflow to optimize SVG
  * github: Do a full icons rebuild if the renderer script changes
  * icons/generate-symlinks.sh: Ignore empty lines on list file
  * icons/phosh.list: Remove trailing empty line
  * CI: Split build workflow in multiple steps
  * icons: Add tests to try generating symlinks
  * meson: Use more fs filename modifications functions
  * Revert "icons: modify meson and deb files (LP: #1965649)
  * github: Fix Links on generated PRs
  * meson: Bump dependency to 0.59 as per fs.parent() usage
  * icons: Install panel icons only if mate or unity are enabled
  * icons: Ensure symlinks are all generated from symlink script
  * icons/scalable: Remove icons that are already handled via symlinks
  * icons: Remove all the links in source dirs, they should be handled via lists
  * CI: Recreate symlinks removing old ones
  * CI: Detect changes on all symlinks files
  * CI: Ensure that no symlinks are used in icon sources
  * CI: Use inverse logic, we don't want symlinks :)
  * CI: Cleanup rendered icons before render them again
  * icons/accented: Remove software store from accented icons
  * gnome-shell: Use correct syntax for or'ed find
  * CI: Archive meson logs
  * generate-index-theme: Support excluding a specific icons directory
  * icons: Also generate symlinks for 22x22 icons
  * icons: Generate panel symlinks, and install them only when needed
  * generate-index-theme: Handle the scalable min/max size cases
  * generate-index-theme: Use proper context names when not computable
  * icons: Auto-generate index.theme for default and mate icon themes
  * generate-index-theme: Support excluding elements by context
  * generate-index-theme: Support providing custom parameters for a folder
  * icons: Replicate symlinks in installed folder when using meson >= 0.61
  * icons: Use nicer way to compute find command for excluded folders
  * gnome-shell: Use native meson symlink installer when possible
  * icons, gnome-shell: Use python-computed relative paths
  * CI: Make meson options more readable in full build
  * gnome-shell: Add further option to toggle UserThemes support
  * debian/rules: Enable user themes support in packages
  * icons: Add more accented icons
  * icons: Use better name for rendered icon target
  * gtk, gnome-shell: Only generate Yaru-$accent-dark themes if `dark` is set
  * icons: Generate dark variants of the icons theme
  * CI: Also consider untracked changes on rendering/optimizing icons
  * CI: Use proper syntax to check on rendered icons changes
  * icons: Install icons symlinks as such also with older meson versions
  * icons: Inherit dark accented variants from Yaru-dark as primary choice
  * yaru-colors-defs: Use a map to define colors so we can avoid repetitions
  * yaru-colors-defs: Ensure we always generate opaque colors
  * yaru-colors-defs: Use more css-style generated definitions
  * gnome-shell: Use proper name for generated target output name
  * gnome-shell: Define custom checkbox bg color and expose bg-color as such
  * icons/symlinks: avoid using symlinks to symlinks not to confuse generator
  * icons: Add speaker icons for mate
  * debian: Include new installed files to proper package

  [ Martin Wimpress ]
  * metacity: Correct Metacity theme contrast so they match GNOME/CSD windows
  * gtk: Add MetacityThemeName to index.theme
  * metacity: Correct titlebar contrast for default and dark themes
  * mate: Restore MATE icons
  * icons: Remove Humanity icons languishing in legacy
  * mate: Drop unnecessary MATE variations of GtkSourceView and Metacity themes
  * icons: Add ulauncher panel icons
  * metacity: Add window buttons to modal windows (LP: #1917185)
  * icons: Add symlinks for fullcolor printer and printers icons
  * icons: Add symlinks for more MATE apps
  * icons: Fix preferences-system.png collision and add more MATE symlinks
  * icons: Add redshift and steam panel icons
  * icons: Add symlink for preferences-desktop-default-applications.png
  * gtk: Add gtk-2.0 themes for color accents (LP: #1965659)
  * icons: Create dark theme subfolders and symlink categories
  * icons: Add Dropbox, Remmina, Transmission & audacious panel icons
(LP: #964518, LP: #1949312)

  [ Lyubomir Popov ]
  * accent colours: subtler purple, magenta and red
  * accent colours: adjust hue of the red color
  * adjust hue of magenta so it corresponds better t

[Desktop-packages] [Bug 1949312] Re: Transmission icon Ubuntu MATE doesn´t fit overall icontheme

This bug was fixed in the package yaru-theme - 22.04.3.1

---
yaru-theme (22.04.3.1) jammy; urgency=medium

  [ Marco Trevisan (Treviño) ]
  * gtk: Do not use shell scss sources to define accent colors used by icons
  * github: Generate rendered icons and symlinks automatically
  * icons: Use more predicibile rendering target names
  * meson: Render each icon separately to use multi-process rendering
  * render-bitmaps: Fail in case no SVG is rendered
  * meson: Allow to render one icon across all the flavours separately
  * render-bitmaps: Support searching for icons by category
  * github: Add automated workflow to optimize SVG
  * github: Do a full icons rebuild if the renderer script changes
  * icons/generate-symlinks.sh: Ignore empty lines on list file
  * icons/phosh.list: Remove trailing empty line
  * CI: Split build workflow in multiple steps
  * icons: Add tests to try generating symlinks
  * meson: Use more fs filename modifications functions
  * Revert "icons: modify meson and deb files (LP: #1965649)
  * github: Fix Links on generated PRs
  * meson: Bump dependency to 0.59 as per fs.parent() usage
  * icons: Install panel icons only if mate or unity are enabled
  * icons: Ensure symlinks are all generated from symlink script
  * icons/scalable: Remove icons that are already handled via symlinks
  * icons: Remove all the links in source dirs, they should be handled via lists
  * CI: Recreate symlinks removing old ones
  * CI: Detect changes on all symlinks files
  * CI: Ensure that no symlinks are used in icon sources
  * CI: Use inverse logic, we don't want symlinks :)
  * CI: Cleanup rendered icons before render them again
  * icons/accented: Remove software store from accented icons
  * gnome-shell: Use correct syntax for or'ed find
  * CI: Archive meson logs
  * generate-index-theme: Support excluding a specific icons directory
  * icons: Also generate symlinks for 22x22 icons
  * icons: Generate panel symlinks, and install them only when needed
  * generate-index-theme: Handle the scalable min/max size cases
  * generate-index-theme: Use proper context names when not computable
  * icons: Auto-generate index.theme for default and mate icon themes
  * generate-index-theme: Support excluding elements by context
  * generate-index-theme: Support providing custom parameters for a folder
  * icons: Replicate symlinks in installed folder when using meson >= 0.61
  * icons: Use nicer way to compute find command for excluded folders
  * gnome-shell: Use native meson symlink installer when possible
  * icons, gnome-shell: Use python-computed relative paths
  * CI: Make meson options more readable in full build
  * gnome-shell: Add further option to toggle UserThemes support
  * debian/rules: Enable user themes support in packages
  * icons: Add more accented icons
  * icons: Use better name for rendered icon target
  * gtk, gnome-shell: Only generate Yaru-$accent-dark themes if `dark` is set
  * icons: Generate dark variants of the icons theme
  * CI: Also consider untracked changes on rendering/optimizing icons
  * CI: Use proper syntax to check on rendered icons changes
  * icons: Install icons symlinks as such also with older meson versions
  * icons: Inherit dark accented variants from Yaru-dark as primary choice
  * yaru-colors-defs: Use a map to define colors so we can avoid repetitions
  * yaru-colors-defs: Ensure we always generate opaque colors
  * yaru-colors-defs: Use more css-style generated definitions
  * gnome-shell: Use proper name for generated target output name
  * gnome-shell: Define custom checkbox bg color and expose bg-color as such
  * icons/symlinks: avoid using symlinks to symlinks not to confuse generator
  * icons: Add speaker icons for mate
  * debian: Include new installed files to proper package

  [ Martin Wimpress ]
  * metacity: Correct Metacity theme contrast so they match GNOME/CSD windows
  * gtk: Add MetacityThemeName to index.theme
  * metacity: Correct titlebar contrast for default and dark themes
  * mate: Restore MATE icons
  * icons: Remove Humanity icons languishing in legacy
  * mate: Drop unnecessary MATE variations of GtkSourceView and Metacity themes
  * icons: Add ulauncher panel icons
  * metacity: Add window buttons to modal windows (LP: #1917185)
  * icons: Add symlinks for fullcolor printer and printers icons
  * icons: Add symlinks for more MATE apps
  * icons: Fix preferences-system.png collision and add more MATE symlinks
  * icons: Add redshift and steam panel icons
  * icons: Add symlink for preferences-desktop-default-applications.png
  * gtk: Add gtk-2.0 themes for color accents (LP: #1965659)
  * icons: Create dark theme subfolders and symlink categories
  * icons: Add Dropbox, Remmina, Transmission & audacious panel icons
(LP: #964518, LP: #1949312)

  [ Lyubomir Popov ]
  * accent colours: subtler purple, magenta and red
  * accent colours: adjust hue of the red color
  * adjust hue of magenta so it corresponds better t

[Desktop-packages] [Bug 1965207] Re: The spinner animation in the panel has hiccups and jumps periodically

This bug was fixed in the package yaru-theme - 22.04.3.1

---
yaru-theme (22.04.3.1) jammy; urgency=medium

  [ Marco Trevisan (Treviño) ]
  * gtk: Do not use shell scss sources to define accent colors used by icons
  * github: Generate rendered icons and symlinks automatically
  * icons: Use more predicibile rendering target names
  * meson: Render each icon separately to use multi-process rendering
  * render-bitmaps: Fail in case no SVG is rendered
  * meson: Allow to render one icon across all the flavours separately
  * render-bitmaps: Support searching for icons by category
  * github: Add automated workflow to optimize SVG
  * github: Do a full icons rebuild if the renderer script changes
  * icons/generate-symlinks.sh: Ignore empty lines on list file
  * icons/phosh.list: Remove trailing empty line
  * CI: Split build workflow in multiple steps
  * icons: Add tests to try generating symlinks
  * meson: Use more fs filename modifications functions
  * Revert "icons: modify meson and deb files (LP: #1965649)
  * github: Fix Links on generated PRs
  * meson: Bump dependency to 0.59 as per fs.parent() usage
  * icons: Install panel icons only if mate or unity are enabled
  * icons: Ensure symlinks are all generated from symlink script
  * icons/scalable: Remove icons that are already handled via symlinks
  * icons: Remove all the links in source dirs, they should be handled via lists
  * CI: Recreate symlinks removing old ones
  * CI: Detect changes on all symlinks files
  * CI: Ensure that no symlinks are used in icon sources
  * CI: Use inverse logic, we don't want symlinks :)
  * CI: Cleanup rendered icons before render them again
  * icons/accented: Remove software store from accented icons
  * gnome-shell: Use correct syntax for or'ed find
  * CI: Archive meson logs
  * generate-index-theme: Support excluding a specific icons directory
  * icons: Also generate symlinks for 22x22 icons
  * icons: Generate panel symlinks, and install them only when needed
  * generate-index-theme: Handle the scalable min/max size cases
  * generate-index-theme: Use proper context names when not computable
  * icons: Auto-generate index.theme for default and mate icon themes
  * generate-index-theme: Support excluding elements by context
  * generate-index-theme: Support providing custom parameters for a folder
  * icons: Replicate symlinks in installed folder when using meson >= 0.61
  * icons: Use nicer way to compute find command for excluded folders
  * gnome-shell: Use native meson symlink installer when possible
  * icons, gnome-shell: Use python-computed relative paths
  * CI: Make meson options more readable in full build
  * gnome-shell: Add further option to toggle UserThemes support
  * debian/rules: Enable user themes support in packages
  * icons: Add more accented icons
  * icons: Use better name for rendered icon target
  * gtk, gnome-shell: Only generate Yaru-$accent-dark themes if `dark` is set
  * icons: Generate dark variants of the icons theme
  * CI: Also consider untracked changes on rendering/optimizing icons
  * CI: Use proper syntax to check on rendered icons changes
  * icons: Install icons symlinks as such also with older meson versions
  * icons: Inherit dark accented variants from Yaru-dark as primary choice
  * yaru-colors-defs: Use a map to define colors so we can avoid repetitions
  * yaru-colors-defs: Ensure we always generate opaque colors
  * yaru-colors-defs: Use more css-style generated definitions
  * gnome-shell: Use proper name for generated target output name
  * gnome-shell: Define custom checkbox bg color and expose bg-color as such
  * icons/symlinks: avoid using symlinks to symlinks not to confuse generator
  * icons: Add speaker icons for mate
  * debian: Include new installed files to proper package

  [ Martin Wimpress ]
  * metacity: Correct Metacity theme contrast so they match GNOME/CSD windows
  * gtk: Add MetacityThemeName to index.theme
  * metacity: Correct titlebar contrast for default and dark themes
  * mate: Restore MATE icons
  * icons: Remove Humanity icons languishing in legacy
  * mate: Drop unnecessary MATE variations of GtkSourceView and Metacity themes
  * icons: Add ulauncher panel icons
  * metacity: Add window buttons to modal windows (LP: #1917185)
  * icons: Add symlinks for fullcolor printer and printers icons
  * icons: Add symlinks for more MATE apps
  * icons: Fix preferences-system.png collision and add more MATE symlinks
  * icons: Add redshift and steam panel icons
  * icons: Add symlink for preferences-desktop-default-applications.png
  * gtk: Add gtk-2.0 themes for color accents (LP: #1965659)
  * icons: Create dark theme subfolders and symlink categories
  * icons: Add Dropbox, Remmina, Transmission & audacious panel icons
(LP: #964518, LP: #1949312)

  [ Lyubomir Popov ]
  * accent colours: subtler purple, magenta and red
  * accent colours: adjust hue of the red color
  * adjust hue of magenta so it corresponds better t

[Desktop-packages] [Bug 1965210] Re: Grey (gray) panel menus don't contrast with the grey login screen

This bug was fixed in the package yaru-theme - 22.04.3.1

---
yaru-theme (22.04.3.1) jammy; urgency=medium

  [ Marco Trevisan (Treviño) ]
  * gtk: Do not use shell scss sources to define accent colors used by icons
  * github: Generate rendered icons and symlinks automatically
  * icons: Use more predicibile rendering target names
  * meson: Render each icon separately to use multi-process rendering
  * render-bitmaps: Fail in case no SVG is rendered
  * meson: Allow to render one icon across all the flavours separately
  * render-bitmaps: Support searching for icons by category
  * github: Add automated workflow to optimize SVG
  * github: Do a full icons rebuild if the renderer script changes
  * icons/generate-symlinks.sh: Ignore empty lines on list file
  * icons/phosh.list: Remove trailing empty line
  * CI: Split build workflow in multiple steps
  * icons: Add tests to try generating symlinks
  * meson: Use more fs filename modifications functions
  * Revert "icons: modify meson and deb files (LP: #1965649)
  * github: Fix Links on generated PRs
  * meson: Bump dependency to 0.59 as per fs.parent() usage
  * icons: Install panel icons only if mate or unity are enabled
  * icons: Ensure symlinks are all generated from symlink script
  * icons/scalable: Remove icons that are already handled via symlinks
  * icons: Remove all the links in source dirs, they should be handled via lists
  * CI: Recreate symlinks removing old ones
  * CI: Detect changes on all symlinks files
  * CI: Ensure that no symlinks are used in icon sources
  * CI: Use inverse logic, we don't want symlinks :)
  * CI: Cleanup rendered icons before render them again
  * icons/accented: Remove software store from accented icons
  * gnome-shell: Use correct syntax for or'ed find
  * CI: Archive meson logs
  * generate-index-theme: Support excluding a specific icons directory
  * icons: Also generate symlinks for 22x22 icons
  * icons: Generate panel symlinks, and install them only when needed
  * generate-index-theme: Handle the scalable min/max size cases
  * generate-index-theme: Use proper context names when not computable
  * icons: Auto-generate index.theme for default and mate icon themes
  * generate-index-theme: Support excluding elements by context
  * generate-index-theme: Support providing custom parameters for a folder
  * icons: Replicate symlinks in installed folder when using meson >= 0.61
  * icons: Use nicer way to compute find command for excluded folders
  * gnome-shell: Use native meson symlink installer when possible
  * icons, gnome-shell: Use python-computed relative paths
  * CI: Make meson options more readable in full build
  * gnome-shell: Add further option to toggle UserThemes support
  * debian/rules: Enable user themes support in packages
  * icons: Add more accented icons
  * icons: Use better name for rendered icon target
  * gtk, gnome-shell: Only generate Yaru-$accent-dark themes if `dark` is set
  * icons: Generate dark variants of the icons theme
  * CI: Also consider untracked changes on rendering/optimizing icons
  * CI: Use proper syntax to check on rendered icons changes
  * icons: Install icons symlinks as such also with older meson versions
  * icons: Inherit dark accented variants from Yaru-dark as primary choice
  * yaru-colors-defs: Use a map to define colors so we can avoid repetitions
  * yaru-colors-defs: Ensure we always generate opaque colors
  * yaru-colors-defs: Use more css-style generated definitions
  * gnome-shell: Use proper name for generated target output name
  * gnome-shell: Define custom checkbox bg color and expose bg-color as such
  * icons/symlinks: avoid using symlinks to symlinks not to confuse generator
  * icons: Add speaker icons for mate
  * debian: Include new installed files to proper package

  [ Martin Wimpress ]
  * metacity: Correct Metacity theme contrast so they match GNOME/CSD windows
  * gtk: Add MetacityThemeName to index.theme
  * metacity: Correct titlebar contrast for default and dark themes
  * mate: Restore MATE icons
  * icons: Remove Humanity icons languishing in legacy
  * mate: Drop unnecessary MATE variations of GtkSourceView and Metacity themes
  * icons: Add ulauncher panel icons
  * metacity: Add window buttons to modal windows (LP: #1917185)
  * icons: Add symlinks for fullcolor printer and printers icons
  * icons: Add symlinks for more MATE apps
  * icons: Fix preferences-system.png collision and add more MATE symlinks
  * icons: Add redshift and steam panel icons
  * icons: Add symlink for preferences-desktop-default-applications.png
  * gtk: Add gtk-2.0 themes for color accents (LP: #1965659)
  * icons: Create dark theme subfolders and symlink categories
  * icons: Add Dropbox, Remmina, Transmission & audacious panel icons
(LP: #964518, LP: #1949312)

  [ Lyubomir Popov ]
  * accent colours: subtler purple, magenta and red
  * accent colours: adjust hue of the red color
  * adjust hue of magenta so it corresponds better t

[Desktop-packages] [Bug 1965659] Re: Yaru color themes make GTK 2.0 apps unreadable white

This bug was fixed in the package yaru-theme - 22.04.3.1

---
yaru-theme (22.04.3.1) jammy; urgency=medium

  [ Marco Trevisan (Treviño) ]
  * gtk: Do not use shell scss sources to define accent colors used by icons
  * github: Generate rendered icons and symlinks automatically
  * icons: Use more predicibile rendering target names
  * meson: Render each icon separately to use multi-process rendering
  * render-bitmaps: Fail in case no SVG is rendered
  * meson: Allow to render one icon across all the flavours separately
  * render-bitmaps: Support searching for icons by category
  * github: Add automated workflow to optimize SVG
  * github: Do a full icons rebuild if the renderer script changes
  * icons/generate-symlinks.sh: Ignore empty lines on list file
  * icons/phosh.list: Remove trailing empty line
  * CI: Split build workflow in multiple steps
  * icons: Add tests to try generating symlinks
  * meson: Use more fs filename modifications functions
  * Revert "icons: modify meson and deb files (LP: #1965649)
  * github: Fix Links on generated PRs
  * meson: Bump dependency to 0.59 as per fs.parent() usage
  * icons: Install panel icons only if mate or unity are enabled
  * icons: Ensure symlinks are all generated from symlink script
  * icons/scalable: Remove icons that are already handled via symlinks
  * icons: Remove all the links in source dirs, they should be handled via lists
  * CI: Recreate symlinks removing old ones
  * CI: Detect changes on all symlinks files
  * CI: Ensure that no symlinks are used in icon sources
  * CI: Use inverse logic, we don't want symlinks :)
  * CI: Cleanup rendered icons before render them again
  * icons/accented: Remove software store from accented icons
  * gnome-shell: Use correct syntax for or'ed find
  * CI: Archive meson logs
  * generate-index-theme: Support excluding a specific icons directory
  * icons: Also generate symlinks for 22x22 icons
  * icons: Generate panel symlinks, and install them only when needed
  * generate-index-theme: Handle the scalable min/max size cases
  * generate-index-theme: Use proper context names when not computable
  * icons: Auto-generate index.theme for default and mate icon themes
  * generate-index-theme: Support excluding elements by context
  * generate-index-theme: Support providing custom parameters for a folder
  * icons: Replicate symlinks in installed folder when using meson >= 0.61
  * icons: Use nicer way to compute find command for excluded folders
  * gnome-shell: Use native meson symlink installer when possible
  * icons, gnome-shell: Use python-computed relative paths
  * CI: Make meson options more readable in full build
  * gnome-shell: Add further option to toggle UserThemes support
  * debian/rules: Enable user themes support in packages
  * icons: Add more accented icons
  * icons: Use better name for rendered icon target
  * gtk, gnome-shell: Only generate Yaru-$accent-dark themes if `dark` is set
  * icons: Generate dark variants of the icons theme
  * CI: Also consider untracked changes on rendering/optimizing icons
  * CI: Use proper syntax to check on rendered icons changes
  * icons: Install icons symlinks as such also with older meson versions
  * icons: Inherit dark accented variants from Yaru-dark as primary choice
  * yaru-colors-defs: Use a map to define colors so we can avoid repetitions
  * yaru-colors-defs: Ensure we always generate opaque colors
  * yaru-colors-defs: Use more css-style generated definitions
  * gnome-shell: Use proper name for generated target output name
  * gnome-shell: Define custom checkbox bg color and expose bg-color as such
  * icons/symlinks: avoid using symlinks to symlinks not to confuse generator
  * icons: Add speaker icons for mate
  * debian: Include new installed files to proper package

  [ Martin Wimpress ]
  * metacity: Correct Metacity theme contrast so they match GNOME/CSD windows
  * gtk: Add MetacityThemeName to index.theme
  * metacity: Correct titlebar contrast for default and dark themes
  * mate: Restore MATE icons
  * icons: Remove Humanity icons languishing in legacy
  * mate: Drop unnecessary MATE variations of GtkSourceView and Metacity themes
  * icons: Add ulauncher panel icons
  * metacity: Add window buttons to modal windows (LP: #1917185)
  * icons: Add symlinks for fullcolor printer and printers icons
  * icons: Add symlinks for more MATE apps
  * icons: Fix preferences-system.png collision and add more MATE symlinks
  * icons: Add redshift and steam panel icons
  * icons: Add symlink for preferences-desktop-default-applications.png
  * gtk: Add gtk-2.0 themes for color accents (LP: #1965659)
  * icons: Create dark theme subfolders and symlink categories
  * icons: Add Dropbox, Remmina, Transmission & audacious panel icons
(LP: #964518, LP: #1949312)

  [ Lyubomir Popov ]
  * accent colours: subtler purple, magenta and red
  * accent colours: adjust hue of the red color
  * adjust hue of magenta so it corresponds better t

[Desktop-packages] [Bug 1965649] Re: package yaru-theme-icon 22.04.2 failed to install/upgrade: trying to overwrite '/usr/share/icons/Yaru/16x16/panel/a11y.svg', which is also in package yaru-theme-un