[Desktop-packages] [Bug 1948355] Re: Firefox settings font size dropdown flashes, hard to select
Sorry I'm late. Here it is. ** Attachment added: "about-support.txt" https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1948355/+attachment/5536862/+files/about-support.txt -- 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/1948355 Title: Firefox settings font size dropdown flashes, hard to select Status in firefox package in Ubuntu: Incomplete Bug description: Go to settings, then font, and try to change the font size. The dropdown flashes and disappears, and is very difficult to select. Happens both on the main screen and the "advanced.." screen for all size selectors. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1948355/+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 1948355] Re: Firefox settings font size dropdown flashes, hard to select
>From #1948356: "As an aside, I have a second system, installed at the same time and in the same way (Ubuntu 21.04, then upgraded to 21.10). The second system (my desktop at home) shows neither of these issues (this one and bug #1948355). The bookmarks and settings are all synced from the same Firefox account, and they're synced with each other. The hardware differences are that this machine is an intel laptop with integrated graphics, the other system is an AMD desktop with an AMD GPU. For software, I may not have all the same extensions enabled. I will get this data from home and compare tonight or tomorrow." -- 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/1948355 Title: Firefox settings font size dropdown flashes, hard to select Status in firefox package in Ubuntu: Incomplete Bug description: Go to settings, then font, and try to change the font size. The dropdown flashes and disappears, and is very difficult to select. Happens both on the main screen and the "advanced.." screen for all size selectors. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1948355/+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 1948704] Re: segfault with gnome-shell & gdm-session-worker
OK I have now opened your gdm-session-worker crash formally in bug 1949127. If you want to report a crash of gnome-shell too then it will need a separate bug following: https://wiki.ubuntu.com/Bugs/Responses#Missing_a_crash_report_or_having_a_.crash_attachment ** Summary changed: - segfault with gnome-shell & gdm-session-worker + segfault with gnome-shell ** Package changed: gdm3 (Ubuntu) => gnome-shell (Ubuntu) -- 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/1948704 Title: segfault with gnome-shell Status in gnome-shell package in Ubuntu: Incomplete Bug description: Using Ubuntu 20.04.3 LTS with 5.11.0-38-generic #42~20.04.1-Ubuntu, gnome-shell/focal-updates,now 3.36.9-0ubuntu0.20.04.2 amd64 [installed,automatic] gnome-shell/focal-security 3.36.4-1ubuntu1~20.04.2 amd64 gnome-shell/focal 3.36.1-5ubuntu1 amd64 gnome-session/focal,focal 3.36.0-2ubuntu1 all Oct 22 19:41:09 ourserver kernel: [15260.574496] show_signal_msg: 29 callbacks suppressed Oct 22 19:41:09 ourserver kernel: [15260.574503] gnome-shell[1475]: segfault at 11390db8 ip 7f3fd36f716c sp 7ffe50e6d788 error 4 in libmozjs-68.so.68.6.0[7f3fd3234000+843000] Oct 22 19:41:09 ourserver kernel: [15260.574525] Code: 50 10 85 d2 75 d0 0f b6 40 14 83 e8 01 3c 01 41 0f 96 c0 44 89 c0 c3 0f 1f 80 00 00 00 00 48 89 f0 45 31 c0 48 25 00 00 f0 ff <48> 8b 90 f8 ff 0f 00 48 39 17 74 08 44 89 c0 c3 0f 1f 40 00 48 85 Oct 22 19:41:09 ourserver kernel: [15260.619146] apport[2636]: segfault at 3 ip 0003 sp 7fffe172cb48 error 14 in python3.8[40+23000] Oct 22 19:41:09 ourserver kernel: [15260.619165] Code: Unable to access opcode bytes at RIP 0xffd9. Oct 22 19:41:09 ourserver kernel: [15260.619186] Process 2636(apport) has RLIMIT_CORE set to 1 Oct 22 19:41:09 ourserver kernel: [15260.619189] Aborting core Oct 22 19:41:09 ourserver NetworkManager[1049]: ../../../gobject/gsignal.c:2595: signal 'cancelled' is invalid for instance '0x562e9e761320' of type 'GCancellable' Oct 22 19:41:09 ourserver NetworkManager[1049]: message repeated 3 times: [ ../../../gobject/gsignal.c:2595: signal 'cancelled' is invalid for instance '0x562e9e761320' of type 'GCancellable'] Oct 22 19:41:09 ourserver NetworkManager[1049]: ../../../gobject/gsignal.c:2595: signal 'cancelled' is invalid for instance '0x562e9e7d7860' of type 'GCancellable' Oct 22 19:41:09 ourserver NetworkManager[1049]: ../../../gobject/gsignal.c:2595: signal 'cancelled' is invalid for instance '0x562e9e80f8e0' of type 'GCancellable' Oct 22 19:41:09 ourserver NetworkManager[1049]: ../../../gobject/gsignal.c:2595: signal 'cancelled' is invalid for instance '0x562e9e811b20' of type 'GCancellable' Oct 22 19:41:09 ourserver NetworkManager[1049]: ../../../gobject/gsignal.c:2595: signal 'cancelled' is invalid for instance '0x562e9e80e0a0' of type 'GCancellable' Oct 22 19:41:09 ourserver NetworkManager[1049]: ../../../gobject/gsignal.c:2595: signal 'cancelled' is invalid for instance '0x7fd938006460' of type 'GCancellable' Oct 22 19:41:09 ourserver NetworkManager[1049]: ../../../gobject/gsignal.c:2595: signal 'cancelled' is invalid for instance '0x562e9e82c1e0' of type 'GCancellable' Oct 22 19:41:09 ourserver NetworkManager[1049]: ../../../gobject/gsignal.c:2595: signal 'cancelled' is invalid for instance '0x562e9e7fc320' of type 'GCancellable' Oct 22 19:41:09 ourserver NetworkManager[1049]: ../../../gobject/gsignal.c:2595: signal 'cancelled' is invalid for instance '0x7fd934004a60' of type 'GCancellable' Oct 22 19:41:09 ourserver NetworkManager[1049]: ../../../gobject/gsignal.c:2595: signal 'cancelled' is invalid for instance '0x562e9e80ff60' of type 'GCancellable' Oct 22 19:41:09 ourserver NetworkManager[1049]: ../../../gobject/gsignal.c:2595: signal 'cancelled' is invalid for instance '0x562e9e8317a0' of type 'GCancellable' Oct 22 19:41:09 ourserver NetworkManager[1049]: ../../../gobject/gsignal.c:2595: signal 'cancelled' is invalid for instance '0x562e9e8145e0' of type 'GCancellable' Oct 22 19:41:09 ourserver NetworkManager[1049]: ../../../gobject/gsignal.c:2595: signal 'cancelled' is invalid for instance '0x7fd934005020' of type 'GCancellable' Oct 22 19:41:09 ourserver NetworkManager[1049]: ../../../gobject/gsignal.c:2595: signal 'cancelled' is invalid for instance '0x562e9e82c420' of type 'GCancellable' Oct 22 19:41:09 ourserver NetworkManager[1049]: ../../../gobject/gsignal.c:2595: signal 'cancelled' is invalid for instance '0x562e9e80fea0' of type 'GCancellable' Oct 22 19:41:09 ourserver NetworkManager[1049]: ../../../gobject/gsignal.c:2595: signal 'cancelled' is invalid for instance '0x562e9e7c05e0' of type 'GCancellable' Oct 22 19:41:09 ourserver NetworkManager[1049]: ../../../gobject/gsignal.c:2595: signal 'cancelled' is invalid for instance
[Desktop-packages] [Bug 1949127] [NEW] gdm-session-worker crashed with SIGSEGV in memcpy() from message_extend_fields() from message_append_field_signature() from sd_bus_message_seal() from bus_seal_m
Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding gdm3. This problem was most recently seen with package version 3.36.3-0ubuntu0.20.04.4, the problem page at https://errors.ubuntu.com/problem/64ab004b91cb702bc3222f735ab9c8fdb32ee25d 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: gdm3 (Ubuntu) Importance: Undecided Status: New ** Tags: focal -- 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/1949127 Title: gdm-session-worker crashed with SIGSEGV in memcpy() from message_extend_fields() from message_append_field_signature() from sd_bus_message_seal() from bus_seal_message() Status in gdm3 package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gdm3. This problem was most recently seen with package version 3.36.3-0ubuntu0.20.04.4, the problem page at https://errors.ubuntu.com/problem/64ab004b91cb702bc3222f735ab9c8fdb32ee25d 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/gdm3/+bug/1949127/+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 1948704] Re: segfault with gnome-shell & gdm-session-worker
** Package changed: gnome-shell (Ubuntu) => gdm3 (Ubuntu) -- 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/1948704 Title: segfault with gnome-shell & gdm-session-worker Status in gdm3 package in Ubuntu: Incomplete Bug description: Using Ubuntu 20.04.3 LTS with 5.11.0-38-generic #42~20.04.1-Ubuntu, gnome-shell/focal-updates,now 3.36.9-0ubuntu0.20.04.2 amd64 [installed,automatic] gnome-shell/focal-security 3.36.4-1ubuntu1~20.04.2 amd64 gnome-shell/focal 3.36.1-5ubuntu1 amd64 gnome-session/focal,focal 3.36.0-2ubuntu1 all Oct 22 19:41:09 ourserver kernel: [15260.574496] show_signal_msg: 29 callbacks suppressed Oct 22 19:41:09 ourserver kernel: [15260.574503] gnome-shell[1475]: segfault at 11390db8 ip 7f3fd36f716c sp 7ffe50e6d788 error 4 in libmozjs-68.so.68.6.0[7f3fd3234000+843000] Oct 22 19:41:09 ourserver kernel: [15260.574525] Code: 50 10 85 d2 75 d0 0f b6 40 14 83 e8 01 3c 01 41 0f 96 c0 44 89 c0 c3 0f 1f 80 00 00 00 00 48 89 f0 45 31 c0 48 25 00 00 f0 ff <48> 8b 90 f8 ff 0f 00 48 39 17 74 08 44 89 c0 c3 0f 1f 40 00 48 85 Oct 22 19:41:09 ourserver kernel: [15260.619146] apport[2636]: segfault at 3 ip 0003 sp 7fffe172cb48 error 14 in python3.8[40+23000] Oct 22 19:41:09 ourserver kernel: [15260.619165] Code: Unable to access opcode bytes at RIP 0xffd9. Oct 22 19:41:09 ourserver kernel: [15260.619186] Process 2636(apport) has RLIMIT_CORE set to 1 Oct 22 19:41:09 ourserver kernel: [15260.619189] Aborting core Oct 22 19:41:09 ourserver NetworkManager[1049]: ../../../gobject/gsignal.c:2595: signal 'cancelled' is invalid for instance '0x562e9e761320' of type 'GCancellable' Oct 22 19:41:09 ourserver NetworkManager[1049]: message repeated 3 times: [ ../../../gobject/gsignal.c:2595: signal 'cancelled' is invalid for instance '0x562e9e761320' of type 'GCancellable'] Oct 22 19:41:09 ourserver NetworkManager[1049]: ../../../gobject/gsignal.c:2595: signal 'cancelled' is invalid for instance '0x562e9e7d7860' of type 'GCancellable' Oct 22 19:41:09 ourserver NetworkManager[1049]: ../../../gobject/gsignal.c:2595: signal 'cancelled' is invalid for instance '0x562e9e80f8e0' of type 'GCancellable' Oct 22 19:41:09 ourserver NetworkManager[1049]: ../../../gobject/gsignal.c:2595: signal 'cancelled' is invalid for instance '0x562e9e811b20' of type 'GCancellable' Oct 22 19:41:09 ourserver NetworkManager[1049]: ../../../gobject/gsignal.c:2595: signal 'cancelled' is invalid for instance '0x562e9e80e0a0' of type 'GCancellable' Oct 22 19:41:09 ourserver NetworkManager[1049]: ../../../gobject/gsignal.c:2595: signal 'cancelled' is invalid for instance '0x7fd938006460' of type 'GCancellable' Oct 22 19:41:09 ourserver NetworkManager[1049]: ../../../gobject/gsignal.c:2595: signal 'cancelled' is invalid for instance '0x562e9e82c1e0' of type 'GCancellable' Oct 22 19:41:09 ourserver NetworkManager[1049]: ../../../gobject/gsignal.c:2595: signal 'cancelled' is invalid for instance '0x562e9e7fc320' of type 'GCancellable' Oct 22 19:41:09 ourserver NetworkManager[1049]: ../../../gobject/gsignal.c:2595: signal 'cancelled' is invalid for instance '0x7fd934004a60' of type 'GCancellable' Oct 22 19:41:09 ourserver NetworkManager[1049]: ../../../gobject/gsignal.c:2595: signal 'cancelled' is invalid for instance '0x562e9e80ff60' of type 'GCancellable' Oct 22 19:41:09 ourserver NetworkManager[1049]: ../../../gobject/gsignal.c:2595: signal 'cancelled' is invalid for instance '0x562e9e8317a0' of type 'GCancellable' Oct 22 19:41:09 ourserver NetworkManager[1049]: ../../../gobject/gsignal.c:2595: signal 'cancelled' is invalid for instance '0x562e9e8145e0' of type 'GCancellable' Oct 22 19:41:09 ourserver NetworkManager[1049]: ../../../gobject/gsignal.c:2595: signal 'cancelled' is invalid for instance '0x7fd934005020' of type 'GCancellable' Oct 22 19:41:09 ourserver NetworkManager[1049]: ../../../gobject/gsignal.c:2595: signal 'cancelled' is invalid for instance '0x562e9e82c420' of type 'GCancellable' Oct 22 19:41:09 ourserver NetworkManager[1049]: ../../../gobject/gsignal.c:2595: signal 'cancelled' is invalid for instance '0x562e9e80fea0' of type 'GCancellable' Oct 22 19:41:09 ourserver NetworkManager[1049]: ../../../gobject/gsignal.c:2595: signal 'cancelled' is invalid for instance '0x562e9e7c05e0' of type 'GCancellable' Oct 22 19:41:09 ourserver NetworkManager[1049]: ../../../gobject/gsignal.c:2595: signal 'cancelled' is invalid for instance '0x562e9e7dfc20' of type 'GCancellable' Oct 22 19:41:09 ourserver NetworkManager[1049]: ../../../gobject/gsignal.c:2595: signal 'cancelled' is invalid for instance '0x562e9e761320' of type 'GCancellable' Oct 22 19:41:09 ourserver gnome-session[1446]: gnome-session-binary[1446]: WARNING: Application 'org.gnome.Shell.desktop' killed by signal 11
[Desktop-packages] [Bug 1948778] Re: Random flashes in gnome-shell
Again I can't see any KMS errors but it is suspicious that bug 1948589 occurred around the time you mention. I'm starting to think this isn't a KMS issue at all. Can you please take a video of the issue using a camera or phone? -- 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/1948778 Title: Random flashes in gnome-shell Status in gnome-shell package in Ubuntu: Incomplete Bug description: Ubuntu 22.04 development branch up to date to latest @ 26/10/2021 kernel 5.13.0-19-generic While working around on the desktop i'm getting short screen flashes like a screenshot style i cant reproduce them, they seem to come on random like every few minutes journal logs dont record anything while they occur this only happens on wayland, tested a long session on xorg where they dont occur ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 40.5-1ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu70 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Oct 26 11:12:30 2021 DisplayManager: gdm3 RelatedPackageVersions: mutter-common 40.5-1ubuntu2 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.xdg.autostart.gnome-shell-overrides-migration.desktop: 2021-10-23T19:12:47.175230 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1948778/+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 1948704] Re: segfault with gnome-shell & gdm-session-worker
That screenshot doesn't show that memory tests actually ran. Did you run the memory tests (which would take several hours)? Your crash has been recorded at https://errors.ubuntu.com/oops/0d1b7258-3816-11ec-ae83-fa163e102db1 but since it's the only crash of its kind I'm not yet sure that is valid. Please ensure you have run the full suite of memory tests over night. -- 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/1948704 Title: segfault with gnome-shell & gdm-session-worker Status in gnome-shell package in Ubuntu: Incomplete Bug description: Using Ubuntu 20.04.3 LTS with 5.11.0-38-generic #42~20.04.1-Ubuntu, gnome-shell/focal-updates,now 3.36.9-0ubuntu0.20.04.2 amd64 [installed,automatic] gnome-shell/focal-security 3.36.4-1ubuntu1~20.04.2 amd64 gnome-shell/focal 3.36.1-5ubuntu1 amd64 gnome-session/focal,focal 3.36.0-2ubuntu1 all Oct 22 19:41:09 ourserver kernel: [15260.574496] show_signal_msg: 29 callbacks suppressed Oct 22 19:41:09 ourserver kernel: [15260.574503] gnome-shell[1475]: segfault at 11390db8 ip 7f3fd36f716c sp 7ffe50e6d788 error 4 in libmozjs-68.so.68.6.0[7f3fd3234000+843000] Oct 22 19:41:09 ourserver kernel: [15260.574525] Code: 50 10 85 d2 75 d0 0f b6 40 14 83 e8 01 3c 01 41 0f 96 c0 44 89 c0 c3 0f 1f 80 00 00 00 00 48 89 f0 45 31 c0 48 25 00 00 f0 ff <48> 8b 90 f8 ff 0f 00 48 39 17 74 08 44 89 c0 c3 0f 1f 40 00 48 85 Oct 22 19:41:09 ourserver kernel: [15260.619146] apport[2636]: segfault at 3 ip 0003 sp 7fffe172cb48 error 14 in python3.8[40+23000] Oct 22 19:41:09 ourserver kernel: [15260.619165] Code: Unable to access opcode bytes at RIP 0xffd9. Oct 22 19:41:09 ourserver kernel: [15260.619186] Process 2636(apport) has RLIMIT_CORE set to 1 Oct 22 19:41:09 ourserver kernel: [15260.619189] Aborting core Oct 22 19:41:09 ourserver NetworkManager[1049]: ../../../gobject/gsignal.c:2595: signal 'cancelled' is invalid for instance '0x562e9e761320' of type 'GCancellable' Oct 22 19:41:09 ourserver NetworkManager[1049]: message repeated 3 times: [ ../../../gobject/gsignal.c:2595: signal 'cancelled' is invalid for instance '0x562e9e761320' of type 'GCancellable'] Oct 22 19:41:09 ourserver NetworkManager[1049]: ../../../gobject/gsignal.c:2595: signal 'cancelled' is invalid for instance '0x562e9e7d7860' of type 'GCancellable' Oct 22 19:41:09 ourserver NetworkManager[1049]: ../../../gobject/gsignal.c:2595: signal 'cancelled' is invalid for instance '0x562e9e80f8e0' of type 'GCancellable' Oct 22 19:41:09 ourserver NetworkManager[1049]: ../../../gobject/gsignal.c:2595: signal 'cancelled' is invalid for instance '0x562e9e811b20' of type 'GCancellable' Oct 22 19:41:09 ourserver NetworkManager[1049]: ../../../gobject/gsignal.c:2595: signal 'cancelled' is invalid for instance '0x562e9e80e0a0' of type 'GCancellable' Oct 22 19:41:09 ourserver NetworkManager[1049]: ../../../gobject/gsignal.c:2595: signal 'cancelled' is invalid for instance '0x7fd938006460' of type 'GCancellable' Oct 22 19:41:09 ourserver NetworkManager[1049]: ../../../gobject/gsignal.c:2595: signal 'cancelled' is invalid for instance '0x562e9e82c1e0' of type 'GCancellable' Oct 22 19:41:09 ourserver NetworkManager[1049]: ../../../gobject/gsignal.c:2595: signal 'cancelled' is invalid for instance '0x562e9e7fc320' of type 'GCancellable' Oct 22 19:41:09 ourserver NetworkManager[1049]: ../../../gobject/gsignal.c:2595: signal 'cancelled' is invalid for instance '0x7fd934004a60' of type 'GCancellable' Oct 22 19:41:09 ourserver NetworkManager[1049]: ../../../gobject/gsignal.c:2595: signal 'cancelled' is invalid for instance '0x562e9e80ff60' of type 'GCancellable' Oct 22 19:41:09 ourserver NetworkManager[1049]: ../../../gobject/gsignal.c:2595: signal 'cancelled' is invalid for instance '0x562e9e8317a0' of type 'GCancellable' Oct 22 19:41:09 ourserver NetworkManager[1049]: ../../../gobject/gsignal.c:2595: signal 'cancelled' is invalid for instance '0x562e9e8145e0' of type 'GCancellable' Oct 22 19:41:09 ourserver NetworkManager[1049]: ../../../gobject/gsignal.c:2595: signal 'cancelled' is invalid for instance '0x7fd934005020' of type 'GCancellable' Oct 22 19:41:09 ourserver NetworkManager[1049]: ../../../gobject/gsignal.c:2595: signal 'cancelled' is invalid for instance '0x562e9e82c420' of type 'GCancellable' Oct 22 19:41:09 ourserver NetworkManager[1049]: ../../../gobject/gsignal.c:2595: signal 'cancelled' is invalid for instance '0x562e9e80fea0' of type 'GCancellable' Oct 22 19:41:09 ourserver NetworkManager[1049]: ../../../gobject/gsignal.c:2595: signal 'cancelled' is invalid for instance '0x562e9e7c05e0' of type 'GCancellable' Oct 22 19:41:09 ourserver NetworkManager[1049]: ../../../gobject/gsignal.c:2595: signal 'cancelled' is invalid for instance '0x562e9e7dfc20' of type
[Desktop-packages] [Bug 1948008] Re: Copying and pasting to/from Nautilus does not work
gnome-shell-extension-desktop-icons is only being maintained for focal. All other Ubuntu releases should use gnome-shell-extension-desktop- icons-ng ** Changed in: gnome-shell-extension-desktop-icons (Ubuntu) Status: Incomplete => 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/1948008 Title: Copying and pasting to/from Nautilus does not work Status in gnome-shell package in Ubuntu: New Status in gnome-shell-extension-desktop-icons package in Ubuntu: Invalid Status in gnome-shell-extension-desktop-icons-ng package in Ubuntu: New Status in gnome-shell source package in Focal: New Status in gnome-shell-extension-desktop-icons source package in Focal: New Status in gnome-shell-extension-desktop-icons-ng source package in Focal: Invalid Status in gnome-shell source package in Hirsute: Fix Released Status in gnome-shell-extension-desktop-icons source package in Hirsute: Invalid Status in gnome-shell-extension-desktop-icons-ng source package in Hirsute: New Status in gnome-shell source package in Impish: Fix Released Status in gnome-shell-extension-desktop-icons source package in Impish: Invalid Status in gnome-shell-extension-desktop-icons-ng source package in Impish: New Bug description: [Impact] * After upstream Nautilus has reverted the following commit [1] related to upstream bug [2] the desktop icons extension lost it's ability to copy to/from nautilus. * This is related to the fact that before there was some metadata passed along in the clipboard along with text data. This was causing issues with compatibility with some applications that were not expecting any metadata (MIME type in this case) was glued to the text clipboard contents. Hence, it was reverted upstream [3]. * Fixing the root cause of this issue required changes to Nautilus [3], gnome-shell [4] and desktop-icons [5] [6]. Nautilus and gnome- shell parts are already implemented and present in Hirsute and Impish. [Test Plan] 1) Make sure desktop-icons extension is enabled. 2) Open nautilus window and copy any file from there by right-clicking and selecting "Copy" from the popup menu. 3) Right-click on desktop and select "Paste" from the context menu. Expected result: selected file is copied to the desktop. Actual result: "Paste" item is disabled in the menu. [Where problems could occur] * Mixing a version of nautilus without commit [3] and fixed version of desktop-icons may still lead to a scenario when copying will not work. * Any extension/application copying to desktop using the smuggled-in- text clipboard behavior should be expected to stop working. [Other Info] [1] https://gitlab.gnome.org/GNOME/nautilus/-/merge_requests/289 [2] https://gitlab.gnome.org/GNOME/nautilus/-/issues/634 [3] https://gitlab.gnome.org/GNOME/nautilus/-/merge_requests/573 [4] https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/1321 [5] https://gitlab.gnome.org/World/ShellExtensions/desktop-icons/-/merge_requests/186 [6] https://gitlab.gnome.org/World/ShellExtensions/desktop-icons/-/merge_requests/195 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1948008/+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 1949116] Re: libgl1-mesa-dri depends on libllvm12 from universe
Given that llvm12 is in main for Focal and Impish maybe it should be for Hirsute too? ** Description changed: - It's not possible to install libgl1-mesa-dri from hirsute-updates on a - system that does not have universe enabled because it depends on - libllvm12 from universe. This was not the case with the version of - libgl1-mesa-dri in the release pocket because it depended upon - libllvm11. + It's not possible to install libgl1-mesa-dri from hirsute-updates (SRU + bug 1932311) on a system that does not have universe enabled because it + depends on libllvm12 from universe. This was not the case with the + version of libgl1-mesa-dri in the release pocket because it depended + upon libllvm11. (hirsute-amd64)root@impulse:~# apt-get install libgl1-mesa-dri Reading package lists... Done Building dependency tree... Done Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: - libgl1-mesa-dri : Depends: libllvm12 (>= 1:9~svn298832-1~) but it is not installable + libgl1-mesa-dri : Depends: libllvm12 (>= 1:9~svn298832-1~) but it is not installable E: Unable to correct problems, you have held broken packages. (hirsute-amd64)root@impulse:~# apt-cache show libgl1-mesa-dri Package: libgl1-mesa-dri Architecture: amd64 Version: 21.0.3-0ubuntu0.3 Multi-Arch: same Priority: optional Section: libs Source: mesa Origin: Ubuntu Maintainer: Ubuntu Developers Original-Maintainer: Debian X Strike Force Bugs: https://bugs.launchpad.net/ubuntu/+filebug Installed-Size: 37016 - Depends: libc6 (>= 2.33), libdrm-amdgpu1 (>= 2.4.100), libdrm-intel1 (>= 2.4.38), libdrm-nouveau2 (>= 2.4.66), libdrm-radeon1 (>= 2.4.31), + Depends: libc6 (>= 2.33), libdrm-amdgpu1 (>= 2.4.100), libdrm-intel1 (>= 2.4.38), libdrm-nouveau2 (>= 2.4.66), libdrm-radeon1 (>= 2.4.31), libdrm2 (>= 2.4.75), libelf1 (>= 0.142), libexpat1 (>= 2.0.1), libgcc-s1 (>= 3.4), libglapi-mesa (= 21.0.3-0ubuntu0.3), libllvm12 (>= 1:9~s vn298832-1~), libsensors5 (>= 1:3.5.0), libstdc++6 (>= 5.2), libvulkan1 (>= 1.2.131.2), libzstd1 (>= 1.3.2), zlib1g (>= 1:1.1.4) Filename: pool/main/m/mesa/libgl1-mesa-dri_21.0.3-0ubuntu0.3_amd64.deb This is blocking some CPC builds: https://launchpad.net/~cloud-images/+livefs/ubuntu/hirsute/cpc-development/+build/306039 ** Changed in: mesa (Ubuntu) Importance: Undecided => Critical -- 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/1949116 Title: libgl1-mesa-dri depends on libllvm12 from universe Status in mesa package in Ubuntu: New Bug description: It's not possible to install libgl1-mesa-dri from hirsute-updates (SRU bug 1932311) on a system that does not have universe enabled because it depends on libllvm12 from universe. This was not the case with the version of libgl1-mesa-dri in the release pocket because it depended upon libllvm11. (hirsute-amd64)root@impulse:~# apt-get install libgl1-mesa-dri Reading package lists... Done Building dependency tree... Done Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: libgl1-mesa-dri : Depends: libllvm12 (>= 1:9~svn298832-1~) but it is not installable E: Unable to correct problems, you have held broken packages. (hirsute-amd64)root@impulse:~# apt-cache show libgl1-mesa-dri Package: libgl1-mesa-dri Architecture: amd64 Version: 21.0.3-0ubuntu0.3 Multi-Arch: same Priority: optional Section: libs Source: mesa Origin: Ubuntu Maintainer: Ubuntu Developers Original-Maintainer: Debian X Strike Force Bugs: https://bugs.launchpad.net/ubuntu/+filebug Installed-Size: 37016 Depends: libc6 (>= 2.33), libdrm-amdgpu1 (>= 2.4.100), libdrm-intel1 (>= 2.4.38), libdrm-nouveau2 (>= 2.4.66), libdrm-radeon1 (>= 2.4.31), libdrm2 (>= 2.4.75), libelf1 (>= 0.142), libexpat1 (>= 2.0.1), libgcc-s1 (>= 3.4), libglapi-mesa (= 21.0.3-0ubuntu0.3), libllvm12 (>= 1:9~s vn298832-1~), libsensors5 (>= 1:3.5.0), libstdc++6 (>= 5.2), libvulkan1 (>= 1.2.131.2), libzstd1 (>= 1.3.2), zlib1g (>= 1:1.1.4) Filename: pool/main/m/mesa/libgl1-mesa-dri_21.0.3-0ubuntu0.3_amd64.deb This is blocking some CPC builds: https://launchpad.net/~cloud-images/+livefs/ubuntu/hirsute/cpc-development/+build/306039 To manage notifications about this bug
[Desktop-packages] [Bug 1949116] [NEW] libgl1-mesa-dri depends on libllvm12 from universe
Public bug reported: It's not possible to install libgl1-mesa-dri from hirsute-updates (SRU bug 1932311) on a system that does not have universe enabled because it depends on libllvm12 from universe. This was not the case with the version of libgl1-mesa-dri in the release pocket because it depended upon libllvm11. (hirsute-amd64)root@impulse:~# apt-get install libgl1-mesa-dri Reading package lists... Done Building dependency tree... Done Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: libgl1-mesa-dri : Depends: libllvm12 (>= 1:9~svn298832-1~) but it is not installable E: Unable to correct problems, you have held broken packages. (hirsute-amd64)root@impulse:~# apt-cache show libgl1-mesa-dri Package: libgl1-mesa-dri Architecture: amd64 Version: 21.0.3-0ubuntu0.3 Multi-Arch: same Priority: optional Section: libs Source: mesa Origin: Ubuntu Maintainer: Ubuntu Developers Original-Maintainer: Debian X Strike Force Bugs: https://bugs.launchpad.net/ubuntu/+filebug Installed-Size: 37016 Depends: libc6 (>= 2.33), libdrm-amdgpu1 (>= 2.4.100), libdrm-intel1 (>= 2.4.38), libdrm-nouveau2 (>= 2.4.66), libdrm-radeon1 (>= 2.4.31), libdrm2 (>= 2.4.75), libelf1 (>= 0.142), libexpat1 (>= 2.0.1), libgcc-s1 (>= 3.4), libglapi-mesa (= 21.0.3-0ubuntu0.3), libllvm12 (>= 1:9~s vn298832-1~), libsensors5 (>= 1:3.5.0), libstdc++6 (>= 5.2), libvulkan1 (>= 1.2.131.2), libzstd1 (>= 1.3.2), zlib1g (>= 1:1.1.4) Filename: pool/main/m/mesa/libgl1-mesa-dri_21.0.3-0ubuntu0.3_amd64.deb This is blocking some CPC builds: https://launchpad.net/~cloud-images/+livefs/ubuntu/hirsute/cpc-development/+build/306039 ** Affects: mesa (Ubuntu) Importance: Critical Status: New ** Tags: regression-update -- 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/1949116 Title: libgl1-mesa-dri depends on libllvm12 from universe Status in mesa package in Ubuntu: New Bug description: It's not possible to install libgl1-mesa-dri from hirsute-updates (SRU bug 1932311) on a system that does not have universe enabled because it depends on libllvm12 from universe. This was not the case with the version of libgl1-mesa-dri in the release pocket because it depended upon libllvm11. (hirsute-amd64)root@impulse:~# apt-get install libgl1-mesa-dri Reading package lists... Done Building dependency tree... Done Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: libgl1-mesa-dri : Depends: libllvm12 (>= 1:9~svn298832-1~) but it is not installable E: Unable to correct problems, you have held broken packages. (hirsute-amd64)root@impulse:~# apt-cache show libgl1-mesa-dri Package: libgl1-mesa-dri Architecture: amd64 Version: 21.0.3-0ubuntu0.3 Multi-Arch: same Priority: optional Section: libs Source: mesa Origin: Ubuntu Maintainer: Ubuntu Developers Original-Maintainer: Debian X Strike Force Bugs: https://bugs.launchpad.net/ubuntu/+filebug Installed-Size: 37016 Depends: libc6 (>= 2.33), libdrm-amdgpu1 (>= 2.4.100), libdrm-intel1 (>= 2.4.38), libdrm-nouveau2 (>= 2.4.66), libdrm-radeon1 (>= 2.4.31), libdrm2 (>= 2.4.75), libelf1 (>= 0.142), libexpat1 (>= 2.0.1), libgcc-s1 (>= 3.4), libglapi-mesa (= 21.0.3-0ubuntu0.3), libllvm12 (>= 1:9~s vn298832-1~), libsensors5 (>= 1:3.5.0), libstdc++6 (>= 5.2), libvulkan1 (>= 1.2.131.2), libzstd1 (>= 1.3.2), zlib1g (>= 1:1.1.4) Filename: pool/main/m/mesa/libgl1-mesa-dri_21.0.3-0ubuntu0.3_amd64.deb This is blocking some CPC builds: https://launchpad.net/~cloud-images/+livefs/ubuntu/hirsute/cpc-development/+build/306039 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1949116/+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 1849346]
In my brand new Ubuntu 21.10 Impish has forced the change of Firefox as Snap, so I'm suffering Kerberos not working from inside the Firefox snap. Kerberos works fine at Linux level.KInit, KList, etc... shows that the tickets are assigned and handle correctly when requested. Which is different in our case that for normal people is that the use of Kerberos requires to set in firefox the preference "network.negotiate-auth.trusted-uris" which by default is not set. In my case it is set as network.negotiate-auth.trusted-uris=cern.ch I have everything setup correctly, linux and firefox snap, and the problem present so if somebody could guide me a bit I can output any log file/debug you wish to spot where the magic disappears. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1849346 Title: [snap] kerberos GSSAPI no longer works after deb->snap transition Status in Mozilla Firefox: New Status in chromium-browser package in Ubuntu: Confirmed Status in firefox package in Ubuntu: Confirmed Bug description: I configure AuthServerWhitelist as documented: https://www.chromium.org/developers/design-documents/http- authentication and can see my whitelisted domains in chrome://policy/ but websites that used to work with SPNEGO/GSSAPI/kerberos no longer work. I'm guessing the snap needs some sort of permission to use the kerberos ticket cache (or the plumbing to do so doesn't exist...). I can confirm that Chrome has the desired behavior. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1849346/+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 1916250] Re: gir1.2-signon-2.0 needs to declare replace on older releases (Groovy2Hirsute and Focal2Jammy)
I followed the test case on a focal chroot whoose sources.list file I modified to impish and the package install did not fail. Preparing to unpack .../7-libsignon-glib2_2.1-3ubuntu0.21.10_amd64.deb ... Unpacking libsignon-glib2:amd64 (2.1-3ubuntu0.21.10) ... Selecting previously unselected package gir1.2-signon-2.0:amd64. Preparing to unpack .../8-gir1.2-signon-2.0_2.1-3ubuntu0.21.10_amd64.deb ... Unpacking gir1.2-signon-2.0:amd64 (2.1-3ubuntu0.21.10) ... Replacing files in old package gir1.2-signon-1.0 (1.14+17.04.20161117-0ubuntu5) ... Preparing to unpack .../9-libsignon-glib-dev_2.1-3ubuntu0.21.10_amd64.deb ... Unpacking libsignon-glib-dev:amd64 (2.1-3ubuntu0.21.10) over (1.14+17.04.20161117-0ubuntu5) ... Setting up libtirpc-common (1.3.2-2) ... Setting up libsepol1-dev:amd64 (3.1-1ubuntu2) ... Setting up libfakeroot:amd64 (1.25.3-1.1ubuntu2) ... Setting up fakeroot (1.25.3-1.1ubuntu2) ... Setting up rpcsvc-proto (1.4.2-0ubuntu5) ... Setting up libffi8:amd64 (3.4.2-1ubuntu5) ... Setting up libc-dev-bin (2.34-0ubuntu3) ... Setting up libtirpc3:amd64 (1.3.2-2) ... Setting up libselinux1-dev:amd64 (3.1-3build2) ... Setting up libglib2.0-0:amd64 (2.68.4-1ubuntu1) ... No schema files found: doing nothing. Setting up libglib2.0-bin (2.68.4-1ubuntu1) ... Setting up libsignon-glib2:amd64 (2.1-3ubuntu0.21.10) ... Setting up libtirpc-dev:amd64 (1.3.2-2) ... Setting up libnsl2:amd64 (1.3.0-2build1) ... Setting up libgirepository-1.0-1:amd64 (1.68.0-1build2) ... Setting up libglib2.0-dev-bin (2.68.4-1ubuntu1) ... Setting up gir1.2-glib-2.0:amd64 (1.68.0-1build2) ... Setting up libnsl-dev:amd64 (1.3.0-2build1) ... Setting up gir1.2-signon-2.0:amd64 (2.1-3ubuntu0.21.10) ... Setting up libc6-dev:amd64 (2.34-0ubuntu3) ... Setting up libmount-dev:amd64 (2.36.1-8ubuntu2) ... Setting up libsignon-glib-dev:amd64 (2.1-3ubuntu0.21.10) ... Setting up libglib2.0-dev:amd64 (2.68.4-1ubuntu1) ... Processing triggers for libc-bin (2.34-0ubuntu3) ... ** Tags removed: verification-needed verification-needed-hirsute verification-needed-impish ** Tags added: verification-done verification-done-hirsute verification-done-impish -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libsignon-glib in Ubuntu. https://bugs.launchpad.net/bugs/1916250 Title: gir1.2-signon-2.0 needs to declare replace on older releases (Groovy2Hirsute and Focal2Jammy) Status in libsignon-glib package in Ubuntu: Fix Released Status in libsignon-glib source package in Hirsute: Fix Committed Status in libsignon-glib source package in Impish: Fix Committed Bug description: gir1.2-signon-1.0 from groovy gir1.2-signon-2.0 from hirsute above two packages ship the same file /usr/lib/python3/dist- packages/gi/overrides/Signon.py without specifying how to resolve the conflict. [Test Case] This can be simply tested with a focal schroot: 1) apt-get install vim libsignon-glib-dev 2) edit /etc/apt/sources.list replacing focal with hirsute 3) apt-get update 4) apt-get install libsignon-glib-dev With the version of libsignon-glib-dev from -proposed you'll no longer receive the 'dpkg: error' from below. Unpacking gir1.2-signon-2.0:amd64 (2.1-3) ... dpkg: error processing archive /var/cache/apt/archives/gir1.2-signon-2.0_2.1-3_amd64.deb (--unpack): trying to overwrite '/usr/lib/python3/dist-packages/gi/overrides/Signon.py', which is also in package gir1.2-signon-1.0 1.14+17.04.20161117-0ubuntu5 Errors were encountered while processing: /var/cache/apt/archives/gir1.2-signon-2.0_2.1-3_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) Probably needs a conflicts/replaces dependency added to the newer hirsute package. [Regression Potential] We are adding a replaces with gir1.2-signon-1.0 so anything that depends on that package would be broken but given that that package is no longer available after focal that seems fine. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libsignon-glib/+bug/1916250/+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 1949066] Re: [upstream] Chapter numbering "sublevels" not showing (Multilevel outline numbers not showing)
Launchpad has imported 10 comments from the remote bug at https://bugs.documentfoundation.org/show_bug.cgi?id=143990. If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. On 2021-08-21T13:04:46+00:00 Patch-public wrote: Description: Multilevel outline no longer shows the numbering characters when formatted using the Multilevel outline tool bar. Steps to Reproduce: 1. Open a new or existing LO Writer document 2. Enter line (paragraph) 3. Format it as a multilevel list using the tool bar and select the predefine example top row, third across 4. Enter a tab to select outline level then type text Actual Results: Outline is formatted with indenting and numbering delimiters Expected Results: Actual outline level number or letter should also be shown Reproducible: Always User Profile Reset: Yes Additional Info: Bug persists in 7.2.0.4 Bug not present in 7.1.4.2 or 7.1.5.2 Reported and verified https://ask.libreoffice.org/t/lo-7-2-0-multilevel-outline-numbering-no-longer-works/67188 Reply at: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1949066/comments/0 On 2021-08-21T13:07:49+00:00 Patch-public wrote: Created attachment 174459 Formating image Reply at: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1949066/comments/1 On 2021-08-21T20:21:38+00:00 Patch-public wrote: The bug actually effects all the tool bar multilevel outline formatting options except those using a symbol (no no actual numbering) or the numbering format 1.1 or 1.1.1 or 1.1.1.1 etc Reply at: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1949066/comments/2 On 2021-08-22T20:29:02+00:00 kompilainenn wrote: confirm in Version: 7.3.0.0.alpha0+ (x64) / LibreOffice Community Build ID: 4677345e3695bac158bb04048b4d5c608ed764b4 CPU threads: 4; OS: Windows 6.1 Service Pack 1 Build 7601; UI render: Skia/Raster; VCL: win Locale: ru-RU (ru_RU); UI: en-US Calc: CL but not in 7.1 => regression I bibisected it and got a sha for a bad commit: sha is 9987b518fca1476bd0ce8c86bcf6ac7c81f7b580 https://gerrit.libreoffice.org/c/core/+/118040 https://git.libreoffice.org/core/commit/9987b518fca1476bd0ce8c86bcf6ac7c81f7b580 Added to CC: Thorsten Behrens and Vasily Melenchuk Reply at: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1949066/comments/3 On 2021-08-24T10:17:09+00:00 Libreoffice-commits wrote: Vasily Melenchuk committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/1fd9116fbcd1a8d25f964087cd1d0eb15df8a2d1 tdf#143990: writer: default value for SetIncludeUpperLevels is 1 It will be available in 7.3.0. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback. Reply at: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1949066/comments/4 On 2021-08-25T05:36:33+00:00 Libreoffice-commits wrote: Vasily Melenchuk committed a patch related to this issue. It has been pushed to "libreoffice-7-2": https://git.libreoffice.org/core/commit/9eb836a1a5f0f4522337ff7b87c9a0a4c7e8ca57 tdf#143990: writer: default value for SetIncludeUpperLevels is 1 It will be available in 7.2.1. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback. Reply at: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1949066/comments/5 On 2021-08-25T20:51:51+00:00 kompilainenn wrote: verified in Version: 7.3.0.0.alpha0+ (x64) / LibreOffice Community Build ID: 4debb7e8cc12563f46d1aaa58afdcb831f21cc83 CPU threads: 4; OS: Windows 6.1 Service Pack 1 Build 7601; UI render: Skia/Raster; VCL: win Locale: ru-RU (ru_RU); UI: en-US Calc: CL Vasily, thanks for fixing Reply at: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1949066/comments/6 On 2021-08-30T14:09:37+00:00 Xiscofauli wrote: *** Bug
[Desktop-packages] [Bug 1916250] Re: gir1.2-signon-2.0 needs to declare replace on older releases (Groovy2Hirsute and Focal2Jammy)
I followed the test case on a focal system whose sources.list file I changed to hirsute and had no issues. Preparing to unpack .../8-gir1.2-signon-2.0_2.1-3ubuntu0.21.04_amd64.deb ... Unpacking gir1.2-signon-2.0:amd64 (2.1-3ubuntu0.21.04) ... Replacing files in old package gir1.2-signon-1.0 (1.14+17.04.20161117-0ubuntu5) ... Preparing to unpack .../9-libsignon-glib-dev_2.1-3ubuntu0.21.04_amd64.deb ... Unpacking libsignon-glib-dev:amd64 (2.1-3ubuntu0.21.04) over (1.14+17.04.20161117-0ubuntu5) ... Setting up libtirpc-common (1.3.1-1build1) ... Setting up libsepol1-dev:amd64 (3.1-1ubuntu1) ... Setting up libffi8ubuntu1:amd64 (3.4~20200819gead65ca871-0ubuntu5) ... Setting up libfakeroot:amd64 (1.25.3-1.1ubuntu2) ... Setting up fakeroot (1.25.3-1.1ubuntu2) ... Setting up rpcsvc-proto (1.4.2-0ubuntu4) ... Setting up libc-dev-bin (2.33-0ubuntu5) ... Setting up libtirpc3:amd64 (1.3.1-1build1) ... Setting up libselinux1-dev:amd64 (3.1-3build1) ... Setting up libglib2.0-0:amd64 (2.68.1-1~ubuntu21.04.1) ... No schema files found: doing nothing. Setting up libglib2.0-bin (2.68.1-1~ubuntu21.04.1) ... Setting up libsignon-glib2:amd64 (2.1-3ubuntu0.21.04) ... Setting up libtirpc-dev:amd64 (1.3.1-1build1) ... Setting up libnsl2:amd64 (1.3.0-0ubuntu3) ... Setting up libgirepository-1.0-1:amd64 (1.66.1-1build1) ... Setting up libglib2.0-dev-bin (2.68.1-1~ubuntu21.04.1) ... Setting up gir1.2-glib-2.0:amd64 (1.66.1-1build1) ... Setting up libnsl-dev:amd64 (1.3.0-0ubuntu3) ... Setting up gir1.2-signon-2.0:amd64 (2.1-3ubuntu0.21.04) ... Setting up libc6-dev:amd64 (2.33-0ubuntu5) ... Setting up libmount-dev:amd64 (2.36.1-7ubuntu2) ... Setting up libsignon-glib-dev:amd64 (2.1-3ubuntu0.21.04) ... Setting up libglib2.0-dev:amd64 (2.68.1-1~ubuntu21.04.1) ... Processing triggers for libc-bin (2.33-0ubuntu5) ... -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libsignon-glib in Ubuntu. https://bugs.launchpad.net/bugs/1916250 Title: gir1.2-signon-2.0 needs to declare replace on older releases (Groovy2Hirsute and Focal2Jammy) Status in libsignon-glib package in Ubuntu: Fix Released Status in libsignon-glib source package in Hirsute: Fix Committed Status in libsignon-glib source package in Impish: Fix Committed Bug description: gir1.2-signon-1.0 from groovy gir1.2-signon-2.0 from hirsute above two packages ship the same file /usr/lib/python3/dist- packages/gi/overrides/Signon.py without specifying how to resolve the conflict. [Test Case] This can be simply tested with a focal schroot: 1) apt-get install vim libsignon-glib-dev 2) edit /etc/apt/sources.list replacing focal with hirsute 3) apt-get update 4) apt-get install libsignon-glib-dev With the version of libsignon-glib-dev from -proposed you'll no longer receive the 'dpkg: error' from below. Unpacking gir1.2-signon-2.0:amd64 (2.1-3) ... dpkg: error processing archive /var/cache/apt/archives/gir1.2-signon-2.0_2.1-3_amd64.deb (--unpack): trying to overwrite '/usr/lib/python3/dist-packages/gi/overrides/Signon.py', which is also in package gir1.2-signon-1.0 1.14+17.04.20161117-0ubuntu5 Errors were encountered while processing: /var/cache/apt/archives/gir1.2-signon-2.0_2.1-3_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) Probably needs a conflicts/replaces dependency added to the newer hirsute package. [Regression Potential] We are adding a replaces with gir1.2-signon-1.0 so anything that depends on that package would be broken but given that that package is no longer available after focal that seems fine. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libsignon-glib/+bug/1916250/+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 1949066] Re: [upstream] Chapter numbering "sublevels" not showing (Multilevel outline numbers not showing)
** Bug watch added: Document Foundation Bugzilla #143990 https://bugs.documentfoundation.org/show_bug.cgi?id=143990 ** Also affects: df-libreoffice via https://bugs.documentfoundation.org/show_bug.cgi?id=143990 Importance: Unknown Status: Unknown -- 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/1949066 Title: [upstream] Chapter numbering "sublevels" not showing (Multilevel outline numbers not showing) Status in LibreOffice: Unknown Status in libreoffice package in Ubuntu: New Bug description: On LibreOffice 7.2.2.2, using the "Chapter Numbering"→"Show Sublevels" feature to create nested chapter numbers (e.g., 1.1, 1.A, etc.) doesn't seem to be working. This was reported (and apparently fixed) upstream, but still seems to be present in the Ubuntu version: https://bugs.documentfoundation.org/show_bug.cgi?id=143990 My package versions seem to be: 1:7.2.2-0ubuntu0.21.10.1 To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1949066/+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 1948704] Re: segfault with gnome-shell & gdm-session-worker
memtest showing now errors I uploaded the results of ubuntu-bug:
cat /var/crash/_usr_lib_gdm3_gdm-session-worker.0.uploaded
0d1b7258-3816-11ec-ae83-fa163e102db1
Perhaps the stacktrace will help or perhaps warnings can be added if memory is
suspected?
Thread 3 (Thread 0x7f9f50e77700 (LWP 1292)):
#0 0x7f9f518eaaff in __GI___poll (fds=0x5565cc27c700, nfds=1, timeout=-1)
at ../sysdeps/unix/sysv/linux/poll.c:29
resultvar = 18446744073709551100
sc_cancel_oldtype = 0
#1 0x7f9f51bab36e in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2 0x7f9f51bab4a3 in g_main_context_iteration () at
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3 0x7f9f51bab4f1 in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#4 0x7f9f51bd4ad1 in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#5 0x7f9f519d0609 in start_thread (arg=) at
pthread_create.c:477
ret =
pd =
unwind_buf = {cancel_jmp_buf = {{jmp_buf = {140322233874176,
1304645551131517484, 140731730720206, 140731730720207, 140731730720352, 140
322233871936, -1358492822650691028, -1358491638588054996}, mask_was_saved =
0}}, priv = {pad = {0x0, 0x0, 0x0, 0x0}, data = {prev = 0x0, cleanup
= 0x0, canceltype = 0}}}
not_first_call = 0
#6 0x7f9f518f7293 in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95
.
Thread 2 (Thread 0x7f9f4bfff700 (LWP 1293)):
#0 0x7f9f518eaaff in __GI___poll (fds=0x5565cc294470, nfds=3, timeout=-1)
at ../sysdeps/unix/sysv/linux/poll.c:29
resultvar = 18446744073709551100
sc_cancel_oldtype = 0
#1 0x7f9f51bab36e in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2 0x7f9f51bab6f3 in g_main_loop_run () at
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3 0x7f9f51e00f8a in () at /lib/x86_64-linux-gnu/libgio-2.0.so.0
#4 0x7f9f51bd4ad1 in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#5 0x7f9f519d0609 in start_thread (arg=) at
pthread_create.c:477
ret =
pd =
unwind_buf = {cancel_jmp_buf = {{jmp_buf = {140322151593728,
1304645551131517484, 140731730720638, 140731730720639, 140731730720784,
140322151591488, -1358504028220366292, -1358491638588054996}, mask_was_saved =
0}}, priv = {pad = {0x0, 0x0, 0x0, 0x0}, data = {prev = 0x0, cleanup = 0x0,
canceltype = 0}}}
not_first_call = 0
#6 0x7f9f518f7293 in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95
.
Thread 1 (Thread 0x7f9f513e9040 (LWP 1291)):
#0 0x7f9f506256e7 in () at /lib/x86_64-linux-gnu/security/pam_systemd.so
#1 0x7f9f5062c02a in () at /lib/x86_64-linux-gnu/security/pam_systemd.so
#2 0x7f9f5061e279 in () at /lib/x86_64-linux-gnu/security/pam_systemd.so
#3 0x7f9f50623b6a in () at /lib/x86_64-linux-gnu/security/pam_systemd.so
#4 0x7f9f5063478a in () at /lib/x86_64-linux-gnu/security/pam_systemd.so
#5 0x7f9f506378be in pam_sm_close_session () at
/lib/x86_64-linux-gnu/security/pam_systemd.so
#6 0x7f9f51a1a056 in () at /lib/x86_64-linux-gnu/libpam.so.0
#7 0x5565cbf9b8e7 in ()
#8 0x5565cbf9b9a6 in ()
#9 0x7f9f51ba7338 in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#10 0x7f9f51bab04e in g_main_context_dispatch () at
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#11 0x7f9f51bab400 in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#12 0x7f9f51bab6f3 in g_main_loop_run () at
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#13 0x5565cbf92413 in ()
#14 0x7f9f517fc0b3 in __libc_start_main (main=0x5565cbf92290, argc=1,
argv=0x7ffea8d18798, init=, fini=,
rtld_fini=, stack_end=0x7ffea8d18788) at ../csu/libc-start.c:308
result =
unwind_buf = {cancel_jmp_buf = {{jmp_buf = {93895702292016,
1304645551131517484, 93895702160560, 140731730724752, 0, 0,
-1304256548182367700, -1358491932716506580}, mask_was_saved = 0}}, priv = {pad
= {0x0, 0x0, 0x1, 0x7ffea8d18798}, data = {prev = 0x0, cleanup = 0x0,
canceltype = 1}}}
not_first_call =
#15 0x5565cbf924de in ()
== Title =
gdm-session-worker crashed with SIGSEGV
** Attachment added: "pic of memtest no errors"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1948704/+attachment/5536832/+files/IMG_0334.jpg
--
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/1948704
Title:
segfault with gnome-shell & gdm-session-worker
Status in gnome-shell package in Ubuntu:
Incomplete
Bug description:
Using Ubuntu 20.04.3 LTS with 5.11.0-38-generic #42~20.04.1-Ubuntu,
gnome-shell/focal-updates,now 3.36.9-0ubuntu0.20.04.2 amd64
[installed,automatic]
gnome-shell/focal-security 3.36.4-1ubuntu1~20.04.2 amd64
gnome-shell/focal 3.36.1-5ubuntu1 amd64
gnome-session/focal,focal 3.36.0-2ubuntu1 all
Oct 22 19:41:09 ourserver kernel: [15260.574496] show_signal_msg: 29
callbacks suppressed
Oct 22 19:41:09 ourserver kernel: [15260.574503] gnome-shell[1475]:
[Desktop-packages] [Bug 1949105] Re: executable text activation does not work
Thank you for your bug report, could you explain what you mean by 'executable text activation'? Describing steps to trigger the issue and the error in details would help to understand what you describe ** Changed in: nautilus (Ubuntu) Importance: Undecided => Low ** Changed in: nautilus (Ubuntu) Status: New => Incomplete -- 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/1949105 Title: executable text activation does not work Status in nautilus package in Ubuntu: Incomplete Bug description: I upgraded my Ubuntu from 21.04 to 21.10. The executable text activation does not work in 21.10. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: nautilus 1:40.2-1ubuntu1 ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14 Uname: Linux 5.13.0-20-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu Oct 28 20:23:12 2021 InstallationDate: Installed on 2020-10-07 (385 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: nautilus UpgradeStatus: Upgraded to impish on 2021-10-14 (13 days ago) usr_lib_nautilus: evince40.4-2 file-roller 3.40.0-2 nautilus-extension-gnome-terminal 3.38.1-1ubuntu2 nautilus-share0.7.3-2ubuntu4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1949105/+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 1942385] Re: [SOF - sof-bytcht rt5640, playback] fails after a while
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: alsa-driver (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1942385 Title: [SOF - sof-bytcht rt5640, playback] fails after a while Status in alsa-driver package in Ubuntu: Confirmed Bug description: I am experiencing beep sound and audio from zoom, firefox, or vlc. It might play media for some seconds then beep. This has something to do with pipewire and sof driver and S16_LE format.( I read online). If I switch the profile Play HiFi quality Music in pavucontrol it does correct the beep sound for some few seconds then it ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.13.0-14.14-generic 5.13.1 Uname: Linux 5.13.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu68 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bret 1249 F pulseaudio /dev/snd/pcmC0D0c: bret 1249 F...m pulseaudio /dev/snd/pcmC0D0p: bret 1249 F...m pulseaudio /dev/snd/timer: bret 1249 f pulseaudio CasperMD5CheckResult: pass CurrentDesktop: XFCE Date: Thu Sep 2 05:25:01 2021 InstallationDate: Installed on 2021-08-29 (3 days ago) InstallationMedia: Xubuntu 21.10 "Impish Indri" - Alpha amd64 (20210612) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_Card: Built-in Audio - sof-bytcht rt5640 Symptom_PulseAudioLog: Sep 02 05:24:14 toshiba systemd[826]: pulseaudio.service: Deactivated successfully. Sep 02 05:24:25 toshiba systemd[826]: pulseaudio.socket: Deactivated successfully. Symptom_Type: Sound works for a while, then breaks Title: [SOF - sof-bytcht rt5640, playback] fails after a while UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/02/2015 dmi.bios.release: 5.20 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 5.20 dmi.board.name: 0700 dmi.board.vendor: FF50 dmi.board.version: Type2 - Board Version dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: OEM Chassis ManuFacturer dmi.chassis.version: OEM Chassis Version dmi.ec.firmware.release: 5.20 dmi.modalias: dmi:bvnINSYDECorp.:bvr5.20:bd11/02/2015:br5.20:efr5.20:svnTOSHIBA:pnSATELLITEClickMiniL9W-B:pvrPDW0FE-002005EN:skuINVALID:rvnFF50:rn0700:rvrType2-BoardVersion:cvnOEMChassisManuFacturer:ct10:cvrOEMChassisVersion: dmi.product.family: INVALID dmi.product.name: SATELLITE Click Mini L9W-B dmi.product.sku: INVALID dmi.product.version: PDW0FE-002005EN dmi.sys.vendor: TOSHIBA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1942385/+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 1949105] [NEW] executable text activation does not work
Public bug reported: I upgraded my Ubuntu from 21.04 to 21.10. The executable text activation does not work in 21.10. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: nautilus 1:40.2-1ubuntu1 ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14 Uname: Linux 5.13.0-20-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu Oct 28 20:23:12 2021 InstallationDate: Installed on 2020-10-07 (385 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: nautilus UpgradeStatus: Upgraded to impish on 2021-10-14 (13 days ago) usr_lib_nautilus: evince40.4-2 file-roller 3.40.0-2 nautilus-extension-gnome-terminal 3.38.1-1ubuntu2 nautilus-share0.7.3-2ubuntu4 ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug impish -- 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/1949105 Title: executable text activation does not work Status in nautilus package in Ubuntu: New Bug description: I upgraded my Ubuntu from 21.04 to 21.10. The executable text activation does not work in 21.10. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: nautilus 1:40.2-1ubuntu1 ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14 Uname: Linux 5.13.0-20-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu Oct 28 20:23:12 2021 InstallationDate: Installed on 2020-10-07 (385 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: nautilus UpgradeStatus: Upgraded to impish on 2021-10-14 (13 days ago) usr_lib_nautilus: evince40.4-2 file-roller 3.40.0-2 nautilus-extension-gnome-terminal 3.38.1-1ubuntu2 nautilus-share0.7.3-2ubuntu4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1949105/+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 1914992] Re: gnome-calendar crashes after a few clicks when creating event or un/toggling which calendar to show
Thank you for your bug report but Mint issue should be reported to the corresponding project and not Ubuntu ** Changed in: gnome-calendar (Ubuntu) Importance: Undecided => Low ** Changed in: gnome-calendar (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-calendar in Ubuntu. https://bugs.launchpad.net/bugs/1914992 Title: gnome-calendar crashes after a few clicks when creating event or un/toggling which calendar to show Status in gnome-calendar package in Ubuntu: Invalid Bug description: I am using gnome-calendar (3.36.2) on Linux Mint 20 (Ulyana), Cinnamon 4.6.7. I am able to replicate the crash by opening gnome-calendar, then clicking on "Manage your calendars" and toggling / untoggling different calendars at random. Here's a log from journalctl if it's of use: -- The job identifier is 27260. Feb 08 01:44:15 saturn org.gnome.Calendar[249540]: ** Feb 08 01:44:15 saturn org.gnome.Calendar[249540]: GcalTimeline:ERROR:../src/core/gcal-timeline.c:212:increase_completed_calendars: assertion failed: (self->completed_calendars <= g_hash_table_size (self->calendars)) Feb 08 01:44:15 saturn org.gnome.Calendar[249540]: Bail out! GcalTimeline:ERROR:../src/core/gcal-timeline.c:212:increase_completed_calendars: assertion failed: (self->completed_calendars <= g_hash_table_size (self->calendars)) Feb 08 01:44:15 saturn systemd[1]: Started Process Core Dump (PID 249641/UID 0). -- Subject: A start job for unit systemd-coredump@41-249641-0.service has finished successfully -- Defined-By: systemd -- Support: http://www.ubuntu.com/support -- -- A start job for unit systemd-coredump@41-249641-0.service has finished successfully. -- -- The job identifier is 27350. Feb 08 01:44:16 saturn systemd-coredump[249642]: Process 249540 (gnome-calendar) of user 1000 dumped core. Stack trace of thread 249540: #0 0x7f1ff002018b __GI_raise (libc.so.6 + 0x4618b) #1 0x7f1fe859 __GI_abort (libc.so.6 + 0x25859) #2 0x7f1ff0523b43 n/a (libglib-2.0.so.0 + 0x1db43) #3 0x7f1ff0580b2f g_assertion_message_expr (libglib-2.0.so.0 + 0x7ab2f) #4 0x5562ad7685a7 n/a (gnome-calendar + 0x455a7) #5 0x7f1ff0645a56 n/a (libgobject-2.0.so.0 + 0x14a56) #6 0x7f1ff0664b28 g_signal_emit_valist (libgobject-2.0.so.0 + 0x33b28) #7 0x7f1ff06650d3 g_signal_emit (libgobject-2.0.so.0 + 0x340d3) #8 0x5562ad7825ec n/a (gnome-calendar + 0x5f5ec) #9 0x7f1ff0557e6e g_main_context_dispatch (libglib-2.0.so.0 + 0x51e6e) #10 0x7f1ff0558220 n/a (libglib-2.0.so.0 + 0x52220) #11 0x7f1ff05582c3 g_main_context_iteration (libglib-2.0.so.0 + 0x522c3) #12 0x7f1ff0773fd5 g_application_run (libgio-2.0.so.0 + 0xe2fd5) #13 0x5562ad747532 main (gnome-calendar + 0x24532) #14 0x7f1ff00010b3 __libc_start_main (libc.so.6 + 0x270b3) #15 0x5562ad74757e _start (gnome-calendar + 0x2457e) Stack trace of thread 249544: #0 0x7f1ff00efaff __GI___poll (libc.so.6 + 0x115aff) #1 0x7f1ff055818e n/a (libglib-2.0.so.0 + 0x5218e) #2 0x7f1ff05582c3 g_main_context_iteration (libglib-2.0.so.0 + 0x522c3) #3 0x7f1ff155799d n/a (libdconfsettings.so + 0xa99d) #4 0x7f1ff0581911 n/a (libglib-2.0.so.0 + 0x7b911) #5 0x7f1fef452609 start_thread (libpthread.so.0 + 0x9609) #6 0x7f1ff00fc293 __clone (libc.so.6 + 0x122293) Stack trace of thread 249543: #0 0x7f1ff00efaff __GI___poll (libc.so.6 + 0x115aff) #1
[Desktop-packages] [Bug 1938658] Re: Week view goes blank when changing weeks or when user screen focus changes.
Thank you for desktop environment and theme do you use? Could you add the journalctl log after triggering the issue to the bug? ** Changed in: gnome-calendar (Ubuntu) Importance: Undecided => Low ** Changed in: gnome-calendar (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-calendar in Ubuntu. https://bugs.launchpad.net/bugs/1938658 Title: Week view goes blank when changing weeks or when user screen focus changes. Status in gnome-calendar package in Ubuntu: Incomplete Bug description: Description: Ubuntu 20.04.2 LTS Release: 20.04 gnome-calendar: Installed: 3.36.2-0ubuntu1 Candidate: 3.36.2-0ubuntu1 Version table: *** 3.36.2-0ubuntu1 500 500 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 3.36.1-1 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages Week view goes blank when changing weeks or when user screen focus changes. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-calendar/+bug/1938658/+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 1921687] Re: gnome-calendar doesn't import ics files correctly
Thank you for your bug report, the issue is likely an upstream one, you would probably have more chance to be worked on if you reported directly on https://gitlab.gnome.org/GNOME/gnome-calendar/-/issues ** Changed in: gnome-calendar (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-calendar in Ubuntu. https://bugs.launchpad.net/bugs/1921687 Title: gnome-calendar doesn't import ics files correctly Status in gnome-calendar package in Ubuntu: New Bug description: gnome-calendar doesn't import ics files correctly. 1. I downloaded public ics files like https://www.calendarlabs.com/ical-calendar/ics/76/US_Holidays.ics Their entries were shown in gnome-calendar, but not in gnome's date & time. In gnome-calendar they had an end date before the start date. The ics files from calendarlabs don't implement the standard from https://tools.ietf.org/html/rfc5545#section-3.6.1 for VEVENTs correctly. While the DATE from DTSTART is inclusive, the DATE from DTEND isn't. For a one day event DTEND's DATE has therefore to be one day after DTSTART's date. Some programs correct this by simply increasing DTEND by one day in these cases and gnome-calendar should do that too. As no event can end before it starts, gnome-calendar's behavior of setting the end date before the start date doesn't make sense. 2. If a VEVENT has a DTSTART property with a DATE but no DURATION and no DTEND property, according to https://tools.ietf.org/html/rfc5545#section-3.6.1 "the event's duration is taken to be one day." I therefore deleted the DTEND property in for instance US_Holidays.ics and expected that now gnome- calendar would import the ics file's VEVENTS correctly. But even in this case of standard conforming ics files gnome-calendar imported them with an end date before the start date. This time without the need to correct an error, but simply the need to implement a standard correctly. In both cases gnome-calendar shouldn't produce events with a end date before the start date. I used apport but again: I have ubuntu 20.04.2 LTS and an up to date gnome-calendar 3.36.2-0ubuntu1. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-calendar 3.36.2-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-70.78-generic 5.4.94 Uname: Linux 5.4.0-70-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Mar 29 02:46:12 2021 InstallationDate: Installed on 2018-08-10 (961 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: gnome-calendar UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-calendar/+bug/1921687/+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 1935669] Re: Gnome calendar app doesn't start
Thank you for your bug report. Did you keep log from the session where it didn't start? If not there is no way to debug the issue ** Changed in: gnome-calendar (Ubuntu) Status: New => Incomplete ** Changed in: gnome-calendar (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-calendar in Ubuntu. https://bugs.launchpad.net/bugs/1935669 Title: Gnome calendar app doesn't start Status in gnome-calendar package in Ubuntu: Incomplete Bug description: I installed the gnome-calendar app through snap and it doesn't start. Output of `dmesg -w` ``` [632748.772120] audit: type=1400 audit(1625822731.031:18470): apparmor="DENIED" operation="open" profile="snap.gnome-calendar.gnome-calendar" name="/var/lib/snapd/hostfs/usr/lib/x86_64-linux-gnu/libGL.so.1.7.0" pid=726971 comm="gnome-calendar" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 [632748.772122] audit: type=1400 audit(1625822731.031:18471): apparmor="DENIED" operation="open" profile="snap.gnome-calendar.gnome-calendar" name="/var/lib/snapd/hostfs/usr/lib/x86_64-linux-gnu/libEGL.so.1.1.0" pid=726971 comm="gnome-calendar" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 [632748.774023] audit: type=1400 audit(1625822731.031:18472): apparmor="DENIED" operation="open" profile="snap.gnome-calendar.gnome-calendar" name="/var/lib/snapd/hostfs/usr/lib/x86_64-linux-gnu/libGLX.so.0.0.0" pid=726971 comm="gnome-calendar" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 [632748.774025] audit: type=1400 audit(1625822731.031:18473): apparmor="DENIED" operation="open" profile="snap.gnome-calendar.gnome-calendar" name="/var/lib/snapd/hostfs/usr/lib/x86_64-linux-gnu/libGLdispatch.so.0.0.0" pid=726971 comm="gnome-calendar" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 ``` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-calendar/+bug/1935669/+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 1936826]
*** Bug 2018028 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 gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1936826
Title:
gnome-shell crashed with SIGSEGV in st_focus_manager_remove_group()
[st-focus-manager.c:199]
Status in GNOME Shell:
Unknown
Status in gnome-shell package in Ubuntu:
Fix Released
Status in gnome-shell package in Fedora:
Confirmed
Bug description:
https://errors.ubuntu.com/problem/a7fed12980ff951be9a10c4f2e04d99a23b010ae
---
Testing daily Ubuntu Impish ISO 2021-07-19
Test machine : Dell [Latitude] 7280 (i5-7300U,
Received the error message - Ubuntu has experienced an internal error
...do you want to send ...etc, etc.
This bug occurred when I was scrolling up and down on the "Settings"
app and selected "Appearance".
ProblemType: Crash
DistroRelease: Ubuntu 21.10
Package: gnome-shell 40.2-1ubuntu1
ProcVersionSignature: Ubuntu 5.11.0-20.21+21.10.1-generic 5.11.21
Uname: Linux 5.11.0-20-generic x86_64
ApportVersion: 2.20.11-0ubuntu67
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Mon Jul 19 12:15:54 2021
DisplayManager: gdm3
ExecutablePath: /usr/bin/gnome-shell
GsettingsChanges:
b'org.gnome.shell' b'welcome-dialog-last-shown-version' b"'40.2'"
b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'is')]"
b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
b'org.gnome.desktop.privacy' b'report-technical-problems' b'true'
InstallationDate: Installed on 2021-07-19 (0 days ago)
InstallationMedia: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210719)
ProcCmdline: /usr/bin/gnome-shell
RelatedPackageVersions: mutter-common 40.2.1-1ubuntu1
Signal: 11
SourcePackage: gnome-shell
StacktraceTop:
st_focus_manager_remove_group () from /usr/lib/gnome-shell/libst-1.0.so
g_closure_invoke () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
g_signal_emit_valist () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
g_signal_emit () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: gnome-shell crashed with SIGSEGV in st_focus_manager_remove_group()
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/gnome-shell/+bug/1936826/+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 1936826]
*** Bug 2018187 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 gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1936826
Title:
gnome-shell crashed with SIGSEGV in st_focus_manager_remove_group()
[st-focus-manager.c:199]
Status in GNOME Shell:
Unknown
Status in gnome-shell package in Ubuntu:
Fix Released
Status in gnome-shell package in Fedora:
Confirmed
Bug description:
https://errors.ubuntu.com/problem/a7fed12980ff951be9a10c4f2e04d99a23b010ae
---
Testing daily Ubuntu Impish ISO 2021-07-19
Test machine : Dell [Latitude] 7280 (i5-7300U,
Received the error message - Ubuntu has experienced an internal error
...do you want to send ...etc, etc.
This bug occurred when I was scrolling up and down on the "Settings"
app and selected "Appearance".
ProblemType: Crash
DistroRelease: Ubuntu 21.10
Package: gnome-shell 40.2-1ubuntu1
ProcVersionSignature: Ubuntu 5.11.0-20.21+21.10.1-generic 5.11.21
Uname: Linux 5.11.0-20-generic x86_64
ApportVersion: 2.20.11-0ubuntu67
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Mon Jul 19 12:15:54 2021
DisplayManager: gdm3
ExecutablePath: /usr/bin/gnome-shell
GsettingsChanges:
b'org.gnome.shell' b'welcome-dialog-last-shown-version' b"'40.2'"
b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'is')]"
b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
b'org.gnome.desktop.privacy' b'report-technical-problems' b'true'
InstallationDate: Installed on 2021-07-19 (0 days ago)
InstallationMedia: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210719)
ProcCmdline: /usr/bin/gnome-shell
RelatedPackageVersions: mutter-common 40.2.1-1ubuntu1
Signal: 11
SourcePackage: gnome-shell
StacktraceTop:
st_focus_manager_remove_group () from /usr/lib/gnome-shell/libst-1.0.so
g_closure_invoke () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
g_signal_emit_valist () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
g_signal_emit () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: gnome-shell crashed with SIGSEGV in st_focus_manager_remove_group()
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/gnome-shell/+bug/1936826/+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 1936826]
*** Bug 2017149 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 gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1936826
Title:
gnome-shell crashed with SIGSEGV in st_focus_manager_remove_group()
[st-focus-manager.c:199]
Status in GNOME Shell:
Unknown
Status in gnome-shell package in Ubuntu:
Fix Released
Status in gnome-shell package in Fedora:
Confirmed
Bug description:
https://errors.ubuntu.com/problem/a7fed12980ff951be9a10c4f2e04d99a23b010ae
---
Testing daily Ubuntu Impish ISO 2021-07-19
Test machine : Dell [Latitude] 7280 (i5-7300U,
Received the error message - Ubuntu has experienced an internal error
...do you want to send ...etc, etc.
This bug occurred when I was scrolling up and down on the "Settings"
app and selected "Appearance".
ProblemType: Crash
DistroRelease: Ubuntu 21.10
Package: gnome-shell 40.2-1ubuntu1
ProcVersionSignature: Ubuntu 5.11.0-20.21+21.10.1-generic 5.11.21
Uname: Linux 5.11.0-20-generic x86_64
ApportVersion: 2.20.11-0ubuntu67
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Mon Jul 19 12:15:54 2021
DisplayManager: gdm3
ExecutablePath: /usr/bin/gnome-shell
GsettingsChanges:
b'org.gnome.shell' b'welcome-dialog-last-shown-version' b"'40.2'"
b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'is')]"
b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
b'org.gnome.desktop.privacy' b'report-technical-problems' b'true'
InstallationDate: Installed on 2021-07-19 (0 days ago)
InstallationMedia: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210719)
ProcCmdline: /usr/bin/gnome-shell
RelatedPackageVersions: mutter-common 40.2.1-1ubuntu1
Signal: 11
SourcePackage: gnome-shell
StacktraceTop:
st_focus_manager_remove_group () from /usr/lib/gnome-shell/libst-1.0.so
g_closure_invoke () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
g_signal_emit_valist () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
g_signal_emit () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: gnome-shell crashed with SIGSEGV in st_focus_manager_remove_group()
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/gnome-shell/+bug/1936826/+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 1936826]
*** Bug 2017987 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 gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1936826
Title:
gnome-shell crashed with SIGSEGV in st_focus_manager_remove_group()
[st-focus-manager.c:199]
Status in GNOME Shell:
Unknown
Status in gnome-shell package in Ubuntu:
Fix Released
Status in gnome-shell package in Fedora:
Confirmed
Bug description:
https://errors.ubuntu.com/problem/a7fed12980ff951be9a10c4f2e04d99a23b010ae
---
Testing daily Ubuntu Impish ISO 2021-07-19
Test machine : Dell [Latitude] 7280 (i5-7300U,
Received the error message - Ubuntu has experienced an internal error
...do you want to send ...etc, etc.
This bug occurred when I was scrolling up and down on the "Settings"
app and selected "Appearance".
ProblemType: Crash
DistroRelease: Ubuntu 21.10
Package: gnome-shell 40.2-1ubuntu1
ProcVersionSignature: Ubuntu 5.11.0-20.21+21.10.1-generic 5.11.21
Uname: Linux 5.11.0-20-generic x86_64
ApportVersion: 2.20.11-0ubuntu67
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Mon Jul 19 12:15:54 2021
DisplayManager: gdm3
ExecutablePath: /usr/bin/gnome-shell
GsettingsChanges:
b'org.gnome.shell' b'welcome-dialog-last-shown-version' b"'40.2'"
b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'is')]"
b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
b'org.gnome.desktop.privacy' b'report-technical-problems' b'true'
InstallationDate: Installed on 2021-07-19 (0 days ago)
InstallationMedia: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210719)
ProcCmdline: /usr/bin/gnome-shell
RelatedPackageVersions: mutter-common 40.2.1-1ubuntu1
Signal: 11
SourcePackage: gnome-shell
StacktraceTop:
st_focus_manager_remove_group () from /usr/lib/gnome-shell/libst-1.0.so
g_closure_invoke () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
g_signal_emit_valist () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
g_signal_emit () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: gnome-shell crashed with SIGSEGV in st_focus_manager_remove_group()
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/gnome-shell/+bug/1936826/+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 1936826]
*** Bug 2017140 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 gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1936826
Title:
gnome-shell crashed with SIGSEGV in st_focus_manager_remove_group()
[st-focus-manager.c:199]
Status in GNOME Shell:
Unknown
Status in gnome-shell package in Ubuntu:
Fix Released
Status in gnome-shell package in Fedora:
Confirmed
Bug description:
https://errors.ubuntu.com/problem/a7fed12980ff951be9a10c4f2e04d99a23b010ae
---
Testing daily Ubuntu Impish ISO 2021-07-19
Test machine : Dell [Latitude] 7280 (i5-7300U,
Received the error message - Ubuntu has experienced an internal error
...do you want to send ...etc, etc.
This bug occurred when I was scrolling up and down on the "Settings"
app and selected "Appearance".
ProblemType: Crash
DistroRelease: Ubuntu 21.10
Package: gnome-shell 40.2-1ubuntu1
ProcVersionSignature: Ubuntu 5.11.0-20.21+21.10.1-generic 5.11.21
Uname: Linux 5.11.0-20-generic x86_64
ApportVersion: 2.20.11-0ubuntu67
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Mon Jul 19 12:15:54 2021
DisplayManager: gdm3
ExecutablePath: /usr/bin/gnome-shell
GsettingsChanges:
b'org.gnome.shell' b'welcome-dialog-last-shown-version' b"'40.2'"
b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'is')]"
b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
b'org.gnome.desktop.privacy' b'report-technical-problems' b'true'
InstallationDate: Installed on 2021-07-19 (0 days ago)
InstallationMedia: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210719)
ProcCmdline: /usr/bin/gnome-shell
RelatedPackageVersions: mutter-common 40.2.1-1ubuntu1
Signal: 11
SourcePackage: gnome-shell
StacktraceTop:
st_focus_manager_remove_group () from /usr/lib/gnome-shell/libst-1.0.so
g_closure_invoke () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
g_signal_emit_valist () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
g_signal_emit () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: gnome-shell crashed with SIGSEGV in st_focus_manager_remove_group()
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/gnome-shell/+bug/1936826/+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 1946440] Re: SRU: enable RTD3 only on laptops
All uploaded. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1946440 Title: SRU: enable RTD3 only on laptops Status in OEM Priority Project: New Status in ubuntu-drivers-common package in Ubuntu: Invalid Status in ubuntu-drivers-common source package in Focal: In Progress Status in ubuntu-drivers-common source package in Hirsute: In Progress Bug description: [Impact] * According to Nvidia README, the RTD3 doesn't support on non-laptop machine [Test Plan] * Installed Nvidia GPU driver * On laptop with Nvidia RTD3 supported GPU. Execute 'sudo gpu-manager', /run/nvidia_runtimepm_supported will be created [Where problems could occur] * With non-laptop machine use RTD3 supported GPU may use more power. But based on Nvidia READ, such case should not happen [Other Info] To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1946440/+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 1946434] Re: SRU: Set on-demand as default, enable RTD3 only on laptops and decouple on-demand with RTD3
I added a couple of fixes that you missed in the debdiffs, and I uploaded the packages. I put the changelogs for the uploads in the bug description. ** Description changed: [Impact] - * Ubuntu will set GPU mode to performance as default which may use more power + * Ubuntu will set GPU mode to performance as default which may use more power * User can't use GPU for other purpose (eg: deep-learning) if RTD3 is not supported * According to Nvidia README, the RTD3 doesn't support on non-laptop machine [Test Plan] * Install 20.04.3 with "Third-party packages". After the installation, reboot the system. Execute "prime-select query" should get "on-demand" * On non-laptop machine. Can set GPU mode to on-demand * On laptop with GPU in runtime PM support list. Set GPU mode to on-demand and Nvidia driver is loaded with "NVreg_DynamicPowerManagement=0x02" [Where problems could occur] - * on-demand mode supported after nvidia driver 450. And focal does not have nvidia driver lower than 450. + * on-demand mode supported after nvidia driver 450. And focal does not have nvidia driver lower than 450. * With GPU supported RTD3 not able enable runtime PM on non-laptop. But based on the Nvidia README, this case shall not happened. [Other Info] + + Changelogs: + + nvidia-prime (0.8.16~0.20.04.2) focal; urgency=medium + + [ Jeremy Szu ] + * Set on-demand mode as default nvidia mode (LP: #1942307) + + [ Alberto Milone ] + * prime-select: + - Detect chassis type and enable RTD3 only + on laptops (LP: #1942788). + - on-demand mode doesn't need to depend on + RTD3 (LP: #1942789). + - Use bootvga detection when last_gfx_boot + is not available. + - Don't check the current profile when setting + a profile (LP: #1946476). + - Catch BrokenPipeError. + - Use bootvga detection when last_gfx_boot is + not available. + + + nvidia-prime (0.8.16.2~0.21.04.1) hirsute; urgency=medium + + [ Jeremy Szu ] + * Set on-demand mode as default nvidia mode (LP: #1942307) + + [ Alberto Milone ] + * prime-select: + - Detect chassis type and enable RTD3 only + on laptops (LP: #1942788). + - on-demand mode doesn't need to depend on + RTD3 (LP: #1942789). + - Use bootvga detection when last_gfx_boot + is not available. + - Don't check the current profile when setting + a profile (LP: #1946476). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1946434 Title: SRU: Set on-demand as default, enable RTD3 only on laptops and decouple on-demand with RTD3 Status in OEM Priority Project: Confirmed Status in nvidia-prime package in Ubuntu: Invalid Status in nvidia-prime source package in Focal: In Progress Status in nvidia-prime source package in Hirsute: In Progress Bug description: [Impact] * Ubuntu will set GPU mode to performance as default which may use more power * User can't use GPU for other purpose (eg: deep-learning) if RTD3 is not supported * According to Nvidia README, the RTD3 doesn't support on non-laptop machine [Test Plan] * Install 20.04.3 with "Third-party packages". After the installation, reboot the system. Execute "prime-select query" should get "on-demand" * On non-laptop machine. Can set GPU mode to on-demand * On laptop with GPU in runtime PM support list. Set GPU mode to on-demand and Nvidia driver is loaded with "NVreg_DynamicPowerManagement=0x02" [Where problems could occur] * on-demand mode supported after nvidia driver 450. And focal does not have nvidia driver lower than 450. * With GPU supported RTD3 not able enable runtime PM on non-laptop. But based on the Nvidia README, this case shall not happened. [Other Info] Changelogs: nvidia-prime (0.8.16~0.20.04.2) focal; urgency=medium [ Jeremy Szu ] * Set on-demand mode as default nvidia mode (LP: #1942307) [ Alberto Milone ] * prime-select: - Detect chassis type and enable RTD3 only on laptops (LP: #1942788). - on-demand mode doesn't need to depend on RTD3 (LP: #1942789). - Use bootvga detection when last_gfx_boot is not available. - Don't check the current profile when setting a profile (LP: #1946476). - Catch BrokenPipeError. - Use bootvga detection when last_gfx_boot is not available. nvidia-prime (0.8.16.2~0.21.04.1) hirsute; urgency=medium [ Jeremy Szu ] * Set on-demand mode as default nvidia mode (LP: #1942307) [ Alberto Milone ] * prime-select: - Detect chassis type and enable RTD3 only on laptops (LP: #1942788). - on-demand mode doesn't need to depend on RTD3 (LP: #1942789). - Use bootvga detection when last_gfx_boot is not available. - Don't check the current profile
[Desktop-packages] [Bug 1946440] Re: SRU: enable RTD3 only on laptops
** Also affects: ubuntu-drivers-common (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: ubuntu-drivers-common (Ubuntu Hirsute) Importance: Undecided Status: New ** Changed in: ubuntu-drivers-common (Ubuntu Focal) Status: New => Triaged ** Changed in: ubuntu-drivers-common (Ubuntu Hirsute) Status: New => Triaged ** Changed in: ubuntu-drivers-common (Ubuntu Focal) Importance: Undecided => High ** Changed in: ubuntu-drivers-common (Ubuntu Hirsute) Importance: Undecided => High ** Changed in: ubuntu-drivers-common (Ubuntu Focal) Assignee: (unassigned) => Alberto Milone (albertomilone) ** Changed in: ubuntu-drivers-common (Ubuntu Hirsute) Assignee: (unassigned) => Alberto Milone (albertomilone) ** Changed in: ubuntu-drivers-common (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1946440 Title: SRU: enable RTD3 only on laptops Status in OEM Priority Project: New Status in ubuntu-drivers-common package in Ubuntu: Invalid Status in ubuntu-drivers-common source package in Focal: In Progress Status in ubuntu-drivers-common source package in Hirsute: In Progress Bug description: [Impact] * According to Nvidia README, the RTD3 doesn't support on non-laptop machine [Test Plan] * Installed Nvidia GPU driver * On laptop with Nvidia RTD3 supported GPU. Execute 'sudo gpu-manager', /run/nvidia_runtimepm_supported will be created [Where problems could occur] * With non-laptop machine use RTD3 supported GPU may use more power. But based on Nvidia READ, such case should not happen [Other Info] To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1946440/+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 1948008] Re: Copying and pasting to/from Nautilus does not work
** This bug is no longer a duplicate of bug 1843588 Nautilus doesn't copy filenames for paste to other programs anymore ** No longer affects: gnome-shell-extension-desktop-icons (Ubuntu Hirsute) ** Also affects: gnome-shell-extension-desktop-icons (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: gnome-shell-extension-desktop-icons-ng (Ubuntu) Importance: Undecided Status: New ** Also affects: gnome-shell-extension-desktop-icons (Ubuntu Impish) Importance: Undecided Status: New ** Also affects: gnome-shell-extension-desktop-icons-ng (Ubuntu Impish) Importance: Undecided Status: New ** Also affects: gnome-shell-extension-desktop-icons (Ubuntu Hirsute) Importance: Undecided Status: New ** Also affects: gnome-shell-extension-desktop-icons-ng (Ubuntu Hirsute) Importance: Undecided Status: New ** Changed in: gnome-shell-extension-desktop-icons (Ubuntu Impish) Status: New => Won't Fix ** Changed in: gnome-shell-extension-desktop-icons (Ubuntu Hirsute) Status: New => Won't Fix ** Changed in: gnome-shell-extension-desktop-icons-ng (Ubuntu Focal) Status: New => Won't Fix ** Also affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Changed in: gnome-shell (Ubuntu Hirsute) Status: New => Won't Fix ** Changed in: gnome-shell (Ubuntu Hirsute) Status: Won't Fix => Fix Released ** Changed in: gnome-shell (Ubuntu Impish) Status: New => Fix Released ** Changed in: gnome-shell (Ubuntu) Importance: Undecided => Low ** Changed in: gnome-shell-extension-desktop-icons (Ubuntu) Importance: Medium => Low ** Changed in: gnome-shell (Ubuntu Focal) Importance: Undecided => Low ** Changed in: gnome-shell-extension-desktop-icons (Ubuntu Focal) Importance: Undecided => Low ** Changed in: gnome-shell-extension-desktop-icons-ng (Ubuntu Hirsute) Importance: Undecided => Low ** Changed in: gnome-shell-extension-desktop-icons-ng (Ubuntu Impish) Importance: Undecided => Low ** Changed in: gnome-shell-extension-desktop-icons-ng (Ubuntu) Importance: Undecided => Low ** Changed in: gnome-shell-extension-desktop-icons (Ubuntu Hirsute) Status: Won't Fix => Invalid ** Changed in: gnome-shell-extension-desktop-icons (Ubuntu Impish) Status: Won't Fix => Invalid ** Changed in: gnome-shell-extension-desktop-icons-ng (Ubuntu Focal) Status: Won't Fix => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-desktop-icons in Ubuntu. https://bugs.launchpad.net/bugs/1948008 Title: Copying and pasting to/from Nautilus does not work Status in gnome-shell package in Ubuntu: New Status in gnome-shell-extension-desktop-icons package in Ubuntu: Incomplete Status in gnome-shell-extension-desktop-icons-ng package in Ubuntu: New Status in gnome-shell source package in Focal: New Status in gnome-shell-extension-desktop-icons source package in Focal: New Status in gnome-shell-extension-desktop-icons-ng source package in Focal: Invalid Status in gnome-shell source package in Hirsute: Fix Released Status in gnome-shell-extension-desktop-icons source package in Hirsute: Invalid Status in gnome-shell-extension-desktop-icons-ng source package in Hirsute: New Status in gnome-shell source package in Impish: Fix Released Status in gnome-shell-extension-desktop-icons source package in Impish: Invalid Status in gnome-shell-extension-desktop-icons-ng source package in Impish: New Bug description: [Impact] * After upstream Nautilus has reverted the following commit [1] related to upstream bug [2] the desktop icons extension lost it's ability to copy to/from nautilus. * This is related to the fact that before there was some metadata passed along in the clipboard along with text data. This was causing issues with compatibility with some applications that were not expecting any metadata (MIME type in this case) was glued to the text clipboard contents. Hence, it was reverted upstream [3]. * Fixing the root cause of this issue required changes to Nautilus [3], gnome-shell [4] and desktop-icons [5] [6]. Nautilus and gnome- shell parts are already implemented and present in Hirsute and Impish. [Test Plan] 1) Make sure desktop-icons extension is enabled. 2) Open nautilus window and copy any file from there by right-clicking and selecting "Copy" from the popup menu. 3) Right-click on desktop and select "Paste" from the context menu. Expected result: selected file is copied to the desktop. Actual result: "Paste" item is disabled in the menu. [Where problems could occur] * Mixing a version of nautilus without commit [3] and fixed version of desktop-icons may still lead to a scenario when copying will not work. * Any extension/application copying to desktop using the smuggled-in- text clipboard behavior
[Desktop-packages] [Bug 1843588] Re: Nautilus doesn't copy filenames for paste to other programs anymore
Marking as verified as per Michael's comment #12. -- 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/1843588 Title: Nautilus doesn't copy filenames for paste to other programs anymore Status in Nautilus: New Status in nautilus package in Ubuntu: Fix Released Status in nautilus source package in Focal: Fix Committed Bug description: [Impact] * One of the upstream changes changed behavior of clipboard copying files/directories from nautilus to applications accepting text only (e.g. gnome-terminal). In such case the pasted input is prefixed with: x-special/nautilus-clipboard copy file:// This was not the case in earlier releases and this change has been reverted in later upstream releases. Reverting the problematic commit will fix the usecase reported in this bug (and all applications where copying from Nautilus and pasting the data into a text-based input makes sense), but will break copying to/from Desktop Icons extension. I recommend reporting the Desktop Icons extension issue (present already in every later Ubuntu release) in a separate bug and track the fix there. [Test Plan] 1. Open nautilus. 2. Right-click on any file or directory and select 'Copy' from the context menu. 3. Open gnome-terminal and right-click paste the contents of the clipboard. Expected result: path of the file/directory is pasted in the terminal. Actual result: pasted input is prefixed with "x-special/nautilus-clipboard copy file://" [Where problems could occur] * There are some workarounds listed in the upstream bug so fixing the root cause may break environments with those workarounds in place. * Reverting this change also limits functionality of the desktop icons extension shipped with Ubuntu. Namely: before the new clipboard API is used in desktop-icons (merge requests [1] and [2]) copying and pasting to/from the desktop extension to a nautilus will not be possible via keyboard shortcuts or context menu (dragging and dropping will remain to work). [1] https://gitlab.gnome.org/World/ShellExtensions/desktop-icons/-/merge_requests/186 [2] https://gitlab.gnome.org/World/ShellExtensions/desktop-icons/-/merge_requests/195 [Other Info] Original bug description: Until Ubuntu 18.10 Nautilus does copy all selected filenames in simple Text format and this way you cold paste the selected files as a list to other programs: for example into the texteditor gedit. This was a very useful function if you have, for example, to upload a file to webmail or other web-service. You cold copy the file within nautilus and paste it directliy to the selection dialog or webfield to upload the file. Or if you wanted a simple List of all your files in a folder you where able to select all files with nautilus, copy and paste into gedit. This is not possible anymore. The output of natilus looks now like this: x-special/nautilus-clipboard copy file:///home//Schreibtisch/new%20document.txt Until Ubuntu 18.10 this looks like this: /home//Schreibtisch/new document.txt Steps to reproduce: 1. Select files with nautilus 2. Press Ctrl+C 3. open gedit 4. press Ctrl+V ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: nautilus 1:3.32.1-0ubuntu0.19.04.0 ProcVersionSignature: Ubuntu 5.0.0-27.28-generic 5.0.21 Uname: Linux 5.0.0-27-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Sep 11 15:06:14 2019 ExecutablePath: /usr/bin/nautilus SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1843588/+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 1843588] Re: Nautilus doesn't copy filenames for paste to other programs anymore
thanks for testing it Michael. Regarding desktop-icons: afaik there's still no fix for it. ** No longer affects: gnome-shell (Ubuntu) ** No longer affects: gnome-shell-extension-desktop-icons (Ubuntu) ** No longer affects: gnome-shell (Ubuntu Focal) ** No longer affects: gnome-shell-extension-desktop-icons (Ubuntu Focal) ** Tags removed: verification-needed verification-needed-focal ** Tags added: verification-done verification-done-focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1843588 Title: Nautilus doesn't copy filenames for paste to other programs anymore Status in Nautilus: New Status in nautilus package in Ubuntu: Fix Released Status in nautilus source package in Focal: Fix Committed Bug description: [Impact] * One of the upstream changes changed behavior of clipboard copying files/directories from nautilus to applications accepting text only (e.g. gnome-terminal). In such case the pasted input is prefixed with: x-special/nautilus-clipboard copy file:// This was not the case in earlier releases and this change has been reverted in later upstream releases. Reverting the problematic commit will fix the usecase reported in this bug (and all applications where copying from Nautilus and pasting the data into a text-based input makes sense), but will break copying to/from Desktop Icons extension. I recommend reporting the Desktop Icons extension issue (present already in every later Ubuntu release) in a separate bug and track the fix there. [Test Plan] 1. Open nautilus. 2. Right-click on any file or directory and select 'Copy' from the context menu. 3. Open gnome-terminal and right-click paste the contents of the clipboard. Expected result: path of the file/directory is pasted in the terminal. Actual result: pasted input is prefixed with "x-special/nautilus-clipboard copy file://" [Where problems could occur] * There are some workarounds listed in the upstream bug so fixing the root cause may break environments with those workarounds in place. * Reverting this change also limits functionality of the desktop icons extension shipped with Ubuntu. Namely: before the new clipboard API is used in desktop-icons (merge requests [1] and [2]) copying and pasting to/from the desktop extension to a nautilus will not be possible via keyboard shortcuts or context menu (dragging and dropping will remain to work). [1] https://gitlab.gnome.org/World/ShellExtensions/desktop-icons/-/merge_requests/186 [2] https://gitlab.gnome.org/World/ShellExtensions/desktop-icons/-/merge_requests/195 [Other Info] Original bug description: Until Ubuntu 18.10 Nautilus does copy all selected filenames in simple Text format and this way you cold paste the selected files as a list to other programs: for example into the texteditor gedit. This was a very useful function if you have, for example, to upload a file to webmail or other web-service. You cold copy the file within nautilus and paste it directliy to the selection dialog or webfield to upload the file. Or if you wanted a simple List of all your files in a folder you where able to select all files with nautilus, copy and paste into gedit. This is not possible anymore. The output of natilus looks now like this: x-special/nautilus-clipboard copy file:///home//Schreibtisch/new%20document.txt Until Ubuntu 18.10 this looks like this: /home//Schreibtisch/new document.txt Steps to reproduce: 1. Select files with nautilus 2. Press Ctrl+C 3. open gedit 4. press Ctrl+V ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: nautilus 1:3.32.1-0ubuntu0.19.04.0 ProcVersionSignature: Ubuntu 5.0.0-27.28-generic 5.0.21 Uname: Linux 5.0.0-27-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Sep 11 15:06:14 2019 ExecutablePath: /usr/bin/nautilus SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1843588/+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 1949075] [NEW] Bluetooth headset not autoconnecting on power-on on 21.10
Public bug reported: After moving to Impish, my bluetooth headset doesn't automatically connect when I power it on (it was working fine on hirsute). When I go to the bluetooth settings, select it and click connect, the first time it disconnects immediately and I see this line in bluetoothd log: Oct 28 13:57:11 arrakis bluetoothd[1106]: src/profile.c:record_cb() Unable to get Hands-Free Voice gateway SDP record: Host is down After that, clicking the connect button again makes it work. I'm not sure where to find info to debug this furhter ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Oct 28 13:57:34 2021 InstallationDate: Installed on 2021-10-16 (11 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 20F6CTO1WW ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-19-generic root=/dev/mapper/ubuntu-root ro rootflags=subvol=@ quiet splash vt.handoff=7 RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/08/2019 dmi.bios.release: 1.44 dmi.bios.vendor: LENOVO dmi.bios.version: R02ET71W (1.44 ) dmi.board.asset.tag: Not Available dmi.board.name: 20F6CTO1WW dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.12 dmi.modalias: dmi:bvnLENOVO:bvrR02ET71W(1.44):bd05/08/2019:br1.44:efr1.12:svnLENOVO:pn20F6CTO1WW:pvrThinkPadX260:skuLENOVO_MT_20F6_BU_Think_FM_ThinkPadX260:rvnLENOVO:rn20F6CTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X260 dmi.product.name: 20F6CTO1WW dmi.product.sku: LENOVO_MT_20F6_BU_Think_FM_ThinkPad X260 dmi.product.version: ThinkPad X260 dmi.sys.vendor: LENOVO hciconfig: hci0: Type: Primary Bus: USB BD Address: E4:A7:A0:01:19:D5 ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING RX bytes:56756 acl:285 sco:0 events:6453 errors:0 TX bytes:3721263 acl:3477 sco:0 commands:2751 errors:0 ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug impish wayland-session -- 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/1949075 Title: Bluetooth headset not autoconnecting on power-on on 21.10 Status in bluez package in Ubuntu: New Bug description: After moving to Impish, my bluetooth headset doesn't automatically connect when I power it on (it was working fine on hirsute). When I go to the bluetooth settings, select it and click connect, the first time it disconnects immediately and I see this line in bluetoothd log: Oct 28 13:57:11 arrakis bluetoothd[1106]: src/profile.c:record_cb() Unable to get Hands-Free Voice gateway SDP record: Host is down After that, clicking the connect button again makes it work. I'm not sure where to find info to debug this furhter ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Oct 28 13:57:34 2021 InstallationDate: Installed on 2021-10-16 (11 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 20F6CTO1WW ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-19-generic root=/dev/mapper/ubuntu-root ro rootflags=subvol=@ quiet splash vt.handoff=7 RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/08/2019 dmi.bios.release: 1.44 dmi.bios.vendor: LENOVO dmi.bios.version: R02ET71W (1.44 ) dmi.board.asset.tag: Not Available dmi.board.name: 20F6CTO1WW dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.12 dmi.modalias: dmi:bvnLENOVO:bvrR02ET71W(1.44):bd05/08/2019:br1.44:efr1.12:svnLENOVO:pn20F6CTO1WW:pvrThinkPadX260:skuLENOVO_MT_20F6_BU_Think_FM_ThinkPadX260:rvnLENOVO:rn20F6CTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X260 dmi.product.name: 20F6CTO1WW dmi.product.sku:
[Desktop-packages] [Bug 1948778] Re: Random flashes in gnome-shell
i tryed journalctl -f in realtime too with the kms logs running and when a flash occurs i cant seem to pinpoint errors on the seconds it happens -- 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/1948778 Title: Random flashes in gnome-shell Status in gnome-shell package in Ubuntu: Incomplete Bug description: Ubuntu 22.04 development branch up to date to latest @ 26/10/2021 kernel 5.13.0-19-generic While working around on the desktop i'm getting short screen flashes like a screenshot style i cant reproduce them, they seem to come on random like every few minutes journal logs dont record anything while they occur this only happens on wayland, tested a long session on xorg where they dont occur ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 40.5-1ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu70 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Oct 26 11:12:30 2021 DisplayManager: gdm3 RelatedPackageVersions: mutter-common 40.5-1ubuntu2 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.xdg.autostart.gnome-shell-overrides-migration.desktop: 2021-10-23T19:12:47.175230 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1948778/+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 1948778] Re: Random flashes in gnome-shell
i had a screen flash on 11h39 with: quiet splash i915.enable_psr=0 MUTTER_DEBUG_ENABLE_ATOMIC_KMS=0 MUTTER_DEBUG=kms enabled ** Attachment added: "anotherflash.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1948778/+attachment/5536736/+files/anotherflash.txt -- 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/1948778 Title: Random flashes in gnome-shell Status in gnome-shell package in Ubuntu: Incomplete Bug description: Ubuntu 22.04 development branch up to date to latest @ 26/10/2021 kernel 5.13.0-19-generic While working around on the desktop i'm getting short screen flashes like a screenshot style i cant reproduce them, they seem to come on random like every few minutes journal logs dont record anything while they occur this only happens on wayland, tested a long session on xorg where they dont occur ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 40.5-1ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu70 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Oct 26 11:12:30 2021 DisplayManager: gdm3 RelatedPackageVersions: mutter-common 40.5-1ubuntu2 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.xdg.autostart.gnome-shell-overrides-migration.desktop: 2021-10-23T19:12:47.175230 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1948778/+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 1949066] [NEW] [upstream] Chapter numbering "sublevels" not showing (Multilevel outline numbers not showing)
Public bug reported: On LibreOffice 7.2.2.2, using the "Chapter Numbering"→"Show Sublevels" feature to create nested chapter numbers (e.g., 1.1, 1.A, etc.) doesn't seem to be working. This was reported (and apparently fixed) upstream, but still seems to be present in the Ubuntu version: https://bugs.documentfoundation.org/show_bug.cgi?id=143990 My package versions seem to be: 1:7.2.2-0ubuntu0.21.10.1 ** 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/1949066 Title: [upstream] Chapter numbering "sublevels" not showing (Multilevel outline numbers not showing) Status in libreoffice package in Ubuntu: New Bug description: On LibreOffice 7.2.2.2, using the "Chapter Numbering"→"Show Sublevels" feature to create nested chapter numbers (e.g., 1.1, 1.A, etc.) doesn't seem to be working. This was reported (and apparently fixed) upstream, but still seems to be present in the Ubuntu version: https://bugs.documentfoundation.org/show_bug.cgi?id=143990 My package versions seem to be: 1:7.2.2-0ubuntu0.21.10.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1949066/+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 1948589] Re: JS ERROR: Error: Expected an object of type ClutterActor for argument 'sibling' but got type undefined _syncStacking@resource:///org/gnome/shell/ui/workspaceAnimat
** Attachment added: "settings.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1948589/+attachment/5536715/+files/settings.txt -- 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/1948589 Title: JS ERROR: Error: Expected an object of type ClutterActor for argument 'sibling' but got type undefined _syncStacking@resource:///org/gnome/shell/ui/workspaceAnimation.js:80:18 Status in gnome-shell package in Ubuntu: New Bug description: Ubuntu 22.04 development branch with kernel 5.13.0-19-generic @ 24/10/2021 (wayland) Testing 4 apps on 4 dynamic workspaces, on switching the apps by clicking their icons from the dock, im getting a lot of JS ERRORS in the journal logs, the more i switch between the apps, the more the errors reproduce: okt 24 18:54:15 R00TB00K gnome-shell[271529]: JS ERROR: Error: Expected an object of type ClutterActor for argument 'sibling' but got type undefined _syncStacking@resource:///org/gnome/shell/ui/workspaceAnimation.js:80:18 okt 24 18:54:15 R00TB00K gnome-shell[271529]: JS ERROR: Error: Expected an object of type ClutterActor for argument 'sibling' but got type undefined _syncStacking@resource:///org/gnome/shell/ui/workspaceAnimation.js:80:18 okt 24 18:54:16 R00TB00K gnome-shell[271529]: JS ERROR: Error: Expected an object of type ClutterActor for argument 'sibling' but got type undefined _syncStacking@resource:///org/gnome/shell/ui/workspaceAnimation.js:80:18 okt 24 18:54:16 R00TB00K gnome-shell[271529]: JS ERROR: Error: Expected an object of type ClutterActor for argument 'sibling' but got type undefined _syncStacking@resource:///org/gnome/shell/ui/workspaceAnimation.js:80:18 okt 24 18:54:29 R00TB00K gnome-shell[271529]: JS ERROR: Error: Expected an object of type ClutterActor for argument 'sibling' but got type undefined _syncStacking@resource:///org/gnome/shell/ui/workspaceAnimation.js:80:18 okt 24 18:54:29 R00TB00K gnome-shell[271529]: JS ERROR: Error: Expected an object of type ClutterActor for argument 'sibling' but got type undefined _syncStacking@resource:///org/gnome/shell/ui/workspaceAnimation.js:80:18 okt 24 18:54:31 R00TB00K gnome-shell[271529]: JS ERROR: Error: Expected an object of type ClutterActor for argument 'sibling' but got type undefined _syncStacking@resource:///org/gnome/shell/ui/workspaceAnimation.js:80:18 okt 24 18:54:32 R00TB00K gnome-shell[271529]: JS ERROR: Error: Expected an object of type ClutterActor for argument 'sibling' but got type undefined _syncStacking@resource:///org/gnome/shell/ui/workspaceAnimation.js:80:18 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 40.5-1ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu70 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Oct 24 18:56:39 2021 DisplayManager: gdm3 RelatedPackageVersions: mutter-common 40.5-1ubuntu2 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.xdg.autostart.gnome-shell-overrides-migration.desktop: 2021-10-23T19:12:47.175230 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1948589/+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 1948589] Re: JS ERROR: Error: Expected an object of type ClutterActor for argument 'sibling' but got type undefined _syncStacking@resource:///org/gnome/shell/ui/workspaceAnimat
** Changed in: gnome-shell (Ubuntu) Status: Incomplete => New -- 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/1948589 Title: JS ERROR: Error: Expected an object of type ClutterActor for argument 'sibling' but got type undefined _syncStacking@resource:///org/gnome/shell/ui/workspaceAnimation.js:80:18 Status in gnome-shell package in Ubuntu: New Bug description: Ubuntu 22.04 development branch with kernel 5.13.0-19-generic @ 24/10/2021 (wayland) Testing 4 apps on 4 dynamic workspaces, on switching the apps by clicking their icons from the dock, im getting a lot of JS ERRORS in the journal logs, the more i switch between the apps, the more the errors reproduce: okt 24 18:54:15 R00TB00K gnome-shell[271529]: JS ERROR: Error: Expected an object of type ClutterActor for argument 'sibling' but got type undefined _syncStacking@resource:///org/gnome/shell/ui/workspaceAnimation.js:80:18 okt 24 18:54:15 R00TB00K gnome-shell[271529]: JS ERROR: Error: Expected an object of type ClutterActor for argument 'sibling' but got type undefined _syncStacking@resource:///org/gnome/shell/ui/workspaceAnimation.js:80:18 okt 24 18:54:16 R00TB00K gnome-shell[271529]: JS ERROR: Error: Expected an object of type ClutterActor for argument 'sibling' but got type undefined _syncStacking@resource:///org/gnome/shell/ui/workspaceAnimation.js:80:18 okt 24 18:54:16 R00TB00K gnome-shell[271529]: JS ERROR: Error: Expected an object of type ClutterActor for argument 'sibling' but got type undefined _syncStacking@resource:///org/gnome/shell/ui/workspaceAnimation.js:80:18 okt 24 18:54:29 R00TB00K gnome-shell[271529]: JS ERROR: Error: Expected an object of type ClutterActor for argument 'sibling' but got type undefined _syncStacking@resource:///org/gnome/shell/ui/workspaceAnimation.js:80:18 okt 24 18:54:29 R00TB00K gnome-shell[271529]: JS ERROR: Error: Expected an object of type ClutterActor for argument 'sibling' but got type undefined _syncStacking@resource:///org/gnome/shell/ui/workspaceAnimation.js:80:18 okt 24 18:54:31 R00TB00K gnome-shell[271529]: JS ERROR: Error: Expected an object of type ClutterActor for argument 'sibling' but got type undefined _syncStacking@resource:///org/gnome/shell/ui/workspaceAnimation.js:80:18 okt 24 18:54:32 R00TB00K gnome-shell[271529]: JS ERROR: Error: Expected an object of type ClutterActor for argument 'sibling' but got type undefined _syncStacking@resource:///org/gnome/shell/ui/workspaceAnimation.js:80:18 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 40.5-1ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu70 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Oct 24 18:56:39 2021 DisplayManager: gdm3 RelatedPackageVersions: mutter-common 40.5-1ubuntu2 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.xdg.autostart.gnome-shell-overrides-migration.desktop: 2021-10-23T19:12:47.175230 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1948589/+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 1948778] Re: Random flashes in gnome-shell
Please enable both the suggestions in comment #5, and then follow comment #7 again. -- 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/1948778 Title: Random flashes in gnome-shell Status in gnome-shell package in Ubuntu: Incomplete Bug description: Ubuntu 22.04 development branch up to date to latest @ 26/10/2021 kernel 5.13.0-19-generic While working around on the desktop i'm getting short screen flashes like a screenshot style i cant reproduce them, they seem to come on random like every few minutes journal logs dont record anything while they occur this only happens on wayland, tested a long session on xorg where they dont occur ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 40.5-1ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu70 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Oct 26 11:12:30 2021 DisplayManager: gdm3 RelatedPackageVersions: mutter-common 40.5-1ubuntu2 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.xdg.autostart.gnome-shell-overrides-migration.desktop: 2021-10-23T19:12:47.175230 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1948778/+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 1948778] Re: Random flashes in gnome-shell
The only error I can see around 10:58 is bug 1948589 so maybe we should eliminate that first. -- 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/1948778 Title: Random flashes in gnome-shell Status in gnome-shell package in Ubuntu: Incomplete Bug description: Ubuntu 22.04 development branch up to date to latest @ 26/10/2021 kernel 5.13.0-19-generic While working around on the desktop i'm getting short screen flashes like a screenshot style i cant reproduce them, they seem to come on random like every few minutes journal logs dont record anything while they occur this only happens on wayland, tested a long session on xorg where they dont occur ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 40.5-1ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu70 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Oct 26 11:12:30 2021 DisplayManager: gdm3 RelatedPackageVersions: mutter-common 40.5-1ubuntu2 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.xdg.autostart.gnome-shell-overrides-migration.desktop: 2021-10-23T19:12:47.175230 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1948778/+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 1948778] Re: Random flashes in gnome-shell
i had a screen flash around 10h58 logs in attachment ** Attachment added: "anotherflash.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1948778/+attachment/5536712/+files/anotherflash.txt -- 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/1948778 Title: Random flashes in gnome-shell Status in gnome-shell package in Ubuntu: Incomplete Bug description: Ubuntu 22.04 development branch up to date to latest @ 26/10/2021 kernel 5.13.0-19-generic While working around on the desktop i'm getting short screen flashes like a screenshot style i cant reproduce them, they seem to come on random like every few minutes journal logs dont record anything while they occur this only happens on wayland, tested a long session on xorg where they dont occur ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 40.5-1ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu70 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Oct 26 11:12:30 2021 DisplayManager: gdm3 RelatedPackageVersions: mutter-common 40.5-1ubuntu2 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.xdg.autostart.gnome-shell-overrides-migration.desktop: 2021-10-23T19:12:47.175230 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1948778/+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 1877038]
*** Bug 1695380 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 firefox in Ubuntu. https://bugs.launchpad.net/bugs/1877038 Title: [upstream] Firefox lacks FIDO2 support with Yubikeys Status in Mozilla Firefox: Confirmed Status in firefox package in Ubuntu: Triaged Bug description: Ubuntu LTS versions affected. "Passwordless" authentications with Yubikeys using Firefox don't work with FIDO2. Tested both with the yubikey software packages from the bionic/universe repo and those from the vendor https://www.yubico.com/ To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1877038/+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 1065126]
*** Bug 1737586 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 firefox in Ubuntu. https://bugs.launchpad.net/bugs/1065126 Title: "Always do this from now on" does not work Status in Mozilla Firefox: Confirmed Status in One Hundred Papercuts: Confirmed Status in firefox package in Ubuntu: Confirmed Bug description: Downloading an unknown file type in Firefox displays a dialog for choosing which application to use for opening the file. The dialog contains a check box labelled "Always do this action from now on". Checking this option does not work: When I download a file of the same type next time, the same dialog is displayed again. This feature is broken for as long as I can remember (> 10 years). It's time it was fixed (or removed). ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: firefox 15.0.1+build1-0ubuntu0.12.04.1 ProcVersionSignature: Ubuntu 3.2.0-31.50-generic 3.2.28 Uname: Linux 3.2.0-31-generic x86_64 NonfreeKernelModules: nvidia AddonCompatCheckDisabled: False AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. ApportVersion: 2.0.1-0ubuntu13 Architecture: amd64 ArecordDevices: List of CAPTURE Hardware Devices card 0: Intel [HDA Intel], device 0: AD198x Analog [AD198x Analog] Subdevices: 2/2 Subdevice #0: subdevice #0 Subdevice #1: subdevice #1 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ruediger 2536 F pulseaudio BuildID: 20120907231657 Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0xfe22 irq 49' Mixer name : 'Analog Devices AD1984' Components : 'HDA:11d41984,17aa20bb,00100400' Controls : 32 Simple ctrls : 20 Card29.Amixer.info: Card hw:29 'ThinkPadEC'/'ThinkPad Console Audio Control at EC reg 0x30, fw 7KHT24WW-1.08' Mixer name : 'ThinkPad EC 7KHT24WW-1.08' Components : '' Controls : 1 Simple ctrls : 1 Card29.Amixer.values: Simple mixer control 'Console',0 Capabilities: pswitch pswitch-joined penum Playback channels: Mono Mono: Playback [on] Channel: Unavailable Date: Wed Oct 10 18:17:44 2012 EcryptfsInUse: Yes ForcedLayersAccel: False IfupdownConfig: auto lo iface lo inet loopback InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1) IpRoute: default via 172.31.0.1 dev wlan0 proto static 169.254.0.0/16 dev wlan0 scope link metric 1000 172.31.0.0/20 dev wlan0 proto kernel scope link src 172.31.9.26 metric 2 MostRecentCrashID: bp-7716491c-74b4-4213-bbf0-37b512110505 PrefSources: prefs.js Profiles: Profile0 (Default) - LastVersion=15.0.1/20120907231657 (In use) RelatedPackageVersions: rhythmbox-mozilla 2.96-0ubuntu4.2 totem-mozilla 3.0.1-0ubuntu21.1 icedtea-6-plugin 1.2-2ubuntu1.2 RunningIncompatibleAddons: False SourcePackage: firefox UpgradeStatus: Upgraded to precise on 2012-04-28 (165 days ago) dmi.bios.date: 03/18/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 7LETC9WW (2.29 ) dmi.board.name: 6457BBG dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr7LETC9WW(2.29):bd03/18/2011:svnLENOVO:pn6457BBG:pvrThinkPadT61:rvnLENOVO:rn6457BBG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 6457BBG dmi.product.version: ThinkPad T61 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1065126/+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 1948954] Re: snap packaged version of Firefox is inaccessible with Orca screen reader.
** Package changed: firefox (Ubuntu) => snap (Ubuntu) ** Changed in: snap (Ubuntu) Importance: Undecided => High -- 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/1948954 Title: snap packaged version of Firefox is inaccessible with Orca screen reader. Status in snapd package in Ubuntu: Confirmed Bug description: I recently updated to Ubuntu mate 21.10, from 21.04. I am unable to browse the web, using the snap version of firefox, provided by default in this release. With Orca running, launch firefox, and it will report inaccessible. I have another 21.10 machine where I have removed the snap version, and it works as expected using the .deb package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1948954/+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 1948954] Re: snap packaged version of Firefox is inaccessible with Orca screen reader.
Seems that's an issue with snaps and not specific to firefox, at least trying with evince it has the same issue -- 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/1948954 Title: snap packaged version of Firefox is inaccessible with Orca screen reader. Status in snap package in Ubuntu: Confirmed Bug description: I recently updated to Ubuntu mate 21.10, from 21.04. I am unable to browse the web, using the snap version of firefox, provided by default in this release. With Orca running, launch firefox, and it will report inaccessible. I have another 21.10 machine where I have removed the snap version, and it works as expected using the .deb package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snap/+bug/1948954/+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 1849478] Re: [snap] (experimental) pipewire support not available
Fixed with https://git.launchpad.net/~chromium-team/chromium- browser/+git/snap-from- source/commit/?id=9bb2debda802087e3910a720dc63172f1471ed09. ** Changed in: chromium-browser (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1849478 Title: [snap] (experimental) pipewire support not available Status in chromium-browser package in Ubuntu: Fix Committed Bug description: I'm using the chromium snap (currently 77.0.3865.120, rev 899), it's not possible to enable experimental support for pipewire, as the toggle doesn't show up in chrome://flags. It would be nice to have chromium compiled with pipewire support, to enable screensharing in Hangouts and similar apps. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1849478/+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 1949054] [NEW] Despite being enabled, `Mouse Keys` stops working after reboot
Public bug reported: if it is enabled and I reboot my device, `Mouse Keys` stops working i.e. when `Num Lock` is disabled, the numeric pad acts like the arrow keys; when `Num Lock` is enabled, the numeric pad can be used to input digits and arithmetic symbols in other words, `Mouse Keys` is completely ignored as if it wasn't enabled in the first place I expected the `Mouse Keys` function to be retained even after a reboot in order to make it work again, I have to disable `Mouse Keys` and enable it back ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: libatk1.0-0 2.36.0-0ubuntu3 ProcVersionSignature: Ubuntu 5.13.0-21.21-generic 5.13.18 Uname: Linux 5.13.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Oct 28 09:53:42 2021 InstallationDate: Installed on 2021-10-10 (17 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Beta amd64 (20210922) SourcePackage: atk1.0 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: atk1.0 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug impish third-party-packages wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to atk1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1949054 Title: Despite being enabled, `Mouse Keys` stops working after reboot Status in atk1.0 package in Ubuntu: New Bug description: if it is enabled and I reboot my device, `Mouse Keys` stops working i.e. when `Num Lock` is disabled, the numeric pad acts like the arrow keys; when `Num Lock` is enabled, the numeric pad can be used to input digits and arithmetic symbols in other words, `Mouse Keys` is completely ignored as if it wasn't enabled in the first place I expected the `Mouse Keys` function to be retained even after a reboot in order to make it work again, I have to disable `Mouse Keys` and enable it back ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: libatk1.0-0 2.36.0-0ubuntu3 ProcVersionSignature: Ubuntu 5.13.0-21.21-generic 5.13.18 Uname: Linux 5.13.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Oct 28 09:53:42 2021 InstallationDate: Installed on 2021-10-10 (17 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Beta amd64 (20210922) SourcePackage: atk1.0 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/atk1.0/+bug/1949054/+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
