Are you enabling the native Wayland backend via the environment variable
`MOZ_ENABLE_WAYLAND=1` (or `GDK_BACKEND=wayland`)?
If not, this is probably an Xwayland issue, possibly fixed in the
upstream xserver 1.20.7 release (or in the upcoming 1.20.8 release).
--
You received this bug
Glad to hear it doesn't seem to happen with the radeon driver.
modesetting driver issues can be filed here:
https://gitlab.freedesktop.org/xorg/xserver/issues/new
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
(In reply to Avamander from comment #13)
> Good to know. So I can re-enable it?
You haven't actually disabled it yet, or the radeon driver wouldn't be
working. But yeah, better make sure it won't actually get disabled.
--
You received this bug notification because you are a member of Ubuntu
(In reply to Avamander from comment #10)
> You can switch from Xorg modesetting driver to the xf86-video-ati radeon
> driver by setting `modeset=0` kernel parameter
That kernel parameter would prevent the radeon kernel driver from
working. It's not directly related to which Xorg driver is used.
You're using the Xorg modesetting driver, not the xf86-video-ati radeon
driver. Does the problem also occur with the latter? If yes, please
attach the corresponding Xorg log file and output of dmesg.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
The Xorg log file is still from the modesetting driver, not the radeon
one. Also, it doesn't contain the failure lines. Make sure you attach
the information corresponding to the problem. You may need to get the
Xorg.*.log.old file.
--
You received this bug notification because you are a member
(In reply to Michel Dänzer from comment #11)
> > and installing the `xserver-xorg-video-radeon` on Ubuntu 19.04.
>
> The radeon driver should be used automatically if xserver-xorg-video-ati is
> installed as well, [...]
Never mind, just installing xserver-xorg-video-radeon s
Resolving per comment 4, thanks for the report and follow-ups.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1707695
Title:
radeon :03:00.0: ring 0 stalled for more than 1msec
To manage
(In reply to mirh from comment #79)
> Is this still a thing?
Let's assume not, thanks for the follow-up.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/571770
Title:
Thread [hd-audio0] consuming
(In reply to mirh from comment #79)
> Is this still a thing?
Let's assume not, thanks for the follow-up.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/879790
Title:
[Lenovo Thinkpad T60] Sound
(In reply to Shmerl from comment #16)
> Is it possible to do anything about it in the compositor, [...] ?
Possibly. Basically, the compositor must not reparent a "borderless
fullscreen" X11 window to a larger X11 window (e.g. for drop shadows).
--
You received this bug notification because you
(In reply to Shmerl from comment #13)
> What is the way to do it in XWayland and KWin for borderless fullscreen like
> in Wine (not true fullscreen)?
I suspect "borderless fullscreen" with kwin is the same as windowed as
far as Xwayland is concerned.
(In reply to Daniel van Vugt from comment
(In reply to erhard_f from comment #15)
> Played around a bit with xorg and kernel options on my G5 and worked out
> that I can drive the Radeon 9650 at AGP x8 if I disable DRI completely via
> Option "NoAccel" "true" in /etc/xorg.conf.
>
> I had no GPU-lockups since then
Sure, because you're
(In reply to tempel.julian from comment #11)
> Is it planned or possible to turn vsync entirely off for Xorg fullscreen
> applications like games to e.g. have lowest input latency?
This can be controlled to some degree via the usual GLX/EGL
functionality, which can be overridden via the driconf
With KWin, the changes referenced in comment 8 only have an effect for
fullscreen applications. (With gnome-shell, it can also have an effect
for windowed apps using client-side decorations)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
It sounds like the latest patch fixes the problem you filed this report
for, so I posted it to the amd-gfx mailing list for review.
The problem(s) with switching between one and two monitors should be
tracked separately, preferably at
So the latest patch doesn't help for the VGA monitor not going off?
Please attach the output of xrandr --verbose when both monitors are
enabled. It doesn't matter whether or not any of my patches are enabled
when you do that.
The kernel panic is a kernel bug and probably not directly related to
Does this updated version of the patch work better? If not:
The black screen when changing between one and two monitors never
happens without this patch?
Please attach the output of xrandr --verbose when both monitors are
enabled.
P.S. Thanks for reporting the compile warning, but it's harmless
Does this patch work better? If not, please provide new gdb backtraces
again.
** Patch added: "Wait for pending flips to complete before turning off an
output or CRTC"
Can you get new gdb backtraces from when it hangs with the old fix with
two monitors and when it hangs with the new fix?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1577170
Title:
[solved] screen
This should be a better fix. Does it fix the problem?
** Also affects: xserver-xorg-driver-ati
Importance: Undecided
Status: New
** Patch added: "Wait for pending flips to complete before turning off a CRTC"
Speaking as a VMware developer who worked on the vmwgfx drivers before,
I'm not sure it makes sense to do this while the kernel driver is
guarded by CONFIG_STAGING and the userspace drivers aren't enabled by
default by VMware Tools.
At the very least, this should probably require a more specific
Public bug reported:
Binary package hint: compiz
Source package: compiz 1:0.8.4-0ubuntu2
1) Ubuntu 9.10
2) compiz-core compiz 1:0.8.4-0ubuntu2
3) The screen should always continue updating properly after the screen
size changes.
4) Sometimes after screen resizes the screen becomes corrupted
** Patch added: Make sure viewport cache always matches last glViewport call
http://launchpadlibrarian.net/41243560/compiz-viewport.diff
--
Occasional corruption after screen resize due to bogus GL viewport
https://bugs.launchpad.net/bugs/541430
You received this bug notification because you
I just successfully finished an Easy Install of Alpha 2.
** Changed in: ubuntu
Status: New = Fix Released
--
Ubuntu 10.04 Alpha1 Desktop does not install on Vmware virtual machine
https://bugs.launchpad.net/bugs/497597
You received this bug notification because you are a member of Ubuntu
It might be worth trying again with xf86-video-vmware = 10.16.9, as
older versions would always crash with xserver = 1.7. Not sure when
this will be available in a lucid install image though.
--
Ubuntu 10.04 Alpha1 Desktop does not install on Vmware virtual machine
26 matches
Mail list logo
