Verified on a few different reference boards internally by running a set
of 3 Unigine benchmarks with the updated mesa on the following:
Stormpeak W/Radeon 7900 XTX
Stormpeak W/Radeon Pro W7500
Stormpeak W/Radeon Pro W7900
Phoenix AMD Ryzen 7 7840U W/AMD Radeon™ 780M
Phoenix2 AMD Ryzen 5
I'm experiencing the same issue as well.
I'm using an Asus TUF A15 with an RTX 4050.
Gnome crashes when using multiple screens with Firefox and the file
explorer.
One tip is to debug 'the frozen screen' by changing the screen order in
Settings > Display.
Best regards,
--
You received this
Tested the 23.04 Wayland session and can confirm that it is better! Feel
free to close the bug as this will be fixed with updates / future
releases. Thanks for the professional bug handling.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
Yes runs on wayland.
Libinput 1.23.0
Mutter 44.2
It is hard to actually objectively judge this as stutter/lag is very
subjective. Though Fedora feels a lot less fluid (i.e. the cursor doesn't seem
to lag a few frames).
--
You received this bug notification because you are a member of Ubuntu-X,
Trying to pinpoint where the problem can be I found that the problem is not
present in fedora with the exact same set up. I think there is something in
Mutter or Gnome that is different in Ubuntu that let's this bug appear.
Using Fedora fixes the issue for me but I thought I'd post it here for
I can confirm that using Kubuntu with Wayland as well as X11 session the
issue is not present. Hence, I believe this is a Gnome / Mutter issue.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libinput in Ubuntu.
The fix seems to be in 23.1
(https://gitlab.freedesktop.org/mesa/mesa/-/blob/23.1/src/mesa/program/prog_to_nir.c?ref_type=heads#L1039).
For anyone else with the issue, there are PPAs that have been updated
with the code that fixes this issue. I'm using this while waiting for
the official release:
Created upstream bug:
https://gitlab.freedesktop.org/libinput/libinput/-/issues/907
** Bug watch added: gitlab.freedesktop.org/libinput/libinput/-/issues #907
https://gitlab.freedesktop.org/libinput/libinput/-/issues/907
--
You received this bug notification because you are a member of
This is very subjective and I could be wrong. Upon disabling the
extensions the lag was still present. With a USB mouse the lag is not
present or at least not as noticable.
Interestingly if I switch to 1080p the issue dissapears.
I think that subjectively the default mouse acceleration for 4k
This bug affects me too.
--
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/2023008
Title:
cannot install libegl-mesa0 on 22.04.2 LTS
To manage notifications about this bug go to:
Public bug reported:
Found after updating from 20.04 to 22.04
ProblemType: Package
DistroRelease: Ubuntu 22.04
Package: libnvidia-gl-390 (not installed)
ProcVersionSignature: Ubuntu 5.15.0-72.79-generic 5.15.98
Uname: Linux 5.15.0-72-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.5
Brilliant!
grep XAUTHORITY ~/.*
found
/home/dave/.bashrc: export XAUTHORITY=~/.Xauthority
and commenting the line out in .bashrc fixed the problem
I don't know how the export got into my .bashrc
Possibly to do with me recently upgrading to 23.04 from 22.04 via 22.10,
without checking 22.10
Public bug reported:
I'm not sure if it's Xorg crashing, i'm using wayland.
Clean installation Ubuntu 22.10 and upgraded to 23.04.
The bug can be re-produced.
Symptom:
Moving firefox with ongoing video for example Youtube. Moving the firefox
window from screen 2 or 3 to screen1 then it
Sorry about that, I thought linking the bugfix to the question would
show the question post more prominently. I'll keep that in mind for
next time.
Is there a way to see when this fix will make its way to the 22.04
repositories? I'm just curious how to follow along with the progress of
the
Public bug reported:
Feature Request: Upgrade mesa libraries to apply upstream bugfix to a
bug introduced in 22.2.5-0ubuntu0.1~22.04.1.
I was directed to report this bug via my question at
answers.launchpad.net/ubuntu:
https://answers.launchpad.net/ubuntu/+question/705988
Please let me know if
Additional info, not sure if it has any relivance but the last update
installed a new wi fi driver for RTL8821CE card. It seemed to take a
very long time to install.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
r a overheating/grapics card problem. Most users would scrap
their hardware if they were presented with this problem. Hopefully my problem
is fixed but if not could you please advise me further.
All the Best
DAvid
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: xorg 1:7.7+23ubuntu2
Pro
https://opensource.com/life/17/10/top-terminal-emulators
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xterm in Ubuntu.
https://bugs.launchpad.net/bugs/1983276
Title:
xterm processing grep color loses char at end of line
To manage
I googled around and see gnome-terminal is popular. It does not drop
characters in color at end of line. Amusingly, $TERM is xterm-256color
!!!
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xterm in Ubuntu.
Sorry about the email post over-repeat!
Linux console! I used to work on computers with a console, but that was
way back! Mainframes likely still have them, even though they run UNIX
under the covers. So I should avoid using the PC monitor? Get a
terminal, install ssh for login, and come in
Linux console! I used to work on computers with a console, but that was
way back! Mainframes likely still have them, even though they run UNIX
under the covers. So I should avoid using the PC monitor? Get a
terminal, install ssh for login, and come in from either a terminal (who
has one any
So I should avoid xterm, as I like the data to be correct? What is a
more sanely emulation ID ?
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xterm in Ubuntu.
https://bugs.launchpad.net/bugs/1983276
Title:
xterm processing grep color loses
Public bug reported:
Note the xterm displays "freshcla_cron.log" but the strace says the
write data held "fresh\33[01;31m\33[Kclam\33[m\33[K_cron.log", no
missing m. (My trussxx is a strace with options and vi wrapper, evolved
since I left Solaris and its 'truss'. My pse is a ps -ef|grep $@. I
Adding
GRUB_GFXMODE=1920x1080
to /etc/default/grub, running update-grub, and rebooting fixed this for me.
--
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/349943
Title:
Screen blinks randomly on
adding the package xserver-xorg-input-libinput appears to have solved
the problem. According to the folks at freedesktop, it should have
defaulted to use the libinput driver, even without the 40-libinput.conf
file, but in my case it didn't
** Changed in: xserver-xorg-input-libinput (Ubuntu)
I was hoping that updates to the full release would fix this, but it
hasn't. Any suggestions on what I should try to track this down?
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-input-libinput in Ubuntu.
separate bug filed for wayland
note that for this bug I am not sure that it's only an input problem for
this bug. The system is unresponsive (inc numlock) so I can't tell if
it's only the input or if the entire system is locked.
--
You received this bug notification because you are a member of
apport information
** Attachment added: "acpidump.txt"
https://bugs.launchpad.net/bugs/1967651/+attachment/5576405/+files/acpidump.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
apport information
** Attachment added: "Xrandr.txt"
https://bugs.launchpad.net/bugs/1967651/+attachment/5576404/+files/Xrandr.txt
--
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/1967651
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1967651/+attachment/5576402/+files/UdevDb.txt
--
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/1967651
apport information
** Attachment added: "xdpyinfo.txt"
https://bugs.launchpad.net/bugs/1967651/+attachment/5576406/+files/xdpyinfo.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1967651/+attachment/5576393/+files/Lspci.txt
--
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/1967651
apport information
** Attachment added: "Lsusb-t.txt"
https://bugs.launchpad.net/bugs/1967651/+attachment/5576396/+files/Lsusb-t.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1967651/+attachment/5576399/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1967651/+attachment/5576400/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1967651/+attachment/5576398/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
apport information
** Attachment added: "XorgLogOld.txt"
https://bugs.launchpad.net/bugs/1967651/+attachment/5576403/+files/XorgLogOld.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1967651/+attachment/5576401/+files/ProcModules.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1967651/+attachment/5576395/+files/Lsusb.txt
--
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/1967651
apport information
** Attachment added: "Lspci-vt.txt"
https://bugs.launchpad.net/bugs/1967651/+attachment/5576394/+files/Lspci-vt.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
apport information
** Attachment added: "Lsusb-v.txt"
https://bugs.launchpad.net/bugs/1967651/+attachment/5576397/+files/Lsusb-v.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
apport information
** Attachment added: "DpkgLog.txt"
https://bugs.launchpad.net/bugs/1967651/+attachment/5576392/+files/DpkgLog.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
apport information
** Tags added: apport-collected jammy ubuntu wayland-session
** Description changed:
after updating to jammy beta, xorg does not work for any desktop, in
every case the desktop comes up, but there is no response to keyboard or
mouse (not even numlock). I tried
Public bug reported:
after updating to jammy beta, xorg does not work for any desktop, in
every case the desktop comes up, but there is no response to keyboard or
mouse (not even numlock). I tried unplugging and replugging the devices
with no luck.
All desktops do 'work' in the wayland version,
Public bug reported:
Mar 21 20:56:03 Ubuntu-desktop gnome-shell[2287]: Unhandled promise rejection.
To suppress this warning, add an error handler to your promise chain with
.catch() or a try-catch block around your await expression. Stack trace of the
failed promise:#012
Public bug reported:
Any time the computer sleeps, and I wake it the screen backlight turns on but
nothing appears.
This has been occurring since upgrading to Kernel 5.11-44.
I used 5.11-40 without issues, and when I did a fresh install, I used 5.11-27
without issues.
I have tried multiple
Public bug reported:
Una disculpa si me llego a equivocar, soy un usuario principiante.
Desde que instale "Ubuntu" (tanto en la versión LTS como en la actual)
la pantalla llega a tener un problema, se pone en negro y tiene lineas
que están parpadeando como si fueran guiones (___---) de color
Just upgrade, I just tried Ubuntu again and I didn't get the problem
this time. Looks like it's fixed in Ubuntu
--
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/1872802
Title:
Resizing any window
I tried to install both, Ubuntu 20.04.2 lts and pop_os 20.04, this
glitch when resizing is the only problem I can't fix. Both were fresh
installations so i assume it is present and I couldn't find a solution
other than to enable wayland. I don't know how to change
GRUB_DEFAULT_LINUX or disable a
Happens to me in a razer blade stealth (late 2016) Intel UHD Graphics
620. This happens with Ubuntu or pop_os 20.04, this doesn't happen with
wayland in Ubuntu 21.04, sadly wayland is not a viable option for this
laptop
--
You received this bug notification because you are a member of Ubuntu-X,
Public bug reported:
Upon startup after a routine software update, my desktop was limited to
640×480 resolution, making the desktop UI unusable. Switching graphics
drivers didn't help.
Downgrading the kernel from linux-image-5.11.0-7612-generic to linux-
image-5.8.0-7642-generic via Grub after
Public bug reported:
Suddenly end up looking a black screen with number indicating that it cleared
blocks.
=>This *usually* happens when using Zoom screen share or watching Zoom video
recording.
=>Last X crash was about 5:03 am US Central Time Feb 28, 2021, approximately 90
mins ago.
=>Crash
This issue became apparent after installing Ubuntu 20.04.2 LTS. Switched
BIOS to discrete mode and touchpad works.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-input-libinput in Ubuntu.
https://bugs.launchpad.net/bugs/1826597
I have just faced this and kbd_mode -s also fixed the issue for me. The
behavior started out of nothing (something I did without perceiving most
likely). I'm using:
[rafaeldtinoco@fujitsu ~]$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 20.10
Release:
[rafaeldtinoco@fujitsu ~]$ sudo kbd_mode
The keyboard is in Unicode (UTF-8) mode
[rafaeldtinoco@fujitsu ~]$ sudo kbd_mode -C /dev/tty1
The keyboard is in Unicode (UTF-8) mode
[rafaeldtinoco@fujitsu ~]$ sudo kbd_mode -s
[rafaeldtinoco@fujitsu ~]$ sudo kbd_mode -C /dev/tty1
The keyboard is in
Public bug reported:
I have installed the nouveau driver as the latest nvidia driver was not
working in my system (blank screen after reboot). The X11 session is
starting up fine, but whenever I open the Ubuntu settings the X11
session is killed, the system goes back to the logon screen and all
Updating on my side:
When i update to nvidia 450 and reboot, my system starts to freeze.
Most of times i can't even really start the session and have to do a forced
reboot because nothing works, not even using CTRL+ALT+F2.
Go this bug with Kubuntu focal fossa and KDE. Tried with Gnome (with
Public bug reported:
Problem just started happening within the last few days. No major system
changes that I can think of other than some 'live-patches' being reported as
updated...
Only appears to happen in Chrome (so maybe I should report it there?) as other
application don't seem to display
Here are the links to the errors from step #2(I did it wrong the first time
so these may have been there then as well):
https://errors.ubuntu.com/oops/f1dcc3fa-988e-11ea-ad8b-fa163e983629
https://errors.ubuntu.com/oops/f3279c74-95fc-11ea-a45e-fa163e6cac46
1. Look in /var/crash for crash files and if found run:
ubuntu-bug YOURFILE.crash
Then tell us the ID of the newly-created bug.
**NO LOG**
2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where
ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine.
Do you
Public bug reported:
was logged in through team viewer and got kicked out. when i was able
to physically access the machine the screens were on, but was not able
to move the mouse or interact with the computer. performed hard reboot
to get it back on.
ProblemType: Bug
DistroRelease: Ubuntu
My partners "HP Pavillon g6" started showing this issue upgrading from
19.04 -> 19.10.
Following the steps documented in 29/31 I ended up with:
evdev:name:SynPS/2 Synaptics
> 1. Is the high CPU usage sustained when you're not doing anything?
No.
> 2. Is the CPU usage only when using a mouse, or does it also occur
when using a keyboard?
In both cases. For example, Xorg's CPU usage jumps to 85% on my machine
when I continuously switch once per second from one
Did that before filing the bug report, Xorg is the top CPU user.
--
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/1879042
Title:
[radeon] Xorg high CPU usage and stuttering on ubuntu 20.04
Public bug reported:
After upgrading Xubuntu from 19.10 to 20.04, some window operations (e.g.
bringing one to foreground) can take an unusually long time (tenths of second,
enough to compromise the general responsiveness of the system).
Even switching from one terminal window to another causes
Reviewing bug 1868519, it certainly matches the situation. Mouse
movement is the trigger for the crash. For gimp it's moving the mouse
after opening or creating an image. For Libreoffice it's beginning to
use the crop tool, which is also a mouse movement.
--
You received this bug notification
One issue here is that it doesn't always produce a crash file.
--
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/1876992
Title:
X11 session crash on using Gimp or LibreOffice
To manage
Well. It's easy to cause the crash. Open Gimp, create a new image, move
mouse. I'll upload some more crash files.
https://errors.ubuntu.com/oops/4f6c0418-903c-11ea-a976-fa163ee63de6
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in
Public bug reported:
Several applications are crashing X11.
Gimp after creating a new image
Gimp after opening an image
Libre office writer on attempting to crop and image
All the currently running applications then log the following into
syslog
May 5 21:25:22 david-XPS-15-7590
*** This bug is a duplicate of bug 1867668 ***
https://bugs.launchpad.net/bugs/1867668
Thanks Daniel. I uninstalled xserver-xorg-video-intel and removed
/etc/X11/xorg.conf.d/20-intel.conf, which sorted all the display
corruption issues.
It looks like there is a problem on the upgrade with
*** This bug is a duplicate of bug 1867668 ***
https://bugs.launchpad.net/bugs/1867668
Sorry Sebastian - I didn't relaise journalctl piped output to less!
Attached is the full output
** Attachment added: "log.txt"
I tested xfce4 and it worked OK. No graphic problems.
--
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/1875645
Title:
Graphics corruption on shell on login screen and session screen
To manage
journalctl -b 0
-- Logs begin at Sat 2020-02-22 20:36:17 GMT, end at Tue 2020-04-28 17:24:34
BST. --
Apr 28 16:19:45 david-XPS-15-7590 kernel: Linux version 5.4.0-26-generic
(buildd@lcy01-amd64-029) (gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2))
#30-Ubuntu SMP Mon Apr 20 16:58:30 UTC 2020
journalctl -b 0
-- Logs begin at Sat 2020-02-22 20:36:17 GMT, end at Tue 2020-04-28 17:24:34
BST. --
Apr 28 16:19:45 david-XPS-15-7590 kernel: Linux version 5.4.0-26-generic
(buildd@lcy01-amd64-029) (gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2))
#30-Ubuntu SMP Mon Apr 20 16:58:30 UTC 2020
** Attachment added: "Corrupted volume icon on login screen"
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1875645/+attachment/5362473/+files/20200428_142516.jpg
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
** Attachment added: "Corrupted text in the password modal"
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1875645/+attachment/5362469/+files/Screenshot%20from%202020-04-28%2014-30-50.png
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
** Attachment added: "Corrupted ubuntu logo on login screen"
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1875645/+attachment/5362470/+files/20200428_142415.jpg
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
** Attachment added: "Screen corruption once logged in"
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1875645/+attachment/5362464/+files/Screenshot%20from%202020-04-28%2014-25-51.png
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg
Public bug reported:
After upgrading from 19.10 to 20.04 I am seeing blocky green and purple
artefacts on icons, background images and text. This is visible on the
login screen and once logged in.
Only the "shell" is corrupted and any subsequent changes, such as
changing the background image,
Just upgraded from Ubuntu 16 to 18.04.
In my case the problem arises when I unload the driver and then try to
load it again. After the error dmesg states the possible cause:
[ 966.030549] NVRM: API mismatch: the client has the version 390.116, but
NVRM: this kernel module has the
Happened again - here's a fresh link:
https://errors.ubuntu.com/oops/080ff692-4a42-11ea-a953-fa163e983629
--
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/1862290
Title:
Xorg restarts when
Here's the link from step 2:
https://errors.ubuntu.com/oops/bcf0b822-49ce-11ea-a811-fa163ee63de6
--
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/1862290
Title:
Xorg restarts when locked
Public bug reported:
My laptop is currently running Xubuntu 18.04.3. Whenever I lock or
suspend my laptop, Xorg crashes and restarts, frequently bringing down
whatever applications are running within it.
Here's my light-locker --debug, just in case that helps:
[gs_debug_init] gs-debug.c:106
I'm terribly sorry that I didn't update this when my memory was a bit
fresher, but it was fixed by updating to the newer PPAs and a few update
iterations.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers-418 in Ubuntu.
** Package changed: nvidia-graphics-drivers-418 (Ubuntu) => nvidia-
graphics-drivers-435 (Ubuntu)
** Also affects: nvidia-graphics-drivers-418 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
Public bug reported:
After upgrading to eoan and updating all packages, I'm unable to enable
the nVidia drivers. I haven't done much to enable new PPAs yet, though.
ProblemType: Package
DistroRelease: Ubuntu 19.10
Package: nvidia-dkms-418 418.56-0ubuntu1
ProcVersionSignature: Ubuntu
** Description changed:
Steps to reproduce:
- - observe touchpad click-drag working normally (i.e. can click touchpad and
drag an icon, or select text in any direction)
+ - observe touchpad click-drag* working normally (i.e. can click touchpad and
drag an icon, or select text in any
** Description changed:
Steps to reproduce:
- observe touchpad click-drag working normally (i.e. can click touchpad and
drag an icon, or select text in any direction)
- close lid to suspend (need to wait some time until red Thinkpad light above
'i' on lid starts to flash
- open lid to
Public bug reported:
Steps to reproduce:
- observe touchpad click-drag working normally (i.e. can click touchpad and
drag an icon, or select text in any direction)
- close lid to suspend (need to wait some time until red Thinkpad light above
'i' on lid starts to flash
- open lid to resume
-
FWIW This description perfectly describes behaviour is still present on 18.04
in X1C laptops. Specifically my X1 Carbon 5th Gen (fully firmware updated in
Windows), fully software updated 18.04, has this behaviour repeatably.
It would appear related to variety of other bugs around touchpad
Public bug reported:
just tried to change the driver on Ubuntu 19.10
ProblemType: Package
DistroRelease: Ubuntu 19.10
Package: libnvidia-compute-390 390.129-0ubuntu1
ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8
Uname: Linux 5.3.0-10-generic x86_64
NonfreeKernelModules: nvidia_uvm
2) whoppsie-id
acbcb5d1b079d5218876ea773fccafd16cc97435e89ea003436c0b92356075d5609cbab296303cff9589b9e2b61f5acb73b83dfbddd2113b419db8f0aeb29b94
3) /home/myuserid/.local/share/xorg/Xorg.0.log file attached.
1) boot with 4.15.0 - to do later today.
** Attachment added: "Xorg.0.log"
I'm still having issues with Xorg memory consumption on 19.04.
- it is somehow connected with sleep/wakeup of the system
- it is same for nvidia and intel graphic
- it is same whenever I call pm-suspend or close the lid
- uptime does not matter
Nearly every wakeup memory goes from around 150 MB
Public bug reported:
Your system is providing 3D via software rendering rather than hardware
rendering. This is a compatibility mode which should display 3D
graphics properly but the performance may be very poor. If the problem
you're reporting is related to graphics performance, your real
Update: The patches have been merged to drm-tip:
https://cgit.freedesktop.org/drm-
tip/commit/?id=1a74fc0b3f49a0603f230b6f087da33bda3d7c66.
--
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/1714178
FWIW, I also get this one (022554), along with two others (10ac08 and
6013d4).
The machine is an ASUS UX501V with an Intel HD Graphics 530 + NVIDIA GTX
960M (more details below). I'm running an up to date Debian 9.9 with a
4.19.28-2~bpo9+1 kernel (from stretch-backports). It is usually plugged
to
Public bug reported:
$ ubuntu-bug manual fsk
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3.1
ProcVersionSignature: Ubuntu 4.4.0-145.171-generic 4.4.176
Uname: Linux 4.4.0-145-generic x86_64
.tmp.unity_support_test.0:
ApportVersion: 2.20.1-0ubuntu2.18
Architecture:
If I understand it correctly, to completely resolve this issue, we will
need mesa + xserver + kernel fix, but currently only mesa fix is in
place, right?
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in Ubuntu.
Also affects me, after idling for some time computer is taking a very
long time to come back to life.
AMD Ryzen 7 1700
AMD RX550
[ 6380.343388] [drm:generic_reg_wait [amdgpu]] *ERROR* REG_WAIT timeout 10us *
3000 tries - dce110_stream_encoder_dp_blank line:927
[ 6380.343515] WARNING: CPU: 1
Public bug reported:
I have a Z390 chipset with an Intel 9th-gen 9700k processor. Please
cherry-pick https://github.com/intel/intel-vaapi-
driver/commit/3db2871522371b92ea30a544099a8d2be93aa231#diff-
d499f68737f270813a99fa1876dc443a, which adds support for this
chipset/processor.
1 - 100 of 1901 matches
Mail list logo
