[Desktop-packages] [Bug 2038834] Re: GPU acceleration via VirGL is broken in qemu

[Mate Kukri]

Hi @sergiodj,

I believe it was already uploaded, and is currently in the unapproved
queue:
https://launchpadlibrarian.net/697888277/mesa_23.2.1-1ubuntu3_23.2.1-1ubuntu3.1.diff.gz

The difference to noble is purely the version number being ubuntu3.1
instead of ubuntu4.

Mate

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

Title:
  GPU acceleration via VirGL is broken in qemu

Status in Release Notes for Ubuntu:
  New
Status in mesa package in Ubuntu:
  Fix Released
Status in mesa source package in Mantic:
  New
Status in mesa source package in Noble:
  Fix Released

Bug description:
  
  [ Impact ] 
   * Enabling GPU acceleration can cause host-side crashes on mantic/noble VMs 

   * This was reported by someone else upstream and is already fixed by 
 https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/25580.

  [ Test Plan ]

   * I've tested the patch on an affected macOS host running Ubuntu in UTM with 
 OpenGL enabled on both Mantic and Noble VMs.

   * Anyone else can do the same on an affected host by simply installing the 
 patched package and booting to the desktop.

  [ Where problems could occur ]

   * This patch fixes an upstream mesa regression which caused libvirglrendrer 
to 
 crash on the host side.

   * This makes a non-working use case work, VirGL on affected hosts cannot 
 regress as it simply didn't work before.

   * Risk of breakage is mainly from other packages possible affected by a mesa 
 rebuild.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-release-notes/+bug/2038834/+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 2043604] Re: Sidebar is not mnaually expandable to make directory names visiible.

[Sebastien Bacher]

Thanks, there had been reports of the issue upstream
https://gitlab.gnome.org/GNOME/nautilus/-/issues/2641

The issue got closed after some refactoring but the issue you describe
is still there so it might be worth asking them to reopen the ticket

You should be able to mouseover the entry and see the name in the popup
as a workaround

** Bug watch added: gitlab.gnome.org/GNOME/nautilus/-/issues #2641
   https://gitlab.gnome.org/GNOME/nautilus/-/issues/2641

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

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

** Summary changed:

- Sidebar is not mnaually expandable to make directory names visiible.
+ Sidebar is not manually expandable to make directory names visible.

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

Title:
  Sidebar is not manually expandable to make directory names visible.

Status in nautilus package in Ubuntu:
  Confirmed

Bug description:
  Sidebar is not manually expandable to make directory names visible.

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: nautilus 1:45~rc-1ubuntu1
  ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
  Uname: Linux 6.5.0-9-generic x86_64
  ApportVersion: 2.27.0-0ubuntu6
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CloudArchitecture: x86_64
  CloudID: none
  CloudName: none
  CloudPlatform: none
  CloudSubPlatform: config
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Nov 15 17:46:14 2023
  GsettingsChanges:
   b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'"
   b'org.gnome.nautilus.preferences' b'migrated-gtk-settings' b'true'
   b'org.gnome.nautilus.window-state' b'maximized' b'true'
  InstallationDate: Installed on 2023-11-15 (0 days ago)
  InstallationMedia: Ubuntu 24.04 "Noble Numbat" - Daily amd64 (20231115.1)
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_nautilus: nautilus-extension-gnome-terminal 3.49.92-2ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2043604/+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 1729433] Re: LibreOffice doesn't remember window size when running under Wayland

[J-Paul BERARD]

With LO 7.6.2.1 and Ubuntu 23.10 (main UI) Wayland :
I create a Writer file with a medium window. I maximize the window and quit LO.
I open again the same file : the window is maximized. When I un-maximize the 
window, it doesn't come back to the medium previous size but to a more 
maximized size ! I mean, the size of the window increases again going behind 
the dock.
If I maximize again and un-maximize a second time, the window comes back to a 
medium size but not the same that the initial one.
But not the very small window we saw before.

Thanks

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

Title:
  LibreOffice doesn't remember window size when running under Wayland

Status in LibreOffice:
  Confirmed
Status in libreoffice package in Ubuntu:
  Fix Released
Status in libreoffice package in Fedora:
  Confirmed

Bug description:
  1. Open any LibreOffice document, e.g., a Writer or Calc document.
  2. Make the window a reasonable, non-maximized size.
  3. Maximize the window.
  4. Close LibreOffice.
  5. Open the document again; it will open maximized.
  6. Un-maximize the window.
  7. Observe how the window has a ridiculously small size, not its previously 
unmaximized size.

  LibreOffice or gnome-shell bug? Not sure.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: libreoffice-core 1:5.4.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Nov  1 16:21:29 2017
  InstallationDate: Installed on 2017-05-19 (166 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: libreoffice
  UpgradeStatus: Upgraded to artful on 2017-10-20 (12 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1729433/+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 1993054] Re: USB key eject does not eject

[corrado venturini]

I did some tests for this problem:
all test with include unmounted volumes = NO

test1 - click eject on files does eject
test2 - click eject on dock does NOT eject, eject must be completed with eject 
on dock
test3 - click Unmount on dock does the same as Eject

---

test1 --- click Eject on files 

at [6820.172534] click Eject on files - eject completed

corrado@corrado-n2-nn-1115:~$ sudo dmesg -W
[sudo] password for corrado: 
[ 6820.214188] evict_inodes inode 7a1f2b20, i_count = 1, was skipped!
[ 6820.214196] evict_inodes inode 4999f002, i_count = 1, was skipped!
[ 6820.214199] evict_inodes inode af46cbb1, i_count = 1, was skipped!
[ 6820.320984] sdc: detected capacity change from 3072 to 0

corrado@corrado-n2-nn-1115:~$ udevadm monitor
monitor will print the received events for:
UDEV - the event which udev sends out after rule processing
KERNEL - the kernel uevent

KERNEL[6820.172534] change   
/devices/pci:00/:00:14.0/usb1/1-14/1-14:1.0/host4/target4:0:0/4:0:0:0/block/sdc/sdc1
 (block)
UDEV  [6820.238892] change   
/devices/pci:00/:00:14.0/usb1/1-14/1-14:1.0/host4/target4:0:0/4:0:0:0/block/sdc/sdc1
 (block)
KERNEL[6820.270341] change   
/devices/pci:00/:00:14.0/usb1/1-14/1-14:1.0/host4/target4:0:0/4:0:0:0/block/sdc
 (block)
KERNEL[6820.270641] remove   
/devices/pci:00/:00:14.0/usb1/1-14/1-14:1.0/host4/target4:0:0/4:0:0:0/block/sdc/sdc1
 (block)
KERNEL[6820.271085] change   
/devices/pci:00/:00:14.0/usb1/1-14/1-14:1.0/host4/target4:0:0/4:0:0:0/block/sdc
 (block)
UDEV  [6820.272584] change   
/devices/pci:00/:00:14.0/usb1/1-14/1-14:1.0/host4/target4:0:0/4:0:0:0/block/sdc
 (block)
UDEV  [6820.273600] remove   
/devices/pci:00/:00:14.0/usb1/1-14/1-14:1.0/host4/target4:0:0/4:0:0:0/block/sdc/sdc1
 (block)
UDEV  [6820.275655] change   
/devices/pci:00/:00:14.0/usb1/1-14/1-14:1.0/host4/target4:0:0/4:0:0:0/block/sdc
 (block)

test2 --- click Eject on dock and then on files 

at [6474.305211] click Eject on dock - eject NOT done
at [6510.630651] click Eject on files - eject completed

corrado@corrado-n2-nn-1115:~$ sudo dmesg -W
[sudo] password for corrado: 
[ 6474.342504] evict_inodes inode 86a23104, i_count = 1, was skipped!
[ 6474.342508] evict_inodes inode 5caf6d28, i_count = 1, was skipped!
[ 6474.342509] evict_inodes inode a02ca119, i_count = 1, was skipped!
[ 6510.678411] sdc: detected capacity change from 3072 to 0

corrado@corrado-n2-nn-1115:~$ udevadm monitor
monitor will print the received events for:
UDEV - the event which udev sends out after rule processing
KERNEL - the kernel uevent

KERNEL[6474.305211] change   
/devices/pci:00/:00:14.0/usb1/1-14/1-14:1.0/host4/target4:0:0/4:0:0:0/block/sdc/sdc1
 (block)
UDEV  [6474.373867] change   
/devices/pci:00/:00:14.0/usb1/1-14/1-14:1.0/host4/target4:0:0/4:0:0:0/block/sdc/sdc1
 (block)
KERNEL[6510.630651] change   
/devices/pci:00/:00:14.0/usb1/1-14/1-14:1.0/host4/target4:0:0/4:0:0:0/block/sdc
 (block)
KERNEL[6510.630872] remove   
/devices/pci:00/:00:14.0/usb1/1-14/1-14:1.0/host4/target4:0:0/4:0:0:0/block/sdc/sdc1
 (block)
KERNEL[6510.632673] change   
/devices/pci:00/:00:14.0/usb1/1-14/1-14:1.0/host4/target4:0:0/4:0:0:0/block/sdc
 (block)
UDEV  [6510.634241] change   
/devices/pci:00/:00:14.0/usb1/1-14/1-14:1.0/host4/target4:0:0/4:0:0:0/block/sdc
 (block)
UDEV  [6510.635018] remove   
/devices/pci:00/:00:14.0/usb1/1-14/1-14:1.0/host4/target4:0:0/4:0:0:0/block/sdc/sdc1
 (block)
UDEV  [6510.637247] change   
/devices/pci:00/:00:14.0/usb1/1-14/1-14:1.0/host4/target4:0:0/4:0:0:0/block/sdc
 (block)

test3 --- click UNMOUNT on dock and then on files 

at [7890.424704] click Unmount on dock - eject NOT done
at [7910.393825] click Eject on files - eject completed

corrado@corrado-n2-nn-1115:~$ sudo dmesg -W
[sudo] password for corrado: 
[ 7890.475269] evict_inodes inode 3639f350, i_count = 1, was skipped!
[ 7890.475273] evict_inodes inode 9b82a3f2, i_count = 1, was skipped!
[ 7890.475275] evict_inodes inode 7dcb575b, i_count = 1, was skipped!
[ 7910.452961] sdc: detected capacity change from 3072 to 0

corrado@corrado-n2-nn-1115:~$ udevadm monitor
monitor will print the received events for:
UDEV - the event which udev sends out after rule processing
KERNEL - the kernel uevent

KERNEL[7890.424704] change   
/devices/pci:00/:00:14.0/usb1/1-14/1-14:1.0/host4/target4:0:0/4:0:0:0/block/sdc/sdc1
 (block)
UDEV  [7890.493612] change   
/devices/pci:00/:00:14.0/usb1/1-14/1-14:1.0/host4/target4:0:0/4:0:0:0/block/sdc/sdc1
 (block)
KERNEL[7910.393825] change   
/devices/pci:00/:00:14.0/usb1/1-14/1-14:1.0/host4/target4:0:0/4:0:0:0/block/sdc
 (block)
KERNEL[7910.394162] remove   
/devices/pci:00/:00:14.0/usb1/1

[Desktop-packages] [Bug 2042772] Re: [amdgpu] Display corrupted/freeze

[Launchpad Bug Tracker]

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

** Changed in: linux (Ubuntu)
   Status: New => Confirmed

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

Title:
  [amdgpu] Display corrupted/freeze

Status in linux package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  Confirmed

Bug description:
  After latest updates login display is fine but after entering password
  display changes to black with random full width 1 pixel high white
  lines that move randomly vertically.  Must power off to recover.  Boot
  in recovery mode works OK.

  Send email if you need more information.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-88.98-generic 5.15.126
  Uname: Linux 5.15.0-88-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: Sun Nov  5 07:09:04 2023
  DistUpgraded: 2022-12-21 11:25:42,433 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
  DistroCodename: jammy
  DistroVariant: ubuntu
  DpkgLog:
   
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: Continuously
  GpuHangReproducibility: Yes, I can easily reproduce it
  GpuHangStarted: Immediately after installing this version of Ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Wani [Radeon R5/R6/R7 Graphics] 
[1002:9874] (rev c9) (prog-if 00 [VGA controller])
 Subsystem: Dell Wani [Radeon R5/R6/R7 Graphics] [1028:0769]
 Subsystem: Dell Topaz XT [Radeon R7 M260/M265 / M340/M360 / M440/M445 / 
530/535 / 620/625 Mobile] [1028:0769]
  InstallationDate: Installed on 2018-08-11 (1912 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: Dell Inc. Inspiron 5565
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-88-generic 
root=UUID=54c49f2a-71f4-4c7f-b611-4f0af1922365 ro recovery nomodeset 
dis_ucode_ldr
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: Upgraded to jammy on 2022-12-21 (318 days ago)
  dmi.bios.date: 10/18/2016
  dmi.bios.release: 5.3
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.0.5
  dmi.board.name: 0021CT
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 1.0.5
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.0.5:bd10/18/2016:br5.3:svnDellInc.:pnInspiron5565:pvr1.0.5:rvnDellInc.:rn0021CT:rvrA00:cvnDellInc.:ct10:cvr1.0.5:sku0769:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5565
  dmi.product.sku: 0769
  dmi.product.version: 1.0.5
  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.0.4-0ubuntu1~22.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 23.0.4-0ubuntu1~22.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2042772/+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 2042772] Re: [amdgpu] Display corrupted/freeze

[Launchpad Bug Tracker]

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

** Changed in: mesa (Ubuntu)
   Status: New => Confirmed

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

Title:
  [amdgpu] Display corrupted/freeze

Status in linux package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  Confirmed

Bug description:
  After latest updates login display is fine but after entering password
  display changes to black with random full width 1 pixel high white
  lines that move randomly vertically.  Must power off to recover.  Boot
  in recovery mode works OK.

  Send email if you need more information.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-88.98-generic 5.15.126
  Uname: Linux 5.15.0-88-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: Sun Nov  5 07:09:04 2023
  DistUpgraded: 2022-12-21 11:25:42,433 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
  DistroCodename: jammy
  DistroVariant: ubuntu
  DpkgLog:
   
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: Continuously
  GpuHangReproducibility: Yes, I can easily reproduce it
  GpuHangStarted: Immediately after installing this version of Ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Wani [Radeon R5/R6/R7 Graphics] 
[1002:9874] (rev c9) (prog-if 00 [VGA controller])
 Subsystem: Dell Wani [Radeon R5/R6/R7 Graphics] [1028:0769]
 Subsystem: Dell Topaz XT [Radeon R7 M260/M265 / M340/M360 / M440/M445 / 
530/535 / 620/625 Mobile] [1028:0769]
  InstallationDate: Installed on 2018-08-11 (1912 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: Dell Inc. Inspiron 5565
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-88-generic 
root=UUID=54c49f2a-71f4-4c7f-b611-4f0af1922365 ro recovery nomodeset 
dis_ucode_ldr
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: Upgraded to jammy on 2022-12-21 (318 days ago)
  dmi.bios.date: 10/18/2016
  dmi.bios.release: 5.3
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.0.5
  dmi.board.name: 0021CT
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 1.0.5
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.0.5:bd10/18/2016:br5.3:svnDellInc.:pnInspiron5565:pvr1.0.5:rvnDellInc.:rn0021CT:rvrA00:cvnDellInc.:ct10:cvr1.0.5:sku0769:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5565
  dmi.product.sku: 0769
  dmi.product.version: 1.0.5
  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.0.4-0ubuntu1~22.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 23.0.4-0ubuntu1~22.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2042772/+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 2042772] Re: [amdgpu] Display corrupted/freeze

[Graeme Thorn]

I asked the askubuntu question here:
https://askubuntu.com/questions/1492364/ubuntu-22-04-3-lts-gui-does-not-
work-with-5-15-0-88-generic for the same error using 22.04.3 (jammy) on
an HP 15-db0598sa laptop, which has a AMD Radeon R4 Graphics Integrated
graphics card.

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

Title:
  [amdgpu] Display corrupted/freeze

Status in linux package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  Confirmed

Bug description:
  After latest updates login display is fine but after entering password
  display changes to black with random full width 1 pixel high white
  lines that move randomly vertically.  Must power off to recover.  Boot
  in recovery mode works OK.

  Send email if you need more information.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-88.98-generic 5.15.126
  Uname: Linux 5.15.0-88-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: Sun Nov  5 07:09:04 2023
  DistUpgraded: 2022-12-21 11:25:42,433 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
  DistroCodename: jammy
  DistroVariant: ubuntu
  DpkgLog:
   
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: Continuously
  GpuHangReproducibility: Yes, I can easily reproduce it
  GpuHangStarted: Immediately after installing this version of Ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Wani [Radeon R5/R6/R7 Graphics] 
[1002:9874] (rev c9) (prog-if 00 [VGA controller])
 Subsystem: Dell Wani [Radeon R5/R6/R7 Graphics] [1028:0769]
 Subsystem: Dell Topaz XT [Radeon R7 M260/M265 / M340/M360 / M440/M445 / 
530/535 / 620/625 Mobile] [1028:0769]
  InstallationDate: Installed on 2018-08-11 (1912 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: Dell Inc. Inspiron 5565
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-88-generic 
root=UUID=54c49f2a-71f4-4c7f-b611-4f0af1922365 ro recovery nomodeset 
dis_ucode_ldr
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: Upgraded to jammy on 2022-12-21 (318 days ago)
  dmi.bios.date: 10/18/2016
  dmi.bios.release: 5.3
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.0.5
  dmi.board.name: 0021CT
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 1.0.5
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.0.5:bd10/18/2016:br5.3:svnDellInc.:pnInspiron5565:pvr1.0.5:rvnDellInc.:rn0021CT:rvrA00:cvnDellInc.:ct10:cvr1.0.5:sku0769:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5565
  dmi.product.sku: 0769
  dmi.product.version: 1.0.5
  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.0.4-0ubuntu1~22.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 23.0.4-0ubuntu1~22.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2042772/+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 1923845] Re: Please compress packages with zstd by default

[Luca Boccassi]

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

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

Title:
  Please compress packages with zstd by default

Status in appstream-glib package in Ubuntu:
  New
Status in apt package in Ubuntu:
  Fix Released
Status in aptly package in Ubuntu:
  Fix Released
Status in boinc package in Ubuntu:
  New
Status in busybox package in Ubuntu:
  New
Status in cdebootstrap package in Ubuntu:
  New
Status in cdist package in Ubuntu:
  New
Status in debdelta package in Ubuntu:
  New
Status in debian-el package in Ubuntu:
  New
Status in debootstrap package in Ubuntu:
  Fix Released
Status in debsig-verify package in Ubuntu:
  New
Status in debsigs package in Ubuntu:
  New
Status in diffoscope package in Ubuntu:
  Fix Released
Status in dpkg package in Ubuntu:
  Fix Released
Status in dpkg-sig package in Ubuntu:
  New
Status in file package in Ubuntu:
  New
Status in hello package in Ubuntu:
  Fix Released
Status in libsolv package in Ubuntu:
  Fix Released
Status in lintian package in Ubuntu:
  Fix Released
Status in lutris package in Ubuntu:
  Invalid
Status in obs-build package in Ubuntu:
  New
Status in osc package in Ubuntu:
  New
Status in python-debian package in Ubuntu:
  Fix Released
Status in radare2 package in Ubuntu:
  New
Status in reprepro package in Ubuntu:
  Fix Released
Status in vim-scripts package in Ubuntu:
  New
Status in zeroinstall-injector package in Ubuntu:
  New
Status in reprepro source package in Focal:
  Fix Released
Status in reprepro source package in Groovy:
  Fix Released
Status in reprepro source package in Hirsute:
  Fix Released
Status in debian-el package in Debian:
  New

Bug description:
  https://people.canonical.com/~rbalint/zstd-debs/ contains a .deb built
  on Hirsute having both data and control members of the .deb being
  compressed with zstd. It can be handy for testing various tools.

  [dpkg]
  Decompression support in dpkg landed first in Bionic and is being SRUd to 
Xenial in LP: #1764220 enable Launchpad's Xenial systems to process the 
zstd-compressed binary packages.
  From dpkg's perspective the upgrade path is cleared.

  The original plan was compressing only the internal data.tar .deb
  member, but dpkg uses uniform compression by default since dpkg 1.19.0
  thus I'm collecting all the changes to support control.tar.zst, too,
  in this bug.

  Reviewed packages from:
  https://codesearch.debian.net/search?q=data.tar.xz&literal=1&perpkg=1
  https://codesearch.debian.net/search?q=control.tar.xz&literal=1&perpkg=1

  appstream-glib  - needs fix: libappstream-builder/asb-package-deb.c
  aptly   - needs fix: deb/deb.go
  boinc   - needs fix: debian/fetch_example_applications.sh
  busybox - needs fix: archival/dpkg_deb.c archival/dpkg.c
  cdebootstrap- needs fix: src/package.c
  cdist   - may need fix, can use dpkg-deb: 
cdist/preos/debootstrap/files/devuan-debootstrap/functions
  debdelta- needs fix: debdelta debpatch.sh
  debian-el   - needs fix: deb-view.el
  debian-handbook - needs fix, maybe later, for Debian
  debootstrap - needs fix, 
https://salsa.debian.org/installer-team/debootstrap/-/merge_requests/54
  debsigs - needs fix, debsigs
  debsig-verify   - needs fix, src/debsig-verify.c
  diffoscope  - needs fix, diffoscope/comparators/deb.py
  dpkg- needs fix, change default
  dpkg-sig- needs fix, dpkg-sig
  dpmb- needs fix, maybe later, for Debian
  elfutils- may need fix, uses dpkg-deb if it is available, does not 
handle .gz either
  file- needs fix, magic/Magdir/archive
  libsolv - needs fix, ext/repo_deb.c
  lintian - needs fix malformed-deb-archive
  lutris  - needs fix, lutris/util/extract.py
  obs-build   - needs fix Build/Deb.pm
  osc - needs fix osc/util/debquery.py control.tar.zst only
  python-apt  - needs fix 
apt_inst.DebFile("glibc-doc-reference_2.33-0ubuntu2~zstd1_all.deb").control.extractall()
  radare2 - needs fix
  reprepro- needs fix, debfile.c
  vim-scripts - needs fix debPlugin/autoload/deb.vim
  winetricks  - needs fix when Debian switches src/winetricks
  zeroinstall-injector - needs fix src/zeroinstall/archive.ml

  acr - skip, does not _have to_ be fixed, just creates packages, 
see dist/deb_hand.mak
  alien   - skip, uses dpkg-deb to extract .deb
  ansible - not affected, just test data in dbdata.tar.xz
  anthy   - not affected, just changelog entry
  apt - seems fixed already
  ceph- not affected in Ubuntu's version
  circlator   - not affected, just test data
  cowdancer   - not affected, just documentation
  eccodes - skip, just orig-data.tar.xz
  eckit   - skip, just ...orig-dat

[Desktop-packages] [Bug 2007702] Re: Deb version numbering is misleading

[Launchpad Bug Tracker]

This bug was fixed in the package chromium-browser - 2:1snap1-0ubuntu1

---
chromium-browser (2:1snap1-0ubuntu1) noble; urgency=low

  * Modify the version scheme of the package (LP: #2007702). Epoch bumped to 2.
Since this is a package that install the Chromium snap, there is no point in
updating it just for the sake of the version number whenever there is a new
Chromium release. On the other hand, we don't want to leave it stuck in a
number such as 85 because it misleads users into believing the package will
install Chromium 85, which would be severily outdated.

 -- Nathan Pratta Teodosio   Mon, 13 Nov
2023 10:20:10 +0100

** Changed in: chromium-browser (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  Deb version numbering is misleading

Status in chromium-browser package in Ubuntu:
  Fix Released

Bug description:
  For Ubuntu >= Focal the transitional debs are frozen at the version
  number 1:85...

  This might make one think[1][2] that it will install a critically
  outdated Chromium while it does not, because it installs the snap.

  [1] 
https://answers.launchpad.net/ubuntu/+source/chromium-browser/+question/702591
  [2] https://askubuntu.com/q/1420925

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2007702/+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 2041716] Re: [SRU] libreoffice 7.5.8 for lunar

[Timo Aaltonen]

Hello Rico, or anyone else affected,

Accepted libreoffice into lunar-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/libreoffice/4:7.5.8-0ubuntu0.23.04.1
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-
lunar to verification-done-lunar. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-lunar. 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.

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

** Tags added: verification-needed verification-needed-lunar

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

Title:
  [SRU] libreoffice 7.5.8 for lunar

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

Bug description:
  [Impact]

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

   * Version 7.5.5 is currently released in lunar. For a list of fixed bugs 
compared to 7.5.7 see the list of bugs fixed in the release candidates of 7.5.8 
(that's a total of 21 bugs):
   https://wiki.documentfoundation.org/Releases/7.5.8/RC1#List_of_fixed_bugs
   https://wiki.documentfoundation.org/Releases/7.5.8/RC2#List_of_fixed_bugs

   7.5.8 RC2 is identical to the 7.5.8 release

   * Given the nature of the project, the complexity of the codebase and
  the high level of quality assurance upstream, it is preferable to SRU
  a minor release rather than cherry-pick selected bug fixes.

  [Testing]

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

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

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

   * Launchpad testing. The libreoffice packages include autopkgtests that were 
run and verified as passing.
  Tested build can be found at 
https://launchpad.net/~ricotz/+archive/ubuntu/ppa/+sourcepub/15348703/+listing-archive-extra
  * [amd64] 
https://autopkgtest.ubuntu.com/results/autopkgtest-lunar-ricotz-ppa/lunar/amd64/libr/libreoffice/20231029_113409_73daf@/log.gz
  * [arm64] 
https://autopkgtest.ubuntu.com/results/autopkgtest-lunar-ricotz-ppa/lunar/arm64/libr/libreoffice/20231029_195903_c198a@/log.gz
  * [armhf] 
https://autopkgtest.ubuntu.com/results/autopkgtest-lunar-ricotz-ppa/lunar/armhf/libr/libreoffice/20231029_204848_b6986@/log.gz
  * [ppc64el] 
https://autopkgtest.ubuntu.com/results/autopkgtest-lunar-ricotz-ppa/lunar/ppc64el/libr/libreoffice/20231029_113020_49f1b@/log.gz
  * [riscv64] not available
  * [s390x] 
https://autopkgtest.ubuntu.com/results/autopkgtest-lunar-ricotz-ppa/lunar/s390x/libr/libreoffice/20231029_131951_9ac3d@/log.gz
   * General smoke testing of all the applications in the office suite were 
carried out by going through the manual testplan as documented by: 
https://wiki.ubuntu.com/Process/Merges/TestPlans/libreoffice

  [Regression Potential]

   * A minor release with a total of 21 bug fixes always carries the
  potential for introducing regressions, even though it is a bugfix-only
  release, meaning that no new features were added, and no existing
  features were removed.

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

To manage notifications about this bug go to:
https://b

[Desktop-packages] [Bug 2007702] Re: Deb version numbering is misleading

[Nathan Teodosio]

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

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

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

** Changed in: chromium-browser (Ubuntu Focal)
   Importance: Undecided => Low

** Changed in: chromium-browser (Ubuntu Jammy)
   Importance: Undecided => Low

** Changed in: chromium-browser (Ubuntu Mantic)
   Importance: Undecided => Low

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

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

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

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

Title:
  Deb version numbering is misleading

Status in chromium-browser package in Ubuntu:
  Fix Released
Status in chromium-browser source package in Focal:
  New
Status in chromium-browser source package in Jammy:
  New
Status in chromium-browser source package in Mantic:
  New

Bug description:
  For Ubuntu >= Focal the transitional debs are frozen at the version
  number 1:85...

  This might make one think[1][2] that it will install a critically
  outdated Chromium while it does not, because it installs the snap.

  [1] 
https://answers.launchpad.net/ubuntu/+source/chromium-browser/+question/702591
  [2] https://askubuntu.com/q/1420925

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2007702/+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 1794064] Re: Clicking a hyperlink in a PDF fails to open it if the default browser is a snap

[Timo Aaltonen]

Hello Olivier, or anyone else affected,

Accepted evince into jammy-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/evince/42.3-0ubuntu3.1
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.

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

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

Title:
  Clicking a hyperlink in a PDF fails to open it if the default browser
  is a snap

Status in apparmor package in Ubuntu:
  Fix Released
Status in evince package in Ubuntu:
  Fix Released
Status in apparmor source package in Jammy:
  Fix Committed
Status in evince source package in Jammy:
  Fix Committed
Status in apparmor source package in Lunar:
  Fix Released
Status in evince source package in Lunar:
  Fix Released
Status in apparmor package in Debian:
  Fix Released
Status in evince package in Debian:
  Confirmed

Bug description:
  [Impact]

   * Users cannot open a hyperlink in a PDF opened with evince when the default 
browser is a snap.
   * The fix creates a snap_browsers abstraction on AppArmor which can be used 
in a transition for when the browser is executed. The snap_browsers abstraction 
provides the minimal amount of permissions required to execute a browser 
provided through snaps. This is a workaround since AppArmor currently does not 
provide mediation/filtering on enhanced environment variables.

  [Test Plan]

   * Make sure the default browser is provided through the snap store.
   * Open a PDF that contains a hyperlink using evince and click on the URL.
   * The browser should open the requested URL. 

  [Where problems could occur]

   * If the browser or snap core update to have new requirements for
  opening a browser, then the current policy could become obsolete and
  will need to be updated again.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1794064/+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 1794064] Autopkgtest regression report (evince/42.3-0ubuntu3.1)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted evince (42.3-0ubuntu3.1) for jammy have 
finished running.
The following regressions have been reported in tests triggered by the package:

apparmor/3.0.4-2ubuntu2.2 (amd64, arm64, armhf, ppc64el, s390x)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/jammy/update_excuses.html#evince

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  Clicking a hyperlink in a PDF fails to open it if the default browser
  is a snap

Status in apparmor package in Ubuntu:
  Fix Released
Status in evince package in Ubuntu:
  Fix Released
Status in apparmor source package in Jammy:
  Fix Committed
Status in evince source package in Jammy:
  Fix Committed
Status in apparmor source package in Lunar:
  Fix Released
Status in evince source package in Lunar:
  Fix Released
Status in apparmor package in Debian:
  Fix Released
Status in evince package in Debian:
  Confirmed

Bug description:
  [Impact]

   * Users cannot open a hyperlink in a PDF opened with evince when the default 
browser is a snap.
   * The fix creates a snap_browsers abstraction on AppArmor which can be used 
in a transition for when the browser is executed. The snap_browsers abstraction 
provides the minimal amount of permissions required to execute a browser 
provided through snaps. This is a workaround since AppArmor currently does not 
provide mediation/filtering on enhanced environment variables.

  [Test Plan]

   * Make sure the default browser is provided through the snap store.
   * Open a PDF that contains a hyperlink using evince and click on the URL.
   * The browser should open the requested URL. 

  [Where problems could occur]

   * If the browser or snap core update to have new requirements for
  opening a browser, then the current policy could become obsolete and
  will need to be updated again.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1794064/+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 2043640] Re: amdgpu: GPU Recovery fails, frequent hangs

[Mario Limonciello]

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

** Package changed: mutter (Ubuntu) => mesa (Ubuntu)

** Also affects: mesa (Ubuntu Lunar)
   Importance: Undecided
   Status: New

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

** Also affects: mesa (Ubuntu Jammy)
   Importance: Undecided
   Status: New

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

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

** Changed in: linux (Ubuntu)
   Status: New => Won't Fix

** Changed in: linux (Ubuntu Jammy)
   Status: New => Won't Fix

** Changed in: linux (Ubuntu Lunar)
   Status: New => Won't Fix

** Also affects: mesa via
   https://gitlab.freedesktop.org/drm/amd/-/issues/2971
   Importance: Unknown
   Status: Unknown

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

Title:
  amdgpu: GPU Recovery fails, frequent hangs

Status in Mesa:
  Unknown
Status in linux package in Ubuntu:
  Won't Fix
Status in mesa package in Ubuntu:
  Fix Released
Status in linux source package in Jammy:
  Won't Fix
Status in mesa source package in Jammy:
  New
Status in linux source package in Lunar:
  Won't Fix
Status in mesa source package in Lunar:
  New

Bug description:
  I've been using 23.04 for a few months, and experienced a total system
  hang occasionally when sharing my screen over Zoom or Google Meet
  (running on Google Chrome).

  At first it hangs and then it periodically flashes like it's trying
  (unsuccessfully) to recover; I've got 3 screens (including the
  laptop's internal one) and each attempt shows something different (at
  first it tries to recover the contents of all 3 screens, then it shows
  only one of them, and then it shows the same content on all 3, but it
  never gets responsive).

  I've recently upgraded to 23.10, hoping a new kernel would help the
  situation. It's only gotten considerably worse now; it hangs sometimes
  just when opening Zoom; it's somehow easier to reproduce with Google
  Chrome. Interestingly, it fails quickly and reliably now when enabling
  my webcam (with special effects). It started hanging badly when using
  Google Maps as well.

  For all these behaviors, I suspect amdgpu is to blame (I'm running on
  Renoir, 4750U Pro); `dmesg` and `journalctl` didn't seem to show
  anything interesting.

  Any tips about debugging this further?

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: linux-generic 6.5.0.10.12
  ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
  Uname: Linux 6.5.0-10-generic x86_64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: GNOME
  Date: Thu Nov 16 02:27:45 2023
  InstallationDate: Installed on 2023-07-02 (137 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=
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-10-generic 
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-6.5.0-10-generic N/A
   linux-backports-modules-6.5.0-10-generic  N/A
   linux-firmware20230919.git3672ccab-0ubuntu2.1
  SourcePackage: linux
  UpgradeStatus: Upgraded to mantic on 2023-11-14 (2 days ago)
  dmi.bios.date: 06/13/2023
  dmi.bios.release: 1.44
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R1BET75W(1.44 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20UD000GUS
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.44
  dmi.modalias: 
dmi:bvnLENOVO:bvrR1BET75W(1.44):bd06/13/2023:br1.44:efr1.44:svnLENOVO:pn20UD000GUS:pvrThinkPadT14Gen1:rvnLENOVO:rn20UD000GUS:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20UD_BU_Think_FM_ThinkPadT14Gen1:
  dmi.product.family: ThinkPad T14 Gen 1
  dmi.product.name: 20UD000GUS
  dmi.product.sku: LENOVO_MT_20UD_BU_Think_FM_ThinkPad T14 Gen 1
  dmi.product.version: ThinkPad T14 Gen 1
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/mesa/+bug/2043640/+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 1973084] Re: transmission-daemon high RAM usage

[Andreas Hasenack]

** Description changed:

- Transmission uses a lot of RAM in ubuntu 22.04 server (arm64) runnign on
- a Raspberry Pi 4.
+ [ Impact ]
+ 
+ There is a memory leak in transmission-daemon that was introduced by a
+ faulty openssl3 patch. It has been reported that it's noticeable after a
+ few hours of seeding/downloading torrent files, less than a day.
+ 
+ 
+ [ Test Plan ]
+ 
+ Being a memory leak, there is no immediate/quick test that can be
+ performed, other than letting it run for a few hours and measure memory
+ consumption "before" and "after". comment #5 mentions about 1Gb of RAM
+ after 18h of runtime. #comment 14 mentions 12Gb of RAM, but not for how
+ long it was running.
+ 
+ I'd suggest a 24h test and that it should stay under 1Gb of RAM.
+ 
+ [ Where problems could occur ]
+ 
+ The patch loads the default and legacy openssl3 providers. This will
+ potentially change the set of algorithms available to the application,
+ compared to what was there before. That being said, the legacy provider
+ is a conservative approach, and the likely result is that *more*
+ algorithms will become available, and not less. This is also the
+ approach I have seen in other applications that were rebuilt using
+ openssl3 instead of openssl1.1.
+ 
+ It does seem safer than the original patch, which was manually handling
+ ciphers, in particular RC4, and, well, introduced the memory leak.
+ 
+ 
+ [ Other Info ]
+  
+ Patch came from gentoo.
+ 
+ 
+ [ Original Description ]
+ Transmission uses a lot of RAM in ubuntu 22.04 server (arm64) runnign on a 
Raspberry Pi 4.
  
  It "eats" RAM and the RAM usage grows each hour until it crashes the
  system.
  
  I sideloaded transmission-daemon and its dependancies from debian 11
  (arm64) locked the packages so apt won't update them and, ever since,
  this issue hasn't happened.
  
- 
  Description:Ubuntu 22.04 LTS
  Release:22.04

** Description changed:

  [ Impact ]
  
  There is a memory leak in transmission-daemon that was introduced by a
  faulty openssl3 patch. It has been reported that it's noticeable after a
  few hours of seeding/downloading torrent files, less than a day.
- 
  
  [ Test Plan ]
  
  Being a memory leak, there is no immediate/quick test that can be
  performed, other than letting it run for a few hours and measure memory
  consumption "before" and "after". comment #5 mentions about 1Gb of RAM
  after 18h of runtime. #comment 14 mentions 12Gb of RAM, but not for how
  long it was running.
+ 
+ comment #20 says that after 24h using the patched version from a PPA
+ build, the memory consumption was steady at 300Mb.
  
  I'd suggest a 24h test and that it should stay under 1Gb of RAM.
  
  [ Where problems could occur ]
  
  The patch loads the default and legacy openssl3 providers. This will
  potentially change the set of algorithms available to the application,
  compared to what was there before. That being said, the legacy provider
  is a conservative approach, and the likely result is that *more*
  algorithms will become available, and not less. This is also the
  approach I have seen in other applications that were rebuilt using
  openssl3 instead of openssl1.1.
  
  It does seem safer than the original patch, which was manually handling
  ciphers, in particular RC4, and, well, introduced the memory leak.
  
+ [ Other Info ]
  
- [ Other Info ]
-  
  Patch came from gentoo.
- 
  
  [ Original Description ]
  Transmission uses a lot of RAM in ubuntu 22.04 server (arm64) runnign on a 
Raspberry Pi 4.
  
  It "eats" RAM and the RAM usage grows each hour until it crashes the
  system.
  
  I sideloaded transmission-daemon and its dependancies from debian 11
  (arm64) locked the packages so apt won't update them and, ever since,
  this issue hasn't happened.
  
  Description:Ubuntu 22.04 LTS
  Release:22.04

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

Title:
  transmission-daemon high RAM usage

Status in transmission package in Ubuntu:
  Confirmed
Status in transmission source package in Jammy:
  New
Status in transmission source package in Lunar:
  New
Status in transmission package in Debian:
  New

Bug description:
  [ Impact ]

  There is a memory leak in transmission-daemon that was introduced by a
  faulty openssl3 patch. It has been reported that it's noticeable after
  a few hours of seeding/downloading torrent files, less than a day.

  [ Test Plan ]

  Being a memory leak, there is no immediate/quick test that can be
  performed, other than letting it run for a few hours and measure
  memory consumption "before" and "after". comment #5 mentions about 1Gb
  of RAM after 18h of runtime. #comment 14 mentions 12Gb of RAM, but not
  for how long it was running.

  comment #20 says that after 24h using the patched version from a PPA
  build, the memory consumption was steady at 300Mb.

  I'd suggest 

[Desktop-packages] [Bug 1973084] Re: transmission-daemon high RAM usage

[Andreas Hasenack]

Sponsored for jammy and lunar. Mantic has 4.0 which is not affected.

Unsubscribing sponsors.

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

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

Title:
  transmission-daemon high RAM usage

Status in transmission package in Ubuntu:
  Fix Released
Status in transmission source package in Jammy:
  New
Status in transmission source package in Lunar:
  New
Status in transmission package in Debian:
  New

Bug description:
  [ Impact ]

  There is a memory leak in transmission-daemon that was introduced by a
  faulty openssl3 patch. It has been reported that it's noticeable after
  a few hours of seeding/downloading torrent files, less than a day.

  [ Test Plan ]

  Being a memory leak, there is no immediate/quick test that can be
  performed, other than letting it run for a few hours and measure
  memory consumption "before" and "after". comment #5 mentions about 1Gb
  of RAM after 18h of runtime. #comment 14 mentions 12Gb of RAM, but not
  for how long it was running.

  comment #20 says that after 24h using the patched version from a PPA
  build, the memory consumption was steady at 300Mb.

  I'd suggest a 24h test and that it should stay under 1Gb of RAM.

  [ Where problems could occur ]

  The patch loads the default and legacy openssl3 providers. This will
  potentially change the set of algorithms available to the application,
  compared to what was there before. That being said, the legacy
  provider is a conservative approach, and the likely result is that
  *more* algorithms will become available, and not less. This is also
  the approach I have seen in other applications that were rebuilt using
  openssl3 instead of openssl1.1.

  It does seem safer than the original patch, which was manually
  handling ciphers, in particular RC4, and, well, introduced the memory
  leak.

  [ Other Info ]

  Patch came from gentoo.

  [ Original Description ]
  Transmission uses a lot of RAM in ubuntu 22.04 server (arm64) runnign on a 
Raspberry Pi 4.

  It "eats" RAM and the RAM usage grows each hour until it crashes the
  system.

  I sideloaded transmission-daemon and its dependancies from debian 11
  (arm64) locked the packages so apt won't update them and, ever since,
  this issue hasn't happened.

  Description:Ubuntu 22.04 LTS
  Release:22.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/transmission/+bug/1973084/+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 2042394] Re: Support goodix fingerprint [27c6:6582]

[Andreas Hasenack]

Marking as incomplete pending the completion of what was requested in
comment #2 above. I also added tasks for the missing ubuntu releases.

** Also affects: libfprint (Ubuntu Jammy)
   Importance: Undecided
   Status: New

** Also affects: libfprint (Ubuntu Noble)
   Importance: High
   Status: New

** Also affects: libfprint (Ubuntu Mantic)
   Importance: Undecided
   Status: New

** Also affects: libfprint (Ubuntu Lunar)
   Importance: Undecided
   Status: New

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

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

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

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

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

** Changed in: libfprint (Ubuntu Jammy)
   Status: New => Triaged

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

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

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

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

Title:
  Support goodix fingerprint [27c6:6582]

Status in OEM Priority Project:
  Triaged
Status in libfprint package in Ubuntu:
  Incomplete
Status in libfprint source package in Jammy:
  Triaged
Status in libfprint source package in Lunar:
  Incomplete
Status in libfprint source package in Mantic:
  Incomplete
Status in libfprint source package in Noble:
  Incomplete

Bug description:
  [27c6:6582] include in
  https://gitlab.freedesktop.org/libfprint/libfprint/-/merge_requests/447

  [Impact]

   * Support goodix [27c6:6582] fingerprint component.

  [Test Plan]

   * Find a machine with this fingerprint device

   * Launch `settings` and enable `Fingerprint Login`

   * Enroll finger and then logout

   * Login system with enrolled finger

  [Where problems could occur]

   * The patch add new ids to id_table. Should not affect previous
  supported device.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/2042394/+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 2043640] Re: amdgpu: GPU Recovery fails, frequent hangs

[Mario Limonciello]

I've published a PPA here:
https://launchpad.net/~superm1/+archive/ubuntu/gitlab2971/+packages

This has builds both for 22.04 (Jammy) and 23.04 (Lunar).  Please
upgrade to that, drop the module parameter and see if things improve.

# sudo add-apt-repository ppa:superm1/gitlab2971
# sudo apt upgrade
# sudo reboot

If they don't, you can remove the PPA using ppa-purge like this:

# sudo ppa-purge ppa:superm1/gitlab2971
# sudo reboot

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

Title:
  amdgpu: GPU Recovery fails, frequent hangs

Status in Mesa:
  Unknown
Status in linux package in Ubuntu:
  Won't Fix
Status in mesa package in Ubuntu:
  Fix Released
Status in linux source package in Jammy:
  Won't Fix
Status in mesa source package in Jammy:
  New
Status in linux source package in Lunar:
  Won't Fix
Status in mesa source package in Lunar:
  New

Bug description:
  I've been using 23.04 for a few months, and experienced a total system
  hang occasionally when sharing my screen over Zoom or Google Meet
  (running on Google Chrome).

  At first it hangs and then it periodically flashes like it's trying
  (unsuccessfully) to recover; I've got 3 screens (including the
  laptop's internal one) and each attempt shows something different (at
  first it tries to recover the contents of all 3 screens, then it shows
  only one of them, and then it shows the same content on all 3, but it
  never gets responsive).

  I've recently upgraded to 23.10, hoping a new kernel would help the
  situation. It's only gotten considerably worse now; it hangs sometimes
  just when opening Zoom; it's somehow easier to reproduce with Google
  Chrome. Interestingly, it fails quickly and reliably now when enabling
  my webcam (with special effects). It started hanging badly when using
  Google Maps as well.

  For all these behaviors, I suspect amdgpu is to blame (I'm running on
  Renoir, 4750U Pro); `dmesg` and `journalctl` didn't seem to show
  anything interesting.

  Any tips about debugging this further?

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: linux-generic 6.5.0.10.12
  ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
  Uname: Linux 6.5.0-10-generic x86_64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: GNOME
  Date: Thu Nov 16 02:27:45 2023
  InstallationDate: Installed on 2023-07-02 (137 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=
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-10-generic 
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-6.5.0-10-generic N/A
   linux-backports-modules-6.5.0-10-generic  N/A
   linux-firmware20230919.git3672ccab-0ubuntu2.1
  SourcePackage: linux
  UpgradeStatus: Upgraded to mantic on 2023-11-14 (2 days ago)
  dmi.bios.date: 06/13/2023
  dmi.bios.release: 1.44
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R1BET75W(1.44 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20UD000GUS
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.44
  dmi.modalias: 
dmi:bvnLENOVO:bvrR1BET75W(1.44):bd06/13/2023:br1.44:efr1.44:svnLENOVO:pn20UD000GUS:pvrThinkPadT14Gen1:rvnLENOVO:rn20UD000GUS:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20UD_BU_Think_FM_ThinkPadT14Gen1:
  dmi.product.family: ThinkPad T14 Gen 1
  dmi.product.name: 20UD000GUS
  dmi.product.sku: LENOVO_MT_20UD_BU_Think_FM_ThinkPad T14 Gen 1
  dmi.product.version: ThinkPad T14 Gen 1
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/mesa/+bug/2043640/+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 2043640] Re: amdgpu: GPU Recovery fails, frequent hangs

[Bug Watch Updater]

** Changed in: mesa
   Status: Unknown => New

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

Title:
  amdgpu: GPU Recovery fails, frequent hangs

Status in Mesa:
  New
Status in linux package in Ubuntu:
  Won't Fix
Status in mesa package in Ubuntu:
  Fix Released
Status in linux source package in Jammy:
  Won't Fix
Status in mesa source package in Jammy:
  New
Status in linux source package in Lunar:
  Won't Fix
Status in mesa source package in Lunar:
  New

Bug description:
  I've been using 23.04 for a few months, and experienced a total system
  hang occasionally when sharing my screen over Zoom or Google Meet
  (running on Google Chrome).

  At first it hangs and then it periodically flashes like it's trying
  (unsuccessfully) to recover; I've got 3 screens (including the
  laptop's internal one) and each attempt shows something different (at
  first it tries to recover the contents of all 3 screens, then it shows
  only one of them, and then it shows the same content on all 3, but it
  never gets responsive).

  I've recently upgraded to 23.10, hoping a new kernel would help the
  situation. It's only gotten considerably worse now; it hangs sometimes
  just when opening Zoom; it's somehow easier to reproduce with Google
  Chrome. Interestingly, it fails quickly and reliably now when enabling
  my webcam (with special effects). It started hanging badly when using
  Google Maps as well.

  For all these behaviors, I suspect amdgpu is to blame (I'm running on
  Renoir, 4750U Pro); `dmesg` and `journalctl` didn't seem to show
  anything interesting.

  Any tips about debugging this further?

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: linux-generic 6.5.0.10.12
  ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
  Uname: Linux 6.5.0-10-generic x86_64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: GNOME
  Date: Thu Nov 16 02:27:45 2023
  InstallationDate: Installed on 2023-07-02 (137 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=
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-10-generic 
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-6.5.0-10-generic N/A
   linux-backports-modules-6.5.0-10-generic  N/A
   linux-firmware20230919.git3672ccab-0ubuntu2.1
  SourcePackage: linux
  UpgradeStatus: Upgraded to mantic on 2023-11-14 (2 days ago)
  dmi.bios.date: 06/13/2023
  dmi.bios.release: 1.44
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R1BET75W(1.44 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20UD000GUS
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.44
  dmi.modalias: 
dmi:bvnLENOVO:bvrR1BET75W(1.44):bd06/13/2023:br1.44:efr1.44:svnLENOVO:pn20UD000GUS:pvrThinkPadT14Gen1:rvnLENOVO:rn20UD000GUS:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20UD_BU_Think_FM_ThinkPadT14Gen1:
  dmi.product.family: ThinkPad T14 Gen 1
  dmi.product.name: 20UD000GUS
  dmi.product.sku: LENOVO_MT_20UD_BU_Think_FM_ThinkPad T14 Gen 1
  dmi.product.version: ThinkPad T14 Gen 1
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/mesa/+bug/2043640/+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 2020078] Re: firefox-snap causes system-wide freeze

[Launchpad Bug Tracker]

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

** Changed in: firefox (Ubuntu)
   Status: New => Confirmed

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

Title:
  firefox-snap causes system-wide freeze

Status in firefox package in Ubuntu:
  Confirmed

Bug description:
  May 18 10:03:02 jonsmith kernel: [  290.566068] ACPI Error: Aborting method 
\_SB.PCI0.PEG0.PEGP.BRT6 due to previous error (AE_NOT_FOUND) 
(20220331/psparse-529)
  May 18 10:03:02 jonsmith kernel: [  290.566228] ACPI Error: Aborting method 
\EV5 due to previous error (AE_NOT_FOUND) (20220331/psparse-529)
  May 18 10:03:02 jonsmith kernel: [  290.566389] ACPI Error: Aborting method 
\SMEE due to previous error (AE_NOT_FOUND) (20220331/psparse-529)
  May 18 10:03:02 jonsmith kernel: [  290.566550] ACPI Error: Aborting method 
\SMIE due to previous error (AE_NOT_FOUND) (20220331/psparse-529)
  May 18 10:03:02 jonsmith kernel: [  290.566708] ACPI Error: Aborting method 
\NEVT due to previous error (AE_NOT_FOUND) (20220331/psparse-529)
  May 18 10:03:02 jonsmith kernel: [  290.566899] ACPI Error: Aborting method 
\_SB.PCI0.LPCB.ECDV._Q66 due to previous error (AE_NOT_FOUND) 
(20220331/psparse-529)
  May 18 10:03:02 jonsmith kernel: [  290.694431] ACPI BIOS Error (bug): Could 
not resolve symbol [\_SB.PCI0.PEG0.PEGP.BRT6.LCD], AE_NOT_FOUND 
(20220331/psargs-330)
  May 18 10:03:02 jonsmith kernel: [  290.694455] 
  May 18 10:03:02 jonsmith kernel: [  290.694458] No Local Variables are 
initialized for Method [BRT6]
  May 18 10:03:02 jonsmith kernel: [  290.694460] 
  May 18 10:03:02 jonsmith kernel: [  290.694463] Initialized Arguments for 
Method [BRT6]:  (2 arguments defined for method invocation)
  May 18 10:03:02 jonsmith kernel: [  290.694465]   Arg0:   409b1dbf 
   Integer 0001
  May 18 10:03:02 jonsmith kernel: [  290.694477]   Arg1:   ad7ffa02 
   Integer 
  May 18 10:03:02 jonsmith kernel: [  290.694486] 
  May 18 10:03:02 jonsmith kernel: [  290.694490] ACPI Error: Aborting method 
\_SB.PCI0.PEG0.PEGP.BRT6 due to previous error (AE_NOT_FOUND) 
(20220331/psparse-529)
  May 18 10:03:02 jonsmith kernel: [  290.694650] ACPI Error: Aborting method 
\EV5 due to previous error (AE_NOT_FOUND) (20220331/psparse-529)
  May 18 10:03:02 jonsmith kernel: [  290.694810] ACPI Error: Aborting method 
\SMEE due to previous error (AE_NOT_FOUND) (20220331/psparse-529)
  May 18 10:03:02 jonsmith kernel: [  290.695006] ACPI Error: Aborting method 
\SMIE due to previous error (AE_NOT_FOUND) (20220331/psparse-529)
  May 18 10:03:02 jonsmith kernel: [  290.695174] ACPI Error: Aborting method 
\NEVT due to previous error (AE_NOT_FOUND) (20220331/psparse-529)
  May 18 10:03:02 jonsmith kernel: [  290.695348] ACPI Error: Aborting method 
\_SB.PCI0.LPCB.ECDV._Q66 due to previous error (AE_NOT_FOUND) 
(20220331/psparse-529)
  May 18 10:03:03 jonsmith kernel: [  291.373091] audit: type=1107 
audit(1684384383.334:60): pid=1089 uid=102 auid=4294967295 ses=4294967295 
subj=unconfined msg='apparmor="DENIED" operation="dbus_method_call"  
bus="system" path="/org/freedesktop/PolicyKit1/Authority" 
interface="org.freedesktop.DBus.Properties" member="GetAll" mask="send" 
name=":1.9" pid=2650 label="snap.snap-store.ubuntu-software" peer_pid= 
peer_label="unconfined"
  May 18 10:03:03 jonsmith kernel: [  291.373091]  exe="/usr/bin/dbus-daemon" 
sauid=102 hostname=? addr=? terminal=?'
  May 18 10:03:03 jonsmith kernel: [  291.373813] audit: type=1107 
audit(1684384383.334:61): pid=1089 uid=102 auid=4294967295 ses=4294967295 
subj=unconfined msg='apparmor="DENIED" operation="dbus_method_call"  
bus="system" path="/org/freedesktop/PolicyKit1/Authority" 
interface="org.freedesktop.PolicyKit1.Authority" member="CheckAuthorization" 
mask="send" name=":1.9" pid=2650 label="snap.snap-store.ubuntu-software" 
peer_pid= peer_label="unconfined"
  May 18 10:03:03 jonsmith kernel: [  291.373813]  exe="/usr/bin/dbus-daemon" 
sauid=102 hostname=? addr=? terminal=?'
  May 18 10:03:03 jonsmith kernel: [  291.377907] audit: type=1107 
audit(1684384383.338:62): pid=1089 uid=102 auid=4294967295 ses=4294967295 
subj=unconfined msg='apparmor="DENIED" operation="dbus_method_call"  
bus="system" path="/org/freedesktop/PolicyKit1/Authority" 
interface="org.freedesktop.DBus.Properties" member="GetAll" mask="send" 
name=":1.9" pid=2650 label="snap.snap-store.ubuntu-software" peer_pid= 
peer_label="unconfined"
  May 18 10:03:03 jonsmith kernel: [  291.377907]  exe="/usr/bin/dbus-daemon" 
sauid=102 hostname=? addr=? terminal=?'
  May 18 10:03:03 jonsmith kernel: [  291.378569] audit: type=1107 
audit(1684384383.338:63): pid=1089 uid=102 auid=4294967295 ses=4294967295 
subj=unconfined msg='apparmor="DENIED" operation="dbus_method_call"  
bus="system" path="/org/freedesktop/PolicyKit1/Aut

[Desktop-packages] [Bug 1729433]

[Stephane-guillou-i]

Thank you Koen!
Let's mark as a duplicate of bug 125543 then.
However, if Jeff, Jan or Olivier can still reproduce, please provide steps and 
version information.

*** This bug has been marked as a duplicate of bug 125543 ***

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

Title:
  LibreOffice doesn't remember window size when running under Wayland

Status in LibreOffice:
  Invalid
Status in libreoffice package in Ubuntu:
  Fix Released
Status in libreoffice package in Fedora:
  Confirmed

Bug description:
  1. Open any LibreOffice document, e.g., a Writer or Calc document.
  2. Make the window a reasonable, non-maximized size.
  3. Maximize the window.
  4. Close LibreOffice.
  5. Open the document again; it will open maximized.
  6. Un-maximize the window.
  7. Observe how the window has a ridiculously small size, not its previously 
unmaximized size.

  LibreOffice or gnome-shell bug? Not sure.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: libreoffice-core 1:5.4.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Nov  1 16:21:29 2017
  InstallationDate: Installed on 2017-05-19 (166 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: libreoffice
  UpgradeStatus: Upgraded to artful on 2017-10-20 (12 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1729433/+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 1729433]

[Koen Roggemans]

I can't reproduce the problem with a fresh 7.6.2.1 installation.
It looks like it's solved.
Thanks!

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

Title:
  LibreOffice doesn't remember window size when running under Wayland

Status in LibreOffice:
  Invalid
Status in libreoffice package in Ubuntu:
  Fix Released
Status in libreoffice package in Fedora:
  Confirmed

Bug description:
  1. Open any LibreOffice document, e.g., a Writer or Calc document.
  2. Make the window a reasonable, non-maximized size.
  3. Maximize the window.
  4. Close LibreOffice.
  5. Open the document again; it will open maximized.
  6. Un-maximize the window.
  7. Observe how the window has a ridiculously small size, not its previously 
unmaximized size.

  LibreOffice or gnome-shell bug? Not sure.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: libreoffice-core 1:5.4.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Nov  1 16:21:29 2017
  InstallationDate: Installed on 2017-05-19 (166 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: libreoffice
  UpgradeStatus: Upgraded to artful on 2017-10-20 (12 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1729433/+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 1729433] Re: LibreOffice doesn't remember window size when running under Wayland

[Bug Watch Updater]

** Changed in: df-libreoffice
   Status: Confirmed => Invalid

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

Title:
  LibreOffice doesn't remember window size when running under Wayland

Status in LibreOffice:
  Unknown
Status in libreoffice package in Ubuntu:
  Fix Released
Status in libreoffice package in Fedora:
  Confirmed

Bug description:
  1. Open any LibreOffice document, e.g., a Writer or Calc document.
  2. Make the window a reasonable, non-maximized size.
  3. Maximize the window.
  4. Close LibreOffice.
  5. Open the document again; it will open maximized.
  6. Un-maximize the window.
  7. Observe how the window has a ridiculously small size, not its previously 
unmaximized size.

  LibreOffice or gnome-shell bug? Not sure.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: libreoffice-core 1:5.4.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Nov  1 16:21:29 2017
  InstallationDate: Installed on 2017-05-19 (166 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: libreoffice
  UpgradeStatus: Upgraded to artful on 2017-10-20 (12 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1729433/+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 1729433] Re: LibreOffice doesn't remember window size when running under Wayland

[Rico Tzschichholz]

** Bug watch added: Document Foundation Bugzilla #125543
   https://bugs.documentfoundation.org/show_bug.cgi?id=125543

** Changed in: df-libreoffice
   Importance: Low => Unknown

** Changed in: df-libreoffice
   Status: Invalid => Unknown

** Changed in: df-libreoffice
 Remote watch: Document Foundation Bugzilla #104371 => Document Foundation 
Bugzilla #125543

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

Title:
  LibreOffice doesn't remember window size when running under Wayland

Status in LibreOffice:
  Unknown
Status in libreoffice package in Ubuntu:
  Fix Released
Status in libreoffice package in Fedora:
  Confirmed

Bug description:
  1. Open any LibreOffice document, e.g., a Writer or Calc document.
  2. Make the window a reasonable, non-maximized size.
  3. Maximize the window.
  4. Close LibreOffice.
  5. Open the document again; it will open maximized.
  6. Un-maximize the window.
  7. Observe how the window has a ridiculously small size, not its previously 
unmaximized size.

  LibreOffice or gnome-shell bug? Not sure.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: libreoffice-core 1:5.4.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Nov  1 16:21:29 2017
  InstallationDate: Installed on 2017-05-19 (166 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: libreoffice
  UpgradeStatus: Upgraded to artful on 2017-10-20 (12 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1729433/+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 1951210] Re: libreoffice help doesn't open in firefox (404 error on file:///tmp/lu417531j7po.tmp/NewHelp0.html)

[Dave Jones]

Thanks @eythian -- I'll take that as confirmation and mark this Fix
Released

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

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

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

Title:
  libreoffice help doesn't open in firefox (404 error on
  file:///tmp/lu417531j7po.tmp/NewHelp0.html)

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

Bug description:
  Ubuntu jammy live QA-test on
  - dell [optiplex] 780 (c2q-q9400, 8gb, amd/ati cedar radeon hd 
5000/6000/7350/8350)

  Opened LibreOffice Writer as random apps in QA-test.
  Hit F1 to call help, and all I get is an error

  URL:  file:///tmp/lu417531j7po.tmp/NewHelp0.html

  ---
  File not found

  Firefox can’t find the file at /tmp/lu417531j7po.tmp/NewHelp0.html.

  Check the file name for capitalization or other typing errors.
  Check to see if the file was moved, renamed or deleted.
  ---

  Firefox opens as a snap; but it isn't accessing the data from
  LibreOffice.

  Reported first at https://forum.snapcraft.io/t/firefox-snap-breaks-
  libreoffice-deb/27537

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: libreoffice-writer 1:7.2.2-0ubuntu0.21.10.1
  ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
  Uname: Linux 5.13.0-19-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu73
  Architecture: amd64
  CasperMD5CheckResult: pass
  CasperVersion: 1.465+canary3.3
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Nov 17 04:46:33 2021
  LiveMediaBuild: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (2026)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1951210/+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 1729433] Re: LibreOffice doesn't remember window size when running under Wayland

[Bug Watch Updater]

Launchpad has imported 55 comments from the remote bug at
https://bugs.documentfoundation.org/show_bug.cgi?id=125543.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2019-05-28T07:50:09+00:00 Heiko-tietze-g wrote:

With a fresh profile, modules start maximized. That's not a good window
size for large screens, so users have to resize. Doing this with Calc
ends up in a tiny and hard to spot square (title bar only). We should a)
use a default windows size according the OS and b) at least define a
minimum size for Calc. AFAIR, it's not an issue for other modules.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1729433/comments/13


On 2019-06-16T03:43:24+00:00 Os-x wrote:

Hello Heiko,
Thank you for reporting this. I confirm it with:
Version: 6.3.0.0.alpha1+
Build ID: 77ae0abe21f672cf4b7d2e069f1d40d20edc49a7
CPU threads: 4; OS: Linux 4.9; UI render: default; VCL: gtk3; 
TinderBox: Linux-rpm_deb-x86_64@86-TDF, Branch:master, Time: 2019-05-31_15:33:33
Locale: en-GB (en_GB.utf8); UI-Language: en-US
Calc: threaded

When minimizing it the window size changes to really tiny square around
12px.

Regarding starting as maximized I don't see it as an issue because the
window size will be preserved for the next start. User will only have to
change it once and most people don't have large screens.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1729433/comments/14


On 2019-06-27T08:04:30+00:00 Heiko-tietze-g wrote:

Since Xisco requests input from UX, let's talk about. I work on a large
super-wide screen where the modules are set to the maximum screen size -
makes not much sense and I always resize first to ~1600x1200px, which is
a 4/3 ratio.

At least Windows has a application size policy with
PreferredLaunchViewSize and we should follow this.

Last but not least we define as minimum required resolution 1280x768px
in [1], that could also be taken into account.

Of course, the actual value has to be responsive to the resolution, and
the default scaling should work with HiRes too (8k screens might come in
some years). And we should maximize in case of very small screens.

[1] https://wiki.documentfoundation.org/Design/MenuBar

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1729433/comments/15


On 2019-07-11T13:12:56+00:00 Heiko-tietze-g wrote:

We discussed the topic in the design meeting and agreed on the proposal,
considering a 16:9 ration, which is better suited for movies, and less
space such as 50%, which would be too small. Any minimum value is an
advantage over the zero size that might appear to users as broken
(therefore I raise the importance).

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1729433/comments/16


On 2019-07-15T11:22:32+00:00 Heiko-tietze-g wrote:

SetMinOutputSizePixel() is implemented for include/vcl/syswindow and
include/sfx2/dockwin but not include/vcl/window.hxx. And this function
should receive the actual value from the OS/DE. Probably an easy hack
for more experienced developers. Thanks jmux for the code pointers.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1729433/comments/17


On 2019-07-18T17:36:02+00:00 Xiscofauli wrote:

@Caolán, I thought you might be interested in this issue...

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1729433/comments/18


On 2019-07-22T15:50:39+00:00 Caolan-mcnamara wrote:

SetMinOutputSizePixel sets the minimum size below which a window cannot
be shrunk, which is probably not whats wanted.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1729433/comments/19


On 2020-08-31T09:24:09+00:00 Buzea-bogdan wrote:

In my case I had the window with 2 mm wight and 1 cm height. It is very
hard to notice that this is a window. You can not edit in Calc in 0,02*1
cm... So, a default minim of 4 cm * 4 cm, or maybe 3*3 cm could be done.
From my POV a 3*3 cm would be a minimum, else you can not see any cell
in any file.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1729433/comments/24


On 2020-09-11T04:08:56+00:00 Buzea-bogdan wrote:

*** Bug 136655 has been marked as a duplicate of

[Desktop-packages] [Bug 2040453] Re: Gnome 45 crash on restart in X11 session [Window manager error: Another compositing manager is already running on screen 0 on display “:0”]

[seth tro]

This also affects me after an upgrade from 23.04 to 23.10. Same issue
that restart only works if no windows are open.

Using the fix in #1, following the mutter build instructions from
https://www.linuxfromscratch.org/blfs/view/svn/gnome/mutter.html fixed
the issue for me.

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

Title:
  Gnome 45 crash on restart in X11 session [Window manager error:
  Another compositing manager is already running on screen 0 on display
  “:0”]

Status in GNOME Shell:
  New
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in gnome-shell package in Arch Linux:
  New

Bug description:
  Hello,

  Since the upgrade to Ubuntu 23.10 with Gnome45, it is no longer
  possible to restart gnome-shell without crashing the session. The only
  way not to crash it is to close all applications before restarting
  gnome-shell. I have verified this too.

  This has already been reported upstream: 
https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/7050
  a tentative patch for mutter proposed: 
https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/7050#note_1876598

  Please consider reviewing/testing this patch and pushing an update so
  people can restart gnome-shell session without crashing it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/2040453/+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 2037121] Re: Freeze when going full screen while watching video

[Ayub Sourjah]

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

I am faced with the same issue even with all the updates in place. The
only work around is to close the laptop screen and reopen it and login.
This is only evident when I have an additional screen.

Ubuntu 23.10
X11
Kernel 6.5.0-10generic
Lenovo V15 G3 IAP

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

Title:
  Freeze when going full screen while watching video

Status in Mutter:
  New
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  Hi.

  The screen freezes when I switch a running video into fullscreen mode.
  It happens with Gnome Totem, VLC, Firefox, so the issue is not
  connected to a certain app.

  I can hear the audio playing in the background while the video output
  gets stuck. The keyboard keeps working but switching to another app
  via keyboard doesn't work because the screen keeps stuck with the
  video.

  Way to reproduce:

  1) Boot Ubuntu
  2) Close lid and let the laptop go to sleep mode
  3) Open the lid and login
  4) Start a random video on Youtube/VLC/Totem
  5) Switch to fullscreen
  -> Immediate freeze of the screen

  Workaround after the video froze:
  1) Press ESC key (As if you would usually leave the fullscreen mode, however, 
the screen will stay stuck)
  2) Close the lid
  3) Wait until the laptop goes into sleep mode
  4) Open the lid and login again

  Step 1) is necessary to leave the fullscreen before going to sleep.
  Otherwise after sleep and logging in again the screen gets stuck again
  immediately because the video is continued in fullscreen.

  Syslog tell me this:

  gnome-shell[1744]: meta_window_set_stack_position_no_sync: assertion
  'window->stack_position >= 0' failed

  Ubuntu 23.10 beta with all updates of 22.09.2023
  Ryzen 7 PRO 6850U
  Kernel 6.5.0-5-generic

To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/2037121/+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 2043863] [NEW] Keyboard Settings Won't Open (Ubuntu Unity 23.10)

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

Note: this is for the Unity flavour of Ubuntu.


I tried opening "Keyboard".
It wouldn't won't open.
The app icon was blinking in that bar thing where all opened apps are.
And then it went away after a couple seconds.


I tried to go to System Settings, and Keyboard.
It wouldn't go to Keyboard settings.
System Settings disappeared.


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

Ubuntu 23.10


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

Sorry, i don't know the package name.
And Ubuntu Unity 23.10 didn't come with Software Center.


3) What you expected to happen

I expected keyboard settings to open.


4) What happened instead

It didn't open.


I made sure system was up to date, and restarted pc. Still won't open.



I tried looking for a solution.
I tried running this in terminal:
unity-control-center keyboard.
It didn't open Keyboard settings.

Here's what terminal said:
amix@amix-XPS-8500:~$ unity-control-center keyboard
(unity-control-center:10603): dconf-DEBUG: 20:51:46.401: watch_fast: 
"/org/gnome/desktop/peripherals/keyboard/" (establishing: 0, active: 0)
(unity-control-center:10603): dconf-DEBUG: 20:51:46.401: watch_fast: 
"/org/gnome/desktop/interface/" (establishing: 0, active: 0)
(unity-control-center:10603): dconf-DEBUG: 20:51:46.401: watch_established: 
"/org/gnome/desktop/peripherals/keyboard/" (establishing: 1)
(unity-control-center:10603): dconf-DEBUG: 20:51:46.401: watch_established: 
"/org/gnome/desktop/interface/" (establishing: 1)
(unity-control-center:10603): dconf-DEBUG: 20:51:46.402: watch_fast: 
"/com/canonical/unity/settings-daemon/plugins/media-keys/" (establishing: 0, 
active: 0)
(unity-control-center:10603): dconf-DEBUG: 20:51:46.403: watch_established: 
"/com/canonical/unity/settings-daemon/plugins/media-keys/" (establishing: 1)
(unity-control-center:10603): dconf-DEBUG: 20:51:46.403: watch_fast: 
"/org/gnome/desktop/input-sources/" (establishing: 0, active: 0)
(unity-control-center:10603): dconf-DEBUG: 20:51:46.403: watch_fast: 
"/org/gnome/desktop/input-sources/" (establishing: 1, active: 0)
(unity-control-center:10603): dconf-DEBUG: 20:51:46.403: watch_established: 
"/org/gnome/desktop/input-sources/" (establishing: 2)
(unity-control-center:10603): dconf-DEBUG: 20:51:46.427: watch_fast: 
"/com/canonical/unity/settings-daemon/plugins/media-keys/" (establishing: 0, 
active: 1)
(unity-control-center:10603): dconf-DEBUG: 20:51:46.427: watch_fast: 
"/com/canonical/unity/settings-daemon/plugins/media-keys/" (establishing: 0, 
active: 2)
(unity-control-center:10603): dconf-DEBUG: 20:51:46.427: watch_fast: 
"/com/canonical/unity/settings-daemon/plugins/media-keys/" (establishing: 0, 
active: 3)
(unity-control-center:10603): dconf-DEBUG: 20:51:46.427: watch_fast: 
"/com/canonical/unity/settings-daemon/plugins/media-keys/" (establishing: 0, 
active: 4)
(unity-control-center:10603): dconf-DEBUG: 20:51:46.427: watch_fast: 
"/com/canonical/unity/settings-daemon/plugins/media-keys/" (establishing: 0, 
active: 5)
(unity-control-center:10603): dconf-DEBUG: 20:51:46.427: watch_fast: 
"/com/canonical/unity/settings-daemon/plugins/media-keys/" (establishing: 0, 
active: 6)
(unity-control-center:10603): dconf-DEBUG: 20:51:46.427: watch_fast: 
"/com/canonical/unity/settings-daemon/plugins/media-keys/" (establishing: 0, 
active: 7)
(unity-control-center:10603): dconf-DEBUG: 20:51:46.427: watch_fast: 
"/com/canonical/unity/settings-daemon/plugins/media-keys/" (establishing: 0, 
active: 8)
(unity-control-center:10603): dconf-DEBUG: 20:51:46.427: watch_fast: 
"/com/canonical/unity/settings-daemon/plugins/media-keys/" (establishing: 0, 
active: 9)
(unity-control-center:10603): dconf-DEBUG: 20:51:46.427: watch_fast: 
"/com/canonical/unity/settings-daemon/plugins/media-keys/" (establishing: 0, 
active: 10)
(unity-control-center:10603): dconf-DEBUG: 20:51:46.427: watch_fast: 
"/com/canonical/unity/settings-daemon/plugins/media-keys/" (establishing: 0, 
active: 11)
(unity-control-center:10603): dconf-DEBUG: 20:51:46.427: watch_fast: 
"/com/canonical/unity/settings-daemon/plugins/media-keys/" (establishing: 0, 
active: 12)
(unity-control-center:10603): dconf-DEBUG: 20:51:46.428: watch_fast: 
"/com/canonical/unity/settings-daemon/plugins/media-keys/" (establishing: 0, 
active: 13)
(unity-control-center:10603): dconf-DEBUG: 20:51:46.428: watch_fast: 
"/com/canonical/unity/settings-daemon/plugins/media-keys/" (establishing: 0, 
active: 14)
(unity-control-center:10603): dconf-DEBUG: 20:51:46.428: watch_fast: 
"/com/canonical/unity/settings-daemon/plugins/media-keys/" (establishing: 0, 
active: 15)
(unity-control-center:10603): dconf-DEBUG: 20:51:46.428: watch_fast: 
"/com/canonical/unity/settings-daemon/plugins/media-keys/" (establishing: 0, 
active: 16)
(unity-control-center:10603): dconf-DEBUG: 20:51:46.428: watch_fast: 
"/com/canonical/unity/settings-da

[Desktop-packages] [Bug 2043863] Re: Keyboard Settings Won't Open (Ubuntu Unity 23.10)

[Erich Eickmeyer]

Thank you for taking the time to report this bug and helping to make Ubuntu 
better. Please execute the following command only once, as it will 
automatically gather debugging information, in a terminal:
apport-collect 2043863

When reporting bugs in the future please use apport by using 'ubuntu-
bug' and the name of the package affected. You can learn more about this
functionality at https://wiki.ubuntu.com/ReportingBugs.

** Package changed: ubuntu => unity-control-center (Ubuntu)

** Changed in: unity-control-center (Ubuntu)
   Status: New => Incomplete

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

Title:
  Keyboard Settings Won't Open (Ubuntu Unity 23.10)

Status in unity-control-center package in Ubuntu:
  Incomplete

Bug description:
  Note: this is for the Unity flavour of Ubuntu.

  
  I tried opening "Keyboard".
  It wouldn't won't open.
  The app icon was blinking in that bar thing where all opened apps are.
  And then it went away after a couple seconds.

  
  I tried to go to System Settings, and Keyboard.
  It wouldn't go to Keyboard settings.
  System Settings disappeared.

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

  Ubuntu 23.10


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

  Sorry, i don't know the package name.
  And Ubuntu Unity 23.10 didn't come with Software Center.

  
  3) What you expected to happen

  I expected keyboard settings to open.


  4) What happened instead

  It didn't open.


  I made sure system was up to date, and restarted pc. Still won't open.



  I tried looking for a solution.
  I tried running this in terminal:
  unity-control-center keyboard.
  It didn't open Keyboard settings.

  Here's what terminal said:
  amix@amix-XPS-8500:~$ unity-control-center keyboard
  (unity-control-center:10603): dconf-DEBUG: 20:51:46.401: watch_fast: 
"/org/gnome/desktop/peripherals/keyboard/" (establishing: 0, active: 0)
  (unity-control-center:10603): dconf-DEBUG: 20:51:46.401: watch_fast: 
"/org/gnome/desktop/interface/" (establishing: 0, active: 0)
  (unity-control-center:10603): dconf-DEBUG: 20:51:46.401: watch_established: 
"/org/gnome/desktop/peripherals/keyboard/" (establishing: 1)
  (unity-control-center:10603): dconf-DEBUG: 20:51:46.401: watch_established: 
"/org/gnome/desktop/interface/" (establishing: 1)
  (unity-control-center:10603): dconf-DEBUG: 20:51:46.402: watch_fast: 
"/com/canonical/unity/settings-daemon/plugins/media-keys/" (establishing: 0, 
active: 0)
  (unity-control-center:10603): dconf-DEBUG: 20:51:46.403: watch_established: 
"/com/canonical/unity/settings-daemon/plugins/media-keys/" (establishing: 1)
  (unity-control-center:10603): dconf-DEBUG: 20:51:46.403: watch_fast: 
"/org/gnome/desktop/input-sources/" (establishing: 0, active: 0)
  (unity-control-center:10603): dconf-DEBUG: 20:51:46.403: watch_fast: 
"/org/gnome/desktop/input-sources/" (establishing: 1, active: 0)
  (unity-control-center:10603): dconf-DEBUG: 20:51:46.403: watch_established: 
"/org/gnome/desktop/input-sources/" (establishing: 2)
  (unity-control-center:10603): dconf-DEBUG: 20:51:46.427: watch_fast: 
"/com/canonical/unity/settings-daemon/plugins/media-keys/" (establishing: 0, 
active: 1)
  (unity-control-center:10603): dconf-DEBUG: 20:51:46.427: watch_fast: 
"/com/canonical/unity/settings-daemon/plugins/media-keys/" (establishing: 0, 
active: 2)
  (unity-control-center:10603): dconf-DEBUG: 20:51:46.427: watch_fast: 
"/com/canonical/unity/settings-daemon/plugins/media-keys/" (establishing: 0, 
active: 3)
  (unity-control-center:10603): dconf-DEBUG: 20:51:46.427: watch_fast: 
"/com/canonical/unity/settings-daemon/plugins/media-keys/" (establishing: 0, 
active: 4)
  (unity-control-center:10603): dconf-DEBUG: 20:51:46.427: watch_fast: 
"/com/canonical/unity/settings-daemon/plugins/media-keys/" (establishing: 0, 
active: 5)
  (unity-control-center:10603): dconf-DEBUG: 20:51:46.427: watch_fast: 
"/com/canonical/unity/settings-daemon/plugins/media-keys/" (establishing: 0, 
active: 6)
  (unity-control-center:10603): dconf-DEBUG: 20:51:46.427: watch_fast: 
"/com/canonical/unity/settings-daemon/plugins/media-keys/" (establishing: 0, 
active: 7)
  (unity-control-center:10603): dconf-DEBUG: 20:51:46.427: watch_fast: 
"/com/canonical/unity/settings-daemon/plugins/media-keys/" (establishing: 0, 
active: 8)
  (unity-control-center:10603): dconf-DEBUG: 20:51:46.427: watch_fast: 
"/com/canonical/unity/settings-daemon/plugins/media-keys/" (establishing: 0, 
active: 9)
  (unity-control-center:10603): dconf-DEBUG: 20:51:46.427: watch_fast: 
"/com/canonical/unity/settings-daemon/plugins/media-keys/" (establishing: 0, 
active: 10)
  (unity-control-center:10603): dconf-DEBUG: 20:51:46.427: watch_fast: 
"/com/canonical/unity/settings-daemon/plugins/me

[Desktop-packages] [Bug 2025531] Re: file-roller crashed with signal 5 in g_object_new_valist()

[Launchpad Bug Tracker]

[Expired for file-roller (Ubuntu) because there has been no activity for
60 days.]

** Changed in: file-roller (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  file-roller crashed with signal 5 in g_object_new_valist()

Status in file-roller package in Ubuntu:
  Expired

Bug description:
  While edubuntu-mantic parallel installing
  kubuntu kde-desktop ubuntucinnamon-desktop:

  E: /tmp/apt-dpkg-install-iBrOhl/518-kubuntu-settings-
  desktop_1%3a23.04.5_all.deb:

  »/etc/skel/.face«

  tried to override because of

  desktop-base 12.0.6ubuntu1



  ProblemType: Crash
  DistroRelease: Ubuntu 23.10
  Package: file-roller 43.0-1
  ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5
  Uname: Linux 6.3.0-7-generic x86_64
  ApportVersion: 2.26.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jul  1 14:35:45 2023
  ExecutablePath: /usr/bin/file-roller
  InstallationDate: Installed on 2023-07-01 (0 days ago)
  InstallationMedia: Edubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230629)
  ProcCmdline: /usr/bin/file-roller --service
  ProcEnviron:
   LANG=de_DE.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  Signal: 5
  SourcePackage: file-roller
  StacktraceTop:
   ?? () from /lib/x86_64-linux-gnu/libgio-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_object_new_valist () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_object_new () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: file-roller crashed with signal 5 in g_object_new_valist()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo users
  separator:


  
  My solution in synaptic was:
  uninstall kubuntu-desktop and kubuntu-settings-desktop

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