[Touch-packages] [Bug 1881699] Re: No analog output
Please attach `dmesg` and `pactl list card`, thanks! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1881699 Title: No analog output Status in linux package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: After a fresh boot and login, there is no analog output. Only HDMI and bluetooth are available. It becomes available when I kill pulseaudio with 'pulseaudio -k' but the sound indicator only shows 'dummy' output and I cannot control the output from the sound settings or the sound indicator. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: pulseaudio 1:13.99.1-1ubuntu3 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu36 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: j-lallement 184080 F pulseaudio /dev/snd/controlC1: j-lallement 184080 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Jun 2 06:32:09 2020 InstallationDate: Installed on 2020-05-31 (1 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200527) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/21/2019 dmi.bios.vendor: Intel Corp. dmi.bios.version: FNCML357.0032.2019.1021.1624 dmi.board.asset.tag: Default string dmi.board.name: NUC10i7FNB dmi.board.vendor: Intel Corporation dmi.board.version: K61360-302 dmi.chassis.asset.tag: Default string dmi.chassis.type: 35 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnIntelCorp.:bvrFNCML357.0032.2019.1021.1624:bd10/21/2019:svnIntel(R)ClientSystems:pnNUC10i7FNH:pvrK61081-302:rvnIntelCorporation:rnNUC10i7FNB:rvrK61360-302:cvnIntelCorporation:ct35:cvr2.0: dmi.product.family: FN dmi.product.name: NUC10i7FNH dmi.product.sku: BXNUC10i7FNH dmi.product.version: K61081-302 dmi.sys.vendor: Intel(R) Client Systems --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu36 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: j-lallement 3669 F pulseaudio /dev/snd/controlC0: j-lallement 3669 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2020-05-31 (1 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200527) MachineType: Intel(R) Client Systems NUC10i7FNH NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: pulseaudio 1:13.99.1-1ubuntu3 PackageArchitecture: amd64 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_huyn9u@/vmlinuz-5.4.0-26-generic root=ZFS=rpool/ROOT/ubuntu_huyn9u ro snd-intel-dspcfg.dsp_driver=1 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 RelatedPackageVersions: linux-restricted-modules-5.4.0-26-generic N/A linux-backports-modules-5.4.0-26-generic N/A linux-firmware1.187 Tags: groovy Uname: Linux 5.4.0-26-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/21/2019 dmi.bios.vendor: Intel Corp. dmi.bios.version: FNCML357.0032.2019.1021.1624 dmi.board.asset.tag: Default string dmi.board.name: NUC10i7FNB dmi.board.vendor: Intel Corporation dmi.board.version: K61360-302 dmi.chassis.asset.tag: Default string dmi.chassis.type: 35 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnIntelCorp.:bvrFNCML357.0032.2019.1021.1624:bd10/21/2019:svnIntel(R)ClientSystems:pnNUC10i7FNH:pvrK61081-302:rvnIntelCorporation:rnNUC10i7FNB:rvrK61360-302:cvnIntelCorporation:ct35:cvr2.0: dmi.product.family: FN dmi.product.name: NUC10i7FNH dmi.product.sku: BXNUC10i7FNH dmi.product.version: K61081-302 dmi.sys.vendor: Intel(R) Client Systems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1881699/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1874953] Re: dpkg: conffile difference visualizer subprocess returned error exit status 127
** Changed in: less (Debian) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to less in Ubuntu. https://bugs.launchpad.net/bugs/1874953 Title: dpkg: conffile difference visualizer subprocess returned error exit status 127 Status in dpkg package in Ubuntu: Triaged Status in less package in Ubuntu: Fix Released Status in smartmontools package in Ubuntu: Invalid Status in dpkg source package in Focal: Confirmed Status in less source package in Focal: Triaged Status in smartmontools source package in Focal: Confirmed Status in dpkg source package in Groovy: Triaged Status in less source package in Groovy: Fix Released Status in smartmontools source package in Groovy: Invalid Status in dpkg package in Debian: New Status in less package in Debian: Fix Committed Bug description: Issue occurred on upgrade from 19.10 to 20.04 ProblemType: Package DistroRelease: Ubuntu 20.04 Package: smartmontools 7.1-1build1 ProcVersionSignature: Ubuntu 5.3.0-46.38-generic 5.3.18 Uname: Linux 5.3.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Apr 24 21:33:08 2020 ErrorMessage: conffile difference visualizer subprocess returned error exit status 127 InstallationDate: Installed on 2011-06-18 (3233 days ago) InstallationMedia: Ubuntu-Server 11.04 "Natty Narwhal" - Release amd64 (20110426) Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18rc1, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2 SourcePackage: smartmontools Title: package smartmontools 7.1-1build1 failed to install/upgrade: conffile difference visualizer subprocess returned error exit status 127 UpgradeStatus: Upgraded to focal on 2020-04-25 (0 days ago) mtime.conffile..etc.default.smartmontools: 2017-12-08T19:12:02.064375 mtime.conffile..etc.smartd.conf: 2017-12-08T20:27:28.727282 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/1874953/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1881699] Re: No analog output
No difference with this option. ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1881699 Title: No analog output Status in linux package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: After a fresh boot and login, there is no analog output. Only HDMI and bluetooth are available. It becomes available when I kill pulseaudio with 'pulseaudio -k' but the sound indicator only shows 'dummy' output and I cannot control the output from the sound settings or the sound indicator. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: pulseaudio 1:13.99.1-1ubuntu3 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu36 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: j-lallement 184080 F pulseaudio /dev/snd/controlC1: j-lallement 184080 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Jun 2 06:32:09 2020 InstallationDate: Installed on 2020-05-31 (1 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200527) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/21/2019 dmi.bios.vendor: Intel Corp. dmi.bios.version: FNCML357.0032.2019.1021.1624 dmi.board.asset.tag: Default string dmi.board.name: NUC10i7FNB dmi.board.vendor: Intel Corporation dmi.board.version: K61360-302 dmi.chassis.asset.tag: Default string dmi.chassis.type: 35 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnIntelCorp.:bvrFNCML357.0032.2019.1021.1624:bd10/21/2019:svnIntel(R)ClientSystems:pnNUC10i7FNH:pvrK61081-302:rvnIntelCorporation:rnNUC10i7FNB:rvrK61360-302:cvnIntelCorporation:ct35:cvr2.0: dmi.product.family: FN dmi.product.name: NUC10i7FNH dmi.product.sku: BXNUC10i7FNH dmi.product.version: K61081-302 dmi.sys.vendor: Intel(R) Client Systems --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu36 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: j-lallement 3669 F pulseaudio /dev/snd/controlC0: j-lallement 3669 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2020-05-31 (1 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200527) MachineType: Intel(R) Client Systems NUC10i7FNH NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: pulseaudio 1:13.99.1-1ubuntu3 PackageArchitecture: amd64 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_huyn9u@/vmlinuz-5.4.0-26-generic root=ZFS=rpool/ROOT/ubuntu_huyn9u ro snd-intel-dspcfg.dsp_driver=1 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 RelatedPackageVersions: linux-restricted-modules-5.4.0-26-generic N/A linux-backports-modules-5.4.0-26-generic N/A linux-firmware1.187 Tags: groovy Uname: Linux 5.4.0-26-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/21/2019 dmi.bios.vendor: Intel Corp. dmi.bios.version: FNCML357.0032.2019.1021.1624 dmi.board.asset.tag: Default string dmi.board.name: NUC10i7FNB dmi.board.vendor: Intel Corporation dmi.board.version: K61360-302 dmi.chassis.asset.tag: Default string dmi.chassis.type: 35 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnIntelCorp.:bvrFNCML357.0032.2019.1021.1624:bd10/21/2019:svnIntel(R)ClientSystems:pnNUC10i7FNH:pvrK61081-302:rvnIntelCorporation:rnNUC10i7FNB:rvrK61360-302:cvnIntelCorporation:ct35:cvr2.0: dmi.product.family: FN dmi.product.name: NUC10i7FNH dmi.product.sku: BXNUC10i7FNH dmi.product.version: K61081-302 dmi.sys.vendor: Intel(R) Client Systems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1881699/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1885435] Re: The wrong sequence of mouse events can render the whole system unusable
Ubuntu 16.04 you are using is over 4 years old and there are two major long term releases newer than that, both of which use a completely different GUI to the one you have. I suggest if you want a higher quality experience then you should install Ubuntu 20.04: https://releases.ubuntu.com/20.04/ ** Package changed: xorg (Ubuntu) => compiz (Ubuntu) ** Also affects: unity (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1885435 Title: The wrong sequence of mouse events can render the whole system unusable Status in compiz package in Ubuntu: New Status in unity package in Ubuntu: New Bug description: This is 100% reproducible with any window, I'll use a terminal window as an example. Steps to reproduce: - open a terminal window (again, this could be a Gedit, Nautilus window or any other window) - make sure the window is not maximized - Place the mouse cursor at the center of the right border of the window, press the mouse left button and don't release it, so as to resize the window by dragging its right border - While dragging the terminal window's right border, press and hold the mouse right button too (remember you're still holding the left button too) - While still holding both mouse buttons pressed, move the mouse cursor away from the border of the window fast. If you move it fast enough, at some point the border will stop following the mouse cursor (which wouldn't happen if you hadn't pressed both buttons). - While the mouse cursor is outside the terminal winow, release the right button and then the left button. Now you are no longer holding any mouse button pressed - move the mouse cursor to the left and to right "crossing" the terminal window border, that is, move the mouse inside and outside the terminal window. Notice how, whenever the cursor "crosses" the window's right border, the border nonsensically moves a little bit following the movements of the cursor for a fraction of a second, as if you were still dragging it, but then it stops following the cursor. This is the first sign that something has gone completely berserk, but it's still nothing compared to what is coming - while the mouse cursor is outside of the offending window (i.e. the terminal window in our example), click on something outside of it. For example, in my case that's a maximized Chrome window that's behind. Observed disaster: now you are unable to do anything with the mouse. Try clicking on any window to move, close, or resize it. Try to click on stuff to give it focus. Try to click on Launcher icons. None of this has any effect. It's as if your mouse buttons dead. Not even by trying to go back to the original window and press and release the mouse buttons in any particular order while the cursor is over the window border seems to allow you to "unlock" the system. There's no way to recover from this situation except by KILLING the offending window without using the mouse. For example, by using alt+tab as many time as needed to give it focus, and then, since in this case it is a terminal, typing "exit" and hitting Enter, so the window gets closed and normal functioning of the mouse gets restored. If the offending window is not a terminal window, then you can hit Ctrl+Alt+T to open a new terminal, and then use a "kill" or "killall" command to kill the process that owns the offending window. Both of these imply loss of any unsaved work. This is a fucking disaster and an incredibly stupid bug of the kind that you usually observe in "software" written by novice programmers (or rather, non-programmers such as web designers playing around with javascript) who write their first programs with mouse events (press, release, rollover, etc) and forget to take into account all possible sequences of events. Seriously, I hadn't seen such stupid mouse behavior bugs outside of the scope of amateur website UIs. Fucking unbelievable. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3.1 ProcVersionSignature: Ubuntu 4.4.0-179.209-generic 4.4.219 Uname: Linux 4.4.0-179-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 340.107 Thu May 24 21:54:01 PDT 2018 GCC version: gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.12) .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.23 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Me
[Touch-packages] [Bug 1885463] Re: display and input freeze
** Tags added: amdgpu ** Summary changed: - display and input freeze + [amdgpu] display and input freeze ** Package changed: xorg (Ubuntu) => xserver-xorg-video-amdgpu (Ubuntu) ** Also affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1885463 Title: [amdgpu] display and input freeze Status in linux package in Ubuntu: Confirmed Status in xserver-xorg-video-amdgpu package in Ubuntu: New Bug description: Newly installed Ubuntu on a Lenovo laptop - less than 24 hours old. Just now, I revived laptop from sleep or hibernate and the display was frozen and corrupted. The bottom 1/3 of display was a patchwork of small squares of junk in green, pink, blue; top 2/3 of screen was a slightly distorted version of the default orange/purple background and the clock. I couldn't interact with the computer with mouse or keyboard - no mouse pointer, no control-alt-delete, no control- backspace. I found alt-PrtSc-reisub on google and was able to reboot from the keyboard. I'm running 18.04.4 LTS, on 2017ish Lenovo E450 with AMD Carrizo graphics card ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-108.109-generic 4.15.18 Uname: Linux 4.15.0-108-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Jun 28 18:33:57 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: This is the first time GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Wani [Radeon R5/R6/R7 Graphics] [1002:9874] (rev cb) (prog-if 00 [VGA controller]) Subsystem: Lenovo Radeon R5 Graphics [17aa:5118] MachineType: LENOVO 20H4CTO1WW ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-108-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/06/2017 dmi.bios.vendor: LENOVO dmi.bios.version: R0EET41W (1.15) dmi.board.asset.tag: Not Available dmi.board.name: 20H4CTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40700 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR0EET41W(1.15):bd06/06/2017:svnLENOVO:pn20H4CTO1WW:pvrThinkPadE475:rvnLENOVO:rn20H4CTO1WW:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad E475 dmi.product.name: 20H4CTO1WW dmi.product.version: ThinkPad E475 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1885463/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1885409] Re: Shut down or restart xorg error
This probably isn't the same issue but your kernel log shows the CD-ROM drive is experiencing problems. Please eject the disc (if any)... As for the main error you are trying to report in this bug, please attach a photo or video of the problem. Also in case it was a crash please follow these steps: https://wiki.ubuntu.com/Bugs/Responses#Missing_a_crash_report_or_having_a_.crash_attachment ** Changed in: xorg (Ubuntu) Status: New => Incomplete ** Package changed: xorg (Ubuntu) => ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1885409 Title: Shut down or restart xorg error Status in Ubuntu: Incomplete Bug description: xorg always appears in shut down or restart as an error. Computer does not shut down & restart does not restart. No further details as the shut down or restart process is to fast for me to read fully? ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-39.43-generic 5.4.41 Uname: Linux 5.4.0-39-generic x86_64 NonfreeKernelModules: nvidia_modeset zfs zunicode zavl icp zcommon znvpair nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.100 Fri May 29 08:45:51 UTC 2020 GCC version: ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip CompositorRunning: None Date: Sun Jun 28 13:15:42 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 440.100, 5.4.0-39-generic, x86_64: installed (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation GK208B [GeForce GT 710] [10de:128b] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] GK208B [GeForce GT 710] [1462:8c93] InstallationDate: Installed on 2020-06-03 (25 days ago) InstallationMedia: Xubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 001 Device 002: ID 046d:0824 Logitech, Inc. Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Gigabyte Technology Co., Ltd. B360 AORUS GAMING 3 WIFI ProcEnviron: LANGUAGE=en_AU:en PATH=(custom, no user) LANG=en_AU.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_t08klu@/vmlinuz-5.4.0-39-generic root=ZFS=rpool/ROOT/ubuntu_t08klu ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/14/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F12 dmi.board.asset.tag: Default string dmi.board.name: B360 AORUS GAMING 3 WIFI-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF12:bd03/14/2019:svnGigabyteTechnologyCo.,Ltd.:pnB360AORUSGAMING3WIFI:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB360AORUSGAMING3WIFI-CF:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: B360 AORUS GAMING 3 WIFI dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. 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.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 xserver.bootTime: Sun Jun 28 11:06:58 2020 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.20.8-2ubuntu2.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1885409/+subscriptions -- Mailing list: https:/
[Touch-packages] [Bug 1885363] Re: Screen flickers after waking up from suspend
** Tags added: amdgpu ** Summary changed: - Screen flickers after waking up from suspend + [amdgpu] Screen flickers after waking up from suspend ** Package changed: xorg (Ubuntu) => xserver-xorg-video-amdgpu (Ubuntu) ** Also affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1885363 Title: [amdgpu] Screen flickers after waking up from suspend Status in linux package in Ubuntu: New Status in xserver-xorg-video-amdgpu package in Ubuntu: New Bug description: I upgraded my Ubuntu 20.04 system with a new graphics card a few days ago. Everything seems fine when running the system normally, however whenever I suspend the machine and then wake it back up, severe problems occur. The first time, the machine froze completely. Switching to a different TTY didn't work anymore and the keyboard LEDs didn't respond to caps and num lock anymore, so I had to force shutdown. The second time, it came back OK but the screen has been flickering heavily since. Restarting Gnome and unplugging and plugging monitors back in hasn't helped. Relevant specs: CPU: AMD® Ryzen 9 3900x 12-core processor × 24 GPU: AMD® Radeon rx 5600 xt (MSI RADEON RX 5600 XT MECH OC) Monitors: 1x Acer running at 3840x2160 60Hz, 2x Medion (showing up as "Messeltronik Dresden GmbH") both running at 1920x1080 60Hz. Gnome: 3.36.2 X11 Apt doesn't report any updates. The flickering is most pronounced on the Acer. On the Medions, it seems to only happen when something changes on the screen. I have tried to capture this on video: https://youtu.be/HWT1J76-x94 This bug seem quite similar to this one (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1874588). I can also stop the flickering by switching the Acer to 1080p but when switching back to 4k, the problem reappears. I hope that ubuntu-bug has included all the necessary details. Let me know if you need anything else. Thank you very much for your help! ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-39.43-generic 5.4.41 Uname: Linux 5.4.0-39-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: GNOME Date: Sat Jun 27 10:44:32 2020 DistUpgraded: 2020-04-30 20:17:33,403 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 440.100, 5.4.0-37-generic, x86_64: installed nvidia, 440.100, 5.4.0-39-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 [Radeon RX 5600 OEM/5600 XT / 5700/5700 XT] [1002:731f] (rev ca) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Navi 10 [Radeon RX 5600 OEM/5600 XT / 5700/5700 XT] [1462:381e] InstallationDate: Installed on 2019-03-26 (458 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-39-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to focal on 2020-04-30 (57 days ago) dmi.bios.date: 04/08/2020 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.60 dmi.board.name: X570 Extreme4 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.60:bd04/08/2020:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnX570Extreme4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. 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 20.0.4-2ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bu
[Touch-packages] [Bug 1855628] Re: Ubuntu keeps having resolution issues and disconnects from the network after I wake it up from sleep
Please reproduce the issue and re-attach the logs. Not seeing any suspend attempt in dmesg. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1855628 Title: Ubuntu keeps having resolution issues and disconnects from the network after I wake it up from sleep Status in linux package in Ubuntu: Incomplete Status in network-manager package in Ubuntu: Confirmed Bug description: Whenever I wake the computer up from sleep, the computer no longer connects to the Internet without my having to go into Settings and turn Wi-Fi off and then back on again. Please address this issue. Thank you! network-manager: Installed: 1.10.6-2ubuntu1.2 Candidate: 1.10.6-2ubuntu1.2 Version table: *** 1.10.6-2ubuntu1.2 500 500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 1.10.6-2ubuntu1.1 500 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 1.10.6-2ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages Description: Ubuntu 18.04.3 LTS Release: 18.04 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: network-manager 1.10.6-2ubuntu1.2 ProcVersionSignature: Ubuntu 5.0.0-37.40~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-37-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Dec 8 19:51:31 2019 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IpRoute: default via 192.168.1.1 dev wlp3s0 proto dhcp metric 600 169.254.0.0/16 dev wlp3s0 scope link metric 1000 192.168.1.0/24 dev wlp3s0 proto kernel scope link src 192.168.1.33 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAMEUUID TYPE TIMESTAMP TIMESTAMP-REAL AUTOCONNECT AUTOCONNECT-PRIORITY READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH SLAVE NETGEAR18 64704ba2-aba5-44de-ad4a-7d0de569815b wifi 1575852612 Sun 08 Dec 2019 07:50:12 PM EST yes 0 no/org/freedesktop/NetworkManager/Settings/1 yes wlp3s0 activated /org/freedesktop/NetworkManager/ActiveConnection/1 -- Wired connection 1 28634e82-4c1c-3a61-b152-3bd92aaa6992 ethernet 1575852610 Sun 08 Dec 2019 07:50:10 PM EST yes 4294966297 no/org/freedesktop/NetworkManager/Settings/2 no -- -- -- -- nmcli-dev: DEVICE TYPE STATEDBUS-PATH CONNECTION CON-UUID CON-PATH wlp3s0 wifi connected/org/freedesktop/NetworkManager/Devices/3 NETGEAR18 64704ba2-aba5-44de-ad4a-7d0de569815b /org/freedesktop/NetworkManager/ActiveConnection/1 enp4s0 ethernet unavailable /org/freedesktop/NetworkManager/Devices/2 -- ---- lo loopback unmanaged/org/freedesktop/NetworkManager/Devices/1 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.10.6 connected started full enabled enabled enabled enabled enabled --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: seija 1560 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2020-04-04 (5 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) IpRoute: default via 192.168.1.1 dev wlp2s0 proto dhcp metric 600 169.254.0.0/16 dev wlp2s0 scope link metric 1000 192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.39 metric 600 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0cf3:e009 Atheros Communications, Inc. Bus 001 Device 003: ID 0bd
[Touch-packages] [Bug 1881699] Re: No analog output
I wonder if it's using SoundWire? Can you please boot mainline kernel without "snd-intel- dspcfg.dsp_driver=1"? ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1881699 Title: No analog output Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: Confirmed Bug description: After a fresh boot and login, there is no analog output. Only HDMI and bluetooth are available. It becomes available when I kill pulseaudio with 'pulseaudio -k' but the sound indicator only shows 'dummy' output and I cannot control the output from the sound settings or the sound indicator. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: pulseaudio 1:13.99.1-1ubuntu3 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu36 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: j-lallement 184080 F pulseaudio /dev/snd/controlC1: j-lallement 184080 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Jun 2 06:32:09 2020 InstallationDate: Installed on 2020-05-31 (1 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200527) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/21/2019 dmi.bios.vendor: Intel Corp. dmi.bios.version: FNCML357.0032.2019.1021.1624 dmi.board.asset.tag: Default string dmi.board.name: NUC10i7FNB dmi.board.vendor: Intel Corporation dmi.board.version: K61360-302 dmi.chassis.asset.tag: Default string dmi.chassis.type: 35 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnIntelCorp.:bvrFNCML357.0032.2019.1021.1624:bd10/21/2019:svnIntel(R)ClientSystems:pnNUC10i7FNH:pvrK61081-302:rvnIntelCorporation:rnNUC10i7FNB:rvrK61360-302:cvnIntelCorporation:ct35:cvr2.0: dmi.product.family: FN dmi.product.name: NUC10i7FNH dmi.product.sku: BXNUC10i7FNH dmi.product.version: K61081-302 dmi.sys.vendor: Intel(R) Client Systems --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu36 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: j-lallement 3669 F pulseaudio /dev/snd/controlC0: j-lallement 3669 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2020-05-31 (1 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200527) MachineType: Intel(R) Client Systems NUC10i7FNH NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: pulseaudio 1:13.99.1-1ubuntu3 PackageArchitecture: amd64 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_huyn9u@/vmlinuz-5.4.0-26-generic root=ZFS=rpool/ROOT/ubuntu_huyn9u ro snd-intel-dspcfg.dsp_driver=1 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 RelatedPackageVersions: linux-restricted-modules-5.4.0-26-generic N/A linux-backports-modules-5.4.0-26-generic N/A linux-firmware1.187 Tags: groovy Uname: Linux 5.4.0-26-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/21/2019 dmi.bios.vendor: Intel Corp. dmi.bios.version: FNCML357.0032.2019.1021.1624 dmi.board.asset.tag: Default string dmi.board.name: NUC10i7FNB dmi.board.vendor: Intel Corporation dmi.board.version: K61360-302 dmi.chassis.asset.tag: Default string dmi.chassis.type: 35 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnIntelCorp.:bvrFNCML357.0032.2019.1021.1624:bd10/21/2019:svnIntel(R)ClientSystems:pnNUC10i7FNH:pvrK61081-302:rvnIntelCorporation:rnNUC10i7FNB:rvrK61360-302:cvnIntelCorporation:ct35:cvr2.0: dmi.product.family: FN dmi.product.name: NUC10i7FNH dmi.product.sku: BXNUC10i7FNH dmi.product.version: K61081-302 dmi.sys.vendor: Intel(R) Client Systems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1881699/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1875912] Re: Selected audio output always USB device as default, but no control
[Expired for pulseaudio (Ubuntu) because there has been no activity for 60 days.] ** Changed in: pulseaudio (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1875912 Title: Selected audio output always USB device as default, but no control Status in pulseaudio package in Ubuntu: Expired Bug description: Upon login in Ubuntu 20.04, the selected audio device will always be my USB device (in this case a Schiit Modi 3 DAC). However, the audio will be played from my motherboard's default line-out through my desktop speakers (the desired and last used audio device). The issue then is that gnome and pulse audio seem to believe that the selected device is the USB DAC, and the volume controls no longer have any affect on the output volume. To regain control of the volume, I have to open up the Settings panel and select the Line-out device. This happens on every boot. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Apr 29 10:49:08 2020 InstallationDate: Installed on 2019-10-31 (180 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: Upgraded to focal on 2020-04-29 (0 days ago) dmi.bios.date: 11/19/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1405 dmi.board.asset.tag: Default string dmi.board.name: PRIME X570-PRO dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1405:bd11/19/2019:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEX570-PRO:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer modified.conffile..etc.pulse.default.pa: [modified] mtime.conffile..etc.pulse.default.pa: 2020-04-29T10:34:28.863415 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1875912/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1885334] Re: Nvidia kernel crashes when running World of Warcrat with wine/vulkan
** Summary changed: - Crashes when running World of Warcrat with wine/vulkan + Nvidia kernel crashes when running World of Warcrat with wine/vulkan ** Package changed: xorg (Ubuntu) => nvidia-graphics-drivers-440 (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1885334 Title: Nvidia kernel crashes when running World of Warcrat with wine/vulkan Status in nvidia-graphics-drivers-440 package in Ubuntu: Invalid Bug description: Hi, while version 440.82-0ubuntu0~0.18.04.2 ran with out any problems 440.100-0ubuntu0.18.04.1 crashes after a while with the following errors: Jun 26 22:41:31 imobil2 kernel: [ 1548.518774] NVRM: GPU at PCI::01:00: GPU-059d1eda-0ee6-ba17-38a2-5e6330b325f1 Jun 26 22:41:31 imobil2 kernel: [ 1548.518779] NVRM: Xid (PCI::01:00): 31, pid=1108, Ch 0012, intr 1000. MMU Fault: ENGINE GRAPHICS GPCCLIENT_PROP_0 faulted @ 0x1_12844000. Fault is of type FAULT_INFO_TYPE_UNSUPPORTED_KIND ACCESS_TYPE_WRITE Jun 26 22:47:32 imobil2 kernel: [ 1909.747689] NVRM: Xid (PCI::01:00): 13, pid=1265, Graphics Exception: Shader Program Header 1 Error Jun 26 22:47:32 imobil2 kernel: [ 1909.747698] NVRM: Xid (PCI::01:00): 13, pid=1265, Graphics Exception: Shader Program Header 2 Error Jun 26 22:47:32 imobil2 kernel: [ 1909.747704] NVRM: Xid (PCI::01:00): 13, pid=1265, Graphics Exception: Shader Program Header 3 Error Jun 26 22:47:32 imobil2 kernel: [ 1909.747708] NVRM: Xid (PCI::01:00): 13, pid=1265, Graphics Exception: Shader Program Header 5 Error Jun 26 22:47:32 imobil2 kernel: [ 1909.747713] NVRM: Xid (PCI::01:00): 13, pid=1265, Graphics Exception: Shader Program Header 9 Error Jun 26 22:47:32 imobil2 kernel: [ 1909.747718] NVRM: Xid (PCI::01:00): 13, pid=1265, Graphics Exception: Shader Program Header 10 Error Jun 26 22:47:32 imobil2 kernel: [ 1909.747723] NVRM: Xid (PCI::01:00): 13, pid=1265, Graphics Exception: Shader Program Header 18 Error Jun 26 22:47:32 imobil2 kernel: [ 1909.747728] NVRM: Xid (PCI::01:00): 13, pid=1265, Graphics Exception: Shader Program Header 19 Error Jun 26 22:47:32 imobil2 kernel: [ 1909.747735] NVRM: Xid (PCI::01:00): 13, pid=1265, Graphics Exception: ESR 0x405840=0x8e0c062e Jun 26 22:47:32 imobil2 kernel: [ 1909.748005] NVRM: Xid (PCI::01:00): 13, pid=1265, Graphics Exception: ChID 0008, Class a097, Offset 1614, Data Jun 26 22:47:33 imobil2 kernel: [ 1910.876226] NVRM: Xid (PCI::01:00): 62, pid=1265, 0110(25dc) 840008ce c415c455 This happend multiple times. Unfortunately the old driver version is not available anymore and I can't check if this is really caused by the driver update. Best regards, Matthias ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-108.109-generic 4.15.18 Uname: Linux 4.15.0-108-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Ist ein Verzeichnis: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.100 Fri May 29 08:45:51 UTC 2020 GCC version: gcc version 7.5.0 (Ubuntu 7.5.0-3ubuntu1~18.04) .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: i3 Date: Fri Jun 26 22:59:14 2020 DistUpgraded: 2020-04-09 19:50:27,912 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: nvidia, 440.100, 4.15.0-106-generic, x86_64: installed nvidia, 440.100, 4.15.0-108-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GK104 [GeForce GTX 770] [10de:1184] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] GK104 [GeForce GTX 770] [1462:2825] InstallationDate: Installed on 2013-12-15 (2384 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: MSI MS-7821 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-108-generic root=UUID=10f3ba43-ad16-4df4-b3b4-e86b64e9f96e ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2020-04-09 (78 days ago) dmi.bios.date: 07/21/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V1.9 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z87-G45 GAMING (MS-7821) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: To be fi
[Touch-packages] [Bug 1885463] Re: display and input freeze
** Package changed: ubuntu => xorg (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1885463 Title: display and input freeze Status in xorg package in Ubuntu: New Bug description: Newly installed Ubuntu on a Lenovo laptop - less than 24 hours old. Just now, I revived laptop from sleep or hibernate and the display was frozen and corrupted. The bottom 1/3 of display was a patchwork of small squares of junk in green, pink, blue; top 2/3 of screen was a slightly distorted version of the default orange/purple background and the clock. I couldn't interact with the computer with mouse or keyboard - no mouse pointer, no control-alt-delete, no control- backspace. I found alt-PrtSc-reisub on google and was able to reboot from the keyboard. I'm running 18.04.4 LTS, on 2017ish Lenovo E450 with AMD Carrizo graphics card ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-108.109-generic 4.15.18 Uname: Linux 4.15.0-108-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Jun 28 18:33:57 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: This is the first time GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Wani [Radeon R5/R6/R7 Graphics] [1002:9874] (rev cb) (prog-if 00 [VGA controller]) Subsystem: Lenovo Radeon R5 Graphics [17aa:5118] MachineType: LENOVO 20H4CTO1WW ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-108-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/06/2017 dmi.bios.vendor: LENOVO dmi.bios.version: R0EET41W (1.15) dmi.board.asset.tag: Not Available dmi.board.name: 20H4CTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40700 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR0EET41W(1.15):bd06/06/2017:svnLENOVO:pn20H4CTO1WW:pvrThinkPadE475:rvnLENOVO:rn20H4CTO1WW:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad E475 dmi.product.name: 20H4CTO1WW dmi.product.version: ThinkPad E475 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1885463/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1885463] [NEW] display and input freeze
You have been subscribed to a public bug: Newly installed Ubuntu on a Lenovo laptop - less than 24 hours old. Just now, I revived laptop from sleep or hibernate and the display was frozen and corrupted. The bottom 1/3 of display was a patchwork of small squares of junk in green, pink, blue; top 2/3 of screen was a slightly distorted version of the default orange/purple background and the clock. I couldn't interact with the computer with mouse or keyboard - no mouse pointer, no control-alt-delete, no control-backspace. I found alt-PrtSc- reisub on google and was able to reboot from the keyboard. I'm running 18.04.4 LTS, on 2017ish Lenovo E450 with AMD Carrizo graphics card ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-108.109-generic 4.15.18 Uname: Linux 4.15.0-108-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Jun 28 18:33:57 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: This is the first time GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Wani [Radeon R5/R6/R7 Graphics] [1002:9874] (rev cb) (prog-if 00 [VGA controller]) Subsystem: Lenovo Radeon R5 Graphics [17aa:5118] MachineType: LENOVO 20H4CTO1WW ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-108-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/06/2017 dmi.bios.vendor: LENOVO dmi.bios.version: R0EET41W (1.15) dmi.board.asset.tag: Not Available dmi.board.name: 20H4CTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40700 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR0EET41W(1.15):bd06/06/2017:svnLENOVO:pn20H4CTO1WW:pvrThinkPadE475:rvnLENOVO:rn20H4CTO1WW:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad E475 dmi.product.name: 20H4CTO1WW dmi.product.version: ThinkPad E475 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic freeze ubuntu -- display and input freeze https://bugs.launchpad.net/bugs/1885463 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1885278] Re: Black screen after standby on Intel NUC
To help us confirm if this is a Xorg bug, please try selecting 'Ubuntu on Wayland' from the login screen. ** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu) ** Changed in: xorg-server (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1885278 Title: Black screen after standby on Intel NUC Status in xorg-server package in Ubuntu: Incomplete Bug description: I have Kubuntu 20.04 on an Intel NUC NUC7JY. When I go into standby and try to wake it up, the NUC wakes up but there is no picture only black screen. This can be reproduced every time I go into standby. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-39.43-generic 5.4.41 Uname: Linux 5.4.0-39-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: KDE Date: Fri Jun 26 15:07:18 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: No GraphicsCard: Intel Corporation UHD Graphics 605 [8086:3185] (rev 03) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation UHD Graphics 605 [8086:2072] InstallationDate: Installed on 2020-06-25 (0 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bus 001 Device 003: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 002: ID 03f0:034a HP, Inc Elite Keyboard Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Intel(R) Client Systems NUC7CJYH ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-39-generic root=UUID=30399171-99ff-4cba-8ebe-26915e7b80c9 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/18/2019 dmi.bios.vendor: Intel Corp. dmi.bios.version: JYGLKCPX.86A.0050.2019.0418.1441 dmi.board.name: NUC7JYB dmi.board.vendor: Intel Corporation dmi.board.version: J67967-404 dmi.chassis.type: 35 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnIntelCorp.:bvrJYGLKCPX.86A.0050.2019.0418.1441:bd04/18/2019:svnIntel(R)ClientSystems:pnNUC7CJYH:pvrJ67971-405:rvnIntelCorporation:rnNUC7JYB:rvrJ67967-404:cvnIntelCorporation:ct35:cvr2.0: dmi.product.family: JY dmi.product.name: NUC7CJYH dmi.product.version: J67971-405 dmi.sys.vendor: Intel(R) Client Systems version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1885278/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1885272] Re: Re-logging occurs continuously during ubuntu operation
*** This bug is a duplicate of bug 1878193 *** https://bugs.launchpad.net/bugs/1878193 ** This bug has been marked a duplicate of bug 1878193 Shell crashes and returns to the login screen -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1885272 Title: Re-logging occurs continuously during ubuntu operation Status in xorg package in Ubuntu: New Bug description: completely impossible to work some errors constantly occur and then reboot the xorg (relogin occurs) https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1875435 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.100 Fri May 29 08:45:51 UTC 2020 GCC version: ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Jun 26 14:48:27 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu GraphicsCard: NVIDIA Corporation TU104BM [GeForce RTX 2080 Mobile] [10de:1ed0] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company TU104BM [GeForce RTX 2080 Mobile] [103c:8603] InstallationDate: Installed on 2020-05-13 (43 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: HP OMEN by HP Laptop 17-cb0xxx ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-40-generic root=UUID=5165ccf9-e9d6-457b-8152-e74b73fe461e ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/09/2019 dmi.bios.vendor: AMI dmi.bios.version: F.22 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 8603 dmi.board.vendor: HP dmi.board.version: 45.41 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAMI:bvrF.22:bd12/09/2019:svnHP:pnOMENbyHPLaptop17-cb0xxx:pvr:rvnHP:rn8603:rvr45.41:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP OMEN dmi.product.name: OMEN by HP Laptop 17-cb0xxx dmi.product.sku: 5VX37AV dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~20.04.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1885272/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1873718] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1873718 Title: CSR8510 based BTA-402 Bluetooth device cannot be started Status in bluez package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Bug description: In the GUI, I can go to the Bluetooth settings and it shows BT to be off. I turn on the little switch at the top but nothing else changes. If I navigate away from this page and then back, the switch is off again. If I try to reset the device on the command line I get: seb@eragon:~$ sudo hciconfig hci0 reset Can't init device hci0: Connection timed out (110) ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: bluez 5.50-0ubuntu5.1 ProcVersionSignature: Ubuntu 5.3.0-46.38-generic 5.3.18 Uname: Linux 5.3.0-46-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.8 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Apr 20 14:39:55 2020 EcryptfsInUse: Yes InterestingModules: bnep btusb bluetooth MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_NZ.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-46-generic root=/dev/mapper/vg0-root rw rootflags=errors=remount-ro quiet splash vt.handoff=1 pti=off SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/23/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: FA dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: 990FXA-UD3 dmi.board.vendor: AMD Corporation dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrFA:bd10/23/2012:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnAMDCorporation:rn990FXA-UD3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: To be filled by O.E.M. dmi.product.sku: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. hciconfig: hci0:Type: Primary Bus: USB BD Address: 00:00:00:00:00:00 ACL MTU: 0:0 SCO MTU: 0:0 DOWN RX bytes:0 acl:0 sco:0 events:0 errors:0 TX bytes:0 acl:0 sco:0 commands:1 errors:1 rfkill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1873718/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1873718] Re: CSR8510 based BTA-402 Bluetooth device cannot be started
** Changed in: bluez (Ubuntu) Status: Expired => New ** Changed in: linux (Ubuntu) Status: Expired => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1873718 Title: CSR8510 based BTA-402 Bluetooth device cannot be started Status in bluez package in Ubuntu: New Status in linux package in Ubuntu: New Bug description: In the GUI, I can go to the Bluetooth settings and it shows BT to be off. I turn on the little switch at the top but nothing else changes. If I navigate away from this page and then back, the switch is off again. If I try to reset the device on the command line I get: seb@eragon:~$ sudo hciconfig hci0 reset Can't init device hci0: Connection timed out (110) ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: bluez 5.50-0ubuntu5.1 ProcVersionSignature: Ubuntu 5.3.0-46.38-generic 5.3.18 Uname: Linux 5.3.0-46-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.8 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Apr 20 14:39:55 2020 EcryptfsInUse: Yes InterestingModules: bnep btusb bluetooth MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_NZ.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-46-generic root=/dev/mapper/vg0-root rw rootflags=errors=remount-ro quiet splash vt.handoff=1 pti=off SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/23/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: FA dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: 990FXA-UD3 dmi.board.vendor: AMD Corporation dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrFA:bd10/23/2012:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnAMDCorporation:rn990FXA-UD3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: To be filled by O.E.M. dmi.product.sku: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. hciconfig: hci0:Type: Primary Bus: USB BD Address: 00:00:00:00:00:00 ACL MTU: 0:0 SCO MTU: 0:0 DOWN RX bytes:0 acl:0 sco:0 events:0 errors:0 TX bytes:0 acl:0 sco:0 commands:1 errors:1 rfkill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1873718/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1885447] Re: Files do no recognize a Lets Encrypt SSH certificate
Another test. When I try wget, I get the same certificate error not valid. So it seems it is at the certificate level that it is not recognized. wget https://XX/share --2020-06-28 21:33:18-- https:///share Resolving XX (XX)... yyy.yyy.yyy.yyy Connecting to X (XXX)|yyy.yyy.yyy.yyy|:443... connected. ERROR: cannot verify XX's certificate, issued by ‘CN=Let's Encrypt Authority X3,O=Let's Encrypt,C=US’: Unable to locally verify the issuer's authority. To connect to X, use `--no-check-certificate'. I replaced IP and Domain for my privacy. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to file in Ubuntu. https://bugs.launchpad.net/bugs/1885447 Title: Files do no recognize a Lets Encrypt SSH certificate Status in file package in Ubuntu: New Bug description: I tried to find any references for this question, but I could not find anything close to the issue. I have a WebDAV server using a Letsencrypt certificate. When I access it through any browser (Chrome, Firefox), the certificate is valid an all goes well. It also works from the default Mac OS file browser. Windows is a no go, as it never worked from the get-go due to a "feature" on its WebDAV client, and a non-issue for us. However, when I try to use the default Files app from Ubuntu 16.04, 18.04, and 20.04 to connect to that server through the +Other Locations option (Dave://domain.com/share), it says the certificate authority is not known. Is this done on purpose (I mean not including the Letencrypt CA by default) Or just a mishappening somewhere? Thanks, ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: file 1:5.38-4 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Jun 28 14:53:00 2020 InstallationDate: Installed on 2020-04-25 (64 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: file UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/file/+bug/1885447/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1884887] Re: rsyslogd dmesg unit leaves /var/log/dmesg* world readable
** Changed in: rsyslog (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsyslog in Ubuntu. https://bugs.launchpad.net/bugs/1884887 Title: rsyslogd dmesg unit leaves /var/log/dmesg* world readable Status in rsyslog package in Ubuntu: New Bug description: [Impact] The rsyslog dmesg systemd unit /lib/systemd/system/dmesg.service in eoan, focal, and groovy create /var/log/dmesg* with the following permissions: -rw-r--r-- 1 root adm 45146 Jun 16 12:32 /var/log/dmesg Most other system logs in /var/log/ are only readable by root and group adm. While it's true that the kernel dmesg buffer by default can be read by anyone using the dmesg(1) command, this can be disabled by setting the sysctl kernel.dmesg_restrict to 1, but doing so as a hardening measure is thwarted by the world readable nature of /var/log/dmesg. The reason dmesg output is sensitive is that it sometimes contains kernel addresses for diagnosing kernel problems, but attackers looking to attack a kernel are also interested in kernel addresses and other information that shows up there. [Test Case] To reproduce: $ ls -l /var/log/dmesg* should show only root and group adm access like so: -rw-r- 1 root adm 50178 Jun 23 12:55 /var/log/dmesg -rw-r- 1 root adm 50217 Jun 23 12:55 /var/log/dmesg.0 -rw-r- 1 root adm 13941 Jun 23 12:47 /var/log/dmesg.1.gz and not world readable: -rw-r--r-- 1 root adm 45146 Jun 16 12:32 /var/log/dmesg [Regression Potential] It's possible tools like apport and others might expect /var/log/dmesg to be world-readable. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1884887/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1885452] Re: pc freezes and crashes during accountservice upgrade on fresh ubuntu focal fossa install
** Tags removed: fossa -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to accountsservice in Ubuntu. https://bugs.launchpad.net/bugs/1885452 Title: pc freezes and crashes during accountservice upgrade on fresh ubuntu focal fossa install Status in accountsservice package in Ubuntu: New Bug description: After a fresh install of Focal Fossa and running sudo apt update and sudo apt upgrade, when the upgrade reaches "setting up accountsservice" the PC freezes. After a reboot, the login screen did not appear anymore. This was reproducible on another computer (laptop). I reinstalled Ubuntu and put the package on hold. Later, I found that by installing and activating lightdm, this problem was remediated. Found this solution accidentally, while I was looking to correct login screen loops after I installed the nvidia drivers. This is unrelated, since the laptop does not have nvidia. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1885452/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1885452] [NEW] pc freezes and crashes during accountservice upgrade on fresh ubuntu focal fossa install
Public bug reported: After a fresh install of Focal Fossa and running sudo apt update and sudo apt upgrade, when the upgrade reaches "setting up accountsservice" the PC freezes. After a reboot, the login screen did not appear anymore. This was reproducible on another computer (laptop). I reinstalled Ubuntu and put the package on hold. Later, I found that by installing and activating lightdm, this problem was remediated. Found this solution accidentally, while I was looking to correct login screen loops after I installed the nvidia drivers. This is unrelated, since the laptop does not have nvidia. ** Affects: accountsservice (Ubuntu) Importance: Undecided Status: New ** Tags: accountsservice focal fossa lightdm -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to accountsservice in Ubuntu. https://bugs.launchpad.net/bugs/1885452 Title: pc freezes and crashes during accountservice upgrade on fresh ubuntu focal fossa install Status in accountsservice package in Ubuntu: New Bug description: After a fresh install of Focal Fossa and running sudo apt update and sudo apt upgrade, when the upgrade reaches "setting up accountsservice" the PC freezes. After a reboot, the login screen did not appear anymore. This was reproducible on another computer (laptop). I reinstalled Ubuntu and put the package on hold. Later, I found that by installing and activating lightdm, this problem was remediated. Found this solution accidentally, while I was looking to correct login screen loops after I installed the nvidia drivers. This is unrelated, since the laptop does not have nvidia. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1885452/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1829399] Re: Lid switch triggered suspend takes much longer than UI triggered suspend
interesting observation: if i close the lid for, say, 1 sec, and then open it again, after similar time delay as observed in the previous comment, my thinkpad goes into suspend although i am working in my desktop (obviously with the lid open). the lid close seems to trigger the suspend which comes 30 seconds later, no matter what... -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1829399 Title: Lid switch triggered suspend takes much longer than UI triggered suspend Status in linux package in Ubuntu: Invalid Status in systemd package in Ubuntu: Confirmed Bug description: IBM T460 5.0.0-13-generic #14-Ubuntu SMP Mon Apr 15 14:59:14 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux When triggering a suspend even from the lid switch of my Lenovo T460 it takes 30 seconds to reach suspend state. Several others with different models of Lenovo laptops have also reproduced this issue. It seems this is isolated to the lid switch as UI triggered suspend (alt+power icon) is far faster. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1829399/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1885447] [NEW] Files do no recognize a Lets Encrypt SSH certificate
Public bug reported: I tried to find any references for this question, but I could not find anything close to the issue. I have a WebDAV server using a Letsencrypt certificate. When I access it through any browser (Chrome, Firefox), the certificate is valid an all goes well. It also works from the default Mac OS file browser. Windows is a no go, as it never worked from the get-go due to a "feature" on its WebDAV client, and a non-issue for us. However, when I try to use the default Files app from Ubuntu 16.04, 18.04, and 20.04 to connect to that server through the +Other Locations option (Dave://domain.com/share), it says the certificate authority is not known. Is this done on purpose (I mean not including the Letencrypt CA by default) Or just a mishappening somewhere? Thanks, ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: file 1:5.38-4 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Jun 28 14:53:00 2020 InstallationDate: Installed on 2020-04-25 (64 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: file UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: file (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to file in Ubuntu. https://bugs.launchpad.net/bugs/1885447 Title: Files do no recognize a Lets Encrypt SSH certificate Status in file package in Ubuntu: New Bug description: I tried to find any references for this question, but I could not find anything close to the issue. I have a WebDAV server using a Letsencrypt certificate. When I access it through any browser (Chrome, Firefox), the certificate is valid an all goes well. It also works from the default Mac OS file browser. Windows is a no go, as it never worked from the get-go due to a "feature" on its WebDAV client, and a non-issue for us. However, when I try to use the default Files app from Ubuntu 16.04, 18.04, and 20.04 to connect to that server through the +Other Locations option (Dave://domain.com/share), it says the certificate authority is not known. Is this done on purpose (I mean not including the Letencrypt CA by default) Or just a mishappening somewhere? Thanks, ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: file 1:5.38-4 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Jun 28 14:53:00 2020 InstallationDate: Installed on 2020-04-25 (64 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: file UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/file/+bug/1885447/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1885448] Re: when i try start tor browser with terminal
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1885448 Title: when i try start tor browser with terminal Status in initramfs-tools package in Ubuntu: New Bug description: when i try start tor browser with terminal ProblemType: Package DistroRelease: Ubuntu 20.04 Package: nvidia-kernel-common-440 440.100-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-39.43-generic 5.4.41 Uname: Linux 5.4.0-39-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip Date: Sat Jun 27 15:10:23 2020 ErrorMessage: installed nvidia-kernel-common-440 package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2020-05-03 (56 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.1 SourcePackage: initramfs-tools Title: package nvidia-kernel-common-440 440.100-0ubuntu0.20.04.1 failed to install/upgrade: installed nvidia-kernel-common-440 package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1885448/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1885448] [NEW] when i try start tor browser with terminal
Public bug reported: when i try start tor browser with terminal ProblemType: Package DistroRelease: Ubuntu 20.04 Package: nvidia-kernel-common-440 440.100-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-39.43-generic 5.4.41 Uname: Linux 5.4.0-39-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip Date: Sat Jun 27 15:10:23 2020 ErrorMessage: installed nvidia-kernel-common-440 package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2020-05-03 (56 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.1 SourcePackage: initramfs-tools Title: package nvidia-kernel-common-440 440.100-0ubuntu0.20.04.1 failed to install/upgrade: installed nvidia-kernel-common-440 package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1885448 Title: when i try start tor browser with terminal Status in initramfs-tools package in Ubuntu: New Bug description: when i try start tor browser with terminal ProblemType: Package DistroRelease: Ubuntu 20.04 Package: nvidia-kernel-common-440 440.100-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-39.43-generic 5.4.41 Uname: Linux 5.4.0-39-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip Date: Sat Jun 27 15:10:23 2020 ErrorMessage: installed nvidia-kernel-common-440 package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2020-05-03 (56 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.1 SourcePackage: initramfs-tools Title: package nvidia-kernel-common-440 440.100-0ubuntu0.20.04.1 failed to install/upgrade: installed nvidia-kernel-common-440 package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1885448/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1883412] Re: 20.04: DNS servers from /etc/network/interfaces not honored by systemd-resolve
Sorry, please ignore my previous comment (comment 6); I'd copied the netplan config from another machine and adjusted all the IPs, but forgot to change the interface name, so the entries were ignored. Basic IP connectivity was working since I have an encrypted volume that's unlocked via the initrd, so the initrd sets up the IP/netmask/gateway, and these simply carried over once the rootfs was mounted; netplan/... didn't clear them out luckily. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1883412 Title: 20.04: DNS servers from /etc/network/interfaces not honored by systemd-resolve Status in systemd package in Ubuntu: Incomplete Bug description: I have a server that uses /etc/network/interfaces to configure static IP info, including DNS, via /etc/network/interfaces. This worked fine in 16.04 and 18.04. However, when I updated to 20.04 this no longer works; I have to run "systemd-resolve --set-dns=192.168.63.1 --interface=enp3s0" to fix it after every boot. My /etc/network/interfaces is: # Loopback auto lo iface lo inet loopback # enp3s0: LAN (Motherboard) auto enp3s0 iface enp3s0 inet static address 192.168.63.2 netmask 255.255.255.0 network 192.168.63.0 broadcast 192.168.63.255 gateway 192.168.63.1 dns-nameservers 192.168.63.1 iface enp3s0 inet6 static address 2001:470:bb52:63::2/64 netmask 64 # WiFi USB # FIXME: Probably will get renamed on boot #allow-hotplug ethFlashAirWifi #iface ethFlashAirWifi inet manual "systemd-resolve --status" outputs the following beforr I run the WAR command given above: Global LLMNR setting: no MulticastDNS setting: no DNSOverTLS setting: no DNSSEC setting: no DNSSEC supported: no DNSSEC NTA: 10.in-addr.arpa 16.172.in-addr.arpa 168.192.in-addr.arpa 17.172.in-addr.arpa 18.172.in-addr.arpa 19.172.in-addr.arpa 20.172.in-addr.arpa 21.172.in-addr.arpa 22.172.in-addr.arpa 23.172.in-addr.arpa 24.172.in-addr.arpa 25.172.in-addr.arpa 26.172.in-addr.arpa 27.172.in-addr.arpa 28.172.in-addr.arpa 29.172.in-addr.arpa 30.172.in-addr.arpa 31.172.in-addr.arpa corp d.f.ip6.arpa home internal intranet lan local private test Link 4 (tun0) Current Scopes: none DefaultRoute setting: no LLMNR setting: yes MulticastDNS setting: no DNSOverTLS setting: no DNSSEC setting: no DNSSEC supported: no Link 3 (lxcbr0) Current Scopes: none DefaultRoute setting: no LLMNR setting: yes MulticastDNS setting: no DNSOverTLS setting: no DNSSEC setting: no DNSSEC supported: no Link 2 (enp3s0) Current Scopes: none DefaultRoute setting: no LLMNR setting: yes MulticastDNS setting: no DNSOverTLS setting: no DNSSEC setting: no DNSSEC supported: no ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: systemd 245.4-4ubuntu3.1 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip Date: Sun Jun 14 01:58:10 2020 InstallationDate: Installed on 2016-04-12 (1524 days ago) InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Beta amd64 (20160408) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-37-generic root=/dev/mapper/severn_vg2016-lv_root ro SourcePackage: systemd UpgradeStatus: Upgraded to focal on 2020-06-14 (0 days ago) dmi.bios.date: 06/18/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.40 dmi.board.name: 890GX Extreme3 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor:
[Touch-packages] [Bug 1883412] Re: 20.04: DNS servers from /etc/network/interfaces not honored by systemd-resolve
Uggh. On a second system that I upgraded 16.04->18.04->20.04, I have netplan installed and a configuration file in place. However, the DNS entry in the netplan config is ignored, so even switching to netplan doesn't fix this bug:-( -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1883412 Title: 20.04: DNS servers from /etc/network/interfaces not honored by systemd-resolve Status in systemd package in Ubuntu: Incomplete Bug description: I have a server that uses /etc/network/interfaces to configure static IP info, including DNS, via /etc/network/interfaces. This worked fine in 16.04 and 18.04. However, when I updated to 20.04 this no longer works; I have to run "systemd-resolve --set-dns=192.168.63.1 --interface=enp3s0" to fix it after every boot. My /etc/network/interfaces is: # Loopback auto lo iface lo inet loopback # enp3s0: LAN (Motherboard) auto enp3s0 iface enp3s0 inet static address 192.168.63.2 netmask 255.255.255.0 network 192.168.63.0 broadcast 192.168.63.255 gateway 192.168.63.1 dns-nameservers 192.168.63.1 iface enp3s0 inet6 static address 2001:470:bb52:63::2/64 netmask 64 # WiFi USB # FIXME: Probably will get renamed on boot #allow-hotplug ethFlashAirWifi #iface ethFlashAirWifi inet manual "systemd-resolve --status" outputs the following beforr I run the WAR command given above: Global LLMNR setting: no MulticastDNS setting: no DNSOverTLS setting: no DNSSEC setting: no DNSSEC supported: no DNSSEC NTA: 10.in-addr.arpa 16.172.in-addr.arpa 168.192.in-addr.arpa 17.172.in-addr.arpa 18.172.in-addr.arpa 19.172.in-addr.arpa 20.172.in-addr.arpa 21.172.in-addr.arpa 22.172.in-addr.arpa 23.172.in-addr.arpa 24.172.in-addr.arpa 25.172.in-addr.arpa 26.172.in-addr.arpa 27.172.in-addr.arpa 28.172.in-addr.arpa 29.172.in-addr.arpa 30.172.in-addr.arpa 31.172.in-addr.arpa corp d.f.ip6.arpa home internal intranet lan local private test Link 4 (tun0) Current Scopes: none DefaultRoute setting: no LLMNR setting: yes MulticastDNS setting: no DNSOverTLS setting: no DNSSEC setting: no DNSSEC supported: no Link 3 (lxcbr0) Current Scopes: none DefaultRoute setting: no LLMNR setting: yes MulticastDNS setting: no DNSOverTLS setting: no DNSSEC setting: no DNSSEC supported: no Link 2 (enp3s0) Current Scopes: none DefaultRoute setting: no LLMNR setting: yes MulticastDNS setting: no DNSOverTLS setting: no DNSSEC setting: no DNSSEC supported: no ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: systemd 245.4-4ubuntu3.1 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip Date: Sun Jun 14 01:58:10 2020 InstallationDate: Installed on 2016-04-12 (1524 days ago) InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Beta amd64 (20160408) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-37-generic root=/dev/mapper/severn_vg2016-lv_root ro SourcePackage: systemd UpgradeStatus: Upgraded to focal on 2020-06-14 (0 days ago) dmi.bios.date: 06/18/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.40 dmi.board.name: 890GX Extreme3 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.40:bd06/18/2010:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rn89
[Touch-packages] [Bug 1879582] Re: [Redmi AirDots Bluetooth] I need to remove device in settings every time i want to connect again
** Attachment added: "Same bug in Dell inspiron 5480 laptop." https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1879582/+attachment/5387956/+files/dell_bad.cap -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1879582 Title: [Redmi AirDots Bluetooth] I need to remove device in settings every time i want to connect again Status in alsa-driver package in Ubuntu: New Bug description: I can connect to my bluetooth phone only the first time after pair the device. It works until disconnecting, (whether by turning off the phone, or putting into the case, or disconnecting in ubuntu settings), and then i turn on the phone again (or remove from the case), i cannot connect until I manually remove from bluetooth devices list in Ubuntu Settings, and then pair it again.. If the Ubuntu/Gnome Settings is opened, i can see the status "connected" blinks, and fastly change to "disconnected". My bluetooth phone works fine with another devices. Ubuntu 20.04 LTS Laptop Acer Aspire Nitro 5 (AN515-52-5771). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: felipe 2149 F pulseaudio /dev/snd/controlC0: felipe 2149 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue May 19 19:10:35 2020 InstallationDate: Installed on 2020-04-29 (20 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_Card: Redmi AirDots_R Symptom_Type: None of the above Title: [Redmi AirDots_R, playback] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/05/2019 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.28 dmi.board.asset.tag: Type2 - Board Serial Number dmi.board.name: Freed_CFS dmi.board.vendor: CFL dmi.board.version: V1.28 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.28 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.28:bd08/05/2019:svnAcer:pnNitroAN515-52:pvrV1.28:rvnCFL:rnFreed_CFS:rvrV1.28:cvnAcer:ct10:cvrV1.28: dmi.product.family: Nitro 5 dmi.product.name: Nitro AN515-52 dmi.product.sku: dmi.product.version: V1.28 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1879582/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1879582] Re: [Redmi AirDots Bluetooth] I need to remove device in settings every time i want to connect again
Hi! I had test the same redmi airdots in more scenarios, that led me to guess that, while autoconnection is not a bug, manual connection is really an Ubuntu bug, since it worked fine in Linux Mint 19.3 in the same hardware. These was the new tested cenarios (all these with redmi airdots phone): * Scenario 1 - Dell Inspiron 5480 with Ubuntu 20.04 in live usb mode. Exactly the same bug that in My acer from original post. I need to do annoying clicks in connection switcher until it works. * Scenario 2 - Same Dell Inspiron 5480, but with Windows 10. Manual Connection works fine. Auto connection not (maybe it's kind a airdots feature, try to connect just in more used device, instead of the last). * Scenario 3 - The acer nitro 5, same from original report, but with Linux Mint 19.3 (live usb). It works, i can manually connect with just one click (but also no auto connection). ** Attachment added: "airdots earbuds manual connecting fine in Linux Mint 19.3" https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1879582/+attachment/5387955/+files/acer_mint_good.cap -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1879582 Title: [Redmi AirDots Bluetooth] I need to remove device in settings every time i want to connect again Status in alsa-driver package in Ubuntu: New Bug description: I can connect to my bluetooth phone only the first time after pair the device. It works until disconnecting, (whether by turning off the phone, or putting into the case, or disconnecting in ubuntu settings), and then i turn on the phone again (or remove from the case), i cannot connect until I manually remove from bluetooth devices list in Ubuntu Settings, and then pair it again.. If the Ubuntu/Gnome Settings is opened, i can see the status "connected" blinks, and fastly change to "disconnected". My bluetooth phone works fine with another devices. Ubuntu 20.04 LTS Laptop Acer Aspire Nitro 5 (AN515-52-5771). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: felipe 2149 F pulseaudio /dev/snd/controlC0: felipe 2149 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue May 19 19:10:35 2020 InstallationDate: Installed on 2020-04-29 (20 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_Card: Redmi AirDots_R Symptom_Type: None of the above Title: [Redmi AirDots_R, playback] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/05/2019 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.28 dmi.board.asset.tag: Type2 - Board Serial Number dmi.board.name: Freed_CFS dmi.board.vendor: CFL dmi.board.version: V1.28 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.28 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.28:bd08/05/2019:svnAcer:pnNitroAN515-52:pvrV1.28:rvnCFL:rnFreed_CFS:rvrV1.28:cvnAcer:ct10:cvrV1.28: dmi.product.family: Nitro 5 dmi.product.name: Nitro AN515-52 dmi.product.sku: dmi.product.version: V1.28 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1879582/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1822712] Re: https mirrors apport-retrace crashed with SystemError in _get_primary_mirror_from_apt_sources(): cannot determine default mirror: /etc/apt/sources.list does not cont
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: apport (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1822712 Title: https mirrors apport-retrace crashed with SystemError in _get_primary_mirror_from_apt_sources(): cannot determine default mirror: /etc/apt/sources.list does not contain a valid deb line Status in apport package in Ubuntu: Confirmed Bug description: 1. Have other crash occur. 2. Click retrace locally. 3. apport-retrace crashes. The only thing I can think is it's the fact that i changed my mirror to: deb https://mirrors.ocf.berkeley.edu/ubuntu/ disco main restricted universe multiverse deb-src https://mirrors.ocf.berkeley.edu/ubuntu/ disco main restricted universe multiverse ProblemType: Crash DistroRelease: Ubuntu 19.04 Package: apport-retrace 2.20.10-0ubuntu23 ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1 Uname: Linux 5.0.0-8-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportLog: ERROR: apport (pid 10677) Mon Apr 1 19:40:34 2019: called for pid 8661, signal 11, core limit 0, dump mode 1 ERROR: apport (pid 10677) Mon Apr 1 19:40:34 2019: executable: /usr/bin/gedit (command line "/usr/bin/gedit --gapplication-service") ERROR: apport (pid 10677) Mon Apr 1 19:40:34 2019: debug: session gdbus call: (true,) ERROR: apport (pid 10677) Mon Apr 1 19:40:42 2019: wrote report /var/crash/_usr_bin_gedit.1000.crash ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 CrashReports: 640:1000:117:8118520:2019-04-01 20:06:04.204469680 -0700:2019-04-01 20:06:05.204469680 -0700:/var/crash/_usr_bin_gedit.1000.crash 640:1000:117:23602:2019-04-01 20:06:21.172740697 -0700:2019-04-01 20:06:22.172740697 -0700:/var/crash/_usr_bin_apport-retrace.1000.crash CurrentDesktop: ubuntu:GNOME Date: Mon Apr 1 20:06:22 2019 ExecutablePath: /usr/bin/apport-retrace InstallationDate: Installed on 2018-04-14 (352 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180414) InterpreterPath: /usr/bin/python3.7 PackageArchitecture: all ProcCmdline: /usr/bin/python3 /usr/bin/apport-retrace -S system -C /home/username/.cache/apport/retrace -v --output /var/crash/_usr_bin_gedit.1000.crash /var/crash/_usr_bin_gedit.1000.crash ProcEnviron: TERM=xterm-256color PATH=(custom, user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash Python3Details: /usr/bin/python3.7, Python 3.7.3, python3-minimal, 3.7.2-1 PythonArgs: ['/usr/bin/apport-retrace', '-S', 'system', '-C', '/home/username/.cache/apport/retrace', '-v', '--output', '/var/crash/_usr_bin_gedit.1000.crash', '/var/crash/_usr_bin_gedit.1000.crash'] PythonDetails: /usr/bin/python2.7, Python 2.7.16, python-minimal, 2.7.16-1 SourcePackage: apport Title: apport-retrace crashed with SystemError in _get_primary_mirror_from_apt_sources(): cannot determine default mirror: /etc/apt/sources.list does not contain a valid deb line UpgradeStatus: Upgraded to disco on 2019-01-05 (86 days ago) UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1822712/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1885435] [NEW] The wrong sequence of mouse events can render the whole system unusable
Public bug reported: This is 100% reproducible with any window, I'll use a terminal window as an example. Steps to reproduce: - open a terminal window (again, this could be a Gedit, Nautilus window or any other window) - make sure the window is not maximized - Place the mouse cursor at the center of the right border of the window, press the mouse left button and don't release it, so as to resize the window by dragging its right border - While dragging the terminal window's right border, press and hold the mouse right button too (remember you're still holding the left button too) - While still holding both mouse buttons pressed, move the mouse cursor away from the border of the window fast. If you move it fast enough, at some point the border will stop following the mouse cursor (which wouldn't happen if you hadn't pressed both buttons). - While the mouse cursor is outside the terminal winow, release the right button and then the left button. Now you are no longer holding any mouse button pressed - move the mouse cursor to the left and to right "crossing" the terminal window border, that is, move the mouse inside and outside the terminal window. Notice how, whenever the cursor "crosses" the window's right border, the border nonsensically moves a little bit following the movements of the cursor for a fraction of a second, as if you were still dragging it, but then it stops following the cursor. This is the first sign that something has gone completely berserk, but it's still nothing compared to what is coming - while the mouse cursor is outside of the offending window (i.e. the terminal window in our example), click on something outside of it. For example, in my case that's a maximized Chrome window that's behind. Observed disaster: now you are unable to do anything with the mouse. Try clicking on any window to move, close, or resize it. Try to click on stuff to give it focus. Try to click on Launcher icons. None of this has any effect. It's as if your mouse buttons dead. Not even by trying to go back to the original window and press and release the mouse buttons in any particular order while the cursor is over the window border seems to allow you to "unlock" the system. There's no way to recover from this situation except by KILLING the offending window without using the mouse. For example, by using alt+tab as many time as needed to give it focus, and then, since in this case it is a terminal, typing "exit" and hitting Enter, so the window gets closed and normal functioning of the mouse gets restored. If the offending window is not a terminal window, then you can hit Ctrl+Alt+T to open a new terminal, and then use a "kill" or "killall" command to kill the process that owns the offending window. Both of these imply loss of any unsaved work. This is a fucking disaster and an incredibly stupid bug of the kind that you usually observe in "software" written by novice programmers (or rather, non-programmers such as web designers playing around with javascript) who write their first programs with mouse events (press, release, rollover, etc) and forget to take into account all possible sequences of events. Seriously, I hadn't seen such stupid mouse behavior bugs outside of the scope of amateur website UIs. Fucking unbelievable. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3.1 ProcVersionSignature: Ubuntu 4.4.0-179.209-generic 4.4.219 Uname: Linux 4.4.0-179-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 340.107 Thu May 24 21:54:01 PDT 2018 GCC version: gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.12) .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.23 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Sun Jun 28 17:28:05 2020 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: No GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] 3rd Gen Core processor Graphics Controller [1025:0647] NVIDIA Corporation GF117M [GeForce 610M/710M/810M/820M / GT 620M/625M/630M/720M] [10de:1140] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] GeForce 710M [1025:0691] InstallationDate: Installed on 2013-10-11 (2451 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: Acer Aspire V3-571G ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-179-generic root=UUID=5830b30e-69e8-4bb4
[Touch-packages] [Bug 1883673] Re: no sound after resume
Hi! Since this bugs continues to happen on my computer, I wonder if there's anything I can do to confirm it and give you more information about it... -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1883673 Title: no sound after resume Status in pulseaudio package in Ubuntu: New Bug description: Hi! After a suspend/resume cycle with HDMI plugged in, it seems that pulseaudio doesn't recognize anymore the internal analog device (speakers/headphones) and I hear no sound. Before suspend I see two audio sinks through "pacmd list-sinks" (internal analog and HDMI), and after resume I only get HDMI audio. Still, audio only ever comes out of the internal device. A "killall pulseaudio" solves this for me (i.e., I get audio from the internal device). This looks a bit similar to the old bug #202089, but I don't know if it's the same. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.2 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: della 1195 F pulseaudio /dev/snd/controlC1: della 1195 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Jun 16 10:50:50 2020 InstallationDate: Installed on 2020-03-12 (95 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: pulseaudio UpgradeStatus: Upgraded to focal on 2020-04-27 (50 days ago) dmi.bios.date: 09/19/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: FX505DD.308 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: FX505DD dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrFX505DD.308:bd09/19/2019:svnASUSTeKCOMPUTERINC.:pnTUFGamingFX505DD_TUF505DD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnFX505DD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: TUF Gaming dmi.product.name: TUF Gaming FX505DD_TUF505DD dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1883673/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 304393] Re: rpcbind grabs ports used by other daemons such as cupsd
** Changed in: rpcbind (Debian) Status: Unknown => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/304393 Title: rpcbind grabs ports used by other daemons such as cupsd Status in cups package in Ubuntu: Invalid Status in rpcbind package in Ubuntu: Fix Released Status in rpcbind source package in Xenial: In Progress Status in rpcbind source package in Bionic: In Progress Status in rpcbind package in Debian: Fix Released Status in Fedora: Confirmed Bug description: [impact] rpcbind binds to a 'random' reserved port at startup, which can conflict with the reserved port number for other applications that actually 'own' the reserved port number. One example is cups, which uses the reserved port 631. This prevents the actual 'owner' of the reserved port from starting, since it can't bind to its reserved port. Additionally, this can raise alarms from security monitoring software that does not expect programs to be listening on random reserved ports. [test case] start rpcbind and check which ports it is listening on, e.g.: $ sudo netstat --inet -p -l | grep rpcbind | grep -v sunrpc udp0 0 0.0.0.0:614 0.0.0.0:* 4678/rpcbind each time rpcbind is restarted, it will be listening to a different 'random' port. [regression potential] this adds a method to disable rpcbind from listening to the 'random' port. any regression would likely prevent rpcbind from starting, or may cause problems with the interaction between rpcinfo and rpcbind, as rpcinfo may use the random reserved port in some cases, as detailed in the Debian bug. [scope] This is needed only for Bionic and earlier. In Focal and later, and in Debian, rpcbind defaults to not opening the random reserved port. The admin can use the -r parameter to cause rpcbind to restore the old behavior of opening the random reserved port. [other info] Note that the -r parameter is a Debian addition, and the upstream rpcbind has disabled the random port functionality at build time; there is no runtime parameter to allow the admin to choose the behavior. Also, as discussed in the Debian bug, disabling this rpcbind 'feature' is known to cause problems for the rpcinfo program, which is why Debian introduced the -r parameter. So, when this -r parameter is backported to Bionic and earlier, we must retain the default behavior for those releases, which is for rpcbind to open the random reserved port. TBD: specific method to disable rmtcalls in backport [original description] As this backports that functionality, it Binary package hint: cups cups 1.3.9-2ubuntu4 From /var/log/cups/error_log: cups: unable to bind socket for address 127.0.0.1:631 - Address already in use. Nothing actually looks wrong. 127.0.0.1:631 is only in use by cupsd when started. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/304393/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1883608] Re: [USB-Audio - UMC204HD 192k, playback] Playback problem
** Package changed: alsa-driver (Ubuntu) => pulseaudio (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1883608 Title: [USB-Audio - UMC204HD 192k, playback] Playback problem Status in pulseaudio package in Ubuntu: New Bug description: I want to split the 4.0 output into 2x2.0 outputs. This is my config for /etc/pulse/default.pa load-module module-remap-sink sink_name=behringera sink_properties="device.description='Behringer Output A (1 and 2)'" remix=no master=alsa_output.usb-BEHRINGER_UMC204HD_192k-00.analog-surround-40 channels=2 master_channel_map=front-left,front-right channel_map=left,right load-module module-remap-sink sink_name=behringerb sink_properties="device.description='Behringer Output B (3 and 4)'" remix=no master=alsa_output.usb-BEHRINGER_UMC204HD_192k-00.analog-surround-40 channels=2 master_channel_map=rear-left,rear-right channel_map=left,right I have tested this config on Ubuntu 18.04, Debian, Fedora 30, it works on all of them. But does not work on Ubuntu 20.04, nor Fedora 32. Both 20.04 and f32 use version 13.99.1 of Pulseaudio, so I suspect the problem to be with this version. When I speak about A and B, I am referring to the device description given in the 2 lines above, line 1 being A and line 2 being B. What is happening on 20.04 and f32 is if I comment out A, then B will work. If I comment out B, A will work, but both A and B are defined, then only A will work. If B is defined first, and then A, something else weird happens where A will work, but is sent out through B, and B will work as expected. A discussion on Reddit, another user has version 13.0 on NixOS and his similar UMC404HD works fine. Here is a link to the info on Reddit: https://www.reddit.com/r/linuxaudio/comments/fqmhbe/pulseaudio_and_multichannel_interfaces/ftkq7ov I know this is probably a pulseaudio bug, but I could not figure out how to submit a bug report to them. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: angus 5429 F pulseaudio /dev/snd/pcmC0D0p: angus 5429 F...m pulseaudio /dev/snd/controlC3: angus 5429 F pulseaudio /dev/snd/controlC2: angus 5429 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Jun 15 23:14:49 2020 InstallationDate: Installed on 2020-04-25 (51 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:U192k successful Symptom_Card: Family 17h (Models 00h-0fh) HD Audio Controller - HD-Audio Generic Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: None of the above Title: [USB-Audio - UMC204HD 192k, playback] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/21/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.H0 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: X370 KRAIT GAMING (MS-7A33) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.H0:bd01/21/2019:svnMicro-StarInternationalCo.,Ltd.:pnMS-7A33:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnX370KRAITGAMING(MS-7A33):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7A33 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1883608/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1650961] Re: ERROR:connection_factory_impl.cc(367)] Failed to connect to MCS endpoint with error -106
Same here (ub18.4.4) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1650961 Title: ERROR:connection_factory_impl.cc(367)] Failed to connect to MCS endpoint with error -106 Status in apport package in Ubuntu: Invalid Bug description: caravena@caravena-530U3C-530U4C:~$ ubuntu-bug linux caravena@caravena-530U3C-530U4C:~$ [12375:12409:1218/134054:ERROR:nss_util.cc(809)] After loading Root Certs, loaded==false: NSS error code: -8018 Se creó una nueva ventana en la sesión existente del navegador. [7185:7220:1218/142107:ERROR:connection_factory_impl.cc(367)] Failed to connect to MCS endpoint with error -106 [7185:7318:1218/142111:ERROR:get_updates_processor.cc(242)] PostClientToServerMessage() failed during GetUpdates [7185:7318:1218/142115:ERROR:get_updates_processor.cc(242)] PostClientToServerMessage() failed during GetUpdates [7185:7220:1218/142117:ERROR:connection_factory_impl.cc(367)] Failed to connect to MCS endpoint with error -105 [7185:7220:1218/143613:ERROR:connection_factory_impl.cc(367)] Failed to connect to MCS endpoint with error -106 [7185:7318:1218/144540:ERROR:get_updates_processor.cc(242)] PostClientToServerMessage() failed during GetUpdates [7185:7220:1218/145430:ERROR:connection_factory_impl.cc(367)] Failed to connect to MCS endpoint with error -106 [7185:7318:1218/162533:ERROR:get_updates_processor.cc(242)] PostClientToServerMessage() failed during GetUpdates [7185:7220:1218/162540:ERROR:connection_factory_impl.cc(367)] Failed to connect to MCS endpoint with error -21 [7185:7318:1218/162540:ERROR:get_updates_processor.cc(242)] PostClientToServerMessage() failed during GetUpdates caravena@caravena-530U3C-530U4C:~$ ubuntu-bug linux caravena@caravena-530U3C-530U4C:~$ [18327:18362:1218/165822:ERROR:nss_util.cc(809)] After loading Root Certs, loaded==false: NSS error code: -8018 ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: apport 2.20.4-0ubuntu1 ProcVersionSignature: Ubuntu 4.9.0-11.12-generic 4.9.0 Uname: Linux 4.9.0-11-generic x86_64 ApportVersion: 2.20.4-0ubuntu1 Architecture: amd64 CurrentDesktop: GNOME Date: Sun Dec 18 17:32:53 2016 InstallationDate: Installed on 2015-07-26 (511 days ago) InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha amd64 (20150723) PackageArchitecture: all SourcePackage: apport UpgradeStatus: Upgraded to zesty on 2016-10-29 (50 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1650961/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp