[Desktop-packages] [Bug 1955001] [NEW] File reading speed is slow
Public bug reported: I created the user's home directory on the computer's mechanical hard drive, but the user's login speed is very slow, and the speed of viewing the file content in the desktop environment is slow. At the same time, I tested the hard disk read speed: hdparm -Tt /dev/sdb /dev/sdb: Timing cached reads: 23962 MB in 2.00 seconds = 11993.56 MB/sec Timing buffered disk reads: 456 MB in 3.00 seconds = 151.78 MB/sec There is no problem with the read speed of the hard disk. And when I have a lot of data exchange while running a python program, the speed used to be 3s, but now it suddenly becomes 30-50s. The above is when my computer is running well. ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New -- 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/1955001 Title: File reading speed is slow Status in nautilus package in Ubuntu: New Bug description: I created the user's home directory on the computer's mechanical hard drive, but the user's login speed is very slow, and the speed of viewing the file content in the desktop environment is slow. At the same time, I tested the hard disk read speed: hdparm -Tt /dev/sdb /dev/sdb: Timing cached reads: 23962 MB in 2.00 seconds = 11993.56 MB/sec Timing buffered disk reads: 456 MB in 3.00 seconds = 151.78 MB/sec There is no problem with the read speed of the hard disk. And when I have a lot of data exchange while running a python program, the speed used to be 3s, but now it suddenly becomes 30-50s. The above is when my computer is running well. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1955001/+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 1851250] Re: [snap] chromium-browser snap cannot upload files outside ~
Hi Olivier! I tried on hirsute, and it's working :-) Then I guess that the only series still supported by Canonical and affected by this bug are the LTSes. ** Also affects: chromium-browser (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: chromium-browser (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: chromium-browser (Ubuntu Focal) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1851250 Title: [snap] chromium-browser snap cannot upload files outside ~ Status in chromium-browser package in Ubuntu: Confirmed Status in chromium-browser source package in Xenial: New Status in chromium-browser source package in Bionic: New Status in chromium-browser source package in Focal: New Bug description: After upgrading from 19.04 to 19.10, my Chromium package was converted to a snap. After figuring out how to manually reconnect the password manager, and figuring out how to apply CHROMIUM_FLAGS that used to live in /etc/chromium-browser/default, and noticing that GMail is no longer able to play a sound when a call comes in, now I see that I am unable to upload files from anywhere except my home directory! Connecting chromium:removable-media as in https://bugs.launchpad.net/ubuntu/+source/chromium- browser/+bug/1832711 does not help with anything else. Is there some way to let the file upload dialog work on any file my user account has access to? Or run this snap in --classic mode? If not, this seems like a critical limitation, as I need this multiple times a day. Switching to Chrome or Firefox cannot be the only workaround for this, surely? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1851250/+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 1954980] [NEW] Chromium showing Japanese fonts incorrectly
Public bug reported: It simply shows square rectangles for all Japanese characters this occurred after a recent update (earlier this week), a restart fixed it the first time but now it has reverted, probably after another update. ProblemType: Bug DistroRelease: Ubuntu 20.04 ProcVersionSignature: Ubuntu 5.4.0-91.102-generic 5.4.151 Uname: Linux 5.4.0-91-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Dec 16 11:54:12 2021 InstallationDate: Installed on 2019-02-08 (1041 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Snap: chromium 96.0.4664.110 (latest/stable) SnapSource: ubuntu/+source/chromium-browser UpgradeStatus: Upgraded to focal on 2021-12-01 (14 days ago) ** Affects: chromium-browser (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal snap ** Attachment added: "screenshot of the problem" https://bugs.launchpad.net/bugs/1954980/+attachment/5547906/+files/chromium_bug.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1954980 Title: Chromium showing Japanese fonts incorrectly Status in chromium-browser package in Ubuntu: New Bug description: It simply shows square rectangles for all Japanese characters this occurred after a recent update (earlier this week), a restart fixed it the first time but now it has reverted, probably after another update. ProblemType: Bug DistroRelease: Ubuntu 20.04 ProcVersionSignature: Ubuntu 5.4.0-91.102-generic 5.4.151 Uname: Linux 5.4.0-91-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Dec 16 11:54:12 2021 InstallationDate: Installed on 2019-02-08 (1041 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Snap: chromium 96.0.4664.110 (latest/stable) SnapSource: ubuntu/+source/chromium-browser UpgradeStatus: Upgraded to focal on 2021-12-01 (14 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1954980/+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 1954970] [NEW] remmina "Cannot connect to the RDP server ... via TLS. Check that the client and server support a common TLS version"
Public bug reported: Xubuntu Jammy (21.04) after upgrade libfreerdp-client2-2 (2.3.0+dfsg1-2ubuntu2 => 2.4.1+dfsg1-1) libfreerdp2-2 (2.3.0+dfsg1-2ubuntu2 => 2.4.1+dfsg1-1) Remmina can't connect to any RDP server (Win2008 R2) with error: "Cannot connect to the RDP server ... via TLS. Check that the client and server support a common TLS version" Rollback to Impish version of libs libfreerdp-client2-2 2.3.0+dfsg1-2ubuntu2 libfreerdp2-2 2.3.0+dfsg1-2ubuntu2 makes it work normal. ** Affects: freerdp2 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to freerdp2 in Ubuntu. https://bugs.launchpad.net/bugs/1954970 Title: remmina "Cannot connect to the RDP server ... via TLS. Check that the client and server support a common TLS version" Status in freerdp2 package in Ubuntu: New Bug description: Xubuntu Jammy (21.04) after upgrade libfreerdp-client2-2 (2.3.0+dfsg1-2ubuntu2 => 2.4.1+dfsg1-1) libfreerdp2-2 (2.3.0+dfsg1-2ubuntu2 => 2.4.1+dfsg1-1) Remmina can't connect to any RDP server (Win2008 R2) with error: "Cannot connect to the RDP server ... via TLS. Check that the client and server support a common TLS version" Rollback to Impish version of libs libfreerdp-client2-2 2.3.0+dfsg1-2ubuntu2 libfreerdp2-2 2.3.0+dfsg1-2ubuntu2 makes it work normal. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/freerdp2/+bug/1954970/+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 1954956] Re: [amdgpu] System crash
Thanks for the bug report. It looks like the amdgpu kernel driver is crashing and experiencing other problems. Can you please try: * The official Ubuntu kernel * https://kernel.ubuntu.com/~kernel-ppa/mainline/drm-tip/current/ ** Summary changed: - Xorg crash + [amdgpu] System crash ** Package changed: xorg (Ubuntu) => linux (Ubuntu) ** Changed in: linux (Ubuntu) Status: New => Incomplete ** Tags added: amdgpu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1954956 Title: [amdgpu] System crash Status in linux package in Ubuntu: Incomplete Bug description: System crashes about 3 times a day; no appearant relation to application or process or triggering situation. Happens constantly. Random time between incidents normally several hours. This is a problem for month now. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xorg 1:7.7+22ubuntu1 Uname: Linux 5.14.0-051400drmtip20210904-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.4 Architecture: amd64 BootLog: CasperMD5CheckResult: unknown CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Wed Dec 15 23:01:59 2021 DistUpgraded: Fresh install DistroCodename: hirsute DistroVariant: ubuntu DkmsStatus: vhba, 20211023, 5.11.0-42-generic, x86_64: installed vhba, 20211023, 5.11.0-44-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8] (rev c8) (prog-if 00 [VGA controller]) Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8] InstallationDate: Installed on 2020-12-16 (364 days ago) InstallationMedia: Ubuntu 16.04.7 LTS "Xenial Xerus" - Release amd64 (20200806) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcEnviron: LANGUAGE=de_DE TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.14.0-051400drmtip20210904-generic root=UUID=54c9f67c-180d-4545-8531-aef138dc5e0a ro SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: No upgrade log present (probably fresh install) XorgConf: Section "InputClass" Identifier "middle button emulation class" MatchIsPointer "on" Option "Emulate3Buttons" "on" EndSection dmi.bios.date: 06/18/2020 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P4.20 dmi.board.name: B450 Pro4 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP4.20:bd06/18/2020:br5.14:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.:rvnASRock:rnB450Pro4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. mtime.conffile..etc.apport.crashdb.conf: 2021-08-13T12:52:00.669929 version.compiz: compiz 1:0.9.14.1+20.10.20200813-0ubuntu4 version.libdrm2: libdrm2 2.4.105-3~21.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3 version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.3-0ubuntu0.3 version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-2build1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1 xserver.bootTime: Wed Dec 15 15:19:50 2021 xserver.configfile: /etc/X11/xorg.conf xserver.errors: AMDGPU(0): Failed to make import prime FD as pixmap: 22 xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.20.11-1ubuntu1.2 xserver.video_driver: amdgpu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1954956/+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 1954911] Re: Xorg freeze
Thanks for the bug report. Please: 1. Reboot, plug in the monitor and reproduce the bug again; a failed boot or system freeze. 2. Wait 10 seconds while it is frozen. 3. Power off the machine. 4. Unplug the monitor. 5. Boot the machine normally. 6. Run this command: journalctl -b-1 > prevboot.txt 7. Attach the resulting text file here. ** Summary changed: - Xorg freeze + [i915] [penyrn] System freeze when HDMI is plugged in ** Package changed: xorg (Ubuntu) => linux (Ubuntu) ** Summary changed: - [i915] [penyrn] System freeze when HDMI is plugged in + [i915] [penryn] System freeze when HDMI is plugged in -- 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/1954911 Title: [i915] [penryn] System freeze when HDMI is plugged in Status in linux package in Ubuntu: Confirmed Bug description: When I try to hookup my laptop to a smart TV using an HDMI it will not boot up at all. With my laptop running after booting normally and I plugin the HDMI cable it freeze up and the only way to unfreeze it is to hold the power down until it shuts off. I've done this at least twice maybe three times. Its like there is not an HDMI driver installed. I have been a computer tech since 1984 but as you know learning a new operating system is very time consuming. I started with Dr. DOS 6.0 and it was a great OP System but than of course MicroShaft but them out of business then I finally had to go to MS DOS 4.0 and its been down hill ever since. I'm 64 and working my way into Linux. Any ideas would be great ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-66.74-generic 5.4.86 Uname: Linux 5.4.0-66-generic x86_64 NonfreeKernelModules: lkp_Ubuntu_5_4_0_66_74_generic_81 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Dec 15 05:09:06 2021 DistUpgraded: 2020-12-17 01:37:02,155 DEBUG icon theme changed, re-reading DistroCodename: focal DistroVariant: ubuntu DpkgLog: ExtraDebuggingInterest: Yes GpuHangFrequency: This is the first time GraphicsCard: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Sony Corporation Mobile 4 Series Chipset Integrated Graphics Controller [104d:9035] Subsystem: Sony Corporation Mobile 4 Series Chipset Integrated Graphics Controller [104d:9035] MachineType: Sony Corporation VGN-FW351J ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-66-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to focal on 2020-12-17 (363 days ago) dmi.bios.date: 11/07/2008 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: R2050Y0 dmi.board.asset.tag: N/A dmi.board.name: VAIO dmi.board.vendor: Sony Corporation dmi.board.version: N/A dmi.chassis.asset.tag: N/A dmi.chassis.type: 10 dmi.chassis.vendor: Sony Corporation dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrR2050Y0:bd11/07/2008:svnSonyCorporation:pnVGN-FW351J:pvrC60184W1:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A: dmi.product.family: N/A dmi.product.name: VGN-FW351J dmi.product.sku: N/A dmi.product.version: C60184W1 dmi.sys.vendor: Sony Corporation version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1954911/+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 1946096] Re: Support manual firmware upgrading for Foxconn and Quectel modems.
** Changed in: oem-priority Status: In Progress => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/1946096 Title: Support manual firmware upgrading for Foxconn and Quectel modems. Status in OEM Priority Project: Fix Released Status in modemmanager package in Ubuntu: Fix Released Status in modemmanager source package in Focal: Fix Released Status in modemmanager source package in Hirsute: Fix Released Bug description: [Impact] The modem certification requires that different modem firmware is used for different network carrier. This needs the firmware upgrading capability during the modem certification process. The modem manufacture vendors (Foxconn and Quectel) provided utilities to do modem's firmware upgrading manually.(LP#1943774, LP#1943780) These utilities are verified to be working when the recent versions(> v 1.18.2) of ModemManager are used with. To support manual firmware upgrading on the current Focal release which is using ModemManager v 1.16.6, we need to apply some patches from v 1.18.2. The requested upstream patches are listed as below: * for Quectel EM160 4G ** https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/83ac82470589a3672092a0ba0be855093b1cf5e2 * for Foxconn T99W175 ** https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/21ae558fe3600c84b3ca7dcd9bf50a3ba576c7c9 **https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/76e700f4fd703f952208993330ab098305c13d6b ** https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/52bf2c641171ded9e617022f40497c8984520371 ** https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/33e2b023ef01bea9da37ae2beb192f7d92bce47a ** https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/f72046701659073fbfa97516e155865647acb154 The firmware upgrading was verified using the patched ModemManager v 1.16.6 with the following 2 modems: * Foxconn SDX55 T99W175 5G sub6 PCIE Modem * Quectel SDX24 EM160R-GL 4G LTE CAT16 PCIE Modem [Test Plan] 1. Install the Ubuntu image. 2. Boot and login the system. 3. Verify if the modem is working 4. Prepare the modem’s firmware and install the firmware upgrading application provided by Foxconn and Quectel 5. Using the firmware upgrading application to upgrade the modem’s firmware 6. Verify if the modem’s firmware upgrading is successful 7. Reboot 8. Verify if the upgraded modem firmware is still working --- Regression test --- Verify if one USB modem are still working with these patches for PCIe modems. [Where problems could occur] The requested update has 2 parts: 1. Informative 1.1 Provide more information about modems whose drivers use WWAN subsystem in kernel 5.13 1.2 Modem manufacture's private utilities can use this information to do modem's FW upgrading manually 2. Changes are specific to Foxconn and Quectel modems 2.1 Modified code are only used by Foxconn and Quectel modems during their FW upgrading. (matched by vendor_id and product_id) In current Ubuntu's certification records for modem: * No other modem uses WWAN subsystem in kernel 5.13 * Modem's FW update is not supported via ModemManager ( < v1.18 ) There is no certificated modems can do the firmware upgrading flow for the regression test. This update should not affect existing modems. The problem would be limited to these two mentioned modems. Each carrier mapping .conf file is for a specific modem. ModemManager will load one of the carrier mapping conf files via the modem manufacturer’s plugin ( if the PCIe VID & PID is matched by the plugin.) We cannot verify if the carrier mapping is correct. This relies on the manufacturer to provide the correct mapping. The carrier mapping .conf files is verified by modem’s manufacture according to the tested SIM card published by different countries. Modem manufacturer confirmed that the content in the .conf file is absolutely correct. [Other Info] The firmware and the upgrading utilities can be downloaded from the following link: * LP#1943774 for Quectel modems * LP#1943780 for Foxconn modems To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1946096/+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 1943816] Re: "ubuntu-drivers install" needs to be used when installing nvidia-driver if enabling "third-party packages"
Create iso with live-build and import ubuntu-drivers-common 0.9.0~0.20.04.4 from focal-proposed. Install Ubuntu with "third-party packages" enabled. After installation finished, '/run/nvidia_runtimepm_supported' had been created and use 'prime-select query' get 'on-demand' ** Tags removed: verification-needed verification-needed-focal ** Tags added: verification-done verification-done-focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1943816 Title: "ubuntu-drivers install" needs to be used when installing nvidia- driver if enabling "third-party packages" Status in OEM Priority Project: Confirmed Status in subiquity: New Status in ubiquity package in Ubuntu: New Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in ubiquity source package in Focal: New Status in ubuntu-drivers-common source package in Focal: Fix Committed Bug description: ubiquity calls ``` ubuntu-drivers install $FREEONLY $NOOEM --package-list /run/ubuntu-drivers.autoinstall ``` to generate package list during live system but "ubuntu-drivers install" not only install packages but also create some config files for switching nvidia mode (e.g. on-demand) and change the runtime config as well (e.g. modify the iniramfs). Thus, not only package list needs to be referred but also the configuration. --- In ubuntu-drivers-common, which read the "/run/ubuntu-drivers.autoinstall" to install package. It also skipping the nvidia-mode changing (made by ubuntu-drivers install). ``` $ cat ubiquity/target-config/31ubuntu_driver_packages #!/bin/sh set -e # install all packages that "ubuntu-drivers autoinstall" installed into the # live system. Ubiquity calls this with --package-list /run/ubuntu-drivers.autoinstall PKGLIST=/run/ubuntu-drivers.autoinstall [ -e $PKGLIST ] || exit 0 for p in `cat $PKGLIST`; do apt-install $p done ``` --- We need to use a same approach to make sure the nvidia mode is same on a same system (either all handing by ubuntu-drivers install or change the logic to maintainer script in each package). --- [Impact] * According to Nvidia README, the RTD3 (Runtime D3) doesn't support on non-laptop machine * Install Ubuntu with "third-party packages" enabled, will not get same GPU configuration by running "ubuntu-drivers install" * Patch make system not enable RTD3 unless it's a laptop and set default GPU mode to "on-demand" [Test Plan] * Create Focal iso with live-build and import ubuntu-drivers-common from -proposed * Install Ubuntu on machine, in "Updates and other software" page select "Install third-party software for graphics and Wi-Fi hardware and additional media formats" * On laptop with Nvidia RTD3 supported GPU. The configuration file '/run/nvidia_runtimepm_supported' will be created. * Call "prime-select query" to make sure the default mode is "on-demand" [Where problems could occur] * With non-laptop machine use RTD3 supported GPU may use more power [Other Info] * For RTD3 (Runtime D3) doesn't support on non-laptop machine, refer to https://bugs.launchpad.net/oem-priority/+bug/1942788 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1943816/+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 1954956] [NEW] Xorg crash
Public bug reported: System crashes about 3 times a day; no appearant relation to application or process or triggering situation. Happens constantly. Random time between incidents normally several hours. This is a problem for month now. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xorg 1:7.7+22ubuntu1 Uname: Linux 5.14.0-051400drmtip20210904-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.4 Architecture: amd64 BootLog: CasperMD5CheckResult: unknown CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Wed Dec 15 23:01:59 2021 DistUpgraded: Fresh install DistroCodename: hirsute DistroVariant: ubuntu DkmsStatus: vhba, 20211023, 5.11.0-42-generic, x86_64: installed vhba, 20211023, 5.11.0-44-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8] (rev c8) (prog-if 00 [VGA controller]) Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8] InstallationDate: Installed on 2020-12-16 (364 days ago) InstallationMedia: Ubuntu 16.04.7 LTS "Xenial Xerus" - Release amd64 (20200806) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcEnviron: LANGUAGE=de_DE TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.14.0-051400drmtip20210904-generic root=UUID=54c9f67c-180d-4545-8531-aef138dc5e0a ro SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: No upgrade log present (probably fresh install) XorgConf: Section "InputClass" Identifier "middle button emulation class" MatchIsPointer "on" Option "Emulate3Buttons" "on" EndSection dmi.bios.date: 06/18/2020 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P4.20 dmi.board.name: B450 Pro4 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP4.20:bd06/18/2020:br5.14:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.:rvnASRock:rnB450Pro4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. mtime.conffile..etc.apport.crashdb.conf: 2021-08-13T12:52:00.669929 version.compiz: compiz 1:0.9.14.1+20.10.20200813-0ubuntu4 version.libdrm2: libdrm2 2.4.105-3~21.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3 version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.3-0ubuntu0.3 version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-2build1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1 xserver.bootTime: Wed Dec 15 15:19:50 2021 xserver.configfile: /etc/X11/xorg.conf xserver.errors: AMDGPU(0): Failed to make import prime FD as pixmap: 22 xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.20.11-1ubuntu1.2 xserver.video_driver: amdgpu ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug crash hirsute third-party-packages 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/1954956 Title: Xorg crash Status in xorg package in Ubuntu: New Bug description: System crashes about 3 times a day; no appearant relation to application or process or triggering situation. Happens constantly. Random time between incidents normally several hours. This is a problem for month now. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xorg 1:7.7+22ubuntu1 Uname: Linux 5.14.0-051400drmtip20210904-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.4 Architecture: amd64 BootLog: CasperMD5CheckResult: unknown CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Wed Dec 15 23:01:59 2021 DistUpgraded: Fresh install DistroCodename: hirsute DistroVariant: ubuntu DkmsStatus: vhba, 20211023, 5.11.0-42-generic, x86_64: installed vhba, 20211023, 5.11.0-44-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8] (rev c8) (prog-if 00 [VGA controller]) Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8] InstallationDate: Installed on 2020-12-16 (364 days ago) InstallationMedia: Ubuntu 16.04.7 LTS "Xenial Xerus" - Release amd64 (20200806) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
[Desktop-packages] [Bug 1951624] Re: OpenSSL 3.0 transition might lead to unsupported protocols
** Changed in: wpa (Ubuntu) Importance: Undecided => High ** Tags added: rls-jj-incoming -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1951624 Title: OpenSSL 3.0 transition might lead to unsupported protocols Status in wpa package in Ubuntu: New Bug description: OpenSSL 3.0, which is planned to land in the archive Very Soon™, has moved quite a few algorithms to its "legacy" provider, which isn't loaded by default. Some of those algorithms are used in various protocols implemented by wpa_supplicant, so it's likely that the package will be broken in this regard. Sadly, this isn't caught by either the build-time tests nor the autopkgtests. A first good step would be to patch wpa_supplicant to load the "legacy" provider (and the default one too, cf https://www.openssl.org/docs/manmaster/man7/crypto.html , look for "legacy"). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1951624/+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 1941752]
(In reply to Gordon Lack from comment #21) Seems to be related to how old the jpegs are. 2016 and earlier it crashes. 2017 and late its OK. Roughly. If I run gwenview on the command line for a failing one this is what I see reported: [gmllaptop]: gwenview DSCN1657.JPG org.kde.kdegraphics.gwenview.lib: Unresolved mime type "image/x-mng" org.kde.kdegraphics.gwenview.lib: Unresolved raw mime type "image/x-nikon-nrw" org.kde.kdegraphics.gwenview.lib: Unresolved raw mime type "image/x-samsung-srw" terminate called after throwing an instance of 'std::out_of_range' what(): basic_string::at: __n (which is 19) >= this->size() (which is 19) KCrash: crashing... crashRecursionCounter = 2 KCrash: Application Name = gwenview path = /usr/bin pid = 15230 KCrash: Arguments: /usr/bin/gwenview DSCN1657.JPG KCrash: Attempting to start /usr/lib/x86_64-linux-gnu/libexec/drkonqi [1]+ Stopped gwenview DSCN1657.JPG [gmllaptop]: fg gwenview DSCN1657.JPG QSocketNotifier: Invalid socket 8 and type 'Read', disabling... QSocketNotifier: Invalid socket 10 and type 'Read', disabling... QSocketNotifier: Invalid socket 13 and type 'Read', disabling... QSocketNotifier: Invalid socket 18 and type 'Read', disabling... ; ^C [gmllaptop]: fg bash: fg: current: no such job [gmllaptop]: gwenview DSCN1657.JPG org.kde.kdegraphics.gwenview.lib: Unresolved mime type "image/x-mng" org.kde.kdegraphics.gwenview.lib: Unresolved raw mime type "image/x-nikon-nrw" org.kde.kdegraphics.gwenview.lib: Unresolved raw mime type "image/x-samsung-srw" terminate called after throwing an instance of 'std::out_of_range' what(): basic_string::at: __n (which is 19) >= this->size() (which is 19) KCrash: crashing... crashRecursionCounter = 2 KCrash: Application Name = gwenview path = /usr/bin pid = 15230 KCrash: Arguments: /usr/bin/gwenview DSCN1657.JPG KCrash: Attempting to start /usr/lib/x86_64-linux-gnu/libexec/drkonqi [1]+ Stopped gwenview DSCN1657.JPG [gmllaptop]: fg gwenview DSCN1657.JPG QSocketNotifier: Invalid socket 8 and type 'Read', disabling... QSocketNotifier: Invalid socket 10 and type 'Read', disabling... QSocketNotifier: Invalid socket 13 and type 'Read', disabling... QSocketNotifier: Invalid socket 18 and type 'Read', disabling... ; ^C [gmllaptop]: fg bash: fg: current: no such job -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to exiv2 in Ubuntu. https://bugs.launchpad.net/bugs/1941752 Title: Regression: exiv2 0.27.3-3ubuntu1.5 makes Gwenview crash when opening images exported by darktable Status in Gwenview: Unknown Status in exiv2 package in Ubuntu: Confirmed Status in gwenview package in Ubuntu: Confirmed Bug description: Since the recent security update of exiv2, Gwenview crashes when trying to open image files that got exported by darktable. Steps to reproduce: * Make a test installation of Kubuntu 21.04 in VirtualBox * Install all updates * Install darktable * Copy one of the images in /usr/share/wallpapers (or any other image) to your home directory and open it with darktable * Within darktable, export a copy of the image (no need to do any actual modifications) * Try to open that copy with Gwenview. Gwenview will crash. I'm attaching a crash report hinting that this is related to exiv2. Temporary workaround: If I downgrade libexiv2-27 to 0.27.3-3ubuntu1.4, Gwenview doesn't crash, so it seems the crash is related to changes in 0.27.3-3ubuntu1.5. I don't know if the underlying cause is actually some bug in exiv2, Gwenview or darktable. Kind regards, Jan ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: libexiv2-27 0.27.3-3ubuntu1.5 ProcVersionSignature: Ubuntu 5.11.0-31.33-generic 5.11.22 Uname: Linux 5.11.0-31-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Thu Aug 26 15:16:47 2021 InstallationDate: Installed on 2021-08-26 (0 days ago) InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) SourcePackage: exiv2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gwenview/+bug/1941752/+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 1941752]
Created attachment 144559 New crash information added by DrKonqi gwenview (21.08.1) using Qt 5.15.2 - What I was doing when the application crashed: Browsing through images with Dolphin. Select to open one in Gwenview. Crashes every time. -- Backtrace (Reduced): #4 __pthread_kill_implementation (no_tid=0, signo=6, threadid=140466192913600) at pthread_kill.c:44 #5 __pthread_kill_internal (signo=6, threadid=140466192913600) at pthread_kill.c:80 #6 __GI___pthread_kill (threadid=140466192913600, signo=signo@entry=6) at pthread_kill.c:91 #7 0x7fc0dafab476 in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26 #8 0x7fc0daf917b7 in __GI_abort () at abort.c:79 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to exiv2 in Ubuntu. https://bugs.launchpad.net/bugs/1941752 Title: Regression: exiv2 0.27.3-3ubuntu1.5 makes Gwenview crash when opening images exported by darktable Status in Gwenview: Unknown Status in exiv2 package in Ubuntu: Confirmed Status in gwenview package in Ubuntu: Confirmed Bug description: Since the recent security update of exiv2, Gwenview crashes when trying to open image files that got exported by darktable. Steps to reproduce: * Make a test installation of Kubuntu 21.04 in VirtualBox * Install all updates * Install darktable * Copy one of the images in /usr/share/wallpapers (or any other image) to your home directory and open it with darktable * Within darktable, export a copy of the image (no need to do any actual modifications) * Try to open that copy with Gwenview. Gwenview will crash. I'm attaching a crash report hinting that this is related to exiv2. Temporary workaround: If I downgrade libexiv2-27 to 0.27.3-3ubuntu1.4, Gwenview doesn't crash, so it seems the crash is related to changes in 0.27.3-3ubuntu1.5. I don't know if the underlying cause is actually some bug in exiv2, Gwenview or darktable. Kind regards, Jan ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: libexiv2-27 0.27.3-3ubuntu1.5 ProcVersionSignature: Ubuntu 5.11.0-31.33-generic 5.11.22 Uname: Linux 5.11.0-31-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Thu Aug 26 15:16:47 2021 InstallationDate: Installed on 2021-08-26 (0 days ago) InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) SourcePackage: exiv2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gwenview/+bug/1941752/+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 1954943] [NEW] ubuntu-bug crashed while reporting an audio issue
Public bug reported: When trying to report an audio issue using "ubuntu-bug", pulse audio crashed. The original audio bug I was trying to report and was not able to was: All audio skips the first 2 seconds AFTER the video starts or continues. This happens in YOUTUBE, VLC etc, in all videos that have audio, the audio skips the first two seconds. If I rewind the video to the beginning, the audio starts correctly as expected. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.13 ProcVersionSignature: Ubuntu 5.11.0-43.47~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-43-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: steve 1093 F pulseaudio /dev/snd/controlC1: steve 1093 F pulseaudio /dev/snd/pcmC1D3p: steve 1093 F...m pulseaudio CasperMD5CheckResult: skip Date: Wed Dec 15 13:00:24 2021 InstallationDate: Installed on 2021-05-11 (218 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio Symptom: audio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/18/2012 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: FB dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: 970A-DS3 dmi.board.vendor: AMD Corporation dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrFB:bd10/18/2012:br4.6:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:skuTobefilledbyO.E.M.:rvnAMDCorporation:rn970A-DS3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: To be filled by O.E.M. dmi.product.sku: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- 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/1954943 Title: ubuntu-bug crashed while reporting an audio issue Status in pulseaudio package in Ubuntu: New Bug description: When trying to report an audio issue using "ubuntu-bug", pulse audio crashed. The original audio bug I was trying to report and was not able to was: All audio skips the first 2 seconds AFTER the video starts or continues. This happens in YOUTUBE, VLC etc, in all videos that have audio, the audio skips the first two seconds. If I rewind the video to the beginning, the audio starts correctly as expected. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.13 ProcVersionSignature: Ubuntu 5.11.0-43.47~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-43-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: steve 1093 F pulseaudio /dev/snd/controlC1: steve 1093 F pulseaudio /dev/snd/pcmC1D3p: steve 1093 F...m pulseaudio CasperMD5CheckResult: skip Date: Wed Dec 15 13:00:24 2021 InstallationDate: Installed on 2021-05-11 (218 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio Symptom: audio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/18/2012 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: FB dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: 970A-DS3 dmi.board.vendor: AMD Corporation dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrFB:bd10/18/2012:br4.6:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:skuTobefilledbyO.E.M.:rvnAMDCorporation:rn970A-DS3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: To be filled by O.E.M. dmi.product.sku: To be filled by O.E.M.
[Desktop-packages] [Bug 1954939] [NEW] Cannot open additional instances of the same file with the same name inside a zip archive
Public bug reported: This issue is very simple. A zip file can legally contain multiple entries with the same name in the same path. If you attempt to open a file that has the same name and path as another, you can only open one of them, and cannot open the other. An example zip file has been provided which contains two `fabric.mod.json` files. If either one of them is double clicked within file roller, it will only open one of them, and never the other. example.zip | | fabric.mod.json (2.1kb) | fabric.mod.json (484 bytes) For me, the 484 byte file is always opened, even if you double click the 2.1kb file. Ubuntu 21.10 file-roller 3.40.0-2 ** Affects: file-roller (Ubuntu) Importance: Undecided Status: New ** Attachment added: "Example zip file which can be used to demonstrate the issue" https://bugs.launchpad.net/bugs/1954939/+attachment/5547843/+files/example.zip ** Summary changed: - Cannot open additional instances of the same file with the same name inside a zip + Cannot open additional instances of the same file with the same name inside a zip archive -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to file-roller in Ubuntu. https://bugs.launchpad.net/bugs/1954939 Title: Cannot open additional instances of the same file with the same name inside a zip archive Status in file-roller package in Ubuntu: New Bug description: This issue is very simple. A zip file can legally contain multiple entries with the same name in the same path. If you attempt to open a file that has the same name and path as another, you can only open one of them, and cannot open the other. An example zip file has been provided which contains two `fabric.mod.json` files. If either one of them is double clicked within file roller, it will only open one of them, and never the other. example.zip | | fabric.mod.json (2.1kb) | fabric.mod.json (484 bytes) For me, the 484 byte file is always opened, even if you double click the 2.1kb file. Ubuntu 21.10 file-roller 3.40.0-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/file-roller/+bug/1954939/+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 1951066] Re: [MIR] dh-elpa
Override component to main dh-elpa 2.0.9ubuntu1 in jammy: universe/misc -> main dh-elpa 2.0.9ubuntu1 in jammy amd64: universe/devel/optional/100% -> main dh-elpa 2.0.9ubuntu1 in jammy arm64: universe/devel/optional/100% -> main dh-elpa 2.0.9ubuntu1 in jammy armhf: universe/devel/optional/100% -> main dh-elpa 2.0.9ubuntu1 in jammy i386: universe/devel/optional/100% -> main dh-elpa 2.0.9ubuntu1 in jammy ppc64el: universe/devel/optional/100% -> main dh-elpa 2.0.9ubuntu1 in jammy riscv64: universe/devel/optional/100% -> main dh-elpa 2.0.9ubuntu1 in jammy s390x: universe/devel/optional/100% -> main dh-elpa-helper 2.0.9ubuntu1 in jammy amd64: universe/devel/optional/100% -> main dh-elpa-helper 2.0.9ubuntu1 in jammy arm64: universe/devel/optional/100% -> main dh-elpa-helper 2.0.9ubuntu1 in jammy armhf: universe/devel/optional/100% -> main dh-elpa-helper 2.0.9ubuntu1 in jammy i386: universe/devel/optional/100% -> main dh-elpa-helper 2.0.9ubuntu1 in jammy ppc64el: universe/devel/optional/100% -> main dh-elpa-helper 2.0.9ubuntu1 in jammy riscv64: universe/devel/optional/100% -> main dh-elpa-helper 2.0.9ubuntu1 in jammy s390x: universe/devel/optional/100% -> main 15 publications overridden. ** Changed in: dh-elpa (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to dh-elpa in Ubuntu. https://bugs.launchpad.net/bugs/1951066 Title: [MIR] dh-elpa Status in cmake package in Ubuntu: Invalid Status in dh-elpa package in Ubuntu: Fix Released Status in dh-elpa package in Debian: New Bug description: [Availability] The package src:dh-elpa is already in Ubuntu universe. The package dh-elpa-helper build for the architectures it is designed to work on It currently builds and works for architectures: all (arch independent) Link to package [[https://launchpad.net/ubuntu/+source/dh-elpa|src:dh-elpa]] It is enough to promote the dh-elpa-helper binary to main. [Rationale] - The package dh-elpa-helper is required in Ubuntu main as src:cmake dependency - The package src:dh-helper will not generally be useful for a large part of our user base, but is important/helpful still because it is a higher level abstraction layer around src:emacsen-common that is used by src:cmake and others to unify the installation of elpa packages (like "cmake-mode"). - Additional reasons: we provided syntax highlighting and indentation for CMakeLists.txt and *.cmake source files in emacs previously and do not want to drop that. - Additionally new use-cases enabled by this are: NONE, just keeping status quo - Package dh-elpa covers the same use case as emacsen-common, but is better because it is a higher level abstraction layer, thereby we want to put it on top to avoid common errors such as https://bugs.debian.org/802915 - The package dh-elpa-helper is a new runtime dependency of package cmake-data that we already support [Security] - No CVEs/security issues in this software in the past - no `suid` or `sgid` binaries - no executables in `/sbin` and `/usr/sbin` - Package does not install services - Packages does not open privileged ports (ports < 1024) - Packages does not contain extensions to security-sensitive software (filters, scanners, plugins, UI skins, ...) – it provides an extension to the debhelper build environment, tho. [Quality assurance - function/usage] - The package works well right after install – if elpa dehbehlper and ${elpa:Depends} are being used [Quality assurance - maintenance] - The package is maintained well in Debian/Ubuntu and has not too many and long term critical bugs open - Ubuntu https://bugs.launchpad.net/ubuntu/+source/dh-elpa/+bug => 0 bugs - Debian https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=dh-elpa => no critical bugs, but 1 long standing bug, classified as "important" https://bugs.debian.org/886024 It cannot be reproduced by the upstream developers and morphed more into a proposal that the maintainers are unconvinced of, therefore it stalled => Another interesting bug is https://bugs.debian.org/995936 that is being discussed as of recently and would remove the Ubuntu delta if resolved. - The package does not deal with exotic hardware we cannot support [Quality assurance - testing] - The package does not run a test at build time. ELPA_NAME is set and ./dh_elpa executed but that doesn't seem to fail the build anything is wrong. - The package does not run an autopkgtest because non is provided in debian/tests - README.org states a limitation: "This tool is currently not very well tested." - We could try adding an autopkgtest that builds a simple elpa package, as descibed in https://wiki.debian.org/Teams/DebianEmacsenTeam/elpa-hello, that we could maybe also run at build time. [Quality assurance -
[Desktop-packages] [Bug 1851250] Re: [snap] chromium-browser snap cannot upload files outside ~
I'm reopening this bug in light of Alberto's recent findings. Alberto, it would be useful if you could test this on a more recent system, e.g. impish, and report whether with a new enough version of the portal, opening/saving files anywhere on the filesystem works. ** Changed in: chromium-browser (Ubuntu) Status: Invalid => Confirmed ** Tags added: snap ** Changed in: chromium-browser (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1851250 Title: [snap] chromium-browser snap cannot upload files outside ~ Status in chromium-browser package in Ubuntu: Confirmed Bug description: After upgrading from 19.04 to 19.10, my Chromium package was converted to a snap. After figuring out how to manually reconnect the password manager, and figuring out how to apply CHROMIUM_FLAGS that used to live in /etc/chromium-browser/default, and noticing that GMail is no longer able to play a sound when a call comes in, now I see that I am unable to upload files from anywhere except my home directory! Connecting chromium:removable-media as in https://bugs.launchpad.net/ubuntu/+source/chromium- browser/+bug/1832711 does not help with anything else. Is there some way to let the file upload dialog work on any file my user account has access to? Or run this snap in --classic mode? If not, this seems like a critical limitation, as I need this multiple times a day. Switching to Chrome or Firefox cannot be the only workaround for this, surely? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1851250/+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 1851250] Re: [snap] chromium-browser snap cannot upload files outside ~
After some good hints from Oliver I did some investigation on this issue. Indeed it looks like the chromium snap is doing the right thing: it first checks if the D-Bus service "org.freedesktop.portal.Desktop" is running (if not, it falls back on calling ListActivatableNames, which is not ideal because this currently gets blocked by AppArmor -- but in my tests the call to NameHasOwner works, so this path is not even taken), and then it checks that the "version" property on the "org.freedesktop.portal.FileChooser" interface is at least 3. Unfortunately, on my Focal system this version is 2 (version 3 was released just about at the time when Focal was: https://github.com/flatpak/xdg-desktop- portal/commit/00b28db5ca45bcbdfea0ddfff8447a3f8836bfd9), so the portal dialog is not used. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1851250 Title: [snap] chromium-browser snap cannot upload files outside ~ Status in chromium-browser package in Ubuntu: Invalid Bug description: After upgrading from 19.04 to 19.10, my Chromium package was converted to a snap. After figuring out how to manually reconnect the password manager, and figuring out how to apply CHROMIUM_FLAGS that used to live in /etc/chromium-browser/default, and noticing that GMail is no longer able to play a sound when a call comes in, now I see that I am unable to upload files from anywhere except my home directory! Connecting chromium:removable-media as in https://bugs.launchpad.net/ubuntu/+source/chromium- browser/+bug/1832711 does not help with anything else. Is there some way to let the file upload dialog work on any file my user account has access to? Or run this snap in --classic mode? If not, this seems like a critical limitation, as I need this multiple times a day. Switching to Chrome or Firefox cannot be the only workaround for this, surely? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1851250/+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 1950214] Re: raspi 64 bit Impish image fails update-initramfs with OOM on zstd
Upload to the current Ubuntu serie, Dave did you want to SRU that to impish? If so could you work on an update patch and SRUfy the reports? ** Changed in: ubuntu-settings (Ubuntu Jammy) Status: Confirmed => Fix Committed ** Changed in: ubuntu-settings (Ubuntu Jammy) Assignee: (unassigned) => Dave Jones (waveform) ** Changed in: ubuntu-settings (Ubuntu Impish) Assignee: (unassigned) => Dave Jones (waveform) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/1950214 Title: raspi 64 bit Impish image fails update-initramfs with OOM on zstd Status in ubuntu-settings package in Ubuntu: Fix Committed Status in ubuntu-settings source package in Impish: Confirmed Status in ubuntu-settings source package in Jammy: Fix Committed Bug description: When attempting to 'apt upgrade' on the pi zero 2 with the 64 bit Impish image and nothing new installed to it, update-initramfs fails like so: Setting up linux-firmware (1.201.1) ... update-initramfs: Generating /boot/initrd.img-5.13.0-1008-raspi Killed E: mkinitramfs failure zstd -q -19 -T0 137 A simple workaround for now is to switch to the old lz4 default: $ sudo apt install lz4 $ sudo sed -i -e '/^COMPRESS=/ c COMPRESS=lz4' /etc/initramfs-tools/initramfs.conf Original Workaround === Adding a swap file to the setup allowed 'apt -f install' to run successfully. How the device was setup 1) xzcat | dd the sdcard with the impish 64 bit server image 2) setup for serial over USB (dtoverlay=dwc2, modules-load=dwc2,g_serial, link getty@ttyGS0.service ) as suggested in https://www.tal.org/tutorials/raspberry-pi-zero-usb-serial-console 3) resize partition 2 - fdisk delete partition 2 and recreate to use the rest of the 16GB flash, e2fsck, resize2fs 4) cp bcm2710-rpi-3-b.dtb bcm2710-rpi-zero-2.dtb per https://waldorf.waveform.org.uk/2021/the-pi-zero-2.html 5) boot, connect to wireless, ssh in 6) apt update && apt upgrade 7) observe above issue ProblemType: Package DistroRelease: Ubuntu 21.10 Package: linux-firmware 1.201.1 ProcVersionSignature: Ubuntu 5.13.0-1009.10-raspi 5.13.14 Uname: Linux 5.13.0-1009-raspi aarch64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Nov 8 19:47 seq crw-rw 1 root audio 116, 33 Nov 8 19:47 timer AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.13.0-1009-raspi. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu71 Architecture: arm64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: unknown Date: Mon Nov 8 21:00:59 2021 Dependencies: ErrorMessage: installed linux-firmware package post-installation script subprocess returned error exit status 1 ImageMediaBuild: 20211013 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lspci: Lspci-vt: -[:00]- Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=dwc2/1p, 480M PackageArchitecture: all PciMultimedia: ProcFB: 0 BCM2708 FB ProcKernelCmdLine: coherent_pool=1M 8250.nr_uarts=1 snd_bcm2835.enable_compat_alsa=0 snd_bcm2835.enable_hdmi=1 bcm2708_fb.fbwidth=720 bcm2708_fb.fbheight=480 bcm2708_fb.fbswap=1 smsc95xx.macaddr=B8:27:EB:5C:DA:C8 vc_mem.mem_base=0x1ec0 vc_mem.mem_size=0x2000 dwc_otg.lpm_enable=0 console=ttyS0,115200 console=tty1 root=LABEL=writable rootfstype=ext4 elevator=deadline rootwait fixrtc quiet splash modules-load=dwc2,g_serial Python3Details: /usr/bin/python3.9, Python 3.9.7, python3-minimal, 3.9.4-1build1 PythonDetails: N/A RelatedPackageVersions: grub-pc N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux-firmware StagingDrivers: bcm2835_mmal_vchiq snd_bcm2835 bcm2835_isp bcm2835_v4l2 bcm2835_codec vc_sm_cma Title: package linux-firmware 1.201.1 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) acpidump: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/1950214/+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 1954928] [NEW] package libgtk-3-0:amd64 3.24.25-1ubuntu4.1 failed to install/upgrade: dependency problems - leaving triggers unprocessed
Public bug reported: Trying to install through Synaptic ProblemType: Package DistroRelease: Ubuntu 21.04 Package: libgtk-3-0:amd64 3.24.25-1ubuntu4.1 ProcVersionSignature: Ubuntu 5.11.0-41.45-generic 5.11.22 Uname: Linux 5.11.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.4 Architecture: amd64 CasperMD5CheckResult: unknown Date: Tue Dec 14 10:23:27 2021 ErrorMessage: dependency problems - leaving triggers unprocessed InstallationDate: Installed on 2021-12-08 (6 days ago) InstallationMedia: Lubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) Python3Details: /usr/bin/python3.9, Python 3.9.5, python3-minimal, 3.9.4-1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.20.9ubuntu1 apt 2.2.4ubuntu0.1 SourcePackage: gtk+3.0 Title: package libgtk-3-0:amd64 3.24.25-1ubuntu4.1 failed to install/upgrade: dependency problems - leaving triggers unprocessed UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gtk+3.0 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package hirsute -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1954928 Title: package libgtk-3-0:amd64 3.24.25-1ubuntu4.1 failed to install/upgrade: dependency problems - leaving triggers unprocessed Status in gtk+3.0 package in Ubuntu: New Bug description: Trying to install through Synaptic ProblemType: Package DistroRelease: Ubuntu 21.04 Package: libgtk-3-0:amd64 3.24.25-1ubuntu4.1 ProcVersionSignature: Ubuntu 5.11.0-41.45-generic 5.11.22 Uname: Linux 5.11.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.4 Architecture: amd64 CasperMD5CheckResult: unknown Date: Tue Dec 14 10:23:27 2021 ErrorMessage: dependency problems - leaving triggers unprocessed InstallationDate: Installed on 2021-12-08 (6 days ago) InstallationMedia: Lubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) Python3Details: /usr/bin/python3.9, Python 3.9.5, python3-minimal, 3.9.4-1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.20.9ubuntu1 apt 2.2.4ubuntu0.1 SourcePackage: gtk+3.0 Title: package libgtk-3-0:amd64 3.24.25-1ubuntu4.1 failed to install/upgrade: dependency problems - leaving triggers unprocessed UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1954928/+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 1945368]
Certainly the blank calendar needs a solution if it is not yet resolved. I leave it to Richard and Anje to decide whether the bug continues and how to most efficiently proceed - whether this bug report should be reopened, or deserves a new new bug report. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1945368 Title: Thunderbird 91 forgets default calendar Status in Mozilla Thunderbird: Invalid Status in thunderbird package in Ubuntu: New Bug description: Upon upgrading from Thunderbird 78 to 91, the default calendar for new events that I selected has been forgotten. I has Google set as the default, but Thunderbird 91 has changed the default to a local calendar that I rarely use. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: thunderbird 1:91.1.1+build2-0ubuntu1 ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13 Uname: Linux 5.13.0-16-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu69 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: alistair 2076 F pulseaudio BuildID: 20210916142849 CasperMD5CheckResult: unknown Channel: Unavailable CurrentDesktop: Unity:Unity7:ubuntu Date: Tue Sep 28 22:11:42 2021 ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) # Include files from /etc/network/interfaces.d: source-directory /etc/network/interfaces.d IncompatibleExtensions: Lightning - {e2fda1a4-762b-4020-b5ad-a41df1933103} English (GB) Language Pack - langpack-en...@thunderbird.mozilla.org Thunderbird (default) - {972ce4c6-7e08-4474-a285-3208198ce6fd} InstallationDate: Installed on 2020-07-14 (441 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IpRoute: default via 172.30.3.254 dev wlp0s20f3 proto dhcp metric 600 10.0.0.0/24 dev wg0 proto kernel scope link src 10.0.0.2 169.254.0.0/16 dev wg0 scope link metric 1000 172.30.0.0/22 dev wlp0s20f3 proto kernel scope link src 172.30.0.92 metric 600 PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/thunderbird/omni.ja:greprefs.js:359 PrefSources: prefs.js Profiles: Profile0 (Default) - LastVersion=91.1.1/20210916142849 (In use) RunningIncompatibleAddons: True SourcePackage: thunderbird UpgradeStatus: Upgraded to impish on 2021-09-24 (4 days ago) dmi.bios.date: 06/21/2021 dmi.bios.release: 1.19 dmi.bios.vendor: LENOVO dmi.bios.version: N2WET29W (1.19 ) dmi.board.asset.tag: Not Available dmi.board.name: 20U9CTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.8 dmi.modalias: dmi:bvnLENOVO:bvrN2WET29W(1.19):bd06/21/2021:br1.19:efr1.8:svnLENOVO:pn20U9CTO1WW:pvrThinkPadX1CarbonGen8:skuLENOVO_MT_20U9_BU_Think_FM_ThinkPadX1CarbonGen8:rvnLENOVO:rn20U9CTO1WW:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon Gen 8 dmi.product.name: 20U9CTO1WW dmi.product.sku: LENOVO_MT_20U9_BU_Think_FM_ThinkPad X1 Carbon Gen 8 dmi.product.version: ThinkPad X1 Carbon Gen 8 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/1945368/+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 1949637] Re: Libreoffice crash
This is definitely related to the user profile, deleting it fixes the problem for a day or two. -- 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/1949637 Title: Libreoffice crash Status in libreoffice package in Ubuntu: Confirmed Bug description: Libreoffice crashed on startup: sven@:~/$ libreoffice terminate called after throwing an instance of 'com::sun::star::lang::IllegalArgumentException' Unspecified Application Error I've removed Libreoffice completely, installed it again via the Software-Center and it crashes again. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: libreoffice 1:7.2.2-0ubuntu0.21.10.1 ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14 Uname: Linux 5.13.0-20-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Nov 3 21:25:16 2021 InstallationDate: Installed on 2019-10-03 (762 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190923) SourcePackage: libreoffice UpgradeStatus: Upgraded to impish on 2021-10-17 (17 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1949637/+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 1954911] [NEW] Xorg freeze
Public bug reported: When I try to hookup my laptop to a smart TV using an HDMI it will not boot up at all. With my laptop running after booting normally and I plugin the HDMI cable it freeze up and the only way to unfreeze it is to hold the power down until it shuts off. I've done this at least twice maybe three times. Its like there is not an HDMI driver installed. I have been a computer tech since 1984 but as you know learning a new operating system is very time consuming. I started with Dr. DOS 6.0 and it was a great OP System but than of course MicroShaft but them out of business then I finally had to go to MS DOS 4.0 and its been down hill ever since. I'm 64 and working my way into Linux. Any ideas would be great ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-66.74-generic 5.4.86 Uname: Linux 5.4.0-66-generic x86_64 NonfreeKernelModules: lkp_Ubuntu_5_4_0_66_74_generic_81 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Dec 15 05:09:06 2021 DistUpgraded: 2020-12-17 01:37:02,155 DEBUG icon theme changed, re-reading DistroCodename: focal DistroVariant: ubuntu DpkgLog: ExtraDebuggingInterest: Yes GpuHangFrequency: This is the first time GraphicsCard: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Sony Corporation Mobile 4 Series Chipset Integrated Graphics Controller [104d:9035] Subsystem: Sony Corporation Mobile 4 Series Chipset Integrated Graphics Controller [104d:9035] MachineType: Sony Corporation VGN-FW351J ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-66-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to focal on 2020-12-17 (363 days ago) dmi.bios.date: 11/07/2008 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: R2050Y0 dmi.board.asset.tag: N/A dmi.board.name: VAIO dmi.board.vendor: Sony Corporation dmi.board.version: N/A dmi.chassis.asset.tag: N/A dmi.chassis.type: 10 dmi.chassis.vendor: Sony Corporation dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrR2050Y0:bd11/07/2008:svnSonyCorporation:pnVGN-FW351J:pvrC60184W1:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A: dmi.product.family: N/A dmi.product.name: VGN-FW351J dmi.product.sku: N/A dmi.product.version: C60184W1 dmi.sys.vendor: Sony Corporation version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal freeze 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/1954911 Title: Xorg freeze Status in xorg package in Ubuntu: New Bug description: When I try to hookup my laptop to a smart TV using an HDMI it will not boot up at all. With my laptop running after booting normally and I plugin the HDMI cable it freeze up and the only way to unfreeze it is to hold the power down until it shuts off. I've done this at least twice maybe three times. Its like there is not an HDMI driver installed. I have been a computer tech since 1984 but as you know learning a new operating system is very time consuming. I started with Dr. DOS 6.0 and it was a great OP System but than of course MicroShaft but them out of business then I finally had to go to MS DOS 4.0 and its been down hill ever since. I'm 64 and working my way into Linux. Any ideas would be great ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-66.74-generic 5.4.86 Uname: Linux 5.4.0-66-generic x86_64 NonfreeKernelModules: lkp_Ubuntu_5_4_0_66_74_generic_81 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Dec 15 05:09:06 2021 DistUpgraded: 2020-12-17 01:37:02,155 DEBUG icon theme changed, re-reading DistroCodename: focal DistroVariant: ubuntu
[Desktop-packages] [Bug 1954902] [NEW] lpoptions cannot change system-wide default printer
Public bug reported: According to "man lpoptions": > When run by the root user, lpoptions gets and sets default options and > instances for all users in the /etc/cups/lpoptions file. Otherwise, > the per-user defaults are managed in the ~/.cups/lpoptions file. According to my experimentation, this is incorrect. When lpoptions is run as root, the file "/root/.cups/lpoptions" is updated (aka the personal default printer of root), not "/etc/cups/lpoptions" (aka the system-wide default printer). I'm unsure whether this is a documentation bug or wrong behavior. I assume the later, because there seems to be no other option to set the system-wide default printer. root@mi553-022:~# lsb_release -rd Description:Ubuntu 20.04.3 LTS Release:20.04 root@mi553-022:~# apt-cache policy cups cups: Installed: 2.3.1-9ubuntu1.1 Candidate: 2.3.1-9ubuntu1.1 Version table: *** 2.3.1-9ubuntu1.1 500 500 http://ftp.luis.uni-hannover.de/ubuntu focal-updates/main amd64 Packages 500 http://ftp.luis.uni-hannover.de/ubuntu focal-security/main amd64 Packages 100 /var/lib/dpkg/status 2.3.1-9ubuntu1 500 500 http://ftp.luis.uni-hannover.de/ubuntu focal/main amd64 Packages 2.2.7-1ubuntu2.8 500 500 http://ftp.luis.uni-hannover.de/ubuntu bionic-security/main amd64 Packages ** Affects: cups (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1954902 Title: lpoptions cannot change system-wide default printer Status in cups package in Ubuntu: New Bug description: According to "man lpoptions": > When run by the root user, lpoptions gets and sets default options and > instances for all users in the /etc/cups/lpoptions file. Otherwise, > the per-user defaults are managed in the ~/.cups/lpoptions file. According to my experimentation, this is incorrect. When lpoptions is run as root, the file "/root/.cups/lpoptions" is updated (aka the personal default printer of root), not "/etc/cups/lpoptions" (aka the system-wide default printer). I'm unsure whether this is a documentation bug or wrong behavior. I assume the later, because there seems to be no other option to set the system-wide default printer. root@mi553-022:~# lsb_release -rd Description: Ubuntu 20.04.3 LTS Release: 20.04 root@mi553-022:~# apt-cache policy cups cups: Installed: 2.3.1-9ubuntu1.1 Candidate: 2.3.1-9ubuntu1.1 Version table: *** 2.3.1-9ubuntu1.1 500 500 http://ftp.luis.uni-hannover.de/ubuntu focal-updates/main amd64 Packages 500 http://ftp.luis.uni-hannover.de/ubuntu focal-security/main amd64 Packages 100 /var/lib/dpkg/status 2.3.1-9ubuntu1 500 500 http://ftp.luis.uni-hannover.de/ubuntu focal/main amd64 Packages 2.2.7-1ubuntu2.8 500 500 http://ftp.luis.uni-hannover.de/ubuntu bionic-security/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1954902/+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 1713021] Re: Minimize/unminimize animations do nothing for the first 100ms or so
** Description changed: gnome-shell's minimize/unminimize animations do nothing for almost the first 100ms or so. They look slow because the easeInExpo curve does nothing for most of the first half of the animation time: - https://developer.gnome.org/clutter/stable/ClutterTimeline.html#ClutterAnimationMode + https://gitlab.gnome.org/GNOME/clutter/-/blob/master/doc/reference/easing- + modes.svg A much more responsive, natural and fluid curve with the same overall duration would be to use an easeOut* curve. -- 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/1713021 Title: Minimize/unminimize animations do nothing for the first 100ms or so Status in GNOME Shell: Expired Status in gnome-shell package in Ubuntu: Triaged Bug description: gnome-shell's minimize/unminimize animations do nothing for almost the first 100ms or so. They look slow because the easeInExpo curve does nothing for most of the first half of the animation time: https://gitlab.gnome.org/GNOME/clutter/-/blob/master/doc/reference/easing- modes.svg A much more responsive, natural and fluid curve with the same overall duration would be to use an easeOut* curve. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1713021/+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 1954901] [NEW] Emacs desktop file doesn't use a hi-res icon and hence the icon is pixelated in hi-res displays
Public bug reported: On my Dell Precision 5530 laptop with a 4K display and 200% scaling in KDE Plasma, the icon used by the emacs desktop file looks pixelated because it is not a high-res version. I am using the 'Large icons' version of the alt-tab switcher in Plasma. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: emacs-gtk 1:27.1+1-3ubuntu3 ProcVersionSignature: Ubuntu 5.13.0-22.22-generic 5.13.19 Uname: Linux 5.13.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Wed Dec 15 15:23:58 2021 InstallationDate: Installed on 2021-12-02 (13 days ago) InstallationMedia: Kubuntu 21.10 "Impish Indri" - Release amd64 (20211012) SourcePackage: emacs UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: emacs (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug impish ** Description changed: On my Dell Precision 5530 laptop with a 4K display and 200% scaling in KDE Plasma, the icon used by the emacs desktop file looks pixelated - because it is not a high-res version. + because it is not a high-res version. I am using the 'Large icons' + version of the alt-tab switcher in Plasma. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: emacs-gtk 1:27.1+1-3ubuntu3 ProcVersionSignature: Ubuntu 5.13.0-22.22-generic 5.13.19 Uname: Linux 5.13.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Wed Dec 15 15:23:58 2021 InstallationDate: Installed on 2021-12-02 (13 days ago) InstallationMedia: Kubuntu 21.10 "Impish Indri" - Release amd64 (20211012) SourcePackage: emacs UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to emacs in Ubuntu. https://bugs.launchpad.net/bugs/1954901 Title: Emacs desktop file doesn't use a hi-res icon and hence the icon is pixelated in hi-res displays Status in emacs package in Ubuntu: New Bug description: On my Dell Precision 5530 laptop with a 4K display and 200% scaling in KDE Plasma, the icon used by the emacs desktop file looks pixelated because it is not a high-res version. I am using the 'Large icons' version of the alt-tab switcher in Plasma. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: emacs-gtk 1:27.1+1-3ubuntu3 ProcVersionSignature: Ubuntu 5.13.0-22.22-generic 5.13.19 Uname: Linux 5.13.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Wed Dec 15 15:23:58 2021 InstallationDate: Installed on 2021-12-02 (13 days ago) InstallationMedia: Kubuntu 21.10 "Impish Indri" - Release amd64 (20211012) SourcePackage: emacs UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/emacs/+bug/1954901/+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 1954649] Re: autopkgtest regressions with python3.10 as supported
migration-reference/0 tests for all affected packages triggered -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pygobject in Ubuntu. https://bugs.launchpad.net/bugs/1954649 Title: autopkgtest regressions with python3.10 as supported Status in ipywidgets package in Ubuntu: New Status in pygobject package in Ubuntu: New Status in pytest-twisted package in Ubuntu: New Status in python-b2sdk package in Ubuntu: New Status in python-hypothesis package in Ubuntu: New Status in python-taskflow package in Ubuntu: New Status in python3-defaults package in Ubuntu: New Status in skimage package in Ubuntu: Invalid Status in supysonic package in Ubuntu: New Status in vorta package in Ubuntu: New Status in ipywidgets package in Debian: New Status in pygobject package in Debian: New Status in pytest-twisted package in Debian: New Status in python-b2sdk package in Debian: New Status in python-hypothesis package in Debian: Unknown Status in supysonic package in Debian: New Status in vorta package in Debian: Unknown Bug description: This bug is for tracking the packages having autopkgtest regressions with python3.10 as a supported version, blocking migration of python3-defaults/3.9.7-4. All packages are in universe except pygobject and python-taskflow in main. All packages have RC bugs in Debian except python-taskflow which is based on a newer upstream version. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ipywidgets/+bug/1954649/+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 1865838] Re: no error displayed on failed fingerprint authentication
** Changed in: oem-priority Status: New => Fix Committed ** Changed in: oem-priority Status: Fix Committed => Fix Released -- 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/1865838 Title: no error displayed on failed fingerprint authentication Status in gdm: New Status in OEM Priority Project: Fix Released Status in fprintd package in Ubuntu: Invalid Status in gdm3 package in Ubuntu: Invalid Status in gnome-shell package in Ubuntu: Fix Released Status in fprintd source package in Focal: Invalid Status in gdm3 source package in Focal: Invalid Status in gnome-shell source package in Focal: Fix Released Status in gnome-shell source package in Groovy: Fix Released Bug description: [ Impact ] No fingerprint errors are exposed on fingerprint login failures. from journalctl, gdm-fingerprint shows error there after retried 5 times of fingerprint login failed, so I open this issue here. [ Test case ] 1. enroll fingerprint for your right index finger. 2. logout 3. login and try login by incorrect finger e.g. middle finger 4. Each time the wrong finger is used an error is shown 5. After 3 times retries, an authentication error is shown, suggesting to use another method. [ Regression potential] Wrong errors are shown during both fingerprint auth and other kinds of authentications. Password failures aren't properly exposed. Verification can't restart on error. Password authentication doesn't work anymore for users with no enrolled prints (as per LP: #1915570) --- ProblemType: BugDistroRelease: Ubuntu 20.04 Package: gdm3 3.34.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Mar 3 15:32:00 2020 InstallationDate: Installed on 2020-03-02 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200301)SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/1865838/+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