[Ubuntu-x-swat] [Bug 1923513] Re: xrandr --panning problem
** Tags added: focal ** Package changed: xorg (Ubuntu) => xorg-server (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/1923513 Title: xrandr --panning problem To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1923513/+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 1923153] Re: [radeon] Display output laggy from iGPU when operating on desktop with attaching AMD R7 430 graphic (dGPU)
Another useful thing that would be easy to test: Does the same bug occur in hirsute? -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1923153 Title: [radeon] Display output laggy from iGPU when operating on desktop with attaching AMD R7 430 graphic (dGPU) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1923153/+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 1923153] Re: [radeon] Display output laggy from iGPU when operating on desktop with attaching AMD R7 430 graphic (dGPU)
Hi Daniel, The "AMD R7 430" is the product name of the graphic card. https://ssl.www8.hp.com/emea_africa/en/products/oas/product-detail.html?oid=26185185 I guess it's related to radeon driver since we could see this issue with amd RX550 as well. ** Tags added: originate-from-1923120 ** Tags added: originate-from-1921875 -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1923153 Title: [radeon] Display output laggy from iGPU when operating on desktop with attaching AMD R7 430 graphic (dGPU) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1923153/+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 1923512] Re: Simple Scan
** Package changed: xorg (Ubuntu) => simple-scan (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/1923512 Title: Simple Scan To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/simple-scan/+bug/1923512/+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 1923437] Re: can't set 2560x1440 resolution after installing nvidia drivers
It appears 2560x1440 was a fake mode created by the open source driver. It's not a mode that is officially supported by the monitor itself, whose data I have decoded below: EDID version: 1.4 Manufacturer: GSM Model 23305 Serial Number 181370 Made in week 5 of 2016 Digital display 10 bits per primary color channel DisplayPort interface Maximum image size: 60 cm x 34 cm Gamma: 2.20 DPMS levels: Standby Supported color formats: RGB 4:4:4, YCrCb 4:4:4, YCrCb 4:2:2 Default (sRGB) color space is primary color space First detailed timing includes the native pixel format and preferred refresh rate Color Characteristics Red: 0.6523, 0.3349 Green: 0.3046, 0.6367 Blue: 0.1484, 0.0615 White: 0.3134, 0.3291 Established Timings I & II 640x48059.940 Hz 4:331.469 kHz 25.175 MHz (DMT) 800x60060.317 Hz 4:337.879 kHz 40.000 MHz (DMT) 1024x76860.004 Hz 4:348.363 kHz 65.000 MHz (DMT) Standard Timings 1152x86459.959 Hz 4:353.783 kHz 81.750 MHz (EDID 1.4 source: CVT) 1152x86460.000 Hz 4:353.700 kHz 81.624 MHz (EDID 1.3 source: GTF) 1280x1024 60.020 Hz 5:463.981 kHz 108.000 MHz (DMT) 1280x72060.000 Hz 16:945.000 kHz 74.250 MHz (DMT) 1600x90060.000 Hz 16:960.000 kHz 108.000 MHz (DMT, RB) 1920x1080 60.000 Hz 16:967.500 kHz 148.500 MHz (DMT) 1280x80059.810 Hz 16:10 49.702 kHz 83.500 MHz (DMT) Detailed mode: Clock 533.280 MHz, 600 mm x 340 mm 3840 3848 3992 4000 ( 8 144 8) 2160 2214 2219 ( 54 5 3) +hsync -vsync VertFreq: 60.000 Hz, HorFreq: 133.320 kHz Detailed mode: Clock 266.640 MHz, 600 mm x 340 mm 3840 3848 3992 4000 ( 8 144 8) 2160 2214 2219 ( 54 5 3) +hsync -vsync VertFreq: 30.000 Hz, HorFreq: 66.660 kHz Display Range Limits Monitor ranges (GTF): 56-61 Hz V, 30-135 kHz H, max dotclock 560 MHz Display Product Name: LG Ultra HD Has 1 extension block Checksum: 0x11 CTA-861 Extension Block Revision 3 Basic audio support Supports YCbCr 4:4:4 Supports YCbCr 4:2:2 1 native detailed modes 13 bytes of CTA data blocks Video Data Block 1920x1080 60.000 Hz 16:967.500 kHz 148.500 MHz (VIC 16, native) 1280x72060.000 Hz 16:945.000 kHz 74.250 MHz (VIC 4) 720x48059.940 Hz 16:931.469 kHz 27.000 MHz (VIC 3) 640x48059.940 Hz 4:331.469 kHz 25.175 MHz (VIC 1) Audio Data Block Linear PCM, max channels 2 Supported sample rates (kHz): 48 44.1 32 Supported sample sizes (bits): 24 20 16 Speaker Allocation Data Block Speaker map: FL/FR - Front Left/Right Detailed mode: Clock 148.500 MHz, 600 mm x 340 mm 1920 2008 2052 2200 ( 88 44 148) 1080 1084 1089 1125 ( 4 5 36) +hsync +vsync VertFreq: 60.000 Hz, HorFreq: 67.500 kHz Checksum: 0x41 ** Package changed: xorg (Ubuntu) => nvidia-graphics-drivers-460 (Ubuntu) ** Summary changed: - can't set 2560x1440 resolution after installing nvidia drivers + Can't add custom mode 2560x1440 after installing nvidia drivers -- 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/1923437 Title: Can't add custom mode 2560x1440 after installing nvidia drivers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-460/+bug/1923437/+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 1923153] Re: Display output laggy from iGPU when operating on desktop with attaching AMD R7 430 graphic (dGPU)
Thanks. That shows 'radeon' is the common problem. Also, is "AMD R7 430" a typo? Should that be "AMD R7 340"? ** No longer affects: xserver-xorg-video-amdgpu (Ubuntu) ** Summary changed: - Display output laggy from iGPU when operating on desktop with attaching AMD R7 430 graphic (dGPU) + [radeon] Display output laggy from iGPU when operating on desktop with attaching AMD R7 430 graphic (dGPU) ** Tags removed: amdgpu ** Also affects: xorg-server (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-amdgpu in Ubuntu. https://bugs.launchpad.net/bugs/1923153 Title: [radeon] Display output laggy from iGPU when operating on desktop with attaching AMD R7 430 graphic (dGPU) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1923153/+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 1865379] Re: Raspberry Pi 4 fails to wake at login prompt
** Changed in: xorg-server (Ubuntu) Status: Incomplete => Invalid -- 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/1865379 Title: Raspberry Pi 4 fails to wake at login prompt To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1865379/+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 1923513] Re: xrandr --panning problem
Thank you for the time & effort shown in researching the issue you've experienced. Before the bug can really be accepted & worked on by Ubuntu, it'll need to be confirmed that Linux Mint run-time adjustments are not-at-play, ie. confirmation on a pure Ubuntu system (with logs provided). Your logic & effort at finding your issue is noticed & appreciated. FYI: For best results, it's best to work on the current development release (so extra SRU steps aren't required, which currently are required for hirsute, so it'll be likely mean the next i-cycle). ** Changed in: xorg (Ubuntu) Status: Incomplete => New -- 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/1923513 Title: xrandr --panning problem To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1923513/+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 1863390] Re: GPU lockup ring 0 stalled for more than X msec
I am also experiencing this issue. I was using 18.04.5 and did not have the issue. I did a new install of 20.04 with the same hardware and the problem started. It continues after upgrade to 20.10. ~~~ user@8560w:~$ sudo lshw -C display [sudo] password for user: *-display description: VGA compatible controller product: Whistler [Radeon HD 6730M/6770M/7690M XT] vendor: Advanced Micro Devices, Inc. [AMD/ATI] physical id: 0 bus info: pci@:01:00.0 version: 00 width: 64 bits clock: 33MHz capabilities: pm pciexpress msi vga_controller bus_master cap_list rom configuration: driver=radeon latency=0 resources: irq:44 memory:c000-cfff memory:d440-d441 ioport:4000(size=256) memory:c-d ~~~ -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-ati in Ubuntu. https://bugs.launchpad.net/bugs/1863390 Title: GPU lockup ring 0 stalled for more than X msec To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/1863390/+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 1923513] Re: xrandr --panning problem
Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command only once, as it will automatically gather debugging information, in a terminal: apport-collect 1923513 When reporting bugs in the future please use apport by using 'ubuntu- bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs. Please note: `ubuntu-bug`, `apport` & bug reporting tools are provided with Ubuntu by default, many require manual addition for some releases of downstream OSes based on Ubuntu (eg. Linux Mint). You should check with your distribution first. ** Changed in: xorg (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/1923513 Title: xrandr --panning problem To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1923513/+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 1923512] [NEW] Simple Scan
Public bug reported: Non si avvia ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-122.124-generic 4.15.18 Uname: Linux 4.15.0-122-generic i686 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.17 Architecture: i386 CompositorRunning: None Date: Mon Apr 12 23:52:06 2021 DistUpgraded: 2020-12-01 13:10:34,496 DEBUG /openCache(), new cache size 61032 DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: virtualbox, 5.2.18, 4.15.0-122-generic, i686: installed GraphicsCard: Intel Corporation 4 Series Chipset Integrated Graphics Controller [8086:2e32] (rev 03) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. 4 Series Chipset Integrated Graphics Controller [1043:836d] InstallationDate: Installed on 2019-10-24 (536 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-122-generic root=UUID=6461ddc3-6faf-4eb3-8849-9f07b17f6e9d ro quiet splash Renderer: Software SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2020-12-01 (132 days ago) dmi.bios.date: 06/22/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0416 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5QPL-AM dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0416:bd06/22/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5QPL-AM:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.101-2~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Sun Mar 8 18:21:30 2020 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputYSTEK USB Mouse MOUSE, id 8 inputMicrosoft® LifeCam VX-2000: Mi KEYBOARD, id 9 inputAT Translated Set 2 keyboard KEYBOARD, id 10 xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.6-1ubuntu4.4 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug bionic i386 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/1923512 Title: Simple Scan To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1923512/+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 1923513] [NEW] xrandr --panning problem
Public bug reported: Dear community Recently I upgraded my old netbook from Linux from Linux Mint 18 to Linux Mint 20 Distribution: cat /etc/upstream-release/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=20.04 DISTRIB_CODENAME=focal DISTRIB_DESCRIPTION="Ubuntu Focal Fossa" Netbook is with small screen 1024x600 To get bigger virtual screen I use xrandr like: xrandr --fb 1024x768 --output LVDS1 --panning 1024x768 To return to normal screen I use xrandr --fb 1024x600 What is expected: when the mouse moves outside the 1024x600 screen - new "clean" virtual area appears. What is in reality: With fresh Ubuntu the first script results to wrong "background" image on the extended area: When I move mouse down below the original 600 pixels, first 768-600=168 strings are shown like a background image. Or new virtual 601 string is the copy of the old 1 602 string is the copy of the old 2 ... 768 string is the copy of the old 168 It looks like an index shift in the array: The string which "disappears" from the top is moved to the bottom This "background" image can be overwritten by the real application window. For example, if I move the terminal window it appears on the top of this "background" But after moving mouse back inside the 1024x600 screen and back outside the 1024x600 screen, the shifted copy of the top part of the screen appears at the bottom according the 1->601 2->602 etc logic. After playing a lot with xrandr parameters I had found a workaround: One has to specify the first parameter in --fb bigger than the first parameter in --panning For example: xrandr --fb 1025x768 --output LVDS1 --panning 1024x768 Here 1025>1024 I had checked this bug with two different laptops, so it is not related with the hardware. More information: xrandr -v xrandr program version 1.5.0 Server reports RandR version 1.6 The working configuration: xrandr Screen 0: minimum 8 x 8, current 1025 x 768, maximum 32767 x 32767 LVDS1 connected primary 1024x768+0+0 (normal left inverted right x axis y axis) 220mm x 130mm panning 1024x768+0+0 1024x600 60.19*+ 1024x576 59.9059.82 960x540 59.6359.82 800x600 60.3256.25 864x486 59.9259.57 640x480 59.94 720x405 59.5158.99 640x360 59.8459.32 512x300 60.00 VGA1 disconnected (normal left inverted right x axis y axis) VIRTUAL1 disconnected (normal left inverted right x axis y axis Wrongly working configuration: xrandr Screen 0: minimum 8 x 8, current 1024 x 768, maximum 32767 x 32767 LVDS1 connected primary 1024x768+0+0 (normal left inverted right x axis y axis) 220mm x 130mm panning 1024x768+0+0 1024x600 60.19*+ 1024x576 59.9059.82 960x540 59.6359.82 800x600 60.3256.25 864x486 59.9259.57 640x480 59.94 720x405 59.5158.99 640x360 59.8459.32 512x300 60.00 VGA1 disconnected (normal left inverted right x axis y axis) VIRTUAL1 disconnected (normal left inverted right x axis y axis) Hope you can reproduce this bug. Best regards, Dmitry ** Affects: xorg (Ubuntu) Importance: Undecided Status: New -- 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/1923513 Title: xrandr --panning problem To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1923513/+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 1914286] Re: xsetwacom non-functional after hot-plug
Note, this appears to be a result of every hotplug resulting in Mode being set to relative. Changing mode to absolute enables the mapping to work. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xf86-input-wacom in Ubuntu. https://bugs.launchpad.net/bugs/1914286 Title: xsetwacom non-functional after hot-plug To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xf86-input-wacom/+bug/1914286/+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 1923472] Re: xdm fails to start on Sundays
** Changed in: xdm (Debian) Status: Unknown => Confirmed -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xdm in Ubuntu. https://bugs.launchpad.net/bugs/1923472 Title: xdm fails to start on Sundays To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xdm/+bug/1923472/+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 1923472] Re: xdm fails to start on Sundays
** Package changed: systemd (Ubuntu) => xdm (Ubuntu) ** Bug watch added: Debian Bug tracker #948346 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=948346 ** Also affects: xdm (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=948346 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xdm in Ubuntu. https://bugs.launchpad.net/bugs/1923472 Title: xdm fails to start on Sundays To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xdm/+bug/1923472/+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 1923472] [NEW] xdm fails to start on Sundays
You have been subscribed to a public bug: On the first login of the week, xdm (1.1.11-3ubuntu2) fails to start on Ubuntu 20.04. More correctly, it does start, but exits almost immediately on signal 12. It leaves /var/run/xdm.pid behind, and also a running X server with no clients. This makes it hard to restart, for one needs to kill the X server and remove the pid file first. The cause is logrotate running during startup and killing xdm before xdm installs a handler for SIGUSR2. The issue is more fully described upstream at https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=948346 In passing I would comment that running logrotate so early during startup seems strange to me. Startup would surely be faster if these sort of "cron" jobs were left until it had finished? ** Affects: xdm (Ubuntu) Importance: Undecided Status: New -- xdm fails to start on Sundays https://bugs.launchpad.net/bugs/1923472 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xdm 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 1865379] Re: Raspberry Pi 4 fails to wake at login prompt
No response to my question in #34 from April of last year so setting 'linux (Ubuntu)' to 'Invalid'. ** Changed in: linux (Ubuntu) Status: Confirmed => Invalid -- 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/1865379 Title: Raspberry Pi 4 fails to wake at login prompt To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1865379/+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 1923153] Re: Display output laggy from iGPU when operating on desktop with attaching AMD R7 430 graphic (dGPU)
@Daniel, Above are the outputs. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-amdgpu in Ubuntu. https://bugs.launchpad.net/bugs/1923153 Title: Display output laggy from iGPU when operating on desktop with attaching AMD R7 430 graphic (dGPU) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1923153/+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 1923153] Re: Display output laggy from iGPU when operating on desktop with attaching AMD R7 430 graphic (dGPU)
** Attachment added: "lspci2.txt" https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-amdgpu/+bug/1923153/+attachment/5486866/+files/lspci2.txt -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-amdgpu in Ubuntu. https://bugs.launchpad.net/bugs/1923153 Title: Display output laggy from iGPU when operating on desktop with attaching AMD R7 430 graphic (dGPU) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1923153/+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 1923153] Re: Display output laggy from iGPU when operating on desktop with attaching AMD R7 430 graphic (dGPU)
** Attachment added: "journal2.txt" https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-amdgpu/+bug/1923153/+attachment/5486867/+files/journal2.txt -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-amdgpu in Ubuntu. https://bugs.launchpad.net/bugs/1923153 Title: Display output laggy from iGPU when operating on desktop with attaching AMD R7 430 graphic (dGPU) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1923153/+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 1923153] Re: Display output laggy from iGPU when operating on desktop with attaching AMD R7 430 graphic (dGPU)
here is the output ** Attachment added: "journal-b-k.log" https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-amdgpu/+bug/1923153/+attachment/5486865/+files/journal-b-k.log -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-amdgpu in Ubuntu. https://bugs.launchpad.net/bugs/1923153 Title: Display output laggy from iGPU when operating on desktop with attaching AMD R7 430 graphic (dGPU) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1923153/+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 1923437] [NEW] can't set 2560x1440 resolution after installing nvidia drivers
Public bug reported: Hello ! I have 2 monitors 1) one is 4K 2) another one is FULLHD, when I installed lubuntu I had 4k monitor work at maximum 4k and another at fullhd , I want to change that 4k monitor to 2560x1440(2k). after install nvidia drivers there is no 2560x1440 resolution in "monitor settings" resolutions tab like it was before installing drivers. when trying to add it manually from xrandr, at some point it gives me that error: X Error of failed request: BadName (named color or font does not exist) Major opcode of failed request: 140 (RANDR) Minor opcode of failed request: 16 (RRCreateMode) Serial number of failed request: 35 Current serial number in output stream: 35 in short , I can't set monitor to 2560x1440. what it might be ? -- 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu Description:Ubuntu Hirsute Hippo (development branch) Release:21.04 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center Unable to locate package pkgname 3) What you expected to happen have 2560x1440 resolution option after installing nvidia driver 4) What happened instead have no 2560x1440 listed in "monitor settings" and can't even create it manually from xrandr commands Best Regard ! ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xorg 1:7.7+22ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11.7 Uname: Linux 5.11.0-13-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..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01: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 460.67 Thu Mar 11 00:11:45 UTC 2021 GCC version: gcc version 10.3.0 (Ubuntu 10.3.0-1ubuntu1) ApportVersion: 2.20.11-0ubuntu62 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: LXQt Date: Mon Apr 12 14:07:34 2021 DistUpgraded: Fresh install DistroCodename: hirsute DistroVariant: ubuntu DkmsStatus: nvidia, 460.67, 5.11.0-13-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation GP107 [GeForce GTX 1050] [10de:1c81] (rev a1) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. GP107 [GeForce GTX 1050] [3842:6150] InstallationDate: Installed on 2021-04-12 (0 days ago) InstallationMedia: Lubuntu 21.04 "Hirsute Hippo" - Beta amd64 (20210331) MachineType: ASUS All Series ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.11.0-13-generic root=UUID=acd8d9c8-3bd0-4c68-9a02-19818e4cf3c3 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/05/2017 dmi.bios.release: 5.11 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3802 dmi.board.asset.tag: Default string dmi.board.name: X99-DELUXE dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3802:bd09/05/2017:br5.11:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnX99-DELUXE:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.sku: All dmi.product.version: System Version dmi.sys.vendor: ASUS version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.104-1build1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.10-3ubuntu7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute resolution 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/1923437 Title: can't set 2560x1440 resolution after installing nvidia drivers To manage notifications about this bug go to:
[Ubuntu-x-swat] [Bug 1923421] [NEW] Can't change ImageMagick as a default application for opening PDF
Public bug reported: I have ImageMagick set as the default application for opening PDF. I am trying to change the setting, but it doesn't work. ** Affects: ubuntu Importance: Undecided Status: New ** Package changed: xorg (Ubuntu) => 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/1923421 Title: Can't change ImageMagick as a default application for opening PDF To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1923421/+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 1923397] Re: Xorg freeze
OK then we should ignore the old links above. Next please: 1. Reproduce the freeze again. 2. Wait 30 seconds. 3. Reboot. 4. Run this command: journalctl -b-1 > prevboot.txt 5. 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/1923397 Title: Xorg freeze To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1923397/+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
Re: [Ubuntu-x-swat] [Bug 1923397] Re: Xorg freeze
On 12/04/2021 10:57, Daniel van Vugt wrote: > Also, all of the above crashes are from a desktop, whereas this bug > report is from an Acer laptop. Which machine do you want this bug to be > about? The bug is about my new Acer laptop. The disk content was copied from an old desktop. -- 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/1923397 Title: Xorg freeze To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1923397/+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 1923397] Re: Xorg freeze
Also, all of the above crashes are from a desktop, whereas this bug report is from an Acer laptop. Which machine do you want this bug to be about? -- 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/1923397 Title: Xorg freeze To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1923397/+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 1923397] Re: Xorg freeze
https://errors.ubuntu.com/oops/34abb3af-6156-11eb-8e20-fa163e6cac46 That is either bug 1897765 or bug 1897832. --- https://errors.ubuntu.com/oops/399bd8fc-d4f8-11ea-ae34-fa163ee63de6 https://errors.ubuntu.com/oops/12279266-8822-11ea-a31f-fa163e6cac46 https://errors.ubuntu.com/oops/204fea4d-e344-11e9-a6a3-fa163e6cac46 Not enough information in those crash reports :( --- https://errors.ubuntu.com/oops/348838a4-fc1f-11e9-b630-fa163e102db1 https://errors.ubuntu.com/oops/09574842-72fd-11e9-a6fc-fa163e102db1 Those are the 'nouveau' driver crashing. If you have any machine with an Nvidia GPU then please use the 'Additional Drivers' app to install the official Nvidia driver instead. -- 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/1923397 Title: Xorg freeze To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1923397/+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
Re: [Ubuntu-x-swat] [Bug 1923397] Re: Xorg freeze
On 12/04/2021 9:38, Daniel van Vugt wrote: > Thank you for taking the time to report this bug and helping to make > Ubuntu better. It sounds like some part of the system has crashed. To > help us find the cause of the crash please follow these steps: > > 1. Look in /var/crash for crash files and if found run: > ubuntu-bug YOURFILE.crash > Then tell us the ID of the newly-created bug. There are no relevant /var/crash/*.crash files. > 2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where > ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. > Do you find any links to recent problems on that page? If so then please > send the links to us. Probably this: https://errors.ubuntu.com/oops/34abb3af-6156-11eb-8e20-fa163e6cac46 https://errors.ubuntu.com/oops/399bd8fc-d4f8-11ea-ae34-fa163ee63de6 https://errors.ubuntu.com/oops/12279266-8822-11ea-a31f-fa163e6cac46 https://errors.ubuntu.com/oops/348838a4-fc1f-11e9-b630-fa163e102db1 https://errors.ubuntu.com/oops/204fea4d-e344-11e9-a6a3-fa163e6cac46 https://errors.ubuntu.com/oops/09574842-72fd-11e9-a6fc-fa163e102db1 > 3. If step 2 also failed then apply the workaround from bug 994921, > reboot, reproduce the crash, and retry step 1. I don't know how to find this 994921. -- 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/1923397 Title: Xorg freeze To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1923397/+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 1923167] Re: Screen flickering- QHD Benq
Please try a different cable. If that doesn't solve the problem then please run these commands: lspci -kv > lspci.txt journalctl -b0 > journal.txt xrandr --verbose > xrandr.txt and attach the resulting text files here. ** Package changed: xorg (Ubuntu) => xserver-xorg-video-amdgpu (Ubuntu) ** Changed in: xserver-xorg-video-amdgpu (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-amdgpu in Ubuntu. https://bugs.launchpad.net/bugs/1923167 Title: Screen flickering- QHD Benq To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-amdgpu/+bug/1923167/+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 1923397] Re: Xorg freeze
Thank you for taking the time to report this bug and helping to make Ubuntu better. It sounds like some part of the system has crashed. To help us find the cause of the crash please follow these steps: 1. Look in /var/crash for crash files and if found run: ubuntu-bug YOURFILE.crash Then tell us the ID of the newly-created bug. 2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us. 3. If step 2 also failed then apply the workaround from bug 994921, reboot, reproduce the crash, and retry step 1. Please take care to avoid attaching .crash files to bugs as we are unable to process them as file attachments. It would also be a security risk for yourself. ** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu) ** 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/1923397 Title: Xorg freeze To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1923397/+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 1923381] Re: [Lenovo ThinkPad T450s] regression: no display when waking from suspend
Thanks for the bug report. I can see two immediate problems. The first problem isn't really related to this bug but you should fix it anyway. Your log is being flooded by crashes in 'onedrive'. If you don't need 'onedrive' then consider uninstalling it. The second problem is these messages in your Xorg logs which might be related to this bug: [ 87005.338] [dix] EventToCore: Not implemented yet [ 87131.437] [dix] EventToCore: Not implemented yet [ 87283.009] [dix] EventToCore: Not implemented yet Next we would like to see a system log of the problem happening so please: 1. Reproduce the bug again such that the machine is unresponsive. 2. Wait 30 seconds. 3. Do a "hard reboot". 4. Run: journalctl -b-1 > prevboot.txt 5. Attach the resulting text file here. 6. Follow these instructions to check for crashes: https://wiki.ubuntu.com/Bugs/Responses#Missing_a_crash_report_or_having_a_.crash_attachment ** Summary changed: - regression: no display when waking from suspend + [Lenovo ThinkPad T450s] regression: no display when waking from suspend ** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu) ** Tags added: multimonitor ** Changed in: xorg-server (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1923381 Title: [Lenovo ThinkPad T450s] regression: no display when waking from suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1923381/+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 1923333] Re: Benq G610HDA not being detected
Thanks for the bug report. It appears the Nvidia Xorg driver has not been installed properly so any display plugged into the Nvidia GPU won't be detected. Please try uninstalling and then reinstalling the Nvidia driver using the 'Additional Drivers' app. ** Package changed: xorg (Ubuntu) => nvidia-graphics-drivers-460 (Ubuntu) ** Changed in: nvidia-graphics-drivers-460 (Ubuntu) Status: New => Incomplete ** Description changed: - My monitor Benq G610HDA is not being detected by Ubuntu. Good VGI Cable, + My monitor Benq G610HDA is not being detected by Ubuntu. Good VGA Cable, still Unknown display ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-48.54~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-48-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..04.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:04: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 460.39 Thu Jan 21 21:54:06 UTC 2021 - GCC version: gcc version 10.2.0 (Ubuntu 10.2.0-5ubuntu1~20.04) + NVRM version: NVIDIA UNIX x86_64 Kernel Module 460.39 Thu Jan 21 21:54:06 UTC 2021 + GCC version: gcc version 10.2.0 (Ubuntu 10.2.0-5ubuntu1~20.04) ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Apr 11 13:13:18 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: - nvidia, 460.39, 5.8.0-45-generic, x86_64: installed (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) - nvidia, 460.39, 5.8.0-48-generic, x86_64: installed - v4l2loopback, 0.12.3, 5.8.0-45-generic, x86_64: installed - v4l2loopback, 0.12.3, 5.8.0-48-generic, x86_64: installed + nvidia, 460.39, 5.8.0-45-generic, x86_64: installed (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) + nvidia, 460.39, 5.8.0-48-generic, x86_64: installed + v4l2loopback, 0.12.3, 5.8.0-45-generic, x86_64: installed + v4l2loopback, 0.12.3, 5.8.0-48-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: - Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) -Subsystem: ASUSTeK Computer Inc. HD Graphics 5500 [1043:1a7d] -Subsystem: ASUSTeK Computer Inc. GM108M [GeForce 940M] [1043:1a7d] + Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) + Subsystem: ASUSTeK Computer Inc. HD Graphics 5500 [1043:1a7d] + Subsystem: ASUSTeK Computer Inc. GM108M [GeForce 940M] [1043:1a7d] InstallationDate: Installed on 2021-02-08 (61 days ago) InstallationMedia: Ubuntu 20.04.2 LTS "Focal Fossa" - Release amd64 (20210204) MachineType: ASUSTeK COMPUTER INC. X455LB ProcEnviron: - LANGUAGE=en_PH:en - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=en_PH.UTF-8 - SHELL=/bin/zsh + LANGUAGE=en_PH:en + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_PH.UTF-8 + SHELL=/bin/zsh ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-48-generic root=UUID=def1bb03-4353-441e-b107-29aaf5b72e17 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/03/2015 dmi.bios.release: 5.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X455LB.205 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X455LB dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX455LB.205:bd08/03/2015:br5.6:svnASUSTeKCOMPUTERINC.:pnX455LB:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX455LB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: X dmi.product.name: X455LB dmi.product.sku: ASUS-NotebookSKU dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers:
[Ubuntu-x-swat] [Bug 1923318] Re: Ubuntu does not detect video output devices
Please also run these commands: lspci -kv > lspci.txt journalctl -b0 > journal.txt xrandr --verbose > xrandr.txt grep . /sys/class/drm/*/status > kernelconn.txt grep . /sys/class/drm/*/modes > kernelmodes.txt and attach the resulting text files here. ** Package changed: xorg (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/1923318 Title: Ubuntu does not detect video output devices To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1923318/+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 1923233] Re: Computer is very slow
Thanks for the bug report. I can't see anything broken so can you explain exactly what is slow (and what isn't)? Please also open a Terminal window and run 'top'. How much CPU is used while the computer is slow? ** 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/1923233 Title: Computer is very slow To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1923233/+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
