date:20221017

[Expired for firefox (Ubuntu) because there has been no activity for 60
days.]

** Changed in: firefox (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  package firefox 101.0.1+build1-0ubuntu0.20.04.1 failed to
  install/upgrade: el subproceso nuevo paquete firefox script pre-
  installation devolvió el código de salida de error 1

Status in firefox package in Ubuntu:
  Expired

Bug description:
  Package stopped installing when upgrading from 20.04 to 22.04

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  Package: firefox 101.0.1+build1-0ubuntu0.20.04.1
  ProcVersionSignature: Ubuntu 5.13.0-51.58~20.04.1-generic 5.13.19
  Uname: Linux 5.13.0-51-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  arturo 1425 F pulseaudio
   /dev/snd/controlC0:  arturo 1425 F pulseaudio
  BuildID: 20220608170832
  CasperMD5CheckResult: unknown
  Channel: Unavailable
  Date: Sun Jun 26 15:24:06 2022
  ErrorMessage: el subproceso nuevo paquete firefox script pre-installation 
devolvió el código de salida de error 1
  ForcedLayersAccel: False
  InstallationDate: Installed on 2022-01-02 (174 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  IpRoute:
   default via 192.168.0.1 dev enp2s0 proto dhcp metric 100 
   169.254.0.0/16 dev enp2s0 scope link metric 1000 
   192.168.0.0/24 dev enp2s0 proto kernel scope link src 192.168.0.104 metric 
100
  NoProfiles: True
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Python3Details: /usr/bin/python3.10, Python 3.10.4, python3-minimal, 
3.10.4-0ubuntu2
  PythonDetails: N/A
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions:
   dpkg 1.21.1ubuntu2.1
   apt  2.4.5
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  Title: package firefox 101.0.1+build1-0ubuntu0.20.04.1 failed to 
install/upgrade: el subproceso nuevo paquete firefox script pre-installation 
devolvió el código de salida de error 1
  UpgradeStatus: Upgraded to jammy on 2022-06-26 (0 days ago)
  dmi.bios.date: 12/04/2019
  dmi.bios.release: 1.16
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8UCN16WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40679WIN
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 330-15AST
  dmi.ec.firmware.release: 1.16
  dmi.modalias: 
dmi:bvnLENOVO:bvr8UCN16WW:bd12/04/2019:br1.16:efr1.16:svnLENOVO:pn81D6:pvrLenovoideapad330-15AST:rvnLENOVO:rnLNVNB161216:rvrSDK0J40679WIN:cvnLENOVO:ct10:cvrLenovoideapad330-15AST:skuLENOVO_MT_81D6_BU_idea_FM_ideapad330-15AST:
  dmi.product.family: ideapad 330-15AST
  dmi.product.name: 81D6
  dmi.product.sku: LENOVO_MT_81D6_BU_idea_FM_ideapad 330-15AST
  dmi.product.version: Lenovo ideapad 330-15AST
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1979919/+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 1986415] Re: package firefox (not installed) failed to install/upgrade: new firefox package pre-installation script subprocess returned error exit status 1

[Expired for firefox (Ubuntu) because there has been no activity for 60
days.]

** Changed in: firefox (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  package firefox (not installed) failed to install/upgrade: new firefox
  package pre-installation script subprocess returned error exit status
  1

Status in firefox package in Ubuntu:
  Expired

Bug description:
  driver issues,,, i  also cant launch genymotion

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  Package: firefox (not installed)
  ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39
  Uname: Linux 5.15.0-46-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  AptOrdering:
   firefox:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Mon Aug  8 00:23:36 2022
  ErrorMessage: new firefox package pre-installation script subprocess returned 
error exit status 1
  InstallationDate: Installed on 2022-07-16 (27 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  Python3Details: /usr/bin/python3.10, Python 3.10.4, python3-minimal, 
3.10.4-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.21.1ubuntu2.1
   apt  2.4.5
  SourcePackage: firefox
  Title: package firefox (not installed) failed to install/upgrade: new firefox 
package pre-installation script subprocess returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1986415/+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 1986456] Re: Firefox fails to start after update

[Expired for firefox (Ubuntu) because there has been no activity for 60
days.]

** Changed in: firefox (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  Firefox fails to start after update

Status in firefox package in Ubuntu:
  Expired

Bug description:
  After system Updates today (14.08.2022) firefox did not start anymore.
  It's Ubuntu 22.04

  Error Message:

  mikey@mikey-notebook:~$ firefox
  /snap/firefox/1670/snap/command-chain/desktop-launch: line 52: 
/home/mikey/.config/user-dirs.dirs: Permission denied
  sed: can't read /home/mikey/.config/user-dirs.dirs: Permission denied
  /snap/firefox/1670/snap/command-chain/desktop-launch: line 264: 
/home/mikey/.config/user-dirs.dirs: Permission denied
  cp: cannot open '/home/mikey/.config/user-dirs.locale' for reading: 
Permission denied
  /snap/firefox/1670/snap/command-chain/desktop-launch: line 269: 
/home/mikey/.config/user-dirs.locale: Permission denied
  /snap/firefox/1670/snap/command-chain/desktop-launch: line 20: 
/snap/firefox/1670/gnome-platform/usr/lib/x86_64-linux-gnu/libgtk-3-0/gtk-query-immodules-3.0:
 No such file or directory
  ERROR: 
/snap/firefox/1670/gnome-platform/usr/lib/x86_64-linux-gnu/libgtk-3-0/gtk-query-immodules-3.0
 exited abnormally with status 127
  XPCOMGlueLoad error for file /snap/firefox/1670/usr/lib/firefox/libmozgtk.so:
  libgtk-3.so.0: cannot open shared object file: No such file or directory
  Couldn't load XPCOM.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1986456/+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 1990207] Re: "Night Light unavailable" in Settings (but the quick settings toggle for it works)

This bug was fixed in the package mutter - 43.0-1ubuntu4

---
mutter (43.0-1ubuntu4) kinetic; urgency=medium

  * debian/rules: Ignore test failures on armhf.
Temporary, to unblock the mutter update while we investigate the regression

 -- Jeremy Bicha   Mon, 17 Oct 2022 19:58:15 -0400

** Changed in: mutter (Ubuntu)
   Status: Fix Committed => 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/1990207

Title:
  "Night Light unavailable" in Settings (but the quick settings toggle
  for it works)

Status in gnome-control-center:
  Fix Released
Status in Mutter:
  Fix Released
Status in gnome-control-center package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Fix Released

Bug description:
  "Night Light unavailable" in Settings (but the quick settings toggle
  for it works).

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-control-center/+bug/1990207/+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 1993114] Re: gnome-shell crashed with SIGSEGV in cmsSetHeaderRenderingIntent → create_icc_profile_from_edid → create_device_profile_from_edid → meta_color_store_ensure_device_p

This bug was fixed in the package mutter - 43.0-1ubuntu4

---
mutter (43.0-1ubuntu4) kinetic; urgency=medium

  * debian/rules: Ignore test failures on armhf.
Temporary, to unblock the mutter update while we investigate the regression

 -- Jeremy Bicha   Mon, 17 Oct 2022 19:58:15 -0400

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

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

Title:
  gnome-shell crashed with SIGSEGV in cmsSetHeaderRenderingIntent →
  create_icc_profile_from_edid → create_device_profile_from_edid →
  meta_color_store_ensure_device_profile → on_cd_device_created

Status in GNOME Shell:
  Fix Released
Status in Release Notes for Ubuntu:
  New
Status in mutter package in Ubuntu:
  Fix Released
Status in mutter package in Debian:
  New

Bug description:
  gnome-shell crashed with SIGSEGV in cmsSetHeaderRenderingIntent →
  create_icc_profile_from_edid → create_device_profile_from_edid →
  meta_color_store_ensure_device_profile → on_cd_device_created

  Tracking in
  https://errors.ubuntu.com/problem/99b51dd6c89bc828d948412692497c33a31e368f

  This is one of the most common gnome-shell crash reports on Ubuntu
  22.10 but there are only a few reports of it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1993114/+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 1993192] Re: crash on dock aftter suspend and lock screen

2022-10-17 Thread Daniel van Vugt

It's unlikely there's a "crash" here because any crash in a Wayland
session will send you back to the login screen, at best.

** Summary changed:

- crash on dock aftter suspend and lock screen
+ after lock screen or suspend the dock can't hide again

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

Title:
  after lock screen or suspend the dock can't hide again

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

Bug description:
  after lock screen or suspend the dock can't hide again

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell-extension-ubuntu-dock 72~ubuntu5.22.04.1
  ProcVersionSignature: Ubuntu 5.15.0-50.56-generic 5.15.60
  Uname: Linux 5.15.0-50-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 18 00:31:50 2022
  InstallationDate: Installed on 2022-10-15 (2 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  PackageArchitecture: all
  SourcePackage: gnome-shell-extension-ubuntu-dock
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1993192/+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 1939058] Re: autopkgtest failure "stacking/override-redirect.metatest" on armhf

2022-10-17 Thread Steve Langasek

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

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

Title:
  autopkgtest failure "stacking/override-redirect.metatest" on armhf

Status in mutter package in Ubuntu:
  Fix Released

Bug description:
  https://autopkgtest.ubuntu.com/results/autopkgtest-
  impish/impish/armhf/m/mutter/20210805_091629_afb25@/log.gz

  
  Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a 
timestamp of 0 for 0x43
  not ok 18 stacking/override-redirect.metatest
 15: stacking: expected='1/2 | 1/1', actual='| 1/1 1/2'

  From the test history on armhf, it appears this particular test case
  intermittently passes or fails about half the time.  Other
  architectures have been passing all tests reliably without errors.

  Presumably the stacking order is non-deterministic on armhf for some
  reason?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1939058/+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 1993021] Re: Chromium displays form fields of a PDF different/wrong

2022-10-17 Thread Randall Whitman

In my assessment, there is almost certainly at least an interoperability
issue with Chromium, if it displays markedly different content than
multiple other implementations (and the other implementations are
consistent between them).

It is possible that there is additionally an issue with certain versions
of PDF-Arranger.

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

Title:
  Chromium displays form fields of a PDF different/wrong

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  With Evince-3.36.10-0ubuntu1, fill in US-IRS PDF Y2020 tax forms
  (f1040, f1040s1, f1040s2) and save.

  With PDF-Arranger 1.4.2-1:
  [+] t2210-f1040.pdf
  [+] t2210-1040s1.pdf
  [+] t2210-1040s2.pdf
  Export (down-arrow icon) t2210-tax-cat2.pdf - popped up warnings in dialog 
box:

  The metadata field /Accessibility with value 'structured; tagged' has no XMP 
equivalent, so it was discarded
  The metadata field /Form with value 'fillable' has no XMP equivalent, so it 
was discarded

  Display of t2210-tax-cat2.pdf page 3 (f1040 s1):

  * chromium-browser-106.0.5249.91: incorrectly displays form entry in lines 
2b, 5, 7, 8-lhs, 11, 13, 16, 21.
  * evince-3.36.10-0ubuntu1: correct (lines 1, 3, 9, 14 only)
  * firefox-104: correct (lines 1, 3, 9, 14 only)
  * xpdf-3.04-7: correct (lines 1, 3, 9, 14 only)

  Display of t2210-tax-cat2.pdf page 4 (f1040 s2):

  * chromium-browser-106.0.5249.91: incorrectly displays form entry in lines 1, 
3, 6, 7b, 8, 8c
  * evince-3.36.10-0ubuntu1: correctly blank except lines 4 & 10.
  * firefox-104: correctly blank except lines 4 & 10.
  * xpdf-3.04-7: correctly blank except lines 4 & 10.

  Ubuntu-20.04.5/Linux-5.4.0/amd64

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  ProcVersionSignature: Ubuntu 5.4.0-125.141-generic 5.4.195
  Uname: Linux 5.4.0-125-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.24
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Fri Oct 14 20:40:01 2022
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2018-11-21 (1424 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  Snap: chromium 106.0.5249.119 (latest/stable)
  SnapSource: ubuntu/+source/chromium-browser
  UpgradeStatus: Upgraded to focal on 2022-07-09 (97 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1993021/+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 1993226] [NEW] mutter autopkgtests fail to detect regressions in mesa

2022-10-17 Thread Steve Langasek

Public bug reported:

a last-hour upload of mutter for kinetic release fails to build from
source on armhf due to what appears to be a regression in mesa's
llvmpipe implementation in the mesa 22.2.1-1ubuntu1 build.

If this is a regression in mesa, it should have been possible to detect
it before mesa was promoted, via autopkgtests in the mutter package.

Counterintuitively, mutter declares autopkgtests, but the autopkgtests
do NOT test any of the OpenGL functionality via the mutter "nested
view".  Therefore the regression was only detected at the next upload of
mutter, NOT before mesa was promoted to the release, when we want to be
catching it.

Please fix mutter to ensure that the autopkgtests have at least as much
coverage as the build-time tests, which is the right way around.

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

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

Title:
  mutter autopkgtests fail to detect regressions in mesa

Status in mutter package in Ubuntu:
  New

Bug description:
  a last-hour upload of mutter for kinetic release fails to build from
  source on armhf due to what appears to be a regression in mesa's
  llvmpipe implementation in the mesa 22.2.1-1ubuntu1 build.

  If this is a regression in mesa, it should have been possible to
  detect it before mesa was promoted, via autopkgtests in the mutter
  package.

  Counterintuitively, mutter declares autopkgtests, but the autopkgtests
  do NOT test any of the OpenGL functionality via the mutter "nested
  view".  Therefore the regression was only detected at the next upload
  of mutter, NOT before mesa was promoted to the release, when we want
  to be catching it.

  Please fix mutter to ensure that the autopkgtests have at least as
  much coverage as the build-time tests, which is the right way around.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1993226/+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 1816497] Re: [snap] vaapi chromium no video hardware decoding

2022-10-17 Thread Daniel van Vugt

It's probably better to focus more on Intel until everything is working
well enough to close the bug. VAAPI has historically only been reliable
on Intel so we risk getting distracted in debugging non-Intel driver
issues (which would also be off-topic given this is a Chromium bug).

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

Title:
  [snap] vaapi chromium no video hardware decoding

Status in chromium-browser package in Ubuntu:
  In Progress

Bug description:
  To test the snap with VA-API changes,

  1. Install the Chromium snap,

     sudo snap install --channel beta/hwacc chromium

  2. Start Chromium,

     snap run chromium

  3. Open a video, e.g. one from https://github.com/chthomos/video-
  media-samples.

  4. Enter about:media-internals in the address bar, click the
  corresponding box (if the video is playing, it will have the "(kPlay)"
  identifier) and note what the page says for kVideoDecoderName.

  Please report

  - The value for kVideoDecoderName from step 4. Success is typically 
{Vaapi,VDA,Mojo}VideoDecoder while failure is {FFMpeg,Vpx,Dav1d}VideoDecoder;
  - Xorg or Wayland (`echo $WAYLAND_DISPLAY`);
  - Distro version (`grep VERSION= /etc/os_release`);
  - GPU (`lscpu`);
  - CPU generation (`lscpu`).

  Currently it seems to work for all reporters on Xorg, but not for all
  reporters on Wayland.

  Just to situate ourselves, beta/hwacc is [1] and I plan to merge it in
  the main snap via [2]. Comments before #176 refer to [3] and _should_
  be roughly equivalent to [1], but I wouldn't be surprised if it turned
  out not to be.

  [1]: 
https://launchpad.net/~nteodosio/+snap/chromium-browser-dev/+build/1875127
  [2]: 
https://code.launchpad.net/~nteodosio/chromium-browser/+git/chromium-browser/+merge/428038
  [3]: 
https://launchpad.net/~nteodosio/+snap/chromium-browser-hwacc/+build/1838168

  --Original Bug report -

  Libva is no longer working for snap installed chromium 72.0.3626.109
  (Official Build) snap (64-bit)

  I followed this instruction
  sudo snap install --channel=candidate/vaapi chromium

  My amdgpu can use libva

  `vainfo: Driver version: Mesa Gallium driver 18.3.3 for AMD STONEY (DRM 
3.27.0, 4.20.0-10.1-liquorix-amd64, LLVM 7.0.1)
  vainfo: Supported profile and entrypoints
    VAProfileMPEG2Simple:   VAEntrypointVLD
    VAProfileMPEG2Main  :   VAEntrypointVLD
    VAProfileVC1Simple  :   VAEntrypointVLD
    VAProfileVC1Main:   VAEntrypointVLD
    VAProfileVC1Advanced:   VAEntrypointVLD
    VAProfileH264ConstrainedBaseline:   VAEntrypointVLD
    VAProfileH264ConstrainedBaseline:   VAEntrypointEncSlice
    VAProfileH264Main   :   VAEntrypointVLD
    VAProfileH264Main   :   VAEntrypointEncSlice
    VAProfileH264High   :   VAEntrypointVLD
    VAProfileH264High   :   VAEntrypointEncSlice
    VAProfileHEVCMain   :   VAEntrypointVLD
    VAProfileHEVCMain10 :   VAEntrypointVLD
    VAProfileJPEGBaseline   :   VAEntrypointVLD
    VAProfileNone   :   VAEntrypointVideoProc`

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1816497/+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 1988256] Re: gnome-shell crashed with SIGSEGV in meta_get_first_subsurface_node() from pointer_can_grab_surface() from meta_wayland_pointer_can_grab_surface() from meta_wayland

2022-10-17 Thread Daniel van Vugt

If the second fix
https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2655 is required
then we should say "fixed in 43.1".

** Tags removed: fixed-in-42.6 fixed-in-43.rc
** Tags added: fixed-in-mutter-42.6 fixed-in-mutter-43.1

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

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

Title:
  gnome-shell crashed with SIGSEGV in meta_get_first_subsurface_node()
  from pointer_can_grab_surface() from
  meta_wayland_pointer_can_grab_surface() from
  meta_wayland_seat_get_grab_info() from token_can_activate()

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

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
gnome-shell.  This problem was most recently seen with package version 
43~beta-1ubuntu1, the problem page at 
https://errors.ubuntu.com/problem/6582f375d7b1e6bec0fdee2e9d2ec574844a8457 
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/mutter/+bug/1988256/+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 1966635] Re: can't move file/directory by drag and drop by using touch monitor

2022-10-17 Thread Kai-Chuan Hsieh

** Tags added: originate-from-1993110

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

Title:
  can't move file/directory by drag and drop by using touch monitor

Status in Mutter:
  Unknown
Status in OEM Priority Project:
  Confirmed
Status in mutter package in Ubuntu:
  New
Status in nautilus package in Ubuntu:
  Incomplete

Bug description:
  Can't move file/directory by drag and drop by using a touch monitor

  OS: 22.04, up to date @ Mar 28, 2022.
  nautilus: 1:42~rc-1-ubuntu1
  mode: wayland

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


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

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

2022-10-17 Thread Bug Watch Updater

** Changed in: mutter
   Status: Unknown => New

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

Title:
  firefox black window

Status in Mozilla Firefox:
  New
Status in Mutter:
  New
Status in firefox package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed

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

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

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

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

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

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


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

[Desktop-packages] [Bug 1993114] Re: gnome-shell crashed with SIGSEGV in cmsSetHeaderRenderingIntent → create_icc_profile_from_edid → create_device_profile_from_edid → meta_color_store_ensure_device_p

2022-10-17 Thread Brian Murray

With regards to possible hardware affected the debian bug report contains the 
following bit of information "I recently stumbled on an old and wacky 
video-projector device that produce 
garbage ICC profiles."

** Also affects: ubuntu-release-notes
   Importance: Undecided
   Status: New

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

Title:
  gnome-shell crashed with SIGSEGV in cmsSetHeaderRenderingIntent →
  create_icc_profile_from_edid → create_device_profile_from_edid →
  meta_color_store_ensure_device_profile → on_cd_device_created

Status in GNOME Shell:
  Fix Released
Status in Release Notes for Ubuntu:
  New
Status in mutter package in Ubuntu:
  Fix Committed
Status in mutter package in Debian:
  New

Bug description:
  gnome-shell crashed with SIGSEGV in cmsSetHeaderRenderingIntent →
  create_icc_profile_from_edid → create_device_profile_from_edid →
  meta_color_store_ensure_device_profile → on_cd_device_created

  Tracking in
  https://errors.ubuntu.com/problem/99b51dd6c89bc828d948412692497c33a31e368f

  This is one of the most common gnome-shell crash reports on Ubuntu
  22.10 but there are only a few reports of it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1993114/+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 1973470] Re: Ubuntu-bug command can't find Firefox on Lubuntu Kinetic

2022-10-17 Thread Brian Murray

I wonder if this bug wasn't a consequence of the firefox deb not being
installed and alternatives not being setup for x-www-browser and gnome-
www-browser. More details about that can be found in bug 1992688.

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

Title:
Ubuntu-bug command can't find Firefox on Lubuntu Kinetic

Status in Apport:
Fix Released
Status in apport package in Ubuntu:
Fix Released
Status in xdg-utils package in Ubuntu:
Invalid

Bug description:
Test hardware is an Elitebook 8570p, 16 GB RAM, 120 GB SSD.

While reporting Bug #1973469, I discovered that ubuntu-bug was unable
to open Firefox at the very end of the process. Sadly, I closed the
terminal window that contained the initial error, but I was able to
easily reproduce it reporting this bug. The full console output of
"ubuntu-bug apport" on Lubuntu Kinetic is:

*** Collecting problem information

The collected information can be sent to the developers to improve the
application. This might take a few minutes.
..

*** Send problem report to the developers?

After the problem report has been sent, please fill out the form in the
automatically opened web browser.

What would you like to do? Your options are:
S: Send report (5.1 KB)
V: View report
K: Keep report file for sending later or copying to somewhere else
I: Cancel and ignore future crashes of this program version
C: Cancel
Please choose (S/V/K/I/C): s

*** Uploading problem information

The collected information is being sent to the bug tracking system.
This might take a few minutes.
94%

*** To continue, you must visit the following URL:

https://bugs.launchpad.net/ubuntu/+source/apport/+filebug/d7ffa3e0-d46d-11ec-a167-40a8f03099c8?

You can launch a browser now, or copy this URL into a browser on
another computer.

Choices:
1: Launch a browser now
C: Cancel
Please choose (1/C): 1
/usr/bin/xdg-open: 882: firefox: not found
/usr/bin/xdg-open: 882: firefox: not found
xdg-open: no method available for opening
'https://bugs.launchpad.net/ubuntu/+source/apport/+filebug/d7ffa3e0-d46d-11ec-a167-40a8f03099c8?'

I am unsure if this problem is in Apport or Lubuntu. ubuntu-bug works
just fine for me on Ubuntu Kinetic, but not on Lubuntu. I suspect this
is due to the Snap version of Firefox, but I don't know for sure.
Since ubuntu-bug is what gave me the error, I'm filing this against
Apport.

ProblemType: Bug
DistroRelease: Ubuntu 22.10
Package: apport 2.20.11-0ubuntu82
ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
Uname: Linux 5.15.0-27-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.11-0ubuntu82
Architecture: amd64
CasperMD5CheckResult: pass
CasperVersion: 1.470
CurrentDesktop: LXQt
Date: Sun May 15 11:41:07 2022
LiveMediaBuild: Lubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220514)
PackageArchitecture: all
SourcePackage: apport
UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/apport/+bug/1973470/+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 1987137] Debian patch

2022-10-17 Thread Nathan Teodosio

I was just messing around and found this Debian patch[1]; Seems to be 
very much on point.

[1]: 
https://sources.debian.org/src/chromium/106.0.5249.119-1/debian/patches/fixes/angle-wayland.patch/

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

Title:
  Migrating chromium-browser to core22 has libwayland-client0 issues

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  Following on an earlier bug report that related to simple core22
  migration for chromium-browser, here is a blocker that I don't know
  how to deal with.

  After checking out the core22 branch from
  git+ssh://git.launchpad.net/~chromium-core22/+git/chromium-core22
  (which already contains the early, easy migration commits), doing a
  build eventually generates (snippet here):

  2022-08-19 20:15:05.809 :: In file included from 
../../third_party/wayland/src/src/wayland-client.h:40:
  2022-08-19 20:15:05.809 :: /usr/include/wayland-client-protocol.h:1038:13: 
error: use of undeclared identifier 'wl_proxy_marshal_flags'
  2022-08-19 20:15:05.809 :: callback = wl_proxy_marshal_flags((struct 
wl_proxy *) wl_display,
  2022-08-19 20:15:05.809 ::^
  2022-08-19 20:15:05.809 :: /usr/include/wayland-client-protocol.h:1062:13: 
error: use of undeclared identifier 'wl_proxy_marshal_flags'
  2022-08-19 20:15:05.810 :: registry = wl_proxy_marshal_flags((struct 
wl_proxy *) wl_display,
  2022-08-19 20:15:05.810 ::^
  2022-08-19 20:15:05.810 :: /usr/include/wayland-client-protocol.h:1175:7: 
error: use of undeclared identifier 'wl_proxy_marshal_flags'
  2022-08-19 20:15:05.810 :: id = wl_proxy_marshal_flags((struct 
wl_proxy *) wl_registry,
  2022-08-19 20:15:05.810 ::  ^
  2022-08-19 20:15:05.810 :: /usr/include/wayland-client-protocol.h:1291:7: 
error: use of undeclared identifier 'wl_proxy_marshal_flags'
  2022-08-19 20:15:05.810 :: id = wl_proxy_marshal_flags((struct 
wl_proxy *) wl_compositor,

  and lots more of the same; it seems pretty clear that the relevant
  wayland library is simply not new enough, and I don't know what to
  add/modify to add core22 support to the mix, so I am open to
  suggestions.

  I do notice the file
  parts/chromium/build/chrome/installer/linux/debian/dist_package_versions.json,
  which contains package version manifests for various distros, but not
  Ubuntu 22.04, so I'm *guessing* that might need enhancement. But
  that's just a guess.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1987137/+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 1993215] [NEW] google account dont works, freeze in gnome login.

2022-10-17 Thread buckaroo

Public bug reported:

google account dont works, freeze in gnome login. cursor dont work, cant
write.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: gnome-online-accounts 3.44.0-1ubuntu1
ProcVersionSignature: Ubuntu 5.15.0-50.56-generic 5.15.60
Uname: Linux 5.15.0-50-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
CasperMD5CheckResult: pass
Date: Mon Oct 17 18:43:27 2022
InstallationDate: Installed on 2022-10-17 (0 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419)
ProcEnviron:
 LANGUAGE=es_AR:es
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=es_AR.UTF-8
 SHELL=/bin/bash
SourcePackage: gnome-online-accounts
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug jammy

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

Title:
  google account dont works, freeze in gnome login.

Status in gnome-online-accounts package in Ubuntu:
  New

Bug description:
  google account dont works, freeze in gnome login. cursor dont work,
  cant write.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-online-accounts 3.44.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-50.56-generic 5.15.60
  Uname: Linux 5.15.0-50-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Mon Oct 17 18:43:27 2022
  InstallationDate: Installed on 2022-10-17 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  ProcEnviron:
   LANGUAGE=es_AR:es
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=es_AR.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-online-accounts
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1993215/+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 1988796] Re: Incorrect rendering triggered by cairo CAIRO_OPERATOR_SATURATE with subpixel positioning

2022-10-17 Thread Benjamin Gilbert

Thanks for the help!

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

Title:
  Incorrect rendering triggered by cairo CAIRO_OPERATOR_SATURATE with
  subpixel positioning

Status in pixman package in Ubuntu:
  Fix Released
Status in pixman source package in Focal:
  In Progress

Bug description:
  [ Impact ]

  OpenSlide (libopenslide0 in Ubuntu) uses Cairo as its rendering
  backend, always with CAIRO_OPERATOR_SATURATE and sometimes with
  subpixel positioning (when reading certain file formats), and Cairo in
  turn invokes this code. As a result, some slides incorrectly render
  with large blank spaces and with some pixels rendered on top of other
  pixels. This effectively makes OpenSlide unusable for several of the
  file formats it supports. No workaround is believed possible within
  the OpenSlide codebase.

  [ Test Plan ]

  Compile and run the pixman.c test program uploaded to this bug. It
  should report "OK".

  [ Where problems could occur ]

  Problems would show up as incorrect pixel output from software that
  renders via Cairo or pixman.

  [ Other Info ]

  While I'm not a pixman expert, it appears that the change should only
  affect the broken code path, and it seems unlikely that anything else
  depends on the incorrect math fixed by this patch. This bug hasn't
  previously been reported in Ubuntu, which may imply that this code
  path is not exercised by other packages in the distro.

  The affected source file has had no further commits upstream since
  this patch was applied in April 2019, and some basic commit grepping
  didn't turn up any followup fixes elsewhere in the tree.

  [ Original message ]

  pixman 0.38.4-0ubuntu1 in focal (and actually pixman 0.38.x generally)
  has a regression that causes incorrect rendering in some
  circumstances.  This can be triggered by the use of cairo with
  CAIRO_OPERATOR_SATURATE and subpixel positioning, and causes OpenSlide
   to produce incorrect output.

  The attached test program will print "Failed" if the bug exists, or
  "OK" if it doesn't.

  This is fixed upstream in
  https://gitlab.freedesktop.org/pixman/pixman/-/commit/8256c235, which
  is in pixman 0.40.0.

  See https://github.com/openslide/openslide/issues/278 for more
  context.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pixman/+bug/1988796/+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 1992255] Re: Cant upload files from remote folders : Firefox and Chrome

2022-10-17 Thread Miguel

Exactly, the fileselector is different in my opinion, like you see in
the screenshots

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

Title:
  Cant upload files from remote folders : Firefox and Chrome

Status in firefox package in Ubuntu:
  New

Bug description:
  I dont know if this is really a Nautilus bug. 
  In windows when we attach file in a webserver it opens "explorer" so I think 
in Linux is more or less the same.

  Problem:
  Upload file from a remote share to a Browser  it does nothing, no error 
nothing.

  If I upload from the same share to Thunderbird and it uploads
  normally.

  I noticed one thing, apparently the browsers uses a different
  "Nautilus" than Thunderbird.

  Please see the screenshots attached

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: nautilus 1:42.2-0ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-50.56-generic 5.15.60
  Uname: Linux 5.15.0-50-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Oct  8 21:15:39 2022
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_nautilus:
   evince42.3-0ubuntu2
   file-roller   3.42.0-1
   nautilus-extension-gnome-terminal 3.44.0-1ubuntu1
   nautilus-share0.7.3-2ubuntu6
   python3-nautilus  1.2.3-3.1build1

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

2022-10-17 Thread Jeremy Bicha

*** This bug is a security vulnerability ***

Public security bug reported:

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.

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

Prerequisite

We need to get mozjs102 on the i386 whitelist for Ubuntu 22.04 LTS

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

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


** Tags: jammy upgrade-software-version

** Summary changed:

- Update gjs to 1.74 using mozjs102 102.3
+ [jammy] Update gjs to 1.74 using mozjs102 102.3

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

** Description changed:

  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.
  
  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
+ 
+ Prerequisite
+ 
+ We need to get mozjs102 on the i386 whitelist for Ubuntu 22.04 LTS

-- 
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:
  New
Status in mozjs102 package in Ubuntu:
  New

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.

  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

  Prerequisite
  
  We need to get mozjs102 on the i386 whitelist for Ubuntu 22.04 LTS

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 78435]

The severity field for this bug is relatively low, S3. However, the bug has 5 
duplicates.
:nika, could you consider increasing the bug severity?

For more information, please visit [auto_nag
documentation](https://wiki.mozilla.org/Release_Management/autonag#severity_underestimated.py).

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

Title:
  temporary filenames should handle multiple extensions (.tar.gz)

Status in Mozilla Thunderbird:
  Confirmed
Status in thunderbird package in Ubuntu:
  Triaged

Bug description:
  Binary package hint: mozilla-thunderbird

  When opening a file named foo.bar, the file is downloaded to /tmp. If
  the file is opened again in a short time, the file is again downloaded
  to /tmp but renamed foo-1.bar.

  If the file has a double extension (for example, opening a foo.tar.gz
  file with ark), the file is renamed as foo.tar-1.gz and thus ark is
  not able to open it properly. It should be foo-1.tar.gz instead.

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

The last needinfo from me was triggered in error by recent activity on
the bug. I'm clearing the needinfo since this is a very old bug and I
don't know if it's still relevant.

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

Title:
  temporary filenames should handle multiple extensions (.tar.gz)

Status in Mozilla Thunderbird:
  Confirmed
Status in thunderbird package in Ubuntu:
  Triaged

Bug description:
  Binary package hint: mozilla-thunderbird

  When opening a file named foo.bar, the file is downloaded to /tmp. If
  the file is opened again in a short time, the file is again downloaded
  to /tmp but renamed foo-1.bar.

  If the file has a double extension (for example, opening a foo.tar.gz
  file with ark), the file is renamed as foo.tar-1.gz and thus ark is
  not able to open it properly. It should be foo-1.tar.gz instead.

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

The last needinfo from me was triggered in error by recent activity on
the bug. I'm clearing the needinfo since this is a very old bug and I
don't know if it's still relevant.

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

Title:
  "print selection only" option cuts multi-page text

Status in Mozilla Firefox:
  Confirmed
Status in firefox package in Ubuntu:
  Confirmed

Bug description:
  I tried selecting some text from a webpage that I wanted to print.
  The text was several pages long.  When I printed it, I noticed that
  the last line of the text was cut horizontally, and the bottom part
  was on the next page, thus making that line very difficult to read.

  I checked with just printing to a file (both postscript and pdf), and
  the same thing happens, and at the same proportions (the same amount
  of the line is cut off, and pushed to the next page)

  Obviously, I think the line of text shouldn't be cut at all.  It
  should be either squeezed into the current page (The "Ignore scaling
  and shrink page to fit width" option is selected, so maybe that could
  justify this?) or, just push the line to the next page.

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

The severity field for this bug is relatively low, S3. However, the bug has 10
duplicates.
:jwatt, could you consider increasing the bug severity?

For more information, please visit [auto_nag
documentation](https://wiki.mozilla.org/Release_Management/autonag#severity_underestimated.py).

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

Title:
"print selection only" option cuts multi-page text

Status in Mozilla Firefox:
Confirmed
Status in firefox package in Ubuntu:
Confirmed

Bug description:
I tried selecting some text from a webpage that I wanted to print.
The text was several pages long. When I printed it, I noticed that
the last line of the text was cut horizontally, and the bottom part
was on the next page, thus making that line very difficult to read.

I checked with just printing to a file (both postscript and pdf), and
the same thing happens, and at the same proportions (the same amount
of the line is cut off, and pushed to the next page)

Obviously, I think the line of text shouldn't be cut at all. It
should be either squeezed into the current page (The "Ignore scaling
and shrink page to fit width" option is selected, so maybe that could
justify this?) or, just push the line to the next page.

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

[Desktop-packages] [Bug 308605]

The last needinfo from me was triggered in error by recent activity on
the bug. I'm clearing the needinfo since this is a very old bug and I
don't know if it's still relevant.

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

Title:
  [MASTER]Firefox is already running message

Status in Mozilla Firefox:
  Confirmed
Status in firefox package in Ubuntu:
  Triaged

Bug description:
  When I close Firefox and start it again I get the following message:

  Firefox is already running, but is not responding. To open a new
  window, you must first close the existing Firefox process, or restart
  your system.

  I also have this problem with Firefox on Vista.
  I use Firefox 3.0.4.
  Ubuntu 8.10 (64 bit)

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

The last needinfo from me was triggered in error by recent activity on
the bug. I'm clearing the needinfo since this is a very old bug and I
don't know if it's still relevant.

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

Title:
  Get uncaught exception when populating a form in FireFox 3.6

Status in Mozilla Firefox:
  Confirmed
Status in firefox package in Ubuntu:
  Triaged

Bug description:
  Binary package hint: firefox

  When populating an input field on a form in Firefox (Linux or Windows)
  where I select or just pass the mouse over one of the historical
  suggestions that drops down while inputting, I receive the following
  error: Error: uncaught exception: [Exception... "Cannot modify
  properties of a WrappedNative"  nsresult: "0x80570034
  (NS_ERROR_XPC_CANT_MODIFY_PROP_ON_WN)"  location: "JS frame ::
  chrome://global/content/bindings/autocomplete.xml :: onxblpopuphiding
  :: line 825"  data: no]

  I do not receive the error in Google Chrome

  ProblemType: Bug
  DistroRelease: Ubuntu 10.04
  Package: firefox 3.6.6+nobinonly-0ubuntu0.10.04.1
  ProcVersionSignature: Ubuntu 2.6.32-23.37-generic 2.6.32.15+drm33.5
  Uname: Linux 2.6.32-23-generic i686
  Architecture: i386
  Date: Wed Jul 14 10:02:01 2010
  FirefoxPackages:
   firefox 3.6.6+nobinonly-0ubuntu0.10.04.1
   firefox-gnome-support 3.6.6+nobinonly-0ubuntu0.10.04.1
   firefox-branding 3.6.6+nobinonly-0ubuntu0.10.04.1
   abroswer N/A
   abrowser-branding N/A
  InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
  ProcEnviron:
   LANG=en_US.utf8
   SHELL=/bin/bash
  SourcePackage: firefox

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

The severity field for this bug is relatively low, S4. However, the bug has 17 
votes.
:mossop, could you consider increasing the bug severity?

For more information, please visit [auto_nag
documentation](https://wiki.mozilla.org/Release_Management/autonag#severity_underestimated.py).

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

Title:
  [MASTER]Firefox is already running message

Status in Mozilla Firefox:
  Confirmed
Status in firefox package in Ubuntu:
  Triaged

Bug description:
  When I close Firefox and start it again I get the following message:

  Firefox is already running, but is not responding. To open a new
  window, you must first close the existing Firefox process, or restart
  your system.

  I also have this problem with Firefox on Vista.
  I use Firefox 3.0.4.
  Ubuntu 8.10 (64 bit)

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