[Ubuntu-x-swat] [Bug 1911887] Re: Xorg freeze
Thanks for the bug report. It appears you have the proprietary Nvidia kernel driver installed but also are using the open source Xorg driver, which is the wrong one. Please try removing and then reinstalling the Nvidia driver in the 'Additional Drivers' app and then reboot. ** Summary changed: - Xorg freeze + [nvidia] Xorg freeze ** Package changed: xorg (Ubuntu) => nvidia-graphics-drivers-340 (Ubuntu) ** Also affects: xorg-server (Ubuntu) Importance: Undecided Status: New ** Changed in: nvidia-graphics-drivers-340 (Ubuntu) Status: New => Incomplete ** Changed in: xorg-server (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/1911887 Title: [nvidia] Xorg freeze To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1911887/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1912083] Re: the icons are longer
Please clarify which icons, where. Can you attach a screenshot or photo of the problem? ** 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/1912083 Title: the icons are longer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1912083/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1911858] Re: i am not aware what are these errors
*** This bug is a duplicate of bug 1911857 *** https://bugs.launchpad.net/bugs/1911857 ** Package changed: xorg (Ubuntu) => ubuntu ** This bug has been marked a duplicate of bug 1911857 cant tell whats wrong -- 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/1911858 Title: i am not aware what are these errors To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1911858/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1911857] Re: cant tell whats wrong
** 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/1911857 Title: cant tell whats wrong To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1911857/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1911219] Re: [nouveau] Xorg freeze
Thanks but unfortunately that did not help. Next please try all of these steps: 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. 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 find any links to recent problems on that page? If so then please send the links to us. 3. If step 2 also failed then apply the workaround from bug 994921, reboot, reproduce the crash, and retry step 1. Please take care to avoid attaching .crash files to bugs as we are unable to process them as file attachments. It would also be a security risk for yourself. -- 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/1911219 Title: [nouveau] Xorg freeze To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1911219/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1873052] Re: Showing two cursors after login
** Tags added: amdgpu -- 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/1873052 Title: Showing two cursors after login To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1873052/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1855757] Re: [nvidia] Background image corrupted after standby or resume from suspend
focal-proposed is not expected to help with this bug. The fix I mentioned in comment #57 is in future mutter version 40. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1855757 Title: [nvidia] Background image corrupted after standby or resume from suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1855757/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1912030] Re: Crash unless ffmpeg direct rendering disabled with ATI X1400
But, not all VLC video outputs are supposed to use OpenGL, so I don't see why Mesa is relevant. One of the crash backtraces doesn't involve Mesa. -- 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/1912030 Title: Crash unless ffmpeg direct rendering disabled with ATI X1400 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1912030/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1912030] Re: Crash unless ffmpeg direct rendering disabled with ATI X1400
Sounds like a driver bug. ** Package changed: vlc (Ubuntu) => mesa (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/1912030 Title: Crash unless ffmpeg direct rendering disabled with ATI X1400 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1912030/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1912030] [NEW] Crash unless ffmpeg direct rendering disabled with ATI X1400
You have been subscribed to a public bug: After upgrading to Ubuntu 20.10, VLC started crashing when I tried to play video. I tried changing to different video output methods, but none of them worked. In the past, I remember several methods working fine. In the ffmpeg advanced preferences page, disabling the direct rendering option made video playback work. I thought the vaapi errors VLC reports had something to do with it, but apparently not, because they still happen with successful playback. This is on a Dell Inspiron 6400 with ATI Mobility Radeon X1400, which doesn't support hardware decoding of the H.264 video I'm trying to play. Here's one backtrace: Thread 26 "vlc" received signal SIGSEGV, Segmentation fault. [Switching to Thread 0x7fff880df640 (LWP 11335)] __memcpy_ssse3 () at ../sysdeps/x86_64/multiarch/memcpy-ssse3.S:104 104 ../sysdeps/x86_64/multiarch/memcpy-ssse3.S: No such file or directory. (gdb) bt #0 __memcpy_ssse3 () at ../sysdeps/x86_64/multiarch/memcpy-ssse3.S:104 #1 0x77d03fc2 in picture_CopyPixels () at /usr/lib/x86_64-linux-gnu/libvlccore.so.9 #2 0x77d04016 in picture_Copy () at /usr/lib/x86_64-linux-gnu/libvlccore.so.9 #3 0x77cdf1ea in () at /usr/lib/x86_64-linux-gnu/libvlccore.so.9 #4 0x77ce1438 in () at /usr/lib/x86_64-linux-gnu/libvlccore.so.9 #5 0x77f67590 in start_thread (arg=0x7fff880df640) at pthread_create.c:463 #6 0x77e87223 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Also another: #0 __memcpy_ssse3 () at ../sysdeps/x86_64/multiarch/memcpy-ssse3.S:104 #1 0x7fffc7022bff in () at /usr/lib/x86_64-linux-gnu/dri/r300_dri.so #2 0x7fffc74f1d66 in () at /usr/lib/x86_64-linux-gnu/dri/r300_dri.so #3 0x7fffc6b41317 in () at /usr/lib/x86_64-linux-gnu/dri/r300_dri.so #4 0x7fffc6cb4b07 in () at /usr/lib/x86_64-linux-gnu/dri/r300_dri.so #5 0x7fffc6cb7dcc in () at /usr/lib/x86_64-linux-gnu/dri/r300_dri.so #6 0x7fffc6cbd9d9 in () at /usr/lib/x86_64-linux-gnu/dri/r300_dri.so #7 0x7fff885b2eee in () at /usr/lib/x86_64-linux-gnu/vlc/plugins/video_output/libgles2_plugin.so #8 0x7fff885ad2c5 in () at /usr/lib/x86_64-linux-gnu/vlc/plugins/video_output/libgles2_plugin.so #9 0x7fff885b3cee in () at /usr/lib/x86_64-linux-gnu/vlc/plugins/video_output/libgles2_plugin.so #10 0x77cdf4e6 in () at /usr/lib/x86_64-linux-gnu/libvlccore.so.9 #11 0x77ce1438 in () at /usr/lib/x86_64-linux-gnu/libvlccore.so.9 #12 0x77f67590 in start_thread (arg=0x7fff886bb640) at pthread_create.c:463 #13 0x77e87223 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: vlc 3.0.11.1-2 ProcVersionSignature: Ubuntu 5.8.0-36.40-generic 5.8.18 Uname: Linux 5.8.0-36-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu50.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Fri Jan 15 18:46:42 2021 InstallationDate: Installed on 2012-01-19 (3284 days ago) InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) SourcePackage: vlc UpgradeStatus: Upgraded to groovy on 2020-10-21 (86 days ago) ** Affects: mesa (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug groovy -- Crash unless ffmpeg direct rendering disabled with ATI X1400 https://bugs.launchpad.net/bugs/1912030 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to mesa in Ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1883497] Re: Only timing mode list in EDID supported on continuous freq monitors
This commit caused a regression to some user upstream, and we have a fix in hirsute but it needs to be applied to groovy as well. As there are no known bugs filed on LP about the regression, we don't have a way to reproduce the issue so the test case here is to just verify the original use case still works. Focal has the fix already because there was a mid-air collision upload of xorg-server to groovy, resulting in my local groovy branch missing the CVE fixes from 2:1.20.9-2ubuntu1.1 that got in the archive. I rejected my groovy upload because it had the wrong buglink, but then for some reason didn't reupload a fixed and rebased version. The focal backport was eventually based on my local -2u1.1 instead of what was in groovy. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server-hwe-18.04 in Ubuntu. https://bugs.launchpad.net/bugs/1883497 Title: Only timing mode list in EDID supported on continuous freq monitors To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1883497/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1883497] Re: Only timing mode list in EDID supported on continuous freq monitors
** Also affects: xorg-server (Ubuntu Groovy) Importance: Undecided Status: New ** Also affects: xorg-server-hwe-18.04 (Ubuntu Groovy) Importance: Undecided Status: New ** Changed in: xorg-server-hwe-18.04 (Ubuntu Groovy) Status: New => Invalid ** Changed in: xorg-server (Ubuntu Groovy) Status: New => In Progress ** Changed in: xorg-server (Ubuntu Groovy) Assignee: (unassigned) => Timo Aaltonen (tjaalton) -- 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/1883497 Title: Only timing mode list in EDID supported on continuous freq monitors To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1883497/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
