[Kernel-packages] [Bug 1776113] Re: Laptop does not suspend when lid is closed
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1776113 Title: Laptop does not suspend when lid is closed Status in linux package in Ubuntu: Expired Bug description: $ lsb_release -rd Description: Ubuntu 18.04 LTS Release: 18.04 In Tweaks > Power, "Suspend when laptop lid is closed" is ON, but my laptop does not suspend when the lid is closed. The laptop is a Thinkpad P50. When closing the laptop lid, no events show up in dmesg. This is my /etc/systemd/login.conf: [Login] #NAutoVTs=6 #ReserveVT=6 #KillUserProcesses=no #KillOnlyUsers= #KillExcludeUsers=root #InhibitDelayMaxSec=5 #HandlePowerKey=poweroff #HandleSuspendKey=suspend #HandleHibernateKey=hibernate HandleLidSwitch=suspend HandleLidSwitchDocked=suspend #PowerKeyIgnoreInhibited=no #SuspendKeyIgnoreInhibited=no #HibernateKeyIgnoreInhibited=no #LidSwitchIgnoreInhibited=yes #HoldoffTimeoutSec=30s #IdleAction=ignore #IdleActionSec=30min #RuntimeDirectorySize=10% #RemoveIPC=yes #InhibitorsMax=8192 #SessionsMax=8192 #UserTasksMax=33% ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-22-generic 4.15.0-22.24 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Jun 10 14:16:10 2018 InstallationDate: Installed on 2018-03-26 (76 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed UpgradeStatus: Upgraded to bionic on 2018-05-17 (24 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1776113/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1776153] Re: package linux-headers-4.13.0-43 (not installed) failed to install/upgrade: unable to open '/usr/src/linux-headers-4.13.0-43/drivers/misc/genwqe/Makefile.dpkg-new':
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1776153 Title: package linux-headers-4.13.0-43 (not installed) failed to install/upgrade: unable to open '/usr/src/linux- headers-4.13.0-43/drivers/misc/genwqe/Makefile.dpkg-new': Operation not permitted Status in linux package in Ubuntu: Expired Bug description: I am keep on getting pop up error message ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-headers-4.13.0-43 (not installed) ProcVersionSignature: Ubuntu 4.13.0-41.46~16.04.1-generic 4.13.16 Uname: Linux 4.13.0-41-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 Date: Mon Jun 11 11:00:55 2018 DpkgHistoryLog: DuplicateSignature: package:linux-headers-4.13.0-43:(not installed) Unpacking linux-headers-4.13.0-43 (4.13.0-43.48~16.04.1) ... dpkg: error processing archive /var/cache/apt/archives/linux-headers-4.13.0-43_4.13.0-43.48~16.04.1_all.deb (--unpack): unable to open '/usr/src/linux-headers-4.13.0-43/drivers/misc/genwqe/Makefile.dpkg-new': Operation not permitted ErrorMessage: unable to open '/usr/src/linux-headers-4.13.0-43/drivers/misc/genwqe/Makefile.dpkg-new': Operation not permitted InstallationDate: Installed on 2017-10-26 (227 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) RelatedPackageVersions: dpkg 1.18.4ubuntu1.3 apt 1.2.24 SourcePackage: linux-hwe Title: package linux-headers-4.13.0-43 (not installed) failed to install/upgrade: unable to open '/usr/src/linux-headers-4.13.0-43/drivers/misc/genwqe/Makefile.dpkg-new': Operation not permitted UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1776153/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1776376] Re: Intel 9462 bluetooth and wifi doesn't work
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1776376 Title: Intel 9462 bluetooth and wifi doesn't work Status in linux package in Ubuntu: Expired Bug description: Besides the issue mentioned above,the keyboard is not completely suitable. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-21-generic 4.4.0-21.37 [modified: boot/vmlinuz-4.4.0-21-generic] ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gjd1940 F pulseaudio CurrentDesktop: Unity Date: Tue Jun 12 10:33:31 2018 HibernationDevice: RESUME=UUID=a93c190f-117c-44c6-8595-37cc0499c28b InstallationDate: Installed on 2018-06-11 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) IwConfig: enp3s0no wireless extensions. lono wireless extensions. MachineType: Dell Inc. G3 3579 ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic.efi.signed root=UUID=7b8b7532-3642-4369-bfeb-04208cf72efc ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-21-generic N/A linux-backports-modules-4.4.0-21-generic N/A linux-firmware1.157.19 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/25/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.0 dmi.board.name: 0JYXHN dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.1.0:bd05/25/2018:svnDellInc.:pnG33579:pvr:rvnDellInc.:rn0JYXHN:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.name: G3 3579 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1776376/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1684240] Re: Lagging square around mouse pointer
Update, logout and login again resolves the issue!!! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-375 in Ubuntu. https://bugs.launchpad.net/bugs/1684240 Title: Lagging square around mouse pointer Status in nvidia-graphics-drivers-375 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-384 package in Ubuntu: Confirmed Status in plasma-workspace package in Ubuntu: Confirmed Bug description: (This can also be an nvidia related problem) Mouse pointer behaves as if it has an invisible square attached to it. This square covers some area next to the pointer, but it is not always clear exactly where (a link to a screenshot is shown below, please note the white square with some text from the previous webpage displayed in that window). This makes selecting text difficult, as one never knows where exactly the selection ends. Also, scrolling in some windows becomes problematic, as the pointer shadows a part of the scrollbar. When a text is being typed, one needs to make sure that the pointer is parked sufficiently far from the text (so, to make a long story short, this is very annoying). This behavior does not depend on the choice of the cursor theme. (A link to the screenshot: https://goo.gl/photos/92KKGyFs3AkdxYb79) ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: plasma-workspace 4:5.9.4-0ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 Uname: Linux 4.10.0-19-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 CurrentDesktop: KDE Date: Wed Apr 19 10:41:58 2017 InstallationDate: Installed on 2015-06-05 (684 days ago) InstallationMedia: Kubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) SourcePackage: plasma-workspace UpgradeStatus: Upgraded to zesty on 2017-04-13 (5 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-375/+bug/1684240/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1684240] Re: Lagging square around mouse pointer
Have the same issue. My system: Ubuntu 16.04.5, latest updates. Unity desktop. Nvidia 384.130 driver. DisplayLink 4.2, tried also with 4.1, the same issue. I also uploaded 12 seconds video: https://www.youtube.com/watch?v=vVwa- cVU_cA Can't confirm if this is Nvidia or DisplayLink or both drivers issue. For sure, in my case, uninstalling DisplayLink driver everything works fine. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-375 in Ubuntu. https://bugs.launchpad.net/bugs/1684240 Title: Lagging square around mouse pointer Status in nvidia-graphics-drivers-375 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-384 package in Ubuntu: Confirmed Status in plasma-workspace package in Ubuntu: Confirmed Bug description: (This can also be an nvidia related problem) Mouse pointer behaves as if it has an invisible square attached to it. This square covers some area next to the pointer, but it is not always clear exactly where (a link to a screenshot is shown below, please note the white square with some text from the previous webpage displayed in that window). This makes selecting text difficult, as one never knows where exactly the selection ends. Also, scrolling in some windows becomes problematic, as the pointer shadows a part of the scrollbar. When a text is being typed, one needs to make sure that the pointer is parked sufficiently far from the text (so, to make a long story short, this is very annoying). This behavior does not depend on the choice of the cursor theme. (A link to the screenshot: https://goo.gl/photos/92KKGyFs3AkdxYb79) ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: plasma-workspace 4:5.9.4-0ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 Uname: Linux 4.10.0-19-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 CurrentDesktop: KDE Date: Wed Apr 19 10:41:58 2017 InstallationDate: Installed on 2015-06-05 (684 days ago) InstallationMedia: Kubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) SourcePackage: plasma-workspace UpgradeStatus: Upgraded to zesty on 2017-04-13 (5 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-375/+bug/1684240/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1785319] Re: All kinds of problems on wake from lid close 18.04
tom, this report is being closed due to your last comment https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1785319/comments/34 regarding this is no longer reproducible. For future reference you can manage the status of your own bugs by clicking on the current status in the yellow line and then choosing a new status in the revealed drop down box. You can learn more about bug statuses at https://wiki.ubuntu.com/Bugs/Status. Thank you again for taking the time to report this bug and helping to make Ubuntu better. Please submit any future bugs you may find. ** Changed in: linux (Ubuntu) Importance: Low => Undecided ** Changed in: linux (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1785319 Title: All kinds of problems on wake from lid close 18.04 Status in linux package in Ubuntu: Invalid Bug description: This seems to be multiple packages, Ubuntu 18.04 itself (because 17.10 and all previous versions worked fine), and firmware. When wake from lid close, GUI freezes up and un-freezes every few seconds. Wifi won't even scan for networks, much less join one. Probably more things are wrong, but that's what's visible to me. Here's dmesg recent errors: [43548.249307] ath10k_warn: 129 callbacks suppressed [43548.249309] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.285609] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.316369] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.347057] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.382893] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.419305] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.455788] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.492277] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.523109] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.553793] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43551.161054] ath10k_pci :02:00.0: failed to read device register, device is gone [43551.270391] ath10k_pci :02:00.0: firmware crashed! (guid c2f1d8ad-ba2b-4c87-a0e1-9dff072ac468) [43551.270394] ath10k_pci :02:00.0: qca6174 hw3.2 target 0x0503 chip_id 0x00340aff sub 1a56:1535 [43551.270396] ath10k_pci :02:00.0: kconfig debug 0 debugfs 1 tracing 1 dfs 0 testmode 0 [43551.270803] ath10k_pci :02:00.0: firmware ver WLAN.RM.4.4.1-00079-QCARMSWPZ-1 api 6 features wowlan,ignore-otp crc32 fd869beb [43551.271233] ath10k_pci :02:00.0: board_file api 2 bmi_id N/A crc32 20d869c3 [43551.271235] ath10k_pci :02:00.0: htt-ver 3.47 wmi-op 4 htt-op 3 cal otp max-sta 32 raw 0 hwcrypto 1 [43551.271242] ath10k_pci :02:00.0: failed to read firmware dump area: -28 [43551.271243] ath10k_pci :02:00.0: Copy Engine register dump: [43551.417001] ath10k_pci :02:00.0: [00]: 0x00034400 4294967295 4294967295 4294967295 4294967295 [43551.562682] ath10k_pci :02:00.0: [01]: 0x00034800 4294967295 4294967295 4294967295 4294967295 [43551.708407] ath10k_pci :02:00.0: [02]: 0x00034c00 4294967295 4294967295 4294967295 4294967295 [43551.841610] ath10k_pci :02:00.0: [03]: 0x00035000 4294967295 4294967295 4294967295 4294967295 [43551.975925] ath10k_pci :02:00.0: [04]: 0x00035400 4294967295 4294967295 4294967295 4294967295 [43552.108938] ath10k_pci :02:00.0: [05]: 0x00035800 4294967295 4294967295 4294967295 4294967295 [43552.254895] ath10k_pci :02:00.0: [06]: 0x00035c00 4294967295 4294967295 4294967295 4294967295 [43552.400652] ath10k_pci :02:00.0: [07]: 0x00036000 4294967295 4294967295 4294967295 4294967295 [43552.400689] ath10k_pci :02:00.0: failed to reset chip: -5 [43552.400690] ath10k_pci :02:00.0: Could not init hif: -5 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tom1383 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-04-26 (103 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180228) MachineType: Dell Inc. XPS 15 9560 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-30-generic root=UUID=9ccc05c8-ea98-4229-a4d3-6d3a292df6df ro quiet splash acpi_rev_override=5 nouveau.modeset=0
[Kernel-packages] [Bug 1765053] Re: Errors were encountered while processing: /tmp/apt-dpkg-install-x8YVfC/03-libnvidia-compute-390_390.48-0ubuntu2_i386.deb
I had the same problem 1) Installed nvidia-driver-390 (390.48 via software-properties-gtk) 2) Restarted to find out that it didn't built for kernel 4.17 3) Purged package, autoremoved, added repo ppa:graphics-drivers/ppa for driver 390.77 4) Restarted, resolution was low (probably because nouveau remained blocked) 5) Started to install nvidia-390, got the same error 6) sudo rm '/etc/OpenCL/vendors/nvidia.icd' 7) sudo apt --fix-broken install After restart everything works. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1765053 Title: Errors were encountered while processing: /tmp/apt-dpkg-install- x8YVfC/03-libnvidia-compute-390_390.48-0ubuntu2_i386.deb Status in nvidia-graphics-drivers-390 package in Ubuntu: Confirmed Status in ubuntu-drivers-common package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-390 source package in Bionic: Confirmed Status in ubuntu-drivers-common source package in Bionic: Confirmed Bug description: Using Ubuntu MATE 18.04 daily ubuntu-drivers fails to install the nvidia 390 drivers. Here is what I captured on stdout. $ sudo ubuntu-drivers autoinstall Reading package lists... Done Building dependency tree Reading state information... Done The following package was automatically installed and is no longer required: gnome-session-common Use 'sudo apt autoremove' to remove it. The following additional packages will be installed: libnvidia-cfg1-390 libnvidia-common-390 libnvidia-compute-390 libnvidia-compute-390:i386 libnvidia-decode-390 libnvidia-decode-390:i386 libnvidia-encode-390 libnvidia-encode-390:i386 libnvidia-fbc1-390 libnvidia-fbc1-390:i386 libnvidia-gl-390 libnvidia-gl-390:i386 libnvidia-ifr1-390 libnvidia-ifr1-390:i386 libwayland-client0:i386 libwayland-server0:i386 libxnvctrl0 nvidia-compute-390 nvidia-compute-no-dkms-390 nvidia-compute-utils-390 nvidia-dkms-390 nvidia-kernel-source-390 nvidia-settings nvidia-utils-390 screen-resolution-extra xserver-xorg-video-nvidia-390 The following NEW packages will be installed libnvidia-cfg1-390 libnvidia-common-390 libnvidia-compute-390 libnvidia-compute-390:i386 libnvidia-decode-390 libnvidia-decode-390:i386 libnvidia-encode-390 libnvidia-encode-390:i386 libnvidia-fbc1-390 libnvidia-fbc1-390:i386 libnvidia-gl-390 libnvidia-gl-390:i386 libnvidia-ifr1-390 libnvidia-ifr1-390:i386 libwayland-client0:i386 libwayland-server0:i386 libxnvctrl0 nvidia-compute-390 nvidia-compute-no-dkms-390 nvidia-compute-utils-390 nvidia-dkms-390 nvidia-driver-390 nvidia-kernel-source-390 nvidia-settings nvidia-utils-390 screen-resolution-extra xserver-xorg-video-nvidia-390 0 to upgrade, 27 to newly install, 0 to remove and 0 not to upgrade. Need to get 0 B/85.3 MB of archives. After this operation, 365 MB of additional disk space will be used. Selecting previously unselected package libnvidia-cfg1-390:amd64. (Reading database ... 258596 files and directories currently installed.) Preparing to unpack .../00-libnvidia-cfg1-390_390.48-0ubuntu2_amd64.deb ... Unpacking libnvidia-cfg1-390:amd64 (390.48-0ubuntu2) ... Selecting previously unselected package libnvidia-common-390. Preparing to unpack .../01-libnvidia-common-390_390.48-0ubuntu2_all.deb ... Unpacking libnvidia-common-390 (390.48-0ubuntu2) ... Selecting previously unselected package libnvidia-compute-390:amd64. Preparing to unpack .../02-libnvidia-compute-390_390.48-0ubuntu2_amd64.deb ... Unpacking libnvidia-compute-390:amd64 (390.48-0ubuntu2) ... Selecting previously unselected package libnvidia-compute-390:i386. Preparing to unpack .../03-libnvidia-compute-390_390.48-0ubuntu2_i386.deb ... Unpacking libnvidia-compute-390:i386 (390.48-0ubuntu2) ... dpkg: error processing archive /tmp/apt-dpkg-install-x8YVfC/03-libnvidia-compute-390_390.48-0ubuntu2_i386.deb (--unpack): trying to overwrite shared '/etc/OpenCL/vendors/nvidia.icd', which is different from other instances of package libnvidia-compute-390:i386 dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) Selecting previously unselected package libnvidia-decode-390:amd64. Preparing to unpack .../04-libnvidia-decode-390_390.48-0ubuntu2_amd64.deb ... Unpacking libnvidia-decode-390:amd64 (390.48-0ubuntu2) ... Selecting previously unselected package libnvidia-decode-390:i386. Preparing to unpack .../05-libnvidia-decode-390_390.48-0ubuntu2_i386.deb ... Unpacking libnvidia-decode-390:i386 (390.48-0ubuntu2) ... Selecting previously unselected package libnvidia-encode-390:i386. Preparing to unpack .../06-libnvidia-encode-390_390.48-0ubuntu2_i386.deb ... Unpacking libnvidia-encode-390:i386 (390.48-0ubuntu2) ... Selecting previously unselected package libnvidia-encode-390:amd64. Preparing to unpack .../07-libnvidia-encode-390_390.48-0ubuntu2_amd64.deb ...
[Kernel-packages] [Bug 1778265] Re: Bionic update: upstream stable patchset 2018-06-22
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: linux (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1778265
Title:
Bionic update: upstream stable patchset 2018-06-22
Status in linux package in Ubuntu:
Confirmed
Status in linux source package in Bionic:
Fix Committed
Bug description:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly from a mainline/stable Linux tree or
a minimally backported form of that patch. The following upstream
stable patches should be included in the Ubuntu kernel:
upstream stable patchset 2018-06-22 (ported from v4.14.39 and v4.16.7)
from git://git.kernel.org/
drm/amd/display: Disallow enabling CRTC without primary plane with FB
drm/amd/display: Fix deadlock when flushing irq
drm/i915/audio: set minimum CD clock to twice the BCLK
drm/i915/fbdev: Enable late fbdev initial configuration
drm/edid: Reset more of the display info
module: Fix display of wrong module .text address
PCI / PM: Do not clear state_saved in pci_pm_freeze() when smart suspend is
set
ASoC: dmic: Fix clock parenting
block: do not use interruptible wait anywhere
serial: mvebu-uart: Fix local flags handling on termios update
powerpc/eeh: Fix race with driver un/bind
arm/arm64: KVM: Add PSCI version selection API
tick/sched: Do not mess with an enqueued hrtimer
x86/microcode: Do not exit early from __reload_late()
x86/microcode/intel: Save microcode patch unconditionally
x86/smpboot: Don't use mwait_play_dead() on AMD systems
x86/ipc: Fix x32 version of shmid64_ds and msqid64_ds
tools/lib/subcmd/pager.c: do not alias select() params
objtool, perf: Fix GCC 8 -Wrestrict error
drm/i915: Enable display WA#1183 from its correct spot
drm/amdgpu: set COMPUTE_PGM_RSRC1 for SGPR/VGPR clearing shaders
earlycon: Use a pointer table to fix __earlycon_table stride
fpga-manager: altera-ps-spi: preserve nCONFIG state
libceph: validate con->state at the top of try_write()
libceph: reschedule a tick in finish_hunting()
libceph: un-backoff on tick when we have a authenticated session
ASoC: fsl_esai: Fix divisor calculation failure at lower ratio
crypto: drbg - set freed buffers to NULL
KVM: arm/arm64: Close VMID generation race
ARM: socfpga_defconfig: Remove QSPI Sector 4K size force
ARM: amba: Don't read past the end of sysfs "driver_override" buffer
ARM: amba: Fix race condition with driver_override
ARM: amba: Make driver_override output consistent with other buses
PCI: aardvark: Fix PCIe Max Read Request Size setting
PCI: aardvark: Use ISR1 instead of ISR0 interrupt in legacy irq mode
PCI: aardvark: Set PIO_ADDR_LS correctly in advk_pcie_rd_conf()
PCI: aardvark: Fix logic in advk_pcie_{rd,wr}_conf()
ANDROID: binder: prevent transactions into own process.
vfio: ccw: process ssch with interrupts disabled
bfq-iosched: ensure to clear bic/bfqq pointers when preparing request
scsi: sd: Defer spinning up drive while SANITIZE is in progress
kobject: don't use WARN for registration failures
mtd: rawnand: tango: Fix struct clk memory leak
mtd: cfi: cmdset_0002: Do not allow read/write to suspend erase block.
mtd: cfi: cmdset_0001: Workaround Micron Erase suspend bug.
mtd: cfi: cmdset_0001: Do not allow read/write to suspend erase block.
mtd: spi-nor: cadence-quadspi: Fix page fault kernel panic
ALSA: hda/realtek - change the location for one of two front mics
ALSA: hda/realtek - Update ALC255 depop optimize
ALSA: hda/realtek - Add some fixes for ALC233
ALSA: hda: Hardening for potential Spectre v1
ALSA: seq: oss: Hardening for potential Spectre v1
ALSA: seq: oss: Fix unbalanced use lock for synth MIDI device
ALSA: core: Report audio_tstamp in snd_pcm_sync_ptr
ALSA: pcm: Return negative delays from SNDRV_PCM_IOCTL_DELAY.
ALSA: control: Hardening for potential Spectre v1
ALSA: rme9652: Hardening for potential Spectre v1
ALSA: hdspm: Hardening for potential Spectre v1
ALSA: asihpi: Hardening for potential Spectre v1
ALSA: opl3: Hardening for potential Spectre v1
ALSA: hda - Skip jack and others for non-existing PCM streams
ALSA: dice: fix error path to destroy initialized stream data
ALSA: dice: fix OUI for TC group
tty: Use __GFP_NOFAIL for tty_ldisc_get()
tty: Avoid possible error pointer dereference at tty_ldisc_restore().
tty: n_gsm: Fix DLCI handling for ADM mode if debug & 2 is not set
tty: n_gsm: Fix long delays with control frame timeouts in ADM mode
tty: Don't call panic() at tty_ldisc_init()
drm/virtio: fix vq wait_event condition
[Kernel-packages] [Bug 1764645] Re: Bluetooth not working
Hi, it's finally OK now on 4.15.0-31. Thanks for helping! ;-)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1764645
Title:
Bluetooth not working
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Bionic:
Fix Committed
Bug description:
== SRU Justification ==
A regression was discovered in Bionic. The regression was introduced by
mainline commit f44cb4b19ed4, which then made it's way into Bionic in
4.15.0-14 as commit c91729972ac6 via stable updates.
This regression is fixed by mainline commit 803cdb8ce584. Commit
803cdb8ce584 was also cc'd to stable. However, it has not landed in
upstream stable 4.15 or Bionic.
== Fix ==
803cdb8ce584 ("Bluetooth: btusb: Apply QCA Rome patches for some ATH3012
models")
== Regression Potential ==
Low. This fix has also been cc'd to upstream stable, so it has had
additonal upstream review.
== Test Case ==
A test kernel was built with this patch and tested by the original bug
reporter.
The bug reporter states the test kernel resolved the bug.
I've installed the Ubuntu Bionic Beta 2 and everything works fine but
the bluetooth (perfectly working with Xenial). In bluetooth control
panel the slider is impossible to move to "on".
1) Ubuntu Release (via 'lsb_release -rd')
Description: Ubuntu Bionic Beaver (development branch)
Release: 18.04
2) Version of package (apt-cache policy gnome-bluetooth)
gnome-bluetooth:
Installato: 3.28.0-2
Candidato: 3.28.0-2
Tabella versione:
*** 3.28.0-2 500
500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages
100 /var/lib/dpkg/status
3) What you expected to happen
I expected to switch on the bluetooth.
4) What happened instead
Bluetooth won't switch on.
5) Output of rfkill list is:
0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
1: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
6) Output of lspci -knn | grep Net -A3; lsusb; dmesg | grep -i blue is:
03:00.0 Network controller [0280]: Qualcomm Atheros AR9462 Wireless
Network Adapter [168c:0034] (rev 01)
Subsystem: Bigfoot Networks, Inc. Killer Wireless-N 1202 Half-
size Mini PCIe Card [1a56:2003]
Kernel driver in use: ath9k
Kernel modules: ath9k
04:00.0 Ethernet controller [0200]: Qualcomm Atheros QCA8171 Gigabit
Ethernet [1969:10a1] (rev 10)
Bus 002 Device 002: ID 8087:8000 Intel Corp.
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 8087:8008 Intel Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 004: ID 04f2:b414 Chicony Electronics Co., Ltd
Bus 003 Device 003: ID 0cf3:3004 Atheros Communications, Inc.
AR3012 Bluetooth 4.0
Bus 003 Device 002: ID 0b05:17c4 ASUSTek Computer, Inc.
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
[ 17.715399] Bluetooth: Core ver 2.22
[ 17.715414] Bluetooth: HCI device and connection manager initialized
[ 17.715416] Bluetooth: HCI socket layer initialized
[ 17.715418] Bluetooth: L2CAP socket layer initialized
[ 17.715422] Bluetooth: SCO socket layer initialized
[ 17.723207] Bluetooth: hci0: don't support firmware rome 0x1102
[ 18.600648] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 18.600649] Bluetooth: BNEP filters: protocol multicast
[ 18.600651] Bluetooth: BNEP socket layer initialized
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-15-generic 4.15.0-15.16
ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
Uname: Linux 4.15.0-15-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.9-0ubuntu5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: stormy 1484 F pulseaudio
/dev/snd/controlC0: stormy 1484 F pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Tue Apr 17 08:46:30 2018
HibernationDevice: RESUME=UUID=3f513ca9-6817-4099-9718-fee68d68ec11
InstallationDate: Installed on 2018-04-16 (0 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404)
MachineType: ASUSTeK COMPUTER INC. G750JH
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=it_IT.UTF-8
SHELL=/bin/bash
ProcFB: 0 EFI VGA
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-15-generic.efi.signed
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
RelatedPackageVersions:
linux-restricted-modules-4.15.0-15-generic N/A
linux-backports-modules-4.15.0-15-generic N/A
linux-firmware 1.173
[Kernel-packages] [Bug 1774950] Re: Suspend fails in Ubuntu and Kubuntu 18.04 but works fine in Ubuntu and Kubuntu 17.10 (and on Kubuntu 18.04 using kernel 4.14.47)
Hello, is there a release which has the fix committed? Because I wanted to try the patched kernel with non-free nvidia drivers (390) are they compatible?. When installing it with dpkg, the machine says that the kernel-image gives conflict with the present one (last 18.04 kernel). I apologize for my newbie knowledge. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1774950 Title: Suspend fails in Ubuntu and Kubuntu 18.04 but works fine in Ubuntu and Kubuntu 17.10 (and on Kubuntu 18.04 using kernel 4.14.47) Status in linux package in Ubuntu: Fix Committed Status in linux source package in Bionic: Confirmed Status in linux source package in Cosmic: Fix Committed Bug description: ===SRU Justification=== [Impact] Systems with acpi-lpss can't do S3/S4 on Bionic. [Test] Users confirmed these patches work for them. [Fix] Commit a192aa923b66a (ACPI / LPSS: Consolidate runtime PM and system sleep handling) applies quirks for both runtime and system suspend. This causes problems for some systems, so avoid using quirks on S3 and S4. [Regression Potential] Low. These patches are in upstream stable, and it brings back driver's old behavior. ===Original Bug Report=== I have installed Kubuntu 18.04 on 3 different machines (my friend's and my own) with no suspend problems but my HP Pavilion 11 x360 does not suspend. It suspends fine with Ubuntu 17.10, Kubuntu 17.10, Devuan Jesse, Devuan ASCII and Windows 10 but fails with Ubuntu 18.04 and Kubuntu 18.04. I have also tried suspend using a live USB of 18.04 on this machine and it fails in the same way, so does not appear to be caused by any additional programs that I had installed. By installing an older kernel (4.14) on Kubuntu 18.04 the suspend function works as expected. Running Kubuntu 18.04 with kernels 4.15, 4.16, 4.17 results in the suspend failure that freezes the machine and requires a hard reset. Correct behaviour is - Screen goes blank, fan goes off, power LED flashes to show machine is in suspend. Pressing power button triggers 'resume' function. What happens - Screen goes blank, fan stays on, power LED stays on. Machine stays in this state and does not respond to any keyboard interaction, mouse movement or power button presses. Ctrl + Alt + f1 (or f2, f3, f4 etc) does not get any response. The only way to use the machine is to shut down by holding down the power button. Checking the logs suggests that the machine believes it is in suspend mode sleep [deep] when it isn't. Having to hard reset to get any response means that the kernel logs say no more than sleep [deep] pm-suspend also results in the same problems with kernels 4.15 and 4.16, but works fine with 4.14. It is curious that a machine that suspends fine on an earlier 4.14 kernel no longer works with 4.15 and above, whilst 3 other machines (including one with pretty similar hardware) do not exhibit this problem. There are only a handful of questions about it on the forums but at least 3 other people have the same problem: https://askubuntu.com/questions/1029405/ubuntu-18-04-crashes-on- resuming-from-suspend https://askubuntu.com/questions/1041369/after-upgrading- from-17-10-ubuntu-18-04-wont-sleep-suspend I am attempting to round up anyone else with the same issue and point them to this bug report. My laptop is HP Pavilion x360 11-n013na Matalaks is Acer Aspire ES1-511 collisionTwo has XPS 9560 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774950/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1785319] Re: All kinds of problems on wake from lid close 18.04
I can't replicate it since the report. I have no idea why, maybe the Ubuntu releases patched it. I haven't changed anything that should have fixed this, to my knowledge, but it just woke up again with wifi OK. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1785319 Title: All kinds of problems on wake from lid close 18.04 Status in linux package in Ubuntu: Incomplete Bug description: This seems to be multiple packages, Ubuntu 18.04 itself (because 17.10 and all previous versions worked fine), and firmware. When wake from lid close, GUI freezes up and un-freezes every few seconds. Wifi won't even scan for networks, much less join one. Probably more things are wrong, but that's what's visible to me. Here's dmesg recent errors: [43548.249307] ath10k_warn: 129 callbacks suppressed [43548.249309] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.285609] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.316369] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.347057] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.382893] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.419305] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.455788] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.492277] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.523109] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.553793] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43551.161054] ath10k_pci :02:00.0: failed to read device register, device is gone [43551.270391] ath10k_pci :02:00.0: firmware crashed! (guid c2f1d8ad-ba2b-4c87-a0e1-9dff072ac468) [43551.270394] ath10k_pci :02:00.0: qca6174 hw3.2 target 0x0503 chip_id 0x00340aff sub 1a56:1535 [43551.270396] ath10k_pci :02:00.0: kconfig debug 0 debugfs 1 tracing 1 dfs 0 testmode 0 [43551.270803] ath10k_pci :02:00.0: firmware ver WLAN.RM.4.4.1-00079-QCARMSWPZ-1 api 6 features wowlan,ignore-otp crc32 fd869beb [43551.271233] ath10k_pci :02:00.0: board_file api 2 bmi_id N/A crc32 20d869c3 [43551.271235] ath10k_pci :02:00.0: htt-ver 3.47 wmi-op 4 htt-op 3 cal otp max-sta 32 raw 0 hwcrypto 1 [43551.271242] ath10k_pci :02:00.0: failed to read firmware dump area: -28 [43551.271243] ath10k_pci :02:00.0: Copy Engine register dump: [43551.417001] ath10k_pci :02:00.0: [00]: 0x00034400 4294967295 4294967295 4294967295 4294967295 [43551.562682] ath10k_pci :02:00.0: [01]: 0x00034800 4294967295 4294967295 4294967295 4294967295 [43551.708407] ath10k_pci :02:00.0: [02]: 0x00034c00 4294967295 4294967295 4294967295 4294967295 [43551.841610] ath10k_pci :02:00.0: [03]: 0x00035000 4294967295 4294967295 4294967295 4294967295 [43551.975925] ath10k_pci :02:00.0: [04]: 0x00035400 4294967295 4294967295 4294967295 4294967295 [43552.108938] ath10k_pci :02:00.0: [05]: 0x00035800 4294967295 4294967295 4294967295 4294967295 [43552.254895] ath10k_pci :02:00.0: [06]: 0x00035c00 4294967295 4294967295 4294967295 4294967295 [43552.400652] ath10k_pci :02:00.0: [07]: 0x00036000 4294967295 4294967295 4294967295 4294967295 [43552.400689] ath10k_pci :02:00.0: failed to reset chip: -5 [43552.400690] ath10k_pci :02:00.0: Could not init hif: -5 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tom1383 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-04-26 (103 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180228) MachineType: Dell Inc. XPS 15 9560 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-30-generic root=UUID=9ccc05c8-ea98-4229-a4d3-6d3a292df6df ro quiet splash acpi_rev_override=5 nouveau.modeset=0 enable_psr=1 disable_power_well=0 pci=noaer pcie_aspm=force nmi_watchdog=0 nouveau.runpm=0 vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-30.32-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-30-generic N/A linux-backports-modules-4.15.0-30-generic N/A linux-firmware 1.173.1 Tags: bionic Uname: Linux 4.15.0-30-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom
[Kernel-packages] [Bug 1228263] syslog.txt
apport information ** Attachment added: "syslog.txt" https://bugs.launchpad.net/bugs/1228263/+attachment/5174178/+files/syslog.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1228263 Title: Volume control doesn't work automatically when connecting Bluetooth device. Status in bluez package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: Incomplete Bug description: When I connect a Bluetooth device, sound is automatically forwarded to the device but volume controls still control the internal sound card device. I must open the sound settings and click on the Bluetooth output device to use volume controls. I wish that the volume controls would automatically control whatever output device is actually active. :) This bug has existed for many versions of Ubuntu now. --- ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 EcryptfsInUse: Yes InstallationDate: Installed on 2016-07-25 (746 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) InterestingModules: btusb bluetooth MachineType: TOSHIBA TECRA R950 Package: pulseaudio PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-130-generic root=UUID=c7679e9c-34aa-4c9b-8e58-05ec7b8e4f63 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-130.156-generic 4.4.134 Tags: xenial Uname: Linux 4.4.0-130-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip libvirtd lpadmin plugdev sambashare sudo vboxusers video _MarkForUpload: True dmi.bios.date: 10/01/2012 dmi.bios.vendor: TOSHIBA dmi.bios.version: Version 6.40 dmi.board.asset.tag: 00 dmi.board.name: TECRA R950 dmi.board.vendor: TOSHIBA dmi.board.version: Version A0 dmi.chassis.asset.tag: 00 dmi.chassis.type: 10 dmi.chassis.vendor: TOSHIBA dmi.chassis.version: Version 1.0 dmi.modalias: dmi:bvnTOSHIBA:bvrVersion6.40:bd10/01/2012:svnTOSHIBA:pnTECRAR950:pvrPT530U-00T007:rvnTOSHIBA:rnTECRAR950:rvrVersionA0:cvnTOSHIBA:ct10:cvrVersion1.0: dmi.product.name: TECRA R950 dmi.product.version: PT530U-00T007 dmi.sys.vendor: TOSHIBA hciconfig: hci0:Type: BR/EDR Bus: USB BD Address: C8:F7:33:2D:6B:6B ACL MTU: 310:10 SCO MTU: 64:8 UP RUNNING RX bytes:580 acl:0 sco:0 events:31 errors:0 TX bytes:368 acl:0 sco:0 commands:30 errors:0 mtime.conffile..etc.bluetooth.main.conf: 2018-05-24T08:46:03.060208 upstart.bluetooth.override: manual To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1228263/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1228263] rfkill.txt
apport information ** Attachment added: "rfkill.txt" https://bugs.launchpad.net/bugs/1228263/+attachment/5174177/+files/rfkill.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1228263 Title: Volume control doesn't work automatically when connecting Bluetooth device. Status in bluez package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: Incomplete Bug description: When I connect a Bluetooth device, sound is automatically forwarded to the device but volume controls still control the internal sound card device. I must open the sound settings and click on the Bluetooth output device to use volume controls. I wish that the volume controls would automatically control whatever output device is actually active. :) This bug has existed for many versions of Ubuntu now. --- ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 EcryptfsInUse: Yes InstallationDate: Installed on 2016-07-25 (746 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) InterestingModules: btusb bluetooth MachineType: TOSHIBA TECRA R950 Package: pulseaudio PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-130-generic root=UUID=c7679e9c-34aa-4c9b-8e58-05ec7b8e4f63 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-130.156-generic 4.4.134 Tags: xenial Uname: Linux 4.4.0-130-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip libvirtd lpadmin plugdev sambashare sudo vboxusers video _MarkForUpload: True dmi.bios.date: 10/01/2012 dmi.bios.vendor: TOSHIBA dmi.bios.version: Version 6.40 dmi.board.asset.tag: 00 dmi.board.name: TECRA R950 dmi.board.vendor: TOSHIBA dmi.board.version: Version A0 dmi.chassis.asset.tag: 00 dmi.chassis.type: 10 dmi.chassis.vendor: TOSHIBA dmi.chassis.version: Version 1.0 dmi.modalias: dmi:bvnTOSHIBA:bvrVersion6.40:bd10/01/2012:svnTOSHIBA:pnTECRAR950:pvrPT530U-00T007:rvnTOSHIBA:rnTECRAR950:rvrVersionA0:cvnTOSHIBA:ct10:cvrVersion1.0: dmi.product.name: TECRA R950 dmi.product.version: PT530U-00T007 dmi.sys.vendor: TOSHIBA hciconfig: hci0:Type: BR/EDR Bus: USB BD Address: C8:F7:33:2D:6B:6B ACL MTU: 310:10 SCO MTU: 64:8 UP RUNNING RX bytes:580 acl:0 sco:0 events:31 errors:0 TX bytes:368 acl:0 sco:0 commands:30 errors:0 mtime.conffile..etc.bluetooth.main.conf: 2018-05-24T08:46:03.060208 upstart.bluetooth.override: manual To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1228263/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1228263] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1228263/+attachment/5174173/+files/ProcModules.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1228263 Title: Volume control doesn't work automatically when connecting Bluetooth device. Status in bluez package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: Incomplete Bug description: When I connect a Bluetooth device, sound is automatically forwarded to the device but volume controls still control the internal sound card device. I must open the sound settings and click on the Bluetooth output device to use volume controls. I wish that the volume controls would automatically control whatever output device is actually active. :) This bug has existed for many versions of Ubuntu now. --- ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 EcryptfsInUse: Yes InstallationDate: Installed on 2016-07-25 (746 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) InterestingModules: btusb bluetooth MachineType: TOSHIBA TECRA R950 Package: pulseaudio PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-130-generic root=UUID=c7679e9c-34aa-4c9b-8e58-05ec7b8e4f63 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-130.156-generic 4.4.134 Tags: xenial Uname: Linux 4.4.0-130-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip libvirtd lpadmin plugdev sambashare sudo vboxusers video _MarkForUpload: True dmi.bios.date: 10/01/2012 dmi.bios.vendor: TOSHIBA dmi.bios.version: Version 6.40 dmi.board.asset.tag: 00 dmi.board.name: TECRA R950 dmi.board.vendor: TOSHIBA dmi.board.version: Version A0 dmi.chassis.asset.tag: 00 dmi.chassis.type: 10 dmi.chassis.vendor: TOSHIBA dmi.chassis.version: Version 1.0 dmi.modalias: dmi:bvnTOSHIBA:bvrVersion6.40:bd10/01/2012:svnTOSHIBA:pnTECRAR950:pvrPT530U-00T007:rvnTOSHIBA:rnTECRAR950:rvrVersionA0:cvnTOSHIBA:ct10:cvrVersion1.0: dmi.product.name: TECRA R950 dmi.product.version: PT530U-00T007 dmi.sys.vendor: TOSHIBA hciconfig: hci0:Type: BR/EDR Bus: USB BD Address: C8:F7:33:2D:6B:6B ACL MTU: 310:10 SCO MTU: 64:8 UP RUNNING RX bytes:580 acl:0 sco:0 events:31 errors:0 TX bytes:368 acl:0 sco:0 commands:30 errors:0 mtime.conffile..etc.bluetooth.main.conf: 2018-05-24T08:46:03.060208 upstart.bluetooth.override: manual To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1228263/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1228263] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1228263/+attachment/5174172/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1228263 Title: Volume control doesn't work automatically when connecting Bluetooth device. Status in bluez package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: Incomplete Bug description: When I connect a Bluetooth device, sound is automatically forwarded to the device but volume controls still control the internal sound card device. I must open the sound settings and click on the Bluetooth output device to use volume controls. I wish that the volume controls would automatically control whatever output device is actually active. :) This bug has existed for many versions of Ubuntu now. --- ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 EcryptfsInUse: Yes InstallationDate: Installed on 2016-07-25 (746 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) InterestingModules: btusb bluetooth MachineType: TOSHIBA TECRA R950 Package: pulseaudio PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-130-generic root=UUID=c7679e9c-34aa-4c9b-8e58-05ec7b8e4f63 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-130.156-generic 4.4.134 Tags: xenial Uname: Linux 4.4.0-130-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip libvirtd lpadmin plugdev sambashare sudo vboxusers video _MarkForUpload: True dmi.bios.date: 10/01/2012 dmi.bios.vendor: TOSHIBA dmi.bios.version: Version 6.40 dmi.board.asset.tag: 00 dmi.board.name: TECRA R950 dmi.board.vendor: TOSHIBA dmi.board.version: Version A0 dmi.chassis.asset.tag: 00 dmi.chassis.type: 10 dmi.chassis.vendor: TOSHIBA dmi.chassis.version: Version 1.0 dmi.modalias: dmi:bvnTOSHIBA:bvrVersion6.40:bd10/01/2012:svnTOSHIBA:pnTECRAR950:pvrPT530U-00T007:rvnTOSHIBA:rnTECRAR950:rvrVersionA0:cvnTOSHIBA:ct10:cvrVersion1.0: dmi.product.name: TECRA R950 dmi.product.version: PT530U-00T007 dmi.sys.vendor: TOSHIBA hciconfig: hci0:Type: BR/EDR Bus: USB BD Address: C8:F7:33:2D:6B:6B ACL MTU: 310:10 SCO MTU: 64:8 UP RUNNING RX bytes:580 acl:0 sco:0 events:31 errors:0 TX bytes:368 acl:0 sco:0 commands:30 errors:0 mtime.conffile..etc.bluetooth.main.conf: 2018-05-24T08:46:03.060208 upstart.bluetooth.override: manual To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1228263/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1228263] modified.conffile..etc.bluetooth.main.conf.txt
apport information ** Attachment added: "modified.conffile..etc.bluetooth.main.conf.txt" https://bugs.launchpad.net/bugs/1228263/+attachment/5174176/+files/modified.conffile..etc.bluetooth.main.conf.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1228263 Title: Volume control doesn't work automatically when connecting Bluetooth device. Status in bluez package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: Incomplete Bug description: When I connect a Bluetooth device, sound is automatically forwarded to the device but volume controls still control the internal sound card device. I must open the sound settings and click on the Bluetooth output device to use volume controls. I wish that the volume controls would automatically control whatever output device is actually active. :) This bug has existed for many versions of Ubuntu now. --- ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 EcryptfsInUse: Yes InstallationDate: Installed on 2016-07-25 (746 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) InterestingModules: btusb bluetooth MachineType: TOSHIBA TECRA R950 Package: pulseaudio PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-130-generic root=UUID=c7679e9c-34aa-4c9b-8e58-05ec7b8e4f63 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-130.156-generic 4.4.134 Tags: xenial Uname: Linux 4.4.0-130-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip libvirtd lpadmin plugdev sambashare sudo vboxusers video _MarkForUpload: True dmi.bios.date: 10/01/2012 dmi.bios.vendor: TOSHIBA dmi.bios.version: Version 6.40 dmi.board.asset.tag: 00 dmi.board.name: TECRA R950 dmi.board.vendor: TOSHIBA dmi.board.version: Version A0 dmi.chassis.asset.tag: 00 dmi.chassis.type: 10 dmi.chassis.vendor: TOSHIBA dmi.chassis.version: Version 1.0 dmi.modalias: dmi:bvnTOSHIBA:bvrVersion6.40:bd10/01/2012:svnTOSHIBA:pnTECRAR950:pvrPT530U-00T007:rvnTOSHIBA:rnTECRAR950:rvrVersionA0:cvnTOSHIBA:ct10:cvrVersion1.0: dmi.product.name: TECRA R950 dmi.product.version: PT530U-00T007 dmi.sys.vendor: TOSHIBA hciconfig: hci0:Type: BR/EDR Bus: USB BD Address: C8:F7:33:2D:6B:6B ACL MTU: 310:10 SCO MTU: 64:8 UP RUNNING RX bytes:580 acl:0 sco:0 events:31 errors:0 TX bytes:368 acl:0 sco:0 commands:30 errors:0 mtime.conffile..etc.bluetooth.main.conf: 2018-05-24T08:46:03.060208 upstart.bluetooth.override: manual To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1228263/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1228263] getfacl.txt
apport information ** Attachment added: "getfacl.txt" https://bugs.launchpad.net/bugs/1228263/+attachment/5174175/+files/getfacl.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1228263 Title: Volume control doesn't work automatically when connecting Bluetooth device. Status in bluez package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: Incomplete Bug description: When I connect a Bluetooth device, sound is automatically forwarded to the device but volume controls still control the internal sound card device. I must open the sound settings and click on the Bluetooth output device to use volume controls. I wish that the volume controls would automatically control whatever output device is actually active. :) This bug has existed for many versions of Ubuntu now. --- ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 EcryptfsInUse: Yes InstallationDate: Installed on 2016-07-25 (746 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) InterestingModules: btusb bluetooth MachineType: TOSHIBA TECRA R950 Package: pulseaudio PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-130-generic root=UUID=c7679e9c-34aa-4c9b-8e58-05ec7b8e4f63 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-130.156-generic 4.4.134 Tags: xenial Uname: Linux 4.4.0-130-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip libvirtd lpadmin plugdev sambashare sudo vboxusers video _MarkForUpload: True dmi.bios.date: 10/01/2012 dmi.bios.vendor: TOSHIBA dmi.bios.version: Version 6.40 dmi.board.asset.tag: 00 dmi.board.name: TECRA R950 dmi.board.vendor: TOSHIBA dmi.board.version: Version A0 dmi.chassis.asset.tag: 00 dmi.chassis.type: 10 dmi.chassis.vendor: TOSHIBA dmi.chassis.version: Version 1.0 dmi.modalias: dmi:bvnTOSHIBA:bvrVersion6.40:bd10/01/2012:svnTOSHIBA:pnTECRAR950:pvrPT530U-00T007:rvnTOSHIBA:rnTECRAR950:rvrVersionA0:cvnTOSHIBA:ct10:cvrVersion1.0: dmi.product.name: TECRA R950 dmi.product.version: PT530U-00T007 dmi.sys.vendor: TOSHIBA hciconfig: hci0:Type: BR/EDR Bus: USB BD Address: C8:F7:33:2D:6B:6B ACL MTU: 310:10 SCO MTU: 64:8 UP RUNNING RX bytes:580 acl:0 sco:0 events:31 errors:0 TX bytes:368 acl:0 sco:0 commands:30 errors:0 mtime.conffile..etc.bluetooth.main.conf: 2018-05-24T08:46:03.060208 upstart.bluetooth.override: manual To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1228263/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1228263] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1228263/+attachment/5174170/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1228263 Title: Volume control doesn't work automatically when connecting Bluetooth device. Status in bluez package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: Incomplete Bug description: When I connect a Bluetooth device, sound is automatically forwarded to the device but volume controls still control the internal sound card device. I must open the sound settings and click on the Bluetooth output device to use volume controls. I wish that the volume controls would automatically control whatever output device is actually active. :) This bug has existed for many versions of Ubuntu now. --- ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 EcryptfsInUse: Yes InstallationDate: Installed on 2016-07-25 (746 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) InterestingModules: btusb bluetooth MachineType: TOSHIBA TECRA R950 Package: pulseaudio PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-130-generic root=UUID=c7679e9c-34aa-4c9b-8e58-05ec7b8e4f63 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-130.156-generic 4.4.134 Tags: xenial Uname: Linux 4.4.0-130-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip libvirtd lpadmin plugdev sambashare sudo vboxusers video _MarkForUpload: True dmi.bios.date: 10/01/2012 dmi.bios.vendor: TOSHIBA dmi.bios.version: Version 6.40 dmi.board.asset.tag: 00 dmi.board.name: TECRA R950 dmi.board.vendor: TOSHIBA dmi.board.version: Version A0 dmi.chassis.asset.tag: 00 dmi.chassis.type: 10 dmi.chassis.vendor: TOSHIBA dmi.chassis.version: Version 1.0 dmi.modalias: dmi:bvnTOSHIBA:bvrVersion6.40:bd10/01/2012:svnTOSHIBA:pnTECRAR950:pvrPT530U-00T007:rvnTOSHIBA:rnTECRAR950:rvrVersionA0:cvnTOSHIBA:ct10:cvrVersion1.0: dmi.product.name: TECRA R950 dmi.product.version: PT530U-00T007 dmi.sys.vendor: TOSHIBA hciconfig: hci0:Type: BR/EDR Bus: USB BD Address: C8:F7:33:2D:6B:6B ACL MTU: 310:10 SCO MTU: 64:8 UP RUNNING RX bytes:580 acl:0 sco:0 events:31 errors:0 TX bytes:368 acl:0 sco:0 commands:30 errors:0 mtime.conffile..etc.bluetooth.main.conf: 2018-05-24T08:46:03.060208 upstart.bluetooth.override: manual To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1228263/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1228263] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1228263/+attachment/5174174/+files/UdevDb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1228263 Title: Volume control doesn't work automatically when connecting Bluetooth device. Status in bluez package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: Incomplete Bug description: When I connect a Bluetooth device, sound is automatically forwarded to the device but volume controls still control the internal sound card device. I must open the sound settings and click on the Bluetooth output device to use volume controls. I wish that the volume controls would automatically control whatever output device is actually active. :) This bug has existed for many versions of Ubuntu now. --- ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 EcryptfsInUse: Yes InstallationDate: Installed on 2016-07-25 (746 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) InterestingModules: btusb bluetooth MachineType: TOSHIBA TECRA R950 Package: pulseaudio PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-130-generic root=UUID=c7679e9c-34aa-4c9b-8e58-05ec7b8e4f63 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-130.156-generic 4.4.134 Tags: xenial Uname: Linux 4.4.0-130-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip libvirtd lpadmin plugdev sambashare sudo vboxusers video _MarkForUpload: True dmi.bios.date: 10/01/2012 dmi.bios.vendor: TOSHIBA dmi.bios.version: Version 6.40 dmi.board.asset.tag: 00 dmi.board.name: TECRA R950 dmi.board.vendor: TOSHIBA dmi.board.version: Version A0 dmi.chassis.asset.tag: 00 dmi.chassis.type: 10 dmi.chassis.vendor: TOSHIBA dmi.chassis.version: Version 1.0 dmi.modalias: dmi:bvnTOSHIBA:bvrVersion6.40:bd10/01/2012:svnTOSHIBA:pnTECRAR950:pvrPT530U-00T007:rvnTOSHIBA:rnTECRAR950:rvrVersionA0:cvnTOSHIBA:ct10:cvrVersion1.0: dmi.product.name: TECRA R950 dmi.product.version: PT530U-00T007 dmi.sys.vendor: TOSHIBA hciconfig: hci0:Type: BR/EDR Bus: USB BD Address: C8:F7:33:2D:6B:6B ACL MTU: 310:10 SCO MTU: 64:8 UP RUNNING RX bytes:580 acl:0 sco:0 events:31 errors:0 TX bytes:368 acl:0 sco:0 commands:30 errors:0 mtime.conffile..etc.bluetooth.main.conf: 2018-05-24T08:46:03.060208 upstart.bluetooth.override: manual To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1228263/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1228263] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1228263/+attachment/5174171/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1228263 Title: Volume control doesn't work automatically when connecting Bluetooth device. Status in bluez package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: Incomplete Bug description: When I connect a Bluetooth device, sound is automatically forwarded to the device but volume controls still control the internal sound card device. I must open the sound settings and click on the Bluetooth output device to use volume controls. I wish that the volume controls would automatically control whatever output device is actually active. :) This bug has existed for many versions of Ubuntu now. --- ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 EcryptfsInUse: Yes InstallationDate: Installed on 2016-07-25 (746 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) InterestingModules: btusb bluetooth MachineType: TOSHIBA TECRA R950 Package: pulseaudio PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-130-generic root=UUID=c7679e9c-34aa-4c9b-8e58-05ec7b8e4f63 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-130.156-generic 4.4.134 Tags: xenial Uname: Linux 4.4.0-130-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip libvirtd lpadmin plugdev sambashare sudo vboxusers video _MarkForUpload: True dmi.bios.date: 10/01/2012 dmi.bios.vendor: TOSHIBA dmi.bios.version: Version 6.40 dmi.board.asset.tag: 00 dmi.board.name: TECRA R950 dmi.board.vendor: TOSHIBA dmi.board.version: Version A0 dmi.chassis.asset.tag: 00 dmi.chassis.type: 10 dmi.chassis.vendor: TOSHIBA dmi.chassis.version: Version 1.0 dmi.modalias: dmi:bvnTOSHIBA:bvrVersion6.40:bd10/01/2012:svnTOSHIBA:pnTECRAR950:pvrPT530U-00T007:rvnTOSHIBA:rnTECRAR950:rvrVersionA0:cvnTOSHIBA:ct10:cvrVersion1.0: dmi.product.name: TECRA R950 dmi.product.version: PT530U-00T007 dmi.sys.vendor: TOSHIBA hciconfig: hci0:Type: BR/EDR Bus: USB BD Address: C8:F7:33:2D:6B:6B ACL MTU: 310:10 SCO MTU: 64:8 UP RUNNING RX bytes:580 acl:0 sco:0 events:31 errors:0 TX bytes:368 acl:0 sco:0 commands:30 errors:0 mtime.conffile..etc.bluetooth.main.conf: 2018-05-24T08:46:03.060208 upstart.bluetooth.override: manual To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1228263/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1228263] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1228263/+attachment/5174168/+files/Lsusb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1228263 Title: Volume control doesn't work automatically when connecting Bluetooth device. Status in bluez package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: Incomplete Bug description: When I connect a Bluetooth device, sound is automatically forwarded to the device but volume controls still control the internal sound card device. I must open the sound settings and click on the Bluetooth output device to use volume controls. I wish that the volume controls would automatically control whatever output device is actually active. :) This bug has existed for many versions of Ubuntu now. --- ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 EcryptfsInUse: Yes InstallationDate: Installed on 2016-07-25 (746 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) InterestingModules: btusb bluetooth MachineType: TOSHIBA TECRA R950 Package: pulseaudio PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-130-generic root=UUID=c7679e9c-34aa-4c9b-8e58-05ec7b8e4f63 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-130.156-generic 4.4.134 Tags: xenial Uname: Linux 4.4.0-130-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip libvirtd lpadmin plugdev sambashare sudo vboxusers video _MarkForUpload: True dmi.bios.date: 10/01/2012 dmi.bios.vendor: TOSHIBA dmi.bios.version: Version 6.40 dmi.board.asset.tag: 00 dmi.board.name: TECRA R950 dmi.board.vendor: TOSHIBA dmi.board.version: Version A0 dmi.chassis.asset.tag: 00 dmi.chassis.type: 10 dmi.chassis.vendor: TOSHIBA dmi.chassis.version: Version 1.0 dmi.modalias: dmi:bvnTOSHIBA:bvrVersion6.40:bd10/01/2012:svnTOSHIBA:pnTECRAR950:pvrPT530U-00T007:rvnTOSHIBA:rnTECRAR950:rvrVersionA0:cvnTOSHIBA:ct10:cvrVersion1.0: dmi.product.name: TECRA R950 dmi.product.version: PT530U-00T007 dmi.sys.vendor: TOSHIBA hciconfig: hci0:Type: BR/EDR Bus: USB BD Address: C8:F7:33:2D:6B:6B ACL MTU: 310:10 SCO MTU: 64:8 UP RUNNING RX bytes:580 acl:0 sco:0 events:31 errors:0 TX bytes:368 acl:0 sco:0 commands:30 errors:0 mtime.conffile..etc.bluetooth.main.conf: 2018-05-24T08:46:03.060208 upstart.bluetooth.override: manual To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1228263/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1228263] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1228263/+attachment/5174169/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1228263 Title: Volume control doesn't work automatically when connecting Bluetooth device. Status in bluez package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: Incomplete Bug description: When I connect a Bluetooth device, sound is automatically forwarded to the device but volume controls still control the internal sound card device. I must open the sound settings and click on the Bluetooth output device to use volume controls. I wish that the volume controls would automatically control whatever output device is actually active. :) This bug has existed for many versions of Ubuntu now. --- ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 EcryptfsInUse: Yes InstallationDate: Installed on 2016-07-25 (746 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) InterestingModules: btusb bluetooth MachineType: TOSHIBA TECRA R950 Package: pulseaudio PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-130-generic root=UUID=c7679e9c-34aa-4c9b-8e58-05ec7b8e4f63 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-130.156-generic 4.4.134 Tags: xenial Uname: Linux 4.4.0-130-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip libvirtd lpadmin plugdev sambashare sudo vboxusers video _MarkForUpload: True dmi.bios.date: 10/01/2012 dmi.bios.vendor: TOSHIBA dmi.bios.version: Version 6.40 dmi.board.asset.tag: 00 dmi.board.name: TECRA R950 dmi.board.vendor: TOSHIBA dmi.board.version: Version A0 dmi.chassis.asset.tag: 00 dmi.chassis.type: 10 dmi.chassis.vendor: TOSHIBA dmi.chassis.version: Version 1.0 dmi.modalias: dmi:bvnTOSHIBA:bvrVersion6.40:bd10/01/2012:svnTOSHIBA:pnTECRAR950:pvrPT530U-00T007:rvnTOSHIBA:rnTECRAR950:rvrVersionA0:cvnTOSHIBA:ct10:cvrVersion1.0: dmi.product.name: TECRA R950 dmi.product.version: PT530U-00T007 dmi.sys.vendor: TOSHIBA hciconfig: hci0:Type: BR/EDR Bus: USB BD Address: C8:F7:33:2D:6B:6B ACL MTU: 310:10 SCO MTU: 64:8 UP RUNNING RX bytes:580 acl:0 sco:0 events:31 errors:0 TX bytes:368 acl:0 sco:0 commands:30 errors:0 mtime.conffile..etc.bluetooth.main.conf: 2018-05-24T08:46:03.060208 upstart.bluetooth.override: manual To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1228263/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1228263] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1228263/+attachment/5174167/+files/Lspci.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1228263 Title: Volume control doesn't work automatically when connecting Bluetooth device. Status in bluez package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: Incomplete Bug description: When I connect a Bluetooth device, sound is automatically forwarded to the device but volume controls still control the internal sound card device. I must open the sound settings and click on the Bluetooth output device to use volume controls. I wish that the volume controls would automatically control whatever output device is actually active. :) This bug has existed for many versions of Ubuntu now. --- ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 EcryptfsInUse: Yes InstallationDate: Installed on 2016-07-25 (746 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) InterestingModules: btusb bluetooth MachineType: TOSHIBA TECRA R950 Package: pulseaudio PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-130-generic root=UUID=c7679e9c-34aa-4c9b-8e58-05ec7b8e4f63 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-130.156-generic 4.4.134 Tags: xenial Uname: Linux 4.4.0-130-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip libvirtd lpadmin plugdev sambashare sudo vboxusers video _MarkForUpload: True dmi.bios.date: 10/01/2012 dmi.bios.vendor: TOSHIBA dmi.bios.version: Version 6.40 dmi.board.asset.tag: 00 dmi.board.name: TECRA R950 dmi.board.vendor: TOSHIBA dmi.board.version: Version A0 dmi.chassis.asset.tag: 00 dmi.chassis.type: 10 dmi.chassis.vendor: TOSHIBA dmi.chassis.version: Version 1.0 dmi.modalias: dmi:bvnTOSHIBA:bvrVersion6.40:bd10/01/2012:svnTOSHIBA:pnTECRAR950:pvrPT530U-00T007:rvnTOSHIBA:rnTECRAR950:rvrVersionA0:cvnTOSHIBA:ct10:cvrVersion1.0: dmi.product.name: TECRA R950 dmi.product.version: PT530U-00T007 dmi.sys.vendor: TOSHIBA hciconfig: hci0:Type: BR/EDR Bus: USB BD Address: C8:F7:33:2D:6B:6B ACL MTU: 310:10 SCO MTU: 64:8 UP RUNNING RX bytes:580 acl:0 sco:0 events:31 errors:0 TX bytes:368 acl:0 sco:0 commands:30 errors:0 mtime.conffile..etc.bluetooth.main.conf: 2018-05-24T08:46:03.060208 upstart.bluetooth.override: manual To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1228263/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1228263] Dependencies.txt
apport information ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1228263/+attachment/5174166/+files/Dependencies.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1228263 Title: Volume control doesn't work automatically when connecting Bluetooth device. Status in bluez package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: Incomplete Bug description: When I connect a Bluetooth device, sound is automatically forwarded to the device but volume controls still control the internal sound card device. I must open the sound settings and click on the Bluetooth output device to use volume controls. I wish that the volume controls would automatically control whatever output device is actually active. :) This bug has existed for many versions of Ubuntu now. --- ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 EcryptfsInUse: Yes InstallationDate: Installed on 2016-07-25 (746 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) InterestingModules: btusb bluetooth MachineType: TOSHIBA TECRA R950 Package: pulseaudio PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-130-generic root=UUID=c7679e9c-34aa-4c9b-8e58-05ec7b8e4f63 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-130.156-generic 4.4.134 Tags: xenial Uname: Linux 4.4.0-130-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip libvirtd lpadmin plugdev sambashare sudo vboxusers video _MarkForUpload: True dmi.bios.date: 10/01/2012 dmi.bios.vendor: TOSHIBA dmi.bios.version: Version 6.40 dmi.board.asset.tag: 00 dmi.board.name: TECRA R950 dmi.board.vendor: TOSHIBA dmi.board.version: Version A0 dmi.chassis.asset.tag: 00 dmi.chassis.type: 10 dmi.chassis.vendor: TOSHIBA dmi.chassis.version: Version 1.0 dmi.modalias: dmi:bvnTOSHIBA:bvrVersion6.40:bd10/01/2012:svnTOSHIBA:pnTECRAR950:pvrPT530U-00T007:rvnTOSHIBA:rnTECRAR950:rvrVersionA0:cvnTOSHIBA:ct10:cvrVersion1.0: dmi.product.name: TECRA R950 dmi.product.version: PT530U-00T007 dmi.sys.vendor: TOSHIBA hciconfig: hci0:Type: BR/EDR Bus: USB BD Address: C8:F7:33:2D:6B:6B ACL MTU: 310:10 SCO MTU: 64:8 UP RUNNING RX bytes:580 acl:0 sco:0 events:31 errors:0 TX bytes:368 acl:0 sco:0 commands:30 errors:0 mtime.conffile..etc.bluetooth.main.conf: 2018-05-24T08:46:03.060208 upstart.bluetooth.override: manual To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1228263/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1228263] Re: Volume control doesn't work automatically when connecting Bluetooth device.
apport information ** Tags added: apport-collected xenial ** Description changed: When I connect a Bluetooth device, sound is automatically forwarded to the device but volume controls still control the internal sound card device. I must open the sound settings and click on the Bluetooth output device to use volume controls. I wish that the volume controls would automatically control whatever output device is actually active. :) This bug has existed for many versions of Ubuntu now. + --- + ApportVersion: 2.20.1-0ubuntu2.18 + Architecture: amd64 + CurrentDesktop: Unity + DistroRelease: Ubuntu 16.04 + EcryptfsInUse: Yes + InstallationDate: Installed on 2016-07-25 (746 days ago) + InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) + InterestingModules: btusb bluetooth + MachineType: TOSHIBA TECRA R950 + Package: pulseaudio + PackageArchitecture: amd64 + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-130-generic root=UUID=c7679e9c-34aa-4c9b-8e58-05ec7b8e4f63 ro quiet splash vt.handoff=7 + ProcVersionSignature: Ubuntu 4.4.0-130.156-generic 4.4.134 + Tags: xenial + Uname: Linux 4.4.0-130-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dialout dip libvirtd lpadmin plugdev sambashare sudo vboxusers video + _MarkForUpload: True + dmi.bios.date: 10/01/2012 + dmi.bios.vendor: TOSHIBA + dmi.bios.version: Version 6.40 + dmi.board.asset.tag: 00 + dmi.board.name: TECRA R950 + dmi.board.vendor: TOSHIBA + dmi.board.version: Version A0 + dmi.chassis.asset.tag: 00 + dmi.chassis.type: 10 + dmi.chassis.vendor: TOSHIBA + dmi.chassis.version: Version 1.0 + dmi.modalias: dmi:bvnTOSHIBA:bvrVersion6.40:bd10/01/2012:svnTOSHIBA:pnTECRAR950:pvrPT530U-00T007:rvnTOSHIBA:rnTECRAR950:rvrVersionA0:cvnTOSHIBA:ct10:cvrVersion1.0: + dmi.product.name: TECRA R950 + dmi.product.version: PT530U-00T007 + dmi.sys.vendor: TOSHIBA + hciconfig: + hci0:Type: BR/EDR Bus: USB + BD Address: C8:F7:33:2D:6B:6B ACL MTU: 310:10 SCO MTU: 64:8 + UP RUNNING + RX bytes:580 acl:0 sco:0 events:31 errors:0 + TX bytes:368 acl:0 sco:0 commands:30 errors:0 + mtime.conffile..etc.bluetooth.main.conf: 2018-05-24T08:46:03.060208 + upstart.bluetooth.override: manual ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1228263/+attachment/5174165/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1228263 Title: Volume control doesn't work automatically when connecting Bluetooth device. Status in bluez package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: Incomplete Bug description: When I connect a Bluetooth device, sound is automatically forwarded to the device but volume controls still control the internal sound card device. I must open the sound settings and click on the Bluetooth output device to use volume controls. I wish that the volume controls would automatically control whatever output device is actually active. :) This bug has existed for many versions of Ubuntu now. --- ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 EcryptfsInUse: Yes InstallationDate: Installed on 2016-07-25 (746 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) InterestingModules: btusb bluetooth MachineType: TOSHIBA TECRA R950 Package: pulseaudio PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-130-generic root=UUID=c7679e9c-34aa-4c9b-8e58-05ec7b8e4f63 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-130.156-generic 4.4.134 Tags: xenial Uname: Linux 4.4.0-130-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip libvirtd lpadmin plugdev sambashare sudo vboxusers video _MarkForUpload: True dmi.bios.date: 10/01/2012 dmi.bios.vendor: TOSHIBA dmi.bios.version: Version 6.40 dmi.board.asset.tag: 00 dmi.board.name: TECRA R950 dmi.board.vendor: TOSHIBA dmi.board.version: Version A0 dmi.chassis.asset.tag: 00 dmi.chassis.type: 10 dmi.chassis.vendor: TOSHIBA dmi.chassis.version: Version 1.0 dmi.modalias: dmi:bvnTOSHIBA:bvrVersion6.40:bd10/01/2012:svnTOSHIBA:pnTECRAR950:pvrPT530U-00T007:rvnTOSHIBA:rnTECRAR950:rvrVersionA0:cvnTOSHIBA:ct10:cvrVersion1.0: dmi.product.name: TECRA R950 dmi.product.version: PT530U-00T007 dmi.sys.vendor: TOSHIBA hciconfig: hci0:Type: BR/EDR Bus: USB BD Address: C8:F7:33:2D:6B:6B ACL MTU: 310:10 SCO MTU: 64:8 UP RUNNING RX bytes:580 acl:0 sco:0 events:31 errors:0 TX bytes:368 acl:0 sco:0 commands:30 errors:0 mtime.conffile..etc.bluetooth.main.conf: 2018-05-24T08:46:03.060208
[Kernel-packages] [Bug 1786625] Re: "find" command throws nonsense error message
It's funny that when creating the bug report there was a choice for the package
to report against:
- linux
- I don't know.
I chose "I don't know", but it has been assigned to linux allthesame.
Brilliant.
** Also affects: findutils (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: linux (Ubuntu)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1786625
Title:
"find" command throws nonsense error message
Status in findutils package in Ubuntu:
New
Bug description:
Steps to reproduce:
1. Run this command from a terminal:
$ find . -name *.txt
Expected result:
It should list all the files found in the current directory or any descendant
directory whose name ends in ".txt". It may or may not find matching files,
depending on whether there are or there aren't.
If there's something wrong in my command, then it should ALWAYS consistently
issue a sensible error message explaining what's wrong with my command, and
that should happen regardless of the contents of the current directory.
Observed results:
If there are no .txt files to be found, it behaves as expected (i.e., no
results, no error message).
If there are files ending in .txt, sometimes it behaves as expected, showing
the results.
If, however, there are files ending in ".txt" with dashes ("-") or spaces ("
") in the filename, AND there is more than one file that matches the criteria,
then it displays this completely nonsensical error message:
find: paths must precede expression: .txt
Usage: find [-H] [-L] [-P] [-Olevel] [-D
help|tree|search|stat|rates|opt|exec|time] [path...] [expression]
where "X.txt" is an actual filename of a matching file.
For example, this will reproduce the issue:
$ echo "lalala" > aaa.txt
$ echo "lololo" > foo-bar.txt
$ find . -name *.txt
find: paths must precede expression: foo-bar.txt
Usage: find [-H] [-L] [-P] [-Olevel] [-D
help|tree|search|stat|rates|opt|exec|time] [path...] [expression]
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-131-generic 4.4.0-131.157
ProcVersionSignature: Ubuntu 4.4.0-131.157-generic 4.4.134
Uname: Linux 4.4.0-131-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: teo2898 F pulseaudio
CurrentDesktop: Unity
Date: Sat Aug 11 17:30:54 2018
HibernationDevice: RESUME=UUID=ff7e702a-a05a-47fd-8c14-551e81f9e9e3
InstallationDate: Installed on 2013-10-11 (1764 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
MachineType: Acer Aspire V3-571G
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-131-generic.efi.signed
root=UUID=5830b30e-69e8-4bb4-8a2b-bc2b43c7414a ro quiet splash vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-4.4.0-131-generic N/A
linux-backports-modules-4.4.0-131-generic N/A
linux-firmware 1.157.20
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/15/2012
dmi.bios.vendor: Acer
dmi.bios.version: V2.07
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: VA50_HC_CR
dmi.board.vendor: Acer
dmi.board.version: Type2 - Board Version
dmi.chassis.type: 10
dmi.chassis.vendor: Acer
dmi.chassis.version: V2.07
dmi.modalias:
dmi:bvnAcer:bvrV2.07:bd10/15/2012:svnAcer:pnAspireV3-571G:pvrV2.07:rvnAcer:rnVA50_HC_CR:rvrType2-BoardVersion:cvnAcer:ct10:cvrV2.07:
dmi.product.name: Aspire V3-571G
dmi.product.version: V2.07
dmi.sys.vendor: Acer
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/findutils/+bug/1786625/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1786625] [NEW] "find" command throws nonsense error message
Public bug reported:
Steps to reproduce:
1. Run this command from a terminal:
$ find . -name *.txt
Expected result:
It should list all the files found in the current directory or any descendant
directory whose name ends in ".txt". It may or may not find matching files,
depending on whether there are or there aren't.
If there's something wrong in my command, then it should ALWAYS consistently
issue a sensible error message explaining what's wrong with my command, and
that should happen regardless of the contents of the current directory.
Observed results:
If there are no .txt files to be found, it behaves as expected (i.e., no
results, no error message).
If there are files ending in .txt, sometimes it behaves as expected, showing
the results.
If, however, there are files ending in ".txt" with dashes ("-") or spaces (" ")
in the filename, AND there is more than one file that matches the criteria,
then it displays this completely nonsensical error message:
find: paths must precede expression: .txt
Usage: find [-H] [-L] [-P] [-Olevel] [-D
help|tree|search|stat|rates|opt|exec|time] [path...] [expression]
where "X.txt" is an actual filename of a matching file.
For example, this will reproduce the issue:
$ echo "lalala" > aaa.txt
$ echo "lololo" > foo-bar.txt
$ find . -name *.txt
find: paths must precede expression: foo-bar.txt
Usage: find [-H] [-L] [-P] [-Olevel] [-D
help|tree|search|stat|rates|opt|exec|time] [path...] [expression]
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-131-generic 4.4.0-131.157
ProcVersionSignature: Ubuntu 4.4.0-131.157-generic 4.4.134
Uname: Linux 4.4.0-131-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: teo2898 F pulseaudio
CurrentDesktop: Unity
Date: Sat Aug 11 17:30:54 2018
HibernationDevice: RESUME=UUID=ff7e702a-a05a-47fd-8c14-551e81f9e9e3
InstallationDate: Installed on 2013-10-11 (1764 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
MachineType: Acer Aspire V3-571G
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-131-generic.efi.signed
root=UUID=5830b30e-69e8-4bb4-8a2b-bc2b43c7414a ro quiet splash vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-4.4.0-131-generic N/A
linux-backports-modules-4.4.0-131-generic N/A
linux-firmware 1.157.20
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/15/2012
dmi.bios.vendor: Acer
dmi.bios.version: V2.07
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: VA50_HC_CR
dmi.board.vendor: Acer
dmi.board.version: Type2 - Board Version
dmi.chassis.type: 10
dmi.chassis.vendor: Acer
dmi.chassis.version: V2.07
dmi.modalias:
dmi:bvnAcer:bvrV2.07:bd10/15/2012:svnAcer:pnAspireV3-571G:pvrV2.07:rvnAcer:rnVA50_HC_CR:rvrType2-BoardVersion:cvnAcer:ct10:cvrV2.07:
dmi.product.name: Aspire V3-571G
dmi.product.version: V2.07
dmi.sys.vendor: Acer
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug xenial
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1786625
Title:
"find" command throws nonsense error message
Status in linux package in Ubuntu:
New
Bug description:
Steps to reproduce:
1. Run this command from a terminal:
$ find . -name *.txt
Expected result:
It should list all the files found in the current directory or any descendant
directory whose name ends in ".txt". It may or may not find matching files,
depending on whether there are or there aren't.
If there's something wrong in my command, then it should ALWAYS consistently
issue a sensible error message explaining what's wrong with my command, and
that should happen regardless of the contents of the current directory.
Observed results:
If there are no .txt files to be found, it behaves as expected (i.e., no
results, no error message).
If there are files ending in .txt, sometimes it behaves as expected, showing
the results.
If, however, there are files ending in ".txt" with dashes ("-") or spaces ("
") in the filename, AND there is more than one file that matches the criteria,
then it displays this completely nonsensical error message:
find: paths must precede expression: .txt
Usage: find [-H] [-L] [-P] [-Olevel] [-D
help|tree|search|stat|rates|opt|exec|time] [path...] [expression]
where "X.txt" is an actual filename of a matching file.
For example, this will reproduce the issue:
$ echo "lalala" > aaa.txt
$ echo "lololo" > foo-bar.txt
$ find . -name *.txt
Re: [Kernel-packages] [Bug 1777338] Re: Linux 4.15.0-23 crashes during the boot process with a "Unable to handle kernel NULL pointer dereference" message
Thanks for preparing this kernel; I am downloading it now. What are the expected hashes of the files, so that I can verify the insecure downloads? On Tue, Aug 7, 2018 at 8:49 AM, Joseph Salisbury wrote: > I built a test kernel with commit 74899d92e3dc7671a8017b3146dcd4735f3b. > The test kernel can be downloaded from: > http://kernel.ubuntu.com/~jsalisbury/lp1777338 > > Can you test this kernel and see if it resolves this bug? > > If this kernel also fixes the bug, I'll submit an SRU request. > > > Note about installing test kernels: > • If the test kernel is prior to 4.15(Bionic) you need to install the > linux-image and linux-image-extra .deb packages. > • If the test kernel is 4.15(Bionic) or newer, you need to install the > linux-modules, linux-modules-extra and linux-image-unsigned .deb packages. > > Thanks in advance! > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1777338 > > Title: > Linux 4.15.0-23 crashes during the boot process with a "Unable to > handle kernel NULL pointer dereference" message > > Status in linux package in Ubuntu: > In Progress > Status in linux source package in Bionic: > In Progress > > Bug description: > I went to boot my computer today and it wouldn't boot. > > I get an "Unable to handle kernel NULL pointer dereference" message > during the boot process, and, a bit after that, a message from the > kernel watchdog about CPU #0 being stuck. Then the boot process stops > completely. > > I was able to boot the system by telling Grub to load 4.15.0-22, which > works perfectly fine, so there has been a regression. > > I am running Ubuntu as a Xen dom0, if that matters. I haven't tried > booting the offending kernel version without Xen. > > I'm not sure where, if anywhere, these messages go on disk, for > posting. > > ProblemType: Bug > DistroRelease: Ubuntu 18.04 > Package: linux-image-4.15.0-23-generic 4.15.0-23.25 > ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 > Uname: Linux 4.15.0-22-generic x86_64 > NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair > ApportVersion: 2.20.9-0ubuntu7.1 > Architecture: amd64 > CurrentDesktop: ubuntu:GNOME > Date: Sun Jun 17 10:12:58 2018 > InstallationDate: Installed on 2017-08-06 (314 days ago) > InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) > ProcEnviron: >TERM=xterm-256color >PATH=(custom, no user) >XDG_RUNTIME_DIR= >LANG=en_US.UTF-8 >SHELL=/bin/bash > SourcePackage: linux-signed > UpgradeStatus: Upgraded to bionic on 2018-05-29 (19 days ago) > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1777338/+subscriptions -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1777338 Title: Linux 4.15.0-23 crashes during the boot process with a "Unable to handle kernel NULL pointer dereference" message Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: In Progress Bug description: I went to boot my computer today and it wouldn't boot. I get an "Unable to handle kernel NULL pointer dereference" message during the boot process, and, a bit after that, a message from the kernel watchdog about CPU #0 being stuck. Then the boot process stops completely. I was able to boot the system by telling Grub to load 4.15.0-22, which works perfectly fine, so there has been a regression. I am running Ubuntu as a Xen dom0, if that matters. I haven't tried booting the offending kernel version without Xen. I'm not sure where, if anywhere, these messages go on disk, for posting. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-23-generic 4.15.0-23.25 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Jun 17 10:12:58 2018 InstallationDate: Installed on 2017-08-06 (314 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed UpgradeStatus: Upgraded to bionic on 2018-05-29 (19 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1777338/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1784998] Re: After a while touchpad doesn't work
fokedFromTheLife: 1) >"so when i install ubuntu the touchpad don't work i go to >http://pclub.in/2017/01/06/Linux-on-Asus-ROG.html and that' worked" To clarify, you are stating that by default, the touchpad doesn't work at all. However, after using the non-default kernel parameters, and installing the NVIDIA proprietary drivers, the touchpad then begins to work? 2) >"after an update my touchpad stopped again" Which update precisely, and what date was the update applied? 3) To confirm this is resolved in Ubuntu, could you please test http://cdimage.ubuntu.com/daily-live/current/ and advise to the results? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1784998 Title: After a while touchpad doesn't work Status in linux package in Ubuntu: Incomplete Status in xorg-server package in Ubuntu: New Bug description: after a while my touch pad don't work but mouse with usb work in my laptop my laptop : Asus GL553V ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Aug 2 10:23:53 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Device [8086:591b] (rev 04) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:15e0] Subsystem: ASUSTeK Computer Inc. GP107M [GeForce GTX 1050 Mobile] [1043:15e0] InstallationDate: Installed on 2018-04-29 (94 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2a Intel Corp. Bus 001 Device 002: ID 0bda:57f5 Realtek Semiconductor Corp. Bus 001 Device 004: ID 0b05:1854 ASUSTek Computer, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. GL553VD ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-29-generic root=UUID=48228a8f-bbca-4be4-a07a-96a383809e68 ro quiet splash nouveau.modeset=0 tpm_tis.interrupts=0 acpi_osi=Linux i915.preliminary_hw_support=1 idle=nomwait vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/02/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GL553VD.306 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: GL553VD 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.:bvrGL553VD.306:bd01/02/2018:svnASUSTeKCOMPUTERINC.:pnGL553VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL553VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: GL dmi.product.name: GL553VD dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 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/1784998/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1786619] 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 Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1786619 Title: Cannot able to upgrade from 16.04 to 18.04 Status in linux package in Ubuntu: Confirmed Bug description: package linux-headers-4.4.0-131 4.4.0-131.157 failed to install/upgrade: package linux-headers-4.4.0-131 is not ready for configuration cannot configure (current status 'half-installed') Processing triggers for libc-bin (2.23-0ubuntu10) ... dpkg: error processing package linux-headers-4.4.0-131 (--configure): package linux-headers-4.4.0-131 is not ready for configuration cannot configure (current status 'half-installed') Errors were encountered while processing: linux-headers-4.4.0-131 E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-headers-4.4.0-131 4.4.0-131.157 ProcVersionSignature: Ubuntu 4.4.0-131.157-generic 4.4.134 Uname: Linux 4.4.0-131-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.1-0ubuntu2.18 AptOrdering: linux-headers-4.4.0-131: Configure NULL: ConfigurePending Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: argha 2096 F pulseaudio /dev/snd/controlC0: argha 2096 F pulseaudio Date: Sat Aug 11 19:54:47 2018 DpkgTerminalLog: dpkg: error processing package linux-headers-4.4.0-131 (--configure): package linux-headers-4.4.0-131 is not ready for configuration cannot configure (current status 'half-installed') ErrorMessage: package linux-headers-4.4.0-131 is not ready for configuration cannot configure (current status 'half-installed') HibernationDevice: RESUME=UUID=cc8a-0f65-4d75-bf10-dd906f85e00b InstallationDate: Installed on 2017-08-12 (363 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Lsusb: Bus 001 Device 003: ID 04f2:b40e Chicony Electronics Co., Ltd HP Truevision HD camera Bus 001 Device 002: ID 8087:8000 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Hewlett-Packard HP 15 Notebook PC PackageArchitecture: all ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-131-generic.efi.signed root=UUID=e95dbb4f-5fb3-4ee3-8ad1-155b711b1a4c ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc N/A SourcePackage: linux Title: package linux-headers-4.4.0-131 4.4.0-131.157 failed to install/upgrade: package linux-headers-4.4.0-131 is not ready for configuration cannot configure (current status 'half-installed') UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/21/2014 dmi.bios.vendor: Insyde dmi.bios.version: F.18 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 2212 dmi.board.vendor: Hewlett-Packard dmi.board.version: 86.28 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.18:bd05/21/2014:svnHewlett-Packard:pnHP15NotebookPC:pvr0991100600087:rvnHewlett-Packard:rn2212:rvr86.28:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.name: HP 15 Notebook PC dmi.product.version: 0991100600087 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786619/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1786619] [NEW] Cannot able to upgrade from 16.04 to 18.04
Public bug reported: package linux-headers-4.4.0-131 4.4.0-131.157 failed to install/upgrade: package linux-headers-4.4.0-131 is not ready for configuration cannot configure (current status 'half-installed') Processing triggers for libc-bin (2.23-0ubuntu10) ... dpkg: error processing package linux-headers-4.4.0-131 (--configure): package linux-headers-4.4.0-131 is not ready for configuration cannot configure (current status 'half-installed') Errors were encountered while processing: linux-headers-4.4.0-131 E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-headers-4.4.0-131 4.4.0-131.157 ProcVersionSignature: Ubuntu 4.4.0-131.157-generic 4.4.134 Uname: Linux 4.4.0-131-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.1-0ubuntu2.18 AptOrdering: linux-headers-4.4.0-131: Configure NULL: ConfigurePending Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: argha 2096 F pulseaudio /dev/snd/controlC0: argha 2096 F pulseaudio Date: Sat Aug 11 19:54:47 2018 DpkgTerminalLog: dpkg: error processing package linux-headers-4.4.0-131 (--configure): package linux-headers-4.4.0-131 is not ready for configuration cannot configure (current status 'half-installed') ErrorMessage: package linux-headers-4.4.0-131 is not ready for configuration cannot configure (current status 'half-installed') HibernationDevice: RESUME=UUID=cc8a-0f65-4d75-bf10-dd906f85e00b InstallationDate: Installed on 2017-08-12 (363 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Lsusb: Bus 001 Device 003: ID 04f2:b40e Chicony Electronics Co., Ltd HP Truevision HD camera Bus 001 Device 002: ID 8087:8000 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Hewlett-Packard HP 15 Notebook PC PackageArchitecture: all ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-131-generic.efi.signed root=UUID=e95dbb4f-5fb3-4ee3-8ad1-155b711b1a4c ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc N/A SourcePackage: linux Title: package linux-headers-4.4.0-131 4.4.0-131.157 failed to install/upgrade: package linux-headers-4.4.0-131 is not ready for configuration cannot configure (current status 'half-installed') UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/21/2014 dmi.bios.vendor: Insyde dmi.bios.version: F.18 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 2212 dmi.board.vendor: Hewlett-Packard dmi.board.version: 86.28 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.18:bd05/21/2014:svnHewlett-Packard:pnHP15NotebookPC:pvr0991100600087:rvnHewlett-Packard:rn2212:rvr86.28:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.name: HP 15 Notebook PC dmi.product.version: 0991100600087 dmi.sys.vendor: Hewlett-Packard ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-package xenial -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1786619 Title: Cannot able to upgrade from 16.04 to 18.04 Status in linux package in Ubuntu: Confirmed Bug description: package linux-headers-4.4.0-131 4.4.0-131.157 failed to install/upgrade: package linux-headers-4.4.0-131 is not ready for configuration cannot configure (current status 'half-installed') Processing triggers for libc-bin (2.23-0ubuntu10) ... dpkg: error processing package linux-headers-4.4.0-131 (--configure): package linux-headers-4.4.0-131 is not ready for configuration cannot configure (current status 'half-installed') Errors were encountered while processing: linux-headers-4.4.0-131 E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-headers-4.4.0-131 4.4.0-131.157 ProcVersionSignature: Ubuntu 4.4.0-131.157-generic 4.4.134 Uname: Linux 4.4.0-131-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.1-0ubuntu2.18 AptOrdering: linux-headers-4.4.0-131: Configure NULL: ConfigurePending Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: argha 2096 F pulseaudio /dev/snd/controlC0: argha 2096 F pulseaudio Date: Sat Aug 11 19:54:47 2018 DpkgTerminalLog: dpkg: error processing package linux-headers-4.4.0-131 (--configure):
[Kernel-packages] [Bug 1784998] Re: After a while touchpad doesn't work
so when i install ubuntu the touchpad don't work i go to http://pclub.in/2017/01/06/Linux-on-Asus-ROG.html and that' worked after an update my touchpad stopped again after deleting that kernel parameters that's not okay thanks -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1784998 Title: After a while touchpad doesn't work Status in linux package in Ubuntu: Incomplete Status in xorg-server package in Ubuntu: New Bug description: after a while my touch pad don't work but mouse with usb work in my laptop my laptop : Asus GL553V ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Aug 2 10:23:53 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Device [8086:591b] (rev 04) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:15e0] Subsystem: ASUSTeK Computer Inc. GP107M [GeForce GTX 1050 Mobile] [1043:15e0] InstallationDate: Installed on 2018-04-29 (94 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2a Intel Corp. Bus 001 Device 002: ID 0bda:57f5 Realtek Semiconductor Corp. Bus 001 Device 004: ID 0b05:1854 ASUSTek Computer, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. GL553VD ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-29-generic root=UUID=48228a8f-bbca-4be4-a07a-96a383809e68 ro quiet splash nouveau.modeset=0 tpm_tis.interrupts=0 acpi_osi=Linux i915.preliminary_hw_support=1 idle=nomwait vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/02/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GL553VD.306 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: GL553VD 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.:bvrGL553VD.306:bd01/02/2018:svnASUSTeKCOMPUTERINC.:pnGL553VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL553VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: GL dmi.product.name: GL553VD dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 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/1784998/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1780806] Re: Kernel 4.15.0 fails to boot with linux-modules-extra
The same issue with notebook Sony Vaio SVS151190X. It works with kernel 4.13 and doesn't work with kernel 4.15 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1780806 Title: Kernel 4.15.0 fails to boot with linux-modules-extra Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: Incomplete Bug description: I upgraded my laptop (Sony VAIO SVS1511C5E, Intel Core i7-3612QM, NVIDIA GK107M / GeForce GT 640M LE, original hard disk changed to a Crucial SSD) yesterday from Ubuntu 17.10. to Ubuntu 18.04. The upgrade process went smoothly without issues. After upgrade, I cannot boot the new kernel version 4.15.0-23 in normal mode. The boot process hangs immediately after displaying "Loading initial ramdisk". In case I choose "Recovery mode", the system does boot successfully with the same kernel. I also tried installing kernels 4.15.0-22 and 4.15.0-24, which both behave identically. The problem seems to be related to the linux-modules-extra package. If the package is not installed, the system boots also in the normal mode. However, the display is not correctly recognized, it shows up as "Unknown display" with 1024x768 resolution. That also happens if I choose "Recovery mode" and "Resume boot". The previous kernel 4.13.0-46 (with linux-modules-extra installed) works without problems and the display is recognized correctly. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: arto 2916 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=2ef70a11-4a51-4152-a156-14c706505b71 InstallationDate: Installed on 2017-10-18 (263 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) MachineType: Sony Corporation SVS1511C5E Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic root=UUID=791d0e17-7a4d-47c8-8f69-708bebb1e658 ro recovery nomodeset ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-23-generic N/A linux-backports-modules-4.15.0-23-generic N/A linux-firmware 1.173.1 Tags: bionic Uname: Linux 4.15.0-23-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-07-08 (0 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare scanner sudo _MarkForUpload: True dmi.bios.date: 05/17/2012 dmi.bios.vendor: Insyde Corp. dmi.bios.version: R0142C5 dmi.board.asset.tag: N/A dmi.board.name: VAIO dmi.board.vendor: Sony Corporation dmi.board.version: N/A dmi.chassis.asset.tag: N/A dmi.chassis.type: 10 dmi.chassis.vendor: Sony Corporation dmi.chassis.version: N/A dmi.modalias: dmi:bvnInsydeCorp.:bvrR0142C5:bd05/17/2012:svnSonyCorporation:pnSVS1511C5E:pvrC60AVZAU:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A: dmi.product.family: VAIO dmi.product.name: SVS1511C5E dmi.product.version: C60AVZAU dmi.sys.vendor: Sony Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1780806/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
Re: [Kernel-packages] [Bug 1753510] Re: Cannot boot/install AMD Ryzen 2400G
if it is of interest, I could buy a USB debugging cable and give you access... saw this: https://www.kernel.org/doc/html/v4.17/driver-api/usb/usb3-debug-port.html but I would have to order the cable. Recommendations welcome. Do you think it is possible to have the other computer be a raspberry pi (which is only USB-2)? If so, it would be easy to just connect and leave it that way for hours. If both ends need to be usb-3, then I need a second USB-3 host and it's a bit more cumbersome. On Sat, Aug 11, 2018 at 8:24 AM, Peter Silva wrote: > during dpkg -i : > > > (Reading database ... 506366 files and directories currently installed.) > Preparing to unpack linux-image-4.18.0-rc1+_4.18.0-rc1+-1_amd64.deb ... > Unpacking linux-image-4.18.0-rc1+ (4.18.0-rc1+-1) ... > Setting up linux-image-4.18.0-rc1+ (4.18.0-rc1+-1) ... > Error! Your kernel headers for kernel 4.18.0-rc1+ cannot be found. > Please install the linux-headers-4.18.0-rc1+ package, > or use the --kernelsourcedir option to tell DKMS where it's located > > ... tried it anyways... > > it behaves similarly to the others. The first time I booted it > eventually dropped into initramfs) prompt, but would not accept keyboard > input. subsequent boot was and endless loop of register dumps. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1753510 > > Title: > Cannot boot/install AMD Ryzen 2400G > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/ > 1753510/+subscriptions > -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1753510 Title: Cannot boot/install AMD Ryzen 2400G Status in linux package in Ubuntu: Confirmed Bug description: Did a motherboard swap on a trusty old computer that ran ubuntu for 10 years or so. Now it only runs windows (same hardware fresh installs windows with no issue). brand new ryzen 2nd gen with graphics. I know about graphics drivers issues, wasn't expecting that to be dealt with. Just trying to use it as a cpu. So I put in an older (RADEON HD 7850 pitcairn) video card to get some functionality. Without the video card, it boots, but the display is unusable. I can ssh in and see that it works fine as a server, but cannot use terminal or graphical display. With the video card, Put daily ubuntu Bionic image, and "Try Ubuntu", and it goes into an infinite loop. photo attached. I tried 16.04.4 and I think it just went into a blank screen. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1753510/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1786192] Re: splash time out on shutdown bios virused
Zoltán Szabó, please answer all of the following: 1) Regarding the kernel trace, is this something that started to happen after an update? if so, which and when precisely? 2) To see if this is already resolved in Ubuntu, could you please test for this via http://cdimage.ubuntu.com/daily-live/current/ and advise to the results? ** Tags added: bios-outdated-1.35 ** Changed in: linux (Ubuntu) Importance: Undecided => Low ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete ** Summary changed: - splash time out on shutdown bios virused + kernel trace -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1786192 Title: kernel trace Status in linux package in Ubuntu: Incomplete Bug description: [ 157.511000] [ cut here ] [ 157.511004] vblank wait timed out on crtc 1 [ 157.511092] WARNING: CPU: 0 PID: 1149 at /build/linux-WHbi0x/linux-4.15.0/drivers/gpu/drm/drm_vblank.c:1073 drm_wait_one_vblank+0x1a1/0x1b0 [drm] [ 157.511094] Modules linked in: option usb_wwan usbserial huawei_cdc_ncm cdc_wdm cdc_ncm usbnet mii ip6t_REJECT nf_reject_ipv6 nf_log_ipv6 snd_hda_codec_hdmi xt_hl snd_hda_codec_realtek ip6t_rt snd_hda_codec_generic snd_hda_intel nf_conntrack_ipv6 nf_defrag_ipv6 snd_hda_codec ipt_REJECT snd_hda_core nf_reject_ipv4 snd_hwdep nf_log_ipv4 snd_pcm nf_log_common xt_LOG snd_seq_midi snd_seq_midi_event snd_rawmidi arc4 pcmcia coretemp xt_limit iwl4965 joydev xt_tcpudp iwlegacy snd_seq acer_wmi snd_seq_device input_leds serio_raw wmi_bmof yenta_socket sparse_keymap pcmcia_rsrc mac80211 tifm_7xx1 xt_addrtype snd_timer pcmcia_core tifm_core snd lpc_ich cfg80211 soundcore shpchp nsc_ircc(CE) irda(CE) nf_conntrack_ipv4 nf_defrag_ipv4 mac_hid xt_conntrack ip6table_filter sch_fq_codel ip6_tables nf_conntrack_netbios_ns [ 157.511145] nf_conntrack_broadcast nf_nat_ftp nf_nat nf_conntrack_ftp nf_conntrack libcrc32c iptable_filter parport_pc ppdev lp parport ip_tables x_tables autofs4 i915 i2c_algo_bit drm_kms_helper syscopyarea sysfillrect sysimgblt firewire_ohci fb_sys_fops tg3 ahci sdhci_pci firewire_core psmouse drm libahci sdhci ptp pata_acpi crc_itu_t pps_core wmi video uas usb_storage [ 157.511176] CPU: 0 PID: 1149 Comm: gnome-shell Tainted: GWC E 4.15.0-30-generic #32-Ubuntu [ 157.511181] Hardware name: AcerTravelMate 5320 /Columbia , BIOS V1.22 10/22/2007 [ 157.511200] EIP: drm_wait_one_vblank+0x1a1/0x1b0 [drm] [ 157.511202] EFLAGS: 00010292 CPU: 0 [ 157.511204] EAX: 001f EBX: f4e2c000 ECX: f63e9630 EDX: 0007 [ 157.511205] ESI: 0001 EDI: EBP: f0713b74 ESP: f0713b3c [ 157.511207] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068 [ 157.511209] CR0: 80050033 CR2: b5a91a90 CR3: 30655f00 CR4: 06f0 [ 157.511211] Call Trace: [ 157.511222] ? wait_woken+0x70/0x70 [ 157.511277] intel_get_load_detect_pipe+0x5eb/0x650 [i915] [ 157.511318] intel_tv_detect+0x113/0x4b0 [i915] [ 157.511360] ? intel_tv_get_modes+0x1f0/0x1f0 [i915] [ 157.511376] drm_helper_probe_detect+0x45/0x80 [drm_kms_helper] [ 157.511386] drm_helper_probe_single_connector_modes+0xbc/0x640 [drm_kms_helper] [ 157.511397] ? drm_helper_probe_detect+0x80/0x80 [drm_kms_helper] [ 157.511417] drm_mode_getconnector+0x11e/0x2c0 [drm] [ 157.511438] ? drm_mode_connector_property_set_ioctl+0x60/0x60 [drm] [ 157.511454] drm_ioctl_kernel+0x56/0xb0 [drm] [ 157.511471] drm_ioctl+0x2c4/0x370 [drm] [ 157.511490] ? drm_mode_connector_property_set_ioctl+0x60/0x60 [drm] [ 157.511497] ? kmap_atomic_prot+0xe0/0x100 [ 157.511500] ? __kunmap_atomic+0x73/0x90 [ 157.511505] ? handle_mm_fault+0xc35/0xe80 [ 157.511522] ? drm_version+0x80/0x80 [drm] [ 157.511527] do_vfs_ioctl+0x93/0x6b0 [ 157.511532] SyS_ioctl+0x58/0x70 [ 157.511536] do_fast_syscall_32+0x7f/0x1e0 [ 157.511542] entry_SYSENTER_32+0x4e/0x7c [ 157.511545] EIP: 0xb7f60d09 [ 157.511546] EFLAGS: 00200292 CPU: 0 [ 157.511548] EAX: ffda EBX: 000b ECX: c05064a7 EDX: bfe159a8 [ 157.511550] ESI: 0001 EDI: c05064a7 EBP: 000b ESP: bfe15928 [ 157.511552] DS: 007b ES: 007b FS: GS: 0033 SS: 007b [ 157.511553] Code: 00 00 00 e9 e4 fe ff ff e8 bd 48 a2 cc 8b 45 d0 8d 55 dc e8 f2 65 a6 cc 85 ff 0f 85 ee fe ff ff 56 68 48 a2 66 f8 e8 2f 46 a2 cc <0f> 0b 58 5a e9 da fe ff ff 8d b6 00 00 00 00 66 66 66 66 90 55 [ 157.511597] ---[ end trace ecf18bbc5fa1e893 ]--- ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: plymouth 0.9.3-1ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-30.32-generic 4.15.18 Uname: Linux 4.15.0-30-generic i686 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: i386 CurrentDesktop: Unity:Unity7:ubuntu Date: Thu Aug 9 10:31:18 2018 DefaultPlymouth: Error: command ['readlink',
[Kernel-packages] [Bug 1655280] Comment bridged from LTC Bugzilla
--- Comment From hbath...@in.ibm.com 2018-08-11 08:48 EDT--- After upgrading to kdump-tools_1.6.4-1~16.04.0cascardo2_ppc64el.deb package, dump capture succeeds without any complaints: The udev rules trigger kdump-tools service reload as can be seen below: -- root@ubuntu:~# dpkg -l | grep kdump-tools ii kdump-tools 1:1.6.4-1~16.04.0cascardo2 ppc64el scripts and tools for automating kdump (Linux crash dumps) root@ubuntu:~# root@ubuntu:~# root@ubuntu:~# root@ubuntu:~# systemctl status kdump-tools.service -l ? kdump-tools.service - Kernel crash dump capture service Loaded: loaded (/lib/systemd/system/kdump-tools.service; enabled; vendor pres Active: active (exited) since Sat 2018-08-11 08:33:27 EDT; 2min 8s ago Process: 25166 ExecStop=/etc/init.d/kdump-tools stop (code=exited, status=0/SU Process: 25200 ExecStart=/etc/init.d/kdump-tools start (code=exited, status=0/ Main PID: 25200 (code=exited, status=0/SUCCESS) Aug 11 08:33:26 ubuntu systemd[1]: Starting Kernel crash dump capture service... Aug 11 08:33:26 ubuntu kdump-tools[25200]: Starting kdump-tools: * Creating sym Aug 11 08:33:26 ubuntu kdump-tools[25200]: * Creating symlink /var/lib/kdump/in Aug 11 08:33:26 ubuntu kdump-tools[25200]: Modified cmdline:BOOT_IMAGE=/boot/vml Aug 11 08:33:26 ubuntu kdump-tools[25200]: * loaded kdump kernel Aug 11 08:33:26 ubuntu kdump-tools[25248]: /sbin/kexec -p --command-line="BOOT_I Aug 11 08:33:27 ubuntu kdump-tools[25249]: loaded kdump kernel Aug 11 08:33:27 ubuntu systemd[1]: Started Kernel crash dump capture service. root@ubuntu:~# root@ubuntu:~# root@ubuntu:~# root@ubuntu:~# root@ubuntu:~# drmgr -c mem -r -q 1 Validating Memory DLPAR capability...yes. [1459216.723209] pseries-hotplug-mem: Attempting to hot-remove 1 LMB(s) [1459216.749014] Offlined Pages 4096 [1459193.925176] kdump-tools[25419]: Stopping kdump-tools: * unloaded kdump kernel [1459193.985143] kdump-tools[25453]: Starting kdump-tools: * Creating symlink /var/lib/kdump/vmlinuz [1459193.986120] kdump-tools[25453]: * Creating symlink /var/lib/kdump/initrd.img [1459194.024961] kdump-tools[25453]: Modified cmdline:BOOT_IMAGE=/boot/vmlinux-4.15.0-24-generic root=UUID=1aa9458c-3974-4cb4-9ab3-9ee03c0f4e5e ro xmon=on nr_cpus=1 systemd.unit=kdump-tools.service irqpoll noirqdistrib nousb elfcorehdr=158144K [1459217.005820] pseries-hotplug-mem: Memory at 4000 was hot-removed DR_TOTAL_RESOURCES=1 root@ubuntu:~# [1459194.297073] kdump-tools[25453]: * loaded kdump kernel root@ubuntu:~# root@ubuntu:~# root@ubuntu:~# root@ubuntu:~# systemctl status kdump-tools.service -l ? kdump-tools.service - Kernel crash dump capture service Loaded: loaded (/lib/systemd/system/kdump-tools.service; enabled; vendor pres Active: active (exited) since Sat 2018-08-11 08:35:47 EDT; 12s ago Process: 25419 ExecStop=/etc/init.d/kdump-tools stop (code=exited, status=0/SU Process: 25453 ExecStart=/etc/init.d/kdump-tools start (code=exited, status=0/ Main PID: 25453 (code=exited, status=0/SUCCESS) Aug 11 08:35:47 ubuntu systemd[1]: Starting Kernel crash dump capture service... Aug 11 08:35:47 ubuntu kdump-tools[25453]: Starting kdump-tools: * Creating sym Aug 11 08:35:47 ubuntu kdump-tools[25453]: * Creating symlink /var/lib/kdump/in Aug 11 08:35:47 ubuntu kdump-tools[25453]: Modified cmdline:BOOT_IMAGE=/boot/vml Aug 11 08:35:47 ubuntu kdump-tools[25453]: * loaded kdump kernel Aug 11 08:35:47 ubuntu kdump-tools[25505]: /sbin/kexec -p --command-line="BOOT_I Aug 11 08:35:47 ubuntu kdump-tools[25506]: loaded kdump kernel Aug 11 08:35:47 ubuntu systemd[1]: Started Kernel crash dump capture service. root@ubuntu:~# -- and dump captured successfully after memory dlpar operation: -- [ 139.944700] kdump-tools[1278]: Starting kdump-tools: * running makedumpfile -c -d 31 /proc/vmcore /var/crash/201808110838/dump-incomplete Copying data : [100.0 %] - eta: 0s [ 147.858420] kdump-tools[1278]: The kernel version is not supported. [ 147.858718] kdump-tools[1278]: The makedumpfile operation may be incomplete. [ 147.859002] kdump-tools[1278]: The dumpfile is saved to /var/crash/201808110838/dump-incomplete. [ 147.859260] kdump-tools[1278]: makedumpfile Completed. [ 147.899799] kdump-tools[1278]: * kdump-tools: saved vmcore in /var/crash/201808110838 [ 147.998442] kdump-tools[1278]: * running makedumpfile --dump-dmesg /proc/vmcore /var/crash/201808110838/dmesg.201808110838 [ 148.008063] kdump-tools[1278]: The kernel version is not supported. [ 148.008436] kdump-tools[1278]: The makedumpfile operation may be incomplete. [ 148.008672] kdump-tools[1278]: The dmesg log is saved to /var/crash/201808110838/dmesg.201808110838. [ 148.008913] kdump-tools[1278]: makedumpfile Completed. [ 148.009135] kdump-tools[1278]: * kdump-tools: saved dmesg content in /var/crash/201808110838 [ 148.033105] kdump-tools[1278]: Sat, 11 Aug 2018 08:38:51 -0400 [ 148.069165]
[Kernel-packages] [Bug 1784998] Re: After a while touchpad doesn't work
fokedFromTheLife, thank you for reporting this and helping make Ubuntu better. Please answer all of the following: 1) Regarding your Bug Description comment: >"after a while..." 1a) Could you please define specifically how long a while is? Seconds, minutes, hours, etc.? 1b) Could you please advise to after a while from when? Boot up, login, opening a program, etc.? 2) Is this issue something that started to happen after an update? If so, which and when precisely? 3) Regarding the non-default kernel parameters: nouveau.modeset=0 tpm_tis.interrupts=0 acpi_osi=Linux i915.preliminary_hw_support=1 idle=nomwait If you remove these, is the issue still reproducible? ** Tags added: bios-outdated-307 ** Changed in: linux (Ubuntu) Importance: Undecided => Low ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1784998 Title: After a while touchpad doesn't work Status in linux package in Ubuntu: Incomplete Status in xorg-server package in Ubuntu: New Bug description: after a while my touch pad don't work but mouse with usb work in my laptop my laptop : Asus GL553V ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Aug 2 10:23:53 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Device [8086:591b] (rev 04) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:15e0] Subsystem: ASUSTeK Computer Inc. GP107M [GeForce GTX 1050 Mobile] [1043:15e0] InstallationDate: Installed on 2018-04-29 (94 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2a Intel Corp. Bus 001 Device 002: ID 0bda:57f5 Realtek Semiconductor Corp. Bus 001 Device 004: ID 0b05:1854 ASUSTek Computer, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. GL553VD ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-29-generic root=UUID=48228a8f-bbca-4be4-a07a-96a383809e68 ro quiet splash nouveau.modeset=0 tpm_tis.interrupts=0 acpi_osi=Linux i915.preliminary_hw_support=1 idle=nomwait vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/02/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GL553VD.306 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: GL553VD 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.:bvrGL553VD.306:bd01/02/2018:svnASUSTeKCOMPUTERINC.:pnGL553VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL553VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: GL dmi.product.name: GL553VD dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 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/1784998/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1687274] Re: Boot fails waiting for /dev/disk/by-uuid
Did a kernel update or the upgrade to a newer Ubuntu release resolve this problem? ** Package changed: xubuntu-meta (Ubuntu) => linux (Ubuntu) ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1687274 Title: Boot fails waiting for /dev/disk/by-uuid Status in linux package in Ubuntu: Incomplete Bug description: The system is stuck waiting 90 seconds for the /dev/disk/by-uuid/* devices to show up. When dropping me to a shell, they do exist. Forcing the system to fsck (by removing power) makes no difference. After rebooting 1-5 times it suddenly completes booting. So it seems it might be a race condition. = Workaround = If I boot once in recovery mode, then the next boot will mostly complete just fine. OK as a workaround, but a horrible solution. I can even just run `systemctl reboot` from recovery mode - no need to boot fully. Running `reboot`, however, does not work. Attached: working$ cat ls-dev-disk-by-uuid working$ cat journalctl-xb failing$ cat ls-dev-disk-by-uuid failing$ cat journalctl-xb To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1687274/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1785319] Re: All kinds of problems on wake from lid close 18.04
** Tags added: nondefault-kernel-parameters -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1785319 Title: All kinds of problems on wake from lid close 18.04 Status in linux package in Ubuntu: Incomplete Bug description: This seems to be multiple packages, Ubuntu 18.04 itself (because 17.10 and all previous versions worked fine), and firmware. When wake from lid close, GUI freezes up and un-freezes every few seconds. Wifi won't even scan for networks, much less join one. Probably more things are wrong, but that's what's visible to me. Here's dmesg recent errors: [43548.249307] ath10k_warn: 129 callbacks suppressed [43548.249309] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.285609] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.316369] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.347057] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.382893] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.419305] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.455788] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.492277] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.523109] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.553793] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43551.161054] ath10k_pci :02:00.0: failed to read device register, device is gone [43551.270391] ath10k_pci :02:00.0: firmware crashed! (guid c2f1d8ad-ba2b-4c87-a0e1-9dff072ac468) [43551.270394] ath10k_pci :02:00.0: qca6174 hw3.2 target 0x0503 chip_id 0x00340aff sub 1a56:1535 [43551.270396] ath10k_pci :02:00.0: kconfig debug 0 debugfs 1 tracing 1 dfs 0 testmode 0 [43551.270803] ath10k_pci :02:00.0: firmware ver WLAN.RM.4.4.1-00079-QCARMSWPZ-1 api 6 features wowlan,ignore-otp crc32 fd869beb [43551.271233] ath10k_pci :02:00.0: board_file api 2 bmi_id N/A crc32 20d869c3 [43551.271235] ath10k_pci :02:00.0: htt-ver 3.47 wmi-op 4 htt-op 3 cal otp max-sta 32 raw 0 hwcrypto 1 [43551.271242] ath10k_pci :02:00.0: failed to read firmware dump area: -28 [43551.271243] ath10k_pci :02:00.0: Copy Engine register dump: [43551.417001] ath10k_pci :02:00.0: [00]: 0x00034400 4294967295 4294967295 4294967295 4294967295 [43551.562682] ath10k_pci :02:00.0: [01]: 0x00034800 4294967295 4294967295 4294967295 4294967295 [43551.708407] ath10k_pci :02:00.0: [02]: 0x00034c00 4294967295 4294967295 4294967295 4294967295 [43551.841610] ath10k_pci :02:00.0: [03]: 0x00035000 4294967295 4294967295 4294967295 4294967295 [43551.975925] ath10k_pci :02:00.0: [04]: 0x00035400 4294967295 4294967295 4294967295 4294967295 [43552.108938] ath10k_pci :02:00.0: [05]: 0x00035800 4294967295 4294967295 4294967295 4294967295 [43552.254895] ath10k_pci :02:00.0: [06]: 0x00035c00 4294967295 4294967295 4294967295 4294967295 [43552.400652] ath10k_pci :02:00.0: [07]: 0x00036000 4294967295 4294967295 4294967295 4294967295 [43552.400689] ath10k_pci :02:00.0: failed to reset chip: -5 [43552.400690] ath10k_pci :02:00.0: Could not init hif: -5 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tom1383 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-04-26 (103 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180228) MachineType: Dell Inc. XPS 15 9560 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-30-generic root=UUID=9ccc05c8-ea98-4229-a4d3-6d3a292df6df ro quiet splash acpi_rev_override=5 nouveau.modeset=0 enable_psr=1 disable_power_well=0 pci=noaer pcie_aspm=force nmi_watchdog=0 nouveau.runpm=0 vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-30.32-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-30-generic N/A linux-backports-modules-4.15.0-30-generic N/A linux-firmware 1.173.1 Tags: bionic Uname: Linux 4.15.0-30-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/23/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.9.4 dmi.board.name: 0JHP5H
[Kernel-packages] [Bug 1753510] Re: Cannot boot/install AMD Ryzen 2400G
during dpkg -i : (Reading database ... 506366 files and directories currently installed.) Preparing to unpack linux-image-4.18.0-rc1+_4.18.0-rc1+-1_amd64.deb ... Unpacking linux-image-4.18.0-rc1+ (4.18.0-rc1+-1) ... Setting up linux-image-4.18.0-rc1+ (4.18.0-rc1+-1) ... Error! Your kernel headers for kernel 4.18.0-rc1+ cannot be found. Please install the linux-headers-4.18.0-rc1+ package, or use the --kernelsourcedir option to tell DKMS where it's located ... tried it anyways... it behaves similarly to the others. The first time I booted it eventually dropped into initramfs) prompt, but would not accept keyboard input. subsequent boot was and endless loop of register dumps. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1753510 Title: Cannot boot/install AMD Ryzen 2400G Status in linux package in Ubuntu: Confirmed Bug description: Did a motherboard swap on a trusty old computer that ran ubuntu for 10 years or so. Now it only runs windows (same hardware fresh installs windows with no issue). brand new ryzen 2nd gen with graphics. I know about graphics drivers issues, wasn't expecting that to be dealt with. Just trying to use it as a cpu. So I put in an older (RADEON HD 7850 pitcairn) video card to get some functionality. Without the video card, it boots, but the display is unusable. I can ssh in and see that it works fine as a server, but cannot use terminal or graphical display. With the video card, Put daily ubuntu Bionic image, and "Try Ubuntu", and it goes into an infinite loop. photo attached. I tried 16.04.4 and I think it just went into a blank screen. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1753510/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1687274] [NEW] Boot fails waiting for /dev/disk/by-uuid
You have been subscribed to a public bug: The system is stuck waiting 90 seconds for the /dev/disk/by-uuid/* devices to show up. When dropping me to a shell, they do exist. Forcing the system to fsck (by removing power) makes no difference. After rebooting 1-5 times it suddenly completes booting. So it seems it might be a race condition. = Workaround = If I boot once in recovery mode, then the next boot will mostly complete just fine. OK as a workaround, but a horrible solution. I can even just run `systemctl reboot` from recovery mode - no need to boot fully. Running `reboot`, however, does not work. Attached: working$ cat ls-dev-disk-by-uuid working$ cat journalctl-xb failing$ cat ls-dev-disk-by-uuid failing$ cat journalctl-xb ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- Boot fails waiting for /dev/disk/by-uuid https://bugs.launchpad.net/bugs/1687274 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1638780] Re: Linux 4.8.0-27-generic Eclipse fail
Was this issue resolved? ** Package changed: xubuntu-meta (Ubuntu) => linux (Ubuntu) ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1638780 Title: Linux 4.8.0-27-generic Eclipse fail Status in linux package in Ubuntu: Incomplete Bug description: ubuntu-16.10 After updating system, on each launching of Eclipse, system freezed and i have one way - reboot PC. Mouse, keyboord no workin, clock stoped ect. When i booting using Linux 4.8.0-26-generic it OK. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1638780/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1730321] Re: Ubuntu VM is not detecting the disks connected to Availa beach (LSI/Avago) in Pass Thru mode
** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete ** Changed in: xubuntu-meta (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1730321 Title: Ubuntu VM is not detecting the disks connected to Availa beach (LSI/Avago) in Pass Thru mode Status in linux package in Ubuntu: Incomplete Status in xubuntu-meta package in Ubuntu: Invalid Bug description: Below is my setup details: C240 M4 24HDD server with AVB card (FW 24.12.1-0048) and Boot SSDs. Installed ESXi 6.0U1b in the boot SSD in AHCI mode. Updated the latest ESXi Native driver on this. (VMWare-Native-6.610.17.00) Created a VM and Installed Ubuntu 14.04.04. AVB card has one RAID1 VD, one JBOD and all other UG drives. Assigned the AVB controller as a Pass thorugh to ESXi host. Added AVB controller as a Pass through device to the Ubuntu VM. Updated the /etc/vmware/passthru.map file with the device ID and vendor ID of AVB card. Updated the Ubuntu VM with the latest MR driver 06.810 I want to run some IOs to the disks connected to the AVB card from Ubuntu VM. But I am unable to see the disks from the VM. I am seeing so many call traces in the console related to megaraid_sas and see the attached screenshots of the same. Avago is able to reproduce the issue in their lab and see the attached email thread on this discussion. Note : The same scenario is working fine with Ubuntu 12.x series VM's.This issue is occurring both Ubuntu 14.x.x and 16.x.x series guest operating systems. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1730321/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1785319] Re: All kinds of problems on wake from lid close 18.04
Tom, in order to allow additional upstream mainline kernel developers to examine the issue, at your earliest convenience, could you please test the latest mainline kernel? Please keep in mind the following: 1) The one to test is in a folder at the very top of the page (not the daily folder). 2) The release names are irrelevant. 3) The folder time stamps aren't indicative of when the kernel actually was released upstream. 4) Install instructions are available at https://wiki.ubuntu.com/Kernel/MainlineBuilds . If testing on your main install would be inconvenient, one may: 1) Install Ubuntu to a different partition and then test this there. 2) Backup, or clone the primary install. If the latest kernel did not allow you to test to the issue (ex. you couldn't boot into the OS) please make a comment in your report about this, and continue to test the next most recent kernel version until you can test to the issue. Once you've tested the mainline kernel, please comment on which kernel version specifically you tested. If this issue is not reproducible in the mainline kernel, please add the following tags by clicking on the yellow circle with a black pencil icon, next to the word Tags, located at the bottom of the Bug Description: kernel-fixed-upstream kernel-fixed-upstream-X.Y-rcZ Where X, and Y are the first two numbers of the kernel version, and Z is the release candidate number if it exists. If the issue is reproducible with the mainline kernel, please add the following tags: kernel-bug-exists-upstream kernel-bug-exists-upstream-X.Y-rcZ Please note, an error to install the kernel does not fit the criteria of kernel-bug-exists-upstream. Also, you don't need to apport-collect further unless specifically requested to do so. In addition, to keep this issue relevant to upstream, please continue to test the latest mainline kernel as it becomes available. Lastly, it is most helpful that after testing of the latest mainline kernel is complete, you mark this report Status Confirmed. Thank you for your help. ** Tags added: bios-outdated-1.10.1 regression-release ** Changed in: linux (Ubuntu) Importance: Undecided => Low ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1785319 Title: All kinds of problems on wake from lid close 18.04 Status in linux package in Ubuntu: Incomplete Bug description: This seems to be multiple packages, Ubuntu 18.04 itself (because 17.10 and all previous versions worked fine), and firmware. When wake from lid close, GUI freezes up and un-freezes every few seconds. Wifi won't even scan for networks, much less join one. Probably more things are wrong, but that's what's visible to me. Here's dmesg recent errors: [43548.249307] ath10k_warn: 129 callbacks suppressed [43548.249309] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.285609] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.316369] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.347057] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.382893] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.419305] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.455788] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.492277] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.523109] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.553793] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43551.161054] ath10k_pci :02:00.0: failed to read device register, device is gone [43551.270391] ath10k_pci :02:00.0: firmware crashed! (guid c2f1d8ad-ba2b-4c87-a0e1-9dff072ac468) [43551.270394] ath10k_pci :02:00.0: qca6174 hw3.2 target 0x0503 chip_id 0x00340aff sub 1a56:1535 [43551.270396] ath10k_pci :02:00.0: kconfig debug 0 debugfs 1 tracing 1 dfs 0 testmode 0 [43551.270803] ath10k_pci :02:00.0: firmware ver WLAN.RM.4.4.1-00079-QCARMSWPZ-1 api 6 features wowlan,ignore-otp crc32 fd869beb [43551.271233] ath10k_pci :02:00.0: board_file api 2 bmi_id N/A crc32 20d869c3 [43551.271235] ath10k_pci :02:00.0: htt-ver 3.47 wmi-op 4 htt-op 3 cal otp max-sta 32 raw 0 hwcrypto 1 [43551.271242] ath10k_pci :02:00.0: failed to read firmware dump area: -28 [43551.271243] ath10k_pci :02:00.0: Copy Engine register dump: [43551.417001] ath10k_pci :02:00.0: [00]: 0x00034400 4294967295 4294967295 4294967295 4294967295 [43551.562682] ath10k_pci :02:00.0: [01]: 0x00034800 4294967295 4294967295 4294967295
[Kernel-packages] [Bug 1638780] [NEW] Linux 4.8.0-27-generic Eclipse fail
You have been subscribed to a public bug: ubuntu-16.10 After updating system, on each launching of Eclipse, system freezed and i have one way - reboot PC. Mouse, keyboord no workin, clock stoped ect. When i booting using Linux 4.8.0-26-generic it OK. ** Affects: linux (Ubuntu) Importance: Undecided Assignee: Kakosz (k-gorgulev) Status: New ** Tags: ubuntu-16.10 -- Linux 4.8.0-27-generic Eclipse fail https://bugs.launchpad.net/bugs/1638780 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1756455] Re: [HP Spectre x360 - 13-ae004na] On battery kernel 4.15.0-12 reboots instead of turning off
** Tags removed: latest-bios-f.15 ** Tags added: bios-outdated-f.22 needs-upstream-testing ** Changed in: linux (Ubuntu) Importance: Medium => Low -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1756455 Title: [HP Spectre x360 - 13-ae004na] On battery kernel 4.15.0-12 reboots instead of turning off Status in linux package in Ubuntu: Expired Bug description: Ubuntu 18.04, installed from beta 1 ISO + all updates to date HP Spectre x360 13", model 13-ae004na, secure boot on, latest BIOS F.15A, Ubuntu is the only system on disk. When using kernel 4.15.0-12 the system does not power off but instead reboots. Both halt -p from the command line and menu action leads to reboot. Booting with previous kernel 4.15.0-10 resolves the issue, system turns off power as expected. I am not attaching any logs because I cannot see anything unusual there, kern.log entries from 4.15.0-10 and 4.15.0-12 seems to be identical (in fact, there is only one entry there "msr: Direct access to MSR 1b0"). Please let me know what additional information you may need. --- ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dmitry 1568 F pulseaudio DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=7b592f97-cd3d-46d3-8183-1685fd2441b4 InstallationDate: Installed on 2018-03-10 (13 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180309) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 04f2:b593 Chicony Electronics Co., Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Spectre x360 Convertible 13-ae0xx Package: linux-signed ProcEnviron: LANGUAGE=en_GB:en TERM=xterm-256color PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-12-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.15.0-12-generic N/A linux-backports-modules-4.15.0-12-generic N/A linux-firmware 1.173 Tags: bionic Uname: Linux 4.15.0-12-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 02/22/2018 dmi.bios.vendor: AMI dmi.bios.version: F.15 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 83B9 dmi.board.vendor: HP dmi.board.version: 56.37 dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAMI:bvrF.15:bd02/22/2018:svnHP:pnHPSpectrex360Convertible13-ae0xx:pvr:rvnHP:rn83B9:rvr56.37:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Spectre dmi.product.name: HP Spectre x360 Convertible 13-ae0xx dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1756455/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1746340] Re: Samsung SSD corruption (fsck needed)
Hello, my Ubuntu Linux was 8-9 months out of order v. 17.10, and later 18.04. I did many installations and tests, changed SSD M.2 four times (recognized reclamation), changed the whole NUC7i7BNH (recognized reclamation). Log Issue on Intel. Finally I installed Fedora 28. and NVME M.2 SSD is in good condition and work properly. I used default LVM partition format. Ubuntu during installation on VLN filed immediatelly during installation, when updates were applied. The problem is bounded specially with Ubuntu. I doesn't check, which driver use Fedora and Ubuntu, Fedora kernel is '4.17.12-200.fc28.x86_64 #1 x86_64 GNU/Linux', so I cannot distill if it should be in driver or is system settings. But finally, i can say, that my reclamations were unauthorized. Sadly, in that case, the easiest workaround for me is to use different Linux. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1746340 Title: Samsung SSD corruption (fsck needed) Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu 4.13.0-21.24-generic 4.13.13 I have a Razer Blade Stealth 2016. The first Ubuntu I installed was Ubuntu 17.04, which gave me this error after 2 weeks of usage. After that, I installed 16.04 and used it for MONTHS without any problems, until it produced the same error this week. I think it has to do with the ubuntu updates, because I did one recently and one today, just before this problem. Could be a coincidence though. I notice the error when I try to save something on disk and it says me that the disk is in read-only mode: lz@lz:/var/log$ touch something touch: cannot touch 'something': Read-only file system lz@lz:/var/log$ cat syslog Jan 29 01:07:39 lz kernel: [62984.375393] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 lz@lz:/var/log$ dmesg [62984.375393] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.377374] Aborting journal on device nvme0n1p2-8. [62984.379343] EXT4-fs (nvme0n1p2): Remounting filesystem read-only [62984.379516] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.381486] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.383484] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.385469] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.387278] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.389262] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.391252] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.393341] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [63285.618078] audit: type=1400 audit(1517195560.393:63): apparmor="DENIED" operation="capable" profile="/usr/sbin/cupsd" pid=22495 comm="cupsd" capability=12 capname="net_admin" Rebooting the ubuntu will give me a black terminal where I can run fsck /dev/nvm30n1p2 (something like that) and it fill fix a lot of orphaned inodes. The majority of time it boots back to the Ubuntu working good, but some times it boots to a broken ubuntu (no images, lots of things broken). I have to reinstall ubuntu then. Every time I reinstall my Ubuntu, I have to try lots of times until it installs without an Input/Output error. When it installs, I can use it for some hours without having the problem, but if I run the software updates, it ALWAYS crashes and enters in read-only mode, specifically in the part that is installing kernel updates. I noticed that Ubuntu installs updates automatically when they're for security reasons. Could this be the reason my Ubuntu worked for months without the problem, but then an update was applied and it broke? I thought that this bug was happening: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184 and tried different nvme_core.default_ps_max_latency_us= combinations, all them gave errors. I just changed to 0 and I had no error while using ubuntu (however I didn't test for a long time) but I still had the error after trying to update my ubuntu. My Samsung 512gb SSD is: SAMSUNG MZVLW512HMJP-0, FW REV: CXY7501Q on a Razer Blade Stealth. I also asked this on ask
[Kernel-packages] [Bug 1776563] Re: Acer Aspire A315 IOAPIC failure on Ubuntu 18.04, kernel hangs, can't load, kernel freeze (AMD Ryzen 5/Radeon/Raven) / AMDGPU Hybrid crash
kernel installed, exactly same problem (cf screenshot from post #54), the only way to start is still with pci=noacpi I don't know how to make an acpi dump, I made one but seems in hex, something unreadable -> https://paste.ubuntu.com/p/z37K3QTQwZ/ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1776563 Title: Acer Aspire A315 IOAPIC failure on Ubuntu 18.04, kernel hangs, can't load, kernel freeze (AMD Ryzen 5/Radeon/Raven) / AMDGPU Hybrid crash Status in amd: New Status in Linux: Incomplete Status in linux package in Ubuntu: Triaged Status in linux-firmware package in Ubuntu: Confirmed Bug description: CPU: Ryzen 5 2500U VGA: Radeon 535 Notebook: Acer Aspire A315 This is a brand new notebook on the market with Ryzen 5/Radeon. The default kernel of Ubuntu(18.04) hangs at loading with message: tsc: Refined TSC clocksource calibration: 1996.250 MHz clocksource: tsc: mask: 0x max_cycles: (...), max_idle_ns: (...) Soft lockup Using pci=noacpi kernel parameter kernel loads without any problem but my notebook produces more heat than on Win10. If I know right Acer notebooks need ACPI to the correct power management. The same thing happens on mainline 4.17,4.18rc1-2. BIOS upgrade to the latest version: 1.08 hasn't helped This problem has been reported upstream: https://bugzilla.kernel.org/show_bug.cgi?id=200087 The latest correctly working kernel was 4.13.* but the heat problem was present with this too. To manage notifications about this bug go to: https://bugs.launchpad.net/amd/+bug/1776563/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1776563] Re: Acer Aspire A315 IOAPIC failure on Ubuntu 18.04, kernel hangs, can't load, kernel freeze (AMD Ryzen 5/Radeon/Raven) / AMDGPU Hybrid crash
lscpi -vv with root : https://pastebin.com/kGgzPVxf -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1776563 Title: Acer Aspire A315 IOAPIC failure on Ubuntu 18.04, kernel hangs, can't load, kernel freeze (AMD Ryzen 5/Radeon/Raven) / AMDGPU Hybrid crash Status in amd: New Status in Linux: Incomplete Status in linux package in Ubuntu: Triaged Status in linux-firmware package in Ubuntu: Confirmed Bug description: CPU: Ryzen 5 2500U VGA: Radeon 535 Notebook: Acer Aspire A315 This is a brand new notebook on the market with Ryzen 5/Radeon. The default kernel of Ubuntu(18.04) hangs at loading with message: tsc: Refined TSC clocksource calibration: 1996.250 MHz clocksource: tsc: mask: 0x max_cycles: (...), max_idle_ns: (...) Soft lockup Using pci=noacpi kernel parameter kernel loads without any problem but my notebook produces more heat than on Win10. If I know right Acer notebooks need ACPI to the correct power management. The same thing happens on mainline 4.17,4.18rc1-2. BIOS upgrade to the latest version: 1.08 hasn't helped This problem has been reported upstream: https://bugzilla.kernel.org/show_bug.cgi?id=200087 The latest correctly working kernel was 4.13.* but the heat problem was present with this too. To manage notifications about this bug go to: https://bugs.launchpad.net/amd/+bug/1776563/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1776563] Re: Acer Aspire A315 IOAPIC failure on Ubuntu 18.04, kernel hangs, can't load, kernel freeze (AMD Ryzen 5/Radeon/Raven) / AMDGPU Hybrid crash
Hi. I have checked and IMOMMU is rightly disabled. "AMD-SVM=Disabled AMD-IOMMU=Disabled" The lspci -vv = https://pastebin.com/46gZfuDE I'm installing the Kai-Heng's kernel now. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1776563 Title: Acer Aspire A315 IOAPIC failure on Ubuntu 18.04, kernel hangs, can't load, kernel freeze (AMD Ryzen 5/Radeon/Raven) / AMDGPU Hybrid crash Status in amd: New Status in Linux: Incomplete Status in linux package in Ubuntu: Triaged Status in linux-firmware package in Ubuntu: Confirmed Bug description: CPU: Ryzen 5 2500U VGA: Radeon 535 Notebook: Acer Aspire A315 This is a brand new notebook on the market with Ryzen 5/Radeon. The default kernel of Ubuntu(18.04) hangs at loading with message: tsc: Refined TSC clocksource calibration: 1996.250 MHz clocksource: tsc: mask: 0x max_cycles: (...), max_idle_ns: (...) Soft lockup Using pci=noacpi kernel parameter kernel loads without any problem but my notebook produces more heat than on Win10. If I know right Acer notebooks need ACPI to the correct power management. The same thing happens on mainline 4.17,4.18rc1-2. BIOS upgrade to the latest version: 1.08 hasn't helped This problem has been reported upstream: https://bugzilla.kernel.org/show_bug.cgi?id=200087 The latest correctly working kernel was 4.13.* but the heat problem was present with this too. To manage notifications about this bug go to: https://bugs.launchpad.net/amd/+bug/1776563/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1785480] Re: Xorg freeze (kernel general protection fault: 0000 [#1] SMP)
Been running a few days on latest 4.18.0-041800rc8 and so far no crashes, so a tentative "fixed" might be appropriate now. Of course this message may be just the curse needed to replicate the issue! (I'll update if so) I'm still none the wiser as to what might have been fixed or what caused the issue in the first place -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1785480 Title: Xorg freeze (kernel general protection fault: [#1] SMP) Status in linux package in Ubuntu: Incomplete Bug description: Stack trace from last freeze: ~$ cat /var/log/kern.log|grep "5 15:1" Aug 5 15:15:45 GA-MA785GMT-UD2H kernel: [54412.878703] general protection fault: [#1] SMP Aug 5 15:15:45 GA-MA785GMT-UD2H kernel: [54412.878740] Modules linked in: pci_stub vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) snd_usb_audio snd_hda_codec_realtek snd_hda_codec_generic snd_hda_codec_hdmi snd_usbmidi_lib snd_hda_intel snd_hda_codec snd_hda_core snd_hwdep snd_pcm joydev snd_seq_midi snd_seq_midi_event snd_rawmidi kvm_amd kvm snd_seq irqbypass snd_seq_device snd_timer snd input_leds k10temp serio_raw edac_mce_amd edac_core i2c_piix4 soundcore shpchp 8250_fintek mac_hid parport_pc ppdev lp parport autofs4 hid_generic hid_logitech_hidpp pata_acpi hid_logitech_dj usbhid hid uas usb_storage amdkfd amd_iommu_v2 radeon i2c_algo_bit ttm drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops r8169 firewire_ohci drm firewire_core mii pata_atiixp crc_itu_t ahci libahci wmi fjes Aug 5 15:15:45 GA-MA785GMT-UD2H kernel: [54412.879121] CPU: 2 PID: 14839 Comm: MemoryInfra Tainted: G OE 4.4.0-131-generic #157-Ubuntu Aug 5 15:15:45 GA-MA785GMT-UD2H kernel: [54412.879163] Hardware name: Gigabyte Technology Co., Ltd. GA-MA785GMT-UD2H/GA-MA785GMT-UD2H, BIOS F1 07/03/2009 Aug 5 15:15:45 GA-MA785GMT-UD2H kernel: [54412.879207] task: 88022143a640 ti: 88006499c000 task.ti: 88006499c000 Aug 5 15:15:45 GA-MA785GMT-UD2H kernel: [54412.879240] RIP: 0010:[] [] find_get_entry+0x34/0xa0 Aug 5 15:15:45 GA-MA785GMT-UD2H kernel: [54412.879280] RSP: 0018:88006499fd78 EFLAGS: 00010246 Aug 5 15:15:45 GA-MA785GMT-UD2H kernel: [54412.879304] RAX: 8800603c5c28 RBX: 880069a27508 RCX: fffa Aug 5 15:15:45 GA-MA785GMT-UD2H kernel: [54412.879335] RDX: RSI: 8800603c5c28 RDI: f7ffea000763c880 Aug 5 15:15:45 GA-MA785GMT-UD2H kernel: [54412.879367] RBP: 88006499fd88 R08: R09: 8800603c5b60 Aug 5 15:15:45 GA-MA785GMT-UD2H kernel: [54412.879398] R10: 88006499fd58 R11: 7f44a30bf000 R12: 0314 Aug 5 15:15:45 GA-MA785GMT-UD2H kernel: [54412.879429] R13: 0200 R14: 8801477fe000 R15: 01d4 Aug 5 15:15:45 GA-MA785GMT-UD2H kernel: [54412.879461] FS: 7f44b1e86700() GS:88022fd0() knlGS: Aug 5 15:15:45 GA-MA785GMT-UD2H kernel: [54412.879496] CS: 0010 DS: ES: CR0: 80050033 Aug 5 15:15:45 GA-MA785GMT-UD2H kernel: [54412.879522] CR2: 163c8d2cc000 CR3: 1a6a5000 CR4: 06f0 Aug 5 15:15:45 GA-MA785GMT-UD2H kernel: [54412.879554] Stack: Aug 5 15:15:45 GA-MA785GMT-UD2H kernel: [54412.879564] 880069a27500 0314 88006499fda8 811c9ed6 Aug 5 15:15:45 GA-MA785GMT-UD2H kernel: [54412.879600] 8801c0071314 0315 88006499fde8 811c9fce Aug 5 15:15:45 GA-MA785GMT-UD2H kernel: [54412.879637] 8801c0071141 88006499fed8 7f44a34c 880176f208c8 Aug 5 15:15:45 GA-MA785GMT-UD2H kernel: [54412.879674] Call Trace: Aug 5 15:15:45 GA-MA785GMT-UD2H kernel: [54412.879690] [] mincore_page+0x26/0xa0 Aug 5 15:15:45 GA-MA785GMT-UD2H kernel: [54412.879715] [] __mincore_unmapped_range+0x7e/0xd0 Aug 5 15:15:45 GA-MA785GMT-UD2H kernel: [54412.879744] [] mincore_unmapped_range+0x1a/0x30 Aug 5 15:15:45 GA-MA785GMT-UD2H kernel: [54412.880836] [] __walk_page_range+0x32b/0x4d0 Aug 5 15:15:45 GA-MA785GMT-UD2H kernel: [54412.881903] [] walk_page_range+0x65/0xe0 Aug 5 15:15:45 GA-MA785GMT-UD2H kernel: [54412.882987] [] SyS_mincore+0x1b8/0x250 Aug 5 15:15:45 GA-MA785GMT-UD2H kernel: [54412.884059] [] ? mincore_unmapped_range+0x30/0x30 Aug 5 15:15:45 GA-MA785GMT-UD2H kernel: [54412.885144] [] ? __mincore_unmapped_range+0xd0/0xd0 Aug 5 15:15:45 GA-MA785GMT-UD2H kernel: [54412.886256] [] ? copy_user_huge_page+0x300/0x300 Aug 5 15:15:45 GA-MA785GMT-UD2H kernel: [54412.887379] [] entry_SYSCALL_64_fastpath+0x22/0xc1 Aug 5 15:15:45 GA-MA785GMT-UD2H kernel: [54412.888534] Code: 41 54 53 48 8d 5f 08 49 89 f4 4c 89 e6 48 89 df e8 d2 3b 27 00 48 85 c0 48 89 c6 74 36 48 8b 38 48 85 ff 74 2e 40 f6 c7 03 75 52 <8b> 4f 1c 85 c9 74 d8 8d 51 01 4c 8d 47 1c 89 c8 f0 0f b1 57 1c Aug
[Kernel-packages] [Bug 1776563] Re: Acer Aspire A315 IOAPIC failure on Ubuntu 18.04, kernel hangs, can't load, kernel freeze (AMD Ryzen 5/Radeon/Raven) / AMDGPU Hybrid crash
It uses latest amdgpu branch. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1776563 Title: Acer Aspire A315 IOAPIC failure on Ubuntu 18.04, kernel hangs, can't load, kernel freeze (AMD Ryzen 5/Radeon/Raven) / AMDGPU Hybrid crash Status in amd: New Status in Linux: Incomplete Status in linux package in Ubuntu: Triaged Status in linux-firmware package in Ubuntu: Confirmed Bug description: CPU: Ryzen 5 2500U VGA: Radeon 535 Notebook: Acer Aspire A315 This is a brand new notebook on the market with Ryzen 5/Radeon. The default kernel of Ubuntu(18.04) hangs at loading with message: tsc: Refined TSC clocksource calibration: 1996.250 MHz clocksource: tsc: mask: 0x max_cycles: (...), max_idle_ns: (...) Soft lockup Using pci=noacpi kernel parameter kernel loads without any problem but my notebook produces more heat than on Win10. If I know right Acer notebooks need ACPI to the correct power management. The same thing happens on mainline 4.17,4.18rc1-2. BIOS upgrade to the latest version: 1.08 hasn't helped This problem has been reported upstream: https://bugzilla.kernel.org/show_bug.cgi?id=200087 The latest correctly working kernel was 4.13.* but the heat problem was present with this too. To manage notifications about this bug go to: https://bugs.launchpad.net/amd/+bug/1776563/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1753510] Re: Cannot boot/install AMD Ryzen 2400G
Ok, please try this kernel: https://people.canonical.com/~khfeng/linux-image-4.18.0-rc1+_4.18.0-rc1+-1_amd64.deb -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1753510 Title: Cannot boot/install AMD Ryzen 2400G Status in linux package in Ubuntu: Confirmed Bug description: Did a motherboard swap on a trusty old computer that ran ubuntu for 10 years or so. Now it only runs windows (same hardware fresh installs windows with no issue). brand new ryzen 2nd gen with graphics. I know about graphics drivers issues, wasn't expecting that to be dealt with. Just trying to use it as a cpu. So I put in an older (RADEON HD 7850 pitcairn) video card to get some functionality. Without the video card, it boots, but the display is unusable. I can ssh in and see that it works fine as a server, but cannot use terminal or graphical display. With the video card, Put daily ubuntu Bionic image, and "Try Ubuntu", and it goes into an infinite loop. photo attached. I tried 16.04.4 and I think it just went into a blank screen. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1753510/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
