Public bug reported:
I was using chrome
deluge was running in the background
I got 3 quick error messages that other apps were shutting down but I
didn't get the names
Then, all applications disappeared from screen
running desktop UI but NO apps
All running apps just stopped.
No error
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]
** Changed in: linux (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-ati in Ubuntu.
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]
** Changed in: linux (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
[Expired for xserver-xorg-video-ati (Ubuntu) because there has been no
activity for 60 days.]
** Changed in: xserver-xorg-video-ati (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
[Expired for xorg-server (Ubuntu) because there has been no activity for
60 days.]
** Changed in: xorg-server (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
Kodi devs-team were very conservative they would not help and asked me
to wait Ubuntu fix the bug.
Kodi is a reference to a bug that affects every graphical software
installed.
I'm observing every new mesa and kernels upgrades, I'll keep informing.
--
You received this bug notification because
No, Kodi does not crash anymore with x-swat and since official mesa
19.0.8-0ubuntu0~18.04.2
But it's followed by another problem, it's not 100% solved.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in Ubuntu.
(In reply to Kai-Heng Feng from comment #145)
> Laptops with Skylake SoC and later shouldn't need bbswitch. PCIe port PM
> will disable the power of the card.
> After nvidia.ko gets unloaded, make sure "power/control" is "auto" for its
> video (e.g. 01:00.0) and audio (e.g. 01:00.1) functions and
I have huwaei matebook d 14
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-amdgpu in Ubuntu.
https://bugs.launchpad.net/bugs/1848741
Title:
[amdgpu] Ubuntu 19.10 horizontal graphics corruption on AMD Ryzen
2500u (Raven
(In reply to Matthias Fulz from comment #144)
> Ok here are more tests:
>
> Disabling the audio part with your suggestion ist working.
> No NVIDIA audio in powertop nor in lspci.
>
> Your solution is basically loading / unloading the nvidia modul now, which
> indeed is working, but not the
Laptops with Skylake SoC and later shouldn't need bbswitch. PCIe port PM will
disable the power of the card.
After nvidia.ko gets unloaded, make sure "power/control" is "auto" for its
video (e.g. 01:00.0) and audio (e.g. 01:00.1) functions and its upstream bridge
(use lspci -t to check).
In
(In reply to Matthias Fulz from comment #143)
> (In reply to arpie from comment #142)
> > (In reply to Matthias Fulz from comment #141)
> > > (In reply to arpie from comment #140)
> > [snip]
>
> Ah I see.
> Then I think this is basically somehow similar to my workaround using the
> snd_hda_intel
(In reply to Kai-Heng Feng from comment #145)
Thank you very much for this optimistic-sounding info, Kai-Heng Feng.
> Laptops with Skylake SoC and later shouldn't need bbswitch. PCIe port PM
> will disable the power of the card.
How do I check if I have Skylake SoC?
I am actually currently
This bug was fixed in the package nvidia-graphics-drivers-435 -
435.21-0ubuntu3
---
nvidia-graphics-drivers-435 (435.21-0ubuntu3) focal; urgency=medium
* debian/templates/control.in:
- Add Conflicts and Replaces to xserver-xorg-video-nvidia-#FLAVOUR#.
This makes sure that
This bug is about kodi crashing, so does it crash with 19.2.1 or not?
If you have other issues, test with 19.10 and then file them upstream.
--
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/1837170
as for testing more AMD hw, (accelerated) media decoding is not within
the scope of hw enablement as required by the OEM's (on any GPU)
--
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/1837170
Public bug reported:
This problem occurs when accessing the systems "setting" menu only after
you try to select "devices" such as printers. The display goes haywire
and refuses to respond to users selections. The only way to recover is
to right-click the gnome menu icon on the left side of
Ok here are more tests:
Disabling the audio part with your suggestion ist working.
No NVIDIA audio in powertop nor in lspci.
Your solution is basically loading / unloading the nvidia modul now,
which indeed is working, but not the optimus part I think?
As soon as I try acpi the freeze is
(In reply to arpie from comment #142)
> (In reply to Matthias Fulz from comment #141)
> > (In reply to arpie from comment #140)
> [snip]
> > > If I completely disable the audio card using :
> > > echo 1 | sudo tee /sys/bus/pci/devices/:01:00.1/remove
> > >
> > > Then the system hangs are
I tried a different cable. It didn't help.
Also, I can trigger my monitors freaking out as described above merely
by launching the Synology Drive Client when the ultra-wide monitor is
connected.
Also, the issue seems to be triggered even if the applet isn't visible
in my top bar, i.e., even if
Just tested your ppa with mesa 19.2.1-1ubuntu1~18.04.1~ppa2, thank you
Since mesa 19.0.8-0ubuntu0~18.04.2 the image produced by Ubuntu with all
media players and browsers is very dark, like the contrast and black
levels were adjusted at a very low value. It became worse than before,
including
I can confirm this bug also on a Dell XPS desktop system, which was
running Ubuntu for several years and versions before without any issues.
In my case the freeze happens with mostly Chrome browsers, usually
within a minute or so. It renders the system practically unusable, so I
would consider it
The video works with kernel 5.4-rc4 form https://kernel.ubuntu.com
/~kernel-ppa/mainline/.
Thank you for your patience.
--
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/1847980
Title:
(In reply to Matthias Fulz from comment #141)
> (In reply to arpie from comment #140)
[snip]
> > If I completely disable the audio card using :
> > echo 1 | sudo tee /sys/bus/pci/devices/:01:00.1/remove
> >
> > Then the system hangs are completely cured
>
> Not working for me. Still
This time I've added 'i915.enable_psr=0 i915.enable_dc=0 i915.enable_fbc=0' to
the kernel parameters. In the current session I had to manually reconnect the
notebook to the docking station and after a few seconds, the displays came back
to life. No flickering at all, it just took a little bit
It's not clear to me how this can be a cable or monitor issue when it
only happens in Xorg and it happens much more frequently when one
particular app is running (see comment #4). Having said that, I will try
to find a spare HDMI cable and test.
I am not using an adapter, I'm plugging an HDMI
the kernel driver seems perfectly happy though.. could you change to
tty1 and copy /var/log/Xorg.0.log somewhere and then attach here
--
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/1847980
and test newer mainline kernels
https://kernel.ubuntu.com/~kernel-ppa/mainline/
try 5.4-rc4 and if it doesn't work, drm-tip
--
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/1847980
Title:
please test mesa 19.2.1 from ppa:ubuntu-x-swat/updates
--
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/1837170
Title:
Kodi package crash after the update of libdrm-amdgpu1
To manage
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: xorg-server (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: lightdm (Ubuntu)
Status: New => Confirmed
--
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/1847980
it's not X to blame, but the one that starts it so moving to gdm3 hoping
that someone would have a clue
** Package changed: xorg-server (Ubuntu) => gdm3 (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
19.10 shipped with mesa 19.2.1
** Project changed: mesa => mesa (Ubuntu)
** Changed in: mesa (Ubuntu)
Status: New => Fix Released
--
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/1826085
You have been subscribed to a public bug:
Description:
Mesa Vulkan VK_INTEL_performance_query extension
Adds support to Mesa and kernel for a new Vulkan extension called
“VK_INTEL_performance_query” enabling exposure of Intel based GPU metric
collection. Enable support for query based metrics
using 'nomodeset' disables the intel gpu completely, so vulkan not
working is the least of your problems ;)
you could try installing newer mainline kernels from
kernel.ubuntu.com/~kernel-ppa/mainline/
maybe start from v5.4-rc and if it doesn't work, try drm-tip. Install
the amd64 version of
35 matches
Mail list logo
