[Bug 378783] Re: xdg-open *.desktop opens text editor
** Changed in: glib Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/378783 Title: xdg-open *.desktop opens text editor To manage notifications about this bug go to: https://bugs.launchpad.net/glib/+bug/378783/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1735986] Re: Unable to set different scale correctly on different monitors
** Bug watch added: gitlab.gnome.org/GNOME/gnome-control-center/-/issues #17 https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/17 ** Also affects: gnome-control-center via https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/17 Importance: Unknown Status: Unknown ** Package changed: gnome-shell (Ubuntu) => mutter (Ubuntu) ** Tags added: focal -- 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/1735986 Title: Unable to set different scale correctly on different monitors To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1735986/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1907468] Re: visual studio code crashes gnome-shell on Ubuntu 20.10
Also, next time the crash happens please reboot and then run: journalctl -b-1 > prevboot.txt and attach the resulting text file here. -- 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/1907468 Title: visual studio code crashes gnome-shell on Ubuntu 20.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1907468/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1907468] Re: visual studio code crashes gnome-shell on Ubuntu 20.10
Thank you for taking the time to report this bug and helping to make Ubuntu better. It sounds like some part of the system has crashed. To help us find the cause of the crash please follow these steps: 1. Look in /var/crash for crash files and if found run: ubuntu-bug YOURFILE.crash Then tell us the ID of the newly-created bug. 2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us. 3. If step 2 also failed then apply the workaround from bug 994921, reboot, reproduce the crash, and retry step 1. Please take care to avoid attaching .crash files to bugs as we are unable to process them as file attachments. It would also be a security risk for yourself. ** Tags added: groovy ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete -- 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/1907468 Title: visual studio code crashes gnome-shell on Ubuntu 20.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1907468/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1907478] Re: integer scaling is locked between multiple monitors
*** This bug is a duplicate of bug 1735986 *** https://bugs.launchpad.net/bugs/1735986 That issue points to bug 1735986 so let's use that. ** This bug has been marked a duplicate of bug 1735986 Unable to set different scale correctly on different monitors -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1907478 Title: integer scaling is locked between multiple monitors To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1907478/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1819890] Re: Restarting gnome-shell displays images of applications running on other workspaces
This bug was closed almost 9 months ago so if you still have problems then please open a new bug. -- 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/1819890 Title: Restarting gnome-shell displays images of applications running on other workspaces To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1819890/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1897765] Re: gnome-shell crashed with signal 5 in g_log("Error in freeze/thaw accounting") from meta_window_actor_thaw() from WindowManager::_sizeChangedWindow
We can't do anything with that screenshot. If you experience crashes
then please open new bugs for them using these instructions:
https://wiki.ubuntu.com/Bugs/Responses#Missing_a_crash_report_or_having_a_.crash_attachment
--
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/1897765
Title:
gnome-shell crashed with signal 5 in g_log("Error in freeze/thaw
accounting") from meta_window_actor_thaw() from
WindowManager::_sizeChangedWindow
To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/1897765/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1905729] Re: power button configuration broken
No it was mounted but fsck.vfat got stuck for some reason, but the sd- card works fine now. Not really sure of what happened in which order.. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1905729 Title: power button configuration broken To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1905729/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1819890] Re: Restarting gnome-shell displays images of applications running on other workspaces
I have the same issue -- 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/1819890 Title: Restarting gnome-shell displays images of applications running on other workspaces To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1819890/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1897765] Re: gnome-shell crashed with signal 5 in g_log("Error in freeze/thaw accounting") from meta_window_actor_thaw() from WindowManager::_sizeChangedWindow
Can we do anything about
https://bugs.launchpad.net/mutter/+bug/1897765/comments/18 ? It is still
crashing a lot with that error
--
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/1897765
Title:
gnome-shell crashed with signal 5 in g_log("Error in freeze/thaw
accounting") from meta_window_actor_thaw() from
WindowManager::_sizeChangedWindow
To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/1897765/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1907478] Re: integer scaling is locked between multiple monitors
The scale setting is only locked in integer mode, they can be independently adjusted if "Fractional Scaling" is selected. This probably is https://gitlab.gnome.org/GNOME/gnome-control- center/-/issues/17 ** Bug watch added: gitlab.gnome.org/GNOME/gnome-control-center/-/issues #17 https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/17 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1907478 Title: integer scaling is locked between multiple monitors To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1907478/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1907478] [NEW] integer scaling is locked between multiple monitors
Public bug reported: If you have 2 monitors with different dpi, you may want different scaling. I am trying to set one monitor at 200% and another at 100% scaling. when I try to select a scale for one monitor, it updates the scale for the other monitor as well. This is not ideal. Tested on versions up to 3.36.5 using the 4 debs available here: https://launchpad.net/ubuntu/+source/gnome-control- center/1:3.36.5-0ubuntu1/+build/20354796 ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1907478 Title: integer scaling is locked between multiple monitors To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1907478/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1907468] [NEW] visual studio code crashes gnome-shell on Ubuntu 20.10
Public bug reported: Ubuntu version: 20.10 Gnome version: 3.38.1 VScode version: 1.51.1 gnome-shell restarts on opening a file in vscode (no matter the version, snap or deb version) Steps to reproduce: 1. Set vscode as default file editor 2. Open a txt file from one location 3. Minimize vscode to dock 4. Try to open a different file -> gnome-shell restarts 5. File actually opens and can be seen after shell restarts Also opened a issue in vscode GitHub (https://github.com/microsoft/vscode/issues/109972) Some logging here: https://github.com/microsoft/vscode/issues/109972#issuecomment-738128549 or: 18:31:05 systemd: gnome-terminal-server.service: Succeeded. 18:30:56 gnome-shell: Can't update stage views actor ClutterClone is on because it needs an allocation. 18:30:56 dbus-daemon: [session uid=1000 pid=1148] Successfully activated service 'org.gnome.Logs' 18:30:56 gnome-shell: Wrong number of result metas returned by search provider org.gnome.seahorse.Application.desktop: expected 1 but got 0 18:30:56 dbus-daemon: [session uid=1000 pid=1148] Successfully activated service 'org.gnome.seahorse.Application' 18:30:55 systemd: Started GNOME Terminal Server. 18:30:55 dbus-daemon: [session uid=1000 pid=1148] Successfully activated service 'org.gnome.Terminal' 18:30:55 systemd: Starting GNOME Terminal Server... 18:30:55 dbus-daemon: [session uid=1000 pid=1148] Activating via systemd: service name='org.gnome.Terminal' unit='gnome-terminal-server.service' requested by ':1.249' (uid=1000 pid=49605 comm="/usr/bin/gnome-shell ") 18:30:55 gnome-shell: value "-inf" of type 'gfloat' is invalid or out of range for property 'height' of type 'gfloat' 18:30:50 Xorg: (--) modeset(0): HDMI max TMDS frequency 225000KHz 18:30:49 gnome-shell: Window manager warning: Overwriting existing binding of keysym 37 with keysym 37 (keycode 10). 18:30:49 gsd-media-keys: Failed to grab accelerator for keybinding settings:playback-repeat 18:30:49 gnome-shell: Error looking up permission: GDBus.Error:org.freedesktop.portal.Error.NotFound: No entry for geolocation 18:30:49 systemd: Started GNOME Shell on X11. 18:30:49 dbus-daemon: [session uid=1000 pid=1148] Successfully activated service 'org.gnome.Shell.Notifications' 18:30:49 gnome-shell: loading default theme (Adwaita) 18:30:48 dbus-daemon: [session uid=1000 pid=1148] Successfully activated service 'org.freedesktop.portal.IBus' 18:30:48 gnome-shell: Will monitor session 1 18:30:48 gsd-media-keys: Failed to grab accelerators: GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: No such interface “org.gnome.Shell” on object at path /org/gnome/Shell 18:30:48 Xorg: (--) modeset(0): HDMI max TMDS frequency 225000KHz 18:30:48 systemd: Starting GNOME Shell on X11... 18:30:48 gnome-shell: #1 7fffea7eb520 b self-hosted:850 (2da5079bfa60 @ 454) 18:30:29 systemd: gnome-terminal-server.service: Succeeded. 18:30:20 dbus-daemon: [session uid=1000 pid=1148] Successfully activated service 'org.gnome.Logs' 18:30:19 gnome-shell: Wrong number of result metas returned by search provider org.gnome.seahorse.Application.desktop: expected 1 but got 0 18:30:19 dbus-daemon: [session uid=1000 pid=1148] Successfully activated service 'org.gnome.seahorse.Application' 18:30:19 systemd: Started GNOME Terminal Server. 18:30:19 dbus-daemon: [session uid=1000 pid=1148] Successfully activated service 'org.gnome.Terminal' 18:30:19 gnome-shell: Can't update stage views actor ClutterText is on because it needs an allocation. 18:30:19 dbus-daemon: [session uid=1000 pid=1148] Successfully activated service 'org.gnome.Calculator.SearchProvider' 18:30:19 systemd: Starting GNOME Terminal Server... 18:30:19 dbus-daemon: [session uid=1000 pid=1148] Activating via systemd: service name='org.gnome.Terminal' unit='gnome-terminal-server.service' requested by ':1.212' (uid=1000 pid=46789 comm="/usr/bin/gnome-shell ") 18:30:01 cron: pam_unix(cron:session): session closed for user root 18:29:58 pkexec: gwolf2u: Executing command [USER=root] [TTY=unknown] [CWD=/home/gwolf2u] [COMMAND=/usr/libexec/gvfsd-admin --spawner :1.4 /org/gtk/gvfs/exec_spaw/5 --address unix:path=/run/user/1000/bus] 18:29:01 Xorg: (EE) event11 - G-SPY USB Gaming Mouse: client bug: event processing lagging behind by 13ms, your system is too slow 18:27:56 dbus-daemon: [session uid=1000 pid=1148] Successfully activated service 'org.gnome.Nautilus' 18:27:48 gnome-shell: value "-inf" of type 'gfloat' is invalid or out of range for property 'height' of type 'gfloat' 18:27:03 systemd: app-gnome-gnome\x2dcontrol\x2dcenter-46971.scope: Succeeded. 18:26:56 code: �[90m[main 2020-12-03T16:26:56.632Z]�[0m update#setState idle 18:26:46 Xorg: (--) modeset(0): HDMI max TMDS frequency 225000KHz 18:26:46 gnome-shell: Window manager warning: Overwriting existing binding of keysym 37 with keysym 37 (keycode 10). 18:26:46 Xorg: (--) modeset(0): HDMI max TMDS frequency 225000KHz 18:26:41 systemd: Started Application launched by gnome-shell. 18:26:39
[Bug 1881197] Re: No network usage info presented, always 0 bytes/s.
Okay, works for me. Package version: 3.36.1-0ubuntu0.20.04.1 (amd64) Details of testing: I changed the update frequency to 0.5 and 0.25 seconds and the network graph and stats continued to work, unlike before when the graph stopped displaying meaningful information. ** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-system-monitor in Ubuntu. https://bugs.launchpad.net/bugs/1881197 Title: No network usage info presented, always 0 bytes/s. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-system-monitor/+bug/1881197/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1907433] Re: [SRU] New stable release 2.64.6
** Description changed: [ Description ] Take this new upstrem stable release. Overview of changes in GLib 2.64.6 == * This is expected to be the last release in the 2.64 series; the new stable - series is 2.66, and maintenance efforts will shift to that + series is 2.66, and maintenance efforts will shift to that * Bugs fixed: - - #2194 gtk3/glib crash on gimp - - #2209 gthreadedresolver: faulty logic in parse_res_txt - - !1633 Backport !1632 Fix large writes in gfileutils to glib-2-64 - - !1634 Backport !1631 “Fix splice behavior on cancellation” to glib-2-64 - - !1656 Backport !1187 “Define G_MSVC_SYMBOL_PREFIX correctly for ARM32” to glib-2-64 - - !1659 Backport !1652 “trash portal: Handle portal failures” to glib-2-64 - - !1666 Backport !1665 “Fix g_module_symbol() under Windows sometimes not succeeding” to glib-2-64 - - !1672 Backport !1671 “gdatetime: Avoid integer overflow creating dates too far in the past” to glib-2-64 + - #2194 gtk3/glib crash on gimp + - #2209 gthreadedresolver: faulty logic in parse_res_txt + - !1633 Backport !1632 Fix large writes in gfileutils to glib-2-64 + - !1634 Backport !1631 “Fix splice behavior on cancellation” to glib-2-64 + - !1656 Backport !1187 “Define G_MSVC_SYMBOL_PREFIX correctly for ARM32” to glib-2-64 + - !1659 Backport !1652 “trash portal: Handle portal failures” to glib-2-64 + - !1666 Backport !1665 “Fix g_module_symbol() under Windows sometimes not succeeding” to glib-2-64 + - !1672 Backport !1671 “gdatetime: Avoid integer overflow creating dates too far in the past” to glib-2-64 * Translation updates: - - Croatian - - Portuguese - + - Croatian + - Portuguese Overview of changes in GLib 2.64.5 == * Fix deadlock in `g_subprocess_communicate_async()` (work by Alexander Larsson) (#2182) * Fix cross-compilation on iOS (work by Nirbheek Chauhan) (#1868) * Bugs fixed: - - !1519 Backport !1468 “glib-compile-resources: Fix exporting on Visual Studio” to glib-2-64 - - !1520 Backport !1517 “GWin32RegistryKey: Move assertions” to glib-2-64 - - !1565 Backport !1563 “gdesktopappinfo: Fix unnecessarily copied and leaked URI list” to glib-2-64 - - !1608 Backport !1607 “meson: Don't use gnulib for printf on iOS” to glib-2-64 - - !1618 Backport !1617 “Ensure g_subprocess_communicate_async() never blocks” to glib-2-64 - - !1621 Backport !1620 “gvariant: Ensure GVS.depth is initialised” to glib-2-64 - + - !1519 Backport !1468 “glib-compile-resources: Fix exporting on Visual Studio” to glib-2-64 + - !1520 Backport !1517 “GWin32RegistryKey: Move assertions” to glib-2-64 + - !1565 Backport !1563 “gdesktopappinfo: Fix unnecessarily copied and leaked URI list” to glib-2-64 + - !1608 Backport !1607 “meson: Don't use gnulib for printf on iOS” to glib-2-64 + - !1618 Backport !1617 “Ensure g_subprocess_communicate_async() never blocks” to glib-2-64 + - !1621 Backport !1620 “gvariant: Ensure GVS.depth is initialised” to glib-2-64 Overview of changes in GLib 2.64.4 == * Bugs fixed: - - #2140 calling malloc in fork child is undefined-behaviour - - !1507 Backport !1504 “win32 gpoll: Fix wait for at least one thread to return” to glib-2-64 - - !1523 Backport !1522 “meson: Fix gnulib printf checks” to glib-2-64 - - !1547 Backport !1544 “Resolve "calling malloc in fork child is undefined-behaviour"” to glib-2-64 + - #2140 calling malloc in fork child is undefined-behaviour + - !1507 Backport !1504 “win32 gpoll: Fix wait for at least one thread to return” to glib-2-64 + - !1523 Backport !1522 “meson: Fix gnulib printf checks” to glib-2-64 + - !1547 Backport !1544 “Resolve "calling malloc in fork child is undefined-behaviour"” to glib-2-64 * Translation updates: - - Kazakh - - Slovenian + - Kazakh + - Slovenian [ QA ] Upstream release, so QA already performed by maintainers https://wiki.ubuntu.com/StableReleaseUpdates/GNOME This upload will trigger many autopkgtests that we expect to not be regressed by this upload. - [ Regression potential ] + [ What could go wrong ] - Various fixes in multiple places so multiple apps could be affected. + This update contains fixes in multiple places so multiple apps could be + affected. The consequences of a broken GLib can range from some + functions returning bad results sometimes, which have minimal runtime + implications, up to the system simply crashing all the time. + Pretty much all parts of GNOME use GLib, so test anything in the desktop that you can. If you reboot the machine and can get to the desktop, that's already tested GLib extensively. But also run applications like GNOME terminal, Files and Epiphany. ** Description changed: [ Description ] Take this new upstrem stable release. + + It was easiest for me to merge the latest release in this series from + Debian,
[Bug 1907433] [NEW] [SRU] New stable release 2.64.6
Public bug reported: [ Description ] Take this new upstrem stable release. Overview of changes in GLib 2.64.6 == * This is expected to be the last release in the 2.64 series; the new stable series is 2.66, and maintenance efforts will shift to that * Bugs fixed: - #2194 gtk3/glib crash on gimp - #2209 gthreadedresolver: faulty logic in parse_res_txt - !1633 Backport !1632 Fix large writes in gfileutils to glib-2-64 - !1634 Backport !1631 “Fix splice behavior on cancellation” to glib-2-64 - !1656 Backport !1187 “Define G_MSVC_SYMBOL_PREFIX correctly for ARM32” to glib-2-64 - !1659 Backport !1652 “trash portal: Handle portal failures” to glib-2-64 - !1666 Backport !1665 “Fix g_module_symbol() under Windows sometimes not succeeding” to glib-2-64 - !1672 Backport !1671 “gdatetime: Avoid integer overflow creating dates too far in the past” to glib-2-64 * Translation updates: - Croatian - Portuguese Overview of changes in GLib 2.64.5 == * Fix deadlock in `g_subprocess_communicate_async()` (work by Alexander Larsson) (#2182) * Fix cross-compilation on iOS (work by Nirbheek Chauhan) (#1868) * Bugs fixed: - !1519 Backport !1468 “glib-compile-resources: Fix exporting on Visual Studio” to glib-2-64 - !1520 Backport !1517 “GWin32RegistryKey: Move assertions” to glib-2-64 - !1565 Backport !1563 “gdesktopappinfo: Fix unnecessarily copied and leaked URI list” to glib-2-64 - !1608 Backport !1607 “meson: Don't use gnulib for printf on iOS” to glib-2-64 - !1618 Backport !1617 “Ensure g_subprocess_communicate_async() never blocks” to glib-2-64 - !1621 Backport !1620 “gvariant: Ensure GVS.depth is initialised” to glib-2-64 Overview of changes in GLib 2.64.4 == * Bugs fixed: - #2140 calling malloc in fork child is undefined-behaviour - !1507 Backport !1504 “win32 gpoll: Fix wait for at least one thread to return” to glib-2-64 - !1523 Backport !1522 “meson: Fix gnulib printf checks” to glib-2-64 - !1547 Backport !1544 “Resolve "calling malloc in fork child is undefined-behaviour"” to glib-2-64 * Translation updates: - Kazakh - Slovenian [ QA ] Upstream release, so QA already performed by maintainers https://wiki.ubuntu.com/StableReleaseUpdates/GNOME This upload will trigger many autopkgtests that we expect to not be regressed by this upload. [ Regression potential ] Various fixes in multiple places so multiple apps could be affected. Pretty much all parts of GNOME use GLib, so test anything in the desktop that you can. If you reboot the machine and can get to the desktop, that's already tested GLib extensively. But also run applications like GNOME terminal, Files and Epiphany. ** Affects: glib2.0 (Ubuntu) Importance: Undecided Status: Fix Released ** Affects: glib2.0 (Ubuntu Focal) Importance: Undecided Assignee: Iain Lane (laney) Status: In Progress ** Also affects: glib2.0 (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: glib2.0 (Ubuntu Focal) Status: New => In Progress ** Changed in: glib2.0 (Ubuntu Focal) Assignee: (unassigned) => Iain Lane (laney) ** Changed in: glib2.0 (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1907433 Title: [SRU] New stable release 2.64.6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1907433/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1905729] Re: power button configuration broken
alright, how did you manage to get fsck active for a non existing disk? did you hotswap out the disk while the machine was on? it seems a udisk issue somehow that it's possible to get it stucked -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1905729 Title: power button configuration broken To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1905729/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1897765] Re: gnome-shell crashed with signal 5 in g_log("Error in freeze/thaw accounting") from meta_window_actor_thaw() from WindowManager::_sizeChangedWindow
Hi, just to confirm that I was also experiencing the citrix issue and it
has been resolved by the patch in Ernst's PPA. Thanks for the fix and
the PPA - the issue was really starting to annoy me!
--
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/1897765
Title:
gnome-shell crashed with signal 5 in g_log("Error in freeze/thaw
accounting") from meta_window_actor_thaw() from
WindowManager::_sizeChangedWindow
To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/1897765/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1798166] Re: “Mouse battery low” notification can't be disabled
Follow-up to Comment #36: Although patching upower fixes the issue, gnome-settings-daemon is still broken, since disabling notifications won't disable all notifications. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1798166 Title: “Mouse battery low” notification can't be disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1798166/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1798166] Re: “Mouse battery low” notification can't be disabled
FYI, here's the corresponding bug in GNOME: https://gitlab.gnome.org/GNOME/gnome-settings-daemon/-/issues/108 And here's the workaround: https://wrgms.com/disable-mouse-battery-low- spam-notification/ ** Bug watch added: gitlab.gnome.org/GNOME/gnome-settings-daemon/-/issues #108 https://gitlab.gnome.org/GNOME/gnome-settings-daemon/-/issues/108 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1798166 Title: “Mouse battery low” notification can't be disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1798166/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
