date:20230526

[Desktop-packages] [Bug 2020789] Re: pcscd should depend on vsmartcard-vpcd

2023-05-26 Thread Nathan Teodosio

Absolutely, now I remember I was testing vsmartcard... Trying to
understand the whole smart card stack I lost track of it, sorry. (:

** Changed in: pcsc-lite (Ubuntu)
   Status: New => Invalid

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

Title:
  pcscd should depend on vsmartcard-vpcd

Status in pcsc-lite package in Ubuntu:
  Invalid

Bug description:
  If I install pcscd but not vsmartcard-vpcd, the service fails to
  start:

  --->
  × pcscd.service - PC/SC Smart Card Daemon
   Loaded: loaded (/lib/systemd/system/pcscd.service; indirect; preset: 
enabled)
   Active: failed (Result: exit-code) since Thu 2023-05-25 16:11:31 CEST; 
1min 52s ago
 Duration: 59ms
  TriggeredBy: ● pcscd.socket
 Docs: man:pcscd(8)
  Process: 410224 ExecStart=/usr/sbin/pcscd --foreground --auto-exit 
$PCSCD_ARGS (code=exited, status=1/FAILURE)
 Main PID: 410224 (code=exited, status=1/FAILURE)
  CPU: 8ms

  mai 25 16:11:30 canonical systemd[1]: Started pcscd.service - PC/SC Smart 
Card Daemon.
  mai 25 16:11:31 canonical pcscd[410224]:  
configfile.l:163:evaluatetoken() Error with library 
/usr/lib/pcsc/drivers/serial/libifdvpcd.so: No such file or directory
  mai 25 16:11:31 canonical pcscd[410224]: 00017989 
pcscdaemon.c:835:clean_temp_files() Cannot remove /run/pcscd/pcscd.pid: No such 
file or directory
  mai 25 16:11:31 canonical systemd[1]: pcscd.service: Main process exited, 
code=exited, status=1/FAILURE
  mai 25 16:11:31 canonical systemd[1]: pcscd.service: Failed with result 
'exit-code'.
  <---

  Should pcscd depend on it?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pcsc-lite/+bug/2020789/+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 2020851] [NEW] Monitor setup via USB-C dock reset by gnome randomly

2023-05-26 Thread Darren

Public bug reported:

When using my intel based HP Dragonfly laptop on a USB-C Dock
(thunderbolt) gnome randomly forgets my 3 screen setup configuration
(display rotation and position)

ProblemType: Bug
DistroRelease: Ubuntu 23.04
Package: gnome-shell 44.0-2ubuntu3
ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
Uname: Linux 6.2.0-20-generic x86_64
ApportVersion: 2.26.1-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Fri May 26 08:28:02 2023
DisplayManager: gdm3
InstallationDate: Installed on 2023-05-22 (3 days ago)
InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230417)
RelatedPackageVersions: mutter-common 44.0-2ubuntu4
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)

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


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

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

Title:
  Monitor setup via USB-C dock reset by gnome randomly

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  When using my intel based HP Dragonfly laptop on a USB-C Dock
  (thunderbolt) gnome randomly forgets my 3 screen setup configuration
  (display rotation and position)

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: gnome-shell 44.0-2ubuntu3
  ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
  Uname: Linux 6.2.0-20-generic x86_64
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Fri May 26 08:28:02 2023
  DisplayManager: gdm3
  InstallationDate: Installed on 2023-05-22 (3 days ago)
  InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230417)
  RelatedPackageVersions: mutter-common 44.0-2ubuntu4
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2020851/+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 2020604] Re: After mesa upgrades, Chrome won't show graphics

2023-05-26 Thread Timo Aaltonen

also, hardware acceleration in chromium is not enabled by default AIUI,
but it is enabled in the recent beta snap

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

Title:
  After mesa upgrades, Chrome won't show graphics

Status in chromium-browser package in Ubuntu:
  Confirmed

Bug description:
  After today's Ubuntu 22.04 mesa upgrades many of our users reported
  problems viewing graphics when using Google Chrome (Stable).

  The mesa upgrades we installed were:

  [UPGRADE] libegl-mesa0:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 
22.2.5-0ubuntu0.1~22.04.2
  [UPGRADE] libegl1-mesa:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 
22.2.5-0ubuntu0.1~22.04.2
  [UPGRADE] libgl1-mesa-dri:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 
22.2.5-0ubuntu0.1~22.04.2
  [UPGRADE] libgl1-mesa-glx:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 
22.2.5-0ubuntu0.1~22.04.2
  [UPGRADE] libglapi-mesa:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 
22.2.5-0ubuntu0.1~22.04.2
  [UPGRADE] libglx-mesa0:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 
22.2.5-0ubuntu0.1~22.04.2
  [UPGRADE] mesa-vulkan-drivers:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 
22.2.5-0ubuntu0.1~22.04.2

  We documented the problem in AskUbuntu before we realized it was
  probably related to mesa, so wanted to link to that report here:

  https://askubuntu.com/questions/1469116/since-23-may-2023-ubuntu-22-04-mesa-
  updates-chrome-wont-display-website-graphi

  There are several useful pointers and bypasses listed in that
  AskUbuntu link (one being to remove affected users' GPUCache
  directories, which does not destroy their profiles and seems to work
  in many but not all cases).

  Not sure if this is an issue with mesa or Chrome or specific machine
  graphics or an interaction between them.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2020604/+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 2020851] Re: Monitor setup via USB-C dock reset by gnome randomly

2023-05-26 Thread Daniel van Vugt

Thanks for the bug report.

1. There are messages in your log suggesting one of the extensions might
be buggy:

   'gsconn...@andyholmes.github.io',
   'coverflowalt...@palatis.blogspot.com',
   'blur-my-shell@aunetx'

   Please remove all of them, log in again and then retest. It may or
may not affect this bug.

2. Please check for any evidence of crashes in /var/crash

3. If nothing is crashing then please reproduce the bug and then collect
a fresh log by running:

   journalctl -b0 > journal.txt

   and attach the resulting text file here.



** Tags added: multimonitor

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

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

Title:
  Monitor setup via USB-C dock reset by gnome randomly

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  When using my intel based HP Dragonfly laptop on a USB-C Dock
  (thunderbolt) gnome randomly forgets my 3 screen setup configuration
  (display rotation and position)

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: gnome-shell 44.0-2ubuntu3
  ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
  Uname: Linux 6.2.0-20-generic x86_64
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Fri May 26 08:28:02 2023
  DisplayManager: gdm3
  InstallationDate: Installed on 2023-05-22 (3 days ago)
  InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230417)
  RelatedPackageVersions: mutter-common 44.0-2ubuntu4
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2020851/+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 2003272] Re: [MIR] cpdb-backend-file

2023-05-26 Thread Sebastien Bacher

the cpdb-libs MIR has got accepted and the desktop-packages team
subscribed so promoting

$ ./change-override -c main -B cpdb-backend-file
Override component to main
cpdb-backend-file 2.0~b4-0ubuntu2 in mantic: universe/net -> main
cpdb-backend-file 2.0~b4-0ubuntu2 in mantic amd64: universe/net/optional/100% 
-> main
cpdb-backend-file 2.0~b4-0ubuntu2 in mantic arm64: universe/net/optional/100% 
-> main
cpdb-backend-file 2.0~b4-0ubuntu2 in mantic armhf: universe/net/optional/100% 
-> main
cpdb-backend-file 2.0~b4-0ubuntu2 in mantic ppc64el: universe/net/optional/100% 
-> main
cpdb-backend-file 2.0~b4-0ubuntu2 in mantic riscv64: universe/net/optional/100% 
-> main
cpdb-backend-file 2.0~b4-0ubuntu2 in mantic s390x: universe/net/optional/100% 
-> main
Override [y|N]? y
7 publications overridden.


** Changed in: cpdb-backend-file (Ubuntu)
   Status: Incomplete => Fix Released

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

Title:
  [MIR] cpdb-backend-file

Status in cpdb-backend-file package in Ubuntu:
  Fix Released

Bug description:
  [Availability]
  The package cpdb-backend-file is already in Ubuntu universe.
  The package cpdb-backend-file builds for the architectures it is designed to 
work on.
  It currently builds and works for architectures: amd64, arm64, armhf, 
ppc64el, riscv64, s390x
  Link to package https://launchpad.net/ubuntu/+source/cpdb-backend-file

  [Rationale]
  See the principle rationale for introducing the Common Print Dialog Backends 
(CPDB) concept in the MIR for cpdb-libs, bug #1747759.

  This package is one of the backends, the backend for printing into a
  (PDF) file. So having installed it, CPDB-supporting print dialogs show
  a printer entry to print into a PDF file in the user's home directory.

  This backend works independent of any printing system, there is no
  CUPS involved and no other system daemon. The backend tells the dialog
  that it needs a file name and the dialog opens a "Save as ..." dialog.
  Then the backend gets the user-selected file name and the job data
  stream and saves it in a file. All running as the calling user, so
  file can be saved only where the user is allowed to.

  The backend provides the only printer entry in print dialogs if on the
  system is no print environment (like CUPS) installed or no print queue
  set up. Therefore it is required to be in Ubuntu Main.

  
  The New Architecture is introduced as standard part of the distro in Ubuntu 
23.10 at the latest. Therefore cpdb-libs NEEDS to be in main before Feature 
Freeze 23.10, ideally some weeks before.

  There are very good chances that the changes on GTK and Qt already
  land in 23.04. In this case we need cpdb-libs in Main already by
  Feature Freeze of 23.04. This way the CPDB-based print dialog will be
  tested more before the switchover into the New Architecture will take
  place.

  
  [Security]
  No CVEs/security issues in this software in the past

   - no `suid` or `sgid` binaries
   - no executables in `/sbin` and `/usr/sbin`
   - Package does not install system services, timers or recurring jobs
   - Packages does not open privileged ports (ports < 1024)
   - Packages does not contain extensions to security-sensitive software

  cpdb-backend-file provides a D-Bus service, but running as normal
  user.

  The backends are triggered via session D-Bus and always run as the
  same user as the calling print dialog, so they do not introduce
  additional security problems.

  The separation of the communication with individual print technologies
  makes this code only be needed once (in the appropriate backend)
  instead of in each print dialog. This simplifies the security
  maintenance.

  
  [Quality assurance - function/usage]
  - The package works well right after install

  Once installed it gets auto-detected and automatically used by
  applications which have a print dialog using CPDB (cpdb-libs, MIR bug:
  1747759). So no explicit user action with this package required. It is
  a kind of plug-in. For the user a "Pint to file" printer will appear
  in the print dialog, so that they can send any printable content into
  a PDF instead of printing it on physical paper. Usage is totally
  intuitive.

  
  [Quality assurance - maintenance]
  - The package is maintained well in Debian/Ubuntu and has not too many
and long term critical bugs open
- Ubuntu https://bugs.launchpad.net/ubuntu/+source/cpdb-backend-file/+bug
- Debian https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=cpdb-backend-file
- Upstream https://github.com/OpenPrinting/cpdb-backend-file/issues
  - No open bugs at all, only this MIR ...
  - The package does not deal with exotic hardware we cannot support (it drops 
the print content in a regular PDF file)

  
  [Quality assurance - testing]
  - The package does not run a test at build time because it does not contai

[Desktop-packages] [Bug 1747760] Re: [MIR] cpdb-backend-cups

2023-05-26 Thread Sebastien Bacher

$ ./change-override -c main -B cpdb-backend-cups
Override component to main
cpdb-backend-cups 2.0~b4-0ubuntu1 in mantic: universe/net -> main
cpdb-backend-cups 2.0~b4-0ubuntu1 in mantic amd64: universe/net/optional/100% 
-> main
cpdb-backend-cups 2.0~b4-0ubuntu1 in mantic arm64: universe/net/optional/100% 
-> main
cpdb-backend-cups 2.0~b4-0ubuntu1 in mantic armhf: universe/net/optional/100% 
-> main
cpdb-backend-cups 2.0~b4-0ubuntu1 in mantic ppc64el: universe/net/optional/100% 
-> main
cpdb-backend-cups 2.0~b4-0ubuntu1 in mantic riscv64: universe/net/optional/100% 
-> main
cpdb-backend-cups 2.0~b4-0ubuntu1 in mantic s390x: universe/net/optional/100% 
-> main
Override [y|N]? y
7 publications overridden.


** Changed in: cpdb-backend-cups (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  [MIR] cpdb-backend-cups

Status in cpdb-backend-cups package in Ubuntu:
  Fix Released

Bug description:
  [Availability]

  Already in universe

  Built for all supported architectures

  [Rationale]

  The Common Printing Dialog Backends (CPDB) project of OpenPrinting is
  about separating the print dialogs of different GUI toolkits and
  applications (GTK, Qt, LibreOffice, ...) from the different print
  technologies (CUPS/IPP, Google Cloud Print, ...) so that they can get
  developed independently and so always from all applications one can
  print with all print technologies and changes in the print
  technologies get supported quickly.

  If one opens the print dialog, the dialog will not talk directly to
  CUPS, Google Cloud Print, or any other printing system. For this
  communication there are the backends. The dialog will find all
  available backend and sends commands to them, for listing all
  available printers, giving property/option lists for the selected
  printers, and printing on the selcted printer. This communication is
  done via D-Bus. So the backends are easily exchangeable and for
  getting support for a new print technology only its backend needs to
  get added.

  [Security]

  No known security issues, no CVEs for cpdb-backend-cups known.

  The backends are triggered via session D-Bus and always run as the
  same user as the calling print dialog, so they do not introduce
  additional security problems.

  The separation of the communication with individual print technologies
  makes this code only be needed once (in the appropriate backend)
  instead of in each print dialog. This simplifies the security
  maintenance.

  [Quality assurance]

  - The Ubuntu Printing Team is subscribed.

  https://bugs.launchpad.net/ubuntu/+source/cpdb-backend-cups
  https://github.com/OpenPrinting/cpdb-backend-cups/issues

  No upstream tests or autopkgtests.

  [Dependencies]

  Depends on cpdb-libs, MIR in bug 1747759.

  [Standards compliance]

  The package meets the FHS and Debian Policy standards (4.1.0)

  [Maintenance]

  - Actively developed upstream. Last release was 1.0.0
  https://github.com/OpenPrinting/cpdb-backend-cups/commits/master

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cpdb-backend-cups/+bug/1747760/+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 1747759] Re: [MIR] cpdb-libs

2023-05-26 Thread Sebastien Bacher

The desktop-packages team has been subscribed and Till clarified the
binary package to promote which was the other TODO ask from the MIR
review, promoting

$ ./change-override -c main -t cpdb-libs
Override component to main
cpdb-libs 2.0~b4-0ubuntu2 in mantic: universe/net -> main
Override [y|N]? y
1 publication overridden.

 ./change-override -c main libcpdb-frontend2 libcpdb2
Override component to main
libcpdb-frontend2 2.0~b4-0ubuntu2 in mantic amd64: universe/libs/optional/100% 
-> main
libcpdb-frontend2 2.0~b4-0ubuntu2 in mantic arm64: universe/libs/optional/100% 
-> main
libcpdb-frontend2 2.0~b4-0ubuntu2 in mantic armhf: universe/libs/optional/100% 
-> main
libcpdb-frontend2 2.0~b4-0ubuntu2 in mantic ppc64el: 
universe/libs/optional/100% -> main
libcpdb-frontend2 2.0~b4-0ubuntu2 in mantic riscv64: 
universe/libs/optional/100% -> main
libcpdb-frontend2 2.0~b4-0ubuntu2 in mantic s390x: universe/libs/optional/100% 
-> main
libcpdb2 2.0~b4-0ubuntu2 in mantic amd64: universe/libs/optional/100% -> main
libcpdb2 2.0~b4-0ubuntu2 in mantic arm64: universe/libs/optional/100% -> main
libcpdb2 2.0~b4-0ubuntu2 in mantic armhf: universe/libs/optional/100% -> main
libcpdb2 2.0~b4-0ubuntu2 in mantic ppc64el: universe/libs/optional/100% -> main
libcpdb2 2.0~b4-0ubuntu2 in mantic riscv64: universe/libs/optional/100% -> main
libcpdb2 2.0~b4-0ubuntu2 in mantic s390x: universe/libs/optional/100% -> main
Override [y|N]? y
12 publications overridden.



** Changed in: cpdb-libs (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  [MIR] cpdb-libs

Status in cpdb-libs package in Ubuntu:
  Fix Released

Bug description:
  [Availability]
  The package cpdb-libs is already in Ubuntu universe.
  The package cpdb-libs build for the architectures it is designed to work on.
  It currently builds and works for architetcures: amd64, arm64, armhf, 
ppc64el, riscv64, s390x

  Link to package https://launchpad.net/ubuntu/+source/cpdb-libs

  [Rationale]
  The Common Printing Dialog Backends (CPDB) project of OpenPrinting is about 
separating the print dialogs of different GUI toolkits and applications (GTK, 
Qt, Firefox, Chromium, LibreOffice, ...) from the different print technologies 
(CUPS, print to file, cloud printing services, ...) so that they can get 
developed independently and so always from all applications one can print with 
all print technologies and changes in the print technologies get supported 
quickly.

  If one opens the print dialog, the dialog will not talk directly to
  CUPS, a cloud printing service, or any other printing system. For this
  communication there are the backends. The dialog will find all
  available backends and sends commands to them, for listing all
  available printers, giving property/option lists for the selected
  printers, and printing on the selected printer. This communication is
  done via D-Bus. So the backends are easily exchangeable and for
  getting support for a new print technology only its backend needs to
  get added.

  Backends can even be packaged as Snaps, because they communicate only
  by D-Bus with the frontend, so a cloud printing provider could put
  their backend into the Snap Store.

  All packages providing a print dialog will get modified (upstream) to
  support CPDB with this library and then these packages will depend on
  cpdb-libs.

  These packages are:

  - GUI toolkits: GTK, Qt
  - GUI applications with their own print dialogs: Firefox/Thunderbird,
    Chromium/Chrome, LibreOffice, ...

  The coding of the CPDB support in GTK and Qt got already done in GSoC
  2022 and currently merge requests are worked on to be included
  upstream. Once they are upstream (and already before the next upstream
  releases) they will get added to Ubuntu as distro patches.

  See

  https://github.com/TinyTrebuchet/gsoc22/

  The dialogs of the browsers and LibreOffice will be worked on in GSoC
  2023:

  https://wiki.linuxfoundation.org/gsoc/google-summer-
  code-2023-openprinting-
  
projects#cpdb_support_for_application_s_print_dialogsfirefox_chromium_libreoffice

  This is also needed for the upcoming New Architecture of printing,
  where we go all-IPP and do not use PPD files any more. The CUPS
  backend for the CPDB (cpdb-backend-cups) is already designed to not
  handle PPD files any more.

  The New Architecture is introduced as standard part of the distro in
  Ubuntu 23.10 at the latest. Therefore cpdb-libs NEEDS to be in main
  before Feature Freeze 23.10, ideally some weeks before.

  There are very good chances that the changes on GTK and Qt already
  land in 23.04. In this case we need cpdb-libs in Main already by
  Feature Freeze of 23.04. This way the CPDB-based print dilaog will be
  tested more before the switchover into the New Architecture will take
  place.

  [Security]
  No CVEs/secur

[Desktop-packages] [Bug 2020708] Autopkgtest regression report (gtk4/4.10.3+ds-0ubuntu1)

2023-05-26 Thread Ubuntu SRU Bot

All autopkgtests for the newly accepted gtk4 (4.10.3+ds-0ubuntu1) for lunar 
have finished running.
The following regressions have been reported in tests triggered by the package:

libadwaita-1/1.3.1-1ubuntu2 (amd64, arm64, armhf, ppc64el, s390x)
libreoffice/4:7.5.3-0ubuntu0.23.04.1 (amd64, armhf)


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#gtk4

[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 gtk4 in Ubuntu.
https://bugs.launchpad.net/bugs/2020708

Title:
  Update gtk4 to 4.10.3

Status in gtk4 package in Ubuntu:
  Fix Released
Status in gtk4 source package in Lunar:
  Fix Committed

Bug description:
  Impact
  -
  There is a new point release in the stable GTK 4.10 series.

  https://gitlab.gnome.org/GNOME/gtk/-/blob/4.10.3/NEWS

  The version currently in Ubuntu 23.04 is 4.10.1

  Test Case 0
  ---
  gtk4 has an extensive build test suite, and failures will fail the build.
  gtk4 also has thorough autopkgtests.
  Ensure that the build succeeds and that the autopgktests pass.

  Test Case 1
  ---
  Make sure that opening and saving files from the Firefox and Chromium snaps 
still work

  Test Case 2
  ---
  snap install portal-test
  snap run portal-test
  Verify that the app seems to still work ok

  What Could Go Wrong
  ---
  Ubuntu includes xdg-desktop-portal-gnome by default which is used for many 
snap actions like providing a file chooser. This is critical functionality for 
our snaps.

  The Ubuntu flavors use a different portal backend, most commonly xdg-
  desktop-portal-gtk which uses GTK3 so it's not affected by this SRU.

  Many of the default Ubuntu 23.04 desktop apps use GTK4. A serious
  enough regression could severely break the Ubuntu Desktop.

  gtk4 is included in the GNOME micro release exception.

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

  Other Info
  --
  The libadwaita autopkgtest needed to be updated to pass with gtk 4.10.3. This 
is being handled with LP: #2019989

  gtk4 needs to be updated before or at the same time as mutter 44.1 to
  avoid a regression with artifacts near window borders. See LP:
  #2020674 for the gtk4 fix and LP: #2020225 for the mutter 44.1 SRU.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk4/+bug/2020708/+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 2020674] Autopkgtest regression report (gtk4/4.10.3+ds-0ubuntu1)

2023-05-26 Thread Ubuntu SRU Bot

All autopkgtests for the newly accepted gtk4 (4.10.3+ds-0ubuntu1) for lunar 
have finished running.
The following regressions have been reported in tests triggered by the package:

libadwaita-1/1.3.1-1ubuntu2 (amd64, arm64, armhf, ppc64el, s390x)
libreoffice/4:7.5.3-0ubuntu0.23.04.1 (amd64, armhf)


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#gtk4

[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 gtk4 in Ubuntu.
https://bugs.launchpad.net/bugs/2020674

Title:
  Artifacts at window borders with mutter 44.1

Status in GTK+:
  Fix Released
Status in gtk4 package in Ubuntu:
  Fix Released
Status in gtk4 source package in Lunar:
  Fix Committed

Bug description:
  Impact
  --
  Mutter 44.1 switched from using the GL renderer to using Cairo to avoid 
rendering artifacts with the Nvidia drivers. However, this also needed a change 
in GTK4 to avoid other artifacts.

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

  https://gitlab.gnome.org/GNOME/gtk/-/merge_requests/5857

  Test Case
  -
  Install gnome-shell 44.1 (currently in lunar-proposed).
  Install this gtk4 update.
  After installing the updates, log out and log back in.
  Open a terminal and the Chromium web browser.
  Tile the terminal to the left and tile Chromium to the right.

  Verify that there aren't rectangle rendering artifacts near the border
  between the two apps.

  What Could Go Wrong
  ---
  This is a one-line patch, cherry-picked from the gtk-4-10 branch that will be 
included in GTK 4.10.4 (which is expected to be released any day now). This 
puts us just a bit ahead of some other distros.

  See the master bug LP: #2020708 for more details about what it means
  to update GTK4.

  Excerpt from Original Report
  
  I wanted to report that I'm now seeing artifacts around window borders, when 
they are arranged to occupy all available area. I should note I'm also using 
gnome-shell-extension-ubuntu-tiling-assistant 39-3ubuntu2.

  I'm attaching a screen recording of what I'm seeing.

  The artifact at the border also happens across monitors. The tall
  chrome window on the right of the left monitor interferes with the
  windows aligned to the left of the right monitor.

  This happened immediately after updating mutter and gnome shell to
  44.1, it wasn't happening before.

  So far I'm seeing them with just google-chrome and chromium (snap),
  but not other apps I quickly tried (gnome-terminal, firefox).

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: libmutter-12-0 44.1-0ubuntu1
  ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
  Uname: Linux 6.2.0-20-generic x86_64
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Wed May 24 10:17:44 2023
  SourcePackage: mutter
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gtk/+bug/2020674/+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 2020674] Re: Artifacts at window borders with mutter 44.1

2023-05-26 Thread m...@papersolve.com

I can confirm that (after figuring out which packages I had to force
version on and getting them all installed and restarting my session) the
gtk4 patch does fix the issue. No more weird corrupted borders, yay! I
do not see any issues with libreoffice either just in basic testing of
Writer and Calc, not sure what happened with that regression.

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

Title:
  Artifacts at window borders with mutter 44.1

Status in GTK+:
  Fix Released
Status in gtk4 package in Ubuntu:
  Fix Released
Status in gtk4 source package in Lunar:
  Fix Committed

Bug description:
  Impact
  --
  Mutter 44.1 switched from using the GL renderer to using Cairo to avoid 
rendering artifacts with the Nvidia drivers. However, this also needed a change 
in GTK4 to avoid other artifacts.

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

  https://gitlab.gnome.org/GNOME/gtk/-/merge_requests/5857

  Test Case
  -
  Install gnome-shell 44.1 (currently in lunar-proposed).
  Install this gtk4 update.
  After installing the updates, log out and log back in.
  Open a terminal and the Chromium web browser.
  Tile the terminal to the left and tile Chromium to the right.

  Verify that there aren't rectangle rendering artifacts near the border
  between the two apps.

  What Could Go Wrong
  ---
  This is a one-line patch, cherry-picked from the gtk-4-10 branch that will be 
included in GTK 4.10.4 (which is expected to be released any day now). This 
puts us just a bit ahead of some other distros.

  See the master bug LP: #2020708 for more details about what it means
  to update GTK4.

  Excerpt from Original Report
  
  I wanted to report that I'm now seeing artifacts around window borders, when 
they are arranged to occupy all available area. I should note I'm also using 
gnome-shell-extension-ubuntu-tiling-assistant 39-3ubuntu2.

  I'm attaching a screen recording of what I'm seeing.

  The artifact at the border also happens across monitors. The tall
  chrome window on the right of the left monitor interferes with the
  windows aligned to the left of the right monitor.

  This happened immediately after updating mutter and gnome shell to
  44.1, it wasn't happening before.

  So far I'm seeing them with just google-chrome and chromium (snap),
  but not other apps I quickly tried (gnome-terminal, firefox).

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: libmutter-12-0 44.1-0ubuntu1
  ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
  Uname: Linux 6.2.0-20-generic x86_64
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Wed May 24 10:17:44 2023
  SourcePackage: mutter
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gtk/+bug/2020674/+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 2020893] [NEW] Changing path for the certificates and keys doesn't work

2023-05-26 Thread mastier1

Private bug reported:

If you modify existing OpenVPN connection NetworkManager does not
reflect them without restart

I changed path for files (other directory), yet it still tries to load
the old path

mastier@drakkar:~$ nmcli con up 'Canonical UK'
Error: Connection activation failed: Unknown reason
Hint: use 'journalctl -xe NM_CONNECTION=9328632c-dcb0-4414-8609-20285bf0acb8 + 
NM_DEVICE=eno1' to get more details.

mastier@drakkar:~$ grep -iHR openvpn /var/log/syslog|tail
/var/log/syslog:May 26 15:16:43 drakkar nm-openvpn[726598]: Cannot pre-load 
keyfile (/home/mastier/Documents/vpn/canonical_ta.key)
/var/log/syslog:May 26 15:16:43 drakkar nm-openvpn[726598]: Exiting due to 
fatal error
/var/log/syslog:May 26 15:16:55 drakkar NetworkManager[5372]:   
[1685107015.3225] 
vpn[0x555f6a6a6750,9328632c-dcb0-4414-8609-20285bf0acb8,"Canonical UK"]: 
starting openvpn
/var/log/syslog:May 26 15:16:55 drakkar nm-openvpn[727045]: DEPRECATED OPTION: 
--cipher set to 'AES-128-CBC' but missing in --data-ciphers 
(AES-256-GCM:AES-128-GCM). Future OpenVPN version will ignore --cipher for 
cipher negotiations. Add 'AES-128-CBC' to --data-ciphers or change --cipher 
'AES-128-CBC' to --data-ciphers-fallback 'AES-128-CBC' to silence this warning.
/var/log/syslog:May 26 15:16:55 drakkar nm-openvpn[727045]: Cannot pre-load 
keyfile (/home/mastier/Documents/vpn/canonical_ta.key)
/var/log/syslog:May 26 15:16:55 drakkar nm-openvpn[727045]: Exiting due to 
fatal error
/var/log/syslog:May 26 15:19:40 drakkar NetworkManager[5372]:   
[1685107180.3388] 
vpn[0x555f6a6a69d0,9328632c-dcb0-4414-8609-20285bf0acb8,"Canonical UK"]: 
starting openvpn
/var/log/syslog:May 26 15:19:40 drakkar nm-openvpn[731307]: DEPRECATED OPTION: 
--cipher set to 'AES-128-CBC' but missing in --data-ciphers 
(AES-256-GCM:AES-128-GCM). Future OpenVPN version will ignore --cipher for 
cipher negotiations. Add 'AES-128-CBC' to --data-ciphers or change --cipher 
'AES-128-CBC' to --data-ciphers-fallback 'AES-128-CBC' to silence this warning.
/var/log/syslog:May 26 15:19:40 drakkar nm-openvpn[731307]: Cannot pre-load 
keyfile (/home/mastier/Documents/vpn/canonical_ta.key)
/var/log/syslog:May 26 15:19:40 drakkar nm-openvpn[731307]: Exiting due to 
fatal error

$ nmcli con show 'Canonical UK' |grep Docum
vpn.data:   ca = 
/home/mastier/Documents/canonical-vpn/canonical_ca.crt, cert = 
/home/mastier/Documents/canonical-vpn/canonical-mastier.crt, cert-pass-flags = 
0, cipher = AES-128-CBC, comp-lzo = adaptive, connection-type = tls, dev = tun, 
dev-type = tun, key = 
/home/mastier/Documents/canonical-vpn/canonical-mastier.key, ping = 10, 
ping-restart = 60, remote = uk.sesame.canonical.com:29419, remote-cert-tls = 
server, ta = /home/mastier/Documents/vpn/canonical_ta.key, ta-dir = 1, 
verify-x509-name = name:access.is

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: network-manager-openvpn 1.8.18-1
ProcVersionSignature: Ubuntu 6.1.0-1012.12-oem 6.1.25
Uname: Linux 6.1.0-1012-oem x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu82.4
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Fri May 26 15:21:21 2023
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: network-manager-openvpn
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: network-manager (Ubuntu)
 Importance: Undecided
 Status: New

** Affects: network-manager-openvpn (Ubuntu)
 Importance: Undecided
 Status: New


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

** Information type changed from Public to Private

** Description changed:

- If you modify existing VPC connection NetworkManager does not reflect
- them without restart
+ If you modify existing OpenVPN connection NetworkManager does not
+ reflect them without restart
  
  I changed path for files (other directory), yet it still tries to load
  the old path
  
  mastier@drakkar:~$ nmcli con up 'Canonical UK'
  Error: Connection activation failed: Unknown reason
  Hint: use 'journalctl -xe NM_CONNECTION=9328632c-dcb0-4414-8609-20285bf0acb8 
+ NM_DEVICE=eno1' to get more details.
  
  mastier@drakkar:~$ grep -iHR openvpn /var/log/syslog|tail
  /var/log/syslog:May 26 15:16:43 drakkar nm-openvpn[726598]: Cannot pre-load 
keyfile (/home/mastier/Documents/vpn/canonical_ta.key)
  /var/log/syslog:May 26 15:16:43 drakkar nm-openvpn[726598]: Exiting due to 
fatal error
  /var/log/syslog:May 26 15:16:55 drakkar NetworkManager[5372]:   
[1685107015.3225] 
vpn[0x555f6a6a6750,9328632c-dcb0-4414-8609-20285bf0acb8,"Canonical UK"]: 
starting openvpn
  /var/log/syslog:May 26 15:16:55 drakkar nm-openvpn[727045]: DEPRECATED 
OPTION: --cipher set to 'AES-128-CBC' but missing in --data-ciphers 
(AES-256-GCM:AES-128-GCM). Future OpenVPN version will ignore --cipher for 
cipher negotiations. Add 'AES-128-CBC' to --data-ciphers or change --c

[Desktop-packages] [Bug 2020674] Re: Artifacts at window borders with mutter 44.1

2023-05-26 Thread Jeremy Bícha

Mike, thank you for reporting the results of your testing.

You can ignore the message about the autopkgtest regression. The
libreoffice autopkgtest is very complex and sometimes fails for other
reasons unrelated to new package updates.

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

Title:
  Artifacts at window borders with mutter 44.1

Status in GTK+:
  Fix Released
Status in gtk4 package in Ubuntu:
  Fix Released
Status in gtk4 source package in Lunar:
  Fix Committed

Bug description:
  Impact
  --
  Mutter 44.1 switched from using the GL renderer to using Cairo to avoid 
rendering artifacts with the Nvidia drivers. However, this also needed a change 
in GTK4 to avoid other artifacts.

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

  https://gitlab.gnome.org/GNOME/gtk/-/merge_requests/5857

  Test Case
  -
  Install gnome-shell 44.1 (currently in lunar-proposed).
  Install this gtk4 update.
  After installing the updates, log out and log back in.
  Open a terminal and the Chromium web browser.
  Tile the terminal to the left and tile Chromium to the right.

  Verify that there aren't rectangle rendering artifacts near the border
  between the two apps.

  What Could Go Wrong
  ---
  This is a one-line patch, cherry-picked from the gtk-4-10 branch that will be 
included in GTK 4.10.4 (which is expected to be released any day now). This 
puts us just a bit ahead of some other distros.

  See the master bug LP: #2020708 for more details about what it means
  to update GTK4.

  Excerpt from Original Report
  
  I wanted to report that I'm now seeing artifacts around window borders, when 
they are arranged to occupy all available area. I should note I'm also using 
gnome-shell-extension-ubuntu-tiling-assistant 39-3ubuntu2.

  I'm attaching a screen recording of what I'm seeing.

  The artifact at the border also happens across monitors. The tall
  chrome window on the right of the left monitor interferes with the
  windows aligned to the left of the right monitor.

  This happened immediately after updating mutter and gnome shell to
  44.1, it wasn't happening before.

  So far I'm seeing them with just google-chrome and chromium (snap),
  but not other apps I quickly tried (gnome-terminal, firefox).

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: libmutter-12-0 44.1-0ubuntu1
  ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
  Uname: Linux 6.2.0-20-generic x86_64
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Wed May 24 10:17:44 2023
  SourcePackage: mutter
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gtk/+bug/2020674/+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 1966413] Re: --no-oem option is broken

2023-05-26 Thread Alberto Milone

** Changed in: ubuntu-drivers-common (Ubuntu)
   Importance: Undecided => High

** Changed in: ubuntu-drivers-common (Ubuntu)
 Assignee: (unassigned) => Alberto Milone (albertomilone)

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

Title:
  --no-oem option is broken

Status in ubuntu-drivers-common package in Ubuntu:
  Confirmed

Bug description:
  [Impact]
  * ubuntu-drivers supports the --no-oem option, which is meant to filter-out 
the OEM metapackages when running on certified hardware.

  * When ubuntu-drivers is invoked with --no-oem as a global option (i.e., 
`ubuntu-drivers --no-oem list` or `ubuntu-drivers --no-oem install`, the script 
crashes with the following exception:
    NameError: name 'install_oem_meta' is not defined

  * When ubuntu-drivers is invoked with --no-oem as a sub-option of
  "install" (i.e., `ubuntu-drivers install --no-oem`), the script does
  not crash but the option is silently ignored - resulting in an OEM
  metapackage to be installed if we are running on certified hardware.
  This defeats the purpose of the option.

  * Today, the --no-oem option can be passed to ubuntu-drivers by ubiquity as a 
suboption of `ubuntu-drivers install`. By default, the option is not passed to 
ubuntu-drivers but the users can opt-in using preseeds. If they do, their 
decision is essentially ignored since the OEM metapackage will still be 
installed:
  https://git.launchpad.net/ubiquity/tree/scripts/simple-plugins#n20

  * As part of the 23.10 cycle, subiquity will start replacing the
  functionality from ubiquity for OEM installs. At the moment, subiquity
  relies on the version of ubuntu-drivers-common from the system being
  installed. But going forward, we might have to ship ubuntu-drivers-
  common in the subiquity snap. This means we will fetch the deb from
  jammy-updates since subiquity is a core22-based snap.

  [Test plan]
  1. We will compare the result of the following commands with and without the 
patch (both on certified and on un-certified hardware):
    * ubuntu-drivers --no-oem list
    -> crashes without the patch. Should not crash with the patch. The list 
returned should not include the OEM metapackage.
    * ubuntu-drivers --no-oem install
    -> crashes without the patch. Should not crash with the patch. The list 
of packages installed should not include the OEM metapackage.
    * ubuntu-drivers install --no-oem
    -> without the patch, the OEM metapackage gets installed on certified 
hardware. With the patch, it should not.

  2. We will ensure ubiquity stills manages to install ubuntu on
  certified hardware. We will also ensure that the OEM metapackage does
  not get installed when it should not.

  [Where problems could occur]
  * When used as a global option, --no-oem currently makes the script crash 
unconditionally. Therefore, the change should be very low risk in that regard.
  * When used as a suboption of "install", the --no-oem option currently gets 
ignored silently. If people have been automating ubuntu deployment in one way 
or another and have used --no-oem, they might be surprised to notice that fewer 
packages get installed on their target system, after the option is fixed. This 
is theoretically a good thing, but might require some adjustments on their end.

  [Original description]
  $ ubuntu-drivers --no-oem install
  Traceback (most recent call last):
    File "/usr/bin/ubuntu-drivers", line 490, in 
  greet()
    File "/usr/lib/python3/dist-packages/click/core.py", line 764, in __call__
  return self.main(*args, **kwargs)
    File "/usr/lib/python3/dist-packages/click/core.py", line 717, in main
  rv = self.invoke(ctx)
    File "/usr/lib/python3/dist-packages/click/core.py", line 1134, in invoke
  Command.invoke(self, ctx)
    File "/usr/lib/python3/dist-packages/click/core.py", line 956, in invoke
  return ctx.invoke(self.callback, **ctx.params)
    File "/usr/lib/python3/dist-packages/click/core.py", line 555, in invoke
  return callback(*args, **kwargs)
    File "/usr/lib/python3/dist-packages/click/decorators.py", line 64, in 
new_func
  return ctx.invoke(f, obj, *args, **kwargs)
    File "/usr/lib/python3/dist-packages/click/core.py", line 555, in invoke
  return callback(*args, **kwargs)
    File "/usr/bin/ubuntu-drivers", line 376, in greet
  config.no_oem = install_oem_meta
  NameError: name 'install_oem_meta' is not defined

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubuntu-drivers-common 1:0.9.0~0.20.04.1
  ProcVersionSignature: Ubuntu 5.13.0-37.42~20.04.1-generic 5.13.19
  Uname: Linux 5.13.0-37-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Fri Mar 25 11:44:15 2022
  InstallationDate: Installed on 2022-03-25 (0 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fo

Re: [Desktop-packages] [Bug 2020604] Re: After mesa upgrades, Chrome won't show graphics

2023-05-26 Thread Chris Hall

Disabling gpu solved the problem for both Brave, Brave-beta and Chrome. 
Once I could get the browsers to open up and render text, it was than 
possible to turn off hardware acceleration. Any idea if the mesa driver 
problem will be addressed in the next update?

An ironic thing about the about://gpu url is that unless you disable the 
gpu, it's not possible to even read  the url. A real chicken and egg 
problem.

Chris Hall

On 5/26/23 4:13 AM, Nathan Teodosio wrote:
> Passing --disable-gpu would likely help here.
>
> Hardware acceleration stuff can be seen in about://gpu.
>
> At the moment we have hardware acceleration decoding, which as far as I
> can tell is not the issue here, in candidate/hwacc and edge/hwacc but
> that is focused at Intel.[1]
>
> For the time being I think for Chromium snap we can just add a
>
>rm -r "$SNAP_USER_COMMON"/chromium/*/GPUCache
>
> as a stop gap measure.
>
> [1] https://discourse.ubuntu.com/t/chromium-hardware-accelerated-build-
> for-intel-based-platforms-available-for-beta-testing/35625/3
>

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

Title:
  After mesa upgrades, Chrome won't show graphics

Status in chromium-browser package in Ubuntu:
  Fix Committed

Bug description:
  After today's Ubuntu 22.04 mesa upgrades many of our users reported
  problems viewing graphics when using Google Chrome (Stable).

  The mesa upgrades we installed were:

  [UPGRADE] libegl-mesa0:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 
22.2.5-0ubuntu0.1~22.04.2
  [UPGRADE] libegl1-mesa:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 
22.2.5-0ubuntu0.1~22.04.2
  [UPGRADE] libgl1-mesa-dri:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 
22.2.5-0ubuntu0.1~22.04.2
  [UPGRADE] libgl1-mesa-glx:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 
22.2.5-0ubuntu0.1~22.04.2
  [UPGRADE] libglapi-mesa:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 
22.2.5-0ubuntu0.1~22.04.2
  [UPGRADE] libglx-mesa0:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 
22.2.5-0ubuntu0.1~22.04.2
  [UPGRADE] mesa-vulkan-drivers:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 
22.2.5-0ubuntu0.1~22.04.2

  We documented the problem in AskUbuntu before we realized it was
  probably related to mesa, so wanted to link to that report here:

  https://askubuntu.com/questions/1469116/since-23-may-2023-ubuntu-22-04-mesa-
  updates-chrome-wont-display-website-graphi

  There are several useful pointers and bypasses listed in that
  AskUbuntu link (one being to remove affected users' GPUCache
  directories, which does not destroy their profiles and seems to work
  in many but not all cases).

  Not sure if this is an issue with mesa or Chrome or specific machine
  graphics or an interaction between them.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2020604/+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 2020604] Re: After mesa upgrades, Chrome won't show graphics

2023-05-26 Thread Nathan Teodosio

> Any idea if the mesa driver
> problem will be addressed in the next update?

Time will tell, if my reading of #12 is correct then this isn't really a 
problem with Mesa but with upstream.

> An ironic thing about the about://gpu url is that unless you disable the
> gpu, it's not possible to even read  the url. A real chicken and egg
> problem.

One could do a blind

   Ctrl+L
   about:gpu
   
   

to get the report to clipboard, but you would never know that without 
seeing the page. (:

That information isn't otherwise available even with 
--enable-logging=stderr --v=1...

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

Title:
  After mesa upgrades, Chrome won't show graphics

Status in chromium-browser package in Ubuntu:
  Fix Committed

Bug description:
  After today's Ubuntu 22.04 mesa upgrades many of our users reported
  problems viewing graphics when using Google Chrome (Stable).

  The mesa upgrades we installed were:

  [UPGRADE] libegl-mesa0:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 
22.2.5-0ubuntu0.1~22.04.2
  [UPGRADE] libegl1-mesa:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 
22.2.5-0ubuntu0.1~22.04.2
  [UPGRADE] libgl1-mesa-dri:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 
22.2.5-0ubuntu0.1~22.04.2
  [UPGRADE] libgl1-mesa-glx:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 
22.2.5-0ubuntu0.1~22.04.2
  [UPGRADE] libglapi-mesa:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 
22.2.5-0ubuntu0.1~22.04.2
  [UPGRADE] libglx-mesa0:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 
22.2.5-0ubuntu0.1~22.04.2
  [UPGRADE] mesa-vulkan-drivers:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 
22.2.5-0ubuntu0.1~22.04.2

  We documented the problem in AskUbuntu before we realized it was
  probably related to mesa, so wanted to link to that report here:

  https://askubuntu.com/questions/1469116/since-23-may-2023-ubuntu-22-04-mesa-
  updates-chrome-wont-display-website-graphi

  There are several useful pointers and bypasses listed in that
  AskUbuntu link (one being to remove affected users' GPUCache
  directories, which does not destroy their profiles and seems to work
  in many but not all cases).

  Not sure if this is an issue with mesa or Chrome or specific machine
  graphics or an interaction between them.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2020604/+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 2019016] Re: nvidia_desktop_pre_installation_hook raises on package names with suffixes

2023-05-26 Thread Alberto Milone

Hi Fox, can you try ubuntu-drivers 1:0.9.6.2~0.22.04.3 from proposed,
please?

The problem should be LP: #1993019

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

Title:
  nvidia_desktop_pre_installation_hook raises on package names with
  suffixes

Status in ubuntu-drivers-common package in Ubuntu:
  New

Bug description:
  The function nvidia_desktop_pre_installation_hook in
  /usr/lib/python3/dist-packages/UbuntuDrivers/detect.py on Ubuntu
  22.04.2 LTS assumes that the driver package name ends with the driver
  version as the suffix.

  However this does not account for the '-open' drivers. The following
  code from that function is at fault:

  ```
  # Enable KMS if nvidia >= 470
  for package_name in to_install:
  if package_name.startswith('nvidia-driver-'):
 try:
 version = int(package_name.split('-')[-1]) # <--- This here
 with_nvidia_kms = version >= 470
 except ValueError:
 pass
 finally:
 with_nvidia_kms = version >= 470  # <-- And this here, too, 
which will never succeed.

  ```

  The line `version = int(package_name.split('-')[-1])` assumes a
  package name like `nvidia-driver-530` rather than `nvidia-
  driver-530-open`, however `nvidia-driver-530-open` is the autoselected
  package for my install.

  This code could be fixed by switching to a regex, or else retrying
  with index -2 rather than index -1.

  Also, the `finally` clause will always fail-- there should only ever
  be one matching `nvidia-driver-` prefixed package, and if that raises
  a ValueError, then `version` will not be set, raising an
  UnboundLocalError.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: ubuntu-drivers-common 1:0.9.6.1 [modified: 
usr/lib/python3/dist-packages/UbuntuDrivers/detect.py]
  ProcVersionSignature: Ubuntu 5.19.0-41.42~22.04.1-generic 5.19.17
  Uname: Linux 5.19.0-41-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.4
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue May  9 10:47:07 2023
  InstallationDate: Installed on 2022-08-20 (261 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/zsh
  SourcePackage: ubuntu-drivers-common
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/2019016/+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 2020604] Re: After mesa upgrades, Chrome won't show graphics

2023-05-26 Thread Nathan Teodosio

The workaround is available in candidate channel (currently only ready
for amd64).

  snap refresh --candidate chromium

If someone could please verify the workaround, I can bump to stable.

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

Title:
  After mesa upgrades, Chrome won't show graphics

Status in chromium-browser package in Ubuntu:
  Fix Committed
Status in mesa package in Ubuntu:
  Triaged

Bug description:
  After today's Ubuntu 22.04 mesa upgrades many of our users reported
  problems viewing graphics when using Google Chrome (Stable).

  The mesa upgrades we installed were:

  [UPGRADE] libegl-mesa0:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 
22.2.5-0ubuntu0.1~22.04.2
  [UPGRADE] libegl1-mesa:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 
22.2.5-0ubuntu0.1~22.04.2
  [UPGRADE] libgl1-mesa-dri:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 
22.2.5-0ubuntu0.1~22.04.2
  [UPGRADE] libgl1-mesa-glx:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 
22.2.5-0ubuntu0.1~22.04.2
  [UPGRADE] libglapi-mesa:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 
22.2.5-0ubuntu0.1~22.04.2
  [UPGRADE] libglx-mesa0:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 
22.2.5-0ubuntu0.1~22.04.2
  [UPGRADE] mesa-vulkan-drivers:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 
22.2.5-0ubuntu0.1~22.04.2

  We documented the problem in AskUbuntu before we realized it was
  probably related to mesa, so wanted to link to that report here:

  https://askubuntu.com/questions/1469116/since-23-may-2023-ubuntu-22-04-mesa-
  updates-chrome-wont-display-website-graphi

  There are several useful pointers and bypasses listed in that
  AskUbuntu link (one being to remove affected users' GPUCache
  directories, which does not destroy their profiles and seems to work
  in many but not all cases).

  Not sure if this is an issue with mesa or Chrome or specific machine
  graphics or an interaction between them.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2020604/+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 2013542] Re: [lunar] windows size/position is not saved for some apps

2023-05-26 Thread Jaromir Obr

It would be great if anyone could add an explanation why such regression 
behavior started in 23.04.
Is it a bug or by design? Maybe it's possible to change the behavior in dconf 
editor?
For me it's a show stopper for upgrade of Ubuntu on other machines I have.

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

Title:
  [lunar] windows size/position is not saved for some apps

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  Lunar up to date, Ubuntu session, Wayland or X11

  1) open Synaptic not in full screen
  2) change window size to full screen
  3) close Synaptic
  4) open Synaptic
  5) its window is not maximized

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2013542/+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 2020604] Re: After mesa upgrades, Chrome won't show graphics

2023-05-26 Thread Dave Chiluk

As I have multiple profiles, I chose to simply delete all Cache
directories


$ find ~/.config/google-chrome \( -name "*Cache" \) | xargs -d '\n' -L 1 rm -rf

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

Title:
  After mesa upgrades, Chrome won't show graphics

Status in chromium-browser package in Ubuntu:
  Fix Committed
Status in mesa package in Ubuntu:
  Triaged

Bug description:
  After today's Ubuntu 22.04 mesa upgrades many of our users reported
  problems viewing graphics when using Google Chrome (Stable).

  The mesa upgrades we installed were:

  [UPGRADE] libegl-mesa0:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 
22.2.5-0ubuntu0.1~22.04.2
  [UPGRADE] libegl1-mesa:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 
22.2.5-0ubuntu0.1~22.04.2
  [UPGRADE] libgl1-mesa-dri:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 
22.2.5-0ubuntu0.1~22.04.2
  [UPGRADE] libgl1-mesa-glx:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 
22.2.5-0ubuntu0.1~22.04.2
  [UPGRADE] libglapi-mesa:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 
22.2.5-0ubuntu0.1~22.04.2
  [UPGRADE] libglx-mesa0:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 
22.2.5-0ubuntu0.1~22.04.2
  [UPGRADE] mesa-vulkan-drivers:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 
22.2.5-0ubuntu0.1~22.04.2

  We documented the problem in AskUbuntu before we realized it was
  probably related to mesa, so wanted to link to that report here:

  https://askubuntu.com/questions/1469116/since-23-may-2023-ubuntu-22-04-mesa-
  updates-chrome-wont-display-website-graphi

  There are several useful pointers and bypasses listed in that
  AskUbuntu link (one being to remove affected users' GPUCache
  directories, which does not destroy their profiles and seems to work
  in many but not all cases).

  Not sure if this is an issue with mesa or Chrome or specific machine
  graphics or an interaction between them.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2020604/+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 2020904] [NEW] gnome-shell segfault when dragging a link from firefox

2023-05-26 Thread Kai Groner

Public bug reported:

This has happened to me twice in the last 24h.

I was dragging a link from firefox to another application.  The crash
occurs before I release the mouse button to drop the link in the second
application. In both cases the drag was across two displays.  The first
time, the intended target was wezterm (deb).  The second time, the
intended target was chromium (snap).

ProblemType: Bug
DistroRelease: Ubuntu 23.04
Package: gnome-shell 44.0-2ubuntu3
ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
Uname: Linux 6.2.0-20-generic x86_64
ApportVersion: 2.26.1-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Fri May 26 11:57:45 2023
DisplayManager: gdm3
InstallationDate: Installed on 2019-06-18 (1438 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
ProcEnviron:
 LANG=en_US.UTF-8
 PATH=(custom, no user)
 SHELL=/bin/bash
 TERM=tmux-256color
 XDG_RUNTIME_DIR=
RelatedPackageVersions: mutter-common 44.0-2ubuntu4.23.04.1
SourcePackage: gnome-shell
UpgradeStatus: Upgraded to lunar on 2023-05-09 (17 days ago)

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


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

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

Title:
  gnome-shell segfault when dragging a link from firefox

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  This has happened to me twice in the last 24h.

  I was dragging a link from firefox to another application.  The crash
  occurs before I release the mouse button to drop the link in the
  second application. In both cases the drag was across two displays.
  The first time, the intended target was wezterm (deb).  The second
  time, the intended target was chromium (snap).

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: gnome-shell 44.0-2ubuntu3
  ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
  Uname: Linux 6.2.0-20-generic x86_64
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Fri May 26 11:57:45 2023
  DisplayManager: gdm3
  InstallationDate: Installed on 2019-06-18 (1438 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=tmux-256color
   XDG_RUNTIME_DIR=
  RelatedPackageVersions: mutter-common 44.0-2ubuntu4.23.04.1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to lunar on 2023-05-09 (17 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2020904/+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 2020904] Re: gnome-shell segfault when dragging a link from firefox

2023-05-26 Thread Kai Groner

apport information

** Tags added: apport-collected

** Description changed:

  This has happened to me twice in the last 24h.
  
  I was dragging a link from firefox to another application.  The crash
  occurs before I release the mouse button to drop the link in the second
  application. In both cases the drag was across two displays.  The first
  time, the intended target was wezterm (deb).  The second time, the
  intended target was chromium (snap).
  
  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: gnome-shell 44.0-2ubuntu3
  ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
  Uname: Linux 6.2.0-20-generic x86_64
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Fri May 26 11:57:45 2023
  DisplayManager: gdm3
  InstallationDate: Installed on 2019-06-18 (1438 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=tmux-256color
   XDG_RUNTIME_DIR=
  RelatedPackageVersions: mutter-common 44.0-2ubuntu4.23.04.1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to lunar on 2023-05-09 (17 days ago)
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.26.1-0ubuntu2
+ Architecture: amd64
+ CasperMD5CheckResult: unknown
+ CurrentDesktop: ubuntu:GNOME
+ DisplayManager: gdm3
+ DistroRelease: Ubuntu 23.04
+ InstallationDate: Installed on 2019-06-18 (1438 days ago)
+ InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
+ Package: gnome-shell 44.0-2ubuntu3
+ PackageArchitecture: amd64
+ ProcEnviron:
+  LANG=en_US.UTF-8
+  PATH=(custom, user)
+  SHELL=/bin/bash
+  TERM=tmux-256color
+  XDG_RUNTIME_DIR=
+ ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
+ RelatedPackageVersions: mutter-common 44.0-2ubuntu4.23.04.1
+ Tags:  lunar wayland-session
+ Uname: Linux 6.2.0-20-generic x86_64
+ UpgradeStatus: Upgraded to lunar on 2023-05-09 (17 days ago)
+ UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo wireshark
+ _MarkForUpload: True

** Attachment added: "Dependencies.txt"
   
https://bugs.launchpad.net/bugs/2020904/+attachment/5675897/+files/Dependencies.txt

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

Title:
  gnome-shell segfault when dragging a link from firefox

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  This has happened to me twice in the last 24h.

  I was dragging a link from firefox to another application.  The crash
  occurs before I release the mouse button to drop the link in the
  second application. In both cases the drag was across two displays.
  The first time, the intended target was wezterm (deb).  The second
  time, the intended target was chromium (snap).

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: gnome-shell 44.0-2ubuntu3
  ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
  Uname: Linux 6.2.0-20-generic x86_64
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Fri May 26 11:57:45 2023
  DisplayManager: gdm3
  InstallationDate: Installed on 2019-06-18 (1438 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=tmux-256color
   XDG_RUNTIME_DIR=
  RelatedPackageVersions: mutter-common 44.0-2ubuntu4.23.04.1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to lunar on 2023-05-09 (17 days ago)
  --- 
  ProblemType: Bug
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 23.04
  InstallationDate: Installed on 2019-06-18 (1438 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  Package: gnome-shell 44.0-2ubuntu3
  PackageArchitecture: amd64
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, user)
   SHELL=/bin/bash
   TERM=tmux-256color
   XDG_RUNTIME_DIR=
  ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
  RelatedPackageVersions: mutter-common 44.0-2ubuntu4.23.04.1
  Tags:  lunar wayland-session
  Uname: Linux 6.2.0-20-generic x86_64
  UpgradeStatus: Upgraded to lunar on 2023-05-09 (17 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo wireshark
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2020904/+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 2020904] ShellJournal.txt

2023-05-26 Thread Kai Groner

apport information

** Attachment added: "ShellJournal.txt"
   
https://bugs.launchpad.net/bugs/2020904/+attachment/5675900/+files/ShellJournal.txt

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

Title:
  gnome-shell segfault when dragging a link from firefox

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  This has happened to me twice in the last 24h.

  I was dragging a link from firefox to another application.  The crash
  occurs before I release the mouse button to drop the link in the
  second application. In both cases the drag was across two displays.
  The first time, the intended target was wezterm (deb).  The second
  time, the intended target was chromium (snap).

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: gnome-shell 44.0-2ubuntu3
  ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
  Uname: Linux 6.2.0-20-generic x86_64
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Fri May 26 11:57:45 2023
  DisplayManager: gdm3
  InstallationDate: Installed on 2019-06-18 (1438 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=tmux-256color
   XDG_RUNTIME_DIR=
  RelatedPackageVersions: mutter-common 44.0-2ubuntu4.23.04.1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to lunar on 2023-05-09 (17 days ago)
  --- 
  ProblemType: Bug
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 23.04
  InstallationDate: Installed on 2019-06-18 (1438 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  Package: gnome-shell 44.0-2ubuntu3
  PackageArchitecture: amd64
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, user)
   SHELL=/bin/bash
   TERM=tmux-256color
   XDG_RUNTIME_DIR=
  ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
  RelatedPackageVersions: mutter-common 44.0-2ubuntu4.23.04.1
  Tags:  lunar wayland-session
  Uname: Linux 6.2.0-20-generic x86_64
  UpgradeStatus: Upgraded to lunar on 2023-05-09 (17 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo wireshark
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2020904/+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 2020904] GsettingsChanges.txt

2023-05-26 Thread Kai Groner

apport information

** Attachment added: "GsettingsChanges.txt"
   
https://bugs.launchpad.net/bugs/2020904/+attachment/5675898/+files/GsettingsChanges.txt

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

Title:
  gnome-shell segfault when dragging a link from firefox

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  This has happened to me twice in the last 24h.

  I was dragging a link from firefox to another application.  The crash
  occurs before I release the mouse button to drop the link in the
  second application. In both cases the drag was across two displays.
  The first time, the intended target was wezterm (deb).  The second
  time, the intended target was chromium (snap).

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: gnome-shell 44.0-2ubuntu3
  ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
  Uname: Linux 6.2.0-20-generic x86_64
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Fri May 26 11:57:45 2023
  DisplayManager: gdm3
  InstallationDate: Installed on 2019-06-18 (1438 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=tmux-256color
   XDG_RUNTIME_DIR=
  RelatedPackageVersions: mutter-common 44.0-2ubuntu4.23.04.1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to lunar on 2023-05-09 (17 days ago)
  --- 
  ProblemType: Bug
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 23.04
  InstallationDate: Installed on 2019-06-18 (1438 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  Package: gnome-shell 44.0-2ubuntu3
  PackageArchitecture: amd64
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, user)
   SHELL=/bin/bash
   TERM=tmux-256color
   XDG_RUNTIME_DIR=
  ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
  RelatedPackageVersions: mutter-common 44.0-2ubuntu4.23.04.1
  Tags:  lunar wayland-session
  Uname: Linux 6.2.0-20-generic x86_64
  UpgradeStatus: Upgraded to lunar on 2023-05-09 (17 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo wireshark
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2020904/+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 2020904] ProcCpuinfoMinimal.txt

2023-05-26 Thread Kai Groner

apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/2020904/+attachment/5675899/+files/ProcCpuinfoMinimal.txt

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

Title:
  gnome-shell segfault when dragging a link from firefox

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  This has happened to me twice in the last 24h.

  I was dragging a link from firefox to another application.  The crash
  occurs before I release the mouse button to drop the link in the
  second application. In both cases the drag was across two displays.
  The first time, the intended target was wezterm (deb).  The second
  time, the intended target was chromium (snap).

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: gnome-shell 44.0-2ubuntu3
  ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
  Uname: Linux 6.2.0-20-generic x86_64
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Fri May 26 11:57:45 2023
  DisplayManager: gdm3
  InstallationDate: Installed on 2019-06-18 (1438 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=tmux-256color
   XDG_RUNTIME_DIR=
  RelatedPackageVersions: mutter-common 44.0-2ubuntu4.23.04.1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to lunar on 2023-05-09 (17 days ago)
  --- 
  ProblemType: Bug
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 23.04
  InstallationDate: Installed on 2019-06-18 (1438 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  Package: gnome-shell 44.0-2ubuntu3
  PackageArchitecture: amd64
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, user)
   SHELL=/bin/bash
   TERM=tmux-256color
   XDG_RUNTIME_DIR=
  ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
  RelatedPackageVersions: mutter-common 44.0-2ubuntu4.23.04.1
  Tags:  lunar wayland-session
  Uname: Linux 6.2.0-20-generic x86_64
  UpgradeStatus: Upgraded to lunar on 2023-05-09 (17 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo wireshark
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2020904/+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 2020904] monitors.xml.txt

2023-05-26 Thread Kai Groner

apport information

** Attachment added: "monitors.xml.txt"
   
https://bugs.launchpad.net/bugs/2020904/+attachment/5675901/+files/monitors.xml.txt

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

Title:
  gnome-shell segfault when dragging a link from firefox

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  This has happened to me twice in the last 24h.

  I was dragging a link from firefox to another application.  The crash
  occurs before I release the mouse button to drop the link in the
  second application. In both cases the drag was across two displays.
  The first time, the intended target was wezterm (deb).  The second
  time, the intended target was chromium (snap).

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: gnome-shell 44.0-2ubuntu3
  ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
  Uname: Linux 6.2.0-20-generic x86_64
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Fri May 26 11:57:45 2023
  DisplayManager: gdm3
  InstallationDate: Installed on 2019-06-18 (1438 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=tmux-256color
   XDG_RUNTIME_DIR=
  RelatedPackageVersions: mutter-common 44.0-2ubuntu4.23.04.1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to lunar on 2023-05-09 (17 days ago)
  --- 
  ProblemType: Bug
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 23.04
  InstallationDate: Installed on 2019-06-18 (1438 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  Package: gnome-shell 44.0-2ubuntu3
  PackageArchitecture: amd64
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, user)
   SHELL=/bin/bash
   TERM=tmux-256color
   XDG_RUNTIME_DIR=
  ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
  RelatedPackageVersions: mutter-common 44.0-2ubuntu4.23.04.1
  Tags:  lunar wayland-session
  Uname: Linux 6.2.0-20-generic x86_64
  UpgradeStatus: Upgraded to lunar on 2023-05-09 (17 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo wireshark
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2020904/+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 2020904] Re: gnome-shell segfault when dragging a link from firefox

2023-05-26 Thread Kai Groner

This appears to be the same as #2012100.

meta_wayland_compositor_get_context (compositor=0x0) at 
../src/wayland/meta-wayland.c:863
display_from_offer (offer=0x55e903542650) at 
../src/wayland/meta-wayland-data-offer.c:45
data_offer_receive (client=, resource=, 
mime_type=0x55e903b084dc "text/uri-list", fd=105) at 
../src/wayland/meta-wayland-data-offer.c:97
ffi_call_unix64 () at ../src/x86/unix64.S:104
ffi_call_int (cif=cif@entry=0x7ffca9966770, fn=, 
rvalue=, avalue=, closure=closure@entry=0x0) at 
../src/x86/ffi64.c:673

Is it a good idea to try the fix from gnome-shell/lunar-proposed?

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

Title:
  gnome-shell segfault when dragging a link from firefox

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  This has happened to me twice in the last 24h.

  I was dragging a link from firefox to another application.  The crash
  occurs before I release the mouse button to drop the link in the
  second application. In both cases the drag was across two displays.
  The first time, the intended target was wezterm (deb).  The second
  time, the intended target was chromium (snap).

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: gnome-shell 44.0-2ubuntu3
  ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
  Uname: Linux 6.2.0-20-generic x86_64
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Fri May 26 11:57:45 2023
  DisplayManager: gdm3
  InstallationDate: Installed on 2019-06-18 (1438 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=tmux-256color
   XDG_RUNTIME_DIR=
  RelatedPackageVersions: mutter-common 44.0-2ubuntu4.23.04.1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to lunar on 2023-05-09 (17 days ago)
  --- 
  ProblemType: Bug
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 23.04
  InstallationDate: Installed on 2019-06-18 (1438 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  Package: gnome-shell 44.0-2ubuntu3
  PackageArchitecture: amd64
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, user)
   SHELL=/bin/bash
   TERM=tmux-256color
   XDG_RUNTIME_DIR=
  ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
  RelatedPackageVersions: mutter-common 44.0-2ubuntu4.23.04.1
  Tags:  lunar wayland-session
  Uname: Linux 6.2.0-20-generic x86_64
  UpgradeStatus: Upgraded to lunar on 2023-05-09 (17 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo wireshark
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2020904/+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 2012100] Re: gnome-shell crashed with SIGSEGV in meta_wayland_compositor_get_context() from display_from_offer() from data_offer_receive() from ffi_call_unix64()

2023-05-26 Thread Kai Groner

I see gnome-shell and mutter 44.1 packages in lunar-proposed.

Is it a good idea to give them a try?

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

Title:
  gnome-shell crashed with SIGSEGV in
  meta_wayland_compositor_get_context() from display_from_offer() from
  data_offer_receive() from ffi_call_unix64()

Status in Mutter:
  Fix Released
Status in mutter package in Ubuntu:
  Fix Released
Status in mutter source package in Lunar:
  Fix Committed
Status in mutter source package in Mantic:
  Fix Released

Bug description:
  https://errors.ubuntu.com/problem/d525586b43c9aeae86d5c9c7bb28ba925afb

  I have this error when I'm connecting to nym-connect (nymtech.net)

  ProblemType: Crash
  DistroRelease: Ubuntu 23.04
  Package: gnome-shell 44~beta-1ubuntu1
  Uname: Linux 5.19.0-21-generic x86_64
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar 17 18:10:09 2023
  ExecutablePath: /usr/bin/gnome-shell
  ExecutableTimestamp: 1677216555
  ProcCmdline: /usr/bin/gnome-shell
  ProcCwd: /home/judemont
  ProcEnviron:
   LANG=fr_FR.UTF-8
   PATH=(custom, user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  Signal: 11
  SourcePackage: gnome-shell
  UserGroups: adm cdrom dip lpadmin plugdev sudo users

To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/2012100/+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 2018538] Re: All PDFs when printed come out mirror image

2023-05-26 Thread Ondrej Maly

** Attachment added: "QL-800.ppd"
   
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/2018538/+attachment/5675905/+files/QL-800.ppd

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

Title:
  All PDFs when printed come out mirror image

Status in cups package in Ubuntu:
  Incomplete

Bug description:
  Since updating to Ubuntu 23.04.  Whenever I try to print a PDF
  (regardless of application the PDF is open in) it will print the PDF
  in mirror image.

  If I enable printing mirror image in the settings, every other page
  become mirror image as instead. (I'm printing double sided/long edge
  print, so one side is normal and the other side becomes mirror image
  when I do this).

  I'm trying to print to a HP Colour LaserJet CP2025dn

  Note: If I print from my second device when it was running Ubuntu
  22.10 it would print normally, but as soon as I updated it to 23.04,
  it started having the same issue as well.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: ubiquity (not installed)
  ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
  Uname: Linux 6.2.0-20-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May  4 20:31:48 2023
  InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed 
maybe-ubiquity quiet splash ---
  InstallationDate: Installed on 2022-10-22 (194 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020)
  SourcePackage: ubiquity
  Symptom: installation
  UpgradeStatus: Upgraded to lunar on 2023-04-21 (13 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/2018538/+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 2018538] Re: All PDFs when printed come out mirror image

2023-05-26 Thread Ondrej Maly

** Attachment added: "QL-800.error_log"
   
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/2018538/+attachment/5675906/+files/QL-800.error_log

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

Title:
  All PDFs when printed come out mirror image

Status in cups package in Ubuntu:
  Incomplete

Bug description:
  Since updating to Ubuntu 23.04.  Whenever I try to print a PDF
  (regardless of application the PDF is open in) it will print the PDF
  in mirror image.

  If I enable printing mirror image in the settings, every other page
  become mirror image as instead. (I'm printing double sided/long edge
  print, so one side is normal and the other side becomes mirror image
  when I do this).

  I'm trying to print to a HP Colour LaserJet CP2025dn

  Note: If I print from my second device when it was running Ubuntu
  22.10 it would print normally, but as soon as I updated it to 23.04,
  it started having the same issue as well.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: ubiquity (not installed)
  ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
  Uname: Linux 6.2.0-20-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May  4 20:31:48 2023
  InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed 
maybe-ubiquity quiet splash ---
  InstallationDate: Installed on 2022-10-22 (194 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020)
  SourcePackage: ubiquity
  Symptom: installation
  UpgradeStatus: Upgraded to lunar on 2023-04-21 (13 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/2018538/+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 1966413] Re: --no-oem option is broken

2023-05-26 Thread Launchpad Bug Tracker

This bug was fixed in the package ubuntu-drivers-common - 1:0.9.7.2

---
ubuntu-drivers-common (1:0.9.7.2) mantic; urgency=medium

  [ Olivier Gayot ]
  * ubuntu-drivers:
- Fix --no-oem option stored in wrong config variable (LP: #1966413).

 -- Alberto Milone   Fri, 26 May 2023
14:17:38 +

** Changed in: ubuntu-drivers-common (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  --no-oem option is broken

Status in ubuntu-drivers-common package in Ubuntu:
  Fix Released

Bug description:
  [Impact]
  * ubuntu-drivers supports the --no-oem option, which is meant to filter-out 
the OEM metapackages when running on certified hardware.

  * When ubuntu-drivers is invoked with --no-oem as a global option (i.e., 
`ubuntu-drivers --no-oem list` or `ubuntu-drivers --no-oem install`, the script 
crashes with the following exception:
    NameError: name 'install_oem_meta' is not defined

  * When ubuntu-drivers is invoked with --no-oem as a sub-option of
  "install" (i.e., `ubuntu-drivers install --no-oem`), the script does
  not crash but the option is silently ignored - resulting in an OEM
  metapackage to be installed if we are running on certified hardware.
  This defeats the purpose of the option.

  * Today, the --no-oem option can be passed to ubuntu-drivers by ubiquity as a 
suboption of `ubuntu-drivers install`. By default, the option is not passed to 
ubuntu-drivers but the users can opt-in using preseeds. If they do, their 
decision is essentially ignored since the OEM metapackage will still be 
installed:
  https://git.launchpad.net/ubiquity/tree/scripts/simple-plugins#n20

  * As part of the 23.10 cycle, subiquity will start replacing the
  functionality from ubiquity for OEM installs. At the moment, subiquity
  relies on the version of ubuntu-drivers-common from the system being
  installed. But going forward, we might have to ship ubuntu-drivers-
  common in the subiquity snap. This means we will fetch the deb from
  jammy-updates since subiquity is a core22-based snap.

  [Test plan]
  1. We will compare the result of the following commands with and without the 
patch (both on certified and on un-certified hardware):
    * ubuntu-drivers --no-oem list
    -> crashes without the patch. Should not crash with the patch. The list 
returned should not include the OEM metapackage.
    * ubuntu-drivers --no-oem install
    -> crashes without the patch. Should not crash with the patch. The list 
of packages installed should not include the OEM metapackage.
    * ubuntu-drivers install --no-oem
    -> without the patch, the OEM metapackage gets installed on certified 
hardware. With the patch, it should not.

  2. We will ensure ubiquity stills manages to install ubuntu on
  certified hardware. We will also ensure that the OEM metapackage does
  not get installed when it should not.

  [Where problems could occur]
  * When used as a global option, --no-oem currently makes the script crash 
unconditionally. Therefore, the change should be very low risk in that regard.
  * When used as a suboption of "install", the --no-oem option currently gets 
ignored silently. If people have been automating ubuntu deployment in one way 
or another and have used --no-oem, they might be surprised to notice that fewer 
packages get installed on their target system, after the option is fixed. This 
is theoretically a good thing, but might require some adjustments on their end.

  [Original description]
  $ ubuntu-drivers --no-oem install
  Traceback (most recent call last):
    File "/usr/bin/ubuntu-drivers", line 490, in 
  greet()
    File "/usr/lib/python3/dist-packages/click/core.py", line 764, in __call__
  return self.main(*args, **kwargs)
    File "/usr/lib/python3/dist-packages/click/core.py", line 717, in main
  rv = self.invoke(ctx)
    File "/usr/lib/python3/dist-packages/click/core.py", line 1134, in invoke
  Command.invoke(self, ctx)
    File "/usr/lib/python3/dist-packages/click/core.py", line 956, in invoke
  return ctx.invoke(self.callback, **ctx.params)
    File "/usr/lib/python3/dist-packages/click/core.py", line 555, in invoke
  return callback(*args, **kwargs)
    File "/usr/lib/python3/dist-packages/click/decorators.py", line 64, in 
new_func
  return ctx.invoke(f, obj, *args, **kwargs)
    File "/usr/lib/python3/dist-packages/click/core.py", line 555, in invoke
  return callback(*args, **kwargs)
    File "/usr/bin/ubuntu-drivers", line 376, in greet
  config.no_oem = install_oem_meta
  NameError: name 'install_oem_meta' is not defined

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubuntu-drivers-common 1:0.9.0~0.20.04.1
  ProcVersionSignature: Ubuntu 5.13.0-37.42~20.04.1-generic 5.13.19
  Uname: Linux 5.13.0-37-generic x86_64
  ApportVersio

[Desktop-packages] [Bug 1798166] Re: “Mouse battery low” notification can't be disabled

2023-05-26 Thread lsutiger

echo $XDG_CURRENT_DESKTOP
GNOME-Flashback:GNOME
OS is Ubuntu 20.04.6 LTS
I am still having this problem.

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

Title:
  “Mouse battery low” notification can't be disabled

Status in gnome-settings-daemon package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Invalid

Bug description:
  https://gitlab.gnome.org/GNOME/gnome-settings-daemon/issues/108

  ---

  I have a wireless mouse powered by non-rechargeable battery. The mouse
  works absolutely fine even with low battery level. Problem is, Ubuntu
  gives notifications about the battery level all the time.

  I have had this issue for almost two months now, and mouse is working
  perfectly. I had to click away the notification almost every time I
  moved the mouse. I was then able to make the notifications appear less
  frequently, but the notification still always appear after some
  interval, and always after I log in.

  Here are some specific things I have tried, they have not helped.

  https://askubuntu.com/questions/1071406/how-to-disable-mouse-battery-
  low-notification-in-ubuntu-18-04

  1)
  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04

  2)
  I assume the packet in question is notify-osd, not sure.
  notify-osd:
    Installed: (none)
    Candidate: 0.9.35+16.04.20160415-0ubuntu2
    Version table:
   0.9.35+16.04.20160415-0ubuntu2 500
  500 http://fi.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages

  3) I expected that no notifications would appear when notifications
  are set to off

  4) Mouse battery low - notification always appears
  ---
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   ohto   2927 F...m pulseaudio
   /dev/snd/controlC0:  ohto   2927 F pulseaudio
   /dev/snd/controlC1:  ohto   2927 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-07-28 (79 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic 
root=UUID=a59cc41b-0147-4609-b6c5-75fa912d2396 ro quiet splash vt.handoff=1
  ProcVersionSignature: hostname 4.15.0-36.39-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-36-generic N/A
   linux-backports-modules-4.15.0-36-generic  N/A
   linux-firmware 1.173.1
  Tags:  bionic
  Uname: Linux 4.15.0-36-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/15/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F12
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z77X-UP5 TH-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: To be filled by O.E.M.
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF12:bd05/15/2014:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ77X-UP5TH-CF:rvrTobefilledbyO.E.M.:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1798166/+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 2013338] Re: Update nautilus to 42.6

2023-05-26 Thread Amin Bandali

Hi Steve, (all,)

Apologies for the slow reply, and thanks for accepting this into jammy-
proposed.

I've tested and I can verify that it fixes the bug per the test case
from LP: #2004475, and otherwise nautilus seems to continue work well
and as expected (I did some general testing: browsing to different
directories, opening different kinds of files, checking file and folder
properties and permissions, ...).

I experienced no problems or regressions, so I'm marking this as
verification-done-jammy.

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

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

Title:
  Update nautilus to 42.6

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

Bug description:
  Impact
  --

  This is a new stable release in the GNOME 42 series:
  https://gitlab.gnome.org/GNOME/nautilus/-/blob/42.6/NEWS

  Test Case 0
  ---

  nautilus has a build test suite that will fail the build if the tests
  fail.

  Test Case 1
  ---

  Install the update.
  Make sure that nautilus isn't running, either by logging out and logging back 
in or by running pkill nautilus.
  Run nautilus and ensure that it still works well.

  Test Case 2
  ---

  See the test case from LP: #2004475 and verify the bug is fixed with
  42.6.

  What Could Go Wrong
  ---

  nautilus is the default GUI file browser for Ubuntu Desktop.  Other
  desktop flavors use other file browsers.

  As a component of GNOME core, there is a micro-release exception for nautilus.
  https://wiki.ubuntu.com/StableReleaseUpdates/GNOME

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2013338/+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 2020814] Re: xmllint does not recognize emdash (— )

2023-05-26 Thread Thorsten Glaser

Yeah well, those portability problems were back in the 1990s when people
used latin1 or whatever codepages.

** Changed in: libxml2 (Ubuntu)
   Status: New => Invalid

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

Title:
  xmllint does not recognize emdash (—)

Status in libxml2 package in Ubuntu:
  Invalid

Bug description:
  I'm using Ubuntu 20.04.2 LTS, x85_64, fully patched. I'm using DocBook to 
build a PDF. One of the steps I use in my build script is to validate and 
format the XML using xmllint from libxml2-utils
  2.9.13+dfsg-1ubuntu0.3:

  echo "Validating book..."
  if ! xmllint --xinclude --noout --postvalid book.xml
  then
  echo "Validation failed. Exiting."
  exit 1
  fi
  echo "Complete."

  echo "Formatting source code..."
  for file in *.xml
  do
  if xmllint --format "${file}" --output "${file}.format"
  then
  mv "${file}.format" "${file}"
  fi
  done
  echo "Complete."

  When I added an emdash (—) the book failed to format:

  Validating book...
  Complete.
  Formatting source code...
  ch02.xml:58: parser error : Entity 'mdash' not defined
   injections are remediated using several methods. And two output devices 
—

 ^
  ch02.xml:58: parser error : Entity 'mdash' not defined
   methods. And two output devices — the printer and plaintext email 
—

 ^
  Complete.

  The text is:

  ... And two output devices — the printer and plaintext
  email — do not require...

  It seems like emdash should be recognized.

  -

  $ lsb_release -a
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:Ubuntu 22.04.2 LTS
  Release:22.04
  Codename:   jammy

  -

  $ xmllint --version
  xmllint: using libxml version 20913
 compiled with: Threads Tree Output Push Reader Patterns Writer SAXv1 FTP 
HTTP DTDValid HTML Legacy C14N Catalog XPath XPointer XInclude Iconv ICU 
ISO8859X Unicode Regexps Automata Schemas Schematron Modules Debug Zlib Lzma

  $ command -v xmllint
  /usr/bin/xmllint

  $ dpkg -S /usr/bin/xmllint
  libxml2-utils: /usr/bin/xmllint

  $ apt-cache show libxml2-utils
  Package: libxml2-utils
  Architecture: amd64
  Version: 2.9.13+dfsg-1ubuntu0.3
  Multi-Arch: foreign
  Priority: optional
  Section: text
  Source: libxml2
  Origin: Ubuntu
  Maintainer: Ubuntu Developers 
  Original-Maintainer: Debian XML/SGML Group 

  Bugs: https://bugs.launchpad.net/ubuntu/+filebug
  Installed-Size: 202
  Depends: libc6 (>= 2.34), libxml2 (>= 2.9.0)
  Filename: 
pool/main/libx/libxml2/libxml2-utils_2.9.13+dfsg-1ubuntu0.3_amd64.deb
  Size: 40192
  MD5sum: 3ca7de07562010fcaabf255ea8fea9c4
  SHA1: 128a9cfaff49e85f2ab08578f389eecb21f17766
  SHA256: c279c07caf909545e2cedb7845b5ac652e0a70f9784e5faf799a1a01441b4649
  SHA512: 
51600d7206c9a5568fdaeee9adddbc48962fc094cc479f4bd42c0714b3725cd3200937f8c876a897db08fc50d891005d7dbabfb6ae12ad27ad6ed416f8b6a03d
  Homepage: http://xmlsoft.org
  ...

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libxml2/+bug/2020814/+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 2020814] Re: xmllint does not recognize emdash (— )

2023-05-26 Thread Jeffrey Walton

Thorsten, a quick question...

The first part of my book build script has this:

echo "Validating book..."
if ! xmllint --xinclude --noout --postvalid book.xml
then
echo "Validation failed. Exiting."
exit 1
fi
echo "Complete."

Why did the book pass validation when using emdash entity reference? It
seems like that should have failed.

An example of the build script can be found at
https://github.com/noloader/POWER8-crypto/tree/master/docbook. make-
book.sh builds the book, and it includes the snippet.

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

Title:
  xmllint does not recognize emdash (—)

Status in libxml2 package in Ubuntu:
  Invalid

Bug description:
  I'm using Ubuntu 20.04.2 LTS, x85_64, fully patched. I'm using DocBook to 
build a PDF. One of the steps I use in my build script is to validate and 
format the XML using xmllint from libxml2-utils
  2.9.13+dfsg-1ubuntu0.3:

  echo "Validating book..."
  if ! xmllint --xinclude --noout --postvalid book.xml
  then
  echo "Validation failed. Exiting."
  exit 1
  fi
  echo "Complete."

  echo "Formatting source code..."
  for file in *.xml
  do
  if xmllint --format "${file}" --output "${file}.format"
  then
  mv "${file}.format" "${file}"
  fi
  done
  echo "Complete."

  When I added an emdash (—) the book failed to format:

  Validating book...
  Complete.
  Formatting source code...
  ch02.xml:58: parser error : Entity 'mdash' not defined
   injections are remediated using several methods. And two output devices 
—

 ^
  ch02.xml:58: parser error : Entity 'mdash' not defined
   methods. And two output devices — the printer and plaintext email 
—

 ^
  Complete.

  The text is:

  ... And two output devices — the printer and plaintext
  email — do not require...

  It seems like emdash should be recognized.

  -

  $ lsb_release -a
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:Ubuntu 22.04.2 LTS
  Release:22.04
  Codename:   jammy

  -

  $ xmllint --version
  xmllint: using libxml version 20913
 compiled with: Threads Tree Output Push Reader Patterns Writer SAXv1 FTP 
HTTP DTDValid HTML Legacy C14N Catalog XPath XPointer XInclude Iconv ICU 
ISO8859X Unicode Regexps Automata Schemas Schematron Modules Debug Zlib Lzma

  $ command -v xmllint
  /usr/bin/xmllint

  $ dpkg -S /usr/bin/xmllint
  libxml2-utils: /usr/bin/xmllint

  $ apt-cache show libxml2-utils
  Package: libxml2-utils
  Architecture: amd64
  Version: 2.9.13+dfsg-1ubuntu0.3
  Multi-Arch: foreign
  Priority: optional
  Section: text
  Source: libxml2
  Origin: Ubuntu
  Maintainer: Ubuntu Developers 
  Original-Maintainer: Debian XML/SGML Group 

  Bugs: https://bugs.launchpad.net/ubuntu/+filebug
  Installed-Size: 202
  Depends: libc6 (>= 2.34), libxml2 (>= 2.9.0)
  Filename: 
pool/main/libx/libxml2/libxml2-utils_2.9.13+dfsg-1ubuntu0.3_amd64.deb
  Size: 40192
  MD5sum: 3ca7de07562010fcaabf255ea8fea9c4
  SHA1: 128a9cfaff49e85f2ab08578f389eecb21f17766
  SHA256: c279c07caf909545e2cedb7845b5ac652e0a70f9784e5faf799a1a01441b4649
  SHA512: 
51600d7206c9a5568fdaeee9adddbc48962fc094cc479f4bd42c0714b3725cd3200937f8c876a897db08fc50d891005d7dbabfb6ae12ad27ad6ed416f8b6a03d
  Homepage: http://xmlsoft.org
  ...

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libxml2/+bug/2020814/+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 2020814] Re: xmllint does not recognize emdash (— )

2023-05-26 Thread Thorsten Glaser

Hmm. I normally use libxml2 via xmlstarlet which has a somewhat nicer UX
than xmllint.

My guess is that you didn’t give a DTD, so it could only check that all
present entities are syntactically valid, but not expand them.

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

Title:
  xmllint does not recognize emdash (—)

Status in libxml2 package in Ubuntu:
  Invalid

Bug description:
  I'm using Ubuntu 20.04.2 LTS, x85_64, fully patched. I'm using DocBook to 
build a PDF. One of the steps I use in my build script is to validate and 
format the XML using xmllint from libxml2-utils
  2.9.13+dfsg-1ubuntu0.3:

  echo "Validating book..."
  if ! xmllint --xinclude --noout --postvalid book.xml
  then
  echo "Validation failed. Exiting."
  exit 1
  fi
  echo "Complete."

  echo "Formatting source code..."
  for file in *.xml
  do
  if xmllint --format "${file}" --output "${file}.format"
  then
  mv "${file}.format" "${file}"
  fi
  done
  echo "Complete."

  When I added an emdash (—) the book failed to format:

  Validating book...
  Complete.
  Formatting source code...
  ch02.xml:58: parser error : Entity 'mdash' not defined
   injections are remediated using several methods. And two output devices 
—

 ^
  ch02.xml:58: parser error : Entity 'mdash' not defined
   methods. And two output devices — the printer and plaintext email 
—

 ^
  Complete.

  The text is:

  ... And two output devices — the printer and plaintext
  email — do not require...

  It seems like emdash should be recognized.

  -

  $ lsb_release -a
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:Ubuntu 22.04.2 LTS
  Release:22.04
  Codename:   jammy

  -

  $ xmllint --version
  xmllint: using libxml version 20913
 compiled with: Threads Tree Output Push Reader Patterns Writer SAXv1 FTP 
HTTP DTDValid HTML Legacy C14N Catalog XPath XPointer XInclude Iconv ICU 
ISO8859X Unicode Regexps Automata Schemas Schematron Modules Debug Zlib Lzma

  $ command -v xmllint
  /usr/bin/xmllint

  $ dpkg -S /usr/bin/xmllint
  libxml2-utils: /usr/bin/xmllint

  $ apt-cache show libxml2-utils
  Package: libxml2-utils
  Architecture: amd64
  Version: 2.9.13+dfsg-1ubuntu0.3
  Multi-Arch: foreign
  Priority: optional
  Section: text
  Source: libxml2
  Origin: Ubuntu
  Maintainer: Ubuntu Developers 
  Original-Maintainer: Debian XML/SGML Group 

  Bugs: https://bugs.launchpad.net/ubuntu/+filebug
  Installed-Size: 202
  Depends: libc6 (>= 2.34), libxml2 (>= 2.9.0)
  Filename: 
pool/main/libx/libxml2/libxml2-utils_2.9.13+dfsg-1ubuntu0.3_amd64.deb
  Size: 40192
  MD5sum: 3ca7de07562010fcaabf255ea8fea9c4
  SHA1: 128a9cfaff49e85f2ab08578f389eecb21f17766
  SHA256: c279c07caf909545e2cedb7845b5ac652e0a70f9784e5faf799a1a01441b4649
  SHA512: 
51600d7206c9a5568fdaeee9adddbc48962fc094cc479f4bd42c0714b3725cd3200937f8c876a897db08fc50d891005d7dbabfb6ae12ad27ad6ed416f8b6a03d
  Homepage: http://xmlsoft.org
  ...

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libxml2/+bug/2020814/+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 1993214] Re: [jammy] Update gjs to 1.74 using mozjs102 102.3

2023-05-26 Thread Steve Langasek

This appears to be covered by the GNOME SRU exception.  However, the bug
description does not reference this exception, and also does not follow
the template at
.  Please
update accordingly.

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

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

Title:
  [jammy] Update gjs to 1.74 using mozjs102 102.3

Status in gjs package in Ubuntu:
  Fix Released
Status in mozjs102 package in Ubuntu:
  Fix Released
Status in gjs source package in Jammy:
  Incomplete
Status in mozjs102 source package in Jammy:
  Fix Committed
Status in mozjs102 source package in Kinetic:
  Fix Committed

Bug description:
  Impact
  --
  GNOME Shell uses the SpiderMonkey JavaScript engine from Firefox ESR (mozjs). 
Firefox 92 ESR has reached end of life; therefore, we should switch to the 102 
ESR series for security updates for the next year.

  This requires updating gjs from 1.72 to 1.74 from GNOME 43, as
  packaged in Ubuntu 22.10.

  This will be done as a Security Update.

  Updating mozjs in stable Ubuntu releases was recommended when Ubuntu
  first switched back to GNOME, but this is the first time it's been
  done.

  Security Impact
  ---
  I looked through
  https://github.com/mozilla/gecko-dev/commits/esr102/js
  and searched for referenced bug numbers in
  https://www.mozilla.org/en-US/security/advisories/
  for Firefox ESR releases since Ubuntu's 91.10

  and found one CVE. Also, there's the vague Mozilla Bug 1771084 (no CVE
  issued) mentioned at

  https://www.mozilla.org/en-US/security/advisories/mfsa2022-24/

  Uploaded Packages
  -
  We will introduce mozjs102, a new source package for Ubuntu 22.04 LTS, being 
careful to publish it in main, not universe.
  And we'll update gjs.
  No other packages need to be updated for this change.
  mozjs91 will remain in Ubuntu 22.04 LTS (source package removals are 
generally not possible), but nothing else in Ubuntu uses it.

  Test Case
  -
  https://wiki.ubuntu.com/DesktopTeam/TestPlans/gjs

  Security Sponsoring
  ---
  sudo apt install git-buildpackage
  gbp clone https://salsa.debian.org/gnome-team/gjs
  cd gjs
  git checkout ubuntu/jammy
  gbp buildpackage --git-builder="debuild -S -nc"

  mkdir ../tarballs; cd ../tarballs
  pull-lp-source mozjs102 kinetic
  cd ..
  gbp clone https://salsa.debian.org/gnome-team/mozjs
  cd mozjs
  git checkout ubuntu/102/jammy
  gbp buildpackage --git-builder="debuild --no-lintian -S -nc" 
--git-tarball-dir=../tarballs
  # That avoids needing to recreate the original tarball from pristine-tar 
which takes a while. Also, running lintian takes a while.

  Initial Testing Done
  
  I built the packages in my PPA.
  I installed the packages on Ubuntu 22.04 LTS and successfully completed the 
Test Case.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/1993214/+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 2020604] Re: After mesa upgrades, Chrome won't show graphics

2023-05-26 Thread Chris Hall

Well, on one of my machines I installed Mesa from the kisak more stable 
ppa ("turtle"), which is more up to date than mesa from the jammy 
repository. I was able to re-enable hardware acceleration with no 
problems. So there is something in the whole collection of mesa packages 
that broke several chromium based browsers.

On 5/26/23 11:14 AM, Nathan Teodosio wrote:
>> Any idea if the mesa driver
>> problem will be addressed in the next update?
> Time will tell, if my reading of #12 is correct then this isn't really a
> problem with Mesa but with upstream.
>
>> An ironic thing about the about://gpu url is that unless you disable the
>> gpu, it's not possible to even read  the url. A real chicken and egg
>> problem.
> One could do a blind
>
> Ctrl+L
> about:gpu
> 
> 
>
> to get the report to clipboard, but you would never know that without
> seeing the page. (:
>
> That information isn't otherwise available even with
> --enable-logging=stderr --v=1...
>

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

Title:
  After mesa upgrades, Chrome won't show graphics

Status in chromium-browser package in Ubuntu:
  Fix Committed
Status in mesa package in Ubuntu:
  Triaged

Bug description:
  After today's Ubuntu 22.04 mesa upgrades many of our users reported
  problems viewing graphics when using Google Chrome (Stable).

  The mesa upgrades we installed were:

  [UPGRADE] libegl-mesa0:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 
22.2.5-0ubuntu0.1~22.04.2
  [UPGRADE] libegl1-mesa:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 
22.2.5-0ubuntu0.1~22.04.2
  [UPGRADE] libgl1-mesa-dri:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 
22.2.5-0ubuntu0.1~22.04.2
  [UPGRADE] libgl1-mesa-glx:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 
22.2.5-0ubuntu0.1~22.04.2
  [UPGRADE] libglapi-mesa:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 
22.2.5-0ubuntu0.1~22.04.2
  [UPGRADE] libglx-mesa0:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 
22.2.5-0ubuntu0.1~22.04.2
  [UPGRADE] mesa-vulkan-drivers:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 
22.2.5-0ubuntu0.1~22.04.2

  We documented the problem in AskUbuntu before we realized it was
  probably related to mesa, so wanted to link to that report here:

  https://askubuntu.com/questions/1469116/since-23-may-2023-ubuntu-22-04-mesa-
  updates-chrome-wont-display-website-graphi

  There are several useful pointers and bypasses listed in that
  AskUbuntu link (one being to remove affected users' GPUCache
  directories, which does not destroy their profiles and seems to work
  in many but not all cases).

  Not sure if this is an issue with mesa or Chrome or specific machine
  graphics or an interaction between them.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2020604/+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 2013235]

2023-05-26 Thread Jean-Baptiste Mardelle

*** Bug 470255 has been marked as a duplicate of this bug. ***

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

Title:
  Drag and Drop not working in Qt-Applications on Gnome 44

Status in Kdenlive:
  Invalid
Status in Mutter:
  Fix Released
Status in mutter package in Ubuntu:
  Fix Committed

Bug description:
  Drag and drop items within Qt applications not working since upgrade
  to Ubuntu Lunar developmental release. The items can be picked up then
  the cursor changed to the "forbid" sign and no further interaction to
  the app.

  Confirmed affected apps: 3d Slicer, Krita.

  Upstream bug report:
  https://gitlab.gnome.org/GNOME/mutter/-/issues/2715

To manage notifications about this bug go to:
https://bugs.launchpad.net/kdenlive/+bug/2013235/+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 2013235]

2023-05-26 Thread Jean-Baptiste Mardelle

As reported, this is caused by a bug in mutter affecting all Qt Apps:
https://gitlab.gnome.org/GNOME/mutter/-/issues/2715

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

Title:
  Drag and Drop not working in Qt-Applications on Gnome 44

Status in Kdenlive:
  Invalid
Status in Mutter:
  Fix Released
Status in mutter package in Ubuntu:
  Fix Committed

Bug description:
  Drag and drop items within Qt applications not working since upgrade
  to Ubuntu Lunar developmental release. The items can be picked up then
  the cursor changed to the "forbid" sign and no further interaction to
  the app.

  Confirmed affected apps: 3d Slicer, Krita.

  Upstream bug report:
  https://gitlab.gnome.org/GNOME/mutter/-/issues/2715

To manage notifications about this bug go to:
https://bugs.launchpad.net/kdenlive/+bug/2013235/+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 2013235]

2023-05-26 Thread Jean-Baptiste Mardelle

*** This bug has been marked as a duplicate of bug 469961 ***

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

Title:
  Drag and Drop not working in Qt-Applications on Gnome 44

Status in Kdenlive:
  Invalid
Status in Mutter:
  Fix Released
Status in mutter package in Ubuntu:
  Fix Committed

Bug description:
  Drag and drop items within Qt applications not working since upgrade
  to Ubuntu Lunar developmental release. The items can be picked up then
  the cursor changed to the "forbid" sign and no further interaction to
  the app.

  Confirmed affected apps: 3d Slicer, Krita.

  Upstream bug report:
  https://gitlab.gnome.org/GNOME/mutter/-/issues/2715

To manage notifications about this bug go to:
https://bugs.launchpad.net/kdenlive/+bug/2013235/+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 2013235] Re: Drag and Drop not working in Qt-Applications on Gnome 44

2023-05-26 Thread Bug Watch Updater

** Changed in: kdenlive
   Status: Incomplete => Invalid

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

Title:
  Drag and Drop not working in Qt-Applications on Gnome 44

Status in Kdenlive:
  Invalid
Status in Mutter:
  Fix Released
Status in mutter package in Ubuntu:
  Fix Committed

Bug description:
  Drag and drop items within Qt applications not working since upgrade
  to Ubuntu Lunar developmental release. The items can be picked up then
  the cursor changed to the "forbid" sign and no further interaction to
  the app.

  Confirmed affected apps: 3d Slicer, Krita.

  Upstream bug report:
  https://gitlab.gnome.org/GNOME/mutter/-/issues/2715

To manage notifications about this bug go to:
https://bugs.launchpad.net/kdenlive/+bug/2013235/+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 2020604] Re: After Mesa upgrades, Chrome won't show graphics

2023-05-26 Thread Sam

** Summary changed:

- After mesa upgrades, Chrome won't show graphics
+ After Mesa upgrades, Chrome won't show graphics

** Description changed:

- After today's Ubuntu 22.04 mesa upgrades many of our users reported
+ After today's Ubuntu 22.04 Mesa upgrades many of our users reported
  problems viewing graphics when using Google Chrome (Stable).
  
- The mesa upgrades we installed were:
+ The Mesa upgrades we installed were:
  
  [UPGRADE] libegl-mesa0:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 
22.2.5-0ubuntu0.1~22.04.2
  [UPGRADE] libegl1-mesa:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 
22.2.5-0ubuntu0.1~22.04.2
  [UPGRADE] libgl1-mesa-dri:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 
22.2.5-0ubuntu0.1~22.04.2
  [UPGRADE] libgl1-mesa-glx:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 
22.2.5-0ubuntu0.1~22.04.2
  [UPGRADE] libglapi-mesa:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 
22.2.5-0ubuntu0.1~22.04.2
  [UPGRADE] libglx-mesa0:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 
22.2.5-0ubuntu0.1~22.04.2
  [UPGRADE] mesa-vulkan-drivers:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 
22.2.5-0ubuntu0.1~22.04.2
  
  We documented the problem in AskUbuntu before we realized it was
- probably related to mesa, so wanted to link to that report here:
+ probably related to Mesa, so wanted to link to that report here:
  
  https://askubuntu.com/questions/1469116/since-23-may-2023-ubuntu-22-04-mesa-
  updates-chrome-wont-display-website-graphi
  
  There are several useful pointers and bypasses listed in that AskUbuntu
  link (one being to remove affected users' GPUCache directories, which
  does not destroy their profiles and seems to work in many but not all
  cases).
  
- Not sure if this is an issue with mesa or Chrome or specific machine
+ Not sure if this is an issue with Mesa or Chrome or specific machine
  graphics or an interaction between them.

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

Title:
  After Mesa upgrades, Chrome won't show graphics

Status in chromium-browser package in Ubuntu:
  Fix Committed
Status in mesa package in Ubuntu:
  Triaged

Bug description:
  After today's Ubuntu 22.04 Mesa upgrades many of our users reported
  problems viewing graphics when using Google Chrome (Stable).

  The Mesa upgrades we installed were:

  [UPGRADE] libegl-mesa0:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 
22.2.5-0ubuntu0.1~22.04.2
  [UPGRADE] libegl1-mesa:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 
22.2.5-0ubuntu0.1~22.04.2
  [UPGRADE] libgl1-mesa-dri:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 
22.2.5-0ubuntu0.1~22.04.2
  [UPGRADE] libgl1-mesa-glx:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 
22.2.5-0ubuntu0.1~22.04.2
  [UPGRADE] libglapi-mesa:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 
22.2.5-0ubuntu0.1~22.04.2
  [UPGRADE] libglx-mesa0:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 
22.2.5-0ubuntu0.1~22.04.2
  [UPGRADE] mesa-vulkan-drivers:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 
22.2.5-0ubuntu0.1~22.04.2

  We documented the problem in AskUbuntu before we realized it was
  probably related to Mesa, so wanted to link to that report here:

  https://askubuntu.com/questions/1469116/since-23-may-2023-ubuntu-22-04-mesa-
  updates-chrome-wont-display-website-graphi

  There are several useful pointers and bypasses listed in that
  AskUbuntu link (one being to remove affected users' GPUCache
  directories, which does not destroy their profiles and seems to work
  in many but not all cases).

  Not sure if this is an issue with Mesa or Chrome or specific machine
  graphics or an interaction between them.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2020604/+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 2021366] [NEW] strange window focus across multiple workspaces

2023-05-26 Thread Steve Langasek

Public bug reported:

On my system, I use multiple workspaces across multiple monitors.  (I
don't at this point remember how I configured multiple workspaces; I
know it's not in the default gnome-settings UI anymore, I thought I had
configured it via gnome-tweaks but I also don't find it in gnome-tweaks
today.)

In kinetic, the behavior was that when switching between workspaces,
only windows on the primary display would swap; windows on the secondary
display would persist across workspaces.  Weird, unexpected, but ok I
adapted and made use of it.

In lunar, the behavior is the same *except* that when switching
workspaces, instead of the window focus returning to whichever window
was previously in the foreground on that workspace, the focus jumps to
the window on the secondary display.  This is unexpected and unhelpful.

ProblemType: Bug
DistroRelease: Ubuntu 23.04
Package: gnome-shell 44.0-2ubuntu3
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
ApportVersion: 2.26.1-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Fri May 26 22:20:02 2023
DisplayManager: gdm3
InstallationDate: Installed on 2019-12-23 (1250 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
RebootRequiredPkgs: Error: path contained symlinks.
RelatedPackageVersions: mutter-common 44.0-2ubuntu4
SourcePackage: gnome-shell
UpgradeStatus: Upgraded to lunar on 2023-05-11 (15 days ago)

** Affects: gnome-shell (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 gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/2021366

Title:
  strange window focus across multiple workspaces

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  On my system, I use multiple workspaces across multiple monitors.  (I
  don't at this point remember how I configured multiple workspaces; I
  know it's not in the default gnome-settings UI anymore, I thought I
  had configured it via gnome-tweaks but I also don't find it in gnome-
  tweaks today.)

  In kinetic, the behavior was that when switching between workspaces,
  only windows on the primary display would swap; windows on the
  secondary display would persist across workspaces.  Weird, unexpected,
  but ok I adapted and made use of it.

  In lunar, the behavior is the same *except* that when switching
  workspaces, instead of the window focus returning to whichever window
  was previously in the foreground on that workspace, the focus jumps to
  the window on the secondary display.  This is unexpected and
  unhelpful.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: gnome-shell 44.0-2ubuntu3
  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
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Fri May 26 22:20:02 2023
  DisplayManager: gdm3
  InstallationDate: Installed on 2019-12-23 (1250 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions: mutter-common 44.0-2ubuntu4
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to lunar on 2023-05-11 (15 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2021366/+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

43 matches

Mail list logo