Thanks for the bug report.
While the flickering is happening please run:
journalctl -b0 > journalwithflicker.txt
and attach the resulting text file here.
Next please try selecting 'Ubuntu on Xorg' on the login screen, login
and run:
journalctl -b0 > journalwithxorg.txt
xrandr --verbose
1) Safe mode is expected to fail because it disables graphics drivers.
2) Live session all working fine.
3) Graphics working but not able to start a terminal.
So the only problem here is the last one where you couldn't start a
terminal. Did you try Ctrl+Alt+T ? Did the shell respond to mouse
We can't read crash files. You need to use the 'ubuntu-bug' or 'apport-
cli' tools to upload crash files.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1975566
Title:
The attachment in comment #16 shows Vulkan is now working, but only with
software rendering(?) so that's going to be slow...
Please run these again:
lspci -k > lspci.txt
journalctl -b0 > journal.txt
glxinfo > glxinfo.txt
and attach the resulting text files here.
--
You received this bug
Oh I see you started with Ubuntu Server.
Please:
1. Don't disable Wayland. Wayland should be enabled.
2. Answer the previous question: After you have switched back to a
'stock' config and kernel, what does vulkaninfo report?
3. Try booting desktop Ubuntu from USB:
Before the upgrade it was an Intel GPU.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1975566
Title:
radeon / amdgpu bad performance or panics
Status in mesa package in
*** This bug is a duplicate of bug 1924251 ***
https://bugs.launchpad.net/bugs/1924251
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 1924251, so it is being marked as such. Please
Thanks for the bug report. It appears your Nvidia kernel driver is not
loading anymore so low resolution is expected. This may have been caused
by a recent kernel update. Please try this:
sudo apt install --reinstall nvidia-driver-510/jammy
sudo apt install --reinstall nvidia-dkms-510/jammy
I don't know much about AMD GPUs but from what I've seen there is
usually only one kernel graphics driver that works for a given GPU.
After you have switched back to a 'stock' config and kernel, what does
vulkaninfo report? Does the "bad performance" persist?
--
You received this bug
The difference between 21.10 and 22.04 might just be that we now default
to Wayland instead of Xorg. So the display subsystems are different.
Please run this command to gather more information:
apport-collect 1975557
And to save time in future please use the 'ubuntu-bug' command to report
new
Pipewire isn't involved in putting pixels on the screen.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1969959
Title:
[nouveau] Weird colors after startup (Ubuntu 22.04)
** Summary changed:
- screen flashes on-off unless PSR is turned off
+ [Star Labs Lite IV] screen flashes on-off unless PSR is turned off
** Package changed: xorg (Ubuntu) => linux (Ubuntu)
** Tags added: psr
--
You received this bug notification because you are a member of Ubuntu
Touch
OK so multiple problems there, which may have the same root cause:
* Your shell/compositor seems to be causing stalling.
* vulkaninfo says your GPU is "not using the AMDGPU kernel driver:
Invalid argument (VK_ERROR_INCOMPATIBLE_DRIVER)"
Sounds fundamentally like the kernel graphics driver isn't
The errors in comment #2 are kernel bugs so please also try the official
Ubuntu kernel (5.15) instead.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1975566
Title:
radeon /
Thanks for the bug report. Please run:
sudo apt install mesa-utils vulkan-tools
glxinfo > glxinfo.txt
vulkaninfo > vulkaninfo.txt
and attach the resulting text files here.
** Package changed: xorg (Ubuntu) => mesa (Ubuntu)
** Changed in: mesa (Ubuntu)
Status: New => Incomplete
** Tags added: jammy
** Package changed: xorg (Ubuntu) => linux (Ubuntu)
** Also affects: linux-firmware (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
Thanks for the bug report.
You seem to have gotten your graphics packages from the 'oibaf' PPA.
That is known to be frequently broken and is UNSUPPORTED.
** Package changed: xorg (Ubuntu) => ubuntu
** Changed in: ubuntu
Status: New => Invalid
--
You received this bug notification
Thanks for the bug report.
Firstly, you are using the (low quality) open source 'nouveau' graphics
driver. It is known to cause such problems so please start by using the
'Additional Drivers' app to install an official Nvidia driver.
After installing the driver and rebooting, if the problem
Thanks for the bug report. Next time the problem happens, after
rebooting run:
journalctl -b-1 > prevboot.txt
and attach the resulting text file here.
** Tags added: nvidia
** Package changed: xorg (Ubuntu) => ubuntu
** Changed in: ubuntu
Status: New => Incomplete
--
You received
Thanks for the bug report. I am guessing this is caused by the kernel
graphics driver. Please run:
grep . /sys/class/drm/*/modes > modes.txt
and attach the resulting text file here.
** Package changed: xorg (Ubuntu) => linux (Ubuntu)
** Changed in: linux (Ubuntu)
Status: New =>
*** This bug is a duplicate of bug 1947185 ***
https://bugs.launchpad.net/bugs/1947185
Thanks for the bug report. It appears 'conky' is an X11 app but you are
using Wayland. Wayland sessions do not support the 'dock' X11 window
type. You will either need a version of conky that supports
*** This bug is a duplicate of bug 1972151 ***
https://bugs.launchpad.net/bugs/1972151
Sounds like bug 1972151.
** Package changed: xorg (Ubuntu) => mutter (Ubuntu)
** This bug has been marked a duplicate of bug 1972151
App window starts overlapping two (vertical) monitors (under the
** Package changed: gtk4 (Ubuntu) => gtk+3.0 (Ubuntu)
** Changed in: gtk+3.0 (Ubuntu)
Importance: Undecided => Low
** Changed in: gtk+3.0 (Ubuntu)
Status: New => Triaged
** No longer affects: gtk+3.0 (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Thanks for the bug report. It sounds like "acpi_backlight=vendor
acpi_osi=linux" is the main issue here but I can't tell if adding it was
the fix, or removing it was the fix. Which was it?
** Tags added: amdgpu nouveau
** Tags added: hybrid
** Summary changed:
- After updating to Ubuntu 22.04
** Package changed: xorg (Ubuntu) => mutter (Ubuntu)
** Changed in: mutter (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1973467
Please explain in more detail what the problem is 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
Touch seeded packages, which is subscribed to xorg
** Summary changed:
- vram memory leak under Wayland
+ [nvidia] vram memory leak under Wayland
** Package changed: xorg (Ubuntu) => mutter (Ubuntu)
** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #2173
https://gitlab.gnome.org/GNOME/mutter/-/issues/2173
** Also affects: mutter
** Summary changed:
- dmesg
+ UBSAN: invalid-load in
/build/linux-WD899k/linux-5.15.0/net/mac80211/status.c:1164:21
** Package changed: xorg (Ubuntu) => linux (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg
I'm not sure we even need switch-on-connect anymore. It was introduced
as a patch in 2017 (bug 1702794) at the request of Will Cooke but I
suspect later upstream changes within the module logic like module-
switch-on-port-available might suffice now.
--
You received this bug notification because
Please also tell us what hypervisor you are using.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1973732
Title:
[vmwgfx] Artifacts in PHPSTORM, Browser, All applications.
Thanks for the bug report. Are you able to provide a photo or video of
the problem?
** Tags added: vmwgfx
** Summary changed:
- Artifacts in PHPSTORM, Browser, All applications. Lags, freeze.
+ [vmwgfx] Artifacts in PHPSTORM, Browser, All applications. Lags, freeze.
** Package changed:
** Also affects: bluez (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1973610
Title:
Bluetooth will not stay on or
For the USB dongle there are kernel messages:
[ 34.065571] Bluetooth: hci0: BCM: firmware Patch file not found, tried:
[ 34.065744] Bluetooth: hci0: BCM: 'brcm/BCM20702A1-0a5c-21e8.hcd'
[ 34.065757] Bluetooth: hci0: BCM: 'brcm/BCM-0a5c-21e8.hcd'
** Package changed: bluez (Ubuntu) => linux
We haven't had any bug reports like this that weren't hardware-specific.
Maybe to avoid confusion here we should choose just one Bluetooth chip.
Either the USB dongle (Broadcom Corp. BCM20702A0) or the internal chip
(Intel AX210/AX211/AX411).
--
You received this bug notification because you are
Does the same bug occur if you choose a Xorg session (or just non-
Wayland) on the login screen?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1973467
Title:
[nvidia]
** Summary changed:
- Screen Blank: External screen is not turned off
+ [nvidia] Screen Blank: External screen is not turned off
** Tags added: nvidia nvidia-wayland wayland
** Tags added: hybrid multimonitor
--
You received this bug notification because you are a member of Ubuntu
Touch
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
Thanks for the bug report.
This sounds like a hardware problem, most likely just new batteries are
required.
Wired mice or wireless with a dongle use the same code paths so clearly
that's working for some mice. I don't think there's any software bug
here.
** Package changed: xorg (Ubuntu) =>
If you are using a USB-C dock then please see bug 1970495.
Otherwise if you think the USB-C port might be wired directly to the
Nvidia GPU then please see bug 1960865.
When the bug occurs next please:
1. Wait 10 seconds.
2. Reboot.
3. Run:
journalctl -b-1 > prevboot.txt
4. Attach the
Also which monitor is displaying the wrong resolution?
** Summary changed:
- monitor resolution issue
+ Wayland session limited to 1024x768
** Package changed: xorg (Ubuntu) => linux (Ubuntu)
** Also affects: mutter (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux
Please try selecting 'Ubuntu on Xorg' on the login screen.
** Tags added: hybrid i915 radeon
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1973143
Title:
[impish] Wayland
** Tags removed: artful wily yakkety zesty
** Tags added: jammy
** Changed in: bluez (Ubuntu)
Status: Fix Released => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
** Tags removed: artful wily yakkety zesty
** Tags added: jammy
** Changed in: bluez (Ubuntu)
Status: Fix Released => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
** Summary changed:
-
/usr/bin/gnome-shell:11:crocus_begin_query:crocus_begin_query:crocus_end_query:crocus_end_query:tc_call_end_query
+ gnome-shell crashed with SIGSEGV in crocus_begin_query() from
crocus_begin_query() from crocus_end_query() from crocus_end_query() from
tc_call_end_query()
Yes it sounds like the cause was the PPA:
https://launchpad.net/~berglh/+archive/ubuntu/pulseaudio-a2dp
pulseaudio-module-bluetooth is in fact installed by default in jammy and
in focal.
** Summary changed:
- Can pair but cannot connect to bluetooth headphones Sennheiser Momentum 3
+
> Looks like with the latest update the problem is solved.
What packages got updated? Certainly not gnome-shell, mutter or mesa.
** No longer affects: mutter (Ubuntu)
** No longer affects: gnome-shell (Ubuntu)
** No longer affects: mesa (Ubuntu)
** Changed in: linux (Ubuntu)
Status:
I'm surprised that:
(a) Xwayland is needed on startup. It shouldn't be started in a Wayland
session until a legacy app is launched.
(b) g_error ("Failed to start X Wayland: %s", error->message); is
fatal. It shouldn't be fatal because of (a), but indeed it apparently
still is in the latest
Thanks for the bug report. While the problem is happening please run:
gsettings list-recursively org.gnome.shell > settings.txt
journalctl -b0 > journal.txt
and attach the resulting text files here.
** Package changed: xorg (Ubuntu) => firefox (Ubuntu)
** Changed in: firefox (Ubuntu)
Thanks for the bug report. Next time the bug happens please run:
journalctl -b0 > journal.txt
and attach the resulting text file here.
Please also try selecting 'Ubuntu on Xorg' at the login screen and tell
us if it has the same problem.
** Package changed: xorg (Ubuntu) => mutter (Ubuntu)
Thanks for the bug report. Next time the problem happens please:
1. Wait 10 seconds.
2. Shutdown/reboot.
3. Run:
journalctl -b-1 > prevboot.txt
4. Attach the resulting text file here.
** No longer affects: wayland (Ubuntu)
** Tags added: resume suspend-resume
--
You received this bug
Thanks for the bug report.
Please:
1. Check for crashes using
https://wiki.ubuntu.com/Bugs/Responses#Missing_a_crash_report_or_having_a_.crash_attachment
2. Try adding kernel parameters 'i915.enable_dc=0
intel_idle.max_cstate=2' in case this is related to bug 1958191.
3. Attach a video showing
Indeed those modules are not installed in vanilla Ubuntu. We don't use
PipeWire for audio or Bluetooth, although Kubuntu/Xubuntu might.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
Thanks for the bug report. Please explain in more detail what messages
or errors you are seeing.
** Package changed: xorg (Ubuntu) => ubuntu
** Changed in: ubuntu
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages,
** Summary changed:
- gnome-extensions-app fails to start (Protocol error)
+ gnome-extensions-app fails to start [Error reading events from display:
Protocol error]
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in
** Summary changed:
- [vmwgfx] Screen and mouse doesn't work in VirtualBox when paravirtualization
is enabled
+ [vmwgfx] Desktop wallpaper is clipped to a rectangle and mouse doesn't work
in VirtualBox when paravirtualization is enabled
** Also affects: gnome-shell (Ubuntu)
Importance:
** Description changed:
+ [Workaround/Fix]
+
+ 1. When starting the Ubuntu live image, select the option 'Ubuntu (safe
+ graphics)' from the boot menu.
+
+ 2. During installation be sure to check the third-party software option
+ in order to get the right Nvidia driver installed.
+
+ [Original
** Changed in: bluez (Ubuntu)
Status: New => Incomplete
** Changed in: linux (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
Can you identify other common factors among the non-working and working distros?
- Kernel version
- BlueZ version
- Intermediate software like gnome-bluetooth
- Bluetooth firmware version reported in the kernel log, currently:
intel/ibt-hw-37.8.10-fw-1.10.3.11.e.bseq
--
You received this
*** This bug is a duplicate of bug 1968875 ***
https://bugs.launchpad.net/bugs/1968875
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 1968875, so it is being marked as such. Please
Thanks for the bug report. Next time a freeze happens please:
1. Wait 10 seconds.
2. Reboot.
3. Run:
journalctl -b-1 > prevboot.txt
4. Attach the resulting text file here.
5. Also check for crashes by following
** Summary changed:
- root pass on discover sofware source error
+ root pass on KDE discover software source error
** Package changed: xorg (Ubuntu) => ubuntu
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
** Package changed: bluez (Ubuntu) => ubuntu
** Changed in: ubuntu
Status: Incomplete => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1969874
Title:
Great. Next would be to try 5.14/ and 5.13.9/ (because it is halfway
between 5.13 and 5.14)
** No longer affects: mesa (Ubuntu)
** Tags added: regression-release
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in
Yes it seems to be specific to 'radeon' which is both a kernel driver
and a Mesa driver.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1971146
Title:
[radeon] Pictures
Not solved then. Recovery mode is a workaround but not a fix.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1971146
Title:
[radeon] Pictures including wallpaper not showing
Great to hear.
Additional logs certainly won't help if it's working now. But if you
have the patience then finding out what version number exactly fixed it
would help. Or what kernel version was the last to have the bug, keeping
in mind the broken kernel was (roughly) upstream version 5.15.30
**
Presumably Ubuntu worked before the upgrade. Please try booting some
older/newer kernels to see which if any are free from the bug:
https://kernel.ubuntu.com/~kernel-ppa/mainline/?C=M;O=D
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
Can you provide a photo of the problem?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1971146
Title:
[radeon] Pictures including wallpaper not showing
Status in linux
Thanks for the bug report. Next time a freeze happens please:
1. Wait 10 seconds.
2. Reboot.
3. Run:
journalctl -b-1 > prevboot.txt
4. Attach the resulting text file here.
5. Also check for crashes by following
Thanks for the bug report. Next time a freeze happens please:
1. Wait 10 seconds.
2. Reboot.
3. Run:
journalctl -b-1 > prevboot.txt
4. Attach the resulting text file here.
5. Also check for crashes by following
** Package changed: xserver-xorg-video-ati (Ubuntu) => linux (Ubuntu)
** Also affects: mutter (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu)
Status: Incomplete => New
** Changed in: mesa (Ubuntu)
Status: Incomplete => New
--
You received this
** Tags added: gamma
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to colord in Ubuntu.
https://bugs.launchpad.net/bugs/938751
Title:
Images are washed out or colors are skewed in some apps (particularly
Image Viewer and
This sounds like bug 1970031. Please try:
Settings > Colour > YOUR MONITOR = OFF
** Package changed: xorg (Ubuntu) => ubuntu
** Changed in: ubuntu
Status: New => Incomplete
** Tags added: gamma
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
Thanks for the bug report.
The kernel log in CurrentDmesg.txt suggests the i915 graphics driver is
having trouble resuming from sleep. We would like to see the whole log
so please run this command after resuming:
journalctl -b0 > journal.txt
and attach the resulting text file here.
**
Maybe related: bug 1953507
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1971146
Title:
[radeon] Pictures including wallpaper not showing
Status in mesa package in Ubuntu:
Thanks for the bug report.
Please try selecting 'Ubuntu' on the login screen instead of 'Ubuntu on
Xorg'. That way you can try a Wayland session instead.
** Summary changed:
- Pictures including wallpaper not showing
+ [radeon] Pictures including wallpaper not showing
** Tags added: radeon
**
Please also check the other VTs: Ctrl+Alt+Fn
just to see if the login really worked but is starting on the wrong VT.
** Package changed: xorg (Ubuntu) => mutter (Ubuntu)
** Changed in: mutter (Ubuntu)
Status: New => Incomplete
** Also affects: xorg-server (Ubuntu)
Importance:
Thanks for the bug report.
After you log in (any way possible) please run:
journalctl -b0 > journal.txt
and then attach the resulting text file here.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
Indeed there seem to be some error messages coming out of Mesa (about
vmwgfx) when the login screen uses Wayland. That probably puts the bug
in either Mesa or the kernel.
** Also affects: mesa (Ubuntu)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu)
Importance:
For future reference, launchpad.net is the only officially recognised
location for tracking Ubuntu bugs.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1969959
Title:
** Summary changed:
-
/usr/bin/gnome-shell:11:v3d_job_submit:v3d_flush:v3d_pipe_flush:st_flush:st_glFlush
+ gnome-shell crashed with SIGSEGV in v3d_job_submit
** Tags added: arm64 raspi raspi-gfx
** Also affects: mesa (Ubuntu)
Importance: Undecided
Status: New
** Tags added: v3d
**
Those errors are from Google Chrome (or Chromium) browser.
** Package changed: xorg (Ubuntu) => chromium-browser (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
Thanks for the bug report.
Can you provide a video of the problem?
Does it look like bug 1970426 or bug 1970869?
** Summary changed:
- Xorg freeze
+ Screen blinking sometimes and the screen is shaking
** Package changed: xorg (Ubuntu) => ubuntu
** Changed in: ubuntu
Status: New =>
Thanks for the bug report.
Is it just Wayland sessions affected? Have you tried selecting 'Ubuntu
on Xorg' at the login screen?
** Summary changed:
- Screen and mouse doesn't work
+ [vmwgfx] Screen and mouse doesn't work in VirtualBox
** Package changed: xorg (Ubuntu) => ubuntu
** Changed in:
Thanks for the bug report.
Please open a Terminal window and type:
gnome-control-center
Now what do you see?
** Package changed: xorg (Ubuntu) => gnome-control-center (Ubuntu)
** Changed in: gnome-control-center (Ubuntu)
Status: New => Incomplete
--
You received this bug
*** This bug is a duplicate of bug 1969140 ***
https://bugs.launchpad.net/bugs/1969140
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 1969140, so it is being marked as such. Please
Thanks for the bug report. Please attach a video of the problem so we
can better understand what kind of flickering this is.
See also bug 1970426.
** Package changed: xorg (Ubuntu) => linux (Ubuntu)
** Changed in: linux (Ubuntu)
Status: New => Incomplete
--
You received this bug
Yes we know. This bug became a single-GPU bug in comment #22.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1969959
Title:
[nouveau] Weird colors after startup (Ubuntu
We will need to see a log of the kernel panic. Next time it happens
please:
1. Wait 10 seconds.
2. Reboot/power off any way you can.
3. Run:
journalctl -b-1 > prevboot.txt
4. Attach the resulting text file here.
** Package changed: xorg (Ubuntu) => linux (Ubuntu)
** Also affects:
** Description changed:
+ https://errors.ubuntu.com/problem/44bd0ca893055a3c496a03038023a8d0d4860802
+
+ ---
+
Description: Ubuntu Jammy Jellyfish (development branch)
Release: 22.04
xdg-desktop-portal-gnome:
- Instalado: 42.0.1-1
- Candidato: 42.0.1-1
- Tabela de versão:
-
** Package changed: xorg (Ubuntu) => gnome-shell (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1970800
Title:
Clicking a calendar date in the bottom row of the
This might turn out to be related to bug 1965882.
** Changed in: linux (Ubuntu)
Importance: Undecided => High
** Changed in: mesa (Ubuntu)
Importance: Undecided => High
** Tags added: regression-release rls-jj-incoming
--
You received this bug notification because you are a member of
I completely agree, it's a bad user experience.
The reason why proprietary drivers like Nvidia are historically not
installed by default I think is because they have their own license
conditions.
In practice the real problem here seems to be the bugginess of the open
source nouveau driver you
Thanks for the bug report.
Those gamma commands only support Xorg, but you are using a Wayland
session without any Xorg running. To use a Xorg session you need to log
out and then select 'Ubuntu on Xorg' on the login screen.
** Changed in: xorg (Ubuntu)
Status: New => Invalid
--
You
If it's just displaying the wrong texture/window then that fix may be
one that's coming in mutter 42.1:
https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2278
** Package changed: xorg (Ubuntu) => gnome-shell (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
It appears the problem started in the RADEON driver and then Xorg
crashed:
[ 186.951] (EE) RADEON(0): drmmode_do_crtc_dpms cannot get last vblank counter
[ 186.958] (II) RADEON(0): Allocate new frame buffer 1080x1920
[ 186.963] (II) RADEON(0): VRAM usage limit set to 218116K
[ 186.965]
*** This bug is a duplicate of bug 1799679 ***
https://bugs.launchpad.net/bugs/1799679
This is technically an old bug 1799679. It just became worse in 22.04
since GNOME started using GTK4, hence OpenGL, and so most apps are now
affected.
** Package changed: xorg (Ubuntu) =>
When you are returned to the login screen, does Ctrl+Alt+F2 fix it? If
not then:
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
Thanks for the bug report.
The white screen problem is bug 1965882. But there are more reasons to
avoid the 'nouveau' driver and it's probably the cause of your other
issues too. Please open the 'Additional Drivers' app and install the
official Nvidia driver with that.
** Summary changed:
-
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Please execute the following command only once, as it
will automatically gather debugging information, in a terminal:
apport-collect 1970131
When reporting bugs in the future please use apport by using 'ubuntu-
1 - 100 of 15300 matches
Mail list logo
