date:20240117

[Desktop-packages] [Bug 2043915] Re: Booting into live session results in try/install page white screen

2024-01-17 Thread Daniel van Vugt

I can't seem to reproduce any such issue with 2024-01-17 here.

Please log a new bug, although it might be bug 2049617 as mentioned in
https://discourse.ubuntu.com/t/help-with-edubuntu-desktop-
installer/41683

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

Title:
  Booting into live session results in try/install page white screen

Status in ubuntu-desktop-installer:
  Fix Released
Status in mesa package in Ubuntu:
  Fix Released

Bug description:
  Testing Ubuntu Noble desktop daily ISO dated 19-11-2023 - Booting into
  live session results in try/install page white screen.Selecting
  install from the dash results in same white screen.

  see the attached screen shot

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: subiquity (unknown)
  ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
  Uname: Linux 6.5.0-9-generic x86_64
  NonfreeKernelModules: zfs
  ApportVersion: 2.27.0-0ubuntu6
  Architecture: amd64
  CasperMD5CheckResult: pass
  CasperVersion: 1.487
  CloudArchitecture: x86_64
  CloudID: nocloud
  CloudName: unknown
  CloudPlatform: nocloud
  CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud)
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Nov 19 07:02:48 2023
  LiveMediaBuild: Ubuntu 24.04 "Noble Numbat" - Daily amd64 (20231119)
  ProcEnviron:
   LANG=C.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  SourcePackage: subiquity
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-desktop-installer/+bug/2043915/+subscriptions


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

[Desktop-packages] [Bug 2043915] Re: Booting into live session results in try/install page white screen

2024-01-17 Thread Bagus Tris

I tried daily build version 2024-01-17, but the bug is still there.
Laptop is Fujitsu WUA/H1. The solution is to restart subiquity snap
service.

https://askubuntu.com/questions/1500457/ubuntu-desktop-
installer-24-04-stuck-on-
installation?noredirect=1#comment2629138_1500457

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

Title:
  Booting into live session results in try/install page white screen

Status in ubuntu-desktop-installer:
  Fix Released
Status in mesa package in Ubuntu:
  Fix Released

Bug description:
  Testing Ubuntu Noble desktop daily ISO dated 19-11-2023 - Booting into
  live session results in try/install page white screen.Selecting
  install from the dash results in same white screen.

  see the attached screen shot

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: subiquity (unknown)
  ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
  Uname: Linux 6.5.0-9-generic x86_64
  NonfreeKernelModules: zfs
  ApportVersion: 2.27.0-0ubuntu6
  Architecture: amd64
  CasperMD5CheckResult: pass
  CasperVersion: 1.487
  CloudArchitecture: x86_64
  CloudID: nocloud
  CloudName: unknown
  CloudPlatform: nocloud
  CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud)
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Nov 19 07:02:48 2023
  LiveMediaBuild: Ubuntu 24.04 "Noble Numbat" - Daily amd64 (20231119)
  ProcEnviron:
   LANG=C.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  SourcePackage: subiquity
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-desktop-installer/+bug/2043915/+subscriptions


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

[Desktop-packages] [Bug 2049697] Re: GPU not being detected when I try to run any game

2024-01-17 Thread Daniel van Vugt

Thanks for the bug report. It looks like the i915 kernel graphics driver
is crashing a lot, which may or may not be related. Please run these
commands in a Terminal:

  sudo apt install mesa-utils
  glxinfo > glxinfo.txt

and attach the resulting text file here.


** Package changed: xorg (Ubuntu) => linux-hwe-6.2 (Ubuntu)

** Summary changed:

- GPU not being detected when I try to run any game
+ [i915] GPU not being detected when I try to run any game

** Changed in: linux-hwe-6.2 (Ubuntu)
   Status: New => Incomplete

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

Title:
  [i915] GPU not being detected when I try to run any game

Status in linux-hwe-6.2 package in Ubuntu:
  Incomplete

Bug description:
  I ran ran apport-bug xorg and it took me here. Trying to figure out an
  issue where any time I open a game, it crashes and gives the error
  message "GPU not detected". From everything I've tried it seems like
  the computer has no problem detecting the GPU and it seems to be
  working fine, but games are still not working. Any help is
  appreciated!

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.2.0-35.35~22.04.1-generic 6.2.16
  Uname: Linux 6.2.0-35-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jan 17 18:34:19 2024
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  DkmsStatus: bcmwl/6.30.223.271+bdcom, 6.2.0-35-generic, x86_64: installed
  DpkgLog:
   
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Device [8086:0d22] (rev 08) (prog-if 00 [VGA controller])
 Subsystem: Apple Inc. Device [106b:0122]
  InstallationDate: Installed on 2023-10-25 (84 days ago)
  InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.2)
  MachineType: Apple Inc. iMac14,1
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-35-generic 
root=UUID=773b635d-a617-4aa4-8333-273b3ed7b502 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/10/2020
  dmi.bios.release: 0.1
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: 146.0.0.0.0
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-031B6874CF7F642A
  dmi.board.vendor: Apple Inc.
  dmi.board.version: iMac14,1
  dmi.chassis.type: 13
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-031B6874CF7F642A
  dmi.modalias: 
dmi:bvnAppleInc.:bvr146.0.0.0.0:bd06/10/2020:br0.1:svnAppleInc.:pniMac14,1:pvr1.0:rvnAppleInc.:rnMac-031B6874CF7F642A:rvriMac14,1:cvnAppleInc.:ct13:cvrMac-031B6874CF7F642A:skuSystemSKU#:
  dmi.product.family: iMac
  dmi.product.name: iMac14,1
  dmi.product.sku: System SKU#
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~22.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-hwe-6.2/+bug/2049697/+subscriptions


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

[Desktop-packages] [Bug 2049665] Re: A recent Ubuntu update broke GPU processing in Folding@Home (nVidia GPU)

2024-01-17 Thread Daniel van Vugt

Thanks for the bug report. It appears you no longer have an nvidia
kernel driver for the current kernel version. I'm also not sure if such
a newer kernel can be supported by the old nvidia 390 driver.

This might just be bug 1975650 so please try reinstalling the driver
using the 'Additional Drivers' app or:

  sudo apt install --reinstall nvidia-driver-390

and reboot. If reinstalling the driver doesn't solve the problem then I
wonder if nvidia-390 requires sticking to an older kernel?

** Package changed: xorg (Ubuntu) => linux-hwe-6.5 (Ubuntu)

** Tags added: nvidia

** Tags added: regression-update

** Also affects: nvidia-graphics-drivers-390 (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  A recent Ubuntu update broke GPU processing in Folding@Home (nVidia
  GPU)

Status in linux-hwe-6.5 package in Ubuntu:
  New
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  New

Bug description:
  A recent Ubuntu update is keeping the GPU software of Folding at Home
  (Folding@Home) from working.  Past updates have not interfered with
  it.

  Expected result:
  An updated nvidia (proprietary) driver would be installed with the update 
that continues to work smoothly, provides OpenCL, etc.

  Actual result:
  The update caused FAH to disable its GPU processing capabilities.  OpenCL is 
mentioned in the error message, so there may be something wrong with the OpenCL 
installation in the nVidia v390 package.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3
  Uname: Linux 6.5.0-14-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jan 17 12:18:33 2024
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  DkmsStatus: bcmwl/6.30.223.271+bdcom, 6.5.0-14-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation GK107M [GeForce GT 750M Mac Edition] [10de:0fe9] (rev a1) 
(prog-if 00 [VGA controller])
 Subsystem: Apple Inc. GK107M [GeForce GT 750M Mac Edition] [106b:011e]
  InstallationDate: Installed on 2024-01-16 (1 days ago)
  InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 
(20230223)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 006: ID 05ac:828d Apple, Inc. Bluetooth USB Host Controller
   Bus 001 Device 003: ID 0a5c:4500 Broadcom Corp. BCM2046B1 USB 2.0 Hub (part 
of BCM2046 Bluetooth)
   Bus 001 Device 002: ID 05ac:8511 Apple, Inc. FaceTime HD Camera (Built-in)
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Apple Inc. iMac14,3
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-14-generic 
root=UUID=567a07dc-70f9-441e-a456-151c0da1e7ea ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/18/2022
  dmi.bios.release: 0.1
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: 433.140.2.0.0
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-77EB7D7DAF985301
  dmi.board.vendor: Apple Inc.
  dmi.board.version: iMac14,3
  dmi.chassis.type: 13
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-77EB7D7DAF985301
  dmi.modalias: 
dmi:bvnAppleInc.:bvr433.140.2.0.0:bd04/18/2022:br0.1:svnAppleInc.:pniMac14,3:pvr1.0:rvnAppleInc.:rnMac-77EB7D7DAF985301:rvriMac14,3:cvnAppleInc.:ct13:cvrMac-77EB7D7DAF985301:skuSystemSKU#:
  dmi.product.family: iMac
  dmi.product.name: iMac14,3
  dmi.product.sku: System SKU#
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~22.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-hwe-6.5/+bug/2049665/+subscriptions


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

[Desktop-packages] [Bug 2049712] [NEW] Acer Switch Alpha 12: Keyboard does not wake after suspend

2024-01-17 Thread Kenneth Hanson

Public bug reported:

This is a tablet computer with a detachable keyboard and touchpad. When
I close and open the lid, the computer goes to sleep and wakes up as
expected, but the entire keyboard portion does not. The backlight stays
off, and keys and touchpad are unresponsive. Removing and reattaching
the keyboard is the only way to fix the problem.

This problem has been present as long as I've had the tablet (2022),
with queries on the web going back to when the computer was released
(2016). However, I can't find a bug report, so I'm posting one now.

Perhaps related: if I try to sleep via the DE (KDE Plasma), command
line, or power button, the computer fails to go to sleep. The screen
turns back on with the lock screen, and the keyboard backlight does not
go off.

Release: Kubuntu 23.10
Package version: 1.4.1.19

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

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

Title:
  Acer Switch Alpha 12: Keyboard does not wake after suspend

Status in pm-utils package in Ubuntu:
  New

Bug description:
  This is a tablet computer with a detachable keyboard and touchpad.
  When I close and open the lid, the computer goes to sleep and wakes up
  as expected, but the entire keyboard portion does not. The backlight
  stays off, and keys and touchpad are unresponsive. Removing and
  reattaching the keyboard is the only way to fix the problem.

  This problem has been present as long as I've had the tablet (2022),
  with queries on the web going back to when the computer was released
  (2016). However, I can't find a bug report, so I'm posting one now.

  Perhaps related: if I try to sleep via the DE (KDE Plasma), command
  line, or power button, the computer fails to go to sleep. The screen
  turns back on with the lock screen, and the keyboard backlight does
  not go off.

  Release: Kubuntu 23.10
  Package version: 1.4.1.19

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


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

[Desktop-packages] [Bug 2049708] [NEW] bluez bluetoothd unable to locate executable

2024-01-17 Thread theofficialgman

Public bug reported:

Release: Ubuntu Noble Dev Branch

the location of bluetoothd was just changed to
/usr/libexec/bluetooth/bluetoothd

this causes bluetooth to fail to start since something is still looking
for the old location

Jan 17 21:23:26 switch systemd[1]: Starting bluetooth.service - Bluetooth 
service...
░░ Subject: A start job for unit bluetooth.service has begun execution
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ A start job for unit bluetooth.service has begun execution.
░░
░░ The job identifier is 2843.
Jan 17 21:23:26 switch (uetoothd)[3245]: ConfigurationDirectory 'bluetooth' 
already exists but the mode is different. (File system: 755 ConfigurationDire>
Jan 17 21:23:26 switch (uetoothd)[3245]: bluetooth.service: Failed to locate 
executable /usr/lib/bluetooth/bluetoothd: No such file or directory
░░ Subject: Process /usr/lib/bluetooth/bluetoothd could not be executed
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ The process /usr/lib/bluetooth/bluetoothd could not be executed and failed.
░░
░░ The error number returned by this process is ERRNO.
Jan 17 21:23:26 switch (uetoothd)[3245]: bluetooth.service: Failed at step EXEC 
spawning /usr/lib/bluetooth/bluetoothd: No such file or directory

the system service ExecStart location was correctly updated so not sure
what still has the old location

cat /lib/systemd/system/bluetooth.service
[Unit]
Description=Bluetooth service
Documentation=man:bluetoothd(8)
ConditionPathIsDirectory=/sys/class/bluetooth

[Service]
Type=dbus
BusName=org.bluez
ExecStart=/usr/libexec/bluetooth/bluetoothd

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

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

Title:
  bluez bluetoothd unable to locate executable

Status in bluez package in Ubuntu:
  New

Bug description:
  Release: Ubuntu Noble Dev Branch

  the location of bluetoothd was just changed to
  /usr/libexec/bluetooth/bluetoothd

  this causes bluetooth to fail to start since something is still
  looking for the old location

  Jan 17 21:23:26 switch systemd[1]: Starting bluetooth.service - Bluetooth 
service...
  ░░ Subject: A start job for unit bluetooth.service has begun execution
  ░░ Defined-By: systemd
  ░░ Support: http://www.ubuntu.com/support
  ░░
  ░░ A start job for unit bluetooth.service has begun execution.
  ░░
  ░░ The job identifier is 2843.
  Jan 17 21:23:26 switch (uetoothd)[3245]: ConfigurationDirectory 'bluetooth' 
already exists but the mode is different. (File system: 755 ConfigurationDire>
  Jan 17 21:23:26 switch (uetoothd)[3245]: bluetooth.service: Failed to locate 
executable /usr/lib/bluetooth/bluetoothd: No such file or directory
  ░░ Subject: Process /usr/lib/bluetooth/bluetoothd could not be executed
  ░░ Defined-By: systemd
  ░░ Support: http://www.ubuntu.com/support
  ░░
  ░░ The process /usr/lib/bluetooth/bluetoothd could not be executed and failed.
  ░░
  ░░ The error number returned by this process is ERRNO.
  Jan 17 21:23:26 switch (uetoothd)[3245]: bluetooth.service: Failed at step 
EXEC spawning /usr/lib/bluetooth/bluetoothd: No such file or directory

  the system service ExecStart location was correctly updated so not
  sure what still has the old location

  cat /lib/systemd/system/bluetooth.service
  [Unit]
  Description=Bluetooth service
  Documentation=man:bluetoothd(8)
  ConditionPathIsDirectory=/sys/class/bluetooth

  [Service]
  Type=dbus
  BusName=org.bluez
  ExecStart=/usr/libexec/bluetooth/bluetoothd

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


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

[Desktop-packages] [Bug 2049660] Re: screen artifacts especially when changing workspaces

2024-01-17 Thread Daniel van Vugt

Thanks for the bug report. I've watched the attached screencast a few
times and can't see any artifacts in it. This is unsurprising given how
screen recording works. You will probably need to take a video of the
screen externally, like with a phone.


** Summary changed:

- screen artifacts especially when changing workspaces
+ [HP Pavilion Plus Laptop 14] Screen artifacts especially when changing 
workspaces

** Summary changed:

- [HP Pavilion Plus Laptop 14] Screen artifacts especially when changing 
workspaces
+ [amdgpu][HP Pavilion Plus Laptop 14] Screen artifacts especially when 
changing workspaces

** Package changed: xorg (Ubuntu) => linux-hwe-6.5 (Ubuntu)

** Tags added: amdgpu

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

Title:
  [amdgpu][HP Pavilion Plus Laptop 14] Screen artifacts especially when
  changing workspaces

Status in linux-hwe-6.5 package in Ubuntu:
  Incomplete

Bug description:
  Installed fresh, artifacts started after update. Happens when
  interacting gnome; menus, changing workspaces, etc. Attached
  screencast

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3
  Uname: Linux 6.5.0-14-generic x86_64
  NonfreeKernelModules: zfs
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jan 17 17:55:34 2024
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Device [1002:15bf] (rev c9) (prog-if 
00 [VGA controller])
 Subsystem: Hewlett-Packard Company Device [103c:8c21]
  InstallationDate: Installed on 2024-01-09 (7 days ago)
  InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.2)
  MachineType: HP HP Pavilion Plus Laptop 14-ey0xxx
  ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_7trxt5@/vmlinuz-6.5.0-14-generic 
root=ZFS=rpool/ROOT/ubuntu_7trxt5 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/10/2023
  dmi.bios.release: 15.2
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.02
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 8C21
  dmi.board.vendor: HP
  dmi.board.version: 87.27
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.ec.firmware.release: 87.27
  dmi.modalias: 
dmi:bvnInsyde:bvrF.02:bd08/10/2023:br15.2:efr87.27:svnHP:pnHPPavilionPlusLaptop14-ey0xxx:pvrType1ProductConfigId:rvnHP:rn8C21:rvr87.27:cvnHP:ct10:cvrChassisVersion:sku8Y7M1EA#ABH:
  dmi.product.family: 103C_5335KV HP Pavilion
  dmi.product.name: HP Pavilion Plus Laptop 14-ey0xxx
  dmi.product.sku: 8Y7M1EA#ABH
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~22.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 23.0.4-0ubuntu1~22.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-hwe-6.5/+bug/2049660/+subscriptions


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

[Desktop-packages] [Bug 2049697] [NEW] GPU not being detected when I try to run any game

2024-01-17 Thread Justin Klassen

Public bug reported:

I ran ran apport-bug xorg and it took me here. Trying to figure out an
issue where any time I open a game, it crashes and gives the error
message "GPU not detected". From everything I've tried it seems like the
computer has no problem detecting the GPU and it seems to be working
fine, but games are still not working. Any help is appreciated!

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.2.0-35.35~22.04.1-generic 6.2.16
Uname: Linux 6.2.0-35-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Wed Jan 17 18:34:19 2024
DistUpgraded: Fresh install
DistroCodename: jammy
DistroVariant: ubuntu
DkmsStatus: bcmwl/6.30.223.271+bdcom, 6.2.0-35-generic, x86_64: installed
DpkgLog:
 
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation Device [8086:0d22] (rev 08) (prog-if 00 [VGA controller])
   Subsystem: Apple Inc. Device [106b:0122]
InstallationDate: Installed on 2023-10-25 (84 days ago)
InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.2)
MachineType: Apple Inc. iMac14,1
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-35-generic 
root=UUID=773b635d-a617-4aa4-8333-273b3ed7b502 ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/10/2020
dmi.bios.release: 0.1
dmi.bios.vendor: Apple Inc.
dmi.bios.version: 146.0.0.0.0
dmi.board.asset.tag: Base Board Asset Tag#
dmi.board.name: Mac-031B6874CF7F642A
dmi.board.vendor: Apple Inc.
dmi.board.version: iMac14,1
dmi.chassis.type: 13
dmi.chassis.vendor: Apple Inc.
dmi.chassis.version: Mac-031B6874CF7F642A
dmi.modalias: 
dmi:bvnAppleInc.:bvr146.0.0.0.0:bd06/10/2020:br0.1:svnAppleInc.:pniMac14,1:pvr1.0:rvnAppleInc.:rnMac-031B6874CF7F642A:rvriMac14,1:cvnAppleInc.:ct13:cvrMac-031B6874CF7F642A:skuSystemSKU#:
dmi.product.family: iMac
dmi.product.name: iMac14,1
dmi.product.sku: System SKU#
dmi.product.version: 1.0
dmi.sys.vendor: Apple Inc.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~22.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1

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


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

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

Title:
  GPU not being detected when I try to run any game

Status in xorg package in Ubuntu:
  New

Bug description:
  I ran ran apport-bug xorg and it took me here. Trying to figure out an
  issue where any time I open a game, it crashes and gives the error
  message "GPU not detected". From everything I've tried it seems like
  the computer has no problem detecting the GPU and it seems to be
  working fine, but games are still not working. Any help is
  appreciated!

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.2.0-35.35~22.04.1-generic 6.2.16
  Uname: Linux 6.2.0-35-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jan 17 18:34:19 2024
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  DkmsStatus: bcmwl/6.30.223.271+bdcom, 6.2.0-35-generic, x86_64: installed
  DpkgLog:
   
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Device [8086:0d22] (rev 08) (prog-if 00 [VGA controller])
 Subsystem: Apple Inc. Device [106b:0122]
  InstallationDate: Installed on 2023-10-25 (84 days ago)
  InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.2)
  MachineType: Apple Inc. iMac14,1
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-35-generic 
root=UUID=773b635d-a617-4aa4-8333-273b3ed7b502 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/10/2020
  dmi.bios.release: 0.1
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: 146.0.0.0.0
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-031B6874CF7F642A
  dmi.board.vendor: Apple Inc.
  dmi.board.version: iMac14,1

[Desktop-packages] [Bug 1845732] Re: nautilus --check stuck after nautilus_self_check_directory

2024-01-17 Thread Bug Watch Updater

** Changed in: nautilus
   Status: New => Fix Released

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

Title:
  nautilus --check stuck after nautilus_self_check_directory

Status in Nautilus:
  Fix Released
Status in nautilus package in Ubuntu:
  Triaged

Bug description:
  According to
nautilus --help
  there is an option
-c, --checkPerform a quick set of self-check tests.

  Running 'nautilus --check' on the 19.10 beta or on 18.04.3 prints:
running nautilus_self_check_file_utilities
running nautilus_self_check_file_operations
running nautilus_self_check_directory

  And then it just sits there. This is probably not intended.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: nautilus 1:3.34.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-12.13-generic 5.3.0
  Uname: Linux 5.3.0-12-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep 27 23:33:12 2019
  GsettingsChanges:
   
  InstallationDate: Installed on 2019-09-27 (0 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Beta amd64 (20190926.1)
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_nautilus:

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


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

[Desktop-packages] [Bug 2049493] Re: Newer rustc version needed in jammy to build chromium updates

2024-01-17 Thread Nathan Teodosio

Thanks for the backport. I launched builds in
https://launchpad.net/~nteodosio/+snap/chromium-rust and will report
back with the results once available.

** Also affects: chromium-browser (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: chromium-browser (Ubuntu)
 Assignee: (unassigned) => Nathan Teodosio (nteodosio)

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

Title:
  Newer rustc version needed in jammy to build chromium updates

Status in chromium-browser package in Ubuntu:
  New
Status in rustc package in Ubuntu:
  New

Bug description:
  The next chromium version is making rustc mandatory to build. Chromium
  is a snap built from core22 so using the jammy packages, the build is
  currently failing because it needs libprofiler_builtins.rlib which
  isn't available.

  Upstream provides toolchain builds that can be used but only for amd64 so 
currently the snap is failing to build on arm
  https://launchpad.net/~chromium-team/+snap/chromium-snap-from-source-beta

  The version upstream is using is 1.75 but it's possible that a lower
  version would be enough for now if libprofiler was enabled

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


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

[Desktop-packages] [Bug 2046150] Re: [BPO] libreoffice 7.5.9 for jammy

2024-01-17 Thread Dan Streetman

approved, very sorry for the long delay.

** Changed in: libreoffice (Ubuntu Jammy)
   Status: In Progress => Fix Committed

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

Title:
  [BPO] libreoffice 7.5.9 for jammy

Status in libreoffice package in Ubuntu:
  Fix Released
Status in libreoffice source package in Jammy:
  Fix Committed

Bug description:
  [Impact]

   * LibreOffice 7.5.9 is in its ninth and last bugfix release of the 7.5 line:
   https://wiki.documentfoundation.org/ReleasePlan/7.5#7.5.9_release

   * This source packages matches the proposed SRU for lunar handled at
   https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/2044369

  [Scope]

   * Backport of
  https://launchpad.net/ubuntu/+source/libreoffice/4:7.5.9-0ubuntu0.23.04.1

   * Backport target is Jammy/22.04 LTS releases to provide an official
  build of a more recent upstream version of LibreOffice

  [Testing]

   * Upstream testing. Bugs fixed upstream typically include
  unit/regression tests, and the release itself is extensively exercised
  (both in an automated manner and manually).

    * A recent set of upstream's automated jenkins testing can be found here:
  https://ci.libreoffice.org/job/gerrit_75/1776/

    * More information about the upstream QA testing can be found here:
  * Automated tests
    https://wiki.documentfoundation.org/QA/Testing/Automated_Tests
  * Automated UI tests
    https://wiki.documentfoundation.org/Development/UITests
  * Regression tests
    https://wiki.documentfoundation.org/QA/Testing/Regression_Tests
  * Feature tests
    https://wiki.documentfoundation.org/QA/Testing/Feature_Tests

   * Launchpad testing. The libreoffice packages include autopkgtests
  that were run and verified as passing.

     Jammy/22.04 build at 
https://launchpad.net/~libreoffice/+archive/ubuntu/libreoffice-still/+sourcepub/15416837/+listing-archive-extra
  * [amd64] 
https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-libreoffice-libreoffice-still/jammy/amd64/libr/libreoffice/20231208_123108_1b879@/log.gz
  * [arm64] 
https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-libreoffice-libreoffice-still/jammy/arm64/libr/libreoffice/20231208_175608_c3b14@/log.gz
  * [armhf] ... (autopkgtests infra problems on this arch)
  * [ppc64el] 
https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-libreoffice-libreoffice-still/jammy/ppc64el/libr/libreoffice/20231208_135706_f6680@/log.gz
  * [riscv64] not available
  * [s390x] 
https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-libreoffice-libreoffice-still/jammy/s390x/libr/libreoffice/20231208_150850_45529@/log.gz

   * General smoke testing of all the applications in the office suite
  were carried out by going through the manual testplan as documented
  by: https://wiki.ubuntu.com/Process/Merges/TestPlans/libreoffice

  [Regression Potential]

   * A combination of autopkgtests and careful smoke testing as
  described above should provide reasonable confidence that no
  regressions sneaked in.

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


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

[Desktop-packages] [Bug 2049679] [NEW] firefox armhf/arm64 failing to build on 18.04/20.04

2024-01-17 Thread theofficialgman

Public bug reported:

Firefox armhf and arm64 have been failing to build on 18.04 and 20.04 on
mozillateam/ppa for the past couple of weeks.

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

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

Title:
  firefox armhf/arm64 failing to build on 18.04/20.04

Status in firefox package in Ubuntu:
  New

Bug description:
  Firefox armhf and arm64 have been failing to build on 18.04 and 20.04
  on mozillateam/ppa for the past couple of weeks.

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


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

[Desktop-packages] [Bug 1922414] Re: Xorg scripts fail with "has_option: command not found"

2024-01-17 Thread Ken Sharp

** Tags removed: ubuntu

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

Title:
  Xorg scripts fail with "has_option: command not found"

Status in Light Display Manager:
  Invalid
Status in gdm3 package in Ubuntu:
  Fix Released
Status in lightdm package in Ubuntu:
  Invalid
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/lightdm/+bug/1922414/+subscriptions


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

[Desktop-packages] [Bug 2049672] [NEW] Should welcome screen be included?

2024-01-17 Thread Jeremy Bícha

Public bug reported:

Ubuntu 24.04 LTS with gnome-initial-setup 46 Alpha shows these screens:

Help improve Ubuntu
Privacy (Location Services)
Done (You can use App Center to install apps)

This is a change from Ubuntu 23.10 where the first screen was Online
Accounts. See LP: #2049513

Would it be useful to add an intro screen instead of immediately asking
for permission to send data?

GNOME Initial Setup has a page available. We may want to adjust the
wording though since there is no "making an account" for existing users
especially now that Online Accounts is no longer integrated here.
Screenshot attached.

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


** Tags: noble

** Attachment added: "Screenshot from 2024-01-17 13-57-25.png"
   
https://bugs.launchpad.net/bugs/2049672/+attachment/5740280/+files/Screenshot%20from%202024-01-17%2013-57-25.png

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

Title:
  Should welcome screen be included?

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

Bug description:
  Ubuntu 24.04 LTS with gnome-initial-setup 46 Alpha shows these
  screens:

  Help improve Ubuntu
  Privacy (Location Services)
  Done (You can use App Center to install apps)

  This is a change from Ubuntu 23.10 where the first screen was Online
  Accounts. See LP: #2049513

  Would it be useful to add an intro screen instead of immediately
  asking for permission to send data?

  GNOME Initial Setup has a page available. We may want to adjust the
  wording though since there is no "making an account" for existing
  users especially now that Online Accounts is no longer integrated
  here. Screenshot attached.

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


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

[Desktop-packages] [Bug 2037604] Re: Backport packages for 22.04.4 HWE stack

2024-01-17 Thread Timo Aaltonen

Any testing is helpful, thanks!

I've now ran tests on Intel DG2/Arc, and things work fine at least on
6.5 kernel. 6.1 (OEM) fails to start gdm/X with a trace from the DRI
driver, need to investigate if that's a regression or not.

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

Title:
  Backport packages for 22.04.4 HWE stack

Status in directx-headers package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Invalid
Status in rust-bindgen package in Ubuntu:
  Invalid
Status in rust-clang-sys package in Ubuntu:
  Invalid
Status in directx-headers source package in Jammy:
  Fix Committed
Status in mesa source package in Jammy:
  Fix Committed
Status in rust-bindgen source package in Jammy:
  Invalid
Status in rust-clang-sys source package in Jammy:
  Invalid

Bug description:
  [Impact]
  The graphics HWE stack from mantic needs to be backported for 22.04.4

  directx-headers
  - build-dep of the new Mesa

  mesa
  - new major release (23.2.x)
  - new HW support, Meteor Lake..

  [Test case]
  We want to cover at least 2-3 different, widely used and already previously 
supported GPU generations from both AMD and Intel which are supported by this 
release, as those are the ones that cover most bases; nouveau users tend to 
switch to the NVIDIA blob after installation. No need to test ancient GPU's 
supported by mesa-amber. And best to focus on the newer generations (~5y and 
newer) as the older ones are less likely to break at this point.
  - AMD: Vega, Navi1x (RX5000*), Navi2x (RX6000*), Navi3x (RX7000*)
  - Intel: gen9 (SKL/APL/KBL/CFL/WHL/CML), gen11 (ICL), gen12 (TGL/RKL/RPL/DG2)

  Install the new packages and run some tests:
  - check that the desktop is still using hw acceleration and hasn't fallen 
back to swrast/llvmpipe
  - run freely available benchmarks that torture the GPU (Unigine 
Heaven/Valley/Superposition)
  - run some games from Steam if possible

  and in each case check that there is no gfx corruption happening or
  worse.

  Note that upstream releases have already been tested for OpenGL and
  Vulkan conformance by their CI.

  [Where things could go wrong]
  This is a major update of Mesa, there could be regressions but we'll try to 
catch any with testing. And since it shares bugs with mantic, we'd already know 
if there are serious issues. We will backport the final 23.2.x at a later 
stage, the first backport is needed for enabling Intel Meteor Lake.

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


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

[Desktop-packages] [Bug 2049670] [NEW] noble: gnome-initial-setup 20 second delay & error popup

2024-01-17 Thread Jeremy Bícha

Public bug reported:

When GNOME Initial Setup is run in Ubuntu 24.04 LTS (the current
development release), when clicking Next on the "Help improve Ubuntu"
screen, the Initial Setup pauses for 20 seconds then shows a popup
dialog (screenshot attached).

This happens regardless of whether Yes or No is chosen on that screen.

Sometimes, the app might go to the next screen and close the popup
dialog itself.

Logs

GNOME Initial Setup can be run from the command line by running
/usr/libexec/gnome-initial-setup --existing-user

When run from the command line, these warnings are emitted:

InitialSetup-Message: Starting gnome-initial-setup
InitialSetup-Message: Production mode: changes will be saved to disk
INFO[0003] no DCD information: couldn't open /var/lib/ubuntu_dist_channel: open 
/var/lib/ubuntu_dist_channel: no such file or directory 

(gnome-initial-setup): InitialSetup-WARNING **: Failed to send report 
information: data were not delivered successfully to metrics server, saving for 
a later automated report: couldn't send post http request: Post 
"https://metrics.ubuntu.com/ubuntu/desktop/24.04": context deadline exceeded 
(Client.Timeout exceeded while awaiting headers)
INFO[0107] no DCD information: couldn't open /var/lib/ubuntu_dist_channel: open 
/var/lib/ubuntu_dist_channel: no such file or directory

Logs 2
==
If No is selected, the command-line warning is slightly different.

Failed to send report decline: data were not delivered successfully to
metrics server, saving for a later automated report: couldn't send post
http request: Post "https://metrics.ubuntu.com/ubuntu/desktop/24.04":
context deadline exceeded (Client.Timeout exceeded while awaiting
headers)

Other Info
==
Perhaps the metrics server is not set up for Ubuntu 24.04 LTS yet?

This bug is related to bug 1761742 and I agree with comment #3 there.

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


** Tags: noble

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

Title:
  noble: gnome-initial-setup 20 second delay & error popup

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

Bug description:
  When GNOME Initial Setup is run in Ubuntu 24.04 LTS (the current
  development release), when clicking Next on the "Help improve Ubuntu"
  screen, the Initial Setup pauses for 20 seconds then shows a popup
  dialog (screenshot attached).

  This happens regardless of whether Yes or No is chosen on that screen.

  Sometimes, the app might go to the next screen and close the popup
  dialog itself.

  Logs
  
  GNOME Initial Setup can be run from the command line by running
  /usr/libexec/gnome-initial-setup --existing-user

  When run from the command line, these warnings are emitted:

  InitialSetup-Message: Starting gnome-initial-setup
  InitialSetup-Message: Production mode: changes will be saved to disk
  INFO[0003] no DCD information: couldn't open /var/lib/ubuntu_dist_channel: 
open /var/lib/ubuntu_dist_channel: no such file or directory 

  (gnome-initial-setup): InitialSetup-WARNING **: Failed to send report 
information: data were not delivered successfully to metrics server, saving for 
a later automated report: couldn't send post http request: Post 
"https://metrics.ubuntu.com/ubuntu/desktop/24.04": context deadline exceeded 
(Client.Timeout exceeded while awaiting headers)
  INFO[0107] no DCD information: couldn't open /var/lib/ubuntu_dist_channel: 
open /var/lib/ubuntu_dist_channel: no such file or directory

  Logs 2
  ==
  If No is selected, the command-line warning is slightly different.

  Failed to send report decline: data were not delivered successfully to
  metrics server, saving for a later automated report: couldn't send
  post http request: Post
  "https://metrics.ubuntu.com/ubuntu/desktop/24.04": context deadline
  exceeded (Client.Timeout exceeded while awaiting headers)

  Other Info
  ==
  Perhaps the metrics server is not set up for Ubuntu 24.04 LTS yet?

  This bug is related to bug 1761742 and I agree with comment #3 there.

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


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

[Desktop-packages] [Bug 1980889] Re: X crashes with qxl(0): error doing QXL_ALLOC

2024-01-17 Thread minphr

This is affecting me as well. The Xorg stack trace is nearly identical
in my case.

I am using Kubuntu 23.10 as Host and 22.04 LTS as guest.
It is quite annoying as I use the VM for work and this kind of crash happens 
randomly sometimes 5 times per day. 

I noticed it happens every time when I either start typing text or click
something inside the Guest. If the thing I clicked was a text field, the
mouse pointer is stuck as the "I" symbol but I can still move it around
for a few seconds until Xorg dies completely.

I use the VM in a multi-monitor setup with 3 screens.

This is my Video QXL config:

  
  
  


I used the exact same configuration and Guest VM on my "old" pc, that
was running Kubuntu 22.04 LTS as host as well as guest, and I never had
this problem there.

My current pc has an integrated AMD Radeon 780m (does not matter if I used 
AMD's drivers or default ones) and the previous one has integrated Intel Xe G7 
80EUs.
All my software is regularly updated to latest available versions.

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

Title:
  X crashes with qxl(0): error doing QXL_ALLOC

Status in xserver-xorg-video-qxl package in Ubuntu:
  Confirmed

Bug description:
  Have Lubuntu 22.04 installed in a virtual machine created with virt-
  manager. The X server will randomly crash with only Firefox and
  Thunderbird running, with one or the other minimized.

  Old bug reports found online suggested increasing the "vram" setting
  to 256 MiB (262144 in the XML file) fixed this problem, however at
  that setting, it crashed and this latest crash is when the "vram" was
  set to 512 MiB (524288 in the XML file).

  Below is the text from the Xorg.0.log.old file from the point of the
  crash. The crash of the X server terminated this particular log.

  [54.773] (II) event4  - spice vdagent tablet: device is a pointer
  [  3431.844] (EE) qxl(0): error doing QXL_ALLOC
  [  3431.844] (EE)
  [  3431.844] (EE) Backtrace:
  [  3431.861] (EE) 0: /usr/lib/xorg/Xorg (OsLookupColor+0x139) [0x56450cb3f2b9]
  [  3431.863] (EE) 1: /lib/x86_64-linux-gnu/libc.so.6 (__sigaction+0x50) 
[0x7fdab48da520]
  [  3431.864] (EE) unw_get_proc_name failed: no unwind info found [-10]
  [  3431.864] (EE) 2: /usr/lib/xorg/modules/drivers/qxl_drv.so (?+0x0) 
[0x7fdab413fb2d]
  [  3431.865] (EE) unw_get_proc_name failed: no unwind info found [-10]
  [  3431.865] (EE) 3: /usr/lib/xorg/modules/drivers/qxl_drv.so (?+0x0) 
[0x7fdab413ffc7]
  [  3431.866] (EE) unw_get_proc_name failed: no unwind info found [-10]
  [  3431.867] (EE) 4: /usr/lib/xorg/modules/drivers/qxl_drv.so (?+0x0) 
[0x7fdab414c7c0]
  [  3431.869] (EE) 5: /usr/lib/xorg/Xorg (miCopyRegion+0x9b) [0x56450cb1c59b]
  [  3431.870] (EE) 6: /usr/lib/xorg/Xorg (miDoCopy+0x456) [0x56450cb1ccf6]
  [  3431.872] (EE) unw_get_proc_name failed: no unwind info found [-10]
  [  3431.872] (EE) 7: /usr/lib/xorg/modules/drivers/qxl_drv.so (?+0x0) 
[0x7fdab414ca02]
  [  3431.873] (EE) 8: /usr/lib/xorg/Xorg (DamageRegionAppend+0x3886) 
[0x56450caafa86]
  [  3431.873] (EE) 9: /usr/lib/xorg/Xorg (SendGraphicsExpose+0x2cd) 
[0x56450c9c4efd]
  [  3431.874] (EE) 10: /usr/lib/xorg/Xorg (SendErrorToClient+0x365) 
[0x56450c9c94a5]
  [  3431.874] (EE) 11: /usr/lib/xorg/Xorg (InitFonts+0x3c4) [0x56450c9cd524]
  [  3431.876] (EE) 12: /lib/x86_64-linux-gnu/libc.so.6 
(__libc_init_first+0x90) [0x7fdab48c1d90]
  [  3431.878] (EE) 13: /lib/x86_64-linux-gnu/libc.so.6 
(__libc_start_main+0x80) [0x7fdab48c1e40]
  [  3431.878] (EE) 14: /usr/lib/xorg/Xorg (_start+0x25) [0x56450c9b65f5]
  [  3431.878] (EE)
  [  3431.878] (EE) Segmentation fault at address 0x0
  [  3431.878] (EE)
  Fatal server error:
  [  3431.879] (EE) Caught signal 11 (Segmentation fault). Server aborting
  [  3431.879] (EE)
  [  3431.879] (EE)
  Please consult the The X.Org Foundation support
   at http://wiki.x.org
   for help.
  [  3431.879] (EE) Please also check the log file at "/var/log/Xorg.0.log" for 
additional information.
  [  3431.879] (EE)
  [  3431.880] (EE) Server terminated with error (1). Closing log file.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-qxl/+bug/1980889/+subscriptions


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

[Desktop-packages] [Bug 2048388] Re: Test suite often fails with "systemd units changed without reload" on s390x

2024-01-17 Thread Launchpad Bug Tracker

** Merge proposal linked:
   https://code.launchpad.net/~ogayot/britney/+git/britney/+merge/458822

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

Title:
  Test suite often fails with "systemd units changed without reload" on
  s390x

Status in netplan:
  Invalid
Status in netplan.io package in Ubuntu:
  Triaged
Status in wpa package in Ubuntu:
  New

Bug description:
  The "ethernets" autopkgtest for netplan.io 0.107-5ubuntu2 on s390x
  often fails with

  AssertionError: systemd units changed without reload

  Looking at the history of autopkgtest runs, it looks like that the
  error does not always occur during execution of a specific test. I've
  seen occurrences of this error during the following test-cases:

  test_dhcp6 (__main__.TestNetworkd.test_dhcp6) ... FAIL
  test_link_local_ipv4 (__main__.TestNetworkd.test_link_local_ipv4) ... FAIL
  test_eth_mtu (__main__.TestNetworkd.test_eth_mtu) ... FAIL

  Example [1]:

  781s FAIL: test_dhcp6 (__main__.TestNetworkd.test_dhcp6)
  781s --
  781s Traceback (most recent call last):
  781s   File 
"/tmp/autopkgtest.G0qQU0/build.Snp/src/tests/integration/ethernets.py", line 
189, in test_dhcp6
  781s self.generate_and_settle([self.state_dhcp6(self.dev_e_client)])
  781s   File 
"/tmp/autopkgtest.G0qQU0/build.Snp/src/tests/integration/base.py", line 342, in 
generate_and_settle
  781s self.fail('systemd units changed without reload')
  781s AssertionError: systemd units changed without reload

  [1] https://autopkgtest.ubuntu.com/results/autopkgtest-
  noble/noble/s390x/n/netplan.io/20240105_144627_cb35e@/log.gz

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


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

[Desktop-packages] [Bug 2049660] [NEW] screen artifacts especially when changing workspaces

2024-01-17 Thread Michael Drakes

Public bug reported:

Installed fresh, artifacts started after update. Happens when
interacting gnome; menus, changing workspaces, etc. Attached screencast

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3
Uname: Linux 6.5.0-14-generic x86_64
NonfreeKernelModules: zfs
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Wed Jan 17 17:55:34 2024
DistUpgraded: Fresh install
DistroCodename: jammy
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Device [1002:15bf] (rev c9) (prog-if 00 
[VGA controller])
   Subsystem: Hewlett-Packard Company Device [103c:8c21]
InstallationDate: Installed on 2024-01-09 (7 days ago)
InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.2)
MachineType: HP HP Pavilion Plus Laptop 14-ey0xxx
ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_7trxt5@/vmlinuz-6.5.0-14-generic 
root=ZFS=rpool/ROOT/ubuntu_7trxt5 ro quiet splash vt.handoff=1
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/10/2023
dmi.bios.release: 15.2
dmi.bios.vendor: Insyde
dmi.bios.version: F.02
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: 8C21
dmi.board.vendor: HP
dmi.board.version: 87.27
dmi.chassis.asset.tag: Chassis Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: HP
dmi.chassis.version: Chassis Version
dmi.ec.firmware.release: 87.27
dmi.modalias: 
dmi:bvnInsyde:bvrF.02:bd08/10/2023:br15.2:efr87.27:svnHP:pnHPPavilionPlusLaptop14-ey0xxx:pvrType1ProductConfigId:rvnHP:rn8C21:rvr87.27:cvnHP:ct10:cvrChassisVersion:sku8Y7M1EA#ABH:
dmi.product.family: 103C_5335KV HP Pavilion
dmi.product.name: HP Pavilion Plus Laptop 14-ey0xxx
dmi.product.sku: 8Y7M1EA#ABH
dmi.product.version: Type1ProductConfigId
dmi.sys.vendor: HP
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~22.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx 23.0.4-0ubuntu1~22.04.1
version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.7
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1

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


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

** Attachment added: "screencast of changing workspaces to cause artificats"
   
https://bugs.launchpad.net/bugs/2049660/+attachment/5740202/+files/Screencast%20from%2017-01-24%2018%3A11%3A51.webm

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

Title:
  screen artifacts especially when changing workspaces

Status in xorg package in Ubuntu:
  New

Bug description:
  Installed fresh, artifacts started after update. Happens when
  interacting gnome; menus, changing workspaces, etc. Attached
  screencast

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3
  Uname: Linux 6.5.0-14-generic x86_64
  NonfreeKernelModules: zfs
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jan 17 17:55:34 2024
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Device [1002:15bf] (rev c9) (prog-if 
00 [VGA controller])
 Subsystem: Hewlett-Packard Company Device [103c:8c21]
  InstallationDate: Installed on 2024-01-09 (7 days ago)
  InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.2)
  MachineType: HP HP Pavilion Plus Laptop 14-ey0xxx
  ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_7trxt5@/vmlinuz-6.5.0-14-generic 
root=ZFS=rpool/ROOT/ubuntu_7trxt5 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/10/2023
  dmi.bios.release: 15.2
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.02
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 8C21
  dmi.board.vendor: HP
  dmi.board.version: 87.27
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.ec.firmware.release:

[Desktop-packages] [Bug 2048388] Re: Test suite often fails with "systemd units changed without reload" on s390x

2024-01-17 Thread Olivier Gayot

After further analysis, it looks like the trigger=wpa/2:2.10-21 highly
increases the likeliness of the error to occur.

At this point, I do not think that there is any regression in wpa
2:2.10-21 compared to 2:2.10-20. The changeset is minimal. OTOH I think
the trigger=wpa/... alters the order of events and somehow consequently
makes the race condition more likely to occur.

FWIW, with a trigger=wpa/..., wpasupplicant gets upgraded before running
the ethernets test:

 96s Unpacking wpasupplicant (2:2.10-21) over (2:2.10-20) ...

https://autopkgtest.ubuntu.com/results/autopkgtest-noble-ogayot-noble-
proposed//noble/s390x/n/netplan.io/20240109_171235_03058@/log.gz

Whereas. without the trigger, it gets installed:

127s Unpacking wpasupplicant (2:2.10-21) ...

https://autopkgtest.ubuntu.com/results/autopkgtest-noble-ogayot-noble-
proposed//noble/s390x/n/netplan.io/20240109_162248_f656d@/log.gz

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

Title:
  Test suite often fails with "systemd units changed without reload" on
  s390x

Status in netplan:
  Invalid
Status in netplan.io package in Ubuntu:
  Triaged
Status in wpa package in Ubuntu:
  New

Bug description:
  The "ethernets" autopkgtest for netplan.io 0.107-5ubuntu2 on s390x
  often fails with

  AssertionError: systemd units changed without reload

  Looking at the history of autopkgtest runs, it looks like that the
  error does not always occur during execution of a specific test. I've
  seen occurrences of this error during the following test-cases:

  test_dhcp6 (__main__.TestNetworkd.test_dhcp6) ... FAIL
  test_link_local_ipv4 (__main__.TestNetworkd.test_link_local_ipv4) ... FAIL
  test_eth_mtu (__main__.TestNetworkd.test_eth_mtu) ... FAIL

  Example [1]:

  781s FAIL: test_dhcp6 (__main__.TestNetworkd.test_dhcp6)
  781s --
  781s Traceback (most recent call last):
  781s   File 
"/tmp/autopkgtest.G0qQU0/build.Snp/src/tests/integration/ethernets.py", line 
189, in test_dhcp6
  781s self.generate_and_settle([self.state_dhcp6(self.dev_e_client)])
  781s   File 
"/tmp/autopkgtest.G0qQU0/build.Snp/src/tests/integration/base.py", line 342, in 
generate_and_settle
  781s self.fail('systemd units changed without reload')
  781s AssertionError: systemd units changed without reload

  [1] https://autopkgtest.ubuntu.com/results/autopkgtest-
  noble/noble/s390x/n/netplan.io/20240105_144627_cb35e@/log.gz

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


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

[Desktop-packages] [Bug 1961508] Re: Dock displaying over window after resuming from blank screen

2024-01-17 Thread Edward

The problem persists. Ubuntu 23.10 / Gnome 45. I'm so used to just re-
maximizing every window now.

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

Title:
  Dock displaying over window after resuming from blank screen

Status in Dash to dock:
  Unknown
Status in Mutter:
  New
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  Won't Fix
Status in mutter package in Ubuntu:
  In Progress
Status in gnome-desktop package in Fedora:
  Confirmed

Bug description:
  I have Blank Screen set to happen after 2 minutes of inactivity.

  When resuming from a Blank Screen (by moving the mouse or touching the
  keyboard), the Dock is displayed over the top of the current program.

  To get it back to normal I need to click "Restore Down" on the current
  programs window and then "Maximize" so that the Dock no longer
  overlaps it.

  (Note: I have Auto-hide dock turned off.)

  This only happens sometimes. I can't reproduce the bug it every time.

  -

  1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> 
About Ubuntu
  - Ubuntu 21.10

  2) The version of the package you are using, via 'apt-cache policy pkgname' 
or by checking in Software Center
  - Not sure (I guess the Dock is part of the Gnome interface?)

  3) What you expected to happen
  - Dock should not overlap the current program on resume from screen blank.

  4) What happened instead
  - The Dock overlaps the current program on resume from screen blank.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 21.10
  InstallationDate: Installed on 2022-02-18 (24 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  Package: gnome-shell-extension-ubuntu-dock
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.13.0-35.40-generic 5.13.19
  RelatedPackageVersions: mutter-common 40.5-1ubuntu3~21.10.1
  Tags:  wayland-session impish
  Uname: Linux 5.13.0-35-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  --- 
  ProblemType: Bug
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 22.10
  InstallationDate: Installed on 2022-02-18 (328 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  Package: mutter
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.19.0-28.29-generic 5.19.17
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions: mutter-common 43.0-1ubuntu4
  Tags: wayland-session third-party-packages kinetic
  Uname: Linux 5.19.0-28-generic x86_64
  UpgradeStatus: Upgraded to kinetic on 2022-10-25 (79 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/dash-to-dock/+bug/1961508/+subscriptions


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

[Desktop-packages] [Bug 2049630] [NEW] [LE-Beats Studio Pro tilhørende j, playback] Playback problem

2024-01-17 Thread Jan Ulrich Thomsen

Public bug reported:

I am no longer able to change pulseaudio card profile from a2dp_sink to 
handsfree_head_unit
It used to work before running apt upgrade where I got a new kernel 
6.5.0-14-generic #14~22.04.1-Ubuntu installed.  As you can see below - and 
actual experience with the headphones, there is no problem switching to and 
from off and a2dp_sink but I can no longer get to the handsfree_head_unit.

journalctl -b -f gives the follwing error message when trying to
activate the handsfree_head_unit profile:

myleno pulseaudio[405145]: Refused to switch profile to
handsfree_head_unit: Not connected

cut/paste of pacmd command:

list-cards:
..
.
.

index: 2
name: 
driver: 
owner module: 24
properties:
device.description = "Beats Studio Pro tilhørende jan"
device.string = "A4:16:C0:63:87:DD"
device.api = "bluez"
device.class = "sound"
device.bus = "bluetooth"
device.form_factor = "headphone"
bluez.path = "/org/bluez/hci0/dev_A4_16_C0_63_87_DD"
bluez.class = "0x240418"
bluez.alias = "Beats Studio Pro tilhørende jan"
device.icon_name = "audio-headphones-bluetooth"
bluetooth.codec = "sbc_xq_453"
profiles:
a2dp_sink: High Fidelity Playback (A2DP Sink) (priority 40, 
available: unknown)
handsfree_head_unit: Handsfree Head Unit (HFP) (priority 30, 
available: no)
off: Off (priority 0, available: yes)
active profile: 
sinks:
bluez_sink.A4_16_C0_63_87_DD.a2dp_sink/#1: Beats Studio Pro 
tilhørende jan
sources:
bluez_sink.A4_16_C0_63_87_DD.a2dp_sink.monitor/#2: Monitor of 
Beats Studio Pro tilhørende jan
ports:
headphone-output: Headphone (priority 0, latency offset 10 
usec, available: unknown)
properties:

headphone-input: Bluetooth Input (priority 0, latency offset 0 
usec, available: no)
properties:

>>> set-card-profile 2 handsfree_head_unit
Failed to set card profile to 'handsfree_head_unit'.
>>> set-card-profile 2 a2dp_sink 
>>> set-card-profile 2 off
>>> set-card-profile 2 a2dp_sink

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: alsa-base 1.0.25+dfsg-0ubuntu7
ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3
Uname: Linux 6.5.0-14-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  jan2314 F pulseaudio
 /dev/snd/controlC0:  jan2314 F pulseaudio
CasperMD5CheckResult: pass
CurrentDesktop: GNOME
Date: Wed Jan 17 14:58:03 2024
InstallationDate: Installed on 2022-12-08 (404 days ago)
InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_Card: LE-Beats Studio Pro tilhørende j
Symptom_Type: Only some of outputs are working
Title: [LE-Beats Studio Pro tilhørende j, playback] Playback problem
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/23/2022
dmi.bios.release: 1.46
dmi.bios.vendor: LENOVO
dmi.bios.version: GLCN46WW
dmi.board.asset.tag: No Asset Tag
dmi.board.name: LNVNB161216
dmi.board.vendor: LENOVO
dmi.board.version: SDK0T76465WIN
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: IdeaPad 3 17ALC6
dmi.ec.firmware.release: 1.46
dmi.modalias: 
dmi:bvnLENOVO:bvrGLCN46WW:bd03/23/2022:br1.46:efr1.46:svnLENOVO:pn82KV:pvrIdeaPad317ALC6:rvnLENOVO:rnLNVNB161216:rvrSDK0T76465WIN:cvnLENOVO:ct10:cvrIdeaPad317ALC6:skuLENOVO_MT_82KV_BU_idea_FM_IdeaPad317ALC6:
dmi.product.family: IdeaPad 3 17ALC6
dmi.product.name: 82KV
dmi.product.sku: LENOVO_MT_82KV_BU_idea_FM_IdeaPad 3 17ALC6
dmi.product.version: IdeaPad 3 17ALC6
dmi.sys.vendor: LENOVO

** Affects: alsa-driver (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug jammy

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

Title:
  [LE-Beats Studio Pro tilhørende j, playback] Playback problem

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  I am no longer able to change pulseaudio card profile from a2dp_sink to 
handsfree_head_unit
  It used to work before running apt upgrade where I got a new kernel 
6.5.0-14-generic #14~22.04.1-Ubuntu installed.  As you can see below - and 
actual experience with the headphones, there is no problem switching to and 
from off and a2dp_sink but I can no longer get to the handsfree_head_unit.

  journalctl -b -f gives the follwing error message when trying to
  activate the

[Desktop-packages] [Bug 2043591] Re: Starting gnome-control-center resets icon theme

2024-01-17 Thread Eric Donkersloot

Any update available on this bug report?

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

Title:
  Starting gnome-control-center resets icon theme

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

Bug description:
  How to reproduce this bug:

  1. Install a new icon theme like the papirus icon theme 
(https://github.com/PapirusDevelopmentTeam/papirus-icon-theme) or the Tela icon 
theme (https://github.com/vinceliuice/Tela-icon-theme) and activate it via 
Gnome Tweaks.
  2. Click on the Settings app or start gnome-control-center from the terminal.
  3. The icon theme will be reset to Yaru.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: gnome-control-center 1:45.0-1ubuntu2
  ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
  Uname: Linux 6.5.0-10-generic x86_64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Nov 15 15:49:15 2023
  InstallationDate: Installed on 2023-10-12 (34 days ago)
  InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Release amd64 (20231011)
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Desktop-packages] [Bug 2049504] Re: Loading application details window hanged in Ubuntu Software app

2024-01-17 Thread Jeremy Bícha

What version of Ubuntu are you using?

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

Title:
  Loading application details window hanged in Ubuntu Software app

Status in gnome-software package in Ubuntu:
  New

Bug description:
  see attached screenshot

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


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

[Desktop-packages] [Bug 2049510] Re: nautilus randomly crashes

2024-01-17 Thread Sebastien Bacher

Thank you for taking the time to report this bug and helping to make
Ubuntu better. It sounds like some part of the system has crashed. To
help us find the cause of the crash please follow these steps:

1. Run these commands:
journalctl -b0 > journal.txt
journalctl -b-1 > prevjournal.txt
and attach the resulting text files here.

2. Look in /var/crash for crash files and if found run:
ubuntu-bug YOURFILE.crash
Then tell us the ID of the newly-created bug.

3. If step 2 failed then look at https://errors.ubuntu.com/user/ID where
ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine.
Do you find any links to recent problems on that page? If so then please
send the links to us.

Please take care to avoid attaching .crash files to bugs as we are
unable to process them as file attachments. It would also be a security
risk for yourself.


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

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

Title:
  nautilus randomly crashes

Status in nautilus package in Ubuntu:
  Incomplete

Bug description:
  Random crashes in nautilus, especially since moving to 23.10, for
  example while changing directory, while searching for a file.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: nautilus 1:45~rc-1ubuntu1
  ProcVersionSignature: Ubuntu 6.5.0-14.14-generic 6.5.3
  Uname: Linux 6.5.0-14-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 16 14:27:43 2024
  InstallationDate: Installed on 2023-06-06 (224 days ago)
  InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418)
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to mantic on 2023-10-14 (94 days ago)
  usr_lib_nautilus:
   file-roller   43.0-1
   nautilus-extension-gnome-terminal 3.49.92-2ubuntu1
   nautilus-image-converter  0.4.0-2
   python3-nautilus  4.0-1build1

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


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

[Desktop-packages] [Bug 2049434] Re: Nautilus crashes when trying to open file options in administrator mode

2024-01-17 Thread Sebastien Bacher

Thank you for taking the time to report this bug and helping to make
Ubuntu better. It sounds like some part of the system has crashed. To
help us find the cause of the crash please follow these steps:

1. Run these commands:
journalctl -b0 > journal.txt
journalctl -b-1 > prevjournal.txt
and attach the resulting text files here.

2. Look in /var/crash for crash files and if found run:
ubuntu-bug YOURFILE.crash
Then tell us the ID of the newly-created bug.

3. If step 2 failed then look at https://errors.ubuntu.com/user/ID where
ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine.
Do you find any links to recent problems on that page? If so then please
send the links to us.

Please take care to avoid attaching .crash files to bugs as we are
unable to process them as file attachments. It would also be a security
risk for yourself.

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

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

Title:
  Nautilus crashes when trying to open file options in administrator
  mode

Status in nautilus package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 23.10
  nautilus 1:45~rc-1ubuntu1

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: nautilus 1:45~rc-1ubuntu1
  ProcVersionSignature: Ubuntu 6.5.0-14.14-generic 6.5.3
  Uname: Linux 6.5.0-14-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 16 00:46:25 2024
  InstallationDate: Installed on 2024-01-11 (4 days ago)
  InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 
(20231016.1)
  ProcEnviron:
   LANG=ru_RU.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_nautilus:
   file-roller   43.0-1
   nautilus-extension-gnome-terminal 3.49.92-2ubuntu1

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


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

[Desktop-packages] [Bug 2049504] Re: Loading application details window hanged in Ubuntu Software app

2024-01-17 Thread Paul White

** Package changed: ubuntu => gnome-software (Ubuntu)

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

Title:
  Loading application details window hanged in Ubuntu Software app

Status in gnome-software package in Ubuntu:
  New

Bug description:
  see attached screenshot

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


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

[Desktop-packages] [Bug 2049504] [NEW] Loading application details window hanged in Ubuntu Software app

2024-01-17 Thread Launchpad Bug Tracker

You have been subscribed to a public bug:

see attached screenshot

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


** Tags: bot-comment
-- 
Loading application details window hanged in Ubuntu Software app
https://bugs.launchpad.net/bugs/2049504
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to gnome-software in Ubuntu.

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

[Desktop-packages] [Bug 2049596] [NEW] Failed to send report information: data not delivered

2024-01-17 Thread corrado venturini

Public bug reported:

After install click to 'send info to canonical' 'help to improve Ubuntu' fails 
with msg: Failed to send report information... 
see attached screenshot

ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: ubuntu-report 1.7.2
ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3
Uname: Linux 6.6.0-14-generic x86_64
ApportVersion: 2.27.0-0ubuntu6
Architecture: amd64
CasperMD5CheckResult: pass
CloudArchitecture: x86_64
CloudID: none
CloudName: none
CloudPlatform: none
CloudSubPlatform: config
CurrentDesktop: ubuntu:GNOME
Date: Wed Jan 17 10:06:35 2024
InstallationDate: Installed on 2024-01-17 (0 days ago)
InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240117)
ProcEnviron:
 LANG=en_US.UTF-8
 PATH=(custom, no user)
 SHELL=/bin/bash
 TERM=xterm-256color
 XDG_RUNTIME_DIR=
SourcePackage: ubuntu-report
UpgradeStatus: No upgrade log present (probably fresh install)

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


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

** Attachment added: "Screenshot from 2024-01-17 10-05-42.png"
   
https://bugs.launchpad.net/bugs/2049596/+attachment/5740142/+files/Screenshot%20from%202024-01-17%2010-05-42.png

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

Title:
  Failed to send report information: data not delivered

Status in ubuntu-report package in Ubuntu:
  New

Bug description:
  After install click to 'send info to canonical' 'help to improve Ubuntu' 
fails with msg: Failed to send report information... 
  see attached screenshot

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: ubuntu-report 1.7.2
  ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3
  Uname: Linux 6.6.0-14-generic x86_64
  ApportVersion: 2.27.0-0ubuntu6
  Architecture: amd64
  CasperMD5CheckResult: pass
  CloudArchitecture: x86_64
  CloudID: none
  CloudName: none
  CloudPlatform: none
  CloudSubPlatform: config
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jan 17 10:06:35 2024
  InstallationDate: Installed on 2024-01-17 (0 days ago)
  InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240117)
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  SourcePackage: ubuntu-report
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Desktop-packages] [Bug 2048087] Re: RM: obsolete & superseded nvidia-graphics-drivers, leftovers

2024-01-17 Thread Steve Langasek

Removing packages from noble:
nvidia-graphics-drivers-450 450.119.03-0ubuntu1 in noble
libnvidia-cfg1-440 450.119.03-0ubuntu1 in noble amd64
libnvidia-common-440 450.119.03-0ubuntu1 in noble amd64
libnvidia-common-440 450.119.03-0ubuntu1 in noble arm64
libnvidia-common-440 450.119.03-0ubuntu1 in noble armhf
libnvidia-common-440 450.119.03-0ubuntu1 in noble i386
libnvidia-common-440 450.119.03-0ubuntu1 in noble ppc64el
libnvidia-common-440 450.119.03-0ubuntu1 in noble riscv64
libnvidia-common-440 450.119.03-0ubuntu1 in noble s390x
libnvidia-common-450 450.119.03-0ubuntu1 in noble amd64
libnvidia-common-450 450.119.03-0ubuntu1 in noble arm64
libnvidia-common-450 450.119.03-0ubuntu1 in noble armhf
libnvidia-common-450 450.119.03-0ubuntu1 in noble i386
libnvidia-common-450 450.119.03-0ubuntu1 in noble ppc64el
libnvidia-common-450 450.119.03-0ubuntu1 in noble riscv64
libnvidia-common-450 450.119.03-0ubuntu1 in noble s390x
libnvidia-compute-440 450.119.03-0ubuntu1 in noble amd64
libnvidia-compute-440 450.119.03-0ubuntu1 in noble i386
libnvidia-decode-440 450.119.03-0ubuntu1 in noble amd64
libnvidia-decode-440 450.119.03-0ubuntu1 in noble i386
libnvidia-encode-440 450.119.03-0ubuntu1 in noble amd64
libnvidia-encode-440 450.119.03-0ubuntu1 in noble i386
libnvidia-extra-440 450.119.03-0ubuntu1 in noble amd64
libnvidia-extra-440 450.119.03-0ubuntu1 in noble i386
libnvidia-fbc1-440 450.119.03-0ubuntu1 in noble amd64
libnvidia-fbc1-440 450.119.03-0ubuntu1 in noble i386
libnvidia-gl-440 450.119.03-0ubuntu1 in noble amd64
libnvidia-gl-440 450.119.03-0ubuntu1 in noble i386
libnvidia-ifr1-440 450.119.03-0ubuntu1 in noble amd64
libnvidia-ifr1-440 450.119.03-0ubuntu1 in noble i386
nvidia-compute-utils-440 450.119.03-0ubuntu1 in noble amd64
nvidia-dkms-440 450.119.03-0ubuntu1 in noble amd64
nvidia-driver-440 450.119.03-0ubuntu1 in noble amd64
nvidia-headless-440 450.119.03-0ubuntu1 in noble amd64
nvidia-headless-no-dkms-440 450.119.03-0ubuntu1 in noble amd64
nvidia-kernel-common-440 450.119.03-0ubuntu1 in noble amd64
nvidia-kernel-source-440 450.119.03-0ubuntu1 in noble amd64
nvidia-utils-440 450.119.03-0ubuntu1 in noble amd64
xserver-xorg-video-nvidia-440 450.119.03-0ubuntu1 in noble amd64
Comment: Unsupported driver version; LP: #2048087
1 package successfully removed.

** Changed in: nvidia-graphics-drivers-450 (Ubuntu)
   Status: Triaged => Fix Released

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

Title:
  RM: obsolete & superseded nvidia-graphics-drivers, leftovers

Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-430 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-435 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-440 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-450 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-455 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-460 package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-510 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-515 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-515-server package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-530 package in Ubuntu:
  Fix Released

Bug description:
  
https://packages.ubuntu.com/search?suite=noble=all=any=nvidia-
  graphics-drivers=sourcenames

  Currently supported drivers are:
  nvidia-graphics-drivers-470
  nvidia-graphics-drivers-525
  nvidia-graphics-drivers-535
  nvidia-graphics-drivers-470-server
  nvidia-graphics-drivers-525-server
  nvidia-graphics-drivers-535-server

  all other drivers are superseded binaries, from obsolete and/or short-
  lived nvidia-graphics-drivers are however still published in the
  archive.

  please remove them.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/2048087/+subscriptions


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

[Desktop-packages] [Bug 2043915] Re: Booting into live session results in try/install page white screen

[Desktop-packages] [Bug 2043915] Re: Booting into live session results in try/install page white screen

[Desktop-packages] [Bug 2049697] Re: GPU not being detected when I try to run any game

[Desktop-packages] [Bug 2049665] Re: A recent Ubuntu update broke GPU processing in Folding@Home (nVidia GPU)

[Desktop-packages] [Bug 2049712] [NEW] Acer Switch Alpha 12: Keyboard does not wake after suspend

[Desktop-packages] [Bug 2049708] [NEW] bluez bluetoothd unable to locate executable

[Desktop-packages] [Bug 2049660] Re: screen artifacts especially when changing workspaces

[Desktop-packages] [Bug 2049697] [NEW] GPU not being detected when I try to run any game

[Desktop-packages] [Bug 1845732] Re: nautilus --check stuck after nautilus_self_check_directory

[Desktop-packages] [Bug 2049493] Re: Newer rustc version needed in jammy to build chromium updates

[Desktop-packages] [Bug 2046150] Re: [BPO] libreoffice 7.5.9 for jammy

[Desktop-packages] [Bug 2049679] [NEW] firefox armhf/arm64 failing to build on 18.04/20.04

[Desktop-packages] [Bug 1922414] Re: Xorg scripts fail with "has_option: command not found"

[Desktop-packages] [Bug 2049672] [NEW] Should welcome screen be included?

[Desktop-packages] [Bug 2037604] Re: Backport packages for 22.04.4 HWE stack

[Desktop-packages] [Bug 2049670] [NEW] noble: gnome-initial-setup 20 second delay & error popup

[Desktop-packages] [Bug 1980889] Re: X crashes with qxl(0): error doing QXL_ALLOC

[Desktop-packages] [Bug 2048388] Re: Test suite often fails with "systemd units changed without reload" on s390x

[Desktop-packages] [Bug 2049660] [NEW] screen artifacts especially when changing workspaces

[Desktop-packages] [Bug 2048388] Re: Test suite often fails with "systemd units changed without reload" on s390x

[Desktop-packages] [Bug 1961508] Re: Dock displaying over window after resuming from blank screen

[Desktop-packages] [Bug 2049630] [NEW] [LE-Beats Studio Pro tilhørende j, playback] Playback problem

[Desktop-packages] [Bug 2043591] Re: Starting gnome-control-center resets icon theme

[Desktop-packages] [Bug 2049504] Re: Loading application details window hanged in Ubuntu Software app

[Desktop-packages] [Bug 2049510] Re: nautilus randomly crashes

[Desktop-packages] [Bug 2049434] Re: Nautilus crashes when trying to open file options in administrator mode

[Desktop-packages] [Bug 2049504] Re: Loading application details window hanged in Ubuntu Software app

[Desktop-packages] [Bug 2049504] [NEW] Loading application details window hanged in Ubuntu Software app

[Desktop-packages] [Bug 2049596] [NEW] Failed to send report information: data not delivered

[Desktop-packages] [Bug 2048087] Re: RM: obsolete & superseded nvidia-graphics-drivers, leftovers

30 matches

Site Navigation

Mail list logo

Footer information