[Bug 2080498] Re: Default session type changed from Xorg to Wayland in some installs of 22.04 on Nvidia hybrids since kernel 6.8

2024-12-09 Thread Alessandro Astone
** Description changed:

  [ Impact ]
  
  On some nvidia hybrid systems, like the HP ZBook Fury G11 platform
  preloaded with Ubuntu 22.04, the windowing system in "Settings -> About"
  used to be Xorg but after doing kernel upgrade from 6.5-oem to 6.8-hwe,
  the windowing system become Wayland.
  
  There is a race condition in udev rules that makes the default desktop
  session either Xorg or Wayland depending on the ordering of hardware
  discovery and modules loading. This would affect both jammy and noble,
  but being a race condition it is unpredictable which hardware defaults
  to which desktop session, and the same hardware may behave differently
  in jammy vs in noble.
  
  The intended default desktop session was meant to be Wayland, however
  the vast majority of nvidia hybrid laptops defaulted to Xorg at launch,
  including and particularly all Ubuntu Certified laptops. For this reason
  we're considering this a bug and are taking measures to ensure that all
  nvidia hybrid laptops keep defaulting to Xorg.
+ 
+ There is also at least onw known issues affecting nvidia on Wayland which 
might swing the preference towards Xorg:
+ * bug 2064205
  
  The fix removes the udev logic that was trying to make nvidia hybrid
  laptops specifically prefer Wayland, making that hardware use the same
  udev rules as nvidia desktops which already default to Xorg.
  
  [ Glossary ]
  
  "nvidia" laptop/system/machine/etc...: A computer with at least one
  nvidia GPU, running the proprietary driver version 470 or higher.
  
  "affected" laptop/system/machine/etc...: An nvidia hybrid laptop that,
  before installing the fix, on the log-in screen presents the options to
  log-in to "Ubuntu" and "Ubuntu on Xorg".
  
  "existing user": A unix user that has already logged-in to a desktop
  session at least once, regardless of whether they ever changed the log-
  in session or not.
  
  "new user": A unix user that has never logged-in to a desktop session,
  regardless of whether it was created before or after the update, or
  whether it ever logged in to a TTY or not.
  
  [ Test-plans overview ]
  
  The expected behaviour after the update is that:
  * for nvidia hybrid laptops affected by the bug: both existing and new users 
will log-in to Xorg by default;
  * for nvidia hybrid laptops unaffected by the bug: the default session for 
new users is Xorg, but existing users will keep their previous preference;
  * for nvidia desktops: the default session for new users is Xorg, but 
existing users will keep their previous preference;
  * for all non-nvidia systems: the default session for new users is Wayland, 
but existing users will keep their previous preference;
  
  Test Plan A and B verify that on a nvidia hybrid laptop both existing
  users and new users log-in to Xorg by default after the update
  
  Test plans C and D verify that on unaffected nvidia systems the user
  preference about which session to log-in to is preserved the update.
  
  Test plans E and F verify that on non-nvidia systems the user preference
  about which session to log-in to is preserved after the update.
  
  Test plans *not* marked as "Regression" should only be verified on an
  affected laptop.
  
  [ Test Plan A ]
  
  1.  Get an affected nvidia hybrid laptop with Ubuntu 22.04 or 24.04
  2.  Before installing the update being tested, reboot to the log-in screen
  3.  Select your username
  4.  Click on the cogwheel icon at the bottom-right of the screen
  5.  Select "Ubuntu"
  6.  Log-in
  7.  Now install the gdm3 update being tested
  8.  Reboot
  9.  At the log-in screen, select your username
  10. Verify that there is a cogwheel icon at the bottom-right of the screen
  11. Click on the cogwheel icon to open up the menu
  12. Verify that the selected option is "Ubuntu"
  13. Verify that the alternative option is "Ubuntu on Wayland"
  14. Close the menu without changing the selection ("Ubuntu")
  15. Log-in
  16. Verify via "Settings -> About" that "Windowing System" is X11
  
  [ Test Plan B ]
  
  1.  Get an affected nvidia hybrid laptop with Ubuntu 22.04 or 24.04
  2.  Install the gdm3 update being tested
  3.  Create a new a new User on the system
  4.  Reboot
  5.  At the log-in screen, select the new User
  6.  Verify that there is a cogwheel icon at the bottom-right of the screen
  7.  Click on the cogwheel icon to open up the menu
  8.  Verify that the selected option is "Ubuntu"
  9.  Verify that the alternative option is "Ubuntu on Wayland"
  10. Close the menu without changing the selection
  11. Log-in
  12. Verify via "Settings -> About" that "Windowing System" is X11
  
  [ Test Plan C - Regression ]
  
  1.  Set up a desktop machine with a single nvidia GPU
  2.  Before installing the update being tested, reboot to the log-in screen
  3.  Select your username
  4.  Click on the cogwheel icon at the bottom-right of the screen
  5.  Select "Ubuntu on Wayland"
  6.  Log-in
  7.  Now install the gdm3 update being tested
 

[Bug 2080498] Re: Default session type changed from Xorg to Wayland in some installs of 22.04 on Nvidia hybrids since kernel 6.8

2024-12-09 Thread Alessandro Astone
** Description changed:

  [ Impact ]
  
  On some nvidia hybrid systems, like the HP ZBook Fury G11 platform
  preloaded with Ubuntu 22.04, the windowing system in "Settings -> About"
  used to be Xorg but after doing kernel upgrade from 6.5-oem to 6.8-hwe,
  the windowing system become Wayland.
  
  There is a race condition in udev rules that makes the default desktop
  session either Xorg or Wayland depending on the ordering of hardware
  discovery and modules loading. This would affect both jammy and noble,
  but being a race condition it is unpredictable which hardware defaults
  to which desktop session, and the same hardware may behave differently
  in jammy vs in noble.
  
  The intended default desktop session was meant to be Wayland, however
  the vast majority of nvidia hybrid laptops defaulted to Xorg at launch,
  including and particularly all Ubuntu Certified laptops. For this reason
  we're considering this a bug and are taking measures to ensure that all
  nvidia hybrid laptops keep defaulting to Xorg.
  
  The fix removes the udev logic that was trying to make nvidia hybrid
  laptops specifically prefer Wayland, making that hardware use the same
  udev rules as nvidia desktops which already default to Xorg.
  
- [ Test Plan ]
  
- 1. Set up a nvidia hybrid laptop with Ubuntu 22.04 or 24.04
- 2. Install the latest updates, particularly the latest kernel
- 2. Install the gdm3 update being tested
- 3. Create a new a new User on the system
- 3. Reboot
- 4. At the log-in screen, select the new User
- 5. Verify that there is a cogwheel icon at the bottom-right of the screen.
- 6. Click on the cogwheel icon to open up the menu
- 7. Verify that the selected option is "Ubuntu"
- 8. Verify that the alternative option is "Ubuntu on Wayland"
- 9. Close the menu without changing the selection
- 10. Log-in
- 11. Verify via "Settings -> About" that "Windowing System" is X11
+ [ Glossary ]
+ 
+ "nvidia" laptop/system/machine/etc...: A computer with at least one
+ nvidia GPU, running the proprietary driver version 470 or higher.
+ 
+ "affected" laptop/system/machine/etc...: An nvidia hybrid laptop that,
+ before installing the fix, on the log-in screen presents the options to
+ log-in to "Ubuntu" and "Ubuntu on Xorg".
+ 
+ "existing user": A unix user that has already logged-in to a desktop
+ session at least once, regardless of whether they ever changed the log-
+ in session or not.
+ 
+ "new user": A unix user that has never logged-in to a desktop session,
+ regardless of whether it was created before or after the update, or
+ whether it ever logged in to a TTY or not.
+ 
+ 
+ [ Test-plans overview ]
+ 
+ The expected behaviour after the update is that:
+ * for nvidia hybrid laptops affected by the bug: both existing and new users 
will log-in to Xorg by default;
+ * for nvidia hybrid laptops unaffected by the bug: the default session for 
new users is Xorg, but existing users will keep their previous preference;
+ * for nvidia desktops: the default session for new users is Xorg, but 
existing users will keep their previous preference;
+ * for all non-nvidia systems: the default session for new users is Wayland, 
but existing users will keep their previous preference;
+ 
+ Test Plan A and B verify that on a nvidia hybrid laptop both existing
+ users and new users log-in to Xorg by default after the update
+ 
+ Test plans C and D verify that on unaffected nvidia systems the user
+ preference about which session to log-in to is preserved the update.
+ 
+ Test plans E and F verify that on non-nvidia systems the user preference
+ about which session to log-in to is preserved after the update.
+ 
+ Test plans *not* marked as "Regression" should only be verified on an
+ affected laptop.
+ 
+ 
+ [ Test Plan A ]
+ 
+ 1. Get an affected nvidia hybrid laptop with Ubuntu 22.04 or 24.04
+ 2. Before installing the gdm3 update being tested, log-in selecting "Ubuntu"
+ 3. Install the gdm3 update being tested
+ 4. Reboot
+ 5. At the log-in screen, select your username
+ 6. Verify that there is a cogwheel icon at the bottom-right of the screen
+ 7. Click on the cogwheel icon to open up the menu
+ 8. Verify that the selected option is "Ubuntu"
+ 9. Verify that the alternative option is "Ubuntu on Wayland"
+ 10. Close the menu without changing the selection ("Ubuntu")
+ 11. Log-in
+ 12. Verify via "Settings -> About" that "Windowing System" is X11
+ 
+ 
+ [ Test Plan B ]
+ 
+ 1.  Get an affected nvidia hybrid laptop with Ubuntu 22.04 or 24.04
+ 2.  Install the gdm3 update being tested
+ 3.  Create a new a new User on the system
+ 4.  Reboot
+ 5.  At the log-in screen, select the new User
+ 6.  Verify that there is a cogwheel icon at the bottom-right of the screen
+ 7.  Click on the cogwheel icon to open up the menu
+ 8.  Verify that the selected option is "Ubuntu"
+ 9.  Verify that the alternative option is "Ubuntu on Wayland"
+ 10. Close the menu without changing the selection
+ 11. Log-in
+ 12. Verify via "Settings -> A

[Bug 2080498] Re: Default session type changed from Xorg to Wayland in some installs of 22.04 on Nvidia hybrids since kernel 6.8

2024-12-09 Thread Alessandro Astone
** Description changed:

  [ Impact ]
  
  On some nvidia hybrid systems, like the HP ZBook Fury G11 platform
  preloaded with Ubuntu 22.04, the windowing system in "Settings -> About"
  used to be Xorg but after doing kernel upgrade from 6.5-oem to 6.8-hwe,
  the windowing system become Wayland.
  
  There is a race condition in udev rules that makes the default desktop
  session either Xorg or Wayland depending on the ordering of hardware
  discovery and modules loading. This would affect both jammy and noble,
  but being a race condition it is unpredictable which hardware defaults
  to which desktop session, and the same hardware may behave differently
  in jammy vs in noble.
  
  The intended default desktop session was meant to be Wayland, however
  the vast majority of nvidia hybrid laptops defaulted to Xorg at launch,
  including and particularly all Ubuntu Certified laptops. For this reason
  we're considering this a bug and are taking measures to ensure that all
  nvidia hybrid laptops keep defaulting to Xorg.
  
  The fix removes the udev logic that was trying to make nvidia hybrid
  laptops specifically prefer Wayland, making that hardware use the same
  udev rules as nvidia desktops which already default to Xorg.
  
- 
  [ Glossary ]
  
  "nvidia" laptop/system/machine/etc...: A computer with at least one
  nvidia GPU, running the proprietary driver version 470 or higher.
  
  "affected" laptop/system/machine/etc...: An nvidia hybrid laptop that,
  before installing the fix, on the log-in screen presents the options to
  log-in to "Ubuntu" and "Ubuntu on Xorg".
  
  "existing user": A unix user that has already logged-in to a desktop
  session at least once, regardless of whether they ever changed the log-
  in session or not.
  
  "new user": A unix user that has never logged-in to a desktop session,
  regardless of whether it was created before or after the update, or
  whether it ever logged in to a TTY or not.
- 
  
  [ Test-plans overview ]
  
  The expected behaviour after the update is that:
  * for nvidia hybrid laptops affected by the bug: both existing and new users 
will log-in to Xorg by default;
  * for nvidia hybrid laptops unaffected by the bug: the default session for 
new users is Xorg, but existing users will keep their previous preference;
  * for nvidia desktops: the default session for new users is Xorg, but 
existing users will keep their previous preference;
  * for all non-nvidia systems: the default session for new users is Wayland, 
but existing users will keep their previous preference;
  
  Test Plan A and B verify that on a nvidia hybrid laptop both existing
  users and new users log-in to Xorg by default after the update
  
  Test plans C and D verify that on unaffected nvidia systems the user
  preference about which session to log-in to is preserved the update.
  
  Test plans E and F verify that on non-nvidia systems the user preference
  about which session to log-in to is preserved after the update.
  
  Test plans *not* marked as "Regression" should only be verified on an
  affected laptop.
  
- 
  [ Test Plan A ]
  
- 1. Get an affected nvidia hybrid laptop with Ubuntu 22.04 or 24.04
- 2. Before installing the gdm3 update being tested, log-in selecting "Ubuntu"
- 3. Install the gdm3 update being tested
- 4. Reboot
- 5. At the log-in screen, select your username
- 6. Verify that there is a cogwheel icon at the bottom-right of the screen
- 7. Click on the cogwheel icon to open up the menu
- 8. Verify that the selected option is "Ubuntu"
- 9. Verify that the alternative option is "Ubuntu on Wayland"
- 10. Close the menu without changing the selection ("Ubuntu")
- 11. Log-in
- 12. Verify via "Settings -> About" that "Windowing System" is X11
- 
+ 1.  Get an affected nvidia hybrid laptop with Ubuntu 22.04 or 24.04
+ 2.  Before installing the update being tested, reboot to the log-in screen
+ 3.  Select your username
+ 4.  Click on the cogwheel icon at the bottom-right of the screen
+ 5.  Select "Ubuntu"
+ 6.  Log-in
+ 7.  Now install the gdm3 update being tested
+ 8.  Reboot
+ 9.  At the log-in screen, select your username
+ 10. Verify that there is a cogwheel icon at the bottom-right of the screen
+ 11. Click on the cogwheel icon to open up the menu
+ 12. Verify that the selected option is "Ubuntu"
+ 13. Verify that the alternative option is "Ubuntu on Wayland"
+ 14. Close the menu without changing the selection ("Ubuntu")
+ 15. Log-in
+ 16. Verify via "Settings -> About" that "Windowing System" is X11
  
  [ Test Plan B ]
  
  1.  Get an affected nvidia hybrid laptop with Ubuntu 22.04 or 24.04
  2.  Install the gdm3 update being tested
  3.  Create a new a new User on the system
  4.  Reboot
  5.  At the log-in screen, select the new User
  6.  Verify that there is a cogwheel icon at the bottom-right of the screen
  7.  Click on the cogwheel icon to open up the menu
  8.  Verify that the selected option is "Ubuntu"
  9.  Verify that the alternative option is "U

[Bug 2064205] Re: Optimize cross-GPU multi-monitor syncs

2024-12-09 Thread Alessandro Astone
This might be the cause of
https://warthogs.atlassian.net/browse/SOMERVILLE-1270

They're considering it a blocker

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

Title:
  Optimize cross-GPU multi-monitor syncs

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


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

[Bug 1246272] Re: Keyboard layout changing randomly

2024-12-09 Thread Vladymir
Ubuntu Unity 24.04 
set: US_Dvorak + Ru (no us_en 'querty"!)
but turning on us_en each time on wakeup from hibernation

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

Title:
  Keyboard layout changing randomly

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


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

[Bug 2085575] Re: Seeking is unreliable and often causes video to stop

2024-12-09 Thread Alessandro Astone
*** This bug is a duplicate of bug 2055842 ***
https://bugs.launchpad.net/bugs/2055842

** This bug has been marked a duplicate of bug 2055842
   gstreamer: unreliable playback due to pulseaudio bug

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

Title:
  Seeking is unreliable and often causes video to stop

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


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

[Bug 2055842] Re: gstreamer: unreliable playback due to pulseaudio bug

2024-12-09 Thread Alessandro Astone
** Changed in: pulseaudio (Ubuntu)
   Status: Incomplete => In Progress

** Changed in: pulseaudio (Ubuntu)
 Assignee: (unassigned) => Alessandro Astone (aleasto)

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

** Also affects: pulseaudio (Ubuntu Noble)
   Importance: Undecided
   Status: New

** Also affects: pulseaudio (Ubuntu Oracular)
   Importance: Undecided
   Status: New

** Changed in: pulseaudio (Ubuntu Noble)
 Assignee: (unassigned) => Alessandro Astone (aleasto)

** Changed in: pulseaudio (Ubuntu Oracular)
 Assignee: (unassigned) => Alessandro Astone (aleasto)

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

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

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

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

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to a duplicate bug report (2085575).
https://bugs.launchpad.net/bugs/2055842

Title:
  gstreamer: unreliable playback due to pulseaudio bug

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


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

[Bug 2091302] Re: "Missing Decoder meta/x-gst-fourcc-mebx" message when trying to play some videos

2024-12-09 Thread Bug Watch Updater
** Changed in: gstreamer1.0
   Status: Unknown => New

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

Title:
  "Missing Decoder meta/x-gst-fourcc-mebx" message when trying to play
  some videos

To manage notifications about this bug go to:
https://bugs.launchpad.net/gstreamer1.0/+bug/2091302/+subscriptions


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

[Bug 2055842] Re: gstreamer: unreliable playback due to pulseaudio bug

2024-12-09 Thread Alessandro Astone
** Description changed:

- i've been investigating bugs of the gstreamer backend of qt
- (QTBUG-122424, QTBUG-122423). it seems that we run into a pulseaudio bug
- that has been fixed in pulseaudio-17.
+ [ Impact ]
  
- what would it take to backport the corresponding fix?
+ gstreamer playback may hang after seeking.
+ This affects all video/audio players that use gstreamer as their backend.
+ The cause of the problem is a pulseaudio bug that was fixed in version 16.2
+ 
+ Some upstream bugs are QTBUG-122424, QTBUG-122423,
+ https://gitlab.gnome.org/GNOME/totem/-/issues/573
+ 
+ Here we backport the relevant patches:
  https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/745
- (i've verified that a local build of pulseaudio with that patch fixes
- the issue).
+ https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/764
  
- edit: a very similar class of bugs requires
- https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/764
- to be backported
+ [ Test Plan ]
+ 
+ 1. Open a movie in the Totem video player
+ 2. Seek back and forth for a few minutes
+ 3. Verify that the playback never hung
+ 4. Verify that the audio plays correctly
+ 
+ [ Regression potential ]
+ 
+ libpulse0 is a critical component of Ubuntu Desktop.
+ It provides the audio interface for all applications.
+ A bug in libpulse0 may break audio input/output in one or many applications.

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to a duplicate bug report (2085575).
https://bugs.launchpad.net/bugs/2055842

Title:
  gstreamer: unreliable playback due to pulseaudio bug

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


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

[Bug 2091306] [NEW] [SRU] Update evolution to 3.54.2

2024-12-09 Thread Alessandro Astone
Public bug reported:

[ Impact ]
This is a new stable release in the 3.54 series.
https://gitlab.gnome.org/GNOME/evolution/-/blob/3.54.2/NEWS

[ Test Plan ]
You may follow the generic test plan at:
https://wiki.ubuntu.com/DesktopTeam/TestPlans/Evolution

[ Where problems could occur ]
Evolution is included by default in Ubuntu MATE.

If the update is malfunctioning, the Evolution app
(mail/contacts/calendar suite) may stop working. The Thunderbird app may
be used alternatively.

Evolution is part of the GNOME micro release exceptions:
https://wiki.ubuntu.com/StableReleaseUpdates/GNOME

[ Other Info ]
This depends on evolution-data-server 3.54.2 so that version ought to reach 
noble-updates before we let evolution 3.54.2 in to noble-updates

** Affects: evolution (Ubuntu)
 Importance: Undecided
 Assignee: Alessandro Astone (aleasto)
 Status: Fix Released

** Affects: evolution (Ubuntu Oracular)
 Importance: Medium
 Assignee: Alessandro Astone (aleasto)
 Status: In Progress

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

** Also affects: evolution (Ubuntu Oracular)
   Importance: Undecided
   Status: New

** Changed in: evolution (Ubuntu)
 Assignee: (unassigned) => Alessandro Astone (aleasto)

** Changed in: evolution (Ubuntu Oracular)
 Assignee: (unassigned) => Alessandro Astone (aleasto)

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

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

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

Title:
  [SRU] Update evolution to 3.54.2

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


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

[Bug 2091307] [NEW] [SRU] Update evolution-data-server to 3.54.2

2024-12-09 Thread Alessandro Astone
Public bug reported:

Impact
--
This is a new stable release in the 3.54 series.

https://gitlab.gnome.org/GNOME/evolution-data-server/-/blob/3.54.2/NEWS

Test Case
-
Install the update
Log out and log back in (or restart)
Then ensure that GNOME Calendar and Evolution still work fine using these test 
cases:

https://wiki.ubuntu.com/DesktopTeam/TestPlans/Calendar
https://wiki.ubuntu.com/DesktopTeam/TestPlans/Evolution

What Could Go Wrong
---
GNOME Calendar, which is pre-installed in Ubuntu Desktop, relies on 
evolution-data-server as its database for events and contacts.
If this component misbehaves, so will GNOME Calendar and Evolution

As a component of GNOME core, there is a micro-release exception for
evolution-data-server

https://wiki.ubuntu.com/StableReleaseUpdates/GNOME

** Affects: evolution-data-server (Ubuntu)
 Importance: Undecided
 Assignee: Alessandro Astone (aleasto)
 Status: Fix Released

** Affects: evolution-data-server (Ubuntu Oracular)
 Importance: Medium
 Assignee: Alessandro Astone (aleasto)
 Status: In Progress

** Changed in: evolution-data-server (Ubuntu)
   Status: New => Fix Released

** Also affects: evolution-data-server (Ubuntu Oracular)
   Importance: Undecided
   Status: New

** Changed in: evolution-data-server (Ubuntu)
 Assignee: (unassigned) => Alessandro Astone (aleasto)

** Changed in: evolution-data-server (Ubuntu Oracular)
 Assignee: (unassigned) => Alessandro Astone (aleasto)

** Changed in: evolution-data-server (Ubuntu Oracular)
   Importance: Undecided => Medium

** Changed in: evolution-data-server (Ubuntu Oracular)
   Status: New => In Progress

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

Title:
  [SRU] Update evolution-data-server to 3.54.2

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


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

[Bug 2055842] Re: gstreamer: unreliable playback due to pulseaudio bug

2024-12-09 Thread Ubuntu Foundations Team Bug Bot
The attachment "pulseaudio_16.1+dfsg1-5.1ubuntu2.debdiff" seems to be a
debdiff.  The ubuntu-sponsors team has been subscribed to the bug report
so that they can review and hopefully sponsor the debdiff.  If the
attachment isn't a patch, please remove the "patch" flag from the
attachment, remove the "patch" tag, and if you are member of the
~ubuntu-sponsors, unsubscribe the team.

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

** Tags added: patch

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to a duplicate bug report (2085575).
https://bugs.launchpad.net/bugs/2055842

Title:
  gstreamer: unreliable playback due to pulseaudio bug

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


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

[Bug 2091302] Re: "Missing Decoder meta/x-gst-fourcc-mebx" message when trying to play some videos

2024-12-09 Thread AsciiWolf
** Attachment added: "Test video"
   
https://bugs.launchpad.net/gstreamer1.0/+bug/2091302/+attachment/5843144/+files/test.MOV

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

Title:
  "Missing Decoder meta/x-gst-fourcc-mebx" message when trying to play
  some videos

To manage notifications about this bug go to:
https://bugs.launchpad.net/gstreamer1.0/+bug/2091302/+subscriptions


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

[Bug 2055842] Re: gstreamer: unreliable playback due to pulseaudio bug

2024-12-09 Thread Alessandro Astone
oracular debdiff

** Patch added: "pulseaudio_16.1+dfsg1-5.1ubuntu1.1.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/2055842/+attachment/5843139/+files/pulseaudio_16.1+dfsg1-5.1ubuntu1.1.debdiff

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to a duplicate bug report (2085575).
https://bugs.launchpad.net/bugs/2055842

Title:
  gstreamer: unreliable playback due to pulseaudio bug

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


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

[Bug 2055842] Re: gstreamer: unreliable playback due to pulseaudio bug

2024-12-09 Thread Alessandro Astone
oracular debdiff

** Patch added: "pulseaudio_16.1+dfsg1-5.1ubuntu1.1.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/2055842/+attachment/5843135/+files/pulseaudio_16.1+dfsg1-5.1ubuntu1.1.debdiff

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to a duplicate bug report (2085575).
https://bugs.launchpad.net/bugs/2055842

Title:
  gstreamer: unreliable playback due to pulseaudio bug

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


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

[Bug 2055842] Re: gstreamer: unreliable playback due to pulseaudio bug

2024-12-09 Thread Alessandro Astone
noble debdiff

** Patch added: "pulseaudio_16.1+dfsg1-2ubuntu12.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/2055842/+attachment/5843136/+files/pulseaudio_16.1+dfsg1-2ubuntu12.debdiff

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to a duplicate bug report (2085575).
https://bugs.launchpad.net/bugs/2055842

Title:
  gstreamer: unreliable playback due to pulseaudio bug

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


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

[Bug 2055842] Re: gstreamer: unreliable playback due to pulseaudio bug

2024-12-09 Thread Alessandro Astone
plucky debdiff

** Patch added: "pulseaudio_16.1+dfsg1-5.1ubuntu2.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/2055842/+attachment/5843134/+files/pulseaudio_16.1+dfsg1-5.1ubuntu2.debdiff

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to a duplicate bug report (2085575).
https://bugs.launchpad.net/bugs/2055842

Title:
  gstreamer: unreliable playback due to pulseaudio bug

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


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

[Bug 2085575] Re: Seeking is unreliable and often causes video to stop

2024-12-09 Thread Alessandro Astone
*** This bug is a duplicate of bug 2055842 ***
https://bugs.launchpad.net/bugs/2055842

This ended up being a pulseaudio bug, so I've closed this as a duplicate
of 2055842

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

Title:
  Seeking is unreliable and often causes video to stop

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


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

[Bug 2055842] Re: gstreamer: unreliable playback due to pulseaudio bug

2024-12-09 Thread Alessandro Astone
** Description changed:

  [ Impact ]
  
  gstreamer playback may hang after seeking.
  This affects all video/audio players that use gstreamer as their backend.
  The cause of the problem is a pulseaudio bug that was fixed in version 16.2
  
  Some upstream bugs are QTBUG-122424, QTBUG-122423,
  https://gitlab.gnome.org/GNOME/totem/-/issues/573
  
  Here we backport the relevant patches:
  https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/745
  https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/764
  
  [ Test Plan ]
  
  1. Open a movie in the Totem video player
- 2. Seek back and forth for a few minutes
+ 2. Repeatedly seek back and forth for a few minutes
  3. Verify that the playback never hung
  4. Verify that the audio plays correctly
  
  [ Regression potential ]
  
  libpulse0 is a critical component of Ubuntu Desktop.
  It provides the audio interface for all applications.
  A bug in libpulse0 may break audio input/output in one or many applications.

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to a duplicate bug report (2085575).
https://bugs.launchpad.net/bugs/2055842

Title:
  gstreamer: unreliable playback due to pulseaudio bug

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


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

[Bug 2091302] [NEW] "Missing Decoder meta/x-gst-fourcc-mebx" message when trying to play some videos

2024-12-09 Thread Launchpad Bug Tracker
You have been subscribed to a public bug by AsciiWolf (asciiwolf):

When trying to play some videos using Totem, the "Missing Decoder
meta/x-gst-fourcc-mebx" message appears. However, the videos start
playing fine after clicking the "Search in Software" button.

Related upstream ticket:
https://gitlab.freedesktop.org/gstreamer/gstreamer/-/issues/2578

** Affects: gstreamer1.0 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: noble oracular
-- 
"Missing Decoder meta/x-gst-fourcc-mebx" message when trying to play some videos
https://bugs.launchpad.net/bugs/2091302
You received this bug notification because you are a member of Ubuntu Desktop 
Bugs, which is subscribed to the bug report.

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

[Bug 2091302] [NEW] "Missing Decoder meta/x-gst-fourcc-mebx" message when trying to play some videos

2024-12-09 Thread AsciiWolf
Public bug reported:

When trying to play some videos using Totem, the "Missing Decoder
meta/x-gst-fourcc-mebx" message appears. However, the videos start
playing fine after clicking the "Search in Software" button.

Related upstream ticket:
https://gitlab.freedesktop.org/gstreamer/gstreamer/-/issues/2578

** Affects: gstreamer1.0
 Importance: Unknown
 Status: Unknown

** Affects: gstreamer1.0 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: noble oracular

** Attachment added: "screenshot.png"
   
https://bugs.launchpad.net/bugs/2091302/+attachment/5843143/+files/screenshot.png

** Bug watch added: gitlab.freedesktop.org/gstreamer/gstreamer/-/issues #2578
   https://gitlab.freedesktop.org/gstreamer/gstreamer/-/issues/2578

** Also affects: gstreamer1.0 via
   https://gitlab.freedesktop.org/gstreamer/gstreamer/-/issues/2578
   Importance: Unknown
   Status: Unknown

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

Title:
  "Missing Decoder meta/x-gst-fourcc-mebx" message when trying to play
  some videos

To manage notifications about this bug go to:
https://bugs.launchpad.net/gstreamer1.0/+bug/2091302/+subscriptions


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

[Bug 2047256] Re: Ubuntu 24.04 Some image thumbnails no longer displayed

2024-12-09 Thread Eugenio Perea
Well, it's been a full month since my last question, prompted by
instructions I received in response to an even earlier comment. I've
received no response so far.

We're also two weeks away from this bug's first anniversary.

It's extremely frustrating, and, to add insult to injury, its status for
months has been "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/2047256

Title:
  Ubuntu 24.04 Some image thumbnails no longer displayed

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


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

[Bug 2055842] Re: gstreamer: unreliable playback due to pulseaudio bug

2024-12-09 Thread Alessandro Astone
plucky debdiff

** Patch removed: "pulseaudio_16.1+dfsg1-5.1ubuntu2.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/2055842/+attachment/5843134/+files/pulseaudio_16.1+dfsg1-5.1ubuntu2.debdiff

** Patch removed: "pulseaudio_16.1+dfsg1-5.1ubuntu1.1.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/2055842/+attachment/5843135/+files/pulseaudio_16.1+dfsg1-5.1ubuntu1.1.debdiff

** Patch removed: "pulseaudio_16.1+dfsg1-2ubuntu12.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/2055842/+attachment/5843136/+files/pulseaudio_16.1+dfsg1-2ubuntu12.debdiff

** Patch added: "pulseaudio_16.1+dfsg1-5.1ubuntu2.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/2055842/+attachment/5843138/+files/pulseaudio_16.1+dfsg1-5.1ubuntu2.debdiff

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to a duplicate bug report (2085575).
https://bugs.launchpad.net/bugs/2055842

Title:
  gstreamer: unreliable playback due to pulseaudio bug

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


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

[Bug 2055842] Re: gstreamer: unreliable playback due to pulseaudio bug

2024-12-09 Thread Alessandro Astone
noble debdiff

** Patch added: "pulseaudio_16.1+dfsg1-2ubuntu12.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/2055842/+attachment/5843140/+files/pulseaudio_16.1+dfsg1-2ubuntu12.debdiff

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to a duplicate bug report (2085575).
https://bugs.launchpad.net/bugs/2055842

Title:
  gstreamer: unreliable playback due to pulseaudio bug

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


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

[Bug 2055842] Re: gstreamer: unreliable playback due to pulseaudio bug

2024-12-09 Thread Alessandro Astone
Also proposed 16.2 in debian, which we can merge later on:
https://salsa.debian.org/pulseaudio-team/pulseaudio/-/merge_requests/28

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to a duplicate bug report (2085575).
https://bugs.launchpad.net/bugs/2055842

Title:
  gstreamer: unreliable playback due to pulseaudio bug

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


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

[Bug 2080498] Re: Default session type changed from Xorg to Wayland in some installs of 22.04 on Nvidia hybrids since kernel 6.8

2024-12-09 Thread Alessandro Astone
** Changed in: gdm3 (Ubuntu Jammy)
   Status: Incomplete => In Progress

** Changed in: gdm3 (Ubuntu Noble)
   Status: Incomplete => In Progress

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

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

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

Title:
  Default session type changed from Xorg to Wayland in some installs of
  22.04 on Nvidia hybrids since kernel 6.8

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


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

[Bug 2091325] Re: Remove gimp on s390x because it fails to build

2024-12-09 Thread Bug Watch Updater
** Changed in: gimp
   Status: Unknown => New

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

Title:
  Remove gimp on s390x because it fails to build

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


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

[Bug 2091325] [NEW] Remove gimp on s390x because it fails to build

2024-12-09 Thread Jeremy BĂ­cha
Public bug reported:

gimp fails to build on s390x. Since s390x is not a Desktop architecture
and the build failure is opaque, I request that gimp be removed on
s390x.

** Affects: gimp
 Importance: Unknown
 Status: Unknown

** Affects: gimp (Ubuntu)
 Importance: Undecided
 Status: Incomplete


** Tags: ftbfs plucky update-excuse

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

** Bug watch added: gitlab.gnome.org/GNOME/gimp/-/issues #12522
   https://gitlab.gnome.org/GNOME/gimp/-/issues/12522

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

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

Title:
  Remove gimp on s390x because it fails to build

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


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

[Bug 1881932] Re: subiquity isn't able to create btrfs subvolumes during installation

2024-12-09 Thread Jonas Gamao
Any progress?

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

Title:
  subiquity isn't able to create btrfs subvolumes during installation

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


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