[Desktop-packages] [Bug 2046844] Re: AppArmor user namespace creation restrictions cause many applications to crash with SIGTRAP

[Alexander Browne]

I am seeing this with the (relatively new) Mozilla-provided Firefox deb
package (https://support.mozilla.org/en-US/kb/install-firefox-
linux#w_install-firefox-deb-package-for-debian-based-distributions).

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

Title:
  AppArmor user namespace creation restrictions cause many applications
  to crash with SIGTRAP

Status in akonadiconsole package in Ubuntu:
  Fix Released
Status in akregator package in Ubuntu:
  Fix Released
Status in angelfish package in Ubuntu:
  Fix Released
Status in apparmor package in Ubuntu:
  Fix Released
Status in bubblewrap package in Ubuntu:
  Confirmed
Status in cantor package in Ubuntu:
  Fix Released
Status in devhelp package in Ubuntu:
  Fix Released
Status in digikam package in Ubuntu:
  Fix Released
Status in epiphany-browser package in Ubuntu:
  Fix Released
Status in evolution package in Ubuntu:
  Fix Released
Status in falkon package in Ubuntu:
  Fix Released
Status in firefox package in Ubuntu:
  New
Status in freecad package in Ubuntu:
  Confirmed
Status in geary package in Ubuntu:
  Confirmed
Status in ghostwriter package in Ubuntu:
  Fix Released
Status in gnome-packagekit package in Ubuntu:
  Confirmed
Status in goldendict-webengine package in Ubuntu:
  Confirmed
Status in kalgebra package in Ubuntu:
  Fix Released
Status in kchmviewer package in Ubuntu:
  Confirmed
Status in kdeplasma-addons package in Ubuntu:
  Confirmed
Status in kgeotag package in Ubuntu:
  Fix Released
Status in kiwix package in Ubuntu:
  Confirmed
Status in kmail package in Ubuntu:
  Fix Released
Status in konqueror package in Ubuntu:
  Fix Released
Status in kontact package in Ubuntu:
  Fix Released
Status in marble package in Ubuntu:
  Fix Released
Status in notepadqq package in Ubuntu:
  Confirmed
Status in opam package in Ubuntu:
  Fix Released
Status in pageedit package in Ubuntu:
  Confirmed
Status in plasma-desktop package in Ubuntu:
  Confirmed
Status in plasma-welcome package in Ubuntu:
  Fix Released
Status in privacybrowser package in Ubuntu:
  Confirmed
Status in qmapshack package in Ubuntu:
  Confirmed
Status in qutebrowser package in Ubuntu:
  Confirmed
Status in rssguard package in Ubuntu:
  Confirmed
Status in steam package in Ubuntu:
  Fix Committed
Status in supercollider package in Ubuntu:
  Confirmed
Status in tellico package in Ubuntu:
  Fix Released

Bug description:
  Hi, I run Ubuntu development branch 24.04 and I have a problem with
  Epiphany browser 45.1-1 (Gnome Web): program doesn't launch, and I get
  this error

  $ epiphany
  bwrap: Creating new namespace failed: Permission denied

  ** (epiphany:12085): ERROR **: 14:44:35.023: Failed to fully launch 
dbus-proxy: Le processus fils s’est terminé avec le code 1
  Trappe pour point d'arrêt et de trace (core dumped)

  $ epiphany
  bwrap: Creating new namespace failed: Permission denied

  ** (epiphany:30878): ERROR **: 22:22:26.926: Failed to fully launch 
dbus-proxy: Le processus fils s’est terminé avec le code 1
  Trappe pour point d'arrêt et de trace (core dumped)

  Thanks for your help!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/akonadiconsole/+bug/2046844/+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 2056190] Re: Tabs of non-flatpak Firefox (and non-flatpak Firefox-based browsers) crash in Kubuntu 24.04

[Alexander Browne]

Same in Ubuntu desktop (GNOME), so not Kubuntu-specific.

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

Title:
  Tabs of non-flatpak Firefox (and non-flatpak Firefox-based browsers)
  crash in Kubuntu 24.04

Status in firefox package in Ubuntu:
  Confirmed

Bug description:
  I have installed Firefox snap version in order to be able to post the
  bug report on that program, but the bug or problem affects all
  browsers based on Firefox that I was able to test, with the notable
  exception of the flatpak versions.

  Firefox (snap, appimage and local) and browsers based on current
  Firefox, as well as nightly version of Firefox (installed as deb or
  local/portable) don't work after update to Kubuntu 24.04. This happens
  in both X11 and Wayland sessions, with both empty/new profile and my
  customized one.

  The errors are of the form:

  `[Parent 35161, IPC I/O Parent] WARNING: process 35276 exited on signal 11: 
file 
/builds/worker/checkouts/gecko/ipc/chromium/src/base/process_util_posix.cc:265
  [Parent 35161, IPC I/O Parent] WARNING: process 35303 exited on signal 11: 
file 
/builds/worker/checkouts/gecko/ipc/chromium/src/base/process_util_posix.cc:265
  [Parent 35161, IPC I/O Parent] WARNING: process 35315 exited on signal 11: 
file 
/builds/worker/checkouts/gecko/ipc/chromium/src/base/process_util_posix.cc:265
  [Parent 35161, IPC I/O Parent] WARNING: process 35325 exited on signal 11: 
file 
/builds/worker/checkouts/gecko/ipc/chromium/src/base/process_util_posix.cc:265
  [Parent 35161, IPC I/O Parent] WARNING: process 35336 exited on signal 11: 
file 
/builds/worker/checkouts/gecko/ipc/chromium/src/base/process_util_posix.cc:265
  [Parent 35161, IPC I/O Parent] WARNING: process 35345 exited on signal 11: 
file 
/builds/worker/checkouts/gecko/ipc/chromium/src/base/process_util_posix.cc:265
  [Parent 35161, IPC I/O Parent] WARNING: process 35354 exited on signal 11: 
file 
/builds/worker/checkouts/gecko/ipc/chromium/src/base/process_util_posix.cc:265
  [Parent 35161, IPC I/O Parent] WARNING: process 35364 exited on signal 11: 
file 
/builds/worker/checkouts/gecko/ipc/chromium/src/base/process_util_posix.cc:265
  [Parent 35161, IPC I/O Parent] WARNING: process 35368 exited on signal 11: 
file 
/builds/worker/checkouts/gecko/ipc/chromium/src/base/process_util_posix.cc:265`

  More details on other browsers:
  https://unix.stackexchange.com/q/771657/341192

  Description:Ubuntu Noble Numbat (development branch)
  Release:24.04

  Programs affected in basically the same way are: Firefox 123 snap,
  Firefox 123 (local/portable), Firefox 125 nightly, Midori 11.2
  (Firefox-based), Waterfox G6.0.9,  Firefox 119 appimage, Librewolf
  appimage, Mullwad (Ff-ESR-based) appimage...

  Note that Palemoon and SeaMonkey are NOT affected. Chrome-based-
  browsers are not affected.

  Flatpak versions of Firefox 123, Waterfox, Librewolf and Floorp
  (Firefox-ESR-based) are NOT affected by this problem.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/2056190/+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 2051870] [NEW] With font scaling, text in the GNOME Shell search box is cut off

[Alexander Browne]

Public bug reported:

If you increase font scaling – either with Gnome Tweaks > Fonts >
Scaling Factor or gsettings org.gnome.desktop.interface text-scaling-
factor – text in the GNOME Shell search box is cut off.

Text scaling can help with hidpi screens and is an accessibility
feature.

I noticed this a while ago but I finally got around to testing it
systematically in December with the then-current noble daily build and
reported it upstream (https://github.com/ubuntu/yaru/issues/4023). I
today confirmed it's still present in an updated Noble install. The
issue does not occur with the default GNOME/Adwaita Shell theme
installed with gnome-session or other OSes like OpenSUSE Tumbleweed so
it seems like a Yaru theme issue.

My upstream bug report (https://github.com/ubuntu/yaru/issues/4023) has
examples with screenshots.

ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: yaru-theme-gnome-shell 23.10.0-0ubuntu2
ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3
Uname: Linux 6.6.0-14-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.27.0-0ubuntu6
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Wed Jan 31 12:03:33 2024
Dependencies:
 
InstallationDate: Installed on 2023-03-16 (321 days ago)
InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20230310)
PackageArchitecture: all
ProcEnviron:
 LANG=en_US.UTF-8
 PATH=(custom, no user)
 SHELL=/bin/bash
 TERM=xterm-256color
 XDG_RUNTIME_DIR=
SourcePackage: yaru-theme
UpgradeStatus: Upgraded to noble on 2023-12-08 (54 days ago)

** Affects: yaru-theme (Ubuntu)
 Importance: Undecided
 Status: New


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

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

Title:
   With font scaling, text in the GNOME Shell search box is cut off

Status in yaru-theme package in Ubuntu:
  New

Bug description:
  If you increase font scaling – either with Gnome Tweaks > Fonts >
  Scaling Factor or gsettings org.gnome.desktop.interface text-scaling-
  factor – text in the GNOME Shell search box is cut off.

  Text scaling can help with hidpi screens and is an accessibility
  feature.

  I noticed this a while ago but I finally got around to testing it
  systematically in December with the then-current noble daily build and
  reported it upstream (https://github.com/ubuntu/yaru/issues/4023). I
  today confirmed it's still present in an updated Noble install. The
  issue does not occur with the default GNOME/Adwaita Shell theme
  installed with gnome-session or other OSes like OpenSUSE Tumbleweed so
  it seems like a Yaru theme issue.

  My upstream bug report (https://github.com/ubuntu/yaru/issues/4023)
  has examples with screenshots.

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: yaru-theme-gnome-shell 23.10.0-0ubuntu2
  ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3
  Uname: Linux 6.6.0-14-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.27.0-0ubuntu6
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jan 31 12:03:33 2024
  Dependencies:
   
  InstallationDate: Installed on 2023-03-16 (321 days ago)
  InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20230310)
  PackageArchitecture: all
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  SourcePackage: yaru-theme
  UpgradeStatus: Upgraded to noble on 2023-12-08 (54 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/yaru-theme/+bug/2051870/+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 1711538] Re: Tap-to-click does not work on the GDM login screen

[Alexander Browne]

Still an issue with current releases. Default GNOME/libinputa doesn't
enable tap-to-click, but Ubuntu does for the GNOME desktop, and
therefore it should also for GDM.

Easy workaround posted in duplicate bug:
https://bugs.launchpad.net/ubuntu-manual-tests/+bug/1968315/comments/1

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

Title:
  Tap-to-click does not work on the GDM login screen

Status in gnome-control-center:
  Fix Released
Status in GNOME Settings Daemon:
  Won't Fix
Status in gdm3 package in Ubuntu:
  Triaged
Status in gnome-control-center package in Ubuntu:
  Triaged

Bug description:
  Tap-to-click does not work in GDM login

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gdm3 3.25.90.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
  Uname: Linux 4.12.0-11-generic x86_64
  ApportVersion: 2.20.6-0ubuntu5
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Aug 18 16:16:56 2017
  InstallationDate: Installed on 2017-05-04 (105 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170503)
  SourcePackage: gdm3
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-control-center/+bug/1711538/+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 1922047]

[Alexander Browne]

> in gtk, kinetic scrolling stops after you put a finger on the touchpad
(zwp_pointer_gesture_hold_v1 event), but in firefox it doesn't, you have
to wait

In GTK 4, and Firefox uses GTK 3. So either someone need to add it to
GTK 3 or Firefox needs to use to GTK 4.

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

Title:
  Touchpad scrolling is too fast

Status in Mozilla Firefox:
  Confirmed
Status in GTK+:
  Fix Released
Status in Mutter:
  New
Status in firefox package in Ubuntu:
  Confirmed
Status in gtk+3.0 package in Ubuntu:
  Confirmed
Status in gtk4 package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  This is an issue which has troubled me for a while. Anecdotally,
  scrolling feels way too fast in GNOME on Wayland compared to on X11. I
  finally tested it semi-scientifically, and it seems like GNOME on
  Wayland scrolls almost exactly 1.5x faster than GNOME on X11.

  I tested this by testing how many lines are scrolled from a full two-
  finger touchpad swipe from the bottom of my touchpad to the top of my
  touchpad, and logged a few attempts in both X and Wayland. I kept
  track of the results in this spreadsheet:
  
https://docs.google.com/spreadsheets/d/17EaBM5Pgt7GdnnzcN2Vchk4kfT7IZ6i4qZ0zpVRGLhc/edit?usp=sharing

  I scrolled in one of my own GTK applications
  (https://github.com/mortie/lograt) because it lets me easily see how
  many lines I scrolled. Attach is a video of one full scroll on X11 and
  one full scroll on Wayland.

  This testing was performed on a Dell XPS 13 9343, but I've also used
  Ubuntu on a Dell XPS 9575 where GNOME Wayland scrolling also feels way
  too fast. I don't have other hardware to test on.

  This has been an issue on both Ubuntu 20.10 and Ubuntu 21.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: gnome-shell 3.38.4-1ubuntu1
  ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11.7
  Uname: Linux 5.11.0-13-generic x86_64
  ApportVersion: 2.20.11-0ubuntu61
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar 31 11:44:04 2021
  DisplayManager: gdm3
  InstallationDate: Installed on 2019-11-21 (495 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  RelatedPackageVersions: mutter-common 3.38.4-1ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to hirsute on 2021-03-16 (14 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/firefox/+bug/1922047/+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 2002886] Re: Can't copy and paste from Geany (and SciTE?) in Wayland with GTK 3.24.35

[Alexander Browne]

Resolved since GTK was updated to 3.24.36. (Tested with
3.24.36-1ubuntu1.)

** Changed in: gtk+3.0 (Ubuntu)
   Status: New => Fix Released

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

Title:
  Can't copy and paste from Geany (and SciTE?) in Wayland with GTK
  3.24.35

Status in gtk+3.0 package in Ubuntu:
  Fix Released

Bug description:
  With GTK 3.24.35, when running under Wayland, it's not possible to
  copy and paste from Geany. (Others report the same issue with SciTE,
  which also uses the Scintilla editor.)

  The Geany upsteam bug isolated the issue to a GTK change
  (https://github.com/geany/geany/issues/3345#issuecomment-1360370992).

  The GTK bug (https://gitlab.gnome.org/GNOME/gtk/-/issues/5397) was
  resolved
  
(https://gitlab.gnome.org/GNOME/gtk/-/commit/eca445672a48ac4a870790efa63339f8d974c2fd)
  and the fix is in GTK 3.24.36.

  I installed the libgtk-3-0_3.24.36-1_amd64.deb and
  libgtk-3-common_3.24.36-1_all.deb packages from Debian on a Lunar test
  system and this did resolve the issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: libgtk-3-0 3.24.35-3ubuntu1
  ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7
  Uname: Linux 5.19.0-21-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.24.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jan 14 14:22:01 2023
  InstallationDate: Installed on 2022-12-28 (17 days ago)
  InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20221228)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gtk+3.0
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/2002886/+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 2002886] [NEW] Can't copy and paste from Geany (and SciTE?) in Wayland with GTK 3.24.35

[Alexander Browne]

Public bug reported:

With GTK 3.24.35, when running under Wayland, it's not possible to copy
and paste from Geany. (Others report the same issue with SciTE, which
also uses the Scintilla editor.)

The Geany upsteam bug isolated the issue to a GTK change
(https://github.com/geany/geany/issues/3345#issuecomment-1360370992).

The GTK bug (https://gitlab.gnome.org/GNOME/gtk/-/issues/5397) was
resolved
(https://gitlab.gnome.org/GNOME/gtk/-/commit/eca445672a48ac4a870790efa63339f8d974c2fd)
and the fix is in GTK 3.24.36.

I installed the libgtk-3-0_3.24.36-1_amd64.deb and
libgtk-3-common_3.24.36-1_all.deb packages from Debian on a Lunar test
system and this did resolve the issue.

ProblemType: Bug
DistroRelease: Ubuntu 23.04
Package: libgtk-3-0 3.24.35-3ubuntu1
ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7
Uname: Linux 5.19.0-21-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.24.0-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Sat Jan 14 14:22:01 2023
InstallationDate: Installed on 2022-12-28 (17 days ago)
InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20221228)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: gtk+3.0
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: gtk+3.0 (Ubuntu)
 Importance: Undecided
 Status: New


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

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

Title:
  Can't copy and paste from Geany (and SciTE?) in Wayland with GTK
  3.24.35

Status in gtk+3.0 package in Ubuntu:
  New

Bug description:
  With GTK 3.24.35, when running under Wayland, it's not possible to
  copy and paste from Geany. (Others report the same issue with SciTE,
  which also uses the Scintilla editor.)

  The Geany upsteam bug isolated the issue to a GTK change
  (https://github.com/geany/geany/issues/3345#issuecomment-1360370992).

  The GTK bug (https://gitlab.gnome.org/GNOME/gtk/-/issues/5397) was
  resolved
  
(https://gitlab.gnome.org/GNOME/gtk/-/commit/eca445672a48ac4a870790efa63339f8d974c2fd)
  and the fix is in GTK 3.24.36.

  I installed the libgtk-3-0_3.24.36-1_amd64.deb and
  libgtk-3-common_3.24.36-1_all.deb packages from Debian on a Lunar test
  system and this did resolve the issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: libgtk-3-0 3.24.35-3ubuntu1
  ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7
  Uname: Linux 5.19.0-21-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.24.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jan 14 14:22:01 2023
  InstallationDate: Installed on 2022-12-28 (17 days ago)
  InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20221228)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gtk+3.0
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/2002886/+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 1993581] Re: [snap] posix_spawn: No such file or directory

[Alexander Browne]

Yes, snap revision 2183 launches for me! I tried with two computers
running 22.10.

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

Title:
  [snap] posix_spawn: No such file or directory

Status in chromium-browser package in Ubuntu:
  Fix Committed

Bug description:
  Chromium from the edge channel fails to launch with

% chromium
[17618:17618:1019/163156.976437:FATAL:spawn_subprocess.cc(221)] 
posix_spawn: No such file or directory (2)

% snap info chromium
channels:
  latest/stable:106.0.5249.119 2022-10-14 (2136) 150MB -
  latest/candidate: 106.0.5249.119 2022-10-13 (2136) 150MB -
  latest/beta:  107.0.5304.36  2022-10-13 (2135) 152MB -
  latest/edge:  108.0.5355.0   2022-10-18 (2146) 153MB -
installed:  108.0.5355.0  (2146) 153MB -

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1993581/+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 1993581] Re: [snap] posix_spawn: No such file or directory

[Alexander Browne]

And just to confirm, Google builds from https://download-
chromium.appspot.com (now version 109.0.5396.0) open without issue.

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

Title:
  [snap] posix_spawn: No such file or directory

Status in chromium-browser package in Ubuntu:
  In Progress

Bug description:
  Chromium from the edge channel fails to launch with

% chromium
[17618:17618:1019/163156.976437:FATAL:spawn_subprocess.cc(221)] 
posix_spawn: No such file or directory (2)

% snap info chromium
channels:
  latest/stable:106.0.5249.119 2022-10-14 (2136) 150MB -
  latest/candidate: 106.0.5249.119 2022-10-13 (2136) 150MB -
  latest/beta:  107.0.5304.36  2022-10-13 (2135) 152MB -
  latest/edge:  108.0.5355.0   2022-10-18 (2146) 153MB -
installed:  108.0.5355.0  (2146) 153MB -

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1993581/+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 1993581] Re: [snap] posix_spawn: No such file or directory

[Alexander Browne]

With the latest version just released to the beta channel, revision
2180, I no longer see the "spawn" lines, but it still is not starting
up for me (Ubuntu 22.10). This is all I get:

$ chromium
Trace/breakpoint trap (core dumped)

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

Title:
  [snap] posix_spawn: No such file or directory

Status in chromium-browser package in Ubuntu:
  In Progress

Bug description:
  Chromium from the edge channel fails to launch with

% chromium
[17618:17618:1019/163156.976437:FATAL:spawn_subprocess.cc(221)] 
posix_spawn: No such file or directory (2)

% snap info chromium
channels:
  latest/stable:106.0.5249.119 2022-10-14 (2136) 150MB -
  latest/candidate: 106.0.5249.119 2022-10-13 (2136) 150MB -
  latest/beta:  107.0.5304.36  2022-10-13 (2135) 152MB -
  latest/edge:  108.0.5355.0   2022-10-18 (2146) 153MB -
installed:  108.0.5355.0  (2146) 153MB -

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1993581/+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 1993581] Re: [snap] posix_spawn: No such file or directory

[Alexander Browne]

$ chromium
[215800:215800:1031/155854.374117:FATAL:spawn_subprocess.cc(221)] posix_spawn: 
No such file or directory (2)
Trace/breakpoint trap (core dumped)

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

Title:
  [snap] posix_spawn: No such file or directory

Status in chromium-browser package in Ubuntu:
  In Progress

Bug description:
  Chromium from the edge channel fails to launch with

% chromium
[17618:17618:1019/163156.976437:FATAL:spawn_subprocess.cc(221)] 
posix_spawn: No such file or directory (2)

% snap info chromium
channels:
  latest/stable:106.0.5249.119 2022-10-14 (2136) 150MB -
  latest/candidate: 106.0.5249.119 2022-10-13 (2136) 150MB -
  latest/beta:  107.0.5304.36  2022-10-13 (2135) 152MB -
  latest/edge:  108.0.5355.0   2022-10-18 (2146) 153MB -
installed:  108.0.5355.0  (2146) 153MB -

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1993581/+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 1993581] Re: [snap] posix_spawn: No such file or directory

[Alexander Browne]

Seeing this with the today's beta build: 108.0.5359.22 (2177).

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

Title:
  [snap] posix_spawn: No such file or directory

Status in chromium-browser package in Ubuntu:
  In Progress

Bug description:
  Chromium from the edge channel fails to launch with

% chromium
[17618:17618:1019/163156.976437:FATAL:spawn_subprocess.cc(221)] 
posix_spawn: No such file or directory (2)

% snap info chromium
channels:
  latest/stable:106.0.5249.119 2022-10-14 (2136) 150MB -
  latest/candidate: 106.0.5249.119 2022-10-13 (2136) 150MB -
  latest/beta:  107.0.5304.36  2022-10-13 (2135) 152MB -
  latest/edge:  108.0.5355.0   2022-10-18 (2146) 153MB -
installed:  108.0.5355.0  (2146) 153MB -

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1993581/+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 1990986] Re: With iwd, doesn't connect to WPA2 Enterprise network (e.g. eduroam)

[Alexander Browne]

Reopening as suggested on the Ubuntu forum, so this issue can be looked
at before iwd becomes default.


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

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

Title:
  With iwd, doesn't connect to WPA2 Enterprise network (e.g. eduroam)

Status in iwd package in Ubuntu:
  New

Bug description:
  I believe my Kinetic system installed iwd with updates today, and now
  I am unable to my University's WPA2 Enterprise network eduroam. There
  is a no graphical error message, it just never connects. I tried
  forgetting the network and re-adding, and again there's no error, but
  no connection is established. Looking in the Logs app, I see messages
  like "Failed to add new connection: (5) 802.1x connections must have
  IWD provisioning files".

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: iwd 1.30-1ubuntu1
  ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0
  Uname: Linux 5.19.0-15-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.23.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Sep 27 09:32:38 2022
  InstallationDate: Installed on 2022-08-25 (32 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220825)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: iwd
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iwd/+bug/1990986/+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 1990986] Re: With iwd, doesn't connect to WPA2 Enterprise network (e.g. eduroam)

[Alexander Browne]

Todays updates included network-manager 1.40.0-1ubuntu2, and after `apt
autopurge` iwd was removed. This wi-fi network connection is working
again normally since.

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

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

Title:
  With iwd, doesn't connect to WPA2 Enterprise network (e.g. eduroam)

Status in iwd package in Ubuntu:
  Fix Released

Bug description:
  I believe my Kinetic system installed iwd with updates today, and now
  I am unable to my University's WPA2 Enterprise network eduroam. There
  is a no graphical error message, it just never connects. I tried
  forgetting the network and re-adding, and again there's no error, but
  no connection is established. Looking in the Logs app, I see messages
  like "Failed to add new connection: (5) 802.1x connections must have
  IWD provisioning files".

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: iwd 1.30-1ubuntu1
  ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0
  Uname: Linux 5.19.0-15-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.23.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Sep 27 09:32:38 2022
  InstallationDate: Installed on 2022-08-25 (32 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220825)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: iwd
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iwd/+bug/1990986/+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 1990986] [NEW] With iwd, doesn't connect to WPA2 Enterprise network (e.g. eduroam)

[Alexander Browne]

Public bug reported:

I believe my Kinetic system installed iwd with updates today, and now I
am unable to my University's WPA2 Enterprise network eduroam. There is a
no graphical error message, it just never connects. I tried forgetting
the network and re-adding, and again there's no error, but no connection
is established. Looking in the Logs app, I see messages like "Failed to
add new connection: (5) 802.1x connections must have IWD provisioning
files".

ProblemType: Bug
DistroRelease: Ubuntu 22.10
Package: iwd 1.30-1ubuntu1
ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0
Uname: Linux 5.19.0-15-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.23.0-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Tue Sep 27 09:32:38 2022
InstallationDate: Installed on 2022-08-25 (32 days ago)
InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220825)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: iwd
UpgradeStatus: No upgrade log present (probably fresh install)

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


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

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

Title:
  With iwd, doesn't connect to WPA2 Enterprise network (e.g. eduroam)

Status in iwd package in Ubuntu:
  New

Bug description:
  I believe my Kinetic system installed iwd with updates today, and now
  I am unable to my University's WPA2 Enterprise network eduroam. There
  is a no graphical error message, it just never connects. I tried
  forgetting the network and re-adding, and again there's no error, but
  no connection is established. Looking in the Logs app, I see messages
  like "Failed to add new connection: (5) 802.1x connections must have
  IWD provisioning files".

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: iwd 1.30-1ubuntu1
  ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0
  Uname: Linux 5.19.0-15-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.23.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Sep 27 09:32:38 2022
  InstallationDate: Installed on 2022-08-25 (32 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220825)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: iwd
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iwd/+bug/1990986/+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 1968377] Re: [snap] New Chromium icon, not yet used by Snap

[Alexander Browne]

The new icon looks good 

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

Title:
  [snap] New Chromium icon, not yet used by Snap

Status in chromium-browser package in Ubuntu:
  Fix Released

Bug description:
  Google updated the Chrome/Chromium icons recently (see more at
  https://twitter.com/elvin_not_11/status/1489647032201465861), but I
  don't think the Snap icon has been updated.

  Here's the Chromium icons on the Chromium source GitHub mirror, which
  was easier for me to search:
  https://github.com/chromium/chromium/tree/main/chrome/app/theme/chromium/linux

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1968377/+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 1989131] Re: [snap] What about PDF MimeType in .desktop file?

[Alexander Browne]

Fair enough :-) I think PDF is pretty major.

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

Title:
  [snap] What about PDF MimeType in .desktop file?

Status in chromium-browser package in Ubuntu:
  Triaged

Bug description:
  I see with a recent commit (https://git.launchpad.net/~chromium-
  team/chromium-browser/+git/snap-from-
  source/commit/?id=f96f95b0b511f0943320af8aed1a41599d921b2f) you've
  added more MimeType entries in the .desktop file. What about PDF,
  since Chromium has a pretty good built-in PDF viewer?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1989131/+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 1989131] [NEW] [snap] What about PDF MimeType in .desktop file?

[Alexander Browne]

Public bug reported:

I see with a recent commit (https://git.launchpad.net/~chromium-
team/chromium-browser/+git/snap-from-
source/commit/?id=f96f95b0b511f0943320af8aed1a41599d921b2f) you've added
more MimeType entries in the .desktop file. What about PDF, since
Chromium has a pretty good built-in PDF viewer?

** Affects: chromium-browser (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  [snap] What about PDF MimeType in .desktop file?

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  I see with a recent commit (https://git.launchpad.net/~chromium-
  team/chromium-browser/+git/snap-from-
  source/commit/?id=f96f95b0b511f0943320af8aed1a41599d921b2f) you've
  added more MimeType entries in the .desktop file. What about PDF,
  since Chromium has a pretty good built-in PDF viewer?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1989131/+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 1968377] Re: [snap] New Chromium icon, not yet used by Snap

[Alexander Browne]

Hey Nathan,

Thanks for the instructions! I think I made a merge proposal correctly:
https://code.launchpad.net/~elcste/chromium-browser/+git/chromium-
browser/+merge/429317

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

Title:
  [snap] New Chromium icon, not yet used by Snap

Status in chromium-browser package in Ubuntu:
  Triaged

Bug description:
  Google updated the Chrome/Chromium icons recently (see more at
  https://twitter.com/elvin_not_11/status/1489647032201465861), but I
  don't think the Snap icon has been updated.

  Here's the Chromium icons on the Chromium source GitHub mirror, which
  was easier for me to search:
  https://github.com/chromium/chromium/tree/main/chrome/app/theme/chromium/linux

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1968377/+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 1897454] Re: [snap] Chromium has Wayland support disabled

[Alexander Browne]

@copong Wayland for Chromium is definitely still experimental, but is
under active development, helped because ChromeOS is/will use it.

I'd suggest you compare with an upstream build: https://download-
chromium.appspot.com/

Just download, unpack and run the chromium binary. Since the snap's
config is all in ~/snap/chromium, and this version just uses ~/
directly, it's easy to use along side.

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

Title:
  [snap] Chromium has Wayland support disabled

Status in chromium-browser package in Ubuntu:
  Fix Committed

Bug description:
  Since v87 Chromium ships with support for Ozone/Wayland:
  https://www.phoronix.com/scan.php?page=news_item=Chrome-87-Ozone-Try-Again.

  This build flag is not disabled in dev (edge) channel build, so it should be 
possible to run Chromium with flags
--enable-features=UseOzonePlatform --ozone-platform=wayland.

  This does not work due to environment variable DISABLE_WAYLAND set to 1 here:
  
https://git.launchpad.net/~chromium-team/chromium-browser/+git/snap-from-source/tree/snapcraft.yaml?h=dev#n18.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1897454/+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 1897454] Re: [snap] Chromium has Wayland support disabled

[Alexander Browne]

I can confirm wayland works for the version 102.0.5005.40 snap just
built and released in the beta channel. Thanks!

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

Title:
  [snap] Chromium has Wayland support disabled

Status in chromium-browser package in Ubuntu:
  Fix Committed

Bug description:
  Since v87 Chromium ships with support for Ozone/Wayland:
  https://www.phoronix.com/scan.php?page=news_item=Chrome-87-Ozone-Try-Again.

  This build flag is not disabled in dev (edge) channel build, so it should be 
possible to run Chromium with flags
--enable-features=UseOzonePlatform --ozone-platform=wayland.

  This does not work due to environment variable DISABLE_WAYLAND set to 1 here:
  
https://git.launchpad.net/~chromium-team/chromium-browser/+git/snap-from-source/tree/snapcraft.yaml?h=dev#n18.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1897454/+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 1958267] Re: "Connection failed" for WPA Enterprise network (e.g. eduroam)

[Alexander Browne]

@seb128

I got another reply from someone up the chain:

We use TLS for the outer tunnel for 802.1x. The inner tunnel is 
connecting using AES with rotating keys. The work around is all 
that we can offer at this time as we are waiting for an update 
from the vender as to where this is on their roadmap.

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

Title:
  "Connection failed" for WPA Enterprise network (e.g. eduroam)

Status in wpa package in Ubuntu:
  Confirmed
Status in wpa source package in Jammy:
  Confirmed

Bug description:
  With the current jammy version of wpasupplicant (2:2.10-1), I cannot
  connect to the WPA Enterprise network eduroam, which is used by
  Universities worldwide. I get a "Connection failed" message or a
  request to re-enter the password.

  - I've re-tried the credentials: no fix ;-)

  - Tried a 21.10 live session on the same machine: works fine!

  - Manually downgraded wpasupplicant to the impish version
  (2:2.9.0-21build1): connected normally.

  - Upgraded wpasupplicant to the latest version: fails to connect
  again.

  
  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: wpasupplicant 2:2.10-1
  ProcVersionSignature: Ubuntu 5.15.0-17.17-generic 5.15.12
  Uname: Linux 5.15.0-17-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu75
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 18 09:56:23 2022
  InstallationDate: Installed on 2021-11-30 (48 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211130)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.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/1958267/+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 1958267] Re: "Connection failed" for WPA Enterprise network (e.g. eduroam)

[Alexander Browne]

@seb128 My University closed my ticket after I confirmed the workaround
works to get connected :-/ I'm not 100% sure they understood the real
source of the issue. I replied, but don't have a big expectation that
they will do anything. Hopefully someone at another institution that
also uses eduroam is successful at getting the needed changes made and
that they propagate to other institutions.

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

Title:
  "Connection failed" for WPA Enterprise network (e.g. eduroam)

Status in wpa package in Ubuntu:
  Confirmed
Status in wpa source package in Jammy:
  Confirmed

Bug description:
  With the current jammy version of wpasupplicant (2:2.10-1), I cannot
  connect to the WPA Enterprise network eduroam, which is used by
  Universities worldwide. I get a "Connection failed" message or a
  request to re-enter the password.

  - I've re-tried the credentials: no fix ;-)

  - Tried a 21.10 live session on the same machine: works fine!

  - Manually downgraded wpasupplicant to the impish version
  (2:2.9.0-21build1): connected normally.

  - Upgraded wpasupplicant to the latest version: fails to connect
  again.

  
  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: wpasupplicant 2:2.10-1
  ProcVersionSignature: Ubuntu 5.15.0-17.17-generic 5.15.12
  Uname: Linux 5.15.0-17-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu75
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 18 09:56:23 2022
  InstallationDate: Installed on 2021-11-30 (48 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211130)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.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/1958267/+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 1958267] Re: "Connection failed" for WPA Enterprise network (e.g. eduroam)

[Alexander Browne]

The workaround linked to in #11 has worked for me:
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1963834/comments/7

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

Title:
  "Connection failed" for WPA Enterprise network (e.g. eduroam)

Status in wpa package in Ubuntu:
  Confirmed
Status in wpa source package in Jammy:
  Confirmed

Bug description:
  With the current jammy version of wpasupplicant (2:2.10-1), I cannot
  connect to the WPA Enterprise network eduroam, which is used by
  Universities worldwide. I get a "Connection failed" message or a
  request to re-enter the password.

  - I've re-tried the credentials: no fix ;-)

  - Tried a 21.10 live session on the same machine: works fine!

  - Manually downgraded wpasupplicant to the impish version
  (2:2.9.0-21build1): connected normally.

  - Upgraded wpasupplicant to the latest version: fails to connect
  again.

  
  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: wpasupplicant 2:2.10-1
  ProcVersionSignature: Ubuntu 5.15.0-17.17-generic 5.15.12
  Uname: Linux 5.15.0-17-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu75
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 18 09:56:23 2022
  InstallationDate: Installed on 2021-11-30 (48 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211130)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.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/1958267/+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 1958267] Re: "Connection failed" for WPA Enterprise network (e.g. eduroam)

[Alexander Browne]

** Summary changed:

- "Connection failed" for WPA Enterprise network eduroam
+ "Connection failed" for WPA Enterprise network (e.g. eduroam)

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

Title:
  "Connection failed" for WPA Enterprise network (e.g. eduroam)

Status in wpa package in Ubuntu:
  Confirmed
Status in wpa source package in Jammy:
  Confirmed

Bug description:
  With the current jammy version of wpasupplicant (2:2.10-1), I cannot
  connect to the WPA Enterprise network eduroam, which is used by
  Universities worldwide. I get a "Connection failed" message or a
  request to re-enter the password.

  - I've re-tried the credentials: no fix ;-)

  - Tried a 21.10 live session on the same machine: works fine!

  - Manually downgraded wpasupplicant to the impish version
  (2:2.9.0-21build1): connected normally.

  - Upgraded wpasupplicant to the latest version: fails to connect
  again.

  
  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: wpasupplicant 2:2.10-1
  ProcVersionSignature: Ubuntu 5.15.0-17.17-generic 5.15.12
  Uname: Linux 5.15.0-17-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu75
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 18 09:56:23 2022
  InstallationDate: Installed on 2021-11-30 (48 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211130)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.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/1958267/+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 1958267] Re: "Connection failed" for WPA Enterprise network eduroam

[Alexander Browne]

FWIW my university's support team replied that they don't support Linux
devices but they would forward my message to the network team. I haven't
heard anything since.

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

Title:
  "Connection failed" for WPA Enterprise network eduroam

Status in wpa package in Ubuntu:
  Confirmed
Status in wpa source package in Jammy:
  Confirmed

Bug description:
  With the current jammy version of wpasupplicant (2:2.10-1), I cannot
  connect to the WPA Enterprise network eduroam, which is used by
  Universities worldwide. I get a "Connection failed" message or a
  request to re-enter the password.

  - I've re-tried the credentials: no fix ;-)

  - Tried a 21.10 live session on the same machine: works fine!

  - Manually downgraded wpasupplicant to the impish version
  (2:2.9.0-21build1): connected normally.

  - Upgraded wpasupplicant to the latest version: fails to connect
  again.

  
  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: wpasupplicant 2:2.10-1
  ProcVersionSignature: Ubuntu 5.15.0-17.17-generic 5.15.12
  Uname: Linux 5.15.0-17-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu75
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 18 09:56:23 2022
  InstallationDate: Installed on 2021-11-30 (48 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211130)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.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/1958267/+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 1968377] Re: New Chromium icon, not yet used by Snap

[Alexander Browne]

Looking at the snapcraft.yaml (https://git.launchpad.net/~chromium-
team/chromium-browser/+git/snap-from-source/tree/snapcraft.yaml#n233)

I think what needs to change is

  cp chrome/app/theme/chromium/product_logo_256.png
$SNAPCRAFT_PART_INSTALL/chromium.png

to

  cp chrome/app/theme/chromium/linux/product_logo_256.png
$SNAPCRAFT_PART_INSTALL/chromium.png

That is, add `linux` to the icon source path, since these new icons
differ by platform.

(If the code was on GitHub I'd submit a PR, but I'm very much a beginner
with git and haven't done it on LP before.)

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

Title:
  New Chromium icon, not yet used by Snap

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  Google updated the Chrome/Chromium icons recently (see more at
  https://twitter.com/elvin_not_11/status/1489647032201465861), but I
  don't think the Snap icon has been updated.

  Here's the Chromium icons on the Chromium source GitHub mirror, which
  was easier for me to search:
  https://github.com/chromium/chromium/tree/main/chrome/app/theme/chromium/linux

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1968377/+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 1968377] [NEW] New Chromium icon, not yet used by Snap

[Alexander Browne]

Public bug reported:

Google updated the Chrome/Chromium icons recently (see more at
https://twitter.com/elvin_not_11/status/1489647032201465861), but I
don't think the Snap icon has been updated.

Here's the Chromium icons on the Chromium source GitHub mirror, which
was easier for me to search:
https://github.com/chromium/chromium/tree/main/chrome/app/theme/chromium/linux

** Affects: chromium-browser (Ubuntu)
 Importance: Undecided
 Status: New

** Description changed:

- Google updated the Chrome/Chromium icons recently, but I don't think the
- Snap icon has been updated.
+ Google updated the Chrome/Chromium icons recently (see more at
+ https://twitter.com/elvin_not_11/status/1489647032201465861), but I
+ don't think the Snap icon has been updated.
  
  Here's the icons on the GitHub mirror, which was easier for me to
  search:
  https://github.com/chromium/chromium/tree/main/chrome/app/theme/chromium/linux

** Description changed:

  Google updated the Chrome/Chromium icons recently (see more at
  https://twitter.com/elvin_not_11/status/1489647032201465861), but I
  don't think the Snap icon has been updated.
  
- Here's the icons on the GitHub mirror, which was easier for me to
- search:
+ Here's the Chromium icons on the Chromium source GitHub mirror, which
+ was easier for me to search:
  https://github.com/chromium/chromium/tree/main/chrome/app/theme/chromium/linux

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

Title:
  New Chromium icon, not yet used by Snap

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  Google updated the Chrome/Chromium icons recently (see more at
  https://twitter.com/elvin_not_11/status/1489647032201465861), but I
  don't think the Snap icon has been updated.

  Here's the Chromium icons on the Chromium source GitHub mirror, which
  was easier for me to search:
  https://github.com/chromium/chromium/tree/main/chrome/app/theme/chromium/linux

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1968377/+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 1958267] Re: "Connection failed" for WPA Enterprise network eduroam

[Alexander Browne]

@seb128

Sorry if that sounded browbeating. My response is more like
"unfortunate, but understandable". Someone has to be first, even if
MS/Apple seem OK to leave it working.

Thanks for finding the Fedora info. I had just wondered about other
distros. Looks like the other bug they link to is a dupe of this?
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1961558

Can I suggest this be documented in the release notes, at least the
issue, but maybe even including the workaround? FWIW, I see now the file
suggested in the workaround above (/usr/lib/ssl/openssl.cnf) is a link
to /etc/ssl/openssl.cnf, so I think it shouldn't get overwritten as I
thought it might.

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

Title:
  "Connection failed" for WPA Enterprise network eduroam

Status in wpa package in Ubuntu:
  Confirmed
Status in wpa source package in Jammy:
  Confirmed

Bug description:
  With the current jammy version of wpasupplicant (2:2.10-1), I cannot
  connect to the WPA Enterprise network eduroam, which is used by
  Universities worldwide. I get a "Connection failed" message or a
  request to re-enter the password.

  - I've re-tried the credentials: no fix ;-)

  - Tried a 21.10 live session on the same machine: works fine!

  - Manually downgraded wpasupplicant to the impish version
  (2:2.9.0-21build1): connected normally.

  - Upgraded wpasupplicant to the latest version: fails to connect
  again.

  
  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: wpasupplicant 2:2.10-1
  ProcVersionSignature: Ubuntu 5.15.0-17.17-generic 5.15.12
  Uname: Linux 5.15.0-17-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu75
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 18 09:56:23 2022
  InstallationDate: Installed on 2021-11-30 (48 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211130)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.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/1958267/+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 1958267] Re: "Connection failed" for WPA Enterprise network eduroam

[Alexander Browne]

I've opened a ticket with my University's IT dept with the suggestion.

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

Title:
  "Connection failed" for WPA Enterprise network eduroam

Status in wpa package in Ubuntu:
  Confirmed
Status in wpa source package in Jammy:
  Confirmed

Bug description:
  With the current jammy version of wpasupplicant (2:2.10-1), I cannot
  connect to the WPA Enterprise network eduroam, which is used by
  Universities worldwide. I get a "Connection failed" message or a
  request to re-enter the password.

  - I've re-tried the credentials: no fix ;-)

  - Tried a 21.10 live session on the same machine: works fine!

  - Manually downgraded wpasupplicant to the impish version
  (2:2.9.0-21build1): connected normally.

  - Upgraded wpasupplicant to the latest version: fails to connect
  again.

  
  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: wpasupplicant 2:2.10-1
  ProcVersionSignature: Ubuntu 5.15.0-17.17-generic 5.15.12
  Uname: Linux 5.15.0-17-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu75
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 18 09:56:23 2022
  InstallationDate: Installed on 2021-11-30 (48 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211130)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.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/1958267/+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 1958267] Re: "Connection failed" for WPA Enterprise network eduroam

[Alexander Browne]

The workaround also does work for me. (For the record, I appended those
lines at the end of the config file.)

I see the openssl bug is marked wontfix. I think this is unfortunate,
since it means that eduroam (maybe poorly configured, but still) will
work out of the box for Windows and Mac (and Android and iOS) but not
Ubuntu 22.10 LTS.

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

Title:
  "Connection failed" for WPA Enterprise network eduroam

Status in wpa package in Ubuntu:
  Confirmed
Status in wpa source package in Jammy:
  Confirmed

Bug description:
  With the current jammy version of wpasupplicant (2:2.10-1), I cannot
  connect to the WPA Enterprise network eduroam, which is used by
  Universities worldwide. I get a "Connection failed" message or a
  request to re-enter the password.

  - I've re-tried the credentials: no fix ;-)

  - Tried a 21.10 live session on the same machine: works fine!

  - Manually downgraded wpasupplicant to the impish version
  (2:2.9.0-21build1): connected normally.

  - Upgraded wpasupplicant to the latest version: fails to connect
  again.

  
  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: wpasupplicant 2:2.10-1
  ProcVersionSignature: Ubuntu 5.15.0-17.17-generic 5.15.12
  Uname: Linux 5.15.0-17-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu75
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 18 09:56:23 2022
  InstallationDate: Installed on 2021-11-30 (48 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211130)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.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/1958267/+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 1897454] Re: [snap] Chromium has Wayland support disabled

[Alexander Browne]

You could test an upstream build of Chromium: https://download-
chromium.appspot.com/

Since this version is unconfined, it doesn't share config data with the
snap, so it's safe to use alongside the snap for testing.

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

Title:
  [snap] Chromium has Wayland support disabled

Status in chromium-browser package in Ubuntu:
  Confirmed

Bug description:
  Since v87 Chromium ships with support for Ozone/Wayland:
  https://www.phoronix.com/scan.php?page=news_item=Chrome-87-Ozone-Try-Again.

  This build flag is not disabled in dev (edge) channel build, so it should be 
possible to run Chromium with flags
--enable-features=UseOzonePlatform --ozone-platform=wayland.

  This does not work due to environment variable DISABLE_WAYLAND set to 1 here:
  
https://git.launchpad.net/~chromium-team/chromium-browser/+git/snap-from-source/tree/snapcraft.yaml?h=dev#n18.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1897454/+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 1958267] Re: "Connection failed" for WPA Enterprise network eduroam

[Alexander Browne]

Eduroam is a WPA2 Enterprise network. It supported different EAP methods
(https://wiki.geant.org/pages/viewpage.action?pageId=121346284):

- EAP TTLS-PAP
- PEAP
- EAP TLS
- EAP-pwd

I always use the default option selected in Ubuntu Wi-Fi Settings, which
is labeled "Tunneled TLS". But I double-checked some guides and most
recommend PEAP, which I've now also tried and had the same issue with.

Guide from my institution: 
https://it.umn.edu/services-technologies/how-tos/wifi-connect-unix-or-linux-most-major
Another guide: 
https://www.ucl.ac.uk/isd/how-to/connecting-to-eduroam-wi-fi-linux

I usually use the "No CA certificate is required" option as shown in the
second guide.

The "Inner authentication" is the default option, MSCHAPv2.

Log attached. Thanks!


** Attachment added: "log.txt"
   
https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1958267/+attachment/5566574/+files/log.txt

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

Title:
  "Connection failed" for WPA Enterprise network eduroam

Status in wpa package in Ubuntu:
  Incomplete

Bug description:
  With the current jammy version of wpasupplicant (2:2.10-1), I cannot
  connect to the WPA Enterprise network eduroam, which is used by
  Universities worldwide. I get a "Connection failed" message or a
  request to re-enter the password.

  - I've re-tried the credentials: no fix ;-)

  - Tried a 21.10 live session on the same machine: works fine!

  - Manually downgraded wpasupplicant to the impish version
  (2:2.9.0-21build1): connected normally.

  - Upgraded wpasupplicant to the latest version: fails to connect
  again.

  
  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: wpasupplicant 2:2.10-1
  ProcVersionSignature: Ubuntu 5.15.0-17.17-generic 5.15.12
  Uname: Linux 5.15.0-17-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu75
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 18 09:56:23 2022
  InstallationDate: Installed on 2021-11-30 (48 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211130)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.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/1958267/+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 1958267] Re: "Connection failed" for WPA Enterprise network eduroam

[Alexander Browne]

Still an issue with the new wpasupplicant 2:2.10-2 package.

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

Title:
  "Connection failed" for WPA Enterprise network eduroam

Status in wpa package in Ubuntu:
  New

Bug description:
  With the current jammy version of wpasupplicant (2:2.10-1), I cannot
  connect to the WPA Enterprise network eduroam, which is used by
  Universities worldwide. I get a "Connection failed" message or a
  request to re-enter the password.

  - I've re-tried the credentials: no fix ;-)

  - Tried a 21.10 live session on the same machine: works fine!

  - Manually downgraded wpasupplicant to the impish version
  (2:2.9.0-21build1): connected normally.

  - Upgraded wpasupplicant to the latest version: fails to connect
  again.

  
  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: wpasupplicant 2:2.10-1
  ProcVersionSignature: Ubuntu 5.15.0-17.17-generic 5.15.12
  Uname: Linux 5.15.0-17-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu75
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 18 09:56:23 2022
  InstallationDate: Installed on 2021-11-30 (48 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211130)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.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/1958267/+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 1958267] [NEW] "Connection failed" for WPA Enterprise network eduroam

[Alexander Browne]

Public bug reported:

With the current jammy version of wpasupplicant (2:2.10-1), I cannot
connect to the WPA Enterprise network eduroam, which is used by
Universities worldwide. I get a "Connection failed" message or a request
to re-enter the password.

- I've re-tried the credentials: no fix ;-)

- Tried a 21.10 live session on the same machine: works fine!

- Manually downgraded wpasupplicant to the impish version
(2:2.9.0-21build1): connected normally.

- Upgraded wpasupplicant to the latest version: fails to connect again.


ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: wpasupplicant 2:2.10-1
ProcVersionSignature: Ubuntu 5.15.0-17.17-generic 5.15.12
Uname: Linux 5.15.0-17-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.11-0ubuntu75
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Tue Jan 18 09:56:23 2022
InstallationDate: Installed on 2021-11-30 (48 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211130)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: wpa
UpgradeStatus: No upgrade log present (probably fresh install)

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


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

** Description changed:

  With the current jammy version of wpasupplicant (2:2.10-1), I cannot
  connect to the WPA Enterprise network eduroam, which is used by
- Universities worldwide. I get a "Connection failed" message or q request
+ Universities worldwide. I get a "Connection failed" message or a request
  to re-enter the password.
  
  - I've re-tried the credentials: no fix ;-)
+ 
  - Tried a 21.10 live session on the same machine: works fine!
- - Manually downgraded wpasupplicant to the impish version (2:2.9.0-21build1): 
connected normally.
- - Upgraded wpasupplicant back to the latest version: fails to connect again.
+ 
+ - Manually downgraded wpasupplicant to the impish version
+ (2:2.9.0-21build1): connected normally.
+ 
+ - Upgraded wpasupplicant to the latest version: fails to connect again.
+ 
  
  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: wpasupplicant 2:2.10-1
  ProcVersionSignature: Ubuntu 5.15.0-17.17-generic 5.15.12
  Uname: Linux 5.15.0-17-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu75
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 18 09:56:23 2022
  InstallationDate: Installed on 2021-11-30 (48 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211130)
  ProcEnviron:
-  TERM=xterm-256color
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=
-  LANG=en_US.UTF-8
-  SHELL=/bin/bash
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
  SourcePackage: wpa
  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 wpa in Ubuntu.
https://bugs.launchpad.net/bugs/1958267

Title:
  "Connection failed" for WPA Enterprise network eduroam

Status in wpa package in Ubuntu:
  New

Bug description:
  With the current jammy version of wpasupplicant (2:2.10-1), I cannot
  connect to the WPA Enterprise network eduroam, which is used by
  Universities worldwide. I get a "Connection failed" message or a
  request to re-enter the password.

  - I've re-tried the credentials: no fix ;-)

  - Tried a 21.10 live session on the same machine: works fine!

  - Manually downgraded wpasupplicant to the impish version
  (2:2.9.0-21build1): connected normally.

  - Upgraded wpasupplicant to the latest version: fails to connect
  again.

  
  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: wpasupplicant 2:2.10-1
  ProcVersionSignature: Ubuntu 5.15.0-17.17-generic 5.15.12
  Uname: Linux 5.15.0-17-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu75
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 18 09:56:23 2022
  InstallationDate: Installed on 2021-11-30 (48 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211130)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.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/1958267/+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 1892085] Re: [snap] Wrong cursor theme (Adwaita) for cursors set by CSS, like cursor:wait and cursor:grab

[Alexander Browne]

This seems resolved for me now with the Impish update to Yaru in the
gtk-common-themes snap candidate channel (0.1-62-g8745644 2021-09-29).

** Changed in: chromium-browser (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  [snap] Wrong cursor theme (Adwaita) for cursors set by CSS, like
  cursor:wait and cursor:grab

Status in chromium-browser package in Ubuntu:
  Fix Released

Bug description:
  0. In an Ubuntu 20.04 live session or new installation, install the
  Chromium snap and Google's Chrome deb packages.

  1. In both browsers, try the MDN cursor demos at
  https://developer.mozilla.org/en-US/docs/Web/CSS/cursor for cursor:
  wait and cursor: grab. (Click the "cursor: wait;" or "cursor: grab;"
  button, then move the mouse over the blue box on the right to see the
  cursor set by that CSS option.) Or any view any page that sets these
  cursors with CSS such as

  - cursor: grab
  - Accuweather/mapbox radar maps, e.g. 
https://www.accuweather.com/en/us/minneapolis/55455/minute-weather-forecast/348794
  - Google Sheets, e.g. hovering over a highlighted cell's border
  - cursor: wait
  - NYT video pages while the video loads, e.g. 
https://www.nytimes.com/video/us/politics/10007231439/who-is-kamala-harris.html

  2. Observe that in Chromium, the CSS-set wait spinner and grab hand
  cursors are using the Adwaita theme, instead of the Ubuntu-default
  Yaru theme. The correct Yaru theme cursors are used in Chrome and
  other apps. (Note that for the cursor:grab examples, the Adwaita grab
  cursor [black hand] is shown when *hovering*, but the correct Yaru
  cursor [white hand] is shown once you click down, since this is no
  longer set by cursor:grab.)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1892085/+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 1861558] Re: Snap 'ed applicaitons have garbage on top of the window Close [x] button

[Alexander Browne]

This doesn't just occur with GNOME. I am seeing it on Plasma desktop
(X11), running on Kubuntu impish, with the GTK theme set to Yaru and the
icon theme set to the Breeze theme (the Kubuntu/Plasma default).

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

Title:
  Snap 'ed applicaitons have garbage on top of the window Close [x]
  button

Status in adwaita-icon-theme package in Ubuntu:
  Confirmed
Status in gnome-themes-extra package in Ubuntu:
  Confirmed
Status in humanity-icon-theme package in Ubuntu:
  Confirmed
Status in snapd package in Ubuntu:
  Confirmed
Status in ubuntu-mono package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce:
  1. Have Ubuntu 19.10 installed
  2. Install GNOME application as a Snap - for example with

  sudo snap install gedit gnome-calculator

  3. Open GNOME Tweaks -> Appearance tab, then switch Icon set to the
  one of the following:

  * Adwaita
  * DMZ-Black
  * DMZ-White
  * hicolor
  * HighContrast
  * Humanity
  * Humanity-Dark
  * LoginIcons

  For example - Adwaita theme with Adwaita icon set.

  4. Open GNOME Calculator as a Snap application:

 /snap/bin/gnome-calculator

  Expected result:

  * GNOME Calculator looks as any other GTK application

  Actual result:

  * GNOME Calculator has garbage on top of the window Close [x] button

  ---

  Notes: 
  1. Problem was first seen on AskUbuntu - https://askubuntu.com/q/1206868
  2. one can use the script below to check all possible Theme<->Icon 
combinations:

  ```
  #!/bin/bash

  DISPLAY=:0

  for t in $(ls -1 /usr/share/themes/)
  do 
for i in $(ls -1 /usr/share/icons/)
do

  echo -e "\nTheme: $t, Icons: $i\n"

gsettings set org.gnome.desktop.interface gtk-theme "$t"
gsettings set org.gnome.desktop.interface icon-theme "$i"

  /snap/bin/gnome-calculator

#read -r -s -p "Press  for next theme"   
done
  done

  ```

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: snapd 2.41+19.10.1
  ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13
  Uname: Linux 5.3.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Feb  1 17:55:09 2020
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: snapd
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/adwaita-icon-theme/+bug/1861558/+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 1802039]

[Alexander Browne]

I haven't used MATE for a couple years now, so I'm not sure myself.

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

Title:
  Firefox without titlebar has visual glitches when
  maximizing/unmaximizing

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

Bug description:
  There is a relatively new feature in Firefox that allows you to hide
  the title bar (I'm running Firefox 63.0), which is very helpful when
  you have a low resolution screen.  However, when changing the
  maximization state, some visual gitches occur.  I didn't notice this
  glitching when running Kubuntu or Ubuntu Budgie on two separate
  systems.

  To try this, go to your Firefox Menu, click Customize, and uncheck
  "Title Bar" at the bottom left.  Then unmaximize the window and then
  remaximize it.

  What it's supposed to look like: https://pasteboard.co/HM0h8oB.png
  Unmaximized (note the large transparent section): 
https://pasteboard.co/HM0hpud.png
  Remaximized (note the duplicate set of close buttons): 
https://pasteboard.co/HM0hCf5.png

  Also another interesting bug I noticed...if you try to use Firefox in
  the no titlebar state with the global menu enabled (e.g. Contemporary,
  Cupertino, or Mutiny panel layouts), the window buttons are not placed
  correctly, being on the window border.

  Systems tried on:

  Laptop, Dell Latitude E5430 - Intel Core i3-3120M dual core with 
hyperthreading, 12 GB DDR3 Memory, Intel 4000 Graphics, Built-in LCD at 
1366x768 (screenshots from this system)
  Desktop, Lenovo ThinkCentre M79 - AMD A4-6300B 3.7 GHz dual core, 8 GB DDR3 
Memory, AMD 8370D Graphics, HP 2009f Monitor at 1600x900

To manage notifications about this bug go to:
https://bugs.launchpad.net/firefox/+bug/1802039/+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 1900783] Re: [snap] On Groovy, Chromium snap takes much longer to load the first time after reboot

[Alexander Browne]

On my test computer at least, today's snap revision 1373 seems to have
solved it.

Running `snap run --trace-exec chromium` on a cold boot I get

Slowest 10 exec calls during snap run:
  0.237s snap-update-ns
  0.400s /usr/lib/snapd/snap-confine
  0.087s /snap/chromium/1373/snap/command-chain/snapcraft-runner
  0.590s /snap/chromium/1373/bin/desktop-launch
  0.065s /usr/bin/snapctl
  0.114s /snap/chromium/1373/bin/chromium.launcher
  0.159s /usr/bin/dbus-send
  0.286s /usr/bin/xdg-settings
  3.609s /proc/self/exe
  5.238s /snap/chromium/1373/usr/lib/chromium-browser/chrome
Total time: 6.515s

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

Title:
  [snap] On Groovy, Chromium snap takes much longer to load the first
  time after reboot

Status in chromium-browser package in Ubuntu:
  Confirmed

Bug description:
  I upgraded from Focal to Groovy, and now the first launch of the
  Chromium snap after a reboot is taking much longer than before. On my
  main home laptop it takes over 30 seconds, while under Focal I don't
  remember it taking more than 10 seconds.

  I tried another computer I could erase. On Groovy that computer takes
  nearly a minute to launch the Chromium snap after rebooting. Then I
  clean installed Focal on the same machine, and the Chromium snap takes
  just under 10 seconds to launch after a reboot. For both I installed
  all updates, and I let the computer sit idle for a few minutes after
  rebooting to try to rule out other activity.

  I haven’t noticed the change for any other snap, although I don’t use
  any that I ever noticed as much of a launch delay as Chromium. (VS
  Code for one doesn’t seem slower — certainly not taking nearly a
  minute — but I haven't done a real comparison like for Chromium.)

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14
  Uname: Linux 5.8.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 20 21:29:20 2020
  InstallationDate: Installed on 2020-04-01 (202 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200331)
  Snap: chromium 87.0.4280.20 (latest/beta)
  SnapSource: ubuntu/+source/chromium-browser
  UpgradeStatus: Upgraded to groovy on 2020-10-17 (3 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1900783/+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 1900783] Re: [snap] On Groovy, Chromium snap takes much longer to load the first time after reboot

[Alexander Browne]

FWIW I hadn't tried Google Chrome on this computer, so I installed it
(same stable version as the snap), and it loads with normal speed on
cold boot and subsequently.

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

Title:
  [snap] On Groovy, Chromium snap takes much longer to load the first
  time after reboot

Status in chromium-browser package in Ubuntu:
  Incomplete

Bug description:
  I upgraded from Focal to Groovy, and now the first launch of the
  Chromium snap after a reboot is taking much longer than before. On my
  main home laptop it takes over 30 seconds, while under Focal I don't
  remember it taking more than 10 seconds.

  I tried another computer I could erase. On Groovy that computer takes
  nearly a minute to launch the Chromium snap after rebooting. Then I
  clean installed Focal on the same machine, and the Chromium snap takes
  just under 10 seconds to launch after a reboot. For both I installed
  all updates, and I let the computer sit idle for a few minutes after
  rebooting to try to rule out other activity.

  I haven’t noticed the change for any other snap, although I don’t use
  any that I ever noticed as much of a launch delay as Chromium. (VS
  Code for one doesn’t seem slower — certainly not taking nearly a
  minute — but I haven't done a real comparison like for Chromium.)

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14
  Uname: Linux 5.8.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 20 21:29:20 2020
  InstallationDate: Installed on 2020-04-01 (202 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200331)
  Snap: chromium 87.0.4280.20 (latest/beta)
  SnapSource: ubuntu/+source/chromium-browser
  UpgradeStatus: Upgraded to groovy on 2020-10-17 (3 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1900783/+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 1900783] Re: [snap] On Groovy, Chromium snap takes much longer to load the first time after reboot

[Alexander Browne]

** Attachment added: "chromium.trace"
   
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1900783/+attachment/5426143/+files/chromium.trace

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

Title:
  [snap] On Groovy, Chromium snap takes much longer to load the first
  time after reboot

Status in chromium-browser package in Ubuntu:
  Incomplete

Bug description:
  I upgraded from Focal to Groovy, and now the first launch of the
  Chromium snap after a reboot is taking much longer than before. On my
  main home laptop it takes over 30 seconds, while under Focal I don't
  remember it taking more than 10 seconds.

  I tried another computer I could erase. On Groovy that computer takes
  nearly a minute to launch the Chromium snap after rebooting. Then I
  clean installed Focal on the same machine, and the Chromium snap takes
  just under 10 seconds to launch after a reboot. For both I installed
  all updates, and I let the computer sit idle for a few minutes after
  rebooting to try to rule out other activity.

  I haven’t noticed the change for any other snap, although I don’t use
  any that I ever noticed as much of a launch delay as Chromium. (VS
  Code for one doesn’t seem slower — certainly not taking nearly a
  minute — but I haven't done a real comparison like for Chromium.)

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14
  Uname: Linux 5.8.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 20 21:29:20 2020
  InstallationDate: Installed on 2020-04-01 (202 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200331)
  Snap: chromium 87.0.4280.20 (latest/beta)
  SnapSource: ubuntu/+source/chromium-browser
  UpgradeStatus: Upgraded to groovy on 2020-10-17 (3 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1900783/+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 1900783] Re: [snap] On Groovy, Chromium snap takes much longer to load the first time after reboot

[Alexander Browne]

Here's after a reboot, again with a clean profile that's been opened one
time, stable channel on up-to-date Groovy:

ab@mb:~$ etrace exec /snap/bin/chromium
2020/10/23 10:27:06 xdotool.go:84:
Gtk-Message: 10:27:14.094: Failed to load module "canberra-gtk-module"
Gtk-Message: 10:27:14.116: Failed to load module "canberra-gtk-module"
[11797:11797:1023/102734.021699:ERROR:sandbox_linux.cc(374)] 
InitializeSandbox() called with multiple threads in process gpu-process.
61 exec calls during snap run:
 Start Stop  ElapsedExec
 0 472100472.100019ms   /snap/bin/chromium
 27013 37971 10.958909ms/usr/lib/snapd/snap-seccomp
 1033121054872.174139ms /usr/lib/snapd/snap-device-helper
 1058381079592.121925ms /usr/lib/snapd/snap-device-helper
 1083191105012.181053ms /usr/lib/snapd/snap-device-helper
 1108501130802.230882ms /usr/lib/snapd/snap-device-helper
 1134211154892.067089ms /usr/lib/snapd/snap-device-helper
 1157721180212.249002ms /usr/lib/snapd/snap-device-helper
 1183351205682.233028ms /usr/lib/snapd/snap-device-helper
 1208671258474.980087ms /usr/lib/snapd/snap-device-helper
 1261981285402.342939ms /usr/lib/snapd/snap-device-helper
 1288601315772.716064ms /usr/lib/snapd/snap-device-helper
 1319401346342.694845ms /usr/lib/snapd/snap-device-helper
 1349731374542.481937ms /usr/lib/snapd/snap-device-helper
 1378061405052.698183ms /usr/lib/snapd/snap-device-helper
 1409621437702.808809ms /usr/lib/snapd/snap-device-helper
 1441081463012.193927ms /usr/lib/snapd/snap-device-helper
 1465911487782.187013ms /usr/lib/snapd/snap-device-helper
 1492171514942.276897ms /usr/lib/snapd/snap-device-helper
 1518471543672.520799ms /usr/lib/snapd/snap-device-helper
 1554221578772.454996ms /usr/lib/snapd/snap-device-helper
 1651571675552.398014ms /usr/lib/snapd/snap-device-helper
 1689471713602.413034ms /usr/lib/snapd/snap-device-helper
 1728261750122.186059ms /usr/lib/snapd/snap-device-helper
 1760981784162.318859ms /usr/lib/snapd/snap-device-helper
 1794351820032.568006ms /usr/lib/snapd/snap-device-helper
 1830771856622.584934ms /usr/lib/snapd/snap-device-helper
 209460445437235.977888ms   snap-update-ns
 45856646876610.200023mssnap-update-ns
 472100573029100.929975ms   /usr/lib/snapd/snap-exec
 5730295822699.239912ms 
/snap/chromium/1362/command-chromium.wrapper
 5822691204112   621.842145ms   /snap/chromium/1362/bin/desktop-launch
 66731067941412.10308ms /bin/date
 7716567809519.294986ms /usr/bin/md5sum
 7844707930448.574008ms /bin/cat
 7957228035557.83205ms  /usr/bin/md5sum
 8058818116555.774974ms /bin/cat
 81351383244718.934011ms/bin/grep
 83952286876729.245853ms/bin/mkdir
 89845195380455.353879ms/usr/bin/head
 95683597338116.54601ms /usr/bin/head
 97643499345717.022132ms/usr/bin/head
 9960591011866   15.806198ms/usr/bin/head
 1014738   1030759   16.021013ms/usr/bin/head
 1033776   1050442   16.666889ms/usr/bin/head
 1053074   1068875   15.800952ms/usr/bin/head
 1071585   1088642   17.056226ms/usr/bin/head
 1091500   1107697   16.196966ms/usr/bin/head
 1115821   1135473   19.652843ms/bin/mkdir
 1141314   1162826   21.512031ms/bin/ln
 1166500   1186408   19.907951ms/bin/rm
 1187048   1201411   14.36305ms /bin/ln
 1204112   1326992   122.879981ms   
/snap/chromium/1362/bin/chromium.launcher
 1213257   1251816   38.558959ms/usr/bin/cut
 1214077   1236867   22.789955ms/usr/bin/id
 1236932   1251408   14.475107ms/usr/bin/getent
 1255490   1326690   71.200847ms/usr/bin/snapctl
 1326992   54340631  53.013638973s  
/snap/chromium/1362/usr/lib/chromium-browser/chrome
 10571131  54331553  43.760421991s  /proc/self/exe
 29713400  30021182  307.781934ms   /usr/bin/xdg-settings
 29913347  30020597  107.249975ms   /usr/bin/dbus-send
Total time:  54.387691975s
Total startup time: 54.414637346s


Here's a few minutes later as a comparison of a re-launch:

ab@mb:~$ etrace exec /snap/bin/chromium
2020/10/23 10:33:04 xdotool.go:84:
Gtk-Message: 10:33:05.870: Failed to load module "canberra-gtk-module"
Gtk-Message: 10:33:05.878: Failed to load module "canberra-gtk-module"
[13532:13532:1023/103306.073051:ERROR:sandbox_linux.cc(374)] 
InitializeSandbox() called with multiple threads in process gpu-process.
55 exec calls during snap run:
 StartStop 

[Desktop-packages] [Bug 1900783] Re: [snap] On Groovy, Chromium snap takes much longer to load the first time after reboot

[Alexander Browne]

And for my main computer, Groovy/Chromium beta channel *with* my normal
profile:

alexander@elcste:~$ snap run --trace-exec chromium
[sudo] password for alexander:
Gtk-Message: 21:19:28.762: Failed to load module "canberra-gtk-module"
Gtk-Message: 21:19:28.790: Failed to load module "canberra-gtk-module"
[3494:3494:1022/211947.584671:ERROR:sandbox_linux.cc(374)] InitializeSandbox() 
called with multiple threads in process gpu-process.
Slowest 10 exec calls during snap run:
  0.198s snap-update-ns
  0.330s /usr/lib/snapd/snap-confine
  0.058s /usr/bin/head
  0.495s /snap/chromium/1366/bin/desktop-launch
  0.045s /usr/bin/snapctl
  0.098s /snap/chromium/1366/bin/chromium.launcher
  0.134s /usr/bin/dbus-send
  0.196s /usr/bin/xdg-settings
  35.202s /proc/self/exe
  43.764s /snap/chromium/1366/usr/lib/chromium-browser/chrome
Total time: 44.773s

I could try stable channel and a fresh profile using another user
account if it's helpful.

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

Title:
  [snap] On Groovy, Chromium snap takes much longer to load the first
  time after reboot

Status in chromium-browser package in Ubuntu:
  Incomplete

Bug description:
  I upgraded from Focal to Groovy, and now the first launch of the
  Chromium snap after a reboot is taking much longer than before. On my
  main home laptop it takes over 30 seconds, while under Focal I don't
  remember it taking more than 10 seconds.

  I tried another computer I could erase. On Groovy that computer takes
  nearly a minute to launch the Chromium snap after rebooting. Then I
  clean installed Focal on the same machine, and the Chromium snap takes
  just under 10 seconds to launch after a reboot. For both I installed
  all updates, and I let the computer sit idle for a few minutes after
  rebooting to try to rule out other activity.

  I haven’t noticed the change for any other snap, although I don’t use
  any that I ever noticed as much of a launch delay as Chromium. (VS
  Code for one doesn’t seem slower — certainly not taking nearly a
  minute — but I haven't done a real comparison like for Chromium.)

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14
  Uname: Linux 5.8.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 20 21:29:20 2020
  InstallationDate: Installed on 2020-04-01 (202 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200331)
  Snap: chromium 87.0.4280.20 (latest/beta)
  SnapSource: ubuntu/+source/chromium-browser
  UpgradeStatus: Upgraded to groovy on 2020-10-17 (3 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1900783/+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 1900783] Re: [snap] On Groovy, Chromium snap takes much longer to load the first time after reboot

[Alexander Browne]

On my main/home computer I've only tried beta channel, but with the
other computer I've tried both stable and beta. It doesn't seem to make
a difference.

Here is what I got for that command on Groovy:

STABLE

ab@mb:~$ snap run --trace-exec chromium
[sudo] password for ab:
Gtk-Message: 17:25:22.173: Failed to load module "canberra-gtk-module"
Gtk-Message: 17:25:22.194: Failed to load module "canberra-gtk-module"
[4206:4206:1022/172540.610350:ERROR:sandbox_linux.cc(374)] InitializeSandbox() 
called with multiple threads in process gpu-process.
Slowest 10 exec calls during snap run:
  0.254s snap-update-ns
  0.436s /usr/lib/snapd/snap-confine
  0.618s /snap/chromium/1362/bin/desktop-launch
  0.115s /snap/chromium/1362/bin/chromium.launcher
  0.118s /usr/bin/dbus-send
  0.227s /usr/bin/xdg-settings
  0.121s /snap/chromium/1362/usr/lib/chromium-browser/chrome
  0.094s /usr/bin/xdg-settings
  36.826s /proc/self/exe
  46.485s /snap/chromium/1362/usr/lib/chromium-browser/chrome
Total time: 47.862s


BETA

ab@mb:~$ snap run --trace-exec chromium
[sudo] password for ab:
Gtk-Message: 17:31:19.827: Failed to load module "canberra-gtk-module"
Gtk-Message: 17:31:19.851: Failed to load module "canberra-gtk-module"
[4553:4553:1022/173142.433976:ERROR:sandbox_linux.cc(374)] InitializeSandbox() 
called with multiple threads in process gpu-process.
Slowest 10 exec calls during snap run:
  0.228s snap-update-ns
  0.389s /usr/lib/snapd/snap-confine
  0.095s /snap/chromium/1357/snap/command-chain/snapcraft-runner
  0.607s /snap/chromium/1357/bin/desktop-launch
  0.072s /usr/bin/snapctl
  0.123s /snap/chromium/1357/bin/chromium.launcher
  0.115s /usr/bin/dbus-send
  0.315s /usr/bin/xdg-settings
  31.778s /proc/self/exe
  44.545s /snap/chromium/1357/usr/lib/chromium-browser/chrome
Total time: 45.843s

I deleted the chromium data (rm -r ~/snap/chromium), launched chromium
once, then rebooted and waited briefly, and finally ran the command.
Then I refreshed channels and did the same again.

If it's useful I can reinstall Focal on that computer when I'm back at
work tomorrow, and get the same info.

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

Title:
  [snap] On Groovy, Chromium snap takes much longer to load the first
  time after reboot

Status in chromium-browser package in Ubuntu:
  Incomplete

Bug description:
  I upgraded from Focal to Groovy, and now the first launch of the
  Chromium snap after a reboot is taking much longer than before. On my
  main home laptop it takes over 30 seconds, while under Focal I don't
  remember it taking more than 10 seconds.

  I tried another computer I could erase. On Groovy that computer takes
  nearly a minute to launch the Chromium snap after rebooting. Then I
  clean installed Focal on the same machine, and the Chromium snap takes
  just under 10 seconds to launch after a reboot. For both I installed
  all updates, and I let the computer sit idle for a few minutes after
  rebooting to try to rule out other activity.

  I haven’t noticed the change for any other snap, although I don’t use
  any that I ever noticed as much of a launch delay as Chromium. (VS
  Code for one doesn’t seem slower — certainly not taking nearly a
  minute — but I haven't done a real comparison like for Chromium.)

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14
  Uname: Linux 5.8.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 20 21:29:20 2020
  InstallationDate: Installed on 2020-04-01 (202 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200331)
  Snap: chromium 87.0.4280.20 (latest/beta)
  SnapSource: ubuntu/+source/chromium-browser
  UpgradeStatus: Upgraded to groovy on 2020-10-17 (3 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1900783/+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 1900783] [NEW] [snap] On Groovy, Chromium snap takes much longer to load the first time after reboot

[Alexander Browne]

Public bug reported:

I upgraded from Focal to Groovy, and now the first launch of the
Chromium snap after a reboot is taking much longer than before. On my
main home laptop it takes over 30 seconds, while under Focal I don't
remember it taking more than 10 seconds.

I tried another computer I could erase. On Groovy that computer takes
nearly a minute to launch the Chromium snap after rebooting. Then I
clean installed Focal on the same machine, and the Chromium snap takes
just under 10 seconds to launch after a reboot. For both I installed all
updates, and I let the computer sit idle for a few minutes after
rebooting to try to rule out other activity.

I haven’t noticed the change for any other snap, although I don’t use
any that I ever noticed as much of a launch delay as Chromium. (VS Code
for one doesn’t seem slower — certainly not taking nearly a minute — but
I haven't done a real comparison like for Chromium.)

ProblemType: Bug
DistroRelease: Ubuntu 20.10
ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14
Uname: Linux 5.8.0-25-generic x86_64
ApportVersion: 2.20.11-0ubuntu50
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Tue Oct 20 21:29:20 2020
InstallationDate: Installed on 2020-04-01 (202 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200331)
Snap: chromium 87.0.4280.20 (latest/beta)
SnapSource: ubuntu/+source/chromium-browser
UpgradeStatus: Upgraded to groovy on 2020-10-17 (3 days ago)

** Affects: chromium-browser (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug groovy snap

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

Title:
  [snap] On Groovy, Chromium snap takes much longer to load the first
  time after reboot

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  I upgraded from Focal to Groovy, and now the first launch of the
  Chromium snap after a reboot is taking much longer than before. On my
  main home laptop it takes over 30 seconds, while under Focal I don't
  remember it taking more than 10 seconds.

  I tried another computer I could erase. On Groovy that computer takes
  nearly a minute to launch the Chromium snap after rebooting. Then I
  clean installed Focal on the same machine, and the Chromium snap takes
  just under 10 seconds to launch after a reboot. For both I installed
  all updates, and I let the computer sit idle for a few minutes after
  rebooting to try to rule out other activity.

  I haven’t noticed the change for any other snap, although I don’t use
  any that I ever noticed as much of a launch delay as Chromium. (VS
  Code for one doesn’t seem slower — certainly not taking nearly a
  minute — but I haven't done a real comparison like for Chromium.)

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14
  Uname: Linux 5.8.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 20 21:29:20 2020
  InstallationDate: Installed on 2020-04-01 (202 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200331)
  Snap: chromium 87.0.4280.20 (latest/beta)
  SnapSource: ubuntu/+source/chromium-browser
  UpgradeStatus: Upgraded to groovy on 2020-10-17 (3 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1900783/+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 1892085] Re: [snap] Wrong cursor theme (Adwaita) for cursors set by CSS, like cursor:wait and cursor:grab

[Alexander Browne]

Also, FWIW since I reported this, I have noticed something similar in
another snap: KeepassXC, when unlocking your vault, shows the Adwaita
spinner. It only flashes for a short time, so is easy to miss. Not sure
if that's also a fallback issue like this or something different.

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

Title:
  [snap] Wrong cursor theme (Adwaita) for cursors set by CSS, like
  cursor:wait and cursor:grab

Status in chromium-browser package in Ubuntu:
  Confirmed

Bug description:
  0. In an Ubuntu 20.04 live session or new installation, install the
  Chromium snap and Google's Chrome deb packages.

  1. In both browsers, try the MDN cursor demos at
  https://developer.mozilla.org/en-US/docs/Web/CSS/cursor for cursor:
  wait and cursor: grab. (Click the "cursor: wait;" or "cursor: grab;"
  button, then move the mouse over the blue box on the right to see the
  cursor set by that CSS option.) Or any view any page that sets these
  cursors with CSS such as

  - cursor: grab
  - Accuweather/mapbox radar maps, e.g. 
https://www.accuweather.com/en/us/minneapolis/55455/minute-weather-forecast/348794
  - Google Sheets, e.g. hovering over a highlighted cell's border
  - cursor: wait
  - NYT video pages while the video loads, e.g. 
https://www.nytimes.com/video/us/politics/10007231439/who-is-kamala-harris.html

  2. Observe that in Chromium, the CSS-set wait spinner and grab hand
  cursors are using the Adwaita theme, instead of the Ubuntu-default
  Yaru theme. The correct Yaru theme cursors are used in Chrome and
  other apps. (Note that for the cursor:grab examples, the Adwaita grab
  cursor [black hand] is shown when *hovering*, but the correct Yaru
  cursor [white hand] is shown once you click down, since this is no
  longer set by cursor:grab.)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1892085/+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 1894226] Re: No per-pixel scrolling in version 86

[Alexander Browne]

Fixed in the latest beta release, 86.0.4240.53.


** Changed in: chromium-browser (Ubuntu)
   Status: New => Fix Released

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

Title:
  No per-pixel scrolling in version 86

Status in chromium-browser package in Ubuntu:
  Fix Released

Bug description:
  I just refreshed the beta snap, from version 85 to 86.0.4240.22, and
  now touchpad scrolling is no longer per pixel (Xinput 2 smooth
  scrolling?) but instead it scrolls a few lines like a mousewheel.

  I'm using Focal with the default GNOME desktop and X11.

  I have not tried Chrome or Chromium deb packages.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1894226/+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 1894226] Re: No per-pixel scrolling in version 86

[Alexander Browne]

This was fixed upstream, but hasn't been merged to the M86 (yet?), so it
still affects the beta channel.

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

Title:
  No per-pixel scrolling in version 86

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  I just refreshed the beta snap, from version 85 to 86.0.4240.22, and
  now touchpad scrolling is no longer per pixel (Xinput 2 smooth
  scrolling?) but instead it scrolls a few lines like a mousewheel.

  I'm using Focal with the default GNOME desktop and X11.

  I have not tried Chrome or Chromium deb packages.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1894226/+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 1894226] Re: No per-pixel scrolling in version 86

[Alexander Browne]

I confirmed this is an upstream issue by testing the Google Chrome deb,
which shows the same issue. I reported it as https://crbug.com/1126756
since that previous bug I mentioned is specifically for ChromeOS.

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

Title:
  No per-pixel scrolling in version 86

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  I just refreshed the beta snap, from version 85 to 86.0.4240.22, and
  now touchpad scrolling is no longer per pixel (Xinput 2 smooth
  scrolling?) but instead it scrolls a few lines like a mousewheel.

  I'm using Focal with the default GNOME desktop and X11.

  I have not tried Chrome or Chromium deb packages.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1894226/+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 1895062] [NEW] Regression: text scaling factor lost for GNOME Shell when logging out

[Alexander Browne]

Public bug reported:

As of a few weeks ago or so, GNOME Shell loses the text scaling factor
(it's set back to 1) when logging out and logging back in again. It is
preserved for other programs, just not the shell (top bar, menus, dash).
Setting it to another value and then back to the desired value changes
it until the next log out. I tried with a new user account and a second
machine, and I see the same thing.

Steps to reproduce:

1. Set a text scaling factor. (Something larger is easier to notice the change 
for.)
$ gsettings set org.gnome.desktop.interface text-scaling-factor 1.5

2. Notice apps and the shell have larger fonts now.

3. Log out and log back in (or restart).

4. Notice now that the top bar and other parts of the Shell are back to
a scale factor of 1, while other apps still have larger fonts.

5. Change the text scaling factor to something else (like 1) and then
back to the desired number.

$ gsettings set org.gnome.desktop.interface text-scaling-factor 1
$ gsettings set org.gnome.desktop.interface text-scaling-factor 1.5

6. Now the Shell does have large fonts, until step 3 is repeated.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gnome-shell 3.36.4-1ubuntu1~20.04.2
ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55
Uname: Linux 5.4.0-47-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.8
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Wed Sep  9 17:10:02 2020
DisplayManager: gdm3
InstallationDate: Installed on 2020-04-01 (160 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200331)
RelatedPackageVersions: mutter-common 3.36.4-0ubuntu0.20.04.2
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug focal

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

Title:
  Regression: text scaling factor lost for GNOME Shell when logging out

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  As of a few weeks ago or so, GNOME Shell loses the text scaling factor
  (it's set back to 1) when logging out and logging back in again. It is
  preserved for other programs, just not the shell (top bar, menus,
  dash). Setting it to another value and then back to the desired value
  changes it until the next log out. I tried with a new user account and
  a second machine, and I see the same thing.

  Steps to reproduce:

  1. Set a text scaling factor. (Something larger is easier to notice the 
change for.)
  $ gsettings set org.gnome.desktop.interface text-scaling-factor 1.5

  2. Notice apps and the shell have larger fonts now.

  3. Log out and log back in (or restart).

  4. Notice now that the top bar and other parts of the Shell are back
  to a scale factor of 1, while other apps still have larger fonts.

  5. Change the text scaling factor to something else (like 1) and then
  back to the desired number.

  $ gsettings set org.gnome.desktop.interface text-scaling-factor 1
  $ gsettings set org.gnome.desktop.interface text-scaling-factor 1.5

  6. Now the Shell does have large fonts, until step 3 is repeated.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.4-1ubuntu1~20.04.2
  ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55
  Uname: Linux 5.4.0-47-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.8
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Sep  9 17:10:02 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-04-01 (160 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200331)
  RelatedPackageVersions: mutter-common 3.36.4-0ubuntu0.20.04.2
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1895062/+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 1894226] Re: No per-pixel scrolling in version 86

[Alexander Browne]

crbug.com/1126610 might be the same issue.

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

Title:
  No per-pixel scrolling in version 86

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  I just refreshed the beta snap, from version 85 to 86.0.4240.22, and
  now touchpad scrolling is no longer per pixel (Xinput 2 smooth
  scrolling?) but instead it scrolls a few lines like a mousewheel.

  I'm using Focal with the default GNOME desktop and X11.

  I have not tried Chrome or Chromium deb packages.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1894226/+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 1894226] [NEW] No per-pixel scrolling in version 86

[Alexander Browne]

Public bug reported:

I just refreshed the beta snap, from version 85 to 86.0.4240.22, and now
touchpad scrolling is no longer per pixel (Xinput 2 smooth scrolling?)
but instead it scrolls a few lines like a mousewheel.

I'm using Focal with the default GNOME desktop and X11.

I have not tried Chrome or Chromium deb packages.

** Affects: chromium-browser (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  No per-pixel scrolling in version 86

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  I just refreshed the beta snap, from version 85 to 86.0.4240.22, and
  now touchpad scrolling is no longer per pixel (Xinput 2 smooth
  scrolling?) but instead it scrolls a few lines like a mousewheel.

  I'm using Focal with the default GNOME desktop and X11.

  I have not tried Chrome or Chromium deb packages.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1894226/+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 1892085] Re: Wrong cursor theme (Adwaita) for cursors set by CSS, like cursor:wait and cursor:grab

[Alexander Browne]

FWIW I had filed Chrome bug 1114812
(https://bugs.chromium.org/p/chromium/issues/detail?id=1114812) for this
before it seemed to isolate to the Snap package only. There was just a
change revision added, so maybe there is/was a Chromium bug (rather than
packaging 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/1892085

Title:
  Wrong cursor theme (Adwaita) for cursors set by CSS, like cursor:wait
  and cursor:grab

Status in chromium-browser package in Ubuntu:
  Confirmed

Bug description:
  0. In an Ubuntu 20.04 live session or new installation, install the
  Chromium snap and Google's Chrome deb packages.

  1. In both browsers, try the MDN cursor demos at
  https://developer.mozilla.org/en-US/docs/Web/CSS/cursor for cursor:
  wait and cursor: grab. (Click the "cursor: wait;" or "cursor: grab;"
  button, then move the mouse over the blue box on the right to see the
  cursor set by that CSS option.) Or any view any page that sets these
  cursors with CSS such as

  - cursor: grab
  - Accuweather/mapbox radar maps, e.g. 
https://www.accuweather.com/en/us/minneapolis/55455/minute-weather-forecast/348794
  - Google Sheets, e.g. hovering over a highlighted cell's border
  - cursor: wait
  - NYT video pages while the video loads, e.g. 
https://www.nytimes.com/video/us/politics/10007231439/who-is-kamala-harris.html

  2. Observe that in Chromium, the CSS-set wait spinner and grab hand
  cursors are using the Adwaita theme, instead of the Ubuntu-default
  Yaru theme. The correct Yaru theme cursors are used in Chrome and
  other apps. (Note that for the cursor:grab examples, the Adwaita grab
  cursor [black hand] is shown when *hovering*, but the correct Yaru
  cursor [white hand] is shown once you click down, since this is no
  longer set by cursor:grab.)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1892085/+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 1892085] [NEW] Wrong cursor theme (Adwaita) for cursors set by CSS, like cursor:wait and cursor:grab

[Alexander Browne]

Public bug reported:

0. In an Ubuntu 20.04 live session or new installation, install the
Chromium snap and Google's Chrome deb packages.

1. In both browsers, try the MDN cursor demos at
https://developer.mozilla.org/en-US/docs/Web/CSS/cursor for cursor: wait
and cursor: grab. (Click the "cursor: wait;" or "cursor: grab;" button,
then move the mouse over the blue box on the right to see the cursor set
by that CSS option.) Or any view any page that sets these cursors with
CSS such as

- cursor: grab
- Accuweather/mapbox radar maps, e.g. 
https://www.accuweather.com/en/us/minneapolis/55455/minute-weather-forecast/348794
- Google Sheets, e.g. hovering over a highlighted cell's border
- cursor: wait
- NYT video pages while the video loads, e.g. 
https://www.nytimes.com/video/us/politics/10007231439/who-is-kamala-harris.html

2. Observe that in Chromium, the CSS-set wait spinner and grab hand
cursors are using the Adwaita theme, instead of the Ubuntu-default Yaru
theme. The correct Yaru theme cursors are used in Chrome and other apps.
(Note that for the cursor:grab examples, the Adwaita grab cursor [black
hand] is shown when *hovering*, but the correct Yaru cursor [white hand]
is shown once you click down, since this is no longer set by
cursor:grab.)

** Affects: chromium-browser (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  Wrong cursor theme (Adwaita) for cursors set by CSS, like cursor:wait
  and cursor:grab

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  0. In an Ubuntu 20.04 live session or new installation, install the
  Chromium snap and Google's Chrome deb packages.

  1. In both browsers, try the MDN cursor demos at
  https://developer.mozilla.org/en-US/docs/Web/CSS/cursor for cursor:
  wait and cursor: grab. (Click the "cursor: wait;" or "cursor: grab;"
  button, then move the mouse over the blue box on the right to see the
  cursor set by that CSS option.) Or any view any page that sets these
  cursors with CSS such as

  - cursor: grab
  - Accuweather/mapbox radar maps, e.g. 
https://www.accuweather.com/en/us/minneapolis/55455/minute-weather-forecast/348794
  - Google Sheets, e.g. hovering over a highlighted cell's border
  - cursor: wait
  - NYT video pages while the video loads, e.g. 
https://www.nytimes.com/video/us/politics/10007231439/who-is-kamala-harris.html

  2. Observe that in Chromium, the CSS-set wait spinner and grab hand
  cursors are using the Adwaita theme, instead of the Ubuntu-default
  Yaru theme. The correct Yaru theme cursors are used in Chrome and
  other apps. (Note that for the cursor:grab examples, the Adwaita grab
  cursor [black hand] is shown when *hovering*, but the correct Yaru
  cursor [white hand] is shown once you click down, since this is no
  longer set by cursor:grab.)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1892085/+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 1803792] Re: Can't pin/keep/lock Quod Libet 4.2 to docks using bamf

[Alexander Browne]

OK, thanks for taking a look, I appreciate it.

I did look at the syslog but I don't see anything related to banf or the
docks, just some gtk theme warnings...

I did notice, however, that Quod Libet 4.1 is listed in the MATE dock
and Plank as "Quod Libet", while 4.2 is listed as " - Quod
Libet".

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

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

Title:
  Can't pin/keep/lock Quod Libet 4.2 to docks using bamf

Status in bamf package in Ubuntu:
  Invalid

Bug description:
  Since upgrading the music player Quod Libet to the latest version
  (4.2, via ppa:lazka/ppa), I there's no option to pin it to the MATE
  dock applet. I'm using 18.10, and I also tried Plank. A Quod Libet
  developer confirmed the issue as well in Unity on 16.04. AFAICT, these
  three docks all use bamf.

  Since all earlier versions of Quod Libet work fine, I posted a bug
  with them (https://github.com/quodlibet/quodlibet/issues/3029), but
  there are no reports of any issue with it from other docks/shells,
  like GNOME Shell or Plasma, so maybe it's a bug with bamf?

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: bamfdaemon 0.5.3+18.04.20180207.2-0ubuntu1
  ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
  Uname: Linux 4.18.0-11-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Fri Nov 16 17:50:42 2018
  InstallationDate: Installed on 2016-11-22 (724 days ago)
  InstallationMedia: Ubuntu-MATE 16.10 "Yakkety Yak" - Release amd64 
(20161012.1)
  SourcePackage: bamf
  UpgradeStatus: Upgraded to cosmic on 2018-09-29 (48 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bamf/+bug/1803792/+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 1803792] [NEW] Can't pin/keep/lock Quod Libet 4.2 to docks using bamf

[Alexander Browne]

Public bug reported:

Since upgrading the music player Quod Libet to the latest version (4.2,
via ppa:lazka/ppa), I there's no option to pin it to the MATE dock
applet. I'm using 18.10, and I also tried Plank. A Quod Libet developer
confirmed the issue as well in Unity on 16.04. AFAICT, these three docks
all use bamf.

Since all earlier versions of Quod Libet work fine, I posted a bug with
them (https://github.com/quodlibet/quodlibet/issues/3029), but there are
no reports of any issue with it from other docks/shells, like GNOME
Shell or Plasma, so maybe it's a bug with bamf?

ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: bamfdaemon 0.5.3+18.04.20180207.2-0ubuntu1
ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
Uname: Linux 4.18.0-11-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.10-0ubuntu13.1
Architecture: amd64
CurrentDesktop: MATE
Date: Fri Nov 16 17:50:42 2018
InstallationDate: Installed on 2016-11-22 (724 days ago)
InstallationMedia: Ubuntu-MATE 16.10 "Yakkety Yak" - Release amd64 (20161012.1)
SourcePackage: bamf
UpgradeStatus: Upgraded to cosmic on 2018-09-29 (48 days ago)

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


** Tags: amd64 apport-bug cosmic

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

Title:
  Can't pin/keep/lock Quod Libet 4.2 to docks using bamf

Status in bamf package in Ubuntu:
  New

Bug description:
  Since upgrading the music player Quod Libet to the latest version
  (4.2, via ppa:lazka/ppa), I there's no option to pin it to the MATE
  dock applet. I'm using 18.10, and I also tried Plank. A Quod Libet
  developer confirmed the issue as well in Unity on 16.04. AFAICT, these
  three docks all use bamf.

  Since all earlier versions of Quod Libet work fine, I posted a bug
  with them (https://github.com/quodlibet/quodlibet/issues/3029), but
  there are no reports of any issue with it from other docks/shells,
  like GNOME Shell or Plasma, so maybe it's a bug with bamf?

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: bamfdaemon 0.5.3+18.04.20180207.2-0ubuntu1
  ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
  Uname: Linux 4.18.0-11-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Fri Nov 16 17:50:42 2018
  InstallationDate: Installed on 2016-11-22 (724 days ago)
  InstallationMedia: Ubuntu-MATE 16.10 "Yakkety Yak" - Release amd64 
(20161012.1)
  SourcePackage: bamf
  UpgradeStatus: Upgraded to cosmic on 2018-09-29 (48 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bamf/+bug/1803792/+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 1760144] Re: Wrong size of icon, if launcher put on desktop

[Alexander Browne]

The large icon also shows up with the Ubuntu MATE Dock panel applet.

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

Title:
  Wrong size of icon, if launcher put on desktop

Status in firefox package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  as off Firefox 59, if a launcher is put on desktop, its icon size is
  too large.

  The culprit may be a missing icons folder ?

  Testing on a liveUSB of Ubuntu 16.04.1 here I get :
  https://postimg.org/image/6t98217zt/
  left window is the liveUSB, right window is my actual 16.04 installation.

  Right after upgrading FF to newer version, I get :
  https://postimg.org/image/cu6wz42bt/
  left window is still the liveUSB.
  « icons » folder disappeared while upgrading FF
  and then instantly icon get much larger on desktop.

  It's not unity related : see
  https://bugzilla.mozilla.org/show_bug.cgi?id=1446262 or https
  ://ubuntu-mate.community/t/firefox-v59-has-a-ridiculously-large-
  static-desktop-icon/16205/3 or https://forum.ubuntu-
  fr.org/viewtopic.php?id=2023636

  The workarounds provided by those topics are not reliable fixes.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1760144/+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 1721669] Re: Restore Disk Image stuck at 0% using 100% of CPU, then Disks crashed when I closed its window

[Alexander Browne]

This occurs for me on a system that had been upgraded from 17.04 to
17.10. I've now upgraded it to 18.04 pre-release and Disks's restore
function is working again. It does seem to use a lot of CPU, however,
but I haven't compare it with another system very scientifically.

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

Title:
  Restore Disk Image stuck at 0% using 100% of CPU, then Disks crashed
  when I closed its window

Status in gnome-disk-utility package in Ubuntu:
  Confirmed

Bug description:
  I was attempting to use "Restore Disk Image" to write an Ubuntu MATE
  iso to flash drive. The task stalled at 0%, and htop showed Disks
  using 100% CPU. I cancelled the task and clicked the window close
  button, and then Disks crashed.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gnome-disk-utility 3.26.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.7-0ubuntu2
  Architecture: amd64
  AssertionMessage: *** Error in `/usr/bin/gnome-disks': free(): invalid 
pointer: 0x55b9230dfd0f ***
  CurrentDesktop: MATE
  Date: Thu Oct  5 18:34:19 2017
  ExecutablePath: /usr/bin/gnome-disks
  InstallationDate: Installed on 2016-11-22 (317 days ago)
  InstallationMedia: Ubuntu-MATE 16.10 "Yakkety Yak" - Release amd64 
(20161012.1)
  ProcCmdline: /usr/bin/gnome-disks
  Signal: 6
  SourcePackage: gnome-disk-utility
  StacktraceTop:
   __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7fe72f8b2408 
"*** Error in `%s': %s: 0x%s ***\n") at ../sysdeps/posix/libc_fatal.c:181
   malloc_printerr (action=, str=0x7fe72f8aed8e "free(): invalid 
pointer", ptr=, ar_ptr=) at malloc.c:5423
   _int_free (av=0x7fe72fae4c20 , p=, have_lock=0) 
at malloc.c:4172
   __GI___libc_free (mem=) at malloc.c:3142
   () at /usr/lib/x86_64-linux-gnu/libcairo.so.2
  Title: gnome-disks assert failure: *** Error in `/usr/bin/gnome-disks': 
free(): invalid pointer: 0x55b9230dfd0f ***
  UpgradeStatus: Upgraded to artful on 2017-10-04 (1 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-disk-utility/+bug/1721669/+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 1707451] Re: udisksd crashed with SIGSEGV in g_mutex_lock()

[Alexander Browne]

I'm not sure if it's related, but I've also had issues with Disks
(gnome-disks), specifically it stalls at 0.0% when I try the "Restore
Disk Image" option. This worked fine before I upgraded to Artful.

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

Title:
  udisksd crashed with SIGSEGV in g_mutex_lock()

Status in udisks2 package in Ubuntu:
  Confirmed

Bug description:
  Showed up after login

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: udisks2 2.6.5-2ubuntu1
  ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8
  Uname: Linux 4.11.0-10-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.6-0ubuntu4
  Architecture: amd64
  Date: Sun Jul 30 00:35:31 2017
  ExecutablePath: /usr/lib/udisks2/udisksd
  InstallationDate: Installed on 2017-06-22 (37 days ago)
  InstallationMedia: Ubuntu-GNOME 17.10 "Artful Aardvark" - Alpha amd64 
(20170622)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcCmdline: /usr/lib/udisks2/udisksd
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.11.0-10-generic.efi.signed 
root=UUID=44b31662-d2ab-443b-9546-86d022d8de0d ro quiet splash vt.handoff=7
  SegvAnalysis:
   Segfault happened at: 0x7f4900fb5c65 :   lock xadd 
%eax,(%rdi)
   PC (0x7f4900fb5c65) ok
   source "%eax" ok
   destination "(%rdi)" (0x3a9d80e262617474) not located in a known VMA region 
(needed writable region)!
  SegvReason: writing unknown VMA
  Signal: 11
  SourcePackage: udisks2
  StacktraceTop:
   g_mutex_lock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   main ()
  Title: udisksd crashed with SIGSEGV in g_mutex_lock()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 04/12/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P3.40
  dmi.board.name: Z87 Extreme4
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP3.40:bd04/12/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ87Extreme4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/udisks2/+bug/1707451/+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 1721669] [NEW] Restore Disk Image stuck at 0% using 100% of CPU, then Disks crashed when I closed its window

[Alexander Browne]

Public bug reported:

I was attempting to use "Restore Disk Image" to write an Ubuntu MATE iso
to flash drive. The task stalled at 0%, and htop showed Disks using 100%
CPU. I cancelled the task and clicked the window close button, and then
Disks crashed.

ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: gnome-disk-utility 3.26.1-0ubuntu1
ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
Uname: Linux 4.13.0-12-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.7-0ubuntu2
Architecture: amd64
AssertionMessage: *** Error in `/usr/bin/gnome-disks': free(): invalid pointer: 
0x55b9230dfd0f ***
CurrentDesktop: MATE
Date: Thu Oct  5 18:34:19 2017
ExecutablePath: /usr/bin/gnome-disks
InstallationDate: Installed on 2016-11-22 (317 days ago)
InstallationMedia: Ubuntu-MATE 16.10 "Yakkety Yak" - Release amd64 (20161012.1)
ProcCmdline: /usr/bin/gnome-disks
Signal: 6
SourcePackage: gnome-disk-utility
StacktraceTop:
 __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7fe72f8b2408 
"*** Error in `%s': %s: 0x%s ***\n") at ../sysdeps/posix/libc_fatal.c:181
 malloc_printerr (action=, str=0x7fe72f8aed8e "free(): invalid 
pointer", ptr=, ar_ptr=) at malloc.c:5423
 _int_free (av=0x7fe72fae4c20 , p=, have_lock=0) at 
malloc.c:4172
 __GI___libc_free (mem=) at malloc.c:3142
 () at /usr/lib/x86_64-linux-gnu/libcairo.so.2
Title: gnome-disks assert failure: *** Error in `/usr/bin/gnome-disks': free(): 
invalid pointer: 0x55b9230dfd0f ***
UpgradeStatus: Upgraded to artful on 2017-10-04 (1 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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


** Tags: amd64 apport-crash artful need-amd64-retrace

** Information type changed from Private to Public

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

Title:
  Restore Disk Image stuck at 0% using 100% of CPU, then Disks crashed
  when I closed its window

Status in gnome-disk-utility package in Ubuntu:
  New

Bug description:
  I was attempting to use "Restore Disk Image" to write an Ubuntu MATE
  iso to flash drive. The task stalled at 0%, and htop showed Disks
  using 100% CPU. I cancelled the task and clicked the window close
  button, and then Disks crashed.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gnome-disk-utility 3.26.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.7-0ubuntu2
  Architecture: amd64
  AssertionMessage: *** Error in `/usr/bin/gnome-disks': free(): invalid 
pointer: 0x55b9230dfd0f ***
  CurrentDesktop: MATE
  Date: Thu Oct  5 18:34:19 2017
  ExecutablePath: /usr/bin/gnome-disks
  InstallationDate: Installed on 2016-11-22 (317 days ago)
  InstallationMedia: Ubuntu-MATE 16.10 "Yakkety Yak" - Release amd64 
(20161012.1)
  ProcCmdline: /usr/bin/gnome-disks
  Signal: 6
  SourcePackage: gnome-disk-utility
  StacktraceTop:
   __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7fe72f8b2408 
"*** Error in `%s': %s: 0x%s ***\n") at ../sysdeps/posix/libc_fatal.c:181
   malloc_printerr (action=, str=0x7fe72f8aed8e "free(): invalid 
pointer", ptr=, ar_ptr=) at malloc.c:5423
   _int_free (av=0x7fe72fae4c20 , p=, have_lock=0) 
at malloc.c:4172
   __GI___libc_free (mem=) at malloc.c:3142
   () at /usr/lib/x86_64-linux-gnu/libcairo.so.2
  Title: gnome-disks assert failure: *** Error in `/usr/bin/gnome-disks': 
free(): invalid pointer: 0x55b9230dfd0f ***
  UpgradeStatus: Upgraded to artful on 2017-10-04 (1 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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