[Bug 1836964] [NEW] 18.04.2: cannot see Macbook Air 7, 1 NVMe partitions
Public bug reported: The kernel that comes with Kubuntu 18.04.1 is able to see the partitions on my Macbook Air 7,1 (mid-2015, 11.6")'s NVMe SSD. However, the kernel included in 18.04.2 cannot. If I check dmesg for the string "nvme" I get nvme nvme0: IO queues not created lspci can see the drive just fine. This seems to be an upstream issue because it also affects Debian Buster and Arch Linux. ** Affects: linux-signed-hwe (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/1836964 Title: 18.04.2: cannot see Macbook Air 7,1 NVMe partitions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe/+bug/1836964/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1836789] [NEW] After 19.04 upgrade: tigercron complains: , --ERROR-- [init001e] Don't have required command DIFF.
Public bug reported: After my upgrade to 19.04, I started to receive regular tigercron emails: --ERROR-- [init001e] Don't have required command DIFF. Perhaps this is a problem with the upgrade process. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: tiger 1:3.2.4~rc1-1 [modified: usr/lib/tiger/systems/default/config] ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8 Uname: Linux 5.0.0-20-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 Date: Tue Jul 16 10:37:09 2019 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: tiger UpgradeStatus: Upgraded to disco on 2019-05-14 (63 days ago) ** Affects: tiger (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug apport-hook-error disco -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1836789 Title: After 19.04 upgrade: tigercron complains: , --ERROR-- [init001e] Don't have required command DIFF. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tiger/+bug/1836789/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1836488] [NEW] After session unlock the login screen is still showing
Public bug reported: On my 19.04 ubuntu, I unlocked my session, but the login screen is still showing and covers everything else. The "Favorites" icons are showing and the top nav bar is also showing. I can "alt-tab", but the login screen permanently covering the entire screen. It shows the password field, and if I enter the password the login screen doesn't disappear. If I click "login as different user", I get to the real login screen, but after entering my password, it get to the stuck state I described earlier. So it appears the login manager (i'm not sure what it's called) is playing up. I pressed ctrl-alt-f3 and logged in via the TTY, and killed xorg, which was running at 100% CPU on one of my cores. This seemed to have resolved the problem. The downside was that it also closed all of my apps. I was running Android Studio with a emulated Nexus phone, not sure if that might have caused some problems. Please let me know what info I should gather if I see it again, and happy to post it up. ** Affects: sddm (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/1836488 Title: After session unlock the login screen is still showing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sddm/+bug/1836488/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1835928] Re: ``` GNU Image Manipulation Program version 2.10.12 git-describe: GIMP_2_10_10-209-g3d8535b55f C compiler: Using built-in specs. COLLECT_GCC=gcc COLLECT_LTO_WRAPPER=/usr/lib/gcc/i686-
¿Solucion? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1835928 Title: ``` GNU Image Manipulation Program version 2.10.12 git-describe: GIMP_2_10_10-209-g3d8535b55f C compiler: Using built-in specs. COLLECT_GCC=gcc COLLECT_LTO_WRAPPER=/usr/lib/gcc/i686-linux- gnu/7/lto-wrapper Target: i686-linux-gnu Configured with: ../src/configure -v --with-pkgversion='Ubuntu 7.4.0-1ubuntu1~18.04.1' --with-bugurl=file:///usr/share/doc/gcc-7/README.Bugs --enable- languages=c,ada,c++,go,brig,d,fortran,objc,obj-c++ --prefix=/usr --with-gcc-major-version-only --program-suffix=-7 --program- prefix=i686-linux-gnu- --enable-shared --enable-linker-build-id --libexecdir=/usr/lib --without-included-gettext --enable- threads=posix --libdir=/usr/lib --enable-nls --with-sysroot=/ --enable-clocale=gnu --enable-libstdcxx-debug --enable-libstdcxx- time=yes --with-default-libstdcxx-abi=new --enable-gnu-unique-object --disable-vtable-verify --enable-libmpx --enable-plugin --enable- default-pie --with-system-zlib --with-target-system-zlib --enable- objc-gc=auto --enable-targets=all --enable-multiarch --disable-werror --with-arch-32=i686 --with-multilib-list=m32,m64,mx32 --enable- multilib --with-tune=generic --enable-checking=release --build=i686 -linux-gnu --host=i686-linux-gnu --target=i686-linux-gnuThread model: posix gcc version 7.4.0 (Ubuntu 7.4.0-1ubuntu1~18.04.1) using GEGL version 0.4.16 (compiled against version 0.4.16) using GLib version 2.56.4 (compiled against version 2.56.4) using GdkPixbuf version 2.36.11 (compiled against version 2.36.11) using GTK+ version 2.24.32 (compiled against version 2.24.32) using Pango version 1.40.14 (compiled against version 1.40.14) using Fontconfig version 2.12.6 (compiled against version 2.12.6) using Cairo version 1.15.10 (compiled against version 1.15.10) ``` > fatal error: Abortado Stack trace: ``` /usr/lib/libgimpbase-2.0.so.0(gimp_stack_trace_print+0x353)[0xb78633c3] gimp-2.10(+0x91ab0)[0x4acab0] gimp-2.10(+0x92111)[0x4ad111] gimp-2.10(+0x927ec)[0x4ad7ec] linux- gate.so.1(__kernel_sigreturn+0x0)[0xb7f40d14] linux- gate.so.1(__kernel_vsyscall+0x9)[0xb7f40d09] /lib/i386-linux- gnu/libc.so.6(gsignal+0xc2)[0xb6bf5832] /lib/i386-linux- gnu/libc.so.6(abort+0x121)[0xb6bf6cc1] /lib/i386-linux- gnu/libc.so.6(+0x257bb)[0xb6bed7bb] /lib/i386-linux- gnu/libc.so.6(+0x25819)[0xb6bed819] /usr/lib/i386-linux- gnu/libX11.so.6(+0x36e17)[0xb6aade17] /usr/lib/i386-linux- gnu/libX11.so.6(+0x36f1a)[0xb6aadf1a] /usr/lib/i386-linux- gnu/libX11.so.6(_XEventsQueued+0x72)[0xb6aae312] /usr/lib/i386-linux- gnu/libX11.so.6(XPending+0x6b)[0xb6a9f95b] /usr/lib/i386-linux- gnu/libgdk-x11-2.0.so.0(+0x51778)[0xb7917778] /usr/lib/i386-linux- gnu/libglib-2.0.so.0(g_main_context_check+0x1a2)[0xb6f12be2] /usr/lib/i386-linux-gnu/libglib-2.0.so.0(+0x49201)[0xb6f13201] /usr/lib/i386-linux- gnu/libglib-2.0.so.0(g_main_loop_run+0xf9)[0xb6f136b9] gimp-2.10(app_run+0x36d)[0x4ac46d] gimp-2.10(main+0x374)[0x4abc44] /lib/i386-linux-gnu/libc.so.6(__libc_start_main+0xf1)[0xb6be0e81] gimp-2.10(+0x90e31)[0x4abe31] ``` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gimp/+bug/1835928/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1835857] Re: partclone.ext4 fails, but error message makes no sense
Please note that this run was done from the Xubuntu 18.04.2 install media. It may be a limitation of the environment set up by that software, in which case please consider this a feature request for the install media (I have no idea how to submit a bug against them, so I've got to do it this way). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1835857 Title: partclone.ext4 fails, but error message makes no sense To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/partclone/+bug/1835857/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1835928] [NEW] ``` GNU Image Manipulation Program version 2.10.12 git-describe: GIMP_2_10_10-209-g3d8535b55f C compiler: Using built-in specs. COLLECT_GCC=gcc COLLECT_LTO_WRAPPER=/usr/lib/gcc/i68
Public bug reported: Se crashea solo ya probé todas las versiones y se sigue crasheando :,( antes no me pasaba y derrepente, instale mi sistema de nuevo y no sigue igual ``` GNU Image Manipulation Program version 2.10.12 git-describe: GIMP_2_10_10-209-g3d8535b55f C compiler: Using built-in specs. COLLECT_GCC=gcc COLLECT_LTO_WRAPPER=/usr/lib/gcc/i686-linux-gnu/7/lto-wrapper Target: i686-linux-gnu Configured with: ../src/configure -v --with-pkgversion='Ubuntu 7.4.0-1ubuntu1~18.04.1' --with-bugurl=file:///usr/share/doc/gcc-7/README.Bugs --enable-languages=c,ada,c++,go,brig,d,fortran,objc,obj-c++ --prefix=/usr --with-gcc-major-version-only --program-suffix=-7 --program-prefix=i686-linux-gnu- --enable-shared --enable-linker-build-id --libexecdir=/usr/lib --without-included-gettext --enable-threads=posix --libdir=/usr/lib --enable-nls --with-sysroot=/ --enable-clocale=gnu --enable-libstdcxx-debug --enable-libstdcxx-time=yes --with-default-libstdcxx-abi=new --enable-gnu-unique-object --disable-vtable-verify --enable-libmpx --enable-plugin --enable-default-pie --with-system-zlib --with-target-system-zlib --enable-objc-gc=auto --enable-targets=all --enable-multiarch --disable-werror --with-arch-32=i686 --with-multilib-list=m32,m64,mx32 --enable-multilib --with-tune=generic --enable-checking=release --build=i686-linux-gnu --host=i686-linux-gnu --target=i686-linux-gnu Thread model: posix gcc version 7.4.0 (Ubuntu 7.4.0-1ubuntu1~18.04.1) using GEGL version 0.4.16 (compiled against version 0.4.16) using GLib version 2.56.4 (compiled against version 2.56.4) using GdkPixbuf version 2.36.11 (compiled against version 2.36.11) using GTK+ version 2.24.32 (compiled against version 2.24.32) using Pango version 1.40.14 (compiled against version 1.40.14) using Fontconfig version 2.12.6 (compiled against version 2.12.6) using Cairo version 1.15.10 (compiled against version 1.15.10) ``` > fatal error: Abortado Stack trace: ``` /usr/lib/libgimpbase-2.0.so.0(gimp_stack_trace_print+0x353)[0xb78633c3] gimp-2.10(+0x91ab0)[0x4acab0] gimp-2.10(+0x92111)[0x4ad111] gimp-2.10(+0x927ec)[0x4ad7ec] linux-gate.so.1(__kernel_sigreturn+0x0)[0xb7f40d14] linux-gate.so.1(__kernel_vsyscall+0x9)[0xb7f40d09] /lib/i386-linux-gnu/libc.so.6(gsignal+0xc2)[0xb6bf5832] /lib/i386-linux-gnu/libc.so.6(abort+0x121)[0xb6bf6cc1] /lib/i386-linux-gnu/libc.so.6(+0x257bb)[0xb6bed7bb] /lib/i386-linux-gnu/libc.so.6(+0x25819)[0xb6bed819] /usr/lib/i386-linux-gnu/libX11.so.6(+0x36e17)[0xb6aade17] /usr/lib/i386-linux-gnu/libX11.so.6(+0x36f1a)[0xb6aadf1a] /usr/lib/i386-linux-gnu/libX11.so.6(_XEventsQueued+0x72)[0xb6aae312] /usr/lib/i386-linux-gnu/libX11.so.6(XPending+0x6b)[0xb6a9f95b] /usr/lib/i386-linux-gnu/libgdk-x11-2.0.so.0(+0x51778)[0xb7917778] /usr/lib/i386-linux-gnu/libglib-2.0.so.0(g_main_context_check+0x1a2)[0xb6f12be2] /usr/lib/i386-linux-gnu/libglib-2.0.so.0(+0x49201)[0xb6f13201] /usr/lib/i386-linux-gnu/libglib-2.0.so.0(g_main_loop_run+0xf9)[0xb6f136b9] gimp-2.10(app_run+0x36d)[0x4ac46d] gimp-2.10(main+0x374)[0x4abc44] /lib/i386-linux-gnu/libc.so.6(__libc_start_main+0xf1)[0xb6be0e81] gimp-2.10(+0x90e31)[0x4abe31] ``` ** Affects: gimp (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/1835928 Title: ``` GNU Image Manipulation Program version 2.10.12 git-describe: GIMP_2_10_10-209-g3d8535b55f C compiler: Using built-in specs. COLLECT_GCC=gcc COLLECT_LTO_WRAPPER=/usr/lib/gcc/i686-linux- gnu/7/lto-wrapper Target: i686-linux-gnu Configured with: ../src/configure -v --with-pkgversion='Ubuntu 7.4.0-1ubuntu1~18.04.1' --with-bugurl=file:///usr/share/doc/gcc-7/README.Bugs --enable- languages=c,ada,c++,go,brig,d,fortran,objc,obj-c++ --prefix=/usr --with-gcc-major-version-only --program-suffix=-7 --program- prefix=i686-linux-gnu- --enable-shared --enable-linker-build-id --libexecdir=/usr/lib --without-included-gettext --enable- threads=posix --libdir=/usr/lib --enable-nls --with-sysroot=/ --enable-clocale=gnu --enable-libstdcxx-debug --enable-libstdcxx- time=yes --with-default-libstdcxx-abi=new --enable-gnu-unique-object --disable-vtable-verify --enable-libmpx --enable-plugin --enable- default-pie --with-system-zlib --with-target-system-zlib --enable- objc-gc=auto --enable-targets=all --enable-multiarch --disable-werror --with-arch-32=i686 --with-multilib-list=m32,m64,mx32 --enable- multilib --with-tune=generic --enable-checking=release --build=i686 -linux-gnu --host=i686-linux-gnu --target=i686-linux-gnuThread model: posix gcc version 7.4.0 (Ubuntu 7.4.0-1ubuntu1~18.04.1) using GEGL version 0.4.16 (compiled against version 0.4.16) using GLib version 2.56.4 (compiled against version 2.56.4) using GdkPixbuf version 2.36.11 (compiled against version 2.36.11) using GTK+ version
[Bug 1835857] Re: partclone.ext4 fails, but error message makes no sense
Here's the partclone log ** Attachment added: "partclone's own log" https://bugs.launchpad.net/ubuntu/+source/partclone/+bug/1835857/+attachment/5275751/+files/partclone.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1835857 Title: partclone.ext4 fails, but error message makes no sense To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/partclone/+bug/1835857/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1835857] [NEW] partclone.ext4 fails, but error message makes no sense
Public bug reported: I've got a 256GB partition, sparsely populated, and I want to clone it to a file on an empty 256GB thumb drive. It starts working, but fails with the message "ERROR: file too large". At that point, the thumb drive is just 4% full. I'll attach output of script(1) for the run as well as /var/log/partclone ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: partclone 0.3.11-1build1 ProcVersionSignature: Ubuntu 4.15.0-54.58-generic 4.15.18 Uname: Linux 4.15.0-54-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 Date: Mon Jul 8 20:09:41 2019 InstallationDate: Installed on 2018-10-18 (263 days ago) InstallationMedia: Xubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: partclone UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: partclone (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ** Attachment added: "script(1) output" https://bugs.launchpad.net/bugs/1835857/+attachment/5275747/+files/pc.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1835857 Title: partclone.ext4 fails, but error message makes no sense To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/partclone/+bug/1835857/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1832882] Re: libcurl-gnutls segfaults spotify client
Pardon my ignorance about the Launchpad bug metadata states, but: is there going to be an update for Ubuntu Disco fixing this issue? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1832882 Title: libcurl-gnutls segfaults spotify client To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/curl/+bug/1832882/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1833281] Re: Complete system freeze even when swapping small amounts of memory
Does this happen to you while using a web browser? This is my issue and it doesn't matter which browser or which kernel. Absolute garbage. Not sure what's happened with Ubuntu or why this is happening, but I'll try to figure out why since clearly I'm not the only person this is happening to and therefore it has nothing to do with my kernel updates. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1833281 Title: Complete system freeze even when swapping small amounts of memory To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1833281/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1830729] Re: package nfs-kernel-server 1:1.2.8-9ubuntu12.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
This bug affects me, but unsure of what exactly the bug is responsible for doing/not doing... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1830729 Title: package nfs-kernel-server 1:1.2.8-9ubuntu12.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/1830729/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1830825] [NEW] /usr/lib/tiger/systems/default/config misspells "export" as "expot"
Public bug reported: The file: /usr/lib/tiger/systems/default/config contains the following line: expot MAILE MD5SUM It should be "export", not "expot" ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: tiger 1:3.2.4~rc1-1 ProcVersionSignature: Ubuntu 5.0.0-15.16-generic 5.0.6 Uname: Linux 5.0.0-15-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: XFCE Date: Tue May 28 20:17:14 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2015-05-18 (1471 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) SourcePackage: tiger UpgradeStatus: Upgraded to disco on 2019-04-20 (39 days ago) ** Affects: tiger (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1830825 Title: /usr/lib/tiger/systems/default/config misspells "export" as "expot" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tiger/+bug/1830825/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1827167] [NEW] New version, current ver is badly outdated
Public bug reported: Current upstream version is 4.1.3, released in July 2018. Please update. ** Affects: angband (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/1827167 Title: New version, current ver is badly outdated To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/angband/+bug/1827167/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1826656] [NEW] dont know
Public bug reported: dont know ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: ubiquity 19.04.9 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CasperVersion: 1.405 Date: Sat Apr 27 12:36:03 2019 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed boot=casper quiet splash --- LiveMediaBuild: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) SourcePackage: grub-installer UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: grub-installer (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco ubiquity-19.04.9 ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1826656 Title: dont know To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1826656/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1826319] [NEW] Please upgrade cgdb to newest version (0.7.0)
Public bug reported: There's been an impressive list of changes between 0.6.7 and 0.7.0: https://github.com/cgdb/cgdb/compare/v0.6.7...v0.7.0 I'm particular interested in the new 256-color mode support. ** Affects: cgdb (Ubuntu) Importance: Undecided Status: New ** Tags: upgrade-software-version -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1826319 Title: Please upgrade cgdb to newest version (0.7.0) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cgdb/+bug/1826319/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1825580] Re: Gnome Online Accounts fails to sign in Exchange emails
I have submitted upstream: GNOME/gnome-online-accounts#60 Thanks for your attention to this! ** Bug watch added: gitlab.gnome.org/GNOME/gnome-online-accounts/issues #60 https://gitlab.gnome.org/GNOME/gnome-online-accounts/issues/60 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1825580 Title: Gnome Online Accounts fails to sign in Exchange emails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1825580/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1825580] Re: Gnome Online Accounts fails to sign in Exchange emails
https://gitlab.gnome.org/GNOME/gnome-online-accounts/issues/60 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1825580 Title: Gnome Online Accounts fails to sign in Exchange emails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1825580/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1825580] Re: Gnome Online Accounts fails to sign in Exchange emails
And on the one machine, the install of 18.10 had the EWS account working, then on upgrade it wouldn't connect--kept asking for the password even after entering multiple times. I deleted the account and tried to set up again, but it failed with this same error. On all of my installs (even fresh installs) the Microsoft Exchange option on Online Accounts appears with a red icon instead of the Exchange icon. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1825580 Title: Gnome Online Accounts fails to sign in Exchange emails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1825580/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1825580] Re: Gnome Online Accounts fails to sign in Exchange emails
The error is in the Online Accounts menu from the settings panel. The Error 7 appears as a red box over the account sign in window after I enter the same credentials and server address I used in 18.10. I tested this on Majaro, Pop_OS and Ubuntu with Gnome 3.32 and it happens on all of them, so seems to be related to Gnome itself. I believe we're on Exchange 2010 still. The account doesn't show up at all in Evolution since it never gets added to Online Accounts or Seahorse due to the error. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1825580 Title: Gnome Online Accounts fails to sign in Exchange emails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1825580/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1825580] Re: Gnome Online Accounts fails to sign in Exchange emails
Also seeing this: Apr 23 19:43:57 kevin-Dell-17 gnome-control-c[5696]: goa_ews_client_autodiscover() failed: 401 — Unauthorized Apr 23 19:44:52 kevin-Dell-17 gnome-control-c[5696]: goa_ews_client_autodiscover() failed: 401 — Unauthorized Apr 23 19:45:52 kevin-Dell-17 gnome-control-c[5696]: goa_ews_client_autodiscover() failed: 7 — Could not connect: Socket I/O timed out -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1825580 Title: Gnome Online Accounts fails to sign in Exchange emails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1825580/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1825580] Re: Gnome Online Accounts fails to sign in Exchange emails
Added journalctl full log on a new install. Let me know if there's more specific info I can look up or provide. ** Attachment added: "Full systemctl output" https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1825580/+attachment/5258377/+files/full_log.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1825580 Title: Gnome Online Accounts fails to sign in Exchange emails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1825580/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1825580] Re: Gnome Online Accounts fails to sign in Exchange emails
Added a log filtered for "goa-" items. Let me know if there's more specific info I can look up or provide. ** Attachment added: "Filtered for term goa-" https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1825580/+attachment/5258378/+files/goa.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1825580 Title: Gnome Online Accounts fails to sign in Exchange emails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1825580/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1739310] Re: Sound crackling in Ubuntu 16.04
tI've had this problem for a number of years on a range of Ubuntu distros; I'm currently working from an Ubuntu install that I switched over to Xubuntu after some graphics issues with the standard window manager. The problem can usually be triggered when I have too many tabs open while one of them is playing Youtube audio in a background tab. Because of this, I suspect there could be a memory allocation issue; tried increasing available browser memory, but since I really have no idea what the problem is, I figured I would post here as well. Let me know if you would like any diagnostic outputs or something similar. Attaching some hw info. Please let me know if you would like a different diagnostic output. ** Attachment added: "output of "arecord -L -l"" https://bugs.launchpad.net/ubuntu/+source/speech-dispatcher/+bug/1739310/+attachment/5257361/+files/sound.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1739310 Title: Sound crackling in Ubuntu 16.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/speech-dispatcher/+bug/1739310/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1825580] [NEW] Gnome Online Accounts fails to sign in Exchange emails
Public bug reported: After upgrading from 18.10 and/or on fresh install, a known-working Exchange email setup fails to sign in, giving "Error 7: Unexpected response from server". Tested the same settings and credentials on a new install of 18.10 and it worked. I have Evolution and Evolution-ews installed on all instances, working in 18.10, not in 19.04. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-online-accounts 3.32.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Apr 19 16:38:32 2019 InstallationDate: Installed on 2018-03-24 (391 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180208) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-online-accounts UpgradeStatus: Upgraded to disco on 2019-03-12 (38 days ago) ** Affects: gnome-online-accounts (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco third-party-packages -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1825580 Title: Gnome Online Accounts fails to sign in Exchange emails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1825580/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1793272] Re: latrace segfaults on armhf
This isn't just ARM. https://bugs.debian.org/cgi- bin/bugreport.cgi?bug=907308 ** Bug watch added: Debian Bug tracker #907308 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=907308 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1793272 Title: latrace segfaults on armhf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/latrace/+bug/1793272/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1823416] Re: runaway high memory usage in lxqt-session
** Attachment added: "massif visualizer chart" https://bugs.launchpad.net/ubuntu/+source/lxqt-session/+bug/1823416/+attachment/5253280/+files/lxqt-session-massif.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1823416 Title: runaway high memory usage in lxqt-session To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxqt-session/+bug/1823416/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1823416] [NEW] runaway high memory usage in lxqt-session
Public bug reported: lxqt-session had multiple gigabytes RSS memory. It seems to be related to what else is running at the time. In my case, it was playing a game. Similar report: https://github.com/lxqt/lxqt/issues/442 `valgrind --leak-check yes` didn't think these were unreachable leaks: ==29251== HEAP SUMMARY: ==29251== in use at exit: 579,390 bytes in 13,710 blocks ==29251== total heap usage: 761,288 allocs, 747,578 frees, 2,257,247,645 bytes allocated [...] ==29251== LEAK SUMMARY: ==29251==definitely lost: 10,392 bytes in 58 blocks ==29251==indirectly lost: 15,727 bytes in 209 blocks ==29251== possibly lost: 0 bytes in 0 blocks ==29251==still reachable: 553,271 bytes in 13,443 blocks ==29251== suppressed: 0 bytes in 0 blocks ==29251== Reachable blocks (those to which a pointer was found) are not shown. ==29251== To see them, rerun with: --leak-check=full --show-leak-kinds=all (those under-a-megabyte numbers are all much smaller than the gigabyte- size leak.) `valgrind --tool=massif` shows memory growth as linear, and reports most of it here: ntime(i) total(B) useful-heap(B) extra-heap(B)stacks(B) 81 10,818,324,1162,585,012,8402,575,948,310 9,064,5300 82 10,857,711,0512,593,973,7762,584,877,698 9,096,0780 99.65% (2,584,877,698B) (heap allocation functions) malloc/new/new[], --alloc-fns, etc. ->99.61% (2,583,820,288B) 0x59C7730: QArrayData::allocate(unsigned long, unsigned long, unsigned long, QFlags) (qarraydata.cpp:118) | ->98.95% (2,566,770,242B) 0x59C967E: QByteArray::QByteArray(int, Qt::Initialization) (qarraydata.h:222) | | ->98.95% (2,566,736,443B) 0x5A31700: QRingBuffer::reserve(long long) (qringbuffer_p.h:77) | | | ->98.95% (2,566,736,443B) 0x5B0880E: QProcessPrivate::tryReadFromChannel(QProcessPrivate::Channel*) (qprocess.cpp:1020) | | | ->98.95% (2,566,724,080B) 0x5B08CCE: QProcess::qt_static_metacall(QObject*, QMetaObject::Call, int, void**) (qprocess.cpp:1081) | | | | ->98.95% (2,566,724,080B) 0x5B986D9: QMetaObject::activate(QObject*, int, int, void**) (qobject.cpp:3771) | | | | ->98.95% (2,566,724,080B) 0x5BA3F17: QSocketNotifier::activated(int, QSocketNotifier::QPrivateSignal) (moc_qsocketnotifier.cpp:136) | | | | ->98.95% (2,566,724,080B) 0x5BA425F: QSocketNotifier::event(QEvent*) (qsocketnotifier.cpp:266) | | | | ->98.95% (2,566,724,080B) 0x4EA049F: QApplicationPrivate::notify_helper(QObject*, QEvent*) (qapplication.cpp:3727) | | | | ->98.95% (2,566,724,080B) 0x4EA7ADE: QApplication::notify(QObject*, QEvent*) (qapplication.cpp:3486) | | | | ->98.95% (2,566,724,080B) 0x5B6F497: QCoreApplication::notifyInternal2(QObject*, QEvent*) (qcoreapplication.cpp:1048) | | | | ->98.95% (2,566,724,080B) 0x5BC1D68: socketNotifierSourceDispatch(_GSource*, int (*)(void*), void*) (qcoreapplication.h:234) | | | | ->98.95% (2,566,724,080B) 0x76D8C3C: g_main_context_dispatch (gmain.c:3182) | | | | ->98.95% (2,566,724,080B) 0x76D8ED6: g_main_context_iterate.isra.26 (gmain.c:3920) | | | | ->98.95% (2,566,724,080B) 0x76D8F6A: g_main_context_iteration (gmain.c:3981) | | | | ->98.95% (2,566,719,959B) 0x5BC1141: QEventDispatcherGlib::processEvents(QFlags) (qeventdispatcher_glib.cpp:423) | | | | | ->98.95% (2,566,719,959B) 0xB471E4F: QPAEventDispatcherGlib::processEvents(QFlags) (qeventdispatcher_glib.cpp:69) | | | | | ->98.95% (2,566,719,959B) 0x5B6E169: QEventLoop::exec(QFlags) (qeventloop.cpp:214) | | | | | ->98.95% (2,566,719,959B) 0x5B762E0: QCoreApplication::exec() (qcoreapplication.cpp:1336) | | | | | ->98.95% (2,566,719,959B) 0x113C26: main (main.cpp:70) I'm not too familiar with Qt, so I'm not sure how to interpret that. It looks like an event handler but none of the functions named there are obviously part of this application. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: lxqt-session 0.13.0-0ubuntu2 ProcVersionSignature: Ubuntu 4.18.0-17.18-generic 4.18.20 Uname: Linux 4.18.0-17-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu13.2 Architecture: amd64 CurrentDesktop: LXQt Date: Fri Apr 5 16:21:53 2019 ExecutablePath: /usr/bin/lxqt-session InstallationDate: Installed on 2018-08-12 (236 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcEnviron: PATH=(custom, user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: lxqt-session UpgradeStatus: Upgraded to cosmic on 2018-11-28 (128 days ago) ** Affects: lxqt-session (Ubuntu) Importance: Undecided
[Bug 1822716] [NEW] [XPS 13 9350, Realtek ALC3246, Black Headphone Out, Front] No sound at all if headphones are plugged in before boot
Public bug reported: This is only an issue if the headphones are plugged in before boot. If I unplug/plug the headphone jack the audio works just fine. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18 Uname: Linux 4.15.0-46-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: strassek 1732 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Apr 1 21:53:00 2019 InstallationDate: Installed on 2018-05-12 (324 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm1309 F pulseaudio strassek 1732 F pulseaudio Symptom_Jack: Black Headphone Out, Front Symptom_Type: No sound at all Title: [XPS 13 9350, Realtek ALC3246, Black Headphone Out, Front] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/01/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.3 dmi.board.name: 0YT4WT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.3:bd03/01/2016:svnDellInc.:pnXPS139350:pvr:rvnDellInc.:rn0YT4WT:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 13 9350 dmi.sys.vendor: Dell Inc. ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1822716 Title: [XPS 13 9350, Realtek ALC3246, Black Headphone Out, Front] No sound at all if headphones are plugged in before boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1822716/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1812410] Re: Intel x550 not negotiating to 10Gb on x299 chipset
@Kevin (thenewmanium) Can you run and post the response on your system? ethtool -i and ethtool -k I'm opening up that ticket I had open with Intel again to see if we can some traction from that. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1812410 Title: Intel x550 not negotiating to 10Gb on x299 chipset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1812410/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1820755] Re: Netboot install fails due to linux-image-4.4.0-143-generic.postinst linux-update-symlinks not found
I just found https://bugs.launchpad.net/ubuntu/xenial/+source/linux/+bug/1820419 - seems like the same root cause and linux-image-4.4.0-145-generic mentioned there (in -proposed) worked as I had hoped above (it has a version check on the Depends: linux-base, which pulls in the needed script from xenial-updates -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1820755 Title: Netboot install fails due to linux-image-4.4.0-143-generic.postinst linux-update-symlinks not found To manage notifications about this bug go to: https://bugs.launchpad.net/bluelinux/+bug/1820755/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1820419] Re: linux-generic should depend on linux-base >=4.1
I'm not the original reporter, but I hit (and analyzed) what seems to be the same failure in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1820755 I just switched our packer template over to -proposed to test this: i.e. changed it to use http://archive.ubuntu.com/ubuntu/dists/xenial- proposed/main/installer- amd64/20101020ubuntu451.28/images/netboot/mini.iso, added apt- setup/proposed=true to the kernel command-line) and I can confirm that this runs to completion (whereas xenial- updates/current/images/netboot/mini.iso errors out. debootstrap still initially installs the original xenial version of linux-base (but that's expected, since debootstrap is unable to look at multiple repositories), but it eventually gets upgraded debootstrap: Preparing to unpack .../linux-base_4.0ubuntu1_all.deb ... debootstrap: Unpacking linux-base (4.0ubuntu1) ... ... debootstrap: Setting up linux-base (4.0ubuntu1) ... ... but later on (once base-installer is doing the kernel using the real in-target apt-get) it picks up the new kernel from xednial-proposed, and that prods it to pick up the new linux-base from xenial-updates ... in-target: The following additional packages will be installed: in-target: linux-base linux-headers-4.4.0-145 linux-headers-4.4.0-145-generic in-target: linux-headers-generic linux-headers-virtual linux-image-4.4.0-145-generic in-target: linux-image-virtual linux-modules-4.4.0-145-generic in-target: Suggested packages: in-target: fdutils linux-doc-4.4.0 | linux-source-4.4.0 linux-tools in-target: Recommended packages: in-target: grub-pc | grub-efi-amd64 | grub-efi-ia32 | grub | lilo in-target: The following NEW packages will be installed: in-target: linux-headers-4.4.0-145 linux-headers-4.4.0-145-generic in-target: linux-headers-generic linux-headers-virtual linux-image-4.4.0-145-generic in-target: linux-image-virtual linux-modules-4.4.0-145-generic linux-virtual in-target: The following packages will be upgraded: in-target: linux-base in-target: 1 upgraded, 8 newly installed, 0 to remove and 98 not upgraded. in-target: Need to get 29.8 MB of archives. in-target: After this operation, 146 MB of additional disk space will be used. in-target: Get:1 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 linux-base all 4.5ubuntu1~16.04.1 [18.1 kB] in-target: Get:2 http://archive.ubuntu.com/ubuntu xenial-proposed/main amd64 linux-headers-4.4.0-145 all 4.4.0-145.171 [10.0 MB] in-target: Get:3 http://archive.ubuntu.com/ubuntu xenial-proposed/main amd64 linux-headers-4.4.0-145-generic amd64 4.4.0-145.171 [820 kB] in-target: Get:4 http://archive.ubuntu.com/ubuntu xenial-proposed/main amd64 linux-headers-generic amd64 4.4.0.145.153 [2,568 B] in-target: Get:5 http://archive.ubuntu.com/ubuntu xenial-proposed/main amd64 linux-headers-virtual amd64 4.4.0.145.153 [1,760 B] in-target: Get:6 http://archive.ubuntu.com/ubuntu xenial-proposed/main amd64 linux-modules-4.4.0-145-generic amd64 4.4.0-145.171 [12.0 MB] in-target: Get:7 http://archive.ubuntu.com/ubuntu xenial-proposed/main amd64 linux-image-4.4.0-145-generic amd64 4.4.0-145.171 [6,919 kB] in-target: Get:8 http://archive.ubuntu.com/ubuntu xenial-proposed/main amd64 linux-image-virtual amd64 4.4.0.145.153 [2,694 B] in-target: Get:9 http://archive.ubuntu.com/ubuntu xenial-proposed/main amd64 linux-virtual amd64 4.4.0.145.153 [1,778 B] ... and it unpacks that first ... in-target: Preparing to unpack .../linux-base_4.5ubuntu1~16.04.1_all.deb ... in-target: in-target: Unpacking linux-base (4.5ubuntu1~16.04.1) over (4.0ubuntu1) ... ... in-target: Setting up linux-base (4.5ubuntu1~16.04.1) ... ...and the symlinks in postinst work ... in-target: Setting up linux-image-4.4.0-145-generic (4.4.0-145.171) ...^M in-target: I: /vmlinuz.old is now a symlink to boot/vmlinuz-4.4.0-145-generic^M in-target: I: /initrd.img.old is now a symlink to boot/initrd.img-4.4.0-145-generic^M in-target: I: /vmlinuz is now a symlink to boot/vmlinuz-4.4.0-145-generic^M in-target: I: /initrd.img is now a symlink to boot/initrd.img-4.4.0-145-generic^M in-target: Setting up linux-image-virtual (4.4.0.145.153) ...^M in-target: Setting up linux-virtual (4.4.0.145.153) ...^M So... I don't know if you need verification from the original reporter too, but it looks good to me. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1820419 Title: linux-generic should depend on linux-base >=4.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1820419/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1820755] Re: Netboot install fails due to linux-image-4.4.0-143-generic.postinst linux-update-symlinks not found
I finally came up with a workaround that can be done in a preseed.cfg (until this can be fixed properly in the kernel image) d-i preseed/early_command string echo -e "#!/bin/sh\napt-install linux- base" > /usr/lib/post-base-installer.d/99-bug1820755; chmod +x /usr/lib /post-base-installer.d/99-bug1820755 In other words, have the early command (which runs before base- installer) set up another post-base-installer callback hook, to upgrade linux-base. Since base-installer runs its post_install_hooks between apt_update and install_kernel, this can pick up the linux-base from xenial-updates, which will let the kernel install succeed. Seems to work for me and ends up with everything at the right versions in the end. That seems better than trying to hold back the linux- image-4.4.0-143-generic, which would leave you vulnerable to USN-3910-1 . -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1820755 Title: Netboot install fails due to linux-image-4.4.0-143-generic.postinst linux-update-symlinks not found To manage notifications about this bug go to: https://bugs.launchpad.net/bluelinux/+bug/1820755/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1812410] Re: Intel x550 not negotiating to 10Gb on x299 chipset
@Kevin (thenewmanium) Can you run and post the response on your system? ethtool -i and ethtool -k I'm opening up that ticket I had open with Intel again to see if we can some traction from that. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1812410 Title: Intel x550 not negotiating to 10Gb on x299 chipset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1812410/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1812410] Re: Intel x550 not negotiating to 10Gb on x299 chipset
I'm pushing on Dell to push on Intel. Not getting a lot of traction on that but I'll update if I do. Definitely have this issue on all my Dell R640s with X550s though. I also suspect the ixgbe module here. The kernel 4.4.0-141 version is 4.2.1. Going to Ubuntu's 4.15.0-43 kernel takes it to 5.1.0 where the 1Gb negotiation issue pops up. I also tried upgrading ixgbe to 5.5.5 and saw the same issue, so it isn't fixed yet or anything. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1812410 Title: Intel x550 not negotiating to 10Gb on x299 chipset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1812410/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1766851] Re: Missing `linux-update-symlinks` causes Linux package installation to fail
Related to #1820755 - although the new linux-base is now available in xenial-updates, the kernel packages do not version their depends to demand the new version, so apt-get will not necessarily install it (which causes base-installer to fail, since debootstrap will not have upgraded from xenial-updates prior to installing base- installer/kernel/image, and will not upgrade when the linux-image- generic Depends are already satisfied) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1766851 Title: Missing `linux-update-symlinks` causes Linux package installation to fail To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-base/+bug/1766851/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1820755] Re: Netboot install fails due to linux-image-4.4.0-143-generic.postinst linux-update-symlinks not found
Some more info: from http://changelogs.ubuntu.com/changelogs/pool/main/l /linux-base/linux-base_4.5ubuntu1~16.04.1/changelog, it looks like the actual cutoff would be Depends: linux-base (>= 4.1) On the question of workarounds, that confirms why pkgsel/upgrade didn't work, it's all in the base-installer udeb. The only hook point between apt-get update (where the new linux-base would be discovered) and the kernel (which currently assumes it's already installed) is the post_install_hooks call at https://salsa.debian.org/installer-team/base- installer/blob/master/debian/bootstrap-base.postinst#L188, which invokes scripts in /usr/lib/post-base-installer.d: https://salsa.debian.org /installer-team/base-installer/blob/master/library.sh#L265. And I find nothing in those hooks that would preseed can control. So I'm not finding any way around it except a fixed kernel package with the right (versioned) Depends on linux-base. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1820755 Title: Netboot install fails due to linux-image-4.4.0-143-generic.postinst linux-update-symlinks not found To manage notifications about this bug go to: https://bugs.launchpad.net/bluelinux/+bug/1820755/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1820755] Re: Netboot install fails due to linux-image-4.4.0-143-generic.postinst linux-update-symlinks not found
The missing linux-update-symlinks script seems like it's supposed to come from linux-base, which appears to exist with the same version number (4.5ubuntu1~16.04.1), yet different contents, in xenial (no linux-update-symlinks) and xenial-updates. It appears that this is because 4.5ubuntu1 is getting picked up from xenial-security, but the packages.ubuntu.com filelist isn't showing this; xenial actually seems to debootstrap 4.0, not 4.5ubuntu1~16.04.1. https://packages.ubuntu.com/xenial/all/linux-base/filelist https://packages.ubuntu.com/xenial-updates/all/linux-base/filelist https://launchpad.net/ubuntu/xenial/+source/linux-base So I *think* (just from first bit of this research, not from actually trying a fix) it might as simple as the linux-base dependency in linux- image-4.4.0-143 needing a version constraint >= 4.5, to force apt to upgrade linux-base first. That certainly seems appropriate in any case, as the script it's planning to call isn't in 4.0 package. The upgraded package is seemingly available (from security or from xenial-updates), but there's no constraint telling apt it must seek it out, and what it already has meets the stated dependency so it's just proceeding with it. As far as workarounds this theory might suggest, I'm not sure if there's a way to get d-i to include xenial-updates in the debootstrap sources so it would just get it the newer one in the first place (which would also avoid the redundancy of downloading/installing old versions and then immediately upgrading it). I had hoped that using `d-i pkgsel/upgrade safe-upgrade` might be another way to get it to install the upgraded linux-base before proceeding to the kernel, but it doesn't happen early enough. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1820755 Title: Netboot install fails due to linux-image-4.4.0-143-generic.postinst linux-update-symlinks not found To manage notifications about this bug go to: https://bugs.launchpad.net/bluelinux/+bug/1820755/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1692303] Re: Mouse over hints / tooltips show no text
Bug seems to be fixed with current version. I startet Inkscape and tested some mouse overs on the right button bar. I could read all "hints". I consider this fixed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1692303 Title: Mouse over hints / tooltips show no text To manage notifications about this bug go to: https://bugs.launchpad.net/inkscape/+bug/1692303/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1812410] Re: Intel x550 not negotiating to 10Gb on x299 chipset
@Kevin (thenewmanium). I honestly think this is a Intel driver bug. See my thread here on the Intel forums. https://forums.intel.com/s/question/0D50P4CK4wZSAT/intel-x550-not- negotiating-to-10gb-on-x299-chipset?language=en_US Their conclusion was that it was an Asus changed x550 chip. Asus said they won't fix it because they "don't support linux". Intel told me they won't do anything because Asus borked with the firmware. I'm basically stuck in the middle of two vendors not wanting to do anything because one doesn't support it and the other doesn't want to look at it because the other vendor changed it. If you can validate that its the same issue with different hardware, it might get some traction (fingers crossed). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1812410 Title: Intel x550 not negotiating to 10Gb on x299 chipset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1812410/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1812410] Re: Intel x550 not negotiating to 10Gb on x299 chipset
Hi, this issue affects my hosts as well. I have about 40 hosts running Intel X550s that were working fine on kernel 4.4.0-141-generic with regard to negotiating 10Gb automatically. Suddenly after booting into 4.15.0-43-generic they automatically negotiate at 1Gb. I have to use ethtool to force them to 10Gb. These are all Dell R640 so I don't think the issue is tied to the Asus x299. Seems more tightly correlated with the Intel X550 and the kernel version (4.15+ for me). I tried the 5.0-rc3 kernel you linked and the issue still exists there. So, somewhere between 4.4 and 4.13 the issue started and it still has not been fixed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1812410 Title: Intel x550 not negotiating to 10Gb on x299 chipset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1812410/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1801609] Re: Fails to deactivate dpms off mode after user initiated wake-up events(not system-suspended, just locked and dpms active)
A simple workaround (that worked for me at least): sudo apt install slick-greeter printf '[Seat:*]\ngreeter-session=slick-greeter\n' | sudo tee -a /etc/lightdm/lightdm.conf -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1801609 Title: Fails to deactivate dpms off mode after user initiated wake-up events(not system-suspended, just locked and dpms active) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1801609/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1794292] Re: plymouthd crashed with SIGSEGV in /sbin/plymouthd:11 in ply_renderer_set_handler_for_input_source -> ply_keyboard_stop_watching_for_renderer_input -> ply_keyboard_stop_watching_for_i
Hello! I've been having these crashes on two laptops nearly every reboot. I installed plymouth 0.9.3-1ubuntu10.1 from the -proposed repository on a fairly recently installed version 18.10 (cosmic) which contains no other proposed updates. So far, after rebooting many times, I'm happy to report that I am not seeing the error. Thanks to everyone who has been looking into this. Kevin -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1794292 Title: plymouthd crashed with SIGSEGV in /sbin/plymouthd:11 in ply_renderer_set_handler_for_input_source -> ply_keyboard_stop_watching_for_renderer_input -> ply_keyboard_stop_watching_for_input -> ply_device_manager_deactivate_keyboards -> on_deactivate To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1794292/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1821296] Re: light-locker blank screen until switching vt back and forth
This worked for me: sudo apt install slick-greeter printf '[Seat:*]\ngreeter-session=slick-greeter\n' | sudo tee -a /etc/lightdm/lightdm.conf (maybe that means this bug is actually in lightdm-gtk-greeter?) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1821296 Title: light-locker blank screen until switching vt back and forth To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/light-locker-settings/+bug/1821296/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1821296] [NEW] light-locker blank screen until switching vt back and forth
Public bug reported: After upgrading to Xubuntu 18.10, if I lock my screen (either win-L or on resume from suspend), the screen turns blank, but moving the mouse doesn't turn it back on. I have to switch vty back and forth (e.g. ctrl- alt-f1 ctrl-alt-f8) before I see the login screen again. It's been reported at https://github.com/the-cavalry/light- locker/issues/114 but I haven't found it in launchpad, so reporting here. ** Affects: light-locker-settings (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/1821296 Title: light-locker blank screen until switching vt back and forth To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/light-locker-settings/+bug/1821296/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1812754]
I have a better idea. Instead of inventing reasons for me to mess up my settings why don't YOU try to confirm it. I sent all the stuff you'd need to try this. If it does not add blank pages for you with whatever settings you have, go ahead and mark it invalid. If it _does_ add blank pages, mark it confirmed and go from there. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1812754 Title: Libreoffice writer adds blank pages on multiple inputs To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1812754/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1718658] Re: ecryptfs-mount-private fails to initialize ecryptfs keys
I would not trust ecryptfs anymore. https://bugs.launchpad.net/ubuntu/+source/ecryptfs-utils/+bug/1756840 Use the time to migrate your data. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1718658 Title: ecryptfs-mount-private fails to initialize ecryptfs keys To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ecryptfs-utils/+bug/1718658/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1812754]
Sorry, I do not have a spare machine to download the software. When I first reported this to Ubuntu I got immediate confirmation, and they suggested I re-submit to you. If you have the latest software, please give it a try. It will either fail or not in a hurry. Maybe 5 minutes max will any downloading and directory prep you decide to do. I set it back to unconfirmed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1812754 Title: Libreoffice writer adds blank pages on multiple inputs To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1812754/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1817410] Re: After last software update Huawei 3372H-153 modem is not working
to ttyUSB2' After (i.e. when it nolonger worked):- 'Feb 24 09:24:58 COMPUTER usb_modeswitch: switch device 12d1:1446 on 001/005 Feb 24 09:24:59 COMPUTER usb_modeswitch_dispatcher[2549]: Could not read attribute: No such file or directory Feb 24 09:24:59 COMPUTER usb_modeswitch[2549]: usb_modeswitch: switched to 12d1:1446 on 1/5 Feb 24 09:25:00 COMPUTER usb_modeswitch_dispatcher[2549]: Unable to open bind list file: No such file or directory Feb 24 09:25:00 COMPUTER kernel: [ 173.445398] usbcore: registered new interface driver usbserial Feb 24 09:25:00 COMPUTER kernel: [ 173.445415] usbcore: registered new interface driver usbserial_generic Feb 24 09:25:00 COMPUTER kernel: [ 173.445428] usbserial: USB Serial support registered for generic Feb 24 09:25:00 COMPUTER kernel: [ 173.475599] usbcore: registered new interface driver option Feb 24 09:25:00 COMPUTER kernel: [ 173.475618] usbserial: USB Serial support registered for GSM modem (1-port) Feb 24 09:25:00 COMPUTER usb_modeswitch[2549]: usb_modeswitch: add device ID 12d1:1446 to driver option Feb 24 09:25:00 COMPUTER usb_modeswitch[2549]: usb_modeswitch: please report the device ID to the Linux USB developers!' It seems to be a problem related to 'usb_modeswitch'. If you do a search on the internet then this seems to be a problem that continually reappears for various ubuntu versions over the last decade. Here is a short term solution I found that worked for me:- 1). Plug your dongle into usb port and wait until it indicates a signal has been detected. 2). Do a 'Ctrl-Alt-t' to get a terminal window up. 3). In terminal window type 'lsusb' and then hit return. 4). One of the entries in the output should read something like:- 'Bus 001 Device 004: ID 12d1:1446 Huawei Technologies Co., Ltd. Broadband stick (modem on)' 5). Make a note of the two hexidecimal numbers after the 'ID' i.e. in this example '12d1' and '1446'. 6). In the terminal window type:- 'sudo usb_modeswitch -v 12d1 -p 1446 -J' replacing the numbers after the '-v' and '-p' with the numbers you made a note of in step 5). above and hit return. 7). The output looks something like:- 'Look for default devices ... product ID matched Found devices in default mode (1) Access device 004 on bus 001 Current configuration number is 1 Use interface number 0 Use endpoints 0x01 (out) and 0x81 (in) USB description data (for identification) - Manufacturer: Huawei Technologies Product: HUAWEI Mobile Serial No.: not provided - Using standard Huawei switching message Looking for active driver ... OK, driver detached Set up interface 0 Use endpoint 0x01 for message sending ... Trying to send message 1 to endpoint 0x01 ... OK, message successfully sent Reset response endpoint 0x81 Reset message endpoint 0x01 Device is gone, skip any further commands -> Run lsusb to note any changes. Bye!' 8). In terminal window type 'lsusb' and then hit return. 9). The entry noted in step 4). above should now read something like:- 'Bus 001 Device 005: ID 12d1:1506 Huawei Technologies Co., Ltd. Modem/Networkcard' 10). The dongle interface should now appear in 'Network Tools' and you should be able to connect as usual. 11). You need to go through this everytime you reboot until an update fixes the bug. Not ideal but a life saver if you can only connect to the network using this device ! regards, Kevin Morgan -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1817410 Title: After last software update Huawei 3372H-153 modem is not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1817410/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1817496] [NEW] Login always shows partitions to be fsck-ed, even after reboot.
Public bug reported: This system reports /dev/sda5 will be checked on the next reboot. Maybe it is (it's EXT4 on as SSD drive, so it could be too fast to notice), but the message persists even after such a reboot. I would expect it to go away. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: login 1:4.5-1ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18 Uname: Linux 4.15.0-45-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 Date: Sun Feb 24 17:27:50 2019 SourcePackage: shadow UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: shadow (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1817496 Title: Login always shows partitions to be fsck-ed, even after reboot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/1817496/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: Ubuntu 18.04.1 LTS Server
Thank you for your reply Guilherme. I have decided to try your second
item and install version 4.15.0-43-generic.
Using google I have found the following commands:
sudo apt install
linux-{image,headers,modules,modules-extra}-4.15.0-43-generic
sudo apt-mark hold linux-*-4.15.0-4[45]-generic
sudo apt remove linux-*-4.15.0-4[45]-generic
I am not experienced with such matters and would appreciate your
comments. The only access I have into my server is via an insecure putty
application.
I apologize for seeking your advice on what must be basic maintenance
but your comments would be much appreciated.
Kevin Gordon.
On 18/02/2019 10:38, Guilherme Piccoli wrote:
Hi, the kernel with this fix for Bionic is present in the -proposed repository,
the version is 4.15.0-46-generic. To enable proposed packages, you
can check [0].
Alternatively, you can install version 4.15.0-43-generic, which does not
have the offending patches that caused the tty issue.
Cheers,
Guilherme
[0] https://wiki.ubuntu.com/Testing/EnableProposed
--
ubuntu-server mailing list
ubuntu-server@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server
More info: https://wiki.ubuntu.com/ServerTeam
[Bug 1816945] [NEW] failsafeXServer does not parse Xorg.failsafe.log correctly
Public bug reported: The timestamp for Xorg.failsafe.log has changed, and is no longer parsed correctly by failsafeXServer Here is a sample error message from syslog 2019-02-15T12:30:36.028591-08:00 awabi failsafeXServer[7805]: expr: non-integer argument 2019-02-15T12:30:36.028735-08:00 awabi failsafeXServer[7805]: /usr/share/xdiagnose/failsafeXServer: line 87: [: -lt: unary operator expected Currently, Xorg.failsafe.log looks like: [ 477.714] (II) Server terminated successfully (0). Closing log file. but failsafeXServer assumes that the date is seconds since 1970-01-01 00:00:00 UTC I have attached a patch which provides a solution to the problem. I look at the timestamp of the file, using %s, which provides seconds since 1970-01-01 00:00:00 UTC ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: xdiagnose 3.8.8 [modified: usr/share/xdiagnose/failsafeXServer] ProcVersionSignature: Ubuntu 4.18.0-15.16-generic 4.18.20 Uname: Linux 4.18.0-15-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.10-0ubuntu13.2 Architecture: amd64 CurrentDesktop: XFCE Date: Wed Feb 20 18:17:05 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2015-05-18 (1374 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) PackageArchitecture: all SourcePackage: xdiagnose UpgradeStatus: Upgraded to cosmic on 2018-11-01 (111 days ago) ** Affects: xdiagnose (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug cosmic ** Patch added: "Patch to failsafeXServer" https://bugs.launchpad.net/bugs/1816945/+attachment/5240463/+files/failsafeXServer.diff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1816945 Title: failsafeXServer does not parse Xorg.failsafe.log correctly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xdiagnose/+bug/1816945/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1816473] [NEW] obamenu depends on python2
Public bug reported: /usr/bin/obamenu in the openbox package requires Python 2, but the openbox package has no dependency on a python2 package. This causes an error dialog to pop up when selecting the Applications menu. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: openbox 3.6.1-7ubuntu0.1 ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18 Uname: Linux 4.15.0-42-generic i686 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: i386 Date: Mon Feb 18 14:08:37 2019 SourcePackage: openbox UpgradeStatus: Upgraded to bionic on 2018-12-16 (64 days ago) ** Affects: openbox (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug bionic i386 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1816473 Title: obamenu depends on python2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openbox/+bug/1816473/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Ubuntu 18.04.1 LTS Server
Ubuntu 18.04.1 LTS Server (GNU/Linux 4.15.0-45-generic x86_64) "Login Incorrect" repeated four times after entering user name. "Userspace break as a result of missing patch backport" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1813873 three kernels installed 4.15.0.39 4.15.0.44 4.15.0.45-generic. Is there a safe replacement for 4.15.0.45-generic? -- ubuntu-server mailing list ubuntu-server@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-server More info: https://wiki.ubuntu.com/ServerTeam
[Bug 1815727] Re: failed to install libreadline-dev
I just tried to install it and it worked on my new install. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1815727 Title: failed to install libreadline-dev To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/readline/+bug/1815727/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1815727] Re: failed to install libreadline-dev
im sorry it took so long to respond, i was using redline to build the new gnome but i ended up having to reinstall ubuntu so i dont have the information anymore -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1815727 Title: failed to install libreadline-dev To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/readline/+bug/1815727/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1815727] [NEW] failed to install libreadline-dev
Public bug reported: Ubuntu 18.10 was just supposed to install the package received this error sudo apt-get install libreadline-dev Reading package lists... Done Building dependency tree Reading state information... Done Suggested packages: readline-doc The following NEW packages will be installed: libreadline-dev 0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded. Need to get 0 B/133 kB of archives. After this operation, 728 kB of additional disk space will be used. (Reading database ... 210470 files and directories currently installed.) Preparing to unpack .../libreadline-dev_7.0-5_amd64.deb ... Unpacking libreadline-dev:amd64 (7.0-5) ... dpkg: error processing archive /var/cache/apt/archives/libreadline-dev_7.0-5_amd64.deb (--unpack): trying to overwrite '/usr/include/readline/chardefs.h', which is also in package readline-devel 6.2-11 dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) Errors were encountered while processing: /var/cache/apt/archives/libreadline-dev_7.0-5_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: libreadline-dev (not installed) Uname: Linux 4.20.7-042007-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Feb 13 01:51:22 2019 InstallationDate: Installed on 2019-02-11 (2 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: readline UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: readline (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug cosmic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1815727 Title: failed to install libreadline-dev To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/readline/+bug/1815727/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1812754] Re: Libreoffice writer adds blank pages on multiple inputs
Filed. https://bugs.documentfoundation.org/show_bug.cgi?id=123297 ** Bug watch added: Document Foundation Bugzilla #123297 https://bugs.documentfoundation.org/show_bug.cgi?id=123297 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1812754 Title: Libreoffice writer adds blank pages on multiple inputs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1812754/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1814593] Re: canonical-livepatch fails to install when logged in via SSH; cannot fix
make that "parser" not "piercer". LOL -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1814593 Title: canonical-livepatch fails to install when logged in via SSH; cannot fix To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1814593/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1814593] Re: canonical-livepatch fails to install when logged in via SSH; cannot fix
Yes. It's in /sbin/apparmor_piercer, and is in the path for root when I sudo to it, but not for ordinary users. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1814593 Title: canonical-livepatch fails to install when logged in via SSH; cannot fix To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1814593/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1814593] [NEW] canonical-livepatch fails to install when logged in via SSH; cannot fix
Public bug reported: It was apparently a mistake to try to get livepatch working when logged in via SSH (direct to root via secure key). I did it under script, so I have the log: snap install canonical-livepatch 0m?25hKerror:ocannot3performutheyfollowing0tasks:e"0m0m00m0m0m0m00m0m0m00m0m0m00m0m0m0m00m0m0m00m0m0100%013.7MB/s00.|ns0m - Setup snap "core" (6350) security profiles (cannot setup apparmor for snap "core": cannot create host snap-confine apparmor configuration: cannot reload snap-confine apparmor profile: cannot load apparmor profiles: exec: "apparmor_parser": executable file not found in $PATH apparmor_parser output: ) - Setup snap "core" (6350) security profiles (cannot create host snap-confine apparmor configuration: cannot reload snap-confine apparmor profile: cannot load apparmor profiles: exec: "apparmor_parser": executable file not found in $PATH apparmor_parser output: ) When I re-try logged in locally, using the indicated 'sudo' formula, the problem persists. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: snapd 2.37.1.1+18.04 ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18 Uname: Linux 4.15.0-45-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 Date: Mon Feb 4 13:53:10 2019 SourcePackage: snapd UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: snapd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1814593 Title: canonical-livepatch fails to install when logged in via SSH; cannot fix To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1814593/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1812758] Re: Boot failure on Dell Precision 5820 with Intel Xeon W-2123 CPU
What status should this bug be moved to? Obviously there is something fishy going on with Intel VMD being enabled, but I'm not using it so it doesn't impact me in this case. Should I get any logs to assist in figuring out why enabling VMD causes the system not boot properly? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1812758 Title: Boot failure on Dell Precision 5820 with Intel Xeon W-2123 CPU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1812758/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1812758] Re: Boot failure on Dell Precision 5820 with Intel Xeon W-2123 CPU
I was able to install 18.04 without issue. It looks like the solution to disable "Intel VMD Technology" in the BIOS solved the issue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1812758 Title: Boot failure on Dell Precision 5820 with Intel Xeon W-2123 CPU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1812758/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1813495] FW: Submit Request Failure
-Original Message- From: boun...@canonical.com [mailto:boun...@canonical.com] On Behalf Of nore...@bugs.launchpad.net Sent: 28 January 2019 17:46 To: ke...@talktalk.net Subject: Submit Request Failure An error occurred while processing a mail you sent to Launchpad's email interface. Error message: The message you sent included commands to modify the bug report, but you didn't sign the message with an OpenPGP key that is registered in Launchpad. -- For more information about using Launchpad by email, see https://help.launchpad.net/EmailInterface or send an email to h...@launchpad.net Hi Robie I am new to ubuntu and followed the error report sending that poped up when trying to install the package and trying to follow the how to do them and set them up thank you for your help on this Kev -Original Message- From: boun...@canonical.com [mailto:boun...@canonical.com] On Behalf Of Robie Basak Sent: 28 January 2019 15:50 To: ke...@talktalk.net Subject: [Bug 1813495] Re: package mysql-server-5.7 5.7.25-0ubuntu0.18.04.2 failed to install/upgrade: installed mysql-server-5.7 package post-installation script subprocess returned error exit status 127 Thank you for your report. This looks like a local configuration problem, rather than a bug in Ubuntu. Specifically, you have an incompatible version of mysql-common installed that was not shipped by Ubuntu, so other related packages cannot be expected to work correctly. You can find pointers to get help for this sort of problem here: http://www.ubuntu.com/support/community Since we use this bug tracker to track bugs in Ubuntu, rather than configuration problems, I'm marking this bug as Invalid. This helps us to focus on fixing bugs in Ubuntu. If you believe that this is really a bug, then you may find it helpful to read "How to report bugs effectively" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem, explain why you believe this is a bug in Ubuntu rather than a problem specific to your system, and then change the bug status back to New. ** Changed in: mysql-5.7 (Ubuntu) Status: New => Invalid -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1813495 Title: package mysql-server-5.7 5.7.25-0ubuntu0.18.04.2 failed to install/upgrade: installed mysql-server-5.7 package post-installation script subprocess returned error exit status 127 Status in mysql-5.7 package in Ubuntu: Invalid Bug description: error happened when tring to set up mqsl for a nextclould server with apacie2 ProblemType: Package DistroRelease: Ubuntu 18.04 Package: mysql-server-5.7 5.7.25-0ubuntu0.18.04.2 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 Date: Sun Jan 27 19:01:02 2019 DuplicateSignature: package:mysql-server-5.7:5.7.25-0ubuntu0.18.04.2 Setting up mysql-server-5.7 (5.7.25-0ubuntu0.18.04.2) ... /var/lib/dpkg/info/mysql-server-5.7.postinst: line 191: /usr/share/mysql-common/configure-symlinks: No such file or directory dpkg: error processing package mysql-server-5.7 (--configure): installed mysql-server-5.7 package post-installation script subprocess returned error exit status 127 ErrorMessage: installed mysql-server-5.7 package post-installation script subprocess returned error exit status 127 InstallationDate: Installed on 2019-01-24 (3 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Logs.var.log.daemon.log: MySQLConf.etc.mysql.mysql.conf.d.mysqld_safe_syslog.cnf: [mysqld_safe] syslog MySQLVarLibDirListing: [] ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic root=UUID=ed3db3d4-237c-4a8e-a52f-56e85f5867d6 ro quiet splash vt.handoff=1 Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 3.6.7-1~18.04 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2.1 apt 1.6.6ubuntu0.1 SourcePackage: mysql-5.7 Title: package mysql-server-5.7 5.7.25-0ubuntu0.18.04.2 failed to install/upgrade: installed mysql-server-5.7 package post-installation script subprocess returned error exit status 127 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-5.7/+bug/1813495/+subscriptions -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1813495 Title: package mysql-server-5.7 5.7.25-0ubuntu0.18.04.2 failed to install/upgrade: installed mysql-server-5.7 package post-installation script subprocess returned error exit status 127 To manage notifications about this bug go to:
[Bug 1813495] [NEW] package mysql-server-5.7 5.7.25-0ubuntu0.18.04.2 failed to install/upgrade: installed mysql-server-5.7 package post-installation script subprocess returned error exit status 127
Public bug reported: error happened when tring to set up mqsl for a nextclould server with apacie2 ProblemType: Package DistroRelease: Ubuntu 18.04 Package: mysql-server-5.7 5.7.25-0ubuntu0.18.04.2 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 Date: Sun Jan 27 19:01:02 2019 DuplicateSignature: package:mysql-server-5.7:5.7.25-0ubuntu0.18.04.2 Setting up mysql-server-5.7 (5.7.25-0ubuntu0.18.04.2) ... /var/lib/dpkg/info/mysql-server-5.7.postinst: line 191: /usr/share/mysql-common/configure-symlinks: No such file or directory dpkg: error processing package mysql-server-5.7 (--configure): installed mysql-server-5.7 package post-installation script subprocess returned error exit status 127 ErrorMessage: installed mysql-server-5.7 package post-installation script subprocess returned error exit status 127 InstallationDate: Installed on 2019-01-24 (3 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Logs.var.log.daemon.log: MySQLConf.etc.mysql.mysql.conf.d.mysqld_safe_syslog.cnf: [mysqld_safe] syslog MySQLVarLibDirListing: [] ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic root=UUID=ed3db3d4-237c-4a8e-a52f-56e85f5867d6 ro quiet splash vt.handoff=1 Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 3.6.7-1~18.04 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2.1 apt 1.6.6ubuntu0.1 SourcePackage: mysql-5.7 Title: package mysql-server-5.7 5.7.25-0ubuntu0.18.04.2 failed to install/upgrade: installed mysql-server-5.7 package post-installation script subprocess returned error exit status 127 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: mysql-5.7 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package bionic third-party-packages -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1813495 Title: package mysql-server-5.7 5.7.25-0ubuntu0.18.04.2 failed to install/upgrade: installed mysql-server-5.7 package post-installation script subprocess returned error exit status 127 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-5.7/+bug/1813495/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1160650] Re: cannot detect IPv6 scanner
At some point along the line this bug has been fixed: kjotte@mystic:/tmp/sane-backends-1.0.27/backend$ grep -n gethostbyname pixma* kjotte@mystic:/tmp/sane-backends-1.0.27/backend$ grep -n getaddrinfo pixma* pixma_bjnp.c:849: if (getaddrinfo(host , service, NULL, ) == 0) pixma_bjnp.c:1714: result = getaddrinfo (host, port, , ); Tested with same scanner in IPv6 only mode. Discovery and scanning are working correctly. Manual specification with pixma.conf of a device with record also appears succesful: $ scanimage -L device `pixma:MX870_gonzo' is a CANON Canon PIXMA MX870 multi-function peripheral ** Changed in: sane-backends (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1160650 Title: cannot detect IPv6 scanner To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1160650/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1812758] Re: Boot failure on Dell Precision 5820 with Intel Xeon W-2123 CPU
I had some luck with Dell after I told them to give me a different machine. Finally got in touch with someone with Dell support that checked their knowledge base. There is an option in the Dell BIOS that has to do with "Intel VMD Technology". The solution that Dell provided was to disable the VMD feature (e.g.mark it as disabled) and in the PCIE Devices list: uncheck all devices and reboot. After doing that, 16.04 and 18.04 now seem to boot without any kernel flags (as long as the nouveau driver supports the card). I'm still doing testing to make sure that this is a work around where the machine will see all devices instead of just 1 core. Will report back with the results. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1812758 Title: Boot failure on Dell Precision 5820 with Intel Xeon W-2123 CPU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1812758/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1812758] Re: Boot failure on Dell Precision 5820 with Intel Xeon W-2123 CPU
@Kai-Heng Feng (kaihengfeng) It does not have an integrated GPU. I've tried several other GPUs. I've done the installation with nomodeset kernel parameters and noapci and a few others. Got it to install, installed the GPU drivers, however it still wouldn't boot properly/consistently without parameters such as noapci. Unfortunately, adding noapci causes the system to only detect 1 CPU core. I'm going to try and get some more logs. I honestly feel this is some type of regression. @TJ (tj) So the information you posted about the certification from Dell is on 16.04.1. If I create a boot media with that version, the machine boots without problem, however 16.04.1 doesn't have new enough drivers to support the on board NIC card. As soon as I upgrade to 16.04.2+ things start breaking. I'm going to try and work on this today and see if I can produce some kernel logs. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1812758 Title: Boot failure on Dell Precision 5820 with Intel Xeon W-2123 CPU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1812758/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1812758] [NEW] Boot failure on Dell Precision 5820 with Intel Xeon W-2123 CPU
Public bug reported: So I'm trying to install Ubuntu 16.04.5 (happens on 18.04 as well) on a Dell Precision 5820 with a GTX 1080 in it. These machines are lease refreshes. I created a UEFI image of 16.04.5, selected "Install Ubuntu" and then starts throwing a bunch of error messages stating [33.192238] nouveau :05:00.0: DRM: base-0: timeout repeating over and over again. It never gets past this. I tried the suggestions of adding "nomodeset" in grub when I'm booting. It progresses a little further but hangs at "failed to start Ubuntu Installation Service, please run journalctl to see what failed". I can't see what failed as I can't get a prompt since nothing is installed. I don't know where to go debug from here. My computer boots to a black screen, what options do I have to fix it? Graphics issues after/while installing Ubuntu 16.04/16.10 with NVIDIA graphics Ubuntu 16.04 Installation Issue Boots Into Black Screen or Freezes - Nouveau/Nvidia Driver issue 1080ti Ubuntu 16.04 installation blank screen Ubuntu 16.04 unable to boot with GTX 1080 etc. However, I tried Ubuntu 16.04.1 LTS and did NOT have the issues with the video and was successfully able to install Ubuntu 16.04.1. Unfortunately, 16.04.1 didn't support the integrated Intel i219-LM network card. I tried 16.04.2, 16.04.3, 16.04.4 and they all exhibit the same behavior as 16.04.5 with the video. Just as a test, I installed 16.04.1, installed broadcom NIC (which was successfully detected), and upgraded from 16.04.1 --> 16.04.5 with apt- get and had no video issues after reboot (I didn't install the video drivers), in addition, after it was upgraded to 16.04.5 the Intel 219-LM drivers were added and would work. I have a workaround, but it's REALLY annoying. The kicker in this is that the Dell Precision 5810 worked 100% correctly. Put the USB boot drive in, select the drive in UEFI to boot and everything works out of the box. I'm working on gathering more logs of this issue and testing different kernel versions. ** Affects: linux (Ubuntu) Importance: Undecided Assignee: TJ (tj) Status: In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1812758 Title: Boot failure on Dell Precision 5820 with Intel Xeon W-2123 CPU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1812758/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1812758] Re: Boot failure on Dell Precision 5820 with Intel Xeon W-2123 CPU
A workaround...but not a complete work around... So I do believe I figured out a "solution" but it literally makes zero sense and indicates a problem with the Dell BIOS and potentially some oversight in the kernel? Built 16.04.5 Desktop image with Rufus 3.3.1400. Partition Scheme: MBR Target system: BIOS (or UEFI-CSM) All other options default. 1.0 So with the computer in UEFI Boot, Secure boot off. Hit F12 to get into "One time boot menu". In the "One time boot menu" you can select "Legacy" and UEFI boot options (e.g. USB Boot Device under legacy menu, and then under UEFI it shows the devices one being this Kingston USB device as a boot option). 1.1 In the UEFI Boot mode if you select the UEFI device, the system will not boot as describe above, no combination of nomodeset, acpi=off, noapci will work. The system hangs at a blinking cursor or in some type of error code as listed above. 1.2 In the UEFI boot mode if you select the USB boot drive under LEGACY, it boots into the selection screen correctly of (Install Ubuntu, Try Ubuntu, etc. menu). You will have to add the F6 options of nomodeset, acpi=off, noapci and then select the "Install Ubuntu" option and then the important part...YOU CANNOT BE USING ONE OF THE DISPLAY PORTS ON THE VIDEO CARD, YOU HAVE TO BE USING THE DVI PORT! At this point you will have the Desktop installer functioning. I didn't really like this "solution" since you would have to be using the DVI port, so I dug some more... 2.0 I switched the machine into "LEGACY BOOT MODE, SECURE BOOT MODE OFF". In the one time boot option (when you hit F12 during POST) the boot menu will still show "LEGACY Boot Options" and "UEFI Boot Options". The same as before. However the results are different. 2.1 While in LEGACY boot mode in the one time boot option if you select the USB boot drive under LEGACY you get the SAME interaction as what I stated in 1.2. (e.g. to get the Installer Desktop GUI to show you have to add the nomodeset, acpi=off, noapci flags and then be plugged into the DVI port) 2.2 This is where it gets fun...while in LEGACY boot mode, select the USB boot device under the UEFI menu. The "Try Ubuntu, Install Ubuntu menu option shows", hit 'e' to edit the boot string, add the "nomodeset" flag hit F10, AND IT BOOTS CORRECTLY, with the DisplayPorts. So why is this stupid? The computer has to be IN LEGACY BOOT MODE AND you must select the boot option from the UEFI menu. Which makes literally zero sense. Why would I need to put the computer in LEGACY mode to only select the boot option from the UEFI menu. You have to add the nomodeset option as well, but the options you have to select are quite absurd to me. So for anyone running into this with BIOS 1.8 in a Dell Precision 5820. Create USB drive that will boot in UEFI mode. You can use Rufus that will boot in UEFI mode or Legacy mode, but I doubt this matters. Set the computer to LEGACY BOOT MODE (THIS IS IMPORTANT) When the computer is posting hit F12 to enter in the one time boot menu. Select the USB device to boot from WITHIN the UEFI menu (you will see both). Highlight the "Install Ubuntu" option and hit 'e'. On the "Linux" line before the "---" change the line to be "[...] nomodeset ---" Hit F10 to boot and you will get the Desktop installation menu. Reading material: https://access.redhat.com/solutions/58790 https://bugs.freedesktop.org/show_bug.cgi?id=105319 The only problem with this is that with noacpi enabled the OS only sees a single core, which is obviously a problem. ** Bug watch added: freedesktop.org Bugzilla #105319 https://bugs.freedesktop.org/show_bug.cgi?id=105319 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1812758 Title: Boot failure on Dell Precision 5820 with Intel Xeon W-2123 CPU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1812758/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1812754] [NEW] Libreoffice writer adds blank pages on multiple inputs
Public bug reported: When I have multiple .txt files on the command line and start libreoffice writer, it adds (many) blank pages to the documents. These blanks contain nothing at all and I have not figured out how to remove them. But they are included when I print them. I'm attaching a file on which this happens. It contains an anonymized fragment of the original, repeates a number of times. I suggest you create two copies, called perhaps junk1.txt and junk2.txt. I use the command "soffice junk*" to load them into the writer, and I get the extra blank pages. If, however, I just do soffice junk1.txt, I get a document of the correct size. I can do that of course, but it is still an annoying and inconvenient error for my workflow. --- One hint to debugging: if I do this: for i in junk1.txt junk2.txt do soffice $i & done I see the problem. If, however, I introduce a delay the problem does not appear. Like so: for i in junk1.txt junk2.txt do sleep 2 soffice $i & done ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libreoffice-writer 1:6.0.7-0ubuntu0.18.04.2 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: XFCE Date: Mon Jan 21 13:58:01 2019 InstallationDate: Installed on 2018-10-18 (95 days ago) InstallationMedia: Xubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: libreoffice (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ** Attachment added: "file that exibits the problem" https://bugs.launchpad.net/bugs/1812754/+attachment/5231229/+files/junk1.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1812754 Title: Libreoffice writer adds blank pages on multiple inputs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1812754/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1812410] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1812410/+attachment/5230379/+files/WifiSyslog.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/1812410 Title: Intel x550 not negotiating to 10Gb on x299 chipset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1812410/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1812410] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1812410/+attachment/5230376/+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/1812410 Title: Intel x550 not negotiating to 10Gb on x299 chipset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1812410/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1812410] AudioDevicesInUse.txt
apport information ** Attachment added: "AudioDevicesInUse.txt" https://bugs.launchpad.net/bugs/1812410/+attachment/5230368/+files/AudioDevicesInUse.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1812410 Title: Intel x550 not negotiating to 10Gb on x299 chipset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1812410/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1812410] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1812410/+attachment/5230372/+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/1812410 Title: Intel x550 not negotiating to 10Gb on x299 chipset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1812410/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1812410] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1812410/+attachment/5230378/+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/1812410 Title: Intel x550 not negotiating to 10Gb on x299 chipset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1812410/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1812410] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1812410/+attachment/5230373/+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/1812410 Title: Intel x550 not negotiating to 10Gb on x299 chipset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1812410/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1812410] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1812410/+attachment/5230377/+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/1812410 Title: Intel x550 not negotiating to 10Gb on x299 chipset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1812410/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1812410] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1812410/+attachment/5230371/+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/1812410 Title: Intel x550 not negotiating to 10Gb on x299 chipset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1812410/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1812410] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1812410/+attachment/5230375/+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/1812410 Title: Intel x550 not negotiating to 10Gb on x299 chipset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1812410/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1812410] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1812410/+attachment/5230369/+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/1812410 Title: Intel x550 not negotiating to 10Gb on x299 chipset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1812410/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1812410] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1812410/+attachment/5230370/+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/1812410 Title: Intel x550 not negotiating to 10Gb on x299 chipset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1812410/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1812410] Re: Intel x550 not negotiating to 10Gb on x299 chipset
apport information ** Tags added: apport-collected bionic ** Description changed: I am having an issue with this particular machine auto negotiating 10Gb. The onboard LOM will only negotiate to 1Gb. If I run `ethtool -s advertise 0x1000`, the machine will delink and then negotiate to 10Gb and work as expecting. Rebooting the machine (or unplugging network cable) will cause it to negotiate to 1G again resulting in having to run the ethtool command again. This is what I have tried: Tried different cable from confirmed working machine that auto negotiates to 10Gb. Tried upgrading ixgbe driver to latest (5.5.3) Tried upgrading X550 firmware. I put an Intel x540-T1 card in the machine and that card works properly and negotiates to 10Gb automatically. Move the cable to the LOM x550, and it still negotiates to 1Gb. I also tried loading a live version of Fedora 29 (Kernel 4.18) with same exact symptoms. We have several other machine negotiating fine on the same exact switch. I have tried those cables to test this problematic machine with same result as above. We have a machine that is pretty similar in hardware that is not exhibiting this issue. It is an ASUS x99 motherboard, with the same LOM Intel x550 card, running on 16.04. The machine that is causing problems is an Asus x299 motherboard with the Intel x550 LOM card running 18.04 (16.04 won't work on the x299 chipset for some reason). I have a suspicion that it could potentially be related to the x299? The only way I have been able to get this problematic machine to negotiate to 10Gbps automatically is by plugging a cable directly from the LOM x550 of the problematic machine to another machines 10Gb network card. Doing that, the problematic machine will negotiate properly to 10Gb. I'm trying to find another 10Gb switch to test with to see if it could be unique to this combination of switch and machine. However, I'm reluctant to blame it on the switch since we have about several other machine working perfectly fine on the switch (some with the same exact x550 LOM). Other notes: - https://serverfault.com/questions/949006/intel-x550-not-negotiating-to- - 10gb?noredirect=1#comment1233436_949006 + https://serverfault.com/questions/949006/intel-x550-not-negotiating-to-10gb?noredirect=1#comment1233436_949006 + --- + ProblemType: Bug + ApportVersion: 2.20.9-0ubuntu7.5 + Architecture: amd64 + DistroRelease: Ubuntu 18.04 + InstallationDate: Installed on 2018-12-14 (34 days ago) + InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) + IwConfig: + enp179s0f1 no wireless extensions. + + lono wireless extensions. + + enp179s0f0 no wireless extensions. + MachineType: System manufacturer System Product Name + NonfreeKernelModules: nvidia_modeset nvidia + Package: linux (not installed) + ProcEnviron: + TERM=xterm + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash + ProcFB: 0 EFI VGA + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic root=UUID=7e94e4fd-ff67-46c2-9b58-3f7bb3840be4 ro quiet splash vt.handoff=1 + ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 + RelatedPackageVersions: + linux-restricted-modules-4.15.0-43-generic N/A + linux-backports-modules-4.15.0-43-generic N/A + linux-firmware 1.173.3 + RfKill: + + Tags: bionic + Uname: Linux 4.15.0-43-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo + _MarkForUpload: True + dmi.bios.date: 11/30/2018 + dmi.bios.vendor: American Megatrends Inc. + dmi.bios.version: 0905 + dmi.board.asset.tag: Default string + dmi.board.name: WS X299 SAGE/10G + dmi.board.vendor: ASUSTeK COMPUTER INC. + dmi.board.version: Rev 1.xx + dmi.chassis.asset.tag: Default string + dmi.chassis.type: 3 + dmi.chassis.vendor: Default string + dmi.chassis.version: Default string + dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0905:bd11/30/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnWSX299SAGE/10G:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: + dmi.product.family: To be filled by O.E.M. + dmi.product.name: System Product Name + dmi.product.version: System Version + dmi.sys.vendor: System manufacturer ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1812410/+attachment/5230367/+files/AlsaInfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1812410 Title: Intel x550 not negotiating to 10Gb on x299 chipset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1812410/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1812410] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1812410/+attachment/5230374/+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/1812410 Title: Intel x550 not negotiating to 10Gb on x299 chipset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1812410/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1812410] Re: Intel x550 not negotiating to 10Gb on x299 chipset
adding additional log information ** Attachment added: "modinfo_ixgbe.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1812410/+attachment/5230330/+files/modinfo_ixgbe.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1812410 Title: Intel x550 not negotiating to 10Gb on x299 chipset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1812410/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1812410] [NEW] Intel x550 not negotiating to 10Gb on x299 chipset
Public bug reported: I am having an issue with this particular machine auto negotiating 10Gb. The onboard LOM will only negotiate to 1Gb. If I run `ethtool -s advertise 0x1000`, the machine will delink and then negotiate to 10Gb and work as expecting. Rebooting the machine (or unplugging network cable) will cause it to negotiate to 1G again resulting in having to run the ethtool command again. This is what I have tried: Tried different cable from confirmed working machine that auto negotiates to 10Gb. Tried upgrading ixgbe driver to latest (5.5.3) Tried upgrading X550 firmware. I put an Intel x540-T1 card in the machine and that card works properly and negotiates to 10Gb automatically. Move the cable to the LOM x550, and it still negotiates to 1Gb. I also tried loading a live version of Fedora 29 (Kernel 4.18) with same exact symptoms. We have several other machine negotiating fine on the same exact switch. I have tried those cables to test this problematic machine with same result as above. We have a machine that is pretty similar in hardware that is not exhibiting this issue. It is an ASUS x99 motherboard, with the same LOM Intel x550 card, running on 16.04. The machine that is causing problems is an Asus x299 motherboard with the Intel x550 LOM card running 18.04 (16.04 won't work on the x299 chipset for some reason). I have a suspicion that it could potentially be related to the x299? The only way I have been able to get this problematic machine to negotiate to 10Gbps automatically is by plugging a cable directly from the LOM x550 of the problematic machine to another machines 10Gb network card. Doing that, the problematic machine will negotiate properly to 10Gb. I'm trying to find another 10Gb switch to test with to see if it could be unique to this combination of switch and machine. However, I'm reluctant to blame it on the switch since we have about several other machine working perfectly fine on the switch (some with the same exact x550 LOM). Other notes: https://serverfault.com/questions/949006/intel-x550-not-negotiating-to- 10gb?noredirect=1#comment1233436_949006 ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Attachment added: "version.log" https://bugs.launchpad.net/bugs/1812410/+attachment/5230328/+files/version.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1812410 Title: Intel x550 not negotiating to 10Gb on x299 chipset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1812410/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1812410] Re: Intel x550 not negotiating to 10Gb on x299 chipset
adding additional log information. ** Attachment added: "lcpci-vnvn.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1812410/+attachment/5230329/+files/lcpci-vnvn.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1812410 Title: Intel x550 not negotiating to 10Gb on x299 chipset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1812410/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1812410] Re: Intel x550 not negotiating to 10Gb on x299 chipset
adding additional log information ** Attachment added: "ethtool_output.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1812410/+attachment/5230332/+files/ethtool_output.txt ** Description changed: I am having an issue with this particular machine auto negotiating 10Gb. The onboard LOM will only negotiate to 1Gb. If I run `ethtool -s advertise 0x1000`, the machine will delink and then negotiate to 10Gb and work as expecting. Rebooting the machine (or unplugging network cable) will cause it to negotiate to 1G again resulting in having to run the ethtool command again. This is what I have tried: Tried different cable from confirmed working machine that auto negotiates to 10Gb. Tried upgrading ixgbe driver to latest (5.5.3) - Tried upgrading X550 firmware. - I put an Intel x540-T1 card in the machine and that card works properly and negotiates to 10Gb automatically. Move the cable to the LOM x550, and it still negotiates to 1Gb. + Tried upgrading X550 firmware. + I put an Intel x540-T1 card in the machine and that card works properly and negotiates to 10Gb automatically. Move the cable to the LOM x550, and it still negotiates to 1Gb. + I also tried loading a live version of Fedora 29 (Kernel 4.18) with same exact symptoms. We have several other machine negotiating fine on the same exact switch. I have tried those cables to test this problematic machine with same result as above. We have a machine that is pretty similar in hardware that is not exhibiting this issue. It is an ASUS x99 motherboard, with the same LOM Intel x550 card, running on 16.04. The machine that is causing problems is an Asus x299 motherboard with the Intel x550 LOM card running 18.04 (16.04 won't work on the x299 chipset for some reason). I have a suspicion that it could potentially be related to the x299? The only way I have been able to get this problematic machine to negotiate to 10Gbps automatically is by plugging a cable directly from the LOM x550 of the problematic machine to another machines 10Gb network card. Doing that, the problematic machine will negotiate properly to 10Gb. I'm trying to find another 10Gb switch to test with to see if it could be unique to this combination of switch and machine. However, I'm reluctant to blame it on the switch since we have about several other machine working perfectly fine on the switch (some with the same exact x550 LOM). - Other notes: https://serverfault.com/questions/949006/intel-x550-not-negotiating-to- 10gb?noredirect=1#comment1233436_949006 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1812410 Title: Intel x550 not negotiating to 10Gb on x299 chipset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1812410/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1772677] Re: gnome-shell filling up syslog with thousands of entries with stack traces ending in osdWindow.js (lines 206/207 in bionic, lines 223/224 in cosmic)
One other bit of info I thought about that could be contributing is my horizontal monitor is hooked up to a cheap 4 port HDMI switch (not a true KVM switch, it's HDMI only). This seems to cause the monitor to flicker back and forth during boot / loading the splash page as it looks (to my untrained eye) like it can't decide if the HDMI is hooked up to a monitor or not. Once the login page is displayed though that particular problem is gone until the next boot. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1772677 Title: gnome-shell filling up syslog with thousands of entries with stack traces ending in osdWindow.js (lines 206/207 in bionic, lines 223/224 in cosmic) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1772677/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1772677] Re: gnome-shell filling up syslog with thousands of entries with stack traces ending in osdWindow.js (lines 206/207 in bionic, lines 223/224 in cosmic)
I just got hit with this bug as well. Fresh Ubuntu 18.10 install on a Desktop (Ryzen 2995x, 32GB RAM, Vega 64, 250GB NVMe /, and 1TB Evo 860 SSD /home) with two monitors (1 vertical using DP, and one horizontal using HDMI), only thing I did post install was install a few flatpaks from flathub (Discord, Telegram, VSCode, Slack), and a snap (CLion) as well as a Rust toolchain (https://rustup.rs). Went to bed, went to work the next morning, and when I came up the computer appeared to be frozen as it wouldn't wake from sleep. After a hard reset and login, I noticed I couldn't do an update do to "disk full". Checked `df` and saw `/` was full. Quick checking of dirs lead to `/var/log/syslog` being 230GB from a single night/day of no use! My plan is to do a re-install (with Kubuntu which is what it was prior to this install), however if there is something else I can provide that would help track down this bug I will (assuming I see a message prior to the nuke/pave). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1772677 Title: gnome-shell filling up syslog with thousands of entries with stack traces ending in osdWindow.js (lines 206/207 in bionic, lines 223/224 in cosmic) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1772677/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1511840] Re: cannot apport-bug from IPv6-only network
I no longer receive the "Network is unreachable" message from the command-line tool, so that part is fixed. I was unable to test the complete workflow of reporting a bug because login.launchpad.net does not have records therefore the browser window that was opened died in its tracks. I realize that's yet another infrastructure bug. Thanks for moving 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/1511840 Title: cannot apport-bug from IPv6-only network To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1511840/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1796119] Re: docker-compose should not require golang-github-docker-docker-credential-helpers package
FWIW. I had 4 Bionic installs that just had docker-ce installed from the repo along with pip docker and this issue hit me. These hosts did not have docker-compose installed. I just had to `apt -y remove golang-docker- credential-helpers; pip install docker` to get it to work via command line or saltstack state apply. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1796119 Title: docker-compose should not require golang-github-docker-docker- credential-helpers package To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/docker-compose/+bug/1796119/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1810216] [NEW] Unable to run do-release-upgrade under script(1) because of a need to clear the screen
Public bug reported: I like to do system updates under script(1) and have a collection of bash aliases to do these things and log the script output. Otherwise all that stuff scrolls by with no chance for me to use it later. I just tried to update my system to 18.04, and it failed with the following output: Checking for a new Ubuntu release Get:1 Upgrade tool signature [819 B] Get:2 Upgrade tool [1,263 kB] Fetched 1,264 kB in 0s (0 B/s) authenticate 'bionic.tar.gz' against 'bionic.tar.gz.gpg' extracting 'bionic.tar.gz' Clear screen capability required. This seems onerous to me. What's the point of generating output if there's no way to learn from it, refer to it, or remember it? ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: ubuntu-release-upgrader-core 1:16.04.26 ProcVersionSignature: Ubuntu 4.4.0-141.167-generic 4.4.162 Uname: Linux 4.4.0-141-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CrashDB: ubuntu Date: Tue Jan 1 14:18:02 2019 InstallationDate: Installed on 2016-08-08 (876 days ago) InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader UpgradeStatus: Upgraded to xenial on 2019-01-01 (0 days ago) ** Affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug dist-upgrade xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1810216 Title: Unable to run do-release-upgrade under script(1) because of a need to clear the screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1810216/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1809407] Re: [nvidia] After resume the unlock screen is a black background with pixel garbage. Bitmap garbage flashes on the screen when interacting with anything.
I did some random trial and error debugging. There's always a login screen on console 1 and there's always a desktop GUI on console 2. It's sometimes waking from sleep into display 2 while still locked. There's a dock, a system menu, and random bitmap garbage. Hitting CTRL-ALT-F1 goes to the login screen. After logging in, it jumps to a normally working display 2. Not sure if it's related: CTRL-ALT-fkey is sometimes generating app keyboard events rather than switching consoles. Installing 18.04 completely corrupted my system and I had wipe the disk. This isn't an old crusty installation. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1809407 Title: [nvidia] After resume the unlock screen is a black background with pixel garbage. Bitmap garbage flashes on the screen when interacting with anything. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1809407/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1809407] [NEW] No unlock screen
Public bug reported: Every other wake from sleep presents a corrupted screen with no unlock app. There's a dock and system menu on a black background with pixel garbage. Some personal information in the dock's large window thumbnails. Bitmap garbage flashes on the screen when interacting with anything. Only workaround is doing another sleep-wake cycle. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: xorg 1:7.7+19ubuntu8 ProcVersionSignature: Ubuntu 4.18.0-12.13-generic 4.18.17 Uname: Linux 4.18.0-12-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..4b.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:4b:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.87 Tue Aug 21 12:33:05 PDT 2018 GCC version: gcc version 8.2.0 (Ubuntu 8.2.0-7ubuntu1) ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Dec 20 22:19:29 2018 DistUpgraded: 2018-12-01 23:07:50,385 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8)) DistroCodename: cosmic DistroVariant: ubuntu DkmsStatus: nvidia, 390.87, 4.18.0-11-generic, x86_64: installed nvidia, 390.87, 4.18.0-12-generic, x86_64: installed virtualbox, 5.2.18, 4.18.0-11-generic, x86_64: installed virtualbox, 5.2.18, 4.18.0-12-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation GP106 [GeForce GTX 1060 3GB] [10de:1c02] (rev a1) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. GP106 [GeForce GTX 1060 3GB] [3842:6162] InstallationDate: Installed on 2018-10-28 (54 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Gigabyte Technology Co., Ltd. Default string ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-12-generic root=UUID=a8c839e7-c579-4699-999a-748f804ff9e0 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to cosmic on 2018-12-02 (18 days ago) dmi.bios.date: 06/08/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F24 dmi.board.asset.tag: Default string dmi.board.name: X99P-SLI-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF24:bd06/08/2017:svnGigabyteTechnologyCo.,Ltd.:pnDefaultstring:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnX99P-SLI-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: Default string dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug cosmic ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1809407 Title: No unlock screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1809407/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1804910] Re: pip3 cannot install gmpy
I wasn't aware of gmpy2. Installing it has solved this issue for me. On Sun, Nov 25, 2018 at 9:20 AM Hans Joachim Desserud < 1804...@bugs.launchpad.net> wrote: > Thanks for reporting. > > I'm a bit confused to the issue. Though I am not familiar with gmpy, it > looks like there are two versions of it available in Ubuntu, gmpy and > gmpy2. While the former doesn't have a python3 package, the latter one > does and this seems to be the maintained version too. That would be > installable through `sudo apt install python3-gmpy2` > (https://packages.ubuntu.com/bionic/python3-gmpy2). > > If for some reason the Ubuntu package doesn't fit or you really need to > use the older gmpy version in combination with Python3 i suppose that might > be why the script attempt to install via pip3 instead of apt. Based on the > error message: > In file included from src/gmpy.c:251:0: > src/gmpy.h:30:10: fatal error: gmp.h: No such file or directory >#include "gmp.h" > ^~~ > compilation terminated. > error: command 'x86_64-linux-gnu-gcc' failed with exit status 1 > it looks like it was fetched, but failed to compile while installing. > Some python packages contain C/C++ code to speed up certain parts and looks > like this is one of them. It might be missing some build dependencies, > which perhaps `sudo apt build-dep python-gmpy` (for gmpy1) or `sudo apt > build-dep python-gmpy2` (for gmpy2, though in that case it is probably > easier to use the existing python3-gmpy2 package as described above) > > > ** Changed in: python3-defaults (Ubuntu) >Status: New => Incomplete > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1804910 > > Title: > pip3 cannot install gmpy > > Status in python3-defaults package in Ubuntu: > Incomplete > > Bug description: > I'm using python3 and want gmpy. Attempts to install it fail. > > I routinely capture the output of maintenance tasks, and am attaching > the results. This output begins with the text of the shell script I > wrote to do this, which includes calls to the bash functions I wrote > to do this self-referential magic. > > ProblemType: Bug > DistroRelease: Ubuntu 18.04 > Package: python3 3.6.7-1~18.04 > ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18 > Uname: Linux 4.15.0-39-generic x86_64 > ApportVersion: 2.20.9-0ubuntu7.5 > Architecture: amd64 > Date: Fri Nov 23 17:44:44 2018 > InstallationDate: Installed on 2018-10-18 (36 days ago) > InstallationMedia: Xubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 > (20180725) > SourcePackage: python3-defaults > UpgradeStatus: No upgrade log present (probably fresh install) > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/1804910/+subscriptions > -- Kevin O'Gorman #define QUESTION ((bb) || (!bb)) /* Shakespeare */ Please consider the environment before printing this email. ** Attachment added: "unnamed" https://bugs.launchpad.net/bugs/1804910/+attachment/5223298/+files/unnamed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1804910 Title: pip3 cannot install gmpy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/1804910/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1807265] Re: Screen locking issue
I discovered that the issue seems to not actually be the lock screen. Last night the screen timed out but did not lock as the lock is set to happen at 30 minutes but the blank screen at 10 min. The screen blanked and the issue occurred. I came back to the laptop some time later and found that the login prompt was there, and it let me enter my password and login. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1807265 Title: Screen locking issue To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1807265/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1807265] Re: Screen locking issue
I am attaching an image of the error. ** Attachment added: "Picture of blank screen after lockup" https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1807265/+attachment/5221095/+files/blank.jpg -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1807265 Title: Screen locking issue To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1807265/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1807627] [NEW] package systemd 237-3ubuntu10.9 failed to install/upgrade: installed systemd package post-installation script subprocess returned error exit status 1
Public bug reported: during upgrade from 16.04 to 18.04 ProblemType: Package DistroRelease: Ubuntu 18.04 Package: systemd 237-3ubuntu10.9 ProcVersionSignature: Ubuntu 4.4.0-140.166-generic 4.4.162 Uname: Linux 4.4.0-140-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Sun Dec 9 17:11:50 2018 ErrorMessage: installed systemd package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2016-09-01 (829 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) Lsusb: Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Hewlett-Packard HP Compaq 8200 Elite SFF PC ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-140-generic root=UUID=aa4fc23f-9987-40c4-8278-a702ff0b99a3 ro RelatedPackageVersions: dpkg 1.19.0.5ubuntu2.1 apt 1.2.29 SourcePackage: systemd Title: package systemd 237-3ubuntu10.9 failed to install/upgrade: installed systemd package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to bionic on 2018-12-10 (0 days ago) dmi.bios.date: 06/20/2012 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: J01 v02.21 dmi.board.asset.tag: 2UA142177C dmi.board.name: 1495 dmi.board.vendor: Hewlett-Packard dmi.chassis.asset.tag: 2UA142177C dmi.chassis.type: 6 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvrJ01v02.21:bd06/20/2012:svnHewlett-Packard:pnHPCompaq8200EliteSFFPC:pvr:rvnHewlett-Packard:rn1495:rvr:cvnHewlett-Packard:ct6:cvr: dmi.product.name: HP Compaq 8200 Elite SFF PC dmi.sys.vendor: Hewlett-Packard ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package bionic third-party-packages -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1807627 Title: package systemd 237-3ubuntu10.9 failed to install/upgrade: installed systemd package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1807627/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1807265] Re: Screen locking issue
I would like to add that the bug occurs after swiping the notification screen up. The blank screen that usually shows with the password entry box shows but without anything on it and the applications bar on the left is still showing. After applying the most recent update the bug seems to be happening less often, and only when the screen locks after not being used until it timed out. I work remotely and use Remina, skype, slack and Chrome which are usually all open when the issue occurs. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1807265 Title: Screen locking issue To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1807265/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1807537] [NEW] failure in fsck option of advanced boot
Public bug reported: I ran into this first on a 16.04.5 install I have. I just retried it on a new laptop with 18.04.1 with the same result. When booting, I chose the advanced form, the rescue variant, and tried to use its fsck option. This failed almost immediately. I'm attaching a photo of the screen showing the error, but the text is /lib/recovery-mode/recovery-menu: line 80: /etc/default/rcS: No such file or directory /dev/nvme0n1p5 is mounted. e2fsck: Cannot continue, aborting. Thus there seems to be no point in having this fsck option because it is doomed to fail. Well, at least in the absence of further guidance about how to use this. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: grub-common 2.02-2ubuntu8.9 ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18 Uname: Linux 4.15.0-42-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 Date: Sat Dec 8 13:52:47 2018 InstallationDate: Installed on 2018-10-18 (51 days ago) InstallationMedia: Xubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: grub2 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: grub2 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ** Attachment added: "iPhone photo of the screen on failure." https://bugs.launchpad.net/bugs/1807537/+attachment/5220436/+files/20181208_214340175_iOS.jpg -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1807537 Title: failure in fsck option of advanced boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1807537/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
