** Summary changed:
- In some boots, screen display is totally black possible i915 issue
+ [Compaq Presario 420] In some boots, screen display is totally black possible
i915 issue
** Package changed: xorg (Ubuntu) => linux (Ubuntu)
--
You received this bug notification because you are a
Thanks for the bug report. Please change the bug description to cover
only one of those issues and move secondary issues to new bugs.
** Package changed: xorg (Ubuntu) => ubuntu
** Changed in: ubuntu
Status: New => Incomplete
--
You received this bug notification because you are a
Please propose the fix upstream first:
https://gitlab.freedesktop.org/xorg/xserver/-/blob/master/hw/xfree86/common/xf86pciBus.c
The fix should be released in Ubuntu 23.10, 23.04 and 22.04 before we
consider 20.04.
** Tags added: focal
** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu)
** Tags added: a11y zoom
** Package changed: xorg (Ubuntu) => gnome-shell (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/2024403
Title:
Accessibility Zoom - display jumping
To manage
Comment #7 shows the wrong driver in use - it's using software rendering
on the CPU instead of using the GPU. I cannot figure out why yet, but
generally recommend you use long term support release 22.04 instead:
https://ubuntu.com/download/desktop
** Changed in: linux-hwe-5.13 (Ubuntu)
** Package changed: xorg (Ubuntu) => mutter (Ubuntu)
** Tags added: amdgpu hybrid multigpu multimonitor nouveau
--
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/2023979
Title:
Ubuntu don't see
Thanks for the bug report. Please try adding the following kernel
parameter:
i915.enable_psr=0
to /etc/default/grub under GRUB_CMDLINE_LINUX_DEFAULT, then run:
sudo update-grub
and reboot. Finally check to see that it's being used:
cat /proc/cmdline
** Package changed: xorg (Ubuntu) =>
*** This bug is a duplicate of bug 2012985 ***
https://bugs.launchpad.net/bugs/2012985
** Package changed: xorg (Ubuntu) => bijiben (Ubuntu)
** This bug has been marked a duplicate of bug 2023730
bijiben-shell-search-provider crashed with SIGSEGV in
** Also affects: libinput via
https://gitlab.freedesktop.org/libinput/libinput/-/issues/907
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libinput in Ubuntu.
That sounds like a kernel problem, but you're not currently using a
supported Ubuntu kernel. Can you try booting the Ubuntu kernel? It
should be version 6.2.0-20.20
** Package changed: xorg (Ubuntu) => linux (Ubuntu)
** Changed in: linux (Ubuntu)
Status: New => Incomplete
** Summary
Thanks for the bug report. Please provide a screenshot, photo or video
so we can understand better what you are describing.
Please also note that Ubuntu 22.10 reaches end of life in a couple of weeks so
please upgrade when you can:
https://ubuntu.com/download/desktop
Thanks for the bug report. Please try running 'gnome-control-center' in
a Terminal window. When the bug occurs again, please tell us what text
if any has been logged to the Terminal window.
** Package changed: xorg (Ubuntu) => gtk+3.0 (Ubuntu)
** Changed in: gtk+3.0 (Ubuntu)
Status: New
Thanks for the bug report. Please reproduce the bug again, wait a while
and power off the machine. Then turn it on again and run:
journalctl -b-1 > prevboot.txt
and attach the resulting text file here.
** Package changed: xorg (Ubuntu) => ubuntu
** Changed in: ubuntu
Status: New =>
Thanks for the bug report.
Please open a Terminal window and run 'top'. Now wait for the bug to
occur again. Does 'top' show any process using high CPU when the stutter
is happening?
** Package changed: xorg (Ubuntu) => ubuntu
** Changed in: ubuntu
Status: New => Incomplete
--
You
** Package changed: xorg (Ubuntu) => gnome-shell (Ubuntu)
** Bug watch added: Mozilla Bugzilla #1745714
https://bugzilla.mozilla.org/show_bug.cgi?id=1745714
** Also affects: thunderbird via
https://bugzilla.mozilla.org/show_bug.cgi?id=1745714
Importance: Unknown
Status: Unknown
I wonder if libinput is incorrectly scaling up the size of the
hysteresis dead zone it uses to ignore finger/sensor jitter. It really
should only be scaling up the movement velocity. The hysteresis size
shouldn't be scaled because it is in touchpad sensor units, not pixels.
--
You received this
** No longer affects: mutter (Ubuntu)
** Also affects: mutter (Ubuntu)
Importance: Undecided
Status: New
** Changed in: libinput (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libinput in
Thanks for the bug report. The 'oibaf' PPA you are using is not
supported and is known to cause graphics bugs like this. Please
uninstall it using the 'ppa-purge' command, reboot, and then open new
bugs for any problems that you find.
** Package changed: xorg (Ubuntu) => ubuntu
** Changed in:
** Package changed: gstreamer-vaapi (Ubuntu) => gstreamer (Ubuntu)
** Changed in: gstreamer (Ubuntu)
Status: Triaged => Fix Committed
** Tags added: fixed-in-gstreamer-1.23 fixed-upstream
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
** Package changed: xorg (Ubuntu) => gnome-shell (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/2022954
Title:
RDP and VNC fail when headless with no monitor (but work otherwise!)
To
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
** Summary changed:
- random blue/pink frames in the desktop
+ [amdgpu] random blue/pink frames in the desktop
** Package changed: xorg (Ubuntu) => linux-hwe-5.19 (Ubuntu)
** Tags added: amdgpu
** Also affects: xserver-xorg-video-amdgpu (Ubuntu)
Importance: Undecided
Status: New
--
Thanks for the bug report. I would usually recommend trying
MUTTER_DEBUG_ENABLE_ATOMIC_KMS=0 to fix this but your logs seem to
suggest that mode is already active.
Please:
1. Try disabling these extensions in case they're having some effect:
'impatie...@gfxmonk.net',
*** This bug is a duplicate of bug 2012388 ***
https://bugs.launchpad.net/bugs/2012388
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 2012388, so it is being marked as such. Please
Thank you for reporting this bug to Ubuntu.
Ubuntu 18.04 (bionic) reached end-of-standard-support on May 31, 2023.
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
** Tags removed: bionic
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers-390 in Ubuntu.
https://bugs.launchpad.net/bugs/1881909
Title:
Screen tearing with Nvidia Optimus
To manage notifications about this bug go to:
Thank you for reporting this bug to Ubuntu.
Ubuntu 18.04 (bionic) reached end-of-standard-support on May 31, 2023.
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
Thank you for reporting this bug to Ubuntu.
Ubuntu 18.04 (bionic) reached end-of-standard-support on May 31, 2023.
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
Thank you for reporting this bug to Ubuntu.
Ubuntu 18.04 (bionic) reached end-of-standard-support on May 31, 2023.
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
Thank you for reporting this bug to Ubuntu.
Ubuntu 18.04 (bionic) reached end-of-standard-support on May 31, 2023.
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
Thank you for reporting this bug to Ubuntu.
Ubuntu 18.04 (bionic) reached end-of-standard-support on May 31, 2023.
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
Thank you for reporting this bug to Ubuntu.
Ubuntu 18.04 (bionic) reached end-of-standard-support on May 31, 2023.
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
Thank you for reporting this bug to Ubuntu.
Ubuntu 18.04 (bionic) reached end-of-standard-support on May 31, 2023.
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
Thank you for reporting this bug to Ubuntu.
Ubuntu 18.04 (bionic) reached end-of-standard-support on May 31, 2023.
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
Thank you for reporting this bug to Ubuntu.
Ubuntu 18.04 (bionic) reached end-of-standard-support on May 31, 2023.
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
** Description changed:
+ [ Impact ]
+
See https://github.com/intel/media-driver/issues/1662 for bug filed
against upstream Intel media-driver project.
The version of intel-media-va-driver on Jammy has broken functionality in the
VPP path.
This can be worked around by replacing with
** Also affects: intel-media-driver (Ubuntu Jammy)
Importance: Undecided
Status: New
** Also affects: intel-media-driver-non-free (Ubuntu Jammy)
Importance: Undecided
Status: New
** No longer affects: intel-media-driver-non-free (Ubuntu Jammy)
** Changed in:
Sounds like another fix similar to bug 1983456 will be required.
** Package changed: xorg (Ubuntu) => gnome-shell-extension-ubuntu-dock
(Ubuntu)
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
The first step would be to identify what to backport to jammy. If the
answer is:
https://github.com/intel/media-
driver/commit/469f8c9f0d497320772629c912464018da653876
then it's quite large so needs to be discussed with the kernel team who
manage hardware enablement.
--
You received this bug
Actually bug controllers don't get the nominate for series link because
we get a "Target for series" link instead. Which means the nomination
was accepted. But the problem is that accepting it and creating a jammy
task also requires the task have an owner - someone assigned to do the
backporting.
** Tags added: dualgpu hybrid nouveau radeon
** Summary changed:
- added nvidia card and got problem with radeon
+ radeon is crashing and logging [drm:radeon_crtc_page_flip_target [radeon]]
*ERROR* failed to pin new rbo buffer before flip
** Package changed: xorg (Ubuntu) => linux-hwe-5.15
** Summary changed:
- Display
+ Screen does not turn on when woken
** Tags added: hybrid i915 multigpu nvidia
** Summary changed:
- Screen does not turn on when woken
+ Lenovo IdeaPad L340-15IRH screen does not turn on when woken
** Package changed: xorg (Ubuntu) => linux (Ubuntu)
** Summary
*** This bug is a duplicate of bug 2012388 ***
https://bugs.launchpad.net/bugs/2012388
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 2012388, so it is being marked as such. Please
Your Intel graphics drivers are installed and working. Because they are
built-in, you will never see them as an option in the GUI.
Also Ubuntu 14.04 reached end of standard support in 2019 so please
install a newer release when you can.
https://wiki.ubuntu.com/Releases
Please look in /var/log/apt/history.log to identify which update you are
referring to.
If the problem is caused by some Ubuntu update then it will be tracked
here, but if it's just a bug in Brave and Chrome then it would need to
be tracked at https://bugs.chromium.org/p/chromium/issues/list
**
*** This bug is a duplicate of bug 2013216 ***
https://bugs.launchpad.net/bugs/2013216
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 2013216, so it is being marked as such. Please
** 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/2020709
Title:
Screens won't turn on after manually suspending
To manage notifications about
Ubuntu keeps multiple kernel versions installed as a safety fallback.
And also each DKMS driver like nvidia should get rebuilt for each kernel
that's installed. Although sometimes that step fails, which might
explain this bug...
Please reproduce the issue again so we can get a system log of it.
** Attachment removed: "CoreDump.gz"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1998984/+attachment/5634943/+files/CoreDump.gz
** Information type changed from Private to Public
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed
Your gnome-shell crash on May 3 looks like it might be caused by an
extension:
meta_compositor_get_laters () from /lib/x86_64-linux-gnu/libmutter-10.so.0
?? () from /lib/x86_64-linux-gnu/libmutter-10.so.0
g_object_unref () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
?? () from
Thanks for the bug report.
We can't support Debian here, although the packages are very similar to
Ubuntu. I don't see any Ubuntu bugs that look like this one.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
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
Strictly speaking this should be "Fix Released" since Ubuntu 23.04 and
later ships the 23 driver already.
You should see a nominate for series link near the top of the page so
please select that to nominate this bug to be fixed in jammy.
P.S. We recommend intel-media-va-driver-non-free because
** No longer affects: xorg-server (Ubuntu)
** Package changed: nvidia-graphics-drivers-525 (Ubuntu) => 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/2018525
Title:
[nvidia]
I don't see any evidence of the offending line in Ubuntu 22.04 so 22.10
is also unlikely. Particularly since we've supported Wayland for quite
some time now, and it works.
It does sound like a manual change you made.
** Package changed: xorg (Ubuntu) => ubuntu
** Changed in: ubuntu
What error do you see when trying to update?
** 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.
Sounds like this isn't a crash (unless you find files in /var/crash).
Can you provide a better summary of the problem than "Xorg crash"?
** Package changed: xorg (Ubuntu) => ubuntu
** Changed in: ubuntu
Status: New => Incomplete
--
You received this bug notification because you are a
Please check to see if the loss of display is:
* gnome-shell crashing and being restarted (while Xorg and the apps keep
running); or
* A faulty monitor cable/connection.
If it's just a laptop display then most likely gnome-shell is crashing
so please follow
Thanks for the bug report.
I can't seem to reproduce the issue here. Perhaps you just need to
delete ~/.Xauthority or perhaps there's something in your local config
setting it? Try:
grep XAUTHORITY ~/.*
--
You received this bug notification because you are a member of Ubuntu-X,
which is
** Changed in: gstreamer-vaapi (Ubuntu)
Importance: Undecided => Medium
** Changed in: gstreamer-vaapi (Ubuntu)
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to intel-media-driver in Ubuntu.
** No longer affects: mutter (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/1754284
Title:
Fullscreen windows are tearing in Xorg sessions
To manage notifications about this
*** This bug is a duplicate of bug 1754284 ***
https://bugs.launchpad.net/bugs/1754284
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 1754284, so it is being marked as such. Please
** Also affects: libinput via
https://gitlab.freedesktop.org/libinput/libinput/-/issues/893
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libinput in Ubuntu.
*** This bug is a duplicate of bug 2012388 ***
https://bugs.launchpad.net/bugs/2012388
Sounds like you're getting blocked by bug 2012388
** Package changed: xorg (Ubuntu) => ubuntu
** This bug has been marked a duplicate of bug 2012388
X11 window at top-right of the screen is invisible
Possibly related: bug 2019869, bug 2019979
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers-390 in Ubuntu.
https://bugs.launchpad.net/bugs/2019481
Title:
System boots to a black screen when nvidia-390 is installed
To
Thanks for the bug report.
Please reproduce the problem again so we can collect the full system
log, then reboot to a terminal and run:
journalctl -b-1 > prevboot.txt
and attach the resulting text file here.
Although your Xorg log already mentions:
[20.820] (EE) NVIDIA(GPU-0): Failed to
Were you actually using Xorg or Wayland when the problem happened?
Sounds like the same mutter issue as bug 1987976.
** Package changed: xorg (Ubuntu) => mutter (Ubuntu)
** Changed in: mutter (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a
Please try:
* Running the affected apps in a Terminal window to see if they log
anything.
* Running 'gnome-extensions list --enabled' to see if any extensions
other than the three Ubuntu extensions are active.
* Running 'journalctl -f' to see if anything is flooding the system
log. Your
Sounds like VirtualBox had a "grab" on the mouse.
** Package changed: xorg (Ubuntu) => virtualbox (Ubuntu)
** Summary changed:
- Mouse events stop being propagated to most of the application windows
+ Mouse events stop being propagated to most of the application windows when
VirtualBox is
Please also check to see if the problem only happens:
* In full screen mode (bug 1754284)
* With multiple monitors (bug 1853094)
* With custom scaling (bug 1846398)
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
Thanks, that's called tearing.
Please log into Xorg again, reproduce the bug and then run:
xrandr --verbose > xrandr-xorg.txt
and attach the resulting text file here.
** Tags added: tearing
** Summary changed:
- Video glitch
+ Screen tearing when playing video
--
You received this bug
Upstream thinks this should be fixed in mutter 44.1, but we're yet to
confirm.
** No longer affects: xorg (Ubuntu)
** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #2816
https://gitlab.gnome.org/GNOME/mutter/-/issues/2816
** Also affects: mutter via
> I just use nvidia Graphics.
It appears the opposite is true. Only the built-in Intel GPU is active
so any secondary monitor connected to the Nvidia GPU won't work...
Please open the 'Additional Drivers' app and use it to reinstall the
Nvidia driver. Try choosing one that's not the "Open"
Please make a video of the problem using a phone and then attach it
here.
** Tags removed: wayland-session
** Changed in: xorg-server (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in
** No longer affects: xwayland (Ubuntu)
--
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/2015577
Title:
middle click to lower window no longer works for xwayland windows
To manage
This bug is about the open source nouveau driver only.
The issue in comment #38 is covered in bug 938751.
--
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/1969959
Title:
[nouveau] Weird colors
Ah right, that's confusing. KBLx only has one Yes per cell whereas you'd need
two Yes's:
https://github.com/intel/media-driver/blob/master/README.md#video-processing-features
Last time I used the processing features it was on Haswell and Kaby
Lake. That was using the old driver model though:
** Summary changed:
- No VA-API VAEntrypointVideoProc on Lunar
+ No VA-API VAEntrypointVideoProc on Kaby Lake
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to intel-media-driver in Ubuntu.
https://bugs.launchpad.net/bugs/2019917
Title:
No
** Tags added: jammy
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to intel-media-driver in Ubuntu.
https://bugs.launchpad.net/bugs/2019831
Title:
intel-media-va-driver VPP broken until 22.6.5
To manage notifications about this bug go to:
Those are different issues. And actually the Nvidia-specific problem was
fixed some time ago when Nvidia drivers started shipping KMS support
enabled by default. So this bug is fixed in all current nvidia-graphics-
drivers.
The remaining problems are better covered by bug 1869655 and bug
1970069.
** Summary changed:
- Xorg freeze
+ drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring vcn_dec timeout
** Package changed: xorg (Ubuntu) => linux-hwe-5.19 (Ubuntu)
** Tags added: amdgpu
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in
** Tags added: vmwgfx
** Summary changed:
- Significant window drawing problems as VMware Workstation 17 guest.
+ [vmwgfx] Significant window drawing problems as VMware Workstation 17 guest.
** Also affects: mesa (Ubuntu)
Importance: Undecided
Status: New
** Package changed:
** Tags added: nvidia
** Summary changed:
- Xorg freeze
+ [nvidia] Intermittent loss of display
** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu)
** Also affects: nvidia-graphics-drivers-525 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification
*** This bug is a duplicate of bug 1870736 ***
https://bugs.launchpad.net/bugs/1870736
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 1870736, so it is being marked as such. Please
** Summary changed:
- Kernel 6.2 touchpad won´t drag and drop
+ [ASUS X555LAB] Kernel 6.2 touchpad won´t drag and drop (but 5.19 works)
** Package changed: xorg (Ubuntu) => linux (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in
*** This bug is a duplicate of bug 2012388 ***
https://bugs.launchpad.net/bugs/2012388
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 2012388, so it is being marked as such. Please
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
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. Which browser are you using?
** Package changed: xorg (Ubuntu) => ubuntu
** Package changed: ubuntu => yaru-theme (Ubuntu)
** Changed in: yaru-theme (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu-X,
Thanks for the bug report. Please report it upstream at
https://gitlab.freedesktop.org/libinput/libinput/-/issues/new including
details of the model of laptop you are using.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libinput in Ubuntu.
*** This bug is a duplicate of bug 2017097 ***
https://bugs.launchpad.net/bugs/2017097
** This bug has been marked a duplicate of bug 2017097
[raspi] GNOME Shell runs at 30 FPS unless the CPU is being stressed
--
You received this bug notification because you are a member of Ubuntu-X,
Thanks for the bug report.
Please:
1. Take a photo or video of the problem.
2. Tell us if the problem occurs in Xorg, Wayland, or both session
types.
** Package changed: xorg (Ubuntu) => ubuntu
** Changed in: ubuntu
Status: New => Incomplete
--
You received this bug notification
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
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
Please also check for crashes by:
https://wiki.ubuntu.com/Bugs/Responses#Missing_a_crash_report_or_having_a_.crash_attachment
--
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/2017528
Title:
Thanks for the bug report.
Please:
1. Check to see if the bug affects Wayland, Xorg, or both.
2. Run:
dconf dump /org/gnome/ > settings.txt
and attach the resulting text file here.
3. Remove any local extensions you might have:
cd ~/.local/share/gnome-shell/
rm -rf extensions
If the BIOS allows you to switch to discrete graphics only (use dGPU for
everything and disable the iGPU) then you would be able to use the
Nvidia driver for all displays and that would avoid the bug.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed
** Summary changed:
- Bug with the graphic driver off my hardware
+ [Lenovo V15-IIL] Screen brightness hotkeys don't work
** Package changed: xorg (Ubuntu) => linux (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
mutter = Invalid because there's nothing mutter or gnome-shell is doing
to cause this.
xorg-server = Won't Fix because it's legacy software and is never going
to be redesigned to avoid this limitation.
linux (kernel) = Opinion because it is the source of the 16384
limitation but that might be a
I've tracked down the origin of the 16384 limit. It's a combination of:
* Xorg treating all monitors as a single framebuffer; and
* The modesetting driver getting the maximum dimensions from the kernel via
drmModeResPtr; and
* The Intel kernel graphics driver limiting framebuffer sizes to
401 - 500 of 9936 matches
Mail list logo
