[Desktop-packages] [Bug 1978429] [NEW] Crashes when smart info is open while the drive is pulled
Public bug reported: 1. Open smart data for a given drive (not the boot drive, *points at step 2*) 2. detach drive from system (sata drives support hot swap) 3. wait a few seconds 4. disk utility has crashed if smart info is not open it will not crash and the drive drops out of the drive list the smart data window should either close or remain open and stop updating if the drive is removed ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-disk-utility 42.0-1ubuntu1 Uname: Linux 5.17.13-051713-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Sun Jun 12 22:42:11 2022 InstallationDate: Installed on 2021-11-26 (198 days ago) InstallationMedia: Kubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211126) RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: gnome-disk-utility UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-disk-utility (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-disk-utility in Ubuntu. https://bugs.launchpad.net/bugs/1978429 Title: Crashes when smart info is open while the drive is pulled Status in gnome-disk-utility package in Ubuntu: New Bug description: 1. Open smart data for a given drive (not the boot drive, *points at step 2*) 2. detach drive from system (sata drives support hot swap) 3. wait a few seconds 4. disk utility has crashed if smart info is not open it will not crash and the drive drops out of the drive list the smart data window should either close or remain open and stop updating if the drive is removed ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-disk-utility 42.0-1ubuntu1 Uname: Linux 5.17.13-051713-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Sun Jun 12 22:42:11 2022 InstallationDate: Installed on 2021-11-26 (198 days ago) InstallationMedia: Kubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211126) RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: gnome-disk-utility UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-disk-utility/+bug/1978429/+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 1977695] Re: Xorg fails to start: (EE) Error parsing the config file
It's not slow adopters -- We encourage all Nvidia users to stick to Xorg. And Nvidia does still contribute to the Xorg project. -- 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/1977695 Title: Xorg fails to start: (EE) Error parsing the config file Status in xorg-server package in Ubuntu: Invalid Bug description: Description: Ubuntu 22.04 LTS Release: 22.04 xorg: Installed: 1:7.7+23ubuntu2 Candidate: 1:7.7+23ubuntu2 Version table: *** 1:7.7+23ubuntu2 500 500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status 1. Uncomment WaylandEnable=false in /etc/gdm3/custom.conf 2. Reboot. 3. See black screen after selecting Ubuntu at GRUB prompt. Login screen never loads. Unplugging any external monitors appears to have no effect on the bug. I am aware that most users of Ubuntu 22.04 see an option at the login screen to change the display manager. I have never seen such an option. My machine always uses Wayland unless I modify /etc/gdm3/custom.conf directly. Using Wayland is detrimental to my health, because the Night Light feature does nothing. I have nvidia- driver-510 installed. I am happy to provide further debugging information upon request. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-35.36-generic 5.15.35 Uname: Linux 5.15.0-35-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 510.73.05 Sat May 7 05:30:26 UTC 2022 GCC version: ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Jun 5 15:47:31 2022 DistUpgraded: 2022-05-07 18:27:00,043 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation HD Graphics 630 [8086:591b] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company HD Graphics 630 [103c:8259] Subsystem: Hewlett-Packard Company GP107M [GeForce GTX 1050 Mobile] [103c:8259] InstallationDate: Installed on 2020-12-09 (543 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: HP OMEN by HP Laptop ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.15.0-35-generic root=UUID=13d7b775-7783-44fc-8e24-164127457fd4 ro rootflags=subvol=@ quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to jammy on 2022-05-08 (28 days ago) dmi.bios.date: 12/22/2020 dmi.bios.release: 15.56 dmi.bios.vendor: Insyde dmi.bios.version: F.56 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8259 dmi.board.vendor: HP dmi.board.version: 83.72 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 83.72 dmi.modalias: dmi:bvnInsyde:bvrF.56:bd12/22/2020:br15.56:efr83.72:svnHP:pnOMENbyHPLaptop:pvrType1ProductConfigId:rvnHP:rn8259:rvr83.72:cvnHP:ct10:cvrChassisVersion:skuW2N35UAR#ABA: dmi.product.family: 103C_5335KV HP Omen dmi.product.name: OMEN by HP Laptop dmi.product.sku: W2N35UAR#ABA dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2 version.libgl1-mesa-glx: libgl1-mesa-glx 22.0.1-1ubuntu2 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3 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-server/+bug/1977695/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to :
[Desktop-packages] [Bug 1978428] [NEW] PCI/internal sound card not detected ALC4080 ASUS Z690 MB
Public bug reported: I have a fresh install of Ubuntu 22.04 Jammy on my ASUS Z690 motherboard with an intel i7 12700K. Ever since the fresh install I am unable to have any sound play through the rear or front audio jacks. I believe it is a problem with ubuntu not being able to recognize the sound card on the MB since this hardware seems to be very very new. It also seems that snd-hda-intel is unable to find any codecs for the sound card or even identify the onboard sound card. Here is the output of dmesg | grep 'snd': [5.426209] snd_hda_intel :00:1f.3: enabling device ( -> 0002) [5.426494] snd_hda_intel :01:00.1: enabling device ( -> 0002) [5.426528] snd_hda_intel :01:00.1: Disabling MSI [5.426531] snd_hda_intel :01:00.1: Handle vga_switcheroo audio client [6.438789] snd_hda_intel :00:1f.3: azx_get_response timeout, switching to polling mode: last cmd=0x000f [7.446910] snd_hda_intel :00:1f.3: No response from codec, disabling MSI: last cmd=0x000f [8.458944] snd_hda_intel :00:1f.3: Codec #0 probe error; disabling it... [9.470934] snd_hda_intel :00:1f.3: azx_get_response timeout, switching to single_cmd mode: last cmd=0x000f [9.471592] snd_hda_intel :00:1f.3: no codecs initialized [9.711743] usbcore: registered new interface driver snd-usb-audio I then tried updating the kernel to 5.18.2 but that was to no luck and the issue still persists. It seems alsa is not able to identify the card. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 Uname: Linux 5.18.2-051802-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Jun 12 19:32:33 2022 InstallationDate: Installed on 2022-05-28 (15 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/10/2021 dmi.bios.release: 7.7 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0707 dmi.board.asset.tag: Default string dmi.board.name: ROG STRIX Z690-A GAMING WIFI D4 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0707:bd11/10/2021:br7.7:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXZ690-AGAMINGWIFID4:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: ASUS mtime.conffile..etc.modprobe.d.alsa-base.conf: 2022-06-12T19:13:55.032469 ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1978428 Title: PCI/internal sound card not detected ALC4080 ASUS Z690 MB Status in alsa-driver package in Ubuntu: New Bug description: I have a fresh install of Ubuntu 22.04 Jammy on my ASUS Z690 motherboard with an intel i7 12700K. Ever since the fresh install I am unable to have any sound play through the rear or front audio jacks. I believe it is a problem with ubuntu not being able to recognize the sound card on the MB since this hardware seems to be very very new. It also seems that snd-hda-intel is unable to find any codecs for the sound card or even identify the onboard sound card. Here is the output of dmesg | grep 'snd': [5.426209] snd_hda_intel :00:1f.3: enabling device ( -> 0002) [5.426494] snd_hda_intel :01:00.1: enabling device ( -> 0002) [5.426528] snd_hda_intel :01:00.1: Disabling MSI [5.426531] snd_hda_intel :01:00.1: Handle vga_switcheroo audio client [6.438789] snd_hda_intel :00:1f.3: azx_get_response timeout, switching to polling mode: last cmd=0x000f [7.446910] snd_hda_intel :00:1f.3: No response from codec, disabling MSI: last cmd=0x000f [8.458944] snd_hda_intel :00:1f.3: Codec #0 probe error; disabling it... [9.470934] snd_hda_intel :00:1f.3: azx_get_response timeout, switching to single_cmd mode: last cmd=0x000f [9.471592] snd_hda_intel :00:1f.3: no codecs initialized [9.711743] usbcore: registered new interface driver snd-usb-audio I then tried updating the kernel to 5.18.2 but that was to no luck and the issue still persists. It seems alsa is not able to
[Desktop-packages] [Bug 1977977] Re: Blanked screen doesn't wake up after locking
OK then it sounds like a kernel configuration problem where the system is sleeping some components too deeply to wake up. Do you have 'tlp' installed? If so then it's a tlp bug/feature. Just uninstall tlp. If you don't have 'tlp' installed then you can still tweak which system components are able to wake the machine up in /proc/acpi/wakeup but it's very cryptic to use. Can you provide output from 'lspci' and a copy of your /proc/acpi/wakeup file? ** Summary changed: - Blanked screen doesn't wake up after locking + Blanked screen doesn't wake up after locking, unless a USB mouse is installed ** Package changed: gnome-shell (Ubuntu) => linux (Ubuntu) ** Summary changed: - Blanked screen doesn't wake up after locking, unless a USB mouse is installed + [Lenovo ThinkPad E580] Blanked screen doesn't wake up after locking, unless a USB mouse is installed -- 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/1977977 Title: [Lenovo ThinkPad E580] Blanked screen doesn't wake up after locking, unless a USB mouse is installed Status in linux package in Ubuntu: Incomplete Bug description: After I lock my screen and let it blank, moving the mouse or pressing any key on the keyboard won't wake it up. Pressing Ctrl+Alt+F1 doesn't help. That's on a fully up-to-date Ubuntu 22.04 (GNOME 42.1, Wayland). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gdm3 42.0-1ubuntu7 ProcVersionSignature: Ubuntu 5.15.0-37.39-generic 5.15.35 Uname: Linux 5.15.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Jun 8 16:30:14 2022 InstallationDate: Installed on 2022-06-08 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1977977/+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 1877194] Re: switch-on-connect mistakes startup for USB hotplug, so seemingly ignores the old default device on reboot
We don't need to check. "switch-on-connect" is a feature of PulseAudio only. Even if a similar bug was ever seen in PipeWire, it would get a seperate bug report. ** Changed in: pulseaudio (Ubuntu Kinetic) Status: Triaged => Won't Fix -- 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/1877194 Title: switch-on-connect mistakes startup for USB hotplug, so seemingly ignores the old default device on reboot Status in PulseAudio: New Status in pulseaudio package in Ubuntu: Triaged Status in ubuntu-settings package in Ubuntu: New Status in pulseaudio source package in Kinetic: Won't Fix Status in ubuntu-settings source package in Kinetic: New Bug description: Similar to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1847570 Only difference is that it does not reset to HDMI output, but to one of my USB-outputs. It does not respect the change I made after reboot. In short: 1. Boot system 2. "Analogue Output - RODE NT-USB" is selected by default. I want to use "Line Out - Built-in Audio", which I choose. 3. Reboot. 4 Output device is now back to "Analogue Output - RODE NT-USB". ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: marcus 1604 F pulseaudio /dev/snd/controlC0: marcus 1604 F pulseaudio /dev/snd/controlC1: marcus 1604 F pulseaudio /dev/snd/pcmC1D0c: marcus 1604 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed May 6 23:40:08 2020 InstallationDate: Installed on 2020-05-06 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/27/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3703 dmi.board.asset.tag: Default string dmi.board.name: MAXIMUS VIII HERO dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3703:bd12/27/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnMAXIMUSVIIIHERO:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1877194/+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 1969574] Re: [Wayland] Can not select JetBrains IntelliJ IDEA windows (including Android Studio) with mouse in workspace
** Also affects: mutter (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: mutter (Ubuntu Jammy) Status: New => Fix Released ** Changed in: mutter (Ubuntu Jammy) Importance: Undecided => Medium -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1969574 Title: [Wayland] Can not select JetBrains IntelliJ IDEA windows (including Android Studio) with mouse in workspace Status in GNOME Shell: Unknown Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Jammy: Fix Released Bug description: I have 3 apps open in 1 workspace, When i press window key and i want to select app 2 or 3 with mouse, app 1 shows up! I can only go to app 2 with [window + tab] or [alt + tab] ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.0-2ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Apr 20 11:05:02 2022 DisplayManager: gdm3 InstallationDate: Installed on 2021-11-25 (145 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) RelatedPackageVersions: mutter-common 42.0-3ubuntu2 SourcePackage: gnome-shell UpgradeStatus: Upgraded to jammy on 2022-04-16 (3 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1969574/+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 1970291] Re: [nvidia] Secondary monitor performance is slow on an Nvidia hybrid system in Wayland sessions
None of the log messages in comment #14 are relevant to this bug. Please see instead bug 1871262 and bug 1870597 about those. We also don't need to discuss this bug 1970291 any more because its cause is fully understood: https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2341 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1970291 Title: [nvidia] Secondary monitor performance is slow on an Nvidia hybrid system in Wayland sessions Status in mutter package in Ubuntu: Opinion Status in nvidia-graphics-drivers-510 package in Ubuntu: Triaged Bug description: In session with Wayland the Nvidia driver settings do not load. And there is a sluggishness when opening apps, show applications menu, maximize, changing workspace, resize, changing monitor windows etc. When in an Xorg session the Nvidia settings load correctly and the performance is satisfactory. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 510.60.02 Wed Mar 16 11:24:05 UTC 2022 GCC version: ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Apr 25 21:18:08 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation CoffeeLake-H GT2 [UHD Graphics 630] [8086:3e9b] (prog-if 00 [VGA controller]) Subsystem: Intel Corporation CoffeeLake-H GT2 [UHD Graphics 630] [8086:2086] NVIDIA Corporation TU116M [GeForce GTX 1660 Ti Mobile] [10de:2191] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation TU116M [GeForce GTX 1660 Ti Mobile] [8086:2086] InstallationDate: Installed on 2022-04-24 (1 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1) MachineType: Avell High Performance A60 MUV ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic root=UUID=894cb598-7172-481c-a449-3133b8f226e5 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/11/2020 dmi.bios.release: 5.13 dmi.bios.vendor: Intel Corp. dmi.bios.version: QCCFL357.0122.2020.0911.1520 dmi.board.name: Avell High Performance dmi.board.vendor: Avell High Performance dmi.chassis.type: 10 dmi.chassis.vendor: Avell High Performance dmi.chassis.version: 1.0 dmi.ec.firmware.release: 1.25 dmi.modalias: dmi:bvnIntelCorp.:bvrQCCFL357.0122.2020.0911.1520:bd09/11/2020:br5.13:efr1.25:svnAvellHighPerformance:pnA60MUV:pvr:rvnAvellHighPerformance:rnAvellHighPerformance:rvr:cvnAvellHighPerformance:ct10:cvr1.0:skuA60MUV: dmi.product.family: A60 MUV dmi.product.name: A60 MUV dmi.product.sku: A60 MUV dmi.sys.vendor: Avell High Performance version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3 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/mutter/+bug/1970291/+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 1972983] Re: File dialog in snap firefox does not have keyboard focus
Since the chromium-browser snap package also uses xdg-desktop-portal-
gnome, it is also affected by the same bug.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1972983
Title:
File dialog in snap firefox does not have keyboard focus
Status in mutter package in Ubuntu:
Confirmed
Status in xdg-desktop-portal-gnome package in Ubuntu:
Confirmed
Bug description:
Steps to reproduce the issue.
After first log in into Ubuntu Desktop 22.04
1. Launch Firefox and open a website (e.g. www.ubuntu.com)
2. Hit Ctrl+S to open the Save file dialog.
3. Type "Ubuntu" to replace the default file name ("Enterprise Open Source
and Linux | Ubuntu.html"). Hit Enter. It works the first time round.
4. Hit Ctrl+S to open the Save file dialog again.
5. Type "Ubuntu - 2" to replace the default file name ("Enterprise Open
Source and Linux | Ubuntu.html"). This time, your typing fails: the file dialog
is not in focus.
Expected behavior anytime when opening a File dialog: the file dialog
should have keyboard focus.
Observed behavior: the file dialog does not have focus, except the
very first time in the session.
Same observations also for File Open dialogs.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1972983/+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 1969974] Re: Gnome screen recorder doesn't work on dist-upgraded jammy systems
*** This bug is a duplicate of bug 1963264 *** https://bugs.launchpad.net/bugs/1963264 Janghou's fix worked for me as well. -- 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/1969974 Title: Gnome screen recorder doesn't work on dist-upgraded jammy systems Status in gnome-shell package in Ubuntu: Confirmed Bug description: I've just installed ubuntu 22.04; Screencasting (video recording) doesn't work... every time I open the screen tools (those which you can open with prtscr), and press the red button for screen recording, a red thing appear top right of my screen and it will be disappeared immediately! And then nothing happen :( Update: log: Apr 27 12:37:52 blacklighter systemd[2022]: Started Tracker metadata extractor. Apr 27 12:39:18 blacklighter dbus-daemon[63804]: [session uid=1000 pid=63804] Activating service name='org.gnome.Shell.Screencast' requested by ':1.30' (uid=1000 pid=63952 comm="/usr/bin/gnome-shell " label="unconfined") Apr 27 12:39:18 blacklighter dbus-daemon[63804]: [session uid=1000 pid=63804] Successfully activated service 'org.gnome.Shell.Screencast' Apr 27 12:39:18 blacklighter gjs[66306]: JS LOG: Failed to create pipeline: Gst.ParseError: no element "pipewiresrc" Apr 27 12:39:18 blacklighter gnome-shell[63952]: Error starting screencast Apr 27 12:39:20 blacklighter gnome-shell[63952]: D-Bus client with active sessions vanished Complete file: https://launchpadlibrarian.net/598628526/log.txt Also I tried installing pipwire: sudo apt update sudo apt install pipewire-media-session libpipewire-0.3-common Seems like I've already had the newest version libpipewire-0.3-common is already the newest version (0.3.48-1ubuntu1). pipewire-media-session is already the newest version (0.4.1-2ubuntu1). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Apr 22 22:03:57 2022 DistUpgraded: 2022-04-22 18:01:56,000 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company HD Graphics 620 [103c:828c] InstallationDate: Installed on 2021-08-07 (257 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04f2:b5ae Chicony Electronics Co., Ltd HP HD Camera Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bluetooth wireless interface Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP EliteBook 840 G4 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-25-generic root=UUID=cfaddaca-a453-457a-bdb2-1acc1600816e ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to jammy on 2022-04-22 (0 days ago) dmi.bios.date: 04/11/2017 dmi.bios.release: 1.3 dmi.bios.vendor: HP dmi.bios.version: P78 Ver. 01.03 dmi.board.name: 828C dmi.board.vendor: HP dmi.board.version: KBC Version 45.34 dmi.chassis.asset.tag: 5CG7242D5P dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.ec.firmware.release: 69.52 dmi.modalias: dmi:bvnHP:bvrP78Ver.01.03:bd04/11/2017:br1.3:efr69.52:svnHP:pnHPEliteBook840G4:pvr:rvnHP:rn828C:rvrKBCVersion45.34:cvnHP:ct10:cvr:skuX3V00AV: dmi.product.family: 103C_5336AN HP EliteBook dmi.product.name: HP EliteBook 840 G4 dmi.product.sku: X3V00AV dmi.sys.vendor: HP version.compiz: compiz 1:0.9.14.1+22.04.20211217-0ubuntu2 version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3 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/gnome-shell/+bug/1969974/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to :
[Desktop-packages] [Bug 1970594] Re: "xdg-settings check default-web-browser something.desktop" fails in Kubuntu 22.04: Bad substitution
I think what Jonas means is that he's expecting the answer to be "yes",
not "no".
Jonas, what is the output of `xdg-settings get default-web-browser` ?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xdg-utils in Ubuntu.
https://bugs.launchpad.net/bugs/1970594
Title:
"xdg-settings check default-web-browser something.desktop" fails in
Kubuntu 22.04: Bad substitution
Status in Xdg-utils:
New
Status in xdg-utils package in Ubuntu:
Fix Released
Status in xdg-utils source package in Jammy:
Fix Released
Bug description:
[Impact]
The firefox snap (default in 22.04) will always report that it thinks
it's not the default browser (even when it actually is) for KDE users
(this can be seen when browsing to about:preferences).
This is caused by an upstream bug in xdg-utils (using bashisms in KDE-
specific functions whereas the default interpreter is dash).
The fix is rather trivial and will visibly improve the UX for those
users.
[Test Plan]
In Kubuntu 22.04:
- make sure firefox isn't your default browser (by changing the setting to a
different browser)
- run the firefox snap, browse to "about:preferences", and observe that
firefox claims NOT to be the default browser
- click the "Set default" button
- refresh the page (F5)
- observe that now firefox claims to be the default browser
- in a terminal, execute `xdg-open https://example.org`, and verify that the
page is open in the firefox snap
[Where problems could occur]
The patch is changing KDE-specific functions (check_browser_kde and
check_url_scheme_handler_kde), so in theory it shouldn't affect
running xdg-utils in any other desktop environment.
If the proposed patch is incorrect, it would affect the functionality
of `xdg-settings check default-web-browser` and `xdg-settings check
default-url-scheme-handler`, so this is what needs to be thoroughly
tested in KDE.
In the event of a regression, these functions wouldn't work as
expected (they already don't, so the user wouldn't observe a
functional regression, merely the absence of a fix).
[Original description]
I'm reporting this issue from stock Ubuntu, but the problem is
observed only in Kubuntu (can be reliably reproduced in a Kubuntu
22.04 VM). The version of xdg-utils is identical.
This problem was initially reported on the snapcraft forum:
https://forum.snapcraft.io/t/firefox-wont-set-as-my-default-
browser/29708.
$ xdg-settings check default-web-browser firefox_firefox.desktop
/usr/bin/xdg-settings: 734: Bad substitution
The offending line is:
if [ x"!" == x"${browser:0:1}" ]; then
If I modify /usr/bin/xdg-settings in place to set the interpreter to
/bin/bash on the first line of the script, the problem goes away.
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: xdg-utils 1.1.3-4.1ubuntu1
ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
Uname: Linux 5.15.0-27-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu82
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Wed Apr 27 11:21:31 2022
InstallationDate: Installed on 2020-09-16 (587 days ago)
InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200910)
PackageArchitecture: all
SourcePackage: xdg-utils
UpgradeStatus: Upgraded to jammy on 2022-03-19 (38 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/xdg-utils/+bug/1970594/+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 1811504] Re: Scan with HP LaserJet Pro MFP M28a fails
It doesn't work under version 3.22.4 :( -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to hplip in Ubuntu. https://bugs.launchpad.net/bugs/1811504 Title: Scan with HP LaserJet Pro MFP M28a fails Status in hplip package in Ubuntu: Triaged Bug description: I’m trying to scan with my new printer Hp LaserJet MFP M28-M31 but I always get this error when scanning using SANE: error: SANE: Error during device I/O (code=9) I’ve installed hplip hplip-plugins and any other dependencies listed in hp-check but without luck. any hints? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hplip/+bug/1811504/+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 1970594] Re: "xdg-settings check default-web-browser something.desktop" fails in Kubuntu 22.04: Bad substitution
Yamiyukisenpai, that is working correctly. The error message does not
impact the functionality of the program. It is merely ugly. There is a
patch upstream that fixes this, but it isn't appropriate to SRU this
fix.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xdg-utils in Ubuntu.
https://bugs.launchpad.net/bugs/1970594
Title:
"xdg-settings check default-web-browser something.desktop" fails in
Kubuntu 22.04: Bad substitution
Status in Xdg-utils:
New
Status in xdg-utils package in Ubuntu:
Fix Released
Status in xdg-utils source package in Jammy:
Fix Released
Bug description:
[Impact]
The firefox snap (default in 22.04) will always report that it thinks
it's not the default browser (even when it actually is) for KDE users
(this can be seen when browsing to about:preferences).
This is caused by an upstream bug in xdg-utils (using bashisms in KDE-
specific functions whereas the default interpreter is dash).
The fix is rather trivial and will visibly improve the UX for those
users.
[Test Plan]
In Kubuntu 22.04:
- make sure firefox isn't your default browser (by changing the setting to a
different browser)
- run the firefox snap, browse to "about:preferences", and observe that
firefox claims NOT to be the default browser
- click the "Set default" button
- refresh the page (F5)
- observe that now firefox claims to be the default browser
- in a terminal, execute `xdg-open https://example.org`, and verify that the
page is open in the firefox snap
[Where problems could occur]
The patch is changing KDE-specific functions (check_browser_kde and
check_url_scheme_handler_kde), so in theory it shouldn't affect
running xdg-utils in any other desktop environment.
If the proposed patch is incorrect, it would affect the functionality
of `xdg-settings check default-web-browser` and `xdg-settings check
default-url-scheme-handler`, so this is what needs to be thoroughly
tested in KDE.
In the event of a regression, these functions wouldn't work as
expected (they already don't, so the user wouldn't observe a
functional regression, merely the absence of a fix).
[Original description]
I'm reporting this issue from stock Ubuntu, but the problem is
observed only in Kubuntu (can be reliably reproduced in a Kubuntu
22.04 VM). The version of xdg-utils is identical.
This problem was initially reported on the snapcraft forum:
https://forum.snapcraft.io/t/firefox-wont-set-as-my-default-
browser/29708.
$ xdg-settings check default-web-browser firefox_firefox.desktop
/usr/bin/xdg-settings: 734: Bad substitution
The offending line is:
if [ x"!" == x"${browser:0:1}" ]; then
If I modify /usr/bin/xdg-settings in place to set the interpreter to
/bin/bash on the first line of the script, the problem goes away.
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: xdg-utils 1.1.3-4.1ubuntu1
ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
Uname: Linux 5.15.0-27-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu82
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Wed Apr 27 11:21:31 2022
InstallationDate: Installed on 2020-09-16 (587 days ago)
InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200910)
PackageArchitecture: all
SourcePackage: xdg-utils
UpgradeStatus: Upgraded to jammy on 2022-03-19 (38 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/xdg-utils/+bug/1970594/+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 1970594] Re: "xdg-settings check default-web-browser something.desktop" fails in Kubuntu 22.04: Bad substitution
Still not fixed for me.
$ kreadconfig5 --file kdeglobals --group General --key BrowserApplication
firefox.desktop
$ xdg-settings check default-web-browser firefox.desktop
/usr/bin/xdg-settings: 734: [: x!: unexpected operator
no
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xdg-utils in Ubuntu.
https://bugs.launchpad.net/bugs/1970594
Title:
"xdg-settings check default-web-browser something.desktop" fails in
Kubuntu 22.04: Bad substitution
Status in Xdg-utils:
New
Status in xdg-utils package in Ubuntu:
Fix Released
Status in xdg-utils source package in Jammy:
Fix Released
Bug description:
[Impact]
The firefox snap (default in 22.04) will always report that it thinks
it's not the default browser (even when it actually is) for KDE users
(this can be seen when browsing to about:preferences).
This is caused by an upstream bug in xdg-utils (using bashisms in KDE-
specific functions whereas the default interpreter is dash).
The fix is rather trivial and will visibly improve the UX for those
users.
[Test Plan]
In Kubuntu 22.04:
- make sure firefox isn't your default browser (by changing the setting to a
different browser)
- run the firefox snap, browse to "about:preferences", and observe that
firefox claims NOT to be the default browser
- click the "Set default" button
- refresh the page (F5)
- observe that now firefox claims to be the default browser
- in a terminal, execute `xdg-open https://example.org`, and verify that the
page is open in the firefox snap
[Where problems could occur]
The patch is changing KDE-specific functions (check_browser_kde and
check_url_scheme_handler_kde), so in theory it shouldn't affect
running xdg-utils in any other desktop environment.
If the proposed patch is incorrect, it would affect the functionality
of `xdg-settings check default-web-browser` and `xdg-settings check
default-url-scheme-handler`, so this is what needs to be thoroughly
tested in KDE.
In the event of a regression, these functions wouldn't work as
expected (they already don't, so the user wouldn't observe a
functional regression, merely the absence of a fix).
[Original description]
I'm reporting this issue from stock Ubuntu, but the problem is
observed only in Kubuntu (can be reliably reproduced in a Kubuntu
22.04 VM). The version of xdg-utils is identical.
This problem was initially reported on the snapcraft forum:
https://forum.snapcraft.io/t/firefox-wont-set-as-my-default-
browser/29708.
$ xdg-settings check default-web-browser firefox_firefox.desktop
/usr/bin/xdg-settings: 734: Bad substitution
The offending line is:
if [ x"!" == x"${browser:0:1}" ]; then
If I modify /usr/bin/xdg-settings in place to set the interpreter to
/bin/bash on the first line of the script, the problem goes away.
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: xdg-utils 1.1.3-4.1ubuntu1
ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
Uname: Linux 5.15.0-27-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu82
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Wed Apr 27 11:21:31 2022
InstallationDate: Installed on 2020-09-16 (587 days ago)
InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200910)
PackageArchitecture: all
SourcePackage: xdg-utils
UpgradeStatus: Upgraded to jammy on 2022-03-19 (38 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/xdg-utils/+bug/1970594/+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 1978411] [NEW] simple-scan throws error and crashes upon scanning document
Public bug reported:
[+0.00s] DEBUG: simple-scan.vala:1720: Starting simple-scan 3.36.3, PID=94430
[+0.00s] DEBUG: unsetenv() is not thread-safe and should not be used after
threads are created
[+0.02s] DEBUG: _g_io_module_get_default: Found default implementation dconf
(DConfSettingsBackend) for ‘gsettings-backend’
[+0.06s] DEBUG: app-window.vala:1906: Loading state from
/home/mcapp/.cache/simple-scan/state
[+0.06s] DEBUG: app-window.vala:1885: Restoring window to 600x400 pixels
[+0.38s] DEBUG: scanner.vala:1539: sane_init () -> SANE_STATUS_GOOD
[+0.38s] DEBUG: scanner.vala:1545: SANE version 1.0.29
[+0.38s] DEBUG: scanner.vala:1606: Requesting redetection of scan devices
[+0.38s] DEBUG: scanner.vala:828: Processing request
[+0.57s] DEBUG: app-window.vala:1981: Saving state to
/home/mcapp/.cache/simple-scan/state
[+9.67s] DEBUG: app-window.vala:1981: Saving state to
/home/mcapp/.cache/simple-scan/state
[+11.26s] DEBUG: scanner.vala:341: sane_get_devices () -> SANE_STATUS_GOOD
[+11.26s] DEBUG: scanner.vala:353: Device: name="brother4:net1;dev0"
vendor="Brother" model="MFC-9130CW" type="MFC-9130CW"
[+11.55s] DEBUG: app-window.vala:1981: Saving state to
/home/mcapp/.cache/simple-scan/state
[+11.70s] DEBUG: app-window.vala:1981: Saving state to
/home/mcapp/.cache/simple-scan/state
[+12.68s] DEBUG: simple-scan.vala:1536: Requesting scan at 1200 dpi from device
'brother4:net1;dev0'
[+12.68s] DEBUG: scanner.vala:1674: Scanner.scan ("brother4:net1;dev0",
dpi=1200, scan_mode=ScanMode.COLOR, depth=8, type=single, paper_width=0,
paper_height=0, brightness=0, contrast=0, delay=3000ms)
[+12.68s] DEBUG: scanner.vala:828: Processing request
[+12.93s] DEBUG: app-window.vala:1981: Saving state to
/home/mcapp/.cache/simple-scan/state
[+14.30s] DEBUG: app-window.vala:1981: Saving state to
/home/mcapp/.cache/simple-scan/state
[+18.55s] DEBUG: scanner.vala:889: sane_open ("brother4:net1;dev0") ->
SANE_STATUS_GOOD
[+18.55s] DEBUG: scanner.vala:910: sane_get_option_descriptor (0)
[+18.55s] DEBUG: scanner.vala:760: Option 0: name='(null)' title='Number of
options' type=bool size=4 cap=soft-detect
[+18.55s] DEBUG: scanner.vala:763: Description: Read-only option that
specifies how many options a specific devices supports.
[+18.55s] DEBUG: scanner.vala:910: sane_get_option_descriptor (1)
[+18.55s] DEBUG: scanner.vala:760: Option 1: name='(null)' title='Mode'
type=group size=4 cap=advanced
[+18.55s] DEBUG: scanner.vala:763: Description:
[+18.55s] DEBUG: scanner.vala:910: sane_get_option_descriptor (2)
[+18.55s] DEBUG: scanner.vala:760: Option 2: name='mode' title='Scan mode'
type=string size=30 values=["Black & White", "Gray[Error Diffusion]", "True
Gray", "24bit Color", "24bit Color[Fast]"] cap=soft-select,soft-detect
[+18.55s] DEBUG: scanner.vala:763: Description: Select the scan mode
[+18.55s] DEBUG: scanner.vala:910: sane_get_option_descriptor (3)
[+18.55s] DEBUG: scanner.vala:760: Option 3: name='resolution' title='Scan
resolution' type=int size=4 unit=dpi values=[100, 150, 200, 300, 400, 600,
1200, 2400, 4800, 9600] cap=soft-select,soft-detect
[+18.55s] DEBUG: scanner.vala:763: Description: Sets the resolution of the
scanned image.
[+18.55s] DEBUG: scanner.vala:910: sane_get_option_descriptor (4)
[+18.55s] DEBUG: scanner.vala:760: Option 4: name='source' title='Scan source'
type=string size=64 values=["FlatBed", "Automatic Document Feeder(left
aligned)", "Automatic Document Feeder(centrally aligned)"]
cap=soft-select,soft-detect
[+18.55s] DEBUG: scanner.vala:763: Description: Selects the scan source (such
as a document-feeder).
[+18.55s] DEBUG: scanner.vala:910: sane_get_option_descriptor (5)
[+18.55s] DEBUG: scanner.vala:760: Option 5: name='brightness'
title='Brightness' type=fixed size=4 unit=percent min=-50.00,
max=50.00, quant=65536 cap=soft-select,soft-detect,inactive
[+18.55s] DEBUG: scanner.vala:763: Description: Controls the brightness of
the acquired image.
[+18.55s] DEBUG: scanner.vala:910: sane_get_option_descriptor (6)
[+18.55s] DEBUG: scanner.vala:760: Option 6: name='contrast' title='Contrast'
type=fixed size=4 unit=percent min=-50.00, max=50.00, quant=65536
cap=soft-select,soft-detect,inactive
[+18.55s] DEBUG: scanner.vala:763: Description: Controls the contrast of the
acquired image.
[+18.55s] DEBUG: scanner.vala:910: sane_get_option_descriptor (7)
[+18.55s] DEBUG: scanner.vala:760: Option 7: name='(null)' title='Geometry'
type=group size=4 cap=advanced
[+18.55s] DEBUG: scanner.vala:763: Description:
[+18.55s] DEBUG: scanner.vala:910: sane_get_option_descriptor (8)
[+18.55s] DEBUG: scanner.vala:760: Option 8: name='tl-x' title='Top-left x'
type=fixed size=4 unit=mm min=0.00, max=211.84, quant=6553
cap=soft-select,soft-detect
[+18.55s] DEBUG: scanner.vala:763: Description: Top-left x position of scan
area.
[+18.55s] DEBUG: scanner.vala:910: sane_get_option_descriptor (9)
[+18.55s] DEBUG: scanner.vala:760: Option 9: name='tl-y'
[Desktop-packages] [Bug 1864215] Re: Please add webp loader to gdk-pixbuf
The webp-pixbuf-loader package is still not available with Ubuntu 22.04 LTS. It is impossible to view a WebP image, except to open it with Firefox. It is really important to add WebP format natively in Uuntu. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdk-pixbuf in Ubuntu. https://bugs.launchpad.net/bugs/1864215 Title: Please add webp loader to gdk-pixbuf Status in gdk-pixbuf: Fix Released Status in gdk-pixbuf package in Ubuntu: Confirmed Status in gdk-pixbuf package in Baltix: Triaged Status in Debian: New Bug description: Attempting to load a webp image -- for instance, https://images.theweek.com/sites/default/files/styles/tw_image_9_4/public/FKK78W.jpg.webp or https://cdn.vox-cdn.com/thumbor/2YtWB5zH7sPycyc0FYv3JSB6SFw=/60x0:1140x720/920x613/filters:focal(60x0:1140x720):format(webp)/cdn.vox-cdn.com/uploads/chorus_image/image/49663815/timburton.0.0.jpg -- in a gdk-pixbuf app results in a "Couldn’t recognize the image file format" error. Bug 1318327 covers this issue in eye of gnome, and bug 1407644 in libwebp, but isn't this really a gdk-pixbuf issue? If it really does belong to libwebp, my apologies, please dup this bug to 1407644 (I'm confident it doesn't belong to eog since I don't use that program; I have other programs that use libgdk-pixbuf). You can probably use eog to test this, or run /usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/gdk-pixbuf-query-loaders | grep -i webp (I assume the loader would mention webp if there was a loader for it). I have these packages installed in addition to libgdk-pixbuf2.0-0: libwebp-dev libwebp6 libwebpdemux2 libwebpmux3 webp. file recognizes the format: $ file /tmp/FKK78W.jpg.webp /tmp/FKK78W.jpg.webp: RIFF (little-endian) data, Web/P image, VP8 encoding, 1200x533, Scaling: [none]x[none], YUV color, decoders should clamp ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: libgdk-pixbuf2.0-0 2.40.0+dfsg-1build1 ProcVersionSignature: Ubuntu 5.3.0-40.32-generic 5.3.18 Uname: Linux 5.3.0-40-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8.4 Architecture: amd64 Date: Fri Feb 21 08:48:36 2020 InstallationDate: Installed on 2019-10-10 (133 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Beta amd64 (20190926.1) SourcePackage: gdk-pixbuf UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gdk-pixbuf/+bug/1864215/+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 1969959] Re: [nouveau] Weird colors after startup (Ubuntu 22.04)
Nvidia 3090 on an Alienware R10: boots normally, but the desktop appears as shades of bright green. It was corrected when I followed Andrii's solution in comment #28. Thank you Andrii, you just saved me a bunch of time. I had already tried the Live USB and installed 22.04 on my Gigabyte Aorus X5 MD Laptop (Nvidia 1080ti) and I have not encountered this issue on it. -- 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/1969959 Title: [nouveau] Weird colors after startup (Ubuntu 22.04) Status in linux package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Confirmed Bug description: [Workaround/Fix] 1. When starting the Ubuntu live image, select the option 'Ubuntu (safe graphics)' from the boot menu. 2. During installation be sure to select the third-party software option checkbox in order to get the right Nvidia driver installed. [Original Description] I started Ubuntu 22.04 from a live pen drive. Everything seems fine, the usual screen with the options to "Try Ubuntu" or "Install" Ubuntu appears. When hitting "Try Ubuntu", the screen turns black for a couple of seconds and then re-appears in yellow and brown colors, feels like a 4 color display (white, black, yellow and orange) and I can hardly see anything - sending this bug report from that live system right after starting it up. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CasperVersion: 1.470 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Apr 22 15:54:05 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation TU117 [GeForce GTX 1650] [10de:1f82] (rev a1) (prog-if 00 [VGA controller]) Subsystem: NVIDIA Corporation TU117 [GeForce GTX 1650] [10de:1f82] Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev d9) (prog-if 00 [VGA controller]) Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] LiveMediaBuild: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Micro-Star International Co., Ltd. MS-7C56 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash --- SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/30/2020 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: A.40 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B550-A PRO (MS-7C56) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrA.40:bd10/30/2020:br5.17:svnMicro-StarInternationalCo.,Ltd.:pnMS-7C56:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB550-APRO(MS-7C56):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7C56 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1969959/+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 1972034] Re: On browser download/save dialog, filename in name box is highlighted as if it is active, but typing doesn't edit name unless you click into the box
Text editor (gedit) works as expected. This is on Ubuntu 22.04, but has been an issue at least since 20.04 if not earlier. -- 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/1972034 Title: On browser download/save dialog, filename in name box is highlighted as if it is active, but typing doesn't edit name unless you click into the box Status in nautilus package in Ubuntu: Incomplete Bug description: This has bugged me for many years now, and figure as long as the kinks are being worked out on this bug: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1971516 I should bring it up: When you download a file from a browser, the save dialog pops up, and the filename in the name box at the top is highlighted (just the name, not the extension), which is the universal symbol for "I'm highlighted, start typing and you'll overwrite me!" However, typing does nothing unless you click the box, at which point the cursor is in the middle of the name, and you have re-highlight if you want to rename the file. This is still confusing to me after many years. Expected behaviour: Either: Filename is highlighted and you can start typing to replace the name (but not the extension) Or: Filname is NOT highlighted by default, indicating you are not ready to edit. Since Ubuntu 20.04... possibly longer. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1972034/+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 1969896] Re: Evince Document Viewer(42.0) does not remember last page in 22.04 and opens in a tiny window when launched
This problem occurs on my fresh Ubuntu 22.04 install. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1969896 Title: Evince Document Viewer(42.0) does not remember last page in 22.04 and opens in a tiny window when launched Status in evince package in Ubuntu: Confirmed Bug description: Just switched from Ubuntu 20.04 to 22.04 and realized that Document Viewer no longer open on the last viewed page and doesn't remember the side pane preference even after using the "Save Current Settings as Default" option. Kindly advise ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: evince 42.1-3 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Apr 22 15:58:50 2022 InstallationDate: Installed on 2022-03-19 (34 days ago) InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: evince UpgradeStatus: Upgraded to jammy on 2022-04-21 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1969896/+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 1877194] Re: switch-on-connect mistakes startup for USB hotplug, so seemingly ignores the old default device on reboot
@seb128 tested with pipewire on kinetic with a Pi 4B and it correctly selects the HDMI out by default both on initial setup and after a few reboots. So, looks like this could be "invalid" on kinetic, at least for the Raspberry Pi case. Would be useful to double-check that on PC hardware too, obviously. -- 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/1877194 Title: switch-on-connect mistakes startup for USB hotplug, so seemingly ignores the old default device on reboot Status in PulseAudio: New Status in pulseaudio package in Ubuntu: Triaged Status in ubuntu-settings package in Ubuntu: New Status in pulseaudio source package in Kinetic: Triaged Status in ubuntu-settings source package in Kinetic: New Bug description: Similar to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1847570 Only difference is that it does not reset to HDMI output, but to one of my USB-outputs. It does not respect the change I made after reboot. In short: 1. Boot system 2. "Analogue Output - RODE NT-USB" is selected by default. I want to use "Line Out - Built-in Audio", which I choose. 3. Reboot. 4 Output device is now back to "Analogue Output - RODE NT-USB". ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: marcus 1604 F pulseaudio /dev/snd/controlC0: marcus 1604 F pulseaudio /dev/snd/controlC1: marcus 1604 F pulseaudio /dev/snd/pcmC1D0c: marcus 1604 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed May 6 23:40:08 2020 InstallationDate: Installed on 2020-05-06 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/27/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3703 dmi.board.asset.tag: Default string dmi.board.name: MAXIMUS VIII HERO dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3703:bd12/27/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnMAXIMUSVIIIHERO:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1877194/+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 1978380] Re: External monitor not detected
Thank you for taking the time to report this bug and helping to make Ubuntu better. Bug reporting is about finding & fixing problems thus preventing future users from hitting the same bug. I suspect a Support site would be more appropriate, eg. https://answers.launchpad.net/ubuntu. You can also find help with your problem in the support forum of your local Ubuntu community http://loco.ubuntu.com/ or asking at https://askubuntu.com or https://ubuntuforums.org, or for more support options please look at https://discourse.ubuntu.com/t/community-support/709 ** Package changed: xorg (Ubuntu) => linux (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/1978380 Title: External monitor not detected Status in linux package in Ubuntu: New Bug description: Hello. I have a laptop Lenovo Legion Y540-15IRH (81SX00EVRA) with Hybrid graphics. OS: 20.04.4 LTS and Windows 10 in dual boot. BIOS is set to Switchable Graphics, meaning Hybrid. NVidia PRIME profile is set to Intel (power saving). So the problem is that on Ubuntu system doesn't detect an external monitor through HDMI port. When PRIME profile was set to NVidia best Performance - it was able to detect the external monitor. But as I am not playing games anymore - I don't want to use power-consuming and noisy discrete RTX 2060. So I switched to integrated Intel UHD Graphics 630. What should I do in order OS to detect an external monitor? Thanks ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.13.0-48.54~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-48-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Jun 11 14:41:50 2022 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 5.13.0-44-generic, x86_64: installed bcmwl, 6.30.223.271+bdcom, 5.13.0-48-generic, x86_64: installed nvidia, 470.129.06, 5.13.0-44-generic, x86_64: installed nvidia, 470.129.06, 5.13.0-48-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (prog-if 00 [VGA controller]) Subsystem: Lenovo UHD Graphics 630 (Mobile) [17aa:3ffd] NVIDIA Corporation TU106M [GeForce RTX 2060 Mobile] [10de:1f11] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo TU106M [GeForce RTX 2060 Mobile] [17aa:3ffd] InstallationDate: Installed on 2020-10-21 (597 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: LENOVO 81SX ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-48-generic root=UUID=96af554d-dedb-4846-b7ca-651771269b4c ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/20/2022 dmi.bios.release: 1.44 dmi.bios.vendor: LENOVO dmi.bios.version: BHCN44WW 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: Legion Y540-15IRH dmi.ec.firmware.release: 1.44 dmi.modalias: dmi:bvnLENOVO:bvrBHCN44WW:bd01/20/2022:br1.44:efr1.44:svnLENOVO:pn81SX:pvrLegionY540-15IRH:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrLegionY540-15IRH:skuLENOVO_MT_81SX_BU_idea_FM_LegionY540-15IRH: dmi.product.family: Legion Y540-15IRH dmi.product.name: 81SX dmi.product.sku: LENOVO_MT_81SX_BU_idea_FM_Legion Y540-15IRH dmi.product.version: Legion Y540-15IRH dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ubuntu1~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A 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/1978380/+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 1978401] [NEW] display turns suddenly off and then on again
Public bug reported: Hi, Randomly the display turns off and then on again. Happens sometimes many times and others times not at all, randomly. Related to https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics- drivers-495/+bug/1956252 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-37.39-generic 5.15.35 Uname: Linux 5.15.0-37-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 510.73.05 Sat May 7 05:30:26 UTC 2022 GCC version: ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Jun 12 09:45:00 2022 DistUpgraded: 2022-04-21 07:46:27,025 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation TU102 [GeForce RTX 2080 Ti Rev. A] [10de:1e07] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd TU102 [GeForce RTX 2080 Ti Rev. A] [1458:37a9] InstallationDate: Installed on 2022-04-03 (69 days ago) InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) MachineType: Gigabyte Technology Co., Ltd. Z390 AORUS PRO ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-37-generic root=UUID=7d72a26f-7e2e-4ed2-851b-4bedb4181f16 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to jammy on 2022-04-21 (52 days ago) dmi.bios.date: 01/19/2021 dmi.bios.release: 5.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F12l dmi.board.asset.tag: Default string dmi.board.name: Z390 AORUS PRO-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF12l:bd01/19/2021:br5.13:svnGigabyteTechnologyCo.,Ltd.:pnZ390AORUSPRO:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnZ390AORUSPRO-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: Default string dmi.product.name: Z390 AORUS PRO dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3 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/1978401 Title: display turns suddenly off and then on again Status in xorg package in Ubuntu: New Bug description: Hi, Randomly the display turns off and then on again. Happens sometimes many times and others times not at all, randomly. Related to https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics- drivers-495/+bug/1956252 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-37.39-generic 5.15.35 Uname: Linux 5.15.0-37-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 510.73.05 Sat May 7 05:30:26 UTC 2022 GCC version: ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult:
[Desktop-packages] [Bug 1962349] Re: Bolt doesn't work with native USB4 hosts
** Changed in: oem-priority Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to bolt in Ubuntu. https://bugs.launchpad.net/bugs/1962349 Title: Bolt doesn't work with native USB4 hosts Status in OEM Priority Project: Fix Released Status in bolt package in Ubuntu: Fix Released Status in linux package in Ubuntu: In Progress Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.17 package in Ubuntu: Invalid Status in bolt source package in Focal: Fix Released Status in linux source package in Focal: Won't Fix Status in linux-oem-5.14 source package in Focal: Fix Released Status in linux-oem-5.17 source package in Focal: Invalid Status in bolt source package in Impish: Fix Released Status in linux source package in Impish: Won't Fix Status in linux-oem-5.14 source package in Impish: Invalid Status in linux-oem-5.17 source package in Impish: Invalid Status in bolt source package in Jammy: Fix Released Status in linux source package in Jammy: Fix Released Status in linux-oem-5.14 source package in Jammy: Invalid Status in linux-oem-5.17 source package in Jammy: Fix Released Bug description: [SRU Justification] [Impact] * AMD Yellow Carp provides integrated USB4 host controllers * When plugging in a Thunderbolt3 or USB4 device, users are unable to authorize it using the GUI due to an error message: "parent not authorized, deferring" [Test Plan] AMD Yellow Carp Host (issue this bug is about) -- * Plug in USB4 device or TBT3 to AMD Yellow Carp host * Ensure that PCI topology has populated * Observe that /sys/bus/thunderbolt/devices/DEVICE/authorized is "0" * Try to run `boltctl enroll $UUID` Alpine Ridge / Titan Ridge host (discrete controller) -- Start out on a host with discrete controller (Alpine Ridge or Titan Ridge) 1. sudo boltctl forget -a 2. Plug in dock 3. Make sure 'boltctl list' enumerates dock. 4. Check /sys/bus/thunderbolt/devices/domain0/iommu_dma_protection (value dependent upon host) - If 0; try to manually enroll using 'boltctl enroll $UUID' - If 1; ensure that device automatically enrolled with bolt. GUI Check - Ensure that devices show up in the Settings GUI and are now able to authorize. Note: for AMD platforms enumerating PCIe devices is a separate problem from BOLT handled by kernel tasks. GUI check is only about "authorization". [Where problems could occur] * Intel USB4 or TBT3 hosts also use bolt. They could have a problem with the new version of bolt. * This is very unlikely however since there is a through test suite, and up until now the entire industry has been using bolt on Intel controllers for a long time. * There haven't been any significant bugs reported upstream or in Ubuntu since 0.9.1 release. [Other Info] * This bug also occurs on Intel controllers from ICL, TGL or ALD, but in many cases they are automatically authorized to an iommu DMA policy. * It is fixed in bolt 0.9.1 or later release. * To solve the SRU, will backport 0.9.1 release from Impish. * I did look into backporting just the commit(s) for fixing this, but it's not a trivial backport. Quoting the changelog (https://gitlab.freedesktop.org/bolt/bolt/-/blob/master/CHANGELOG.md): "Additionally the unique_id of said host controller changes with every boot, which breaks one of the fundamental assumptions in boltd". To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1962349/+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 1978400] [NEW] GNOME Network Displays does not work with error Authorization supplicant timed out
Public bug reported: I have a problem with connecting to a Miracast device via GNOME Network Displays package (https://gitlab.gnome.org/GNOME/gnome-network-displays) on Ubuntu. It sees the device normally (I see the device name in "Available Video Sinks" list), but when I'm trying to connect, after some time I've got the connection failed with the error: ``` p2p-dev-wlp0s20f3: Authorization supplicant timed out ``` Other systems (Android, Windows, MacOS) connects to it successfully. In the https://gitlab.gnome.org/GNOME/gnome-network-displays it's described that wpa_supplicant requires the patch: https://patchwork.ozlabs.org/project/hostap/patch/20200825062902.124600-1-benja...@sipsolutions.net/ Maybe just adding this one-line patch could resolve this issue? Or it is already applied? ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: wpasupplicant 2:2.10-6ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Sun Jun 12 09:56:19 2022 InstallationDate: Installed on 2022-04-14 (58 days ago) InstallationMedia: Error: [Errno 13] Permission denied: '/var/log/installer/media-info' SourcePackage: wpa UpgradeStatus: Upgraded to jammy on 2022-04-14 (58 days ago) modified.conffile..etc.cron.daily.apport: [deleted] ** Affects: wpa (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1978400 Title: GNOME Network Displays does not work with error Authorization supplicant timed out Status in wpa package in Ubuntu: New Bug description: I have a problem with connecting to a Miracast device via GNOME Network Displays package (https://gitlab.gnome.org/GNOME/gnome-network-displays) on Ubuntu. It sees the device normally (I see the device name in "Available Video Sinks" list), but when I'm trying to connect, after some time I've got the connection failed with the error: ``` p2p-dev-wlp0s20f3: Authorization supplicant timed out ``` Other systems (Android, Windows, MacOS) connects to it successfully. In the https://gitlab.gnome.org/GNOME/gnome-network-displays it's described that wpa_supplicant requires the patch: https://patchwork.ozlabs.org/project/hostap/patch/20200825062902.124600-1-benja...@sipsolutions.net/ Maybe just adding this one-line patch could resolve this issue? Or it is already applied? ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: wpasupplicant 2:2.10-6ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Sun Jun 12 09:56:19 2022 InstallationDate: Installed on 2022-04-14 (58 days ago) InstallationMedia: Error: [Errno 13] Permission denied: '/var/log/installer/media-info' SourcePackage: wpa UpgradeStatus: Upgraded to jammy on 2022-04-14 (58 days ago) modified.conffile..etc.cron.daily.apport: [deleted] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1978400/+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
