date:20230512

Hello jeremyszu, or anyone else affected,

Accepted mesa into jammy-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/mesa/22.2.5-0ubuntu0.1~22.04.2 in a
few hours, and then in the -proposed repository.

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

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

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

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

** Changed in: mesa (Ubuntu Jammy)
   Status: In Progress => Fix Committed

** Tags added: verification-needed verification-needed-jammy

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

Title:
  Screen freeze when performing memory stress in Wayland mode

Status in Linux:
  New
Status in Mutter:
  Fix Released
Status in OEM Priority Project:
  Incomplete
Status in mesa package in Ubuntu:
  Fix Released
Status in mesa source package in Jammy:
  Fix Committed
Status in mesa source package in Kinetic:
  Won't Fix
Status in mesa source package in Lunar:
  Fix Released

Bug description:
  [Impact]

  Running stress-ng freezes the screen under wayland on intel iris.
  Upstream has fixed it in

  5aae8a05264c354aa93017d323ce238858f68227 iris: Retry 
DRM_IOCTL_I915_GEM_EXECBUFFER2 on ENOMEM
  646cff13bca8a92b846984d782ef00e57d34d7a1 Revert "iris: Avoid abort() if 
kernel can't allocate memory"

  which need to be backported for 22.2.5

  [Test case]

  Install the update, then

  1. stress-ng --stack 0 --timeout 300
  2. check the screen

  and note that it shouldn't freeze anymore.

  [Where things could go wrong]

  This moves checking ENOMEM to the right place, so it's hard to see how
  it might cause issues.

  --

  [Steps to reproduce]
  (disable systemd-oomd or executing over ssh)
  (below command allocates a lot of memory to stress kernel page fault)

  1. stress-ng --stack 0 --timeout 300
  2. check the screen

  [Expected result]
  Screen will update slowly when performing the stress-test.
  but screen needs back to work after stress.

  [Actual result]
  Screen freeze after stress test.

  [Additional information]
  kernel version: vmlinuz-5.17.0-1017-oem
  kernel version: vmlinuz-6.0.0-06rc4drmtip20220910-generic
  Mesa version: 22.0.5-0ubuntu0.1
  Mutter version: 42.2-0ubuntu1
  Gnome-shell version: 42.2-0ubuntu0.2

  * Issue happens in Wayland only

  * gnome-shell keeps issuing ioctl()
  ```
  (gdb) bt
  #0  __GI___ioctl (fd=fd@entry=14, request=request@entry=3223348419) at 
../sysdeps/unix/sysv/linux/ioctl.c:36
  #1  0x7fcacab0eb4f in intel_ioctl (arg=0x7fffc5404d80, 
request=3223348419, fd=14) at ../src/intel/common/intel_gem.h:75
  #2  iris_wait_syncobj (timeout_nsec=140736502713808, syncobj=, 
bufmgr=) at ../src/gallium/drivers/iris/iris_fence.c:229
  #3  iris_wait_syncobj (bufmgr=, syncobj=, 
timeout_nsec=timeout_nsec@entry=9223372036854775807) at 
../src/gallium/drivers/iris/iris_fence.c:215
  #4  0x7fcacab8beab in iris_get_query_result (result=0x7fffc5404e50, 
wait=, query=0x55774159b800, ctx=) at 
../src/gallium/drivers/iris/iris_query.c:635
  #5  iris_get_query_result (ctx=, query=0x55774159b800, 
wait=, result=0x7fffc5404e50) at 
../src/gallium/drivers/iris/iris_query.c:601
  #6  0x7fcaca405e89 in tc_get_query_result (_pipe=, 
query=0x55774159b800, wait=, result=0x7fffc5404e50) at 
../src/gallium/auxiliary/util/u_threaded_context.c:881
  #7  0x7fcaca0f0e64 in get_query_result (pipe=pipe@entry=0x55773f87bad0, 
q=q@entry=0x557741a0c790, wait=wait@entry=1 '\001') at 
../src/mesa/main/queryobj.c:266
  #8  0x7fcaca0f1b12 in _mesa_wait_query (q=0x557741a0c790, 
ctx=0x55773f8af980) at ../src/mesa/main/queryobj.c:344
  #9  get_query_object (ctx=0x55773f8af980, func=func@entry=0x7fcacaf28283 
"glGetQueryObjecti64v", id=, pname=34918, 
ptype=ptype@entry=5134, buf=0x0, offset=140736502714192)
  at ../src/mesa/main/queryobj.c:1174
  #10 0x7fcaca0f2d65 in _mesa_GetQueryObjecti64v (id=, 
pname=, params=) at 
../src/mesa/main/queryobj.c:1257
  #11 0x7fcadfa39b90 in ?? () from 
/usr/lib/x86_64-linux-gnu/mutter

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

Hello Kai, or anyone else affected,

Accepted mesa into jammy-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/mesa/22.2.5-0ubuntu0.1~22.04.2 in a
few hours, and then in the -proposed repository.

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

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

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

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

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

Title:
  kwin_x11: The X11 connection broke: I/O error (code 1)

Status in KDE Base Workspace:
  Fix Released
Status in Mesa:
  Fix Released
Status in kwin package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Fix Released
Status in kwin source package in Jammy:
  Invalid
Status in mesa source package in Jammy:
  Fix Committed
Status in kwin package in Debian:
  New

Bug description:
  [Impact]

  kwin might crash after running some time

  Two commits have been reverted upstream since 22.2.x branch was
  closed, needs those backported to fix this.

  [Test case]

  Run kwin for a day or so, which is usually enough time to hit this.

  Crash happens mostly on a notification popups, so system must be
  actively receiving notifications to test the crash. Without that crash
  may not happen even in a week of runtime.

  [Where things could go wrong]

  This just reverts two commits, and they have been upstream for a few
  months now, so these causing a regression is unlikely.

To manage notifications about this bug go to:
https://bugs.launchpad.net/kdebase-workspace/+bug/2003339/+subscriptions


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

[Desktop-packages] [Bug 2003339] Re: kwin_x11: The X11 connection broke: I/O error (code 1)

The revert is not in Kinetic, implying it could be affected by this bug
too. Do you intend to skip kinetic, or is it not affected?

** Changed in: mesa (Ubuntu Jammy)
   Status: In Progress => Fix Committed

** Tags added: verification-needed verification-needed-jammy

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

Title:
  kwin_x11: The X11 connection broke: I/O error (code 1)

Status in KDE Base Workspace:
  Fix Released
Status in Mesa:
  Fix Released
Status in kwin package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Fix Released
Status in kwin source package in Jammy:
  Invalid
Status in mesa source package in Jammy:
  Fix Committed
Status in kwin package in Debian:
  New

Bug description:
  [Impact]

  kwin might crash after running some time

  Two commits have been reverted upstream since 22.2.x branch was
  closed, needs those backported to fix this.

  [Test case]

  Run kwin for a day or so, which is usually enough time to hit this.

  Crash happens mostly on a notification popups, so system must be
  actively receiving notifications to test the crash. Without that crash
  may not happen even in a week of runtime.

  [Where things could go wrong]

  This just reverts two commits, and they have been upstream for a few
  months now, so these causing a regression is unlikely.

To manage notifications about this bug go to:
https://bugs.launchpad.net/kdebase-workspace/+bug/2003339/+subscriptions


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

[Desktop-packages] [Bug 2017142] Re: [jammy] VA-API doesn't work on DCN 3.1.4

Hello Mario, or anyone else affected,

Accepted mesa into jammy-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/mesa/22.2.5-0ubuntu0.1~22.04.2 in a
few hours, and then in the -proposed repository.

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

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

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

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

** Changed in: mesa (Ubuntu Jammy)
   Status: In Progress => Fix Committed

** Tags added: verification-needed verification-needed-jammy

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

Title:
  [jammy] VA-API doesn't work on DCN 3.1.4

Status in mesa package in Ubuntu:
  Fix Released
Status in mesa source package in Jammy:
  Fix Committed

Bug description:
  [ Impact ]
  VA-API decoding doesn't work on DCN 3.1.4.
  Mesa 22.2.5 includes all the code to support it but is missing the chip ID.

  The device ID was included in upstream mesa 22.3.1.

  [ Test Plan ]

   * Verify that VA-API works using "mpv" or a similar tool that uses VA-API
   * Verify that '# vainfo' shows the correct information.

  [ Where problems could occur ]

   * If just the new ID is backported then they would be unique to DCN 3.1.4 as 
it's now running VA-API codepaths.
   * If newer mesa point release is adopted, then it could be a regression that 
happened in changes on common code in mesa between those two point releases.

  [ Other Info ]
  * It can be cherry picked with this single commit:
  
https://gitlab.freedesktop.org/mesa/mesa/-/commit/4291e545d5a0f18c652f0ea57907f445392e8858

  * AMD has already tested cherry-picked commit on top of the Ubuntu
  mesa 22.2.5 package and verified it works.

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


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

[Desktop-packages] [Bug 1869470] Re: Can't minimize Thunderbird Lightning reminder window

2023-05-12 Thread KJ

Me too and it's really annoying cause it always has the focus and covers all 
the other windows.
No solution so far?

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

Title:
  Can't minimize Thunderbird Lightning reminder window

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

Bug description:
  Ever since Ubuntu moved back to Gnome from Unity, it's impossible to
  minimize the Thunderbird Lightning reminder window. It's really
  annoying, the window is always on top of Thunderbird and has to be
  constantly moved around to use the program.

  Closing the window makes no sense as a) it tends to start syncing the events 
with reminders, which can show conflict prompts requiring even more work from 
the user and b) the window comes back very quickly. So, minimize makes the most 
sense.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu21
  Architecture: amd64
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 20.04
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-10-12 (903 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20171011)
  NonfreeKernelModules: nvidia
  Package: mutter 3.36.0-2ubuntu1
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pl_PL.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
  Tags:  focal
  Uname: Linux 5.4.0-18-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-03-26 (7 days ago)
  UserGroups: audio cdrom dialout kvm lpadmin sudo vboxusers video
  _MarkForUpload: True

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


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

[Desktop-packages] [Bug 2012638] Re: tracker-extract-3 crashed with SIGSEGV in decorator_item_cache_remove()

2023-05-12 Thread Bug Watch Updater

** Changed in: tracker
   Status: New => Fix Released

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

Title:
  tracker-extract-3 crashed with SIGSEGV in
  decorator_item_cache_remove()

Status in Tracker:
  Fix Released
Status in tracker-miners package in Ubuntu:
  Fix Released
Status in ubuntu-release-upgrader package in Ubuntu:
  Fix Released

Bug description:
  https://errors.ubuntu.com/problem/76c7a9b949987c296ebfd60bf2328fc949156e32

  laptop freeze when trying change desktop background

  ProblemType: Crash
  DistroRelease: Ubuntu 23.04
  Package: tracker-extract 3.4.3-1ubuntu1
  ProcVersionSignature: Ubuntu 6.2.0-18.18-generic 6.2.6
  Uname: Linux 6.2.0-18-generic x86_64
  ApportVersion: 2.26.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Mar 23 15:49:56 2023
  ExecutablePath: /usr/libexec/tracker-extract-3
  InstallationDate: Installed on 2023-03-23 (0 days ago)
  InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20230323)
  ProcCmdline: /usr/libexec/tracker-extract-3
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  SegvAnalysis:
   Segfault happened at: 0x7f611a08e5b8:mov(%r15),%rbx
   PC (0x7f611a08e5b8) ok
   source "(%r15)" (0x2c0010b18b376185) not located in a known VMA region 
(needed readable region)!
   destination "%rbx" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: tracker-miners
  StacktraceTop:
   ?? () from 
/usr/lib/x86_64-linux-gnu/tracker-miners-3.0/libtracker-miner-3.0.so
   ?? () from /lib/x86_64-linux-gnu/libffi.so.8
   ?? () from /lib/x86_64-linux-gnu/libffi.so.8
   ffi_call () from /lib/x86_64-linux-gnu/libffi.so.8
   g_cclosure_marshal_generic () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: tracker-extract-3 crashed with SIGSEGV in ffi_call()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sudo users
  separator:

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


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

Re: [Desktop-packages] [Bug 1971984] Re: pcscd 1.9.5-3 do not start automatically, only manual

2023-05-12 Thread Ubucolors

Good news Tony, almost 1 year after the release of Ubuntu 22.04 finally a
solution that works.

Op vr 12 mei 2023 om 17:31 schreef Tony Espy
<1971...@bugs.launchpad.net>:

> I ran into this bug earlier this week while trying to setup my new
> Nitrokey HSM2 (https://docs.nitrokey.com/hsm/linux/) on a Thinkpad
> running 22.04 LTS.
>
> I've confirmed that the upstream commit from 1.9.9-2 fixes the problem,
> and am uploading this as a patch.
>
> ** Patch added: "Backported packaging fix from upstream 1.9.9-2"
>
> https://bugs.launchpad.net/ubuntu/+source/pcsc-lite/+bug/1971984/+attachment/5672739/+files/0001-Fix-dh_installsystemd-doesn-t-handle-files-in-usr-li.patch
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1971984
>
> Title:
>   pcscd 1.9.5-3 do not start automatically, only manual
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/pcsc-lite/+bug/1971984/+subscriptions
>
>

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

Title:
  pcscd 1.9.5-3 do not start automatically, only manual

Status in pcsc-lite package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu Mate 22.04 with the latest updates.
  Problem is present with internal smart-card reader and also external usb 
smart-card reader.

  eid-viewer sees no card reader,but When i do:

  sudo pcscd -f

  it is working, also following the tips of Ludovic:
  
https://ludovicrousseau.blogspot.com/2011/11/pcscd-auto-start-using-systemd.html

  sudo systemctl stop pcscd.socket
  sudo systemctl start pcscd.socket

  It is working until next restart.

  libacsccid1  version: 1.1.8-1
  libccid version: 1.5.0-2
  pcscd version: 1.9.5-3
  eid-archive version: 2022.3
  eid-mw version: 5.0.28v5.0.28-0u2204-1
  eid-viewer version: 5.0.28v5.0.28-0u2204-1

  In Firefox, my eid card is then also recognized, but only in the ESR
  version, but this is a know Mozilla bug.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pcsc-lite/+bug/1971984/+subscriptions


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

[Desktop-packages] [Bug 2018155] Re: gnome-magnifier prevents starting a graphical session

2023-05-12 Thread Arnold Loubriat

Hello Daniel,
There is no crash file generated, and going to the webpage you provided shows 
no error that could be linked to this issue.
But as I mentioned above, the issue should be very easy to reproduce.

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

Title:
  gnome-magnifier prevents starting a graphical session

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  After upgrading from Ubuntu 22.10 to Ubuntu 23.04, I am unable to
  login to my session as I always get the "Oh no! Something has gone
  wrong." error message.

  I have screen magnifier enabled, but disabling it using:
  gsettings set org.gnome.desktop.a11y.applications screen-magnifier-enabled 
false
  makes the issue disappear. I can reproduce the bug inside a virtual machine 
on Windows as well, with different hardware.
  The only piece of log I can find and that might be linked to the issue is:

  avril 29 11:21:19 arnold-ThinkStation-P620 systemd[6918]: Starting 
org.gnome.Shell@x11.service - GNOME Shell on X11...
  avril 29 11:21:19 arnold-ThinkStation-P620 dbus-daemon[6942]: [session 
uid=1000 pid=6942] Activating via systemd: service 
name='org.freedesktop.impl.portal.desktop.gtk' 
unit='xdg-desktop-portal-gtk.service' requested by ':1.52' (uid=1000 pid=7773 
comm="/usr/libexec/xdg-desktop-portal" label="unconfined")
  avril 29 11:21:19 arnold-ThinkStation-P620 systemd[6918]: Starting 
xdg-desktop-portal-gtk.service - Portal service (GTK/GNOME implementation)...
  avril 29 11:21:19 arnold-ThinkStation-P620 at-spi-bus-launcher[7212]: 
dbus-daemon[7212]: Activating service name='org.a11y.atspi.Registry' requested 
by ':1.5' (uid=1000 pid=7862 comm="/usr/libexec/xdg-desktop-portal-gtk" 
label="unconfined")
  avril 29 11:21:19 arnold-ThinkStation-P620 dbus-daemon[6942]: [session 
uid=1000 pid=6942] Activating service name='org.gnome.ScreenSaver' requested by 
':1.55' (uid=1000 pid=7862 comm="/usr/libexec/xdg-desktop-portal-gtk" 
label="unconfined")
  avril 29 11:21:19 arnold-ThinkStation-P620 at-spi-bus-launcher[7212]: 
dbus-daemon[7212]: Successfully activated service 'org.a11y.atspi.Registry'
  avril 29 11:21:19 arnold-ThinkStation-P620 at-spi-bus-launcher[7869]: 
SpiRegistry daemon is running with well-known name - org.a11y.atspi.Registry
  avril 29 11:21:19 arnold-ThinkStation-P620 gnome-shell[7863]: Running GNOME 
Shell (using mutter 44.0) as a X11 window and compositing manager
  avril 29 11:21:19 arnold-ThinkStation-P620 dbus-daemon[6942]: [session 
uid=1000 pid=6942] Successfully activated service 'org.gnome.ScreenSaver'
  avril 29 11:21:19 arnold-ThinkStation-P620 gnome-session[7361]: 
gnome-session-binary[7361]: WARNING: Could not retrieve current screensaver 
active state: GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message recipient 
disconnected from message bus without replying
  avril 29 11:21:19 arnold-ThinkStation-P620 gnome-session-binary[7361]: 
WARNING: Could not retrieve current screensaver active state: 
GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message recipient disconnected 
from message bus without replying
  avril 29 11:21:19 arnold-ThinkStation-P620 dbus-daemon[6942]: [session 
uid=1000 pid=6942] Successfully activated service 
'org.freedesktop.impl.portal.desktop.gtk'
  avril 29 11:21:19 arnold-ThinkStation-P620 systemd[6918]: Started 
xdg-desktop-portal-gtk.service - Portal service (GTK/GNOME implementation).
  avril 29 11:21:19 arnold-ThinkStation-P620 dbus-daemon[6942]: [session 
uid=1000 pid=6942] Successfully activated service 
'org.freedesktop.portal.Desktop'
  avril 29 11:21:19 arnold-ThinkStation-P620 systemd[6918]: Started 
xdg-desktop-portal.service - Portal service.
  avril 29 11:21:19 arnold-ThinkStation-P620 snapd-desktop-i[7769]: New theme: 
gtk=Yaru icon=Yaru cursor=(null), sound=Yaru
  avril 29 11:21:19 arnold-ThinkStation-P620 snapd-desktop-i[7769]: All 
available theme snaps installed
  avril 29 11:21:19 arnold-ThinkStation-P620 gnome-shell[7984]: libEGL warning: 
DRI2: failed to authenticate
  avril 29 11:21:19 arnold-ThinkStation-P620 kernel: gnome-shell[7863]: 
segfault at 18 ip 7f7af86b2004 sp 7ffeb1dc3a18 error 4 in 
libmutter-12.so.0.0.0[7f7af864a000+13d000] likely on CPU 15 (core 15, socket 0)
  avril 29 11:21:19 arnold-ThinkStation-P620 kernel: Code: 00 00 00 00 66 90 f3 
0f 1e fa 48 63 05 79 67 16 00 48 8b 04 07 c3 f3 0f 1e fa 48 8b 87 40 01 00 00 
c3 0f 1f 40 00 f3 0f 1e fa <48> 8b 47 18 c3 0f 1f 80 00 00 00 00 f3 0f 1e fa 48 
8b 47 28 c3 0f
  avril 29 11:21:20 arnold-ThinkStation-P620 systemd[6918]: 
org.gnome.Shell@x11.service: Main process exited, code=dumped, status=11/SEGV
  avril 29 11:21:20 arnold-ThinkStation-P620 systemd[6918]: 
org.gnome.Shell@x11.service: Failed with result 'core-dump'.
  avril 29 11:21:20 arnold-ThinkStation-P620 systemd[6918]: Failed to start 
org.gnome.Shell@x11.service - GNOME Shell on X1

[Desktop-packages] [Bug 1987976] Re: firefox black window on wayland

2023-05-12 Thread Gunnar Hjalmarsson

As regards the failed autopkgtest on amd64, it's reasonably not related
to the proposed change, since also version 44.0-2ubuntu4 fails now
(unlike before the 23.04 release). My impression is that it's a problem
beyond the mutter package:

Running test case...
TAP version 13
# random seed: R02S29be415b178acf3a28289b5a6c5eecf4
# GLib-GIO-DEBUG: _g_io_module_get_default: Found default implementation memory 
(GMemorySettingsBackend) for ‘gsettings-backend’
# libmutter-MESSAGE: Running Mutter Test (using mutter 44.0) as a Wayland 
display server
Bail out! libmutter-FATAL-WARNING: Failed to open gpu '/dev/dri/card0': 
Couldn't find render node device for '/dev/dri/card0'
Trace/breakpoint trap (core dumped)
FAIL: 
mutter-12/closed-transient-no-input-parent-delayed-focus-default-cancelled.test 
(Child process exited with code 133)
Running test: mutter-12/closed-transient-no-input-no-take-focus-parents.test
Starting D-Bus daemons (session & system)...
Launching required services...
Starting mocked services...
Running test case...
TAP version 13
# random seed: R02Se6b3bbfe78ba522ee4e9987b0b12eb51
# GLib-GIO-DEBUG: _g_io_module_get_default: Found default implementation memory 
(GMemorySettingsBackend) for ‘gsettings-backend’
# libmutter-MESSAGE: Running Mutter Test (using mutter 44.0) as a Wayland 
display server
Bail out! libmutter-FATAL-WARNING: Failed to open gpu '/dev/dri/card0': 
Couldn't find render node device for '/dev/dri/card0'
Trace/breakpoint trap (core dumped)
FAIL: mutter-12/closed-transient-no-input-no-take-focus-parents.test (Child 
process exited with code 133)

The very same failure happens in mantic:

https://autopkgtest.ubuntu.com/packages/m/mutter/mantic/amd64

but somebody seems to have added a hint so 44.0-2ubuntu6 migrated to
mantic-release, and I suppose doing so would be motivated for
lunar/amd64 too.

As regards the regular verification, I successfully accomplished the
steps in the test plan using version 44.0-2ubuntu4.23.04.1 (from lunar-
proposed) of the binaries built by the mutter source.

** Tags removed: verification-needed verification-needed-lunar
** Tags added: verification-done verification-done-lunar

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

Title:
  firefox black window on wayland

Status in Mozilla Firefox:
  Unknown
Status in Mutter:
  New
Status in Release Notes for Ubuntu:
  Fix Released
Status in mutter package in Ubuntu:
  Fix Released
Status in mutter source package in Lunar:
  Fix Committed

Bug description:
  [ Impact ]

  On some systems, when you open the Firefox snap right after having
  logged in into an Ubuntu on Wayland session, you are met by a black
  window. This happens because the FF snap is run under Xwayland, and
  Xwayland may not be enabled early enough to handle the start of the
  application properly.

  You can easily reproduce the issue in a Wayland session:

  * Close Firefox
  * Run the command "killall Xwayland" in terminal
  * Open Firefox

  An upstream mutter change addresses this issue, and the proposed lunar
  change cherry picks that upstream change as a patch.

  [ Test Plan ]

  On an updated Ubuntu 23.04:

  * Install the mutter related binaries from lunar-proposed

  * Reboot and log in to an Ubuntu on Wayland session

  * Run the command "killall Xwayland"

  * Open the Firefox snap, and find that it starts normally

  [ Where problems could occur ]

  This is the upstream merge request in question:

  https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2970

  The changes (except for the test related ones) are small, and
  specifically intended to address issues like the one reported in this
  bug. There are also reviews by a couple of experienced GNOME devs.

  So even if the proposed change is not well tested yet, it seems to me
  that the risk for adverse side effects is limited.

  [ Original description ]

  nicolas@nicolas-fixe:~$ lsb_release -rd
  Description:  Ubuntu 22.04.1 LTS
  Release:  22.04

  nicolas@nicolas-fixe:~$ apt-cache policy firefox
  firefox:
    Installé : 1:1snap1-0ubuntu2
    Candidat : 1:1snap1-0ubuntu2
   Table de version :
   *** 1:1snap1-0ubuntu2 500
  500 http://fr.archive.ubuntu.com/ubuntu jammy/main amd64 Packages
  100 /var/lib/dpkg/status

  When I boot Ubuntu and start Firefox, the Firefox's window is totally
  black. See attachment.

  I am at your disposal to answer any question you have.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: firefox 1:1snap1-0ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39
  Uname: Linux 5.15.0-46-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Aug 28 12:42:29 2022
  InstallationDate: Installed on 2022-08-25 (2 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(

[Desktop-packages] [Bug 1987528] Re: Since upgrade from 20.04 → 22.04 ; unable to print in color, only black and white

2023-05-12 Thread Ian Gordon

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

I suspect this problem is caused by this issue
(https://github.com/OpenPrinting/cups/pull/500) that is fixed in cups
where the option print-color-mode is set to monochrome when the printer
PPD file has ColorModel: CMYK and not ColorModel: RGB (Our Ricoh C4500
uses CMYK as its ColorModel: CMYK)

We were trying to use

lpadmin -p  -o print-color-mode-default=colour
lpadmin -p  -o print-color-mode=colour

and this worked the first time we printed to the printer and then it
would reset to "monochrome" which I suspect is caused by this report
typo: https://github.com/OpenPrinting/cups/pull/687

Cheers,

Ian.

PS Failed to note this was a duplicate bug before posting. Apologies.
And I see it is already know in #1971242 that the latest version of cups
fixes the issue

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

Title:
  Since upgrade from 20.04 → 22.04 ; unable to print in color, only
  black and white

Status in cups-filters package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  Printer ( in my context ) is Ricoh Aficio mpc 3002 and most Ricoh's
  drivers are open-source (
  https://www.openprinting.org/printer/Ricoh/Ricoh-Aficio_MP_C3002 )

  Since I « upgraded » my installation from 20.04 → 22.04, I'm unable to
  print in colors, only black and white, whatever I set in driver.

  I tried what's suggested in
  ⋅ 
https://askubuntu.com/questions/1410583/upgrading-to-22-04-printer-doesnt-works-in-color
  ⋅ 
https://discourse.ubuntubudgie.org/t/22-04-unable-to-add-printer-which-perfectly-worked-in-20-04/6209

  I might go wrong somewhere cause I still can't manage to print in color.
  → the snap thing ( Gutenprint Printer Application ) does not detect my ( 
network ) printer,
  → I'm not sure of the name for PRINTER I should input in command « lpadmin -p 
PRINTER -o print-color-mode-default=color » ( and is this as normal user or 
sudo ? )

  It seems related to
  ⋅ https://github.com/OpenPrinting/cups/issues/421

  It's a regression ( as it used to work out of the box before 22.04 ).

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


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

[Desktop-packages] [Bug 1971242] Re: printing PDF appears always grey, no color

2023-05-12 Thread Ian Gordon

I suspect this problem is caused by this issue
(https://github.com/OpenPrinting/cups/pull/500) that is fixed in cups
where the option print-color-mode is set to monochrome when the printer
PPD file has ColorModel: CMYK and not ColorModel: RGB (Our Ricoh C4500
uses CMYK as its ColorModel: CMYK)

We were trying to use

lpadmin -p  -o print-color-mode-default=colour
lpadmin -p  -o print-color-mode=colour

and this worked the first time we printed to the printer and then it
would reset to "monochrome" which I suspect is caused by this reported
typo: https://github.com/OpenPrinting/cups/pull/687

Cheers,

Ian.

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

Title:
  printing PDF appears always grey, no color

Status in CUPS:
  New
Status in atril package in Ubuntu:
  Confirmed
Status in cups package in Ubuntu:
  Confirmed
Status in okular package in Ubuntu:
  Confirmed

Bug description:
  After upgrading from 20.04 LTS to 22.04 LTS I can't print colored PDF
  document. The print appears always b/w regardless color printing was
  enabled or not. Printing from LibreOffice produces a color print. This
  behavior (bug) is reproducible on three upgraded machines. It would be
  nice to have color print back again.

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


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

[Desktop-packages] [Bug 1969901] Re: network-manager fails to renew ipv6 address

2023-05-12 Thread Mathew Hodson

** Tags added: patch

** Changed in: network-manager (Ubuntu Bionic)
   Status: Incomplete => Triaged

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

Title:
  network-manager fails to renew ipv6 address

Status in network-manager package in Ubuntu:
  Fix Released
Status in network-manager source package in Bionic:
  Triaged

Bug description:
  [Impact]

   * This affects Ubuntu 18.04 where Network Manager version 1.10.6 is
  used.

   * Network manager might kill dhclient(6) and fail to start it again
     causing the IPv6 address to be lost on a network that uses mixed
     IPv4/IPV6.
     The network status will still be seen as online in gnome since ipv4
     is still active.
     The user then have to manually remove the dhcpv6 lease files and
     restart ipv6 connection/restart network manager to regain IPv6
     connectivity.

   * This is a cherry-pick from Network manager 1.10.8 (Ubuntu's version
     is based on 1.10.6):
     
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/commit/7fbbe7ebee99785e38d39c37e515a64a28edef0f

   * Upstream bug:
     https://bugzilla.gnome.org/show_bug.cgi?id=783391

  [Test Plan]

  The test requires three computers
  * one computer runing isc dhcpd server (with network configured static)
  * one computer running patched network manager
  * one computer running vanilla ubuntu

  The idea is to execute on an isolated network and trigger the error by 
changing
  ip range handed out by the dhcp-server to force a nack response back to the
  clients.

  Expected result
  * patched network keeps dhclient6 alive
  * vanilla network manager will fail to keep dhclient6 alive
in network manager logs dhcp6 will expire and not be restarted

  ON THE SERVER
  # Disable app-armor, as it has rules restricting dhcpd
  aa-teardown

  # install isc dhcpserver
  isc-dhcp-server

  # configure network static
  sudo nmcli connection modify "${CONNECTION_NAME}" \
   ipv4.method "manual" \
   ipv4.addresses "192.168.1.1/24" \
   ipv4.gateway "192.168.1.254" \
   ipv4.dns "192.168.1.1" \
   ipv6.method "manual" \
   ipv6.addresses "2001:db8:0:1::1/64" \
   ipv6.gateway "2001:db8:0:1::ffbb" \
   ipv6.dns "2001:db8:0:1::1/64"

  mkdir -p tmp
  touch tmp/dhcpd4_a.leases
  touch tmp/dhcpd4_b.leases
  touch tmp/dhcpd6_a.leases
  touch tmp/dhcpd6_b.leases

  Then it is time to execute dhcpd
  -f - run in foreground
  -d - print errors to stderr instead of syslog

  # Start in separate terminals
  dhcpd -f -d -4 -cf dhcp_v4_a.conf -lf tmp/dhcpd4_a.leases enp0s31f6
  dhcpd -f -d -6 -cf dhcp_v6_a.conf -lf tmp/dhcpd6_a.leases enp0s31f6

  Press ctrl-C to kill servers, then restart with the b configurations

  dhcpd -f -d -4 -cf dhcp_v4_b.conf -lf tmp/dhcpd4_b.leases enp0s31f6
  dhcpd -f -d -6 -cf dhcp_v6_b.conf -lf tmp/dhcpd6_b.leases enp0s31f6

  Then leases to expire (check for clients that kills dhclient)
  Press ctrl-C to kill servers, then restart with the a configurations

  ON THE CLIENTS
  Setup:
  Configure ipv6 network in settings to use dhcp (using the gui)

  Test:
  check that dhcp clients are still running:
  ps aux|grep dhclient

  Expected in output
  one client for dhcpv4
  one client for dhcpv6

  Also check network manager status :
  journalctl -u NetworkManager.service
  journalctl -u NetworkManager.service|grep dhcp6 # to only view dhclient6
  journalctl -u NetworkManager.service|grep dhcp4 # to only view dhclient4

  if dhclient is not running:
  stop network in gui
  remove lease files (/var/lib/NetworkManager/dhclient*.lease). Only remove the 
lease for the client not running.
  start network in gui

  if dhclients are running:
  wait additional ten minutes, repeat from beginning of test

  [Where problems could occur]

   * The change is in the dchp lease expiration handling so verify that
  there is no regression in dhcp renewals on different type of
  configuration include IPv6

  [Other Info]
   * We have tested this patch on a couple of clients where we have seen this
     this problem. If this patch is feasible to include in Ubuntu 18.04 we
     could request more users to test.

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


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

[Desktop-packages] [Bug 1998782] Re: Totem unable to play video on Raspberry Pi: "could not initialize OpenGL support"

2023-05-12 Thread Leó Kolbeinsson

This bug is still present in Ubuntu Daily Mantic RaspPI ISO dated
12-05-2023

** Tags added: mantic

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

Title:
  Totem unable to play video on Raspberry Pi: "could not initialize
  OpenGL support"

Status in totem package in Ubuntu:
  Confirmed

Bug description:
  Testing Ubuntu Lunar Daily RaspPI 4 image dated 2022-12-05

  I received this error trying to play the video "big_buck_bunny" in
  Totem as per the testcase:

  This maybe a duplicate of the old bug 1969512 but as the error message
  is not the same a new bug is filed.

  See attached screenshot.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: totem 43.0-2ubuntu1
  ProcVersionSignature: Ubuntu 5.19.0-1004.10-raspi 5.19.7
  Uname: Linux 5.19.0-1004-raspi aarch64
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: arm64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Dec  5 11:24:38 2022
  ImageMediaBuild: 20221205
  LogAlsaMixer:
   Simple mixer control 'PCM',0
 Capabilities: pvolume pvolume-joined pswitch pswitch-joined
 Playback channels: Mono
 Limits: Playback -10239 - 400
 Mono: Playback -1988 [78%] [-19.88dB] [on]
  SourcePackage: totem
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Desktop-packages] [Bug 1987976] Re: firefox black window on wayland

2023-05-12 Thread Mathew Hodson

** No longer affects: firefox (Ubuntu)

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

Title:
  firefox black window on wayland

Status in Mozilla Firefox:
  Unknown
Status in Mutter:
  New
Status in Release Notes for Ubuntu:
  Fix Released
Status in mutter package in Ubuntu:
  Fix Released
Status in mutter source package in Lunar:
  Fix Committed

Bug description:
  [ Impact ]

  On some systems, when you open the Firefox snap right after having
  logged in into an Ubuntu on Wayland session, you are met by a black
  window. This happens because the FF snap is run under Xwayland, and
  Xwayland may not be enabled early enough to handle the start of the
  application properly.

  You can easily reproduce the issue in a Wayland session:

  * Close Firefox
  * Run the command "killall Xwayland" in terminal
  * Open Firefox

  An upstream mutter change addresses this issue, and the proposed lunar
  change cherry picks that upstream change as a patch.

  [ Test Plan ]

  On an updated Ubuntu 23.04:

  * Install the mutter related binaries from lunar-proposed

  * Reboot and log in to an Ubuntu on Wayland session

  * Run the command "killall Xwayland"

  * Open the Firefox snap, and find that it starts normally

  [ Where problems could occur ]

  This is the upstream merge request in question:

  https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2970

  The changes (except for the test related ones) are small, and
  specifically intended to address issues like the one reported in this
  bug. There are also reviews by a couple of experienced GNOME devs.

  So even if the proposed change is not well tested yet, it seems to me
  that the risk for adverse side effects is limited.

  [ Original description ]

  nicolas@nicolas-fixe:~$ lsb_release -rd
  Description:  Ubuntu 22.04.1 LTS
  Release:  22.04

  nicolas@nicolas-fixe:~$ apt-cache policy firefox
  firefox:
    Installé : 1:1snap1-0ubuntu2
    Candidat : 1:1snap1-0ubuntu2
   Table de version :
   *** 1:1snap1-0ubuntu2 500
  500 http://fr.archive.ubuntu.com/ubuntu jammy/main amd64 Packages
  100 /var/lib/dpkg/status

  When I boot Ubuntu and start Firefox, the Firefox's window is totally
  black. See attachment.

  I am at your disposal to answer any question you have.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: firefox 1:1snap1-0ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39
  Uname: Linux 5.15.0-46-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Aug 28 12:42:29 2022
  InstallationDate: Installed on 2022-08-25 (2 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  Snap.Changes: aucun changement trouvé
  SourcePackage: firefox
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Desktop-packages] [Bug 1926165] Re: Bass speakers not enabled on Lenovo Yoga 9i

2023-05-12 Thread Tim Woelfle

I'm now on Ubuntu 23.04 (incl. new kernel) and managed to make the bass
work on my Lenovo Yoga 9 14IAP7 through this trick:
https://wiki.archlinux.org/title/Lenovo_Yoga_9i_2022_(14AiPI7)#Audio

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

Title:
  Bass speakers not enabled on Lenovo Yoga 9i

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  The Lenovo Yoga 9i has two sets of speakers: regular ones and bass
  speakers. The former work but while latter are detected and show up in
  alsamixer, they play no sound. Plugging headphones in and out or
  toggling any of the volume options does not fix the issue.

  A possibly related issue for a different Yoga version:
  https://bugzilla.kernel.org/show_bug.cgi?id=205755

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu7
  ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
  Uname: Linux 5.11.0-16-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 4466 F pulseaudio
ubuntu 6219 F alsamixer
   /dev/snd/pcmC0D0p:   ubuntu 4466 F...m pulseaudio
  CasperMD5CheckResult: pass
  CasperVersion: 1.461
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr 26 15:10:05 2021
  LiveMediaBuild: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:sofhdadsp 
successful
  Symptom_Card: Tiger Lake-LP Smart Sound Technology Audio Controller - 
sof-hda-dsp
  Symptom_Jack: Speaker, Internal
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: None of the above
  Title: [82BG, Realtek ALC287, Speaker, Internal] Playback problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/28/2021
  dmi.bios.release: 1.40
  dmi.bios.vendor: LENOVO
  dmi.bios.version: EHCN40WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697WIN
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Yoga 9 14ITL5
  dmi.ec.firmware.release: 1.40
  dmi.modalias: 
dmi:bvnLENOVO:bvrEHCN40WW:bd01/28/2021:br1.40:efr1.40:svnLENOVO:pn82BG:pvrYoga914ITL5:rvnLENOVO:rnLNVNB161216:rvrSDK0J40697WIN:cvnLENOVO:ct31:cvrYoga914ITL5:
  dmi.product.family: Yoga 9 14ITL5
  dmi.product.name: 82BG
  dmi.product.sku: LENOVO_MT_82BG_BU_idea_FM_Yoga 9 14ITL5
  dmi.product.version: Yoga 9 14ITL5
  dmi.sys.vendor: LENOVO

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


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

[Desktop-packages] [Bug 1316202] Re: Can't change date or time manually

2023-05-12 Thread Bryan Quigley

** Changed in: unity-control-center (Ubuntu)
   Status: Confirmed => Invalid

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

Title:
  Can't change date or time manually

Status in unity-control-center package in Ubuntu:
  Invalid

Bug description:
  1) Ubuntu 14.04
  2) 14.04.3+14.04.20140410-0ubuntu1 
  3) I should be able to use the GUI "Time & Date Settings" manual option to 
set the date/time.  
  4) Changes were just completely ignored

  I also had issues changing the date on 12.04, but time seemed to work
  there.

  Step by step:
  1. Click on the Clock and go to Time and Date Settings
  2. Switch "Set the Time" to manually.
  3. Change the date and time and close the window.
  4. Click on the Clock and go to Time and Date Settings, see how the time/date 
is back to where it was before.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity-control-center 14.04.3+14.04.20140410-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  Date: Mon May  5 11:40:48 2014
  InstallationDate: Installed on 2014-04-27 (7 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: unity-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_unity-control-center:
   activity-log-manager 0.9.7-0ubuntu14
   deja-dup 30.0-0ubuntu4
   gnome-control-center 1:3.6.3-0ubuntu56

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


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

[Desktop-packages] [Bug 1921939] Re: Create Upstream Repo

2023-05-12 Thread Bryan Quigley

** Changed in: software-properties (Ubuntu)
   Status: Confirmed => Invalid

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

Title:
  Create Upstream Repo

Status in software-properties package in Ubuntu:
  Invalid

Bug description:
  I started investigating this due to software-properties in Debian
  being listed as under-maintained per
  https://mako.cc/copyrighteous/identifying-underproduced-software

  AFAICT the source of truth for this package is in the current Ubuntu
  packages.  Would it be possible to make a real upstream repo that both
  Debian and Ubuntu can eventually pull from?

  Today, the Debian package has no updates for a while and I get that
  many of the additions are for Livepatch/other ubuntu specific things.
  If it's better for software-properties in Debian to just become it's
  own thing, that's a path too.

  Related debian bug:
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=661908

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


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

[Desktop-packages] [Bug 1971984] Re: pcscd 1.9.5-3 do not start automatically, only manual

2023-05-12 Thread Tony Espy

I ran into this bug earlier this week while trying to setup my new
Nitrokey HSM2 (https://docs.nitrokey.com/hsm/linux/) on a Thinkpad
running 22.04 LTS.

I've confirmed that the upstream commit from 1.9.9-2 fixes the problem,
and am uploading this as a patch.

** Patch added: "Backported packaging fix from upstream 1.9.9-2"
   
https://bugs.launchpad.net/ubuntu/+source/pcsc-lite/+bug/1971984/+attachment/5672739/+files/0001-Fix-dh_installsystemd-doesn-t-handle-files-in-usr-li.patch

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

Title:
  pcscd 1.9.5-3 do not start automatically, only manual

Status in pcsc-lite package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu Mate 22.04 with the latest updates.
  Problem is present with internal smart-card reader and also external usb 
smart-card reader.

  eid-viewer sees no card reader,but When i do:

  sudo pcscd -f

  it is working, also following the tips of Ludovic:
  
https://ludovicrousseau.blogspot.com/2011/11/pcscd-auto-start-using-systemd.html

  sudo systemctl stop pcscd.socket
  sudo systemctl start pcscd.socket

  It is working until next restart.

  libacsccid1  version: 1.1.8-1
  libccid version: 1.5.0-2
  pcscd version: 1.9.5-3
  eid-archive version: 2022.3
  eid-mw version: 5.0.28v5.0.28-0u2204-1
  eid-viewer version: 5.0.28v5.0.28-0u2204-1

  In Firefox, my eid card is then also recognized, but only in the ESR
  version, but this is a know Mozilla bug.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pcsc-lite/+bug/1971984/+subscriptions


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

[Desktop-packages] [Bug 1951586] Re: Need option to specify wifi regulatory domain

2023-05-12 Thread James Falcon

Tracked in Github Issues as https://github.com/canonical/cloud-
init/issues/3926

** Bug watch added: github.com/canonical/cloud-init/issues #3926
   https://github.com/canonical/cloud-init/issues/3926

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

Title:
  Need option to specify wifi regulatory domain

Status in cloud-init:
  Invalid
Status in netplan:
  Fix Released
Status in NetworkManager:
  New
Status in netplan.io package in Ubuntu:
  Fix Released
Status in network-manager package in Ubuntu:
  Incomplete
Status in netplan.io source package in Jammy:
  Triaged
Status in network-manager source package in Jammy:
  Incomplete
Status in netplan.io source package in Kinetic:
  Fix Released
Status in network-manager source package in Kinetic:
  Incomplete

Bug description:
  It would be nice if netplan offered an option to specify the wifi
  regulatory domain (country code).

  
  For devices such as the Raspberry Pi you are currently advertising that users 
can simply setup Ubuntu Server headless by putting the wifi configuration 
details in cloudinit/netplan's "network-config" on the FAT partition of the SD 
card: 
https://ubuntu.com/tutorials/how-to-install-ubuntu-on-your-raspberry-pi#3-wifi-or-ethernet
  But an option to set the wifi country code there does not seem to exist, so 
may not work.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1951586/+subscriptions


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

[Desktop-packages] [Bug 1987976] Autopkgtest regression report (mutter/44.0-2ubuntu4.23.04.1)

2023-05-12 Thread Ubuntu SRU Bot

All autopkgtests for the newly accepted mutter (44.0-2ubuntu4.23.04.1) for 
lunar have finished running.
The following regressions have been reported in tests triggered by the package:

mutter/44.0-2ubuntu4.23.04.1 (amd64)


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/lunar/update_excuses.html#mutter

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

Thank you!

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

Title:
  firefox black window on wayland

Status in Mozilla Firefox:
  Unknown
Status in Mutter:
  New
Status in Release Notes for Ubuntu:
  Fix Released
Status in firefox package in Ubuntu:
  Invalid
Status in mutter package in Ubuntu:
  Fix Released
Status in mutter source package in Lunar:
  Fix Committed

Bug description:
  [ Impact ]

  On some systems, when you open the Firefox snap right after having
  logged in into an Ubuntu on Wayland session, you are met by a black
  window. This happens because the FF snap is run under Xwayland, and
  Xwayland may not be enabled early enough to handle the start of the
  application properly.

  You can easily reproduce the issue in a Wayland session:

  * Close Firefox
  * Run the command "killall Xwayland" in terminal
  * Open Firefox

  An upstream mutter change addresses this issue, and the proposed lunar
  change cherry picks that upstream change as a patch.

  [ Test Plan ]

  On an updated Ubuntu 23.04:

  * Install the mutter related binaries from lunar-proposed

  * Reboot and log in to an Ubuntu on Wayland session

  * Run the command "killall Xwayland"

  * Open the Firefox snap, and find that it starts normally

  [ Where problems could occur ]

  This is the upstream merge request in question:

  https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2970

  The changes (except for the test related ones) are small, and
  specifically intended to address issues like the one reported in this
  bug. There are also reviews by a couple of experienced GNOME devs.

  So even if the proposed change is not well tested yet, it seems to me
  that the risk for adverse side effects is limited.

  [ Original description ]

  nicolas@nicolas-fixe:~$ lsb_release -rd
  Description:  Ubuntu 22.04.1 LTS
  Release:  22.04

  nicolas@nicolas-fixe:~$ apt-cache policy firefox
  firefox:
    Installé : 1:1snap1-0ubuntu2
    Candidat : 1:1snap1-0ubuntu2
   Table de version :
   *** 1:1snap1-0ubuntu2 500
  500 http://fr.archive.ubuntu.com/ubuntu jammy/main amd64 Packages
  100 /var/lib/dpkg/status

  When I boot Ubuntu and start Firefox, the Firefox's window is totally
  black. See attachment.

  I am at your disposal to answer any question you have.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: firefox 1:1snap1-0ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39
  Uname: Linux 5.15.0-46-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Aug 28 12:42:29 2022
  InstallationDate: Installed on 2022-08-25 (2 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  Snap.Changes: aucun changement trouvé
  SourcePackage: firefox
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Desktop-packages] [Bug 2019378] [NEW] HDMI sound not working

2023-05-12 Thread Ton Hofhuis

Public bug reported:

Running Ubuntu 23.04 with all the latest patches on Dell XPS 15 9510/Nvidia 
3050Ti via Thunderbolt 4 cable attached to a DELL WB22TB4 dockingstation via 
Displayport 2.0 cable to an Asus 4K monitor with an audio out to a surround 
set. 
The sound via HDMI was working great when running 22.10, but works rarely on 
23.04 (I haven't figured out which set-up it always does work). nVidia driver = 
525.105.17

More questions on ton.hofh...@canonical.com or via MM @ton211

ProblemType: Bug
DistroRelease: Ubuntu 23.04
Package: alsa-base 1.0.25+dfsg-0ubuntu7
ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
Uname: Linux 6.2.0-20-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
ApportVersion: 2.26.1-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  ton5180 F wireplumber
 /dev/snd/controlC1:  ton5180 F wireplumber
 /dev/snd/pcmC1D0c:   ton5176 F...m pipewire
 /dev/snd/seq:ton5176 F pipewire
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Fri May 12 16:06:40 2023
InstallationDate: Installed on 2023-02-02 (98 days ago)
InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/10/2023
dmi.bios.release: 1.19
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.19.0
dmi.board.name: 01V4T3
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.19.0:bd03/10/2023:br1.19:svnDellInc.:pnXPS159510:pvr:rvnDellInc.:rn01V4T3:rvrA00:cvnDellInc.:ct10:cvr:sku0A61:
dmi.product.family: XPS
dmi.product.name: XPS 15 9510
dmi.product.sku: 0A61
dmi.sys.vendor: Dell Inc.

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


** Tags: amd64 apport-bug lunar

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

Title:
  HDMI sound not working

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Running Ubuntu 23.04 with all the latest patches on Dell XPS 15 9510/Nvidia 
3050Ti via Thunderbolt 4 cable attached to a DELL WB22TB4 dockingstation via 
Displayport 2.0 cable to an Asus 4K monitor with an audio out to a surround 
set. 
  The sound via HDMI was working great when running 22.10, but works rarely on 
23.04 (I haven't figured out which set-up it always does work). nVidia driver = 
525.105.17

  More questions on ton.hofh...@canonical.com or via MM @ton211

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu7
  ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
  Uname: Linux 6.2.0-20-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ton5180 F wireplumber
   /dev/snd/controlC1:  ton5180 F wireplumber
   /dev/snd/pcmC1D0c:   ton5176 F...m pipewire
   /dev/snd/seq:ton5176 F pipewire
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Fri May 12 16:06:40 2023
  InstallationDate: Installed on 2023-02-02 (98 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/10/2023
  dmi.bios.release: 1.19
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.19.0
  dmi.board.name: 01V4T3
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.19.0:bd03/10/2023:br1.19:svnDellInc.:pnXPS159510:pvr:rvnDellInc.:rn01V4T3:rvrA00:cvnDellInc.:ct10:cvr:sku0A61:
  dmi.product.family: XPS
  dmi.product.name: XPS 15 9510
  dmi.product.sku: 0A61
  dmi.sys.vendor: Dell Inc.

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


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

[Desktop-packages] [Bug 2019379] [NEW] HDMI sound not working

2023-05-12 Thread Ton Hofhuis

Public bug reported:

Running Ubuntu 23.04 with all the latest patches on Dell XPS 15 9510/Nvidia 
3050Ti via Thunderbolt 4 cable attached to a DELL WB22TB4 dockingstation via 
Displayport 2.0 cable to an Asus 4K monitor with an audio out to a surround 
set. 
The sound via HDMI was working great when running 22.10, but works rarely on 
23.04 (I haven't figured out which set-up it always does work). nVidia driver = 
525.105.17

More questions on ton.hofh...@canonical.com or via MM @ton211

ProblemType: Bug
DistroRelease: Ubuntu 23.04
Package: alsa-base 1.0.25+dfsg-0ubuntu7
ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
Uname: Linux 6.2.0-20-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
ApportVersion: 2.26.1-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  ton5180 F wireplumber
 /dev/snd/controlC1:  ton5180 F wireplumber
 /dev/snd/pcmC1D0c:   ton5176 F...m pipewire
 /dev/snd/seq:ton5176 F pipewire
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Fri May 12 16:06:40 2023
InstallationDate: Installed on 2023-02-02 (98 days ago)
InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/10/2023
dmi.bios.release: 1.19
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.19.0
dmi.board.name: 01V4T3
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.19.0:bd03/10/2023:br1.19:svnDellInc.:pnXPS159510:pvr:rvnDellInc.:rn01V4T3:rvrA00:cvnDellInc.:ct10:cvr:sku0A61:
dmi.product.family: XPS
dmi.product.name: XPS 15 9510
dmi.product.sku: 0A61
dmi.sys.vendor: Dell Inc.

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


** Tags: amd64 apport-bug lunar

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

Title:
  HDMI sound not working

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Running Ubuntu 23.04 with all the latest patches on Dell XPS 15 9510/Nvidia 
3050Ti via Thunderbolt 4 cable attached to a DELL WB22TB4 dockingstation via 
Displayport 2.0 cable to an Asus 4K monitor with an audio out to a surround 
set. 
  The sound via HDMI was working great when running 22.10, but works rarely on 
23.04 (I haven't figured out which set-up it always does work). nVidia driver = 
525.105.17

  More questions on ton.hofh...@canonical.com or via MM @ton211

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu7
  ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
  Uname: Linux 6.2.0-20-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ton5180 F wireplumber
   /dev/snd/controlC1:  ton5180 F wireplumber
   /dev/snd/pcmC1D0c:   ton5176 F...m pipewire
   /dev/snd/seq:ton5176 F pipewire
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Fri May 12 16:06:40 2023
  InstallationDate: Installed on 2023-02-02 (98 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/10/2023
  dmi.bios.release: 1.19
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.19.0
  dmi.board.name: 01V4T3
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.19.0:bd03/10/2023:br1.19:svnDellInc.:pnXPS159510:pvr:rvnDellInc.:rn01V4T3:rvrA00:cvnDellInc.:ct10:cvr:sku0A61:
  dmi.product.family: XPS
  dmi.product.name: XPS 15 9510
  dmi.product.sku: 0A61
  dmi.sys.vendor: Dell Inc.

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


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

[Desktop-packages] [Bug 2013128] Re: mesa: set info.separate_shader for ARB programs

it got dropped from 23.0 because:

"Causes virgl regressions, probably needs a groundwork patch in virgl"

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

Title:
  mesa: set info.separate_shader for ARB programs

Status in mesa package in Ubuntu:
  In Progress
Status in mesa source package in Jammy:
  In Progress
Status in mesa source package in Kinetic:
  Won't Fix
Status in mesa source package in Lunar:
  Triaged
Status in mesa source package in Mantic:
  In Progress

Bug description:
  [Impact]
  There's a shader bug in 22.2.x, fixed upstream in commit

  
https://gitlab.freedesktop.org/mesa/mesa/-/commit/7e68cf91d74e6bd9a88c2b52417451d9afec4782

  but since 22.2.x is already EOL, we need to backport it.

  [Test case]

  Install update, check that the application from the submitter works.

  
  [Where things could go wrong]
  This is a oneliner that flips a bool, but it's hard to imagine use-cases 
which would expect the old value.

  
  --

  
  I have a bug that occurs in Ubuntu 22.04's most up to date libmesa related 
packages (=22.2.5-0ubuntu0.1~22.04.1) that was not there in =22.0.1-1ubuntu2. 
It has since been solved in mesa's repo and pulled into debian's repo. I do not 
know the proper way to request an updated version be made for Ubuntu. I've 
manually installed many different versions of libmesa to test on my own that it 
was working in an older version, is broken in this update, and was fixed again 
in 22.3.4 and 22.3.5.

  The one-line fix is implemented here in libmesa's repo:
  
https://gitlab.freedesktop.org/mesa/mesa/-/commit/7e68cf91d74e6bd9a88c2b52417451d9afec4782

  Unfortunately I'm not using libmesa directly. I'm programming an
  application using fox-toolkit which interfaces with libmesa behind the
  scenes for me. I reported my issue to them first, and they stated it
  appears to be in the mesa library, which is what ultimately led me
  down the path to their repo, debian's repo, and here. Please let me
  know if I'm in the right spot, and, if so, what my next step is to
  properly report this.

  --

  Feature Request: Upgrade mesa libraries to apply upstream bugfix to a
  bug introduced in 22.2.5-0ubuntu0.1~22.04.1.

  I was directed to report this bug via my question at
  answers.launchpad.net/ubuntu:
  https://answers.launchpad.net/ubuntu/+question/705988

  Please let me know if you need further information.  Thanks!

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

   > apt-cache policy libglx-mesa0
  libglx-mesa0:
    Installed: 22.2.5-0ubuntu0.1~22.04.1
    Candidate: 22.2.5-0ubuntu0.1~22.04.1
    Version table:
   *** 22.2.5-0ubuntu0.1~22.04.1 500
  500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   22.0.1-1ubuntu2 500
  500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: libglx-mesa0 22.2.5-0ubuntu0.1~22.04.1
  ProcVersionSignature: Ubuntu 5.19.0-35.36~22.04.1-generic 5.19.17
  Uname: Linux 5.19.0-35-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: i3
  Date: Tue Mar 28 15:30:59 2023
  InstallationDate: Installed on 2022-04-28 (334 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: mesa
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.default.apport: [modified]
  mtime.conffile..etc.default.apport: 2022-04-29T14:47:14.568862

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


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

[Desktop-packages] [Bug 2019200] Re: fullscreen unredirection broken in gnome 44

2023-05-12 Thread 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 Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/2019200

Title:
  fullscreen unredirection broken in gnome 44

Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  Gnome broke fullscreen unredir in mutter 12
  resulting in serious performance regressions
  shown in : https://www.phoronix.com/review/ubuntu-2304-laptops/2

  this MR fixes it
  https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2941

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


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

[Desktop-packages] [Bug 2013128] Re: mesa: set info.separate_shader for ARB programs

seems that this commit never got applied to 23.0.x while it did get in
22.3.x...

** Also affects: mesa (Ubuntu Mantic)
   Importance: Undecided
   Status: Fix Released

** Also affects: mesa (Ubuntu Lunar)
   Importance: Undecided
   Status: New

** Changed in: mesa (Ubuntu Mantic)
   Status: Fix Released => In Progress

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

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

Title:
  mesa: set info.separate_shader for ARB programs

Status in mesa package in Ubuntu:
  In Progress
Status in mesa source package in Jammy:
  In Progress
Status in mesa source package in Kinetic:
  Won't Fix
Status in mesa source package in Lunar:
  Triaged
Status in mesa source package in Mantic:
  In Progress

Bug description:
  [Impact]
  There's a shader bug in 22.2.x, fixed upstream in commit

  
https://gitlab.freedesktop.org/mesa/mesa/-/commit/7e68cf91d74e6bd9a88c2b52417451d9afec4782

  but since 22.2.x is already EOL, we need to backport it.

  [Test case]

  Install update, check that the application from the submitter works.

  
  [Where things could go wrong]
  This is a oneliner that flips a bool, but it's hard to imagine use-cases 
which would expect the old value.

  
  --

  
  I have a bug that occurs in Ubuntu 22.04's most up to date libmesa related 
packages (=22.2.5-0ubuntu0.1~22.04.1) that was not there in =22.0.1-1ubuntu2. 
It has since been solved in mesa's repo and pulled into debian's repo. I do not 
know the proper way to request an updated version be made for Ubuntu. I've 
manually installed many different versions of libmesa to test on my own that it 
was working in an older version, is broken in this update, and was fixed again 
in 22.3.4 and 22.3.5.

  The one-line fix is implemented here in libmesa's repo:
  
https://gitlab.freedesktop.org/mesa/mesa/-/commit/7e68cf91d74e6bd9a88c2b52417451d9afec4782

  Unfortunately I'm not using libmesa directly. I'm programming an
  application using fox-toolkit which interfaces with libmesa behind the
  scenes for me. I reported my issue to them first, and they stated it
  appears to be in the mesa library, which is what ultimately led me
  down the path to their repo, debian's repo, and here. Please let me
  know if I'm in the right spot, and, if so, what my next step is to
  properly report this.

  --

  Feature Request: Upgrade mesa libraries to apply upstream bugfix to a
  bug introduced in 22.2.5-0ubuntu0.1~22.04.1.

  I was directed to report this bug via my question at
  answers.launchpad.net/ubuntu:
  https://answers.launchpad.net/ubuntu/+question/705988

  Please let me know if you need further information.  Thanks!

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

   > apt-cache policy libglx-mesa0
  libglx-mesa0:
    Installed: 22.2.5-0ubuntu0.1~22.04.1
    Candidate: 22.2.5-0ubuntu0.1~22.04.1
    Version table:
   *** 22.2.5-0ubuntu0.1~22.04.1 500
  500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   22.0.1-1ubuntu2 500
  500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: libglx-mesa0 22.2.5-0ubuntu0.1~22.04.1
  ProcVersionSignature: Ubuntu 5.19.0-35.36~22.04.1-generic 5.19.17
  Uname: Linux 5.19.0-35-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: i3
  Date: Tue Mar 28 15:30:59 2023
  InstallationDate: Installed on 2022-04-28 (334 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: mesa
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.default.apport: [modified]
  mtime.conffile..etc.default.apport: 2022-04-29T14:47:14.568862

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


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

[Desktop-packages] [Bug 1995320] Re: [amdgpu] intermittent green static

2023-05-12 Thread Kai Groner

** Tags removed: kinetic
** Tags added: lunar

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

Title:
  [amdgpu] intermittent green static

Status in linux package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  New

Bug description:
  After upgrading from 22.04 to 22.10 I've been seeing some display
  glitches.

  - green static appears, usually when scrolling, regular sized green blocks, 
like giant pixels
  - firefox not refreshing when full screen video plays (separate windows, 
separate screens)

  I would guess I probably have the wrong package here, but there's no
  way for me to tell if it's mesa, the kernel, gnome-shell, or something
  else.

  Radeon 6700XT
  Dual displays
  Wayland

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: gnome-shell 43.0-1ubuntu2
  ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7
  Uname: Linux 5.19.0-23-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct 31 21:46:03 2022
  DisplayManager: gdm3
  InstallationDate: Installed on 2019-06-18 (1231 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  ProcEnviron:
   TERM=tmux-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 43.0-1ubuntu4
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to kinetic on 2022-10-30 (1 days ago)
  --- 
  ProblemType: Bug
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  CRDA: N/A
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.10
  InstallationDate: Installed on 2019-06-18 (1232 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  ProcEnviron:
   TERM=tmux-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-23-generic 
root=/dev/mapper/infodata-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7
  RelatedPackageVersions:
   linux-restricted-modules-5.19.0-23-generic N/A
   linux-backports-modules-5.19.0-23-generic  N/A
   linux-firmware 20220923.gitf09bebf3-0ubuntu1
  RfKill:
   
  Tags:  kinetic wayland-session
  Uname: Linux 5.19.0-23-generic x86_64
  UpgradeStatus: Upgraded to kinetic on 2022-10-30 (1 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo wireshark
  _MarkForUpload: True
  dmi.bios.date: 11/27/2019
  dmi.bios.release: 5.14
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P2.90
  dmi.board.name: B450M Steel Legend
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP2.90:bd11/27/2019:br5.14:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB450MSteelLegend:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

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


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

[Desktop-packages] [Bug 1965208] Re: Ubuntu dock is visible too early during the login animation

** Description changed:

+ [ Impact ]
+ 
  Ubuntu dock is visible too early during the login animation: It appears
  immediately, disappears, then appears again.
  
+ [ Test case ]
+ 
+ Run:
+ 
+ env GNOME_SHELL_SESSION_MODE='ubuntu' GNOME_SHELL_SLOWDOWN_FACTOR=3 \
+   dbus-run-session gnome-shell --nested --wayland --unsafe-mode
+ 
+ Observe that the dock should be hidden while the startup animation
+ happens, and doesn't hide and snow again
+ 
+ [ Regression potential ]
+ 
+ Dock is never shown or animation is not properly executed.
+ 
+ ---
+ 
  In jammy this problem only occurred in Xorg sessions, but in kinetic it
  now occurs in Wayland sessions.

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

Title:
  Ubuntu dock is visible too early during the login animation

Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  Fix Released
Status in gnome-shell-extension-ubuntu-dock source package in Jammy:
  Fix Committed

Bug description:
  [ Impact ]

  Ubuntu dock is visible too early during the login animation: It
  appears immediately, disappears, then appears again.

  [ Test case ]

  Run:

  env GNOME_SHELL_SESSION_MODE='ubuntu' GNOME_SHELL_SLOWDOWN_FACTOR=3 \
dbus-run-session gnome-shell --nested --wayland --unsafe-mode

  Observe that the dock should be hidden while the startup animation
  happens, and doesn't hide and snow again

  [ Regression potential ]

  Dock is never shown or animation is not properly executed.

  ---

  In jammy this problem only occurred in Xorg sessions, but in kinetic
  it now occurs in Wayland sessions.

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


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

[Desktop-packages] [Bug 1979096] Re: gnome-shell search can't launch apps if dock auto-hide is enabled

** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu Jammy)
 Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0)

** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu Jammy)
   Importance: Undecided => Medium

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

Title:
  gnome-shell search can't launch apps if dock auto-hide is enabled

Status in Dash to dock:
  Fix Released
Status in gnome-shell package in Ubuntu:
  Triaged
Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  Fix Released
Status in gnome-shell-extension-ubuntu-dock source package in Jammy:
  In Progress

Bug description:
  [ Impact ]

  Search

  [ Test case ]

  1. From settings:
a. Enable non-fractional scaling of 200%
b. Show the dock on the left side
c. Enable dock auto-hide

  2. Hit Super key and search for any result
  3. Hitting Enter key or clicking on an application icon should launch it

  [ Regression potential ]

  App grid has wrong sizes or not properly visible

  ---

  
  The problem happens, when I enable the dock to hide automatically. With this 
enabled, it is not possible to run the programs through the search. But when 
disabled, it is possible to search and run the programs. Here's the video of 
the problem.

  ProblemType: BugDistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-39.42-generic 5.15.35
  Uname: Linux 5.15.0-39-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permissão negada: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jun 17 18:21:45 2022
  DistUpgraded: 2022-04-21 13:52:59,951 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
  DistroCodename: jammy
  DistroVariant: ubuntu
  DkmsStatus:
   v4l2loopback/0.12.5, 5.15.0-37-generic, x86_64: installed
   v4l2loopback/0.12.5, 5.15.0-39-generic, x86_64: installed
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] RS780L [Radeon 3000] [1002:9616] 
(prog-if 00 [VGA controller])
     Subsystem: ASUSTeK Computer Inc. RS780L [Radeon 3000] [1043:8388]
  InstallationDate: Installed on 2021-04-15 (428 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-39-generic 
root=UUID=7e3c483e-6d02-4fc2-be0e-48207eb147eb ro quiet splash 
vt.handoff=7SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to jammy on 2022-04-21 (57 days ago)
  dmi.bios.date: 03/04/2017
  dmi.bios.release: 8.15
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1201
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: M5A78L-M LX/BR
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1201:bd03/04/2017:br8.15:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM5A78L-MLX/BR:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:skuToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.110-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 22.0.1-1ubuntu2.1
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

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


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

[Desktop-packages] [Bug 2018600] Re: [SRU] libreoffice 7.4.7 for kinetic

Hello Rico, or anyone else affected,

Accepted libreoffice into kinetic-proposed. The package will build now
and be available at
https://launchpad.net/ubuntu/+source/libreoffice/1:7.4.7-0ubuntu0.22.10.1
in a few hours, and then in the -proposed repository.

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

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

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

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

** Changed in: libreoffice (Ubuntu Kinetic)
   Status: In Progress => Fix Committed

** Tags added: verification-needed verification-needed-kinetic

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

Title:
  [SRU] libreoffice 7.4.7 for kinetic

Status in libreoffice package in Ubuntu:
  Fix Released
Status in libreoffice source package in Kinetic:
  Fix Committed

Bug description:
  [Impact]

   * LibreOffice 7.4.7 is in its seventh bugfix release of the 7.4 line:
   https://wiki.documentfoundation.org/ReleasePlan/7.4#7.4.7_release

   * Version 7.4.6 is currently released in kinetic. For a list of fixed bugs 
compared to 7.4.6 see the list of bugs fixed in the release candidates of 7.4.7 
(that's a total of 73 bugs):
   https://wiki.documentfoundation.org/Releases/7.4.7/RC1#List_of_fixed_bugs
   https://wiki.documentfoundation.org/Releases/7.4.7/RC2#List_of_fixed_bugs

   * Given the nature of the project, the complexity of the codebase and
  the high level of quality assurance upstream, it is preferable to SRU
  a minor release rather than cherry-pick selected bug fixes.

  [Testing]

   * Upstream testing. Bugs fixed upstream typically include
  unit/regression tests, and the release itself is extensively exercised
  (both in an automated manner and manually).

    * A recent set of upstream's automated jenkins testing can be found here:
  https://ci.libreoffice.org/job/gerrit_74/1827/

    * More information about the upstream QA testing can be found here:
  * Automated tests
    https://wiki.documentfoundation.org/QA/Testing/Automated_Tests
  * Automated UI tests
    https://wiki.documentfoundation.org/Development/UITests
  * Regression tests
    https://wiki.documentfoundation.org/QA/Testing/Regression_Tests
  * Feature tests
    https://wiki.documentfoundation.org/QA/Testing/Feature_Tests

   * Launchpad testing. The libreoffice packages include autopkgtests that were 
run and verified as passing.
  Tested build can be found at 
https://launchpad.net/~ricotz/+archive/ubuntu/ppa/+sourcepub/14734942/+listing-archive-extra
  * [amd64] 
https://autopkgtest.ubuntu.com/results/autopkgtest-kinetic-ricotz-ppa/kinetic/amd64/libr/libreoffice/20230504_151518_a9360@/log.gz
  * [arm64] 
https://autopkgtest.ubuntu.com/results/autopkgtest-kinetic-ricotz-ppa/kinetic/arm64/libr/libreoffice/20230504_200542_1dfdd@/log.gz
  * [armhf] 
https://autopkgtest.ubuntu.com/results/autopkgtest-kinetic-ricotz-ppa/kinetic/armhf/libr/libreoffice/20230505_142551_a6b85@/log.gz
  * [ppc64el] 
https://autopkgtest.ubuntu.com/results/autopkgtest-kinetic-ricotz-ppa/kinetic/ppc64el/libr/libreoffice/20230504_161525_fdb04@/log.gz
  * [s390x] 
https://autopkgtest.ubuntu.com/results/autopkgtest-kinetic-ricotz-ppa/kinetic/s390x/libr/libreoffice/20230506_054745_25b3f@/log.gz
   * General smoke testing of all the applications in the office suite were 
carried out by going through the manual testplan as documented by: 
https://wiki.ubuntu.com/Process/Merges/TestPlans/libreoffice

  [Regression Potential]

   * A minor release with a total of 73 bug fixes always carries the
  potential for introducing regressions, even though it is a bugfix-only
  release, meaning that no new features were added, and no existing
  features were removed.

   * A combination of autopkgtests and careful smoke testing as
  described above should provide reasonable confidence that no
  regressions sneaked in.

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

[Desktop-packages] [Bug 2017976] Re: [SRU] libreoffice 7.5.3 for lunar

Hello Rico, or anyone else affected,

Accepted libreoffice into lunar-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/libreoffice/4:7.5.3-0ubuntu0.23.04.1
in a few hours, and then in the -proposed repository.

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

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

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

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

** Changed in: libreoffice (Ubuntu Lunar)
   Status: In Progress => Fix Committed

** Tags added: verification-needed verification-needed-lunar

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

Title:
  [SRU] libreoffice 7.5.3 for lunar

Status in libreoffice package in Ubuntu:
  Fix Committed
Status in libreoffice source package in Lunar:
  Fix Committed
Status in libreoffice source package in Mantic:
  Fix Committed

Bug description:
  [Impact]

   * LibreOffice 7.5.3 is in its third bugfix release of the 7.5 line:
   https://wiki.documentfoundation.org/ReleasePlan/7.5#7.5.3_release

   * Version 7.5.2 is currently released in lunar. For a list of fixed bugs 
compared to 7.5.2 see the list of bugs fixed in the release candidates of 7.5.3 
(that's a total of 119 bugs):
   https://wiki.documentfoundation.org/Releases/7.5.3/RC1#List_of_fixed_bugs
   https://wiki.documentfoundation.org/Releases/7.5.3/RC2#List_of_fixed_bugs

   * Given the nature of the project, the complexity of the codebase and
  the high level of quality assurance upstream, it is preferable to SRU
  a minor release rather than cherry-pick selected bug fixes.

  [Testing]

   * Upstream testing. Bugs fixed upstream typically include
  unit/regression tests, and the release itself is extensively exercised
  (both in an automated manner and manually).

    * A recent set of upstream's automated jenkins testing can be found here:
  https://ci.libreoffice.org/job/gerrit_75/1277/

    * More information about the upstream QA testing can be found here:
  * Automated tests
    https://wiki.documentfoundation.org/QA/Testing/Automated_Tests
  * Automated UI tests
    https://wiki.documentfoundation.org/Development/UITests
  * Regression tests
    https://wiki.documentfoundation.org/QA/Testing/Regression_Tests
  * Feature tests
    https://wiki.documentfoundation.org/QA/Testing/Feature_Tests

   * Launchpad testing. The libreoffice packages include autopkgtests that were 
run and verified as passing.
  Tested build can be found at 
https://launchpad.net/~libreoffice/+archive/ubuntu/libreoffice-prereleases/+sourcepub/14726196/+listing-archive-extra
  * [amd64] 
https://autopkgtest.ubuntu.com/results/autopkgtest-lunar-libreoffice-libreoffice-prereleases/lunar/amd64/libr/libreoffice/20230428_091914_c1745@/log.gz
  * [arm64] 
https://autopkgtest.ubuntu.com/results/autopkgtest-lunar-libreoffice-libreoffice-prereleases/lunar/arm64/libr/libreoffice/20230428_145808_db4a8@/log.gz
  * [armhf] 
https://autopkgtest.ubuntu.com/results/autopkgtest-lunar-libreoffice-libreoffice-prereleases/lunar/armhf/libr/libreoffice/20230428_112634_ff879@/log.gz
  * [ppc64el] 
https://autopkgtest.ubuntu.com/results/autopkgtest-lunar-libreoffice-libreoffice-prereleases/lunar/ppc64el/libr/libreoffice/20230428_092959_ffca8@/log.gz
  * [riscv64] not available
  * [s390x] 
https://autopkgtest.ubuntu.com/results/autopkgtest-lunar-libreoffice-libreoffice-prereleases/lunar/s390x/libr/libreoffice/20230428_214513_ee240@/log.gz
   * General smoke testing of all the applications in the office suite were 
carried out by going through the manual testplan as documented by: 
https://wiki.ubuntu.com/Process/Merges/TestPlans/libreoffice

  [Regression Potential]

   * A minor release with a total of 119 bug fixes always carries the
  potential for introducing regressions, even though it is a bugfix-only
  release, meaning that no new features were added, and no existing
  features were removed.

   * A combination of autopkgtests and careful smoke t

[Desktop-packages] [Bug 1991022] Debdiff

2023-05-12 Thread Nathan Teodosio

** Attachment added: "speechd.debdiff"
   
https://bugs.launchpad.net/bugs/1991022/+attachment/5672708/+files/speechd.debdiff

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

Title:
  Service activation via Systemd socket

Status in speech-dispatcher package in Ubuntu:
  In Progress

Bug description:
  [Description]

  Systemd socket activation for Speech Dispatcher.

    - Creates the speech-dispatcher.socket;
    - Modifies the server so that it can detect it was automatically launched 
by that socket activation; and
    - Modifies the Autotools files accordingly.

  [Rationale]

  It's relevance is described in [1], of which I quote the essential
  parts [my notes in brackets]:

  > Sandboxed applications [snaps] that use Speech Dispatcher currently bundle 
it inside of the sandbox, so that each application has its own "private" 
instance of Speech Dispatcher running. This works more or less, but it has the 
downside that speech dispatcher cannot coordinate simultaneous messages from 
multiple apps. When multiple sandboxed apps use Speech Dispatcher at the same 
time, the text reading overlaps.
  >
  > In order to solve this issue, I would really like to give sandboxed apps 
access to the Speech Dispatcher instance of the host.

  And then,

  > The only issue I see is having it auto launch. I think it would
  probably be a good step forward for speech-dispatcher to be auto
  launched by a systemd socket like other daemons already do on demand.
  That way the host speech-dispatcher with it's configuration would be
  used by all snaps,

  [Additional information]

  The changes are already merged upstream[2], but still not released.

  I have built and installed the package in Mantic and verified that
  running spd-say from inside a snap causes the host's dispatcher to
  spawn and emit sound — see 'Reproduction case' for more details.

  The installed socket needs to be started manually to function
  correctly, or else the system needs to be rebooted.

  [Reproduction case]

  Install the proposed speech-dispatcher from the PPA[3] and the snap[4]
  with spd-say. Then,

systemctl start --user speech-dispatcher.socket
snap run --shell geheim
$ XDG_RUNTIME_DIR=/run/user/1000 spd-say hi

  [1] https://github.com/brailcom/speechd/issues/335
  [2] https://github.com/brailcom/speechd/pull/763
  [3] https://launchpad.net/~nteodosio/+archive/ubuntu/rebuilds/+build/26035882
  [4] https://launchpad.net/~nteodosio/+snap/test-speechd/+build/2103550

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/speech-dispatcher/+bug/1991022/+subscriptions


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

[Desktop-packages] [Bug 1991022] Re: [FFe] Socket activation

2023-05-12 Thread Nathan Teodosio

** Description changed:

  [Description]
  
  Systemd socket activation for Speech Dispatcher.
  
    - Creates the speech-dispatcher.socket;
    - Modifies the server so that it can detect it was automatically launched 
by that socket activation; and
    - Modifies the Autotools files accordingly.
  
  [Rationale]
  
  It's relevance is described in [1], of which I quote the essential parts
  [my notes in brackets]:
  
  > Sandboxed applications [snaps] that use Speech Dispatcher currently bundle 
it inside of the sandbox, so that each application has its own "private" 
instance of Speech Dispatcher running. This works more or less, but it has the 
downside that speech dispatcher cannot coordinate simultaneous messages from 
multiple apps. When multiple sandboxed apps use Speech Dispatcher at the same 
time, the text reading overlaps.
  >
  > In order to solve this issue, I would really like to give sandboxed apps 
access to the Speech Dispatcher instance of the host.
  
  And then,
  
  > The only issue I see is having it auto launch. I think it would
  probably be a good step forward for speech-dispatcher to be auto
  launched by a systemd socket like other daemons already do on demand.
  That way the host speech-dispatcher with it's configuration would be
  used by all snaps,
  
  [Additional information]
  
  The changes are already merged upstream[2], but still not released.
  
- I have built and installed the package in Kinetic and verified that spd-
- say still causes the dispatcher spawn and emits sound. Upstream test can
- also confirm this.
+ I have built and installed the package in Mantic and verified that
+ running spd-say from inside a snap causes the host's dispatcher to spawn
+ and emit sound — see 'Reproduction case' for more details.
  
- [1]: https://github.com/brailcom/speechd/issues/335
- [2]: https://github.com/brailcom/speechd/pull/763
+ The installed socket needs to be started manually to function correctly,
+ or else the system needs to be rebooted.
+ 
+ [Reproduction case]
+ 
+ Install the proposed speech-dispatcher from the PPA[3] and the snap[4]
+ with spd-say. Then,
+ 
+   systemctl start --user speech-dispatcher.socket
+   snap run --shell geheim
+   $ XDG_RUNTIME_DIR=/run/user/1000 spd-say hi
+ 
+ [1] https://github.com/brailcom/speechd/issues/335
+ [2] https://github.com/brailcom/speechd/pull/763
+ [3] https://launchpad.net/~nteodosio/+archive/ubuntu/rebuilds/+build/26035882
+ [4] https://launchpad.net/~nteodosio/+snap/test-speechd/+build/2103550

** Changed in: speech-dispatcher (Ubuntu)
   Status: Fix Released => In Progress

** Summary changed:

- [FFe] Socket activation
+ Service activation via Systemd socket

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

Title:
  Service activation via Systemd socket

Status in speech-dispatcher package in Ubuntu:
  In Progress

Bug description:
  [Description]

  Systemd socket activation for Speech Dispatcher.

    - Creates the speech-dispatcher.socket;
    - Modifies the server so that it can detect it was automatically launched 
by that socket activation; and
    - Modifies the Autotools files accordingly.

  [Rationale]

  It's relevance is described in [1], of which I quote the essential
  parts [my notes in brackets]:

  > Sandboxed applications [snaps] that use Speech Dispatcher currently bundle 
it inside of the sandbox, so that each application has its own "private" 
instance of Speech Dispatcher running. This works more or less, but it has the 
downside that speech dispatcher cannot coordinate simultaneous messages from 
multiple apps. When multiple sandboxed apps use Speech Dispatcher at the same 
time, the text reading overlaps.
  >
  > In order to solve this issue, I would really like to give sandboxed apps 
access to the Speech Dispatcher instance of the host.

  And then,

  > The only issue I see is having it auto launch. I think it would
  probably be a good step forward for speech-dispatcher to be auto
  launched by a systemd socket like other daemons already do on demand.
  That way the host speech-dispatcher with it's configuration would be
  used by all snaps,

  [Additional information]

  The changes are already merged upstream[2], but still not released.

  I have built and installed the package in Mantic and verified that
  running spd-say from inside a snap causes the host's dispatcher to
  spawn and emit sound — see 'Reproduction case' for more details.

  The installed socket needs to be started manually to function
  correctly, or else the system needs to be rebooted.

  [Reproduction case]

  Install the proposed speech-dispatcher from the PPA[3] and the snap[4]
  with spd-say. Then,

systemctl start --user speech-dispatcher.socket
snap run --shell geheim
$ XDG_RUNTIME_DIR=/run/user/1000 spd-say hi

  [1] https://github.com/brailcom/speechd/issues/335
  [2] h

[Desktop-packages] [Bug 1997264] Re: Slow or Hanging GVFS mounts may lead the whole session to hang

** Also affects: gvfs (Ubuntu Jammy)
   Importance: Undecided
   Status: New

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

** Also affects: gnome-shell-extension-ubuntu-dock (Ubuntu Jammy)
   Importance: Undecided
   Status: New

** No longer affects: gnome-shell (Ubuntu Jammy)

** No longer affects: gvfs (Ubuntu Jammy)

** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu Jammy)
 Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0)

** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu Jammy)
   Importance: Undecided => High

** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu Jammy)
   Status: New => In Progress

** Description changed:

+ [ Impact ]
+ 
  Trying to query info from a mout point that is hanging may lead the
  whole shell to hang due to a sync call, that cannot be cancelled nor
  times out.
+ 
+ [ Test case ]
+ 
+ 1. Start a slow copy operation on file manager (good test case is using mpt 
protocol,
+and so, copying some big file to/from an android device) on  a mounted 
device that
+is visible in the launcher.
+ 2. Try to interact with the mounted launcher icon (right clicking it)
+ 3. The whole session should never hang
+ 
+ [ Regression potential ]
+ 
+ Mounted locations are not properly launched from dock

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

Title:
  Slow or Hanging GVFS mounts may lead the whole session to hang

Status in gnome-shell package in Ubuntu:
  Won't Fix
Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  Fix Released
Status in gvfs package in Ubuntu:
  Triaged
Status in gnome-shell-extension-ubuntu-dock source package in Jammy:
  In Progress

Bug description:
  [ Impact ]

  Trying to query info from a mout point that is hanging may lead the
  whole shell to hang due to a sync call, that cannot be cancelled nor
  times out.

  [ Test case ]

  1. Start a slow copy operation on file manager (good test case is using mpt 
protocol,
 and so, copying some big file to/from an android device) on  a mounted 
device that
 is visible in the launcher.
  2. Try to interact with the mounted launcher icon (right clicking it)
  3. The whole session should never hang

  [ Regression potential ]

  Mounted locations are not properly launched from dock

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


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

[Desktop-packages] [Bug 1971012] Re: Nautilus windows not respecting workspace isolation

** Description changed:

+ [ Impact ]
+ 
+ Workspace isolation is not respected by nautilus in dock
+ 
+ [ Test case ]
+ 
+ 1. From settings -> Multitasking:
+  - Enable "Include applications from the current workspace only"
+ 2. Open a Files window in a workspace
+ 3. Switch to another workspace
+ 4. File manager icon should be visible with no count
+ 5. Open a new file-manager instance (clicking on the dock icon)
+ 6. A icon dot should be visible
+ 7. Switching back to the initial workspace should show the icon dots
+respecting the number of icons
+ 
+ [ Regression potential ]
+ 
+ Wrong number of windows are shown on file-manager icons
+ 
+ 
+ ---
+ 
  In settings, under multitasking > application switching, setting
  "include applications from the current workspace only" is supposed to
  provide workspace isolation, making only apps in the current workspace
  show in the dock. For example, if I have 2 firefox windows in workspace
  1, and a terminal window in workspace 2, terminal should not show as
  open in the dock in workspace 1, and firefox should not show as open in
  the dock in workspace 2.
  
  Additionally, quitting all windows from right click in the dock should
  close only all windows of that app in the current workspace.
  
  This mostly works correctly, but for some reason some apps, including
  nautilus and software and updates, do not respect it. If you switch
  workspaces with them open, the new workspace shows them as having the
  same number of open windows as the previous workspace, even though no
  windows are open in that workspace. If you quit with right click from
  the dock, it sometimes quits all instances across all workspaces. If you
  open a separate window in the new workspace with right click on the
  dock, it then updates to the correct number, but the problem then
  returns on switching back to the previous workspace. If you open and
  close a window in the new workspace, then switch back to the old one, it
  is possible to get to a point where despite several windows of the app
  being open in that workspace, it shows as not open in the dock.
  
  The problem persists across different installs and machines
  
  To reproduce:
  Open ubuntu (a live version is fine). Turn on workspace isolation in 
settings. Pin nautilus to favorites so it shows in the dock. Open a window of 
nautilus, and a window of some other app (firefox works). Switch workspaces. 
Observe that an orange dot is still present under nautilus, and it still acts 
like it is open in the new workspace
  
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
- DisplayManager: gdm3
- DistroRelease: Ubuntu 22.04
+ DisplayManager: gdm3DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2020-04-25 (735 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: gnome-shell 42.0-2ubuntu1
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  RelatedPackageVersions: mutter-common 42.0-3ubuntu2
  Tags:  jammy
  Uname: Linux 5.15.0-27-generic x86_64
  UpgradeStatus: Upgraded to jammy on 2022-04-30 (1 days ago)
  UserGroups: adm cdrom dip lpadmin lxd nordvpn plugdev sambashare sudo 
wireshark
  _MarkForUpload: True

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

Title:
  Nautilus windows not respecting workspace isolation

Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  Fix Released
Status in gnome-shell-extension-ubuntu-dock source package in Jammy:
  In Progress

Bug description:
  [ Impact ]

  Workspace isolation is not respected by nautilus in dock

  [ Test case ]

  1. From settings -> Multitasking:
   - Enable "Include applications from the current workspace only"
  2. Open a Files window in a workspace
  3. Switch to another workspace
  4. File manager icon should be visible with no count
  5. Open a new file-manager instance (clicking on the dock icon)
  6. A icon dot should be visible
  7. Switching back to the initial workspace should show the icon dots
 respecting the number of icons

  [ Regression potential ]

  Wrong number of windows are shown on file-manager icons

  
  ---

  In settings, under multitasking > application switching, setting
  "include applications from the current workspace only" is supposed to
  provide workspace isolation, making only apps in the current workspace
  show in the dock. For example, if I have 2 firefox windows in
  workspace 1, and a terminal window in workspace 2, terminal should not
  show as open in the dock in workspace 1, and firefox should not show
  as

[Desktop-packages] [Bug 1971012] Re: Nautilus windows not respecting workspace isolation

** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu Jammy)
   Status: Triaged => In Progress

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

Title:
  Nautilus windows not respecting workspace isolation

Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  Fix Released
Status in gnome-shell-extension-ubuntu-dock source package in Jammy:
  In Progress

Bug description:
  [ Impact ]

  Workspace isolation is not respected by nautilus in dock

  [ Test case ]

  1. From settings -> Multitasking:
   - Enable "Include applications from the current workspace only"
  2. Open a Files window in a workspace
  3. Switch to another workspace
  4. File manager icon should be visible with no count
  5. Open a new file-manager instance (clicking on the dock icon)
  6. A icon dot should be visible
  7. Switching back to the initial workspace should show the icon dots
 respecting the number of icons

  [ Regression potential ]

  Wrong number of windows are shown on file-manager icons

  
  ---

  In settings, under multitasking > application switching, setting
  "include applications from the current workspace only" is supposed to
  provide workspace isolation, making only apps in the current workspace
  show in the dock. For example, if I have 2 firefox windows in
  workspace 1, and a terminal window in workspace 2, terminal should not
  show as open in the dock in workspace 1, and firefox should not show
  as open in the dock in workspace 2.

  Additionally, quitting all windows from right click in the dock should
  close only all windows of that app in the current workspace.

  This mostly works correctly, but for some reason some apps, including
  nautilus and software and updates, do not respect it. If you switch
  workspaces with them open, the new workspace shows them as having the
  same number of open windows as the previous workspace, even though no
  windows are open in that workspace. If you quit with right click from
  the dock, it sometimes quits all instances across all workspaces. If
  you open a separate window in the new workspace with right click on
  the dock, it then updates to the correct number, but the problem then
  returns on switching back to the previous workspace. If you open and
  close a window in the new workspace, then switch back to the old one,
  it is possible to get to a point where despite several windows of the
  app being open in that workspace, it shows as not open in the dock.

  The problem persists across different installs and machines

  To reproduce:
  Open ubuntu (a live version is fine). Turn on workspace isolation in 
settings. Pin nautilus to favorites so it shows in the dock. Open a window of 
nautilus, and a window of some other app (firefox works). Switch workspaces. 
Observe that an orange dot is still present under nautilus, and it still acts 
like it is open in the new workspace

  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2020-04-25 (735 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: gnome-shell 42.0-2ubuntu1
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  RelatedPackageVersions: mutter-common 42.0-3ubuntu2
  Tags:  jammy
  Uname: Linux 5.15.0-27-generic x86_64
  UpgradeStatus: Upgraded to jammy on 2022-04-30 (1 days ago)
  UserGroups: adm cdrom dip lpadmin lxd nordvpn plugdev sambashare sudo 
wireshark
  _MarkForUpload: True

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


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

[Desktop-packages] [Bug 1979096] Re: gnome-shell search can't launch apps if dock auto-hide is enabled

** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu Jammy)
   Status: Confirmed => In Progress

** Description changed:

- The problem happens, when I enable the dock to hide automatically. With
- this enabled, it is not possible to run the programs through the search.
- But when disabled, it is possible to search and run the programs. Here's
- the video of the problem.
+ [ Impact ]
  
- ProblemType: Bug
- DistroRelease: Ubuntu 22.04
+ Search
+ 
+ [ Test case ]
+ 
+ 1. From settings:
+   a. Enable non-fractional scaling of 200%
+   b. Show the dock on the left side
+   c. Enable dock auto-hide
+ 
+ 2. Hit Super key and search for any result
+ 3. Hitting Enter key or clicking on an application icon should launch it
+ 
+ [ Regression potential ]
+ 
+ App grid has wrong sizes or not properly visible
+ 
+ ---
+ 
+ 
+ The problem happens, when I enable the dock to hide automatically. With this 
enabled, it is not possible to run the programs through the search. But when 
disabled, it is possible to search and run the programs. Here's the video of 
the problem.
+ 
+ ProblemType: BugDistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-39.42-generic 5.15.35
  Uname: Linux 5.15.0-39-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permissão negada: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jun 17 18:21:45 2022
  DistUpgraded: 2022-04-21 13:52:59,951 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
  DistroCodename: jammy
  DistroVariant: ubuntu
  DkmsStatus:
-  v4l2loopback/0.12.5, 5.15.0-37-generic, x86_64: installed
-  v4l2loopback/0.12.5, 5.15.0-39-generic, x86_64: installed
+  v4l2loopback/0.12.5, 5.15.0-37-generic, x86_64: installed
+  v4l2loopback/0.12.5, 5.15.0-39-generic, x86_64: installed
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
-  Advanced Micro Devices, Inc. [AMD/ATI] RS780L [Radeon 3000] [1002:9616] 
(prog-if 00 [VGA controller])
-Subsystem: ASUSTeK Computer Inc. RS780L [Radeon 3000] [1043:8388]
+  Advanced Micro Devices, Inc. [AMD/ATI] RS780L [Radeon 3000] [1002:9616] 
(prog-if 00 [VGA controller])
+    Subsystem: ASUSTeK Computer Inc. RS780L [Radeon 3000] [1043:8388]
  InstallationDate: Installed on 2021-04-15 (428 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  MachineType: System manufacturer System Product Name
- ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-39-generic 
root=UUID=7e3c483e-6d02-4fc2-be0e-48207eb147eb ro quiet splash vt.handoff=7
- SourcePackage: xorg
+ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-39-generic 
root=UUID=7e3c483e-6d02-4fc2-be0e-48207eb147eb ro quiet splash 
vt.handoff=7SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to jammy on 2022-04-21 (57 days ago)
  dmi.bios.date: 03/04/2017
  dmi.bios.release: 8.15
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1201
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: M5A78L-M LX/BR
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1201:bd03/04/2017:br8.15:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM5A78L-MLX/BR:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:skuToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.110-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 22.0.1-1ubuntu2.1
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

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

Title:
  gnome-shell search can't launch apps if dock auto-hide is enabled

Status in Dash to dock:
  Fix Released
Status in gnome-shell package in Ubuntu:
  Triaged
Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  Fix Released
Status in gnome-shell-extension-ubuntu-dock source package in Jammy:
  In Progress

Bug description:
  [ Impact ]

  Search

  [ Test case ]

[Desktop-packages] [Bug 1987976] Re: firefox black window on wayland

Hello Michelet, or anyone else affected,

Accepted mutter into lunar-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/mutter/44.0-2ubuntu4.23.04.1 in a
few hours, and then in the -proposed repository.

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

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

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

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

** Changed in: mutter (Ubuntu Lunar)
   Status: In Progress => Fix Committed

** Tags added: verification-needed verification-needed-lunar

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

Title:
  firefox black window on wayland

Status in Mozilla Firefox:
  Unknown
Status in Mutter:
  New
Status in Release Notes for Ubuntu:
  Fix Released
Status in firefox package in Ubuntu:
  Invalid
Status in mutter package in Ubuntu:
  Fix Released
Status in mutter source package in Lunar:
  Fix Committed

Bug description:
  [ Impact ]

  On some systems, when you open the Firefox snap right after having
  logged in into an Ubuntu on Wayland session, you are met by a black
  window. This happens because the FF snap is run under Xwayland, and
  Xwayland may not be enabled early enough to handle the start of the
  application properly.

  You can easily reproduce the issue in a Wayland session:

  * Close Firefox
  * Run the command "killall Xwayland" in terminal
  * Open Firefox

  An upstream mutter change addresses this issue, and the proposed lunar
  change cherry picks that upstream change as a patch.

  [ Test Plan ]

  On an updated Ubuntu 23.04:

  * Install the mutter related binaries from lunar-proposed

  * Reboot and log in to an Ubuntu on Wayland session

  * Run the command "killall Xwayland"

  * Open the Firefox snap, and find that it starts normally

  [ Where problems could occur ]

  This is the upstream merge request in question:

  https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2970

  The changes (except for the test related ones) are small, and
  specifically intended to address issues like the one reported in this
  bug. There are also reviews by a couple of experienced GNOME devs.

  So even if the proposed change is not well tested yet, it seems to me
  that the risk for adverse side effects is limited.

  [ Original description ]

  nicolas@nicolas-fixe:~$ lsb_release -rd
  Description:  Ubuntu 22.04.1 LTS
  Release:  22.04

  nicolas@nicolas-fixe:~$ apt-cache policy firefox
  firefox:
    Installé : 1:1snap1-0ubuntu2
    Candidat : 1:1snap1-0ubuntu2
   Table de version :
   *** 1:1snap1-0ubuntu2 500
  500 http://fr.archive.ubuntu.com/ubuntu jammy/main amd64 Packages
  100 /var/lib/dpkg/status

  When I boot Ubuntu and start Firefox, the Firefox's window is totally
  black. See attachment.

  I am at your disposal to answer any question you have.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: firefox 1:1snap1-0ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39
  Uname: Linux 5.15.0-46-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Aug 28 12:42:29 2022
  InstallationDate: Installed on 2022-08-25 (2 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  Snap.Changes: aucun changement trouvé
  SourcePackage: firefox
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Desktop-packages] [Bug 2019045] Re: [snap] New Ubuntu font with normal weight displayed as bold in Google Docs in Chromium after upgrading to Lunar

2023-05-12 Thread Nathan Teodosio

** Description changed:

  I am experiencing a rendering regression after upgrading from Kinetic to 
Lunar.
  Google Docs using the Ubuntu font family are displayed incorrectly in 
Chromium: the normal weight font is rendered identically to the bold weight 
one, instead of being thicker than light and thinner than medium.
  
  Printing is also affected, unless I use Google Docs' download to PDF
  function, although that probably triggers a server-side rendering.
  
- This issue does not occur in Firefox.
+ This issue does not occur in Firefox or Google Chrome.
  
  One thing that may be relevant: if I force-refresh my test Google Doc I
  see all four Ubuntu font lines initially being rendered as bold. The
  light and medium lines are then re-rendered with the correct weight.
  It's as if bold was the default weight and the normal variant
  disappeared.
  
  As far as I can tell I was already running Chromium 112.0.5615.49 in
  Kinetic, and with Chromium being a snap I don't quite understand why the
  Ubuntu series would matter.
  
  I have also tried version 114.0.5735.16 (in latest/beta at the moment);
  the symptoms are identical.
  
  The attachments show the rendering error.

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

Title:
  [snap] New Ubuntu font with normal weight displayed as bold in Google
  Docs in Chromium after upgrading to Lunar

Status in chromium-browser package in Ubuntu:
  Triaged
Status in fonts-ubuntu package in Ubuntu:
  Confirmed

Bug description:
  I am experiencing a rendering regression after upgrading from Kinetic to 
Lunar.
  Google Docs using the Ubuntu font family are displayed incorrectly in 
Chromium: the normal weight font is rendered identically to the bold weight 
one, instead of being thicker than light and thinner than medium.

  Printing is also affected, unless I use Google Docs' download to PDF
  function, although that probably triggers a server-side rendering.

  This issue does not occur in Firefox or Google Chrome.

  One thing that may be relevant: if I force-refresh my test Google Doc
  I see all four Ubuntu font lines initially being rendered as bold. The
  light and medium lines are then re-rendered with the correct weight.
  It's as if bold was the default weight and the normal variant
  disappeared.

  As far as I can tell I was already running Chromium 112.0.5615.49 in
  Kinetic, and with Chromium being a snap I don't quite understand why
  the Ubuntu series would matter.

  I have also tried version 114.0.5735.16 (in latest/beta at the
  moment); the symptoms are identical.

  The attachments show the rendering error.

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


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

[Desktop-packages] [Bug 2018316] Re: wireplumber sometime segfault on bluez devices disconnect

Hello Sebastien, or anyone else affected,

Accepted pipewire into lunar-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/pipewire/0.3.65-3ubuntu1 in a few
hours, and then in the -proposed repository.

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

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

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

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

** Also affects: pipewire (Ubuntu Jammy)
   Importance: Undecided
   Status: New

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

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

** Tags added: verification-needed verification-needed-lunar

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

Title:
  wireplumber sometime segfault on bluez devices disconnect

Status in pipewire package in Ubuntu:
  Fix Released
Status in pipewire source package in Jammy:
  New
Status in pipewire source package in Lunar:
  Fix Committed

Bug description:
  * Impact

  wireplumber sometime segfault on bluez devices disconnect leading to
  non working pipewire audio

  * Test case

  Connect and disconnect bluetooth audio devices and ensure
  wireplumber/pipewire-pulse don't hit an error and sound keeps working
  in the desktop (sound settings testsound, rhythmbox, firefox playing
  video)

  and check that error reports stop on 
  https://errors.ubuntu.com/problem/a1b673a5eb264d829f8851e55351dec64a517f53

  * Regression potential

  The change is in the pipewire bluez plugin so the testing should focus
  on bluetooth audio devices

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


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

[Desktop-packages] [Bug 1992843] Re: Windows previewes are not scaled in HiDPI monitors

** Description changed:

[ Impact ]

Menu previews in the dock are not scaled when using hi-dpi integer
scaling (no fractional scaling)

[ Test Case ]

- 1. Scale your display to 2x or any other integer value
+ 1. Scale your display to 2x or any other integer value (disabling fractional
scaling)
2. Ensure that the fractional scaling is disabled (may require logout/login)
3. Open one or more windows
4. Right-click to see the windows previews
5. The scaled windows should have a size that is scaled and proportional to
scaling

[ Regression potential ]

It's not possible to see / use all the windows previews, or they have
wrong aspect ratio.

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

Title:
Windows previewes are not scaled in HiDPI monitors

Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
Fix Released
Status in gnome-shell-extension-ubuntu-dock source package in Jammy:
In Progress

Bug description:
[ Impact ]

Menu previews in the dock are not scaled when using hi-dpi integer
scaling (no fractional scaling)

[ Test Case ]

1. Scale your display to 2x or any other integer value (disabling fractional
scaling)
2. Ensure that the fractional scaling is disabled (may require logout/login)
3. Open one or more windows
4. Right-click to see the windows previews
5. The scaled windows should have a size that is scaled and proportional to
scaling

[ Regression potential ]

It's not possible to see / use all the windows previews, or they have
wrong aspect ratio.

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

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

[Desktop-packages] [Bug 1983130] Re: Ubuntu dock set to auto-hide hides after a right-click menu is closed even when there are no reasons for it to do so.