*** This bug is a duplicate of bug 1970291 ***
https://bugs.launchpad.net/bugs/1970291
This bug is closed because it's a duplicate of bug 1970291.
If you have found any new bugs in comments #8 - #18 then please open new
bug reports for them.
--
You received this bug notification because
*** This bug is a duplicate of bug 1970291 ***
https://bugs.launchpad.net/bugs/1970291
Appears to be a red herring, VirtualBox apparently experiences random
guest crashes when split lock detection is enabled on the Host OS. ( I
am able to verify this )
Reference:
"Random crashes with Windows
Tested version 44.3-0ubuntu1 of libmutter-12-0 on ubuntu budgie.
Test case I substituted settings for budgie-control-center. No
regressions noted.
Checked general window management - max, min, tiling as well as side-by-side
tiling. No regressions. No reported /var/crash type stuff.
Checked
*** This bug is a duplicate of bug 1970291 ***
https://bugs.launchpad.net/bugs/1970291
This may be unrelated -- but I am also seeing "x86/split lock detection"
errors. Is this just a red herring ? Only seeing these when using the
VirtualBox to drive the GPU.
[Tue Jul 11 14:50:44 2023] usb
*** This bug is a duplicate of bug 1970291 ***
https://bugs.launchpad.net/bugs/1970291
Notably, when I "enable 3d" with a windows 10 guest on VirtualBox, I can
see the GPU being actively used!
Now, if there was only a way to use it with Xorg on the Host machine,
not just the guest.
--
You
*** This bug is a duplicate of bug 1970291 ***
https://bugs.launchpad.net/bugs/1970291
Then onto check why the GPU is not even being detected ...
beadon@semiauto:~$ sudo nvidia-smi
NVIDIA-SMI has failed because it couldn't communicate with the NVIDIA driver.
Make sure that the latest NVIDIA
*** This bug is a duplicate of bug 1970291 ***
https://bugs.launchpad.net/bugs/1970291
setting the PRIME profile back into place for NVIDIA.
This causes the gdm issues, I suspect because this promotes the eGPU to
primary and there is some kind of resource sharing problem.
So, the way it
*** This bug is a duplicate of bug 1970291 ***
https://bugs.launchpad.net/bugs/1970291
ok, SUPER interesting -- when I force the intel profile to be PRIME,
then I can safely boot with the enclosure attached(!), the systems gets
through gdm, and I can login no problem.
I suspect there is a
*** This bug is a duplicate of bug 1970291 ***
https://bugs.launchpad.net/bugs/1970291
I am also seeing a couple things like this ..
options nvidia-drm modeset=1
Perhaps this is a path I need to take and specify PRIME vs non-prime ?
*** This bug is a duplicate of bug 1970291 ***
https://bugs.launchpad.net/bugs/1970291
worse still , now I cannot get a gdm login unless I disconnect the USB-C
eGPU (this NVIDIA GPU enclosure).
I am reading up further on "prime" and "reverse prime" GPUs. The behavior here
may be similar:
** Changed in: glib2.0 (Ubuntu)
Status: New => In Progress
** Changed in: glib2.0 (Ubuntu)
Importance: Undecided => High
** Changed in: glib2.0 (Ubuntu)
Assignee: (unassigned) => Sebastien Bacher (seb128)
--
You received this bug notification because you are a member of Ubuntu
*** This bug is a duplicate of bug 1970291 ***
https://bugs.launchpad.net/bugs/1970291
Notably -- there seems to be a known issue with DisplayPort connectivity
1.3 and 1.4 and NVIDIA GPUs recently.
I am seeing a firmware update issued by NVIDIA on June 26 2023 for SOME NVIDIA
chipsets:
*** This bug is a duplicate of bug 1970291 ***
https://bugs.launchpad.net/bugs/1970291
As expected I am using Xorg now,
beadon@semiauto:~$ echo $XDG_SESSION_TYPE
x11
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in
*** This bug is a duplicate of bug 1970291 ***
https://bugs.launchpad.net/bugs/1970291
I was unable to select the "Ubuntu on Xorg" as a configuration option,
so I did it manually.
I modified /etc/gdm3/custom.conf
current configuration:
# GDM configuration storage
#
# See
I installed gjs 1.76.2-1ubuntu23.04.1 on Ubuntu 23.04 and successfully
completed both test cases.
** Tags removed: verification-needed verification-needed-lunar
** Tags added: verification-done verification-done-lunar
--
You received this bug notification because you are a member of Ubuntu
** Description changed:
This morning, I upgraded gnome-shell and gnome-shell-common from
42.5-0ubuntu1 to 42.9-0ubuntu2, and I noticed that chrome no longer
renders properly. Notice the missing image header on the Ubuntu website
and the garbled right click menu here:
Public bug reported:
Hi Ubuntu Team,
MY ISSUE:
I installed today my PC with Ubuntu IOT Desktop(22.04.2 LTS (Jammy Jellyfish)).
But with updated for all packages and with reboot PC, i have error with
starting gdm and access to /dev/dri/card0.
ERROR:
iul 11 19:00:10 MY-PC gnome-session[1022]:
Public bug reported:
This morning, I upgraded gnome-shell and gnome-shell-common from
42.5-0ubuntu1 to 42.9-0ubuntu2, and I noticed that chrome no longer
renders properly. Notice the missing image header on the Ubuntu website
and the garbled right click menu here:
https://i.imgur.com/BPnqfVG.png
Might be related to https://gitlab.gnome.org/GNOME/glib/-/issues/2927
** Bug watch added: gitlab.gnome.org/GNOME/glib/-/issues #2927
https://gitlab.gnome.org/GNOME/glib/-/issues/2927
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
I will, thank you.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-terminal in Ubuntu.
https://bugs.launchpad.net/bugs/2011727
Title:
Seemingly random crashes of all terminal windows
To manage notifications about this bug go
As far as I can see, VTE did not change. However, any external
circumstance might have accidentally made it occur much less frequently.
Please get back to me if it crashes again, knowing what action triggered
the crash might be a big clue for us.
--
You received this bug notification because
Hi Egmont - While this issue occurred more often back in March, I
haven't experienced this problem recently. I'm now running Ubuntu
20.04.6 instead of 20.04.5 - Perhaps something in this upgrade solved
the issue?
--
You received this bug notification because you are a member of Ubuntu
Desktop
** Description changed:
Netplan FTBFS as of the latest release of glib2.0 (2.77.0-0ubuntu1) in
mantic-proposed.
See: https://launchpad.net/ubuntu/+source/netplan.io/0.106.1-3
When I downgrade glib in my sbuild environment, everything works as
expected:
$ apt install
The issue remains after disabling all non-default extensions. With
regards to Signal, I have noticed that enabling the setting 'Draw
attention to this window when a notification arrives' will generate an
extra notification that "Signal (1) is ready", in addition to the
message itself.
In 22.04.2,
I'm tagging this block-proposed to avoid this broken GLib to move into
mantic-release.
** Tags added: block-proposed
--
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/2026826
Title:
Public bug reported:
Netplan FTBFS as of the latest release of glib2.0 (2.77.0-0ubuntu1) in
mantic-proposed.
See: https://launchpad.net/ubuntu/+source/netplan.io/0.106.1-3
When I downgrade glib in my sbuild environment, everything works as
expected:
$ apt install libglib2.0-0=2.76.3-1ubuntu1
*** This bug is a duplicate of bug 1970291 ***
https://bugs.launchpad.net/bugs/1970291
Perhaps I over-thought that. Since you actually get some frames on
screen and they're just slow, I think the real issue is bug 1970291:
> Secondary GPU initialization failed (Failed to create gbm_surface:
I'm starting to wonder whether it's really
https://gitlab.gnome.org/GNOME/vte/-/issues/2577, or perhaps the change
done there covers up this bug (prevents a crash) but might still result
in slightly incorrect behavior (e.g. not recognizing whatever needs to
be recognized as being under the mouse),
28 matches
Mail list logo
