[Desktop-packages] [Bug 2034993] [NEW] libwmf0.2-7-gtk is installed by Ubuntu metapackages

2023-09-08 Thread wontfix
Public bug reported:

>From the package description-
libwmf0.2-7-gtk
Windows metafile (WMF) is a picture format used by many Windows
 programs, e.g. Microsoft Word.

This transitional package depends on the new names of the shared library
packages, to provide smooth upgrades from Debian 11. It can be removed
if no installed packages depend on it.

Dependency chain-
ubuntu-desktop,ubuntu-desktop-minimal,libwmf0.2-7-gtk,libwmf-0.2-7-gtk,libwmf-0.2-7,libwmflite-0.2-7

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

** Affects: ubuntu-meta (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: bitesize bloat jammy lunar mantic packaging ubuntu-meta

** Also affects: ubuntu-meta (Ubuntu)
   Importance: Undecided
   Status: New

** Summary changed:

- libwmf0.2-7-gtk is recommended by Ubuntu metapackages
+ libwmf0.2-7-gtk is installed by Ubuntu metapackages

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

Title:
  libwmf0.2-7-gtk is installed by Ubuntu metapackages

Status in libwmf package in Ubuntu:
  New
Status in ubuntu-meta package in Ubuntu:
  New

Bug description:
  From the package description-
  libwmf0.2-7-gtk
  Windows metafile (WMF) is a picture format used by many Windows
   programs, e.g. Microsoft Word.

  This transitional package depends on the new names of the shared library
  packages, to provide smooth upgrades from Debian 11. It can be removed
  if no installed packages depend on it.

  Dependency chain-
  
ubuntu-desktop,ubuntu-desktop-minimal,libwmf0.2-7-gtk,libwmf-0.2-7-gtk,libwmf-0.2-7,libwmflite-0.2-7

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libwmf/+bug/2034993/+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 1876917] Re: libu2f-udev has been rendered unnecessary by systemd v244

2023-09-08 Thread wontfix
** Tags added: bitesize bloat jammy lunar mantic packaging ubuntu-meta

** Also affects: ubuntu-meta (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  libu2f-udev has been rendered unnecessary by systemd v244

Status in libu2f-host package in Ubuntu:
  Confirmed
Status in ubuntu-meta package in Ubuntu:
  New

Bug description:
  Since systemd v244, specifically this commit
  (https://github.com/systemd/systemd/issues/11996), systemd detects U2F
  devices based on their declared usage (page) and automatically
  generates the relevant udev rules. Manually maintaining device-
  specific rules is therefore no longer necessary and libu2f-udev can be
  removed from libu2f-host.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libu2f-host/+bug/1876917/+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 2034672] Re: gnome-shell crashed with GLXBadDrawable on startup in a Xorg session

2023-09-08 Thread Daniel van Vugt
** Changed in: mutter (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  gnome-shell crashed with GLXBadDrawable on startup in a Xorg session

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

Bug description:
  Mantic 20230907 on Latitude 3320

  Crash on boot of the live session

  ProblemType: Crash
  DistroRelease: Ubuntu 23.10
  Package: gnome-shell 45~rc-0ubuntu1
  ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5
  Uname: Linux 6.3.0-7-generic x86_64
  NonfreeKernelModules: zfs
  ApportVersion: 2.27.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CasperVersion: 1.482
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Sep  7 08:02:08 2023
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  ExecutableTimestamp: 1694028853
  LiveMediaBuild: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230907)
  ProcCmdline: /usr/bin/gnome-shell
  ProcCwd: /home/ubuntu
  ProcEnviron:
   LANG=C.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  RelatedPackageVersions: mutter-common 45~rc-0ubuntu1
  Signal: 5
  SourcePackage: gnome-shell
  StacktraceTop:
   g_log_structured_array () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_log_default_handler () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_logv () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_log () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/mutter-13/libmutter-mtk-13.so.0
  Title: gnome-shell crashed with signal 5 in g_log_structured_array()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo users
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/2034672/+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 2034664] Re: Meta.Rectangle is deprecated, use Mtk.Rectangle instead

2023-09-08 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  Meta.Rectangle is deprecated, use Mtk.Rectangle instead

Status in gnome-shell-extension-tiling-assistant package in Ubuntu:
  Confirmed
Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  Confirmed

Bug description:
  The gnome-shell 45.rc log fills with:

  Meta.Rectangle is deprecated, use Mtk.Rectangle instead

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-tiling-assistant/+bug/2034664/+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 2034664] Re: Meta.Rectangle is deprecated, use Mtk.Rectangle instead

2023-09-08 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: gnome-shell-extension-tiling-assistant (Ubuntu)
   Status: New => Confirmed

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

Title:
  Meta.Rectangle is deprecated, use Mtk.Rectangle instead

Status in gnome-shell-extension-tiling-assistant package in Ubuntu:
  Confirmed
Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  Confirmed

Bug description:
  The gnome-shell 45.rc log fills with:

  Meta.Rectangle is deprecated, use Mtk.Rectangle instead

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-tiling-assistant/+bug/2034664/+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 2016217] Re: gnome-shell crashed with SIGSEGV in clutter_actor_remove_effect() from st_scroll_view_dispose() from g_object_unref() from GjsAutoPointer() from GjsAutoPointer()

2023-09-08 Thread Marcos Alano
I'm getting this problem on Mantic with GNOME Shell 45 RC. There is a
way to produce debug information to confirm the problem?

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

Title:
  gnome-shell crashed with SIGSEGV in clutter_actor_remove_effect() from
  st_scroll_view_dispose() from g_object_unref() from GjsAutoPointer()
  from GjsAutoPointer()

Status in GNOME Shell:
  Fix Released
Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  Confirmed

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

  #0  0x7f3aa429dd82 in clutter_actor_remove_effect 
(self=self@entry=0x55d60fa59e90, effect=0x55d6101c48a0) at 
../clutter/clutter/clutter-actor.c:14830
  __inst = 0x55d6101c48a0
  __t = 94377826055744
  __r = 
  _g_boolean_var_274 = 
  __func__ = "clutter_actor_remove_effect"
  #1  0x7f3aa3f9d27f in st_scroll_view_dispose (object=0x55d60fa59e90) at 
../src/st/st-scroll-view.c:246
  priv = 0x55d60fa59a00
  #2  0x7f3aa4aeada0 in g_object_unref (_object=0x55d60fa59e90) at 
../../../gobject/gobject.c:3891
  _pp = 
  gaig_temp = 
  gaig_temp = 
  weak_locations = 
  nqueue = 0x55d60fa6da60
  _ptr = 
  object = 0x55d60fa59e90
  old_ref = 
  retry_atomic_decrement1 = 
  __func__ = "g_object_unref"
  #3  0x7f3aa43b4b2c in GjsAutoPointer<_GObject, void, _object_unref, 
_object_ref>::reset (ptr=0x0, this=) at ../gjs/jsapi-util.h:229
  old_ptr = 
  #4  GjsAutoPointer<_GObject, void, _object_unref, 
_object_ref>::~GjsAutoPointer (this=, this=) at 
../gjs/jsapi-util.h:172
  No locals.
  #5  GjsSmartPointer<_GObject>::~GjsSmartPointer (this=, 
this=) at ../gjs/jsapi-util.h:349
  No locals.
  #6  ObjectInstance::release_native_object (this=0x55d60fa0ce80) at 
/usr/src/gjs-1.76.0-1/obj-x86_64-linux-gnu/../gi/object.cpp:1524
  No locals.
  #7  ObjectInstance::release_native_object (this=0x55d60fa0ce80) at 
/usr/src/gjs-1.76.0-1/obj-x86_64-linux-gnu/../gi/object.cpp:1500
  No locals.
  #8  0x7f3aa43c9ec0 in ObjectInstance::~ObjectInstance (this=, this=) at 
/usr/src/gjs-1.76.0-1/obj-x86_64-linux-gnu/../gi/object.cpp:1945
  was_using_toggle_refs = false
  had_toggle_up = false
  had_toggle_down = 
  had_toggle_up = 
  had_toggle_down = 
  was_using_toggle_refs = 
  #9  GIWrapperInstance::finalize_impl (this=0x55d60fa0ce80) at ../gi/wrapperutils.h:1113
  No locals.
  #10 ObjectInstance::finalize_impl (gcx=, obj=0x35b1abd24820, 
this=0x55d60fa0ce80) at 
/usr/src/gjs-1.76.0-1/obj-x86_64-linux-gnu/../gi/object.cpp:1912
  query = {type = 94377830362416, type_name = 0x7f3aa3fdcda6 
"StScrollView", class_size = 664, instance_size = 48}
  query = 
  _g_boolean_var_74 = 
  #11 GIWrapperBase::finalize 
(gcx=, obj=0x35b1abd24820) at ../gi/wrapperutils.h:411
  priv = 0x55d60fa0ce80

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/2016217/+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 2034986] Re: some text became unreadable during a distribution upgrade

2023-09-08 Thread Jeremy Bícha
I'm attaching a screenshot from an upgrade I did from Lunar to Mantic on
July 18.

** Attachment added: "Screenshot from 2023-07-18 13-19-22.png"
   
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2034986/+attachment/5699480/+files/Screenshot%20from%202023-07-18%2013-19-22.png

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

Title:
  some text became unreadable during a distribution upgrade

Status in ubuntu-meta package in Ubuntu:
  New
Status in ubuntu-release-upgrader package in Ubuntu:
  New

Bug description:
  I was upgrading from Lunar to Mantic the other day and left a couple
  of applications open during the upgrade process. During the upgrade
  the text in audacious became unreadable (I'll attach a screenshot) and
  I seem to recall the title bar of Firefox being unreadable but the
  contents of web pages still being readable.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: ubuntu-release-upgrader-core 1:23.10.5
  ProcVersionSignature: Ubuntu 6.5.0-4.4-generic 6.5.0
  Uname: Linux 6.5.0-4-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia zfs
  ApportVersion: 2.27.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep  8 15:39:27 2023
  InstallationDate: Installed on 2018-08-10 (1855 days ago)
  InstallationMedia: Ubuntu-Server 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: ubuntu-release-upgrader
  UpgradeStatus: Upgraded to mantic on 2023-09-06 (2 days ago)
  VarLogDistupgradeAptclonesystemstate.tar.gz: Error: command ['pkexec', 'cat', 
'/var/log/dist-upgrade/apt-clone_system_state.tar.gz'] failed with exit code 
126: Error executing command as another user: Request dismissed
  VarLogDistupgradeTermlog:
   
  mtime.conffile..etc.update-manager.meta-release: 2021-05-27T16:30:16.970490

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/2034986/+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 2034986] Re: some text became unreadable during a distribution upgrade

2023-09-08 Thread Jeremy Bícha
This is a longstanding bug in our font stack. Things can go very bad
when a font in use is upgraded.

See for instance https://launchpad.net/bugs/1600160

It's not been noticed more recently because the Ubuntu font hasn't been
updated in a while. (And there is no longer an Ubuntu GNOME shipping the
Cantarell font by default.)

What about this idea for a workaround: have the upgrader temporarily
switch the UI font to a font that hasn't been changed since Jammy?

** Changed in: ubuntu-release-upgrader (Ubuntu)
   Importance: Undecided => Critical

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

Title:
  some text became unreadable during a distribution upgrade

Status in ubuntu-meta package in Ubuntu:
  New
Status in ubuntu-release-upgrader package in Ubuntu:
  New

Bug description:
  I was upgrading from Lunar to Mantic the other day and left a couple
  of applications open during the upgrade process. During the upgrade
  the text in audacious became unreadable (I'll attach a screenshot) and
  I seem to recall the title bar of Firefox being unreadable but the
  contents of web pages still being readable.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: ubuntu-release-upgrader-core 1:23.10.5
  ProcVersionSignature: Ubuntu 6.5.0-4.4-generic 6.5.0
  Uname: Linux 6.5.0-4-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia zfs
  ApportVersion: 2.27.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep  8 15:39:27 2023
  InstallationDate: Installed on 2018-08-10 (1855 days ago)
  InstallationMedia: Ubuntu-Server 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: ubuntu-release-upgrader
  UpgradeStatus: Upgraded to mantic on 2023-09-06 (2 days ago)
  VarLogDistupgradeAptclonesystemstate.tar.gz: Error: command ['pkexec', 'cat', 
'/var/log/dist-upgrade/apt-clone_system_state.tar.gz'] failed with exit code 
126: Error executing command as another user: Request dismissed
  VarLogDistupgradeTermlog:
   
  mtime.conffile..etc.update-manager.meta-release: 2021-05-27T16:30:16.970490

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/2034986/+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 2034989] [NEW] package libjpeg8 8c-2ubuntu8 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libjpeg8/changelog.Debian.gz', which is different from other i

2023-09-08 Thread Jagdeep Singh
Public bug reported:

# sudo chmod +x libdouble-conversion1_3.1.0-3_amd64.deb 
libjpeg-turbo8_2.1.2-0ubuntu1_amd64.deb libjpeg8_8c-2ubuntu10_amd64.deb 
CiscoPacketTracer_821_Ubuntu_64bit.deb  
 
sudo dpkg -i libdouble-conversion1_3.1.0-3_amd64.deb 
libjpeg-turbo8_2.1.2-0ubuntu1_amd64.deb libjpeg8_8c-2ubuntu10_amd64.deb 
CiscoPacketTracer_821_Ubuntu_64bit.deb

(Reading database ... 224856 files and directories currently installed.)
Preparing to unpack libdouble-conversion1_3.1.0-3_amd64.deb ...
Unpacking libdouble-conversion1:amd64 (3.1.0-3) over (3.1.0-3) ...
Preparing to unpack libjpeg-turbo8_2.1.2-0ubuntu1_amd64.deb ...
Unpacking libjpeg-turbo8:amd64 (2.1.2-0ubuntu1) over (2.0.3-0ubuntu1) ...
dpkg: error processing archive libjpeg-turbo8_2.1.2-0ubuntu1_amd64.deb 
(--install):
 trying to overwrite shared 
'/usr/share/doc/libjpeg-turbo8/changelog.Debian.gz', which is different from 
other instances of package libjpeg-turbo8:amd64
Preparing to unpack libjpeg8_8c-2ubuntu10_amd64.deb ...
Unpacking libjpeg8:amd64 (8c-2ubuntu10) over (8c-2ubuntu8) ...
dpkg: error processing archive libjpeg8_8c-2ubuntu10_amd64.deb (--install):
 trying to overwrite shared '/usr/share/doc/libjpeg8/changelog.Debian.gz', 
which is different from other instances of package libjpeg8:amd64
Preparing to unpack CiscoPacketTracer_821_Ubuntu_64bit.deb ...
Unpacking packettracer (8.2.1) over (8.2.1) ...
gtk-update-icon-cache: No theme index file.
Setting up libdouble-conversion1:amd64 (3.1.0-3) ...
Setting up packettracer (8.2.1) ...
gtk-update-icon-cache: No theme index file.
Processing triggers for libc-bin (2.35-0ubuntu3.1) ...
Processing triggers for shared-mime-info (2.1-2) ...
Errors were encountered while processing:
 libjpeg-turbo8_2.1.2-0ubuntu1_amd64.deb
 libjpeg8_8c-2ubuntu10_amd64.deb


# sudo apt install ./CiscoPacketTracer_821_Ubuntu_64bit.deb --fix-broken
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Correcting dependencies... Done
Note, selecting 'packettracer' instead of 
'./CiscoPacketTracer_821_Ubuntu_64bit.deb'
packettracer is already the newest version (8.2.1).
The following additional packages will be installed:
  libjpeg-turbo8 libjpeg8
The following packages will be upgraded:
  libjpeg-turbo8 libjpeg8
2 upgraded, 0 newly installed, 0 to remove and 8 not upgraded.
4 not fully installed or removed.
Need to get 137 kB of archives.
After this operation, 32.8 kB disk space will be freed.
Do you want to continue? [Y/n] y
Get:1 http://ca.archive.ubuntu.com/ubuntu jammy/main amd64 libjpeg-turbo8 amd64 
2.1.2-0ubuntu1 [134 kB]
Get:2 http://ca.archive.ubuntu.com/ubuntu jammy/main amd64 libjpeg8 amd64 
8c-2ubuntu10 [2,264 B]
Fetched 137 kB in 0s (529 kB/s)  
(Reading database ... 224856 files and directories currently installed.)
Preparing to unpack .../libjpeg-turbo8_2.1.2-0ubuntu1_amd64.deb ...
Unpacking libjpeg-turbo8:amd64 (2.1.2-0ubuntu1) over (2.0.3-0ubuntu1) ...
dpkg: error processing archive 
/var/cache/apt/archives/libjpeg-turbo8_2.1.2-0ubuntu1_amd64.deb (--unpack):
 trying to overwrite shared 
'/usr/share/doc/libjpeg-turbo8/changelog.Debian.gz', which is different from 
other instances of package libjpeg-turbo8:amd
64
Preparing to unpack .../libjpeg8_8c-2ubuntu10_amd64.deb ...
Unpacking libjpeg8:amd64 (8c-2ubuntu10) over (8c-2ubuntu8) ...
dpkg: error processing archive 
/var/cache/apt/archives/libjpeg8_8c-2ubuntu10_amd64.deb (--unpack):
 trying to overwrite shared '/usr/share/doc/libjpeg8/changelog.Debian.gz', 
which is different from other instances of package libjpeg8:amd64
Errors were encountered while processing:
 /var/cache/apt/archives/libjpeg-turbo8_2.1.2-0ubuntu1_amd64.deb
 /var/cache/apt/archives/libjpeg8_8c-2ubuntu10_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)

ProblemType: Package
DistroRelease: Ubuntu 22.04
Package: libjpeg8 8c-2ubuntu8
ProcVersionSignature: Ubuntu 6.2.0-32.32~22.04.1-generic 6.2.16
Uname: Linux 6.2.0-32-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.5
AptOrdering:
 libjpeg-turbo8:amd64: Install
 libjpeg8:amd64: Install
 NULL: ConfigurePending
Architecture: amd64
CasperMD5CheckResult: pass
Date: Fri Sep  8 20:09:58 2023
ErrorMessage: trying to overwrite shared 
'/usr/share/doc/libjpeg8/changelog.Debian.gz', which is different from other 
instances of package libjpeg8:amd64
InstallationDate: Installed on 2023-09-03 (5 days ago)
InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.2)
Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 
3.10.6-1~22.04
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.21.1ubuntu2.2
 apt  2.4.10
SourcePackage: libjpeg8-empty
Title: package libjpeg8 8c-2ubuntu8 failed to install/upgrade: trying to 
overwrite shared '/usr/share/doc/libjpeg8/changelog.Debian.gz', which is 
different from other instances of package libjpeg8:amd64
UpgradeStatus: No upgrade 

[Desktop-packages] [Bug 1966552] Re: IBus input method candidate box cannot follow the cursor

2023-09-08 Thread Gunnar Hjalmarsson
Marking this as invalid for ibus and ibus-libpinyin. ibus upstream
provided an explanation and confirmed that the workaround makes sense.

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

** Changed in: ibus-libpinyin (Ubuntu)
   Status: New => Invalid

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

Title:
  IBus input method candidate box cannot follow the cursor

Status in ibus:
  Fix Released
Status in ibus package in Ubuntu:
  Invalid
Status in ibus-libpinyin package in Ubuntu:
  Invalid

Bug description:
  I have tested it in some software, such as Microsoft Edge, Onlyoffice,
  and it does not follow the cursor position correctly, but always at
  the bottom left of the application window. However, in some
  applications such as Gedit, it works fine.

  Pictures are here:https://i.bmp.ovh/imgs/2022/03/34ebb5158ceeedfc.png

  OS: Ubuntu Jammy Jellyfish
  Kernel: 5.15.0-23-generic
  on Wayland

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: ibus-libpinyin 1.12.1-2ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Uname: Linux 5.15.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Mar 26 23:59:28 2022
  InstallationDate: Installed on 2022-02-09 (45 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  SourcePackage: ibus-libpinyin
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ibus/+bug/1966552/+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 2034986] Re: some text became unreadable during a distribution upgrade

2023-09-08 Thread Brian Murray
This isn't a problem with ubuntu-release-upgrader but rather something
with the desktop environment during the upgrade process so I've opened
an ubuntu-meta task.

** Tags added: rls-mm-incoming

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

Title:
  some text became unreadable during a distribution upgrade

Status in ubuntu-meta package in Ubuntu:
  New
Status in ubuntu-release-upgrader package in Ubuntu:
  New

Bug description:
  I was upgrading from Lunar to Mantic the other day and left a couple
  of applications open during the upgrade process. During the upgrade
  the text in audacious became unreadable (I'll attach a screenshot) and
  I seem to recall the title bar of Firefox being unreadable but the
  contents of web pages still being readable.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: ubuntu-release-upgrader-core 1:23.10.5
  ProcVersionSignature: Ubuntu 6.5.0-4.4-generic 6.5.0
  Uname: Linux 6.5.0-4-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia zfs
  ApportVersion: 2.27.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep  8 15:39:27 2023
  InstallationDate: Installed on 2018-08-10 (1855 days ago)
  InstallationMedia: Ubuntu-Server 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: ubuntu-release-upgrader
  UpgradeStatus: Upgraded to mantic on 2023-09-06 (2 days ago)
  VarLogDistupgradeAptclonesystemstate.tar.gz: Error: command ['pkexec', 'cat', 
'/var/log/dist-upgrade/apt-clone_system_state.tar.gz'] failed with exit code 
126: Error executing command as another user: Request dismissed
  VarLogDistupgradeTermlog:
   
  mtime.conffile..etc.update-manager.meta-release: 2021-05-27T16:30:16.970490

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/2034986/+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 2034986] [NEW] some text became unreadable during a distribution upgrade

2023-09-08 Thread Brian Murray
Public bug reported:

I was upgrading from Lunar to Mantic the other day and left a couple of
applications open during the upgrade process. During the upgrade the
text in audacious became unreadable (I'll attach a screenshot) and I
seem to recall the title bar of Firefox being unreadable but the
contents of web pages still being readable.

ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: ubuntu-release-upgrader-core 1:23.10.5
ProcVersionSignature: Ubuntu 6.5.0-4.4-generic 6.5.0
Uname: Linux 6.5.0-4-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia zfs
ApportVersion: 2.27.0-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: unknown
CrashDB: ubuntu
CurrentDesktop: ubuntu:GNOME
Date: Fri Sep  8 15:39:27 2023
InstallationDate: Installed on 2018-08-10 (1855 days ago)
InstallationMedia: Ubuntu-Server 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
PackageArchitecture: all
SourcePackage: ubuntu-release-upgrader
Symptom: ubuntu-release-upgrader
UpgradeStatus: Upgraded to mantic on 2023-09-06 (2 days ago)
VarLogDistupgradeAptclonesystemstate.tar.gz: Error: command ['pkexec', 'cat', 
'/var/log/dist-upgrade/apt-clone_system_state.tar.gz'] failed with exit code 
126: Error executing command as another user: Request dismissed
VarLogDistupgradeTermlog:
 
mtime.conffile..etc.update-manager.meta-release: 2021-05-27T16:30:16.970490

** Affects: ubuntu-meta (Ubuntu)
 Importance: Undecided
 Status: New

** Affects: ubuntu-release-upgrader (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug dist-upgrade mantic rls-mm-incoming

** Attachment added: "Screenshot from 2023-09-06 16-19-39.png"
   
https://bugs.launchpad.net/bugs/2034986/+attachment/5699443/+files/Screenshot%20from%202023-09-06%2016-19-39.png

** Also affects: ubuntu-meta (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  some text became unreadable during a distribution upgrade

Status in ubuntu-meta package in Ubuntu:
  New
Status in ubuntu-release-upgrader package in Ubuntu:
  New

Bug description:
  I was upgrading from Lunar to Mantic the other day and left a couple
  of applications open during the upgrade process. During the upgrade
  the text in audacious became unreadable (I'll attach a screenshot) and
  I seem to recall the title bar of Firefox being unreadable but the
  contents of web pages still being readable.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: ubuntu-release-upgrader-core 1:23.10.5
  ProcVersionSignature: Ubuntu 6.5.0-4.4-generic 6.5.0
  Uname: Linux 6.5.0-4-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia zfs
  ApportVersion: 2.27.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep  8 15:39:27 2023
  InstallationDate: Installed on 2018-08-10 (1855 days ago)
  InstallationMedia: Ubuntu-Server 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: ubuntu-release-upgrader
  UpgradeStatus: Upgraded to mantic on 2023-09-06 (2 days ago)
  VarLogDistupgradeAptclonesystemstate.tar.gz: Error: command ['pkexec', 'cat', 
'/var/log/dist-upgrade/apt-clone_system_state.tar.gz'] failed with exit code 
126: Error executing command as another user: Request dismissed
  VarLogDistupgradeTermlog:
   
  mtime.conffile..etc.update-manager.meta-release: 2021-05-27T16:30:16.970490

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/2034986/+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 2034979] [NEW] Some events are missing

2023-09-08 Thread eezacque
Public bug reported:

One specific event from a google calendar is missing, while it is shown
on the Google Calendar application and the Calendar application in
Android, and in https://calendar.google.com. Synchronising the calendar
doesn't fix it.

$ lsb_release -rd
Description:Ubuntu 22.04.3 LTS
Release:22.04

$ apt-cache policy gnome-calendar
gnome-calendar:
  Installed: 41.2-3
  Candidate: 41.2-3
  Version table:
 *** 41.2-3 500
500 http://mirror.transip.net/ubuntu/ubuntu jammy/main amd64 Packages
100 /var/lib/dpkg/status

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

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

Title:
  Some events are missing

Status in gnome-calendar package in Ubuntu:
  New

Bug description:
  One specific event from a google calendar is missing, while it is
  shown on the Google Calendar application and the Calendar application
  in Android, and in https://calendar.google.com. Synchronising the
  calendar doesn't fix it.

  $ lsb_release -rd
  Description:  Ubuntu 22.04.3 LTS
  Release:  22.04

  $ apt-cache policy gnome-calendar
  gnome-calendar:
Installed: 41.2-3
Candidate: 41.2-3
Version table:
   *** 41.2-3 500
  500 http://mirror.transip.net/ubuntu/ubuntu jammy/main amd64 Packages
  100 /var/lib/dpkg/status

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-calendar/+bug/2034979/+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 2006669] Re: Asynchronous wait on fence ... timed out (hint:intel_atomic_commit_ready [i915])

2023-09-08 Thread julien
very very annoying bug !
I don't have zoom, but I often have discord and slack opened.

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

Title:
  Asynchronous wait on fence ... timed out
  (hint:intel_atomic_commit_ready [i915])

Status in mesa package in Ubuntu:
  Fix Released
Status in mesa source package in Jammy:
  Fix Released
Status in mesa source package in Kinetic:
  Won't Fix
Status in mesa source package in Lunar:
  Fix Released

Bug description:
  GUI hard lock during zoom session and gnome-terminal

  kern.log shows a mix of errors 
  __
  kernel: [ 3627.948545] Asynchronous wait on fence 
:00:02.0:gnome-shell[4236]:40810 timed out (hint:intel_atomic_commit_ready 
[i915])
  kernel: [ 3631.063832] i915 :00:02.0: [drm] GPU HANG: ecode 
12:1:85db, in chrome [5521]
  kernel: [ 3631.064218] i915 :00:02.0: [drm] Resetting chip for stopped 
heartbeat on rcs0
  kernel: [ 3631.165642] i915 :00:02.0: [drm] chrome[5521] context reset 
due to GPU hang
  kernel: [ 3631.165719] i915 :00:02.0: [drm] GuC firmware 
i915/adlp_guc_70.1.1.bin version 70.1
  kernel: [ 3631.165725] i915 :00:02.0: [drm] HuC firmware 
i915/tgl_huc_7.9.3.bin version 7.9
  kernel: [ 3631.187377] i915 :00:02.0: [drm] HuC authenticated
  kernel: [ 3631.187670] i915 :00:02.0: [drm] GuC submission enabled
  kernel: [ 3631.187672] i915 :00:02.0: [drm] GuC SLPC enabled
  ___

  I suspect this issue to be 
  upstream: https://gitlab.freedesktop.org/mesa/mesa/-/issues/7755
  upstream commit: 
https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/20169/commits?commit_id=b9403b1c477e7af04114ae6a4e16ca370e22253c#d6ffde011ad32c6371611e7d64affaeb21b6b217

  Reproducer: Although I don't have my own reproducer, the upstream mesa
  reproducer does trigger a hang on my machine.

  Upstream Reproducer: Open https://kartikmandhang.netlify.app/ when it
  loads, you will see pikachu. Press "S", he will go back.  My whole
  system freezes from this in Wayland, regardless of the browser.

  Kernel: 6.0.0-1008-oem
  Mesa: 22.2.5-0ubuntu0.1~22.04.1

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: libgl1-mesa-dri 22.2.5-0ubuntu0.1~22.04.1
  ProcVersionSignature: Ubuntu 6.0.0-1008.8-oem 6.0.9
  Uname: Linux 6.0.0-1008-oem x86_64
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Feb  8 21:40:19 2023
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation Alder Lake-P Integrated Graphics Controller [8086:46a6] 
(rev 0c) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:0b1a]
 Subsystem: Dell Device [1028:0b1a]
  InstallationDate: Installed on 2022-07-13 (211 days ago)
  InstallationMedia: Ubuntu-Server 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220421)
  MachineType: Dell Inc. Precision 5570
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.0.0-1008-oem 
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro pcie_aspm=force quiet splash 
mem_sleep_default=deep vt.handoff=7
  SourcePackage: mesa
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/21/2022
  dmi.bios.release: 1.9
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.9.1
  dmi.board.name: 03M8N5
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.9.1:bd11/21/2022:br1.9:svnDellInc.:pnPrecision5570:pvr:rvnDellInc.:rn03M8N5:rvrA00:cvnDellInc.:ct10:cvr:sku0B1A:
  dmi.product.family: Precision
  dmi.product.name: Precision 5570
  dmi.product.sku: 0B1A
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1~22.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 22.2.5-0ubuntu0.1~22.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

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


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

[Desktop-packages] [Bug 2034975] Re: Maximized windows appear behind launcher after waking laptop

2023-09-08 Thread Ash
** Attachment added: "Example of maximized window appearlng behind launcher."
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2034975/+attachment/5699441/+files/Screenshot%20from%202023-09-08%2015-32-44.png

** Description changed:

  == RELEASE ==
  Description:  Ubuntu 22.04.3 LTS
  Release:  22.04
  
  == PACKAGE VERSION ==
  gnome-shell-extension-ubuntu-dock:
    Installed: 72~ubuntu5.22.04.2.1
    Candidate: 72~ubuntu5.22.04.2.1
    Version table:
   *** 72~ubuntu5.22.04.2.1 500
  500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64 
Packages
  500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main i386 
Packages
  100 /var/lib/dpkg/status
   72~ubuntu5 500
  500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages
  500 http://us.archive.ubuntu.com/ubuntu jammy/main i386 Packages
  
  == EXPECTED ==
  Screen restored to previous state when waking
  
  == ACTUAL ==
  Maximized windows appear behind launcher after waking laptop
  
  == DETAILS ==
- I have experienced this behavior with two devices; both originally came 
preinstalled with Windows and both inevitably ran 22.04. When I put the laptop 
to sleep (ie, close the lid) and wake it back up, maximized windows of some 
applications (namely, gnome-terminal and thunderbird, but not firefox) take up 
the entire screen, including the space reserved for the launcher, like this: 
https://i.stack.imgur.com/jvCc9.png
+ I have experienced this behavior with two devices; both originally came 
preinstalled with Windows and both inevitably ran 22.04. When I put the laptop 
to sleep (ie, close the lid) and wake it back up, maximized windows of some 
applications (namely, gnome-terminal and thunderbird, but not firefox) take up 
the entire screen, including the space reserved for the launcher, like this: 
https://imgur.com/a/vQ665sc
  
  Restoring and re-maximizing will fit the window correctly, but the
  problem will just happen again when I close my laptop.
  
  Here is journal output for the duration of closing and reopening my laptop:
  https://gist.github.com/ash-m/b7532f33afb7ca7b40bf32dd16eed620
  
  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 42.9-0ubuntu2
  ProcVersionSignature: Ubuntu 6.2.0-32.32~22.04.1-generic 6.2.16
  Uname: Linux 6.2.0-32-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep  8 14:56:02 2023
  DisplayManager: gdm3
  InstallationDate: Installed on 2023-07-26 (44 days ago)
  InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 
(20230223)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 42.9-0ubuntu4
  SourcePackage: gnome-shell
  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 gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/2034975

Title:
  Maximized windows appear behind launcher after waking laptop

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  == RELEASE ==
  Description:  Ubuntu 22.04.3 LTS
  Release:  22.04

  == PACKAGE VERSION ==
  gnome-shell-extension-ubuntu-dock:
    Installed: 72~ubuntu5.22.04.2.1
    Candidate: 72~ubuntu5.22.04.2.1
    Version table:
   *** 72~ubuntu5.22.04.2.1 500
  500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64 
Packages
  500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main i386 
Packages
  100 /var/lib/dpkg/status
   72~ubuntu5 500
  500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages
  500 http://us.archive.ubuntu.com/ubuntu jammy/main i386 Packages

  == EXPECTED ==
  Screen restored to previous state when waking

  == ACTUAL ==
  Maximized windows appear behind launcher after waking laptop

  == DETAILS ==
  I have experienced this behavior with two devices; both originally came 
preinstalled with Windows and both inevitably ran 22.04. When I put the laptop 
to sleep (ie, close the lid) and wake it back up, maximized windows of some 
applications (namely, gnome-terminal and thunderbird, but not firefox) take up 
the entire screen, including the space reserved for the launcher, like this: 
https://imgur.com/a/vQ665sc

  Restoring and re-maximizing will fit the window correctly, but the
  problem will just happen again when I close my laptop.

  Here is journal output for the duration of closing and reopening my laptop:
  https://gist.github.com/ash-m/b7532f33afb7ca7b40bf32dd16eed620

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 42.9-0ubuntu2
  ProcVersionSignature: Ubuntu 6.2.0-32.32~22.04.1-generic 6.2.16
  Uname: Linux 6.2.0-32-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: 

[Desktop-packages] [Bug 2034975] [NEW] Maximized windows appear behind launcher after waking laptop

2023-09-08 Thread Ash
Public bug reported:

== RELEASE ==
Description:Ubuntu 22.04.3 LTS
Release:22.04

== PACKAGE VERSION ==
gnome-shell-extension-ubuntu-dock:
  Installed: 72~ubuntu5.22.04.2.1
  Candidate: 72~ubuntu5.22.04.2.1
  Version table:
 *** 72~ubuntu5.22.04.2.1 500
500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64 
Packages
500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main i386 Packages
100 /var/lib/dpkg/status
 72~ubuntu5 500
500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages
500 http://us.archive.ubuntu.com/ubuntu jammy/main i386 Packages

== EXPECTED ==
Screen restored to previous state when waking

== ACTUAL ==
Maximized windows appear behind launcher after waking laptop

== DETAILS ==
I have experienced this behavior with two devices; both originally came 
preinstalled with Windows and both inevitably ran 22.04. When I put the laptop 
to sleep (ie, close the lid) and wake it back up, maximized windows of some 
applications (namely, gnome-terminal and thunderbird, but not firefox) take up 
the entire screen, including the space reserved for the launcher, like this: 
https://i.stack.imgur.com/jvCc9.png

Restoring and re-maximizing will fit the window correctly, but the
problem will just happen again when I close my laptop.

Here is journal output for the duration of closing and reopening my laptop:
https://gist.github.com/ash-m/b7532f33afb7ca7b40bf32dd16eed620

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: gnome-shell 42.9-0ubuntu2
ProcVersionSignature: Ubuntu 6.2.0-32.32~22.04.1-generic 6.2.16
Uname: Linux 6.2.0-32-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Fri Sep  8 14:56:02 2023
DisplayManager: gdm3
InstallationDate: Installed on 2023-07-26 (44 days ago)
InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 
(20230223)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
RelatedPackageVersions: mutter-common 42.9-0ubuntu4
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)

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


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

** Description changed:

- RELEASE
+ == RELEASE ==
  Description:  Ubuntu 22.04.3 LTS
  Release:  22.04
  
- PACKAGE VERSION
+ == PACKAGE VERSION ==
  gnome-shell-extension-ubuntu-dock:
-   Installed: 72~ubuntu5.22.04.2.1
-   Candidate: 72~ubuntu5.22.04.2.1
-   Version table:
-  *** 72~ubuntu5.22.04.2.1 500
- 500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64 
Packages
- 500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main i386 
Packages
- 100 /var/lib/dpkg/status
-  72~ubuntu5 500
- 500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages
- 500 http://us.archive.ubuntu.com/ubuntu jammy/main i386 Packages
+   Installed: 72~ubuntu5.22.04.2.1
+   Candidate: 72~ubuntu5.22.04.2.1
+   Version table:
+  *** 72~ubuntu5.22.04.2.1 500
+ 500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64 
Packages
+ 500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main i386 
Packages
+ 100 /var/lib/dpkg/status
+  72~ubuntu5 500
+ 500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages
+ 500 http://us.archive.ubuntu.com/ubuntu jammy/main i386 Packages
  
- EXPECTED
+ == EXPECTED ==
  Screen restored to previous state when waking
  
- ACTUAL
+ == ACTUAL ==
  Maximized windows appear behind launcher after waking laptop
  
- DETAILS
- I have experienced this behavior with two devices; both originally came 
preinstalled with Windows and both inevitably ran 22.04. When I put the laptop 
to sleep (ie, close the lid) and wake it back up, maximized windows of some 
applications (namely, gnome-shell and thunderbird, but not firefox) take up the 
entire screen, including the space reserved for the launcher, like this: 
https://i.stack.imgur.com/jvCc9.png
+ == DETAILS ==
+ I have experienced this behavior with two devices; both originally came 
preinstalled with Windows and both inevitably ran 22.04. When I put the laptop 
to sleep (ie, close the lid) and wake it back up, maximized windows of some 
applications (namely, gnome-terminal and thunderbird, but not firefox) take up 
the entire screen, including the space reserved for the launcher, like this: 
https://i.stack.imgur.com/jvCc9.png
  
  Restoring and re-maximizing will fit the window correctly, but the
  problem will just happen again when I close my laptop.
  
  Here is journal output for the duration of closing and reopening my laptop:
  https://gist.github.com/ash-m/b7532f33afb7ca7b40bf32dd16eed620
  
  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 42.9-0ubuntu2
  ProcVersionSignature: Ubuntu 

[Desktop-packages] [Bug 2034967] Re: cloud-init & cloud-guest-utils are installed on non-cloud installations

2023-09-08 Thread Dan Bungert
** Changed in: subiquity (Ubuntu)
   Status: New => Won't Fix

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

Title:
  cloud-init & cloud-guest-utils are installed on non-cloud
  installations

Status in cloud-init package in Ubuntu:
  Invalid
Status in cloud-utils package in Ubuntu:
  New
Status in subiquity package in Ubuntu:
  Won't Fix
Status in ubuntu-meta package in Ubuntu:
  New

Bug description:
  ~$ apt-cache rdepends --installed cloud-init
  cloud-init
  Reverse Depends:
cloud-guest-utils

  ~$ apt-cache rdepends --installed cloud-guest-utils
  cloud-guest-utils
  Reverse Depends:
   |cloud-init

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/2034967/+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 2034967] Re: cloud-init & cloud-guest-utils are installed on non-cloud installations

2023-09-08 Thread Brett Holman
** Also affects: subiquity (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  cloud-init & cloud-guest-utils are installed on non-cloud
  installations

Status in cloud-init package in Ubuntu:
  Invalid
Status in cloud-utils package in Ubuntu:
  New
Status in subiquity package in Ubuntu:
  Won't Fix
Status in ubuntu-meta package in Ubuntu:
  New

Bug description:
  ~$ apt-cache rdepends --installed cloud-init
  cloud-init
  Reverse Depends:
cloud-guest-utils

  ~$ apt-cache rdepends --installed cloud-guest-utils
  cloud-guest-utils
  Reverse Depends:
   |cloud-init

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/2034967/+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 2034967] Re: cloud-init & cloud-guest-utils are installed on non-cloud installations

2023-09-08 Thread Brett Holman
** Changed in: cloud-init (Ubuntu)
   Status: New => Invalid

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

Title:
  cloud-init & cloud-guest-utils are installed on non-cloud
  installations

Status in cloud-init package in Ubuntu:
  Invalid
Status in cloud-utils package in Ubuntu:
  New
Status in subiquity package in Ubuntu:
  New
Status in ubuntu-meta package in Ubuntu:
  New

Bug description:
  ~$ apt-cache rdepends --installed cloud-init
  cloud-init
  Reverse Depends:
cloud-guest-utils

  ~$ apt-cache rdepends --installed cloud-guest-utils
  cloud-guest-utils
  Reverse Depends:
   |cloud-init

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/2034967/+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 2034722] Re: High CPU usage causing slowdown

2023-09-08 Thread Umayr Saghir
Yep I somehow had that set in my /etc/environment (don't ever remember
setting it though). I removed it and rebooted and performance has gotten
slightly better but now the logs are being spammed with "Meta.Rectangle
is deprecated, use Mtk.Rectangle instead" from the bug you linked.
Gnome-shell's CPU usage doesn't get as high as previously, it now ends
up getting to around 50±% but is accompanied by a spike in systemd-
journald so I guess that points to the log spam causing the slowdown on
my machine. The spikes mainly occur when going into the overview and
switching workspaces.

I expect lower end/older systems would feel this the most, with newer
systems not noticing any significant slowdown on the desktop.

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

Title:
  High CPU usage causing slowdown

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  I have been experiencing high CPU usage from gnome-shell since
  upgrading to Mantic. htop shows gnome-shell consuming around 120% of
  the CPU. This ends up resulting a very sluggish feeling desktop.

  # System Details Report
  ---

  ## Report details
  - **Date generated:**  2023-09-07 16:31:07

  ## Hardware Information:
  - **Hardware Model:**  Apple Inc. MacBookPro12,1
  - **Memory:**  8.0 GiB
  - **Processor:**   Intel® Core™ i5-5257U × 4
  - **Graphics:**Intel® Iris® Graphics 6100 
(BDW GT3)
  - **Disk Capacity:**   (null)

  ## Software Information:
  - **Firmware Version:**184.0.0.0.0
  - **OS Name:** Ubuntu Mantic Minotaur 
(development branch)
  - **OS Build:**(null)
  - **OS Type:** 64-bit
  - **GNOME Version:**   45.rc
  - **Windowing System:**Wayland
  - **Kernel Version:**  Linux 6.3.0-7-generic

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: gnome-shell 45~rc-0ubuntu1
  ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5
  Uname: Linux 6.3.0-7-generic x86_64
  ApportVersion: 2.27.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Sep  7 16:25:02 2023
  DisplayManager: gdm3
  InstallationDate: Installed on 2022-03-31 (525 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 
(20220329.1)
  RelatedPackageVersions: mutter-common 45~rc-0ubuntu1
  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/2034722/+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 2034967] [NEW] cloud-init & cloud-guest-utils are installed on non-cloud installations

2023-09-08 Thread wontfix
Public bug reported:

~$ apt-cache rdepends --installed cloud-init
cloud-init
Reverse Depends:
  cloud-guest-utils

~$ apt-cache rdepends --installed cloud-guest-utils
cloud-guest-utils
Reverse Depends:
 |cloud-init

** Affects: cloud-init (Ubuntu)
 Importance: Undecided
 Status: New

** Affects: cloud-utils (Ubuntu)
 Importance: Undecided
 Status: New

** Affects: ubuntu-meta (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: bloat mantic packaging

** Also affects: cloud-init (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: cloud-utils (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  cloud-init & cloud-guest-utils are installed on non-cloud
  installations

Status in cloud-init package in Ubuntu:
  New
Status in cloud-utils package in Ubuntu:
  New
Status in ubuntu-meta package in Ubuntu:
  New

Bug description:
  ~$ apt-cache rdepends --installed cloud-init
  cloud-init
  Reverse Depends:
cloud-guest-utils

  ~$ apt-cache rdepends --installed cloud-guest-utils
  cloud-guest-utils
  Reverse Depends:
   |cloud-init

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/2034967/+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 2034960] [NEW] [mantic] GNOME Shell no longer supporting Yaru color styles

2023-09-08 Thread Jeremy Bícha
Public bug reported:

Test Case
-
1. Open the Settings app
2. Switch to the Appearance page
3. Choose the Purple color
4. Click the quick settings area in the far right side of GNOME Shell's top bar
5. The highlights should be purple

What Happens Instead

The highlights are still orange

Other Info
--
If I remember correctly, this worked for GNOME Shell 45 Beta but broke for 45 
RC. But I may be misremembering.

ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: gnome-shell 45~rc-0ubuntu1
ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5
Uname: Linux 6.3.0-7-generic x86_64
ApportVersion: 2.27.0-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: pass
CloudArchitecture: x86_64
CloudID: none
CloudName: none
CloudPlatform: none
CloudSubPlatform: config
CurrentDesktop: ubuntu:GNOME
Date: Fri Sep  8 14:26:16 2023
DisplayManager: gdm3
InstallationDate: Installed on 2023-09-08 (0 days ago)
InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230908)
ProcEnviron:
 LANG=en_US.UTF-8
 PATH=(custom, no user)
 SHELL=/bin/bash
 TERM=xterm-256color
 XDG_RUNTIME_DIR=
RelatedPackageVersions: mutter-common 45~rc-0ubuntu1
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: gnome-shell (Ubuntu)
 Importance: Medium
 Assignee: Marco Trevisan (Treviño) (3v1n0)
 Status: Triaged


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

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

Title:
  [mantic] GNOME Shell no longer supporting Yaru color styles

Status in gnome-shell package in Ubuntu:
  Triaged

Bug description:
  Test Case
  -
  1. Open the Settings app
  2. Switch to the Appearance page
  3. Choose the Purple color
  4. Click the quick settings area in the far right side of GNOME Shell's top 
bar
  5. The highlights should be purple

  What Happens Instead
  
  The highlights are still orange

  Other Info
  --
  If I remember correctly, this worked for GNOME Shell 45 Beta but broke for 45 
RC. But I may be misremembering.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: gnome-shell 45~rc-0ubuntu1
  ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5
  Uname: Linux 6.3.0-7-generic x86_64
  ApportVersion: 2.27.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CloudArchitecture: x86_64
  CloudID: none
  CloudName: none
  CloudPlatform: none
  CloudSubPlatform: config
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep  8 14:26:16 2023
  DisplayManager: gdm3
  InstallationDate: Installed on 2023-09-08 (0 days ago)
  InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230908)
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  RelatedPackageVersions: mutter-common 45~rc-0ubuntu1
  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/2034960/+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 2023322] Re: Unable to setup Google Online Accounts with Nvidia drivers

2023-09-08 Thread Jonathan Kamens
I can't use the nouveau driver because it doesn't play nicely with
DisplayLink for some reason and I don't have any displays plugged into
my computer directly. My workaround for adding a Google Account was
therefore the following:

1. Run `kill -TERM -1`

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

Title:
  Unable to setup Google Online Accounts with Nvidia drivers

Status in Webkit:
  Confirmed
Status in webkit2gtk package in Ubuntu:
  Incomplete
Status in webkit2gtk package in Debian:
  Confirmed

Bug description:
  When I go into Settings > Online Accounts > Google, I get to the
  prompt for email address, once in a while it stops accepting input
  there. But often I can get to the password screen. Once I do, I can't
  type anything or paste anything.

  This is a fresh install of Ubuntu 23.04 and I have installed all
  updates.

  Nothing in /var/crash

  Jun 08 11:15:59 CCW-HAL systemd[3523]: 
vte-spawn-8b4a59a3-a060-4bdd-92e6-285656bdb9a2.scope: Consumed 3.448s CPU time.
  Jun 08 11:16:01 CCW-HAL gnome-shell[3803]: g_closure_unref: assertion 
'closure->ref_count > 0' failed
  Jun 08 11:16:01 CCW-HAL gnome-shell[3803]: g_closure_unref: assertion 
'closure->ref_count > 0' failed
  Jun 08 11:16:01 CCW-HAL gnome-shell[3803]: g_closure_unref: assertion 
'closure->ref_count > 0' failed
  Jun 08 11:16:29 CCW-HAL systemd[3523]: Started 
app-gnome-org.gnome.Terminal-10924.scope - Application launched by gnome-shell.
  Jun 08 11:16:29 CCW-HAL dbus-daemon[3552]: [session uid=1000 pid=3552] 
Activating via systemd: service name='org.gnome.Terminal' 
unit='gnome-terminal-server.service' requested by ':1.167' (uid=1000 pid=10927 
comm="/usr/bin/gnome-terminal.real" label="unconfined")
  Jun 08 11:16:29 CCW-HAL systemd[3523]: Starting gnome-terminal-server.service 
- GNOME Terminal Server...
  Jun 08 11:16:29 CCW-HAL dbus-daemon[3552]: [session uid=1000 pid=3552] 
Successfully activated service 'org.gnome.Terminal'
  Jun 08 11:16:29 CCW-HAL systemd[3523]: Started gnome-terminal-server.service 
- GNOME Terminal Server.
  Jun 08 11:16:29 CCW-HAL systemd[3523]: Started 
vte-spawn-9cee1911-372a-4bb4-8b57-694984e43990.scope - VTE child process 10955 
launched by gnome-terminal-server process 10931.
  Jun 08 11:16:49 CCW-HAL gnome-control-c[8079]: Error showing account: Child 
process exited with code 1
  Jun 08 11:16:53 CCW-HAL gnome-online-accounts-panel.desktop[9764]: GLib-GIO: 
Using cross-namespace EXTERNAL authentication (this will deadlock if server is 
GDBus < 2.73.3)GLib-GIO: _g_io_module_get_default: Found default implementation 
gvfs (GDaemonVfs) for ‘gio-vfs’GLib: unsetenv() is not thread-safe and should 
not be used after threads are createdGLib-GIO: _g_io_module_get_default: Found 
default implementation dconf (DConfSettingsBackend) for 
‘gsettings-backend’GoaBackend: Loading all providers: GoaBackend: - 
googleGoaBackend: - owncloudGoaBackend: - windows_liveGoaBackend: - 
exchangeGoaBackend: - lastfmGoaBackend: - imap_smtpGoaBackend: - 
kerberosGoaBackend: activated kerberos providerGLib-GIO: 
_g_io_module_get_default: Found default implementation gnutls 
(GTlsBackendGnutls) for ‘gio-tls-backend’Failed to create account: Dialog was 
dismissed
  Jun 08 11:16:53 CCW-HAL xdg-desktop-por[3907]: Realtime error: Could not map 
pid: Could not determine pid namespace: Could not find instance-id in process's 
/.flatpak-info
  Jun 08 11:17:01 CCW-HAL CRON[11093]: pam_unix(cron:session): session opened 
for user root(uid=0) by (uid=0)
  Jun 08 11:17:01 CCW-HAL CRON[11094]: (root) CMD (cd / && run-parts --report 
/etc/cron.hourly)
  Jun 08 11:17:01 CCW-HAL CRON[11093]: pam_unix(cron:session): session closed 
for user root
  Jun 08 11:17:06 CCW-HAL kernel: WebKitWebProces[11026]: segfault at 
55bd22ad9adc ip 55bd22ad9adc sp 7ffd1f6adbe8 error 14 likely on CPU 2 
(core 2, socket 0)
  Jun 08 11:17:06 CCW-HAL kernel: Code: Unable to access opcode bytes at 
0x55bd22ad9ab2.
  Jun 08 11:17:36 CCW-HAL gnome-shell[3803]: Window manager warning: 
WM_TRANSIENT_FOR window 0x3a02767 for 0x3a02778 window override-redirect is an 
override-redirect window and this is not correct according to the standard, so 
we'll fallback to the first non-override-redirect window 0x3a006dc.
  Jun 08 11:17:42 CCW-HAL systemd[1]: Starting systemd-tmpfiles-clean.service - 
Cleanup of Temporary Directories...
  Jun 08 11:17:42 CCW-HAL systemd[1]: systemd-tmpfiles-clean.service: 
Deactivated successfully.
  Jun 08 11:17:42 CCW-HAL systemd[1]: Finished systemd-tmpfiles-clean.service - 
Cleanup of Temporary Directories.
  Jun 08 11:17:42 CCW-HAL systemd[1]: 
run-credentials-systemd\x2dtmpfiles\x2dclean.service.mount: Deactivated 
successfully.
  Jun 08 11:18:10 CCW-HAL gnome-shell[3803]: Window manager warning: 
WM_TRANSIENT_FOR window 0x3a029e2 for 0x3a029f0 window override-redirect is an 
override-redirect window and 

[Desktop-packages] [Bug 2023322] Re: Unable to setup Google Online Accounts with Nvidia drivers

2023-09-08 Thread Jonathan Kamens
Woops, posted that prematurely by accident.

I can't use the nouveau driver because it doesn't play nicely with
DisplayLink for some reason and I don't have any displays plugged into
my computer directly. My workaround for adding a Google Account was
therefore the following:

1. Run `kill -TERM -1` in my GNOME session to make sure all processes under my 
account are well and truly dead.
2. Ctrl-Alt-F3 to switch to a text virtual terminal.
3. Log in as root on the virtual terminal.
4. Run `xinit -- :1` to bring up an X server without any GNOME session or 
anything, with an xterm running in it.
5. In the xterm, run `xinit /usr/bin/sudo -u myusername -H gnome-session -- 
/usr/bin/Xephyr :2` (note that you need Xephyr installed for this to work).

That should start a GNOME session in which you can run gnome-control-
center and add the Google account successfully. Then you log out of the
GNOME session, exit from the xterm, and log out of the virtual terminal.

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

Title:
  Unable to setup Google Online Accounts with Nvidia drivers

Status in Webkit:
  Confirmed
Status in webkit2gtk package in Ubuntu:
  Incomplete
Status in webkit2gtk package in Debian:
  Confirmed

Bug description:
  When I go into Settings > Online Accounts > Google, I get to the
  prompt for email address, once in a while it stops accepting input
  there. But often I can get to the password screen. Once I do, I can't
  type anything or paste anything.

  This is a fresh install of Ubuntu 23.04 and I have installed all
  updates.

  Nothing in /var/crash

  Jun 08 11:15:59 CCW-HAL systemd[3523]: 
vte-spawn-8b4a59a3-a060-4bdd-92e6-285656bdb9a2.scope: Consumed 3.448s CPU time.
  Jun 08 11:16:01 CCW-HAL gnome-shell[3803]: g_closure_unref: assertion 
'closure->ref_count > 0' failed
  Jun 08 11:16:01 CCW-HAL gnome-shell[3803]: g_closure_unref: assertion 
'closure->ref_count > 0' failed
  Jun 08 11:16:01 CCW-HAL gnome-shell[3803]: g_closure_unref: assertion 
'closure->ref_count > 0' failed
  Jun 08 11:16:29 CCW-HAL systemd[3523]: Started 
app-gnome-org.gnome.Terminal-10924.scope - Application launched by gnome-shell.
  Jun 08 11:16:29 CCW-HAL dbus-daemon[3552]: [session uid=1000 pid=3552] 
Activating via systemd: service name='org.gnome.Terminal' 
unit='gnome-terminal-server.service' requested by ':1.167' (uid=1000 pid=10927 
comm="/usr/bin/gnome-terminal.real" label="unconfined")
  Jun 08 11:16:29 CCW-HAL systemd[3523]: Starting gnome-terminal-server.service 
- GNOME Terminal Server...
  Jun 08 11:16:29 CCW-HAL dbus-daemon[3552]: [session uid=1000 pid=3552] 
Successfully activated service 'org.gnome.Terminal'
  Jun 08 11:16:29 CCW-HAL systemd[3523]: Started gnome-terminal-server.service 
- GNOME Terminal Server.
  Jun 08 11:16:29 CCW-HAL systemd[3523]: Started 
vte-spawn-9cee1911-372a-4bb4-8b57-694984e43990.scope - VTE child process 10955 
launched by gnome-terminal-server process 10931.
  Jun 08 11:16:49 CCW-HAL gnome-control-c[8079]: Error showing account: Child 
process exited with code 1
  Jun 08 11:16:53 CCW-HAL gnome-online-accounts-panel.desktop[9764]: GLib-GIO: 
Using cross-namespace EXTERNAL authentication (this will deadlock if server is 
GDBus < 2.73.3)GLib-GIO: _g_io_module_get_default: Found default implementation 
gvfs (GDaemonVfs) for ‘gio-vfs’GLib: unsetenv() is not thread-safe and should 
not be used after threads are createdGLib-GIO: _g_io_module_get_default: Found 
default implementation dconf (DConfSettingsBackend) for 
‘gsettings-backend’GoaBackend: Loading all providers: GoaBackend: - 
googleGoaBackend: - owncloudGoaBackend: - windows_liveGoaBackend: - 
exchangeGoaBackend: - lastfmGoaBackend: - imap_smtpGoaBackend: - 
kerberosGoaBackend: activated kerberos providerGLib-GIO: 
_g_io_module_get_default: Found default implementation gnutls 
(GTlsBackendGnutls) for ‘gio-tls-backend’Failed to create account: Dialog was 
dismissed
  Jun 08 11:16:53 CCW-HAL xdg-desktop-por[3907]: Realtime error: Could not map 
pid: Could not determine pid namespace: Could not find instance-id in process's 
/.flatpak-info
  Jun 08 11:17:01 CCW-HAL CRON[11093]: pam_unix(cron:session): session opened 
for user root(uid=0) by (uid=0)
  Jun 08 11:17:01 CCW-HAL CRON[11094]: (root) CMD (cd / && run-parts --report 
/etc/cron.hourly)
  Jun 08 11:17:01 CCW-HAL CRON[11093]: pam_unix(cron:session): session closed 
for user root
  Jun 08 11:17:06 CCW-HAL kernel: WebKitWebProces[11026]: segfault at 
55bd22ad9adc ip 55bd22ad9adc sp 7ffd1f6adbe8 error 14 likely on CPU 2 
(core 2, socket 0)
  Jun 08 11:17:06 CCW-HAL kernel: Code: Unable to access opcode bytes at 
0x55bd22ad9ab2.
  Jun 08 11:17:36 CCW-HAL gnome-shell[3803]: Window manager warning: 
WM_TRANSIENT_FOR window 0x3a02767 for 0x3a02778 window override-redirect is an 
override-redirect window and this is not correct according to the 

[Desktop-packages] [Bug 2034942] Re: Hanging every time I attempt to add a Google account in GNOME control center

2023-09-08 Thread Jeremy Bícha
*** This bug is a duplicate of bug 2023322 ***
https://bugs.launchpad.net/bugs/2023322

Your bug report indicates you are using Nvidia graphics. Therefore, I am
marking this a duplicate of bug 2023322

** This bug has been marked a duplicate of bug 2023322
   Unable to setup Google Online Accounts with Nvidia drivers

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

Title:
  Hanging every time I attempt to add a Google account in GNOME control
  center

Status in gnome-control-center package in Ubuntu:
  New

Bug description:
  I've tried about 15 times in a row now to add a Google account in
  GNOME control center, and every time it has hung at some point in the
  process before letting me enter my password.

  Sometimes it hangs before it even asks for my Google username.
  Sometimes it hangs right after it accepts my username, before displaying the 
password prompt.
  Sometimes it displays the password prompt but hangs before I am able to enter 
my password.

  Sometimes when it hangs I see the message "GLib: unsetenv() is not
  thread-safe and should not be used after threads are created" in
  journalctl --user --follow output. I wonder if there is a memory
  corruption issue attributable to that. :shrug:

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: gnome-control-center 1:45~rc-1ubuntu2
  ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5
  Uname: Linux 6.3.0-7-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.27.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep  8 12:11:52 2023
  InstallationDate: Installed on 2019-01-02 (1710 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to mantic on 2023-05-20 (111 days ago)

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


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


Re: [Desktop-packages] [Bug 2011281]

2023-09-08 Thread Steve Langasek
On Fri, Sep 08, 2023 at 06:23:22AM -, Nathan Teodosio wrote:
> In bug description:

> 1> when I went to use my saved passwords in chromium today, I found that 
> they were absent.

> In your last comment:

> 2> chromium continues to be able to *use* my saved passwords. But I 
> don't know where they're actually saved

> Which one is correct/up to date?

The second.  Somehow the initial problem corrected itself along the way.  So
Chromium can *use* passwords and *save* passwords but it will not *display*
passwords.

> Likewise for

> 3> I found that there was a 
> ~/snap/chromium/common/chromium/Default/Login Data.old containing all of 
> my passwords, and a ~/snap/chromium/common/chromium/Default/Login Data 
> containing a single password entry

> and

> 4> But I don't know where they're actually saved

> It looks impossible that Chromium is accessing passwords from 'Login 
> Data.old'; there is no longer any reference to that, anywhere, so I 
> think quote 3 might not be up to date.

It contained all passwords that had been saved in my browser prior to this
issue.

Currently, I have a ~/snap/chromium/common/chromium/Default/Login Data which
was last modified September 5.  So perhaps passwords are still being written
here.

> Depending on the situation you could try --password-store=basic, but 
> given the already buggy circumstances, better have those configuration 
> files backed up.

> Without a reproducible case and access to those data files, which of 
> course you must not share as it contains passwords, this is hard to debug.

So for you, chrome://settings/passwords shows your passwords under 'Saved
Passwords' without having to specify --password-store=basic?

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

Title:
  chromium snap upgrade "lost" my passwords

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  On upgrade to chromium snap revision 2333 (now since upgraded to
  2367), I received a window with a notice about password migration:

  "Password storage via the Gnome keyring has been fixed, but for it to
  work, you have to rename your old
  ~/snap/chromium/common/chromium/Default/Login Data file so that a new,
  working one can replace it."

  I don't remember if I did this or not.  However, when I went to use my
  saved passwords in chromium today, I found that they were absent.

  Tracking down the data in the chromium profile, I found that there was
  a ~/snap/chromium/common/chromium/Default/Login Data.old containing
  all of my passwords, and a
  ~/snap/chromium/common/chromium/Default/Login Data containing a single
  password entry for a site that I happened to have created a new login
  for in the past few days.

  That's not a very user-friendly experience on upgrade.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2011281/+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 2013533] Re: segfault in iris_dri.so when resuming from sleep

2023-09-08 Thread Dominik Stadler
It did not re-occur recently, so I think it can be closed as "fixed" by
the newer package for now.

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

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

Title:
  segfault in iris_dri.so when resuming from sleep

Status in mesa package in Ubuntu:
  Fix Released

Bug description:
  When resuming from sleep, the desktop crashes and restarts and I am
  presented with the display-manager log-in screen. All UI applications
  were terminated as well.

  It happens often, but not always.

  I have a Display connected via USB-C/Thunderbolt and usually I power
  it on along resuming the Laptop from sleep, maybe some timing there is
  related.

  system-logs contain the following crash-info:

  Mar 31 08:37:47 dstathink /usr/libexec/gdm-x-session[2009152]: XXX: resource 
creation failed
  Mar 31 08:37:47 dstathink /usr/libexec/gdm-x-session[2009152]: (EE)
  Mar 31 08:37:47 dstathink /usr/libexec/gdm-x-session[2009152]: (EE) Backtrace:
  Mar 31 08:37:47 dstathink /usr/libexec/gdm-x-session[2009152]: (EE) 0: 
/usr/lib/xorg/Xorg (?+0x0) [0x565164614729]
  Mar 31 08:37:47 dstathink /usr/libexec/gdm-x-session[2009152]: (EE) 1: 
/lib/x86_64-linux-gnu/libc.so.6 (?+0x0) [0x7fdb7530a520]
  Mar 31 08:37:47 dstathink /usr/libexec/gdm-x-session[2009152]: (EE) 2: 
/usr/lib/x86_64-linux-gnu/dri/iris_dri.so (?+0x0) [0x7fdb73d25c8e]
  Mar 31 08:37:47 dstathink /usr/libexec/gdm-x-session[2009152]: (EE) 3: 
/usr/lib/x86_64-linux-gnu/dri/iris_dri.so (?+0x0) [0x7fdb73afa90e]
  Mar 31 08:37:47 dstathink /usr/libexec/gdm-x-session[2009152]: (EE) 4: 
/usr/lib/x86_64-linux-gnu/dri/iris_dri.so (?+0x0) [0x7fdb7312f7bc]
  Mar 31 08:37:47 dstathink /usr/libexec/gdm-x-session[2009152]: (EE) 5: 
/usr/lib/x86_64-linux-gnu/dri/iris_dri.so (?+0x0) [0x7fdb730f0cff]
  Mar 31 08:37:47 dstathink /usr/libexec/gdm-x-session[2009152]: (EE) 6: 
/usr/lib/x86_64-linux-gnu/dri/iris_dri.so (?+0x0) [0x7fdb730f41a9]
  Mar 31 08:37:47 dstathink /usr/libexec/gdm-x-session[2009152]: (EE) 7: 
/usr/lib/x86_64-linux-gnu/dri/iris_dri.so (?+0x0) [0x7fdb730fa919]
  Mar 31 08:37:47 dstathink /usr/libexec/gdm-x-session[2009152]: (EE) 8: 
/usr/lib/xorg/modules/libglamoregl.so (?+0x0) [0x7fdb74b5ea53]
  Mar 31 08:37:47 dstathink /usr/libexec/gdm-x-session[2009152]: (EE) 9: 
/usr/lib/xorg/modules/libglamoregl.so (?+0x0) [0x7fdb74b4daa1]
  Mar 31 08:37:47 dstathink /usr/libexec/gdm-x-session[2009152]: (EE) 10: 
/usr/lib/xorg/Xorg (?+0x0) [0x5651645f1a0b]
  Mar 31 08:37:47 dstathink /usr/libexec/gdm-x-session[2009152]: (EE) 11: 
/usr/lib/xorg/Xorg (?+0x0) [0x5651645f2166]
  Mar 31 08:37:47 dstathink /usr/libexec/gdm-x-session[2009152]: (EE) 12: 
/usr/lib/xorg/modules/libglamoregl.so (?+0x0) [0x7fdb74b4e1b8]
  Mar 31 08:37:47 dstathink /usr/libexec/gdm-x-session[2009152]: (EE) 13: 
/usr/lib/xorg/Xorg (?+0x0) [0x565164584a56]
  Mar 31 08:37:47 dstathink /usr/libexec/gdm-x-session[2009152]: (EE) 14: 
/usr/lib/xorg/Xorg (?+0x0) [0x565164537a15]
  Mar 31 08:37:47 dstathink /usr/libexec/gdm-x-session[2009152]: (EE) 15: 
/usr/lib/xorg/Xorg (?+0x0) [0x56516449e4b5]
  Mar 31 08:37:47 dstathink /usr/libexec/gdm-x-session[2009152]: (EE) 16: 
/usr/lib/xorg/Xorg (?+0x0) [0x5651644a2534]
  Mar 31 08:37:47 dstathink /usr/libexec/gdm-x-session[2009152]: (EE) 17: 
/lib/x86_64-linux-gnu/libc.so.6 (?+0x0) [0x7fdb752f1d90]
  Mar 31 08:37:47 dstathink /usr/libexec/gdm-x-session[2009152]: (EE) 18: 
/lib/x86_64-linux-gnu/libc.so.6 (?+0x0) [0x7fdb752f1e40]
  Mar 31 08:37:47 dstathink /usr/libexec/gdm-x-session[2009152]: (EE) 19: 
/usr/lib/xorg/Xorg (?+0x0) [0x56516448b605]
  Mar 31 08:37:47 dstathink /usr/libexec/gdm-x-session[2009152]: (EE)
  Mar 31 08:37:47 dstathink /usr/libexec/gdm-x-session[2009152]: (EE) 
Segmentation fault at address 0x10c
  Mar 31 08:37:47 dstathink /usr/libexec/gdm-x-session[2009152]: (EE)
  Mar 31 08:37:47 dstathink /usr/libexec/gdm-x-session[2009152]: Fatal server 
error:
  Mar 31 08:37:47 dstathink /usr/libexec/gdm-x-session[2009152]: (EE) Caught 
signal 11 (Segmentation fault). Server aborting
  Mar 31 08:37:47 dstathink /usr/libexec/gdm-x-session[2009152]: (EE)
  Mar 31 08:37:47 dstathink /usr/libexec/gdm-x-session[2009152]: (EE)
  Mar 31 08:37:47 dstathink /usr/libexec/gdm-x-session[2009152]: Please consult 
the The X.Org Foundation support
  Mar 31 08:37:47 dstathink /usr/libexec/gdm-x-session[2009152]: #011 at 
http://wiki.x.org
  Mar 31 08:37:47 dstathink /usr/libexec/gdm-x-session[2009152]:  for help.
  Mar 31 08:37:47 dstathink /usr/libexec/gdm-x-session[2009152]: (EE) Please 
also check the log file at "/home/dstadler/.local/share/xorg/Xorg.0.log" for 
additional information.
  Mar 31 08:37:47 dstathink /usr/libexec/gdm-x-session[2009152]: (EE)
  Mar 31 08:37:47 dstathink /usr/libexec/gdm-x-session[2009152]: (II) AIGLX: 
Suspending AIGLX clients for VT switch
  Mar 31 08:37:47 dstathink 

[Desktop-packages] [Bug 2034942] Re: Hanging every time I attempt to add a Google account in GNOME control center

2023-09-08 Thread Jonathan Kamens
Tried building gnome-control-center from source and running gnome-
control-center-goa-helper under valgrind, no memory errors detected.

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

Title:
  Hanging every time I attempt to add a Google account in GNOME control
  center

Status in gnome-control-center package in Ubuntu:
  New

Bug description:
  I've tried about 15 times in a row now to add a Google account in
  GNOME control center, and every time it has hung at some point in the
  process before letting me enter my password.

  Sometimes it hangs before it even asks for my Google username.
  Sometimes it hangs right after it accepts my username, before displaying the 
password prompt.
  Sometimes it displays the password prompt but hangs before I am able to enter 
my password.

  Sometimes when it hangs I see the message "GLib: unsetenv() is not
  thread-safe and should not be used after threads are created" in
  journalctl --user --follow output. I wonder if there is a memory
  corruption issue attributable to that. :shrug:

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: gnome-control-center 1:45~rc-1ubuntu2
  ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5
  Uname: Linux 6.3.0-7-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.27.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep  8 12:11:52 2023
  InstallationDate: Installed on 2019-01-02 (1710 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to mantic on 2023-05-20 (111 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2034942/+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 2034942] [NEW] Hanging every time I attempt to add a Google account in GNOME control center

2023-09-08 Thread Jonathan Kamens
Public bug reported:

I've tried about 15 times in a row now to add a Google account in GNOME
control center, and every time it has hung at some point in the process
before letting me enter my password.

Sometimes it hangs before it even asks for my Google username.
Sometimes it hangs right after it accepts my username, before displaying the 
password prompt.
Sometimes it displays the password prompt but hangs before I am able to enter 
my password.

Sometimes when it hangs I see the message "GLib: unsetenv() is not
thread-safe and should not be used after threads are created" in
journalctl --user --follow output. I wonder if there is a memory
corruption issue attributable to that. :shrug:

ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: gnome-control-center 1:45~rc-1ubuntu2
ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5
Uname: Linux 6.3.0-7-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.27.0-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Fri Sep  8 12:11:52 2023
InstallationDate: Installed on 2019-01-02 (1710 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3)
SourcePackage: gnome-control-center
UpgradeStatus: Upgraded to mantic on 2023-05-20 (111 days ago)

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


** Tags: amd64 apport-bug mantic third-party-packages

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

Title:
  Hanging every time I attempt to add a Google account in GNOME control
  center

Status in gnome-control-center package in Ubuntu:
  New

Bug description:
  I've tried about 15 times in a row now to add a Google account in
  GNOME control center, and every time it has hung at some point in the
  process before letting me enter my password.

  Sometimes it hangs before it even asks for my Google username.
  Sometimes it hangs right after it accepts my username, before displaying the 
password prompt.
  Sometimes it displays the password prompt but hangs before I am able to enter 
my password.

  Sometimes when it hangs I see the message "GLib: unsetenv() is not
  thread-safe and should not be used after threads are created" in
  journalctl --user --follow output. I wonder if there is a memory
  corruption issue attributable to that. :shrug:

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: gnome-control-center 1:45~rc-1ubuntu2
  ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5
  Uname: Linux 6.3.0-7-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.27.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep  8 12:11:52 2023
  InstallationDate: Installed on 2019-01-02 (1710 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to mantic on 2023-05-20 (111 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2034942/+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 2034672] Re: gnome-shell crashed with GLXBadDrawable on startup in a Xorg session

2023-09-08 Thread Ubuntu QA Website
This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
https://iso.qa.ubuntu.com/qatracker/reports/bugs/2034672

** Tags added: iso-testing

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

Title:
  gnome-shell crashed with GLXBadDrawable on startup in a Xorg session

Status in Mutter:
  New
Status in mutter package in Ubuntu:
  In Progress

Bug description:
  Mantic 20230907 on Latitude 3320

  Crash on boot of the live session

  ProblemType: Crash
  DistroRelease: Ubuntu 23.10
  Package: gnome-shell 45~rc-0ubuntu1
  ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5
  Uname: Linux 6.3.0-7-generic x86_64
  NonfreeKernelModules: zfs
  ApportVersion: 2.27.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CasperVersion: 1.482
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Sep  7 08:02:08 2023
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  ExecutableTimestamp: 1694028853
  LiveMediaBuild: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230907)
  ProcCmdline: /usr/bin/gnome-shell
  ProcCwd: /home/ubuntu
  ProcEnviron:
   LANG=C.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  RelatedPackageVersions: mutter-common 45~rc-0ubuntu1
  Signal: 5
  SourcePackage: gnome-shell
  StacktraceTop:
   g_log_structured_array () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_log_default_handler () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_logv () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_log () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/mutter-13/libmutter-mtk-13.so.0
  Title: gnome-shell crashed with signal 5 in g_log_structured_array()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo users
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/2034672/+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 2034763] Re: Flatpak applications ignore appearance settings with glib2.0 2.77.3 and xdg-desktop-portal 1.17.2

2023-09-08 Thread Jeremy Bícha
** Package changed: xdg-desktop-portal (Ubuntu) => plasma-workspace
(Ubuntu)

** Changed in: plasma-workspace (Ubuntu)
   Importance: Undecided => High

** Changed in: plasma-workspace (Ubuntu)
   Status: New => Triaged

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

** Also affects: xdg-desktop-portal-kde (Debian) via
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1050798
   Importance: Unknown
   Status: Unknown

** Package changed: plasma-workspace (Ubuntu) => xdg-desktop-portal-kde
(Ubuntu)

** No longer affects: glib2.0 (Ubuntu)

** Tags added: rls-mm-incoming

** Summary changed:

- Flatpak applications ignore appearance settings with glib2.0 2.77.3 and 
xdg-desktop-portal 1.17.2
+ KDE Plasma: Flatpak applications ignore appearance settings with 
xdg-desktop-portal 1.17.2-1ubuntu1

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

Title:
  KDE Plasma: Flatpak applications ignore appearance settings with xdg-
  desktop-portal 1.17.2-1ubuntu1

Status in xdg-desktop-portal-kde package in Ubuntu:
  Triaged
Status in xdg-desktop-portal-kde package in Debian:
  Unknown

Bug description:
  I use Plasma desktop in Mantic. With the latest versions of glib2.0
  and xdg-desktop-portal all Flatpak applications ignore host settings
  like GTK theme, cursor theme and window controls position. I can get
  proper appearance only in the following state:

  > sudo apt list --upgradable 
  Listing... Done
  libglib2.0-0/mantic 2.77.3-1 amd64 [upgradable from: 2.77.1-1]
  libglib2.0-bin/mantic 2.77.3-1 amd64 [upgradable from: 2.77.1-1]
  libglib2.0-data/mantic,mantic 2.77.3-1 all [upgradable from: 2.77.1-1]
  xdg-desktop-portal/mantic 1.17.2-1ubuntu1 amd64 [upgradable from: 
1.16.0-3ubuntu1]

  Upgrading either glib2.0 or xdg-desktop-portal causes the problem, so
  I don't know exactly which package causes this incompatibility.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal-kde/+bug/2034763/+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 2034928] Re: gnome-shell crashed with signal 5 in g_log_structured_array()

2023-09-08 Thread Apport retracing service
*** This bug is a duplicate of bug 2034672 ***
https://bugs.launchpad.net/bugs/2034672

Thank you for taking the time to report this crash and helping to make
this software better.  This particular crash has already been reported
and is a duplicate of bug #2034672, so is being marked as such.  Please
look at the other bug report to see if there is any missing information
that you can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report.  Please continue to report any other bugs you may
find.

** Attachment removed: "CoreDump.gz"
   
https://bugs.launchpad.net/bugs/2034928/+attachment/5699277/+files/CoreDump.gz

** Attachment removed: "Disassembly.txt"
   
https://bugs.launchpad.net/bugs/2034928/+attachment/5699279/+files/Disassembly.txt

** Attachment removed: "ProcMaps.txt"
   
https://bugs.launchpad.net/bugs/2034928/+attachment/5699283/+files/ProcMaps.txt

** Attachment removed: "ProcStatus.txt"
   
https://bugs.launchpad.net/bugs/2034928/+attachment/5699284/+files/ProcStatus.txt

** Attachment removed: "Registers.txt"
   
https://bugs.launchpad.net/bugs/2034928/+attachment/5699285/+files/Registers.txt

** Attachment removed: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/2034928/+attachment/5699287/+files/Stacktrace.txt

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/2034928/+attachment/5699288/+files/ThreadStacktrace.txt

** This bug has been marked a duplicate of bug 2034672
   gnome-shell crashed with GLXBadDrawable on startup in a Xorg session

** Tags removed: need-amd64-retrace

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

Title:
  gnome-shell crashed with signal 5 in g_log_structured_array()

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  gnome-shell crashed with signal 5 in g_log_structured_array()

  Testing Ubuntu Mantic Desktop Daily ISO dated 08.09.2023

  Booted the ISO media and the system crashed with an internal error

  ProblemType: Crash
  DistroRelease: Ubuntu 23.10
  Package: gnome-shell 45~rc-0ubuntu1
  ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5
  Uname: Linux 6.3.0-7-generic x86_64
  NonfreeKernelModules: zfs
  ApportVersion: 2.27.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CasperVersion: 1.482
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep  8 13:18:38 2023
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  LiveMediaBuild: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230908)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   LANG=C.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  RelatedPackageVersions: mutter-common 45~rc-0ubuntu1
  Signal: 5
  SourcePackage: gnome-shell
  StacktraceTop:
   g_log_structured_array () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_log_default_handler () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_logv () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_log () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/mutter-13/libmutter-mtk-13.so.0
  Title: gnome-shell crashed with signal 5 in g_log_structured_array()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo users
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2034928/+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 2034928] [NEW] gnome-shell crashed with signal 5 in g_log_structured_array()

2023-09-08 Thread Leó Kolbeinsson
Public bug reported:

gnome-shell crashed with signal 5 in g_log_structured_array()

Testing Ubuntu Mantic Desktop Daily ISO dated 08.09.2023

Booted the ISO media and the system crashed with an internal error

ProblemType: Crash
DistroRelease: Ubuntu 23.10
Package: gnome-shell 45~rc-0ubuntu1
ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5
Uname: Linux 6.3.0-7-generic x86_64
NonfreeKernelModules: zfs
ApportVersion: 2.27.0-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: unknown
CasperVersion: 1.482
CurrentDesktop: ubuntu:GNOME
Date: Fri Sep  8 13:18:38 2023
DisplayManager: gdm3
ExecutablePath: /usr/bin/gnome-shell
LiveMediaBuild: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230908)
ProcCmdline: /usr/bin/gnome-shell
ProcEnviron:
 LANG=C.UTF-8
 PATH=(custom, no user)
 SHELL=/bin/bash
 XDG_RUNTIME_DIR=
RelatedPackageVersions: mutter-common 45~rc-0ubuntu1
Signal: 5
SourcePackage: gnome-shell
StacktraceTop:
 g_log_structured_array () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_log_default_handler () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_logv () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_log () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/mutter-13/libmutter-mtk-13.so.0
Title: gnome-shell crashed with signal 5 in g_log_structured_array()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo users
separator:

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


** Tags: amd64 apport-crash mantic 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-shell in Ubuntu.
https://bugs.launchpad.net/bugs/2034928

Title:
  gnome-shell crashed with signal 5 in g_log_structured_array()

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  gnome-shell crashed with signal 5 in g_log_structured_array()

  Testing Ubuntu Mantic Desktop Daily ISO dated 08.09.2023

  Booted the ISO media and the system crashed with an internal error

  ProblemType: Crash
  DistroRelease: Ubuntu 23.10
  Package: gnome-shell 45~rc-0ubuntu1
  ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5
  Uname: Linux 6.3.0-7-generic x86_64
  NonfreeKernelModules: zfs
  ApportVersion: 2.27.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CasperVersion: 1.482
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep  8 13:18:38 2023
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  LiveMediaBuild: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230908)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   LANG=C.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  RelatedPackageVersions: mutter-common 45~rc-0ubuntu1
  Signal: 5
  SourcePackage: gnome-shell
  StacktraceTop:
   g_log_structured_array () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_log_default_handler () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_logv () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_log () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/mutter-13/libmutter-mtk-13.so.0
  Title: gnome-shell crashed with signal 5 in g_log_structured_array()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo users
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2034928/+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 2013116] Re: xdg-desktop-portal-gnome 44 causes delays in non-GNOME desktops

2023-09-08 Thread Jeremy Bícha
I'm closing the Lunar tasks based on comment #5 to be realistic that
fixing this issue for Lunar isn't something we are working on.

** Changed in: xdg-desktop-portal-gnome (Ubuntu Lunar)
   Status: Triaged => Won't Fix

** Changed in: xdg-desktop-portal (Ubuntu Lunar)
   Status: Triaged => Won't Fix

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

Title:
  xdg-desktop-portal-gnome 44 causes delays in non-GNOME desktops

Status in xdg-desktop-portal package in Ubuntu:
  Fix Released
Status in xdg-desktop-portal-gnome package in Ubuntu:
  Fix Released
Status in xdg-desktop-portal source package in Lunar:
  Won't Fix
Status in xdg-desktop-portal-gnome source package in Lunar:
  Won't Fix

Bug description:
  Test Case
  -

  - Install xdg-desktop-portal-gnome 44.beta
  - Log out, then log into a non-GNOME desktop like MATE
  - Open an app that uses portals, like the Firefox Snap
  - From the app, open the Open dialog

  What Happens
  
  Nothing for 2 minutes or however long the service timeout takes.
  After that initial timeout, the filechooser dialogs open like normal.

  Other Info
  --
  This is a regression compared to xdg-desktop-portal-gnome 43.
  My understanding is that xdg-desktop-portal currently attempts to load the 
portal backends in alphabetical order. By coincidence, this happens to do what 
we would expect (gnome, then gtk, kde, lxqt, wlr).
  It is expected that systems with multiple desktop environments installed will 
have multiple portal backends installed. These backends should work in any of 
the desktops. (For instance, maybe MATE users want to have the GTK 4.10 icon 
view filechooser for their Flatpak/Snap web browser.)

  Upstream
  ---
  https://gitlab.gnome.org/GNOME/xdg-desktop-portal-gnome/-/issues/74
  https://github.com/flatpak/xdg-desktop-portal/pull/985
  Related: https://bugzilla.redhat.com/show_bug.cgi?id=2154665

  https://www.bassi.io/articles/2023/05/29/configuring-portals/

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal/+bug/2013116/+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 2034907] Re: The surf browser renders white pages with the new webkitgtk

2023-09-08 Thread Sebastien Bacher
checking the denial the profile blocks access to
/usr/share/glvnd/egl_vendor.d/50_mesa.json which is probalby the issue

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

Title:
  The surf browser renders white pages with the new webkitgtk

Status in surf package in Ubuntu:
  New
Status in webkit2gtk package in Ubuntu:
  In Progress

Bug description:
  The new webkit is making
  https://autopkgtest.ubuntu.com/packages/s/surf red

  Debian had the same problem, https://bugs.debian.org/cgi-
  bin/bugreport.cgi?bug=1050777 , but resolved it by adding a libgles2
  depends.

  The solution dopesn't seem to be enough for Ubuntu though and the
  problem can be reproduced in a normal xorg session, for some reason
  libGL is being used instead of libGLES, the problem doesn't happen in
  Debian or Fedora though...

  The bug has been reported upstream now

  https://bugs.webkit.org/show_bug.cgi?id=261268

  
  Testcase
  - install libwebkit2gtk-4.1-0 and libjavascriptcoregtk-4.1-0 from 
mantic-proposed
  - surf http://www.ubuntu.com

  it fails to render content and the journal shows some denials

  after doing
  $ sudo aa-complain /etc/apparmor.d/usr.bin.surf

  the rendering is working as expected

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/surf/+bug/2034907/+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 2034907] Re: The surf browser renders white pages with the new webkitgtk

2023-09-08 Thread Sebastien Bacher
** Description changed:

  The new webkit is making https://autopkgtest.ubuntu.com/packages/s/surf
  red
  
  Debian had the same problem, https://bugs.debian.org/cgi-
  bin/bugreport.cgi?bug=1050777 , but resolved it by adding a libgles2
  depends.
  
  The solution dopesn't seem to be enough for Ubuntu though and the
  problem can be reproduced in a normal xorg session, for some reason
  libGL is being used instead of libGLES, the problem doesn't happen in
  Debian or Fedora though...
  
  The bug has been reported upstream now
  
  https://bugs.webkit.org/show_bug.cgi?id=261268
+ 
+ 
+ Testcase
+ - install libwebkit2gtk-4.1-0 and libjavascriptcoregtk-4.1-0 from 
mantic-proposed
+ - surf http://www.ubuntu.com
+ 
+ it fails to render content and the journal shows some denials
+ 
+ after doing
+ $ sudo aa-complain /etc/apparmor.d/usr.bin.surf
+ 
+ the rendering is working as expected

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

Title:
  The surf browser renders white pages with the new webkitgtk

Status in surf package in Ubuntu:
  New
Status in webkit2gtk package in Ubuntu:
  In Progress

Bug description:
  The new webkit is making
  https://autopkgtest.ubuntu.com/packages/s/surf red

  Debian had the same problem, https://bugs.debian.org/cgi-
  bin/bugreport.cgi?bug=1050777 , but resolved it by adding a libgles2
  depends.

  The solution dopesn't seem to be enough for Ubuntu though and the
  problem can be reproduced in a normal xorg session, for some reason
  libGL is being used instead of libGLES, the problem doesn't happen in
  Debian or Fedora though...

  The bug has been reported upstream now

  https://bugs.webkit.org/show_bug.cgi?id=261268

  
  Testcase
  - install libwebkit2gtk-4.1-0 and libjavascriptcoregtk-4.1-0 from 
mantic-proposed
  - surf http://www.ubuntu.com

  it fails to render content and the journal shows some denials

  after doing
  $ sudo aa-complain /etc/apparmor.d/usr.bin.surf

  the rendering is working as expected

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/surf/+bug/2034907/+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 2034895] Re: [Mantic] No system-config-printer button in Printers tab

2023-09-08 Thread Launchpad Bug Tracker
This bug was fixed in the package system-config-printer -
1.5.18-1ubuntu2

---
system-config-printer (1.5.18-1ubuntu2) mantic; urgency=medium

  * debian/patches/Hide-Printers-app-in-GNOME-and-KDE.patch: include the
.desktop again in GNOME sessions, the access button was removed from
 settings and the GUI isn't installed by default (lp: #2034895)

 -- Sebastien Bacher   Fri, 08 Sep 2023 11:01:31
+0200

** Changed in: system-config-printer (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  [Mantic] No system-config-printer button in Printers tab

Status in system-config-printer package in Ubuntu:
  Fix Released

Bug description:
  Hi,

  Since cups-deb has been finally chosen, this useful button is missing.
  At least, system-config-printer should be offered in apps list, not only in 
command line.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/system-config-printer/+bug/2034895/+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 2034907] Re: The surf browser renders white pages with the new webkitgtk

2023-09-08 Thread Sebastien Bacher
In fact that's an issue due to the surf apparmor profile, details on
https://bugs.webkit.org/show_bug.cgi?id=261268#c10


** Bug watch added: bugs.webkit.org/ #261268
   https://bugs.webkit.org/show_bug.cgi?id=261268

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

** Changed in: surf (Ubuntu)
   Importance: Undecided => High

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

Title:
  The surf browser renders white pages with the new webkitgtk

Status in surf package in Ubuntu:
  New
Status in webkit2gtk package in Ubuntu:
  In Progress

Bug description:
  The new webkit is making
  https://autopkgtest.ubuntu.com/packages/s/surf red

  Debian had the same problem, https://bugs.debian.org/cgi-
  bin/bugreport.cgi?bug=1050777 , but resolved it by adding a libgles2
  depends.

  The solution dopesn't seem to be enough for Ubuntu though and the
  problem can be reproduced in a normal xorg session, for some reason
  libGL is being used instead of libGLES, the problem doesn't happen in
  Debian or Fedora though...

  The bug has been reported upstream now

  https://bugs.webkit.org/show_bug.cgi?id=261268

  
  Testcase
  - install libwebkit2gtk-4.1-0 and libjavascriptcoregtk-4.1-0 from 
mantic-proposed
  - surf http://www.ubuntu.com

  it fails to render content and the journal shows some denials

  after doing
  $ sudo aa-complain /etc/apparmor.d/usr.bin.surf

  the rendering is working as expected

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/surf/+bug/2034907/+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 2033377] Re: New whitespace between digits and colon in time at top of desktop screen

2023-09-08 Thread Gunnar Hjalmarsson
>   1. Patch to revert to a colon in the default US English translation.
> 
>   2. Propose to upstream to not use RATIO in future because fonts don't
> often implement the Mathematical Operators block.

Those were my reflexive thoughts too, especially item 2. But then I saw
that RATIO has been used for several years at the request of GNOME's
design team, and I don't have the energy right now to argue with those
folks. :/

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

Title:
  New whitespace between digits and colon in time at top of desktop
  screen

Status in gnome-desktop package in Ubuntu:
  Won't Fix
Status in language-pack-gnome-en package in Ubuntu:
  Won't Fix
Status in language-pack-gnome-en-base package in Ubuntu:
  Won't Fix
Status in language-selector package in Ubuntu:
  Fix Released

Bug description:
  This has been confirmed in the daily canary image and the daily normal mantic 
image. This whitespace didn't exist in older images or in previous releases. An 
image will be attached in the comments
  --- 
  ProblemType: Bug
  ApportVersion: 2.27.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CloudArchitecture: x86_64
  CloudID: none
  CloudName: none
  CloudPlatform: none
  CloudSubPlatform: config
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 23.10
  InstallationDate: Installed on 2023-08-30 (0 days ago)
  InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230829)
  Package: gnome-shell 44.3-1ubuntu1
  PackageArchitecture: amd64
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5
  RelatedPackageVersions: mutter-common 44.3-1ubuntu1
  Tags: mantic wayland-session
  Uname: Linux 6.3.0-7-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sudo users
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-desktop/+bug/2033377/+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 2034907] [NEW] The surf browser renders white pages with the new webkitgtk

2023-09-08 Thread Sebastien Bacher
Public bug reported:

The new webkit is making https://autopkgtest.ubuntu.com/packages/s/surf
red

Debian had the same problem, https://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=1050777 , but resolved it by adding a libgles2
depends.

The solution dopesn't seem to be enough for Ubuntu though and the
problem can be reproduced in a normal xorg session, for some reason
libGL is being used instead of libGLES, the problem doesn't happen in
Debian or Fedora though...

The bug has been reported upstream now

https://bugs.webkit.org/show_bug.cgi?id=261268

** Affects: webkit2gtk (Ubuntu)
 Importance: High
 Assignee: Sebastien Bacher (seb128)
 Status: In Progress


** Tags: update-excuse

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

Title:
  The surf browser renders white pages with the new webkitgtk

Status in webkit2gtk package in Ubuntu:
  In Progress

Bug description:
  The new webkit is making
  https://autopkgtest.ubuntu.com/packages/s/surf red

  Debian had the same problem, https://bugs.debian.org/cgi-
  bin/bugreport.cgi?bug=1050777 , but resolved it by adding a libgles2
  depends.

  The solution dopesn't seem to be enough for Ubuntu though and the
  problem can be reproduced in a normal xorg session, for some reason
  libGL is being used instead of libGLES, the problem doesn't happen in
  Debian or Fedora though...

  The bug has been reported upstream now

  https://bugs.webkit.org/show_bug.cgi?id=261268

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/webkit2gtk/+bug/2034907/+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 2034895] Re: [Mantic] No system-config-printer button in Printers tab

2023-09-08 Thread Sebastien Bacher
** Changed in: system-config-printer (Ubuntu)
   Status: In Progress => Fix Committed

** Changed in: system-config-printer (Ubuntu)
 Assignee: (unassigned) => Sebastien Bacher (seb128)

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

Title:
  [Mantic] No system-config-printer button in Printers tab

Status in system-config-printer package in Ubuntu:
  Fix Committed

Bug description:
  Hi,

  Since cups-deb has been finally chosen, this useful button is missing.
  At least, system-config-printer should be offered in apps list, not only in 
command line.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/system-config-printer/+bug/2034895/+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 2033377] Re: New whitespace between digits and colon in time at top of desktop screen

2023-09-08 Thread Tim Andersson
Looks like it's fixed in today's daily image ! Lovely stuff :)

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

Title:
  New whitespace between digits and colon in time at top of desktop
  screen

Status in gnome-desktop package in Ubuntu:
  Won't Fix
Status in language-pack-gnome-en package in Ubuntu:
  Won't Fix
Status in language-pack-gnome-en-base package in Ubuntu:
  Won't Fix
Status in language-selector package in Ubuntu:
  Fix Released

Bug description:
  This has been confirmed in the daily canary image and the daily normal mantic 
image. This whitespace didn't exist in older images or in previous releases. An 
image will be attached in the comments
  --- 
  ProblemType: Bug
  ApportVersion: 2.27.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CloudArchitecture: x86_64
  CloudID: none
  CloudName: none
  CloudPlatform: none
  CloudSubPlatform: config
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 23.10
  InstallationDate: Installed on 2023-08-30 (0 days ago)
  InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230829)
  Package: gnome-shell 44.3-1ubuntu1
  PackageArchitecture: amd64
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5
  RelatedPackageVersions: mutter-common 44.3-1ubuntu1
  Tags: mantic wayland-session
  Uname: Linux 6.3.0-7-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sudo users
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-desktop/+bug/2033377/+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 2034895] Re: [Mantic] No system-config-printer button in Printers tab

2023-09-08 Thread Sebastien Bacher
Thanks for the report. we stopped to include the system-config-printer
by default and removed the button from settings  because it's a legacy
application and we believe that the settings should do most of what is
needed. You are right though that we should enable back the ;.desktop so
users who install the utility can find it easily

** Package changed: gnome-control-center (Ubuntu) => system-config-
printer (Ubuntu)

** Changed in: system-config-printer (Ubuntu)
   Importance: Undecided => Low

** Changed in: system-config-printer (Ubuntu)
   Status: New => In Progress

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

Title:
  [Mantic] No system-config-printer button in Printers tab

Status in system-config-printer package in Ubuntu:
  In Progress

Bug description:
  Hi,

  Since cups-deb has been finally chosen, this useful button is missing.
  At least, system-config-printer should be offered in apps list, not only in 
command line.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/system-config-printer/+bug/2034895/+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 1841810] Re: Ubuntu login screen does not show full name if it's slightly too long (but not really that long)

2023-09-08 Thread Bug Watch Updater
** Changed in: gnome-shell
   Status: Unknown => New

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

Title:
  Ubuntu login screen does not show full name if it's slightly too long
  (but not really that long)

Status in GNOME Shell:
  New
Status in gnome-shell package in Ubuntu:
  Triaged

Bug description:
  I use Ubuntu 18.04 LTS with gdm3 3.28.3

  My native language is Spanish and my fullname use accents and hyphens
  (Néstor Rodríguez-Triana Domínguez) but it not appear in the gdm3
  login screen, only my username (nrtriana). My locale is configured
  properly as:

  LANG=es_ES.UTF-8
  LANGUAGE=es_ES
  LC_CTYPE="es_ES.UTF-8"
  LC_NUMERIC="es_ES.UTF-8"
  LC_TIME="es_ES.UTF-8"
  LC_COLLATE="es_ES.UTF-8"
  LC_MONETARY="es_ES.UTF-8"
  LC_MESSAGES="es_ES.UTF-8"
  LC_PAPER="es_ES.UTF-8"
  LC_NAME="es_ES.UTF-8"
  LC_ADDRESS="es_ES.UTF-8"
  LC_TELEPHONE="es_ES.UTF-8"
  LC_MEASUREMENT="es_ES.UTF-8"
  LC_IDENTIFICATION="es_ES.UTF-8"
  LC_ALL=es_ES.UTF-8

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1841810/+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 2034898] Re: my audio of system has crashed as i tried some online solutions to fix problem of pairing my sony WF-C500 earbud to the system

2023-09-08 Thread Naseela Jehan
sudo apt-get install blueman
mv ~/.config/pulse/ ~/.config/pulse.old
sudo apt-get install pavucontrol
sudo add-apt-repository ppa:pipewire-debian/pipewire-upstream
sudo apt update
sudo apt install pipewire
sudo apt install libspa-0.2-bluetooth
sudo apt install pipewire-audio-client-libraries
systemctl --user daemon-reload
systemctl --user --now disable pulseaudio.service pulseaudio.socket
systemctl --user mask pulseaudio
systemctl --user --now enable pipewire-media-session.service
systemctl --user --now enable pipewire.service
pactl info
sudo apt remove ofono
mv ~/.config/pulse/ ~/.config/pulse.old
systemctl --user restart pulseaudio
mv ~/.config/pulse/ ~/.config/pulse.old
systemctl --user restart pulseaudio
pact1 info
sudo add-apt-repository ppa:pipewire-debian/pipewire-upstream
sudo apt update
sudo apt install gstreamer1.0-pipewire libpipewire-0.3-{0,dev,modules} 
libspa-0.2-{bluetooth,dev,jack,modules} 
pipewire{,-{audio-client-libraries,pulse,media-session,bin,locales,tests}}
systemctl --user daemon-reload
systemctl --user --now disable pulseaudio.service pulseaudio.socket
systemctl --user --now enable pipewire pipewire-pulse
pact1 info
pactl info
sudo service bluetooth restart
sudo systemctl restart bluetooth
sudo service bluetooth restart
sudo systemctl restart bluetooth
sudo apt update
sudo apt upgrade
pacl info

these are the commands ihad given

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

Title:
  my audio of system has crashed as i tried some online solutions to fix
  problem of pairing my sony WF-C500 earbud to the system

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  i have done this Open your terminal and follow these steps:

  We will use a PPA for adding Pipewire to Ubuntu 20.04, which is
  maintained regularly:

  sudo add-apt-repository ppa:pipewire-debian/pipewire-upstream

  To update the PPA packages in your system do:

  sudo apt update

  Install the package:

  sudo apt install pipewire

  There is also a dependency needed to be installed with Pipewire,
  otherwise you will face the issue of “Bluetooth headset won’t connect
  after installing pipewire”. Install the dependency by:

  sudo apt install libspa-0.2-bluetooth

  Now, to install the client libraries:

  sudo apt install pipewire-audio-client-libraries

  Reload the daemon:

  systemctl --user daemon-reload

  Disable PulseAudio:

  systemctl --user --now disable pulseaudio.service
  pulseaudio.socket

  If you are on Ubuntu 20.04, you also need to “mask” the PulseAudio
  by:

  systemctl --user mask pulseaudio

  I am not sure but, if possible, you can try to run this on other versions too.
  9. After a new update of Pipewire, you also need to enable 
pipewire-media-session-service:

 systemctl --user --now enable pipewire-media-session.service

  You can ensure that Pipewire is now running through:

  pactl info

  This command will give the following output, in Server Name you
  can see:

  PulseAudio (on PipeWire 0.3.28)

  Things should be working by now and you can see your microphone.

  If it doesn’t show up, then try restarting Pipewire by this command:

  systemctl --user restart pipewire

  
  then after that
  i did 
  mv ~/.config/pulse/ ~/.config/pulse.old

  systemctl --user restart pulseaudio

  mv ~/.config/pulse/ ~/.config/pulse.old

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: pulseaudio 1:16.1+dfsg1-1ubuntu3.1
  ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7
  Uname: Linux 5.19.0-21-generic x86_64
  ApportVersion: 2.23.1-0ubuntu3.2
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', 
'/dev/snd/pcmC0D17p', '/dev/snd/pcmC0D16p', '/dev/snd/pcmC0D15p', 
'/dev/snd/pcmC0D14p', '/dev/snd/pcmC0D13p', '/dev/snd/pcmC0D12p', 
'/dev/snd/pcmC0D11p', '/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', 
'/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', 
'/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep  8 13:49:46 2023
  InstallationDate: Installed on 2023-09-04 (3 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020)
  ProcEnviron:
   LANGUAGE=en_IN:en
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_IN
   SHELL=/bin/bash
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: pulseaudio
  Symptom: audio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/31/2022
  dmi.bios.release: 1.18
  dmi.bios.vendor: 

[Desktop-packages] [Bug 2034898] [NEW] my audio of system has crashed as i tried some online solutions to fix problem of pairing my sony WF-C500 earbud to the system

2023-09-08 Thread Naseela Jehan
Public bug reported:

i have done this Open your terminal and follow these steps:

We will use a PPA for adding Pipewire to Ubuntu 20.04, which is
maintained regularly:

sudo add-apt-repository ppa:pipewire-debian/pipewire-upstream

To update the PPA packages in your system do:

sudo apt update

Install the package:

sudo apt install pipewire

There is also a dependency needed to be installed with Pipewire,
otherwise you will face the issue of “Bluetooth headset won’t connect
after installing pipewire”. Install the dependency by:

sudo apt install libspa-0.2-bluetooth

Now, to install the client libraries:

sudo apt install pipewire-audio-client-libraries

Reload the daemon:

systemctl --user daemon-reload

Disable PulseAudio:

systemctl --user --now disable pulseaudio.service pulseaudio.socket

If you are on Ubuntu 20.04, you also need to “mask” the PulseAudio
by:

systemctl --user mask pulseaudio

I am not sure but, if possible, you can try to run this on other versions too.
9. After a new update of Pipewire, you also need to enable 
pipewire-media-session-service:

   systemctl --user --now enable pipewire-media-session.service

You can ensure that Pipewire is now running through:

pactl info

This command will give the following output, in Server Name you can
see:

PulseAudio (on PipeWire 0.3.28)

Things should be working by now and you can see your microphone.

If it doesn’t show up, then try restarting Pipewire by this command:

systemctl --user restart pipewire


then after that
i did 
mv ~/.config/pulse/ ~/.config/pulse.old

systemctl --user restart pulseaudio

mv ~/.config/pulse/ ~/.config/pulse.old

ProblemType: Bug
DistroRelease: Ubuntu 22.10
Package: pulseaudio 1:16.1+dfsg1-1ubuntu3.1
ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7
Uname: Linux 5.19.0-21-generic x86_64
ApportVersion: 2.23.1-0ubuntu3.2
Architecture: amd64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', 
'/dev/snd/pcmC0D17p', '/dev/snd/pcmC0D16p', '/dev/snd/pcmC0D15p', 
'/dev/snd/pcmC0D14p', '/dev/snd/pcmC0D13p', '/dev/snd/pcmC0D12p', 
'/dev/snd/pcmC0D11p', '/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', 
'/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', 
'/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Fri Sep  8 13:49:46 2023
InstallationDate: Installed on 2023-09-04 (3 days ago)
InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020)
ProcEnviron:
 LANGUAGE=en_IN:en
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=en_IN
 SHELL=/bin/bash
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
RebootRequiredPkgs: Error: path contained symlinks.
SourcePackage: pulseaudio
Symptom: audio
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/31/2022
dmi.bios.release: 1.18
dmi.bios.vendor: LENOVO
dmi.bios.version: R1XET36W (1.18 )
dmi.board.asset.tag: Not Available
dmi.board.name: 21C1S0BY00
dmi.board.vendor: LENOVO
dmi.board.version: Not Defined
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.13
dmi.modalias: 
dmi:bvnLENOVO:bvrR1XET36W(1.18):bd08/31/2022:br1.18:efr1.13:svnLENOVO:pn21C1S0BY00:pvrThinkPadL14Gen3:rvnLENOVO:rn21C1S0BY00:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21C1_BU_Think_FM_ThinkPadL14Gen3:
dmi.product.family: ThinkPad L14 Gen 3
dmi.product.name: 21C1S0BY00
dmi.product.sku: LENOVO_MT_21C1_BU_Think_FM_ThinkPad L14 Gen 3
dmi.product.version: ThinkPad L14 Gen 3
dmi.sys.vendor: LENOVO

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


** Tags: amd64 apport-bug kinetic

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

Title:
  my audio of system has crashed as i tried some online solutions to fix
  problem of pairing my sony WF-C500 earbud to the system

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  i have done this Open your terminal and follow these steps:

  We will use a PPA for adding Pipewire to Ubuntu 20.04, which is
  maintained regularly:

  sudo add-apt-repository ppa:pipewire-debian/pipewire-upstream

  To update the PPA packages in your system do:

  sudo apt update

  Install the package:

  sudo apt install pipewire

  There is also a dependency needed to be installed with Pipewire,
  otherwise you will face the issue of “Bluetooth headset won’t connect
  after installing pipewire”. Install the dependency by:

  sudo apt install libspa-0.2-bluetooth

  Now, to install the client libraries:


[Desktop-packages] [Bug 2034763] Re: Flatpak applications ignore appearance settings with glib2.0 2.77.3 and xdg-desktop-portal 1.17.2

2023-09-08 Thread Sebastien Bacher
The issue comes from the new xdg-desktop-portal, see
https://github.com/flatpak/xdg-desktop-portal/pull/1082 for details

The new configuration system gives more flexibility to the desktop
environment to select the portal variants that should be used but it
might require tweaks from those desktop environments

The GNOME configuration which fixes the issue was added in 
https://salsa.debian.org/gnome-team/gnome-session/-/commit/b201c9c4 
which is including in the gnome-session version uploaded to Ubuntu yesterday

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

Title:
  Flatpak applications ignore appearance settings with glib2.0 2.77.3
  and xdg-desktop-portal 1.17.2

Status in glib2.0 package in Ubuntu:
  Invalid
Status in xdg-desktop-portal package in Ubuntu:
  New

Bug description:
  I use Plasma desktop in Mantic. With the latest versions of glib2.0
  and xdg-desktop-portal all Flatpak applications ignore host settings
  like GTK theme, cursor theme and window controls position. I can get
  proper appearance only in the following state:

  > sudo apt list --upgradable 
  Listing... Done
  libglib2.0-0/mantic 2.77.3-1 amd64 [upgradable from: 2.77.1-1]
  libglib2.0-bin/mantic 2.77.3-1 amd64 [upgradable from: 2.77.1-1]
  libglib2.0-data/mantic,mantic 2.77.3-1 all [upgradable from: 2.77.1-1]
  xdg-desktop-portal/mantic 1.17.2-1ubuntu1 amd64 [upgradable from: 
1.16.0-3ubuntu1]

  Upgrading either glib2.0 or xdg-desktop-portal causes the problem, so
  I don't know exactly which package causes this incompatibility.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/2034763/+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 2034763] Re: Flatpak applications ignore appearance settings with glib2.0 2.77.3 and xdg-desktop-portal 1.17.2

2023-09-08 Thread Sebastien Bacher
** Changed in: glib2.0 (Ubuntu)
   Status: New => Invalid

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

Title:
  Flatpak applications ignore appearance settings with glib2.0 2.77.3
  and xdg-desktop-portal 1.17.2

Status in glib2.0 package in Ubuntu:
  Invalid
Status in xdg-desktop-portal package in Ubuntu:
  New

Bug description:
  I use Plasma desktop in Mantic. With the latest versions of glib2.0
  and xdg-desktop-portal all Flatpak applications ignore host settings
  like GTK theme, cursor theme and window controls position. I can get
  proper appearance only in the following state:

  > sudo apt list --upgradable 
  Listing... Done
  libglib2.0-0/mantic 2.77.3-1 amd64 [upgradable from: 2.77.1-1]
  libglib2.0-bin/mantic 2.77.3-1 amd64 [upgradable from: 2.77.1-1]
  libglib2.0-data/mantic,mantic 2.77.3-1 all [upgradable from: 2.77.1-1]
  xdg-desktop-portal/mantic 1.17.2-1ubuntu1 amd64 [upgradable from: 
1.16.0-3ubuntu1]

  Upgrading either glib2.0 or xdg-desktop-portal causes the problem, so
  I don't know exactly which package causes this incompatibility.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/2034763/+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 2011281]

2023-09-08 Thread Nathan Teodosio
In bug description:

1> when I went to use my saved passwords in chromium today, I found that 
they were absent.

In your last comment:

2> chromium continues to be able to *use* my saved passwords. But I 
don't know where they're actually saved

Which one is correct/up to date?

Likewise for

3> I found that there was a 
~/snap/chromium/common/chromium/Default/Login Data.old containing all of 
my passwords, and a ~/snap/chromium/common/chromium/Default/Login Data 
containing a single password entry

and

4> But I don't know where they're actually saved

It looks impossible that Chromium is accessing passwords from 'Login 
Data.old'; there is no longer any reference to that, anywhere, so I 
think quote 3 might not be up to date.

Depending on the situation you could try --password-store=basic, but 
given the already buggy circumstances, better have those configuration 
files backed up.

Without a reproducible case and access to those data files, which of 
course you must not share as it contains passwords, this is hard to debug.

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

Title:
  chromium snap upgrade "lost" my passwords

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  On upgrade to chromium snap revision 2333 (now since upgraded to
  2367), I received a window with a notice about password migration:

  "Password storage via the Gnome keyring has been fixed, but for it to
  work, you have to rename your old
  ~/snap/chromium/common/chromium/Default/Login Data file so that a new,
  working one can replace it."

  I don't remember if I did this or not.  However, when I went to use my
  saved passwords in chromium today, I found that they were absent.

  Tracking down the data in the chromium profile, I found that there was
  a ~/snap/chromium/common/chromium/Default/Login Data.old containing
  all of my passwords, and a
  ~/snap/chromium/common/chromium/Default/Login Data containing a single
  password entry for a site that I happened to have created a new login
  for in the past few days.

  That's not a very user-friendly experience on upgrade.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2011281/+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 2034895] [NEW] [Mantic] No system-config-printer button in Printers tab

2023-09-08 Thread Francois Thirioux
Public bug reported:

Hi,

Since cups-deb has been finally chosen, this useful button is missing.
At least, system-config-printer should be offered in apps list, not only in 
command line.

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

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

Title:
  [Mantic] No system-config-printer button in Printers tab

Status in gnome-control-center package in Ubuntu:
  New

Bug description:
  Hi,

  Since cups-deb has been finally chosen, this useful button is missing.
  At least, system-config-printer should be offered in apps list, not only in 
command line.

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