[Bug 2004063] Re: Mouse and shell become laggy after some time and progressively gets worse
** Summary changed: - mouse pointer becomes laggy after some time and progressively gets worse + Mouse and shell become laggy after some time and progressively gets worse -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2004063 Title: Mouse and shell become laggy after some time and progressively gets worse To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2004063/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2003176] Please test proposed package
Hello Mustafa, or anyone else affected, Accepted metacity into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/metacity/1:3.44.0-1ubuntu1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-jammy. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to metacity in Ubuntu. https://bugs.launchpad.net/bugs/2003176 Title: SRU: metacity crashes while minimizing a windows that has undocked child To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/2003176/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2003176] Re: SRU: metacity crashes while minimizing a windows that has undocked child
Hello Mustafa, or anyone else affected, Accepted metacity into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/metacity/1:3.36.1-1ubuntu1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: metacity (Ubuntu Focal) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-focal ** Changed in: metacity (Ubuntu Jammy) Status: In Progress => Fix Committed ** Tags added: verification-needed-jammy -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to metacity in Ubuntu. https://bugs.launchpad.net/bugs/2003176 Title: SRU: metacity crashes while minimizing a windows that has undocked child To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/2003176/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1998286] Re: Release mutter 42.7 to jammy
Although 42.8 doesn't exist upstream yet. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1998286 Title: Release mutter 42.7 to jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1998286/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1998286] Re: Release mutter 42.7 to jammy
^^^ https://bugs.launchpad.net/ubuntu/jammy/+source/mutter -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1998286 Title: Release mutter 42.7 to jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1998286/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1998286] Re: Release mutter 42.7 to jammy
@jbicha Is there any update about Mutter 42.8 in the Jammy repo? There are two irritating bugs in Mutter that are already resolved in 42.8 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1998286 Title: Release mutter 42.7 to jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1998286/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Re: [Bug 1887252] Re: config-error-dialog.sh should pass --no-markup
On Wed, Feb 8, 2023 at 10:25 AM Gunnar Hjalmarsson <1887...@bugs.launchpad.net> wrote: > > That looks like a better solution indeed, and I think I have got enough > of evidence that we should go for Sebastian's suggestion. > > ( Why didn't you mention that upstream discussion in your bug? ;) ) That should be my negligence. I only gave a link for reference from discourse.gnome.org to bugs.launchpad.net [1] but did not provide the opposite link on bugs.launchpad.net pointing to discourse.gnome.org, at that moment. > Thanks for your persistence! I'll make that change soon. OK. > ** Changed in: gdm3 (Ubuntu) >Status: Incomplete => In Progress > > ** Changed in: lightdm (Ubuntu) >Status: Incomplete => In Progress [1] https://discourse.gnome.org/t/are-you-sure-you-want-to-proceed-message-on-login/13758/11?u=hongyi-zhao [2] https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/2005135 Regards, Zhao > -- > You received this bug notification because you are subscribed to a > duplicate bug report (2005135). > https://bugs.launchpad.net/bugs/1887252 > > Title: > config-error-dialog.sh should pass --no-markup > > Status in gdm3 package in Ubuntu: > In Progress > Status in lightdm package in Ubuntu: > In Progress > > Bug description: > I modified my ~/.profile to call "logger". This resulted in in > producing some output on stderr like > > ``` > <13>Jul 11 13:02:46 /usr/sbin/lightdm-session[1408]: profile sourced ... > ``` > > This showed an empty zenity prompt. > > Logs suggest zenity was failing because it was treating `<13>` as > pango markup. > > ``` >from markup due to error parsing markup: Error on line 3 char 6: “13” is > not a valid > ``` > > We should not assume the error message strings contain valid markup, > since their source is unknown. > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1887252/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1887252 Title: config-error-dialog.sh should pass --no-markup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1887252/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1983523] Re: Evolution / Evolution EWS using Oauth2 Segfault when adding account
[Expired for evolution (Ubuntu) because there has been no activity for 60 days.] ** Changed in: evolution (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evolution in Ubuntu. https://bugs.launchpad.net/bugs/1983523 Title: Evolution / Evolution EWS using Oauth2 Segfault when adding account To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1983523/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2004533] Re: Gtk-WARNING ... drawing failure for widget ... invalid value (typically too big)
I think this is a consequence of your desktop being 18432 pixels wide. Each 4K monitor is 6144 logical pixels wide because of a custom Xrandr scaling factor of 1.6. Turning off screens wouldn't fix it, only unplugging them might. But still this sounds like a GTK bug because modern Nvidia GPUs like yours should be fine with an 18K desktop. ** Bug watch added: gitlab.gnome.org/GNOME/gtk/-/issues #3050 https://gitlab.gnome.org/GNOME/gtk/-/issues/3050 ** Also affects: gtk via https://gitlab.gnome.org/GNOME/gtk/-/issues/3050 Importance: Unknown Status: Unknown ** Changed in: gtk+3.0 (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/2004533 Title: Gtk-WARNING ... drawing failure for widget ... invalid value (typically too big) To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/2004533/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1887252] Re: config-error-dialog.sh should pass --no-markup
That looks like a better solution indeed, and I think I have got enough of evidence that we should go for Sebastian's suggestion. ( Why didn't you mention that upstream discussion in your bug? ;) ) Thanks for your persistence! I'll make that change soon. ** Changed in: gdm3 (Ubuntu) Status: Incomplete => In Progress ** Changed in: lightdm (Ubuntu) Status: Incomplete => In Progress -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1887252 Title: config-error-dialog.sh should pass --no-markup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1887252/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1994010] Re: gnome-shell crashed with SIGSEGV in std::__atomic_base::load(__m=std::memory_order_relaxed, this=0x0) from mozilla::detail::IntrinsicMemoryOps
I just noticed this is a shutdown crash, which isn't obvious until you scroll down to frames #46-#54: https://errors.ubuntu.com/problem/d31a7f723bab2a42586060136dc27f56bc71 Although that's probably not an excuse for letting this sneak into jammy. Another interesting note is that it looks like libnm is involved in frames #22-#25 so it might be NetworkManager that got fixed in lunar? ** Also affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Changed in: network-manager (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1994010 Title: gnome-shell crashed with SIGSEGV in std::__atomic_base::load(__m=std::memory_order_relaxed, this=0x0) from mozilla::detail::IntrinsicMemoryOps::load() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/1994010/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Re: [Bug 1887252] Re: config-error-dialog.sh should pass --no-markup
On Wed, Feb 8, 2023 at 9:15 AM Gunnar Hjalmarsson <1887...@bugs.launchpad.net> wrote: > > @Hongyi Zhao: As you wrote in the duplicate bug, my simplistic code in > comment #2, which only escapes the '<' character, would not be > sufficient. At the same time the issue I mentioned, about --no-markup > making \n being displayed literally instead of interpreted as a newline, > still stands. > > Probably this variant would do it: > > TEXT=$(printf '%s' "$TEXT" | sed 's/&/\/g; > s/ s/>/\/g; > s/"/\/g; > s/'"'"'/\/g') > > But before making the change, I would appreciate some feedback from you > or others that that addition to /etc/gdm3/config-error-dialog.sh would > address the issues you have observed. Please see the comments given by Sebastian Keller here [1]. [1] https://discourse.gnome.org/t/are-you-sure-you-want-to-proceed-message-on-login/13758/13 Best, Zhao > -- > You received this bug notification because you are subscribed to a > duplicate bug report (2005135). > https://bugs.launchpad.net/bugs/1887252 > > Title: > config-error-dialog.sh should pass --no-markup > > Status in gdm3 package in Ubuntu: > Incomplete > Status in lightdm package in Ubuntu: > Incomplete > > Bug description: > I modified my ~/.profile to call "logger". This resulted in in > producing some output on stderr like > > ``` > <13>Jul 11 13:02:46 /usr/sbin/lightdm-session[1408]: profile sourced ... > ``` > > This showed an empty zenity prompt. > > Logs suggest zenity was failing because it was treating `<13>` as > pango markup. > > ``` >from markup due to error parsing markup: Error on line 3 char 6: “13” is > not a valid > ``` > > We should not assume the error message strings contain valid markup, > since their source is unknown. > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1887252/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1887252 Title: config-error-dialog.sh should pass --no-markup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1887252/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1887252] Re: config-error-dialog.sh should pass --no-markup
@Hongyi Zhao: As you wrote in the duplicate bug, my simplistic code in comment #2, which only escapes the '<' character, would not be sufficient. At the same time the issue I mentioned, about --no-markup making \n being displayed literally instead of interpreted as a newline, still stands. Probably this variant would do it: TEXT=$(printf '%s' "$TEXT" | sed 's/&/\/g; s//\/g; s/"/\/g; s/'"'"'/\/g') But before making the change, I would appreciate some feedback from you or others that that addition to /etc/gdm3/config-error-dialog.sh would address the issues you have observed. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1887252 Title: config-error-dialog.sh should pass --no-markup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1887252/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1975884] Re: Temporary screen freeze when gnome-shell logs "Removing a network device that was not added"
I have observed the issue described in this report on three separate installations of 22.04 (clean install & upgrade from 20.04) from release until now. Given the highly user impacting nature of it, I am surprised it remains of undecided importance and unassigned. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1975884 Title: Temporary screen freeze when gnome-shell logs "Removing a network device that was not added" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1975884/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2006483] [NEW] Fails autopkgtests when tested against fuse3 >= 3.13
Public bug reported: The autopkgtest in `tests/test-rofiles-fuse.sh` (executed via `gnome- desktop-testing-runner libostree/test-rofiles-fuse.sh.test`) fails to execute `setfattr -n user.foo -v bar mnt/anewfile-for-fuse` with the error message "setfattr: mnt/anewfile-for-fuse: Numerical result out of range". It's unclear if this is related to glibc, FUSE_USE_VERSION, kernel fuse protocol or another component. On Debian this specific test is skipped, due to missing the "capsh" binary (libcap2-bin) in the test env: ``` /usr/libexec/installed-tests/libostree/libtest.sh: line 688: capsh: command not found 1..0 # SKIP No cap_sys_admin in bounding set, can't use FUSE ``` The relevant log (inside an Ubuntu autopkgtest qemu runner) is provided here: ``` $ ../tests/test-rofiles-fuse.sh Copying gpghome to /tmp/autopkgtest.Eaudsf/build.b3k/src/tmp4 checking for xattrs.../usr/bin/setfattr /tmp/autopkgtest.Eaudsf/build.b3k/src/tmp4 /tmp/autopkgtest.Eaudsf/build.b3k/src/tmp4 # testlabel.txt: security.selinux: No such attribute Unable to retrieve SELinux label, assuming disabled /tmp/autopkgtest.Eaudsf/build.b3k/src/tmp4 done checking for overlayfs whiteouts...done /usr/bin/setfattr d9793c4639f817fb95e3f1ae7a3f0571826db12a28baffaa3b3510f2ef0434a4 812152c68bb9c0b2a3bfcafeb5c4a4aa53827d8df5eeb755fe307f6a68f0febf fsck objects (20/20) [=] 100% object fsck of 2 commits completed successfully - no errors found. 1..12 a122802794e487785d14b58fe8969ab8716fd5c4c0ceed7de5c76061cd93f896 ok mount ok failed inplace mutation (open O_TRUNCATE) ok failed mutation chmod + chown setfattr: mnt/firstfile-link: Read-only file system ok new content setfattr: mnt/anewfile-for-fuse: Numerical result out of range Unexpected nonzero exit status 1 while running: setfattr -n user.foo -v bar mnt/anewfile-for-fuse gpg-connect-agent: no running gpg-agent - starting '/usr/bin/gpg-agent' gpg-connect-agent: waiting for the agent to come up ... (5s) gpg-connect-agent: connection to agent established OK closing connection ``` ** Affects: fuse3 (Ubuntu) Importance: Undecided Status: New ** Affects: ostree (Ubuntu) Importance: Undecided Status: New ** Tags: update-excuse ** Also affects: fuse3 (Ubuntu) Importance: Undecided Status: New ** Description changed: The autopkgtest in `tests/test-rofiles-fuse.sh` (executed via `gnome- desktop-testing-runner libostree/test-rofiles-fuse.sh.test`) fails to execute `setfattr -n user.foo -v bar mnt/anewfile-for-fuse` with the error message "setfattr: mnt/anewfile-for-fuse: Numerical result out of range". It's unclear if this is related to glibc, FUSE_USE_VERSION, kernel fuse protocol or another component. - The relevant log is provided here: + On Debian this specific test is skipped, due to missing the "capsh" binary (libcap2-bin) in the test env: + ``` + /usr/libexec/installed-tests/libostree/libtest.sh: line 688: capsh: command not found + 1..0 # SKIP No cap_sys_admin in bounding set, can't use FUSE + ``` + + The relevant log (inside an Ubuntu autopkgtest qemu runner) is provided + here: ``` - $ ../tests/test-rofiles-fuse.sh + $ ../tests/test-rofiles-fuse.sh Copying gpghome to /tmp/autopkgtest.Eaudsf/build.b3k/src/tmp4 checking for xattrs.../usr/bin/setfattr /tmp/autopkgtest.Eaudsf/build.b3k/src/tmp4 /tmp/autopkgtest.Eaudsf/build.b3k/src/tmp4 # testlabel.txt: security.selinux: No such attribute Unable to retrieve SELinux label, assuming disabled /tmp/autopkgtest.Eaudsf/build.b3k/src/tmp4 done checking for overlayfs whiteouts...done /usr/bin/setfattr d9793c4639f817fb95e3f1ae7a3f0571826db12a28baffaa3b3510f2ef0434a4 812152c68bb9c0b2a3bfcafeb5c4a4aa53827d8df5eeb755fe307f6a68f0febf fsck objects (20/20) [=] 100% object fsck of 2 commits completed successfully - no errors found. 1..12 a122802794e487785d14b58fe8969ab8716fd5c4c0ceed7de5c76061cd93f896 ok mount ok failed inplace mutation (open O_TRUNCATE) ok failed mutation chmod + chown setfattr: mnt/firstfile-link: Read-only file system ok new content setfattr: mnt/anewfile-for-fuse: Numerical result out of range Unexpected nonzero exit status 1 while running: setfattr -n user.foo -v bar mnt/anewfile-for-fuse gpg-connect-agent: no running gpg-agent - starting '/usr/bin/gpg-agent' gpg-connect-agent: waiting for the agent to come up ... (5s) gpg-connect-agent: connection to agent established OK closing connection ``` -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to ostree in Ubuntu. https://bugs.launchpad.net/bugs/2006483 Title: Fails autopkgtests when tested against fuse3 >= 3.13 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fuse3/+bug/2006483/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1993214] Re: [jammy] Update gjs to 1.74 using mozjs102 102.3
We are not going to release these yet, we are blocked on comment #8. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gjs in Ubuntu. https://bugs.launchpad.net/bugs/1993214 Title: [jammy] Update gjs to 1.74 using mozjs102 102.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/1993214/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2006468] [NEW] firefox does not detect mousemove events
Public bug reported: I have an issue, which I saw only on Firefox : after some time (or some event which I haven't identified yet), Firefox does not react to my mouse movement events meaning : * when hovering over an HTML item, it does not highlight/change appearance even if it is supposed to do so, * when hovering over a clickable item, the cursor does not change, * when hovering over selectable text, the cursor does not change, * tooltips do not appear, * etc ... if I trigger other GUI events (if I *click*, or if I *press any keyboard key* -- `[A]`, `[Shift]`, `[Ctrl]` ...), then the GUI reacts (cursor changes, tooltips appear, animations get triggered ...), a bit as if, by handling that other event, firefox realized "oh, the cursor is actually there", but with no external event, my mousenter/mouseleave events seem to be ignored, or stalled. Running Ubuntu 22.10 (kinetic), and regular firefox snap install (my current version: 109.0.1-1). As said in the previous sentence: firefox is installed through snap (which, if I am correct, is the default way to install firefox on a Ubuntu system these days) not through an apt package. Is this a known issue ? ** Affects: firefox (Ubuntu) Importance: Undecided Status: New ** Package changed: nautilus (Ubuntu) => firefox (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/2006468 Title: firefox does not detect mousemove events To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/2006468/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1990677] Re: Update fonts-noto-color-emoji for Unicode 15
This bug was fixed in the package fonts-noto-color-emoji - 2.038-0ubuntu1 --- fonts-noto-color-emoji (2.038-0ubuntu1) jammy; urgency=medium * New upstream release (LP: #1990677) - This major update introduces support for the Unicode 15 standard https://blog.emojipedia.org/whats-new-in-unicode-15-0/ * Bump minimum nototools -- Bram Stolk Mon, 26 Sep 2022 13:04:23 -0700 ** Changed in: fonts-noto-color-emoji (Ubuntu Jammy) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to fonts-noto-color-emoji in Ubuntu. https://bugs.launchpad.net/bugs/1990677 Title: Update fonts-noto-color-emoji for Unicode 15 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fonts-noto-color-emoji/+bug/1990677/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1993214] Re: [jammy] Update gjs to 1.74 using mozjs102 102.3
@mdeslaur yes, basically all stable-series daily builds always build with -proposed enabled. The reason for that is that we want people to be able to test proposed updates in images in case its needed for validation. We always enable -proposed for those as one of the steps *after* we release an LTS version. Devel series dailies however always build with -proposed *disabled*. Anyway, please give me a sign when this update is good to go. Can I safely release kinetic at least? Should this go to -security? -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gjs in Ubuntu. https://bugs.launchpad.net/bugs/1993214 Title: [jammy] Update gjs to 1.74 using mozjs102 102.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/1993214/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1796649] Re: gjs-console crashed with SIGABRT in g_assertion_message()
Seems to affect me in a persistent live system running Ubuntu Desktop Lunar daily iso file in Dell Precision M4800 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gjs in Ubuntu. https://bugs.launchpad.net/bugs/1796649 Title: gjs-console crashed with SIGABRT in g_assertion_message() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/1796649/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1959937] Re: gnome-shell crashed with SIGSEGV in meta_context_terminate(context=0x0) from process_ice_messages()
Tracking in:
https://errors.ubuntu.com/problem/fc75ee04fbc965ec925af6675c012cd4e03a770b
** Changed in: mutter (Ubuntu Jammy)
Status: In Progress => Fix Committed
** Tags removed: rls-jj-incoming
** Tags added: fixed-in-mutter-42.8
** Description changed:
+ https://errors.ubuntu.com/problem/fc75ee04fbc965ec925af6675c012cd4e03a770b
+
+ ---
+
The error occurred when I ran apt update/upgrade in a terminal window
after logging in.
ProblemType: Crash
DistroRelease: Ubuntu 22.04
Package: gnome-shell 41.3-1ubuntu1
ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12
Uname: Linux 5.15.0-18-generic x86_64
ApportVersion: 2.20.11-0ubuntu76
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Thu Feb 3 09:03:52 2022
DisplayManager: gdm3
ExecutablePath: /usr/bin/gnome-shell
GsettingsChanges:
- b'org.gnome.shell' b'welcome-dialog-last-shown-version' b"'41.3'"
- b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'hu')]"
- b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
- b'org.gnome.desktop.notifications' b'application-children'
b"['gnome-initial-setup']"
- b'org.gnome.desktop.privacy' b'report-technical-problems' b'true'
+ b'org.gnome.shell' b'welcome-dialog-last-shown-version' b"'41.3'"
+ b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'hu')]"
+ b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
+ b'org.gnome.desktop.notifications' b'application-children'
b"['gnome-initial-setup']"
+ b'org.gnome.desktop.privacy' b'report-technical-problems' b'true'
InstallationDate: Installed on 2022-02-03 (0 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220202)
ProcCmdline: /usr/bin/gnome-shell
RelatedPackageVersions: mutter-common 41.3-1ubuntu1
Signal: 11
SourcePackage: gnome-shell
StacktraceTop:
- meta_context_terminate () from /lib/x86_64-linux-gnu/libmutter-9.so.0
- ?? () from /lib/x86_64-linux-gnu/libmutter-9.so.0
- g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
- ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
- g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
+ meta_context_terminate () from /lib/x86_64-linux-gnu/libmutter-9.so.0
+ ?? () from /lib/x86_64-linux-gnu/libmutter-9.so.0
+ g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
+ ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
+ g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
Title: gnome-shell crashed with SIGSEGV in meta_context_terminate()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
separator:
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1959937
Title:
gnome-shell crashed with SIGSEGV in
meta_context_terminate(context=0x0) from process_ice_messages()
To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1959937/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1959937] Re: gnome-shell crashed with SIGSEGV in meta_context_terminate(context=0x0) from process_ice_messages()
Jammy got forgotten for a while... https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2830 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1959937 Title: gnome-shell crashed with SIGSEGV in meta_context_terminate(context=0x0) from process_ice_messages() To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1959937/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1959937] Re: gnome-shell crashed with SIGSEGV in meta_context_terminate(context=0x0) from process_ice_messages()
** Also affects: mutter (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: mutter (Ubuntu Jammy) Status: New => In Progress ** Changed in: mutter (Ubuntu Jammy) Importance: Undecided => Medium ** Changed in: mutter (Ubuntu Jammy) Assignee: (unassigned) => Daniel van Vugt (vanvugt) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1959937 Title: gnome-shell crashed with SIGSEGV in meta_context_terminate(context=0x0) from process_ice_messages() To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1959937/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1970917] Re: gnome-shell crashes with SIGABRT due to assertion failure "!window->monitor || g_list_find (meta_monitor_manager_get_logical_monitors (monitor_manager), window->monitor)" in meta_win
** Changed in: mutter (Ubuntu Jammy) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1970917 Title: gnome-shell crashes with SIGABRT due to assertion failure "!window->monitor || g_list_find (meta_monitor_manager_get_logical_monitors (monitor_manager), window->monitor)" in meta_window_update_for_monitors_changed() To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1970917/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
