Re: [Desktop-packages] [ext] [Bug 2049923] Re: gnome-terminal freezing, then crashing

2024-01-30 Thread Ralf Hildebrandt
* Ralf Hildebrandt <2049...@bugs.launchpad.net>:

> I'll have to check this when it happens the next time

I found a way to reproduce (works every second to third time):

* open a new terminal
* type nothing into the terminal
* press CTRL-SHIT T to create a new tab
* change to that new tab
* type something; I mostly press RETURN three times
* detach that newly created tab

All open instances of gnome-termin terminal close after about half a
second

-- 
Ralf Hildebrandt
Charité - Universitätsmedizin Berlin
Geschäftsbereich IT | Abteilung Netz | Netzwerk-Administration
Invalidenstraße 120/121 | D-10115 Berlin

Tel. +49 30 450 570 155
ralf.hildebra...@charite.de
https://www.charite.de

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

Title:
  gnome-terminal freezing, then crashing

Status in gnome-terminal package in Ubuntu:
  New

Bug description:
  First: It's very hard to reproduce, but it happens to me about once per week.
  If often open new windows or split windows out from tabs. And then it 
happens. First it becomes unresponsive, and then after about 2-3 seconds it 
simply closes all instances.

  
  [328830.780749] gnome-terminal-[117706]: segfault at 460742 ip 
7fdb2fb45611 sp 7ffdb8c5fda0 error 4 in 
libgtk-3.so.0.2406.32[7fdb2f883000+38f000] likely on CPU 4 (core 4, socket 0)

  [328830.780761] Code: fb 48 83 ec 20 64 48 8b 04 25 28 00 00 00 48 89
  44 24 18 31 c0 e8 bf 6d ff ff 48 85 db 74 7a 48 89 c6 48 8b 03 48 85
  c0 74 05 <48> 39 30 74 0c 48 89 df e8 a2 c2 d4 ff 85 c0 74 5e 48 89 e6
  48 89

  [329377.925310] gnome-terminal-[120116]: segfault at 2f0774 ip
  7f86af745611 sp 7ffc9943c5c0 error 4 in
  libgtk-3.so.0.2406.32[7f86af483000+38f000] likely on CPU 2 (core 2,
  socket 0)

  [329377.925324] Code: fb 48 83 ec 20 64 48 8b 04 25 28 00 00 00 48 89
  44 24 18 31 c0 e8 bf 6d ff ff 48 85 db 74 7a 48 89 c6 48 8b 03 48 85
  c0 74 05 <48> 39 30 74 0c 48 89 df e8 a2 c2 d4 ff 85 c0 74 5e 48 89 e6
  48 89

  unfortunately, apport isn't automatically creating a crash report.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: gnome-terminal 3.49.92-2ubuntu1
  ProcVersionSignature: Ubuntu 6.5.0-14.14-generic 6.5.3
  Uname: Linux 6.5.0-14-generic x86_64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jan 19 16:48:43 2024
  SourcePackage: gnome-terminal
  UpgradeStatus: Upgraded to mantic on 2023-10-17 (94 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/2049923/+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 2050743] Re: plymouthd crashed with SIGSEGV in ply_input_device_get_keymap()

2024-01-30 Thread Daniel van Vugt
** Bug watch added: gitlab.freedesktop.org/plymouth/plymouth/-/issues #245
   https://gitlab.freedesktop.org/plymouth/plymouth/-/issues/245

** Also affects: plymouth via
   https://gitlab.freedesktop.org/plymouth/plymouth/-/issues/245
   Importance: Unknown
   Status: Unknown

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

Title:
  plymouthd crashed with SIGSEGV in ply_input_device_get_keymap()

Status in Plymouth:
  Unknown
Status in plymouth package in Ubuntu:
  Confirmed

Bug description:
  Unsure

  ProblemType: Crash
  DistroRelease: Ubuntu 24.04
  Package: plymouth 23.360.11-0ubuntu2
  ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3
  Uname: Linux 6.6.0-14-generic x86_64
  ApportVersion: 2.27.0-0ubuntu6
  Architecture: amd64
  CasperMD5CheckResult: pass
  CloudArchitecture: x86_64
  CloudID: none
  CloudName: none
  CloudPlatform: none
  CloudSubPlatform: config
  Date: Mon Jan 22 18:15:26 2024
  DefaultPlymouth: /usr/share/plymouth/themes/bgrt/bgrt.plymouth
  ExecutablePath: /usr/sbin/plymouthd
  InstallationDate: Installed on 2024-01-22 (0 days ago)
  InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240122)
  JournalErrors: -- No entries --
  Lspci:
   
  Lspci-vt:
   
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  Lsusb-t:
   
  Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1:
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.6.0-14-generic 
root=UUID=be8601a9-912c-475f-a790-c973864eb61f ro quiet splash vt.handoff=7
  ProcCmdline: /usr/sbin/plymouthd --mode=boot --pid-file=/run/plymouth/pid 
--attach-to-session
  ProcEnviron:
   LANG=C.UTF-8
   PATH=(custom, no user)
  ProcFB: 0 hyperv_fb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.6.0-14-generic 
root=UUID=be8601a9-912c-475f-a790-c973864eb61f ro quiet splash vt.handoff=7
  SegvAnalysis:
   Segfault happened at: 0x766b66f5aeab :   
mov0x40(%rdi),%rdi
   PC (0x766b66f5aeab) ok
   source "0x40(%rdi)" (0x0040) not located in a known VMA region (needed 
readable region)!
   destination "%rdi" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: plymouth
  StacktraceTop:
   ply_input_device_get_keymap () from 
/lib/x86_64-linux-gnu/libply-splash-core.so.5
   ?? () from /usr/lib/x86_64-linux-gnu/plymouth/renderers/frame-buffer.so
   ply_keymap_icon_new () from /lib/x86_64-linux-gnu/libply-splash-graphics.so.5
   ?? () from /usr/lib/x86_64-linux-gnu/plymouth/two-step.so
   ?? () from /lib/x86_64-linux-gnu/libply-splash-core.so.5
  TextPlymouth: /usr/share/plymouth/themes/ubuntu-text/ubuntu-text.plymouth
  Title: plymouthd crashed with SIGSEGV in ply_input_device_get_keymap()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  dmi.bios.date: 04/06/2022
  dmi.bios.release: 4.1
  dmi.bios.vendor: Microsoft Corporation
  dmi.bios.version: Hyper-V UEFI Release v4.1
  dmi.board.asset.tag: None
  dmi.board.name: Virtual Machine
  dmi.board.vendor: Microsoft Corporation
  dmi.board.version: Hyper-V UEFI Release v4.1
  dmi.chassis.asset.tag: 4565-7867-8475-0140-6079-1274-47
  dmi.chassis.type: 3
  dmi.chassis.vendor: Microsoft Corporation
  dmi.chassis.version: Hyper-V UEFI Release v4.1
  dmi.modalias: 
dmi:bvnMicrosoftCorporation:bvrHyper-VUEFIReleasev4.1:bd04/06/2022:br4.1:svnMicrosoftCorporation:pnVirtualMachine:pvrHyper-VUEFIReleasev4.1:rvnMicrosoftCorporation:rnVirtualMachine:rvrHyper-VUEFIReleasev4.1:cvnMicrosoftCorporation:ct3:cvrHyper-VUEFIReleasev4.1:skuNone:
  dmi.product.family: Virtual Machine
  dmi.product.name: Virtual Machine
  dmi.product.sku: None
  dmi.product.version: Hyper-V UEFI Release v4.1
  dmi.sys.vendor: Microsoft Corporation
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/plymouth/+bug/2050743/+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 2051478] Re: unlock passphrase doesn't work in plymouth but works in recovery mode

2024-01-30 Thread Daniel van Vugt
** Also affects: plymouth via
   https://gitlab.freedesktop.org/plymouth/plymouth/-/issues/243
   Importance: Unknown
   Status: Unknown

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

Title:
  unlock passphrase doesn't work in plymouth but works in recovery mode

Status in Plymouth:
  Unknown
Status in cryptsetup package in Ubuntu:
  Invalid
Status in plymouth package in Ubuntu:
  New

Bug description:
  The system suddenly stopped accepting the existing passphrase on boot.
  However, the passphrase is definitely correct since the same one can
  be used in the recovery mode and it unlocks the volume appropriately.

  More precisely, it looks like devices that inject characters pretty
  quickly (e.g. Yubikey to type pre-created random strings with
  length=32) are necessary to trigger the issue.

  WORKAROUND:
  1. boot into the recovery mode
  2. unlock the volume in the console
  3. remove "splash" from /etc/default/grub and run `update-grub`
  3. reboot

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: cryptsetup 2:2.6.1-6ubuntu1
  ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3
  Uname: Linux 6.6.0-14-generic x86_64
  NonfreeKernelModules: zfs
  ApportVersion: 2.27.0-0ubuntu6
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jan 29 15:41:03 2024
  InstallationDate: Installed on 2024-01-08 (21 days ago)
  InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240104)
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  SourcePackage: cryptsetup
  UpgradeStatus: No upgrade log present (probably fresh install)
  cmdline: BOOT_IMAGE=/vmlinuz-6.6.0-14-generic 
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash
  crypttab: dm_crypt-0 UUID=cfd8c295-9988-4934-a91a-460a9d16d80f none luks

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


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


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

2024-01-30 Thread Daniel van Vugt
Ah it's because the new systemd (which will fix this) is stuck in
proposed. To work around it you need to manually revert:

https://launchpadlibrarian.net/709437063/plymouth_23.360.11-0ubuntu1_23.360.11-0ubuntu2.diff.gz

** Changed in: plymouth (Ubuntu)
   Status: New => In Progress

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

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

** Changed in: plymouth (Ubuntu)
   Status: In Progress => Won't Fix

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

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

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

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

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

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


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


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

2024-01-30 Thread Daniel van Vugt
Public bug reported:

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

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

** Affects: plymouth (Ubuntu)
 Importance: Undecided
 Status: In Progress


** Tags: ftbfs noble regression-release

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

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

Status in plymouth package in Ubuntu:
  In Progress

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

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

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


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


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

2024-01-30 Thread Lee Sheng Hung
Sorry for the late reply. Proposed package 23.2.1-1ubuntu3.1~22.04.2
amd64 [installed,automatic], GUI displayed normally, thank you for the
help!

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

Title:
  GUI crashed after installed proposed package libegl-mesa0

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

Bug description:
  [Impact]

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

  [Fix]

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

  [Test case]

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

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

  ---

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

  GUI crashed but still able to access system by ssh.

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

  [Expected result]
  GUI displayed normally

  [Actual result]
  GUI crashed

  [Failure rate]
  100%

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

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

  [Stage]
  Issue reported.

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


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


[Desktop-packages] [Bug 2050831] Re: Performance

2024-01-30 Thread Daniel van Vugt
Thanks for the bug report. It appears the graphics driver and Xorg are
working correctly here. And certainly I would not expect all modern
games to maintain 60 FPS on the integrated GPU of an Intel i3-1115G4.

As for the blurry HDMI output, the Samsung un32t4300 is limited to
1366x768 so a little blurry compared to the laptop screen is probably
correct. Can you please plug the TV in again and then run:

  xrandr --verbose > xrandr.txt

and attach the resulting text file here?

Also please try to report only one problem per bug report. You can log
many separate bug reports.



** Package changed: xorg (Ubuntu) => ubuntu

** Changed in: ubuntu
   Status: New => Incomplete

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

Title:
  Performance

Status in Ubuntu:
  Incomplete

Bug description:
  Hello, inside Steam, in big picture mode, in system, system
  information, the vram memory has a negative value, it is not showing
  the real amount that the onboard reaches, supports. I think it's the
  video driver, or some other driver.

  There are also some fps losses, games that reach 60fps, at various
  times it is below, like 45fps or less. Even switching to maximum
  performance mode by clicking on the system battery icon.

  When I connect the PC to a smart TV as the primary screen, with HDMI, full 
HD, the image is blurry, as if there were blurs in the images.
  In the TV settings, it is set to maximum contrast and sharpness.

  Also another feedback: in languages, in the system settings, I can't
  download the missing packages, the download button is not shown. This
  happens after installing the system in minimal mode, and then
  installing other additional programs. I will send the name of the
  programs.

  sudo apt install --install-recommends guvcview rhythmbox libreoffice
  psensor

  Lenovo Ideapad 3 15itl6 82md
  Linux Kubuntu lts 22.04
  Kde plasma
  1920x1080p 60hz
  4gb ram
  20gb swap
  btfrs
  ptbr utf8 abnt2

  Steam (.deb), from the Steam website.

  samsung smarttv, 32 inches, un32t4300

  In the system settings, on monitor, the scale is at 100%

  Thank you in advance, success always
  

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3
  Uname: Linux 6.5.0-14-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: KDE
  Date: Mon Jan 22 17:09:37 2024
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Device [8086:9a78] (rev 03) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Device [17aa:3f9c]
  InstallationDate: Installed on 2024-01-13 (9 days ago)
  InstallationMedia: Kubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.1)
  MachineType: LENOVO 82MD
  ProcEnviron:
   LANGUAGE=pt_BR:pt:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pt_BR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-6.5.0-14-generic 
root=UUID=58277c11-b933-4491-8d44-0caa0d498477 ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/06/2023
  dmi.bios.release: 1.57
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GGCN57WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0T76466 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: IdeaPad 3 15ITL6
  dmi.ec.firmware.release: 1.57
  dmi.modalias: 
dmi:bvnLENOVO:bvrGGCN57WW:bd09/06/2023:br1.57:efr1.57:svnLENOVO:pn82MD:pvrIdeaPad315ITL6:rvnLENOVO:rnLNVNB161216:rvrSDK0T76466WIN:cvnLENOVO:ct10:cvrIdeaPad315ITL6:skuLENOVO_MT_82MD_BU_idea_FM_IdeaPad315ITL6:
  dmi.product.family: IdeaPad 3 15ITL6
  dmi.product.name: 82MD
  dmi.product.sku: LENOVO_MT_82MD_BU_idea_FM_IdeaPad 3 15ITL6
  dmi.product.version: IdeaPad 3 15ITL6
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~22.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

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


-- 
Mailing list: 

[Desktop-packages] [Bug 2045329] Re: The 'Files Selecting' window shows Asia fonts incompletely.

2024-01-30 Thread Launchpad Bug Tracker
[Expired for nautilus (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  The 'Files Selecting' window shows Asia fonts incompletely.

Status in nautilus package in Ubuntu:
  Expired

Bug description:
  The 'Files Selecting' windows shows Asia fonts incompletely. Please
  view the image I uploaded of it.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: nautilus 1:45~rc-1ubuntu1
  ProcVersionSignature: Ubuntu 6.5.0-13.13-generic 6.5.3
  Uname: Linux 6.5.0-13-generic x86_64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Dec  1 08:51:46 2023
  GsettingsChanges:
   
  InstallationDate: Installed on 2023-10-26 (35 days ago)
  InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418)
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=tmux-256color
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to mantic on 2023-10-26 (35 days ago)
  usr_lib_nautilus:
   file-roller   43.0-1
   nautilus-extension-gnome-terminal 3.49.92-2ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2045329/+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 2051738] Re: Suspend button does not respond to mouse click, only touchcreen

2024-01-30 Thread Daniel van Vugt
I don't have mantic handy, but it's almost the same gnome-shell version
as in noble. And in noble the bug doesn't happen here.

I also don't see any upstream bug reports about this so maybe it's time to 
report it there:
https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/new

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

Title:
  Suspend button does not respond to mouse click, only touchcreen

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  So, this is pretty weird.

  In the Shell quick settings panel (the one accessed by clicking on the
  wifi/bluetooth/sound/battery part of the top bar), in the Shutdown
  submenu, the "Suspend" button - and *only* the Suspend button - does
  not respond to mouse clicks. I cannot use it to suspend the system
  with either the touchpad or an external mouse.

  The other buttons in that menu respond to mouse clicks, and the
  Suspend button responds when I use the touchscreen to tap it.

  I've attached a screencast in an attempt to demonstrate this (although
  it obviously doesn't show when I'm actually clicking the mouse).

  This behaviour has been going on for a while, at least the whole
  Mantic cycle, but maybe longer.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: gnome-shell 45.2-0ubuntu1
  ProcVersionSignature: Ubuntu 6.5.0-14.14-generic 6.5.3
  Uname: Linux 6.5.0-14-generic x86_64
  NonfreeKernelModules: zfs
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jan 31 09:21:31 2024
  DisplayManager: gdm3
  InstallationDate: Installed on 2021-06-26 (949 days ago)
  InstallationMedia: Ubuntu 21.10.0 2021.05.28 amd64 "bcachefs" (20210622)
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions: mutter-common 45.2-0ubuntu3
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to mantic on 2023-10-22 (101 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2051738/+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 2051694] Re: Regression: Kubuntu 22.04 LTS overrides Xorg.conf-specified monitor layout

2024-01-30 Thread Daniel van Vugt
** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu)

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

Title:
  Regression: Kubuntu 22.04 LTS overrides Xorg.conf-specified monitor
  layout

Status in xorg-server package in Ubuntu:
  New

Bug description:
  When I built a new PC with Kubuntu 22.04 LTS, I carried over my
  recently purchased GeForce RTX 3060 and copied over the Xorg.conf that
  was doing perfectly well for me in 20.04 LTS, containing the following
  line:

  Option  "metamodes" "HDMI-0: 1280x1024 +3200+0, DP-3:
  1280x1024 +0+0, DP-1: 1920x1080 +1280+0"

  (Bear in mind that, due to a history of bugginess in KScreen2 and how
  it interacts with Plasma panel layouts, I disable it in the Background
  Services control panel and do my best to lock down the allowed layouts
  and resolutions in Xorg.conf.)

  This technique has been working for me for close to a decade, with my
  previous video card being a GeForce GTX750 and, if I remember
  correctly, I was also using it with the GeForce GT430 I was using
  before that, and with Kubuntu and Lubuntu versions going back to at
  least Kubuntu 16.04 LTS and likely to Lubuntu 14.04 and possibly even
  Lubuntu 12.04.

  However, much to my dismay, it appeared to have no effect, and the
  system was still assigning a virtual layout that didn't match the
  physical arrangement of the monitors.

  Eventually, I realized from /var/log/Xorg.0.log that my metamodes line
  WAS getting set, but, for reasons I still have no idea how to
  diagnose, something else was overriding it and resetting the metamodes
  line back to the undesired default, with unlocked resolutions and an
  incorrect monitor layout.

  [21.689] (II) NVIDIA(0): Setting mode "HDMI-0: 1280x1024 @1280x1024 
+3200+0 {ViewPortIn=1280x1024, ViewPortOut=1280x1024+0+0}, DP-3: 1280x1024 
@1280x1024 +0+0 {ViewPortIn=1280x1024, ViewPortOut=1280x1024+0+0}, DP-1: 
nvidia-auto-select @1920x1080 +0+0 {ViewPortIn=1920x1080, 
ViewPortOut=1920x1080+0+0}"
  [21.747] (II) NVIDIA(0): Setting mode "DP-3: 1280x1024 @1280x1024 +0+0 
{ViewPortIn=1280x1024, ViewPortOut=1280x1024+0+0}, DP-1: nvidia-auto-select 
@1920x1080 +0+0 {ViewPortIn=1920x1080, ViewPortOut=1920x1080+0+0}"
  [21.834] (II) NVIDIA(0): Setting mode "HDMI-0: nvidia-auto-select 
@1280x1024 +1920+0 {ViewPortIn=1280x1024, ViewPortOut=1280x1024+0+0}, DP-3: 
1280x1024 @1280x1024 +0+0 {ViewPortIn=1280x1024, ViewPortOut=1280x1024+0+0}, 
DP-1: nvidia-auto-select @1920x1080 +0+0 {ViewPortIn=1920x1080, 
ViewPortOut=1920x1080+0+0}"
  [21.922] (II) NVIDIA(0): Setting mode "HDMI-0: nvidia-auto-select 
@1280x1024 +1920+0 {ViewPortIn=1280x1024, ViewPortOut=1280x1024+0+0}, DP-3: 
nvidia-auto-select @1280x1024 +3200+0 {ViewPortIn=1280x1024, 
ViewPortOut=1280x1024+0+0}, DP-1: nvidia-auto-select @1920x1080 +0+0 
{ViewPortIn=1920x1080, ViewPortOut=1920x1080+0+0}"

  As a workaround which may or may not show up in the ubuntu-bug report,
  I've created a /etc/X11/Xsession.d/01-fix-the-damn-ignored-metamodes
  file containing the line `xrandr --output DP-3 --left-of DP-1`.

  ...though that doesn't fix the monitor layout at the login screen and
  it's not possible to work around the forced changeability of the
  resolution without a working metamodes according to
  https://gitlab.freedesktop.org/xorg/xserver/-/issues/353#note_91110

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3
  Uname: Linux 6.5.0-14-generic x86_64
  NonfreeKernelModules: zfs nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
  .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
  .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  535.146.02  Sun Dec  3 
14:06:14 UTC 2023
   GCC version:  gcc version 12.3.0 (Ubuntu 12.3.0-1ubuntu1~22.04)
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: KDE
  Date: Tue Jan 30 06:25:44 2024
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation GA106 [GeForce RTX 3060 Lite Hash Rate] [10de:2504] (rev 
a1) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. GA106 [GeForce RTX 3060 Lite Hash Rate] 
[1043:8810]
   Advanced Micro Devices, Inc. [AMD/ATI] Device [1002:164e] (rev c6) (prog-if 
00 [VGA controller])
 Subsystem: Advanced Micro 

[Desktop-packages] [Bug 2051711] Re: Ubuntu Freezes

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

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

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

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

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



** Package changed: xorg (Ubuntu) => ubuntu

** Changed in: ubuntu
   Status: New => Incomplete

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

Title:
  Ubuntu Freezes

Status in Ubuntu:
  Incomplete

Bug description:
  Likely - problem with graphical card driver

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.5.0-15.15~22.04.1-generic 6.5.3
  Uname: Linux 6.5.0-15-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckMismatches: 
./pool/main/g/gcc-12/cpp-12_12.1.0-2ubuntu1~22.04_amd64.deb 
./pool/restricted/n/nvidia-graphics-drivers-515/libnvidia-gl-515_515.86.01-0ubuntu0.22.04.1_amd64.deb
 
./pool/restricted/n/nvidia-graphics-drivers-525/libnvidia-gl-525_525.78.01-0ubuntu0.22.04.1_amd64.deb
  CasperMD5CheckResult: fail
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 30 16:29:33 2024
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Device [8086:46a8] (rev 0c) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Device [17aa:22e8]
  InstallationDate: Installed on 2023-07-10 (204 days ago)
  InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 
(20230223)
  MachineType: LENOVO 21AH0092CK
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-15-generic 
root=UUID=5a82ce67-8314-4e81-9866-eaaf4c03e725 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/07/2022
  dmi.bios.release: 1.2
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N3MET05W (1.02 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 21AH0092CK
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0T76530 WIN
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.3
  dmi.modalias: 
dmi:bvnLENOVO:bvrN3MET05W(1.02):bd06/07/2022:br1.2:efr1.3:svnLENOVO:pn21AH0092CK:pvrThinkPadT14Gen3:rvnLENOVO:rn21AH0092CK:rvrSDK0T76530WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21AH_BU_Think_FM_ThinkPadT14Gen3:
  dmi.product.family: ThinkPad T14 Gen 3
  dmi.product.name: 21AH0092CK
  dmi.product.sku: LENOVO_MT_21AH_BU_Think_FM_ThinkPad T14 Gen 3
  dmi.product.version: ThinkPad T14 Gen 3
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~22.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 23.0.4-0ubuntu1~22.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/2051711/+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 1970069] Re: Annoying boot messages interfering with splash screen

2024-01-30 Thread Daniel van Vugt
** Changed in: plymouth (Ubuntu)
   Status: Invalid => Confirmed

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

Title:
  Annoying boot messages interfering with splash screen

Status in linux package in Ubuntu:
  In Progress
Status in plymouth package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  New

Bug description:
  Since upgrading from 20.04.6 Desktop to 22.04, the boot screen is not
  as clean as it used to be.

  Basically, the flow used to be in 20.04:

  GRUB > Splash screen > Login prompt

  Currently in 22.04:

  GRUB > Splash screen > Messages (in the attached file) > Splash screen
  again for a sec > Login prompt

  All of those messages already existed in 20.04, the difference is that
  they were not appearing during boot.

  I was able to get rid of the "usb" related messages by just adding
  "loglevel=0" in GRUB. Currently is "quiet loglevel=0 splash".

  Regarding the fsck related message, I can get rid of them by adding
  "fsck.mode=skip".

  However, I do not want to just disable fsck or set the loglevel to 0.
  This is not a sustainable solution.

  Something definitely changed here. These messages are not of enough
  relevance to be shown at boot by default, and they should remain
  hidden like they were in Focal.

  Obviously a minor issue, but important to the whole look and feel of
  the OS for desktop.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1970069/+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 2051738] [NEW] Suspend button does not respond to mouse click, only touchcreen

2024-01-30 Thread Chris Halse Rogers
Public bug reported:

So, this is pretty weird.

In the Shell quick settings panel (the one accessed by clicking on the
wifi/bluetooth/sound/battery part of the top bar), in the Shutdown
submenu, the "Suspend" button - and *only* the Suspend button - does not
respond to mouse clicks. I cannot use it to suspend the system with
either the touchpad or an external mouse.

The other buttons in that menu respond to mouse clicks, and the Suspend
button responds when I use the touchscreen to tap it.

I've attached a screencast in an attempt to demonstrate this (although
it obviously doesn't show when I'm actually clicking the mouse).

This behaviour has been going on for a while, at least the whole Mantic
cycle, but maybe longer.

ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: gnome-shell 45.2-0ubuntu1
ProcVersionSignature: Ubuntu 6.5.0-14.14-generic 6.5.3
Uname: Linux 6.5.0-14-generic x86_64
NonfreeKernelModules: zfs
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Wed Jan 31 09:21:31 2024
DisplayManager: gdm3
InstallationDate: Installed on 2021-06-26 (949 days ago)
InstallationMedia: Ubuntu 21.10.0 2021.05.28 amd64 "bcachefs" (20210622)
RebootRequiredPkgs: Error: path contained symlinks.
RelatedPackageVersions: mutter-common 45.2-0ubuntu3
SourcePackage: gnome-shell
UpgradeStatus: Upgraded to mantic on 2023-10-22 (101 days ago)

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


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

** Attachment added: "Screencast of failing to click on the suspend button"
   
https://bugs.launchpad.net/bugs/2051738/+attachment/5743692/+files/Screencast%20from%202024-01-31%2009-26-10.webm

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

Title:
  Suspend button does not respond to mouse click, only touchcreen

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  So, this is pretty weird.

  In the Shell quick settings panel (the one accessed by clicking on the
  wifi/bluetooth/sound/battery part of the top bar), in the Shutdown
  submenu, the "Suspend" button - and *only* the Suspend button - does
  not respond to mouse clicks. I cannot use it to suspend the system
  with either the touchpad or an external mouse.

  The other buttons in that menu respond to mouse clicks, and the
  Suspend button responds when I use the touchscreen to tap it.

  I've attached a screencast in an attempt to demonstrate this (although
  it obviously doesn't show when I'm actually clicking the mouse).

  This behaviour has been going on for a while, at least the whole
  Mantic cycle, but maybe longer.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: gnome-shell 45.2-0ubuntu1
  ProcVersionSignature: Ubuntu 6.5.0-14.14-generic 6.5.3
  Uname: Linux 6.5.0-14-generic x86_64
  NonfreeKernelModules: zfs
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jan 31 09:21:31 2024
  DisplayManager: gdm3
  InstallationDate: Installed on 2021-06-26 (949 days ago)
  InstallationMedia: Ubuntu 21.10.0 2021.05.28 amd64 "bcachefs" (20210622)
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions: mutter-common 45.2-0ubuntu3
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to mantic on 2023-10-22 (101 days ago)

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


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


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

2024-01-30 Thread Bug Watch Updater
** Changed in: df-libreoffice
   Status: Confirmed => 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/2039021

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

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

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

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

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

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

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

  Specific examples:

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

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

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

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

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

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


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


[Desktop-packages] [Bug 2039021]

2024-01-30 Thread Libreoffice-commits
Noel Grandin committed a patch related to this issue.
It has been pushed to "master":

https://git.libreoffice.org/core/commit/8d26ca7f9ac37b5ada0a2c463b37181bcc8301a8

tdf#158695 convert-to bogusly needs libcui (--disable-gui build)

It will be available in 24.8.0.

The patch should be included in the daily builds available at
https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More
information about daily builds can be found at:
https://wiki.documentfoundation.org/Testing_Daily_Builds

Affected users are encouraged to test the fix and report feedback.

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

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

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

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

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

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

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

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

  Specific examples:

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

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

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

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

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

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


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


[Desktop-packages] [Bug 2047256] Re: Ubuntu 24.04 Some image thumbnails no longer displayed

2024-01-30 Thread corrado venturini
** Description changed:

- After recent updates on my Ubuntu Noble 24.04 nautilus does not show 
thumbnails of PDF files.
- On a different partition same PC Ubuntu Noble 24.04 not recently updated PDF 
thumbnails are correctly displayed
+ After recent updates on my Ubuntu Noble 24.04 nautilus does not show 
thumbnails of PDF and other image files.
+ On a different partition same PC Ubuntu Noble 24.04 not recently updated 
image thumbnails are correctly displayed
  
  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: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Dec 22 16:15:59 2023
  GsettingsChanges:
-  b'org.gnome.nautilus.preferences' b'migrated-gtk-settings' b'true'
-  b'org.gnome.nautilus.window-state' b'initial-size' b'(879, 943)'
+  b'org.gnome.nautilus.preferences' b'migrated-gtk-settings' b'true'
+  b'org.gnome.nautilus.window-state' b'initial-size' b'(879, 943)'
  InstallationDate: Installed on 2023-12-10 (12 days ago)
  InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20231210)
  ProcEnviron:
-  LANG=en_US.UTF-8
-  PATH=(custom, no user)
-  SHELL=/bin/bash
-  TERM=xterm-256color
-  XDG_RUNTIME_DIR=
+  LANG=en_US.UTF-8
+  PATH=(custom, no user)
+  SHELL=/bin/bash
+  TERM=xterm-256color
+  XDG_RUNTIME_DIR=
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_nautilus:
-  file-roller   43.1-1
-  nautilus-extension-gnome-terminal 3.49.92-2ubuntu1
-  nautilus-image-converter  0.4.0-2
-  nautilus-share0.7.5-0.3
-  python3-nautilus  4.0-1build1
+  file-roller   43.1-1
+  nautilus-extension-gnome-terminal 3.49.92-2ubuntu1
+  nautilus-image-converter  0.4.0-2
+  nautilus-share0.7.5-0.3
+  python3-nautilus  4.0-1build1

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

Title:
  Ubuntu 24.04 Some image thumbnails no longer displayed

Status in nautilus package in Ubuntu:
  Confirmed

Bug description:
  After recent updates on my Ubuntu Noble 24.04 nautilus does not show 
thumbnails of PDF and other image files.
  On a different partition same PC Ubuntu Noble 24.04 not recently updated 
image thumbnails are correctly displayed

  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: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Dec 22 16:15:59 2023
  GsettingsChanges:
   b'org.gnome.nautilus.preferences' b'migrated-gtk-settings' b'true'
   b'org.gnome.nautilus.window-state' b'initial-size' b'(879, 943)'
  InstallationDate: Installed on 2023-12-10 (12 days ago)
  InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20231210)
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_nautilus:
   file-roller   43.1-1
   nautilus-extension-gnome-terminal 3.49.92-2ubuntu1
   nautilus-image-converter  0.4.0-2
   nautilus-share0.7.5-0.3
   python3-nautilus  4.0-1build1

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


Re: [Desktop-packages] [Bug 2051574] Re: gnome-shell-portal-helper crashed with SIGTRAP in waitUntilSyncedOrDie() from WebKit::XDGDBusProxy::launch()

2024-01-30 Thread Marcelo Carvalho
I can confirm it happened to me all the time when tryin 24.04.

_M

On Mon, Jan 29, 2024 at 7:35 PM Daniel van Vugt <2051...@bugs.launchpad.net>
wrote:

> ** Summary changed:
>
> - WiFi connecting gives error message every time but connects - Ubuntu
> 24.04
> + gnome-shell-portal-helper crashed with SIGTRAP in waitUntilSyncedOrDie()
> from WebKit::XDGDBusProxy::launch()
>
> ** Information type changed from Private to Public
>
> ** Also affects: webkit2gtk (Ubuntu)
>Importance: Undecided
>Status: New
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/2051574
>
> Title:
>   gnome-shell-portal-helper crashed with SIGTRAP in
>   waitUntilSyncedOrDie() from WebKit::XDGDBusProxy::launch()
>
> Status in gnome-shell package in Ubuntu:
>   New
> Status in webkit2gtk package in Ubuntu:
>   New
>
> Bug description:
>   Same as Summary
>
>   ProblemType: Crash
>   DistroRelease: Ubuntu 24.04
>   Package: gnome-shell 45.3-1ubuntu1
>   ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3
>   Uname: Linux 6.6.0-14-generic x86_64
>   ApportVersion: 2.27.0-0ubuntu6
>   Architecture: amd64
>   CasperMD5CheckResult: pass
>   CrashCounter: 1
>   CurrentDesktop: ubuntu:GNOME
>   Date: Mon Jan 29 08:56:29 2024
>   DisplayManager: gdm3
>   ExecutablePath: /usr/libexec/gnome-shell-portal-helper
>   InstallationDate: Installed on 2024-01-25 (4 days ago)
>   InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64
> (20240116)
>   ProcCmdline: /usr/libexec/gnome-shell-portal-helper
>   ProcEnviron:
>LANG=en_US.UTF-8
>PATH=(custom, no user)
>SHELL=/bin/bash
>XDG_RUNTIME_DIR=
>   RelatedPackageVersions: mutter-common 45.3-1ubuntu1
>   Signal: 5
>   SourcePackage: gnome-shell
>   StacktraceTop:
>?? () from /lib/x86_64-linux-gnu/libwebkitgtk-6.0.so.4
>?? () from /lib/x86_64-linux-gnu/libwebkitgtk-6.0.so.4
>?? () from /lib/x86_64-linux-gnu/libwebkitgtk-6.0.so.4
>?? () from /lib/x86_64-linux-gnu/libwebkitgtk-6.0.so.4
>?? () from /lib/x86_64-linux-gnu/libwebkitgtk-6.0.so.4
>   Title: gnome-shell-portal-helper crashed with signal 5
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   UserGroups: adm cdrom dip lpadmin plugdev sudo users
>   separator:
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2051574/+subscriptions
>
>

--



This email and any attachments may contain Astranis confidential 
and/or proprietary information governed by a non-disclosure agreement, and 
are intended solely for the individual or entity specified by the message.

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

Title:
  gnome-shell-portal-helper crashed with SIGTRAP in
  waitUntilSyncedOrDie() from WebKit::XDGDBusProxy::launch()

Status in gnome-shell package in Ubuntu:
  New
Status in webkit2gtk package in Ubuntu:
  New

Bug description:
  Same as Summary

  ProblemType: Crash
  DistroRelease: Ubuntu 24.04
  Package: gnome-shell 45.3-1ubuntu1
  ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3
  Uname: Linux 6.6.0-14-generic x86_64
  ApportVersion: 2.27.0-0ubuntu6
  Architecture: amd64
  CasperMD5CheckResult: pass
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jan 29 08:56:29 2024
  DisplayManager: gdm3
  ExecutablePath: /usr/libexec/gnome-shell-portal-helper
  InstallationDate: Installed on 2024-01-25 (4 days ago)
  InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240116)
  ProcCmdline: /usr/libexec/gnome-shell-portal-helper
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  RelatedPackageVersions: mutter-common 45.3-1ubuntu1
  Signal: 5
  SourcePackage: gnome-shell
  StacktraceTop:
   ?? () from /lib/x86_64-linux-gnu/libwebkitgtk-6.0.so.4
   ?? () from /lib/x86_64-linux-gnu/libwebkitgtk-6.0.so.4
   ?? () from /lib/x86_64-linux-gnu/libwebkitgtk-6.0.so.4
   ?? () from /lib/x86_64-linux-gnu/libwebkitgtk-6.0.so.4
   ?? () from /lib/x86_64-linux-gnu/libwebkitgtk-6.0.so.4
  Title: gnome-shell-portal-helper crashed with signal 5
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sudo users
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2051574/+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 2051031] Re: Occasionally system alert will play as loud scary static noise.

2024-01-30 Thread Nicholas Romero
Happened twice today I swear this is going to give some one a heart
attack

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

Title:
  Occasionally system alert will play as loud scary static noise.

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  EG when I made this issue I was trying to autocomplete a scp command
  in my terminal. The autocomplete noise was a scary static noise..
  litterlly like something out of a horror movie and it's very jarring.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu7
  ProcVersionSignature: Ubuntu 6.1.0-1027.27-oem 6.1.61
  Uname: Linux 6.1.0-1027-oem x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 23 14:37:35 2024
  InstallationDate: Installed on 2023-12-05 (49 days ago)
  InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.2)
  PackageArchitecture: all
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Blackjack 
successful
  Symptom_Card: BRIO Ultra HD Webcam - Logitech BRIO
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: None of the above
  Title: [USB-Audio - Onyx Blackjack, playback] Playback problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/17/2023
  dmi.bios.release: 3.3
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 03.03
  dmi.board.asset.tag: *
  dmi.board.name: FRANMDCP07
  dmi.board.vendor: Framework
  dmi.board.version: A7
  dmi.chassis.asset.tag: FRANDGCPA73433005D
  dmi.chassis.type: 10
  dmi.chassis.vendor: Framework
  dmi.chassis.version: A7
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr03.03:bd10/17/2023:br3.3:svnFramework:pnLaptop13(AMDRyzen7040Series):pvrA7:rvnFramework:rnFRANMDCP07:rvrA7:cvnFramework:ct10:cvrA7:skuFRANDGCP07:
  dmi.product.family: Laptop
  dmi.product.name: Laptop 13 (AMD Ryzen 7040Series)
  dmi.product.sku: FRANDGCP07
  dmi.product.version: A7
  dmi.sys.vendor: Framework

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2051031/+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 2051572] Re: Always preseed core and snapd snap in server seed

2024-01-30 Thread Simon Déziel
** Description changed:

  In removing the LXD snap from preseeding in the server seed for Ubuntu
- 24.04 as part LP #2051346 [1] we also removed the snaps snap and the
+ 24.04 as part LP #2051346 [1] we also removed the snapd snap and the
  core22 snap.
  
  This means that are subsequent snap install, like LXD, will take much
  longer than expected for a non minimized image.
  
- 
- Time taken to install LXD snap using the lxd-installer package without snapd 
and core22 preinstalled/seeded
+ Time taken to install LXD snap using the lxd-installer package without
+ snapd and core22 preinstalled/seeded
  
  ```
  ubuntu@cloudimg:~$ time sudo lxd --version
  Installing LXD snap, please be patient.
  5.19
  
  real  0m29.107s
  user  0m0.006s
  sys   0m0.005s
  ```
  
- 
- Time taken to install LXD snap using the lxd-installer package with snapd and 
core22 already installed.
+ Time taken to install LXD snap using the lxd-installer package with
+ snapd and core22 already installed.
  
  ```
  ubuntu@cloudimg:~$ time sudo lxd --version
  Installing LXD snap, please be patient.
  5.19
  
  real  0m15.034s
  user  0m0.005s
  sys   0m0.005s
  ```
  
  This is a significant difference and for a workload we intend to remain
  as a core tested and tracked workload. As such I propose we re-introduce
  core22 and snaps snaps to our seed.
  
  LXD do intend to move to the core24 snap as their base as I'm sure snapd
  does too so when that does happen we need to update the preseeded core
  snap.
  
  This bug is to track the work of making that change in the server seed @
  https://git.launchpad.net/~ubuntu-core-dev/ubuntu-
  seeds/+git/ubuntu/tree/server#n69
  
- 
  [1] https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/2051346

** Description changed:

  In removing the LXD snap from preseeding in the server seed for Ubuntu
  24.04 as part LP #2051346 [1] we also removed the snapd snap and the
  core22 snap.
  
  This means that are subsequent snap install, like LXD, will take much
  longer than expected for a non minimized image.
  
  Time taken to install LXD snap using the lxd-installer package without
  snapd and core22 preinstalled/seeded
  
  ```
  ubuntu@cloudimg:~$ time sudo lxd --version
  Installing LXD snap, please be patient.
  5.19
  
  real  0m29.107s
  user  0m0.006s
  sys   0m0.005s
  ```
  
  Time taken to install LXD snap using the lxd-installer package with
  snapd and core22 already installed.
  
  ```
  ubuntu@cloudimg:~$ time sudo lxd --version
  Installing LXD snap, please be patient.
  5.19
  
  real  0m15.034s
  user  0m0.005s
  sys   0m0.005s
  ```
  
  This is a significant difference and for a workload we intend to remain
  as a core tested and tracked workload. As such I propose we re-introduce
- core22 and snaps snaps to our seed.
+ core22 and snapd snaps to our seed.
  
  LXD do intend to move to the core24 snap as their base as I'm sure snapd
  does too so when that does happen we need to update the preseeded core
  snap.
  
  This bug is to track the work of making that change in the server seed @
  https://git.launchpad.net/~ubuntu-core-dev/ubuntu-
  seeds/+git/ubuntu/tree/server#n69
  
  [1] https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/2051346

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

Title:
  Always preseed core and snapd snap in server seed

Status in ubuntu-meta package in Ubuntu:
  New
Status in ubuntu-meta source package in Noble:
  New

Bug description:
  In removing the LXD snap from preseeding in the server seed for Ubuntu
  24.04 as part LP #2051346 [1] we also removed the snapd snap and the
  core22 snap.

  This means that are subsequent snap install, like LXD, will take much
  longer than expected for a non minimized image.

  Time taken to install LXD snap using the lxd-installer package without
  snapd and core22 preinstalled/seeded

  ```
  ubuntu@cloudimg:~$ time sudo lxd --version
  Installing LXD snap, please be patient.
  5.19

  real  0m29.107s
  user  0m0.006s
  sys   0m0.005s
  ```

  Time taken to install LXD snap using the lxd-installer package with
  snapd and core22 already installed.

  ```
  ubuntu@cloudimg:~$ time sudo lxd --version
  Installing LXD snap, please be patient.
  5.19

  real  0m15.034s
  user  0m0.005s
  sys   0m0.005s
  ```

  This is a significant difference and for a workload we intend to
  remain as a core tested and tracked workload. As such I propose we re-
  introduce core22 and snapd snaps to our seed.

  LXD do intend to move to the core24 snap as their base as I'm sure
  snapd does too so when that does happen we need to update the
  preseeded core snap.

  This bug is to track the work of making that change in the server seed
  @ https://git.launchpad.net/~ubuntu-core-dev/ubuntu-
  seeds/+git/ubuntu/tree/server#n69

  [1] 

[Desktop-packages] [Bug 2051711] [NEW] Ubuntu Freezes

2024-01-30 Thread Dmytro
Public bug reported:

Likely - problem with graphical card driver

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-15.15~22.04.1-generic 6.5.3
Uname: Linux 6.5.0-15-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5CheckMismatches: 
./pool/main/g/gcc-12/cpp-12_12.1.0-2ubuntu1~22.04_amd64.deb 
./pool/restricted/n/nvidia-graphics-drivers-515/libnvidia-gl-515_515.86.01-0ubuntu0.22.04.1_amd64.deb
 
./pool/restricted/n/nvidia-graphics-drivers-525/libnvidia-gl-525_525.78.01-0ubuntu0.22.04.1_amd64.deb
CasperMD5CheckResult: fail
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Tue Jan 30 16:29:33 2024
DistUpgraded: Fresh install
DistroCodename: jammy
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation Device [8086:46a8] (rev 0c) (prog-if 00 [VGA controller])
   Subsystem: Lenovo Device [17aa:22e8]
InstallationDate: Installed on 2023-07-10 (204 days ago)
InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 
(20230223)
MachineType: LENOVO 21AH0092CK
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-15-generic 
root=UUID=5a82ce67-8314-4e81-9866-eaaf4c03e725 ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/07/2022
dmi.bios.release: 1.2
dmi.bios.vendor: LENOVO
dmi.bios.version: N3MET05W (1.02 )
dmi.board.asset.tag: Not Available
dmi.board.name: 21AH0092CK
dmi.board.vendor: LENOVO
dmi.board.version: SDK0T76530 WIN
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.3
dmi.modalias: 
dmi:bvnLENOVO:bvrN3MET05W(1.02):bd06/07/2022:br1.2:efr1.3:svnLENOVO:pn21AH0092CK:pvrThinkPadT14Gen3:rvnLENOVO:rn21AH0092CK:rvrSDK0T76530WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21AH_BU_Think_FM_ThinkPadT14Gen3:
dmi.product.family: ThinkPad T14 Gen 3
dmi.product.name: 21AH0092CK
dmi.product.sku: LENOVO_MT_21AH_BU_Think_FM_ThinkPad T14 Gen 3
dmi.product.version: ThinkPad T14 Gen 3
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~22.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx 23.0.4-0ubuntu1~22.04.1
version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.7
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1

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


** Tags: amd64 apport-bug jammy ubuntu

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

Title:
  Ubuntu Freezes

Status in xorg package in Ubuntu:
  New

Bug description:
  Likely - problem with graphical card driver

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.5.0-15.15~22.04.1-generic 6.5.3
  Uname: Linux 6.5.0-15-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckMismatches: 
./pool/main/g/gcc-12/cpp-12_12.1.0-2ubuntu1~22.04_amd64.deb 
./pool/restricted/n/nvidia-graphics-drivers-515/libnvidia-gl-515_515.86.01-0ubuntu0.22.04.1_amd64.deb
 
./pool/restricted/n/nvidia-graphics-drivers-525/libnvidia-gl-525_525.78.01-0ubuntu0.22.04.1_amd64.deb
  CasperMD5CheckResult: fail
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 30 16:29:33 2024
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Device [8086:46a8] (rev 0c) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Device [17aa:22e8]
  InstallationDate: Installed on 2023-07-10 (204 days ago)
  InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 
(20230223)
  MachineType: LENOVO 21AH0092CK
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-15-generic 
root=UUID=5a82ce67-8314-4e81-9866-eaaf4c03e725 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/07/2022
  dmi.bios.release: 1.2
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N3MET05W (1.02 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 21AH0092CK
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0T76530 WIN
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.3
  dmi.modalias: 

[Desktop-packages] [Bug 2051705] [NEW] package bluez 5.68-0ubuntu1.1 failed to install/upgrade: installed bluez package post-installation script subprocess returned error exit status 1

2024-01-30 Thread Sachin
Public bug reported:

I am unable to turn on my Bluetooth so I unable to connect to my mouse
and earbuds to laptops

ProblemType: Package
DistroRelease: Ubuntu 23.10
Package: bluez 5.68-0ubuntu1.1
ProcVersionSignature: Ubuntu 6.5.0-15.15-generic 6.5.3
Uname: Linux 6.5.0-15-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
AptOrdering:
 bluez:amd64: Install
 python3-gi-cairo:amd64: Install
 blueman:amd64: Install
 NULL: ConfigurePending
Architecture: amd64
CasperMD5CheckResult: pass
Date: Tue Jan 30 20:30:22 2024
ErrorMessage: installed bluez package post-installation script subprocess 
returned error exit status 1
InstallationDate: Installed on 2023-07-28 (186 days ago)
InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418)
InterestingModules: rfcomm bnep btusb bluetooth
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 0bda:58ea Realtek Semiconductor Corp. EasyCamera
 Bus 001 Device 002: ID 8087:0a2a Intel Corp. Bluetooth wireless interface
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-15-generic 
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash vt.handoff=7
Python3Details: /usr/bin/python3.11, Python 3.11.6, python3-minimal, 3.11.4-5
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.22.0ubuntu1
 apt  2.7.3
SnapChanges:
 ID   Status  Spawn  Ready  Summary
 115  Done2024-01-30T20:08:13+05:30  2024-01-30T20:09:04+05:30  Install 
"bluez" snap
SourcePackage: bluez
Title: package bluez 5.68-0ubuntu1.1 failed to install/upgrade: installed bluez 
package post-installation script subprocess returned error exit status 1
UpgradeStatus: Upgraded to mantic on 2023-11-20 (71 days ago)
dmi.bios.date: 06/13/2018
dmi.bios.release: 1.44
dmi.bios.vendor: LENOVO
dmi.bios.version: 8TCN44WW
dmi.board.asset.tag: NO Asset Tag
dmi.board.name: LNVNB161216
dmi.board.vendor: LENOVO
dmi.board.version: NO DPK
dmi.chassis.asset.tag: NO Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Lenovo ideapad 330-15IKB
dmi.ec.firmware.release: 1.44
dmi.modalias: 
dmi:bvnLENOVO:bvr8TCN44WW:bd06/13/2018:br1.44:efr1.44:svnLENOVO:pn81DE:pvrLenovoideapad330-15IKB:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrLenovoideapad330-15IKB:skuLENOVO_MT_81DE_BU_idea_FM_ideapad330-15IKB:
dmi.product.family: ideapad 330-15IKB
dmi.product.name: 81DE
dmi.product.sku: LENOVO_MT_81DE_BU_idea_FM_ideapad 330-15IKB
dmi.product.version: Lenovo ideapad 330-15IKB
dmi.sys.vendor: LENOVO
hciconfig:
 hci0:  Type: Primary  Bus: USB
BD Address: 20:16:B9:30:5F:51  ACL MTU: 1021:5  SCO MTU: 96:6
DOWN 
RX bytes:20039 acl:61 sco:0 events:2513 errors:0
TX bytes:1443881 acl:2245 sco:0 commands:251 errors:0

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


** Tags: amd64 apport-package mantic

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

Title:
  package bluez 5.68-0ubuntu1.1 failed to install/upgrade: installed
  bluez package post-installation script subprocess returned error exit
  status 1

Status in bluez package in Ubuntu:
  New

Bug description:
  I am unable to turn on my Bluetooth so I unable to connect to my mouse
  and earbuds to laptops

  ProblemType: Package
  DistroRelease: Ubuntu 23.10
  Package: bluez 5.68-0ubuntu1.1
  ProcVersionSignature: Ubuntu 6.5.0-15.15-generic 6.5.3
  Uname: Linux 6.5.0-15-generic x86_64
  ApportVersion: 2.27.0-0ubuntu5
  AptOrdering:
   bluez:amd64: Install
   python3-gi-cairo:amd64: Install
   blueman:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Tue Jan 30 20:30:22 2024
  ErrorMessage: installed bluez package post-installation script subprocess 
returned error exit status 1
  InstallationDate: Installed on 2023-07-28 (186 days ago)
  InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418)
  InterestingModules: rfcomm bnep btusb bluetooth
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0bda:58ea Realtek Semiconductor Corp. EasyCamera
   Bus 001 Device 002: ID 8087:0a2a Intel Corp. Bluetooth wireless interface
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-15-generic 
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash vt.handoff=7
  Python3Details: /usr/bin/python3.11, Python 3.11.6, python3-minimal, 3.11.4-5
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.22.0ubuntu1
   apt  2.7.3
  SnapChanges:
   ID   Status  Spawn  Ready  Summary
   115  Done2024-01-30T20:08:13+05:30  

[Desktop-packages] [Bug 595934] Re: gvfs-backends should be split in multiple sub-packages

2024-01-30 Thread Birgit Edel
Another unpleasant side effect of the dependencies is that libmtp-common
with `/usr/lib/udev/rules.d/69-libmtp.rules` is pulled in, making snap-
device-helper bugs more difficult to decipher from logs.

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

Title:
  gvfs-backends should be split in multiple sub-packages

Status in gvfs package in Ubuntu:
  Confirmed
Status in gvfs package in Debian:
  New

Bug description:
  Binary package hint: gvfs

  The gvfs-backends should be transformed in a meta-package that only
  recommends other more specific sub-packages.

  Currently the gvfs-backends package contains «the afc, archive, burn,
  cdda, dav, dnssd, ftp, gphoto2, http, network, obexftp, sftp,
  smb and smb-browse backends» and depends on 22 different libraries.

  While all these backends may come handy at times, low-resource
  computer would benefit if some of these where not installed.

  For example cd-less computers (not only netbooks) do not need the
  "burn" or "cdda" backends. These two backends install and run a demon
  that requires memory and installs unneeded libraries.

  A similar argument applies to the AFS backend (not that much useful
  these days to a wide audience, runs a daemon), gphoto2 (office
  workstation and thin clients do not need it, runs a daemon), obexftp
  (makes any Gnome installation dependent on Bluetooth libraries) and
  any other protocol.

  While installing all these backends by default is certainly a good
  thing, not having a way to remove them when not needed is a problem.
  Making gvfs-backends a meta-package and splitting its current content
  in multiple packages (gvfs-backends-afs, gvfs-backends-sftp, gvfs-
  backends-smb) would retain the good behaviour while still allowing
  users with little resources (RAM, disk, CPU) to remove the unneeded
  components.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/595934/+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 1965123] Re: Rounded corners are missing (square indents instead)

2024-01-30 Thread Dima Golub
I also have this problem on clear ubuntu

OS: Ubuntu 23.10
Kernel: 6.5.0-15-generic
Session: Wayland
GPU: rx6700xt
CPU: Ryzen 9 7950x


** Attachment added: "shakal.png"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1965123/+attachment/5743571/+files/shakal.png

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

Title:
  Rounded corners are missing (square indents instead)

Status in Dash to dock:
  Unknown
Status in GNOME Shell:
  New
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 22.04 development branch @ 16/03/2022

  after yesterdays updates to gnome 42 beta

  the docks area around the active launcher is missing 4 pixels in the corners
  when hovering mouse over them

  switching to another active launchers can be reproduced

  non-active area around launchers does not suffer this bug

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell-extension-ubuntu-dock 72~ubuntu3
  ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19
  Uname: Linux 5.15.0-22-generic x86_64
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar 16 12:55:20 2022
  PackageArchitecture: all
  SourcePackage: gnome-shell-extension-ubuntu-dock
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/dash-to-dock/+bug/1965123/+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 2050831] Re: Performance

2024-01-30 Thread Leandro
ok, thanks, success always 

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

Title:
  Performance

Status in xorg package in Ubuntu:
  New

Bug description:
  Hello, inside Steam, in big picture mode, in system, system
  information, the vram memory has a negative value, it is not showing
  the real amount that the onboard reaches, supports. I think it's the
  video driver, or some other driver.

  There are also some fps losses, games that reach 60fps, at various
  times it is below, like 45fps or less. Even switching to maximum
  performance mode by clicking on the system battery icon.

  When I connect the PC to a smart TV as the primary screen, with HDMI, full 
HD, the image is blurry, as if there were blurs in the images.
  In the TV settings, it is set to maximum contrast and sharpness.

  Also another feedback: in languages, in the system settings, I can't
  download the missing packages, the download button is not shown. This
  happens after installing the system in minimal mode, and then
  installing other additional programs. I will send the name of the
  programs.

  sudo apt install --install-recommends guvcview rhythmbox libreoffice
  psensor

  Lenovo Ideapad 3 15itl6 82md
  Linux Kubuntu lts 22.04
  Kde plasma
  1920x1080p 60hz
  4gb ram
  20gb swap
  btfrs
  ptbr utf8 abnt2

  Steam (.deb), from the Steam website.

  samsung smarttv, 32 inches, un32t4300

  In the system settings, on monitor, the scale is at 100%

  Thank you in advance, success always
  

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3
  Uname: Linux 6.5.0-14-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: KDE
  Date: Mon Jan 22 17:09:37 2024
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Device [8086:9a78] (rev 03) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Device [17aa:3f9c]
  InstallationDate: Installed on 2024-01-13 (9 days ago)
  InstallationMedia: Kubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.1)
  MachineType: LENOVO 82MD
  ProcEnviron:
   LANGUAGE=pt_BR:pt:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pt_BR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-6.5.0-14-generic 
root=UUID=58277c11-b933-4491-8d44-0caa0d498477 ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/06/2023
  dmi.bios.release: 1.57
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GGCN57WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0T76466 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: IdeaPad 3 15ITL6
  dmi.ec.firmware.release: 1.57
  dmi.modalias: 
dmi:bvnLENOVO:bvrGGCN57WW:bd09/06/2023:br1.57:efr1.57:svnLENOVO:pn82MD:pvrIdeaPad315ITL6:rvnLENOVO:rnLNVNB161216:rvrSDK0T76466WIN:cvnLENOVO:ct10:cvrIdeaPad315ITL6:skuLENOVO_MT_82MD_BU_idea_FM_IdeaPad315ITL6:
  dmi.product.family: IdeaPad 3 15ITL6
  dmi.product.name: 82MD
  dmi.product.sku: LENOVO_MT_82MD_BU_idea_FM_IdeaPad 3 15ITL6
  dmi.product.version: IdeaPad 3 15ITL6
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~22.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/2050831/+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 2008491] Re: Memory leak in pulseaudio

2024-01-30 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  Memory leak in pulseaudio

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  This is very weird, but my pulseaudio uses 3.5GB as I type this. That
  seems big for audio stuff.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: pulseaudio 1:15.99.1+dfsg1-1ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-60.66-generic 5.15.78
  Uname: Linux 5.15.0-60-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Feb 24 14:56:46 2023
  InstallationDate: Installed on 2023-01-04 (51 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/11/2022
  dmi.bios.release: 1.32
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R23ET62W (1.32 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 21CKCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: ThinkPad
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.23
  dmi.modalias: 
dmi:bvnLENOVO:bvrR23ET62W(1.32):bd11/11/2022:br1.32:efr1.23:svnLENOVO:pn21CKCTO1WW:pvrThinkPadP16sGen1:rvnLENOVO:rn21CKCTO1WW:rvrThinkPad:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21CK_BU_Think_FM_ThinkPadP16sGen1:
  dmi.product.family: ThinkPad P16s Gen 1
  dmi.product.name: 21CKCTO1WW
  dmi.product.sku: LENOVO_MT_21CK_BU_Think_FM_ThinkPad P16s Gen 1
  dmi.product.version: ThinkPad P16s Gen 1
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/2008491/+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 2026885] Re: nano is not available on i386

2024-01-30 Thread Ken Sharp
** Also affects: ubuntu-meta (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  nano is not available on i386

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

Bug description:
  There is no i386 Nano package in Jammy. I used Nano all the time
  including in chroots, which is where this reared its ugly head.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nano/+bug/2026885/+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 2051536] Re: security update regression tracking bug

2024-01-30 Thread Launchpad Bug Tracker
This bug was fixed in the package xorg-server -
2:21.1.4-2ubuntu1.7~22.04.8

---
xorg-server (2:21.1.4-2ubuntu1.7~22.04.8) jammy-security; urgency=medium

  * SECURITY REGRESSION: memory leak due to incomplete fix (LP: #2051536)
- debian/patches/CVE-2024-21886-3.patch: fix use after free in input
  device shutdown in dix/devices.c.

 -- Marc Deslauriers   Mon, 29 Jan 2024
07:43:15 -0500

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

Title:
  security update regression tracking bug

Status in xorg-server package in Ubuntu:
  Fix Released
Status in xwayland package in Ubuntu:
  Fix Released
Status in xorg-server source package in Focal:
  Fix Released
Status in xwayland source package in Focal:
  Invalid
Status in xorg-server source package in Jammy:
  Fix Released
Status in xwayland source package in Jammy:
  Fix Released
Status in xorg-server source package in Mantic:
  Fix Released
Status in xwayland source package in Mantic:
  Fix Released
Status in xorg-server source package in Noble:
  Fix Released
Status in xwayland source package in Noble:
  Fix Released

Bug description:
  USN-6587-1 fixed security issues in X.Org. A commit was missing which
  may result in a regression (memory leak).

  See:

  https://bugs.debian.org/1061110
  https://gitlab.freedesktop.org/xorg/xserver/-/issues/1623

  
https://gitlab.freedesktop.org/xorg/xserver/-/commit/8b75ec34dfbe435cd3a17e64138e22a37395a6d8

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/2051536/+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 2051536] Re: security update regression tracking bug

2024-01-30 Thread Launchpad Bug Tracker
This bug was fixed in the package xorg-server - 2:21.1.7-3ubuntu2.7

---
xorg-server (2:21.1.7-3ubuntu2.7) mantic-security; urgency=medium

  * SECURITY REGRESSION: memory leak due to incomplete fix (LP: #2051536)
- debian/patches/CVE-2024-21886-3.patch: fix use after free in input
  device shutdown in dix/devices.c.

 -- Marc Deslauriers   Mon, 29 Jan 2024
07:40:13 -0500

** Changed in: xorg-server (Ubuntu Jammy)
   Status: In Progress => Fix Released

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

Title:
  security update regression tracking bug

Status in xorg-server package in Ubuntu:
  Fix Released
Status in xwayland package in Ubuntu:
  Fix Released
Status in xorg-server source package in Focal:
  Fix Released
Status in xwayland source package in Focal:
  Invalid
Status in xorg-server source package in Jammy:
  Fix Released
Status in xwayland source package in Jammy:
  Fix Released
Status in xorg-server source package in Mantic:
  Fix Released
Status in xwayland source package in Mantic:
  Fix Released
Status in xorg-server source package in Noble:
  Fix Released
Status in xwayland source package in Noble:
  Fix Released

Bug description:
  USN-6587-1 fixed security issues in X.Org. A commit was missing which
  may result in a regression (memory leak).

  See:

  https://bugs.debian.org/1061110
  https://gitlab.freedesktop.org/xorg/xserver/-/issues/1623

  
https://gitlab.freedesktop.org/xorg/xserver/-/commit/8b75ec34dfbe435cd3a17e64138e22a37395a6d8

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/2051536/+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 2051536] Re: security update regression tracking bug

2024-01-30 Thread Launchpad Bug Tracker
This bug was fixed in the package xwayland - 2:22.1.1-1ubuntu0.11

---
xwayland (2:22.1.1-1ubuntu0.11) jammy-security; urgency=medium

  * SECURITY REGRESSION: memory leak due to incomplete fix (LP: #2051536)
- debian/patches/CVE-2024-21886-3.patch: fix use after free in input
  device shutdown in dix/devices.c.

 -- Marc Deslauriers   Mon, 29 Jan 2024
07:51:17 -0500

** Changed in: xorg-server (Ubuntu Mantic)
   Status: In Progress => Fix Released

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

Title:
  security update regression tracking bug

Status in xorg-server package in Ubuntu:
  Fix Released
Status in xwayland package in Ubuntu:
  Fix Released
Status in xorg-server source package in Focal:
  Fix Released
Status in xwayland source package in Focal:
  Invalid
Status in xorg-server source package in Jammy:
  Fix Released
Status in xwayland source package in Jammy:
  Fix Released
Status in xorg-server source package in Mantic:
  Fix Released
Status in xwayland source package in Mantic:
  Fix Released
Status in xorg-server source package in Noble:
  Fix Released
Status in xwayland source package in Noble:
  Fix Released

Bug description:
  USN-6587-1 fixed security issues in X.Org. A commit was missing which
  may result in a regression (memory leak).

  See:

  https://bugs.debian.org/1061110
  https://gitlab.freedesktop.org/xorg/xserver/-/issues/1623

  
https://gitlab.freedesktop.org/xorg/xserver/-/commit/8b75ec34dfbe435cd3a17e64138e22a37395a6d8

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/2051536/+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 2051536] Re: security update regression tracking bug

2024-01-30 Thread Launchpad Bug Tracker
This bug was fixed in the package xorg-server -
2:1.20.13-1ubuntu1~20.04.15

---
xorg-server (2:1.20.13-1ubuntu1~20.04.15) focal-security; urgency=medium

  * SECURITY REGRESSION: memory leak due to incomplete fix (LP: #2051536)
- debian/patches/CVE-2024-21886-3.patch: fix use after free in input
  device shutdown in dix/devices.c.

 -- Marc Deslauriers   Mon, 29 Jan 2024
07:44:21 -0500

** Changed in: xorg-server (Ubuntu Focal)
   Status: In Progress => Fix Released

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2024-21886

** Changed in: xwayland (Ubuntu Jammy)
   Status: In Progress => Fix Released

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

Title:
  security update regression tracking bug

Status in xorg-server package in Ubuntu:
  Fix Released
Status in xwayland package in Ubuntu:
  Fix Released
Status in xorg-server source package in Focal:
  Fix Released
Status in xwayland source package in Focal:
  Invalid
Status in xorg-server source package in Jammy:
  Fix Released
Status in xwayland source package in Jammy:
  Fix Released
Status in xorg-server source package in Mantic:
  Fix Released
Status in xwayland source package in Mantic:
  Fix Released
Status in xorg-server source package in Noble:
  Fix Released
Status in xwayland source package in Noble:
  Fix Released

Bug description:
  USN-6587-1 fixed security issues in X.Org. A commit was missing which
  may result in a regression (memory leak).

  See:

  https://bugs.debian.org/1061110
  https://gitlab.freedesktop.org/xorg/xserver/-/issues/1623

  
https://gitlab.freedesktop.org/xorg/xserver/-/commit/8b75ec34dfbe435cd3a17e64138e22a37395a6d8

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/2051536/+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 2051350] Re: package libasound2-plugins 1.2.7.1-1ubuntu2 failed to install/upgrade: trying to overwrite shared '/etc/alsa/conf.d/99-pulseaudio-default.conf.example', which is d

2024-01-30 Thread Apport retracing service
** Package changed: ubuntu => alsa-plugins (Ubuntu)

** Tags removed: need-duplicate-check

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

Title:
  package libasound2-plugins 1.2.7.1-1ubuntu2 failed to install/upgrade:
  trying to overwrite shared '/etc/alsa/conf.d/99-pulseaudio-
  default.conf.example', which is different from other instances of
  package libasound2-plugins:i386

Status in alsa-plugins package in Ubuntu:
  New

Bug description:
  wa installing wine

  ProblemType: Package
  DistroRelease: Ubuntu 23.10
  Package: libasound2-plugins 1.2.7.1-1ubuntu2
  ProcVersionSignature: Ubuntu 6.5.0-15.15.1-lowlatency 6.5.3
  Uname: Linux 6.5.0-15-lowlatency x86_64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Fri Jan 26 10:23:45 2024
  DuplicateSignature:
   package:libasound2-plugins:1.2.7.1-1ubuntu2
   Unpacking libasound2-plugins:i386 (1.2.7.1-1ubuntu2) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-LCQD0p/134-libasound2-plugins_1.2.7.1-1ubuntu2_i386.deb 
(--unpack):
trying to overwrite shared 
'/etc/alsa/conf.d/99-pulseaudio-default.conf.example', which is different from 
other instances of package libasound2-plugins:i386
  ErrorMessage: trying to overwrite shared 
'/etc/alsa/conf.d/99-pulseaudio-default.conf.example', which is different from 
other instances of package libasound2-plugins:i386
  InstallationDate: Installed on 2024-01-25 (1 days ago)
  InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 
(20231016.1)
  Python3Details: /usr/bin/python3.11, Python 3.11.6, python3-minimal, 3.11.4-5
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.22.0ubuntu1
   apt  2.7.3
  SourcePackage: alsa-plugins
  Title: package libasound2-plugins 1.2.7.1-1ubuntu2 failed to install/upgrade: 
trying to overwrite shared 
'/etc/alsa/conf.d/99-pulseaudio-default.conf.example', which is different from 
other instances of package libasound2-plugins:i386
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-plugins/+bug/2051350/+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 2050831] Re: Performance

2024-01-30 Thread Eduardo Barretto
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug.  I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privilege boundaries nor directly cause loss of data/privacy.
Please feel free to report any other bugs you may find.

** Information type changed from Private Security to Public

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

Title:
  Performance

Status in xorg package in Ubuntu:
  New

Bug description:
  Hello, inside Steam, in big picture mode, in system, system
  information, the vram memory has a negative value, it is not showing
  the real amount that the onboard reaches, supports. I think it's the
  video driver, or some other driver.

  There are also some fps losses, games that reach 60fps, at various
  times it is below, like 45fps or less. Even switching to maximum
  performance mode by clicking on the system battery icon.

  When I connect the PC to a smart TV as the primary screen, with HDMI, full 
HD, the image is blurry, as if there were blurs in the images.
  In the TV settings, it is set to maximum contrast and sharpness.

  Also another feedback: in languages, in the system settings, I can't
  download the missing packages, the download button is not shown. This
  happens after installing the system in minimal mode, and then
  installing other additional programs. I will send the name of the
  programs.

  sudo apt install --install-recommends guvcview rhythmbox libreoffice
  psensor

  Lenovo Ideapad 3 15itl6 82md
  Linux Kubuntu lts 22.04
  Kde plasma
  1920x1080p 60hz
  4gb ram
  20gb swap
  btfrs
  ptbr utf8 abnt2

  Steam (.deb), from the Steam website.

  samsung smarttv, 32 inches, un32t4300

  In the system settings, on monitor, the scale is at 100%

  Thank you in advance, success always
  

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3
  Uname: Linux 6.5.0-14-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: KDE
  Date: Mon Jan 22 17:09:37 2024
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Device [8086:9a78] (rev 03) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Device [17aa:3f9c]
  InstallationDate: Installed on 2024-01-13 (9 days ago)
  InstallationMedia: Kubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.1)
  MachineType: LENOVO 82MD
  ProcEnviron:
   LANGUAGE=pt_BR:pt:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pt_BR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-6.5.0-14-generic 
root=UUID=58277c11-b933-4491-8d44-0caa0d498477 ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/06/2023
  dmi.bios.release: 1.57
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GGCN57WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0T76466 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: IdeaPad 3 15ITL6
  dmi.ec.firmware.release: 1.57
  dmi.modalias: 
dmi:bvnLENOVO:bvrGGCN57WW:bd09/06/2023:br1.57:efr1.57:svnLENOVO:pn82MD:pvrIdeaPad315ITL6:rvnLENOVO:rnLNVNB161216:rvrSDK0T76466WIN:cvnLENOVO:ct10:cvrIdeaPad315ITL6:skuLENOVO_MT_82MD_BU_idea_FM_IdeaPad315ITL6:
  dmi.product.family: IdeaPad 3 15ITL6
  dmi.product.name: 82MD
  dmi.product.sku: LENOVO_MT_82MD_BU_idea_FM_IdeaPad 3 15ITL6
  dmi.product.version: IdeaPad 3 15ITL6
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~22.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/2050831/+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 2051350] [NEW] package libasound2-plugins 1.2.7.1-1ubuntu2 failed to install/upgrade: trying to overwrite shared '/etc/alsa/conf.d/99-pulseaudio-default.conf.example', which is

2024-01-30 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

wa installing wine

ProblemType: Package
DistroRelease: Ubuntu 23.10
Package: libasound2-plugins 1.2.7.1-1ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-15.15.1-lowlatency 6.5.3
Uname: Linux 6.5.0-15-lowlatency x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
CasperMD5CheckResult: pass
Date: Fri Jan 26 10:23:45 2024
DuplicateSignature:
 package:libasound2-plugins:1.2.7.1-1ubuntu2
 Unpacking libasound2-plugins:i386 (1.2.7.1-1ubuntu2) ...
 dpkg: error processing archive 
/tmp/apt-dpkg-install-LCQD0p/134-libasound2-plugins_1.2.7.1-1ubuntu2_i386.deb 
(--unpack):
  trying to overwrite shared 
'/etc/alsa/conf.d/99-pulseaudio-default.conf.example', which is different from 
other instances of package libasound2-plugins:i386
ErrorMessage: trying to overwrite shared 
'/etc/alsa/conf.d/99-pulseaudio-default.conf.example', which is different from 
other instances of package libasound2-plugins:i386
InstallationDate: Installed on 2024-01-25 (1 days ago)
InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1)
Python3Details: /usr/bin/python3.11, Python 3.11.6, python3-minimal, 3.11.4-5
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.22.0ubuntu1
 apt  2.7.3
SourcePackage: alsa-plugins
Title: package libasound2-plugins 1.2.7.1-1ubuntu2 failed to install/upgrade: 
trying to overwrite shared 
'/etc/alsa/conf.d/99-pulseaudio-default.conf.example', which is different from 
other instances of package libasound2-plugins:i386
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package mantic need-duplicate-check package-conflict
-- 
package libasound2-plugins 1.2.7.1-1ubuntu2 failed to install/upgrade: trying 
to overwrite shared '/etc/alsa/conf.d/99-pulseaudio-default.conf.example', 
which is different from other instances of package libasound2-plugins:i386
https://bugs.launchpad.net/bugs/2051350
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to alsa-plugins in Ubuntu.

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


[Desktop-packages] [Bug 2051694] [NEW] Regression: Kubuntu 22.04 LTS overrides Xorg.conf-specified monitor layout

2024-01-30 Thread Stephan Sokolow
Public bug reported:

When I built a new PC with Kubuntu 22.04 LTS, I carried over my recently
purchased GeForce RTX 3060 and copied over the Xorg.conf that was doing
perfectly well for me in 20.04 LTS, containing the following line:

Option  "metamodes" "HDMI-0: 1280x1024 +3200+0, DP-3:
1280x1024 +0+0, DP-1: 1920x1080 +1280+0"

(Bear in mind that, due to a history of bugginess in KScreen2 and how it
interacts with Plasma panel layouts, I disable it in the Background
Services control panel and do my best to lock down the allowed layouts
and resolutions in Xorg.conf.)

This technique has been working for me for close to a decade, with my
previous video card being a GeForce GTX750 and, if I remember correctly,
I was also using it with the GeForce GT430 I was using before that, and
with Kubuntu and Lubuntu versions going back to at least Kubuntu 16.04
LTS and likely to Lubuntu 14.04 and possibly even Lubuntu 12.04.

However, much to my dismay, it appeared to have no effect, and the
system was still assigning a virtual layout that didn't match the
physical arrangement of the monitors.

Eventually, I realized from /var/log/Xorg.0.log that my metamodes line
WAS getting set, but, for reasons I still have no idea how to diagnose,
something else was overriding it and resetting the metamodes line back
to the undesired default, with unlocked resolutions and an incorrect
monitor layout.

[21.689] (II) NVIDIA(0): Setting mode "HDMI-0: 1280x1024 @1280x1024 +3200+0 
{ViewPortIn=1280x1024, ViewPortOut=1280x1024+0+0}, DP-3: 1280x1024 @1280x1024 
+0+0 {ViewPortIn=1280x1024, ViewPortOut=1280x1024+0+0}, DP-1: 
nvidia-auto-select @1920x1080 +0+0 {ViewPortIn=1920x1080, 
ViewPortOut=1920x1080+0+0}"
[21.747] (II) NVIDIA(0): Setting mode "DP-3: 1280x1024 @1280x1024 +0+0 
{ViewPortIn=1280x1024, ViewPortOut=1280x1024+0+0}, DP-1: nvidia-auto-select 
@1920x1080 +0+0 {ViewPortIn=1920x1080, ViewPortOut=1920x1080+0+0}"
[21.834] (II) NVIDIA(0): Setting mode "HDMI-0: nvidia-auto-select 
@1280x1024 +1920+0 {ViewPortIn=1280x1024, ViewPortOut=1280x1024+0+0}, DP-3: 
1280x1024 @1280x1024 +0+0 {ViewPortIn=1280x1024, ViewPortOut=1280x1024+0+0}, 
DP-1: nvidia-auto-select @1920x1080 +0+0 {ViewPortIn=1920x1080, 
ViewPortOut=1920x1080+0+0}"
[21.922] (II) NVIDIA(0): Setting mode "HDMI-0: nvidia-auto-select 
@1280x1024 +1920+0 {ViewPortIn=1280x1024, ViewPortOut=1280x1024+0+0}, DP-3: 
nvidia-auto-select @1280x1024 +3200+0 {ViewPortIn=1280x1024, 
ViewPortOut=1280x1024+0+0}, DP-1: nvidia-auto-select @1920x1080 +0+0 
{ViewPortIn=1920x1080, ViewPortOut=1920x1080+0+0}"

As a workaround which may or may not show up in the ubuntu-bug report,
I've created a /etc/X11/Xsession.d/01-fix-the-damn-ignored-metamodes
file containing the line `xrandr --output DP-3 --left-of DP-1`.

...though that doesn't fix the monitor layout at the login screen and
it's not possible to work around the forced changeability of the
resolution without a working metamodes according to
https://gitlab.freedesktop.org/xorg/xserver/-/issues/353#note_91110

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3
Uname: Linux 6.5.0-14-generic x86_64
NonfreeKernelModules: zfs nvidia_modeset nvidia
.proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
.proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
.proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.suspend: suspend hibernate resume
.proc.driver.nvidia.suspend_depth: default modeset uvm
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  535.146.02  Sun Dec  3 
14:06:14 UTC 2023
 GCC version:  gcc version 12.3.0 (Ubuntu 12.3.0-1ubuntu1~22.04)
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: KDE
Date: Tue Jan 30 06:25:44 2024
DistUpgraded: Fresh install
DistroCodename: jammy
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 NVIDIA Corporation GA106 [GeForce RTX 3060 Lite Hash Rate] [10de:2504] (rev 
a1) (prog-if 00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. GA106 [GeForce RTX 3060 Lite Hash Rate] 
[1043:8810]
 Advanced Micro Devices, Inc. [AMD/ATI] Device [1002:164e] (rev c6) (prog-if 00 
[VGA controller])
   Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Device [1002:164e]
InstallationDate: Installed on 2024-01-05 (24 days ago)
InstallationMedia: Kubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.1)
MachineType: ASRock B650 PG Lightning
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-14-generic 
root=UUID=7aefb7ca-223b-4111-81e4-0d2a1003dbce ro 
zfs.zfs_dmu_offset_next_sync=0 quiet splash vt.handoff=7
RebootRequiredPkgs: Error: path contained symlinks.
SourcePackage: xorg
Symptom: display

[Desktop-packages] [Bug 1970069] Re: Annoying boot messages interfering with splash screen

2024-01-30 Thread Daniel van Vugt
** Also affects: systemd (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  Annoying boot messages interfering with splash screen

Status in linux package in Ubuntu:
  In Progress
Status in plymouth package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  New

Bug description:
  Since upgrading from 20.04.6 Desktop to 22.04, the boot screen is not
  as clean as it used to be.

  Basically, the flow used to be in 20.04:

  GRUB > Splash screen > Login prompt

  Currently in 22.04:

  GRUB > Splash screen > Messages (in the attached file) > Splash screen
  again for a sec > Login prompt

  All of those messages already existed in 20.04, the difference is that
  they were not appearing during boot.

  I was able to get rid of the "usb" related messages by just adding
  "loglevel=0" in GRUB. Currently is "quiet loglevel=0 splash".

  Regarding the fsck related message, I can get rid of them by adding
  "fsck.mode=skip".

  However, I do not want to just disable fsck or set the loglevel to 0.
  This is not a sustainable solution.

  Something definitely changed here. These messages are not of enough
  relevance to be shown at boot by default, and they should remain
  hidden like they were in Focal.

  Obviously a minor issue, but important to the whole look and feel of
  the OS for desktop.

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