[Touch-packages] [Bug 2063221] Re: Drop libglib2.0-0 transitional package

2024-04-29 Thread Jeremy Bícha
** Description changed:

  Impact
  --
  apt can struggle with ordering when handling the massive Y2028 time_t 
transition when upgrading to Ubuntu 24.04 LTS.
  
  It was identified that dropping the libglib2.0-0 transitional package
  can help apt do things in the correct order.
  
+ Technically, Steve Langasek already removed libglib2.0-0 from noble
+ release just before release. This upload is necessary to ensure that we
+ don't accidentally bring it back.
+ 
  Test Case
  -
- Is libglib2.0-0 built?
+ 1. Is libglib2.0-0 built?
+ 
+ 2. Run rmadison libglib2.0-0
+ There should be 0 results for noble, noble-proposed, or noble-updates
+ 
+ 3. Ensure that libglib2.0-0 is removed during the upgrade from Ubuntu
+ 22.04 LTS to 24.04 LTS. Technically, ubuntu-release-upgrader is
+ currently set to disallow upgrades to 24.04 LTS. If this is still the
+ case when it is time to verify this SRU, you can manually substitute
+ jammy → noble in /etc/apt/sources.list for purposes of testing this
+ upgrade, probably in a VM since that's not the supported way to upgrade.
  
  Where Problems Could Occur
  --
  We have landed the change from this SRU in Debian Unstable and it 
successfully migrated to Debian Testing on April 27 as one of the first t64 
packages to migrate there.
  
  This SRU was recommended by Julian Klode, the apt maintainer for Debian
  and Ubuntu.
  
  The original transitional package was added by Simon McVittie in hopes
  that it would help apt be able to calculate the upgrade easier. At least
  in the Ubuntu Desktop 22.04 LTS → 24.04 LTS case, it looks like it was
  the opposite.
  
- Hmm, we can't actually drop libglib2.0-0 after release, can we?
- 
  Other Info
  --
  This is related to LP: #2061918 for the thunderbird deb to snap upgrade
  
  There are likely several other Launchpad bugs that can be resolved by
  this update and some other workarounds in other packages, like in the
  transitional thunderbird package.
  
  https://salsa.debian.org/gnome-team/glib/-/merge_requests/34

** Description changed:

  Impact
  --
  apt can struggle with ordering when handling the massive Y2028 time_t 
transition when upgrading to Ubuntu 24.04 LTS.
  
  It was identified that dropping the libglib2.0-0 transitional package
  can help apt do things in the correct order.
  
  Technically, Steve Langasek already removed libglib2.0-0 from noble
  release just before release. This upload is necessary to ensure that we
  don't accidentally bring it back.
  
  Test Case
  -
  1. Is libglib2.0-0 built?
  
  2. Run rmadison libglib2.0-0
  There should be 0 results for noble, noble-proposed, or noble-updates
  
  3. Ensure that libglib2.0-0 is removed during the upgrade from Ubuntu
  22.04 LTS to 24.04 LTS. Technically, ubuntu-release-upgrader is
  currently set to disallow upgrades to 24.04 LTS. If this is still the
  case when it is time to verify this SRU, you can manually substitute
  jammy → noble in /etc/apt/sources.list for purposes of testing this
  upgrade, probably in a VM since that's not the supported way to upgrade.
  
  Where Problems Could Occur
  --
- We have landed the change from this SRU in Debian Unstable and it 
successfully migrated to Debian Testing on April 27 as one of the first t64 
packages to migrate there.
- 
- This SRU was recommended by Julian Klode, the apt maintainer for Debian
- and Ubuntu.
- 
- The original transitional package was added by Simon McVittie in hopes
- that it would help apt be able to calculate the upgrade easier. At least
- in the Ubuntu Desktop 22.04 LTS → 24.04 LTS case, it looks like it was
- the opposite.
+ Doing an upload to not build a package that already does not exist in Ubuntu 
24.04 LTS should have no regression potential. The only other change in this 
SRU is bumping the Breaks version to ensure that the transitional libglib2.0-0 
is also removed for people who were using Ubuntu 24.04 LTS early. That also 
should not cause problems since the package was an empty transitional package 
for early Ubuntu 24.04 LTS users.
  
  Other Info
  --
  This is related to LP: #2061918 for the thunderbird deb to snap upgrade
  
  There are likely several other Launchpad bugs that can be resolved by
- this update and some other workarounds in other packages, like in the
- transitional thunderbird package.
+ removing the transitional package and some other workarounds in other
+ packages, like in the transitional thunderbird package.
  
  https://salsa.debian.org/gnome-team/glib/-/merge_requests/34
+ 
+ We have landed the removal in Debian Unstable and it successfully
+ migrated to Debian Testing on April 27 as one of the first t64 packages
+ to migrate there.
+ 
+ The removal was recommended by Julian Klode, the apt maintainer for
+ Debian and Ubuntu.
+ 
+ The original transitional package was added by Simon McVittie in hopes
+ that it would help apt be able to calculate the upgrade 

[Touch-packages] [Bug 2063221] Re: Drop libglib2.0-0 transitional package

2024-04-29 Thread Jeremy Bícha
** Description changed:

  Impact
  --
  apt can struggle with ordering when handling the massive Y2028 time_t 
transition when upgrading to Ubuntu 24.04 LTS.
  
  It was identified that dropping the libglib2.0-0 transitional package
  can help apt do things in the correct order.
  
  Test Case
  -
  Is libglib2.0-0 built?
  
+ Where Problems Could Occur
+ --
+ We have landed the change from this SRU in Debian Unstable and it 
successfully migrated to Debian Testing on April 27 as one of the first t64 
packages to migrate there.
+ 
+ This SRU was recommended by Julian Klode, the apt maintainer for Debian
+ and Ubuntu.
+ 
+ The original transitional package was added by Simon McVittie in hopes
+ that it would help apt be able to calculate the upgrade easier. At least
+ in the Ubuntu Desktop 22.04 LTS → 24.04 LTS case, it looks like it was
+ the opposite.
+ 
+ Hmm, we can't actually drop libglib2.0-0 after release, can we?
+ 
  Other Info
  --
  This is related to LP: #2061918 for the thunderbird deb to snap upgrade
  
  There are likely several other Launchpad bugs that can be resolved by
  this update and some other workarounds in other packages, like in the
  transitional thunderbird package.
  
  https://salsa.debian.org/gnome-team/glib/-/merge_requests/34

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

Title:
  Drop libglib2.0-0 transitional package

Status in glib2.0 package in Ubuntu:
  In Progress
Status in glib2.0 source package in Noble:
  Incomplete

Bug description:
  Impact
  --
  apt can struggle with ordering when handling the massive Y2028 time_t 
transition when upgrading to Ubuntu 24.04 LTS.

  It was identified that dropping the libglib2.0-0 transitional package
  can help apt do things in the correct order.

  Test Case
  -
  Is libglib2.0-0 built?

  Where Problems Could Occur
  --
  We have landed the change from this SRU in Debian Unstable and it 
successfully migrated to Debian Testing on April 27 as one of the first t64 
packages to migrate there.

  This SRU was recommended by Julian Klode, the apt maintainer for
  Debian and Ubuntu.

  The original transitional package was added by Simon McVittie in hopes
  that it would help apt be able to calculate the upgrade easier. At
  least in the Ubuntu Desktop 22.04 LTS → 24.04 LTS case, it looks like
  it was the opposite.

  Hmm, we can't actually drop libglib2.0-0 after release, can we?

  Other Info
  --
  This is related to LP: #2061918 for the thunderbird deb to snap upgrade

  There are likely several other Launchpad bugs that can be resolved by
  this update and some other workarounds in other packages, like in the
  transitional thunderbird package.

  https://salsa.debian.org/gnome-team/glib/-/merge_requests/34

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/2063221/+subscriptions


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


[Touch-packages] [Bug 2063221] Re: Drop libglib2.0-0 transitional package

2024-04-29 Thread Jeremy Bícha
** Tags removed: block-proposed

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

Title:
  Drop libglib2.0-0 transitional package

Status in glib2.0 package in Ubuntu:
  In Progress
Status in glib2.0 source package in Noble:
  In Progress

Bug description:
  Impact
  --
  apt can struggle with ordering when handling the massive Y2028 time_t 
transition when upgrading to Ubuntu 24.04 LTS.

  It was identified that dropping the libglib2.0-0 transitional package
  can help apt do things in the correct order.

  Test Case
  -
  Is libglib2.0-0 built?

  Other Info
  --
  This is related to LP: #2061918 for the thunderbird deb to snap upgrade

  There are likely several other Launchpad bugs that can be resolved by
  this update and some other workarounds in other packages, like in the
  transitional thunderbird package.

  https://salsa.debian.org/gnome-team/glib/-/merge_requests/34

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/2063221/+subscriptions


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


[Touch-packages] [Bug 2063221] Re: Drop libglib2.0-0 transitional package

2024-04-23 Thread Jeremy Bícha
** Tags added: block-proposed

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

Title:
  Drop libglib2.0-0 transitional package

Status in glib2.0 package in Ubuntu:
  In Progress
Status in glib2.0 source package in Noble:
  In Progress

Bug description:
  Impact
  --
  apt can struggle with ordering when handling the massive Y2028 time_t 
transition when upgrading to Ubuntu 24.04 LTS.

  It was identified that dropping the libglib2.0-0 transitional package
  can help apt do things in the correct order.

  Test Case
  -
  Is libglib2.0-0 built?

  Other Info
  --
  This is related to LP: #2061918 for the thunderbird deb to snap upgrade

  There are likely several other Launchpad bugs that can be resolved by
  this update and some other workarounds in other packages, like in the
  transitional thunderbird package.

  https://salsa.debian.org/gnome-team/glib/-/merge_requests/34

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/2063221/+subscriptions


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


[Touch-packages] [Bug 2063221] Re: Drop libglib2.0-0 transitional package

2024-04-23 Thread Jeremy Bícha
** Changed in: glib2.0 (Ubuntu)
   Status: Triaged => In Progress

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

Title:
  Drop libglib2.0-0 transitional package

Status in glib2.0 package in Ubuntu:
  In Progress

Bug description:
  Impact
  --
  apt can struggle with ordering when handling the massive Y2028 time_t 
transition when upgrading to Ubuntu 24.04 LTS.

  It was identified that dropping the libglib2.0-0 transitional package
  can help apt do things in the correct order.

  Test Case
  -
  Is libglib2.0-0 built?

  Other Info
  --
  This is related to LP: #2061918 for the thunderbird deb to snap upgrade

  There are likely several other Launchpad bugs that can be resolved by
  this update and some other workarounds in other packages, like in the
  transitional thunderbird package.

  https://salsa.debian.org/gnome-team/glib/-/merge_requests/34

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/2063221/+subscriptions


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


[Touch-packages] [Bug 2063221] [NEW] Drop libglib2.0-0 transitional package

2024-04-23 Thread Jeremy Bícha
Public bug reported:

Impact
--
apt can struggle with ordering when handling the massive Y2028 time_t 
transition when upgrading to Ubuntu 24.04 LTS.

It was identified that dropping the libglib2.0-0 transitional package
can help apt do things in the correct order.

Test Case
-
Is libglib2.0-0 built?

Other Info
--
This is related to LP: #2061918 for the thunderbird deb to snap upgrade

There are likely several other Launchpad bugs that can be resolved by
this update and some other workarounds in other packages, like in the
transitional thunderbird package.

https://salsa.debian.org/gnome-team/glib/-/merge_requests/34

** Affects: glib2.0 (Ubuntu)
 Importance: High
 Status: Triaged


** Tags: noble

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

Title:
  Drop libglib2.0-0 transitional package

Status in glib2.0 package in Ubuntu:
  Triaged

Bug description:
  Impact
  --
  apt can struggle with ordering when handling the massive Y2028 time_t 
transition when upgrading to Ubuntu 24.04 LTS.

  It was identified that dropping the libglib2.0-0 transitional package
  can help apt do things in the correct order.

  Test Case
  -
  Is libglib2.0-0 built?

  Other Info
  --
  This is related to LP: #2061918 for the thunderbird deb to snap upgrade

  There are likely several other Launchpad bugs that can be resolved by
  this update and some other workarounds in other packages, like in the
  transitional thunderbird package.

  https://salsa.debian.org/gnome-team/glib/-/merge_requests/34

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/2063221/+subscriptions


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


[Touch-packages] [Bug 2061316] Re: first screen refers to Noble Numbat (development branch)

2024-04-22 Thread Jeremy Bícha
I'm closing since base-files is now in noble-proposed and should migrate
to -release soon.

Here's the updated screenshot.

** Attachment added: "Screenshot from 2024-04-22 11-30-38.png"
   
https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/2061316/+attachment/5769448/+files/Screenshot%20from%202024-04-22%2011-30-38.png

** Changed in: base-files (Ubuntu Noble)
   Status: Triaged => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to base-files in Ubuntu.
https://bugs.launchpad.net/bugs/2061316

Title:
  first screen refers to Noble Numbat (development branch)

Status in base-files package in Ubuntu:
  Fix Released
Status in base-files source package in Noble:
  Fix Released

Bug description:
  While Noble is still in development and this screen is currently
  accurate, what will make it change to say Ubuntu 24.04? This should be
  done by the end of the week / early next week as we will be building
  candidate images for the final release.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/2061316/+subscriptions


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


[Touch-packages] [Bug 2062115] Re: Connected Google account, but Drive is not shown

2024-04-19 Thread Jeremy Bícha
The extra info in your original bug report says that your install was
originally with Ubuntu 20.04 LTS but there is no upgrade log for
upgrading to Ubuntu 24.04 LTS which I think means that you did not use
update-manager or do-release-upgrade to do the upgrade.

I don't know if that affects how gnome-online-accounts is working for
you. I was able to add my Google account to GNOME Online Accounts
successfully and it shows up in my Nautilus file browser in the left
sidebar in the second section from the top (listed after Trash).

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

Title:
  Connected Google account, but Drive is not shown

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

Bug description:
  After the recent updates of Ubuntu 24.04 Noble Numbat, Nautilus is
  unable to access Google Drive: it is not shown. I cannot find any
  error message in the logs.

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: gnome-online-accounts 3.50.0-4ubuntu1
  ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1
  Uname: Linux 6.8.0-22-generic x86_64
  ApportVersion: 2.28.0-0ubuntu1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr 18 06:56:05 2024
  InstallationDate: Installed on 2023-07-05 (288 days ago)
  InstallationMedia: Ubuntu 20.04.6 LTS "Focal Fossa" - Release amd64 (20230316)
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  SourcePackage: gnome-online-accounts
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.init.d.apport: [modified]
  mtime.conffile..etc.init.d.apport: 2024-02-22T15:20:00

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


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


[Touch-packages] [Bug 2062377] Re: Ubuntu 24.04. Xorg crash when dmz-white cursor is selected

2024-04-18 Thread Jeremy Bícha
** Package changed: xorg (Ubuntu) => mutter (Ubuntu)

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/2062377

Title:
  Ubuntu 24.04. Xorg crash when dmz-white cursor is selected

Status in mutter package in Ubuntu:
  New

Bug description:
  1)Go to xorg
  2)Download Gnome Tweak Tool
  3)Select DMZ-white
  4)crash from the system

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: xorg 1:7.7+23ubuntu3
  ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1
  Uname: Linux 6.8.0-22-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
  .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
  .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  535.161.07  Sat Feb 17 
22:55:48 UTC 2024
   GCC version:
  ApportVersion: 2.28.0-0ubuntu1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr 18 17:38:02 2024
  DistUpgraded: Fresh install
  DistroCodename: noble
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Subsystem: Acer Incorporated [ALI] GA107M [GeForce RTX 3050 Ti Mobile] 
[1025:1524]
   Advanced Micro Devices, Inc. [AMD/ATI] Lucienne [1002:164c] (rev c2) 
(prog-if 00 [VGA controller])
 Subsystem: Acer Incorporated [ALI] Lucienne [1025:1524]
  InstallationDate: Installed on 2024-04-17 (1 days ago)
  InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Beta amd64 (20240417.2)
  MachineType: Acer Aspire A715-42G
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-22-generic 
root=UUID=12cf9ac8-f034-465e-92e4-0c64e47e2350 ro quiet splash vt.handoff=7
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/19/2021
  dmi.bios.release: 1.2
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.02
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Azalea_CAS
  dmi.board.vendor: LN
  dmi.board.version: V1.02
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.02
  dmi.ec.firmware.release: 1.2
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.02:bd02/19/2021:br1.2:efr1.2:svnAcer:pnAspireA715-42G:pvrV1.02:rvnLN:rnAzalea_CAS:rvrV1.02:cvnAcer:ct10:cvrV1.02:sku:
  dmi.product.family: Aspire 7
  dmi.product.name: Aspire A715-42G
  dmi.product.sku: 
  dmi.product.version: V1.02
  dmi.sys.vendor: Acer
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.120-2build1
  version.libgl1-mesa-dri: libgl1-mesa-dri 24.0.5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.11-2ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:22.0.0-1build1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1build1
  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/mutter/+bug/2062377/+subscriptions


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


[Touch-packages] [Bug 2062115] Re: Connected Google account, but Drive is not shown

2024-04-18 Thread Jeremy Bícha
I believe there is an upgrade issue where you need to reauthenticate in
Settings > Online Accounts after upgrading to gnome-online-accounts
3.49/3.50 (which will happen when upgrading to Ubuntu 24.04 LTS).

Could you check if this fixes your issue? If it does, we can use this
bug to track that upgrade issue.

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

Title:
  Connected Google account, but Drive is not shown

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

Bug description:
  After the recent updates of Ubuntu 24.04 Noble Numbat, Nautilus is
  unable to access Google Drive: it is not shown. I cannot find any
  error message in the logs.

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: gnome-online-accounts 3.50.0-4ubuntu1
  ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1
  Uname: Linux 6.8.0-22-generic x86_64
  ApportVersion: 2.28.0-0ubuntu1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr 18 06:56:05 2024
  InstallationDate: Installed on 2023-07-05 (288 days ago)
  InstallationMedia: Ubuntu 20.04.6 LTS "Focal Fossa" - Release amd64 (20230316)
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  SourcePackage: gnome-online-accounts
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.init.d.apport: [modified]
  mtime.conffile..etc.init.d.apport: 2024-02-22T15:20:00

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


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


[Touch-packages] [Bug 2061118] Re: Rendering issues in vmware with 3d on (GTK ngl backend)

2024-04-17 Thread Jeremy Bícha
(The latest version of the Ubuntu Desktop installer installs all
available updates at the end of the install. It's a nice feature in
cases like this.)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded 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/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1986450] Re: Visual artifact 1px vertical white line right side of the wallpaper

2024-04-17 Thread Jeremy Bícha
Ambiance/Radiance are basically unmaintained so if there's a bug it
would probably be easier for you to propose a fix then trying to find
someone else to do it.

If you have concerns about the extension, I suggest filing an upstream issue:
https://gitlab.com/rastersoft/desktop-icons-ng/-/issues

** Summary changed:

- Visual artifact 1px vertical white line right side of the wallpaper
+ Visual artifact 1px vertical white line right side of the wallpaper with 
Ambiance/Radiance

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu.
https://bugs.launchpad.net/bugs/1986450

Title:
  Visual artifact 1px vertical white line right side of the wallpaper
  with Ambiance/Radiance

Status in gnome-shell package in Ubuntu:
  New
Status in gnome-shell-extension-desktop-icons-ng package in Ubuntu:
  New
Status in ubuntu-themes package in Ubuntu:
  New

Bug description:
  After manually upgrading from 20.04 LTS to 22.04.1 LTS I find that
  there is a 1px wide vertical white line on the desktop that appears
  whenever an application has focus. It is on the right side of the
  monitor, covering the background wallpaper but not the menu.

  Workaround: in Displays, change scale to something else than 100% and then 
change back to 100%. That white vertical line will stay at the former 100% 
window size location until the Settings window is closed. It disappears when 
the Settings is closed.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2018-04-27 (1570 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Package: gnome-shell 42.2-0ubuntu0.2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39
  RelatedPackageVersions: mutter-common 42.2-0ubuntu1
  Tags:  wayland-session jammy
  Uname: Linux 5.15.0-46-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo www-data
  _MarkForUpload: True

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


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


[Touch-packages] [Bug 1986450] Re: Visual artifact 1px vertical white line right side of the wallpaper

2024-04-17 Thread Jeremy Bícha
Wow, I didn't realize that people were still trying to use Ambiance and
Radiance (from source package ubuntu-themes) with Ubuntu 24.04 LTS.

Would you like to submit a patch and subscribe ubuntu-sponsors?

** Package changed: light-themes (Ubuntu) => ubuntu-themes (Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu.
https://bugs.launchpad.net/bugs/1986450

Title:
  Visual artifact 1px vertical white line right side of the wallpaper

Status in gnome-shell package in Ubuntu:
  New
Status in gnome-shell-extension-desktop-icons-ng package in Ubuntu:
  New
Status in ubuntu-themes package in Ubuntu:
  New

Bug description:
  After manually upgrading from 20.04 LTS to 22.04.1 LTS I find that
  there is a 1px wide vertical white line on the desktop that appears
  whenever an application has focus. It is on the right side of the
  monitor, covering the background wallpaper but not the menu.

  Workaround: in Displays, change scale to something else than 100% and then 
change back to 100%. That white vertical line will stay at the former 100% 
window size location until the Settings window is closed. It disappears when 
the Settings is closed.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2018-04-27 (1570 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Package: gnome-shell 42.2-0ubuntu0.2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39
  RelatedPackageVersions: mutter-common 42.2-0ubuntu1
  Tags:  wayland-session jammy
  Uname: Linux 5.15.0-46-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo www-data
  _MarkForUpload: True

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


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


[Touch-packages] [Bug 2061118] Re: Rendering issues in vmware with 3d on (GTK ngl backend)

2024-04-17 Thread Jeremy Bícha
I was unable to complete the VMWare Workstation Player 17 install on a
Ubuntu 24.04 LTS host even though there is a Linux installer.

Note that this bug report says that the host is Windows 11.

Similarly, I was able to install VirtualBox on a Ubuntu 24.04 LTS host
but was unable to duplicate https://launchpad.net/bugs/2061584 . I
suspect that it happens on a Windows 11 host because I have heard
reports of it affecting someone with a Windows 11 host with Intel
graphics (no Nvidia).

I have other priority work I need to do today, but someone interested in
trying to duplicate this bug should check if it happens with a Windows
11 host.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded 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/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 2054908] Re: gpg-wks-server pulls in postfix

2024-04-15 Thread Jeremy Bícha
*** This bug is a duplicate of bug 2060578 ***
https://bugs.launchpad.net/bugs/2060578

** This bug has been marked a duplicate of bug 2060578
   postfix installed during release upgrade to Noble

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/2054908

Title:
  gpg-wks-server pulls in postfix

Status in Auto Package Testing:
  Fix Released
Status in apt package in Ubuntu:
  Invalid
Status in gnupg2 package in Ubuntu:
  Won't Fix
Status in munin package in Ubuntu:
  Invalid

Bug description:
  Example 1
  
  I did a sudo apt dist-upgrade today on my developer machine running Ubuntu 
Desktop 24.04 LTS and it surprisingly pulled in postfix.

  I did not built this into a full reproducible test case because I
  found another test case…

  Example 2
  
  munin's autopkgtests are now failing because postfix is now unexpectedly 
being installed.

  https://autopkgtest.ubuntu.com/packages/munin/noble/amd64

  Other Info
  
  gnupg2's changelog indicates that there was an attempt to avoid this 
misbehavior by having gnupg only Suggest gpg-wks-server. In fact, there is 
**nothing** in Ubuntu 24.04 LTS that Depends or Recommends gpg-wks-server.

  I added a munin bug task as a pointer in case anyone wonder's about
  the autopkgtest regression but I don't believe munin needs any
  changes.

To manage notifications about this bug go to:
https://bugs.launchpad.net/auto-package-testing/+bug/2054908/+subscriptions


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


[Touch-packages] [Bug 2061118] Re: Rendering issues in vmware with 3d on (GTK ngl backend)

2024-04-15 Thread Jeremy Bícha
I have split VirtualBox to a separate issue,
https://launchpad.net/bugs/2061584 because we believe the VMWare issue
is fixed with mesa 24.0.5-1ubuntu1 in noble-proposed.

** Summary changed:

- Rendering issues in vmware/virtualbox with 3d on (GTK ngl backend)
+ Rendering issues in vmware with 3d on (GTK ngl backend)

** Changed in: gtk4 (Ubuntu Noble)
   Status: Triaged => Invalid

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

** No longer affects: open-vm-tools (Ubuntu)

** No longer affects: open-vm-tools (Ubuntu Noble)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded 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 Committed
Status in gtk4 source package in Noble:
  Invalid
Status in mesa source package in Noble:
  Fix Committed

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/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 2061584] [NEW] Rendering issues in VirtualBox with 3d on (GTK ngl backend)

2024-04-15 Thread Jeremy Bícha
Public bug reported:

GTK4 apps are rendering very badly with Ubuntu 24.04 LTS Beta when ran
in VirtualBox.

This includes the Welcome to Ubuntu app (gnome-initial-setup), gnome-
text-editor, and drawing the background (which uses gnome-shell-
extension-desktop-icons-ng on Ubuntu).

This issue was triggered by GTK4's switch to ngl as the default renderer
instead of gl.

However, some other similar issues (LP: #2061118, LP: #2060679) are
being fixed in mesa instead of in gtk4 itself.

** Affects: gtk
 Importance: Unknown
 Status: Unknown

** Affects: mesa
 Importance: Unknown
 Status: Unknown

** Affects: gtk4 (Ubuntu)
 Importance: High
 Status: Triaged

** Affects: mesa (Ubuntu)
 Importance: High
 Status: Triaged

** Affects: gtk4 (Ubuntu Noble)
 Importance: High
 Status: Triaged

** Affects: mesa (Ubuntu Noble)
 Importance: High
 Status: Triaged


** Tags: iso-testing noble

** Also affects: gtk4 (Ubuntu Noble)
   Importance: High
   Status: Triaged

** Bug watch added: gitlab.gnome.org/GNOME/gtk/-/issues #6542
   https://gitlab.gnome.org/GNOME/gtk/-/issues/6542

** Also affects: gtk via
   https://gitlab.gnome.org/GNOME/gtk/-/issues/6542
   Importance: Unknown
   Status: Unknown

** Description changed:

  GTK4 apps are rendering very badly with Ubuntu 24.04 LTS Beta when ran
  in VirtualBox.
  
  This includes the Welcome to Ubuntu app (gnome-initial-setup), gnome-
  text-editor, and drawing the background (which uses gnome-shell-
  extension-desktop-icons-ng on Ubuntu).
+ 
+ This issue was triggered by GTK4's switch to ngl as the default renderer
+ instead of gl.
+ 
+ However, some other similar issues (LP: #2061118, LP: #2060679) are
+ being fixed in mesa instead of in gtk4 itself.

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

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

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

** Bug watch added: gitlab.freedesktop.org/mesa/mesa/-/issues #11008
   https://gitlab.freedesktop.org/mesa/mesa/-/issues/11008

** Also affects: mesa via
   https://gitlab.freedesktop.org/mesa/mesa/-/issues/11008
   Importance: Unknown
   Status: Unknown

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/2061584

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

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

Bug description:
  GTK4 apps are rendering very badly with Ubuntu 24.04 LTS Beta when ran
  in VirtualBox.

  This includes the Welcome to Ubuntu app (gnome-initial-setup), gnome-
  text-editor, and drawing the background (which uses gnome-shell-
  extension-desktop-icons-ng on Ubuntu).

  This issue was triggered by GTK4's switch to ngl as the default
  renderer instead of gl.

  However, some other similar issues (LP: #2061118, LP: #2060679) are
  being fixed in mesa instead of in gtk4 itself.

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


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


[Touch-packages] [Bug 2060679] Re: No icons for gtk4 applications under noble

2024-04-15 Thread Jeremy Bícha
** Changed in: mesa (Ubuntu Noble)
   Status: In Progress => Fix Committed

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/2060679

Title:
  No icons for gtk4 applications under noble

Status in mesa package in Ubuntu:
  Fix Committed
Status in mesa source package in Noble:
  Fix Committed

Bug description:
  While testing the Ubuntu noble (24.04) desktop for Raspberry Pi beta,
  I noticed that all GTK4 applications appear to be missing various
  icons. All lack the minimize / maximize / close icons (which are left
  as three empty circles on the window), and others lack icons within
  the windows, e.g. on various controls like radio buttons, or folder
  icons in nautilus. GTK3 applications appear unaffected. I'll attach
  some screenshots demonstrating the issue.

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


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


[Touch-packages] [Bug 2060009] Re: mesa 24.0.3-1ubuntu3 breaks OpenGL applications on amdgpu

2024-04-15 Thread Jeremy Bícha
** Changed in: mesa (Ubuntu)
   Status: In Progress => Fix Committed

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/2060009

Title:
  mesa 24.0.3-1ubuntu3 breaks OpenGL applications on amdgpu

Status in mesa package in Ubuntu:
  Fix Committed

Bug description:
  With mesa 24.0.3-1ubuntu3 OpenSCAD does not work correctly on AMD GPUs.
  Cf. https://github.com/openscad/openscad/issues/5072

  According to OpenSCAD maintainers this was a bug fixed in Mesa-24.0.4. Cf. 
https://docs.mesa3d.org/relnotes/24.0.4.html
  ---
  ProblemType: Bug
  ApportVersion: 2.28.0-0ubuntu1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: KDE
  DistUpgraded: Fresh install
  DistroCodename: noble
  DistroRelease: Ubuntu 24.04
  DistroVariant: ubuntu
  DkmsStatus:
   fwts-efi-runtime-dkms/24.01.00, 6.8.0-11-generic, x86_64: installed 
(WARNING! Diff between built and installed module!)
   fwts-efi-runtime-dkms/24.01.00, 6.8.0-20-generic, x86_64: installed 
(WARNING! Diff between built and installed module!)
  DpkgLog:

  ExtraDebuggingInterest: No
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / 
Radeon Vega Mobile Series] [1002:15dd] (rev c4) (prog-if 00 [VGA controller])
     Subsystem: Lenovo Raven Ridge [Radeon Vega Series / Radeon Vega Mobile 
Series] [17aa:506f]
  InstallationDate: Installed on 2021-07-01 (1006 days ago)
  InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 003 Device 003: ID 04f2:b604 Chicony Electronics Co., Ltd Integrated 
Camera (1280x720@30)
   Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  MachineType: LENOVO 20KV0008GE
  Package: mesa (not installed)
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.8.0-20-generic 
root=/dev/mapper/vgubuntu-root ro
  ProcVersionSignature: Ubuntu 6.8.0-20.20-generic 6.8.1
  Tags: noble ubuntu regression reproducible
  Uname: Linux 6.8.0-20-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip libvirt lpadmin lxd plugdev sambashare 
sbuild sispmctl sudo
  _MarkForUpload: True
  dmi.bios.date: 02/08/2023
  dmi.bios.release: 1.63
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R0UET83W (1.63 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20KV0008GE
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.63
  dmi.modalias: 
dmi:bvnLENOVO:bvrR0UET83W(1.63):bd02/08/2023:br1.63:efr1.63:svnLENOVO:pn20KV0008GE:pvrThinkPadE585:rvnLENOVO:rn20KV0008GE:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20KV_BU_Think_FM_ThinkPadE585:
  dmi.product.family: ThinkPad E585
  dmi.product.name: 20KV0008GE
  dmi.product.sku: LENOVO_MT_20KV_BU_Think_FM_ThinkPad E585
  dmi.product.version: ThinkPad E585
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.120-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 24.0.3-1ubuntu3
  version.libgl1-mesa-glx: libgl1-mesa-glx 23.1.3-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.11-2ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:22.0.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

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


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


[Touch-packages] [Bug 2061118] Re: Rendering issues in vmware/virtualbox with 3d on (GTK ngl backend)

2024-04-13 Thread Jeremy Bícha
** Package changed: gnome-shell (Ubuntu Noble) => gtk4 (Ubuntu Noble)

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

** Bug watch added: gitlab.freedesktop.org/mesa/mesa/-/issues #10901
   https://gitlab.freedesktop.org/mesa/mesa/-/issues/10901

** Also affects: mesa via
   https://gitlab.freedesktop.org/mesa/mesa/-/issues/10901
   Importance: Unknown
   Status: Unknown

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

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

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/2061118

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

Status in GTK+:
  Fix Released
Status in Mesa:
  Unknown
Status in gtk4 package in Ubuntu:
  Triaged
Status in mesa package in Ubuntu:
  Triaged
Status in open-vm-tools package in Ubuntu:
  Invalid
Status in gtk4 source package in Noble:
  Triaged
Status in mesa source package in Noble:
  Triaged
Status in open-vm-tools source package in Noble:
  Invalid

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/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 2060813] Re: Upgrade UPower to 1.90.3 to lower cpu and disk usage

2024-04-11 Thread Jeremy Bícha
This bug was fixed in the package upower - 1.90.3-1

---
upower (1.90.3-1) unstable; urgency=medium

  * New upstream version 1.90.3
  * Drop patches, merged upstream
  * Bump Build-Depends on meson to (>= 0.60.0) and libglib2.0-dev to (>= 2.66)
as per meson.build
  * Switch Build-Depends on pkg-config to pkgconf
  * Bump Standards-Version to 4.7.0

 -- Michael Biebl   Mon, 08 Apr 2024 09:42:45 +0200

** Changed in: upower (Ubuntu)
   Status: Triaged => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to upower in Ubuntu.
https://bugs.launchpad.net/bugs/2060813

Title:
  Upgrade UPower to 1.90.3 to lower cpu and disk usage

Status in upower package in Ubuntu:
  Fix Released
Status in upower package in Debian:
  Unknown

Bug description:
  Reference: https://www.phoronix.com/news/UPower-1.90.4-Released

  Upower 1.90.4 has been released, which fixes an issue making some
  users (maybe having Logitech devices and others) use more cpu and disk
  than intended.

  For me (I have Logitech mouse receiver), when I look at htop without
  doing anything, I see upower appearing there as using CPU.

  If the upgrade cannot be done at this stage, maybe the patch can be
  added to 1.90.2 (the current version in the repository of 24.04):
  https://gitlab.freedesktop.org/upower/upower/-/merge_requests/212

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


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


[Touch-packages] [Bug 2060898] Re: Trying to install gimp-help-en threatens to install wslu

2024-04-11 Thread Jeremy Bícha
Sorry, I ran this command. Not sure why it's wrong.

$ seeded-in-ubuntu chromium-browser
chromium-browser (from chromium-browser) is seeded in:
  ubuntustudio: dvd

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

Title:
  Trying to install gimp-help-en threatens to install wslu

Status in edubuntu-meta package in Ubuntu:
  Triaged
Status in kubuntu-meta package in Ubuntu:
  Triaged
Status in lubuntu-meta package in Ubuntu:
  Triaged
Status in ubuntu-budgie-meta package in Ubuntu:
  Fix Committed
Status in ubuntu-mate-meta package in Ubuntu:
  Triaged
Status in ubuntu-meta package in Ubuntu:
  Invalid
Status in ubuntustudio-meta package in Ubuntu:
  Triaged
Status in wslu package in Ubuntu:
  Invalid
Status in edubuntu-meta source package in Noble:
  Triaged
Status in kubuntu-meta source package in Noble:
  Triaged
Status in lubuntu-meta source package in Noble:
  Triaged
Status in ubuntu-budgie-meta source package in Noble:
  Fix Committed
Status in ubuntu-mate-meta source package in Noble:
  Triaged
Status in ubuntu-meta source package in Noble:
  Invalid
Status in ubuntustudio-meta source package in Noble:
  Triaged
Status in wslu source package in Noble:
  Invalid

Bug description:
  Filing this against ubuntu-meta since I believe this is a seed problem
  that potentially affects all variants of Ubuntu (flavors or
  otherwise).

  wslu is "a collection of utilities for the Windows 10 Linux Subsystem,
  such as for converting Linux paths to a Windows paths or creating
  Linux application shortcuts on the Windows 10 Desktop." Obviously this
  package should *never* be installed on a desktop or even on most VMs,
  but only within WSL instances. However...

  wslu provides the virtual package www-browser, as one of its features
  is to open links in Windows 10 using the default browser set there.
  This means that if a package depends or recommends www-browser, it may
  attempt to pull in one of several packages, wslu included. In the
  past, this hasn't been a problem because Firefox was present on all
  flavor images, and Firefox provides www-browser as well. However, now
  that Firefox is a Snap, it is possible for Firefox to be installed
  without the firefox transitional apt package being installed. (This is
  the case in a default installation of Kubuntu Noble Beta.) As it turns
  out, Kubuntu Noble Beta ships with *no* packages that provide www-
  browser, meaning that any package that depends on it will have to
  install a new browser.

  Due to some stroke of misfortune, apt is picking wslu out of all
  packages as the package for this use case. Installing gimp-help-en
  will also install www-browser, which results in wslu becoming
  installed.

  wslu causes quite a few problems when installed on a desktop system -
  among them, the syslog is spammed with errors due to the system not in
  fact being a WSL VM, audio breaks in weird ways, and application
  launchers sometimes fail. Why this happens is unclear, but the issues
  appear to resolve once wslu is removed from the system. It is
  therefore probably a good idea to avoid wslu becoming installed on
  accident in this way.

  Probably the best way to resolve this is to ensure that some package
  that provides www-browser is available on every Ubuntu image. This
  could be done via seeding or by adding a package to ubuntu-minimal.
  Alternatively, wslu could be set to no longer provide www-browser,
  though it's unclear if that would break its functionality.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/edubuntu-meta/+bug/2060898/+subscriptions


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


[Touch-packages] [Bug 2060693] Re: No welcome/login sound on Ubuntu desktop

2024-04-11 Thread Jeremy Bícha
** Tags added: ally noble

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libcanberra in Ubuntu.
https://bugs.launchpad.net/bugs/2060693

Title:
  No welcome/login sound on Ubuntu desktop

Status in libcanberra package in Ubuntu:
  New

Bug description:
  Under the Ubuntu desktop for Raspberry Pi, for several recent
  releases, the startup sound from the Yaru sound theme has failed to
  play both at the initial setup (from oem-config, where it used to play
  just before language selection), and at the greeter.

  This worked in Jammy (22.04), but on at least mantic (23.10) and the
  forthcoming noble (24.04) (and possibly earlier), this has failed.
  It's not due to a crash in canberra-gtk-play (used to play the sound).
  The only hint that something has failed appears in the oem-config.log:

Failed to play sound: Not available

  Unfortunately there's nothing else in the log that hints at why
  canberra-gtk-play is failing.

  There are several similar bug report, but I doubt they are related
  given their age (e.g. LP: #1002114 relates to ubuntu 12.04 which had a
  very different sound stack and predates the preinstalled desktop
  images).

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


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


[Touch-packages] [Bug 2060898] Re: Trying to install gimp-help-en threatens to install wslu

2024-04-11 Thread Jeremy Bícha
wslu includes wslview which has a feature of being a "fake web browser
that allows opening urls in your default browser on Windows 10".
Therefore, Provides: www-browser is not a bug.

https://manpages.ubuntu.com/wslview

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

Title:
  Trying to install gimp-help-en threatens to install wslu

Status in kubuntu-meta package in Ubuntu:
  Triaged
Status in lubuntu-meta package in Ubuntu:
  Triaged
Status in ubuntu-budgie-meta package in Ubuntu:
  Triaged
Status in ubuntu-mate-meta package in Ubuntu:
  Triaged
Status in ubuntu-meta package in Ubuntu:
  Invalid
Status in wslu package in Ubuntu:
  Invalid
Status in kubuntu-meta source package in Noble:
  Triaged
Status in lubuntu-meta source package in Noble:
  Triaged
Status in ubuntu-budgie-meta source package in Noble:
  Triaged
Status in ubuntu-mate-meta source package in Noble:
  Triaged
Status in ubuntu-meta source package in Noble:
  Invalid
Status in wslu source package in Noble:
  Invalid

Bug description:
  Filing this against ubuntu-meta since I believe this is a seed problem
  that potentially affects all variants of Ubuntu (flavors or
  otherwise).

  wslu is "a collection of utilities for the Windows 10 Linux Subsystem,
  such as for converting Linux paths to a Windows paths or creating
  Linux application shortcuts on the Windows 10 Desktop." Obviously this
  package should *never* be installed on a desktop or even on most VMs,
  but only within WSL instances. However...

  wslu provides the virtual package www-browser, as one of its features
  is to open links in Windows 10 using the default browser set there.
  This means that if a package depends or recommends www-browser, it may
  attempt to pull in one of several packages, wslu included. In the
  past, this hasn't been a problem because Firefox was present on all
  flavor images, and Firefox provides www-browser as well. However, now
  that Firefox is a Snap, it is possible for Firefox to be installed
  without the firefox transitional apt package being installed. (This is
  the case in a default installation of Kubuntu Noble Beta.) As it turns
  out, Kubuntu Noble Beta ships with *no* packages that provide www-
  browser, meaning that any package that depends on it will have to
  install a new browser.

  Due to some stroke of misfortune, apt is picking wslu out of all
  packages as the package for this use case. Installing gimp-help-en
  will also install www-browser, which results in wslu becoming
  installed.

  wslu causes quite a few problems when installed on a desktop system -
  among them, the syslog is spammed with errors due to the system not in
  fact being a WSL VM, audio breaks in weird ways, and application
  launchers sometimes fail. Why this happens is unclear, but the issues
  appear to resolve once wslu is removed from the system. It is
  therefore probably a good idea to avoid wslu becoming installed on
  accident in this way.

  Probably the best way to resolve this is to ensure that some package
  that provides www-browser is available on every Ubuntu image. This
  could be done via seeding or by adding a package to ubuntu-minimal.
  Alternatively, wslu could be set to no longer provide www-browser,
  though it's unclear if that would break its functionality.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kubuntu-meta/+bug/2060898/+subscriptions


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


[Touch-packages] [Bug 2060898] Re: Trying to install gimp-help-en threatens to install wslu

2024-04-11 Thread Jeremy Bícha
I do not believe this is fixable in ubuntu-meta at all, unless the
Flavors want Firefox to be moved to desktop-common which would prevent
any flavor from choosing chromium-browser. (Notably, Ubuntu Studio does
choose Chromium instead of Firefox.)

Therefore, I'm closing the ubuntu-meta task and adding tasks for the
flavors that don't ship the apt package.

** Changed in: ubuntu-meta (Ubuntu Noble)
   Status: New => Invalid

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

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

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

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

** Changed in: kubuntu-meta (Ubuntu Noble)
   Importance: Undecided => High

** Changed in: kubuntu-meta (Ubuntu Noble)
   Status: New => Triaged

** Changed in: lubuntu-meta (Ubuntu Noble)
   Importance: Undecided => High

** Changed in: lubuntu-meta (Ubuntu Noble)
   Status: New => Triaged

** Changed in: ubuntu-budgie-meta (Ubuntu Noble)
   Importance: Undecided => High

** Changed in: ubuntu-budgie-meta (Ubuntu Noble)
   Status: New => Triaged

** Changed in: ubuntu-mate-meta (Ubuntu Noble)
   Importance: Undecided => High

** Changed in: ubuntu-mate-meta (Ubuntu Noble)
   Status: New => Triaged

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

Title:
  Trying to install gimp-help-en threatens to install wslu

Status in kubuntu-meta package in Ubuntu:
  Triaged
Status in lubuntu-meta package in Ubuntu:
  Triaged
Status in ubuntu-budgie-meta package in Ubuntu:
  Triaged
Status in ubuntu-mate-meta package in Ubuntu:
  Triaged
Status in ubuntu-meta package in Ubuntu:
  Invalid
Status in wslu package in Ubuntu:
  Invalid
Status in kubuntu-meta source package in Noble:
  Triaged
Status in lubuntu-meta source package in Noble:
  Triaged
Status in ubuntu-budgie-meta source package in Noble:
  Triaged
Status in ubuntu-mate-meta source package in Noble:
  Triaged
Status in ubuntu-meta source package in Noble:
  Invalid
Status in wslu source package in Noble:
  Invalid

Bug description:
  Filing this against ubuntu-meta since I believe this is a seed problem
  that potentially affects all variants of Ubuntu (flavors or
  otherwise).

  wslu is "a collection of utilities for the Windows 10 Linux Subsystem,
  such as for converting Linux paths to a Windows paths or creating
  Linux application shortcuts on the Windows 10 Desktop." Obviously this
  package should *never* be installed on a desktop or even on most VMs,
  but only within WSL instances. However...

  wslu provides the virtual package www-browser, as one of its features
  is to open links in Windows 10 using the default browser set there.
  This means that if a package depends or recommends www-browser, it may
  attempt to pull in one of several packages, wslu included. In the
  past, this hasn't been a problem because Firefox was present on all
  flavor images, and Firefox provides www-browser as well. However, now
  that Firefox is a Snap, it is possible for Firefox to be installed
  without the firefox transitional apt package being installed. (This is
  the case in a default installation of Kubuntu Noble Beta.) As it turns
  out, Kubuntu Noble Beta ships with *no* packages that provide www-
  browser, meaning that any package that depends on it will have to
  install a new browser.

  Due to some stroke of misfortune, apt is picking wslu out of all
  packages as the package for this use case. Installing gimp-help-en
  will also install www-browser, which results in wslu becoming
  installed.

  wslu causes quite a few problems when installed on a desktop system -
  among them, the syslog is spammed with errors due to the system not in
  fact being a WSL VM, audio breaks in weird ways, and application
  launchers sometimes fail. Why this happens is unclear, but the issues
  appear to resolve once wslu is removed from the system. It is
  therefore probably a good idea to avoid wslu becoming installed on
  accident in this way.

  Probably the best way to resolve this is to ensure that some package
  that provides www-browser is available on every Ubuntu image. This
  could be done via seeding or by adding a package to ubuntu-minimal.
  Alternatively, wslu could be set to no longer provide www-browser,
  though it's unclear if that would break its functionality.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kubuntu-meta/+bug/2060898/+subscriptions


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


[Touch-packages] [Bug 2060898] Re: Trying to install gimp-help-en threatens to install wslu

2024-04-11 Thread Jeremy Bícha
Yes, Ubuntu Desktop Flavors that want to use Firefox need to install the
Firefox apt package. Or if they want to use Chromium, they need to
install the chromium-browser apt package.

The firefox and chromium-browser apt packages should have their package
descriptions updated because they are not only transitional packages but
provide a few things that can't be provided by a snap.

This was discussed here for Chromium but the same thing applies to Firefox:
https://lists.ubuntu.com/archives/ubuntu-devel/2022-February/thread.html

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

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

Title:
  Trying to install gimp-help-en threatens to install wslu

Status in kubuntu-meta package in Ubuntu:
  Triaged
Status in lubuntu-meta package in Ubuntu:
  Triaged
Status in ubuntu-budgie-meta package in Ubuntu:
  Triaged
Status in ubuntu-mate-meta package in Ubuntu:
  Triaged
Status in ubuntu-meta package in Ubuntu:
  Invalid
Status in wslu package in Ubuntu:
  Invalid
Status in kubuntu-meta source package in Noble:
  Triaged
Status in lubuntu-meta source package in Noble:
  Triaged
Status in ubuntu-budgie-meta source package in Noble:
  Triaged
Status in ubuntu-mate-meta source package in Noble:
  Triaged
Status in ubuntu-meta source package in Noble:
  Invalid
Status in wslu source package in Noble:
  Invalid

Bug description:
  Filing this against ubuntu-meta since I believe this is a seed problem
  that potentially affects all variants of Ubuntu (flavors or
  otherwise).

  wslu is "a collection of utilities for the Windows 10 Linux Subsystem,
  such as for converting Linux paths to a Windows paths or creating
  Linux application shortcuts on the Windows 10 Desktop." Obviously this
  package should *never* be installed on a desktop or even on most VMs,
  but only within WSL instances. However...

  wslu provides the virtual package www-browser, as one of its features
  is to open links in Windows 10 using the default browser set there.
  This means that if a package depends or recommends www-browser, it may
  attempt to pull in one of several packages, wslu included. In the
  past, this hasn't been a problem because Firefox was present on all
  flavor images, and Firefox provides www-browser as well. However, now
  that Firefox is a Snap, it is possible for Firefox to be installed
  without the firefox transitional apt package being installed. (This is
  the case in a default installation of Kubuntu Noble Beta.) As it turns
  out, Kubuntu Noble Beta ships with *no* packages that provide www-
  browser, meaning that any package that depends on it will have to
  install a new browser.

  Due to some stroke of misfortune, apt is picking wslu out of all
  packages as the package for this use case. Installing gimp-help-en
  will also install www-browser, which results in wslu becoming
  installed.

  wslu causes quite a few problems when installed on a desktop system -
  among them, the syslog is spammed with errors due to the system not in
  fact being a WSL VM, audio breaks in weird ways, and application
  launchers sometimes fail. Why this happens is unclear, but the issues
  appear to resolve once wslu is removed from the system. It is
  therefore probably a good idea to avoid wslu becoming installed on
  accident in this way.

  Probably the best way to resolve this is to ensure that some package
  that provides www-browser is available on every Ubuntu image. This
  could be done via seeding or by adding a package to ubuntu-minimal.
  Alternatively, wslu could be set to no longer provide www-browser,
  though it's unclear if that would break its functionality.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kubuntu-meta/+bug/2060898/+subscriptions


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


[Touch-packages] [Bug 2060806] Re: Update gstreamer to 1.24.2

2024-04-10 Thread Jeremy Bícha
** Changed in: gst-plugins-good1.0 (Ubuntu)
   Status: Triaged => In Progress

** Changed in: gst-plugins-bad1.0 (Ubuntu)
   Status: Triaged => In Progress

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gst-plugins-bad1.0 in
Ubuntu.
https://bugs.launchpad.net/bugs/2060806

Title:
  Update gstreamer to 1.24.2

Status in gst-plugins-bad1.0 package in Ubuntu:
  In Progress
Status in gst-plugins-good1.0 package in Ubuntu:
  In Progress

Bug description:
  Yesterday, there was a new bugfix release in the stable 1.24.2 series.
  This bug is to track updates for Ubuntu 24.04 LTS.

  https://gstreamer.freedesktop.org/releases/1.24/#1.24.2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gst-plugins-bad1.0/+bug/2060806/+subscriptions


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


[Touch-packages] [Bug 2060813] Re: Upgrade UPower to 1.90.3 to lower cpu and disk usage

2024-04-10 Thread Jeremy Bícha
The Debian maintainer pointed out 1.90.3 is the same as 1.90.4 except
for the version change so 1.90.3 is good enough for the fix you are
wanting.

** Summary changed:

- Upgrade UPower to 1.90.4 to lower cpu and disk usage
+ Upgrade UPower to 1.90.3 to lower cpu and disk usage

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to upower in Ubuntu.
https://bugs.launchpad.net/bugs/2060813

Title:
  Upgrade UPower to 1.90.3 to lower cpu and disk usage

Status in upower package in Ubuntu:
  Triaged
Status in upower package in Debian:
  Unknown

Bug description:
  Reference: https://www.phoronix.com/news/UPower-1.90.4-Released

  Upower 1.90.4 has been released, which fixes an issue making some
  users (maybe having Logitech devices and others) use more cpu and disk
  than intended.

  For me (I have Logitech mouse receiver), when I look at htop without
  doing anything, I see upower appearing there as using CPU.

  If the upgrade cannot be done at this stage, maybe the patch can be
  added to 1.90.2 (the current version in the repository of 24.04):
  https://gitlab.freedesktop.org/upower/upower/-/merge_requests/212

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


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


[Touch-packages] [Bug 2060813] Re: Upgrade UPower to 1.90.4 to lower cpu and disk usage

2024-04-10 Thread Jeremy Bícha
** Changed in: upower (Ubuntu)
   Status: New => Triaged

** Changed in: upower (Ubuntu)
   Importance: Undecided => Medium

** Tags added: noble upgrade-software-version

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to upower in Ubuntu.
https://bugs.launchpad.net/bugs/2060813

Title:
  Upgrade UPower to 1.90.4 to lower cpu and disk usage

Status in upower package in Ubuntu:
  Triaged
Status in upower package in Debian:
  Unknown

Bug description:
  Reference: https://www.phoronix.com/news/UPower-1.90.4-Released

  Upower 1.90.4 has been released, which fixes an issue making some
  users (maybe having Logitech devices and others) use more cpu and disk
  than intended.

  For me (I have Logitech mouse receiver), when I look at htop without
  doing anything, I see upower appearing there as using CPU.

  If the upgrade cannot be done at this stage, maybe the patch can be
  added to 1.90.2 (the current version in the repository of 24.04):
  https://gitlab.freedesktop.org/upower/upower/-/merge_requests/212

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


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


[Touch-packages] [Bug 2060813] Re: Upgrade UPower to 1.90.4 to lower cpu and disk usage

2024-04-10 Thread Jeremy Bícha
** Bug watch added: Debian Bug tracker #1068763
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068763

** Also affects: upower (Debian) via
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068763
   Importance: Unknown
   Status: Unknown

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to upower in Ubuntu.
https://bugs.launchpad.net/bugs/2060813

Title:
  Upgrade UPower to 1.90.4 to lower cpu and disk usage

Status in upower package in Ubuntu:
  Triaged
Status in upower package in Debian:
  Unknown

Bug description:
  Reference: https://www.phoronix.com/news/UPower-1.90.4-Released

  Upower 1.90.4 has been released, which fixes an issue making some
  users (maybe having Logitech devices and others) use more cpu and disk
  than intended.

  For me (I have Logitech mouse receiver), when I look at htop without
  doing anything, I see upower appearing there as using CPU.

  If the upgrade cannot be done at this stage, maybe the patch can be
  added to 1.90.2 (the current version in the repository of 24.04):
  https://gitlab.freedesktop.org/upower/upower/-/merge_requests/212

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


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


[Touch-packages] [Bug 2059830] Re: Port software-properties-gtk to GTK 4

2024-04-10 Thread Jeremy Bícha
** Changed in: software-properties (Ubuntu)
   Status: Confirmed => Triaged

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

Title:
  Port software-properties-gtk to GTK 4

Status in software-properties package in Ubuntu:
  Triaged

Bug description:
  It still uses old GTK 3. Please upgrade it to GTK 4!

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


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


[Touch-packages] [Bug 2059830] Re: Port software-properties-gtk to GTK 4

2024-04-10 Thread Jeremy Bícha
** Changed in: software-properties (Ubuntu)
   Importance: Undecided => Low

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

Title:
  Port software-properties-gtk to GTK 4

Status in software-properties package in Ubuntu:
  Confirmed

Bug description:
  It still uses old GTK 3. Please upgrade it to GTK 4!

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


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


[Touch-packages] [Bug 2060806] [NEW] Update gstreamer to 1.24.2

2024-04-10 Thread Jeremy Bícha
Public bug reported:

Yesterday, there was a new bugfix release in the stable 1.24.2 series.
This bug is to track updates for Ubuntu 24.04 LTS.

https://gstreamer.freedesktop.org/releases/1.24/#1.24.2

** Affects: gst-plugins-bad1.0 (Ubuntu)
 Importance: Medium
 Status: Triaged

** Affects: gst-plugins-good1.0 (Ubuntu)
 Importance: Medium
 Status: Triaged


** Tags: noble upgrade-software-version

** Also affects: gst-plugins-bad1.0 (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: gst-plugins-bad1.0 (Ubuntu)
   Status: New => Triaged

** Changed in: gst-plugins-bad1.0 (Ubuntu)
   Importance: Undecided => Medium

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gst-plugins-bad1.0 in
Ubuntu.
https://bugs.launchpad.net/bugs/2060806

Title:
  Update gstreamer to 1.24.2

Status in gst-plugins-bad1.0 package in Ubuntu:
  Triaged
Status in gst-plugins-good1.0 package in Ubuntu:
  Triaged

Bug description:
  Yesterday, there was a new bugfix release in the stable 1.24.2 series.
  This bug is to track updates for Ubuntu 24.04 LTS.

  https://gstreamer.freedesktop.org/releases/1.24/#1.24.2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gst-plugins-bad1.0/+bug/2060806/+subscriptions


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


[Touch-packages] [Bug 2060319] Re: tracker failing autopkgtest on noble

2024-04-06 Thread Jeremy Bícha
** Bug watch added: Debian Bug tracker #1068468
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068468

** Also affects: tracker (Debian) via
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068468
   Importance: Unknown
   Status: Unknown

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to tracker in Ubuntu.
https://bugs.launchpad.net/bugs/2060319

Title:
  tracker failing autopkgtest on noble

Status in Tracker:
  New
Status in tracker package in Ubuntu:
  Triaged
Status in tracker package in Debian:
  Unknown

Bug description:
  tracker's autopkgtest is failing. I have reported this issue upstream.
  Our autopkgtest configuration is similar but not identical to our
  build test configuration which does pass.

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


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


[Touch-packages] [Bug 2056556] Re: apt-add-repository incorrectly forces lowercase

2024-04-06 Thread Jeremy Bícha
Could you use a lower case suite in your local apt repository as a
workaround for this issue?

I feel like it's a bit of a standard to have lowercase: jammy, bookworm,
virginia etc.

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

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

Title:
  apt-add-repository incorrectly forces lowercase

Status in software-properties package in Ubuntu:
  New

Bug description:
  I have a local APT repository with a non-lowercase suite identifier.
  apt-add-repository always forces it into lowercase, which causes apt
  to emit warnings when it notices the mismatch:

  $ sudo apt-add-repository "deb http://example.com/deb FooBar Baz"
  Repository: 'deb http://example.com/ foobar Baz'
  Description:
  Archive for codename: foobar components: Baz
  More info: http://example.com/
  Adding repository.
  Press [ENTER] to continue or Ctrl-c to cancel.
  (...)
  $ sudo apt update
  (...)
  W: Conflicting distribution: http://example.com/deb foobar InRelease 
(expected foobar but got FooBar)

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


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


[Touch-packages] [Bug 2058720] Re: 'Other Software' section displays verbose ubuntu.sources comment

2024-04-06 Thread Jeremy Bícha
*** This bug is a duplicate of bug 2059797 ***
https://bugs.launchpad.net/bugs/2059797

** This bug has been marked a duplicate of bug 2059797
   Other Software shows extra comment for Ubuntu distribution repository

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded 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/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 2060319] [NEW] tracker failing autopkgtest on noble

2024-04-06 Thread Jeremy Bícha
Public bug reported:

tracker's autopkgtest is failing. I have reported this issue upstream.
Our autopkgtest configuration is similar but not identical to our build
test configuration which does pass.

** Affects: tracker
 Importance: Unknown
 Status: New

** Affects: tracker (Ubuntu)
 Importance: High
 Status: Triaged


** Tags: noble update-excuse

** Bug watch added: gitlab.gnome.org/GNOME/tracker/-/issues #434
   https://gitlab.gnome.org/GNOME/tracker/-/issues/434

** Also affects: tracker via
   https://gitlab.gnome.org/GNOME/tracker/-/issues/434
   Importance: Unknown
   Status: Unknown

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to tracker in Ubuntu.
https://bugs.launchpad.net/bugs/2060319

Title:
  tracker failing autopkgtest on noble

Status in Tracker:
  New
Status in tracker package in Ubuntu:
  Triaged

Bug description:
  tracker's autopkgtest is failing. I have reported this issue upstream.
  Our autopkgtest configuration is similar but not identical to our
  build test configuration which does pass.

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


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


[Touch-packages] [Bug 2059797] Re: Other Software shows extra comment for Ubuntu distribution repository

2024-04-06 Thread Jeremy Bícha
** Attachment added: "Screenshot from 2024-03-22 10-38-59.png"
   
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2059797/+attachment/5761695/+files/Screenshot%20from%202024-03-22%2010-38-59.png

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

Title:
  Other Software shows extra comment for Ubuntu distribution repository

Status in software-properties package in Ubuntu:
  Confirmed

Bug description:
  Test Case
  -
  - Open the Software & Updates tab
  - Switch to the Other Software tab

  There is an entry for
  ## Ubuntu distribution repository
  ##
  ## The following settings can be adjusted to configure which packages to use 
from Ubuntu.

  etc.

  What I Expected
  ---
  That comment should not show. Selecting the entry and clicking Edit allows 
adjusting the main Ubuntu repository source settings which should not be 
allowed there since it is already possible to do that from the Ubuntu Software 
tab.

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: software-properties-gtk 0.99.44
  ProcVersionSignature: Ubuntu 6.8.0-20.20-generic 6.8.1
  Uname: Linux 6.8.0-20-generic x86_64
  NonfreeKernelModules: zfs
  ApportVersion: 2.28.0-0ubuntu1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar 29 12:10:24 2024
  InstallationDate: Installed on 2022-04-06 (723 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Daily amd64 (20220405)
  PackageArchitecture: all
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  SourcePackage: software-properties
  UpgradeStatus: Upgraded to noble on 2023-12-09 (111 days ago)

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


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


[Touch-packages] [Bug 2052851] Re: add-apt-repository Cannot Manage deb822 Repository Sources

2024-04-06 Thread Jeremy Bícha
*** This bug is a duplicate of bug 2033949 ***
https://bugs.launchpad.net/bugs/2033949

I marked this as a duplicate because Ubuntu 24.04 LTS does handle PPAs
now. I recommend trying Ubuntu 24.04 LTS Beta when it is released soon.

Could you open a separate issue for add-apt-repository --list not
returning any deb822 repositories?

** This bug has been marked a duplicate of bug 2033949
   Does not work with Ubuntu sources in deb822 format

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

Title:
  add-apt-repository Cannot Manage deb822 Repository Sources

Status in software-properties package in Ubuntu:
  New

Bug description:
  On Ubuntu 23.10...

  * When adding a PPA, 'add-apt-repository' will add the repository in
  the new deb822 format as a '.sources' file in
  '/etc/apt/sources.list.d'

  * However, 'add-apt-repository --list' cannot see/understand the new
  '.sources' file

  For example, with the flacon ppa
  (https://launchpad.net/~flacon/+archive/ubuntu/ppa):

  1. 'sudo add-apt-repository ppa:flacon/ppa' adds the flacon repo as
  '/etc/apt/sources.list.d/flacon-ubuntu-ppa-mantic.sources'

  2. apt can install and update from the new repo, as expected. you can
  also remove the repo, as expected, by running 'sudo add-apt-repository
  --remove ppa:flacon/ppa'

  3. However, 'add-apt-repository --list' does not list the repo as it
  should. GUI package managers such as Muon and Synaptic also do not see
  the new repo.

  It makes working with packages quite frustrating, and unfortunately,
  per Julian Andres Klode (juliank), there seems to be no plan to fix
  the broken 'software-properties-common' any time soon. See here:

  https://bugs.launchpad.net/ubuntu/+source/software-
  properties/+bug/2033949

  Also see related issues:

  https://bugs.launchpad.net/ubuntu/+source/ppa-purge/+bug/2036761
  https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2037210
  https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2036288
  https://lists.ubuntu.com/archives/ubuntu-devel/2023-September/042791.html

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


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


[Touch-packages] [Bug 2060073] [NEW] folks build test failures with glib 2.80

2024-04-02 Thread Jeremy Bícha
Public bug reported:

folks build tests are failing.

I reported this issue upstream. It appears to be triggered by glib 2.80
and gobject-introspection 1.80.

We worked around this issue for Ubuntu 24.04 LTS by ignoring build test
failures because it was essential that we build folks to clear
transitions.

** Affects: libfolks
 Importance: Unknown
 Status: Unknown

** Affects: folks (Ubuntu)
 Importance: High
 Status: Triaged


** Tags: ftbfs noble

** Bug watch added: gitlab.gnome.org/GNOME/folks/-/issues #140
   https://gitlab.gnome.org/GNOME/folks/-/issues/140

** Also affects: libfolks via
   https://gitlab.gnome.org/GNOME/folks/-/issues/140
   Importance: Unknown
   Status: Unknown

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to folks in Ubuntu.
https://bugs.launchpad.net/bugs/2060073

Title:
  folks build test failures with glib 2.80

Status in libfolks:
  Unknown
Status in folks package in Ubuntu:
  Triaged

Bug description:
  folks build tests are failing.

  I reported this issue upstream. It appears to be triggered by glib
  2.80 and gobject-introspection 1.80.

  We worked around this issue for Ubuntu 24.04 LTS by ignoring build
  test failures because it was essential that we build folks to clear
  transitions.

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


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


[Touch-packages] [Bug 2059797] [NEW] Other Software shows extra comment for Ubuntu distribution repository

2024-03-29 Thread Jeremy Bícha
Public bug reported:

Test Case
-
- Open the Software & Updates tab
- Switch to the Other Software tab

There is an entry for
## Ubuntu distribution repository
##
## The following settings can be adjusted to configure which packages to use 
from Ubuntu.

etc.

What I Expected
---
That comment should not show. Selecting the entry and clicking Edit allows 
adjusting the main Ubuntu repository source settings which should not be 
allowed there since it is already possible to do that from the Ubuntu Software 
tab.

ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: software-properties-gtk 0.99.44
ProcVersionSignature: Ubuntu 6.8.0-20.20-generic 6.8.1
Uname: Linux 6.8.0-20-generic x86_64
NonfreeKernelModules: zfs
ApportVersion: 2.28.0-0ubuntu1
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Fri Mar 29 12:10:24 2024
InstallationDate: Installed on 2022-04-06 (723 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Daily amd64 (20220405)
PackageArchitecture: all
ProcEnviron:
 LANG=en_US.UTF-8
 PATH=(custom, no user)
 SHELL=/bin/bash
 TERM=xterm-256color
 XDG_RUNTIME_DIR=
SourcePackage: software-properties
UpgradeStatus: Upgraded to noble on 2023-12-09 (111 days ago)

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


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

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

Title:
  Other Software shows extra comment for Ubuntu distribution repository

Status in software-properties package in Ubuntu:
  New

Bug description:
  Test Case
  -
  - Open the Software & Updates tab
  - Switch to the Other Software tab

  There is an entry for
  ## Ubuntu distribution repository
  ##
  ## The following settings can be adjusted to configure which packages to use 
from Ubuntu.

  etc.

  What I Expected
  ---
  That comment should not show. Selecting the entry and clicking Edit allows 
adjusting the main Ubuntu repository source settings which should not be 
allowed there since it is already possible to do that from the Ubuntu Software 
tab.

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: software-properties-gtk 0.99.44
  ProcVersionSignature: Ubuntu 6.8.0-20.20-generic 6.8.1
  Uname: Linux 6.8.0-20-generic x86_64
  NonfreeKernelModules: zfs
  ApportVersion: 2.28.0-0ubuntu1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar 29 12:10:24 2024
  InstallationDate: Installed on 2022-04-06 (723 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Daily amd64 (20220405)
  PackageArchitecture: all
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  SourcePackage: software-properties
  UpgradeStatus: Upgraded to noble on 2023-12-09 (111 days ago)

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


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


[Touch-packages] [Bug 2059796] [NEW] Other Software > Remove button doesn't work

2024-03-29 Thread Jeremy Bícha
Public bug reported:

Test Case
-
- Add a PPA
- Open the Software & Updates tab
- Switch to the Other Software tab
- Select the PPA line and click Remove
- After Authentication, nothing happens.

No error is emitted to the command line. The repo line still shows. The
repo is still in /etc/apt/sources.list.d/

ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: software-properties-gtk 0.99.44
ProcVersionSignature: Ubuntu 6.8.0-20.20-generic 6.8.1
Uname: Linux 6.8.0-20-generic x86_64
NonfreeKernelModules: zfs
ApportVersion: 2.28.0-0ubuntu1
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Fri Mar 29 12:06:07 2024
InstallationDate: Installed on 2022-04-06 (723 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Daily amd64 (20220405)
PackageArchitecture: all
ProcEnviron:
 LANG=en_US.UTF-8
 PATH=(custom, no user)
 SHELL=/bin/bash
 TERM=xterm-256color
 XDG_RUNTIME_DIR=
SourcePackage: software-properties
UpgradeStatus: Upgraded to noble on 2023-12-09 (111 days ago)

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


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

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

Title:
  Other Software > Remove button doesn't work

Status in software-properties package in Ubuntu:
  New

Bug description:
  Test Case
  -
  - Add a PPA
  - Open the Software & Updates tab
  - Switch to the Other Software tab
  - Select the PPA line and click Remove
  - After Authentication, nothing happens.

  No error is emitted to the command line. The repo line still shows.
  The repo is still in /etc/apt/sources.list.d/

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: software-properties-gtk 0.99.44
  ProcVersionSignature: Ubuntu 6.8.0-20.20-generic 6.8.1
  Uname: Linux 6.8.0-20-generic x86_64
  NonfreeKernelModules: zfs
  ApportVersion: 2.28.0-0ubuntu1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar 29 12:06:07 2024
  InstallationDate: Installed on 2022-04-06 (723 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Daily amd64 (20220405)
  PackageArchitecture: all
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  SourcePackage: software-properties
  UpgradeStatus: Upgraded to noble on 2023-12-09 (111 days ago)

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


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


[Touch-packages] [Bug 2056753] Re: pygobject FTBFS on armhf: time_t build test failure

2024-03-29 Thread Jeremy Bícha
** Changed in: gobject-introspection (Ubuntu)
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gobject-introspection in
Ubuntu.
https://bugs.launchpad.net/bugs/2056753

Title:
  pygobject FTBFS on armhf: time_t build test failure

Status in GObject Introspection:
  Fix Released
Status in gobject-introspection package in Ubuntu:
  Fix Released
Status in gobject-introspection package in Debian:
  Fix Released

Bug description:
  pygobject fails to build on armhf, the only Ubuntu 32-bit architecture
  that has done the time_t transition.

  test_gi.py runs a time_t test that I believe is using functions in
  glib2.0

  Test log excerpt
  

  tests/test_gi.py ... [ 
21%]
  .
  --- stderr ---
  Fatal Python error: Aborted

  Current thread 0xf785e020 (most recent call first):
File "/<>/tests/test_gi.py", line 579 in test_time_t_in
File "/usr/lib/python3.12/unittest/case.py", line 589 in _callTestMethod
File "/usr/lib/python3.12/unittest/case.py", line 634 in run
File "/usr/lib/python3.12/unittest/case.py", line 690 in __call__
File "/usr/lib/python3/dist-packages/_pytest/unittest.py", line 338 in 
runtest
File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 170 in 
pytest_runtest_call
File "/usr/lib/python3/dist-packages/pluggy/_callers.py", line 102 in 
_multicall
File "/usr/lib/python3/dist-packages/pluggy/_manager.py", line 119 in 
_hookexec
File "/usr/lib/python3/dist-packages/pluggy/_hooks.py", line 501 in __call__
File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 263 in 

File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 342 in 
from_call
File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 262 in 
call_runtest_hook
File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 223 in 
call_and_report
File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 134 in 
runtestprotocol
File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 115 in 
pytest_runtest_protocol
File "/usr/lib/python3/dist-packages/pluggy/_callers.py", line 102 in 
_multicall
File "/usr/lib/python3/dist-packages/pluggy/_manager.py", line 119 in 
_hookexec
File "/usr/lib/python3/dist-packages/pluggy/_hooks.py", line 501 in __call__
File "/usr/lib/python3/dist-packages/_pytest/main.py", line 352 in 
pytest_runtestloop
File "/usr/lib/python3/dist-packages/pluggy/_callers.py", line 102 in 
_multicall
File "/usr/lib/python3/dist-packages/pluggy/_manager.py", line 119 in 
_hookexec
File "/usr/lib/python3/dist-packages/pluggy/_hooks.py", line 501 in __call__
File "/usr/lib/python3/dist-packages/_pytest/main.py", line 327 in _main
File "/usr/lib/python3/dist-packages/_pytest/main.py", line 273 in 
wrap_session
File "/usr/lib/python3/dist-packages/_pytest/main.py", line 320 in 
pytest_cmdline_main
File "/usr/lib/python3/dist-packages/pluggy/_callers.py", line 102 in 
_multicall
File "/usr/lib/python3/dist-packages/pluggy/_manager.py", line 119 in 
_hookexec
File "/usr/lib/python3/dist-packages/pluggy/_hooks.py", line 501 in __call__
File "/usr/lib/python3/dist-packages/_pytest/config/__init__.py", line 175 
in main
File "/usr/lib/python3/dist-packages/_pytest/config/__init__.py", line 198 
in console_main
File "/usr/lib/python3/dist-packages/pytest/__main__.py", line 7 in 
File "", line 88 in _run_code
File "", line 198 in _run_module_as_main

  Full build log
  ==
  
https://launchpad.net/ubuntu/+source/pygobject/3.47.0-3build1/+latestbuild/armhf

To manage notifications about this bug go to:
https://bugs.launchpad.net/gobject-introspection/+bug/2056753/+subscriptions


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


[Touch-packages] [Bug 2058647] Re: GNOME OAuth2 Handler desktop entry not hidden

2024-03-21 Thread Jeremy Bícha
This is already fixed in noble-proposed. Therefore, I'm closing this
bug.

https://gitlab.gnome.org/GNOME/gnome-online-
accounts/-/merge_requests/177

** Changed in: gnome-online-accounts (Ubuntu)
   Status: New => Fix Released

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

Title:
  GNOME OAuth2 Handler desktop entry not hidden

Status in gnome-online-accounts package in Ubuntu:
  Fix Released

Bug description:
  The GNOME OAuth2 Handler desktop entry should be hidden (it is not an
  user app and clicking it does nothing), but is displayed in Shell
  Overview on latest Ubuntu 24.04. This is because the "X-Ubuntu-
  Gettext-Domain" line that is incorrectly added to the file without a
  newline character:

  $ cat org.gnome.OnlineAccounts.OAuth2.desktop
  [Desktop Entry]
  Name=GNOME OAuth2 Handler
  Exec=/usr/libexec/goa-oauth2-handler %u
  Type=Application
  
MimeType=x-scheme-handler/goa-oauth2;x-scheme-handler/com.googleusercontent.apps.44438659992-7kgjeitenc16ssihbtdjbgguch7ju55s
  NoDisplay=trueX-Ubuntu-Gettext-Domain=gnome-online-accounts

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


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


[Touch-packages] [Bug 2056649] Re: Outlook.com does not authenticate anymore with evolution-ews or gnome online accounts

2024-03-20 Thread Jeremy Bícha
** Changed in: evolution-ews (Ubuntu)
   Status: New => Fix Committed

** No longer affects: gnome-online-accounts (Ubuntu)

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

Title:
  Outlook.com does not authenticate anymore with evolution-ews or gnome
  online accounts

Status in evolution-ews:
  Fix Released
Status in evolution-ews package in Ubuntu:
  Fix Committed

Bug description:
  Ubuntu 22.04.4
  evolution-ews 3.44.0-1
  gnome-online-accounts 3.44.0-1ubuntu1

  Earlier I could add outlook.com to gnome calendar with exchange in
  Gnome online accounts and evolution-ews installed, now Microsoft has
  changed something and it does not authenticate anymore..

  https://support.microsoft.com/en-us/office/outlook-and-other-apps-are-
  unable-to-connect-to-outlook-com-when-using-basic-
  authentication-f4202ebf-89c6-4a8a-bec3-3d60cf7deaef

  It's not very long to the release date for 24.04 LTS, and I hope this
  is fixed before that..

  In evolution it does ask for outlook.com password and I use the right
  password, nothing happens, other than it just asking for password
  again.. edit: I got a error message now (see screenshot in comment #1)

  edit 10.3.24: upgraded to Ubuntu 23.10 and it still does not work

To manage notifications about this bug go to:
https://bugs.launchpad.net/evolution-ews/+bug/2056649/+subscriptions


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


[Touch-packages] [Bug 2044420] Re: gtkpod segfaults when attempting to display songs

2024-03-20 Thread Jeremy Bícha
Please update the bug description to use the SRU Template in order for
this to be sponsored for Ubuntu 23.10.

https://wiki.ubuntu.com/StableReleaseUpdates#SRU_Bug_Template

Does this fix require a fix for glib in Ubuntu 23.10 first?

I am setting this bug to Incomplete and unsubscribing ubuntu-sponsors.
Please set it back to New and resubscribe ubuntu-sponsors when these
items have been dealt with.

** Changed in: gtkpod (Ubuntu)
   Status: New => Won't Fix

** Changed in: gtkpod (Ubuntu Mantic)
   Status: New => Incomplete

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

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

Title:
  gtkpod segfaults when attempting to display songs

Status in GLib:
  Fix Released
Status in glib2.0 package in Ubuntu:
  Fix Released
Status in gtkpod package in Ubuntu:
  Won't Fix
Status in glib2.0 source package in Mantic:
  Triaged
Status in gtkpod source package in Mantic:
  Incomplete

Bug description:
  Open gtkpod, and select your ipod from the list. If it has more than
  one screenfull of songs to display in the list, gtkpod will
  immediately segfault.

  I haven't found a workaround yet.

  Broken on Mantic, works on Lunar.

  Thread 1 "gtkpod" received signal SIGSEGV, Segmentation fault.
  __GI___wcsxfrm_l (dest=0x0, src=0x0, n=0, l=0x76fff5a0 
<_nl_global_locale>) at ../string/strxfrm_l.c:685
  685   ../string/strxfrm_l.c: No such file or directory.
  (gdb) bt
  #0  __GI___wcsxfrm_l (dest=0x0, src=0x0, n=0, l=0x76fff5a0 
<_nl_global_locale>) at ../string/strxfrm_l.c:685
  #1  0x770c5a5e in g_utf8_collate_key () at 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
  #2  0x77f852ec in fuzzy_skip_prefix () at 
/lib/x86_64-linux-gnu/libgtkpod.so.1
  #3  0x7fffa80980ca in ??? () at 
/usr/lib/x86_64-linux-gnu/gtkpod/libsorttab_display.so
  #4  0x7fffa80997fd in normal_sort_tab_page_add_track () at 
/usr/lib/x86_64-linux-gnu/gtkpod/libsorttab_display.so
  #5  0x7fffa8099526 in normal_sort_tab_page_add_track () at 
/usr/lib/x86_64-linux-gnu/gtkpod/libsorttab_display.so
  #6  0x7fffa809f196 in sorttab_display_select_playlist_cb () at 
/usr/lib/x86_64-linux-gnu/gtkpod/libsorttab_display.so
  #7  0x7718d130 in g_closure_invoke () at 
/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  #8  0x771ba4ac in ??? () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0
  #9  0x771ab9b1 in ??? () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0
  #10 0x771abbd6 in g_signal_emit_valist () at 
/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  #11 0x771abc93 in g_signal_emit () at 
/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  #12 0x77f67e4b in gtkpod_set_current_playlist () at 
/lib/x86_64-linux-gnu/libgtkpod.so.1
  #13 0x7fffa807cce0 in ??? () at 
/usr/lib/x86_64-linux-gnu/gtkpod/libplaylist_display.so
  #14 0x7708ba11 in ??? () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
  #15 0x770e746f in ??? () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
  #16 0x7708c46f in g_main_loop_run () at 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
  #17 0x777f61ed in gtk_main () at /lib/x86_64-linux-gnu/libgtk-3.so.0
  #18 0xea1f in main ()

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


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


[Touch-packages] [Bug 2037569] Re: udev issues with mantic beta

2024-03-20 Thread Jeremy Bícha
The libblockdev fix was included in 3.0.4 which is now in Ubuntu 24.04
LTS

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/2037569

Title:
  udev issues with mantic beta

Status in Ubuntu on IBM z Systems:
  Fix Released
Status in libblockdev package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Invalid
Status in udisks2 package in Ubuntu:
  Fix Released

Bug description:
  While installing mantic beta (on s390x, LPAR and z/VM - but this might not be 
architecture specific) I faced issues with udev.
  In my installation I've updated the installer to "edge/lp-2009141" (subiquity 
 22.02.2+git1762.1b1ee6f4  5164).

  During my installations I first noticed bad response times in case of
  dealing with devices (like enabling new devices with chzdev). chzdev
  is used during the installation, hence the installation procedure is
  also affected by this. (I mainly notice this issue in case of DASD
  ECKD disk enablements.)

  But even after after a successful (but due to this issue less snappier) 
installation, means after the post-install reboot, in the installed system I 
can find several udev related processes, like:
69448 root  20   0   31280  11944   2560 S  39.2   0.0   2:51.67 
(udev-worker)
  509 root  20   0   31276  13812   4600 S  20.6   0.0   2:07.76 
systemd-udevd
  893 root  20   0  469016  13544  10496 R  17.3   0.0   1:43.53 
udisksd  
1 root  20   0  168664  12748   8396 S  16.3   0.0   1:40.47 
systemd  
  which is not only unusual, but (as one can see) they consume quite some 
resources.
  Even the remote ssh into that system is impacted by this high load.

  So far I only see this in mantic.
  I tried 20.04.3 as well as lunar, but both do not seem to be affected by this 
udev problem.
  I neither face the bad response on device enablement, nor can see any udev 
related processes still running after post-install-reboot in the installed 
system.

  (Sometimes I could also see a growing log file 'syslog').

  I cannot say yet what is causing this, but since I see 'systemd-udevd'
  as prominent process in top, I'll first of all mark this as affecting
  systemd-udevd (or systemd).

  I've attached the outcome of some more investigations I did ...

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/2037569/+subscriptions


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


[Touch-packages] [Bug 907916] Re: empathy crashed with SIGSEGV in empathy_contact_get_alias()

2024-03-16 Thread Jeremy Bícha
** Changed in: folks (Ubuntu)
   Status: Confirmed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to folks in Ubuntu.
https://bugs.launchpad.net/bugs/907916

Title:
  empathy crashed with SIGSEGV in empathy_contact_get_alias()

Status in empathy package in Ubuntu:
  Fix Released
Status in folks package in Ubuntu:
  Fix Released

Bug description:
  This crash occurs when trying to add a new contact and when trying to
  place a "New call" to a SIP number not in the contact list.

  ProblemType: Crash
  DistroRelease: Ubuntu 12.04
  Package: empathy 3.3.3-0ubuntu1
  ProcVersionSignature: Ubuntu 3.2.0-6.12-generic 3.2.0-rc6
  Uname: Linux 3.2.0-6-generic x86_64
  ApportVersion: 1.90-0ubuntu1
  Architecture: amd64
  CheckboxSubmission: 1e7afd42fe45733e86839c658e18c54d
  CheckboxSystem: bb422ca46d02494cdbc459927a98bc2f
  Date: Thu Dec 22 16:02:04 2011
  ExecutablePath: /usr/bin/empathy
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Alpha amd64 (20110802)
  ProcCmdline: empathy
  SegvAnalysis:
   Segfault happened at: 0x47e766 : cmp
%rax,(%rdx)
   PC (0x0047e766) ok
   source "%rax" ok
   destination "(%rdx)" (0xe7894cc689f2894c) not located in a known VMA region 
(needed writable region)!
  SegvReason: writing unknown VMA
  Signal: 11
  SourcePackage: empathy
  StacktraceTop:
   empathy_contact_get_account (contact=) at 
empathy-contact.c:978
   empathy_new_call_dialog_response (dialog=0x2302a80, response_id=-3) at 
empathy-new-call-dialog.c:99
   g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: empathy crashed with SIGSEGV in empathy_contact_get_account()
  UpgradeStatus: Upgraded to precise on 2011-11-08 (44 days ago)
  UserGroups: adm admin cdrom dialout libvirtd lpadmin plugdev sambashare

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


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


[Touch-packages] [Bug 2057836] Re: gst-python1.0 fails to build: test failures

2024-03-13 Thread Jeremy Bícha
The issue appears to be a pygobject bug so I've forwarded the issue
there now.

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

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pygobject in Ubuntu.
https://bugs.launchpad.net/bugs/2057836

Title:
  gst-python1.0 fails to build: test failures

Status in pygobject:
  Unknown
Status in gst-python1.0 package in Ubuntu:
  Triaged
Status in pygobject package in Ubuntu:
  Triaged
Status in gst-python1.0 package in Debian:
  Unknown

Bug description:
  gst-python1.0 fails to build because of test failures.

  https://launchpad.net/ubuntu/+source/gst-python1.0/1.22.10-1build1

  https://launchpad.net/ubuntu/+source/gst-python1.0/1.24.0-1

  I have reported the issue to the upstream developers

  https://gitlab.freedesktop.org/gstreamer/gstreamer/-/issues/3353

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


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


[Touch-packages] [Bug 2057836] [NEW] gst-python1.0 fails to build: test failures

2024-03-13 Thread Jeremy Bícha
Public bug reported:

gst-python1.0 fails to build because of test failures.

https://launchpad.net/ubuntu/+source/gst-python1.0/1.22.10-1build1

https://launchpad.net/ubuntu/+source/gst-python1.0/1.24.0-1

I have reported the issue to the upstream developers

https://gitlab.freedesktop.org/gstreamer/gstreamer/-/issues/3353

** Affects: pygobject
 Importance: Unknown
 Status: Unknown

** Affects: gst-python1.0 (Ubuntu)
 Importance: High
 Status: Triaged

** Affects: pygobject (Ubuntu)
 Importance: High
 Status: Triaged

** Affects: gst-python1.0 (Debian)
 Importance: Unknown
 Status: Unknown


** Tags: ftbfs noble update-excuse

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

** Also affects: gst-python1.0 (Debian) via
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065547
   Importance: Unknown
   Status: Unknown

** Description changed:

  gst-python1.0 fails to build because of test failures.
  
  https://launchpad.net/ubuntu/+source/gst-python1.0/1.22.10-1build1
  
  https://launchpad.net/ubuntu/+source/gst-python1.0/1.24.0-1
  
  I have reported the issue to the upstream developers
+ 
+ https://gitlab.freedesktop.org/gstreamer/gstreamer/-/issues/3353

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

** Bug watch added: gitlab.gnome.org/GNOME/pygobject/-/issues #624
   https://gitlab.gnome.org/GNOME/pygobject/-/issues/624

** Also affects: pygobject via
   https://gitlab.gnome.org/GNOME/pygobject/-/issues/624
   Importance: Unknown
   Status: Unknown

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pygobject in Ubuntu.
https://bugs.launchpad.net/bugs/2057836

Title:
  gst-python1.0 fails to build: test failures

Status in pygobject:
  Unknown
Status in gst-python1.0 package in Ubuntu:
  Triaged
Status in pygobject package in Ubuntu:
  Triaged
Status in gst-python1.0 package in Debian:
  Unknown

Bug description:
  gst-python1.0 fails to build because of test failures.

  https://launchpad.net/ubuntu/+source/gst-python1.0/1.22.10-1build1

  https://launchpad.net/ubuntu/+source/gst-python1.0/1.24.0-1

  I have reported the issue to the upstream developers

  https://gitlab.freedesktop.org/gstreamer/gstreamer/-/issues/3353

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


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


[Touch-packages] [Bug 1833322] Re: Please consider no more having irqbalance enabled by default (per image/use-case/TBD)

2024-03-13 Thread Jeremy Bícha
David, please open a new bug against ubuntu-meta about that issue.

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

Title:
  Please consider no more having irqbalance enabled by default (per
  image/use-case/TBD)

Status in cloud-images:
  New
Status in Release Notes for Ubuntu:
  Fix Released
Status in Ubuntu on IBM z Systems:
  Fix Released
Status in irqbalance package in Ubuntu:
  Opinion
Status in ubuntu-meta package in Ubuntu:
  Fix Released

Bug description:
  as per https://github.com/pop-os/default-settings/issues/60

  Distribution (run cat /etc/os-release):

  $ cat /etc/os-release
  NAME="Pop!_OS"
  VERSION="19.04"
  ID=ubuntu
  ID_LIKE=debian
  PRETTY_NAME="Pop!_OS 19.04"
  VERSION_ID="19.04"
  HOME_URL="https://system76.com/pop;
  SUPPORT_URL="http://support.system76.com;
  BUG_REPORT_URL="https://github.com/pop-os/pop/issues;
  PRIVACY_POLICY_URL="https://system76.com/privacy;
  VERSION_CODENAME=disco
  UBUNTU_CODENAME=disco

  Related Application and/or Package Version (run apt policy $PACKAGE
  NAME):

  $ apt policy irqbalance
  irqbalance:
  Installed: 1.5.0-3ubuntu1
  Candidate: 1.5.0-3ubuntu1
  Version table:
  *** 1.5.0-3ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu disco/main amd64 Packages
  100 /var/lib/dpkg/status

  $ apt rdepends irqbalance
  irqbalance
  Reverse Depends:
  Recommends: ubuntu-standard
  gce-compute-image-packages

  Issue/Bug Description:

  as per konkor/cpufreq#48 and
  http://konkor.github.io/cpufreq/faq/#irqbalance-detected

  irqbalance is technically not needed on desktop systems (supposedly it
  is mainly for servers), and may actually reduce performance and power
  savings. It appears to provide benefits only to server environments
  that have relatively-constant loading. If it is truly a server-
  oriented package, then it shouldn't be installed by default on a
  desktop/laptop system and shouldn't be included in desktop OS images.

  Steps to reproduce (if you know):

  This is potentially an issue with all default installs.

  Expected behavior:

  n/a

  Other Notes:

  I can safely remove it via "sudo apt purge irqbalance" without any
  apparent adverse side-effects. If someone is running a situation where
  they need it, then they always have the option of installing it from
  the repositories.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-images/+bug/1833322/+subscriptions


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


[Touch-packages] [Bug 2054924] Re: color emoji are broken with fontconfig 2.15

2024-03-12 Thread Jeremy Bícha
** Changed in: fontconfig (Ubuntu)
   Status: Triaged => Fix Committed

** Changed in: fonts-noto-color-emoji (Ubuntu)
   Status: Triaged => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to fontconfig in Ubuntu.
https://bugs.launchpad.net/bugs/2054924

Title:
  color emoji are broken with fontconfig 2.15

Status in Fontconfig:
  Fix Released
Status in fontconfig package in Ubuntu:
  Fix Committed
Status in fonts-noto-color-emoji package in Ubuntu:
  Fix Released
Status in fontconfig package in Debian:
  Fix Released

Bug description:
  The Noto Color Emoji font is no longer used to show emoji. Many emoji
  no longer show and the few that do are not in color.

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


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


[Touch-packages] [Bug 2056753] Re: pygobject FTBFS on armhf: time_t build test failure

2024-03-12 Thread Jeremy Bícha
** No longer affects: pygobject (Ubuntu)

** Changed in: gobject-introspection (Ubuntu)
   Status: Triaged => Fix Committed

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gobject-introspection in
Ubuntu.
https://bugs.launchpad.net/bugs/2056753

Title:
  pygobject FTBFS on armhf: time_t build test failure

Status in GObject Introspection:
  New
Status in gobject-introspection package in Ubuntu:
  Fix Committed
Status in gobject-introspection package in Debian:
  New

Bug description:
  pygobject fails to build on armhf, the only Ubuntu 32-bit architecture
  that has done the time_t transition.

  test_gi.py runs a time_t test that I believe is using functions in
  glib2.0

  Test log excerpt
  

  tests/test_gi.py ... [ 
21%]
  .
  --- stderr ---
  Fatal Python error: Aborted

  Current thread 0xf785e020 (most recent call first):
File "/<>/tests/test_gi.py", line 579 in test_time_t_in
File "/usr/lib/python3.12/unittest/case.py", line 589 in _callTestMethod
File "/usr/lib/python3.12/unittest/case.py", line 634 in run
File "/usr/lib/python3.12/unittest/case.py", line 690 in __call__
File "/usr/lib/python3/dist-packages/_pytest/unittest.py", line 338 in 
runtest
File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 170 in 
pytest_runtest_call
File "/usr/lib/python3/dist-packages/pluggy/_callers.py", line 102 in 
_multicall
File "/usr/lib/python3/dist-packages/pluggy/_manager.py", line 119 in 
_hookexec
File "/usr/lib/python3/dist-packages/pluggy/_hooks.py", line 501 in __call__
File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 263 in 

File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 342 in 
from_call
File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 262 in 
call_runtest_hook
File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 223 in 
call_and_report
File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 134 in 
runtestprotocol
File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 115 in 
pytest_runtest_protocol
File "/usr/lib/python3/dist-packages/pluggy/_callers.py", line 102 in 
_multicall
File "/usr/lib/python3/dist-packages/pluggy/_manager.py", line 119 in 
_hookexec
File "/usr/lib/python3/dist-packages/pluggy/_hooks.py", line 501 in __call__
File "/usr/lib/python3/dist-packages/_pytest/main.py", line 352 in 
pytest_runtestloop
File "/usr/lib/python3/dist-packages/pluggy/_callers.py", line 102 in 
_multicall
File "/usr/lib/python3/dist-packages/pluggy/_manager.py", line 119 in 
_hookexec
File "/usr/lib/python3/dist-packages/pluggy/_hooks.py", line 501 in __call__
File "/usr/lib/python3/dist-packages/_pytest/main.py", line 327 in _main
File "/usr/lib/python3/dist-packages/_pytest/main.py", line 273 in 
wrap_session
File "/usr/lib/python3/dist-packages/_pytest/main.py", line 320 in 
pytest_cmdline_main
File "/usr/lib/python3/dist-packages/pluggy/_callers.py", line 102 in 
_multicall
File "/usr/lib/python3/dist-packages/pluggy/_manager.py", line 119 in 
_hookexec
File "/usr/lib/python3/dist-packages/pluggy/_hooks.py", line 501 in __call__
File "/usr/lib/python3/dist-packages/_pytest/config/__init__.py", line 175 
in main
File "/usr/lib/python3/dist-packages/_pytest/config/__init__.py", line 198 
in console_main
File "/usr/lib/python3/dist-packages/pytest/__main__.py", line 7 in 
File "", line 88 in _run_code
File "", line 198 in _run_module_as_main

  Full build log
  ==
  
https://launchpad.net/ubuntu/+source/pygobject/3.47.0-3build1/+latestbuild/armhf

To manage notifications about this bug go to:
https://bugs.launchpad.net/gobject-introspection/+bug/2056753/+subscriptions


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


[Touch-packages] [Bug 2056753] Re: pygobject FTBFS on armhf: time_t build test failure

2024-03-11 Thread Jeremy Bícha
** Also affects: gobject-introspection (Ubuntu)
   Importance: Undecided
   Status: New

** Bug watch added: gitlab.gnome.org/GNOME/gobject-introspection/-/issues #494
   https://gitlab.gnome.org/GNOME/gobject-introspection/-/issues/494

** Also affects: gobject-introspection via
   https://gitlab.gnome.org/GNOME/gobject-introspection/-/issues/494
   Importance: Unknown
   Status: Unknown

** Changed in: gobject-introspection (Ubuntu)
   Status: New => Triaged

** Changed in: gobject-introspection (Ubuntu)
   Importance: Undecided => High

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

** Also affects: gobject-introspection (Debian) via
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066032
   Importance: Unknown
   Status: Unknown

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gobject-introspection in
Ubuntu.
https://bugs.launchpad.net/bugs/2056753

Title:
  pygobject FTBFS on armhf: time_t build test failure

Status in GObject Introspection:
  Unknown
Status in gobject-introspection package in Ubuntu:
  Triaged
Status in pygobject package in Ubuntu:
  Triaged
Status in gobject-introspection package in Debian:
  Unknown

Bug description:
  pygobject fails to build on armhf, the only Ubuntu 32-bit architecture
  that has done the time_t transition.

  test_gi.py runs a time_t test that I believe is using functions in
  glib2.0

  Test log excerpt
  

  tests/test_gi.py ... [ 
21%]
  .
  --- stderr ---
  Fatal Python error: Aborted

  Current thread 0xf785e020 (most recent call first):
File "/<>/tests/test_gi.py", line 579 in test_time_t_in
File "/usr/lib/python3.12/unittest/case.py", line 589 in _callTestMethod
File "/usr/lib/python3.12/unittest/case.py", line 634 in run
File "/usr/lib/python3.12/unittest/case.py", line 690 in __call__
File "/usr/lib/python3/dist-packages/_pytest/unittest.py", line 338 in 
runtest
File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 170 in 
pytest_runtest_call
File "/usr/lib/python3/dist-packages/pluggy/_callers.py", line 102 in 
_multicall
File "/usr/lib/python3/dist-packages/pluggy/_manager.py", line 119 in 
_hookexec
File "/usr/lib/python3/dist-packages/pluggy/_hooks.py", line 501 in __call__
File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 263 in 

File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 342 in 
from_call
File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 262 in 
call_runtest_hook
File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 223 in 
call_and_report
File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 134 in 
runtestprotocol
File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 115 in 
pytest_runtest_protocol
File "/usr/lib/python3/dist-packages/pluggy/_callers.py", line 102 in 
_multicall
File "/usr/lib/python3/dist-packages/pluggy/_manager.py", line 119 in 
_hookexec
File "/usr/lib/python3/dist-packages/pluggy/_hooks.py", line 501 in __call__
File "/usr/lib/python3/dist-packages/_pytest/main.py", line 352 in 
pytest_runtestloop
File "/usr/lib/python3/dist-packages/pluggy/_callers.py", line 102 in 
_multicall
File "/usr/lib/python3/dist-packages/pluggy/_manager.py", line 119 in 
_hookexec
File "/usr/lib/python3/dist-packages/pluggy/_hooks.py", line 501 in __call__
File "/usr/lib/python3/dist-packages/_pytest/main.py", line 327 in _main
File "/usr/lib/python3/dist-packages/_pytest/main.py", line 273 in 
wrap_session
File "/usr/lib/python3/dist-packages/_pytest/main.py", line 320 in 
pytest_cmdline_main
File "/usr/lib/python3/dist-packages/pluggy/_callers.py", line 102 in 
_multicall
File "/usr/lib/python3/dist-packages/pluggy/_manager.py", line 119 in 
_hookexec
File "/usr/lib/python3/dist-packages/pluggy/_hooks.py", line 501 in __call__
File "/usr/lib/python3/dist-packages/_pytest/config/__init__.py", line 175 
in main
File "/usr/lib/python3/dist-packages/_pytest/config/__init__.py", line 198 
in console_main
File "/usr/lib/python3/dist-packages/pytest/__main__.py", line 7 in 
File "", line 88 in _run_code
File "", line 198 in _run_module_as_main

  Full build log
  ==
  
https://launchpad.net/ubuntu/+source/pygobject/3.47.0-3build1/+latestbuild/armhf

To manage notifications about this bug go to:
https://bugs.launchpad.net/gobject-introspection/+bug/2056753/+subscriptions


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


[Touch-packages] [Bug 2056753] Re: pygobject FTBFS on armhf: time_t build test failure

2024-03-11 Thread Jeremy Bícha
** Tags added: update-excuse

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pygobject in Ubuntu.
https://bugs.launchpad.net/bugs/2056753

Title:
  pygobject FTBFS on armhf: time_t build test failure

Status in pygobject package in Ubuntu:
  Triaged

Bug description:
  pygobject fails to build on armhf, the only Ubuntu 32-bit architecture
  that has done the time_t transition.

  test_gi.py runs a time_t test that I believe is using functions in
  glib2.0

  Test log excerpt
  

  tests/test_gi.py ... [ 
21%]
  .
  --- stderr ---
  Fatal Python error: Aborted

  Current thread 0xf785e020 (most recent call first):
File "/<>/tests/test_gi.py", line 579 in test_time_t_in
File "/usr/lib/python3.12/unittest/case.py", line 589 in _callTestMethod
File "/usr/lib/python3.12/unittest/case.py", line 634 in run
File "/usr/lib/python3.12/unittest/case.py", line 690 in __call__
File "/usr/lib/python3/dist-packages/_pytest/unittest.py", line 338 in 
runtest
File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 170 in 
pytest_runtest_call
File "/usr/lib/python3/dist-packages/pluggy/_callers.py", line 102 in 
_multicall
File "/usr/lib/python3/dist-packages/pluggy/_manager.py", line 119 in 
_hookexec
File "/usr/lib/python3/dist-packages/pluggy/_hooks.py", line 501 in __call__
File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 263 in 

File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 342 in 
from_call
File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 262 in 
call_runtest_hook
File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 223 in 
call_and_report
File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 134 in 
runtestprotocol
File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 115 in 
pytest_runtest_protocol
File "/usr/lib/python3/dist-packages/pluggy/_callers.py", line 102 in 
_multicall
File "/usr/lib/python3/dist-packages/pluggy/_manager.py", line 119 in 
_hookexec
File "/usr/lib/python3/dist-packages/pluggy/_hooks.py", line 501 in __call__
File "/usr/lib/python3/dist-packages/_pytest/main.py", line 352 in 
pytest_runtestloop
File "/usr/lib/python3/dist-packages/pluggy/_callers.py", line 102 in 
_multicall
File "/usr/lib/python3/dist-packages/pluggy/_manager.py", line 119 in 
_hookexec
File "/usr/lib/python3/dist-packages/pluggy/_hooks.py", line 501 in __call__
File "/usr/lib/python3/dist-packages/_pytest/main.py", line 327 in _main
File "/usr/lib/python3/dist-packages/_pytest/main.py", line 273 in 
wrap_session
File "/usr/lib/python3/dist-packages/_pytest/main.py", line 320 in 
pytest_cmdline_main
File "/usr/lib/python3/dist-packages/pluggy/_callers.py", line 102 in 
_multicall
File "/usr/lib/python3/dist-packages/pluggy/_manager.py", line 119 in 
_hookexec
File "/usr/lib/python3/dist-packages/pluggy/_hooks.py", line 501 in __call__
File "/usr/lib/python3/dist-packages/_pytest/config/__init__.py", line 175 
in main
File "/usr/lib/python3/dist-packages/_pytest/config/__init__.py", line 198 
in console_main
File "/usr/lib/python3/dist-packages/pytest/__main__.py", line 7 in 
File "", line 88 in _run_code
File "", line 198 in _run_module_as_main

  Full build log
  ==
  
https://launchpad.net/ubuntu/+source/pygobject/3.47.0-3build1/+latestbuild/armhf

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


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


[Touch-packages] [Bug 2056753] [NEW] pygobject FTBFS on armhf: time_t build test failure

2024-03-11 Thread Jeremy Bícha
Public bug reported:

pygobject fails to build on armhf, the only Ubuntu 32-bit architecture
that has done the time_t transition.

test_gi.py runs a time_t test that I believe is using functions in
glib2.0

Test log excerpt


tests/test_gi.py ... [ 21%]
.
--- stderr ---
Fatal Python error: Aborted

Current thread 0xf785e020 (most recent call first):
  File "/<>/tests/test_gi.py", line 579 in test_time_t_in
  File "/usr/lib/python3.12/unittest/case.py", line 589 in _callTestMethod
  File "/usr/lib/python3.12/unittest/case.py", line 634 in run
  File "/usr/lib/python3.12/unittest/case.py", line 690 in __call__
  File "/usr/lib/python3/dist-packages/_pytest/unittest.py", line 338 in runtest
  File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 170 in 
pytest_runtest_call
  File "/usr/lib/python3/dist-packages/pluggy/_callers.py", line 102 in 
_multicall
  File "/usr/lib/python3/dist-packages/pluggy/_manager.py", line 119 in 
_hookexec
  File "/usr/lib/python3/dist-packages/pluggy/_hooks.py", line 501 in __call__
  File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 263 in 
  File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 342 in from_call
  File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 262 in 
call_runtest_hook
  File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 223 in 
call_and_report
  File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 134 in 
runtestprotocol
  File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 115 in 
pytest_runtest_protocol
  File "/usr/lib/python3/dist-packages/pluggy/_callers.py", line 102 in 
_multicall
  File "/usr/lib/python3/dist-packages/pluggy/_manager.py", line 119 in 
_hookexec
  File "/usr/lib/python3/dist-packages/pluggy/_hooks.py", line 501 in __call__
  File "/usr/lib/python3/dist-packages/_pytest/main.py", line 352 in 
pytest_runtestloop
  File "/usr/lib/python3/dist-packages/pluggy/_callers.py", line 102 in 
_multicall
  File "/usr/lib/python3/dist-packages/pluggy/_manager.py", line 119 in 
_hookexec
  File "/usr/lib/python3/dist-packages/pluggy/_hooks.py", line 501 in __call__
  File "/usr/lib/python3/dist-packages/_pytest/main.py", line 327 in _main
  File "/usr/lib/python3/dist-packages/_pytest/main.py", line 273 in 
wrap_session
  File "/usr/lib/python3/dist-packages/_pytest/main.py", line 320 in 
pytest_cmdline_main
  File "/usr/lib/python3/dist-packages/pluggy/_callers.py", line 102 in 
_multicall
  File "/usr/lib/python3/dist-packages/pluggy/_manager.py", line 119 in 
_hookexec
  File "/usr/lib/python3/dist-packages/pluggy/_hooks.py", line 501 in __call__
  File "/usr/lib/python3/dist-packages/_pytest/config/__init__.py", line 175 in 
main
  File "/usr/lib/python3/dist-packages/_pytest/config/__init__.py", line 198 in 
console_main
  File "/usr/lib/python3/dist-packages/pytest/__main__.py", line 7 in 
  File "", line 88 in _run_code
  File "", line 198 in _run_module_as_main

Full build log
==
https://launchpad.net/ubuntu/+source/pygobject/3.47.0-3build1/+latestbuild/armhf

** Affects: pygobject (Ubuntu)
 Importance: High
 Status: Triaged


** Tags: ftbfs noble

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pygobject in Ubuntu.
https://bugs.launchpad.net/bugs/2056753

Title:
  pygobject FTBFS on armhf: time_t build test failure

Status in pygobject package in Ubuntu:
  Triaged

Bug description:
  pygobject fails to build on armhf, the only Ubuntu 32-bit architecture
  that has done the time_t transition.

  test_gi.py runs a time_t test that I believe is using functions in
  glib2.0

  Test log excerpt
  

  tests/test_gi.py ... [ 
21%]
  .
  --- stderr ---
  Fatal Python error: Aborted

  Current thread 0xf785e020 (most recent call first):
File "/<>/tests/test_gi.py", line 579 in test_time_t_in
File "/usr/lib/python3.12/unittest/case.py", line 589 in _callTestMethod
File "/usr/lib/python3.12/unittest/case.py", line 634 in run
File "/usr/lib/python3.12/unittest/case.py", line 690 in __call__
File "/usr/lib/python3/dist-packages/_pytest/unittest.py", line 338 in 
runtest
File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 170 in 
pytest_runtest_call
File "/usr/lib/python3/dist-packages/pluggy/_callers.py", line 102 in 
_multicall
File "/usr/lib/python3/dist-packages/pluggy/_manager.py", line 119 in 
_hookexec
File "/usr/lib/python3/dist-packages/pluggy/_hooks.py", line 501 in __call__
File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 263 in 

File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 342 in 
from_call
File 

[Touch-packages] [Bug 1881180] Re: drop suru-icon-theme (and use UBports' suru-icon-theme as upstream)

2024-03-07 Thread Jeremy Bícha
I dropped suru-icon-theme from the ubuntu-themes source today and synced
Debian's version of suru-icon-theme.

** Changed in: ubuntu-themes (Ubuntu)
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu.
https://bugs.launchpad.net/bugs/1881180

Title:
  drop suru-icon-theme (and use UBports' suru-icon-theme as upstream)

Status in ubuntu-themes package in Ubuntu:
  Fix Released

Bug description:
  As part of the initiative of packaging Lomiri (former Unity8) for
  Debian, I have just created a standalone source project for suru-icon-
  theme [1]. This will soon be packaged for and uploaded to Debian
  unstable.

  The UBports developers have added several changes to "their" suru-
  icon-theme which makes it impossible to use suru-icon-theme from the
  ubuntu-theme src:pkg on Ubuntu Touch. On the other hand, UBports'
  suru-icon-theme should still be good to go with on Ubuntu.

  Furthermore, for Debian upload, I preferred not to package the ubuntu
  specific artwork as a whole. The solution at UBports upstream was
  providing suru-icon-theme as a standalone upstream project.

  Thus, I'd like to suggest dropping suru-icon-theme from Ubuntu Theme
  (at least the bin:pkg) and use the suru-icon-theme package being
  available in Debian soon('ish (dependening on NEW queue processing)).

  The UBports devs are open to merge requests if that is required from
  time to time.

  Thanks+Greets,
  Mike (aka sunweaver at debian.org)

  [1] https://gitlab.com/ubports/core/suru-icon-theme

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


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


[Touch-packages] [Bug 2039235] Re: gnome-online-accounts -> when signing into google account, infinite loading after entering password

2024-03-07 Thread Jeremy Bícha
I am closing this issue because it is fixed in Ubuntu 24.04 LTS which is
expected to be released later in April. It was fixed by switching gnome-
online-accounts to always use your browser for log in instead of an
embedded webkit powered popup window. That kind of change is probably
too large to try to backport to Ubuntu 23.10 and our developer time is
focused now on getting Ubuntu 24.04 LTS ready.

** Changed in: gnome-online-accounts (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  gnome-online-accounts -> when signing into google account, infinite
  loading after entering password

Status in gnome-online-accounts package in Ubuntu:
  Fix Released

Bug description:
  1) What you expected to happen
  - sign in is successful, which will allow google services to populate the 
appropriate applications (calendar, mail, google drive)

  2) What actually happened
  - sign in hangs infinitely after entering the password
  - the process is able to detect that the password is correct or incorrect. 
When entering an incorrect password, it will correctly and quickly complain 
that the password is incorrect. When entering the correct password, the bug 
will occur.

  3) Steps to reproduce
    a) start the program
    b) select online accounts
    c) select google
    d) enter email
    e) enter password
    f) loads forever

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: gnome-online-accounts 3.48.0-2
  ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
  Uname: Linux 6.5.0-9-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 12 22:27:59 2023
  InstallationDate: Installed on 2023-10-12 (0 days ago)
  InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Release amd64 (20231011)
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  SourcePackage: gnome-online-accounts
  UpgradeStatus: No upgrade log present (probably fresh install)

  Hardware info (not sure if relevant):
  cpu: intel
  gpu: nvidia (driver version: "Using NVIDIA driver metapackage from 
nvidia-driver-535(proprietary, tested)")

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


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


[Touch-packages] [Bug 2055779] Re: software and updates not opening

2024-03-04 Thread Jeremy Bícha
*** This bug is a duplicate of bug 2053228 ***
https://bugs.launchpad.net/bugs/2053228

** This bug has been marked a duplicate of bug 2053228
   software-properties-gtk does not start

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

Title:
  software and updates not opening

Status in software-properties package in Ubuntu:
  Incomplete

Bug description:
  Since recent updates trying to access software sources or additional
  drivers gets no response.

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


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


[Touch-packages] [Bug 2054924] Re: color emoji are broken with fontconfig 2.15

2024-02-27 Thread Jeremy Bícha
** Changed in: fontconfig (Ubuntu)
   Status: Confirmed => Triaged

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to fontconfig in Ubuntu.
https://bugs.launchpad.net/bugs/2054924

Title:
  color emoji are broken with fontconfig 2.15

Status in Fontconfig:
  Fix Released
Status in fontconfig package in Ubuntu:
  Triaged
Status in fonts-noto-color-emoji package in Ubuntu:
  Triaged
Status in fontconfig package in Debian:
  Confirmed

Bug description:
  The Noto Color Emoji font is no longer used to show emoji. Many emoji
  no longer show and the few that do are not in color.

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


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


[Touch-packages] [Bug 2053207] Re: glib requires gobject-introspection >= 1.78.1-13

2024-02-26 Thread Jeremy Bícha
** Changed in: glib2.0 (Ubuntu)
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gobject-introspection in
Ubuntu.
https://bugs.launchpad.net/bugs/2053207

Title:
  glib requires gobject-introspection >= 1.78.1-13

Status in glib2.0 package in Ubuntu:
  Fix Released
Status in gobject-introspection package in Ubuntu:
  Fix Released

Bug description:
  glib2.0 2.79.1-1 requires gobject-introspection >= 1.78.13 to migrate
  out of noble-proposed before or at the same as glib2.0.

  I'm filing this bug to explain why glib2.0 isn't migrating despite the
  excuses page saying "Will attempt migration"

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/2053207/+subscriptions


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


[Touch-packages] [Bug 2054908] Re: gpg-wks-server pulls in postfix

2024-02-25 Thread Jeremy Bícha
** Description changed:

  Example 1
  
  I did a sudo apt dist-upgrade today on my developer machine running Ubuntu 
Desktop 24.04 LTS and it surprisingly pulled in postfix.
  
  I did not built this into a full reproducible test case because I found
  another test case…
  
  Example 2
  
  munin's autopkgtests are now failing because postfix is now unexpectedly 
being installed.
  
  https://autopkgtest.ubuntu.com/packages/munin/noble/amd64
  
  Other Info
  
- gnupg2's changelog indicates that there was an attempt to avoid this 
misbehavior by having gnupg only Suggest gpg-wks-server. In fact, there is 
**nothing** in Ubuntu that Depends or Recommends gpg-wks-server.
+ gnupg2's changelog indicates that there was an attempt to avoid this 
misbehavior by having gnupg only Suggest gpg-wks-server. In fact, there is 
**nothing** in Ubuntu 24.04 LTS that Depends or Recommends gpg-wks-server.
  
  I added a munin bug task as a pointer in case anyone wonder's about the
  autopkgtest regression but I don't believe munin needs any changes.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/2054908

Title:
  gpg-wks-server pulls in postfix

Status in Auto Package Testing:
  New
Status in apt package in Ubuntu:
  Invalid
Status in gnupg2 package in Ubuntu:
  New
Status in munin package in Ubuntu:
  Invalid
Status in ubuntu-release-upgrader package in Ubuntu:
  New

Bug description:
  Example 1
  
  I did a sudo apt dist-upgrade today on my developer machine running Ubuntu 
Desktop 24.04 LTS and it surprisingly pulled in postfix.

  I did not built this into a full reproducible test case because I
  found another test case…

  Example 2
  
  munin's autopkgtests are now failing because postfix is now unexpectedly 
being installed.

  https://autopkgtest.ubuntu.com/packages/munin/noble/amd64

  Other Info
  
  gnupg2's changelog indicates that there was an attempt to avoid this 
misbehavior by having gnupg only Suggest gpg-wks-server. In fact, there is 
**nothing** in Ubuntu 24.04 LTS that Depends or Recommends gpg-wks-server.

  I added a munin bug task as a pointer in case anyone wonder's about
  the autopkgtest regression but I don't believe munin needs any
  changes.

To manage notifications about this bug go to:
https://bugs.launchpad.net/auto-package-testing/+bug/2054908/+subscriptions


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


[Touch-packages] [Bug 2054924] Re: color emoji are broken with fontconfig 2.15

2024-02-25 Thread Jeremy Bícha
** Also affects: fonts-noto-color-emoji (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: fonts-noto-color-emoji (Ubuntu)
   Importance: Undecided => High

** Changed in: fonts-noto-color-emoji (Ubuntu)
   Status: New => Triaged

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to fontconfig in Ubuntu.
https://bugs.launchpad.net/bugs/2054924

Title:
  color emoji are broken with fontconfig 2.15

Status in Fontconfig:
  Fix Released
Status in fontconfig package in Ubuntu:
  Triaged
Status in fonts-noto-color-emoji package in Ubuntu:
  Triaged
Status in fontconfig package in Debian:
  New

Bug description:
  The Noto Color Emoji font is no longer used to show emoji. Many emoji
  no longer show and the few that do are not in color.

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


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


[Touch-packages] [Bug 2054924] Re: color emoji are broken with fontconfig 2.15

2024-02-25 Thread Jeremy Bícha
** Summary changed:

- color emoji is broken with fontconfig 2.15
+ color emoji are broken with fontconfig 2.15

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to fontconfig in Ubuntu.
https://bugs.launchpad.net/bugs/2054924

Title:
  color emoji are broken with fontconfig 2.15

Status in Fontconfig:
  Unknown
Status in fontconfig package in Ubuntu:
  Triaged
Status in fontconfig package in Debian:
  Unknown

Bug description:
  The Noto Color Emoji font is no longer used to show emoji. Many emoji
  no longer show and the few that do are not in color.

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


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


[Touch-packages] [Bug 2054924] [NEW] color emoji is broken with fontconfig 2.15

2024-02-25 Thread Jeremy Bícha
Public bug reported:

The Noto Color Emoji font is no longer used to show emoji. Many emoji no
longer show and the few that do are not in color.

** Affects: fontconfig
 Importance: Unknown
 Status: Unknown

** Affects: fontconfig (Ubuntu)
 Importance: High
 Status: Triaged

** Affects: fontconfig (Debian)
 Importance: Unknown
 Status: Unknown


** Tags: noble

** Bug watch added: gitlab.freedesktop.org/fontconfig/fontconfig/-/issues #400
   https://gitlab.freedesktop.org/fontconfig/fontconfig/-/issues/400

** Also affects: fontconfig via
   https://gitlab.freedesktop.org/fontconfig/fontconfig/-/issues/400
   Importance: Unknown
   Status: Unknown

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

** Also affects: fontconfig (Debian) via
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064267
   Importance: Unknown
   Status: Unknown

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to fontconfig in Ubuntu.
https://bugs.launchpad.net/bugs/2054924

Title:
  color emoji is broken with fontconfig 2.15

Status in Fontconfig:
  Unknown
Status in fontconfig package in Ubuntu:
  Triaged
Status in fontconfig package in Debian:
  Unknown

Bug description:
  The Noto Color Emoji font is no longer used to show emoji. Many emoji
  no longer show and the few that do are not in color.

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


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


[Touch-packages] [Bug 2054908] Re: gpg-wks-server pulls in postfix

2024-02-25 Thread Jeremy Bícha
** Description changed:

  Example 1
  
  I did a sudo apt dist-upgrade today on my developer machine running Ubuntu 
Desktop 24.04 LTS and it surprisingly pulled in postfix.
  
  I did not built this into a full reproducible test case because I found
  another test case…
  
  Example 2
  
  munin's autopkgtests are now failing because postfix and gpg-wks-server is 
now unexpectedly being installed.
  
  https://autopkgtest.ubuntu.com/packages/munin/noble/amd64
  
  Other Info
  
  gnupg2's changelog indicates that there was an attempt to avoid this 
misbehavior by having gnupg only Suggest gpg-wks-server. In fact, there is 
**nothing** in Ubuntu that Depends or Recommends gpg-wks-server.
  
- Notably, gnupg has
- Suggests: gpg-wks-server (<< 2.4.4-2ubuntu7.1~), gpg-wks-server (>= 
2.4.4-2ubuntu7)
- 
- I don't recall ever seeing strict versioned Suggests before so it's my
- wild guess that apt does not strict handle versioned Suggests in the
- expected way.
- 
- As a workaround, try dropping the versions from gnupg's Suggests.
- 
- But the true fix may be in apt.
- 
  I added a munin bug task as a pointer in case anyone wonder's about the
  autopkgtest regression but I don't believe munin needs any changes.

** Description changed:

  Example 1
  
  I did a sudo apt dist-upgrade today on my developer machine running Ubuntu 
Desktop 24.04 LTS and it surprisingly pulled in postfix.
  
  I did not built this into a full reproducible test case because I found
  another test case…
  
  Example 2
  
- munin's autopkgtests are now failing because postfix and gpg-wks-server is 
now unexpectedly being installed.
+ munin's autopkgtests are now failing because postfix is now unexpectedly 
being installed.
  
  https://autopkgtest.ubuntu.com/packages/munin/noble/amd64
  
  Other Info
  
  gnupg2's changelog indicates that there was an attempt to avoid this 
misbehavior by having gnupg only Suggest gpg-wks-server. In fact, there is 
**nothing** in Ubuntu that Depends or Recommends gpg-wks-server.
  
  I added a munin bug task as a pointer in case anyone wonder's about the
  autopkgtest regression but I don't believe munin needs any changes.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/2054908

Title:
  gpg-wks-server pulls in postfix

Status in Auto Package Testing:
  New
Status in apt package in Ubuntu:
  Invalid
Status in gnupg2 package in Ubuntu:
  Invalid
Status in munin package in Ubuntu:
  Invalid
Status in ubuntu-release-upgrader package in Ubuntu:
  New

Bug description:
  Example 1
  
  I did a sudo apt dist-upgrade today on my developer machine running Ubuntu 
Desktop 24.04 LTS and it surprisingly pulled in postfix.

  I did not built this into a full reproducible test case because I
  found another test case…

  Example 2
  
  munin's autopkgtests are now failing because postfix is now unexpectedly 
being installed.

  https://autopkgtest.ubuntu.com/packages/munin/noble/amd64

  Other Info
  
  gnupg2's changelog indicates that there was an attempt to avoid this 
misbehavior by having gnupg only Suggest gpg-wks-server. In fact, there is 
**nothing** in Ubuntu that Depends or Recommends gpg-wks-server.

  I added a munin bug task as a pointer in case anyone wonder's about
  the autopkgtest regression but I don't believe munin needs any
  changes.

To manage notifications about this bug go to:
https://bugs.launchpad.net/auto-package-testing/+bug/2054908/+subscriptions


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


[Touch-packages] [Bug 2054908] Re: gpg-wks-server pulls in postfix

2024-02-25 Thread Jeremy Bícha
Ok, pulling in postfix is very disruptive since gpg-wks-client was
seeded in Ubuntu Desktop 22.04 LTS and 23.10 and several flavors.
postfix's install has a debconf prompt which is now allowed for the
default desktop install.

** Summary changed:

- gnupg is pulling in gpg-wks-server which pulls in postfix
+ gpg-wks-server pulls in postfix

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/2054908

Title:
  gpg-wks-server pulls in postfix

Status in Auto Package Testing:
  New
Status in apt package in Ubuntu:
  Invalid
Status in gnupg2 package in Ubuntu:
  Invalid
Status in munin package in Ubuntu:
  Invalid
Status in ubuntu-release-upgrader package in Ubuntu:
  New

Bug description:
  Example 1
  
  I did a sudo apt dist-upgrade today on my developer machine running Ubuntu 
Desktop 24.04 LTS and it surprisingly pulled in postfix.

  I did not built this into a full reproducible test case because I
  found another test case…

  Example 2
  
  munin's autopkgtests are now failing because postfix and gpg-wks-server is 
now unexpectedly being installed.

  https://autopkgtest.ubuntu.com/packages/munin/noble/amd64

  Other Info
  
  gnupg2's changelog indicates that there was an attempt to avoid this 
misbehavior by having gnupg only Suggest gpg-wks-server. In fact, there is 
**nothing** in Ubuntu that Depends or Recommends gpg-wks-server.

  Notably, gnupg has
  Suggests: gpg-wks-server (<< 2.4.4-2ubuntu7.1~), gpg-wks-server (>= 
2.4.4-2ubuntu7)

  I don't recall ever seeing strict versioned Suggests before so it's my
  wild guess that apt does not strict handle versioned Suggests in the
  expected way.

  As a workaround, try dropping the versions from gnupg's Suggests.

  But the true fix may be in apt.

  I added a munin bug task as a pointer in case anyone wonder's about
  the autopkgtest regression but I don't believe munin needs any
  changes.

To manage notifications about this bug go to:
https://bugs.launchpad.net/auto-package-testing/+bug/2054908/+subscriptions


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


[Touch-packages] [Bug 2054908] [NEW] gnupg is pulling in gpg-wks-server which pulls in postfix

2024-02-24 Thread Jeremy Bícha
Public bug reported:

Example 1

I did a sudo apt dist-upgrade today on my developer machine running Ubuntu 
Desktop 24.04 LTS and it surprisingly pulled in postfix.

I did not built this into a full reproducible test case because I found
another test case…

Example 2

munin's autopkgtests are now failing because postfix and gpg-wks-server is now 
unexpectedly being installed.

https://autopkgtest.ubuntu.com/packages/munin/noble/amd64

Other Info

gnupg2's changelog indicates that there was an attempt to avoid this 
misbehavior by having gnupg only Suggest gpg-wks-server. In fact, there is 
**nothing** in Ubuntu that Depends or Recommends gpg-wks-server.

Notably, gnupg has
Suggests: gpg-wks-server (<< 2.4.4-2ubuntu7.1~), gpg-wks-server (>= 
2.4.4-2ubuntu7)

I don't recall ever seeing strict versioned Suggests before so it's my
wild guess that apt does not strict handle versioned Suggests in the
expected way.

As a workaround, try dropping the versions from gnupg's Suggests.

But the true fix may be in apt.

I added a munin bug task as a pointer in case anyone wonder's about the
autopkgtest regression but I don't believe munin needs any changes.

** Affects: apt (Ubuntu)
 Importance: High
 Status: New

** Affects: gnupg2 (Ubuntu)
 Importance: High
 Status: New

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


** Tags: noble update-excuse

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

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

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

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

** Tags added: update-excuse

** Description changed:

  Example 1
  
  I did a sudo apt dist-upgrade today on my developer machine running Ubuntu 
Desktop 24.04 LTS and it surprisingly pulled in postfix.
  
  I did not built this into a full reproducible test case because I found
  another test case…
  
  Example 2
  
  munin's autopkgtests are now failing because postfix and gpg-wks-server is 
now unexpectedly being installed.
  
  https://autopkgtest.ubuntu.com/packages/munin/noble/amd64
  
  Other Info
  
  gnupg2's changelog indicates that there was an attempt to avoid this 
misbehavior by having gnupg only Suggest gpg-wks-server. In fact, there is 
**nothing** in Ubuntu that Depends or Recommends gpg-wks-server.
  
  Notably, gnupg has
  Suggests: gpg-wks-server (<< 2.4.4-2ubuntu7.1~), gpg-wks-server (>= 
2.4.4-2ubuntu7)
  
  I don't recall ever seeing versioned Suggests before so it's my wild
- guess that maybe apt does not handle versioned Suggests in the expected
- way.
+ guess that apt does not handle versioned Suggests in the expected way.
  
- As a workaround, try dropping the versions from the Suggests.
+ As a workaround, try dropping the versions from gnupg's Suggests.
  
- But the ultimate fix may be in apt.
+ But the true fix may be in apt.
+ 
+ I added a munin bug task as a pointer in case anyone wonder's about the
+ autopkgtest regression but I don't believe munin needs any changes.

** Description changed:

  Example 1
  
  I did a sudo apt dist-upgrade today on my developer machine running Ubuntu 
Desktop 24.04 LTS and it surprisingly pulled in postfix.
  
  I did not built this into a full reproducible test case because I found
  another test case…
  
  Example 2
  
  munin's autopkgtests are now failing because postfix and gpg-wks-server is 
now unexpectedly being installed.
  
  https://autopkgtest.ubuntu.com/packages/munin/noble/amd64
  
  Other Info
  
  gnupg2's changelog indicates that there was an attempt to avoid this 
misbehavior by having gnupg only Suggest gpg-wks-server. In fact, there is 
**nothing** in Ubuntu that Depends or Recommends gpg-wks-server.
  
  Notably, gnupg has
  Suggests: gpg-wks-server (<< 2.4.4-2ubuntu7.1~), gpg-wks-server (>= 
2.4.4-2ubuntu7)
  
- I don't recall ever seeing versioned Suggests before so it's my wild
- guess that apt does not handle versioned Suggests in the expected way.
+ I don't recall ever seeing strict versioned Suggests before so it's my
+ wild guess that apt does not strict handle versioned Suggests in the
+ expected way.
  
  As a workaround, try dropping the versions from gnupg's Suggests.
  
  But the true fix may be in apt.
  
  I added a munin bug task as a pointer in case anyone wonder's about the
  autopkgtest regression but I don't believe munin needs any changes.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/2054908

Title:
  gnupg is pulling in gpg-wks-server which pulls in postfix

Status in apt package in Ubuntu:
  New
Status in gnupg2 package in Ubuntu:
  New
Status in munin package in Ubuntu:
  Triaged

Bug description:
  Example 1
  
  I did a sudo apt dist-upgrade today on my developer machine 

[Touch-packages] [Bug 2054902] [NEW] apport test error: /bin/bash not found

2024-02-24 Thread Jeremy Bícha
Public bug reported:

This looks like fallout from the completion of usrmerge.

https://autopkgtest.ubuntu.com/packages/apport


=== FAILURES ===
367s ___ T.test_get_file_package 

367s 
367s self = 
367s 
367s def test_get_file_package(self):
367s """get_file_package() on installed files."""
367s >   self.assertEqual(impl.get_file_package("/bin/bash"), "bash")
367s E   AssertionError: None != 'bash'
367s 
367s tests/integration/test_packaging_apt_dpkg.py:158: AssertionError
367s ___ T.test_get_files 
___
367s 
367s self = 
367s 
367s def test_get_files(self):
367s """get_files()."""
367s self.assertRaises(ValueError, impl.get_files, "nonexisting")
367s >   self.assertIn("/bin/bash", impl.get_files("bash"))
367s E   AssertionError: '/bin/bash' not found in ['/.', '/etc', 
'/etc/bash.bashrc', '/etc/skel', '/etc/skel/.bash_logout', '/etc/skel/.bashrc', 
'/etc/skel/.profile', '/usr', '/usr/bin', '/usr/bin/bash', '/usr/bin/bashbug',

** Affects: apport (Ubuntu)
 Importance: High
 Status: New


** Tags: noble update-excuse

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/2054902

Title:
  apport test error: /bin/bash not found

Status in apport package in Ubuntu:
  New

Bug description:
  This looks like fallout from the completion of usrmerge.

  https://autopkgtest.ubuntu.com/packages/apport

  
  === FAILURES 
===
  367s ___ T.test_get_file_package 

  367s 
  367s self = 
  367s 
  367s def test_get_file_package(self):
  367s """get_file_package() on installed files."""
  367s >   self.assertEqual(impl.get_file_package("/bin/bash"), "bash")
  367s E   AssertionError: None != 'bash'
  367s 
  367s tests/integration/test_packaging_apt_dpkg.py:158: AssertionError
  367s ___ T.test_get_files 
___
  367s 
  367s self = 
  367s 
  367s def test_get_files(self):
  367s """get_files()."""
  367s self.assertRaises(ValueError, impl.get_files, "nonexisting")
  367s >   self.assertIn("/bin/bash", impl.get_files("bash"))
  367s E   AssertionError: '/bin/bash' not found in ['/.', '/etc', 
'/etc/bash.bashrc', '/etc/skel', '/etc/skel/.bash_logout', '/etc/skel/.bashrc', 
'/etc/skel/.profile', '/usr', '/usr/bin', '/usr/bin/bash', '/usr/bin/bashbug',

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


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


[Touch-packages] [Bug 1892997] Re: libgirepository-1.0-1_1.64.1-1build2 cause gnome-shell problem

2024-02-19 Thread Jeremy Bícha
Ubuntu 20.10 is no longer supported and this bug does not have enough
details.

** Changed in: gobject-introspection (Ubuntu)
   Status: New => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gobject-introspection in
Ubuntu.
https://bugs.launchpad.net/bugs/1892997

Title:
  libgirepository-1.0-1_1.64.1-1build2 cause gnome-shell problem

Status in gobject-introspection package in Ubuntu:
  Invalid

Bug description:
  libgirepository-1.0-1_1.64.1-1build2_amd64.deb cause gnome-shell
  problem on ubuntu 20.10

  Aug 26 14:32:19 youling257-Default-string kernel: [8.570168]
  gnome-shell[1365]: segfault at 7f7d870a3b10 ip 7f7d870a21dd sp
  7ffd7eb6c640 error 7 in libgjs.so.0.0.0[7f7d8707c000+87000]

  Aug 26 14:32:19 youling257-Default-string kernel: [8.570172] Code:
  bd 50 fd ff ff 03 48 89 85 20 fd ff ff 0f 85 05 ff ff ff 48 8b 85 20
  fd ff ff 48 8b 00 48 85 c0 0f 84 17 ff ff ff 48 8b 78 28 <83> 2f 01 0f
  84 3e 07 00 00 48 8b 85 20 fd ff ff 48 c7 00 00 00 00

  libgirepository-1.0-1_1.64.1-1_amd64.deb no this problem on ubuntu
  20.10

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gobject-introspection/+bug/1892997/+subscriptions


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


[Touch-packages] [Bug 1174810] Re: configure or patch gobject-introspection to include /usr/local in typelib search path

2024-02-19 Thread Jeremy Bícha
** Changed in: gobject-introspection (Ubuntu)
   Importance: Undecided => Low

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gobject-introspection in
Ubuntu.
https://bugs.launchpad.net/bugs/1174810

Title:
  configure or patch gobject-introspection to include /usr/local in
  typelib search path

Status in GObject Introspection:
  Won't Fix
Status in gobject-introspection package in Ubuntu:
  Triaged

Bug description:
  Ubuntu includes /usr/local/lib in the library search path via a file
  in /etc/ld.so.conf.d, and also configures pkg-config to look for .pc
  files in /usr/local/lib/pkgconfig.  But gobject-introspection's built-
  in search path looks for type libraries only in /usr, not in
  /usr/local.  That's inconsistent: I can install shared libraries in
  /usr/local and programs will find them, but their type libraries will
  not be found.

  For consistency, I think Ubuntu should set the default gobject-
  introspection search path to include /usr/local/lib/girepository-1.0.
  It would be nice if gobject-introspection had a configure option that
  could set that (see
  https://bugzilla.gnome.org/show_bug.cgi?id=699331).  In the meantime,
  it wouldn't be hard to patch gobject-introspection to set the default
  path; see init_globals() in girepository.c.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gobject-introspection/+bug/1174810/+subscriptions


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


[Touch-packages] [Bug 1812223] Re: gir test fail on ppc64el

2024-02-19 Thread Jeremy Bícha
** Changed in: gobject-introspection (Ubuntu)
   Status: New => Fix Released

** Changed in: gcc-8 (Ubuntu)
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gobject-introspection in
Ubuntu.
https://bugs.launchpad.net/bugs/1812223

Title:
  gir test fail on ppc64el

Status in Meson:
  New
Status in gcc-8 package in Ubuntu:
  Fix Released
Status in gobject-introspection package in Ubuntu:
  Fix Released
Status in meson package in Ubuntu:
  Fix Released

Bug description:
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-
  disco/disco/ppc64el/m/meson/20190116_031026_4df33@/log.gz

  ninja explain: genmarshal/genmarshalprog is dirty
  [1/75] Generating simple-resources_c with a custom command.
  [2/75] Generating simple-resources_h with a custom command.
  [3/75] Generating res3 with a meson_exe.py custom command.
  [4/75] Compiling C object 
'resources/41d311a@@simple-resources-test@exe/meson-generated_.._simple-resources.c.o'.
  [5/75] Compiling C object 
'resources/41d311a@@simple-resources-test@exe/simple-main.c.o'.
  [6/75] Generating simple-resources_gresource with a custom command.
  [7/75] Generating generated-resources_c with a custom command.
  [8/75] Generating generated-resources_h with a custom command.
  [9/75] Linking target resources/simple-resources-test.
  [10/75] Compiling C object 
'resources/41d311a@@generated-resources-test@exe/meson-generated_.._generated-resources.c.o'.
  [11/75] Generating build-resources_gresource with a custom command.
  [12/75] Compiling C object 
'resources/41d311a@@generated-resources-test@exe/generated-main.c.o'.
  [13/75] Linking target resources/generated-resources-test.
  [14/75] Compiling C object 'gir/dep1/dep2/7cbf35a@@dep2lib@sha/dep2.c.o'.
  [15/75] Linking target gir/dep1/dep2/libdep2lib.so.
  [16/75] Compiling C object 'gir/dep1/07d7481@@dep1lib@sha/dep1.c.o'.
  [17/75] Generating symbol file 
'gir/dep1/dep2/7cbf35a@@dep2lib@sha/libdep2lib.so.symbols'.
  [18/75] Linking target gir/dep1/libdep1lib.so.
  [19/75] Generating symbol file 
'gir/dep1/07d7481@@dep1lib@sha/libdep1lib.so.symbols'.
  [20/75] Compiling C object 'gir/327a146@@gir_lib2@sha/meson-sample2.c.o'.
  [21/75] Linking target gir/libgir_lib2.so.
  [22/75] Generating gsettings-compile-schemas with a custom command.
  [23/75] Compiling C object 'schemas/fd70ea1@@schemaprog@exe/schemaprog.c.o'.
  [24/75] Linking target schemas/schemaprog.
  [25/75] Generating generated-gdbus.c with a custom command.
  [26/75] Generating generated-gdbus.h with a custom command.
  [27/75] Generating generated-gdbus-docbook with a custom command.
  [28/75] Compiling C object 
'gdbus/8d60afc@@gdbus-test@exe/meson-generated_.._generated-gdbus.c.o'.
  [29/75] Compiling C object 'gdbus/8d60afc@@gdbus-test@exe/gdbusprog.c.o'.
  [30/75] Generating MesonDep2-1.0.gir with a custom command.
  g-ir-scanner: link: cc -o 
/tmp/tmpbrjz1hlu/tmp-introspect81qm411v/MesonDep2-1.0 
/tmp/tmpbrjz1hlu/tmp-introspect81qm411v/MesonDep2-1.0.o -L. -Wl,-rpath,. 
-Wl,--no-as-needed -L/tmp/tmpbrjz1hlu/gir/dep1/dep2 
-Wl,-rpath,/tmp/tmpbrjz1hlu/gir/dep1/dep2 -lasan -ldep2lib -lgobject-2.0 
-lglib-2.0 -lgio-2.0 -lgobject-2.0 -Wl,--export-dynamic -lgmodule-2.0 -pthread 
-lglib-2.0
  [31/75] Linking target gdbus/gdbus-test.
  [32/75] Generating MesonDep2-1.0.typelib with a custom command.
  [33/75] Generating enums.h with a meson_exe.py custom command.
  [34/75] Generating enums.c with a meson_exe.py custom command.
  [35/75] Compiling C object 
'mkenums/75bf728@@enumprog1@exe/meson-generated_.._enums.c.o'.
  [36/75] Compiling C object 
'mkenums/75bf728@@enumprog1@exe/meson-generated_.._main1.c.o'.
  [37/75] Linking target mkenums/enumprog1.
  [38/75] Generating MesonDep1-1.0.gir with a custom command.
  FAILED: gir/dep1/MesonDep1-1.0.gir 
  /usr/bin/g-ir-scanner -pthread -I/usr/include/gobject-introspection-1.0 
-I/usr/include/glib-2.0 -I/usr/lib/powerpc64le-linux-gnu/glib-2.0/include 
--no-libtool --namespace=MesonDep1 --nsversion=1.0 --warn-all --output 
gir/dep1/MesonDep1-1.0.gir --c-include=dep1.h 
'-I/tmp/autopkgtest.GpLQfj/build.Rq6/src/test cases/frameworks/7 
gnome/gir/dep1' -I/tmp/tmpbrjz1hlu/gir/dep1 
--filelist=/tmp/tmpbrjz1hlu/gir/dep1/07d7481@@dep1lib@sha/MesonDep1_1.0_gir_filelist
 --include=GObject-2.0 --include=MesonDep2-1.0 --symbol-prefix=meson 
--identifier-prefix=Meson --cflags-begin -DMESON_TEST -fsanitize=address 
-fno-omit-frame-pointer -I/usr/include/glib-2.0 
-I/usr/lib/powerpc64le-linux-gnu/glib-2.0/include --cflags-end 
--add-include-path=/tmp/tmpbrjz1hlu/gir/dep1/dep2 -lasan 
-L/tmp/tmpbrjz1hlu/gir/dep1/dep2 --extra-library=dep2lib --library dep1lib 
-L/tmp/tmpbrjz1hlu/gir/dep1 --extra-library=gobject-2.0 --extra-library=glib-2.0
  g-ir-scanner: link: cc -o 
/tmp/tmpbrjz1hlu/tmp-introspectghii58n3/MesonDep1-1.0 

[Touch-packages] [Bug 2053207] Re: glib requires gobject-introspection >= 1.78.1-13

2024-02-19 Thread Jeremy Bícha
** Changed in: gobject-introspection (Ubuntu)
   Status: In Progress => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gobject-introspection in
Ubuntu.
https://bugs.launchpad.net/bugs/2053207

Title:
  glib requires gobject-introspection >= 1.78.1-13

Status in glib2.0 package in Ubuntu:
  Fix Committed
Status in gobject-introspection package in Ubuntu:
  Fix Released

Bug description:
  glib2.0 2.79.1-1 requires gobject-introspection >= 1.78.13 to migrate
  out of noble-proposed before or at the same as glib2.0.

  I'm filing this bug to explain why glib2.0 isn't migrating despite the
  excuses page saying "Will attempt migration"

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/2053207/+subscriptions


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


[Touch-packages] [Bug 2033949] Re: Does not work with Ubuntu sources in deb822 format

2024-02-17 Thread Jeremy Bícha
This did not fix the issue, but the issue is now being tracked at LP:
#2053228

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python-apt in Ubuntu.
https://bugs.launchpad.net/bugs/2033949

Title:
  Does not work with Ubuntu sources in deb822 format

Status in python-apt package in Ubuntu:
  Fix Committed
Status in software-properties package in Ubuntu:
  Fix Released
Status in python-apt source package in Mantic:
  Won't Fix
Status in software-properties source package in Mantic:
  Won't Fix

Bug description:
  On my Mantic I have sources in new deb822 format.
  Starting software-properties-gtk seems my server is Main server, but from 
/etc/apt/sources.list.d/ubuntu.sources I see server from Italy and I 
software-properties-gtk seems unable to change.

  corrado@corrado-n16-mm-0901:~$ cat /etc/apt/sources.list.d/ubuntu.sources
  Types: deb
  URIs: http://it.archive.ubuntu.com/ubuntu
  Suites: mantic mantic-updates mantic-backports
  Components: main restricted universe multiverse
  Signed-By: /usr/share/keyrings/ubuntu-archive-keyring.gpg

  Types: deb
  URIs: http://it.archive.ubuntu.com/ubuntu
  Suites: mantic-security
  Components: main restricted universe multiverse
  Signed-By: /usr/share/keyrings/ubuntu-archive-keyring.gpg

  corrado@corrado-n16-mm-0901:~$

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: software-properties-gtk 0.99.39
  ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5
  Uname: Linux 6.3.0-7-generic x86_64
  ApportVersion: 2.27.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Sep  2 10:33:12 2023
  InstallationDate: Installed on 2023-09-01 (1 days ago)
  InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230901)
  PackageArchitecture: all
  ProcEnviron:
   LANG=en_US.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/python-apt/+bug/2033949/+subscriptions


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


[Touch-packages] [Bug 2053207] Re: glib requires gobject-introspection >= 1.78.1-13

2024-02-16 Thread Jeremy Bícha
No, it does not need an epoch, but we do need to do another gobject-
introspection upload to stop building the binary packages that glib now
provides.

I have requested a review from another Debian maintainer:
https://salsa.debian.org/gnome-team/gobject-introspection/-/merge_requests/14

** Also affects: gobject-introspection (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: gobject-introspection (Ubuntu)
   Importance: Undecided => High

** Changed in: gobject-introspection (Ubuntu)
   Status: New => In Progress

** Changed in: gobject-introspection (Ubuntu)
 Assignee: (unassigned) => Jeremy Bícha (jbicha)

** Tags added: ftbfs

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gobject-introspection in
Ubuntu.
https://bugs.launchpad.net/bugs/2053207

Title:
  glib requires gobject-introspection >= 1.78.1-13

Status in glib2.0 package in Ubuntu:
  Fix Committed
Status in gobject-introspection package in Ubuntu:
  In Progress

Bug description:
  glib2.0 2.79.1-1 requires gobject-introspection >= 1.78.13 to migrate
  out of noble-proposed before or at the same as glib2.0.

  I'm filing this bug to explain why glib2.0 isn't migrating despite the
  excuses page saying "Will attempt migration"

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/2053207/+subscriptions


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


[Touch-packages] [Bug 2053207] Re: glib requires gobject-introspection >= 1.78.1-13

2024-02-15 Thread Jeremy Bícha
** Summary changed:

- Don't migrate glib yet
+ glib requires gobject-introspection >= 1.78.1-13

** Changed in: glib2.0 (Ubuntu)
   Status: Invalid => Triaged

** Tags removed: block-proposd
** Tags added: update-excuse

** Changed in: glib2.0 (Ubuntu)
   Status: Triaged => Fix Committed

** Description changed:

- .
+ glib2.0 2.79.1-1 requires gobject-introspection >= 1.78.13 to migrate
+ out of noble-proposed before or at the same as glib2.0.
+ 
+ I'm filing this bug to explain why glib2.0 isn't migrating despite the
+ excuses page saying "Will attempt migration"

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

Title:
  glib requires gobject-introspection >= 1.78.1-13

Status in glib2.0 package in Ubuntu:
  Fix Committed

Bug description:
  glib2.0 2.79.1-1 requires gobject-introspection >= 1.78.13 to migrate
  out of noble-proposed before or at the same as glib2.0.

  I'm filing this bug to explain why glib2.0 isn't migrating despite the
  excuses page saying "Will attempt migration"

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/2053207/+subscriptions


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


[Touch-packages] [Bug 2053207] [NEW] Don't migrate glib yet

2024-02-14 Thread Jeremy Bícha
Public bug reported:

.

** Affects: glib2.0 (Ubuntu)
 Importance: Undecided
 Status: Invalid


** Tags: block-proposd noble

** Changed in: glib2.0 (Ubuntu)
   Status: New => Invalid

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

Title:
  Don't migrate glib yet

Status in glib2.0 package in Ubuntu:
  Invalid

Bug description:
  .

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/2053207/+subscriptions


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


[Touch-packages] [Bug 2026885] Re: nano is not available on i386

2024-02-03 Thread Jeremy Bícha
I am subscribing ubuntu-archive in case they want to add nano to the
hard-coded i386 allowlist.

However, Ubuntu no longer supports i386 as a full architecture. It only
has limited packages to allow people to use legacy software (such as
games) that is not available for the usual 64-bit architecture.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to nano in Ubuntu.
https://bugs.launchpad.net/bugs/2026885

Title:
  nano is not available on i386

Status in nano package in Ubuntu:
  New

Bug description:
  There is no i386 Nano package in Jammy. I used Nano all the time
  including in chroots, which is where this reared its ugly head.

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


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


[Touch-packages] [Bug 2026885] Re: nano is not available on i386

2024-02-03 Thread Jeremy Bícha
** No longer affects: ubuntu-meta (Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to nano in Ubuntu.
https://bugs.launchpad.net/bugs/2026885

Title:
  nano is not available on i386

Status in nano package in Ubuntu:
  New

Bug description:
  There is no i386 Nano package in Jammy. I used Nano all the time
  including in chroots, which is where this reared its ugly head.

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


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


[Touch-packages] [Bug 2051672] Re: Merge iproute2 with the latest Debian version: 6.7.0-2 from testing/unstable (main)

2024-02-01 Thread Jeremy Bícha
** Summary changed:

- Sync iproute2 with the latest Debian version: 6.7.0-2 from testing/unstable 
(main)
+ Merge iproute2 with the latest Debian version: 6.7.0-2 from testing/unstable 
(main)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to iproute2 in Ubuntu.
https://bugs.launchpad.net/bugs/2051672

Title:
  Merge iproute2 with the latest Debian version: 6.7.0-2 from
  testing/unstable (main)

Status in iproute2 package in Ubuntu:
  New

Bug description:
  A few versions have been released and Ubuntu Noble still has the 6.1
  version (6.1.0-1ubuntu2) from one year ago. Could it be possible to
  import the latest version from Debian unstable fixing a bunch of
  issues and supporting features from more recent kernels?

  Please note that Ubuntu Noble 24.04 will probably be shipped with the
  v6.8 kernel [1]. IPRoute v6.1 supports features added up to the v6.1
  kernel, so missing the ones added to earlier versions. Switching to
  the v6.7 now should ease the upgrade to the v6.8 later.

  [1] https://discourse.ubuntu.com/t/introducing-kernel-6-8-for-
  the-24-04-noble-numbat-release/41958

  Upstream ChangeLog:

  - 6.2: https://lore.kernel.org/netdev/20230220105811.674bd304@hermes.local/
  - 6.3: https://lore.kernel.org/netdev/20230427090253.7a92616b@hermes.local/
  - 6.4: https://lore.kernel.org/netdev/20230626093137.2f302acc@hermes.local/
  - 6.5: https://lore.kernel.org/netdev/20230906093918.394a1b1d@hermes.local/
  - 6.6: https://lore.kernel.org/netdev/20231106090325.07092c87@hermes.local/
  - 6.7: https://lore.kernel.org/netdev/20240108094709.050e22bc@hermes.local/

  (Previous changelog:
  
https://lore.kernel.org/netdev/?q=s%3A%22%5BANNOUNCE%5D+iproute2%22+AND+NOT+s%3A%22Re%3A%22
  )

  ChangeLog from Debian:

  iproute2 (6.7.0-2) unstable; urgency=medium

    * Backport fix for 'ss' output

   -- Luca Boccassi <>  Mon, 22 Jan 2024 12:24:29 +

  iproute2 (6.7.0-1) unstable; urgency=medium

    * Add Italian debconf translation (Closes: #1056582)
    * Update upstream source from tag 'upstream/6.7.0'
    * Bump copyright year ranges in d/copyright
    * Drop 0002-Revert-Makefile-ensure-CONF_USR_DIR-honours-the-libd.patch,
  merged upstream
    * Default config files moved from /usr/lib to /usr/share

   -- Luca Boccassi <>  Fri, 12 Jan 2024 21:47:59 +

  iproute2 (6.6.0-1) unstable; urgency=medium

    * Update upstream source from tag 'upstream/6.6.0'
    * Backport patch to fix configuration installation
    * Remove handling of qt_atm.so, dropped upstream

   -- Luca Boccassi <>  Sun, 05 Nov 2023 22:46:20 +

  iproute2 (6.5.0-5) unstable; urgency=medium

    * Use dh-sequence-movetousr

   -- Luca Boccassi <>  Tue, 24 Oct 2023 15:24:01 +0100

  iproute2 (6.5.0-4) unstable; urgency=medium

    * postinst: handle legacy config files only when upgrading from previous
  versions that shipped them
    * postinst: ensure that locally modified legacy config files are
  preserved as overrides on upgrade (Closes: #1051577)
    * Note configuration files location changes in NEWS

   -- Luca Boccassi <>  Sat, 16 Sep 2023 18:58:51 +0100

  iproute2 (6.5.0-3) unstable; urgency=medium

    * Remove further leftovers as part of upstream's move of config to /usr
  (Closes: #1051577)

   -- Luca Boccassi <>  Mon, 11 Sep 2023 09:42:12 +0100

  iproute2 (6.5.0-2) unstable; urgency=medium

    * Add maintscript to remove conffiles that upstream has moved to /usr
  (Closes: #1051577)

   -- Luca Boccassi <>  Sun, 10 Sep 2023 21:28:28 +0100

  iproute2 (6.5.0-1) unstable; urgency=medium

    [ Luca Boccassi ]
    * Use wildcard for Lintian overrides

    [ Peter Kvillegård ]
    * Add Swedish translation of debconf messages (Closes: #1050442)

    [ Luca Boccassi ]
    * Update upstream source from tag 'upstream/6.5.0'
    * Use cap_bpf instead of cap_sys_admin for ip vrf-exec
    * Package-provided config files are now shipped in /usr/iproute2 instead
  of /etc/iproute2

   -- Luca Boccassi <>  Sat, 09 Sep 2023 16:32:54 +0100

  iproute2 (6.4.0-1) unstable; urgency=medium

    * Fix patch header Forwarded field
    * Enable ELF metadata stamping
    * Update upstream source from tag 'upstream/6.4.0'
    * Update Lintian overrides

   -- Luca Boccassi <>  Fri, 30 Jun 2023 12:16:40 +0100

  iproute2 (6.3.0-1) unstable; urgency=medium

    * Drop obsolete conflicts/replaces
    * Update upstream source from tag 'upstream/6.3.0'

   -- Luca Boccassi <>  Tue, 13 Jun 2023 23:49:37 +0100

  iproute2 (6.1.0-3) unstable; urgency=medium

    * Ensure 'ip mo' resolves to 'ip monitor' (Closes: #1036534)

   -- Luca Boccassi <>  Mon, 22 May 2023 14:19:52 +0100

  iproute2 (6.1.0-2) unstable; urgency=medium

    * Add Romanian language translation for debconf (Closes: #1031917)
    * Bump Standards-Version to 4.6.2, no changes
    * Bump d/copyright year range

   -- Luca Boccassi <>  Sat, 25 Feb 2023 19:46:35 +

To 

[Touch-packages] [Bug 2051454] Re: pipewire wireplumber can not detect the sound output device when using an unofficial linux kernel

2024-01-29 Thread Jeremy Bícha
** Changed in: pipewire (Ubuntu)
   Importance: Undecided => High

** Changed in: pipewire (Ubuntu)
   Status: Confirmed => In Progress

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/2051454

Title:
  pipewire wireplumber can not detect the sound output device  when
  using an unofficial linux kernel

Status in apparmor package in Ubuntu:
  Confirmed
Status in pipewire package in Ubuntu:
  In Progress
Status in wireplumber package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 24.04 noble

  I tested on Kernel-6.7.2, 6.7.1, 6.6.8, don't work.

  relating service status:
   
  gsd-media-keys[6441]: gvc_mixer_card_get_index: assertion 'GVC_IS_MIXER_CARD 
(card)' failed

  pipewire-pulse[5768]: mod.protocol-pulse: client 0x5e701af4f9a0 [Mutter]: 
ERROR command:-1 (invalid) tag:418 error:25 (Input/output error)
  pipewire-pulse[5768]: mod.protocol-pulse: client 0x5e701af4f9a0 [Mutter]: 
ERROR command:-1 (invalid) tag:426 error:25 (Input/output error)
  pipewire-pulse[5298]: default: snap_get_audio_permissions: failed to get the 
AppArmor info.

  wireplumber[61568]:  si-standard-link: 
in/out items are not valid anymore
  wireplumber[61568]:  2 of 2 PipeWire links 
failed to activate

  It's worked on kernel linux-image-6.5.0-14-generic.

  I built the same version 1.0.1 from the
  https://gitlab.freedesktop.org/pipewire source code, The sound card
  can be detected normally and shown in the gnome setting.

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


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


[Touch-packages] [Bug 2047705] Re: Packaging ships /etc/gtk-3.0/settings.ini, forcing the GTK3 theme to Yaru and preventing flavors from overriding it with XDG configuration

2024-01-19 Thread Jeremy Bícha
** Changed in: gtk+3.0 (Ubuntu)
   Status: Confirmed => Incomplete

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

Title:
  Packaging ships /etc/gtk-3.0/settings.ini, forcing the GTK3 theme to
  Yaru and preventing flavors from overriding it with XDG configuration

Status in gtk+3.0 package in Ubuntu:
  Incomplete
Status in lxqt-session package in Ubuntu:
  Fix Released

Bug description:
  Lubuntu uses Qt as the primary framework for most of the apps we ship.
  However, some functionality we ship in Lubuntu doesn't have a Qt
  application that provides that functionality, so we have some GTK3
  apps that we ship as well. Starting in Lubuntu 24.04, we are adding
  and enabling the breeze-gtk-theme package, providing more uniform
  theming between Qt and GTK apps on Lubuntu. However, this bug makes
  this impossible.

  As we do not ship xsettingsd, but instead use the XDG specification
  for shipping configuration, we are attempting to place the default
  configuration files for GTK2 and GTK3 theming in /etc/xdg/xdg-
  Lubuntu/gtk-2.0/gtkrc and /etc/xdg/xdg-Lubuntu/gtk-3.0/settings.ini.
  This solutions works for GTK2 apps, however GTK3 apps silently ignore
  the vendored configuration file and are using a different theme.

  As it turns out, this is because the /etc directory is given higher
  priority than /etc/xdg/xdg-Lubuntu when searching for XDG
  configuration files, and as it happens, libgtk-3-0 ships a
  /etc/gtk-3.0/settings.ini file that sets Yaru as the default theme.
  GTK3 applications end up selecting this configuration file rather than
  /etc/xdg/xdg-Lubuntu/gtk-3.0/settings.ini.

  /etc/gtk-3.0 is, I would argue, *not* a place where GTK3's
  settings.ini file should go, as it makes it difficult for flavors who
  rely on XDG configuration to override it without risking a file
  conflict. (Technically I guess a flavor package *could* use dpkg-
  divert to simply "get rid of" the /etc/gtk-3.0/settings.ini file, but
  that seems like the wrong way to approach this.)

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: libgtk-3-0 3.24.38-5ubuntu2
  ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
  Uname: Linux 6.5.0-9-generic x86_64
  ApportVersion: 2.27.0-0ubuntu6
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: LXQt
  Date: Fri Dec 29 10:08:23 2023
  InstallationDate: Installed on 2023-10-22 (69 days ago)
  InstallationMedia: Lubuntu 23.10 "Mantic Minotaur" - Release amd64 (20231010)
  SourcePackage: gtk+3.0
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/2047705/+subscriptions


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


[Touch-packages] [Bug 2043915] Re: Booting into live session results in try/install page white screen

2024-01-16 Thread Jeremy Bícha
** Changed in: ubuntu-desktop-installer
   Importance: Unknown => Undecided

** Changed in: ubuntu-desktop-installer
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/2043915

Title:
  Booting into live session results in try/install page white screen

Status in ubuntu-desktop-installer:
  Fix Released
Status in mesa package in Ubuntu:
  Fix Released

Bug description:
  Testing Ubuntu Noble desktop daily ISO dated 19-11-2023 - Booting into
  live session results in try/install page white screen.Selecting
  install from the dash results in same white screen.

  see the attached screen shot

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: subiquity (unknown)
  ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
  Uname: Linux 6.5.0-9-generic x86_64
  NonfreeKernelModules: zfs
  ApportVersion: 2.27.0-0ubuntu6
  Architecture: amd64
  CasperMD5CheckResult: pass
  CasperVersion: 1.487
  CloudArchitecture: x86_64
  CloudID: nocloud
  CloudName: unknown
  CloudPlatform: nocloud
  CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud)
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Nov 19 07:02:48 2023
  LiveMediaBuild: Ubuntu 24.04 "Noble Numbat" - Daily amd64 (20231119)
  ProcEnviron:
   LANG=C.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  SourcePackage: subiquity
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-desktop-installer/+bug/2043915/+subscriptions


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


[Touch-packages] [Bug 1813076] Re: goa crashes when trying to authenticate against google & DUO

2024-01-11 Thread Jeremy Bícha
This is fixed for Ubuntu 24.04 LTS which will use the browser to log in
to Google or Microsoft for Settings > Online Accounts.

Previously, it used a popup powered by WebkitGTK. Webkit is the engine
in Apple's Safari browsers so this user agent identifies itself as
similar to Safari.

** Changed in: gnome-online-accounts (Ubuntu)
   Status: New => Fix Released

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

Title:
  goa crashes when trying to authenticate against google & DUO

Status in gnome-online-accounts package in Ubuntu:
  Fix Released

Bug description:
  My google eMAIL account is managed by my organisation.  They recently
  required everyone to validate their sign-ons (sign-ins) via a central
  authentication server (CAS) using the 2FA from DUO.  When attempting
  to connect using goa, I am now re-directed to my organisation's CAS
  and when the DUO login page refreshes, it states that login could not
  proceed because I am using a SAFARI browser that is more than one year
  out of date.  Of course, I'm not using SAFARI, but rather goa.  Is
  there a way to deed the proper header (a more recent version of SAFARI
  in goa) to be able to complete 2FA with DUO?

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-online-accounts 3.28.0-0ubuntu2.1
  ProcVersionSignature: Ubuntu 4.18.0-14.15~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-14-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Wed Jan 23 15:20:45 2019
  InstallationDate: Installed on 2019-01-15 (8 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: gnome-online-accounts
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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


[Touch-packages] [Bug 1827764] Re: GOA cannot add a Gmail account of a minor (young child who needs consent)

2024-01-11 Thread Jeremy Bícha
I believe this is fixed for Ubuntu 24.04 LTS which will use the browser
to log in instead of a popup window powered by WebkitGTK.

** Changed in: gnome-online-accounts (Ubuntu)
   Status: New => Fix Released

** Changed in: gnome-online-accounts (Ubuntu)
   Status: Fix Released => Fix Committed

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

Title:
  GOA cannot add a Gmail account of a minor (young child who needs
  consent)

Status in gnome-online-accounts package in Ubuntu:
  Fix Committed

Bug description:
  Hello
  I am user of ubuntu 18.04 with gnome version 3.28.2 and it seems that I have 
found a bug when a GMAIL account is added.
  I have a problem setting up my child's GMAIL account (minor). The normal 
thing in any web browser is that when entering the GMAIL website, enter the 
data of them and then have to enter mine to consent to their access. In the 
GNOME directly blocks access when entering from ONLINE ACCOUNTS. Is there a 
solution for you to access? 
  Thanks and best regards

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: ubuntu-release-upgrader-core 1:18.04.31
  ProcVersionSignature: Ubuntu 4.18.0-18.19~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-18-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Sun May  5 07:43:54 2019
  InstallationDate: Installed on 2019-04-07 (27 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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


[Touch-packages] [Bug 1826311] Re: Cannot Login to Google with Advanced Protection Enabled

2024-01-11 Thread Jeremy Bícha
** Changed in: gnome-online-accounts (Ubuntu)
   Status: Triaged => Fix Committed

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

Title:
  Cannot Login to Google with Advanced Protection Enabled

Status in gnome-online-accounts:
  Fix Released
Status in gnome-online-accounts package in Ubuntu:
  Fix Committed

Bug description:
  Description:  Ubuntu 19.04
  Release:  19.04

  
  gnome-online-accounts:
Installed: 3.32.0-1ubuntu1
Candidate: 3.32.0-1ubuntu1
Version table:
   *** 3.32.0-1ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu disco/main amd64 Packages
  100 /var/lib/dpkg/status

  1) Open Online accounts and select google (From settings or during OS setup)
  2) enter username and password.

  What I expect: I get the prompt to plug-in my 2 factor hardware key
  What actually happens: I get a prompt saying, "You can only use your Security 
keys with Google Chrome"

  
  Not sure if this is actually fixable, I know desktop firefox has hidden 
settings to allow u2f, but not sure if that extends to the embedded browsers 
(if gnome-online-accounts even uses an embedded firefox for its browser)

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gnome-online-accounts 3.32.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr 25 00:16:27 2019
  InstallationDate: Installed on 2019-04-25 (0 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-online-accounts
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-online-accounts/+bug/1826311/+subscriptions


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


[Touch-packages] [Bug 2047780] Re: BlueZ release 5.71

2024-01-11 Thread Jeremy Bícha
ell had an approved MIR but the only thing it was used for was iwd which
is not currently in main. After the MIR is approved, something in main
needs to depend on it (or add it to a main seed) and then the Archive
Admins can promote it to main.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/2047780

Title:
  BlueZ release 5.71

Status in bluez package in Ubuntu:
  Fix Released

Bug description:
  Release BlueZ 5.71 to noble.

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


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


[Touch-packages] [Bug 2047780] Re: BlueZ release 5.71 and merge from Debian

2024-01-10 Thread Jeremy Bícha
Simon, ell already has a recent approved MIR LP: #1971738

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/2047780

Title:
  BlueZ release 5.71 and merge from Debian

Status in bluez package in Ubuntu:
  In Progress

Bug description:
  Release BlueZ 5.71 to noble.

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


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


[Touch-packages] [Bug 1731628] Re: Cannot add caldav calendar

2024-01-10 Thread Jeremy Bícha
This will be possible with Ubuntu 24.04 LTS by adding the account using
the Settings app > Online Accounts > WebDAV

** Package changed: gnome-calendar (Ubuntu) => gnome-online-accounts
(Ubuntu)

** Changed in: gnome-online-accounts (Ubuntu)
   Status: Confirmed => Fix Committed

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

Title:
  Cannot add caldav calendar

Status in gnome-online-accounts package in Ubuntu:
  Fix Committed

Bug description:
  Hi,

  I try to add a caldav calendar

  calendars -> Add -> From Web ->
  https://posteo.de:8443/calendars/max.mustermann/default/

  and I hit enter but the "add" button in the right upper corner remains
  grayed out.

  Kind regards

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-calendar 3.26.2-1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Nov 11 14:47:03 2017
  InstallationDate: Installed on 2017-11-11 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171109)
  SourcePackage: gnome-calendar
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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


[Touch-packages] [Bug 1851046] Re: Enable Last.fm provider

2024-01-10 Thread Jeremy Bícha
GNOME 46 Alpha has removed the Last.fm provider

** Changed in: gnome-online-accounts (Ubuntu)
   Status: New => Won't Fix

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

Title:
  Enable Last.fm provider

Status in gnome-online-accounts package in Ubuntu:
  Won't Fix

Bug description:
  Since a while now GOA supports Last.fm accounts but for some reason this 
provider is excluded in the Ubuntu build parameters of this package.
  Is there a specific reason why this is not enabled? Would it be possible to 
enable this provider as well?

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-online-accounts 3.34.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sat Nov  2 16:07:05 2019
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-11-26 (1437 days ago)
  InstallationMedia: It
  SourcePackage: gnome-online-accounts
  UpgradeStatus: Upgraded to eoan on 2019-10-20 (13 days ago)

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


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


[Touch-packages] [Bug 2047780] Re: BlueZ release 5.71

2024-01-07 Thread Jeremy Bícha
evolution-data-server still has uninstallable binaries on i386. You can
ignore bluez for the binfmt-support issue.

However, for bluez, Ubuntu uses --enable-phonebook-ebook . There are
other phonebook options; maybe what Debian uses works for Debian.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/2047780

Title:
  BlueZ release 5.71

Status in bluez package in Ubuntu:
  Fix Committed

Bug description:
  Release BlueZ 5.71 to noble.

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


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


[Touch-packages] [Bug 2047780] Re: BlueZ release 5.71

2024-01-06 Thread Jeremy Bícha
Simon, I think it would be better to get libphonenumber fixed correctly
instead of working around it.

https://launchpad.net/ubuntu/+source/libphonenumber/8.12.57+ds-4build1

https://ubuntu-archive-team.ubuntu.com/proposed-
migration/noble_uninst.txt

In other words, asking an Archive Admin to build binfmt-support on i386.
I suspect that it would need to be special-cased something like this,
because jarwrapper is arch:all

https://code.launchpad.net/~jbicha/ubuntu-archive-tools/+git/ubuntu-
archive-tools/+merge/457360

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/2047780

Title:
  BlueZ release 5.71

Status in bluez package in Ubuntu:
  Fix Committed

Bug description:
  Release BlueZ 5.71 to noble.

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


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


[Touch-packages] [Bug 2047780] Re: BlueZ release 5.71

2024-01-04 Thread Jeremy Bícha
Daniel, systemd was updated today in noble-proposed. It includes changes
as part of Debian's ongoing usrmerge work. In particular this commit:
https://salsa.debian.org/systemd-team/systemd/-/commit/ee83b5721

Here is a Debian commit to adapt to the change:
https://salsa.debian.org/bluetooth-team/bluez/-/commit/f4d76255cdfa

Something like this could be simpler though:
https://salsa.debian.org/DebianOnMobile-team/modemmanager/-/commit/367180c3


** Tags added: update-excuse

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/2047780

Title:
  BlueZ release 5.71

Status in bluez package in Ubuntu:
  Fix Committed

Bug description:
  Release BlueZ 5.71 to noble.

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


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


[Touch-packages] [Bug 2037604] Re: Backport packages for 22.04.4 HWE stack

2024-01-03 Thread Jeremy Bícha
All the failing autopkgtests currently reported for this update also
failed a migration-reference/0 run

mutter/42.9-0ubuntu5 (arm64, ppc64el)
vtk9/9.1.0+really9.1.0+dfsg2-3build1 (armhf)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/2037604

Title:
  Backport packages for 22.04.4 HWE stack

Status in directx-headers package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Invalid
Status in rust-bindgen package in Ubuntu:
  Invalid
Status in rust-clang-sys package in Ubuntu:
  Invalid
Status in directx-headers source package in Jammy:
  Fix Committed
Status in mesa source package in Jammy:
  Fix Committed
Status in rust-bindgen source package in Jammy:
  Invalid
Status in rust-clang-sys source package in Jammy:
  Invalid

Bug description:
  [Impact]
  The graphics HWE stack from mantic needs to be backported for 22.04.4

  directx-headers
  - build-dep of the new Mesa

  mesa
  - new major release (23.2.x)
  - new HW support, Meteor Lake..

  [Test case]
  We want to cover at least 2-3 different, widely used and already previously 
supported GPU generations from both AMD and Intel which are supported by this 
release, as those are the ones that cover most bases; nouveau users tend to 
switch to the NVIDIA blob after installation. No need to test ancient GPU's 
supported by mesa-amber. And best to focus on the newer generations (~5y and 
newer) as the older ones are less likely to break at this point.
  - AMD: Vega, Navi1x (RX5000*), Navi2x (RX6000*), Navi3x (RX7000*)
  - Intel: gen9 (SKL/APL/KBL/CFL/WHL/CML), gen11 (ICL), gen12 (TGL/RKL/RPL/DG2)

  Install the new packages and run some tests:
  - check that the desktop is still using hw acceleration and hasn't fallen 
back to swrast/llvmpipe
  - run freely available benchmarks that torture the GPU (Unigine 
Heaven/Valley/Superposition)
  - run some games from Steam if possible

  and in each case check that there is no gfx corruption happening or
  worse.

  Note that upstream releases have already been tested for OpenGL and
  Vulkan conformance by their CI.

  [Where things could go wrong]
  This is a major update of Mesa, there could be regressions but we'll try to 
catch any with testing. And since it shares bugs with mantic, we'd already know 
if there are serious issues. We will backport the final 23.2.x at a later 
stage, the first backport is needed for enabling Intel Meteor Lake.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/directx-headers/+bug/2037604/+subscriptions


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


[Touch-packages] [Bug 2034466] Re: nautilus-sendto is included in the minimal Jammy 22.04 install

2023-12-30 Thread Jeremy Bícha
nautilus-sendto was intentionally included in Ubuntu 22.04 LTS and
intentionally removed from later Ubuntu releases. It may be
intentionally included in Ubuntu 24.04 LTS.

** Changed in: ubuntu-meta (Ubuntu)
   Status: New => Fix Released

** Changed in: nautilus-sendto (Ubuntu)
   Status: New => Fix Released

** Changed in: ubuntu-meta (Ubuntu)
   Status: Fix Released => Invalid

** Changed in: nautilus-sendto (Ubuntu)
   Status: Fix Released => Invalid

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

Title:
  nautilus-sendto is included in the minimal Jammy 22.04 install

Status in nautilus-sendto package in Ubuntu:
  Invalid
Status in ubuntu-meta package in Ubuntu:
  Invalid

Bug description:
  nautilus-sendto is installed because of a package not in the minimal
  installation.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus-sendto/+bug/2034466/+subscriptions


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


[Touch-packages] [Bug 2033139] Re: ubuntu-desktop{-minimal} still depending on ghostscript-x package

2023-12-13 Thread Jeremy Bícha
https://launchpad.net/ubuntu/+source/ubuntu-meta/1.526

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

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

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

Title:
  ubuntu-desktop{-minimal} still depending on ghostscript-x package

Status in ghostscript package in Ubuntu:
  Fix Released
Status in ubuntu-meta package in Ubuntu:
  Fix Released

Bug description:
  The packages ubuntu-desktop and ubuntu-desktop-minimal still depend on 
package ghostscript-x, but it's a dummy package that just points for the 
package ghostscript.
  So the idea is to change the dependency so the dummy package ghostscript-x 
can be removed safely.

  Description:  Ubuntu Mantic Minotaur (development branch)
  Release:  23.10

  Packages version: 1.516

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


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


[Touch-packages] [Bug 2046166] Re: mesa 23.3 zink errors

2023-12-12 Thread Jeremy Bícha
** Changed in: mesa (Ubuntu)
   Status: Triaged => Fix Released

** Changed in: gtk4 (Ubuntu)
   Status: Triaged => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/2046166

Title:
  mesa 23.3 zink errors

Status in gtk4 package in Ubuntu:
  Fix Released
Status in mesa package in Ubuntu:
  Fix Released

Bug description:
  mesa 23.3 is emitting ZINK errors. Some initial issues were fixed
  which had caused autopkgtest failures for mutter and gtk4.

  There is still a gtk4 build test failure. My theory is that the extra
  ZINK stderr output is confusing the gtk:tools / validate test which is
  not expecting the extra errors.

  https://launchpad.net/ubuntu/+source/gtk4/4.12.4+ds-3ubuntu1

  I am setting the block-proposed tag since I don't think we want mesa
  to migrate out of noble-proposed while it is causing gtk4 to fail to
  build.

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


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


[Touch-packages] [Bug 2046166] Re: mesa 23.3 zink errors

2023-12-11 Thread Jeremy Bícha
** Tags removed: block-proposed
** Tags added: block-proposed-noble update-excuse

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/2046166

Title:
  mesa 23.3 zink errors

Status in gtk4 package in Ubuntu:
  Triaged
Status in mesa package in Ubuntu:
  Triaged

Bug description:
  mesa 23.3 is emitting ZINK errors. Some initial issues were fixed
  which had caused autopkgtest failures for mutter and gtk4.

  There is still a gtk4 build test failure. My theory is that the extra
  ZINK stderr output is confusing the gtk:tools / validate test which is
  not expecting the extra errors.

  https://launchpad.net/ubuntu/+source/gtk4/4.12.4+ds-3ubuntu1

  I am setting the block-proposed tag since I don't think we want mesa
  to migrate out of noble-proposed while it is causing gtk4 to fail to
  build.

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


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


[Touch-packages] [Bug 2046166] [NEW] mesa 23.3 zink errors

2023-12-11 Thread Jeremy Bícha
Public bug reported:

mesa 23.3 is emitting ZINK errors. Some initial issues were fixed which
had caused autopkgtest failures for mutter and gtk4.

There is still a gtk4 build test failure. My theory is that the extra
ZINK stderr output is confusing the gtk:tools / validate test which is
not expecting the extra errors.

https://launchpad.net/ubuntu/+source/gtk4/4.12.4+ds-3ubuntu1

I am setting the block-proposed tag since I don't think we want mesa to
migrate out of noble-proposed while it is causing gtk4 to fail to build.

** Affects: gtk4 (Ubuntu)
 Importance: High
 Status: Triaged

** Affects: mesa (Ubuntu)
 Importance: High
 Status: Triaged


** Tags: block-proposed ftbfs noble

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

** Description changed:

  mesa 23.3 is emitting ZINK errors. Some initial issues were fixed which
  had caused autopkgtest failures for mutter and gtk4.
  
  There is still a gtk4 build test failure. My theory is that the extra
- ZINK stderr is confusing the gtk:tools / validate test which is not
- expecting the extra errors.
+ ZINK stderr output is confusing the gtk:tools / validate test which is
+ not expecting the extra errors.
  
  https://launchpad.net/ubuntu/+source/gtk4/4.12.4+ds-3ubuntu1
  
  I am setting the block-proposed tag since I don't think we want mesa to
  migrate out of noble-proposed while it is causing gtk4 to fail to build.

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

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/2046166

Title:
  mesa 23.3 zink errors

Status in gtk4 package in Ubuntu:
  Triaged
Status in mesa package in Ubuntu:
  Triaged

Bug description:
  mesa 23.3 is emitting ZINK errors. Some initial issues were fixed
  which had caused autopkgtest failures for mutter and gtk4.

  There is still a gtk4 build test failure. My theory is that the extra
  ZINK stderr output is confusing the gtk:tools / validate test which is
  not expecting the extra errors.

  https://launchpad.net/ubuntu/+source/gtk4/4.12.4+ds-3ubuntu1

  I am setting the block-proposed tag since I don't think we want mesa
  to migrate out of noble-proposed while it is causing gtk4 to fail to
  build.

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


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


[Touch-packages] [Bug 2023322] Re: GTK internal browser does not render with Nvidia drivers

2023-12-05 Thread Jeremy Bícha
That bug was filed before we fixed Jammy on 2023-11-20

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

Title:
  GTK internal browser does not render with Nvidia drivers

Status in Webkit:
  Confirmed
Status in gnome-control-center package in Ubuntu:
  Invalid
Status in gnome-online-accounts package in Ubuntu:
  Invalid
Status in webkit2gtk package in Ubuntu:
  Fix Released
Status in yelp package in Ubuntu:
  Invalid
Status in webkit2gtk package in Debian:
  Fix Released

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

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

  Nothing in /var/crash

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

  1   2   3   >