date:20230113

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

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

-- 
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:
  Fix Committed
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

[Desktop-packages] [Bug 1993214] Re: [jammy] Update gjs to 1.74 using mozjs102 102.3

2023-01-13 Thread Steve Langasek

Hello Jeremy, or anyone else affected,

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

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

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

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

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

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

** Tags added: verification-needed-kinetic

-- 
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:
  Confirmed
Status in mozjs102 package in Ubuntu:
  Confirmed
Status in gjs source package in Jammy:
  Fix Committed
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

[Desktop-packages] [Bug 1993214] Re: [jammy] Update gjs to 1.74 using mozjs102 102.3

2023-01-13 Thread Steve Langasek

Hello Jeremy, or anyone else affected,

Accepted gjs into jammy-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/gjs/1.74.0-0ubuntu1 in
a few hours, and then in the -proposed repository.

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

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

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

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

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

-- 
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:
  Confirmed
Status in mozjs102 package in Ubuntu:
  Confirmed
Status in gjs source package in Jammy:
  Fix Committed
Status in mozjs102 source package in Jammy:
  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

[Desktop-packages] [Bug 1990592] Re: Desktop environment fails to start

2023-01-13 Thread Brian Murray

I tested this today with a Lunar daily build from 20230110 and could not
recreate the issue so at least Lunar will be okay.

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

Title:
  Desktop environment fails to start

Status in xserver-xorg-video-nouveau package in Ubuntu:
  New

Bug description:
  A fresh installation of the Kinetic daily image dated 20220920 fails
  to start the graphical environment when using the nouveau drivers and
  I'm only able to log in on the console. The system under test is using
  QEMU w/ GPU passthrough and an NVIDIA GeForce GTX 650 device.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: xserver-xorg-video-nouveau 1:1.0.17-2build1
  ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0
  Uname: Linux 5.19.0-15-generic x86_64
  ApportVersion: 2.23.0-0ubuntu2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  Date: Thu Sep 22 16:39:27 2022
  DistUpgraded: Fresh install
  DistroCodename: kinetic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Red Hat, Inc. QXL paravirtual graphic card [1b36:0100] (rev 05) (prog-if 00 
[VGA controller])
 Subsystem: Red Hat, Inc. QEMU Virtual Machine [1af4:1100]
   NVIDIA Corporation GK107 [GeForce GTX 650] [10de:0fc6] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: eVga.com. Corp. GK107 [GeForce GTX 650] [3842:2652]
  InstallationDate: Installed on 2022-09-22 (0 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220920)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Lsusb-t:
   /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/15p, 5000M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/15p, 480M
   |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 
480M
  MachineType: QEMU Standard PC (Q35 + ICH9, 2009)
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-15-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  SourcePackage: xserver-xorg-video-nouveau
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/06/2015
  dmi.bios.release: 0.0
  dmi.bios.vendor: EFI Development Kit II / OVMF
  dmi.bios.version: 0.0.0
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-q35-6.2
  dmi.modalias: 
dmi:bvnEFIDevelopmentKitII/OVMF:bvr0.0.0:bd02/06/2015:br0.0:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-6.2:cvnQEMU:ct1:cvrpc-q35-6.2:sku:
  dmi.product.name: Standard PC (Q35 + ICH9, 2009)
  dmi.product.version: pc-q35-6.2
  dmi.sys.vendor: QEMU
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.112-3ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.1.7-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/1990592/+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-01-13 Thread Steve Langasek

Hello Jeremy, or anyone else affected,

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

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

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

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

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

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

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

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to 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:
  Confirmed
Status in mozjs102 package in Ubuntu:
  Confirmed
Status in mozjs102 source package in Jammy:
  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

[Desktop-packages] [Bug 1999308] Re: Snap keeps uninstalling apt Firefox, and reinstalling snap Firefox

2023-01-13 Thread Gordon Lack

I'm having the same problem (on multiple systems).

I've remove'd firefox as a snap nut the snap still gets installed at
some later point (when a new one is available?) despite the fact that my
apt preferences are set to use the mozillateam-ubuntu-ppa-kinetic PPA.

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

Title:
  Snap keeps uninstalling apt Firefox, and reinstalling snap Firefox

Status in firefox package in Ubuntu:
  Confirmed

Bug description:
   I have looked on various forums including the search features of
  Launchpad, help.ubuntu..com, and Google for answers on this but not been
  able to.

  I have uninstalled the snap of firefox multiple times, installing the real
  Firefox from ppa.launchpadcontent.net/mozillateam/ppa/ubuntu/, only for a
  few days later (once hours later) for snap to uninstall the real thing and
  install its snap version instead.

  I have tried a basic
 sudo snap remove firefox

  and when that didn't work
 sudo snap disable firefox
 sudo snap remove --purget firefox

  The former should be enough - that's a direct expression of my preferences,
  some thing like "You should have typed sudo snap remove --do-not-reinstall
  --disable-auto-ignore-preferences firefox"  would not resolve this bug.

  When installing using apt-get, the correct version is being installed, and
  snap afterwards does not show the presence of firefox:

  Get:1 http://us.archive.ubuntu.com/ubuntu jammy/universe amd64
  xul-ext-ubufox all 3.4-0ubuntu1.17.10.1 [3,320 B]
  Get:2 https://ppa.launchpadcontent.net/mozillateam/ppa/ubuntu jammy/main
  amd64 firefox-locale-en amd64 108.0+build2-0ubuntu0.22.04.1~mt1 [831 kB]
  Get:3 https://ppa.launchpadcontent.net/mozillateam/ppa/ubuntu jammy/main
  amd64 firefox amd64 108.0+build2-0ubuntu0.22.04.1~mt1 [64.9 MB]

  Name   Version RevTracking
  Publisher  Notes
  authy  2.2.2   12 latest/stable
 twilio-authy   -
  bare   1.0 5  latest/stable
 canonical✓ base
  chromium   108.0.5359.94   2238   latest/stable
 canonical✓ -
  code   5235c6bb114latest/stable
 vscode✓classic
  core   16-2.57.6   14399  latest/stable
 canonical✓ core
  core18 202211032632   latest/stable
 canonical✓ base
  core20 202211231738   latest/stable
 canonical✓ base
  cups   2.4.2-4 836latest/stable
 openprinting✓  -
  gnome-3-28-18043.28.0-19-g98f9e67.98f9e67  161latest/stable
 canonical✓ -
  gnome-3-38-20040+git.6f39565   119latest/stable
 canonical✓ -
  gtk-common-themes  0.1-81-g442e511 1535
  latest/stable/…  canonical✓ -
  onlyoffice-desktopeditors  7.2.1   133latest/stable
 onlyoffice✓-
  snap-store 41.3-66-gfe1e325638
   latest/stable/…  canonical✓ -
  snapd  2.57.6  17883  latest/stable
 canonical✓ snapd

  
  /var/lib/snapd/seed/snaps contains (once firefox is removed):

  core18_1880.snap  gnome-3-34-1804_36.snap  gtk-common-themes_1506.snap
   snapd_8542.snap  snap-store_467.snap

  
https://ubuntuhandbook.org/index.php/2021/10/prevent-installing-firefox-snap-ubuntu-mate-21-10/
  claims that a similar issue affects Ubuntu MATE 21.04 and the solution was
  to type "sudo apt-mark manual firefox", which I have done, but that has not
  resolved the problem.

  I'm not here to explain why I wouldn't want the snap version, it is clearly
  a bug for snap to accept a command to uninstall something and then
  automatically reinstall it days later without the permission of the user,
  and especially galling that it removes the real version at the same time.

  I have lost data (passwords and history) because of this bug, because one
  of the many faults of the snap version is that it ignores the user's real
  ~/.mozilla profile and creates a shadow profile instead inside of the snap
  system.

  Please disable this behavior. It's obnoxious, it ignores EXPLICITY stated
  user preferences, and it causes the loss of data.

  I am unclear on what package is causing the behavior so for now marking it
  against Firefox, but it could be against some other piece of infrastructure
  related to snap:

   affects ubuntu/firefox

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


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

[Desktop-packages] [Bug 1999308] Re: Snap keeps uninstalling apt Firefox, and reinstalling snap Firefox

2023-01-13 Thread Launchpad Bug Tracker

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

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

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

Title:
  Snap keeps uninstalling apt Firefox, and reinstalling snap Firefox

Status in firefox package in Ubuntu:
  Confirmed

Bug description:
   I have looked on various forums including the search features of
  Launchpad, help.ubuntu..com, and Google for answers on this but not been
  able to.

  I have uninstalled the snap of firefox multiple times, installing the real
  Firefox from ppa.launchpadcontent.net/mozillateam/ppa/ubuntu/, only for a
  few days later (once hours later) for snap to uninstall the real thing and
  install its snap version instead.

  I have tried a basic
 sudo snap remove firefox

  and when that didn't work
 sudo snap disable firefox
 sudo snap remove --purget firefox

  The former should be enough - that's a direct expression of my preferences,
  some thing like "You should have typed sudo snap remove --do-not-reinstall
  --disable-auto-ignore-preferences firefox"  would not resolve this bug.

  When installing using apt-get, the correct version is being installed, and
  snap afterwards does not show the presence of firefox:

  Get:1 http://us.archive.ubuntu.com/ubuntu jammy/universe amd64
  xul-ext-ubufox all 3.4-0ubuntu1.17.10.1 [3,320 B]
  Get:2 https://ppa.launchpadcontent.net/mozillateam/ppa/ubuntu jammy/main
  amd64 firefox-locale-en amd64 108.0+build2-0ubuntu0.22.04.1~mt1 [831 kB]
  Get:3 https://ppa.launchpadcontent.net/mozillateam/ppa/ubuntu jammy/main
  amd64 firefox amd64 108.0+build2-0ubuntu0.22.04.1~mt1 [64.9 MB]

  Name   Version RevTracking
  Publisher  Notes
  authy  2.2.2   12 latest/stable
 twilio-authy   -
  bare   1.0 5  latest/stable
 canonical✓ base
  chromium   108.0.5359.94   2238   latest/stable
 canonical✓ -
  code   5235c6bb114latest/stable
 vscode✓classic
  core   16-2.57.6   14399  latest/stable
 canonical✓ core
  core18 202211032632   latest/stable
 canonical✓ base
  core20 202211231738   latest/stable
 canonical✓ base
  cups   2.4.2-4 836latest/stable
 openprinting✓  -
  gnome-3-28-18043.28.0-19-g98f9e67.98f9e67  161latest/stable
 canonical✓ -
  gnome-3-38-20040+git.6f39565   119latest/stable
 canonical✓ -
  gtk-common-themes  0.1-81-g442e511 1535
  latest/stable/…  canonical✓ -
  onlyoffice-desktopeditors  7.2.1   133latest/stable
 onlyoffice✓-
  snap-store 41.3-66-gfe1e325638
   latest/stable/…  canonical✓ -
  snapd  2.57.6  17883  latest/stable
 canonical✓ snapd

  
  /var/lib/snapd/seed/snaps contains (once firefox is removed):

  core18_1880.snap  gnome-3-34-1804_36.snap  gtk-common-themes_1506.snap
   snapd_8542.snap  snap-store_467.snap

  
https://ubuntuhandbook.org/index.php/2021/10/prevent-installing-firefox-snap-ubuntu-mate-21-10/
  claims that a similar issue affects Ubuntu MATE 21.04 and the solution was
  to type "sudo apt-mark manual firefox", which I have done, but that has not
  resolved the problem.

  I'm not here to explain why I wouldn't want the snap version, it is clearly
  a bug for snap to accept a command to uninstall something and then
  automatically reinstall it days later without the permission of the user,
  and especially galling that it removes the real version at the same time.

  I have lost data (passwords and history) because of this bug, because one
  of the many faults of the snap version is that it ignores the user's real
  ~/.mozilla profile and creates a shadow profile instead inside of the snap
  system.

  Please disable this behavior. It's obnoxious, it ignores EXPLICITY stated
  user preferences, and it causes the loss of data.

  I am unclear on what package is causing the behavior so for now marking it
  against Firefox, but it could be against some other piece of infrastructure
  related to snap:

   affects ubuntu/firefox

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1999308/+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 2002575] Re: Update nautilus to 43.2

** Changed in: nautilus (Ubuntu Kinetic)
   Status: Triaged => In Progress

** Description changed:

  Impact
  --
  This is a new stable release in the GNOME 43 series
  
  https://gitlab.gnome.org/GNOME/nautilus/-/blob/43.2/NEWS
  
  (The current version in Ubuntu 22.10 is 43.0)
  
  Nautilus 43 switched to GTK4 which was a major change for a complex app.
  Many regressions have been fixed in the new point release updates.
  
  Test Case 0
  ---
  Nautilus has a build test suite that will fail the build if the tests fail.
  
  Test Case 1
  ---
  Install the update
- Ensure that Nautilus still works well
+ 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
  
  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
+ As a component of GNOME Core, there is a micro-release exception for
  nautilus
  
  https://wiki.ubuntu.com/StableReleaseUpdates/GNOME

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

Title:
  Update nautilus to 43.2

Status in nautilus package in Ubuntu:
  Fix Committed
Status in nautilus source package in Kinetic:
  In Progress

Bug description:
  Impact
  --
  This is a new stable release in the GNOME 43 series

  https://gitlab.gnome.org/GNOME/nautilus/-/blob/43.2/NEWS

  (The current version in Ubuntu 22.10 is 43.0)

  Nautilus 43 switched to GTK4 which was a major change for a complex
  app. Many regressions have been fixed in the new point release
  updates.

  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

  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/2002575/+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 1990563] Re: Some maximized/fullscreen windows appear on both monitors

2023-01-13 Thread gpothier

Mutter 43.2 has been released upsteam:
https://gitlab.gnome.org/GNOME/mutter/-/tags/43.2

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

Title:
  Some maximized/fullscreen windows appear on both monitors

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

Bug description:
  I have a dual monitor setup, with external monitor configured as primary. 
When I maximize certain windows on the secondary monitor, a copy of the same 
window appears on the primary monitor (see first attached video). It happens 
with some apps, not with all of them. For example, it happens with IntelliJ 
IDEA (Java app) and Spotify (presumably Electron app), not with Gnome Text 
Editor, Gnome Terminal, Chrome or Firefox, for instance.
  A very similar situation occurs when taking a screenshot with Flameshot, 
though in the opposite way: a copy of the primary monitor appears on the 
secondary (see second attached video).

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: mutter 43.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0
  Uname: Linux 5.19.0-15-generic x86_64
  ApportVersion: 2.23.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: GNOME
  Date: Thu Sep 22 14:37:37 2022
  InstallationDate: Installed on 2018-12-14 (1378 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  SourcePackage: mutter
  UpgradeStatus: Upgraded to kinetic on 2022-09-02 (20 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/1990563/+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 2002845] Re: debhelper 13.11.4ubuntu1 broke dh-translations

Reversal of a specific debhelper commit fixes it:

https://launchpad.net/~gunnarhj/+archive/ubuntu/debhelper/+packages

This is the applied patch:

https://pastebin.ubuntu.com/p/P8qM2sHn9C/

And the reversed commit was made in response to a wishlist bug so it
shouldn't be so important.

https://bugs.debian.org/1016354

** Bug watch added: Debian Bug tracker #1016354
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1016354

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

Title:
  debhelper 13.11.4ubuntu1 broke dh-translations

Status in debhelper package in Ubuntu:
  Triaged
Status in gnome-control-center package in Ubuntu:
  Triaged
Status in gnome-text-editor package in Ubuntu:
  Triaged
Status in pkgbinarymangler package in Ubuntu:
  Triaged

Bug description:
  Today's debhelper 13.11.4ubuntu1 merge broke dh-translations.

  https://launchpad.net/ubuntu/+source/gnome-text-editor/43.2-1ubuntu1

  gnome-text-editor build log excerpt
  ---
  dh_translations
  Can't exec "meson introspect '/<>/obj-x86_64-linux-gnu' 
--targets |
   jq -r -M '.[].name | select(endswith("-pot")) | sub("-pot"; "")'":
   No such file or directory at /usr/share/perl5/Debian/Debhelper/Dh_Lib.pm 
line 518.
  dh_translations: error: exec (for cmd: "meson introspect 
'/<>/obj-x86_64-linux-gnu'
   --targets | jq -r -M '.[].name | select(endswith(\"-pot\")) |
   sub(\"-pot\"; \"\")'") failed: No such file or directory
  dh_translations: error: "meson introspect 
'/<>/obj-x86_64-linux-gnu'
   --targets | jq -r -M '.[].name | select(endswith(\"-pot\")) |
   sub(\"-pot\"; \"\")'" returned exit code 25

  Other Info
  --
  Gunnar identified the bad commit as
  https://salsa.debian.org/debian/debhelper/-/commit/62a8608

  https://launchpad.net/~gunnarhj/+archive/ubuntu/debhelper/+packages
  https://pastebin.ubuntu.com/p/P8qM2sHn9C/

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/debhelper/+bug/2002845/+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 1848942] Re: Freeze on opening font viewer

2023-01-13 Thread B

I'm still seeing this on Ubuntu 20.04.5 LTS and gnome-font-viewer 3.34.0

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

Title:
  Freeze on opening font viewer

Status in gnome-font-viewer package in Ubuntu:
  Confirmed

Bug description:
  When I open gnome-font-viewer, after few seconds interface freezes and
  I only can move my cursor.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-font-viewer 3.34.0-1
  ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
  Uname: Linux 5.3.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct 20 20:02:24 2019
  InstallationDate: Installed on 2019-10-20 (0 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-font-viewer
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-font-viewer/+bug/1848942/+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 2002845] [NEW] debhelper 13.11.4ubuntu1 broke dh-translations

Public bug reported:

Today's debhelper 13.11.4ubuntu1 merge broke dh-translations.

https://launchpad.net/ubuntu/+source/gnome-text-editor/43.2-1ubuntu1

gnome-text-editor build log excerpt
---
dh_translations
Can't exec "meson introspect '/<>/obj-x86_64-linux-gnu' --targets |
 jq -r -M '.[].name | select(endswith("-pot")) | sub("-pot"; "")'":
 No such file or directory at /usr/share/perl5/Debian/Debhelper/Dh_Lib.pm line 
518.
dh_translations: error: exec (for cmd: "meson introspect 
'/<>/obj-x86_64-linux-gnu'
 --targets | jq -r -M '.[].name | select(endswith(\"-pot\")) |
 sub(\"-pot\"; \"\")'") failed: No such file or directory
dh_translations: error: "meson introspect 
'/<>/obj-x86_64-linux-gnu'
 --targets | jq -r -M '.[].name | select(endswith(\"-pot\")) |
 sub(\"-pot\"; \"\")'" returned exit code 25

Other Info
--
Gunnar identified the bad commit as
https://salsa.debian.org/debian/debhelper/-/commit/62a8608

https://launchpad.net/~gunnarhj/+archive/ubuntu/debhelper/+packages
https://pastebin.ubuntu.com/p/P8qM2sHn9C/

** Affects: debhelper (Ubuntu)
 Importance: Critical
 Status: Triaged

** Affects: gnome-control-center (Ubuntu)
 Importance: Undecided
 Status: Triaged

** Affects: gnome-text-editor (Ubuntu)
 Importance: Undecided
 Status: Triaged

** Affects: pkgbinarymangler (Ubuntu)
 Importance: Undecided
 Status: Triaged


** Tags: block-proposed ftbfs lunar

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

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

** Also affects: pkgbinarymangler (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: gnome-control-center (Ubuntu)
   Status: New => Triaged

** Changed in: gnome-text-editor (Ubuntu)
   Status: New => Triaged

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

** Tags added: ftbfs

** Description changed:

  Today's debhelper 13.11.4ubuntu1 merge broke dh-translations.
+ 
+ https://launchpad.net/ubuntu/+source/gnome-text-editor/43.2-1ubuntu1
  
  gnome-text-editor build log excerpt
  ---
  dh_translations
  Can't exec "meson introspect '/<>/obj-x86_64-linux-gnu' 
--targets |
-  jq -r -M '.[].name | select(endswith("-pot")) | sub("-pot"; "")'":
-  No such file or directory at /usr/share/perl5/Debian/Debhelper/Dh_Lib.pm 
line 518.
+  jq -r -M '.[].name | select(endswith("-pot")) | sub("-pot"; "")'":
+  No such file or directory at /usr/share/perl5/Debian/Debhelper/Dh_Lib.pm 
line 518.
  dh_translations: error: exec (for cmd: "meson introspect 
'/<>/obj-x86_64-linux-gnu'
-  --targets | jq -r -M '.[].name | select(endswith(\"-pot\")) |
-  sub(\"-pot\"; \"\")'") failed: No such file or directory
+  --targets | jq -r -M '.[].name | select(endswith(\"-pot\")) |
+  sub(\"-pot\"; \"\")'") failed: No such file or directory
  dh_translations: error: "meson introspect 
'/<>/obj-x86_64-linux-gnu'
-  --targets | jq -r -M '.[].name | select(endswith(\"-pot\")) |
-  sub(\"-pot\"; \"\")'" returned exit code 25
+  --targets | jq -r -M '.[].name | select(endswith(\"-pot\")) |
+  sub(\"-pot\"; \"\")'" returned exit code 25
  
  Other Info
  --
  Gunnar identified the bad commit as
  https://salsa.debian.org/debian/debhelper/-/commit/62a8608
  
  https://launchpad.net/~gunnarhj/+archive/ubuntu/debhelper/+packages
  https://pastebin.ubuntu.com/p/P8qM2sHn9C/

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

Title:
  debhelper 13.11.4ubuntu1 broke dh-translations

Status in debhelper package in Ubuntu:
  Triaged
Status in gnome-control-center package in Ubuntu:
  Triaged
Status in gnome-text-editor package in Ubuntu:
  Triaged
Status in pkgbinarymangler package in Ubuntu:
  Triaged

Bug description:
  Today's debhelper 13.11.4ubuntu1 merge broke dh-translations.

  https://launchpad.net/ubuntu/+source/gnome-text-editor/43.2-1ubuntu1

  gnome-text-editor build log excerpt
  ---
  dh_translations
  Can't exec "meson introspect '/<>/obj-x86_64-linux-gnu' 
--targets |
   jq -r -M '.[].name | select(endswith("-pot")) | sub("-pot"; "")'":
   No such file or directory at /usr/share/perl5/Debian/Debhelper/Dh_Lib.pm 
line 518.
  dh_translations: error: exec (for cmd: "meson introspect 
'/<>/obj-x86_64-linux-gnu'
   --targets | jq -r -M '.[].name | select(endswith(\"-pot\")) |
   sub(\"-pot\"; \"\")'") failed: No such file or directory
  dh_translations: error: "meson introspect 
'/<>/obj-x86_64-linux-gnu'
   --targets | jq -r -M '.[].name | select(endswith(\"-pot\")) |
   sub(\"-pot\"; \"\")'" returned exit code 25

  Other Info
  --
  Gunnar identified the bad commit as
  https://salsa.debian.org/debian/debhelper/-/commit/62a8608

[Desktop-packages] [Bug 1999924] Re: Unsupported buffer format 842094158

2023-01-13 Thread Bram Stolk

Ugh, this may need revisiting. Even though it stops the crash, it also
seems to stop hardware decode support for me. I would have sworn I
tested with intel_gpu_top, but on the current edge build, I see no HW
acceleration anymore.

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

Title:
  Unsupported buffer format 842094158

Status in chromium-browser package in Ubuntu:
  Fix Committed

Bug description:
  This is with 107.0.5304.121-hwacc from latest/candidate/hwacc on
  Ubuntu 22.10 Wayland.

  When playing a h264 video, or a youtube video, I get:

  ```
  $ snap info chromium | grep installed
  installed:  107.0.5304.121-hwacc(2224) 171MB -
  $ chromium ~/sample.mp4
  Gtk-Message: 09:25:06.701: Not loading module "atk-bridge": The functionality 
is provided by GTK natively. Please try to not load it.
  [15876:15876:1216/092506.880657:ERROR:gpu_init.cc(537)] Passthrough is not 
supported, GL is egl, ANGLE is
  [15747:15837:1216/092506.908136:ERROR:top_sites_backend.cc(79)] Failed to 
initialize database.
  [15747:15747:1216/092507.059802:ERROR:wayland_event_watcher.cc(36)] 
libwayland: [destroyed object]: error 7: failed to import supplied dmabufs: 
Unsupported buffer format 842094158

  Trace/breakpoint trap (core dumped)
  ```

  Test video: https://test-
  videos.co.uk/vids/bigbuckbunny/mp4/h264/1080/Big_Buck_Bunny_1080_10s_30MB.mp4

  I will try other hwacc versions and a non-hwacc version to see if they
  behave differently.

  OS: Ubuntu 22.10

  Desktop: Wayland

  GPU: Intel AlderLake-S GT1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/124/+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 1871320] Re: Switching alert sound will not take effect unless you switch to Default alert first

2023-01-13 Thread Bug Watch Updater

** Changed in: gnome-control-center
   Status: Unknown => Fix Released

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

Title:
  Switching alert sound will not take effect unless you switch to
  Default alert first

Status in gnome-control-center:
  Fix Released
Status in gnome-control-center package in Ubuntu:
  Fix Committed

Bug description:
  I installed April 5th's nightly build, of Ubuntu Focal Fossa (development 
branch).
  Description:  Ubuntu Focal Fossa (development branch)
  Release:  20.04

  The issue is,

  Whichever the notification sound we choose after default, only that
  sound will take effect. Directly changing to another type of alert
  sound will not take effect.

  To reproduce the problem,

  1. Open terminal,
  2. Open sound settings, initially it will be "default". Change that to some 
other alert sound, say, "Drip".
  3. Switch to terminal and press backspace, you will hear "Drip".
  4. Switch to sound settings, this time select "Glass".
  5. Switch to terminal and press backspace, here is the issue. You will not 
hear "Glass". You will still hear "Drip".
  6. Switch to sound settings, now select default first and then select "Glass".
  7. Switch to terminal and press backspace, now you will hear "Glass".

  So to summarize, if you want to change the alert sound, first you have to 
switch back to "Default" and then only whichever other alert sound you select, 
will take effect.
  Since the release time is near, I thought it would be helpful to fix this 
before release.

  Thank you.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-control-center/+bug/1871320/+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 1961508] Re: Dock displaying over window after resuming from blank screen

2023-01-13 Thread Mike

I have same bug with clean install of Ubuntu 22.04.01 LTS. I did
reinstall as I assumed a couple of bugs were caused by kernel updates
and other non-standard settings, seems not.

HP Laptop - 15s-fq1xxx
Intel® Core™ i5-1035G4 CPU
Mesa Intel® Iris(R) Plus Graphics (ICL GT1.5)

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

Title:
  Dock displaying over window after resuming from blank screen

Status in Dash to dock:
  Unknown
Status in Mutter:
  New
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed
Status in gnome-desktop package in Fedora:
  Confirmed

Bug description:
  I have Blank Screen set to happen after 2 minutes of inactivity.

  When resuming from a Blank Screen (by moving the mouse or touching the
  keyboard), the Dock is displayed over the top of the current program.

  To get it back to normal I need to click "Restore Down" on the current
  programs window and then "Maximize" so that the Dock no longer
  overlaps it.

  (Note: I have Auto-hide dock turned off.)

  This only happens sometimes. I can't reproduce the bug it every time.

  -

  1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> 
About Ubuntu
  - Ubuntu 21.10

  2) The version of the package you are using, via 'apt-cache policy pkgname' 
or by checking in Software Center
  - Not sure (I guess the Dock is part of the Gnome interface?)

  3) What you expected to happen
  - Dock should not overlap the current program on resume from screen blank.

  4) What happened instead
  - The Dock overlaps the current program on resume from screen blank.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 21.10
  InstallationDate: Installed on 2022-02-18 (24 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  Package: gnome-shell-extension-ubuntu-dock
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.13.0-35.40-generic 5.13.19
  RelatedPackageVersions: mutter-common 40.5-1ubuntu3~21.10.1
  Tags:  wayland-session impish
  Uname: Linux 5.13.0-35-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  --- 
  ProblemType: Bug
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 22.10
  InstallationDate: Installed on 2022-02-18 (328 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  Package: mutter
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.19.0-28.29-generic 5.19.17
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions: mutter-common 43.0-1ubuntu4
  Tags: wayland-session third-party-packages kinetic
  Uname: Linux 5.19.0-28-generic x86_64
  UpgradeStatus: Upgraded to kinetic on 2022-10-25 (79 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/dash-to-dock/+bug/1961508/+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 1871320] Re: Switching alert sound will not take effect unless you switch to Default alert first

This is fixed in gnome-control-center 44 Alpha.

** Changed in: gnome-control-center (Ubuntu)
   Status: Confirmed => Fix Committed

** Bug watch added: gitlab.gnome.org/GNOME/gnome-control-center/-/issues #2277
   https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/2277

** Also affects: gnome-control-center via
   https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/2277
   Importance: Unknown
   Status: Unknown

** Tags added: focal jammy kinetic

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

Title:
  Switching alert sound will not take effect unless you switch to
  Default alert first

Status in gnome-control-center:
  Fix Released
Status in gnome-control-center package in Ubuntu:
  Fix Committed

Bug description:
  I installed April 5th's nightly build, of Ubuntu Focal Fossa (development 
branch).
  Description:  Ubuntu Focal Fossa (development branch)
  Release:  20.04

  The issue is,

  Whichever the notification sound we choose after default, only that
  sound will take effect. Directly changing to another type of alert
  sound will not take effect.

  To reproduce the problem,

  1. Open terminal,
  2. Open sound settings, initially it will be "default". Change that to some 
other alert sound, say, "Drip".
  3. Switch to terminal and press backspace, you will hear "Drip".
  4. Switch to sound settings, this time select "Glass".
  5. Switch to terminal and press backspace, here is the issue. You will not 
hear "Glass". You will still hear "Drip".
  6. Switch to sound settings, now select default first and then select "Glass".
  7. Switch to terminal and press backspace, now you will hear "Glass".

  So to summarize, if you want to change the alert sound, first you have to 
switch back to "Default" and then only whichever other alert sound you select, 
will take effect.
  Since the release time is near, I thought it would be helpful to fix this 
before release.

  Thank you.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-control-center/+bug/1871320/+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 2002837] [NEW] dialog contents uses wrong ratio

2023-01-13 Thread SR

Public bug reported:

Laptop with external HDMI display connected.
Ratio is 200% on external display, 100% on laptop display.
Please find attached the picture of a dialog using the wrong ratio for the 
dialog contents, but the correct ratio for the dialog borders, icons, etc.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: thunderbird 1:102.4.2+build2-0ubuntu0.22.04.1
ProcVersionSignature: Ubuntu 5.15.0-57.63-generic 5.15.74
Uname: Linux 5.15.0-57-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
AddonCompatCheckDisabled: False
ApportVersion: 2.20.11-0ubuntu82.3
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  stan   2677 F pipewire-media-
 /dev/snd/seq:stan   2676 F pipewire
BuildID: 20221101185644
CasperMD5CheckResult: unknown
Channel: Unavailable
CurrentDesktop: ubuntu:GNOME
Date: Fri Jan 13 18:55:23 2023
ExecutablePath: /usr/lib/thunderbird/thunderbird
Extensions: extensions.sqlite corrupt or missing
ForcedLayersAccel: False
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini 
or extensions.sqlite)
InstallationDate: Installed on 2019-04-26 (1357 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
IpRoute:
 default via 192.168.0.1 dev enxe848b85b98b1 proto dhcp metric 100 
 169.254.0.0/16 dev enxe848b85b98b1 scope link metric 1000 
 192.168.0.0/24 dev enxe848b85b98b1 proto kernel scope link src 192.168.0.246 
metric 100 
 192.168.127.0/24 dev enxe848b85b98b1 proto kernel scope link src 
192.168.127.246 
 192.168.128.0/24 dev enxe848b85b98b1 proto kernel scope link src 
192.168.128.246
Locales: extensions.sqlite corrupt or missing
PrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/thunderbird/omni.ja:greprefs.js:306
PrefSources: prefs.js
Profiles: Profile0 (Default) - LastVersion=102.4.2/20221101185644 (In use)
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
RebootRequiredPkgs: Error: path contained symlinks.
RunningIncompatibleAddons: False
SourcePackage: thunderbird
Themes: extensions.sqlite corrupt or missing
UpgradeStatus: Upgraded to jammy on 2022-09-03 (132 days ago)
dmi.bios.date: 12/09/2021
dmi.bios.release: 1.15
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.15.0
dmi.board.name: 0WWHJ2
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.15.0:bd12/09/2021:br1.15:svnDellInc.:pnPrecision5540:pvr:rvnDellInc.:rn0WWHJ2:rvrA00:cvnDellInc.:ct10:cvr:sku0906:
dmi.product.family: Precision
dmi.product.name: Precision 5540
dmi.product.sku: 0906
dmi.sys.vendor: Dell Inc.

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


** Tags: amd64 apport-bug jammy

** Attachment added: "Screenshot from 2023-01-13 18-50-48.png"
   
https://bugs.launchpad.net/bugs/2002837/+attachment/5641236/+files/Screenshot%20from%202023-01-13%2018-50-48.png

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

Title:
  dialog contents uses wrong ratio

Status in thunderbird package in Ubuntu:
  New

Bug description:
  Laptop with external HDMI display connected.
  Ratio is 200% on external display, 100% on laptop display.
  Please find attached the picture of a dialog using the wrong ratio for the 
dialog contents, but the correct ratio for the dialog borders, icons, etc.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: thunderbird 1:102.4.2+build2-0ubuntu0.22.04.1
  ProcVersionSignature: Ubuntu 5.15.0-57.63-generic 5.15.74
  Uname: Linux 5.15.0-57-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  stan   2677 F pipewire-media-
   /dev/snd/seq:stan   2676 F pipewire
  BuildID: 20221101185644
  CasperMD5CheckResult: unknown
  Channel: Unavailable
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jan 13 18:55:23 2023
  ExecutablePath: /usr/lib/thunderbird/thunderbird
  Extensions: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  InstallationDate: Installed on 2019-04-26 (1357 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  IpRoute:
   default via 192.168.0.1 dev enxe848b85b98b1 proto dhcp metric 100 
   169.254.0.0/16 dev enxe848b85b98b1 scope link metric 1000 
   192.168.0.0/24 dev

[Desktop-packages] [Bug 1993019] Re: UnboundLocalError: local variable 'version' referenced before assignment

2023-01-13 Thread Alberto Milone

** Also affects: ubuntu-drivers-common (Ubuntu Kinetic)
   Importance: Undecided
   Status: New

** Also affects: ubuntu-drivers-common (Ubuntu Focal)
   Importance: Undecided
   Status: New

** Also affects: ubuntu-drivers-common (Ubuntu Jammy)
   Importance: Undecided
   Status: New

** Also affects: ubuntu-drivers-common (Ubuntu Bionic)
   Importance: Undecided
   Status: New

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

** Changed in: ubuntu-drivers-common (Ubuntu Kinetic)
   Status: New => In Progress

** Changed in: ubuntu-drivers-common (Ubuntu Jammy)
   Status: New => In Progress

** Changed in: ubuntu-drivers-common (Ubuntu Focal)
   Status: New => In Progress

** Changed in: ubuntu-drivers-common (Ubuntu Bionic)
   Status: New => In Progress

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

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

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

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

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

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

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

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

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

Title:
  UnboundLocalError: local variable 'version' referenced before
  assignment

Status in ubuntu-drivers-common package in Ubuntu:
  Fix Released
Status in ubuntu-drivers-common source package in Bionic:
  In Progress
Status in ubuntu-drivers-common source package in Focal:
  In Progress
Status in ubuntu-drivers-common source package in Jammy:
  In Progress
Status in ubuntu-drivers-common source package in Kinetic:
  In Progress

Bug description:
  Hello, we received a drive-by complaint about the ubuntu-drivers
  autoinstall tool:

  < Fhazal> hye i have problem with ubuntu 22.04 nvidia auto install command
  < Fhazal> this error appear when i try to auto install recommended driver
  < Fhazal> https://pastebin.com/ydZVFT24

  The contents of the pastebin:

  Traceback (most recent call last):
File "/usr/bin/ubuntu-drivers", line 513, in 
  greet()
File "/usr/lib/python3/dist-packages/click/core.py", line 1128, in __call__
  return self.main(*args, **kwargs)
File "/usr/lib/python3/dist-packages/click/core.py", line 1053, in main
  rv = self.invoke(ctx)
File "/usr/lib/python3/dist-packages/click/core.py", line 1659, in invoke
  return _process_result(sub_ctx.command.invoke(sub_ctx))
File "/usr/lib/python3/dist-packages/click/core.py", line 1395, in invoke
  return ctx.invoke(self.callback, **ctx.params)
File "/usr/lib/python3/dist-packages/click/core.py", line 754, in invoke
  return __callback(*args, **kwargs)
File "/usr/lib/python3/dist-packages/click/decorators.py", line 84, in 
new_func
  return ctx.invoke(f, obj, *args, **kwargs)
File "/usr/lib/python3/dist-packages/click/core.py", line 754, in invoke
  return __callback(*args, **kwargs)
File "/usr/bin/ubuntu-drivers", line 432, in autoinstall
  command_install(config)
File "/usr/bin/ubuntu-drivers", line 187, in command_install
  UbuntuDrivers.detect.nvidia_desktop_pre_installation_hook(to_install)
File "/usr/lib/python3/dist-packages/UbuntuDrivers/detect.py", line 839, in 
nvidia_desktop_pre_installation_hook
  with_nvidia_kms = version >= 470
  UnboundLocalError: local variable 'version' referenced before assignment

  
  Skimming the version on my system it sure feels plausible:

  def nvidia_desktop_pre_installation_hook(to_install):
  '''Applies changes that need to happen before installing the NVIDIA 
drivers'''
  with_nvidia_kms = False

  # Enable KMS if nvidia >= 470
  for package_name in to_install:
  if package_name.startswith('nvidia-driver-'):
  try:
  version = int(package_name.split('-')[-1])
  except ValueError:
  pass
  finally:
  with_nvidia_kms = version >= 470

  if with_nvidia_kms:
  set_nvidia_kms(1)


  If there was an exception splitting, indexing, or converting to an
  int, that 'version' variable may not have a value.

  Thanks

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1993019/+subscriptions


-- 
Mailing list:

[Desktop-packages] [Bug 1972790] Re: Can't connect to hotspot created on ubuntu

2023-01-13 Thread Clemens Falker-Gieske

I have that problem since I switched to Ubuntu 22.04. Cannot connect
with any of my three different Android devices.

Now I downgraded my OS to Ubuntu 20.04 (for some other reason), which
runs wpa_supplicant v2.9. I still cannot connect.

I have another hotspot PC running, which works fine with Ubuntu 18.04.

I would highly appreciate a fix, since being a hotspot is the main
reason for this computer's existence.

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

Title:
  Can't connect to hotspot created on ubuntu

Status in wpa package in Ubuntu:
  Confirmed

Bug description:
  We currently have older systems (18.04) with hotspot's and we will migrate to 
22.04.
  Anything work's fine, expect the hotspot.
  The Hotspot will be created and is visible in the WLAN-List, but if the 
security is set to "WPA & WPA2 Personal" we get the error message "Failed to 
connect to the network".
  If we change the Security to "WPA3 Personal" we get the error message 
"Invalid Password", even if the password is correct.
  As soon we remove the security (change it to "none"), we can connect with out 
any problems.

  We can reproduce it with a fresh installtion of the Ubuntu Server
  22.04 and the following two commands:

  apt install network-manager

  nmcli c add type wifi ifname wlp3s0 con-name Hotspot autoconnect yes
  ssid test-ap 802-11-wireless.mode ap 802-11-wireless.band bg
  802-11-wireless.mac-address "80:45:dd:f0:27:ba" wifi-sec.group ccmp
  wifi-sec.key-mgmt wpa-psk wifi-sec.pairwise ccmp wifi-sec.proto rsn
  wifi-sec.psk "test12345" ipv4.addresses 192.168.60.1/24 ipv4.method
  shared && nmcli connection up Hotspot

  
  We thought it could be similar to this issue: 
https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1958267
  Because if we test it with 20.04 it worked fine, because 20.04 uses the 
Version 2:2.9.0-21build1 as described in the Ticket.

  As @Sebastian Bacher suggested 
(https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1958267/comments/58), i 
created a own report.
  In the attachment is the requested log file.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: wpasupplicant 2:2.10-6 [modified: 
lib/systemd/system/wpa_supplicant.service]
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Tue May 10 07:24:15 2022
  InstallationDate: Installed on 2022-05-10 (0 days ago)
  InstallationMedia: Ubuntu-Server 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220421)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: wpa
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1972790/+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 1987945] Re: [snap] chromium does not read root-owned files in $HOME

2023-01-13 Thread Nathan Teodosio

Sorry but this should be marked "Won't fix" as per the Snapcraft team
response on #9.

** Changed in: chromium-browser (Ubuntu)
Assignee: Nathan Teodosio (nteodosio) => (unassigned)

** Changed in: chromium-browser (Ubuntu)
Status: Triaged => Won't Fix

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

Title:
[snap] chromium does not read root-owned files in $HOME

Status in chromium-browser package in Ubuntu:
Won't Fix

Bug description:
Today, I literally spent hours trying to figure out why I cound't
upload a large file.

Of course I thought the problem was the size of the file.

It wasn't. The problem was that Chromium in Snap for some reason is
confined so that it can SEE file-owned-by-root.zip, but NOT READ file-
owned-by-root.zip.

I tried to upload the big file onto a PsiTransfer webpage. And it
simply stalled. The apache2 backend reported 400-errors and I got no
useful info out of that.

Chromium itself reported this in the Networking tab:

PATCH https://PSITRANSFER_HOST/path net::ERR_FAILED

Which is totally useless. In no way could I expect that the ultimate
cause was that the local file was not owned by me.

_If I can see the file, and I have read-permissions on it, I expect
that I can upload the file._

Another example:

$ ls -l ~/Junk/rode_muur*
-rw-rw-r-- 1 walter walter 64773 aug 27 18:08 /home/walter/Junk/rode_muur.jpg
-rw-rw-r-- 1 root root 64773 aug 27 18:08
/home/walter/Junk/rode_muur_root.jpg

Trying to upload rode_muur_root.jpg to e.g.
https://www.filestack.com/fileschool/html/html-file-upload-tutorial-
example/ yields this error-page:

This site can’t be reached
The webpage at
https://www.filestack.com/fileschool/html/html-file-upload-tutorial-example/fileupload.php
might be temporarily down or it may have moved permanently to a new web
address.
ERR_ACCESS_DENIED

That does not tell me that there is a problem with the local file.
That looks like a remote problem, am I right?

What would be the fix?

- Either don't show the file, if you're not letting me access it;
- or let me access the file;
- or, if that isn't possible, give me a reasonable error message. Having to
look in journalctl [1] as root to find out why a client application is
misbehaving is just not acceptable.

[1] # journalctl -t audit -n1 -o cat
AVC apparmor="DENIED" operation="open" profile="snap.chromium.chromium"
name="/home/walter/Junk/rode_muur_root.jpg" pid=768825 comm="ThreadPoolForeg"
requested_mask="r" denied_mask="r" fsuid=1000 ouid=0

(I know that I'll be complaining to deaf ears. You have your reasons
for putting all the browsers in snap. But from a user's perspective,
this whole snap thing has been One Giant Disappointment. I'm actually
considering moving to alternative distros after more than 10 perfectly
satisfactory years on Ubuntu.)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1987945/+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 1988836] Re: LRMv6: Enable the open NVIDIA kernel modules

2023-01-13 Thread Andy Whitcroft

** Summary changed:

- Enable the open NVIDIA kernel modules
+ LRMv6: Enable the open NVIDIA kernel modules

** Summary changed:

- LRMv6: Enable the open NVIDIA kernel modules
+ LRMv7: Enable the open NVIDIA kernel modules

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

Title:
  LRMv7: Enable the open NVIDIA kernel modules

Status in linux-restricted-modules package in Ubuntu:
  In Progress
Status in nvidia-graphics-drivers-515 package in Ubuntu:
  Fix Released
Status in ubuntu-drivers-common package in Ubuntu:
  Fix Released
Status in linux-restricted-modules source package in Focal:
  In Progress
Status in nvidia-graphics-drivers-515 source package in Focal:
  Fix Released
Status in ubuntu-drivers-common source package in Focal:
  Fix Committed
Status in linux-restricted-modules source package in Jammy:
  In Progress
Status in nvidia-graphics-drivers-515 source package in Jammy:
  Fix Released
Status in ubuntu-drivers-common source package in Jammy:
  Fix Committed

Bug description:
  [ Impact ]

   * The 515 series introduced open kernel modules for the NVIDIA driver. They 
come with an open source licence, and should be provided as an option for 
datacenter GPUs:
 
https://developer.nvidia.com/blog/nvidia-releases-open-source-gpu-kernel-modules/

 Currently, this is only production-ready (and enabled) on
  datacenter GPUs.

   * We should enable signed modules for the 515-open drivers, giving
  users the option to try the drivers.

   * The ubuntu-drivers tool should set a lower priority for the -open
  flavour, so that we do not end up recommending it over the plain 515
  flavour.

  [ Test Plan ]

   * [ubuntu-drivers-common]:
 "sudo ubuntu-drivers install (to make sure the driver is not installed by 
default)"

   * [nvidia driver]

 "sudo ubuntu-drivers install nvidia:515-open" to make sure that the
  driver can be installed manually.

 Please make sure that this installs the correct linux-restricted-
  modules.

 Note: support for GeForce and Workstation GPUs is alpha-quality,
  and is disabled by default. This means that desktop testing is not
  needed at the moment.

  [ Where problems could occur ]

   * This adds a new driver combination, which is not meant to be default, and 
is only enabled for a limited amount of devices (datacenter GPUs).
   * We need to be sure that the driver is not recommended over the other 
drivers.

  [ Other Info ]
   
  -

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/1988836/+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 2002680] Re: "Sharing Options" not translated to local language

I decided that this is the most sensible route and uploaded the thing to
Debian. This will make sense to translations in Ubuntu once 0.7.5-0.3
has built in Ubuntu followed by an update of the language packs.

Upstream may need some tutoring as regards translations. But that is
another story.

** Changed in: nautilus-share (Ubuntu)
   Status: New => In Progress

** Changed in: nautilus-share (Ubuntu)
 Assignee: (unassigned) => Gunnar Hjalmarsson (gunnarhj)

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

Title:
  "Sharing Options" not translated to local language

Status in Ubuntu Translations:
  Incomplete
Status in nautilus-share package in Ubuntu:
  In Progress

Bug description:
  after installing nautilus-share the context entry for sharing is
  inconsistent with system language.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-translations/+bug/2002680/+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 1997907] Re: [snap] Message 0 rejected by interface blink.mojom.WidgetHost

2023-01-13 Thread Ted Saker

Yes, wireless function is nominal.

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

Title:
  [snap] Message 0 rejected by interface blink.mojom.WidgetHost

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  Chromium shuts down and when restarted, says it didn't shut down
  properly.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  ProcVersionSignature: Ubuntu 5.15.0-53.59~20.04.1-generic 5.15.64
  Uname: Linux 5.15.0-53-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.25
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Nov 24 16:34:50 2022
  InstallationDate: Installed on 2022-03-19 (250 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Snap: chromium 107.0.5304.110 (latest/stable)
  SnapSource: ubuntu/+source/chromium-browser
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1997907/+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 1997907] Re: [snap] Message 0 rejected by interface blink.mojom.WidgetHost

2023-01-13 Thread Nathan Teodosio

You have a bunch of

  ndisc[0x55d1069466d0,"wlp2s0"]: solicit: failure sending router
solicitation: Operation not permitted

warnings, is your wireless interface working correctly at all? Not that
this should cause Chromium to crash or not launch.

** Summary changed:

- [snap] trap invalid opcode
+ [snap] Message 0 rejected by interface blink.mojom.WidgetHost

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

Title:
  [snap] Message 0 rejected by interface blink.mojom.WidgetHost

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  Chromium shuts down and when restarted, says it didn't shut down
  properly.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  ProcVersionSignature: Ubuntu 5.15.0-53.59~20.04.1-generic 5.15.64
  Uname: Linux 5.15.0-53-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.25
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Nov 24 16:34:50 2022
  InstallationDate: Installed on 2022-03-19 (250 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Snap: chromium 107.0.5304.110 (latest/stable)
  SnapSource: ubuntu/+source/chromium-browser
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1997907/+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 2002680] Re: "Sharing Options" not translated to local language

** Patch removed: "possible-upload-to-debian.diff"
   
https://bugs.launchpad.net/ubuntu-translations/+bug/2002680/+attachment/5641179/+files/possible-upload-to-debian.diff

** Patch added: "possible-upload-to-debian.diff"
   
https://bugs.launchpad.net/ubuntu-translations/+bug/2002680/+attachment/5641180/+files/possible-upload-to-debian.diff

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

Title:
  "Sharing Options" not translated to local language

Status in Ubuntu Translations:
  Incomplete
Status in nautilus-share package in Ubuntu:
  New

Bug description:
  after installing nautilus-share the context entry for sharing is
  inconsistent with system language.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-translations/+bug/2002680/+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 1998263] Re: JPEG ( backing store not supported ) : many pictures won't open.

Let's SRU that change to 22.10

** Description changed:

+ * Impact
+ 
+ Eog can't open high resolution jpg files
+ 
+ * Test Case
+ 
+ - download 
https://gitlab.gnome.org/GNOME/gdk-pixbuf/uploads/fcda5bc359fbf55a1b9755ba92c3303d/kwiatek.jpg
+ - try to open the image in eog
+ 
+ * Regression potential
+ 
+ The change increase the memory usage limit for loading jpg, it could
+ lead to put the system under memory pressure. The limit has been added
+ in 22.10 though so it isn't a regression compared to the previous
+ version of Ubuntu
+ 
+ -
+ 
+ 
  Hi,
  
  22.10. Just try to open some .jpg files from my usual storage.
  
  Error interpreting jpeg file ( Backing store not supported. )
  
  Those same pictures open in other OSes ( 22.04, 20.04 and else. )
  
  Can't use those pictures as backgrounds.
  
  But able to open them in Gimp or Shotwell.
  
  Maybe related to : https://gitlab.gnome.org/GNOME/gdk-
  pixbuf/-/issues/216
  
  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: eog 43.0-1
  ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7
  Uname: Linux 5.19.0-23-generic x86_64
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Nov 29 23:31:36 2022
  InstallationDate: Installed on 2022-10-27 (33 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: eog
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  JPEG ( backing store not supported ) : many pictures won't open.

Status in Eye of GNOME:
  Fix Released
Status in gdk-pixbuf:
  Fix Released
Status in gdk-pixbuf package in Ubuntu:
  Fix Released
Status in gdk-pixbuf source package in Jammy:
  Invalid
Status in gdk-pixbuf source package in Lunar:
  Fix Released

Bug description:
  * Impact

  Eog can't open high resolution jpg files

  * Test Case

  - download 
https://gitlab.gnome.org/GNOME/gdk-pixbuf/uploads/fcda5bc359fbf55a1b9755ba92c3303d/kwiatek.jpg
  - try to open the image in eog

  * Regression potential

  The change increase the memory usage limit for loading jpg, it could
  lead to put the system under memory pressure. The limit has been added
  in 22.10 though so it isn't a regression compared to the previous
  version of Ubuntu

  -

  
  Hi,

  22.10. Just try to open some .jpg files from my usual storage.

  Error interpreting jpeg file ( Backing store not supported. )

  Those same pictures open in other OSes ( 22.04, 20.04 and else. )

  Can't use those pictures as backgrounds.

  But able to open them in Gimp or Shotwell.

  Maybe related to : https://gitlab.gnome.org/GNOME/gdk-
  pixbuf/-/issues/216

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: eog 43.0-1
  ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7
  Uname: Linux 5.19.0-23-generic x86_64
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Nov 29 23:31:36 2022
  InstallationDate: Installed on 2022-10-27 (33 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: eog
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/eog/+bug/1998263/+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 2002680] Re: "Sharing Options" not translated to local language

Please see the attached diff about what I'm about to upload to Debian.

** Patch added: "possible-upload-to-debian.diff"
   
https://bugs.launchpad.net/ubuntu/+source/nautilus-share/+bug/2002680/+attachment/5641179/+files/possible-upload-to-debian.diff

** Tags added: patch

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

Title:
  "Sharing Options" not translated to local language

Status in Ubuntu Translations:
  Incomplete
Status in nautilus-share package in Ubuntu:
  New

Bug description:
  after installing nautilus-share the context entry for sharing is
  inconsistent with system language.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-translations/+bug/2002680/+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 1961508] Re: Dock displaying over window after resuming from blank screen

2023-01-13 Thread Bug Watch Updater

Launchpad has imported 1 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=2155862.

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


On 2022-12-22T16:52:52+00:00 fabriciol.castillo wrote:

Created attachment 1934127
12 screenshots

Description of problem:
Windows that are maximized or that take all vertical space are resized after 
lock (and logging back in) so that they "leave space" for top panel, even 
though panel is set to auto-hide (via Hide Top Bar extension). This only 
happens to focused windows. I had this happen to Firefox, Text Editor and 
Terminal. Tested VSCode, Chrome and Files but that doesn't happen in those 
cases.

How reproducible:
I cannot be certain if this affects other apps cause I couldn't carry out more 
extensive tests. However, as it affects those important apps (for me) it is a 
bit annoying (enough to report).


Steps to Reproduce:
1. Install and enable the Hide Top Bar gnome extension.
2. Open Firefox and maximize it. Alternatively it could be Terminal or Text 
Editor. Also, you can try when window is moved to the horizontal split position 
(left right) via shortcut (window takes all vertical space) 
3. Lock session with Super+L
5. Unlock and restore session

Actual results:
Firefox (or Terminal or Text Editor)is resized and is not taking all vertical 
space anymore. Also, it looks as if the app "thinks" it is maximized because 
the shortcut for this doesn't work until you resize and reposition and try 
maximizing again. Only the focused window (before lock) is afected. 

Expected results:
No window position or size is changed after lock.

Additional info:
- Attaching some screenshots to illustrate issue. I'm including 4 cases (two 
firefox, one terminal and one text editor. Each case has a before lock and 
after lock. I included an extra screen shot to show that the top bar extends to 
the space that resized windows leave. 
- I don't remember having this problem before.
- I thought it may have to do with firefox but other gnome app are affected.

Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-
extension-ubuntu-dock/+bug/1961508/comments/38


** Changed in: gnome-desktop (Fedora)
   Status: Unknown => Confirmed

** Changed in: gnome-desktop (Fedora)
   Importance: Unknown => Low

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

Title:
  Dock displaying over window after resuming from blank screen

Status in Dash to dock:
  Unknown
Status in Mutter:
  New
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed
Status in gnome-desktop package in Fedora:
  Confirmed

Bug description:
  I have Blank Screen set to happen after 2 minutes of inactivity.

  When resuming from a Blank Screen (by moving the mouse or touching the
  keyboard), the Dock is displayed over the top of the current program.

  To get it back to normal I need to click "Restore Down" on the current
  programs window and then "Maximize" so that the Dock no longer
  overlaps it.

  (Note: I have Auto-hide dock turned off.)

  This only happens sometimes. I can't reproduce the bug it every time.

  -

  1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> 
About Ubuntu
  - Ubuntu 21.10

  2) The version of the package you are using, via 'apt-cache policy pkgname' 
or by checking in Software Center
  - Not sure (I guess the Dock is part of the Gnome interface?)

  3) What you expected to happen
  - Dock should not overlap the current program on resume from screen blank.

  4) What happened instead
  - The Dock overlaps the current program on resume from screen blank.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 21.10
  InstallationDate: Installed on 2022-02-18 (24 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  Package: gnome-shell-extension-ubuntu-dock
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.13.0-35.40-generic 5.13.19
  RelatedPackageVersions: mutter-common 40.5-1ubuntu3~21.10.1
  Tags:  wayland-session impish
  Uname: Linux 5.13.0-35-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  --- 
  ProblemType: Bug
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64

[Desktop-packages] [Bug 1961508] Re: Dock displaying over window after resuming from blank screen

2023-01-13 Thread Jan Vlug

** Bug watch added: Red Hat Bugzilla #2155862
   https://bugzilla.redhat.com/show_bug.cgi?id=2155862

** Also affects: gnome-desktop (Fedora) via
   https://bugzilla.redhat.com/show_bug.cgi?id=2155862
   Importance: Unknown
   Status: Unknown

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

Title:
  Dock displaying over window after resuming from blank screen

Status in Dash to dock:
  Unknown
Status in Mutter:
  New
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed
Status in gnome-desktop package in Fedora:
  Unknown

Bug description:
  I have Blank Screen set to happen after 2 minutes of inactivity.

  When resuming from a Blank Screen (by moving the mouse or touching the
  keyboard), the Dock is displayed over the top of the current program.

  To get it back to normal I need to click "Restore Down" on the current
  programs window and then "Maximize" so that the Dock no longer
  overlaps it.

  (Note: I have Auto-hide dock turned off.)

  This only happens sometimes. I can't reproduce the bug it every time.

  -

  1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> 
About Ubuntu
  - Ubuntu 21.10

  2) The version of the package you are using, via 'apt-cache policy pkgname' 
or by checking in Software Center
  - Not sure (I guess the Dock is part of the Gnome interface?)

  3) What you expected to happen
  - Dock should not overlap the current program on resume from screen blank.

  4) What happened instead
  - The Dock overlaps the current program on resume from screen blank.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 21.10
  InstallationDate: Installed on 2022-02-18 (24 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  Package: gnome-shell-extension-ubuntu-dock
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.13.0-35.40-generic 5.13.19
  RelatedPackageVersions: mutter-common 40.5-1ubuntu3~21.10.1
  Tags:  wayland-session impish
  Uname: Linux 5.13.0-35-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  --- 
  ProblemType: Bug
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 22.10
  InstallationDate: Installed on 2022-02-18 (328 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  Package: mutter
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.19.0-28.29-generic 5.19.17
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions: mutter-common 43.0-1ubuntu4
  Tags: wayland-session third-party-packages kinetic
  Uname: Linux 5.19.0-28-generic x86_64
  UpgradeStatus: Upgraded to kinetic on 2022-10-25 (79 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/dash-to-dock/+bug/1961508/+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 2002290] Re: Poor Arabic rendering in VTE

2023-01-13 Thread Egmont Koblinger

** Package changed: vte (Ubuntu) => vte2.91 (Ubuntu)

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

Title:
  Poor Arabic rendering in VTE

Status in gnome-terminal package in Ubuntu:
  New
Status in vte2.91 package in Ubuntu:
  New

Bug description:
  VTE has a number of issues when it comes to rendering Arabic letters
  in the terminal, which could affect a number of languages (Arabic,
  Urdu, Persian... etc).

  Bug 1: Any Arabic word in any VTE-based terminal is choppily displayed
  with spaces between its letters, making readability hard and sometimes
  not possible. Sometimes the letters are crushed together very closely
  making reading impossible too.

  Bug 2: If a non-Arabic text and an Arabic text are displayed together
  in the same line, then the entire line will be missed up and you won't
  be able to understand what is being said.

  Both of these bugs can be seen from the image I attached.

  I reported both of these bugs together because it's unlikely they can
  be fixed separately, probably they are related to each other.

  Problem can be seen in any VTE-based terminal. Here I am using GNOME
  Terminal 3.44.0 on Ubuntu 22.04, but it can be seen in any Ubuntu
  version and in any terminal version as well (it has been there since
  forever).

  I reported the bug here instead of upstream because that's what they
  said at the page: https://wiki.gnome.org/Apps/Terminal/ReportingBugs,
  but this bug is not related to Ubuntu only; it happens on all Linux
  distributions.

  Happy to provide any information you need, or any do tests or
  experiments.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/2002290/+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 1986451] Re: Can't click context menu items when they cover the dock (in a Xorg session)

2023-01-13 Thread vadim

Yes, I noticed that it also affects the menu bar. If this is indeed a
problem with the widget in xorg, what should I do? I don't want to use
wayland because it contains many bugs that degrade the Linux experience.

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

Title:
  Can't click context menu items when they cover the dock (in a Xorg
  session)

Status in Dash to dock:
  Unknown
Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  New

Bug description:
  ubuntu dock in bottom position won't let me click on button (convert
  java file to Kotlin file) in android studio, but in the left position
  everything works correctly. That is, if the menu android studio
  overlaps the ubuntu dock, then the menu buttons will not be pressed.

  https://youtu.be/KsOVG7Uucow

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39
  Uname: Linux 5.15.0-46-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
  .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
  .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  515.65.01  Wed Jul 20 
14:00:58 UTC 2022
   GCC version:
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CompositorRunning: None
  Date: Sun Aug 14 10:52:56 2022
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  DkmsStatus:
   openrazer-driver/3.4.0, 5.15.0-43-generic, x86_64: installed
   openrazer-driver/3.4.0, 5.15.0-46-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: Xiaomi UHD Graphics 620 [1d72:1701]
 Subsystem: Xiaomi Mi Notebook Pro [GeForce MX150] [1d72:1701]
  InstallationDate: Installed on 2022-07-13 (31 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  MachineType: Timi TM1701
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-46-generic 
root=UUID=7c5eaac1-9b38-4169-8a20-0fef5e97c644 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/02/2018
  dmi.bios.release: 106.121
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: XMAKB5R0P0603
  dmi.board.asset.tag: Any
  dmi.board.name: TM1701
  dmi.board.vendor: Timi
  dmi.board.version: MP
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Timi
  dmi.chassis.version: Chassis Version
  dmi.ec.firmware.release: 0.3
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvrXMAKB5R0P0603:bd02/02/2018:br106.121:efr0.3:svnTimi:pnTM1701:pvr:rvnTimi:rnTM1701:rvrMP:cvnTimi:ct10:cvrChassisVersion:sku:
  dmi.product.family: Timibook
  dmi.product.name: TM1701
  dmi.sys.vendor: Timi
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.110-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 22.0.5-0ubuntu0.1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

To manage notifications about this bug go to:
https://bugs.launchpad.net/dash-to-dock/+bug/1986451/+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 2000937] Re: DING settings values shown untranslated

Great, thanks Gunnar!

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

Title:
  DING settings values shown untranslated

Status in Ubuntu Translations:
  Fix Committed
Status in gnome-control-center package in Ubuntu:
  Fix Committed

Bug description:
  Ubuntu 22.10 ; Gnome 43.0

  Hello,
  There is a translation problem (missing?) in gnome-control-center.
  See image attached.
  Regards,
  Roxfr

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-translations/+bug/2000937/+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 2002212] Re: Outdated version of libglib2.0-dev in Ubuntu Jammy

Thank you for your bug report. Updating to a new major serie of glib isn't 
going to be done as a stable update because that wouldn't be a safe update and 
might create build or runtime issues for existing software. 
You probably want to update your code to be compatible with older version of 
glib since that's what most users will still have today, use 
G_APPLICATION_FLAGS_NONE instead of the new default flag for example

** Changed in: glib2.0 (Ubuntu)
   Importance: Undecided => Wishlist

** Changed in: glib2.0 (Ubuntu)
   Status: New => Won't Fix

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

Title:
  Outdated version of libglib2.0-dev in Ubuntu Jammy

Status in glib2.0 package in Ubuntu:
  Won't Fix

Bug description:
  The version of libglib2.0-dev that is currently included in the
  repositories for Ubuntu is 2.72.1-1, which is outdated and missing
  important features and bug fixes. In particular, the
  G_APPLICATION_DEFAULT_FLAGS macro, which was added in GTK+ 3.22, is
  not available in this version of libglib2.0-dev. This is causing
  issues with my application, which requires the use of this macro.

  I request that the package be updated to the latest version (currently
  2.74) in order to resolve this issue.

  Steps to reproduce:
1. Install libglib2.0-dev version 2.72.1-1 on an Ubuntu system
2. Attempt to compile an application that uses the 
G_APPLICATION_DEFAULT_FLAGS macro
3. Observe the compilation error due to the missing macro

  Expected result:
  The application compiles successfully and can be run.

  Actual result:
  The application fails to compile due to the missing 
G_APPLICATION_DEFAULT_FLAGS macro.

  Release:
Description:Ubuntu 22.04.1 LTS
Release:22.04

  Using version:
  2.72.1-1

  Requested version:
  2.74(+)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/2002212/+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 1993621] Re: Switching virtual terminals [Ctrl-Alt-F1 - F7] to a X session turns off keyboard LEDs

2023-01-13 Thread Bug Watch Updater

** Changed in: xorg-server
   Status: Unknown => New

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

Title:
  Switching virtual terminals [Ctrl-Alt-F1 - F7] to a X session turns
  off keyboard LEDs

Status in OEM Priority Project:
  New
Status in X.Org X server:
  New
Status in xorg-server package in Ubuntu:
  New

Bug description:
  Switching virtual terminals [Ctrl-Alt-F1 - F7] to a X session turns
  off keyboard LEDs.

  This issue is reproducible on 2:21.1.3-2ubuntu2.1 (on 22.04)

  To reproduce:
  1. Log on a X session desktop (GNOME Xorg for example)
  2. Turn on NumLock
  3. Use Ctrl-Alt-F3 to switch to a text console, then Ctrl-Alt-F2 to switch 
back to desktop

  Expected:
  NumLock LED should be on

  Actual:
  NumLock LED is off, but functions like NumLock is on.  If NumLock is pressed 
the LED turns off as well as the function.  If CapsLock is pressed the LED 
states sync back (LED turns back on).

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1993621/+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 1993127] Re: /usr/bin/nautilus:11:g_list_store_find_with_equal_func_full:g_list_store_find_with_equal_func:g_list_store_find:nautilus_view_model_get_index:scroll_to_file_on_idl

The issue should be fixed by the new version in lunar-proposed

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

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

Title:
  
/usr/bin/nautilus:11:g_list_store_find_with_equal_func_full:g_list_store_find_with_equal_func:g_list_store_find:nautilus_view_model_get_index:scroll_to_file_on_idle

Status in Nautilus:
  Fix Released
Status in nautilus package in Ubuntu:
  Fix Committed

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
nautilus.  This problem was most recently seen with package version 
1:43.0-1ubuntu1, the problem page at 
https://errors.ubuntu.com/problem/32454f0bde038596049406d7ad99e47263fb8bf7 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nautilus/+bug/1993127/+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 2000185] Re: Nautilus crashes when returning to search results from a directory

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

thanks, that indicates it's the same issue than bug #1993127

** This bug has been marked a duplicate of bug 1993127
   
/usr/bin/nautilus:11:g_list_store_find_with_equal_func_full:g_list_store_find_with_equal_func:g_list_store_find:nautilus_view_model_get_index:scroll_to_file_on_idle

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

Title:
  Nautilus crashes when returning to search results from a directory

Status in nautilus package in Ubuntu:
  Incomplete

Bug description:
  I cannot figure out how to capture the crash. Launching nautilus from
  terminal does not give any crash logs when it happens and it is very
  easily reproduced and extremely annoying. To reproduce it yourself,
  perform the following:

  1. Launch nautilus and click on the 'other locations' tab.
  2. Select any drive, partition, filesystem, whatever you have there. For the 
sake of continuity, just select whatever drive Ubuntu is installed on.
  3. Type in a search query. It doesn't matter what it is, but it has to return 
a directory in the results that you can then enter. For example, type 
'pictures' into the search to return your pictures folder.
  4. Enter any of the directories that show up in the search results. From 
here, it doesn't matter what you do. As soon as you press back to return to the 
search results, nautilus will ALWAYS crash.

  This obviously makes searching for things like application files,
  where many directories will have the same name, extremely difficult
  and cumbersome. I can reproduce this crash 100% of the time. This is
  on Ubuntu 22.10 with nautilus 1:43.0-1ubuntu1.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: nautilus 1:43.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.19.0-26.27-generic 5.19.7
  Uname: Linux 5.19.0-26-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Dec 20 20:21:26 2022
  InstallationDate: Installed on 2022-07-09 (164 days ago)
  InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to kinetic on 2022-10-21 (60 days ago)
  usr_lib_nautilus:
   file-roller   43.0-1
   nautilus-extension-gnome-terminal 3.46.2-1ubuntu1
   nautilus-megasync 5.1.0-1.1
   python3-nautilus  4.0-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2000185/+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 1993621] Re: Switching virtual terminals [Ctrl-Alt-F1 - F7] to a X session turns off keyboard LEDs

2023-01-13 Thread Yao Wei

Related MP for this issue, however the MP does not fix the issue, and we
are proposing a similar patch:
https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/764

** Bug watch added: gitlab.freedesktop.org/xorg/xserver/-/issues #1234
   https://gitlab.freedesktop.org/xorg/xserver/-/issues/1234

** Also affects: xorg-server via
   https://gitlab.freedesktop.org/xorg/xserver/-/issues/1234
   Importance: Unknown
   Status: Unknown

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

Title:
  Switching virtual terminals [Ctrl-Alt-F1 - F7] to a X session turns
  off keyboard LEDs

Status in OEM Priority Project:
  New
Status in X.Org X server:
  Unknown
Status in xorg-server package in Ubuntu:
  New

Bug description:
  Switching virtual terminals [Ctrl-Alt-F1 - F7] to a X session turns
  off keyboard LEDs.

  This issue is reproducible on 2:21.1.3-2ubuntu2.1 (on 22.04)

  To reproduce:
  1. Log on a X session desktop (GNOME Xorg for example)
  2. Turn on NumLock
  3. Use Ctrl-Alt-F3 to switch to a text console, then Ctrl-Alt-F2 to switch 
back to desktop

  Expected:
  NumLock LED should be on

  Actual:
  NumLock LED is off, but functions like NumLock is on.  If NumLock is pressed 
the LED turns off as well as the function.  If CapsLock is pressed the LED 
states sync back (LED turns back on).

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1993621/+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 2000185] Re: Nautilus crashes when returning to search results from a directory

2023-01-13 Thread Munch

** Attachment added: "gdb-nautilus.txt"
   
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2000185/+attachment/5641144/+files/gdb-nautilus.txt

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

Title:
  Nautilus crashes when returning to search results from a directory

Status in nautilus package in Ubuntu:
  Incomplete

Bug description:
  I cannot figure out how to capture the crash. Launching nautilus from
  terminal does not give any crash logs when it happens and it is very
  easily reproduced and extremely annoying. To reproduce it yourself,
  perform the following:

  1. Launch nautilus and click on the 'other locations' tab.
  2. Select any drive, partition, filesystem, whatever you have there. For the 
sake of continuity, just select whatever drive Ubuntu is installed on.
  3. Type in a search query. It doesn't matter what it is, but it has to return 
a directory in the results that you can then enter. For example, type 
'pictures' into the search to return your pictures folder.
  4. Enter any of the directories that show up in the search results. From 
here, it doesn't matter what you do. As soon as you press back to return to the 
search results, nautilus will ALWAYS crash.

  This obviously makes searching for things like application files,
  where many directories will have the same name, extremely difficult
  and cumbersome. I can reproduce this crash 100% of the time. This is
  on Ubuntu 22.10 with nautilus 1:43.0-1ubuntu1.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: nautilus 1:43.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.19.0-26.27-generic 5.19.7
  Uname: Linux 5.19.0-26-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Dec 20 20:21:26 2022
  InstallationDate: Installed on 2022-07-09 (164 days ago)
  InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to kinetic on 2022-10-21 (60 days ago)
  usr_lib_nautilus:
   file-roller   43.0-1
   nautilus-extension-gnome-terminal 3.46.2-1ubuntu1
   nautilus-megasync 5.1.0-1.1
   python3-nautilus  4.0-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2000185/+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 2000185] Re: Nautilus crashes when returning to search results from a directory