[Bug 1822246] [NEW] binfmt_misc02 in LTP kernel/fs/ failed with Bionic
Public bug reported: Found on a KVM node, I think this test case might need some investigation, as the LTP suite should be chop down into pieces like the syscalls variant. <<>> tag=binfmt_misc02 stime=1553796942 cmdline="binfmt_misc02.sh" contacts="" analysis=exit <<>> binfmt_misc02 1 TINFO: timeout per run is 0h 5m 0s binfmt_misc02 1 TFAIL: Recognise a disabled binary type successfully binfmt_misc02 2 TFAIL: Recognise a disabled binary type successfully binfmt_misc02 3 TFAIL: Recognise a disabled binary type successfully binfmt_misc02 4 TFAIL: Recognise a disabled binary type successfully binfmt_misc02 5 TFAIL: Recognise a binary type successfully binfmt_misc02 6 TFAIL: Recognise a binary type successfully binfmt_misc02 7 TINFO: AppArmor enabled, this may affect test results binfmt_misc02 7 TINFO: You can try to disable it with TST_DISABLE_APPARMOR=1 (requires super/root) binfmt_misc02 7 TINFO: loaded AppArmor profiles: none Summary: passed 0 failed 6 skipped 0 warnings 0 <<>> initiation_status="ok" duration=1 termination_type=exited termination_id=1 corefile=no cutime=14 cstime=6 <<>> ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-46-generic 4.15.0-46.49 ProcVersionSignature: User Name 4.15.0-46.49-generic 4.15.18 Uname: Linux 4.15.0-46-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mar 29 06:45 seq crw-rw 1 root audio 116, 33 Mar 29 06:45 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDmesg: Date: Fri Mar 29 06:48:07 2019 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: QEMU Standard PC (i440FX + PIIX, 1996) PciMultimedia: ProcFB: 0 cirrusdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-46-generic root=UUID=2a4b0342-a2dd-4feb-b3e2-9644ca1c4a60 ro RelatedPackageVersions: linux-restricted-modules-4.15.0-46-generic N/A linux-backports-modules-4.15.0-46-generic N/A linux-firmware 1.173.3 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: Ubuntu-1.8.2-1ubuntu1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-xenial dmi.modalias: dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-xenial:cvnQEMU:ct1:cvrpc-i440fx-xenial: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-xenial dmi.sys.vendor: QEMU ** Affects: ubuntu-kernel-tests Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: amd64 apport-bug bionic uec-images ** Description changed: Found on a KVM node, I think this test case might need some - investigation, as we are not going to disable the apparmor. + investigation, as the LTP suite should be chop down into pieces like the + syscalls variant. - <<>> - tag=binfmt_misc02 stime=1553796942 - cmdline="binfmt_misc02.sh" - contacts="" - analysis=exit - <<>> - binfmt_misc02 1 TINFO: timeout per run is 0h 5m 0s - binfmt_misc02 1 TFAIL: Recognise a disabled binary type successfully - binfmt_misc02 2 TFAIL: Recognise a disabled binary type successfully - binfmt_misc02 3 TFAIL: Recognise a disabled binary type successfully - binfmt_misc02 4 TFAIL: Recognise a disabled binary type successfully - binfmt_misc02 5 TFAIL: Recognise a binary type successfully - binfmt_misc02 6 TFAIL: Recognise a binary type successfully - binfmt_misc02 7 TINFO: AppArmor enabled, this may affect test results - binfmt_misc02 7 TINFO: You can try to disable it with TST_DISABLE_APPARMOR=1 (requires super/root) - binfmt_misc02 7 TINFO: loaded AppArmor profiles: none - - Summary: - passed 0 - failed 6 - skipped 0 - warnings 0 - <<>> - initiation_status="ok" - duration=1 termination_type=exited termination_id=1 corefile=no - cutime=14 cstime=6 - <<>> + <<>> + tag=binfmt_misc02 stime=1553796942 + cmdline="binfmt_misc02.sh" + contacts="" + analysis=exit + <<>> + binfmt_misc02 1 TINFO: timeout per run is 0h 5m 0s + binfmt_misc02 1 TFAIL: Recognise a disabled binary type successfully + binfmt_misc02 2 TFAIL: Recognise a disabled binary type successfully + binfmt_misc02 3 TFAIL: Recognise a disabled binary type successfully + binfmt_misc02 4 TFAIL: Recognise a disabled binary type successfully + binfmt_misc02 5 TFAIL: Recognise a binary type successfully + binfmt_misc02 6 TFAIL: Recognise a binary type suc
[Bug 1821723] Re: linux-snapdragon: 4.4.0-1110.115 -proposed tracker
Hardware Certification have completed testing this -proposed kernel. No regressions were observed, results are available here: http://people.canonical.com/~hwcert/sru- testing/snapdragon/4.4.0-1110.115/snapdragon-4.4-proposed-published.html ** Tags added: certification-testing-passed ** Changed in: kernel-sru-workflow/certification-testing Status: In Progress => 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/1821723 Title: linux-snapdragon: 4.4.0-1110.115 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1821723/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1822247] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1822247 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete ** Changed in: linux (Ubuntu Bionic) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1822247 Title: ubuntu_nbd_smoke_test failed on P9 with Bionic kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1822247/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1822247] [NEW] ubuntu_nbd_smoke_test failed on P9 with Bionic kernel
Public bug reported: Reproduce rate: 2 out of 3 runs This issue can be found on other arches as well, normally it will fail with the first run and pass with the second attempt. * Command: /home/ubuntu/autotest/client/tests/ubuntu_nbd_smoke_test/ubuntu_nbd_smoke _test.sh Exit status: 1 Duration: 7.90551400185 stdout: creating backing nbd image /tmp/nbd_image.img Image path:/tmp/nbd_image.img Mount point: /mnt/nbd-test-13924 Date: Fri Mar 29 06:06:04 UTC 2019 Host: baltar Kernel:4.15.0-46-generic #49-Ubuntu SMP Wed Feb 6 09:32:48 UTC 2019 Machine: baltar ppc64le ppc64le CPUs online: 160 CPUs total:160 Page size: 65536 Pages avail: 1904339 Pages total: 2089666 Free space: Filesystem Size Used Avail Use% Mounted on udev 61G 0 61G 0% /dev tmpfs13G 12M 13G 1% /run /dev/sda2 1.8T 11G 1.7T 1% / tmpfs64G 0 64G 0% /dev/shm tmpfs 5.0M 0 5.0M 0% /run/lock tmpfs64G 0 64G 0% /sys/fs/cgroup tmpfs13G 0 13G 0% /run/user/1000 NBD device /dev/nbd0 created found nbd export NBD exports found: test starting client with NBD device /dev/nbd0 Negotiation: ..size = 128MB creating ext4 on /dev/nbd0 mkfs on /dev/nbd0 succeeded after 0 attempt(s) checking ext4 on /dev/nbd0 fsck from util-linux 2.31.1 /dev/nbd0: clean, 11/32768 files, 9787/131072 blocks mount: /dev/nbd0 on /mnt/nbd-test-13924 type ext4 (rw,relatime,data=ordered) mounted on /dev/nbd0 free: Filesystem 1K-blocks Used Available Use% Mounted on /dev/nbd0 122835 1550112111 2% /mnt/nbd-test-13924 creating large file /mnt/nbd-test-13924/largefile -rw-r--r-- 1 root root 100M Mar 29 06:06 /mnt/nbd-test-13924/largefile free: Filesystem 1K-blocks Used Available Use% Mounted on /dev/nbd0 122835 103951 9710 92% /mnt/nbd-test-13924 removing file /mnt/nbd-test-13924/largefile unmounting /mnt/nbd-test-13924 stopping client disconnect, sock, done Found kernel warning, IO error and/or call trace echo [ 694.662746] creating backing nbd image /tmp/nbd_image.img [ 695.821047] NBD device /dev/nbd0 created [ 696.271555] found nbd export [ 697.318393] starting client with NBD device /dev/nbd0 [ 697.323210] creating ext4 on /dev/nbd0 [ 697.589620] mkfs on /dev/nbd0 succeeded after 0 attempt(s) [ 697.821953] checking ext4 on /dev/nbd0 [ 697.919173] EXT4-fs (nbd0): mounted filesystem with ordered data mode. Opts: (null) [ 697.925418] mounted on /dev/nbd0 [ 697.927107] creating large file /mnt/nbd-test-13924/largefile [ 698.839327] removing file /mnt/nbd-test-13924/largefile [ 699.596736] unmounting /mnt/nbd-test-13924 [ 700.664881] stopping client [ 700.667573] block nbd0: NBD_DISCONNECT [ 700.667733] block nbd0: shutting down sockets [ 700.668690] nbd0: detected capacity change from 0 to 134217728 [ 700.668758] print_req_error: I/O error, dev nbd0, sector 0 [ 700.668840] Buffer I/O error on dev nbd0, logical block 0, async page read [ 700.669068] print_req_error: I/O error, dev nbd0, sector 0 [ 700.669124] Buffer I/O error on dev nbd0, logical block 0, async page read [ 700.669203] print_req_error: I/O error, dev nbd0, sector 0 [ 700.669243] Buffer I/O error on dev nbd0, logical block 0, async page read [ 700.669315] ldm_validate_partition_table(): Disk read failed. [ 700.669324] print_req_error: I/O error, dev nbd0, sector 0 [ 700.669364] Buffer I/O error on dev nbd0, logical block 0, async page read [ 700.669542] print_req_error: I/O error, dev nbd0, sector 0 [ 700.669580] Buffer I/O error on dev nbd0, logical block 0, async page read [ 700.669646] print_req_error: I/O error, dev nbd0, sector 0 [ 700.669686] Buffer I/O error on dev nbd0, logical block 0, async page read [ 700.669747] print_req_error: I/O error, dev nbd0, sector 0 [ 700.669785] Buffer I/O error on dev nbd0, logical block 0, async page read [ 700.669850] Dev nbd0: unable to read RDB block 0 [ 700.669895] print_req_error: I/O error, dev nbd0, sector 0 [ 700.669932] Buffer I/O error on dev nbd0, logical block 0, async page read [ 700.670014] print_req_error: I/O error, dev nbd0, sector 0 [ 700.670053] Buffer I/O error on dev nbd0, logical block 0, async page read [ 700.670118] print_req_error: I/O error, dev nbd0, sector 0 [ 700.670161] Buffer I/O error on dev nbd0, logical block 0, async page read [ 700.670237] nbd0: unable to read partition table [ 700.880422] Found kernel warning, IO error and/or call trace [ 700.880479] echo killing server ==
[Bug 1822246] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1822246 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1822246 Title: binfmt_misc02 in LTP kernel/fs/ failed with Bionic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1822246/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1819707] Re: linux-fips: 4.15.0-1002.3 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-signing Status: New => Confirmed ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1819716 phase: Holding before Promote to Proposed phase-changed: Friday, 29. March 2019 06:21 UTC reason: - promote-to-signing: unknown workflow task + promote-to-signing: Pending -- ready for review -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1819707 Title: linux-fips: 4.15.0-1002.3 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1819707/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1576859] Re: [nvidia] Graphics corruption when resuming from suspend
*** This bug is a duplicate of bug 1809407 *** https://bugs.launchpad.net/bugs/1809407 >Aside from anything else, JournalErrors.txt above is showing this bug is from Nvidia driver version 364.19 which doesn't seem to have ever been officially released so is not supported: It was from the unofficial "official" Ubuntu Nvidia driver PPA. I remember issues with resuming from suspend was a noted problem on Nvidia's website at the time although I don't know if they were referring to this bug specifically. >But regardless of the driver version, Nvidia is closed source so neither Canonical nor the community have any power to fix it. We can only track its bugs. Fine. What about the hundred(thousands?) of other critical bugs with open source software that Ubuntu could fix? Like https://bugs.launchpad.net/ubuntu/+source/gnome- software/+bug/1575426 OR https://bugs.launchpad.net/ubuntu/xenial/+source/gnome- session/+bug/1575434 Which was marked as "fixed" because it was fixed in a newer Gnome version. Presumably it's still an issue on 16.04. What the actual hell? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1576859 Title: [nvidia] Graphics corruption when resuming from suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1576859/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1818645] Re: Ubuntu18.04.01: [Power9] power8 Compat guest(RHEL7.6) crashes during guest boot with > 256G of memory (kernel/kvm)
** Changed in: linux (Ubuntu Bionic) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1818645 Title: Ubuntu18.04.01: [Power9] power8 Compat guest(RHEL7.6) crashes during guest boot with > 256G of memory (kernel/kvm) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1818645/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1819306] Re: 100% cpu in libreoffice
Hi Olivier Tilloy. That bug of the laptop overheating like crazy when LibreOffice is running (which seemed to be that LibreOffice was hogging a bunch of CPU all the sudden) seems to not be happening anymore. This is in reference to https://bugs.launchpad.net/bugs/1819306 . Thanks again. B On Wed, Mar 20, 2019 at 1:31 PM Olivier Tilloy wrote: > Can you share the output of: > > apt policy libreoffice-core > > Were you editing relatively big files when this happened? > > Could you try running libreoffice with the --safe-mode parameter and see > if this happens again? > > ** Changed in: libreoffice (Ubuntu) >Status: New => Incomplete > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1819306 > > Title: > 100% cpu in libreoffice > > Status in libreoffice package in Ubuntu: > Incomplete > > Bug description: > I've been seeing high cpu from libreoffice in the last week (today is > 3/9/2019). I had a bunch of files open, but nothing actively > happening. The circumstances don't seem to match the other reports of > high cpu. > > It's happened twice. Each time, the only solution I found was to > restart libreoffice. > > ProblemType: Bug > DistroRelease: Ubuntu 18.04 > Package: libreoffice (not installed) > ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18 > Uname: Linux 4.15.0-45-generic x86_64 > NonfreeKernelModules: nvidia_modeset nvidia > ApportVersion: 2.20.9-0ubuntu7.5 > Architecture: amd64 > CurrentDesktop: ubuntu:GNOME > Date: Sat Mar 9 23:51:06 2019 > InstallationDate: Installed on 2018-12-01 (98 days ago) > InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 > (20180725) > ProcEnviron: >TERM=xterm-256color >PATH=(custom, no user) >XDG_RUNTIME_DIR= >LANG=en_US.UTF-8 >SHELL=/bin/bash > SourcePackage: libreoffice > UpgradeStatus: No upgrade log present (probably fresh install) > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1819306/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1819306 Title: 100% cpu in libreoffice To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1819306/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1803319] Re: GNOME Shell task bar menus not updated with external monitor primary and laptop screen fractionally scaled
Sounds reasonable. Thanks for letting me know. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1803319 Title: GNOME Shell task bar menus not updated with external monitor primary and laptop screen fractionally scaled To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1803319/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1822254] [NEW] Can't drag and drop files to Desktop on Disco 19.04 beta
Public bug reported: Summary: Can't drag and drop files to Desktop on Disco 19.04 beta Steps to reproduce: 1. Click "Files" on luncher 2. Select some files 3. Drag and drop the files to desktop (Disco Dingo wallpaper) Expected result: Drag and drop the files to desktop successfully Actual result: Can't drap and drop files to desktop Addtional information: Drag and drog the files in "Files" to "Desktop" folder were succesful and the files show on desktop (Disco Dingo wallpapaer) Failure rate: 100% - CPU: Intel(R) Core(TM) i7-8850H CPU @ 2.60GHz (12x) system-product-name: Precision 5530 bios-version: 1.6.0 system-manufacturer: Dell Inc. GPU: 00:02.0 VGA compatible controller: Intel Corporation Device 3e9b ** Affects: ubuntu Importance: Undecided Status: New ** Tags: ce-qa-concern disco -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1822254 Title: Can't drag and drop files to Desktop on Disco 19.04 beta To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1822254/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1822254] Re: Can't drag and drop files to Desktop on Disco 19.04 beta
Automatically attached ** Attachment added: "snap_list.log" https://bugs.launchpad.net/bugs/1822254/+attachment/5250506/+files/snap_list.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1822254 Title: Can't drag and drop files to Desktop on Disco 19.04 beta To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1822254/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1822254] Re: Can't drag and drop files to Desktop on Disco 19.04 beta
Automatically attached ** Attachment added: "sosreport-u-Precision-5530-20190329152001.tar.gz" https://bugs.launchpad.net/bugs/1822254/+attachment/5250505/+files/sosreport-u-Precision-5530-20190329152001.tar.gz -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1822254 Title: Can't drag and drop files to Desktop on Disco 19.04 beta To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1822254/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1822254] Re: Can't drag and drop files to Desktop on Disco 19.04 beta
Automatically attached ** Attachment added: "acpidump.log" https://bugs.launchpad.net/bugs/1822254/+attachment/5250504/+files/acpidump.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1822254 Title: Can't drag and drop files to Desktop on Disco 19.04 beta To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1822254/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1822249] Re: calamares crashed with SIGSEGV in KPMHelpers::isPartitionNew()
** Information type changed from Private to Public -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1822249 Title: calamares crashed with SIGSEGV in KPMHelpers::isPartitionNew() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/calamares/+bug/1822249/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1822249] calamares crashed with SIGSEGV in KPMHelpers::isPartitionNew()
StacktraceTop: KPMHelpers::isPartitionNew (partition=0x0) at /usr/include/kpmcore/core/partition.h:187 PartitionPage::onEditClicked (this=0x7f9b64024480) at ./src/modules/partition/gui/PartitionPage.cpp:403 QtPrivate::QSlotObjectBase::call (a=0x7ffea4f2e940, r=0x7f9b64024480, this=0x555da4e63760) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:376 QMetaObject::activate (sender=0x555da4e4f9d0, signalOffset=, local_signal_index=, argv=) at kernel/qobject.cpp:3754 QAbstractButton::clicked (this=this@entry=0x555da4e4f9d0, _t1=) at .moc/moc_qabstractbutton.cpp:308 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1822249 Title: calamares crashed with SIGSEGV in KPMHelpers::isPartitionNew() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/calamares/+bug/1822249/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1822249] StacktraceSource.txt
** Attachment added: "StacktraceSource.txt" https://bugs.launchpad.net/bugs/1822249/+attachment/5250514/+files/StacktraceSource.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1822249 Title: calamares crashed with SIGSEGV in KPMHelpers::isPartitionNew() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/calamares/+bug/1822249/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1822255] [NEW] package gambas3-runtime 3.8.4-2ubuntu3.1 failed to install/upgrade: a tentar sobre-escrever '/usr/lib/gambas3/gb.gui.qt.webkit.so.0.0.0', que também está no pacote gambas3-gb-gui-q
Public bug reported: nao sei explicar ProblemType: Package DistroRelease: Ubuntu 16.04 Package: gambas3-runtime 3.8.4-2ubuntu3.1 ProcVersionSignature: Ubuntu 4.15.0-46.49~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-46-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Fri Mar 29 03:48:50 2019 DpkgTerminalLog: A preparar para desempacotar .../gambas3-runtime_3.12.2+git5962.78f8359+build4.f16e457.8.7951239~ubuntu16.04.1_amd64.deb ... A descompactar gambas3-runtime (3.12.2+git5962.78f8359+build4.f16e457.8.7951239~ubuntu16.04.1) sobre (3.8.4-2ubuntu3.1) ... dpkg: erro ao processar o arquivo /var/cache/apt/archives/gambas3-runtime_3.12.2+git5962.78f8359+build4.f16e457.8.7951239~ubuntu16.04.1_amd64.deb (--unpack): a tentar sobre-escrever '/usr/lib/gambas3/gb.gui.qt.webkit.so.0.0.0', que também está no pacote gambas3-gb-gui-qt-webkit 3.8.4-2ubuntu3.1 ErrorMessage: a tentar sobre-escrever '/usr/lib/gambas3/gb.gui.qt.webkit.so.0.0.0', que também está no pacote gambas3-gb-gui-qt-webkit 3.8.4-2ubuntu3.1 InstallationDate: Installed on 2019-03-27 (2 days ago) InstallationMedia: Ubuntu 16.04.6 LTS "Xenial Xerus" - Release amd64 (20190227) RelatedPackageVersions: dpkg 1.18.4ubuntu1.5 apt 1.2.31 SourcePackage: gambas3 Title: package gambas3-runtime 3.8.4-2ubuntu3.1 failed to install/upgrade: a tentar sobre-escrever '/usr/lib/gambas3/gb.gui.qt.webkit.so.0.0.0', que também está no pacote gambas3-gb-gui-qt-webkit 3.8.4-2ubuntu3.1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gambas3 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1822255 Title: package gambas3-runtime 3.8.4-2ubuntu3.1 failed to install/upgrade: a tentar sobre-escrever '/usr/lib/gambas3/gb.gui.qt.webkit.so.0.0.0', que também está no pacote gambas3-gb-gui-qt-webkit 3.8.4-2ubuntu3.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gambas3/+bug/1822255/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1822249] ThreadStacktrace.txt
** Attachment added: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1822249/+attachment/5250515/+files/ThreadStacktrace.txt ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1822249/+attachment/5250494/+files/CoreDump.gz ** Changed in: calamares (Ubuntu) Importance: Undecided => Medium ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1822249 Title: calamares crashed with SIGSEGV in KPMHelpers::isPartitionNew() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/calamares/+bug/1822249/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1819546] Re: Avoid potential memory corruption on HiSilicon SoCs
** Changed in: linux (Ubuntu Bionic) Status: In Progress => Fix Committed ** Changed in: linux (Ubuntu Cosmic) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1819546 Title: Avoid potential memory corruption on HiSilicon SoCs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1819546/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1822246] Re: binfmt_misc02 in LTP kernel/fs/ failed with Bionic
Tried to run the test with TST_DISABLE_APPARMOR=1, but it seems this is not working as well: root@zeppo:/opt/ltp# export TST_DISABLE_APPARMOR=1 root@zeppo:/opt/ltp# ./runltp -f /tmp/a <<>> incrementing stop binfmt_misc02 1 TINFO: timeout per run is 0h 5m 0s binfmt_misc02 1 TFAIL: Recognise a disabled binary type successfully binfmt_misc02 2 TFAIL: Recognise a disabled binary type successfully binfmt_misc02 3 TFAIL: Recognise a disabled binary type successfully binfmt_misc02 4 TFAIL: Recognise a disabled binary type successfully binfmt_misc02 5 TFAIL: Recognise a binary type successfully binfmt_misc02 6 TFAIL: Recognise a binary type successfully binfmt_misc02 7 TINFO: AppArmor enabled, this may affect test results binfmt_misc02 7 TINFO: You can try to disable it with TST_DISABLE_APPARMOR=1 (requires super/root) binfmt_misc02 7 TINFO: loaded AppArmor profiles: none -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1822246 Title: binfmt_misc02 in LTP kernel/fs/ failed with Bionic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1822246/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1822249] Stacktrace.txt
** Attachment added: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1822249/+attachment/5250513/+files/Stacktrace.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1822249 Title: calamares crashed with SIGSEGV in KPMHelpers::isPartitionNew() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/calamares/+bug/1822249/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1821927] Re: Systemd do not respawn sssd on failure
We discussed this yesterday and think that is a vlaid bug report - thanks! It spawned a spin-off discussion how we want to handle auto-restart in general which will go on for a while. For this particular case Andreas wanted to take a look at the details and maybe bring the suggestion also upstream (to avoid there being known reasons for not restarting it). To mark that I'll subscribe the team and assign it to Andreas (for now) ** Tags added: server-next ** Changed in: sssd (Ubuntu) Assignee: (unassigned) => Andreas Hasenack (ahasenack) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1821927 Title: Systemd do not respawn sssd on failure To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/1821927/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1822254] Re: Can't drag and drop files to Desktop on Disco 19.04 beta
** Package changed: ubuntu => gnome-shell-extension-desktop-icons (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1822254 Title: Can't drag and drop files to Desktop on Disco 19.04 beta To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons/+bug/1822254/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1576859] Re: [nvidia] Graphics corruption when resuming from suspend
*** This bug is a duplicate of bug 1809407 *** https://bugs.launchpad.net/bugs/1809407 Neither of those bugs are critical or affecting many people at all. So that's why no developers seem to have fixed them for 16.04 yet. We have several orders of magnitude more bugs than we can possibly hope to fix. But I do understand your frustration -- I made exactly the same complaint to Canonical years before joining Canonical. As for Gnome Shell bugs, those are especially unlikely to ever get touched because Ubuntu only really started supporting Gnome Shell properly in 17.10 (which is already past end of life). So Gnome Shell bugs will generally be fixed in Ubuntu 18.04 and later. I know Ubuntu- GNOME existed long before that, but it's not a flavor that the main desktop team supports. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1576859 Title: [nvidia] Graphics corruption when resuming from suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1576859/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1818881] Re: ath10k_pci crashing
I just got a XPS 13 9380, not find the issue yet, I'm keep using that machine wireless to see if I can reproduce here. Not sure if the wireless chip same as the machine be reported. hardware information: 02:00.0 Network controller [0280]: Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter [168c:003e] (rev 32) uname -r: 4.18.0-16-generic (4.18.0-16.17~18.04.1) system ID: 08AF $ modinfo ath10k_pci http://paste.ubuntu.com/p/QXxkBR9Ymt/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1818881 Title: ath10k_pci crashing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818881/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1821935] Re: Samba panic or segfault
@Paride - I think Andreas said we should ask for the .crash file right? @Marc - could you please attach the full crash file that is create din /var/crash for this? That would allow to see more than just the backtrace. To know exactly the versions you have installed atm I think you could also run $ apport-collect 1821935 I'm not entirely sure if this also auto-attaches the crash. If it doesn't you can do so manually after the other info is added. Setting incomplete waiting for that extra data. ** Changed in: samba (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1821935 Title: Samba panic or segfault To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1821935/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1822258] [NEW] package libfprint-dev (not installed) failed to install/upgrade: tentative de remplacement de « /usr/include/libfprint/fprint.h », qui appartient aussi au paquet libfprint 0.0.6-1
Public bug reported: unable to use my fingerprint ProblemType: Package DistroRelease: Ubuntu 18.10 Package: libfprint-dev (not installed) ProcVersionSignature: Ubuntu 4.18.0-16.17-generic 4.18.20 Uname: Linux 4.18.0-16-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 AptOrdering: aes2501-wy:amd64: Install libfprint-dev:amd64: Install NULL: ConfigurePending Architecture: amd64 Date: Fri Mar 29 08:48:45 2019 ErrorMessage: tentative de remplacement de « /usr/include/libfprint/fprint.h », qui appartient aussi au paquet libfprint 0.0.6-1 InstallationDate: Installed on 2019-03-28 (0 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Python3Details: /usr/bin/python3.6, Python 3.6.7rc1, python3-minimal, 3.6.6-1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.0.5ubuntu5 apt 1.7.0 SourcePackage: libfprint Title: package libfprint-dev (not installed) failed to install/upgrade: tentative de remplacement de « /usr/include/libfprint/fprint.h », qui appartient aussi au paquet libfprint 0.0.6-1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: libfprint (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package cosmic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1822258 Title: package libfprint-dev (not installed) failed to install/upgrade: tentative de remplacement de « /usr/include/libfprint/fprint.h », qui appartient aussi au paquet libfprint 0.0.6-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libfprint/+bug/1822258/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1822249] Re: calamares crashed with SIGSEGV in KPMHelpers::isPartitionNew()
** Description changed: Lubuntu 19.04 QA checklist installs. - This install was going to re-use my /home, and have auto-login enabled - using manual partitioning. + This install was going to re-use my partitions (keep my /home & format + my /) and have auto-login enabled using manual partitioning. I noticed what appeared (twice at that stage) where I'd selected "format" a partition, when I re-entered the partition [settings] it seemed to show "keep". I was re-opening to explore that before seeing if I was mistaken, or it is an issue when the calamares installer disappeared off screen (crash). Sure enough there was a crash report in /var/crash, which `ubuntu-bug` caused this report. Only significant behavior was re-entering (to view) partitions a few times exploring the 'keep' or 'format' option which I'm suspicious is flipping 'keep' when it shouldn't. + --- + I've done more exploration/testing of the keep/format option & so have added some notes at the bottom, which is an issue I've logged here instead of a new bug report. + ProblemType: Crash DistroRelease: Ubuntu 19.04 Package: calamares 3.2.4-0ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0 Uname: Linux 5.0.0-7-generic x86_64 .etc.calamares.modules.automirror.conf: - --- - baseUrl: archive.ubuntu.com - distribution: Lubuntu - geoIpUrl: https://ipapi.co/json + --- + baseUrl: archive.ubuntu.com + distribution: Lubuntu + geoIpUrl: https://ipapi.co/json .etc.calamares.modules.finished.conf: - --- - restartNowChecked: true - restartNowEnabled: true - restartNowCommand: "systemctl -i reboot" + --- + restartNowChecked: true + restartNowEnabled: true + restartNowCommand: "systemctl -i reboot" .etc.calamares.modules.partition.conf: - efiSystemPartition: "/boot/efi" - enableLuksAutomatedPartitioning: true - neverCreateSwap: true - drawNestedPartitions: true + efiSystemPartition: "/boot/efi" + enableLuksAutomatedPartitioning: true + neverCreateSwap: true + drawNestedPartitions: true .etc.calamares.modules.shellprocess_logs.conf: - --- - dontChroot: true - timeout: 30 - script: - - calamares-logs-helper @@ROOT@@ + --- + dontChroot: true + timeout: 30 + script: + - calamares-logs-helper @@ROOT@@ .etc.calamares.modules.unpackfs.conf: - --- - unpack: - - source: "/cdrom/casper/filesystem.squashfs" - sourcefs: "squashfs" - destination: "" + --- + unpack: + - source: "/cdrom/casper/filesystem.squashfs" + sourcefs: "squashfs" + destination: "" ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 CasperVersion: 1.402 CurrentDesktop: LXQt Date: Fri Mar 29 17:58:38 2019 ExecutablePath: /usr/bin/calamares ExecutableTimestamp: 1550273216 LiveMediaBuild: Lubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190326.1) ProcCmdline: calamares ProcCwd: /home/lubuntu ProcEnviron: - SHELL=/bin/bash - LANG=C.UTF-8 - TERM=qterminal - XDG_RUNTIME_DIR= - PATH=(custom, no user) + SHELL=/bin/bash + LANG=C.UTF-8 + TERM=qterminal + XDG_RUNTIME_DIR= + PATH=(custom, no user) RelatedPackageVersions: - calamares-settings-ubuntu-common 1:19.04.3 - calamares-settings-lubuntu 1:19.04.3 - xfsprogs 4.15.1-1ubuntu1 - btrfs-progs 4.20.2-1 + calamares-settings-ubuntu-common 1:19.04.3 + calamares-settings-lubuntu 1:19.04.3 + xfsprogs 4.15.1-1ubuntu1 + btrfs-progs 4.20.2-1 SegvAnalysis: - Segfault happened at: 0x7f9b8f157f10 <_ZN10KPMHelpers14isPartitionNewEP9Partition>: cmpl $0x1,0x90(%rdi) - PC (0x7f9b8f157f10) ok - source "$0x1" ok - destination "0x90(%rdi)" (0x0090) not located in a known VMA region (needed writable region)! + Segfault happened at: 0x7f9b8f157f10 <_ZN10KPMHelpers14isPartitionNewEP9Partition>: cmpl $0x1,0x90(%rdi) + PC (0x7f9b8f157f10) ok + source "$0x1" ok + destination "0x90(%rdi)" (0x0090) not located in a known VMA region (needed writable region)! SegvReason: writing NULL VMA Signal: 11 SourcePackage: calamares StacktraceTop: - KPMHelpers::isPartitionNew(Partition*) () from /usr/lib/x86_64-linux-gnu/calamares/modules/partition/libcalamares_viewmodule_partition.so - PartitionPage::onEditClicked() () from /usr/lib/x86_64-linux-gnu/calamares/modules/partition/libcalamares_viewmodule_partition.so - QMetaObject::activate(QObject*, int, int, void**) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 - QAbstractButton::clicked(bool) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 - ?? () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 + KPMHelpers::isPartitionNew(Partition*) () from /usr/lib/x86_64-linux-gnu/calamares/modules/partition/libcalamares_viewmodule_partition.so + PartitionPage::onEditClicked() () from /usr/lib/x86_64-linux-gnu/calamares/modules/partition/libcalamares_viewmodule_partition.so + QMetaObject::activate(QObject*, int, int
[Bug 1776228] Re: Duplicate default routes on VMs with multiple NICs
netplan.io (0.96-0ubuntu0.18.10.2 works fine as netplan.io 0.96-0ubuntu0.18.10.1 did. What changes did make a new test necessary? ** Tags removed: verification-needed-cosmic ** Tags added: verification-done-cosmic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1776228 Title: Duplicate default routes on VMs with multiple NICs To manage notifications about this bug go to: https://bugs.launchpad.net/netplan/+bug/1776228/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1821678] Re: [FFe] Please sync ukui-biometric-auth 1.0.3-2(universe) from debian(experimental)
** Changed in: ubuntukylin Status: New => Fix Released ** Changed in: ukui-biometric-auth (Ubuntu) Status: New => 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/1821678 Title: [FFe] Please sync ukui-biometric-auth 1.0.3-2(universe) from debian(experimental) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntukylin/+bug/1821678/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1818645] Re: Ubuntu18.04.01: [Power9] power8 Compat guest(RHEL7.6) crashes during guest boot with > 256G of memory (kernel/kvm)
Since the fix is already included in the disco kernel I'm changing the root 'linux (Ubuntu)' entry (that is usually used to track the current development release kernel) to Fix Released. And because the bionic entry is Fix Committed I adjust the project entry and change it to Fix Committed, too. ** Changed in: linux (Ubuntu) Status: New => Fix Released ** Changed in: ubuntu-power-systems Status: Triaged => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1818645 Title: Ubuntu18.04.01: [Power9] power8 Compat guest(RHEL7.6) crashes during guest boot with > 256G of memory (kernel/kvm) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1818645/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1822240] Re: Installer doesn't like Kogan 360 laptop.
Thanks for your report. >From the logs it seems that the installation media is corrupted Mar 29 05:54:28 ubuntu-mate kernel: [ 228.068019] mmc2: tuning execution failed: -22 Mar 29 05:54:28 ubuntu-mate kernel: [ 228.068030] mmc2: error -22 whilst initialising SD card Mar 29 05:54:41 ubuntu-mate kernel: [ 240.300523] mmc2: tuning execution failed: -22 Mar 29 05:54:41 ubuntu-mate kernel: [ 240.300534] mmc2: error -22 whilst initialising SD card Mar 29 05:54:51 ubuntu-mate kernel: [ 250.669023] SQUASHFS error: zlib decompression failed, data probably corrupt Mar 29 05:54:51 ubuntu-mate kernel: [ 250.669029] SQUASHFS error: squashfs_read_data failed to read block 0x183c235f Mar 29 05:54:51 ubuntu-mate kernel: [ 250.669687] SQUASHFS error: zlib decompression failed, data probably corrupt Mar 29 05:54:51 ubuntu-mate kernel: [ 250.669689] SQUASHFS error: squashfs_read_data failed to read block 0x183c235f Could you try another one? ** Changed in: ubiquity (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1822240 Title: Installer doesn't like Kogan 360 laptop. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1822240/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1822068] Re: Intellij ToolBox Running prevents Mysql 5.7 installing
There would need to be better steps to rpreoduce the error at least. Are you sure that process 3539 "now" is the same as when mysql has thrown the error? Also I wondere about 1023 (which might be too close to 1024 to be a coincident). Once this happens, could you also check - what that FD points to (if it exists) - check /proc//limits if by any chance this is just ulimits in som eway - check dmesg if there was a related apparmor Deny that could be reported -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1822068 Title: Intellij ToolBox Running prevents Mysql 5.7 installing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-5.7/+bug/1822068/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1795292] Re: ELAN469D touch pad not working
Hey everyone. I was directed here from askubuntu. Having the same issue. No wifi or touchpad. Although I updated to the latest BIOS through windows before making the switch to ubuntu. Before looking around, I was able to update to kernel v5.0.4-50004 (using ethernet to usb converter). and still no touchpad or wifi. Have there been any updates reguarding getting at least the touchpad working without having to compile the kernel? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1795292 Title: ELAN469D touch pad not working To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1795292/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1821939] Re: package openssh-server 1:7.2p2-4ubuntu2.8 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
FYI - Might be: - bug 1811580 Or broken /var/run / /run connection which is related to - https://askubuntu.com/questions/1109934 - https://serverfault.com/questions/941855 You might pickup some hints about the issue in general there. As paride said let us know if you identified a bug in Ubuntu itself, but so far it was always a system setup issue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1821939 Title: package openssh-server 1:7.2p2-4ubuntu2.8 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/openssh/+bug/1821939/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1822068] Re: Intellij ToolBox Running prevents Mysql 5.7 installing
Hi Cr Viper, Thank you for taking the time to report this bug and helping to make Ubuntu better. Since there isn't enough information in your report to differentiate between a local configuration problem and a bug in Ubuntu, I'm marking this bug as Incomplete. If indeed this is a local configuration problem, you can find pointers to get help for this sort of problem here: http://www.ubuntu.com/support/community Or 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 => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1822068 Title: Intellij ToolBox Running prevents Mysql 5.7 installing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-5.7/+bug/1822068/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1776228] Re: Duplicate default routes on VMs with multiple NICs
netplan.io 0.96-0ubuntu0.18.04.2 works fine as 0.96-0ubuntu0.18.04.1 did. Subsequent hickup up of systemd 237-3ubuntu10.15 also remains as expected. ** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1776228 Title: Duplicate default routes on VMs with multiple NICs To manage notifications about this bug go to: https://bugs.launchpad.net/netplan/+bug/1776228/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1818770] Re: Unexpected graybar on top of openstack-dashboard login page
Thanks Karl for your double check. I verified your proposed fix on Firefox and Chrome. I will update the packages. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1818770 Title: Unexpected graybar on top of openstack-dashboard login page To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1818770/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1821867] Re: network interface is down after post-install reboot of a default disco installation
I first of all tested the package: https://launchpad.net/ubuntu/+source/netplan.io/0.96-0ubuntu4 from disco proposed, since it was on disco where I faced that problem, and that works now. Tested just upgraded an already installed disco system to the netplan.io version from proposed, as well as doing a proposed installation (having 'apt-setup/proposed=true' added to the parmfile). Both is good so far - looking forward to see it landing in one of the next disco daily images. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1821867 Title: network interface is down after post-install reboot of a default disco installation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1821867/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1818770] Re: Unexpected graybar on top of openstack-dashboard login page
Karl, If you can ACK the changes. https://code.launchpad.net/~sahid- ferdjaoui/ubuntu/+source/horizon/+git/horizon Thanks. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1818770 Title: Unexpected graybar on top of openstack-dashboard login page To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1818770/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1814892] Re: [19.04 FEAT] qeth: Enhanced link speed - kernel part
** Changed in: linux (Ubuntu Bionic) Status: New => Fix Committed ** Changed in: linux (Ubuntu Cosmic) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1814892 Title: [19.04 FEAT] qeth: Enhanced link speed - kernel part To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1814892/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1777062] Re: Logitech M535 mouse only pairs successfully after 4-5 tries
Yes, I just removed the mouse under gnome-control-center, went into `bluetoothctl` and tried to pair it again: [bluetooth]# scan on Discovery started [NEW] Device 49:4E:A7:0B:A0:51 49-4E-A7-0B-A0-51 [NEW] Device 34:88:5D:3E:A1:A4 Bluetooth Mouse M336/M337/M535 [bluetooth]# pair 34:88:5D:3E:A1:A4 Attempting to pair with 34:88:5D:3E:A1:A4 [CHG] Device 34:88:5D:3E:A1:A4 Connected: yes [CHG] Device 34:88:5D:3E:A1:A4 Modalias: usb:v046DpB014d1200 [CHG] Device 34:88:5D:3E:A1:A4 UUIDs: 1000--1000-8000-00805f9b34fb [CHG] Device 34:88:5D:3E:A1:A4 UUIDs: 1124--1000-8000-00805f9b34fb [CHG] Device 34:88:5D:3E:A1:A4 UUIDs: 1200--1000-8000-00805f9b34fb [CHG] Device 34:88:5D:3E:A1:A4 ServicesResolved: yes [CHG] Device 34:88:5D:3E:A1:A4 Paired: yes Pairing successful [CHG] Device 34:88:5D:3E:A1:A4 ServicesResolved: no [CHG] Device 34:88:5D:3E:A1:A4 Connected: no [bluetooth]# pair 34:88:5D:3E:A1:A4 Attempting to pair with 34:88:5D:3E:A1:A4 Failed to pair: org.bluez.Error.AlreadyExists [bluetooth]# connect 34:88:5D:3E:A1:A4 Attempting to connect to 34:88:5D:3E:A1:A4 Failed to connect: org.bluez.Error.Failed [bluetooth]# version Version 5.50 [bluetooth]# quit $ uname -a Linux michal-laptop 4.18.0-16-generic #17-Ubuntu SMP Fri Feb 8 00:06:57 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux bluetoothctl claims it pairs it, but then disconnects again. The mouse continues to blink, remaining in pairing mode. Even when it does pair successfully, only every 10 times or so does the pairing "persist" across suspend/reboot cycles. Most often I have to re- pair from scratch every boot/resume. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1777062 Title: Logitech M535 mouse only pairs successfully after 4-5 tries To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1777062/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1777062] Re: Logitech M535 mouse only pairs successfully after 4-5 tries
When it does pair, bluetoothctl doesn't report "ServicesResolved: no" or "Connected: no". -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1777062 Title: Logitech M535 mouse only pairs successfully after 4-5 tries To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1777062/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1822242] Re: No output to extenal thunderbolt3 display on Disco 19.04 beta
Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Freenode. To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/1822242/+editstatus and add the package name in the text box next to the word Package. [This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.] ** Tags added: bot-comment -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1822242 Title: No output to extenal thunderbolt3 display on Disco 19.04 beta To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1822242/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1822239] Re: NVIDIA Corporation GP107GLM [Quadro P1000 Mobile] [10de:1cbb] doesn't support 3D capabilities on Disco 19.04 beta
Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Freenode. To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/1822239/+editstatus and add the package name in the text box next to the word Package. [This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.] ** Tags added: bot-comment -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1822239 Title: NVIDIA Corporation GP107GLM [Quadro P1000 Mobile] [10de:1cbb] doesn't support 3D capabilities on Disco 19.04 beta To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1822239/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1817817] Re: To add power setting bin file for SAR support (QCA6174)
verify done. verification procedure: 1. find a machine that load ath10k module. install cosmic and make sure kernel module ath10k module is loaded. 2. apt update; apt upgrade. 3. rename the board-2.bin, reboot, and make sure wifi failed. (it means: the firmware is needed for the driver work properly). and then rename back. (at this time, linux-firmware version is: 1.175.1) 4. turn on the proposed channel, install linux-firmware 1.175.3. 5. make sure the md5sum for the board-2.bin is updated. 6. reboot, and confirm wifi still working well. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1817817 Title: To add power setting bin file for SAR support (QCA6174) To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1817817/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1817817] Re: To add power setting bin file for SAR support (QCA6174)
as do test in #3, the kernel used is 4.18.0-16-generic. ** Tags added: verification-done-cosmic ** Changed in: oem-priority Importance: High => Critical -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1817817 Title: To add power setting bin file for SAR support (QCA6174) To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1817817/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1817817] Re: To add power setting bin file for SAR support (QCA6174)
Per requirement from OEM customer, we need this change SRU to bionic. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1817817 Title: To add power setting bin file for SAR support (QCA6174) To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1817817/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1815665] Re: New upstream microreleases 9.5.16, 10.7 and 11.2
I was checking the tests, and so far I found: - Bionic all built and all tests good - Cosmic all built and just one flake test in diaspora-installer (re-triggered just now) - Xenial didn't build on ppc64el (WTH it did in the PPAs two weeks ago) This seems to be a locking issue in the builders - it runs since 18 hours and show messages like INFO: pkgstripfiles: waiting for lock (postgresql-plperl-9.5) ... Lets abort and restart that build for now, lets see after a few hours ... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1815665 Title: New upstream microreleases 9.5.16, 10.7 and 11.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pg-partman/+bug/1815665/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1814892] Re: [19.04 FEAT] qeth: Enhanced link speed - kernel part
** Changed in: ubuntu-z-systems Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1814892 Title: [19.04 FEAT] qeth: Enhanced link speed - kernel part To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1814892/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1822261] [NEW] Upgrade of procps disables net.ipv4.ip_forward=1
Public bug reported: Expected behavior: Settings in /etc/sysctl.conf won't be changed by an upgrade or there will be a prompt if the original file should be overwritten. What happened: After performing an upgrade of package procps IPv4Forwarding was disabled in /etc/sysctl.conf without asking: # Uncomment the next line to enable packet forwarding for IPv4 #net.ipv4.ip_forward=1 I was able to reproduce this behavior by using unattended-upgrades and also by upgrading manually (apt-get upgrade) My system: lsb_release -rd Description:Ubuntu 18.04.2 LTS Release:18.04 apt-cache policy procps procps: Installed: 2:3.3.12-3ubuntu1.1 Candidate: 2:3.3.12-3ubuntu1.1 Version table: *** 2:3.3.12-3ubuntu1.1 500 500 http://de.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 100 /var/lib/dpkg/status 2:3.3.12-3ubuntu1 500 500 http://de.archive.ubuntu.com/ubuntu bionic/main amd64 Packages ** Affects: procps (Ubuntu) Importance: Undecided Status: Confirmed ** Description changed: Expected behavior: Settings in /etc/sysctl.conf won't be changed by an upgrade or there will be a prompt if the original file should be overwritten. What happened: After performing an upgrade of package procps IPv4Forwarding was disabled in /etc/sysctl.conf without asking: # Uncomment the next line to enable packet forwarding for IPv4 - net.ipv4.ip_forward=1 + #net.ipv4.ip_forward=1 I was able to reproduce this behavior by using unattended-upgrades and also by upgrading manually (apt-get upgrade) My system: lsb_release -rd Description:Ubuntu 18.04.2 LTS Release:18.04 apt-cache policy procps procps: - Installed: 2:3.3.12-3ubuntu1.1 - Candidate: 2:3.3.12-3ubuntu1.1 - Version table: - *** 2:3.3.12-3ubuntu1.1 500 - 500 http://de.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages - 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages - 100 /var/lib/dpkg/status - 2:3.3.12-3ubuntu1 500 - 500 http://de.archive.ubuntu.com/ubuntu bionic/main amd64 Packages + Installed: 2:3.3.12-3ubuntu1.1 + Candidate: 2:3.3.12-3ubuntu1.1 + Version table: + *** 2:3.3.12-3ubuntu1.1 500 + 500 http://de.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages + 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages + 100 /var/lib/dpkg/status + 2:3.3.12-3ubuntu1 500 + 500 http://de.archive.ubuntu.com/ubuntu bionic/main amd64 Packages -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1822261 Title: Upgrade of procps disables net.ipv4.ip_forward=1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/procps/+bug/1822261/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1821882] Re: Screen is very dark and brightness cannot be adjusted
Is this a regression from older releases? when you say that disabling switchable graphics makes it use nvidia, I'd doubt that.. it should use intel then? ** Package changed: xorg (Ubuntu) => linux (Ubuntu) ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1821882 Title: Screen is very dark and brightness cannot be adjusted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1821882/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1821293] Re: Sometimes apache2 hang after boot
Today the same problem, no data added to /var/log/apache2/access.log, but in /var/log/apache2/error.log I found: [Fri Mar 29 09:25:39.351071 2019] [core:notice] [pid 2292] AH00051: child pid 11272 exit signal Segmentation fault (11), possible coredump in /etc/apache2 [Fri Mar 29 09:25:39.351073 2019] [core:error] [pid 2292] AH00546: no record of generation 0 of exiting child 11272 [Fri Mar 29 09:25:41.353823 2019] [core:notice] [pid 2292] AH00051: child pid 11301 exit signal Segmentation fault (11), possible coredump in /etc/apache2 [Fri Mar 29 09:25:41.353869 2019] [core:error] [pid 2292] AH00546: no record of generation 0 of exiting child 11301 [Fri Mar 29 09:25:42.357223 2019] [core:notice] [pid 2292] AH00051: child pid 11303 exit signal Segmentation fault (11), possible coredump in /etc/apache2 [Fri Mar 29 09:25:42.357255 2019] [core:error] [pid 2292] AH00546: no record of generation 0 of exiting child 11303 [Fri Mar 29 09:25:42.357285 2019] [core:notice] [pid 2292] AH00051: child pid 11304 exit signal Segmentation fault (11), possible coredump in /etc/apache2 [Fri Mar 29 09:25:42.357291 2019] [core:error] [pid 2292] AH00546: no record of generation 0 of exiting child 11304 [Fri Mar 29 09:25:43.364074 2019] [core:notice] [pid 2292] AH00051: child pid 11308 exit signal Segmentation fault (11), possible coredump in /etc/apache2 [Fri Mar 29 09:25:43.364104 2019] [core:error] [pid 2292] AH00546: no record of generation 0 of exiting child 11308 [Fri Mar 29 09:25:43.364131 2019] [core:notice] [pid 2292] AH00051: child pid 11309 exit signal Segmentation fault (11), possible coredump in /etc/apache2 [Fri Mar 29 09:25:43.364134 2019] [core:error] [pid 2292] AH00546: no record of generation 0 of exiting child 11309 [Fri Mar 29 09:25:43.364146 2019] [core:notice] [pid 2292] AH00051: child pid 11312 exit signal Segmentation fault (11), possible coredump in /etc/apache2 [Fri Mar 29 09:25:43.364149 2019] [core:error] [pid 2292] AH00546: no record of generation 0 of exiting child 11312 [Fri Mar 29 09:25:43.364161 2019] [core:notice] [pid 2292] AH00051: child pid 11313 exit signal Segmentation fault (11), possible coredump in /etc/apache2 [Fri Mar 29 09:25:43.364164 2019] [core:error] [pid 2292] AH00546: no record of generation 0 of exiting child 11313 [Fri Mar 29 09:25:44.365277 2019] [core:notice] [pid 2292] AH00051: child pid 11316 exit signal Segmentation fault (11), possible coredump in /etc/apache2 [Fri Mar 29 09:25:44.365311 2019] [core:error] [pid 2292] AH00546: no record of generation 0 of exiting child 11316 [Fri Mar 29 09:25:44.365332 2019] [core:notice] [pid 2292] AH00051: child pid 11318 exit signal Segmentation fault (11), possible coredump in /etc/apache2 [Fri Mar 29 09:25:44.365338 2019] [core:error] [pid 2292] AH00546: no record of generation 0 of exiting child 11318 [Fri Mar 29 09:25:44.365357 2019] [core:notice] [pid 2292] AH00051: child pid 11319 exit signal Segmentation fault (11), possible coredump in /etc/apache2 [Fri Mar 29 09:25:44.365363 2019] [core:error] [pid 2292] AH00546: no record of generation 0 of exiting child 11319 [Fri Mar 29 09:25:44.365382 2019] [core:notice] [pid 2292] AH00051: child pid 11321 exit signal Segmentation fault (11), possible coredump in /etc/apache2 [Fri Mar 29 09:25:44.365388 2019] [core:error] [pid 2292] AH00546: no record of generation 0 of exiting child 11321 [Fri Mar 29 09:25:44.365408 2019] [core:notice] [pid 2292] AH00051: child pid 11323 exit signal Segmentation fault (11), possible coredump in /etc/apache2 [Fri Mar 29 09:25:44.365414 2019] [core:error] [pid 2292] AH00546: no record of generation 0 of exiting child 11323 [Fri Mar 29 09:25:44.365434 2019] [core:notice] [pid 2292] AH00051: child pid 11325 exit signal Segmentation fault (11), possible coredump in /etc/apache2 [Fri Mar 29 09:25:44.365439 2019] [core:error] [pid 2292] AH00546: no record of generation 0 of exiting child 11325 [Fri Mar 29 09:25:44.365458 2019] [core:notice] [pid 2292] AH00051: child pid 11327 exit signal Segmentation fault (11), possible coredump in /etc/apache2 [Fri Mar 29 09:25:44.365476 2019] [core:error] [pid 2292] AH00546: no record of generation 0 of exiting child 11327 [Fri Mar 29 09:25:44.365506 2019] [core:notice] [pid 2292] AH00051: child pid 11329 exit signal Segmentation fault (11), possible coredump in /etc/apache2 [Fri Mar 29 09:25:44.365511 2019] [core:error] [pid 2292] AH00546: no record of generation 0 of exiting child 11329 I can't find any coredump -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1821293 Title: Sometimes apache2 hang after boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1821293/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1822044] Re: Laptop freezes after installation is finished when pressing "Restart Now"
*** This bug is a duplicate of bug 1822026 *** https://bugs.launchpad.net/bugs/1822026 ** This bug has been marked a duplicate of bug 1822026 [Dell Precision 7530/5530 with Nvidia Quadro P1000] Live USB freezes or cannot complete install when nouveau driver is loaded (crashing in GP100 code) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1822044 Title: Laptop freezes after installation is finished when pressing "Restart Now" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1822044/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1761497] Re: syslinux menu is displayed when a desktop ISO is powered from virt-manager
Switching from spice to VNC works around 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/1761497 Title: syslinux menu is displayed when a desktop ISO is powered from virt- manager To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/virt-manager/+bug/1761497/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1821239] Please test proposed package
Hello Seth, or anyone else affected, Accepted linux-firmware into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/linux- firmware/1.173.5 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1821239 Title: Update linux-firmware in bionic for 5.0-based hwe-edge kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1821239/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1808389] Re: iwlwifi Intel 8265 firmware crashing on lenovo x1 Gen 6
Hello James, or anyone else affected, Accepted linux-firmware into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/linux- firmware/1.173.5 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: linux-firmware (Ubuntu Bionic) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1808389 Title: iwlwifi Intel 8265 firmware crashing on lenovo x1 Gen 6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1808389/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1817817] Please test proposed package
Hello AceLan, or anyone else affected, Accepted linux-firmware into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/linux- firmware/1.173.5 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1817817 Title: To add power setting bin file for SAR support (QCA6174) To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1817817/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1822261] Re: Upgrade of procps disables net.ipv4.ip_forward=1
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: procps (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1822261 Title: Upgrade of procps disables net.ipv4.ip_forward=1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/procps/+bug/1822261/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1794055] Please test proposed package
Hello bugproxy, or anyone else affected, Accepted linux-firmware into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/linux- firmware/1.173.5 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1794055 Title: [Witherspoon-DD2.2][Ubu 18.10] [4.18.0-7-generic ] OS booting thrown with nouveau errors; OS booted successfully To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1794055/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1821933] Re: Touch input is offset with two screens (even appearing on the wrong screen)
No additional scaling is set, everything is 100%. It does feel like there is some acceleration going on though. The offset seems consistent to shell, apps and the backdrop. e.g. I position a window on the right hand screen and I can grab the top of it by dragging on the left screen. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1821933 Title: Touch input is offset with two screens (even appearing on the wrong screen) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1821933/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1761497] Re: syslinux menu is displayed when a desktop ISO is powered from virt-manager and SPICE enabled.
** Summary changed: - syslinux menu is displayed when a desktop ISO is powered from virt-manager + syslinux menu is displayed when a desktop ISO is powered from virt-manager and SPICE enabled. ** Description changed: If a desktop ISO is booted from virt-manager it displays the syslinux menu (text menu that a user gets when a key is pressed on boot) The menu is not displayed when the image is booted from a command line with virsh start. I expect the behaviour to be the same than booting on hardware, the syslinux should not be displayed and the ISO boots to ubiquity-dm (Ubiquity dialog showing the options try or install Ubuntu) This is always reproducible on the same machine with ISOs of different flavours, but not all the physical machines running the same version of libvirt and qemu exhibit this behaviour. + + Switching to VNC works around this issue. + ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: virt-manager 1:1.5.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 ApportVersion: 2.20.9-0ubuntu2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Apr 5 15:03:40 2018 InstallationDate: Installed on 2014-07-15 (1360 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140520) PackageArchitecture: all SourcePackage: virt-manager UpgradeStatus: Upgraded to bionic on 2018-03-24 (11 days ago) ** Description changed: If a desktop ISO is booted from virt-manager it displays the syslinux menu (text menu that a user gets when a key is pressed on boot) The menu is not displayed when the image is booted from a command line with virsh start. I expect the behaviour to be the same than booting on hardware, the syslinux should not be displayed and the ISO boots to ubiquity-dm (Ubiquity dialog showing the options try or install Ubuntu) This is always reproducible on the same machine with ISOs of different flavours, but not all the physical machines running the same version of libvirt and qemu exhibit this behaviour. - Switching to VNC works around this issue. - + Switching to VNC or booting directly from virt-manager without the UI + works around this issue. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: virt-manager 1:1.5.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 ApportVersion: 2.20.9-0ubuntu2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Apr 5 15:03:40 2018 InstallationDate: Installed on 2014-07-15 (1360 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140520) PackageArchitecture: all SourcePackage: virt-manager UpgradeStatus: Upgraded to bionic on 2018-03-24 (11 days ago) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1761497 Title: syslinux menu is displayed when a desktop ISO is powered from virt- manager and SPICE enabled. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/virt-manager/+bug/1761497/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1822032] Re: perf_event_open02 in ubuntu_ltp_syscalls failed on Cosmic s390x
Spotted on Bionic as well. ** Also affects: linux (Ubuntu Bionic) 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/1822032 Title: perf_event_open02 in ubuntu_ltp_syscalls failed on Cosmic s390x To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1822032/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1821933] Re: Touch input is offset with two screens (even appearing on the wrong screen)
It sounds like touches are being scaled to stage coordinates instead of view coordinates. So a touch halfway across the touch screen gets mapped to a desktop location halfway across all monitors. Just a guess. ** No longer affects: gnome-shell-extension-desktop-icons (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1821933 Title: Touch input is offset with two screens (even appearing on the wrong screen) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1821933/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1817817] Re: To add power setting bin file for SAR support (QCA6174)
** Tags added: verification-needed-bionic ** Changed in: oem-priority Assignee: (unassigned) => Yuan-Chen Cheng (ycheng-twn) ** Changed in: oem-priority Status: Confirmed => 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/1817817 Title: To add power setting bin file for SAR support (QCA6174) To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1817817/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1821863] Re: Need to add Intel CML related pci-id's
leaving cosmic out, this will only be needed in disco and bionic. ** Description changed: + [Impact] + Please make it happen in the coming oem-kernel as there will be a flood - of Intel CML platforms that would need it. Thank you. + of Intel Comet Lake (CML) platforms that would need it. Thank you. The same is needed for the rest of the stack. + + [Test case] + + Test that i915 graphics works on CML. + + [Regression potential] + + None really, these only add a bunch of new pci-id's across the stack. ** Also affects: mesa (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: libdrm (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: xorg-server (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: linux-oem (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: libdrm (Ubuntu Bionic) Assignee: (unassigned) => Timo Aaltonen (tjaalton) ** Changed in: mesa (Ubuntu Bionic) Assignee: (unassigned) => Timo Aaltonen (tjaalton) ** Changed in: xorg-server (Ubuntu Bionic) Assignee: (unassigned) => Timo Aaltonen (tjaalton) ** Description changed: [Impact] Please make it happen in the coming oem-kernel as there will be a flood of Intel Comet Lake (CML) platforms that would need it. Thank you. The same is needed for the rest of the stack. + + CML is basically another iteration of Skylake/Kabylake/Coffee Lake, and + doesn't need other changes than pci-id's and support for the PCH + (similar to Cannon point, already supported by the kernel). [Test case] Test that i915 graphics works on CML. [Regression potential] None really, these only add a bunch of new pci-id's across the stack. ** Also affects: linux (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/1821863 Title: Need to add Intel CML related pci-id's To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1821863/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1821867] Re: network interface is down after post-install reboot of a default disco installation
Successfully verified on cosmic - since I was able to login to a newly installed system (that was installed using 'apt-setup/proposed=true') right away: $ ssh ubuntu@hwe0007 ubuntu@hwe0007's password: Welcome to Ubuntu 18.10 (GNU/Linux 4.18.0-17-generic s390x) * Documentation: https://help.ubuntu.com * Management: https://landscape.canonical.com * Support:https://ubuntu.com/advantage The programs included with the Ubuntu system are free software; the exact distribution terms for each program are described in the individual files in /usr/share/doc/*/copyright. Ubuntu comes with ABSOLUTELY NO WARRANTY, to the extent permitted by applicable law. To run a command as administrator (user "root"), use "sudo ". See "man sudo_root" for details. ubuntu@hwe0007:~$ apt-cache policy netplan.io netplan.io: Installed: 0.96-0ubuntu0.18.10.2 Candidate: 0.96-0ubuntu0.18.10.2 Version table: *** 0.96-0ubuntu0.18.10.2 500 500 http://us.ports.ubuntu.com/ubuntu-ports cosmic-proposed/main s390x Packages 100 /var/lib/dpkg/status 0.40.2.2 500 500 http://us.ports.ubuntu.com/ubuntu-ports cosmic-updates/main s390x Packages 0.40.2 500 500 http://us.ports.ubuntu.com/ubuntu-ports cosmic/main s390x Packages ubuntu@hwe0007:~$ Adjusting verification tag ... ** Tags removed: verification-needed-cosmic ** Tags added: verification-done-cosmic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1821867 Title: network interface is down after post-install reboot of a default disco installation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1821867/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1821933] Re: Touch input is offset with two screens (even appearing on the wrong screen)
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-shell (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1821933 Title: Touch input is offset with two screens (even appearing on the wrong screen) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1821933/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1821863] Re: Need to add Intel CML related pci-id's
** Changed in: linux (Ubuntu Bionic) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1821863 Title: Need to add Intel CML related pci-id's To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1821863/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1785165] Re: firmware update on fwupdate version 10-3 not work on some AMI's firmwares
set back to fix committed based on #24. @Brian, please kindly review again. ** Changed in: fwupdate (Ubuntu Bionic) Status: Incomplete => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1785165 Title: firmware update on fwupdate version 10-3 not work on some AMI's firmwares To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1785165/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1821863] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1821863 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1821863 Title: Need to add Intel CML related pci-id's To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1821863/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1821935] Re: Samba panic or segfault
** Tags removed: server-triage-discuss -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1821935 Title: Samba panic or segfault To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1821935/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1815665] Re: New upstream microreleases 9.5.16, 10.7 and 11.2
- Xenial ppc64el build complete now, tests will run over the weekend. - The cosmic diaspora test succeeded on the re-run as expected, thereby all of Cosmic is good as well Marking B&C as verified, X has to wait a bit due to the build issue causing a delay ** Tags removed: verification-needed-bionic verification-needed-cosmic ** Tags added: verification-done-bionic verification-done-cosmic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1815665 Title: New upstream microreleases 9.5.16, 10.7 and 11.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pg-partman/+bug/1815665/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1819716] Re: linux: 4.15.0-47.50 -proposed tracker
4.15.0-47.50 - generic Regression test CMPL, RTB. Issue to note in amd64: ubuntu_kernel_selftests - global.get_metadata in seccomp (bug 1811057) raw_skew in timer (bug 1811194) ubuntu_kvm_unit_tests - apic-split timeouted (bug 1821390) apic timeouted (bug 1748103) vmware_backdoors (bug 1821393) svm (bug 1821903) ubunut_ltp - binfmt_misc02 (bug 1822246) ubuntu_ltp_syscalls - inotify08 (bug 1775784) fanotify09-2 (bug 1804594) sync_file_range02 (bug 1819116) xfstests - timed out on ext4 generic/430 test (bug 1755999) Issue to note in arm64: hwclock - issue for HP m400 (bug 1716603) ubuntu_bpf - test_map failed (bug 1788562) ubuntu_kernel_selftests - cpu-hotplug failed on moonshot (bug 1809701) global.get_metadata in seccomp (bug 1811057) raw_skew in timer (bug 1811194) ubuntu_kvm_unit_tests - gicv3-ipi and gicv3-active failed on Moonshot (bug 1790825) ubuntu_ltp_syscalls - inotify08 (bug 1775784) fanotify09-2 (bug 1804594) sync_file_range02 (bug 1819116) xfstests - timed out on ext4 generic/430 test (bug 1755999) Issue to note in i386: ubuntu_bpf - Some test in test_verifier failed on i386 Bionic (bug 1788578) ubuntu_kernel_selftests - reuseport_bpf_numa in net (bug 1812638) global.get_metadata in seccomp (bug 1811057) raw_skew in timer (bug 1811194) Kprobe event string type argument in ftrace (bug 1812645) ubuntu_kvm_smoke_test - timed out waiting for dnsmasq lease (bug 1802056) ubuntu_kvm_unit_tests - all 29 test failed on i386 (bug 1822235) ubuntu_ltp_syscalls - inotify08 (bug 1775784) fanotify09-2 (bug 1804594) sync_file_range02 (bug 1819116) xfstests - timed out on ext4 generic/430 test (bug 1755999) Issue to note in ppc64le (P8): ubuntu_bpf - test_map failed (bug 1788562) ubuntu_kernel_selftests - reuseport_bpf_numa in net (bug 1812638) TRACE_syscall.ptrace_syscall_dropped in seccomp (bug 1812796) global.get_metadata in seccomp (bug 1811057) raw_skew in timer (bug 1811194) ebb in powerpc (bug 1812805) Kprobe event argument syntax in ftrace (bug 1812809) ubuntu_kvm_unit_tests - sprs timed out (bug 1740017) ubuntu_ltp_syscalls - fallocate05 (bug 1783880) inotify08 (bug 1775784) fanotify09-2 (bug 1804594) sync_file_range02 (bug 1819116) xfstests - timed out on ext4 generic/430 test (bug 1755999) 48 / 49 tests were run, missing: xfstests Issue to note in ppc64le (P9): hwclock - hwclock test failed on Power9 system with Bionic kernel (bug 1775858) ubuntu_bpf - test_map failed (bug 1788562) ubuntu_btrfs_kernel_fixes - test 9e622d6bea0202e9fe267955362c01918562c09b timeouted ubuntu_kernel_selftests - reuseport_bpf_numa in net (bug 1812638) TRACE_syscall.ptrace_syscall_dropped in seccomp (bug 1812796) global.get_metadata in seccomp (bug 1811057) raw_skew in timer (bug 1811194) ebb in powerpc (bug 1812805) tm-unavailable in powerpc (bug 1813129) ubuntu_kvm_unit_tests - sprs timed out (bug 1740017) buntu_ltp_syscalls - fallocate05 (bug 1783880) inotify08 (bug 1775784) fanotify09-2 (bug 1804594) sync_file_range02 (bug 1819116) 47 / 48 tests were run, missing: ubuntu_btrfs_kernel_fixes Issue to note in s390x (KVM): ubuntu_bpf - test_map failed (bug 1788562) ubuntu_kernel_selftests - reuseport_dualstack in net (bug 1812843) TRACE_syscall in seccomp (bug 1812824) global.get_metadata in seccomp (bug 1811057) ftrace (bug 1812836) ubuntu_ltp_syscalls - inotify08 (bug 1775784) fanotify09-2 (bug 1804594) ubuntu_lxc - Container "reboot" is defined (bug 1788574) 47 / 48 tests were run, missing: ubuntu_btrfs_kernel_fixes Issue to note in s390x (Ubuntu on LPAR): ubuntu_bpf - test_map failed (bug 1788562) ubuntu_kernel_selftests - reuseport_dualstack in net (bug 1812843) TRACE_syscall in seccomp (bug 1812824) global.get_metadata in seccomp (bug 1811057) ftrace (bug 1812836) ubuntu_ltp_syscalls - inotify08 (bug 1775784) fanotify09-2 (bug 1804594) sync_file_range02 (bug 1819116) ubuntu_lxc - lxc-test-api-reboot failed (bug 1776381) Container "reboot" is defined (bug 1788574) 47 / 48 tests were run, missing: ubuntu_btrfs_kernel_fixes Issue to note in s390x (zVM): ubuntu_bpf - test_map failed (bug 1788562) ubuntu_kernel_selftests - reuseport_dualstack in net (bug 1812843) TRACE_syscall in seccomp (bug 1812824) global.get_metadata in seccomp (bug 1811057) ftrace (bug 1812836) ubuntu_kvm_unit_tests - skey failed (bug 1778705) ubuntu_ltp_syscalls - inotify08 (bug 1775784) fanotify09-2 (bug 1804594) sync_file_range02 (bug 1819116) ubuntu_lxc - Container "reboot" is defined (bug 1788574) Note: No xfstests for P9 as it does not have a scratch drive Note: Missing ubuntu_btrfs_kernel_fixes for s390x (bug 1809860) ** Changed in: kernel-sru-workflow/regression-testing Status: Confirmed => Fix Released ** Changed in: kernel-sru-workflow/regression-testing Assignee: Canonical Kernel Team (canonical-kernel-team) => Po-Hsu Lin (cypressyew) ** Tags added: regression-testing-passed -- You received this bug noti
[Bug 1723039] Re: With 2 monitors, touches to the touch screen appear across both (and in the wrong place)
Touches should never be reaching the external monitor regardless of whether the internal screen is on or off. So we're tracking that as bug 1821933 now. ** Bug watch added: GNOME Bug Tracker #766762 https://gitlab.gnome.org/766762 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1723039 Title: with 2 monitors, touchscreen is not disabled when the internal display is disabled To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1723039/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1723039] Re: with 2 monitors, touchscreen is not disabled when the internal display is disabled
Apparently Fix Released in disco (mutter 3.31.4 onward) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1723039 Title: with 2 monitors, touchscreen is not disabled when the internal display is disabled To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1723039/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1723039] Re: with 2 monitors, touchscreen is not disabled when the internal display is disabled
Actually it sounds like this might be a feature added after: https://bugzilla.gnome.org/show_bug.cgi?id=766762 ** Bug watch added: GNOME Bug Tracker #742598 https://gitlab.gnome.org/742598 ** Also affects: mutter via https://gitlab.gnome.org/742598 Importance: Unknown Status: Unknown ** Package changed: gnome-shell (Ubuntu) => mutter (Ubuntu) ** Changed in: mutter (Ubuntu) Status: New => 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/1723039 Title: with 2 monitors, touchscreen is not disabled when the internal display is disabled To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1723039/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1723039] Re: with 2 monitors, touchscreen is not disabled when the internal display is disabled
The fix was https://gitlab.gnome.org/GNOME/mutter/commit/d30301c0 ** Also affects: mutter (Ubuntu Disco) Importance: Undecided Status: Fix Released ** Tags removed: artful -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1723039 Title: with 2 monitors, touchscreen is not disabled when the internal display is disabled To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1723039/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1822269] [NEW] mktemp does not handle -p option when --tmpdir option goes after -p option
Public bug reported: # This is correct. The printed temp file name is in folder / $ mktemp -u --tmpdir -p / /tmp.aFd4MwfGDU # after swapping the options, mktemp do not handle the -p option correctly. # swapping options should not affect the output. $ mktemp -u -p / --tmpdir /tmp/tmp.FkTPrEsTMs This should be a software bug, not relevant to any hardware. ** Affects: coreutils (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/1822269 Title: mktemp does not handle -p option when --tmpdir option goes after -p option To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/1822269/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1822269] Re: mktemp does not handle -p option when --tmpdir option goes after -p option
Note: coreutils verions as shown by dpkg -l command: $ dpkg -l coreutils Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-=-===-===-=== ii coreutils 8.21-1ubuntu5.4 amd64 GNU core utilities -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1822269 Title: mktemp does not handle -p option when --tmpdir option goes after -p option To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/1822269/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1822270] [NEW] Debconf readline frontend does not show options
Public bug reported: AFFECTED RELEASE: Bionic PACKAGE VERSION: debconf - 1.5.66 DESCRIPTION: When upgrading the kernel on a recent Bionic minimal image, the user is prompted to resolve a conflict in the file /boot/grub/menu.lst. The minimal images do not have dialog/whiptail installed, so debconf falls back to using the readline frontend. The user sees the prompt: "What would you like to do about menu.lst?" but is not presented with the list of options to choose from. If a valid option is typed in, debconf will continue processing correctly and the list of options appears on the screen. See also https://pastebin.ubuntu.com/p/8xvSn88SKG/ STEPS TO REPRODUCE: Launch the minimal Bionic image with serial 20190212 http://cloud- images.ubuntu.com/minimal/releases/bionic/release-20190212/ubuntu-18.04 -minimal-cloudimg-amd64.img for example via multipass and run `apt-get update` and `apt-get dist- upgrade`. ** Affects: debconf (Ubuntu) Importance: Undecided Status: New ** Tags: bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1822270 Title: Debconf readline frontend does not show options To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debconf/+bug/1822270/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1808389] Re: iwlwifi Intel 8265 firmware crashing on lenovo x1 Gen 6
I have had no issues anymore since I switched to my self built 1.177~ppa0f22c85 (PPA) - while before they were rather common. Thanks for accepting that into Bionic-Proposed. I have switched to 1.173.5 from Proposed and unplugged the cables. The install (a downgrade for me as outlined) itself worked fine, I'll reboot now and check on Monday I'll check if any connectivity issues came up over the weekend. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1808389 Title: iwlwifi Intel 8265 firmware crashing on lenovo x1 Gen 6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1808389/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1818638] Re: segfault on Samba v4.3.11-Ubuntu
Hi, A few minutes ago (10:15), I had a crash. This is the trace : The Samba 'panic action' script, /usr/share/samba/panic-action, was called for PID 20037 (/usr/sbin/smbd). This means there was a problem with the program, such as a segfault. Below is a backtrace for this process generated with gdb, which shows the state of the program at the time the error occurred. The Samba log files may contain additional information about the problem. If the problem persists, you are encouraged to first install the samba-dbg package, which contains the debugging symbols for the Samba binaries. Then submit the provided information as a bug report to Ubuntu by visiting this link: https://launchpad.net/ubuntu/+source/samba/+filebug [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". 0x7f5f9a37a07a in __GI___waitpid (pid=20038, stat_loc=stat_loc@entry=0x7fffd405d190, options=options@entry=0) at ../sysdeps/unix/sysv/linux/waitpid.c:29 #0 0x7f5f9a37a07a in __GI___waitpid (pid=20038, stat_loc=stat_loc@entry=0x7fffd405d190, options=options@entry=0) at ../sysdeps/unix/sysv/linux/waitpid.c:29 #1 0x7f5f9a2f2fbb in do_system (line=line@entry=0x55ae6bc2b610 "/usr/share/samba/panic-action 20037") at ../sysdeps/posix/system.c:148 #2 0x7f5f9a2f339a in __libc_system (line=line@entry=0x55ae6bc2b610 "/usr/share/samba/panic-action 20037") at ../sysdeps/posix/system.c:184 #3 0x7f5f9cd9e8d1 in smb_panic_s3 (why=) at ../source3/lib/util.c:802 #4 0x7f5f9db11f1f in smb_panic (why=why@entry=0x7f5f9db55ab8 "internal error") at ../lib/util/fault.c:166 #5 0x7f5f9db12136 in fault_report (sig=) at ../lib/util/fault.c:83 #6 sig_fault (sig=) at ../lib/util/fault.c:94 #7 #8 smbXsrv_session_create (conn=conn@entry=0x55ae6bc18c80, now=now@entry=131983244855041970, _session=_session@entry=0x7fffd405db40) at ../source3/smbd/smbXsrv_session.c:1158 #9 0x7f5f9d6a3643 in reply_sesssetup_and_X (req=req@entry=0x55ae6bc29a00) at ../source3/smbd/sesssetup.c:953 #10 0x7f5f9d6dfe67 in switch_message (type=, req=req@entry=0x55ae6bc29a00) at ../source3/smbd/process.c:1649 #11 0x7f5f9d6e1bb3 in construct_reply (deferred_pcd=0x0, encrypted=false, seqnum=0, unread_bytes=0, size=76, inbuf=0x0, xconn=0x55ae6bc18c80) at ../source3/smbd/process.c:1685 #12 process_smb (xconn=xconn@entry=0x55ae6bc18c80, inbuf=, nread=76, unread_bytes=0, seqnum=0, encrypted=, deferred_pcd=0x0) at ../source3/smbd/process.c:1932 #13 0x7f5f9d6e321c in smbd_server_connection_read_handler (xconn=0x55ae6bc18c80, fd=40) at ../source3/smbd/process.c:2531 #14 0x7f5f9ba31917 in run_events_poll (ev=0x55ae6bc0c120, pollrtn=, pfds=0x55ae6bc20b00, num_pfds=4) at ../source3/lib/events.c:257 #15 0x7f5f9ba31b77 in s3_event_loop_once (ev=0x55ae6bc0c120, location=) at ../source3/lib/events.c:326 #16 0x7f5f9a67bd3d in _tevent_loop_once () from /usr/lib/x86_64-linux-gnu/libtevent.so.0 #17 0x7f5f9a67bedb in tevent_common_loop_wait () from /usr/lib/x86_64-linux-gnu/libtevent.so.0 #18 0x7f5f9d6e4578 in smbd_process (ev_ctx=0x55ae6bc0c120, msg_ctx=, sock_fd=40, interactive=) at ../source3/smbd/process.c:4032 #19 0x55ae6b29ae12 in smbd_accept_connection (ev=0x55ae6bc0c120, fde=, flags=, private_data=) at ../source3/smbd/server.c:646 #20 0x7f5f9ba31917 in run_events_poll (ev=0x55ae6bc0c120, pollrtn=, pfds=0x55ae6bc20b00, num_pfds=6) at ../source3/lib/events.c:257 #21 0x7f5f9ba31b77 in s3_event_loop_once (ev=0x55ae6bc0c120, location=) at ../source3/lib/events.c:326 #22 0x7f5f9a67bd3d in _tevent_loop_once () from /usr/lib/x86_64-linux-gnu/libtevent.so.0 #23 0x7f5f9a67bedb in tevent_common_loop_wait () from /usr/lib/x86_64-linux-gnu/libtevent.so.0 #24 0x55ae6b299099 in smbd_parent_loop (parent=0x55ae6bc0e920, ev_ctx=0x55ae6bc0c120) at ../source3/smbd/server.c:1011 #25 main (argc=, argv=) at ../source3/smbd/server.c:1663 A debugging session is active. Inferior 1 [process 20037] will be detached. Quit anyway? (y or n) [answered Y; input not from terminal] It happened when a colleague has wanted to browse the samba directory from outlook to save a file. You can find attached logfiles and cores. ** Attachment added: "traces 29-03-19.zip" https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1818638/+attachment/5250525/+files/traces%2029-03-19.zip -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1818638 Title: segfault on Samba v4.3.11-Ubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1818638/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1771185] Re: Secondary monitor not connecting in 18.04 LTS
I can also confirm the problem. The Ubuntu 18.04LTS (updated everything) does NOT sense when I disconnect the HDMI. There is no change in /sys. This uis the mainb problem, I guess. The events does not generate screen switching. Very annoying when the screen locked and disconnected from external monitor, the notebook display remaions black! I checked the status, and it STILL shown connected but the HDMI monitor was disconnected: root@notebook:~# cat /sys/class/drm/card0-HDMI-A-1/status connected root@notebook:~# cat /sys/class/drm/card0-HDMI-A-1/status connected root@notebook:~# cat /sys/class/drm/card0-HDMI-A-1/status HW: Dell Lattitude 7490 Sometimes work, sometimes NOT. It is very annoying when I work with the notebook, it's screen remains black after I disconnect the external monitor. I created Keyboard shortucts to force screen UP: Lspci: 00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v6/7th Gen Core Processor Host Bridge/DRAM Registers (rev 02) 00:02.0 VGA compatible controller: Intel Corporation HD Graphics 620 (rev 02) 00:04.0 Signal processing controller: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem (rev 02) 00:14.0 USB controller: Intel Corporation Sunrise Point-LP USB 3.0 xHCI Controller (rev 21) 00:14.2 Signal processing controller: Intel Corporation Sunrise Point-LP Thermal subsystem (rev 21) 00:15.0 Signal processing controller: Intel Corporation Sunrise Point-LP Serial IO I2C Controller #0 (rev 21) 00:15.1 Signal processing controller: Intel Corporation Sunrise Point-LP Serial IO I2C Controller #1 (rev 21) 00:15.2 Signal processing controller: Intel Corporation Sunrise Point-LP Serial IO I2C Controller #2 (rev 21) 00:15.3 Signal processing controller: Intel Corporation Sunrise Point-LP Serial IO I2C Controller #3 (rev 21) 00:16.0 Communication controller: Intel Corporation Sunrise Point-LP CSME HECI #1 (rev 21) 00:16.3 Serial controller: Intel Corporation Device 9d3d (rev 21) 00:17.0 SATA controller: Intel Corporation Sunrise Point-LP SATA Controller [AHCI mode] (rev 21) 00:1c.0 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port #1 (rev f1) 00:1c.2 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port #3 (rev f1) 00:1f.0 ISA bridge: Intel Corporation Intel(R) 100 Series Chipset Family LPC Controller/eSPI Controller - 9D4E (rev 21) 00:1f.2 Memory controller: Intel Corporation Sunrise Point-LP PMC (rev 21) 00:1f.3 Audio device: Intel Corporation Sunrise Point-LP HD Audio (rev 21) 00:1f.4 SMBus: Intel Corporation Sunrise Point-LP SMBus (rev 21) 00:1f.6 Ethernet controller: Intel Corporation Ethernet Connection (4) I219-LM (rev 21) 01:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS525A PCI Express Card Reader (rev 01) 02:00.0 Network controller: Intel Corporation Wireless 8265 / 8275 (rev 78) -- root@notebook:~# uname -a Linux notebook 4.18.0-16-generic #17~18.04.1-Ubuntu SMP Tue Feb 12 13:35:51 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux -- -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1771185 Title: Secondary monitor not connecting in 18.04 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1771185/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1821713] Re: linux-raspi2: 4.4.0-1106.114 -proposed tracker
Hardware Certification have completed testing this -proposed kernel. No regressions were observed, results are available here: http://people.canonical.com/~hwcert/sru- testing/raspi2/4.4.0-1106.114/raspi2-4.4-proposed-published.html ** Tags added: certification-testing-passed ** Changed in: kernel-sru-workflow/certification-testing Status: In Progress => 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/1821713 Title: linux-raspi2: 4.4.0-1106.114 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1821713/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1821933] Re: Touch input is offset with two screens (even appearing on the wrong screen)
The problem appears to be that clutter_input_device_evdev_translate_coordinates has no idea that the stage might include multiple monitors: https://gitlab.gnome.org/GNOME/mutter/blob/master/clutter/clutter/evdev /clutter-input-device-evdev.c#L1509 Sadly I can't see any information that would help to correct it either. It would be a bit of a redesign. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1821933 Title: Touch input is offset with two screens (even appearing on the wrong screen) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1821933/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1821933] Re: Touch input is offset with two screens (even appearing on the wrong screen)
That would be a consequence of the "touch screen" input device not having any relation in software to the "screen" output device. They are very separate things :( -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1821933 Title: Touch input is offset with two screens (even appearing on the wrong screen) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1821933/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1794629] Re: CVE-2018-15473 - User enumeration vulnerability
@seth, apt-upgrade doesnt update even in 18.04, I had to compile new ver 7.9p1 and replace the sshd bin file..!, don't know why it is still not pushed to the main repo!. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1794629 Title: CVE-2018-15473 - User enumeration vulnerability To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1794629/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1813587] Re: libunistring and libidn ftbfs on 18.04 LTS
Hello Matthias, or anyone else affected, Accepted libidn into cosmic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/libidn/1.33-2.2ubuntu1.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-cosmic to verification-done-cosmic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-cosmic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: libidn (Ubuntu Cosmic) Status: In Progress => Fix Committed ** Tags added: verification-needed-cosmic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1813587 Title: libunistring and libidn ftbfs on 18.04 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libidn/+bug/1813587/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1653448] Re: [SRU] Mouse fails to scroll apps in Xfce Settings Manager
Hello Kev, or anyone else affected, Accepted xfce4-settings into cosmic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/xfce4-settings/4.13.4-1ubuntu1.18.10.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-cosmic to verification-done-cosmic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-cosmic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: xfce4-settings (Ubuntu Cosmic) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-cosmic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1653448 Title: [SRU] Mouse fails to scroll apps in Xfce Settings Manager To manage notifications about this bug go to: https://bugs.launchpad.net/xfce4-settings/+bug/1653448/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1822274] [NEW] 9e622d6bea0202e9fe267955362c01918562c09b in ubuntu_btrfs_kernel_fixes timeouted on B P9
Public bug reported: This test will timeout on our P9 node "baltar" A manual run shows that the sysbench command in this test will take about 2 hours to complete: # sysbench --num-threads=1 --test=fileio --file-num=81920 --file-total-size=80M --file-block-size=1K --file-io-mode=sync --file-test-mode=seqwr prepare ... ... ... Creating file test_file.81917 Creating file test_file.81918 Creating file test_file.81919 83886080 bytes written in 7231.40 seconds (0.01 MiB/sec). # And our timeout threshold is exactly 2 hours. An easy fix for this is to bump the threshold. But it's weird that this test only fail on Bionic 4.15. On Bionic 4.18, it took only 90 minute to finish this test. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-46-generic 4.15.0-46.49 ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18 Uname: Linux 4.15.0-46-generic ppc64le AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mar 29 07:04 seq crw-rw 1 root audio 116, 33 Mar 29 07:04 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.6 Architecture: ppc64el ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDmesg: Date: Fri Mar 29 09:55:09 2019 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0451:80ff Texas Instruments, Inc. Bus 001 Device 004: ID 0557:2419 ATEN International Co., Ltd Bus 001 Device 002: ID 0557:7000 ATEN International Co., Ltd Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub PciMultimedia: ProcFB: 0 astdrmfb ProcKernelCmdLine: root=UUID=acd1a0d7-f6fc-4130-928c-c8b11ad6e4be ro console=hvc0 ProcLoadAvg: 0.09 0.04 0.27 1/1367 5463 ProcLocks: 1: FLOCK ADVISORY WRITE 3539 00:17:524 0 EOF 2: POSIX ADVISORY WRITE 3875 00:17:602 0 EOF 3: FLOCK ADVISORY WRITE 3912 00:17:598 0 EOF 4: POSIX ADVISORY WRITE 3902 00:17:580 0 EOF 5: POSIX ADVISORY WRITE 1820 00:17:373 0 EOF ProcSwaps: Filename TypeSizeUsedPriority /swap.img file 8388544 0 -2 ProcVersion: Linux version 4.15.0-46-generic (buildd@bos02-ppc64el-009) (gcc version 7.3.0 (Ubuntu 7.3.0-16ubuntu3)) #49-Ubuntu SMP Wed Feb 6 09:32:48 UTC 2019 RelatedPackageVersions: linux-restricted-modules-4.15.0-46-generic N/A linux-backports-modules-4.15.0-46-generic N/A linux-firmware 1.173.3 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) VarLogDump_list: total 0 cpu_cores: Number of cores present = 40 cpu_coreson: Number of cores online = 40 cpu_dscr: DSCR is 16 cpu_freq: min: 2.862 GHz (cpu 159) max: 2.862 GHz (cpu 1) avg: 2.862 GHz cpu_runmode: Could not retrieve current diagnostics mode, No kernel interface to firmware cpu_smt: SMT=4 ** Affects: ubuntu-kernel-tests Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Tags: apport-bug bionic ppc64el uec-images ** Also affects: linux (Ubuntu Bionic) 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/1822274 Title: 9e622d6bea0202e9fe267955362c01918562c09b in ubuntu_btrfs_kernel_fixes timeouted on B P9 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1822274/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1822273] [NEW] freeplane hang on edit input
Public bug reported: open existing map try edit fields freeplan hang need to kill ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: freeplane 1.6.13-1 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.6 Architecture: amd64 Date: Fri Mar 29 10:50:00 2019 InstallationDate: Installed on 2018-10-18 (161 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: freeplane UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: freeplane (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/1822273 Title: freeplane hang on edit input To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/freeplane/+bug/1822273/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1821933] Re: Touch input is offset with two screens (even appearing on the wrong screen)
Experimental fix: https://gitlab.gnome.org/GNOME/mutter/commit/4a06424b9c1de7242cec0613bc1fd53c832d9144.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1821933 Title: Touch input is offset with two screens (even appearing on the wrong screen) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1821933/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1822271] [NEW] Xenial update: 4.4.177 upstream stable release
Public bug reported: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: 4.4.177 upstream stable release from git://git.kernel.org/ ** Affects: linux (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Xenial) Importance: Medium Assignee: Stefan Bader (smb) Status: In Progress ** Tags: kernel-stable-tracking-bug ** Changed in: linux (Ubuntu) Status: New => Confirmed ** Tags added: kernel-stable-tracking-bug ** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Xenial) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Xenial) Status: New => In Progress ** Changed in: linux (Ubuntu Xenial) Assignee: (unassigned) => Stefan Bader (smb) ** Changed in: linux (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1822271 Title: Xenial update: 4.4.177 upstream stable release To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1822271/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1818974] Re: Ubuntu 18.04 Kernel 4.18 - Standby wakeup user session crash
SMART long offline test was successful. Everything is fine. I formatted the ext4 partition. I assume the corruption came, because I turned of the external HDD hub too early several times. But this weird bug happened one time I unplugged the external HDD before waking up my ThinkPad T460P. PS: I hope the issue can be found and fixed. A crashing user session is a bit weird. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1818974 Title: Ubuntu 18.04 Kernel 4.18 - Standby wakeup user session crash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818974/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1804513] Re: Cosmic: Mixxx 2.1.3 is not stable with Qt5
> Solutions would be to go to a 2.1.3 Qt4 build a 2.1.7 Qt4 build or a 2.2.0 Qt5 build. Sorry, I missed your 2.1.x proposals earlier. My previous comments is referring only to the 2.2.x proposal. For 2.1.x, please see the document Simon linked for details of the policy (specifically https://wiki.ubuntu.com/StableReleaseUpdates#New_upstream_microreleases). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1804513 Title: Cosmic: Mixxx 2.1.3 is not stable with Qt5 To manage notifications about this bug go to: https://bugs.launchpad.net/mixxx/+bug/1804513/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1804513] Re: Cosmic: Mixxx 2.1.3 is not stable with Qt5
We can certainly consider this _if_ the current version in Cosmic really is a problem for users that cannot practically be fixed any other way. But please could you actually demonstrate that? For the only bug actually linked, surely a cherry-pick would be lower regression risk for existing users? > We as Mixxx team do not support 2.1.x qt5 builds. So the user is pretty alone with issues with throws a bad light on Mixxx. We certainly appreciate involvement from upstreams, but I don't think this qualifies as an SRU justification in itself. "We...do not support" is certainly not a reason. You're entitled to choose not to support what you wish (or more specifically you get to choose what you want to spend your time on), but such a position is certainly not a justification to ignore the stability* promises we make to Ubuntu users. The focus on stable release updates must be on users, and their expectation is of stability* in that, in general, no major version updates are expected to pull the rug out from under their feet. What can we do to fix these problems for this set of users? How difficult would it be to cherry-pick bug fixes for them? If cherry-picking is practical and would avoid problems for users successfully using the Cosmic package today, why aren't we doing that? Note that there are only four months left of support for Cosmic, and that Disco will be out soon. It seems to be that the benefit of a major update now would be limited, compared to the consequences of ignoring our stability* promise to users. A user who tries to start using the Cosmic package in three weeks will have the option of using Disco. A user who is successfully using the Cosmic package today might never use Ubuntu again if we break our stability promise and this destroys their performance. These are the promises we make to users for packages that ship as part of the distribution. I can understand that you may find this frustrating, but please remember that users of stable* distributions _want_ this policy. If you would prefer to have control of your own release management directly to your users, you might consider shipping a snap (http://snapcraft.io/). * Stability means different things to different people. In this context I don't mean "no bugs"; obviously there are bugs and achieving no bugs is generally not practical. In this context I mean "doesn't suddenly change behaviour". To be clear, I'm not ruling out an update to 2.2.x in Cosmic, but I think there needs to be a real justification that includes an explanation of the actual bugs actually impacting users in Cosmic and why the fixes cannot practically be cherry-picked. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1804513 Title: Cosmic: Mixxx 2.1.3 is not stable with Qt5 To manage notifications about this bug go to: https://bugs.launchpad.net/mixxx/+bug/1804513/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1675949] Re: perf report can't annotate kernel and dbgsym package has wrong addresses
** Also affects: linux (Ubuntu Disco) Importance: Medium Assignee: Paolo Pisati (p-pisati) Status: Confirmed ** Also affects: linux (Ubuntu Cosmic) 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/1675949 Title: perf report can't annotate kernel and dbgsym package has wrong addresses To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1675949/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1821480] Re: UEFI model PC using CMS coult not update ubuntu-18.04.2
I update software updater to update developer option update. kenel update to 4.15.0-47-generic. shudown and power-on up need a lot of time. and a lot of ureadahead found in syslog. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1821480 Title: UEFI model PC using CMS coult not update ubuntu-18.04.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1821480/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
