date:20201002

[Expired for gnome-shell (Ubuntu) because there has been no activity for
60 days.]

** Changed in: gnome-shell (Ubuntu)
   Status: Incomplete => Expired

-- 
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/1890124

Title:
  I can't click on the bottom ~25 % of the screen

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1890124/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1890124] Re: I can't click on the bottom ~25 % of the screen

[Expired for mutter (Ubuntu) because there has been no activity for 60
days.]

** Changed in: mutter (Ubuntu)
   Status: Incomplete => Expired

-- 
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/1890124

Title:
  I can't click on the bottom ~25 % of the screen

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1890124/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1898153] Re: I upgraded from 18.04 to 20.04.1 and the screen doesn't lock or go blank at the set time.

Sure

The Keyboard Shortcuts for Lock Screen is set to Ctrl+Alt+L
Found in Settings -> Keyboard Shortcuts -> Lock screen -> Ctrl+Alt+L

1) I can't lock the screen using the (keybinding / shortcut) Ctrl+Alt+L 
https://i.imgur.com/VKiXvZV.png

2) I can lock the screen by clicking on the lock option but the screen doesn't 
go blank
https://i.imgur.com/JDHEs2Q.png

3) Here's something that looks interesting I found in the journalctlr file
Oct 02 19:18:52 sys76 gnome-shell[2577]: meta_window_raise: assertion 
'!window->override_redirect' failed
Oct 02 19:18:52 sys76 gnome-shell[2577]: meta_window_lower: assertion 
'!window->override_redirect' failed
Oct 02 19:18:56 sys76 gsd-media-keys[2742]: Couldn't lock screen: Cannot invoke 
method; proxy is for the well-known name org.gnome.ScreenSaver without an 
owner, and proxy was constructed with the G_DBUS_PROXY_FLAGS_DO_NOT_AUTO_START 
flag

4) The full file is below


** Attachment added: "journalctl -b 0 > jour.txt  file requested"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1898153/+attachment/5416816/+files/jour.txt

-- 
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/1898153

Title:
  I upgraded from 18.04 to 20.04.1 and  the screen doesn't lock or go
  blank at the set time.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1898153/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1891270] Re: Iranian calendar shows in Azerbaijani language

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: ubiquity (Ubuntu)
   Status: New => Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-calendar in Ubuntu.
https://bugs.launchpad.net/bugs/1891270

Title:
  Iranian calendar shows in Azerbaijani language

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-calendar/+bug/1891270/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1872159] Re: booting with splash hangs when external monitors are connected

2020-10-02 Thread Tim Wetzel

This bug recurred with the last two 20.04 Updater packages, starting
mid-September. The initramfs upacking bug 1835660 recurred about the
same time. Turning off the Ubuntu splash screen seems to avoid the
problem, but when it doesn't (or until you realize that you have to make
that change); the spinning logo hang forces a hard power down which
seems to cause other problems and affects general stability.

-- 
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/1872159

Title:
  booting with splash hangs when external monitors are connected

To manage notifications about this bug go to:
https://bugs.launchpad.net/plymouth/+bug/1872159/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1898153] Re: I upgraded from 18.04 to 20.04.1 and the screen doesn't lock or go blank at the set time.

2020-10-02 Thread Sebastien Bacher

Could you add your 'journalctl -b 0' log after getting the issue? can
you manually lock the screen from the indicator or using the keybinding?

-- 
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/1898153

Title:
  I upgraded from 18.04 to 20.04.1 and  the screen doesn't lock or go
  blank at the set time.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1898153/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1868293] Re: gnome-shell crashed in meta_workspace_index: Workspace does not exist to index!

2020-10-02 Thread Marius Zaharie

I'm from an upgraded ubuntu 20.04 notebook that freezes less than 1
minute after login. The only time it unfrozen a bit it thrown the popup
with this error. Well, at least there was the link to this bug as
duplicate or something.

The solution they suggested here 
https://forums.developer.nvidia.com/t/ubuntu-20-04-screen-freezes-after-5-minutes-of-uptime-with-nvidia-drivers/122297
 didn't work.
So I think it's something in gnome--ubuntu20.04

-- 
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/1868293

Title:
  gnome-shell crashed in meta_workspace_index: Workspace does not exist
  to index!

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1868293/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 62949]

2020-10-02 Thread Rickstockton-7

(In reply to Nate Graham from comment #41)
> 
> Even if there's no explicit Qt support (is this still true?) we could still
> implement it ourselves on the KDE side.
I should note that Qt support is explicitly "good" for X11, and Wayland seems 
ready for up to 16 buttons. The reasons why I should no longer be the assignee 
are (1) the fact that I am unqualified to make the 'visionary' choices: which 
buttons should default to which actions; and (2) the glue which must hold it 
together (clicks -> signals and slots for "actions") and (3) making coherent 
updates for all of the programs which should perhaps make use of 
higher-numbered buttons.

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-system-tools in Ubuntu.
https://bugs.launchpad.net/bugs/62949

Title:
  No way to configure mouse button number

To manage notifications about this bug go to:
https://bugs.launchpad.net/kdelibs/+bug/62949/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 62949]

2020-10-02 Thread Rickstockton-7

(In reply to Nate Graham from comment #41)
> Re-opening since this is a reasonable request. Binding shortcuts/actions to
> additional mouse buttons seems reasonable.
> 
> Even if there's no explicit Qt support (is this still true?) we could still
> implement it ourselves on the KDE side.

I'm not much of a programmer. It seems that KGlobalAccel would need some
new member function signatures, creating a bit of a mess for backward
compatibility. Or, would it be better to create an entire new class for
"KGlobalMouseAccel" ?

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-system-tools in Ubuntu.
https://bugs.launchpad.net/bugs/62949

Title:
  No way to configure mouse button number

To manage notifications about this bug go to:
https://bugs.launchpad.net/kdelibs/+bug/62949/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 62949]

2020-10-02 Thread Rickstockton-7

(removed myself as assignee)

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-system-tools in Ubuntu.
https://bugs.launchpad.net/bugs/62949

Title:
  No way to configure mouse button number

To manage notifications about this bug go to:
https://bugs.launchpad.net/kdelibs/+bug/62949/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1897959] Re: Audio Shuts Down with Screen Blanking

2020-10-02 Thread Cliff Carson

The problem is with Pithos 1.5 which I recently installed.  It has two
optional setting.  One looks like it disables the screen saver (screen
blanking) and the other is not to pause in screen saver mode (my problem
os loosing audio).

-- 
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/1897959

Title:
  Audio Shuts Down with Screen Blanking

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1897959/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1848277] Re: Won't start, get "cannot open display: :0" message

2020-10-02 Thread Martin Vysny

Also does not work for me on Ubuntu 20.10 when running on Xorg.

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-calculator in Ubuntu.
https://bugs.launchpad.net/bugs/1848277

Title:
  Won't start, get "cannot open display: :0" message

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-calculator/+bug/1848277/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1898153] Re: I upgraded from 18.04 to 20.04.1 and the screen doesn't lock or go blank at the set time.

1. The specific steps or actions you took that caused you to encounter
the problem.

-I tried to set the screen to lock at a specific interval and it doesn't lock
Settings-> Privacy-> Screen Lock -> Automatic Screen Lock -> Enabled
Settings-> Privacy-> Screen Lock -> Automatic Screen Lock -> 30 seconds

-The screen doesn't go blank at all (option found under)
Settings-> Privacy-> Screen Lock -> Blank screen Delay -> 1 minute

2. The behavior you expected.
It should lock the screen and have the screen go blank but it doesn't

3. The behavior you actually encountered (in as much detail as possible).
Nothing happens the screen doesn't lock or goes blank.

Please also ensure that you include the release and flavour of Ubuntu that you
are using.
I upgraded from 18.04 to 20.04.1 using the sotware updater GUI
rt@sys76:~$ uname -a
Linux sys76 5.4.0-48-generic #52-Ubuntu SMP Thu Sep 10 10:58:49 UTC 2020 x86_64
x86_64 x86_64 GNU/Linux

About me including the file-manager being nemo I was just trying to
include everything I could think of to help out.

If you need anything else let me know.

--
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/1898153

Title:
I upgraded from 18.04 to 20.04.1 and the screen doesn't lock or go
blank at the set time.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1898153/+subscriptions

--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1898153] Re: I upgraded from 18.04 to 20.04.1 and the screen doesn't lock or go blank at the set time.

Should be: 
Settings-> Privacy-> Screen Lock -> Automatic Screen Lock Delay -> 30 seconds

-- 
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/1898153

Title:
  I upgraded from 18.04 to 20.04.1 and  the screen doesn't lock or go
  blank at the set time.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1898153/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1898153] Re: I upgraded from 18.04 to 20.04.1 and the screen doesn't lock or go blank at the set time.

2020-10-02 Thread Sebastien Bacher

The description isn't clear, it doesn't lock at the same time than what?
Also what has the filemanager having to do with the issue?

-- 
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/1898153

Title:
  I upgraded from 18.04 to 20.04.1 and  the screen doesn't lock or go
  blank at the set time.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1898153/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1898153] Re: I upgraded from 18.04 to 20.04.1 and the screen doesn't lock or go blank at the set time.

2020-10-02 Thread Sebastien Bacher

Thank you for taking the time to report this bug and helping to make
Ubuntu better. Unfortunately, we cannot work on this bug because your
description didn't include enough information. You may find it helpful
to read "How to report bugs effectively"
http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful
if you would then provide a more complete description of the problem.

We have instructions on debugging some types of problems at
http://wiki.ubuntu.com/DebuggingProcedures.

At a minimum, we need:

1. The specific steps or actions you took that caused you to encounter the
problem.
2. The behavior you expected.
3. The behavior you actually encountered (in as much detail as possible).

Please also ensure that you include the release and flavour of Ubuntu
that you are using.

Thank you!

** Changed in: gnome-control-center (Ubuntu)
Importance: Undecided => Low

** Changed in: gnome-control-center (Ubuntu)
Status: New => Incomplete

--
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/1898153

Title:
I upgraded from 18.04 to 20.04.1 and the screen doesn't lock or go
blank at the set time.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1898153/+subscriptions

--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1897832] Re: gnome-shell crashed with SIGTRAP in meta_window_actor_thaw() from meta_window_x11_update_sync_request_counter() from handle_other_xevent() from meta_x11_display_handle_xevent() from

2020-10-02 Thread Bug Watch Updater

** Changed in: gnome-shell (Fedora)
   Status: Unknown => Won't Fix

** Changed in: gnome-shell (Fedora)
   Importance: Unknown => Undecided

-- 
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/1897832

Title:
  gnome-shell crashed with SIGTRAP in meta_window_actor_thaw() from
  meta_window_x11_update_sync_request_counter() from
  handle_other_xevent() from meta_x11_display_handle_xevent() from
  xevent_filter()

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1897832/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1898153] Re: I upgraded from 18.04 to 20.04.1 and the screen doesn't lock or go blank at the set time.

The options for locking, blanking and shortcut keys are in the gnome-
control-center

** Package changed: ubuntu => gnome-control-center (Ubuntu)

-- 
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/1898153

Title:
  I upgraded from 18.04 to 20.04.1 and  the screen doesn't lock or go
  blank at the set time.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1898153/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1898153] [NEW] I upgraded from 18.04 to 20.04.1 and the screen doesn't lock or go blank at the set time.

You have been subscribed to a public bug:

I upgraded from 18.04 to 20.04.1 and  the screen doesn't lock or go
blank at the set time.  I think this issue also effects the shortcuts
not working also.

I'm using nemo as my file manager I followed these instructions below

https://itsfoss.com/install-nemo-file-manager-ubuntu/

** Affects: gnome-control-center (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: bot-comment
-- 
I upgraded from 18.04 to 20.04.1 and  the screen doesn't lock or go blank at 
the set time.
https://bugs.launchpad.net/bugs/1898153
You received this bug notification because you are a member of Ubuntu Desktop 
Bugs, which is subscribed to gnome-control-center in Ubuntu.

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1897959] Re: Audio Shuts Down with Screen Blanking

2020-10-02 Thread Cliff Carson

The audio feed from the io ports is indeed going to a stand alone
bluetooth transmitter located central in the house.  I did split off the
audio cable to feed a stereo located next to the desktop.  The stereo
also looses the audio feed when the screen blanks.

-- 
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/1897959

Title:
  Audio Shuts Down with Screen Blanking

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1897959/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1897959] Re: Audio Shuts Down with Screen Blanking

2020-10-02 Thread Cliff Carson

the bud id of the associated crash 1898090

-- 
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/1897959

Title:
  Audio Shuts Down with Screen Blanking

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1897959/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1888983] Re: Suspend notification wakes external monitor.

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: gnome-shell (Ubuntu)
   Status: New => Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1888983

Title:
  Suspend notification wakes external monitor.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1888983/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 260334] Re: gvfs FTP only does passive connections

2020-10-02 Thread David V.

Ubuntu version : 20.04
How to trigger :

1) Lauch nautilus
2) Type CTRL-L
3) Type ftp://
4) The dialog opens and asks for an anonymous connection or a username and a 
password.
5) Type an username and password
6) Nautilus is stuck trying to load the directory.

The FTP I'm trying to connect to is private, so I can't share the IP address.
Using command-line FTP, it is possible to retrieve the directory listing or 
download a file only after exiting passive mode.

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
https://bugs.launchpad.net/bugs/260334

Title:
  gvfs FTP only does passive connections

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/260334/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1897832] Re: /usr/bin/gnome-shell:5:meta_window_actor_thaw:meta_window_x11_update_sync_request_counter:handle_other_xevent:meta_x11_display_handle_xevent:xevent_filter

** This bug is no longer a duplicate of bug 1897765
   gnome-shell crashed with signal 5 in g_log("Error in freeze/thaw 
accounting") from meta_window_actor_thaw() from 
WindowManager::_sizeChangedWindow

** Bug watch added: Red Hat Bugzilla #1402492
   https://bugzilla.redhat.com/show_bug.cgi?id=1402492

** Also affects: gnome-shell (Fedora) via
   https://bugzilla.redhat.com/show_bug.cgi?id=1402492
   Importance: Unknown
   Status: Unknown

** Summary changed:

- 
/usr/bin/gnome-shell:5:meta_window_actor_thaw:meta_window_x11_update_sync_request_counter:handle_other_xevent:meta_x11_display_handle_xevent:xevent_filter
+ gnome-shell crashed with SIGTRAP in meta_window_actor_thaw() from 
meta_window_x11_update_sync_request_counter() from handle_other_xevent() from 
meta_x11_display_handle_xevent() from xevent_filter()

-- 
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/1897832

Title:
  gnome-shell crashed with SIGTRAP in meta_window_actor_thaw() from
  meta_window_x11_update_sync_request_counter() from
  handle_other_xevent() from meta_x11_display_handle_xevent() from
  xevent_filter()

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1897832/+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

** Summary changed:

- gnome-shell crashed with signal 5 in g_log("Error in freeze/thaw accounting") 
from meta_window_actor_thaw()
+ gnome-shell crashed with signal 5 in g_log("Error in freeze/thaw accounting") 
from meta_window_actor_thaw() from WindowManager::_sizeChangedWindow

** Package changed: mutter (Ubuntu) => gnome-shell (Ubuntu)

-- 
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/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 1897765] Re: gnome-shell crashed with signal 5 in g_log("Error in freeze/thaw accounting") from meta_window_actor_thaw()

Timo,

Can you test this?

https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/1453.patch

-- 
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/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 1897765] Re: gnome-shell crashed with signal 5 in g_log("Error in freeze/thaw accounting") from meta_window_actor_thaw()