[Desktop-packages] [Bug 402621] Re: Firefox should have resizable form fields like Safari
** Changed in: firefox Importance: Wishlist => Medium -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/402621 Title: Firefox should have resizable form fields like Safari Status in Mozilla Firefox: Fix Released Status in firefox package in Ubuntu: Fix Released Bug description: Look what this person does to the text box after typing his message: http://www.youtube.com/watch?v=LsX3C0ZtNDE min 0:48 To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/402621/+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 1880218] Re: gnome-shell crashed with SIGSEGV in st_theme_node_lookup_shadow() from st_theme_node_get_background_image_shadow() from st_theme_node_paint_equal() from st_widget_
Zero crashes since 20.10 so consider this fixed. ** Changed in: gnome-shell (Ubuntu) Status: Confirmed => 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/1880218 Title: gnome-shell crashed with SIGSEGV in st_theme_node_lookup_shadow() from st_theme_node_get_background_image_shadow() from st_theme_node_paint_equal() from st_widget_recompute_style() from st_widget_style_changed() Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: Fix Released Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 3.36.2-1ubuntu1~20.04.1, the problem page at https://errors.ubuntu.com/problem/1918c0de443d58d0513f9914a411daf2c41bdad6 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1880218/+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 1960865] Re: System freeze when plugging USB-C monitor into a hybrid Intel/Nvidia laptop: [drm:__nv_drm_gem_nvkms_memory_prime_get_sg_table [nvidia_drm]] *ERROR* [nvidia-drm] [
Great, thanks for the explanation. So blaming just the nvidia-drm kernel module seems most reasonable right now. It is what's crashing after all. Most likely the fix will come in the form of a new Nvidia driver. Please try apt install nvidia-driver-510 or via the 'Additional Drivers' app. You don't need to upgrade all of Ubuntu just yet. ** No longer affects: mutter (Ubuntu) ** No longer affects: linux (Ubuntu) -- 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/1960865 Title: System freeze when plugging USB-C monitor into a hybrid Intel/Nvidia laptop: [drm:__nv_drm_gem_nvkms_memory_prime_get_sg_table [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x0100] Failed to get memory pages for NvKmsKapiMemory Status in Mutter: Unknown Status in nvidia-graphics-drivers-470 package in Ubuntu: Confirmed Bug description: I recently upgraded my NVidia drivers on my ThinkPad P1 Gen 3. If I start Ubuntu on Wayland session and plug in my USB-C monitor the system reliably completely freeze. The freeze is also reproducible if the screen is plugged in during startup and trying to login into a Wayland session. Only Wayland session experiences a crash. The crash happens ONLY if the USB-C monitor is plugged in. USB-C monitor is also a USB3 hub. Hardware seems to work fine, as Windows shows no issues with the setup. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: xorg 1:7.7+22ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-30.33-generic 5.13.19 Uname: Linux 5.13.0-30-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 470.103.01 Thu Jan 6 12:10:04 UTC 2022 GCC version: gcc version 11.2.0 (Ubuntu 11.2.0-7ubuntu2) ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Feb 14 16:39:34 2022 DistUpgraded: 2021-10-14 18:36:11,564 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: impish DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GpuHangFrequency: Continuously GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Within the last few days GraphicsCard: Intel Corporation CometLake-H GT2 [UHD Graphics] [8086:9bc4] (rev 05) (prog-if 00 [VGA controller]) Subsystem: Lenovo CometLake-H GT2 [UHD Graphics] [17aa:22c1] NVIDIA Corporation TU117GLM [Quadro T1000 Mobile] [10de:1fb9] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo TU117GLM [Quadro T1000 Mobile] [17aa:22c1] InstallationDate: Installed on 2020-10-05 (497 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: LENOVO 20THCT01WW ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-30-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to impish on 2021-10-14 (122 days ago) dmi.bios.date: 12/27/2021 dmi.bios.release: 1.21 dmi.bios.vendor: LENOVO dmi.bios.version: N2VET36W (1.21 ) dmi.board.asset.tag: Not Available dmi.board.name: 20THCT01WW dmi.board.vendor: LENOVO dmi.board.version: 0B98417 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.10 dmi.modalias: dmi:bvnLENOVO:bvrN2VET36W(1.21):bd12/27/2021:br1.21:efr1.10:svnLENOVO:pn20THCT01WW:pvrThinkPadP1Gen3:rvnLENOVO:rn20THCT01WW:rvr0B98417WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20TH_BU_Think_FM_ThinkPadP1Gen3: dmi.product.family: ThinkPad P1 Gen 3 dmi.product.name: 20THCT01WW dmi.product.sku: LENOVO_MT_20TH_BU_Think_FM_ThinkPad P1 Gen 3 dmi.product.version: ThinkPad P1 Gen 3 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1 version.libgl1-mesa-glx: libgl1-mesa-glx 21.2.6-0ubuntu0.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1.1 version.xserver-xorg-input-evdev:
[Desktop-packages] [Bug 1960336] Re: No login screen when fprintd is installed and not starting
Bug 1933633 is a clean exit whereas this bug 1960336 is a segfault. So the two bugs should be kept separate. We can make this bug about both your issues though: (a) fprintd crashes with SIGSEGV; and (b) login screen can't survive fprintd failure. Next please follow the steps in https://wiki.ubuntu.com/Bugs/Responses#Missing_a_crash_report_or_having_a_.crash_attachment to look for the fprintd crash. ** Changed in: gdm3 (Ubuntu) Status: Incomplete => New ** Also affects: fprintd (Ubuntu) Importance: Undecided Status: New ** Summary changed: - No login screen when fprintd is installed and not starting + No login screen when fprintd crashes ** Changed in: fprintd (Ubuntu) Importance: Undecided => High ** Changed in: fprintd (Ubuntu) Status: New => Incomplete ** Changed in: gdm3 (Ubuntu) Importance: High => Medium -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1960336 Title: No login screen when fprintd crashes Status in fprintd package in Ubuntu: Incomplete Status in gdm3 package in Ubuntu: New Bug description: After a recent update, when using gdm3 as login manager, there is no account visible and it is not possible to login. When switching to lightdm I can login but sleep is broken and some notifications do not work. Running the latest 22.04 dev branch with Wayland and Nvidia driver. Had to select kernel 5.12 to have display link working. This issue occurs with and without external displays attached. A recent attempt to switch back to gdm3 gave me just a black screen. I tried to reinstall gdm3 to no avail. This seems like a quite serious issue, hence this report for the dev version. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu76 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DisplayManager: lightdm DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2019-12-17 (784 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) NonfreeKernelModules: nvidia_modeset wl nvidia Package: gnome-shell 41.3-1ubuntu1 PackageArchitecture: amd64 RelatedPackageVersions: mutter-common 41.3-1ubuntu1 Tags: third-party-packages jammy Uname: Linux 5.12.19-051219-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip docker libvirt lpadmin lxd microk8s plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fprintd/+bug/1960336/+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 1942789] Re: On-demand and RTD3 need to be separated
Hi Chris, For -390, we did find a machine to test it and also provided a corresponding handler in https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1957094 The bug1957094 is completed, does it solve your concerns? Also CC, Brian and Timo for awareness. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1942789 Title: On-demand and RTD3 need to be separated Status in OEM Priority Project: Confirmed Status in nvidia-prime package in Ubuntu: Fix Released Status in nvidia-prime source package in Focal: Incomplete Status in nvidia-prime source package in Hirsute: Invalid Bug description: [Steps to reproduce] 1. Install 20.04.3 with "Third-party packages" on a system which containing a RTD3 supported nvidia card. 2. After the installation, press enter to reboot system 3. prime-select query [Expected result] on-demand [Actual result] performance --- It's because ubiquity launches `ubuntu-drivers install --packages-list ...` in live system but install each package to target storage. When installing nvidia-prime, the preinst set "on" to "/etc/prime- discrete" which will be referred by gpu-manager. The gpu-manager will set to performance mode. After confirming with Alberto on Mattermost, since we don't have a nvidia driver which lower than 450 version since focal. I think we are ok to switch to on-demand mode. --- [Impact] * Ubuntu will set GPU mode to performance as default which may use more power * User can't use GPU for other purpose (eg: deep-learning) if RTD3 is not supported * According to Nvidia README, the RTD3 doesn't support on non-laptop machine [Test Plan] * Install Ubuntu, and then execute 'ubuntu-drivers install' to install GPU driver. After the installation, reboot the system. Execute "prime-select query" should get "on-demand" * Old GPU (which supported by nvidia-390 only) will keep in performance mode, refer LP:1957094. Execute "prime-select query" should get "nvidia" * On non-laptop machine. Can set GPU mode to on-demand * On laptop with GPU in runtime PM support list. Set GPU mode to on-demand and Nvidia driver is loaded with "NVreg_DynamicPowerManagement=0x02" [Where problems could occur] * With GPU supported RTD3 not able enable runtime PM on non-laptop. But based on the Nvidia README, this case shall not happened. [Other Info] Changelogs: nvidia-prime (0.8.16~0.20.04.2) focal; urgency=medium [ Jeremy Szu ] * Set on-demand mode as default nvidia mode (LP: #1942307) [ Alberto Milone ] * prime-select: - Detect chassis type and enable RTD3 only on laptops (LP: #1942788). - on-demand mode doesn't need to depend on RTD3 (LP: #1942789). - Use bootvga detection when last_gfx_boot is not available. - Don't check the current profile when setting a profile (LP: #1946476). - Catch BrokenPipeError. - Use bootvga detection when last_gfx_boot is not available. nvidia-prime (0.8.16.2~0.21.04.1) hirsute; urgency=medium [ Jeremy Szu ] * Set on-demand mode as default nvidia mode (LP: #1942307) [ Alberto Milone ] * prime-select: - Detect chassis type and enable RTD3 only on laptops (LP: #1942788). - on-demand mode doesn't need to depend on RTD3 (LP: #1942789). - Use bootvga detection when last_gfx_boot is not available. - Don't check the current profile when setting a profile (LP: #1946476). To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1942789/+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 1960898] Re: Wayland sessions crash with Gjs:ERROR:../gi/interface.cpp:101:bool InterfacePrototype::has_instance_impl(JSContext*, const JS::CallArgs&): assertion failed: (args[
** Also affects: gjs (Ubuntu) Importance: Undecided Status: New ** Changed in: gjs (Ubuntu) Importance: Undecided => Medium ** Changed in: gjs (Ubuntu) Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) ** Changed in: gjs (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1960898 Title: Wayland sessions crash with Gjs:ERROR:../gi/interface.cpp:101:bool InterfacePrototype::has_instance_impl(JSContext*, const JS::CallArgs&): assertion failed: (args[0].isObject()) from ubuntu- d...@ubuntu.com/locations.js:1108 Status in gjs package in Ubuntu: In Progress Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: New Bug description: Hardware: https://linux-hardware.org/?probe=1055dc7082 Worked without Problem in 21.04 Had some flicker and problem with the left dock in 21.10 not working since updating to 22.04 now I'm running xorg. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 41.3-1ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Uname: Linux 5.15.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu76 Architecture: amd64 CasperMD5CheckMismatches: ./pool/restricted/n/nvidia-graphics-drivers-450/libnvidia-gl-450_450.102.04-0ubuntu2_amd64.deb CasperMD5CheckResult: fail CurrentDesktop: ubuntu:GNOME Date: Tue Feb 15 08:07:04 2022 DisplayManager: gdm3 InstallationDate: Installed on 2021-08-15 (183 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) RelatedPackageVersions: mutter-common 41.3-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to jammy on 2022-02-14 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/1960898/+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 1961041] Re: gnome-shell crashed with SIGSEGV in meta_context_run_main_loop()
** Information type changed from Private to Public -- 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/1961041 Title: gnome-shell crashed with SIGSEGV in meta_context_run_main_loop() Status in gnome-shell package in Ubuntu: New Bug description: Happened after opening the Ubuntu Pro popup. Not sure if it's related though. ProblemType: Crash DistroRelease: Ubuntu 22.04 Package: gnome-shell 41.3-1ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Uname: Linux 5.15.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu76 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Feb 16 11:06:55 2022 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2022-02-03 (13 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220202) ProcCmdline: /usr/bin/gnome-shell RelatedPackageVersions: mutter-common 41.3-1ubuntu5 SegvAnalysis: Segfault happened at: 0x7f0dc0d9a808 <__pthread_kill_internal+24>: mov 0x28,%eax PC (0x7f0dc0d9a808) ok source "0x28" (0x0028) not located in a known VMA region (needed readable region)! destination "%eax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: gnome-shell StacktraceTop: meta_context_run_main_loop () from /lib/x86_64-linux-gnu/libmutter-9.so.0 g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 meta_context_run_main_loop () from /lib/x86_64-linux-gnu/libmutter-9.so.0 Title: gnome-shell crashed with SIGSEGV in meta_context_run_main_loop() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1961041/+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 1953052] Re: In Jammy sound level reset after reboot
** Also affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Changed in: pulseaudio (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1953052 Title: In Jammy sound level reset after reboot Status in alsa-utils package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: After reboot sound level is reset ignoring the level set in previous session. I manually set the sound output level at next boot the sound is set at a different level (about 70%) Expected: the sound level is persistent across power off/on What happens : sound level is set at a different level (about 70%) Note: this problem does not occur on different partitions of same PC running Ubuntu 20.04 or 21.10 corrado@corrado-p3-jj-1130:~$ apt policy gnome-control-center gnome-control-center: Installed: 1:41.1-1ubuntu1 Candidate: 1:41.1-1ubuntu1 Version table: *** 1:41.1-1ubuntu1 500 500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status corrado@corrado-p3-jj-1130:~$ inxi -Fx System:Host: corrado-p3-jj-1130 Kernel: 5.13.0-19-generic x86_64 bits: 64 compiler: gcc v: 11.2.0 Desktop: GNOME 40.5 Distro: Ubuntu 22.04 (Jammy Jellyfish) Machine: Type: Laptop System: Dell product: Inspiron 3793 v: N/A serial: Mobo: Dell model: 0C1PF2 v: A00 serial: UEFI: Dell v: 1.5.0 date: 12/17/2019 Battery: ID-1: BAT0 charge: 13.9 Wh (42.1%) condition: 33.0/42.0 Wh (78.7%) volts: 11.3 min: 11.4 model: SWD-ATL3.618 DELL WJPC403 status: Discharging CPU: Info: Quad Core model: Intel Core i5-1035G1 bits: 64 type: MT MCP arch: Ice Lake rev: 5 cache: L2: 6 MiB flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 19046 Speed: 968 MHz min/max: 400/1000 MHz Core speeds (MHz): 1: 968 2: 710 3: 706 4: 714 5: 966 6: 712 7: 724 8: 821 Graphics: Device-1: Intel Iris Plus Graphics G1 vendor: Dell driver: i915 v: kernel bus-ID: 00:02.0 Device-2: Realtek Integrated_Webcam_HD type: USB driver: uvcvideo bus-ID: 1-6:3 Display: wayland server: X.Org 1.21.1.2 compositor: gnome-shell driver: loaded: i915 note: n/a (using device driver) resolution: 1920x1080~60Hz OpenGL: renderer: Mesa Intel UHD Graphics (ICL GT1) v: 4.6 Mesa 21.2.2 direct render: Yes Audio: Device-1: Intel Ice Lake-LP Smart Sound Audio vendor: Dell driver: snd_hda_intel v: kernel bus-ID: 00:1f.3 Sound Server-1: ALSA v: k5.13.0-19-generic running: yes Sound Server-2: PulseAudio v: 15.0 running: yes Sound Server-3: PipeWire v: 0.3.40 running: yes Network: Device-1: Realtek RTL810xE PCI Express Fast Ethernet vendor: Dell driver: r8169 v: kernel port: 3000 bus-ID: 01:00.0 IF: enp1s0 state: down mac: 98:e7:43:59:19:19 Device-2: Qualcomm Atheros QCA9377 802.11ac Wireless Network Adapter vendor: Dell driver: ath10k_pci v: kernel bus-ID: 02:00.0 IF: wlp2s0 state: up mac: d8:12:65:b8:21:b9 Bluetooth: Device-1: Qualcomm Atheros type: USB driver: btusb v: 0.8 bus-ID: 1-10:4 Report: hciconfig ID: hci0 rfk-id: 0 state: down bt-service: enabled,running rfk-block: hardware: no software: yes address: D8:12:65:B8:21:BA Drives:Local Storage: total: 942.7 GiB used: 11.77 GiB (1.2%) ID-1: /dev/nvme0n1 vendor: Toshiba model: KBG40ZNS512G NVMe KIOXIA 512GB size: 476.94 GiB temp: 24.9 C ID-2: /dev/sda vendor: Crucial model: CT500MX500SSD1 size: 465.76 GiB Partition: ID-1: / size: 46.95 GiB used: 11.73 GiB (25.0%) fs: ext4 dev: /dev/nvme0n1p3 ID-2: /boot/efi size: 246 MiB used: 46.4 MiB (18.9%) fs: vfat dev: /dev/nvme0n1p1 Swap: Alert: No swap data was found. Sensors: System Temperatures: cpu: 27.8 C mobo: N/A Fan Speeds (RPM): cpu: 0 Info: Processes: 263 Uptime: 31m Memory: 15.4 GiB used: 2.45 GiB (15.9%) Init: systemd runlevel: 5 Compilers: gcc: N/A Packages: 1785 Shell: Bash v: 5.1.12 inxi: 3.3.07 corrado@corrado-p3-jj-1130:~$ --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu74 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-11-30 (2 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211130) Package: gnome-control-center 1:41.1-1ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Tags: wayland-session jammy Uname: Linux 5.13.0-19-generic x86_64 UpgradeStatus: No upgrade log present
[Desktop-packages] [Bug 1960898] Re: Wayland sessions crash with Gjs:ERROR:../gi/interface.cpp:101:bool InterfacePrototype::has_instance_impl(JSContext*, const JS::CallArgs&): assertion failed: (args[
AlderHorst, thanks for the feedback. So gjs in this case should definitely not crash, and I've fixed it there [1] (will prepare a package soon). I'm quite curious to understand how is possible that Gio would emit a null device in such case, but that's another issue I'll have to handle. I'll try to simulate your setup but maybe can you provide the output of this script? https://www.pastery.net/menmxf/ Just save it in disk and run it with `gjs gio-mounts-debug.js`. IIRC I noticed during development that it could happen that we may get a case where a Mount is added but its relative GVolume isn't set (yet). [1] https://gitlab.gnome.org/GNOME/gjs/-/merge_requests/726 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1960898 Title: Wayland sessions crash with Gjs:ERROR:../gi/interface.cpp:101:bool InterfacePrototype::has_instance_impl(JSContext*, const JS::CallArgs&): assertion failed: (args[0].isObject()) from ubuntu- d...@ubuntu.com/locations.js:1108 Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: New Bug description: Hardware: https://linux-hardware.org/?probe=1055dc7082 Worked without Problem in 21.04 Had some flicker and problem with the left dock in 21.10 not working since updating to 22.04 now I'm running xorg. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 41.3-1ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Uname: Linux 5.15.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu76 Architecture: amd64 CasperMD5CheckMismatches: ./pool/restricted/n/nvidia-graphics-drivers-450/libnvidia-gl-450_450.102.04-0ubuntu2_amd64.deb CasperMD5CheckResult: fail CurrentDesktop: ubuntu:GNOME Date: Tue Feb 15 08:07:04 2022 DisplayManager: gdm3 InstallationDate: Installed on 2021-08-15 (183 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) RelatedPackageVersions: mutter-common 41.3-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to jammy on 2022-02-14 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1960898/+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 1929038] Re: [SRU] Backport to 20.04 LTS
** Changed in: adsys (Ubuntu Focal) Milestone: ubuntu-20.04.4 => focal-updates -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to adsys in Ubuntu. https://bugs.launchpad.net/bugs/1929038 Title: [SRU] Backport to 20.04 LTS Status in adsys package in Ubuntu: Fix Released Status in golang-1.16 package in Ubuntu: Fix Released Status in adsys source package in Focal: Fix Committed Status in golang-1.16 source package in Focal: Fix Released Bug description: As part of our entreprise desktop offering, there is the request to backport ADSys to 20.04 LTS. The package is in universe for now. ADSys is our Active Directory GPO integration. It’s available starting Ubuntu 21.04. [Impact] * ADSys is a new package. Impacts is thus only for people installing. * It depends on a recent Golang (1.16). We thus needs to backport this package from Ubuntu 21.04/21.10 (1.16.2-0ubuntu1 at the time of this writing) by introducing a versioned separate package (each Go version is a separate package already in the distribution). It is similar to what has been done for snaps in previous LTS. * This is a entreprise feature requested by desktop customers running LTS. [Test Plan for Golang 1.16] 1. Ensure Golang 1.16 is published in -proposed 2. Start a build with a package, requiring Golang 1.16 (dependency + PATH set to Golang 1.16 go binary). 3. Ensure the package builds successfully. 4. Run go version which should display: "go1.16.x" (x being the version uploaded). [Test Plan for ADSys] 1. Configure your machine with AD, with a correctly configured SSSD and KRB5 (AD user should be able to log in). Instructions can be found on https://github.com/ubuntu/adsys/wiki/2.-Prerequisites 2. Install admx and adml files on your AD controller: https://github.com/ubuntu/adsys/wiki/3.-AD-Setup 3. Configure some values in AD (https://github.com/ubuntu/adsys/wiki/4.-Using-GPO), for instance: * GDM login screen background * User favorites apps 4. Install ADSys, reboot the machine and login in as an AD user 5. Ensure both GDM background and user favorites apps follows what you set in AD [Where problems could occur] For Go 1.16: * Package depending on this Go version would not be able to compile. * As this is a separate, versionned, new package, no impact on existing ones. * FYI, we already built ADSys against this Go version in our ppa: https://launchpad.net/~didrocks/+archive/ubuntu/adsys For ADSys: * Machine will fail booting if ADSys can’t connect to AD on first boot. * AD User will fail logging if ADSys can’t connect to AD on first boot. * As this is a separate, versionned, new package, no impact on existing installations. [Other Info] * ADSys (built against Go 1.16 in the same PPA) is battle-tested from our PPA. * We will first upload Go 1.16 and let it migrate before uploading ADSys itself. * Of course, ADSys new version (the one we will backport) will be first uploaded in Impish. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/adsys/+bug/1929038/+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 1957094] Update Released
The verification of the Stable Release Update for nvidia-settings has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- 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/1957094 Title: on-demand mode doesn't work with nvidia-390 Status in OEM Priority Project: New Status in nvidia-settings package in Ubuntu: Fix Released Status in ubuntu-drivers-common package in Ubuntu: Fix Committed Status in nvidia-settings source package in Focal: Fix Released Status in ubuntu-drivers-common source package in Focal: Fix Released Status in nvidia-settings source package in Impish: Fix Committed Status in ubuntu-drivers-common source package in Impish: Fix Committed Status in nvidia-settings source package in Jammy: Fix Released Status in ubuntu-drivers-common source package in Jammy: Fix Committed Bug description: [Impact] * In any Ubuntu series, if user using a old GPU (which supported by nvidia-390 only) then issuing glxinfo will get "Error: couldn't find RGB GLX visual or fbconfig". Which mean the Xorg doesn't load dri driver correctly. [Test Plan] * install nvidia-390 on nvidia-390 supported system. * prime-select on-demand * reboot * glxinfo * after applying this patch, it will fall back to "ON" mode after reboot. * install nvidia-450 on nvidia-450 supported system. * prime-select on-demand * reboot the system * prime-select query (and check that on-demand mode is still in use). [Where problems could occur] * Since nvidia-390 doesn't support on-demand mode (RTD3 either). If a user stays in on-demand mode with 390 without problem, the after upgrading u-d-c and reboot. The mode will fall back to "ON" mode. * From my point of view, it's fine because nvidia-390 doesn't support RTD3. Thus, the nvidia will always stay in "Active" stage no matter which mode it is. * While there is no way to inform the user about this change, changing to the only supported default will avoid breaking GLX. --- The regression from https://bugs.launchpad.net/ubuntu/+source/ubuntu- drivers-common/+bug/1942789. It impacts Jammy and Impish so far. [Steps to reproduce] 1. Find a GPU supports nvidia-390 2. ubuntu-drivers install nvidia:390 3. prime-select on-demand 4. glxinfo [Expected result] Shows intel or nvidia drives monitor [Actual result] Error: couldn't find RGB GLX visual or fbconfig Since we are all agree "on-demand" mode as default mode. Pre-talk with Alberto, on-demand doesn't support with nvidia-390 (no matter RTD3). We could consider to make it as performance mode and leave a note on nvidia-settings. I'll prepare some test packages. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1957094/+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 1957094] Re: on-demand mode doesn't work with nvidia-390
This bug was fixed in the package ubuntu-drivers-common - 1:0.9.0~0.20.04.5 --- ubuntu-drivers-common (1:0.9.0~0.20.04.5) focal; urgency=medium * gpu-manager.c: - Fall back from on-demand to on if nvidia < 450 (LP: #1957094). -- Alberto Milone Tue, 18 Jan 2022 08:58:23 + ** Changed in: ubuntu-drivers-common (Ubuntu Focal) Status: Fix Committed => Fix Released -- 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/1957094 Title: on-demand mode doesn't work with nvidia-390 Status in OEM Priority Project: New Status in nvidia-settings package in Ubuntu: Fix Released Status in ubuntu-drivers-common package in Ubuntu: Fix Committed Status in nvidia-settings source package in Focal: Fix Released Status in ubuntu-drivers-common source package in Focal: Fix Released Status in nvidia-settings source package in Impish: Fix Committed Status in ubuntu-drivers-common source package in Impish: Fix Committed Status in nvidia-settings source package in Jammy: Fix Released Status in ubuntu-drivers-common source package in Jammy: Fix Committed Bug description: [Impact] * In any Ubuntu series, if user using a old GPU (which supported by nvidia-390 only) then issuing glxinfo will get "Error: couldn't find RGB GLX visual or fbconfig". Which mean the Xorg doesn't load dri driver correctly. [Test Plan] * install nvidia-390 on nvidia-390 supported system. * prime-select on-demand * reboot * glxinfo * after applying this patch, it will fall back to "ON" mode after reboot. * install nvidia-450 on nvidia-450 supported system. * prime-select on-demand * reboot the system * prime-select query (and check that on-demand mode is still in use). [Where problems could occur] * Since nvidia-390 doesn't support on-demand mode (RTD3 either). If a user stays in on-demand mode with 390 without problem, the after upgrading u-d-c and reboot. The mode will fall back to "ON" mode. * From my point of view, it's fine because nvidia-390 doesn't support RTD3. Thus, the nvidia will always stay in "Active" stage no matter which mode it is. * While there is no way to inform the user about this change, changing to the only supported default will avoid breaking GLX. --- The regression from https://bugs.launchpad.net/ubuntu/+source/ubuntu- drivers-common/+bug/1942789. It impacts Jammy and Impish so far. [Steps to reproduce] 1. Find a GPU supports nvidia-390 2. ubuntu-drivers install nvidia:390 3. prime-select on-demand 4. glxinfo [Expected result] Shows intel or nvidia drives monitor [Actual result] Error: couldn't find RGB GLX visual or fbconfig Since we are all agree "on-demand" mode as default mode. Pre-talk with Alberto, on-demand doesn't support with nvidia-390 (no matter RTD3). We could consider to make it as performance mode and leave a note on nvidia-settings. I'll prepare some test packages. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1957094/+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 1957094] Re: on-demand mode doesn't work with nvidia-390
This bug was fixed in the package nvidia-settings - 470.57.01-0ubuntu0.20.04.3 --- nvidia-settings (470.57.01-0ubuntu0.20.04.3) focal; urgency=medium [ Jeremy Szu ] * debian/patches/18_remove_power-saving_if_on-demand.patch, debian/patches/19_lp1957094-adjust-on-demand-mode-description.patch: - Disable the item of power saving mode if on-demand is supported (LP: #1957094). - Leave the item there because the user might issue 'prime-select intel' manually. Thus, leave it there could prevent selection confuse. - Explain the on-demand mode if driver < 450. -- Alberto Milone Tue, 18 Jan 2022 15:43:01 + ** Changed in: nvidia-settings (Ubuntu Focal) Status: Fix Committed => Fix Released -- 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/1957094 Title: on-demand mode doesn't work with nvidia-390 Status in OEM Priority Project: New Status in nvidia-settings package in Ubuntu: Fix Released Status in ubuntu-drivers-common package in Ubuntu: Fix Committed Status in nvidia-settings source package in Focal: Fix Released Status in ubuntu-drivers-common source package in Focal: Fix Released Status in nvidia-settings source package in Impish: Fix Committed Status in ubuntu-drivers-common source package in Impish: Fix Committed Status in nvidia-settings source package in Jammy: Fix Released Status in ubuntu-drivers-common source package in Jammy: Fix Committed Bug description: [Impact] * In any Ubuntu series, if user using a old GPU (which supported by nvidia-390 only) then issuing glxinfo will get "Error: couldn't find RGB GLX visual or fbconfig". Which mean the Xorg doesn't load dri driver correctly. [Test Plan] * install nvidia-390 on nvidia-390 supported system. * prime-select on-demand * reboot * glxinfo * after applying this patch, it will fall back to "ON" mode after reboot. * install nvidia-450 on nvidia-450 supported system. * prime-select on-demand * reboot the system * prime-select query (and check that on-demand mode is still in use). [Where problems could occur] * Since nvidia-390 doesn't support on-demand mode (RTD3 either). If a user stays in on-demand mode with 390 without problem, the after upgrading u-d-c and reboot. The mode will fall back to "ON" mode. * From my point of view, it's fine because nvidia-390 doesn't support RTD3. Thus, the nvidia will always stay in "Active" stage no matter which mode it is. * While there is no way to inform the user about this change, changing to the only supported default will avoid breaking GLX. --- The regression from https://bugs.launchpad.net/ubuntu/+source/ubuntu- drivers-common/+bug/1942789. It impacts Jammy and Impish so far. [Steps to reproduce] 1. Find a GPU supports nvidia-390 2. ubuntu-drivers install nvidia:390 3. prime-select on-demand 4. glxinfo [Expected result] Shows intel or nvidia drives monitor [Actual result] Error: couldn't find RGB GLX visual or fbconfig Since we are all agree "on-demand" mode as default mode. Pre-talk with Alberto, on-demand doesn't support with nvidia-390 (no matter RTD3). We could consider to make it as performance mode and leave a note on nvidia-settings. I'll prepare some test packages. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1957094/+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 1960601] Re: Ubuntu 20.04 stopped detecting HP LaserJet P2055dn after this morning's update
@till-kamppeter, I'm not certain what you mean by the "upstream source." The printer auto-installed when I installed Ubuntu 20.04 shortly after its release. After your post, I did: # apt purge cups cups-client cups-bsd # apt purge hplip hpijs printer-driver-gutenprint # apt autoremove # reboot # apt install cups cups-client cups-bsd # apt install printer-driver-gutenprint printer-driver-hpcups printer-driver-hpijs printer-driver-postscript-hp # reboot # journalctl -b 0 and got >2000 consecutive entries reading: AVC apparmor="DENIED" operation="create" profile="snap.hplip-printer- app.hplip-printer-app-server" pid=2211 comm="hplip-printer-a" family="inet" sock_type="stream" protocol=0 requested_mask="create" denied_mask="create" AppArmor is not expressly configured (meaning no one here manually configured it) on this system. I'd guess this is what's at work but don't know. Please advise. Otherwise, regarding snap, I don't code around others' steaming piles. -- 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/1960601 Title: Ubuntu 20.04 stopped detecting HP LaserJet P2055dn after this morning's update Status in cups package in Ubuntu: New Bug description: I printed yesterday. I updated Ubuntu 20.04.3 this morning. The system now does not detect the HP LaserJet P2055dn to which it has been connected for years. The output of the command "apt-cache policy cups" is: cups: Installed: 2.3.1-9ubuntu1.1 Candidate: 2.3.1-9ubuntu1.1 Version table: *** 2.3.1-9ubuntu1.1 500 500 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu focal-security/main amd64 Packages 100 /var/lib/dpkg/status 2.3.1-9ubuntu1 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages What I expected to happen was to print a document. Then, for the system to recognize the printer when I tried to reinstall it. What happened instead was that printing failed. Settings > Printers > Additional Printer Settings vomited an error message saying that the printer may not be connected. The print job hung on "Processing" for 5-10 minutes before I terminated it. I deleted the printer on the system and the system would / could not detect the device. No obvious means exists to install a printer driver for a specified printer, which is an astonishing design failure for the platform. I have rebooted the system and the printer multiple times throughout this process. I also attempted to update the system but no updates are available. All the wiring and power is as before. The system recognizes any number of other USB devices connected to it, including scanners, etc., that are freshly powered on. Power cycling the HP printer has no effect on lsusb output. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: cups 2.3.1-9ubuntu1.1 ProcVersionSignature: Ubuntu 5.4.0-99.112-generic 5.4.162 Uname: Linux 5.4.0-99-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: pass CupsErrorLog: E [11/Feb/2022:00:00:13 -0800] Unable to open listen socket for address [v1.::1]:631 - Address family not supported by protocol. E [11/Feb/2022:00:10:42 -0800] [Client 27] Returning HTTP Forbidden for CUPS-Add-Modify-Printer (ipp://localhost/printers/HP-LaserJet-P2055dn) from localhost E [11/Feb/2022:00:17:48 -0800] [Client 1329757] Returning IPP client-error-document-format-not-supported for Print-Job (ipp://localhost:631/printers/CUPS-BRF-Printer) from localhost. CurrentDesktop: ubuntu:GNOME CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Operation not permitted Date: Fri Feb 11 00:44:52 2022 InstallationDate: Installed on 2020-08-20 (539 days ago) InstallationMedia: Ubuntu-Server 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) KernLog: Lpstat: device for CUPS-BRF-Printer: cups-brf:/ MachineType: System manufacturer System Product Name Papersize: letter PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/CUPS-BRF-Printer.ppd'] failed with exit code 2: grep: /etc/cups/ppd/CUPS-BRF-Printer.ppd: Permission denied 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.4.0-99-generic root=UUID=94757e46-a814-4c27-b3a5-4ff139bd211d ro ipv6.disable=1 nomodeset ipv6.disable=1 SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/19/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1602 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P9X79-E WS dmi.board.vendor: ASUSTeK
[Desktop-packages] [Bug 1961109] Re: package libreoffice-core 1:5.1.6~rc2-0ubuntu1~xenial9 failed to install/upgrade: impossible de copier les données extraites pour « ./usr/lib/libreoffice/program/li
Thank you for reporting this bug to Ubuntu. Ubuntu 16.04 (xenial) reached end-of-standard-support on April 29, 2021. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases To purchase an Ubuntu Advantage subscription for extended support beyond standard, please see https://ubuntu.com/support . ** Changed in: libreoffice (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1961109 Title: package libreoffice-core 1:5.1.6~rc2-0ubuntu1~xenial9 failed to install/upgrade: impossible de copier les données extraites pour « ./usr/lib/libreoffice/program/libmergedlo.so » vers « /usr/lib/libreoffice/program/libmergedlo.so.dpkg-new » : fin de fichier ou de flux inattendue Status in libreoffice package in Ubuntu: Invalid Bug description: Tried to update Ubuntu 14-6 to more recent version, and this crash error report got triggered ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libreoffice-core 1:5.1.6~rc2-0ubuntu1~xenial9 ProcVersionSignature: Ubuntu 4.15.0-64.73~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-64-generic i686 ApportVersion: 2.20.1-0ubuntu2.19 Architecture: i386 Date: Wed Feb 16 21:48:11 2022 DpkgHistoryLog: Start-Date: 2022-02-16 21:48:09 Commandline: apt-get install -f Requested-By: em (1000) Upgrade: libreoffice-core:i386 (1:5.1.6~rc2-0ubuntu1~xenial9, 1:5.1.6~rc2-0ubuntu1~xenial10) ErrorMessage: impossible de copier les données extraites pour « ./usr/lib/libreoffice/program/libmergedlo.so » vers « /usr/lib/libreoffice/program/libmergedlo.so.dpkg-new » : fin de fichier ou de flux inattendue InstallationDate: Installed on 2019-06-12 (980 days ago) InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release i386 (20180228) RelatedPackageVersions: dpkg 1.18.4ubuntu1.5 apt 1.2.32 SourcePackage: libreoffice Title: package libreoffice-core 1:5.1.6~rc2-0ubuntu1~xenial9 failed to install/upgrade: impossible de copier les données extraites pour « ./usr/lib/libreoffice/program/libmergedlo.so » vers « /usr/lib/libreoffice/program/libmergedlo.so.dpkg-new » : fin de fichier ou de flux inattendue UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1961109/+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 1960768] Re: fwupd crash on stop
** Tags removed: rls-jj-incoming -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libgusb in Ubuntu. https://bugs.launchpad.net/bugs/1960768 Title: fwupd crash on stop Status in OEM Priority Project: Fix Released Status in fwupd package in Ubuntu: Invalid Status in libgusb package in Ubuntu: Fix Released Status in libusb package in Ubuntu: Invalid Bug description: I can reproduce crash with a similar stack as below as I stop fwupd service. https://errors.ubuntu.com/problem/4bfcf571c017010afe4775687ff2a9ca7ff79661 also test fwupd 1.7.5 (https://launchpad.net/~ycheng-twn/+archive/ubuntu/fwupd175) still can reproduce this issue. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1960768/+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 1961109] [NEW] package libreoffice-core 1:5.1.6~rc2-0ubuntu1~xenial9 failed to install/upgrade: impossible de copier les données extraites pour « ./usr/lib/libreoffice/program/
Public bug reported: Tried to update Ubuntu 14-6 to more recent version, and this crash error report got triggered ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libreoffice-core 1:5.1.6~rc2-0ubuntu1~xenial9 ProcVersionSignature: Ubuntu 4.15.0-64.73~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-64-generic i686 ApportVersion: 2.20.1-0ubuntu2.19 Architecture: i386 Date: Wed Feb 16 21:48:11 2022 DpkgHistoryLog: Start-Date: 2022-02-16 21:48:09 Commandline: apt-get install -f Requested-By: em (1000) Upgrade: libreoffice-core:i386 (1:5.1.6~rc2-0ubuntu1~xenial9, 1:5.1.6~rc2-0ubuntu1~xenial10) ErrorMessage: impossible de copier les données extraites pour « ./usr/lib/libreoffice/program/libmergedlo.so » vers « /usr/lib/libreoffice/program/libmergedlo.so.dpkg-new » : fin de fichier ou de flux inattendue InstallationDate: Installed on 2019-06-12 (980 days ago) InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release i386 (20180228) RelatedPackageVersions: dpkg 1.18.4ubuntu1.5 apt 1.2.32 SourcePackage: libreoffice Title: package libreoffice-core 1:5.1.6~rc2-0ubuntu1~xenial9 failed to install/upgrade: impossible de copier les données extraites pour « ./usr/lib/libreoffice/program/libmergedlo.so » vers « /usr/lib/libreoffice/program/libmergedlo.so.dpkg-new » : fin de fichier ou de flux inattendue UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: libreoffice (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package i386 xenial -- 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/1961109 Title: package libreoffice-core 1:5.1.6~rc2-0ubuntu1~xenial9 failed to install/upgrade: impossible de copier les données extraites pour « ./usr/lib/libreoffice/program/libmergedlo.so » vers « /usr/lib/libreoffice/program/libmergedlo.so.dpkg-new » : fin de fichier ou de flux inattendue Status in libreoffice package in Ubuntu: New Bug description: Tried to update Ubuntu 14-6 to more recent version, and this crash error report got triggered ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libreoffice-core 1:5.1.6~rc2-0ubuntu1~xenial9 ProcVersionSignature: Ubuntu 4.15.0-64.73~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-64-generic i686 ApportVersion: 2.20.1-0ubuntu2.19 Architecture: i386 Date: Wed Feb 16 21:48:11 2022 DpkgHistoryLog: Start-Date: 2022-02-16 21:48:09 Commandline: apt-get install -f Requested-By: em (1000) Upgrade: libreoffice-core:i386 (1:5.1.6~rc2-0ubuntu1~xenial9, 1:5.1.6~rc2-0ubuntu1~xenial10) ErrorMessage: impossible de copier les données extraites pour « ./usr/lib/libreoffice/program/libmergedlo.so » vers « /usr/lib/libreoffice/program/libmergedlo.so.dpkg-new » : fin de fichier ou de flux inattendue InstallationDate: Installed on 2019-06-12 (980 days ago) InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release i386 (20180228) RelatedPackageVersions: dpkg 1.18.4ubuntu1.5 apt 1.2.32 SourcePackage: libreoffice Title: package libreoffice-core 1:5.1.6~rc2-0ubuntu1~xenial9 failed to install/upgrade: impossible de copier les données extraites pour « ./usr/lib/libreoffice/program/libmergedlo.so » vers « /usr/lib/libreoffice/program/libmergedlo.so.dpkg-new » : fin de fichier ou de flux inattendue UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1961109/+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 1961108] [NEW] network options greyed out in paprefs
Public bug reported:
I installed Kubuntu 21.10 which comes with pulseaudio
1:15.0+dfsg1-1ubuntu2.2. When I start paprefs all network options are
greyed out. The problem seems to be, that the directory with the modules
is called /usr/lib/pulse-15.0+dfsg1, but paprefs expects the modules in
/usr/lib/pulse-15.0
$ strace paprefs 2>&1 |grep /lib/pulse
access("/usr/lib/pulse-15.0/modules/module-esound-protocol-tcp.so", F_OK) = -1
ENOENT (No such file or directory)
access("/usr/lib/pulse-15.0/modules/module-native-protocol-tcp.so", F_OK) = -1
ENOENT (No such file or directory)
access("/usr/lib/pulse-15.0/modules/module-zeroconf-publish.so", F_OK) = -1
ENOENT (No such file or directory)
access("/usr/lib/pulse-15.0/modules/module-zeroconf-discover.so", F_OK) = -1
ENOENT (No such file or directory)
access("/usr/lib/pulse-15.0/modules/module-raop-discover.so", F_OK) = -1 ENOENT
(No such file or directory)
access("/usr/lib/pulse-15.0/modules/module-rtp-recv.so", F_OK) = -1 ENOENT (No
such file or directory)
access("/usr/lib/pulse-15.0/modules/module-rtp-send.so", F_OK) = -1 ENOENT (No
such file or directory)
access("/usr/lib/pulse-15.0/modules/module-rygel-media-server.so", F_OK) = -1
ENOENT (No such file or directory)
Creating a symlink /usr/lib/pulse-15.0 solves the problem
** Affects: pulseaudio (Ubuntu)
Importance: Undecided
Status: New
--
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/1961108
Title:
network options greyed out in paprefs
Status in pulseaudio package in Ubuntu:
New
Bug description:
I installed Kubuntu 21.10 which comes with pulseaudio
1:15.0+dfsg1-1ubuntu2.2. When I start paprefs all network options are
greyed out. The problem seems to be, that the directory with the
modules is called /usr/lib/pulse-15.0+dfsg1, but paprefs expects the
modules in /usr/lib/pulse-15.0
$ strace paprefs 2>&1 |grep /lib/pulse
access("/usr/lib/pulse-15.0/modules/module-esound-protocol-tcp.so", F_OK) =
-1 ENOENT (No such file or directory)
access("/usr/lib/pulse-15.0/modules/module-native-protocol-tcp.so", F_OK) =
-1 ENOENT (No such file or directory)
access("/usr/lib/pulse-15.0/modules/module-zeroconf-publish.so", F_OK) = -1
ENOENT (No such file or directory)
access("/usr/lib/pulse-15.0/modules/module-zeroconf-discover.so", F_OK) = -1
ENOENT (No such file or directory)
access("/usr/lib/pulse-15.0/modules/module-raop-discover.so", F_OK) = -1
ENOENT (No such file or directory)
access("/usr/lib/pulse-15.0/modules/module-rtp-recv.so", F_OK) = -1 ENOENT
(No such file or directory)
access("/usr/lib/pulse-15.0/modules/module-rtp-send.so", F_OK) = -1 ENOENT
(No such file or directory)
access("/usr/lib/pulse-15.0/modules/module-rygel-media-server.so", F_OK) = -1
ENOENT (No such file or directory)
Creating a symlink /usr/lib/pulse-15.0 solves the problem
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1961108/+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 1960768] Re: fwupd crash on stop
> If fwupd is being backported to previous releases of Ubuntu it seems like libgusb would also need to be backported. Actually the bug was introduced in libgusb 0.3.8, fixed in libgusb 0.3.9. If older releases have older than 0.3.8 they shouldn't need libgusb backport. See comment #3. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libgusb in Ubuntu. https://bugs.launchpad.net/bugs/1960768 Title: fwupd crash on stop Status in OEM Priority Project: Fix Released Status in fwupd package in Ubuntu: Invalid Status in libgusb package in Ubuntu: Fix Released Status in libusb package in Ubuntu: Invalid Bug description: I can reproduce crash with a similar stack as below as I stop fwupd service. https://errors.ubuntu.com/problem/4bfcf571c017010afe4775687ff2a9ca7ff79661 also test fwupd 1.7.5 (https://launchpad.net/~ycheng-twn/+archive/ubuntu/fwupd175) still can reproduce this issue. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1960768/+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 1960768] Re: fwupd crash on stop
If fwupd is being backported to previous releases of Ubuntu it seems like libgusb would also need to be backported. ** Tags added: rls-jj-incoming -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libgusb in Ubuntu. https://bugs.launchpad.net/bugs/1960768 Title: fwupd crash on stop Status in OEM Priority Project: Fix Released Status in fwupd package in Ubuntu: Invalid Status in libgusb package in Ubuntu: Fix Released Status in libusb package in Ubuntu: Invalid Bug description: I can reproduce crash with a similar stack as below as I stop fwupd service. https://errors.ubuntu.com/problem/4bfcf571c017010afe4775687ff2a9ca7ff79661 also test fwupd 1.7.5 (https://launchpad.net/~ycheng-twn/+archive/ubuntu/fwupd175) still can reproduce this issue. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1960768/+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 1960924] Re: qpdf 10.6.1 not syncing?
It helps. Thanks. I just released 10.6.2, and pikepdf 5.0 is also being released hopefully today to get the two back in sync. Hopefully no further manual action will be required. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to qpdf in Ubuntu. https://bugs.launchpad.net/bugs/1960924 Title: qpdf 10.6.1 not syncing? Status in qpdf package in Ubuntu: New Bug description: I'm noticing that qpdf-10.6.1 is not syncing from Debian even though, as far as I can see, automatic sync freeze has not yet happened. There are some major changes in 10.6 that I would really like to get into Ubuntu because they include transitional code to help users migrate to qpdf 11. Is there something that needs to happen for this to sync? I don't want to miss the window. At this time, there are test failures in pikepdf because of a bug fix to qpdf in transcoding. We have determined that these test failures don't indicate a serious problem with either qpdf or pikepdf -- they are basically that pikepdf had some tests that were depending on incorrect qpdf functionality. For details, see https://github.com/pikepdf/pikepdf/issues/303 The pikepdf author is aware of the upcoming Ubuntu 22.04 freeze and is trying to get a fix in in time, but I'm hoping we can avoid getting into a situation where we miss the bus. There's a chance I might release 10.6.2 to fix one other minor transcoding issue, but I don't consider the issue to be important enough to justify a release. But if the pikepdf author wants a release to simplify his testing, I will do it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qpdf/+bug/1960924/+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 1960848] Re: sane-backends stuck in -proposed due to gscan2pdf autopkgtest failure
** Changed in: gscan2pdf (Debian) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to sane-backends in Ubuntu. https://bugs.launchpad.net/bugs/1960848 Title: sane-backends stuck in -proposed due to gscan2pdf autopkgtest failure Status in gscan2pdf package in Ubuntu: Fix Released Status in sane-backends package in Ubuntu: Invalid Status in gscan2pdf package in Debian: Fix Released Bug description: Version 1.1.1-2ubuntu1 of sane-backends does not migrate to jammy since the autopkgtest for gscan2pdf fails for multiple architectures. It's actually the upstream tests which fail, and gscan2pdf also fails to build on Debian unstable with the very same errors: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1005576 Probably a gscan2pdf rebuild would fail on Ubuntu too, but I haven't confirmed that. Several other packages are blocked from migration because of this problem with gscan2pdf. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gscan2pdf/+bug/1960848/+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 1960848] Re: sane-backends stuck in -proposed due to gscan2pdf autopkgtest failure
Fixed in gscan2pdf 2.12.5-1. ** Changed in: gscan2pdf (Ubuntu) Status: New => Fix Released ** Changed in: sane-backends (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to sane-backends in Ubuntu. https://bugs.launchpad.net/bugs/1960848 Title: sane-backends stuck in -proposed due to gscan2pdf autopkgtest failure Status in gscan2pdf package in Ubuntu: Fix Released Status in sane-backends package in Ubuntu: Invalid Status in gscan2pdf package in Debian: New Bug description: Version 1.1.1-2ubuntu1 of sane-backends does not migrate to jammy since the autopkgtest for gscan2pdf fails for multiple architectures. It's actually the upstream tests which fail, and gscan2pdf also fails to build on Debian unstable with the very same errors: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1005576 Probably a gscan2pdf rebuild would fail on Ubuntu too, but I haven't confirmed that. Several other packages are blocked from migration because of this problem with gscan2pdf. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gscan2pdf/+bug/1960848/+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 1816634] Re: GNOME Shell consistently ignores mouse clicks in a particular app window
The bug is reproduced on Eclipse IDE (screenshot https://disk.yandex.ru/i/z7kqQV47z8xeFQ). Left click always closes the popup window instead of set focus on it. Pressing the "F2" buttons leads to the same result. Ubuntu 20.04.3 LTS GNOME Shell 3.36.9 Eclipse 2021-12 (4.22.0) -- 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/1816634 Title: GNOME Shell consistently ignores mouse clicks in a particular app window Status in Mutter: New Status in gnome-shell package in Ubuntu: Triaged Bug description: https://gitlab.gnome.org/GNOME/mutter/issues/475 --- This is similar in some ways to https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1181666 but affects only the mouse, not the keyboard, and is consistent almost all (99%+) of the time. This is happening for Ubuntu 18.04.2 LTS (bionic) in the default desktop environment (Ubuntu). It also happens for the GNOME and GNOME Classic desktop environments. The version of gnome- shell is 3.28.3-0ubuntu0.18.04.4. Our program is a blend of C# winforms (Mono) with embedded web browser windows using Geckofx45 (mozilla version 45). Editing windows in the program use HTML to display formatting and typescript/javascript code to assist with popup dialogs and other editing help. Inside these editing windows, left mouse clicks are essentially ignored. Keyboarding still works fine as far as I can tell. Clicking on the gear button inside the editing window fails to bring up the Styles dialog more than 95% of the time. When the dialog does display, it is always (100%) nonfunctional as the first click in it causes it to close immediately. Tracing the internal behavior of the code, it appears that clicking the first time inside the editing (browser) window causes a series of WM_FOCUS messages to be sent and the javascript to hook up a left mouse click handler to a gear button displayed in the lower left corner of the editing window. This is the expected behavior, and the same as on other window managers. But then, on GNOME Shell only, a series of WM_KILLFOCUS messages are sent immediately. This does not happen for other window managers. (The main window receives a WM_ACTIVATE message with the argument to make it deactivate.) Any other left mouse clicks inside that window are ignored >95% of the time, probably only when double clicking quickly enough to occur before those messages to lose focus/deactivate are handled. (Right mouse clicks are handled at a higher level and appear to function normally.) The program in question is called Bloom. The source code is available at https://github.com/BloomBooks/BloomDesktop and prebuilt debian/ubuntu packages are available at http://packages.sil.org/ubuntu/ as bloom-desktop or bloom-desktop- beta. After spending a few days looking at this problem, I've reluctantly come to the conclusion that it must be a GNOME Shell bug that I can't work around in our code. It's working fine in Microsoft Windows and all the other Linux window managers that I've tested (Unity, Cinnamon, KDE Plasma, MATE, XFCE, and LXDE). To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1816634/+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 1952947] Re: ubuntu-bug -w (using xprop) doesn't work under wayland
** Changed in: apport (Ubuntu Impish) Importance: Medium => Low ** Also affects: apport (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: x11-utils (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: apport (Ubuntu Focal) Status: New => Triaged ** Changed in: apport (Ubuntu Focal) Importance: Undecided => Low -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to x11-utils in Ubuntu. https://bugs.launchpad.net/bugs/1952947 Title: ubuntu-bug -w (using xprop) doesn't work under wayland Status in apport package in Ubuntu: Fix Released Status in x11-utils package in Ubuntu: Invalid Status in apport source package in Focal: Triaged Status in x11-utils source package in Focal: New Status in apport source package in Impish: Triaged Status in x11-utils source package in Impish: Invalid Status in apport source package in Jammy: Fix Released Status in x11-utils source package in Jammy: Invalid Bug description: [Impact] This bug makes it more difficult for Wayland users to report bugs with apport. When a Wayland user tries to use the -w,--window option, apport fails silently. We do not want users to face a high barrier to submitting bug reports. The patch for this bug adds a message explaining that the -w,--window option cannot be used on Wayland, and suggests a method for finding the window's PID instead. [Test Plan] * Log on to Ubuntu on Wayland. You can check that $XDG_SESSION_TYPE=="wayland" in your current session. * Open a terminal, and run `ubuntu-bug -w`. * Click on any other window, and observe that the apport UI will not respond. [Where problems could occur] The patch uses os.getenv to check that $XDG_SESSION_TYPE is set to 'wayland'. If either of these strings in the patch were wrong, or the environment variable was not used in the target release, the condition would likely never be true. [Original Description] I want to report a Bug about the application Studio Controls. As I did it already quite a few times, I run "ubuntu-bug -w", get a message that I can select the window of the app I want to report a bug about after closing this message. I close the message with a click on the appropriate button. I click on the window of the application "Studio Controls" that I want to report a bug about. Nothing happens. I wait for a few minutes. Still nothing happens. In the console where I started ubuntu-bug -w I see the following message: (apport-gtk:11537): Gdk-CRITICAL **: 20:06:41.384: gdk_wayland_window_set_dbus_properties_libgtk_only: assertion 'GDK_IS_WAYLAND_WINDOW (window)' failed What I expect: Usaully when I use this procedure, after a relatively short while a new message window pops up asking me if the bug should be reported and showing me the data that is sent to Launchpad. I tried other applications, too, same effect. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: apport 2.20.11-0ubuntu71 ProcVersionSignature: Ubuntu 5.13.0-21.21-lowlatency 5.13.18 Uname: Linux 5.13.0-21-lowlatency x86_64 ApportLog: ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Dec 1 20:01:23 2021 InstallationDate: Installed on 2020-04-12 (597 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitecture: all SourcePackage: apport UpgradeStatus: Upgraded to impish on 2021-11-14 (16 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1952947/+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 1960865] Re: System freeze when plugging USB-C monitor into a hybrid Intel/Nvidia laptop: [drm:__nv_drm_gem_nvkms_memory_prime_get_sg_table [nvidia_drm]] *ERROR* [nvidia-drm] [
I'll reproduce later today after hours. Will also try to install 22.04 to see if it helps. -- 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/1960865 Title: System freeze when plugging USB-C monitor into a hybrid Intel/Nvidia laptop: [drm:__nv_drm_gem_nvkms_memory_prime_get_sg_table [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x0100] Failed to get memory pages for NvKmsKapiMemory Status in Mutter: Unknown Status in linux package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Opinion Status in nvidia-graphics-drivers-470 package in Ubuntu: Confirmed Bug description: I recently upgraded my NVidia drivers on my ThinkPad P1 Gen 3. If I start Ubuntu on Wayland session and plug in my USB-C monitor the system reliably completely freeze. The freeze is also reproducible if the screen is plugged in during startup and trying to login into a Wayland session. Only Wayland session experiences a crash. The crash happens ONLY if the USB-C monitor is plugged in. USB-C monitor is also a USB3 hub. Hardware seems to work fine, as Windows shows no issues with the setup. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: xorg 1:7.7+22ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-30.33-generic 5.13.19 Uname: Linux 5.13.0-30-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 470.103.01 Thu Jan 6 12:10:04 UTC 2022 GCC version: gcc version 11.2.0 (Ubuntu 11.2.0-7ubuntu2) ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Feb 14 16:39:34 2022 DistUpgraded: 2021-10-14 18:36:11,564 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: impish DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GpuHangFrequency: Continuously GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Within the last few days GraphicsCard: Intel Corporation CometLake-H GT2 [UHD Graphics] [8086:9bc4] (rev 05) (prog-if 00 [VGA controller]) Subsystem: Lenovo CometLake-H GT2 [UHD Graphics] [17aa:22c1] NVIDIA Corporation TU117GLM [Quadro T1000 Mobile] [10de:1fb9] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo TU117GLM [Quadro T1000 Mobile] [17aa:22c1] InstallationDate: Installed on 2020-10-05 (497 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: LENOVO 20THCT01WW ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-30-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to impish on 2021-10-14 (122 days ago) dmi.bios.date: 12/27/2021 dmi.bios.release: 1.21 dmi.bios.vendor: LENOVO dmi.bios.version: N2VET36W (1.21 ) dmi.board.asset.tag: Not Available dmi.board.name: 20THCT01WW dmi.board.vendor: LENOVO dmi.board.version: 0B98417 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.10 dmi.modalias: dmi:bvnLENOVO:bvrN2VET36W(1.21):bd12/27/2021:br1.21:efr1.10:svnLENOVO:pn20THCT01WW:pvrThinkPadP1Gen3:rvnLENOVO:rn20THCT01WW:rvr0B98417WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20TH_BU_Think_FM_ThinkPadP1Gen3: dmi.product.family: ThinkPad P1 Gen 3 dmi.product.name: 20THCT01WW dmi.product.sku: LENOVO_MT_20TH_BU_Think_FM_ThinkPad P1 Gen 3 dmi.product.version: ThinkPad P1 Gen 3 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1 version.libgl1-mesa-glx: libgl1-mesa-glx 21.2.6-0ubuntu0.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1.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-2build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu2 version.xserver-xorg-video-nouveau:
[Desktop-packages] [Bug 1960865] Re: System freeze when plugging USB-C monitor into a hybrid Intel/Nvidia laptop: [drm:__nv_drm_gem_nvkms_memory_prime_get_sg_table [nvidia_drm]] *ERROR* [nvidia-drm] [
@vanvugt - USB-C port seems to be wired to NVIDIA GPU on this laptop. I cannot use the monitor, if I switch to Intel GPU (`prime-select intel`) - it doesn't even identify that a monitor was connected. -- 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/1960865 Title: System freeze when plugging USB-C monitor into a hybrid Intel/Nvidia laptop: [drm:__nv_drm_gem_nvkms_memory_prime_get_sg_table [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x0100] Failed to get memory pages for NvKmsKapiMemory Status in Mutter: Unknown Status in linux package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Opinion Status in nvidia-graphics-drivers-470 package in Ubuntu: Confirmed Bug description: I recently upgraded my NVidia drivers on my ThinkPad P1 Gen 3. If I start Ubuntu on Wayland session and plug in my USB-C monitor the system reliably completely freeze. The freeze is also reproducible if the screen is plugged in during startup and trying to login into a Wayland session. Only Wayland session experiences a crash. The crash happens ONLY if the USB-C monitor is plugged in. USB-C monitor is also a USB3 hub. Hardware seems to work fine, as Windows shows no issues with the setup. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: xorg 1:7.7+22ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-30.33-generic 5.13.19 Uname: Linux 5.13.0-30-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 470.103.01 Thu Jan 6 12:10:04 UTC 2022 GCC version: gcc version 11.2.0 (Ubuntu 11.2.0-7ubuntu2) ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Feb 14 16:39:34 2022 DistUpgraded: 2021-10-14 18:36:11,564 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: impish DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GpuHangFrequency: Continuously GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Within the last few days GraphicsCard: Intel Corporation CometLake-H GT2 [UHD Graphics] [8086:9bc4] (rev 05) (prog-if 00 [VGA controller]) Subsystem: Lenovo CometLake-H GT2 [UHD Graphics] [17aa:22c1] NVIDIA Corporation TU117GLM [Quadro T1000 Mobile] [10de:1fb9] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo TU117GLM [Quadro T1000 Mobile] [17aa:22c1] InstallationDate: Installed on 2020-10-05 (497 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: LENOVO 20THCT01WW ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-30-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to impish on 2021-10-14 (122 days ago) dmi.bios.date: 12/27/2021 dmi.bios.release: 1.21 dmi.bios.vendor: LENOVO dmi.bios.version: N2VET36W (1.21 ) dmi.board.asset.tag: Not Available dmi.board.name: 20THCT01WW dmi.board.vendor: LENOVO dmi.board.version: 0B98417 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.10 dmi.modalias: dmi:bvnLENOVO:bvrN2VET36W(1.21):bd12/27/2021:br1.21:efr1.10:svnLENOVO:pn20THCT01WW:pvrThinkPadP1Gen3:rvnLENOVO:rn20THCT01WW:rvr0B98417WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20TH_BU_Think_FM_ThinkPadP1Gen3: dmi.product.family: ThinkPad P1 Gen 3 dmi.product.name: 20THCT01WW dmi.product.sku: LENOVO_MT_20TH_BU_Think_FM_ThinkPad P1 Gen 3 dmi.product.version: ThinkPad P1 Gen 3 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1 version.libgl1-mesa-glx: libgl1-mesa-glx 21.2.6-0ubuntu0.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1.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-2build1 version.xserver-xorg-video-intel:
[Desktop-packages] [Bug 1952947] Re: ubuntu-bug -w (using xprop) doesn't work under wayland
** Patch added: "apport-lp-1952947-impish.debdiff" https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1952947/+attachment/5561447/+files/apport-lp-1952947-impish.debdiff -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to x11-utils in Ubuntu. https://bugs.launchpad.net/bugs/1952947 Title: ubuntu-bug -w (using xprop) doesn't work under wayland Status in apport package in Ubuntu: Fix Released Status in x11-utils package in Ubuntu: Invalid Status in apport source package in Focal: Triaged Status in x11-utils source package in Focal: New Status in apport source package in Impish: Triaged Status in x11-utils source package in Impish: Invalid Status in apport source package in Jammy: Fix Released Status in x11-utils source package in Jammy: Invalid Bug description: [Impact] This bug makes it more difficult for Wayland users to report bugs with apport. When a Wayland user tries to use the -w,--window option, apport fails silently. We do not want users to face a high barrier to submitting bug reports. The patch for this bug adds a message explaining that the -w,--window option cannot be used on Wayland, and suggests a method for finding the window's PID instead. [Test Plan] * Log on to Ubuntu on Wayland. You can check that $XDG_SESSION_TYPE=="wayland" in your current session. * Open a terminal, and run `ubuntu-bug -w`. * Click on any other window, and observe that the apport UI will not respond. [Where problems could occur] The patch uses os.getenv to check that $XDG_SESSION_TYPE is set to 'wayland'. If either of these strings in the patch were wrong, or the environment variable was not used in the target release, the condition would likely never be true. [Original Description] I want to report a Bug about the application Studio Controls. As I did it already quite a few times, I run "ubuntu-bug -w", get a message that I can select the window of the app I want to report a bug about after closing this message. I close the message with a click on the appropriate button. I click on the window of the application "Studio Controls" that I want to report a bug about. Nothing happens. I wait for a few minutes. Still nothing happens. In the console where I started ubuntu-bug -w I see the following message: (apport-gtk:11537): Gdk-CRITICAL **: 20:06:41.384: gdk_wayland_window_set_dbus_properties_libgtk_only: assertion 'GDK_IS_WAYLAND_WINDOW (window)' failed What I expect: Usaully when I use this procedure, after a relatively short while a new message window pops up asking me if the bug should be reported and showing me the data that is sent to Launchpad. I tried other applications, too, same effect. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: apport 2.20.11-0ubuntu71 ProcVersionSignature: Ubuntu 5.13.0-21.21-lowlatency 5.13.18 Uname: Linux 5.13.0-21-lowlatency x86_64 ApportLog: ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Dec 1 20:01:23 2021 InstallationDate: Installed on 2020-04-12 (597 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitecture: all SourcePackage: apport UpgradeStatus: Upgraded to impish on 2021-11-14 (16 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1952947/+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 1952947] Re: ubuntu-bug -w (using xprop) doesn't work under wayland
** Description changed: + [Impact] + + This bug makes it more difficult for Wayland users to report bugs with + apport. When a Wayland user tries to use the -w,--window option, apport + fails silently. We do not want users to face a high barrier to + submitting bug reports. + + The patch for this bug adds a message explaining that the -w,--window + option cannot be used on Wayland, and suggests a method for finding the + window's PID instead. + + [Test Plan] + + * Log on to Ubuntu on Wayland. You can check that $XDG_SESSION_TYPE=="wayland" in your current session. + * Open a terminal, and run `ubuntu-bug -w`. + * Click on any other window, and observe that the apport UI will not respond. + + [Where problems could occur] + + The patch uses os.getenv to check that $XDG_SESSION_TYPE is set to + 'wayland'. If either of these strings in the patch were wrong, or the + environment variable was not used in the target release, the condition + would likely never be true. + + [Original Description] + I want to report a Bug about the application Studio Controls. As I did it already quite a few times, I run "ubuntu-bug -w", get a message that I can select the window of the app I want to report a bug about after closing this message. I close the message with a click on the appropriate button. I click on the window of the application "Studio Controls" that I want to report a bug about. Nothing happens. I wait for a few minutes. Still nothing happens. In the console where I started ubuntu-bug -w I see the following message: (apport-gtk:11537): Gdk-CRITICAL **: 20:06:41.384: gdk_wayland_window_set_dbus_properties_libgtk_only: assertion 'GDK_IS_WAYLAND_WINDOW (window)' failed - What I expect: Usaully when I use this procedure, after a relatively short while a new message window pops up asking me if the bug should be reported and showing me the data that is sent to Launchpad. I tried other applications, too, same effect. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: apport 2.20.11-0ubuntu71 ProcVersionSignature: Ubuntu 5.13.0-21.21-lowlatency 5.13.18 Uname: Linux 5.13.0-21-lowlatency x86_64 ApportLog: - + ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Dec 1 20:01:23 2021 InstallationDate: Installed on 2020-04-12 (597 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitecture: all SourcePackage: apport UpgradeStatus: Upgraded to impish on 2021-11-14 (16 days ago) ** Patch added: "apport-lp-1952947-focal.debdiff" https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1952947/+attachment/5561446/+files/apport-lp-1952947-focal.debdiff -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to x11-utils in Ubuntu. https://bugs.launchpad.net/bugs/1952947 Title: ubuntu-bug -w (using xprop) doesn't work under wayland Status in apport package in Ubuntu: Fix Released Status in x11-utils package in Ubuntu: Invalid Status in apport source package in Focal: Triaged Status in x11-utils source package in Focal: New Status in apport source package in Impish: Triaged Status in x11-utils source package in Impish: Invalid Status in apport source package in Jammy: Fix Released Status in x11-utils source package in Jammy: Invalid Bug description: [Impact] This bug makes it more difficult for Wayland users to report bugs with apport. When a Wayland user tries to use the -w,--window option, apport fails silently. We do not want users to face a high barrier to submitting bug reports. The patch for this bug adds a message explaining that the -w,--window option cannot be used on Wayland, and suggests a method for finding the window's PID instead. [Test Plan] * Log on to Ubuntu on Wayland. You can check that $XDG_SESSION_TYPE=="wayland" in your current session. * Open a terminal, and run `ubuntu-bug -w`. * Click on any other window, and observe that the apport UI will not respond. [Where problems could occur] The patch uses os.getenv to check that $XDG_SESSION_TYPE is set to 'wayland'. If either of these strings in the patch were wrong, or the environment variable was not used in the target release, the condition would likely never be true. [Original Description] I want to report a Bug about the application Studio Controls. As I did it already quite a few times, I run "ubuntu-bug -w", get a message that I can select the window of the app I want to report a bug about after closing this message. I close the message with a click on the appropriate button. I click on the window of the application "Studio Controls" that I want to report a bug about. Nothing happens. I wait for a few minutes. Still nothing happens. In the console where I started ubuntu-bug -w I see the
[Desktop-packages] [Bug 27867]
You can find the option here: https://bugs.edge.launchpad.net/firefox/+bug/27867 Thanks Nikhil https://getkeel.com/ -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/27867 Title: Background color is always white, top banner is never displayed in Firefox Status in Mozilla Firefox: Confirmed Status in firefox package in Ubuntu: Fix Released Bug description: Problem shows whatever the version of Epiphany (before and after today's upodate ie). Whatever the website I visit, the background colour is always white, and the logo/banner at the top of the page, is not displayed. I attached an example, showing Ubuntu bugzilla. No Ubuntu logo at the top, and no yellow background. http://bugzilla.gnome.org/show_bug.cgi?id=121118: http://bugzilla.gnome.org/show_bug.cgi?id=121118 To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/27867/+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 1960865] Re: System freeze when plugging USB-C monitor into a hybrid Intel/Nvidia laptop: [drm:__nv_drm_gem_nvkms_memory_prime_get_sg_table [nvidia_drm]] *ERROR* [nvidia-drm] [
> The strange thing to me is that Nvidia shouldn't be involved here. A USB-C > port is likely to be > wired to the Intel chips only. As a DisplayPort the USB-C is wired to the > Intel GPU. And gnome- > shell by default will use the integrated Intel GPU only for the desktop. FWIW, but I'm also experiencing the issue and I recall reading (I can't remember where) that the Thunderbolt port on the left end of my laptop is directly wired to the NVIDIA GPU, even when Optimus is enabled. This is not the case for other USB-C ports on my laptop. This seems to be verified by the fact that, on X11, attaching a display to the Thunderbolt port also makes it show up in the NVIDIA control panel, which shows a reduced view and feature set - because it is acting as secondary GPU. The main laptop display is also not shown there, as it is being handled by the Intel GPU. -- 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/1960865 Title: System freeze when plugging USB-C monitor into a hybrid Intel/Nvidia laptop: [drm:__nv_drm_gem_nvkms_memory_prime_get_sg_table [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x0100] Failed to get memory pages for NvKmsKapiMemory Status in Mutter: Unknown Status in linux package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Opinion Status in nvidia-graphics-drivers-470 package in Ubuntu: Confirmed Bug description: I recently upgraded my NVidia drivers on my ThinkPad P1 Gen 3. If I start Ubuntu on Wayland session and plug in my USB-C monitor the system reliably completely freeze. The freeze is also reproducible if the screen is plugged in during startup and trying to login into a Wayland session. Only Wayland session experiences a crash. The crash happens ONLY if the USB-C monitor is plugged in. USB-C monitor is also a USB3 hub. Hardware seems to work fine, as Windows shows no issues with the setup. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: xorg 1:7.7+22ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-30.33-generic 5.13.19 Uname: Linux 5.13.0-30-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 470.103.01 Thu Jan 6 12:10:04 UTC 2022 GCC version: gcc version 11.2.0 (Ubuntu 11.2.0-7ubuntu2) ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Feb 14 16:39:34 2022 DistUpgraded: 2021-10-14 18:36:11,564 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: impish DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GpuHangFrequency: Continuously GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Within the last few days GraphicsCard: Intel Corporation CometLake-H GT2 [UHD Graphics] [8086:9bc4] (rev 05) (prog-if 00 [VGA controller]) Subsystem: Lenovo CometLake-H GT2 [UHD Graphics] [17aa:22c1] NVIDIA Corporation TU117GLM [Quadro T1000 Mobile] [10de:1fb9] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo TU117GLM [Quadro T1000 Mobile] [17aa:22c1] InstallationDate: Installed on 2020-10-05 (497 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: LENOVO 20THCT01WW ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-30-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to impish on 2021-10-14 (122 days ago) dmi.bios.date: 12/27/2021 dmi.bios.release: 1.21 dmi.bios.vendor: LENOVO dmi.bios.version: N2VET36W (1.21 ) dmi.board.asset.tag: Not Available dmi.board.name: 20THCT01WW dmi.board.vendor: LENOVO dmi.board.version: 0B98417 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.10 dmi.modalias: dmi:bvnLENOVO:bvrN2VET36W(1.21):bd12/27/2021:br1.21:efr1.10:svnLENOVO:pn20THCT01WW:pvrThinkPadP1Gen3:rvnLENOVO:rn20THCT01WW:rvr0B98417WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20TH_BU_Think_FM_ThinkPadP1Gen3: dmi.product.family: ThinkPad P1 Gen 3
[Desktop-packages] [Bug 1961092] [NEW] Installing collectd pulls in the X.org stack
Public bug reported: On Ubuntu Server, "apt install collectd" pulls in huge parts of the X.org stack, which is generally undesirable. This was brought up in #ubuntu-server earlier. Workaround: use --no-install-recommends This seems to be due to collectd -> libnotify4 -> gnome-shell -> ... chain. This appears to have been made worse in an Ubuntu delta regarding gnome-shell. Debian's packaging still recommends notification-daemon which still pulls in quite a lot. It seems odd to me that a lib* package would recommend anything, since they tend to be leaves in the dependency tree apart from other lib* packages. Further it's difficult to avoid depending on a lib* package for optional functionality, so it ends up being inconvenient as demonstrated in this use case. Wouldn't it be better for the desktop environment to recommend something that can receive notifications in order for the dependency system to do the sensible thing by default, instead of using Recommends from the notification sending end? Then headless systems wouldn't end up pulling in a "head" via Recommends. So my suggestion is to drop the Recommends from libnotify4 altogether, including in Debian. >From a policy perspective, Recommends is defined as "The Recommends field should list packages that would be found together with this one in all but unusual installations". I think the headless case is a common installation, not an unusual one, so that disqualifies libnotify4 anyway. ** Affects: libnotify (Ubuntu) Importance: Medium Status: Triaged -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libnotify in Ubuntu. https://bugs.launchpad.net/bugs/1961092 Title: Installing collectd pulls in the X.org stack Status in libnotify package in Ubuntu: Triaged Bug description: On Ubuntu Server, "apt install collectd" pulls in huge parts of the X.org stack, which is generally undesirable. This was brought up in #ubuntu-server earlier. Workaround: use --no-install-recommends This seems to be due to collectd -> libnotify4 -> gnome-shell -> ... chain. This appears to have been made worse in an Ubuntu delta regarding gnome-shell. Debian's packaging still recommends notification-daemon which still pulls in quite a lot. It seems odd to me that a lib* package would recommend anything, since they tend to be leaves in the dependency tree apart from other lib* packages. Further it's difficult to avoid depending on a lib* package for optional functionality, so it ends up being inconvenient as demonstrated in this use case. Wouldn't it be better for the desktop environment to recommend something that can receive notifications in order for the dependency system to do the sensible thing by default, instead of using Recommends from the notification sending end? Then headless systems wouldn't end up pulling in a "head" via Recommends. So my suggestion is to drop the Recommends from libnotify4 altogether, including in Debian. From a policy perspective, Recommends is defined as "The Recommends field should list packages that would be found together with this one in all but unusual installations". I think the headless case is a common installation, not an unusual one, so that disqualifies libnotify4 anyway. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libnotify/+bug/1961092/+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 1715642] Re: display problem
Nima, I thought it best to ask than to close just in case you still saw a problem *related* in any way to the one that you saw while using the Trusty release. So, I'll close this as "Invalid" as the issue was never confirmed by another user and the Trusty release in now EOL. ** Changed in: xorg (Ubuntu) Status: Incomplete => Invalid -- 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/1715642 Title: display problem Status in xorg package in Ubuntu: Invalid Bug description: when I run a program through wine that needs to reduce the resolution to windows xp basic (800 x 600), wine program stopping unexpectedly and my desktop changes resolution so every time I need to restart my ubuntu. for more information pls check the photo I sent. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 4.4.0-93.116~14.04.1-generic 4.4.79 Uname: Linux 4.4.0-93-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 381.22 Thu May 4 00:55:03 PDT 2017 GCC version: gcc version 4.8.4 (Ubuntu 4.8.4-2ubuntu1~14.04.3) ApportVersion: 2.14.1-0ubuntu3.25 Architecture: amd64 CurrentDesktop: Unity Date: Thu Sep 7 17:33:30 2017 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: bbswitch, 0.7, 4.4.0-93-generic, x86_64: installed nvidia-381, 381.22, 4.4.0-93-generic, x86_64: installed GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:108d] NVIDIA Corporation GF108M [GeForce GT 540M] [10de:0df4] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:108d] InstallationDate: Installed on 2016-12-06 (274 days ago) InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release amd64 (20160217.1) MachineType: Micro-Star International Co., Ltd. GE620/GE620DX/FX620DX ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-93-generic root=UUID=f01602a0-6076-4436-9a4b-e05e01b6cdc5 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/26/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E16G5IMS V1.0F dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: MS-16G5 dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 10 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: To be filled by O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE16G5IMSV1.0F:bd05/26/2011:svnMicro-StarInternationalCo.,Ltd.:pnGE620/GE620DX/FX620DX:pvrTobefilledbyO.E.M.:rvnMicro-StarInternationalCo.,Ltd.:rnMS-16G5:rvrTobefilledbyO.E.M.:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrTobefilledbyO.E.M.: dmi.product.name: GE620/GE620DX/FX620DX dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Micro-Star International Co., Ltd. version.compiz: compiz 1:0.9.11.3+14.04.20160425-0ubuntu1 version.ia32-libs: ia32-libs 20090808ubuntu36 version.libdrm2: libdrm2 2.4.67-1ubuntu0.14.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri N/A version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A 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 N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Thu Sep 7 17:29:53 2017 xserver.configfile: /etc/X11/xorg.conf xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.3-1ubuntu2.3~trusty2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1715642/+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 1960924] Re: qpdf 10.6.1 not syncing?
Hi, thanks for reporting. >I'm noticing that qpdf-10.6.1 is not syncing from Debian The package has been automatically synced, but only to Jammy-proposed. It hasn't migrated to the release archive yet. This can be seen at the package overview page or https://bugs.launchpad.net/ubuntu/+source/qpdf/10.6.1-1. If everything is ok, packages from -proposed migrate to the release archive after a short while. Since this hasn't happened, I checked https://people.canonical.com/~ubuntu-archive/proposed- migration/jammy/update_excuses.html#qpdf to see why. Looks like it's mainly the autopkgtest for pikepdf/4.2.0+dfsg-1 marked as regressions holding it back. Didn't dig deeper into the test results, but I assume this is the issue you mention above. The Debian import freeze is in about a week, but any new releases uploaded to Debian up to that point will be imported. I.e. "10.6.2 in the next day or two" should be synced automatically. It is possible to request package syncs after, but it needs a Freeze Exception Request (https://wiki.ubuntu.com/FreezeExceptionProcess) Hope this helps :) ** Tags added: jammy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to qpdf in Ubuntu. https://bugs.launchpad.net/bugs/1960924 Title: qpdf 10.6.1 not syncing? Status in qpdf package in Ubuntu: New Bug description: I'm noticing that qpdf-10.6.1 is not syncing from Debian even though, as far as I can see, automatic sync freeze has not yet happened. There are some major changes in 10.6 that I would really like to get into Ubuntu because they include transitional code to help users migrate to qpdf 11. Is there something that needs to happen for this to sync? I don't want to miss the window. At this time, there are test failures in pikepdf because of a bug fix to qpdf in transcoding. We have determined that these test failures don't indicate a serious problem with either qpdf or pikepdf -- they are basically that pikepdf had some tests that were depending on incorrect qpdf functionality. For details, see https://github.com/pikepdf/pikepdf/issues/303 The pikepdf author is aware of the upcoming Ubuntu 22.04 freeze and is trying to get a fix in in time, but I'm hoping we can avoid getting into a situation where we miss the bus. There's a chance I might release 10.6.2 to fix one other minor transcoding issue, but I don't consider the issue to be important enough to justify a release. But if the pikepdf author wants a release to simplify his testing, I will do it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qpdf/+bug/1960924/+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 1960014] Re: Missing Dutch language interface for LibreOffice in Snap installation
[quote]Adolfo Jayme (fitojb) wrote 6 minutes ago: #2 There is no need for that; LibreOffice is in the Debian (and Ubuntu) archives and will remain there[/quote] That may be, but how many inexperienced users of Linux know that when the Software library offers only the snap packs for some app, you can still also get the normal ones? -- 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/1960014 Title: Missing Dutch language interface for LibreOffice in Snap installation Status in libreoffice package in Ubuntu: Triaged Bug description: Hi. My native language is Dutch, I live in the Netherlands, but when I get the LibreOffice packages from Ubuntu Linux (Snap), I can choose from only 15 interface languages, and Dutch is not one of them. Even though Dutch is available as interface language on the generic LibreOffice that can be downloaded from the LibreOffice website, but that isn’t automatically updated. For Dutch people who aren’t very good at English, or are good at it but still want the Dutch interface language, this is a bit of a problem, especially because it isn’t at all obvious how you can download & install a separate language pack. This topic in Ask LibreOffice is about the same problem (warning: text in Dutch): https://ask.libreoffice.org/t/kan-de-user-interface-taal- niet-veranderen/73301/5 Can this be fixed? Currently on: Version: 7.2.5.2.0+ / LibreOffice Community Build ID: 711f8d38e9451cd2fd39b6963d2a3fc166f04cb1 CPU threads: 4; OS: Linux 5.4; UI render: default; VCL: gtk3 Locale: nl-NL (nl_NL.UTF-8); UI: en-US Calc: threaded To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1960014/+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 1960014] Re: Missing Dutch language interface for LibreOffice in Snap installation
There is no need for that; LibreOffice is in the Debian (and Ubuntu) archives and will remain there -- 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/1960014 Title: Missing Dutch language interface for LibreOffice in Snap installation Status in libreoffice package in Ubuntu: Triaged Bug description: Hi. My native language is Dutch, I live in the Netherlands, but when I get the LibreOffice packages from Ubuntu Linux (Snap), I can choose from only 15 interface languages, and Dutch is not one of them. Even though Dutch is available as interface language on the generic LibreOffice that can be downloaded from the LibreOffice website, but that isn’t automatically updated. For Dutch people who aren’t very good at English, or are good at it but still want the Dutch interface language, this is a bit of a problem, especially because it isn’t at all obvious how you can download & install a separate language pack. This topic in Ask LibreOffice is about the same problem (warning: text in Dutch): https://ask.libreoffice.org/t/kan-de-user-interface-taal- niet-veranderen/73301/5 Can this be fixed? Currently on: Version: 7.2.5.2.0+ / LibreOffice Community Build ID: 711f8d38e9451cd2fd39b6963d2a3fc166f04cb1 CPU threads: 4; OS: Linux 5.4; UI render: default; VCL: gtk3 Locale: nl-NL (nl_NL.UTF-8); UI: en-US Calc: threaded To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1960014/+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 1952107] Re: Google Contacts API Deprecated
Upgrade to evolution 3.36.5-0ubuntu2 on Ubuntu 20.04.03 (focal) did not fix the bug for me either. I am wondering if anyone has gotten it to work on focal. To fix the bug on Ubuntu 18.04 (bionic), I had to compile the source (master branch), largely following the instructions at https://wiki.gnome.org/Apps/Evolution/Building, but I also had to build libcmark and turn off introspection, vala, and weather to get it to build. I couldn't use the flatpak build because the machine is a laptop and very limited on disk space. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1952107 Title: Google Contacts API Deprecated Status in evolution-data-server: Unknown Status in evolution package in Ubuntu: Fix Released Status in evolution-data-server package in Ubuntu: Fix Released Status in evolution source package in Focal: Fix Committed Status in evolution-data-server source package in Focal: Fix Committed Status in evolution source package in Impish: Fix Released Status in evolution-data-server source package in Impish: Fix Released Bug description: * Impact The google contacts integration with the GNOME component will stop working since it relies on an API which is going to be shutdown * Testcase - use evolution - add a google account - go the contacts section The contacts stored on the google account should be listed, no error should be displayed * Regression potential The patch changes the google contact backend so any potential issue is likely to be with contacts integration. I opened Evolution today and a red banner appeared on top with the following message: > Failed to connect address book “ : Contacts” > Invalid request URI or header, or unsupported nonstandard parameter: Contacts API is being deprecated. Migrate to People API to retain programmatic access to Google Contacts. See https://developers.google.com/people/contacts-api-migration. I found the upstream bug report for this[0], which references the commit[1] that fixes it. However, that commit is in release 3.42.0, whereas Ubuntu 21.10 currently has 3.40.4-1. Is it possible to backport this commit so that Evolution will continue to work properly? [0]: https://gitlab.gnome.org/GNOME/evolution/-/issues/1658 [1]: https://gitlab.gnome.org/GNOME/evolution-data-server/-/commit/d63a1ce3921a6a6c573a6a To manage notifications about this bug go to: https://bugs.launchpad.net/evolution-data-server/+bug/1952107/+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 1181666] Re: gnome-shell randomly blocks mouse clicks from working in app windows
I face the same issue that Legendary Nacar has described in his comment #160. The workaround is to use Alt+F2 and type single letter r in the textbox and hit enter as described by Axel Kittenberger in his comment #16. -- 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/1181666 Title: gnome-shell randomly blocks mouse clicks from working in app windows Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: Under GNOME 3, the use of the mouse-click stops occasionally, though I can still move the mouse around and can still click on items in the Activities screen and the top-bar. I can use alt-tab to cycle windows and can still type into already- active textboxes in windows, but I cannot click within the windows, and the mouse is not picked up at all by the windows. I can open the alt-f2 "run command" dialogue, but cannot type into it. The workaround I'm using is to open terminal (ctrl-alt-T) and run "gnome-shell -r", and restarting that command every time I have the problem again. Please ask if there's anything I forgot to mention. ADDITIONAL: The error tends to happen randomly, but it seems to happen upon opening a new window, changing windows, closing windows, or opening the activities pane (whether a change of window is thus instigated or not) ADDITIONAL 2: (sorry, it's early) The other workaround is to log out and to log in again, but that is also less than ideal ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: gnome-shell 3.6.3.1-0ubuntu6 ProcVersionSignature: Ubuntu 3.8.0-22.33-generic 3.8.11 Uname: Linux 3.8.0-22-generic x86_64 ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 Date: Sun May 19 07:02:18 2013 DisplayManager: gdm GsettingsChanges: b'org.gnome.desktop.interface' b'clock-show-date' b'true' b'org.gnome.desktop.interface' b'clock-show-seconds' b'true' b'org.gnome.desktop.interface' b'document-font-name' b"'Sans 10'" b'org.gnome.desktop.interface' b'font-name' b"'Cantarell 10'" b'org.gnome.desktop.interface' b'monospace-font-name' b"'Ubuntu Mono 12'" InstallationDate: Installed on 2013-05-04 (14 days ago) InstallationMedia: Ubuntu-GNOME 13.04 "Raring Ringtail" - Release amd64 (20130424) MarkForUpload: True ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1181666/+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 402892] Re: Mouse cursor gets stuck in "drag and drop" mode
I have a similar problem on Linux Mint Cinnamon 20.3: https://bugs.launchpad.net/ubuntu/+bug/1961034 Video: https://emalm.com/?v=DsBSK Is anyone working on fixing this bug? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/402892 Title: Mouse cursor gets stuck in "drag and drop" mode Status in OpenShot Video Editor: New Status in X.Org X server: New Status in chromium-browser package in Ubuntu: Confirmed Status in firefox package in Ubuntu: Confirmed Status in rapidsvn package in Ubuntu: Confirmed Bug description: Binary package hint: rapidsvn When clicking on the Bookmark root or on one of the bookmarks below the mouse cursor gets stuck in "drag n drop" mode, blocking all keyboard entry and also mouse clicks for the the whole GUI (systemwide). Unfortunately I cannot provide any debug or other information, as I have to reboot everytime. I am running Ubuntu 9.04 with compiz enabled. Many thanks in advance for your help with this problem, /nxT To manage notifications about this bug go to: https://bugs.launchpad.net/openshot/+bug/402892/+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 1861262] Re: Add message/rfc822 to thunderbird.desktop
Thank you for updating the .desktop file. The issue is more hairy than it seems at first glance. E.g. https://debbugs.gnu.org/ sends "Content-disposition" header with ".mbox" suffix when a single comment in mbox format is requested (to reply to particular message). Thunderbird believes that a suitable action is to compose a new message with downloaded file as an attachment. There is no command line option to force thunderbird to open a file as namely mail message. The position of developers is that such file must have ".eml" extension otherwise it is not a message. See https://bugzilla.mozilla.org/show_bug.cgi?id=1755454 for details (bug title has been changed to fix a loosely related issue). ** Bug watch added: Mozilla Bugzilla #1755454 https://bugzilla.mozilla.org/show_bug.cgi?id=1755454 -- 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/1861262 Title: Add message/rfc822 to thunderbird.desktop Status in thunderbird package in Ubuntu: Fix Released Bug description: Please add message/rfc822 to thunderbird.desktop: -MimeType=x-scheme-handler/mailto;application/x-xpinstall; +MimeType=x-scheme-handler/mailto;application/x-xpinstall;message/rfc822; It will allow to open *.eml files. I attach an example eml file. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1861262/+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 1959596] Re: Applications end up in session scope, rather than per .desktop scope
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-shell (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1959596 Title: Applications end up in session scope, rather than per .desktop scope Status in gnome-shell package in Ubuntu: Confirmed Status in gnome-shell source package in Jammy: Confirmed Bug description: During systemd-oomd install in jammy (w/ GNOME session) today, I noticed that applications ended up in the wrong control group - in the session scope, rather than per .desktop one: Control group /: -.slice ├─user.slice │ └─user-1000.slice │ ├─user@1000.service │ │ ├─session.slice │ │ │ ├─xdg-document-portal.service │ │ │ │ ├─4514 /usr/libexec/xdg-document-portal │ │ │ │ └─4556 fusermount3 -o rw,nosuid,nodev,fsname=portal,auto_unmount,subt… │ │ │ ├─xdg-desktop-portal.service │ │ │ │ └─6186 /usr/libexec/xdg-desktop-portal │ │ │ ├─pipewire-pulse.service │ │ │ │ └─4473 /usr/bin/pipewire-pulse │ │ │ ├─wireplumber.service │ │ │ │ └─4472 /usr/bin/wireplumber │ │ │ └─pipewire.service │ │ │ └─4461 /usr/bin/pipewire │ │ ├─background.slice │ │ │ └─tracker-miner-fs-3.service │ │ │ └─4940 /usr/libexec/tracker-miner-fs-3 │ │ ├─user.slice │ │ │ └─podman-pause-6313308764925138924.scope │ │ │ └─4602 /usr/bin/podman │ │ ├─app.slice │ │ │ ├─gvfs-goa-volume-monitor.service │ │ │ │ └─5417 /usr/libexec/gvfs-goa-volume-monitor │ │ │ ├─snap.syncthing.syncthing.908e68e0-47a9-47b6-80b0-a6a3afdd4f24.scope │ │ │ │ ├─4470 /snap/syncthing/501/syncthing │ │ │ │ └─5510 /snap/syncthing/501/syncthing │ │ │ ├─xdg-permission-store.service │ │ │ │ └─4527 /usr/libexec/xdg-permission-store │ │ │ ├─snap.spotify.spotify.b3c54917-38c3-473b-8774-b90e1d30a8c3.scope │ │ │ │ ├─198100 /snap/spotify/57/usr/share/spotify/spotify │ │ │ │ ├─198169 /snap/spotify/57/usr/share/spotify/spotify --type=zygote --n… │ │ │ │ ├─198170 /snap/spotify/57/usr/share/spotify/spotify --type=zygote --n… │ │ │ │ ├─198188 /snap/spotify/57/usr/share/spotify/spotify --type=gpu-proces… │ │ │ │ ├─198205 /snap/spotify/57/usr/share/spotify/spotify --type=utility --… │ │ │ │ ├─198208 /snap/spotify/57/usr/share/spotify/spotify --type=utility --… │ │ │ │ └─198235 /snap/spotify/57/usr/share/spotify/spotify --type=renderer -… │ │ │ ├─evolution-calendar-factory.service │ │ │ │ └─6018 /usr/libexec/evolution-calendar-factory │ │ │ ├─xdg-desktop-portal-gnome.service │ │ │ │ └─6193 /usr/libexec/xdg-desktop-portal-gnome │ │ │ ├─dconf.service │ │ │ │ └─5837 /usr/libexec/dconf-service │ │ │ ├─gvfs-daemon.service │ │ │ │ ├─ 4515 /usr/libexec/gvfsd │ │ │ │ ├─ 4531 /usr/libexec/gvfsd-fuse /run/user/1000/gvfs -f │ │ │ │ ├─ 8485 /usr/libexec/gvfsd-http --spawner :1.4 /org/gtk/gvfs/exec_spa… │ │ │ │ ├─29658 /usr/libexec/gvfsd-trash --spawner :1.4 /org/gtk/gvfs/exec_sp… │ │ │ │ └─29990 /usr/libexec/gvfsd-burn --spawner :1.4 /org/gtk/gvfs/exec_spa… │ │ │ ├─evolution-source-registry.service │ │ │ │ └─5820 /usr/libexec/evolution-source-registry │ │ │ ├─gvfs-udisks2-volume-monitor.service │ │ │ │ └─5202 /usr/libexec/gvfs-udisks2-volume-monitor │ │ │ ├─app-org.gnome.Terminal.slice │ │ │ │ ├─gnome-terminal-server.service │ │ │ │ │ └─8577 /usr/libexec/gnome-terminal-server │ │ │ │ └─vte-spawn-e31cc856-c6d7-4247-935c-6d28706ab542.scope │ │ │ │ ├─ 8595 -bash │ │ │ │ ├─ 8617 tmux -u -2 -f /usr/share/byobu/profiles/tmuxrc new-session… │ │ │ │ ├─ 8648 tmux -u -2 -f /usr/share/byobu/profiles/tmuxrc new-session… │ │ │ │ ├─ 8655 /bin/bash │ │ │ │ ├─ 8749 journalctl -f │ │ │ │ ├─ 25429 /bin/bash │ │ │ │ ├─179012 /bin/bash │ │ │ │ ├─208170 systemd-cgls │ │ │ │ └─208171 xclip │ │ │ ├─gpg-agent.service │ │ │ │ ├─29718 /usr/bin/gpg-agent --supervised │ │ │ │ └─70766 scdaemon --multi-server │ │ │ ├─gvfs-gphoto2-volume-monitor.service │ │ │ │ └─5403 /usr/libexec/gvfs-gphoto2-volume-monitor │ │ │ ├─xdg-desktop-portal-gtk.service │ │ │ │ └─7143 /usr/libexec/xdg-desktop-portal-gtk │ │ │ ├─obex.service │ │ │ │ └─63426 /usr/lib/bluetooth/obexd │ │ │ ├─at-spi-dbus-bus.service │ │ │ │ ├─5443 /usr/libexec/at-spi-bus-launcher │ │ │ │ ├─5457 /usr/bin/dbus-daemon --config-file=/usr/share/defaults/at-spi2… │ │ │ │ └─5886 /usr/libexec/at-spi2-registryd --use-gnome-session │ │ │ ├─gvfs-metadata.service │ │ │ │ └─5931 /usr/libexec/gvfsd-metadata │ │ │ ├─dbus.service │ │ │ │ ├─ 4508 /usr/bin/dbus-daemon --session --address=systemd: --nofork --… │ │ │ │ ├─ 5431 /usr/libexec/goa-daemon │ │ │ │ ├─ 5513 /usr/libexec/goa-identity-service │ │ │ │
[Desktop-packages] [Bug 1959596] Re: Applications end up in session scope, rather than per .desktop scope
Possibly related: the user graphical-session.target unit is never reached in Jammy. From Impish and Jammy we have for `systemctl --user is-active graphical-session.target`: - Impish clean install: active - Jammy clean install: inactive Note that this means that the .service units under /usr/lib/systemd/user/graphical-session-pre.target.wants/ are not being executed. These are: gnome-keyring-ssh.service gnome-keyring.service session-migration.service ssh-agent.service (Initially reported in https://bugs.launchpad.net/ubuntu/+source/gnome- session/+bug/1743366) -- 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/1959596 Title: Applications end up in session scope, rather than per .desktop scope Status in gnome-shell package in Ubuntu: Confirmed Status in gnome-shell source package in Jammy: Confirmed Bug description: During systemd-oomd install in jammy (w/ GNOME session) today, I noticed that applications ended up in the wrong control group - in the session scope, rather than per .desktop one: Control group /: -.slice ├─user.slice │ └─user-1000.slice │ ├─user@1000.service │ │ ├─session.slice │ │ │ ├─xdg-document-portal.service │ │ │ │ ├─4514 /usr/libexec/xdg-document-portal │ │ │ │ └─4556 fusermount3 -o rw,nosuid,nodev,fsname=portal,auto_unmount,subt… │ │ │ ├─xdg-desktop-portal.service │ │ │ │ └─6186 /usr/libexec/xdg-desktop-portal │ │ │ ├─pipewire-pulse.service │ │ │ │ └─4473 /usr/bin/pipewire-pulse │ │ │ ├─wireplumber.service │ │ │ │ └─4472 /usr/bin/wireplumber │ │ │ └─pipewire.service │ │ │ └─4461 /usr/bin/pipewire │ │ ├─background.slice │ │ │ └─tracker-miner-fs-3.service │ │ │ └─4940 /usr/libexec/tracker-miner-fs-3 │ │ ├─user.slice │ │ │ └─podman-pause-6313308764925138924.scope │ │ │ └─4602 /usr/bin/podman │ │ ├─app.slice │ │ │ ├─gvfs-goa-volume-monitor.service │ │ │ │ └─5417 /usr/libexec/gvfs-goa-volume-monitor │ │ │ ├─snap.syncthing.syncthing.908e68e0-47a9-47b6-80b0-a6a3afdd4f24.scope │ │ │ │ ├─4470 /snap/syncthing/501/syncthing │ │ │ │ └─5510 /snap/syncthing/501/syncthing │ │ │ ├─xdg-permission-store.service │ │ │ │ └─4527 /usr/libexec/xdg-permission-store │ │ │ ├─snap.spotify.spotify.b3c54917-38c3-473b-8774-b90e1d30a8c3.scope │ │ │ │ ├─198100 /snap/spotify/57/usr/share/spotify/spotify │ │ │ │ ├─198169 /snap/spotify/57/usr/share/spotify/spotify --type=zygote --n… │ │ │ │ ├─198170 /snap/spotify/57/usr/share/spotify/spotify --type=zygote --n… │ │ │ │ ├─198188 /snap/spotify/57/usr/share/spotify/spotify --type=gpu-proces… │ │ │ │ ├─198205 /snap/spotify/57/usr/share/spotify/spotify --type=utility --… │ │ │ │ ├─198208 /snap/spotify/57/usr/share/spotify/spotify --type=utility --… │ │ │ │ └─198235 /snap/spotify/57/usr/share/spotify/spotify --type=renderer -… │ │ │ ├─evolution-calendar-factory.service │ │ │ │ └─6018 /usr/libexec/evolution-calendar-factory │ │ │ ├─xdg-desktop-portal-gnome.service │ │ │ │ └─6193 /usr/libexec/xdg-desktop-portal-gnome │ │ │ ├─dconf.service │ │ │ │ └─5837 /usr/libexec/dconf-service │ │ │ ├─gvfs-daemon.service │ │ │ │ ├─ 4515 /usr/libexec/gvfsd │ │ │ │ ├─ 4531 /usr/libexec/gvfsd-fuse /run/user/1000/gvfs -f │ │ │ │ ├─ 8485 /usr/libexec/gvfsd-http --spawner :1.4 /org/gtk/gvfs/exec_spa… │ │ │ │ ├─29658 /usr/libexec/gvfsd-trash --spawner :1.4 /org/gtk/gvfs/exec_sp… │ │ │ │ └─29990 /usr/libexec/gvfsd-burn --spawner :1.4 /org/gtk/gvfs/exec_spa… │ │ │ ├─evolution-source-registry.service │ │ │ │ └─5820 /usr/libexec/evolution-source-registry │ │ │ ├─gvfs-udisks2-volume-monitor.service │ │ │ │ └─5202 /usr/libexec/gvfs-udisks2-volume-monitor │ │ │ ├─app-org.gnome.Terminal.slice │ │ │ │ ├─gnome-terminal-server.service │ │ │ │ │ └─8577 /usr/libexec/gnome-terminal-server │ │ │ │ └─vte-spawn-e31cc856-c6d7-4247-935c-6d28706ab542.scope │ │ │ │ ├─ 8595 -bash │ │ │ │ ├─ 8617 tmux -u -2 -f /usr/share/byobu/profiles/tmuxrc new-session… │ │ │ │ ├─ 8648 tmux -u -2 -f /usr/share/byobu/profiles/tmuxrc new-session… │ │ │ │ ├─ 8655 /bin/bash │ │ │ │ ├─ 8749 journalctl -f │ │ │ │ ├─ 25429 /bin/bash │ │ │ │ ├─179012 /bin/bash │ │ │ │ ├─208170 systemd-cgls │ │ │ │ └─208171 xclip │ │ │ ├─gpg-agent.service │ │ │ │ ├─29718 /usr/bin/gpg-agent --supervised │ │ │ │ └─70766 scdaemon --multi-server │ │ │ ├─gvfs-gphoto2-volume-monitor.service │ │ │ │ └─5403 /usr/libexec/gvfs-gphoto2-volume-monitor │ │ │ ├─xdg-desktop-portal-gtk.service │ │ │ │ └─7143 /usr/libexec/xdg-desktop-portal-gtk │ │ │ ├─obex.service │ │ │ │ └─63426 /usr/lib/bluetooth/obexd │ │ │ ├─at-spi-dbus-bus.service │ │ │ │ ├─5443 /usr/libexec/at-spi-bus-launcher │ │ │ │
[Desktop-packages] [Bug 1697957] Re: Impress crashes when using smooth fade transition on Gnome based desktop environment
I ran into this problem today with LO Version: 6.4.7.2. (Both the crashes and the jagged, flickering transitions.) Is it possible that this was never fixed? -- 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/1697957 Title: Impress crashes when using smooth fade transition on Gnome based desktop environment Status in libreoffice package in Ubuntu: Expired Bug description: Please note that this bug only affects Gnome based desktop environments such as Unity, Mate and Gnome itself, and at version 17.04 only. It does NOT affect Kubuntu, Xubuntu or Lubuntu, or earlier versions. Create a slide show of four or more slides. Set all slides to use the smooth Fade transition, and to automatically change after approx' 10 seconds. Libreoffice will crash after the second or third transition. Starting the Impress application from the terminal gives the following error messages:- javaldx: Could not find a Java Runtime Environment! Warning: failed to read path from javaldx (soffice:4497): Gtk-WARNING **: Allocating size to OOoFixed 0x55e904d49e40 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Application Error Please note that all of the above versions (17.04) were run from live USB or live DVD, not from a full install. Turning hardware acceleration on/off has no effect. Turning presenter console on/off has no effect. This bug is repeatable on a Dell Studio 15 laptop which has Intel Core2Duo cpu, and ATI mobile radeon HD4530/4570/545v graphics. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: libreoffice (not installed) ProcVersionSignature: Ubuntu 4.4.0-79.100-generic 4.4.67 Uname: Linux 4.4.0-79-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64 CurrentDesktop: Unity Date: Wed Jun 14 16:10:42 2017 InstallationDate: Installed on 2016-01-08 (523 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) SourcePackage: libreoffice UpgradeStatus: Upgraded to xenial on 2016-07-29 (319 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1697957/+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 1961042] Re: gnome-shell crashed with SIGSEGV in meta_context_run_main_loop()
*** This bug is a duplicate of bug 1961041 *** https://bugs.launchpad.net/bugs/1961041 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1961041, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1961042/+attachment/5561330/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1961042/+attachment/5561332/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1961042/+attachment/5561337/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1961042/+attachment/5561338/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1961042/+attachment/5561339/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1961042/+attachment/5561341/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1961042/+attachment/5561342/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1961041 ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- 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/1961042 Title: gnome-shell crashed with SIGSEGV in meta_context_run_main_loop() Status in gnome-shell package in Ubuntu: New Bug description: Happened after opening the Ubuntu Pro popup. Not sure if it's related though. ProblemType: Crash DistroRelease: Ubuntu 22.04 Package: gnome-shell 41.3-1ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Uname: Linux 5.15.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu76 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Feb 16 11:06:55 2022 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2022-02-03 (13 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220202) ProcCmdline: /usr/bin/gnome-shell RelatedPackageVersions: mutter-common 41.3-1ubuntu5 SegvAnalysis: Segfault happened at: 0x7f0dc0d9a808 <__pthread_kill_internal+24>: mov 0x28,%eax PC (0x7f0dc0d9a808) ok source "0x28" (0x0028) not located in a known VMA region (needed readable region)! destination "%eax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: gnome-shell StacktraceTop: meta_context_run_main_loop () from /lib/x86_64-linux-gnu/libmutter-9.so.0 g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 meta_context_run_main_loop () from /lib/x86_64-linux-gnu/libmutter-9.so.0 Title: gnome-shell crashed with SIGSEGV in meta_context_run_main_loop() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1961042/+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 1960898] Re: Wayland sessions crash with Gjs:ERROR:../gi/interface.cpp:101:bool InterfacePrototype::has_instance_impl(JSContext*, const JS::CallArgs&): assertion failed: (args[
May importante. I use Wireguard and have a mounted sft there. Since my update to 21.10 it do not work anymore. Goal here is to have imediately after login a mounted drive. I never found a recommended way how to automount a network drive in Ubuntu. $HOME/.local/share/systemd/user/ contain a .mount and .automout file with folowing content. .mount ___ [Unit] Description=Speicher einbinden [Install] WantedBy=multi-user.target [Mount] What=USER@SERVER-IP:/ Where=/media/USER/Mountpoint Type=fuse.sshfs Options=_netdev,allow_other,IdentityFile=/home/USER/.ssh/SSH-FILE,reconnect,ServerAliveInterval=15,ServerAliveCountMax=10,uid=1000,gid=1000 TimeoutSec=60 .automount ___ [Unit] Description=Auto Speicher einbinden [Install] WantedBy=multi-user.target [Automount] Where=/media/USER/sieben -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1960898 Title: Wayland sessions crash with Gjs:ERROR:../gi/interface.cpp:101:bool InterfacePrototype::has_instance_impl(JSContext*, const JS::CallArgs&): assertion failed: (args[0].isObject()) from ubuntu- d...@ubuntu.com/locations.js:1108 Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: New Bug description: Hardware: https://linux-hardware.org/?probe=1055dc7082 Worked without Problem in 21.04 Had some flicker and problem with the left dock in 21.10 not working since updating to 22.04 now I'm running xorg. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 41.3-1ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Uname: Linux 5.15.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu76 Architecture: amd64 CasperMD5CheckMismatches: ./pool/restricted/n/nvidia-graphics-drivers-450/libnvidia-gl-450_450.102.04-0ubuntu2_amd64.deb CasperMD5CheckResult: fail CurrentDesktop: ubuntu:GNOME Date: Tue Feb 15 08:07:04 2022 DisplayManager: gdm3 InstallationDate: Installed on 2021-08-15 (183 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) RelatedPackageVersions: mutter-common 41.3-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to jammy on 2022-02-14 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1960898/+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 1751954] Re: Bluetooth and Wi-Fi items in Power are worded ambiguously
The fix is in gnome-control-center version 41 and later. So that's in Ubuntu 22.04 only right now. And in fact it was only released to Ubuntu 22.04 in November/December. This doesn't appear to be a severe bug. I'm not sure if such a design change is appropriate for some future 20.04.x release. If you think it is then you can add tag 'rls-ff-incoming'. ** Changed in: gnome-control-center (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1751954 Title: Bluetooth and Wi-Fi items in Power are worded ambiguously Status in gnome-control-center: Fix Released Status in gnome-control-center package in Ubuntu: Fix Released Bug description: In the gnome-control-center, in the power section, there is a checkbox that says: Wi-Fi Turn off Wi-Fi to save power I have it checked, so after a few minutes without using my computer, the wi-fi is disabled. I want to keep my wi-fi working, so I unchecked this box, but it disables my wi-fi immediately. So, it's obviously wrong to disable the wi-fi when I click that checkbox. And I don't seem to have a way to keep my wi-fi enabled. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-control-center 1:3.26.2-0ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Feb 26 18:27:16 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2017-10-04 (145 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20170930) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=eo SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: Upgraded to bionic on 2017-11-17 (101 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1751954/+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 1960898] Re: Wayland sessions crash with Gjs:ERROR:../gi/interface.cpp:101:bool InterfacePrototype::has_instance_impl(JSContext*, const JS::CallArgs&): assertion failed: (args[
1.) Did first test from Marco trevisan 2.) after that I run 'gsettings set org.gnome.shell.extensions.dash-to-dock show-mounts true' 3.) than restarted to Wayland 4.) got back to xorg exported the data with journalctl -b0 >Journal.txt 5.) this file is around 3MB in size so I compacted it to journal.tar.xz ** Attachment added: "journal.tar.xz" https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1960898/+attachment/5561316/+files/journal.tar.xz -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1960898 Title: Wayland sessions crash with Gjs:ERROR:../gi/interface.cpp:101:bool InterfacePrototype::has_instance_impl(JSContext*, const JS::CallArgs&): assertion failed: (args[0].isObject()) from ubuntu- d...@ubuntu.com/locations.js:1108 Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: New Bug description: Hardware: https://linux-hardware.org/?probe=1055dc7082 Worked without Problem in 21.04 Had some flicker and problem with the left dock in 21.10 not working since updating to 22.04 now I'm running xorg. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 41.3-1ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Uname: Linux 5.15.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu76 Architecture: amd64 CasperMD5CheckMismatches: ./pool/restricted/n/nvidia-graphics-drivers-450/libnvidia-gl-450_450.102.04-0ubuntu2_amd64.deb CasperMD5CheckResult: fail CurrentDesktop: ubuntu:GNOME Date: Tue Feb 15 08:07:04 2022 DisplayManager: gdm3 InstallationDate: Installed on 2021-08-15 (183 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) RelatedPackageVersions: mutter-common 41.3-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to jammy on 2022-02-14 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1960898/+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 1751954] Re: Bluetooth and Wi-Fi items in Power are worded ambiguously
It says above fix released in August, however I still have the bad wording and it has caught me out today. I'm running Ubuntu 20.04.03 gnome 3.36.8. Why has the fix not reached me yet please? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1751954 Title: Bluetooth and Wi-Fi items in Power are worded ambiguously Status in gnome-control-center: Fix Released Status in gnome-control-center package in Ubuntu: Fix Committed Bug description: In the gnome-control-center, in the power section, there is a checkbox that says: Wi-Fi Turn off Wi-Fi to save power I have it checked, so after a few minutes without using my computer, the wi-fi is disabled. I want to keep my wi-fi working, so I unchecked this box, but it disables my wi-fi immediately. So, it's obviously wrong to disable the wi-fi when I click that checkbox. And I don't seem to have a way to keep my wi-fi enabled. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-control-center 1:3.26.2-0ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Feb 26 18:27:16 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2017-10-04 (145 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20170930) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=eo SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: Upgraded to bionic on 2017-11-17 (101 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1751954/+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 1942789] Re: On-demand and RTD3 need to be separated
** Changed in: nvidia-prime (Ubuntu Hirsute) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1942789 Title: On-demand and RTD3 need to be separated Status in OEM Priority Project: Confirmed Status in nvidia-prime package in Ubuntu: Fix Released Status in nvidia-prime source package in Focal: Incomplete Status in nvidia-prime source package in Hirsute: Invalid Bug description: [Steps to reproduce] 1. Install 20.04.3 with "Third-party packages" on a system which containing a RTD3 supported nvidia card. 2. After the installation, press enter to reboot system 3. prime-select query [Expected result] on-demand [Actual result] performance --- It's because ubiquity launches `ubuntu-drivers install --packages-list ...` in live system but install each package to target storage. When installing nvidia-prime, the preinst set "on" to "/etc/prime- discrete" which will be referred by gpu-manager. The gpu-manager will set to performance mode. After confirming with Alberto on Mattermost, since we don't have a nvidia driver which lower than 450 version since focal. I think we are ok to switch to on-demand mode. --- [Impact] * Ubuntu will set GPU mode to performance as default which may use more power * User can't use GPU for other purpose (eg: deep-learning) if RTD3 is not supported * According to Nvidia README, the RTD3 doesn't support on non-laptop machine [Test Plan] * Install Ubuntu, and then execute 'ubuntu-drivers install' to install GPU driver. After the installation, reboot the system. Execute "prime-select query" should get "on-demand" * Old GPU (which supported by nvidia-390 only) will keep in performance mode, refer LP:1957094. Execute "prime-select query" should get "nvidia" * On non-laptop machine. Can set GPU mode to on-demand * On laptop with GPU in runtime PM support list. Set GPU mode to on-demand and Nvidia driver is loaded with "NVreg_DynamicPowerManagement=0x02" [Where problems could occur] * With GPU supported RTD3 not able enable runtime PM on non-laptop. But based on the Nvidia README, this case shall not happened. [Other Info] Changelogs: nvidia-prime (0.8.16~0.20.04.2) focal; urgency=medium [ Jeremy Szu ] * Set on-demand mode as default nvidia mode (LP: #1942307) [ Alberto Milone ] * prime-select: - Detect chassis type and enable RTD3 only on laptops (LP: #1942788). - on-demand mode doesn't need to depend on RTD3 (LP: #1942789). - Use bootvga detection when last_gfx_boot is not available. - Don't check the current profile when setting a profile (LP: #1946476). - Catch BrokenPipeError. - Use bootvga detection when last_gfx_boot is not available. nvidia-prime (0.8.16.2~0.21.04.1) hirsute; urgency=medium [ Jeremy Szu ] * Set on-demand mode as default nvidia mode (LP: #1942307) [ Alberto Milone ] * prime-select: - Detect chassis type and enable RTD3 only on laptops (LP: #1942788). - on-demand mode doesn't need to depend on RTD3 (LP: #1942789). - Use bootvga detection when last_gfx_boot is not available. - Don't check the current profile when setting a profile (LP: #1946476). To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1942789/+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 1958019]
(In reply to Lucas Tanure from comment #539) > Hi, > > We are waiting for this patch series to be merged: > > https://lkml.org/lkml/2022/1/21/471 > > Thanks > Lucas Hi, just wanted to confirm, adding these patches on top of 5.17-rc4 works for me on my 2021 Legion 7 (AMD). This is running Ubuntu 21.04. I grabbed the kernel source from the Ubuntu tree, as linked here https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.17-rc4/ And built following the instructions here https://wiki.ubuntu.com/Kernel/BuildYourOwnKernel In the editconfigs step you have to navigate in menuconfig to Device Drivers / X86 Platform Specific Device Drivers / I2C and SPI multi instantiate pseudo device driver and select that module. Then Exit/Save the config and build. It takes a few minutes to build, but the process goes smoothly. Thanks for getting this working! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1958019 Title: [Lenovo Legion7 16ACHg6 82N6, Realtek ALC287, Speaker, Internal] No sound at all Status in sound-2.6 (alsa-kernel): Confirmed Status in alsa-driver package in Ubuntu: Confirmed Bug description: On my Lenovo Legion-7-16ACHg6 laptop I can't hear any sound by internal speakers, but it work by headphones connected to standard jack aux. uname -r 5.11.0-44-generic ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.11.0-44.48~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-44-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: i3draven 1266 F pulseaudio /dev/snd/controlC0: i3draven 1266 F pulseaudio /dev/snd/controlC1: i3draven 1266 F pulseaudio /dev/snd/pcmC1D0p: i3draven 1266 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Jan 15 15:10:53 2022 InstallationDate: Installed on 2021-10-11 (96 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed Symptom_Card: Family 17h (Models 10h-1fh) HD Audio Controller - HD-Audio Generic Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: i3draven 1266 F pulseaudio /dev/snd/controlC0: i3draven 1266 F pulseaudio /dev/snd/controlC1: i3draven 1266 F pulseaudio /dev/snd/pcmC1D0p: i3draven 1266 F...m pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [82N6, Realtek ALC287, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/08/2021 dmi.bios.release: 1.49 dmi.bios.vendor: LENOVO dmi.bios.version: GKCN49WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Legion 7 16ACHg6 dmi.ec.firmware.release: 1.49 dmi.modalias: dmi:bvnLENOVO:bvrGKCN49WW:bd11/08/2021:br1.49:efr1.49:svnLENOVO:pn82N6:pvrLegion716ACHg6:skuLENOVO_MT_82N6_BU_idea_FM_Legion716ACHg6:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLegion716ACHg6: dmi.product.family: Legion 7 16ACHg6 dmi.product.name: 82N6 dmi.product.sku: LENOVO_MT_82N6_BU_idea_FM_Legion 7 16ACHg6 dmi.product.version: Legion 7 16ACHg6 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/sound-2.6/+bug/1958019/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1953507] Re: [radeon] jammy live - on adjusting display config; one display is unsuable blocky-mess
so this is with X, what about the wayland session which should be the default? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-ati in Ubuntu. https://bugs.launchpad.net/bugs/1953507 Title: [radeon] jammy live - on adjusting display config; one display is unsuable blocky-mess Status in xserver-xorg-video-ati package in Ubuntu: New Bug description: ubuntu jammy daily (canary build) live test on - dell optiplex 960 (this is my primary machine; so is normally used for entry of data & not doing the QA-testing). on adjusting the displays to match my setup (six displays; two high & three across; this box uses two in the middle with middle on top row & middle on bottom row).. the top display is still useable, but the bottom is not. This boxes are not perfectly aligned as not all my displays are the exact same size; so top display is slightly to right of bottom display the bottom resembles a digital TV with bad signal, mostly blocky & parts of it flashing (very quickly). it doesn't match the attached picture (as viewable on this box anyway.. my top display; which was LEFT prior to alignment is perfectly readable). ** actual my top display is usable, bottom is not (blocky warped picture) ** expected on adjust displays to match my config; both displays remain usable & readable. ** notes likely related to graphics card & not GNOME. If I recall correctly; this box has an older video card used as it had 2x DVI connections my screens use. My usual install on this box is jammy; but I usually use LXQt/Lubuntu and I don't experience issues.. I also have installed Xubuntu/Xfce & Ubuntu/GNOME so can test the installed OS (where I don't believe I have issue), but my install is somewhat old (artful install upgraded every six months ~30-36 hours after each release) thus is likely heavily modified. ** Picture comments My top display is ~perfect (vertical white bar to left of ubuntu-dock- items I'd not expect, but the color-blocks to the left of the 'install/firefox/thunderbird/files` is NOT visible; only a vertical WHITE bar a few pixels wide to left of the dock appears' rest of top display is perfect. My bottom display is nothing like picture; it's unusable. A mixture of black/white boxes with red/purple bits which would be the picture warped into blocky-components. When I type, I get reactions on this display with the picture changing (mostly the black & white portions which flash, the red/purple bits which are warped indri picture appear to remain static). My phone/camera isn't working, but I've taken a photograph. I didn't anticipate issues in this QA-test (it's past 1AM now) otherwise I'd not have run this QA-test now. ** further comments this is likely a duplicate... I experience this type of reaction on other boxes; likely radeon related but I've yet to look & can't even remember which video card exists in this box (I don't experience issues with the display configuration of the box with identical card to this, but it relates to display setup/config... my other box with this card is landscape+portrait I believe and doesn't have one display above the other; ie. d780; I get these issues when one display is above the other - and only with single orientation (swap top/bottom and issues don't exist)) ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu1 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu74 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CasperVersion: 1.465+canary3.3 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Dec 7 13:52:56 2021 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Cedar [Radeon HD 5000/6000/7350/8350 Series] [1002:68f9] (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Radeon HD 6350 [103c:2126] LiveMediaBuild: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211206) MachineType: Dell Inc. OptiPlex 960 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz layerfs-path=minimal.standard.live.squashfs maybe-ubiquity --- quiet splash SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/05/2011 dmi.bios.release: 10.0 dmi.bios.vendor: Dell Inc. dmi.bios.version: A14 dmi.board.name: 0F428D dmi.board.vendor: Dell Inc. dmi.board.version: A00
