[Bug 1901470] Re: [modeset][i915] Native resolution (EDID detailed mode) of 2560x1440 not listed, defaults to 1920x1080 instead
Follow post of a work around that automatically enables the resolution I want. I added a file named: 45custom_xrandr_settings in folder: /etc/X11/Xsession.d containing: xrandr --newmode "Mode 0" 241.50 2560 2608 2640 2720 1440 1443 1448 1481 +hsync -vsync xrandr --addmode HDMI-1-1 "Mode 0" This will cause X11 to use the 2560x1440 resolution after reboot. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901470 Title: [modeset][i915] Native resolution (EDID detailed mode) of 2560x1440 not listed, defaults to 1920x1080 instead To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1901470/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901470] Re: resolution not listed in xrandr from ASUS ROG PG278QR via HDMI
output from: grep . /sys/class/drm/*/modes > modes.txt ** Attachment added: "modes.txt" https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1901470/+attachment/5428462/+files/modes.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to 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 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Bugs, which is subscribed to 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 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Bugs, which is subscribed to 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 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Bugs, which is subscribed to 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 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Bugs, which is subscribed to 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 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Bugs, which is subscribed to 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 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Bugs, which is subscribed to 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 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Bugs, which is subscribed to 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 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Bugs, which is subscribed to 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 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Bugs, which is subscribed to 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 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Bugs, which is subscribed to 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 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Bugs, which is subscribed to 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 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Bugs, which is subscribed to 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 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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
[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 Bugs, which is subscribed to 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 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Bugs, which is subscribed to 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 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Bugs, which is subscribed to 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 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Bugs, which is subscribed to 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 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Bugs, which is subscribed to 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 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Bugs, which is subscribed to 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 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Bugs, which is subscribed to 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 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Bugs, which is subscribed to 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 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Bugs, which is subscribed to 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 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901470] Re: resolution not listed in xrandr from ASUS ROG PG278QR via HDMI
** Attachment added: "after xrandr --addmode" https://bugs.launchpad.net/ubuntu/+bug/1901470/+attachment/5427131/+files/Screenshot%20from%202020-10-26%2013-23-41.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to 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/+bug/1901470/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901470] [NEW] resolution not listed in xrandr from ASUS ROG PG278QR via HDMI
Public bug reported: 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 Option "PreferredMode" "Mode 1" EndSection "Mode 0" above is the mode that I want to use, which doesn't appear in the Settings app list of available resolutions. I used "Mode 0" to via xrandr --newmode: ~$ xrandr --newmode "Mode 0" 241.50 2560 2608 2640
[Bug 1189639] Re: [dp] External Screen doesn't wake up from sleep
This issue affects me as well. Lenovo T460 and a Lenovo basic docking station. The docking station is connected to an Acer 24" monitor via VGA. Once the desktop locks and the unity login appears the external display enters power save mode. Unlocking via the password does not power up the external display (all windows are moved to laptop display). I have to eject the laptop from the dock, wait a couple of seconds, then put the laptop back in the dock for the external display to power back up. I'd prefer not to physically undock/dock the laptop several times a day. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1189639 Title: [dp] External Screen doesn't wake up from sleep To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1189639/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1596154] [NEW] Attempted to re-install from sd-card
Public bug reported: I did a fresh erase install over an old Mac OS X installation on a Core 2 Duo MacBook Pro. I didn't have the ethernet cable connected at the time. The download updates check box was grayed out. The installation completed. I logged in and noticed that I couldn't configure the wifi network via the System Settings panel. I realized that installation probably needed to download a BroadCom 3rd Party binary package. I figured that I didn't really configure anything, or have anything to loose, so I decided to connect the Ethernet cable and re-install Ubuntu. After option-boot into the SD card, the media I used for the initial installation as well, a radio box selection appears, including "Re- install Ubuntu 16 LTS only" or something along those lines. It said it would use as much of the existing system as possible and leave the home directories. I figured, that sounds like what I want. (It was also the first option.) That started along, but then complained that there wasn't an EFI partition for boot loader and it said this is not the same as the /boot partition. So I added a EFI System Partition in some free space of 134MB towards the end of the drive. Then it complained about two partitions that will mount in /boot and to change the mount point of one of them. The new partition that I made did not have a mount point in the list. Didn't get past that. Then it ended up back in the radio box selection for which type of installation to perform. I selected the next one on the list, Erase and Install. It re-partitioned and then I selected the option to download updates while installing. Then the installation failed. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: ubiquity 2.21.63 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CasperVersion: 1.376 Date: Sat Jun 25 06:33:42 2016 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi file=/cdrom/preseed/ubuntu.seed boot=casper only-ubiquity quiet splash --- LiveMediaBuild: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug ubiquity-2.21.63 ubuntu xenial ** Attachment added: "/var/log/syslog" https://bugs.launchpad.net/bugs/1596154/+attachment/4690028/+files/syslog -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1596154 Title: Attempted to re-install from sd-card To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1596154/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1426542] [NEW] nvidia-331 331.113-0ubuntu0.1: nvidia-331 kernel module failed to build
Public bug reported: Happens every time I turn on the computer ProblemType: Package DistroRelease: Ubuntu 14.10 Package: nvidia-331 331.113-0ubuntu0.1 ProcVersionSignature: Ubuntu 3.16.0-31.41-generic 3.16.7-ckt5 Uname: Linux 3.16.0-31-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.7-0ubuntu8.2 Architecture: amd64 DKMSKernelVersion: 3.16.0-31-generic Date: Thu Feb 26 15:05:36 2015 InstallationDate: Installed on 2014-10-18 (132 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) PackageVersion: 331.113-0ubuntu0.1 SourcePackage: nvidia-graphics-drivers-331 Title: nvidia-331 331.113-0ubuntu0.1: nvidia-331 kernel module failed to build UpgradeStatus: Upgraded to utopic on 2014-10-24 (126 days ago) modified.conffile..etc.modprobe.d.nvidia.331.hybrid.conf: [deleted] ** Affects: nvidia-graphics-drivers-331 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package third-party-packages utopic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1426542 Title: nvidia-331 331.113-0ubuntu0.1: nvidia-331 kernel module failed to build To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1426542/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1315462] [NEW] virtio-scsi not packaged in Precise installer kernel
Public bug reported: I'm trying to install Precise on a QEMU VM using the virtio-scsi driver. The guest kernel driver, module virtio-scsi, doesn't seem to be included, so my guest has no hard drives. I think this should be packaged in the virtio-modules udeb. The LTS kernel package has the module, so once Precise installs it should work fine. mwharris@mwharris-glaptop:~/Downloads$ dpkg-deb --contents virtio-modules-3.11.0-18-generic-di_3.11.0-18.32~precise1_amd64.udeb | grep virtio_sci mwharris@mwharris-glaptop:~/Downloads$ The newer Trusty installer has it though: mwharris@mwharris-glaptop:~/Downloads$ dpkg-deb --contents virtio-modules-3.13.0-24-generic-di_3.13.0-24.46_amd64.udeb | grep virtio_scsi -rw-r--r-- root/root 28044 2014-04-10 13:19 ./lib/modules/3.13.0-24-generic/kernel/drivers/scsi/virtio_scsi.ko mwharris@mwharris-glaptop:~/Downloads$ ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1315462 Title: virtio-scsi not packaged in Precise installer kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1315462/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1315462] Re: virtio-scsi not packaged in Precise installer kernel
This is an installer bug, there's no apport-collect when it breaks. Marking as confirmed. ** Changed in: linux (Ubuntu) Status: Incomplete = Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1315462 Title: virtio-scsi not packaged in Precise installer kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1315462/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1287401] Re: please include virtio-scsi in linux-virtual
Can this fix be applied to Precise as well? At least to the most recent backport kernel? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1287401 Title: please include virtio-scsi in linux-virtual To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1287401/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1257962] [NEW] qemu needs at least version 1.3.0-3 of libfdt-dev to build
Public bug reported: I'm backporting QEMU from Trusty to Precise, and I've exposed a build dependency problem. The library libfdt-dev had a bug with version before 1.3.0-3 preventing it from being used. See the changelog: device-tree-compiler (1.3.0-3) unstable; urgency=low * libfdt-dev: Missing header file prevents the library usage Thanks Domenico Andreoli (Closes: #706137) Currently QEMU just build-depends on librbd-dev with no version. It needs to depend on at least version 1.3.0-3. This isn't an issue when building on Trusty, but on Precise the old broken libfdt-dev will get used. ** Affects: qemu (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu in Ubuntu. https://bugs.launchpad.net/bugs/1257962 Title: qemu needs at least version 1.3.0-3 of libfdt-dev to build To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1257962/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1226741] Re: doxygen is build-depends, not only Build-Depends-Indep
Can this trivial patch be released on the main libusbx package too? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1226741 Title: doxygen is build-depends, not only Build-Depends-Indep To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1226741/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1257962] [NEW] qemu needs at least version 1.3.0-3 of libfdt-dev to build
Public bug reported: I'm backporting QEMU from Trusty to Precise, and I've exposed a build dependency problem. The library libfdt-dev had a bug with version before 1.3.0-3 preventing it from being used. See the changelog: device-tree-compiler (1.3.0-3) unstable; urgency=low * libfdt-dev: Missing header file prevents the library usage Thanks Domenico Andreoli (Closes: #706137) Currently QEMU just build-depends on librbd-dev with no version. It needs to depend on at least version 1.3.0-3. This isn't an issue when building on Trusty, but on Precise the old broken libfdt-dev will get used. ** Affects: qemu (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1257962 Title: qemu needs at least version 1.3.0-3 of libfdt-dev to build To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1257962/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 560839] Re: error: too small lower memory (0x99100 0x98400)
I've reproduced this with an HP Z620, with 64G of RAM. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/560839 Title: error: too small lower memory (0x99100 0x98400) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/memtest86+/+bug/560839/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1026442] Re: Buddy pounce - send message window too short
Did this make it into precise-propsed? I don't see it yet. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1026442 Title: Buddy pounce - send message window too short To manage notifications about this bug go to: https://bugs.launchpad.net/pidgin/+bug/1026442/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1007575] Re: SB Arena USB headset causes X BUG, can't click outside window
Chris, that patch fixed my problems. Thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1007575 Title: SB Arena USB headset causes X BUG, can't click outside window To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1007575/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1040900] [NEW] syslog messages truncated to 256 chars during debian-installer run
Public bug reported: We're seeing syslog messages during installers runs truncated to 256 chars. This is annoying. Digging into the debian-installer source, its calling /sbin/syslogd from the initrd - this is a busybox binary. In the busybox source, there's a config variable CONFIG_FEATURE_SYSLOGD_READ_BUFFER_SIZE that defaults to 256. From the code, that looks to be the problem. Can we either - 1. fix busybox to use a dynamic buffer, or 2. bump the config variable up to 1024 or so? I'm perfectly happy with solution 2 :) ** Affects: ubuntu Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1040900 Title: syslog messages truncated to 256 chars during debian-installer run To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1040900/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1040900] Re: syslog messages truncated to 256 chars during debian-installer run
Reproduction instructions, using the binary itself. # Extract syslogd from the Precise netboot: wget http://archive.ubuntu.com/ubuntu/dists/precise/main/installer-amd64/current/images/netboot/netboot.tar.gz tar xzf /home/mwharris/Downloads/netboot.tar.gz ./ubuntu-installer/amd64/initrd.gz mkdir sbin gzip -dc ubuntu-installer/amd64/initrd.gz | cpio -i sbin/syslogd # Run the new syslogd. sudo stop rsyslog # to free the port sudo ./sbin/syslogd -n # Now the busybox syslogd is running. # Send a long line to syslogd logger watch runs command repeatedly, displaying its output and errors (the first screenfull). This allows you to watch the program output change over time. By default, the program is run every 2 seconds; use -n or --interval to specify a different interval. Normally, this interval is interpreted as the amout of time between the completion of one run of command and the beginning of the next run. However, with the -p or --precise option, you can make watch attempt to run command every interval seconds. Try it with ntptime and notice how the fractional seconds stays (nearly) the same, as opposed to normal mode where they continuously increase. Check /var/log/messages for truncated output. Another option to reproduce would be to look for a long line generated during install time, but I don't know of one off-hand. We're running puppet during install and it generates some long lines when it errors. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1040900 Title: syslog messages truncated to 256 chars during debian-installer run To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1040900/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1026990] [NEW] Add new option to dhclient to send DHCP requests on a cerrtain interface
Public bug reported: We have an interesting situation with dhclient, multiple interfaces, and DHCP servers not on the same subnet as a network. The setup: - on a machine with two connected interfaces, eth0 and wlan0. - the DHCP server for wlan0 is not on the same network segment as its clients. When it's time to renew the lease for wlan0, dhclient will try to renew via unicast to the DHCP server. Since it's on a different segment, the kernels routing tables are used to decide what interface the packet is sent out over. This could result in a DHCP request for wlan0 getting sent out over eth0, which is undesirable. The DHCP standard doesn't address this problem, so it's not really a bug, but it would be nice to resolve. This issue came up when we noticed errors on some switches. To resolve this, we're thinking this might work: a) Add a new flag to dhclient so that dhclient only sends IP packages via the interface the running instance is responsible for (ignoring the routing table). b) Add an option to network-manager which passes this flag to dhclient ** Affects: isc-dhcp (Ubuntu) Importance: Undecided Status: Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1026990 Title: Add new option to dhclient to send DHCP requests on a cerrtain interface To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1026990/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 933903] Re: Dropbear's initramfs scripts mount /dev/pts a second time
Looks good to me, thanks! ** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/933903 Title: Dropbear's initramfs scripts mount /dev/pts a second time To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dropbear/+bug/933903/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 933903] Re: Dropbear's initramfs scripts mount /dev/pts a second time
I don't see dropbear versino 2011.54-1ubuntu0.12.04.2 in the precise- proposed repo, is it there yet? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/933903 Title: Dropbear's initramfs scripts mount /dev/pts a second time To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dropbear/+bug/933903/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1007575] Re: SB Arena USB headset causes X BUG, can't click outside window
Here's the output of 'xinput test-i2'. I started it waited a bit plugged in the headset waited about 30 seconds then tried to click in another window twice. waited a bit then unplugged the headset. ** Attachment added: test-xi2 https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1007575/+attachment/3181069/+files/test-xi2 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1007575 Title: SB Arena USB headset causes X BUG, can't click outside window To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1007575/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 933903] Re: Dropbear's initramfs scripts mount /dev/pts a second time
Can this be released for Precise too? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/933903 Title: Dropbear's initramfs scripts mount /dev/pts a second time To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dropbear/+bug/933903/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1007575] Re: SB Arena USB headset causes X BUG, can't click outside window
The new packages fix the BUG, but I'm still getting the weird click behavior. What I'm seeing: 1. In a Konsole session, start a sudo tail -f /var/log/Xorg.0.log to watch the X log. 2. WIth focus still in Konsole, plug in the head phones. 3. Try to click another Konsole window I have open. Nothing happens from the click. 4. But I can click in a Chrome window I have open. 5. For the next second or so, I can click normally. But then it goes back to 3. What other logs or toubleshooting would help? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1007575 Title: SB Arena USB headset causes X BUG, can't click outside window To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1007575/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1007575] Re: SB Arena USB headset causes X BUG, can't click outside window
I've attached device.prop and xinput-list. ** Attachment added: device.prop https://bugs.launchpad.net/ubuntu/precise/+source/xorg-server/+bug/1007575/+attachment/3178146/+files/device.prop -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1007575 Title: SB Arena USB headset causes X BUG, can't click outside window To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1007575/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1007575] Re: SB Arena USB headset causes X BUG, can't click outside window
** Attachment added: output of xinput list --long https://bugs.launchpad.net/ubuntu/precise/+source/xorg-server/+bug/1007575/+attachment/3178147/+files/xinput-list -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1007575 Title: SB Arena USB headset causes X BUG, can't click outside window To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1007575/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1007575] Re: SB Arena USB headset causes X BUG, can't click outside window
Here's the evemu-record output. I'm worried the problem input is sent as soon as it's plugged in, which I can't capture with evemu since it doesn't exist yet. Maybe I should hook it in udev? ** Attachment added: device.record https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1007575/+attachment/3178347/+files/device.record -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1007575 Title: SB Arena USB headset causes X BUG, can't click outside window To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1007575/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1007575] Re: SB Arena USB headset causes X BUG, can't click outside window
Are you sure ppa:chasedouglas/mercury is correct? It looks out of date, with no Precise dist, just natty. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1007575 Title: SB Arena USB headset causes X BUG, can't click outside window To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1007575/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1007575] [NEW] SB Arena USB headset causes X BUG, can't click outside window
Public bug reported: When I plug my SB Arena USB headset in, I can't click the mouse in any window besides the one with focus. The current window works ok, but any other doesn't register the click. Also, I get a BUG in the X logs. This on Precise, xserver-xorg-input-evdev version 1:2.7.0-0ubuntu1 /var/log/Xorg.0.log: on device insert: [252903.181] (II) config/udev: Adding input device Creative Technology SB Arena Headset (/dev/input/event9) [252903.181] (**) Creative Technology SB Arena Headset: Applying InputClass evdev keyboard catchall [252903.181] (II) Using input driver 'evdev' for 'Creative Technology SB Arena Headset' [252903.181] (II) Loading /usr/lib/xorg/modules/input/evdev_drv.so [252903.181] (**) Creative Technology SB Arena Headset: always reports core events [252903.181] (**) evdev: Creative Technology SB Arena Headset: Device: /dev/input/event9 [252903.181] (--) evdev: Creative Technology SB Arena Headset: Vendor 0x41e Product 0x403 [252903.181] (--) evdev: Creative Technology SB Arena Headset: Found 8 mouse buttons [252903.181] (--) evdev: Creative Technology SB Arena Headset: Found keys [252903.181] (II) evdev: Creative Technology SB Arena Headset: Configuring as mouse [252903.181] (II) evdev: Creative Technology SB Arena Headset: Configuring as keyboard [252903.181] (**) evdev: Creative Technology SB Arena Headset: YAxisMapping: buttons 4 and 5 [252903.181] (**) evdev: Creative Technology SB Arena Headset: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200 [252903.181] (**) Option config_info udev:/sys/devices/pci:00/:00:1a.1/usb4/4-1/4-1:1.3/input/input18/event9 [252903.181] (II) XINPUT: Adding extended input device Creative Technology SB Arena Headset (type: KEYBOARD, id 15) [252903.181] (**) Option xkb_rules evdev [252903.181] (**) Option xkb_model pc105 [252903.181] (**) Option xkb_layout us [252903.191] BUG: triggered 'if (!dev-valuator || dev-valuator-numAxes 2)' BUG: ../../dix/getevents.c:850 in scale_to_desktop() [252903.191] Backtrace: [252903.192] 0: /usr/bin/X (xorg_backtrace+0x26) [0x7f148e6f3866] [252903.192] 1: /usr/bin/X (0x7f148e56b000+0x621fe) [0x7f148e5cd1fe] [252903.192] 2: /usr/bin/X (0x7f148e56b000+0x62e6d) [0x7f148e5cde6d] [252903.192] 3: /usr/bin/X (GetPointerEvents+0xe2) [0x7f148e5cf202] [252903.192] 4: /usr/bin/X (QueuePointerEvents+0x1d) [0x7f148e5cf65d] [252903.192] 5: /usr/bin/X (xf86PostButtonEvent+0xdd) [0x7f148e60b5ed] [252903.192] 6: /usr/lib/xorg/modules/input/evdev_drv.so (0x7f1486989000+0x5f48) [0x7f148698ef48] [252903.192] 7: /usr/bin/X (0x7f148e56b000+0x8ae07) [0x7f148e5f5e07] [252903.192] 8: /usr/bin/X (0x7f148e56b000+0xb0d4a) [0x7f148e61bd4a] [252903.192] 9: /lib/x86_64-linux-gnu/libpthread.so.0 (0x7f148d891000+0xfcb0) [0x7f148d8a0cb0] [252903.192] 10: /lib/x86_64-linux-gnu/libc.so.6 (__select+0x13) [0x7f148c7f0803] [252903.192] 11: /usr/bin/X (WaitForSomething+0x19b) [0x7f148e6f0c4b] [252903.192] 12: /usr/bin/X (0x7f148e56b000+0x4e4f2) [0x7f148e5b94f2] [252903.192] 13: /usr/bin/X (0x7f148e56b000+0x3d6aa) [0x7f148e5a86aa] [252903.192] 14: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xed) [0x7f148c72676d] [252903.192] 15: /usr/bin/X (0x7f148e56b000+0x3d99d) [0x7f148e5a899d] on removal: [252937.048] BUG: triggered 'if (!dev-valuator || dev-valuator-numAxes 2)' BUG: ../../dix/getevents.c:850 in scale_to_desktop() [252937.048] Backtrace: [252937.048] 0: /usr/bin/X (xorg_backtrace+0x26) [0x7f148e6f3866] [252937.048] 1: /usr/bin/X (0x7f148e56b000+0x621fe) [0x7f148e5cd1fe] [252937.048] 2: /usr/bin/X (0x7f148e56b000+0x62e6d) [0x7f148e5cde6d] [252937.048] 3: /usr/bin/X (GetPointerEvents+0xe2) [0x7f148e5cf202] [252937.048] 4: /usr/bin/X (QueuePointerEvents+0x1d) [0x7f148e5cf65d] [252937.048] 5: /usr/bin/X (xf86PostButtonEvent+0xdd) [0x7f148e60b5ed] [252937.048] 6: /usr/lib/xorg/modules/input/evdev_drv.so (0x7f1486989000+0x5f48) [0x7f148698ef48] [252937.048] 7: /usr/bin/X (0x7f148e56b000+0x8ae07) [0x7f148e5f5e07] [252937.048] 8: /usr/bin/X (0x7f148e56b000+0xb0d4a) [0x7f148e61bd4a] [252937.048] 9: /lib/x86_64-linux-gnu/libpthread.so.0 (0x7f148d891000+0xfcb0) [0x7f148d8a0cb0] [252937.048] 10: /lib/x86_64-linux-gnu/libc.so.6 (__select+0x13) [0x7f148c7f0803] [252937.048] 11: /usr/bin/X (WaitForSomething+0x19b) [0x7f148e6f0c4b] [252937.049] 12: /usr/bin/X (0x7f148e56b000+0x4e4f2) [0x7f148e5b94f2] [252937.049] 13: /usr/bin/X (0x7f148e56b000+0x3d6aa) [0x7f148e5a86aa] [252937.049] 14: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xed) [0x7f148c72676d] [252937.049] 15: /usr/bin/X (0x7f148e56b000+0x3d99d) [0x7f148e5a899d] [252937.310] (II) config/udev: removing device Creative Technology SB Arena Headset [252937.310] (II) evdev: Creative Technology SB Arena Headset: Close [252937.310] (II) UnloadModule: evdev [252937.310] (II) Unloading evdev lsusb: mwharris@linux:~$ lsusb -s 4:11 -v Bus 004 Device 011: ID 041e:0403 Creative Technology, Ltd Couldn't open device, some information will be missing
[Bug 933903] Re: Dropbear's initramfs scripts mount /dev/pts a second time
The packages you built fixes it for me. Thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/933903 Title: Dropbear's initramfs scripts mount /dev/pts a second time To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dropbear/+bug/933903/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 933903] Re: Dropbear's initramfs scripts mount /dev/pts a second time
** Summary changed: - Dropbear's init scripts mount /dev/pts a second time + Dropbear's initramfs scripts mount /dev/pts a second time -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/933903 Title: Dropbear's initramfs scripts mount /dev/pts a second time To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dropbear/+bug/933903/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 933903] [NEW] Dropbear's init scripts mount /dev/pts a second time
Public bug reported: The dropbear package includes an initramfs script, /usr/share/initramfs- tools/scripts/init-premount/devpts, that mounts devpts a second time, after it's already been mounted by /usr/share/initramfs-tools/init, provided by initramfs-tools. Line 23 in /usr/share/initramfs-tools/scripts/init-premount/devpts from dropbear: mount -t devpts none /dev/pts Line 25 in /usr/share/initramfs-tools/init from initramfs-tools: mount -t devpts -o noexec,nosuid,gid=5,mode=0620 devpts /dev/pts || true The second mount from dropbear fails since /dev/pts is already mounted, but it does change the mount options: mwharris@mwharris-test:~$ grep pts /proc/mounts devpts /dev/pts devpts rw,nosuid,noexec,relatime,mode=600,ptmxmode=000 0 0 I'm not sure why dropbear tried to mount devpts a second time, but it seems like the best fix would just be to remove /usr/share/initramfs- tools/scripts/init-premount/devpts from dropbear I'm on Precise using dropbear_2011.54-1 and initramfs-tools_0.99ubuntu10 ** Affects: dropbear (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/933903 Title: Dropbear's init scripts mount /dev/pts a second time To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dropbear/+bug/933903/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
