[Desktop-packages] [Bug 2064096] Re: Services fail to start in noble deployed with TPM+FDE

[James Paton-Smith]

Answering questions from #2064088

Q: Can you also show the output of: ps fauxwZ

A: See attached

** Attachment added: "ps"
   
https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/2064096/+attachment/5774011/+files/ps

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

Title:
  Services fail to start in noble deployed with TPM+FDE

Status in apparmor package in Ubuntu:
  New
Status in cups package in Ubuntu:
  Confirmed
Status in rsyslog package in Ubuntu:
  Confirmed
Status in sssd package in Ubuntu:
  Confirmed

Bug description:
  What's known so far:
  - 24.04 desktop deployed with TPM+FDE shows this bug
  - services confined with apparmor that need to access something in 
/run/systemd (like the notify socket) fail to do so, even if the apparmor 
profile is in complain mode. And the apparmor profile does already have rules 
to allow that access
  - only after running aa-disable  can the service start fine
  - paths logged by the apparmor DENIED or ALLOWED messages are missing the 
"/run" prefix from "/run/systemd/..".
  - When we add rules to the profile using "/systemd/" (i.e., also dropping 
the /run prefix), then it works
  - other access in /run/systemd/ are also blocked, but the most noticeable one 
is the notify mechanism
  - comment #2 also states that azure CVM images are also impacted
  - comment #4 has instructions on how to create such a VM locally with LXD vms

  Original description follows:

  This might be related to #2064088

  The rsyslog service is continually timing out and restarting. If I use
  a service drop-in file and change the 'Type' from 'notify' to
  'simple', the service starts and appears to work normally.

  In the journal, I can see the attached apparmor errors. I can't make
  sense of them, but if it's a similar issue to #2064088, then I suspect
  apparmor is preventing the systemd notify function from alerting
  systemd that the service is up and running.

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: rsyslog 8.2312.0-3ubuntu9
  ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1
  Uname: Linux 6.8.0-31-generic x86_64
  ApportVersion: 2.28.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckMismatches: ./boot/grub/grub.cfg
  CasperMD5CheckResult: fail
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr 29 10:37:46 2024
  ProcEnviron:
   LANG=en_GB.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  SourcePackage: rsyslog
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2064096/+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 2064096] Re: Services fail to start in noble deployed with TPM+FDE

[James Paton-Smith]

Answering questions from #2064088

Q: Did you install this fde/tpm setup using the ubuntu desktop noble installer? 
Or was hit some manual setup?
A: The install was performed using autoinstall with the desktop ISO. Attached 
is a copy of the autoinstall yaml

** Attachment added: "autoinstall user-data YAML"
   
https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/2064096/+attachment/5774010/+files/user-data

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

Title:
  Services fail to start in noble deployed with TPM+FDE

Status in apparmor package in Ubuntu:
  New
Status in cups package in Ubuntu:
  Confirmed
Status in rsyslog package in Ubuntu:
  Confirmed
Status in sssd package in Ubuntu:
  Confirmed

Bug description:
  What's known so far:
  - 24.04 desktop deployed with TPM+FDE shows this bug
  - services confined with apparmor that need to access something in 
/run/systemd (like the notify socket) fail to do so, even if the apparmor 
profile is in complain mode. And the apparmor profile does already have rules 
to allow that access
  - only after running aa-disable  can the service start fine
  - paths logged by the apparmor DENIED or ALLOWED messages are missing the 
"/run" prefix from "/run/systemd/..".
  - When we add rules to the profile using "/systemd/" (i.e., also dropping 
the /run prefix), then it works
  - other access in /run/systemd/ are also blocked, but the most noticeable one 
is the notify mechanism
  - comment #2 also states that azure CVM images are also impacted
  - comment #4 has instructions on how to create such a VM locally with LXD vms

  Original description follows:

  This might be related to #2064088

  The rsyslog service is continually timing out and restarting. If I use
  a service drop-in file and change the 'Type' from 'notify' to
  'simple', the service starts and appears to work normally.

  In the journal, I can see the attached apparmor errors. I can't make
  sense of them, but if it's a similar issue to #2064088, then I suspect
  apparmor is preventing the systemd notify function from alerting
  systemd that the service is up and running.

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: rsyslog 8.2312.0-3ubuntu9
  ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1
  Uname: Linux 6.8.0-31-generic x86_64
  ApportVersion: 2.28.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckMismatches: ./boot/grub/grub.cfg
  CasperMD5CheckResult: fail
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr 29 10:37:46 2024
  ProcEnviron:
   LANG=en_GB.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  SourcePackage: rsyslog
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2064096/+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 2063961] [NEW] Microsoft 365 account keeps disconnecting

[Mark Smith]

Public bug reported:

When I use the new (24.04) settings and 'Online Accounts' to connect to 
Microsoft 365, it authenticates, works well for about 5 minutes and then 
disconnects.
I have to remove that account and redo it every time I want to use it.

ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: ubuntu-settings 24.04.3
ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1
Uname: Linux 6.8.0-31-generic x86_64
ApportVersion: 2.28.1-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Sat Apr 27 19:04:06 2024
InstallationDate: Installed on 2024-04-27 (0 days ago)
InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424)
PackageArchitecture: all
SourcePackage: ubuntu-settings
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug noble

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

Title:
  Microsoft 365 account keeps disconnecting

Status in ubuntu-settings package in Ubuntu:
  New

Bug description:
  When I use the new (24.04) settings and 'Online Accounts' to connect to 
Microsoft 365, it authenticates, works well for about 5 minutes and then 
disconnects.
  I have to remove that account and redo it every time I want to use it.

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: ubuntu-settings 24.04.3
  ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1
  Uname: Linux 6.8.0-31-generic x86_64
  ApportVersion: 2.28.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr 27 19:04:06 2024
  InstallationDate: Installed on 2024-04-27 (0 days ago)
  InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424)
  PackageArchitecture: all
  SourcePackage: ubuntu-settings
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/2063961/+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 1944746] Re: LibreOffice from Ubuntu Store/snaps broken GNOME integration for remote smb shares

[James Paton-Smith]

This issue is still present with the current latest Libreoffice Snap
version (24.2.2.2) both in Ubuntu 22.04 LTS and in the 24.04 Beta.

SMB shares and other GVFS mounted network locations are not visible in
the Open/Save file window.

If I try to manually navigate to the files under `/run/user//gvfs/`
I'm getting a 'Permission denied' error.

If I open the file directly from Nautilus using right-click 'Open With',
instead I get the attached error.

** Attachment added: "Screenshot from 2024-04-22 15-34-32.png"
   
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1944746/+attachment/5769396/+files/Screenshot%20from%202024-04-22%2015-34-32.png

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

Title:
  LibreOffice from Ubuntu Store/snaps broken GNOME integration for
  remote smb shares

Status in libreoffice package in Ubuntu:
  Triaged

Bug description:
  1)
  lsb_release -rd
  Description:  Ubuntu 21.04
  Release:  21.04

  2)
  Name Version RevTracking  
   Publisher   Notes
  snap list | grep libreoffice
  libreoffice  7.2.1.2 235
latest/edge  canonical*  -

  apt-cache policy gnome-shell
  gnome-shell:
Installed: 3.38.4-1ubuntu3~21.04.1
Candidate: 3.38.4-1ubuntu3~21.04.1
Version table:
   *** 3.38.4-1ubuntu3~21.04.1 500
  500 http://us.archive.ubuntu.com/ubuntu hirsute-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   3.38.4-1ubuntu2 500
  500 http://us.archive.ubuntu.com/ubuntu hirsute/main amd64 Packages

  3) What I expected to happen is using any version of LibreOffice snaps from 
Ubuntu Software app (i.e. https://snapcraft.io/libreoffice ) works as it does 
as if I used the default install of libreoffice. Specifically, when I open the 
GNOME Files program via the icon on the bar on the left, I have an smb share 
already added via "Other Locations". When I use the default libreoffice install 
version as per below, when I attempt to open a file in Libreoffice Calc, the 
share is visible and I'm able to open files, edit, save, close, etc.:
  apt-cache policy libreoffice
  libreoffice:
Installed: (none)
Candidate: 1:7.1.6-0ubuntu0.21.04.1
Version table:
   1:7.1.6-0ubuntu0.21.04.1 500 (phased 70%)
  500 http://us.archive.ubuntu.com/ubuntu hirsute-updates/universe 
amd64 Packages
   1:7.1.2~rc2-0ubuntu2 500
  500 http://us.archive.ubuntu.com/ubuntu hirsute/universe amd64 
Packages

  4) However, when I completely remove all things libreoffice-* via
  command line, then install the snap version, the smb share is not
  visible.

  It's confirmed all packages associated with default install are
  removed, and only the snap is installed. I've tried completely
  removing each snap and trying a different version (e.g. stable,
  candidate, edge) but it's the same problem.

  I'm guessing it's something borked with the libreoffice-gnome
  integration between the snap and the GNOME environment but that's a
  wild guess.

  I tried the snap package as the default install Draw kept crashing
  opening a particular file, and was hoping to work around it by
  installing later snap version.

  WORKAROUND: Use default install of LibreOffice.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  ProcVersionSignature: Ubuntu 5.11.0-36.40-generic 5.11.22
  Uname: Linux 5.11.0-36-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu65.3
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Sep 23 08:58:30 2021
  InstallationDate: Installed on 2021-08-25 (28 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Snap: libreoffice 7.2.1.2 (latest/edge)
  SnapSource: ubuntu/+source/libreoffice
  UpgradeStatus: Upgraded to hirsute on 2021-09-20 (3 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1944746/+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 2061118] Re: Rendering issues in vmware with 3d on (GTK ngl backend)

[Oliver Smith]

My issue is compounded by the fact that Ubuntu registers no network
interfaces in Ubuntu on vmwareplayer in NAT mode and it sees a
connection but can't connect in bridged mode. As a result I can't apply
updates on install or upgrade my NVIDIA drivers which may help resolve
the issue. I will try again with the newer NVIDIA drivers in the next
daily.

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

Title:
  Rendering issues in vmware with 3d on (GTK ngl backend)

Status in GTK+:
  New
Status in Mesa:
  New
Status in gtk4 package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Triaged
Status in gtk4 source package in Noble:
  Invalid
Status in mesa source package in Noble:
  Triaged

Bug description:
  Build: Noble Daily Current from 12th April

  Host OS: Windows 11

  VM App: VMWare Workstation 17 Player

  Issue: During installation there is continuous black flickering
  artefacts throughout the flow. Installation completed successfully,
  got to GDM, logged in but desktop screen is black and then locks up
  the whole application, cannot shutdown or interact with Player and
  need to hard kill from task manager.

  The issue appears does not appear with Mantic with the exact same
  machine configuration and appears to be an issue with GPU, my host
  machine is running an NVIDIA 4070ti with the latest windows drivers.

  On reboot some elements of the desktop are visible but cannot be
  interacted with without further lockups.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gtk/+bug/2061118/+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 2061118] Re: Rendering issues in vmware with 3d on (GTK ngl backend)

[Oliver Smith]

@Timo, I have tried the latest daily with the new Mesa and there is no
change to behaviour it is still non-functional with 3D acceleration
enabled.

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

Title:
  Rendering issues in vmware with 3d on (GTK ngl backend)

Status in GTK+:
  New
Status in Mesa:
  New
Status in gtk4 package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Fix Released
Status in gtk4 source package in Noble:
  Invalid
Status in mesa source package in Noble:
  Fix Released

Bug description:
  Build: Noble Daily Current from 12th April

  Host OS: Windows 11

  VM App: VMWare Workstation 17 Player

  Issue: During installation there is continuous black flickering
  artefacts throughout the flow. Installation completed successfully,
  got to GDM, logged in but desktop screen is black and then locks up
  the whole application, cannot shutdown or interact with Player and
  need to hard kill from task manager.

  The issue appears does not appear with Mantic with the exact same
  machine configuration and appears to be an issue with GPU, my host
  machine is running an NVIDIA 4070ti with the latest windows drivers.

  On reboot some elements of the desktop are visible but cannot be
  interacted with without further lockups.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gtk/+bug/2061118/+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 2061118] Re: Noble black-screen freezes in VMWare Workstation Player on Windows

[Oliver Smith]

** Also affects: gnome-shell (Ubuntu)
   Importance: Undecided
   Status: 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/2061118

Title:
  Noble black-screen freezes in VMWare Workstation Player on Windows

Status in gnome-shell package in Ubuntu:
  New
Status in open-vm-tools package in Ubuntu:
  New

Bug description:
  Build: Noble Daily Current from 12th April

  Host OS: Windows 11

  VM App: VMWare Workstation 17 Player

  Issue: During installation there is continuous black flickering
  artefacts throughout the flow. Installation completed successfully,
  got to GDM, logged in but desktop screen is black and then locks up
  the whole application, cannot shutdown or interact with Player and
  need to hard kill from task manager.

  The issue appears does not appear with Mantic with the exact same
  machine configuration and appears to be an issue with GPU, my host
  machine is running an NVIDIA 4070ti with the latest windows drivers.

  On reboot some elements of the desktop are visible but cannot be
  interacted with without further lockups.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2061118/+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 1991545] Re: Domain groups not accepted as 'AdminIdentities'

[James Paton-Smith]

After revisiting this, I found the issue was on my side.

Our LDAP wasn't returning the members list for groups when queried so polkit 
wasn't able to authorise those users.
I fixed this in our sssd.conf using the 'ignore_group_members = false' option.

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

Title:
  Domain groups not accepted as  'AdminIdentities'

Status in policykit-1 package in Ubuntu:
  New

Bug description:
  Domain groups cannot be configured as 'AdminIdentities' under
  /etc/polkit-1/localauthority.conf.d

  EXAMPLE CONFIG

  # /etc/polkit-1/localauthority.conf.d/90-test.conf
  [Configuration]
  AdminIdentities=unix-group:sysapp

  
  With the above config, 'sysapp' is a group in LDAP. SSSD is configured on the 
machine to allow domain users to log in.
  Sudo rules have been configured for the 'sysapp' group and work correctly.

  However, any action that creates a polkit/GUI prompt for
  authentication does not allow users in the 'sysapp' group to
  authenticate. Instead, it only accepts auth from the root user.

  
  If I change the config to use a local group, instead of a domain group, 
everything works as expected.
  Similarly if I specify a domain USER instead of a domain group, everything 
works as expected.

  The problem seems to only be with domain/LDAP groups.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: policykit-1 0.105-33
  ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53
  Uname: Linux 5.15.0-48-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Mon Oct  3 15:20:36 2022
  InstallationDate: Installed on 2022-07-15 (80 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  SourcePackage: policykit-1
  UpgradeStatus: Upgraded to jammy on 2022-08-02 (61 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/policykit-1/+bug/1991545/+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 2058923] [NEW] Clicking 'App Details' from the Apps tab does not work

[James Paton-Smith]

Public bug reported:

This was tested on Ubuntu 24.04 with all current updates applied.

To reproduce the issue:
- Open gnome-control-centre
- Navigate to the 'Apps' section
- Click on any app
- Click the 'App Details' button

The system will open the snap-store front-page, but won't show the given
apps details. This seems to be the same for both .deb and Snap packages.

ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: gnome-control-center 1:46~beta-1ubuntu1
ProcVersionSignature: Ubuntu 6.5.0-26.26-generic 6.5.13
Uname: Linux 6.5.0-26-generic x86_64
ApportVersion: 2.28.0-0ubuntu1
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Mon Mar 25 11:05:37 2024
ProcEnviron:
 LANG=en_GB.UTF-8
 PATH=(custom, no user)
 SHELL=/usr/local/bin/bash
 TERM=xterm-256color
 XDG_RUNTIME_DIR=
RebootRequiredPkgs: Error: path contained symlinks.
SourcePackage: gnome-control-center
UpgradeStatus: No upgrade log present (probably fresh install)

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


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

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

Title:
  Clicking 'App Details' from the Apps tab does not work

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

Bug description:
  This was tested on Ubuntu 24.04 with all current updates applied.

  To reproduce the issue:
  - Open gnome-control-centre
  - Navigate to the 'Apps' section
  - Click on any app
  - Click the 'App Details' button

  The system will open the snap-store front-page, but won't show the
  given apps details. This seems to be the same for both .deb and Snap
  packages.

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: gnome-control-center 1:46~beta-1ubuntu1
  ProcVersionSignature: Ubuntu 6.5.0-26.26-generic 6.5.13
  Uname: Linux 6.5.0-26-generic x86_64
  ApportVersion: 2.28.0-0ubuntu1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Mar 25 11:05:37 2024
  ProcEnviron:
   LANG=en_GB.UTF-8
   PATH=(custom, no user)
   SHELL=/usr/local/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2058923/+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 2058733] [NEW] polkitd does not create default config files on noble

[James Paton-Smith]

Public bug reported:

With a fresh install of the daily Ubuntu 24.04, polkitd does not create
the default config files under /etc/polkit-1/localauthority.conf.d/

This folder should contain some default config files which specify which
users can perform GUI admin authorization.

In fact, even if I create a config file under that directory, the
settings are not respected at all

ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: polkitd 124-1
ProcVersionSignature: Ubuntu 6.5.0-25.25-generic 6.5.13
Uname: Linux 6.5.0-25-generic x86_64
ApportVersion: 2.28.0-0ubuntu1
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Fri Mar 22 11:17:16 2024
ProcEnviron:
 LANG=en_GB.UTF-8
 PATH=(custom, no user)
 SHELL=/usr/local/bin/bash
 TERM=xterm-256color
 XDG_RUNTIME_DIR=
SourcePackage: policykit-1
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: policykit-1 (Ubuntu)
 Importance: Undecided
 Status: New


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

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

Title:
  polkitd does not create default config files on noble

Status in policykit-1 package in Ubuntu:
  New

Bug description:
  With a fresh install of the daily Ubuntu 24.04, polkitd does not
  create the default config files under
  /etc/polkit-1/localauthority.conf.d/

  This folder should contain some default config files which specify
  which users can perform GUI admin authorization.

  In fact, even if I create a config file under that directory, the
  settings are not respected at all

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: polkitd 124-1
  ProcVersionSignature: Ubuntu 6.5.0-25.25-generic 6.5.13
  Uname: Linux 6.5.0-25-generic x86_64
  ApportVersion: 2.28.0-0ubuntu1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar 22 11:17:16 2024
  ProcEnviron:
   LANG=en_GB.UTF-8
   PATH=(custom, no user)
   SHELL=/usr/local/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  SourcePackage: policykit-1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/policykit-1/+bug/2058733/+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 2052784] Re: Settings not responding

[James Paton-Smith]

Same issue for me. It looks like this only occurs on the first login
with a given user.

After logging-out and back in again, I can't reproduce the issue.

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

Title:
  Settings not responding

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

Bug description:
  Select Settings > System > Region - gnome-control-center
  hangs

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: gnome-control-center 1:46~alpha-2ubuntu2
  ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3
  Uname: Linux 6.6.0-14-generic x86_64
  ApportVersion: 2.27.0-0ubuntu6
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Feb  9 10:42:27 2024
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2052784/+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 2058720] [NEW] 'Other Software' section displays verbose ubuntu.sources comment

[James Paton-Smith]

Public bug reported:

With software-properties-gtk (0.99.44), the 'Other Software' section displays 
the full multi-line comment from the new ubuntu.sources file.
This creates an unpleasant looking entry in the list.

** Affects: software-properties (Ubuntu)
 Importance: Undecided
 Status: New

** Attachment added: "Screenshot from 2024-03-22 10-38-59.png"
   
https://bugs.launchpad.net/bugs/2058720/+attachment/5758293/+files/Screenshot%20from%202024-03-22%2010-38-59.png

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

Title:
  'Other Software' section displays verbose ubuntu.sources comment

Status in software-properties package in Ubuntu:
  New

Bug description:
  With software-properties-gtk (0.99.44), the 'Other Software' section displays 
the full multi-line comment from the new ubuntu.sources file.
  This creates an unpleasant looking entry in the list.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2058720/+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 2058715] [NEW] ubuntu.sources can become broken via GUI

[James Paton-Smith]

Public bug reported:

With the latest proposed versions of software-properties-gtk, software-
properties-common, and python3-software-properties (0.99.44), it is
possible to break the default ubuntu.sources list.

How to replicate
1. Open software-properties-gtk
2. Uncheck all of the repository suites (main, universe, multiverse, etc.)
3. Cat the /etc/apt/sources.list.d/ubuntu.sources file. It should be mostly 
empty.
4. Re-check all of the repository suites again.
5. Cat the /etc/apt/sources.list.d/ubuntu.sources file again. It will still be 
mostly empty with no repository configuration present.


The ubuntu.sources file remains in a broken state even though 
software-properties-gtk shows the suites as checked.

We can workaround this issue by using the 'Revert' button in software-
properties-gtk.

ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: software-properties-gtk 0.99.44
ProcVersionSignature: Ubuntu 6.5.0-26.26-generic 6.5.13
Uname: Linux 6.5.0-26-generic x86_64
ApportVersion: 2.28.0-0ubuntu1
Architecture: amd64
CasperMD5CheckMismatches: ./boot/grub/grub.cfg
CasperMD5CheckResult: fail
CurrentDesktop: ubuntu:GNOME
Date: Fri Mar 22 09:05:37 2024
InstallationDate: Installed on 2024-03-13 (9 days ago)
InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240313)
PackageArchitecture: all
ProcEnviron:
 LANG=en_GB.UTF-8
 PATH=(custom, no user)
 SHELL=/bin/bash
 TERM=xterm-256color
 XDG_RUNTIME_DIR=
SourcePackage: software-properties
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: software-properties (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug noble package-from-proposed wayland-session

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

Title:
  ubuntu.sources can become broken via GUI

Status in software-properties package in Ubuntu:
  New

Bug description:
  With the latest proposed versions of software-properties-gtk,
  software-properties-common, and python3-software-properties (0.99.44),
  it is possible to break the default ubuntu.sources list.

  How to replicate
  1. Open software-properties-gtk
  2. Uncheck all of the repository suites (main, universe, multiverse, etc.)
  3. Cat the /etc/apt/sources.list.d/ubuntu.sources file. It should be mostly 
empty.
  4. Re-check all of the repository suites again.
  5. Cat the /etc/apt/sources.list.d/ubuntu.sources file again. It will still 
be mostly empty with no repository configuration present.

  
  The ubuntu.sources file remains in a broken state even though 
software-properties-gtk shows the suites as checked.

  We can workaround this issue by using the 'Revert' button in software-
  properties-gtk.

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: software-properties-gtk 0.99.44
  ProcVersionSignature: Ubuntu 6.5.0-26.26-generic 6.5.13
  Uname: Linux 6.5.0-26-generic x86_64
  ApportVersion: 2.28.0-0ubuntu1
  Architecture: amd64
  CasperMD5CheckMismatches: ./boot/grub/grub.cfg
  CasperMD5CheckResult: fail
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar 22 09:05:37 2024
  InstallationDate: Installed on 2024-03-13 (9 days ago)
  InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240313)
  PackageArchitecture: all
  ProcEnviron:
   LANG=en_GB.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  SourcePackage: software-properties
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2058715/+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 2056060] [NEW] Ubuntu instances on WSL aren't attached by the Pro App

[Oliver Smith]

Public bug reported:

Running Windows 11 with WSL from the store, Ubuntu 22.04 LTS from the
store and the Ubuntu Pro app from the store. All have been updated
today.

I have submitted my personal Pro token to the GUI app and restarted my
WSL instances, but the instance never attaches and pro status remains
unattached.

I have attached  the log file from my Windows machine.

** Affects: wsl-pro-service (Ubuntu)
 Importance: Undecided
 Status: New

** Attachment added: "Logs from ubuntu pro"
   https://bugs.launchpad.net/bugs/2056060/+attachment/5752521/+files/log

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

Title:
  Ubuntu instances on WSL aren't attached by the Pro App

Status in wsl-pro-service package in Ubuntu:
  New

Bug description:
  Running Windows 11 with WSL from the store, Ubuntu 22.04 LTS from the
  store and the Ubuntu Pro app from the store. All have been updated
  today.

  I have submitted my personal Pro token to the GUI app and restarted my
  WSL instances, but the instance never attaches and pro status remains
  unattached.

  I have attached  the log file from my Windows machine.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/wsl-pro-service/+bug/2056060/+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 2045743] [NEW] Ubuntu Pro attached machine displays ESM support until 31/12/99

[Oliver Smith]

Public bug reported:

The Software and Update app incorrectly shows ESM support continuing
until 31/12/99 when the machine is Pro attached. The date for basic
support displays correctly when Pro is not enabled.

Worth noting that this page does not refresh when a Pro token is
detached and needs a relaunch to display the correct support status.

** Affects: software-properties (Ubuntu)
 Importance: Undecided
 Status: New

** Attachment added: "Screenshot from 2023-12-06 08-48-52.png"
   
https://bugs.launchpad.net/bugs/2045743/+attachment/5726651/+files/Screenshot%20from%202023-12-06%2008-48-52.png

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

Title:
  Ubuntu Pro attached machine displays ESM support until 31/12/99

Status in software-properties package in Ubuntu:
  New

Bug description:
  The Software and Update app incorrectly shows ESM support continuing
  until 31/12/99 when the machine is Pro attached. The date for basic
  support displays correctly when Pro is not enabled.

  Worth noting that this page does not refresh when a Pro token is
  detached and needs a relaunch to display the correct support status.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2045743/+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 2037967] [NEW] Official wallpapers should be chooseable outside of dark/light mode

[Oliver Smith]

Public bug reported:

Currently if you choose dark mode on 23.10 you can only use the
monochrome version of the official wallpaper.

Most users will expect to be able to combine the coloured wallpaper with
dark mode and this restriction of choice is not ideal. It would be good
to leave that option as-is but also include independently select-able
coloured and monocrhome wallpapers so users can have parity with
previous releases in terms of customisation.

ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: ubuntu-wallpapers 23.10.3
ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0
Uname: Linux 6.5.0-5-generic x86_64
ApportVersion: 2.27.0-0ubuntu3
Architecture: amd64
CasperMD5CheckResult: pass
CloudArchitecture: x86_64
CloudID: none
CloudName: none
CloudPlatform: none
CloudSubPlatform: config
CurrentDesktop: ubuntu:GNOME
Date: Thu Oct 12 23:46:19 2023
Dependencies: ubuntu-wallpapers-mantic 23.10.3
InstallationDate: Installed on 2023-10-02 (11 days ago)
InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20231001)
PackageArchitecture: all
ProcEnviron:
 LANG=en_US.UTF-8
 PATH=(custom, no user)
 SHELL=/bin/bash
 TERM=xterm-256color
 XDG_RUNTIME_DIR=
SourcePackage: ubuntu-wallpapers
UpgradeStatus: No upgrade log present (probably fresh install)

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


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

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

Title:
  Official wallpapers should be chooseable outside of dark/light mode

Status in ubuntu-wallpapers package in Ubuntu:
  New

Bug description:
  Currently if you choose dark mode on 23.10 you can only use the
  monochrome version of the official wallpaper.

  Most users will expect to be able to combine the coloured wallpaper
  with dark mode and this restriction of choice is not ideal. It would
  be good to leave that option as-is but also include independently
  select-able coloured and monocrhome wallpapers so users can have
  parity with previous releases in terms of customisation.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: ubuntu-wallpapers 23.10.3
  ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0
  Uname: Linux 6.5.0-5-generic x86_64
  ApportVersion: 2.27.0-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CloudArchitecture: x86_64
  CloudID: none
  CloudName: none
  CloudPlatform: none
  CloudSubPlatform: config
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 12 23:46:19 2023
  Dependencies: ubuntu-wallpapers-mantic 23.10.3
  InstallationDate: Installed on 2023-10-02 (11 days ago)
  InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20231001)
  PackageArchitecture: all
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  SourcePackage: ubuntu-wallpapers
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-wallpapers/+bug/2037967/+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 2036981] [NEW] References to 'Ubuntu Software' must be updated to reference 'App Center'

[Oliver Smith]

Public bug reported:

On Mantic Beta build, gnome initial setup incorrectly references 'ubuntu
software' when it should refer to the 'App Center'

We should also replace the snapcrafter icon with the icon of the App
Center as well

ProblemType: Bug

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


** Tags: amd64 apport-bug mantic

** Attachment added: "Screenshot of gnome initial setup"
   
https://bugs.launchpad.net/bugs/2036981/+attachment/5703231/+files/Screenshot%20from%202023-09-21%2014-49-58.png

** Description changed:

  On Mantic Beta build, gnome initial setup incorrectly references 'ubuntu
  software' when it should refer to the 'App Center'
  
  We should also replace the snapcrafter icon with the icon of the App
  Center as well
  
  ProblemType: Bug
- DistroRelease: Ubuntu 22.04
- Package: gnome-initial-setup 42.0.1-1ubuntu2.3
- ProcVersionSignature: Ubuntu 6.2.0-33.33~22.04.1-generic 6.2.16
- Uname: Linux 6.2.0-33-generic x86_64
- NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
- ApportVersion: 2.20.11-0ubuntu82.5
- Architecture: amd64
- CasperMD5CheckResult: unknown
- CurrentDesktop: ubuntu:GNOME
- Date: Thu Sep 21 15:08:01 2023
- InstallationDate: Installed on 2023-03-06 (198 days ago)
- InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 
(20230223)
- SourcePackage: gnome-initial-setup
- 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-initial-setup in Ubuntu.
https://bugs.launchpad.net/bugs/2036981

Title:
  References to 'Ubuntu Software' must be updated to reference 'App
  Center'

Status in gnome-initial-setup package in Ubuntu:
  New

Bug description:
  On Mantic Beta build, gnome initial setup incorrectly references
  'ubuntu software' when it should refer to the 'App Center'

  We should also replace the snapcrafter icon with the icon of the App
  Center as well

  ProblemType: Bug

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-initial-setup/+bug/2036981/+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 2011244] Re: emacs launching in GNOME is all messed up

[Gregory Smith]

As a workaround to the pinning issue, commenting out the StartupWMClass
line in /usr/share/applications/emacsclient.desktop allows pinning the
Emacs (GUI) desktop entry and doesn't add another icon. The two desktop
entries share the same StartupWMClass and I don't know how gnome shell
would be able to associate the windows to icons correctly in that
situation.

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

Title:
  emacs launching in GNOME is all messed up

Status in GNU Emacs:
  New
Status in emacs package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  With the most recent Lunar updates, which I believe include both an
  Emacs update and a GNOME update, I have encountered multiple annoying
  / bizarre problems with launching Emacs in GNOME. In particular:

  1) Sometimes Emacs launches as a tiny window rather than a window of the 
correct size.
  2) Sometimes it gets into a state where when I click on the icon in the dock 
instead of bringing the open Emacs window to the front it launches a new Emacs 
every time I click.
  3) Sometimes it fails to show up in the dock at all when I launch it.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: emacs 1:28.2+1-10ubuntu1
  ProcVersionSignature: Ubuntu 6.1.0-16.16-generic 6.1.6
  Uname: Linux 6.1.0-16-generic x86_64
  ApportVersion: 2.26.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar 10 16:13:14 2023
  InstallationDate: Installed on 2019-08-16 (1302 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  PackageArchitecture: all
  SourcePackage: emacs
  UpgradeStatus: Upgraded to lunar on 2022-11-24 (106 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/emacs/+bug/2011244/+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 1971434] Re: Display powersave only blanks, but does not turn off

[Dawn Smith]

I'm on 22.04 and can also confirm that the fix in #33 worked for me.
Thanks for the help Daniel!

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

Title:
  Display powersave only blanks, but does not turn off

Status in gnome-settings-daemon package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  Recently upgraded to Ubuntu 22.04, and it seems like the power-saving
  feature in Gnome 42 does not actually turn off the screen(s) after X
  minutes, but just blanks them. When I manually run `xset dpms force
  off`, they do properly turn off and go to powersave mode.

  1) Description:   Ubuntu 22.04 LTS
 Release:   22.04

  2) gnome-settings-daemon:
Installed: 42.1-1ubuntu2
Candidate: 42.1-1ubuntu2

  3) In Settings -> Power -> Screen Blank, set the inactivity period to
  5 minutes. After 5 minutes, the screens should turn off.

  4) Screens go black, but remain active and consume (too much) power.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-bionic-amd64-20190418-59+beaver-osp1+X00
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2020-07-04 (667 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20190418-12:10
  Package: gnome-settings-daemon 42.1-1ubuntu2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Tags:  jammy
  Uname: Linux 5.15.0-27-generic x86_64
  UpgradeStatus: Upgraded to jammy on 2022-04-30 (3 days ago)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo vboxusers 
video wireshark
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1971434/+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 2031096] Re: udisks2 daemon fails to start

[Paul Smith]

Same.  This is on a machine with several nvme and sata SSDs.  Oddly
enough, I upgraded my laptop (which has a single nvme SSD) and have had
no problems.

journalctl -xeu udisks2.service output:

Sep 01 03:03:59 case udisksd[6200]: udisks daemon version 2.10.0 starting
Sep 01 03:03:59 case udisksd[6200]: *** stack smashing detected ***: terminated
Sep 01 03:03:59 case systemd[1]: udisks2.service: Main process exited, 
code=killed, status=6/ABRT
Sep 01 03:03:59 case systemd[1]: udisks2.service: Failed with result 'signal'.
Sep 01 03:03:59 case systemd[1]: Failed to start udisks2.service - Disk Manager.
cvpsmith@case:~$ journalctl -xeu udisks2.service
Sep 01 03:03:59 case udisksd[6200]: *** stack smashing detected ***: terminated
Sep 01 03:03:59 case systemd[1]: udisks2.service: Main process exited, 
code=killed, status=6/ABRT
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░ 
░░ An ExecStart= process belonging to unit udisks2.service has exited.
░░ 
░░ The process' exit code is 'killed' and its exit status is 6.
Sep 01 03:03:59 case systemd[1]: udisks2.service: Failed with result 'signal'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░ 
░░ The unit udisks2.service has entered the 'failed' state with result 'signal'.
Sep 01 03:03:59 case systemd[1]: Failed to start udisks2.service - Disk Manager.
░░ Subject: A start job for unit udisks2.service has failed
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░ 
░░ A start job for unit udisks2.service has finished with a failure.
░░ 
░░ The job identifier is 3124 and the job result is failed.

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

Title:
  udisks2 daemon fails to start

Status in udisks:
  New
Status in udisks2 package in Ubuntu:
  Confirmed

Bug description:
  udisks2 2.10.0 fails to start in Ubuntu Mantic (23.10)

  Error status is:

  Aug 11 10:36:37 nodename systemd[1]: Starting udisks2.service - Disk 
Manager...
  Aug 11 10:36:37 nodename udisksd[232247]: udisks daemon version 2.10.0 
starting
  Aug 11 10:36:38 nodename udisksd[232247]: Error getting 'loop28' information: 
Failed to open device loop28: No such file o>
  Aug 11 10:36:38 nodename udisksd[232247]: Error getting 'loop28' information: 
Failed to open device loop28: No such file o>
  Aug 11 10:36:38 nodename udisksd[232247]: *** stack smashing detected ***: 
terminated
  Aug 11 10:36:38 nodename systemd[1]: udisks2.service: Main process exited, 
code=dumped, status=6/ABRT
  Aug 11 10:36:38 nodename systemd[1]: udisks2.service: Failed with result 
'core-dump'.
  Aug 11 10:36:38 nodename systemd[1]: Failed to start udisks2.service - Disk 
Manager.

  This bug seems to refer: https://github.com/storaged-
  project/udisks/issues/1139

To manage notifications about this bug go to:
https://bugs.launchpad.net/udisks/+bug/2031096/+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 2028610] [NEW] bring-to-front and send-to-back not working for some apps

[Paul Smith]

Public bug reported:

Since I upgraded to Ubuntu 23.04, a number of my applications have
stopped accepting bring-to-front (right click on the title bar) and
send-to-back (middle click on the title bar).  On the other hand, other
apps (native Gnome apps seemingly) do still seem to work.  Note I'm
using X11 not Wayland.

A set of apps I know do not work anymore, that used to work with Ubuntu 22.10 
and below:
* xterm
* Emacs
* Chrome
* Slack
* Spotify
* VirtualBox manager

Some apps that do still work:
* Remmina
* File Manager
* gnome-terminal
* Gnome Settings
* Ubuntu Software

There are many more in both categories.

Please fix things so that I can use bring-to-front and send-to-back on
all my apps again.  Thanks!

ProblemType: Bug
DistroRelease: Ubuntu 23.04
Package: mutter 44.2-0ubuntu1
ProcVersionSignature: Ubuntu 5.14.0-1054.61-oem 5.14.21
Uname: Linux 5.14.0-1054-oem x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.26.1-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Mon Jul 24 23:31:31 2023
DistributionChannelDescriptor:
 # This is the distribution channel descriptor for the OEM CDs
 # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor
 canonical-oem-somerville-focal-amd64-20200502-85
InstallationDate: Installed on 2022-12-02 (234 days ago)
InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58
SourcePackage: mutter
UpgradeStatus: Upgraded to lunar on 2023-06-04 (50 days ago)

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


** Tags: amd64 apport-bug lunar

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

Title:
  bring-to-front and send-to-back not working for some apps

Status in mutter package in Ubuntu:
  New

Bug description:
  Since I upgraded to Ubuntu 23.04, a number of my applications have
  stopped accepting bring-to-front (right click on the title bar) and
  send-to-back (middle click on the title bar).  On the other hand,
  other apps (native Gnome apps seemingly) do still seem to work.  Note
  I'm using X11 not Wayland.

  A set of apps I know do not work anymore, that used to work with Ubuntu 22.10 
and below:
  * xterm
  * Emacs
  * Chrome
  * Slack
  * Spotify
  * VirtualBox manager

  Some apps that do still work:
  * Remmina
  * File Manager
  * gnome-terminal
  * Gnome Settings
  * Ubuntu Software

  There are many more in both categories.

  Please fix things so that I can use bring-to-front and send-to-back on
  all my apps again.  Thanks!

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: mutter 44.2-0ubuntu1
  ProcVersionSignature: Ubuntu 5.14.0-1054.61-oem 5.14.21
  Uname: Linux 5.14.0-1054-oem x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jul 24 23:31:31 2023
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-focal-amd64-20200502-85
  InstallationDate: Installed on 2022-12-02 (234 days ago)
  InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 
20200502-05:58
  SourcePackage: mutter
  UpgradeStatus: Upgraded to lunar on 2023-06-04 (50 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2028610/+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 1983112] Re: Appstream does not install config file

[James Paton-Smith]

Had some time to test this more.

I'm almost certain this is caused by the server autoinstall method.

After doing another manual server install (interactive), and installing
ubuntu-desktop-minimal, I just need to do a `snap refresh snapd` to fix
the issue with the software store. /etc/apt/apt.conf.d/50appstream is
present without any extra steps.

If I do an autoinstall, and list appstream as the only package to install, 
/etc/apt/apt.conf.d/50appstream is missing.
The command run by the installer is below:
```
/usr/bin/apt-get --quiet --assume-yes 
--option=Dpkg::options::=--force-unsafe-io 
--option=Dpkg::Options::=--force-confold install appstream
```

But if I run this manually on a clean system,
/etc/apt/apt.conf.d/50appstream is present. So the issue must be
something else related to the autoinstall.

I can only replicate this issue if using the Ubuntu Autoinstall method.

Should I open a separate issue for this? I've already added subiquity
package to the affected packages list.

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

Title:
  Appstream does not install config file

Status in appstream package in Ubuntu:
  New
Status in subiquity package in Ubuntu:
  New

Bug description:
  After performing an Ubuntu automated server install, and installing
  the ubuntu-desktop-minimal package (which includes appstream as a
  dependency) then the snap-store, the snap-store will fail to display
  search results for .deb packages in the Ubuntu apt repositories.

  This is due to a missing config file (/etc/apt/apt.conf.d/50appstream)
  which is supposed to be installed as part of the appstream package.

  The issue can be fixed by re-installing appstream with the following 
command-line:
  apt-get -y install --reinstall -o Dpkg::Options::="--force-confmiss" appstream

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: appstream 0.15.2-2
  ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39
  Uname: Linux 5.15.0-41-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckMismatches: ./boot/grub/grub.cfg
  CasperMD5CheckResult: fail
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jul 29 15:25:44 2022
  InstallationDate: Installed on 2022-07-27 (1 days ago)
  InstallationMedia: Ubuntu-Server 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220421)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: appstream
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/appstream/+bug/1983112/+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 1983112] Re: Appstream does not install config file

[James Paton-Smith]

** 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 appstream in Ubuntu.
https://bugs.launchpad.net/bugs/1983112

Title:
  Appstream does not install config file

Status in appstream package in Ubuntu:
  New
Status in subiquity package in Ubuntu:
  New

Bug description:
  After performing an Ubuntu automated server install, and installing
  the ubuntu-desktop-minimal package (which includes appstream as a
  dependency) then the snap-store, the snap-store will fail to display
  search results for .deb packages in the Ubuntu apt repositories.

  This is due to a missing config file (/etc/apt/apt.conf.d/50appstream)
  which is supposed to be installed as part of the appstream package.

  The issue can be fixed by re-installing appstream with the following 
command-line:
  apt-get -y install --reinstall -o Dpkg::Options::="--force-confmiss" appstream

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: appstream 0.15.2-2
  ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39
  Uname: Linux 5.15.0-41-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckMismatches: ./boot/grub/grub.cfg
  CasperMD5CheckResult: fail
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jul 29 15:25:44 2022
  InstallationDate: Installed on 2022-07-27 (1 days ago)
  InstallationMedia: Ubuntu-Server 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220421)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: appstream
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/appstream/+bug/1983112/+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 2019498] Re: Unable to connect to Google in GCC

[Mark Smith]

Here is the output:

$ journalctl -f
May 19 21:05:13 nitro gnome-control-c[5879]: Error showing account: Child 
process exited with code 1
May 19 21:06:07 nitro org.gnome.Settings.desktop[5921]: 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: Dialogue was 
dismissed
May 19 21:06:07 nitro xdg-desktop-por[2266]: Realtime error: Could not map pid: 
Could not determine pid namespace: Could not find instance-id in process's 
/.flatpak-info
May 19 21:06:19 nitro kernel: WebKitWebProces[6157]: segfault at 5564481e0ac8 
ip 5564481e0ac8 sp 7ffc22016728 error 14 likely on CPU 2 (core 1, 
socket 0)
May 19 21:06:19 nitro kernel: Code: Unable to access opcode bytes at 
0x5564481e0a9e.
May 19 21:07:39 nitro systemd[1]: Starting systemd-tmpfiles-clean.service - 
Cleanup of Temporary Directories...
May 19 21:07:39 nitro systemd[1]: systemd-tmpfiles-clean.service: Deactivated 
successfully.
May 19 21:07:39 nitro systemd[1]: Finished systemd-tmpfiles-clean.service - 
Cleanup of Temporary Directories.
May 19 21:07:39 nitro systemd[1]: 
run-credentials-systemd\x2dtmpfiles\x2dclean.service.mount: Deactivated 
successfully.
May 19 21:07:41 nitro gnome-control-c[5879]: Error showing account: Child 
process exited with code 1
May 19 21:07:49 nitro org.gnome.Settings.desktop[6127]: 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: Dialogue was 
dismissed
May 19 21:07:50 nitro xdg-desktop-por[2266]: Realtime error: Could not map pid: 
Could not determine pid namespace: Could not find instance-id in process's 
/.flatpak-info
May 19 21:08:01 nitro kernel: WebKitWebProces[6296]: segfault at 55ce66a0a8da 
ip 55ce66a0a8da sp 7ffce52facf8 error 14 likely on CPU 0 (core 0, 
socket 0)
May 19 21:08:01 nitro kernel: Code: Unable to access opcode bytes at 
0x55ce66a0a8b0.

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

Title:
  Unable to connect to Google in GCC

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

Bug description:
  At installation of Ubuntu 23.04, and subsequently, when trying to use
  Gnome Control Center to connect my Google account in Online Accounts,
  I am able to enter my email address, but then the screen freezes in
  the transition to the screen where I'd enter my password.

  This happens every time.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: gnome-control-center 1:44.0-1ubuntu5
  ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
  Uname: Linux 6.2.0-20-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sun May 14 12:44:51 2023
  InstallationDate: Installed on 2023-05-14 (0 days ago)
  InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230417)
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2019498/+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 2019498] Re: Unable to connect to Google in GCC

[Mark Smith]

Hi,

I'm away with work for the rest of this week, so I'll do this on Saturday
for you.

On Tue, 16 May 2023 at 10:59, Sebastien Bacher <2019...@bugs.launchpad.net>
wrote:

> Thank you for your bug report. Could you do
> $ journalctl -f
> then trigger the bug and see if any error is printed in the journal log?
>
> ** Changed in: gnome-control-center (Ubuntu)
>Status: New => Incomplete
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/2019498
>
> Title:
>   Unable to connect to Google in GCC
>
> Status in gnome-control-center package in Ubuntu:
>   Incomplete
>
> Bug description:
>   At installation of Ubuntu 23.04, and subsequently, when trying to use
>   Gnome Control Center to connect my Google account in Online Accounts,
>   I am able to enter my email address, but then the screen freezes in
>   the transition to the screen where I'd enter my password.
>
>   This happens every time.
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 23.04
>   Package: gnome-control-center 1:44.0-1ubuntu5
>   ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
>   Uname: Linux 6.2.0-20-generic x86_64
>   NonfreeKernelModules: nvidia_modeset nvidia
>   ApportVersion: 2.26.1-0ubuntu2
>   Architecture: amd64
>   CasperMD5CheckResult: pass
>   CurrentDesktop: ubuntu:GNOME
>   Date: Sun May 14 12:44:51 2023
>   InstallationDate: Installed on 2023-05-14 (0 days ago)
>   InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64
> (20230417)
>   SourcePackage: gnome-control-center
>   UpgradeStatus: No upgrade log present (probably fresh install)
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2019498/+subscriptions
>
> Launchpad-Notification-Type: bug
> Launchpad-Bug: distribution=ubuntu; sourcepackage=gnome-control-center;
> component=main; status=Incomplete; importance=Undecided; assignee=None;
> Launchpad-Bug-Tags: amd64 apport-bug lunar
> Launchpad-Bug-Information-Type: Public
> Launchpad-Bug-Private: no
> Launchpad-Bug-Security-Vulnerability: no
> Launchpad-Bug-Commenters: juglugs1974 seb128
> Launchpad-Bug-Reporter: Mark Smith (juglugs1974)
> Launchpad-Bug-Modifier: Sebastien Bacher (seb128)
> Launchpad-Message-Rationale: Subscriber
> Launchpad-Message-For: juglugs1974
>
>

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

Title:
  Unable to connect to Google in GCC

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

Bug description:
  At installation of Ubuntu 23.04, and subsequently, when trying to use
  Gnome Control Center to connect my Google account in Online Accounts,
  I am able to enter my email address, but then the screen freezes in
  the transition to the screen where I'd enter my password.

  This happens every time.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: gnome-control-center 1:44.0-1ubuntu5
  ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
  Uname: Linux 6.2.0-20-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sun May 14 12:44:51 2023
  InstallationDate: Installed on 2023-05-14 (0 days ago)
  InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230417)
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2019498/+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 2019498] [NEW] Unable to connect to Google in GCC

[Mark Smith]

Public bug reported:

At installation of Ubuntu 23.04, and subsequently, when trying to use
Gnome Control Center to connect my Google account in Online Accounts, I
am able to enter my email address, but then the screen freezes in the
transition to the screen where I'd enter my password.

This happens every time.

ProblemType: Bug
DistroRelease: Ubuntu 23.04
Package: gnome-control-center 1:44.0-1ubuntu5
ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
Uname: Linux 6.2.0-20-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.26.1-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Sun May 14 12:44:51 2023
InstallationDate: Installed on 2023-05-14 (0 days ago)
InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230417)
SourcePackage: gnome-control-center
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug lunar

** Attachment added: "Screenshot of frozen online accounts screen"
   
https://bugs.launchpad.net/bugs/2019498/+attachment/5672961/+files/20230514OnlineAccountsBug.jpg

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

Title:
  Unable to connect to Google in GCC

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

Bug description:
  At installation of Ubuntu 23.04, and subsequently, when trying to use
  Gnome Control Center to connect my Google account in Online Accounts,
  I am able to enter my email address, but then the screen freezes in
  the transition to the screen where I'd enter my password.

  This happens every time.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: gnome-control-center 1:44.0-1ubuntu5
  ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
  Uname: Linux 6.2.0-20-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sun May 14 12:44:51 2023
  InstallationDate: Installed on 2023-05-14 (0 days ago)
  InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230417)
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2019498/+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 2018343] [NEW] Single screen of multi-monitor setup went blank

[Dayton Smith]

Public bug reported:

Single screen of multi-monitor setup went blank

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: gnome-shell 42.0-2ubuntu1
ProcVersionSignature: Ubuntu 5.19.0-41.42~22.04.1-generic 5.19.17
Uname: Linux 5.19.0-41-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.4
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Tue May  2 17:10:03 2023
DisplayManager: gdm3
InstallationDate: Installed on 2022-12-04 (149 days ago)
InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
RelatedPackageVersions: mutter-common 42.5-0ubuntu1
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug jammy third-party-packages 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/2018343

Title:
  Single screen of multi-monitor setup went blank

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Single screen of multi-monitor setup went blank

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 42.0-2ubuntu1
  ProcVersionSignature: Ubuntu 5.19.0-41.42~22.04.1-generic 5.19.17
  Uname: Linux 5.19.0-41-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.4
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue May  2 17:10:03 2023
  DisplayManager: gdm3
  InstallationDate: Installed on 2022-12-04 (149 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 42.5-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/2018343/+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 2017794] [NEW] selecting text problem when app runs full screen

[John Smith]

Public bug reported:

When Text editor runs full screen, it is not possible to select (with the 
mouse) the portion of text which is in the bottom of the screen. When app 
doesn't run full screen, the behavior goes back to normal : selecting text 
while moving pointer in the bottom of the window makes text move up, so that 
the text selection extends.
Precision : Ubuntu 23.04, Gnome 44, some Gnome extensions installed but not the 
one that creates a taskbar at the bottom of the screen ; interface configured 
with nothing at the bottom of the screen

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


** Tags: gnome-text-editor selection text

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

Title:
  selecting text problem when app runs full screen

Status in gnome-text-editor package in Ubuntu:
  New

Bug description:
  When Text editor runs full screen, it is not possible to select (with the 
mouse) the portion of text which is in the bottom of the screen. When app 
doesn't run full screen, the behavior goes back to normal : selecting text 
while moving pointer in the bottom of the window makes text move up, so that 
the text selection extends.
  Precision : Ubuntu 23.04, Gnome 44, some Gnome extensions installed but not 
the one that creates a taskbar at the bottom of the screen ; interface 
configured with nothing at the bottom of the screen

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-text-editor/+bug/2017794/+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 2013188] [NEW] Font issues on desktop decrypt in plymouth

[Oliver Smith]

Public bug reported:

New Ubuntu font doesn't render on Plymouth when asking for cryptenroll
password.

See screenshot

Build:  Ubuntu-daily 28th March

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

** Attachment added: "plymouth-decrypt"
   
https://bugs.launchpad.net/bugs/2013188/+attachment/5658601/+files/plymouth-decrypt

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

Title:
  Font issues on desktop decrypt in plymouth

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

Bug description:
  New Ubuntu font doesn't render on Plymouth when asking for cryptenroll
  password.

  See screenshot

  Build:  Ubuntu-daily 28th March

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/2013188/+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 2011829] Re: Dock glitches when switching between light and dark mode

[Oliver Smith]

During install this bug happens every time I toggle light-dark in the
installer option.

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

Title:
  Dock glitches when switching between light and dark mode

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

Bug description:
  When switching between like and dark modes, the dock icons glitch
  their positioning every 4th or so time dark/light is switched. See the
  video attached for repeated toggles - 75% behaves as expected, 25% the
  glitch appears. This does not happen in current releases of Ubuntu
  Desktop.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/2011829/+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 2011313] Re: gnome-control-center crashes after launch

[Mark Smith]

I can confirm that this issue is now resolved

On Thu, 16 Mar 2023 at 12:15, Mark Smith <2011...@bugs.launchpad.net>
wrote:

> Awesome! Thank you for your help on this.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/2011313
>
> Title:
>   gnome-control-center crashes after launch
>
> Status in gnome-control-center package in Ubuntu:
>   Fix Released
>
> Bug description:
>   I had successfully opened settings and used it to change some of the
> desktop options (size of the docker icons, etc.).
>   Then I clicked on "Users" and ubuntu-settings crashed.
>   Since then, I am unable to open ubuntu-settings - it will open and flash
> up on the screen before crashing.
>   This has continued even after restarting the machine a few times.
>
>   ubuntu-settings version: 23.04.2 500
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 23.04
>   Package: ubuntu-settings 23.04.2
>   ProcVersionSignature: Ubuntu 6.1.0-16.16-generic 6.1.6
>   Uname: Linux 6.1.0-16-generic x86_64
>   NonfreeKernelModules: nvidia_modeset nvidia
>   ApportVersion: 2.26.0-0ubuntu2
>   Architecture: amd64
>   CasperMD5CheckResult: pass
>   CurrentDesktop: ubuntu:GNOME
>   Date: Sat Mar 11 18:33:16 2023
>   InstallationDate: Installed on 2023-03-11 (0 days ago)
>   InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20230310)
>   PackageArchitecture: all
>   ProcEnviron:
>LANG=en_US.UTF-8
>PATH=(custom, no user)
>SHELL=/bin/bash
>TERM=xterm-256color
>XDG_RUNTIME_DIR=
>   SourcePackage: ubuntu-settings
>   UpgradeStatus: No upgrade log present (probably fresh install)
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2011313/+subscriptions
>
> Launchpad-Notification-Type: bug
> Launchpad-Bug: distribution=ubuntu; sourcepackage=gnome-control-center;
> component=main; status=Fix Released; importance=High; assignee=
> jeremy.bi...@canonical.com;
> Launchpad-Bug-Tags: amd64 apport-bug lunar
> Launchpad-Bug-Information-Type: Public
> Launchpad-Bug-Private: no
> Launchpad-Bug-Security-Vulnerability: no
> Launchpad-Bug-Commenters: fthx gunnarhj juglugs1974 starkus
> Launchpad-Bug-Reporter: Mark Smith (juglugs1974)
> Launchpad-Bug-Modifier: Mark Smith (juglugs1974)
> Launchpad-Message-Rationale: Subscriber
> Launchpad-Message-For: juglugs1974
>
>

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

Title:
  gnome-control-center crashes after launch

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

Bug description:
  I had successfully opened settings and used it to change some of the desktop 
options (size of the docker icons, etc.).
  Then I clicked on "Users" and ubuntu-settings crashed.
  Since then, I am unable to open ubuntu-settings - it will open and flash up 
on the screen before crashing.
  This has continued even after restarting the machine a few times.

  ubuntu-settings version: 23.04.2 500

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: ubuntu-settings 23.04.2
  ProcVersionSignature: Ubuntu 6.1.0-16.16-generic 6.1.6
  Uname: Linux 6.1.0-16-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.26.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Mar 11 18:33:16 2023
  InstallationDate: Installed on 2023-03-11 (0 days ago)
  InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20230310)
  PackageArchitecture: all
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  SourcePackage: ubuntu-settings
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2011313/+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 2011829] [NEW] Dock glitches when switching between light and dark mode

[Oliver Smith]

Public bug reported:

When switching between like and dark modes, the dock icons glitch their
positioning every 4th or so time dark/light is switched. See the video
attached for repeated toggles - 75% behaves as expected, 25% the glitch
appears. This does not happen in current releases of Ubuntu Desktop.

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

** Attachment added: "Screencast from 16-03-23 13:31:37.webm"
   
https://bugs.launchpad.net/bugs/2011829/+attachment/5654876/+files/Screencast%20from%2016-03-23%2013%3A31%3A37.webm

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

Title:
  Dock glitches when switching between light and dark mode

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

Bug description:
  When switching between like and dark modes, the dock icons glitch
  their positioning every 4th or so time dark/light is switched. See the
  video attached for repeated toggles - 75% behaves as expected, 25% the
  glitch appears. This does not happen in current releases of Ubuntu
  Desktop.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/2011829/+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 2011827] [NEW] gnome-initial-setup doesn't respect dark mode selection in 23.04

[Oliver Smith]

Public bug reported:

In the 16th March Pending Desktop image
https://cdimage.ubuntu.com/daily-live/pending/

Switching between Dark and Light modes while gnome initial setup is open
does not change the appearance of GIS. See the attached video.

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

** Attachment added: "Screencast from 16-03-23 13:31:37.webm"
   
https://bugs.launchpad.net/bugs/2011827/+attachment/5654875/+files/Screencast%20from%2016-03-23%2013%3A31%3A37.webm

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

Title:
  gnome-initial-setup doesn't respect dark mode selection in 23.04

Status in gnome-initial-setup package in Ubuntu:
  New

Bug description:
  In the 16th March Pending Desktop image
  https://cdimage.ubuntu.com/daily-live/pending/

  Switching between Dark and Light modes while gnome initial setup is
  open does not change the appearance of GIS. See the attached video.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-initial-setup/+bug/2011827/+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 2011313] Re: gnome-control-center crashes after launch

[Mark Smith]

Awesome! Thank you for your help on this.

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

Title:
  gnome-control-center crashes after launch

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

Bug description:
  I had successfully opened settings and used it to change some of the desktop 
options (size of the docker icons, etc.).
  Then I clicked on "Users" and ubuntu-settings crashed.
  Since then, I am unable to open ubuntu-settings - it will open and flash up 
on the screen before crashing.
  This has continued even after restarting the machine a few times.

  ubuntu-settings version: 23.04.2 500

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: ubuntu-settings 23.04.2
  ProcVersionSignature: Ubuntu 6.1.0-16.16-generic 6.1.6
  Uname: Linux 6.1.0-16-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.26.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Mar 11 18:33:16 2023
  InstallationDate: Installed on 2023-03-11 (0 days ago)
  InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20230310)
  PackageArchitecture: all
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  SourcePackage: ubuntu-settings
  UpgradeStatus: No upgrade log present (probably fresh install)

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

[Mark Smith]

Ahaha so ubuntu-settings was rolled out into Lunar overnight NOT 
gnome-control-settings.
I had forgotten that I had originally tagged the wrong app - in fact, I'm not 
going to have to go and look up the difference between them :)

So - false alarm - It's not ready yet :)

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

Title:
  gnome-control-center crashes after launch

Status in gnome-control-center package in Ubuntu:
  In Progress

Bug description:
  I had successfully opened settings and used it to change some of the desktop 
options (size of the docker icons, etc.).
  Then I clicked on "Users" and ubuntu-settings crashed.
  Since then, I am unable to open ubuntu-settings - it will open and flash up 
on the screen before crashing.
  This has continued even after restarting the machine a few times.

  ubuntu-settings version: 23.04.2 500

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: ubuntu-settings 23.04.2
  ProcVersionSignature: Ubuntu 6.1.0-16.16-generic 6.1.6
  Uname: Linux 6.1.0-16-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.26.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Mar 11 18:33:16 2023
  InstallationDate: Installed on 2023-03-11 (0 days ago)
  InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20230310)
  PackageArchitecture: all
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  SourcePackage: ubuntu-settings
  UpgradeStatus: No upgrade log present (probably fresh install)

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

[Mark Smith]

Yeah, I think that it's not worth fixing in the alpha version.
Do you know when 1:44~rc will be merged?

Thank you for your help with this bug! It is much appreciated :)

On Sun, 12 Mar 2023 at 22:00, Gunnar Hjalmarsson <2011...@bugs.launchpad.net>
wrote:

> Yeah.. That "Couldn't get locale for language: (null)" warning comes
> from a patch which I wrote initially, and first I feared that the
> segfault is related to that. But it's not. I committed a fix which will
> get rid of the warning in this situation:
>
> https://salsa.debian.org/gnome-team/gnome-control-
> center/-/commit/53e9a9a2
>
> But it still segfaults. For some reason it fails to fetch the user data
> properly.
>
> My thought is that since the problem seems to be gone in g-c-c 1:44~rc,
> it's not worth it to figure out why exactly the alpha version crashes.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/2011313
>
> Title:
>   gnome-control-center crashes after launch
>
> Status in gnome-control-center package in Ubuntu:
>   In Progress
>
> Bug description:
>   I had successfully opened settings and used it to change some of the
> desktop options (size of the docker icons, etc.).
>   Then I clicked on "Users" and ubuntu-settings crashed.
>   Since then, I am unable to open ubuntu-settings - it will open and flash
> up on the screen before crashing.
>   This has continued even after restarting the machine a few times.
>
>   ubuntu-settings version: 23.04.2 500
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 23.04
>   Package: ubuntu-settings 23.04.2
>   ProcVersionSignature: Ubuntu 6.1.0-16.16-generic 6.1.6
>   Uname: Linux 6.1.0-16-generic x86_64
>   NonfreeKernelModules: nvidia_modeset nvidia
>   ApportVersion: 2.26.0-0ubuntu2
>   Architecture: amd64
>   CasperMD5CheckResult: pass
>   CurrentDesktop: ubuntu:GNOME
>   Date: Sat Mar 11 18:33:16 2023
>   InstallationDate: Installed on 2023-03-11 (0 days ago)
>   InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20230310)
>   PackageArchitecture: all
>   ProcEnviron:
>LANG=en_US.UTF-8
>PATH=(custom, no user)
>SHELL=/bin/bash
>TERM=xterm-256color
>XDG_RUNTIME_DIR=
>   SourcePackage: ubuntu-settings
>   UpgradeStatus: No upgrade log present (probably fresh install)
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2011313/+subscriptions
>
> Launchpad-Notification-Type: bug
> Launchpad-Bug: distribution=ubuntu; sourcepackage=gnome-control-center;
> component=main; status=In Progress; importance=High; assignee=
> jeremy.bi...@canonical.com;
> Launchpad-Bug-Tags: amd64 apport-bug lunar
> Launchpad-Bug-Information-Type: Public
> Launchpad-Bug-Private: no
> Launchpad-Bug-Security-Vulnerability: no
> Launchpad-Bug-Commenters: gunnarhj juglugs1974 starkus
> Launchpad-Bug-Reporter: Mark Smith (juglugs1974)
> Launchpad-Bug-Modifier: Gunnar Hjalmarsson (gunnarhj)
> Launchpad-Message-Rationale: Subscriber
> Launchpad-Message-For: juglugs1974
>
>

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

Title:
  gnome-control-center crashes after launch

Status in gnome-control-center package in Ubuntu:
  In Progress

Bug description:
  I had successfully opened settings and used it to change some of the desktop 
options (size of the docker icons, etc.).
  Then I clicked on "Users" and ubuntu-settings crashed.
  Since then, I am unable to open ubuntu-settings - it will open and flash up 
on the screen before crashing.
  This has continued even after restarting the machine a few times.

  ubuntu-settings version: 23.04.2 500

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: ubuntu-settings 23.04.2
  ProcVersionSignature: Ubuntu 6.1.0-16.16-generic 6.1.6
  Uname: Linux 6.1.0-16-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.26.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Mar 11 18:33:16 2023
  InstallationDate: Installed on 2023-03-11 (0 days ago)
  InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20230310)
  PackageArchitecture: all
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  SourcePackage: ubuntu-settings
  UpgradeStatus: No upgrade log present (probably fresh install)

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

[Mark Smith]

That command:

gsettings reset org.gnome.ControlCenter last-panel

Doesn't work for me - I get:

No such schema “org.gnome.ControlCenter”

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

Title:
  gnome-control-center crashes after launch

Status in gnome-control-center package in Ubuntu:
  In Progress

Bug description:
  I had successfully opened settings and used it to change some of the desktop 
options (size of the docker icons, etc.).
  Then I clicked on "Users" and ubuntu-settings crashed.
  Since then, I am unable to open ubuntu-settings - it will open and flash up 
on the screen before crashing.
  This has continued even after restarting the machine a few times.

  ubuntu-settings version: 23.04.2 500

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: ubuntu-settings 23.04.2
  ProcVersionSignature: Ubuntu 6.1.0-16.16-generic 6.1.6
  Uname: Linux 6.1.0-16-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.26.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Mar 11 18:33:16 2023
  InstallationDate: Installed on 2023-03-11 (0 days ago)
  InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20230310)
  PackageArchitecture: all
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  SourcePackage: ubuntu-settings
  UpgradeStatus: No upgrade log present (probably fresh install)

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

[Mark Smith]

And thanks for the tip ref running it without going to "Users" :)

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

Title:
  gnome-control-center crashes after launch

Status in gnome-control-center package in Ubuntu:
  In Progress

Bug description:
  I had successfully opened settings and used it to change some of the desktop 
options (size of the docker icons, etc.).
  Then I clicked on "Users" and ubuntu-settings crashed.
  Since then, I am unable to open ubuntu-settings - it will open and flash up 
on the screen before crashing.
  This has continued even after restarting the machine a few times.

  ubuntu-settings version: 23.04.2 500

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: ubuntu-settings 23.04.2
  ProcVersionSignature: Ubuntu 6.1.0-16.16-generic 6.1.6
  Uname: Linux 6.1.0-16-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.26.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Mar 11 18:33:16 2023
  InstallationDate: Installed on 2023-03-11 (0 days ago)
  InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20230310)
  PackageArchitecture: all
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  SourcePackage: ubuntu-settings
  UpgradeStatus: No upgrade log present (probably fresh install)

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

[Mark Smith]

As a data point, when I run gnome-control-center from the terminal I get
a "Segmentation Error" and core dump.

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

Title:
  gnome-control-center crashes after launch

Status in gnome-control-center package in Ubuntu:
  In Progress

Bug description:
  I had successfully opened settings and used it to change some of the desktop 
options (size of the docker icons, etc.).
  Then I clicked on "Users" and ubuntu-settings crashed.
  Since then, I am unable to open ubuntu-settings - it will open and flash up 
on the screen before crashing.
  This has continued even after restarting the machine a few times.

  ubuntu-settings version: 23.04.2 500

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: ubuntu-settings 23.04.2
  ProcVersionSignature: Ubuntu 6.1.0-16.16-generic 6.1.6
  Uname: Linux 6.1.0-16-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.26.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Mar 11 18:33:16 2023
  InstallationDate: Installed on 2023-03-11 (0 days ago)
  InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20230310)
  PackageArchitecture: all
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  SourcePackage: ubuntu-settings
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2011313/+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 2011313] [NEW] Ubuntu-Settings crashes after launch

[Mark Smith]

Public bug reported:

I had successfully opened settings and used it to change some of the desktop 
options (size of the docker icons, etc.).
Then I clicked on "Users" and ubuntu-settings crashed.
Since then, I am unable to open ubuntu-settings - it will open and flash up on 
the screen before crashing.
This has continued even after restarting the machine a few times.

ubuntu-settings version: 23.04.2 500

ProblemType: Bug
DistroRelease: Ubuntu 23.04
Package: ubuntu-settings 23.04.2
ProcVersionSignature: Ubuntu 6.1.0-16.16-generic 6.1.6
Uname: Linux 6.1.0-16-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.26.0-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Sat Mar 11 18:33:16 2023
InstallationDate: Installed on 2023-03-11 (0 days ago)
InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20230310)
PackageArchitecture: all
ProcEnviron:
 LANG=en_US.UTF-8
 PATH=(custom, no user)
 SHELL=/bin/bash
 TERM=xterm-256color
 XDG_RUNTIME_DIR=
SourcePackage: ubuntu-settings
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug lunar

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

Title:
  Ubuntu-Settings crashes after launch

Status in ubuntu-settings package in Ubuntu:
  New

Bug description:
  I had successfully opened settings and used it to change some of the desktop 
options (size of the docker icons, etc.).
  Then I clicked on "Users" and ubuntu-settings crashed.
  Since then, I am unable to open ubuntu-settings - it will open and flash up 
on the screen before crashing.
  This has continued even after restarting the machine a few times.

  ubuntu-settings version: 23.04.2 500

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: ubuntu-settings 23.04.2
  ProcVersionSignature: Ubuntu 6.1.0-16.16-generic 6.1.6
  Uname: Linux 6.1.0-16-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.26.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Mar 11 18:33:16 2023
  InstallationDate: Installed on 2023-03-11 (0 days ago)
  InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20230310)
  PackageArchitecture: all
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  SourcePackage: ubuntu-settings
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/2011313/+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 2003844] [NEW] Screensharing from my browser (Firefox snap) freezes the display requiring a hard reboot

[Oliver Smith]

Public bug reported:

In the firefox snap (although I'm not convinced it is specific to the
firefox snap) when in a google meets session, I choose to share either
my screen or a specific browser tab.

In ~40% of instances this results in a complete visual freeze of my
system with no interactivity.

Audio / Microphone / Webcam /keyboard are still functional during this
time. But I need to hard restart to be able to interact with my system
again.

This happens more often the longer my system has been running and is
pretty much guaranteed to happen once a day if I am presenting multiple
times.

For reference I have two monitors: A UHD Monitor 1440p (60HZ) and a high
refresh (144HZ) 1080p Monitor, both have scaling set to 100%. It does
not seem to matter which screen I'm presenting to the other.

I have attached the journalctl of my previous boot.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: gnome-shell 42.5-0ubuntu1
ProcVersionSignature: Ubuntu 5.15.0-58.64-generic 5.15.74
Uname: Linux 5.15.0-58-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
ApportVersion: 2.20.11-0ubuntu82.3
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Wed Jan 25 08:51:10 2023
DisplayManager: gdm3
InstallationDate: Installed on 2022-07-31 (177 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419)
RelatedPackageVersions: mutter-common 42.5-0ubuntu1
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug jammy

** Attachment added: "prevboot.txt"
   
https://bugs.launchpad.net/bugs/2003844/+attachment/5643250/+files/prevboot.txt

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

Title:
  Screensharing from my browser (Firefox snap) freezes the display
  requiring a hard reboot

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  In the firefox snap (although I'm not convinced it is specific to the
  firefox snap) when in a google meets session, I choose to share either
  my screen or a specific browser tab.

  In ~40% of instances this results in a complete visual freeze of my
  system with no interactivity.

  Audio / Microphone / Webcam /keyboard are still functional during this
  time. But I need to hard restart to be able to interact with my system
  again.

  This happens more often the longer my system has been running and is
  pretty much guaranteed to happen once a day if I am presenting
  multiple times.

  For reference I have two monitors: A UHD Monitor 1440p (60HZ) and a
  high refresh (144HZ) 1080p Monitor, both have scaling set to 100%. It
  does not seem to matter which screen I'm presenting to the other.

  I have attached the journalctl of my previous boot.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 42.5-0ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-58.64-generic 5.15.74
  Uname: Linux 5.15.0-58-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jan 25 08:51:10 2023
  DisplayManager: gdm3
  InstallationDate: Installed on 2022-07-31 (177 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  RelatedPackageVersions: mutter-common 42.5-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/2003844/+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 1981109] Re: server image pulls in ModemManager via fwupd, consumes 25MiB RAM in every container

[Chloé Smith]

Tested by building a GCE Jammy image using livecd-rootfs from the
proposed pocket. I checked the package manifest of the build and can
confirm that fwupd, modemmanager, and udisks2 are not installed.

I won't change the "verification-needed-jammy" tag yet as the other
clouds will be checked too.

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

Title:
  server image pulls in ModemManager via fwupd, consumes 25MiB RAM in
  every container

Status in fwupd package in Ubuntu:
  Invalid
Status in livecd-rootfs package in Ubuntu:
  Fix Released
Status in modemmanager package in Ubuntu:
  Triaged
Status in ubuntu-meta package in Ubuntu:
  New
Status in fwupd source package in Jammy:
  Invalid
Status in livecd-rootfs source package in Jammy:
  Fix Committed
Status in modemmanager source package in Jammy:
  New
Status in ubuntu-meta source package in Jammy:
  New

Bug description:
  [Impact]

  Cloud images should not have fwupd, modemmanager, and udisks2
  installed as those are not needed and only taking up memory.

  [Test Case]

  Build cloud images with livecd-rootfs and confirm that fwupd,
  modemmanager, and udisks2 are not present and not running.

  [Regression Potential]

  Only thing that might happen is for any of the 3 listed packages
  getting removed from images where they might be used. So possibly
  double-checking if this will affect preinstalled server images and if
  they care about this or not.

  [Original Description]

  Looking at memory utilization in a pristine Ubuntu lxd container (top
  -o RES), I see that ModemManager is running, which I was surprised to
  see is present at all in the stock image.

  Tracking this I find that fwupd depends on libmm-glib0, which in turn
  Recommends: modemmanager.

  Libraries in general should not recommend daemons, so it's possible
  this should be fixed by libmm-glib0 dropping this Recommends.  It
  certainly doesn't seem to be a deliberate decision by the Server Team
  to have modemmanager installed and running by default on all systems.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/1981109/+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 1998017] Re: inhibitShortcutsDialog not working in Ubuntu 22.10 / Gnome 43. Breaks keygrab and passing keys to VMs/remote systems

[John Smith]

** Tags added: kinetic

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

Title:
  inhibitShortcutsDialog not working in Ubuntu 22.10 / Gnome 43. Breaks
  keygrab and passing keys to VMs/remote systems

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  inhibitShortcutsDialog not working in Ubuntu 22.10 / Gnome 43. Breaks
  keygrab and passing keys to VMs/remote systems

  Bug is fixed upstream: https://gitlab.gnome.org/GNOME/gnome-
  shell/-/issues/6107

  Without that fix it is impossible to use same system shortcuts
  (Alt+Shift, etc.) in main system and in VM in virt-manager.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1998017/+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 1998017] [NEW] inhibitShortcutsDialog not working in Ubuntu 22.10 / Gnome 43. Breaks keygrab and passing keys to VMs/remote systems

[John Smith]

Public bug reported:

inhibitShortcutsDialog not working in Ubuntu 22.10 / Gnome 43. Breaks
keygrab and passing keys to VMs/remote systems

Bug is fixed upstream: https://gitlab.gnome.org/GNOME/gnome-
shell/-/issues/6107

Without that fix it is impossible to use same system shortcuts
(Alt+Shift, etc.) in main system and in VM in virt-manager.

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


** Tags: kinetic

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

Title:
  inhibitShortcutsDialog not working in Ubuntu 22.10 / Gnome 43. Breaks
  keygrab and passing keys to VMs/remote systems

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  inhibitShortcutsDialog not working in Ubuntu 22.10 / Gnome 43. Breaks
  keygrab and passing keys to VMs/remote systems

  Bug is fixed upstream: https://gitlab.gnome.org/GNOME/gnome-
  shell/-/issues/6107

  Without that fix it is impossible to use same system shortcuts
  (Alt+Shift, etc.) in main system and in VM in virt-manager.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1998017/+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 1991545] [NEW] Domain groups not accepted as 'AdminIdentities'

[James Paton-Smith]

Public bug reported:

Domain groups cannot be configured as 'AdminIdentities' under
/etc/polkit-1/localauthority.conf.d

EXAMPLE CONFIG

# /etc/polkit-1/localauthority.conf.d/90-test.conf
[Configuration]
AdminIdentities=unix-group:sysapp


With the above config, 'sysapp' is a group in LDAP. SSSD is configured on the 
machine to allow domain users to log in.
Sudo rules have been configured for the 'sysapp' group and work correctly.

However, any action that creates a polkit/GUI prompt for authentication
does not allow users in the 'sysapp' group to authenticate. Instead, it
only accepts auth from the root user.


If I change the config to use a local group, instead of a domain group, 
everything works as expected.
Similarly if I specify a domain USER instead of a domain group, everything 
works as expected.

The problem seems to only be with domain/LDAP groups.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: policykit-1 0.105-33
ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53
Uname: Linux 5.15.0-48-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
CasperMD5CheckResult: unknown
Date: Mon Oct  3 15:20:36 2022
InstallationDate: Installed on 2022-07-15 (80 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
SourcePackage: policykit-1
UpgradeStatus: Upgraded to jammy on 2022-08-02 (61 days ago)

** Affects: policykit-1 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug jammy

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

Title:
  Domain groups not accepted as  'AdminIdentities'

Status in policykit-1 package in Ubuntu:
  New

Bug description:
  Domain groups cannot be configured as 'AdminIdentities' under
  /etc/polkit-1/localauthority.conf.d

  EXAMPLE CONFIG

  # /etc/polkit-1/localauthority.conf.d/90-test.conf
  [Configuration]
  AdminIdentities=unix-group:sysapp

  
  With the above config, 'sysapp' is a group in LDAP. SSSD is configured on the 
machine to allow domain users to log in.
  Sudo rules have been configured for the 'sysapp' group and work correctly.

  However, any action that creates a polkit/GUI prompt for
  authentication does not allow users in the 'sysapp' group to
  authenticate. Instead, it only accepts auth from the root user.

  
  If I change the config to use a local group, instead of a domain group, 
everything works as expected.
  Similarly if I specify a domain USER instead of a domain group, everything 
works as expected.

  The problem seems to only be with domain/LDAP groups.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: policykit-1 0.105-33
  ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53
  Uname: Linux 5.15.0-48-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Mon Oct  3 15:20:36 2022
  InstallationDate: Installed on 2022-07-15 (80 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  SourcePackage: policykit-1
  UpgradeStatus: Upgraded to jammy on 2022-08-02 (61 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/policykit-1/+bug/1991545/+subscriptions


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

[Desktop-packages] [Bug 1848942] Re: Freeze on opening font viewer

[James Paton-Smith]

I tested gnome-font-viewer again on the same systems after upgrading to
Ubuntu 22.04.1 and haven't been able to replicate the issue yet.

Ubuntu 22.04.1
gnome-font-viewer 41.0-2

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

Title:
  Freeze on opening font viewer

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

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

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-font-viewer/+bug/1848942/+subscriptions


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

[Desktop-packages] [Bug 1983112] Re: Appstream does not install config file

[James Paton-Smith]

** Attachment added: "scenario_2_appstream.txt"
   
https://bugs.launchpad.net/ubuntu/+source/appstream/+bug/1983112/+attachment/5607337/+files/scenario_2_appstream.txt

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

Title:
  Appstream does not install config file

Status in appstream package in Ubuntu:
  New

Bug description:
  After performing an Ubuntu automated server install, and installing
  the ubuntu-desktop-minimal package (which includes appstream as a
  dependency) then the snap-store, the snap-store will fail to display
  search results for .deb packages in the Ubuntu apt repositories.

  This is due to a missing config file (/etc/apt/apt.conf.d/50appstream)
  which is supposed to be installed as part of the appstream package.

  The issue can be fixed by re-installing appstream with the following 
command-line:
  apt-get -y install --reinstall -o Dpkg::Options::="--force-confmiss" appstream

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: appstream 0.15.2-2
  ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39
  Uname: Linux 5.15.0-41-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckMismatches: ./boot/grub/grub.cfg
  CasperMD5CheckResult: fail
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jul 29 15:25:44 2022
  InstallationDate: Installed on 2022-07-27 (1 days ago)
  InstallationMedia: Ubuntu-Server 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220421)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: appstream
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/appstream/+bug/1983112/+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 1983112] Re: Appstream does not install config file

[James Paton-Smith]

** Attachment added: "scenario_3_installer.zip"
   
https://bugs.launchpad.net/ubuntu/+source/appstream/+bug/1983112/+attachment/5607336/+files/scenario_3_installer.zip

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

Title:
  Appstream does not install config file

Status in appstream package in Ubuntu:
  New

Bug description:
  After performing an Ubuntu automated server install, and installing
  the ubuntu-desktop-minimal package (which includes appstream as a
  dependency) then the snap-store, the snap-store will fail to display
  search results for .deb packages in the Ubuntu apt repositories.

  This is due to a missing config file (/etc/apt/apt.conf.d/50appstream)
  which is supposed to be installed as part of the appstream package.

  The issue can be fixed by re-installing appstream with the following 
command-line:
  apt-get -y install --reinstall -o Dpkg::Options::="--force-confmiss" appstream

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: appstream 0.15.2-2
  ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39
  Uname: Linux 5.15.0-41-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckMismatches: ./boot/grub/grub.cfg
  CasperMD5CheckResult: fail
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jul 29 15:25:44 2022
  InstallationDate: Installed on 2022-07-27 (1 days ago)
  InstallationMedia: Ubuntu-Server 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220421)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: appstream
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/appstream/+bug/1983112/+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 1983112] Re: Appstream does not install config file

[James Paton-Smith]

** Attachment added: "scenario_2_installer.zip"
   
https://bugs.launchpad.net/ubuntu/+source/appstream/+bug/1983112/+attachment/5607335/+files/scenario_2_installer.zip

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

Title:
  Appstream does not install config file

Status in appstream package in Ubuntu:
  New

Bug description:
  After performing an Ubuntu automated server install, and installing
  the ubuntu-desktop-minimal package (which includes appstream as a
  dependency) then the snap-store, the snap-store will fail to display
  search results for .deb packages in the Ubuntu apt repositories.

  This is due to a missing config file (/etc/apt/apt.conf.d/50appstream)
  which is supposed to be installed as part of the appstream package.

  The issue can be fixed by re-installing appstream with the following 
command-line:
  apt-get -y install --reinstall -o Dpkg::Options::="--force-confmiss" appstream

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: appstream 0.15.2-2
  ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39
  Uname: Linux 5.15.0-41-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckMismatches: ./boot/grub/grub.cfg
  CasperMD5CheckResult: fail
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jul 29 15:25:44 2022
  InstallationDate: Installed on 2022-07-27 (1 days ago)
  InstallationMedia: Ubuntu-Server 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220421)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: appstream
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/appstream/+bug/1983112/+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 1983112] Re: Appstream does not install config file

[James Paton-Smith]

** Attachment added: "scenario_1_installer.zip"
   
https://bugs.launchpad.net/ubuntu/+source/appstream/+bug/1983112/+attachment/5607334/+files/scenario_1_installer.zip

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

Title:
  Appstream does not install config file

Status in appstream package in Ubuntu:
  New

Bug description:
  After performing an Ubuntu automated server install, and installing
  the ubuntu-desktop-minimal package (which includes appstream as a
  dependency) then the snap-store, the snap-store will fail to display
  search results for .deb packages in the Ubuntu apt repositories.

  This is due to a missing config file (/etc/apt/apt.conf.d/50appstream)
  which is supposed to be installed as part of the appstream package.

  The issue can be fixed by re-installing appstream with the following 
command-line:
  apt-get -y install --reinstall -o Dpkg::Options::="--force-confmiss" appstream

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: appstream 0.15.2-2
  ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39
  Uname: Linux 5.15.0-41-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckMismatches: ./boot/grub/grub.cfg
  CasperMD5CheckResult: fail
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jul 29 15:25:44 2022
  InstallationDate: Installed on 2022-07-27 (1 days ago)
  InstallationMedia: Ubuntu-Server 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220421)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: appstream
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/appstream/+bug/1983112/+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 1983112] Re: Appstream does not install config file

[James Paton-Smith]

Reuploading previous attachments after redacting sensitive information.

Original comment copied below:

Okay, I've gone down the rabbit hole with this one. It's possible this
is 2 separate issues.

I tested 3 scenarios:
Scenario 1 - Performed a clean Ubuntu Server install (interactive), and 
installed ubuntu-desktop-minimal post-deployment.
After rebooting, the 50appstream config is present, and I installed snap-store 
and gnome-software.
Neither snap-store nor gnome-software showed any .deb packages. Only snaps.
I tried re-installing appstream and forcing a refresh of the cache, but still 
no .deb packages shown.
Nothing I have tried in this install has been able to fix the issue.

Scenario 2 - I performed a clean install using our automated install image 
(/var/log/installer contents attached) WITHOUT our appstream config reinstall 
script that I shared previously.
After deployment, ubuntu-desktop-minimal is already installed, and 50appstream 
config is MISSING (see attachment).
Both snap-store and gnome-software only show snaps. No .deb packages.
Next, I ran the appstream re-install script I shared previously and rebooted 
the machine.
After the reboot, gnome-software correctly shows .deb packages. However, 
snap-store is still only showing snaps!!!

Scenario 3 - I performed a clean install using our automated install image 
(/var/log/installer contents attached), this time including our appstream 
config reinstall script.
After the deployment, 50appstream config is PRESENT.
Both snap-store and gnome-software work correctly and show both snaps and .deb 
packages.

The varying behaviour between all 3 has completely blown my mind. I
really don't know what is the cause of the issue, and potentially this
is even 2 separate issues, since in Scenario 1, neither snap-store nor
gnome-software work correctly.

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

Title:
  Appstream does not install config file

Status in appstream package in Ubuntu:
  New

Bug description:
  After performing an Ubuntu automated server install, and installing
  the ubuntu-desktop-minimal package (which includes appstream as a
  dependency) then the snap-store, the snap-store will fail to display
  search results for .deb packages in the Ubuntu apt repositories.

  This is due to a missing config file (/etc/apt/apt.conf.d/50appstream)
  which is supposed to be installed as part of the appstream package.

  The issue can be fixed by re-installing appstream with the following 
command-line:
  apt-get -y install --reinstall -o Dpkg::Options::="--force-confmiss" appstream

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: appstream 0.15.2-2
  ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39
  Uname: Linux 5.15.0-41-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckMismatches: ./boot/grub/grub.cfg
  CasperMD5CheckResult: fail
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jul 29 15:25:44 2022
  InstallationDate: Installed on 2022-07-27 (1 days ago)
  InstallationMedia: Ubuntu-Server 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220421)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: appstream
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/appstream/+bug/1983112/+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 1983112] Re: Appstream does not install config file

[James Paton-Smith]

** Attachment removed: "installer logs for Scenario 1"
   
https://bugs.launchpad.net/ubuntu/+source/appstream/+bug/1983112/+attachment/5607134/+files/scenario_1_installer.zip

** Attachment removed: "scenario_2_installer.zip"
   
https://bugs.launchpad.net/ubuntu/+source/appstream/+bug/1983112/+attachment/5607135/+files/scenario_2_installer.zip

** Attachment removed: "scenario_2_appstream.txt"
   
https://bugs.launchpad.net/ubuntu/+source/appstream/+bug/1983112/+attachment/5607136/+files/scenario_2_appstream.txt

** Attachment removed: "scenario_3_installer.zip"
   
https://bugs.launchpad.net/ubuntu/+source/appstream/+bug/1983112/+attachment/5607137/+files/scenario_3_installer.zip

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

Title:
  Appstream does not install config file

Status in appstream package in Ubuntu:
  New

Bug description:
  After performing an Ubuntu automated server install, and installing
  the ubuntu-desktop-minimal package (which includes appstream as a
  dependency) then the snap-store, the snap-store will fail to display
  search results for .deb packages in the Ubuntu apt repositories.

  This is due to a missing config file (/etc/apt/apt.conf.d/50appstream)
  which is supposed to be installed as part of the appstream package.

  The issue can be fixed by re-installing appstream with the following 
command-line:
  apt-get -y install --reinstall -o Dpkg::Options::="--force-confmiss" appstream

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: appstream 0.15.2-2
  ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39
  Uname: Linux 5.15.0-41-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckMismatches: ./boot/grub/grub.cfg
  CasperMD5CheckResult: fail
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jul 29 15:25:44 2022
  InstallationDate: Installed on 2022-07-27 (1 days ago)
  InstallationMedia: Ubuntu-Server 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220421)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: appstream
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/appstream/+bug/1983112/+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 1983112] Re: Appstream does not install config file

[James Paton-Smith]

** Attachment added: "scenario_3_installer.zip"
   
https://bugs.launchpad.net/ubuntu/+source/appstream/+bug/1983112/+attachment/5607137/+files/scenario_3_installer.zip

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

Title:
  Appstream does not install config file

Status in appstream package in Ubuntu:
  New

Bug description:
  After performing an Ubuntu automated server install, and installing
  the ubuntu-desktop-minimal package (which includes appstream as a
  dependency) then the snap-store, the snap-store will fail to display
  search results for .deb packages in the Ubuntu apt repositories.

  This is due to a missing config file (/etc/apt/apt.conf.d/50appstream)
  which is supposed to be installed as part of the appstream package.

  The issue can be fixed by re-installing appstream with the following 
command-line:
  apt-get -y install --reinstall -o Dpkg::Options::="--force-confmiss" appstream

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: appstream 0.15.2-2
  ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39
  Uname: Linux 5.15.0-41-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckMismatches: ./boot/grub/grub.cfg
  CasperMD5CheckResult: fail
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jul 29 15:25:44 2022
  InstallationDate: Installed on 2022-07-27 (1 days ago)
  InstallationMedia: Ubuntu-Server 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220421)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: appstream
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/appstream/+bug/1983112/+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 1983112] Re: Appstream does not install config file

[James Paton-Smith]

** Attachment added: "scenario_2_appstream.txt"
   
https://bugs.launchpad.net/ubuntu/+source/appstream/+bug/1983112/+attachment/5607136/+files/scenario_2_appstream.txt

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

Title:
  Appstream does not install config file

Status in appstream package in Ubuntu:
  New

Bug description:
  After performing an Ubuntu automated server install, and installing
  the ubuntu-desktop-minimal package (which includes appstream as a
  dependency) then the snap-store, the snap-store will fail to display
  search results for .deb packages in the Ubuntu apt repositories.

  This is due to a missing config file (/etc/apt/apt.conf.d/50appstream)
  which is supposed to be installed as part of the appstream package.

  The issue can be fixed by re-installing appstream with the following 
command-line:
  apt-get -y install --reinstall -o Dpkg::Options::="--force-confmiss" appstream

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: appstream 0.15.2-2
  ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39
  Uname: Linux 5.15.0-41-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckMismatches: ./boot/grub/grub.cfg
  CasperMD5CheckResult: fail
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jul 29 15:25:44 2022
  InstallationDate: Installed on 2022-07-27 (1 days ago)
  InstallationMedia: Ubuntu-Server 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220421)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: appstream
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/appstream/+bug/1983112/+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 1983112] Re: Appstream does not install config file

[James Paton-Smith]

** Attachment added: "scenario_2_installer.zip"
   
https://bugs.launchpad.net/ubuntu/+source/appstream/+bug/1983112/+attachment/5607135/+files/scenario_2_installer.zip

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

Title:
  Appstream does not install config file

Status in appstream package in Ubuntu:
  New

Bug description:
  After performing an Ubuntu automated server install, and installing
  the ubuntu-desktop-minimal package (which includes appstream as a
  dependency) then the snap-store, the snap-store will fail to display
  search results for .deb packages in the Ubuntu apt repositories.

  This is due to a missing config file (/etc/apt/apt.conf.d/50appstream)
  which is supposed to be installed as part of the appstream package.

  The issue can be fixed by re-installing appstream with the following 
command-line:
  apt-get -y install --reinstall -o Dpkg::Options::="--force-confmiss" appstream

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: appstream 0.15.2-2
  ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39
  Uname: Linux 5.15.0-41-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckMismatches: ./boot/grub/grub.cfg
  CasperMD5CheckResult: fail
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jul 29 15:25:44 2022
  InstallationDate: Installed on 2022-07-27 (1 days ago)
  InstallationMedia: Ubuntu-Server 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220421)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: appstream
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/appstream/+bug/1983112/+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 1983112] Re: Appstream does not install config file

[James Paton-Smith]

Okay, I've gone down the rabbit hole with this one. It's possible this
is 2 separate issues.

I tested 3 scenarios:
Scenario 1 - Performed a clean Ubuntu Server install (interactive), and 
installed ubuntu-desktop-minimal post-deployment.
After rebooting, the 50appstream config is present, and I installed snap-store 
and gnome-software.
Neither snap-store nor gnome-software showed any .deb packages. Only snaps.
I tried re-installing appstream and forcing a refresh of the cache, but still 
no .deb packages shown.
Nothing I have tried in this install has been able to fix the issue.

Scenario 2 - I performed a clean install using our automated install image 
(/var/log/installer contents attached) WITHOUT our appstream config reinstall 
script that I shared previously.
After deployment, ubuntu-desktop-minimal is already installed, and 50appstream 
config is MISSING (see attachment).
Both snap-store and gnome-software only show snaps. No .deb packages.
Next, I ran the appstream re-install script I shared previously and rebooted 
the machine.
After the reboot, gnome-software correctly shows .deb packages. However, 
snap-store is still only showing snaps!!!

Scenario 3 - I performed a clean install using our automated install image 
(/var/log/installer contents attached), this time including our appstream 
config reinstall script.
After the deployment, 50appstream config is PRESENT.
Both snap-store and gnome-software work correctly and show both snaps and .deb 
packages.

The varying behaviour between all 3 has completely blown my mind. I
really don't know what is the cause of the issue, and potentially this
is even 2 separate issues, since in Scenario 1, neither snap-store nor
gnome-software work correctly.




** Attachment added: "installer logs for Scenario 1"
   
https://bugs.launchpad.net/ubuntu/+source/appstream/+bug/1983112/+attachment/5607134/+files/scenario_1_installer.zip

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

Title:
  Appstream does not install config file

Status in appstream package in Ubuntu:
  New

Bug description:
  After performing an Ubuntu automated server install, and installing
  the ubuntu-desktop-minimal package (which includes appstream as a
  dependency) then the snap-store, the snap-store will fail to display
  search results for .deb packages in the Ubuntu apt repositories.

  This is due to a missing config file (/etc/apt/apt.conf.d/50appstream)
  which is supposed to be installed as part of the appstream package.

  The issue can be fixed by re-installing appstream with the following 
command-line:
  apt-get -y install --reinstall -o Dpkg::Options::="--force-confmiss" appstream

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: appstream 0.15.2-2
  ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39
  Uname: Linux 5.15.0-41-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckMismatches: ./boot/grub/grub.cfg
  CasperMD5CheckResult: fail
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jul 29 15:25:44 2022
  InstallationDate: Installed on 2022-07-27 (1 days ago)
  InstallationMedia: Ubuntu-Server 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220421)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: appstream
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/appstream/+bug/1983112/+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 1853115] Re: localauthority.conf - AdminIdentities: unix-group is ignored

[James Paton-Smith]

I am experiencing the same issue on Ubuntu 20.04.4 with the below polkit
config, where sysapp is an LDAP group, and we are using SSSD for LDAP
login to our machines.


# This file is managed by Puppet. DO NOT EDIT.
[Configuration]
AdminIdentities=unix-group:sysapp;unix-group:sudo;unix-group:admin


When attempting to install software via GUI (snap-store) or update packages, 
the GUI prompt only accepts authorisation from users in the 'sudo' or 'admin' 
groups.

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

Title:
  localauthority.conf - AdminIdentities: unix-group is ignored

Status in policykit-1 package in Ubuntu:
  Confirmed

Bug description:
  Allowed users and groups as admins for pkexec are defined in:

/etc/polkit-1/localauthority.conf.d/51-ubuntu-admin.conf

[Configuration]
AdminIdentities=unix-group:sudo;unix-group:admin;unix-group:localadmin

  
  As you can see, I added unix-group:localadmin

  My user is localadmin-user1 who is in the local group localadmin. It does not 
matter if I create a new configuration file
/etc/polkit-1/localauthority.conf.d/99-myadmins.conf or expand the original 
51-ubuntu-admin.conf

  
[Configuration]
AdminIdentities=unix-group:sudo;unix-group:admin;unix-group:localadmin

  
  If I add the user himself instead of his group localadmin the user is listed 
the allowed list for pkexec.

[Configuration]
AdminIdentities=unix-group:sudo;unix-group:admin;unix-user:localadmin-user1



  How to reproduce:
  - create local user and group (here: localadmin)
  - add unix-group:localadmin to 
/etc/polkit-1/localauthority.conf.d/51-ubuntu-admin.conf
  - pkexec mount
-> the local user in group localadmin is not listed
  - add unix-user:localadmin-user1 to 
/etc/polkit-1/localauthority.conf.d/51-ubuntu-admin.conf
  - pkexec mount
-> the local user localadmin-user1 is listed

  
  
  Kubuntu 19.10
  policykit-10.105-26ubuntu1
  SSSD for system authorization including domain

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/policykit-1/+bug/1853115/+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 1983112] Re: Appstream does not install config file

[James Paton-Smith]

As far as I can tell, this only happens during deployment when 
installing the ubuntu-desktop-minimal (haven't tried with the full-fat 
ubuntu-desktop package) via the new Ubuntu automated server install method.

So probably is an Ubuntu-specific issue. I will try to do more testing 
and narrow down the exact combination of events causing this.


On 01/08/2022 10:23, Matthias Klumpp wrote:
> Very odd... There is nothing special about this config file (it's installed 
> like every other) and this works absolutely fine on Debian and even my Ubuntu 
> VM.
> So, something very odd and possibly uBUNTU-SPECIFIC is going on here...
>
-- 
James Paton-Smith
Linux Support Officer

EBI Systems Application Group, South Building, Studio 12
European Bioinformatics Institute (EMBL-EBI)
Wellcome Trust Genome Campus
Hinxton
Cambridge
CB10 1SD

+44 (0)1223 494308

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

Title:
  Appstream does not install config file

Status in appstream package in Ubuntu:
  New

Bug description:
  After performing an Ubuntu automated server install, and installing
  the ubuntu-desktop-minimal package (which includes appstream as a
  dependency) then the snap-store, the snap-store will fail to display
  search results for .deb packages in the Ubuntu apt repositories.

  This is due to a missing config file (/etc/apt/apt.conf.d/50appstream)
  which is supposed to be installed as part of the appstream package.

  The issue can be fixed by re-installing appstream with the following 
command-line:
  apt-get -y install --reinstall -o Dpkg::Options::="--force-confmiss" appstream

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: appstream 0.15.2-2
  ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39
  Uname: Linux 5.15.0-41-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckMismatches: ./boot/grub/grub.cfg
  CasperMD5CheckResult: fail
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jul 29 15:25:44 2022
  InstallationDate: Installed on 2022-07-27 (1 days ago)
  InstallationMedia: Ubuntu-Server 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220421)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: appstream
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/appstream/+bug/1983112/+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 1983112] Re: Appstream does not install config file

[James Paton-Smith]

No, I did not remove the config file manually.
We're actually using the attached bash script as a late-command in the 
autoinstall as a workaround to fix the issue.

Without this script, the snap-store simply refuses to show .deb packages
from the repos.

** Attachment added: "appstream_config_reinstall"
   
https://bugs.launchpad.net/ubuntu/+source/appstream/+bug/1983112/+attachment/5606252/+files/appstream_fix.sh

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

Title:
  Appstream does not install config file

Status in appstream package in Ubuntu:
  New

Bug description:
  After performing an Ubuntu automated server install, and installing
  the ubuntu-desktop-minimal package (which includes appstream as a
  dependency) then the snap-store, the snap-store will fail to display
  search results for .deb packages in the Ubuntu apt repositories.

  This is due to a missing config file (/etc/apt/apt.conf.d/50appstream)
  which is supposed to be installed as part of the appstream package.

  The issue can be fixed by re-installing appstream with the following 
command-line:
  apt-get -y install --reinstall -o Dpkg::Options::="--force-confmiss" appstream

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: appstream 0.15.2-2
  ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39
  Uname: Linux 5.15.0-41-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckMismatches: ./boot/grub/grub.cfg
  CasperMD5CheckResult: fail
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jul 29 15:25:44 2022
  InstallationDate: Installed on 2022-07-27 (1 days ago)
  InstallationMedia: Ubuntu-Server 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220421)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: appstream
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/appstream/+bug/1983112/+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 1983112] [NEW] Appstream does not install config file

[James Paton-Smith]

Public bug reported:

After performing an Ubuntu automated server install, and installing the
ubuntu-desktop-minimal package (which includes appstream as a
dependency) then the snap-store, the snap-store will fail to display
search results for .deb packages in the Ubuntu apt repositories.

This is due to a missing config file (/etc/apt/apt.conf.d/50appstream)
which is supposed to be installed as part of the appstream package.

The issue can be fixed by re-installing appstream with the following 
command-line:
apt-get -y install --reinstall -o Dpkg::Options::="--force-confmiss" appstream

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: appstream 0.15.2-2
ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39
Uname: Linux 5.15.0-41-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
CasperMD5CheckMismatches: ./boot/grub/grub.cfg
CasperMD5CheckResult: fail
CurrentDesktop: ubuntu:GNOME
Date: Fri Jul 29 15:25:44 2022
InstallationDate: Installed on 2022-07-27 (1 days ago)
InstallationMedia: Ubuntu-Server 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220421)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
SourcePackage: appstream
UpgradeStatus: No upgrade log present (probably fresh install)

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


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

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

Title:
  Appstream does not install config file

Status in appstream package in Ubuntu:
  New

Bug description:
  After performing an Ubuntu automated server install, and installing
  the ubuntu-desktop-minimal package (which includes appstream as a
  dependency) then the snap-store, the snap-store will fail to display
  search results for .deb packages in the Ubuntu apt repositories.

  This is due to a missing config file (/etc/apt/apt.conf.d/50appstream)
  which is supposed to be installed as part of the appstream package.

  The issue can be fixed by re-installing appstream with the following 
command-line:
  apt-get -y install --reinstall -o Dpkg::Options::="--force-confmiss" appstream

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: appstream 0.15.2-2
  ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39
  Uname: Linux 5.15.0-41-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckMismatches: ./boot/grub/grub.cfg
  CasperMD5CheckResult: fail
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jul 29 15:25:44 2022
  InstallationDate: Installed on 2022-07-27 (1 days ago)
  InstallationMedia: Ubuntu-Server 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220421)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: appstream
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/appstream/+bug/1983112/+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 1976498] Re: nautilus causes gvfsd-trash 'Too many files open' error and fills syslog

[Mark Smith]

Not sure this was actually a bug. I reinstalled my system anyway so the
issue went away. Now marked as invalid

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

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

Title:
  nautilus causes gvfsd-trash 'Too many files open' error and fills
  syslog

Status in nautilus package in Ubuntu:
  Invalid

Bug description:
  My syslog is filled (to >30GB) regularly with these messages.

  Jun  1 11:41:49 marks-linux-box gvfsd[123068]: (process:123068): 
GLib-GIO-WARNING **: 10:41:49.625: fail: Error accepting connection: Too many 
open files
  Jun  1 11:41:49 marks-linux-box gvfsd[123068]: message repeated 2 times: [ 
(process:123068): GLib-GIO-WARNING **: 10:41:49.625: fail: Error accepting 
connection: Too many open files]
  Jun  1 11:41:49 marks-linux-box gvfsd[123068]: (process:123068): 
GLib-GIO-WARNING **: 10:41:49.626: fail: Error accepting connection: Too many 
open files
  Jun  1 11:41:49 marks-linux-box gvfsd[123068]: message repeated 2 times: [ 
(process:123068): GLib-GIO-WARNING **: 10:41:49.626: fail: Error accepting 
connection: Too many open files]
  Jun  1 11:41:49 marks-linux-box gvfsd[123068]: (process:123068): 
GLib-GIO-WARNING **: 10:41:49.627: fail: Error accepting connection: Too many 
open files
  Jun  1 11:41:49 marks-linux-box gvfsd[123068]: message repeated 2 times: [ 
(process:123068): GLib-GIO-WARNING **: 10:41:49.627: fail: Error accepting 
connection: Too many open files]
  Jun  1 11:41:49 marks-linux-box gvfsd[123068]: (process:123068): 
GLib-GIO-WARNING **: 10:41:49.628: fail: Error accepting connection: Too many 
open files
  Jun  1 11:41:49 marks-linux-box gvfsd[123068]: message repeated 2 times: [ 
(process:123068): GLib-GIO-WARNING **: 10:41:49.628: fail: Error accepting 
connection: Too many open files]
  Jun  1 11:41:49 marks-linux-box gnome-shell[3312]: DING: 
(org.gnome.Nautilus:156898): GVFS-WARNING **: 11:41:49.618: The peer-to-peer 
connection failed: Unable to create socket: Too many open files. Falling back 
to the session bus. Your application is probably missing 
--filesystem=xdg-run/gvfsd privileges.
  Jun  1 11:41:49 marks-linux-box gvfsd[123068]: (process:123068): 
GLib-GIO-WARNING **: 10:41:49.629: fail: Error accepting connection: Too many 
open files
  Jun  1 11:41:49 marks-linux-box gvfsd[123068]: (process:123068): 
GLib-GIO-WARNING **: 10:41:49.629: fail: Error accepting connection: Too many 
open files
  Jun  1 11:41:49 marks-linux-box gvfsd[123068]: (process:123068): 
GLib-GIO-WARNING **: 10:41:49.630: fail: Error accepting connection: Too many 
open files
  Jun  1 11:41:49 marks-linux-box gvfsd[123068]: message repeated 2 times: [ 
(process:123068): GLib-GIO-WARNING **: 10:41:49.630: fail: Error accepting 
connection: Too many open files]
  Jun  1 11:41:49 marks-linux-box gvfsd[123068]: (process:123068): 
GLib-GIO-WARNING **: 10:41:49.631: fail: Error accepting connection: Too many 
open files
  Jun  1 11:41:49 marks-linux-box gvfsd[123068]: daemon: Error creating server 
at address unix:path=/run/user/1000/gvfsd/socket-z3fCgn9o: Unable to create 
socket: Too many open files
  Jun  1 11:41:49 marks-linux-box gvfsd[123068]: (process:123068): 
GLib-GIO-WARNING **: 10:41:49.631: fail: Error accepting connection: Too many 
open files
  Jun  1 11:41:49 marks-linux-box gvfsd[123068]: (process:123068): 
GLib-GIO-WARNING **: 10:41:49.632: fail: Error accepting connection: Too many 
open files
  Jun  1 11:41:49 marks-linux-box gvfsd[123068]: message repeated 2 times: [ 
(process:123068): GLib-GIO-WARNING **: 10:41:49.632: fail: Error accepting 
connection: Too many open files]
  Jun  1 11:41:49 marks-linux-box gvfsd[123068]: (process:123068): 
GLib-GIO-WARNING **: 10:41:49.633: fail: Error accepting connection: Too many 
open files
  Jun  1 11:41:49 marks-linux-box gvfsd[123068]: (process:123068): 
GLib-GIO-WARNING **: 10:41:49.633: fail: Error accepting connection: Too many 
open files
  Jun  1 11:41:49 marks-linux-box gnome-shell[3312]: DING: GNOME nautilus 42.1.1
  Jun  1 11:41:49 marks-linux-box gvfsd[123068]: (process:123068): 
GLib-GIO-WARNING **: 10:41:49.633: fail: Error accepting connection: Too many 
open files
  Jun  1 11:41:49 marks-linux-box gvfsd[123068]: (process:123068): 
GLib-GIO-WARNING **: 10:41:49.634: fail: Error accepting connection: Too many 
open files
  Jun  1 11:41:49 marks-linux-box gvfsd[123068]: (process:123068): 
GLib-GIO-WARNING **: 10:41:49.634: fail: Error accepting connection: Too many 
open files
  Jun  1 11:41:49 marks-linux-box gvfsd[123068]: (process:123068): 
GLib-GIO-WARNING **: 10:41:49.635: fail: Error accepting connection: Too many 
open files
  Jun  1 11:41:49 marks-linux-box gvfsd[123068]: message repeated 2 times: [ 
(process:123068): GLib-GIO-WARNING **: 10:41:49.635: fail: Error accepting 
connection: Too many open files]
  Jun  1 11:41:49 

[Desktop-packages] [Bug 1976498] Re: DING causes gvfsd 'Too many files open' error and fills syslog

[Mark Smith]

Changed from ding to nautilus after reading about nautilus gvfsd-trash
bug

** Package changed: ding (Ubuntu) => nautilus (Ubuntu)

** Summary changed:

- DING causes gvfsd 'Too many files open' error and fills syslog
+ nautilus causes gvfsd-trash 'Too many files open' error and fills syslog

** Description changed:

- My syslog is filled (to >30GB) regularly with these messages. I seem to
- have this thing called DING going on, which maybe causing it?
+ My syslog is filled (to >30GB) regularly with these messages.
  
  Jun  1 11:41:49 marks-linux-box gvfsd[123068]: (process:123068): 
GLib-GIO-WARNING **: 10:41:49.625: fail: Error accepting connection: Too many 
open files
  Jun  1 11:41:49 marks-linux-box gvfsd[123068]: message repeated 2 times: [ 
(process:123068): GLib-GIO-WARNING **: 10:41:49.625: fail: Error accepting 
connection: Too many open files]
  Jun  1 11:41:49 marks-linux-box gvfsd[123068]: (process:123068): 
GLib-GIO-WARNING **: 10:41:49.626: fail: Error accepting connection: Too many 
open files
  Jun  1 11:41:49 marks-linux-box gvfsd[123068]: message repeated 2 times: [ 
(process:123068): GLib-GIO-WARNING **: 10:41:49.626: fail: Error accepting 
connection: Too many open files]
  Jun  1 11:41:49 marks-linux-box gvfsd[123068]: (process:123068): 
GLib-GIO-WARNING **: 10:41:49.627: fail: Error accepting connection: Too many 
open files
  Jun  1 11:41:49 marks-linux-box gvfsd[123068]: message repeated 2 times: [ 
(process:123068): GLib-GIO-WARNING **: 10:41:49.627: fail: Error accepting 
connection: Too many open files]
  Jun  1 11:41:49 marks-linux-box gvfsd[123068]: (process:123068): 
GLib-GIO-WARNING **: 10:41:49.628: fail: Error accepting connection: Too many 
open files
  Jun  1 11:41:49 marks-linux-box gvfsd[123068]: message repeated 2 times: [ 
(process:123068): GLib-GIO-WARNING **: 10:41:49.628: fail: Error accepting 
connection: Too many open files]
  Jun  1 11:41:49 marks-linux-box gnome-shell[3312]: DING: 
(org.gnome.Nautilus:156898): GVFS-WARNING **: 11:41:49.618: The peer-to-peer 
connection failed: Unable to create socket: Too many open files. Falling back 
to the session bus. Your application is probably missing 
--filesystem=xdg-run/gvfsd privileges.
  Jun  1 11:41:49 marks-linux-box gvfsd[123068]: (process:123068): 
GLib-GIO-WARNING **: 10:41:49.629: fail: Error accepting connection: Too many 
open files
  Jun  1 11:41:49 marks-linux-box gvfsd[123068]: (process:123068): 
GLib-GIO-WARNING **: 10:41:49.629: fail: Error accepting connection: Too many 
open files
  Jun  1 11:41:49 marks-linux-box gvfsd[123068]: (process:123068): 
GLib-GIO-WARNING **: 10:41:49.630: fail: Error accepting connection: Too many 
open files
  Jun  1 11:41:49 marks-linux-box gvfsd[123068]: message repeated 2 times: [ 
(process:123068): GLib-GIO-WARNING **: 10:41:49.630: fail: Error accepting 
connection: Too many open files]
  Jun  1 11:41:49 marks-linux-box gvfsd[123068]: (process:123068): 
GLib-GIO-WARNING **: 10:41:49.631: fail: Error accepting connection: Too many 
open files
  Jun  1 11:41:49 marks-linux-box gvfsd[123068]: daemon: Error creating server 
at address unix:path=/run/user/1000/gvfsd/socket-z3fCgn9o: Unable to create 
socket: Too many open files
  Jun  1 11:41:49 marks-linux-box gvfsd[123068]: (process:123068): 
GLib-GIO-WARNING **: 10:41:49.631: fail: Error accepting connection: Too many 
open files
  Jun  1 11:41:49 marks-linux-box gvfsd[123068]: (process:123068): 
GLib-GIO-WARNING **: 10:41:49.632: fail: Error accepting connection: Too many 
open files
  Jun  1 11:41:49 marks-linux-box gvfsd[123068]: message repeated 2 times: [ 
(process:123068): GLib-GIO-WARNING **: 10:41:49.632: fail: Error accepting 
connection: Too many open files]
  Jun  1 11:41:49 marks-linux-box gvfsd[123068]: (process:123068): 
GLib-GIO-WARNING **: 10:41:49.633: fail: Error accepting connection: Too many 
open files
  Jun  1 11:41:49 marks-linux-box gvfsd[123068]: (process:123068): 
GLib-GIO-WARNING **: 10:41:49.633: fail: Error accepting connection: Too many 
open files
  Jun  1 11:41:49 marks-linux-box gnome-shell[3312]: DING: GNOME nautilus 42.1.1
  Jun  1 11:41:49 marks-linux-box gvfsd[123068]: (process:123068): 
GLib-GIO-WARNING **: 10:41:49.633: fail: Error accepting connection: Too many 
open files
  Jun  1 11:41:49 marks-linux-box gvfsd[123068]: (process:123068): 
GLib-GIO-WARNING **: 10:41:49.634: fail: Error accepting connection: Too many 
open files
  Jun  1 11:41:49 marks-linux-box gvfsd[123068]: (process:123068): 
GLib-GIO-WARNING **: 10:41:49.634: fail: Error accepting connection: Too many 
open files
  Jun  1 11:41:49 marks-linux-box gvfsd[123068]: (process:123068): 
GLib-GIO-WARNING **: 10:41:49.635: fail: Error accepting connection: Too many 
open files
  Jun  1 11:41:49 marks-linux-box gvfsd[123068]: message repeated 2 times: [ 
(process:123068): GLib-GIO-WARNING **: 10:41:49.635: fail: Error accepting 
connection: Too many open files]
  Jun  1 11:41:49 marks-linux-box gvfsd[123068]: 

[Desktop-packages] [Bug 1975487] [NEW] zsys not installed during Kinetic ISO install with ZFS option

[Mark Smith]

Public bug reported:

After following the instructions at:
http://iso.qa.ubuntu.com/qatracker/milestones/433/builds/248685/testcases/1716/results
 
on the 20220523 daily build of Kinetic, I used the command

zsysctl show

and was met with the message:

~$ zsysctl show
Command 'zsysctl' not found, but can be installed with:
sudo apt install zsys

ProblemType: Bug
DistroRelease: Ubuntu 22.10
Package: zsys (not installed)
ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
Uname: Linux 5.15.0-27-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu82
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Mon May 23 12:33:24 2022
InstallationDate: Installed on 2022-05-23 (0 days ago)
InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220522)
SourcePackage: zsys
UpgradeStatus: No upgrade log present (probably fresh install)

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


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

** Attachment added: "Screenshot"
   
https://bugs.launchpad.net/bugs/1975487/+attachment/5592259/+files/Screenshot%20from%202022-05-23%2012-39-43.png

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

Title:
  zsys not installed during Kinetic ISO install with ZFS option

Status in zsys package in Ubuntu:
  New

Bug description:
  After following the instructions at:
  
http://iso.qa.ubuntu.com/qatracker/milestones/433/builds/248685/testcases/1716/results
 
  on the 20220523 daily build of Kinetic, I used the command

  zsysctl show

  and was met with the message:

  ~$ zsysctl show
  Command 'zsysctl' not found, but can be installed with:
  sudo apt install zsys

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: zsys (not installed)
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Uname: Linux 5.15.0-27-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon May 23 12:33:24 2022
  InstallationDate: Installed on 2022-05-23 (0 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220522)
  SourcePackage: zsys
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zsys/+bug/1975487/+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 1970013] Re: Totem Video player displays distorted video (Intel Ivy Bridge)

[John Smith]

My Ubuntu 22.04 also affected. It's work fine under xorg session, but distorted 
under wayland.
cpu: i7 3612qm (Ivy Bridge).

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

Title:
  Totem Video player displays distorted video (Intel Ivy Bridge)

Status in totem package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 22.04 freshly installed along with ubuntu-restricted-extra
  package. Default totem player unable to play videos properly. videos
  looks distorted. Forwarding videos does not work. Video get stopped
  once forwarded.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr 23 11:02:49 2022
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:21f9]
  InstallationDate: Installed on 2022-04-22 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  MachineType: LENOVO 34601F4
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-25-generic 
root=UUID=be040347-6300-407e-9e19-da58389c3a6f ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/19/2013
  dmi.bios.release: 2.59
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G6ET99WW (2.59 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 34601F4
  dmi.board.vendor: LENOVO
  dmi.board.version: NO DPK
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.ec.firmware.release: 1.4
  dmi.modalias: 
dmi:bvnLENOVO:bvrG6ET99WW(2.59):bd11/19/2013:br2.59:efr1.4:svnLENOVO:pn34601F4:pvrThinkPadX1Carbon:rvnLENOVO:rn34601F4:rvrNODPK:cvnLENOVO:ct10:cvrNotAvailable:skuLENOVO_MT_3460:
  dmi.product.family: ThinkPad X1 Carbon
  dmi.product.name: 34601F4
  dmi.product.sku: LENOVO_MT_3460
  dmi.product.version: ThinkPad X1 Carbon
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.110-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3
  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/totem/+bug/1970013/+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 1969140] Re: graphic glitches when minimizing and maximizing apps

[Daniel Smith]

I reported this as well, however, they think that it is issue with my
device. https://bugs.launchpad.net/ubuntu/+source/gnome-
shell/+bug/1967471

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

Title:
  graphic glitches when minimizing and maximizing apps

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Graphic glitches appears while minimizing or maximizing apps in x11
  session randomly

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 42.0-2ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Thu Apr 14 17:07:49 2022
  DisplayManager: gdm3
  GsettingsChanges:
   
  InstallationDate: Installed on 2022-04-12 (2 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Daily amd64 (20220409)
  ProcEnviron:
   LANGUAGE=en_GB:en
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 42.0-3ubuntu1
  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/1969140/+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 1967883] Re: [snap] Firefox Nightly Application Icon missing from "Show Applications" screen

[Mark Smith]

No, It was a straight install with me present at the desktop computer
all the way through - no switching or even screen locking.

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

Title:
  [snap] Firefox Nightly Application Icon missing from "Show
  Applications" screen

Status in firefox package in Ubuntu:
  New

Bug description:
  From a clean install of Ubuntu 22.04 beta, I have installed VLC and Firefox 
(nightly) from Ubuntu Software (as snaps).
  Neither of the two icons/graphics show up in the show applications window - 
either in the thumbnails of the groups I have created, or the expanded windows 
(see screenshots).

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 42.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Uname: Linux 5.15.0-23-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu80
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr  5 14:49:04 2022
  DisplayManager: gdm3
  InstallationDate: Installed on 2022-03-31 (4 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 
(20220329.1)
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions: mutter-common 42.0-1ubuntu1
  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/firefox/+bug/1967883/+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 1967883] Re: Application Icons missing from "Show Applications" screen

[Mark Smith]

** Attachment added: "Screenshot from 2022-04-05 14-48-11.png"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1967883/+attachment/5577339/+files/Screenshot%20from%202022-04-05%2014-48-11.png

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

Title:
  Application Icons missing from "Show Applications" screen

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  From a clean install of Ubuntu 22.04 beta, I have installed VLC and Firefox 
(nightly) from Ubuntu Software (as snaps).
  Neither of the two icons/graphics show up in the show applications window - 
either in the thumbnails of the groups I have created, or the expanded windows 
(see screenshots).

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 42.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Uname: Linux 5.15.0-23-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu80
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr  5 14:49:04 2022
  DisplayManager: gdm3
  InstallationDate: Installed on 2022-03-31 (4 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 
(20220329.1)
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions: mutter-common 42.0-1ubuntu1
  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/1967883/+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 1967883] Re: Application Icons missing from "Show Applications" screen

[Mark Smith]

** Attachment added: "Screenshot from 2022-04-05 14-48-11.png"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1967883/+attachment/5577338/+files/Screenshot%20from%202022-04-05%2014-48-11.png

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

Title:
  Application Icons missing from "Show Applications" screen

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  From a clean install of Ubuntu 22.04 beta, I have installed VLC and Firefox 
(nightly) from Ubuntu Software (as snaps).
  Neither of the two icons/graphics show up in the show applications window - 
either in the thumbnails of the groups I have created, or the expanded windows 
(see screenshots).

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 42.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Uname: Linux 5.15.0-23-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu80
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr  5 14:49:04 2022
  DisplayManager: gdm3
  InstallationDate: Installed on 2022-03-31 (4 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 
(20220329.1)
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions: mutter-common 42.0-1ubuntu1
  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/1967883/+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 1967883] [NEW] Application Icons missing from "Show Applications" screen

[Mark Smith]

Public bug reported:

>From a clean install of Ubuntu 22.04 beta, I have installed VLC and Firefox 
>(nightly) from Ubuntu Software (as snaps).
Neither of the two icons/graphics show up in the show applications window - 
either in the thumbnails of the groups I have created, or the expanded windows 
(see screenshots).

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: gnome-shell 42.0-1ubuntu1
ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
Uname: Linux 5.15.0-23-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu80
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Tue Apr  5 14:49:04 2022
DisplayManager: gdm3
InstallationDate: Installed on 2022-03-31 (4 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1)
RebootRequiredPkgs: Error: path contained symlinks.
RelatedPackageVersions: mutter-common 42.0-1ubuntu1
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug jammy

** Attachment added: "Screenshot from 2022-04-05 14-47-30.png"
   
https://bugs.launchpad.net/bugs/1967883/+attachment/5577331/+files/Screenshot%20from%202022-04-05%2014-47-30.png

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

Title:
  Application Icons missing from "Show Applications" screen

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  From a clean install of Ubuntu 22.04 beta, I have installed VLC and Firefox 
(nightly) from Ubuntu Software (as snaps).
  Neither of the two icons/graphics show up in the show applications window - 
either in the thumbnails of the groups I have created, or the expanded windows 
(see screenshots).

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 42.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Uname: Linux 5.15.0-23-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu80
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr  5 14:49:04 2022
  DisplayManager: gdm3
  InstallationDate: Installed on 2022-03-31 (4 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 
(20220329.1)
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions: mutter-common 42.0-1ubuntu1
  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/1967883/+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 1967471] [NEW] Artifacts when any window is being minimized to tray (on the second or more tries)

[Daniel Smith]

Public bug reported:

sudo update and sudo apt full-upgrade have been performed as well. Video
screen has been attached

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: gnome-shell 42.0-1ubuntu1
ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
Uname: Linux 5.15.0-23-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu80
Architecture: amd64
CasperMD5CheckResult: pass
CasperVersion: 1.468
CurrentDesktop: ubuntu:GNOME
Date: Fri Apr  1 07:36:46 2022
DisplayManager: gdm3
LiveMediaBuild: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=ru_RU.UTF-8
 SHELL=/bin/bash
RebootRequiredPkgs: Error: path contained symlinks.
RelatedPackageVersions: mutter-common 42.0-1ubuntu1
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug jammy

** Attachment added: "Запись экрана от 01.04.2022 07:34:56.webm"
   
https://bugs.launchpad.net/bugs/1967471/+attachment/5575524/+files/%D0%97%D0%B0%D0%BF%D0%B8%D1%81%D1%8C%20%D1%8D%D0%BA%D1%80%D0%B0%D0%BD%D0%B0%20%D0%BE%D1%82%2001.04.2022%2007%3A34%3A56.webm

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

Title:
  Artifacts when any window is being minimized to tray (on the second or
  more tries)

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  sudo update and sudo apt full-upgrade have been performed as well.
  Video screen has been attached

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 42.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Uname: Linux 5.15.0-23-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu80
  Architecture: amd64
  CasperMD5CheckResult: pass
  CasperVersion: 1.468
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr  1 07:36:46 2022
  DisplayManager: gdm3
  LiveMediaBuild: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions: mutter-common 42.0-1ubuntu1
  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/1967471/+subscriptions


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

[Desktop-packages] [Bug 1848942] Re: Freeze on opening font viewer

[James Paton-Smith]

Ubuntu 20.04.4
gnome-font-viewer 3.34.0-2

Have attached the output of 'journalctl -b 0' after seeing this issue twice in 
a row.
First time, the entire desktop froze and I had to switch TTY and force kill the 
process.
Second time, only gnome-font-viewer froze and eventually prompted to 'force 
quit'

Both occurred between about 14:30 and 14:55 11-03-2022

** Attachment added: "journalctl -b 0"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-font-viewer/+bug/1848942/+attachment/5567988/+files/fonts_issue.txt

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

Title:
  Freeze on opening font viewer

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

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

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-font-viewer/+bug/1848942/+subscriptions


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

[Desktop-packages] [Bug 1961625] [NEW] nvidia-340 340.108-0ubuntu5.20.04.1: nvidia-340 kernel module failed to build

[Howard Smith]

Public bug reported:

I dont know details. The system reported an error of some kind after the
system had been running for a few minutes. I am assuming it was an
update of the nvidia software, at least that was what it said. I don't
have details.

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: nvidia-340 340.108-0ubuntu5.20.04.1
ProcVersionSignature: Ubuntu 5.8.0-41.46~20.04.1-generic 5.8.18
Uname: Linux 5.8.0-41-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.20.11-0ubuntu27.16
Architecture: amd64
CasperMD5CheckResult: skip
DKMSKernelVersion: 5.13.0-30-generic
Date: Mon Feb 21 19:08:04 2022
InstallationDate: Installed on 2021-02-06 (380 days ago)
InstallationMedia: Ubuntu 20.04.2 LTS "Focal Fossa" - Release amd64 (20210204)
PackageVersion: 340.108-0ubuntu5.20.04.1
Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 
3.8.2-0ubuntu2
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.19.7ubuntu3
 apt  2.0.4
SourcePackage: nvidia-graphics-drivers-340
Title: nvidia-340 340.108-0ubuntu5.20.04.1: nvidia-340 kernel module failed to 
build
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: nvidia-graphics-drivers-340 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package focal

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

Title:
  nvidia-340 340.108-0ubuntu5.20.04.1: nvidia-340 kernel module failed
  to build

Status in nvidia-graphics-drivers-340 package in Ubuntu:
  New

Bug description:
  I dont know details. The system reported an error of some kind after
  the system had been running for a few minutes. I am assuming it was an
  update of the nvidia software, at least that was what it said. I don't
  have details.

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: nvidia-340 340.108-0ubuntu5.20.04.1
  ProcVersionSignature: Ubuntu 5.8.0-41.46~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-41-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  CasperMD5CheckResult: skip
  DKMSKernelVersion: 5.13.0-30-generic
  Date: Mon Feb 21 19:08:04 2022
  InstallationDate: Installed on 2021-02-06 (380 days ago)
  InstallationMedia: Ubuntu 20.04.2 LTS "Focal Fossa" - Release amd64 (20210204)
  PackageVersion: 340.108-0ubuntu5.20.04.1
  Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.4
  SourcePackage: nvidia-graphics-drivers-340
  Title: nvidia-340 340.108-0ubuntu5.20.04.1: nvidia-340 kernel module failed 
to build
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1961625/+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 1956612] [NEW] Play in this way

[Smith]

Public bug reported:

how to play DOS/Windows executable (application/x-ms-dos-executable)
Firstly, it's also a requirement that you must have pc or phone to play it!
For more Info: https://apkmortgage.com/disney-magic-kingdom-mod-apk-1/

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

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

Title:
  Play in this way

Status in nautilus package in Ubuntu:
  New

Bug description:
  how to play DOS/Windows executable (application/x-ms-dos-executable)
  Firstly, it's also a requirement that you must have pc or phone to play it!
  For more Info: https://apkmortgage.com/disney-magic-kingdom-mod-apk-1/

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1956612/+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 1939455] Re: Upgrading from 20.0.4-2ubuntu1 to 21.0.3-0ubuntu0.2~20.04.1 breaks vlc video output

[Tony Smith]

For the benefit of others I had a similar problem with Kaffeine 2.0.18
on Lubuntu 20.04.3, no video with DVB-T broadcast and only audio
working. The upgrade to 21.0.3 broke a system that was stable for about
a year. Also Kaffeine will crash changing channels. Running Kaffeine
from command prompt shows unable to decode video messages type messages.
Finally tracked down this ticket and down leveling to 20.0.4 solved
problem.

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

Title:
  Upgrading from 20.0.4-2ubuntu1 to 21.0.3-0ubuntu0.2~20.04.1 breaks vlc
  video output

Status in mesa package in Ubuntu:
  New

Bug description:
  Hello!

  As reported here
  https://bugs.launchpad.net/ubuntu/+source/vlc/+bug/1939447 upgrading
  mesa-vdpau-drivers package from 20.0.4-2ubuntu1 to
  21.0.3-0ubuntu0.2~20.04.1 breaks vlc video hardware acceleration.

  Thanks!

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: mesa-vdpau-drivers 21.0.3-0ubuntu0.2~20.04.1
  ProcVersionSignature: Ubuntu 5.4.0-80.90-generic 5.4.124
  Uname: Linux 5.4.0-80-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Wed Aug 11 02:21:08 2021
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Mullins [Radeon R4/R5 Graphics] 
[1002:9851] (rev 40) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Mullins [Radeon R4/R5 Graphics] 
[103c:81e5]
  MachineType: HP HP 245 G5 Notebook PC
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-80-generic 
root=UUID=e8820090-c9e5-4245-bcb4-92818bd91e34 ro quiet splash vt.handoff=7
  SourcePackage: mesa
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/21/2016
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.08
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 81E5
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 73.14
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.08:bd04/21/2016:svnHP:pnHP245G5NotebookPC:pvrType1ProductConfigId:rvnHP:rn81E5:rvrKBCVersion73.14:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5336AN G=N L=SMB B=HP S=245
  dmi.product.name: HP 245 G5 Notebook PC
  dmi.product.sku: Y9Q66PC#ACJ
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP
  modified.conffile..etc.default.apport:
   # set this to 0 to disable apport, or to 1 to enable it
   # you can temporarily override this with
   # sudo service apport start force_start=1
   enabled=0
  mtime.conffile..etc.default.apport: 2020-08-12T15:11:08.785042
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.105-3~20.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.2~20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1~20.04.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1939455/+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 1953525] [NEW] debian control should express a package dependency on ubuntu-advantage-tools

[Chad Smith]

Public bug reported:

./softwareproperties/gtk/utils.py relies on presence of ua command
delivered by ubuntu-advantage-tools. This deb should probably express at
least a Recommends on ubuntu-advantage-tools.

** Affects: software-properties (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  debian control should express a package dependency on ubuntu-
  advantage-tools

Status in software-properties package in Ubuntu:
  New

Bug description:
  ./softwareproperties/gtk/utils.py relies on presence of ua command
  delivered by ubuntu-advantage-tools. This deb should probably express
  at least a Recommends on ubuntu-advantage-tools.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1953525/+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 1952515] Re: QA Test Ubuntu 22.04 Gnome-shell Crashed

[Mark Smith]

Unable to reproduce in VB environment

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

Title:
  QA Test Ubuntu 22.04 Gnome-shell Crashed

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  QA Test Ubuntu 22.04 Gnome-shell Crashed.
  Apport could not send data.
  Reason: Invalid core dump /tmp/apport_core_k657r8ti is truncated.
  Daily Build 20211127
  Crash happened while testing Ubuntu Live Test.
  Opened terminal manually started Apport for this bug report.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 40.5-1ubuntu2
  ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
  Uname: Linux 5.13.0-19-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu73
  Architecture: amd64
  CasperMD5CheckResult: pass
  CasperVersion: 1.465
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Nov 27 16:00:24 2021
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.shell' b'welcome-dialog-last-shown-version' b"'40.5'"
   b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'us'), ('xkb', 
'au'), ('xkb', 'cm'), ('xkb', 'gb')]"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  LiveMediaBuild: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211127)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 40.5-1ubuntu3
  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/1952515/+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 1939732] Re: report availability of Ubuntu Advantage ESM services on unattached machines

[Chad Smith]

** Also affects: software-properties (Ubuntu Bionic)
   Importance: Undecided
   Status: New

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

Title:
  report availability of Ubuntu Advantage ESM services on unattached
  machines

Status in software-properties package in Ubuntu:
  Fix Committed
Status in software-properties source package in Bionic:
  New
Status in software-properties source package in Focal:
  Fix Committed
Status in software-properties source package in Hirsute:
  Fix Committed
Status in software-properties source package in Impish:
  Fix Committed

Bug description:
  [Impact]

    * Error messages emitted to software-properties-gtk console "[Errno 2] No 
such file or directory: '/var/lib/ubuntu-advantage/status.json'" due to 
incorrect expectation that status.json file is written when non-root runs `ua 
status`
    * This logic results in multiple `ua status` calls which each result in a 
network-egress to https://contracts.canonical.com on unattached machines which 
could result in delays in rendering  the GTK dialogs while awaiting a response.

  [Test Case]
  1. Install latest version of software-properties-gtk from -proposed
  cat > setup_proposed.sh 

[Desktop-packages] [Bug 1920836] Re: Show Extended Security Maintenence status

[Chad Smith]

# Impish desktop results: SUCCESS non-LTS has neither ESM-Infra nor ESM-Apps 
support or availability.
# so  1. it will not expose "Extend..." links to provide ESM information in 
Updates tab
# and 2. When attached no ESM information will be represented in Updates tab


1. # install proposed

$ cat > setup_proposed.sh  Fix Committed

** Changed in: software-properties (Ubuntu Impish)
   Importance: Undecided => High

** Changed in: software-properties (Ubuntu Impish)
 Assignee: (unassigned) => Robert Ancell (robert-ancell)

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

Title:
  Show Extended Security Maintenence status

Status in software-properties package in Ubuntu:
  Fix Released
Status in software-properties source package in Xenial:
  New
Status in software-properties source package in Bionic:
  Fix Committed
Status in software-properties source package in Focal:
  Fix Committed
Status in software-properties source package in Hirsute:
  Fix Committed
Status in software-properties source package in Impish:
  Fix Committed

Bug description:
  [Impact]
  There is not currently a graphical method of determining if a system is 
subscribed to [Extended Security Maintenance](https://ubuntu.com/security/esm) 
updates. This is resolved by adding some [new 
UI](https://wiki.ubuntu.com/SoftwareUpdates#Extended_Security_Maintenance) to 
the software properties application.

  [Test Case]
  1. Install latest version of Ubuntu advantage:
  $ sudo add-apt-repository ppa:ua-client/stable
  $ sudo apt update
  $ sudo apt upgrade
  2. Open Software Properties
  3. Go to Updates tab.

  Expected result:
  Information is shown that indicates if this system is using Extended Security 
Maintenance updates, when updates will supported until, and a link to upgrade 
to ESM.

  Observed result:
  No ESM information currently shown.

  [Where problems could occur]
  - Software properties could hit a bug getting a response from the ua app. The 
current code carefully checks if and what is returned, falling back to a safe 
default behavior.
  - Launching software properties could trigger a bug in the ua app.
  - Software properties could show incorrect information, causing confusion for 
the user. The solution uses 

[Desktop-packages] [Bug 1948667] Re: Elantech Touchpad not working on Fujitsu E5410

[Peter Smith]

additional info: the output of 
sudo acpidump | grep -C3 ELAN
yields
   39D60: 0D 41 54 4D 4C 32 39 35 32 00 5F 48 49 44 70 00  .ATML2952._HIDp.
   39D70: 48 49 44 32 70 0A 4A 42 41 44 52 70 0C 80 1A 06  HID2p.JBADRp
   39D80: 00 53 50 45 44 A4 00 A0 30 93 54 50 4C 54 0A 03  .SPED...0.TPLT..
   39D90: 70 0D 45 4C 41 4E 32 30 39 37 00 5F 48 49 44 70  p.ELAN2097._HIDp
   39DA0: 01 48 49 44 32 70 0A 10 42 41 44 52 70 0C 80 1A  .HID2p..BADRp...
   39DB0: 06 00 53 50 45 44 A4 00 A0 30 93 54 50 4C 54 0A  ..SPED...0.TPLT.
   39DC0: 04 70 0D 4E 54 52 47 30 30 30 31 00 5F 48 49 44  .p.NTRG0001._HID
--
   3A560: 54 0A 02 70 0D 41 54 4D 4C 32 39 35 32 00 5F 48  T..p.ATML2952._H
   3A570: 49 44 70 00 48 49 44 32 70 0A 4A 42 41 44 52 70  IDp.HID2p.JBADRp
   3A580: 0C 80 1A 06 00 53 50 45 44 A4 00 A0 30 93 54 50  .SPED...0.TP
   3A590: 4C 54 0A 03 70 0D 45 4C 41 4E 32 30 39 37 00 5F  LT..p.ELAN2097._
   3A5A0: 48 49 44 70 01 48 49 44 32 70 0A 10 42 41 44 52  HIDp.HID2p..BADR
   3A5B0: 70 0C 80 1A 06 00 53 50 45 44 A4 00 A0 30 93 54  p.SPED...0.T
   3A5C0: 50 4C 54 0A 04 70 0D 4E 54 52 47 30 30 30 31 00  PLT..p.NTRG0001.
--
   3B530: 50 4C 54 0A 02 70 0D 41 54 4D 4C 32 39 35 32 00  PLT..p.ATML2952.
   3B540: 5F 48 49 44 70 00 48 49 44 32 70 0A 4A 42 41 44  _HIDp.HID2p.JBAD
   3B550: 52 70 0C 80 1A 06 00 53 50 45 44 A4 00 A0 30 93  Rp.SPED...0.
   3B560: 54 50 4C 54 0A 03 70 0D 45 4C 41 4E 32 30 39 37  TPLT..p.ELAN2097
   3B570: 00 5F 48 49 44 70 01 48 49 44 32 70 0A 10 42 41  ._HIDp.HID2p..BA
   3B580: 44 52 70 0C 80 1A 06 00 53 50 45 44 A4 00 A0 30  DRp.SPED...0
   3B590: 93 54 50 4C 54 0A 04 70 0D 4E 54 52 47 30 30 30  .TPLT..p.NTRG000

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

Title:
  Elantech Touchpad not working on Fujitsu E5410

Status in xserver-xorg-input-libinput package in Ubuntu:
  New

Bug description:
  The Fujitsu E5410 (model type 5E14A1 according to the bottom sticker)
  is supplied with an Elantech(?) Touchpad. This apparently requires
  i2c_hid and does not properly work in Ubuntu 20.04. It seems also to
  interfere with the (internal) keyboard.

  Problem behavior:

  booting Ubuntu 20.04 with kernel 5.11.0-27:
  keyboard works, touchpad is not recognized.
  Running sudo modprobe i2c_hid manually from a terminal sometimes results in 
the touchpad working. Sometimes however the keyboard does not recognize any 
input anymore. After rebooting, approx 1/2 times the keyboard is not working 
anymore.

  Making sudo modprobe i2c_hid permanent via /etc/modules-load.d/
  permanently crashes the keyboard on startup such that it is impossible
  to log in.

  booting with kernel 5.14.0-1004-oem:
  sudo modprobe i2c_hid has no effect, the touchpad is never recognized. 
Booting with this kernel, 9/10 times the keyboard is not recognized at all and 
one cannot log in. Permanently loading the module via /etc/modules-load.d has 
no effect.

  booting with kernel 5.14.9-051409 (a mainline kernel from 
ppa:tuxinvader/lts-mainline ):
  modprobing the i2c_hid module has no effect. The keyboard works.

  probably not just xserver-xorg-input-libinput but also i2c_hid is
  affected. However w.r.t.
  https://wiki.ubuntu.com/DebuggingTouchpadDetection and without being
  able to further diagnose the problem I filed this bug against xserver-
  xorg-input-libinput.

  
  (likely) relevant output of cat /proc/bus/input/devices:

  I: Bus=0018 Vendor=04f3 Product=308a Version=0100
  N: Name="0X45 0X4C 0X41 0X4E 04F3:308A Touchpad"
  P: Phys=i2c-0X45 0X4C 0X41 0X4E 0X30 0X44 0X30 0X30 0X00:00
  S: Sysfs=/devices/pci:00/:00:15.3/i2c_designware.1/i2c-2/i2c-0X45 
0X4C 0X41 0X4E 0X30 0X44 0X30 0X30 0X00:00/0018:04F3:308A.0002/input/input26
  U: Uniq=
  H: Handlers=mouse2 event14 
  B: PROP=1
  B: EV=1b
  B: KEY=e520 3 0 0 0 0
  B: ABS=2e08003
  B: MSC=20

  
  I: Bus=0018 Vendor=04f3 Product=308a Version=0100
  N: Name="0X45 0X4C 0X41 0X4E 04F3:308A Mouse"
  P: Phys=i2c-0X45 0X4C 0X41 0X4E 0X30 0X44 0X30 0X30 0X00:00
  S: Sysfs=/devices/pci:00/:00:15.3/i2c_designware.1/i2c-2/i2c-0X45 
0X4C 0X41 0X4E 0X30 0X44 0X30 0X30 0X00:00/0018:04F3:308A.0002/input/input24
  U: Uniq=
  H: Handlers=mouse1 event13 
  B: PROP=0
  B: EV=17
  B: KEY=3 0 0 0 0
  B: REL=3
  B: MSC=10

  I: Bus=0011 Vendor=0001 Product=0001 Version=ab54
  N: Name="AT Translated Set 2 keyboard"
  P: Phys=isa0060/serio0/input0
  S: Sysfs=/devices/platform/i8042/serio0/input/input2
  U: Uniq=
  H: Handlers=sysrq kbd event2 leds 
  B: PROP=0
  B: EV=120013
  B: KEY=40200 3803078f800d001 fedfffef fffe
  B: MSC=10
  B: LED=7

  I: Bus=0019 Vendor= Product= Version=
  N: Name="Fujitsu FUJ02E3"
  P: Phys=FUJ02E3/input0
  S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/FUJ02E3:00/input/input7
  U: Uniq=
  H: Handlers=rfkill kbd event3 
  B: PROP=0
  B: 

[Desktop-packages] [Bug 1948667] [NEW] Elantech Touchpad not working on Fujitsu E5410

[Peter Smith]

Public bug reported:

The Fujitsu E5410 (model type 5E14A1 according to the bottom sticker) is
supplied with an Elantech(?) Touchpad. This apparently requires i2c_hid
and does not properly work in Ubuntu 20.04. It seems also to interfere
with the (internal) keyboard.

Problem behavior:

booting Ubuntu 20.04 with kernel 5.11.0-27:
keyboard works, touchpad is not recognized.
Running sudo modprobe i2c_hid manually from a terminal sometimes results in the 
touchpad working. Sometimes however the keyboard does not recognize any input 
anymore. After rebooting, approx 1/2 times the keyboard is not working anymore.

Making sudo modprobe i2c_hid permanent via /etc/modules-load.d/
permanently crashes the keyboard on startup such that it is impossible
to log in.

booting with kernel 5.14.0-1004-oem:
sudo modprobe i2c_hid has no effect, the touchpad is never recognized. Booting 
with this kernel, 9/10 times the keyboard is not recognized at all and one 
cannot log in. Permanently loading the module via /etc/modules-load.d has no 
effect.

booting with kernel 5.14.9-051409 (a mainline kernel from 
ppa:tuxinvader/lts-mainline ):
modprobing the i2c_hid module has no effect. The keyboard works.

probably not just xserver-xorg-input-libinput but also i2c_hid is
affected. However w.r.t.
https://wiki.ubuntu.com/DebuggingTouchpadDetection and without being
able to further diagnose the problem I filed this bug against xserver-
xorg-input-libinput.


(likely) relevant output of cat /proc/bus/input/devices:

I: Bus=0018 Vendor=04f3 Product=308a Version=0100
N: Name="0X45 0X4C 0X41 0X4E 04F3:308A Touchpad"
P: Phys=i2c-0X45 0X4C 0X41 0X4E 0X30 0X44 0X30 0X30 0X00:00
S: Sysfs=/devices/pci:00/:00:15.3/i2c_designware.1/i2c-2/i2c-0X45 0X4C 
0X41 0X4E 0X30 0X44 0X30 0X30 0X00:00/0018:04F3:308A.0002/input/input26
U: Uniq=
H: Handlers=mouse2 event14 
B: PROP=1
B: EV=1b
B: KEY=e520 3 0 0 0 0
B: ABS=2e08003
B: MSC=20


I: Bus=0018 Vendor=04f3 Product=308a Version=0100
N: Name="0X45 0X4C 0X41 0X4E 04F3:308A Mouse"
P: Phys=i2c-0X45 0X4C 0X41 0X4E 0X30 0X44 0X30 0X30 0X00:00
S: Sysfs=/devices/pci:00/:00:15.3/i2c_designware.1/i2c-2/i2c-0X45 0X4C 
0X41 0X4E 0X30 0X44 0X30 0X30 0X00:00/0018:04F3:308A.0002/input/input24
U: Uniq=
H: Handlers=mouse1 event13 
B: PROP=0
B: EV=17
B: KEY=3 0 0 0 0
B: REL=3
B: MSC=10

I: Bus=0011 Vendor=0001 Product=0001 Version=ab54
N: Name="AT Translated Set 2 keyboard"
P: Phys=isa0060/serio0/input0
S: Sysfs=/devices/platform/i8042/serio0/input/input2
U: Uniq=
H: Handlers=sysrq kbd event2 leds 
B: PROP=0
B: EV=120013
B: KEY=40200 3803078f800d001 fedfffef fffe
B: MSC=10
B: LED=7

I: Bus=0019 Vendor= Product= Version=
N: Name="Fujitsu FUJ02E3"
P: Phys=FUJ02E3/input0
S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/FUJ02E3:00/input/input7
U: Uniq=
H: Handlers=rfkill kbd event3 
B: PROP=0
B: EV=13
B: KEY=4 0 0 0 0 1810c00 30 0 0
B: MSC=10

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xserver-xorg-input-libinput 0.29.0-1
ProcVersionSignature: Ubuntu 5.11.0-27.29~20.04.1-generic 5.11.22
Uname: Linux 5.11.0-27-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.20
Architecture: amd64
BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log'
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Mon Oct 25 13:50:39 2021
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
InstallationDate: Installed on 2021-10-04 (21 days ago)
InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 04f2:b6a0 Chicony Electronics Co., Ltd FJ Camera
 Bus 001 Device 004: ID 8087:0026 Intel Corp. 
 Bus 001 Device 002: ID 046d:c077 Logitech, Inc. M105 Optical Mouse
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: FUJITSU CLIENT COMPUTING LIMITED LIFEBOOK E5410
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no username)
 XDG_RUNTIME_DIR=
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-27-generic 
root=UUID=521e4756-042b-473e-adce-11bbb047275b ro quiet splash vt.handoff=7
SourcePackage: xserver-xorg-input-libinput
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/06/2021
dmi.bios.release: 2.20
dmi.bios.vendor: FUJITSU CLIENT COMPUTING LIMITED
dmi.bios.version: Version 2.20
dmi.board.name: FJNB2D6
dmi.board.vendor: FUJITSU CLIENT COMPUTING LIMITED
dmi.board.version: A2
dmi.chassis.type: 10
dmi.chassis.vendor: FUJITSU CLIENT COMPUTING LIMITED
dmi.chassis.version: LIFEBOOK E5410
dmi.modalias: 
dmi:bvnFUJITSUCLIENTCOMPUTINGLIMITED:bvrVersion2.20:bd07/06/2021:br2.20:svnFUJITSUCLIENTCOMPUTINGLIMITED:pnLIFEBOOKE5410:pvr10601736746:rvnFUJITSUCLIENTCOMPUTINGLIMITED:rnFJNB2D6:rvrA2:cvnFUJITSUCLIENTCOMPUTINGLIMITED:ct10:cvrLIFEBOOKE5410:
dmi.product.family: LIFEBOOK-FTS
dmi.product.name: LIFEBOOK E5410
dmi.product.sku: SK00

[Desktop-packages] [Bug 1947627] [NEW] Sound > Output Device selection reverts to default after resuming from sleepng from

[Oliver Smith]

Public bug reported:

My Dell XPS 13 is connected to a Lenovo Thinkpad docking station.

By default the audio output is selected as the audio out from the
docking station.

I manually select the output device to be the XPS speakers.

After going into standby/suspend mode the audio output reverts to the
docking station audio out.

Expected behaviour: The selected audio output device settings would be
persistent across standby/suspend.

Potentially this may be expected to be persistent across power off/on or
disconnect/reconnect as other settings (eg number of displays, order and
orientation) are maintained.

ProblemType: Bug
DistroRelease: Ubuntu 21.04
Package: gnome-control-center 1:3.38.5-1ubuntu2
ProcVersionSignature: Ubuntu 5.11.0-37.41-generic 5.11.22
Uname: Linux 5.11.0-37-generic x86_64
ApportVersion: 2.20.11-0ubuntu65.3
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Mon Oct 18 20:58:55 2021
ExecutablePath: /usr/bin/gnome-control-center
InstallationDate: Installed on 2021-06-19 (121 days ago)
InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
ProcEnviron:
 LANGUAGE=en_GB:en
 PATH=(custom, user)
 XDG_RUNTIME_DIR=
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
SourcePackage: gnome-control-center
UpgradeStatus: No upgrade log present (probably fresh install)

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


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

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

Title:
  Sound > Output Device selection reverts to default after resuming from
  sleepng from

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

Bug description:
  My Dell XPS 13 is connected to a Lenovo Thinkpad docking station.

  By default the audio output is selected as the audio out from the
  docking station.

  I manually select the output device to be the XPS speakers.

  After going into standby/suspend mode the audio output reverts to the
  docking station audio out.

  Expected behaviour: The selected audio output device settings would be
  persistent across standby/suspend.

  Potentially this may be expected to be persistent across power off/on
  or disconnect/reconnect as other settings (eg number of displays,
  order and orientation) are maintained.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: gnome-control-center 1:3.38.5-1ubuntu2
  ProcVersionSignature: Ubuntu 5.11.0-37.41-generic 5.11.22
  Uname: Linux 5.11.0-37-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65.3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct 18 20:58:55 2021
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2021-06-19 (121 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1947627/+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 1939732] [NEW] report availability of Ubuntu Advantage ESM services on unattached machines

[Chad Smith]

Public bug reported:

Release: bionic/focal
Version: 0.96.24.32 (bionic)

Issue:
Software & Updates GTK UI doesn't report availability of UBuntu Advantage ESM 
Infra or ESM Apps services on unattached machines

Steps to repropduce:

Launch software-properties-gtk from the commandline.
See unexpected errors on the terminal

 No ua status file written:
[Errno 2] No such file or directory: '/var/lib/ubuntu-advantage/status.json'


Navigation to the "Updates" tab
See only:
Basic Security Maintenance
04/26/2023

Expected results:
See no error messages on terminal
See a link to the right of Basic Security Maintenance on the "Updates" tab that 
points to ESM info
Basic Security Maintenance  Extend...(links to  
ubuntu.com/security/esm)

** Affects: software-properties (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  report availability of Ubuntu Advantage ESM services on unattached
  machines

Status in software-properties package in Ubuntu:
  New

Bug description:
  Release: bionic/focal
  Version: 0.96.24.32 (bionic)

  Issue:
  Software & Updates GTK UI doesn't report availability of UBuntu Advantage ESM 
Infra or ESM Apps services on unattached machines

  Steps to repropduce:

  Launch software-properties-gtk from the commandline.
  See unexpected errors on the terminal

   No ua status file written:
  [Errno 2] No such file or directory: '/var/lib/ubuntu-advantage/status.json'

  
  Navigation to the "Updates" tab
  See only:
  Basic Security Maintenance
  04/26/2023

  Expected results:
  See no error messages on terminal
  See a link to the right of Basic Security Maintenance on the "Updates" tab 
that points to ESM info
  Basic Security Maintenance  Extend...(links to  
ubuntu.com/security/esm)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1939732/+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 1881712] Re: gnome-software says connection is metered while is not

[Mark Smith]

Same issue on 21.04

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

Title:
  gnome-software says connection is metered while is not

Status in gnome-software package in Ubuntu:
  Confirmed

Bug description:
  I open gnome-software and i see a message 'automatic updates paused' for my 
connection is metered but my connection is NOT metered.
  see attached screenshot. 
  corrado@corrado-HP-x4-gg-0525ebook-PC:~$ inxi -Fx
  System:Host: corrado-HP-x4-gg-0525ebook-PC Kernel: 5.4.0-26-generic 
x86_64 bits: 64 compiler: gcc v: 9.3.0 
 Desktop: Gnome 3.36.2 Distro: Ubuntu 20.10 (Groovy Gorilla) 
  Machine:   Type: Laptop System: Hewlett-Packard product: HP 250 G3 Notebook 
PC v: 0991100600087 
 serial:  
 Mobo: Hewlett-Packard model: 2211 v: 86.49 serial:  UEFI: Insyde v: F.36 
 date: 12/18/2014 
  Battery:   ID-1: BAT1 charge: 10.2 Wh condition: 16.4/16.4 Wh (100%) model: 
13-42 OA03031 status: Charging 
  CPU:   Topology: Dual Core model: Intel Core i5-4210U bits: 64 type: MT 
MCP arch: Haswell rev: 1 
 L2 cache: 3072 KiB 
 flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx 
bogomips: 19156 
 Speed: 1696 MHz min/max: 800/2700 MHz Core speeds (MHz): 1: 1697 
2: 1696 3: 1696 4: 1697 
  Graphics:  Device-1: Intel Haswell-ULT Integrated Graphics vendor: 
Hewlett-Packard driver: i915 v: kernel 
 bus ID: 00:02.0 
 Device-2: Suyin type: USB driver: uvcvideo bus ID: 1-1.5:3 
 Display: x11 server: X.Org 1.20.8 driver: modesetting unloaded: 
fbdev,vesa resolution: 1366x768~60Hz 
 OpenGL: renderer: Mesa DRI Intel HD Graphics 4400 (HSW GT2) v: 4.5 
Mesa 20.0.7 direct render: Yes 
  Audio: Device-1: Intel Haswell-ULT HD Audio vendor: Hewlett-Packard 
driver: snd_hda_intel v: kernel 
 bus ID: 00:03.0 
 Device-2: Intel 8 Series HD Audio vendor: Hewlett-Packard driver: 
snd_hda_intel v: kernel bus ID: 00:1b.0 
 Sound Server: ALSA v: k5.4.0-26-generic 
  Network:   Device-1: Realtek RTL810xE PCI Express Fast Ethernet vendor: 
Hewlett-Packard driver: r8169 v: kernel 
 port: 3000 bus ID: 08:00.0 
 IF: enp8s0 state: down mac: 5c:b9:01:06:ba:ce 
 Device-2: Ralink RT3290 Wireless 802.11n 1T/1R PCIe vendor: 
Hewlett-Packard driver: rt2800pci v: 2.3.0 
 port: 3000 bus ID: 09:00.0 
 IF: wlp9s0f0 state: up mac: ac:d1:b8:82:03:5d 
  Drives:Local Storage: total: 689.33 GiB used: 6.76 GiB (1.0%) 
 ID-1: /dev/sda vendor: Seagate model: ST500LT012-1DG142 size: 
465.76 GiB 
 ID-2: /dev/sdb vendor: SanDisk model: SSD PLUS 240GB size: 223.57 
GiB 
  Partition: ID-1: / size: 31.25 GiB used: 6.75 GiB (21.6%) fs: ext4 dev: 
/dev/sdb5 
  Swap:  ID-1: swap-1 type: partition size: 4.00 GiB used: 0 KiB (0.0%) 
dev: /dev/sda2 
  Sensors:   System Temperatures: cpu: 39.0 C mobo: 39.0 C 
 Fan Speeds (RPM): N/A 
  Info:  Processes: 236 Uptime: 49m Memory: 3.78 GiB used: 1.39 GiB (36.7%) 
Init: systemd runlevel: 5 Compilers: 
 gcc: 9.3.0 Shell: bash v: 5.0.16 inxi: 3.1.00 
  corrado@corrado-HP-x4-gg-0525ebook-PC:~$

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: gnome-software 3.36.0-0ubuntu3
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu36
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jun  2 08:57:28 2020
  ExecutablePath: /usr/bin/gnome-software
  InstallationDate: Installed on 2020-05-26 (6 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200525)
  InstalledPlugins:
   gnome-software-plugin-flatpak N/A
   gnome-software-plugin-snap3.36.0-0ubuntu3
  SourcePackage: gnome-software
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-04-21 (41 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200420)
  InstalledPlugins:
   gnome-software-plugin-flatpak N/A
   gnome-software-plugin-snap3.36.0-0ubuntu3
  Package: gnome-software 3.36.0-0ubuntu3
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34
  Tags:  focal
  Uname: Linux 5.4.0-33-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

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

-- 
Mailing list: 

[Desktop-packages] [Bug 1767431] Re: restore type-ahead find, again

[Rich Smith]

This is really annoying, counter-intuitive behaviour. At the very least
the old behaviour should be restorable by a setting.

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

Title:
  restore type-ahead find, again

Status in nautilus package in Ubuntu:
  Confirmed

Bug description:
  The dropping of the type-ahead find patch in 17.10 might deeply affect
  non-technical users, as pointed out, this is possibly a bad HCI
  design. As there is a patch exists from the Arch community[1], and the
  at least some people managed to patch it in 17.10[2], might it be
  possible to add such patch back before 18.04.1 so that it won't affect
  people upgraded from 16.04?

  [1]: https://aur.archlinux.org/nautilus-typeahead.git
  [2]: https://askubuntu.com/a/1002521

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1767431/+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 1885344] Re: nvidia-340 340.108-0ubuntu2: nvidia-340 kernel module failed to build (oem 5.6 kernel)

[Philip J. Smith]

Confirmed, using PPA kelebek333/nvidia-legacy works with my ancient GT216M 
[GeForce GT 230M].
Thank you Andrea (andrea-amoroso81).

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

Title:
  nvidia-340 340.108-0ubuntu2: nvidia-340 kernel module failed to build
  (oem 5.6 kernel)

Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Confirmed

Bug description:
  Nvidia kernel module fails to build with linux kernel 5.6.0. Exits
  with error code 2.

  Description:  Ubuntu 20.04 LTS
  Release:  20.04

  linux-image-unsigned-5.6.0-1018-oem:
Installed: 5.6.0-1018.18
Candidate: 5.6.0-1018.18
Version table:
   *** 5.6.0-1018.18 500
  500 http://archive.ubuntu.com/ubuntu focal-proposed/main amd64 
Packages
  100 /var/lib/dpkg/status

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: nvidia-340 340.108-0ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  Uname: Linux 5.4.0-40-generic x86_64
  NonfreeKernelModules: talpa_vfshook talpa_pedconnector talpa_pedevice 
talpa_vcdevice talpa_core talpa_linux talpa_syscallhook nvidia
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  DKMSKernelVersion: 5.6.0-1018-oem
  Date: Sat Jun 27 02:15:51 2020
  DuplicateSignature: 
dkms:nvidia-340:340.108-0ubuntu2:/var/lib/dkms/nvidia-340/340.108/build/nv-drm.c:54:25:
 error: implicit declaration of function ‘drm_pci_init’; did you mean 
‘drm_mm_init’? [-Werror=implicit-function-declaration]
  InstallationDate: Installed on 2020-04-24 (63 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  PackageVersion: 340.108-0ubuntu2
  Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.3
  SourcePackage: nvidia-graphics-drivers-340
  Title: nvidia-340 340.108-0ubuntu2: nvidia-340 kernel module failed to build
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1885344/+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 1885344] Re: nvidia-340 340.108-0ubuntu2: nvidia-340 kernel module failed to build (oem 5.6 kernel)

[Philip J. Smith]

Similar issue, during Ubuntu 20.04 update and upgrade at 14:48 UTC today
I got an error installing package nvidia-340 340.108-0ubuntu2. After
reboot, video flashes several times, can only get to CLI. I am new to
Linux; I have not taken any actions to correct the problem and get the
GUI to work. I captured _some_ of the error info...

Crash report 
Sorry, a problem occurred while installing software. 

- Package
nvidia-340 340.108-0ubuntu2 
- ProblemType 
Package
- Title 
nvidia-340 340.108-0ubuntu2: nvidia-340 kernel module failed to build 
- ApportVersion 
2.20.11-0ubuntu27.14 
- Date
Fri Jan 8 08:23:25 2021
- DistroRelease 
Ubuntu 20.04 
- Duplicateof 
https://bugs.launchpad.net/bugs/1885344 
- DuplicateSignature 
dkms:nvidia-340:340.108-0-ubuntu2:/var/lib/dkms/nvidia-340/340.108/build/nv-drm.c:54:25:
 error: implicit declaration of function 'drm_pci_init'; did you mean 
'drm_mm_init'? [-Werror=implicit-function-declaration]
- InstallationDate 
Installed on 2020-08-28 (132 days ago) 
- InstallationMedia 
Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)

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

Title:
  nvidia-340 340.108-0ubuntu2: nvidia-340 kernel module failed to build
  (oem 5.6 kernel)

Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Confirmed

Bug description:
  Nvidia kernel module fails to build with linux kernel 5.6.0. Exits
  with error code 2.

  Description:  Ubuntu 20.04 LTS
  Release:  20.04

  linux-image-unsigned-5.6.0-1018-oem:
Installed: 5.6.0-1018.18
Candidate: 5.6.0-1018.18
Version table:
   *** 5.6.0-1018.18 500
  500 http://archive.ubuntu.com/ubuntu focal-proposed/main amd64 
Packages
  100 /var/lib/dpkg/status

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: nvidia-340 340.108-0ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  Uname: Linux 5.4.0-40-generic x86_64
  NonfreeKernelModules: talpa_vfshook talpa_pedconnector talpa_pedevice 
talpa_vcdevice talpa_core talpa_linux talpa_syscallhook nvidia
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  DKMSKernelVersion: 5.6.0-1018-oem
  Date: Sat Jun 27 02:15:51 2020
  DuplicateSignature: 
dkms:nvidia-340:340.108-0ubuntu2:/var/lib/dkms/nvidia-340/340.108/build/nv-drm.c:54:25:
 error: implicit declaration of function ‘drm_pci_init’; did you mean 
‘drm_mm_init’? [-Werror=implicit-function-declaration]
  InstallationDate: Installed on 2020-04-24 (63 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  PackageVersion: 340.108-0ubuntu2
  Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.3
  SourcePackage: nvidia-graphics-drivers-340
  Title: nvidia-340 340.108-0ubuntu2: nvidia-340 kernel module failed to build
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1885344/+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 1855595] Re: CUPS fails to print to autodetected printers because of cups-browsed error

[Mark Smith]

Adding some cross-linking to help people who encounter this in the
future, and perhaps also help the devs:

This is discussed in the Ask Ubuntu post:
https://askubuntu.com/questions/1128164/no-suitable-destination-host-
found-by-cups-browsed

The solution there (which worked for me) is to `apt remove cups-browsed`
and add the printer manually.

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

Title:
  CUPS fails to print to autodetected printers because of cups-browsed
  error

Status in cups-filters package in Ubuntu:
  Confirmed

Bug description:
  When trying to autodetected IPP printers, print job stays in queue.

  lpstat -l:

  HP_LaserJet_CM1415fn_44A808_-23 erik 30720   So 08 Dez 2019 
15:50:20 CET
  Status: No suitable destination host found by cups-browsed.
  Alarme: resources-are-not-ready
  in Warteschlange eingereiht für HP_LaserJet_CM1415fn_44A808_

  Removing the print job, restarting cups-browsed with `service cups-
  browsed restart` followed by `service cups restart` enables printing
  for one print job; the next one fails again with the same issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: cups-browsed 1.25.13-1
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Uname: Linux 5.3.0-24-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu13
  Architecture: amd64
  CurrentDesktop: LXQt
  Date: Sun Dec  8 16:06:02 2019
  InstallationDate: Installed on 2019-10-19 (50 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191019)
  Lpstat:
   device for HP_LaserJet_CM1415fn_44A808_: 
implicitclass://HP_LaserJet_CM1415fn_44A808_/
   device for Samsung_C48x_Series_SEC84251900EE44_: 
implicitclass://Samsung_C48x_Series_SEC84251900EE44_/
  MachineType: Dell Inc. Latitude E6530
  Papersize: a4
  PpdFiles:
   Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/HP_LaserJet_CM1415fn_44A808_.ppd', 
'/etc/cups/ppd/Samsung_C48x_Series_SEC84251900EE44_.ppd'] failed with exit code 
2: grep: /etc/cups/ppd/HP_LaserJet_CM1415fn_44A808_.ppd: Permission denied
   grep: /etc/cups/ppd/Samsung_C48x_Series_SEC84251900EE44_.ppd: Permission 
denied
  ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_utwd0l@/vmlinuz-5.3.0-24-generic 
root=ZFS=rpool/ROOT/ubuntu_utwd0l ro quiet splash vt.handoff=1
  SourcePackage: cups-filters
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/30/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A22
  dmi.board.name: 07Y85M
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA22:bd11/30/2018:svnDellInc.:pnLatitudeE6530:pvr01:rvnDellInc.:rn07Y85M:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E6530
  dmi.product.sku: Latitude E6530
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/1855595/+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 1906507] [NEW] System Monitor File Systems capacity GUI ProgressBar partly off-screen (multiple displays)

[Ziggy Smith]

Public bug reported:

Very minor bug - see attached screenshot.

To Reproduce:
1. Open g-s-m in the larger of two displays
2. Navigate to the either the "Processes" or "Resources" tab
3. Move the g-s-m window to a smaller display
4. Navigate to the "File Systems" tab
5. File system capacity GUI ProgressBar should now be partly off-screen (see 
attached screenshot)

Gnome System Monitor version: 3.38.0-1
Ubuntu release: 20.10

ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: gnome-system-monitor 3.38.0-1
ProcVersionSignature: Ubuntu 5.8.0-29.31-generic 5.8.14
Uname: Linux 5.8.0-29-generic x86_64
ApportVersion: 2.20.11-0ubuntu50.2
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Wed Dec  2 21:12:09 2020
InstallationDate: Installed on 2020-11-20 (12 days ago)
InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
ProcEnviron:
 LANGUAGE=en_AU:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_AU.UTF-8
 SHELL=/bin/bash
SourcePackage: gnome-system-monitor
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug groovy

** Attachment added: "g-s-m_ProgressBar_partly_offscreen.png"
   
https://bugs.launchpad.net/bugs/1906507/+attachment/5440315/+files/g-s-m_ProgressBar_partly_offscreen.png

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

Title:
  System Monitor File Systems capacity GUI ProgressBar partly off-screen
  (multiple displays)

Status in gnome-system-monitor package in Ubuntu:
  New

Bug description:
  Very minor bug - see attached screenshot.

  To Reproduce:
  1. Open g-s-m in the larger of two displays
  2. Navigate to the either the "Processes" or "Resources" tab
  3. Move the g-s-m window to a smaller display
  4. Navigate to the "File Systems" tab
  5. File system capacity GUI ProgressBar should now be partly off-screen (see 
attached screenshot)

  Gnome System Monitor version: 3.38.0-1
  Ubuntu release: 20.10

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: gnome-system-monitor 3.38.0-1
  ProcVersionSignature: Ubuntu 5.8.0-29.31-generic 5.8.14
  Uname: Linux 5.8.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Dec  2 21:12:09 2020
  InstallationDate: Installed on 2020-11-20 (12 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  ProcEnviron:
   LANGUAGE=en_AU:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-system-monitor
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-system-monitor/+bug/1906507/+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 33072] Re: Pulling AC plug suspends computer

[Jan Smith]

This happens consistently every time on my laptop running Ubuntu 20.04.1 LTS.
I keep it running with the lid open and the AC power cable connected, when I 
unplug the cable Ubuntu auto-suspends (battery is well over 90%). Extremely 
annoying. 

The power settings are:
* Automatic suspend when on battery power

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

Title:
  Pulling AC plug suspends computer

Status in HAL:
  Fix Released
Status in gnome-power-manager package in Ubuntu:
  Fix Released
Status in hal package in Ubuntu:
  Fix Released
Status in gnome-power-manager package in Fedora:
  Fix Released

Bug description:
  g-p-m (I guess) immediately suspends when switching from AC to battery
  - even if the battery is full (as reported by g-p-m itself after
  unsuspension).

  This is almost always reproducible.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hal/+bug/33072/+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 1183735] Re: By default, Onboard keyboard cannot be moved through the screen

[Theodore R. Smith]

For me, I have dual monitors and for the life of me could not get
Launchpad's Onboard keyboard to my main monitor. It was also stuck on
the top of the screen, making it a major hinderence.

Arch Linux, Gnome 3.36.

It's also the only GUI app I have ever encountered which does not
respond to the Alt + Space keyboard shortcut to display Gnome's window
menubar, which I normally use to show toolbars, etc.

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

Title:
  By default, Onboard keyboard cannot be moved through the screen

Status in One Hundred Papercuts:
  Invalid
Status in onboard package in Ubuntu:
  Invalid

Bug description:
  
  HOW TO REPRODUCE
  
  - With the default configuration, try to move Onboard through the screen.

  *
  BEHAVIOUR
  *
  - EXPECTED: The keyboard to be movable.
  - REAL: The keyboard cannot be moved.

  ***
  WORK-AROUND
  ***
  1. Click on the "Papercuts" button.
  2. Click on the "Preferences" button.
  3. Go to the "Window" tab.
  4. Mark the "Show the window's decoration" check-box.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: onboard 0.99.0~alpha1~tr1190-0ubuntu1
  ProcVersionSignature: Ubuntu 3.8.0-21.32-generic 3.8.8
  Uname: Linux 3.8.0-21-generic x86_64
  ApportVersion: 2.9.2-0ubuntu8
  Architecture: amd64
  Date: Fri May 24 11:34:00 2013
  InstallationDate: Installed on 2013-05-21 (2 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MarkForUpload: True
  SourcePackage: onboard
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/hundredpapercuts/+bug/1183735/+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 1824874] Re: undismissable, unclickable authentication dialog left on screen (top-left corner) after policykit authentication [pushModal: invocation of begin_modal failed]

[Mark Smith]

ID = #3026

https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/3026

** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/-/issues #3026
   https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/3026

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

Title:
  undismissable, unclickable authentication dialog left on screen (top-
  left corner) after policykit authentication [pushModal: invocation of
  begin_modal failed]

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  In disco, when policykit prompted me for a password in order for
  update-manager to dispatch instructions to aptdaemon to perform
  package updates, the password dialog remained on the screen after I
  clicked 'authenticate'.

  The window is not clickable, it appears not to even be a window -
  mouse presses are received by the window underneath.  The exception is
  that the 'cancel' button is active and receives mouse events - but
  clicking it does nothing.

  This may be a gnome-shell issue rather than policykit.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: policykit-1 0.105-25
  ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1
  Uname: Linux 5.0.0-8-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr 15 13:14:33 2019
  InstallationDate: Installed on 2010-09-24 (3125 days ago)
  InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 
(20100816.1)
  SourcePackage: policykit-1
  UpgradeStatus: Upgraded to disco on 2019-04-11 (3 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1824874/+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 1849942] Re: 19.10 Gnome Settings and Tweak Tools Window Bar Bug

[John Smith]

I too have this behaviour, making gnome-tweaks very hard to use. I have
had it for some months, presumably since installing 19.10. It is still
there in 20.04. Could something be done to fix it?

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

Title:
  19.10 Gnome Settings and Tweak Tools Window Bar Bug

Status in gnome-control-center package in Ubuntu:
  Incomplete
Status in gnome-tweak-tool package in Ubuntu:
  Confirmed

Bug description:
  I upgraded from 19.04 to 19.10 and now there are some strange bugs with the 
Gnome Settings and the Tweak Tool:
  
https://drive.google.com/file/d/1PpxTRKOqrrPfNLC_0fLSXNZTrsOIWDxg/view?usp=sharing

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1849942/+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 1292398] Re: Second screen position isn't saved from one session to another

[Grant Smith]

This is the other xml file that does not work.

** Attachment added: "monitors-desired-config-will-not-load.xml"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1292398/+attachment/5361060/+files/monitors-desired-config-will-not-load.xml

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

Title:
  Second screen position isn't saved from one session to another

Status in elementary OS:
  Fix Released
Status in GNOME Settings Daemon:
  Incomplete
Status in GNOME Shell:
  Confirmed
Status in Mutter:
  Confirmed
Status in Ubuntu GNOME:
  Confirmed
Status in Ubuntu GNOME trusty series:
  Confirmed
Status in Ubuntu GNOME xenial series:
  Confirmed
Status in Ubuntu GNOME Flashback:
  Confirmed
Status in Unity:
  New
Status in gnome-settings-daemon package in Ubuntu:
  Triaged
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  (Noticed on Ubuntu 14.04 beta 1 GNOME)
  At work I have a second screen, which I prefer to virtually put on the left 
side of my laptop screen.
  Using gnome-control-center I can change the position of the second without 
problem.
  But when I disconnect the second screen (to work on another place) and then 
connect it again
  OR if I just power off the laptop and turn it on again,
  the second screen position is set back to the default right position.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: gnome-control-center 1:3.6.3-0ubuntu53
  ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6
  Uname: Linux 3.13.0-17-generic x86_64
  ApportVersion: 2.13.3-0ubuntu1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Mar 14 08:50:00 2014
  InstallationDate: Installed on 2014-03-01 (12 days ago)
  InstallationMedia: Ubuntu-GNOME 14.04 "Trusty Tahr" - Alpha amd64 (20140226)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_gnome-control-center: deja-dup 29.5-0ubuntu2

To manage notifications about this bug go to:
https://bugs.launchpad.net/elementaryos/+bug/1292398/+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 1292398] Re: Second screen position isn't saved from one session to another

[Grant Smith]

I tried testing what happens if I try a configuration with only one
monitor enabled. The log in screen has all three monitors on, but then
when I log in it properly disables two of them and the config loads as
it was when I logged out. Monitor 2 enabled with fractional scaling 1.5
and monitors 1 and 3 disabled.

I will attach the files of the working config and the config I want that
does not load.

After comparing the two XML files, my best guess as to what is going on
is that if there is more than one "" element then the
config will not load properly.

** Attachment added: "monitors-not-desired-config-will-load.xml"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1292398/+attachment/5361059/+files/monitors-not-desired-config-will-load.xml

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

Title:
  Second screen position isn't saved from one session to another

Status in elementary OS:
  Fix Released
Status in GNOME Settings Daemon:
  Incomplete
Status in GNOME Shell:
  Confirmed
Status in Mutter:
  Confirmed
Status in Ubuntu GNOME:
  Confirmed
Status in Ubuntu GNOME trusty series:
  Confirmed
Status in Ubuntu GNOME xenial series:
  Confirmed
Status in Ubuntu GNOME Flashback:
  Confirmed
Status in Unity:
  New
Status in gnome-settings-daemon package in Ubuntu:
  Triaged
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  (Noticed on Ubuntu 14.04 beta 1 GNOME)
  At work I have a second screen, which I prefer to virtually put on the left 
side of my laptop screen.
  Using gnome-control-center I can change the position of the second without 
problem.
  But when I disconnect the second screen (to work on another place) and then 
connect it again
  OR if I just power off the laptop and turn it on again,
  the second screen position is set back to the default right position.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: gnome-control-center 1:3.6.3-0ubuntu53
  ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6
  Uname: Linux 3.13.0-17-generic x86_64
  ApportVersion: 2.13.3-0ubuntu1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Mar 14 08:50:00 2014
  InstallationDate: Installed on 2014-03-01 (12 days ago)
  InstallationMedia: Ubuntu-GNOME 14.04 "Trusty Tahr" - Alpha amd64 (20140226)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_gnome-control-center: deja-dup 29.5-0ubuntu2

To manage notifications about this bug go to:
https://bugs.launchpad.net/elementaryos/+bug/1292398/+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 1292398] Re: Second screen position isn't saved from one session to another

[Grant Smith]

Hi Daniel,


I'm having this problem, so I tried the test you detailed in comment #147. Both 
XML files were identical and they also have the settings I want. Still when I 
log in the monitors are in the wrong place, orientation, scaling level, and 
primary monitor.

I'm using a fresh installation of Ubuntu 20.04, X11, and AMD open-source
drivers.

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

Title:
  Second screen position isn't saved from one session to another

Status in elementary OS:
  Fix Released
Status in GNOME Settings Daemon:
  Incomplete
Status in GNOME Shell:
  Confirmed
Status in Mutter:
  Confirmed
Status in Ubuntu GNOME:
  Confirmed
Status in Ubuntu GNOME trusty series:
  Confirmed
Status in Ubuntu GNOME xenial series:
  Confirmed
Status in Ubuntu GNOME Flashback:
  Confirmed
Status in Unity:
  New
Status in gnome-settings-daemon package in Ubuntu:
  Triaged
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  (Noticed on Ubuntu 14.04 beta 1 GNOME)
  At work I have a second screen, which I prefer to virtually put on the left 
side of my laptop screen.
  Using gnome-control-center I can change the position of the second without 
problem.
  But when I disconnect the second screen (to work on another place) and then 
connect it again
  OR if I just power off the laptop and turn it on again,
  the second screen position is set back to the default right position.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: gnome-control-center 1:3.6.3-0ubuntu53
  ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6
  Uname: Linux 3.13.0-17-generic x86_64
  ApportVersion: 2.13.3-0ubuntu1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Mar 14 08:50:00 2014
  InstallationDate: Installed on 2014-03-01 (12 days ago)
  InstallationMedia: Ubuntu-GNOME 14.04 "Trusty Tahr" - Alpha amd64 (20140226)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_gnome-control-center: deja-dup 29.5-0ubuntu2

To manage notifications about this bug go to:
https://bugs.launchpad.net/elementaryos/+bug/1292398/+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 1870748] Re: Authentication Window Stays Open

[Mark Smith]

Sorry, I should add that the pop-up window remained on top of all the others, 
so it wasn't hidden behind anything else before I went to bed. 
And although it was at the top, when I entered my password and the field went 
grey, the window remained visible, but if I clicked anywhere in the window, I 
actually clicked whatever was behind it.

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

Title:
  Authentication Window Stays Open

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  I left the Beta of Focal Fossa running overnight and when I logged in
  this morning, I found an open Authentication window with the message
  "To change software repository settings, you need to authenticate"
  (see attached screenshot).

  I enter my password and the password field grey out.

  The window stays persistent but is "invisible" to the mouse - i.e. if I click 
anywhere in it, it actually clicks the thing behind it. 
  The Cancel button does nothing.

  I had this same issue yesterday when actually running Software &
  Updates.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: software-properties-gtk 0.98.7
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr  4 09:55:33 2020
  InstallationDate: Installed on 2020-01-24 (70 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: software-properties
  UpgradeStatus: Upgraded to focal on 2020-04-03 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1870748/+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 1870748] Re: Authentication Window Stays Open

[Mark Smith]

Not at that time - I had just gone to bed. I had changed them earlier that day, 
and the error triggered. So I rebooted. This time the error came about without 
me touching it.
Journal output attached.
The bug doesn't appear to be triggered by any steps in Software-Updater


** Attachment added: "journal.txt"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1870748/+attachment/5347706/+files/journal.txt

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

Title:
  Authentication Window Stays Open

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  I left the Beta of Focal Fossa running overnight and when I logged in
  this morning, I found an open Authentication window with the message
  "To change software repository settings, you need to authenticate"
  (see attached screenshot).

  I enter my password and the password field grey out.

  The window stays persistent but is "invisible" to the mouse - i.e. if I click 
anywhere in it, it actually clicks the thing behind it. 
  The Cancel button does nothing.

  I had this same issue yesterday when actually running Software &
  Updates.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: software-properties-gtk 0.98.7
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr  4 09:55:33 2020
  InstallationDate: Installed on 2020-01-24 (70 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: software-properties
  UpgradeStatus: Upgraded to focal on 2020-04-03 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1870748/+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 1797734] Re: slow calculator startup

[Paul Smith]

Hey, if my assertion incentivizes someone to figure out how to do that,
I'm more than willing to admit I was wrong :).

The thing is, IMO "fast enough" for a desktop calculator is pretty darn
fast.  In my opinion the current integrated DEB version is already slow
enough to be frustrating, so there's plenty of work in this area without
even considering the issue of snaps.  People just don't expect to have
to wait for a calculator on their computer: isn't calculating the thing
that computers were built for and are best at?!

I'm not suggesting we should do something like waste users' memory by
preloading the calculator app just so it can be ready to display a
window quickly, though.  In reality probably not enough people use the
app often enough to justify that.

Cheers!

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

Title:
  slow calculator startup

Status in gnome-calculator package in Ubuntu:
  Confirmed
Status in ubuntu-meta package in Ubuntu:
  New

Bug description:
  The calculator starts very slowly. It's a tiny program, but it runs
  like a very big one. In previous versions of Ubuntu, the launch was
  normal, very fast.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-calculator (not installed)
  ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
  Uname: Linux 4.15.0-36-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct 14 08:40:06 2018
  InstallationDate: Installed on 2018-05-06 (160 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-calculator
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-calculator/+bug/1797734/+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 1797734] Re: slow calculator startup

[Paul Smith]

It is not physically possible to ever get a snap to start as fast as a
native application.  The entire purpose of a snap is that it uses its
own set of dependencies, which means that by definition it cannot share
those dependencies with other applications on the system, which means
that they must be loaded separately, which will take longer, use more
system resources, etc.

snaps should be used for applications which (a) are difficult to
package, and/or (b) want to be used across multiple versions where
prerequisites might change, and/or (c) snaps downsides are not as
relevant (for example, they are left running for longer periods of time
and are large enough that they aren't expected to start quickly, to
amortize the increased start time and resource usage).

None of those criteria hold true for a desktop calculator utility.  We
need to get to the point where I can hit the calculator button on the
keyboard and a calculator window appears virtually instantaneously.
gnome-calculator was always too slow to start, but now it's far slower:
it's moving in exactly the wrong direction.  Using it as a way to
experiment with snaps just gives both snaps and gnome-calculator a bad
reputation.

This bug is not trying to say "we must improve snap startup times".

This bug is trying to say "gnome-calculator is not an appropriate
application to be snapped and should be changed back to a native
application".

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

Title:
  slow calculator startup

Status in gnome-calculator package in Ubuntu:
  Confirmed

Bug description:
  The calculator starts very slowly. It's a tiny program, but it runs
  like a very big one. In previous versions of Ubuntu, the launch was
  normal, very fast.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-calculator (not installed)
  ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
  Uname: Linux 4.15.0-36-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct 14 08:40:06 2018
  InstallationDate: Installed on 2018-05-06 (160 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-calculator
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-calculator/+bug/1797734/+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 1797734] Re: slow calculator startup

[Paul Smith]

I'm not sure why the "is 2s too slow to start" is the question being
asked.  Who starts and stops their calculator multiple times in a row?
That's not a realistic use-case for the vast majority.

Most people need a calculator once a day or every few days, and a
desktop calculator is not an application people tend to leave running
for long periods like a browser or word processor.  They need to do a
quick bit of computation so they open the app, work in it for a few
minutes, then close it again.  Startup speed is, after correctness,
probably THE most important aspect of a utility like this.

The interesting number for gnome-calculator is the FIRST number: how
long it takes to be able to use the application from a cold start.  15s
is much closer to what I see, EVERY TIME I start gnome-calculator.

That's just... close to unusable.

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

Title:
  slow calculator startup

Status in gnome-calculator package in Ubuntu:
  Confirmed

Bug description:
  The calculator starts very slowly. It's a tiny program, but it runs
  like a very big one. In previous versions of Ubuntu, the launch was
  normal, very fast.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-calculator (not installed)
  ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
  Uname: Linux 4.15.0-36-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct 14 08:40:06 2018
  InstallationDate: Installed on 2018-05-06 (160 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-calculator
  UpgradeStatus: No upgrade log present (probably fresh install)

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