[Desktop-packages] [Bug 1996985] [NEW] ubuntu dock doesn't show network drives
Public bug reported: On Ubuntu 22.10, after successfully mounting a network drive through Nautilus (Files -> Other Locations -> Connect to Server), the network drive doesn't appear as it should in the dock. Settings -> Ubuntu Desktop -> Configure dock behavior -> Include Unmounted Volumes & Include Network Volumes gsettings get org.gnome.shell.extensions.dash-to-dock show-mounts true gsettings get org.gnome.shell.extensions.dash-to-dock show-mounts-network true All options are enabled (as it is by default). Note that it works fine for external drives like a USB key. It just doesn't for network drives somehow. ** Affects: gnome-shell-extension-ubuntu-dock (Ubuntu) Importance: Undecided Status: New -- 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/1996985 Title: ubuntu dock doesn't show network drives Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: New Bug description: On Ubuntu 22.10, after successfully mounting a network drive through Nautilus (Files -> Other Locations -> Connect to Server), the network drive doesn't appear as it should in the dock. Settings -> Ubuntu Desktop -> Configure dock behavior -> Include Unmounted Volumes & Include Network Volumes gsettings get org.gnome.shell.extensions.dash-to-dock show-mounts true gsettings get org.gnome.shell.extensions.dash-to-dock show-mounts-network true All options are enabled (as it is by default). Note that it works fine for external drives like a USB key. It just doesn't for network drives somehow. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1996985/+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 1871959] Re: Crash with SIGABRT in _iris_batch_flush from iris_fence_flush()
** Changed in: mesa Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1871959 Title: Crash with SIGABRT in _iris_batch_flush from iris_fence_flush() Status in Mesa: Fix Released Status in mesa package in Ubuntu: Confirmed Bug description: https://errors.ubuntu.com/problem/23a23997d8d3287584722beeaee600306df3a1bf https://errors.ubuntu.com/problem/d9ee437c6ea3330d18aecaa0d3e07f71ca0c8d1a https://errors.ubuntu.com/problem/a960bab710b867c695551df03b8207cdc0da9a6f --- nothing particular done to trigger this, just opening the lid apparently crashed the x server (ubuntu 20.04); then after reboot apport prompted me to report a crash ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: xserver-xorg-core 2:1.20.7-2ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 Uname: Linux 5.4.0-12-generic x86_64 ApportVersion: 2.20.11-0ubuntu25 Architecture: amd64 CompositorRunning: None CurrentDesktop: GNOME-Greeter:GNOME Date: Fri Apr 10 00:50:52 2020 DistUpgraded: 2019-12-20 18:35:39,979 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20180608-47+north-bay-14-15-15p+X56 DistroCodename: focal DistroVariant: ubuntu ExecutablePath: /usr/lib/xorg/Xorg ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 620 (Whiskey Lake) [1028:08b9] InstallationDate: Installed on 2019-11-27 (134 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 0bda:5532 Realtek Semiconductor Corp. Integrated_Webcam_HD Bus 001 Device 003: ID 8087:0029 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Latitude 5500 ProcCmdline: /usr/lib/xorg/Xorg vt1 -displayfd 3 -auth /run/user/120/gdm/Xauthority -background none -noreset -keeptty -verbose 3 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-12-generic root=UUID=559b7a9d-8198-424b-8812-ea72c10f013e ro mem_sleep_default=deep quiet splash vt.handoff=7 Signal: 6 SourcePackage: xorg-server StacktraceTop: __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50 __GI_abort () at abort.c:79 ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so Title: Xorg crashed with SIGABRT in __GI_raise() UpgradeStatus: Upgraded to focal on 2019-12-20 (111 days ago) UserGroups: dmi.bios.date: 08/21/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.1 dmi.board.name: 0M14W7 dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.5.1:bd08/21/2019:svnDellInc.:pnLatitude5500:pvr:rvnDellInc.:rn0M14W7:rvrA01:cvnDellInc.:ct10:cvr: dmi.product.family: Latitude dmi.product.name: Latitude 5500 dmi.product.sku: 08B9 dmi.sys.vendor: Dell Inc. separator: version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.100-4 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1871959/+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 1992187] Re: hplip not working after install in 22.04, python error
I also had this issue. I had hplip installed as part of my default ubuntu 22.04.1 LTS install. I downloaded the installer from the hp dev website (https://developers.hp.com/hp-linux-imaging-and- printing/install/install/index) and ran the auto installer. The installer installed some packages, and removed the old hplip install. This resulted in a working hplip. I did try reinstalling with apt but it did not resolve the issue. I had to use the installer from the hp website. Best of luck. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to hplip in Ubuntu. https://bugs.launchpad.net/bugs/1992187 Title: hplip not working after install in 22.04, python error Status in hplip package in Ubuntu: New Bug description: after upgrade from 20.04 to 22.04.1 (not a new installation): new installation of hplip >sudo apt install hplip hplip-gui Install completes without error. Using hplip, e.g. >hp-setup manual detection of wireless printer using IP works, printer is listed, but on 'next' -> process hangs (wait/termination suggested, wait does not help) alternative: (hplip installs a suite of programs) >hp-check(verifies installation and contact to printer, scanner produces normal output ending prematurely with error message: Saving output in log file: /home/glassel/hp-check.log HP Linux Imaging and Printing System (ver. 3.22.2) Dependency/Version Check Utility ver. 15.1 Copyright (c) 2001-18 HP Development Company, LP This software comes with ABSOLUTELY NO WARRANTY. This is free software, and you are welcome to distribute it under certain conditions. See COPYING file for more details. Note: hp-check can be run in three modes: 1. Compile-time check mode (-c or --compile): Use this mode before compiling the HPLIP supplied tarball (.tar.gz or .run) to determine if the proper dependencies are installed to successfully compile HPLIP. 2. Run-time check mode (-r or --run): Use this mode to determine if a distro supplied package (.deb, .rpm, etc) or an already built HPLIP supplied tarball has the proper dependencies installed to successfully run. 3. Both compile- and run-time check mode (-b or --both) (Default): This mode will check both of the above cases (both compile- and run-time dependencies). Check types: a. EXTERNALDEP - External Dependencies b. GENERALDEP - General Dependencies (required both at compile and run time) c. COMPILEDEP - Compile time Dependencies d. [All are run-time checks] PYEXT SCANCONF QUEUES PERMISSION Status Types: OK MISSING - Missing Dependency or Permission or Plug-in INCOMPAT - Incompatible dependency-version or Plugin-version -Traceback (most recent call last): File "/usr/bin/hp-check", line 861, in dep.core.init() File "/usr/share/hplip/installer/core_install.py", line 523, in init self.get_distro() File "/usr/share/hplip/installer/core_install.py", line 661, in get_distro if 'MX' in distro_release_name: NameError: name 'distro_release_name' is not defined further info: >apt-cache policy hplip hplip: Installed: 3.22.2+dfsg0-1+klbkjammy Candidate: 3.22.2+dfsg0-1+klbkjammy Version table: *** 3.22.2+dfsg0-1+klbkjammy 500 500 https://ppa.launchpadcontent.net/kelebek333/hplip/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status 3.21.12+dfsg0-1 500 500 http://de.archive.ubuntu.com/ubuntu jammy/main amd64 Packages > apt-cache policy hplip-gui hplip-gui: Installed: 3.22.2+dfsg0-1+klbkjammy Candidate: 3.22.2+dfsg0-1+klbkjammy Version table: *** 3.22.2+dfsg0-1+klbkjammy 500 500 https://ppa.launchpadcontent.net/kelebek333/hplip/ubuntu jammy/main amd64 Packages 500 https://ppa.launchpadcontent.net/kelebek333/hplip/ubuntu jammy/main i386 Packages 100 /var/lib/dpkg/status 3.21.12+dfsg0-1 500 500 http://de.archive.ubuntu.com/ubuntu jammy/universe amd64 Packages 500 http://de.archive.ubuntu.com/ubuntu jammy/universe i386 Packages --- I tried alternate ways to install hplip: hplip-3.22.6.run downloaded from hp this fails with an unmet dependency 'libcups2', but sudo apt install libcups2 tells me it is installed (-dev version, too) A fresh install of cups did not help. Best regards ... Peter Glassel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hplip/+bug/1992187/+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 1996946] Re: Memory leak on every frame when reading GIF animations
The attachment "Fix memory leak" seems to be a patch. If it isn't, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team. [This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issues please contact him.] ** Tags added: patch -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdk-pixbuf in Ubuntu. https://bugs.launchpad.net/bugs/1996946 Title: Memory leak on every frame when reading GIF animations Status in gdk-pixbuf package in Ubuntu: New Bug description: There is a big memory leak when reading GIF animations. The issue was identified and fixed in gdk-pixbuf two (2) years ago, but it was released in a version grater that the available in Ubuntu 20.04. At first glance, the leak appears only when a static image is requested, but this function is used by pixbuf's upload functions and calls this function internally. So the leak happens every time a GIF is loaded. Here is the commit with the fix released in version 2.41: https://gitlab.gnome.org/GNOME/gdk- pixbuf/-/commit/dd3aa9ed64a0a370c8150f98e849ffc6e73da827 A patch is attached to this message. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdk-pixbuf/+bug/1996946/+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 1996946] Re: Memory leak on every frame when reading GIF animations
** Description changed: There is a big memory leak when reading GIF animations. The issue was identified and fixed in gdk-pixbuf two (2) years ago, but it was released in a version grater that the available in Ubuntu 20.04. At first glance, the leak appears only when a static image is requested, but this function is used by pixbuf's upload functions and calls this function internally. So the leak happens every time a GIF is loaded. - Here is the commit with the fix releases in version 2.41: + Here is the commit with the fix released in version 2.41: https://gitlab.gnome.org/GNOME/gdk- pixbuf/-/commit/dd3aa9ed64a0a370c8150f98e849ffc6e73da827 A patch is attached to this message. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdk-pixbuf in Ubuntu. https://bugs.launchpad.net/bugs/1996946 Title: Memory leak on every frame when reading GIF animations Status in gdk-pixbuf package in Ubuntu: New Bug description: There is a big memory leak when reading GIF animations. The issue was identified and fixed in gdk-pixbuf two (2) years ago, but it was released in a version grater that the available in Ubuntu 20.04. At first glance, the leak appears only when a static image is requested, but this function is used by pixbuf's upload functions and calls this function internally. So the leak happens every time a GIF is loaded. Here is the commit with the fix released in version 2.41: https://gitlab.gnome.org/GNOME/gdk- pixbuf/-/commit/dd3aa9ed64a0a370c8150f98e849ffc6e73da827 A patch is attached to this message. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdk-pixbuf/+bug/1996946/+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 1996946] [NEW] Memory leak on every frame when reading GIF animations
Public bug reported: There is a big memory leak when reading GIF animations. The issue was identified and fixed in gdk-pixbuf two (2) years ago, but it was released in a version grater that the available in Ubuntu 20.04. At first glance, the leak appears only when a static image is requested, but this function is used by pixbuf's upload functions and calls this function internally. So the leak happens every time a GIF is loaded. Here is the commit with the fix releases in version 2.41: https://gitlab.gnome.org/GNOME/gdk- pixbuf/-/commit/dd3aa9ed64a0a370c8150f98e849ffc6e73da827 A patch is attached to this message. ** Affects: gdk-pixbuf (Ubuntu) Importance: Undecided Status: New ** Patch added: "Fix memory leak" https://bugs.launchpad.net/bugs/1996946/+attachment/5631282/+files/fix-animation-iterator-leak.patch ** Summary changed: - Memory leak on every frmae when reading GIF animations + Memory leak on every frame when reading GIF animations -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdk-pixbuf in Ubuntu. https://bugs.launchpad.net/bugs/1996946 Title: Memory leak on every frame when reading GIF animations Status in gdk-pixbuf package in Ubuntu: New Bug description: There is a big memory leak when reading GIF animations. The issue was identified and fixed in gdk-pixbuf two (2) years ago, but it was released in a version grater that the available in Ubuntu 20.04. At first glance, the leak appears only when a static image is requested, but this function is used by pixbuf's upload functions and calls this function internally. So the leak happens every time a GIF is loaded. Here is the commit with the fix releases in version 2.41: https://gitlab.gnome.org/GNOME/gdk- pixbuf/-/commit/dd3aa9ed64a0a370c8150f98e849ffc6e73da827 A patch is attached to this message. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdk-pixbuf/+bug/1996946/+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 964497] Re: GIF loader uses about 280M of VmRSS for a 200Kb GIF
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gdk-pixbuf (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdk-pixbuf in Ubuntu. https://bugs.launchpad.net/bugs/964497 Title: GIF loader uses about 280M of VmRSS for a 200Kb GIF Status in gdk-pixbuf: Fix Released Status in gdk-pixbuf package in Ubuntu: Confirmed Bug description: https://bugzilla.gnome.org/show_bug.cgi?id=585425 Patch reduced memory usage from 892MiB to 30MiB on amd64 - may it will be useful? To manage notifications about this bug go to: https://bugs.launchpad.net/gdk-pixbuf/+bug/964497/+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 1950040] Re: Wayland Screensharing broken in Ubuntu 21.10
The fix is available in Chromium beta and edge channels. If someone can confirm it I'll release to stable too. ** Changed in: chromium-browser (Ubuntu) Status: Triaged => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xdg-desktop-portal-gtk in Ubuntu. https://bugs.launchpad.net/bugs/1950040 Title: Wayland Screensharing broken in Ubuntu 21.10 Status in chromium-browser package in Ubuntu: Fix Committed Status in firefox package in Ubuntu: Fix Released Status in gnome-shell package in Ubuntu: Invalid Status in pipewire package in Ubuntu: Invalid Status in xdg-desktop-portal package in Ubuntu: Invalid Status in xdg-desktop-portal-gtk package in Ubuntu: Fix Released Bug description: Freshly installed Ubuntu 21.10, screen sharing does not work with any browser, tested the following options: - Firefox snap - Firefox deb - Chromium snap - Chromium flatpak Steps to reproduce: 1. Go to https://www.webrtc-experiment.com/Pluginfree-Screen-Sharing/#7325517390736006 2. Select to share the whole desktop in the xdg-desktop-portal 3. Notice the orange screen share indicator in Gnome-Shell but actually nothing is shared in the browser. This should be handled high priority since this is a critical feature during the pandemic. Filed against ubuntu-meta since I don't know exactly which package to blame, whether it's pipewire, xdg-desktop portal or some problem directely with mutter / gnome-shell, please reassign accordingly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1950040/+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 1995766] Re: X server segfault when starting youtube videos
Crash just happened again (this time watching a video on reddit, not youtube.) There are three resulting files in /var/crash: 2022-11-17 09:43:59 _usr_bin_kwin_x11.1000.crash 2022-11-17 09:43:54 _usr_lib_x86_64-linux-gnu_libexec_drkonqi.1000.crash 2022-11-17 09:43:53 _usr_lib_xorg_Xorg.0.crash ...I did "ubuntu-bug filename" for each one of them, and that seemed to work fine, but there was no ID reported to me of the newly-created bug, so I can't report that per the instructions above. How do I discover this in order to report it? I could also post those files somewhere, if it's not a big security risk. ubuntu-bug was run roughly at 2022-11-17 17:45:00 UTC, if that helps. I checked the whoopsie link and there were no relevant crashes there that I could find. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1995766 Title: X server segfault when starting youtube videos Status in xorg-server package in Ubuntu: Incomplete Bug description: This is an intermittent bug; happens perhaps 1-3 times a week. Always when just starting to play a youtube videos (I haven't seen it playing videos on other sites, or locally, but the sample size is skewed.) I'm using Nvidia drivers with a 6GB 1060 GTX running three monitors. Kubuntu 22.04, up-to-date. GPU memory is not stressed (usually around 5 or 6% usage. System RAM is 16GB, also not stressed (10-15%). Stack trace in Xorg.0.log.old is always the same: [ 1890.850] (EE) [ 1890.850] (EE) Backtrace: [ 1890.851] (EE) 0: /usr/lib/xorg/Xorg (OsLookupColor+0x139) [0x558c420666e9] [ 1890.852] (EE) 1: /lib/x86_64-linux-gnu/libc.so.6 (__sigaction+0x50) [0x7f40d5da5520] [ 1890.852] (EE) 2: /usr/lib/xorg/Xorg (NewCurrentScreen+0x1b9) [0x558c41efb1e9] [ 1890.852] (EE) 3: /usr/lib/xorg/Xorg (MaybeDeliverEventsToClient+0x4d5) [0x558c41efcc85] [ 1890.852] (EE) 4: /usr/lib/xorg/Xorg (MaybeDeliverEventsToClient+0x9d3) [0x558c41efd183] [ 1890.852] (EE) 5: /usr/lib/xorg/Xorg (WindowsRestructured+0x163) [0x558c41efe183] [ 1890.853] (EE) 6: /usr/lib/xorg/Xorg (InitProximityClassDeviceStruct+0x1fdd) [0x558c41fdca7d] [ 1890.853] (EE) 7: /usr/lib/xorg/Xorg (XkbHandleActions+0x1dc) [0x558c42006e4c] [ 1890.853] (EE) 8: /usr/lib/xorg/Xorg (XkbRemoveResourceClient+0x7c1) [0x558c4121] [ 1890.853] (EE) 9: /usr/lib/xorg/Xorg (XkbRemoveResourceClient+0x9be) [0x558c4200011e] [ 1890.854] (EE) 10: /usr/lib/xorg/Xorg (TimerSet+0x170) [0x558c4205fc60] [ 1890.854] (EE) 11: /usr/lib/xorg/Xorg (WaitForSomething+0x258) [0x558c4205fee8] [ 1890.854] (EE) 12: /usr/lib/xorg/Xorg (SendErrorToClient+0x117) [0x558c41ef0257] [ 1890.854] (EE) 13: /usr/lib/xorg/Xorg (InitFonts+0x3c4) [0x558c41ef4524] [ 1890.854] (EE) 14: /lib/x86_64-linux-gnu/libc.so.6 (__libc_init_first+0x90) [0x7f40d5d8cd90] [ 1890.854] (EE) 15: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0x80) [0x7f40d5d8ce40] [ 1890.855] (EE) 16: /usr/lib/xorg/Xorg (_start+0x25) [0x558c41edd5f5] [ 1890.855] (EE) [ 1890.855] (EE) Segmentation fault at address 0x7ffec8965000 [ 1890.855] (EE) Fatal server error: [ 1890.855] (EE) Caught signal 11 (Segmentation fault). Server aborting ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60 Uname: Linux 5.15.0-52-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.141.03 Thu Jun 30 18:45:31 UTC 2022 GCC version: gcc version 11.2.0 (Ubuntu 11.2.0-19ubuntu1) ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: KDE Date: Sat Nov 5 10:27:18 2022 DistUpgraded: 2022-05-14 14:47:14,165 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: jammy DistroVariant: ubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: No GraphicsCard: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [1458:d000] NVIDIA Corporation GP106 [GeForce GTX 1060 6GB] [10de:1c03] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Micro-Star
[Desktop-packages] [Bug 1996927] [NEW] Nautilus send mail not working
Public bug reported: Hi, After upgrade from 22.04 to 22.10 Send an attached file to email from nautilus is not working anymore. Menu sendmail ( courriel in french) appears when i right click on file , then thunderbird appears but without the attachement . It was working very well with previous releases . regards Yanick ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: nautilus 1:43.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7 Uname: Linux 5.19.0-23-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Nov 17 18:42:19 2022 InstallationDate: Installed on 2021-10-16 (397 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: file-roller 43.0-1 nautilus-extension-gnome-terminal 3.46.2-1ubuntu1 nautilus-image-converter 0.4.0-2 python3-nautilus 4.0-1 ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug kinetic wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1996927 Title: Nautilus send mail not working Status in nautilus package in Ubuntu: New Bug description: Hi, After upgrade from 22.04 to 22.10 Send an attached file to email from nautilus is not working anymore. Menu sendmail ( courriel in french) appears when i right click on file , then thunderbird appears but without the attachement . It was working very well with previous releases . regards Yanick ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: nautilus 1:43.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7 Uname: Linux 5.19.0-23-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Nov 17 18:42:19 2022 InstallationDate: Installed on 2021-10-16 (397 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: file-roller 43.0-1 nautilus-extension-gnome-terminal 3.46.2-1ubuntu1 nautilus-image-converter 0.4.0-2 python3-nautilus 4.0-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1996927/+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 1973441] Re: Printing does not work on Ubuntu 22.04 - cups-pki-invalid
Further confirmation, deleting a certificate file (dated Sept 2nd) got printing working again. Printer Xerox B230 (probably not relevant, I'm guessing) -- 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/1973441 Title: Printing does not work on Ubuntu 22.04 - cups-pki-invalid Status in cups package in Ubuntu: Confirmed Bug description: After upgrading to 22.04 printing did not work. There is cups-pki- invalid error and printer goes to paused state. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: cups 2.4.1op1-1ubuntu4 Uname: Linux 5.17.7-051707-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CupsErrorLog: Error: [Errno 13] Permission denied: '/var/log/cups/error_log' CurrentDesktop: ubuntu:GNOME Date: Sun May 15 15:34:47 2022 EcryptfsInUse: Yes InstallationDate: Installed on 2021-10-12 (214 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Daily amd64 (20211010) Lpstat: device for HP_Color_LaserJet_M552_5F80BF: implicitclass://HP_Color_LaserJet_M552_5F80BF/ MachineType: ASUSTeK COMPUTER INC. ROG Strix G513QY_G513QY Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/HP_Color_LaserJet_M552_5F80BF.ppd'] failed with exit code 2: grep: /etc/cups/ppd/HP_Color_LaserJet_M552_5F80BF.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.17.7-051707-generic root=UUID=ff964c9b-ce92-4334-8759-9d785a262c60 ro rootflags=subvol=@ quiet splash vt.handoff=7 SourcePackage: cups UpgradeStatus: Upgraded to jammy on 2022-04-24 (21 days ago) dmi.bios.date: 03/29/2022 dmi.bios.release: 5.19 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: G513QY.318 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: G513QY dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.ec.firmware.release: 0.81 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrG513QY.318:bd03/29/2022:br5.19:efr0.81:svnASUSTeKCOMPUTERINC.:pnROGStrixG513QY_G513QY:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG513QY:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku: dmi.product.family: ROG Strix dmi.product.name: ROG Strix G513QY_G513QY dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1973441/+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 1992679] Re: Can not login after new kernel installed (nvidia driver crashed)
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: xserver-xorg-video-intel (Ubuntu Jammy) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu. https://bugs.launchpad.net/bugs/1992679 Title: Can not login after new kernel installed (nvidia driver crashed) Status in linux package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-510 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-515 package in Ubuntu: Confirmed Status in xserver-xorg-video-intel package in Ubuntu: Confirmed Status in linux source package in Jammy: Confirmed Status in nvidia-graphics-drivers-510 source package in Jammy: Confirmed Status in nvidia-graphics-drivers-515 source package in Jammy: Confirmed Status in xserver-xorg-video-intel source package in Jammy: Confirmed Bug description: Hello. Today i have installed new kernel from. I installed 5.15.0-50 and after that i can not login to system... I see boot text, but after booting i see black log screen and can not login. I able boot and login with old kernel (5.15.0-48). I updated these packages: Install: linux-headers-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic), linux-cloud-tools-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic), linux-modules-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic), linux-modules-extra-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic), linux-cloud-tools-5.15.0-50:amd64 (5.15.0-50.56, automatic), linux-tools-5.15.0-50:amd64 (5.15.0-50.56, automatic), linux-headers-5.15.0-50:amd64 (5.15.0-50.56, automatic), linux-image-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic), linux-tools-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic) Upgrade: linux-headers-generic:amd64 (5.15.0.48.48, 5.15.0.50.50), google-chrome-stable:amd64 (106.0.5249.103-1, 106.0.5249.119-1), linux-generic:amd64 (5.15.0.48.48, 5.15.0.50.50), linux-image-generic:amd64 (5.15.0.48.48, 5.15.0.50.50), linux-tools-generic:amd64 (5.15.0.48.48, 5.15.0.50.50), linux-cloud-tools-generic:amd64 (5.15.0.48.48, 5.15.0.50.50) Updated logs see in attachement. Logs from journalctl see in attachements. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-50-generic 5.15.0-50.56 ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53 Uname: Linux 5.15.0-48-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: vodka 1819 F pulseaudio /dev/snd/controlC1: vodka 1819 F pulseaudio CasperMD5CheckResult: unknown Date: Wed Oct 12 19:56:43 2022 InstallationDate: Installed on 2018-05-02 (1623 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 05e3:0608 Genesys Logic, Inc. Hub Bus 001 Device 003: ID 09da:fa18 A4Tech Co., Ltd. USB Device Bus 001 Device 002: ID 046d:c084 Logitech, Inc. G203 Gaming Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Gigabyte Technology Co., Ltd. H610M S2H DDR4 ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-48-generic root=UUID=b27e8e45-cedd-4ab6-b2e6-ab6bef5e9336 ro PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.15.0-48-generic N/A linux-backports-modules-5.15.0-48-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.5 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2022-04-27 (167 days ago) dmi.bios.date: 03/28/2022 dmi.bios.release: 5.24 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: F7a dmi.board.asset.tag: Default string dmi.board.name: H610M S2H DDR4 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF7a:bd03/28/2022:br5.24:svnGigabyteTechnologyCo.,Ltd.:pnH610MS2HDDR4:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnH610MS2HDDR4:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: H610 MB dmi.product.name: H610M S2H DDR4 dmi.product.sku: Default string dmi.product.version: -CF dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1992679/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net
[Desktop-packages] [Bug 1992679] Re: Can not login after new kernel installed (nvidia driver crashed)
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: xserver-xorg-video-intel (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu. https://bugs.launchpad.net/bugs/1992679 Title: Can not login after new kernel installed (nvidia driver crashed) Status in linux package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-510 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-515 package in Ubuntu: Confirmed Status in xserver-xorg-video-intel package in Ubuntu: Confirmed Status in linux source package in Jammy: Confirmed Status in nvidia-graphics-drivers-510 source package in Jammy: Confirmed Status in nvidia-graphics-drivers-515 source package in Jammy: Confirmed Status in xserver-xorg-video-intel source package in Jammy: Confirmed Bug description: Hello. Today i have installed new kernel from. I installed 5.15.0-50 and after that i can not login to system... I see boot text, but after booting i see black log screen and can not login. I able boot and login with old kernel (5.15.0-48). I updated these packages: Install: linux-headers-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic), linux-cloud-tools-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic), linux-modules-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic), linux-modules-extra-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic), linux-cloud-tools-5.15.0-50:amd64 (5.15.0-50.56, automatic), linux-tools-5.15.0-50:amd64 (5.15.0-50.56, automatic), linux-headers-5.15.0-50:amd64 (5.15.0-50.56, automatic), linux-image-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic), linux-tools-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic) Upgrade: linux-headers-generic:amd64 (5.15.0.48.48, 5.15.0.50.50), google-chrome-stable:amd64 (106.0.5249.103-1, 106.0.5249.119-1), linux-generic:amd64 (5.15.0.48.48, 5.15.0.50.50), linux-image-generic:amd64 (5.15.0.48.48, 5.15.0.50.50), linux-tools-generic:amd64 (5.15.0.48.48, 5.15.0.50.50), linux-cloud-tools-generic:amd64 (5.15.0.48.48, 5.15.0.50.50) Updated logs see in attachement. Logs from journalctl see in attachements. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-50-generic 5.15.0-50.56 ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53 Uname: Linux 5.15.0-48-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: vodka 1819 F pulseaudio /dev/snd/controlC1: vodka 1819 F pulseaudio CasperMD5CheckResult: unknown Date: Wed Oct 12 19:56:43 2022 InstallationDate: Installed on 2018-05-02 (1623 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 05e3:0608 Genesys Logic, Inc. Hub Bus 001 Device 003: ID 09da:fa18 A4Tech Co., Ltd. USB Device Bus 001 Device 002: ID 046d:c084 Logitech, Inc. G203 Gaming Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Gigabyte Technology Co., Ltd. H610M S2H DDR4 ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-48-generic root=UUID=b27e8e45-cedd-4ab6-b2e6-ab6bef5e9336 ro PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.15.0-48-generic N/A linux-backports-modules-5.15.0-48-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.5 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2022-04-27 (167 days ago) dmi.bios.date: 03/28/2022 dmi.bios.release: 5.24 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: F7a dmi.board.asset.tag: Default string dmi.board.name: H610M S2H DDR4 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF7a:bd03/28/2022:br5.24:svnGigabyteTechnologyCo.,Ltd.:pnH610MS2HDDR4:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnH610MS2HDDR4:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: H610 MB dmi.product.name: H610M S2H DDR4 dmi.product.sku: Default string dmi.product.version: -CF dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1992679/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net
[Desktop-packages] [Bug 1991526] Re: Laptop panel freezes on return from screensaver with external monitor attached
FYI, this seems to be fixed with the latest updates, I no longer encounter it since about two, three weeks now. -- 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/1991526 Title: Laptop panel freezes on return from screensaver with external monitor attached Status in gnome-shell package in Ubuntu: New Bug description: My setup is composed of a Dell XPS13 9320, with one (or two) external USB-C monitors attached. The laptop panel is the primary screen. I'm using gnome on Wayland. Everything is working fine, except when resuming from screensaver: the prompt for password is shown on the laptop panel, and I start typing the password. At this point, the laptop panel freezes. This can happen almost immediately (I will see for example two or three dots as I typed the first characters of my password) or this can happen a few seconds later (meanwhile the screen has been unlocked, the panel shows the desktop, then it freezes). Interestingly, the external monitors are woken up, desktop is unlocked, and will continue working, while the laptop panel is frozen. After that, let's say 40% of the time, the panel will un-freeze itself after 30 seconds or so. 40% of the time it will remain frozen, and 20% of the time the whole display will freeze (including the external monitors). When it happens, I can recover by either un-plugging / re-plugging one of the external monitors, or by typing Ctrl-Alt-F1, then retyping my password, then everything is fine again... until the next screen lock. This bug is reproducible more or less 50% of the time (one in two screen locks causes freezes). Deactivating the dash-to-panel gnome extension made it less reproducible, but it still happens. I didn't see any interesting error message in the logs, but maybe I didn't look at the correct place. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gdm3 42.0-1ubuntu7 ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53 Uname: Linux 5.15.0-48-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Oct 3 13:54:42 2022 ExecutablePath: /usr/libexec/gdm-wayland-session InstallationDate: Installed on 2022-07-20 (75 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) ProcEnviron: SHELL=/bin/bash PATH=(custom, no user) LANG=fr_FR.UTF-8 XDG_RUNTIME_DIR= SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1991526/+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 1996905] Re: Minimise window fails first time
I removed libreoffice-gnome and -gtk3, and the problem went away. My version now shows: Version: 7.4.2.3 / LibreOffice Community Build ID: 40(Build:3) CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: x11 Locale: en-GB (en_GB.UTF-8); UI: en-GB Ubuntu package version: 1:7.4.2~rc3-0ubuntu0.22.04.1~lo1 Calc: threaded It's not as user friendly. Note that my original problem only seems to occur when I open the start center already full screen from the last time I opened it. -- 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/1996905 Title: Minimise window fails first time Status in libreoffice package in Ubuntu: New Bug description: Opening libreoffice full screen, pressing the button at top right to shrink the window causes the window to expand beyond the edge of the screen. It is just possible to press it again on the edge of the screen, and LO goes back to normal full screen. Pressing it again works normally. Version: 7.4.2.3 / LibreOffice Community Build ID: 40(Build:3) CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3 Locale: en-GB (en_GB.UTF-8); UI: en-GB Ubuntu package version: 1:7.4.2~rc3-0ubuntu0.22.04.1~lo1 Calc: threaded In Windows 10 this doesn't happen. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1996905/+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 1995537] Re: snap 'cannot communicate with server:'
** Package changed: snap (Ubuntu) => snapd (Ubuntu)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1995537
Title:
snap 'cannot communicate with server:'
Status in lightdm package in Ubuntu:
New
Status in snapd package in Ubuntu:
New
Status in ubuntu-advantage-tools package in Ubuntu:
Invalid
Bug description:
Both snap and lightdm haven't worked on my laptop for a while. Both
work on my desktop without issue. The only difference I can find is
that my laptop has an NVIDIA gpu while my desktop has an AMD GPU. This
could account for the lightdm issues: whenever I try to use lightdm
instead of gdm3, I get stuck in an infinite login loop. But it
shouldn't account for the snap not functioning at all.
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: ubuntu-advantage-tools 27.11.3~22.04.1
ProcVersionSignature: Ubuntu 5.15.0-53.59-generic 5.15.64
Uname: Linux 5.15.0-53-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu82.2
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: Unity:Unity7:ubuntu
Date: Wed Nov 2 17:51:30 2022
InstallationDate: Installed on 2021-02-23 (617 days ago)
InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: ubuntu-advantage-tools
UpgradeStatus: Upgraded to jammy on 2022-04-24 (192 days ago)
cloud-id.txt-error: Invalid command specified 'cloud-id'.
jobs-status.json: {"update_messaging": {"last_run":
"2022-11-03T00:06:13.370368+00:00", "next_run":
"2022-11-03T06:06:13.370368+00:00"}, "update_status": {"last_run":
"2022-11-02T17:09:56+00:00", "next_run": "2022-11-03T05:09:56+00:00"},
"metering": {"last_run": "2022-11-03T00:06:13.370368+00:00", "next_run":
"2022-11-03T04:06:13.370368+00:00"}}
livepatch-status.txt-error: Invalid command specified
'/snap/bin/canonical-livepatch status'.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1995537/+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 1996905] Re: Minimise window fails first time
I mean the button that makes the window smaller, not the one that makes it disappear to the toolbar. -- 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/1996905 Title: Minimise window fails first time Status in libreoffice package in Ubuntu: New Bug description: Opening libreoffice full screen, pressing the button at top right to shrink the window causes the window to expand beyond the edge of the screen. It is just possible to press it again on the edge of the screen, and LO goes back to normal full screen. Pressing it again works normally. Version: 7.4.2.3 / LibreOffice Community Build ID: 40(Build:3) CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3 Locale: en-GB (en_GB.UTF-8); UI: en-GB Ubuntu package version: 1:7.4.2~rc3-0ubuntu0.22.04.1~lo1 Calc: threaded In Windows 10 this doesn't happen. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1996905/+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 1996905] [NEW] Minimise window fails first time
Public bug reported: Opening libreoffice full screen, pressing the button at top right to shrink the window causes the window to expand beyond the edge of the screen. It is just possible to press it again on the edge of the screen, and LO goes back to normal full screen. Pressing it again works normally. Version: 7.4.2.3 / LibreOffice Community Build ID: 40(Build:3) CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3 Locale: en-GB (en_GB.UTF-8); UI: en-GB Ubuntu package version: 1:7.4.2~rc3-0ubuntu0.22.04.1~lo1 Calc: threaded In Windows 10 this doesn't happen. ** Affects: libreoffice (Ubuntu) Importance: Undecided Status: New -- 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/1996905 Title: Minimise window fails first time Status in libreoffice package in Ubuntu: New Bug description: Opening libreoffice full screen, pressing the button at top right to shrink the window causes the window to expand beyond the edge of the screen. It is just possible to press it again on the edge of the screen, and LO goes back to normal full screen. Pressing it again works normally. Version: 7.4.2.3 / LibreOffice Community Build ID: 40(Build:3) CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3 Locale: en-GB (en_GB.UTF-8); UI: en-GB Ubuntu package version: 1:7.4.2~rc3-0ubuntu0.22.04.1~lo1 Calc: threaded In Windows 10 this doesn't happen. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1996905/+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 1996900] [NEW] display flashes
Public bug reported: During normal usage the display sometimes flashes black. In particular some websites cause intense flickering with several black frames per second. This actually seems to happen in both Wayland and xorg sessions and flashes the entire screen, so it seems more like a driver bug but I'm not sure where to file that. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7 Uname: Linux 5.19.0-23-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: KDE Date: Thu Nov 17 14:00:15 2022 DistUpgraded: Fresh install DistroCodename: kinetic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Raphael [1002:164e] (rev c1) (prog-if 00 [VGA controller]) Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Raphael [1002:164e] InstallationDate: Installed on 2022-10-30 (18 days ago) InstallationMedia: Lubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221017.1) MachineType: ASUS System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-23-generic root=UUID=bcf965e4-1a60-42fe-8033-214524d1908b ro quiet cryptdevice=UUID=66cc3c7b-e0bd-4535-b634-d56226dd88f1:luks-66cc3c7b-e0bd-4535-b634-d56226dd88f1 root=/dev/mapper/luks-66cc3c7b-e0bd-4535-b634-d56226dd88f1 splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/08/2022 dmi.bios.release: 6.3 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0603 dmi.board.asset.tag: Default string dmi.board.name: TUF GAMING X670E-PLUS dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0603:bd09/08/2022:br6.3:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnTUFGAMINGX670E-PLUS:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: ASUS version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug corruption kinetic kubuntu ubuntu wayland-session -- 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/1996900 Title: display flashes Status in xorg package in Ubuntu: New Bug description: During normal usage the display sometimes flashes black. In particular some websites cause intense flickering with several black frames per second. This actually seems to happen in both Wayland and xorg sessions and flashes the entire screen, so it seems more like a driver bug but I'm not sure where to file that. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7 Uname: Linux 5.19.0-23-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: KDE Date: Thu Nov 17 14:00:15 2022 DistUpgraded: Fresh install DistroCodename: kinetic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Raphael [1002:164e] (rev c1) (prog-if 00 [VGA controller]) Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Raphael [1002:164e] InstallationDate: Installed on 2022-10-30 (18 days ago) InstallationMedia: Lubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221017.1) MachineType: ASUS System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-23-generic root=UUID=bcf965e4-1a60-42fe-8033-214524d1908b ro quiet cryptdevice=UUID=66cc3c7b-e0bd-4535-b634-d56226dd88f1:luks-66cc3c7b-e0bd-4535-b634-d56226dd88f1 root=/dev/mapper/luks-66cc3c7b-e0bd-4535-b634-d56226dd88f1 splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install)
[Desktop-packages] [Bug 1815036] Re: uri defined for connectivity check does not have IPv6 address
The connectivity server does handle IPv6 now ** Changed in: network-manager (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1815036 Title: uri defined for connectivity check does not have IPv6 address Status in network-manager package in Ubuntu: Fix Released Bug description: As per subject. This package defines the file /usr/lib/NetworkManager/conf.d/20-connectivity-ubuntu.conf, which defines the uri for the connectivity check to be http://connectivity- check.ubuntu.com This hostname does not resolve to an IPv6 address. Therefore, even if the user has fully working IPv6, the connectivity check for IPv6 will fail. As a result, the IPv6 default routes will be heavily deprioritised (ie: having 2 added to the metric) rendering them effectively inoperable absent a deliberate effort to use IPv6-only addresses. NB: This was discovered by-the-by during reporting of bug #1814262 upstream at https://gitlab.freedesktop.org/NetworkManager/NetworkManager/issues/116#note_114448 It seems to be irrelevant to the main thrust of that bug, which is that IPv4 wired routes are not being identified as working correctly. In fact, when I switch to network-manager-config-connectivity-debian, the hostname defined there *does* have a working IPv6 address, and the issue actually being reported in that other bug does not affect the IPv6 routes, only the IPv4 ones. The bug here probably doesn't need any change made to the package itself, but rather to the networking of the actual target URL. It needs an IPv6 () DNS record, and for it to function on that address. I note in passing the debian connectivity check URL resolves to several IP addresses - four IPv4 addresses and 3 IPv6 addresses, presumably geographically diverse. (It's actually a CNAME to static.debian.org) This looks like it would be a more reliable target for connectivity checks. The ubuntu URL only resolves to a single IPv4 address. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: network-manager-config-connectivity-ubuntu 1.15.2-0ubuntu1 ProcVersionSignature: Ubuntu 4.19.0-12.13-generic 4.19.18 Uname: Linux 4.19.0-12-generic x86_64 ApportVersion: 2.20.10-0ubuntu20 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Feb 7 12:35:24 2019 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2018-09-11 (148 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180214) IpRoute: default via 192.168.1.254 dev enp63s0 proto dhcp metric 100 default via 192.168.1.254 dev wlp2s0 proto dhcp metric 20600 169.254.0.0/16 dev wlp2s0 scope link metric 1000 192.168.1.0/24 dev enp63s0 proto kernel scope link src 192.168.1.106 metric 100 192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.101 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true PackageArchitecture: all SourcePackage: network-manager UpgradeStatus: Upgraded to disco on 2019-01-13 (24 days ago) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.15.2 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1815036/+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 1995137] Re: Add "sun4i-drm_dri.so" to libg1-mesa-dri and fix compilation on riscv64
Prebuilt packages for riscv64 are available in this PPA: https://launchpad.net/~itrue/+archive/ubuntu/mesa-riscv64 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1995137 Title: Add "sun4i-drm_dri.so" to libg1-mesa-dri and fix compilation on riscv64 Status in mesa package in Ubuntu: New Bug description: "sun4i-drm_dri.so" is needed for some RISC-V platforms such as the Allwinner D1. This file is missing from the riscv64 packages, but present on others. This affects (at least) 20.04 and 22.04. itrue@lxc-focal ~/tmp> dpkg -c libgl1-mesa-dri_21.2.6-0ubuntu0.1~20.04.2_arm64.deb | grep _dri.so *snip* hrw-r--r-- root/root 0 2022-03-08 16:37 ./usr/lib/aarch64-linux-gnu/dri/sun4i-drm_dri.so link to ./usr/lib/aarch64-linux-gnu/dri/armada-drm_dri.so *snip* itrue@lxc-focal ~/tmp> dpkg -c libgl1-mesa-dri_21.2.6-0ubuntu0.1~20.04.2_riscv64.deb | grep _dri.so -rw-r--r-- root/root 16498024 2022-03-08 16:37 ./usr/lib/riscv64-linux-gnu/dri/kms_swrast_dri.so hrw-r--r-- root/root 0 2022-03-08 16:37 ./usr/lib/riscv64-linux-gnu/dri/nouveau_dri.so link to ./usr/lib/riscv64-linux-gnu/dri/kms_swrast_dri.so -rw-r--r-- root/root 4692400 2022-03-08 16:37 ./usr/lib/riscv64-linux-gnu/dri/nouveau_vieux_dri.so hrw-r--r-- root/root 0 2022-03-08 16:37 ./usr/lib/riscv64-linux-gnu/dri/r200_dri.so link to ./usr/lib/riscv64-linux-gnu/dri/nouveau_vieux_dri.so hrw-r--r-- root/root 0 2022-03-08 16:37 ./usr/lib/riscv64-linux-gnu/dri/r300_dri.so link to ./usr/lib/riscv64-linux-gnu/dri/kms_swrast_dri.so hrw-r--r-- root/root 0 2022-03-08 16:37 ./usr/lib/riscv64-linux-gnu/dri/r600_dri.so link to ./usr/lib/riscv64-linux-gnu/dri/kms_swrast_dri.so hrw-r--r-- root/root 0 2022-03-08 16:37 ./usr/lib/riscv64-linux-gnu/dri/radeon_dri.so link to ./usr/lib/riscv64-linux-gnu/dri/nouveau_vieux_dri.so hrw-r--r-- root/root 0 2022-03-08 16:37 ./usr/lib/riscv64-linux-gnu/dri/radeonsi_dri.so link to ./usr/lib/riscv64-linux-gnu/dri/kms_swrast_dri.so hrw-r--r-- root/root 0 2022-03-08 16:37 ./usr/lib/riscv64-linux-gnu/dri/swrast_dri.so link to ./usr/lib/riscv64-linux-gnu/dri/kms_swrast_dri.so hrw-r--r-- root/root 0 2022-03-08 16:37 ./usr/lib/riscv64-linux-gnu/dri/virtio_gpu_dri.so link to ./usr/lib/riscv64-linux-gnu/dri/kms_swrast_dri.so hrw-r--r-- root/root 0 2022-03-08 16:37 ./usr/lib/riscv64-linux-gnu/dri/zink_dri.so link to ./usr/lib/riscv64-linux-gnu/dri/kms_swrast_dri.so To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1995137/+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 1987631] Re: Screencast only records one second
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: pipewire (Ubuntu Jammy) 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/1987631 Title: Screencast only records one second Status in GNOME Shell: Fix Released Status in OEM Priority Project: In Progress Status in gnome-shell package in Ubuntu: Fix Released Status in pipewire package in Ubuntu: Fix Released Status in gnome-shell source package in Jammy: Fix Released Status in pipewire source package in Jammy: Confirmed Bug description: When recording a screencast with gnome on kinetic the resulting video will play for one second and then freeze. It looks like the same bug was discussed upstream at https://gitlab.gnome.org/GNOME/gnome- shell/-/issues/5585 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1987631/+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 1950040] Re: Wayland Screensharing broken in Ubuntu 21.10
** Changed in: chromium-browser (Ubuntu) Status: Invalid => Triaged ** Changed in: chromium-browser (Ubuntu) Assignee: (unassigned) => Nathan Pratta Teodosio (nteodosio) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xdg-desktop-portal-gtk in Ubuntu. https://bugs.launchpad.net/bugs/1950040 Title: Wayland Screensharing broken in Ubuntu 21.10 Status in chromium-browser package in Ubuntu: Triaged Status in firefox package in Ubuntu: Fix Released Status in gnome-shell package in Ubuntu: Invalid Status in pipewire package in Ubuntu: Invalid Status in xdg-desktop-portal package in Ubuntu: Invalid Status in xdg-desktop-portal-gtk package in Ubuntu: Fix Released Bug description: Freshly installed Ubuntu 21.10, screen sharing does not work with any browser, tested the following options: - Firefox snap - Firefox deb - Chromium snap - Chromium flatpak Steps to reproduce: 1. Go to https://www.webrtc-experiment.com/Pluginfree-Screen-Sharing/#7325517390736006 2. Select to share the whole desktop in the xdg-desktop-portal 3. Notice the orange screen share indicator in Gnome-Shell but actually nothing is shared in the browser. This should be handled high priority since this is a critical feature during the pandemic. Filed against ubuntu-meta since I don't know exactly which package to blame, whether it's pipewire, xdg-desktop portal or some problem directely with mutter / gnome-shell, please reassign accordingly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1950040/+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 1950040] Chromium
I verified that full screen sharing doesn't work out of the box in Chromium and Google Chrome. However, the fix suggested by https://superuser.com/a/1481800 works, namely to enable the flag in chrome://flags/#enable-webrtc-pipewire-capturer. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xdg-desktop-portal-gtk in Ubuntu. https://bugs.launchpad.net/bugs/1950040 Title: Wayland Screensharing broken in Ubuntu 21.10 Status in chromium-browser package in Ubuntu: Invalid Status in firefox package in Ubuntu: Fix Released Status in gnome-shell package in Ubuntu: Invalid Status in pipewire package in Ubuntu: Invalid Status in xdg-desktop-portal package in Ubuntu: Invalid Status in xdg-desktop-portal-gtk package in Ubuntu: Fix Released Bug description: Freshly installed Ubuntu 21.10, screen sharing does not work with any browser, tested the following options: - Firefox snap - Firefox deb - Chromium snap - Chromium flatpak Steps to reproduce: 1. Go to https://www.webrtc-experiment.com/Pluginfree-Screen-Sharing/#7325517390736006 2. Select to share the whole desktop in the xdg-desktop-portal 3. Notice the orange screen share indicator in Gnome-Shell but actually nothing is shared in the browser. This should be handled high priority since this is a critical feature during the pandemic. Filed against ubuntu-meta since I don't know exactly which package to blame, whether it's pipewire, xdg-desktop portal or some problem directely with mutter / gnome-shell, please reassign accordingly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1950040/+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 1963767] Re: [jammy] Microphone not working after suspend
Did you test he same webcam as I did (Logitech BRIO)? If it happens for me with two laptops from different manufacturers that have different processors (Intel vs AMD), there is certainly something going on. It happened on 21.10 and now happns on 22.04 LTS version of Ubuntu, so the bug report should be valid IMHO. Thankfully I'm not using laptop actively, it is a really bad experience. -- 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/1963767 Title: [jammy] Microphone not working after suspend Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: Incomplete Bug description: I have Logitech BRIO 4k Pro webcam connected via its USB cable to Asus Vivobook Pro 16X OLED M7600QE-L2014X (90NB0V71-M02190) laptop. On Ubuntu 21.10 after suspend (`systemctl suspend`) webcam's microphone stops working (device is still there, but audio level is at zero all the time). To make it work again I need to do 2 things (just one is not sufficient): 1) Disconnect and connect webcam again to the laptop 2) Restart pulseaudio with `pulseaudio --kill; pulseaudio --start` Not sure whose fault it is, likely kernel driver, but the fact that pulseaudio needs to be restarted is concerning as well. Reproducible 100% for me. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: Custom DistroRelease: Ubuntu 21.10 Package: pulseaudio 1:15.0+dfsg1-1ubuntu2.2 PackageArchitecture: amd64 Tags: impish Uname: Linux 5.16.11-xanmod1 x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip docker libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nazar-pc 1488 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-02-15 (153 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04ca:300d Lite-On Technology Corp. Atheros AR3012 Bluetooth Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M |__ Port 3: Dev 3, If 0, Class=Wireless, Driver=btusb, 12M |__ Port 3: Dev 3, If 1, Class=Wireless, Driver=btusb, 12M MachineType: Purism Librem 13 v4 Package: pulseaudio 1:15.99.1+dfsg1-1ubuntu1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=uk_UA.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-39-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-39.42-generic 5.15.35 RelatedPackageVersions: linux-restricted-modules-5.15.0-39-generic N/A linux-backports-modules-5.15.0-39-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.2 Tags: jammy wayland-session wayland-session Uname: Linux 5.15.0-39-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-06-21 (27 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/27/2022 dmi.bios.release: 4.15 dmi.bios.vendor: coreboot dmi.bios.version: 4.15-Purism-3 dmi.board.name: Librem 13 v4 dmi.board.vendor: Purism dmi.board.version: 1.0 dmi.chassis.type: 9 dmi.chassis.vendor: Purism dmi.ec.firmware.release: 0.0 dmi.modalias: dmi:bvncoreboot:bvr4.15-Purism-3:bd01/27/2022:br4.15:efr0.0:svnPurism:pnLibrem13v4:pvr1.0:rvnPurism:rnLibrem13v4:rvr1.0:cvnPurism:ct9:cvr:sku: dmi.product.family: Librem 13 dmi.product.name: Librem 13 v4 dmi.product.version: 1.0 dmi.sys.vendor: Purism To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1963767/+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 1995416] Re: lmdb is out of date - please update to 0.9.29
** Changed in: lmdb (Debian) Status: Unknown => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lmdb in Ubuntu. https://bugs.launchpad.net/bugs/1995416 Title: lmdb is out of date - please update to 0.9.29 Status in lmdb package in Ubuntu: New Status in lmdb package in Debian: New Bug description: Subject says it all. Is it possible to report out-of-date packages in another way that a bugreport ? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lmdb/+bug/1995416/+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 1968887] Re: Save As Dialog Box does not get focus in Ubuntu 22.04
*** This bug is a duplicate of bug 1949340 *** https://bugs.launchpad.net/bugs/1949340 I don't think this is a duplicate of the upstream bug report, because that's about Chromium, and this also affects Firefox. For anyone else who ends up here and just wants to fix their UI in Firefox, open "about:config" and set "widget.use-xdg-desktop- portal.file-picker" to 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/1968887 Title: Save As Dialog Box does not get focus in Ubuntu 22.04 Status in gnome-shell package in Ubuntu: Confirmed Bug description: When using a browser to right click a file and save as, the save as window does not get focus, which means you can't just type the name of the file you want, you have to force focus onto the window to use it by clicking it. This defeats the entire purpose of 2 built in features, 1 being the pre-selected original file name (since you can't rename until you re- aquire focus for that window, thereby undoing the pre-selection programmed in) and 2, the ability to quickly save the file with a keystroke. A side note to this, ubuntu-bug should have an option to report bugs with other WITHOUT having to specify a package. This is a bug in ubuntu-bug. Not a feature. Because we don't always know what package(s) are involved. This needs to be addressed. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubuntu-release-upgrader-core 1:22.04.8 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu81 Architecture: amd64 CasperMD5CheckResult: pass CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Wed Apr 13 07:55:24 2022 InstallationDate: Installed on 2022-03-31 (12 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1968887/+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
