[Desktop-packages] [Bug 1958019]

[soyer]

I don't know the reasons, but this code has been working in this way for
10+ years, so this type of collision can not be common.

I sent the ALC285_FIXUP_THINKPAD_HEADSET_JACK patch to the lists:
https://lore.kernel.org/all/7ffae10ebba58601d25fe2ff8381a6ae3a926e62.1708687813.git.so...@irl.hu/

And I sent a question about how to handle this collision:
https://lore.kernel.org/all/d5b42e483566a3815d229270abd668131a0d9f3a.ca...@irl.hu/

If you are interested in linux sound development, you can subscribe to the 
linux-sound list:
http://vger.kernel.org/vger-lists.html#linux-sound

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

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

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

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

  uname -r
  5.11.0-44-generic

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/sound-2.6/+bug/1958019/+subscriptions


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

[Desktop-packages] [Bug 2054771] Re: Kernel panic boot error with kernel 6.5.0.21

[atactic]

Could restore a working Kernel 6.5.0.21 with 
$ sudo apt update
$ sudo apt upgrade

However, the system starts up directly without asking for the user
login, which is really weird.

There is also a security warning when updating:

$ sudo apt update
Hit:1 http://archive.ubuntu.com/ubuntu mantic InRelease
Hit:2 http://archive.ubuntu.com/ubuntu mantic-updates InRelease
Hit:3 http://archive.ubuntu.com/ubuntu mantic-backports InRelease  
Hit:4 http://security.ubuntu.com/ubuntu mantic-security InRelease  
Ign:5 http://linux.dropbox.com/ubuntu mantic InRelease 
Hit:6 http://linux.dropbox.com/ubuntu mantic Release   
Get:7 http://linux.dropbox.com/ubuntu mantic Release.gpg [488 B]
Ign:7 http://linux.dropbox.com/ubuntu mantic Release.gpg 
Hit:8 https://dl.google.com/linux/chrome/deb stable InRelease
Reading package lists... Done
W: GPG error: http://linux.dropbox.com/ubuntu mantic Release: The following 
signatures were invalid: BADSIG FC918B335044912E Dropbox Automatic Signing Key 

E: The repository 'http://linux.dropbox.com/ubuntu mantic Release' is not 
signed.
N: Updating from such a repository can't be done securely, and is therefore 
disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration 
details.
N: Skipping acquire of configured file 'main/binary-i386/Packages' as 
repository 'https://dl.google.com/linux/chrome/deb stable InRelease' doesn't 
support architecture 'i386'

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

Title:
  Kernel panic boot error with kernel 6.5.0.21

Status in network-manager package in Ubuntu:
  New

Bug description:
  Booting on kernel 6.5.0.21-generic returns error:

  'Unable to mount root fs on unknown-block(0.0)'

  The system starts up correctly with the previous kernel
  6.7.0.17-generic

  Trying fixing 6.5.0.21-generic does not work:

  
  $ update-initramfs -u -k 6.5.0.21-generic
  update-initramfs: Generating /boot/initrd.img-6.5.0.21-generic
  touch: cannot touch '/boot/initrd.img-6.5.0.21-generic.new': Permission denied
  W: Kernel configuration /boot/config-6.5.0.21-generic is missing, cannot 
check for zstd compression support (CONFIG_RD_ZSTD)
  W: missing /lib/modules/6.5.0.21-generic
  W: Ensure all necessary drivers are built into the linux image!
  depmod: ERROR: could not open directory /lib/modules/6.5.0.21-generic: No 
such file or directory
  depmod: FATAL: could not search modules: No such file or directory
  cat: 
/var/tmp/mkinitramfs_uR0VlQ/lib/modules/6.5.0.21-generic/modules.builtin: No 
such file or directory
  W: Can't find modules.builtin.modinfo (for locating built-in drivers' 
firmware, supported in Linux >=5.2)
  /dev/mapper/control: open failed: Permission denied
  Failure to communicate with kernel device-mapper driver.
  Incompatible libdevmapper 1.02.185 (2022-05-18) and kernel driver (unknown 
version).
  Command failed.
  /dev/mapper/control: open failed: Permission denied
  Failure to communicate with kernel device-mapper driver.
  Incompatible libdevmapper 1.02.185 (2022-05-18) and kernel driver (unknown 
version).
  Command failed.
  /dev/mapper/control: open failed: Permission denied
  Failure to communicate with kernel device-mapper driver.
  Incompatible libdevmapper 1.02.185 (2022-05-18) and kernel driver (unknown 
version).
  Command failed.
  /dev/mapper/control: open failed: Permission denied
  Failure to communicate with kernel device-mapper driver.
  Incompatible libdevmapper 1.02.185 (2022-05-18) and kernel driver (unknown 
version).
  Command failed.
  I: The initramfs will attempt to resume from /dev/dm-2
  I: (UUID=ae16e50c-6748-4c2f-877f-b084acd65a51)
  I: Set the RESUME variable to override this.
  cp: cannot access '/etc/lvm/backup': Permission denied
  depmod: WARNING: could not open modules.order at 
/var/tmp/mkinitramfs_uR0VlQ/lib/modules/6.5.0.21-generic: No such file or 
directory
  depmod: WARNING: could not open modules.builtin at 
/var/tmp/mkinitramfs_uR0VlQ/lib/modules/6.5.0.21-generic: No such file or 
directory
  depmod: WARNING: could not open modules.builtin.modinfo at 
/var/tmp/mkinitramfs_uR0VlQ/lib/modules/6.5.0.21-generic: No such file or 
directory
  /usr/sbin/mkinitramfs: 539: cannot create 
/boot/initrd.img-6.5.0.21-generic.new: Permission denied
  update-initramfs: failed for /boot/initrd.img-6.5.0.21-generic with 2.

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


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

[Desktop-packages] [Bug 2054864] [NEW] Only Link Local IPv6 after upgrading to 22.04.4 LTS from 22.04.3

[David]

Public bug reported:

After I ran the updater last week, my computer could only have a Link
Local address for IPv6. I have now confirmed that IPv6 works normally
when I install a fresh copy of 22.04.3 LTS and has the bug even after a
fresh install of 22.04.4 LTS. Previous data and fault finding on this
fault can be found on 2 Ask Ubuntu Posts I made regarding this fault
during the last week (Note: Originally I thought that this was just an
mDNS6 fault, hence the inaccurate title on the first post):

First Ask Ubuntu Post: https://askubuntu.com/questions/1503895/cant-
ping-dynamic-ipv6-xubuntu-hostname-from-kubuntu-laptop

Second Ask Ubuntu Post: https://askubuntu.com/questions/1504030/only-
ipv6-link-local-address-after-ubuntu-update

The Ubuntu Release I am currently using is:
Description:Ubuntu 22.04.4 LTS
Release:22.04

network-manager version reports as:
  Installed: 1.36.6-0ubuntu2
  Candidate: 1.36.6-0ubuntu2
  Version table:
 *** 1.36.6-0ubuntu2 500

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: network-manager 1.36.6-0ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-18.18~22.04.1-generic 6.5.8
Uname: Linux 6.5.0-18-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CRDA: N/A
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Sat Feb 24 16:02:45 2024
InstallationDate: Installed on 2024-02-24 (0 days ago)
InstallationMedia: Ubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 
(20240220)
IpRoute:
 default via 192.168.0.1 dev wlp3s0 proto dhcp metric 600 
 192.168.0.0/24 dev wlp3s0 proto kernel scope link src 192.168.0.203 metric 600
ProcEnviron:
 LANGUAGE=en_AU:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_AU.UTF-8
 SHELL=/bin/bash
SourcePackage: network-manager
UpgradeStatus: No upgrade log present (probably fresh install)
nmcli-nm:
 RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  WIFI  
   WWAN-HW  WWAN
 running  1.36.6   connected  started  full  enabled enabled  
enabled  enabled  enabled

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


** Tags: amd64 apport-bug jammy

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

Title:
  Only Link Local IPv6 after upgrading to 22.04.4 LTS from 22.04.3

Status in network-manager package in Ubuntu:
  New

Bug description:
  After I ran the updater last week, my computer could only have a Link
  Local address for IPv6. I have now confirmed that IPv6 works normally
  when I install a fresh copy of 22.04.3 LTS and has the bug even after
  a fresh install of 22.04.4 LTS. Previous data and fault finding on
  this fault can be found on 2 Ask Ubuntu Posts I made regarding this
  fault during the last week (Note: Originally I thought that this was
  just an mDNS6 fault, hence the inaccurate title on the first post):

  First Ask Ubuntu Post: https://askubuntu.com/questions/1503895/cant-
  ping-dynamic-ipv6-xubuntu-hostname-from-kubuntu-laptop

  Second Ask Ubuntu Post: https://askubuntu.com/questions/1504030/only-
  ipv6-link-local-address-after-ubuntu-update

  The Ubuntu Release I am currently using is:
  Description:  Ubuntu 22.04.4 LTS
  Release:  22.04

  network-manager version reports as:
Installed: 1.36.6-0ubuntu2
Candidate: 1.36.6-0ubuntu2
Version table:
   *** 1.36.6-0ubuntu2 500

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: network-manager 1.36.6-0ubuntu2
  ProcVersionSignature: Ubuntu 6.5.0-18.18~22.04.1-generic 6.5.8
  Uname: Linux 6.5.0-18-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Feb 24 16:02:45 2024
  InstallationDate: Installed on 2024-02-24 (0 days ago)
  InstallationMedia: Ubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 
(20240220)
  IpRoute:
   default via 192.168.0.1 dev wlp3s0 proto dhcp metric 600 
   192.168.0.0/24 dev wlp3s0 proto kernel scope link src 192.168.0.203 metric 
600
  ProcEnviron:
   LANGUAGE=en_AU:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.36.6   connected  started  full  enabled enabled  
enabled  enabled  enabled

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


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

[Desktop-packages] [Bug 2054859] [NEW] VNC connection issues with 22.04

[Dan Towle]

Public bug reported:

I have several computers running 20.04 and a couple running 22.04. VNC
was great on 20.04. I could connect using remina or real vnc no problem.
on the 22.04 machines though, I cannot connect reliably at all. If the
server montitor is in sleep, the server rejects the connection. On some
machines I can connect once, but then not again until I restart the vnc
server.

The issue is the same using rdp or vnc.

I have searched on this, but couldn't find any information that was
helpful.

Thanks. Loving Ubuntu (35 year mac user)

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-15.15~22.04.1-generic 6.5.3
Uname: Linux 6.5.0-15-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: unknown
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Fri Feb 23 18:33:28 2024
DistUpgraded: 2022-09-04 14:22:00,091 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
DistroCodename: jammy
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller])
   Subsystem: Apple Inc. 2nd Generation Core Processor Family Integrated 
Graphics Controller [106b:00e6]
InstallationDate: Installed on 2021-12-13 (803 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
MachineType: Apple Inc. Macmini5,1
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-15-generic 
root=UUID=3c9a744c-c73a-44bc-95a9-149b6bbc399a ro quiet splash vt.handoff=7
RebootRequiredPkgs: Error: path contained symlinks.
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to jammy on 2022-09-04 (537 days ago)
dmi.bios.date: 04/09/2018
dmi.bios.release: 0.1
dmi.bios.vendor: Apple Inc.
dmi.bios.version: MM51.88Z.0080.B00.1804091930
dmi.board.asset.tag: Base Board Asset Tag#
dmi.board.name: Mac-8ED6AF5B48C039E1
dmi.board.vendor: Apple Inc.
dmi.board.version: Macmini5,1
dmi.chassis.type: 16
dmi.chassis.vendor: Apple Inc.
dmi.chassis.version: Mac-8ED6AF5B48C039E1
dmi.modalias: 
dmi:bvnAppleInc.:bvrMM51.88Z.0080.B00.1804091930:bd04/09/2018:br0.1:svnAppleInc.:pnMacmini5,1:pvr1.0:rvnAppleInc.:rnMac-8ED6AF5B48C039E1:rvrMacmini5,1:cvnAppleInc.:ct16:cvrMac-8ED6AF5B48C039E1:skuSystemSKU#:
dmi.product.family: Macmini
dmi.product.name: Macmini5,1
dmi.product.sku: System SKU#
dmi.product.version: 1.0
dmi.sys.vendor: Apple Inc.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3.1~22.04.2
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.8
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1

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


** Tags: amd64 apport-bug jammy ubuntu

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

Title:
  VNC connection issues with 22.04

Status in xorg package in Ubuntu:
  New

Bug description:
  I have several computers running 20.04 and a couple running 22.04. VNC
  was great on 20.04. I could connect using remina or real vnc no
  problem. on the 22.04 machines though, I cannot connect reliably at
  all. If the server montitor is in sleep, the server rejects the
  connection. On some machines I can connect once, but then not again
  until I restart the vnc server.

  The issue is the same using rdp or vnc.

  I have searched on this, but couldn't find any information that was
  helpful.

  Thanks. Loving Ubuntu (35 year mac user)

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.5.0-15.15~22.04.1-generic 6.5.3
  Uname: Linux 6.5.0-15-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Feb 23 18:33:28 2024
  DistUpgraded: 2022-09-04 14:22:00,091 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0126] (rev 09) (prog-if 

[Desktop-packages] [Bug 2049628] Re: Persistent Audio Issues on Dell Vostro 3400 Running Ubuntu 22.04.3 LTS

[aminesaka]

** Description changed:

- Since the last three weeks' updates, I have encountered several
- challenges with the audio functionality on my system. Primarily, upon
- starting my laptop, the audio often fails to work, displaying "Dummy
- Output." To resolve this, I find myself needing to restart the laptop
- two or three times before the audio becomes functional.
- 
- Even when the audio is working, I've noticed a recurring issue where,
- after playing video or audio for approximately 2-3 minutes, the sound
- starts crackling and buzzing. The intensity of these distortions
- gradually increases, resembling the static interference on a radio
- station with a weak signal. This issue persists even when using 3.5mm
- headphones, requiring the use of a USB headset or Bluetooth headphones
- to enjoy distortion-free audio.
- 
- Furthermore, I have observed that, regardless of the Ubuntu version
- (ranging from 22.04 to 22.04.3), I face difficulties changing the
- microphone output settings when an external audio peripheral, such as a
- USB headset, 3.5mm headphones, or Bluetooth headphones, is connected.
- The OS appears to exclusively utilize the microphone from the connected
- peripheral, making it impossible to switch to the laptop's built-in
- microphone.
- 
- For your reference, here are the specifications of my laptop and the
- Ubuntu version I am currently using:
- 
- Laptop: Dell Vostro 3400
- CPU: 11th Gen Intel i5-1135G7
- GPU: Intel TigerLake-LP GT2 Iris Xe
- Memory: 2490MiB / 19720MiB
- Resolution: 1920x1080
- OS: Ubuntu 22.04.3 LTS x86_64
- Kernel: 6.5.0-14-generic
- DE: GNOME 42.9
- Shell: bash 5.1.16
- Sound Card: Card: HDA Intel PCH, Chip: Cirrus Logic CS8409/CS42L42
- 
- I want to emphasize that I receive updates from the Tunisia Ubuntu
- server.
- 
- ProblemType: Bug
- DistroRelease: Ubuntu 22.04
- Package: pulseaudio 1:15.99.1+dfsg1-1ubuntu2.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
- AudioDevicesInUse:
-  USERPID ACCESS COMMAND
-  /dev/snd/controlC0:  galxy-a10   1404 F pulseaudio
- CasperMD5CheckResult: pass
- CurrentDesktop: ubuntu:GNOME
- Date: Wed Jan 17 14:56:16 2024
- InstallationDate: Installed on 2024-01-16 (1 days ago)
- InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.2)
- PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
- SourcePackage: pulseaudio
- UpgradeStatus: No upgrade log present (probably fresh install)
- dmi.bios.date: 10/03/2023
- dmi.bios.release: 1.27
- dmi.bios.vendor: Dell Inc.
- dmi.bios.version: 1.27.1
- dmi.board.name: 0GGCMJ
- dmi.board.vendor: Dell Inc.
- dmi.board.version: A02
- dmi.chassis.type: 10
- dmi.chassis.vendor: Dell Inc.
- dmi.modalias: 
dmi:bvnDellInc.:bvr1.27.1:bd10/03/2023:br1.27:svnDellInc.:pnVostro3400:pvr:rvnDellInc.:rn0GGCMJ:rvrA02:cvnDellInc.:ct10:cvr:sku0A23:
- dmi.product.family: Vostro
- dmi.product.name: Vostro 3400
- dmi.product.sku: 0A23
- dmi.sys.vendor: Dell Inc.
+ https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2051570

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

Title:
  Persistent Audio Issues on Dell Vostro 3400 Running Ubuntu 22.04.3 LTS

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2051570

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


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

[Desktop-packages] [Bug 2054856] [NEW] Icon theme is reset on dark/light theme switch

[Junior Martins]

Public bug reported:

### Affected version
GNOME Shell 45.2 on Ubuntu 23.10 (Wayland)

### Bug summary

When you switch between dark and light mode the icon theme is reset.
This also affects other theming options, such as the "Legacy
applications" theme option in Gnome Tweaks. I suspect that it also
affects the primary color settings, since I remember having it changed
to the default orange after switching from light to dark some days ago,
but I don't remember what setting I changed before this.

### Steps to reproduce

1. On Gnome Tweaks > Appearance, change the icon theme (I used Papyrus dark)
2. On the quick toggles, switch between dark and light mode
3. Switch again between dark and light mode

### What happened

The icon theme is changed to "Yaru-blue" and then to "Yaru-blue-dark"

### What did you expect to happen

No change to my icon theme, or at least use its light variant.

### Relevant info

Some `gsettings` options:

```bash
# After changing the icon theme
org.gnome.desktop.interface color-scheme 'prefer-dark'
org.gnome.desktop.interface gtk-theme 'Yaru-blue-dark'
org.gnome.desktop.interface icon-theme 'Papirus-Dark'

# After switching to light mode
org.gnome.desktop.interface color-scheme 'default'
org.gnome.desktop.interface gtk-theme 'Yaru-blue'
org.gnome.desktop.interface icon-theme 'Yaru-blue'

# After switching to dark mode again
org.gnome.desktop.interface color-scheme 'prefer-dark'
org.gnome.desktop.interface gtk-theme 'Yaru-blue-dark'
org.gnome.desktop.interface icon-theme 'Yaru-blue-dark'
```

ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: gnome-shell 45.2-0ubuntu1
ProcVersionSignature: Ubuntu 6.5.0-21.21-generic 6.5.8
Uname: Linux 6.5.0-21-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Fri Feb 23 21:57:38 2024
DisplayManager: gdm3
InstallationDate: Installed on 2023-07-25 (213 days ago)
InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418)
RelatedPackageVersions: mutter-common 45.2-0ubuntu3
SourcePackage: gnome-shell
UpgradeStatus: Upgraded to mantic on 2023-10-29 (117 days ago)

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


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

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

Title:
  Icon theme is reset on dark/light theme switch

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  ### Affected version
  GNOME Shell 45.2 on Ubuntu 23.10 (Wayland)

  ### Bug summary

  When you switch between dark and light mode the icon theme is reset.
  This also affects other theming options, such as the "Legacy
  applications" theme option in Gnome Tweaks. I suspect that it also
  affects the primary color settings, since I remember having it changed
  to the default orange after switching from light to dark some days
  ago, but I don't remember what setting I changed before this.

  ### Steps to reproduce

  1. On Gnome Tweaks > Appearance, change the icon theme (I used Papyrus dark)
  2. On the quick toggles, switch between dark and light mode
  3. Switch again between dark and light mode

  ### What happened

  The icon theme is changed to "Yaru-blue" and then to "Yaru-blue-dark"

  ### What did you expect to happen

  No change to my icon theme, or at least use its light variant.

  ### Relevant info

  Some `gsettings` options:

  ```bash
  # After changing the icon theme
  org.gnome.desktop.interface color-scheme 'prefer-dark'
  org.gnome.desktop.interface gtk-theme 'Yaru-blue-dark'
  org.gnome.desktop.interface icon-theme 'Papirus-Dark'

  # After switching to light mode
  org.gnome.desktop.interface color-scheme 'default'
  org.gnome.desktop.interface gtk-theme 'Yaru-blue'
  org.gnome.desktop.interface icon-theme 'Yaru-blue'

  # After switching to dark mode again
  org.gnome.desktop.interface color-scheme 'prefer-dark'
  org.gnome.desktop.interface gtk-theme 'Yaru-blue-dark'
  org.gnome.desktop.interface icon-theme 'Yaru-blue-dark'
  ```

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: gnome-shell 45.2-0ubuntu1
  ProcVersionSignature: Ubuntu 6.5.0-21.21-generic 6.5.8
  Uname: Linux 6.5.0-21-generic x86_64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Feb 23 21:57:38 2024
  DisplayManager: gdm3
  InstallationDate: Installed on 2023-07-25 (213 days ago)
  InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418)
  RelatedPackageVersions: mutter-common 45.2-0ubuntu3
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to mantic on 2023-10-29 (117 days ago)

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


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to 

[Desktop-packages] [Bug 2041732] Re: Touchpad is extra-sensitive on Wayland

[Connor Nolan]

I was finally able to find another bug report for this issue:
https://bugzilla.redhat.com/show_bug.cgi?id=2014222

It seems this applies to mice in addition to touchpads.

** Bug watch added: Red Hat Bugzilla #2014222
   https://bugzilla.redhat.com/show_bug.cgi?id=2014222

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

Title:
  Touchpad is extra-sensitive on Wayland

Status in libinput package in Ubuntu:
  New
Status in mutter package in Ubuntu:
  New

Bug description:
  Whenever I use Wayland, the touchpad is *much* more sensitive than on
  X11. I'm using the default settings for everything (sensitivity,
  acceleration profile, etc) and both X11 and Wayland are using
  libinput.

  Both normal mouse movement and two-finger scrolling are more
  sensitive.

  Here's the entry in libinput list-deviecs for my touchpad:

  Device:   ELAN06FA:00 04F3:3293 Touchpad
  Kernel:   /dev/input/event9
  Group:6
  Seat: seat0, default
  Size: 134x78mm
  Capabilities: pointer gesture
  Tap-to-click: disabled
  Tap-and-drag: enabled
  Tap drag lock:disabled
  Left-handed:  disabled
  Nat.scrolling:disabled
  Middle emulation: disabled
  Calibration:  n/a
  Scroll methods:   *two-finger edge 
  Click methods:*button-areas clickfinger 
  Disable-w-typing: enabled
  Disable-w-trackpointing: enabled
  Accel profiles:   flat *adaptive custom
  Rotation: n/a

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: libinput10 1.23.0-2
  ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
  Uname: Linux 6.5.0-9-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
  .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
  .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  535.113.01  Tue Sep 12 
19:41:24 UTC 2023
   GCC version:
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Oct 28 16:54:16 2023
  DistUpgraded: 2023-09-23 14:28:46,526 INFO cache.commit()
  DistroCodename: mantic
  DistroVariant: ubuntu
  DkmsStatus:
   acpi-call/1.2.2, 6.5.0-10-generic, x86_64: installed
   acpi-call/1.2.2, 6.5.0-9-generic, x86_64: installed
   nvidia/535.113.01, 6.5.0-10-generic, x86_64: installed
   nvidia/535.113.01, 6.5.0-9-generic, x86_64: installed (WARNING! Diff between 
built and installed module!) (WARNING! Diff between built and installed 
module!) (WARNING! Diff between built and installed module!) (WARNING! Diff 
between built and installed module!) (WARNING! Diff between built and installed 
module!)
  GraphicsCard:
   Intel Corporation Raptor Lake-P [Iris Xe Graphics] [8086:a7a0] (rev 04) 
(prog-if 00 [VGA controller])
 Subsystem: Lenovo Raptor Lake-P [Iris Xe Graphics] [17aa:3e53]
   NVIDIA Corporation AD107M [GeForce RTX 4050 Max-Q / Mobile] [10de:28e1] (rev 
a1) (prog-if 00 [VGA controller])
 Subsystem: Lenovo GN21-X2 [17aa:3e53]
  InstallationDate: Installed on 2023-08-02 (88 days ago)
  InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418)
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-9-generic 
root=UUID=ab9aefbd-ccde-4fe6-ae0c-5802f04e9528 ro quiet splash
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: libinput
  UpgradeStatus: Upgraded to mantic on 2023-09-23 (35 days ago)
  XorgLogOld:
   
  dmi.bios.date: 07/25/2023
  dmi.bios.release: 1.26
  dmi.bios.vendor: LENOVO
  dmi.bios.version: MBCN26WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0T76461 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Slim Pro 9 14IRP8
  dmi.ec.firmware.release: 1.26
  dmi.modalias: 
dmi:bvnLENOVO:bvrMBCN26WW:bd07/25/2023:br1.26:efr1.26:svnLENOVO:pn83BV:pvrLenovoSlimPro914IRP8:rvnLENOVO:rnLNVNB161216:rvrSDK0T76461WIN:cvnLENOVO:ct10:cvrLenovoSlimPro914IRP8:skuLENOVO_MT_83BV_BU_idea_FM_SlimPro914IRP8:
  dmi.product.family: Slim Pro 9 14IRP8
  dmi.product.name: 83BV
  dmi.product.sku: LENOVO_MT_83BV_BU_idea_FM_Slim Pro 9 14IRP8
  dmi.product.version: Lenovo Slim Pro 9 14IRP8
  dmi.sys.vendor: LENOVO
  

Re: [Desktop-packages] [Bug 1833322] Re: Consider removing irqbalance from default install on desktop images

[Steve Langasek]

Belated response, but just for the record, Paride's recounting of upstream's
position in the context of the Debian decision was definitive for me:

On Wed, Jan 10, 2024 at 11:47:56AM -, Paride Legovini wrote:
> Back in the day I asked upstream their take on irqbalance usefulness
> with newer kernels, here is their reply:

In effect what this says is that: irqbalance is still useful, but unless
the admin configures it, the policy it provides is not a discernable
improvement over the in-kernel default policy.

Therefore I think it is the right path forward to unseed this and let users
install it in situations where they want to configure it.

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

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

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

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

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

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

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

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

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

  Issue/Bug Description:

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

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

  Steps to reproduce (if you know):

  This is potentially an issue with all default installs.

  Expected behavior:

  n/a

  Other Notes:

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

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


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

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

[popov895]

> The Workaround from #71 does not seem to work for me.

Try increasing the delay in the extension settings (available through
the Extensions app).

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

Title:
  Dock displaying over window after resuming from blank screen

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

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

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

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

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

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

  -

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

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

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

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

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


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

[Desktop-packages] [Bug 2051765] Re: Plymouth FTBFS (even after apt-get build-dep plymouth)

[Nick Rosbrook]

The systemd version in question migrated.

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

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

Title:
  Plymouth FTBFS (even after apt-get build-dep plymouth)

Status in plymouth package in Ubuntu:
  Won't Fix
Status in systemd package in Ubuntu:
  Fix Released

Bug description:
  dh_install
  dh_install: warning: Cannot find (any matches for) "lib/systemd/system" 
(tried in ., debian/tmp)

  dh_install: warning: plymouth missing files: lib/systemd/system
  dh_install: error: missing files, aborting

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


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

[Desktop-packages] [Bug 1162475] Re: [hostnamed] Changing hostname doesn't update /etc/hosts

[Nick Rosbrook]

** Changed in: systemd (Ubuntu)
   Status: Triaged => Won't Fix

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

Title:
  [hostnamed] Changing hostname doesn't update /etc/hosts

Status in gnome-control-center package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Won't Fix
Status in unity-control-center package in Ubuntu:
  Won't Fix
Status in gnome-control-center source package in Xenial:
  Confirmed
Status in systemd source package in Xenial:
  Triaged
Status in unity-control-center source package in Xenial:
  Confirmed
Status in gnome-control-center package in Debian:
  Fix Released

Bug description:
  GUI
  ---
  1a. Run sudo gnome-control-center, or...
  1b. Save the gnome-control-center.pkla from 
https://bazaar.launchpad.net/~ubuntu-desktop/gnome-control-center/ubuntu/revision/556
 to /var/lib/polkit-1/localauthority/10-vendor.d/ and then run 
gnome-control-center as an admin user

  2. Enter the Details panel
  3. The "Device name" (hostname) text field should be editable; change the 
text to something else.
  4. The hostname is updated instantly which can be verified by looking in 
/etc/hostname. However /etc/hosts/ is not updated.

  Command line
  
  hostnamectl set-hostname

  The hostnamed documentation at 
http://www.freedesktop.org/wiki/Software/systemd/hostnamed says
  "To properly handle name lookups with changing local hostnames without having 
to edit /etc/hosts for them we recommend using hostnamed in combination with 
nss-myhostname: http://0pointer.de/lennart/projects/nss-myhostname/ "

  Without /etc/hosts being handled correctly, the hostnamed integration
  is only half-working.


  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: gnome-control-center 1:3.6.3-0ubuntu18
  ProcVersionSignature: Ubuntu 3.8.0-15.25-generic 3.8.4
  Uname: Linux 3.8.0-15-generic x86_64
  ApportVersion: 2.9.2-0ubuntu5
  Architecture: amd64
  Date: Sun Mar 31 08:52:57 2013
  MarkForUpload: True
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_gnome-control-center:
   activity-log-manager-control-center 0.9.4-0ubuntu6.1
   deja-dup26.0-0ubuntu1
   gnome-control-center-signon 0.1.5-0ubuntu1
   gnome-control-center-unity  1.2daily13.02.15-0ubuntu1
   indicator-datetime  12.10.3daily13.03.26-0ubuntu1

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


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

[Desktop-packages] [Bug 827695]

[Rgb-mldc]

*** Bug 40998 has been marked as a duplicate of this bug. ***

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

Title:
  [Upstream] bug in displaying scalable square brackets in math object

Status in LibreOffice:
  Confirmed
Status in OpenOffice:
  Confirmed
Status in libreoffice package in Ubuntu:
  Confirmed
Status in openoffice.org package in Ubuntu:
  Won't Fix

Bug description:
  1) lsb_release -rd
  Description:  Ubuntu 11.04
  Release:  11.04

  2) apt-cache policy libreoffice-writer
  libreoffice-writer:
    Installed: 1:3.3.3-1ubuntu2
    Candidate: 1:3.3.3-1ubuntu2
    Version table:
   *** 1:3.3.3-1ubuntu2 0
  100 /var/lib/dpkg/status
   1:3.3.2-1ubuntu5 0
  500 http://us.archive.ubuntu.com/ubuntu/ natty-updates/main i386 
Packages
   1:3.3.2-1ubuntu4 0
  500 http://us.archive.ubuntu.com/ubuntu/ natty/main i386 Packages

  3) When is expected to happen in LibreOffice Writer via a terminal:
  cd ~/Desktop && wget 
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/827695/+attachment/2284273/+files/bracket_example.odt
 && lowriter --nologo bracket_example.odt

  is the scalable square brackets look as they would in Word. Latex also
  shows the desired bracket shape as per
  
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/827695/+attachment/2287347/+files/latex_brackets.pdf
  .

  4) What happens instead is the top and bottom part of the bracket look
  like a square instead of a line pointing inwards towards the equation.

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/827695/+subscriptions


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

[Desktop-packages] [Bug 1990173] Re: [kinetic] gnome-initial-setup shows minimize button

[Launchpad Bug Tracker]

This bug was fixed in the package gnome-initial-setup - 46~beta-1ubuntu1

---
gnome-initial-setup (46~beta-1ubuntu1) noble; urgency=medium

  * Merge with Debian. Remaining changes:
+ debian/control:
  - Add Build-Depends: libsnapd-glib-dev and libsysmetrics-dev
+ Add Ubuntu-specific patches:
  - 0001-Make-summary-page-explicitly-request-navigation-butt.patch
  - 0001-Ensure-stamp-file-if-the-user-quit-the-wizard.patch
  - 0001-Add-Ubuntu-mode-with-special-pages.patch
  - 0001-Display-the-ubuntu-welcome-wizard-in-Unity.patch
  - 0008-Ubuntu-location-default.patch
  - ubuntu-distributor-logo.patch
  * Update patches

gnome-initial-setup (46~beta-1) unstable; urgency=medium

  * New upstream release
- Minimize button correctly hidden (LP: #1990173)
  * Drop patch applied in new release

 -- Jeremy Bícha   Mon, 12 Feb 2024 14:28:07 -0500

** Changed in: gnome-initial-setup (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  [kinetic] gnome-initial-setup shows minimize button

Status in gnome-initial-setup package in Ubuntu:
  Fix Released

Bug description:
  In Ubuntu 22.10, gnome-initial-setup shows a minimize window button.
  It didn't show this button in Ubuntu 22.04 LTS.

  gnome-initial-setup was ported to GTK4 this cycle so this may be a
  regression.

  Test Case
  -
  Run

  /usr/libexec/gnome-initial-setup --existing-user

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


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

[Desktop-packages] [Bug 2054109] Re: nautilus fails to build on armhf

[Launchpad Bug Tracker]

This bug was fixed in the package nautilus - 1:46~beta-0ubuntu3

---
nautilus (1:46~beta-0ubuntu3) noble; urgency=medium

  * Add another patch to fix 32-bit build (LP: #2054109)

 -- Jeremy Bícha   Fri, 23 Feb 2024 08:57:34 -0500

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

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

Title:
  nautilus fails to build on armhf

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

Bug description:
  Nautilus 46 fails to build on armhf because of a test failure.
  However, the test failure might be revealing a bug in nautilus's
  functions that would affect 32-bit architectures. I have filed the
  issue with the Nautilus developers.

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


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

[Desktop-packages] [Bug 2041732] Re: Touchpad is extra-sensitive on Wayland

[Connor Nolan]

Yup, I just tested with 300% scaling and the bug is even worse. I think
something's being multiplied by the scaling factor on Wayland that
shouldn't be.

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

Title:
  Touchpad is extra-sensitive on Wayland

Status in libinput package in Ubuntu:
  New
Status in mutter package in Ubuntu:
  New

Bug description:
  Whenever I use Wayland, the touchpad is *much* more sensitive than on
  X11. I'm using the default settings for everything (sensitivity,
  acceleration profile, etc) and both X11 and Wayland are using
  libinput.

  Both normal mouse movement and two-finger scrolling are more
  sensitive.

  Here's the entry in libinput list-deviecs for my touchpad:

  Device:   ELAN06FA:00 04F3:3293 Touchpad
  Kernel:   /dev/input/event9
  Group:6
  Seat: seat0, default
  Size: 134x78mm
  Capabilities: pointer gesture
  Tap-to-click: disabled
  Tap-and-drag: enabled
  Tap drag lock:disabled
  Left-handed:  disabled
  Nat.scrolling:disabled
  Middle emulation: disabled
  Calibration:  n/a
  Scroll methods:   *two-finger edge 
  Click methods:*button-areas clickfinger 
  Disable-w-typing: enabled
  Disable-w-trackpointing: enabled
  Accel profiles:   flat *adaptive custom
  Rotation: n/a

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: libinput10 1.23.0-2
  ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
  Uname: Linux 6.5.0-9-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
  .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
  .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  535.113.01  Tue Sep 12 
19:41:24 UTC 2023
   GCC version:
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Oct 28 16:54:16 2023
  DistUpgraded: 2023-09-23 14:28:46,526 INFO cache.commit()
  DistroCodename: mantic
  DistroVariant: ubuntu
  DkmsStatus:
   acpi-call/1.2.2, 6.5.0-10-generic, x86_64: installed
   acpi-call/1.2.2, 6.5.0-9-generic, x86_64: installed
   nvidia/535.113.01, 6.5.0-10-generic, x86_64: installed
   nvidia/535.113.01, 6.5.0-9-generic, x86_64: installed (WARNING! Diff between 
built and installed module!) (WARNING! Diff between built and installed 
module!) (WARNING! Diff between built and installed module!) (WARNING! Diff 
between built and installed module!) (WARNING! Diff between built and installed 
module!)
  GraphicsCard:
   Intel Corporation Raptor Lake-P [Iris Xe Graphics] [8086:a7a0] (rev 04) 
(prog-if 00 [VGA controller])
 Subsystem: Lenovo Raptor Lake-P [Iris Xe Graphics] [17aa:3e53]
   NVIDIA Corporation AD107M [GeForce RTX 4050 Max-Q / Mobile] [10de:28e1] (rev 
a1) (prog-if 00 [VGA controller])
 Subsystem: Lenovo GN21-X2 [17aa:3e53]
  InstallationDate: Installed on 2023-08-02 (88 days ago)
  InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418)
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-9-generic 
root=UUID=ab9aefbd-ccde-4fe6-ae0c-5802f04e9528 ro quiet splash
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: libinput
  UpgradeStatus: Upgraded to mantic on 2023-09-23 (35 days ago)
  XorgLogOld:
   
  dmi.bios.date: 07/25/2023
  dmi.bios.release: 1.26
  dmi.bios.vendor: LENOVO
  dmi.bios.version: MBCN26WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0T76461 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Slim Pro 9 14IRP8
  dmi.ec.firmware.release: 1.26
  dmi.modalias: 
dmi:bvnLENOVO:bvrMBCN26WW:bd07/25/2023:br1.26:efr1.26:svnLENOVO:pn83BV:pvrLenovoSlimPro914IRP8:rvnLENOVO:rnLNVNB161216:rvrSDK0T76461WIN:cvnLENOVO:ct10:cvrLenovoSlimPro914IRP8:skuLENOVO_MT_83BV_BU_idea_FM_SlimPro914IRP8:
  dmi.product.family: Slim Pro 9 14IRP8
  dmi.product.name: 83BV
  dmi.product.sku: LENOVO_MT_83BV_BU_idea_FM_Slim Pro 9 14IRP8
  dmi.product.version: Lenovo Slim Pro 9 14IRP8
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.115-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3
  

[Desktop-packages] [Bug 2041732] Re: Touchpad is extra-sensitive on Wayland

[Connor Nolan]

Hmm, this might be scaling related. I set my laptop to 100% scaling
(instead of 200%) and the bug seemed to disappear.

Unfortunately, using 100% scaling on a HiDPI laptop is not a practical
solution.

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

Title:
  Touchpad is extra-sensitive on Wayland

Status in libinput package in Ubuntu:
  New
Status in mutter package in Ubuntu:
  New

Bug description:
  Whenever I use Wayland, the touchpad is *much* more sensitive than on
  X11. I'm using the default settings for everything (sensitivity,
  acceleration profile, etc) and both X11 and Wayland are using
  libinput.

  Both normal mouse movement and two-finger scrolling are more
  sensitive.

  Here's the entry in libinput list-deviecs for my touchpad:

  Device:   ELAN06FA:00 04F3:3293 Touchpad
  Kernel:   /dev/input/event9
  Group:6
  Seat: seat0, default
  Size: 134x78mm
  Capabilities: pointer gesture
  Tap-to-click: disabled
  Tap-and-drag: enabled
  Tap drag lock:disabled
  Left-handed:  disabled
  Nat.scrolling:disabled
  Middle emulation: disabled
  Calibration:  n/a
  Scroll methods:   *two-finger edge 
  Click methods:*button-areas clickfinger 
  Disable-w-typing: enabled
  Disable-w-trackpointing: enabled
  Accel profiles:   flat *adaptive custom
  Rotation: n/a

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: libinput10 1.23.0-2
  ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
  Uname: Linux 6.5.0-9-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
  .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
  .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  535.113.01  Tue Sep 12 
19:41:24 UTC 2023
   GCC version:
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Oct 28 16:54:16 2023
  DistUpgraded: 2023-09-23 14:28:46,526 INFO cache.commit()
  DistroCodename: mantic
  DistroVariant: ubuntu
  DkmsStatus:
   acpi-call/1.2.2, 6.5.0-10-generic, x86_64: installed
   acpi-call/1.2.2, 6.5.0-9-generic, x86_64: installed
   nvidia/535.113.01, 6.5.0-10-generic, x86_64: installed
   nvidia/535.113.01, 6.5.0-9-generic, x86_64: installed (WARNING! Diff between 
built and installed module!) (WARNING! Diff between built and installed 
module!) (WARNING! Diff between built and installed module!) (WARNING! Diff 
between built and installed module!) (WARNING! Diff between built and installed 
module!)
  GraphicsCard:
   Intel Corporation Raptor Lake-P [Iris Xe Graphics] [8086:a7a0] (rev 04) 
(prog-if 00 [VGA controller])
 Subsystem: Lenovo Raptor Lake-P [Iris Xe Graphics] [17aa:3e53]
   NVIDIA Corporation AD107M [GeForce RTX 4050 Max-Q / Mobile] [10de:28e1] (rev 
a1) (prog-if 00 [VGA controller])
 Subsystem: Lenovo GN21-X2 [17aa:3e53]
  InstallationDate: Installed on 2023-08-02 (88 days ago)
  InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418)
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-9-generic 
root=UUID=ab9aefbd-ccde-4fe6-ae0c-5802f04e9528 ro quiet splash
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: libinput
  UpgradeStatus: Upgraded to mantic on 2023-09-23 (35 days ago)
  XorgLogOld:
   
  dmi.bios.date: 07/25/2023
  dmi.bios.release: 1.26
  dmi.bios.vendor: LENOVO
  dmi.bios.version: MBCN26WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0T76461 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Slim Pro 9 14IRP8
  dmi.ec.firmware.release: 1.26
  dmi.modalias: 
dmi:bvnLENOVO:bvrMBCN26WW:bd07/25/2023:br1.26:efr1.26:svnLENOVO:pn83BV:pvrLenovoSlimPro914IRP8:rvnLENOVO:rnLNVNB161216:rvrSDK0T76461WIN:cvnLENOVO:ct10:cvrLenovoSlimPro914IRP8:skuLENOVO_MT_83BV_BU_idea_FM_SlimPro914IRP8:
  dmi.product.family: Slim Pro 9 14IRP8
  dmi.product.name: 83BV
  dmi.product.sku: LENOVO_MT_83BV_BU_idea_FM_Slim Pro 9 14IRP8
  dmi.product.version: Lenovo Slim Pro 9 14IRP8
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.115-1
  

[Desktop-packages] [Bug 2041732] Re: Touchpad is extra-sensitive on Wayland

[Connor Nolan]

I just loaded up the latest Ubuntu 24.04 daily build on a USB, and I can
reproduce the bug on it as well.

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

Title:
  Touchpad is extra-sensitive on Wayland

Status in libinput package in Ubuntu:
  New
Status in mutter package in Ubuntu:
  New

Bug description:
  Whenever I use Wayland, the touchpad is *much* more sensitive than on
  X11. I'm using the default settings for everything (sensitivity,
  acceleration profile, etc) and both X11 and Wayland are using
  libinput.

  Both normal mouse movement and two-finger scrolling are more
  sensitive.

  Here's the entry in libinput list-deviecs for my touchpad:

  Device:   ELAN06FA:00 04F3:3293 Touchpad
  Kernel:   /dev/input/event9
  Group:6
  Seat: seat0, default
  Size: 134x78mm
  Capabilities: pointer gesture
  Tap-to-click: disabled
  Tap-and-drag: enabled
  Tap drag lock:disabled
  Left-handed:  disabled
  Nat.scrolling:disabled
  Middle emulation: disabled
  Calibration:  n/a
  Scroll methods:   *two-finger edge 
  Click methods:*button-areas clickfinger 
  Disable-w-typing: enabled
  Disable-w-trackpointing: enabled
  Accel profiles:   flat *adaptive custom
  Rotation: n/a

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: libinput10 1.23.0-2
  ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
  Uname: Linux 6.5.0-9-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
  .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
  .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  535.113.01  Tue Sep 12 
19:41:24 UTC 2023
   GCC version:
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Oct 28 16:54:16 2023
  DistUpgraded: 2023-09-23 14:28:46,526 INFO cache.commit()
  DistroCodename: mantic
  DistroVariant: ubuntu
  DkmsStatus:
   acpi-call/1.2.2, 6.5.0-10-generic, x86_64: installed
   acpi-call/1.2.2, 6.5.0-9-generic, x86_64: installed
   nvidia/535.113.01, 6.5.0-10-generic, x86_64: installed
   nvidia/535.113.01, 6.5.0-9-generic, x86_64: installed (WARNING! Diff between 
built and installed module!) (WARNING! Diff between built and installed 
module!) (WARNING! Diff between built and installed module!) (WARNING! Diff 
between built and installed module!) (WARNING! Diff between built and installed 
module!)
  GraphicsCard:
   Intel Corporation Raptor Lake-P [Iris Xe Graphics] [8086:a7a0] (rev 04) 
(prog-if 00 [VGA controller])
 Subsystem: Lenovo Raptor Lake-P [Iris Xe Graphics] [17aa:3e53]
   NVIDIA Corporation AD107M [GeForce RTX 4050 Max-Q / Mobile] [10de:28e1] (rev 
a1) (prog-if 00 [VGA controller])
 Subsystem: Lenovo GN21-X2 [17aa:3e53]
  InstallationDate: Installed on 2023-08-02 (88 days ago)
  InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418)
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-9-generic 
root=UUID=ab9aefbd-ccde-4fe6-ae0c-5802f04e9528 ro quiet splash
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: libinput
  UpgradeStatus: Upgraded to mantic on 2023-09-23 (35 days ago)
  XorgLogOld:
   
  dmi.bios.date: 07/25/2023
  dmi.bios.release: 1.26
  dmi.bios.vendor: LENOVO
  dmi.bios.version: MBCN26WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0T76461 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Slim Pro 9 14IRP8
  dmi.ec.firmware.release: 1.26
  dmi.modalias: 
dmi:bvnLENOVO:bvrMBCN26WW:bd07/25/2023:br1.26:efr1.26:svnLENOVO:pn83BV:pvrLenovoSlimPro914IRP8:rvnLENOVO:rnLNVNB161216:rvrSDK0T76461WIN:cvnLENOVO:ct10:cvrLenovoSlimPro914IRP8:skuLENOVO_MT_83BV_BU_idea_FM_SlimPro914IRP8:
  dmi.product.family: Slim Pro 9 14IRP8
  dmi.product.name: 83BV
  dmi.product.sku: LENOVO_MT_83BV_BU_idea_FM_Slim Pro 9 14IRP8
  dmi.product.version: Lenovo Slim Pro 9 14IRP8
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.115-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3
  version.libgl1-mesa-glx: libgl1-mesa-glx 

[Desktop-packages] [Bug 882255] Re: No administrative actions possible (password refused) after enabling passwordless login

[ravi mano]

Stragely though, when I reboot my ubuntu and mosue-click some times out of my 
ubuntu and inside my VmWare player randomly some times, it allowed me in. and 
also on reboot, it works with an Enter
( i.e  removing password effected ).

Also i tried to change password with passwd command giving the same
string I had used earlier, as new password. Strangely, this fails saying
"please enter a longer password". Then why was I allowed to be using a
"shorter" password all these days ?

My config:
--
anon@ubuntu:~$ 
anon@ubuntu:~$ uname -as
Linux ubuntu 4.15.0-142-generic #146~16.04.1-Ubuntu SMP Tue Apr 13 09:27:15 UTC 
2021 x86_64 x86_64 x86_64 GNU/Linux
anon@ubuntu:~$ 
anon@ubuntu:~$ 

anon@ubuntu:~$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 16.04.7 LTS
Release:16.04
Codename:   xenial
anon@ubuntu:~$


VmWare player version: ( not related though )
VMware® Workstation 16 Pro
16.1.2 build-17966106

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

Title:
  No administrative actions possible (password refused) after enabling
  passwordless login

Status in accountsservice package in Ubuntu:
  Triaged
Status in gnome-control-center package in Ubuntu:
  Triaged
Status in gnome-system-tools package in Ubuntu:
  Invalid
Status in lightdm package in Ubuntu:
  Triaged

Bug description:
  If I choose not to have a password for my operating account, every
  operation fails if it needs root access. Reproducible even on a newly
  set up machine. See: http://ubuntuforums.org/showthread.php?t=1862543

  Release: 11.10

  Cause: The password is cleared to be empty, and this prevents
  authentification for many admin tasks for security reasons. However,
  the user only needs to be added to the "nopasswdlogin" group, to
  enable passwordless login with gdm (and any other DM that ships with a
  corresponding "auth sufficient pam_succeed_if.so user ingroup
  nopasswdlogin" configuration).

  Fix:
   * lightdm to add pam rule
   * account managing tools not clearing password but only adding user to
 "nopasswdlogin" group

  
  Steps to reproduce:
  1. Install Ubuntu 11.10 as normal. During installation, when you are asked to 
choose a password, enter one, since the installation can not continue if you do 
not do so.
  2. Boot the newly installed system and log in as usual.
  3. Choose "System Settings" from the launcher on the left and open "User 
Accounts".
  4. In the User Accounts window, click on Unlock at the top right of the 
dialog. Enter your user password when prompted.
  5. Click on the four dots next to the "Password" label to change your 
password.
  6. Select "Log in without a password" from the dropdown box. Close the window.
  7. Try to perform an action requiring administrative privileges. For example, 
try running "sudo apt-get update" from a terminal.

  Expected behavior:
  sudo should require the user's password and accept it, or proceed without 
requiring any password altogether.

  Actual behavior:
  sudo requires the user's password and does not accept it (since it is set to 
an empty string in /etc/shadow).

  Further notes:
  After disabling the password request at login, the /etc/shadow file related 
to the test user account I created looked like this:
  test::15283:0:9:7:::
  This shows that the password hash is made completely empty; that conflicts 
with the policies listed in /etc/sudoers, which require a password to be given 
in order to perform
  administrative actions.

  Workaround:
  -If you can not perform administrative actions but can still login without a 
password, open a terminal and type "passwd". This command should prompt you for 
a new password and change it without any problems.
  -If you can not login, you can reset your password by booting into recovery 
mode and changing it there. Follow the instructions at 
.

  You may also choose to use a password for your account and to enable
  autologin at the same time. This choice will enable you to benefit the
  advantage of not entering a password at boot time with the security of
  Ubuntu requiring your password when attempting to perform privileged
  actions. Of course, this helps when you are the only desktop user or
  the primary one.

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


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

[Desktop-packages] [Bug 2054827] Re: [regression] GUI crashed after installed proposed package after mesa updates

[drouineau]

and here is the syslog

** Attachment added: "syslog"
   
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2054827/+attachment/5748736/+files/syslog

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

Title:
  [regression] GUI crashed after installed proposed package after mesa
  updates

Status in mesa package in Ubuntu:
  New

Bug description:
  Dear all, after the upgrade of various mesa packages on monday 
(23.2.1-1ubuntu3.1~22.04.2 from repo jammy-updates), I suffer similar symptoms 
at startup (causing a blank screen with no GDM running and message "something 
went wrong) than those reported there 
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2051068. 
  I am using 22.04.3 LTS "Jammy Jellyfish" with kernel 6.1.0-1034-oem but the 
issue remains with kernel 6.2.0-26-generic). I have a Dell precision 5480. The 
issue occurs if I use either the nouveau driver or the proprietary nvidia 
driver (535 from ubuntu repo) with profile "on-demand". The problem is solved 
with proprietary driver and profile "nvidia" (but costs a lot to the battery 
lifetime).
  I enclose the syslog before the crash which mentions an issue with mesa 
drivers.
  I will enclose also the apt log describing the operations that have cause the 
bug

  I suspect that this bug is related to this one
  https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2051068


  
  Description:  Ubuntu 22.04.4 LTS
  Release:  22.04


  
  libegl-mesa0:
Installé : 23.2.1-1ubuntu3.1~22.04.2
Candidat : 23.2.1-1ubuntu3.1~22.04.2
   Table de version :
   *** 23.2.1-1ubuntu3.1~22.04.2 500
  500 http://fr.archive.ubuntu.com/ubuntu jammy-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   22.0.1-1ubuntu2 500
  500 http://fr.archive.ubuntu.com/ubuntu jammy/main amd64 Packages


  
  libgl1-mesa-dri:
Installé : 23.2.1-1ubuntu3.1~22.04.2
Candidat : 23.2.1-1ubuntu3.1~22.04.2
   Table de version :
   *** 23.2.1-1ubuntu3.1~22.04.2 500
  500 http://fr.archive.ubuntu.com/ubuntu jammy-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   22.0.1-1ubuntu2 500
  500 http://fr.archive.ubuntu.com/ubuntu jammy/main amd64 Packages


  [Summary]
  After upgrade of packages last monday, reboot system when using nouveau 
driver, nvidia-driver with on-demand profile, with kernel 6.1oem, 6.2 generic. 
It works if using nvidia-driver with profile nvidia.


  [Steps to reproduce]
  1. Boot into OS
  2. sudo apt update
  3. sudo apt upgrade
  4. After upgrade process finished, reboot system.
  5. GUI crashed.

  [Expected result]
  GUI displayed normally

  [Actual result]
  GUI crashed

  [Failure rate]
  100%

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: libegl-mesa0 23.2.1-1ubuntu3.1~22.04.2
  ProcVersionSignature: Ubuntu 6.1.0-1034.34-oem 6.1.73
  Uname: Linux 6.1.0-1034-oem x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
  .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
  .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  535.154.05  Thu Dec 28 
15:37:48 UTC 2023
   GCC version:  gcc version 12.3.0 (Ubuntu 12.3.0-1ubuntu1~22.04)
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Feb 23 16:21:34 2024
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia/535.154.05, 6.1.0-1034-oem, x86_64: installed
   nvidia/535.154.05, 6.2.0-26-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Device [8086:a7a0] (rev 04) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:0c40]
 Subsystem: Dell Device [1028:0c40]
  InstallationDate: Installed on 2024-01-12 (42 days ago)
  InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.2)
  MachineType: Dell Inc. Precision 5480
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.1.0-1034-oem 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  SourcePackage: mesa
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/18/2023
  dmi.bios.release: 1.8
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.8.0
  dmi.board.name: 0VCJYY
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.ec.firmware.release: 1.16
  dmi.modalias: 

[Desktop-packages] [Bug 2054827] Re: [regression] GUI crashed after installed proposed package after mesa updates

[drouineau]

here is the apt.log of the upgrade that have raised the issue

** Attachment added: "apt.log"
   
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2054827/+attachment/5748735/+files/apt.log

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

Title:
  [regression] GUI crashed after installed proposed package after mesa
  updates

Status in mesa package in Ubuntu:
  New

Bug description:
  Dear all, after the upgrade of various mesa packages on monday 
(23.2.1-1ubuntu3.1~22.04.2 from repo jammy-updates), I suffer similar symptoms 
at startup (causing a blank screen with no GDM running and message "something 
went wrong) than those reported there 
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2051068. 
  I am using 22.04.3 LTS "Jammy Jellyfish" with kernel 6.1.0-1034-oem but the 
issue remains with kernel 6.2.0-26-generic). I have a Dell precision 5480. The 
issue occurs if I use either the nouveau driver or the proprietary nvidia 
driver (535 from ubuntu repo) with profile "on-demand". The problem is solved 
with proprietary driver and profile "nvidia" (but costs a lot to the battery 
lifetime).
  I enclose the syslog before the crash which mentions an issue with mesa 
drivers.
  I will enclose also the apt log describing the operations that have cause the 
bug

  I suspect that this bug is related to this one
  https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2051068


  
  Description:  Ubuntu 22.04.4 LTS
  Release:  22.04


  
  libegl-mesa0:
Installé : 23.2.1-1ubuntu3.1~22.04.2
Candidat : 23.2.1-1ubuntu3.1~22.04.2
   Table de version :
   *** 23.2.1-1ubuntu3.1~22.04.2 500
  500 http://fr.archive.ubuntu.com/ubuntu jammy-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   22.0.1-1ubuntu2 500
  500 http://fr.archive.ubuntu.com/ubuntu jammy/main amd64 Packages


  
  libgl1-mesa-dri:
Installé : 23.2.1-1ubuntu3.1~22.04.2
Candidat : 23.2.1-1ubuntu3.1~22.04.2
   Table de version :
   *** 23.2.1-1ubuntu3.1~22.04.2 500
  500 http://fr.archive.ubuntu.com/ubuntu jammy-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   22.0.1-1ubuntu2 500
  500 http://fr.archive.ubuntu.com/ubuntu jammy/main amd64 Packages


  [Summary]
  After upgrade of packages last monday, reboot system when using nouveau 
driver, nvidia-driver with on-demand profile, with kernel 6.1oem, 6.2 generic. 
It works if using nvidia-driver with profile nvidia.


  [Steps to reproduce]
  1. Boot into OS
  2. sudo apt update
  3. sudo apt upgrade
  4. After upgrade process finished, reboot system.
  5. GUI crashed.

  [Expected result]
  GUI displayed normally

  [Actual result]
  GUI crashed

  [Failure rate]
  100%

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: libegl-mesa0 23.2.1-1ubuntu3.1~22.04.2
  ProcVersionSignature: Ubuntu 6.1.0-1034.34-oem 6.1.73
  Uname: Linux 6.1.0-1034-oem x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
  .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
  .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  535.154.05  Thu Dec 28 
15:37:48 UTC 2023
   GCC version:  gcc version 12.3.0 (Ubuntu 12.3.0-1ubuntu1~22.04)
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Feb 23 16:21:34 2024
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia/535.154.05, 6.1.0-1034-oem, x86_64: installed
   nvidia/535.154.05, 6.2.0-26-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Device [8086:a7a0] (rev 04) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:0c40]
 Subsystem: Dell Device [1028:0c40]
  InstallationDate: Installed on 2024-01-12 (42 days ago)
  InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.2)
  MachineType: Dell Inc. Precision 5480
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.1.0-1034-oem 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  SourcePackage: mesa
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/18/2023
  dmi.bios.release: 1.8
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.8.0
  dmi.board.name: 0VCJYY
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.ec.firmware.release: 1.16
  

[Desktop-packages] [Bug 2054827] [NEW] [regression] GUI crashed after installed proposed package after mesa updates

[drouineau]

Public bug reported:

Dear all, after the upgrade of various mesa packages on monday 
(23.2.1-1ubuntu3.1~22.04.2 from repo jammy-updates), I suffer similar symptoms 
at startup (causing a blank screen with no GDM running and message "something 
went wrong) than those reported there 
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2051068. 
I am using 22.04.3 LTS "Jammy Jellyfish" with kernel 6.1.0-1034-oem but the 
issue remains with kernel 6.2.0-26-generic). I have a Dell precision 5480. The 
issue occurs if I use either the nouveau driver or the proprietary nvidia 
driver (535 from ubuntu repo) with profile "on-demand". The problem is solved 
with proprietary driver and profile "nvidia" (but costs a lot to the battery 
lifetime).
I enclose the syslog before the crash which mentions an issue with mesa drivers.
I will enclose also the apt log describing the operations that have cause the 
bug

I suspect that this bug is related to this one
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2051068


Description:Ubuntu 22.04.4 LTS
Release:22.04


libegl-mesa0:
  Installé : 23.2.1-1ubuntu3.1~22.04.2
  Candidat : 23.2.1-1ubuntu3.1~22.04.2
 Table de version :
 *** 23.2.1-1ubuntu3.1~22.04.2 500
500 http://fr.archive.ubuntu.com/ubuntu jammy-updates/main amd64 
Packages
100 /var/lib/dpkg/status
 22.0.1-1ubuntu2 500
500 http://fr.archive.ubuntu.com/ubuntu jammy/main amd64 Packages


libgl1-mesa-dri:
  Installé : 23.2.1-1ubuntu3.1~22.04.2
  Candidat : 23.2.1-1ubuntu3.1~22.04.2
 Table de version :
 *** 23.2.1-1ubuntu3.1~22.04.2 500
500 http://fr.archive.ubuntu.com/ubuntu jammy-updates/main amd64 
Packages
100 /var/lib/dpkg/status
 22.0.1-1ubuntu2 500
500 http://fr.archive.ubuntu.com/ubuntu jammy/main amd64 Packages


[Summary]
After upgrade of packages last monday, reboot system when using nouveau driver, 
nvidia-driver with on-demand profile, with kernel 6.1oem, 6.2 generic. It works 
if using nvidia-driver with profile nvidia.


[Steps to reproduce]
1. Boot into OS
2. sudo apt update
3. sudo apt upgrade
4. After upgrade process finished, reboot system.
5. GUI crashed.

[Expected result]
GUI displayed normally

[Actual result]
GUI crashed

[Failure rate]
100%

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: libegl-mesa0 23.2.1-1ubuntu3.1~22.04.2
ProcVersionSignature: Ubuntu 6.1.0-1034.34-oem 6.1.73
Uname: Linux 6.1.0-1034-oem x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
.proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
.proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.suspend: suspend hibernate resume
.proc.driver.nvidia.suspend_depth: default modeset uvm
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  535.154.05  Thu Dec 28 
15:37:48 UTC 2023
 GCC version:  gcc version 12.3.0 (Ubuntu 12.3.0-1ubuntu1~22.04)
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Fri Feb 23 16:21:34 2024
DistUpgraded: Fresh install
DistroCodename: jammy
DistroVariant: ubuntu
DkmsStatus:
 nvidia/535.154.05, 6.1.0-1034-oem, x86_64: installed
 nvidia/535.154.05, 6.2.0-26-generic, x86_64: installed
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation Device [8086:a7a0] (rev 04) (prog-if 00 [VGA controller])
   Subsystem: Dell Device [1028:0c40]
   Subsystem: Dell Device [1028:0c40]
InstallationDate: Installed on 2024-01-12 (42 days ago)
InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.2)
MachineType: Dell Inc. Precision 5480
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.1.0-1034-oem 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
SourcePackage: mesa
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/18/2023
dmi.bios.release: 1.8
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.8.0
dmi.board.name: 0VCJYY
dmi.board.vendor: Dell Inc.
dmi.board.version: A01
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.ec.firmware.release: 1.16
dmi.modalias: 
dmi:bvnDellInc.:bvr1.8.0:bd12/18/2023:br1.8:efr1.16:svnDellInc.:pnPrecision5480:pvr:rvnDellInc.:rn0VCJYY:rvrA01:cvnDellInc.:ct10:cvr:sku0C40:
dmi.product.family: Precision
dmi.product.name: Precision 5480
dmi.product.sku: 0C40
dmi.sys.vendor: Dell Inc.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3.1~22.04.2
version.libgl1-mesa-glx: libgl1-mesa-glx 23.0.4-0ubuntu1~22.04.1
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.8
version.xserver-xorg-input-evdev: 

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

[Rolf Kutz]

The Workaround from #71 does not seem to work for me.

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

Title:
  Dock displaying over window after resuming from blank screen

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

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

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

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

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

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

  -

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

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

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

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

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


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

[Desktop-packages] [Bug 2054109] Re: nautilus fails to build on armhf

[Jeremy Bícha]

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

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

Title:
  nautilus fails to build on armhf

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

Bug description:
  Nautilus 46 fails to build on armhf because of a test failure.
  However, the test failure might be revealing a bug in nautilus's
  functions that would affect 32-bit architectures. I have filed the
  issue with the Nautilus developers.

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


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

[Desktop-packages] [Bug 1917939] Re: Windows maximise underneath dock after monitor sleep

[tetsuo29]

This bug is happening to me on 22.04.4 with all updates installed. It's
minor but also super annoying and the fact that it has gone unfixed for
so long makes Ubuntu seem like an unpolished distro which is weird
because I generally find Ubuntu to be the best and most polished distro
of them all. What can a normal user like myself do to get a bug like
this fixed? Make a donation? Keep reporting it here or somewhere else?

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

Title:
  Windows maximise underneath dock after monitor sleep

Status in Dash to dock:
  New
Status in Mutter:
  New
Status in gnome-shell package in Ubuntu:
  Fix Released
Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  Opinion
Status in mutter package in Ubuntu:
  Fix Released
Status in gnome-shell package in Fedora:
  Won't Fix

Bug description:
  Under wayland on 21.04 windows keep maximising underneath the dock. So
  I can see icons "through" the dock, when I shouldn't. In the attached
  screenshot you can see Telegram showing through the dock.

  If I switch to the application in question, unmaximise and re-
  maximise, it goes back to maximising inside the usable area of my
  desktop.

  But when I suspend and resume, then login, I'm left with windows under
  the dock again. Never seen this under xorg. I only discovered I was in
  wayland when I tried to ALT+F2, R to restart.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: gnome-shell 3.38.3-2ubuntu2
  ProcVersionSignature: Ubuntu 5.10.0-14.15-generic 5.10.11
  Uname: Linux 5.10.0-14-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu59
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar  5 19:21:39 2021
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-06-11 (267 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  RelatedPackageVersions: mutter-common 3.38.3-2ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to hirsute on 2020-12-14 (81 days ago)

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


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

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

[tetsuo29]

This bug is affecting me and I really wish I could do something to get
it fixed. On the one hand, it is a relatively minor bug but, on the the
other, it has gone unfixed for so long now and it's very annoying to
have to unmaximize and then remaximize windows after waking my laptop
from sleep or lock.

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

Title:
  Dock displaying over window after resuming from blank screen

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

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

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

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

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

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

  -

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

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

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

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

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


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

[Desktop-packages] [Bug 2052925] Re: lpoptions -d as root

[Timo Aaltonen]

Hello Rudra, or anyone else affected,

Accepted cups into jammy-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/cups/2.4.1op1-1ubuntu4.8 in a few
hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
jammy to verification-done-jammy. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-jammy. In either case, without details of your testing we will
not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

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

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

Title:
  lpoptions -d as root

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

Bug description:
  Copied from https://github.com/OpenPrinting/cups/issues/454

  Yair Yarom submitted Debian bug 1008053 and observed that running
  lpoptions as root does not update /etc/cups/lpoptions but
  /root/.cups/lpoptions.

  Running lpoptions as root (e.g. "lpoptions -d HP-OfficeJet") should
  update /etc/cups/lpoptions to be the defaults for all users. But
  instead it tries to update /root/.cups/lpoptions.

  This has been fixed upstream in cups, in debian sid, and mantic.
  Proposing to add this change in jammy and older (still supported)
  series as well.

  The fix is a one line change in
  https://github.com/OpenPrinting/cups/pull/456

  Thanks.

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

  ubuntu@jammy-vm:~$ lsb_release -rd
  Description:  Ubuntu 22.04.3 LTS
  Release:  22.04

  2) The version of the package you are using, via 'apt-cache policy
  pkgname' or by checking in Software Center

  ubuntu@jammy-vm:~$ apt-cache policy cups
  cups:
    Installed: 2.4.1op1-1ubuntu4.7
    Candidate: 2.4.1op1-1ubuntu4.7
    Version table:
   *** 2.4.1op1-1ubuntu4.7 500
  500 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages
  500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   2.4.1op1-1ubuntu4 500
  500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages

  3) What you expected to happen:

  root@jammy-vm:~# lpstat -p
  printer HP-Officejet-Pro-8710 is idle.  enabled since Thu 01 Feb 2024 
03:17:49 PM UTC
  root@jammy-vm:~#
  root@jammy-vm:~# lpoptions -d HP-Officejet-Pro-8710
  copies=1 device-uri=lpd://10.20.135.153:515/PASSTHRU finishings=3 
job-cancel-after=10800 job-hold-until=no-hold job-priority=50 
job-sheets=none,none marker-change-time=0 number-up=1 print-color-mode=color 
printer-commands=none printer-info=HP-Officejet-Pro-8710 
printer-is-accepting-jobs=true printer-is-shared=true 
printer-is-temporary=false printer-location printer-make-and-model='HP 
Officejet Pro 8710, hpcups 3.21.12' printer-state=3 
printer-state-change-time=1706800669 printer-state-reasons=none 
printer-type=4124 
printer-uri-supported=ipp://localhost/printers/HP-Officejet-Pro-8710
  root@jammy-vm:~#
  root@jammy-vm:~# cat /etc/cups/lpoptions
  Default HP-Officejet-Pro-8710
  root@jammy-vm:~#
  root@jammy-vm:~# cat /root/.cups/lpoptions
  cat: /etc/cups/lpoptions: No such file or directory
  root@jammy-vm:~#

  4) What happened instead:

  root@jammy-vm:~# lpstat -p
  printer HP-Officejet-Pro-8710 is idle.  enabled since Thu 01 Feb 2024 
03:17:49 PM UTC
  root@jammy-vm:~#
  root@jammy-vm:~# lpoptions -d HP-Officejet-Pro-8710
  copies=1 device-uri=lpd://10.20.135.153:515/PASSTHRU finishings=3 
job-cancel-after=10800 job-hold-until=no-hold job-priority=50 
job-sheets=none,none marker-change-time=0 number-up=1 print-color-mode=color 
printer-commands=none printer-info=HP-Officejet-Pro-8710 
printer-is-accepting-jobs=true printer-is-shared=true 
printer-is-temporary=false printer-location printer-make-and-model='HP 
Officejet Pro 8710, hpcups 3.21.12' printer-state=3 
printer-state-change-time=1706800669 printer-state-reasons=none 
printer-type=4124 
printer-uri-supported=ipp://localhost/printers/HP-Officejet-Pro-8710
  root@jammy-vm:~#
  root@jammy-vm:~# cat 

[Desktop-packages] [Bug 2051188] Re: Firefox 122 update breaks webextensions permission

[Amin Bandali]

Hi Paul, I don't think so?  Yesterday I tested on Firefox 123 an
extension that requires natives messaging to work, and it seemed to work
just fine.

Could you please double-check that the issue is happening with Firefox
123, and if so, please provide more details including some logs,
screenshots, and steps to reproduce the issue.

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

Title:
  Firefox 122 update breaks webextensions permission

Status in Mozilla Firefox:
  Fix Released
Status in firefox package in Ubuntu:
  Fix Released

Bug description:
  We build webextensions for Firefox.

  Since the latest update to Firefox 122, the native webextension bridge
  stopped working.

  ```
  $ flatpak permission-show snap.firefox
  Table ObjectApp  
Permissions   Data
  desktop-used-apps application/vnd.debian.binary-package snap.firefox 
gnome-software-local-file,1,3 0x00
  webextensions net.downloadhelper.coapp  snap.firefox yes  
 0x00
  ```

  This used to work and be enough, but not anymore.

  In the logs I see:

  
  ```
  Jan 25 12:47:56 ubuntu-linux-22-04-02-desktop firefox[154219]: 
OnGetManifestDone error: GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: 
No such method “GetManifest”
  Jan 25 12:47:57 ubuntu-linux-22-04-02-desktop 
firefox_firefox.desktop[154219]: [Parent 154219, Main Thread] WARNING: 
OnGetManifestDone error: GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: 
No such method “GetManifest”: 'glib warning', file 
/build/firefox/parts/firefox/build/toolkit/xre/nsSigHandlers.cpp:187
  ```

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


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

[Desktop-packages] [Bug 2054109] Re: nautilus fails to build on armhf

[Jeremy Bícha]

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

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

Title:
  nautilus fails to build on armhf

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

Bug description:
  Nautilus 46 fails to build on armhf because of a test failure.
  However, the test failure might be revealing a bug in nautilus's
  functions that would affect 32-bit architectures. I have filed the
  issue with the Nautilus developers.

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


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

[Desktop-packages] [Bug 2051068] Re: GUI crashed after installed proposed package libegl-mesa0

[drouineau]

I also enclose the apt log describing the dist-upgrade that causes the
issue

** Attachment added: "apt.log"
   
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2051068/+attachment/5748703/+files/apt.log

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

Title:
  GUI crashed after installed proposed package libegl-mesa0

Status in linux-oem-6.1 package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Invalid
Status in linux-oem-6.1 source package in Jammy:
  Won't Fix
Status in mesa source package in Jammy:
  Fix Released

Bug description:
  [Impact]

  OEM-6.1 kernel is missing support for minimum page size of 64k on DG2
  (gfx12.5). Mesa 23.2 started using that, so it broke initializing the
  gpu on boot, causing a blank screen with no GDM running (with wayland,
  and fallback to X failed too).

  [Fix]

  Revert the commit that allows using 64k page size, since that's what
  the current version in jammy-updates is using. OEM-6.1 kernel is going
  away, no need to patch that anymore. No other kernel is affected, >6.2
  works fine and thus this revert is not necessary in mantic or noble.

  [Test case]

  Install the update, boot up a machine with DG2 (iGPU or dGPU, doesn't
  matter). The login screen should appear.

  [Where things could go wrong]
  Hard to see how this could regress anything, as it just restores the limits 
for intel gfx12.5 as they were in the current mesa version in jammy.

  ---

  [Summary]
  After installed proposed package libegl-mesa0, reboot system.

  GUI crashed but still able to access system by ssh.

  [Steps to reproduce]
  1. Boot into OS
  2. sudo apt update
  3. sudo apt upgrade
  4. After upgrade process finished, reboot system.
  5. GUI crashed.

  [Expected result]
  GUI displayed normally

  [Actual result]
  GUI crashed

  [Failure rate]
  100%

  Tester comments
  ---
  if we don't upgrade libegl-mesa0, GUI will be fine.

  [Additional information]
  CID: 202303-31429
  SKU: MYBY-DVT2-C5
  Image: dell-bto-jammy-jellyfish-muk-X105-20231026-26_A02.iso
  system-manufacturer: Dell Inc.
  system-product-name: Precision 5680
  CPU: Intel(R) Core(TM) i7-13700H
  kernel-version: 6.1.0-1028-oem

  [Stage]
  Issue reported.

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


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

[Desktop-packages] [Bug 2051068] Re: GUI crashed after installed proposed package libegl-mesa0

[drouineau]

Dear all, after the upgrade of mesa packages on monday 
(23.2.1-1ubuntu3.1~22.04.2 from repo jammy-updates), I suffer similar symptoms 
at startup (causing a blank screen with no GDM running and message "something 
went wrong). I am using 22.04.3 LTS "Jammy Jellyfish" with kernel 
6.1.0-1034-oem but the issue remains with kernel 6.2.0-26-generic). I have a 
Dell precision 5480. The issue occurs if I use the nouveau driver or the 
proprietary nvidia driver (535) with profile "on-demand". The problem is solved 
with proprietary driver and profile "nvidia" (but costs a lot to the battery 
lifetime).  
I enclose the syslog around the crash which mentions an issue with mesa drivers.

Is this the same issue or should I open a new issue?


** Attachment added: "syslog"
   
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2051068/+attachment/5748702/+files/syslog

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

Title:
  GUI crashed after installed proposed package libegl-mesa0

Status in linux-oem-6.1 package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Invalid
Status in linux-oem-6.1 source package in Jammy:
  Won't Fix
Status in mesa source package in Jammy:
  Fix Released

Bug description:
  [Impact]

  OEM-6.1 kernel is missing support for minimum page size of 64k on DG2
  (gfx12.5). Mesa 23.2 started using that, so it broke initializing the
  gpu on boot, causing a blank screen with no GDM running (with wayland,
  and fallback to X failed too).

  [Fix]

  Revert the commit that allows using 64k page size, since that's what
  the current version in jammy-updates is using. OEM-6.1 kernel is going
  away, no need to patch that anymore. No other kernel is affected, >6.2
  works fine and thus this revert is not necessary in mantic or noble.

  [Test case]

  Install the update, boot up a machine with DG2 (iGPU or dGPU, doesn't
  matter). The login screen should appear.

  [Where things could go wrong]
  Hard to see how this could regress anything, as it just restores the limits 
for intel gfx12.5 as they were in the current mesa version in jammy.

  ---

  [Summary]
  After installed proposed package libegl-mesa0, reboot system.

  GUI crashed but still able to access system by ssh.

  [Steps to reproduce]
  1. Boot into OS
  2. sudo apt update
  3. sudo apt upgrade
  4. After upgrade process finished, reboot system.
  5. GUI crashed.

  [Expected result]
  GUI displayed normally

  [Actual result]
  GUI crashed

  [Failure rate]
  100%

  Tester comments
  ---
  if we don't upgrade libegl-mesa0, GUI will be fine.

  [Additional information]
  CID: 202303-31429
  SKU: MYBY-DVT2-C5
  Image: dell-bto-jammy-jellyfish-muk-X105-20231026-26_A02.iso
  system-manufacturer: Dell Inc.
  system-product-name: Precision 5680
  CPU: Intel(R) Core(TM) i7-13700H
  kernel-version: 6.1.0-1028-oem

  [Stage]
  Issue reported.

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


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

[Desktop-packages] [Bug 2026194] Re: When clicking on some maximized or tiled windows, focus on roughly the lower quarter falls to the window behind

[Tais P. Hansen]

I think this might be similar to what I've experienced lately. It seems
like it is definitely triggered after a window resize, both manual and
automatic. After the resize, button clicks seems to fall through the
window to whatever is behind it. Reproduction is reliable so I can even
record a video of it happening if it helps.

This is on Ubuntu 23.10, mutter=45.2-0ubuntu3, Xorg.

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

Title:
  When clicking on some maximized or tiled windows, focus on roughly the
  lower quarter falls to the window behind

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  Initially I thought this was an issue with IntelliJ and filed a bug there:
  
https://youtrack.jetbrains.com/issue/IDEA-323780/Maximizing-the-the-window-sometimes-causes-clicks-on-a-lower-fraction-to-pass-through-to-the-window-behind

  But when I had the same issue with GIMP, I realized it's an Ubuntu or
  GNOME issue instead. I am assuming this is a gnome-shell problem.

  
  Every once in a while, when I maximize or tile (Win+Right) the IntelliJ 
window, a bottom fraction of the window (somewhere around a quarter) becomes 
impossible to interact with, with the mouse. Clicking in that lower area will 
give focus to the thing behind IntelliJ, and if it's a window, raise it to the 
foreground. if I restore the window so that it is not maximized, the entire 
window is interactive with the mouse once again.

  This also happened with GIMP.

  
  The attached "Screencast" is a recording. I had to crop it to hide personal 
information. The attached screenshot shows the state of my screen so you have 
context, with a bright green color used to replace personal information.

  For the first 10s of the recording, I simply moused over to show how
  the cursor changes around a quarter from the bottom of the screen.

  For the next 10s, I left click, then move, then left click, then move,
  until focus changes to Sublime, the window behind IntelliJ.

  For the remainder of the video I show that right-clicking and mousing
  over works fine on the top three quarters, until I reach the bottom
  again, and then the right click is sent to Sublime.

  
  Ubuntu 23.04
  gnome-shell version 44.2-0ubuntu1

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: gnome-shell 44.2-0ubuntu1
  ProcVersionSignature: Ubuntu 6.2.0-24.24-generic 6.2.12
  Uname: Linux 6.2.0-24-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jul  5 12:05:46 2023
  DisplayManager: gdm3
  InstallationDate: Installed on 2022-09-19 (289 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/usr/bin/zsh
   TERM=screen-256color
   XDG_RUNTIME_DIR=
  RelatedPackageVersions: mutter-common 44.2-0ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Desktop-packages] [Bug 2026194] Re: When clicking on some maximized or tiled windows, focus on roughly the lower quarter falls to the window behind

[Launchpad Bug Tracker]

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: gnome-shell (Ubuntu)
   Status: New => Confirmed

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

Title:
  When clicking on some maximized or tiled windows, focus on roughly the
  lower quarter falls to the window behind

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  Initially I thought this was an issue with IntelliJ and filed a bug there:
  
https://youtrack.jetbrains.com/issue/IDEA-323780/Maximizing-the-the-window-sometimes-causes-clicks-on-a-lower-fraction-to-pass-through-to-the-window-behind

  But when I had the same issue with GIMP, I realized it's an Ubuntu or
  GNOME issue instead. I am assuming this is a gnome-shell problem.

  
  Every once in a while, when I maximize or tile (Win+Right) the IntelliJ 
window, a bottom fraction of the window (somewhere around a quarter) becomes 
impossible to interact with, with the mouse. Clicking in that lower area will 
give focus to the thing behind IntelliJ, and if it's a window, raise it to the 
foreground. if I restore the window so that it is not maximized, the entire 
window is interactive with the mouse once again.

  This also happened with GIMP.

  
  The attached "Screencast" is a recording. I had to crop it to hide personal 
information. The attached screenshot shows the state of my screen so you have 
context, with a bright green color used to replace personal information.

  For the first 10s of the recording, I simply moused over to show how
  the cursor changes around a quarter from the bottom of the screen.

  For the next 10s, I left click, then move, then left click, then move,
  until focus changes to Sublime, the window behind IntelliJ.

  For the remainder of the video I show that right-clicking and mousing
  over works fine on the top three quarters, until I reach the bottom
  again, and then the right click is sent to Sublime.

  
  Ubuntu 23.04
  gnome-shell version 44.2-0ubuntu1

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: gnome-shell 44.2-0ubuntu1
  ProcVersionSignature: Ubuntu 6.2.0-24.24-generic 6.2.12
  Uname: Linux 6.2.0-24-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jul  5 12:05:46 2023
  DisplayManager: gdm3
  InstallationDate: Installed on 2022-09-19 (289 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/usr/bin/zsh
   TERM=screen-256color
   XDG_RUNTIME_DIR=
  RelatedPackageVersions: mutter-common 44.2-0ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Desktop-packages] [Bug 2023322] Re: GTK internal browser does not render with Nvidia drivers

[Bug Watch Updater]

** Bug watch added: bugs.webkit.org/ #210100
   https://bugs.webkit.org/show_bug.cgi?id=210100

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

Title:
  GTK internal browser does not render with Nvidia drivers

Status in Webkit:
  Fix Released
Status in gnome-control-center package in Ubuntu:
  Invalid
Status in gnome-online-accounts package in Ubuntu:
  Invalid
Status in webkit2gtk package in Ubuntu:
  Fix Released
Status in yelp package in Ubuntu:
  Invalid
Status in webkit2gtk package in Debian:
  Fix Released

Bug description:
  When I go into Settings > Online Accounts > Google, I get to the
  prompt for email address, once in a while it stops accepting input
  there. But often I can get to the password screen. Once I do, I can't
  type anything or paste anything.

  This is a fresh install of Ubuntu 23.04 and I have installed all
  updates.

  Nothing in /var/crash

  Jun 08 11:15:59 CCW-HAL systemd[3523]: 
vte-spawn-8b4a59a3-a060-4bdd-92e6-285656bdb9a2.scope: Consumed 3.448s CPU time.
  Jun 08 11:16:01 CCW-HAL gnome-shell[3803]: g_closure_unref: assertion 
'closure->ref_count > 0' failed
  Jun 08 11:16:01 CCW-HAL gnome-shell[3803]: g_closure_unref: assertion 
'closure->ref_count > 0' failed
  Jun 08 11:16:01 CCW-HAL gnome-shell[3803]: g_closure_unref: assertion 
'closure->ref_count > 0' failed
  Jun 08 11:16:29 CCW-HAL systemd[3523]: Started 
app-gnome-org.gnome.Terminal-10924.scope - Application launched by gnome-shell.
  Jun 08 11:16:29 CCW-HAL dbus-daemon[3552]: [session uid=1000 pid=3552] 
Activating via systemd: service name='org.gnome.Terminal' 
unit='gnome-terminal-server.service' requested by ':1.167' (uid=1000 pid=10927 
comm="/usr/bin/gnome-terminal.real" label="unconfined")
  Jun 08 11:16:29 CCW-HAL systemd[3523]: Starting gnome-terminal-server.service 
- GNOME Terminal Server...
  Jun 08 11:16:29 CCW-HAL dbus-daemon[3552]: [session uid=1000 pid=3552] 
Successfully activated service 'org.gnome.Terminal'
  Jun 08 11:16:29 CCW-HAL systemd[3523]: Started gnome-terminal-server.service 
- GNOME Terminal Server.
  Jun 08 11:16:29 CCW-HAL systemd[3523]: Started 
vte-spawn-9cee1911-372a-4bb4-8b57-694984e43990.scope - VTE child process 10955 
launched by gnome-terminal-server process 10931.
  Jun 08 11:16:49 CCW-HAL gnome-control-c[8079]: Error showing account: Child 
process exited with code 1
  Jun 08 11:16:53 CCW-HAL gnome-online-accounts-panel.desktop[9764]: GLib-GIO: 
Using cross-namespace EXTERNAL authentication (this will deadlock if server is 
GDBus < 2.73.3)GLib-GIO: _g_io_module_get_default: Found default implementation 
gvfs (GDaemonVfs) for ‘gio-vfs’GLib: unsetenv() is not thread-safe and should 
not be used after threads are createdGLib-GIO: _g_io_module_get_default: Found 
default implementation dconf (DConfSettingsBackend) for 
‘gsettings-backend’GoaBackend: Loading all providers: GoaBackend: - 
googleGoaBackend: - owncloudGoaBackend: - windows_liveGoaBackend: - 
exchangeGoaBackend: - lastfmGoaBackend: - imap_smtpGoaBackend: - 
kerberosGoaBackend: activated kerberos providerGLib-GIO: 
_g_io_module_get_default: Found default implementation gnutls 
(GTlsBackendGnutls) for ‘gio-tls-backend’Failed to create account: Dialog was 
dismissed
  Jun 08 11:16:53 CCW-HAL xdg-desktop-por[3907]: Realtime error: Could not map 
pid: Could not determine pid namespace: Could not find instance-id in process's 
/.flatpak-info
  Jun 08 11:17:01 CCW-HAL CRON[11093]: pam_unix(cron:session): session opened 
for user root(uid=0) by (uid=0)
  Jun 08 11:17:01 CCW-HAL CRON[11094]: (root) CMD (cd / && run-parts --report 
/etc/cron.hourly)
  Jun 08 11:17:01 CCW-HAL CRON[11093]: pam_unix(cron:session): session closed 
for user root
  Jun 08 11:17:06 CCW-HAL kernel: WebKitWebProces[11026]: segfault at 
55bd22ad9adc ip 55bd22ad9adc sp 7ffd1f6adbe8 error 14 likely on CPU 2 
(core 2, socket 0)
  Jun 08 11:17:06 CCW-HAL kernel: Code: Unable to access opcode bytes at 
0x55bd22ad9ab2.
  Jun 08 11:17:36 CCW-HAL gnome-shell[3803]: Window manager warning: 
WM_TRANSIENT_FOR window 0x3a02767 for 0x3a02778 window override-redirect is an 
override-redirect window and this is not correct according to the standard, so 
we'll fallback to the first non-override-redirect window 0x3a006dc.
  Jun 08 11:17:42 CCW-HAL systemd[1]: Starting systemd-tmpfiles-clean.service - 
Cleanup of Temporary Directories...
  Jun 08 11:17:42 CCW-HAL systemd[1]: systemd-tmpfiles-clean.service: 
Deactivated successfully.
  Jun 08 11:17:42 CCW-HAL systemd[1]: Finished systemd-tmpfiles-clean.service - 
Cleanup of Temporary Directories.
  Jun 08 11:17:42 CCW-HAL systemd[1]: 
run-credentials-systemd\x2dtmpfiles\x2dclean.service.mount: Deactivated 
successfully.
  Jun 08 11:18:10 CCW-HAL gnome-shell[3803]: Window manager warning: 
WM_TRANSIENT_FOR window 0x3a029e2 for 0x3a029f0 window override-redirect is an 
override-redirect window 

[Desktop-packages] [Bug 2023322]

[Georges Basile Stavracas Neto]

This bug is for GTK4, Liferea is GTK3. That's a separate issue that
should not be marked as a blocker for
https://bugs.webkit.org/show_bug.cgi?id=210100

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

Title:
  GTK internal browser does not render with Nvidia drivers

Status in Webkit:
  Fix Released
Status in gnome-control-center package in Ubuntu:
  Invalid
Status in gnome-online-accounts package in Ubuntu:
  Invalid
Status in webkit2gtk package in Ubuntu:
  Fix Released
Status in yelp package in Ubuntu:
  Invalid
Status in webkit2gtk package in Debian:
  Fix Released

Bug description:
  When I go into Settings > Online Accounts > Google, I get to the
  prompt for email address, once in a while it stops accepting input
  there. But often I can get to the password screen. Once I do, I can't
  type anything or paste anything.

  This is a fresh install of Ubuntu 23.04 and I have installed all
  updates.

  Nothing in /var/crash

  Jun 08 11:15:59 CCW-HAL systemd[3523]: 
vte-spawn-8b4a59a3-a060-4bdd-92e6-285656bdb9a2.scope: Consumed 3.448s CPU time.
  Jun 08 11:16:01 CCW-HAL gnome-shell[3803]: g_closure_unref: assertion 
'closure->ref_count > 0' failed
  Jun 08 11:16:01 CCW-HAL gnome-shell[3803]: g_closure_unref: assertion 
'closure->ref_count > 0' failed
  Jun 08 11:16:01 CCW-HAL gnome-shell[3803]: g_closure_unref: assertion 
'closure->ref_count > 0' failed
  Jun 08 11:16:29 CCW-HAL systemd[3523]: Started 
app-gnome-org.gnome.Terminal-10924.scope - Application launched by gnome-shell.
  Jun 08 11:16:29 CCW-HAL dbus-daemon[3552]: [session uid=1000 pid=3552] 
Activating via systemd: service name='org.gnome.Terminal' 
unit='gnome-terminal-server.service' requested by ':1.167' (uid=1000 pid=10927 
comm="/usr/bin/gnome-terminal.real" label="unconfined")
  Jun 08 11:16:29 CCW-HAL systemd[3523]: Starting gnome-terminal-server.service 
- GNOME Terminal Server...
  Jun 08 11:16:29 CCW-HAL dbus-daemon[3552]: [session uid=1000 pid=3552] 
Successfully activated service 'org.gnome.Terminal'
  Jun 08 11:16:29 CCW-HAL systemd[3523]: Started gnome-terminal-server.service 
- GNOME Terminal Server.
  Jun 08 11:16:29 CCW-HAL systemd[3523]: Started 
vte-spawn-9cee1911-372a-4bb4-8b57-694984e43990.scope - VTE child process 10955 
launched by gnome-terminal-server process 10931.
  Jun 08 11:16:49 CCW-HAL gnome-control-c[8079]: Error showing account: Child 
process exited with code 1
  Jun 08 11:16:53 CCW-HAL gnome-online-accounts-panel.desktop[9764]: GLib-GIO: 
Using cross-namespace EXTERNAL authentication (this will deadlock if server is 
GDBus < 2.73.3)GLib-GIO: _g_io_module_get_default: Found default implementation 
gvfs (GDaemonVfs) for ‘gio-vfs’GLib: unsetenv() is not thread-safe and should 
not be used after threads are createdGLib-GIO: _g_io_module_get_default: Found 
default implementation dconf (DConfSettingsBackend) for 
‘gsettings-backend’GoaBackend: Loading all providers: GoaBackend: - 
googleGoaBackend: - owncloudGoaBackend: - windows_liveGoaBackend: - 
exchangeGoaBackend: - lastfmGoaBackend: - imap_smtpGoaBackend: - 
kerberosGoaBackend: activated kerberos providerGLib-GIO: 
_g_io_module_get_default: Found default implementation gnutls 
(GTlsBackendGnutls) for ‘gio-tls-backend’Failed to create account: Dialog was 
dismissed
  Jun 08 11:16:53 CCW-HAL xdg-desktop-por[3907]: Realtime error: Could not map 
pid: Could not determine pid namespace: Could not find instance-id in process's 
/.flatpak-info
  Jun 08 11:17:01 CCW-HAL CRON[11093]: pam_unix(cron:session): session opened 
for user root(uid=0) by (uid=0)
  Jun 08 11:17:01 CCW-HAL CRON[11094]: (root) CMD (cd / && run-parts --report 
/etc/cron.hourly)
  Jun 08 11:17:01 CCW-HAL CRON[11093]: pam_unix(cron:session): session closed 
for user root
  Jun 08 11:17:06 CCW-HAL kernel: WebKitWebProces[11026]: segfault at 
55bd22ad9adc ip 55bd22ad9adc sp 7ffd1f6adbe8 error 14 likely on CPU 2 
(core 2, socket 0)
  Jun 08 11:17:06 CCW-HAL kernel: Code: Unable to access opcode bytes at 
0x55bd22ad9ab2.
  Jun 08 11:17:36 CCW-HAL gnome-shell[3803]: Window manager warning: 
WM_TRANSIENT_FOR window 0x3a02767 for 0x3a02778 window override-redirect is an 
override-redirect window and this is not correct according to the standard, so 
we'll fallback to the first non-override-redirect window 0x3a006dc.
  Jun 08 11:17:42 CCW-HAL systemd[1]: Starting systemd-tmpfiles-clean.service - 
Cleanup of Temporary Directories...
  Jun 08 11:17:42 CCW-HAL systemd[1]: systemd-tmpfiles-clean.service: 
Deactivated successfully.
  Jun 08 11:17:42 CCW-HAL systemd[1]: Finished systemd-tmpfiles-clean.service - 
Cleanup of Temporary Directories.
  Jun 08 11:17:42 CCW-HAL systemd[1]: 
run-credentials-systemd\x2dtmpfiles\x2dclean.service.mount: Deactivated 
successfully.
  Jun 08 11:18:10 CCW-HAL gnome-shell[3803]: Window manager warning: 
WM_TRANSIENT_FOR window 0x3a029e2 for 0x3a029f0 

[Desktop-packages] [Bug 2023322]

[Mcatanzaro-c]

Hi Craig and Thomas (and Emil if you're still around): if you're still
encountering problems with NVIDIA graphics, please report new a bug and
leave a comment here linking to the new bug.

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

Title:
  GTK internal browser does not render with Nvidia drivers

Status in Webkit:
  Fix Released
Status in gnome-control-center package in Ubuntu:
  Invalid
Status in gnome-online-accounts package in Ubuntu:
  Invalid
Status in webkit2gtk package in Ubuntu:
  Fix Released
Status in yelp package in Ubuntu:
  Invalid
Status in webkit2gtk package in Debian:
  Fix Released

Bug description:
  When I go into Settings > Online Accounts > Google, I get to the
  prompt for email address, once in a while it stops accepting input
  there. But often I can get to the password screen. Once I do, I can't
  type anything or paste anything.

  This is a fresh install of Ubuntu 23.04 and I have installed all
  updates.

  Nothing in /var/crash

  Jun 08 11:15:59 CCW-HAL systemd[3523]: 
vte-spawn-8b4a59a3-a060-4bdd-92e6-285656bdb9a2.scope: Consumed 3.448s CPU time.
  Jun 08 11:16:01 CCW-HAL gnome-shell[3803]: g_closure_unref: assertion 
'closure->ref_count > 0' failed
  Jun 08 11:16:01 CCW-HAL gnome-shell[3803]: g_closure_unref: assertion 
'closure->ref_count > 0' failed
  Jun 08 11:16:01 CCW-HAL gnome-shell[3803]: g_closure_unref: assertion 
'closure->ref_count > 0' failed
  Jun 08 11:16:29 CCW-HAL systemd[3523]: Started 
app-gnome-org.gnome.Terminal-10924.scope - Application launched by gnome-shell.
  Jun 08 11:16:29 CCW-HAL dbus-daemon[3552]: [session uid=1000 pid=3552] 
Activating via systemd: service name='org.gnome.Terminal' 
unit='gnome-terminal-server.service' requested by ':1.167' (uid=1000 pid=10927 
comm="/usr/bin/gnome-terminal.real" label="unconfined")
  Jun 08 11:16:29 CCW-HAL systemd[3523]: Starting gnome-terminal-server.service 
- GNOME Terminal Server...
  Jun 08 11:16:29 CCW-HAL dbus-daemon[3552]: [session uid=1000 pid=3552] 
Successfully activated service 'org.gnome.Terminal'
  Jun 08 11:16:29 CCW-HAL systemd[3523]: Started gnome-terminal-server.service 
- GNOME Terminal Server.
  Jun 08 11:16:29 CCW-HAL systemd[3523]: Started 
vte-spawn-9cee1911-372a-4bb4-8b57-694984e43990.scope - VTE child process 10955 
launched by gnome-terminal-server process 10931.
  Jun 08 11:16:49 CCW-HAL gnome-control-c[8079]: Error showing account: Child 
process exited with code 1
  Jun 08 11:16:53 CCW-HAL gnome-online-accounts-panel.desktop[9764]: GLib-GIO: 
Using cross-namespace EXTERNAL authentication (this will deadlock if server is 
GDBus < 2.73.3)GLib-GIO: _g_io_module_get_default: Found default implementation 
gvfs (GDaemonVfs) for ‘gio-vfs’GLib: unsetenv() is not thread-safe and should 
not be used after threads are createdGLib-GIO: _g_io_module_get_default: Found 
default implementation dconf (DConfSettingsBackend) for 
‘gsettings-backend’GoaBackend: Loading all providers: GoaBackend: - 
googleGoaBackend: - owncloudGoaBackend: - windows_liveGoaBackend: - 
exchangeGoaBackend: - lastfmGoaBackend: - imap_smtpGoaBackend: - 
kerberosGoaBackend: activated kerberos providerGLib-GIO: 
_g_io_module_get_default: Found default implementation gnutls 
(GTlsBackendGnutls) for ‘gio-tls-backend’Failed to create account: Dialog was 
dismissed
  Jun 08 11:16:53 CCW-HAL xdg-desktop-por[3907]: Realtime error: Could not map 
pid: Could not determine pid namespace: Could not find instance-id in process's 
/.flatpak-info
  Jun 08 11:17:01 CCW-HAL CRON[11093]: pam_unix(cron:session): session opened 
for user root(uid=0) by (uid=0)
  Jun 08 11:17:01 CCW-HAL CRON[11094]: (root) CMD (cd / && run-parts --report 
/etc/cron.hourly)
  Jun 08 11:17:01 CCW-HAL CRON[11093]: pam_unix(cron:session): session closed 
for user root
  Jun 08 11:17:06 CCW-HAL kernel: WebKitWebProces[11026]: segfault at 
55bd22ad9adc ip 55bd22ad9adc sp 7ffd1f6adbe8 error 14 likely on CPU 2 
(core 2, socket 0)
  Jun 08 11:17:06 CCW-HAL kernel: Code: Unable to access opcode bytes at 
0x55bd22ad9ab2.
  Jun 08 11:17:36 CCW-HAL gnome-shell[3803]: Window manager warning: 
WM_TRANSIENT_FOR window 0x3a02767 for 0x3a02778 window override-redirect is an 
override-redirect window and this is not correct according to the standard, so 
we'll fallback to the first non-override-redirect window 0x3a006dc.
  Jun 08 11:17:42 CCW-HAL systemd[1]: Starting systemd-tmpfiles-clean.service - 
Cleanup of Temporary Directories...
  Jun 08 11:17:42 CCW-HAL systemd[1]: systemd-tmpfiles-clean.service: 
Deactivated successfully.
  Jun 08 11:17:42 CCW-HAL systemd[1]: Finished systemd-tmpfiles-clean.service - 
Cleanup of Temporary Directories.
  Jun 08 11:17:42 CCW-HAL systemd[1]: 
run-credentials-systemd\x2dtmpfiles\x2dclean.service.mount: Deactivated 
successfully.
  Jun 08 11:18:10 CCW-HAL gnome-shell[3803]: Window manager warning: 

[Desktop-packages] [Bug 2023322]

[Zlatko-webkit]

Hi Michael,

I already hopped over to bug #261874, as the description in #c32 over
there matches my setup exactly. The errors I get are:

> [zlatko@disclosure:~]$ liferea
> src/nv_gbm.c:99: GBM-DRV error (nv_gbm_bo_create): 
> DRM_IOCTL_NVIDIA_GEM_ALLOC_NVKMS_MEMORY failed (ret=-1)
> 
> Failed to create GBM buffer of size 469x191: Invalid argument
> src/nv_gbm.c:99: GBM-DRV error (nv_gbm_bo_create): 
> DRM_IOCTL_NVIDIA_GEM_ALLOC_NVKMS_MEMORY failed (ret=-1)
> 
>Failed to create GBM buffer of size 469x191: Invalid argument
> src/nv_gbm.c:99: GBM-DRV error (nv_gbm_bo_create): 
> DRM_IOCTL_NVIDIA_GEM_ALLOC_NVKMS_MEMORY failed (ret=-1)
> 
> Failed to create GBM buffer of size 469x191: Invalid argument
> Failed to create EGL images for DMABufs with file descriptors -1, -1 and -1

Yes, I'm on X11 without modsetting (with NVidia this only works when
booting UEFI, which I don't), and "liferea" is a GTK3 application (ie.
using libwebkit2gtk-4.0.so), where the current state still seems to be
...

> "There's no workaround for GTK3, we need to figure out why gbm_bo_map
is failing and fix it."

... so this bug seems to be the perfect fit. :-)

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

Title:
  GTK internal browser does not render with Nvidia drivers

Status in Webkit:
  Fix Released
Status in gnome-control-center package in Ubuntu:
  Invalid
Status in gnome-online-accounts package in Ubuntu:
  Invalid
Status in webkit2gtk package in Ubuntu:
  Fix Released
Status in yelp package in Ubuntu:
  Invalid
Status in webkit2gtk package in Debian:
  Fix Released

Bug description:
  When I go into Settings > Online Accounts > Google, I get to the
  prompt for email address, once in a while it stops accepting input
  there. But often I can get to the password screen. Once I do, I can't
  type anything or paste anything.

  This is a fresh install of Ubuntu 23.04 and I have installed all
  updates.

  Nothing in /var/crash

  Jun 08 11:15:59 CCW-HAL systemd[3523]: 
vte-spawn-8b4a59a3-a060-4bdd-92e6-285656bdb9a2.scope: Consumed 3.448s CPU time.
  Jun 08 11:16:01 CCW-HAL gnome-shell[3803]: g_closure_unref: assertion 
'closure->ref_count > 0' failed
  Jun 08 11:16:01 CCW-HAL gnome-shell[3803]: g_closure_unref: assertion 
'closure->ref_count > 0' failed
  Jun 08 11:16:01 CCW-HAL gnome-shell[3803]: g_closure_unref: assertion 
'closure->ref_count > 0' failed
  Jun 08 11:16:29 CCW-HAL systemd[3523]: Started 
app-gnome-org.gnome.Terminal-10924.scope - Application launched by gnome-shell.
  Jun 08 11:16:29 CCW-HAL dbus-daemon[3552]: [session uid=1000 pid=3552] 
Activating via systemd: service name='org.gnome.Terminal' 
unit='gnome-terminal-server.service' requested by ':1.167' (uid=1000 pid=10927 
comm="/usr/bin/gnome-terminal.real" label="unconfined")
  Jun 08 11:16:29 CCW-HAL systemd[3523]: Starting gnome-terminal-server.service 
- GNOME Terminal Server...
  Jun 08 11:16:29 CCW-HAL dbus-daemon[3552]: [session uid=1000 pid=3552] 
Successfully activated service 'org.gnome.Terminal'
  Jun 08 11:16:29 CCW-HAL systemd[3523]: Started gnome-terminal-server.service 
- GNOME Terminal Server.
  Jun 08 11:16:29 CCW-HAL systemd[3523]: Started 
vte-spawn-9cee1911-372a-4bb4-8b57-694984e43990.scope - VTE child process 10955 
launched by gnome-terminal-server process 10931.
  Jun 08 11:16:49 CCW-HAL gnome-control-c[8079]: Error showing account: Child 
process exited with code 1
  Jun 08 11:16:53 CCW-HAL gnome-online-accounts-panel.desktop[9764]: GLib-GIO: 
Using cross-namespace EXTERNAL authentication (this will deadlock if server is 
GDBus < 2.73.3)GLib-GIO: _g_io_module_get_default: Found default implementation 
gvfs (GDaemonVfs) for ‘gio-vfs’GLib: unsetenv() is not thread-safe and should 
not be used after threads are createdGLib-GIO: _g_io_module_get_default: Found 
default implementation dconf (DConfSettingsBackend) for 
‘gsettings-backend’GoaBackend: Loading all providers: GoaBackend: - 
googleGoaBackend: - owncloudGoaBackend: - windows_liveGoaBackend: - 
exchangeGoaBackend: - lastfmGoaBackend: - imap_smtpGoaBackend: - 
kerberosGoaBackend: activated kerberos providerGLib-GIO: 
_g_io_module_get_default: Found default implementation gnutls 
(GTlsBackendGnutls) for ‘gio-tls-backend’Failed to create account: Dialog was 
dismissed
  Jun 08 11:16:53 CCW-HAL xdg-desktop-por[3907]: Realtime error: Could not map 
pid: Could not determine pid namespace: Could not find instance-id in process's 
/.flatpak-info
  Jun 08 11:17:01 CCW-HAL CRON[11093]: pam_unix(cron:session): session opened 
for user root(uid=0) by (uid=0)
  Jun 08 11:17:01 CCW-HAL CRON[11094]: (root) CMD (cd / && run-parts --report 
/etc/cron.hourly)
  Jun 08 11:17:01 CCW-HAL CRON[11093]: pam_unix(cron:session): session closed 
for user root
  Jun 08 11:17:06 CCW-HAL kernel: WebKitWebProces[11026]: segfault at 
55bd22ad9adc ip 55bd22ad9adc sp 7ffd1f6adbe8 error 14 

[Desktop-packages] [Bug 2036388] Re: Login screen grey background flickers

[Daniel van Vugt]

Looks like Yaru would need the same fix.

** Also affects: yaru-theme (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: yaru-theme (Ubuntu)
   Importance: Undecided => Low

** Changed in: yaru-theme (Ubuntu)
   Status: New => Triaged

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

Title:
  Login screen grey background flickers

Status in gnome-shell package in Ubuntu:
  In Progress
Status in yaru-theme package in Ubuntu:
  Triaged

Bug description:
  Login screen grey background flickers on startup and again on login.
  It looks like it's trying to fade between two very similar shades of
  grey and there just aren't enough colours between them to fade
  smoothly.

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


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

[Desktop-packages] [Bug 2036388] Re: Login screen grey background flickers

[Daniel van Vugt]

Fix proposed: https://gitlab.gnome.org/GNOME/gnome-
shell/-/merge_requests/3207

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

Title:
  Login screen grey background flickers

Status in gnome-shell package in Ubuntu:
  In Progress

Bug description:
  Login screen grey background flickers on startup and again on login.
  It looks like it's trying to fade between two very similar shades of
  grey and there just aren't enough colours between them to fade
  smoothly.

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


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

[Desktop-packages] [Bug 2039021] Re: NO-GUI headless convert-to function error in 7.6.1.2 60(Build:2)

[Rico Tzschichholz]

** Changed in: libreoffice (Ubuntu)
   Status: New => Fix Committed

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

Title:
  NO-GUI headless convert-to function error in 7.6.1.2 60(Build:2)

Status in LibreOffice:
  Fix Released
Status in libreoffice package in Ubuntu:
  Fix Committed

Bug description:
  Original bug report to LibreOffice team:
  https://bugs.documentfoundation.org/show_bug.cgi?id=157424

  7.6.1.2 60(Build:2) no-gui version, Ubuntu Server  20.04 LTS gives
  error.

  soffice --headless --convert-to pdf path/to/file --> Error: source
  file could not be loaded

  Ubuntu 20.04 LTS Desktop version has no error with the same version,
  only on Server. The installation difference is libreoffice vs
  libreoffice-nogui. Previous version doesent produces this error:
  7.5.6.2 50(Build:2) work perfect.

  Lots of no-gui version fails in Ubuntu Server 20.04 LTS with "Error:
  source file could not be loaded" message.

  Specific examples:

  - LibreOffice 6.4.7.2 40(Build:2)  --> Same error with xlsx with --convert-to 
html
  - LibreOffice 7.5.3.2 50(Build:2)  --> Same error with xlsx with --convert-to 
html

  !!! Only LibreOffice 7.5.6.2 50(Build:2) works perfectly in both case.
  !!! Example outputs:

  soffice --headless --convert-to pdf teszt.docx
  convert /home/zsolt/teszt.docx -> /home/zsolt/teszt.pdf using filter : 
writer_pdf_Export

  soffice --headless --convert-to html teszt.xlsx
  convert /home/zsolt/teszt.xlsx -> /home/zsolt/teszt.html using filter : HTML 
(StarCalc)

  Fortunately *ppa:libreoffice/libreoffice-still* contains the good
  version so i had to change the repos in all servers

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/2039021/+subscriptions


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