[Bug 2044630] Re: zfs-dkms 2.1.5-1ubuntu6~22.04.2- Kernel module failed to build
Same here: can't appear to install anything new zfs-2.1.5-1ubuntu6~22.04.4 zfs-kmod-2.2.0-0ubuntu1~23.10.2 I'm not seeing any time-to-fix notices -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2044630 Title: zfs-dkms 2.1.5-1ubuntu6~22.04.2- Kernel module failed to build To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/2044630/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958313] [NEW] nvidia-dkms-460 460.80-0ubuntu0.20.04.2: nvidia kernel module failed to build
Public bug reported: Description:Ubuntu 20.04.2 LTS Release:20.04 First occurrence. Using text editor after starting from hibernation. GIMP was still running in the background with low res scanned doc. Months of error free graphics since graphics-card upgrade which I don't believe has caused this error. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: nvidia-dkms-460 460.80-0ubuntu0.20.04.2 ProcVersionSignature: Ubuntu 5.11.0-46.51~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-46-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip DKMSKernelVersion: 5.13.0-25-generic Date: Wed Jan 19 08:01:08 2022 DuplicateSignature: dkms:nvidia-dkms-460:460.80-0ubuntu0.20.04.2:/var/lib/dkms/nvidia/460.80/build/nvidia-drm/nvidia-drm-crtc.c:311:23: error: initialization of ‘int (*)(struct drm_plane *, struct drm_atomic_state *)’ from incompatible pointer type ‘int (*)(struct drm_plane *, struct drm_plane_state *)’ [-Werror=incompatible-pointer-types] InstallationDate: Installed on 2021-07-01 (201 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) PackageVersion: 460.80-0ubuntu0.20.04.2 Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: nvidia-graphics-drivers-460 Title: nvidia-dkms-460 460.80-0ubuntu0.20.04.2: nvidia kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nvidia-graphics-drivers-460 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958313 Title: nvidia-dkms-460 460.80-0ubuntu0.20.04.2: nvidia kernel module failed to build To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-460/+bug/1958313/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1940993] [NEW] package tex-common 6.09 failed to install/upgrade: installed tex-common package post-installation script subprocess returned error exit status 1
Public bug reported: I was just upgrading from 16 LTS to 18 LTS to 20 LTS and this popped up. ProblemType: Package DistroRelease: Ubuntu 18.04 Package: tex-common 6.09 ProcVersionSignature: Ubuntu 4.15.0-154.161-generic 4.15.18 Uname: Linux 4.15.0-154-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.24 Architecture: amd64 Date: Tue Aug 24 12:49:22 2021 ErrorMessage: installed tex-common package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2014-02-13 (2749 days ago) InstallationMedia: Ubuntu 12.04.3 LTS "Precise Pangolin" - Release amd64 (20130820.1) PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.9, python3-minimal, 3.6.7-1~18.04 PythonDetails: /usr/bin/python2.7, Python 2.7.17, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2.3 apt 1.6.14 SourcePackage: tex-common Title: package tex-common 6.09 failed to install/upgrade: installed tex-common package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to bionic on 2021-08-24 (0 days ago) ** Affects: tex-common (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package bionic third-party-packages -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1940993 Title: package tex-common 6.09 failed to install/upgrade: installed tex- common package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tex-common/+bug/1940993/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1915565] [NEW] screen fades for about 10 seconds glslideshowthen returns to normal
Public bug reported: The fading happens online at . But it also happens offline in games. Using Ubuntu 20.04 Unable to locate package pkgname ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-65.73-generic 5.4.78 Uname: Linux 5.4.0-65-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 BootLog: CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Fri Feb 12 13:14:56 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: bbswitch, 0.8, 5.4.0-64-generic, x86_64: installed bbswitch, 0.8, 5.4.0-65-generic, x86_64: installed nvidia, 390.141, 5.4.0-64-generic, x86_64: installed nvidia, 390.141, 5.4.0-65-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Skylake GT2 [HD Graphics 520] [103c:820c] Subsystem: Hewlett-Packard Company GM108M [GeForce 940MX] [103c:820c] InstallationDate: Installed on 2017-04-14 (1400 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0eef:c04d D-WAV Scientific Co., Ltd eGalaxTouch EXC3000-0367-44.01.00 Bus 001 Device 003: ID 8087:0a2a Intel Corp. Bus 001 Device 002: ID 0408:5090 Quanta Computer, Inc. HP Wide version HD Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Pavilion Notebook ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-65-generic root=UUID=07e929a4-0ebf-4ecc-bedd-3f5fbf79e6d8 ro quiet splash SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/21/2016 dmi.bios.vendor: Insyde dmi.bios.version: F.22 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 820C dmi.board.vendor: HP dmi.board.version: 82.29 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.22:bd09/21/2016:svnHP:pnHPPavilionNotebook:pvrType1ProductConfigId:rvnHP:rn820C:rvr82.29:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV X=Null dmi.product.name: HP Pavilion Notebook dmi.product.sku: X0S49UA#ABA 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: Sat Oct 17 14:45:19 2020 xserver.configfile: default xserver.errors: open /dev/dri/card0: No such file or directory open /dev/dri/card0: No such file or directory Screen 0 deleted because of no matching config section. xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.20.8-2ubuntu2.4 ** 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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1915565 Title: screen fades for about 10 seconds glslideshowthen returns to normal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1915565/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1906947] [NEW] package wireguard-dkms 1.0.20201112-1~20.04.1 failed to install/upgrade: installed wireguard-dkms package post-installation script subprocess returned error exit status 10
Public bug reported: On attempted upgrade from 18.04LTS to 20LTS ProblemType: Package DistroRelease: Ubuntu 20.04 Package: wireguard-dkms 1.0.20201112-1~20.04.1 ProcVersionSignature: Ubuntu 4.15.0-50.54-generic 4.15.18 Uname: Linux 4.15.0-50-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.13 Architecture: amd64 CasperMD5CheckResult: skip Date: Sat Dec 5 18:27:09 2020 ErrorMessage: installed wireguard-dkms package post-installation script subprocess returned error exit status 10 InstallationDate: Installed on 2020-12-04 (1 days ago) InstallationMedia: PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.1 SourcePackage: wireguard-linux-compat Title: package wireguard-dkms 1.0.20201112-1~20.04.1 failed to install/upgrade: installed wireguard-dkms package post-installation script subprocess returned error exit status 10 UpgradeStatus: Upgraded to focal on 2020-12-05 (0 days ago) ** Affects: wireguard-linux-compat (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1906947 Title: package wireguard-dkms 1.0.20201112-1~20.04.1 failed to install/upgrade: installed wireguard-dkms package post-installation script subprocess returned error exit status 10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wireguard-linux-compat/+bug/1906947/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1903927] [NEW] package fd-find 8.1.1-1 failed to install/upgrade: trying to overwrite '/usr/share/bash-completion/completions/fd', which is also in package fd-musl 7.2.0
Public bug reported: This is just happening after installing fd-find ProblemType: Package DistroRelease: Ubuntu 20.10 Package: fd-find 8.1.1-1 ProcVersionSignature: Ubuntu 5.8.0-28.30-generic 5.8.14 Uname: Linux 5.8.0-28-generic x86_64 ApportVersion: 2.20.11-0ubuntu50 AptOrdering: fd-find:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Wed Nov 11 16:20:25 2020 DpkgTerminalLog: Preparing to unpack .../fd-find_8.1.1-1_amd64.deb ... Unpacking fd-find (8.1.1-1) ... [1mdpkg:[0m error processing archive /var/cache/apt/archives/fd-find_8.1.1-1_amd64.deb (--unpack): trying to overwrite '/usr/share/bash-completion/completions/fd', which is also in package fd-musl 7.2.0 ErrorMessage: trying to overwrite '/usr/share/bash-completion/completions/fd', which is also in package fd-musl 7.2.0 InstallationDate: Installed on 2020-11-11 (0 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) Python3Details: /usr/bin/python3.8, Python 3.8.6, python3-minimal, 3.8.6-0ubuntu1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.20.5ubuntu2 apt 2.1.10 SourcePackage: rust-fd-find Title: package fd-find 8.1.1-1 failed to install/upgrade: trying to overwrite '/usr/share/bash-completion/completions/fd', which is also in package fd-musl 7.2.0 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: rust-fd-find (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package groovy third-party-packages -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1903927 Title: package fd-find 8.1.1-1 failed to install/upgrade: trying to overwrite '/usr/share/bash-completion/completions/fd', which is also in package fd-musl 7.2.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rust-fd-find/+bug/1903927/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901470] Re: [modeset][i915] Native resolution (EDID detailed mode) of 2560x1440 not listed, defaults to 1920x1080 instead
Follow post of a work around that automatically enables the resolution I want. I added a file named: 45custom_xrandr_settings in folder: /etc/X11/Xsession.d containing: xrandr --newmode "Mode 0" 241.50 2560 2608 2640 2720 1440 1443 1448 1481 +hsync -vsync xrandr --addmode HDMI-1-1 "Mode 0" This will cause X11 to use the 2560x1440 resolution after reboot. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901470 Title: [modeset][i915] Native resolution (EDID detailed mode) of 2560x1440 not listed, defaults to 1920x1080 instead To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1901470/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1902403] [NEW] [HP Compaq 6005 Pro SFF PC, Realtek ALC662 rev1, Green Line Out, Rear] No sound at all
Public bug reported: No audio at all ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: saint 1685 F pulseaudio /dev/snd/controlC0: saint 1685 F pulseaudio /dev/snd/pcmC0D0p: saint 1685 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Oct 31 23:27:11 2020 InstallationDate: Installed on 2020-11-01 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:SB failed Symptom_Card: Built-in Audio - HDA ATI SB Symptom_Jack: Green Line Out, Rear Symptom_Type: No sound at all Title: [HP Compaq 6005 Pro SFF PC, Realtek ALC662 rev1, Green Line Out, Rear] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/02/2011 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 786G6 v01.15 dmi.board.asset.tag: 2UA1320F73 dmi.board.name: 3047h dmi.board.vendor: Hewlett-Packard dmi.chassis.asset.tag: 2UA1320F73 dmi.chassis.type: 4 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr786G6v01.15:bd08/02/2011:svnHewlett-Packard:pnHPCompaq6005ProSFFPC:pvr:rvnHewlett-Packard:rn3047h:rvr:cvnHewlett-Packard:ct4:cvr: dmi.product.family: 103C_53307F dmi.product.name: HP Compaq 6005 Pro SFF PC dmi.product.sku: SN052UC#ABA dmi.sys.vendor: Hewlett-Packard ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1902403 Title: [HP Compaq 6005 Pro SFF PC, Realtek ALC662 rev1, Green Line Out, Rear] No sound at all To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1902403/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901470] Re: resolution not listed in xrandr from ASUS ROG PG278QR via HDMI
output from: grep . /sys/class/drm/*/modes > modes.txt ** Attachment added: "modes.txt" https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1901470/+attachment/5428462/+files/modes.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901470 Title: resolution not listed in xrandr from ASUS ROG PG278QR via HDMI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1901470/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901470] NvidiaBugReportLog.txt
apport information ** Attachment added: "NvidiaBugReportLog.txt" https://bugs.launchpad.net/bugs/1901470/+attachment/5427749/+files/NvidiaBugReportLog.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901470 Title: resolution not listed in xrandr from ASUS ROG PG278QR via HDMI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1901470/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901470] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/1901470/+attachment/5427744/+files/Lspci-vt.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901470 Title: resolution not listed in xrandr from ASUS ROG PG278QR via HDMI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1901470/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901470] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1901470/+attachment/5427757/+files/UdevDb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901470 Title: resolution not listed in xrandr from ASUS ROG PG278QR via HDMI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1901470/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901470] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1901470/+attachment/5427752/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901470 Title: resolution not listed in xrandr from ASUS ROG PG278QR via HDMI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1901470/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901470] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1901470/+attachment/5427755/+files/ProcModules.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901470 Title: resolution not listed in xrandr from ASUS ROG PG278QR via HDMI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1901470/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901470] nvidia-settings.txt
apport information ** Attachment added: "nvidia-settings.txt" https://bugs.launchpad.net/bugs/1901470/+attachment/5427764/+files/nvidia-settings.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901470 Title: resolution not listed in xrandr from ASUS ROG PG278QR via HDMI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1901470/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901470] DpkgLog.txt
apport information ** Attachment added: "DpkgLog.txt" https://bugs.launchpad.net/bugs/1901470/+attachment/5427742/+files/DpkgLog.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901470 Title: resolution not listed in xrandr from ASUS ROG PG278QR via HDMI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1901470/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901470] xdpyinfo.txt
apport information ** Attachment added: "xdpyinfo.txt" https://bugs.launchpad.net/bugs/1901470/+attachment/5427765/+files/xdpyinfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901470 Title: resolution not listed in xrandr from ASUS ROG PG278QR via HDMI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1901470/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901470] acpidump.txt
apport information ** Attachment added: "acpidump.txt" https://bugs.launchpad.net/bugs/1901470/+attachment/5427763/+files/acpidump.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901470 Title: resolution not listed in xrandr from ASUS ROG PG278QR via HDMI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1901470/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901470] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/1901470/+attachment/5427747/+files/Lsusb-v.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901470 Title: resolution not listed in xrandr from ASUS ROG PG278QR via HDMI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1901470/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901470] Xrandr.txt
apport information ** Attachment added: "Xrandr.txt" https://bugs.launchpad.net/bugs/1901470/+attachment/5427761/+files/Xrandr.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901470 Title: resolution not listed in xrandr from ASUS ROG PG278QR via HDMI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1901470/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901470] XorgLogOld.txt
apport information ** Attachment added: "XorgLogOld.txt" https://bugs.launchpad.net/bugs/1901470/+attachment/5427760/+files/XorgLogOld.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901470 Title: resolution not listed in xrandr from ASUS ROG PG278QR via HDMI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1901470/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901470] Re: resolution not listed in xrandr from ASUS ROG PG278QR via HDMI
apport information ** Tags added: apport-collected ubuntu ** Description changed: The PG278QR monitor supports 2560x1440. After installing Ubuntu 20.4, the max resolution presented in the Settings app is 1920x1080, and this resolution is the one that it uses. Switching between the Nvidia driver or the Intel driver (laptop has low-power intel gpu too) doesn't correct the problem. Digging in deeper, based on https://wiki.ubuntu.com/X/Troubleshooting/Resolution#Problem:__Wrong_resolutions.2C_refresh_rates.2C_or_monitor_specs Under Wrong resolutions/refresh rates/or monitor specs, step 3 is to use get-edid | parse-edid. After applying the mode that I wanted manually via xrandr --newmode and xrandr --addmode, I was able to select the max resolution of the monitor and works correctly, until reboot. I will add it to my xorg.conf next. Here is information I collected: output from xrandr after fresh boot: ~$ xrandr Screen 0: minimum 8 x 8, current 3840 x 1080, maximum 32767 x 32767 eDP-1-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 344mm x 193mm 1920x1080 60.01*+ 60.0159.9759.9659.93 1680x1050 59.9559.88 1600x1024 60.17 1400x1050 59.98 1600x900 59.9959.9459.9559.82 1280x1024 60.02 1440x900 59.89 1400x900 59.9659.88 1280x960 60.00 1440x810 60.0059.97 1368x768 59.8859.85 1360x768 59.8059.96 1280x800 59.9959.9759.8159.91 1152x864 60.00 1280x720 60.0059.9959.8659.74 1024x768 60.0460.00 960x720 60.00 928x696 60.05 896x672 60.01 1024x576 59.9559.9659.9059.82 960x600 59.9360.00 960x540 59.9659.9959.6359.82 800x600 60.0060.3256.25 840x525 60.0159.88 864x486 59.9259.57 800x512 60.17 700x525 59.98 800x450 59.9559.82 640x512 60.02 720x450 59.89 700x450 59.9659.88 640x480 60.0059.94 720x405 59.5158.99 684x384 59.8859.85 680x384 59.8059.96 640x400 59.8859.98 576x432 60.06 640x360 59.8659.8359.8459.32 512x384 60.00 512x288 60.0059.92 480x270 59.6359.82 400x300 60.3256.34 432x243 59.9259.57 320x240 60.05 360x202 59.5159.13 320x180 59.8459.32 HDMI-1-1 connected 1920x1080+1920+0 (normal left inverted right x axis y axis) 598mm x 336mm 1920x1080 60.00* 50.0059.94 1280x720 60.0050.0059.94 1024x768 60.00 800x600 60.32 720x576 50.00 720x480 60.0059.94 640x480 60.0059.94 DP-1-1 disconnected (normal left inverted right x axis y axis) output from get-edid | parse-edid: ~$ sudo get-edid | parse-edid This is read-edid version 3.0.2. Prepare for some fun. Attempting to use i2c interface No EDID on bus 1 No EDID on bus 2 No EDID on bus 3 No EDID on bus 5 No EDID on bus 6 No EDID on bus 7 No EDID on bus 9 No EDID on bus 10 3 potential busses found: 0 4 8 Will scan through until the first EDID is found. Pass a bus number as an option to this program to go only for that one. Bus 0 doesn't really have an EDID... 256-byte EDID successfully retrieved from i2c bus 4 Looks like i2c was successful. Have a good day. Checksum Correct Section "Monitor" Identifier "ROG PG278QR" ModelName "ROG PG278QR" VendorName "AUS" # Monitor Manufactured week 47 of 2016 # EDID version 1.3 # Digital Display DisplaySize 600 340 Gamma 2.20 Option "DPMS" "false" Horizsync 30-140 VertRefresh 24-60 # Maximum pixel clock is 300MHz #Extension block found. Parsing... Modeline"Mode 1" 148.500 1920 2008 2052 2200 1080 1084 1089 1125 +hsync +vsync Modeline"Mode 0" 241.50 2560 2608 2640 2720 1440 1443 1448 1481 +hsync -vsync Modeline"Mode 2" 148.500 1920 2448 2492 2640 1080 1084 1089 1125 +hsync +vsync Modeline"Mode 3" 74.250 1280 1390 1420 1650 720 725 730 750 +hsync +vsync Modeline"Mode 4" 74.250 1280 1720 1760 1980 720 725 730 750 +hsync +vsync Modeline"Mode 5" 27.027 720 736 798 858 480 489 495 525 -hsync -vsync Modeline"Mode 6" 27.000 720 732 796 864 576 581 586 625 -hsync -vsync Modeline"Mode 7" 25.200 640 656 752 800 480 490 492 525 -hsync
[Bug 1901470] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1901470/+attachment/5427741/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901470 Title: resolution not listed in xrandr from ASUS ROG PG278QR via HDMI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1901470/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901470] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1901470/+attachment/5427753/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901470 Title: resolution not listed in xrandr from ASUS ROG PG278QR via HDMI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1901470/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901470] XorgLog.txt
apport information ** Attachment added: "XorgLog.txt" https://bugs.launchpad.net/bugs/1901470/+attachment/5427759/+files/XorgLog.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901470 Title: resolution not listed in xrandr from ASUS ROG PG278QR via HDMI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1901470/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901470] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1901470/+attachment/5427745/+files/Lsusb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901470 Title: resolution not listed in xrandr from ASUS ROG PG278QR via HDMI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1901470/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901470] Lsusb-t.txt
apport information ** Attachment added: "Lsusb-t.txt" https://bugs.launchpad.net/bugs/1901470/+attachment/5427746/+files/Lsusb-t.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901470 Title: resolution not listed in xrandr from ASUS ROG PG278QR via HDMI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1901470/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901470] MonitorsUser.xml.txt
apport information ** Attachment added: "MonitorsUser.xml.txt" https://bugs.launchpad.net/bugs/1901470/+attachment/5427748/+files/MonitorsUser.xml.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901470 Title: resolution not listed in xrandr from ASUS ROG PG278QR via HDMI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1901470/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901470] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1901470/+attachment/5427754/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901470 Title: resolution not listed in xrandr from ASUS ROG PG278QR via HDMI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1901470/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901470] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1901470/+attachment/5427750/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901470 Title: resolution not listed in xrandr from ASUS ROG PG278QR via HDMI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1901470/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901470] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1901470/+attachment/5427743/+files/Lspci.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901470 Title: resolution not listed in xrandr from ASUS ROG PG278QR via HDMI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1901470/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901470] Re: resolution not listed in xrandr from ASUS ROG PG278QR via HDMI
** Attachment added: "after xrandr --addmode" https://bugs.launchpad.net/ubuntu/+bug/1901470/+attachment/5427131/+files/Screenshot%20from%202020-10-26%2013-23-41.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901470 Title: resolution not listed in xrandr from ASUS ROG PG278QR via HDMI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1901470/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901470] [NEW] resolution not listed in xrandr from ASUS ROG PG278QR via HDMI
Public bug reported: The PG278QR monitor supports 2560x1440. After installing Ubuntu 20.4, the max resolution presented in the Settings app is 1920x1080, and this resolution is the one that it uses. Switching between the Nvidia driver or the Intel driver (laptop has low-power intel gpu too) doesn't correct the problem. Digging in deeper, based on https://wiki.ubuntu.com/X/Troubleshooting/Resolution#Problem:__Wrong_resolutions.2C_refresh_rates.2C_or_monitor_specs Under Wrong resolutions/refresh rates/or monitor specs, step 3 is to use get-edid | parse-edid. After applying the mode that I wanted manually via xrandr --newmode and xrandr --addmode, I was able to select the max resolution of the monitor and works correctly, until reboot. I will add it to my xorg.conf next. Here is information I collected: output from xrandr after fresh boot: ~$ xrandr Screen 0: minimum 8 x 8, current 3840 x 1080, maximum 32767 x 32767 eDP-1-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 344mm x 193mm 1920x1080 60.01*+ 60.0159.9759.9659.93 1680x1050 59.9559.88 1600x1024 60.17 1400x1050 59.98 1600x900 59.9959.9459.9559.82 1280x1024 60.02 1440x900 59.89 1400x900 59.9659.88 1280x960 60.00 1440x810 60.0059.97 1368x768 59.8859.85 1360x768 59.8059.96 1280x800 59.9959.9759.8159.91 1152x864 60.00 1280x720 60.0059.9959.8659.74 1024x768 60.0460.00 960x720 60.00 928x696 60.05 896x672 60.01 1024x576 59.9559.9659.9059.82 960x600 59.9360.00 960x540 59.9659.9959.6359.82 800x600 60.0060.3256.25 840x525 60.0159.88 864x486 59.9259.57 800x512 60.17 700x525 59.98 800x450 59.9559.82 640x512 60.02 720x450 59.89 700x450 59.9659.88 640x480 60.0059.94 720x405 59.5158.99 684x384 59.8859.85 680x384 59.8059.96 640x400 59.8859.98 576x432 60.06 640x360 59.8659.8359.8459.32 512x384 60.00 512x288 60.0059.92 480x270 59.6359.82 400x300 60.3256.34 432x243 59.9259.57 320x240 60.05 360x202 59.5159.13 320x180 59.8459.32 HDMI-1-1 connected 1920x1080+1920+0 (normal left inverted right x axis y axis) 598mm x 336mm 1920x1080 60.00* 50.0059.94 1280x720 60.0050.0059.94 1024x768 60.00 800x600 60.32 720x576 50.00 720x480 60.0059.94 640x480 60.0059.94 DP-1-1 disconnected (normal left inverted right x axis y axis) output from get-edid | parse-edid: ~$ sudo get-edid | parse-edid This is read-edid version 3.0.2. Prepare for some fun. Attempting to use i2c interface No EDID on bus 1 No EDID on bus 2 No EDID on bus 3 No EDID on bus 5 No EDID on bus 6 No EDID on bus 7 No EDID on bus 9 No EDID on bus 10 3 potential busses found: 0 4 8 Will scan through until the first EDID is found. Pass a bus number as an option to this program to go only for that one. Bus 0 doesn't really have an EDID... 256-byte EDID successfully retrieved from i2c bus 4 Looks like i2c was successful. Have a good day. Checksum Correct Section "Monitor" Identifier "ROG PG278QR" ModelName "ROG PG278QR" VendorName "AUS" # Monitor Manufactured week 47 of 2016 # EDID version 1.3 # Digital Display DisplaySize 600 340 Gamma 2.20 Option "DPMS" "false" Horizsync 30-140 VertRefresh 24-60 # Maximum pixel clock is 300MHz #Extension block found. Parsing... Modeline"Mode 1" 148.500 1920 2008 2052 2200 1080 1084 1089 1125 +hsync +vsync Modeline"Mode 0" 241.50 2560 2608 2640 2720 1440 1443 1448 1481 +hsync -vsync Modeline"Mode 2" 148.500 1920 2448 2492 2640 1080 1084 1089 1125 +hsync +vsync Modeline"Mode 3" 74.250 1280 1390 1420 1650 720 725 730 750 +hsync +vsync Modeline"Mode 4" 74.250 1280 1720 1760 1980 720 725 730 750 +hsync +vsync Modeline"Mode 5" 27.027 720 736 798 858 480 489 495 525 -hsync -vsync Modeline"Mode 6" 27.000 720 732 796 864 576 581 586 625 -hsync -vsync Modeline"Mode 7" 25.200 640 656 752 800 480 490 492 525 -hsync -vsync Option "PreferredMode" "Mode 1" EndSection "Mode 0" above is the mode that I want to use, which doesn't appear in the Settings app list of available resolutions. I used "Mode 0" to via xrandr --newmode: ~$ xrandr --newmode "Mode 0" 241.50 2560 2608 2640
[Bug 1861936] Re: Raspberry Pi 3 network dies shortly after a burst of IPv6 tunnel network load ((lan78xx): transmit queue 0 timed out)
@mlx I'm running eth0 in bridge, and also using a tunnel broker ipv6 tunnel like the original poster. How would I go about running the testing kernel? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1861936 Title: Raspberry Pi 3 network dies shortly after a burst of IPv6 tunnel network load ((lan78xx): transmit queue 0 timed out) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1861936/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1861936] Re: Raspberry Pi 3 network dies shortly after a burst of IPv6 tunnel network load ((lan78xx): transmit queue 0 timed out)
I can confirm having the same issue, including on multiple raspberry pi 3s, one with an IPv6 tunnel from tunnelbroker.net, and one without. It can be triggered by a lot of IPv4 traffic for me as well. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1861936 Title: Raspberry Pi 3 network dies shortly after a burst of IPv6 tunnel network load ((lan78xx): transmit queue 0 timed out) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1861936/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1870356] Re: Can't connect to paired bluetooth devices via g-c-c
I've actually found if you keep toggling the switch it will eventually work. Sometimes it only takes a couple or other times I've clicked it 30 times. Before I discovered this I was removing and re-adding my devices to get them to reconnect. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1870356 Title: Can't connect to paired bluetooth devices via g-c-c To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1870356/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1879322] Re: syslog filling up root partition
** Description changed: New MATE 20.04 installation with all original settings for Power Management and Screensaver on desktop computer. After awakening computer from Screensaver, explosion of log entries in syslog fills up root partition (normal free space is 20GB). If explosion does not occur on first awakening from Screensaver then retry several more times. Here is sample from syslog: May 17 17:03:34 jim-pc org.mate.panel.applet.BriskMenuFactory[14549]: move 0 from 1 to 6 (-1) Prio: 104 May 17 17:03:34 jim-pc org.mate.panel.applet.BriskMenuFactory[14549]: move 0 from 2 to 3 (-1) Prio: 4 May 17 17:03:34 jim-pc org.mate.panel.applet.BriskMenuFactory[14549]: move 5 from 9 to 3 (-1) Prio: 9 May 17 17:03:34 jim-pc org.mate.panel.applet.BriskMenuFactory[14549]: move 0 from 6 to 2 (-1) Prio: 7 May 17 17:03:34 jim-pc org.mate.panel.applet.BriskMenuFactory[14549]: move 0 from 6 to 3 (-1) Prio: 49 May 17 17:03:34 jim-pc org.mate.panel.applet.BriskMenuFactory[14549]: move 1 from 6 to 3 (-1) Prio: 44 May 17 17:03:34 jim-pc org.mate.panel.applet.BriskMenuFactory[14549]: move 2 from 6 to 3 (-1) Prio: 39 May 17 17:03:34 jim-pc org.mate.panel.applet.BriskMenuFactory[14549]: move 3 from 6 to 3 (-1) Prio: 34 May 17 17:03:34 jim-pc org.mate.panel.applet.BriskMenuFactory[14549]: move 4 from 9 to 3 (-1) Prio: 14 May 17 17:03:34 jim-pc org.mate.panel.applet.BriskMenuFactory[14549]: move 4 from 6 to 3 (-1) Prio: 29 May 17 17:03:34 jim-pc org.mate.panel.applet.BriskMenuFactory[14549]: move 5 from 6 to 3 (-1) Prio: 24 May 17 17:03:34 jim-pc org.mate.panel.applet.BriskMenuFactory[14549]: move 6 from 6 to 3 (-1) Prio: 19 May 17 17:03:34 jim-pc org.mate.panel.applet.BriskMenuFactory[14549]: move 3 from 9 to 3 (-1) Prio: 19 May 17 17:03:34 jim-pc org.mate.panel.applet.BriskMenuFactory[14549]: move 7 from 6 to 3 (-1) Prio: 14 LATER: After a week of further testing, I believe my problem to be heat related. Specifically, the syslog - "jim-pc org.mate.panel.applet.BriskMenuFactory[14549]" - explosion occurs after 4 or 5 hours of the computer being turned on. If no one else is having this problem, I think it's safe to conclude that the problem is specific to my hardware. Have run stress-ng. No errors showing up. Set up logrotate. Up to 3GB in syslog after only 3 hours run time. + + After a week of trying to resolve issue, I have reinstalled MATE 18.04. + This resolved my issue of syslog filling up. I did, however, save a copy + of my 3GB syslog file. I can upload this to Google Drive or DropBox if + it would help resolve this issue. Contact me at jharris1112@gmaildotcom -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1879322 Title: syslog filling up root partition To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1879322/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1879322] Re: syslog filling up root partition
** Description changed: New MATE 20.04 installation with all original settings for Power Management and Screensaver on desktop computer. After awakening computer from Screensaver, explosion of log entries in syslog fills up root partition (normal free space is 20GB). If explosion does not occur on first awakening from Screensaver then retry several more times. Here is sample from syslog: May 17 17:03:34 jim-pc org.mate.panel.applet.BriskMenuFactory[14549]: move 0 from 1 to 6 (-1) Prio: 104 May 17 17:03:34 jim-pc org.mate.panel.applet.BriskMenuFactory[14549]: move 0 from 2 to 3 (-1) Prio: 4 May 17 17:03:34 jim-pc org.mate.panel.applet.BriskMenuFactory[14549]: move 5 from 9 to 3 (-1) Prio: 9 May 17 17:03:34 jim-pc org.mate.panel.applet.BriskMenuFactory[14549]: move 0 from 6 to 2 (-1) Prio: 7 May 17 17:03:34 jim-pc org.mate.panel.applet.BriskMenuFactory[14549]: move 0 from 6 to 3 (-1) Prio: 49 May 17 17:03:34 jim-pc org.mate.panel.applet.BriskMenuFactory[14549]: move 1 from 6 to 3 (-1) Prio: 44 May 17 17:03:34 jim-pc org.mate.panel.applet.BriskMenuFactory[14549]: move 2 from 6 to 3 (-1) Prio: 39 May 17 17:03:34 jim-pc org.mate.panel.applet.BriskMenuFactory[14549]: move 3 from 6 to 3 (-1) Prio: 34 May 17 17:03:34 jim-pc org.mate.panel.applet.BriskMenuFactory[14549]: move 4 from 9 to 3 (-1) Prio: 14 May 17 17:03:34 jim-pc org.mate.panel.applet.BriskMenuFactory[14549]: move 4 from 6 to 3 (-1) Prio: 29 May 17 17:03:34 jim-pc org.mate.panel.applet.BriskMenuFactory[14549]: move 5 from 6 to 3 (-1) Prio: 24 May 17 17:03:34 jim-pc org.mate.panel.applet.BriskMenuFactory[14549]: move 6 from 6 to 3 (-1) Prio: 19 May 17 17:03:34 jim-pc org.mate.panel.applet.BriskMenuFactory[14549]: move 3 from 9 to 3 (-1) Prio: 19 May 17 17:03:34 jim-pc org.mate.panel.applet.BriskMenuFactory[14549]: move 7 from 6 to 3 (-1) Prio: 14 LATER: After a week of further testing, I believe my problem to be heat related. Specifically, the syslog - "jim-pc org.mate.panel.applet.BriskMenuFactory[14549]" - explosion occurs after 4 or 5 hours of the computer being turned on. If no one else is having this problem, I think it's safe to conclude that the problem is specific - to my hardware. Thanks, + to my hardware. + + Have run stress-ng. No errors showing up. Set up logrotate. Up to 3GB in + syslog after only 3 hours run time. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1879322 Title: syslog filling up root partition To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1879322/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1879322] Re: syslog filling up root partition
** Description changed: New MATE 20.04 installation with all original settings for Power Management and Screensaver on desktop computer. After awakening computer from Screensaver, explosion of log entries in syslog fills up root partition (normal free space is 20GB). If explosion does not occur on first awakening from Screensaver then retry several more times. Here is sample from syslog: May 17 17:03:34 jim-pc org.mate.panel.applet.BriskMenuFactory[14549]: move 0 from 1 to 6 (-1) Prio: 104 May 17 17:03:34 jim-pc org.mate.panel.applet.BriskMenuFactory[14549]: move 0 from 2 to 3 (-1) Prio: 4 May 17 17:03:34 jim-pc org.mate.panel.applet.BriskMenuFactory[14549]: move 5 from 9 to 3 (-1) Prio: 9 May 17 17:03:34 jim-pc org.mate.panel.applet.BriskMenuFactory[14549]: move 0 from 6 to 2 (-1) Prio: 7 May 17 17:03:34 jim-pc org.mate.panel.applet.BriskMenuFactory[14549]: move 0 from 6 to 3 (-1) Prio: 49 May 17 17:03:34 jim-pc org.mate.panel.applet.BriskMenuFactory[14549]: move 1 from 6 to 3 (-1) Prio: 44 May 17 17:03:34 jim-pc org.mate.panel.applet.BriskMenuFactory[14549]: move 2 from 6 to 3 (-1) Prio: 39 May 17 17:03:34 jim-pc org.mate.panel.applet.BriskMenuFactory[14549]: move 3 from 6 to 3 (-1) Prio: 34 May 17 17:03:34 jim-pc org.mate.panel.applet.BriskMenuFactory[14549]: move 4 from 9 to 3 (-1) Prio: 14 May 17 17:03:34 jim-pc org.mate.panel.applet.BriskMenuFactory[14549]: move 4 from 6 to 3 (-1) Prio: 29 May 17 17:03:34 jim-pc org.mate.panel.applet.BriskMenuFactory[14549]: move 5 from 6 to 3 (-1) Prio: 24 May 17 17:03:34 jim-pc org.mate.panel.applet.BriskMenuFactory[14549]: move 6 from 6 to 3 (-1) Prio: 19 May 17 17:03:34 jim-pc org.mate.panel.applet.BriskMenuFactory[14549]: move 3 from 9 to 3 (-1) Prio: 19 May 17 17:03:34 jim-pc org.mate.panel.applet.BriskMenuFactory[14549]: move 7 from 6 to 3 (-1) Prio: 14 + + LATER: After a week of further testing, I believe my problem to be heat + related. Specifically, the syslog - "jim-pc + org.mate.panel.applet.BriskMenuFactory[14549]" - explosion occurs after + 4 or 5 hours of the computer being turned on. If no one else is having + this problem, I think it's safe to conclude that the problem is specific + to my hardware. Thanks, -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1879322 Title: syslog filling up root partition To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1879322/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1877655] Re: [Dell Venue 11 Pro 7140] Trackpad does not work
Any other suggestions for what I should try? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1877655 Title: [Dell Venue 11 Pro 7140] Trackpad does not work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1877655/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1877655] Re: [Dell Venue 11 Pro 7140] Trackpad does not work
Gave it a go - similar results to what happens when I first power it up and log in - the trackpad controls the pointer for a few seconds then stops once the desktop (I assume) is done loading. Is there any kind of command to find out what devices X and/or gnome is responding to? It almost feels like it might be switching from (I know this is not right, but just using it as reference) hidraw0 to hidraw3 ignoring hidraw0? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1877655 Title: [Dell Venue 11 Pro 7140] Trackpad does not work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1877655/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1877655] Re: [Dell Venue 11 Pro 7140] Trackpad does not work
No change. Still stops working after a few seconds once the full desktop is active. Also I notice once it stops working at that point, if I log out the trackpad continues to not work at the logon screen. Rebooting the system brings back trackpad functionality until I log back in. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1877655 Title: [Dell Venue 11 Pro 7140] Trackpad does not work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1877655/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1877655] Re: [Dell Venue 11 Pro 7140] Trackpad does not work
I assume you mean output from hid-recorder - I'll attach the 4 files one at a time: This one contains hidraw0 which is the touchpad input - data in it includes me moving my finger on the touch pad. ** Attachment added: "hidraw0" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1877655/+attachment/5370364/+files/hidraw0 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1877655 Title: [Dell Venue 11 Pro 7140] Trackpad does not work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1877655/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1877655] Re: [Dell Venue 11 Pro 7140] Trackpad does not work
This last one is hidraw3 - I have NO CLUE what this one is. ** Attachment added: "hidraw3" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1877655/+attachment/5370367/+files/hidraw3 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1877655 Title: [Dell Venue 11 Pro 7140] Trackpad does not work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1877655/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1877655] Re: [Dell Venue 11 Pro 7140] Trackpad does not work
This one is hidraw1, it is the keyboard (see sample keypresses in the output) ** Attachment added: "hidraw1" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1877655/+attachment/5370365/+files/hidraw1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1877655 Title: [Dell Venue 11 Pro 7140] Trackpad does not work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1877655/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1877655] Re: [Dell Venue 11 Pro 7140] Trackpad does not work
This is hidraw2 which is the touch screen, I let it record me touching and moving my finger on the screen. ** Attachment added: "hidraw2" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1877655/+attachment/5370366/+files/hidraw2 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1877655 Title: [Dell Venue 11 Pro 7140] Trackpad does not work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1877655/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1877655] Re: [Dell Venue 11 Pro 7140] Trackpad does not work
vanvugt: Well, I ran into a little issue. I went ahead and did a reinstall of ubuntu (at the point when I submitted my original bug, I was running PopOS). Before ANY updates, the trackpad works as it should until I launch software center (or even dmesg -w). The instant I run one of those, the track pad stops working. (kernel 5.4.0-26-generic). This activity is the same in Wayland and Xorg. After I did an update to bring it to the latest updates (kernel 5.4.0.29-generic + whatever else needed to be updated from the current ISO downloadable from Ubuntu (I downloaded it this morning to reinstall)) the trackpad works at the login screen as it should (clicks and everything), but once the full desktop is brought up it stops working. It will actually work for a few seconds until the desktop is done loading. kaihengfeng: Ok, this was interesting. I downloaded the tool and ran it, the first interesting thing is that there are 4 entries listed for the input, 3 of which are listed for Synaptics pad - /dev/hidraw0: Synaptics T Pad V 01.31 /dev/hidraw1: Synaptics T Pad V 01.31 /dev/hidraw2: SYNA7500:00 06CB:780E /dev/hidraw3: Synaptics T Pad V 01.31 hidraw0 gives data feed back as I move my finger over the trackpad, clicking the buttons show data scrolling similar to as I move my finger on the trackpad hidraw1 give basic info, but no data feed back as I click or move my finger on the trackpad - this appears to be the hid interface of the keyboard, as I press keys it shows what key I press hidraw2 Is the touch screen of the tablet portion, it gives feed back as I move my finger on the screen hidraw3 I have NO idea what this is, keypresses do nothing, trackpad interaction does nothing, touch screen does nothing, buttons on the side of the screen (volume up/down) do not trigger any feedback hidraw0 is definitely the trackpad input; I wonder if somehow when the desktop pulls up its changing what it thinks it should use for the trackpad from hidraw0 to hidraw3? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1877655 Title: [Dell Venue 11 Pro 7140] Trackpad does not work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1877655/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1877655] xdpyinfo.txt
apport information ** Attachment added: "xdpyinfo.txt" https://bugs.launchpad.net/bugs/1877655/+attachment/5369853/+files/xdpyinfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1877655 Title: Synaptic Trackpad does not work in Xorg sessions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1877655/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1877655] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1877655/+attachment/5369849/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1877655 Title: Synaptic Trackpad does not work in Xorg sessions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1877655/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1877655] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1877655/+attachment/5369851/+files/UdevDb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1877655 Title: Synaptic Trackpad does not work in Xorg sessions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1877655/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1877655] Xrandr.txt
apport information ** Attachment added: "Xrandr.txt" https://bugs.launchpad.net/bugs/1877655/+attachment/5369852/+files/Xrandr.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1877655 Title: Synaptic Trackpad does not work in Xorg sessions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1877655/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1877655] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1877655/+attachment/5369847/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1877655 Title: Synaptic Trackpad does not work in Xorg sessions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1877655/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1877655] Re: Synaptic Trackpad does not work in Xorg sessions
I should note - I did try out xserver-xorg-input-synaptics yesterday prior to getting your email, it had no effect One thing I did find, I'm not sure if it has any bearing, but my current kernel is: 5.4.0-7626-generic With this kernel, as I mentioned before I could move the trackpad at the login screen, but the buttons didn't work; on login, no mouse input worked. I came across a thread about certain kernels having regression issues with certain trackpads, so I tried the original kernel that came with my distribution: 5.4.0-7625-generic Now, with that kernel, at the login screen I can move the trackpad AND use the trackpad buttons; still once I'm fully logged into the desktop the trackpad doesn't work at all. As I mentioned, not sure if this has any bearing, but I thought I should mention it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1877655 Title: Synaptic Trackpad does not work in Xorg sessions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1877655/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1877655] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1877655/+attachment/5369848/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1877655 Title: Synaptic Trackpad does not work in Xorg sessions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1877655/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1877655] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1877655/+attachment/5369850/+files/ProcModules.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1877655 Title: Synaptic Trackpad does not work in Xorg sessions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1877655/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1877655] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1877655/+attachment/5369841/+files/Lspci.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1877655 Title: Synaptic Trackpad does not work in Xorg sessions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1877655/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1877655] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1877655/+attachment/5369838/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1877655 Title: Synaptic Trackpad does not work in Xorg sessions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1877655/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1877655] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/1877655/+attachment/5369845/+files/Lsusb-v.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1877655 Title: Synaptic Trackpad does not work in Xorg sessions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1877655/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1877655] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1877655/+attachment/5369843/+files/Lsusb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1877655 Title: Synaptic Trackpad does not work in Xorg sessions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1877655/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1877655] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/1877655/+attachment/5369842/+files/Lspci-vt.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1877655 Title: Synaptic Trackpad does not work in Xorg sessions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1877655/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1877655] Re: Synaptic Trackpad does not work in Xorg sessions
apport information ** Tags added: apport-collected ubuntu ** Description changed: I have a Dell Venue Pro 7140 with the keyboard/trackpad/extra battery dock. PopOS 20.04 fully updated. I have experienced this bug on stock Ubuntu 20.04 as well as Kubuntu 20.04. When at the login page, the trackpad and keyboard operate as they should. Once the login process is complete and the desktop is displayed, the keyboard still works as expected but the trackpad no longer controls the pointer. The touch display still functions as expected but the trackpad on the keyboard dock doesn't work. The attached document is my device list, here is the evtest: Input driver version is 1.0.1 Input device ID: bus 0x3 vendor 0x6cb product 0x2819 version 0x111 Input device name: "Synaptics T Pad V 01.31 Touchpad" Supported events: Event type 0 (EV_SYN) Event type 1 (EV_KEY) Event code 272 (BTN_LEFT) Event code 325 (BTN_TOOL_FINGER) Event code 330 (BTN_TOUCH) Event code 333 (BTN_TOOL_DOUBLETAP) Event code 334 (BTN_TOOL_TRIPLETAP) Event type 3 (EV_ABS) Event code 0 (ABS_X) Value483 Min0 Max 1056 Resolution 12 Event code 1 (ABS_Y) Value266 Min0 Max 516 Resolution 12 Event code 47 (ABS_MT_SLOT) Value 0 Min0 Max2 Event code 53 (ABS_MT_POSITION_X) Value 0 Min0 Max 1056 Resolution 12 Event code 54 (ABS_MT_POSITION_Y) Value 0 Min0 Max 516 Resolution 12 Event code 55 (ABS_MT_TOOL_TYPE) Value 0 Min0 Max2 Event code 57 (ABS_MT_TRACKING_ID) Value 0 Min0 Max65535 Event type 4 (EV_MSC) Event code 5 (MSC_TIMESTAMP) Properties: Property type 0 (INPUT_PROP_POINTER) Property type 2 (INPUT_PROP_BUTTONPAD) Testing ... (interrupt to exit) I did try to remove xserver-xorg-input-synaptics, but it is not installed on 20.04. - There is still an issue with Wayland and the trackpad, but it's - different than Xorg so the problem may be in how Xorg is processing the - trackpad (I honestly don't know) - in Wayland, it will work until I - attempt to run the sofware center. + There is still an issue with Wayland and the trackpad, but it's different than Xorg so the problem may be in how Xorg is processing the trackpad (I honestly don't know) - in Wayland, it will work until I attempt to run the sofware center. + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu27 + Architecture: amd64 + CasperMD5CheckResult: skip + CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' + CompositorRunning: None + DistUpgraded: Fresh install + DistroCodename: focal + DistroRelease: Pop!_OS 20.04 + DistroVariant: ubuntu + ExtraDebuggingInterest: Yes, if not too technical + GraphicsCard: + Intel Corporation HD Graphics 5300 [8086:161e] (rev 09) (prog-if 00 [VGA controller]) +Subsystem: Dell HD Graphics 5300 [1028:066b] + MachineType: Dell Inc. Venue 11 Pro 7140 + Package: xorg-server (not installed) + ProcKernelCmdLine: initrd=\EFI\Pop_OS-70755969-68c4-4da9-982b-a38628a19db0\initrd.img root=UUID=70755969-68c4-4da9-982b-a38628a19db0 ro quiet loglevel=0 systemd.show_status=false splash + ProcVersionSignature: Ubuntu 5.4.0-7626.30~1588169883~20.04~bbe668a-generic 5.4.30 + Tags: focal ubuntu ubuntu + Uname: Linux 5.4.0-7626-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: + + _MarkForUpload: True + dmi.bios.date: 09/10/2018 + dmi.bios.vendor: Dell Inc. + dmi.bios.version: A17 + dmi.board.name: 0XMVMH + dmi.board.vendor: Dell Inc. + dmi.board.version: A00 + dmi.chassis.type: 8 + dmi.chassis.vendor: Dell Inc. + dmi.modalias: dmi:bvnDellInc.:bvrA17:bd09/10/2018:svnDellInc.:pnVenue11Pro7140:pvr:rvnDellInc.:rn0XMVMH:rvrA00:cvnDellInc.:ct8:cvr: + dmi.product.name: Venue 11 Pro 7140 + dmi.product.sku: 066B + dmi.sys.vendor: Dell Inc. + version.compiz: compiz N/A + version.libdrm2: libdrm2 2.4.101-2 + version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 + version.libgl1-mesa-glx: libgl1-mesa-glx N/A + version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 + 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 ** Attachment added: "BootLog.txt" https://bugs.launchpad.net/bugs/1877655/+attachment/5369837/+files/BootLog.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.
[Bug 1877655] DkmsStatus.txt
apport information ** Attachment added: "DkmsStatus.txt" https://bugs.launchpad.net/bugs/1877655/+attachment/5369839/+files/DkmsStatus.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1877655 Title: Synaptic Trackpad does not work in Xorg sessions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1877655/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1877655] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1877655/+attachment/5369846/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1877655 Title: Synaptic Trackpad does not work in Xorg sessions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1877655/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1877655] Lsusb-t.txt
apport information ** Attachment added: "Lsusb-t.txt" https://bugs.launchpad.net/bugs/1877655/+attachment/5369844/+files/Lsusb-t.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1877655 Title: Synaptic Trackpad does not work in Xorg sessions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1877655/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1877655] DpkgLog.txt
apport information ** Attachment added: "DpkgLog.txt" https://bugs.launchpad.net/bugs/1877655/+attachment/5369840/+files/DpkgLog.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1877655 Title: Synaptic Trackpad does not work in Xorg sessions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1877655/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1877655] Re: Synaptic Trackpad works until actually logged into Xorg desktop
I have no idea what sub group/package this belongs in. I know it affects Gnome and KDE on Xorg. I don't know if GDM (or whatever now handles the login process) does differently from the full gnome that allows the trackpad to at least partially work (movement, but not button clicks) ** Description changed: I have a Dell Venue Pro 7140 with the keyboard/trackpad/extra battery dock. PopOS 20.04 fully updated. I have experienced this bug on stock Ubuntu 20.04 as well as Kubuntu 20.04. - When at the login page, the trackpad and keyboard operate as they + When at the login page, the trackpad and keyboard operate as they should. Once the login process is complete and the desktop is displayed, the keyboard still works as expected but the trackpad no longer controls the pointer. The touch display still functions as expected but the trackpad on the keyboard dock doesn't work. The attached document is my device list, here is the evtest: Input driver version is 1.0.1 Input device ID: bus 0x3 vendor 0x6cb product 0x2819 version 0x111 Input device name: "Synaptics T Pad V 01.31 Touchpad" Supported events: - Event type 0 (EV_SYN) - Event type 1 (EV_KEY) - Event code 272 (BTN_LEFT) - Event code 325 (BTN_TOOL_FINGER) - Event code 330 (BTN_TOUCH) - Event code 333 (BTN_TOOL_DOUBLETAP) - Event code 334 (BTN_TOOL_TRIPLETAP) - Event type 3 (EV_ABS) - Event code 0 (ABS_X) - Value483 - Min0 - Max 1056 - Resolution 12 - Event code 1 (ABS_Y) - Value266 - Min0 - Max 516 - Resolution 12 - Event code 47 (ABS_MT_SLOT) - Value 0 - Min0 - Max2 - Event code 53 (ABS_MT_POSITION_X) - Value 0 - Min0 - Max 1056 - Resolution 12 - Event code 54 (ABS_MT_POSITION_Y) - Value 0 - Min0 - Max 516 - Resolution 12 - Event code 55 (ABS_MT_TOOL_TYPE) - Value 0 - Min0 - Max2 - Event code 57 (ABS_MT_TRACKING_ID) - Value 0 - Min0 - Max65535 - Event type 4 (EV_MSC) - Event code 5 (MSC_TIMESTAMP) + Event type 0 (EV_SYN) + Event type 1 (EV_KEY) + Event code 272 (BTN_LEFT) + Event code 325 (BTN_TOOL_FINGER) + Event code 330 (BTN_TOUCH) + Event code 333 (BTN_TOOL_DOUBLETAP) + Event code 334 (BTN_TOOL_TRIPLETAP) + Event type 3 (EV_ABS) + Event code 0 (ABS_X) + Value483 + Min0 + Max 1056 + Resolution 12 + Event code 1 (ABS_Y) + Value266 + Min0 + Max 516 + Resolution 12 + Event code 47 (ABS_MT_SLOT) + Value 0 + Min0 + Max2 + Event code 53 (ABS_MT_POSITION_X) + Value 0 + Min0 + Max 1056 + Resolution 12 + Event code 54 (ABS_MT_POSITION_Y) + Value 0 + Min0 + Max 516 + Resolution 12 + Event code 55 (ABS_MT_TOOL_TYPE) + Value 0 + Min0 + Max2 + Event code 57 (ABS_MT_TRACKING_ID) + Value 0 + Min0 + Max65535 + Event type 4 (EV_MSC) + Event code 5 (MSC_TIMESTAMP) Properties: - Property type 0 (INPUT_PROP_POINTER) - Property type 2 (INPUT_PROP_BUTTONPAD) + Property type 0 (INPUT_PROP_POINTER) + Property type 2 (INPUT_PROP_BUTTONPAD) Testing ... (interrupt to exit) - - I did try to remove xserver-xorg-input-synaptics, but it is not installed on 20.04. + I did try to remove xserver-xorg-input-synaptics, but it is not + installed on 20.04. There is still an issue with Wayland and the trackpad, but it's different than Xorg so the problem may be in how Xorg is processing the trackpad (I honestly don't know) - in Wayland, it will work until I attempt to run the sofware center. ** Package changed: ubuntu => xorg (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1877655 Title: Synaptic Trackpad works until actually logged into Xorg desktop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1877655/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1877655] Re: Synaptic Trackpad works until actually logged into Xorg desktop
Update note: I just rebooted again, I somehow didn't notice, but during the login window currently, I can move the pointer with the trackpad, but the left/right click doesn't work. Once logged into the actual desktop the trackpad (still) completely ceases to work. Just wanted to fix that. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1877655 Title: Synaptic Trackpad works until actually logged into Xorg desktop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1877655/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1846539] Re: [broadwell-rt286, playback] Since Linux 5.2rc2 audio playback no longer works on Dell Venue 11 Pro 7140
I am seeing this issue with the stock kernel in Ubuntu 20.04 on a Dell Venue Pro 7140 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1846539 Title: [broadwell-rt286, playback] Since Linux 5.2rc2 audio playback no longer works on Dell Venue 11 Pro 7140 To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1846539/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1877655] [NEW] Synaptic Trackpad works until actually logged into Xorg desktop
Public bug reported: I have a Dell Venue Pro 7140 with the keyboard/trackpad/extra battery dock. PopOS 20.04 fully updated. I have experienced this bug on stock Ubuntu 20.04 as well as Kubuntu 20.04. When at the login page, the trackpad and keyboard operate as they should. Once the login process is complete and the desktop is displayed, the keyboard still works as expected but the trackpad no longer controls the pointer. The touch display still functions as expected but the trackpad on the keyboard dock doesn't work. The attached document is my device list, here is the evtest: Input driver version is 1.0.1 Input device ID: bus 0x3 vendor 0x6cb product 0x2819 version 0x111 Input device name: "Synaptics T Pad V 01.31 Touchpad" Supported events: Event type 0 (EV_SYN) Event type 1 (EV_KEY) Event code 272 (BTN_LEFT) Event code 325 (BTN_TOOL_FINGER) Event code 330 (BTN_TOUCH) Event code 333 (BTN_TOOL_DOUBLETAP) Event code 334 (BTN_TOOL_TRIPLETAP) Event type 3 (EV_ABS) Event code 0 (ABS_X) Value483 Min0 Max 1056 Resolution 12 Event code 1 (ABS_Y) Value266 Min0 Max 516 Resolution 12 Event code 47 (ABS_MT_SLOT) Value 0 Min0 Max2 Event code 53 (ABS_MT_POSITION_X) Value 0 Min0 Max 1056 Resolution 12 Event code 54 (ABS_MT_POSITION_Y) Value 0 Min0 Max 516 Resolution 12 Event code 55 (ABS_MT_TOOL_TYPE) Value 0 Min0 Max2 Event code 57 (ABS_MT_TRACKING_ID) Value 0 Min0 Max65535 Event type 4 (EV_MSC) Event code 5 (MSC_TIMESTAMP) Properties: Property type 0 (INPUT_PROP_POINTER) Property type 2 (INPUT_PROP_BUTTONPAD) Testing ... (interrupt to exit) I did try to remove xserver-xorg-input-synaptics, but it is not installed on 20.04. There is still an issue with Wayland and the trackpad, but it's different than Xorg so the problem may be in how Xorg is processing the trackpad (I honestly don't know) - in Wayland, it will work until I attempt to run the sofware center. ** Affects: ubuntu Importance: Undecided Status: New ** Attachment added: "dev.txt" https://bugs.launchpad.net/bugs/1877655/+attachment/5368593/+files/dev.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1877655 Title: Synaptic Trackpad works until actually logged into Xorg desktop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1877655/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1865088] Re: setupcon cannot handle large fonts in FONT, "putfont: KDFONTOP: Invalid argument"
I notice that the output from setupcon mentions loading the font twice.
That seems to correspond to this fragment of code in setupcon:
# FONTFILES
FONTFILES=''
if [ "$FONT" ]; then
for f in $FONT; do
FONTFILES="$FONTFILES `findfile $fontdir $f`"
RES=`findfile $fontdir $f`
if [ -z "$RES" ]; then
fdec="${f%.gz}"
RES=`findfile $fontdir $fdec`
fi
FONTFILES="$FONTFILES $RES"
done
fi
It looks to me like this will add each font file to FONTFILES twice,
once in the first line of the loop body, and once in the last.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1865088
Title:
setupcon cannot handle large fonts in FONT, "putfont: KDFONTOP:
Invalid argument"
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1865088/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1865088] [NEW] setupcon cannot handle large fonts in FONT, "putfont: KDFONTOP: Invalid argument"
Public bug reported: When I specify a large font file using the FONT variable in .console- setup, setupcon fails to load the font, reporting "putfont: KDFONTOP: Invalid argument". If I specify the same font by setting CODESET, FONTFACE, and FONTSIZE, the setupcon loads it fine. For instance, if I have the following files: bjh21@sole:~$ tail .console-setup.test* ==> .console-setup.test1 <== VERBOSE_OUTPUT="no" ACTIVE_CONSOLES="/dev/tty[1-6]" CHARMAP="UTF-8" CODESET="Uni2" FONTFACE="Terminus" FONTSIZE="32x16" ==> .console-setup.test2 <== VERBOSE_OUTPUT="no" ACTIVE_CONSOLES="/dev/tty[1-6]" CHARMAP="UTF-8" FONT=Uni2-Terminus32x16.psf.gz ==> .console-setup.test3 <== VERBOSE_OUTPUT="no" ACTIVE_CONSOLES="/dev/tty[1-6]" CHARMAP="UTF-8" FONT=Uni2-Terminus16.psf.gz Running "setupcon test1" correctly loads Uni2-Terminus32x16, but "setupcon test2" does not, reporting "putfont: KDFONTOP: Invalid argument". "setupcon test3" works, demonstrating that not all uses of FONT are broken. I've attached the verbose output from "setupcon -v test2". ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: console-setup 1.178ubuntu2.9 ProcVersionSignature: Ubuntu 4.15.0-88.88-generic 4.15.18 Uname: Linux 4.15.0-88-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.11 Architecture: i386 CurrentDesktop: Unity:Unity7:ubuntu Date: Thu Feb 27 20:40:08 2020 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-motts-20100121-3 EcryptfsInUse: Yes InstallationDate: Installed on 2010-06-09 (3550 days ago) InstallationMedia: Ubuntu GNU/Linux 9.10 "Karmic" - Build i386 LIVE Binary 20100121-21:52 PackageArchitecture: all SourcePackage: console-setup UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: console-setup (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug bionic i386 ** Attachment added: "Output from "setupcon -v test2"" https://bugs.launchpad.net/bugs/1865088/+attachment/5331723/+files/setupcon.out -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1865088 Title: setupcon cannot handle large fonts in FONT, "putfont: KDFONTOP: Invalid argument" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1865088/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1862987] Re: qtbase5-private-dev does not install private headers for QtWayland
** Patch removed: "qtwayland-opensource-src-package-qtwayland-private-headers-as-qtwayland5-private-dev-package.diff" https://bugs.launchpad.net/ubuntu/+source/qtwayland-opensource-src/+bug/1862987/+attachment/5327746/+files/qtwayland-opensource-src-package-qtwayland-private-headers-as-qtwayland5-private-dev-package.diff ** Patch added: "qtwayland-opensource-src-package-qtwayland-private-headers-as-qtwayland5-private-dev-package.diff" https://bugs.launchpad.net/ubuntu/+source/qtwayland-opensource-src/+bug/1862987/+attachment/5327747/+files/qtwayland-opensource-src-package-qtwayland-private-headers-as-qtwayland5-private-dev-package.diff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1862987 Title: qtbase5-private-dev does not install private headers for QtWayland To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtwayland-opensource-src/+bug/1862987/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1862987] Re: qtbase5-private-dev does not install private headers for QtWayland
** Patch added: "qtwayland-opensource-src-package-qtwayland-private-headers-as-qtwayland5-private-dev-package.diff" https://bugs.launchpad.net/ubuntu/+source/qtwayland-opensource-src/+bug/1862987/+attachment/5327746/+files/qtwayland-opensource-src-package-qtwayland-private-headers-as-qtwayland5-private-dev-package.diff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1862987 Title: qtbase5-private-dev does not install private headers for QtWayland To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtwayland-opensource-src/+bug/1862987/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1862987] Re: qtbase5-private-dev does not install private headers for QtWayland
Upon further inspection I think qtwayland-opensource-src is the package this bug should be filed against. ** Package changed: qtbase-opensource-src (Ubuntu) => qtwayland- opensource-src (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1862987 Title: qtbase5-private-dev does not install private headers for QtWayland To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtwayland-opensource-src/+bug/1862987/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1862987] [NEW] qtbase5-private-dev does not install private headers for QtWayland
Public bug reported: Trying to build QGNOMEPlatform (https://github.com/FedoraQt/QGnomePlatform/releases) fails with the following error message: Project ERROR: Unknown module(s) in QT: waylandclient-private Running `dpkg -L qtbase5-private-dev | grep -i wayland` shows nothing, running `apt-file search /usr/include/x86_64-linux- gnu/qt5/QtWaylandClient/5.12.5/QtWaylandClient/private` also returns nothing. I also tried installing qtbase5-private-dev in a Debian container and they have the same issue so it may be worth notifying them if you fix this. ** Affects: qtbase-opensource-src (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1862987 Title: qtbase5-private-dev does not install private headers for QtWayland To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1862987/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1854601] Re: Ubiquity installation says "You can try Ubuntu without making any changes to your computer directly from this CD
This affects me, too. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1854601 Title: Ubiquity installation says "You can try Ubuntu without making any changes to your computer directly from this CD To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1854601/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1851229] [NEW] device_list:268: no soundcards found
Public bug reported: Couldn't play my music because gstreamer wasn't installed. After installation of gstreamer music can play but can't be heard. System settings have dummy output as the selected sound card. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-170.220-generic 3.13.11-ckt39 Uname: Linux 3.13.0-170-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.29 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: Unity Date: Mon Nov 4 11:33:59 2019 PackageArchitecture: all ProcEnviron: LANGUAGE=en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty uec-images -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1851229 Title: device_list:268: no soundcards found To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1851229/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1839793] [NEW] Crash during install.
Public bug reported: I was installing Ubuntu Mate 19.04 on a Dell XPS17 which has 16 GB RAM and 2 1TB SHDD drives. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: ubiquity 19.04.9 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CasperVersion: 1.405 Date: Sun Aug 11 19:49:52 2019 InstallCmdLine: file=/cdrom/preseed/ubuntu-mate.seed boot=casper initrd=/casper/initrd quiet splash --- maybe-ubiquity LiveMediaBuild: Ubuntu-MATE 19.04 "Disco Dingo" - Release amd64 (20190416) ProcEnviron: LANGUAGE=en_US.UTF-8 PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 LC_NUMERIC=C.UTF-8 SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco ubiquity-19.04.9 ubuntu-mate -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1839793 Title: Crash during install. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1839793/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1793780] Re: Clipit broken on Cosmic
Broken on 19.04, at least under unity-desktop. Downgrading works, however the notification icon is a red circle with a diagonal line going through it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1793780 Title: Clipit broken on Cosmic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/clipit/+bug/1793780/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1837335] Re: Screen goes to black after a few seconds using 19.04
Chris: Thank you for your quick response. Graphics: Intel® HD Graphics 520 (Skylake GT2) The install was an upgrade from 18.04 LTS to 18.04 to 19.04. After the upgrade was completed, I could not understand why my Dell laptop screen was blanking out. I discovered that my "color management profile" was in the "on" position and that was causing the screen blackout. I clicked on Settings, Devices, Color, Laptop Screen. There I found that the color setting was defaulted to the "on" position for my Dell Inspiron 15-7599. I turned off that setting and the problem disappeared. The screen works normally. I may consider removing that specific color profile to avoid the problem in future upgrades. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1837335 Title: Screen goes to black after a few seconds using 19.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/virt-manager/+bug/1837335/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1837335] [NEW] Screen goes to black after a few seconds using 19.04
Public bug reported: The screen started to "blank out" (goes to a black screen) after a few seconds of no input. For example, started to read a webpage and the screen suddenly went to black after less than ten seconds. Or, when typing this bug report the screen display would shut off. After touching the mouse or touchpad, the screen would turn on. Never experienced this bug before. This only occurred after I had upgraded from Ubuntu 18.04 LTS to Ubuntu 19.04. Yes, this is really a bug. UBUNTU 19.04 GNOME 3.32.1 ** Affects: virt-manager (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1837335 Title: Screen goes to black after a few seconds using 19.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/virt-manager/+bug/1837335/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1828712] Re: I/O errors when trying to loop mount an image
@brian-murray thanks for the suggestion. Have done you suggest but apport-cli on the system with the GUI does not seem to allow an existing bug to be updated with the info, so rather than generating a new bug report am copying the file generated by apport-cli --save below. ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 Date: Fri May 17 10:50:14 2019 Dependencies: adduser 3.116ubuntu1 apt 1.6.10 apt-utils 1.6.10 busybox-initramfs 1:1.27.2-2ubuntu3.2 ca-certificates 20180409 coreutils 8.28-1ubuntu1 cpio 2.12+dfsg-6 debconf 1.5.66 debconf-i18n 1.5.66 dmsetup 2:1.02.145-4.1ubuntu3 dpkg 1.19.0.5ubuntu2.1 fdisk 2.31.1-0.4ubuntu3.3 gcc-8-base 8.3.0-6ubuntu1~18.04 gettext-base 0.19.8.1-6ubuntu0.3 gpgv 2.2.4-1ubuntu1.2 grub-common 2.02-2ubuntu8.13 grub-gfxpayload-lists 0.7 grub-pc 2.02-2ubuntu8.13 grub-pc-bin 2.02-2ubuntu8.13 grub2-common 2.02-2ubuntu8.13 init-system-helpers 1.51 initramfs-tools 0.130ubuntu3.7 initramfs-tools-bin 0.130ubuntu3.7 initramfs-tools-core 0.130ubuntu3.7 klibc-utils 2.0.4-9ubuntu2 kmod 24-1ubuntu3.2 libacl1 2.2.52-3build1 libapt-inst2.0 1.6.10 libapt-pkg5.0 1.6.10 libattr1 1:2.4.47-2build1 libaudit-common 1:2.8.2-1ubuntu1 libaudit1 1:2.8.2-1ubuntu1 libblkid1 2.31.1-0.4ubuntu3.3 libbz2-1.0 1.0.6-8.1 libc6 2.27-3ubuntu1 libcap-ng0 0.7.7-3.1 libdb5.3 5.3.28-13.1ubuntu1 libdevmapper1.02.1 2:1.02.145-4.1ubuntu3 libfdisk1 2.31.1-0.4ubuntu3.3 libffi6 3.2.1-8 libfreetype6 2.8.1-2ubuntu2 libfuse2 2.9.7-1ubuntu1 libgcc1 1:8.3.0-6ubuntu1~18.04 libgcrypt20 1.8.1-4ubuntu1.1 libgmp10 2:6.1.2+dfsg-2 libgnutls30 3.5.18-1ubuntu1 libgpg-error0 1.27-6 libgpm2 1.20.7-5 libhogweed4 3.4-1 libidn2-0 2.0.4-1.1build2 libklibc 2.0.4-9ubuntu2 libkmod2 24-1ubuntu3.2 liblocale-gettext-perl 1.07-3build2 liblz4-1 0.0~r131-2ubuntu3 liblzma5 5.2.2-1.3 libmount1 2.31.1-0.4ubuntu3.3 libncurses5 6.1-1ubuntu1.18.04 libncursesw5 6.1-1ubuntu1.18.04 libnettle6 3.4-1 libp11-kit0 0.23.9-2 libpam-modules 1.1.8-3.6ubuntu2.18.04.1 libpam-modules-bin 1.1.8-3.6ubuntu2.18.04.1 libpam0g 1.1.8-3.6ubuntu2.18.04.1 libpcre3 2:8.39-9 libpng16-16 1.6.34-1ubuntu0.18.04.2 libprocps6 2:3.3.12-3ubuntu1.1 libseccomp2 2.3.1-2.1ubuntu4.1 libselinux1 2.7-2build2 libsemanage-common 2.7-2build2 libsemanage1 2.7-2build2 libsepol1 2.7-1 libsmartcols1 2.31.1-0.4ubuntu3.3 libssl1.1 1.1.0g-2ubuntu4.3 libstdc++6 8.3.0-6ubuntu1~18.04 libsystemd0 237-3ubuntu10.21 libtasn1-6 4.13-2 libtext-charwidth-perl 0.04-7.1 libtext-iconv-perl 1.7-5build6 libtext-wrapi18n-perl 0.06-7.1 libtinfo5 6.1-1ubuntu1.18.04 libudev1 237-3ubuntu10.21 libunistring2 0.9.9-0ubuntu2 libuuid1 2.31.1-0.4ubuntu3.3 libzstd1 1.3.3+dfsg-2ubuntu1 linux-base 4.5ubuntu1 linux-modules-4.18.0-18-generic 4.18.0-18.19~18.04.1 lsb-base 9.20170808ubuntu1 openssl 1.1.0g-2ubuntu4.3 os-prober 1.74ubuntu1 passwd 1:4.5-1ubuntu2 perl-base 5.26.1-6ubuntu0.3 procps 2:3.3.12-3ubuntu1.1 psmisc 23.1-1ubuntu0.1 sensible-utils 0.0.12 tar 1.29b-2ubuntu0.1 ubuntu-keyring 2018.09.18.1~18.04.0 ucf 3.0038 udev 237-3ubuntu10.21 update-motd 3.6-0ubuntu1 util-linux 2.31.1-0.4ubuntu3.3 uuid-runtime 2.31.1-0.4ubuntu3.3 zlib1g 1:1.2.11.dfsg-0ubuntu2 DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2015-10-25 (1299 days ago) InstallationMedia: Ubuntu-Server 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) Package: linux-image-4.18.0-18-generic 4.18.0-18.19~18.04.1 PackageArchitecture: amd64 ProcCpuinfoMinimal: processor : 0 vendor_id : GenuineIntel cpu family : 6 model : 42 model name : Intel(R) Core(TM) i7-2860QM CPU @ 2.50GHz stepping : 7 cpu MHz: 2494.338 cache size : 8192 KB physical id: 0 siblings : 1 core id: 0 cpu cores : 1 apicid : 0 initial apicid : 0 fpu: yes fpu_exception : yes cpuid level: 13 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 syscall nx rdtscp lm constant_tsc rep_good nopl xtopology nonstop_tsc cpuid tsc_known_freq pni pclmulqdq monitor ssse3 cx16 sse4_1 sse4_2 popcnt aes xsave avx hypervisor lahf_lm pti bugs : cpu_meltdown spectre_v1 spectre_v2 spec_store_bypass l1tf bogomips : 4988.67 clflush size : 64 cache_alignment: 64 address sizes : 36 bits physical, 48 bits virtual power management: ProcEnviron: LANG=en_GB.UTF-8 SHELL=/bin/bash TERM=ansi LANGUAGE=en_GB:en XDG_RUNTIME_DIR= PATH=(custom, no user) ProcVersionSignature: Ubuntu 4.18.0-18.19~18.04.1-generic 4.18.20 SourcePackage: linux-signed-hwe Tags: bionic Uname: Linux 4.18.0-18-generic x86_64 UpgradeStatus: Upgraded to bionic on 2019-02-08 (97 days ago) _MarkForUpload: True -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1828712 Title: I/O errors when trying
[Bug 1828712] Re: I/O errors when trying to loop mount an image
Sorry I cannot run apport-collect as the machine has no GUI. I have tried the command on the console and via ssh but the resulting text-mode screen seems to prevent me entering my email address to log in. I also tried apport-cli but it had the same problem with the same authentication screen. As for logs, I did include the relevant syslog entries in the original report, if that helps. ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1828712 Title: I/O errors when trying to loop mount an image To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1828712/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1828712] Re: I/O errors when trying to loop mount an image
Setting package to linux kernel as advised for a filesystem issue. Ran apport-collect -p linux 1828712 per the instructions but I don't know that it worked as machine has no GUI. ** Package changed: ubuntu => linux (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1828712 Title: I/O errors when trying to loop mount an image To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1828712/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1828712] [NEW] I/O errors when trying to loop mount an image
Public bug reported: Command sudo mount -t vfat flop1 /mnt/flop1 fails. The image is readable but the log shows many I/O errors such as May 12 07:57:24 us64a kernel: [69801.335823] print_req_error: I/O error, dev loop0, sector 0 May 12 07:57:24 us64a kernel: [69801.337707] print_req_error: I/O error, dev loop0, sector 0 May 12 07:57:24 us64a kernel: [69801.339521] FAT-fs (loop0): unable to read boot sector May 12 07:57:24 us64a kernel: [69801.342063] print_req_error: I/O error, dev loop0, sector 0 May 12 07:57:24 us64a kernel: [69801.343891] Buffer I/O error on dev loop0, logical block 0, async page read May 12 07:57:24 us64a kernel: [69801.345974] print_req_error: I/O error, dev loop0, sector 1 May 12 07:57:24 us64a kernel: [69801.347832] Buffer I/O error on dev loop0, logical block 1, async page read May 12 07:57:24 us64a kernel: [69801.349928] print_req_error: I/O error, dev loop0, sector 2 May 12 07:57:24 us64a kernel: [69801.351818] Buffer I/O error on dev loop0, logical block 2, async page read May 12 07:57:24 us64a kernel: [69801.356103] print_req_error: I/O error, dev loop0, sector 3 May 12 07:57:24 us64a kernel: [69801.356109] Buffer I/O error on dev loop0, logical block 3, async page read May 12 07:57:24 us64a kernel: [69801.356117] print_req_error: I/O error, dev loop0, sector 4 May 12 07:57:24 us64a kernel: [69801.356119] Buffer I/O error on dev loop0, logical block 4, async page read May 12 07:57:24 us64a kernel: [69801.356122] print_req_error: I/O error, dev loop0, sector 5 May 12 07:57:24 us64a kernel: [69801.356125] Buffer I/O error on dev loop0, logical block 5, async page read May 12 07:57:24 us64a kernel: [69801.356128] print_req_error: I/O error, dev loop0, sector 6 May 12 07:57:24 us64a kernel: [69801.356130] Buffer I/O error on dev loop0, logical block 6, async page read May 12 07:57:24 us64a kernel: [69801.356134] print_req_error: I/O error, dev loop0, sector 7 May 12 07:57:24 us64a kernel: [69801.356136] Buffer I/O error on dev loop0, logical block 7, async page read May 12 07:57:24 us64a kernel: [69801.356260] Buffer I/O error on dev loop0, logical block 0, async page read May 12 07:57:24 us64a kernel: [69801.356263] Buffer I/O error on dev loop0, logical block 1, async page read The command, understandably, reports "can't read superblock on /dev/loop0". The problem happens even on newly created images. Here's a sample set of commands and responses: $ mkfs.msdos -C flop1 1440 $ ls -l -rwxrwxrwx 1 root root 1474560 May 10 18:49 flop1 $ hd flop1 <--- output looks reasonable including 55 aa and two FATs ---> $ sudo mkdir /mnt/flop1 $ sudo mount -o loop flop1 /mnt/flop1 mount: /mnt/flop1: can't read superblock on /dev/loop0. $ losetup -f /dev/loop0 $ I see plenty of reports of similar on different websites but without resolution, including one on Launchpad but where the OP stopped responding so it did not get resolved. I don't know when this problem started to occur on this machine. If it's relevant, this is running under VirtualBox which reports itself as Version 5.2.26 r128414 (Qt5.6.2) with their 'host extensions' enabled. However, mounting a floppy image previously worked on this virtual machine. I have rebooted with /forcefsck to check the root (and only) filesystem. I have upgraded to the latest LTS Ubuntu, as below, but the problem persists. System info: No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 18.04.2 LTS Release:18.04 Codename: bionic Linux us64a 4.18.0-18-generic #19~18.04.1-Ubuntu SMP Fri Apr 5 10:22:13 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux The machine is command-line only, i.e. no windowing. ** Affects: ubuntu Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1828712 Title: I/O errors when trying to loop mount an image To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1828712/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1814012] Re: netplan type wifis needs a device option
Here's one (e.g. my) case: Asus AC1200 USB-AC53 Nano wifi adapter. No linux driver available from the manufacturer. But there are open-source drivers available that work well, but that require the -D parameter in order to be able to use wpa_supplicant. Quoting https://github.com/jeremyb31/rtl8822bu/blob/master/README.md NOTES This driver allows use of wpa_supplicant by using the nl80211 driver wpa_supplicant -Dnl80211 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1814012 Title: netplan type wifis needs a device option To manage notifications about this bug go to: https://bugs.launchpad.net/netplan/+bug/1814012/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1814012] Re: netplan type wifis needs a device option
Re range of possible values for -D option: >From man wpa_supplicant: AVAILABLE DRIVERS A summary of available driver backends is below. Support for each of the driver backends is chosen at wpa_supplicant compile time. For a list of supported driver backends that may be used with the -D option on your system, refer to the help output of wpa_supplicant (wpa_supplicant -h). wext Linux wireless extensions (generic). wired wpa_supplicant wired Ethernet driver roboswitch wpa_supplicant Broadcom switch driver bsdBSD 802.11 support (Atheros, etc.). ndis Windows NDIS driver. from wpa_supplicant --help on my system: drivers: nl80211 = Linux nl80211/cfg80211 wext = Linux wireless extensions (generic) wired = Wired Ethernet driver none = no driver (RADIUS server/WPS ER) ** Description changed: - Some wifi adaptors need to use the -Ddevicename argument for + Some wifi adaptors need to use the -Ddrivername argument for wpa_supplicant to successfully associate with an AP. - The netplan yaml spec doesn't currently support an optional device + The netplan yaml spec doesn't currently support an optional driver property for the wifis type. For instance, here's my 01-netcfg.yaml: network: - version: 2 - renderer: networkd - ethernets: - ens32: - dhcp4: no - dhcp6: no - addresses: [192.168.0.222/24] - gateway4: 192.168.0.1 - nameservers: - addresses: [8.8.8.8,8.8.4.4] - wifis: - wlx4cedfb37602e: - optional: true - dhcp4: no - dhcp6: no - addresses: [192.168.1.222/24] - access-points: - "myssid": - password: "mywpapsk" + version: 2 + renderer: networkd + ethernets: + ens32: + dhcp4: no + dhcp6: no + addresses: [192.168.0.222/24] + gateway4: 192.168.0.1 + nameservers: + addresses: [8.8.8.8,8.8.4.4] + wifis: + wlx4cedfb37602e: + optional: true + dhcp4: no + dhcp6: no + addresses: [192.168.1.222/24] + access-points: + "myssid": + password: "mywpapsk" This isn't currently enough to get the wifi interface to associate. I have to hand-edit: /run/systemd/system/multi-user.target.wants/netplan- wpa@wlx4cedfb37602e.service - ..to include the proper device name. E.g.: + ..to include the proper driver name. E.g.: [Service] Type=simple ExecStart=/sbin/wpa_supplicant -c /run/netplan/wpa-%I.conf -i%I -Dnl80211 Once that edit has been made and systemctl daemon-reload run, the wifi interface associates. It would be nice if netplan included a.. - device: "devicename" + driver: "drivername" - ..option for the yaml file that would add the -Ddevicename to the unit + ..option for the yaml file that would add the -Ddrivername to the unit file. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1814012 Title: netplan type wifis needs a device option To manage notifications about this bug go to: https://bugs.launchpad.net/netplan/+bug/1814012/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1813170] Re: Opening reader mode causes audio distortion in all other tabs
Effect also observed if tab begins playing audio after reader mode is opened. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1813170 Title: Opening reader mode causes audio distortion in all other tabs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1813170/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1813170] Re: Opening reader mode causes audio distortion in all other tabs
Observed that effect seems to resolve if audio/video is stopped for a short while (~5 minutes in this case). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1813170 Title: Opening reader mode causes audio distortion in all other tabs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1813170/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1813170] [NEW] Opening reader mode causes audio distortion in all other tabs
Public bug reported: Description:Ubuntu 18.10 Release:18.10 firefox: Installed: 64.0+build3-0ubuntu0.18.10.1 Candidate: 64.0+build3-0ubuntu0.18.10.1 Version table: *** 64.0+build3-0ubuntu0.18.10.1 500 500 http://us.archive.ubuntu.com/ubuntu cosmic-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu cosmic-security/main amd64 Packages 100 /var/lib/dpkg/status 63.0+build1-0ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu cosmic/main amd64 Packages Hardware Motherboard: ASRock X399 Taichi Processor: AMD Threadripper x1900 Video Card: Nvidia GTX 1080 Audio Chipset: Realtek ALC1220 Expectation: Opening reader mode has no audio side effects. Actual: Occasionally when opening reader mode from any tab all audio in any other tab will crackle and pop until Firefox is restarted. Issue can be replicated in safe mode as well. ** Affects: firefox (Ubuntu) Importance: Undecided Status: New ** Tags: audio firefox reader -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1813170 Title: Opening reader mode causes audio distortion in all other tabs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1813170/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1755023] Re: Restore ignores what I type into the folder box
I have exactly the same problem, on a clean install of Bionic/18.04 Desktop AMD64, with a locally-attached (USB) 2TB SATA hard drive which works perfectly AFAIK for all functions other than Deja Dup. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1755023 Title: Restore ignores what I type into the folder box To manage notifications about this bug go to: https://bugs.launchpad.net/deja-dup/+bug/1755023/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1775672] Re: virtualbox-dkms installation hangs in 18.04 (with secure boot)
I've struggled through this several times now. I don't have a definitive solution but the general routine was something like this. When you asked to enroll the machine owner key to sign the kernel module there is an interface that popups up and waits for user input. I tried this in in a shell-only session and in a gnome session several times. In both cases the process that spawns the window gets stuck in a child process and I think it was sent to a different tty altogether. One time I accidentally recover the interface by killing all the login window session processes while I was in a trying something else in a shell session. When i jumped back everything redrew and there was a new window that asked me to enroll the MOK key password. I was not able to reproduce that the next time I got stuck in this spot, but what worked for me was disabling my machines nvidia video card proprietary drivers, and then switching from wayland to gnome (or gnome to wayland) after I did that then the processes worked as it was supposed to. This issue is very frustrating, but you should be able to keep secure boot enabled. I saved the logs from those times I was able to get it to work. I'll see if I can find anything to back up what I'm saying here. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1775672 Title: virtualbox-dkms installation hangs in 18.04 (with secure boot) To manage notifications about this bug go to: https://bugs.launchpad.net/dkms/+bug/1775672/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1733557] Re: Login screen showing Authentication Failure Switch to greeter...
In reply to #105 Have tested reverting that fix and it just re-introduces the bug "After locking screen there is no input field to type password for unlock" Having no input field is worse. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1733557 Title: Login screen showing Authentication Failure Switch to greeter... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1733557/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 508901] Re: update-grub sets wrong root argument
HOLY COW This bug was reported in 2010 AND STILL HAS NOT BEEN FIXED ! Totally unacceptable. To make sure we have a common understanding. I have linux on partition sda9 and "other" version of linux on partitions sda8, sdb8, and sdb9. The menu entries for ALL the "other" linuxes all specify the sda8 partition is the root partition, which is wrong for the sdb8 and sdb9 partitions. The bug applies if one is specifying the root using UUID or device name. I have inserted the following line into 30_os-prober as a Bug-Work- Around. The BWA only works because I am specifing root with a device name and not a UUID. A different BWA would be required for those using UUID. Fixing this should not be a major undertaking. I cannot fathom why in some much time it has not been addressed. LPARAMS=`echo $LPARAMS | sed "s:root=/dev/[A-Za-z0-9]* :root=$LROOT :"` -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/508901 Title: update-grub sets wrong root argument To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/508901/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1780819] [NEW] package cups-browsed 1.8.3-2ubuntu3.4 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Public bug reported: sudo apt-get install curl python-software-properties [sudo] password for pedro: Reading package lists... Done Building dependency tree Reading state information... Done curl is already the newest version (7.47.0-1ubuntu2.8). The following packages were automatically installed and are no longer required: ant ant-optional junit junit4 libaopalliance-java libapache-pom-java libasm4-java libatinject-jsr330-api-java libbsh-java libcdi-api-java libcglib3-java libclassworlds-java libcommons-cli-java libcommons-codec-java libcommons-httpclient-java libcommons-io-java libcommons-lang-java libcommons-lang3-java libcommons-logging-java libcommons-net-java libcommons-net2-java libcommons-parent-java libdom4j-java libdoxia-core-java libeasymock-java libeclipse-aether-java libgeronimo-interceptor-3.0-spec-java libgeronimo-jta-1.1-spec-java libguava-java libguice-java libhamcrest-java libhttpclient-java libhttpcore-java libjaxen-java libjdom1-java libjetty-java libjsch-java libjsoup-java libjsr305-java libllvm4.0 libllvm4.0:i386 libllvm6.0 libllvm6.0:i386 liblog4j1.2-java libmaven-parent-java libmaven2-core-java libmaven3-core-java libobjenesis-java libplexus-ant-factory-java libplexus-archiver-java libplexus-bsh-factory-java libplexus-cipher-java libplexus-classworlds-java libplexus-classworlds2-java libplexus-cli-java libplexus-component-annotations-java libplexus-component-metadata-java libplexus-container-default-java libplexus-container-default1.5-java libplexus-containers-java libplexus-containers1.5-java libplexus-interactivity-api-java libplexus-interpolation-java libplexus-io-java libplexus-sec-dispatcher-java libplexus-utils-java libplexus-utils2-java libqdox2-java libqmi-glib1 libqpdf17 libservlet2.5-java libservlet3.1-java libsisu-inject-java libsisu-plexus-java libslf4j-java libwagon-java libwagon2-java libxbean-java libxom-java libxpp2-java libxpp3-java libxz-java Use 'sudo apt autoremove' to remove them. The following NEW packages will be installed python-software-properties 0 to upgrade, 1 to newly install, 0 to remove and 48 not to upgrade. 1 not fully installed or removed. Need to get 20.7 kB of archives. After this operation, 122 kB of additional disk space will be used. Do you want to continue? [Y/n] y Get:1 http://gb.archive.ubuntu.com/ubuntu xenial-updates/universe amd64 python-software-properties all 0.96.20.7 [20.7 kB] Fetched 20.7 kB in 0s (590 kB/s) Selecting previously unselected package python-software-properties. (Reading database ... 290831 files and directories currently installed.) Preparing to unpack .../python-software-properties_0.96.20.7_all.deb ... Unpacking python-software-properties (0.96.20.7) ... Setting up cups-browsed (1.8.3-2ubuntu3.4) ... Failed to start cups-browsed.service: Unit cups.service is masked. invoke-rc.d: initscript cups-browsed, action "start" failed. ● cups-browsed.service - Make remote CUPS printers available locally Loaded: loaded (/lib/systemd/system/cups-browsed.service; enabled; vendor preset: enabled) Active: active (running) since Mon 2018-07-09 08:37:35 BST; 8h ago Main PID: 1445 (cups-browsed) CGroup: /system.slice/cups-browsed.service └─1445 /usr/sbin/cups-browsed Jul 09 08:37:35 pedro-laptop systemd[1]: Started Make remote CUPS printers available locally. dpkg: error processing package cups-browsed (--configure): subprocess installed post-installation script returned error exit status 1 Setting up python-software-properties (0.96.20.7) ... Errors were encountered while processing: cups-browsed E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Package DistroRelease: Ubuntu 16.04 Package: cups-browsed 1.8.3-2ubuntu3.4 ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15 Uname: Linux 4.4.0-34-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 AptOrdering: python-software-properties: Install cups-browsed: Configure python-software-properties: Configure NULL: ConfigurePending Architecture: amd64 CupsErrorLog: Date: Mon Jul 9 16:53:07 2018 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2015-01-30 (1256 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: Bad file descriptor MachineType: Hewlett-Packard HP Pavilion 15 Notebook PC Papersize: a4 PpdFiles: Deskjet-3050-J610-series: HP Deskjet 3050 j610 Series, hpcups 3.16.3 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-34-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash acpi_backlight=vendor vt.handoff=7 RelatedPackageVersions: dpkg 1.18.4ubuntu1.4 apt 1.2.26 SourcePackage: cups-filters Title: package cups-browsed 1.8.3-2ubuntu3.4 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present
[Bug 1776076] Re: package virtualbox-dkms 5.2.10-dfsg-6 failed to install/upgrade: installed virtualbox-dkms package post-installation script subprocess was killed by signal (Killed)
This has happened to me a couple times, I dont have a clear answer how to fix it yet, but the dkms install hangs waiting for input at the secure-boot update screen, but it seems to open in different tty so I end up having to kill the process to regain control of the terminal. You can see virtualbox-dkms getting stuck easily if you look at the process tree. I'll try to attach more useful information after my next attempt. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1776076 Title: package virtualbox-dkms 5.2.10-dfsg-6 failed to install/upgrade: installed virtualbox-dkms package post-installation script subprocess was killed by signal (Killed) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/1776076/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1759836] Re: systemd-udevd consumes 100% of CPU
As per https://patchwork.kernel.org/patch/10384111/ message from Bluez mailing list, editing 97-hid2hci.rules as follows works around the new uevents added to the kernel in https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=1455cf8dbfd06aa7651dcfccbadb7a093944ca65 -ACTION=="remove", GOTO="hid2hci_end" +ACTION!="add", GOTO="hid2hci_end" Bluetooth now works with kernels above and below 4.14. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1759836 Title: systemd-udevd consumes 100% of CPU To manage notifications about this bug go to: https://bugs.launchpad.net/bluez/+bug/1759836/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 513903] Re: wireshark must be run as root unless wireshark-common is reconfigured
It appears that the Ubuntu policy is that, if dumpcap is to be given elevated privileges, it be executable only by its owner (presumably root) and by members of the group that owns it, which appears to be the "wireshark" group. The intent is presumably not to give *everybody* on the system sufficient privilege to capture traffic; only people in the wireshark group can use dumpcap to capture network traffic. This is why they don't give world execute privileges to dumpcap; anybody who can run dumpcap would have sufficient privileges to capture on regular network devices (although some non-network devices that are also supported by libpcap on Linux, such as USB buses, may require root privileges). If you have to give dumpcap world execute privileges, that's because you're not in the group that owns it. You would have to add yourself to that group. You *can* give dumpcap world permission, instead, but doing so means that you will be giving the ability to capture traffic to every account on the system. If that's not what you want, do that; if that *is* what you want, perhaps you should ask the Ubuntu packagers to provide that as a configuration option, if they don't do so already. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/513903 Title: wireshark must be run as root unless wireshark-common is reconfigured To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wireshark/+bug/513903/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1767603] Re: BCM2046B1 and hid2hci generates highcpu usage due to udev since 4.14 kernel
Duplicate of https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1759836 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1767603 Title: BCM2046B1 and hid2hci generates highcpu usage due to udev since 4.14 kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1767603/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1759836] Re: systemd-udevd consumes 100% of CPU
It's a known kernel bug that Dell bluetooth is broken in kernels >=4.14, so sticking with the old kernel that works for now. Kernel bluetooth bug causes bluez 97-hid2hci.rules udev rule to fail. systemd-udevd has always consumed 100% whenever a udev rule fails (could be argued that's also a bug but at least you become immediately aware there's a problem). Possibly no coincidence that the break was introduced at the same time kernel tree commits were made to btusb.c wrt. Dell 'features' being addded. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1759836 Title: systemd-udevd consumes 100% of CPU To manage notifications about this bug go to: https://bugs.launchpad.net/bluez/+bug/1759836/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
