[Touch-packages] [Bug 2062667] Re: Fails on (and should be removed from) raspi desktop

[Ubuntu QA Website]

This bug has been reported on the Ubuntu ISO testing tracker.

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

** Tags added: iso-testing

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

Title:
  Fails on (and should be removed from) raspi desktop

Status in protection-domain-mapper package in Ubuntu:
  Confirmed
Status in qrtr package in Ubuntu:
  Confirmed
Status in ubuntu-meta package in Ubuntu:
  Confirmed

Bug description:
  The protection-domain-mapper package (and qrtr-tools) are both
  installed by default on the Ubuntu Desktop for Raspberry Pi images,
  thanks to their inclusion in the desktop-minimal seed for arm64.
  However, there's no hardware that they target on these platforms, and
  the result is a permanently failed service (pd-mapper.service).

  It appears these were added to support the X13s laptop [1]. I've
  attempted to work around the issue by excluding these packages in the
  desktop-raspi seed (experimentally in my no-pd-mapper branch [2]) but
  this does not work (the packages still appear in the built images).
  Ideally, these packages should be moved into a hardware-specific seed
  for the X13s (and/or whatever other laptops need these things).
  Alternatively, at a bare minimum, the package should have some
  conditional that causes the service not to attempt to start when it's
  not on Qualcomm hardware.

  [1]: https://git.launchpad.net/~ubuntu-core-dev/ubuntu-
  seeds/+git/ubuntu/commit/desktop-
  minimal?id=afe820cd49514896e96d02303298ed873d8d7f8a

  [2]: https://git.launchpad.net/~waveform/ubuntu-
  seeds/+git/ubuntu/commit/?id=875bddac19675f7e971f56d9c5d39a9912dc6e38

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/protection-domain-mapper/+bug/2062667/+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 2063003] Re: package manager could not make changes to the installed system

[Ubuntu QA Website]

This bug has been reported on the Ubuntu ISO testing tracker.

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

** Tags added: iso-testing

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

Title:
  package manager could not make changes to the installed system

Status in apt package in Ubuntu:
  New

Bug description:
  This is the cause of Ubuntu Unity failing to install. Test case
  requires system to be offline.

  The full error message is:
  The package manager could not make changes to the installed system. The 
command apt-get --purge -q -y remove ^live-* 
calamares-settings-ubuntu-unity calamares zram-config cifs-utils returned 
error code 100.

  There are no logs in /var/log/installer or /var/crash

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/2063003/+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 2061214] Re: Software sources not correctly updated after upgrade

[Ubuntu QA Website]

This bug has been reported on the Ubuntu ISO testing tracker.

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

** Tags added: iso-testing

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

Title:
  Software sources not correctly updated after upgrade

Status in software-properties package in Ubuntu:
  New

Bug description:
  Upgrading Lubuntu Jammy to Lubuntu Noble using TUI results in
  "Software sources" not correctly updated after upgrade. Prompt= shows
  normal and not LTS

  Otherwise the upgrade is good

  see attached screenshot

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: software-properties-common 0.99.46
  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: LXQt
  Date: Sat Apr 13 11:44:28 2024
  InstallationDate: Installed on 2024-04-13 (0 days ago)
  InstallationMedia: Lubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 
(20240331)
  PackageArchitecture: all
  SourcePackage: software-properties
  UpgradeStatus: Upgraded to noble on 2024-04-13 (0 days ago)
  mtime.conffile..etc.init.d.apport: 2024-02-22T14:20:00

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2061214/+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 login sound on Ubuntu desktop

[Ubuntu QA Website]

This bug has been reported on the Ubuntu ISO testing tracker.

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

** Tags added: iso-testing

-- 
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 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 2060730] Re: totem cannot install codecs via packagekit

[Ubuntu QA Website]

This bug has been reported on the Ubuntu ISO testing tracker.

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

** Tags added: iso-testing

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

Title:
  totem cannot install codecs via packagekit

Status in packagekit package in Ubuntu:
  New
Status in totem package in Ubuntu:
  New

Bug description:
  While attempting to play a video on Ubuntu noble desktop for raspberry
  pi, totem attempts to locate a package for the H.264 codec but cannot
  find a service providing org.freedesktop.PackageKit. This is strange
  given that packagekit is installed, provides packagekit.service, which
  declares that it provides that name over DBus. Specifically, the
  following is output by totem:

  ** Message: 21:13:39.000: Missing plugin: gstreamer|1.0|totem|MPEG-4 AAC 
decoder|decoder-audio/mpeg, mpegversion=(int)4, level=(string)4, 
base-profile=(string)lc, profile=(string)lc (MPEG-4 AAC decoder)
  ** Message: 21:13:39.000: Missing plugin: gstreamer|1.0|totem|H.264 (Main 
Profile) decoder|decoder-video/x-h264, level=(string)3.1, profile=(string)main 
(H.264 (Main Profile) decoder)
  ** Message: 21:13:39.414: PackageKit: xid = 0
  ** Message: 21:13:39.414: PackageKit: desktop_id = org.gnome.Totem.desktop
  ** Message: 21:13:39.414: PackageKit: Codec nice name: MPEG-4 AAC decoder
  ** Message: 21:13:39.414: PackageKit: ignoring field named level
  ** Message: 21:13:39.414: PackageKit: ignoring field named base-profile
  ** Message: 21:13:39.414: PackageKit: ignoring field named profile
  ** Message: 21:13:39.414: PackageKit: field is: mpegversion, type: gint
  ** Message: 21:13:39.414: PackageKit: structure: 
gstreamer1(decoder-audio/mpeg)(mpegversion=4)()(64bit)
  ** Message: 21:13:39.414: PackageKit: Codec nice name: H.264 (Main 
Profile) decoder
  ** Message: 21:13:39.414: PackageKit: ignoring field named level
  ** Message: 21:13:39.414: PackageKit: ignoring field named profile
  ** Message: 21:13:39.414: PackageKit: structure: 
gstreamer1(decoder-video/x-h264)()(64bit)
  ** Message: 21:13:39.434: PackageKit: Did not install codec: 
GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name 
org.freedesktop.PackageKit was not provided by any .service files
  ** Message: 21:13:39.441: No installation candidate for missing plugins 
found.

  The packagekit.service is defined as:

  $ systemctl cat packagekit.service
  # /usr/lib/systemd/system/packagekit.service
  [Unit]
  Description=PackageKit Daemon
  # PK doesn't know how to do anything on ostree-managed systems;
  # currently the design is to have dedicated daemons like
  # eos-updater and rpm-ostree, and gnome-software talks to those.
  ConditionPathExists=!/run/ostree-booted
  Wants=network-online.target
  
  [Service]
  Type=dbus
  BusName=org.freedesktop.PackageKit
  User=root
  ExecStart=/usr/libexec/packagekitd

  And just to demonstrate packagekit is actually running:

  $ systemctl status packagekit.service
  ● packagekit.service - PackageKit Daemon
   Loaded: loaded (/usr/lib/systemd/system/packagekit.service; static)
   Active: active (running) since Tue 2024-04-09 21:11:35 BST; 2min 23s 
ago
 Main PID: 1565 (packagekitd)
Tasks: 4 (limit: 3864)
   Memory: 6.2M (peak: 6.7M)
  CPU: 180ms
   CGroup: /system.slice/packagekit.service
   └─1565 /usr/libexec/packagekitd
  
  Apr 09 21:11:34 fozzie systemd[1]: Starting packagekit.service - 
PackageKit Daemon...
  Apr 09 21:11:34 fozzie PackageKit[1565]: daemon start
  Apr 09 21:11:35 fozzie systemd[1]: Started packagekit.service - 
PackageKit Daemon.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/packagekit/+bug/2060730/+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 2060311] Re: Setting "optional: true" to overcome he timeout "Job systemd-networkd-wait-online" does no longer work with latest noble image

[Ubuntu QA Website]

This bug has been reported on the Ubuntu ISO testing tracker.

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

** Tags added: iso-testing

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

Title:
  Setting "optional: true" to overcome he timeout "Job systemd-networkd-
  wait-online" does no longer work with latest noble image

Status in Netplan:
  New
Status in Ubuntu on IBM z Systems:
  New
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  Especially on s390x (but not limited to s390x) it's often the case that a 
system has network devices that are not necessarily connected during boot-up 
and one gets such a 2 min timeout:
  "Job systemd-networkd-wait-online. Start running (1min 59s / no limit)"

  In the past I could avoid that by setting "optional: true" post-install (no 
perfect, but worked),
  but this does no longer seem to work using the latest noble ISO image (Apr 
5th).

  Setting 'optional: true' in /etc/netplan/50-cloud-init.yaml looks like
  this for me:

  # This file is generated from information provided by the datasource.  Changes
  # to it will not persist across an instance reboot.  To disable cloud-init's
  # network configuration capabilities, write a file
  # /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following:
  # network: {config: disabled}
  network:
  ethernets:
  enP1p0s0:
  optional: true
  dhcp4: true
  enP1p0s0d1:
  optional: true
  dhcp4: true
  enP2p0s0:
  optional: true
  dhcp4: true
  enP2p0s0d1:
  optional: true
  dhcp4: true
  encc000: {}
  version: 2
  vlans:
  encc000.2653:
  addresses:
  - 10.11.12.15/24
  gateway4: 10.11.12.1
  id: 2653
  link: encc000
  nameservers:
  addresses:
  - 10.11.12.1

  ... can be set fine (also --dry-run does not moan, except about
  dhcp4).

  This worked in the past on noble, but also on older Ubuntu releases
  like jammy.

To manage notifications about this bug go to:
https://bugs.launchpad.net/netplan/+bug/2060311/+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 2060681] Re: systemd-networkd-wait-online.service halts booting for 2 1/2 minutes

[Ubuntu QA Website]

This bug has been reported on the Ubuntu ISO testing tracker.

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

** Tags added: iso-testing

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

Title:
  systemd-networkd-wait-online.service halts booting for 2 1/2 minutes

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  When booting http://cdimage.ubuntu.com/ubuntu-server/daily-
  preinstalled/20240409/noble-preinstalled-server-riscv64.img.xz the
  system waits for 2 1/2 minutes for systemd-networkd-wait-
  online.service to time out.

  See attached boot chart.
  --- 
  ProblemType: Bug
  ApportVersion: 2.28.0-0ubuntu1
  Architecture: riscv64
  CasperMD5CheckResult: unknown
  CloudArchitecture: riscv64
  CloudBuildName: server
  CloudID: nocloud
  CloudName: unknown
  CloudPlatform: nocloud
  CloudSerial: 20240409
  CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud-net)
  DistroRelease: Ubuntu 24.04
  Lspci-vt:
   -[:00]-+-00.0  Red Hat, Inc. QEMU PCIe Host bridge
  +-01.0  Red Hat, Inc. Virtio RNG
  \-02.0  Red Hat, Inc. Virtio block device
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  Lsusb-t:
   
  Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1:
  Package: systemd 255.4-1ubuntu7
  PackageArchitecture: riscv64
  ProcEnviron:
   LANG=C.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=vt220
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-20-generic 
root=LABEL=cloudimg-rootfs ro efi=debug earlycon 
init=/lib/systemd/systemd-bootchart
  ProcVersionSignature: Ubuntu 6.8.0-20.20.1-generic 6.8.1
  SystemdFailedUnits:
   Error: command ['systemctl', 'status', '--full', '●'] failed with exit code 
4: Invalid unit name "●" escaped as "\xe2\x97\x8f" (maybe you should use 
systemd-escape?).
   Unit \xe2\x97\x8f.service could not be found.
  Tags: cloud-image noble
  Uname: Linux 6.8.0-20-generic riscv64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  acpidump:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2060681/+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 2049210] Re: After install Rasp Pi 4 - system fails to send report info to metrics server

[Ubuntu QA Website]

This bug has been reported on the Ubuntu ISO testing tracker.

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

** Tags added: iso-testing

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

Title:
  After install Rasp Pi 4 - system fails to send report info to metrics
  server

Status in xorg package in Ubuntu:
  New

Bug description:
  Testing Rasp Pi Ubuntu Noble daily iso dated 12-01-2024

  After install system fails to send report info to metrics server,
  (client:timeout exceeded while awaiting headers.

  Will also attach screenshot of error received.

  Not sure if this is correct package for the bug report -

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.5.0-1005.7-raspi 6.5.3
  Uname: Linux 6.5.0-1005-raspi aarch64
  ApportVersion: 2.27.0-0ubuntu6
  Architecture: arm64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CloudArchitecture: aarch64
  CloudID: none
  CloudName: none
  CloudPlatform: none
  CloudSubPlatform: config
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jan 12 14:26:42 2024
  DistUpgraded: Fresh install
  DistroCodename: noble
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   
  Lspci-vt: -[:00]---00.0-[01]00.0  VIA Technologies, Inc. VL805/806 
xHCI USB 3.0 Controller
  ProcEnviron:
   LANG=C.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  ProcKernelCmdLine: coherent_pool=1M 8250.nr_uarts=0 
snd_bcm2835.enable_headphones=0 snd_bcm2835.enable_headphones=1 
snd_bcm2835.enable_hdmi=1 snd_bcm2835.enable_hdmi=0 
video=HDMI-A-1:1920x1080M@60 smsc95xx.macaddr=DC:A6:32:D1:2B:AD 
vc_mem.mem_base=0x3ec0 vc_mem.mem_size=0x4000  zswap.enabled=1 
zswap.zpool=z3fold zswap.compressor=zstd multipath=off dwc_otg.lpm_enable=0 
console=tty1 root=LABEL=writable rootfstype=ext4 rootwait fixrtc quiet splash
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  acpidump:
   
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.117-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 23.3.0-2ubuntu3
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.10-1ubuntu1
  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 N/A
  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/xorg/+bug/2049210/+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 798414] Re: update-initramfs should produce a more helpful error message when there isn't enough free space--or provide an automatic tool for removal of old files

[Ubuntu QA Website]

This bug has been reported on the Ubuntu ISO testing tracker.

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

** Tags added: iso-testing

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

Title:
  update-initramfs should produce a more helpful error message when
  there isn't enough  free space--or provide an automatic tool for
  removal of old files

Status in initramfs-tools package in Ubuntu:
  Won't Fix

Bug description:
  Binary package hint: initramfs-tools

  When installing a kernel, /boot may become full during execution of
  post-installation script typically when update-initramfs is creating
  or updating an initrd.img file. This is resulting in kernel
  installation error.  For example:

  Setting up initramfs-tools (0.98.8ubuntu3) ...
  update-initramfs: deferring update (trigger activated)
  Processing triggers for initramfs-tools ...
  update-initramfs: Generating /boot/initrd.img-2.6.38-8-generic

  gzip: stdout: No space left on device
  E: mkinitramfs failure cpio 141 gzip 1
  update-initramfs: failed for /boot/initrd.img-2.6.38-8-generic
  dpkg: error processing initramfs-tools (--configure):
   subprocess installed post-installation script returned error exit status 1

  Ideal behavior:

  Give a more helpful error message when this unfortunate situation
  occurs so that user can fix the broken system and keep it going.

  Workaround:

  As the bug reporting system forwards user to this bug report, such 
instructions can be given here:
  https://help.ubuntu.com/community/RemoveOldKernels

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/798414/+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 2035315] Re: Unprivileged user namespace restrictions break various applications

[Ubuntu QA Website]

This bug has been reported on the Ubuntu ISO testing tracker.

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

** Tags added: iso-testing

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

Title:
  Unprivileged user namespace restrictions break various applications

Status in apparmor package in Ubuntu:
  Fix Released
Status in lxc package in Ubuntu:
  Fix Released

Bug description:
  When the unprivileged user namespace restrictions are enabled, various
  applications within and outside the Ubuntu archive fail to function,
  as they use unprivileged user namespaces as part of their normal
  operation.

  A search of the Ubuntu archive for the 23.10 release was performed
  looking for all applications that make legitimate use of the
  CLONE_NEWUSER argument, the details of which can be seen in
  
https://docs.google.com/spreadsheets/d/1MOPVoTW0BROF1TxYqoWeJ3c6w2xKElI4w-VjdCG0m9s/edit#gid=2102562502

  For each package identified in that list, an investigation was made to
  determine if the application actually used this as an unprivileged
  user, and if so which of the binaries within the package were
  affected.

  The full investigation can be seen in
  https://warthogs.atlassian.net/browse/SEC-1898 (which is unfortunately
  private) but is summarised to the following list of Ubuntu source
  packages, with the affected binaries as noted. NOTE that due to time
  constraints for some packages it was not possible to finish the
  complete investigation and so for those *all* the binaries from the
  package are listed below.

  For each of these binaries, an apparmor profile is required so that
  the binary can be granted use of unprivileged user namespaces - an
  example profile for the ch-run binary within the charliecloud package
  is shown:

  $ cat /etc/apparmor.d/usr.bin.ch-run 
  abi ,

  include 

  /usr/bin/ch-run flags=(unconfined) {
userns,

# Site-specific additions and overrides. See local/README for details.
include if exists 
  }

  
  However, in a few select cases, it has been decided not to ship an apparmor 
profile, since this would effectively allow this mitigation to be bypassed. In 
particular, the unshare and setns binaries within the util-linux package are 
installed on every Ubuntu system, and allow an unprivileged user the ability to 
launch an arbitrary application within a new user namespace. Any malicious 
application then that wished to exploit an unprivileged user namespace to 
conduct an attack on the kernel would simply need to spawn itself via `unshare 
-U` or similar to be granted this permission. Therefore, due to the ubiquitous 
nature of the unshare (and setns) binaries, profiles are not planned to be 
provided for these by default. Similarly, the bwrap binary within bubblewrap is 
also installed by default on Ubuntu Desktop 23.10 and can also be used to 
launch arbitrary binaries within a new user namespace and so no profile is 
planned to be provided for this either.

  Those packages for which either a profile is not required or which a
  profile is not planned are listed below, whilst the list of packages
  that require a profile (and their associated binaries) is listed at
  the end:

  Packages that use user namespaces but for which a profile is not
  required or not planned:

- bubblewrap
  - /usr/bin/bwrap (NOT PLANNED AS NOTED ABOVE)
- cifs-utils
  - /usr/sbin/cifs.upcall (NOT REQUIRED AS IS EXECUTED AS root)
- consfigurator  # NOT REQUIRED, NO BINARIES OR reverse-depends
- criu
  - /usr/sbin/criu (NOT REQUIRED SINCE ONLY FUNCTIONS AS root)
- docker.io-app
  - /usr/bin/dockerd (NOT REQUIRED SINCE RUNS AS root)
- firejail
  - /usr/bin/firejail (NOT REQUIRED SINCE is suid root)
- golang-github-containers-storage
  - /usr/bin/containers-storage (NOT REQUIRED SINCE ONLY FUNCTIONS AS root)
- golang-gvisor-gvisor
  - /usr/bin/runsc (NOT REQUIRED SINCE ONLY FUNCTIONS AS root)
- guix
  - /usr/bin/guix-daemon (NOT REQURIED SINCE RUNS AS root)
- libvdestack # NOT REQUIRED, NO BINARIES OR reverse-depends
- libvirt # NOT REQUIRED SINCE USES lxc WHICH WILL HAVE A PROFILE
- network-manager # NOT REQUIRED SINCE CODE IS UNUSED
- nix # APPEARS UNNEEDED IN DEFAULT CONFIGURATION
- ocaml-extunix # NO BINARIES OR reverse-depends
- passt
  - /usr/bin/passt # IS EXPECTED TO BE EXECUTED AS root
- rust-rustix # NO BINARIES AND CODE IS UNUSED IN THE ARCHIVE
- util-linux
  - 
  Packages that use unprivileged user namespaces which require a profile (or 
already have one as part of the previous apparmor update in 
4.0.0~alpha2-0ubuntu1 via LP: #2030353):

- bazel-bootstrap
  - /usr/libexec/@{multiarch}/bazel/linux-sandbox
- busybox
  - /usr/bin/busybox
- 

[Touch-packages] [Bug 1547589] Re: rtkit-daemon flooding syslog

[Ubuntu QA Website]

This bug has been reported on the Ubuntu ISO testing tracker.

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

** Tags added: iso-testing

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

Title:
  rtkit-daemon flooding syslog

Status in Rtkit:
  New
Status in rtkit package in Ubuntu:
  Confirmed
Status in rtkit package in Debian:
  Confirmed

Bug description:
  rtkit is flooding syslog with the following:

  Feb 19 11:42:07 galactica rtkit-daemon[20798]: Supervising 0 threads of 0 
processes of 1 users.
  Feb 19 11:42:07 galactica rtkit-daemon[20798]: Warning: Reached burst limit 
for user '1000', denying request.
  Feb 19 11:42:07 galactica rtkit-daemon[20798]: Supervising 0 threads of 0 
processes of 1 users.
  Feb 19 11:42:07 galactica rtkit-daemon[20798]: Warning: Reached burst limit 
for user '1000', denying request.
  Feb 19 11:42:07 galactica rtkit-daemon[20798]: Supervising 0 threads of 0 
processes of 1 users.
  Feb 19 11:42:07 galactica rtkit-daemon[20798]: Warning: Reached burst limit 
for user '1000', denying request.
  Feb 19 11:42:07 galactica rtkit-daemon[20798]: Supervising 0 threads of 0 
processes of 1 users.
  Feb 19 11:42:07 galactica rtkit-daemon[20798]: Warning: Reached burst limit 
for user '1000', denying request.
  Feb 19 11:42:07 galactica rtkit-daemon[20798]: Supervising 0 threads of 0 
processes of 1 users.
  Feb 19 11:42:07 galactica rtkit-daemon[20798]: Warning: Reached burst limit 
for user '1000', denying request.
  Feb 19 11:42:07 galactica rtkit-daemon[20798]: Supervising 0 threads of 0 
processes of 1 users.
  Feb 19 11:42:07 galactica rtkit-daemon[20798]: Warning: Reached burst limit 
for user '1000', denying request.
  Feb 19 11:42:07 galactica rtkit-daemon[20798]: Supervising 0 threads of 0 
processes of 1 users.
  Feb 19 11:42:07 galactica rtkit-daemon[20798]: Warning: Reached burst limit 
for user '1000', denying request.
  Feb 19 11:42:07 galactica rtkit-daemon[20798]: Supervising 0 threads of 0 
processes of 1 users.
  Feb 19 11:42:07 galactica rtkit-daemon[20798]: Warning: Reached burst limit 
for user '1000', denying request.

  This may be related to but #1547585

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: rtkit 0.11-4
  ProcVersionSignature: Ubuntu 4.4.0-6.21-generic 4.4.1
  Uname: Linux 4.4.0-6-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Feb 19 11:42:58 2016
  InstallationDate: Installed on 2016-02-11 (7 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160210)
  SourcePackage: rtkit
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/rtkit/+bug/1547589/+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 2037874] Re: Totem black screen playing an webm video

[Ubuntu QA Website]

This bug has been reported on the Ubuntu ISO testing tracker.

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

** Tags added: iso-testing

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

Title:
  Totem black screen playing an webm video

Status in gstreamer1.0 package in Ubuntu:
  New

Bug description:
  Totem black screen playing an webm video. Video is payed ok by mpv.
  corrado@corrado-n02-mm-0923:~/Videos$ ffprobe -loglevel error -show_streams 
-show_format DSCF0001.webm 

  [STREAM]
  index=0
  codec_name=vp9
  codec_long_name=Google VP9
  profile=Profile 1
  codec_type=video
  codec_tag_string=[0][0][0][0]
  codec_tag=0x
  width=1280
  height=720
  coded_width=1280
  coded_height=720
  closed_captions=0
  film_grain=0
  has_b_frames=0
  sample_aspect_ratio=1:1
  display_aspect_ratio=16:9
  pix_fmt=yuv422p
  level=-99
  color_range=tv
  color_space=bt470bg
  color_transfer=unknown
  color_primaries=unknown
  chroma_location=center
  field_order=progressive
  refs=1
  id=N/A
  r_frame_rate=30/1
  avg_frame_rate=30/1
  time_base=1/1000
  start_pts=0
  start_time=0.00
  duration_ts=N/A
  duration=N/A
  bit_rate=N/A
  max_bit_rate=N/A
  bits_per_raw_sample=N/A
  nb_frames=N/A
  nb_read_frames=N/A
  nb_read_packets=N/A
  DISPOSITION:default=0
  DISPOSITION:dub=0
  DISPOSITION:original=0
  DISPOSITION:comment=0
  DISPOSITION:lyrics=0
  DISPOSITION:karaoke=0
  DISPOSITION:forced=0
  DISPOSITION:hearing_impaired=0
  DISPOSITION:visual_impaired=0
  DISPOSITION:clean_effects=0
  DISPOSITION:attached_pic=0
  DISPOSITION:timed_thumbnails=0
  DISPOSITION:captions=0
  DISPOSITION:descriptions=0
  DISPOSITION:metadata=0
  DISPOSITION:dependent=0
  DISPOSITION:still_image=0
  TAG:ENCODER=Lavc60.3.100 libvpx-vp9
  TAG:DURATION=00:00:15.0
  [/STREAM]
  [STREAM]
  index=1
  codec_name=opus
  codec_long_name=Opus (Opus Interactive Audio Codec)
  profile=unknown
  codec_type=audio
  codec_tag_string=[0][0][0][0]
  codec_tag=0x
  sample_fmt=fltp
  sample_rate=48000
  channels=1
  channel_layout=mono
  bits_per_sample=0
  initial_padding=312
  id=N/A
  r_frame_rate=0/0
  avg_frame_rate=0/0
  time_base=1/1000
  start_pts=-7
  start_time=-0.007000
  duration_ts=N/A
  duration=N/A
  bit_rate=N/A
  max_bit_rate=N/A
  bits_per_raw_sample=N/A
  nb_frames=N/A
  nb_read_frames=N/A
  nb_read_packets=N/A
  extradata_size=19
  DISPOSITION:default=0
  DISPOSITION:dub=0
  DISPOSITION:original=0
  DISPOSITION:comment=0
  DISPOSITION:lyrics=0
  DISPOSITION:karaoke=0
  DISPOSITION:forced=0
  DISPOSITION:hearing_impaired=0
  DISPOSITION:visual_impaired=0
  DISPOSITION:clean_effects=0
  DISPOSITION:attached_pic=0
  DISPOSITION:timed_thumbnails=0
  DISPOSITION:captions=0
  DISPOSITION:descriptions=0
  DISPOSITION:metadata=0
  DISPOSITION:dependent=0
  DISPOSITION:still_image=0
  TAG:ENCODER=Lavc60.3.100 libopus
  TAG:DURATION=00:00:15.00800
  [/STREAM]
  [FORMAT]
  filename=DSCF0001.webm
  nb_streams=2
  nb_programs=0
  format_name=matroska,webm
  format_long_name=Matroska / WebM
  start_time=-0.007000
  duration=15.008000
  size=6005941
  bit_rate=3201461
  probe_score=100
  TAG:ENCODER=Lavf60.3.100
  [/FORMAT]
  corrado@corrado-n02-mm-0923:~/Videos$ totem DSCF0001.webm

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: libgstreamer1.0-0 1.22.5-1
  ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0
  Uname: Linux 6.5.0-5-generic x86_64
  ApportVersion: 2.27.0-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct  1 09:39:34 2023
  ExecutablePath: /usr/bin/totem
  InstallationDate: Installed on 2023-09-23 (8 days ago)
  InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Beta amd64 (20230923)
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  SourcePackage: gstreamer1.0
  UpgradeStatus: No upgrade log present (probably fresh install)
  XorgLog: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log'

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/2037874/+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 2039107] Re: package linux-image-6.5.0-9-generic 6.5.0-9.9 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1

[Ubuntu QA Website]

This bug has been reported on the Ubuntu ISO testing tracker.

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

** Tags added: iso-testing

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

Title:
  package linux-image-6.5.0-9-generic 6.5.0-9.9 failed to
  install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools
  exited with return code 1

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  This failure occurred during a test upgrade from a clean install of
  Edubuntu 23.04 to 23.10.

  ProblemType: Package
  DistroRelease: Ubuntu 23.10
  Package: linux-image-6.5.0-9-generic 6.5.0-9.9
  ProcVersionSignature: Ubuntu 6.2.0-34.34-generic 6.2.16
  Uname: Linux 6.2.0-34-generic x86_64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  erich  1313 F wireplumber
   /dev/snd/seq:erich  1310 F pipewire
  CRDA: N/A
  CasperMD5CheckResult: pass
  Date: Wed Oct 11 14:17:46 2023
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  InstallationDate: Installed on 2023-10-11 (0 days ago)
  InstallationMedia: Edubuntu 23.04 "Lunar Lobster" - Release amd64 (20230417)
  IwConfig:
   lono wireless extensions.
   
   enp0s3no wireless extensions.
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Lsusb-t:
   /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 5000M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/8p, 480M
   |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcFB: 0 vmwgfxdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-34-generic 
root=UUID=84103c76-ebaa-4a1f-8ca9-ca298dacd756 ro quiet splash vt.handoff=7
  Python3Details: /usr/bin/python3.11, Python 3.11.6, python3-minimal, 3.11.4-5
  PythonDetails: N/A
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions: grub-pc 2.12~rc1-10ubuntu4
  RfKill:
   
  SourcePackage: initramfs-tools
  Title: package linux-image-6.5.0-9-generic 6.5.0-9.9 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  UpgradeStatus: Upgraded to mantic on 2023-10-11 (0 days ago)
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:sku:
  dmi.product.family: Virtual Machine
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH

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

[Ubuntu QA Website]

This bug has been reported on the Ubuntu ISO testing tracker.

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

** Tags added: iso-testing

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

Title:
  some text became unreadable during a distribution upgrade

Status in Ubuntu MATE:
  New
Status in ubuntu-meta package in Ubuntu:
  Fix Released
Status in ubuntu-release-upgrader package in Ubuntu:
  In Progress
Status in ubuntu-meta source package in Mantic:
  Fix Released
Status in ubuntu-release-upgrader source package in Mantic:
  In Progress

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

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-mate/+bug/2034986/+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 2038964] Re: raspi ethernet rename is racy

[Ubuntu QA Website]

This bug has been reported on the Ubuntu ISO testing tracker.

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

** Tags added: iso-testing

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

Title:
  raspi ethernet rename is racy

Status in ubuntu-settings package in Ubuntu:
  New

Bug description:
  The renaming of the ethernet interface (controlled by 10-raspi-
  eth0.link in ubuntu-raspi-settings) turns out to be racy.
  Specifically, in the final mantic server images (but not the desktop
  images), under armhf or arm64, on the Raspberry Pi 3B+ (but not any
  other supported board, including the 3B), the interface renames
  several times during boot. By the end, the interface is left in the
  enxMACMACMAC state and the netplan configuration fails to apply.

  Will attach kern.log from an affected platform, and another from an
  unaffected platform.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/2038964/+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 2038857] Re: Mantic Daily Text Editor Crashed Xorg

[Ubuntu QA Website]

This bug has been reported on the Ubuntu ISO testing tracker.

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

** Tags added: iso-testing

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

Title:
  Mantic Daily Text Editor Crashed Xorg

Status in xorg package in Ubuntu:
  New

Bug description:
  In testing Mantic Daily ISO. Dl'ed today and updated to current git in
  installer. After selecting "Erase All and Install Ubuntu: Experimental
  ZFS > Next... Jumped out to system and started gnome-terminal.

  Created file of all modified files within the last 5 minutes. Opened
  Text Editor > Open... Text editor could not see any recent files and
  had no way to navigate to folders... Selected menu in top bar of
  editor... Scree when blank, then to lock-screen.

  On getting back through lockscreen, ubuntu-desktop-installer
  restarted. Went to "try". apport said that Xorg had crashed.

  On choosing report bug, apport crashed. Submitted report via 'ubuntu-
  bug'.

  Here we are.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0
  Uname: Linux 6.5.0-5-generic x86_64
  NonfreeKernelModules: zfs
  ApportVersion: 2.27.0-0ubuntu4
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CasperVersion: 1.486
  CloudArchitecture: x86_64
  CloudID: nocloud
  CloudName: unknown
  CloudPlatform: nocloud
  CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud)
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct  9 17:58:20 2023
  DistUpgraded: Fresh install
  DistroCodename: mantic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Red Hat, Inc. QXL paravirtual graphic card [1b36:0100] (rev 05) (prog-if 00 
[VGA controller])
 Subsystem: Red Hat, Inc. QEMU Virtual Machine [1af4:1100]
  LiveMediaBuild: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20231004)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Lsusb-t:
   /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/15p, 5000M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/15p, 480M
   |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 
480M
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz 
layerfs-path=minimal.standard.live.squashfs --- quiet splash
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/06/2015
  dmi.bios.release: 0.0
  dmi.bios.vendor: EFI Development Kit II / OVMF
  dmi.bios.version: 0.0.0
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-q35-6.2
  dmi.modalias: 
dmi:bvnEFIDevelopmentKitII/OVMF:bvr0.0.0:bd02/06/2015:br0.0:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-6.2:cvnQEMU:ct1:cvrpc-q35-6.2:sku:
  dmi.product.name: Standard PC (Q35 + ICH9, 2009)
  dmi.product.version: pc-q35-6.2
  dmi.sys.vendor: QEMU
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.115-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu2
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
  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/xorg/+bug/2038857/+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 2037210] Re: unable to add PPA by its sources.list line

[Ubuntu QA Website]

This bug has been reported on the Ubuntu ISO testing tracker.

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

** Tags added: iso-testing

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

Title:
  unable to add PPA by its sources.list line

Status in Software Properties:
  Confirmed
Status in software-properties package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce:
  1. Have Ubuntu 23.10 installed
  2. Run 

  ```
  sudo apt-key adv --keyserver keyserver.ubuntu.com --recv 
E756285F30DB2B2BB35012E219BFCAF5168D33A9
  sudo add-apt-repository -y "deb http://ppa.launchpad.net/nrbrtx/vte/ubuntu 
jammy main"
  sudo add-apt-repository -y "deb http://ppa.launchpad.net/nrbrtx/wnck/ubuntu 
jammy main"
  ```

  Expected results:

  * key added, two repositories are added to the relevant *.list files
  at /etc/apt/sources.list.d/

  Actual results:

  * relevant *.list files at /etc/apt/sources.list.d/ are not created,
  having errors instead

  ```
  $ sudo add-apt-repository -y "deb http://ppa.launchpad.net/nrbrtx/vte/ubuntu 
jammy main"
  Repository: 'deb http: //ppa.launchpad.net/nrbrtx/vte/ubuntu jammy main
  Components: 
  '
  Description:
  This PPA contains VTE library from Ubuntu 20.04 LTS which is not affected by 
stupid bug https://pad.lv/1922276 . So user will be able to select all terminal 
output with full scroll-back in MATE Terminal and other VTE-based terminals as 
it is expected.

  This PPA is useful for Ubuntu 22.04 LTS, Debian 11 (bullseye) and
  Debian 12 (bookworm).

  As usual one can always remove this PPA and downgrade VTE packages by using 
`sudo apt-get install ppa-purge` and `sudo ppa-purge ppa:nrbrtx/vte`.
  More info: https://launchpad.net/~nrbrtx/+archive/ubuntu/vte
  Adding repository.
  E: Malformed entry 1 in sources file 
/etc/apt/sources.list.d/nrbrtx-ubuntu-vte-mantic.sources (URI)
  E: The list of sources could not be read.

  $ sudo add-apt-repository -y "deb http://ppa.launchpad.net/nrbrtx/wnck/ubuntu 
jammy main"
  Repository: 'deb http: //ppa.launchpad.net/nrbrtx/wnck/ubuntu jammy main
  Components: 
  '
  Description:
  This PPA provides patched libwnck3 package to fix  
https://github.com/mate-desktop/mate-panel/issues/1230 and 
https://pad.lv/1947420 .
  See details at 
https://github.com/mate-desktop/mate-panel/issues/1230#issuecomment-997422612 .

  This PPA is useful for Ubuntu 22.04 LTS and Debian 12 (bookworm).

  As usual one can always remove this PPA and downgrade WNCK packages by using 
`sudo apt-get install ppa-purge` and `sudo ppa-purge ppa:nrbrtx/wnck`.
  More info: https://launchpad.net/~nrbrtx/+archive/ubuntu/wnck
  Adding repository.
  Found existing deb entry in 
/etc/apt/sources.list.d/nrbrtx-ubuntu-vte-mantic.sources
  E: Malformed entry 1 in sources file 
/etc/apt/sources.list.d/nrbrtx-ubuntu-vte-mantic.sources (URI)
  E: The list of sources could not be read.

  $ sudo apt-get update 
  E: Malformed entry 1 in sources file 
/etc/apt/sources.list.d/nrbrtx-ubuntu-vte-mantic.sources (URI)
  E: The list of sources could not be read.
  ```

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: software-properties-common 0.99.39
  ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0
  Uname: Linux 6.5.0-5-generic x86_64
  ApportVersion: 2.27.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: GNOME-Flashback
  Date: Sun Sep 24 14:02:10 2023
  PackageArchitecture: all
  SourcePackage: software-properties
  UpgradeStatus: Upgraded to mantic on 2023-04-13 (164 days ago)
  modified.conffile..etc.default.apport:
   # set this to 0 to disable apport, or to 1 to enable it
   # you can temporarily override this with
   # sudo service apport start force_start=1
   enabled=0
  mtime.conffile..etc.default.apport: 2023-09-24T13:25:34.901411

To manage notifications about this bug go to:
https://bugs.launchpad.net/software-properties/+bug/2037210/+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 sources in deb822 format

[Ubuntu QA Website]

This bug has been reported on the Ubuntu ISO testing tracker.

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

** Tags added: iso-testing

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

Title:
  Does not work with sources in deb822 format

Status in software-properties package in Ubuntu:
  Confirmed

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/software-properties/+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 2033262] Re: Ubuntu mantic live session (desktop)_& `apt install` ends with "Error: Timeout was reached"

[Ubuntu QA Website]

This bug has been reported on the Ubuntu ISO testing tracker.

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

** Tags added: iso-testing

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

Title:
  Ubuntu mantic live session (desktop)_& `apt install` ends with "Error:
  Timeout was reached"

Status in apt package in Ubuntu:
  New

Bug description:
  Running a Ubuntu Desktop mantic live session on
  - dell [optiplex] 780 (c2q-q9400, 8gb, amd/ati cedar radeon hd 
5000/6000/7350/8350)

  ** steps to create

  - boot & ubuntu mantic daily; select 'TRY'
  - wait for boot to complete
  - open terminal (ctrl+alt+t)
  - sudo apt update
  - sudo apt install vlc

  ** expected results

  package & requirements install

  ** actual result

  Setting up libheif-plugin-aomenc:amd64 (1.16.2-2ubuntu1) ...
  Processing triggers for libc-bin (2.38-1ubuntu3) ...
  Processing triggers for man-db (2.11.2-3) ...
  Error: Timeout was reached

  ** comments

  this was repeated twice, same result.

  PROBLEM MAYBE ONLY FINAL ERROR MESSAGE SHOWN on terminal, ie. ending
  with "Error: Timeout was reached" as I can use the packages that I
  installed.. though my running `apt install -f` was because of the
  final error message

  also occurred with `sudo apt install gstreamer1.0-plugins-bad`

  ** actual paste of terminal  (top redacted)

  rocessing triggers for libc-bin (2.38-1ubuntu3) ...
  Processing triggers for man-db (2.11.2-3) ...
  Error: Timeout was reached
  ubuntu@ubuntu:~$   sudo apt -f install
  Reading package lists... Done
  Building dependency tree... Done
  Reading state information... Done
  0 upgraded, 0 newly installed, 0 to remove and 195 not upgraded.
  ubuntu@ubuntu:~$ sudo apt install vlc
  Reading package lists... Done
  Building dependency tree... Done
  Reading state information... Done
  The following additional packages will be installed:
    fonts-freefont-ttf liba52-0.7.4 libaacs0 libaribb24-0 libavformat60 
libbdplus0 libbluray2 libcddb2 libcjson1
    libdouble-conversion3 libdvbpsi10 libebml5 libgnutls30 libixml11 
liblirc-client0 liblua5.2-0 libmad0 libmatroska7
    libmbedcrypto7 libmd4c0 libmpeg2-4 libmysofa1 libnorm1 libopenmpt-modplug1 
libp11-kit0 libpcre2-16-0 libpcre2-32-0
    libpcre2-8-0 libpgm-5.3-0 libpostproc57 libprotobuf-lite32 libproxy-tools 
libqt5core5a libqt5dbus5 libqt5gui5
    libqt5network5 libqt5qml5 libqt5qmlmodels5 libqt5quick5 libqt5svg5 
libqt5waylandclient5 libqt5waylandcompositor5
    libqt5widgets5 libqt5x11extras5 librabbitmq4 libresid-builder0c2a librist4 
libsidplay2 libspatialaudio0
    libspeexdsp1 libssh-gcrypt-4 libssh2-1 libswscale7 libudfread0 libupnp17 
libva-wayland2 libvlc-bin libvlc5
    libvlccore9 libvncclient1 libxcb-composite0 libxcb-xinerama0 libxcb-xinput0 
libzmq5 p11-kit p11-kit-modules
    qt5-gtk-platformtheme qttranslations5-l10n qtwayland5 vlc-bin vlc-data 
vlc-l10n vlc-plugin-access-extra
    vlc-plugin-base vlc-plugin-notify vlc-plugin-qt vlc-plugin-samba 
vlc-plugin-skins2 vlc-plugin-video-output
    vlc-plugin-video-splitter vlc-plugin-visualization
  Suggested packages:
    libbluray-bdj gnutls-bin lirc qgnomeplatform-qt5 qt5-image-formats-plugins 
qt5-qmltooling-plugins
    vlc-plugin-fluidsynth vlc-plugin-jack vlc-plugin-pipewire vlc-plugin-svg 
libdvdcss2
  The following NEW packages will be installed:
    fonts-freefont-ttf liba52-0.7.4 libaacs0 libaribb24-0 libavformat60 
libbdplus0 libbluray2 libcddb2 libcjson1
    libdouble-conversion3 libdvbpsi10 libebml5 libixml11 liblirc-client0 
liblua5.2-0 libmad0 libmatroska7
    libmbedcrypto7 libmd4c0 libmpeg2-4 libmysofa1 libnorm1 libopenmpt-modplug1 
libpcre2-16-0 libpgm-5.3-0 libpostproc57
    libprotobuf-lite32 libproxy-tools libqt5core5a libqt5dbus5 libqt5gui5 
libqt5network5 libqt5qml5 libqt5qmlmodels5
    libqt5quick5 libqt5svg5 libqt5waylandclient5 libqt5waylandcompositor5 
libqt5widgets5 libqt5x11extras5 librabbitmq4
    libresid-builder0c2a librist4 libsidplay2 libspatialaudio0 libspeexdsp1 
libssh-gcrypt-4 libssh2-1 libswscale7
    libudfread0 libupnp17 libva-wayland2 libvlc-bin libvlc5 libvlccore9 
libvncclient1 libxcb-composite0
    libxcb-xinerama0 libxcb-xinput0 libzmq5 qt5-gtk-platformtheme 
qttranslations5-l10n qtwayland5 vlc vlc-bin vlc-data
    vlc-l10n vlc-plugin-access-extra vlc-plugin-base vlc-plugin-notify 
vlc-plugin-qt vlc-plugin-samba vlc-plugin-skins2
    vlc-plugin-video-output vlc-plugin-video-splitter vlc-plugin-visualization
  The following packages will be upgraded:
    libgnutls30 libp11-kit0 libpcre2-32-0 libpcre2-8-0 p11-kit p11-kit-modules
  6 upgraded, 76 newly installed, 0 to remove and 189 not upgraded.
  Need to get 0 B/41.9 MB of archives.
  After this operation, 158 MB of additional disk space will be used.
  Do you want to continue? [Y/n] y
  Extracting 

[Touch-packages] [Bug 2028454] Re: apt-config crashed with SIGSEGV in _int_malloc()

[Ubuntu QA Website]

This bug has been reported on the Ubuntu ISO testing tracker.

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

** Tags added: iso-testing

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

Title:
  apt-config crashed with SIGSEGV in _int_malloc()

Status in apt package in Ubuntu:
  Incomplete

Bug description:
  ProblemType: Crash
  DistroRelease: Ubuntu 23.10
  Package: apt 2.7.2
  ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5
  Uname: Linux 6.3.0-7-generic x86_64
  NonfreeKernelModules: zfs
  ApportVersion: 2.26.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckMismatches: ./casper/minimal.fr.squashfs
  CasperMD5CheckResult: fail
  CasperVersion: 1.481
  Date: Sun Jul 23 09:14:39 2023
  ExecutablePath: /usr/bin/apt-config
  JournalErrors:
   Jul 23 09:14:31 hostname kernel: overlayfs: fs on 
'/tmp/tmpc4daggpg/root.dir' does not support file handles, falling back to 
xino=off.
   Jul 23 09:14:35 hostname kernel: overlayfs: fs on 
'/tmp/tmpkuua06i6/root.dir' does not support file handles, falling back to 
xino=off.
   Jul 23 09:14:37 hostname kernel: overlayfs: fs on 
'/tmp/tmpkuua06i6/root.dir' does not support file handles, falling back to 
xino=off.
   Jul 23 09:14:37 hostname kernel: overlayfs: lowerdir is in-use as 
upperdir/workdir of another mount, accessing files from both mounts will result 
in undefined behavior.
   Jul 23 09:14:40 hostname pipewire[1573]: spa.alsa: front:0: (0 missed) 
impossible htimestamp diff:-8420
  LiveMediaBuild: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230723)
  ProcCmdline: apt-config shell TRUSTEDPARTS Dir::Etc::TrustedParts/d
  ProcEnviron:
   LANG=
   LC_MESSAGES=
   PATH=(custom, no user)
   SHELL=/bin/sh
  SegvAnalysis:
   Segfault happened at: 0x7fd06012f111 <_int_malloc+737>:  cmp
0x10(%r8),%rdx
   PC (0x7fd06012f111) ok
   source "0x10(%r8)" (0x69efc653158d0b5d) not located in a known VMA region 
(needed readable region)!
   destination "%rdx" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: apt
  StacktraceTop:
   _int_malloc (av=av@entry=0x7fd060287c80 , bytes=bytes@entry=472) 
at ./malloc/malloc.c:3994
   __GI___libc_malloc (bytes=bytes@entry=472) at ./malloc/malloc.c:3297
   __fopen_internal (is32=1, mode=0x7fd0604878c3 "r", filename=0x5579117a9860 
"/usr/share/dpkg/tupletable") at ./libio/iofopen.c:65
   _IO_new_fopen (filename=0x5579117a9860 "/usr/share/dpkg/tupletable", 
mode=0x7fd0604878c3 "r") at ./libio/iofopen.c:86
   std::__basic_file::open(char const*, std::_Ios_Openmode, int) () from 
/lib/x86_64-linux-gnu/libstdc++.so.6
  Title: apt-config crashed with SIGSEGV in _int_malloc()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/2028454/+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 2027987] Re: Ubuntu mate mantic 23.10 failed to completely reboot into installed OS

[Ubuntu QA Website]

This bug has been reported on the Ubuntu ISO testing tracker.

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

** Tags added: iso-testing

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

Title:
  Ubuntu mate mantic 23.10 failed to completely reboot into installed OS

Status in systemd package in Ubuntu:
  New

Bug description:
  QA Testing Build 20230717

  Ubuntu mate mantic 23.10 failed to completely reboot into installed OS
  Systemd crashed OS failed to completely reboot into installed OS.
  Had to manually shutdown/restart virtual box to make bug report.
  Installer worked fine until the reboot.
  The remove media to reboot came on/ hit enter/Crashed..No reboot.
  Reproduced 2 times..same result.
  What should of happened- click remove media to reboot. Reboot into installed 
OS.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: systemd 252.5-2ubuntu3
  ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5
  Uname: Linux 6.3.0-7-generic x86_64
  ApportVersion: 2.26.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: MATE
  Date: Mon Jul 17 08:45:10 2023
  InstallationDate: Installed on 2023-07-17 (0 days ago)
  InstallationMedia: Ubuntu-MATE 23.10 "Mantic Minotaur" - Daily amd64 
(20230717)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet
   Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Lsusb-t:
   /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/12p, 480M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ohci-pci/12p, 12M
   |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M
  MachineType: innotek GmbH VirtualBox
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.3.0-7-generic 
root=UUID=c396954f-1b91-404e-ad9d-599038ddfcf8 ro quiet splash
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:sku:
  dmi.product.family: Virtual Machine
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2027987/+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 2027707] Re: Edubuntu Manic 23.10 crashed on shutdown

[Ubuntu QA Website]

This bug has been reported on the Ubuntu ISO testing tracker.

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

** Tags added: iso-testing

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

Title:
  Edubuntu Manic 23.10 crashed on shutdown

Status in systemd package in Ubuntu:
  New

Bug description:
  Edubuntu Manic 23.10 bootloader crashed
  Finished the install, remove the disc and press enter.
  Crash no reboot.
  Physically shutdown the VM and started it to make this bug report.
  Daily build 20230713
  QA Testing using Virtual Box

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: grub2 (not installed)
  ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5
  Uname: Linux 6.3.0-7-generic x86_64
  ApportVersion: 2.26.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jul 13 09:22:20 2023
  InstallationDate: Installed on 2023-07-13 (0 days ago)
  InstallationMedia: Edubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230713)
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  SourcePackage: grub2
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2027707/+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 2017090] Re: [raspi] glmark2-wayland --fullscreen stutters visually while reporting hundreds of FPS

[Ubuntu QA Website]

This bug has been reported on the Ubuntu ISO testing tracker.

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

** Tags added: iso-testing

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

Title:
  [raspi] glmark2-wayland --fullscreen stutters visually while reporting
  hundreds of FPS

Status in glmark2 package in Ubuntu:
  New
Status in mesa package in Ubuntu:
  New
Status in mutter package in Ubuntu:
  New

Bug description:
  glmark2-wayland --fullscreen stutters visually while reporting
  hundreds of FPS in the terminal.

  Doesn't seem to happen in windowed mode.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: glmark2-wayland 2021.02-0ubuntu1
  ProcVersionSignature: Ubuntu 6.2.0-1004.5-raspi 6.2.6
  Uname: Linux 6.2.0-1004-raspi aarch64
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: arm64
  CasperMD5CheckResult: unknown
  Date: Thu Apr 20 15:10:16 2023
  ImageMediaBuild: 20230417
  SourcePackage: glmark2
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glmark2/+bug/2017090/+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 2017076] Re: default Chinese font is ugly

[Ubuntu QA Website]

This bug has been reported on the Ubuntu ISO testing tracker.

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

** Tags added: iso-testing

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

Title:
  default Chinese font is ugly

Status in fontconfig package in Ubuntu:
  New

Bug description:
  After installs Ubuntu 23.04 with Chinese language selected, the
  default font is chosen to AR PL UMing CN, which is very ugly.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: fontconfig 2.14.1-3ubuntu3
  ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
  Uname: Linux 6.2.0-20-generic x86_64
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CloudArchitecture: x86_64
  CloudID: none
  CloudName: none
  CloudPlatform: none
  CloudSubPlatform: config
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr 20 14:18:45 2023
  InstallationDate: Installed on 2023-04-20 (0 days ago)
  InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418)
  ProcEnviron:
   LANG=zh_CN.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  SourcePackage: fontconfig
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/2017076/+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 1951586] Re: Need option to specify wifi regulatory domain

[Ubuntu QA Website]

This bug has been reported on the Ubuntu ISO testing tracker.

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

** Tags added: iso-testing

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

Title:
  Need option to specify wifi regulatory domain

Status in cloud-init:
  Invalid
Status in netplan:
  Fix Released
Status in NetworkManager:
  New
Status in netplan.io package in Ubuntu:
  Fix Released
Status in network-manager package in Ubuntu:
  Incomplete
Status in netplan.io source package in Jammy:
  Triaged
Status in network-manager source package in Jammy:
  Incomplete
Status in netplan.io source package in Kinetic:
  Fix Released
Status in network-manager source package in Kinetic:
  Incomplete

Bug description:
  It would be nice if netplan offered an option to specify the wifi
  regulatory domain (country code).

  
  For devices such as the Raspberry Pi you are currently advertising that users 
can simply setup Ubuntu Server headless by putting the wifi configuration 
details in cloudinit/netplan's "network-config" on the FAT partition of the SD 
card: 
https://ubuntu.com/tutorials/how-to-install-ubuntu-on-your-raspberry-pi#3-wifi-or-ethernet
  But an option to set the wifi country code there does not seem to exist, so 
may not work.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1951586/+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 2012879] Re: indicator-messages-service crashed with SIGSEGV in ACT_IS_USER() from _act_user_update_from_object_path() from fetch_user_incrementally() from on_find_user_by_name_f

[Ubuntu QA Website]

This bug has been reported on the Ubuntu ISO testing tracker.

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

** Tags added: iso-testing

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

Title:
  indicator-messages-service crashed with SIGSEGV in ACT_IS_USER() from
  _act_user_update_from_object_path() from fetch_user_incrementally()
  from on_find_user_by_name_finished() from g_task_return_now()

Status in accountsservice package in Ubuntu:
  Confirmed

Bug description:
  https://errors.ubuntu.com/problem/2416b63fd3efcd8ec09f184b6f50981fc56fb16d

  Crash in indicator-messages-service

  ProblemType: Crash
  DistroRelease: Ubuntu 23.04
  Package: indicator-messages 13.10.1+18.10.20180918-0ubuntu3
  Uname: Linux 6.2.0-18-generic x86_64
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Mar 27 14:25:09 2023
  ExecutablePath: 
/usr/lib/x86_64-linux-gnu/indicator-messages/indicator-messages-service
  ExecutableTimestamp: 1633601577
  ProcCmdline: 
/usr/lib/x86_64-linux-gnu/indicator-messages/indicator-messages-service
  ProcCwd: /home/dan
  ProcEnviron:
   LANG=en_AU.UTF-8
   LANGUAGE=en_AU:en
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  Signal: 11
  SourcePackage: indicator-messages
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/2012879/+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 2013071] Re: Session crash after initial login

[Ubuntu QA Website]

This bug has been reported on the Ubuntu ISO testing tracker.

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

** Tags added: iso-testing

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

Title:
  Session crash after initial login

Status in xorg package in Ubuntu:
  New

Bug description:
  Xubuntu lunar beta 20230328, GNOME Boxes 43.2, "Install third-party
  software for graphics and Wi-Fi hardware and additional media formats"
  selected during install.

  When logging in for the first time, the session immediately crashes
  and returns to the login screen.

  Attempting to login again without rebooting is successful.
  Attempting to login again after rebooting reproduces the issue.

  The issue doesn't seem to present itself if "Install third-party software for 
graphics and Wi-Fi hardware and additional media formats" is not selected 
during install. Differences in installed packages:
  - chromium-codecs-ffmpeg-extra
  - gimp-help-common
  - gimp-help-en
  - gstreamer1.0-plugins-ugly
  - gstreamer1.0-vaapi
  - hyphen-en-us
  - liba52-0.7.4
  - libmpeg2-4
  - libopencore-amrnb0
  - libopencore-amrwb0
  - libreoffice-help-common
  - libreoffice-help-en-us
  - libsidplay1v5
  - libva-wayland2
  - mythes-en-us
  - thunderbird-locale-en
  - thunderbird-locale-en-us
  - ubuntu-restricted-addons
  - wbritish

  Since it seems unlikely that the language pack packages are
  interfering... maybe libva-wayland2 is to blame?

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.2.0-18.18-generic 6.2.6
  Uname: Linux 6.2.0-18-generic x86_64
  ApportVersion: 2.26.0-0ubuntu2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Tue Mar 28 07:47:04 2023
  DistUpgraded: Fresh install
  DistroCodename: lunar
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Red Hat, Inc. QXL paravirtual graphic card [1b36:0100] (rev 05) (prog-if 00 
[VGA controller])
     Subsystem: Red Hat, Inc. QEMU Virtual Machine [1af4:1100]
  InstallationDate: Installed on 2023-03-28 (0 days ago)
  InstallationMedia: Xubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20230328)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet
   Bus 001 Device 002: ID 08e6:4433 Gemalto (was Gemplus) GemPC433-Swap
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Lsusb-t:
   /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/15p, 5000M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/15p, 480M
   |__ Port 1: Dev 2, If 0, Class=Chip/SmartCard, Driver=, 12M
   |__ Port 2: Dev 3, If 0, Class=Human Interface Device, Driver=usbhid, 
480M
  MachineType: QEMU Standard PC (Q35 + ICH9, 2009)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-18-generic 
root=UUID=0a9a1a3f-22b7-4cef-b7d4-a193beb89089 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/01/2014
  dmi.bios.release: 0.0
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: 1.16.1-2.fc37
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-q35-7.0
  dmi.modalias: 
dmi:bvnSeaBIOS:bvr1.16.1-2.fc37:bd04/01/2014:br0.0:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-7.0:cvnQEMU:ct1:cvrpc-q35-7.0:sku:
  dmi.product.name: Standard PC (Q35 + ICH9, 2009)
  dmi.product.version: pc-q35-7.0
  dmi.sys.vendor: QEMU
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.114-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.3.6-1ubuntu2
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
  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/xorg/+bug/2013071/+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 2012623] Re: Edubuntu 23.04 apparmor package crashed

[Ubuntu QA Website]

This bug has been reported on the Ubuntu ISO testing tracker.

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

** Tags added: iso-testing

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

Title:
  Edubuntu 23.04 apparmor package crashed

Status in apparmor package in Ubuntu:
  New

Bug description:
  Edubuntu 23.04 apparmor package crashed during QA Testing Build 20230323.
  In addition to the crash the mouse pointer/spinner during the
  install did not spin it was stationary.
  Install completed as expected except for the package crash.
  apparmor:
    Installed: 3.0.8-1ubuntu2
    Candidate: 3.0.8-1ubuntu2
    Version table:
   *** 3.0.8-1ubuntu2 500
  500 http://us.archive.ubuntu.com/ubuntu lunar/main amd64 Packages
  100 /var/lib/dpkg/status
  No LSB modules are available.
  Description:  Ubuntu Lunar Lobster (development branch)
  Release:  23.04

  ProblemType: Crash
  DistroRelease: Ubuntu 23.04
  Package: apparmor 3.0.8-1ubuntu2
  Uname: Linux 6.2.0-18-generic x86_64
  Architecture: amd64
  Date: Thu Mar 23 07:18:57 2023
  ExecutablePath: /usr/sbin/apparmor_parser
  ExecutableTimestamp: 1677622692
  ProcCmdline: apparmor_parser --replace --write-cache -O no-expr-simplify 
--cache-loc=/var/cache/apparmor -j2 --skip-read-cache --quiet 
/var/lib/snapd/apparmor/profiles/snap-update-ns.firefox 
/var/lib/snapd/apparmor/profiles/snap.firefox.firefox 
/var/lib/snapd/apparmor/profiles/snap.firefox.geckodriver 
/var/lib/snapd/apparmor/profiles/snap.firefox.hook.configure 
/var/lib/snapd/apparmor/profiles/snap.firefox.hook.connect-plug-host-hunspell 
/var/lib/snapd/apparmor/profiles/snap.firefox.hook.disconnect-plug-host-hunspell
 /var/lib/snapd/apparmor/profiles/snap.firefox.hook.post-refresh
  ProcCwd: /
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
  Signal: 6
  SourcePackage: apparmor
  UserGroups: N/A

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2012623/+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 2011751] Re: openbox crashed with SIGABRT

[Ubuntu QA Website]

This bug has been reported on the Ubuntu ISO testing tracker.

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

** Tags added: iso-testing

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

Title:
  openbox crashed with SIGABRT

Status in glib2.0 package in Ubuntu:
  Confirmed
Status in openbox package in Ubuntu:
  Confirmed

Bug description:
  Lubuntu lunar (primary box) on
  - dell [optiplex] 7050 (i5-6500, 16gb, intel hd530/i915)

  I experienced a crash yesterday (openbox) but tend to ignore the first
  crashes... Whilst using the machine again today a crash occurred.

  This is my primary box, so my setup is pretty consistent

  - featherpad (restored session)
  - hexchat (irc)
  - qterminal (only single tab today; usually many)
  - firefox (snap, most sites excluding google related)
  - chromium (snap, used for anything google related)
  - telegram (snap)
  - element

  I was using chromium full screen (trying to read my gmail inbox) when
  borders around windows disappeared & I lost the capacity to switch
  between windows; mouse would move, but keyboard appeared mostly dead
  (it wasn't, more I think windows weren't responding, inc. clicks with
  mouse though that's likely inconsistent; I could work out how to
  describe it yesterday, but todays is almost identical).

  I switched to text terminal (ctrl+alt+f4) & explored; returned to GUI and used
  - ctrl+alt+t to open new terminal
  - openbox &

  session returned to what I expect...

  ** expected outcome

  Openbox doesn't crash

  ** actual outcome

  all windows lost borders, and i lost ability to switch between windows
  I appeared to have minimal control (not true, more a fraction of what I 
expect)

  ** How to get crash

  For me,

  - I used chromium (browser)
  - make chromium full screen (ie. F11)
  - click on something & right-click to open in new window
  OPENBOX CRASH.

  ProblemType: Crash
  DistroRelease: Ubuntu 23.04
  Package: openbox 3.6.1-10
  ProcVersionSignature: Ubuntu 6.1.0-16.16-generic 6.1.6
  Uname: Linux 6.1.0-16-generic x86_64
  ApportVersion: 2.26.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CrashCounter: 1
  CurrentDesktop: LXQt
  Date: Thu Mar 16 09:46:22 2023
  ExecutablePath: /usr/bin/openbox
  ExecutableTimestamp: 1643543619
  InstallationDate: Installed on 2023-01-25 (49 days ago)
  InstallationMedia: Lubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20230124)
  JournalErrors: -- No entries --
  ProcCmdline: /usr/bin/openbox
  ProcCwd: /home/guiverc
  RebootRequiredPkgs: Error: path contained symlinks.
  Signal: 6
  SourcePackage: openbox
  StacktraceTop:
   () at /lib/x86_64-linux-gnu/libobt.so.2
    () at /lib/x86_64-linux-gnu/libc.so.6
   client_calc_layer ()
   ()
   () at /lib/x86_64-linux-gnu/libobt.so.2
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  separator:

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

[Ubuntu QA Website]

This bug has been reported on the Ubuntu ISO testing tracker.

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

** Tags added: iso-testing

-- 
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 GTK+:
  Unknown
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:
  Fix Released
Status in xdg-desktop-portal-gnome package in Ubuntu:
  Confirmed
Status in xdg-desktop-portal-gtk package in Ubuntu:
  Confirmed
Status in gtk+3.0 source package in Jammy:
  Confirmed
Status in gtk4 source package in Jammy:
  Triaged
Status in gtk+3.0 source package in Kinetic:
  Confirmed
Status in gtk4 source package in Kinetic:
  Fix Released

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 2008638] Re: apport-gtk crashed with urllib.error.HTTPError in http_error_default(): HTTP Error 502: Bad Gateway

[Ubuntu QA Website]

This bug has been reported on the Ubuntu ISO testing tracker.

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

** Tags added: iso-testing

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

Title:
  apport-gtk crashed with urllib.error.HTTPError in
  http_error_default(): HTTP Error 502: Bad Gateway

Status in Apport:
  Fix Committed
Status in apport package in Ubuntu:
  Confirmed

Bug description:
  Had a Nautlius crash prior to this error.

  ProblemType: Crash
  DistroRelease: Ubuntu 23.04
  Package: apport-gtk 2.26.0-0ubuntu2
  ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7
  Uname: Linux 5.19.0-21-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.26.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CrashReports:
   640:1201:124:38512857:2023-02-24 12:17:00.435185909 -0500:2023-02-24 
12:17:01.435185909 -0500:/var/crash/_usr_bin_gnome-shell.1201.crash
   640:1000:1000:90509:2023-02-26 10:18:25.277171373 -0500:2023-02-26 
10:18:26.277171373 -0500:/var/crash/_usr_share_apport_apport-gtk.1000.crash
   600:116:124:37:2023-02-26 10:18:21.948992294 -0500:2023-02-18 
17:59:57.688578533 -0500:/var/crash/_usr_bin_nautilus.1000.uploaded
   640:1000:124:14955989:2023-02-26 10:16:50.213119506 -0500:2023-02-26 
10:17:03.637664041 -0500:/var/crash/_usr_bin_nautilus.1000.crash
   664:1000:1000:0:2023-02-26 10:17:03.617663168 -0500:2023-02-26 
10:17:03.617663168 -0500:/var/crash/_usr_bin_nautilus.1000.upload
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Feb 26 10:18:26 2023
  ExecutablePath: /usr/share/apport/apport-gtk
  InstallationDate: Installed on 2023-02-13 (12 days ago)
  InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20221209)
  InterpreterPath: /usr/bin/python3.11
  JournalErrors:
   Feb 26 10:18:26 hostname systemd[2030]: update-notifier-crash.service: 
Failed with result 'exit-code'.
   Feb 26 10:18:26 hostname systemd[2030]: Failed to start Notification 
regarding a crash report.
  PackageArchitecture: all
  ProcCmdline: /usr/bin/python3 /usr/share/apport/apport-gtk
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  Python3Details: /usr/bin/python3.11, Python 3.11.1, python3-minimal, 3.11.1-3
  PythonArgs: ['/usr/share/apport/apport-gtk']
  PythonDetails: N/A
  SourcePackage: apport
  Title: apport-gtk crashed with urllib.error.HTTPError in 
http_error_default(): HTTP Error 502: Bad Gateway
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo users

To manage notifications about this bug go to:
https://bugs.launchpad.net/apport/+bug/2008638/+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 2009034] Re: Ubuntu 23.04 Canary subiquity crashed install failed

[Ubuntu QA Website]

This bug has been reported on the Ubuntu ISO testing tracker.

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

** Tags added: iso-testing

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

Title:
  Ubuntu 23.04 Canary subiquity crashed install failed

Status in openssh package in Ubuntu:
  New

Bug description:
  QA Testing daily build 20230302 install failed.

  Mar 02 06:24:14 ubuntu subiquity_log.3098[12985]: Running command ['mount', 
'--make-private', '/target/dev'] with allowed return codes [0] (capture=False)
  Mar 02 06:24:14 ubuntu subiquity_log.3098[12985]: Running command ['umount', 
'/target/dev'] with allowed return codes [0] (capture=False)
  Mar 02 06:24:14 ubuntu subiquity_log.3098[12985]: finish: cmd-in-target: 
FAIL: curtin command in-target

  ProblemType: Crash
  DistroRelease: Ubuntu 23.04
  Package: openssh-client 1:9.0p1-1ubuntu8
  Uname: Linux 5.19.0-21-generic x86_64
  Architecture: amd64
  Date: Thu Mar  2 12:13:28 2023
  ExecutablePath: /usr/bin/ssh-keygen
  ExecutableTimestamp: 1666713463
  ProcCmdline: ssh-keygen -t rsa -b 4096 -N  -f /tmp/snapd3272526883/rsa.key -m 
PEM
  ProcCwd: /
  ProcEnviron:
   LANG=C.UTF-8
   PATH=(custom, no user)
  Signal: 7
  SourcePackage: openssh
  UserGroups: N/A

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/2009034/+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 1993493] Re: lightdm crashed after switching users (lightdm-gtk-greeter, xfce4-screensaver)

[Ubuntu QA Website]

This bug has been reported on the Ubuntu ISO testing tracker.

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

** Tags added: iso-testing

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

Title:
  lightdm crashed after switching users (lightdm-gtk-greeter,
  xfce4-screensaver)

Status in lightdm package in Ubuntu:
  New

Bug description:
  Running the Xubuntu Post-install test on GNOME Boxes. This is on a
  fresh install, first boot.

  1. Create a new user
  2. Lock your session (xflock4)
  3. Switch user (xfce4-screensaver)
  4. Log in as the new user (lightdm-gtk-greeter)
  5. Log out
  6. Log back in as the original user
  7. The screen goes black, and the original user is logged out

  I've seen this a few times with 22.10, but thought it was a weird one-
  off issue. Repeating the test with a new session does not seem to
  reproduce the issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: lightdm 1.30.0-0ubuntu7
  ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7
  Uname: Linux 5.19.0-21-generic x86_64
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: XFCE
  Date: Wed Oct 19 04:33:32 2022
  InstallationDate: Installed on 2022-10-19 (0 days ago)
  InstallationMedia: Xubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221018)
  LightdmConfig:
   [Seat:*]
   autologin-guest=false
   autologin-user=oem
   autologin-user-timeout=0
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1993493/+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 1993370] Re: Cannot install proprietary Broadcom WiFi drivers on Ubuntu Studio Kinetic

[Ubuntu QA Website]

This bug has been reported on the Ubuntu ISO testing tracker.

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

** Tags added: iso-testing

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

Title:
  Cannot install proprietary Broadcom WiFi drivers on Ubuntu Studio
  Kinetic

Status in software-properties package in Ubuntu:
  New

Bug description:
  Hardware: HP Elitebook 8570p, 16 GB RAM, 120 GB SSD, 3rd Gen Intel
  Core i5, UEFI, no secure boot, Broadcom WiFi.

  OS: Ubuntu Studio Kinetic, Final ISO

  Steps to reproduce:

  1. Boot the Ubuntu Studio ISO on a system with Broadcom WiFi, and install the 
system normally. (No encryption, allow Internet access during installation 
using some method of connectivity other than WiFi.)
  2. Reboot and log into the newly installed system.
  3. Open a terminal and run "sudo software-properties-kde".
  4. Click "Additional Drivers" in the window that pops up.
  5. Click "Using Broadcom 802.11 Linux STA wireless driver source from 
bcmwl-kernel-source (proprietary)".

  Expected result: The Apply Changes button should become clickable,
  allowing the user to install the driver.

  Actual result: The button remains grayed out, and the following error
  message is printed in the terminal:

  Traceback (most recent call last):
File 
"/usr/lib/python3/dist-packages/softwareproperties/qt/SoftwarePropertiesQt.py", 
line 1063, in on_driver_selection_changed
  modules_package_obj = self.apt_cache[modules_package]
  TypeError: Expected a string or a pair of strings

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: software-properties-qt 0.99.27
  ProcVersionSignature: Ubuntu 5.19.0-1007.7-lowlatency 5.19.7
  Uname: Linux 5.19.0-1007-lowlatency x86_64
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  Date: Tue Oct 18 21:33:51 2022
  InstallationDate: Installed on 2022-10-19 (0 days ago)
  InstallationMedia: Ubuntu-Studio 22.10 "Kinetic Kudu" - Release amd64 
(20221017.1)
  PackageArchitecture: all
  SourcePackage: software-properties
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1993370/+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

[Ubuntu QA Website]

This bug has been reported on the Ubuntu ISO testing tracker.

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

** Tags added: iso-testing

-- 
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.

  ** 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" profile="snap-update-ns.chromium" 
name="/usr/local/share/fonts/" pid=3518 comm="6" requested_mask="r" 
denied_mask="r" fsuid=0 ouid=0
  [ 1628.635260] kauditd_printk_skb: 6 callbacks suppressed
  [ 1628.635268] audit: type=1400 

[Touch-packages] [Bug 1988145] Re: Couldn't create temporary file /tmp/apt.conf.fsIutr for passing config to apt-key

[Ubuntu QA Website]

This bug has been reported on the Ubuntu ISO testing tracker.

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

** Tags added: iso-testing

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

Title:
  Couldn't create temporary file /tmp/apt.conf.fsIutr for passing config
  to apt-key

Status in apt package in Ubuntu:
  Invalid

Bug description:
  I tried to run
  
http://iso.qa.ubuntu.com/qatracker/milestones/438/builds/257552/testcases/1318/results

  I downloaded http://cdimage.ubuntu.com/ubuntu-
  base/focal/daily/20220829.1/focal-base-riscv64.tar.gz

  mkdir base
  sudo tar -C base -zxf focal-base-riscv64.tar.gz
  sudo mount --bind /proc base/proc
  sudo mount --bind /sys base/sys
  sudo mount --bind /dev base/dev
  sudo mount --bind /dev/pts base/dev/pts
  sudo cp /etc/resolv.conf base/etc/
  sudo chroot base

  apt-get update results in:

  Get:1 http://ports.ubuntu.com/ubuntu-ports focal InRelease [265 kB]
  Get:2 http://ports.ubuntu.com/ubuntu-ports focal-updates InRelease [114 kB]
  Err:1 http://ports.ubuntu.com/ubuntu-ports focal InRelease
    Couldn't create temporary file /tmp/apt.conf.fsIutr for passing config to 
apt-key
  Err:2 http://ports.ubuntu.com/ubuntu-ports focal-updates InRelease
    Couldn't create temporary file /tmp/apt.conf.x7LQrB for passing config to 
apt-key
  Get:3 http://ports.ubuntu.com/ubuntu-ports focal-backports InRelease [108 kB]
  Err:3 http://ports.ubuntu.com/ubuntu-ports focal-backports InRelease
    Couldn't create temporary file /tmp/apt.conf.t2upW0 for passing config to 
apt-key
  Get:4 http://ports.ubuntu.com/ubuntu-ports focal-security InRelease [114 kB]
  Err:4 http://ports.ubuntu.com/ubuntu-ports focal-security InRelease
    Couldn't create temporary file /tmp/apt.conf.L2I28d for passing config to 
apt-key
  Reading package lists... Done
  W: GPG error: http://ports.ubuntu.com/ubuntu-ports focal InRelease: Couldn't 
create temporary file /tmp/apt.conf.fsIutr for passing config to apt-key
  E: The repository 'http://ports.ubuntu.com/ubuntu-ports focal InRelease' is 
not signed.
  N: Updating from such a repository can't be done securely, and is therefore 
disabled by default.
  N: See apt-secure(8) manpage for repository creation and user configuration 
details.
  W: GPG error: http://ports.ubuntu.com/ubuntu-ports focal-updates InRelease: 
Couldn't create temporary file /tmp/apt.conf.x7LQrB for passing config to 
apt-key
  E: The repository 'http://ports.ubuntu.com/ubuntu-ports focal-updates 
InRelease' is not signed.
  N: Updating from such a repository can't be done securely, and is therefore 
disabled by default.
  N: See apt-secure(8) manpage for repository creation and user configuration 
details.
  W: GPG error: http://ports.ubuntu.com/ubuntu-ports focal-backports InRelease: 
Couldn't create temporary file /tmp/apt.conf.t2upW0 for passing config to 
apt-key
  E: The repository 'http://ports.ubuntu.com/ubuntu-ports focal-backports 
InRelease' is not signed.
  N: Updating from such a repository can't be done securely, and is therefore 
disabled by default.
  N: See apt-secure(8) manpage for repository creation and user configuration 
details.
  W: GPG error: http://ports.ubuntu.com/ubuntu-ports focal-security InRelease: 
Couldn't create temporary file /tmp/apt.conf.L2I28d for passing config to 
apt-key
  E: The repository 'http://ports.ubuntu.com/ubuntu-ports focal-security 
InRelease' is not signed.
  N: Updating from such a repository can't be done securely, and is therefore 
disabled by default.
  N: See apt-secure(8) manpage for repository creation and user configuration 
details.

  As touch /tmp/apt.conf.fsIutr works without issues there must be a bug
  in how apt creates temporary files.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1988145/+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 1820584] Re: seahorse assert failure: seahorse: glib-watch.c:195: timeout_update: Assertion `!t->dead' failed.

[Ubuntu QA Website]

This bug has been reported on the Ubuntu ISO testing tracker.

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

** Tags added: iso-testing

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

Title:
  seahorse assert failure: seahorse: glib-watch.c:195: timeout_update:
  Assertion `!t->dead' failed.

Status in avahi package in Ubuntu:
  Confirmed

Bug description:
  -
  Description:  Ubuntu Disco Dingo (development branch)
  Release:  19.04
  -
  seahorse:
Installed: 3.32-1
Candidate: 3.32-1
Version table:
   *** 3.32-1 500
  500 http://br.archive.ubuntu.com/ubuntu disco/main amd64 Packages
  100 /var/lib/dpkg/status
  -

  I have absolutely no idea why or how. Just collected this report from
  apport-cli.

  Some times receiving "internal error" reports, no details provided,
  just "Cancel" or "Send report" options. So, I decided to check apport
  and there was this report.

  ProblemType: Crash
  DistroRelease: Ubuntu 19.04
  Package: seahorse 3.32-1
  ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0
  Uname: Linux 5.0.0-7-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  AssertionMessage: seahorse: glib-watch.c:195: timeout_update: Assertion 
`!t->dead' failed.
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Mar 17 18:09:01 2019
  ExecutablePath: /usr/bin/seahorse
  InstallationDate: Installed on 2019-03-17 (0 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190316)
  ProcCmdline: /usr/bin/seahorse --gapplication-service
  Signal: 6
  SourcePackage: seahorse
  StacktraceTop:
   __assert_fail_base (fmt=0x7f733ae49588 "%s%s%s:%u: %s%sAssertion `%s' 
failed.\n%n", assertion=0x7f733aecf02d "!t->dead", file=0x7f733aecf000 
"glib-watch.c", line=195, function=) at assert.c:92
   __GI___assert_fail (assertion=0x7f733aecf02d "!t->dead", file=0x7f733aecf000 
"glib-watch.c", line=195, function=0x7f733aecf1d8 "timeout_update") at 
assert.c:101
   ?? () from /lib/x86_64-linux-gnu/libavahi-glib.so.1
   ?? () from /lib/x86_64-linux-gnu/libavahi-client.so.3
   ?? () from /lib/x86_64-linux-gnu/libavahi-glib.so.1
  Title: seahorse assert failure: seahorse: glib-watch.c:195: timeout_update: 
Assertion `!t->dead' failed.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1820584/+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 1924251] Re: Embedded browser display corruption under Wayland on Pi desktop

[Ubuntu QA Website]

This bug has been reported on the Ubuntu ISO testing tracker.

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

** Tags added: iso-testing

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

Title:
  Embedded browser display corruption under Wayland on Pi desktop

Status in gtk+3.0 package in Ubuntu:
  Confirmed
Status in webkit2gtk package in Ubuntu:
  Confirmed
Status in yelp package in Ubuntu:
  Confirmed

Bug description:
  On the hirsute Pi desktop, under a wayland session with the "full" KMS
  overlay enabled, and "kms-modifiers" present in the
  org.gnome.mutter/experimental-features, the body of a window
  containing an HTML renderer (e.g. help text or a login page) displays
  corruption.

  These reproduction cases may not be entirely reliable given that
  *some* pages appear to render correctly, but I'll include a couple in
  the hopes of making it reliably reproducible:

  1. Open the Lights Off game
  2. Select "Help" from the menu
  3. In the help window that appears, select any link

  "Basics", "Rules", and "Strategy" all reliably reproduce the issue for
  me, but "Help Translate" doesn't so you may need to click around some
  links until the corruption appears -- however, once it does even
  navigating back to the prior page which rendered happily now displays
  the same corruption.

  Another reproduction case:

  1. Open the Settings application
  2. Select the Online Applications option from the left
  3. Select the Google entry in the list
  4. The login window that appears always displays corruption for me

  The Microsoft option always reliably corrupts for me, but the Facebook
  one doesn't so again I wonder how reproducible this may be for others
  (might be worth trying several options if the first doesn't display
  corruption).

  The corruption appears in the form of "shredded" content as if a
  horizontal stride is set incorrectly somewhere, but only appears in
  the body of the window; the window decorations are unaffected. I'll
  attach a screenshot of the corrupted help window to illustrate.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1924251/+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 1982935] Re: Selecting "restore defaults" in software-properties-qt has no effect

[Ubuntu QA Website]

This bug has been reported on the Ubuntu ISO testing tracker.

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

** Tags added: iso-testing

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

Title:
  Selecting "restore defaults" in software-properties-qt has no effect

Status in software-properties package in Ubuntu:
  New

Bug description:
  Testing Lubuntu Kinetic daily ISO 26-07-2022

  1. Open "Software Sources" from "Preferences menu
  2. Select "Authentication" 
  3. Delete the keys from "Trusted Service Providers"
  4. Select "Restore Defaults"
  5. After selecting "Restore Defaults" - nothing happens i.e the keys are not 
restored resulting in  the user being unable to perform updates to the system.

  
  This bug is most likely related to bug 11795278 
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1795278

  Attached is a screenshot after removing the keys re: step #3

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: software-properties-qt 0.99.25
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Uname: Linux 5.15.0-27-generic x86_64
  ApportVersion: 2.22.0-0ubuntu4
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: LXQt
  Date: Wed Jul 27 09:19:33 2022
  InstallationDate: Installed on 2022-07-27 (0 days ago)
  InstallationMedia: Lubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220726)
  PackageArchitecture: all
  SourcePackage: software-properties
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1982935/+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 1973470] Re: Ubuntu-bug command can't find Firefox on Lubuntu Kinetic

[Ubuntu QA Website]

This bug has been reported on the Ubuntu ISO testing tracker.

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

** Tags added: iso-testing

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

Title:
  Ubuntu-bug command can't find Firefox on Lubuntu Kinetic

Status in apport package in Ubuntu:
  New

Bug description:
  Test hardware is an Elitebook 8570p, 16 GB RAM, 120 GB SSD.

  While reporting Bug #1973469, I discovered that ubuntu-bug was unable
  to open Firefox at the very end of the process. Sadly, I closed the
  terminal window that contained the initial error, but I was able to
  easily reproduce it reporting this bug. The full console output of
  "ubuntu-bug apport" on Lubuntu Kinetic is:

  
  *** Collecting problem information

  The collected information can be sent to the developers to improve the
  application. This might take a few minutes.
  ..

  *** Send problem report to the developers?

  After the problem report has been sent, please fill out the form in the
  automatically opened web browser.

  What would you like to do? Your options are:
S: Send report (5.1 KB)
V: View report
K: Keep report file for sending later or copying to somewhere else
I: Cancel and ignore future crashes of this program version
C: Cancel
  Please choose (S/V/K/I/C): s

  *** Uploading problem information

  The collected information is being sent to the bug tracking system.
  This might take a few minutes.
  94%

  *** To continue, you must visit the following URL:

  
https://bugs.launchpad.net/ubuntu/+source/apport/+filebug/d7ffa3e0-d46d-11ec-a167-40a8f03099c8?

  You can launch a browser now, or copy this URL into a browser on
  another computer.

  
  Choices:
1: Launch a browser now
C: Cancel
  Please choose (1/C): 1
  /usr/bin/xdg-open: 882: firefox: not found
  /usr/bin/xdg-open: 882: firefox: not found
  xdg-open: no method available for opening 
'https://bugs.launchpad.net/ubuntu/+source/apport/+filebug/d7ffa3e0-d46d-11ec-a167-40a8f03099c8?'

  I am unsure if this problem is in Apport or Lubuntu. ubuntu-bug works
  just fine for me on Ubuntu Kinetic, but not on Lubuntu. I suspect this
  is due to the Snap version of Firefox, but I don't know for sure.
  Since ubuntu-bug is what gave me the error, I'm filing this against
  Apport.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: apport 2.20.11-0ubuntu82
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Uname: Linux 5.15.0-27-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: pass
  CasperVersion: 1.470
  CurrentDesktop: LXQt
  Date: Sun May 15 11:41:07 2022
  LiveMediaBuild: Lubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220514)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1973470/+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 1972009] Re: Totem fails to find video - kinetic ubuntu raspi pi

[Ubuntu QA Website]

This bug has been reported on the Ubuntu ISO testing tracker.

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

** Tags added: iso-testing

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

Title:
  Totem fails to find video - kinetic ubuntu raspi pi

Status in gstreamer1.0 package in Ubuntu:
  New

Bug description:
  Running test kinetic ubuntu daily - raspi 4 8GB daily ISO

  When attempting to run "totem big_buck_bunny_720p_surround.mp4" as per
  the testcase - received the error - An error occurred - the specified
  movie could not be found.

  No further errors encountered

  
  -- I ran ubuntu-bug totem but see that the package selected is "gstreamer1.0" 
- please correct if need be.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: libgstreamer1.0-0 1.20.1-1
  ProcVersionSignature: Ubuntu 5.15.0-1006.6-raspi 5.15.30
  Uname: Linux 5.15.0-1006-raspi aarch64
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: arm64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Fri May  6 17:07:53 2022
  ImageMediaBuild: 20220506
  LogAlsaMixer:
   Simple mixer control 'Headphone',0
 Capabilities: pvolume pvolume-joined pswitch pswitch-joined
 Playback channels: Mono
 Limits: Playback -10239 - 400
 Mono: Playback -2000 [77%] [-20.00dB] [on]
  SourcePackage: gstreamer1.0
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1972009/+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 1965439] Re: software-properties-qt can no longer launch when called by pkexec

[Ubuntu QA Website]

This bug has been reported on the Ubuntu ISO testing tracker.

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

** Tags added: iso-testing

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

Title:
  software-properties-qt can no longer launch when called by pkexec

Status in kubuntu-settings package in Ubuntu:
  In Progress
Status in policykit-1 package in Ubuntu:
  Confirmed
Status in software-properties package in Ubuntu:
  Confirmed
Status in ubuntustudio-default-settings package in Ubuntu:
  In Progress
Status in kubuntu-settings source package in Jammy:
  In Progress
Status in policykit-1 source package in Jammy:
  Confirmed
Status in software-properties source package in Jammy:
  Confirmed
Status in ubuntustudio-default-settings source package in Jammy:
  In Progress

Bug description:
  See description below. As the driver manager is done inside software-
  properties-qt, it's basically the same bug, but now it's affected by
  something we can't exactly get into the mechanism of: plasma-
  discover's "Software Sources" link.

  Steps to recrate:

  1) Open Plasma-discover
  2) Go to Settings
  3) Under click on "Software Sources"
  4) Attempt to enter password

  Expected: Software properties opens

  Actual: Pkexec keeps asking for password.

  --

  Earlier description:

  The driver manager for both Ubuntu Studio and Kubuntu can no longer
  launch due to some updated security measures in PolicyKit.

  The original behavior was that systemsettings would open
  /usr/bin/ubuntustudio-driver-manager (or /usr/bin/kubuntu-driver-
  manger) via pkexec, which would then open software-settings-qt.
  Unfortunately, the new behavior does not act correctly to pkexec and
  pkexec does not see the user as available in the sudoers file.

  The only way around this was to pass "export DISPLAY=:0" inside the
  appropriate driver manager executable with the command "sudo software-
  properties-qt". The KCM itself needs to execute the driver-manager via
  xterm, which then prompts for a password. It's ugly, but it works.

  I will attach a debdiff for the kubuntu-settings package.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: ubuntustudio-default-settings 22.04.19 [modified: 
usr/share/sddm/themes/ubuntustudio/theme.conf]
  ProcVersionSignature: Ubuntu 5.15.0-22.22-lowlatency 5.15.19
  Uname: Linux 5.15.0-22-lowlatency x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  Date: Thu Mar 17 12:19:44 2022
  InstallationDate: Installed on 2021-03-20 (361 days ago)
  InstallationMedia: Ubuntu-Studio 21.04 "Hirsute Hippo" - Alpha amd64 
(20210320)
  PackageArchitecture: all
  SourcePackage: ubuntustudio-default-settings
  UpgradeStatus: Upgraded to jammy on 2021-11-07 (130 days ago)
  modified.conffile..etc.skel..local.share.konsole.Profile: [deleted]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kubuntu-settings/+bug/1965439/+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 1877194] Re: switch-on-connect mistakes startup for USB hotplug, so seemingly ignores the old default device on reboot

[Ubuntu QA Website]

This bug has been reported on the Ubuntu ISO testing tracker.

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

** Tags added: iso-testing

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

Title:
  switch-on-connect mistakes startup for USB hotplug, so seemingly
  ignores the old default device on reboot

Status in PulseAudio:
  Unknown
Status in pulseaudio package in Ubuntu:
  Triaged

Bug description:
  Similar to:
  https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1847570

  Only difference is that it does not reset to HDMI output, but to one
  of my USB-outputs. It does not respect the change I made after reboot.

  In short:
  1. Boot system
  2. "Analogue Output - RODE NT-USB" is selected by default. I want to use 
"Line Out - Built-in Audio", which I choose.
  3. Reboot.
  4 Output device is now back to "Analogue Output - RODE NT-USB".

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu3
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  marcus 1604 F pulseaudio
   /dev/snd/controlC0:  marcus 1604 F pulseaudio
   /dev/snd/controlC1:  marcus 1604 F pulseaudio
   /dev/snd/pcmC1D0c:   marcus 1604 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed May  6 23:40:08 2020
  InstallationDate: Installed on 2020-05-06 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/27/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3703
  dmi.board.asset.tag: Default string
  dmi.board.name: MAXIMUS VIII HERO
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3703:bd12/27/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnMAXIMUSVIIIHERO:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

To manage notifications about this bug go to:
https://bugs.launchpad.net/pulseaudio/+bug/1877194/+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 1962036] Re: dbus was stopped during today's jammy update, breaking desktop

[Ubuntu QA Website]

This bug has been reported on the Ubuntu ISO testing tracker.

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

** Tags added: iso-testing

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

Title:
  dbus was stopped during today's jammy update, breaking desktop

Status in dbus package in Ubuntu:
  Fix Released
Status in dbus source package in Jammy:
  Fix Released

Bug description:
  Impact: logind stopped, so desktop stopped, ssh stopped, got no getty.
  Had to hard reset.

  Today's jammy upgrade stopped dbus at 19:46:27

  Feb 23 19:46:27 jak-t480s systemd[1]: Stopping D-Bus System Message
  Bus...

  This should not happen. I don't know which package caused this, but
  presumably dbus should not be stoppable in the first place.


  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: dbus 1.12.20-2ubuntu3
  ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19
  Uname: Linux 5.15.0-22-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu78
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: GNOME
  Date: Wed Feb 23 20:03:41 2022
  InstallationDate: Installed on 2018-03-14 (1442 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180313)
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: dbus
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1962036/+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 1967648] Re: lubuntu jammy - `ubuntu-bug lxqt-config` isn't opening firefox

[Ubuntu QA Website]

This bug has been reported on the Ubuntu ISO testing tracker.

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

** Tags added: iso-testing

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

Title:
  lubuntu jammy - `ubuntu-bug lxqt-config` isn't opening firefox

Status in apport package in Ubuntu:
  New

Bug description:
  /usr/bin/xdg-open: 882: firefox: not found
  /usr/bin/xdg-open: 882: firefox: not found
  xdg-open: no method available for opening 
'https://bugs.launchpad.net/ubuntu/+source/lxqt-config/+filebug/9f12535a-b2f0-11ec-b9ed-40a8f0305cb4?'

  
  Lubuntu jammy install test on dell optiplex 780

  I adjusted displays as mouse-movements were annoying me, noticed an
  issue thus filed a bug report using `ubuntu-bug lxqt-config`

  ** expected output

  on executing `ubuntu-but lxqt-config` I expected firefox to start

  ** actual output

  ---
  lubuntu@lubuntu:~$ ubuntu-bug lxqt-config

  *** Collecting problem information

  The collected information can be sent to the developers to improve the
  application. This might take a few minutes.
  ...

  *** Send problem report to the developers?

  After the problem report has been sent, please fill out the form in the
  automatically opened web browser.

  What would you like to do? Your options are:
    S: Send report (19.6 KB)
    V: View report
    K: Keep report file for sending later or copying to somewhere else
    I: Cancel and ignore future crashes of this program version
    C: Cancel
  Please choose (S/V/K/I/C): s

  *** Uploading problem information

  The collected information is being sent to the bug tracking system.
  This might take a few minutes.
  98%

  *** To continue, you must visit the following URL:

    https://bugs.launchpad.net/ubuntu/+source/lxqt-
  config/+filebug/9f12535a-b2f0-11ec-b9ed-40a8f0305cb4?

  You can launch a browser now, or copy this URL into a browser on
  another computer.

  Choices:
    1: Launch a browser now
    C: Cancel
  Please choose (1/C): 1
  /usr/bin/xdg-open: 882: firefox: not found
  /usr/bin/xdg-open: 882: firefox: not found
  xdg-open: no method available for opening 
'https://bugs.launchpad.net/ubuntu/+source/lxqt-config/+filebug/9f12535a-b2f0-11ec-b9ed-40a8f0305cb4?'
  ---

  ie. `firefox` doesn't start as it's now a snap package

  first attempt to file `ubuntu-bug apport` ended up with

  ---
  *** To continue, you must visit the following URL:

    https://bugs.launchpad.net/ubuntu/+source/lxqt-
  config/+filebug/9f12535a-b2f0-11ec-b9ed-40a8f0305cb4?

  You can launch a browser now, or copy this URL into a browser on
  another computer.

  Choices:
    1: Launch a browser now
    C: Cancel
  Please choose (1/C): 1
  /usr/bin/xdg-open: 882: firefox: not found
  /usr/bin/xdg-open: 882: firefox: not found
  xdg-open: no method available for opening 
'https://bugs.launchpad.net/ubuntu/+source/lxqt-config/+filebug/9f12535a-b2f0-11ec-b9ed-40a8f0305cb4?'
  lubuntu@lubuntu:~$
  ---

  ** other notes

  - I don't know if this only impacts lubuntu, or others too
  - I've not (yet) looked for other/existing bugs

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: apport 2.20.11-0ubuntu80
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Uname: Linux 5.15.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu80
  Architecture: amd64
  CasperMD5CheckResult: pass
  CasperVersion: 1.468
  CurrentDesktop: LXQt
  Date: Sun Apr  3 12:09:05 2022
  LiveMediaBuild: Lubuntu 22.04 LTS "Jammy Jellyfish" - Daily amd64 (20220402)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1967648/+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 1966418] Re: [jammy regression] Evolution does not display message content anymore

[Ubuntu QA Website]

This bug has been reported on the Ubuntu ISO testing tracker.

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

** Tags added: iso-testing

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

Title:
  [jammy regression] Evolution does not display message content anymore

Status in Mesa:
  Unknown
Status in Webkit:
  Confirmed
Status in epiphany-browser package in Ubuntu:
  Invalid
Status in evolution package in Ubuntu:
  Invalid
Status in gnome-control-center package in Ubuntu:
  Invalid
Status in liferea package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Confirmed
Status in webkit2gtk package in Ubuntu:
  Confirmed

Bug description:
  Impact
  --
  All webkit using apps for affected users display a blank screen.

  Original Bug Report
  ---
  Evolution has suddenly stopped displaying message contents on the last 24h. 
Starting it up from the command line shows this output:

  ```
  EGLDisplay Initialization failed: EGL_NOT_INITIALIZED
  Cannot create EGL context: invalid display (last error: EGL_SUCCESS)
  ```

  I don't know if it's related, but googling around shows some webkitgtk
  hits on this error.

  The email contents are however clickable. They're just not rendered to
  screen (see attached file).

  Deleting the evolution folders from `~/.config`, `~/.cache` and
  `~/.local/share` does not help.

  Email accounts are all google, configured through gnome online
  accounts.

  Workaround #1
  -
  You can run the app from the command line with
  WEBKIT_DISABLE_COMPOSITING_MODE=1 evolution
  (Replace evolution with the name of the webkit app you are trying to use)

  Workaround #2
  -
  Log out.
  Select your name on the login screen.
  Click the gear button and choose Ubuntu on Xorg.
  Enter your password to finish logging in.

  
  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: evolution 3.44.0-1
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Uname: Linux 5.15.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: sway
  Date: Fri Mar 25 10:55:49 2022
  SourcePackage: evolution
  UpgradeStatus: Upgraded to jammy on 2022-03-01 (24 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/mesa/+bug/1966418/+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 1964579] Re: Pulseaudio fails to detect /enable Intel SST sound card

[Ubuntu QA Website]

This bug has been reported on the Ubuntu ISO testing tracker.

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

** Tags added: iso-testing

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

Title:
  Pulseaudio fails to detect /enable Intel SST sound card

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Testing Live session and also full install  Ubuntu Mate Jammy daily
  ISO 11-03-2022

  The machine tested - AEROFARA Aero2 Pro, N5105,8GB,Ethernet
  GB,WiFi,Bluetooth 4.0,128GB SSD,Intel UHD Graphics

  The audio card is not detected - entering sound preferences settings -
  "output" only shows

  dummy output stereo - under "hardware" is no entry available

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: pulseaudio 1:15.99.1+dfsg1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19
  Uname: Linux 5.15.0-22-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu78
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/pcmC0D3p', 
'/dev/snd/pcmC0D2p', '/dev/snd/pcmC0D1p', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
  CasperMD5CheckResult: pass
  CasperVersion: 1.467
  CurrentDesktop: MATE
  Date: Fri Mar 11 09:25:31 2022
  LiveMediaBuild: Ubuntu-MATE 22.04 LTS "Jammy Jellyfish" - Alpha amd64 
(20220311)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_Card: sof-hda-dsp - sof-hda-dsp
  Symptom_Jack: Digital Out, HDMI
  Title: [AERO 2 Pro, Intel Jasperlake HDMI, Digital Out, HDMI] Pulseaudio 
fails to detect card
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/13/2021
  dmi.bios.release: 5.19
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: JB1006
  dmi.board.asset.tag: Default string
  dmi.board.name: AERO 2 Pro
  dmi.board.vendor: Shenzhen Wangang Technology Co., Ltd
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 35
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.ec.firmware.release: 0.7
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrJB1006:bd12/13/2021:br5.19:efr0.7:svnShenzhenWangangTechnologyCo.,Ltd:pnAERO2Pro:pvrDefaultstring:rvnShenzhenWangangTechnologyCo.,Ltd:rnAERO2Pro:rvrDefaultstring:cvnDefaultstring:ct35:cvrDefaultstring:skuAERO2Pro:
  dmi.product.family: Windows 10 Pro
  dmi.product.name: AERO 2 Pro
  dmi.product.sku: AERO 2 Pro
  dmi.product.version: Default string
  dmi.sys.vendor: Shenzhen Wangang Technology Co., Ltd

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1964579/+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 1964405] Re: ubuntu-bug doesn't launch browser to upload collected information automagically to Launchpad

[Ubuntu QA Website]

This bug has been reported on the Ubuntu ISO testing tracker.

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

** Tags added: iso-testing

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

Title:
  ubuntu-bug doesn't launch browser to upload collected information
  automagically to Launchpad

Status in apport package in Ubuntu:
  New

Bug description:
  1) lsb_release -rd
  Description:Ubuntu Jammy Jellyfish (development branch)
  Release:22.04

  (Kubuntu Jammy live session in QEMU VM)

  2) package version - apt-cache policy pkgname'
  apt-cache policy apport
  apport:
    Installed: 2.20.11-0ubuntu78

  3) expected to happen
  * launch bug gathering via terminal (specifying as argument any package, in 
this case Dolphin)
   $ ubuntu-bug dolphin
  * GUI opens while gathering information, presents dialogue for review.
  * Upon clicking "Send" button, browser should launch to Launchpad login 
screen for submitting the bug report.

  4) happened instead
  * Upon clicking "Send" button, browser *does not* launch to Launchpad login 
screen for submitting the bug report. Broswer does not launch. Nothing else 
appears to happen.

  ## Additional Info
  * works as expected on Ubuntu 20.04.4 LTS / apport 2.20.11-0ubuntu27.21
  * apport-collect [bug-number] works as expected (launches browser)

  ## workaround
  * save bug report to file, manually upload to Launchpad
   $ ubuntu-bug --save=[file] [package]

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

[Ubuntu QA Website]

This bug has been reported on the Ubuntu ISO testing tracker.

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

** Tags added: iso-testing

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

Title:
  "Connection failed" for WPA Enterprise network eduroam

Status in wpa package in Ubuntu:
  Confirmed

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

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

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

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

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

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

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


-- 
Mailing list: https://launchpad.net/~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 1960083] Re: dirname applet missing from initramfs

[Ubuntu QA Website]

This bug has been reported on the Ubuntu ISO testing tracker.

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

** Tags added: iso-testing

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

Title:
  dirname applet missing from initramfs

Status in busybox package in Ubuntu:
  Fix Released
Status in zfs-linux package in Ubuntu:
  Confirmed

Bug description:
  The initramfs is currently being built without the dirname applet.
  This is causing issues with zfs encrypted devices, as cryptsetup is
  attempting to use dirname to determine the location of the system key.
  This results in the following error:

  /init: line 971: dirname: not found

  followed by a prompt that is missing the zpool name. For example

  "Please unlock disk keystore-" rather than "Please unlock disk
  keystore-rpool".

  After entering the password, the user is dropped to an initramfs
  shell.

  It appears that this was caused by a change in cryptsetup to suddenly
  need dirname to function properly.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/busybox/+bug/1960083/+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 1960460] Re: Fails to import ZFS rpool during boot

[Ubuntu QA Website]

This bug has been reported on the Ubuntu ISO testing tracker.

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

** Tags added: iso-testing

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

Title:
  Fails to import ZFS rpool during boot

Status in systemd package in Ubuntu:
  New

Bug description:
  Fresh install using 20220202 Daily ISO with ZFS + Encryption selected
  from the installer

  The system ends up in busybox after entering the unlock key.

  Here is a part of the logs captured from the screen, the complete log
  can be found as an attachement:

  find: /dev/zvol/: No such file or directory 
  /init: line 971: dirname: not found
  BusyBox v1.30.1 (Ubuntu 1:1.30.1-7ubuntu2) multi-call binary.

  Usage: basename FILE [SUFFIX]
  Strip directory path and SUFFIX from FILE 
  Please unlock disk keystore-:_

  Key load error: Failed to open key material file: No such file or
  directory

  Command: mount -o zfsutil -t zfs rpool/ROOT/ubuntu_ui69ph /root// Message: 
filesystem 'rpool/ROOT/ubuntu_ui69ph' can not be mounted: Permission denied 
  filesystem 'rpool/ROOT/ubuntu_ui69ph' can not be mounted: Permission denied 
  mount: mounting rpool/ROOT/ubuntu_u169ph on /root// failed: Permission denied 
Error: 1

  Failed to mount rpool/ROOT/ubuntu ui69ph on /root//.
  Manually mount the filesystem and exit.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1960460/+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 1787368] Re: Caja does not show previews of text files on Bionic and newer versions

[Ubuntu QA Website]

This bug has been reported on the Ubuntu ISO testing tracker.

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

** Tags added: iso-testing

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

Title:
  Caja does not show previews of text files on Bionic and newer versions

Status in MATE Desktop:
  New
Status in caja package in Ubuntu:
  Confirmed
Status in gtk+3.0 package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce:
  1. Install Ubuntu MATE 18.04 LTS (or upgrade from 16.04 LTS)
  2. Create text file somewhere (in home folder for example) with `echo text > 
~/file.txt`.
  3. Open Caja in home folder

  Expected results:
  * Caja shows preview (the contents) of `file.txt` in Icon view.

  Actual results:
  * Caja does not show preview of `file.txt`.

  
  Notes:
  1. all settings in Preview tab are set to *Local Only*
  2. this happens on clean user profile and/or after `dconf reset -f /` and 
`gsettings reset-recursively  org.mate.caja`
  3. Problem first seen on AskUbuntu ( https://askubuntu.com/q/1065825/66509 ).

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: caja 1.20.2-4ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-30.32-generic 4.15.18
  Uname: Linux 4.15.0-30-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Thu Aug 16 12:36:57 2018
  InstallationDate: Installed on 2018-04-26 (111 days ago)
  InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  SourcePackage: caja
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/mate-desktop/+bug/1787368/+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 1922414] Re: ssh-agent fails to start (has_option: command not found)

[Ubuntu QA Website]

This bug has been reported on the Ubuntu ISO testing tracker.

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

** Tags added: iso-testing

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

Title:
  ssh-agent fails to start (has_option: command not found)

Status in gdm3 package in Ubuntu:
  Fix Released
Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  I have been using ssh-agent for years and since I upgraded my system
  to Ubuntu 21.04/groovy, ssh-agent fails to start.

  Here is the error message:

  # journalctl | grep ssh-agent
  [...]
  Apr 02 20:16:32 vougeot /usr/libexec/gdm-x-session[3752]: 
/etc/X11/Xsession.d/90x11-common_ssh-agent: line 9: has_option: command not 
found

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: x11-common 1:7.7+22ubuntu1
  Uname: Linux 5.11.11-05-lowlatency x86_64
  ApportVersion: 2.20.11-0ubuntu61
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: KDE
  Date: Sat Apr  3 09:02:46 2021
  Dependencies: lsb-base 11.1.0ubuntu2
  DistUpgraded: Fresh install
  DistroCodename: hirsute
  DistroVariant: ubuntu
  DkmsStatus:
   tuxedo-keyboard, 3.0.4, 5.11.0-13-generic, x86_64: installed
   tuxedo-keyboard, 3.0.4, 5.11.0-13-lowlatency, x86_64: installed
   tuxedo-keyboard, 3.0.4, 5.11.11-05-lowlatency, x86_64: installed
  ExtraDebuggingInterest: No
  GraphicsCard:
   Intel Corporation TigerLake GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) 
(prog-if 00 [VGA controller])
 Subsystem: CLEVO/KAPOK Computer Iris Xe Graphics [1558:51a1]
  MachineType: TUXEDO TUXEDO InfinityBook S 15 Gen6
  PackageArchitecture: all
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.11-05-lowlatency 
root=/dev/mapper/MonVolume2-UbuntuRacine ro vsyscall=none security=apparmor 
quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/07/2020
  dmi.bios.release: 7.3
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 1.07.03RTR
  dmi.board.name: NS50MU
  dmi.board.vendor: TUXEDO
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.ec.firmware.release: 7.2
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr1.07.03RTR:bd09/07/2020:br7.3:efr7.2:svnTUXEDO:pnTUXEDOInfinityBookS15Gen6:pvrNotApplicable:rvnTUXEDO:rnNS50MU:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: TUXEDO InfinityBook S 15 Gen6
  dmi.product.sku: Not Applicable
  dmi.product.version: Not Applicable
  dmi.sys.vendor: TUXEDO
  version.compiz: compiz 1:0.9.14.1+20.10.20200813-0ubuntu4
  version.libdrm2: libdrm2 2.4.104-1build1
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-1
  version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.1-1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.10-3ubuntu5
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-2build1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1922414/+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 1955859] Re: ubuntu-core on jammy daily: apt-key has no access to /dev/null

[Ubuntu QA Website]

This bug has been reported on the Ubuntu ISO testing tracker.

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

** Tags added: iso-testing

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

Title:
  ubuntu-core on jammy daily: apt-key has no access to /dev/null

Status in apt package in Ubuntu:
  New

Bug description:
  Ubuntu Jammy Core - Smoke test fails.

  One of the issues that I believe may be the primary issue is that apt-
  key has no access to /dev/null.

  root@Joshua-PC:/# apt-get update
  Ign:1 http://archive.ubuntu.com/ubuntu jammy-updates InRelease
  Ign:2 http://security.ubuntu.com/ubuntu jammy-security InRelease
  Get:3 http://security.ubuntu.com/ubuntu jammy-security Release [89.8 kB]
  Get:4 http://security.ubuntu.com/ubuntu jammy-security Release.gpg [819 B]
  0% [Waiting for headers]/usr/bin/apt-key: 95: cannot create /dev/null: 
Permission denied
  /usr/bin/apt-key: 95: cannot create /dev/null: Permission denied
  /usr/bin/apt-key: 95: cannot create /dev/null: Permission denied
  E: gpgv, gpgv2 or gpgv1 required for verification, but neither seems installed
  Ign:4 http://security.ubuntu.com/ubuntu jammy-security Release.gpg
  Ign:5 http://archive.ubuntu.com/ubuntu jammy InRelease
 
  Get:6 http://archive.ubuntu.com/ubuntu jammy-updates Release [89.8 kB]
 
  Get:7 http://archive.ubuntu.com/ubuntu jammy-backports InRelease [90.7 kB]
 
  0% [Working]   13.8 kB/s 
0s/usr/bin/apt-key: 95: cannot create /dev/null: Permission denied
  /usr/bin/apt-key: 95: cannot create /dev/null: Permission denied
  /usr/bin/apt-key: 95: cannot create /dev/null: Permission denied
  E: gpgv, gpgv2 or gpgv1 required for verification, but neither seems installed
  Err:7 http://archive.ubuntu.com/ubuntu jammy-backports InRelease  
 
gpgv, gpgv2 or gpgv1 required for verification, but neither seems installed
  Get:8 http://archive.ubuntu.com/ubuntu jammy Release [269 kB] 
 
  Get:9 http://archive.ubuntu.com/ubuntu jammy-updates Release.gpg [819 B]  
 
  0% [Working]   13.8 kB/s 
6s/usr/bin/apt-key: 95: cannot create /dev/null: Permission denied
  /usr/bin/apt-key: 95: cannot create /dev/null: Permission denied
  /usr/bin/apt-key: 95: cannot create /dev/null: Permission denied
  E: gpgv, gpgv2 or gpgv1 required for verification, but neither seems installed
  Ign:9 http://archive.ubuntu.com/ubuntu jammy-updates Release.gpg  
 
  Get:10 http://archive.ubuntu.com/ubuntu jammy Release.gpg [819 B] 
 
  0% [Working]   13.8 kB/s 
6s/usr/bin/apt-key: 95: cannot create /dev/null: Permission denied
  /usr/bin/apt-key: 95: cannot create /dev/null: Permission denied
  /usr/bin/apt-key: 95: cannot create /dev/null: Permission denied
  E: gpgv, gpgv2 or gpgv1 required for verification, but neither seems installed
  Ign:10 http://archive.ubuntu.com/ubuntu jammy Release.gpg 
 
  Reading package lists... Done 
 
  W: GPG error: http://security.ubuntu.com/ubuntu jammy-security Release: gpgv, 
gpgv2 or gpgv1 required for verification, but neither seems installed
  E: The repository 'http://security.ubuntu.com/ubuntu jammy-security Release' 
is not signed.
  N: Updating from such a repository can't be done securely, and is therefore 
disabled by default.
  N: See apt-secure(8) manpage for repository creation and user configuration 
details.
  W: GPG error: http://archive.ubuntu.com/ubuntu jammy-backports InRelease: 
gpgv, gpgv2 or gpgv1 required for verification, but neither seems installed
  E: The repository 'http://archive.ubuntu.com/ubuntu jammy-backports 
InRelease' is not signed.
  N: Updating from such a repository can't be done securely, and is therefore 
disabled by default.
  N: See apt-secure(8) manpage for repository creation and user configuration 
details.
  W: GPG error: http://archive.ubuntu.com/ubuntu jammy-updates Release: gpgv, 
gpgv2 or gpgv1 required for verification, but neither seems installed
  E: The repository 'http://archive.ubuntu.com/ubuntu jammy-updates Release' is 
not signed.
  N: Updating from such a repository can't be done securely, and is therefore 
disabled by default.
  N: See apt-secure(8) manpage for repository creation and user configuration 
details.
  W: GPG error: http://archive.ubuntu.com/ubuntu jammy Release: gpgv, gpgv2 or 
gpgv1 required for verification, but neither seems installed
  E: The repository 'http://archive.ubuntu.com/ubuntu jammy Release' is not 
signed.
  N: Updating from such a repository can't be done securely, and is therefore 
disabled by default.
  N: See 

[Touch-packages] [Bug 1854383] Re: Extra window decorations are created on windows with client-side decorations.

[Ubuntu QA Website]

This bug has been reported on the Ubuntu ISO testing tracker.

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

** Tags added: iso-testing

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

Title:
  Extra window decorations are created on windows with client-side
  decorations.

Status in Ubuntu MATE:
  Confirmed
Status in gtk+3.0 package in Ubuntu:
  Confirmed
Status in marco package in Ubuntu:
  New

Bug description:
  Steps to reproduce after a minimal/full install of Ubuntu MATE:

  1. Start up a Gtk3 application with a header bar (tested with Gnome
  Software) or a browser (such as Firefox) without using a standard
  window title bar that saves the position and size of the window before
  it was closed.

  2. Maximize the application window, then close it without changing the
  window size

  3. Relaunch the application and resize/unmaximize it

  After this, dummy window decorations will be created around the
  window. This issue has been tested on a Dell XPS 9570 and using Gnome
  Boxes 3.34.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-mate/+bug/1854383/+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 1926256] Re: Pasted text in the terminal is always highlighted and selected

[Ubuntu QA Website]

This bug has been reported on the Ubuntu ISO testing tracker.

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

** Tags added: iso-testing

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

Title:
  Pasted text in the terminal is always highlighted and selected

Status in bash package in Ubuntu:
  Confirmed
Status in gnome-terminal package in Ubuntu:
  Invalid
Status in mate-terminal package in Ubuntu:
  Confirmed
Status in vte2.91 package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce:
  1. Have Ubuntu 21.04 installed
  2. Launch terminal
  3a. Execute some command, select this command to copy it, then paste command
  3b. Paste some command from clipboard to terminal

  Expected result:
  * pasted command is not highlighted and is not selected

  Actual result:
  * pasted command is selected and highlighted

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: mate-terminal 1.24.1-1
  ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
  Uname: Linux 5.11.0-16-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: MATE
  Date: Tue Apr 27 09:43:56 2021
  InstallationDate: Installed on 2021-04-23 (3 days ago)
  InstallationMedia: Ubuntu-MATE 21.04 "Hirsute Hippo" - Release amd64 
(20210420)
  SourcePackage: mate-terminal
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1926256/+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 1955135] Re: multiple issues with /etc/X11/Xsession.d/ - "has_option: command not found"

[Ubuntu QA Website]

This bug has been reported on the Ubuntu ISO testing tracker.

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

** Tags added: iso-testing

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

Title:
  multiple issues with /etc/X11/Xsession.d/ - "has_option: command not
  found"

Status in dbus package in Ubuntu:
  New
Status in xorg package in Ubuntu:
  New

Bug description:
  Steps to reproduce:
  1. Boot 20211217 Ubuntu MATE daily ISO
  2. Open ~/.xsession-errors

  Expected results:
  * no errors and warnings 

  Actual results:
  * there are two errors about xorg:

  /etc/X11/Xsession.d/30x11-common_xresources: line 16: has_option: command not 
found
  /etc/X11/Xsession.d/90x11-common_ssh-agent: line 9: has_option: command not 
found

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: x11-common 1:7.7+23ubuntu1
  ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
  Uname: Linux 5.13.0-19-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu74
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CasperVersion: 1.465
  CompositorRunning: None
  CurrentDesktop: MATE
  Date: Fri Dec 17 14:22:15 2021
  Dependencies: lsb-base 11.1.0ubuntu3
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation GF108M [GeForce GT 425M] [10de:0df0] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Sony Corporation GF108M [GeForce GT 425M] [104d:907a]
  LiveMediaBuild: Ubuntu-MATE 22.04 LTS "Jammy Jellyfish" - Alpha amd64 
(20211217)
  MachineType: Sony Corporation VPCF13Z1R
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz 
file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash ---
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/20/2010
  dmi.bios.release: 1.90
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: R0190Y9
  dmi.board.asset.tag: N/A
  dmi.board.name: VAIO
  dmi.board.vendor: Sony Corporation
  dmi.board.version: N/A
  dmi.chassis.asset.tag: N/A
  dmi.chassis.type: 10
  dmi.chassis.vendor: Sony Corporation
  dmi.chassis.version: N/A
  dmi.ec.firmware.release: 1.90
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrR0190Y9:bd10/20/2010:br1.90:efr1.90:svnSonyCorporation:pnVPCF13Z1R:pvrC606GZYK:skuN/A:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A:
  dmi.product.family: VAIO
  dmi.product.name: VPCF13Z1R
  dmi.product.sku: N/A
  dmi.product.version: C606GZYK
  dmi.sys.vendor: Sony Corporation
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.107-8ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-1ubuntu2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-1build1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1955135/+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 1955136] Re: /etc/X11/Xsession.d/75dbus_dbus-launch: line 9: has_option: command not found

[Ubuntu QA Website]

This bug has been reported on the Ubuntu ISO testing tracker.

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

** Tags added: iso-testing

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

Title:
  /etc/X11/Xsession.d/75dbus_dbus-launch: line 9: has_option: command
  not found

Status in dbus package in Ubuntu:
  New

Bug description:
  teps to reproduce:
  1. Boot 20211217 Ubuntu MATE daily ISO
  2. Open ~/.xsession-errors

  Expected results:
  * no errors and warnings

  Actual results:
  * there are two errors about dbus:

  /etc/X11/Xsession.d/75dbus_dbus-launch: line 9: has_option: command
  not found

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: dbus-x11 1.12.20-2ubuntu2
  ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
  Uname: Linux 5.13.0-19-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu74
  Architecture: amd64
  CasperMD5CheckResult: pass
  CasperVersion: 1.465
  CurrentDesktop: MATE
  Date: Fri Dec 17 14:28:01 2021
  LiveMediaBuild: Ubuntu-MATE 22.04 LTS "Jammy Jellyfish" - Alpha amd64 
(20211217)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: dbus
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1955136/+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 1953507] Re: jammy live - on adjusting display config; one display is unsuable blocky-mess

[Ubuntu QA Website]

This bug has been reported on the Ubuntu ISO testing tracker.

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

** Tags added: iso-testing

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

Title:
  jammy live - on adjusting display config; one display is unsuable
  blocky-mess

Status in xorg package in Ubuntu:
  New

Bug description:
  ubuntu jammy daily (canary build) live test on 
  - dell optiplex 960

  (this is my primary machine; so is normally used for entry of data &
  not doing the QA-testing).

  on adjusting the displays to match my setup (six displays; two high &
  three across; this box uses two in the middle with middle on top row &
  middle on bottom row)..  the top display is still useable, but the
  bottom is not.  This boxes are not perfectly aligned as not all my
  displays are the exact same size; so top display is slightly to right
  of bottom display

  the bottom resembles a digital TV with bad signal, mostly blocky &
  parts of it flashing (very quickly).  it doesn't match the attached
  picture (as viewable on this box anyway.. my top display; which was
  LEFT prior to alignment is perfectly readable).

  ** actual

  my top display is usable, bottom is not (blocky warped picture)

  ** expected

  on adjust displays to match my config; both displays remain usable &
  readable.

  ** notes

  likely related to graphics card & not GNOME.   If I recall correctly;
  this box has an older video card used as it had 2x DVI connections my
  screens use.

  My usual install on this box is jammy; but I usually use LXQt/Lubuntu
  and I don't experience issues.. I also have installed Xubuntu/Xfce &
  Ubuntu/GNOME so can test the installed OS (where I don't believe I
  have issue), but my install is somewhat old (artful install upgraded
  every six months ~30-36 hours after each release) thus is likely
  heavily modified.

  ** Picture comments

  My top display is ~perfect (vertical white bar to left of ubuntu-dock-
  items I'd not expect, but the color-blocks to the left of the
  'install/firefox/thunderbird/files` is NOT visible; only a vertical
  WHITE bar a few pixels wide to left of the dock appears' rest of top
  display is perfect.

  My bottom display is nothing like picture; it's unusable.  A mixture
  of black/white boxes with red/purple bits which would be the picture
  warped into blocky-components.  When I type, I get reactions on this
  display with the picture changing (mostly the black & white portions
  which flash, the red/purple bits which are warped indri picture appear
  to remain static).

  My phone/camera isn't working, but I've taken a photograph. I didn't
  anticipate issues in this QA-test (it's past 1AM now) otherwise I'd
  not have run this QA-test now.

  ** further comments

  this is likely a duplicate... I experience this type of reaction on
  other boxes; likely radeon related but I've yet to look & can't even
  remember which video card exists in this box (I don't experience
  issues with the display configuration of the box with identical card
  to this, but it relates to display setup/config... my other box with
  this card is landscape+portrait I believe and doesn't have one display
  above the other; ie. d780; I get these issues when one display is
  above the other - and only with single orientation (swap top/bottom
  and issues don't exist))

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu1
  ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
  Uname: Linux 5.13.0-19-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu74
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CasperVersion: 1.465+canary3.3
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Dec  7 13:52:56 2021
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Cedar [Radeon HD 5000/6000/7350/8350 
Series] [1002:68f9] (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Radeon HD 6350 [103c:2126]
  LiveMediaBuild: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211206)
  MachineType: Dell Inc. OptiPlex 960
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz 
layerfs-path=minimal.standard.live.squashfs maybe-ubiquity --- quiet splash
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/05/2011
  dmi.bios.release: 10.0
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A14
  

[Touch-packages] [Bug 1952977] Re: Invalid security certificates everywhere in KDE

[Ubuntu QA Website]

This bug has been reported on the Ubuntu ISO testing tracker.

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

** Tags added: iso-testing

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

Title:
  Invalid security certificates everywhere in KDE

Status in qtbase-opensource-src package in Ubuntu:
  Fix Committed

Bug description:
  Upgrading 5.15.2+dfsg-13 to 5.15.2+dfsg-14 results in security cert.
  errors like this  https://imgur.com/a/7Kyt8U6

  This causes problems for discover, downloading widgets, using the
  weather widget, using the kde browser integrations, downloading tabs
  for ksysguard, etc.

  you can get console errors like this

  org.kde.plasma.discover: Trying to open unexisting file 
QUrl("file:///home/chad/%25F")
  adding empty sources model QStandardItemModel(0x5646c6ed2e80)
  qt.network.ssl: QSslSocket: cannot resolve SSL_CTX_load_verify_dir
  org.kde.plasma.libdiscover: Couldn't find a category for  "fwupd-backend"
  qt.network.ssl: QSslSocket: cannot resolve SSL_CTX_load_verify_dir
  
file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/private/PrivateActionToolButton.qml:74:5:
 QML Binding: Binding loop detected for property "value"
  qt.network.ssl: QSslSocket: cannot call unresolved function 
SSL_CTX_load_verify_dir
  qt.network.ssl: An error encountered while to set root certificates location: 
""
  qt.network.ssl: QSslSocket: cannot call unresolved function 
SSL_CTX_load_verify_dir
  qt.network.ssl: An error encountered while to set root certificates location: 
""
  qt.network.ssl: QSslSocket: cannot call unresolved function 
SSL_CTX_load_verify_dir
  qt.network.ssl: An error encountered while to set root certificates location: 
""
  qt.network.ssl: QSslSocket: cannot call unresolved function 
SSL_CTX_load_verify_dir
  qt.network.ssl: An error encountered while to set root certificates location: 
""
  qt.network.ssl: QSslSocket: cannot call unresolved function 
SSL_CTX_load_verify_dir
  qt.network.ssl: An error encountered while to set root certificates location: 
""


  
  qt.network.ssl: QSslSocket: cannot resolve EVP_PKEY_base_id qt.network.ssl: 
QSslSocket: cannot resolve SSL_get_peer_certificate

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: libqt5network5 5.15.2+dfsg-14
  Uname: Linux 5.15.5-051505-generic x86_64
  ApportVersion: 2.20.11-0ubuntu73
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: KDE
  Date: Wed Dec  1 21:43:08 2021
  InstallationDate: Installed on 2021-11-26 (5 days ago)
  InstallationMedia: Kubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 
(20211126)
  SourcePackage: qtbase-opensource-src
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1952977/+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 1951214] Re: ubuntu-bug isn't opening firefox (snap) on jammy, instead gedit gets data

[Ubuntu QA Website]

This bug has been reported on the Ubuntu ISO testing tracker.

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

** Tags added: iso-testing

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

Title:
  ubuntu-bug isn't opening firefox (snap) on jammy, instead gedit gets
  data

Status in apport package in Ubuntu:
  New

Bug description:
  This has been reported before on Ubuntu Community Hub, but I want/need
  a bug report filed on launchpad to report/track on iso.qa.ubuntu.com

  On a `ubuntu-bug` or apport opening up a bug report; a gedit window
  opens with

  ---
  
  
OpenID transaction in progress
  
  
  https://login.launchpad.net/+openid; method="post" 
accept-charset="UTF-8" enctype="application/x-www-form-urlencoded">http://openid.net/extensions/sreg/1.1"/>https://launchpad.net/+openid-callback?starting_url=https%3A%2F%2Fbugs.launchpad.net%2Fsubiquity%2F%2Bfilebug%2Ff55a6274-4767-11ec-a1ce-d485646cd9a4%3Ffield.title%3Dinstall%2Bfailed%2Bcrashed%2Bwith%2BCalledProcessErrorjanrain_nonce=2021-11-17T05%3A34%3A05Zo24b46"/>https://launchpad.net/"/>http://specs.openid.net/auth/2.0/identifier_select"/>http://specs.openid.net/auth/2.0"/>http://specs.openid.net/auth/2.0/identifier_select"/>
  
  var elements = document.forms[0].elements;
  for (var i = 0; i < elements.length; i++) {
elements[i].style.display = "none";
  }
  
  
  
  ---

  this is detail that belongs in `firefox` and not `gedit` ... ie. bug.

  This issue is NOT new.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: apport 2.20.11-0ubuntu73
  ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
  Uname: Linux 5.13.0-19-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportLog:
   ERROR: apport (pid 2820) Wed Nov 17 16:33:33 2021: called for pid 2593, 
signal 11, core limit 0, dump mode 1
   ERROR: apport (pid 2820) Wed Nov 17 16:33:33 2021: executable: 
/snap/ubuntu-desktop-installer/171/bin/ubuntu_desktop_installer (command line 
"/snap/ubuntu-desktop-installer/171/bin/ubuntu_desktop_installer")
   ERROR: apport (pid 2820) Wed Nov 17 16:33:33 2021: executable does not 
belong to a package, ignoring
  ApportVersion: 2.20.11-0ubuntu73
  Architecture: amd64
  CasperMD5CheckResult: pass
  CasperVersion: 1.465+canary3.3
  CrashReports:
   644:0:0:30:2021-11-17 16:33:08.496906043 +1100:2021-11-17 16:33:08.496906043 
+1100:/var/crash/1637127188.494807005.install_fail.meta
   640:0:0:726809:2021-11-17 16:33:41.277731657 +1100:2021-11-17 
16:33:42.277731657 +1100:/var/crash/1637127188.494807005.install_fail.crash
   644:0:0:0:2021-11-17 16:33:45.953817607 +1100:2021-11-17 16:33:45.953817607 
+1100:/var/crash/1637127188.494807005.install_fail.upload
   600:116:123:5:2021-11-17 16:48:24.898416884 +1100:2021-11-17 
16:33:45.953817607 +1100:/var/crash/1637127188.494807005.install_fail.uploaded
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Nov 17 16:52:32 2021
  LiveMediaBuild: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (2026)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1951214/+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 1943318] Re: systemd-shutdown[1]: Failed to finalize file systems, ignoring.

[Ubuntu QA Website]

This bug has been reported on the Ubuntu ISO testing tracker.

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

** Tags added: iso-testing

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

Title:
  systemd-shutdown[1]: Failed to finalize file systems, ignoring.

Status in systemd package in Ubuntu:
  New

Bug description:
  Description:  Ubuntu Impish Indri (development branch)
  Release:  21.10

  Impish Indri 20210911 build, erase disk and install, packages updated
  after installation

  Installation failed at step 15: bug #1925314 "no eject media message
  after install".

  System restarted successfully. Changed downloading updates to main
  server and was prompted to update a few packages. After updates
  finished, pressed "Restart now". This is the result.

  Updated packages:
  Start-Date: 2021-09-11  15:56:40
  Commandline: aptdaemon role='role-commit-packages' sender=':1.83'
  Upgrade: libedata-book-1.2-26:amd64 (3.40.2-1build1, 3.40.4-1), 
libebook-1.2-20:amd64 (3.40.2-1build1, 3.40.4-1), libgomp1:amd64 
(11.2.0-3ubuntu1, 11.2.0-5ubuntu1), libecal-2.0-1:amd64 (3.40.2-1build1, 
3.40.4-1), libedataserver-1.2-26:amd64 (3.40.2-1build1, 3.40.4-1), 
evolution-data-server:amd64 (3.40.2-1build1, 3.40.4-1), libgcr-base-3-1:amd64 
(3.38.1-2, 3.40.0-3), evolution-data-server-common:amd64 (3.40.2-1build1, 
3.40.4-1), open-vm-tools-desktop:amd64 (2:11.2.5-2ubuntu1, 2:11.3.0-2), 
gcr:amd64 (3.38.1-2, 3.40.0-3), libgcr-ui-3-1:amd64 (3.38.1-2, 3.40.0-3), 
libcamel-1.2-62:amd64 (3.40.2-1build1, 3.40.4-1), libxmlsec1:amd64 (1.2.31-1, 
1.2.32-1), libebook-contacts-1.2-3:amd64 (3.40.2-1build1, 3.40.4-1), 
libedataserverui-1.2-3:amd64 (3.40.2-1build1, 3.40.4-1), open-vm-tools:amd64 
(2:11.2.5-2ubuntu1, 2:11.3.0-2), libgupnp-av-1.0-2:amd64 (0.12.11-2, 
0.12.11-3), cpp-11:amd64 (11.2.0-3ubuntu1, 11.2.0-5ubuntu1), 
printer-driver-pnm2ppa:amd64 (1.13+nondbs-0ubuntu7, 1.13+nondbs-0ubuntu8), 
libedata-cal-2.0-1:amd64 (3.40.2-1build1, 3.40.4-1), gcc-11-base:amd64 
(11.2.0-3ubuntu1, 11.2.0-5ubuntu1), groff-base:amd64 (1.22.4-6, 1.22.4-7), 
libgck-1-0:amd64 (3.38.1-2, 3.40.0-3), gir1.2-gck-1:amd64 (3.38.1-2, 3.40.0-3), 
libstdc++6:amd64 (11.2.0-3ubuntu1, 11.2.0-5ubuntu1), libebackend-1.2-10:amd64 
(3.40.2-1build1, 3.40.4-1), libxmlsec1-openssl:amd64 (1.2.31-1, 1.2.32-1), 
gir1.2-gcr-3:amd64 (3.38.1-2, 3.40.0-3), libgcc-s1:amd64 (11.2.0-3ubuntu1, 
11.2.0-5ubuntu1)
  End-Date: 2021-09-11  15:57:17

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: systemd 248.3-1ubuntu3
  ProcVersionSignature: Ubuntu 5.13.0-14.14-generic 5.13.1
  Uname: Linux 5.13.0-14-generic x86_64
  ApportVersion: 2.20.11-0ubuntu68
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Sep 11 16:07:46 2021
  InstallationDate: Installed on 2021-09-11 (0 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210910)
  Lsusb:
   Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet
   Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Lsusb-t:
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ohci-pci/12p, 12M
   |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M
  MachineType: innotek GmbH VirtualBox
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-14-generic 
root=UUID=54dc5a9f-dd8b-435f-a346-0647390276de ro quiet splash
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:sku:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.family: Virtual Machine
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1943318/+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 1942685] Re: pulseaudio crashed with SIGSEGV in _IceTransClose()

[Ubuntu QA Website]

This bug has been reported on the Ubuntu ISO testing tracker.

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

** Tags added: iso-testing

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

Title:
  pulseaudio crashed with SIGSEGV in _IceTransClose()

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Installing Xubuntu Impish daily ISO 04092021

  After install I rebooted - applied updates and then rebooted again-

  the errors (pulseaudio crashed with SIGSEGV in _IceTransClose() )
  occurred after logging in.

  ProblemType: Crash
  DistroRelease: Ubuntu 21.10
  Package: pulseaudio 1:15.0+dfsg1-1ubuntu2
  ProcVersionSignature: Ubuntu 5.13.0-14.14-generic 5.13.1
  Uname: Linux 5.13.0-14-generic x86_64
  ApportVersion: 2.20.11-0ubuntu68
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  kx  847 F pulseaudio
  CasperMD5CheckResult: pass
  Date: Sat Sep  4 16:43:45 2021
  ExecutablePath: /usr/bin/pulseaudio
  InstallationDate: Installed on 2021-09-04 (0 days ago)
  InstallationMedia: Xubuntu 21.10 "Impish Indri" - Alpha amd64 (20210904)
  ProcCmdline: /usr/bin/pulseaudio --daemonize=no --log-target=journal
  Signal: 11
  SourcePackage: pulseaudio
  StacktraceTop:
   _IceTransClose () from /lib/x86_64-linux-gnu/libICE.so.6
   _IceFreeConnection () from /lib/x86_64-linux-gnu/libICE.so.6
   IceCloseConnection () from /lib/x86_64-linux-gnu/libICE.so.6
   SmcCloseConnection () from /lib/x86_64-linux-gnu/libSM.so.6
   ?? () from /usr/lib/pulse-15.0+dfsg1/modules/module-x11-xsmp.so
  Title: pulseaudio crashed with SIGSEGV in _IceTransClose()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  dmi.bios.date: 12/23/2020
  dmi.bios.release: 1.51
  dmi.bios.vendor: LENOVO
  dmi.bios.version: DKCN51WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40700 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo V14-IIL
  dmi.ec.firmware.release: 1.51
  dmi.modalias: 
dmi:bvnLENOVO:bvrDKCN51WW:bd12/23/2020:br1.51:efr1.51:svnLENOVO:pn82C4:pvrLenovoV14-IIL:skuLENOVO_MT_82C4_BU_idea_FM_V14-IIL:rvnLENOVO:rnLNVNB161216:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrLenovoV14-IIL:
  dmi.product.family: V14-IIL
  dmi.product.name: 82C4
  dmi.product.sku: LENOVO_MT_82C4_BU_idea_FM_V14-IIL
  dmi.product.version: Lenovo V14-IIL
  dmi.sys.vendor: LENOVO
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1942685/+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 1942031] Re: gnome-shell crashed with SIGSEGV in _XSend() from XQueryExtension() from InitDisplayInfoEntry() from __glXLookupDisplay() from CommonMakeCurrent()

[Ubuntu QA Website]

This bug has been reported on the Ubuntu ISO testing tracker.

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

** Tags added: iso-testing

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

Title:
  gnome-shell crashed with SIGSEGV in _XSend() from XQueryExtension()
  from InitDisplayInfoEntry() from __glXLookupDisplay() from
  CommonMakeCurrent()

Status in gnome-shell package in Ubuntu:
  Confirmed
Status in libx11 package in Ubuntu:
  Confirmed

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1942031/+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 1920813] Re: /etc/pam.d/lightdm and /etc/pam.d/lightdm-autologin should have uncommented "session required pam_loginuid.so" for compatibility with user applications

[Ubuntu QA Website]

This bug has been reported on the Ubuntu ISO testing tracker.

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

** Tags added: iso-testing

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

Title:
  /etc/pam.d/lightdm and /etc/pam.d/lightdm-autologin should have
  uncommented "session requiredpam_loginuid.so" for
  compatibility with user applications

Status in Ubuntu MATE:
  New
Status in lightdm package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce:
  1. Install Ubuntu MATE 21.04
  2. Launch MATE Terminal
  3. Execute `cat /proc/self/loginuid`

  Expected results:
  * above command returned 1000

  Actual results:
  * above command returned 4294967295

  
  Remediation:
  * edit /etc/pam.d/lightdm and /etc/pam.d/lightdm-autologin to uncomment

  session requiredpam_loginuid.so

  for compatibility with user applications.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: lightdm 1.30.0-0ubuntu3.1
  ProcVersionSignature: Ubuntu 5.11.0-11.12-generic 5.11.0
  Uname: Linux 5.11.0-11-generic x86_64
  ApportVersion: 2.20.11-0ubuntu60
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Mon Mar 22 22:41:05 2021
  InstallationDate: Installed on 2021-03-21 (1 days ago)
  InstallationMedia: Ubuntu-MATE 21.04 "Hirsute Hippo" - Alpha amd64 (20210321)
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-mate/+bug/1920813/+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 1930945] Re: ubuntu desktop - changing display configuration lost wallpaper (trap messages filled dmesg)

[Ubuntu QA Website]

This bug has been reported on the Ubuntu ISO testing tracker.

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

** Tags added: iso-testing

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

Title:
  ubuntu desktop - changing display configuration lost wallpaper (trap
  messages filled dmesg)

Status in ubuntu-meta package in Ubuntu:
  New

Bug description:
  Ubuntu Desktop Impish daily test on
  - - hp dc7700 (c2d-e6320, 5gb, nvidia quadro nvs 290)

  Changing display positions in settings.  I have two monitors, one
  above the other (so not the default).

  I made change and it looked okay so I said keep. I noticed I was wrong
  having TOP/BOTTOM displays the wrong way (detected via mouse movements
  between displays) so I made another change of the TOP/BOTTOM displays
  in "DISPLAYS" of GNOME settings clicked apply again & keep...

  ** Expected Results

  On changing display orientation I expect wallpaper to be redrawn, or
  remain on screen

  ** Actual Results

  I now have BLUE background on both displays.

  (this was soon changing.. but that didn't occur until I tried to
  change wallpapers...)

  /var/crash is empty... operation appears normal; I lost background.
  lots of TRAP messages though fill `dmesg`

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: ubuntu-desktop 1.469
  ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
  Uname: Linux 5.11.0-16-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu67
  Architecture: amd64
  CasperMD5CheckResult: pass
  CasperVersion: 1.461
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jun  5 03:01:52 2021
  LiveMediaBuild: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210604)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-meta
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1930945/+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 1926062] Re: [hirsute/impish] Can't turn bluetooth on again after turning it off

[Ubuntu QA Website]

This bug has been reported on the Ubuntu ISO testing tracker.

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

** Tags added: iso-testing

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

Title:
  [hirsute/impish] Can't turn bluetooth on again after turning it off

Status in bluez package in Ubuntu:
  Confirmed
Status in gnome-control-center package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When ever i Turn on my system or restart bluetooth is open any it
  connects to any device. But when i turn off bluetooth and try to turn
  it on again. it neither turns on nor scans/connects to any device.
  This is happening since I updated my system to ubuntu 21.04 LTS

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: bluetooth (not installed)
  ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
  Uname: Linux 5.11.0-16-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 25 15:09:23 2021
  InstallationDate: Installed on 2020-12-15 (130 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: LENOVO 80TR
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic 
root=UUID=7c507bd4-c66c-4233-a64e-804f6df5412b ro quiet splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: Upgraded to hirsute on 2021-04-22 (2 days ago)
  dmi.bios.date: 07/31/2017
  dmi.bios.release: 1.29
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 3UCN29WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Nano 5B1
  dmi.board.vendor: LENOVO
  dmi.board.version: No DPK
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 110-15AST
  dmi.ec.firmware.release: 1.29
  dmi.modalias: 
dmi:bvnLENOVO:bvr3UCN29WW:bd07/31/2017:br1.29:efr1.29:svnLENOVO:pn80TR:pvrLenovoideapad110-15AST:rvnLENOVO:rnNano5B1:rvrNoDPK:cvnLENOVO:ct10:cvrLenovoideapad110-15AST:
  dmi.product.family: IDEAPAD
  dmi.product.name: 80TR
  dmi.product.sku: LENOVO_MT_80TR_BU_idea_FM_Lenovo ideapad 110-15AST
  dmi.product.version: Lenovo ideapad 110-15AST
  dmi.sys.vendor: LENOVO
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: C8:3D:D4:84:E0:06  ACL MTU: 820:8  SCO MTU: 255:16
DOWN 
RX bytes:744804 acl:76 sco:0 events:105989 errors:0
TX bytes:51871528 acl:113157 sco:0 commands:192 errors:0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1926062/+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 1930447] Re: Unable to turn on bluetooth

[Ubuntu QA Website]

This bug has been reported on the Ubuntu ISO testing tracker.

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

** Tags added: iso-testing

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

Title:
  Unable to turn on bluetooth

Status in bluez package in Ubuntu:
  New

Bug description:
  Testing Ubuntu Impish daily ISO 01-06-2021 0n QA tracking site -

  After successful install go to settings "Bluetooth" and select the on
  tab in upper right hand corner and nothing happens.

  This maybe related to bug # 1928924
  https://bugs.launchpad.net/ubuntu/+source/bluedevil/+bug/1928924

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: bluez 5.58-0ubuntu1
  ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
  Uname: Linux 5.11.0-16-generic x86_64
  ApportVersion: 2.20.11-0ubuntu67
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jun  1 16:30:07 2021
  InstallationDate: Installed on 2021-06-01 (0 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210601)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: LENOVO 82C4
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic 
root=UUID=efd131f1-9709-400b-9f5d-d72be1df3885 ro quiet splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/23/2020
  dmi.bios.release: 1.51
  dmi.bios.vendor: LENOVO
  dmi.bios.version: DKCN51WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40700 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo V14-IIL
  dmi.ec.firmware.release: 1.51
  dmi.modalias: 
dmi:bvnLENOVO:bvrDKCN51WW:bd12/23/2020:br1.51:efr1.51:svnLENOVO:pn82C4:pvrLenovoV14-IIL:rvnLENOVO:rnLNVNB161216:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrLenovoV14-IIL:
  dmi.product.family: V14-IIL
  dmi.product.name: 82C4
  dmi.product.sku: LENOVO_MT_82C4_BU_idea_FM_V14-IIL
  dmi.product.version: Lenovo V14-IIL
  dmi.sys.vendor: LENOVO
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 28:39:26:D5:7D:8E  ACL MTU: 1021:6  SCO MTU: 255:12
DOWN 
RX bytes:1682 acl:0 sco:0 events:183 errors:0
TX bytes:36490 acl:0 sco:0 commands:183 errors:0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1930447/+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 1925344] Re: Session not started after reboot (black screen) - requires switching tty back and forth

[Ubuntu QA Website]

This bug has been reported on the Ubuntu ISO testing tracker.

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

** Tags added: iso-testing

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

Title:
  Session not started after reboot (black screen) - requires switching
  tty back and forth

Status in nvidia-graphics-drivers-460 package in Ubuntu:
  New
Status in nvidia-prime package in Ubuntu:
  New
Status in xorg package in Ubuntu:
  New

Bug description:
  After installation, the first boot works as expected - the system
  boots into a graphical shell login screen. However all subsequent
  reboots end up with a black screen with a blinking cursor in the top-
  left corner of the screen. To get to the login screen, one has to
  switch to a different tty (like tty2 with ctrl+alt+f2) and then to
  tty1.

  Running `prime-select query` shows `nvidia`.

  Interesting enough, when I change the nvidia-prime settings at least
  once, like to on-demand via `prime-select on-demand` - then everything
  starts working as expected. Even when I switch back to `nvidia`.

  Not sure which package I should fill this under.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: xserver-xorg 1:7.7+22ubuntu1
  ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
  Uname: Linux 5.11.0-16-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/capabilities/gpu0'
  .proc.driver.nvidia.capabilities.mig: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/capabilities/mig'
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .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  460.67  Thu Mar 11 00:11:45 
UTC 2021
   GCC version:
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr 21 15:20:15 2021
  DistUpgraded: Fresh install
  DistroCodename: hirsute
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation CometLake-H GT2 [UHD Graphics] [8086:9bc4] (rev 05) 
(prog-if 00 [VGA controller])
 Subsystem: Dell UHD Graphics [1028:09e1]
   NVIDIA Corporation TU116M [GeForce GTX 1660 Ti Mobile] [10de:2191] (rev a1) 
(prog-if 00 [VGA controller])
 Subsystem: Dell TU116M [GeForce GTX 1660 Ti Mobile] [1028:09e1]
  InstallationDate: Installed on 2021-04-21 (0 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  MachineType: Dell Inc. G3 3500
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pl_PL.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic 
root=UUID=5b38428b-60e8-4741-8b7f-0e60094a80f7 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/04/2020
  dmi.bios.release: 1.7
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.7.1
  dmi.board.name: 06ND9G
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.7.1:bd12/04/2020:br1.7:svnDellInc.:pnG33500:pvr:rvnDellInc.:rn06ND9G:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: GSeries
  dmi.product.name: G3 3500
  dmi.product.sku: 09E1
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.104-1build1
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-2
  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:1.20.11-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-460/+bug/1925344/+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 1925265] Re: Fresh install of hirsute-preinstalled-desktop-arm64+raspi has packages to autoremove

[Ubuntu QA Website]

This bug has been reported on the Ubuntu ISO testing tracker.

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

** Tags added: iso-testing

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

Title:
  Fresh install of hirsute-preinstalled-desktop-arm64+raspi has packages
  to autoremove

Status in ubuntu-meta package in Ubuntu:
  New

Bug description:
  Immediately after installing hirsute-preinstalled-desktop-arm64+raspi
  on a Raspberry Pi I noticed that there were packages available for
  autoremoval.

  bdmurray@bdmurray-desktop:~$ sudo apt autoremove
  [sudo] password for bdmurray:
  Reading package lists... Done
  Building dependency tree... Done
  Reading state information... Done
  The following packages will be REMOVED:
cryptsetup-bin dctrl-tools dmeventd dmraid dpkg-repack efibootmgr 
gir1.2-timezonemap-1.0 gir1.2-xkl-1.0 grub-common grub-efi-arm64
grub-efi-arm64-bin grub-efi-arm64-signed grub2-common kpartx kpartx-boot 
libdebian-installer4 libdevmapper-event1.02.1
libdmraid1.0.0.rc16 liblvm2cmd2.03 libtimezonemap-data libtimezonemap1 lvm2 
os-prober python3-icu python3-pam rdate
thin-provisioning-tools
  0 upgraded, 0 newly installed, 27 to remove and 0 not upgraded.
  After this operation, 45.5 MB disk space will be freed.
  Do you want to continue? [Y/n] n
  Abort.

  It seems to me the installation process should run an autoremove at
  the end.

  bdmurray@bdmurray-desktop:~$ cat /var/log/installer/version 
  ubiquity 21.04.19

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1925265/+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 1920665] Re: Ubiquity crash on try/install and from live session with "malloc(): unaligned tcache chunk detected"

[Ubuntu QA Website]

This bug has been reported on the Ubuntu ISO testing tracker.

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

** Tags added: iso-testing

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

Title:
  Ubiquity crash on try/install and from live session with "malloc():
  unaligned tcache chunk detected"

Status in mesa package in Ubuntu:
  New
Status in ubiquity package in Ubuntu:
  New
Status in mesa source package in Hirsute:
  New
Status in ubiquity source package in Hirsute:
  New

Bug description:
  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: ubiquity 21.04.11
  ProcVersionSignature: Ubuntu 5.11.0-11.12-generic 5.11.0
  Uname: Linux 5.11.0-11-generic x86_64
  ApportVersion: 2.20.11-0ubuntu60
  Architecture: amd64
  CasperMD5CheckResult: pass
  CasperVersion: 1.460
  CurrentDesktop: KDE
  Date: Sun Mar 21 11:53:44 2021
  InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/kubuntu.seed 
maybe-ubiquity quiet splash ---
  LiveMediaBuild: Kubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20210321)
  SourcePackage: ubiquity
  UpgradeStatus: No upgrade log present (probably fresh install)

  Since approximately 16/03/2021 ubiquity from maybe-ubiquity (try
  install screen) and from the live session is crashing on launch or
  shortly after.

  An example /var/log/installer/debug log from a session where both
  crashes were triggered is below.

   /var/log/installer/debug 

  Ubiquity 21.04.11
  TEXT If more than one person will use this computer, you can set up 
multiple accounts after installation.
  TEXT Enter the same password twice, so that it can be checked for 
typing errors.
  TEXT The name it uses when it talks to other computers.
  TEXT Enter the same password twice, so that it can be checked for 
typing errors.
  TEXT Enter the same password twice, so that it can be checked for 
typing errors.
  TEXT If more than one person will use this computer, you can set up 
multiple accounts after installation.
  TEXT Enter the same password twice, so that it can be checked for 
typing errors.
  TEXT The name it uses when it talks to other computers.
  QSocketNotifier: Invalid socket 17 and type 'Read', disabling...
  QSocketNotifier: Invalid socket 17 and type 'Write', disabling...
  QSocketNotifier: Invalid socket 17 and type 'Exception', disabling...
  Your console font configuration will be updated the next time your system
  boots. If you want to update it now, run 'setupcon' from a virtual console.
  update-initramfs is disabled since running on read-only media
  debconf: DbDriver "passwords" warning: could not open 
/var/cache/debconf/passwords.dat: Permission denied
  munmap_chunk(): invalid pointer
  Ubiquity 21.04.11
  QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu'
  QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu'
  QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu'
  TEXT If more than one person will use this computer, you can set up 
multiple accounts after installation.
  TEXT Enter the same password twice, so that it can be checked for 
typing errors.
  TEXT The name it uses when it talks to other computers.
  TEXT Enter the same password twice, so that it can be checked for 
typing errors.
  malloc(): unaligned tcache chunk detected

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1920665/+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 1795278] Re: software-properties-{qt, kde} attempts to use KUrl but it doesn't exist

[Ubuntu QA Website]

This bug has been reported on the Ubuntu ISO testing tracker.

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

** Tags added: iso-testing

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

Title:
  software-properties-{qt,kde} attempts to use KUrl but it doesn't exist

Status in software-properties package in Ubuntu:
  Triaged

Bug description:
  Release: Kubuntu 18.04
  Version: 0.96.24.32.1

  When clicking the "Import Key" button in the "Authentication" section
  of the panel it throws this error:

  Traceback (most recent call last):
File 
"/usr/lib/python3/dist-packages/softwareproperties/kde/SoftwarePropertiesKDE.py",
 line 667, in add_key_clicked
  url = KUrl.fromPath(home)
  NameError: name 'KUrl' is not defined

  While this doesn't crash the program it causes nothing to happen when
  clicking the button. Running the program in a terminal reveals the
  error being printed to stderr.

  After debugging it appears KUrl doesn't exist anywhere and I'm not
  sure if's a python module that has changed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1795278/+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 3312] Re: Ubuntu nm package lacking vpn support

[Ubuntu QA Website]

This bug has been reported on the Ubuntu ISO testing tracker.

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

** Tags added: iso-testing

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

Title:
  Ubuntu nm package lacking vpn support

Status in network-manager package in Ubuntu:
  Invalid

Bug description:
  The network-manager package in ubuntu breezy is lacking VPN support.
  Tools like nm-vpnc-service, nm-vpnc-service-vpnc-helper, and
  configuration files in /etc/NetworkManager/VPN are not installed.

  These tools are supposed to be built out of the vpn-daemons/
  subdirectory of the source package of the network-manager source
  tarball.  Note that this directory has its own set of configure script
  and Makefile.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/3312/+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 1907956] Re: ubiquity crash on whoopsie removal, Xubuntu 21.04 minimal install

[Ubuntu QA Website]

This bug has been reported on the Ubuntu ISO testing tracker.

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

** Tags added: iso-testing

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

Title:
  ubiquity crash on whoopsie removal, Xubuntu 21.04 minimal install

Status in ubiquity package in Ubuntu:
  New
Status in whoopsie package in Ubuntu:
  New

Bug description:
  Xubuntu hirsute 20201213 minimal install crashed on whoopsie removal
  but finished installing. This is 1907951 with hopefully more crash
  information.

  Related logs identified:
  Dec 13 12:37:05 xubuntu ubiquity: Purging configuration files for whoopsie 
(0.2.73) ...
  Dec 13 12:37:05 xubuntu ubiquity: #015
  Dec 13 12:37:05 xubuntu ubiquity: Running in chroot, ignoring command 
'daemon-reload'#015
  Dec 13 12:37:05 xubuntu ubiquity: message repeated 2 times: [ Running in 
chroot, ignoring command 'daemon-reload'#015]
  Dec 13 12:37:05 xubuntu ubiquity: rm:
  Dec 13 12:37:05 xubuntu ubiquity: cannot remove 
'/var/lib/whoopsie/whoopsie-id'
  Dec 13 12:37:05 xubuntu ubiquity: : No such file or directory
  Dec 13 12:37:05 xubuntu ubiquity: #015
  Dec 13 12:37:05 xubuntu ubiquity: dpkg: error processing package whoopsie 
(--purge):
  Dec 13 12:37:05 xubuntu ubiquity: #015
  Dec 13 12:37:05 xubuntu ubiquity:  installed whoopsie package post-removal 
script subprocess returned error exit status 1
  Dec 13 12:37:05 xubuntu ubiquity: #015

  Looks like it's a bug in the postrm script:
  #! /bin/sh

  set -e

  #DEBHELPER#

  if [ "$1" = "purge" ]; then
  deluser --quiet --system whoopsie > /dev/null || true
  chmod g-s /var/crash >/dev/null 2>&1
  chgrp root /var/crash >/dev/null 2>&1
  rm /var/lib/whoopsie/whoopsie-id >/dev/null
  fi

  exit 0

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: ubiquity 21.04.3
  ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14
  Uname: Linux 5.8.0-25-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu55
  Architecture: amd64
  CasperMD5CheckResult: pass
  CasperVersion: 1.456
  Date: Sun Dec 13 07:40:33 2020
  InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/xubuntu.seed 
maybe-ubiquity quiet splash ---
  LiveMediaBuild: Xubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20201213)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
  RebootRequiredPkgs:
   linux-image-5.8.0-25-generic
   linux-base
  SourcePackage: ubiquity
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1907956/+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 1899962] Re: Wrong audio output device selected on Raspberry Pi Desktop

[Ubuntu QA Website]

This bug has been reported on the Ubuntu ISO testing tracker.

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

** Tags added: iso-testing

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

Title:
  Wrong audio output device selected on Raspberry Pi Desktop

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  On each boot, an incorrect audio output device is selected, at least
  when HDMI audio output is in use (still need to test the TV/aux
  output; will update the bug when done).

  Specifically, the settings application lists "Multichannel Output -
  Built-in Audio" as the selected output device. However, for audio to
  play through the connected HDMI device, "Analog Output - Built-in
  Audio" must be selected instead. Unfortunately, this setting will be
  lost on subsequent boots. A workaround is to remove the following
  lines from /etc/pulse/default.pa:

  ### Use hot-plugged devices like Bluetooth or USB automatically (LP: 
#1702794)
  .ifexists module-switch-on-connect.so
  load-module module-switch-on-connect
  .endif

  However, removal of these lines will (as the comment suggests) result
  in hot-plugged USB devices *not* being automatically selected.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1899962/+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 1899628] Re: ubuntu-bug fails just after installing apt update has never been done

[Ubuntu QA Website]

This bug has been reported on the Ubuntu ISO testing tracker.

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

** Tags added: iso-testing

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

Title:
  ubuntu-bug fails just after installing apt update has never been done

Status in apport package in Ubuntu:
  New

Bug description:
  Doing the ISO testing in a machine, that I did it staying offline.

  After installing, I connected and noticed a bug I wanted to report in
  ubuntu-drivers-common, but doing `ubuntu-bug` on it failed:

  This does not seem to be an official Ubuntu Package. Please retry
  after updating the indexes of available packages...

  https://i.imgur.com/fnDz6vf.png

  This is true as per:

  $ apt-cache policy ubuntu-drivers-common
  ubuntu-drivers-common:
Installed: 1:0.8.5.4
Candidate: 1:0.8.5.4
Version table:
   *** 1:0.8.5.4 100
  100 /var/lib/dpkg/status

  However, apport should probably trigger an apt-update in such case
  first instead of failing, or adding a button to do this easily and
  then proceed with the report.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: apport 2.20.11-0ubuntu49
  ProcVersionSignature: Ubuntu 5.8.0-22.23-generic 5.8.14
  Uname: Linux 5.8.0-22-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu49
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 13 14:19:30 2020
  InstallationDate: Installed on 2020-10-13 (0 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Beta amd64 (20201013.1)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1899628/+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 1897934] Re: The initial sound level is set to zero (mute)

[Ubuntu QA Website]

This bug has been reported on the Ubuntu ISO testing tracker.

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

** Tags added: iso-testing

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

Title:
  The initial sound level is set to zero (mute)

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  On boot into the live session - or on first install the sound level is
  muted.

  I have to use GNOME Control Center - Sounds to change to an
  appropriate level.  Once changed the level chosen is correctly
  retained between reboots.

  This appears to be a regression from 18.04 where the sound level was
  set to - I guess - 80% on the live-session/first install

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: pulseaudio 1:13.99.1-1ubuntu11
  ProcVersionSignature: Ubuntu 5.8.0-20.21-generic 5.8.10
  Uname: Linux 5.8.0-20-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu48
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu-budgie   5041 F pulseaudio
  CasperMD5CheckResult: pass
  CasperVersion: 1.452
  CurrentDesktop: Budgie:GNOME
  Date: Wed Sep 30 16:03:08 2020
  LiveMediaBuild: Ubuntu-Budgie 20.10 "Groovy Gorilla" - Beta amd64 (20200930)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/15/2016
  dmi.bios.release: 15.31
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.1F
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 80BF
  dmi.board.vendor: HP
  dmi.board.version: 95.16
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.ec.firmware.release: 95.22
  dmi.modalias: 
dmi:bvnInsyde:bvrF.1F:bd02/15/2016:br15.31:efr95.22:svnHP:pnHPNotebook:pvr:rvnHP:rn80BF:rvr95.16:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP
  dmi.product.name: HP Notebook
  dmi.product.sku: N9S73EA#ABU
  dmi.sys.vendor: HP

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1897934/+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 1897273] Re: booting ubuntu groovy daily; display unusuable

[Ubuntu QA Website]

This bug has been reported on the Ubuntu ISO testing tracker.

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

** Tags added: iso-testing

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

Title:
  booting ubuntu groovy daily; display unusuable

Status in ubuntu-meta package in Ubuntu:
  New

Bug description:
  booting Ubuntu daily on
  dell [optiplex] 990 (i7-2600, 16gb, nvidia geforce gt 6600 gt)

  Media validation occurs as expected, passes the Ubuntu logo is as
  expected then I get a Ubuntu background type color and the session is
  now unusable

  The first display (after checks etc) occur is

  https://photos.app.goo.gl/gHgb98LTgGiWtMEw7

  If left, i'll eventually get a purple screen and cursor, however
  nothing that responds as expected.

  No usable session, but screen is there, background a solid Ubuntu
  color, with normal cursor; alas nothing more.

  By switching to a terminal,  I can check that no squashfs errors
  occurred & explore the system (including file this bug), however
  switching back gets me screens like

  https://photos.app.goo.gl/LJg4qvS7VajRny4e8

  followed by hitting CTRL+ALT+T to open a terminal and the screen
  changes to

  https://photos.app.goo.gl/PJQxSABrNwg6UNGW9

  The CTRL+ALT+T was recognized, as the terminal can be seen in the
  pinky area top left of screen, but it's not usable...

  I wonder if it's the screensaver kicking in that screws up the
  session, but I've not worked that up yet.  I've been unable to watch
  the machine the whole time so I've not worked out pattern.

  ( FYI:  this is not the first boot or attempt. This has occurred now
  three times tried (same iso, just rebooting machine).  My intention
  tonight was explore
  https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1897173 via
  install on this box alas I can't install with it performing like this.
  A number of QA-test installs have been run on this system today,
  Lubuntu had no issues, Xubuntu failed due 1897173 with readable
  screens )

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: ubuntu-desktop 1.457
  ProcVersionSignature: Ubuntu 5.8.0-19.20-generic 5.8.8
  Uname: Linux 5.8.0-19-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu47
  Architecture: amd64
  CasperMD5CheckResult: pass
  CasperVersion: 1.452
  Date: Fri Sep 25 11:58:18 2020
  LiveMediaBuild: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200925)
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-meta
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1897273/+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 1887220] Re: Clicking on preinstalled /usr/share/applications/vim.desktop ends with "There was an error launching the application." and Vim is not launched

[Ubuntu QA Website]

This bug has been reported on the Ubuntu ISO testing tracker.

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

** Tags added: iso-testing

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

Title:
  Clicking on preinstalled  /usr/share/applications/vim.desktop ends
  with "There was an error launching the application." and Vim is not
  launched

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

Bug description:
  Steps to reproduce:
  1. Have Ubuntu MATE installed
  2. Open Caja, navigate to 

 /usr/share/applications/

  3. Click on Vim

  Expected result:
  * Vim is launched

  Actual result:
  * Vim is not launched, the error window is shown with text "There was an 
error launching the application."

  Notes:

  the /usr/share/applications/vim.desktop refers to `vim` executable which is 
not installed.
  The /usr/share/applications/vim.desktop came from 

  ```
  $ dpkg -S /usr/share/applications/vim.desktop 
  vim-common: /usr/share/applications/vim.desktop

  $ aptitude why vim-common 
  i   vim-tiny Depends vim-common (= 2:7.4.1689-3ubuntu1.2)

  $ aptitude why vim-tiny 
  i   ubuntu-minimal Depends vim-tiny
  ```

  So it is a dependency issue. Having vim.desktop without installed `vim` 
executable is useless.
  All Ubuntu versions are affected.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: ubuntu-minimal 1.361.2
  ProcVersionSignature: Ubuntu 4.15.0-46.49~16.04.1-generic 4.15.18
  Uname: Linux 4.15.0-46-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Sat Jul 11 11:05:44 2020
  InstallationDate: Installed on 2018-08-07 (703 days ago)
  InstallationMedia: Ubuntu-MATE 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  SourcePackage: ubuntu-meta
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-mate-meta/+bug/1887220/+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 1890515] Re: ubuntu-bug blah.crash file gives errors that imply it wasn't submitted

[Ubuntu QA Website]

This bug has been reported on the Ubuntu ISO testing tracker.

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

** Tags added: iso-testing

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

Title:
  ubuntu-bug blah.crash file gives errors  that imply it wasn't
  submitted

Status in apport package in Ubuntu:
  New

Bug description:
  Unclear messages on `ubuntu-bug /var/crash/blah.crash`

  on i386 live qa-test
  asus eepc 1000HE (intel atom n270, 1gb, intel mobile 945gse integrated), 
wireless RT2790

  
  lubuntu@lubuntu:/var/crash$ ubuntu-bug _usr_bin_gnome-mpv.999.crash

  (apport-gtk:2872): dbind-WARNING **: 01:56:11.124: Error retrieving 
accessibility bus address: org.freedesktop.DBus.Error.ServiceUnknown: The name 
org.a11y.Bus was not provided by any .service files
  ERROR: gdb does not exist in the sandbox nor on the host

  The last line "ERROR: gdb does not exist in the sandbox nor on the
  host" I wonder if it's a reason for the submission not taking place,
  but it could also be something else.

  A clearer message at the end would be helpful,  eg.
  "Bug submitted: Thank you for helping make Ubuntu better"

  or
  "Submission a duplicate of existing, noted. Thank you for helping make Ubuntu 
better"

  Note: I've not thought about what I've written here, but a clearer
  message maybe helpful. But ending on an 'ERROR:' doesn't help
  users/testers know if the `ubuntu-bug` succeeded.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: apport 2.20.9-0ubuntu7.16
  ProcVersionSignature: Ubuntu 5.4.0-42.46~18.04.1-generic 5.4.44
  Uname: Linux 5.4.0-42-generic i686
  ApportVersion: 2.20.9-0ubuntu7.16
  Architecture: i386
  CasperVersion: 1.394.3
  CrashReports: 640:999:117:17658765:2020-08-06 01:57:14.718189716 
+:2020-08-06 01:57:15.718189716 
+:/var/crash/_usr_bin_gnome-mpv.999.crash
  CurrentDesktop: LXDE
  Date: Thu Aug  6 02:08:57 2020
  LiveMediaBuild: Lubuntu 18.04.5 LTS "Bionic Beaver" - Release i386 (20200805)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  SourcePackage: apport
  UpgradeStatus: No upgradwas not provided by any .service files
  ERROR: gdb does not exist in the sandbox nor on the hoste log present 
(probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1890515/+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 1889962] Re: kubuntu 20.04.1 live qa-test, screen alignment made display unusable

[Ubuntu QA Website]

This bug has been reported on the Ubuntu ISO testing tracker.

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

** Tags added: iso-testing

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

Title:
  kubuntu 20.04.1 live qa-test, screen alignment made display unusable

Status in ubuntu-meta package in Ubuntu:
  New

Bug description:
  Kubuntu 20.04.1 daily QA-test on 
  dell [optiplex] 755 (c2d-e8300, 8gb, amd/ati radeon rv610/radeon hd2400 
pro/xt)

  When I adjusted display.settings to have landscape+portrait, the
  landscape display became unreadable, and I obviously made mistake as
  portrait was upside-down.. GUI isn't usable as menu is on unusable
  display

  this box appears to have IDENTICAL files in /var/crash reported in
  https://bugs.launchpad.net/ubuntu/+source/kubuntu-meta/+bug/1889960
  but are likely unrelated.  They were `ubuntu-bug` reported

  This will be filed against INCORRECT package sorry; I suspect it's
  radeon related..

  Picture of screens 
  
https://photos.google.com/share/AF1QipPcjlzMvHtKIQVmi4QLOaY1_yLPbhFXbYFA32iLRCIrT2NTwvY-EpOEh54vwF8g2A?key=M2gtdTN4YjZ2c3RLVWJPMXQ2YXliZ3JMMG1PSW9R
 

  Much of the time the image shown on my-left display was changing
  (lower panel portion especially, also I think where cursor would be on
  terminal), about 3 changes per second, but at times it became static
  for awhile.


  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubuntu-desktop (not installed)
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  CasperMD5CheckResult: pass
  CasperVersion: 1.445.1
  CurrentDesktop: KDE
  Date: Sat Aug  1 05:46:46 2020
  LiveMediaBuild: Kubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  SourcePackage: ubuntu-meta
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1889962/+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 1884221] Re: `ubuntu-bug` fails with "UnboundLocalError: local variable 'project' referenced before assignment"

[Ubuntu QA Website]

This bug has been reported on the Ubuntu ISO testing tracker.

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

** Tags added: iso-testing

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

Title:
  `ubuntu-bug` fails with "UnboundLocalError: local variable 'project'
  referenced before assignment"

Status in apport package in Ubuntu:
  New

Bug description:
  I just tried to `ubuntu-bug ubiquity` on a groovy(20.10) qa-test
  install using Xubuntu, however `ubuntu-bug` abended with python
  errors.

  I tried to file this with `ubuntu-bug apport` & again errors (but
  scanning it looks identical)

  I'm filing this report on my primary box and will apport-collect after
  filing, plus copy/paste the details from the actual box.

  "UnboundLocalError: local variable 'project' referenced before
  assignment"

  xubuntu@xubuntu:~$ ubuntu-bug ubiquity
  Traceback (most recent call last):
File "/usr/share/apport/apport-gtk", line 597, in 
  app.run_argv()
File "/usr/lib/python3/dist-packages/apport/ui.py", line 708, in run_argv
  return self.run_report_bug()
File "/usr/lib/python3/dist-packages/apport/ui.py", line 549, in 
run_report_bug
  self.file_report()
File "/usr/lib/python3/dist-packages/apport/ui.py", line 1396, in 
file_report
  url = self.crashdb.get_comment_url(self.report, ticket)
File "/usr/lib/python3/dist-packages/apport/crashdb_impl/launchpad.py", 
line 247, in get_comment_url
  if not project:
  UnboundLocalError: local variable 'project' referenced before assignment

  xubuntu@xubuntu:~$ ubuntu-bug apport
  Traceback (most recent call last):
File "/usr/share/apport/apport-gtk", line 597, in 
  app.run_argv()
File "/usr/lib/python3/dist-packages/apport/ui.py", line 708, in run_argv
  return self.run_report_bug()
File "/usr/lib/python3/dist-packages/apport/ui.py", line 549, in 
run_report_bug
  self.file_report()
File "/usr/lib/python3/dist-packages/apport/ui.py", line 1396, in 
file_report
  url = self.crashdb.get_comment_url(self.report, ticket)
File "/usr/lib/python3/dist-packages/apport/crashdb_impl/launchpad.py", 
line 247, in get_comment_url
  if not project:
  UnboundLocalError: local variable 'project' referenced before assignment

  
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu40
  Architecture: amd64
  CasperMD5CheckResult: pass
  CasperVersion: 1.451
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 20.10
  LiveMediaBuild: Xubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200619)
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: apport 2.20.11-0ubuntu40
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Tags:  groovy
  Uname: Linux 5.4.0-26-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1884221/+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 1843982] Re: Various programs crashed with SIGSEGV in g_str_hash() from g_hash_table_lookup() from update_user()

[Ubuntu QA Website]

This bug has been reported on the Ubuntu ISO testing tracker.

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

** Tags added: iso-testing

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

Title:
  Various programs crashed with SIGSEGV in g_str_hash() from
  g_hash_table_lookup() from update_user()

Status in accountsservice:
  New
Status in accountsservice package in Ubuntu:
  Triaged
Status in accountsservice source package in Focal:
  Triaged
Status in accountsservice package in Debian:
  Confirmed

Bug description:
  https://errors.ubuntu.com/problem/597be858df957473f357a9249b002b0e39f42781
  https://errors.ubuntu.com/problem/3a817938d76d231fdfc8f698392fbf5e3724084f
  https://errors.ubuntu.com/problem/3945cd9cdcec914cab9a3220d05e969696c7

  ProblemType: Crash
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell 3.34.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8
  Uname: Linux 5.3.0-10-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Sep 14 10:29:16 2019
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2019-05-24 (112 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190523)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   LANG=nb_NO.UTF-8
   LANGUAGE=nb_NO:nb:no_NO:no:nn_NO:nn:en
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  RelatedPackageVersions: mutter-common 3.34.0-2ubuntu1
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   g_str_hash () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_hash_table_lookup () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libaccountsservice.so.0
   g_closure_invoke () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: gnome-shell crashed with SIGSEGV in g_str_hash()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/accountsservice/+bug/1843982/+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 1874178] Re: Unlocking existing session needs two attempts after selecting Switch User

[Ubuntu QA Website]

This bug has been reported on the Ubuntu ISO testing tracker.

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

** Tags added: iso-testing

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

Title:
  Unlocking existing session needs two attempts after selecting Switch
  User

Status in lightdm package in Ubuntu:
  New

Bug description:
  This has been occurring during the Xubuntu post-install test. It's not
  the same as Bug #1776475, as it's not necessary to have logged in as
  another user (or even for another user to exist) for the problem to
  happen.

  My sequence of actions is:

  *Create new user.
  *Open a program (usually Thunar or Terminal).
  *Lock session.
  *Click on "Switch User". <-- This is all that's necessary to trigger it.
  *Enter password to unlock my own session.
  *Then there's a delay and screen goes black, then the unlock prompt appears 
again.
  *The second time, my session unlocks.

  This particular report is from a QEMU/KVM vm, but it's also been
  happening on a bare-metal install.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: lightdm 1.30.0-0ubuntu3.1
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Wed Apr 22 15:30:29 2020
  InstallationDate: Installed on 2020-04-22 (0 days ago)
  InstallationMedia: Xubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200421)
  ProcEnviron:
   LANGUAGE=en_NZ:en
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_NZ.UTF-8
   SHELL=/bin/bash
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1874178/+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 1859308] Re: software-properties-gtk erroneously reports that Intel Wireless-AC 9260 device is not working

[Ubuntu QA Website]

This bug has been reported on the Ubuntu ISO testing tracker.

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

** Tags added: iso-testing

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

Title:
  software-properties-gtk erroneously reports that Intel Wireless-AC
  9260 device is not working

Status in software-properties package in Ubuntu:
  Confirmed

Bug description:
  On Ubuntu 20.04 (development branch), as of today, Additional Drivers
  (software-properties-gtk 0.98.6) reports that the device "Intel
  Corporation: Wireless-AC 9260" is not working, and suggests using a
  manually installed driver (cf. screenshot).

  However the device is working correctly:

    * lsmod | grep iwlwifi, lspci -v, lshw, dmesg | grep iwlwifi all show
  that its driver iwlwifi is in use
    * ls /lib/firmware/*9260* show that the appropriate firmware files
  are present

  And I am indeed writing this bug report connected to an ac (5 GHz)
  wifi network, where I can verify a ~130-160 Mbps download speed, so
  software-properties-gtk shouldn't report the device as not working and
  suggest manually installing a driver. Not sure why it says so?

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: software-properties-gtk 0.98.6
  ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3
  Uname: Linux 5.4.0-9-generic x86_64
  ApportVersion: 2.20.11-0ubuntu15
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jan 12 00:53:43 2020
  ExecutablePath: /usr/bin/software-properties-gtk
  InstallationDate: Installed on 2019-12-29 (13 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191226)
  InterpreterPath: /usr/bin/python3.7
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.7, Python 3.7.6, python3-minimal, 
3.7.5-1ubuntu1
  PythonDetails: /usr/bin/python2.7, Python 2.7.17, python-minimal, 2.7.17-1
  SourcePackage: software-properties
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1859308/+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 1845801] Re: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login.

[Ubuntu QA Website]

This bug has been reported on the Ubuntu ISO testing tracker.

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

** Tags added: iso-testing

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

Title:
  [nvidia] Automatic login fails and then all subsequent logins fail.
  Killing gnome-session-binary fixes it, or just not using automatic
  login.

Status in gdm3 package in Ubuntu:
  Confirmed
Status in gnome-session package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-430 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-435 package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Incomplete
Status in gdm3 source package in Eoan:
  Confirmed
Status in gnome-session source package in Eoan:
  Confirmed
Status in nvidia-graphics-drivers-435 source package in Eoan:
  Confirmed

Bug description:
  I just updated to the Ubuntu 19.10 beta. After boot, I'm shown the GDM
  login screen (which I shouldn't; I have auto login enabled), and
  logging in just takes me back to the same user selection screen even
  though the password is correct.

  If I switch to a TTY and run `sudo pkill gnome-session-binary`,
  logging in through GDM starts working again.

  I should add that the do-release-upgrade was rocky; I did it in a
  terminal from within gnome, went away for a while, and when I
  returned, I just saw an Ubuntu 19.10 in a TTY. I was able to do `sudo
  dpkg --configure -a` and complete the upgrade, but I don't know if
  something's still messed up due to that.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0
  Uname: Linux 5.3.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .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  435.21  Sun Aug 25 08:17:57 
CDT 2019
   GCC version:  gcc version 9.2.1 20190909 (Ubuntu 9.2.1-8ubuntu1)
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Sep 28 19:55:42 2019
  DistUpgraded: 2019-09-28 18:35:15,142 INFO cache.commit()
  DistroCodename: eoan
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 435.21, 5.3.0-13-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] [10de:1b06] (rev a1) (prog-if 
00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. GP102 [GeForce GTX 1080 Ti] [1043:85e4]
  InstallationDate: Installed on 2019-09-14 (13 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  MachineType: MSI MS-7A67
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-13-generic 
root=UUID=04974c80-e732-49b6-8148-c3dce7c02a25 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: Upgraded to eoan on 2019-09-28 (0 days ago)
  dmi.bios.date: 01/25/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2.60
  dmi.board.asset.tag: Default string
  dmi.board.name: H270I GAMING PRO AC (MS-7A67)
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2.60:bd01/25/2018:svnMSI:pnMS-7A67:pvr1.0:rvnMSI:rnH270IGAMINGPROAC(MS-7A67):rvr1.0:cvnMSI:ct3:cvr1.0:
  dmi.product.family: Default string
  dmi.product.name: MS-7A67
  dmi.product.sku: Default string
  dmi.product.version: 1.0
  dmi.sys.vendor: MSI
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.1.6-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:1.20.5+git20190820-0ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Touch-packages] [Bug 1776475] Re: Unlocking existing session often requires several attempts.

[Ubuntu QA Website]

This bug has been reported on the Ubuntu ISO testing tracker.

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

** Tags added: iso-testing

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

Title:
  Unlocking existing session often requires several attempts.

Status in lightdm package in Ubuntu:
  Confirmed

Bug description:
  # Context

  * Computer with several X sessions opened.
  * Users switching from one opened session to another.
  * Lightdm opens new greeter, wait for typing password.
  * User types password.
  * Password is accepted.
  * System closes the current greeter (screen gets black for an instant).

  # Expected

  * User gets back to their already opened session.

  # Observed

  * System immediately opens another greeter.
  * User has to type password again.

  # Reproducible

  * Not always. At times, often, at other times, rare.

  # Additional information

  Users switch session via 
  dm-tool switch-to-user $OTHERUSER
  but I guess bug appears with other means (like menu item like "lock screen", 
etc).

  # Information requested

  lsb_release -rd

  Description:  Ubuntu 18.04 LTS
  Release:  18.04

  
  LC_ALL=C apt-cache policy lightdm

  lightdm:
Installed: 1.26.0-0ubuntu1
Candidate: 1.26.0-0ubuntu1
Version table:
   *** 1.26.0-0ubuntu1 500
  500 http://fr.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: lightdm 1.26.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  Date: Tue Jun 12 14:14:52 2018
  ExecutablePath: /usr/sbin/lightdm
  InstallationDate: Installed on 2018-05-25 (18 days ago)
  InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  ProcEnviron:
   LANG=fr_FR.UTF-8
   PATH=(custom, no user)
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.logrotate.d.lightdm: [modified]
  mtime.conffile..etc.logrotate.d.lightdm: 2018-05-25T06:19:22.081830

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1776475/+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 1870213] Re: "Switching to another layout" shortcut was not set by oem-config for end-user

[Ubuntu QA Website]

This bug has been reported on the Ubuntu ISO testing tracker.

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

** Tags added: iso-testing

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

Title:
  "Switching to another layout" shortcut was not set by oem-config for
  end-user

Status in console-setup package in Ubuntu:
  New
Status in oem-config package in Ubuntu:
  New

Bug description:
  Steps to reproduce:
  1. Launch Ubuntu MATE 20.04 LTS installer in OEM mode
  2. Confirm using English locale
  3. While setting OS for end user specify Russian language, confirm system 
configuration
  4. Login to the configured system

  Expected result:
  * the keyboard layout switcher shows two layouts - *en* and *ru*, reacts on 
+ hotkey 

  Actual result:
  * the keyboard layout switcher shows two layouts - *en* and *ru*, but does 
not react on + hotkey 

  Note: the contents of keyboard configuration files is the following:

  ```
  $ cat /etc/default/keyboard
  # KEYBOARD CONFIGURATION FILE

  # Consult the keyboard(5) manual page.

  XKBMODEL="pc105"
  XKBLAYOUT="us,ru"
  XKBVARIANT=","
  XKBOPTIONS="grp_led:scroll"

  BACKSPACE="guess"

  ```
  so keyboard layout switcher is not defined here.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: keyboard-configuration 1.194ubuntu3
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu21
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Thu Apr  2 00:43:16 2020
  InstallationDate: Installed on 2020-04-01 (0 days ago)
  InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Beta amd64 (20200401)
  PackageArchitecture: all
  SourcePackage: console-setup
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1870213/+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 1868780] Re: Xubuntu 20.04 - Blank screen after login

[Ubuntu QA Website]

This bug has been reported on the Ubuntu ISO testing tracker.

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

** Tags added: iso-testing

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

Title:
  Xubuntu 20.04 - Blank screen after login

Status in xorg package in Ubuntu:
  New

Bug description:
  Both on Xubuntu 20.04 23rd March and 24th March daily build.
  Using Martin Wimpress QuickEMU setup.
  Installation part of xubuntu is working fine.
  But after install and reboot, you get the login box. I type in the password 
for the user and then just get a black screen and mouse cursor, no other error 
boxes or gui.
  Have tested my QuickEMU setup on ubuntu-mate and do not see this issue, only 
on Xubuntu daily builds do I see this issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
  Uname: Linux 5.4.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu21
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  Date: Tue Mar 24 16:40:12 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Red Hat, Inc. Virtio GPU [1af4:1050] (rev 01) (prog-if 00 [VGA controller])
 Subsystem: Red Hat, Inc. Virtio GPU [1af4:1100]
  InstallationDate: Installed on 2020-03-24 (0 days ago)
  InstallationMedia: Xubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200324)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet
   Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Keyboard
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Lsusb-t:
   /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/8p, 5000M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/8p, 480M
   |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 
480M
   |__ Port 2: Dev 3, If 0, Class=Human Interface Device, Driver=usbhid, 
480M
  MachineType: QEMU Standard PC (Q35 + ICH9, 2009)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-18-generic 
root=UUID=4b1c21e9-1325-435b-9ade-04263b901e6d ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: rel-1.12.0-59-gc9ba5276e321-prebuilt.qemu.org
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-q35-4.2
  dmi.modalias: 
dmi:bvnSeaBIOS:bvrrel-1.12.0-59-gc9ba5276e321-prebuilt.qemu.org:bd04/01/2014:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-4.2:cvnQEMU:ct1:cvrpc-q35-4.2:
  dmi.product.name: Standard PC (Q35 + ICH9, 2009)
  dmi.product.version: pc-q35-4.2
  dmi.sys.vendor: QEMU
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.100-4
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.0-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1868780/+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 1864526] Re: Display ghosting when dragging icons or opening menus

[Ubuntu QA Website]

This bug has been reported on the Ubuntu ISO testing tracker.

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

** Tags added: iso-testing

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

Title:
  Display ghosting when dragging icons or opening menus

Status in xorg package in Ubuntu:
  New

Bug description:
  Display ghosting when dragging icons or opening menus.
  Have tested several machines and this only occurring on Intel NUC 8i3BEK - 
and only when
  installing or using FOCAL Lubuntu 20.04 .

  This also is occurring in the Live sessions before install.

  I have tested Lubuntu Eoan 19.01 and Lubuntu Bionic 18.04.04 on this
  machine and cannot reproduce the issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
  Uname: Linux 5.4.0-14-generic x86_64
  ApportVersion: 2.20.11-0ubuntu18
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: LXQt
  Date: Mon Feb 24 18:23:21 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Iris Plus Graphics 655 [8086:3ea5] (rev 01) (prog-if 00 
[VGA controller])
 Subsystem: Intel Corporation Iris Plus Graphics 655 [8086:2074]
  InstallationDate: Installed on 2020-02-24 (0 days ago)
  InstallationMedia: Lubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200224)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 04f2:0402 Chicony Electronics Co., Ltd Genius 
LuxeMate i200 Keyboard
   Bus 001 Device 002: ID 2188:0ae1  USB OPTICAL MOUSE 
   Bus 001 Device 004: ID 8087:0aaa Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Intel(R) Client Systems NUC8i3BEK
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-14-generic 
root=UUID=11c10d68-db79-4d45-9bbe-8357e125b46b ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/18/2019
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: BECFL357.86A.0073.2019.0618.1409
  dmi.board.name: NUC8BEB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: J72693-307
  dmi.chassis.type: 35
  dmi.chassis.vendor: Intel Corporation
  dmi.chassis.version: 2.0
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrBECFL357.86A.0073.2019.0618.1409:bd06/18/2019:svnIntel(R)ClientSystems:pnNUC8i3BEK:pvrJ72748-306:rvnIntelCorporation:rnNUC8BEB:rvrJ72693-307:cvnIntelCorporation:ct35:cvr2.0:
  dmi.product.family: BE
  dmi.product.name: NUC8i3BEK
  dmi.product.sku: BOXNUC8i3BEK
  dmi.product.version: J72748-306
  dmi.sys.vendor: Intel(R) Client Systems
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.100-4
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.0-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu1
  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+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1864526/+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 1854621] Re: ubuntu 20.04 daily boots with no background, selecting other background has warped picture

[Ubuntu QA Website]

This bug has been reported on the Ubuntu ISO testing tracker.

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

** Tags added: iso-testing

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

Title:
  ubuntu 20.04 daily boots with no background, selecting other
  background has warped picture

Status in ubuntu-meta package in Ubuntu:
  New

Bug description:
  Ubuntu 20.04 daily - verified (check disc for defects) prior to boot.
  dell [optiplex] 755 (c2d-e6850, 5gb, amd/ati radeon rv516/x1300/x1550)

  On booting, the 20.04 daily has no background when desktop is loaded?
  (ie. top panel is there, dock on left side on black screen)

  When changing background (to any already installed), they are warped
  when selected and made the bacground as if corrupted (but small image
  where selection is made looks valid).


  This issue may relate to video card  [radeon]

  ubuntu@ubuntu:~$ sudo lshw -C video
*-display:0   
 description: VGA compatible controller
 product: RV516 [Radeon X1300/X1550 Series]
 vendor: Advanced Micro Devices, Inc. [AMD/ATI]
 physical id: 0
 bus info: pci@:01:00.0
 version: 00
 width: 64 bits
 clock: 33MHz
 capabilities: pm pciexpress msi vga_controller bus_master cap_list rom
 configuration: driver=radeon latency=0
 resources: irq:16 memory:d000-dfff memory:fe9e-fe9e 
ioport:dc00(size=256) memory:c-d
*-display:1 UNCLAIMED
 description: Display controller
 product: RV516 [Radeon X1300/X1550 Series] (Secondary)
 vendor: Advanced Micro Devices, Inc. [AMD/ATI]
 physical id: 0.1
 bus info: pci@:01:00.1
 version: 00
 width: 64 bits
 clock: 33MHz
 capabilities: pm pciexpress bus_master cap_list
 configuration: latency=0
 resources: memory:fe9f-fe9f

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubuntu-desktop 1.440
  ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
  Uname: Linux 5.3.0-18-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu9
  Architecture: amd64
  CasperVersion: 1.432
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Dec  1 11:58:33 2019
  LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191128)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-meta
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1854621/+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 1851058] Re: Live session any mouse or keyboard command is ignored

[Ubuntu QA Website]

This bug has been reported on the Ubuntu ISO testing tracker.

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

** Tags added: iso-testing

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

Title:
  Live session any mouse or keyboard command is ignored

Status in xorg package in Ubuntu:
  New

Bug description:
  The problem happens in the live session. Ubiquity starts ok, The default 
desktop is displayed, but any mouse or keyboard command is ignored. If instead 
of "Try Ubuntu" I select "install Ubuntu" the install runs fine but the new 
installed system has the problem described in bug #1850969.
  Same problem with ISO Alpha amd64 (20191101), 20191102, 20191030 and 20191031
  also on a different hardware (HP laptop) and also selecting 'graphic failsafe'
  Now I'm working with Wayland session because X11 does not work.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
  Uname: Linux 5.3.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu9
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Nov  2 17:36:01 2019
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation HD Graphics 630 [8086:5912] (rev 04) (prog-if 00 [VGA 
controller])
 Subsystem: ASRock Incorporation HD Graphics 630 [1849:5912]
  InstallationDate: Installed on 2019-11-01 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191101)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 046d:c016 Logitech, Inc. Optical Wheel Mouse
   Bus 001 Device 002: ID 058f:6377 Alcor Micro Corp. AU6375 4-LUN card reader
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-18-generic 
root=UUID=062c7ec4-2948-49df-934f-d054f397e4c4 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/11/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.10
  dmi.board.name: H110M-G/M.2
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.10:bd05/11/2017:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH110M-G/M.2:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
  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+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1851058/+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 1849835] Re: add-apt-repository does not work in focal

[Ubuntu QA Website]

This bug has been reported on the Ubuntu ISO testing tracker.

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

** Tags added: iso-testing

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

Title:
  add-apt-repository does not work in focal

Status in software-properties package in Ubuntu:
  New

Bug description:
  I tested to use a ppa because I wanted to test if mkusb will work in
  focal. But

  add-apt-repository

  does not work.

  ---
  lubuntu@lubuntu:~$ sudo add-apt-repository ppa:mkusb/ppa  # existing ppa
  Traceback (most recent call last):
File "/usr/bin/add-apt-repository", line 107, in 
  sp = SoftwareProperties(options=options)
File 
"/usr/lib/python3/dist-packages/softwareproperties/SoftwareProperties.py", line 
118, in __init__
  self.reload_sourceslist()
File 
"/usr/lib/python3/dist-packages/softwareproperties/SoftwareProperties.py", line 
613, in reload_sourceslist
  self.distro.get_sources(self.sourceslist)
File "/usr/lib/python3/dist-packages/aptsources/distro.py", line 93, in 
get_sources
  (self.id, self.codename))
  aptsources.distro.NoDistroTemplateException: Error: could not find a 
distribution template for Ubuntu/focal
  lubuntu@lubuntu:~$ sudo add-apt-repository ppa:qwerty/asdf  # not existing 
ppa: same output
  Traceback (most recent call last):
File "/usr/bin/add-apt-repository", line 107, in 
  sp = SoftwareProperties(options=options)
File 
"/usr/lib/python3/dist-packages/softwareproperties/SoftwareProperties.py", line 
118, in __init__
  self.reload_sourceslist()
File 
"/usr/lib/python3/dist-packages/softwareproperties/SoftwareProperties.py", line 
613, in reload_sourceslist
  self.distro.get_sources(self.sourceslist)
File "/usr/lib/python3/dist-packages/aptsources/distro.py", line 93, in 
get_sources
  (self.id, self.codename))
  aptsources.distro.NoDistroTemplateException: Error: could not find a 
distribution template for Ubuntu/focal
  lubuntu@lubuntu:~$ lsb_release -a
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:Ubuntu Focal Fossa (development branch)
  Release:20.04
  Codename:   focal
  lubuntu@lubuntu:~$ 
  ---

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: software-properties-common 0.98.5
  ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
  Uname: Linux 5.3.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  CasperVersion: 1.427
  CurrentDesktop: LXQt
  Date: Fri Oct 25 13:10:33 2019
  LiveMediaBuild: Lubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191024)
  PackageArchitecture: all
  SourcePackage: software-properties
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1849835/+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 1848558] Re: (intermittent) need to authenticate 3 times before accepted

[Ubuntu QA Website]

This bug has been reported on the Ubuntu ISO testing tracker.

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

** Tags added: iso-testing

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

Title:
  (intermittent) need to authenticate 3 times before accepted

Status in apport package in Ubuntu:
  New

Bug description:
  When at the terminal, trying to file an issue with ubuntu-bug, I was
  prompted for authentication. Only after the third try was the password
  accepted.

  1. I entered the password correctly and the authentication window closed and 
reopened very quickly (no error message that I had entered the password 
incorrectly).
  2. Then I entered a bogus password and the authentication window closed and 
reopened very quickly (this time with the expected “Your authentication attempt 
was unsuccessful. Please try again”).
  3. Then I entered the correct password again and it was accepted.

  This happens more often than not, however sometimes I'm not prompted
  for authentication at all with ubuntu-bug. When I am prompted for
  authentication, all three tries can be the correct password (no need
  to have a bogus password entered as one of the tries) and only the
  third one is accepted.

  The expected behavior is:
  1. Consistency: ubuntu-bug should either always prompt the user for a 
password or always not
  2. Only one entry needed: If ubuntu-bug is going to prompt the user for a 
password using apport, then the first correct entry should be accepted.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: apport 2.20.11-0ubuntu8
  ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
  Uname: Linux 5.3.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Thu Oct 17 11:44:30 2019
  InstallationDate: Installed on 2019-10-17 (0 days ago)
  InstallationMedia: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1848558/+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 1841079] Re: Speech Dispatcher user should not be shown on LightdDM login screen

[Ubuntu QA Website]

This bug has been reported on the Ubuntu ISO testing tracker.

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

** Tags added: iso-testing

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

Title:
  Speech Dispatcher user should not be shown on LightdDM login screen

Status in lightdm package in Ubuntu:
  Confirmed
Status in speech-dispatcher package in Ubuntu:
  Confirmed
Status in ubuntu-mate-settings package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce:
  1. Download Ubuntu MATE 19.10 alpha ISO - 20190822
  2. Install it using Entire-disk erase scenario with default settings
  3. Reboot system

  Expected results:
  * LightDM shows only just created username

  Actual results:
  * LightDM shows two user names, Speech Dispatcher is selected by default

  Note:
  problem occurs on VM and on real hardware; Minimal desktop installation is 
affected too; OEM installation is affected by bug 1840971 .

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: speech-dispatcher 0.9.1-2
  ProcVersionSignature: Ubuntu 5.2.0-10.11-generic 5.2.4
  Uname: Linux 5.2.0-10-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Thu Aug 22 19:02:42 2019
  InstallationDate: Installed on 2019-08-22 (0 days ago)
  InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Alpha amd64 (20190822)
  SourcePackage: speech-dispatcher
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1841079/+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 1824670] Re: Boot to black screen after Kubuntu 19.04 install

[Ubuntu QA Website]

This bug has been reported on the Ubuntu ISO testing tracker.

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

** Tags added: iso-testing

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

Title:
  Boot to black screen after Kubuntu 19.04 install

Status in xorg package in Ubuntu:
  New

Bug description:
  Legacy laptop, Dell Vostro 1720, booted to black screen after fresh
  full disk install.  Using ctrl-alt-f2 to drop to a terminal and
  issuing "startx" completed the boot process.

  Installed NVidia 340 driver which crashed the current session and sent
  me to an endless GUI (sddm?) login loop where login immediately
  crashed back to the GUI login.

  Rebooting from the login screen worked as expected and system is
  running fine now.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.0.0-11.12-generic 5.0.6
  Uname: Linux 5.0.0-11-generic x86_64
  NonfreeKernelModules: nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  340.107  Thu May 24 21:54:01 
PDT 2018
   GCC version:  gcc version 8.3.0 (Ubuntu 8.3.0-6ubuntu1)
  .proc.driver.nvidia.warnings.fbdev:
   Your system is not currently configured to drive a VGA console
   on the primary VGA device. The NVIDIA Linux graphics driver
   requires the use of a text-mode VGA console. Use of other console
   drivers including, but not limited to, vesafb, may result in
   corruption and stability problems, and is not supported.
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: KDE
  Date: Sat Apr 13 21:03:41 2019
  DistUpgraded: Fresh install
  DistroCodename: disco
  DistroVariant: ubuntu
  DkmsStatus: nvidia-340, 340.107, 5.0.0-11-generic, x86_64: installed
  GraphicsCard:
   NVIDIA Corporation G96M [GeForce 9600M GS] [10de:0648] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Dell G96M [GeForce 9600M GS] [1028:02c0]
  InstallationDate: Installed on 2019-04-14 (0 days ago)
  InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190413.1)
  MachineType: Dell Inc. Vostro 1720
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-11-generic 
root=UUID=bd90d4b8-d528-46cd-8c3a-55001a8200b9 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/27/2009
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A05
  dmi.board.name: 0P369J
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnDellInc.:bvrA05:bd10/27/2009:svnDellInc.:pnVostro1720:pvrNull:rvnDellInc.:rn0P369J:rvr:cvnDellInc.:ct8:cvrN/A:
  dmi.product.family: Vostro
  dmi.product.name: Vostro 1720
  dmi.product.sku: Null
  dmi.product.version: Null
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-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:1.20.4-1ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20180925-2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1824670/+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 1823306] Re: lxqt-sudo added to Exec line of software-properties-qt.desktop breaks use in KDE Plasma Discover

[Ubuntu QA Website]

This bug has been reported on the Ubuntu ISO testing tracker.

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

** Tags added: iso-testing

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

Title:
  lxqt-sudo added to Exec line of software-properties-qt.desktop breaks
  use in KDE Plasma Discover

Status in software-properties package in Ubuntu:
  In Progress
Status in software-properties source package in Disco:
  In Progress

Bug description:
  In the upload: https://launchpad.net/ubuntu/+source/software-
  properties/0.97.8

  there is a change in the software-properties-qt.desktop files which is
  (a) not documented in the changelog, and (b) not communicated to other
  flavour users of this application (Kubuntu in this case).

  -Exec=software-properties-qt
  +Exec=lxqt-sudo software-properties-qt

  This results in Plasma Discover not being able to launch software-
  properties-qt, as it uses privilege elevation via kdesu of whatever is
  in the Exec line, and lxqt-sudo added there makes this fail.

  Context to this is:

  For Cosmic release Lubuntu developers requested agreement from Kubuntu
  to the porting of the software-properties-kde package to pure Qt, so
  that it could be used in both Kubuntu and Lubuntu (lxqt) without
  pulling a lot of KDE dependencies into Lubuntu's lqxt images/installs.
  This was on the condition that despite being renamed to -qt, it
  remained completely as a tool for joint usage between the two
  flavours.

  The original sofware-properties-kde was meant to be launched by
  applications and was set not to show in DE menus by default.

  It seems that Lubuntu wishes to now have it useable directly from a
  'start'/'search' menu, hence making it visible and adding the lxqt-
  sudo in the Exec line to facilitate launch with privilege escalation.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1823306/+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 1822047] Re: After install, cannot boot into system unless I use nomodeset kernel parameter

[Ubuntu QA Website]

This bug has been reported on the Ubuntu ISO testing tracker.

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

** Tags added: iso-testing

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

Title:
  After install, cannot boot into system unless I use nomodeset kernel
  parameter

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  System: Disco (19.04 beta)
  Hardware: Dell Precision 7530

  After installing the system, it cannot start unless manually adding
  `nomodeset` in the kernel command line at boot time.

  Steps to reproduce:

  1. Install disco 19.04 beta on the device. Leave all the options at default 
values (i.e. do not install third party drivers)
  2. Once installation is finished, restart the system (the system will freeze 
after install is finished, it's a known issue -> lp:1822044)

  Expected result:

  2. The system boots and user can log in and see Gnome interface.

  Actual result:

  2. The first time, I could log into the system. However, when I tried
  to access the Settings screen, the system froze. After that, everytime
  I tried to boot the device, the screen was filled with dark purple, a
  mouse cursor may appear, but nothing else would happen. At that stage,
  the only thing I could do was to force shutdown the device, start it
  again and at Grub screen, press `e` to edit the kernel parameters and
  add `nomodeset`.

  This bug is created from the actual device, using `nomodeset` kernel
  parameter. `nouveau` graphics driver is most likely the culprit, like
  in all the previous issues that have been raised (see lp:1822026,
  lp:1822044, lp:1821882)

  Two workarounds exist:

  1. After installation, use `nomodeset` kernel parameter to boot into the 
system, then install proprietary nvidia drivers.
  2. During installation, install third party drivers. If Secure Boot is 
enabled, this requires to set a password that will be asked when the device 
reboots.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0
  Uname: Linux 5.0.0-7-generic x86_64
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Mar 28 15:39:40 2019
  DistUpgraded: Fresh install
  DistroCodename: disco
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (prog-if 00 [VGA 
controller])
 Subsystem: Dell UHD Graphics 630 (Mobile) [1028:0889]
   NVIDIA Corporation GP107GLM [Quadro P1000 Mobile] [10de:1cbb] (rev a1) 
(prog-if 00 [VGA controller])
 Subsystem: Dell GP107GLM [Quadro P1000 Mobile] [1028:0889]
  InstallationDate: Installed on 2019-03-28 (0 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190326.2)
  MachineType: Dell Inc. Precision 7530
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-7-generic 
root=UUID=e07663b1-0b3d-4cdb-aa6c-f6f2e8c4ee5d ro quiet splash nomodeset 
vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/19/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.7.0
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.7.0:bd02/19/2019:svnDellInc.:pnPrecision7530:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:
  dmi.product.family: Precision
  dmi.product.name: Precision 7530
  dmi.product.sku: 0889
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.0-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20180925-2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1822047/+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 1821882] Re: Screen is very dark and brightness cannot be adjusted

[Ubuntu QA Website]

This bug has been reported on the Ubuntu ISO testing tracker.

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

** Tags added: iso-testing

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

Title:
  Screen is very dark and brightness cannot be adjusted

Status in xorg package in Ubuntu:
  New

Bug description:
  Device: Dell Precision 7530
  In the BIOS, the Switchable Graphics option is deactived, which means only 
the nVidia GPU is used.

  When booting 19.04 beta live USB, the screen becomes very dark and
  brightness cannot be adjusted. (The same issue happens with 18.04.2)

  There is only a "nv_backlight" in /sys/class/backlight/ (i.e. no
  intel_backlight):

  $ ll /sys/class/backlight/
  total 0
  drwxr-xr-x  2 root root 0 Mar 27 09:36 ./
  drwxr-xr-x 74 root root 0 Mar 27 09:28 ../
  lrwxrwxrwx  1 root root 0 Mar 27 09:28 nv_backlight -> 
../../devices/pci:00/:00:01.0/:01:00.0/drm/card0/card0-eDP-1/nv_backlight/

  Trying to manually change brightness doesn't do anything:

  $ sudo su
  root@ubuntu:/home/ubuntu# cd /sys/class/backlight/nv_backlight
  root@ubuntu:/sys/class/backlight/nv_backlight# ll
  total 0
  drwxr-xr-x 3 root root0 Mar 27 09:28 ./
  drwxr-xr-x 4 root root0 Mar 27 09:28 ../
  -r--r--r-- 1 root root 4096 Mar 27 09:37 actual_brightness
  -rw-r--r-- 1 root root 4096 Mar 27 09:37 bl_power
  -rw-r--r-- 1 root root 4096 Mar 27 09:28 brightness
  lrwxrwxrwx 1 root root0 Mar 27 09:37 device -> ../../card0-eDP-1/
  -r--r--r-- 1 root root 4096 Mar 27 09:28 max_brightness
  drwxr-xr-x 2 root root0 Mar 27 09:28 power/
  lrwxrwxrwx 1 root root0 Mar 27 09:28 subsystem -> 
../../../../../../../../class/backlight/
  -r--r--r-- 1 root root 4096 Mar 27 09:28 type
  -rw-r--r-- 1 root root 4096 Mar 27 09:28 uevent
  root@ubuntu:/sys/class/backlight/nv_backlight# cat actual_brightness
  100
  root@ubuntu:/sys/class/backlight/nv_backlight# cat brightness
  100
  root@ubuntu:/sys/class/backlight/nv_backlight# cat max_brightness
  100
  root@ubuntu:/sys/class/backlight/nv_backlight# echo 50 > brightness
  root@ubuntu:/sys/class/backlight/nv_backlight# cat brightness
  50

  Although the value is changed, the screen brightness doesn't change.

  in dmesg, I can see the following:

  [0.241878] ACPI: Added _OSI(Module Device)
  [0.241878] ACPI: Added _OSI(Processor Device)
  [0.241878] ACPI: Added _OSI(3.0 _SCP Extensions)
  [0.241878] ACPI: Added _OSI(Processor Aggregator Device)
  [0.241878] ACPI: Added _OSI(Linux-Dell-Video)
  [0.241878] ACPI: Added _OSI(Linux-Lenovo-NV-HDMI-Audio)
  [0.241878] ACPI: Added _OSI(Linux-HPI-Hybrid-Graphics)
  [0.286326] ACPI BIOS Error (bug): Failure creating 
[\_SB.PCI0.XHC.RHUB.HS01._UPC], AE_ALREADY_EXISTS (20181213/dswload2-324)
  [0.286332] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog 
(20181213/psobject-221)
  [0.286334] ACPI: Skipping parse of AML opcode: Method (0x0014)
  [0.286336] ACPI BIOS Error (bug): Failure creating 
[\_SB.PCI0.XHC.RHUB.HS01._PLD], AE_ALREADY_EXISTS (20181213/dswload2-324)
  [0.286339] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog 
(20181213/psobject-221)
  [0.286340] ACPI: Skipping parse of AML opcode: Method (0x0014)
  [0.287096] ACPI BIOS Error (bug): Failure creating 
[\_SB.PCI0.XHC.RHUB.HS02._UPC], AE_ALREADY_EXISTS (20181213/dswload2-324)
  [0.287099] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog 
(20181213/psobject-221)
  [0.287101] ACPI: Skipping parse of AML opcode: Method (0x0014)
  [0.287102] ACPI BIOS Error (bug): Failure creating 
[\_SB.PCI0.XHC.RHUB.HS02._PLD], AE_ALREADY_EXISTS (20181213/dswload2-324)
  [0.287105] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog 
(20181213/psobject-221)
  [0.287106] ACPI: Skipping parse of AML opcode: Method (0x0014)
  [0.287858] ACPI BIOS Error (bug): Failure creating 
[\_SB.PCI0.XHC.RHUB.HS03._UPC], AE_ALREADY_EXISTS (20181213/dswload2-324)
  [0.287861] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog 
(20181213/psobject-221)
  [0.287863] ACPI: Skipping parse of AML opcode: Method (0x0014)
  [0.287864] ACPI BIOS Error (bug): Failure creating 
[\_SB.PCI0.XHC.RHUB.HS03._PLD], AE_ALREADY_EXISTS (20181213/dswload2-324)
  [0.287867] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog 
(20181213/psobject-221)
  [0.287869] ACPI: Skipping parse of AML opcode: Method (0x0014)
  [0.288614] ACPI BIOS Error (bug): Failure creating 
[\_SB.PCI0.XHC.RHUB.HS04._UPC], AE_ALREADY_EXISTS (20181213/dswload2-324)
  [0.288617] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog 
(20181213/psobject-221)
  [0.288619] ACPI: Skipping parse of AML opcode: Method (0x0014)
  [0.288620] ACPI BIOS Error (bug): 

[Touch-packages] [Bug 1821609] Re: lightdm login screen briefly appears and then blanks out on Intel(R) Core(TM)2 Duo CPU T5870

[Ubuntu QA Website]

This bug has been reported on the Ubuntu ISO testing tracker.

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

** Tags added: iso-testing

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

Title:
  lightdm login screen briefly appears and then blanks out on Intel(R)
  Core(TM)2 Duo CPU T5870

Status in xorg package in Ubuntu:
  New

Bug description:
  Okay the has happened recently at least since march 18, 2019 iso and
  march 22, 2019 iso are both effected very similar to one of my
  previously reported bugs .. which was related to xorg not being
  installed ..

  
  back ground .. PC is lenovo sl 500 with evo860 SSD drive

  3 partions contain installs of disco sda1 -- main working system -- I
  usually install grub from here as master ..

  sda6 and sda7 are test installs of disco daily iso's 03-18-2019,
  03-22-2019 repectively

  
  on the test installs as long as the iso is using the grub boot loader 
installed from that install the system will boot normally .. the display manger 
tends to flicker on and off but does final start and login can proceed. 

  but if another install re-installs grub as master  the display manager
  fails to stay active or even come-up  for sda6 or sda7 only if their
  own grubs are reinstalled will they work normally

  sda1 display manager/xorg login works always no matter which "grub-
  source" is in control.

  if I use rescue boot from any grub as master I can get the displays to work 
by running dpkg fix which does nothing .. and then resuming the boot .. then 
things work normally..
  if the "non-rescue" boots are used the screen/computer locks and only a power 
down and reboot gives access. (sometime requiring radical depowering .. 
unpluging and removing battery)

  now the is a message that appears that RCs??? level is missing.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xorg 1:7.7+19ubuntu11
  ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0
  Uname: Linux 5.0.0-7-generic x86_64
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Mon Mar 25 11:25:58 2019
  DistUpgraded: Fresh install
  DistroCodename: disco
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GpuHangFrequency: Several times a day
  GpuHangReproducibility: Yes, I can easily reproduce it
  GpuHangStarted: Immediately after installing this version of Ubuntu
  GraphicsCard:
   Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller 
[8086:2a42] (rev 07) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller 
[17aa:20e4]
 Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller 
[17aa:20e4]
  InstallationDate: Installed on 2019-03-23 (1 days ago)
  InstallationMedia: Xubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190322)
  MachineType: LENOVO 2746CTO
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-7-generic 
root=UUID=1d61086d-275b-4537-bed5-f2d3080670eb ro recovery nomodeset
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2010
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6AET64WW
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: 2746CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: LENOVO 6AET64WW
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: LENOVO 6AET64WW
  dmi.modalias: 
dmi:bvnLENOVO:bvr6AET64WW:bd12/01/2010:svnLENOVO:pn2746CTO:pvrThinkPadSL500:rvnLENOVO:rn2746CTO:rvrLENOVO6AET64WW:cvnLENOVO:ct10:cvrLENOVO6AET64WW:
  dmi.product.name: 2746CTO
  dmi.product.version: ThinkPad SL500
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.0-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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