[Expired for gnome-shell-extension-ubuntu-dock (Ubuntu) because there
has been no activity for 60 days.]
** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscrib
Thanks for the explanation, I can understand the difficulty and hope
misbehaving external extensions don't affect the image of GNOME too
much.
I will reactivate the dock and repeat the steps in comments #1 and #3 at
the next crash, although I'm unsure how that will bring new information
as I would
Regarding your other question; sandboxing would of course be best but
that's something that would need to be designed from the ground up. And
then new APIs specifically for sandboxed extensions would be needed. And
then we would still find either most extensions want to do things not
possible in th
Bug 1951786 would not explain these crashes, it's just something I saw
in your log.
To track down the crashes further you would need to repeat the steps in
comments #1 and #3. But at least it sounds like we can assign it to
ubuntu-dock now. Probably.
** Package changed: gnome-shell (Ubuntu) => g
I'm sure the discussion has been held elsewhere, and there's been made a
case against sandboxing them or handling their crashes, as lack of
freedom would defeat the very purpose of these extensions?
At any rate I'm happy to have reached a solution. 3 monitor unplugs
without crashes convinces me th
Extensions have free reign to do anything, including crash the shell.
They are the causes of lots of our bugs. The alternative would be to
disallow extensions which would be more stable but probably less
popular.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
After a few more disconnects with the Ubuntu Dock disabled and no
crashes, it sounds like the culprit may be the Ubuntu Dock. The solution
should be relatively simple then (although I'm a bit shocked that it can
take down mutter)
--
You received this bug notification because you are a member of U
Funnily, after disabling the Ubuntu Dock (have not yet logged out and in
again) and unplugging my cable, there was no crash. Then again, the
crashes are not consistent so I'll try again.
This interferes with my work so much that I cannot test this constantly.
--
You received this bug notificatio
The log in comment #12 seems to mostly match bug 1951786 so maybe try
briefly disabling the Ubuntu Dock extension in the 'Extensions' app and
then log in again.
If that has not fixed the problem then please repeat the steps in
comment #3. Then if you see the same messages as in comment #5 please
o
Hello Daniel, thanks for your help. Please find the requested
information attached. Two extra points:
- I set the external monitor as my primary monitor, with the dock and title bar
displaying here
- Since 40.1 already contains the fix for the symptoms you quoted from my
report, while they are t
apport information
** Tags added: apport-collected impish third-party-packages wayland-
session
** Description changed:
This bug has been persisting since I've bought an external monitor for
my laptop and started using Wayland (first on Ubuntu 20.04) until today
(Ubuntu 21.10).
It isn
Since it sounds like you already have the fix for bug 1754687, this bug
is now reopened.
Next please run 'apport-collect 1952766' to attach more information
about the system. Once we confirm the package versions a new upstream
bug will need to be created.
** This bug is no longer a duplicate of
*** This bug is a duplicate of bug 1754687 ***
https://bugs.launchpad.net/bugs/1754687
** Tags removed: impish
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1952766
Title:
Disconnecting monitor
*** This bug is a duplicate of bug 1754687 ***
https://bugs.launchpad.net/bugs/1754687
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1754687, so it is being marked as such. Please look
*** This bug is a duplicate of bug 1754687 ***
https://bugs.launchpad.net/bugs/1754687
This looks like the problem:
dec 02 23:11:31 tuhao2 gnome-shell[8076]:
meta_monitor_manager_get_logical_monitor_from_number: assertion '(unsigned int)
number < g_list_length (manager->logical_monitors)' f
attached is a log after reproducing the bug, crashing, logging in,
waiting 10 seconds, rebooting, and logging. NOTE: edited for privacy
reasons (names, references to VPN connections)
** Attachment added: "prevboot.txt"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1952766/+attachm
If 'ubuntu-bug' doesn't work then please try 'apport-cli'. Please also
check https://errors.ubuntu.com/user/ID again.
Also, next time the crash happens please:
1. Wait 10 seconds.
2. Reboot.
3. Run:
journalctl -b-1 > prevboot.txt
4. Attach the resulting text file here.
--
You received th
Thanks. The bug report is now attached to this bug.
(Some asides about the bug-uploading process:)
There was already a _usr_bin_gnome-shell.1000.crash.uploaded file,
however I cannot see my bug in errors.ubuntu.com. So I went and tried
doing it manually:
```
$ ubuntu-bug _usr_bin_gnome-shell.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
19 matches
Mail list logo
