Comment #19 is probably important to answer because we need to know if
we're looking for a backport or a whole new upstream fix.
--
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/1923153
Title
The other finding for comment#20.
If connecting two monitors then there is a way to reproduce it.
1. Set iGPU as primary monitor
2. Run an application from secondary display (dGPU) (e.g. glxgear)
3. Moving the application from secondary display (dGPU) to primary display
(iGPU) then the issue occ
Hi Daniel,
I could reproduce this issue when using today hirsute daily build
$ sha256sum ~/Downloads/hirsute-desktop-amd64.iso
4908a5c919f4b796a856be69a044334eb1a910727180618348db0a8a1ef70360
/home/jeremysu/Downloads/hirsute-desktop-amd64.iso
after switching back to xorg (hirsute default uses
** Changed in: oem-priority
Status: Confirmed => In Progress
--
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/1923153
Title:
[radeon] Display output laggy from iGPU when operating on
** Changed in: ubiquity (Ubuntu Hirsute)
Status: Incomplete => Invalid
--
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/1920665
Title:
Ubiquity KDE crash on try/install and from live sessio
As a workaround you should be able to avoid the radeon Xorg driver with
a custom config, something like:
Section "Device"
Identifier "devname"
Driver "modesetting"
BusID "pci:bus:dev:func"
...
EndSection
--
You received this bug notification bec
As a workaround you should be able to avoid the radeon Xorg driver with
a custom config, something like:
Section "Device"
Identifier "MyRadeon"
Driver "modesetting"
BusID "pci:1:0:0"
EndSection
Then it will use the same interfaces as in a Wayland session.
Combining the above two ideas you could add a new config file (make sure
its name loads before "10-radeon.conf"):
Section "OutputClass"
Identifier "MyRadeon"
MatchDriver "radeon"
Driver "modesetting"
EndSection
--
You received this bug notification because you are a membe
Or just remove/edit /usr/share/X11/xorg.conf.d/10-radeon.conf
--
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/1923153
Title:
[radeon] Display output laggy from iGPU when operating on deskt
@Bin, thanks for the work there. By SRU rule the issue needs to be fixed
in the current serie first. Are the patches in 1.8/hirsute? If not could
you prepare a debdiff for that serie?
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libwacom in Ub
Hi Daniel,
Thanks for sharing comment#27.
Let me summarize the reproduce scenarios in Intel + AMD case.
1. Boot from iGPU -> switch to dGPU -> switch back to iGPU -> iGPU lag.
2. Boot from iGPU -> connect secondary monitor to dGPU -> remove 1st monitor
from iGPU -> dGPU lag.
3. Boot from iGPU -
Public bug reported:
ubuntu whole screen flickering.
ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: xorg 1:7.7+19ubuntu15
ProcVersionSignature: Ubuntu 5.8.0-49.55-generic 5.8.18
Uname: Linux 5.8.0-49-generic x86_64
ApportVersion: 2.20.11-0ubuntu50.5
Architecture: amd64
BootLog: Error: [Err
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: xorg (Ubuntu)
Status: New => Confirmed
--
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/1923632
Title:
Hello,
I was affected by the same bug as you following the Linux
5.8.0-49-generic kernel update (everything is ok with the
5.8.0-48-generic kernel)
However, the problem has been solved with the X.org update which has
been available for a few hours.
Can you look for new updates available and test
Public bug reported:
the information was send by the system
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-70.78-generic 5.4.94
Uname: Linux 5.4.0-70-generic x86_64
.tmp.unity_support_test.0:
ApportVersion: 2.20.11-0ubuntu27.16
Arc
** Changed in: mutter (Ubuntu)
Status: In Progress => Fix Committed
--
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/1896171
Title:
Wayland GL apps appear corrupt on Raspberry Pi 4B (v3d dr
I'm slightly worried you might be hitting multiple different bugs there.
But instead of worrying, maybe just try the 'modesetting' driver. It
might solve even more problems if you get both GPUs using the same
driver:
Section "OutputClass"
Identifier "Use Modesetting"
MatchDriver "radeon|amdgpu
Please explain what kind of problem you have.
** 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.net/bugs/192
Is the problem tearing or flickering? In which apps? Only when full
screen?
Please attach a video or photo of the problem so we can understand
better.
** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu)
** Changed in: xorg-server (Ubuntu)
Status: Confirmed => Incomplete
--
You rec
https://gitlab.freedesktop.org/mesa/mesa/-/issues/4275#note_796719:
```
if (ret < 0) {
#ifdef DEBUG
const bool color = INTEL_DEBUG & DEBUG_COLOR;
fprintf(stderr, "%siris: Failed to submit batchbuffer: %-80s%s\n",
color ? "\e[1;41m" : "", strerror(-ret), color ? "\e[0m"
@seb128,
Thanks for your feedback, I checked 1.8-2ubuntu1 in hirsute-devel,
these patches which I made for focal are all included. So this issue
should be fixed in hirsute with libwacom2-1.8-2ubuntu1 package. Thanks!
--
You received this bug notification because you are a member of Ubuntu-X,
wh
21 matches
Mail list logo
