[Ubuntu-x-swat] [Bug 1901563] Re: Kernel panic - Xorg tainted - i915
Your kernel log mentions: [ 618.131916] i915 :00:02.0: [drm] *ERROR* Atomic update failure on pipe B (start=36634 end=36635) time 217 us, min 1431, max 1439, scanline start 1421, end 1440 which I think can only happen in Xorg sessions. Try selecting 'Ubuntu on Wayland' from the login screen before you enter your password. ** Package changed: xorg (Ubuntu) => linux (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/1901563 Title: Kernel panic - Xorg tainted - i915 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1901563/+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 1901561] Re: night light not working
It also looks like the BIOS is hiding the Intel GPU, which your old Xorg logs seem to suggest is required to drive the screen, and night light. Please look in your BIOS to try and re-enable the integrated Intel GPU. ** 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/1901561 Title: night light not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1901561/+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 1901561] Re: night light not working
It looks like the Nvidia driver also is not working for you... Try removing and reinstalling the Nvidia driver via the 'Additional Drivers' app. Failing that, I think this should be merged into one of: bug 1880739, bug 1890957 -- 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/1901561 Title: night light not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1901561/+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 1901585] Re: Ubuntu 20.04 LTS Desktop Screen blinking/flickering black and side menu bar turn upsidedown
** Tags added: nvidia ** Package changed: xorg (Ubuntu) => nvidia-graphics-drivers-450 (Ubuntu) ** Also affects: mutter (Ubuntu) Importance: Undecided Status: New ** Changed in: mutter (Ubuntu) Importance: Undecided => High ** Changed in: nvidia-graphics-drivers-450 (Ubuntu) Importance: Undecided => High ** Summary changed: - Ubuntu 20.04 LTS Desktop Screen blinking/flickering black and side menu bar turn upsidedown + [nvidia] Ubuntu 20.04 LTS Desktop Screen blinking/flickering black and side menu bar turn upsidedown -- 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/1901585 Title: [nvidia] Ubuntu 20.04 LTS Desktop Screen blinking/flickering black and side menu bar turn upsidedown To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1901585/+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 1550779] Re: Black screen flickering and [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun
I initially saw flickering with Wayland, so i switched to Xorg to check if it happens also there... and it happens. -- 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/1550779 Title: Black screen flickering and [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1550779/+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 1901470] Re: resolution not listed in xrandr from ASUS ROG PG278QR via HDMI
apport information ** Tags added: apport-collected ubuntu ** Description changed: The PG278QR monitor supports 2560x1440. After installing Ubuntu 20.4, the max resolution presented in the Settings app is 1920x1080, and this resolution is the one that it uses. Switching between the Nvidia driver or the Intel driver (laptop has low-power intel gpu too) doesn't correct the problem. Digging in deeper, based on https://wiki.ubuntu.com/X/Troubleshooting/Resolution#Problem:__Wrong_resolutions.2C_refresh_rates.2C_or_monitor_specs Under Wrong resolutions/refresh rates/or monitor specs, step 3 is to use get-edid | parse-edid. After applying the mode that I wanted manually via xrandr --newmode and xrandr --addmode, I was able to select the max resolution of the monitor and works correctly, until reboot. I will add it to my xorg.conf next. Here is information I collected: output from xrandr after fresh boot: ~$ xrandr Screen 0: minimum 8 x 8, current 3840 x 1080, maximum 32767 x 32767 eDP-1-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 344mm x 193mm 1920x1080 60.01*+ 60.0159.9759.9659.93 1680x1050 59.9559.88 1600x1024 60.17 1400x1050 59.98 1600x900 59.9959.9459.9559.82 1280x1024 60.02 1440x900 59.89 1400x900 59.9659.88 1280x960 60.00 1440x810 60.0059.97 1368x768 59.8859.85 1360x768 59.8059.96 1280x800 59.9959.9759.8159.91 1152x864 60.00 1280x720 60.0059.9959.8659.74 1024x768 60.0460.00 960x720 60.00 928x696 60.05 896x672 60.01 1024x576 59.9559.9659.9059.82 960x600 59.9360.00 960x540 59.9659.9959.6359.82 800x600 60.0060.3256.25 840x525 60.0159.88 864x486 59.9259.57 800x512 60.17 700x525 59.98 800x450 59.9559.82 640x512 60.02 720x450 59.89 700x450 59.9659.88 640x480 60.0059.94 720x405 59.5158.99 684x384 59.8859.85 680x384 59.8059.96 640x400 59.8859.98 576x432 60.06 640x360 59.8659.8359.8459.32 512x384 60.00 512x288 60.0059.92 480x270 59.6359.82 400x300 60.3256.34 432x243 59.9259.57 320x240 60.05 360x202 59.5159.13 320x180 59.8459.32 HDMI-1-1 connected 1920x1080+1920+0 (normal left inverted right x axis y axis) 598mm x 336mm 1920x1080 60.00* 50.0059.94 1280x720 60.0050.0059.94 1024x768 60.00 800x600 60.32 720x576 50.00 720x480 60.0059.94 640x480 60.0059.94 DP-1-1 disconnected (normal left inverted right x axis y axis) output from get-edid | parse-edid: ~$ sudo get-edid | parse-edid This is read-edid version 3.0.2. Prepare for some fun. Attempting to use i2c interface No EDID on bus 1 No EDID on bus 2 No EDID on bus 3 No EDID on bus 5 No EDID on bus 6 No EDID on bus 7 No EDID on bus 9 No EDID on bus 10 3 potential busses found: 0 4 8 Will scan through until the first EDID is found. Pass a bus number as an option to this program to go only for that one. Bus 0 doesn't really have an EDID... 256-byte EDID successfully retrieved from i2c bus 4 Looks like i2c was successful. Have a good day. Checksum Correct Section "Monitor" Identifier "ROG PG278QR" ModelName "ROG PG278QR" VendorName "AUS" # Monitor Manufactured week 47 of 2016 # EDID version 1.3 # Digital Display DisplaySize 600 340 Gamma 2.20 Option "DPMS" "false" Horizsync 30-140 VertRefresh 24-60 # Maximum pixel clock is 300MHz #Extension block found. Parsing... Modeline"Mode 1" 148.500 1920 2008 2052 2200 1080 1084 1089 1125 +hsync +vsync Modeline"Mode 0" 241.50 2560 2608 2640 2720 1440 1443 1448 1481 +hsync -vsync Modeline"Mode 2" 148.500 1920 2448 2492 2640 1080 1084 1089 1125 +hsync +vsync Modeline"Mode 3" 74.250 1280 1390 1420 1650 720 725 730 750 +hsync +vsync Modeline"Mode 4" 74.250 1280 1720 1760 1980 720 725 730 750 +hsync +vsync Modeline"Mode 5" 27.027 720 736 798 858 480 489 495 525 -hsync -vsync Modeline"Mode 6" 27.000 720 732 796 864 576 581 586 625 -hsync -vsync Modeline"Mode 7" 25.200 640 656 752 800 480 490 492 525 -hsync -vsync
[Ubuntu-x-swat] [Bug 1901470] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1901470/+attachment/5427741/+files/CurrentDmesg.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/1901470 Title: resolution not listed in xrandr from ASUS ROG PG278QR via HDMI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1901470/+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 1901470] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1901470/+attachment/5427743/+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/1901470 Title: resolution not listed in xrandr from ASUS ROG PG278QR via HDMI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1901470/+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 1901470] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/1901470/+attachment/5427747/+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. https://bugs.launchpad.net/bugs/1901470 Title: resolution not listed in xrandr from ASUS ROG PG278QR via HDMI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1901470/+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 1901470] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1901470/+attachment/5427745/+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/1901470 Title: resolution not listed in xrandr from ASUS ROG PG278QR via HDMI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1901470/+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 1901470] Lsusb-t.txt
apport information ** Attachment added: "Lsusb-t.txt" https://bugs.launchpad.net/bugs/1901470/+attachment/5427746/+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. https://bugs.launchpad.net/bugs/1901470 Title: resolution not listed in xrandr from ASUS ROG PG278QR via HDMI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1901470/+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 1901470] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/1901470/+attachment/5427744/+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. https://bugs.launchpad.net/bugs/1901470 Title: resolution not listed in xrandr from ASUS ROG PG278QR via HDMI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1901470/+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 1901470] MonitorsUser.xml.txt
apport information ** Attachment added: "MonitorsUser.xml.txt" https://bugs.launchpad.net/bugs/1901470/+attachment/5427748/+files/MonitorsUser.xml.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/1901470 Title: resolution not listed in xrandr from ASUS ROG PG278QR via HDMI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1901470/+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 1901470] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1901470/+attachment/5427753/+files/ProcEnviron.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/1901470 Title: resolution not listed in xrandr from ASUS ROG PG278QR via HDMI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1901470/+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 1901470] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1901470/+attachment/5427752/+files/ProcCpuinfoMinimal.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/1901470 Title: resolution not listed in xrandr from ASUS ROG PG278QR via HDMI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1901470/+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 1901470] NvidiaBugReportLog.txt
apport information ** Attachment added: "NvidiaBugReportLog.txt" https://bugs.launchpad.net/bugs/1901470/+attachment/5427749/+files/NvidiaBugReportLog.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/1901470 Title: resolution not listed in xrandr from ASUS ROG PG278QR via HDMI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1901470/+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 1901470] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1901470/+attachment/5427750/+files/ProcCpuinfo.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/1901470 Title: resolution not listed in xrandr from ASUS ROG PG278QR via HDMI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1901470/+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 1901470] XorgLogOld.txt
apport information ** Attachment added: "XorgLogOld.txt" https://bugs.launchpad.net/bugs/1901470/+attachment/5427760/+files/XorgLogOld.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/1901470 Title: resolution not listed in xrandr from ASUS ROG PG278QR via HDMI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1901470/+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 1901470] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1901470/+attachment/5427754/+files/ProcInterrupts.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/1901470 Title: resolution not listed in xrandr from ASUS ROG PG278QR via HDMI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1901470/+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 1901470] XorgLog.txt
apport information ** Attachment added: "XorgLog.txt" https://bugs.launchpad.net/bugs/1901470/+attachment/5427759/+files/XorgLog.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/1901470 Title: resolution not listed in xrandr from ASUS ROG PG278QR via HDMI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1901470/+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 1901470] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1901470/+attachment/5427757/+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/1901470 Title: resolution not listed in xrandr from ASUS ROG PG278QR via HDMI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1901470/+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 1901470] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1901470/+attachment/5427755/+files/ProcModules.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/1901470 Title: resolution not listed in xrandr from ASUS ROG PG278QR via HDMI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1901470/+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 1901470] Xrandr.txt
apport information ** Attachment added: "Xrandr.txt" https://bugs.launchpad.net/bugs/1901470/+attachment/5427761/+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/1901470 Title: resolution not listed in xrandr from ASUS ROG PG278QR via HDMI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1901470/+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 1901470] nvidia-settings.txt
apport information ** Attachment added: "nvidia-settings.txt" https://bugs.launchpad.net/bugs/1901470/+attachment/5427764/+files/nvidia-settings.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/1901470 Title: resolution not listed in xrandr from ASUS ROG PG278QR via HDMI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1901470/+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 1901470] xdpyinfo.txt
apport information ** Attachment added: "xdpyinfo.txt" https://bugs.launchpad.net/bugs/1901470/+attachment/5427765/+files/xdpyinfo.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/1901470 Title: resolution not listed in xrandr from ASUS ROG PG278QR via HDMI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1901470/+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 1901470] acpidump.txt
apport information ** Attachment added: "acpidump.txt" https://bugs.launchpad.net/bugs/1901470/+attachment/5427763/+files/acpidump.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/1901470 Title: resolution not listed in xrandr from ASUS ROG PG278QR via HDMI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1901470/+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 1901470] DpkgLog.txt
apport information ** Attachment added: "DpkgLog.txt" https://bugs.launchpad.net/bugs/1901470/+attachment/5427742/+files/DpkgLog.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/1901470 Title: resolution not listed in xrandr from ASUS ROG PG278QR via HDMI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1901470/+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 1901695] [NEW] Ubuntu 20.04 Suspend resume fails if laptop lid is closed [modeset(G0): failed to set mode: No space left on device] (Razer Blade 15 laptop with nvidia proprietary
You have been subscribed to a public bug: Steps to reproduce: - Boot docked laptop (i.e. lid closed, external monitors connected, USB keyboard plugged in) - Log in, click desktop menu item "Power off / logout -> suspend" - Laptop will suspend - Press key on USB keyboard to resume - Resume fails - external monitor shows black screen with cursor - (this used to work ok in Ubuntu 18.04) Journal shows that Xorg failed: Oct 27 12:06:41 blade /usr/lib/gdm3/gdm-x-session[1595]: (EE) modeset(G0): failed to set mode: No space left on device Oct 27 12:06:41 blade /usr/lib/gdm3/gdm-x-session[1595]: (EE) Oct 27 12:06:41 blade /usr/lib/gdm3/gdm-x-session[1595]: Fatal server error: Oct 27 12:06:41 blade /usr/lib/gdm3/gdm-x-session[1595]: (EE) EnterVT failed for gpu screen 0 Oct 27 12:06:41 blade /usr/lib/gdm3/gdm-x-session[1595]: (EE) Oct 27 12:06:41 blade /usr/lib/gdm3/gdm-x-session[1595]: (EE) Oct 27 12:06:41 blade /usr/lib/gdm3/gdm-x-session[1595]: Please consult the The X.Org Foundation support Oct 27 12:06:41 blade /usr/lib/gdm3/gdm-x-session[1595]: at http://wiki.x.org Oct 27 12:06:41 blade /usr/lib/gdm3/gdm-x-session[1595]: for help. Oct 27 12:06:41 blade /usr/lib/gdm3/gdm-x-session[1595]: (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information. Oct 27 12:06:41 blade /usr/lib/gdm3/gdm-x-session[1595]: (EE) Oct 27 12:06:41 blade /usr/lib/gdm3/gdm-x-session[1595]: (EE) Server terminated with error (1). Closing log file. ** Affects: xorg-server (Ubuntu) Importance: Undecided Status: New -- Ubuntu 20.04 Suspend resume fails if laptop lid is closed [modeset(G0): failed to set mode: No space left on device] (Razer Blade 15 laptop with nvidia proprietary driver) https://bugs.launchpad.net/bugs/1901695 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server 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 1901695] Re: Ubuntu 20.04 Suspend resume fails if laptop lid is closed [modeset(G0): failed to set mode: No space left on device] (Razer Blade 15 laptop with nvidia proprietary dr
** Attachment added: "journal" https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1901695/+attachment/5427808/+files/journal -- 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/1901695 Title: Ubuntu 20.04 Suspend resume fails if laptop lid is closed [modeset(G0): failed to set mode: No space left on device] (Razer Blade 15 laptop with nvidia proprietary driver) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1901695/+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 1901695] [NEW] Ubuntu 20.04 Suspend resume fails if laptop lid is closed [modeset(G0): failed to set mode: No space left on device] (Razer Blade 15 laptop with nvidia proprietary
Public bug reported: Steps to reproduce: - Boot docked laptop (i.e. lid closed, external monitors connected, USB keyboard plugged in) - Log in, click desktop menu item "Power off / logout -> suspend" - Laptop will suspend - Press key on USB keyboard to resume - Resume fails - external monitor shows black screen with cursor - (this used to work ok in Ubuntu 18.04) Journal shows that Xorg failed: Oct 27 12:06:41 blade /usr/lib/gdm3/gdm-x-session[1595]: (EE) modeset(G0): failed to set mode: No space left on device Oct 27 12:06:41 blade /usr/lib/gdm3/gdm-x-session[1595]: (EE) Oct 27 12:06:41 blade /usr/lib/gdm3/gdm-x-session[1595]: Fatal server error: Oct 27 12:06:41 blade /usr/lib/gdm3/gdm-x-session[1595]: (EE) EnterVT failed for gpu screen 0 Oct 27 12:06:41 blade /usr/lib/gdm3/gdm-x-session[1595]: (EE) Oct 27 12:06:41 blade /usr/lib/gdm3/gdm-x-session[1595]: (EE) Oct 27 12:06:41 blade /usr/lib/gdm3/gdm-x-session[1595]: Please consult the The X.Org Foundation support Oct 27 12:06:41 blade /usr/lib/gdm3/gdm-x-session[1595]: at http://wiki.x.org Oct 27 12:06:41 blade /usr/lib/gdm3/gdm-x-session[1595]: for help. Oct 27 12:06:41 blade /usr/lib/gdm3/gdm-x-session[1595]: (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information. Oct 27 12:06:41 blade /usr/lib/gdm3/gdm-x-session[1595]: (EE) Oct 27 12:06:41 blade /usr/lib/gdm3/gdm-x-session[1595]: (EE) Server terminated with error (1). Closing log file. ** Affects: xorg-server (Ubuntu) Importance: Undecided Status: New ** Package changed: gnome-shell (Ubuntu) => xorg-server (Ubuntu) -- 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/1901695 Title: Ubuntu 20.04 Suspend resume fails if laptop lid is closed [modeset(G0): failed to set mode: No space left on device] (Razer Blade 15 laptop with nvidia proprietary driver) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1901695/+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 1901695] Re: Ubuntu 20.04 Suspend resume fails if laptop lid is closed [modeset(G0): failed to set mode: No space left on device] (Razer Blade 15 laptop with nvidia proprietary dr
Sounds somewhat similar to bug #1879893 but it appears that is supposed
to be fixed now.
** Description changed:
Steps to reproduce:
- - Boot docked laptop (i.e. lid closed, external monitors connected, USB
keyboard plugged in)
- - Log in, click desktop menu item "Power off / logout -> suspend"
- - Laptop will suspend
- - Press key on USB keyboard to resume
- - Resume fails - external monitor shows black screen with cursor
- - (this used to work ok in Ubuntu 18.04)
+ - Boot docked laptop (i.e. lid closed, external monitors connected, USB
keyboard plugged in)
+ - Log in, click desktop menu item "Power off / logout -> suspend"
+ - Laptop will suspend
+ - Press key on USB keyboard to resume
+ - Resume fails - external monitor shows black screen with cursor
+ - (this used to work ok in Ubuntu 18.04)
Journal shows that Xorg failed:
+ Oct 27 12:06:37 blade /usr/lib/gdm3/gdm-x-session[2125]: (--) NVIDIA(GPU-0):
DELL 2209WA (DFP-0): connected
+ Oct 27 12:06:37 blade /usr/lib/gdm3/gdm-x-session[2125]: (--) NVIDIA(GPU-0):
DELL 2209WA (DFP-0): Internal TMDS
+ Oct 27 12:06:37 blade /usr/lib/gdm3/gdm-x-session[2125]: (--) NVIDIA(GPU-0):
DELL 2209WA (DFP-0): 165.0 MHz maximum pixel clock
+ Oct 27 12:06:37 blade /usr/lib/gdm3/gdm-x-session[2125]: (--) NVIDIA(GPU-0):
+ Oct 27 12:06:37 blade /usr/lib/gdm3/gdm-x-session[2125]: (--) NVIDIA(GPU-0):
DFP-1: disconnected
+ Oct 27 12:06:37 blade /usr/lib/gdm3/gdm-x-session[2125]: (--) NVIDIA(GPU-0):
DFP-1: Internal DisplayPort
+ Oct 27 12:06:37 blade /usr/lib/gdm3/gdm-x-session[2125]: (--) NVIDIA(GPU-0):
DFP-1: 1440.0 MHz maximum pixel clock
+ Oct 27 12:06:37 blade /usr/lib/gdm3/gdm-x-session[2125]: (--) NVIDIA(GPU-0):
+ Oct 27 12:06:37 blade /usr/lib/gdm3/gdm-x-session[2125]: (--) NVIDIA(GPU-0):
DELL 2209WA (DFP-2): connected
+ Oct 27 12:06:37 blade /usr/lib/gdm3/gdm-x-session[2125]: (--) NVIDIA(GPU-0):
DELL 2209WA (DFP-2): Internal TMDS
+ Oct 27 12:06:37 blade /usr/lib/gdm3/gdm-x-session[2125]: (--) NVIDIA(GPU-0):
DELL 2209WA (DFP-2): 165.0 MHz maximum pixel clock
+ Oct 27 12:06:37 blade /usr/lib/gdm3/gdm-x-session[2125]: (--) NVIDIA(GPU-0):
+ Oct 27 12:06:37 blade /usr/lib/gdm3/gdm-x-session[2125]: (II) NVIDIA(0):
Setting mode "HDMI-0: nvidia-auto-select @1050x1680 +2102+0
{ViewPortIn=1050x1680, ViewPortOut=1680x1050+0+0, Rotation=90}, DP-1:
nvidia-auto-select @1050x1680 +1050+0 {ViewPortIn=1050x1680,
ViewPortOut=1680x1050+0+0, Rotation=90}"
+ ...
Oct 27 12:06:41 blade /usr/lib/gdm3/gdm-x-session[1595]: (EE) modeset(G0):
failed to set mode: No space left on device
Oct 27 12:06:41 blade /usr/lib/gdm3/gdm-x-session[1595]: (EE)
Oct 27 12:06:41 blade /usr/lib/gdm3/gdm-x-session[1595]: Fatal server error:
Oct 27 12:06:41 blade /usr/lib/gdm3/gdm-x-session[1595]: (EE) EnterVT failed
for gpu screen 0
Oct 27 12:06:41 blade /usr/lib/gdm3/gdm-x-session[1595]: (EE)
Oct 27 12:06:41 blade /usr/lib/gdm3/gdm-x-session[1595]: (EE)
Oct 27 12:06:41 blade /usr/lib/gdm3/gdm-x-session[1595]: Please consult the
The X.Org Foundation support
Oct 27 12:06:41 blade /usr/lib/gdm3/gdm-x-session[1595]: at
http://wiki.x.org
Oct 27 12:06:41 blade /usr/lib/gdm3/gdm-x-session[1595]: for help.
Oct 27 12:06:41 blade /usr/lib/gdm3/gdm-x-session[1595]: (EE) Please also
check the log file at "/var/log/Xorg.0.log" for additional information.
Oct 27 12:06:41 blade /usr/lib/gdm3/gdm-x-session[1595]: (EE)
Oct 27 12:06:41 blade /usr/lib/gdm3/gdm-x-session[1595]: (EE) Server
terminated with error (1). Closing log 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/1901695
Title:
Ubuntu 20.04 Suspend resume fails if laptop lid is closed
[modeset(G0): failed to set mode: No space left on device] (Razer
Blade 15 laptop with nvidia proprietary driver)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1901695/+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
** Changed in: mutter (Ubuntu Focal) Assignee: (unassigned) => Daniel van Vugt (vanvugt) -- 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 1901694] [NEW] No hardware aceleration
You have been subscribed to a public bug: Computer HP EliteBook 8460p. It uses hybrid graphics card. Processor Intel Core i5-2520M CPU @ 2.50GHz × 4; 2nd generation. The system only runs well with llvmpipe (LLVM 6.0, 256 bits) graphic software, AMD Caicos sometimes it's charged too, but the graphic display have problems and don't goes fine or fluid. Maybe there is no support for the processor graphics because It's a little bit old. I don't know how to install AMD proprietary drivers, It maybe solve the problem. I installed Ubuntu 20.04 LTS but don't works, It don't charge any graphic interface, only a black screen. I only uses the system in recovery mode. For that reason I returned to Ubuntu 16.04 LTS but my graphics don't have hardware acceleration, only software acceleration. When I tried to play (Super Tux Kart for example) I expected a berry poor graphic improvement, so I can't play It. Thanks for your time and attention! ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3.1 ProcVersionSignature: Ubuntu 4.15.0-122.124~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-122-generic x86_64 .tmp.unity_support_test.1: ApportVersion: 2.20.1-0ubuntu2.24 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Tue Oct 27 05:47:39 2020 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Seymour [Radeon HD 6400M/7400M Series] [1002:6760] (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Radeon HD 6470M [103c:161e] InstallationDate: Installed on 2020-10-25 (1 days ago) InstallationMedia: Ubuntu 16.04.7 LTS "Xenial Xerus" - Release amd64 (20200806) MachineType: Hewlett-Packard HP EliteBook 8460p ProcEnviron: LANGUAGE=es_CR:es PATH=(custom, no user) LANG=es_CR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-122-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 Renderer: Software SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/12/2015 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68SCF Ver. F.60 dmi.board.name: 161C dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 97.4E dmi.chassis.asset.tag: IS09189 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68SCFVer.F.60:bd03/12/2015:svnHewlett-Packard:pnHPEliteBook8460p:pvrA0001D02:rvnHewlett-Packard:rn161C:rvrKBCVersion97.4E:cvnHewlett-Packard:ct10:cvr: dmi.product.family: 103C_5336AN dmi.product.name: HP EliteBook 8460p dmi.product.version: A0001D02 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.91-2~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Tue Oct 27 05:43:49 2020 xserver.configfile: default xserver.errors: AIGLX: reverting to software rendering xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.6-1ubuntu4.1~16.04.4 xserver.video_driver: radeon ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 ubuntu xenial -- No hardware aceleration https://bugs.launchpad.net/bugs/1901694 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg 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 1901694] Re: No hardware aceleration
** 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/1901694 Title: No hardware aceleration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1901694/+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 1878293] Re: xterm resize is wonky
Hello John, or anyone else affected, Accepted mutter into groovy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/mutter/3.38.1-2ubuntu1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- groovy to verification-done-groovy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-groovy. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: mutter (Ubuntu Groovy) Status: New => Fix Committed ** Tags added: verification-needed verification-needed-groovy -- 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/1878293 Title: xterm resize is wonky To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1878293/+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 1897185] Re: Laptop docked with lid closed, goes to sleep immediately on login
Daniel, this seems consistent: so long as I don't load the Dropbox app, I haven't seen the suspend. I don't know if this is the cause but regardless the Dropbox app may help in reproducing this issue? Thanks... -- 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/1897185 Title: Laptop docked with lid closed, goes to sleep immediately on login To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1897185/+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 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05
The standalone patch #217 is working for MSFT0001:00 04F3:3140 but isn't working perfectly for MSFT0001:00 06CB:7F28. The MSFT0001:00 06CB:7F28 touchpad frequently locks into scroll mode when using multitouch gestures. -- 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/1887190 Title: MSFT Touchpad not working on Lenovo Legion-5 15ARH05 To manage notifications about this bug go to: https://bugs.launchpad.net/pop-os/+bug/1887190/+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 1901736] [NEW] Xorg freeze
You have been subscribed to a public bug: Most of the time Ubuntu boots the dock seems to freeze and not load any icons, sometimes for up to a minute. When this happens the dock will not appear when any window is maximized. Once in a while Ubuntu loads without a problem. The dock loads instantly and has no problem behind a maximized window. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.10 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Oct 27 12:35:14 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Iris Plus Graphics 640 [8086:5926] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation Iris Plus Graphics 640 [8086:2068] InstallationDate: Installed on 2020-09-16 (41 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Intel(R) Client Systems NUC7i5BNK ProcEnviron: LANGUAGE=en_CA:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-52-generic root=UUID=50f7562f-c44b-4a47-b1b4-02bdd6281c08 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/25/2019 dmi.bios.vendor: Intel Corp. dmi.bios.version: BNKBL357.86A.0080.2019.0725.1139 dmi.board.name: NUC7i5BNB dmi.board.vendor: Intel Corporation dmi.board.version: J31144-314 dmi.chassis.type: 35 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnIntelCorp.:bvrBNKBL357.86A.0080.2019.0725.1139:bd07/25/2019:svnIntel(R)ClientSystems:pnNUC7i5BNK:pvrJ31159-315:rvnIntelCorporation:rnNUC7i5BNB:rvrJ31144-314:cvnIntelCorporation:ct35:cvr2.0: dmi.product.family: BN dmi.product.name: NUC7i5BNK dmi.product.version: J31159-315 dmi.sys.vendor: Intel(R) Client Systems version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug false-gpu-hang focal freeze ubuntu wayland-session -- Xorg freeze https://bugs.launchpad.net/bugs/1901736 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg 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 1901736] Re: Xorg freeze
** 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/1901736 Title: Xorg freeze To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1901736/+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 1901342] Re: Xorg sessions fail to start on Intel Core 2 T5800: modeset(0): drmSetMaster failed: Permission denied
Yes - "after login" means after I have successfully entered my password. Also, I have not been able to locate the 'Ubuntu on Wayland' selection. -- 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/1901342 Title: Xorg sessions fail to start on Intel Core 2 T5800: modeset(0): drmSetMaster failed: Permission denied To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1901342/+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 1550779] Re: Black screen flickering and [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun
** No longer affects: xorg-server (Ubuntu) -- 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/1550779 Title: Black screen flickering and [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1550779/+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 1901342] Re: Xorg sessions fail to start on Intel Core 2 T5800: modeset(0): drmSetMaster failed: Permission denied
** Changed in: gdm3 (Ubuntu) Status: Incomplete => New ** Changed in: mutter (Ubuntu) Status: Incomplete => New ** Changed in: xorg-server (Ubuntu) Status: Incomplete => New -- 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/1901342 Title: Xorg sessions fail to start on Intel Core 2 T5800: modeset(0): drmSetMaster failed: Permission denied To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1901342/+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 1901470] Re: resolution not listed in xrandr from ASUS ROG PG278QR via HDMI
Yep, the detailed mode 2560x1440 is in the EDID returned by the monitor: Standard Timings: none Detailed mode: Clock 241.500 MHz, 598 mm x 336 mm 2560 2608 2640 2720 ( 48 32 80) 1440 1443 1448 1481 ( 3 5 33) +hsync -vsync VertFreq: 59.951 Hz, HorFreq: 88.787 kHz Display Product Serial Number: GBLMQS047683 Display Range Limits Monitor ranges (Bare Limits): 24-60 Hz V, 30-140 kHz H, max dotclock 300 MHz Display Product Name: ROG PG278QR -- 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/1901470 Title: resolution not listed in xrandr from ASUS ROG PG278QR via HDMI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1901470/+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 1901470] Re: resolution not listed in xrandr from ASUS ROG PG278QR via HDMI
I would like to check to see if the problem is occurring in the kernel and not just in Xorg. Please run: grep . /sys/class/drm/*/modes > modes.txt and then attach the resulting text file 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/1901470 Title: resolution not listed in xrandr from ASUS ROG PG278QR via HDMI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1901470/+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 1901694] Re: [radeon] No hardware aceleration
It appears the Xorg radeon driver is working. It's only 3D that's not working so that's Mesa. ** Summary changed: - No hardware aceleration + [radeon] No hardware aceleration ** Summary changed: - [radeon] No hardware aceleration + [radeon] No hardware acceleration ** Tags added: radeon ** Package changed: xorg (Ubuntu) => mesa (Ubuntu) ** Summary changed: - [radeon] No hardware acceleration + [radeon] No hardware acceleration on AMD Seymour [Radeon HD 6400M/7400M Series] -- 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/1901694 Title: [radeon] No hardware acceleration on AMD Seymour [Radeon HD 6400M/7400M Series] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1901694/+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 1901695] Re: Ubuntu 20.04 Suspend resume fails if laptop lid is closed [modeset(G0): failed to set mode: No space left on device] (Razer Blade 15 laptop with nvidia proprietary dr
*** This bug is a duplicate of bug 1791981 *** https://bugs.launchpad.net/bugs/1791981 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1791981, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** Tags added: focal ** This bug has been marked a duplicate of bug 1791981 X Server session crash with "No space left on device" and then "EnterVT failed for gpu screen 0" -- 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/1901695 Title: Ubuntu 20.04 Suspend resume fails if laptop lid is closed [modeset(G0): failed to set mode: No space left on device] (Razer Blade 15 laptop with nvidia proprietary driver) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1901695/+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 1791981] Re: X Server session crash with "No space left on device" and then "EnterVT failed for gpu screen 0"
** Summary changed: - X Server session crash for "No space left on device" + X Server session crash with "No space left on device" and then "EnterVT failed for gpu screen 0" ** Summary changed: - X Server session crash with "No space left on device" and then "EnterVT failed for gpu screen 0" + [nvidia] X Server session crash with "No space left on device" and then "EnterVT failed for gpu screen 0" -- 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/1791981 Title: [nvidia] X Server session crash with "No space left on device" and then "EnterVT failed for gpu screen 0" To manage notifications about this bug go to: https://bugs.launchpad.net/nvidia/+bug/1791981/+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 1276804] Re: Xorg crashed with SIGABRT in OsAbort(no screens found?)
Thank you for reporting this bug to Ubuntu.
Ubuntu GNOME 14.04 (trusty) reached end-of-life on April 28, 2017
https://wiki.ubuntu.com/TrustyTahr/ReleaseNotes/UbuntuGNOME#Support
https://lists.ubuntu.com/archives/ubuntu-gnome/2017-March/004211.html
We appreciate that this bug may be old and you might not be interested
in discussing it any more. But if you are then please upgrade to the
latest Ubuntu version and re-test. If you then find the bug is still
present in the newer Ubuntu version, please add a comment here telling
us which new version it is in.
** This bug is no longer a duplicate of bug 1543192
Xorg crashed with SIGABRT in OsAbort() from AbortServer() from
FatalError("EnterVT failed for gpu screen %d\n") from xf86VTEnter() from
WakeupHandler()
--
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/1276804
Title:
Xorg crashed with SIGABRT in OsAbort(no screens found?)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1276804/+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 1276804] Re: Xorg crashed with SIGABRT in OsAbort(no screens found?)
Ubuntu 14.04 reached end of standard support in April 2019: https://wiki.ubuntu.com/Releases If you would like to continue with free support then please update to a newer Ubuntu version and tell us if the problem still occurs. If you would like to continue with Ubuntu 14.04 then there is a paid support option detailed at https://www.ubuntu.com/esm ** Changed in: xorg-server (Ubuntu) Status: New => Won't Fix -- 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/1276804 Title: Xorg crashed with SIGABRT in OsAbort(no screens found?) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1276804/+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 1858351] Re: Xorg crashed with SIGABRT in raise() from abort() from OsAbort() from AbortServer() from FatalError("no screens found")
*** This bug is a duplicate of bug 1813897 ***
https://bugs.launchpad.net/bugs/1813897
** This bug is no longer a duplicate of bug 1543192
Xorg crashed with SIGABRT in OsAbort() from AbortServer() from FatalError()
from dix_main()
** Summary changed:
- Xorg crashed with SIGABRT in raise() from abort() from OsAbort() from
AbortServer() from FatalError("no screens found")
+ Xorg crashed with SIGABRT in raise() from abort() from OsAbort() from
AbortServer() from FatalError() from InitOutput()
** Summary changed:
- Xorg crashed with SIGABRT in raise() from abort() from OsAbort() from
AbortServer() from FatalError() from InitOutput()
+ Xorg crashed with SIGABRT in raise() from abort() from OsAbort() from
AbortServer() from FatalError("AddScreen/ScreenInit failed for driver %d\n")
from InitOutput()
** This bug has been marked a duplicate of bug 1813897
Xorg crashed with SIGABRT in OsAbort() from AbortServer() from
FatalError("AddScreen/ScreenInit failed for driver %d\n")
--
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/1858351
Title:
Xorg crashed with SIGABRT in raise() from abort() from OsAbort() from
AbortServer() from FatalError("AddScreen/ScreenInit failed for driver
%d\n") from InitOutput()
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1858351/+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 1543192] Re: Xorg crashed with SIGABRT in OsAbort() from AbortServer() from FatalError("EnterVT failed for gpu screen %d\n") from xf86VTEnter() from WakeupHandler()
I think this is the wrong bug for all of those duplicates. There's no
evidence of either of those messages here. I'll see if I can split this
into other bugs...
** Summary changed:
- Xorg crashed with SIGABRT in OsAbort() from AbortServer() from
FatalError("EnterVT failed for gpu screen %d\n") from xf86VTEnter() from
WakeupHandler()
+ Xorg crashed with SIGABRT in OsAbort() from AbortServer() from FatalError
** Summary changed:
- Xorg crashed with SIGABRT in OsAbort() from AbortServer() from FatalError
+ Xorg crashed with SIGABRT in OsAbort() from AbortServer() from FatalError()
from dix_main()
** Description changed:
https://errors.ubuntu.com/problem/4de849dfec89af168af9cda3318221a2a654e530
- https://errors.ubuntu.com/problem/4c203db78dea0a68c29cbd981d4abbd4aef31851
---
No idea what happened.
ProblemType: Crash
DistroRelease: Ubuntu 16.04
Package: xserver-xorg-core 2:1.17.3-2ubuntu2
ProcVersionSignature: Ubuntu 4.4.0-2.16-generic 4.4.0
Uname: Linux 4.4.0-2-generic x86_64
.tmp.unity.support.test.0:
ApportVersion: 2.19.4-0ubuntu2
Architecture: amd64
CompizPlugins: No value set for
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CrashCounter: 1
Date: Mon Feb 8 17:07:23 2016
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
ExecutablePath: /usr/lib/xorg/Xorg
ExtraDebuggingInterest: Yes
GraphicsCard:
Intel Corporation 2nd Generation Core Processor Family Integrated Graphics
Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller])
Subsystem: Lenovo 2nd Generation Core Processor Family Integrated Graphics
Controller [17aa:21da]
InstallationDate: Installed on 2015-04-30 (283 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
MachineType: LENOVO 429149G
ProcCmdline: /usr/lib/xorg/Xorg -core :0 -seat seat0 -auth
/var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
ProcEnviron:
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-2-generic
root=UUID=457973fc-512e-4b6a-b65b-85f15fa85b7b ro console=tty1 console=ttyS0
panic=-1
Signal: 6
SourcePackage: xorg-server
StacktraceTop:
OsAbort ()
?? ()
FatalError ()
?? ()
__libc_start_main (main=0x557f8180ff00, argc=11, argv=0x7fffc9e34fd8,
init=, fini=, rtld_fini=,
stack_end=0x7fffc9e34fc8) at libc-start.c:289
SystemImageInfo: Error: command ['system-image-cli', '-i'] failed with exit
code 2:
Title: Xorg crashed with SIGABRT in OsAbort()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
dmi.bios.date: 05/18/2011
dmi.bios.vendor: LENOVO
dmi.bios.version: 8DET46WW (1.16 )
dmi.board.asset.tag: Not Available
dmi.board.name: 429149G
dmi.board.vendor: LENOVO
dmi.board.version: Not Available
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias:
dmi:bvnLENOVO:bvr8DET46WW(1.16):bd05/18/2011:svnLENOVO:pn429149G:pvrThinkPadX220:rvnLENOVO:rn429149G:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 429149G
dmi.product.version: ThinkPad X220
dmi.sys.vendor: LENOVO
version.compiz: compiz 1:0.9.12.2+16.04.20151211-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.66-2
version.libgl1-mesa-dri: libgl1-mesa-dri 11.1.1-1ubuntu2
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 11.1.1-1ubuntu2
version.xserver-xorg-core: xserver-xorg-core 2:1.17.3-2ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.6.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel
2:2.99.917+git20160127-1ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1
xserver.bootTime: Mon Feb 8 17:08:14 2016
xserver.configfile: default
xserver.errors: systemd-logind: failed to get session: PID 9847 does not
belong to any known session
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
product id 728
vendor LGD
xserver.version: 2:1.17.3-2ubuntu2
--
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/1543192
Title:
Xorg crashed with SIGABRT in OsAbort() from AbortServer() from
FatalError("no screens found") from dix_main()
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1543192/+subscriptions
___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swa
[Ubuntu-x-swat] [Bug 1545103] Re: Xorg crashed with SIGABRT in raise()
There's not enough information here to tell which FatalError this is. ** This bug is no longer a duplicate of bug 1543192 Xorg crashed with SIGABRT in OsAbort() from AbortServer() from FatalError() from dix_main() ** 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-server in Ubuntu. https://bugs.launchpad.net/bugs/1545103 Title: Xorg crashed with SIGABRT in raise() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1545103/+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 1545158] Re: Xorg crashed with SIGABRT in OsAbort() from ?? from FatalError("no screens found")
*** This bug is a duplicate of bug 1543192 ***
https://bugs.launchpad.net/bugs/1543192
** Summary changed:
- Xorg crashed with SIGABRT in OsAbort()
+ Xorg crashed with SIGABRT in OsAbort() from ?? from FatalError("no screens
found")
--
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/1545158
Title:
Xorg crashed with SIGABRT in OsAbort() from ?? from FatalError("no
screens found")
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1545158/+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 1543141] Re: Xorg crashed with SIGABRT in OsAbort()
There's not enough information here to tell which FatalError this is. ** This bug is no longer a duplicate of bug 1543192 Xorg crashed with SIGABRT in OsAbort() from AbortServer() from FatalError() from dix_main() ** 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-server in Ubuntu. https://bugs.launchpad.net/bugs/1543141 Title: Xorg crashed with SIGABRT in OsAbort() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1543141/+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 1544252] Re: Xorg crashed with SIGABRT in OsAbort()
I can't see any evidence of which Xorg crash this is. ** This bug is no longer a duplicate of bug 1543192 Xorg crashed with SIGABRT in OsAbort() from AbortServer() from FatalError() from dix_main() ** 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-server in Ubuntu. https://bugs.launchpad.net/bugs/1544252 Title: Xorg crashed with SIGABRT in OsAbort() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1544252/+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 1543706] Re: Xorg crashed with SIGABRT in OsAbort()
I can't tell *which* FatalError this is. ** This bug is no longer a duplicate of bug 1543192 Xorg crashed with SIGABRT in OsAbort() from AbortServer() from FatalError() from dix_main() ** 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-server in Ubuntu. https://bugs.launchpad.net/bugs/1543706 Title: Xorg crashed with SIGABRT in OsAbort() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1543706/+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 1791981] Re: [nvidia] X Server session crash with "No space left on device" and then "EnterVT failed for gpu screen 0"
It looks like bug 1897530 might cover this but it's unclear. The fix for that is only in Ubuntu 20.10 so far. -- 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/1791981 Title: [nvidia] X Server session crash with "No space left on device" and then "EnterVT failed for gpu screen 0" To manage notifications about this bug go to: https://bugs.launchpad.net/nvidia/+bug/1791981/+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 1787332] Re: Xorg crashed with SIGABRT in OsAbort() from AbortServer() from FatalError("EnterVT failed for screen %d\n") from xf86VTEnter() from systemd_logind_vtenter()
** Summary changed:
- Xorg crashed with SIGABRT in OsAbort() from AbortServer() from
FatalError("EnterVT failed for screen ...") from xf86VTEnter() from
systemd_logind_vtenter()
+ Xorg crashed with SIGABRT in OsAbort() from AbortServer() from
FatalError("EnterVT failed for screen %d\n") from xf86VTEnter() from
systemd_logind_vtenter()
--
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/1787332
Title:
Xorg crashed with SIGABRT in OsAbort() from AbortServer() from
FatalError("EnterVT failed for screen %d\n") from xf86VTEnter() from
systemd_logind_vtenter()
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1787332/+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 1543192] Re: Xorg crashed with SIGABRT in OsAbort() from AbortServer() from FatalError("no screens found") from dix_main()
OK, clarified somewhat now. This bug is back to being about just "no
screens found".
** Summary changed:
- Xorg crashed with SIGABRT in OsAbort() from AbortServer() from FatalError()
from dix_main()
+ Xorg crashed with SIGABRT in OsAbort() from AbortServer() from FatalError("no
screens found") from dix_main()
--
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/1543192
Title:
Xorg crashed with SIGABRT in OsAbort() from AbortServer() from
FatalError("no screens found") from dix_main()
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1543192/+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 1901736] Re: Freeze
This sounds like either bug 1896110 or bug 1874578. Do you think? ** Summary changed: - Xorg freeze + Freeze ** Package changed: xorg (Ubuntu) => gnome-shell-extension-ubuntu-dock (Ubuntu) ** Changed in: gnome-shell-extension-ubuntu-dock (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/1901736 Title: Freeze To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1901736/+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 1901342] Re: Xorg sessions fail to start on Intel Core 2 T5800: modeset(0): drmSetMaster failed: Permission denied
you're using 'nomodeset' boot option which disables things, don't do that -- 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/1901342 Title: Xorg sessions fail to start on Intel Core 2 T5800: modeset(0): drmSetMaster failed: Permission denied To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1901342/+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 1901342] Re: Xorg sessions fail to start on Intel Core 2 T5800: modeset(0): drmSetMaster failed: Permission denied
No they're not really. That's just recovery mode, required to log this bug. -- 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/1901342 Title: Xorg sessions fail to start on Intel Core 2 T5800: modeset(0): drmSetMaster failed: Permission denied To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1901342/+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 1901694] Re: [radeon] No hardware acceleration on AMD Seymour [Radeon HD 6400M/7400M Series]
[39.611] (II) AIGLX: Screen 0 is not DRI2 capable [39.611] (EE) AIGLX: reverting to software rendering 16.04 is just old and you're not getting any (gfx) updates there anymore at this point -- 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/1901694 Title: [radeon] No hardware acceleration on AMD Seymour [Radeon HD 6400M/7400M Series] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1901694/+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 1901808] [NEW] no acceleration on Intel HD 4400
Public bug reported: I have laptop dell with intel i5-4100U, intel hd 4400 and geforce 820m on board. I added zotac gtx 960 and one monitor via rizer. gtx and monitor worked correctly. but laptop displays has lags and tearing. I tried install i915 i965-va-drivers intel config section Section "Device" Identifier "Device1" Driver "intel" VendorName "Intel Corporation" Option "TearFree" "true" Option "DRI" "2" EndSection ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/gpu0' .proc.driver.nvidia.capabilities.mig: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/mig' .proc.driver.nvidia.gpus..06.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:06:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 455.32.00 Wed Oct 14 22:46:18 UTC 2020 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04) ApportVersion: 2.20.11-0ubuntu27.10 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: Deepin Date: Wed Oct 28 11:03:01 2020 DistUpgraded: 2020-08-20 21:43:47,424 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: No GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 0b) (prog-if 00 [VGA controller]) Subsystem: Dell Haswell-ULT Integrated Graphics Controller [1028:0652] NVIDIA Corporation GM206 [GeForce GTX 960] [10de:1401] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ZOTAC International (MCO) Ltd. GM206 [GeForce GTX 960] [19da:2378] Subsystem: Dell GeForce 820M [1028:0652] InstallationDate: Installed on 2020-07-16 (103 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) MachineType: Dell Inc. Inspiron 3542 ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.4.0-52-generic root=UUID=ab9e3a31-2ad4-4c5f-a786-92ff7dbde56d ro rootflags=subvol=@ nouveau.modeset=0 DEEPIN_GFXMODE= crashkernel=512M-:192M SourcePackage: xorg UpgradeStatus: Upgraded to focal on 2020-08-20 (68 days ago) dmi.bios.date: 03/28/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A01 dmi.board.name: 0926J6 dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA01:bd03/28/2014:svnDellInc.:pnInspiron3542:pvrNotSpecified:rvnDellInc.:rn0926J6:rvrA01:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Inspiron 3542 dmi.product.sku: 0652 dmi.product.version: Not Specified dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1 version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~20.04.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal third-party-packages 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/1901808 Title: no acceleration on Intel HD 4400 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1901808/+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
