[Desktop-packages] [Bug 1964542] Re: [nvidia] One monitor remains black on startup or resume from sleep
Maybe try enabling Wayland and then see if logging into 'Ubuntu on Wayland' avoids the problem. To enable Wayland you will need to change the kernel parameter: nomodeset to: nvidia-drm.modeset=1 and then run: sudo update-grub and reboot. -- 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/1964542 Title: [nvidia] One monitor remains black on startup or resume from sleep Status in mutter package in Ubuntu: New Status in nvidia-graphics-drivers-470 package in Ubuntu: New Bug description: when the pc starts up or comes out of sleep mode the primary screen remains black. To reactivate it I have to go through screen clone apply and redo join the screens and apply. Thanks Ps: have done several research and attempt, without success, on the internet including in your forums. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: xorg 1:7.7+22ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-35.40-generic 5.13.19 Uname: Linux 5.13.0-35-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..02.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 non accordée: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Mar 10 18:45:17 2022 DistUpgraded: 2022-02-23 17:47:37,810 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: impish DistroVariant: ubuntu DkmsStatus: nvidia, 470.103.01, 5.13.0-32-generic, x86_64: installed nvidia, 470.103.01, 5.13.0-35-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GM206 [GeForce GTX 960] [10de:1401] (rev a1) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. GM206 [GeForce GTX 960] [3842:2966] InstallationDate: Installed on 2022-02-15 (23 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) MachineType: ASUS All Series ProcEnviron: LANGUAGE=fr_CA:fr PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_CA.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-35-generic root=UUID=c8e08c76-0308-495c-8c5a-83f9aa24b1a0 ro quiet splash nomodeset vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to impish on 2022-02-23 (15 days ago) dmi.bios.date: 07/10/2019 dmi.bios.release: 5.11 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4101 dmi.board.asset.tag: Default string dmi.board.name: SABERTOOTH X99 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.:bvr4101:bd07/10/2019:br5.11:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnSABERTOOTHX99:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuAll: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.sku: All dmi.product.version: System Version dmi.sys.vendor: ASUS 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 N/A 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: xserver-xorg-video-nouveau 1:1.0.17-1build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1964542/+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 1964542] Re: [nvidia] One monitor remains black on startup or resume from sleep
Is it the IBM or the LG monitor that remains black? I can't see any hints of a problem in the log. It sounds like maybe GNOME can't uniquely identify one of the monitors and so can't remember its preferred setting. ** Also affects: mutter (Ubuntu) Importance: Undecided Status: New -- 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/1964542 Title: [nvidia] One monitor remains black on startup or resume from sleep Status in mutter package in Ubuntu: New Status in nvidia-graphics-drivers-470 package in Ubuntu: New Bug description: when the pc starts up or comes out of sleep mode the primary screen remains black. To reactivate it I have to go through screen clone apply and redo join the screens and apply. Thanks Ps: have done several research and attempt, without success, on the internet including in your forums. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: xorg 1:7.7+22ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-35.40-generic 5.13.19 Uname: Linux 5.13.0-35-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..02.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 non accordée: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Mar 10 18:45:17 2022 DistUpgraded: 2022-02-23 17:47:37,810 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: impish DistroVariant: ubuntu DkmsStatus: nvidia, 470.103.01, 5.13.0-32-generic, x86_64: installed nvidia, 470.103.01, 5.13.0-35-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GM206 [GeForce GTX 960] [10de:1401] (rev a1) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. GM206 [GeForce GTX 960] [3842:2966] InstallationDate: Installed on 2022-02-15 (23 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) MachineType: ASUS All Series ProcEnviron: LANGUAGE=fr_CA:fr PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_CA.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-35-generic root=UUID=c8e08c76-0308-495c-8c5a-83f9aa24b1a0 ro quiet splash nomodeset vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to impish on 2022-02-23 (15 days ago) dmi.bios.date: 07/10/2019 dmi.bios.release: 5.11 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4101 dmi.board.asset.tag: Default string dmi.board.name: SABERTOOTH X99 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.:bvr4101:bd07/10/2019:br5.11:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnSABERTOOTHX99:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuAll: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.sku: All dmi.product.version: System Version dmi.sys.vendor: ASUS 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 N/A 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: xserver-xorg-video-nouveau 1:1.0.17-1build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1964542/+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 1964711] Re: Locked Ubuntu is frozen and cannot be unlocked
Thank you for taking the time to report this bug and helping to make Ubuntu better. You've not given details as to your actual install; was it a Ubuntu Desktop 20.04 LTS or Ubuntu Server 20.04 LTS? You do mention moving mouse; a device not normally attached to servers, so I'm assume (rightly/wrongly) you're asking about a desktop system - but it's best if these details are provided. Please execute the following command only once, as it will automatically gather debugging information, in a terminal: apport-collect 1964711 When reporting bugs in the future please use apport by using 'ubuntu- bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs. (Note: this issue could be related to https://bugs.launchpad.net/bugs/1851992) ** Package changed: ubuntu => gdm3 (Ubuntu) -- 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/1964711 Title: Locked Ubuntu is frozen and cannot be unlocked Status in gdm3 package in Ubuntu: New Bug description: After locking Ubuntu and leaving it unattended for a while, the operating system cannot be unlocked anymore. No means of user input (e.g. typing on the keyboard, moving the mouse) produce the lock screen and I have to shut down my computer by pressing down the power button. The attached monitor does not receive a signal from the computer during these attempts. This started to happen several weeks ago and worked without a problem before then. Due to the nature of this issue, I can neither report any errors occurring nor can I observe any other out of the ordinary things from happening. Thus, I don’t know which package is causing the issue. Also, this issue happens every time I leave the computer unattended for a longer time and lock it. However, locking it and triggering an input immediately after does produce the lock screen, so the lock screen seems to work in principle. Description: Ubuntu 20.04.4 LTS Release: 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1964711/+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 1964711] [NEW] Locked Ubuntu is frozen and cannot be unlocked
You have been subscribed to a public bug: After locking Ubuntu and leaving it unattended for a while, the operating system cannot be unlocked anymore. No means of user input (e.g. typing on the keyboard, moving the mouse) produce the lock screen and I have to shut down my computer by pressing down the power button. The attached monitor does not receive a signal from the computer during these attempts. This started to happen several weeks ago and worked without a problem before then. Due to the nature of this issue, I can neither report any errors occurring nor can I observe any other out of the ordinary things from happening. Thus, I don’t know which package is causing the issue. Also, this issue happens every time I leave the computer unattended for a longer time and lock it. However, locking it and triggering an input immediately after does produce the lock screen, so the lock screen seems to work in principle. Description:Ubuntu 20.04.4 LTS Release:20.04 ** Affects: gdm3 (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment -- Locked Ubuntu is frozen and cannot be unlocked https://bugs.launchpad.net/bugs/1964711 You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdm3 in Ubuntu. -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1964684] Re: Yaru (battery) icons in Power Statistics do not show correctly
** Also affects: gnome-power-manager (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to yaru-theme in Ubuntu. https://bugs.launchpad.net/bugs/1964684 Title: Yaru (battery) icons in Power Statistics do not show correctly Status in gnome-power-manager package in Ubuntu: New Status in yaru-theme package in Ubuntu: New Bug description: Yaru (battery) icons in Power Statistics do not show correctly. Some are not visible to the white background. See attached screenshot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/1964684/+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 1388491] Re: [upstream] calc: "Cut" and "Paste special" -> "Transpose" affects other cells
** Changed in: libreoffice (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1388491 Title: [upstream] calc: "Cut" and "Paste special" -> "Transpose" affects other cells Status in LibreOffice: Fix Released Status in libreoffice package in Ubuntu: Fix Released Bug description: Step to reproduce: 1. Open the attached ods file. 2. Select I12 to L16 and cut this region (Ctrl+X). (This bug doesn't occur with copy) 3. Select I5 and open Paste Special dialog (Shift+Ctrl+V). 4. Enable "Transpose" option and Click "OK" Then, values of some cells in C9 to E10, which are not related to blank cells are changed: C9: =C3/SUM(C$3:C$6) -> K7/SUM(C$3:C$6) D9: =D3/SUM(D$3:D$6) -> L7/SUM(D$3:D6) E9: =E3/SUM(E$3:E$6) -> M7/SUM(E$3:E$6) C10: =C4/SUM(C$3:C$6) -> K8/SUM(C$3:C$6) D10: =D4/SUM(D$3:D$6) -> L8/SUM(D$3:D6) E10: =E4/SUM(E$3:E$6) -> M8/SUM(E$3:E$6) My environment is Ubuntu 14.04 LibreOffice 4.2.6.3 To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1388491/+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 1889051] Re: Unreachable options
*** This bug is a duplicate of bug 1870564 *** https://bugs.launchpad.net/bugs/1870564 ** This bug has been marked a duplicate of bug 1870564 Libreoffice's "Customize" dialog is too big in Ubuntu 19.10 -- 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/1889051 Title: Unreachable options Status in libreoffice package in Ubuntu: New Bug description: Proof: https://webmshare.com/qda19 What I am doing in "Screen Record"? Ans: I am trying to Save the Keyboard Shortkey that I created for Insert. But sadly 3 options which say "Reset", "Cancel" and "Ok" are hidden down below. Neither I can touch it by dragging my Window around, nor I can save this shortkey. Distro: Ubuntu 20.04 LibreOffice Writer Version: 6.4.4.2 Display Server: Wayland GNOME: 3.36.3 What to do? ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libreoffice-writer 1:6.4.4-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Jul 27 13:52:26 2020 InstallationDate: Installed on 2020-02-16 (162 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: libreoffice UpgradeStatus: Upgraded to focal on 2020-05-08 (80 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1889051/+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
** Changed in: libreoffice (Ubuntu) Status: Triaged => In Progress -- 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: In Progress 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 1962327] Re: VERTICAL FRACTION FEATURE PRESENT IN FONT NOT APPLIED BY WRITER
** Changed in: libreoffice (Ubuntu) Status: Confirmed => Triaged ** Changed in: libreoffice (Ubuntu) Importance: Undecided => Medium ** Summary changed: - VERTICAL FRACTION FEATURE PRESENT IN FONT NOT APPLIED BY WRITER + [Upstream] Vertical fraction feature present in font not applied by Writer -- 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/1962327 Title: [Upstream] Vertical fraction feature present in font not applied by Writer Status in libreoffice package in Ubuntu: Triaged Bug description: ~ $ lsb_release -rd Description: Ubuntu 20.04.3 LTS Release: 20.04 ~$ apt-cache policy libreoffice-writer libreoffice-writer: Installed: 1:6.4.7-0ubuntu0.20.04.2 Candidate: 1:6.4.7-0ubuntu0.20.04.2 Version table: *** 1:6.4.7-0ubuntu0.20.04.2 500 500 http://security.ubuntu.com/ubuntu focal-security/main amd64 Packages 100 /var/lib/dpkg/status 1:6.4.2-0ubuntu3 500 500 http://in.archive.ubuntu.com/ubuntu focal/main amd64 Packages ~$ apt-show-versions -r libreoffice* liblibreofficekitgtk:amd64/focal-security 1:6.4.7-0ubuntu0.20.04.2 uptodate libreoffice-base-core:amd64/focal-security 1:6.4.7-0ubuntu0.20.04.2 uptodate libreoffice-calc:amd64/focal-security 1:6.4.7-0ubuntu0.20.04.2 uptodate libreoffice-common:all/focal-security 1:6.4.7-0ubuntu0.20.04.2 uptodate libreoffice-core:amd64/focal-security 1:6.4.7-0ubuntu0.20.04.2 uptodate libreoffice-draw:amd64/focal-security 1:6.4.7-0ubuntu0.20.04.2 uptodate libreoffice-gnome:amd64/focal-security 1:6.4.7-0ubuntu0.20.04.2 uptodate libreoffice-gtk:all/focal-security 1:6.4.7-0ubuntu0.20.04.2 uptodate libreoffice-gtk2:all/focal-security 1:6.4.7-0ubuntu0.20.04.2 uptodate libreoffice-gtk3:amd64/focal-security 1:6.4.7-0ubuntu0.20.04.2 uptodate libreoffice-impress:amd64/focal-security 1:6.4.7-0ubuntu0.20.04.2 uptodate libreoffice-java-common:all/focal-security 1:6.4.7-0ubuntu0.20.04.2 uptodate libreoffice-l10n-bn:all/focal-security 1:6.4.7-0ubuntu0.20.04.2 uptodate libreoffice-math:amd64/focal-security 1:6.4.7-0ubuntu0.20.04.2 uptodate libreoffice-style-colibre:all/focal-security 1:6.4.7-0ubuntu0.20.04.2 uptodate libreoffice-style-elementary:all/focal-security 1:6.4.7-0ubuntu0.20.04.2 uptodate libreoffice-style-tango:all/focal-security 1:6.4.7-0ubuntu0.20.04.2 uptodate libreoffice-writer:amd64/focal-security 1:6.4.7-0ubuntu0.20.04.2 uptodate libreofficekit-data:all/focal-security 1:6.4.7-0ubuntu0.20.04.2 uptodate What is expected to happen in Writer is My font has vertical fraction look up for Bengali script. On selecting Format > Characters > CTL Font > Features Alternate (vertical) Fraction Feature is visible in options. Selecting the option should apply the feature on selected fraction see screenshot http://cloud.atipra.in/index.php/s/YosGiyFSoTQeW8i What happened instead is.. The feature is not applied, and the selected text is unchanged It should change as happens in firefox on selecting alternate (Vertical) fraction lookup in css see screenshot http://cloud.atipra.in/index.php/s/MxYbEisyFT3KnKT Extension installed : None ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libreoffice-writer 1:6.4.7-0ubuntu0.20.04.2 ProcVersionSignature: Ubuntu 5.4.0-100.113-generic 5.4.166 Uname: Linux 5.4.0-100-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Feb 25 20:33:24 2022 InstallationDate: Installed on 2020-01-03 (783 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: libreoffice UpgradeStatus: Upgraded to focal on 2021-09-16 (162 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1962327/+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 1964393] Re: gnome-shell crashed with assertion failure in meta_kms_update_set_power_save: !update->plane_assignments
That's great, but: (a) When you reported this bug in GNOME 41 you didn't have the triple buffering feature (libmutter-9-0 41.3-3ubuntu1); and (b) If you are using jammy-proposed then even that (mutter 42~beta-1ubuntu2) does not yet have the MUTTER_DEBUG_DISABLE_TRIPLE_BUFFERING feature. So it sounds like *introducing* triple buffering has fixed the problem for you. I suspected that might happen thanks to https://gitlab.gnome.org/GNOME/mutter/-/commit/163776ae49f Or you might just be lucky and the problem may come back... We'll have a better idea after Ubuntu 22.04 is released to a wider audience. -- 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/1964393 Title: gnome-shell crashed with assertion failure in meta_kms_update_set_power_save: !update->plane_assignments Status in gnome-shell package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: I think the crash occurs when turning the screen blank after idle time. ProblemType: Crash DistroRelease: Ubuntu 22.04 Package: gnome-shell 41.3-1ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19 Uname: Linux 5.15.0-22-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 CasperMD5CheckResult: pass CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Wed Mar 9 19:11:12 2022 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2022-02-26 (10 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220226) ProcCmdline: /usr/bin/gnome-shell RelatedPackageVersions: mutter-common 41.3-3ubuntu1 Signal: 6 SourcePackage: gnome-shell StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libmutter-9.so.0 ?? () from /lib/x86_64-linux-gnu/libmutter-9.so.0 g_closure_invoke () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: gnome-shell crashed with SIGABRT in g_assertion_message_expr() 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/1964393/+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 1944113]
*** Bug 147957 has been marked as a duplicate of this bug. *** -- 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/1944113 Title: Many UI elements (list box, drop down) don't work at all in kf5 environment Status in LibreOffice: Confirmed Status in libreoffice package in Ubuntu: Fix Released Bug description: Many UI elements (list box, drop down) don't work at all in kf5 environment. This makes LO unusable. For example, try to insert a table from standard toolbar in LO Writer – nothing inserted. Same happens with other drop down elements (styles, font family, font size, font color, font highlight, etc). Bug reports at LO's bug tracker: https://bugs.documentfoundation.org/show_bug.cgi?id=144037 https://bugs.documentfoundation.org/show_bug.cgi?id=144562 https://gerrit.libreoffice.org/c/core/+/122116 Operating System: Kubuntu 20.04 KDE Plasma Version: 5.18.5 KDE Frameworks Version: 5.68.0 Qt Version: 5.12.8 Kernel Version: 5.11.0-34-generic OS Type: 64-bit Processors: 4 × Intel® Core™ i5-4310U CPU @ 2.00GHz Memory: 7,7 GiB Version: 7.2.1.2 / LibreOffice Community Build ID: 20(Build:2) CPU threads: 4; OS: Linux 5.11; UI render: default; VCL: kf5 (cairo+xcb) Locale: hu-HU (hu_HU.UTF-8); UI: hu-HU Ubuntu package version: 1:7.2.1~rc2-0ubuntu0.20.04.1~lo3 Calc: threaded To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1944113/+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 1964675] Re: Window dragging lag when rendering 3d objects. (GNOME 42, NVIDIA, glxgear, pymol)
This sounds like a continuation of Nvidia bug 1799679. Please test regular Ubuntu 22.04 (GNOME 41) and/or Ubuntu 21.10 (GNOME 40) and tell us if the same problem exists there. I just want to confirm it's not a new problem in GNOME 42 here. ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete -- 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/1964675 Title: Window dragging lag when rendering 3d objects. (GNOME 42, NVIDIA, glxgear, pymol) Status in gnome-shell package in Ubuntu: Incomplete Bug description: OS/software: Ubuntu Jammy Jellyfish (development branch), GNOME 42.beta, X11, NVIDIA-driver-510 (510.54) Hardware: Intel® Xeon(R) CPU E5-1650 v2 @ 3.50GHz × 12, 31,3 GiB RAM, NVIDIA Corporation GP106 [GeForce GTX 1060 6GB] How to reproduce: open glxgear, on the same workspace, move any window, there is badly dragging lag. But there is no lag if move window on a different workspace. CPU/GPU usages are normal (<3%). Disable Sync to VBlank in NVIDIA Settings can solve this issue, but CPU/GPU usages are abornmally high (single core CPU>80%, GPU>10% only for glxgear). Both NVIDIA-driver-510 and NVIDIA-driver-470 have the same issue. But another Intel-GPU based laptop works fine. This is not a glxgear bug, as other realtime 3D rendering (PyMOL, Blender...) casue the same issue. Possible reasons I guess: NVIDIA driver bug, kernel bug, or GNOME 42 bug. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1964675/+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 1959888] Re: Wayland sessions can't use external monitors that are connected to an Nvidia GPU with the proprietary driver
Proof of concept workaround/fix: https://gitlab.gnome.org/vanvugt/mutter/-/commit/8c57fd13766c74007c696a0fbb74f1b2a89ff099 But even when finished it will be a little slow. We're waiting for Nvidia to update their driver such that the GBM API doesn't fail when it's the secondary GPU. Until then we should probably default to Xorg so that all monitors work with reasonable performance. -- 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/1959888 Title: Wayland sessions can't use external monitors that are connected to an Nvidia GPU with the proprietary driver Status in Mutter: Unknown Status in mutter package in Ubuntu: In Progress Bug description: When an external display is connected to my laptop, running Ubuntu 22.04, the display is detected and I am sent to the login screen. After logging in again, the display is not running, although the primary laptop display works fine. The external monitor is looking for connection in that moment, which it never founds. The bug is tested on two Samsung monitors: S24R350FHUXEN and S22F350FHU. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Uname: Linux 5.15.0-18-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 495.46 Wed Oct 27 16:31:33 UTC 2021 GCC version: gcc version 11.2.0 (Ubuntu 11.2.0-14ubuntu1) ApportVersion: 2.20.11-0ubuntu76 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Feb 3 13:25:04 2022 DistUpgraded: 2022-01-13 15:37:13,056 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: nvidia/495.46, 5.15.0-17-generic, x86_64: installed nvidia/495.46, 5.15.0-18-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation CoffeeLake-H GT2 [UHD Graphics 630] [8086:3e9b] (prog-if 00 [VGA controller]) Subsystem: Dell CoffeeLake-H GT2 [UHD Graphics 630] [1028:086f] Subsystem: Dell GP107M [GeForce GTX 1050 Ti Mobile] [1028:086f] InstallationDate: Installed on 2021-09-09 (146 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: Dell Inc. G3 3579 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-18-generic root=UUID=fd3be223-e609-4a8d-97fb-31ee2f754766 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to jammy on 2022-01-13 (20 days ago) dmi.bios.date: 04/20/2021 dmi.bios.release: 1.15 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.15.0 dmi.board.name: 0M5H57 dmi.board.vendor: Dell Inc. dmi.board.version: A05 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.15.0:bd04/20/2021:br1.15:svnDellInc.:pnG33579:pvr:rvnDellInc.:rn0M5H57:rvrA05:cvnDellInc.:ct10:cvr:sku086F: dmi.product.family: GSeries dmi.product.name: G3 3579 dmi.product.sku: 086F dmi.sys.vendor: Dell Inc. nvidia-settings: ERROR: Unable to find display on any available system ERROR: Unable to find display on any available system version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.109-2ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 21.2.2-1ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.14-1ubuntu1 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: xserver-xorg-video-nouveau 1:1.0.17-1build1 To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1959888/+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 1962679] Re: Take screenshot in Totem does not work
** Summary changed: - take screenshot does not work + Take screenshot in Totem does not work -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1962679 Title: Take screenshot in Totem does not work Status in Totem: Unknown Status in totem package in Ubuntu: Fix Committed Bug description: playing an .avi video i select 'take screensot' and i have a small window with a message 'Totem could not get a screenshot of the video. This is not supposed to happen; please file a bug report'corrado@corrado-p5-jj-0203:~$ inxi -SGx System: Host: corrado-p5-jj-0203 Kernel: 5.15.0-18-generic x86_64 bits: 64 compiler: gcc v: 11.2.0 Desktop: GNOME 41.3 Distro: Ubuntu 22.04 (Jammy Jellyfish) Graphics: Device-1: Intel 4th Generation Core Processor Family Integrated Graphics vendor: Gigabyte driver: i915 v: kernel bus-ID: 00:02.0 Display: wayland server: X.Org v: 1.22.1 with: Xwayland v: 22.1.0 compositor: gnome-shell driver: X: loaded: modesetting unloaded: fbdev,vesa gpu: i915 resolution: 1680x1050~60Hz OpenGL: renderer: Mesa DRI Intel HD Graphics 4400 (HSW GT2) v: 4.5 Mesa 21.2.2 direct render: Yes corrado@corrado-p5-jj-0203:~$ ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: totem 41~alpha~20220222-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-0ubuntu78 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Mar 2 06:26:15 2022 InstallationDate: Installed on 2022-02-08 (21 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220202) SourcePackage: totem UpgradeStatus: No upgrade log present (probably fresh install) XorgLog: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log' To manage notifications about this bug go to: https://bugs.launchpad.net/totem/+bug/1962679/+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 1964678] Re: gnome-shell crashed with SIGSEGV in g_type_check_instance_cast() from st_entry_get_text() from gnome-clipbo...@b00f.github.io/searchBox.js:22
** Summary changed: - gnome-shell crashed with SIGSEGV in g_type_check_instance_cast() from st_entry_get_text() from ffi_call_unix64() + gnome-shell crashed with SIGSEGV in g_type_check_instance_cast() from st_entry_get_text() from gnome-clipbo...@b00f.github.io/searchBox.js:22 ** Summary changed: - gnome-shell crashed with SIGSEGV in g_type_check_instance_cast() from st_entry_get_text() from gnome-clipbo...@b00f.github.io/searchBox.js:22 + gnome-shell crashed with SIGSEGV in g_type_check_instance_cast() from st_entry_get_text() from ffi_call_unix64() [gnome-clipbo...@b00f.github.io/searchBox.js:22] -- 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/1964678 Title: gnome-shell crashed with SIGSEGV in g_type_check_instance_cast() from st_entry_get_text() from ffi_call_unix64() [gnome- clipbo...@b00f.github.io/searchBox.js:22] Status in gnome-shell package in Ubuntu: Invalid Bug description: https://errors.ubuntu.com/problem/0a44a1b3318d644c23879475d2fd975d86d0d665 --- gnome-shell crashed while window switching ProblemType: Crash DistroRelease: Ubuntu 22.04 Package: gnome-shell 41.3-1ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19 Uname: Linux 5.15.0-22-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Mar 12 18:51:29 2022 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2022-03-11 (1 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220310) ProcCmdline: /usr/bin/gnome-shell RelatedPackageVersions: mutter-common 41.3-3ubuntu1 Signal: 11 SourcePackage: gnome-shell StacktraceTop: g_type_check_instance_cast () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 st_entry_get_text () from /usr/lib/gnome-shell/libst-1.0.so ?? () from /lib/x86_64-linux-gnu/libffi.so.8 ?? () from /lib/x86_64-linux-gnu/libffi.so.8 ?? () from /lib/x86_64-linux-gnu/libgjs.so.0 Title: gnome-shell crashed with SIGSEGV in g_type_check_instance_cast() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1964678/+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 1948877] Re: Bluetooth headphones media buttons no longer work
** Changed in: bluez (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1948877 Title: Bluetooth headphones media buttons no longer work Status in bluez package in Ubuntu: Fix Released Bug description: In KUbuntu 21.10, most media buttons in my bluetooth headphones stopped working. This includes the "play/pause" button, "play next" (calls after long press of volume increase), and "play previous" (long press of volume decrease). The volume +/- buttons themselves are working, but this seemingly is implemented entirely in the headphones and does not require any communication over bluetooth. In previous ubuntu (21.04) these buttons worked, and I expect them working. My headset is Qumo Accord 3. Here is output of "inxi -Eaz" in terminal: Bluetooth: Device-1: Realtek Bluetooth Radio type: USB driver: btusb v: 0.8 bus-ID: 1-7:3 chip-ID: 0bda:b008 class-ID: e001 serial: Report: hciconfig ID: hci0 rfk-id: 1 state: up address: bt-v: 2.1 lmp-v: 4.0 sub-v: 9f73 hci-v: 4.0 rev: e2f Info: acl-mtu: 820:8 sco-mtu: 255:16 link-policy: rswitch hold sniff park link-mode: slave accept service-classes: rendering, capturing, object transfer, audio, telephony Some possible workarounds that I found suggest to "modprobe uinput", but the uinput module does not get loaded (lsmod does not list it even after modprobe'ing). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1948877/+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 1964678] Re: gnome-shell crashed with SIGSEGV in g_type_check_instance_cast() from st_entry_get_text() from ffi_call_unix64()
The crash is in your extension: /home/ravage/.local/share/gnome- shell/extensions/gnome-clipbo...@b00f.github.io [74412.043807] esport gnome-shell[7855]: GNOME Shell crashed with signal 11 [74412.043807] esport gnome-shell[7855]: == Stack trace for context 0x55b8b5203170 == [74412.043807] esport gnome-shell[7855]: #0 55b8c3907310 i /home/ravage/.local/share/gnome-shell/extensions/gnome-clipbo...@b00f.github.io/searchBox.js:22 (3ea4a7bb56f0 @ 22) [74412.043807] esport gnome-shell[7855]: #1 55b8c3907278 i /home/ravage/.local/share/gnome-shell/extensions/gnome-clipbo...@b00f.github.io/clipboardPanel.js:114 (b13d51ea100 @ 28) [74412.043807] esport gnome-shell[7855]: #2 55b8c39071d8 i /home/ravage/.local/share/gnome-shell/extensions/gnome-clipbo...@b00f.github.io/clipboardPanel.js:157 (b13d51ea290 @ 138) [74412.043807] esport gnome-shell[7855]: #3 55b8c3907148 i /home/ravage/.local/share/gnome-shell/extensions/gnome-clipbo...@b00f.github.io/clipboardPanel.js:190 (b13d51ea420 @ 66) ** Description changed: + https://errors.ubuntu.com/problem/0a44a1b3318d644c23879475d2fd975d86d0d665 + + --- + gnome-shell crashed while window switching ProblemType: Crash DistroRelease: Ubuntu 22.04 Package: gnome-shell 41.3-1ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19 Uname: Linux 5.15.0-22-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Mar 12 18:51:29 2022 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2022-03-11 (1 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220310) ProcCmdline: /usr/bin/gnome-shell RelatedPackageVersions: mutter-common 41.3-3ubuntu1 Signal: 11 SourcePackage: gnome-shell StacktraceTop: - g_type_check_instance_cast () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 - st_entry_get_text () from /usr/lib/gnome-shell/libst-1.0.so - ?? () from /lib/x86_64-linux-gnu/libffi.so.8 - ?? () from /lib/x86_64-linux-gnu/libffi.so.8 - ?? () from /lib/x86_64-linux-gnu/libgjs.so.0 + g_type_check_instance_cast () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 + st_entry_get_text () from /usr/lib/gnome-shell/libst-1.0.so + ?? () from /lib/x86_64-linux-gnu/libffi.so.8 + ?? () from /lib/x86_64-linux-gnu/libffi.so.8 + ?? () from /lib/x86_64-linux-gnu/libgjs.so.0 Title: gnome-shell crashed with SIGSEGV in g_type_check_instance_cast() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo separator: ** Changed in: gnome-shell (Ubuntu) Status: Confirmed => Invalid -- 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/1964678 Title: gnome-shell crashed with SIGSEGV in g_type_check_instance_cast() from st_entry_get_text() from ffi_call_unix64() [gnome- clipbo...@b00f.github.io/searchBox.js:22] Status in gnome-shell package in Ubuntu: Invalid Bug description: https://errors.ubuntu.com/problem/0a44a1b3318d644c23879475d2fd975d86d0d665 --- gnome-shell crashed while window switching ProblemType: Crash DistroRelease: Ubuntu 22.04 Package: gnome-shell 41.3-1ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19 Uname: Linux 5.15.0-22-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Mar 12 18:51:29 2022 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2022-03-11 (1 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220310) ProcCmdline: /usr/bin/gnome-shell RelatedPackageVersions: mutter-common 41.3-3ubuntu1 Signal: 11 SourcePackage: gnome-shell StacktraceTop: g_type_check_instance_cast () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 st_entry_get_text () from /usr/lib/gnome-shell/libst-1.0.so ?? () from /lib/x86_64-linux-gnu/libffi.so.8 ?? () from /lib/x86_64-linux-gnu/libffi.so.8 ?? () from /lib/x86_64-linux-gnu/libgjs.so.0 Title: gnome-shell crashed with SIGSEGV in g_type_check_instance_cast() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1964678/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help :
[Desktop-packages] [Bug 1964678] Re: gnome-shell crashed with SIGSEGV in g_type_check_instance_cast() from st_entry_get_text() from ffi_call_unix64()
** Summary changed: - gnome-shell crashed with SIGSEGV in g_type_check_instance_cast() + gnome-shell crashed with SIGSEGV in g_type_check_instance_cast() from st_entry_get_text() from ffi_call_unix64() -- 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/1964678 Title: gnome-shell crashed with SIGSEGV in g_type_check_instance_cast() from st_entry_get_text() from ffi_call_unix64() Status in gnome-shell package in Ubuntu: Invalid Bug description: https://errors.ubuntu.com/problem/0a44a1b3318d644c23879475d2fd975d86d0d665 --- gnome-shell crashed while window switching ProblemType: Crash DistroRelease: Ubuntu 22.04 Package: gnome-shell 41.3-1ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19 Uname: Linux 5.15.0-22-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Mar 12 18:51:29 2022 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2022-03-11 (1 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220310) ProcCmdline: /usr/bin/gnome-shell RelatedPackageVersions: mutter-common 41.3-3ubuntu1 Signal: 11 SourcePackage: gnome-shell StacktraceTop: g_type_check_instance_cast () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 st_entry_get_text () from /usr/lib/gnome-shell/libst-1.0.so ?? () from /lib/x86_64-linux-gnu/libffi.so.8 ?? () from /lib/x86_64-linux-gnu/libffi.so.8 ?? () from /lib/x86_64-linux-gnu/libgjs.so.0 Title: gnome-shell crashed with SIGSEGV in g_type_check_instance_cast() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1964678/+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 1964678] Re: gnome-shell crashed with SIGSEGV in g_type_check_instance_cast() from st_entry_get_text() from ffi_call_unix64()
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/1964678 Title: gnome-shell crashed with SIGSEGV in g_type_check_instance_cast() from st_entry_get_text() from ffi_call_unix64() Status in gnome-shell package in Ubuntu: Invalid Bug description: https://errors.ubuntu.com/problem/0a44a1b3318d644c23879475d2fd975d86d0d665 --- gnome-shell crashed while window switching ProblemType: Crash DistroRelease: Ubuntu 22.04 Package: gnome-shell 41.3-1ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19 Uname: Linux 5.15.0-22-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Mar 12 18:51:29 2022 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2022-03-11 (1 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220310) ProcCmdline: /usr/bin/gnome-shell RelatedPackageVersions: mutter-common 41.3-3ubuntu1 Signal: 11 SourcePackage: gnome-shell StacktraceTop: g_type_check_instance_cast () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 st_entry_get_text () from /usr/lib/gnome-shell/libst-1.0.so ?? () from /lib/x86_64-linux-gnu/libffi.so.8 ?? () from /lib/x86_64-linux-gnu/libffi.so.8 ?? () from /lib/x86_64-linux-gnu/libgjs.so.0 Title: gnome-shell crashed with SIGSEGV in g_type_check_instance_cast() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1964678/+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 1964734] Re: /usr/bin/gnome-shell:11:g_type_check_instance_cast:st_entry_get_text:ffi_call_unix64:ffi_call_int:Gjs::Function::invoke
*** This bug is a duplicate of bug 1964678 *** https://bugs.launchpad.net/bugs/1964678 ** This bug has been marked a duplicate of bug 1964678 gnome-shell crashed with SIGSEGV in g_type_check_instance_cast() from st_entry_get_text() from ffi_call_unix64() -- 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/1964734 Title: /usr/bin/gnome- shell:11:g_type_check_instance_cast:st_entry_get_text:ffi_call_unix64:ffi_call_int:Gjs::Function::invoke Status in gnome-shell package in Ubuntu: New 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 41.3-1ubuntu1, the problem page at https://errors.ubuntu.com/problem/0a44a1b3318d644c23879475d2fd975d86d0d665 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/ubuntu/+source/gnome-shell/+bug/1964734/+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 1964734] [NEW] /usr/bin/gnome-shell:11:g_type_check_instance_cast:st_entry_get_text:ffi_call_unix64:ffi_call_int:Gjs::Function::invoke
*** This bug is a duplicate of bug 1964678 *** https://bugs.launchpad.net/bugs/1964678 Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 41.3-1ubuntu1, the problem page at https://errors.ubuntu.com/problem/0a44a1b3318d644c23879475d2fd975d86d0d665 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/. ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: jammy -- 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/1964734 Title: /usr/bin/gnome- shell:11:g_type_check_instance_cast:st_entry_get_text:ffi_call_unix64:ffi_call_int:Gjs::Function::invoke Status in gnome-shell package in Ubuntu: New 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 41.3-1ubuntu1, the problem page at https://errors.ubuntu.com/problem/0a44a1b3318d644c23879475d2fd975d86d0d665 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/ubuntu/+source/gnome-shell/+bug/1964734/+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 1926862] Re: Unable to exit Activities Overview in Ubuntu 21.04
*** This bug is a duplicate of bug 1922353 *** https://bugs.launchpad.net/bugs/1922353 Comment #6 doesn't appear to be directly relevant to this bug. But most likely if you don't have the option to log into a Wayland session then you're probably using Nvidia and need to add the kernel parameter: nvidia-drm.modeset=1 -- 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/1926862 Title: Unable to exit Activities Overview in Ubuntu 21.04 Status in gnome-shell package in Ubuntu: Confirmed Bug description: In Ubuntu 21.04, after entering the Activities Overview by clicking on Activities, by using the hot corner, or by pressing the Super key, the user is not able to exit the Activities Overview and return to the Desktop. The user can still open or close applications, or move applications to different work spaces, but the user can not interact with open applications or return to the normal GNOME desktop. This issue occurs randomly. The only remedy is to logout, restart gnome shell with Alt-F2, R if using Xorg. This affects: Ubuntu 21.04 gnome-shell 3.38.4-1ubuntu2 ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome-shell 3.38.4-1ubuntu2 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: Ubuntu-Blue:ubuntu:GNOME Date: Sat May 1 21:37:12 2021 DisplayManager: gdm3 InstallationDate: Installed on 2021-04-28 (3 days ago) InstallationMedia: Ubuntu 21.04.0 2021.04.27 amd64 "Custom Hirsute Hippo" (20210427) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.38.4-1ubuntu2 SourcePackage: gnome-shell 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/1926862/+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 1875015] Re: Displaylink is extremely slow
** No longer affects: nvidia-graphics-drivers-470 (Ubuntu) ** Summary changed: - Displaylink is extremely slow + Displaylink is extremely slow in Xorg sessions -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-amdgpu in Ubuntu. https://bugs.launchpad.net/bugs/1875015 Title: Displaylink is extremely slow in Xorg sessions Status in Nouveau Xorg driver: Unknown Status in OEM Priority Project: New Status in xf86-video-amd: Unknown Status in X.Org X server: Unknown Status in xorg-server package in Ubuntu: Fix Released Status in xserver-xorg-video-amdgpu package in Ubuntu: In Progress Status in xserver-xorg-video-nouveau package in Ubuntu: In Progress Status in xorg-server source package in Focal: Fix Released Status in xorg-server source package in Hirsute: Won't Fix Status in xorg-server source package in Impish: Fix Released Bug description: Using ubuntu 20.04 on displaylink docking with external monitor is totally slow, unusable. The GUI responds very slow, if you click, the command of the click goes on after about 3 seconds... if you type, all the letters are with the same lag, so it is totally unusable. Was using displaylink without any problem on 19.10 until yesterday, when I upgraded to 20.04. It is terrific. If i plug out the usb for the displaylink docking station, than the speed is back, and the system is ok, if I connect it to the docking station again, everything extremely slow again. Please investigate this asap, as it is unusable on displaylink docking stations. To manage notifications about this bug go to: https://bugs.launchpad.net/nouveau/+bug/1875015/+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 1959747] Re: [upstream] Very high CPU and slow responsiveness in Thunderbird 91
** Summary changed: - [upstream] Very high CPU and slow responsiveness in Thunderbird 91.5.0 + [upstream] Very high CPU and slow responsiveness in Thunderbird 91 -- 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/1959747 Title: [upstream] Very high CPU and slow responsiveness in Thunderbird 91 Status in Mozilla Thunderbird: Confirmed Status in thunderbird package in Ubuntu: Triaged Bug description: Very high CPU and slow responsiveness in Thunderbird 91.5.0. Just moving the mouse cursor over a message list results in 365% CPU for me. I had to set this in the config editor to fix it: gfx.webrender.force-disabled = TRUE Upstream bug: https://bugzilla.mozilla.org/show_bug.cgi?id=1730423 To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/1959747/+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 1964682] Re: IBus not starting properly at login with gnome-shell 42
The issue only happens when logging in to a wayland session. Also, I stumbled upon this upstream gtk issue: https://gitlab.gnome.org/GNOME/gtk/-/issues/4699 Currently we install ibus-gtk4 by default (ibus recommends it), which is my 'fault'. Assumed that it should be consistent with how ibus-gtk3 is handled. Maybe not? OTOH, uninstalling ibus-gtk4 does not make a difference with respect to the issue reported through this bug, so this piece of info may be off topic here. ** Bug watch added: gitlab.gnome.org/GNOME/gtk/-/issues #4699 https://gitlab.gnome.org/GNOME/gtk/-/issues/4699 ** Tags added: wayland ** Summary changed: - IBus not starting properly at login with gnome-shell 42 + IBus not starting properly at login to wayland with gnome-shell 42 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1964682 Title: IBus not starting properly at login to wayland with gnome-shell 42 Status in gnome-shell package in Ubuntu: New Status in ibus package in Ubuntu: New Bug description: To get to the state in the bug summary I did: 1. Installed Ubuntu via the 220312 ISO 2. Made sure that all packages were updated 3. Installed ibus-libpinyin, re-logged in, and added "Intelligent Pinyin" to the input sources 4. Enabled -proposed 5. Run this command: sudo apt install gnome-shell gnome-shell-common gir1.2-mutter-10 libmutter-10-0 mutter-common 6. Rebooted Now, once logged in, gnome-shell does not include "Intelligent Pinyin" in the input source menu. Several expected processes are missing: $ ps aux | grep ibus gunnar 3057 0.0 0.0 232404 7984 ?Sl 20:05 0:00 ibus-daemon --panel disable -r --xim gunnar 3076 0.0 0.0 157280 6228 ?Sl 20:05 0:00 /usr/libexec/ibus-memconf gunnar 5117 0.0 0.0 24492 2776 pts/0S+ 20:06 0:00 grep --color=auto ibus If I start ibus-setup it shows the attached dialog. From there I can click "Yes" and successfully start IBus that way, and then it works as expected. Note that im-config is not involved. Nowadays, on GNOME desktops, we rely completely on the GNOME mechanisms for starting and configuring IBus. One thought is that ibus upstream has not released since August 20. Can it possibly be that some unreleased upstream ibus commits are needed for gnome-shell 42? https://github.com/ibus/ibus/commits/master To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1964682/+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 1964732] [NEW] [FFe] Include Desktop Icons Appearance Settings
Public bug reported: In Jammy the default desktop extension is providing lots settings in a non very integrated way, accessible from right-click: https://i.imgur.com/boMhCrH.png We got a community contribution (https://gitlab.gnome.org/Community/Ubuntu/gnome-control- center/-/merge_requests/9) to move the most relevant (for ubuntu) settings into the ubuntu "appearance" panel in gnome-control-center so that we can explicitly only support a restricted number of options that we care about, while all the rest can be tuned when using the ding options manually or tools such as d-conf editor. The appearance options will include these new widgets: https://i.imgur.com/Cup75om.png This is the code involved: - https://salsa.debian.org/gnome-team/gnome-control-center/-/commit/3f7c10501b1ac28311dd9edb64e64bfbbcd67204 Not sure this is fully a FFe request, given that from the global desktop point of view we want actually support less features. --- It would be nice to be able to upload the update before UIF, so that we don't require further exception steps. ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Description changed: In Jammy the default desktop extension is providing lots settings in a non very integrated way, accessible from right-click: https://i.imgur.com/boMhCrH.png - We got a community contribution to move the most relevant (for ubuntu) + We got a community contribution + (https://gitlab.gnome.org/Community/Ubuntu/gnome-control- + center/-/merge_requests/9) to move the most relevant (for ubuntu) settings into the ubuntu "appearance" panel in gnome-control-center so that we can explicitly only support a restricted number of options that we care about, while all the rest can be tuned when using the ding options manually or tools such as d-conf editor. The appearance options will include these new widgets: https://i.imgur.com/Cup75om.png This is the code involved: - - https://salsa.debian.org/gnome-team/gnome-control-center/-/commit/3f7c10501b1ac28311dd9edb64e64bfbbcd67204 + - https://salsa.debian.org/gnome-team/gnome-control-center/-/commit/3f7c10501b1ac28311dd9edb64e64bfbbcd67204 Not sure this is fully a FFe request, given that from the global desktop point of view we want actually support less features. --- It would be nice to be able to upload the update before UIF, so that we don't require further exception steps. -- 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/1964732 Title: [FFe] Include Desktop Icons Appearance Settings Status in gnome-control-center package in Ubuntu: New Bug description: In Jammy the default desktop extension is providing lots settings in a non very integrated way, accessible from right-click: https://i.imgur.com/boMhCrH.png We got a community contribution (https://gitlab.gnome.org/Community/Ubuntu/gnome-control- center/-/merge_requests/9) to move the most relevant (for ubuntu) settings into the ubuntu "appearance" panel in gnome-control-center so that we can explicitly only support a restricted number of options that we care about, while all the rest can be tuned when using the ding options manually or tools such as d-conf editor. The appearance options will include these new widgets: https://i.imgur.com/Cup75om.png This is the code involved: - https://salsa.debian.org/gnome-team/gnome-control-center/-/commit/3f7c10501b1ac28311dd9edb64e64bfbbcd67204 Not sure this is fully a FFe request, given that from the global desktop point of view we want actually support less features. --- It would be nice to be able to upload the update before UIF, so that we don't require further exception steps. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1964732/+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 1964675] Re: Window dragging lag when rendering 3d objects. (GNOME 42, NVIDIA, glxgear, pymol)
Other DEs (xfce, icewm, and fvwm) do NOT have such issues. I guess this might be a gnome related bug. -- 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/1964675 Title: Window dragging lag when rendering 3d objects. (GNOME 42, NVIDIA, glxgear, pymol) Status in gnome-shell package in Ubuntu: New Bug description: OS/software: Ubuntu Jammy Jellyfish (development branch), GNOME 42.beta, X11, NVIDIA-driver-510 (510.54) Hardware: Intel® Xeon(R) CPU E5-1650 v2 @ 3.50GHz × 12, 31,3 GiB RAM, NVIDIA Corporation GP106 [GeForce GTX 1060 6GB] How to reproduce: open glxgear, on the same workspace, move any window, there is badly dragging lag. But there is no lag if move window on a different workspace. CPU/GPU usages are normal (<3%). Disable Sync to VBlank in NVIDIA Settings can solve this issue, but CPU/GPU usages are abornmally high (single core CPU>80%, GPU>10% only for glxgear). Both NVIDIA-driver-510 and NVIDIA-driver-470 have the same issue. But another Intel-GPU based laptop works fine. This is not a glxgear bug, as other realtime 3D rendering (PyMOL, Blender...) casue the same issue. Possible reasons I guess: NVIDIA driver bug, kernel bug, or GNOME 42 bug. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1964675/+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 1926862] Re: Unable to exit Activities Overview in Ubuntu 21.04
*** This bug is a duplicate of bug 1922353 *** https://bugs.launchpad.net/bugs/1922353 How can I change from Wayland to Xorg if it doesn't appear as an option on my login screen? I am currently unable to exit this view and I can't seem to find any alternative ways of doing so. -- 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/1926862 Title: Unable to exit Activities Overview in Ubuntu 21.04 Status in gnome-shell package in Ubuntu: Confirmed Bug description: In Ubuntu 21.04, after entering the Activities Overview by clicking on Activities, by using the hot corner, or by pressing the Super key, the user is not able to exit the Activities Overview and return to the Desktop. The user can still open or close applications, or move applications to different work spaces, but the user can not interact with open applications or return to the normal GNOME desktop. This issue occurs randomly. The only remedy is to logout, restart gnome shell with Alt-F2, R if using Xorg. This affects: Ubuntu 21.04 gnome-shell 3.38.4-1ubuntu2 ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome-shell 3.38.4-1ubuntu2 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: Ubuntu-Blue:ubuntu:GNOME Date: Sat May 1 21:37:12 2021 DisplayManager: gdm3 InstallationDate: Installed on 2021-04-28 (3 days ago) InstallationMedia: Ubuntu 21.04.0 2021.04.27 amd64 "Custom Hirsute Hippo" (20210427) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.38.4-1ubuntu2 SourcePackage: gnome-shell 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/1926862/+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 1769116] Re: Some code accessed the property 'discreteGpuAvailable' on the module 'appDisplay'
I am seeing this after CDROM read errors of audio CDs using rhythmbox on Ubuntu
20.04 with an Nvidia video card.
After that, rhythmbox fails to start, adding this complaint to /var/log/syslog,
and cannot be restarted without logging off or rebooting.
Nearby syslog entries appended.
Mar 13 08:56:29 wedgingt kernel: [121925.744832] ata2.00: exception Emask 0x0
SAct 0x0 SErr 0x0 action 0x6 frozen
Mar 13 08:56:29 wedgingt kernel: [121925.744838] ata2.00: cmd
a0/01:00:00:10:f8/00:00:00:00:00/a0 tag 15 dma 63504 in
Mar 13 08:56:29 wedgingt kernel: [121925.744838] Volume set (in), Read
cd be 00 00 05 56 a2 00 00 1b f8 00 00res 40/00:03:00:00:00/00:00:00:00:00/a0
Emask 0x4 (timeout)
Mar 13 08:56:29 wedgingt kernel: [121925.744839] ata2.00: status: { DRDY }
Mar 13 08:56:29 wedgingt kernel: [121925.744841] ata2: hard resetting link
Mar 13 08:56:30 wedgingt kernel: [121926.059355] ata2: SATA link up 1.5 Gbps
(SStatus 113 SControl 300)
Mar 13 08:56:30 wedgingt kernel: [121926.064621] ata2.00: configured for
UDMA/100
Mar 13 08:56:30 wedgingt rhythmbox.desktop[16448]: scsi_read error:
sector=349858 length=27 retry=0
Mar 13 08:56:30 wedgingt kernel: [121926.065866] ata2: EH complete
Mar 13 08:56:30 wedgingt rhythmbox.desktop[16448]: Sense key:
5 ASC: 21 ASCQ: 4
Mar 13 08:56:30 wedgingt rhythmbox.desktop[16448]: Transport
error: Illegal SCSI request (rejected by target)
Mar 13 08:56:30 wedgingt rhythmbox.desktop[16448]: System
error: Invalid argument
Mar 13 08:57:20 wedgingt kernel: [121976.939509] ata2.00: exception Emask 0x0
SAct 0x0 SErr 0x0 action 0x6 frozen
Mar 13 08:57:20 wedgingt kernel: [121976.939515] ata2.00: cmd
a0/01:00:00:70:77/00:00:00:00:00/a0 tag 19 dma 30576 in
Mar 13 08:57:20 wedgingt kernel: [121976.939515] Volume set (in), Read
cd be 00 00 05 56 a2 00 00 0d f8 00 00res 40/00:03:00:00:00/00:00:00:00:00/a0
Emask 0x4 (timeout)
Mar 13 08:57:20 wedgingt kernel: [121976.939516] ata2.00: status: { DRDY }
Mar 13 08:57:20 wedgingt kernel: [121976.939518] ata2: hard resetting link
Mar 13 08:57:21 wedgingt kernel: [121977.253940] ata2: SATA link up 1.5 Gbps
(SStatus 113 SControl 300)
Mar 13 08:57:21 wedgingt kernel: [121977.259226] ata2.00: configured for
UDMA/100
Mar 13 08:57:21 wedgingt rhythmbox.desktop[16448]: scsi_read error:
sector=349858 length=13 retry=1
Mar 13 08:57:21 wedgingt rhythmbox.desktop[16448]: Sense key:
5 ASC: 21 ASCQ: 4
Mar 13 08:57:21 wedgingt rhythmbox.desktop[16448]: Transport
error: Illegal SCSI request (rejected by target)
Mar 13 08:57:21 wedgingt rhythmbox.desktop[16448]: System
error: Invalid argument
Mar 13 08:57:21 wedgingt kernel: [121977.260496] ata2: EH complete
Mar 13 08:57:29 wedgingt gnome-shell[3230]: Some code accessed the property
'discreteGpuAvailable' on the module 'appDisplay'. That property was defined
with 'let' or 'const' inside the module. This was previously supported, but is
not correct according to the ES6 standard. Any symbols to be exported from a
module must be defined with 'var'. The property access will work as previously
for the time being, but please fix your code anyway.
Mar 13 08:57:29 wedgingt gnome-shell[3230]:
../clutter/clutter/clutter-actor.c:10558: The clutter_actor_set_allocation()
function can only be called from within the implementation of the
ClutterActor::allocate() virtual function.
Mar 13 08:57:30 wedgingt systemd[2994]: Started Application launched by
gnome-shell.
Mar 13 08:57:30 wedgingt gnome-shell[1803751]: gio: cdda://sr0/: mount
doesn�~@~Yt implement �~@~\eject�~@~] or �~@~\eject_with_operation�~@~]
Mar 13 08:57:30 wedgingt systemd[2994]: gnome-launched-gio-1803751.scope:
Succeeded.
Mar 13 08:58:12 wedgingt kernel: [122028.146104] ata2.00: exception Emask 0x0
SAct 0x0 SErr 0x0 action 0x6 frozen
Mar 13 08:58:12 wedgingt kernel: [122028.146110] ata2.00: cmd
a0/01:00:00:20:37/00:00:00:00:00/a0 tag 16 dma 14112 in
Mar 13 08:58:12 wedgingt kernel: [122028.146110] Volume set (in), Read
cd be 00 00 05 56 a2 00 00 06 f8 00 00res 40/00:03:00:00:00/00:00:00:00:00/a0
Emask 0x4 (timeout)
Mar 13 08:58:12 wedgingt kernel: [122028.146111] ata2.00: status: { DRDY }
Mar 13 08:58:12 wedgingt kernel: [122028.146113] ata2: hard resetting link
Mar 13 08:58:12 wedgingt kernel: [122028.460550] ata2: SATA link up 1.5 Gbps
(SStatus 113 SControl 300)
Mar 13 08:58:12 wedgingt kernel: [122028.465458] ata2.00: configured for
UDMA/100
Mar 13 08:58:12 wedgingt rhythmbox.desktop[16448]: scsi_read error:
sector=349858 length=6 retry=2
Mar 13 08:58:12 wedgingt rhythmbox.desktop[16448]: Sense key:
5 ASC: 21 ASCQ: 4
Mar 13 08:58:12 wedgingt rhythmbox.desktop[16448]: Transport
error: Illegal SCSI request (rejected by target)
Mar 13 08:58:12 wedgingt rhythmbox.desktop[16448]: System
error: Invalid argument
Mar 13 08:58:12 wedgingt kernel:
[Desktop-packages] [Bug 1964547] Re: [apt] Firefox 98 installed from apt cannot Play YouTube
** Attachment added: "More Debug Information" https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1964547/+attachment/5568402/+files/Screenshot%20from%202022-03-13%2022-17-50.png -- 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/1964547 Title: [apt] Firefox 98 installed from apt cannot Play YouTube Status in firefox package in Ubuntu: New Bug description: • Ubuntu 21.10 (64 bit) • Firefox 98 installed via apt (cookies & cache have been cleared) • Kernel 5.13.0-30-generic x86_64 • Tried on both wayland and X11 session → same result Steps to reproduce: (1) Visit https://www.youtube.com (2) Choose one of the video Actual Result: Video doesn't play What Expected: Video Play normally Previously it was normal on Firefox 97 (apt version) Tried installing Firefox 98 Snap version and it works normally To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1964547/+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 1964547] Re: [apt] Firefox 98 installed from apt cannot Play YouTube
Package: firefox
Version: 98.0+build3-0ubuntu0.21.10.2
Priority: optional
Section: web
Origin: Ubuntu
Maintainer: Ubuntu Mozilla Team
Bugs: https://bugs.launchpad.net/ubuntu/+filebug
Installed-Size: 232 MB
Provides: gnome-www-browser, iceweasel, www-browser
Depends: lsb-release, libasound2 (>= 1.0.16), libatk1.0-0 (>= 1.12.4), libc6
(>= 2.34), libcairo-gobject2 (>= 1.10.0), libcairo2 (>= 1.10.0), libdbus-1-3
(>= 1.9.14), libdbus-glib-1-2 (>= 0.78), libfontconfig1 (>= 2.12.6),
libfreetype6 (>= 2.10.1), libgcc-s1 (>= 3.3), libgdk-pixbuf-2.0-0 (>= 2.22.0),
libglib2.0-0 (>= 2.42), libgtk-3-0 (>= 3.14), libharfbuzz0b (>= 0.6.0),
libpango-1.0-0 (>= 1.14.0), libpangocairo-1.0-0 (>= 1.14.0), libstdc++6 (>=
11), libx11-6, libx11-xcb1 (>= 2:1.7.2), libxcb-shm0, libxcb1, libxcomposite1
(>= 1:0.4.5), libxcursor1 (>> 1.1.2), libxdamage1 (>= 1:1.1), libxext6,
libxfixes3, libxi6, libxrandr2 (>= 2:1.4.0), libxrender1, libxtst6
Recommends: xul-ext-ubufox, libcanberra0, libdbusmenu-glib4, libdbusmenu-gtk3-4
Suggests: fonts-lyx
Replaces: kubuntu-firefox-installer
Task: kubuntu-desktop, kubuntu-full, xubuntu-desktop, lubuntu-desktop,
ubuntustudio-desktop, ubuntukylin-desktop, ubuntu-mate-core,
ubuntu-mate-desktop, ubuntu-budgie-desktop, ubuntu-budgie-desktop-raspi
Xul-Appid: {ec8030f7-c20a-464f-9b0e-13a3a9e97384}
Download-Size: 62.6 MB
APT-Sources: http://archive.ubuntu.com/ubuntu impish-updates/main amd64 Packages
Description: Safe and easy web browser from Mozilla
Firefox delivers safe, easy web browsing. A familiar user interface,
enhanced security features including protection from online identity theft,
and integrated search let you get the most out of the web.
--
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/1964547
Title:
[apt] Firefox 98 installed from apt cannot Play YouTube
Status in firefox package in Ubuntu:
New
Bug description:
• Ubuntu 21.10 (64 bit)
• Firefox 98 installed via apt (cookies & cache have been cleared)
• Kernel 5.13.0-30-generic x86_64
• Tried on both wayland and X11 session → same result
Steps to reproduce:
(1) Visit https://www.youtube.com
(2) Choose one of the video
Actual Result: Video doesn't play
What Expected: Video Play normally
Previously it was normal on Firefox 97 (apt version)
Tried installing Firefox 98 Snap version and it works normally
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1964547/+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 1964547] Re: [apt] Firefox 98 installed from apt cannot Play YouTube
** Attachment added: "The Video keep loading" https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1964547/+attachment/5568401/+files/Screenshot%20from%202022-03-13%2022-18-38.png -- 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/1964547 Title: [apt] Firefox 98 installed from apt cannot Play YouTube Status in firefox package in Ubuntu: New Bug description: • Ubuntu 21.10 (64 bit) • Firefox 98 installed via apt (cookies & cache have been cleared) • Kernel 5.13.0-30-generic x86_64 • Tried on both wayland and X11 session → same result Steps to reproduce: (1) Visit https://www.youtube.com (2) Choose one of the video Actual Result: Video doesn't play What Expected: Video Play normally Previously it was normal on Firefox 97 (apt version) Tried installing Firefox 98 Snap version and it works normally To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1964547/+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 1964707] [NEW] please sync qpdf 10.6.3
Public bug reported: qpdf 10.6.3 is in debian unstable with no blockers other than age. It is a bug-fix only release. The two code-facing changes are fix to allow correct handling of PDF 2.0 native UTF-8 strings and a fix to appearance stream generation when "0 Tf" appears in "/DA". ** Affects: qpdf (Ubuntu) Importance: Undecided Status: New -- 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/1964707 Title: please sync qpdf 10.6.3 Status in qpdf package in Ubuntu: New Bug description: qpdf 10.6.3 is in debian unstable with no blockers other than age. It is a bug-fix only release. The two code-facing changes are fix to allow correct handling of PDF 2.0 native UTF-8 strings and a fix to appearance stream generation when "0 Tf" appears in "/DA". To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qpdf/+bug/1964707/+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 1940754] Re: Scanned images are deteriorated by compression artifacts with Brother MFC-L2710DW
The problems has disappeared. xsane and scanimage work fine now: - The xsane gui offers scan resolutions up to 9600 dpi - No compression artefacts, tested with 1200 dpi - No error messages are displayed by xsane The reason is a mystery, neither any sane nor brscan related packages seem to have been updated in the meantime, but the options xsane offers and how it behaves are clearly different. I can't remember having touched any scanner related configuration since then. However, even though there is only one device, which is connected via WLAN, xsane offers me two "devices" upon startup: Brother *b20210821 MFC-L2710DW [brother4:net1;dev0] and ESCL Brother MFC-L271 flatbed scanner [escl:http://192.168.178.26:80] With the first "device", "Brother *b20210821", scanning works fine, with the second device "ESCL Brother MFC-L271", the old problems occur. -- 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/1940754 Title: Scanned images are deteriorated by compression artifacts with Brother MFC-L2710DW Status in sane-backends package in Ubuntu: New Bug description: I have a Brother MFC-L2710DW printer with integrated flatbed scanner. There are two major problems when scanning with sane: The first problem is that the quality of all scanned images is very poor due to 8x8 pixel JPG compression artefacts. The root coarse seems to be the backend, as the result is the same independently if the image is acquired through xsane or scanimage. The second problem is that sane only scans up to 300 dpi. 1200 dpi is not offered at all and for 600 dpi the error message "Failed to start scanner: Invalid argument" is displayed. Interestingly the message is displayed after the scanner has completed the scan, but the data seems not to be received or understood by sane. The scanner works fine in Ubuntu with the commercial software vuescan, which rules out a firmware bug or malfunctioning of the scanner itself. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libsane 1.0.29-0ubuntu5.2 ProcVersionSignature: Ubuntu 5.11.0-16.17~20.04.5-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Aug 21 23:00:21 2021 InstallationDate: Installed on 2015-11-05 (2116 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) SourcePackage: sane-backends UpgradeStatus: Upgraded to focal on 2020-09-10 (345 days ago) modified.conffile..etc.apport.crashdb.conf: [modified] mtime.conffile..etc.apport.crashdb.conf: 2019-03-07T14:28:39.455024 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1940754/+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 1964701] Re: nautilus crashed with SIGSEGV in gtk_widget_get_ancestor()
*** This bug is a duplicate of bug 1962761 *** https://bugs.launchpad.net/bugs/1962761 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 #1962761, 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/1964701/+attachment/5568380/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1964701/+attachment/5568382/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1964701/+attachment/5568385/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1964701/+attachment/5568386/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1964701/+attachment/5568387/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1964701/+attachment/5568388/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1964701/+attachment/5568389/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1962761 nautilus crashed with SIGSEGV in gtk_widget_get_ancestor() ** 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 nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1964701 Title: nautilus crashed with SIGSEGV in gtk_widget_get_ancestor() Status in nautilus package in Ubuntu: New Bug description: Happened when I tried to open nautlus twice and very quickly between the clicks ProblemType: Crash DistroRelease: Ubuntu 22.04 Package: nautilus 1:42~rc-1ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19 Uname: Linux 5.15.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Mar 13 09:55:30 2022 ExecutablePath: /usr/bin/nautilus GsettingsChanges: b'org.gnome.nautilus.icon-view' b'default-zoom-level' b"'larger'" b'org.gnome.nautilus.window-state' b'maximized' b'true' InstallationDate: Installed on 2022-01-03 (68 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211230) ProcCmdline: /usr/bin/nautilus --gapplication-service ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) LANG=ro_RO.UTF-8 SegvAnalysis: Segfault happened at: 0x7f703da1aa88 : cmp %rax,(%rbx) PC (0x7f703da1aa88) ok source "%rax" ok destination "(%rbx)" (0x34434e33496a4c74) not located in a known VMA region (needed writable region)! SegvReason: writing unknown VMA Signal: 11 SourcePackage: nautilus StacktraceTop: gtk_widget_get_ancestor () at /lib/x86_64-linux-gnu/libgtk-3.so.0 () g_closure_invoke () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0 () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_emit_valist () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: nautilus crashed with SIGSEGV in gtk_widget_get_ancestor() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo separator: usr_lib_nautilus: evince41.3-3 file-roller 3.41.90-1 nautilus-extension-gnome-terminal 3.43.90-1ubuntu1 nautilus-share0.7.3-2ubuntu4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1964701/+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
