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. Run these commands:
journalctl -b0 > journal.txt
journalctl -b-1 > prevjournal.txt
an
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. Run these commands:
journalctl -b0 > journal.txt
journalctl -b-1 > prevjournal.txt
an
If Xwayland isn't leaving core files (which would show up as crash files
in /var/crash) then it might be inheriting Xorg's built-in crash
handler, logging the stack trace to *somewhere* and that never makes it
to the system journal.
--
You received this bug notification because you are a member o
Dropped the 'regression-update' tag because this bug really has existed
forever. The only regression-update is bug 2080498.
** Tags removed: regression-update
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to egl-wayland in Ubuntu.
https://bugs.la
This gnome-shell suicide is the only explanation I can see:
Sep 18 15:01:22 shanu-Inspiron-15-3511 gnome-shell[16721]: Connection to
xwayland lost
Sep 18 15:01:22 shanu-Inspiron-15-3511 gnome-shell[16721]: Xwayland terminated,
exiting since it was mandatory
Sep 18 15:01:22 shanu-Inspiron-15-3511
> Alessandro informs me that this was caused by some combination of kernel
> 6.8.0 and a
> nvidia-driver-550 update, so tagging regression-update, and I'll review the
> proposed fix next.
The regression-update is probably better tracked in bug 2080498.
--
You received this bug notification bec
In theory this is fix released now that Oracular has Nvidia-560. I can't
totally confirm it though, because once again Chrome has regressed to
not having any hardware acceleration enabled. But let's keep that
separate...
** Also affects: nvidia-graphics-drivers-560 (Ubuntu)
Importance: Undecid
Still happening in Oracular (bug 2080909)
** Changed in: xorg-server (Ubuntu)
Status: Fix Released => Confirmed
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1811023
Title:
Xorg
I don't see any random logouts in the attached logs. Let's treat it as a
crash anyway...
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. Run
It sounds like you're reporting multiple unrelated issues here. Please
be careful to only report one issue per bug report.
* kernel: ACPI Error: are BIOS bugs and can be safely ignored in most
cases. Also Ubuntu can't fix those.
* Random log out: Sounds like the biggest issue so let's focus on th
Thank you for reporting this bug to Ubuntu.
Ubuntu 16.04 (xenial) reached end-of-standard-support on April 29, 2021.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old and you might not be interested
in discussing it
Assuming the bug is in journal-1.txt, it looks like the nouveau kernel
graphics driver that's crashing. To solve that I suggest installing an
official Nvidia driver from the 'Additional Drivers' app.
** Package changed: xorg (Ubuntu) => linux (Ubuntu)
** Summary changed:
- Xorg freeze
+ [nouvea
** Package changed: xorg (Ubuntu) => libreoffice (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/2080806
Title:
wrong font size is displaying on editing
To manage notifications about th
Reverting to mirror mode suggests the system doesn't recognise the new
config on wakeup as being equal to the old config before sleeping.
One of your configurations in ~/.config/monitors.xml seems to contain a
disabled "unknown" monitor which likely was bug 2060268. So I suggest:
1. Make sure you
** Tags added: multimonitor nvidia
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/2080782
Title:
Problems when my computer monitors go to sleep
To manage notifications about this bug go to:
htt
Thanks. Please proceed to steps 2 and 3 in comment #2.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xwayland in Ubuntu.
https://bugs.launchpad.net/bugs/2080361
Title:
Ubuntu 24.04.1 LTS Wayland crashes
To manage notifications about this bu
Next steps:
1. Add SRU documentation (https://canonical-sru-docs.readthedocs-
hosted.com/en/latest/reference/bug-template/)
2. Subscribe ubuntu-sponsors
** Changed in: egl-wayland (Ubuntu Jammy)
Importance: Critical => High
** Changed in: egl-wayland (Ubuntu Jammy)
Status: Triaged =>
** Changed in: gnome-shell (Ubuntu)
Importance: Undecided => Medium
** Changed in: switcheroo-control (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to egl-wayland in Ubuntu.
https://bugs.launchpad.ne
** Also affects: egl-wayland (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to egl-wayland in Ubuntu.
https://bugs.launchpad.net/bugs/2080282
Title:
Apps run on the discrete Nvidia GPU by defa
*** This bug is a duplicate of bug 2062951 ***
https://bugs.launchpad.net/bugs/2062951
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 2062951, so it is being marked as such. Please look
It appears there are hidden settings internally:
org.gnome.desktop.a11y.keyboard mousekeys-accel-time 300
org.gnome.desktop.a11y.keyboard mousekeys-enable false
org.gnome.desktop.a11y.keyboard mousekeys-init-delay 300
org.gnome.desktop.a11y.keyboard mousekeys-max-speed 10
You can adjust t
** Summary changed:
- ラップトップをタブレットとして使用する際画面回転を認識しない
+ [Lenovo Yoga 7 14ARB7] Screen rotation support is intermittent
** Package changed: xorg (Ubuntu) => linux-hwe-6.8 (Ubuntu)
** Also affects: iio-sensor-proxy (Ubuntu)
Importance: Undecided
Status: New
** Also affects: gnome-shell (
Thanks Jack. Your system I expect will suffer from all of these due to
the Quadro K4200 being limited to Nvidia driver 470:
* https://gitlab.gnome.org/GNOME/mutter/-/issues/3196 (fixed in Mutter 47.rc)
* https://gitlab.gnome.org/GNOME/mutter/-/issues/3464 (fixed in Mutter 47.rc)
* Bug 206208
*** This bug is a duplicate of bug 2066353 ***
https://bugs.launchpad.net/bugs/2066353
Yes please click that link and submit the requested info in bug 2066353.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in Ubuntu.
https://bugs.laun
Nvidia users might have bug 2062082 to blame here. Please try:
sudo apt install libnvidia-egl-wayland1
and reboot. So maybe it's really two issues:
* Nvidia is using Zink when it shouldn't (bug 2062082)
* For non-Nvidia systems that might need Zink, it doesn't work (bug 2066353)
--
You r
Thanks for the bug report. It looks like the machine is missing an
Nvidia kernel driver (and failed to use the open source driver). Please
try installing a new driver through the 'Additional Drivers' app. I
expect only Nvidia driver 470 supports the GT 730.
After rebooting, if that hasn't fixed th
** Summary changed:
- Wrong screen resolution
+ Wrong screen resolution (missing nvidia kernel module)
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/2080266
Title:
Wrong screen resolution (mis
Everyone affected; please run:
lspci -k > lspci.txt
dpkg -l > packages.txt
and attach the resulting text files here.
Also if anyone has the skills to test patches then please try:
https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/30479.patch
(from bug 2075549 which I think Marco
See also bug 2066353.
** Tags added: zink
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/2075549
Title:
Running gtk applications in compositor supporting only shared memory
buffers does not w
> wondering why Ubuntu never noticed this during the beta phase??
The answer appears to be at the top of the page ("This bug affects 6
people"). So not many people (and apparently zero developers) have
encountered the bug.
** Tags added: jammy noble
** Tags removed: jammy
--
You received this
*** This bug is a duplicate of bug 2066353 ***
https://bugs.launchpad.net/bugs/2066353
Great, that's a workaround. The main issue here (at least what looks
like the main issue) is already being tracked in bug 2066353.
** Package changed: gdm3 (Ubuntu) => mesa (Ubuntu)
** Summary changed:
-
** Package changed: xorg (Ubuntu) => thunar (Ubuntu)
** Summary changed:
- Xfce interface display problem
+ [fbdev] Xfce interface display problem
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/2
I don't think BlueZ is involved here. It's the libinput Xorg driver
that's claiming anything with buttons as a keyboard. Although this may
need to be patched as a udev rule in udev, systemd, or somewhere else.
So shipping the rule in 'bluez' may still make sense.
** Also affects: xserver-xorg-inpu
Thanks for the bug report. While the problem is happening, please open a
virtual terminal (Ctrl+Alt+F4) and run:
journalctl -b0 > journal.txt
and attach the resulting text file here.
** Package changed: xorg (Ubuntu) => ubuntu
** Changed in: ubuntu
Status: New => Incomplete
--
You r
Also reported in:
https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/7508
https://gitlab.gnome.org/GNOME/mutter/-/issues/3477
https://gitlab.gnome.org/GNOME/mutter/-/issues/3340
** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/-/issues #7508
https://gitlab.gnome.org/GNOME/gnome-shell/-/i
Thanks for the bug report.
Please try removing all local extensions:
cd ~/.local/share/gnome-shell
rm -rf extensions
and then log in again. Does the bug still occur?
** Tags added: focus
** Package changed: xorg (Ubuntu) => mutter (Ubuntu)
** Changed in: mutter (Ubuntu)
Status: New
It looks like the image viewer app has leaked override redirect windows.
Although that suggests to me it's still running?
If you run 'xwininfo -all' and then click on the artifacts, does it
reveal where they come from?
** Package changed: xorg (Ubuntu) => gnome-shell (Ubuntu)
** Changed in: gnom
Thanks for the bug report. It appears this USB device is the wireless
receiver for the mouse:
Bus 001 Device 007: ID 3151:3020 YICHIP Wireless Device
and some googling is telling me that other people have connection
problems with the same device.
Since the wireless part of this setup is done e
Thanks for the bug report. That kernel looks old and should have been
updated by now. Please try:
sudo apt install linux-generic-hwe-22.04
and reboot.
** Package changed: xorg (Ubuntu) => linux-hwe-6.2 (Ubuntu)
** Changed in: linux-hwe-6.2 (Ubuntu)
Status: New => Incomplete
--
You r
Thanks for the bug report. That kernel looks old and should have been
updated by now. Please try:
sudo apt install linux-generic-hwe-22.04
and reboot.
** Summary changed:
- I cannot change or control display brightness
+ [Lenovo LOQ 15ARP9] I cannot change or control backlight brightness
**
Thanks for the bug report. First we should check to see if the problem
is specific to GNOME/Xorg or coming from the kernel. You can do this by
pressing Ctrl+Alt+F4 and logging into a virtual terminal. Does the bug
still occur there?
To return to GNOME, press Alt+F2.
** Package changed: xorg (Ubun
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. Run these commands:
journalctl -b0 > journal.txt
journalctl -b-1 > prevjournal.txt
an
** Tags added: jammy
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1969995
Title:
xserver-xorg is set to depend on python3-apport making it impossible
to uninstall
To manage notificat
*** This bug is a duplicate of bug 2063827 ***
https://bugs.launchpad.net/bugs/2063827
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 2063827, so it is being marked as such. Please look
Looks like it's still a common issue:
https://errors.ubuntu.com/?package=systemd&period=week
but we'd need the crash ID or the machine's whoopsie ID to tell which
instance this is.
** Package changed: xorg (Ubuntu) => systemd (Ubuntu)
** Changed in: systemd (Ubuntu)
Status: New => Inco
Please explain in more detail what kind of problem you are experiencing.
** Package changed: xorg (Ubuntu) => ubuntu
** Changed in: ubuntu
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https://
Thanks for the bug report. I can see two main problems here:
1. The amdgpu kernel graphics driver is emitting warnings that look like
crashes.
2. The rtw_8821ce kernel wifi driver is flooding the system log (this is
probably the performance issue).
So I can only suggest trying an older Ubuntu r
*** This bug is a duplicate of bug 2049578 ***
https://bugs.launchpad.net/bugs/2049578
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 2049578, so it is being marked as such. Please look
It looks like you triggered the screen magnifier. Try holding the
Windows key and pressing +/- or =/-
Please also run this command to collect more system information:
apport-collect 2077825
** Package changed: xorg (Ubuntu) => plasma-desktop (Ubuntu)
** Changed in: plasma-desktop (Ubuntu)
Thanks for the bug report. It looks like mutter-x11-frames is
segfaulting repeatedly. That's probably not helping. Let's treat this as
a crash and see what else might be crashing. Please follow these steps:
1. Run these commands:
journalctl -b0 > journal.txt
journalctl -b-1 > prevjournal.t
** Package changed: xorg (Ubuntu) => linux-hwe-6.8 (Ubuntu)
** Package changed: linux-hwe-6.8 (Ubuntu) => linux (Ubuntu)
** Also affects: mutter (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed t
Unfortunately all forms of smooth scrolling are toolkit or app-specific.
So we will make this one about Firefox.
** Package changed: xorg (Ubuntu) => firefox (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https://bugs.l
*** This bug is a duplicate of bug 1861609 ***
https://bugs.launchpad.net/bugs/1861609
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 1861609, so it is being marked as such. Please look
Nvidia driver 555 is not supported by Ubuntu for now:
https://launchpad.net/ubuntu/+source/nvidia-graphics-drivers-555
But it sounds like you have hit bug 1975650, so if the driver is from a
PPA then you can try something like:
sudo apt install linux-modules-nvidia-555-`uname -r`
** Package
** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/2077612
Title:
Slow X11 performance through ssh
To manage notifications about thi
** Changed in: mutter (Ubuntu)
Status: Incomplete => New
** Changed in: nvidia-graphics-drivers-535 (Ubuntu)
Status: Incomplete => New
** Changed in: xorg-server (Ubuntu)
Status: Incomplete => New
** Summary changed:
- XIO: fatal IO error is killing gnome-shell (black scree
Sorry I just remembered the Nvidia 550 driver will be hidden from the
GUI on most systems.
This should get you most of the way:
sudo apt purge nvidia-driver-535
sudo apt install nvidia-driver-550 linux-modules-nvidia-550-generic
libnvidia-egl-wayland1
--
You received this bug notification
Based on the description I think this is most likely to be bug 2037055.
But to be sure, please follow these steps:
1. Run these commands:
journalctl -b0 > journal.txt
journalctl -b-1 > prevjournal.txt
and attach the resulting text files here.
2. Look in /var/crash for crash files and if f
As a workaround, please try adding this to /etc/environment:
MUTTER_DEBUG_FORCE_KMS_MODE=simple
and reboot.
** Tags added: i915 psr regression-update
** Package changed: xorg (Ubuntu) => linux-hwe-6.8 (Ubuntu)
** Changed in: linux-hwe-6.8 (Ubuntu)
Importance: Undecided => Medium
** Summa
*** This bug is a duplicate of bug 2062951 ***
https://bugs.launchpad.net/bugs/2062951
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 2062951, so it is being marked as such. Please look
For most people, having too many browser tabs or virtual machines open
will be the trigger for this. But we should also discuss the correctness
of killing the shell via systemd-oomd.
** Package changed: xorg (Ubuntu) => systemd (Ubuntu)
** Summary changed:
- GUI crashes and returns back to login
Thanks for the bug report. Please try this for a little while to see if
the bug goes away:
gnome-extensions disable ubuntu-d...@ubuntu.com
** Package changed: xorg (Ubuntu) => gnome-shell-extension-ubuntu-dock
(Ubuntu)
** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu)
Status: Ne
Thanks. Looks like there's a similar crash:
août 17 23:41:22 Aspire-E5-575G org.gnome.Shell.desktop[1570]: XIO: fatal IO
error 11 (Ressource temporairement non disponible) on X server ":0"
août 17 23:41:22 Aspire-E5-575G org.gnome.Shell.desktop[1570]: after 4519
requests (4519 known proce
Yes there are lots of kernel warnings from the nvidia driver. I can't
tell if they're fatal but they're certainly the only problem I can see
right now.
In case your main "crash" has a different cause, please follow these
steps:
1. Run these commands:
journalctl -b0 > journal.txt
journalct
Thanks for the bug report.
We will need to see a boot log that's not in recovery mode. Please
reproduce the bug again, then reboot into recovery mode and run:
journalctl -b-1 > prevboot.txt
And attach the resulting text file here.
** Package changed: xorg (Ubuntu) => ubuntu
** Changed in: u
** Package changed: xorg (Ubuntu) => kwin (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/2076495
Title:
Display Configuration is not remembered with external monitor setup
To manage no
Please describe what kind of problem you are experiencing.
** Package changed: xorg (Ubuntu) => ubuntu
** Changed in: ubuntu
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https://bugs.launchpa
Please tell us what kind of problem you are encountering.
** Package changed: xorg (Ubuntu) => ubuntu
** Changed in: ubuntu
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https://bugs.launchpad
Please tell us what kind of problem you are encountering.
** Package changed: xorg (Ubuntu) => ubuntu
** Changed in: ubuntu
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.
Thanks for the bug report.
Most intermittent black screen flickers are caused by a loss of display
signal integrity. It's especially common at high resolutions or refresh
rates (I notice you're using 4K). That can usually be fixed by replacing
the display cable and/or taking the dock out of the eq
Judging by the bug reports, this seems to have stopped happening in
24.04 and later(?)
** Changed in: linux (Ubuntu)
Status: Confirmed => Incomplete
** Changed in: mutter (Ubuntu)
Status: Triaged => Incomplete
** Changed in: xorg-server (Ubuntu)
Status: Confirmed => Incomple
*** This bug is a duplicate of bug 1997550 ***
https://bugs.launchpad.net/bugs/1997550
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 1997550, so it is being marked as such. Please look
Thanks for the bug report. If you can then please try a USB-C monitor
cable, you should be able to find one that is HDMI on the other end.
That will allow you to avoid running the signal through the Nvidia card
and should provide a better experience.
Please also try selecting 'Ubuntu on Wayland' f
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. Run these commands:
journalctl -b0 > journal.txt
journalctl -b-1 > prevjournal.txt
an
Thanks for the bug report. Next time the problem happens, immediately
after rebooting run:
journalctl -b-1 > prevboot.txt
and attach the resulting text file here.
** Tags added: multimonitor
** Package changed: wayland (Ubuntu) => mutter (Ubuntu)
** Changed in: mutter (Ubuntu)
Status:
*** This bug is a duplicate of bug 1876632 ***
https://bugs.launchpad.net/bugs/1876632
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 1876632, so it is being marked as such. Please look
Thanks for the bug report. Please try adding this to /etc/environment:
MUTTER_DEBUG_FORCE_KMS_MODE=simple
and then reboot.
** Summary changed:
- Top margin of secondary monitor covered with black flickering rectangle
+ [nouveau] Top margin of secondary monitor covered with black flickering
r
*** This bug is a duplicate of bug 2062951 ***
https://bugs.launchpad.net/bugs/2062951
Please try adding kernel parameter:
i915.enable_psr=0
** Package changed: xorg (Ubuntu) => linux (Ubuntu)
** Changed in: linux (Ubuntu)
Status: New => Incomplete
--
You received this bug notifi
Thanks for the bug report. Please attach a video or photo of the
problem. You can create either by pressing PrtScn.
** Tags added: nouveau
** Package changed: xorg (Ubuntu) => ubuntu
** Summary changed:
- smash the window
+ [nouveau] menu turns on and off at a very high speed
** Changed in: ub
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. Run these commands:
journalctl -b0 > journal.txt
journalctl -b-1 > prevjournal.txt
an
Thanks for the bug report.
This looks similar to Nvidia bug 2061079 so please try adding
GSK_RENDERER=gl to /etc/environment and reboot.
** Tags added: nouveau
** Summary changed:
- Crashing System
+ Graphics corruption in Nautilus
** Package changed: xorg (Ubuntu) => ubuntu
** Changed in: ub
** Package changed: xorg (Ubuntu) => linux (Ubuntu)
** Also affects: gnome-settings-daemon (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/20740
Are we sure this can't just be grouped in with bug 2061118?
Bug 2063923 for example is not VMware but shows a video with the same
looking artifacts as bug 2061118.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in Ubuntu.
https://bugs.laun
Here's the fix for Oracular.
** Changed in: mesa (Ubuntu)
Status: Confirmed => Won't Fix
** Patch added: "webkit2gtk_2.44.0-2ubuntu1.debdiff"
https://bugs.launchpad.net/ubuntu/+source/webkit2gtk/+bug/2037015/+attachment/5772919/+files/webkit2gtk_2.44.0-2ubuntu1.debdiff
--
You receive
** Changed in: mesa (Ubuntu)
Status: Triaged => Won't Fix
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/2062146
Title:
Raspberry Pi: webkit2gtk apps crash with SIGSEGV in v3d_load_utile
I wonder if this is due to bug 2060268...
** Package changed: xorg (Ubuntu) => gnome-control-center (Ubuntu)
** Also affects: nvidia-graphics-drivers-470 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu-X,
which is sub
*** This bug is a duplicate of bug 2063970 ***
https://bugs.launchpad.net/bugs/2063970
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 2063970, so it is being marked as such. Please look
When the problem is happening please run:
gsettings list-recursively | grep keybindings > keybindings.txt
and attach the resulting text file here.
** Package changed: xorg (Ubuntu) => gnome-shell (Ubuntu)
** Changed in: gnome-shell (Ubuntu)
Status: New => Incomplete
--
You received t
Please try adding kernel parameter:
i915.enable_psr=0
** Package changed: xorg (Ubuntu) => linux (Ubuntu)
** Changed in: linux (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https://
The crash (bug 2062146) is now awkwardly entangled with this bug. It
occurs at the same time as, or usually instead of corruption. Bisected
in Mesa:
https://gitlab.freedesktop.org/mesa/mesa/-/issues/11033#note_2385595
Prior to that regression, I still believe the corruption probably
started aro
** No longer affects: yelp (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/2062146
Title:
Raspberry Pi: webkit2gtk apps crash with SIGSEGV in v3d_load_utile
To manage notifications abou
Also tracking in https://gitlab.freedesktop.org/mesa/mesa/-/issues/11008
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/2061118
Title:
Rendering issues in virtual machines (GTK ngl backend)
To
Bug 2061079 being so similar makes me think long term we will find that
GTK4 is doing something wrong. We just don't know what it's doing wrong
yet.
** Changed in: gtk4 (Ubuntu Noble)
Status: Invalid => Confirmed
** Bug watch added: gitlab.freedesktop.org/mesa/mesa/-/issues #11008
http
Users of the Nvidia 470 driver please see bug 2061079.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/2061118
Title:
Rendering issues in virtual machines (GTK ngl backend)
To manage notificatio
Generalised to cover non-VMware (bug 2063923).
** Summary changed:
- Rendering issues in vmware with 3d on (GTK ngl backend)
+ Rendering issues in virtual machines (GTK ngl backend)
** Tags added: noble vmwgfx
--
You received this bug notification because you are a member of Ubuntu-X,
which is
*** This bug is a duplicate of bug 2061118 ***
https://bugs.launchpad.net/bugs/2061118
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 2061118, so it is being marked as such. Please look
** Summary changed:
- Sometimes gnome-shell crash upon unlocking session from suspension
+ gnome-shell crashed with assertion failure
"meta_monitor_manager_get_logical_monitor_from_number: assertion '(unsigned
int) number < g_list_length (manager->l>"
** No longer affects: xwayland (Ubuntu)
**
** Package changed: xorg (Ubuntu) => mutter (Ubuntu)
** Tags added: focus
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/2063831
Title:
Clicking on bottom half of applications switches to backg
I can see 'gjs' crashing constantly so please try:
gnome-extensions disable d...@rastersoft.com
If that doesn't fix it then please provide a video of the problem.
** Package changed: xorg (Ubuntu) => ubuntu
** Changed in: ubuntu
Status: New => Incomplete
--
You received this bug noti
It looks like the kernel ran out of memory and the main culprit is a
'java' process. This is not an Ubuntu bug.
** Package changed: xorg (Ubuntu) => ubuntu
** Changed in: ubuntu
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu-X,
which is su
1 - 100 of 1011 matches
Mail list logo
