*** This bug is a duplicate of bug 1792932 ***
https://bugs.launchpad.net/bugs/1792932
** This bug has been marked a duplicate of bug 1792932
Desktop fails to boot in vbox: Xorg assert failure: Xorg:
../../../../dix/privates.c:384: dixRegisterPrivateKey: Assertion
`!global_keys[type].cre
*** This bug is a duplicate of bug 1811023 ***
https://bugs.launchpad.net/bugs/1811023
Thanks for the bug report. The crash in XorgLogOld.txt looks a lot like
bug 1811023 so we should track it there for now.
If you would like to investigate further and help us find out more details of
the cr
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
Unfortunately the backtrace in Xorg logs can't be trusted. It's usually
wrong because of the lack of debug symbols. Also I can't find any other
reports of crashes that look like this one. So...
Thank you for taking the time to report this bug and helping to make
Ubuntu better. It sounds like some
TX 2080 SUPER Mobile / Max-Q] [10de:1e93]
(rev a1) (prog-if 00 [VGA controller])
Subsystem: Hewlett-Packard Company TU104M [GeForce RTX 2080 SUPER Mobile /
Max-Q] [103c:8736]
InstallationDate: Installed on 2021-04-16 (0 days ago)
InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Bet
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
[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.
https://bugs.launc
The solution has been found and should have been rather obvious in the
first place... Just try a different distribution.
I decided to try out Linux Mint 20.1 and have been testing it for the
past ~6 hours, completely stock (except for all updates installed), no
kernel modifications or GRUB options
Public bug reported:
[ 1681.827] (II) FBDEV: driver for framebuffer: fbdev
[ 1681.827] (II) VESA: driver for VESA chipsets: vesa
[ 1681.828] (**) modeset(0): claimed PCI slot 0@0:2:0
[ 1681.828] (II) modeset(0): using default device
[ 1681.828] (WW) Falling back to old probe method for fbdev
** Also affects: xserver-xorg-driver-ati via
https://gitlab.freedesktop.org/xorg/driver/xf86-video-ati/-/issues/194
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
https://bu
This bug was fixed in the package mutter - 3.38.4-1ubuntu2
---
mutter (3.38.4-1ubuntu2) hirsute; urgency=medium
[ Daniel van Vugt ]
* Revert "debian/patches: Properly handle configuration events on windows"
to fix a regression making some windows to move on resize (LP: #192203
** Package changed: ubuntu => xorg (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/1924583
Title:
ASPEED AST driver seems unstable in 20.04.2 LTS
To manage notifications about this bug
You have been subscribed to a public bug:
I have had the screen go blank several times. Each time that this
occurred, I was selecting the "Settings" item from the upper right
corner arrow. Perhaps there are a lot of low level accesses that occur
when this menu item is selected that somehow locks
thanks. Timo, could you SRU this one please?
** Also affects: xserver-xorg-input-libinput (Ubuntu Hirsute)
Importance: High
Status: Triaged
** Changed in: xserver-xorg-input-libinput (Ubuntu Hirsute)
Assignee: (unassigned) => Timo Aaltonen (tjaalton)
** Tags removed: rls-hh-incomi
Hi Daniel,
Thank you for sharing.
We are not allow to provide a customization as workaround before we know the
fix plan.
I reported an upstream issue:
https://gitlab.freedesktop.org/xorg/driver/xf86-video-ati/-/issues/194
--
You received this bug notification because you are a member of Ubuntu
Hi Daniel,
Thank you for sharing.
OEM team is not allow the provide a customization as workaround before we don't
know the plan to fix.
I reported an issue as
https://gitlab.freedesktop.org/xorg/driver/xf86-video-ati/-/issues/194
** Bug watch added: gitlab.freedesktop.org/xorg/driver/xf86-vide
Public bug reported:
llvm 12.0 is finally out, migrate the Intel OpenCL stack to it to match
Mesa et al.
** Affects: intel-opencl-clang (Ubuntu)
Importance: Undecided
Status: New
** Affects: spirv-llvm-translator (Ubuntu)
Importance: Undecided
Status: New
** Also aff
@seb128,
Thanks a lot!
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libwacom in Ubuntu.
https://bugs.launchpad.net/bugs/1921991
Title:
[SRU] Support isdv4-aes stylus group and multiple AES stylus
definitions
To manage notifications abo
Anyway, for this bug my thinking is that if a different config satisfies
the OEM then that can be considered as a semipermanent workaround.
Other than that, it looks like the bug needs to be reported upstream to
https://gitlab.freedesktop.org/xorg/driver/xf86-video-ati
--
You received this bug n
Good point. Running 'man amdgpu' I can immediately see one such good
reason:
Option "TearFree" "boolean"
--
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
because the native drivers have features that modesetting_drv does not
have, and how AMD expects them to be used
--
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] Dis
Uploaded to focal
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libwacom in Ubuntu.
https://bugs.launchpad.net/bugs/1921991
Title:
[SRU] Support isdv4-aes stylus group and multiple AES stylus
definitions
To manage notifications about this
I've seen a couple of people report issues with manual NVIDIA driver
installations recently but so long as you installed the NVIDIA driver
through the 'Additional Drivers' app then it is expected to work.
I think I ran out of ideas for this bug a month ago but it does seem to
be assigned to the wr
23 matches
Mail list logo
