date:20221016

[Touch-packages] [Bug 1713803] Re: replacement of resolvconf with systemd needs integration

2022-10-16 Thread Steve Langasek

** Changed in: dnscrypt-proxy (Ubuntu)
   Status: Confirmed => Invalid

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

Title:
  replacement of resolvconf with systemd needs integration

Status in android-androresolvd package in Ubuntu:
  Invalid
Status in avahi package in Ubuntu:
  Invalid
Status in bind9 package in Ubuntu:
  Invalid
Status in cloud-init package in Ubuntu:
  Invalid
Status in cloud-initramfs-tools package in Ubuntu:
  Invalid
Status in dhcpcd5 package in Ubuntu:
  Invalid
Status in dibbler package in Ubuntu:
  Won't Fix
Status in dnscrypt-proxy package in Ubuntu:
  Invalid
Status in dnsmasq package in Ubuntu:
  Invalid
Status in dnssec-trigger package in Ubuntu:
  Invalid
Status in fetchmail package in Ubuntu:
  Invalid
Status in freedombox-setup package in Ubuntu:
  Confirmed
Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in isc-dhcp package in Ubuntu:
  Fix Released
Status in ndisc6 package in Ubuntu:
  Fix Released
Status in netscript-2.4 package in Ubuntu:
  Won't Fix
Status in open-iscsi package in Ubuntu:
  Triaged
Status in openvpn package in Ubuntu:
  Confirmed
Status in postfix package in Ubuntu:
  Invalid
Status in pppconfig package in Ubuntu:
  Confirmed
Status in pump package in Ubuntu:
  Confirmed
Status in resolvconf package in Ubuntu:
  Invalid
Status in sendmail package in Ubuntu:
  Invalid
Status in squid3 package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Invalid
Status in unbound package in Ubuntu:
  Triaged
Status in vpnc package in Ubuntu:
  Invalid
Status in vpnc-scripts package in Ubuntu:
  Invalid
Status in whereami package in Ubuntu:
  Triaged

Bug description:
  There is a plan to remove resolvconf from the Ubuntu Server image.
  resolvconf integrated with other parts of the system in 2 ways:
   * hooks invoked on change (/etc/resolvconf/update.d/)
   * resolvconf tool (invoked with -a and -d or -u)

  Packages which install files into /etc/resolvconf/update.d are:
  - dnsmasq: This may be mostly covered by systemd-resolved itself (the dns
    caching path).
  - resolvconf: This probably isn't necessary in systemd-resolved path.
  - unbound: This is another "validating, recursive, caching DNS resolver".

  The list of Depends/Suggests/Recommends on resolvconf.

  # for pkg in $(apt-cache rdepends resolvconf | grep -v openreso | grep -v 
Reverse); do out=$(apt-cache show $pkg | grep resolvconf); src=$(apt-cache show 
$pkg | awk '$1 == "Source:" { print $2 }'); [ -n "$src" ] || src=$pkg; case 
"$out" in Depends:*resolvconf) r=depends;; Suggests:*) r=suggests;; 
Recommends:*) r=recommends;; esac; echo "$r $src"; done  | sort -u
  depends android-androresolvd
  recommends avahi
  recommends dhcpcd5
  recommends dibbler
  recommends ndisc6
  recommends whereami
  suggests bind9
  suggests dnscrypt-proxy
  suggests dnsmasq
  suggests dnssec-trigger
  suggests fetchmail
  suggests freedombox-setup
  suggests isc-dhcp
  suggests netscript-2.4
  suggests openvpn
  suggests postfix
  suggests pppconfig
  suggests pump
  suggests resolvconf
  suggests sendmail
  suggests squid3
  suggests vpnc
  suggests vpnc-scripts

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: systemd 234-2ubuntu9
  ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
  Uname: Linux 4.12.0-11-generic x86_64
  ApportVersion: 2.20.6-0ubuntu7
  Architecture: amd64
  Date: Tue Aug 29 18:53:50 2017
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.12.0-11-generic 
root=UUID=f897b32a-eacf-4191-9717-844918947069 ro quiet splash vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.vendor: Intel Corporation

  Related bugs:
   * bug 1698181: Switch to netplan renderer in Artful
   * bug 1714308: dns does not work in initramfs after configure_networking
   * bug 1717983 replacement of isc-dhcp-client with with systemd-networkd for 
dhclient needs integration

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/android-androresolvd/+bug/1713803/+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 1713803] Re: replacement of resolvconf with systemd needs integration

2022-10-16 Thread Steve Langasek

The resolvconf interface is now implemented in the systemd-resolved
package and integrates correctly with systemd.  There is no longer a
need for packages to port away from this interface.

** Changed in: android-androresolvd (Ubuntu)
   Status: Triaged => Invalid

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

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

** Changed in: dhcpcd5 (Ubuntu)
   Status: Confirmed => Invalid

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

Title:
  replacement of resolvconf with systemd needs integration

Status in android-androresolvd package in Ubuntu:
  Invalid
Status in avahi package in Ubuntu:
  Invalid
Status in bind9 package in Ubuntu:
  Invalid
Status in cloud-init package in Ubuntu:
  Invalid
Status in cloud-initramfs-tools package in Ubuntu:
  Invalid
Status in dhcpcd5 package in Ubuntu:
  Invalid
Status in dibbler package in Ubuntu:
  Won't Fix
Status in dnscrypt-proxy package in Ubuntu:
  Confirmed
Status in dnsmasq package in Ubuntu:
  Invalid
Status in dnssec-trigger package in Ubuntu:
  Invalid
Status in fetchmail package in Ubuntu:
  Confirmed
Status in freedombox-setup package in Ubuntu:
  Confirmed
Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in isc-dhcp package in Ubuntu:
  Fix Released
Status in ndisc6 package in Ubuntu:
  Fix Released
Status in netscript-2.4 package in Ubuntu:
  Won't Fix
Status in open-iscsi package in Ubuntu:
  Triaged
Status in openvpn package in Ubuntu:
  Confirmed
Status in postfix package in Ubuntu:
  Invalid
Status in pppconfig package in Ubuntu:
  Confirmed
Status in pump package in Ubuntu:
  Confirmed
Status in resolvconf package in Ubuntu:
  Invalid
Status in sendmail package in Ubuntu:
  Invalid
Status in squid3 package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Invalid
Status in unbound package in Ubuntu:
  Triaged
Status in vpnc package in Ubuntu:
  Invalid
Status in vpnc-scripts package in Ubuntu:
  Invalid
Status in whereami package in Ubuntu:
  Triaged

Bug description:
  There is a plan to remove resolvconf from the Ubuntu Server image.
  resolvconf integrated with other parts of the system in 2 ways:
   * hooks invoked on change (/etc/resolvconf/update.d/)
   * resolvconf tool (invoked with -a and -d or -u)

  Packages which install files into /etc/resolvconf/update.d are:
  - dnsmasq: This may be mostly covered by systemd-resolved itself (the dns
    caching path).
  - resolvconf: This probably isn't necessary in systemd-resolved path.
  - unbound: This is another "validating, recursive, caching DNS resolver".

  The list of Depends/Suggests/Recommends on resolvconf.

  # for pkg in $(apt-cache rdepends resolvconf | grep -v openreso | grep -v 
Reverse); do out=$(apt-cache show $pkg | grep resolvconf); src=$(apt-cache show 
$pkg | awk '$1 == "Source:" { print $2 }'); [ -n "$src" ] || src=$pkg; case 
"$out" in Depends:*resolvconf) r=depends;; Suggests:*) r=suggests;; 
Recommends:*) r=recommends;; esac; echo "$r $src"; done  | sort -u
  depends android-androresolvd
  recommends avahi
  recommends dhcpcd5
  recommends dibbler
  recommends ndisc6
  recommends whereami
  suggests bind9
  suggests dnscrypt-proxy
  suggests dnsmasq
  suggests dnssec-trigger
  suggests fetchmail
  suggests freedombox-setup
  suggests isc-dhcp
  suggests netscript-2.4
  suggests openvpn
  suggests postfix
  suggests pppconfig
  suggests pump
  suggests resolvconf
  suggests sendmail
  suggests squid3
  suggests vpnc
  suggests vpnc-scripts

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: systemd 234-2ubuntu9
  ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
  Uname: Linux 4.12.0-11-generic x86_64
  ApportVersion: 2.20.6-0ubuntu7
  Architecture: amd64
  Date: Tue Aug 29 18:53:50 2017
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.12.0-11-generic 
root=UUID=f897b32a-eacf-4191-9717-844918947069 ro quiet splash vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.vendor: Intel Corporation

  Related bugs:
   * bug 1698181: Switch to netplan renderer in Artful
   * bug 1714308: dns does not work in initramfs after configure_networking
   * bug 1717983 replacement of isc-dhcp-client with with systemd-networkd for 
dhclient needs integration

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/android-androresolvd/+bug/1713803/+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 1990743] Re: resolvconf install fails upgrading from Jammy to Kinetic

2022-10-16 Thread Steve Langasek

Upon further inspection, it turns out that systemd-resolved now
implements the resolvconf interface.  We should drop resolvconf and
openresolv now from the archive, and users requesting resolvconf will be
directed to systemd-resolved.  Packages which depend/recommend systemd-
resolved will also get the supported implementation going forward.

Using this bug for the removal of resolvconf and openresolv.

** Changed in: resolvconf (Ubuntu)
   Status: Incomplete => Triaged

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

** Summary changed:

- resolvconf install fails upgrading from Jammy to Kinetic
+ RM: resolvconf, openresolv (and blacklist)

** Description changed:

+ systemd-resolved now implements the resolvconf interface, and Conflicts:
+ with other implementations of resolvconf.  Installing these other
+ implementations on a full system or container will wrongly result in
+ removal of the systemd-resolved package.  We should drop resolvconf and
+ openresolv now from the archive (and blacklist them).  Users requesting
+ resolvconf will be directed to systemd-resolved. Packages which
+ depend/recommend systemd-resolved will also get the supported
+ implementation going forward.
+ 
+ [Original description]
  Setting up resolvconf (1.91ubuntu1) ...
  cp: not writing through dangling symlink 
'/etc/resolvconf/resolv.conf.d/original'
  dpkg: error processing package resolvconf (--configure):
-  installed resolvconf package post-installation script subprocess returned 
error exit status 1
+  installed resolvconf package post-installation script subprocess returned 
error exit status 1
  Errors were encountered while processing:
-  resolvconf
+  resolvconf
  E: Sub-process /usr/bin/dpkg returned an error code (1)
- $ ls -l /etc/resolvconf/resolv.conf.d/original 
+ $ ls -l /etc/resolvconf/resolv.conf.d/original
  lrwxrwxrwx 1 root root 39 Jan  2  2019 /etc/resolvconf/resolv.conf.d/original 
-> ../run/systemd/resolve/stub-resolv.conf
  
  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: resolvconf 1.91ubuntu1
  ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0
  Uname: Linux 5.19.0-15-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.23.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Sep 24 18:48:31 2022
  InstallationDate: Installed on 2019-01-02 (1361 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  PackageArchitecture: all
  SourcePackage: resolvconf
  UpgradeStatus: Upgraded to kinetic on 2022-09-24 (0 days ago)
  modified.conffile..etc.resolvconf.resolv.conf.d.base: [modified]
  modified.conffile..etc.resolvconf.update.d.dnscache: [deleted]
  mtime.conffile..etc.resolvconf.resolv.conf.d.base: 2019-01-02T12:33:18.553144

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

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

Title:
  RM: resolvconf, openresolv (and blacklist)

Status in openresolv package in Ubuntu:
  Fix Released
Status in resolvconf package in Ubuntu:
  Fix Released

Bug description:
  systemd-resolved now implements the resolvconf interface, and
  Conflicts: with other implementations of resolvconf.  Installing these
  other implementations on a full system or container will wrongly
  result in removal of the systemd-resolved package.  We should drop
  resolvconf and openresolv now from the archive (and blacklist them).
  Users requesting resolvconf will be directed to systemd-resolved.
  Packages which depend/recommend systemd-resolved will also get the
  supported implementation going forward.

  [Original description]
  Setting up resolvconf (1.91ubuntu1) ...
  cp: not writing through dangling symlink 
'/etc/resolvconf/resolv.conf.d/original'
  dpkg: error processing package resolvconf (--configure):
   installed resolvconf package post-installation script subprocess returned 
error exit status 1
  Errors were encountered while processing:
   resolvconf
  E: Sub-process /usr/bin/dpkg returned an error code (1)
  $ ls -l /etc/resolvconf/resolv.conf.d/original
  lrwxrwxrwx 1 root root 39 Jan  2  2019 /etc/resolvconf/resolv.conf.d/original 
-> ../run/systemd/resolve/stub-resolv.conf

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: resolvconf 1.91ubuntu1
  ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0
  Uname: Linux 5.19.0-15-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.23.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Sep 24 18:48:31 2022
  InstallationDate: Installed on 2019-01-02 (1361 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  PackageArchitecture: all
  SourcePackage: resolvconf

[Touch-packages] [Bug 1990743] Re: RM: resolvconf, openresolv (and blacklist)

2022-10-16 Thread Steve Langasek

Removing packages from kinetic:
openresolv 3.12.0-2 in kinetic
openresolv 3.12.0-2 in kinetic amd64
openresolv 3.12.0-2 in kinetic arm64
openresolv 3.12.0-2 in kinetic armhf
openresolv 3.12.0-2 in kinetic i386
openresolv 3.12.0-2 in kinetic ppc64el
openresolv 3.12.0-2 in kinetic riscv64
openresolv 3.12.0-2 in kinetic s390x
resolvconf 1.91ubuntu1 in kinetic
resolvconf 1.91ubuntu1 in kinetic amd64
resolvconf 1.91ubuntu1 in kinetic arm64
resolvconf 1.91ubuntu1 in kinetic armhf
resolvconf 1.91ubuntu1 in kinetic i386
resolvconf 1.91ubuntu1 in kinetic ppc64el
resolvconf 1.91ubuntu1 in kinetic riscv64
resolvconf 1.91ubuntu1 in kinetic s390x
Comment: Conflicts with systemd-resolved, which is now the preferred 
implementation as of kinetic; LP: #1990743
2 packages successfully removed.


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

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

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

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

Title:
  RM: resolvconf, openresolv (and blacklist)

Status in openresolv package in Ubuntu:
  Fix Released
Status in resolvconf package in Ubuntu:
  Fix Released

Bug description:
  systemd-resolved now implements the resolvconf interface, and
  Conflicts: with other implementations of resolvconf.  Installing these
  other implementations on a full system or container will wrongly
  result in removal of the systemd-resolved package.  We should drop
  resolvconf and openresolv now from the archive (and blacklist them).
  Users requesting resolvconf will be directed to systemd-resolved.
  Packages which depend/recommend systemd-resolved will also get the
  supported implementation going forward.

  [Original description]
  Setting up resolvconf (1.91ubuntu1) ...
  cp: not writing through dangling symlink 
'/etc/resolvconf/resolv.conf.d/original'
  dpkg: error processing package resolvconf (--configure):
   installed resolvconf package post-installation script subprocess returned 
error exit status 1
  Errors were encountered while processing:
   resolvconf
  E: Sub-process /usr/bin/dpkg returned an error code (1)
  $ ls -l /etc/resolvconf/resolv.conf.d/original
  lrwxrwxrwx 1 root root 39 Jan  2  2019 /etc/resolvconf/resolv.conf.d/original 
-> ../run/systemd/resolve/stub-resolv.conf

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: resolvconf 1.91ubuntu1
  ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0
  Uname: Linux 5.19.0-15-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.23.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Sep 24 18:48:31 2022
  InstallationDate: Installed on 2019-01-02 (1361 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  PackageArchitecture: all
  SourcePackage: resolvconf
  UpgradeStatus: Upgraded to kinetic on 2022-09-24 (0 days ago)
  modified.conffile..etc.resolvconf.resolv.conf.d.base: [modified]
  modified.conffile..etc.resolvconf.update.d.dnscache: [deleted]
  mtime.conffile..etc.resolvconf.resolv.conf.d.base: 2019-01-02T12:33:18.553144

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openresolv/+bug/1990743/+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 1971984] Re: pcscd 1.9.5-3 do not start automatically, only manual

2022-10-16 Thread Peter Surda

The bug described here looks like the one I'm experiencing. I have
multiple yubikeys which I use for SSH and GPG (occasionally U2F but that
doesn't appear to be affected by this). If I just enable the pcscd
service, the daemon doesn't auto-start after a reboot. Running ssh or
gpg commands fails to access the key. I also need to enable the socket.
Then the daemon auto-starts and I can use ssh/gpg:

$ systemctl enable pcscd
# after a reboot, pcscd is stopped, ssh/gpg unable to access the key. Need to 
start pcscd manually.

$ systemctl enable pcscd.socket
# now after reboot both the socket and the service are running and ssh/gpg works

It wasn't like this with 20.04, there enabling pcscd.service was enough.

Hope this helps others with the issue, and/or the maintainers to address
it.

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

Title:
  pcscd 1.9.5-3 do not start automatically, only manual

Status in pcsc-lite package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu Mate 22.04 with the latest updates.
  Problem is present with internal smart-card reader and also external usb 
smart-card reader.

  eid-viewer sees no card reader,but When i do:

  sudo pcscd -f

  it is working, also following the tips of Ludovic:
  
https://ludovicrousseau.blogspot.com/2011/11/pcscd-auto-start-using-systemd.html

  sudo systemctl stop pcscd.socket
  sudo systemctl start pcscd.socket

  It is working until next restart.

  libacsccid1  version: 1.1.8-1
  libccid version: 1.5.0-2
  pcscd version: 1.9.5-3
  eid-archive version: 2022.3
  eid-mw version: 5.0.28v5.0.28-0u2204-1
  eid-viewer version: 5.0.28v5.0.28-0u2204-1

  In Firefox, my eid card is then also recognized, but only in the ESR
  version, but this is a know Mozilla bug.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pcsc-lite/+bug/1971984/+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 1993027] Re: Display settings lost when leaving screen saver / screen switch

2022-10-16 Thread Daniel van Vugt

Supporting manual xrandr settings is generally not a priority for shell
developers. The shell expects to own and control everything, and that
the user has chosen their settings in the GUI provided by the shell /
desktop environment.

But we can make it an enhancement request to see if it's possible for
them all to co-exist.

** Package changed: xorg (Ubuntu) => ubuntu

** Package changed: ubuntu => kwin (Ubuntu)

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

Title:
  Display settings lost when leaving screen saver / screen switch

Status in kwin package in Ubuntu:
  New

Bug description:
  The settings of the screen, in particular brightness and gamma, are being 
lost in numerous situations:
  - leaving a screen saver/lock
  - switching users
  - random time
  - logging in

  This applies to settings set via xrandr, or using the nvidia-settings
  tool.

  This did not happen in previous versions of Ubuntu (20.04 for
  example).  I am using Kubuntu as a desktop.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-50.56-generic 5.15.60
  Uname: Linux 5.15.0-50-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia wl
  .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..65.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  515.76  Mon Sep 12 19:21:56 
UTC 2022
   GCC version:
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: KDE
  Date: Sat Oct 15 11:43:15 2022
  DistUpgraded: 2022-09-22 20:03:38,859 ERROR found exception: 'E:Sub-process 
/usr/bin/dpkg returned an error code (1)'
  DistroCodename: jammy
  DistroVariant: ubuntu
  DkmsStatus:
   bcmwl/6.30.223.271+bdcom, 5.15.0-48-generic, x86_64: installed
   bcmwl/6.30.223.271+bdcom, 5.15.0-50-generic, x86_64: installed
   virtualbox/6.1.38, 5.15.0-48-generic, x86_64: installed
   virtualbox/6.1.38, 5.15.0-50-generic, x86_64: installed
  ExtraDebuggingInterest: No
  GraphicsCard:
   NVIDIA Corporation GP106 [GeForce GTX 1060 6GB] [10de:1c03] (rev a1) 
(prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. GP106 [GeForce GTX 1060 6GB] [1043:85a4]
  MachineType: Micro-Star International Co., Ltd. MS-7A94
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-50-generic 
root=UUID=937cdc48-c0d2-45e6-a578-a819d2b1378f ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to jammy on 2022-09-22 (22 days ago)
  dmi.bios.date: 07/12/2019
  dmi.bios.release: 5.13
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.B0
  dmi.board.asset.tag: Default string
  dmi.board.name: X299 RAIDER (MS-7A94)
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.B0:bd07/12/2019:br5.13:svnMicro-StarInternationalCo.,Ltd.:pnMS-7A94:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnX299RAIDER(MS-7A94):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: MS-7A94
  dmi.product.sku: Default string
  dmi.product.version: 1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.110-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 22.0.5-0ubuntu0.1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kwin/+bug/1993027/+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 1951491] Re: Can't run snaps: .slice/session-1.scope is not a snap cgroup

2022-10-16 Thread Daniel van Vugt

IMHO it's not reasonable for any software to absolutely require an
environment variable that's not already set in a default console login.
We all need to build better software that still works without
environment variables.

Also changing multiple desktop environments now and into the future
doesn't scale.

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

Title:
  Can't run snaps: .slice/session-1.scope is not a snap cgroup

Status in X2Go:
  New
Status in snapd package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Incomplete
Status in x2goserver package in Ubuntu:
  Confirmed
Status in snapd package in Debian:
  New

Bug description:
  I just upgraded from hirsute to impish using do-release-upgrade. On
  the upgraded system, I can't run either firefox or chromium (both of
  which worked fine under hirsute). Both fail with:

  /user.slice/user-NNN.slice/session-1.scope is not a snap cgroup where
  NNN is my uid

  With firefox, I was able to fix the problem with:

  snap remove --purge firefox
  apt purge firefox
  apt install firefox

  Now firefox works. But I tried the same thing substituting chromium-
  browser for firefox, and it didn't help: chromium fails with the same
  error message.

  I guess there must be something left over from the hirsute version of
  snapd that isn't getting noticed or cleared by the impish version?

  Someone suggested this might be related to bug 1850667, but that bug
  is marked fixed as of a couple months ago, and I just did this upgrade
  today. Also, it doesn't mention the error message I'm seeing.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: snapd 2.53+21.10ubuntu1
  ProcVersionSignature: Ubuntu 5.13.0-21.21-generic 5.13.18
  Uname: Linux 5.13.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Thu Nov 18 18:12:45 2021
  InstallationDate: Installed on 2020-04-29 (568 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  SourcePackage: snapd
  UpgradeStatus: Upgraded to impish on 2021-11-18 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/x2go/+bug/1951491/+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 1992995] Re: Graphics

2022-10-16 Thread Daniel van Vugt

Can you provide a screenshot or photo of the screen?

** Package changed: xorg (Ubuntu) => ubuntu

** Changed in: ubuntu
   Status: New => Incomplete

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

Title:
  Graphics

Status in Ubuntu:
  Incomplete

Bug description:
  I am trying to use MATLAB plots but no graphics are showing.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-128.144-generic 5.4.210
  Uname: Linux 5.4.0-128-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.24
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct 14 19:23:11 2022
  DistUpgraded: 2020-11-09 21:29:05,838 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
  DistroCodename: focal
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: Dell UHD Graphics 620 [1028:081c]
  InstallationDate: Installed on 2019-06-20 (1212 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  MachineType: Dell Inc. Latitude 7490
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-128-generic 
root=UUID=38ffaac9-4782-4848-b6e2-86ba57246327 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to focal on 2020-11-09 (703 days ago)
  dmi.bios.date: 01/07/2021
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.18.0
  dmi.board.name: 0KP0FT
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.18.0:bd01/07/2021:svnDellInc.:pnLatitude7490:pvr:rvnDellInc.:rn0KP0FT:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 7490
  dmi.product.sku: 081C
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.107-8ubuntu1~20.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx 21.2.6-0ubuntu0.1~20.04.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1992995/+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 1951491] Re: Can't run snaps: .slice/session-1.scope is not a snap cgroup

2022-10-16 Thread Michael Hudson-Doyle

I think the issue here is that snaps (with cgroupsv2) require a systemd
user session and some desktop environments do not set this up? It's not
clear to me what needs to change here -- should snapd be more tolerant
of this situation or should the other desktop environments change to set
the necessary environment variables?

** Changed in: systemd (Ubuntu)
   Status: Confirmed => Incomplete

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

Title:
  Can't run snaps: .slice/session-1.scope is not a snap cgroup

Status in X2Go:
  New
Status in snapd package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Incomplete
Status in x2goserver package in Ubuntu:
  Confirmed
Status in snapd package in Debian:
  New

Bug description:
  I just upgraded from hirsute to impish using do-release-upgrade. On
  the upgraded system, I can't run either firefox or chromium (both of
  which worked fine under hirsute). Both fail with:

  /user.slice/user-NNN.slice/session-1.scope is not a snap cgroup where
  NNN is my uid

  With firefox, I was able to fix the problem with:

  snap remove --purge firefox
  apt purge firefox
  apt install firefox

  Now firefox works. But I tried the same thing substituting chromium-
  browser for firefox, and it didn't help: chromium fails with the same
  error message.

  I guess there must be something left over from the hirsute version of
  snapd that isn't getting noticed or cleared by the impish version?

  Someone suggested this might be related to bug 1850667, but that bug
  is marked fixed as of a couple months ago, and I just did this upgrade
  today. Also, it doesn't mention the error message I'm seeing.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: snapd 2.53+21.10ubuntu1
  ProcVersionSignature: Ubuntu 5.13.0-21.21-generic 5.13.18
  Uname: Linux 5.13.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Thu Nov 18 18:12:45 2021
  InstallationDate: Installed on 2020-04-29 (568 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  SourcePackage: snapd
  UpgradeStatus: Upgraded to impish on 2021-11-18 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/x2go/+bug/1951491/+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 1269840] Re: ubuntu-bug ubuntu-bug doesn't work

2022-10-16 Thread Michael Hudson-Doyle

** Changed in: apport (Ubuntu)
   Importance: Undecided => Low

** Changed in: apport (Ubuntu)
   Status: Confirmed => Triaged

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

Title:
  ubuntu-bug ubuntu-bug doesn't work

Status in apport package in Ubuntu:
  Triaged

Bug description:
  ubuntu-bug doesn't make program lookup when package lookup failed.
  This is inconvenient for users, who don't know about `which` command.
  Is it possible to automate lookup and continue search until something
  matches?

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: apport 2.12.5-0ubuntu2.2
  ProcVersionSignature: Ubuntu 3.11.0-15.23-generic 3.11.10
  Uname: Linux 3.11.0-15-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.12.5-0ubuntu2.2
  Architecture: i386
  CrashReports:
   640:1000:122:1423125:2014-01-09 20:22:25.104739665 +0300:2014-01-09 
20:22:26.104739665 
+0300:/var/crash/_usr_lib_i386-linux-gnu_bamf_bamfdaemon.1000.crash
   640:1000:122:157297300:2014-01-09 20:56:44.036795854 +0300:2014-01-09 
20:56:45.036795854 +0300:/var/crash/_usr_bin_compiz.1000.crash
   640:0:122:4884804:2014-01-10 13:10:06.891414880 +0300:2014-01-10 
13:10:07.891414880 +0300:/var/crash/_usr_bin_Xorg.0.crash
  Date: Thu Jan 16 18:10:59 2014
  InstallationDate: Installed on 2012-03-12 (675 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta i386 (20120301)
  MarkForUpload: True
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: Upgraded to saucy on 2013-10-21 (87 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1269840/+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 1992688] Re: firefox deb not installed

2022-10-16 Thread Michael Hudson-Doyle

This just needs to be backported to Jammy now?

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

Title:
  firefox deb not installed

Status in firefox package in Ubuntu:
  New
Status in ubuntu-meta package in Ubuntu:
  Fix Released
Status in firefox source package in Jammy:
  New
Status in ubuntu-meta source package in Jammy:
  Triaged

Bug description:
  Bug 1964036 leads me to believe that the firefox deb provides some
  important functionality (the firefox favourite icon in the gnome shell
  dock) but there is nothing that would require the deb to be installed
  (it is not seeded nor has an rdep) and the package description
  indicates that it can be safely removed. Is there some important
  functionality that it provides?

  ProblemType: BugDistroRelease: Ubuntu 22.10
  Package: ubuntu-release-upgrader-core 1:22.10.8
  ProcVersionSignature: User Name 5.19.0-19.19-generic 5.19.7
  Uname: Linux 5.19.0-19-generic x86_64
  ApportVersion: 2.23.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckMismatches: ./boot/grub/grub.cfg
  CasperMD5CheckResult: fail
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct 12 11:30:46 2022
  InstallationDate: Installed on 2022-04-27 (167 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bashSourcePackage: ubuntu-release-upgrader
  Symptom: ubuntu-release-upgrader
  UpgradeStatus: Upgraded to kinetic on 2022-10-12 (0 days ago)
  VarLogDistupgradeTermlog:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1992688/+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 1992430] Re: Snap based apps crash after 5.19.0-18->5.19.0-19 kernel upgrade

2022-10-16 Thread John Johansen

*** This bug is a duplicate of bug 1991691 ***
https://bugs.launchpad.net/bugs/1991691

** This bug has been marked a duplicate of bug 1991691
   cannot change mount namespace

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

Title:
  Snap based apps crash after 5.19.0-18->5.19.0-19 kernel upgrade

Status in apparmor package in Ubuntu:
  New

Bug description:
  This occurs on Ubuntu ver. 22.10.
  Here is an example:

  skype 
  update.go:85: cannot change mount namespace according to change mount 
(/run/user/1000/doc/by-app/snap.skype /run/user/1000/doc none 
bind,rw,x-snapd.ignore-missing 0 0): cannot inspect "/run/user/1000/doc": lstat 
/run/user/1000/doc: permission denied
  + [ -f /home/user/snap/skype/common/.config/skypeforlinux/settings.json ]
  + export SKYPE_LOGS=/home/user/snap/skype/231/logs
  + [ ! -d /home/user/snap/skype/231/logs ]
  + exec /snap/skype/231/usr/share/skypeforlinux/skypeforlinux

  (skypeforlinux:9439): Gtk-WARNING **: 10:13:12.251: Theme parsing error: 
gtk.css:3536:25: 'font-feature-settings' is not a valid property name
  Gtk-Message: 10:13:12.294: Failed to load module "colorreload-gtk-module"
  Gtk-Message: 10:13:12.295: Failed to load module 
"window-decorations-gtk-module"
  [1011/101312.442717:ERROR:scoped_ptrace_attach.cc(27)] ptrace: Permission 
denied (13)
  Nyomkövetési/töréspont csapda (core készült)

  Google translation: Trace/breakpoint trap (core made)

  Here is an another one:
  teams
  update.go:85: cannot change mount namespace according to change mount 
(/var/lib/snapd/hostfs/usr/share/fonts /usr/share/fonts none bind,ro 0 0): 
cannot inspect "/var/lib/snapd/hostfs/usr/share/fonts": lstat 
/var/lib/snapd/hostfs/usr/share/fonts: permission denied
  update.go:85: cannot change mount namespace according to change mount 
(/var/lib/snapd/hostfs/usr/local/share/fonts /usr/local/share/fonts none 
bind,ro 0 0): cannot inspect "/usr/local/share/fonts": lstat 
/usr/local/share/fonts: permission denied
  update.go:85: cannot change mount namespace according to change mount 
(/run/user/1000/doc/by-app/snap.teams /run/user/1000/doc none 
bind,rw,x-snapd.ignore-missing 0 0): cannot inspect "/run/user/1000/doc": lstat 
/run/user/1000/doc: permission denied

  Loading of the previous kernel fixes the issue this is why I think it
  could be kernel-related or something like that.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1992430/+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 1992430] Re: Snap based apps crash after 5.19.0-18->5.19.0-19 kernel upgrade

2022-10-16 Thread John Johansen

*** This bug is a duplicate of bug 1991691 ***
https://bugs.launchpad.net/bugs/1991691

It is not a duplicate of
https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1991691

** This bug is no longer a duplicate of bug 1991691
   cannot change mount namespace

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

Title:
  Snap based apps crash after 5.19.0-18->5.19.0-19 kernel upgrade

Status in apparmor package in Ubuntu:
  New

Bug description:
  This occurs on Ubuntu ver. 22.10.
  Here is an example:

  skype 
  update.go:85: cannot change mount namespace according to change mount 
(/run/user/1000/doc/by-app/snap.skype /run/user/1000/doc none 
bind,rw,x-snapd.ignore-missing 0 0): cannot inspect "/run/user/1000/doc": lstat 
/run/user/1000/doc: permission denied
  + [ -f /home/user/snap/skype/common/.config/skypeforlinux/settings.json ]
  + export SKYPE_LOGS=/home/user/snap/skype/231/logs
  + [ ! -d /home/user/snap/skype/231/logs ]
  + exec /snap/skype/231/usr/share/skypeforlinux/skypeforlinux

  (skypeforlinux:9439): Gtk-WARNING **: 10:13:12.251: Theme parsing error: 
gtk.css:3536:25: 'font-feature-settings' is not a valid property name
  Gtk-Message: 10:13:12.294: Failed to load module "colorreload-gtk-module"
  Gtk-Message: 10:13:12.295: Failed to load module 
"window-decorations-gtk-module"
  [1011/101312.442717:ERROR:scoped_ptrace_attach.cc(27)] ptrace: Permission 
denied (13)
  Nyomkövetési/töréspont csapda (core készült)

  Google translation: Trace/breakpoint trap (core made)

  Here is an another one:
  teams
  update.go:85: cannot change mount namespace according to change mount 
(/var/lib/snapd/hostfs/usr/share/fonts /usr/share/fonts none bind,ro 0 0): 
cannot inspect "/var/lib/snapd/hostfs/usr/share/fonts": lstat 
/var/lib/snapd/hostfs/usr/share/fonts: permission denied
  update.go:85: cannot change mount namespace according to change mount 
(/var/lib/snapd/hostfs/usr/local/share/fonts /usr/local/share/fonts none 
bind,ro 0 0): cannot inspect "/usr/local/share/fonts": lstat 
/usr/local/share/fonts: permission denied
  update.go:85: cannot change mount namespace according to change mount 
(/run/user/1000/doc/by-app/snap.teams /run/user/1000/doc none 
bind,rw,x-snapd.ignore-missing 0 0): cannot inspect "/run/user/1000/doc": lstat 
/run/user/1000/doc: permission denied

  Loading of the previous kernel fixes the issue this is why I think it
  could be kernel-related or something like that.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1992430/+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 1992930] Re: chromium won't launch at menu when installed; lubuntu kinetic

2022-10-16 Thread Alex Murray

This current bug looks like LP: #1991691

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

Title:
  chromium won't launch at menu when installed; lubuntu kinetic

Status in apparmor package in Ubuntu:
  New

Bug description:
  Lubuntu kinetic live test

  `chromium` snap once installed; will not open from menu, but will open
  if started from terminal.  This maybe filed against incorrect package
  sorry.

  Originally reported here - https://discourse.lubuntu.me/t/lubuntu-
  kinetic-after-5-19-update-chromium-only-start-from-terminal/3685 where
  it was reported as an issue on the 5.19.0-19-generic kernel update

  ** to re-create

  - boot currently lubuntu kinetic daily
  - snap install chromium
  - using menu, attempt to run chromium from internet apps

  ** expected outcome

  chromium starts

  ** actual outcome

  menu just closes; no messages.

  ** further notes

  u/FossFreedom (Ubuntu Budgie) reports no issues with Ubuntu Budgie
  kinetic starting Chromium.

  On Lubuntu's discourse; u/neblaz (OP for issue) also reported issues starting 
Opera; with that package being the snap (loaded from discover) and reported as 
(using `snap list`)
  opera   91.0.4516.77202
latest/stable

  
  ** in `dmesg` I note the following (this may be unrelated or unhelpful sorry)

  [ 1510.255228] loop7: detected capacity change from 0 to 293648
  [ 1510.739240] audit: type=1400 audit(1665727470.633:54): apparmor="STATUS" 
operation="profile_load" profile="unconfined" name="snap-update-ns.chromium" 
pid=3359 comm="apparmor_parser"
  [ 1510.820094] audit: type=1400 audit(1665727470.713:55): apparmor="STATUS" 
operation="profile_load" profile="unconfined" name="snap.chromium.chromedriver" 
pid=3360 comm="apparmor_parser"
  [ 1511.014103] audit: type=1400 audit(1665727470.909:56): apparmor="STATUS" 
operation="profile_load" profile="unconfined" name="snap.chromium.chromium" 
pid=3361 comm="apparmor_parser"
  [ 1511.071575] audit: type=1400 audit(1665727470.965:57): apparmor="STATUS" 
operation="profile_load" profile="unconfined" 
name="snap.chromium.hook.configure" pid=3362 comm="apparmor_parser"
  [ 1515.313383] audit: type=1400 audit(1665727475.206:58): apparmor="STATUS" 
operation="profile_replace" info="same as current profile, skipping" 
profile="unconfined" name="/snap/snapd/17029/usr/lib/snapd/snap-confine" 
pid=3496 comm="apparmor_parser"
  [ 1515.313401] audit: type=1400 audit(1665727475.206:59): apparmor="STATUS" 
operation="profile_replace" info="same as current profile, skipping" 
profile="unconfined" 
name="/snap/snapd/17029/usr/lib/snapd/snap-confine//mount-namespace-capture-helper"
 pid=3496 comm="apparmor_parser"
  [ 1516.817149] audit: type=1400 audit(1665727476.710:60): apparmor="STATUS" 
operation="profile_replace" profile="unconfined" name="snap-update-ns.chromium" 
pid=3498 comm="apparmor_parser"
  [ 1518.067335] audit: type=1400 audit(1665727477.962:61): apparmor="STATUS" 
operation="profile_replace" profile="unconfined" 
name="snap.chromium.chromedriver" pid=3499 comm="apparmor_parser"
  [ 1518.568962] audit: type=1400 audit(1665727478.462:62): apparmor="STATUS" 
operation="profile_replace" profile="unconfined" 
name="snap.chromium.hook.configure" pid=3501 comm="apparmor_parser"
  [ 1519.485025] audit: type=1400 audit(1665727479.378:63): apparmor="STATUS" 
operation="profile_replace" profile="unconfined" name="snap.chromium.chromium" 
pid=3500 comm="apparmor_parser"
  [ 1520.203518] audit: type=1400 audit(1665727480.098:64): apparmor="DENIED" 
operation="getattr" class="file" profile="snap-update-ns.chromium" 
name="/meta/snap.yaml" pid=3518 comm="6" requested_mask="r" denied_mask="r" 
fsuid=0 ouid=0
  [ 1520.245234] audit: type=1400 audit(1665727480.142:65): apparmor="DENIED" 
operation="getattr" class="file" profile="snap-update-ns.chromium" 
name="/usr/local/share/fonts/" pid=3518 comm="6" requested_mask="r" 
denied_mask="r" fsuid=0 ouid=0
  [ 1520.245256] audit: type=1400 audit(1665727480.142:66): apparmor="DENIED" 
operation="getattr" class="file" profile="snap-update-ns.chromium" 
name="/usr/local/share/" pid=3518 comm="6" requested_mask="r" denied_mask="r" 
fsuid=0 ouid=0
  [ 1520.246876] audit: type=1400 audit(1665727480.142:67): apparmor="DENIED" 
operation="getattr" class="file" profile="snap-update-ns.chromium" 
name="/var/lib/snapd/hostfs/usr/share/doc/" pid=3518 comm="6" 
requested_mask="r" denied_mask="r" fsuid=0 ouid=0
  [ 1520.246933] audit: type=1400 audit(1665727480.142:68): apparmor="DENIED" 
operation="getattr" class="file" profile="snap-update-ns.chromium" 
name="/var/lib/snapd/hostfs/usr/share/fonts/" pid=3518 comm="6" 
requested_mask="r" denied_mask="r" fsuid=0 ouid=0
  [ 1520.349971] audit: type=1400 audit(1665727480.246:69): apparmor="DENIED" 
operation="getattr" class="file"

[Touch-packages] [Bug 1993084] [NEW] libkrb5-dev: dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)

2022-10-16 Thread Keith David Bershatsky

Public bug reported:

Ubuntu 22.04.1 LTS:  sudo apt install libkrb5-dev

Installation fails with this message:

dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)

I had tried to install this package as a dependency of building Wine
from source:

configure: libkrb5 32-bit/64-bit development files not found (or too
old), Kerberos won't be supported.

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

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

Title:
  libkrb5-dev:  dpkg-deb: error: paste subprocess was killed by signal
  (Broken pipe)

Status in krb5 package in Ubuntu:
  New

Bug description:
  Ubuntu 22.04.1 LTS:  sudo apt install libkrb5-dev

  Installation fails with this message:

  dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)

  I had tried to install this package as a dependency of building Wine
  from source:

  configure: libkrb5 32-bit/64-bit development files not found (or too
  old), Kerberos won't be supported.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/krb5/+bug/1993084/+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 862280] Re: Patch cannot handle spaces in filenames

2022-10-16 Thread i30817

10 years later, I still have to remember to add tabs manually every time
i do a refresh from quilt. Is there any patch alternative i can install
that is sane instead of insane about their precious purity of not using
spaces in pathnames?

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

Title:
  Patch cannot handle spaces in filenames

Status in patch package in Ubuntu:
  Confirmed

Bug description:
  When there are spaces in a filename in a patch file, quilt is unable
  to properly apply the patch. See this patch file example:

  --- a/foo bar/file.txt
  +++ b/foo bar/file.txt
  

  The patch is applied on 'a/foo' instead of 'a/foo bar/file.txt'

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/patch/+bug/862280/+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 1949340] Re: [upstream] Saving downloads or pages is difficult because of unfocused file chooser dialog

2022-10-16 Thread kowach

Same with upload dialog and it does not remembers last directory. It
always starts from home directory.

Ubuntu Mate 22.04.1 LTS

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

Title:
  [upstream] Saving downloads or pages is difficult because of unfocused
  file chooser dialog

Status in Mozilla Firefox:
  New
Status in chromium-browser package in Ubuntu:
  Confirmed
Status in firefox package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in gtk+3.0 package in Ubuntu:
  Confirmed
Status in gtk4 package in Ubuntu:
  Confirmed
Status in xdg-desktop-portal-gnome package in Ubuntu:
  Confirmed
Status in xdg-desktop-portal-gtk package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce:
  1. Open Chromium (release does not matter, here deb-packaged version from 
18.04 LTS is used)
  2a. Navigate to some page, press +
  2b. Navigate to some page, with "Ask where to save each file before 
downloading" enabled try to download some file

  Actual result:
  * file chooser dialog is unfocused, user should select the window by mouse 
and then hit  for specified location

  Expected result:
  * file chooser dialog is focused, user can simply hit  to save in 
previously selected location.

To manage notifications about this bug go to:
https://bugs.launchpad.net/firefox/+bug/1949340/+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 1993067] [NEW] Missing dependency of network-manager to iwd

2022-10-16 Thread Martin Schreiber

Public bug reported:

It seems that the current network-manager in Ubuntu 22.10 would like to
use iwd per default after the upgrade.

However, there's no dependency to the iwd package resulting in a lack of
wifi support after the upgrade.

** Affects: network-manager (Ubuntu)
 Importance: Undecided
 Status: New

** Project changed: launchpad => network-manager (Ubuntu)

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

Title:
  Missing dependency of network-manager to iwd

Status in network-manager package in Ubuntu:
  New

Bug description:
  It seems that the current network-manager in Ubuntu 22.10 would like
  to use iwd per default after the upgrade.

  However, there's no dependency to the iwd package resulting in a lack
  of wifi support after the upgrade.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1993067/+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 1993067] [NEW] Missing dependency of network-manager to iwd

2022-10-16 Thread Launchpad Bug Tracker

You have been subscribed to a public bug:

It seems that the current network-manager in Ubuntu 22.10 would like to
use iwd per default after the upgrade.

However, there's no dependency to the iwd package resulting in a lack of
wifi support after the upgrade.

** Affects: network-manager (Ubuntu)
 Importance: Undecided
 Status: New

-- 
Missing dependency of network-manager to iwd
https://bugs.launchpad.net/bugs/1993067
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to network-manager in Ubuntu.

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

2022-10-16 Thread paul

(In reply to Cameron Berkenpas from comment #702)
 
> jochemp...@gmail.com & toyeisf...@gmail.com,
> My suggestion for both of you is to follow up with Lenovo support as I
> mentioned and see where that gets us. If enough of us take issue, they might
> be inclined to fix it.
> 
> Failing that, if enough of us are affected, maybe we can start a petition?
> 
> I still haven't been able to follow up on my ticket. Too busy with work/life.

Same issue for me on a Legion S7 16ARHA7. I've opened a support case
with Lenovo, let's see how it goes.

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

Title:
  [Lenovo Legion7 16ACHg6 82N6, Realtek ALC287, Speaker, Internal] No
  sound at all

Status in sound-2.6 (alsa-kernel):
  Confirmed
Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  On my Lenovo Legion-7-16ACHg6 laptop I can't hear any sound by
  internal speakers, but it work by headphones connected to standard
  jack aux.

  uname -r
  5.11.0-44-generic

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.11.0-44.48~20.04.2-generic 5.11.22
  Uname: Linux 5.11.0-44-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  i3draven   1266 F pulseaudio
   /dev/snd/controlC0:  i3draven   1266 F pulseaudio
   /dev/snd/controlC1:  i3draven   1266 F pulseaudio
   /dev/snd/pcmC1D0p:   i3draven   1266 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jan 15 15:10:53 2022
  InstallationDate: Installed on 2021-10-11 (96 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed
  Symptom_Card: Family 17h (Models 10h-1fh) HD Audio Controller - HD-Audio 
Generic
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  i3draven   1266 F pulseaudio
   /dev/snd/controlC0:  i3draven   1266 F pulseaudio
   /dev/snd/controlC1:  i3draven   1266 F pulseaudio
   /dev/snd/pcmC1D0p:   i3draven   1266 F...m pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [82N6, Realtek ALC287, Speaker, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/08/2021
  dmi.bios.release: 1.49
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GKCN49WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0R32862 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Legion 7 16ACHg6
  dmi.ec.firmware.release: 1.49
  dmi.modalias: 
dmi:bvnLENOVO:bvrGKCN49WW:bd11/08/2021:br1.49:efr1.49:svnLENOVO:pn82N6:pvrLegion716ACHg6:skuLENOVO_MT_82N6_BU_idea_FM_Legion716ACHg6:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLegion716ACHg6:
  dmi.product.family: Legion 7 16ACHg6
  dmi.product.name: 82N6
  dmi.product.sku: LENOVO_MT_82N6_BU_idea_FM_Legion 7 16ACHg6
  dmi.product.version: Legion 7 16ACHg6
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/sound-2.6/+bug/1958019/+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 1842320] Re: Can't boot: "error: out of memory." immediately after the grub menu

2022-10-16 Thread Stefan Akatyschew

I can replicate this on my Dell XPS13 9380 (no encryption). Occurs as well with 
Ubuntu 20.04 LTS, but not with 18.04 LTS, so not sure if it is related to the 
same reason?
-> Disabling Secure Boot and SGX did not resolve the issue

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

Title:
  Can't boot: "error: out of memory." immediately after the grub menu

Status in grub:
  Unknown
Status in OEM Priority Project:
  Triaged
Status in grub2-signed package in Ubuntu:
  Triaged
Status in initramfs-tools package in Ubuntu:
  Won't Fix
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  [Impact]

   * In some cases, if the users’ initramfs grow bigger, then it’ll
  likely not be able to be loaded by grub2.

   * Some real cases from OEM projects:

  In many built-in 4k monitor laptops with nvidia drivers, the u-d-c
  puts the nvidia*.ko to initramfs which grows the initramfs to ~120M.
  Also the gfxpayload=auto will remain to use 4K resolution since it’s
  what EFI POST passed.

  In this case, the grub isn't able to load initramfs because the
  grub_memalign() won't be able to get suitable memory for the larger
  file:

  ```
  #0 grub_memalign (align=1, size=592214020) at ../../../grub-core/kern/mm.c:376
  #1 0x7dd7b074 in grub_malloc (size=592214020) at 
../../../grub-core/kern/mm.c:408
  #2 0x7dd7a2c8 in grub_verifiers_open (io=0x7bc02d80, type=131076)
  at ../../../grub-core/kern/verifiers.c:150
  #3 0x7dd801d4 in grub_file_open (name=0x7bc02f00 
"/boot/initrd.img-5.17.0-1011-oem",
  type=131076) at ../../../grub-core/kern/file.c:121
  #4 0x7bcd5a30 in ?? ()
  #5 0x7fe21247 in ?? ()
  #6 0x7bc030c8 in ?? ()
  #7 0x00017fe21238 in ?? ()
  #8 0x7bcd5320 in ?? ()
  #9 0x7fe21250 in ?? ()
  #10 0x in ?? ()
  ```

  Based on grub_mm_dump, we can see the memory fragment (some parts seem
  likely be used because of 4K resolution?) and doesn’t have available
  contiguous memory for larger file as:

  ```
  grub_real_malloc(...)
  ...
  if (cur->size >= n + extra)
  ```

  Based on UEFI Specification Section 7.2[1] and UEFI driver writers’
  guide 4.2.3[2], we can ask 32bits+ on AllocatePages().

  As most X86_64 platforms should support 64 bits addressing, we should
  extend GRUB_EFI_MAX_USABLE_ADDRESS to 64 bits to get more available
  memory.

   * When users grown the initramfs, then probably will get initramfs
  not found which really annoyed and impact the user experience (system
  not able to boot).

  [Test Plan]

   * detailed instructions how to reproduce the bug:

  1. Any method to grow the initramfs, such as install nvidia-driver.

  2. If developers would like to reproduce, then could dd if=/dev/random
  of=... bs=1M count=500, something like:

  ```
  $ cat /usr/share/initramfs-tools/hooks/zzz-touch-a-file
  #!/bin/sh

  PREREQ=""

  prereqs()
  {
  echo "$PREREQ"
  }

  case $1 in
  # get pre-requisites
  prereqs)
  prereqs
  exit 0
  ;;
  esac

  . /usr/share/initramfs-tools/hook-functions
  dd if=/dev/random of=${DESTDIR}/test-500M bs=1M count=500
  ```

  And then update-initramfs

   * After applying my patches, the issue is gone.

   * I did also test my test grubx64.efi in:

  1. X86_64 qemu with
  1.1. 60M initramfs + 5.15.0-37-generic kernel
  1.2. 565M initramfs + 5.17.0-1011-oem kernel

  2. Amd64 HP mobile workstation with
  2.1. 65M initramfs + 5.15.0-39-generic kernel
  2.2. 771M initramfs + 5.17.0-1011-oem kernel

  All working well.

  [Where problems could occur]

  * The changes almost in i386/efi, thus the impact will be in the i386 / 
x86_64 EFI system.
  The other change is to modify the “grub-core/kern/efi/mm.c” but I use the 
original addressing for “arm/arm64/ia64/riscv32/riscv64”.
  Thus it should not impact them.

  * There is a “#if defined(__x86_64__)” which intent to limit the >
  32bits code in i386 system and also

  ```
   #if defined (__code_model_large__)
  -#define GRUB_EFI_MAX_USABLE_ADDRESS 0x
  +#define GRUB_EFI_MAX_USABLE_ADDRESS __UINTPTR_MAX__
  +#define GRUB_EFI_MAX_ALLOCATION_ADDRESS 0x7fff
   #else
   #define GRUB_EFI_MAX_USABLE_ADDRESS 0x7fff
  +#define GRUB_EFI_MAX_ALLOCATION_ADDRESS 0x3fff
   #endif
  ```

  If everything works as expected, then i386 should working good.

  If not lucky, based on “UEFI writers’ guide”[2], the i386 will get >
  4GB memory region and never be able to access.

  [Other Info]

   * Upstream grub2 bug #61058
  https://savannah.gnu.org/bugs/index.php?61058

   * Test PPA: https://launchpad.net/~os369510/+archive/ubuntu/lp1842320

   * Test grubx64.efi:
  https://people.canonical.com/~jeremysu/lp1842320/grubx64.efi.lp1842320

   * Test source code: https://github.com/os369510/grub2/tree/lp1842320

   * If you built the package, then

[Touch-packages] [Bug 1713803] Re: replacement of resolvconf with systemd needs integration

[Touch-packages] [Bug 1713803] Re: replacement of resolvconf with systemd needs integration

[Touch-packages] [Bug 1990743] Re: resolvconf install fails upgrading from Jammy to Kinetic

[Touch-packages] [Bug 1990743] Re: RM: resolvconf, openresolv (and blacklist)

[Touch-packages] [Bug 1971984] Re: pcscd 1.9.5-3 do not start automatically, only manual

[Touch-packages] [Bug 1993027] Re: Display settings lost when leaving screen saver / screen switch

[Touch-packages] [Bug 1951491] Re: Can't run snaps: .slice/session-1.scope is not a snap cgroup

[Touch-packages] [Bug 1992995] Re: Graphics

[Touch-packages] [Bug 1951491] Re: Can't run snaps: .slice/session-1.scope is not a snap cgroup

[Touch-packages] [Bug 1269840] Re: ubuntu-bug ubuntu-bug doesn't work

[Touch-packages] [Bug 1992688] Re: firefox deb not installed

[Touch-packages] [Bug 1992430] Re: Snap based apps crash after 5.19.0-18->5.19.0-19 kernel upgrade

[Touch-packages] [Bug 1992430] Re: Snap based apps crash after 5.19.0-18->5.19.0-19 kernel upgrade

[Touch-packages] [Bug 1992930] Re: chromium won't launch at menu when installed; lubuntu kinetic

[Touch-packages] [Bug 1993084] [NEW] libkrb5-dev: dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)

[Touch-packages] [Bug 862280] Re: Patch cannot handle spaces in filenames

[Touch-packages] [Bug 1949340] Re: [upstream] Saving downloads or pages is difficult because of unfocused file chooser dialog

[Touch-packages] [Bug 1993067] [NEW] Missing dependency of network-manager to iwd

[Touch-packages] [Bug 1993067] [NEW] Missing dependency of network-manager to iwd

[Touch-packages] [Bug 1958019]

[Touch-packages] [Bug 1842320] Re: Can't boot: "error: out of memory." immediately after the grub menu

21 matches

Site Navigation

Mail list logo

Footer information