[Bug 1777099] Re: [backport] DRM devices opened by logind stay referenced indefinitely by PID 1
the irc conversation about this patch: https://pastebin.canonical.com/p/k7YkQ8rmSR/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1777099 Title: [backport] DRM devices opened by logind stay referenced indefinitely by PID 1 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1777099/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1768230] Re: Long time booting : Failed to connect to lvmetad. Falling back to device scanning.
And this warning is not really reassuring: sudo update-initramfs -u update-initramfs: Generating /boot/initrd.img-4.15.0-20-generic I: The initramfs will attempt to resume from /dev/dm-1 I: (/dev/mapper/xubuntu--vg-swap_1) I: Set the RESUME variable to override this. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1768230 Title: Long time booting : Failed to connect to lvmetad. Falling back to device scanning. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1768230/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1777514] Re: gnome-shell crashed with SIGABRT (corrupted double-linked list) in free() from ... _mesa_glsl_release_builtin_functions() from _mesa_destroy_shader_compiler_caches() from _mesa_destr
Not sure if this was the correct "corrupted double linked list" issue but if it is, it was happening under Wayland. Fresh install. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1777514 Title: gnome-shell crashed with SIGABRT (corrupted double-linked list) in free() from ... _mesa_glsl_release_builtin_functions() from _mesa_destroy_shader_compiler_caches() from _mesa_destroy_shader_compiler() from one_time_fini() from __run_exit_handlers() from exit() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1777514/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1776333] Re: linux: 4.13.0-46.51 -proposed tracker
4.13.0-46.51 - generic Regression test CMPL, RTB. Issue to note in amd64: libhugetlbfs - failed 7 killed by signal 7 bad config 1 monotonic_time - lodygin constantly failed with tsc test (bug 1732620) ubuntu_kvm_unit_tests - 27 failed on amaura, 4 failed on lodygin, 11 failed on michael, 16 failed on zeppo ubuntu_ltp_syscalls - inotify07 failed with X/X-LTS/A kernel (bug 1774387) inotify08 failed with X/X-LTS/X-HWE/A kernel (bug 1775784) fanotify09 failed with A/T kernel (bug 1775153) ubuntu_lxc - lxc-test-ubuntu failed (Failed to start networking in ubuntu-cloud container) Issue to note in arm64: hwclock - issue for HP m400 (bug 1716603) libhugetlbfs - failed 1 killed by signal 1 bad config 1 ubuntu_bpf - failed to build on ARM64 (bug 1675395) ubuntu_kvm_smoke_test - Unable to create KVM with uvtool on arm64 system (bug 1749427) ubuntu_ltp_syscalls - inotify07 failed with X/X-LTS/A kernel (bug 1774387) inotify08 failed with X/X-LTS/X-HWE/A kernel (bug 1775784) fanotify09 failed with A/T kernel (bug 1775153) Issue to note in i386: libhugetlbfs - failed 4 killed by signal 4 bad config 1 ubuntu_bpf - test_verifier failed on Artful i386 (bug 1755101) test_maps failed (bug 1750724) ubuntu_kvm_unit_tests - 28 failed on pepe ubuntu_ltp_syscalls - inotify07 failed with X/X-LTS/A kernel (bug 1774387) inotify08 failed with X/X-LTS/X-HWE/A kernel (bug 1775784) fanotify09 failed with A/T kernel (bug 1775153) Issue to note in ppc64le: libhugetlbfs - failed 7 killed by signal 6 ubuntu_bpf - failed to build on ppc64le (bug 1750793) ubuntu_kvm_smoke_test - unable to start kvm, uvtool template issue (bug 1755118) ubuntu_kvm_unit_tests - sprs hang (bug 1740017) ubuntu_ltp_syscalls - inotify07 failed with X/X-LTS/A kernel (bug 1774387) inotify08 failed with X/X-LTS/X-HWE/A kernel (bug 1775784) fanotify09 failed with A/T kernel (bug 1775153) Issue to note in s390x (zKVM): libhugetlbfs - failed 11 killed by signal 7 bad config 1 ubuntu_bpf - failed to build on s390x (bug 1711299) ubuntu_kvm_unit_tests - Nested virtualization with KVM is not supported on s390x ubuntu_ltp_syscalls - inotify07 failed with X/X-LTS/A kernel (bug 1774387) inotify08 failed with X/X-LTS/X-HWE/A kernel (bug 1775784) fanotify09 failed with A/T kernel (bug 1775153) Issue to note in s390x (zVM): libhugetlbfs - failed 11 killed by signal 7 bad config 1 ubuntu_bpf - failed to build on s390x (bug 1711299) ubuntu_kvm_smoke_test - uvtool-libvirt needs arch specific template (bug 1729854) ubuntu_kvm_unit_tests - skey failed (0 tests) ubuntu_ltp_syscalls - inotify07 failed with X/X-LTS/A kernel (bug 1774387) inotify08 failed with X/X-LTS/X-HWE/A kernel (bug 1775784) fanotify09 failed with A/T kernel (bug 1775153) ** 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 notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1776333 Title: linux: 4.13.0-46.51 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1776333/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1704297] Re: Bluetooth audio stuck in A2DP profile ([pulseaudio] module-bluez5-device.c: Refused to switch profile to headset_head_unit: Not connected)
I have a similar issue. I'm trying to get the mic working on Beats X headset. These series of patches helped me to solve the issue: https://patchwork.freedesktop.org/patch/178198/ https://patchwork.freedesktop.org/patch/178199/ https://patchwork.freedesktop.org/patch/178200/ https://patchwork.freedesktop.org/patch/178201/ Can we get them upstream? I'm on Ubuntu 18.04. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1704297 Title: Bluetooth audio stuck in A2DP profile ([pulseaudio] module- bluez5-device.c: Refused to switch profile to headset_head_unit: Not connected) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1704297/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 19554] Re: Could (have an option to) convert dirs outside home
** Changed in: utf8-migration-tool (Debian) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/19554 Title: Could (have an option to) convert dirs outside home To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/utf8-migration-tool/+bug/19554/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1777586] [NEW] Ubuntu Server 18.04 LTS aacraid error
Public bug reported: I upgraded from a previous version of Ubuntu 14.04LTS to 18.04LTS and am now running into these raid adapter driver errors. The server ran fine in older version. My apologies as I lost the exact version, but it never had any errors like this version. Now when ever I try to copy files to the RAID 5 drive, or untar a file, I get these errors now after a few MB's of written data. Linux batboat 4.15.0-23-generic #25-Ubuntu SMP Wed May 23 18:02:16 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux batboat:/var/log$ lsb_release -rd Description:Ubuntu 18.04 LTS Release:18.04 I have tried the IRQ debugging tips to no avail. I loaded in Debian9.4.0 and it only briefly showed this error once. But appears to be much more resilient and appears to work fine. Jun 19 00:02:21 batboat kernel: [ 498.770839] aacraid: Host adapter reset request. SCSI hang ? Jun 19 00:02:37 batboat kernel: [ 514.139167] aacraid: Host adapter reset request. SCSI hang ? Jun 19 00:02:37 batboat kernel: [ 514.795083] aacraid :03:09.0: Adapter health - 199 Jun 19 00:02:37 batboat kernel: [ 514.800376] aacraid :03:09.0: outstanding cmd: midlevel-0 Jun 19 00:02:37 batboat kernel: [ 514.800378] aacraid :03:09.0: outstanding cmd: lowlevel-0 Jun 19 00:02:37 batboat kernel: [ 514.800381] aacraid :03:09.0: outstanding cmd: error handler-0 Jun 19 00:02:37 batboat kernel: [ 514.800383] aacraid :03:09.0: outstanding cmd: firmware-5 Jun 19 00:02:37 batboat kernel: [ 514.800385] aacraid :03:09.0: outstanding cmd: kernel-0 Jun 19 00:02:37 batboat kernel: [ 514.800391] sd 4:0:0:0: Device offlined - not ready after error recovery Jun 19 00:02:37 batboat kernel: [ 514.800394] sd 4:0:0:0: Device offlined - not ready after error recovery Jun 19 00:02:37 batboat kernel: [ 514.800396] sd 4:0:0:0: Device offlined - not ready after error recovery Jun 19 00:02:37 batboat kernel: [ 514.800399] sd 4:0:0:0: Device offlined - not ready after error recovery Jun 19 00:02:37 batboat kernel: [ 514.800401] sd 4:0:0:0: Device offlined - not ready after error recovery ** 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/1777586 Title: Ubuntu Server 18.04 LTS aacraid error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1777586/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1777586] Re: Ubuntu Server 18.04 LTS aacraid error
** Attachment added: "lspci log file" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1777586/+attachment/5154210/+files/lspci-vnvn.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1777586 Title: Ubuntu Server 18.04 LTS aacraid error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1777586/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1777586] Re: Ubuntu Server 18.04 LTS aacraid error
** Attachment added: "Version Log File" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1777586/+attachment/5154209/+files/version.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1777586 Title: Ubuntu Server 18.04 LTS aacraid error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1777586/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1777418] Re: crash on armhf (autopkgtest)
Upstream acked the patch, will be in git soon and then we can pull it into Cosmic. Later upstream releases can then sync over it. ** Changed in: pgpool2 (Ubuntu) Status: New => Triaged -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1777418 Title: crash on armhf (autopkgtest) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pgpool2/+bug/1777418/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1775170] Re: [SRU] Fixing empty create swift container dialog after upgrading horizon from newton to ocata
Hello Corey I paste directory structure and result of python manage.py collectstatic --no-input https://pastebin.ubuntu.com/p/vjgmjHcTf6/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1775170 Title: [SRU] Fixing empty create swift container dialog after upgrading horizon from newton to ocata To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1775170/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1755106] Re: Bug 1755106
Will anyone ever tell me what to look for when the problem occurs? I did a fresh reinstall of the whole 18.04 system from scratch, but the problem is still there. I could provide more information if someone tells me what to look for. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1755106 Title: /org/gnome/settings-daemon/plugins/media-keys/custom-keybindings/ fails to load To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-settings-daemon/+bug/1755106/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1704297] Re: Bluetooth audio stuck in A2DP profile ([pulseaudio] module-bluez5-device.c: Refused to switch profile to headset_head_unit: Not connected)
Alexey, Indeed it appears that PulseAudio, even upstream, is missing those patches. However this is not the right place to request their inclusion. Please talk to the upstream PulseAudio people instead: https://www.freedesktop.org/wiki/Software/PulseAudio/Documentation/User/Community/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1704297 Title: Bluetooth audio stuck in A2DP profile ([pulseaudio] module- bluez5-device.c: Refused to switch profile to headset_head_unit: Not connected) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1704297/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1777586] 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 1777586 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 ** Tags added: bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1777586 Title: Ubuntu Server 18.04 LTS aacraid error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1777586/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1777418] Re: crash on armhf (autopkgtest)
** Merge proposal linked: https://code.launchpad.net/~paelzer/ubuntu/+source/pgpool2/+git/pgpool2/+merge/348198 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1777418 Title: crash on armhf (autopkgtest) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pgpool2/+bug/1777418/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1777514] Re: gnome-shell crashed with SIGABRT (corrupted double-linked list) in free() from ... _mesa_glsl_release_builtin_functions() from _mesa_destroy_shader_compiler_caches() from _mesa_destr
Hmm, problem: https://errors.ubuntu.com/problem/c1f46d2d92c2be5d4c6d68c44ef0817ccea8ccab is not being deduplicated accurately by the robots at errors.ubuntu.com. 5 hours ago the stack trace was in Mesa as mentioned above. And now it's something different. So we must generalize this bug to match :S ** Summary changed: - gnome-shell crashed with SIGABRT (corrupted double-linked list) in free() from ... _mesa_glsl_release_builtin_functions() from _mesa_destroy_shader_compiler_caches() from _mesa_destroy_shader_compiler() from one_time_fini() from __run_exit_handlers() from exit() + gnome-shell crashed with SIGABRT (corrupted double-linked list) in free() ** No longer affects: mesa (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1777514 Title: gnome-shell crashed with SIGABRT (corrupted double-linked list) in free() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1777514/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 798414] Re: update-initramfs should produce a more helpful error message when there isn't enough free space
** Changed in: initramfs-tools (Ubuntu) Assignee: Deon Joubert (02deon-j) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/798414 Title: update-initramfs should produce a more helpful error message when there isn't enough free space To manage notifications about this bug go to: https://bugs.launchpad.net/initramfs-tools/+bug/798414/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1776344] Re: linux-gcp: 4.15.0-1010.10 -proposed tracker
4.15.0-1010.10 - gcp Regression test CMPL, RTB. Issue to note in gcp: ubuntu_kvm_unit_tests - failed due to no KVM support ubuntu_ltp - test disabled ubuntu_ltp_syscalls - inotify08 failed with X/X-LTS/X-HWE/A/B kernel (bug 1775784) ubuntu_lxc - lxc-test-usernic.in failed on Bionic (bug 1775809) ubuntu_quota_smoke_test - need the -extra package (bug 1777114) ubuntu_unionmount_overlayfs_suite - File unexpectedly on union layer (bug 1751243) Skipped / blacklisted: * libhugetlbfs * ubuntu_nbd_smoke_test * ubuntu_seccomp * ubuntu_zram_smoke_test ** 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 notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1776344 Title: linux-gcp: 4.15.0-1010.10 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1776344/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1776808] Re: Please merge 5.6-4 from Debian Sid
This bug was fixed in the package brltty - 5.6-4ubuntu1 --- brltty (5.6-4ubuntu1) cosmic; urgency=low * Merge from Debian Sid (LP: #1776808). Remaining changes: - Add brltty-setup, installed in both the udeb and the normal system. - Add initramfs integration to run brltty-setup if necessary before plymouth starts. - Add ubiquity integration to propagate any brltty configuration to the target system. - Add udev rules file that uses brltty-udev.service to activate via systemd. - Disable brltty.service by default, but enable it if the user configures Braille at install time for a non-USB display. - Don't install /etc/brltty.conf in the package. - Enable brltty at startup on the target system if the alternate installer is used. - debian/brltty.sh: Update path /sbin/brltty to /bin/brltty brltty (5.6-4) unstable; urgency=medium * Cherry-pick python brlapi close fix, to avoid orca accumulating brlapi connections. * Cherry-pick at-spi2 initialization fix. * Cherry-pick xbrlapi patch to be able to type any keysym. * Bump Standards-Version to 4.1.4 (no changes). -- Simon Quigley Wed, 13 Jun 2018 21:55:05 -0500 ** Changed in: brltty (Ubuntu) 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/1776808 Title: Please merge 5.6-4 from Debian Sid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/brltty/+bug/1776808/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1776209] Comment bridged from LTC Bugzilla
--- Comment From heinz-werner_se...@de.ibm.com 2018-06-19 03:49 EDT--- IBM bugzilla status -> closed, Fix Released within 18.10 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1776209 Title: [18.10 FEAT] Upgrade openssl-ibmca >=2.0.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1776209/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1777600] [NEW] chzdev can't find modprobe
Public bug reported: Description: only when trying to change some attributes chzdev fails because it cant find modprobe under Ubuntu 18.04 root@m83lp09:~# chzdev zfcp --type datarouter=0 dbflevel=5 sh: 1: /usr/sbin/modprobe: not found zfcp device type configure failed Error: Command failed (exit code 127): /usr/sbin/modprobe -r zfcp root@m83lp09:~# whereis modprobe modprobe: /sbin/modprobe /etc/modprobe.d /lib/modprobe.d /usr/share/man/man8/modprobe.8.gz Potential solution ? : adding a symlink is a workaround, is this path hardcoded? ** Affects: linux (Ubuntu) Importance: Undecided Assignee: Skipper Bug Screeners (skipper-screen-team) Status: New ** Tags: architecture-s39064 bugnameltc-168976 severity-high targetmilestone-inin1804 ** Tags added: architecture-s39064 bugnameltc-168976 severity-high targetmilestone-inin1804 ** Changed in: ubuntu Assignee: (unassigned) => Skipper Bug Screeners (skipper-screen-team) ** Package changed: ubuntu => linux (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1777600 Title: chzdev can't find modprobe To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1777600/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1775743] Re: [regression] Cosmic daily images 20180606-11 install but boots only to grub prompt on EFI systems
** Merge proposal linked: https://code.launchpad.net/~sil2100/ubiquity/+git/ubiquity/+merge/348201 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1775743 Title: [regression] Cosmic daily images 20180606-11 install but boots only to grub prompt on EFI systems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1775743/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1777605] [NEW] package libjpeg9-dev (not installed) failed to install/upgrade: trying to overwrite '/usr/include/jerror.h', which is also in package libjpeg-turbo8-dev:amd64 1.5.2-0ubuntu5
Public bug reported: dpkg: error processing archive /var/cache/apt/archives/libjpeg9-dev_1%3a9b-2_amd64.deb (--unpack): trying to overwrite '/usr/include/jerror.h', which is also in package libjpeg-turbo8-dev:amd64 1.5.2-0ubuntu5 dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) Errors were encountered while processing: /var/cache/apt/archives/libjpeg9-dev_1%3a9b-2_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Package DistroRelease: Ubuntu 18.04 Package: libjpeg9-dev (not installed) ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Tue Jun 19 02:01:07 2018 ErrorMessage: trying to overwrite '/usr/include/jerror.h', which is also in package libjpeg-turbo8-dev:amd64 1.5.2-0ubuntu5 InstallationDate: Installed on 2018-05-24 (25 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.1 SourcePackage: libjpeg9 Title: package libjpeg9-dev (not installed) failed to install/upgrade: trying to overwrite '/usr/include/jerror.h', which is also in package libjpeg-turbo8-dev:amd64 1.5.2-0ubuntu5 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: libjpeg9 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1777605 Title: package libjpeg9-dev (not installed) failed to install/upgrade: trying to overwrite '/usr/include/jerror.h', which is also in package libjpeg-turbo8-dev:amd64 1.5.2-0ubuntu5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libjpeg9/+bug/1777605/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1777601] [NEW] can not delete a non-empty directory on remote NAS smb share
Public bug reported: Using Lubuntu 18.04 LTS graphical file manager pcmanfm, can not delete a non-empty subdirectory on a remote Network Attached Storage samba smb shared folder. Lubuntu 16.04 LTS did not behave this way. With 18.04 LTS, must navigate through the entire directory structure, deleting files in each individual subdirectory. As a work-around, I found that I can delete a non-empty subdir on a NAS smb share from the Terminal command line using the "rm -rf" command. I have confirmed that the same behavior exists in Ubuntu 18.04 LTS using the nautilus file manager and also Ubuntu Mate 18.04 LTS using the caja file manager. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pcmanfm 1.2.5-3ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic i686 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: i386 Config_pcmanfm_System_Lubuntu: Error: [Errno 2] No such file or directory: '/etc/xdg/pcmanfm/Lubuntu/lubuntu.conf' CurrentDesktop: LXDE Date: Tue Jun 19 01:04:26 2018 InstallationDate: Installed on 2018-05-04 (46 days ago) InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Release i386 (20180426) SourcePackage: pcmanfm Udisks_dump: Error: [Errno 2] No such file or directory: 'udisks': 'udisks' UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: pcmanfm (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug bionic i386 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1777601 Title: can not delete a non-empty directory on remote NAS smb share To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pcmanfm/+bug/1777601/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1777577] Re: cant upgrade to new version
** Tags added: artful2bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1777577 Title: cant upgrade to new version To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1777577/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1777579] Re: 18.04 Dekstop LTS DNS behavior (systemd-resolved)
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/1777579/+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/1777579 Title: 18.04 Dekstop LTS DNS behavior (systemd-resolved) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1777579/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1712866] Re: icons from qt applications disappear after screen lock/sleep
This happening to me in 18.04 Bionic: the icons disappear after lock/sleep and do not appear on login. Restarting with Alt+F2 + r makes them reappear. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1712866 Title: icons from qt applications disappear after screen lock/sleep To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/1712866/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1776822] Re: linux: 4.4.0-130.156 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: Incomplete => 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/1776822 Title: linux: 4.4.0-130.156 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1776822/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1777094] Re: dnsmasq started too early, not getting all interfaces
setting optional: false does not solve the problem, a systemctl restart dnsmasq is still required. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1777094 Title: dnsmasq started too early, not getting all interfaces To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1777094/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1777601] Re: can not delete a non-empty directory on remote NAS smb share
Clarification: when I try to delete a non-empty NAS smb subdirectory using pcmanfm, the directory disappears from the window, but the directory is not really gone. If I navigate away from the current folder and then come back (or if I press F5 to reload the folder), the subdirectory that I thought that I had just deleted reappears on the screen. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1777601 Title: can not delete a non-empty directory on remote NAS smb share To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pcmanfm/+bug/1777601/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1777612] [NEW] Scrollbar : missing arrows & Resize...
Public bug reported: For few days I notice that the arrows to go to left/right and up/down are missing... I notice, too, that is impossible to resize the windows eventhough we use the Window Menu... we can't minimize width less than the half of the screen... Please, help ! @HP-14-TS-Notebook-PC:~$ uname -a Linux HP-14-TS-Notebook-PC 4.15.0-23-generic #25-Ubuntu SMP Wed May 23 18:02:16 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux @HP-14-TS-Notebook-PC:~$ lsb_release -d Description:Ubuntu 18.04 LTS @HP-14-TS-Notebook-PC:~$ libreoffice --version LibreOffice 6.0.4.2 00m0(Build:2) Thank you in advance. Best regards, Sab ** Affects: libreoffice (Ubuntu) Importance: Undecided Status: New ** Tags: arrow scroll width -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1777612 Title: Scrollbar : missing arrows & Resize... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1777612/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1768390] Re: BadMatch error in X_GLXSwapBuffers running OpenGL apps with nvidia-driver-390
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: libglvnd (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/1768390 Title: BadMatch error in X_GLXSwapBuffers running OpenGL apps with nvidia- driver-390 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libglvnd/+bug/1768390/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1752772] Re: r8169 ethernet card don't work after returning from suspension
4.15.0-24-generic from bionic-proposed has not solved the issue. 2 network cards - one Intel and the other Realtek (r8169). Realtek not found after suspend on previous kernel, now not found on boot either. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1752772 Title: r8169 ethernet card don't work after returning from suspension To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1752772/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1760201] Re: ubuntu 18.04 GDM - missing icons and letters on login screen with nouveau + Wayland
I'd like to report that this issue is also being reproduced with nouveau on NVIDIA GF108. However, my dmesg does not seem to contain nouveau errors. dmesg sample containing nouveau (as above): [5.254956] nouveau :01:00.0: enabling device (0006 -> 0007) [5.255096] nouveau :01:00.0: NVIDIA GF108 (0c1480a1) [5.285074] nouveau :01:00.0: bios: version 70.08.a8.00.2b [5.393498] nouveau :01:00.0: fb: 2048 MiB DDR3 [5.449440] nouveau :01:00.0: DRM: VRAM: 2048 MiB [5.449441] nouveau :01:00.0: DRM: GART: 1048576 MiB [5.449444] nouveau :01:00.0: DRM: TMDS table version 2.0 [5.449454] nouveau :01:00.0: DRM: DCB version 4.0 [5.449455] nouveau :01:00.0: DRM: DCB outp 00: 02010300 [5.449457] nouveau :01:00.0: DRM: DCB conn 00: [5.451120] nouveau :01:00.0: DRM: MM: using COPY0 for buffer copies [5.485363] nouveau :01:00.0: DRM: allocated 1024x768 fb: 0x6, bo 10a8d043 [5.488176] nouveau :01:00.0: fb0: nouveaufb frame buffer device [5.512017] [drm] Initialized nouveau 1.3.1 20120801 for :01:00.0 on minor 1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1760201 Title: ubuntu 18.04 GDM - missing icons and letters on login screen with nouveau + Wayland To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1760201/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 603421]
http://bottom.rickelsky.org Del -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/603421 Title: package mbr 1.1.10-2 failed to install/upgrade: package mbr is already installed and configured To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/603421/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 816197] Re: Cannot change city name font for gtk client- too small
This will be fixed upstream in 2.6.x. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/816197 Title: Cannot change city name font for gtk client- too small To manage notifications about this bug go to: https://bugs.launchpad.net/freeciv/+bug/816197/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1777615] [NEW] OKULAR - can't set print default to duplex
Public bug reported: I filed this bug report with KDE: https://bugs.kde.org/show_bug.cgi?id=395517 They suggested "What you can try to do is open a bug against Ubuntu and ask whether they can backport the commit mentioned in comment 1 to the Qt version in Ubuntu 18.04... " https://wiki.qt.io/Qt_5.12_Release https://codereview.qt-project.org/#/c/226881/ ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: okular 4:17.12.3-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: KDE Date: Tue Jun 19 11:57:15 2018 InstallationDate: Installed on 2018-06-15 (3 days ago) InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: okular UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: okular (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/1777615 Title: OKULAR - can't set print default to duplex To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/okular/+bug/1777615/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1777612] Re: Scrollbar : missing arrows & Resize...
** Description changed: For few days I notice that the arrows to go to left/right and up/down are missing... - I notice, too, that is impossible to resize the windows eventhough if we - use the Windows Menu... we can't minimise width less than the half of - the screen... + I notice, too, that is impossible to resize the windows eventhough we + use the Window Menu... we can't minimize width less than the half of the + screen... Please, help ! @HP-14-TS-Notebook-PC:~$ uname -a Linux HP-14-TS-Notebook-PC 4.15.0-23-generic #25-Ubuntu SMP Wed May 23 18:02:16 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux @HP-14-TS-Notebook-PC:~$ lsb_release -d Description: Ubuntu 18.04 LTS @HP-14-TS-Notebook-PC:~$ libreoffice --version LibreOffice 6.0.4.2 00m0(Build:2) - Thank you in advance. Best regards, Sab ** Tags added: scroll ** Tags added: arrow width -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1777612 Title: Scrollbar : missing arrows & Resize... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1777612/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1777099] Re: [backport] DRM devices opened by logind stay referenced indefinitely by PID 1
** Changed in: systemd (Ubuntu) Status: Triaged => In Progress ** Also affects: systemd (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: systemd (Ubuntu Bionic) Status: New => In Progress ** Changed in: systemd (Ubuntu Bionic) Importance: Undecided => High ** Changed in: systemd (Ubuntu Bionic) Assignee: (unassigned) => Alberto Milone (albertomilone) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1777099 Title: [backport] DRM devices opened by logind stay referenced indefinitely by PID 1 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1777099/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 405294] Re: A2DP Bluetooth audio skips terribly ["Skipping NNN us (= MMM bytes) in audio stream"]
Launchpad has imported 38 comments from the remote bug at https://bugs.freedesktop.org/show_bug.cgi?id=58746. If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. On 2012-12-25T13:10:22+00:00 farbing wrote: I'm using a bluetooth headset with pulseaudio. Whenever the connection temporarily drops (e.g. by moving too far from the bt device), I get the message in the syslog: [bluetooth] module-bluetooth-device.c: Skipping 24275 us (= 4280 bytes) in audio stream and the audio lags behind after that. A workaround is to suspend and resume the sink using "pactl suspend-sink 1 && pactl suspend-sink 0", after which the audio is in sync again. Using the same headset on Windows doesn't show the same behavior. Reply at: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/405294/comments/109 On 2016-02-13T23:32:25+00:00 Z-mike-y wrote: Bumping this due to the fact that this bug is still very much present in 5, 6, 7, 8 and renders the act of using a bluetooth headset on most linux operating systems using pulseaudio utterly useless. The slightest blip throws the whole audio out of sync with the video. I noticed this when trying to watch a movie from a 6ft distance away (sill in range) but occasionally the signal would blip and cause said problem. Evidence in the logs: Three of many lines: Feb 13 17:25:49 saturn.net.overtmind.com pulseaudio[30599]: [bluetooth] module-bluez5-device.c: Skipping 5124656 us (= 903988 bytes) in audio stream Feb 13 17:25:49 saturn.net.overtmind.com pulseaudio[30599]: [bluetooth] mod ule-bluez5-device.c: Skipping 220060 us (= 38816 bytes) in audio stream Feb 13 17:25:49 saturn.net.overtmind.com pulseaudio[30599]: [bluetooth] module-bluez5-device.c: Skipping 346147 us (= 61060 bytes) in audio stream Packages tested in Fedora 23: rawhide: bluez-5.37-2.fc24.x86_64 pulseaudio-8.0-3.fc24.x86_64 and also tried initially with: bluez-5.36-1.fc23.x86_64 pulseaudio-7.1-1.fc23.x86_64 The rest of my findings are here, where someone else has also mentioned seeing this on Gentoo with PA 5,6 - I have tested 7 and 8: https://www.reddit.com/r/linuxquestions/comments/45n710/pulseaudio_bluetooth_degraded_signal_out_of_sync/ Reply at: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/405294/comments/126 On 2016-02-14T09:53:05+00:00 Raymond wrote: If you want audio sync with video after audio transmission is broken, you need the application to skip some audio and restart audio playback Reply at: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/405294/comments/127 On 2016-02-14T10:21:54+00:00 Z-mike-y wrote: Shouldn't the buffer reset after detecting a skip event? Reply at: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/405294/comments/128 On 2016-05-04T01:37:04+00:00 Sb wrote: (In reply to xenith from comment #3) > Shouldn't the buffer reset after detecting a skip event? This would seem to be the most logical thing. The way it is now, even stopping and re-starting the audio stream doesn't fix the latency issue if there has ever been a brief blip in the current Bluetooth connection. Quite a showstopper for watching video with bluetooth speakers/headphones. Reply at: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/405294/comments/130 On 2016-05-08T15:46:53+00:00 Arun Raghavan wrote: I've tried to reproduce this behaviour in the past, but it doesn't always happen this way (but I have seen the delays turn up on drops at times). If someone has a patch that definitely works (or a way to repro that is 100% reliable), I can try to look at this. Reply at: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/405294/comments/131 On 2016-05-10T15:58:47+00:00 Sb wrote: (In reply to Arun Raghavan from comment #5) > I've tried to reproduce this behaviour in the past, but it doesn't always > happen this way (but I have seen the delays turn up on drops at times). If > someone has a patch that definitely works (or a way to repro that is 100% > reliable), I can try to look at this. I have about 6 different cheap Chinese bluetooth speakers, and they all exhibit this behavior. They all use the A2DP protocol, are you possibly seeing different behavior with HSP/HFP? Reply at: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/405294/comments/132 -
[Bug 1776452] Re: Fail to set DNS server and search domain when customize Ubuntu18.04 to DHCP IP by cloud-init
Attached the cust.cfg, Thanks Christian. ** Attachment added: "cust.cfg" https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1776452/+attachment/5154229/+files/cust.cfg -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1776452 Title: Fail to set DNS server and search domain when customize Ubuntu18.04 to DHCP IP by cloud-init To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1776452/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1777600] Re: chzdev can't find modprobe
** Also affects: ubuntu-z-systems 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/1777600 Title: chzdev can't find modprobe To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1777600/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1777620] [NEW] failure during install. not this package is broken
Public bug reported: failure during install. now this package is broken ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: shim-signed 1.34.9+13-0ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 .proc.sys.kernel.moksbstate_disabled: Error: [Errno 2] No such file or directory: '/proc/sys/kernel/moksbstate_disabled' ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 BootEFIContents: fw fwupx64.efi CurrentDesktop: ubuntu:GNOME Date: Tue Jun 19 11:27:34 2018 EFIBootMgr: Error: command ['efibootmgr', '-v'] failed with exit code 2: EFI variables are not supported on this system. EFITables: Jun 19 11:15:06 X1-18 fwupd[3544]: disabling plugin because: failed to startup uefi: UEFI firmware updating not supported SourcePackage: shim-signed UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: shim-signed (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/1777620 Title: failure during install. not this package is broken To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shim-signed/+bug/1777620/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1752772] Re: r8169 ethernet card don't work after returning from suspension
Correction! Realtek network card driver not loaded on boot but after loading with sudo modprobe -r r8169 and sudo modprobe r8169 is still present after suspend so solved one problem and created another. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1752772 Title: r8169 ethernet card don't work after returning from suspension To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1752772/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1777621] [NEW] xrandr fails to change into the native resolution, useless setup whitout Wayland
Public bug reported: Hello I have found bugs from Ubuntu 18.04 (form 16.04 by do-release-upgrade) a) xrandr fails to change into native resolution b) disabling Wayland cause “Out of Range” → can’t login at all (no login via HDMI or virtual TTY:s) c) X fails to detect old VGA monitor (ViewSonic VA902) native resolution (this is a persistent bug) I have used dual monitor setup over a decade, started with Etch and turned into Ubuntu some years ago. First monitor is connected via HDMI and second one by VGA. During Ubuntu installations/updates resolution has been problem, with xrandr etc I have managed situation until now. I have tested: 1) 16.04 & Radeon works OK with 60 Hz VGA modeline 2) 18.04 & Radeon: HDMI is OK but VGA cant’t go into the native resolution 3) 18.04 & Intel: HDMI is OK but VGA cant’t go into the native resolution 4) 18.04 & Radeon VGA without Wayland is Out of Range and useless 5) 18.04 & Intel & xrandr with “easy” modeline do not work 6) 18.04 & Radeon & xrandr with “easy” modeline do not work pg@pg-desktop:~$ xrandr --newmode 1280x1024_40.00 69.75 1280 1336 1472 1664 1024 1025 1028 1048 -HSync +Vsync pg@pg-desktop:~$ xrandr --verbose --addmode XWAYLAND1 1280x1024_40.00 pg@pg-desktop:~$ xrandr --verbose --output XWAYLAND1 --mode 1280x1024_40.00 screen 0: 2560x1024 677x271 mm 95.98dpi crtc 1: 1280x1024_40.00 40.00 +1280+0 "XWAYLAND1" xrandr: Configure crtc 1 failed crtc 0: disable crtc 1: disable screen 0: revert crtc 0: revert crtc 1: revert pg@pg-desktop:~$ lspci -k | grep -iEA5 'vga|3d|display' 00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller (rev 06) Subsystem: ASRock Incorporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller Kernel driver in use: i915 Kernel modules: i915 00:03.0 Audio device: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor HD Audio Controller (rev 06) Subsystem: ASRock Incorporation Xeon E3-1200 v3/4th Gen Core Processor HD Audio Controller pg@pg-desktop:~$ more /var/log/Xorg.0.log | grep EE (WW) warning, (EE) error, (NI) not implemented, (??) unknown. pg@pg-desktop:~$ more /var/log/Xorg.0.log | grep WW (WW) warning, (EE) error, (NI) not implemented, (??) unknown. [ 4.672] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist. [ 4.672] (WW) The directory "/usr/share/fonts/X11/100dpi/" does not exist. [ 4.672] (WW) The directory "/usr/share/fonts/X11/75dpi/" does not exist. [ 4.672] (WW) The directory "/usr/share/fonts/X11/100dpi" does not exist. [ 4.672] (WW) The directory "/usr/share/fonts/X11/75dpi" does not exist. [ 4.852] (WW) Falling back to old probe method for modesetting [ 4.853] (WW) Falling back to old probe method for fbdev [ 4.853] (WW) Falling back to old probe method for vesa pg@pg-desktop:~$ uname -a Linux pg-desktop 4.13.0-45-generic #50-Ubuntu SMP Wed May 30 08:23:18 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux Also fails with separate Radeon GPU: [ 4.904] (II) modesetting: Driver for Modesetting Kernel Drivers: kms [ 4.904] (II) FBDEV: driver for framebuffer: fbdev [ 4.904] (II) VESA: driver for VESA chipsets: vesa [ 4.931] (II) [KMS] Kernel modesetting enabled. [ 4.931] (WW) Falling back to old probe method for modesetting [ 4.931] (WW) Falling back to old probe method for fbdev [ 4.931] (II) Loading sub module "fbdevhw" [ 4.931] (II) LoadModule: "fbdevhw" [ 4.931] (II) Loading /usr/lib/xorg/modules/libfbdevhw.so [ 4.931] (II) Module fbdevhw: vendor="X.Org Foundation" [ 4.931]compiled for 1.19.5, module version = 0.0.2 [ 4.931]ABI class: X.Org Video Driver, version 23.0 [ 4.931] (WW) Falling back to old probe method for vesa [ 4.931] (II) RADEON(0): Creating default Display subsection in Screen section "Default Screen Section" for depth/fbbpp 24/32 [ 4.931] (==) RADEON(0): Depth 24, (--) framebuffer bpp 32 [ 4.931] (II) RADEON(0): Pixel depth = 24 bits stored in 4 bytes (32 bpp pixmaps) [ 4.931] (==) RADEON(0): Default visual is TrueColor [ 4.931] (==) RADEON(0): RGB weight 888 [ 4.931] (II) RADEON(0): Using 8 bits per RGB (8 bit DAC) [ 4.931] (--) RADEON(0): Chipset: "ATI Radeon HD 4350" (ChipID = 0x954f) [ 4.931] (II) Loading sub module "fb" ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-45.50-generic 4.13.16 Uname: Linux 4.13.0-45-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.9 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Jun 19 12:30:55 2018 InstallationDate: Installed on 2017-09-28 (263 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: xorg (Ubuntu) Importance: Undecided Status: New
[Bug 1777600] Re: chzdev can't find modprobe
** Changed in: ubuntu-z-systems Status: New => Triaged ** Changed in: ubuntu-z-systems Importance: Undecided => High ** Changed in: ubuntu-z-systems Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1777600 Title: chzdev can't find modprobe To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1777600/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1777621] Re: xrandr fails to change into the native resolution, useless setup whitout Wayland
I made mistake with update, want 18.04 but got 17.10 and don't recognize it! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1777621 Title: xrandr fails to change into the native resolution, useless setup whitout Wayland To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1777621/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1775145] Re: Please merge gnome-shell 3.28.2 from Debian
** Changed in: gnome-shell (Ubuntu Bionic) Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) ** Tags removed: rls-bb-incoming -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1775145 Title: Please merge gnome-shell 3.28.2 from Debian To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1775145/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1771087] Re: Please remove src:blacs-mpi
** Changed in: blacs-mpi (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/1771087 Title: Please remove src:blacs-mpi To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/blacs-mpi/+bug/1771087/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1776826] Re: linux-kvm: 4.4.0-1029.34 -proposed tracker
4.4.0-1029.34 - kvm Regression test CMPL, RTB. Issue to note in amd64: ubuntu_blktrace_smoke_test - ubuntu_blktrace_smoke_test failed with 4.4 / 4.15 kvm kernel (bug 1760636) ubuntu_fan_smoke_test - ubuntu_fan_smoke_test failed on 4.4 X-kvm kernel (bug 1763323) ubuntu_kvm_unit_tests - 18 failed on harpo ubuntu_lttng_smoke_test - Unable to build lttng module on 4.4/4.15 KVM kernel (bug 1760647) ubuntu_lxc - python3 API failed (bug 1764618) ubuntu_stress_smoke_test - af-alg failed with 4.4/4.15 KVM kernel (bug 1760637) dccp failed with 4.4/4.15 KVM kernel (bug 1760638) ubuntu_zram_smoke_test - zram module not found (bug 1766823) ** 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 notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1776826 Title: linux-kvm: 4.4.0-1029.34 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1776826/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1777194] Comment bridged from LTC Bugzilla
--- Comment From hasri...@in.ibm.com 2018-06-19 05:39 EDT--- (In reply to comment #34) > > I built a test kernel with commits 6bed3237624e and ac61c1156623. The test > kernel can be downloaded from: > http://kernel.ubuntu.com/~jsalisbury/lp1777194 > > Can you test this kernel and see if it resolves this bug? > > Note about installing test kernels: > ? If the test kernel is prior to 4.15(Bionic) you need to install the > linux-image and linux-image-extra .deb packages. > ? If the test kernel is 4.15(Bionic) or newer, you need to install the > linux-modules, linux-modules-extra and linux-image-unsigned .deb packages. > > Thanks in advance! Issue is not observed with the unsigned kernel provided above. # uname -a Linux ltc-wspoon12 4.15.0-23-generic #26~lp1777194 SMP Mon Jun 18 23:45:25 UTC 2018 ppc64le ppc64le ppc64le GNU/Linux Thanks, Harish -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1777194 Title: Hard LOCKUP observed on stressing Ubuntu 18 04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1777194/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1759961] Re: Update to bluez 5.50
** Changed in: bluez (Ubuntu) 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/1759961 Title: Update to bluez 5.50 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1759961/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1772137] Re: networkd-dispatcher starts too late to take effect on boot
** Changed in: networkd-dispatcher (Ubuntu) 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/1772137 Title: networkd-dispatcher starts too late to take effect on boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/networkd-dispatcher/+bug/1772137/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1777621] Re: xrandr fails to change into the native resolution, useless setup whitout Wayland
** Description changed: - - Hello - I have found bugs from Ubuntu 18.04 (form 16.04 by do-release-upgrade) + Hello + I have found bugs from Ubuntu 17.10 (form 16.04 by do-release-upgrade) a) xrandr fails to change into native resolution b) disabling Wayland cause “Out of Range” → can’t login at all (no login via HDMI or virtual TTY:s) c) X fails to detect old VGA monitor (ViewSonic VA902) native resolution (this is a persistent bug) I have used dual monitor setup over a decade, started with Etch and turned into Ubuntu some years ago. First monitor is connected via HDMI and second one by VGA. During Ubuntu installations/updates resolution has been problem, with xrandr etc I have managed situation until now. I have tested: 1) 16.04 & Radeon works OK with 60 Hz VGA modeline 2) 18.04 & Radeon: HDMI is OK but VGA cant’t go into the native resolution 3) 18.04 & Intel: HDMI is OK but VGA cant’t go into the native resolution 4) 18.04 & Radeon VGA without Wayland is Out of Range and useless 5) 18.04 & Intel & xrandr with “easy” modeline do not work 6) 18.04 & Radeon & xrandr with “easy” modeline do not work - pg@pg-desktop:~$ xrandr --newmode 1280x1024_40.00 69.75 1280 1336 1472 1664 1024 1025 1028 1048 -HSync +Vsync pg@pg-desktop:~$ xrandr --verbose --addmode XWAYLAND1 1280x1024_40.00 pg@pg-desktop:~$ xrandr --verbose --output XWAYLAND1 --mode 1280x1024_40.00 screen 0: 2560x1024 677x271 mm 95.98dpi crtc 1: 1280x1024_40.00 40.00 +1280+0 "XWAYLAND1" xrandr: Configure crtc 1 failed crtc 0: disable crtc 1: disable screen 0: revert crtc 0: revert crtc 1: revert pg@pg-desktop:~$ lspci -k | grep -iEA5 'vga|3d|display' 00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller (rev 06) - Subsystem: ASRock Incorporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller - Kernel driver in use: i915 - Kernel modules: i915 + Subsystem: ASRock Incorporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller + Kernel driver in use: i915 + Kernel modules: i915 00:03.0 Audio device: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor HD Audio Controller (rev 06) - Subsystem: ASRock Incorporation Xeon E3-1200 v3/4th Gen Core Processor HD Audio Controller + Subsystem: ASRock Incorporation Xeon E3-1200 v3/4th Gen Core Processor HD Audio Controller pg@pg-desktop:~$ more /var/log/Xorg.0.log | grep EE - (WW) warning, (EE) error, (NI) not implemented, (??) unknown. + (WW) warning, (EE) error, (NI) not implemented, (??) unknown. pg@pg-desktop:~$ more /var/log/Xorg.0.log | grep WW - (WW) warning, (EE) error, (NI) not implemented, (??) unknown. + (WW) warning, (EE) error, (NI) not implemented, (??) unknown. [ 4.672] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist. [ 4.672] (WW) The directory "/usr/share/fonts/X11/100dpi/" does not exist. [ 4.672] (WW) The directory "/usr/share/fonts/X11/75dpi/" does not exist. [ 4.672] (WW) The directory "/usr/share/fonts/X11/100dpi" does not exist. [ 4.672] (WW) The directory "/usr/share/fonts/X11/75dpi" does not exist. [ 4.852] (WW) Falling back to old probe method for modesetting [ 4.853] (WW) Falling back to old probe method for fbdev [ 4.853] (WW) Falling back to old probe method for vesa pg@pg-desktop:~$ uname -a Linux pg-desktop 4.13.0-45-generic #50-Ubuntu SMP Wed May 30 08:23:18 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux Also fails with separate Radeon GPU: [ 4.904] (II) modesetting: Driver for Modesetting Kernel Drivers: kms [ 4.904] (II) FBDEV: driver for framebuffer: fbdev [ 4.904] (II) VESA: driver for VESA chipsets: vesa [ 4.931] (II) [KMS] Kernel modesetting enabled. [ 4.931] (WW) Falling back to old probe method for modesetting [ 4.931] (WW) Falling back to old probe method for fbdev [ 4.931] (II) Loading sub module "fbdevhw" [ 4.931] (II) LoadModule: "fbdevhw" [ 4.931] (II) Loading /usr/lib/xorg/modules/libfbdevhw.so [ 4.931] (II) Module fbdevhw: vendor="X.Org Foundation" [ 4.931] compiled for 1.19.5, module version = 0.0.2 [ 4.931] ABI class: X.Org Video Driver, version 23.0 [ 4.931] (WW) Falling back to old probe method for vesa [ 4.931] (II) RADEON(0): Creating default Display subsection in Screen section - "Default Screen Section" for depth/fbbpp 24/32 + "Default Screen Section" for depth/fbbpp 24/32 [ 4.931] (==) RADEON(0): Depth 24, (--) framebuffer bpp 32 [ 4.931] (II) RADEON(0): Pixel depth = 24 bits stored in 4 bytes (32 bpp pixmaps) [ 4.931] (==) RADEON(0): Default visual is TrueColor [ 4.931] (==) RADEON(0): RGB weight 888 [ 4.931] (II) RADEON(0): Using 8 bits per RGB (8 bit DAC) [ 4.931] (--) RADEON(0): Chipset: "ATI Radeon HD 435
[Bug 1690475] Re: TypeError: 'NoneType' object is not callable
I get this bug on Ubuntu Mate 16.04 when another process is updating some packages. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1690475 Title: TypeError: 'NoneType' object is not callable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1690475/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1777623] [NEW] installer reported that grub failed to install
Public bug reported: I have installed win 10. On an another partition I tried to install ubuntu. While installing it reported a grub crash. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubiquity 18.04.14 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CasperVersion: 1.394 Date: Tue Jun 19 11:56:32 2018 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed boot=casper quiet splash --- LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: grub-installer UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: grub-installer (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ubiquity-18.04.14 ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1777623 Title: installer reported that grub failed to install To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1777623/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1777345] Re: Sound card not working in Ubuntu new kernel version except reinstall some packages
I have the same issue. Sound card works with 127 kernel and with 4.15.xx under Kubuntu 18.04 but fails to work under 128 kernel. Moreover, it causes Plasma load about several minutes until error line in dmesg appear hda_intel azx_get_response timeout switching to single cmd mode this is my sound card 00:1f.3 Audio device: Intel Corporation Device 9d71 (rev 21) At the end, after next reboot under 128 sound card disappears from lspci completely and do not appear even if I boot to any other kernel or even other OS. I have to disable it and enable back in BIOS in order to appear back in lspci. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1777345 Title: Sound card not working in Ubuntu new kernel version except reinstall some packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1777345/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1777624] [NEW] Ubuntu 18.04 installer crashed. Grub failed to install.
Public bug reported: Installation failed after completing about 90% of the process and gave the error message: GRUB installation failed - 'grub-efi-amd64-signed' package failed to install into /target/. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubiquity 18.04.14 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CasperVersion: 1.394 Date: Tue Jun 19 15:31:34 2018 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed cdrom-detect/try-usb=true noprompt floppy.allowed_drive_mask=0 ignore_uuid boot=casper quiet splash --- LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: grub-installer UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: grub-installer (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ubiquity-18.04.14 ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1777624 Title: Ubuntu 18.04 installer crashed. Grub failed to install. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1777624/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1770862] Re: ASUS GU501GM touchpad not detected
I had this problem on the Zephyrus M GS501M, it suddenly disappeared. I'm not sure what fixed it but i suspect: - Try going to the bios, disable and enable the trackpad again, save and retry. (do it even if it's already enable, it seems to fix a windows 10 bug with proprietary bios settings when using Rog Gaming Center). - If it doesn't work, try installing the bios update via windows 10 if you have it in dual boot. For some reason this bios was only available on windows update and I could not download it from Asus website. After doing this my trackpad start being detected and worked without any additionnal settings. I have "acpi_osi=" in my kernel parameters otherwise I have hardware detection problems. I use libinput 1.11.0-1 on arch linux, I haven't tested ubuntu yet. BIOS Information Vendor: American Megatrends Inc. Version: GM501GS.303 Release Date: 04/23/2018 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1770862 Title: ASUS GU501GM touchpad not detected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1770862/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1729674]
I think I have the same issue with my laptop and dock (Dell TB16). Laptop is new and installed in Fedora 28. All firmware are up-to-date. Ethernet works fine unless I want to transfert a large amount of data. Session (sftp, rsync or scp) cut abruptly after a few seconds. Nothing relevant appears in system logs. If I offload the RC checksums (as suggested above) using : ethtool --offload enp11s0u1u2 rx off Everything works fine. Tell me if you need more logs or informations -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1729674 Title: TB16 dock ethernet corrupts data with hw checksum silently failing To manage notifications about this bug go to: https://bugs.launchpad.net/dell-sputnik/+bug/1729674/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1729674]
FYI this commit ended up landing related to this. I would recommend to backport it. https://github.com/torvalds/linux/commit/0b1655143df00ac5349f27b765b2ed13a3ac40ca -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1729674 Title: TB16 dock ethernet corrupts data with hw checksum silently failing To manage notifications about this bug go to: https://bugs.launchpad.net/dell-sputnik/+bug/1729674/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1729674]
Hi Mario, thanks for the pointer. Fedora stable releases are currently on 4.16.15 so that fix should be in place. I've got a TB16 at home so I can also try to reproduce this on Fedora 28 this evening. marianne, adding the dmesg logs would be helpful. Thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1729674 Title: TB16 dock ethernet corrupts data with hw checksum silently failing To manage notifications about this bug go to: https://bugs.launchpad.net/dell-sputnik/+bug/1729674/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1770166] Re: The brightness of the notebook
1-in previous versions if it worked, install ubuntu 18 and it does not work. 2-I'm on it -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1770166 Title: The brightness of the notebook To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1770166/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1768610] Re: leftover conffile forces GNOME is software rendering
Cheers!
My nux-tools review comments apply to x11-common too. The following are
for x11-common:
What's the reason for doing this in preinst rather than postinst
configure? It's fine in this case but usually we do things in postinst
where possible.
What about adding a "Breaks: nux-tools (<<
4.0.8+18.04.20180613.5-0ubuntu1)" to x11-common, and making the script
not do the fix up if we're upgrading from the new version ("if dpkg
--compare-versions "${2}" lt 1:7.7+19ubuntu8; then do stuff; fi")?
I think it's a good idea generally to make fix up actions in maintainer
scripts strictly limited to certain package versions and this will mean
if you still have nux-tools installed you have to upgrade it to the
fixed version, so the removal can only have happened earlier than
x11-common 1:7.7+19ubuntu8.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1768610
Title:
leftover conffile forces GNOME is software rendering
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nux/+bug/1768610/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1729674]
Looks like this is more of a firmware issue with these docks and/or a driver issue with the 8152, so I'm throwing this back onto the queue where it was. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1729674 Title: TB16 dock ethernet corrupts data with hw checksum silently failing To manage notifications about this bug go to: https://bugs.launchpad.net/dell-sputnik/+bug/1729674/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1775743] Re: [regression] Cosmic daily images 20180606-11 install but boots only to grub prompt on EFI systems
I would need someone to take a look and review my proposed fix for debian-installer. I have tested that on a custom ISO image and as a result I got my system booting. It did cause the grub prompt to appear (asking on which partition to install), but I suppose that's not anything new. ** Patch added: "First try on getting d-i install grub-pc." https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1775743/+attachment/5154252/+files/d-i-install-grub-pc.patch ** Changed in: grub2-signed (Ubuntu) Status: Triaged => Won't Fix ** Changed in: grub2 (Ubuntu) Status: Triaged => Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1775743 Title: [regression] Cosmic daily images 20180606-11 install but boots only to grub prompt on EFI systems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1775743/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1777420] Re: Login loop after inactivity in login screen
I've updated to bionic from xenial recently, so I'm sure this issue always existed. Installed 4.17.2 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1777420 Title: Login loop after inactivity in login screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1777420/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1776614] Re: Upstream renamed, package out-of-date
** Changed in: python-hp3parclient (Ubuntu) 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/1776614 Title: Upstream renamed, package out-of-date To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-hp3parclient/+bug/1776614/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1772137] Re: networkd-dispatcher starts too late to take effect on boot
This bug was fixed in the package networkd-dispatcher - 1.7-0ubuntu6 --- networkd-dispatcher (1.7-0ubuntu6) cosmic; urgency=medium * networkd-dispatcher.conf: Run startup triggers by default (LP: #1772137) -- Julian Andres Klode Tue, 19 Jun 2018 11:19:39 +0200 ** Changed in: networkd-dispatcher (Ubuntu) Status: Fix Committed => 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/1772137 Title: networkd-dispatcher starts too late to take effect on boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/networkd-dispatcher/+bug/1772137/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1777579] Re: 18.04 Dekstop LTS DNS behavior (systemd-resolved)
** Package changed: ubuntu => systemd (Ubuntu) ** Tags added: bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1777579 Title: 18.04 Dekstop LTS DNS behavior (systemd-resolved) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1777579/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1774950] Re: Suspend fails in Ubuntu and Kubuntu 18.04 but works fine in Ubuntu and Kubuntu 17.10 (and on Kubuntu 18.04 using kernel 4.14.47)
I am a Linux Mint user, of course which is downstream from Ubuntu. At the bottom of my post is an "inxi -Fxz" output with my machine info. I am replying because I am getting issues with exactly the same kernels (4.15 and up), and 4.14 installed unconventionally via Ukuu seems okay. My problems that I noticed were: 1) plugged-in HDD (Dell Latitude media bay, SATA bus), no drive recognized. Reboot with drive plugged in required. 2) wireless settings in Dell BIOS go ignored: a) wireless switch (WLAN, WWAN, Bluetooth) -this is three checkboxes to configure each to be controlled by the physical switch on the right side of laptop. b) wireless enable (WLAN, WWAN, Bluetooth) -again, three checkboxes, these enable or disable each. The resulting behaviors for 2) included physical wireless switch on right-hand side of laptop being enabled, even though I had it disabled in BIOS. Also wireless connectivity had dropouts. The wireless devices I had disabled in the BIOS settings also remained up and running. This meant that the Bluetooth couldn't effectively be disabled at BIOS settings. Different from everyone else's results. These are just the things I noticed. I have verified this to be related to kernels 4.15 - 4.17.1 (using UKUU), which is why I am replying here. Below are my "inxi -Fxy" results: ~ $ inxi -Fxz System:Host: travel Kernel: 4.14.50-041450-generic x86_64 (64 bit gcc: 7.3.0) Desktop: Cinnamon 3.6.7 (Gtk 3.18.9-1ubuntu3.3) Distro: Linux Mint 18.3 Sylvia Machine: System: Dell (portable) product: Latitude E6420 v: 01 Mobo: Dell model: 0X8R3Y Bios: Dell v: A24 date: 05/12/2017 CPU: Dual core Intel Core i7-2640M (-HT-MCP-) cache: 4096 KB flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx) bmips: 11173 clock speeds: max: 3500 MHz 1: 798 MHz 2: 967 MHz 3: 931 MHz 4: 806 MHz Graphics: Card: Intel 2nd Generation Core Processor Family Integrated Graphics Controller bus-ID: 00:02.0 Display Server: X.Org 1.18.4 drivers: intel (unloaded: fbdev,vesa) Resolution: 1600x900@60.00hz GLX Renderer: Mesa DRI Intel Sandybridge Mobile GLX Version: 3.0 Mesa 17.2.8 Direct Rendering: Yes Audio: Card Intel 6 Series/C200 Series Family High Definition Audio Controller driver: snd_hda_intel bus-ID: 00:1b.0 Sound: ALSA v: k4.14.50-041450-generic Network: Card: Intel Centrino Advanced-N 6205 [Taylor Peak] driver: iwlwifi bus-ID: 02:00.0 IF: wlp2s0 state: up mac: Drives:HDD Total Size: 128.0GB (53.4% used) ID-1: /dev/sda model: Samsung_SSD_850 size: 128.0GB Partition: ID-1: / size: 115G used: 62G (57%) fs: ext4 dev: /dev/sda1 ID-2: swap-1 size: 2.56GB used: 0.00GB (0%) fs: swap dev: /dev/sda2 RAID: No RAID devices: /proc/mdstat, md_mod kernel module present Sensors: System Temperatures: cpu: 58.0C mobo: N/A Fan Speeds (in rpm): cpu: N/A Info: Processes: 184 Uptime: 36 min Memory: 1175.6/7852.4MB Init: systemd runlevel: 5 Gcc sys: 5.4.0 Client: Shell (bash 4.3.481) inxi: 2.2.35 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1774950 Title: Suspend fails in Ubuntu and Kubuntu 18.04 but works fine in Ubuntu and Kubuntu 17.10 (and on Kubuntu 18.04 using kernel 4.14.47) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774950/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1774950] Re: Suspend fails in Ubuntu and Kubuntu 18.04 but works fine in Ubuntu and Kubuntu 17.10 (and on Kubuntu 18.04 using kernel 4.14.47)
@user-unknown - thanks for the information, it's good to hear that the patch is helping sort out the suspend issues. Interesting to see it's another Bay Trail Atom type CPU that seems to be affected too. I haven't experienced any graphical issues so far. I'm mostly running Kubuntu but also have a separate install of Ubuntu with the standard Gnome desktop. Both have been running fine with the patched 4.15 kernel and suspend issues are not present anymore. I'm curious about the graphical issues only being present with the patched kernel. I'd be tempted to think they are due to the different desktop environments somehow interefering with each other, but it's odd that they are not present with a different kernel. Would it be possible to try it without the cstate flag? I'd be interested to know if there is any difference in behaviour. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1774950 Title: Suspend fails in Ubuntu and Kubuntu 18.04 but works fine in Ubuntu and Kubuntu 17.10 (and on Kubuntu 18.04 using kernel 4.14.47) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774950/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1773679] Re: Samba panics; samba-dbg package not found
** Changed in: samba Status: Fix Committed => 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/1773679 Title: Samba panics; samba-dbg package not found To manage notifications about this bug go to: https://bugs.launchpad.net/samba/+bug/1773679/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1735377] Re: openvswitch: Use of Python3 needed
@xnox Revisiting this work this week with intent to upload ASAP. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1735377 Title: openvswitch: Use of Python3 needed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openvswitch/+bug/1735377/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1767934] Re: breaking the apparmor profile leads to misleading error messages
There are other reasons this could trigger, but one is e.g. adding e.g. a disk with: You need to create the file or libvirt will detect and exit before that. $ sudo qemu-img create -f qcow2 '/var/lib/libvirt/images/break,^*[]", foo"me.qcow' 10M Error (on most recent libvirt) is like: error: Failed to start domain c error: internal error: cannot load AppArmor profile 'libvirt-8763795d-f056-4373-9d57-3d3bad391e5a' The same used as hotplug device will trigger: error: Failed to attach device from disk.xml error: internal error: cannot update AppArmor profile 'libvirt-8763795d-f056-4373-9d57-3d3bad391e5a' I have found no way with recent versions to get the misleading pointer to the "qemu-... does not exists". Setting incomplete. ** Changed in: libvirt (Ubuntu) Status: Triaged => Incomplete ** Tags removed: libvirt-18.10 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1767934 Title: breaking the apparmor profile leads to misleading error messages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1767934/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1767934] Re: breaking the apparmor profile leads to misleading error messages
Actually, if we could have a filename that makes it bad it would be nice, but at low prio ** Changed in: libvirt (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1767934 Title: breaking the apparmor profile leads to misleading error messages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1767934/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1751006] Re: Journalctl compiled without pattern matching support, pcre2 is not in main
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: pcre2 (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/1751006 Title: Journalctl compiled without pattern matching support, pcre2 is not in main To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pcre2/+bug/1751006/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1777633] [NEW] Xorg Out of Range with VGA native resolution
Public bug reported: This bug is related to Bug 1777621 with 17.10 pg@pg-desktop:~$ xrandr Screen 0: minimum 320 x 200, current 2304 x 1024, maximum 8192 x 8192 VGA-1 connected primary 1024x768+1280+0 (normal left inverted right x axis y axis) 0mm x 0mm 1024x768 60.00* 800x600 60.3256.25 848x480 60.00 640x480 59.94 HDMI-1 connected 1280x1024+0+0 (normal left inverted right x axis y axis) 376mm x 301mm 1280x1024 60.02*+ 76.0075.0272.05 1152x864 75.00 1024x768 75.0370.0760.00 832x624 74.55 800x600 72.1975.0060.32 640x480 75.0072.8166.6759.94 720x400 70.08 640x350 70.07 HDMI-2 disconnected (normal left inverted right x axis y axis) 1280x1024_60.00 (0x120) 109.000MHz -HSync +VSync h: width 1280 start 1368 end 1496 total 1712 skew0 clock 63.67KHz v: height 1024 start 1027 end 1034 total 1063 clock 59.89Hz pg@pg-desktop:~$ xrandr --newmode 1280x1024_40.00 69.75 1280 1336 1472 1664 1024 1025 1028 1048 -HSync +Vsync pg@pg-desktop:~$ xrandr --verbose --addmode VGA-1 1280x1024_40.00 pg@pg-desktop:~$ xrandr --verbose --output VGA-1 --mode 1280x1024_40.00 screen 0: 2560x1024 677x271 mm 95.98dpi crtc 0: 1280x1024_40.00 40.00 +1280+0 "VGA-1" pg@pg-desktop:~$ => VGA-1 Out of Range! ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Jun 19 14:37:03 2018 DistUpgraded: 2018-06-19 13:58:44,011 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8)) DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [8086:0402] (rev 06) (prog-if 00 [VGA controller]) Subsystem: ASRock Incorporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [1849:0402] InstallationDate: Installed on 2017-09-28 (264 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic root=UUID=32b56d21-8cb0-4fcd-8f39-bdee0a192558 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to bionic on 2018-06-19 (0 days ago) dmi.bios.date: 12/06/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.10 dmi.board.name: B85M dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.10:bd12/06/2013:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB85M:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Sun Jun 17 11:33:00 2018 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.5-0ubuntu2~16.04.1 xserver.video_driver: radeon ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic false-gpu-hang freeze ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1777633 Title: Xorg Out of Range with VGA native resolution To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1777633/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1767934] Re: breaking the apparmor profile leads to misleading error messages
virt-aa-helper reports actually already a good message internally: virt-aa-helper: error: skipped restricted file virt-aa-helper: error: invalid VM definition You'd already see it in journal or on a systemctl to libvirtd: Jun 19 11:35:53 c libvirtd[25978]: 2018-06-19 11:35:53.415+: 25979: error : virCommandWait:2601 : internal error: Child process (LIBVIRT_LOG_OUTPUTS=3:stderr /usr/lib/libvirt/virt-aa-helper -p 0 -r -u libvirt-8763795d-f056-4373-9d57-3d3bad391e5a -f '/var/lib/libvirt/images/break,^*[]", foo"me.qcow') unexpected exit status 1: virt-aa-helper: error: /var/lib/libvirt/images/break,^*[]", foo"me.qcow Jun 19 11:35:53 c libvirtd[25978]: virt-aa-helper: error: skipped restricted file Jun 19 11:35:53 c libvirtd[25978]: virt-aa-helper: error: invalid VM definition Jun 19 11:35:53 c libvirtd[25978]: 2018-06-19 11:35:53.415+: 25979: error : AppArmorSetSecurityImageLabel:843 : internal error: cannot update AppArmor profile 'libvirt-8763795d-f056-4373-9d57-3d3bad391e5a' -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1767934 Title: breaking the apparmor profile leads to misleading error messages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1767934/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 951610] Re: root partition combobox should include empty element
> [Expired for ubiquity (Ubuntu) because there has been no activity for 60 > days.] Correction. No activity for 6 years. =) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/951610 Title: root partition combobox should include empty element To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/951610/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1777634] [NEW] no more than 1 GATT descriptor allowed
Public bug reported: By running the example-gatt-server and example-gatt-advertising, it was impossible to get more than one Descriptor per characteristic. if i comment one i can see the other in the test characteristic. but if i set both, it just act like no descriptor available. ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Tags: gatt server -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1777634 Title: no more than 1 GATT descriptor allowed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1777634/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1775743] Re: [regression] Cosmic daily images 20180606-11 install but boots only to grub prompt on EFI systems
@sil2100, Colin already commented on a similar change you proposed against ubiquity https://code.launchpad.net/~sil2100/ubiquity/+git/ubiquity/+merge/348201/comments/909076 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1775743 Title: [regression] Cosmic daily images 20180606-11 install but boots only to grub prompt on EFI systems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1775743/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1717807] Re: When the menu contains too elements, the bottom ones does not appear
I also experienced this bug with a different clipboard history indicator. Also, these kind of applications (those that keep a history of clipboard contents for easy retrieval) are relatively common, so I disagree with the "low" priority categorization of this bug, which literally makes any indicator that is higher than your given screen height useless. As the sole purpose of this plugin is to display and allow interaction with indicators, such an issue seems fairly important. :-) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1717807 Title: When the menu contains too elements, the bottom ones does not appear To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/1717807/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1777636] Re: dm-writeboost 2.2.6-1~16.04.2 ADT test failure with linux-hwe-edge 4.15.0-23.25~16.04.1
** Attachment added: "make.log" https://bugs.launchpad.net/bugs/1777636/+attachment/5154276/+files/make.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1777636 Title: dm-writeboost 2.2.6-1~16.04.2 ADT test failure with linux-hwe-edge 4.15.0-23.25~16.04.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dm-writeboost/+bug/1777636/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1777636] [NEW] dm-writeboost 2.2.6-1~16.04.2 ADT test failure with linux-hwe-edge 4.15.0-23.25~16.04.1
Public bug reported: Testing failed on: amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/amd64/d/dm-writeboost/20180528_193648_1f08d@/log.gz armhf: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/armhf/d/dm-writeboost/20180528_193945_1f08d@/log.gz i386: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/i386/d/dm-writeboost/20180528_193900_1f08d@/log.gz ppc64el: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/ppc64el/d/dm-writeboost/20180528_193841_1f08d@/log.gz s390x: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/s390x/d/dm-writeboost/20180528_194034_1f08d@/log.gz ** Affects: dm-writeboost (Ubuntu) Importance: Undecided Status: New ** Tags: kernel-adt-failure ** Tags added: kernel-adt-failure -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1777636 Title: dm-writeboost 2.2.6-1~16.04.2 ADT test failure with linux-hwe-edge 4.15.0-23.25~16.04.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dm-writeboost/+bug/1777636/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1767564] Re: Ubuntu 18.04 Workspaces only change on primary monitor
Throwing in my two bits, I have multiple monitors - they are my desktop. When I switch desktops I expect both to switch together. I see that Jim expected each to be independent - I could live with that too, but it's not the behavior I expect. My situation is a desktop with multiple monitors, not a laptop with an external monitor; that probably contributes to the way I look at it. Linux 4.15.0-23-generic x86_64 Ubuntu 18.04 LTS (Bionic Beaver) == /sys/devices/pci:00/:00:01.0/:01:00.0 == modalias : pci:v10DEd1CB2sv10DEsd11BDbc03sc00i00 vendor : NVIDIA Corporation model: GP107GL [Quadro P600] driver : nvidia-driver-390 - distro non-free recommended driver : xserver-xorg-video-nouveau - distro free builtin -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1767564 Title: Ubuntu 18.04 Workspaces only change on primary monitor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1767564/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1679664] Re: dm-writeboost 2.1.1-1ubuntu1 ADT test failure with linux-hwe-edge 4.10.0-14.16~16.04.1
** Changed in: dm-writeboost (Ubuntu) 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/1679664 Title: dm-writeboost 2.1.1-1ubuntu1 ADT test failure with linux-hwe-edge 4.10.0-14.16~16.04.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dm-writeboost/+bug/1679664/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1777636] Re: dm-writeboost 2.2.6-1~16.04.2 ADT test failure with linux-hwe-edge 4.15.0-23.25~16.04.1
** Description changed: + [Impact] + + Currently the DKMS package fails to install on supported custom + kernels that are based on 4.15. That includes the current 4.15 + hwe-edge and some of the custom and cloud kernels as well. + + [Test Case] + + Install the broadcom-sta package with the 4.15 hwe-edge kernel. The + package installation should proceed without any errors. + + [Regression Potential] + + Although new patches were added, the regression risk is very low since + the new changes are conditionally compiled based on the kernel + version. + + Besides that, the new package was tested with the following kernels in + an amd64 environment: + + - linux-generic 4.4 + - linux-hwe 4.13 + - linux-hwe-edge 4.15 + - linux-azure 4.15 + + [Original Description] + Testing failed on: - amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/amd64/d/dm-writeboost/20180528_193648_1f08d@/log.gz - armhf: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/armhf/d/dm-writeboost/20180528_193945_1f08d@/log.gz - i386: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/i386/d/dm-writeboost/20180528_193900_1f08d@/log.gz - ppc64el: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/ppc64el/d/dm-writeboost/20180528_193841_1f08d@/log.gz - s390x: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/s390x/d/dm-writeboost/20180528_194034_1f08d@/log.gz + amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/amd64/d/dm-writeboost/20180528_193648_1f08d@/log.gz + armhf: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/armhf/d/dm-writeboost/20180528_193945_1f08d@/log.gz + i386: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/i386/d/dm-writeboost/20180528_193900_1f08d@/log.gz + ppc64el: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/ppc64el/d/dm-writeboost/20180528_193841_1f08d@/log.gz + s390x: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/s390x/d/dm-writeboost/20180528_194034_1f08d@/log.gz -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1777636 Title: dm-writeboost 2.2.6-1~16.04.2 ADT test failure with linux-hwe-edge 4.15.0-23.25~16.04.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dm-writeboost/+bug/1777636/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1777639] [NEW] No C++ demangling in perf
Public bug reported: Hello, It appears that C++ demangling support is missing from linux- tools-4.15.0-23-generic, on Ubuntu 16.04. Could that please be fixed? The lack of demangling support was also noticed in linux-tools-4.13.0-45-generic. Kind regards, Francois. Ps: Launchpad reported "linux-tools-4.15.0-23-generic" does not exist in Ubuntu. Package name changed to "linux". ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: c++ demangling linux-tools perf -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1777639 Title: No C++ demangling in perf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1777639/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1774950] Re: Suspend fails in Ubuntu and Kubuntu 18.04 but works fine in Ubuntu and Kubuntu 17.10 (and on Kubuntu 18.04 using kernel 4.14.47)
@noreasternhumidty - I'm interested to see the information you provided but I don't think it will get looked into by posting on this bug report :) I had a quick look for 'wireless' bugs that are open but only found this one that looked vaguely similar to what you described: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774102 This is my first bug report so I'm still finding my way around, but I think it works something like this: - If you are experiencing any issues with your distribution, it's helpful to check on the forums (or something similar to AskUbuntu) to see if anyone else is experiencing the same issue. This helps rule out the possibility that it's just something specific to your machine. https://forums.linuxmint.com/ - You can open a bug report stating the issue (e.g 'BIOS settings for Wireless and Bluetooth are ignored in kernels 4.15 and above') https://bugs.launchpad.net/linuxmint - In this case, because it's Linux Mint you'd be best to get in touch with their developers. If the issue affects something used by other projects (e.g the kernel) then I think they will be in the best position to check the details and offer suggestions first and then pass on the information to the relevant project. This bug specifically is just about suspend not working on 18.04. It's only affecting a small number of machines but it's been great to see that it's being looked into. One of the Ubuntu developers passed along the information to a kernel.org developer, but only after getting more information and narrowing down the cause of the issue. I think this is the normal procedure for bugs of this kind. Start with the Linux Mint forums and then open a bug report if you can't find a fix for it and then it should get looked into. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1774950 Title: Suspend fails in Ubuntu and Kubuntu 18.04 but works fine in Ubuntu and Kubuntu 17.10 (and on Kubuntu 18.04 using kernel 4.14.47) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774950/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1777636] Re: dm-writeboost 2.2.6-1~16.04.2 ADT test failure with linux-hwe-edge 4.15.0-23.25~16.04.1
** Patch added: "dm-writeboost_2.2.6-1~16.04.3.debdiff" https://bugs.launchpad.net/ubuntu/+source/dm-writeboost/+bug/1777636/+attachment/5154278/+files/dm-writeboost_2.2.6-1~16.04.3.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1777636 Title: dm-writeboost 2.2.6-1~16.04.2 ADT test failure with linux-hwe-edge 4.15.0-23.25~16.04.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dm-writeboost/+bug/1777636/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1759628] Re: bluez regression: Bluetooth audio fails to reconnect after resume
This bug was fixed in the package bluez - 5.50-0ubuntu1 --- bluez (5.50-0ubuntu1) cosmic; urgency=medium * New upstream release 5.50: - Fix issue with GATT and reading long values. - Fix issue with GATT and reading multiple includes. - Fix issue with GATT and service changes when offline. - Fix issue with handling secondary service discovery. - Fix issue with handling persistency of CCC values. - Fix issue with handling Mesh session on disconnection. - Fix issue with handling Mesh proxy PDU SAR message length. - Fix issue with handling Mesh default heartbeat TTL value. - Add support for Mesh node-reset operation handling. - Add support for GATT authorization request handling. - Add support for GATT minimum key size requirements. - Add support for GATT server and included services. - Add support for handling additional advertising data. - Add support for handling separate discoverable state. - Add support for enabling HFP version 1.7 features. - Add support for dedicated Bluetooth logging daemon. * Refreshed debian/patches to work with 5.50 and apply cleanly. * Fixed lintian errors: - dpkg-maintscript-helper missing in postinst and postrm. - Synchronized (some) man pages from Debian. * New upstream release 5.49 (LP: #1759961): - Fix issue with configuring discoverable advertising flag. - Fix issue with bearer selection and single mode controllers. - Fix issue with Connect and ConnectProfile returning in progress. - Fix issue with missing Paired property change when not bonded. - Fix issue with storage for controllers without public address. - Fix issue with handling AVCTP disconnecting the channel queue. - Fix issue with not clearing connectable setting on power off. - Fix issue with creating multiple mgmt socket instances. - Fix issue with GATT server and BR/EDR only devices. - Fix issue with InterfaceAdded event ordering. (LP: #1759628) - Add support for generic ConnectDevice method call. - Add support for Mesh heartbeat client functionality. * Drop upstreamed patch: - fix-lp1750308-upstream-commit-1bf03369.patch -- Daniel van Vugt Wed, 06 Jun 2018 16:26:40 +0800 ** Changed in: bluez (Ubuntu) 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/1759628 Title: bluez regression: Bluetooth audio fails to reconnect after resume To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1759628/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1777099] Re: [backport] DRM devices opened by logind stay referenced indefinitely by PID 1
Attaching the debdiff ** Patch added: "systemd_237-3ubuntu10.2.debdiff" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1777099/+attachment/5154277/+files/systemd_237-3ubuntu10.2.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1777099 Title: [backport] DRM devices opened by logind stay referenced indefinitely by PID 1 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1777099/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1759961] Re: Update to bluez 5.50
This bug was fixed in the package bluez - 5.50-0ubuntu1 --- bluez (5.50-0ubuntu1) cosmic; urgency=medium * New upstream release 5.50: - Fix issue with GATT and reading long values. - Fix issue with GATT and reading multiple includes. - Fix issue with GATT and service changes when offline. - Fix issue with handling secondary service discovery. - Fix issue with handling persistency of CCC values. - Fix issue with handling Mesh session on disconnection. - Fix issue with handling Mesh proxy PDU SAR message length. - Fix issue with handling Mesh default heartbeat TTL value. - Add support for Mesh node-reset operation handling. - Add support for GATT authorization request handling. - Add support for GATT minimum key size requirements. - Add support for GATT server and included services. - Add support for handling additional advertising data. - Add support for handling separate discoverable state. - Add support for enabling HFP version 1.7 features. - Add support for dedicated Bluetooth logging daemon. * Refreshed debian/patches to work with 5.50 and apply cleanly. * Fixed lintian errors: - dpkg-maintscript-helper missing in postinst and postrm. - Synchronized (some) man pages from Debian. * New upstream release 5.49 (LP: #1759961): - Fix issue with configuring discoverable advertising flag. - Fix issue with bearer selection and single mode controllers. - Fix issue with Connect and ConnectProfile returning in progress. - Fix issue with missing Paired property change when not bonded. - Fix issue with storage for controllers without public address. - Fix issue with handling AVCTP disconnecting the channel queue. - Fix issue with not clearing connectable setting on power off. - Fix issue with creating multiple mgmt socket instances. - Fix issue with GATT server and BR/EDR only devices. - Fix issue with InterfaceAdded event ordering. (LP: #1759628) - Add support for generic ConnectDevice method call. - Add support for Mesh heartbeat client functionality. * Drop upstreamed patch: - fix-lp1750308-upstream-commit-1bf03369.patch -- Daniel van Vugt Wed, 06 Jun 2018 16:26:40 +0800 ** Changed in: bluez (Ubuntu) Status: Fix Committed => 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/1759961 Title: Update to bluez 5.50 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1759961/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1775743] Re: [regression] Cosmic daily images 20180606-11 install but boots only to grub prompt on EFI systems
** Tags added: patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1775743 Title: [regression] Cosmic daily images 20180606-11 install but boots only to grub prompt on EFI systems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1775743/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1777636] Re: dm-writeboost 2.2.6-1~16.04.2 ADT test failure with linux-hwe-edge 4.15.0-23.25~16.04.1
** Tags added: patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1777636 Title: dm-writeboost 2.2.6-1~16.04.2 ADT test failure with linux-hwe-edge 4.15.0-23.25~16.04.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dm-writeboost/+bug/1777636/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1777639] 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 1777639 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 ** Tags added: bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1777639 Title: No C++ demangling in perf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1777639/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1776344] Re: linux-gcp: 4.15.0-1010.10 -proposed tracker
Setting snap-release-to-* tasks to 'Invalid' since Bionic kernel snaps are not being uploaded to the Store yet. ** Changed in: kernel-sru-workflow/snap-release-to-beta Status: Confirmed => Invalid ** Changed in: kernel-sru-workflow/snap-release-to-candidate Status: New => Invalid ** Changed in: kernel-sru-workflow/snap-release-to-edge 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/1776344 Title: linux-gcp: 4.15.0-1010.10 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1776344/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1729736] Re: 10de:1c8c [MSI] Module nouveau fails to manage GeForce GTX 1050 Ti Mobile
With Linux kernel 4.18.0-041800rc1 from http://kernel.ubuntu.com /~kernel-ppa/mainline, graphical login fails. Following workaround given by Pierre Moreau at https://bugs.freedesktop.org/show_bug.cgi?id=101665 succeeds: Inside the kernel command line, add options 'acpi_osi=! acpi_osi="Windows 2009"' ** Tags removed: kernel-bug-exists-upstream-4.17 ** Tags added: kernel-bug-exists-upstream-4.18 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1729736 Title: 10de:1c8c [MSI] Module nouveau fails to manage GeForce GTX 1050 Ti Mobile To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1729736/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1777099] Re: [backport] DRM devices opened by logind stay referenced indefinitely by PID 1
** Tags added: patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1777099 Title: [backport] DRM devices opened by logind stay referenced indefinitely by PID 1 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1777099/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
