[Bug 2080799] [NEW] package linux-headers-6.8.0-44-generic 6.8.0-44.44 failed to install/upgrade: installed linux-headers-6.8.0-44-generic package post-installation script subprocess returned error ex
Public bug reported: recently upgraded to Ubuntu 24.04.1 LTS ProblemType: Package DistroRelease: Ubuntu 24.04 Package: linux-headers-6.8.0-44-generic 6.8.0-44.44 ProcVersionSignature: Ubuntu 6.8.0-41.41-generic 6.8.12 Uname: Linux 6.8.0-41-generic x86_64 ApportVersion: 2.28.1-0ubuntu3.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/seq:mike 3681 F pipewire /dev/snd/controlC0: mike 3686 F wireplumber /dev/snd/controlC1: mike 3686 F wireplumber CRDA: N/A CasperMD5CheckResult: unknown Date: Sun Sep 15 16:23:46 2024 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20180608-47+italia-whl+X37 ErrorMessage: installed linux-headers-6.8.0-44-generic package post-installation script subprocess returned error exit status 11 InstallationDate: Installed on 2019-06-17 (1917 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 MachineType: Dell Inc. XPS 13 9380 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-41-generic root=UUID=efa0a27e-3b01-4807-ad62-789e99ebc783 ro quiet splash vt.handoff=7 Python3Details: /usr/bin/python3.12, Python 3.12.3, python3-minimal, 3.12.3-0ubuntu2 PythonDetails: /usr/bin/python3.12, Python 3.12.3, python-is-python3, 3.11.4-1 RelatedPackageVersions: grub-pc N/A SourcePackage: linux Title: package linux-headers-6.8.0-44-generic 6.8.0-44.44 failed to install/upgrade: installed linux-headers-6.8.0-44-generic package post-installation script subprocess returned error exit status 11 UpgradeStatus: Upgraded to noble on 2024-09-03 (12 days ago) dmi.bios.date: 09/11/2023 dmi.bios.release: 1.26 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.26.0 dmi.board.name: 0KTW76 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.26.0:bd09/11/2023:br1.26:svnDellInc.:pnXPS139380:pvr:rvnDellInc.:rn0KTW76:rvrA00:cvnDellInc.:ct10:cvr:sku08AF: dmi.product.family: XPS dmi.product.name: XPS 13 9380 dmi.product.sku: 08AF dmi.sys.vendor: Dell Inc. mtime.conffile..etc.init.d.apport: 2024-07-22T10:59:07 ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package noble -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2080799 Title: package linux-headers-6.8.0-44-generic 6.8.0-44.44 failed to install/upgrade: installed linux-headers-6.8.0-44-generic package post-installation script subprocess returned error exit status 11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2080799/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1641290] Re: [04f3:0903] Elan Microelectronics Corp fingerprint reader not recognised
Same issue, fingerprint reader not recognized. ASUS VivoBook K-513 Linux Mint 20.3 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1641290 Title: [04f3:0903] Elan Microelectronics Corp fingerprint reader not recognised To manage notifications about this bug go to: https://bugs.launchpad.net/libfprint/+bug/1641290/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1949909] Re: Computer stops responding on resume from suspend
Hi, After the latest Ubuntu updates I am no longer experiencing this issue (possibly nvidia related?) Thanks for your support. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1949909 Title: Computer stops responding on resume from suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1949909/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1949909] Re: Bluetooth crashes on resume from suspend
Hi, apologies if bluez is not the appropriate package. I have followed the above instructions in an case. 1. No crash files present. 2. The following problems were reported on errors.ubuntu.com https://errors.ubuntu.com/oops/feac943a-8847-11eb-9538-fa163ee63de6 https://errors.ubuntu.com/oops/7f383282-8841-11eb-9347-fa163e6cac46 https://errors.ubuntu.com/oops/414874ba-40fd-11e9-90bf-fa163e6cac46 https://errors.ubuntu.com/oops/6c93da58-3552-11e9-9eff-fa163e102db1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1949909 Title: Bluetooth crashes on resume from suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1949909/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1949909] [NEW] bluetooth crashes on resume from suspend
Public bug reported: Crash on resume from suspend. The following messages appear and the computer stops responding: ``` [ 26.227264] Bluetooth: hci0: Reading supported features failed (-16) [ 26.228275] Bluetooth: hci0: Setting Intel telemetry ddc write event mask failed (-95) ``` ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: bluez (not installed) ProcVersionSignature: Ubuntu 5.11.0-38.42~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-38-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Nov 4 22:50:23 2021 InstallationDate: Installed on 2021-09-16 (49 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1949909 Title: bluetooth crashes on resume from suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1949909/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1932987] Re: OpenSCAD multiple OpenGL errors, crashes on render
More, this is on a Lenovo laptop, LCD only (no external monitors, no USB graphics cards on anything like that). Also: = $ openscad --info QObject::startTimer: Timers can only be used with threads started with QThread OpenSCAD Version: 2021.01 System information: Linux 5.11.0-18-generic #19-Ubuntu SMP Fri May 7 14:22:03 UTC 2021 x86_64 Ubuntu 21.04 4 CPUs 7.23 GB RAM User Agent: OpenSCAD/2021.01 (Linux x86_64; Ubuntu 21.04) Compiler: GCC "10.2.1 20210306" 64bit MinGW build: No Debug build: No Boost version: 1_74 Eigen version: 3.3.9 CGAL version, kernels: 5.2, Cartesian, Extended_cartesian, Epeck OpenCSG version: OpenCSG 1.4.2 Qt version: 5.15.2 QScintilla version: 2.11.6 InputDrivers: GLib version: 2.67.5 lodepng version: 20180910 libzip version: 1.7.3 fontconfig version: 2.13.1 freetype version: 2.10.4 harfbuzz version: 2.7.4 cairo version: 1.16.0 lib3mf version: 1.8.1 Application Path: /usr/bin Documents Path: /home/rob/.local/share User Documents Path: /home/rob/Documents Resource Path: /usr/share/openscad User Library Path: /home/rob/.local/share/OpenSCAD/libraries User Config Path: /home/rob/.config/OpenSCAD Backup Path: /home/rob/.local/share/OpenSCAD/backups OPENSCADPATH: OpenSCAD library path: /home/rob/.local/share/OpenSCAD/libraries /usr/share/openscad/libraries OPENSCAD_FONT_PATH: OpenSCAD font path: /usr/share/fonts /usr/local/share/fonts /home/rob/.local/share/fonts /home/rob/.fonts /usr/share/fonts/X11 /usr/share/fonts/cMap /usr/share/fonts/cmap /usr/share/fonts/opentype /usr/share/fonts/truetype /usr/share/fonts/type1 /usr/share/fonts/X11/Type1 /usr/share/fonts/X11/encodings /usr/share/fonts/X11/misc /usr/share/fonts/X11/util /usr/share/fonts/cmap/adobe-cns1 /usr/share/fonts/cmap/adobe-gb1 /usr/share/fonts/cmap/adobe-japan1 /usr/share/fonts/cmap/adobe-japan2 /usr/share/fonts/cmap/adobe-korea1 /usr/share/fonts/opentype/font-awesome /usr/share/fonts/opentype/freefont /usr/share/fonts/opentype/malayalam /usr/share/fonts/opentype/noto /usr/share/fonts/opentype/urw-base35 /usr/share/fonts/truetype/Gargi /usr/share/fonts/truetype/Gubbi /usr/share/fonts/truetype/Nakula /usr/share/fonts/truetype/Navilu /usr/share/fonts/truetype/Sahadeva /usr/share/fonts/truetype/Sarai /usr/share/fonts/truetype/abyssinica /usr/share/fonts/truetype/arphic /usr/share/fonts/truetype/dejavu /usr/share/fonts/truetype/droid /usr/share/fonts/truetype/font-awesome /usr/share/fonts/truetype/fonts-beng-extra /usr/share/fonts/truetype/fonts-deva-extra /usr/share/fonts/truetype/fonts-gujr-extra /usr/share/fonts/truetype/fonts-guru-extra /usr/share/fonts/truetype/fonts-kalapi /usr/share/fonts/truetype/fonts-orya-extra /usr/share/fonts/truetype/fonts-telu-extra /usr/share/fonts/truetype/fonts-yrsa-rasa /usr/share/fonts/truetype/freefont /usr/share/fonts/truetype/kacst /usr/share/fonts/truetype/kacst-one /usr/share/fonts/truetype/lao /usr/share/fonts/truetype/lato /usr/share/fonts/truetype/liberation /usr/share/fonts/truetype/liberation2 /usr/share/fonts/truetype/libreoffice /usr/share/fonts/truetype/lohit-assamese /usr/share/fonts/truetype/lohit-bengali /usr/share/fonts/truetype/lohit-devanagari /usr/share/fonts/truetype/lohit-gujarati /usr/share/fonts/truetype/lohit-kannada /usr/share/fonts/truetype/lohit-malayalam /usr/share/fonts/truetype/lohit-oriya /usr/share/fonts/truetype/lohit-punjabi /usr/share/fonts/truetype/lohit-tamil /usr/share/fonts/truetype/lohit-tamil-classical /usr/share/fonts/truetype/lohit-telugu /usr/share/fonts/truetype/lyx /usr/share/fonts/truetype/malayalam /usr/share/fonts/truetype/noto /usr/share/fonts/truetype/open-sans /usr/share/fonts/truetype/padauk /usr/share/fonts/truetype/pagul /usr/share/fonts/truetype/samyak /usr/share/fonts/truetype/samyak-fonts /usr/share/fonts/truetype/sinhala /usr/share/fonts/truetype/teluguvijayam /usr/share/fonts/truetype/tibetan-machine /usr/share/fonts/truetype/tlwg /usr/share/fonts/truetype/ttf-bitstream-vera /usr/share/fonts/truetype/ttf-khmeros-core /usr/share/fonts/truetype/ubuntu /usr/share/fonts/type1/gsfonts /usr/share/fonts/type1/urw-base35 /usr/share/fonts/X11/encodings/large GLEW version: 2.1.0 OpenGL Version: 4.6 (Compatibility Profile) Mesa 21.0.1 GL Renderer: AMD Radeon R7 Graphics (CARRIZO, DRM 3.40.0, 5.11.0-18-generic, LLVM 11.0.1) GL Vendor: AMD RGBA(), depth(24), stencil(8) GL_ARB_framebuffer_object: yes GL_EXT_framebuffer_object: yes GL_EXT_packed_depth_stencil: yes GL context creator: GLX PNG generator: lodepng GLX version: 1.4 OS info: Linux 5.11.0-18-generic #19-Ubuntu SMP Fri May 7 14:22:03 UTC 2021 Machine: x86_64 Thanks again! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1932987 Title: OpenSCAD multiple OpenGL errors, crashes on render To
[Bug 1932987] [NEW] OpenSCAD multiple OpenGL errors, crashes on render
Public bug reported: After upgrade from 20.10 to 21.04, I am unable to run OpenSCAD successfully. The program launches ok, but after clicking New or loading a file, the preview/render window is blank with no axes shown. When opening an existing .scad file, the Console window shows that the design was rendered, but nothing appears in the viewer. If I then try to do a full Render, the program crashes. If I run OpenSCAD from a command line, I see numerous OpenGL errors: = START === $ openscad Warning: Ignoring XDG_SESSION_TYPE=wayland on Gnome. Use QT_QPA_PLATFORM=wayland to run on Wayland anyway. GLEW Error: Unknown error OpenGL Error: invalid operation OpenGL Error: invalid operation OpenGL Error: invalid operation OpenGL Error: invalid operation OpenGL Program Linker Error: error: linking with uncompiled/unspecialized shadererror: linking with uncompiled/unspecialized shaderOpenGL error src/mouseselector.cc:66:Vertex Shader: invalid enumerant src/mouseselector.cc: OpenGL fragment shader Error: 0:1(1): error: No precision specified in this scope for type `vec3' src/mouseselector.cc: OpenGL Program Linker Error: error: linking with uncompiled/unspecialized shader src/mouseselector.cc: OpenGL symbol retrieval went wrong, id is -1 OpenGL error start: invalid operation OpenGL error render: invalid operation OpenGL error start: invalid operation OpenGL error render: invalid operation CGAL error: assertion violation! Expression : object_list_ File : src/ext/CGAL/OGL_helper.h Line : 578 Explanation: Refer to the bug-reporting instructions at https://www.cgal.org/bug_report.html Aborted (core dumped) === END FWIW, noting the warning at the top, I tried using different values of QT_QPA_PLATFORM, but mostly just hung on launch and never displayed anything. I did not see any similar reports under either Ubuntu's or OpenSCAD's bug trackers. Thanks! ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: openscad 2021.01-1ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-18.19-generic 5.11.17 Uname: Linux 5.11.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Jun 18 23:12:31 2021 InstallationDate: Installed on 2021-03-08 (102 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: openscad UpgradeStatus: Upgraded to hirsute on 2021-06-14 (4 days ago) ** Affects: openscad (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute wayland-session -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1932987 Title: OpenSCAD multiple OpenGL errors, crashes on render To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openscad/+bug/1932987/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931501] [NEW] Stack trace when --help flag added to the end of a command
Public bug reported: If I add --help to the end of an enable command, I get a stack trace: ``` ubuntu@pro1604:~$ sudo ua enable fips --help ERROR:root:Unhandled exception, please file a bug Traceback (most recent call last): File "/usr/lib/python3/dist-packages/uaclient/cli.py", line 937, in wrapper return func(*args, **kwargs) File "/usr/lib/python3/dist-packages/uaclient/cli.py", line 987, in main args = parser.parse_args(args=cli_arguments) File "/usr/lib/python3.5/argparse.py", line 1735, in parse_args args, argv = self.parse_known_args(args, namespace) File "/usr/lib/python3.5/argparse.py", line 1767, in parse_known_args namespace, args = self._parse_known_args(args, namespace) File "/usr/lib/python3.5/argparse.py", line 1955, in _parse_known_args positionals_end_index = consume_positionals(start_index) File "/usr/lib/python3.5/argparse.py", line 1932, in consume_positionals take_action(action, args) File "/usr/lib/python3.5/argparse.py", line 1841, in take_action action(self, namespace, argument_values, option_string) File "/usr/lib/python3.5/argparse.py", line 1138, in __call__ subnamespace, arg_strings = parser.parse_known_args(arg_strings, None) File "/usr/lib/python3.5/argparse.py", line 1767, in parse_known_args namespace, args = self._parse_known_args(args, namespace) File "/usr/lib/python3.5/argparse.py", line 1973, in _parse_known_args start_index = consume_optional(start_index) File "/usr/lib/python3.5/argparse.py", line 1913, in consume_optional take_action(action, args, option_string) File "/usr/lib/python3.5/argparse.py", line 1841, in take_action action(self, namespace, argument_values, option_string) File "/usr/lib/python3.5/argparse.py", line 1025, in __call__ parser.print_help() File "/usr/lib/python3/dist-packages/uaclient/cli.py", line 93, in print_help super().print_help(file=file) File "/usr/lib/python3.5/argparse.py", line 2367, in print_help self._print_message(self.format_help(), file) File "/usr/lib/python3.5/argparse.py", line 2351, in format_help return formatter.format_help() File "/usr/lib/python3.5/argparse.py", line 287, in format_help help = self._root_section.format_help() File "/usr/lib/python3.5/argparse.py", line 217, in format_help func(*args) File "/usr/lib/python3.5/argparse.py", line 217, in format_help func(*args) File "/usr/lib/python3.5/argparse.py", line 524, in _format_action help_text = self._expand_help(action) File "/usr/lib/python3.5/argparse.py", line 611, in _expand_help return self._get_help_string(action) % params TypeError: unsupported operand type(s) for %: 'tuple' and 'dict' Unexpected error(s) occurred. For more details, see the log: /var/log/ubuntu-advantage.log To file a bug run: ubuntu-bug ubuntu-advantage-tools ``` ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: ubuntu-advantage-tools 26.3~16.04.1 ProcVersionSignature: User Name 4.15.0-1113.126~16.04.1-azure 4.15.18 Uname: Linux 4.15.0-1113-azure x86_64 ApportVersion: 2.20.1-0ubuntu2.30 Architecture: amd64 Date: Wed Jun 9 21:14:41 2021 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-advantage-tools UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubuntu-advantage-tools (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug third-party-packages uec-images xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1931501 Title: Stack trace when --help flag added to the end of a command To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/1931501/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1927029] Re: ua attach command fails
I suspect it might be an issue with snapd not being ready to execute snaps, this might help confirm. Is this a persistent issue or does it eventually resolve with retries? Did this happen early in the machine uptime, perhaps in cloud-init? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1927029 Title: ua attach command fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/1927029/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1917409] Re: neutron-l3-agents won't become active
*** This bug is a duplicate of bug 1883089 *** https://bugs.launchpad.net/bugs/1883089 As the fix this was a duplicate of has been abandoned, can this still be addressed somehow? Is there anything I can do to move this forward? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1917409 Title: neutron-l3-agents won't become active To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1917409/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1914881] acpidump.txt
apport information ** Attachment added: "acpidump.txt" https://bugs.launchpad.net/bugs/1914881/+attachment/5461009/+files/acpidump.txt ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1914881 Title: No sound from internal speakers HP Spectre x360 Convertible 14-ea0xxx, Realtek ALC245, To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1914881/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1914881] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1914881/+attachment/5461008/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1914881 Title: No sound from internal speakers HP Spectre x360 Convertible 14-ea0xxx, Realtek ALC245, To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1914881/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1914881] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1914881/+attachment/5461007/+files/UdevDb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1914881 Title: No sound from internal speakers HP Spectre x360 Convertible 14-ea0xxx, Realtek ALC245, To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1914881/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1914881] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1914881/+attachment/5461006/+files/RfKill.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1914881 Title: No sound from internal speakers HP Spectre x360 Convertible 14-ea0xxx, Realtek ALC245, To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1914881/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1914881] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1914881/+attachment/5461005/+files/PulseList.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1914881 Title: No sound from internal speakers HP Spectre x360 Convertible 14-ea0xxx, Realtek ALC245, To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1914881/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1914881] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1914881/+attachment/5461004/+files/ProcModules.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1914881 Title: No sound from internal speakers HP Spectre x360 Convertible 14-ea0xxx, Realtek ALC245, To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1914881/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1914881] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1914881/+attachment/5461003/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1914881 Title: No sound from internal speakers HP Spectre x360 Convertible 14-ea0xxx, Realtek ALC245, To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1914881/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1914881] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1914881/+attachment/5461002/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1914881 Title: No sound from internal speakers HP Spectre x360 Convertible 14-ea0xxx, Realtek ALC245, To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1914881/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1914881] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1914881/+attachment/5461001/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1914881 Title: No sound from internal speakers HP Spectre x360 Convertible 14-ea0xxx, Realtek ALC245, To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1914881/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1914881] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1914881/+attachment/5461000/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1914881 Title: No sound from internal speakers HP Spectre x360 Convertible 14-ea0xxx, Realtek ALC245, To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1914881/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1914881] PaInfo.txt
apport information ** Attachment added: "PaInfo.txt" https://bugs.launchpad.net/bugs/1914881/+attachment/5460999/+files/PaInfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1914881 Title: No sound from internal speakers HP Spectre x360 Convertible 14-ea0xxx, Realtek ALC245, To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1914881/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1914881] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/1914881/+attachment/5460998/+files/Lsusb-v.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1914881 Title: No sound from internal speakers HP Spectre x360 Convertible 14-ea0xxx, Realtek ALC245, To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1914881/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1914881] Lsusb-t.txt
apport information ** Attachment added: "Lsusb-t.txt" https://bugs.launchpad.net/bugs/1914881/+attachment/5460997/+files/Lsusb-t.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1914881 Title: No sound from internal speakers HP Spectre x360 Convertible 14-ea0xxx, Realtek ALC245, To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1914881/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1914881] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1914881/+attachment/5460996/+files/Lsusb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1914881 Title: No sound from internal speakers HP Spectre x360 Convertible 14-ea0xxx, Realtek ALC245, To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1914881/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1914881] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/1914881/+attachment/5460995/+files/Lspci-vt.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1914881 Title: No sound from internal speakers HP Spectre x360 Convertible 14-ea0xxx, Realtek ALC245, To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1914881/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1914881] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1914881/+attachment/5460994/+files/Lspci.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1914881 Title: No sound from internal speakers HP Spectre x360 Convertible 14-ea0xxx, Realtek ALC245, To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1914881/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1914881] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1914881/+attachment/5460993/+files/IwConfig.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1914881 Title: No sound from internal speakers HP Spectre x360 Convertible 14-ea0xxx, Realtek ALC245, To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1914881/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1914881] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1914881/+attachment/5460992/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1914881 Title: No sound from internal speakers HP Spectre x360 Convertible 14-ea0xxx, Realtek ALC245, To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1914881/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1914881] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1914881/+attachment/5460991/+files/CRDA.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1914881 Title: No sound from internal speakers HP Spectre x360 Convertible 14-ea0xxx, Realtek ALC245, To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1914881/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1914881] Re: No sound from internal speakers HP Spectre x360 Convertible 14-ea0xxx, Realtek ALC245,
apport information ** Tags added: apport-collected ** Description changed: There is no sound output from the laptop internal speakers when running Ubuntu 20.10. This is a dual-boot system; - Booting Windows first and then rebooting to Ubuntu -> sound works fine - Booting Ubuntu first and then rebooting to Windows -> Windows identifies sound as not enables and runs its troubleshooter to enable it The card seems to be recognised OK (system sound settings report output device as Speaker - Tiger Lake-LP Smart Sound technology Audio Controller. VU meters etc all appear as if sound is playing, but no sound. Headphone socket works perfectly. Similar bug reports for different laptops in the HP x360 series suggest this is a pinning problem and that the extract below from the boot logs may support this. lsb_release -rd Description: Ubuntu 20.10 Release: 20.10 aplay -l List of PLAYBACK Hardware Devices card 0: sofhdadsp [sof-hda-dsp], device 0: HDA Analog (*) [] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: sofhdadsp [sof-hda-dsp], device 1: HDA Digital (*) [] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: sofhdadsp [sof-hda-dsp], device 3: HDMI1 (*) [] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: sofhdadsp [sof-hda-dsp], device 4: HDMI2 (*) [] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: sofhdadsp [sof-hda-dsp], device 5: HDMI3 (*) [] Subdevices: 1/1 Subdevice #0: subdevice #0 extract from journalctl -b kernel: snd_hda_codec_realtek ehdaudio0D0: autoconfig for ALC245: line_outs=1 (0x17/0x0/0x0/0x0/0x0) type:> kernel: snd_hda_codec_realtek ehdaudio0D0:speaker_outs=0 (0x0/0x0/0x0/0x0/0x0) kernel: snd_hda_codec_realtek ehdaudio0D0:hp_outs=1 (0x21/0x0/0x0/0x0/0x0) kernel: snd_hda_codec_realtek ehdaudio0D0:mono: mono_out=0x0 kernel: snd_hda_codec_realtek ehdaudio0D0:inputs: kernel: snd_hda_codec_realtek ehdaudio0D0: Mic=0x19 ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.8.0-41.46-generic 5.8.18 Uname: Linux 5.8.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: derek 1460 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Feb 6 20:48:52 2021 InstallationDate: Installed on 2021-02-04 (2 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:sofhdadsp failed Symptom_Card: Tiger Lake-LP Smart Sound Technology Audio Controller - sof-hda-dsp Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: derek 1460 F pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [HP Spectre x360 Convertible 14-ea0xxx, Realtek ALC245, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/13/2021 dmi.bios.release: 15.9 dmi.bios.vendor: AMI dmi.bios.version: F.09 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 87F7 dmi.board.vendor: HP dmi.board.version: 40.43 dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 40.43 dmi.modalias: dmi:bvnAMI:bvrF.09:bd01/13/2021:br15.9:efr40.43:svnHP:pnHPSpectrex360Convertible14-ea0xxx:pvr:rvnHP:rn87F7:rvr40.43:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Spectre dmi.product.name: HP Spectre x360 Convertible 14-ea0xxx dmi.product.sku: 2G2C7EA#ABU dmi.sys.vendor: HP + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu50.5 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC0: derek 1481 F pulseaudio + CasperMD5CheckResult: skip + CurrentDesktop: ubuntu:GNOME + DistroRelease: Ubuntu 20.10 + InstallationDate: Installed on 2021-02-04 (2 days ago) + InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) + MachineType: HP HP Spectre x360 Convertible 14-ea0xxx + Package: linux (not installed) + ProcFB: 0 i915drmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-41-generic root=UUID=0a15de41-a7a7-4152-a5dc-e7e69f45fccb ro quiet splash vt.handoff=7 + ProcVersionSignature: Ubuntu 5.8.0-41.46-generic 5.8.18 + RelatedPackageVersions: + linux-restricted-modules-5.8.0-41-generic N/A + linux-backports-modules-5.8.0-41-generic N/A + linux-firmware1.190.3 + Tags: wayland-session groovy + Uname: Linux 5.8.0-41-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm audio cdrom dip lpadmin lxd plugdev pulse pulse-access sambashare sudo
[Bug 1914881] Re: No sound from internal speakers HP Spectre x360 Convertible 14-ea0xxx, Realtek ALC245,
Following instructions at: https://wiki.ubuntu.com/DebuggingSoundProblems ** Package changed: alsa-driver (Ubuntu) => linux (Ubuntu) ** Tags added: kernel-sound ** Description changed: There is no sound output from the laptop internal speakers when running Ubuntu 20.10. This is a dual-boot system; - - Booting windows first and then rebooting to Ubuntu = sound works fine - - Booting Ubuntu first and then rebooting to Windows - Windows identifies sound as not enables and runs its troubleshooter to enable it + - Booting Windows first and then rebooting to Ubuntu -> sound works fine + - Booting Ubuntu first and then rebooting to Windows -> Windows identifies sound as not enables and runs its troubleshooter to enable it The card seems to be recognised OK (system sound settings report output device as Speaker - Tiger Lake-LP Smart Sound technology Audio Controller. VU meters etc all appear as if sound is playing, but no sound. Headphone socket works perfectly. Similar bug reports for different laptops in the HP x360 series suggest this is a pinning problem and that the extract below from the boot logs may support this. lsb_release -rd Description: Ubuntu 20.10 Release: 20.10 - aplay -l List of PLAYBACK Hardware Devices card 0: sofhdadsp [sof-hda-dsp], device 0: HDA Analog (*) [] - Subdevices: 1/1 - Subdevice #0: subdevice #0 + Subdevices: 1/1 + Subdevice #0: subdevice #0 card 0: sofhdadsp [sof-hda-dsp], device 1: HDA Digital (*) [] - Subdevices: 1/1 - Subdevice #0: subdevice #0 + Subdevices: 1/1 + Subdevice #0: subdevice #0 card 0: sofhdadsp [sof-hda-dsp], device 3: HDMI1 (*) [] - Subdevices: 1/1 - Subdevice #0: subdevice #0 + Subdevices: 1/1 + Subdevice #0: subdevice #0 card 0: sofhdadsp [sof-hda-dsp], device 4: HDMI2 (*) [] - Subdevices: 1/1 - Subdevice #0: subdevice #0 + Subdevices: 1/1 + Subdevice #0: subdevice #0 card 0: sofhdadsp [sof-hda-dsp], device 5: HDMI3 (*) [] - Subdevices: 1/1 - Subdevice #0: subdevice #0 + Subdevices: 1/1 + Subdevice #0: subdevice #0 extract from journalctl -b kernel: snd_hda_codec_realtek ehdaudio0D0: autoconfig for ALC245: line_outs=1 (0x17/0x0/0x0/0x0/0x0) type:> kernel: snd_hda_codec_realtek ehdaudio0D0:speaker_outs=0 (0x0/0x0/0x0/0x0/0x0) kernel: snd_hda_codec_realtek ehdaudio0D0:hp_outs=1 (0x21/0x0/0x0/0x0/0x0) kernel: snd_hda_codec_realtek ehdaudio0D0:mono: mono_out=0x0 kernel: snd_hda_codec_realtek ehdaudio0D0:inputs: kernel: snd_hda_codec_realtek ehdaudio0D0: Mic=0x19 ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.8.0-41.46-generic 5.8.18 Uname: Linux 5.8.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC0: derek 1460 F pulseaudio + USERPID ACCESS COMMAND + /dev/snd/controlC0: derek 1460 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Feb 6 20:48:52 2021 InstallationDate: Installed on 2021-02-04 (2 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:sofhdadsp failed Symptom_Card: Tiger Lake-LP Smart Sound Technology Audio Controller - sof-hda-dsp Symptom_DevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC0: derek 1460 F pulseaudio + USERPID ACCESS COMMAND + /dev/snd/controlC0: derek 1460 F pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [HP Spectre x360 Convertible 14-ea0xxx, Realtek ALC245, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/13/2021 dmi.bios.release: 15.9 dmi.bios.vendor: AMI dmi.bios.version: F.09 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 87F7 dmi.board.vendor: HP dmi.board.version: 40.43 dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 40.43 dmi.modalias: dmi:bvnAMI:bvrF.09:bd01/13/2021:br15.9:efr40.43:svnHP:pnHPSpectrex360Convertible14-ea0xxx:pvr:rvnHP:rn87F7:rvr40.43:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Spectre dmi.product.name: HP Spectre x360 Convertible 14-ea0xxx dmi.product.sku: 2G2C7EA#ABU dmi.sys.vendor: HP -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1914881 Title: No sound from internal speakers HP Spectre x360 Convertible 14-ea0xxx, Realtek ALC245, To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1914881/+subscrip
[Bug 1914881] Re: No sound from internal speakers HP Spectre x360 Convertible 14-ea0xxx, Realtek ALC245,
Adding the alsainfo_good attachment ** Attachment added: "alsainfo_good.txt" https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1914881/+attachment/5460962/+files/alsainfo_good.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1914881 Title: No sound from internal speakers HP Spectre x360 Convertible 14-ea0xxx, Realtek ALC245, To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1914881/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1914881] Re: No sound from internal speakers HP Spectre x360 Convertible 14-ea0xxx, Realtek ALC245,
Have collected alsa-info output from non-working and working situations as per the notes at https://bugzilla.kernel.org/show_bug.cgi?id=195457#c11 echo 1 | sudo tee /sys/module/snd_hda_codec/parameters/dump_coef sudo alsa-info --no-upload --output /home/derek/alsainfo_bad.txt ** Bug watch added: Linux Kernel Bug Tracker #195457 https://bugzilla.kernel.org/show_bug.cgi?id=195457 ** Attachment added: "alsainfo run when sound not working" https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1914881/+attachment/5460961/+files/alsainfo_bad.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1914881 Title: No sound from internal speakers HP Spectre x360 Convertible 14-ea0xxx, Realtek ALC245, To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1914881/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1914881] [NEW] No sound from internal speakers HP Spectre x360 Convertible 14-ea0xxx, Realtek ALC245,
Public bug reported: There is no sound output from the laptop internal speakers when running Ubuntu 20.10. This is a dual-boot system; - Booting windows first and then rebooting to Ubuntu = sound works fine - Booting Ubuntu first and then rebooting to Windows - Windows identifies sound as not enables and runs its troubleshooter to enable it The card seems to be recognised OK (system sound settings report output device as Speaker - Tiger Lake-LP Smart Sound technology Audio Controller. VU meters etc all appear as if sound is playing, but no sound. Headphone socket works perfectly. Similar bug reports for different laptops in the HP x360 series suggest this is a pinning problem and that the extract below from the boot logs may support this. lsb_release -rd Description:Ubuntu 20.10 Release:20.10 aplay -l List of PLAYBACK Hardware Devices card 0: sofhdadsp [sof-hda-dsp], device 0: HDA Analog (*) [] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: sofhdadsp [sof-hda-dsp], device 1: HDA Digital (*) [] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: sofhdadsp [sof-hda-dsp], device 3: HDMI1 (*) [] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: sofhdadsp [sof-hda-dsp], device 4: HDMI2 (*) [] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: sofhdadsp [sof-hda-dsp], device 5: HDMI3 (*) [] Subdevices: 1/1 Subdevice #0: subdevice #0 extract from journalctl -b kernel: snd_hda_codec_realtek ehdaudio0D0: autoconfig for ALC245: line_outs=1 (0x17/0x0/0x0/0x0/0x0) type:> kernel: snd_hda_codec_realtek ehdaudio0D0:speaker_outs=0 (0x0/0x0/0x0/0x0/0x0) kernel: snd_hda_codec_realtek ehdaudio0D0:hp_outs=1 (0x21/0x0/0x0/0x0/0x0) kernel: snd_hda_codec_realtek ehdaudio0D0:mono: mono_out=0x0 kernel: snd_hda_codec_realtek ehdaudio0D0:inputs: kernel: snd_hda_codec_realtek ehdaudio0D0: Mic=0x19 ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.8.0-41.46-generic 5.8.18 Uname: Linux 5.8.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: derek 1460 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Feb 6 20:48:52 2021 InstallationDate: Installed on 2021-02-04 (2 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:sofhdadsp failed Symptom_Card: Tiger Lake-LP Smart Sound Technology Audio Controller - sof-hda-dsp Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: derek 1460 F pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [HP Spectre x360 Convertible 14-ea0xxx, Realtek ALC245, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/13/2021 dmi.bios.release: 15.9 dmi.bios.vendor: AMI dmi.bios.version: F.09 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 87F7 dmi.board.vendor: HP dmi.board.version: 40.43 dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 40.43 dmi.modalias: dmi:bvnAMI:bvrF.09:bd01/13/2021:br15.9:efr40.43:svnHP:pnHPSpectrex360Convertible14-ea0xxx:pvr:rvnHP:rn87F7:rvr40.43:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Spectre dmi.product.name: HP Spectre x360 Convertible 14-ea0xxx dmi.product.sku: 2G2C7EA#ABU dmi.sys.vendor: HP ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug groovy wayland-session -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1914881 Title: No sound from internal speakers HP Spectre x360 Convertible 14-ea0xxx, Realtek ALC245, To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1914881/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1912944] Re: keyboard becomes unresponsive in some applications
though it may be at a lower level (I wanted to enter kde-plasma-desktop here which I do have installed from Ubuntu) ** Package changed: ubuntu => meta-kde (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1912944 Title: keyboard becomes unresponsive in some applications To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/meta-kde/+bug/1912944/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1912944] [NEW] keyboard becomes unresponsive in some applications
Public bug reported: Since my upgrade to 20.10 I am sometimes seeing the keyboard becoming unresponsive (or very slowly responding) in some applications. At the moment emacs is in this state - menu events in emacs are fine. I've also seen this behaviour in konsole and firefox. I think the loss of keyboard happens after closing a window (but not always), so far I don't have a recipe for replicating. I've seen bug #1912670 but I'm running plasma (and kde 5.74.0) and my mouse isn't affected - and the current hypothesis on that one is that it is xfce related. In spite of keyboard not working, here I am typing (in the browser) without a problem. Sometimes when it is unresponsive I'm seeing a c5sec delay before the keyboard event is acted upon rather than nothing at all happening. lsb_release -rd Description:Ubuntu 20.10 Release:20.10 I've just suspended the desktop and on un-sleeping the problem is still present. There's no messages in stdout/err for the current emacs session. CPU doesn't look terribly busy. Suggestions on how to debug this are welcome! ** Affects: ubuntu Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1912944 Title: keyboard becomes unresponsive in some applications To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1912944/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1898557] [NEW] Ubuntu focal boot times slower than other distros
Public bug reported: I've noticed first boot times are significantly slower on Ubuntu Focal than other distros. The following benchmark was taken on the same host with in-sync images (so image downloads aren't a factor). https://paste.ubuntu.com/p/ZdscB88vWY/ I'm opening this bug because I care quite a bit about Ubuntu boot times on servers and containers and I think we can probably do better. Opening here as I truly believe this is an Ubuntu distro concern. If it's inappropriate, please let me know where I should raise this if this is the wrong place. Thanks, Casey ** Affects: ubuntu Importance: Undecided Status: New ** Description changed: I've noticed first boot times are significantly slower on Ubuntu Focal than other distros. The following benchmark was taken on the same host with in-sync images (so image downloads aren't a factor). - https://paste.ubuntu.com/p/K98mvRcWCQ/ + https://paste.ubuntu.com/p/ZdscB88vWY/ I'm opening this bug because I care quite a bit about Ubuntu boot times on servers and containers and I think we can probably do better. Opening here as I truly believe this is an Ubuntu distro concern. If it's inappropriate, please let me know where I should raise this if this is the wrong place. Thanks, Casey -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1898557 Title: Ubuntu focal boot times slower than other distros To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1898557/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1642581] Re: Livepatch checkState: check-failed
*** This bug is a duplicate of bug 1886994 *** https://bugs.launchpad.net/bugs/1886994 ** This bug is no longer a duplicate of bug 1655458 Livepatch gives "Invalid Machine Token" and "check-failed" resulting in no payload ** This bug has been marked a duplicate of bug 1886994 Bionic/Focal VMs get the same machine-id -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1642581 Title: Livepatch checkState: check-failed To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1642581/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1860620] Re: ubuntu-desktop-minimal should not depend on mysql libs
Why does desktop depend on libsnmp35 though? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1860620 Title: ubuntu-desktop-minimal should not depend on mysql libs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/net-snmp/+bug/1860620/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1867573] Re: crash in log of cloned Pro instance: uaclient.exceptions.AlreadyAttachedError:
Since `ua auto-attach` runs on boot, it needs to be improved to detect changes in instance-id. If the instance-id changes, all prior tokens should be deleted prior (or as part of) `ua auto-attach`. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1867573 Title: crash in log of cloned Pro instance: uaclient.exceptions.AlreadyAttachedError: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/1867573/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1866703] [NEW] gnome-shell crashes on lock screen
Public bug reported: After latest focal updates, gnome-shell crashes and I lose my entire session when I lock the screen. c@slate:~$ dpkg -l | grep gnome-shell ii gnome-shell3.35.91-1ubuntu2 amd64graphical shell for the GNOME desktop c@slate:~$ lsb_release -rd Description:Ubuntu Focal Fossa (development branch) Release:20.04 syslog at the time of crash shows: Mar 9 15:40:59 slate gnome-shell[14000]: ClutterBoxLayout child Gjs_ui_shellEntry_CapsLockWarning natural height: 0.00 < minimum 24.00 for width 337.00 Mar 9 15:40:59 slate kernel: [ 6402.118795] traps: gnome-shell[14000] trap int3 ip:7f7562fb60d5 sp:7fff34854e80 error:0 in libglib-2.0.so.0.6400.0[7f7562f7a000+84000] Mar 9 15:40:59 slate quasselclient[14674]: Error reading events from display: Broken pipe Mar 9 15:40:59 slate gsd-power[14200]: Error reading events from display: Broken pipe Mar 9 15:40:59 slate gsd-media-keys[14199]: Error reading events from display: Broken pipe Mar 9 15:40:59 slate evolution-alarm[14258]: Error reading events from display: Broken pipe Mar 9 15:40:59 slate gsd-wacom[14211]: Error reading events from display: Broken pipe Mar 9 15:40:59 slate update-notifier[15178]: Error reading events from display: Broken pipe Mar 9 15:40:59 slate gsd-color[14190]: Error reading events from display: Broken pipe Mar 9 15:40:59 slate gsd-keyboard[14196]: Error reading events from display: Broken pipe Mar 9 15:40:59 slate systemd[1660]: gsd-power.service: Main process exited, code=exited, status=1/FAILURE Mar 9 15:40:59 slate systemd[1660]: gsd-power.service: Failed with result 'exit-code'. Mar 9 15:40:59 slate systemd[1660]: gsd-keyboard.service: Main process exited, code=exited, status=1/FAILURE Mar 9 15:40:59 slate systemd[1660]: gsd-keyboard.service: Failed with result 'exit-code'. Mar 9 15:40:59 slate systemd[1660]: gsd-media-keys.service: Main process exited, code=exited, status=1/FAILURE Mar 9 15:40:59 slate systemd[1660]: gsd-media-keys.service: Failed with result 'exit-code'. Mar 9 15:40:59 slate systemd[1660]: gsd-wacom.service: Main process exited, code=exited, status=1/FAILURE Mar 9 15:40:59 slate systemd[1660]: gsd-wacom.service: Failed with result 'exit-code'. Mar 9 15:40:59 slate systemd[1660]: Stopped target GNOME Keyboard handling. Mar 9 15:40:59 slate systemd[1660]: Stopped target GNOME Media keys handling. Mar 9 15:40:59 slate systemd[1660]: Stopped target GNOME Power management handling. Mar 9 15:40:59 slate systemd[1660]: Stopped target GNOME Wacom handling. Mar 9 15:40:59 slate systemd[1660]: gnome-shell-wayland.service: Main process exited, code=dumped, status=5/TRAP Mar 9 15:40:59 slate gnome-shell[14035]: (EE) failed to read Wayland events: Broken pipe Mar 9 15:40:59 slate gsd-media-keys[16326]: X connection to :0 broken (explicit kill or server shutdown). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.35.91-1ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Mar 9 15:49:14 2020 DisplayManager: gdm3 InstallationDate: Installed on 2018-08-26 (561 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.35.91-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2020-01-23 (46 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal wayland-session -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1866703 Title: gnome-shell crashes on lock screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1866703/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1864770] Re: Please remove hockeypuck from Ubuntu
I'm the upstream maintainer of Hockeypuck. If someone wanted to maintain the package in Ubuntu or Debian, I'd be supportive, but this is not work I'm willing to take on. Hockeypuck is primarily distributed as a snap and docker image. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1864770 Title: Please remove hockeypuck from Ubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hockeypuck/+bug/1864770/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1861354] [NEW] installer issuses. using usb stick error 5
Public bug reported: Ive tried different usb sticks and continue to have system installer crash while partitioning the hard drive ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubiquity 20.04.4 ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3 Uname: Linux 5.4.0-9-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 CasperVersion: 1.438 Date: Wed Jan 29 14:58:15 2020 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed quiet splash --- LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200124) SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubiquity-20.04.4 ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1861354 Title: installer issuses. using usb stick error 5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1861354/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1860620] [NEW] ubuntu-desktop-minimal should not depend on mysql libs
Public bug reported: After upgrading to 20.04 I decided to remove packages that I don't need or use. I was surprised to find that mysql client, server and common packages were installed, as I could not remember having installed mysql -- I don't use it or develop for it... When I removed them, ubuntu-desktop-minimal went along for the ride: c@slate:~$ sudo apt-get purge -y mysql-client-core-5.7 mysql-common mysql-server-core-5.7 Reading package lists... Done Building dependency tree Reading state information... Done Package 'mysql-client-core-5.7' is not installed, so not removed Package 'mysql-server-core-5.7' is not installed, so not removed The following package was automatically installed and is no longer required: libgsound0 Use 'sudo apt autoremove' to remove it. The following packages will be REMOVED: colord* gnome-control-center* libmysqlclient21* libsane* libsnmp30* mysql-common* ubuntu-desktop-minimal* 0 upgraded, 0 newly installed, 7 to remove and 0 not upgraded. After this operation, 28.4 MB disk space will be freed. (Reading database ... 381127 files and directories currently installed.) Removing ubuntu-desktop-minimal (1.443) ... Removing gnome-control-center (1:3.34.1-1ubuntu3) ... Removing colord (1.4.4-1ubuntu1) ... Removing libsane:amd64 (1.0.27-3.2ubuntu3) ... Removing libsnmp30:amd64 (5.7.3+dfsg-5ubuntu6) ... Removing libmysqlclient21:amd64 (8.0.18-0ubuntu5) ... Removing mysql-common (5.8+1.0.5ubuntu2) ... Processing triggers for mime-support (3.64ubuntu1) ... Processing triggers for gnome-menus (3.32.0-1ubuntu1) ... Processing triggers for libglib2.0-0:amd64 (2.63.3-1) ... Processing triggers for libc-bin (2.30-0ubuntu3) ... Processing triggers for man-db (2.9.0-2) ... Processing triggers for dbus (1.12.16-2ubuntu2) ... Processing triggers for udev (244-3ubuntu1) ... Processing triggers for desktop-file-utils (0.24-1ubuntu1) ... (Reading database ... 380812 files and directories currently installed.) Purging configuration files for mysql-common (5.8+1.0.5ubuntu2) ... Purging configuration files for colord (1.4.4-1ubuntu1) ... And, reinstalling ubuntu-desktop-minimal wants to brings them back, even with recommends and suggests turned off: c@slate:~$ sudo apt install ubuntu-desktop-minimal --no-install-recommends --no-install- --no-install-recommends --no-install-suggests c@slate:~$ sudo apt install ubuntu-desktop-minimal --no-install-recommends --no-install-suggests Reading package lists... Done Building dependency tree Reading state information... Done The following additional packages will be installed: colord gnome-control-center libmysqlclient21 libsane libsnmp30 mysql-common Suggested packages: colord-sensor-argyll gnome-user-share realmd libcanberra-gtk-module hplip Recommended packages: gnome-online-accounts gnome-control-center-faces rygel | rygel-tracker sane-utils firefox hplip The following NEW packages will be installed: colord gnome-control-center libmysqlclient21 libsane libsnmp30 mysql-common ubuntu-desktop-minimal 0 upgraded, 7 newly installed, 0 to remove and 0 not upgraded. Need to get 0 B/6,114 kB of archives. After this operation, 28.4 MB of additional disk space will be used. Do you want to continue? [Y/n] This seems really wrong... and looks like a transitive dependency, as I don't see it in apt-get showpkg ubuntu-desktop-minimal. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-desktop-minimal 1.443 ProcVersionSignature: Ubuntu 4.15.0-74.84-generic 4.15.18 Uname: Linux 4.15.0-74-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair binder_linux ashmem_linux ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Jan 22 19:26:53 2020 InstallationDate: Installed on 2018-08-26 (514 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-meta UpgradeStatus: Upgraded to focal on 2020-01-23 (0 days ago) ** Affects: ubuntu-meta (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal wayland-session -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1860620 Title: ubuntu-desktop-minimal should not depend on mysql libs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1860620/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1841659] Re: shaky, unreadable screens; orig. prog seems to be over written??
*** This bug is a duplicate of bug 1841318 *** https://bugs.launchpad.net/bugs/1841318 I fumbled around and got it fixed. On Tue, Aug 27, 2019 at 8:45 PM Daniel van Vugt < daniel.van.v...@canonical.com> wrote: > *** This bug is a duplicate of bug 1841318 *** > https://bugs.launchpad.net/bugs/1841318 > > Thank you for taking the time to report this bug and helping to make > Ubuntu better. This particular bug has already been reported and is a > duplicate of bug 1841318, so it is being marked as such. Please look at > the other bug report to see if there is any missing information that you > can provide, or to see if there is a workaround for the bug. > Additionally, any further discussion regarding the bug should occur in > the other report. Feel free to continue to report any other bugs you may > find. > > > ** This bug has been marked a duplicate of bug 1841318 >Shaky display on GM965 [X3100] (Core 2 Duo L7500) > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1841659 > > Title: > shaky, unreadable screens; orig. prog seems to be over written?? > > Status in xorg package in Ubuntu: > New > > Bug description: > I apologize that I cannot explain clearly what happened to end up with > this problem. The machine works when I get into firefox, but I really > don't have much. My orig. sys. did not have a "dash"? but I had top > and bottom options. I just do not know what occurred, but I would like > to get rid of the shaky pages either with this or my original > settings. > > This problem occurred when I was trying to fix or change something. I > do not think this is a bug but it is probably my fault somehow. > > Is there a chance this can be fixed? If not I'll have to re-install > after I save all my documents and stuff. It is a dual boot win 7/ > Uuntu system. > > Is there a step by step guide to help me get this fixed? > > Is there any chance you all can help? > > Does my explanation of this problem make any sense? > > ProblemType: Bug > DistroRelease: Ubuntu 19.04 > Package: xorg 1:7.7+19ubuntu12 > ProcVersionSignature: Ubuntu 5.0.0-25.26-generic 5.0.18 > Uname: Linux 5.0.0-25-generic x86_64 > .tmp.unity_support_test.0: > > ApportVersion: 2.20.10-0ubuntu27.1 > Architecture: amd64 > CompizPlugins: No value set for > `/apps/compiz-1/general/screen0/options/active_plugins' > CompositorRunning: compiz > CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' > CompositorUnredirectFSW: true > CurrentDesktop: Unity:Unity7:ubuntu > Date: Tue Aug 27 14:04:31 2019 > DistUpgraded: Fresh install > DistroCodename: disco > DistroVariant: ubuntu > ExtraDebuggingInterest: Yes, if not too technical > GraphicsCard: >Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller > (primary) [8086:2a02] (rev 0c) (prog-if 00 [VGA controller]) > Subsystem: Lenovo GM965 [X3100] on ThinkPad T61/R61 [17aa:20b5] > Subsystem: Lenovo GM965 [X3100] on ThinkPad T61/R61 [17aa:20b5] > InstallationDate: Installed on 2015-09-10 (1447 days ago) > InstallationMedia: Ubuntu-MATE 15.04 "Vivid Vervet" - Release amd64 > (20150422.1) > MachineType: LENOVO 7763CU8 > PccardctlIdent: >Socket 0: > no product info available > PccardctlStatus: >Socket 0: > no card > ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-25-generic > root=UUID=125478c5-8ad6-45c1-b162-78e61507b85c ro quiet splash vt.handoff=1 > SourcePackage: xorg > Symptom: display > UpgradeStatus: No upgrade log present (probably fresh install) > dmi.bios.date: 10/12/2009 > dmi.bios.vendor: LENOVO > dmi.bios.version: 7SET38WW (1.24 ) > dmi.board.name: 7763CU8 > dmi.board.vendor: LENOVO > dmi.board.version: Not Available > dmi.chassis.asset.tag: 2075960 > dmi.chassis.type: 10 > dmi.chassis.vendor: LENOVO > dmi.chassis.version: Not Available > dmi.modalias: > dmi:bvnLENOVO:bvr7SET38WW(1.24):bd10/12/2009:svnLENOVO:pn7763CU8:pvrThinkPadX61Tablet:rvnLENOVO:rn7763CU8:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: > dmi.product.family: ThinkPad X61 Tablet > dmi.product.name: 7763CU8 > dmi.product.version: ThinkPad X61 Tablet > dmi.sys.vendor: LENOVO > version.compiz: compiz 1:0.9.14.0+19.04.20190223.1-0ubuntu1 > version.libdrm2: libdrm2 2.4.97-1ubuntu1 > version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~19.04.1 > version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~19.04.1 > version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3 > version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1 > version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1 > version.xserver-xorg-video-intel: xserver-xorg-video-intel > 2:2.99.917+git20180925-2 > version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 > > To manage notifications about this bug go to: > https://bugs.launchpad.net
Re: [Bug 1841659] Re: shaky, unreadable screens; orig. prog seems to be over written??
*** This bug is a duplicate of bug 1841318 *** https://bugs.launchpad.net/bugs/1841318 How can it be repaired? On Tue, Aug 27, 2019 at 8:45 PM Daniel van Vugt < daniel.van.v...@canonical.com> wrote: > *** This bug is a duplicate of bug 1841318 *** > https://bugs.launchpad.net/bugs/1841318 > > Thank you for taking the time to report this bug and helping to make > Ubuntu better. This particular bug has already been reported and is a > duplicate of bug 1841318, so it is being marked as such. Please look at > the other bug report to see if there is any missing information that you > can provide, or to see if there is a workaround for the bug. > Additionally, any further discussion regarding the bug should occur in > the other report. Feel free to continue to report any other bugs you may > find. > > > ** This bug has been marked a duplicate of bug 1841318 >Shaky display on GM965 [X3100] (Core 2 Duo L7500) > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1841659 > > Title: > shaky, unreadable screens; orig. prog seems to be over written?? > > Status in xorg package in Ubuntu: > New > > Bug description: > I apologize that I cannot explain clearly what happened to end up with > this problem. The machine works when I get into firefox, but I really > don't have much. My orig. sys. did not have a "dash"? but I had top > and bottom options. I just do not know what occurred, but I would like > to get rid of the shaky pages either with this or my original > settings. > > This problem occurred when I was trying to fix or change something. I > do not think this is a bug but it is probably my fault somehow. > > Is there a chance this can be fixed? If not I'll have to re-install > after I save all my documents and stuff. It is a dual boot win 7/ > Uuntu system. > > Is there a step by step guide to help me get this fixed? > > Is there any chance you all can help? > > Does my explanation of this problem make any sense? > > ProblemType: Bug > DistroRelease: Ubuntu 19.04 > Package: xorg 1:7.7+19ubuntu12 > ProcVersionSignature: Ubuntu 5.0.0-25.26-generic 5.0.18 > Uname: Linux 5.0.0-25-generic x86_64 > .tmp.unity_support_test.0: > > ApportVersion: 2.20.10-0ubuntu27.1 > Architecture: amd64 > CompizPlugins: No value set for > `/apps/compiz-1/general/screen0/options/active_plugins' > CompositorRunning: compiz > CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' > CompositorUnredirectFSW: true > CurrentDesktop: Unity:Unity7:ubuntu > Date: Tue Aug 27 14:04:31 2019 > DistUpgraded: Fresh install > DistroCodename: disco > DistroVariant: ubuntu > ExtraDebuggingInterest: Yes, if not too technical > GraphicsCard: >Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller > (primary) [8086:2a02] (rev 0c) (prog-if 00 [VGA controller]) > Subsystem: Lenovo GM965 [X3100] on ThinkPad T61/R61 [17aa:20b5] > Subsystem: Lenovo GM965 [X3100] on ThinkPad T61/R61 [17aa:20b5] > InstallationDate: Installed on 2015-09-10 (1447 days ago) > InstallationMedia: Ubuntu-MATE 15.04 "Vivid Vervet" - Release amd64 > (20150422.1) > MachineType: LENOVO 7763CU8 > PccardctlIdent: >Socket 0: > no product info available > PccardctlStatus: >Socket 0: > no card > ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-25-generic > root=UUID=125478c5-8ad6-45c1-b162-78e61507b85c ro quiet splash vt.handoff=1 > SourcePackage: xorg > Symptom: display > UpgradeStatus: No upgrade log present (probably fresh install) > dmi.bios.date: 10/12/2009 > dmi.bios.vendor: LENOVO > dmi.bios.version: 7SET38WW (1.24 ) > dmi.board.name: 7763CU8 > dmi.board.vendor: LENOVO > dmi.board.version: Not Available > dmi.chassis.asset.tag: 2075960 > dmi.chassis.type: 10 > dmi.chassis.vendor: LENOVO > dmi.chassis.version: Not Available > dmi.modalias: > dmi:bvnLENOVO:bvr7SET38WW(1.24):bd10/12/2009:svnLENOVO:pn7763CU8:pvrThinkPadX61Tablet:rvnLENOVO:rn7763CU8:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: > dmi.product.family: ThinkPad X61 Tablet > dmi.product.name: 7763CU8 > dmi.product.version: ThinkPad X61 Tablet > dmi.sys.vendor: LENOVO > version.compiz: compiz 1:0.9.14.0+19.04.20190223.1-0ubuntu1 > version.libdrm2: libdrm2 2.4.97-1ubuntu1 > version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~19.04.1 > version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~19.04.1 > version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3 > version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1 > version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1 > version.xserver-xorg-video-intel: xserver-xorg-video-intel > 2:2.99.917+git20180925-2 > version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+so
[Bug 1841659] [NEW] shaky, unreadable screens; orig. prog seems to be over written??
Public bug reported: I apologize that I cannot explain clearly what happened to end up with this problem. The machine works when I get into firefox, but I really don't have much. My orig. sys. did not have a "dash"? but I had top and bottom options. I just do not know what occurred, but I would like to get rid of the shaky pages either with this or my original settings. This problem occurred when I was trying to fix or change something. I do not think this is a bug but it is probably my fault somehow. Is there a chance this can be fixed? If not I'll have to re-install after I save all my documents and stuff. It is a dual boot win 7/ Uuntu system. Is there a step by step guide to help me get this fixed? Is there any chance you all can help? Does my explanation of this problem make any sense? ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.0.0-25.26-generic 5.0.18 Uname: Linux 5.0.0-25-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity:Unity7:ubuntu Date: Tue Aug 27 14:04:31 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (primary) [8086:2a02] (rev 0c) (prog-if 00 [VGA controller]) Subsystem: Lenovo GM965 [X3100] on ThinkPad T61/R61 [17aa:20b5] Subsystem: Lenovo GM965 [X3100] on ThinkPad T61/R61 [17aa:20b5] InstallationDate: Installed on 2015-09-10 (1447 days ago) InstallationMedia: Ubuntu-MATE 15.04 "Vivid Vervet" - Release amd64 (20150422.1) MachineType: LENOVO 7763CU8 PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-25-generic root=UUID=125478c5-8ad6-45c1-b162-78e61507b85c ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/12/2009 dmi.bios.vendor: LENOVO dmi.bios.version: 7SET38WW (1.24 ) dmi.board.name: 7763CU8 dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: 2075960 dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr7SET38WW(1.24):bd10/12/2009:svnLENOVO:pn7763CU8:pvrThinkPadX61Tablet:rvnLENOVO:rn7763CU8:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad X61 Tablet dmi.product.name: 7763CU8 dmi.product.version: ThinkPad X61 Tablet dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.14.0+19.04.20190223.1-0ubuntu1 version.libdrm2: libdrm2 2.4.97-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~19.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~19.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20180925-2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 corruption disco ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1841659 Title: shaky, unreadable screens; orig. prog seems to be over written?? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1841659/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1841318] [NEW] some crash rest to a "dash" on left, old system ???
Public bug reported: I have a dual boot system that somehow got corrupted on the ubuntu side. What causes it I do not have a clue. There are two very shaky, blurred screens. Pressing the firefox icon open up browser fine and all seems to work. The display is different from what I gotten use to, but it seems ok. If I close, I get the shaky, very annoying display. I wish I could give you more helpful info. I tried some stuff on the terminal that I got readying internet. I think I must have had another "display" stuffed on top of my original. I don't know how so I am just guessing. I did not have the "dash"??? on the left before. Now, I do. I am 78 years old and I choose Ubuntu because I like it. I do not do a lot of "programing" type of stuff. Ubutnu Mate is what I was using, I think. Hope there is something that helps you. Thank you so much for your help. Ubuntu is a good system. Thanx, Charlie ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.0.0-25.26-generic 5.0.18 Uname: Linux 5.0.0-25-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity:Unity7:ubuntu Date: Sat Aug 24 11:53:20 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (primary) [8086:2a02] (rev 0c) (prog-if 00 [VGA controller]) Subsystem: Lenovo GM965 [X3100] on ThinkPad T61/R61 [17aa:20b5] Subsystem: Lenovo GM965 [X3100] on ThinkPad T61/R61 [17aa:20b5] InstallationDate: Installed on 2015-09-10 (1444 days ago) InstallationMedia: Ubuntu-MATE 15.04 "Vivid Vervet" - Release amd64 (20150422.1) LightdmDisplayLog: (EE) Wacom Serial Penabled Pen eraser: Error reading wacom device : No such device MachineType: LENOVO 7763CU8 PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-25-generic root=UUID=125478c5-8ad6-45c1-b162-78e61507b85c ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/12/2009 dmi.bios.vendor: LENOVO dmi.bios.version: 7SET38WW (1.24 ) dmi.board.name: 7763CU8 dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: 2075960 dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr7SET38WW(1.24):bd10/12/2009:svnLENOVO:pn7763CU8:pvrThinkPadX61Tablet:rvnLENOVO:rn7763CU8:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad X61 Tablet dmi.product.name: 7763CU8 dmi.product.version: ThinkPad X61 Tablet dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.14.0+19.04.20190223.1-0ubuntu1 version.libdrm2: libdrm2 2.4.97-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~19.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~19.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20180925-2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 corruption disco ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1841318 Title: some crash rest to a "dash" on left, old system ??? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1841318/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1075923] Re: nautilus hangs copying large directories from a samba share
This is still an issue on Ubuntu 18.04.2 LTS. I can reliably get it to happen. Need to run killall to get it to stop trying with large transfers. The [x] to stop file operations will not work all the time once it hangs. The terminal and windows dualboot work fine for transferring the same files. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1075923 Title: nautilus hangs copying large directories from a samba share To manage notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/1075923/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1833277] [NEW] LIvepatch widget should link to secure boot information on error
Public bug reported: The livepatch widget will show an error[0] if patches cannot be applied. They cannot be applied on a Secure Boot system unless the livepatch signing key is imported. Unfortunately this requires a reboot and some confirmation in the UEFI settings, so it can't be automated. `canonical-livepatch help` displays some instructions to fix this: SECUREBOOT: If you are using secure boot, you will also need to import the livepatch public keys into your keyring. This can be done with the following command: sudo mokutil --import /snap/canonical-livepatch/current/keys/livepatch-kmod.x509 After this enter a password if necessary for MOK, then reboot. Your BIOS will then guide you through enrolling a new key in MOK. At this point you will be able to verify the module signatures. This is probably something worth linking to from that error message. In general, we might need a page explaining other reasons the kernel can't be patched, how to get more details from the system log, etc. c@slate:~$ canonical-livepatch status client-version: 9.3.0 architecture: x86_64 cpu-model: Intel(R) Core(TM) i7-8550U CPU @ 1.80GHz last-check: 2019-06-18T10:40:35-05:00 boot-time: 2019-06-18T11:05:06-05:00 uptime: 50m59s status: - kernel: 4.15.0-51.55-generic running: true livepatch: checkState: check-failed patchState: apply-failed version: "52.3" fixes: |- * CVE-2019-11477 * CVE-2019-11478 [0] https://drive.google.com/file/d/1cQbtCNE- ekoPO159SJDwKrjPGpkSuucm/view?usp=sharing ** Affects: update-notifier (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1833277 Title: LIvepatch widget should link to secure boot information on error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-notifier/+bug/1833277/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1789035] Re: cannot login due to seeing only white screen
Same problem on an old HP NX7010 Laptop with i386 and forcepae install. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1789035 Title: cannot login due to seeing only white screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sddm/+bug/1789035/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1772374] Re: ubiquity need mount point /sys/firmware/efi/efivars
What is this? Can u stop? On Jan 25, 2019 12:36 AM, "Seth Arnold" <1772...@bugs.launchpad.net> wrote: > ** Information type changed from Public Security to Public > > -- > You received this bug notification because you are subscribed to a > duplicate bug report (1776110). > https://bugs.launchpad.net/bugs/1772374 > > Title: > ubiquity need mount point /sys/firmware/efi/efivars > > Status in OEM Priority Project: > Triaged > Status in ubiquity package in Ubuntu: > Fix Released > Status in ubiquity source package in Bionic: > Confirmed > > Bug description: > Without mount point /sys/firmware/efi/efivars for target system, > ubiquity sometimes failed to install bootloader on target system. > > May 21 08:21:55 ubuntu ubiquity[29387]: Setting up grub-efi-amd64 > (2.02-2ubuntu8) ... > May 21 08:21:56 ubuntu ubiquity[29387]: > May 21 08:21:56 ubuntu ubiquity[29387]: Creating config file > /etc/default/grub with new version > May 21 08:21:56 ubuntu ubiquity[29387]: Installing for x86_64-efi > platform. > May 21 08:21:57 ubuntu ubiquity[29387]: Skipping unreadable variable > "Boot": Input/output error > May 21 08:21:57 ubuntu ubiquity[29387]: Could not prepare Boot variable: > Input/output error > May 21 08:21:57 ubuntu ubiquity[29387]: grub-install: error: efibootmgr > failed to register the boot entry: Input/output error. > May 21 08:21:57 ubuntu ubiquity[29387]: Failed: grub-install > --target=x86_64-efi > May 21 08:21:57 ubuntu ubiquity[29387]: WARNING: Bootloader is not > properly installed, system may not be bootable > May 21 08:21:57 ubuntu ubiquity[29387]: Setting up grub-efi-amd64-signed > (1.93+2.02-2ubuntu8) ... > May 21 08:21:57 ubuntu ubiquity[29387]: Installing for x86_64-efi > platform. > May 21 08:21:58 ubuntu ubiquity[29387]: Skipping unreadable variable > "Boot": Input/output error > May 21 08:21:58 ubuntu ubiquity[29387]: Could not prepare Boot variable: > Input/output error > May 21 08:21:58 ubuntu ubiquity[29387]: grub-install: error: efibootmgr > failed to register the boot entry: Input/output error. > May 21 08:21:58 ubuntu ubiquity[29387]: dpkg: error processing package > grub-efi-amd64-signed (--configure): > May 21 08:21:58 ubuntu ubiquity[29387]: installed grub-efi-amd64-signed > package post-installation script subprocess returned error exit status 1 > May 21 08:21:58 ubuntu ubiquity[29387]: Errors were encountered while > processing: > May 21 08:21:58 ubuntu ubiquity[29387]: grub-efi-amd64-signed > > To manage notifications about this bug go to: > https://bugs.launchpad.net/oem-priority/+bug/1772374/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1772374 Title: ubiquity need mount point /sys/firmware/efi/efivars To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1772374/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1772374] Re: ubiquity need mount point /sys/firmware/efi/efivars
hu? should i be worried? On Thu, Jan 17, 2019 at 5:00 PM Brian Murray wrote: > ** Changed in: ubiquity (Ubuntu Bionic) > Milestone: None => ubuntu-18.04.2 > > -- > You received this bug notification because you are subscribed to a > duplicate bug report (1776110). > https://bugs.launchpad.net/bugs/1772374 > > Title: > ubiquity need mount point /sys/firmware/efi/efivars > > Status in OEM Priority Project: > Triaged > Status in ubiquity package in Ubuntu: > Fix Released > Status in ubiquity source package in Bionic: > Confirmed > > Bug description: > Without mount point /sys/firmware/efi/efivars for target system, > ubiquity sometimes failed to install bootloader on target system. > > May 21 08:21:55 ubuntu ubiquity[29387]: Setting up grub-efi-amd64 > (2.02-2ubuntu8) ... > May 21 08:21:56 ubuntu ubiquity[29387]: > May 21 08:21:56 ubuntu ubiquity[29387]: Creating config file > /etc/default/grub with new version > May 21 08:21:56 ubuntu ubiquity[29387]: Installing for x86_64-efi > platform. > May 21 08:21:57 ubuntu ubiquity[29387]: Skipping unreadable variable > "Boot": Input/output error > May 21 08:21:57 ubuntu ubiquity[29387]: Could not prepare Boot variable: > Input/output error > May 21 08:21:57 ubuntu ubiquity[29387]: grub-install: error: efibootmgr > failed to register the boot entry: Input/output error. > May 21 08:21:57 ubuntu ubiquity[29387]: Failed: grub-install > --target=x86_64-efi > May 21 08:21:57 ubuntu ubiquity[29387]: WARNING: Bootloader is not > properly installed, system may not be bootable > May 21 08:21:57 ubuntu ubiquity[29387]: Setting up grub-efi-amd64-signed > (1.93+2.02-2ubuntu8) ... > May 21 08:21:57 ubuntu ubiquity[29387]: Installing for x86_64-efi > platform. > May 21 08:21:58 ubuntu ubiquity[29387]: Skipping unreadable variable > "Boot": Input/output error > May 21 08:21:58 ubuntu ubiquity[29387]: Could not prepare Boot variable: > Input/output error > May 21 08:21:58 ubuntu ubiquity[29387]: grub-install: error: efibootmgr > failed to register the boot entry: Input/output error. > May 21 08:21:58 ubuntu ubiquity[29387]: dpkg: error processing package > grub-efi-amd64-signed (--configure): > May 21 08:21:58 ubuntu ubiquity[29387]: installed grub-efi-amd64-signed > package post-installation script subprocess returned error exit status 1 > May 21 08:21:58 ubuntu ubiquity[29387]: Errors were encountered while > processing: > May 21 08:21:58 ubuntu ubiquity[29387]: grub-efi-amd64-signed > > To manage notifications about this bug go to: > https://bugs.launchpad.net/oem-priority/+bug/1772374/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1772374 Title: ubiquity need mount point /sys/firmware/efi/efivars To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1772374/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1772374] Re: ubiquity need mount point /sys/firmware/efi/efivars
sorry who is this? On Thu, Jan 3, 2019 at 7:25 AM Drew Walton wrote: > This needs to be merged back to bionic ASAP because it entirely prevents > installing on UEFI systems. > > -- > You received this bug notification because you are subscribed to a > duplicate bug report (1776110). > https://bugs.launchpad.net/bugs/1772374 > > Title: > ubiquity need mount point /sys/firmware/efi/efivars > > Status in OEM Priority Project: > Triaged > Status in ubiquity package in Ubuntu: > Fix Released > Status in ubiquity source package in Bionic: > Confirmed > > Bug description: > Without mount point /sys/firmware/efi/efivars for target system, > ubiquity sometimes failed to install bootloader on target system. > > May 21 08:21:55 ubuntu ubiquity[29387]: Setting up grub-efi-amd64 > (2.02-2ubuntu8) ... > May 21 08:21:56 ubuntu ubiquity[29387]: > May 21 08:21:56 ubuntu ubiquity[29387]: Creating config file > /etc/default/grub with new version > May 21 08:21:56 ubuntu ubiquity[29387]: Installing for x86_64-efi > platform. > May 21 08:21:57 ubuntu ubiquity[29387]: Skipping unreadable variable > "Boot": Input/output error > May 21 08:21:57 ubuntu ubiquity[29387]: Could not prepare Boot variable: > Input/output error > May 21 08:21:57 ubuntu ubiquity[29387]: grub-install: error: efibootmgr > failed to register the boot entry: Input/output error. > May 21 08:21:57 ubuntu ubiquity[29387]: Failed: grub-install > --target=x86_64-efi > May 21 08:21:57 ubuntu ubiquity[29387]: WARNING: Bootloader is not > properly installed, system may not be bootable > May 21 08:21:57 ubuntu ubiquity[29387]: Setting up grub-efi-amd64-signed > (1.93+2.02-2ubuntu8) ... > May 21 08:21:57 ubuntu ubiquity[29387]: Installing for x86_64-efi > platform. > May 21 08:21:58 ubuntu ubiquity[29387]: Skipping unreadable variable > "Boot": Input/output error > May 21 08:21:58 ubuntu ubiquity[29387]: Could not prepare Boot variable: > Input/output error > May 21 08:21:58 ubuntu ubiquity[29387]: grub-install: error: efibootmgr > failed to register the boot entry: Input/output error. > May 21 08:21:58 ubuntu ubiquity[29387]: dpkg: error processing package > grub-efi-amd64-signed (--configure): > May 21 08:21:58 ubuntu ubiquity[29387]: installed grub-efi-amd64-signed > package post-installation script subprocess returned error exit status 1 > May 21 08:21:58 ubuntu ubiquity[29387]: Errors were encountered while > processing: > May 21 08:21:58 ubuntu ubiquity[29387]: grub-efi-amd64-signed > > To manage notifications about this bug go to: > https://bugs.launchpad.net/oem-priority/+bug/1772374/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1772374 Title: ubiquity need mount point /sys/firmware/efi/efivars To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1772374/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1561474] Re: Bluetooth will be disable after resume from suspend on Xenial
Upgrading bluez to 5.50 as mentioned in link below fixed the problem with bluetooth headphones not connecting after resume on Ubuntu 18.04. https://askubuntu.com/questions/1036195/bluetooth-doesnt-work-after- resuming-from-sleep-ubuntu-18-04-lts -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1561474 Title: Bluetooth will be disable after resume from suspend on Xenial To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1561474/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1777520] [NEW] package gnome-software-common 3.28.1-0ubuntu4.18.04.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configurati
Public bug reported: Dont know. tried to do update and got this automatically ProblemType: Package DistroRelease: Ubuntu 18.04 Package: gnome-software-common 3.28.1-0ubuntu4.18.04.1 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Mon Jun 18 14:40:41 2018 Dependencies: DuplicateSignature: package:gnome-software-common:3.28.1-0ubuntu4.18.04.1 Unpacking wireless-regdb (2018.05.09-0ubuntu1~18.04.1) over (2016.06.10-0ubuntu1) ... dpkg: error processing package gnome-software-common (--configure): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2014-12-14 (1282 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) InstalledPlugins: gnome-software-plugin-flatpak N/A gnome-software-plugin-limba N/A gnome-software-plugin-snap3.28.1-0ubuntu4.18.04.1 PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.1 SourcePackage: gnome-software Title: package gnome-software-common 3.28.1-0ubuntu4.18.04.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: Upgraded to bionic on 2018-05-04 (45 days ago) ** Affects: gnome-software (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1777520 Title: package gnome-software-common 3.28.1-0ubuntu4.18.04.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1777520/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1776110] [NEW] it just failed, dont know what else to say but it stoped the installation and game me an error
Public bug reported: nothing ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubiquity 18.04.14 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CasperVersion: 1.394 CurrentDesktop: ubuntu:GNOME Date: Sun Jun 10 15:47:05 2018 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed boot=casper only-ubiquity quiet splash --- LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: LANGUAGE=en_US.UTF-8 PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 LC_NUMERIC=C.UTF-8 SourcePackage: grub-installer UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: grub-installer (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ubiquity-18.04.14 ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1776110 Title: it just failed, dont know what else to say but it stoped the installation and game me an error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1776110/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1689225] [NEW] [Built-in Audio - HD-Audio Generic, playback] Playback problem
Public bug reported: I can hear the right speaker when I use headphones, but not from the built-in speakers on my laptop. System sees the sound card. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-75.96-generic 4.4.59 Uname: Linux 4.4.0-75-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: marshall 2187 F pulseaudio /dev/snd/controlC2: marshall 2187 F pulseaudio /dev/snd/controlC0: marshall 2187 F pulseaudio CurrentDesktop: Unity Date: Sun May 7 21:49:19 2017 InstallationDate: Installed on 2013-07-25 (1382 days ago) InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release amd64 (20130213) PackageArchitecture: all ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_Card: Q1U dynamic microphone - AT2020 USB Symptom_Type: Only some of outputs are working Title: [Built-in Audio - HD-Audio Generic, playback] Playback problem UpgradeStatus: Upgraded to xenial on 2016-07-31 (281 days ago) dmi.bios.date: 12/09/2010 dmi.bios.vendor: Acer dmi.bios.version: V1.02 dmi.board.name: Aspire 5253 dmi.board.vendor: Acer dmi.board.version: V1.02 dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAcer:bvrV1.02:bd12/09/2010:svnAcer:pnAspire5253:pvrV1.02:rvnAcer:rnAspire5253:rvrV1.02:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.name: Aspire 5253 dmi.product.version: V1.02 dmi.sys.vendor: Acer ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1689225 Title: [Built-in Audio - HD-Audio Generic, playback] Playback problem To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1689225/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1301125] Re: Lock screen after idle time freezes unity
I am experiencing the issue where my console becomes completely unresponsive when the unity screensaver is activated. I have tested some potential work arounds for console lockup when the unity screensaver activates under 16.04 (choose one) : Upgrade to 16.10 Upgrade to 16.04.2 Install the 16.04 HWE kernel and X packages Set Radeon option "EnablePageFlip" to "false" Set Radeon option "Accel" to "false" Ubuntu 16.04 (64 bit) ; Unity desktop environment ; "radeon" driver ; Radeon X600 video card ; Dell Optiplex 745 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] RV370 [Radeon X600/X600 SE] ( 1002:5b62 Subsystem: 1002:0b02 ) When the Unity screensaver activates, the screen fades to black and the monitor powers off. After that, the keyboard is unresponsive (not even num lock or scroll lock trigger their keyboard lights) and will not wake the system. The mouse is unresponsive and will not wake the system. Moving the mouse or pressing a number of keys will trigger an "[mi] EQ overflowing" error message and backtrace in /var/log/Xorg.0.log : ... [ 408.605] (II) RADEON(0): Modeline "1152x864"x0.0 108.00 1152 1216 1344 160 0 864 865 868 900 +hsync +vsync (67.5 kHz e) (EE) [mi] EQ overflowing. Additional events will be discarded until existing events are processed. (EE) (EE) Backtrace: (EE) 0: /usr/lib/xorg/Xorg (xorg_backtrace+0x4e) [0x55f7683dbade] (EE) 1: /usr/lib/xorg/Xorg (mieqEnqueue+0x253) [0x55f7683bd583] (EE) 2: /usr/lib/xorg/Xorg (QueuePointerEvents+0x52) [0x55f768295862] (EE) 3: /usr/lib/xorg/modules/input/evdev_drv.so (0x7fbf704d9000+0x61f3) [0x7fbf704df1f3] (EE) 4: /usr/lib/xorg/modules/input/evdev_drv.so (0x7fbf704d9000+0x6a5d) [0x7fbf704dfa5d] (EE) 5: /usr/lib/xorg/Xorg (0x55f768229000+0x94538) [0x55f7682bd538] (EE) 6: /usr/lib/xorg/Xorg (0x55f768229000+0xb9922) [0x55f7682e2922] (EE) 7: /lib/x86_64-linux-gnu/libc.so.6 (0x7fbf7a1b1000+0x354b0) [0x7fbf7a1e64b0] (EE) 8: /lib/x86_64-linux-gnu/libc.so.6 (__read+0x2b) [0x7fbf7a2a769b] (EE) 9: /usr/lib/x86_64-linux-gnu/libdrm.so.2 (drmHandleEvent+0x37) [0x7fbf7b598de7] (EE) 10: /usr/lib/xorg/modules/drivers/radeon_drv.so (0x7fbf7629f000+0x4f9ec) [0x7fbf762ee9ec] (EE) 11: /usr/lib/xorg/modules/drivers/radeon_drv.so (0x7fbf7629f000+0x498e6) [0x7fbf762e88e6] (EE) 12: /usr/lib/xorg/modules/drivers/radeon_drv.so (0x7fbf7629f000+0x499af) [0x7fbf762e89af] (EE) 13: /usr/lib/xorg/Xorg (dixSaveScreens+0x29e) [0x55f7682ae6ee] (EE) 14: /usr/lib/xorg/Xorg (mieqProcessInputEvents+0x1e6) [0x55f7683bdc06] (EE) 15: /usr/lib/xorg/Xorg (ProcessInputEvents+0x19) [0x55f7682bd789] (EE) 16: /usr/lib/xorg/Xorg (0x55f768229000+0x53b7f) [0x55f76827cb7f] (EE) 17: /usr/lib/xorg/Xorg (0x55f768229000+0x57dd3) [0x55f768280dd3] (EE) 18: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf0) [0x7fbf7a1d1830] (EE) 19: /usr/lib/xorg/Xorg (_start+0x29) [0x55f76826b049] (EE) (EE) [mi] These backtraces from mieqEnqueue may point to a culprit higher up the stack. (EE) [mi] mieq is *NOT* the cause. It is a victim. (EE) [mi] EQ overflow continuing. 100 events have been dropped. The only way to restore console operation was to completely kill the existing X11 session (and all running applications) and restart X11. This required logging in remotely and running : sudo service lightdm restart This particular machine does not have any problem under XFCE and xscreensaver -- the screen locks and unlocks without issue. My experience is that it is only a problem with the Unity desktop environment screensaver / screen locker. I found that if I disabled DPMS through the xorg.conf, that the console did not lockup or become unresponsive. However, the screen would not blank. When the screen lock activates, the unlock prompt screen appears and remains visible at all times. After some further experimentation, I have found that if the "EnablePageFlip" option for the radeon driver is set to "false", then the console does not become unresponsive when the Unity screensaver / screen lock activated. Alternately, I also found that setting the radeon driver option "Accel" to "false" also seemed to prevent the console from becoming unresponsive when the Unity screensaver / screen lock activated. sudo mkdir /etc/X11/xorg.conf.d/ sudo echo '## xorg.conf fragment to set radeon option "EnablePageFlip" to "false" Section "Device" Identifier"vdev0" Driver"radeon" Option"EnablePageFlip" "false" EndSection Section "Monitor" Identifier"vmon0" EndSection Section "Screen" Identifier"Default Screen" Monitor "vmon0" Device"vdev0" EndSection ' >> /etc/X11/xorg.conf.d/video.conf -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1301125 Title: Lock screen after idle time freezes unity To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/13011
[Bug 1680286] [NEW] MAAS DNS doesn't handle non /24 subnets well
Public bug reported: We currently have a maas 1.9.5 setup on trusty that has 4 subnets defined in it under 10.x.0.0, one /24, 2 /23s and a /21. With the latest version of maas installed it appears that it is writing out two zones configs for x.10.in-addr.arpa in the named.conf.maas file, which is causing bind to error out. After a bit of debugging, I've confirmed that it is being passed one DNSForwardZoneConfig (for the maas zone) and 2 DNSReverseZoneConfigs (for the x.10.in-addr.arpa zones). Given the zones will overlap in the x.10.in-addr.arpa, it seems there needs to be a way to handle that in the code. Please let me know if you need any further information. Versions: $ dpkg-query -W maas maas1.9.5+bzr4599-0ubuntu1~14.04.1 $ lsb_release -dc Description:Ubuntu 14.04.5 LTS Codename: trusty ** Affects: maas (Ubuntu) Importance: Undecided Status: New ** Tags: canonical-bootstack -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1680286 Title: MAAS DNS doesn't handle non /24 subnets well To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1680286/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1668123] Re: lxc fails to start with cgroup error
** Changed in: systemd (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1668123 Title: lxc fails to start with cgroup error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1668123/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1668123] Re: lxc fails to start with cgroup error
I've had this occur on another system, and this time I could debug it a little more freely. This is an interesting output: # dpkg --purge --simulate systemd dpkg: dependency problems prevent removal of systemd: snapd depends on systemd (>= 204-5ubuntu20.20); however: Package systemd is to be removed. dpkg: error processing package systemd (--purge): dependency problems - not removing Errors were encountered while processing: systemd Now, why snapd was installed I'm not sure, but I guess that's what installed systemd, since the snapd package depends on systemd. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1668123 Title: lxc fails to start with cgroup error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1668123/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1571416] Re: System freezes shortly after reaching the desktop (Ubuntu MATE 16.04, PowerPC)
Got it fixed, thanks. Now I'm having other issues but I don't think they are related. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1571416 Title: System freezes shortly after reaching the desktop (Ubuntu MATE 16.04, PowerPC) To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1571416/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1571416] Re: System freezes shortly after reaching the desktop (Ubuntu MATE 16.04, PowerPC)
I put quotes around both, that must be what broke it. Then I tried to fix it using live CD to re-edit but I couldn't make it stick as the live CD couldn't update the bin. Mint always warns me of syntax errors so if this did as well I missed it. I'll try it again. I might just switch back to Tiger though, nothing against Ubuntu (well Mint, but it's all the same) on a modern laptop. Antique computers can be a pain compared to modern ones. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1571416 Title: System freezes shortly after reaching the desktop (Ubuntu MATE 16.04, PowerPC) To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1571416/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1571416] Re: System freezes shortly after reaching the desktop (Ubuntu MATE 16.04, PowerPC)
I tried that and got a syntax error on reboot that I couldn't recover from. I'll look at it again. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1571416 Title: System freezes shortly after reaching the desktop (Ubuntu MATE 16.04, PowerPC) To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1571416/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1571416] Re: System freezes shortly after reaching the desktop (Ubuntu MATE 16.04, PowerPC)
How do I add the boot options and have them stick? I tried modifying the yaboot but I ended up breaking my install. I can get it installed with the live radeon.agpmode=-1 then I was able to boot it by typing at the first boot Linux radeon.agpmode=-1 that's where it breaks down, I don't know how to make that change stick. I'm used to using Linux Mint which is similar, but just different enough that it breaks things when I try to adjust them. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1571416 Title: System freezes shortly after reaching the desktop (Ubuntu MATE 16.04, PowerPC) To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1571416/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1668123] Re: lxc fails to start with cgroup error
> Sidenote) the 18GB of /var/lib/juju/db (with backups, of backups, of backups) > was not helpful, I'll need to talk to sosreport people about that. This is > what made the report so huge. I did notice that, but I figured getting you all of the data was better than fiddling around trying to not include that part, and maybe missing bits. It'd be nice to have better control over it so we don't have to throw the juju state db around if we don't need to. > 1) It appears that deputy systemd was installed on the machine and > subsequently upgraded: > 2017-02-12 01:30:24 upgrade systemd:amd64 204-5ubuntu20.22 204-5ubuntu20.24 > However, there are no logs available as to what/who/why 20.22 deputy systemd > was installed. Interesting. I don't really know why it would have been installed. > 2) Have you tried to use snapd on trusty on that host? Has anything else > tried to do that? (e.g. juju manual provider or some such?!) No, I don't believe anyone has, I don't see any evidence of that. > 3) To recover the system, you should $ apt remove systemd; and reboot. > However that is the workaround Ok, I'll organise removing the package and rebooting it. > 4) Is this nested lxc? or errors inside the instances? > E.g. from logs I see failures to start lxc instances, but I don't see logs > for failing to start instances for some reason. This is LXCs on a KVM. The errors are in /var/log/lxc, its odd that the sosreport didn't include it. > 5) Why was lxc downgraded/upgraded/downgraded multiple times? We were trying to work out if LP#1656280 was related somehow, the errors were occuring before we did that. > 6) Are the error messages from this machine? Whilst I do see that systemd is > installed, and dsystemd cgroup is mounted, I am failing to find the logs for > any lxc failures related to starting them. The errors are in /var/log/lxc - see the next reply. > Is there /var/log/lxc or some such that you could share privately? for > some reason it was not part of the sosreport. I've uploaded it to https://private- fileshare.canonical.com/~bradm/lp1668123/lp1668123-var-log-lxc.tar.gz > cgmanager should not be interracting with dsystemd. > systemd should not be present on this system (as hwe kernel is not in use, > nor is snapd). > lxc should work irrespective of dsystemd. Its odd that stopping and starting cgmanager would let LXC work then. > I will setup trusty, with GA kernel, lxc1, deploy any charm (e.g. ubuntu), > and install deputy systemd to try to reproduce this test case. > I wonder if upstart systemd job should be neutered, unless snapd is present, > and we are booted with hwe kernel. It does sound like a good idea if we're going to have failures like what we saw. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1668123 Title: lxc fails to start with cgroup error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1668123/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1668123] Re: lxc fails to start with cgroup error
It's uploading slowly to https://private- fileshare.canonical.com/~bradm/lp1668123/, once you see the .md5 file in place and the sosreport is 7.7G, it'll be done. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1668123 Title: lxc fails to start with cgroup error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1668123/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1668123] Re: lxc fails to start with cgroup error
I've generated a sosreport, but its 7.7G. How would you like me to get this to you? The interesting part is that all this was deployed via juju, so I don't know how we got into this state. It also appears to be the only node in this state, so its a bit confusing as to how it got to be this way. Is there anything I can check configuration wise to see why its using deputy systemd? Its certainly not something we've explicitly picked as far as I know. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1668123 Title: lxc fails to start with cgroup error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1668123/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1668123] [NEW] lxc fails to start with cgroup error
Public bug reported: After rebooting a KVM instance hosting LXCs, we get the following error: $ sudo lxc-ls --fancy lxc: cgmanager.c: lxc_cgmanager_escape: 331 call to cgmanager_move_pid_abs_sync(name=dsystemd) failed: invalid request and the LXCs won't start up. In the error logs it showed: lxc-start 1487906073.534 ERRORlxc_cgfs - cgfs.c:lxc_cgroupfs_create:873 - Could not find writable mount point for cgroup hierarchy 11 while trying to create cgroup. The only way I could get the lxcs started was to stop and start cgmanager, just a simple restart wasn't sufficient. Please let me know if you need any further information. $ lsb_release -a Description:Ubuntu 14.04.5 LTS Release:14.04 $ dpkg-query -W systemd systemd 204-5ubuntu20.24 $ dpkg-query -W cgmanager cgmanager 0.24-0ubuntu7.5 $ dpkg-query -W lxc lxc 1.0.9-0ubuntu2 $ uname -a Linux infra 3.13.0-110-generic #157-Ubuntu SMP Mon Feb 20 11:54:05 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: canonical-bootstack -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1668123 Title: lxc fails to start with cgroup error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1668123/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1555760] Re: Too many levels of symbolic links /proc/sys/fs/binfmt_misc
For any poor soul who wanders here, here is the best known workaround for this issue I've seen to date: 22-09-2016 15:23:18 < stgraber!~stgraber@ubuntu/member/stgraber: cmars: if you mask (systemctl mask) the systemd units related to binfmt (systemctl -a | grep binfmt) and reboot, then the problem is gone for good. This is related to systemd's use of automount and not to binfmt- misc (which just ships a bunch of binfmt hooks) FYI, I think this will disable binfmt. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1555760 Title: Too many levels of symbolic links /proc/sys/fs/binfmt_misc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/binfmt-support/+bug/1555760/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1624697] [NEW] package wine-gecko2.21:amd64 2.21-0ubuntu1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration
Public bug reported: think I had an update failure trying to get 16.04 ProblemType: Package DistroRelease: Ubuntu 16.04 Package: wine-gecko2.21:amd64 2.21-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16 Uname: Linux 4.4.0-36-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 Date: Tue Sep 13 11:30:23 2016 ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2014-03-03 (924 days ago) InstallationMedia: Ubuntu 12.04.4 LTS "Precise Pangolin" - Release amd64 (20140204) RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.12~ubuntu16.04.1 SourcePackage: wine-gecko2.21 Title: package wine-gecko2.21:amd64 2.21-0ubuntu1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: Upgraded to xenial on 2016-09-13 (0 days ago) ** Affects: wine-gecko2.21 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1624697 Title: package wine-gecko2.21:amd64 2.21-0ubuntu1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wine-gecko2.21/+bug/1624697/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1555760] Re: Too many levels of symbolic links /proc/sys/fs/binfmt_misc
I apt purge'ed binfmt-support from my system and I'm still able to comment here :) We'll see if this fixes the issue. If it does, why was it even installed on my system by default to begin with? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1555760 Title: Too many levels of symbolic links /proc/sys/fs/binfmt_misc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/binfmt-support/+bug/1555760/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1555760] Re: Too many levels of symbolic links /proc/sys/fs/binfmt_misc
Still seeing this on xenial enough that I've written a script to perform the umounting when LXD gets stuck. Do I even need binfmt_misc on my system? Can I just remove it or would that break something? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1555760 Title: Too many levels of symbolic links /proc/sys/fs/binfmt_misc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/binfmt-support/+bug/1555760/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1602090] [NEW] nova-compute process killed after libc-bin upgrade
Public bug reported: nova-compute process across 2 Openstack deployments died around the same time as the recent libc-bin upgrade: 2016-07-12 00:59:26 status half-configured libc-bin:amd64 2.19-0ubuntu6.9 2016-07-12 00:59:26 status installed libc-bin:amd64 2.19-0ubuntu6.9 Digging into the logs showed it was possibly related to ceph: common/ceph_crypto.cc: In function 'void ceph::crypto::init(CephContext*)' thread 7fbbdb76a740 time 2016-07-12 00:59:37.195100 common/ceph_crypto.cc: 73: FAILED assert(crypto_context != __null) ceph version 0.94.6 (e832001feaf8c176593e0325c8298e3f16dfb403) 1: (()+0x11d2ab) [0x7fbb693b92ab] 2: (()+0x16ad60) [0x7fbb69406d60] 3: (()+0x1372e9) [0x7fbb693d32e9] 4: (()+0x1347b0) [0x7fbb693d07b0] 5: (()+0x6704f) [0x7fbb6930304f] 6: (ffi_call_unix64()+0x4c) [0x7fbbd9447cce] 7: (ffi_call()+0x308) [0x7fbbd9447738] 8: (_ctypes_callproc()+0x48e) [0x7fbbd8e745fe] 9: (()+0x15f9e) [0x7fbbd8e75f9e] 10: (PyObject_Call()+0x36) [0x505f96] 11: (PyEval_EvalFrameEx()+0x1dfa) [0x49b07a] 12: (PyEval_EvalFrameEx()+0xc72) [0x499ef2] 13: (PyEval_EvalFrameEx()+0xc72) [0x499ef2] 14: /usr/bin/python() [0x4a1c9a] 15: (PyObject_Call()+0x36) [0x505f96] 16: (PyEval_EvalFrameEx()+0x1dfa) [0x49b07a] 17: /usr/bin/python() [0x4a1c9a] 18: (PyEval_CallObjectWithKeywords()+0xf6) [0x4dca56] 19: (()+0x392c) [0x7fbbda44b92c] 20: (()+0x3276) [0x7fbbda44b276] 21: (()+0x3dc6) [0x7fbbda44bdc6] 22: (PyEval_EvalFrameEx()+0x3259) [0x49c4d9] 23: /usr/bin/python() [0x4a1c9a] 24: /usr/bin/python() [0x4dfe94] 25: (PyObject_Call()+0x36) [0x505f96] 26: /usr/bin/python() [0x4dddad] 27: (PyEval_EvalFrameEx()+0x965) [0x499be5] 28: (PyEval_EvalFrameEx()+0xc72) [0x499ef2] 29: /usr/bin/python() [0x4a1c9a] 30: /usr/bin/python() [0x4dfe94] 31: (PyEval_CallObjectWithKeywords()+0x6b) [0x4dc9cb] 32: (()+0x392c) [0x7fbbda44b92c] 33: (()+0x3276) [0x7fbbda44b276] 34: /usr/bin/python() [0x5d9538] NOTE: a copy of the executable, or `objdump -rdS ` is needed to interpret this. terminate called after throwing an instance of 'ceph::FailedAssertion' $ dpkg-query -W nova-compute nova-compute2:12.0.3-0ubuntu1~cloud0 $ dpkg-query -W ceph ceph0.94.7-0ubuntu0.15.10.1~cloud0 $ dpkg-query -W libc-bin libc-bin2.19-0ubuntu6.9 Please let us know if you need any further information. ** Affects: nova-compute (Ubuntu) Importance: Undecided Status: New ** Tags: canonical-bootstack -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1602090 Title: nova-compute process killed after libc-bin upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nova-compute/+bug/1602090/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1599681] [NEW] ceph-osd process hung and blocked ps listings
Public bug reported: We ran into a situation over the past couple of days where we had 2 different ceph-osd nodes crash in such a way that they caused ps listing to hang when enumerating the process. Both had a call trace associated with them: Node 1: Jul 4 07:46:15 provider-cs-03 kernel: [4188396.493011] ceph-osdD 882029a67b90 0 5312 1 0x0004 Jul 4 07:46:15 provider-cs-03 kernel: [4188396.590564] 882029a67b90 881037cb8000 8820284f3700 882029a68000 Jul 4 07:46:16 provider-cs-03 kernel: [4188396.688603] 88203296e5a8 88203296e5c0 0015 8820284f3700 Jul 4 07:46:16 provider-cs-03 kernel: [4188396.789329] 882029a67ba8 817ec495 8820284f3700 882029a67bf8 Jul 4 07:46:16 provider-cs-03 kernel: [4188396.891376] Call Trace: Jul 4 07:46:16 provider-cs-03 kernel: [4188396.939271] [] schedule+0x35/0x80 Jul 4 07:46:16 provider-cs-03 kernel: [4188396.989957] [] rwsem_down_read_failed+0xea/0x120 Jul 4 07:46:16 provider-cs-03 kernel: [4188397.041502] [] call_rwsem_down_read_failed+0x14/0x30 Jul 4 07:46:16 provider-cs-03 kernel: [4188397.092616] [] ? __clear_user+0x25/0x50 Jul 4 07:46:16 provider-cs-03 kernel: [4188397.141510] [] ? __clear_user+0x25/0x50 Jul 4 07:46:16 provider-cs-03 kernel: [4188397.189877] [] ? down_read+0x20/0x30 Jul 4 07:46:16 provider-cs-03 kernel: [4188397.237513] [] __do_page_fault+0x398/0x430 Jul 4 07:46:16 provider-cs-03 kernel: [4188397.285588] [] do_page_fault+0x22/0x30 Jul 4 07:46:16 provider-cs-03 kernel: [4188397.332936] [] page_fault+0x28/0x30 Jul 4 07:46:16 provider-cs-03 kernel: [4188397.379495] [] ? __clear_user+0x25/0x50 Jul 4 07:46:16 provider-cs-03 kernel: [4188397.426400] [] copy_fpstate_to_sigframe+0x118/0x1d0 Jul 4 07:46:16 provider-cs-03 kernel: [4188397.474904] [] get_sigframe.isra.7.constprop.9+0x12d/0x150 Jul 4 07:46:16 provider-cs-03 kernel: [4188397.563204] [] do_signal+0x1e8/0x6d0 Jul 4 07:46:16 provider-cs-03 kernel: [4188397.609783] [] ? __sys_sendmsg+0x42/0x80 Jul 4 07:46:16 provider-cs-03 kernel: [4188397.656633] [] ? handle_mm_fault+0x250/0x540 Jul 4 07:46:16 provider-cs-03 kernel: [4188397.703785] [] exit_to_usermode_loop+0x59/0xa2 Jul 4 07:46:17 provider-cs-03 kernel: [4188397.751367] [] syscall_return_slowpath+0x4e/0x60 Jul 4 07:46:17 provider-cs-03 kernel: [4188397.799369] [] int_ret_from_sys_call+0x25/0x8f Node 2: [733869.727139] CPU: 17 PID: 1735127 Comm: ceph-osd Not tainted 4.4.0-15-generic #31-Ubuntu [733869.796954] Hardware name: Dell Inc. PowerEdge R730/0H21J3, BIOS 1.3.6 06/03/2015 [733869.927182] task: 881841dc6e00 ti: 8810cc0a task.ti: 8810cc0a [733870.059139] RIP: 0010:[] [] task_numa_find_cpu+0x2cd/0x710 [733870.192753] RSP: :8810cc0a3bd8 EFLAGS: 00010257 [733870.260298] RAX: RBX: 8810cc0a3c78 RCX: 0012 [733870.389322] RDX: RSI: RDI: 8810210a0e00 [733870.517883] RBP: 8810cc0a3c40 R08: 0006 R09: 013e [733870.646335] R10: 03b4 R11: 001f R12: 881018118000 [733870.774514] R13: 0006 R14: 8810210a0e00 R15: 0379 [733870.902262] FS: 7fdcfab03700() GS:88203e60() knlGS: [733871.031347] CS: 0010 DS: ES: CR0: 80050033 [733871.097820] CR2: 7fdcfab02c20 CR3: 001029204000 CR4: 001406e0 [733871.223381] Stack: [733871.282453] 8810cc0a3c40 811f04ce 88102f6e9680 0012 [733871.404947] 0077 008f 00016d40 0006 [733871.527250] 881841dc6e00 8810cc0a3c78 01ac 01b8 [733871.649648] Call Trace: [733871.707884] [] ? migrate_page_copy+0x21e/0x530 [733871.770946] [] task_numa_migrate+0x43e/0x9b0 [733871.832808] [] ? page_add_anon_rmap+0x10/0x20 [733871.893897] [] numa_migrate_preferred+0x79/0x80 [733871.954283] [] task_numa_fault+0x7f4/0xd40 [733872.013128] [] handle_mm_fault+0xbc0/0x1820 [733872.071309] [] ? do_futex+0x120/0x500 [733872.128149] [] ? __fget_light+0x25/0x60 [733872.184044] [] __do_page_fault+0x197/0x400 [733872.239300] [] do_page_fault+0x22/0x30 [733872.293001] [] page_fault+0x28/0x30 [733872.345187] Code: d0 4c 89 f7 e8 95 c7 ff ff 49 8b 84 24 d8 01 00 00 49 8b 76 78 31 d2 49 0f af 86 b0 00 00 00 4c 8b 45 d0 48 8b 4d b0 48 83 c6 01 <48> f7 f6 4c 89 c6 48 89 da 48 8d 3c 01 48 29 c6 e8 de c5 ff ff [733872.507088] RIP [] task_numa_find_cpu+0x2cd/0x710 [733872.559965] RSP [733872.673773] ---[ end trace aec37273a19e57dc ]--- In the ceph logs for node 1 there is: ./include/interval_set.h: 340: FAILED assert(0) ceph version 0.94.7 (d56bdf93ced6b80b07397d57e3fa68fe68304432) 1: (ceph::__ceph_assert_fail(char const*, char const*, int, char const*)+0x8b) [0x56042ebdeceb] 2: (()+0x4892b8) [0x56042e9512b8] 3: (boost::statechart::simple_s
[Bug 1524635] Re: haproxy syslog configuration causes double logging
I've just tried upgrading a system to the haproxy from your PPA, and it now only logs to /var/log/syslog. The rsyslog.d file has disappeared completely, and its no longer logging to /var/log/haproxy.log. Is that the intended outcome from this? Or should it be logging to just /var/log/haproxy.log? I also tried installing the new haproxy by hand, and it still had /etc/rsyslog.d/haproxy.conf file, and was only logging to /var/log/syslog. Please let me know if you need any more information. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1524635 Title: haproxy syslog configuration causes double logging To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/haproxy/+bug/1524635/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1572320] Re: nova-consoleauth (2:12.0.2-0ubuntu1~cloud0) upgrade leaves nova-consoleauth stopped
This just occured on another cloud, this time with nova-consoleauth 1:2015.1.4-0ubuntu2. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1572320 Title: nova-consoleauth (2:12.0.2-0ubuntu1~cloud0) upgrade leaves nova- consoleauth stopped To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nova/+bug/1572320/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1578080] Re: percona cluster hits resource limits in HA Openstack cloud with xenial
I've upgraded systemd across my cluster to 229-4ubuntu6, removed all my custom tweaks to systemd settings, reloaded the daemon and both rabbitmq and mysql appear to be working fine on my openstack cluster. I'll be throwing a bit more load at it, but usually by this point mysql has fallen over, so I'd say this is a success. ** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1578080 Title: percona cluster hits resource limits in HA Openstack cloud with xenial To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/percona-xtradb-cluster-5.6/+bug/1578080/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1579586] [NEW] ppc64el node maas install failing talking to mpath0
Public bug reported: I'm trying to install a PPC64EL node with Xenial via MAAS 1.9.2 using Juju 1.25.5 and it seems to be failing due to a possible multipath issue. The node is setup in maas with a default single partition. The boot logs show: Begin: Running /scripts/init-premount ... done. Begin: Mounting root file system ... Begin: Running /scripts/local-top ... lvmetad is not active yet, using direct activation during sysinit Volume group "mpath0" not found Cannot process volume group mpath0 done. and then multiple repeats of: Begin: Waiting for root file system ... Begin: Running /scripts/local-block ... lvmetad is not active yet, using direct activation during sysinit Volume group "mpath0" not found Cannot process volume group mpath0 done. To finally fail with: Gave up waiting for root device. Common problems: - Boot args (cat /proc/cmdline) - Check rootdelay= (did the system wait long enough?) - Check root= (did the system wait for the right device?) - Missing modules (cat /proc/modules; ls /dev) ALERT! /dev/mapper/mpath0-part2 does not exist. Dropping to a shell! Rebooting automatically due to panic= boot argument $ dpkg-query -W maas maas1.9.2+bzr4568-0ubuntu1~trusty1 $ dpkg-query -W juju-core juju-core 1.25.5-0ubuntu1~14.04.2~juju1 Kernel version booting on the PPC64EL node is Linux version 4.4.0-21-generic. Please let me know what further information you require to debug this. Thanks, Brad ** Affects: multipath-tools (Ubuntu) Importance: Undecided Status: New ** Tags: canonical-bootstack -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1579586 Title: ppc64el node maas install failing talking to mpath0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1579586/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1578080] Re: percona cluster hits resource limits in HA Openstack cloud with xenial
FWIW I'm also seeing limits hit in other areas, rabbitmq-server seems to be a common one. I'm also randomly seeing: Failed to allocate directory watch: Too many open files on the command line. I suspect its related to the percona and rabbitmq services hitting limits, but I'm not exactly sure. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1578080 Title: percona cluster hits resource limits in HA Openstack cloud with xenial To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/percona-xtradb-cluster-5.6/+bug/1578080/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1555760] Re: Too many levels of symbolic links /proc/sys/fs/binfmt_misc
When is this going to be fixed upstream? I'm having to remount on the host and restart containers quite often. I can't imagine this will be a good user experience for new LXD users on xenial. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1555760 Title: Too many levels of symbolic links /proc/sys/fs/binfmt_misc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/binfmt-support/+bug/1555760/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1569471] [NEW] package python-path (not installed) failed to install/upgrade: trying to overwrite '/usr/lib/python2.7/dist-packages/test_path.py', which is also in package python-path.py 7.2-1ubu
Public bug reported: apt-get update && apt-get dist-upgrade and this happened ProblemType: Package DistroRelease: Ubuntu 16.04 Package: python-path (not installed) ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6 Uname: Linux 4.4.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl ApportVersion: 2.20.1-0ubuntu1 Architecture: amd64 Date: Tue Apr 12 10:52:05 2016 ErrorMessage: trying to overwrite '/usr/lib/python2.7/dist-packages/test_path.py', which is also in package python-path.py 7.2-1ubuntu2~ubuntu16.04.1~ppa1 InstallationDate: Installed on 2016-02-28 (44 days ago) InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160224) RelatedPackageVersions: dpkg 1.18.4ubuntu1 apt 1.2.10 SourcePackage: path.py Title: package python-path (not installed) failed to install/upgrade: trying to overwrite '/usr/lib/python2.7/dist-packages/test_path.py', which is also in package python-path.py 7.2-1ubuntu2~ubuntu16.04.1~ppa1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: path.py (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1569471 Title: package python-path (not installed) failed to install/upgrade: trying to overwrite '/usr/lib/python2.7/dist-packages/test_path.py', which is also in package python-path.py 7.2-1ubuntu2~ubuntu16.04.1~ppa1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/path.py/+bug/1569471/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1568305] [NEW] zfs-dkms 0.6.5.6-0ubuntu6: zfs kernel module failed to build
Public bug reported: Did an apt-get update && apt-get dist-upgrade. My /boot partition did fill up at some point but I was able to recover with autoremove. apport opened this bug so I'll send it anyway in case something in it is helpful. FWIW I've stopped evaluating zfs for the time being because it doesn't seem to work with ceph in containers so this isn't really a problem for me atm as long as my laptop still boots. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: zfs-dkms 0.6.5.6-0ubuntu6 ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6 Uname: Linux 4.4.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl ApportVersion: 2.20.1-0ubuntu1 Architecture: amd64 DKMSBuildLog: DKMS make.log for zfs-0.6.5.6 for kernel 4.4.0-18-generic (x86_64) Sat Apr 9 01:26:39 CDT 2016 make: *** No targets specified and no makefile found. Stop. DKMSKernelVersion: 4.4.0-18-generic Date: Sat Apr 9 01:26:42 2016 InstallationDate: Installed on 2016-02-28 (41 days ago) InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160224) PackageVersion: 0.6.5.6-0ubuntu6 RelatedPackageVersions: dpkg 1.18.4ubuntu1 apt 1.2.10 SourcePackage: zfs-linux Title: zfs-dkms 0.6.5.6-0ubuntu6: zfs kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: zfs-linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1568305 Title: zfs-dkms 0.6.5.6-0ubuntu6: zfs kernel module failed to build To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1568305/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1567807] [NEW] nova delete doesn't work with EFI booted VMs
Public bug reported: I've been setting up a Mitaka Openstack using the cloud archive running on Trusty, and am having problems working with EFI enabled instances on ARM64. I've done some work with wgrant and gotten things to a stage where I can boot instances, using the aavmf images. However, when I tried to delete a VM booted like this, I get an error: libvirtError: Requested operation is not valid: cannot delete inactive domain with nvram I've included the full traceback at https://paste.ubuntu.com/15682718/. Thanks to a suggestion from wgrant again, I got it working by editing nova/virt/libvirt/guest.py in delete_configuration() and replacing self._domain.undefineFlags(libvirt.VIR_DOMAIN_UNDEFINE_MANAGED_SAVE) with self._domain.undefineFlags(libvirt.VIR_DOMAIN_UNDEFINE_MANAGED_SAVE | libvirt.VIR_DOMAIN_UNDEFINE_NVRAM). I've attached a rough patch. Once that's applied and nova-compute restarted, I was able to delete the instance fine. Could someone please investigate this and see if its the correct fix, and look at getting it fixed in the archive? This was done on a updated trusty deployment using the cloud-archives for mitaka. $ dpkg-query -W python-nova python-nova 2:13.0.0~b2-0ubuntu1~cloud0 Please let me know if you need any further information. ** Affects: nova (Ubuntu) Importance: Undecided Status: New ** Tags: canonical-bootstack ** Attachment added: "nova-libvirt-fix-delete.patch" https://bugs.launchpad.net/bugs/1567807/+attachment/4628612/+files/nova-libvirt-fix-delete.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1567807 Title: nova delete doesn't work with EFI booted VMs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nova/+bug/1567807/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1555760] Re: Too many levels of symbolic links /proc/sys/fs/binfmt_misc
I'm not seeing the symbolic links error, but I am seeing this when trying to start a trusty container on xenial: https://github.com/lxc/lxd/issues/1836 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1555760 Title: Too many levels of symbolic links /proc/sys/fs/binfmt_misc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/binfmt-support/+bug/1555760/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1551897] Re: Excessive CPU utilization
I can work around this with my custom build of pcscd with udev disabled, but it seems that this issue will still affect Debian and Ubuntu users who install the package. Can we mark this bug as Confirmed, since my symptoms are so similar to the descriptions in the Debian bug[1] you've linked above? Anything else I can do to help? Thanks, Casey [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=812087 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1551897 Title: Excessive CPU utilization To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pcsc-lite/+bug/1551897/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1557345] Re: xenial juju 1.25.3 unable to deploy to lxc containers
Note these are freshly bootstrapped clouds, as per an irc conversation with alexisb and anastasiamac_. I took a working juju environment deploying to canonistack, just changed the default series, did a juju bootstrap and then a juju deploy local:xenial/ubuntu --to lxc:0, and got an error as above. I also confirmed that the bootstrap node had lxc installed when I first could log into it, before trying to deploy LXC to it: dpkubuntu@juju-bradm-lcy01-machine-0:~$ dpkg --list | grep lxc ii liblxc1 2.0.0~rc10-0ubuntu2 amd64 Linux Containers userspace tools (library) ii lxc 2.0.0~rc10-0ubuntu2 all Transitional package for lxc1 ii lxc-common 2.0.0~rc10-0ubuntu2 amd64 Linux Containers userspace tools (common tools) ii lxc-templates2.0.0~rc10-0ubuntu2 amd64 Linux Containers userspace tools (templates) ii lxc1 2.0.0~rc10-0ubuntu2 amd64 Linux Containers userspace tools ii lxcfs2.0.0~rc5-0ubuntu1 amd64 FUSE based filesystem for LXC ii python3-lxc 2.0.0~rc10-0ubuntu2 amd64 Linux Containers userspace tools (Python 3.x bindings) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1557345 Title: xenial juju 1.25.3 unable to deploy to lxc containers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1557345/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1557345] Re: xenial juju 1.25.3 unable to deploy to lxc containers
** Tags added: canonical-bootstack -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1557345 Title: xenial juju 1.25.3 unable to deploy to lxc containers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1557345/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1557345] [NEW] xenial juju 1.25.3 unable to deploy to lxc containers
Public bug reported: There appears to be some issue with deploying to lxc containers using juju 1.25.3 on Xenial. When deploying with xenial to canonistack-lcy02: bradm@serenity:~/src/juju$ juju deploy local:xenial/ubuntu --to lxc:0 Added charm "local:xenial/ubuntu-2" to the environment. ERROR adding new machine to host unit "ubuntu/1": cannot add a new machine: machine 0 cannot host lxc containers When deploying with trusty to canonistack-lcy02, the only change I made was to change the default-series from xenial to trusty: bradm@serenity:~/src/juju$ juju deploy local:trusty/ubuntu --to lxc:0 Added charm "local:trusty/ubuntu-1" to the environment. Versions used to deploy: $ juju --version 1.25.3-xenial-amd64 $ lsb_release -rd Description:Ubuntu Xenial Xerus (development branch) Release:16.04 Please let me know if you need any further information. ** Affects: juju-core (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1557345 Title: xenial juju 1.25.3 unable to deploy to lxc containers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1557345/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1557327] [NEW] kvm-ok script gives syntax error when running on kvm
Public bug reported: While debugging something, I ran the kvm-ok script on a VM running on openstack, and got an interesting error: ubuntu@juju-bradm-lcy02-machine-0:~$ sudo kvm-ok INFO: /dev/kvm does not exist HINT: sudo modprobe kvm_intel INFO: Your CPU supports KVM extensions /usr/sbin/kvm-ok: 120: /usr/sbin/kvm-ok: Syntax error: "else" unexpected (expecting "then") ubuntu@juju-bradm-lcy02-machine-0:~$ echo $? 2 The code in question just needs a ; then added at the end of it. Please let me know if you need any further information. $ dpkg-query -W cpu-checker cpu-checker 0.7-0ubuntu6 $ lsb_release -d Description:Ubuntu Xenial Xerus (development branch) ** Affects: cpu-checker (Ubuntu) Importance: Undecided Status: New ** Tags: canonical-bootstack -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1557327 Title: kvm-ok script gives syntax error when running on kvm To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cpu-checker/+bug/1557327/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1551854] Re: LXD bootstrap issues on xenial
Thanks for the fix. I didn't notice anything in particular that seemed to cause the issue. I do remember having the issue right after boot & desktop environment -- in some cases the first thing I did was start containers in a gnome terminal. Other things I did at various points last week: - Usual developer userspace stuff (tmux, vim, git, golang, juju). - Usual manager stuff (Google hangouts and drive) in firefox. - Messing with pcscd (build from source, etc) because of a bug where it consumes 100% CPU if I plug or unplug any USB device. - Messing with hdparm and smartctl because the power management burns through load cycle count on my x230 otherwise. - Built some debian packages for a release, uploaded to a launchpad PPA. - Daily package updates (update, dist-upgrade, autoremove). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1551854 Title: LXD bootstrap issues on xenial To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/1551854/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1551854] Re: LXD bootstrap issues on xenial
Haven't seen it in a few days. I'll reboot and see if I can reproduce it. It usually happens after rebooting the host, when launching new containers or existing ones would autostart. Info you requested. I think the /usr/share/lxc/... might have been a red herring. I'm exclusively using LXD on this xenial host, not messing with the old lxc commands. $ dpkg -l lxc liblxc1 lxd lxd-client lxcfs Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ NameVersion Architecture Description +++-===--- ii liblxc1 2.0.0~rc5-0ubuntu1 amd64 Linux Containers userspace tools (library) ii lxc 2.0.0~rc5-0ubuntu1 all Transitional package for lxc1 ii lxcfs 2.0.0~rc2-0ubuntu2 amd64 FUSE based filesystem for LXC ii lxd 2.0.0~rc1-0ubuntu3 amd64 Container hypervisor based on LXC - daemon ii lxd-client 2.0.0~rc1-0ubuntu3 amd64 Container hypervisor based on LXC - client $ lxc info apicompat: 0 auth: trusted environment: addresses: - 192.168.88.234:8443 - 192.168.122.1:8443 - 10.0.3.1:8443 architectures: - x86_64 - i686 certificate: | -BEGIN CERTIFICATE- MIIFqjCCA5KgAwIBAgIQXpne6Qjwhg8de+RmyV1+mTANBgkqhkiG9w0BAQsFADA6 MRwwGgYDVQQKExNsaW51eGNvbnRhaW5lcnMub3JnMRowGAYDVQQDDBFyb290QG1h d2hyaW4tc2tlbDAeFw0xNjAyMjgwMzEyMzdaFw0yNjAyMjUwMzEyMzdaMDoxHDAa BgNVBAoTE2xpbnV4Y29udGFpbmVycy5vcmcxGjAYBgNVBAMMEXJvb3RAbWF3aHJp bi1za2VsMIICIjANBgkqhkiG9w0BAQEFAAOCAg8AMIICCgKCAgEAzv/3uX3JWduq wmtbyTABmfJkup6Z5Lh4lKPXgL/H2gQ/mlccORKm1eDZhAGmv9UuQGeMRHEneJqD V9c3f7/9cJBwvz2loKlppWj0ohAzTP91L8paeUSfP4X9EAr702Qjyb2ig+xWv5tM cJxbdl0zGpjYO1P+xmUdthSidsFrzWQPXptOlcZvak7n0QL5GlkVXdqX+she2Pbs ONtyTaBSpF3zEYv6cM9ZeJYL4Hl7LEQ1/p8ojpOyaxO8B1Cn/gIbuDqgzRwmei90 Aca06YDF4SHVcl8qFajrwkPF3jWW5pgS8sAJlYoq2+ROhl0CnpdBl4AiJrvfFsIs RL8dKSuFA6AcLhYooWgMy6UWR8mLbmYHp04ThuBDoRaTt0uGLDlTAfMg7e8Gwpz+ aEwxSzzQhvJYr4e6TSP1C4zXNqS5mUHfm6RtfEccVFmq6vyqZGELAyREce76J88V FMf/V+KYlQYUxo0JH2k+BYMO4Iigar0+8p8o8drqh6Lks5zTP6idsKa0LSWA4rwm 3+5hjnVJtFa9CVCItJW3r0+nczwtAbjvRojkr7Yb2Kifufhilb+I695qSk+Toug3 HKOODTqc9sbH+urmfr7jBBexACtWVX/tMptWFnBmcqoN4ptSZutY7CPf+KR//9p0 8fFRQP+ItmElJHRFO+madGOBMVrC7j8CAwEAAaOBqzCBqDAOBgNVHQ8BAf8EBAMC BaAwEwYDVR0lBAwwCgYIKwYBBQUHAwEwDAYDVR0TAQH/BAIwADBzBgNVHREEbDBq ggxtYXdocmluLXNrZWyCETE5Mi4xNjguODguMjM0LzI0ghxmZTgwOjozZWE5OmY0 ZmY6ZmU1Njo0N2RjLzY0ggsxMC4wLjMuMS8yNIIcZmU4MDo6NThkNTpjMmZmOmZl ZTQ6NzJiYy82NDANBgkqhkiG9w0BAQsFAAOCAgEAB6aFItuxlZm5+2/IB2eCVAM0 eQbO6dfvfF2khfiEbWWaKPtkZSYKlDIcoOph35obnNMQjT+y4zlnF/fepvjq8P1R yGd+Q+GMcXWVRht3uIMW2ZqwNqOujunyn9+Hl1SYi1dV1g/CH9lJt8I7FKIvyieh siZRe5Zp7TdPREkIJveuz8qB3X87WVh9bqvMpoX91Mgrjzd3qATef/tN0HP+b26Y XjtRz9rhOkUfJx9b5HsyBLuGOQS979twl9LPKc1WsIrJaavY1JBT7SIwX3W7u7CU UWueEQoVvA9pkgeL8NXYYoHOkkrfW3oqExkuA1pqucMt8iRjn88njV57Vk576tjZ +bNqLL6R4xoUvnr9VIwq7tMLvodK/E5WvsmP5GrdMru2sa/xd+fS0137oOYqP4Qb T296jMcehHg5Gg1ZR1DbTqzWFPKb+CtXU+bqI68Hplq5Lemufsman2C2dthmKwcm OumpykWiH9vNKauY52VR8iffppBsH7jup1+yVtIOiT4Whp5LGBtZdYri7GE77qv+ qtBL7HdeBJxsBadRIfjdeLZlZPlMX7hV+v8Bzxz9fGuPKSnxDdpoPw1XF+zP1YAn VeDCRo7oCFV40nVFyb5wCreDoegtSFuQt7/Guv9u/gQSfmGoY1QyjlaHh2pJAAgS CPRGObnrdrQMMEqLDaI= -END CERTIFICATE- driver: lxc driverversion: 2.0.0.rc5 kernel: Linux kernelarchitecture: x86_64 kernelversion: 4.4.0-10-generic server: lxd serverpid: 2382 serverversion: 2.0.0.rc1 storage: zfs storageversion: "5" config: core.https_address: '[::]' storage.zfs_pool_name: lxdpool public: false -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1551854 Title: LXD bootstrap issues on xenial To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1551854/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1551897] Re: Excessive CPU utilization
Recompiling with --disable-libudev gets rid of the 100% CPU problem and I can still use my smartcard. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1551897 Title: Excessive CPU utilization To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pcsc-lite/+bug/1551897/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1551854] Re: LXD bootstrap issues on xenial
@stforshee I'll uncomment the debugfs mount in my
/usr/share/lxc/config/ubuntu.common.conf (putting it back the way it
was), reboot, and see if I can reproduce it again.
My juju-lxd profile shows:
name: juju-lxd
config:
boot.autostart: "true"
security.nesting: "true"
description: ""
devices: {}
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1551854
Title:
LXD bootstrap issues on xenial
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1551854/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1551854] Re: LXD bootstrap issues on xenial
Interesting. I removed the /sys/kernel/debug mount and containers seem to start up just fine: c@mawhrin-skel:~$ grep kernel/debug /usr/share/lxc/config/ubuntu.common.conf # lxc.mount.entry = /sys/kernel/debug sys/kernel/debug none bind,optional 0 0 c@mawhrin-skel:~$ lxc launch ubuntu-trusty t2 Creating t2 Starting t2 c@mawhrin-skel:~$ lxc exec t2 -- ps -ef UIDPID PPID C STIME TTY TIME CMD root 1 0 4 19:02 ?00:00:00 /sbin/init root 453 1 0 19:02 ?00:00:00 upstart-socket-bridge --daemon root 1507 1 0 19:02 ?00:00:00 upstart-udev-bridge --daemon root 1513 1 0 19:02 ?00:00:00 /lib/systemd/systemd-udevd --dae root 1583 1 0 19:02 ?00:00:00 dhclient -1 -v -pf /run/dhclient root 1606 1 0 19:02 ?00:00:00 /bin/sh /etc/network/if-up.d/ntp root 1610 1606 0 19:02 ?00:00:00 lockfile-touch /var/lock/ntpdate root 1619 1606 0 19:02 ?00:00:00 /usr/sbin/ntpdate -s ntp.ubuntu. root 1772 1 0 19:02 ?00:00:00 /bin/sh /etc/network/if-up.d/ntp message+ 1773 1 0 19:02 ?00:00:00 dbus-daemon --system --fork root 1775 1772 0 19:02 ?00:00:00 lockfile-create /var/lock/ntpdat root 1812 1 0 19:02 ?00:00:00 /lib/systemd/systemd-logind root 1864 1 0 19:02 ?00:00:00 cron daemon1866 1 0 19:02 ?00:00:00 atd root 1867 1 0 19:02 ?00:00:00 acpid -c /etc/acpi/events -s /va root 1870 1 0 19:02 ?00:00:00 /usr/sbin/irqbalance root 1886 1 0 19:02 ?00:00:00 /usr/sbin/sshd -D root 1910 1 0 19:02 ?00:00:00 upstart-file-bridge --daemon root 1925 1 0 19:02 ?00:00:00 /bin/sh /etc/init.d/ondemand bac root 1937 1925 0 19:02 ?00:00:00 sleep 60 syslog1943 1 2 19:02 ?00:00:00 rsyslogd root 2023 1 0 19:02 ?00:00:00 /usr/bin/python /usr/bin/cloud-i root 2025 0 0 19:02 ?00:00:00 ps -ef -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1551854 Title: LXD bootstrap issues on xenial To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1551854/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1551897] Re: Excessive CPU utilization
** Attachment added: "pcscd binary and core dump" https://bugs.launchpad.net/ubuntu/+source/pcsc-lite/+bug/1551897/+attachment/4588521/+files/pcscd-core-bin.tar.bz2 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1551897 Title: Excessive CPU utilization To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pcsc-lite/+bug/1551897/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1551897] Re: Excessive CPU utilization
Here's a core dump with the corresponding pcscd binary I built from source, which was taken in the above-mentioned gdb session. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1551897 Title: Excessive CPU utilization To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pcsc-lite/+bug/1551897/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1551897] Re: Excessive CPU utilization
Oh, here's /var/log/syslog from unplugging and replugging in my camera. I Ctrl-C killed pcscd after it went to 100% each time. pcscd segfaulted. Mar 4 12:04:11 mawhrin-skel pcscd: debuglog.c:289:DebugLogSetLevel() debug level=debug Mar 4 12:04:13 mawhrin-skel kernel: [14604.513268] usb 3-1: USB disconnect, device number 6 Mar 4 12:04:13 mawhrin-skel systemd[1]: Reloading Laptop Mode Tools. Mar 4 12:04:13 mawhrin-skel systemd[1]: Reloaded Laptop Mode Tools. Mar 4 12:04:13 mawhrin-skel laptop-mode: Laptop mode Mar 4 12:04:13 mawhrin-skel laptop_mode[17937]: Laptop mode Mar 4 12:04:13 mawhrin-skel laptop-mode: enabled, not active [unchanged] Mar 4 12:04:13 mawhrin-skel laptop_mode[17937]: enabled, not active [unchanged] Mar 4 12:04:53 mawhrin-skel systemd[1]: Starting Laptop Mode Tools - Battery Polling Service... Mar 4 12:04:53 mawhrin-skel systemd[1]: Reloading Laptop Mode Tools. Mar 4 12:04:53 mawhrin-skel systemd[1]: Started Laptop Mode Tools - Battery Polling Service. Mar 4 12:04:53 mawhrin-skel laptop-mode: Laptop mode Mar 4 12:04:53 mawhrin-skel laptop_mode[17997]: Laptop mode Mar 4 12:04:53 mawhrin-skel laptop-mode: enabled, not active [unchanged] Mar 4 12:04:53 mawhrin-skel laptop_mode[17997]: enabled, not active [unchanged] Mar 4 12:04:53 mawhrin-skel systemd[1]: Reloaded Laptop Mode Tools. Mar 4 12:05:01 mawhrin-skel CRON[18049]: (root) CMD ([ -x /usr/sbin/dma ] && /usr/sbin/dma -q1) Mar 4 12:05:17 mawhrin-skel kernel: [14668.018203] pcscd[17921]: segfault at 7f447696064c ip 7f447696064c sp 7f447694fed0 error 14 in libc-2.21.so[7f4476d85000+1c] Mar 4 12:05:20 mawhrin-skel pcscd: debuglog.c:289:DebugLogSetLevel() debug level=debug Mar 4 12:05:30 mawhrin-skel kernel: [14681.443071] usb 3-1: new high-speed USB device number 7 using xhci_hcd Mar 4 12:05:31 mawhrin-skel kernel: [14681.844167] usb 3-1: New USB device found, idVendor=046d, idProduct=0825 Mar 4 12:05:31 mawhrin-skel kernel: [14681.844175] usb 3-1: New USB device strings: Mfr=0, Product=0, SerialNumber=2 Mar 4 12:05:31 mawhrin-skel kernel: [14681.844179] usb 3-1: SerialNumber: DD923C60 Mar 4 12:05:31 mawhrin-skel kernel: [14681.845342] uvcvideo: Found UVC 1.00 device (046d:0825) Mar 4 12:05:31 mawhrin-skel kernel: [14681.937806] input: UVC Camera (046d:0825) as /devices/pci:00/:00:14.0/usb3/3-1/3-1:1.0/input/input19 Mar 4 12:05:32 mawhrin-skel kernel: [14683.279489] usb 3-1: set resolution quirk: cval->res = 384 Mar 4 12:05:32 mawhrin-skel mtp-probe: checking bus 3, device 7: "/sys/devices/pci:00/:00:14.0/usb3/3-1" Mar 4 12:05:32 mawhrin-skel mtp-probe: bus: 3, device: 7 was not an MTP device Mar 4 12:05:32 mawhrin-skel systemd[1]: Reloading Laptop Mode Tools. Mar 4 12:05:32 mawhrin-skel systemd[1]: Reloaded Laptop Mode Tools. Mar 4 12:05:32 mawhrin-skel systemd[1]: message repeated 3 times: [ Reloaded Laptop Mode Tools.] Mar 4 12:05:32 mawhrin-skel systemd-udevd[18064]: Process '/usr/sbin/alsactl -E HOME=/run/alsa restore 1' failed with exit code 99. Mar 4 12:05:32 mawhrin-skel laptop-mode: Laptop mode Mar 4 12:05:32 mawhrin-skel laptop_mode[18067]: Laptop mode Mar 4 12:05:32 mawhrin-skel laptop-mode: enabled, not active [unchanged] Mar 4 12:05:32 mawhrin-skel laptop_mode[18067]: enabled, not active [unchanged] Mar 4 12:05:32 mawhrin-skel pulseaudio[6720]: [pulseaudio] source.c: Default and alternate sample rates are the same. Mar 4 12:05:32 mawhrin-skel rtkit-daemon[6721]: Supervising 3 threads of 1 processes of 1 users. Mar 4 12:05:32 mawhrin-skel rtkit-daemon[6721]: Successfully made thread 18136 of process 6720 (n/a) owned by '1000' RT at priority 5. Mar 4 12:05:32 mawhrin-skel rtkit-daemon[6721]: Supervising 4 threads of 1 processes of 1 users. Mar 4 12:07:09 mawhrin-skel kernel: [14780.487379] pcscd[18060]: segfault at 7f74fedfa64c ip 7f74fedfa64c sp 7f74fede9ed0 error 14 in libc-2.21.so[7f74ff21f000+1c] Mar 4 12:07:43 mawhrin-skel systemd[1]: Starting Laptop Mode Tools - Battery Polling Service... Mar 4 12:07:43 mawhrin-skel systemd[1]: Reloading Laptop Mode Tools. Mar 4 12:07:43 mawhrin-skel systemd[1]: Started Laptop Mode Tools - Battery Polling Service. Mar 4 12:07:43 mawhrin-skel laptop-mode: Laptop mode Mar 4 12:07:43 mawhrin-skel laptop_mode[18161]: Laptop mode Mar 4 12:07:43 mawhrin-skel laptop-mode: enabled, not active [unchanged] Mar 4 12:07:43 mawhrin-skel laptop_mode[18161]: enabled, not active [unchanged] Mar 4 12:07:43 mawhrin-skel systemd[1]: Reloaded Laptop Mode Tools. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1551897 Title: Excessive CPU utilization To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pcsc-lite/+bug/1551897/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1551897] Re: Excessive CPU utilization
Ran it with gdb, reproduced, and then interrupted when it started consuming 100% CPU: Thread 1 "pcscd" received signal SIGINT, Interrupt. 0x774e2853 in select () from /lib/x86_64-linux-gnu/libc.so.6 (gdb) bt #0 0x774e2853 in select () from /lib/x86_64-linux-gnu/libc.so.6 #1 0x00411cfd in ProcessEventsServer (pdwClientID=pdwClientID@entry=0x7fffe49c) at winscard_msg_srv.c:223 #2 0x004037f9 in SVCServiceRunLoop () at pcscdaemon.c:128 #3 main (argc=, argv=) at pcscdaemon.c:685 (gdb) info threads Id Target Id Frame * 1Thread 0x77fb9740 (LWP 18298) "pcscd" 0x774e2853 in select () from /lib/x86_64-linux-gnu/libc.so.6 2Thread 0x76fb0700 (LWP 18302) "pcscd" 0x774e09ed in poll () from /lib/x86_64-linux-gnu/libc.so.6 3Thread 0x767af700 (LWP 18303) "pcscd" 0x774e09ed in poll () from /lib/x86_64-linux-gnu/libc.so.6 4Thread 0x75fae700 (LWP 18304) "pcscd" 0x774e09ed in poll () from /lib/x86_64-linux-gnu/libc.so.6 5Thread 0x757ad700 (LWP 18305) "pcscd" 0x774e09ed in poll () from /lib/x86_64-linux-gnu/libc.so.6 (gdb) thread 2 [Switching to thread 2 (Thread 0x76fb0700 (LWP 18302))] #0 0x774e09ed in poll () from /lib/x86_64-linux-gnu/libc.so.6 (gdb) bt #0 0x774e09ed in poll () from /lib/x86_64-linux-gnu/libc.so.6 #1 0x76fc064c in ?? () from /lib/x86_64-linux-gnu/libusb-1.0.so.0 #2 0x777b666a in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0 #3 0x774ec01d in clone () from /lib/x86_64-linux-gnu/libc.so.6 (gdb) thread 3 [Switching to thread 3 (Thread 0x767af700 (LWP 18303))] #0 0x774e09ed in poll () from /lib/x86_64-linux-gnu/libc.so.6 (gdb) bt #0 0x774e09ed in poll () from /lib/x86_64-linux-gnu/libc.so.6 #1 0x76fc064c in ?? () from /lib/x86_64-linux-gnu/libusb-1.0.so.0 #2 0x777b666a in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0 #3 0x774ec01d in clone () from /lib/x86_64-linux-gnu/libc.so.6 (gdb) thread 4 [Switching to thread 4 (Thread 0x75fae700 (LWP 18304))] #0 0x774e09ed in poll () from /lib/x86_64-linux-gnu/libc.so.6 (gdb) bt #0 0x774e09ed in poll () from /lib/x86_64-linux-gnu/libc.so.6 #1 0x76fb9bc5 in ?? () from /lib/x86_64-linux-gnu/libusb-1.0.so.0 #2 0x76fbab53 in libusb_handle_events_timeout_completed () from /lib/x86_64-linux-gnu/libusb-1.0.so.0 #3 0x76fbac3f in libusb_handle_events () from /lib/x86_64-linux-gnu/libusb-1.0.so.0 #4 0x771d64bc in ?? () from /usr/lib/pcsc/drivers/ifd-ccid.bundle/Contents/Linux/libccid.so #5 0x771d0b83 in ?? () from /usr/lib/pcsc/drivers/ifd-ccid.bundle/Contents/Linux/libccid.so #6 0x004064db in EHStatusHandlerThread (rContext=0x61f010) at eventhandler.c:464 #7 0x777b666a in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0 #8 0x774ec01d in clone () from /lib/x86_64-linux-gnu/libc.so.6 (gdb) thread 5 [Switching to thread 5 (Thread 0x757ad700 (LWP 18305))] #0 0x774e09ed in poll () from /lib/x86_64-linux-gnu/libc.so.6 (gdb) bt #0 0x774e09ed in poll () from /lib/x86_64-linux-gnu/libc.so.6 #1 0x0040eeaa in poll (__timeout=-1, __nfds=1, __fds=0x757aced0) at /usr/include/x86_64-linux-gnu/bits/poll2.h:46 #2 HPEstablishUSBNotifications (arg=0x649910) at hotplug_libudev.c:624 #3 0x777b666a in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0 #4 0x774ec01d in clone () from /lib/x86_64-linux-gnu/libc.so.6 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1551897 Title: Excessive CPU utilization To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pcsc-lite/+bug/1551897/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
