[Bug 2081052] [NEW] audio

[Dave Andrew]

Public bug reported:

i get sound through speakers for about 30 seconds and then sound cuts
off.sound through a headset is ok

ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: pulseaudio 1:16.1+dfsg1-2ubuntu10
ProcVersionSignature: Ubuntu 6.8.0-45.45-generic 6.8.12
Uname: Linux 6.8.0-45-generic x86_64
ApportVersion: 2.28.1-0ubuntu3.1
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/seq:dave   1388 F pipewire
 /dev/snd/controlC0:  dave   1396 F wireplumber
CasperMD5CheckResult: unknown
CurrentDesktop: KDE
Date: Wed Sep 18 11:23:05 2024
InstallationDate: Installed on 2020-02-07 (1685 days ago)
InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
MachineType: RM Education RM
ProcEnviron:
 LANG=en_GB.UTF-8
 LANGUAGE=en_GB
 PATH=(custom, no user)
 SHELL=/bin/bash
 XDG_RUNTIME_DIR=
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
SourcePackage: pulseaudio
Symptom: audio
UpgradeStatus: Upgraded to noble on 2024-09-18 (0 days ago)
dmi.bios.date: 04/20/2011
dmi.bios.release: 4.6
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 202
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: RM MOBILE ONE 310
dmi.board.vendor: RM Education
dmi.board.version: 1.0
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 10
dmi.chassis.vendor: RM Education
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr202:bd04/20/2011:br4.6:svnRMEducation:pnRM:pvr1.0:rvnRMEducation:rnRMMOBILEONE310:rvr1.0:cvnRMEducation:ct10:cvr1.0:skuTobefilledbyO.E.M.:
dmi.product.family: PEGA Family
dmi.product.name: RM
dmi.product.sku: To be filled by O.E.M.
dmi.product.version: 1.0
dmi.sys.vendor: RM Education
mtime.conffile..etc.init.d.apport: 2024-07-22T15:59:07

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


** Tags: amd64 apport-bug noble

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2081052

Title:
  audio

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2080963] Re: ModuleNotFoundError: No module named 'distutils'

[Andrew Schulman]

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

Sorry. Dup of
https://bugs.launchpad.net/ubuntu/+source/diffuse/+bug/2066030.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2080963

Title:
  ModuleNotFoundError: No module named 'distutils'

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2080963] [NEW] ModuleNotFoundError: No module named 'distutils'

[Andrew Schulman]

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

Public bug reported:

I installed diffuse with apt-get. When I try to start it, it immediately
crashes with "ModuleNotFoundError: No module named 'distutils'". See
traceback below.

andrex@helium ~> diffuse
Traceback (most recent call last):
  File "/usr/bin/diffuse", line 44, in 
from diffuse import main
  File "/usr/share/diffuse/diffuse/main.py", line 26, in 
from diffuse import constants, utils
  File "/usr/share/diffuse/diffuse/utils.py", line 33, in 
from diffuse.resources import theResources
  File "/usr/share/diffuse/diffuse/resources.py", line 33, in 
from distutils import util
ModuleNotFoundError: No module named 'distutils'

When I try to start it from the Gnome shell, nothing happens, so I guess
it also crashes then.

ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: diffuse 0.8.2-1ubuntu1
ProcVersionSignature: Ubuntu 6.8.0-44.44-generic 6.8.12
Uname: Linux 6.8.0-44-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.28.1-0ubuntu3.1
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Tue Sep 17 10:05:46 2024
InstallationDate: Installed on 2024-09-05 (12 days ago)
InstallationMedia: Ubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 
(20240220)
PackageArchitecture: all
RebootRequiredPkgs: Error: path contained symlinks.
SourcePackage: diffuse
UpgradeStatus: Upgraded to noble on 2024-09-05 (12 days ago)
mtime.conffile..etc.init.d.apport: 2024-07-22T10:59:07

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


** Tags: amd64 apport-bug noble

** This bug has been marked a duplicate of bug 2066030
   Package "diffuse" has a dependency on package "python3-distutils-extra" 
which is not automatically installed.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2080963

Title:
  ModuleNotFoundError: No module named 'distutils'

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2080866] Re: lockd: refusing to freeze on S3 suspend; prevents suspend

[Andrew Stiegmann]

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

Sweet.  Thank ya.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2080866

Title:
  lockd: refusing to freeze on S3 suspend; prevents suspend

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2080866] [NEW] lockd: refusing to freeze on S3 suspend; prevents suspend

[Andrew Stiegmann]

Public bug reported:

When I have one of my NFSv3 mounts active, the system will fail to go to
sleep. Kernel trace:

kernel: Freezing user space processes ... (elapsed 0.003 seconds) done.
kernel: OOM killer disabled.
kernel: Freezing remaining freezable tasks ...
kernel: Freezing of tasks failed after 20.003 seconds (1 tasks refusing to 
freeze, wq_busy=0):
kernel: task:lockd   state:I stack:0 pid:174656 ppid: 2 
flags:0x4000
kernel: Call Trace:
kernel:  
kernel:  __schedule+0x24e/0x590
kernel:  schedule+0x69/0x110
kernel:  schedule_timeout+0x105/0x140
kernel:  svc_get_next_xprt+0xf1/0x190 [sunrpc]
kernel:  svc_recv+0x1a9/0x330 [sunrpc]
kernel:  lockd+0xa9/0x1c0 [lockd]
kernel:  ? set_grace_period+0xa0/0xa0 [lockd]
kernel:  kthread+0x127/0x150
kernel:  ? set_kthread_struct+0x50/0x50
kernel:  ret_from_fork+0x1f/0x30
kernel:  

First appeared in linux-image-5.15.0-118-generic, present in linux-
image-5.15.0-119-generic, not present in linux-image-5.15.0-117-generic.

Steps to reproduce:
* Boot linux-image-5.15.0-118-generic or -119
* Mount an nfs share.  Ensure that lockd kernel module is loaded
* Put computer into suspsend, it will fail to enter suspend as the lockd task 
will fail to freeze.

When lockd module is not loaded, system is able to go into S3 without
issue.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: linux-image-5.15.0-118-generic (not installed)
ProcVersionSignature: Ubuntu 5.15.0-117.127-generic 5.15.158
Uname: Linux 5.15.0-117-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu82.6
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  stieg  2541 F pipewire
  stieg  2542 F wireplumber
 /dev/snd/controlC0:  stieg  2542 F wireplumber
 /dev/snd/seq:stieg  2541 F pipewire
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Mon Sep 16 09:01:52 2024
InstallationDate: Installed on 2021-07-13 (1160 days ago)
InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
MachineType: LENOVO 20Y4S0CQ00
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-117-generic 
root=/dev/mapper/vgubuntu-root ro nvidia_drm.modeset=1 quiet splash vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
 linux-restricted-modules-5.15.0-117-generic N/A
 linux-backports-modules-5.15.0-117-generic  N/A
 linux-firmware  20220329.git681281e4-0ubuntu3.31
SourcePackage: linux
UpgradeStatus: Upgraded to jammy on 2022-06-17 (821 days ago)
dmi.bios.date: 07/31/2024
dmi.bios.release: 1.29
dmi.bios.vendor: LENOVO
dmi.bios.version: N40ET47W (1.29 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20Y4S0CQ00
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.18
dmi.modalias: 
dmi:bvnLENOVO:bvrN40ET47W(1.29):bd07/31/2024:br1.29:efr1.18:svnLENOVO:pn20Y4S0CQ00:pvrThinkPadP1Gen4i:rvnLENOVO:rn20Y4S0CQ00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20Y4_BU_Think_FM_ThinkPadP1Gen4i:
dmi.product.family: ThinkPad P1 Gen 4i
dmi.product.name: 20Y4S0CQ00
dmi.product.sku: LENOVO_MT_20Y4_BU_Think_FM_ThinkPad P1 Gen 4i
dmi.product.version: ThinkPad P1 Gen 4i
dmi.sys.vendor: LENOVO

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


** Tags: amd64 apport-bug jammy

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2080866

Title:
  lockd: refusing to freeze on S3 suspend; prevents suspend

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Re: [Bug 1717878] Re: gdm3/gdm-session-worker crashed with SIGTRAP logging "GdmSession: no session desktop files installed, aborting..." from get_fallback_session_name from get_default_session_name fr

[Andrew Diete]

Thank you to everyone that added to the resolution.

On Fri, 13 Sept 2024, 11:45 am Daniel van Vugt, <1717...@bugs.launchpad.net>
wrote:

> A fix is coming via bug 1978310.
>
> ** Also affects: fuse3 (Ubuntu)
>Importance: Undecided
>Status: New
>
> ** Changed in: fuse3 (Ubuntu)
>Status: New => Fix Committed
>
> ** Tags added: udeng-1780
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1717878
>
> Title:
>   gdm3/gdm-session-worker crashed with SIGTRAP logging "GdmSession: no
>   session desktop files installed, aborting..." from
>   get_fallback_session_name from get_default_session_name from
>   get_session_name from get_session_filename from
>   gdm_session_is_wayland_session
>
> Status in fuse package in Ubuntu:
>   Confirmed
> Status in fuse3 package in Ubuntu:
>   Fix Committed
> Status in gdm3 package in Ubuntu:
>   Triaged
> Status in fuse package in Debian:
>   New
>
> Bug description:
>
> https://errors.ubuntu.com/problem/b8e7721d0034b2c4a5ddafcac2e1cc55703f9dbd
>
> https://errors.ubuntu.com/problem/55afdb022e0f09e32692656f5ec80985acf385cc
>
> https://errors.ubuntu.com/problem/f4fce39ac75fb4f87b243f14cb5f8e72f90c2c0f
>
>   ---
>
>   This crash occurs when you uninstall all session files (by accident)
>   from the system. One common way this can happen is by trying to
>   install 'fuse'.
>
>   To fix it just run:
>
> sudo apt install --reinstall ubuntu-session
>
>   or whatever-session for your preferred Ubuntu flavor.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/fuse/+bug/1717878/+subscriptions
>
>

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1717878

Title:
  gdm3/gdm-session-worker crashed with SIGTRAP logging "GdmSession: no
  session desktop files installed, aborting..." from
  get_fallback_session_name from get_default_session_name from
  get_session_name from get_session_filename from
  gdm_session_is_wayland_session

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2077766] Re: [i915] Dell Ultrasharp 4919DW only achieves half of native resolution

[Steven Andrew Lawrence]

Hi Daniel, I have ordered the Apple Thunderbolt 4 Pro :) I should get it by 
Friday. It will be good if that fixes the issue I will let you know thanks
Steve

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2077766

Title:
  [i915] Dell Ultrasharp 4919DW only achieves half of native resolution

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2077766] Re: [i915] Dell Ultrasharp 4919DW only achieves half of native resolution

[Steven Andrew Lawrence]

Hi Daniel, I tested with three different cables same result. however I brought 
home another carbon X1 (Windows and now windows is reporting a faulty usb, it 
wont register the screen is connected-- Its possible / likely that the screen 
is faulty & its just out of warranty..  I am going to bring my X1 to the office 
and test it on the work Dell 4919 screen. Can I do that then if it is the 
screen I will update you tomorrow? 
Thanks

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2077766

Title:
  [i915] Dell Ultrasharp 4919DW only achieves half of native resolution

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2029480] Re: SyntaxWarnings with Python3.12

[Andrew Ziem]

BleachBit 4.6.1 beta has fixed for the syntax warning

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2029480

Title:
  SyntaxWarnings with Python3.12

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2077766] Re: [i915] Dell Ultrasharp 4919DW only achieves half of native resolution

[Steven Andrew Lawrence]

okay I updated the file with the info below. - I changed the screen mode back 
to 5k as when its in the tk mode it will only have a max output of 2k.
In 5k mode im unable to get the resolution to exceed 1024*768 - Should I try 
adjust the file with the resolution for the screen ?5120 x 1440 (32:9)


  

  0
  0
  1
  yes
  

  DP-1
  unknown
  unknown
  unknown


  1024
  768
  60.004
  
  8
  

  

~

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2077766

Title:
  [i915] Dell Ultrasharp 4919DW only achieves half of native resolution

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2077766] Re: [i915] Dell Ultrasharp 4919DW only achieves half of native resolution

[Steven Andrew Lawrence]

the above is the vim command - vim ~/.config/monitors.xml

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2077766

Title:
  [i915] Dell Ultrasharp 4919DW only achieves half of native resolution

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2077766] Re: [i915] Dell Ultrasharp 4919DW only achieves half of native resolution

[Steven Andrew Lawrence]

sorry I opened this file and its diffrent now - 
monitors version="2">
  

  0
  0
  1
  yes
  

  DP-1
  unknown
  unknown
  unknown


  1024
  768
  60.004

8
  

  
  

  0
  0
  1.4953271150588989
  


-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2077766

Title:
  [i915] Dell Ultrasharp 4919DW only achieves half of native resolution

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2077766] Re: [i915] Dell Ultrasharp 4919DW only achieves half of native resolution

[Steven Andrew Lawrence]

the below is the output in 5k mode -


ode: /dev/dri/card1
├───Driver: i915 (Intel Graphics) version 1.6.0 (20230929)
│   ├───DRM_CLIENT_CAP_STEREO_3D supported
│   ├───DRM_CLIENT_CAP_UNIVERSAL_PLANES supported
│   ├───DRM_CLIENT_CAP_ATOMIC supported
│   ├───DRM_CLIENT_CAP_ASPECT_RATIO supported
│   ├───DRM_CLIENT_CAP_WRITEBACK_CONNECTORS supported
│   ├───DRM_CAP_DUMB_BUFFER = 1
│   ├───DRM_CAP_VBLANK_HIGH_CRTC = 1
│   ├───DRM_CAP_DUMB_PREFERRED_DEPTH = 24
│   ├───DRM_CAP_DUMB_PREFER_SHADOW = 1
│   ├───DRM_CAP_PRIME = 3
│   ├───DRM_CAP_TIMESTAMP_MONOTONIC = 1
│   ├───DRM_CAP_ASYNC_PAGE_FLIP = 1
│   ├───DRM_CAP_CURSOR_WIDTH = 256
│   ├───DRM_CAP_CURSOR_HEIGHT = 256
│   ├───DRM_CAP_ADDFB2_MODIFIERS = 1
│   ├───DRM_CAP_PAGE_FLIP_TARGET = 0
│   ├───DRM_CAP_CRTC_IN_VBLANK_EVENT = 1
│   ├───DRM_CAP_SYNCOBJ = 1
│   └───DRM_CAP_SYNCOBJ_TIMELINE = 1
├───Device: PCI 8086:3ea0 Intel Corporation WhiskeyLake-U GT2 [UHD Graphics 620]
│   └───Available nodes: primary, render
├───Framebuffer size
│   ├───Width: [0, 16384]
│   └───Height: [0, 16384]
├───Connectors
│   ├───Connector 0
│   │   ├───Object ID: 95
│   │   ├───Type: eDP
│   │   ├───Status: connected
│   │   ├───Physical size: 310x170 mm
│   │   ├───Subpixel: unknown
│   │   ├───Encoders: {0}
│   │   ├───Modes
│   │   │   └───2560x1440@60.00 preferred driver phsync nvsync 
│   │   └───Properties
│   │   ├───"EDID" (immutable): blob = 125
│   │   ├───"DPMS": enum {On, Standby, Suspend, Off} = On
│   │   ├───"link-status": enum {Good, Bad} = Good
│   │   ├───"non-desktop" (immutable): range [0, 1] = 0
│   │   ├───"TILE" (immutable): blob = 0
│   │   ├───"CRTC_ID" (atomic): object CRTC = 51
│   │   ├───"scaling mode": enum {Full, Center, Full aspect} = Full aspect
│   │   ├───"panel orientation" (immutable): enum {Normal, Upside Down, 
Left Side Up, Right Side Up} = Normal
│   │   ├───"Broadcast RGB": enum {Automatic, Full, Limited 16:235} = 
Automatic
│   │   ├───"max bpc": range [6, 12] = 12
│   │   └───"Colorspace": enum {Default, BT709_YCC, XVYCC_601, XVYCC_709, 
SYCC_601, opYCC_601, opRGB, BT2020_CYCC, BT2020_RGB, BT2020_YCC, 
DCI-P3_RGB_D65, RGB_WIDE_FIXED, RGB_WIDE_FLOAT, BT601_YCC} = Default
│   ├───Connector 1
│   │   ├───Object ID: 103
│   │   ├───Type: DisplayPort
│   │   ├───Status: connected
│   │   ├───Physical size: 0x0 mm
│   │   ├───Subpixel: unknown
│   │   ├───Encoders: {1}
│   │   ├───Modes
│   │   │   ├───640x480@59.94 preferred driver nhsync nvsync 
│   │   │   ├───1024x768@60.00 driver nhsync nvsync 
│   │   │   ├───800x600@60.32 driver phsync pvsync 
│   │   │   ├───800x600@56.25 driver phsync pvsync 
│   │   │   └───848x480@60.00 driver phsync pvsync 
│   │   └───Properties
│   │   ├───"EDID" (immutable): blob = 0
│   │   ├───"DPMS": enum {On, Standby, Suspend, Off} = On
│   │   ├───"link-status": enum {Good, Bad} = Good
│   │   ├───"non-desktop" (immutable): range [0, 1] = 0
│   │   ├───"TILE" (immutable): blob = 0
│   │   ├───"CRTC_ID" (atomic): object CRTC = 72
│   │   ├───"subconnector" (immutable): enum {Unknown, VGA, DVI-D, HDMI, 
DP, Wireless, Native} = Native
│   │   ├───"audio": enum {force-dvi, off, auto, on} = auto
│   │   ├───"Broadcast RGB": enum {Automatic, Full, Limited 16:235} = 
Automatic
│   │   ├───"max bpc": range [6, 12] = 12
│   │   ├───"Colorspace": enum {Default, BT709_YCC, XVYCC_601, XVYCC_709, 
SYCC_601, opYCC_601, opRGB, BT2020_CYCC, BT2020_RGB, BT2020_YCC, 
DCI-P3_RGB_D65, RGB_WIDE_FIXED, RGB_WIDE_FLOAT, BT601_YCC} = Default
│   │   ├───"HDR_OUTPUT_METADATA": blob = 0
│   │   ├───"Content Protection": enum {Undesired, Desired, Enabled} = 
Undesired
│   │   └───"HDCP Content Type": enum {HDCP Type0, HDCP Type1} = HDCP Type0
│   ├───Connector 2
│   │   ├───Object ID: 113
│   │   ├───Type: HDMI-A
│   │   ├───Status: disconnected
│   │   ├───Encoders: {1}
│   │   └───Properties
│   │   ├───"EDID" (immutable): blob = 0
│   │   ├───"DPMS": enum {On, Standby, Suspend, Off} = Off
│   │   ├───"link-status": enum {Good, Bad} = Good
│   │   ├───"non-desktop" (immutable): range [0, 1] = 0
│   │   ├───"TILE" (immutable): blob = 0
│   │   ├───"CRTC_ID" (atomic): object CRTC = 0
│   │   ├───"audio": enum {force-dvi, off, auto, on} = auto
│   │   ├───"Broadcast RGB": enum {Automatic, Full, Limited 16:235} = 
Automatic
│   │   ├───"aspect ratio": enum {Automatic, 4:3, 16:9} = Automatic
│   │   ├───"Colorspace": enum {Default, SMPTE_170M_YCC, BT709_YCC, 
XVYCC_601, XVYCC_709, SYCC_601, opYCC_601, opRGB, BT2020_CYCC, BT2020_RGB, 
BT2020_YCC, DCI-P3_RGB_D65, DCI-P3_RGB_Theater} = Default
│   │   ├───"content type": enum {No Data, Graphics, Photo, Cinema, Game} = 
No Data
│   │   ├───"max bpc": range [8, 12] = 12
│   │   ├───"Content Protection": enum {Undesired, Desired, Enabled} = 
Undesired
│   │   └───"HDCP Content Type": enum {HDCP Type0, HDCP Type1} = HDCP Type0
│   └───Conn

[Bug 2077766] Re: [i915] Dell Ultrasharp 4919DW only achieves half of native resolution

[Steven Andrew Lawrence]

Im sorry I thought I sent this off just before I left for JHB :(

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2077766

Title:
  [i915] Dell Ultrasharp 4919DW only achieves half of native resolution

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2077766] Re: [i915] Dell Ultrasharp 4919DW only achieves half of native resolution

[Steven Andrew Lawrence]

sudo drm_info
Node: /dev/dri/card1
├───Driver: i915 (Intel Graphics) version 1.6.0 (20230929)
│   ├───DRM_CLIENT_CAP_STEREO_3D supported
│   ├───DRM_CLIENT_CAP_UNIVERSAL_PLANES supported
│   ├───DRM_CLIENT_CAP_ATOMIC supported
│   ├───DRM_CLIENT_CAP_ASPECT_RATIO supported
│   ├───DRM_CLIENT_CAP_WRITEBACK_CONNECTORS supported
│   ├───DRM_CAP_DUMB_BUFFER = 1
│   ├───DRM_CAP_VBLANK_HIGH_CRTC = 1
│   ├───DRM_CAP_DUMB_PREFERRED_DEPTH = 24
│   ├───DRM_CAP_DUMB_PREFER_SHADOW = 1
│   ├───DRM_CAP_PRIME = 3
│   ├───DRM_CAP_TIMESTAMP_MONOTONIC = 1
│   ├───DRM_CAP_ASYNC_PAGE_FLIP = 1
│   ├───DRM_CAP_CURSOR_WIDTH = 256
│   ├───DRM_CAP_CURSOR_HEIGHT = 256
│   ├───DRM_CAP_ADDFB2_MODIFIERS = 1
│   ├───DRM_CAP_PAGE_FLIP_TARGET = 0
│   ├───DRM_CAP_CRTC_IN_VBLANK_EVENT = 1
│   ├───DRM_CAP_SYNCOBJ = 1
│   └───DRM_CAP_SYNCOBJ_TIMELINE = 1
├───Device: PCI 8086:3ea0 Intel Corporation WhiskeyLake-U GT2 [UHD Graphics 620]
│   └───Available nodes: primary, render
├───Framebuffer size
│   ├───Width: [0, 16384]
│   └───Height: [0, 16384]
├───Connectors
│   ├───Connector 0
│   │   ├───Object ID: 95
│   │   ├───Type: eDP
│   │   ├───Status: connected
│   │   ├───Physical size: 310x170 mm
│   │   ├───Subpixel: unknown
│   │   ├───Encoders: {0}
│   │   ├───Modes
│   │   │   └───2560x1440@60.00 preferred driver phsync nvsync 
│   │   └───Properties
│   │   ├───"EDID" (immutable): blob = 128
│   │   ├───"DPMS": enum {On, Standby, Suspend, Off} = Off
│   │   ├───"link-status": enum {Good, Bad} = Good
│   │   ├───"non-desktop" (immutable): range [0, 1] = 0
│   │   ├───"TILE" (immutable): blob = 0
│   │   ├───"CRTC_ID" (atomic): object CRTC = 0
│   │   ├───"scaling mode": enum {Full, Center, Full aspect} = Full aspect
│   │   ├───"panel orientation" (immutable): enum {Normal, Upside Down, 
Left Side Up, Right Side Up} = Normal
│   │   ├───"Broadcast RGB": enum {Automatic, Full, Limited 16:235} = 
Automatic
│   │   ├───"max bpc": range [6, 12] = 12
│   │   └───"Colorspace": enum {Default, BT709_YCC, XVYCC_601, XVYCC_709, 
SYCC_601, opYCC_601, opRGB, BT2020_CYCC, BT2020_RGB, BT2020_YCC, 
DCI-P3_RGB_D65, RGB_WIDE_FIXED, RGB_WIDE_FLOAT, BT601_YCC} = Default
│   ├───Connector 1
│   │   ├───Object ID: 103
│   │   ├───Type: DisplayPort
│   │   ├───Status: connected
│   │   ├───Physical size: 600x340 mm
│   │   ├───Subpixel: unknown
│   │   ├───Encoders: {1}
│   │   ├───Modes
│   │   │   ├───2560x1440@59.95 preferred driver phsync nvsync 
│   │   │   ├───1920x1080@60.00 driver phsync pvsync 
│   │   │   ├───1920x1080@60.00 driver phsync pvsync 16:9 
│   │   │   ├───1920x1080@59.94 driver phsync pvsync 16:9 
│   │   │   ├───1920x1080@50.00 driver phsync pvsync 16:9 
│   │   │   ├───1600x1200@60.00 driver phsync pvsync 
│   │   │   ├───1280x1024@75.03 driver phsync pvsync 
│   │   │   ├───1280x1024@60.02 driver phsync pvsync 
│   │   │   ├───1280x800@59.81 driver nhsync pvsync 
│   │   │   ├───1152x864@75.00 driver phsync pvsync 
│   │   │   ├───1280x720@60.00 driver phsync pvsync 
│   │   │   ├───1280x720@60.00 driver phsync pvsync 16:9 
│   │   │   ├───1280x720@59.94 driver phsync pvsync 16:9 
│   │   │   ├───1280x720@50.00 driver phsync pvsync 16:9 
│   │   │   ├───1024x768@75.03 driver phsync pvsync 
│   │   │   ├───1024x768@60.00 driver nhsync nvsync 
│   │   │   ├───800x600@75.00 driver phsync pvsync 
│   │   │   ├───800x600@60.32 driver phsync pvsync 
│   │   │   ├───720x576@50.00 driver nhsync nvsync 16:9 
│   │   │   ├───720x480@60.00 driver nhsync nvsync 16:9 
│   │   │   ├───720x480@60.00 driver nhsync nvsync 4:3 
│   │   │   ├───720x480@59.94 driver nhsync nvsync 16:9 
│   │   │   ├───720x480@59.94 driver nhsync nvsync 4:3 
│   │   │   ├───640x480@75.00 driver nhsync nvsync 
│   │   │   ├───640x480@60.00 driver nhsync nvsync 4:3 
│   │   │   ├───640x480@59.94 driver nhsync nvsync 
│   │   │   ├───640x480@59.94 driver nhsync nvsync 4:3 
│   │   │   └───720x400@70.08 driver nhsync pvsync 
│   │   └───Properties
│   │   ├───"EDID" (immutable): blob = 129
│   │   ├───"DPMS": enum {On, Standby, Suspend, Off} = On
│   │   ├───"link-status": enum {Good, Bad} = Good
│   │   ├───"non-desktop" (immutable): range [0, 1] = 0
│   │   ├───"TILE" (immutable): blob = 0
│   │   ├───"CRTC_ID" (atomic): object CRTC = 72
│   │   ├───"subconnector" (immutable): enum {Unknown, VGA, DVI-D, HDMI, 
DP, Wireless, Native} = Native
│   │   ├───"audio": enum {force-dvi, off, auto, on} = auto
│   │   ├───"Broadcast RGB": enum {Automatic, Full, Limited 16:235} = 
Automatic
│   │   ├───"max bpc": range [6, 12] = 12
│   │   ├───"Colorspace": enum {Default, BT709_YCC, XVYCC_601, XVYCC_709, 
SYCC_601, opYCC_601, opRGB, BT2020_CYCC, BT2020_RGB, BT2020_YCC, 
DCI-P3_RGB_D65, RGB_WIDE_FIXED, RGB_WIDE_FLOAT, BT601_YCC} = Default
│   │   ├───"HDR_OUTPUT_METADATA": blob = 0
│   │   ├───"Content Protection": enum {Undesired, Desired, Enabled} = 
Undesired
│   │   └───"HDCP Content Typ

[Bug 2009858] Re: User authentication is broken with 2:4.15.13+dfsg-0ubuntu0.20.04.1 package

[Andrew Berry]

> - use mapping (but contents of /etc/samba/username_map unknown)

In my case, it turned out I had the mapping file usernames backwards,
with ` = `. I'm not sure why this ever
worked with older versions, but it did.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2009858

Title:
  User authentication is broken with 2:4.15.13+dfsg-0ubuntu0.20.04.1
  package

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1970108] Re: Impossible to build against OpenVDB v8.1 due to TBB system version

[Andrew Jong]

I believe this issue still persists?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1970108

Title:
  Impossible to build against OpenVDB v8.1 due to TBB system version

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Re: [Bug 2077766] Re: Dell Ultrasharp 4919DW

[Steven Andrew Lawrence]

Thanks, so this is an X1 I have an office full of X1s running on this dell
I am using the Dell usb I have tried with a unetech cable. I will bring the
laptop to the office and try on a different 4919DW. just to add info. As I
said it did work with no hardware changes for about a year then after an
update it stopped working ( It stopped detecting that it was a dell
monitor) and stopped detecting the correct resolution

On Mon, 26 Aug 2024 at 08:30, Daniel van Vugt <2077...@bugs.launchpad.net>
wrote:

> I've noticed through multiple bug reports that recent kernels have
> become pedantic about bandwidth requirements and therefore which
> resolutions they are willing to offer.
>
> Also 5120x1440 at 60Hz is right near the limit of what the i7-8565U can
> do:
>
> https://ark.intel.com/content/www/us/en/ark/products/149091/intel-
> core-i7-8565u-processor-8m-cache-up-to-4-60-ghz.html#tab-blade-1-0-4
> 
>
> Still, if it worked before then you probably just need either:
>
>  * A higher grade USB-C (or better yet Thunderbolt) cable that will work
> on more kernel versions; or
>  * To try various older and newer kernel versions to see which are willing
> to offer the full resolution.
>
>
> ** No longer affects: mutter (Ubuntu)
>
> ** Summary changed:
>
> - Dell Ultrasharp 4919DW
> + [i915] Dell Ultrasharp 4919DW only achieves half of native resolution
>
> ** Tags added: regression-update
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/2077766
>
> Title:
>   [i915] Dell Ultrasharp 4919DW only achieves half of native resolution
>
> Status in linux package in Ubuntu:
>   New
>
> Bug description:
>   Hi :) hope all is well
>
>   The Dell Ultrasharp 4919DW monitor is no longer detected correctly in
>   Ubuntu after a recent update, causing it to only display a resolution
>   of 1024x768 instead of its native 5120x1440 (32:9) resolution over
>   USB-C.
>
>   Steps to Reproduce:
>
>   Connect the Dell Ultrasharp 4919DW monitor to a laptop running Ubuntu
> via USB-C.
>   Observe that the monitor is detected as a "PNP screen" instead of "Dell"
> and defaults to a resolution of 1024x768.
>   Attempt to change the screen mode to achieve higher resolution. The
> maximum available resolution is 2560x1440 (2K), but it only uses half of
> the screen. PBP mode on the screen
>   Reload the system with the latest Ubuntu LTS version.
>   Repeat the steps on another laptop using Linux Mint.
>   Expected Result:
>   The monitor should be detected as a Dell Ultrasharp 4919DW and should
> display at its full native resolution of 5120x1440.
>
>   Actual Result:
>   The monitor is detected as a generic "PNP screen" with a default
> resolution of 1024x768. Changing the screen mode to pbp only achieves
> 2560x1440, which utilizes only half of the screen.
>
>   Additional Information:
>
>   The issue persists after reloading the system with the latest Ubuntu LTS
> version.
>   The issue also occurs on another laptop running Linux Mint.
>   The monitor works correctly on a Windows system, displaying at its full
> 5120x1440 resolution.
>   thanks
>   Steve
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 24.04
>   Package: xorg 1:7.7+23ubuntu3
>   ProcVersionSignature: Ubuntu 6.8.0-38.38-generic 6.8.8
>   Uname: Linux 6.8.0-38-generic x86_64
>   NonfreeKernelModules: zfs
>   ApportVersion: 2.28.1-0ubuntu3
>   Architecture: amd64
>   BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
>   CasperMD5CheckResult: pass
>   CompositorRunning: None
>   CurrentDesktop: ubuntu:GNOME
>   Date: Fri Aug 23 21:40:31 2024
>   DistUpgraded: Fresh install
>   DistroCodename: noble
>   DistroVariant: ubuntu
>   ExtraDebuggingInterest: Yes, if not too technical
>   GraphicsCard:
>Intel Corporation WhiskeyLake-U GT2 [UHD Graphics 620] [8086:3ea0] (rev
> 02) (prog-if 00 [VGA controller])
>  Subsystem: Lenovo WhiskeyLake-U GT2 [UHD Graphics 620] [17aa:2292]
>   InstallationDate: Installed on 2024-05-21 (95 days ago)
>   InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64
> (20240424)
>   MachineType: LENOVO 20QD001NZA
>   ProcEnviron:
>LANG=en_US.UTF-8
>PATH=(custom, no user)
>SHELL=/bin/bash
>TERM=xterm-256color
>XDG_RUNTIME_DIR=
>   ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_yno3im@/vmlinuz-6.8.0-38-generic
> root=ZFS=rpool/ROOT/ubuntu_yno3im ro quiet splash vt.handoff=1
>   SourcePackage: xorg
>   Symptom: display
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   dmi.bios.date: 12/06/2022
>   dmi.bios.release: 1.56
>   dmi.bios.vendor: LENOVO
>   dmi.bios.version: N2HET73W (1.56 )
>   dmi.board.asset.tag: Not Available
>   dmi.board.name: 20QD001NZA
>   dmi.board.vendor: LENOVO
>   dmi.board.version: SDK0K17763 WIN
>   dmi.chassis.asset.tag: No Asset Information
>   dmi.chassis

[Bug 2077766] [NEW] Dell Ultrasharp 4919DW

[Steven Andrew Lawrence]

Public bug reported:

Hi :) hope all is well

The Dell Ultrasharp 4919DW monitor is no longer detected correctly in
Ubuntu after a recent update, causing it to only display a resolution of
1024x768 instead of its native 5120x1440 (32:9) resolution over USB-C.

Steps to Reproduce:

Connect the Dell Ultrasharp 4919DW monitor to a laptop running Ubuntu via USB-C.
Observe that the monitor is detected as a "PNP screen" instead of "Dell" and 
defaults to a resolution of 1024x768.
Attempt to change the screen mode to achieve higher resolution. The maximum 
available resolution is 2560x1440 (2K), but it only uses half of the screen. 
PBP mode on the screen
Reload the system with the latest Ubuntu LTS version.
Repeat the steps on another laptop using Linux Mint.
Expected Result:
The monitor should be detected as a Dell Ultrasharp 4919DW and should display 
at its full native resolution of 5120x1440.

Actual Result:
The monitor is detected as a generic "PNP screen" with a default resolution of 
1024x768. Changing the screen mode to pbp only achieves 2560x1440, which 
utilizes only half of the screen.

Additional Information:

The issue persists after reloading the system with the latest Ubuntu LTS 
version.
The issue also occurs on another laptop running Linux Mint.
The monitor works correctly on a Windows system, displaying at its full 
5120x1440 resolution.
thanks 
Steve

ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: xorg 1:7.7+23ubuntu3
ProcVersionSignature: Ubuntu 6.8.0-38.38-generic 6.8.8
Uname: Linux 6.8.0-38-generic x86_64
NonfreeKernelModules: zfs
ApportVersion: 2.28.1-0ubuntu3
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Fri Aug 23 21:40:31 2024
DistUpgraded: Fresh install
DistroCodename: noble
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation WhiskeyLake-U GT2 [UHD Graphics 620] [8086:3ea0] (rev 02) 
(prog-if 00 [VGA controller])
   Subsystem: Lenovo WhiskeyLake-U GT2 [UHD Graphics 620] [17aa:2292]
InstallationDate: Installed on 2024-05-21 (95 days ago)
InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424)
MachineType: LENOVO 20QD001NZA
ProcEnviron:
 LANG=en_US.UTF-8
 PATH=(custom, no user)
 SHELL=/bin/bash
 TERM=xterm-256color
 XDG_RUNTIME_DIR=
ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_yno3im@/vmlinuz-6.8.0-38-generic 
root=ZFS=rpool/ROOT/ubuntu_yno3im ro quiet splash vt.handoff=1
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/06/2022
dmi.bios.release: 1.56
dmi.bios.vendor: LENOVO
dmi.bios.version: N2HET73W (1.56 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20QD001NZA
dmi.board.vendor: LENOVO
dmi.board.version: SDK0K17763 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.25
dmi.modalias: 
dmi:bvnLENOVO:bvrN2HET73W(1.56):bd12/06/2022:br1.56:efr1.25:svnLENOVO:pn20QD001NZA:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20QD001NZA:rvrSDK0K17763WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20QD_BU_Think_FM_ThinkPadX1Carbon7th:
dmi.product.family: ThinkPad X1 Carbon 7th
dmi.product.name: 20QD001NZA
dmi.product.sku: LENOVO_MT_20QD_BU_Think_FM_ThinkPad X1 Carbon 7th
dmi.product.version: ThinkPad X1 Carbon 7th
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.120-2build1
version.libgl1-mesa-dri: libgl1-mesa-dri 24.0.9-0ubuntu0.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.12-1ubuntu1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:22.0.0-1build1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1build1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1

** Affects: ubuntu
 Importance: Undecided
 Status: New


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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2077766

Title:
  Dell Ultrasharp 4919DW

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2064647] Re: Documentation for how to enable gnome-remote-desktop on a completly headless system

[Andrew Weaver]

Hello, 
I'm attempting to automate the process to build images for use on other 
machines.

first enable gsettings
gsettings set org.gnome.desktop.remote-desktop.rdp enable true
gsettings set org.gnome.desktop.remote-desktop.rdp screen-share-mode 
mirror-primary
gsettings set org.gnome.desktop.remote-desktop.rdp view-only false

then create a Default_keyring.keyring
create_default_keyring() {
# Define the path for the keyring
local keyring_path="$HOME/.local/share/keyrings/Default_keyring.keyring"

# Create the directory if it doesn't exist
mkdir -p "$HOME/.local/share/keyrings/"

# Write the content to the keyring file
cat < "$keyring_path"
[keyring]
display-name=Default keyring
ctime=1723570530
mtime=0
lock-on-idle=false
lock-after=false

[1]
item-type=0
display-name=GNOME Remote Desktop RDP credentials
secret={'username': <''>, 'password': <''>}
mtime=1723570630
ctime=1723570530

[1:attribute0]
name=xdg:schema
type=string
value=org.gnome.RemoteDesktop.RdpCredentials
EOL

# Set the permissions to rw--- (600)
chmod 600 "$keyring_path"

echo "Default_keyring.keyring has been created at $keyring_path with 
permissions 600"
}

then create the other default file

create_default_link() {
# Define the path for the default file
local default_path="$HOME/.local/share/keyrings/default"

# Create the directory if it doesn't exist
mkdir -p "$HOME/.local/share/keyrings/"

# Write the content to the default file
echo "Default_keyring" > "$default_path"

# Set the permissions to rw-rw-r-- (664)
chmod 664 "$default_path"

echo "Default file has been created at $default_path with permissions 664"
}


But I still must open the GUI > settings > system > remote desktop, do nothing, 
and close it. Then the machine will accept RDP with the username password set 
above.


I can also use grdctl and toggle the password, but still must open the
GUI menu once.

# Function to clear and set RDP credentials
set_rdp_credentials() {
local username="$1"
local password="$2"

# Logging utility
log() {
echo "$1"
}

# Clear existing RDP credentials
log "Clearing existing RDP credentials..."
grdctl rdp clear-credentials
log "RDP credentials cleared."

# Set new RDP credentials
log "Setting new RDP credentials for user '$username'..."
grdctl rdp set-credentials "$username" "$password"
log "RDP credentials set for user '$username'."
}

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2064647

Title:
  Documentation for how to enable gnome-remote-desktop on a completly
  headless system

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2073776] Re: nsswitch.conf "passwd" entry misses "systemd", breaking DynamicUser=yes systemd units

[Andrew Martin]

Yes, I had changed it with ansible

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2073776

Title:
  nsswitch.conf "passwd" entry misses "systemd", breaking
  DynamicUser=yes systemd units

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2066314] Re: Please update the agent to upstream tag 20240307.00

[Andrew Cloke]

Following the "Test Case" in the description, for each of the Focal,
Jammy, Mantic and Noble releases we have now:

 * published an image based on the -proposed packages to the 
ubuntu-os-cloud-devel project
 * had confirmation from the GCE team that they have successfully validated 
that new image; they have confirmed that the new package addresses the issues 
it is expected to address, and that the image passes their internal image 
validation.

Updated verification tags accordingly.


** Tags removed: verification-needed verification-needed-focal 
verification-needed-jammy verification-needed-mantic verification-needed-noble
** Tags added: verification-done verification-done-focal 
verification-done-jammy verification-done-mantic verification-done-noble

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2066314

Title:
  Please update the agent to upstream tag 20240307.00

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gce-compute-image-packages/+bug/2066314/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2073776] Re: cockpit-ws 321-1~bpo22.04.1 changes user to cockpit-wsinstance but systemd units still use cockpit-ws as the username

[Andrew Martin]

I checked and `libnss-systemd` was installed, however the "passwd" line
in /etc/nsswitch.conf was missing the "systemd" part; once I added it, I
was able to successfully start cockpit. Thank you for the help
troubleshooting this issue; this bug report can be closed!

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2073776

Title:
  cockpit-ws 321-1~bpo22.04.1 changes user to cockpit-wsinstance but
  systemd units still use cockpit-ws as the username

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2073776] Re: cockpit-ws 321-1~bpo22.04.1 changes user to cockpit-wsinstance but systemd units still use cockpit-ws as the username

[Andrew Martin]

Yes, cockpit fails to start:
cockpit-wsinstance-https-factory.socket: Job 
cockpit-wsinstance-https-factory.socket/start failed with result 'dependency'.
cockpit.service: Job cockpit.service/start failed with result 'dependency'.
cockpit-wsinstance-https-factory.socket: Control process exited, code=exited, 
status=217/USER
cockpit-wsinstance-https-factory.socket: Failed to resolve user cockpit-ws: No 
such process
cockpit-wsinstance-http.socket: Failed with result 'exit-code'.
Failed to listen on Socket for Cockpit Web Service http instance.
Dependency failed for Cockpit Web Service.
Dependency failed for Socket for Cockpit Web Service https instance factory.

This is on Ubuntu 22.04.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2073776

Title:
  cockpit-ws 321-1~bpo22.04.1 changes user to cockpit-wsinstance but
  systemd units still use cockpit-ws as the username

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2073776] [NEW] cockpit-ws 321-1~bpo22.04.1 changes user to cockpit-wsinstance but systemd units still use cockpit-ws as the username

[Andrew Martin]

Public bug reported:

The 321-1~bpo22.04.1 version of cockpit-ws calls the cockpit user 
"cockpit-wsinstance":
$ cat usr/lib/sysusers.d/cockpit-wsinstance.conf
u cockpit-wsinstance - "User for cockpit-ws instances" -

However the following systemd files still reference the old "cockpit-ws" 
username, so the service fails to start:
$ grep -r cockpit-ws$ lib/systemd/system
lib/systemd/system/cockpit-ws-user.service:Description=Dynamic user for 
cockpit-ws
lib/systemd/system/cockpit-ws-user.service:User=cockpit-ws
lib/systemd/system/cockpit-ws-user.service:Group=cockpit-ws
lib/systemd/system/cockpit-wsinstance-https@.socket:SocketUser=cockpit-ws
lib/systemd/system/cockpit-wsinstance-https-factory.socket:SocketUser=cockpit-ws
lib/systemd/system/cockpit.service:User=cockpit-ws
lib/systemd/system/cockpit.service:Group=cockpit-ws
lib/systemd/system/cockpit-wsinstance-http.socket:SocketUser=cockpit-ws

Can these systemd files be updated to use the new username? Thanks!

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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2073776

Title:
  cockpit-ws 321-1~bpo22.04.1 changes user to cockpit-wsinstance but
  systemd units still use cockpit-ws as the username

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2073163] Re: Please update to 20240716.00

[Andrew Cloke]

The Google team have highlighted an issue with the 20240701.00 tag, and
have requested that we instead bump to the 20240716.00 tag. Updated
title accordingly.

** Summary changed:

- Please update to 20240701.00
+ Please update to 20240716.00

** Description changed:

  Following on from previous similar package update requests @ LP:
  #2040945, LP: #2018272 and LP: #1959392, this bug is a request to update
- the google-guest-agent package to the upstream version `20240701.00` @
+ the google-guest-agent package to the upstream version `20240716.00` @
  https://github.com/GoogleCloudPlatform/guest-
- agent/releases/tag/20240701.00
+ agent/releases/tag/20240716.00
  
  This package has an SRU exception @
  https://wiki.ubuntu.com/StableReleaseUpdates#google-guest-agent
  including an ageing exception detailed @ https://wiki.ubuntu.com/google-
  guest-agent-Updates
  
  [Impact]
  
  This package is provided by Google for installation within guests that
  run on Google Compute Engine. It is part of a collection of tools and
  daemons, that ensure that the Ubuntu images published to GCE run
  properly on their platform.
  
  Cloud platforms evolve at a rate that can't be handled in six-month
  increments, and they will often develop features that they would like to
  be available to customers who don't want to upgrade from earlier Ubuntu
  releases. As such, updating this package to more recent upstream
  releases is required within all Ubuntu releases, so they continue to
  function properly in their environment.
  
  [Test Case]
  
  When a new version of this package is uploaded to -proposed, the
  following will happen:
  
-  * an image based on -proposed will be built for GCE and published to the 
ubuntu-os-cloud-devel project
-  * the GCE team will be asked to validate that the new package addresses the 
issues it is expected to address, and that the image passes their internal 
image validation.
+  * an image based on -proposed will be built for GCE and published to the 
ubuntu-os-cloud-devel project
+  * the GCE team will be asked to validate that the new package addresses the 
issues it is expected to address, and that the image passes their internal 
image validation.
  
  If all the testing indicates that the image containing the new package
  is acceptable, verification will be considered to be done.
  
  [Vendored Dependency]
  
  ## Add notes here Chlo ##
  
  [Where Problems Could Occur]
  
- There are many upstream changes in `20240701.00-0ubuntu1` vs.
+ There are many upstream changes in `20240716.00-0ubuntu1` vs.
  `20240213.00-0ubuntu4`; however between the guest-test-infra suite [0]
  (which is run for validation by CPC _and_ Google) and CPC's own internal
  test harness (CTF), there is confidence that most if not all "edge
  cases" and/or obvious regressions concerns can be dismissed before the
  new version lands in `-updates`
  
  [Other Information]
  
  This bug is used for tracking of releasing the new upstream version for
  all supported series, as per the approved policy mentioned in the
  following MRE:
  
  https://wiki.ubuntu.com/google-guest-agent-Updates
  
  The updated package is not built for armhf and riscv64 due to upstream
  regressions but the package is not used on those architectures thus
  please release the SRU without the armhf and risc64 binaries.
  
  The package does not build for powerpc on Xenial, but this is OK since
  it is not used on powerpc either.
  
  [0]: https://github.com/GoogleCloudPlatform/guest-test-infra

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2073163

Title:
  Please update to 20240716.00

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/google-guest-agent/+bug/2073163/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2065914] Re: rspamd webgui navigation not working ( ubuntu 24.04)

[Andrew Keynes]

Note that as earlier this week, they are now building packages for 24.04
(See https://github.com/rspamd/rspamd/issues/5040).

Following the instructions on their site
(https://rspamd.com/downloads.html) to add their repository and it
installs successfully and fixes the issue reported here.

Another fairly useful bugfix in v3.9.0 is the one for the bayes learning
issue (https://github.com/rspamd/rspamd/pull/4930).

** Bug watch added: github.com/rspamd/rspamd/issues #5040
   https://github.com/rspamd/rspamd/issues/5040

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2065914

Title:
  rspamd webgui navigation not working ( ubuntu 24.04)

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2072681] [NEW] The monit daemon fails when attempting to start under systemd

[Andrew Torry]

Public bug reported:

After upgrading from 22.04 LTS to 24.04 LTS, we noticed that our monit service 
failed to start.
We expected "sudo systemctl status monit" to show that the daemon is running, 
but instead we got:-

Started monit.service - Pro-active monitoring utility for unix systems.
monit.service: Main process exited, code=exited, status=1/FAILURE
monit.service: Failed with result 'exit-code'.

Our machine has monit version 1:5.33.0-2build2

We figured out a workaround by altering this line in the
"/usr/lib/systemd/system/monit.service" file:-

ProtectHome=yes

When we changed this to "ProtectHome=read-only", monit then started as
expected under systemd.

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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2072681

Title:
  The monit daemon fails when attempting to start under systemd

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2066118] Re: 24.04 Subiquity Cannot Read Auto-install Cloud-init Files

[Andrew Meyer]

I cannot PXE boot Ubuntu from cobbler because of this.  I ahve tried
this on 22.04.4, 23.04, 23.10 as well.  All the same issue!

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2066118

Title:
  24.04 Subiquity Cannot Read Auto-install Cloud-init Files

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2043820] Re: Unable to contact snap store on Xubuntu from Jammy to Noble

[Andrew Phelps]

Hello, I was able to reproduce this issue when upgrading MATE from Jammy
to Noble.

By manually running "snap info firefox" during the upgrade process, I
could see it failing:

$ snap info firefox
error: no snap found for "firefox"

This error message isn't great, but it is what we report right now from
"snap info" when we're unable to reach the store.

This issue wasn't unique to snapd though, I wasn't able to resolve any
DNS queries at all.

$ nslookup snapcraft.io
communications error to 127.0.0.53#53: connection refused
communications error to 127.0.0.53#53: connection refused
communications error to 127.0.0.53#53: connection refused
no servers could be reached

It looks like systemd-resolved was in some sort of broken state, here
are its logs:

systemd-resolved.service: Current command vanished from the unit file, 
execution of the command list won't be resumed.
systemd-resolved.service: Got notification message from PID 344, but reception 
is disabled.
systemd-resolved.service: Got notification message from PID 344, but reception 
is disabled.
systemd-resolved.service: Got notification message from PID 344, but reception 
is disabled.
systemd-resolved.service: Watchdog timeout (limit 3min)!
systemd-resolved.service: Killing process 344 (systemd-resolve) with signal 
SIGABRT.
systemd-resolved.service: Main process exited, code=dumped, status=6/ABRT
systemd-resolved.service: Failed with result 'watchdog'.

/etc/resolv.conf was still the systemd-resolved generated one. When I
replaced it with "nameserver 8.8.8.8", then "snap info firefox"
succeeded and I was able to continue with the release upgrade.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2043820

Title:
  Unable to contact snap store on Xubuntu from Jammy to Noble

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2069400] Re: Some DUTs can't boot up after installing the hwe kernel in the proposed on Focal

[Andrew Bonkowski]

I had this issue just now as well. I rolled back to the previous kernel
and it works. I am new to Linux, so I know zero about how to capture
errors and all that, but  I'm running an Asus laptop and haven't even
figured out how to list my hardware using Mint yet. I have a long way to
go before I can replace windows with THIS, especially if it's prone to
bugging out where I can't boot.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2069400

Title:
  Some DUTs can't boot up after installing the hwe kernel in the
  proposed on Focal

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2059847] Re: Input lag or freezes on Nvidia desktops with X11 after logging "MetaSyncRing: Sync object is not ready -- were events handled properly?"

[Andrew Moffat]

Ok, it sounds like it was some atypical conditions that caused the
undesired outcome. Thanks for explaining it and for your hard work on
this issue, Daniel.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2059847

Title:
  Input lag or freezes on Nvidia desktops with X11 after logging
  "MetaSyncRing: Sync object is not ready -- were events handled
  properly?"

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2059847] Re: Input lag or freezes on Nvidia desktops with X11 after logging "MetaSyncRing: Sync object is not ready -- were events handled properly?"

[Andrew Moffat]

Thank you for fixing the bug.

How can this be avoided for the future? I know this is free software,
and so we the users have limited entitlement to expectations of the
software, but a large number of people having a degraded system for over
2 months is not really acceptable. Why could the regression not be
rolled back? Why did we need to sit in a broken state for so long? I
understand if people are busy and can't fix the issue in a timely
manner. But if they are too busy to fast-track a fix, can the breaking
change please be rolled back? Was there something preventing this?

I'm not trying to point fingers or lay blame. I am sincerely curious
about what new procedures will be adopted to prevent a repeat of a High
Importance issue sitting broken for so long.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2059847

Title:
  Input lag or freezes on Nvidia desktops with X11 after logging
  "MetaSyncRing: Sync object is not ready -- were events handled
  properly?"

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1947364] Re: mt76 module disagrees on a lot

[Andrew Dabrowski]

I'm running into this also, on 24.04.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1947364

Title:
  mt76 module disagrees on a lot

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1999308] Re: Snap keeps uninstalling apt Firefox, and reinstalling snap Firefox

[Andrew Conway]

The same problem occurs on 24.04, but the workaround of setting the
ubuntu priority to a negative number seems to be working.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1999308

Title:
  Snap keeps uninstalling apt Firefox, and reinstalling snap Firefox

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2063456] Re: package cephadm: dependency "cephadmlib" missing

[Andrew Beeman]

I can confirm this is still an issue.

I could not get #4 to work; there were dependency errors on some of the
commands.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2063456

Title:
  package cephadm: dependency "cephadmlib" missing

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Re: [Bug 2048945] Re: scsi_eh_* process using idle CPU after upgrade to kernel 6.5

[Andrew Reis]

Confirmed. And it also looks like the fix made it into the 6.8 kernel
for noble.


From: nore...@launchpad.net  on behalf of ku4eto 
<2048...@bugs.launchpad.net>
Date: Friday, May 3, 2024 at 15:20
To: Drew Reis 
Subject: [Bug 2048945] Re: scsi_eh_* process using idle CPU after upgrade to 
kernel 6.5
Issue seems to have been fixed, with the bug report not being mentioned in the 
changelog.
Tested on Ubuntu 22.04, with 6.5.0-28-generic, vSphere 6.5, ESXi 6.5, IDE 
CD/DVD as Client Device.
I guess this can be closed.

@areis422 Can you test and confirm on your side as well?

--
You received this bug notification because you are subscribed to the bug
report.
https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbugs.launchpad.net%2Fbugs%2F2048945&data=05%7C02%7Cdrew_reis%40gensler.com%7Caa2ee77f19b24bd7689908dc6bae78e8%7C94a74758f2ff413c9f705725701b8d02%7C0%7C0%7C638503644324869373%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C&sdata=5SEDThTBhEDUa%2BPxcBjVPk9Y0Oh9x6R49qET%2FIqA%2BxA%3D&reserved=0

Title:
  scsi_eh_* process using idle CPU after upgrade to kernel 6.5

Status in linux:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in linux-aws-6.5 package in Ubuntu:
  Confirmed
Status in linux-hwe-6.5 package in Ubuntu:
  Confirmed
Status in linux-meta-hwe-6.5 package in Ubuntu:
  Confirmed
Status in linux-signed-hwe-6.5 package in Ubuntu:
  Confirmed

Bug description:
  Possibly related to 
https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Flkml.kernel.org%2Flinux-&data=05%7C02%7Cdrew_reis%40gensler.com%7Caa2ee77f19b24bd7689908dc6bae78e8%7C94a74758f2ff413c9f705725701b8d02%7C0%7C0%7C638503644324879127%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C&sdata=PkMnglOHo3q9hgHMSOyDsJug1rM0HJJO2YW%2FgtRUtW0%3D&reserved=0
  scsi/7611d95d0aada3814a5b140661b3b5188b8b86bb.ca...@redhat.com/T/

  Getting alerts from monitoring tools about high average CPU usage.
  Machine reporting the following:

  root@server:~# uptime
   17:04:34 up 14 days,  6:33,  2 users,  load average: 15.66, 15.88, 15.94

  root@server:~# top -d 1

  top - 17:04:49 up 14 days,  6:33,  2 users,  load average: 15.59, 15.85, 15.93
  Tasks: 223 total,   1 running, 222 sleeping,   0 stopped,   0 zombie
  %Cpu(s):  0.7 us,  1.4 sy,  0.0 ni, 49.3 id, 48.6 wa,  0.0 hi,  0.0 si,  0.0 
st
  MiB Mem :   7896.6 total,   1772.6 free,   1163.9 used,   4960.0 buff/cache
  MiB Swap:   2048.0 total,   1784.6 free,263.4 used.   6431.6avail Mem

  PID USER  PR  NIVIRTRESSHR S  %CPU  %MEM TIME+ COMMAND
   88 root  20   0   0  0  0 D  55.4   0.0  11275:46 
scsi_eh_1

  root@server:~# lsb_release -rd
  Description:Ubuntu 22.04.3 LTS
  Release:22.04

  root@server:~# apt-cache policy linux-image-virtual-hwe-22.04-edge
  linux-image-virtual-hwe-22.04-edge:
Installed: 6.5.0.14.14~22.04.6
Candidate: 6.5.0.14.14~22.04.7
Version table:
   6.5.0.14.14~22.04.7 500
  500 
https://nam10.safelinks.protection.outlook.com/?url=http%3A%2F%2Fus.archive.ubuntu.com%2Fubuntu&data=05%7C02%7Cdrew_reis%40gensler.com%7Caa2ee77f19b24bd7689908dc6bae78e8%7C94a74758f2ff413c9f705725701b8d02%7C0%7C0%7C638503644324885309%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C&sdata=gPrK1nNfbsxG84ZwqwLBYjT0SO5pehjcA78j5U3IPSE%3D&reserved=0
 jammy-updates/main amd64 Packages
  500 
https://nam10.safelinks.protection.outlook.com/?url=http%3A%2F%2Fsecurity.ubuntu.com%2Fubuntu&data=05%7C02%7Cdrew_reis%40gensler.com%7Caa2ee77f19b24bd7689908dc6bae78e8%7C94a74758f2ff413c9f705725701b8d02%7C0%7C0%7C638503644324888966%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C&sdata=OmDdYEQ6WlEFtwTyVrFV%2BZSqMFfkCU%2BO7XZCVJXRc2o%3D&reserved=0
 jammy-security/main amd64 Packages
   *** 6.5.0.14.14~22.04.6 100
  100 /var/lib/dpkg/status
   5.15.0.25.27 500
  500 
https://nam10.safelinks.protection.outlook.com/?url=http%3A%2F%2Fus.archive.ubuntu.com%2Fubuntu&data=05%7C02%7Cdrew_reis%40gensler.com%7Caa2ee77f19b24bd7689908dc6bae78e8%7C94a74758f2ff413c9f705725701b8d02%7C0%7C0%7C638503644324893922%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C&sdata=JR3G%2Fag6CELAWOxKRrHAZC7DF4HzQaZc6TbgfAoOBnc%3D&reserved=0
 jammy/main amd64 Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-6.5.0-14-generic 6.5.0-14.14~22.04.1
  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
  CasperMD5CheckResult: 

[Bug 2064147] Re: OneDrive integration causes sigfault after entering My Files

[Andrew Baker]

** Bug watch added: gitlab.gnome.org/GNOME/gvfs/-/issues #732
   https://gitlab.gnome.org/GNOME/gvfs/-/issues/732

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

** Summary changed:

- OneDrive integration causes sigfault after entering My Files
+ Unable to browse My Files using OneDrive integration

** Information type changed from Public to Private

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2064147

Title:
  Unable to browse My Files using OneDrive integration

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2064147] Re: OneDrive integration causes sigfault after entering My Files

[Andrew Baker]

Captured gvfsd debug log of entering My Files

** Attachment added: "gvfs debug log"
   
https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/2064147/+attachment/5772565/+files/gvfsd.log

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2064147

Title:
  Unable to browse My Files using OneDrive integration

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2064147] [NEW] Unable to browse My Files using OneDrive integration

[Andrew Baker]

Private bug reported:

The new OneDrive integration is causing a sigfault when opening the My
Files folder.

Release information:
No LSB modules are available.
Description:Ubuntu 24.04 LTS
Release:24.04

Apt Cache:
gvfs:
  Installed: 1.54.0-1ubuntu2
  Candidate: 1.54.0-1ubuntu2
  Version table:
 *** 1.54.0-1ubuntu2 500
500 http://gb.archive.ubuntu.com/ubuntu noble/main amd64 Packages
100 /var/lib/dpkg/status

Expected result:

1. Sign in to Microsoft 365 using personal account
2. Open Nautilus
3. Mount OneDrive storage
4. Enter My Files
5. Nautilus displays files in OneDrive

Actual result:

1. Sign in to Microsoft 365 using personal account
2. Open Nautilus
3. Mount OneDrive storage
4. Enter My Files
5. Nautilus shows "This location could not be displayed. Sorry, could not 
display all the contents of "My Files": The connection is closed"

ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: gvfs 1.54.0-1ubuntu2
ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1
Uname: Linux 6.8.0-31-generic x86_64
ApportVersion: 2.28.1-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Mon Apr 29 18:03:59 2024
InstallationDate: Installed on 2024-04-26 (3 days ago)
InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424)
ProcEnviron:
 LANG=en_US.UTF-8
 PATH=(custom, no user)
 SHELL=/bin/bash
 TERM=xterm-256color
 XDG_RUNTIME_DIR=
SourcePackage: gvfs
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: gvfs
 Importance: Unknown
 Status: Unknown

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


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

** Attachment added: "Screencast of fault"
   
https://bugs.launchpad.net/bugs/2064147/+attachment/5772559/+files/Screencast%20from%202024-04-29%2018-09-30.webm

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2064147

Title:
  Unable to browse My Files using OneDrive integration

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2018425] Re: apt install ubuntu-desktop takes forever

[Andrew N]

Hi, I’ve run into this issue many times and today tracked down the cause
to this open bug: https://bugs.launchpad.net/netplan/+bug/1999178

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2018425

Title:
  apt install ubuntu-desktop takes forever

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 794098] Re: [Regression] linux: 2.6.32-33.66 -proposed tracker

[Andrew Foran]

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

i have also facing the same type of issue on my client's site kindly
visit: https://www.pikashowgeeks.com/pikashow-for-ios/

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/794098

Title:
  [Regression] linux: 2.6.32-33.66 -proposed tracker

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/794098/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2063325] Re: postgis no longer works after dist-upgrade

[Andrew Gallagher]

This error went away on restart, so it's probably safe to close.

** Description changed:

  After dist-upgrading from focal to jammy, postgis no longer works due to
- an undeclared dependency on glibc 3.4.29:
+ an undeclared dependency on glibc++ 3.4.29:
  
  ```
  Apr 24 10:55:14 tiles2 renderd[1761]:reason: Postgis Plugin: ERROR:  
could not load library "/usr/lib/postgresql/12/lib/postgis-3.so": 
/lib/x86_64-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.29'
  not found (required by /lib/x86_64-linux-gnu/libSFCGAL.so.1)#012LINE 16: )
  ```
  
  This makes it both impossible to use postgis, and impossible to migrate
  to postgresql 14, since for a postgres upgrade both versions must be
  operational simultaneously.
  
  See also https://bugs.launchpad.net/ubuntu/+source/update-
  manager/+bug/1907652?comments=all and
  https://bugs.launchpad.net/ubuntu/+source/postgis/+bug/1950772 .
  
  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: postgis 3.2.0+dfsg-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-177.197-generic 5.4.268
  Uname: Linux 5.4.0-177-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Wed Apr 24 10:59:04 2024
  ProcEnviron:
-  TERM=xterm-256color
-  PATH=(custom, no user)
-  LANG=en_US.UTF-8
-  SHELL=/bin/bash
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: postgis
  UpgradeStatus: Upgraded to jammy on 2024-04-23 (0 days ago)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2063325

Title:
  postgis no longer works after dist-upgrade

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2063325] [NEW] postgis no longer works after dist-upgrade

[Andrew Gallagher]

Public bug reported:

After dist-upgrading from focal to jammy, postgis no longer works due to
an undeclared dependency on glibc 3.4.29:

```
Apr 24 10:55:14 tiles2 renderd[1761]:reason: Postgis Plugin: ERROR:  could 
not load library "/usr/lib/postgresql/12/lib/postgis-3.so": 
/lib/x86_64-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.29'
not found (required by /lib/x86_64-linux-gnu/libSFCGAL.so.1)#012LINE 16: )
```

This makes it both impossible to use postgis, and impossible to migrate
to postgresql 14, since for a postgres upgrade both versions must be
operational simultaneously.

See also https://bugs.launchpad.net/ubuntu/+source/update-
manager/+bug/1907652?comments=all and
https://bugs.launchpad.net/ubuntu/+source/postgis/+bug/1950772 .

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: postgis 3.2.0+dfsg-1ubuntu1
ProcVersionSignature: Ubuntu 5.4.0-177.197-generic 5.4.268
Uname: Linux 5.4.0-177-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5CheckResult: unknown
Date: Wed Apr 24 10:59:04 2024
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
RebootRequiredPkgs: Error: path contained symlinks.
SourcePackage: postgis
UpgradeStatus: Upgraded to jammy on 2024-04-23 (0 days ago)

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


** Tags: amd64 apport-bug jammy

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2063325

Title:
  postgis no longer works after dist-upgrade

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2045708] Re: [SRU] Improve debian/99-gce.rules to set schedulers based on disk

[Andrew Cloke]

As outlined in the [Test Case] for focal:

 * Images have been built with these packages from the -proposed pocket and
   published in the `ubuntu-os-cloud-image-proposed` project
 * The images have gone through CPC's own CTF framework and testing has been 
successful
 * The images have been shared with the Google team and their testing has also 
been successful


** Tags removed: verification-needed verification-needed-focal
** Tags added: verification-done verification-done-focal

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2045708

Title:
  [SRU] Improve debian/99-gce.rules to set schedulers based on disk

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gce-compute-image-packages/+bug/2045708/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2052438] Re: Update d/control file with a dependency on google-guest-agent

[Andrew Cloke]

As outlined in the [Test Case] for focal:

 * Images have been built with these packages from the -proposed pocket and
   published in the `ubuntu-os-cloud-image-proposed` project
 * The images have gone through CPC's own CTF framework and testing has been 
successful
 * The images have been shared with the Google team and their testing has also 
been successful


** Tags removed: verification-needed verification-needed-focal
** Tags added: verification-done verification-done-focal

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2052438

Title:
  Update d/control file with a dependency on google-guest-agent

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/google-compute-engine-oslogin/+bug/2052438/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2061599] [NEW] cant download apache

[Andrew Cambron]

Public bug reported:

error code in subprocess usr/bin/dpkg

ProblemType: Package
DistroRelease: Ubuntu 22.04
Package: gitweb 1:2.34.1-1ubuntu1.10
ProcVersionSignature: Ubuntu 6.5.0-26.26~22.04.1-generic 6.5.13
Uname: Linux 6.5.0-26-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.5
AptOrdering:
 apache2:amd64: Install
 apache2-bin:amd64: Install
 apache2-data:amd64: Install
 apache2-utils:amd64: Install
 NULL: ConfigurePending
Architecture: amd64
CasperMD5CheckResult: pass
Date: Mon Apr 15 13:33:35 2024
ErrorMessage: installed gitweb package post-installation script subprocess 
returned error exit status 1
InstallationDate: Installed on 2024-02-21 (54 days ago)
InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.2)
PackageArchitecture: all
Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 
3.10.6-1~22.04
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.21.1ubuntu2.3
 apt  2.4.12
SourcePackage: git
Title: package gitweb 1:2.34.1-1ubuntu1.10 failed to install/upgrade: installed 
gitweb package post-installation script subprocess returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)
modified.conffile..etc.apache2.conf-available.gitweb.conf: [deleted]

** Affects: ubuntu
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package jammy

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2061599

Title:
  cant download apache

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2045708] Re: [SRU] Improve debian/99-gce.rules to set schedulers based on disk

[Andrew Cloke]

As outlined in the [Test Case] for mantic and jammy:

 * Images have been built with these packages from the -proposed pocket and
   published in the `ubuntu-os-cloud-image-proposed` project
 * The images have gone through CPC's own CTF framework and testing has been 
successful
 * The images have been shared with the Google team and their testing has also 
been successful

The Google's team testing of the focal images is still ongoing.

** Tags removed: verification-needed-jammy verification-needed-mantic
** Tags added: verification-done-jammy verification-done-mantic

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2045708

Title:
  [SRU] Improve debian/99-gce.rules to set schedulers based on disk

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gce-compute-image-packages/+bug/2045708/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2052438] Re: Update d/control file with a dependency on google-guest-agent

[Andrew Cloke]

As outlined in the [Test Case] for mantic and jammy:

 * Images have been built with these packages from the -proposed pocket and
   published in the `ubuntu-os-cloud-image-proposed` project
 * The images have gone through CPC's own CTF framework and testing has been 
successful
 * The images have been shared with the Google team and their testing has also 
been successful

The Google's team testing of the focal images is still ongoing.


** Tags removed: verification-needed-jammy verification-needed-mantic
** Tags added: verification-done-jammy verification-done-mantic

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2052438

Title:
  Update d/control file with a dependency on google-guest-agent

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/google-compute-engine-oslogin/+bug/2052438/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2045708] Re: [SRU] Improve debian/99-gce.rules to set schedulers based on disk

[Andrew Cloke]

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2045708

Title:
  [SRU] Improve debian/99-gce.rules to set schedulers based on disk

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gce-compute-image-packages/+bug/2045708/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2059847] Re: Input lag or freezes on Nvidia desktops with X11

[Andrew Fernandes]

Daniel (@vanvugt) Thank you very much for your hard work, out-of-band
patch (the ppa!), and speed addressing this extremely subtle, yet
annoying bug... much appreciated!

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2059847

Title:
  Input lag or freezes on Nvidia desktops with X11

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2058411] Re: Builds with gcc -fsanitize=address crashing on startup

[Andrew Burnard]

Also affects me, using Uname: Linux 6.5.0-26-generic x86_64

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2058411

Title:
  Builds with gcc -fsanitize=address crashing on startup

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2058307] [NEW] package libjurt-java 1:6.4.7-0ubuntu0.20.04.9 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration

[Andrew Ken Bell]

Public bug reported:

issue arose while installing first updates after install of ubuntu 20.04
operating system

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: libjurt-java 1:6.4.7-0ubuntu0.20.04.9
ProcVersionSignature: Ubuntu 5.15.0-101.111~20.04.1-generic 5.15.143
Uname: Linux 5.15.0-101-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.27
Architecture: amd64
CasperMD5CheckResult: skip
Date: Tue Mar 19 09:52:18 2024
DuplicateSignature:
 package:libjurt-java:1:6.4.7-0ubuntu0.20.04.9
 Setting up uno-libs-private (1:6.4.7-0ubuntu0.20.04.9) ...
 dpkg: error processing package libjurt-java (--configure):
  package is in a very bad inconsistent state; you should
ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
InstallationDate: Installed on 2024-03-18 (0 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
PackageArchitecture: all
Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.19.7ubuntu3.2
 apt  2.0.10
SourcePackage: libreoffice
Title: package libjurt-java 1:6.4.7-0ubuntu0.20.04.9 failed to install/upgrade: 
package is in a very bad inconsistent state; you should  reinstall it before 
attempting configuration
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package focal need-duplicate-check

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2058307

Title:
  package libjurt-java 1:6.4.7-0ubuntu0.20.04.9 failed to
  install/upgrade: package is in a very bad inconsistent state; you
  should  reinstall it before attempting configuration

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2051876] Re: tpm2_nvwrite using an offset causes a TPM error

[Andrew Oswald]

With the advent of 22.04.4, this issue seems to have been resolved.

Thanks again for looking into it, Sudip!  =)

** Changed in: tpm2-tools (Ubuntu)
   Status: Incomplete => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2051876

Title:
  tpm2_nvwrite using an offset causes a TPM error

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2051876] Re: tpm2_nvwrite using an offset causes a TPM error

[Andrew Oswald]

Hello again, Sudip, hope this message finds you well!

I attempted to recreate the issue using a cert whose footprint exceeds
the 1,024 byte TPM data bus by using two tpm2_nvwrite commands (the
second of which specifying --offset=1024) and I'm happy to report that
it's working!

However, we were experiencing the issue on HP gear and this is a Dell
laptop.. so I still need to test it on HP.

thanks again!
-andy

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2051876

Title:
  tpm2_nvwrite using an offset causes a TPM error

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2051876] Re: tpm2_nvwrite using an offset causes a TPM error

[Andrew Oswald]

Thanks for looking into this, Sudip!  I will need to write up explicit
instructions, but the issue only shows up when you attempt to write to
an offset, which (I would presume) is why your test didn't produce any
issues.  My usecase is storing a DER encoded x509 certificate whose
footprint exceeds the TPM data bus size, thus requiring multiple
tpm2_nvwrite calls, with any call other than the initial, requiring the
--offset flag and the appropriate offset starting point.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2051876

Title:
  tpm2_nvwrite using an offset causes a TPM error

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2048876] Re: Allow server and pool sources to be overridden through a conf.d or sources.d configuration

[Andrew Cloke]

Many thanks for that feedback and guidance. In parallel with working on
the suggested changes, I wanted to understand the right approach we
should take to fixing this bug.

From your comment in #1 "It can't hurt to discuss with Debian but it's
highly doubtful they'll take our delta", would it be reasonable to
assume that, as Ubuntu has already branched the chrony config associated
with NTP pools away from Debian, we should attempt to land this bug fix
to the NTP pools config directly into Ubuntu?

Thanks again for your help, Andy.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2048876

Title:
  Allow server and pool sources to be overridden through a conf.d or
  sources.d configuration

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2048945] Re: scsi_eh_* process using idle CPU after upgrade to kernel 6.5

[Andrew Reis]

Bump. Is anyone looking at this at all?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2048945

Title:
  scsi_eh_* process using idle CPU after upgrade to kernel 6.5

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1884299] Re: Chromium snap won't run with nfs home drive

[Andrew Conway]

Matthieu, more recently a more likely problem has been characterized by Alberto 
Mardegan and found the line in question in
https://bugs.launchpad.net/snapd/+bug/1973321

In particular, restarting snapd doesn't help at all for me, so having
the directory mounted before snapd starts doesn't help, and the same
problem occurs with other file systems. However _starting_ outside the
home directory does help. This is the situation for me with Kerberos
authenticated NFS, and others with sshfs. I don't know whether it is
relevant for people using NFS without authentication. It is easy to test
for yourself - restart snapd and see if that helps.

So I think there is progress in understanding the problem, even if not
working out how to fix it.

FYI: I initially tried a work around where I used the debian repository
for firefox instead of the snap version, but despite giving it a higher
priority (confirmed via "sudo apt policy firefox") I found the debian
package twice over a week uninstalled and replaced by the snap version
that then would not start. I can manually revert it but it is
inconvenient. Any suggestions on how to make that work reliably would be
appreciated.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1884299

Title:
  Chromium snap won't run with nfs home drive

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1964763] Re: QtChooser doesn't support qt6

[Andrew Hayzen]

I was going to request this change into Debian as well, but appears that
has already been attempted and was rejected due to "qtchooser is dead
upstream". https://salsa.debian.org/qt-kde-
team/qt/qtchooser/-/merge_requests/2

I wonder if the situation can be improved though as if you are trying to
use Qt 6 tooling in a container image then you need workarounds :-/

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1964763

Title:
  QtChooser doesn't support qt6

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1973114] Re: Key trust verification fails on Ubuntu 22.04

[Andrew Cloke]

Thanks Fabio. Adjusted tags accordingly.

** Tags removed: verification-needed verification-needed-jammy
** Tags added: verification-done verification-done-jammy

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1973114

Title:
   Key trust verification fails on Ubuntu 22.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ec2-instance-connect/+bug/1973114/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1966773] Re: [FFe] remove zfs option from the installer

[Andrew L. Moore]

Why would Ubuntu want to remove ZFS support?  I use both Ubuntu and
Fedora but would have no reason to continue with Ubuntu without ZFS.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1966773

Title:
  [FFe] remove zfs option from the installer

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1784774] Re: snapd is not autofs aware and fails with nfs home dir

[Andrew Conway]

Thanks Alberto. I tried running "hello" in a different directory, and
you were correct:

arc@andrewfairfield:~$ hello
cannot open path of the current working directory: Permission denied
arc@andrewfairfield:~$ cd /
arc@andrewfairfield:/$ hello
Hello, world!
arc@andrewfairfield:/$ 

[ This is in 20.04, not 22.04 ]

Yay! that is the first time I have seen a snap actually work with my
normal user account.

This feels like significant progress in working out what is going on!

Of course firefox needs access to the home directory to load the profile
and store downloads. Is the whole process run as some other user (a la
sudo) or is there just some starting stub running as some other user
doing something that returns to the actual user after doing something
that thinks it needs access to the current directory but could get by
without it?

Actually, I can sort of answer that - I tried running "musescore" as a snap, 
starting from /
It successfully ran. I tried saving something, and it sort of did... but in a 
new, empty "home" directory in a /home/arc/snap/musescore/216/ that the save 
file dialog went to when I pressed the home button. Is this normal behaviour 
for a snap? Regardless of the inconvenience of the subdirectory, that is 
running over nfs successfully. I can close Musescore and load it again. But not 
with cwd=/home/arc.

So that is fairly strong evidence supporting your idea that it is the
same root cause as https://bugs.launchpad.net/bugs/1973321 . I will add
a comment there.

Thanks for the insight Alberto!

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1784774

Title:
  snapd is not autofs aware and fails with nfs home dir

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1884299] Re: Chromium snap won't run with nfs home drive

[Andrew Conway]

I (using Kerberos) don't the get apparmor DENIED messages that Eric (not
using Kerberos) did, but I get exactly the same "cannot open path of the
current working directory: Permission denied" error.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1884299

Title:
  Chromium snap won't run with nfs home drive

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1784774] Re: snapd is not autofs aware and fails with nfs home dir

[Andrew Conway]

Using NVFv4, kerberos authenticated, mounted by autofs:

arc@andrewshoreham:~$ hello
cannot open path of the current working directory: Permission denied

[ Then as user with sudo privs, sudo systemctl restart snapd ]

arc@andrewshoreham:~$ hello
cannot open path of the current working directory: Permission denied


Logs since just before restarting snapd

syslog
--
May 15 14:54:09 andrewshoreham kernel: [12319.195323] audit: type=1400 
audit(1652590449.676:183): apparmor="ALLOWED" operation="open" 
profile="/usr/sbin/sssd" name="/proc/24886/cmdline" pid=910 comm="sssd_nss" 
requested_mask="r" denied_mask="r" fsuid=0 ouid=0
May 15 14:54:09 andrewshoreham systemd[1]: Stopping Snap Daemon...
May 15 14:54:09 andrewshoreham snapd[726]: main.go:155: Exiting on terminated 
signal.
May 15 14:54:09 andrewshoreham snapd[726]: overlord.go:504: Released state lock 
file
May 15 14:54:09 andrewshoreham systemd[1]: snapd.service: Deactivated 
successfully.
May 15 14:54:09 andrewshoreham systemd[1]: Stopped Snap Daemon.
May 15 14:54:09 andrewshoreham systemd[1]: snapd.service: Consumed 2.753s CPU 
time.
May 15 14:54:09 andrewshoreham systemd[1]: Starting Snap Daemon...
May 15 14:54:09 andrewshoreham snapd[24890]: AppArmor status: apparmor is 
enabled and all features are available
May 15 14:54:09 andrewshoreham snapd[24890]: overlord.go:263: Acquiring state 
lock file
May 15 14:54:09 andrewshoreham snapd[24890]: overlord.go:268: Acquired state 
lock file
May 15 14:54:09 andrewshoreham snapd[24890]: daemon.go:247: started 
snapd/2.55.3+22.04 (series 16; classic) ubuntu/22.04 (amd64) 
linux/5.15.0-25-generic.
May 15 14:54:09 andrewshoreham kernel: [12319.270748] loop11: detected capacity 
change from 0 to 8
May 15 14:54:09 andrewshoreham snapd[24890]: daemon.go:340: adjusting startup 
timeout by 1m10s (pessimistic estimate of 30s plus 5s per snap)
May 15 14:54:09 andrewshoreham systemd[1]: 
tmp-sanity\x2dmountpoint\x2d2760788470.mount: Deactivated successfully.
May 15 14:54:09 andrewshoreham snapd[24890]: backend.go:133: snapd enabled NFS 
support, additional implicit network permissions granted
May 15 14:54:10 andrewshoreham kernel: [12319.549118] audit: type=1400 
audit(1652590450.028:184): apparmor="STATUS" operation="profile_replace" 
profile="unconfined" name="/usr/lib/snapd/snap-confine" pid=24926 
comm="apparmor_parser"
May 15 14:54:10 andrewshoreham kernel: [12319.578896] audit: type=1400 
audit(1652590450.060:185): apparmor="STATUS" operation="profile_replace" 
profile="unconfined" 
name="/usr/lib/snapd/snap-confine//mount-namespace-capture-helper" pid=24926 
comm="apparmor_parser"
May 15 14:54:10 andrewshoreham kernel: [12319.969313] audit: type=1400 
audit(1652590450.448:186): apparmor="STATUS" operation="profile_replace" 
profile="unconfined" name="/snap/snapd/15534/usr/lib/snapd/snap-confine" 
pid=24946 comm="apparmor_parser"
May 15 14:54:10 andrewshoreham kernel: [12319.983029] audit: type=1400 
audit(1652590450.464:187): apparmor="STATUS" operation="profile_replace" 
profile="unconfined" 
name="/snap/snapd/15534/usr/lib/snapd/snap-confine//mount-namespace-capture-helper"
 pid=24946 comm="apparmor_parser"
May 15 14:54:10 andrewshoreham kernel: [12320.165228] audit: type=1400 
audit(1652590450.644:188): apparmor="STATUS" operation="profile_replace" 
profile="unconfined" name="snap.snapd-desktop-integration.hook.configure" 
pid=24950 comm="apparmor_parser"
May 15 14:54:10 andrewshoreham kernel: [12320.341043] audit: type=1400 
audit(1652590450.820:189): apparmor="STATUS" operation="profile_replace" 
profile="unconfined" 
name="snap.snapd-desktop-integration.snapd-desktop-integration" pid=24951 
comm="apparmor_parser"
May 15 14:54:11 andrewshoreham kernel: [12320.633250] audit: type=1400 
audit(1652590451.112:190): apparmor="STATUS" operation="profile_replace" 
info="same as current profile, skipping" profile="unconfined" 
name="snap-update-ns.snap-store" pid=24948 comm="apparmor_parser"
May 15 14:54:11 andrewshoreham kernel: [12320.721431] audit: type=1400 
audit(1652590451.200:191): apparmor="STATUS" operation="profile_replace" 
info="same as current profile, skipping" profile="unconfined" 
name="snap-update-ns.snapd-desktop-integration" pid=24949 comm="apparmor_parser"
May 15 14:54:11 andrewshoreham kernel: [12320.727129] audit: type=1400 
audit(1652590451.208:192): apparmor="STATUS" operation="profile_replace" 
info="same as current profile, skipping" profile="unconfined" 
name="snap-update-ns.hello" pid=24954 comm="apparmor_parser"
May 15 14:54:11 andrewshoreham systemd[1]: Started Snap Daemon.
May 15 14:54:11 andrewshoreham dbus-daemon[693]: [system] Activating via 
systemd: service name='org.freedesktop.timedate1' 
unit='dbus-org.freedesktop.timedate1.service' requested by ':1.166' (uid=0 
pid=24890 comm="/usr/lib/snapd/snapd " label="unconfined")
May 15 14:54:11 andrewshoreham systemd[1]: Starting Time & Date Service...
May 15 14:54:11 andrewshoreham dbus-daemon[693]: [system] Successfully 
activated

[Bug 1643706] Re: snap apps need to be able to browse outside of user $HOME dir. for Desktop installs

[Andrew Aitchison]

> The whole issue also raises the silly question: what is so security-
sensitive about /tmp?

Another, non-privileged, user can write to it, so could leave a trojan
(malware) in there ...

Ubuntu has /tmp/user/uid which I assume exists to work around that issue,
but chromium wont let me see /tmp/user// or file:///tmp/user//

One workaround would be to consistently use a directory you can access
through snap, such as /home/USER/tmp, instead of /tmp. (Globally)
setting TMP, TEMP, TMPDIR and/or TEMPDIR may help with this ...

https://www.the-art-of-web.com/php/where-is-tmp/ describes some other
"solutions" to this problem that have caused problems.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1643706

Title:
  snap apps need to be able to browse outside of user $HOME dir. for
  Desktop installs

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1396379] Re: installer uses first EFI system partition found even when directed otherwise

[Andrew Byrd]

I encountered this last week installing Ubuntu 22.04. I booted from USB
install media and installed to a second attached USB storage device. I
created an EFI system partition on the install target device, and
specifically selected this EFI system partition in the GUI as the place
to install the bootloader. However the bootloader was instead installed
to the EFI system partition of the machine's internal SSD.

I reproduced the process running ubiquity from a terminal with the debug
flag. The section of the logs that appears relevant is reproduced below.
The logs show it fetching the debconf value and running "grub-install
/dev/sdd1", which correctly reflects the partition I selected in the UI.

Based on documentation and various forum discussions I'm reading, my
impression is that the device is specified as a parameter to the grub-
install command (as Ubiquity seems to be doing here) for MBR installs
and EFI installs work differently, requiring the target EFI system
partition to be mounted on /boot/efi. Is this correct, and it possible
Ubiquity is missing some unmount/remount steps here?


debconf (developer): <-- METAGET grub-installer/progress/step_bootdev 
description
debconf (developer): --> 1 Determining GRUB boot device...
May  7 21:22:29 debconf (filter): --> 0 OK
May  7 21:22:29 debconf (filter): <-- FGET grub-installer/bootdev seen
debconf (developer): <-- FGET grub-installer/bootdev seen
debconf (developer): --> 0 true
May  7 21:22:29 debconf (filter): <-- GET grub-installer/bootdev
debconf (developer): <-- GET grub-installer/bootdev
debconf (developer): --> 1 /dev/sdd1
May  7 21:22:29 debconf (filter): <-- PROGRESS STEP 1
May  7 21:22:29 debconf (filter): widget found for grub-installer/progress/title
May  7 21:22:29 debconf (filter): --> 0 OK
May  7 21:22:29 debconf (filter): <-- SUBST 
grub-installer/progress/step_install_loader BOOTDEV /dev/sdd1
debconf (developer): <-- SUBST grub-installer/progress/step_install_loader 
BOOTDEV /dev/sdd1
debconf (developer): --> 0
May  7 21:22:29 debconf (filter): <-- PROGRESS INFO 
grub-installer/progress/step_install_loader
May  7 21:22:29 debconf (filter): widget found for grub-installer/progress/title
debconf (developer): <-- METAGET grub-installer/progress/step_install_loader 
description
debconf (developer): --> 1 Running "grub-install /dev/sdd1"...
May  7 21:22:29 debconf (filter): --> 0 OK
May  7 21:22:29 debconf (filter): <-- INPUT low 
grub-installer/force-efi-extra-removable
debconf (developer): <-- METAGET grub-installer/force-efi-extra-removable Type
debconf (developer): --> 1 boolean
debconf (developer): <-- INPUT low grub-installer/force-efi-extra-removable
debconf (developer): --> 30 question skipped
May  7 21:22:29 debconf (filter): <-- GO 
debconf (developer): <-- GO 
debconf (developer): --> 0 ok
May  7 21:22:29 debconf (filter): <-- GET 
grub-installer/force-efi-extra-removable
debconf (developer): <-- GET grub-installer/force-efi-extra-removable
debconf (developer): --> 1 false
May  7 21:22:32 debconf (filter): <-- GET grub-installer/make_active
debconf (developer): <-- GET grub-installer/make_active
debconf (developer): --> 1 true
May  7 21:22:32 debconf (filter): <-- PROGRESS STEP 1
May  7 21:22:32 debconf (filter): widget found for grub-installer/progress/title
May  7 21:22:32 debconf (filter): --> 0 OK
May  7 21:22:32 debconf (filter): <-- PROGRESS INFO 
grub-installer/progress/step_config_loader
May  7 21:22:32 debconf (filter): widget found for grub-installer/progress/title
debconf (developer): <-- METAGET grub-installer/progress/step_config_loader 
description
debconf (developer): --> 1 Running "update-grub"...

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1396379

Title:
  installer uses first EFI system partition found even when directed
  otherwise

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1784774] Re: snapd is not autofs aware and fails with nfs home dir

[Andrew Conway]

I got exactly the same errors as Miles above; a simple permission denied
error stopping things before AppArmor got involved.

I.e., the answer to Markus Kuhn's question is no, in fact even in
enforce mode there are no denied apparmor complaints.

I don't know whether this is because the gating problem is not being
able to read the ticket in /tmp, or whether being in the kernel solves
some of the apparmor issues, but the greater pickiness of kerberos user
definition is an issue. Do snaps run as a different uid?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1784774

Title:
  snapd is not autofs aware and fails with nfs home dir

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1884299] Re: Chromium snap won't run with nfs home drive

[Andrew Conway]

Firefox also doesn't work now it is a snap in 22.04.

I think there are still multiple issues here. The original poster seems
to be using NVSv3 I believe based on the RPC errors (NFSv3 uses multiple
ports, one of which is called something like RPC, but I am not an expert
in this as I have only used NFSv4, which uses a single port). Is this
correct tylerecouture?

NFSv3 has no user authentication; NFSv4 uses Kerberos for authentication
(and privacy and tamper resistance). I think this brings in additional
problems as snaps don't appear to work with Kerberos

e.g.

https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1849346

https://bugzilla.mozilla.org/show_bug.cgi?id=1734791

I get a very different error - a simple permission denied error rather
than an AppArmor problem.



** Bug watch added: Mozilla Bugzilla #1734791
   https://bugzilla.mozilla.org/show_bug.cgi?id=1734791

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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1884299

Title:
  Chromium snap won't run with nfs home drive

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1971895] [NEW] Warning messages from stat printed on installation with no user crontabs

[Andrew Ruthven]

Public bug reported:

On installation of cron on a new system, or (I expect) an upgrade with
no user crontab files the following is printed:

Setting up cron (3.0pl1-128.1ubuntu1.1) ...
stat: cannot stat '*': No such file or directory
stat: cannot stat '*': No such file or directory
stat: cannot stat '*': No such file or directory
Warning: * is not a regular file!

This is related to the fix for CVE-2017-9525 introduced in
3.0pl1-128.1ubuntu1.1. The for loop at line 66 of cron.postinst needs to
have a guard like the following added to it:

[ "$tab_name" = "*" ] && continue

We have observed this with Bionic, I haven't checked any other Ubuntu
releases.

Cheers,
Andrew

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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1971895

Title:
  Warning messages from stat printed on installation with no user
  crontabs

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1662552] Re: snaps don't work with NFS home

[Andrew Conway]

I am pretty sure this is at least partly a problem with snaps not
working with Kerberos, which is the authentication mechanism for NFS.
The Kerberos credentials are (with good reason) not stored in the home
directory.

I described this in more detail in bug 1784774.

This means that firefox and lxd don't work in 22.04 with authenticated
NFS home directories.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1662552

Title:
  snaps don't work with NFS home

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1784774] Re: snapd is not autofs aware and fails with nfs home dir

[Andrew Conway]

I did some more investigating, and I think there are two independent problems 
here:
(1) The problem as believed so far, network access permissions
(2) New insight: Kerberos doesn't work with snaps.
This explains why fixing (1) didn't help me (or Adam).

Background: Kerberos is the authentication mechanism used for NFS.
Assuming you are using authentication (as almost everyone does), then
when you access NFS contents, you need to provide kerberos credentials.
These are stored outside of your home directory (after all, home
directories are one of the most common reasons to use NFS, so you can't
store them there). I believe snaps restrict access to just your home
directory, so you can't access the Kerberos key and therefore can't
access your home directory.

This is supported by various bugs like
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1849346
(unresolved) which is a different but relevant issue - people who don't
use NFS but do use Kerberos features in Firefox found they don't work
post snap conversion.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1784774

Title:
  snapd is not autofs aware and fails with nfs home dir

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1969162] Re: bad interaction between snapd and update-notifier when snapd package is being upgraded

[Andrew Robbins]

ah whoops-please undo

** Changed in: snapd (Ubuntu)
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1969162

Title:
  bad interaction between snapd and update-notifier when snapd package
  is being upgraded

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1662552] Re: snaps don't work with NFS home

[Andrew Conway]

This still doesn't work with 22.04, which is a problem for firefox,
which is now installed as a snap. This seems somewhat strange as firefox
obviously needs network access, so it is not just the network access
that causes problems.

Running firefox from the command line produces an error complaining that
it doesn't have read access to the current working directory (which
would be true if it were as a different user as a different user doesn't
have access to the kerberos ticket).

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1662552

Title:
  snaps don't work with NFS home

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1784774] Re: snapd is not autofs aware and fails with nfs home dir

[Andrew Conway]

I never got it to work in 20.04, so I don't know whether your fix ever
made it in.

I have just installed Jammy Jellyfish (22.04), and can confirm snaps
don't work in it when using autofs and nfs mounted home directories.

The prior work around was just never use any snap applications, which
was OK as nothing important was in snaps prior to 22.04.

This is harder in 22.04 as firefox is distributed as a snap, and so
firefox doesn't work in 22.04 if you have autofs NFS home directories.

Work around is to use a different source for firefox,
https://ubuntuhandbook.org/index.php/2022/04/install-firefox-deb-
ubuntu-22-04/ but I don't know whether that will get security updates as
quickly, so this is a serious problem.

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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1784774

Title:
  snapd is not autofs aware and fails with nfs home dir

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1956243] Re: Ping give socket error initially if IPv6 is disabled

[Andrew Welham]

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1956243

Title:
  Ping give socket  error initially if IPv6 is disabled

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1969211] Re: Out of date driver with no capabilities for 2.5Gb full duplex

[Andrew Welham]

I got it working, and confirmed the bug, only problem is it will get
overwritten with the next patch, and others cant use the fix.

Hopefully this is a quick fix for a proc dev.

This is how i did it


 When you try to compile the drivers you get

./r8152-2.15.0/r8152.c:18530:25: error: initialization of ‘int (*)(struct 
net_device *, struct ethtool_coalesce *, struct kernel_ethtool_coalesce *, 
struct netlink_ext_ack *)’ from incompatible pointer type ‘int (*)(struct 
net_device *, struct ethtool_coalesce *)’ [-Werror=incompatible-pointer-types]
18530 | .get_coalesce = rtl8152_get_coalesce,
  | ^~~~
./r8152-2.15.0/r8152.c:18530:25: note: (near initialization for 
‘ops.get_coalesce’)
./r8152-2.15.0/r8152.c:18531:25: error: initialization of ‘int (*)(struct 
net_device *, struct ethtool_coalesce *, struct kernel_ethtool_coalesce *, 
struct netlink_ext_ack *)’ from incompatible pointer type ‘int (*)(struct 
net_device *, struct ethtool_coalesce *)’ [-Werror=incompatible-pointer-types]
18531 | .set_coalesce = rtl8152_set_coalesce,

I had a look at the code and googled  (i cant code in C or C++ btw)
This site had similar code
https://sbexr.rabexc.org/latest/sources/26/53bfa290b96570.html#e00100031001

so i made the following changes to the realtek code. not sure if it
right or performant, but it now compiles


# diff ./r8152.c ../r8152-2.15.0/r8152.c
18339,18341c18339
<   struct ethtool_coalesce *coalesce,
<   struct kernel_ethtool_coalesce *,
<   struct netlink_ext_ack *)
---
>   struct ethtool_coalesce *coalesce)
18360,18363c18358
<   struct ethtool_coalesce *coalesce,
< struct kernel_ethtool_coalesce *,
< struct netlink_ext_ack *)
<
---
>   struct ethtool_coalesce *coalesce)

make install copied the code , but throws the following error, looks to
do with code signing ??? Any way i ignored it

At main.c:160:
- SSL error:02001002:system library:fopen:No such file or directory: 
../crypto/bio/bss_file.c:69
- SSL error:2006D080:BIO routines:BIO_new_file:no such file: 
../crypto/bio/bss_file.c:76
sign-file: certs/signing_key.pem: No such file or directory


I ran

# sudo depmod -a
# sudo update-initramfs -u

as requested by the drivers readme file

 rebooted

 ethtool -s enx5c857e38e9b7 autoneg on advertise 0x802f

now works

 ethtool enx5c857e38e9b7
Settings for enx5c857e38e9b7:
Supported ports: [ MII ]
Supported link modes:   10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
1000baseT/Full
2500baseT/Full
Supported pause frame use: No
Supports auto-negotiation: Yes
Supported FEC modes: Not reported
Advertised link modes:  10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
1000baseT/Full
2500baseT/Full
Advertised pause frame use: No
Advertised auto-negotiation: Yes
Advertised FEC modes: Not reported
Link partner advertised link modes:  10baseT/Half 10baseT/Full
 100baseT/Half 100baseT/Full
 1000baseT/Full
 2500baseT/Full
Link partner advertised pause frame use: No
Link partner advertised auto-negotiation: Yes
Link partner advertised FEC modes: Not reported
Speed: 2500Mb/s
Duplex: Full
Auto-negotiation: on
Port: MII
PHYAD: 32
Transceiver: internal
Supports Wake-on: pumbg
Wake-on: g
Current message level: 0x7fff (32767)
   drv probe link timer ifdown ifup rx_err tx_err 
tx_queued intr tx_done rx_status pktdata hw wol
Link detected: yes


checking the version

# modinfo /lib/modules/5.15.0-25-generic/kernel/drivers/net/usb/r8152.ko
filename:   /lib/modules/5.15.0-25-generic/kernel/drivers/net/usb/r8152.ko
version:v2.15.0 (2021/04/15)
license:GPL

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1969211

Title:
  Out of date driver with no capabilities for 2.5Gb full duplex

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1969211] [NEW] Out of date driver with no capabilities for 2.5Gb full duplex

[Andrew Welham]

Public bug reported:

Running on the latest release of ubuntu 22.04, with a usb-2.5gb ethernet
dongle containing the 8156b chip.

This chip is supported 8156b  by the R5182 driver.

see https://www.realtek.com/en/component/zoo/category/network-interface-
controllers-10-100-1000m-gigabit-ethernet-usb-3-0-software

The repository states the driver is not required above kernel 5.6, but the 
driver in this release of ubuntu looks to be out of date 
# modinfo r8152.ko
filename:   /lib/modules/5.15.0-25-generic/kernel/drivers/net/usb/r8152.ko
version:v1.12.12

and v 2.15.0 int he realtek repository


The driver only allows the max speed is 2500 / half

ethtool enx5c857e38e9b7

Settings for enx5c857e38e9b7:
Supported ports: [  ]
Supported link modes:   Not reported
Supported pause frame use: No
Supports auto-negotiation: No
Supported FEC modes: Not reported
Advertised link modes:  Not reported
Advertised pause frame use: No
Advertised auto-negotiation: No
Advertised FEC modes: Not reported
Speed: 2500Mb/s
Duplex: Half
Auto-negotiation: off
Port: Twisted Pair
PHYAD: 0
Transceiver: internal
MDI-X: Unknown
Current message level: 0x0007 (7)
   drv probe link
Link detected: yes

and the command to increase the speed

ethtool -s enx5c857e38e9b7 autoneg on advertise 0x802f

responds with 
netlink error: Operation not supported


I tried to build the driver, but it fails to build on ubuntu 22.04, but builds 
fine on older released ( in know not much help)

/home/andrew/r8152-2.15.0/r8152.c:18530:25: note: (near initialization for 
‘ops.get_coalesce’)
/home/andrew/r8152-2.15.0/r8152.c:18531:25: error: initialization of ‘int 
(*)(struct net_device *, struct ethtool_coalesce *, struct 
kernel_ethtool_coalesce *, struct netlink_ext_ack *)’ from incompatible pointer 
type ‘int (*)(struct net_device *, struct ethtool_coalesce *)’ 
[-Werror=incompatible-pointer-types]
18531 | .set_coalesce = rtl8152_set_coalesce,

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: linux-modules-extra-5.15.0-25-generic 5.15.0-25.25 [modified: 
lib/modules/5.15.0-25-generic/kernel/drivers/net/usb/r8152.ko]
ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
Uname: Linux 5.15.0-25-generic x86_64
AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k5.15.0-25-generic.
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
ApportVersion: 2.20.11-0ubuntu82
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/controlC2', '/dev/snd/hwC2D0', '/dev/snd/pcmC2D2c', 
'/dev/snd/pcmC2D1p', '/dev/snd/pcmC2D0c', '/dev/snd/pcmC2D0p', 
'/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D10p', 
'/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', 
'/dev/snd/pcmC0D3p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer'
Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer'
Card2.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer'
Card2.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer'
CasperMD5CheckResult: pass
Date: Fri Apr 15 11:22:22 2022
InstallationDate: Installed on 2022-04-14 (0 days ago)
InstallationMedia: Ubuntu-Server 22.04 LTS "Jammy Jellyfish" - Beta amd64 
(20220330)
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
MachineType: System manufacturer System Product Name
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-25-generic 
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro
RelatedPackageVersions:
 linux-restricted-modules-5.15.0-25-generic N/A
 linux-backports-modules-5.15.0-25-generic  N/A
 linux-firmware 20220329.git681281e4-0ubuntu1
RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/19/2019
dmi.bios.release: 5.14
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1405
dmi.board.asset.tag: Default string
dmi.board.name: PRIME X570-PRO
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1405:bd11/19/2019:br5.14:svnSystemmanufacturer:pnSystemProduct

[Bug 1933301] Re: [uacc-0623] hisi_sec2 fail to alloc uacce

[Andrew Cloke]

** Changed in: kunpeng920/ubuntu-22.04
   Status: Fix Committed => Fix Released

** Changed in: kunpeng920
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1933301

Title:
  [uacc-0623] hisi_sec2  fail to alloc uacce

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1967924] Re: One overlayfs fix has not been backported to the 5.13 branch

[Andrew Vagin]

Any update?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1967924

Title:
  One overlayfs fix has not been backported to the 5.13 branch

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1967924] [NEW] One overlayfs fix has not been backported to the 5.13 bracnh

[Andrew Vagin]

Public bug reported:

The next patch has not been ported to the the 5.13 branch:

$ git show Ubuntu-azure-5.8-5.8.0-1033.35_20.04.1~656
commit 5f5716d1f7ece06c66d7d8145dd6b3a5886b3e56
Author: Alexander Mikhalitsyn 
Date:   Mon Apr 26 10:11:00 2021 +0200

UBUNTU: SAUCE: overlayfs: fix incorrect mnt_id of files opened from 
map_files

BugLink: https://bugs.launchpad.net/bugs/1857257

...

Fixes: d24b8a5 ("UBUNTU: SAUCE: overlayfs: allow with shiftfs as
underlay")


But it isn't in the 5.13 branch:

$ git log --pretty=oneline origin/azure-5.13-next fs/overlayfs/file.c 
1e6145d8708c831d2aa5c26aa15eb98e1a1683b9 ovl: fix use after free in struct 
ovl_aio_req
7b5bda27d1fc4d7bde20cf6ed203fe88c458169a ovl: fix IOCB_DIRECT if underlying fs 
doesn't support direct IO
1626e7f7ab7eb74e142fec7fe6b7c9614972a56b ovl: fix deadlock in splice write
1443bc4a25ca84d60d39a8ae1dc6215abdd637a4 UBUNTU: SAUCE: overlayfs: allow with 
shiftfs as underlay

** Affects: linux-azure (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: kernel-bug

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1967924

Title:
  One overlayfs fix has not been backported to the 5.13 bracnh

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1857257] Re: linux-image-5.0.0-35-generic breaks checkpointing of container

[Andrew Vagin]

** Also affects: linux-azure (Ubuntu)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1857257

Title:
  linux-image-5.0.0-35-generic breaks checkpointing of container

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1966980] [NEW] GIMP crashes as soon as text tool is used

[Andrew Packer]

Public bug reported:

```
GNU Image Manipulation Program version 2.10.18
git-describe: GIMP_2_10_16-38-gde7f04567d
Build: unknown rev 0 for linux
# C compiler #
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/9/lto-wrapper
OFFLOAD_TARGET_NAMES=nvptx-none:hsa
OFFLOAD_TARGET_DEFAULT=1
Target: x86_64-linux-gnu
Configured with: ../src/configure -v --with-pkgversion='Ubuntu 
9.3.0-8ubuntu1' --with-bugurl=file:///usr/share/doc/gcc-9/README.Bugs 
--enable-languages=c,ada,c++,go,brig,d,fortran,objc,obj-c++,gm2 --prefix=/usr 
--with-gcc-major-version-only --program-suffix=-9 
--program-prefix=x86_64-linux-gnu- --enable-shared --enable-linker-build-id 
--libexecdir=/usr/lib --without-included-gettext --enable-threads=posix 
--libdir=/usr/lib --enable-nls --enable-clocale=gnu --enable-libstdcxx-debug 
--enable-libstdcxx-time=yes --with-default-libstdcxx-abi=new 
--enable-gnu-unique-object --disable-vtable-verify --enable-plugin 
--enable-default-pie --with-system-zlib --with-target-system-zlib=auto 
--enable-objc-gc=auto --enable-multiarch --disable-werror --with-arch-32=i686 
--with-abi=m64 --with-multilib-list=m32,m64,mx32 --enable-multilib 
--with-tune=generic --enable-offload-targets=nvptx-none,hsa 
--without-cuda-driver --enable-checking=release --build=x86_64-linux-gnu 
--host=x86_64-linux-gnu --target=x86_64-linux-gnu
Thread model: posix
gcc version 9.3.0 (Ubuntu 9.3.0-8ubuntu1) 

# Libraries #
using babl version 0.1.74 (compiled against version 0.1.74)
using GEGL version 0.4.22 (compiled against version 0.4.22)
using GLib version 2.64.6 (compiled against version 2.64.1)
using GdkPixbuf version 2.40.0 (compiled against version 2.40.0)
using GTK+ version 2.24.32 (compiled against version 2.24.32)
using Pango version 1.44.7 (compiled against version 1.44.7)
using Fontconfig version 2.13.1 (compiled against version 2.13.1)
using Cairo version 1.16.0 (compiled against version 1.16.0)

```
> GIMP-CRITICAL: gimp_tool_key_press: assertion 'gimp_tool_control_is_active 
> (tool->control) == FALSE' failed

Stack trace:
```

# Stack traces obtained from PID 28234 - Thread 28234 #

[New LWP 28236]
[New LWP 28237]
[New LWP 28238]
[New LWP 28250]
[New LWP 28251]
[New LWP 28259]
[New LWP 28297]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
__libc_read (nbytes=256, buf=0x7ffd6d110d10, fd=15) at 
../sysdeps/unix/sysv/linux/read.c:26
  Id   Target Id   Frame 
* 1Thread 0x7f9d8c631340 (LWP 28234) "gimp-2.10"   __libc_read (nbytes=256, 
buf=0x7ffd6d110d10, fd=15) at ../sysdeps/unix/sysv/linux/read.c:26
  2Thread 0x7f9d8beca700 (LWP 28236) "worker"  syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  3Thread 0x7f9d8b6c9700 (LWP 28237) "worker"  syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  4Thread 0x7f9d8aec8700 (LWP 28238) "worker"  syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  5Thread 0x7f9d5a7e8700 (LWP 28250) "gmain"   0x7f9d8d46c9cf in 
__GI___poll (fds=0x5634fef2c370, nfds=2, timeout=-1) at 
../sysdeps/unix/sysv/linux/poll.c:29
  6Thread 0x7f9d5cfe9700 (LWP 28251) "gdbus"   0x7f9d8d46c9cf in 
__GI___poll (fds=0x5634fef444b0, nfds=2, timeout=-1) at 
../sysdeps/unix/sysv/linux/poll.c:29
  7Thread 0x7f9d896c5700 (LWP 28259) "async"   syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  8Thread 0x7f9d7bfff700 (LWP 28297) "swap writer" syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38

Thread 8 (Thread 0x7f9d7bfff700 (LWP 28297)):
#0  syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
No locals.
#1  0x7f9d8d765623 in g_cond_wait () from 
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
No symbol table info available.
#2  0x7f9d8dc65aad in ?? () from /usr/lib/x86_64-linux-gnu/libgegl-0.4.so.0
No symbol table info available.
#3  0x7f9d8d741ad1 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
No symbol table info available.
#4  0x7f9d8d554609 in start_thread (arg=) at 
pthread_create.c:477
ret = 
pd = 
unwind_buf = {cancel_jmp_buf = {{jmp_buf = {140314366965504, 
3992424551288561243, 140726433284430, 140726433284431, 140726433284576, 
140314366961792, -4009040371817750949, -4009071936541270437}, mask_was_saved = 
0}}, priv = {pad = {0x0, 0x0, 0x0, 0x0}, data = {prev = 0x0, cleanup = 0x0, 
canceltype = 0}}}
not_first_call = 0
#5  0x7f9d8d479163 in clone () at 
../sysdeps/unix/sysv/linux/x86_64/clone.S:95
No locals.

Thread 7 (Thread 0x7f9d896c5700 (LWP 28259)):
#0  syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
No locals.
#1  0x7f9d8d765623 in g_cond_wait () from 
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
No symbol table info available.
#2  0x5634fe290d84 in ?? ()
No symbol table info available.
#

[Bug 1961425] Re: 22.04: FTBFS due to test failure

[Andrew Cloke]

As 0.8.0-2ubuntu2 has fixed the build issue, marking this bug as "Fix Released".
Please feel free to revert if the issue is persisting.

** Changed in: capnproto (Ubuntu)
   Status: Confirmed => Fix Released

** Changed in: ubuntu-power-systems
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1961425

Title:
  22.04: FTBFS due to test failure

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1957053] Re: BleachBit shows Errors trying to update

[Andrew Ziem]

This was fixed two years ago for BleachBit 4.0.0
https://github.com/bleachbit/bleachbit/issues/819

The latest BleachBit 4.4.0 is here https://www.bleachbit.org/

Ubuntu has a "no rolling release" policy, so the version in the Ubuntu
repository may be rather old.

** Bug watch added: github.com/bleachbit/bleachbit/issues #819
   https://github.com/bleachbit/bleachbit/issues/819

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1957053

Title:
  BleachBit shows Errors trying to update

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1473527] Re: module ssh-authkey-fingerprints fails Input/output error: /dev/console

[Andrew Lee]

I've fixed this in https://github.com/canonical/cloud-
init/pull/1340/files (sadly blocked on getting the CLA signed)

I'm interested that you've hit this too @tony-casanova-nc-33-2017.

FWIW, I'm using:
- cloud-init 22.1
- I'm on a Microsoft OS called 'Mariner'
- I'm on VMware vSphere V7 -> I've only ever seen this bug on VMware. 

Are you using similar versions?

I'm fairly sure there's a corresponding VMware bug here (causing the
kernel to incorrectly set up the /dev/ttyS0 serial device).

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1473527

Title:
  module ssh-authkey-fingerprints fails Input/output error: /dev/console

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1473527] Re: module ssh-authkey-fingerprints fails Input/output error: /dev/console

[Andrew Lee]

I've also hit this (on VMware), and while I suspect that may be due to
some particular funnies of the OS I am on, I agree a defensive fix in
cloud-init to not raise an Exception if you can't write to /dev/console
and fall back to writing to stdout would be welcomed.

Any objections if I raise a PR to do that?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1473527

Title:
  module ssh-authkey-fingerprints fails Input/output error: /dev/console

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1942684] Re: Kernel 5.14.X / 5.13.14 fails to boot

[Andrew Purtell]

Running 5.13.0-xx on Parallels Desktop on M1 Macbook. 5.13.0-12-generic
is the last kernel that will boot. -13 and -14 have been withdrawn,
apparently. -15 and -16 just hang as soon as control is given to the
kernel back from the EFI loader. Some fail code was backported post -12
from more recent kernels it seems.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1942684

Title:
  Kernel 5.14.X / 5.13.14 fails to boot

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1957716] Re: Update for CVE-2021-43860 and CVE-2022-21682

[Andrew Hayzen]

@alexmurray, hey, I believe that commit was reverted later as it caused
a behavioural regression? The Github advisory
(https://github.com/flatpak/flatpak/security/advisories/GHSA-8ch7-5j3h-g4fx)
was changed to point to a different commit
(https://github.com/flatpak/flatpak/commit/5709f1aaed6579f0136976e14e7f3cae399134ca).

When creating that debdiff, if i recall correctly I went though the
commits in this branch
https://github.com/flatpak/flatpak/commits/flatpak-1.10.x combined with
referring to the github advisories and then skipped the "Make
--nofilesystem=host/home remove access to subdirs of those"
(307ee18dd62f65c1319594501d01bbdb10f88ab8) as it was reverted later with
"Revert "Make --nofilesystem=host/home remove access to subdirs of
those"" (ed91bba615d4e50ccd7de53ca9861e367175bbfb).

Please correct me if you think i've missed something :-)

In the github advisory
(https://github.com/flatpak/flatpak/security/advisories/GHSA-8ch7-5j3h-g4fx)
there are two commits for flatpak-builder so this could also be done.

Also note I tried looking at focal/bionic but there are a large amount
of merge conflicts due to substantial change in the codebase and I'm not
familiar enough with GObject/GLib etc to rewrite that code.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1957716

Title:
  Update for CVE-2021-43860 and CVE-2022-21682

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1962304] [NEW] package ubuntustudio-branding-common 20.04.1 failed to install/upgrade: installed ubuntustudio-branding-common package post-installation script subprocess returned error exit statu

[Andrew]

Public bug reported:

I'm on a Raspberry Pi 4 Cannakit build. I have had some troubles with a
lot of various packages. I'm not sure if there's a way around this. I
thought I read somewhere you have to use curl for everything, but I had
trouble with that too. I'll keep playing around with it and see what I
can find.

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: ubuntustudio-branding-common 20.04.1
ProcVersionSignature: Ubuntu 5.4.0-1052.58-raspi 5.4.162
Uname: Linux 5.4.0-1052-raspi aarch64
ApportVersion: 2.20.11-0ubuntu27.21
Architecture: arm64
CasperMD5CheckResult: skip
Date: Fri Feb 25 11:20:23 2022
DuplicateSignature:
 package:ubuntustudio-branding-common:20.04.1
 Setting up ubuntustudio-branding-common (20.04.1) ...
 /var/lib/dpkg/info/ubuntustudio-branding-common.postinst: 22: update-grub: not 
found
 dpkg: error processing package ubuntustudio-branding-common (--configure):
  installed ubuntustudio-branding-common package post-installation script 
subprocess returned error exit status 127
ErrorMessage: installed ubuntustudio-branding-common package post-installation 
script subprocess returned error exit status 127
ImageMediaBuild: 20210819.1
PackageArchitecture: all
Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.19.7ubuntu3.1
 apt  2.0.6
SourcePackage: ubuntustudio-look
Title: package ubuntustudio-branding-common 20.04.1 failed to install/upgrade: 
installed ubuntustudio-branding-common package post-installation script 
subprocess returned error exit status 127
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: ubuntustudio-look (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: apport-package arm64 arm64-image focal need-duplicate-check 
raspi-image uec-images

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1962304

Title:
  package ubuntustudio-branding-common 20.04.1 failed to
  install/upgrade: installed ubuntustudio-branding-common package post-
  installation script subprocess returned error exit status 127

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1927076] Re: IPv6 TCP in reuseport_bpf_cpu from ubuntu_kernel_selftests/net crash P8 node entei (Oops: Exception in kernel mode, sig: 4 [#1])

[Andrew Cloke]

Marking as "incomplete" while waiting for input from Power MMU experts.

** Changed in: ubuntu-power-systems
   Status: Confirmed => Incomplete

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1927076

Title:
  IPv6 TCP in reuseport_bpf_cpu from ubuntu_kernel_selftests/net crash
  P8 node entei (Oops: Exception in kernel mode, sig: 4 [#1])

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1927076/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1933301] Re: [uacc-0623] hisi_sec2 fail to alloc uacce

[Andrew Cloke]

** Changed in: kunpeng920/ubuntu-21.10
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1933301

Title:
  [uacc-0623] hisi_sec2  fail to alloc uacce

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1951289] Re: ubuntu_ltp_controllers:cpuset_sched_domains: tests 3, 9, 11, 17, 19, 25 report incorrect sched domain for cpu#32

[Andrew Cloke]

** Changed in: kunpeng920
   Importance: Undecided => Low

** Changed in: kunpeng920
 Assignee: (unassigned) => dann frazier (dannf)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1951289

Title:
  ubuntu_ltp_controllers:cpuset_sched_domains: tests 3,9,11,17,19,25
  report incorrect sched domain for cpu#32

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1956202] Re: `libexpat1-dev` CMake configuration error

[Andrew Aitchison]

https://github.com/OSGeo/gdal/issues/5324 is a result of this and the
upstream https://github.com/libexpat/libexpat/issues/501

** Bug watch added: github.com/OSGeo/gdal/issues #5324
   https://github.com/OSGeo/gdal/issues/5324

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1956202

Title:
  `libexpat1-dev` CMake configuration error

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1956202] Re: `libexpat1-dev` CMake configuration error

[Andrew Aitchison]

** Bug watch added: github.com/libexpat/libexpat/issues #501
   https://github.com/libexpat/libexpat/issues/501

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1956202

Title:
  `libexpat1-dev` CMake configuration error

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1956202] Re: `libexpat1-dev` CMake configuration error

[Andrew Aitchison]

** Also affects: expat via
   https://github.com/libexpat/libexpat/issues/501
   Importance: Unknown
   Status: Unknown

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1956202

Title:
  `libexpat1-dev` CMake configuration error

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1751954] Re: Bluetooth and Wi-Fi items in Power are worded ambiguously

[Andrew-Q]

It says above fix released in August, however I still have the bad
wording and it has caught me out today.  I'm running Ubuntu 20.04.03
gnome 3.36.8.  Why has the fix not reached me yet please?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1751954

Title:
  Bluetooth and Wi-Fi items in Power are worded ambiguously

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1953386] Re: hisi_sas driver may oops in prep_ssp_v3_hw()

[Andrew Cloke]

** Changed in: kunpeng920/ubuntu-18.04
   Status: Fix Committed => Fix Released

** Changed in: kunpeng920
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1953386

Title:
  hisi_sas driver may oops in prep_ssp_v3_hw()

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1742852] Re: [hostname, Realtek ALC294, Speaker, Internal] No sound at all after windows update

[Andrew Platt]

Having a similar issue on my ASUS Zenbook UX434, also using the ALC294
as above, Kernel: 5.13.0-28-generic.

In my case after a reboot from my Windows 10 dual boot the audio out is
fine, but the microphone has very loud crackling which makes it
unusable. The problem isn't fixed by a reboot but after a full shutdown
and restart the problem seems to go away. Thanks to Hilikus for the
workaround!

Had an identical problem on Kubuntu 20.04 and now ZorinOS 16 - clearly
this issue isn't entirely fixed even with more recent kernel patches.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1742852

Title:
  [hostname, Realtek ALC294, Speaker, Internal] No sound at all after
  windows update

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1959926] [NEW] Version v1.9 has compiler bug when reading from 64-bit BAR

[Andrew]

Public bug reported:

There's a known issue in nvme-cli where the compiler optimizes out BAR
accesses into a single 64B read rather than 2 32-bits. This causes some
devices to hang and reboot the system. This bug was fixed in version
v1.14. The ubuntu supported version should be >= v1.14.

** Affects: nvme-cli (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1959926

Title:
  Version v1.9 has compiler bug when reading from 64-bit BAR

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs