[Bug 1946042] Re: Ubuntu Dock changes look/breaks in High Contrast

[Daniel van Vugt]

** 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 Ubuntu
Desktop Bugs, 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

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


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

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

[Launchpad Bug Tracker]

[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 Ubuntu
Desktop Bugs, 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()

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


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

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

[Launchpad Bug Tracker]

[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 Ubuntu
Desktop Bugs, which is subscribed to tracker in Ubuntu.
https://bugs.launchpad.net/bugs/1780296

Title:
  [SRU] Update to bugfix 2.0.5 in Bionic

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


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

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

[Launchpad Bug Tracker]

[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 Ubuntu
Desktop Bugs, 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()

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


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

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

[Launchpad Bug Tracker]

[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 Ubuntu
Desktop Bugs, which is subscribed to tracker-miners in Ubuntu.
https://bugs.launchpad.net/bugs/1724971

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

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


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

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

[Launchpad Bug Tracker]

[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 Ubuntu
Desktop Bugs, which is subscribed to tracker in Ubuntu.
https://bugs.launchpad.net/bugs/1780296

Title:
  [SRU] Update to bugfix 2.0.5 in Bionic

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


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

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

[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 Ubuntu
Desktop Bugs, which is subscribed to gnome-calculator in Ubuntu.
https://bugs.launchpad.net/bugs/1967037

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

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


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[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)

[Daniel van Vugt]

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 Ubuntu
Desktop Bugs, which is subscribed to mutter 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)

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


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

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

[Daniel van Vugt]

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 Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1966921

Title:
  Display freezes after entering password from login screen

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


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[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)

[Prajjwal Devkota]

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 Ubuntu
Desktop Bugs, which is subscribed to mutter 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)

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


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[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)

[Prajjwal Devkota]

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 Ubuntu
Desktop Bugs, which is subscribed to mutter 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)

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


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

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

[Daniel van Vugt]

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 Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1967011

Title:
  Unable to Share Screen via PipeWire in OBS Studio

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


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[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)

[Daniel van Vugt]

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 Ubuntu
Desktop Bugs, which is subscribed to mutter 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)

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


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1966786] Re: login screen shown twice

[Daniel van Vugt]

** 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 Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
https://bugs.launchpad.net/bugs/1966786

Title:
  login screen shown twice

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


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1967025] Re: Double login screen

[Daniel van Vugt]

*** 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 Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1967025

Title:
  Double login screen

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


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

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

[Gunnar Hjalmarsson]

** 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 Ubuntu
Desktop Bugs, which is subscribed to ibus-libpinyin in Ubuntu.
https://bugs.launchpad.net/bugs/1966552

Title:
  IBus input method candidate box cannot follow the cursor

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


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

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

[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 Ubuntu
Desktop Bugs, which is subscribed to nautilus 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

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


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1967025] Re: Double login screen

[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 Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1967025

Title:
  Double login screen

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


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1967025] [NEW] Double login screen

[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 Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1967025

Title:
  Double login screen

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


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1965798] Re: evolution crashed with SIGSEGV using WAYLAND

[Launchpad Bug Tracker]

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

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

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

Title:
  evolution crashed with SIGSEGV using WAYLAND

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


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1967022] Re: evolution crashed with SIGSEGV

[Apport retracing service]

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

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 #1965798, 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/1967022/+attachment/5574459/+files/CoreDump.gz

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

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

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

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

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

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

** This bug has been marked a duplicate of bug 1965798
   evolution crashed with SIGSEGV using WAYLAND

** Tags removed: need-amd64-retrace

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

Title:
  evolution crashed with SIGSEGV

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


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

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

[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 Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1967011

Title:
  Unable to Share Screen via PipeWire in OBS Studio

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


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1967022] [NEW] evolution crashed with SIGSEGV

[Erich Eickmeyer ]

Public bug reported:

Possibly related to bug 1967020

ProblemType: Crash
DistroRelease: Ubuntu 22.04
Package: evolution 3.44.0-1
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
CurrentDesktop: ubuntu:GNOME
Date: Tue Mar 29 17:16:04 2022
ExecutablePath: /usr/bin/evolution
InstallationDate: Installed on 2021-08-19 (222 days ago)
InstallationMedia: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210818)
ProcCmdline: evolution
ProcEnviron:
 PATH=(custom, user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7f859f07930b:  mov0x8,%rax
 PC (0x7f859f07930b) ok
 source "0x8" (0x0008) not located in a known VMA region (needed readable 
region)!
 destination "%rax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: evolution
StacktraceTop:
 () at /lib/x86_64-linux-gnu/libwebkit2gtk-4.0.so.37
 () at /lib/x86_64-linux-gnu/libffi.so.8
 () at /lib/x86_64-linux-gnu/libffi.so.8
 () at /lib/x86_64-linux-gnu/libwayland-server.so.0
 () at /lib/x86_64-linux-gnu/libwayland-server.so.0
Title: evolution crashed with SIGSEGV
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm audio cdrom dip lpadmin lxd plugdev sambashare sudo
separator:

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


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

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

Title:
  evolution crashed with SIGSEGV

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


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

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

[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 Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1965219

Title:
  gnome lock screen does not permit reentering password

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


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

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

[Martin Wimpress ]

** Information type changed from Private to Public

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

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

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


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

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

[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 Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1967011

Title:
  Unable to Share Screen via PipeWire in OBS Studio

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


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

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

[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 

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

[Paul White]

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 Ubuntu
Desktop Bugs, 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)

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


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

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

[Brian Murray]

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

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, 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

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


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

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

[Paul White]

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 Ubuntu
Desktop Bugs, 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

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


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1931494] Re: Wrong scaling

[Paul White]

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 Ubuntu
Desktop Bugs, which is subscribed to evince in Ubuntu.
https://bugs.launchpad.net/bugs/1931494

Title:
  Wrong scaling

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


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

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

[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 Ubuntu
Desktop Bugs, which is subscribed to epiphany-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1966418

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

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


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

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

[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 Ubuntu
Desktop Bugs, which is subscribed to epiphany-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1966418

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

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


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

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

[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 Ubuntu
Desktop Bugs, which is subscribed to gvfs in Ubuntu.
https://bugs.launchpad.net/bugs/1927100

Title:
  Slow file dialogs, open and save

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


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

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

[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 Ubuntu
Desktop Bugs, which is subscribed to evince in Ubuntu.
https://bugs.launchpad.net/bugs/1915910

Title:
  evince does not print (apparmor, pxgsettings)

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


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1966980] [NEW] GIMP crashes as soon as text tool is used

[Andrew Packer]

Public bug reported:

```
GNU Image Manipulation Program version 2.10.18
git-describe: GIMP_2_10_16-38-gde7f04567d
Build: unknown rev 0 for linux
# C compiler #
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/9/lto-wrapper
OFFLOAD_TARGET_NAMES=nvptx-none:hsa
OFFLOAD_TARGET_DEFAULT=1
Target: x86_64-linux-gnu
Configured with: ../src/configure -v --with-pkgversion='Ubuntu 
9.3.0-8ubuntu1' --with-bugurl=file:///usr/share/doc/gcc-9/README.Bugs 
--enable-languages=c,ada,c++,go,brig,d,fortran,objc,obj-c++,gm2 --prefix=/usr 
--with-gcc-major-version-only --program-suffix=-9 
--program-prefix=x86_64-linux-gnu- --enable-shared --enable-linker-build-id 
--libexecdir=/usr/lib --without-included-gettext --enable-threads=posix 
--libdir=/usr/lib --enable-nls --enable-clocale=gnu --enable-libstdcxx-debug 
--enable-libstdcxx-time=yes --with-default-libstdcxx-abi=new 
--enable-gnu-unique-object --disable-vtable-verify --enable-plugin 
--enable-default-pie --with-system-zlib --with-target-system-zlib=auto 
--enable-objc-gc=auto --enable-multiarch --disable-werror --with-arch-32=i686 
--with-abi=m64 --with-multilib-list=m32,m64,mx32 --enable-multilib 
--with-tune=generic --enable-offload-targets=nvptx-none,hsa 
--without-cuda-driver --enable-checking=release --build=x86_64-linux-gnu 
--host=x86_64-linux-gnu --target=x86_64-linux-gnu
Thread model: posix
gcc version 9.3.0 (Ubuntu 9.3.0-8ubuntu1) 

# Libraries #
using babl version 0.1.74 (compiled against version 0.1.74)
using GEGL version 0.4.22 (compiled against version 0.4.22)
using GLib version 2.64.6 (compiled against version 2.64.1)
using GdkPixbuf version 2.40.0 (compiled against version 2.40.0)
using GTK+ version 2.24.32 (compiled against version 2.24.32)
using Pango version 1.44.7 (compiled against version 1.44.7)
using Fontconfig version 2.13.1 (compiled against version 2.13.1)
using Cairo version 1.16.0 (compiled against version 1.16.0)

```
> GIMP-CRITICAL: gimp_tool_key_press: assertion 'gimp_tool_control_is_active 
> (tool->control) == FALSE' failed

Stack trace:
```

# Stack traces obtained from PID 28234 - Thread 28234 #

[New LWP 28236]
[New LWP 28237]
[New LWP 28238]
[New LWP 28250]
[New LWP 28251]
[New LWP 28259]
[New LWP 28297]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
__libc_read (nbytes=256, buf=0x7ffd6d110d10, fd=15) at 
../sysdeps/unix/sysv/linux/read.c:26
  Id   Target Id   Frame 
* 1Thread 0x7f9d8c631340 (LWP 28234) "gimp-2.10"   __libc_read (nbytes=256, 
buf=0x7ffd6d110d10, fd=15) at ../sysdeps/unix/sysv/linux/read.c:26
  2Thread 0x7f9d8beca700 (LWP 28236) "worker"  syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  3Thread 0x7f9d8b6c9700 (LWP 28237) "worker"  syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  4Thread 0x7f9d8aec8700 (LWP 28238) "worker"  syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  5Thread 0x7f9d5a7e8700 (LWP 28250) "gmain"   0x7f9d8d46c9cf in 
__GI___poll (fds=0x5634fef2c370, nfds=2, timeout=-1) at 
../sysdeps/unix/sysv/linux/poll.c:29
  6Thread 0x7f9d5cfe9700 (LWP 28251) "gdbus"   0x7f9d8d46c9cf in 
__GI___poll (fds=0x5634fef444b0, nfds=2, timeout=-1) at 
../sysdeps/unix/sysv/linux/poll.c:29
  7Thread 0x7f9d896c5700 (LWP 28259) "async"   syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  8Thread 0x7f9d7bfff700 (LWP 28297) "swap writer" syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38

Thread 8 (Thread 0x7f9d7bfff700 (LWP 28297)):
#0  syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
No locals.
#1  0x7f9d8d765623 in g_cond_wait () from 
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
No symbol table info available.
#2  0x7f9d8dc65aad in ?? () from /usr/lib/x86_64-linux-gnu/libgegl-0.4.so.0
No symbol table info available.
#3  0x7f9d8d741ad1 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
No symbol table info available.
#4  0x7f9d8d554609 in start_thread (arg=) at 
pthread_create.c:477
ret = 
pd = 
unwind_buf = {cancel_jmp_buf = {{jmp_buf = {140314366965504, 
3992424551288561243, 140726433284430, 140726433284431, 140726433284576, 
140314366961792, -4009040371817750949, -4009071936541270437}, mask_was_saved = 
0}}, priv = {pad = {0x0, 0x0, 0x0, 0x0}, data = {prev = 0x0, cleanup = 0x0, 
canceltype = 0}}}
not_first_call = 0
#5  0x7f9d8d479163 in clone () at 
../sysdeps/unix/sysv/linux/x86_64/clone.S:95
No locals.

Thread 7 (Thread 0x7f9d896c5700 (LWP 28259)):
#0  syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
No locals.
#1  0x7f9d8d765623 in g_cond_wait () from 
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
No symbol table info available.
#2  0x5634fe290d84 in ?? ()
No symbol table info available.

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

[Launchpad Bug Tracker]

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 Ubuntu
Desktop Bugs, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/1962761

Title:
  nautilus crashed with SIGSEGV in gtk_widget_get_ancestor()

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


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

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

[Launchpad Bug Tracker]

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 Ubuntu
Desktop Bugs, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/1965558

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

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


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

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

[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 Ubuntu
Desktop Bugs, 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

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


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

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

[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 Ubuntu
Desktop Bugs, 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

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


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

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

[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 Ubuntu
Desktop Bugs, 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

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


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1966221] Re: gnome-extensions-app crashes with "Segmentation fault (core dumped)"

[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 Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1966221

Title:
  gnome-extensions-app crashes with "Segmentation fault (core dumped)"

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


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

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

[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 Ubuntu
Desktop Bugs, 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

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


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1966786] Re: login screen shown twice

[BertN45]

I did found the following crash report from yesterday in /var/crash and
I think it has already been uploaded automatically.

** Attachment added: "_usr_lib_update-notifier_list-oem-metapackages.1000.crash"
   
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1966786/+attachment/5574329/+files/_usr_lib_update-notifier_list-oem-metapackages.1000.crash

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

Title:
  login screen shown twice

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


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1966949] Re: gvfsd-mtp crashed with SIGSEGV in ___pthread_mutex_lock()

[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 Ubuntu
Desktop Bugs, which is subscribed to gvfs in Ubuntu.
https://bugs.launchpad.net/bugs/1966949

Title:
  gvfsd-mtp crashed with SIGSEGV in ___pthread_mutex_lock()

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


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1966947] Re: nautilus crashed with SIGSEGV in gtk_widget_get_ancestor()

[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 Ubuntu
Desktop Bugs, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/1966947

Title:
  nautilus crashed with SIGSEGV in gtk_widget_get_ancestor()

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


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

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

[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 Ubuntu
Desktop Bugs, which is subscribed to epiphany-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1966418

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

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


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[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)

[Prajjwal Devkota]

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 Ubuntu
Desktop Bugs, which is subscribed to mutter 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)

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


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[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)

[Prajjwal Devkota]

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 Ubuntu
Desktop Bugs, which is subscribed to mutter 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)

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


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1965696] Re: Shell keyboard navigation (after pressing Ctrl+Alt+Tab) doesn't work in Xorg sessions

[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 Ubuntu
Desktop Bugs, 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

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


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1966418]

[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 Ubuntu
Desktop Bugs, which is subscribed to epiphany-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1966418

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

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


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1966418]

[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 Ubuntu
Desktop Bugs, which is subscribed to epiphany-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1966418

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

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


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1966418]

[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 Ubuntu
Desktop Bugs, which is subscribed to epiphany-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1966418

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

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


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1966418]

[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 Ubuntu
Desktop Bugs, which is subscribed to epiphany-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1966418

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

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


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1966418]

[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 Ubuntu
Desktop Bugs, which is subscribed to epiphany-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1966418

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

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


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1966418]

[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 Ubuntu
Desktop Bugs, which is subscribed to epiphany-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1966418

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

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


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1965696] Re: Shell keyboard navigation (after pressing Ctrl+Alt+Tab) doesn't work in Xorg sessions

[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 Ubuntu
Desktop Bugs, 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

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


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1966007] Re: Flood of Bluetooth Malicious advertisind data

[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 Ubuntu
Desktop Bugs, which is subscribed to gnome-terminal in Ubuntu.
https://bugs.launchpad.net/bugs/1966007

Title:
  Flood of Bluetooth Malicious advertisind data

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


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1966221] Re: gnome-extensions-app crashes with "Segmentation fault (core dumped)"

[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 Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1966221

Title:
  gnome-extensions-app crashes with "Segmentation fault (core dumped)"

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


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[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)

[Daniel van Vugt]

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 Ubuntu
Desktop Bugs, which is subscribed to mutter 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)

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


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1966524] Re: yelp crashed with SIGSEGV

[Sebastien Bacher]

** Information type changed from Private to Public

** Summary changed:

- yelp crashed with SIGSEGV
+ yelp crashed with SIGSEGV in  WebKit::WaylandCompositor::Buffer::createImage

** Package changed: yelp (Ubuntu) => webkitgtk (Ubuntu)

** Package changed: webkitgtk (Ubuntu) => webkit2gtk (Ubuntu)

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

Title:
  yelp crashed with SIGSEGV in
  WebKit::WaylandCompositor::Buffer::createImage

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


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1966502] Re: gjs-console crashed with SIGSEGV

[Sebastien Bacher]

** Package changed: gjs (Ubuntu) => mesa (Ubuntu)

** Summary changed:

- gjs-console crashed with SIGSEGV
+ gjs-console crashed with SIGSEGV in lookup_opcode_desc under X

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

Title:
  gjs-console crashed with SIGSEGV in lookup_opcode_desc under X

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


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

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

[Sebastien Bacher]

sorry but the description is unclear, you mention that it doesn't work
in wayland, is that the issue you report? then you mention that hold the
press opens the context menu, is that the issue or another one?

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, 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

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


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

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

[Matt Austin]

Public bug reported:

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

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

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

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


** Tags: amd64 apport-bug jammy

** Description changed:

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

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

Title:
  Display freezes after entering password from login screen

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


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1966905] Re: Valgrind memory errors in gnome-shell 42 from accountsservice

[Sebastien Bacher]

Reported upstream on
https://gitlab.freedesktop.org/accountsservice/accountsservice/-/issues/103

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

** Bug watch added: 
gitlab.freedesktop.org/accountsservice/accountsservice/-/issues #103
   https://gitlab.freedesktop.org/accountsservice/accountsservice/-/issues/103

** Also affects: accountsservice via
   https://gitlab.freedesktop.org/accountsservice/accountsservice/-/issues/103
   Importance: Unknown
   Status: Unknown

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

Title:
  Valgrind memory errors in gnome-shell 42 from accountsservice

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


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1966911] [NEW] Cannot enroll finger on Jammy

[Andy Chi]

Public bug reported:

[Summary]
Cannot enroll finger on Jammy.

[Steps]
1. Install Jammy on XPS-9310
2. Open Gnome-control-center and select `User`
3. Enroll fingerprint

[Expected]
Enroll fingerprint without issue.

[Actual]
Cannot enroll fingerprint

** Affects: libfprint-2-tod1-goodix
 Importance: Critical
 Assignee: Andy Chi (andch)
 Status: Confirmed

** Affects: oem-priority
 Importance: Critical
 Assignee: Andy Chi (andch)
 Status: Confirmed

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


** Tags: oem-priority originate-from-1965879 somerville

** Attachment added: "fprintd.log"
   
https://bugs.launchpad.net/bugs/1966911/+attachment/5574222/+files/fprintd.log

** Tags added: oem-priority originate-from-1965879 somerville

** Changed in: oem-priority
 Assignee: (unassigned) => Andy Chi (andch)

** Changed in: oem-priority
   Importance: Undecided => Critical

** Changed in: oem-priority
   Status: New => Confirmed

** Also affects: libfprint
   Importance: Undecided
   Status: New

** Project changed: libfprint => ubuntu

** Package changed: ubuntu => libfprint (Ubuntu)

** Changed in: libfprint-2-tod1-goodix
 Assignee: (unassigned) => Andy Chi (andch)

** Changed in: libfprint-2-tod1-goodix
   Importance: Undecided => Critical

** Changed in: libfprint-2-tod1-goodix
   Status: New => Confirmed

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

Title:
  Cannot enroll finger on Jammy

To manage notifications about this bug go to:
https://bugs.launchpad.net/libfprint-2-tod1-goodix/+bug/1966911/+subscriptions


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1966911] [NEW] Cannot enroll finger on Jammy

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

[Summary]
Cannot enroll finger on Jammy.

[Steps]
1. Install Jammy on XPS-9310
2. Open Gnome-control-center and select `User`
3. Enroll fingerprint

[Expected]
Enroll fingerprint without issue.

[Actual]
Cannot enroll fingerprint

** Affects: libfprint-2-tod1-goodix
 Importance: Undecided
 Status: New

** Affects: oem-priority
 Importance: Critical
 Assignee: Andy Chi (andch)
 Status: Confirmed

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


** Tags: oem-priority originate-from-1965879 somerville
-- 
Cannot enroll finger on Jammy
https://bugs.launchpad.net/bugs/1966911
You received this bug notification because you are a member of Ubuntu Desktop 
Bugs, which is subscribed to libfprint in Ubuntu.

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1944369] Re: Crash with fprintd 1.92.0

[Andy Chi]

fprintd won't crash with new libfprint version on Jammy which is
1:1.94.3+tod1-0ubuntu1.

** Changed in: oem-priority
   Status: Confirmed => Fix Released

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

Title:
  Crash with fprintd 1.92.0

To manage notifications about this bug go to:
https://bugs.launchpad.net/libfprint-2-tod1-goodix/+bug/1944369/+subscriptions


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1966905] [NEW] Valgrind memory errors in gnome-shell 42 from accountsservice

[Daniel van Vugt]

Public bug reported:

Valgrind memory errors in gnome-shell 42 from accountsservice:

==60511== Invalid read of size 8
==60511==at 0x4D207FA: g_type_check_instance_cast (gtype.c:4120)
==60511==by 0x1E421CA2: free_fetch_user_request (act-user-manager.c:1708)
==60511==by 0x1E4298E7: on_find_user_by_name_finished 
(act-user-manager.c:1187)
==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230)
==60511==by 0x4BC0E0A: UnknownInlinedFun (gtask.c:1300)
==60511==by 0x4BC0E0A: g_task_return (gtask.c:1256)
==60511==by 0x4C298BA: reply_cb (gdbusproxy.c:2576)
==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230)
==60511==by 0x4BC0E0A: UnknownInlinedFun (gtask.c:1300)
==60511==by 0x4BC0E0A: g_task_return (gtask.c:1256)
==60511==by 0x4C2107E: g_dbus_connection_call_done (gdbusconnection.c:5895)
==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230)
==60511==by 0x4BC0C4C: complete_in_idle_cb (gtask.c:1244)
==60511==by 0x4D9CC23: UnknownInlinedFun (gmain.c:3417)
==60511==by 0x4D9CC23: g_main_context_dispatch (gmain.c:4135)
==60511==  Address 0x185b5110 is 0 bytes inside a block of size 64 free'd
==60511==at 0x484B27F: free (in 
/usr/libexec/valgrind/vgpreload_memcheck-amd64-linux.so)
==60511==by 0x4D1F7D4: g_type_free_instance (gtype.c:2008)
==60511==by 0x1E428ECA: UnknownInlinedFun (act-user.c:562)
==60511==by 0x1E428ECA: UnknownInlinedFun (act-user.c:557)
==60511==by 0x1E428ECA: _act_user_update_from_object_path (act-user.c:1346)
==60511==by 0x1E42966F: fetch_user_incrementally (act-user-manager.c:1789)
==60511==by 0x1E4298E7: on_find_user_by_name_finished 
(act-user-manager.c:1187)
==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230)
==60511==by 0x4BC0E0A: UnknownInlinedFun (gtask.c:1300)
==60511==by 0x4BC0E0A: g_task_return (gtask.c:1256)
==60511==by 0x4C298BA: reply_cb (gdbusproxy.c:2576)
==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230)
==60511==by 0x4BC0E0A: UnknownInlinedFun (gtask.c:1300)
==60511==by 0x4BC0E0A: g_task_return (gtask.c:1256)
==60511==by 0x4C2107E: g_dbus_connection_call_done (gdbusconnection.c:5895)
==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230)
==60511==  Block was alloc'd at
==60511==at 0x4848899: malloc (in 
/usr/libexec/valgrind/vgpreload_memcheck-amd64-linux.so)
==60511==by 0x4DA5718: g_malloc (gmem.c:125)
==60511==by 0x4DBCB64: g_slice_alloc (gslice.c:1072)
==60511==by 0x4DBD1CD: g_slice_alloc0 (gslice.c:1098)
==60511==by 0x4D24E61: g_type_create_instance (gtype.c:1911)
==60511==by 0x4D0BF4C: g_object_new_internal (gobject.c:2011)
==60511==by 0x4D0D1AC: g_object_new_with_properties (gobject.c:2181)
==60511==by 0x4D0DCB0: g_object_new (gobject.c:1821)
==60511==by 0x1E422792: create_new_user (act-user-manager.c:706)
==60511==by 0x1E429BD8: act_user_manager_get_user (act-user-manager.c:1879)
==60511==by 0x68ADE2D: ??? (in /usr/lib/x86_64-linux-gnu/libffi.so.8.1.0)
==60511==by 0x68AA492: ??? (in /usr/lib/x86_64-linux-gnu/libffi.so.8.1.0)
==60511== 
==60511== Invalid read of size 8
==60511==at 0x4D206E9: g_type_check_instance_is_fundamentally_a 
(gtype.c:4091)
==60511==by 0x4D06E9A: g_object_set_data (gobject.c:3982)
==60511==by 0x1E421CB6: free_fetch_user_request (act-user-manager.c:1708)
==60511==by 0x1E4298E7: on_find_user_by_name_finished 
(act-user-manager.c:1187)
==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230)
==60511==by 0x4BC0E0A: UnknownInlinedFun (gtask.c:1300)
==60511==by 0x4BC0E0A: g_task_return (gtask.c:1256)
==60511==by 0x4C298BA: reply_cb (gdbusproxy.c:2576)
==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230)
==60511==by 0x4BC0E0A: UnknownInlinedFun (gtask.c:1300)
==60511==by 0x4BC0E0A: g_task_return (gtask.c:1256)
==60511==by 0x4C2107E: g_dbus_connection_call_done (gdbusconnection.c:5895)
==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230)
==60511==by 0x4BC0C4C: complete_in_idle_cb (gtask.c:1244)
==60511==  Address 0x185b5110 is 0 bytes inside a block of size 64 free'd
==60511==at 0x484B27F: free (in 
/usr/libexec/valgrind/vgpreload_memcheck-amd64-linux.so)
==60511==by 0x4D1F7D4: g_type_free_instance (gtype.c:2008)
==60511==by 0x1E428ECA: UnknownInlinedFun (act-user.c:562)
==60511==by 0x1E428ECA: UnknownInlinedFun (act-user.c:557)
==60511==by 0x1E428ECA: _act_user_update_from_object_path (act-user.c:1346)
==60511==by 0x1E42966F: fetch_user_incrementally (act-user-manager.c:1789)
==60511==by 0x1E4298E7: on_find_user_by_name_finished 
(act-user-manager.c:1187)
==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230)
==60511==by 0x4BC0E0A: UnknownInlinedFun (gtask.c:1300)
==60511==by 0x4BC0E0A: g_task_return (gtask.c:1256)
==60511==by 0x4C298BA: reply_cb (gdbusproxy.c:2576)
==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230)
==60511==by 0x4BC0E0A: UnknownInlinedFun 

[Bug 1778069] Re: [xfce] nautilus don't open files if set as default file manager

[Sean Davis]

Xubuntu 18.04 is no longer supported. Marking this ticket resolved for
20.04+.

** Changed in: exo (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  [xfce] nautilus don't open files if set as default file manager

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


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1966787] Re: Totem crashes on launch | GStreamer-GL-CRITICAL **: Failed to flush Wayland connection | Gdk-Message: Error flushing display: Protocol error

[Daniel van Vugt]

I meant that mutter commit 690b8806d sounds like it might fix some
Wayland protocol errors seen in apps recently. Maybe, maybe not.

** Summary changed:

- Totem crashes on launch or when attempting to play video with a Wayland flush 
error
+ Totem crashes on launch | GStreamer-GL-CRITICAL **: Failed to flush Wayland 
connection | Gdk-Message: Error flushing display: Protocol error

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

** Tags added: nvidia

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

Title:
  Totem crashes on launch | GStreamer-GL-CRITICAL **: Failed to flush
  Wayland connection | Gdk-Message: Error flushing display: Protocol
  error

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


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1965563] Re: gnome-extensions-app fails to start (Protocol error)

[Daniel van Vugt]

We should probably only discuss Wayland here. Xorg has bug 1966221.

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

Title:
  gnome-extensions-app fails to start (Protocol error)

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


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1966787] Re: Totem crashes on launch or when attempting to play video with a Wayland flush error

[Robin Sheat]

> 1. Tell us which message you now mean; and

robin@malik:~/Videos$ totem Outrageous\ Fortune\ S04E08.m4v 
Gdk-Message: 11:02:22.100: Error flushing display: Protocol error
robin@malik:~/Videos$ 

This result appears pretty much immediately, and no desktop window
opens.

> 2. Follow these instructions:
https://wiki.ubuntu.com/Bugs/Responses#Missing_a_crash_report_or_having_a_.crash_attachment

No crash dump is produced as this isn't a SIGSEV or similar style crash,
more a failing to work so shutting down abort.

> Maybe related?

This looks to me more like a screencast bug rather than a playback bug.

Maybe relevant, I do get slightly different results sometimes. I just
tried it again:

robin@malik:~/Videos$ totem Outrageous\ Fortune\ S04E08.m4v

(totem:3576): GStreamer-GL-CRITICAL **: 11:09:08.153: Failed to flush
Wayland connection

Gdk-Message: 11:09:08.153: Error flushing display: Protocol error

(totem:3576): GStreamer-GL-CRITICAL **: 11:09:08.153: Failed to flush
Wayland connection

robin@malik:~/Videos$

i.e sometimes the "Failed to flush" message appears, sometimes it
doesn't.

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

Title:
  Totem crashes on launch or when attempting to play video with a
  Wayland flush error

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


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1966787] Re: Totem crashes on launch or when attempting to play video with a Wayland flush error

[Robin Sheat]

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

Title:
  Totem crashes on launch or when attempting to play video with a
  Wayland flush error

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


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1966891] Re: gnome-control-center crashed with SIGSEGV

[Apport retracing service]

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

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 #1965702, 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/1966891/+attachment/5574194/+files/CoreDump.gz

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

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

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

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

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

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

** This bug has been marked a duplicate of private bug 1965702

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  gnome-control-center crashed with SIGSEGV

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


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1966440] Re: gnome-shell crashes often when using the menu (start) button

[Daniel van Vugt]

Yes your upgrade is broken:

DistroRelease: Ubuntu 22.04
Package: gnome-shell 3.36.9-0ubuntu0.20.04.2  <-- belongs in Ubuntu 20.04 only

Probably the only sensible solution is to backup your data, wipe the
machine and reinstall. Because trying to guess our way through repairing
the system will take much longer.

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

Title:
  gnome-shell crashes often when using the menu (start) button

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


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1965563] Re: gnome-extensions-app fails to start (Protocol error)

[Gunnar Hjalmarsson]

I installed version 42.0-1ubuntu1 of the mutter and gnome-shell
packages. Didn't help, neither on Wayland nor Xorg.

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

Title:
  gnome-extensions-app fails to start (Protocol error)

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


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1966440] Re: gnome-shell crashes often when using the menu (start) button

[KaOS-bEat]

Thanks for looking into this.

'Wayland + nvidia drivers' seems to be very problematic...even with 510
I had to reboot in recovery and edit /etc/gdm3/custom.conf to disable wayland 
and reinstall nvidia 470 to get a working system again.


I did enable some PPAs, for hardware like an intel realsense depth camera, just 
removing the PPAs did not fix the problems.
I never enabled the 'proposed'
a broken upgrade could be a thing...
the dist-upgrade (20.04 >> 22.04) did crash and I had to do 'dpkg --configure 
-a' and 'apt --fix-broken' or something similar. Probably a fresh install is a 
good idea...

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

Title:
  gnome-shell crashes often when using the menu (start) button

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


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1949200] Re: gnome-shell crashed with SIGTRAP from error "Can't create a GtkStyleContext without a display connection" in gtk_style_context_init

[Daniel van Vugt]

** Description changed:

  GNOME Shell isn't meant to use GTK at all, but it's repeatedly crashing
  in GTK since the introduction of GNOME 40.
  
  https://errors.ubuntu.com/problem/45d4ce4e8f26828ab6993261e8a20208ecf261b0
  https://errors.ubuntu.com/problem/e60359af65f32c18a4a6ccc93fd3469b0e675844
  https://errors.ubuntu.com/problem/73a93ba578f68516e680373ae324db01336e8bad
  https://errors.ubuntu.com/problem/d69ccaf1379f588b04ecac2a6cc93b9be31100b4
  
  This seems to be a result of Xwayland crashing and gnome-shell then
  trying to recover (and failing). Although gnome-shell shouldn't be using
  GTK, and Wayland sessions shouldn't be dependent on having an X11 server
  (Xwayland) available. Fixing either of those should resolve this.
+ 
+ WORKAROUND:
+ 
+ sudo apt remove libcanberra-gtk3-module
+ 
+ TEST CASE:
+ 
+ 1. Log into a Wayland session.
+ 2. Open a Terminal.
+ 3. $ xrandr   # Just to ensure Xwayland starts
+ 4. $ killall Xwayland
+ 
+ Expected: gnome-shell still responds.
+ Observed: gnome-shell freezes or exits.
+ 
+ ---
  
  ProblemType: Crash
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 40.5-1ubuntu2
  ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
  Uname: Linux 5.13.0-19-generic x86_64
  ApportVersion: 2.20.11-0ubuntu72
  Architecture: amd64
  CasperMD5CheckResult: pass
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct 29 15:11:43 2021
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2021-10-27 (2 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211023)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   LANG=nb_NO.UTF-8
   LANGUAGE=nb_NO:nb:no_NO:no:nn_NO:nn:en
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  RelatedPackageVersions: mutter-common 40.5-1ubuntu2
  Signal: 5
  SourcePackage: gnome-shell
  StacktraceTop:
   g_log_writer_default () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_log_structured_array () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_log_structured_standard () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libgtk-3.so.0
   g_type_create_instance () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: gnome-shell crashed with signal 5 in g_log_writer_default()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  separator:

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

Title:
  gnome-shell crashed with SIGTRAP from error "Can't create a
  GtkStyleContext without a display connection" in
  gtk_style_context_init

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


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1954649] Re: autopkgtest regressions with python3.10 as supported

[Bug Watch Updater]

** Changed in: python-b2sdk (Debian)
   Status: Confirmed => Fix Released

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

Title:
  autopkgtest regressions with python3.10 as supported

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


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1965563] Re: gnome-extensions-app fails to start (Protocol error)

[Daniel van Vugt]

Maybe related?

https://gitlab.gnome.org/GNOME/mutter/-/issues/2155 which is fixed in 42.rc:
https://gitlab.gnome.org/GNOME/mutter/-/commit/690b8806d

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

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

Title:
  gnome-extensions-app fails to start (Protocol error)

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


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1966787] Re: Totem crashes on launch or when attempting to play video with a Wayland flush error

[Daniel van Vugt]

Maybe related?

https://gitlab.gnome.org/GNOME/mutter/-/issues/2155 which is fixed in 42.rc:
https://gitlab.gnome.org/GNOME/mutter/-/commit/690b8806d

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

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

Title:
  Totem crashes on launch or when attempting to play video with a
  Wayland flush error

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


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[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)

[Daniel van Vugt]

I wonder if this fix (coming in 42.rc) is needed?

https://gitlab.gnome.org/GNOME/mutter/-/commit/690b8806d

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter 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)

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


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[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)

[Daniel van Vugt]

** Summary changed:

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

** Tags added: rls-jj-incoming

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter 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)

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


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1949200] Re: gnome-shell crashed with SIGTRAP from error "Can't create a GtkStyleContext without a display connection" in gtk_style_context_init

[Daniel van Vugt]

** Description changed:

  GNOME Shell isn't meant to use GTK at all, but it's repeatedly crashing
  in GTK since the introduction of GNOME 40.
  
  https://errors.ubuntu.com/problem/45d4ce4e8f26828ab6993261e8a20208ecf261b0
  https://errors.ubuntu.com/problem/e60359af65f32c18a4a6ccc93fd3469b0e675844
  https://errors.ubuntu.com/problem/73a93ba578f68516e680373ae324db01336e8bad
+ https://errors.ubuntu.com/problem/d69ccaf1379f588b04ecac2a6cc93b9be31100b4
  
  This seems to be a result of Xwayland crashing and gnome-shell then
  trying to recover (and failing). Although gnome-shell shouldn't be using
  GTK, and Wayland sessions shouldn't be dependent on having an X11 server
  (Xwayland) available. Fixing either of those should resolve this.
  
  ProblemType: Crash
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 40.5-1ubuntu2
  ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
  Uname: Linux 5.13.0-19-generic x86_64
  ApportVersion: 2.20.11-0ubuntu72
  Architecture: amd64
  CasperMD5CheckResult: pass
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct 29 15:11:43 2021
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2021-10-27 (2 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211023)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   LANG=nb_NO.UTF-8
   LANGUAGE=nb_NO:nb:no_NO:no:nn_NO:nn:en
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  RelatedPackageVersions: mutter-common 40.5-1ubuntu2
  Signal: 5
  SourcePackage: gnome-shell
  StacktraceTop:
   g_log_writer_default () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_log_structured_array () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_log_structured_standard () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libgtk-3.so.0
   g_type_create_instance () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: gnome-shell crashed with signal 5 in g_log_writer_default()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  separator:

** Changed in: libcanberra (Ubuntu)
   Status: Confirmed => Triaged

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

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

Title:
  gnome-shell crashed with SIGTRAP from error "Can't create a
  GtkStyleContext without a display connection" in
  gtk_style_context_init

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


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1966796] Re: gnome-shell lost connection to Xwayland

[Daniel van Vugt]

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

Let's assume this was bug 1949200 since I've got to the bottom of that
now.

** This bug has been marked a duplicate of bug 1949200
   gnome-shell crashed with SIGTRAP from error "Can't create a GtkStyleContext 
without a display connection" in gtk_style_context_init

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

Title:
  gnome-shell lost connection to Xwayland

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


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1924251] Re: Embedded browser display corruption under Wayland on Pi desktop

[Sebastien Bacher]

@Dave, we believe that webkitgtk is broken on arm64 at the moment, at least the 
surf autopkgtest are failing 
https://autopkgtest.ubuntu.com/packages/s/surf/jammy/arm64

and the webkitgtk demo browser segfault when started on a canonistack
instance which I reported upstream as
https://bugs.webkit.org/show_bug.cgi?id=237636

do you see similar issues on the pi?

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

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

Title:
  Embedded browser display corruption under Wayland on Pi desktop

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1924251/+subscriptions


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1949200] Re: gnome-shell crashed with SIGTRAP from error "Can't create a GtkStyleContext without a display connection" in gtk_style_context_init

[Daniel van Vugt]

Confirmed! The workaround/fix is:

  sudo apt remove libcanberra-gtk3-module

Also I can't find an active bug tracker for libcanberra and its last
release was in 2012.

** Package changed: gtk+3.0 (Ubuntu) => ubuntu

** Package changed: ubuntu => libcanberra (Ubuntu)

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

Title:
  gnome-shell crashed with SIGTRAP from error "Can't create a
  GtkStyleContext without a display connection" in
  gtk_style_context_init

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


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1949200] Re: gnome-shell crashed with SIGTRAP from error "Can't create a GtkStyleContext without a display connection" in gtk_style_context_init

[Daniel van Vugt]

Removed appindicator task because I've confirmed it happens without any
extensions loaded (duplicate bug 1966862).


** No longer affects: gnome-shell-extension-appindicator (Ubuntu)

** Description changed:

  GNOME Shell isn't meant to use GTK at all, but it's repeatedly crashing
  in GTK since the introduction of GNOME 40.
  
  https://errors.ubuntu.com/problem/45d4ce4e8f26828ab6993261e8a20208ecf261b0
  https://errors.ubuntu.com/problem/e60359af65f32c18a4a6ccc93fd3469b0e675844
  https://errors.ubuntu.com/problem/73a93ba578f68516e680373ae324db01336e8bad
- .
+ 
+ This seems to be a result of Xwayland crashing and gnome-shell then
+ trying to recover (and failing). Although gnome-shell shouldn't be using
+ GTK, and Wayland sessions shouldn't be dependent on having an X11 server
+ available. Fixing either of those should resolve this.
  
  ProblemType: Crash
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 40.5-1ubuntu2
  ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
  Uname: Linux 5.13.0-19-generic x86_64
  ApportVersion: 2.20.11-0ubuntu72
  Architecture: amd64
  CasperMD5CheckResult: pass
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct 29 15:11:43 2021
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2021-10-27 (2 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211023)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   LANG=nb_NO.UTF-8
   LANGUAGE=nb_NO:nb:no_NO:no:nn_NO:nn:en
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  RelatedPackageVersions: mutter-common 40.5-1ubuntu2
  Signal: 5
  SourcePackage: gnome-shell
  StacktraceTop:
   g_log_writer_default () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_log_structured_array () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_log_structured_standard () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libgtk-3.so.0
   g_type_create_instance () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: gnome-shell crashed with signal 5 in g_log_writer_default()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  separator:

** Description changed:

  GNOME Shell isn't meant to use GTK at all, but it's repeatedly crashing
  in GTK since the introduction of GNOME 40.
  
  https://errors.ubuntu.com/problem/45d4ce4e8f26828ab6993261e8a20208ecf261b0
  https://errors.ubuntu.com/problem/e60359af65f32c18a4a6ccc93fd3469b0e675844
  https://errors.ubuntu.com/problem/73a93ba578f68516e680373ae324db01336e8bad
  
  This seems to be a result of Xwayland crashing and gnome-shell then
  trying to recover (and failing). Although gnome-shell shouldn't be using
  GTK, and Wayland sessions shouldn't be dependent on having an X11 server
- available. Fixing either of those should resolve this.
+ (Xwayland) available. Fixing either of those should resolve this.
  
  ProblemType: Crash
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 40.5-1ubuntu2
  ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
  Uname: Linux 5.13.0-19-generic x86_64
  ApportVersion: 2.20.11-0ubuntu72
  Architecture: amd64
  CasperMD5CheckResult: pass
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct 29 15:11:43 2021
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2021-10-27 (2 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211023)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   LANG=nb_NO.UTF-8
   LANGUAGE=nb_NO:nb:no_NO:no:nn_NO:nn:en
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  RelatedPackageVersions: mutter-common 40.5-1ubuntu2
  Signal: 5
  SourcePackage: gnome-shell
  StacktraceTop:
   g_log_writer_default () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_log_structured_array () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_log_structured_standard () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libgtk-3.so.0
   g_type_create_instance () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: gnome-shell crashed with signal 5 in g_log_writer_default()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  separator:

** Tags added: rls-jj-incoming

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

Title:
  gnome-shell crashed with SIGTRAP from error "Can't create a
  GtkStyleContext without a display connection" in
  gtk_style_context_init

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


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com

[Bug 1966787] Re: Totem crashes on launch or when attempting to play video with a Wayland flush error

[Daniel van Vugt]

> Update: my resolution didn't resolve it. If I attempt to play a file,
it crashes with the same message as above.

Please:

1. Tell us which message you now mean; and

2. Follow these instructions:
https://wiki.ubuntu.com/Bugs/Responses#Missing_a_crash_report_or_having_a_.crash_attachment

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

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

Title:
  Totem crashes on launch or when attempting to play video with a
  Wayland flush error

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


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1240336] Re: After release upgrade, the user loses permissions for several basic actions in the system

[shamita]

Need for dell laptop repairing contact dell service center in thane because we 
have door step support for dell laptop users thane if you have problem with 
your laptop like  motherboard issue ,screen issue ,battery issue or ram 
replacement we capable to resolve your issue at your place within same day .For 
more information please visit call our office dell service center thane .
https://www.laptopsservice.center/dell-laptop-service-center-thane-mumbai.html

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

Title:
  After release upgrade, the user loses permissions for several basic
  actions in the system

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


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1966786] Re: login screen shown twice

[Daniel van Vugt]

Perhaps the first session is crashing. Please try:

https://wiki.ubuntu.com/Bugs/Responses#Missing_a_crash_report_or_having_a_.crash_attachment

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

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

Title:
  login screen shown twice

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


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1960336] Re: No login screen when fprintd crashes

[Daniel van Vugt]

** Tags added: fingerprint

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

Title:
  No login screen when fprintd crashes

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


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1966781] Re: gdm3 refuse to launch

[Daniel van Vugt]

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

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 1966808, 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.


** Tags added: amdgpu

** This bug has been marked a duplicate of bug 1966808
   [amdgpu][radeon] gnome-shell: Failed to lock front buffer on /dev/dri/card1: 
drmModeAddFB2WithModifiers failed: Invalid argument

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

Title:
  gdm3 refuse to launch

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


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1966795] Re: First boot with fingerprint auth enabled, gdm doesn't prompt to enter password

[Daniel van Vugt]

In case this is due to fprintd crashing, see also bug 1960336.

** Package changed: gdm (Ubuntu) => gdm3 (Ubuntu)

** Tags added: fprint jammy

** Tags removed: fprint
** Tags added: fingerprint

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

Title:
  First boot with fingerprint auth enabled, gdm doesn't prompt to enter
  password

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


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1966808] Re: [amdgpu][radeon] gnome-shell: Failed to lock front buffer on /dev/dri/card1: drmModeAddFB2WithModifiers failed: Invalid argument

[Launchpad Bug Tracker]

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

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

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

Title:
  [amdgpu][radeon] gnome-shell: Failed to lock front buffer on
  /dev/dri/card1: drmModeAddFB2WithModifiers failed: Invalid argument

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


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1966808] Re: [amdgpu][radeon] gnome-shell: Failed to lock front buffer on /dev/dri/card1: drmModeAddFB2WithModifiers failed: Invalid argument

[Launchpad Bug Tracker]

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

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

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

Title:
  [amdgpu][radeon] gnome-shell: Failed to lock front buffer on
  /dev/dri/card1: drmModeAddFB2WithModifiers failed: Invalid argument

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


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1966808] Re: [radeon] gnome-shell: Failed to lock front buffer on /dev/dri/card1: drmModeAddFB2WithModifiers failed: Invalid argument

[Daniel van Vugt]

Also seen in bug 1966781.

** Tags added: amdgpu

** Summary changed:

- [radeon] gnome-shell: Failed to lock front buffer on /dev/dri/card1: 
drmModeAddFB2WithModifiers failed: Invalid argument
+ [amdgpu][radeon] gnome-shell: Failed to lock front buffer on /dev/dri/card1: 
drmModeAddFB2WithModifiers failed: Invalid argument

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

Title:
  [amdgpu][radeon] gnome-shell: Failed to lock front buffer on
  /dev/dri/card1: drmModeAddFB2WithModifiers failed: Invalid argument

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


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1871538] Re: dbus timeout-ed during an upgrade, taking services down including gdm

[Christian Ehrhardt ]

I can't test this reliably (as stated in the SRU description), but at
least I can say I haven't seen it in the last 24h :-) I think this is on
@gjolly to try to reproduce it in the mentioned azure test environment.

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, 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

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


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs