*** This bug is a duplicate of bug 1986455 ***
https://bugs.launchpad.net/bugs/1986455
Thank you for taking the time to report this crash and helping to make
this software better. This particular crash has already been reported
and is a duplicate of bug #1986455, so is being marked as such.
How to reproduce:
* Startup 22.10 beta ISO image
* Enable "Install third-party software for graphics and Wi-Fi hardware and
additional media format" on "Update and Software" step.
* Complete installs and reboot
* No startup GDM session
More simple step:
* Install gstreamer1.0-vaapi package on
** Also affects: gnome-shell (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: gnome-shell (Ubuntu)
** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/-/issues #5932
https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/5932
** Also affects: gnome-shell via
Yes people should be able to promote a feature advertised during
install...
While the bug remains open, a workaround is to:
1. Install *without* the third-party option.
2. sudo apt install ubuntu-restricted-extras
3. sudo apt remove gstreamer1.0-vaapi
--
You received this bug notification
I am using 22.04.1 and GNOME 42.4, this bug is still there
** Attachment added: "Screenshot from 2022-10-04 14-19-00.png"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1970800/+attachment/5620944/+files/Screenshot%20from%202022-10-04%2014-19-00.png
--
You received this bug
I'm using VirtualBox to test upcoming Ubuntu versions using the exact
same config and packages that will later be used on several physical
machines. So it's pretty important to me to install the third-party
packages in VMs as well. But yes, I can live with the workaround for
now.
--
You received
That makes sense, and I have done the same in the past. Although this
bug highlights the fact that those third-party packages behave
differently and exercise different code paths in virtual vs real
machines.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs,
** Also affects: gnome-shell (Ubuntu)
Importance: Undecided
Status: New
** Changed in: gnome-shell (Ubuntu)
Importance: Undecided => Medium
** Changed in: gnome-shell (Ubuntu)
Status: New => Confirmed
** Changed in: gnome-shell (Ubuntu)
Status: Confirmed => Triaged
I moved all my applications to virtual machines, I use 6 VMs for that
purpose. One VM is dealing with all multimedia apps and I need all
codecs there. That is, why the Host OS is a minimal install of Ubuntu
22.04 LTS, so without any Apps except Firefox.
I can live with my Xorg workaround for 2
I am experiencing the same issue to this day. I have sent many crash
reports about it.
Ubuntu 22.04.1 LTS
Linux Kernel 5.15.0-48-generic
I'm using Wayland.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to nautilus in Ubuntu.
** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/-/issues #5933
https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/5933
** Also affects: gnome-shell via
https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/5933
Importance: Unknown
Status: Unknown
--
You received this bug
Public bug reported:
This is for version 42.0 of gnome-system-monitor on Ubuntu 22.04 LTS.
The update interval setting is off by one decimal place specifically for
the setting that affects the resources tab. So if the update interval is
set to 0.10 seconds, it will refresh every second. If it's
Public bug reported:
over day gnome-shell memory usage increase to 1GB and more. I have 2 enabled
extensions:
gnome-extensions list --enabled
ubuntu-appindicat...@ubuntu.com
ubuntu-d...@ubuntu.com
other info:
lsb_release -rd
Description:Ubuntu 22.04.1 LTS
Release:22.04
You have been subscribed to a public bug:
When unlocking A screen in gnome desktop in Ubuntu 22.04
if there are NFS mounted drives (using fstab) and bookmarks are added to those
in Files, gnome does some kind of access to those folders before unlocking the
screen
In specific case if the NFS
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: gnome-system-monitor (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-system-monitor in Ubuntu.
I'm having the same issue on 22.04.1 LTS with gnome-system-monitor
version 42. I have 32GB of RAM installed and system monitor reports
33.4GB for some reason.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-system-monitor in
** Package changed: ubuntu => gnome-screensaver (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-screensaver in Ubuntu.
https://bugs.launchpad.net/bugs/1991665
Title:
Ubuntu 22.04 screensaver unlock issue with NFS
looks like https://gitlab.gnome.org/GNOME/gtk/-/merge_requests/5070
addresses this in gtk3 apps, can it (and/or the next gtk release) be
added to the ubuntu package and the snap package that contains gtk3
(gnome-* snap?)
--
You received this bug notification because you are a member of Ubuntu
I think comment #5 is describing bug 1988488.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-session in Ubuntu.
https://bugs.launchpad.net/bugs/1988786
Title:
system does not boot after full-upgrade on kinetic
To manage
That issue was being tracked in bug 1943558 too...
I don't think any patching is necessary here. The very low rate of
reports of this issue, and the simplicity of the workaround, indicate
that we don't need to prioritise this bug.
** Also affects: gnome-shell via
** Summary changed:
- Panel freezes on return from screensaver with external monitor attached
+ Laptop panel freezes on return from screensaver with external monitor attached
** Changed in: ubuntu
Status: Incomplete => New
** Package changed: ubuntu => gnome-shell (Ubuntu)
--
You
This is the GNOME issue tracking this upstream.
https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/4071
It was introduced into GNOME 40 by this commit.
https://gitlab.gnome.org/GNOME/gnome-settings-
daemon/-/commit/e90a75fd59ac41aa331f53492a84712e43bcbce2
There was an attempt to revert it
The verification of the Stable Release Update for evolution has
completed successfully and the package is now being released to
-updates. Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you
** No longer affects: 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/1991724
Title:
system monitor fails with Nvideo multi-monitor
To manage notifications
Moving to private to avoid "me too" comments from other users. Everyone
should log their own separate bugs.
** Information type changed from Public to Private
** Changed in: gnome-shell (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of
It appears you also have extension 'removeappm...@dragon8oy.com'
enabled. Please start by deleting all local extensions:
cd ~/.local/share/gnome-shell
rm -rf extensions
and then log in again and tell us if the leak still happens. If you find
the leak is still happening then please run:
ps
While others are commenting on this, it's worth noting that during this
freeze issue on the lockscreen the computer may still be responsive to
keyboard input when a correct password + enter was inputted.
For example, if I have an application (e.g. calendar reminder
notifications, or a browser +
You have been subscribed to a public bug:
I have four monitors attached to my Nvideo card, and when I try to run
the system monitor it does not come up. The icon in the left panel shows
that one instance is running, but there is no way to bring up the actual
window (a picture of the activated
This bug was fixed in the package evolution - 3.44.4-0ubuntu1
---
evolution (3.44.4-0ubuntu1) jammy; urgency=medium
* New upstream release (LP: #1976623)
* Bump e-d-s dependencies and build-dependencies to 3.44.3
-- Nathan Pratta Teodosio Wed, 10 Aug
2022 12:12:31 -0400
**
I have the same problem on 2 installs out of 3. And no "Removing a
network device that was not added" in /var/log/syslog.
I also found that the problem does not seem to occur on Xorg, only on
Wayland.
And I also found that the work around is to go to a console and then
back using (e.g.)
You have been subscribed to a public bug:
My setup is composed of a Dell XPS13 9320, with one (or two) external
USB-C monitors attached. The laptop panel is the primary screen. I'm
using gnome on Wayland.
Everything is working fine, except when resuming from screensaver: the
prompt for password
** Tags added: nvidia
** Package changed: xorg (Ubuntu) => mutter (Ubuntu)
** Also affects: gnome-shell (Ubuntu)
Importance: Undecided
Status: New
** Tags added: multimonitor
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed
I'm not totally sure that's a fix, but let's assume it is.
** Changed in: gtk+3.0 (Ubuntu)
Status: Confirmed => Fix Committed
** Tags added: fixed-in-gtk-3.24.35 fixed-upstream
** Also affects: mutter via
https://gitlab.gnome.org/GNOME/mutter/-/issues/602
Importance: Unknown
33 matches
Mail list logo
