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
Public bug reported:
[Impact]
/var/lib/dkms/nvidia/390.157/build/nvidia/nv-mmap.c: In function
‘nvidia_mmap_helper’:
/var/lib/dkms/nvidia/390.157/build/nvidia/nv-mmap.c:474:23: error: assignment
of read-only member ‘vm_flags’
474 | vma->vm_flags |= VM_IO;
|
it doesn't matter if it's 1080p, 720p, avi, mkv or mp4
** Attachment added: "PXL_20230517_102804992.mp4"
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/2018458/+attachment/5673547/+files/PXL_20230517_102804992.mp4
--
You received this bug notification because you are a member of
** Attachment added: "PXL_20230517_102927982.mp4"
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/2018458/+attachment/5673546/+files/PXL_20230517_102927982.mp4
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
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
All autopkgtests for the newly accepted mesa (22.2.5-0ubuntu0.1~22.04.2) for
jammy have finished running.
The following regressions have been reported in tests triggered by the package:
gtk+3.0/3.24.33-1ubuntu2 (i386)
mir/2.7.0-0ubuntu3 (armhf)
mutter/42.5-0ubuntu1 (amd64)
Please visit the
All autopkgtests for the newly accepted mesa (22.2.5-0ubuntu0.1~22.04.2) for
jammy have finished running.
The following regressions have been reported in tests triggered by the package:
gtk+3.0/3.24.33-1ubuntu2 (i386)
mir/2.7.0-0ubuntu3 (armhf)
mutter/42.5-0ubuntu1 (amd64)
Please visit the
** 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
All autopkgtests for the newly accepted mesa (22.2.5-0ubuntu0.1~22.04.2) for
jammy have finished running.
The following regressions have been reported in tests triggered by the package:
gtk+3.0/3.24.33-1ubuntu2 (i386)
mir/2.7.0-0ubuntu3 (armhf)
mutter/42.5-0ubuntu1 (amd64)
Please visit the
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:
Happens with me too after sleep/wakeup lenovo x1 carbon gen8 / HDMI LG 27GL850
which should run at 2460x1440@60hz but instead its 1920x1080@60hz.
In my case only restart works. One thing I noticed is that my screen is
initally determined as LG Electronics 31" but its actually 27" monitor
--
It looks like this isn't related to the other bug report. I hadn't fully
understood the table at the bottom of this readme file:
https://github.com/intel/media-driver/blob/master/README.md
Looks like my CPU is one year too old to support post-processing with
the free shaders.
--
You received
** 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
17 matches
Mail list logo
