[Bug 1828609] Re: Cannot do updates, not even partial
https://launchpadlibrarian.net/423140934/VarLogDistupgradeAptlog.txt seems to suggest you have packages from multiple Ubuntu releases installed. If this can be confirmed, then this is more of a support case than a bug in the software. This said, more robust handling by the release upgrader (detecting this situation - which is difficult to do -, and handling it, probably by preventing a release upgrade to be initiated under these unsafe conditions, and providing further suggestion) would be more than just nice to have in general (and deserves its separate bug report). ** Changed in: ubuntu-release-upgrader (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1828609 Title: Cannot do updates, not even partial To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1828609/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1828597] Comment bridged from LTC Bugzilla
--- Comment From hbath...@in.ibm.com 2019-05-10 13:25 EDT--- Right, Cascardo. nr_cpus=1 for KDump case has never worked before on ppc64. Mahesh tried fixing it but the maintainer had a few apprensions and rightly so. This fix doesn't work in all cases. Say, KVM host (baremetal with SMT off).. So, to start with, "nr_cpus=1" as default parameter instead of "maxcpus=1" for KDump kernel on ppc64, even with the kernel fix from Mahes was not a good idea, as it was not something that works always... IMHO, with no alternate and foolproof way to fix this in discussion yet, we can save the "nr_cpus=1" option as default for another day and stick with "maxcpus=1" for now. That was the intention behind this bug.. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1828597 Title: KDump boot fails with nr_cpus=1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1828597/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1828613] [NEW] See - [Bug 1828569] [NEW] Popping sound when audio driver engaged - [, Realtek ALC889, Green Line Out, Rear] Playback problem
Public bug reported: I had logged bug 1828569 and then ran this test to provide the driver/hardware info. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: sidboswell 1591 F pulseaudio /dev/snd/controlC2: sidboswell 1591 F pulseaudio /dev/snd/controlC0: sidboswell 1591 F pulseaudio /dev/snd/controlC3: sidboswell 1591 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Fri May 10 12:03:10 2019 InstallationDate: Installed on 2019-04-20 (19 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:MID successful Symptom_Card: Built-in Audio - HDA Intel MID Symptom_Jack: Green Line Out, Rear Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: None of the above Title: [, Realtek ALC889, Green Line Out, Rear] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/23/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 080016 dmi.board.name: EVGA P55 3X SLI E658 dmi.board.vendor: EVGA dmi.board.version: Ibex Peak dmi.chassis.type: 3 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr080016:bd09/23/2010:svn:pn:pvr:rvnEVGA:rnEVGAP553XSLIE658:rvrIbexPeak:cvn:ct3:cvr: ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1828613 Title: See - [Bug 1828569] [NEW] Popping sound when audio driver engaged - [, Realtek ALC889, Green Line Out, Rear] Playback problem To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1828613/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1718719] Re: qemu can't capture keys properly under wayland
Launchpad has imported 9 comments from the remote bug at https://bugs.freedesktop.org/show_bug.cgi?id=102475. 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 2017-08-30T11:42:57+00:00 Sebastien Bacher wrote: The Ubuntu maintainer backported the recent change to add keyboard grabbing to xwayland, with that change the keyboard arrow keys stop working in kvm Reply at: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1718719/comments/0 On 2017-08-30T12:40:12+00:00 Olivier Fourdan wrote: Can you please elaborate of what exactly has been backported and the resulting patches? Which Wayland compositor do you use? It's worth noting that the xwayland patches in themselves won't make a difference *unless* the Wayland compositor implements the corresponding protocol, and I am aware of none for now (the patch for mutter is still pending). Reply at: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1718719/comments/1 On 2017-08-30T13:36:16+00:00 Sebastien Bacher wrote: The Ubuntu diff is http://launchpadlibrarian.net/334552966/xorg-server_2%3A1.19.3-1ubuntu3_2%3A1.19.3-1ubuntu4.diff.gz it looks like the backported commits are xwayland-pointer-confine.diff +d5e2f271ad93e50 xwayland: Remove two unused proc pointers. +ca17f3e9fd3b59f xwayland: Lock the pointer if it is confined and has no cursor +513e3bd3870fdb8 xwayland: Update root window size when desktop size changes +fafdb0cc9697eb5 xwayland: "Accept" confineTo on InputOnly windows +c217fcb4c4640ff xwayland: Allow pointer warp on root/None window xwayland-add-grab-protocol-support.diff https://cgit.freedesktop.org/xorg/xserver/commit/?id=0a448d133 Ubuntu doesn't have any compositor change, it's standard GNOME 3.24 so there is must be something wrong and it does make a difference without implementing the protocole. Note that reverting 0a448d133 does fix the issue Reply at: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1718719/comments/2 On 2017-08-30T14:57:34+00:00 Olivier Fourdan wrote: Tried reproducing the issue with the arrow keys using the current Xwayland from master with mutter/gnome-shell from master, using qemu-kvm with SDL backend (-display sdl) but failedto reproduce, all keys (including the arrow keys) work fine in the guest. Reply at: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1718719/comments/3 On 2017-08-31T16:26:13+00:00 Olivier Fourdan wrote: Created attachment 133910 Test patch Can you try the attached patch (this is for testing purpose *only*) and report back if that makes any difference? With this patch, if the compositor has no support for Xwayland keyboard grab protocol as you said you haven't in Ubuntu, Xwayland won't set up its grab handler at all. Reply at: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1718719/comments/4 On 2017-08-31T23:04:19+00:00 Sebastien Bacher wrote: the patch doesn't seem to make a difference Reply at: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1718719/comments/5 On 2017-09-01T07:15:06+00:00 Olivier Fourdan wrote: Well, what this patch does is disabling any specific grab handler if the Xwayland grab protocol is not available, by postponing the setup of those handler until Xwayland can bind to the relevant interface as advertised by the compositor. If the compositor doesn't support the Xwayland grab protocol, then all those routines are not "enabled" in Xwayland, I don't see how they could break anything if not used... Unfortunately, we cannot tell whether or not the compositor supports the Xwayland grab protocol using something like weston-info because, for security reasons, the compositor will (should) only advertiset he given protocl to Xwayland alone and hide it to any other client. So, if that patch makes no difference, it means that: - The Wayland compositor claim to support Xwayland grab protocol but is buggy and doesn't send all key events as expected - Or the problem is completely unrelated to this patch. So next step for you is to: - Check the actual patches applied to mutter in Ubuntu - Check what happens at the protocol level To do so, yo can use the envvar WAYLAND_DEBUG prior to start gnome-shell (which will spawn Xwayland) so that we can tell what globals are listed in the wl_registry and see if "zwp_xwayland_keyboard_grab_manager_v1" is one of them. e.g.,
[Bug 1806053] Fix included in openstack/horizon 14.0.3
This issue was fixed in the openstack/horizon 14.0.3 release. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1806053 Title: APITestCase still needs to be patched utils.patch_middleware_get_user() To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1806053/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1828615] Re: v4l2loopback 10.0-1ubuntu1 ADT test failure with linux 5.0.0-14-generic
The attachment "v4l2loopback_0.10.0-1ubuntu1.1.debdiff" seems to be a debdiff. The ubuntu-sponsors team has been subscribed to the bug report so that they can review and hopefully sponsor the debdiff. If the attachment isn't a patch, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are member of the ~ubuntu-sponsors, unsubscribe the team. [This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issue please contact him.] ** 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/1828615 Title: v4l2loopback 10.0-1ubuntu1 ADT test failure with linux 5.0.0-14-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/v4l2loopback/+bug/1828615/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 520546] Re: Alt+KEY incorrectly behaves like Ctrl+Alt+KEY, and/or unwanted VT switch from Alt+Left/Right
This bug was fixed in the package kbd - 2.0.4-4ubuntu2 --- kbd (2.0.4-4ubuntu2) eoan; urgency=medium * kbd_mode: Add -f option and don't perform dangerous mode switches without it. In the back-ported fix kbd_mode exits with success, even when the dangerous mode change is skipped, just prints an error, to not break old scripts. (LP: #520546) -- Balint Reczey Thu, 09 May 2019 17:22:51 +0200 ** Changed in: kbd (Ubuntu Eoan) 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/520546 Title: Alt+KEY incorrectly behaves like Ctrl+Alt+KEY, and/or unwanted VT switch from Alt+Left/Right To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/520546/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1783906] Re: Linux 4.15 and onwards fails to initialize some hard drives
Ok thanks, please look at this some more, I will try to get back with you soon. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1783906 Title: Linux 4.15 and onwards fails to initialize some hard drives To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1783906/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1710971] Re: Unmatched entries in cron and secure
Thanks for forwarding your change upstream, it looks like they've incorporated the systemd-logind log handling, via commits dcb79597 and 44d6719b (the latter including mention of your patch), which are now included in the 7.5.0 release. So, I think we can close this bug as fixed in eoan. 14.04.6 support ended last month, so this isn't a candidate for backporting to that release, but if you need it in bionic or xenial, feel free to reopen. Btw, I notice upstream commit 4525ed0d tweaks the rules a bit to ignore New session entries, which may break your counting, so if that's something you're relying on you may want to test out the upstream code. That change is included in upstream's 7.5.1 but not 7.5.0. Debian and Ubuntu are on 7.5.0 right now; I'm not sure when we'll be pulling in 7.5.1 but feel free to file a new bug if there's followup work needed here. ** Changed in: logwatch (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/1710971 Title: Unmatched entries in cron and secure To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/logwatch/+bug/1710971/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1763608] Re: Netplan ignores Interfaces without IP Addresses
So; this has landed in Eoan now, and also in -proposed repositories for 18.04, 18.10, 19.04. I'll start doing testing on these releases, but since I don't have an openvswitch setup, any and all further independent confirmation that the issue is fixed (or indeed, if it's not), is welcome. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1763608 Title: Netplan ignores Interfaces without IP Addresses To manage notifications about this bug go to: https://bugs.launchpad.net/kolla/+bug/1763608/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1791312] Re: ubuntu 18.04 flickering screen with Radeon X1600
Being fixed in upstream https://cgit.freedesktop.org/~agd5f/linux/commit/?h=drm- next-5.2=2e26ccb119bde03584be53406bbd22e711b0d6e6 Maybe a candidate for SRUs too after the fix hits eoan (19.10). ** Also affects: linux via https://bugs.freedesktop.org/show_bug.cgi?id=108514 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1791312 Title: ubuntu 18.04 flickering screen with Radeon X1600 To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1791312/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1796193] Re: DistUpgradeViewNonInteractive crashes / requires interaction
For the xenial->bionic question, I had already implemented the workaround mentioned here to use Dpkg::Options::="--force-confdef" across all upgrade tests, which has been working fine. I can remove the workaround and try it if you are specifically interested in finding out whether it's necessary on the upgrade to bionic though. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1796193 Title: DistUpgradeViewNonInteractive crashes / requires interaction To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1796193/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1825444] Re: "make rpm" fails on CentOS after commit 947d3c208
This bug was fixed in the package cloud-init - 19.1-0ubuntu1 --- cloud-init (19.1-0ubuntu1) eoan; urgency=medium * New upstream release. - release 19.1 (LP: #1828479) - freebsd: add chpasswd pkg in the image [Gonéri Le Bouder] - tests: add Eoan release [Paride Legovini] - cc_mounts: check if mount -a on no-change fstab path [Jason Zions (MSFT)] (LP: #1825596) - replace remaining occurrences of LOG.warn - DataSourceAzure: Adjust timeout for polling IMDS [Anh Vo] - Azure: Changes to the Hyper-V KVP Reporter [Anh Vo] - git tests: no longer show warning about safe yaml. [Scott Moser] - tools/read-version: handle errors [Chad Miller] - net/sysconfig: only indicate available on known sysconfig distros (LP: #1819994) - packages: update rpm specs for new bash completion path (LP: #1825444) - test_azure: mock util.SeLinuxGuard where needed [Jason Zions (MSFT)] (LP: #1825253) - setup.py: install bash completion script in new location - mount_cb: do not pass sync and rw options to mount [Gonéri Le Bouder] (LP: #1645824) - cc_apt_configure: fix typo in apt documentation [Dominic Schlegel] -- Chad Smith Fri, 10 May 2019 12:11:06 -0600 ** Changed in: cloud-init (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/1825444 Title: "make rpm" fails on CentOS after commit 947d3c208 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1825444/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1583706] Re: unmatched entries for rsyslogd
Commits 32adbfdd and 3abbb24d address this issue, and both are included in upstream's 7.5.0 release, which is packaged for and released in Ubuntu disco (19.04). We can consider this fixed now. ** Changed in: logwatch (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/1583706 Title: unmatched entries for rsyslogd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/logwatch/+bug/1583706/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1825211] Re: package menu 2.1.47ubuntu3 failed to install/upgrade: triggers looping, abandoned
I was able to recreate this today by taking a stock cosmic lxc image, installing ubuntu-mate-desktop, and then upgrading to disco. Here's the DuplicateSignature from the crash: == DuplicateSignature = package:libvlc-bin:3.0.6-1 Setting up fontconfig (2.13.1-2ubuntu2) ... Regenerating fonts cache... done. dpkg: cycle found while processing triggers: chain of packages whose triggers are or may be responsible: bamfdaemon -> mime-support packages' pending triggers which are or may be unresolvable: libvlc-bin:amd64: /usr/lib/x86_64-linux-gnu/vlc/plugins dbus: /etc/dbus-1/system.d ca-certificates: update-ca-certificates gnome-icon-theme: /usr/share/icons/gnome libc-bin: ldconfig dictionaries-common: update-default-ispell: update-default-wordlist: aspell-autobuildhash hicolor-icon-theme: /usr/share/icons/hicolor initramfs-tools: update-initramfs mime-support: /usr/share/applications: /usr/lib/mime/packages bamfdaemon: /usr/share/applications dpkg: error processing package libvlc-bin:amd64 (--configure): triggers looping, abandoned I submitted bug 1828639 with details. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1825211 Title: package menu 2.1.47ubuntu3 failed to install/upgrade: triggers looping, abandoned To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/1825211/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1827788] Re: Add #ubuntu as 'get more help' resource in the docs
** Branch linked: lp:ubuntu-docs -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1827788 Title: Add #ubuntu as 'get more help' resource in the docs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-docs/+bug/1827788/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1824522] Re: package update-notifier-common 3.168.10 failed to install/upgrade: le sous-processus script post-installation installé a retourné une erreur de sortie d'état 1
This part might have something to do with the issue: sudo add-apt-repository ppa:jonathonf/python-3.6 sudo apt-get update sudo apt-get install python2.7-dev python3.5-dev python3.6-dev pylint -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1824522 Title: package update-notifier-common 3.168.10 failed to install/upgrade: le sous-processus script post-installation installé a retourné une erreur de sortie d'état 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-notifier/+bug/1824522/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1828495] Re: [KVM][CLX] CPUID_7_0_EDX_ARCH_CAPABILITIES is not enabled in VM.
** Also affects: qemu (Ubuntu) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed ** Changed in: qemu (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/1828495 Title: [KVM][CLX] CPUID_7_0_EDX_ARCH_CAPABILITIES is not enabled in VM. To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1828495/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1828466] Re: Dub binary not runnable in Disco
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: dub (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/1828466 Title: Dub binary not runnable in Disco To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dub/+bug/1828466/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1828649] [NEW] Wayland freeze
Public bug reported: When I switch to wayland the gnome desktop locks up before I see my desktop. It doesn't lock up when I have my laptop closed and only one display connected. When I connect up the second display, it locks up every time. I tried deleting my monitors.xml file.. that doesn't make any difference. I was able to get it to work by connecting one display via DisplayPort. When I connect the second display, via active HDMI to DisplayPort on dock, it doesn't work if I select Wayland. This wire configuration works fine with Xorg. Additionally, when I lift my laptop screen, one of my monitors goes out and re-enabling it causes another to go off. Linux kernel is not smart enough to drive the 3 displays. I am able to drive two monitors and have my laptop screen open in Windows just fine. Of importance is that my DisplayPort to HDMI adaptor is ACTIVE. If I was to use a PASSIVE adaptor, I cannot drive two external displays and the laptop display. With my laptop screen closed, I was able to drive both displays in Wayland just fine in 18.10 so this is a regression. The GNU/Linux kernel has always (as far as I know) been lacking in smarts to drive all three displays. This work system is has Intel 4000 Integrated video (Lenovo ThinkPad laptop). Main screen is 2560x1600 via DisplayPort to laptop. Secondary screen is 1920x1200 via DisplayPort to laptop dock. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri May 10 16:55:27 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: This is the first time GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:2203] InstallationDate: Installed on 2019-03-25 (46 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190325) MachineType: LENOVO 343522U ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic root=UUID=7e84182c-37f4-407a-91ca-1b6bbec80a00 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/15/2018 dmi.bios.vendor: LENOVO dmi.bios.version: GCETB2WW (2.72 ) dmi.board.asset.tag: Not Available dmi.board.name: 343522U dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGCETB2WW(2.72):bd11/15/2018:svnLENOVO:pn343522U:pvrThinkPadX230Tablet:rvnLENOVO:rn343522U:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad X230 Tablet dmi.product.name: 343522U dmi.product.sku: LENOVO_MT_3435 dmi.product.version: ThinkPad X230 Tablet dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20180925-2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco 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/1828649 Title: Wayland freeze To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1828649/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1799779] Re: LXD module installs the wrong ZFS package if it's missing
This bug is believed to be fixed in cloud-init in version 19.1. If this is still a problem for you, please make a comment and set the state back to New Thank you. ** Changed in: cloud-init 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/1799779 Title: LXD module installs the wrong ZFS package if it's missing To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1799779/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1811446] Re: chpasswd: is mangling certain password hashes
This bug is believed to be fixed in cloud-init in version 19.1. If this is still a problem for you, please make a comment and set the state back to New Thank you. ** Changed in: cloud-init 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/1811446 Title: chpasswd: is mangling certain password hashes To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1811446/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1828615] [NEW] v4l2loopback 10.0-1ubuntu1 ADT test failure with linux 5.0.0-14-generic
Public bug reported: [ Impact ] The DKMS package fails to install on kernels based on 5.0; specifically noticed in the Bionic HWE Edge kernel. [ Test Case ] Install the v4l2loopback-dkms package with a 5.0 kernel. The package should install without any errors. [ The Problem ] "do_gettimeofday" was deprecated and removed in the 5.0 kernels, so the package will not compile since the function it requires does not exist. [ Proposed Fix ] Port the following patch from the package developers which replaces calls to the deprecated API with appropriate wrapper functions: https://github.com/umlaeute/v4l2loopback/commit/afe0b233070d7ca5d6df83c5f2723d276dcd287d.patch [ Regression Potential ] I think regression potential is low if the proposed fix is accepted. The function calls that supplant the deprecated ones have been there since before kernel 4.15 (of which Bionic is based upon). amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/amd64/v/v4l2loopback/20190429_215733_875ac@/log.gz arm64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/arm64/v/v4l2loopback/20190429_220415_875ac@/log.gz i386: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/i386/v/v4l2loopback/20190429_215750_875ac@/log.gz ppc64el: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/ppc64el/v/v4l2loopback/20190429_215314_875ac@/log.gz s390x: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/s390x/v/v4l2loopback/20190429_214920_875ac@/log.gz ** Affects: v4l2loopback (Ubuntu) Importance: Undecided Assignee: Connor Kuehl (connork) Status: New ** Tags: 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/1828615 Title: v4l2loopback 10.0-1ubuntu1 ADT test failure with linux 5.0.0-14-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/v4l2loopback/+bug/1828615/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1828597] Re: KDump boot fails with nr_cpus=1
Okay, let's consider this option on makedumpfile side. I'll test it and provide a test package by next week. Cascardo. ** Also affects: makedumpfile (Ubuntu) Importance: Undecided Status: New ** Changed in: makedumpfile (Ubuntu Eoan) Importance: Undecided => High ** Changed in: makedumpfile (Ubuntu Eoan) Status: New => Confirmed ** Changed in: makedumpfile (Ubuntu Eoan) Assignee: (unassigned) => Thadeu Lima de Souza Cascardo (cascardo) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1828597 Title: KDump boot fails with nr_cpus=1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1828597/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1821315] Re: Brisk menu should allow keyboard-only navigation for buttom left corner items (end session, lock, turn off)
Reported upstream as https://github.com/solus-project/brisk-menu/issues/117 (deprecated) https://github.com/getsolus/brisk-menu/issues/8 ** Bug watch added: github.com/solus-project/brisk-menu/issues #117 https://github.com/solus-project/brisk-menu/issues/117 ** Bug watch added: github.com/getsolus/brisk-menu/issues #8 https://github.com/getsolus/brisk-menu/issues/8 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1821315 Title: Brisk menu should allow keyboard-only navigation for buttom left corner items (end session, lock, turn off) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/brisk-menu/+bug/1821315/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1828615] Re: v4l2loopback 10.0-1ubuntu1 ADT test failure with linux 5.0.0-14-generic
** Description changed: [ Impact ] The DKMS package fails to install on kernels based on 5.0; specifically noticed in the Bionic HWE Edge kernel. [ Test Case ] Install the v4l2loopback-dkms package with a 5.0 kernel. The package should install without any errors. + + [ Testing ] + + I tested this install process (using the .debdiff in comment #1) for + both 4.15.0-49-generic and 5.0.0-14-generic to test for regressions + since the changes introduced by this patch are not conditionally + compiled. + + - Create a Bionic 18.04 VM + - Install the Bionic Linux HWE Edge kernel from -proposed or install the built .debs located here: https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/ppa/+packages?field.name_filter=linux-hwe-edge_filter=published_filter=bionic + - Try installing v4l2loopback-dkms with apt (or you can pull the sources with "pull-lp-source v4l2loopback bionic" and build with "debuild -b -uc -us" + - Confirm that installation fails for the 5.0 kernel (it will succeed for 4.15) + - Pull the sources with "pull-lp-source v4l2loopback bionic" + - Apply the debdiff "debdiff-apply < path-to-diff-in-this-comment.debdiff" + - Build the package "debuild -b -uc -us" + - Install the .deb produced from the previous step "sudo dpkg --install path-to-deb.deb" + - Verify the installation completed successfully. You can also verify the output of "sudo dkms status" is correct. [ The Problem ] "do_gettimeofday" was deprecated and removed in the 5.0 kernels, so the package will not compile since the function it requires does not exist. [ Proposed Fix ] Port the following patch from the package developers which replaces calls to the deprecated API with appropriate wrapper functions: https://github.com/umlaeute/v4l2loopback/commit/afe0b233070d7ca5d6df83c5f2723d276dcd287d.patch [ Regression Potential ] I think regression potential is low if the proposed fix is accepted. The function calls that supplant the deprecated ones have been there since before kernel 4.15 (of which Bionic is based upon). - amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/amd64/v/v4l2loopback/20190429_215733_875ac@/log.gz - arm64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/arm64/v/v4l2loopback/20190429_220415_875ac@/log.gz - i386: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/i386/v/v4l2loopback/20190429_215750_875ac@/log.gz - ppc64el: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/ppc64el/v/v4l2loopback/20190429_215314_875ac@/log.gz - s390x: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/s390x/v/v4l2loopback/20190429_214920_875ac@/log.gz + amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/amd64/v/v4l2loopback/20190429_215733_875ac@/log.gz + arm64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/arm64/v/v4l2loopback/20190429_220415_875ac@/log.gz + i386: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/i386/v/v4l2loopback/20190429_215750_875ac@/log.gz + ppc64el: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/ppc64el/v/v4l2loopback/20190429_215314_875ac@/log.gz + s390x: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/s390x/v/v4l2loopback/20190429_214920_875ac@/log.gz ** Description changed: [ Impact ] The DKMS package fails to install on kernels based on 5.0; specifically noticed in the Bionic HWE Edge kernel. [ Test Case ] Install the v4l2loopback-dkms package with a 5.0 kernel. The package should install without any errors. + + + [ The Problem ] + + "do_gettimeofday" was deprecated and removed in the 5.0 kernels, so the + package will not compile since the function it requires does not exist. + + [ Proposed Fix ] + + Port the following patch from the package developers which replaces + calls to the deprecated API with appropriate wrapper functions: + https://github.com/umlaeute/v4l2loopback/commit/afe0b233070d7ca5d6df83c5f2723d276dcd287d.patch [ Testing ] I tested this install process (using the .debdiff in comment #1) for both 4.15.0-49-generic and 5.0.0-14-generic to test for regressions since the changes introduced by this patch are not conditionally compiled. - Create a Bionic 18.04 VM - Install the Bionic Linux HWE Edge kernel from -proposed or install the built .debs
[Bug 1828628] [NEW] cntlm logs every connection to systemd journal log
Public bug reported: Can you disable cntlm from logging every connection to the systemd journal log? I did not see an option to turn it off the excess logging. Thanks! ** Affects: cntlm (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/1828628 Title: cntlm logs every connection to systemd journal log To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cntlm/+bug/1828628/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1827335] Comment bridged from LTC Bugzilla
--- Comment From mranw...@us.ibm.com 2019-05-10 17:33 EDT--- >From the opal-utils package can you try: sudo opal-gard list? I think if >there's something there you can use opal-gard show to get more details. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1827335 Title: Unable to put offline CPU back online on Bionic/B-hwe-edge P9 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1827335/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1828632] [NEW] bionic i386 kernel crashes in memory pressure situations
Public bug reported: The linux-image-4.15.0-49-generic (currently in bionic-proposed) can be made to crash in a kvm guest with memory pressure. The reproducer used is to attempt to run netbeans with openjdk-8-jre installed as the only jvm. It will fail to run, and when it fails, it also causes gnome-shell to crash. After 3 to 5 repeats of this, the kernel will crash with the following oops in dmesg: [ 545.926175] rfkill: input handler enabled [ 546.117550] [ cut here ] [ 546.117552] kernel BUG at /build/linux-S9wgEU/linux-4.15.0/arch/x86/mm/fault.c:268! [ 546.117564] invalid opcode: [#1] SMP PTI [ 546.117565] Modules linked in: snd_hda_codec_generic snd_hda_intel snd_hda_codec snd_hda_core snd_hwdep snd_pcm kvm_intel kvm snd_seq_midi snd_seq_midi_e vent snd_rawmidi irqbypass snd_seq snd_seq_device input_leds joydev snd_timer serio_raw snd soundcore qemu_fw_cfg mac_hid binfmt_misc sch_fq_codel ib_iser r dma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi parport_pc ppdev lp parport ip_tables x_tables autofs4 btrfs zstd_compress r aid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear hid_generic usbhid hid crc32_pc lmul pcbc qxl ttm drm_kms_helper syscopyarea aesni_intel aes_i586 sysfillrect sysimgblt crypto_simd cryptd fb_sys_fops psmouse virtio_blk virtio_net floppy drm pata_acpi i2c_piix4 [ 546.117600] CPU: 0 PID: 1335 Comm: Xorg Not tainted 4.15.0-49-generic #53-Ubuntu [ 546.117600] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.10.2-1ubuntu1 04/01/2014 [ 546.117618] EIP: vmalloc_fault+0x229/0x240 [ 546.117618] EFLAGS: 00010086 CPU: 0 [ 546.117619] EAX: 026c EBX: c3e20c50 ECX: f8eb EDX: [ 546.117620] ESI: f140 EDI: f800 EBP: eddc1934 ESP: eddc1918 [ 546.117621] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068 [ 546.117621] CR0: 80050033 CR2: f140 CR3: 25f16000 CR4: 001406f0 [ 546.117624] Call Trace: [ 546.117637] ? kvm_async_pf_task_wait+0x1b0/0x1b0 [ 546.117638] __do_page_fault+0x39d/0x510 [ 546.117640] ? kvm_async_pf_task_wait+0x1b0/0x1b0 [ 546.117641] do_page_fault+0x27/0xf0 [ 546.117644] ? kvm_async_pf_task_wait+0x1b0/0x1b0 [ 546.117645] do_async_page_fault+0x55/0x90 [ 546.117655] common_exception+0x130/0x136 [ 546.117659] EIP: qxl_image_init+0x338/0x390 [qxl] [ 546.117659] EFLAGS: 00010286 CPU: 0 [ 546.117660] EAX: fffbb000 EBX: 0fec ECX: fffbb014 EDX: 0030 [ 546.117661] ESI: f140 EDI: fffbb018 EBP: eddc1a18 ESP: eddc19e4 [ 546.117661] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068 [ 546.117663] ? ioremap_nocache+0x12/0x20 [ 546.117665] qxl_draw_dirty_fb+0x1cd/0x3d0 [qxl] [ 546.117668] qxl_primary_atomic_update+0x159/0x2c0 [qxl] [ 546.117680] drm_atomic_helper_commit_planes+0xe8/0x240 [drm_kms_helper] [ 546.117684] drm_atomic_helper_commit_tail+0x23/0x50 [drm_kms_helper] [ 546.117688] commit_tail+0x5d/0x60 [drm_kms_helper] [ 546.117691] drm_atomic_helper_commit+0xf7/0x100 [drm_kms_helper] [ 546.117695] ? drm_atomic_helper_setup_commit+0x3f0/0x3f0 [drm_kms_helper] [ 546.117715] drm_atomic_commit+0x3f/0x50 [drm] [ 546.117719] restore_fbdev_mode_atomic+0x16b/0x1c0 [drm_kms_helper] [ 546.117723] restore_fbdev_mode+0x2c/0x150 [drm_kms_helper] [ 546.117725] ? _cond_resched+0x17/0x40 [ 546.117729] drm_fb_helper_restore_fbdev_mode_unlocked.part.32+0x21/0x70 [drm_kms_helper] [ 546.117732] drm_fb_helper_set_par+0x45/0x80 [drm_kms_helper] [ 546.117743] fb_set_var+0x1a9/0x440 [ 546.117750] ? wakeup_preempt_entity+0x73/0x80 [ 546.117752] ? check_preempt_wakeup+0x108/0x230 [ 546.117753] ? check_cfs_rq_runtime+0x70/0x70 [ 546.117755] ? check_preempt_curr+0x27/0x80 [ 546.117757] ? ttwu_do_wakeup+0x17/0x190 [ 546.117760] fbcon_blank+0x29e/0x370 [ 546.117772] ? __switch_to_asm+0x27/0x4c [ 546.117774] ? fbcon_cursor+0x1b0/0x1b0 [ 546.117782] do_unblank_screen+0xaa/0x1b0 [ 546.117784] vt_ioctl+0x4e3/0x11e0 [ 546.117786] ? complete_change_console+0xe0/0xe0 [ 546.117788] tty_ioctl+0xec/0x910 [ 546.117793] ? jbd2_journal_stop+0xd7/0x3e0 [ 546.117797] ? ext4_free_inode+0x3c7/0x560 [ 546.117798] ? ext4_free_inode+0x1f2/0x560 [ 546.117812] ? intel_pmu_lbr_init_atom+0x46/0x50 [ 546.117819] ? call_rcu_sched+0x14/0x20 [ 546.117821] ? tty_vhangup+0x20/0x20 [ 546.117826] do_vfs_ioctl+0x93/0x6b0 [ 546.117831] ? destroy_inode+0x34/0x60 [ 546.117833] ? __raw_callee_save___pv_queued_spin_unlock+0x9/0x10 [ 546.117834] ? putname+0x47/0x60 [ 546.117836] ? __fdget+0x12/0x20 [ 546.117840] ? SyS_epoll_ctl+0x5b/0x990 [ 546.117841] ? putname+0x47/0x60 [ 546.117844] ? do_unlinkat+0x7f/0x2c0 [ 546.117846] SyS_ioctl+0x58/0x70 [ 546.117848] do_fast_syscall_32+0x7f/0x1e0 [ 546.117850] entry_SYSENTER_32+0x6b/0xbe [ 546.117860] EIP: 0xb7f9fd09 [ 546.117861] EFLAGS: 00200296 CPU: 0 [ 546.117861] EAX: ffda EBX: 000b ECX: 4b3a
[Bug 1796193] Re: DistUpgradeViewNonInteractive crashes / requires interaction
This bug was fixed in the package ubuntu-release-upgrader - 1:19.10.5 --- ubuntu-release-upgrader (1:19.10.5) eoan; urgency=medium * DistUpgrade/DistUpgradeViewNonInteractive.py: when responding to a conffile prompt with "n" use bytes not a string. (LP: #1796193) * DistUpgrade/DistUpgradeController.py: set a default value for devRelease even if there are no options specified. (LP: #1827441) -- Brian Murray Fri, 10 May 2019 13:30:07 -0700 ** Changed in: ubuntu-release-upgrader (Ubuntu Eoan) 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/1796193 Title: DistUpgradeViewNonInteractive crashes / requires interaction To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1796193/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1815123] Re: Hardware test stress-ng-cpu-long bind failed
** Changed in: maas Status: Incomplete => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1815123 Title: Hardware test stress-ng-cpu-long bind failed To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1815123/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1828495] Re: [KVM][CLX] CPUID_7_0_EDX_ARCH_CAPABILITIES is not enabled in VM.
List of commits needed to enable ARCH_CAPABILITIES:
Kernel:
commit 2bdb76c015df7125783d8394d6339d181cb5bc30
Author: Xiaoyao Li
Date: Fri Mar 8 15:57:20 2019 +0800
kvm/x86: Move MSR_IA32_ARCH_CAPABILITIES to array emulated_msrs
QEMU:
commit 014018e19b3c54dd1bf5072bc912ceffea40abe8
Author: Eduardo Habkost
Date: Fri Jan 25 20:06:06 2019 -0200
i386: Make arch_capabilities migratable
commit 485b1d256bcb0874bcde0223727c159b6837e6f8
Author: Eduardo Habkost
Date: Fri Jan 25 20:06:05 2019 -0200
i386: kvm: Disable arch_capabilities if MSR can't be set
commit b0a1980384fc265d91de7e09aa5fe531a69e6288
Author: Tao Xu
Date: Thu Dec 27 10:43:03 2018 +0800
i386: Update stepping of Cascadelake-Server
commit aec5e9c3a94cf8b7920f59bef69a6f426092c4a0
Author: Bandan Das
Date: Sun Nov 25 23:17:28 2018 -0500
kvm: Use KVM_GET_MSR_INDEX_LIST for MSR_IA32_ARCH_CAPABILITIES support
commit 07585923485952bf4cb7da563c9f91fecc85d09c
Author: Robert Hoo
Date: Mon Oct 15 12:47:24 2018 +0800
x86: Data structure changes to support MSR based features
commit f57bceb6ab5163ddd6c41ff4344ab8cf28a9c63d
Author: Robert Hoo
Date: Mon Oct 15 12:47:23 2018 +0800
kvm: Add support to KVM_GET_MSR_FEATURE_INDEX_LIST and KVM_GET_MSRS system
ioctl
commit d86f963694df27f11b3681ffd225c9362de1b634
Author: Robert Hoo
Date: Mon Oct 15 12:47:25 2018 +0800
x86: define a new MSR based feature word – FEATURE_WORDS_ARCH_CAPABILITIES
commit c7a88b52f62b30c04158eeb07f73e3f72221b6a8
Author: Tao Xu
Date: Wed Sep 19 11:11:22 2018 +0800
i386: Add new model of Cascadelake-Server
commit 3fc7c73139d2d38ae80c3b0bc963b1ac1555924c
Author: Robert Hoo
Date: Thu Jul 5 17:09:55 2018 +0800
i386: Add CPUID bit and feature words for IA32_ARCH_CAPABILITIES MSR
commit 8a11c62da9146dd89aee98947e6bd831e65a970d
Author: Robert Hoo
Date: Thu Jul 5 17:09:58 2018 +0800
i386: Add new CPU model Icelake-{Server,Client}
commit 8c80c99fcceabd0708a5a83f08577e778c9419f5
Author: Robert Hoo
Date: Thu Jul 5 17:09:54 2018 +0800
i386: Add new MSR indices for IA32_PRED_CMD and IA32_ARCH_CAPABILITIES
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1828495
Title:
[KVM][CLX] CPUID_7_0_EDX_ARCH_CAPABILITIES is not enabled in VM.
To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/1828495/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1828467] Re: [sru] remove juju-db stop/start service interactions
** Changed in: sosreport (Ubuntu Trusty) Status: New => 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/1828467 Title: [sru] remove juju-db stop/start service interactions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sosreport/+bug/1828467/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1796193] Re: DistUpgradeViewNonInteractive crashes / requires interaction
To elaborate more I seen the following in the console output of a job which upgrades from bionic to cosmic: Setting up ubuntu-release-upgrader-core (1:18.10.11.6) ... Configuration file '/etc/update-manager/release-upgrades' ==> Modified (by you or by a script) since installation. ==> Package distributor has shipped an updated version. What would you like to do about it ? Your options are: Y or I : install the package maintainer's version N or O : keep your currently-installed version D : show the differences between the versions Z : start a shell to examine the situation The default action is to keep your current version. *** release-upgrades (Y/I/N/O/D/Z) [default=N] ? dpkg: error: dpkg status database is locked by another process auto-upgrade [06:09:35]: ERROR: ERROR: Something went wrong with the upgrade. release-upgrades has had Prompt changed from lts to normal so that we can test the upgrade to cosmic and then we get the bytes like object crash. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1796193 Title: DistUpgradeViewNonInteractive crashes / requires interaction To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1796193/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1828467] Re: [sru] remove juju-db stop/start service interactions
I marked Trusty as 'Won't Fix' as it reached EOL. ** Description changed: [Impact] The juju plugin will stop and start the juju-db service during data collection. sosreport should not impact running services, or attempt to recover them. This has been reported upstream[0] and will be fixed by the juju 2.x refactor[1] This is a stop-gap tracking the removal of the juju-db service restart code in existing sosreport releases. [0] - https://github.com/sosreport/sos/issues/1653 [1] - https://github.com/sosreport/sos/pull/1670 [Test Case] - * Make sure you are in the juju controller. + * Make sure you are in the juju controller. * Install sosreport * Look mongod PID before ** $ pidof mongod * Run sosreport, ensuring that the juju plugin is exercised * Confirm the juju-db service was not restarted, and mongoexport data captured. * Look mongod PID after ** $ pidof mongod - Check for errors while running, or in /tmp/sosreport-*/sos_logs/ The offending function ensure_service_is_running() in theory doesn't create any harm unless juju plugin is exercised during a sosreport run from a juju controller where mongod and/or juju-db resides. [Regression Potential] * Risk is low. * Change is limited in scope to the juju plugin. * Worst-case scenario is that the mongoexport command will fail to collect any data, which won't affect core functionality of sosreport itself nor impact other sosreport plugins. + + [Other information] + + We will temporary divert from the juju plugin found upstream and debian, + while the refactoring is completed to avoid any situation where + sosreport is run on a controller since it may have production impact on + Ubuntu juju environment. + + Once the refactoring of the juju plugin is completed upstream, we will + make sure to update debian and put the juju plugin align with what found + upstream and debian. + + Actually, sosreport 3.7 micro-release is waiting on this via LP: + #1825010. ** Description changed: [Impact] The juju plugin will stop and start the juju-db service during data collection. sosreport should not impact running services, or attempt to recover them. This has been reported upstream[0] and will be fixed by the juju 2.x refactor[1] This is a stop-gap tracking the removal of the juju-db service restart code in existing sosreport releases. [0] - https://github.com/sosreport/sos/issues/1653 [1] - https://github.com/sosreport/sos/pull/1670 [Test Case] * Make sure you are in the juju controller. * Install sosreport * Look mongod PID before ** $ pidof mongod * Run sosreport, ensuring that the juju plugin is exercised * Confirm the juju-db service was not restarted, and mongoexport data captured. * Look mongod PID after ** $ pidof mongod Check for errors while running, or in /tmp/sosreport-*/sos_logs/ The offending function ensure_service_is_running() in theory doesn't create any harm unless juju plugin is exercised during a sosreport run from a juju controller where mongod and/or juju-db resides. [Regression Potential] * Risk is low. * Change is limited in scope to the juju plugin. * Worst-case scenario is that the mongoexport command will fail to collect any data, which won't affect core functionality of sosreport itself nor impact other sosreport plugins. [Other information] We will temporary divert from the juju plugin found upstream and debian, while the refactoring is completed to avoid any situation where sosreport is run on a controller since it may have production impact on Ubuntu juju environment. Once the refactoring of the juju plugin is completed upstream, we will make sure to update debian and put the juju plugin align with what found upstream and debian. - Actually, sosreport 3.7 micro-release is waiting on this via LP: - #1825010. + Actually, sosreport 3.7 micro-release is blocked waiting for this + refactoring to be completed (LP: #1825010). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1828467 Title: [sru] remove juju-db stop/start service interactions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sosreport/+bug/1828467/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1828467] Re: [sru] remove juju-db stop/start service interactions
I marked Trusty as 'Won't Fix' in it reached EOL. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1828467 Title: [sru] remove juju-db stop/start service interactions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sosreport/+bug/1828467/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1796193] Re: unattended do-release-upgrade asks about /etc/cron.daily/apt-compat
Well I'm fairly certain this issue, DistUpgradeViewNonInteractive not being non-interactive, is contributing to automatic upgrade testing so I'll be SRU'ing this change everywhere. ** Summary changed: - unattended do-release-upgrade asks about /etc/cron.daily/apt-compat + DistUpgradeViewNonInteractive crashes / requires interaction ** Also affects: apt (Ubuntu Disco) Importance: Undecided Status: New ** Also affects: ubuntu-release-upgrader (Ubuntu Disco) Importance: Undecided Status: New ** Also affects: apt (Ubuntu Cosmic) Importance: Undecided Status: New ** Also affects: ubuntu-release-upgrader (Ubuntu Cosmic) Importance: Undecided Status: New ** Changed in: ubuntu-release-upgrader (Ubuntu Disco) Status: New => In Progress ** Changed in: ubuntu-release-upgrader (Ubuntu Disco) Assignee: (unassigned) => Brian Murray (brian-murray) ** Changed in: ubuntu-release-upgrader (Ubuntu Cosmic) Status: New => In Progress ** Changed in: ubuntu-release-upgrader (Ubuntu Cosmic) Assignee: (unassigned) => Brian Murray (brian-murray) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1796193 Title: DistUpgradeViewNonInteractive crashes / requires interaction To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1796193/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1828625] Re: Can't purge if apt-get update fails (18.04)
And I guess the solution is in deleting "exit 1" on line 120 of bionic ppa-purge script -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1828625 Title: Can't purge if apt-get update fails (18.04) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ppa-purge/+bug/1828625/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1828625] [NEW] Can't purge if apt-get update fails (18.04)
Public bug reported: I want to purge buggy ppa that makes apt-get update to report error, but I can't because apt-get update reports error. It's a circle. I can remember a good times when ppa-purge didn't call for apt-get update at all (or that was "add-apt-repository", don't remember...). And everything was ok. I think it's just a wasting of time in the most cases. If I wish to "apt-get update" I'd like to do it manually. But ppa-purge does't have a way to let me avoid it. The buggy ppa is ppa:swatchbooker/ppa. It doesn't have a Release file for bionic for now so "apt-get update" passes the error to ppa-purge and that's it. One can try to add this repo and then ppa-purge it on Ubuntu bionic. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ppa-purge 0.2.8+bzr63 ProcVersionSignature: Ubuntu 4.15.0-48.51-generic 4.15.18 Uname: Linux 4.15.0-48-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: LXDE Date: Fri May 10 23:05:17 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2018-06-11 (333 days ago) InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all SourcePackage: ppa-purge UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ppa-purge (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/1828625 Title: Can't purge if apt-get update fails (18.04) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ppa-purge/+bug/1828625/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1796193] Re: DistUpgradeViewNonInteractive crashes / requires interaction
** Description changed: - I'm trying to do some automated testing that involved upgrading a system - from xenial to bionic, so I need it to not ask for user input. + [Impact] + The NonInteractive view of ubuntu-release-upgrader doesn't work so it is hard to automate upgrade testing. + + [Test Case] + You need to create a situation where you'll receive a conffile prompt since the handling of those is broken. + + 1) On a bionic system modify /etc/update-manager/release-upgrades so that Prompt=normal + 2) Test an upgrade from bionic to cosmic or disco i.e. run do-release-upgrade + 3) Observe the upgrade hang on the '/etc/update-manager/release-upgrades' conffifle and the following in /var/log/dist-upgrade/main.log + "2019-05-10 21:21:21,313 WARNING got a conffile-prompt from dpkg for file: '/etc/update-manager/release-upgrades' + 2019-05-10 21:21:26,319 ERROR error 'a bytes-like object is required, not 'str'' when trying to write to the conffile" + + With the version of the release-upgrader from -proposed you'll no longer + observe the upgrade process hanging. + + [Regression Potential] + The fix is making it so that a byte object is passed to the prompt instead of a string one so there really isn't one. + + [Original Description] + I'm trying to do some automated testing that involved upgrading a system from xenial to bionic, so I need it to not ask for user input. Before running do-release-upgrade, the system got a fresh dist-upgrade and reboot. To avoid interactive responses, I'm using: $ sudo do-release-upgrade -d -f DistUpgradeViewNonInteractive Part way through the upgrade, I do get prompted for something though: Preparing to unpack .../apt_1.6.3ubuntu0.1_amd64.deb ... Unpacking apt (1.6.3ubuntu0.1) over (1.2.27) ... Processing triggers for libc-bin (2.27-3ubuntu1) ... /sbin/ldconfig.real: Warning: ignoring configuration file that cannot be opened: /etc/ld.so.conf.d/x86_64-linux-gnu_EGL.conf: No such file or directory /sbin/ldconfig.real: Warning: ignoring configuration file that cannot be opened: /etc/ld.so.conf.d/x86_64-linux-gnu_GL.conf: No such file or directory Setting up apt (1.6.3ubuntu0.1) ... Installing new version of config file /etc/apt/apt.conf.d/01autoremove ... - Configuration file '/etc/cron.daily/apt-compat' - ==> Deleted (by you or by a script) since installation. + ==> Deleted (by you or by a script) since installation. - ==> Package distributor has shipped an updated version. + ==> Package distributor has shipped an updated version. -What would you like to do about it ? Your options are: + What would you like to do about it ? Your options are: - Y or I : install the package maintainer's version + Y or I : install the package maintainer's version - N or O : keep your currently-installed version + N or O : keep your currently-installed version - D : show the differences between the versions + D : show the differences between the versions - Z : start a shell to examine the situation + Z : start a shell to examine the situation - The default action is to keep your current version. + The default action is to keep your current version. Comparing the sha1 of apt-compat before the upgrade to another xenial system that has been unmodified, they are the same: In /var/log/dist-upgrade/main.log, I also found this: 2018-10-04 14:20:24,575 WARNING got a conffile-prompt from dpkg for file: '/etc/cron.daily/apt-compat' 2018-10-04 14:20:29,580 ERROR error 'a bytes-like object is required, not 'str'' when trying to write to the conffile -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1796193 Title: DistUpgradeViewNonInteractive crashes / requires interaction To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1796193/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1828136] Re: [Intel DH67CL, Realtek ALC892, Grey SPDIF Out, Rear] No sound at all
I rebooted, ran pactl list cards, ran alsa force reload, then re-ran the pactl command. Results was as you predicted. The pactl outputs before and after appear below. Here's the before output: Card #0 Name: alsa_card.pci-_01_00.1 Driver: module-alsa-card.c Owner Module: 5 Properties: alsa.card = "1" alsa.card_name = "HDA NVidia" alsa.long_card_name = "HDA NVidia at 0xfe08 irq 17" alsa.driver_name = "snd_hda_intel" device.bus_path = "pci-:01:00.1" sysfs.path = "/devices/pci:00/:00:01.0/:01:00.1/sound/card1" device.bus = "pci" device.vendor.id = "10de" device.vendor.name = "NVIDIA Corporation" device.product.id = "0fbc" device.string = "1" device.description = "HDA NVidia" module-udev-detect.discovered = "1" device.icon_name = "audio-card-pci" Profiles: output:hdmi-stereo: Digital Stereo (HDMI) Output (sinks: 1, sources: 0, priority: 5900, available: no) output:hdmi-surround: Digital Surround 5.1 (HDMI) Output (sinks: 1, sources: 0, priority: 800, available: no) output:hdmi-surround71: Digital Surround 7.1 (HDMI) Output (sinks: 1, sources: 0, priority: 800, available: no) output:hdmi-stereo-extra1: Digital Stereo (HDMI 2) Output (sinks: 1, sources: 0, priority: 5700, available: yes) output:hdmi-stereo-extra2: Digital Stereo (HDMI 3) Output (sinks: 1, sources: 0, priority: 5700, available: no) output:hdmi-surround-extra2: Digital Surround 5.1 (HDMI 3) Output (sinks: 1, sources: 0, priority: 600, available: no) output:hdmi-surround71-extra2: Digital Surround 7.1 (HDMI 3) Output (sinks: 1, sources: 0, priority: 600, available: no) off: Off (sinks: 0, sources: 0, priority: 0, available: yes) Active Profile: off Ports: hdmi-output-0: HDMI / DisplayPort (priority: 5900, latency offset: 0 usec, not available) Properties: device.icon_name = "video-display" Part of profile(s): output:hdmi-stereo, output:hdmi-surround, output:hdmi-surround71 hdmi-output-1: HDMI / DisplayPort 2 (priority: 5800, latency offset: 0 usec, available) Properties: device.icon_name = "video-display" device.product.name = "DELL U2715H " Part of profile(s): output:hdmi-stereo-extra1 hdmi-output-2: HDMI / DisplayPort 3 (priority: 5700, latency offset: 0 usec, not available) Properties: device.icon_name = "video-display" Part of profile(s): output:hdmi-stereo-extra2, output:hdmi-surround-extra2, output:hdmi-surround71-extra2 --- Here is the after output: Card #0 Name: alsa_card.pci-_01_00.1 Driver: module-alsa-card.c Owner Module: 5 Properties: alsa.card = "1" alsa.card_name = "HDA NVidia" alsa.long_card_name = "HDA NVidia at 0xfe08 irq 17" alsa.driver_name = "snd_hda_intel" device.bus_path = "pci-:01:00.1" sysfs.path = "/devices/pci:00/:00:01.0/:01:00.1/sound/card1" device.bus = "pci" device.vendor.id = "10de" device.vendor.name = "NVIDIA Corporation" device.product.id = "0fbc" device.string = "1" device.description = "HDA NVidia" module-udev-detect.discovered = "1" device.icon_name = "audio-card-pci" Profiles: output:hdmi-stereo: Digital Stereo (HDMI) Output (sinks: 1, sources: 0, priority: 5900, available: no) output:hdmi-surround: Digital Surround 5.1 (HDMI) Output (sinks: 1, sources: 0, priority: 800, available: no) output:hdmi-surround71: Digital Surround 7.1 (HDMI) Output (sinks: 1, sources: 0, priority: 800, available: no) output:hdmi-stereo-extra1: Digital Stereo (HDMI 2) Output (sinks: 1, sources: 0, priority: 5700, available: yes) output:hdmi-stereo-extra2: Digital Stereo (HDMI 3) Output (sinks: 1, sources: 0, priority: 5700, available: no) output:hdmi-surround-extra2: Digital Surround 5.1 (HDMI 3) Output (sinks: 1, sources: 0, priority: 600, available: no) output:hdmi-surround71-extra2: Digital Surround 7.1 (HDMI 3) Output (sinks: 1, sources: 0, priority: 600, available: no) off:
[Bug 1828568] Re: Ubuntu 18.04.2 LTS amd64 installer hangs shortly after boot unless acpi=off and noapic
What magic is required to get into safe graphic mode from the Disco live USB? (normal boot on that version fails in the same way) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1828568 Title: Ubuntu 18.04.2 LTS amd64 installer hangs shortly after boot unless acpi=off and noapic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1828568/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1606741] Re: [SRU] Metadata service for instances is unavailable when the l3-agent on the compute host is dvr_snat mode
Hello Zhixin, or anyone else affected, Accepted neutron into cosmic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/neutron/2:13.0.2-0ubuntu3.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-cosmic to verification-done-cosmic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-cosmic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: neutron (Ubuntu Cosmic) Status: Triaged => Fix Committed ** Tags added: verification-needed verification-needed-cosmic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1606741 Title: [SRU] Metadata service for instances is unavailable when the l3-agent on the compute host is dvr_snat mode To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1606741/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1828622] [NEW] No network in AWS (VPC EC2 instance) after launching an instance from an AMI captured earlier
Public bug reported:
This is a follow on from https://bugs.launchpad.net/ubuntu/+source
/cloud-init/+bug/1802073 + its fix in: https://git.launchpad.net/cloud-
init/commit/?id=0bb4c74e
After a clean launch of Ubuntu 18.04.2 on a t3.small AWS EC2 instance,
in a VPC in the eu-west-1 region, we can see the following:
---snip---
root@ip-172-31-23-210:~# cat /etc/os-release
NAME="Ubuntu"
VERSION="18.04.2 LTS (Bionic Beaver)"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 18.04.2 LTS"
VERSION_ID="18.04"
HOME_URL="https://www.ubuntu.com/;
SUPPORT_URL="https://help.ubuntu.com/;
BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/;
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy;
VERSION_CODENAME=bionic
UBUNTU_CODENAME=bionic
root@ip-172-31-23-210:~# dpkg -l | grep '\(cloud-init.*\|netplan.*\|ifupdown\)'
ii cloud-init 18.4-0ubuntu1~18.04.1 all
Init scripts for cloud instances
ii cloud-initramfs-copymods 0.40ubuntu1.1 all
copy initramfs modules into root filesystem for later use
ii cloud-initramfs-dyn-netconf0.40ubuntu1.1 all
write a network interface file in /run for BOOTIF
ii netplan.io 0.40.1~18.04.4amd64
YAML network configuration abstraction for various backends
root@ip-172-31-23-210:~# cat /etc/netplan/50-cloud-init.yaml
# This file is generated from information provided by
# the datasource. Changes to it will not persist across an instance.
# To disable cloud-init's network configuration capabilities, write a file
# /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following:
# network: {config: disabled}
network:
version: 2
ethernets:
ens5:
dhcp4: true
match:
macaddress: 06:bd:10:32:ce:7e
set-name: ens5
root@ip-172-31-23-210:~#
root@ip-172-31-23-210:~# ip addr
1: lo: mtu 65536 qdisc noqueue state UNKNOWN group
default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: ens5: mtu 9001 qdisc mq state UP group
default qlen 1000
link/ether 06:bd:10:32:ce:7e brd ff:ff:ff:ff:ff:ff
inet 172.31.23.210/20 brd 172.31.31.255 scope global dynamic ens5
valid_lft 3510sec preferred_lft 3510sec
inet6 fe80::4bd:10ff:fe32:ce7e/64 scope link
valid_lft forever preferred_lft forever
root@ip-172-31-23-210:~#
---snip---
At this point, I installed all OS updates via: apt-get clean;apt-get
update;apt-get dist-upgrade;
I rebooted the machine and checked the version of packages now
installed:
---snip---
root@ip-172-31-23-210:~# dpkg -l | grep '\(cloud-init.*\|netplan.*\|ifupdown\)'
ii cloud-init 18.5-45-g3554ffe8-0ubuntu1~18.04.1 all
Init scripts for cloud instances
ii cloud-initramfs-copymods 0.40ubuntu1.1 all
copy initramfs modules into root filesystem for later use
ii cloud-initramfs-dyn-netconf0.40ubuntu1.1 all
write a network interface file in /run for BOOTIF
ii netplan.io 0.96-0ubuntu0.18.04.4 amd64
YAML network configuration abstraction for various backends
---snip---
1. The contents of the /etc/netplan/50-cloud-init.yaml file remained the
same as above after OS updates.
2. This means that if this machine is powered off and an AMI taken of
it, any new EC2 instances launched from that AMI will not have a working
network since the mac address of the new EC2 instances will not match
the "macaddress" line in the /etc/netplan/50-cloud-init.yaml file.
3. This happens because the mac address of a VPC EC2 instance is tied to
the ENI associated to the EC2 instance.
4. When a new instance is launched from the capture AMI, it will get a
new ENI and hence a new MAC address. So although the network
configuration file should be regenerated at first boot in the newly
launched instance, this currently doesn't happen. I do not know why.
** Affects: cloud-init (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/1828622
Title:
No network in AWS (VPC EC2 instance) after launching an instance from
an AMI captured earlier
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1828622/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1827441] Re: ubuntu-release-upgrader crashed with configparser.NoOptionError: No option 'devrelease' in section: 'Options'
** Changed in: ubuntu-release-upgrader (Ubuntu) Status: New => In Progress ** Changed in: ubuntu-release-upgrader (Ubuntu) Assignee: (unassigned) => Brian Murray (brian-murray) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1827441 Title: ubuntu-release-upgrader crashed with configparser.NoOptionError: No option 'devrelease' in section: 'Options' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1827441/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1827930] Re: [SRU] Please generate tarball for WSL
** Merge proposal linked: https://code.launchpad.net/~rbalint/livecd-rootfs/+git/livecd-rootfs/+merge/367293 ** Merge proposal linked: https://code.launchpad.net/~rbalint/livecd-rootfs/+git/livecd-rootfs/+merge/367294 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1827930 Title: [SRU] Please generate tarball for WSL To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1827930/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1111610]
Hello folks,
revisiting. Rejoice! Progress has been made.
*
https://source.winehq.org/git/wine.git/commitdiff/2aa494686133bf4c4b6b054a45bf1d1d429acdc5
("mspatcha: Add functions to API header file.")
*
https://source.winehq.org/git/wine.git/commitdiff/8695a6986ef2b7cae7c1f3247fec8e8e14de1971
("mspatcha: Partially implement ApplyPatchToFileW and related
functions.")
--- quote ---
This can patch non-executables and 64-bit executable files, but patching of
32-bit executables is not supported. They are subject to special processing
which alters PE relocations to match with those in the old file to improve
compression. To reverse this, the meaning of the decoding data must be
interpreted. Details, including where to find that data in the patch file, are
included in pa19.c. Interleaved decompression of large files is also not
supported.
--- quote ---
*
https://source.winehq.org/git/wine.git/commitdiff/f8c25628266f025e01332b780c793d96d97dad25
("mspatcha: Add stubs for signature and normalization functions.")
Thanks Conor so far!
Adding stable download link from Internet Archive for one of the
smallest installers (MS SQL Server Express):
https://web.archive.org/web/20130318195510/http://download.microsoft.com/download/6/C/7
/6C7458CA-8B07-411E-9E3B-0DED20512696/SQLEXPR32.EXE
--- snip ---
$ WINEDEBUG=+seh,+relay,+mspatcha wine ./SQLEXPR32.EXE >>log.txt 2>&1
...
002a:Call KERNEL32.LoadLibraryA(0034f44c "C:\\windows\\system32\\mspatcha.dll")
ret=010036a5
002a:Call PE DLL (proc=0x7cefc320,module=0x7cef
L"mspatcha.dll",reason=PROCESS_ATTACH,res=(nil))
002a:trace:mspatcha:DllMain (0x0x7cef, 1, (nil))
002a:Call KERNEL32.DisableThreadLibraryCalls(7cef) ret=7cefa489
002a:Ret KERNEL32.DisableThreadLibraryCalls() retval=0001 ret=7cefa489
002a:Ret PE DLL (proc=0x7cefc320,module=0x7cef
L"mspatcha.dll",reason=PROCESS_ATTACH,res=(nil)) retval=1
002a:Ret KERNEL32.LoadLibraryA() retval=7cef ret=010036a5
002a:Call KERNEL32.GetProcAddress(7cef,0100238c "GetFilePatchSignatureA")
ret=010036bc
002a:Ret KERNEL32.GetProcAddress() retval=7cef8188 ret=010036bc
002a:Call KERNEL32.GetProcAddress(7cef,01002378 "ApplyPatchToFileA")
ret=010036ce
002a:Ret KERNEL32.GetProcAddress() retval=7cef80ac ret=010036ce
002a:Call mspatcha.ApplyPatchToFileA(0034faa4
"c:\\ef244e8344c867a4618ba071ad7a67b6\\_sfx_._p",0034fba8
"c:\\ef244e8344c867a4618ba071ad7a67b6\\Setup\\Program Files\\Microsoft SQL
Server\\x86\\Install\\sqlagent90_msdb_upgrade.sql",0034fcac
"c:\\ef244e8344c867a4618ba071ad7a67b6\\Setup\\Program Files\\Microsoft SQL
Server\\x86\\Install\\instmsdb.sql",) ret=0100483a
...
002a:trace:mspatcha:read_header patched file size will be 1139896
002a:trace:mspatcha:read_header patch supports 1 old file(s)
...
002a:trace:mspatcha:read_header found 0 range(s) to ignore
002a:trace:mspatcha:read_header found 0 range(s) to retain
...
002a:trace:mspatcha:decode_lzxd_stream decoding stream of size 290 to size
1139896, starting at 1221164
...
002a:trace:mspatcha:decode_lzxd_stream setting window to 0x40
...
002a:Ret mspatcha.ApplyPatchToFileA() retval=0001 ret=0100483a
...
002b:Call winex11.drv.SetWindowText(0001007a,0019ff20 L"Setup\\Program
Files\\Microsoft SQL Server\\x86\\Data\\msdbdata.mdf") ret=7e6e6ee9
002b:Ret winex11.drv.SetWindowText() retval= ret=7e6e6ee9
...
002a:Call mspatcha.ApplyPatchToFileA(0034faa4
"c:\\ef244e8344c867a4618ba071ad7a67b6\\_sfx_0001._p",0034fba8
"c:\\ef244e8344c867a4618ba071ad7a67b6\\Setup\\Program Files\\Microsoft SQL
Server\\x86\\Install\\instmsdb.sql",0034fcac
"c:\\ef244e8344c867a4618ba071ad7a67b6\\Setup\\Program Files\\Microsoft SQL
Server\\x86\\Data\\msdbdata.mdf",) ret=0100483a
...
002a:trace:mspatcha:read_header patched file size will be 4653056
002a:trace:mspatcha:read_header patch supports 1 old file(s)
...
002a:trace:mspatcha:read_header found 0 range(s) to ignore
002a:trace:mspatcha:read_header found 0 range(s) to retain
...
002a:trace:mspatcha:decode_lzxd_stream decoding stream of size 418322 to size
4653056, starting at 1139896
...
002a:trace:mspatcha:decode_lzxd_stream setting window to 0x80
...
002a:Ret mspatcha.ApplyPatchToFileA() retval=0001 ret=0100483a
...
--- snip ---
--- snip ---
...
002b:Call winex11.drv.SetWindowText(0001007a,001a0108 L"Setup\\Program
Files\\Microsoft SQL Server\\x86\\Binn\\res\\1033\\XPStar90.RLL") ret=7e6e6ee9
002b:Ret winex11.drv.SetWindowText() retval= ret=7e6e6ee9
...
002a:trace:mspatcha:read_header skipping rebase field
002a:trace:mspatcha:read_header patched file size will be 8491603
002a:trace:mspatcha:read_header patch supports 28 old file(s)
...
002a:trace:mspatcha:read_header found 2 range(s) to ignore
...
002a:Call KERNEL32.DeleteFileW(001a0660
L"c:\\ef244e8344c867a4618ba071ad7a67b6\\Setup\\Program Files\\Microsoft SQL
Server\\x86\\Binn\\res\\1033\\XPStar90.RLL") ret=7cefc2ef
002a:Ret KERNEL32.DeleteFileW() retval=0001 ret=7cefc2ef
...
[Bug 1766765] Re: xflock4 fails if light-locker installed in /usr/local/bin
** Changed in: xfce4-session Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1766765 Title: xflock4 fails if light-locker installed in /usr/local/bin To manage notifications about this bug go to: https://bugs.launchpad.net/xfce4-session/+bug/1766765/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1828634] [NEW] update-notifier runs too often on a Ubuntu
Public bug reported: Hello. update-notifier runs too often on a Ubuntu. According to sources (update-notifier.c) utility check updates every 10 minutes: // the timeout (in sec) when a further activity from dpkg/apt // causes the applet to "ungray" #define TIMEOUT_APT_RUN 600 /* 600 sec */ As result, this utility writes about 2 gigabytes on disk per day (https://imgur.com/4jzbONU). This is to much for me. I want to save SSD resources. I want to decrease update check interval up to ~2h. It is will be OK for me. Could you please make check interval configurable? 'Every 10 min' should be by default, but users should be able to change this interval via config files or GUI. What do you think? Thank you! ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: update-notifier 3.192.18 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat May 11 01:01:43 2019 InstallationDate: Installed on 2018-05-02 (373 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: update-notifier UpgradeStatus: Upgraded to disco on 2019-04-18 (22 days ago) ** Affects: update-notifier (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1828634 Title: update-notifier runs too often on a Ubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-notifier/+bug/1828634/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1752091] Re: gvfsd-metadata[1703]: g_udev_device_has_property: assertion 'G_UDEV_IS_DEVICE (device)' failed
same problem here. don't know where this is coming from but it maybe related to this: https://gitlab.gnome.org/GNOME/gvfs/commit/d7e1397854f32e793b4f65d894908d67072dcb3f my system (inxi -Fxz): System:Host: Work Kernel: 4.15.0-48-generic x86_64 bits: 64 gcc: 7.3.0 Desktop: Xfce 4.12.3 (Gtk 2.24.31) Distro: Ubuntu 18.04.2 LTS Machine: Device: desktop Mobo: ASRock model: B450M Pro4 serial: UEFI [Legacy]: American Megatrends v: P1.10 date: 06/19/2018 CPU: Quad core AMD Ryzen 5 2400G with Radeon Vega Graphics (-MT-MCP-) arch: Zen rev.0 cache: 2048 KB flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm) bmips: 28746 clock speeds: max: 3600 MHz 1: 2156 MHz 2: 2065 MHz 3: 1736 MHz 4: 1732 MHz 5: 1970 MHz 6: 2145 MHz 7: 3763 MHz 8: 3765 MHz Graphics: Card: Advanced Micro Devices [AMD/ATI] Raven Ridge [Radeon Vega Series / Radeon Vega Mobile Series] bus-ID: 38:00.0 Display Server: X.Org 1.19.6 drivers: ati,amdgpu (unloaded: modesetting,fbdev,vesa,radeon) Resolution: 1920x1080@59.93hz OpenGL: renderer: AMD RAVEN (DRM 3.23.0, 4.15.0-48-generic, LLVM 7.0.0) version: 4.5 Mesa 18.2.8 Direct Render: Yes Audio: Card-1 Advanced Micro Devices [AMD] Device 15e3 driver: snd_hda_intel bus-ID: 38:00.6 Card-2 Advanced Micro Devices [AMD/ATI] Device 15de driver: snd_hda_intel bus-ID: 38:00.1 Sound: Advanced Linux Sound Architecture v: k4.15.0-48-generic Network: Card: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller driver: r8169 v: 2.3LK-NAPI port: f000 bus-ID: 1f:00.0 IF: enp31s0 state: up speed: 1000 Mbps duplex: full mac: Drives:HDD Total Size: 1000.2GB (20.7% used) ID-1: /dev/nvme0n1 model: Samsung_SSD_970_EVO_500GB size: 500.1GB ID-2: /dev/sda model: WDC_WD5000AAKS size: 500.1GB temp: 43C Partition: ID-1: / size: 458G used: 72G (16%) fs: ext4 dev: /dev/nvme0n1p1 RAID: No RAID devices: /proc/mdstat, md_mod kernel module present Sensors: System Temperatures: cpu: 57.5C mobo: N/A gpu: 0.0 Fan Speeds (in rpm): cpu: N/A Info: Processes: 384 Uptime: 15 days Memory: 12261.7/15025.5MB Init: systemd runlevel: 5 Gcc sys: 7.4.0 Client: Shell (sudo) inxi: 2.3.56 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1752091 Title: gvfsd-metadata[1703]: g_udev_device_has_property: assertion 'G_UDEV_IS_DEVICE (device)' failed To manage notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/1752091/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1827788] Re: Add #ubuntu as 'get more help' resource in the docs
I have committed a tiny "Community support" page, which I think can be considered to address this bug: https://bazaar.launchpad.net/~ubuntu-core-doc/ubuntu- docs/trunk/revision/72/ubuntu-help/C/community-support.page The page will be added to the "Get more help" section of the desktop guide. ** Changed in: ubuntu-docs (Ubuntu) Status: Confirmed => Fix Committed ** Changed in: ubuntu-docs (Ubuntu) Assignee: (unassigned) => Gunnar Hjalmarsson (gunnarhj) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1827788 Title: Add #ubuntu as 'get more help' resource in the docs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-docs/+bug/1827788/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1828642] [NEW] /usr/bin/nautilus:11:nautilus_list_model_get_all_iters_for_file:nautilus_list_model_get_first_iter_for_file:nautilus_list_view_scroll_to_file:list_view_scroll_to_file:view_ended_lo
Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding nautilus. This problem was most recently seen with package version 1:3.26.4-0ubuntu7.2, the problem page at https://errors.ubuntu.com/problem/b602a0d844bdf5a495f5843d042e2f2b9dbb58d0 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: artful bionic cosmic kylin-17.10 xenial yakkety zesty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1828642 Title: /usr/bin/nautilus:11:nautilus_list_model_get_all_iters_for_file:nautilus_list_model_get_first_iter_for_file:nautilus_list_view_scroll_to_file:list_view_scroll_to_file:view_ended_loading To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1828642/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1828597] Re: KDump boot fails with nr_cpus=1
** Changed in: ubuntu-power-systems 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/1828597 Title: KDump boot fails with nr_cpus=1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1828597/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1823836] Re: dpdk app is reporting: net_mlx5: probe of PCI device xxxx aborted after encountering an error: Unknown error -95
** Tags removed: verification-needed verification-needed-disco ** Tags added: verification-done verification-done-disco -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1823836 Title: dpdk app is reporting: net_mlx5: probe of PCI device aborted after encountering an error: Unknown error -95 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1823836/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1828553] Re: Unable to boot Bionic 5.0 linux-hwe-edge kernel on ARM64 Moonshot node
I confirmed that if we compress the kernel (as Seth's patch does), the 5.0 kernel would boot fine on the HP m400[*]. I chatted w/ apw about this and we agreed that a respin isn't necessary because LP showed that there is no current linux-hwe-edge package in bionic, and therefore introducing one should not be a regression. ***But*** I now see that I gave him bad information. What I failed to recognize is that the linux-*meta*-hwe-edge package is already in bionic-updates - it just depends on binaries from the linux-hwe package at the moment. So, there could very well be users with the linux-image-generic-18.04-hwe-edge installed today (which currently depends on 4.18) that would get a broken update if they were to dist-upgrade to the new version that depends on the 5.0 kernel. To be clear - the fix here is a respin of the linux-signed-hwe- edge/bionic package with the patch referenced in comment #3. This does not require a rebuild/recompile of the kernel, just a rebuild of the package that ingests pre-compiled/signed binaries. This would impact all signed architectures (x86, power & arm64). But, other than arm64's vmlinuz now being gzip'd, the resulting binaries landed should be verifiably bit-identical. [*] At least some of our cartridges. We have one at least one that is impacted by bug 1823753 as well, so it'll still be broken until the next SRU cycle. It is unclear what the difference is between these cartridges (silicon rev? fw?) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1828553 Title: Unable to boot Bionic 5.0 linux-hwe-edge kernel on ARM64 Moonshot node To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1828553/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1828592] Re: Duplicate entry Exec and Path in scripts.
Removed symbolic links: /usr/share/pykaraoke/fonts/DejaVuSans.ttf /usr/share/pykaraoke/fonts/DejaVuSansCondensed.ttf /usr/share/pykaraoke/fonts/DejaVuSansCondensed-Bold.ttf Copyed instead fonts in /usr/share/pykaraoke/fonts/ Works fine. ** Package changed: linux (Ubuntu) => pykaraoke (Ubuntu) ** Summary changed: - Duplicate entry Exec and Path in scripts. + pykaraoke wont read fonts ** Changed in: pykaraoke (Ubuntu) Status: Incomplete => Fix Committed ** Changed in: pykaraoke (Ubuntu) Status: Fix Committed => Opinion ** Changed in: pykaraoke (Ubuntu) Assignee: (unassigned) => J.G. (j.gorski) ** Summary changed: - pykaraoke wont read fonts + pykaraoke won't read fonts -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1828592 Title: pykaraoke won't read fonts To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pykaraoke/+bug/1828592/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1606741] Re: [SRU] Metadata service for instances is unavailable when the l3-agent on the compute host is dvr_snat mode
A patched version of the ubuntu neutron package has been uploaded to the cosmic unapproved queue [1] where it is awaiting SRU team review. [1] https://launchpad.net/ubuntu/cosmic/+queue?queue_state=1_text=neutron -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1606741 Title: [SRU] Metadata service for instances is unavailable when the l3-agent on the compute host is dvr_snat mode To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1606741/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1826045] Re: Unsatisfiable recommended dependencies pacemaker >= 2.0, corosync >= 3.0
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: pcs (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/1826045 Title: Unsatisfiable recommended dependencies pacemaker >= 2.0, corosync >= 3.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pcs/+bug/1826045/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1828118] Re: docker tarballs contain /dev/null
Well ok but those are currently deleted downstream anyway by https://github.com/tianon/docker-brew-ubuntu-core/blob/master/update.sh#L91. Do you want to submit a patch there and then we can patch it here too? In the mean time I still would like to release this change. On Fri, 10 May 2019, 19:30 Julian Andres Klode, wrote: > Namely partial/ is an _apt owned sandbox arena. I think there is some > code to restore a missing one and fixup permissions but that's super > ugly. > > The correct change to make for cleaning apt would be to run apt-get > clean with -o dir::etc::sourcelist=/dev/null, same with sourceparts. > > That will take care of cleaning everything up that should be cleaned up > and stop messing with internals. > > -- > You received this bug notification because you are a member of Canonical > Cloudware, which is subscribed to livecd-rootfs in Ubuntu. > https://bugs.launchpad.net/bugs/1828118 > > Title: > docker tarballs contain /dev/null > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1828118/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1828118 Title: docker tarballs contain /dev/null To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1828118/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1828259] Fix merged to charm-nova-compute (stable/19.04)
Reviewed: https://review.opendev.org/658404 Committed: https://git.openstack.org/cgit/openstack/charm-nova-compute/commit/?id=d33fa57b40994483cf88f338a4d000e06aaf6cc5 Submitter: Zuul Branch:stable/19.04 commit d33fa57b40994483cf88f338a4d000e06aaf6cc5 Author: Corey Bryant Date: Thu May 9 08:13:51 2019 -0400 py3: deal with more subordinate dependencies Ensure subordinate py3 packages are installed if their py2 counter-parts are currently installed for neutron-openvswitch. In this case we had missed python(3)-neutron-fwaas. Change-Id: I9d5e7c2ad034cd7bdf9cbf292b9107577860dac1 Closes-Bug: #1828259 (cherry picked from commit 96b5e8a2493305ec7667c153d070dffda1bf547b) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1828259 Title: [rocky][19.04] Upgrading a deployment from Queens to Rocky resulted in purging of neutron-l3-agent package To manage notifications about this bug go to: https://bugs.launchpad.net/charm-neutron-openvswitch/+bug/1828259/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1826628] Re: Lubuntu fails to install when disk/RAM sizes equal minimum requirements
** Changed in: calamares 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/1826628 Title: Lubuntu fails to install when disk/RAM sizes equal minimum requirements To manage notifications about this bug go to: https://bugs.launchpad.net/calamares/+bug/1826628/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1828259] Re: [rocky][19.04] Upgrading a deployment from Queens to Rocky resulted in purging of neutron-l3-agent package
** Changed in: charm-nova-compute Milestone: None => 19.04 ** Changed in: charm-nova-compute 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/1828259 Title: [rocky][19.04] Upgrading a deployment from Queens to Rocky resulted in purging of neutron-l3-agent package To manage notifications about this bug go to: https://bugs.launchpad.net/charm-neutron-openvswitch/+bug/1828259/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1828632] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1828632 Title: bionic i386 kernel crashes in memory pressure situations To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1828632/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1827416] Re: Removal Request: Demote from main
This is now processed, and heartbeat is showing as a universe package: heartbeat | 1:3.0.6-9| disco | source, amd64, arm64, armhf, i386, ppc64el, s390x heartbeat | 1:3.0.6-9ubuntu1 | eoan/universe | source, amd64, arm64, armhf, i386, ppc64el, s390x Also confirmed showing in universe at: https://launchpad.net/ubuntu/+source/heartbeat ** Changed in: heartbeat (Ubuntu) Status: New => Fix Released ** Changed in: heartbeat (Ubuntu) Assignee: (unassigned) => Bryce Harrington (bryce) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1827416 Title: Removal Request: Demote from main To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/heartbeat/+bug/1827416/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1811824] Re: [MIR] xdg-dbus-proxy
It seems the security team was no longer assigned, but we knew this was coming so I performed the security team MIR. I reviewed xdg-dbus-proxy 0.1.1-1 as checked into eoan. This shouldn't be considered a full audit but rather a quick gauge of maintainability. xdg-dbus-proxy is a "filtering proxy for D-Bus connections". It is invoked via the command line line with arguments that specify the address to proxy and the path for client connections. It will listen on a unix domain socket for clients to connect. For each client connection, it opens a new connection to the proxied address, forwarding data between the two. xdg-dbus-proxy operates in two modes, filtered and unfiltered (ie, forward all messages). With filtering mode, policy is applied to determine which messages to allow and drop. Filtering is applied to signals and method calls from the client and broadcast signals from the proxied address. Replies (errors and method returns) are allowed for the outstanding call, but not otherwise (this is analogous to how dbus-daemon works with LSM policy like AppArmor). Policy is simple, yet flexible and aggregates various common DBus APIs into SEE, TALK and OWN policy levels (listed from lowest to highest, with each higher level implying lower levels) that are specified in rules for use with well-known DBus names (ie, *not* private/unique names). The default policy allows TALKing to the bus itself (org.freedesktop.DBus) and to its own unique ID. Other clients are invisible (this is not unlike the dbus-strict and dbus-session-strict AppArmor abstractions). Policy rules allow a glob syntax for suffixes such that org.foo.* matches org.foo, org.foo.bar, org.foo.bar.baz but not org.norf. While the rule is specified for the well-known name, the rule will also apply such that the policy for the private/unique DBus name of the client is the union of all rules for well-known names that the client owns. where the highest level wins. In addition to these policy levels, it is possible to also specify interface and object paths with method calls/signals on well-known names (similar to fine-grained AppArmor rules). xdg-dbus-proxy is a lowlevel application intended to be driven by a higher level application (eg, bubblewrap, flatpak (which drives bubblewrap, etc). It does not support policy files and typical usage is to proxy, for example, the session bus for an application, with all rules specified on the command line (bwrap typically uses the --args option, which allows passing nul-separated arguments via a file descriptor). Eg (showing full args instead of the normal --args usage): $ xdg-dbus-proxy --fd=26 unix:path=/run/usr/1000/bus /run/usr/1000/.dbus-proxy/session-bus-proxy --filter --own=org.gnome.ghex.* --talk=ca.desrt.dconf --call=org.freedesktop.portal.*=* such that different applications will each have their own proxy. bwrap usage shows sockets in /run/user//.dbus-proxy/session-bus-proxy-* where there is a named socket allocated for each application that corresponds to to the (now deleted) --args fd. xdg-dbus-proxy does support proxying the system bus (eg, xdg-dbus-proxy unix:path=/run/dbus/system_bus_socket /tmp/foo). Additionally, with typical bwrap usage, xdg-dbus-proxy isn't going to be invoked as root as it is intended for use in user sessions. This architecture also seems reasonable. The rules language, syntax and xdg-dbus-proxy invocation looks fine from a design POV. Due to time constraints, I did not review the implementation for enforcement correctness. I did some blackbox testing like so: $ sudo apt-get install flatpak gnome-software-plugin-flatpak d-feet $ flatpak remote-add --if-not-exists flathub https://flathub.org/repo/flathub.flatpakrepo $ flatpak install flathub org.gnome.ghex $ flatpak install flathub org.gnome.Logs $ flatpak install flathub org.wireshark.Wireshark $ flatpak run org.gnome.ghex & $ flatpak run org.gnome.Logs & $ flatpak run org.wireshark.Wireshark & $ xdg-dbus-proxy unix:path=/run/dbus/system_bus_socket /tmp/test-system & # unfiltered $ xdg-dbus-proxy unix:path=/run/dbus/system_bus_socket /tmp/test-session & # unfiltered $ d-feet # 'Connect to other bus', choose unix:path=/tmp/test-system and see system bus $ d-feet # 'Connect to other bus', choose unix:path=/tmp/test-session and see session bus $ ls -l /run/user/1000/.dbus-proxy/ total 0 srwxr-xr-x 1 jamie jamie 0 May 10 17:32 a11y-bus-proxy-A5PT1Z srwxr-xr-x 1 jamie jamie 0 May 10 16:35 a11y-bus-proxy-ORKL1Z srwxr-xr-x 1 jamie jamie 0 May 10 16:36 a11y-bus-proxy-PZFD1Z srwxr-xr-x 1 jamie jamie 0 May 10 16:35 session-bus-proxy-9IQL1Z srwxr-xr-x 1 jamie jamie 0 May 10 16:36 session-bus-proxy-EZ9C1Z srwxr-xr-x 1 jamie jamie 0 May 10 17:32 session-bus-proxy-KHRT1Z (interesting that these all end with '1Z', but this would be in bwrap) $ d-feet # 'Connect to other bus', choose unix:path=/run/user/1000 /.dbus-proxy/session-bus-proxy-9IQL1Z In this last example, we see only what ghex is allowed (verified by
[Bug 1828639] [NEW] package libvlc-bin 3.0.6-1 failed to install/upgrade: 90.8592:triggers looping, abandoned
Public bug reported: Encountered when upgrading from cosmic to disco with ubuntu-mate-desktop installed. ProblemType: Package DistroRelease: Ubuntu 19.04 Package: libvlc-bin 3.0.6-1 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 Date: Fri May 10 22:48:10 2019 ErrorMessage: 90.8592:triggers looping, abandoned Python3Details: /usr/bin/python3.7, Python 3.7.3, python3-minimal, 3.7.3-1 PythonDetails: /usr/bin/python2.7, Python 2.7.16, python-minimal, 2.7.16-1 SourcePackage: vlc Title: package libvlc-bin 3.0.6-1 failed to install/upgrade: 90.8592:triggers looping, abandoned UpgradeStatus: Upgraded to disco on 2019-05-10 (0 days ago) ** Affects: vlc (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package dist-upgrade need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1828639 Title: package libvlc-bin 3.0.6-1 failed to install/upgrade: 90.8592:triggers looping, abandoned To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vlc/+bug/1828639/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1828638] [NEW] Support sane option --scan-area on GUI applications
Public bug reported: Several sane backends provide the option --scan-area to guarantee the scan is correctly aligned, even if the scan area with automatic document feeder (ADF) is right-aligned in contrast to the flatbed of the same device, which is normally left-aligned. Currently SimpleScan and XSane only support options -l -t -x -y, which leads to misalignment of some scanners when using the ADF. As example for this problem see: https://gitlab.com/utsushi/utsushi/issues/68 ** Affects: simple-scan Importance: Undecided Status: New ** Affects: simple-scan (Ubuntu) Importance: Undecided Status: New ** Affects: xsane (Ubuntu) Importance: Undecided Status: New ** Also affects: simple-scan (Ubuntu) Importance: Undecided Status: New ** Summary changed: - Support option --scan-area + Support sane option --scan-area on GUI applications ** Also affects: simple-scan Importance: Undecided Status: New ** Description changed: Several sane backends provide the option --scan-area to guarantee the scan is correctly aligned, even if the scan area with automatic document feeder (ADF) is right-aligned in contrast to the flatbed of the same - device is normally left-aligned. + device, which is normally left-aligned. Currently SimpleScan and XSane only support options -l -t -x -y, which leads to misalignment of some scanners when using the ADF. As example for this problem see: https://gitlab.com/utsushi/utsushi/issues/68 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1828638 Title: Support sane option --scan-area on GUI applications To manage notifications about this bug go to: https://bugs.launchpad.net/simple-scan/+bug/1828638/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1788098] Comment bridged from LTC Bugzilla
--- Comment From leona...@ibm.com 2019-05-10 19:54 EDT--- Hello Juerg, As this complete list was suggested by Paul, I think he may be the best person to show the context of the patch series. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1788098 Title: Avoid migration issues with aligned 2MB THB To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1788098/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1785715] Re: ubuntu hynix ssd I/O Errors after some minutes
Sorry, i forgot to report back. Thank you for asking. No, i got my SSD replaced by a new one and now it is all good. Seems like it has been a hardware-related problem. Am 10.05.2019 um 17:26 schrieb Kai-Heng Feng: > Do you still see this bug? > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1785715 Title: ubuntu hynix ssd I/O Errors after some minutes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1785715/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1796193] Re: DistUpgradeViewNonInteractive crashes / requires interaction
On Fri, May 10, 2019 at 08:13:47PM -, Paul Larson wrote: > For the xenial->bionic question, I had already implemented the > workaround mentioned here to use Dpkg::Options::="--force-confdef" > across all upgrade tests, which has been working fine. I can remove the > workaround and try it if you are specifically interested in finding out > whether it's necessary on the upgrade to bionic though. Yes, the foundations team is interested. If there is a package creating a conffile prompt during a release upgrade we'd like to know what package it is and why. -- Brian Murray -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1796193 Title: DistUpgradeViewNonInteractive crashes / requires interaction To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1796193/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1827441] Re: ubuntu-release-upgrader crashed with configparser.NoOptionError: No option 'devrelease' in section: 'Options'
** Branch linked: lp:ubuntu-release-upgrader -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1827441 Title: ubuntu-release-upgrader crashed with configparser.NoOptionError: No option 'devrelease' in section: 'Options' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1827441/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1828358] Re: 175% fractional scaling on X11 results in often unaccessible desktop after suspend / re-login
** Attachment added: "(adding attachments to illustrate)" https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1828358/+attachment/5262991/+files/VID_20190509_224648.mp4 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1828358 Title: 175% fractional scaling on X11 results in often unaccessible desktop after suspend / re-login To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1828358/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1828606] Re: Ubuntu 18.04 "Files" app unable to show Samba/SMB shares where 'access based share enumeration = yes'
Thank you for your bug report, the issue looks like an upsream one though, maybe you could report it to them on https://gitlab.gnome.org/GNOME/gvfs/issues ? ** Package changed: nautilus (Ubuntu) => gvfs (Ubuntu) ** Changed in: gvfs (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1828606 Title: Ubuntu 18.04 "Files" app unable to show Samba/SMB shares where 'access based share enumeration = yes' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1828606/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1828358] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1828358/+attachment/5262987/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1828358 Title: 175% fractional scaling on X11 results in often unaccessible desktop after suspend / re-login To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1828358/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1828358] Re: 175% fractional scaling on X11 results in often unaccessible desktop after suspend / re-login
apport information ** Tags added: apport-collected ** Description changed: Having enabled fractional scaling on X11, I have a lot of issues with returning to a hw-suspended session, re-login screen becomes a black rectangle, and windows are being resized and there are black rectangular artifacts and a lot of weird stuff with resizing going on. Sometimes I am able to reach the login screen, but often I have to killall -HUP gnome-shell from the terminal. I will try to attach X logs etc when this happens again. Which are the most relevant log files to look into? Ubuntu 19.04, gnome-shell 3.32.0, mutter 3.32.0+git20190410-1ubuntu1, NVIDIA 418.56 Screen at 3840x2160 and 175% scaling + --- + ProblemType: Bug + ApportVersion: 2.20.10-0ubuntu27 + Architecture: amd64 + CurrentDesktop: ubuntu:GNOME + DistroRelease: Ubuntu 19.04 + InstallationDate: Installed on 2018-07-04 (310 days ago) + InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) + NonfreeKernelModules: nvidia_modeset nvidia + Package: mutter 3.32.0+git20190410-1ubuntu1 + PackageArchitecture: amd64 + ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 + Tags: disco + Uname: Linux 5.0.0-13-generic x86_64 + UpgradeStatus: Upgraded to disco on 2019-04-17 (23 days ago) + UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo + _MarkForUpload: True + mtime.conffile..etc.apport.crashdb.conf: 2018-07-13T14:12:17.455274 ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1828358/+attachment/5262985/+files/Dependencies.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1828358 Title: 175% fractional scaling on X11 results in often unaccessible desktop after suspend / re-login To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1828358/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1828358] Re: 175% fractional scaling on X11 results in often unaccessible desktop after suspend / re-login
** Attachment added: "(adding attachments to illustrate)" https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1828358/+attachment/5262989/+files/MVIMG_20190509_110046.jpg -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1828358 Title: 175% fractional scaling on X11 results in often unaccessible desktop after suspend / re-login To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1828358/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1828358] Re: 175% fractional scaling on X11 results in often unaccessible desktop after suspend / re-login
** Attachment added: "(adding attachments to illustrate)" https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1828358/+attachment/5262990/+files/MVIMG_20190510_225124.jpg -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1828358 Title: 175% fractional scaling on X11 results in often unaccessible desktop after suspend / re-login To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1828358/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1828358] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1828358/+attachment/5262986/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1828358 Title: 175% fractional scaling on X11 results in often unaccessible desktop after suspend / re-login To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1828358/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1828358] modified.conffile..etc.apport.crashdb.conf.txt
apport information ** Attachment added: "modified.conffile..etc.apport.crashdb.conf.txt" https://bugs.launchpad.net/bugs/1828358/+attachment/5262988/+files/modified.conffile..etc.apport.crashdb.conf.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1828358 Title: 175% fractional scaling on X11 results in often unaccessible desktop after suspend / re-login To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1828358/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1828136] Re: [Intel DH67CL, Realtek ALC892, Grey SPDIF Out, Rear] No sound at all
The before file was attached to the last comment. Here's the after file from pactl. ** Attachment added: "postforce" https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1828136/+attachment/5263010/+files/postforce -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1828136 Title: [Intel DH67CL, Realtek ALC892, Grey SPDIF Out, Rear] No sound at all To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1828136/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1796193] Re: DistUpgradeViewNonInteractive crashes / requires interaction
** Branch linked: lp:~ubuntu-core-dev/ubuntu/disco/ubuntu-release- upgrader/disco -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1796193 Title: DistUpgradeViewNonInteractive crashes / requires interaction To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1796193/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1828516] Re: avahi-daemon seems unable to advertise _uscan._tcp??
Trent, Thanks that does work. Now on to seeing how to addd the txt attributes for scanner features and such, hopefully this too is attainable. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1828516 Title: avahi-daemon seems unable to advertise _uscan._tcp?? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1828516/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1828578] Re: dell xps 9570 wifi reconnection issue followed by freeze + Ubuntu 18.04.2 LTS
Does this kernel supports Killer 1435, 1435s and 1535 wireless cards ? >> linux-image-generic-hwe-18.04 = 4.18.0.17.67 Or support for this wifi cards available in 5.x kernel, please specify. Note:- As per killer networking, they haven't mentioned about 18.04 https://support.killernetworking.com/knowledge-base/installing-the-killer-1535-1525-1435-in-ubuntu-debian/ Please confirm which linux-firmware supports this driver? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1828578 Title: dell xps 9570 wifi reconnection issue followed by freeze + Ubuntu 18.04.2 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1828578/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1828578] Re: dell xps 9570 wifi reconnection issue followed by freeze + Ubuntu 18.04.2 LTS
Does any of the linux-firmware supports these killer wifi driver ? http://mirrors.edge.kernel.org/ubuntu/pool/main/l/linux-firmware/ Issue:- Intermittently reconnection / sometime freezing issue. Mostly seeing this in home network. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1828578 Title: dell xps 9570 wifi reconnection issue followed by freeze + Ubuntu 18.04.2 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1828578/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1828615] Re: v4l2loopback 10.0-1ubuntu1 ADT test failure with linux 5.0.0-14-generic
.debdiff attached to this comment. To fix this, I've backported this patch: https://github.com/umlaeute/v4l2loopback/commit/afe0b233070d7ca5d6df83c5f2723d276dcd287d.patch No context adjustments were required. [ Testing ] I tested this install process for both 4.15.0-49-generic and 5.0.0-14-generic to test for regressions since the changes introduced by this patch are not conditionally compiled. - Create a Bionic 18.04 VM - Install the Bionic Linux HWE Edge kernel from -proposed or install the built .debs located here: https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/ppa/+packages?field.name_filter=linux-hwe-edge_filter=published_filter=bionic - Try installing v4l2loopback-dkms with apt (or you can pull the sources with "pull-lp-source v4l2loopback bionic" and build with "debuild -b -uc -us" - Confirm that installation fails for the 5.0 kernel (it will succeed for 4.15) - Pull the sources with "pull-lp-source v4l2loopback bionic" - Apply the debdiff "debdiff-apply < path-to-diff-in-this-comment.debdiff" - Build the package "debuild -b -uc -us" - Install the .deb produced from the previous step "sudo dpkg --install path-to-deb.deb" - Verify the installation completed successfully. You can also verify the output of "sudo dkms status" is correct. ** Patch added: "v4l2loopback_0.10.0-1ubuntu1.1.debdiff" https://bugs.launchpad.net/ubuntu/+source/v4l2loopback/+bug/1828615/+attachment/5262980/+files/v4l2loopback_0.10.0-1ubuntu1.1.debdiff ** Changed in: v4l2loopback (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1828615 Title: v4l2loopback 10.0-1ubuntu1 ADT test failure with linux 5.0.0-14-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/v4l2loopback/+bug/1828615/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1828617] [NEW] Hosts randomly 'losing' disks, breaking ceph-osd service enumeration
Public bug reported: Ubuntu 18.04.2 Ceph deployment. Ceph OSD devices utilizing LVM volumes pointing to udev-based physical devices. LVM module is supposed to create PVs from devices using the links in /dev/disk/by-dname/ folder that are created by udev. However on reboot it happens (not always, rather like race condition) that Ceph services cannot start, and pvdisplay doesn't show any volumes created. The folder /dev/disk/by-dname/ however has all necessary device created by the end of boot process. The behaviour can be fixed manually by running "#/sbin/lvm pvscan --cache --activate ay /dev/nvme0n1" command for re-activating the LVM components and then the services can be started. ** Affects: systemd (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/1828617 Title: Hosts randomly 'losing' disks, breaking ceph-osd service enumeration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1828617/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1827441] Re: ubuntu-release-upgrader crashed with configparser.NoOptionError: No option 'devrelease' in section: 'Options'
This bug was fixed in the package ubuntu-release-upgrader - 1:19.10.5 --- ubuntu-release-upgrader (1:19.10.5) eoan; urgency=medium * DistUpgrade/DistUpgradeViewNonInteractive.py: when responding to a conffile prompt with "n" use bytes not a string. (LP: #1796193) * DistUpgrade/DistUpgradeController.py: set a default value for devRelease even if there are no options specified. (LP: #1827441) -- Brian Murray Fri, 10 May 2019 13:30:07 -0700 ** Changed in: ubuntu-release-upgrader (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/1827441 Title: ubuntu-release-upgrader crashed with configparser.NoOptionError: No option 'devrelease' in section: 'Options' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1827441/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1828632] Re: bionic i386 kernel crashes in memory pressure situations
In discussing this with Tyler Hicks, he noted that is a somewhat similar i386 PTI failure report: https://lore.kernel.org/lkml/14206a19d597881b2490eb3fea47ee97be17ca93.ca...@sympatico.ca/ and that the response to it needs fixes from the tip/x86/mm branch. Is it possible that the bionic PTI i386 backports are missing some additional fixes? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1828632 Title: bionic i386 kernel crashes in memory pressure situations To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1828632/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1813063] Re: ndiswrapper 1.60-6 ADT test failure with linux 5.0.0-1.2
** Description changed:
+ NOTE: This SRU template was added 2019-05-10 after the original report
+ was opened and was fixed for Disco. I'm adding this because this problem
+ is affecting the Bionic HWE Edge kernel this SRU cycle. -connork
+
+ [Impact]
+
+ * The DKMS package fails to install on kernels based on 5.0;
+ specifically noticed in the Bionic HWE Edge kernel.
+
+ [The Problem]
+ This module uses the "do_gettimeofday" API which has been deprecated and
removed from the 5.0 kernels. As a result, on a 5.0 kernel, the module will not
compile successfully during installation since it depends on symbols that are
no longer there.
+
+ [Proposed Fix]
+ Backport the following patch which has already landed in Disco's version of
this package to support the 5.0 kernels:
https://salsa.debian.org/jak/ndiswrapper/commit/f4502d63e8731b20b436a1266e96c5416e02a3af
+
+ [Test Case]
+ * Install the ndiswrapper-dkms package with a 5.0 kernel. The package should
install without any errors.
+
+ [Testing]
+
+ - Create an Ubuntu 18.04 VM
+ - Install the HWE Edge kernel from -proposed (or one can find .debs here:
https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/ppa/+packages?field.name_filter=linux-hwe-edge_filter=published_filter=bionic)
+ - Install ndiswrapper; you can use apt ("sudo apt update" "sudo apt install
ndiswrapper-dkms") or you can use "pull-lp-source ndiswrapper bionic" to build
and install the .deb from that
+ - Confirm that installation fails
+ - Remove it "sudo apt remove ndiswrapper-dkms"
+ - If you haven't already: "pull-lp-source ndiswrapper bionic"
+ - Apply the debdiff ("debdiff-apply < ../ndiswrapper_1.60-6ubuntu0.1.debdiff")
+ - Build the package ("debuild -us -uc")
+ - Install the package
+ - Verify it installs successfully! ("sudo dkms status")
+
+ [Regression Potential]
+
+ * Low. Changes are conditionally compiled based on the kernel being >=
+ 5.0. These changes have also been in Disco.
+
+
Testing failed on:
- amd64:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-disco-canonical-kernel-team-unstable/disco/amd64/n/ndiswrapper/20190123_164111_540fe@/log.gz
- i386:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-disco-canonical-kernel-team-unstable/disco/i386/n/ndiswrapper/20190123_172043_540fe@/log.gz
+ amd64:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-disco-canonical-kernel-team-unstable/disco/amd64/n/ndiswrapper/20190123_164111_540fe@/log.gz
+ i386:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-disco-canonical-kernel-team-unstable/disco/i386/n/ndiswrapper/20190123_172043_540fe@/log.gz
** Description changed:
NOTE: This SRU template was added 2019-05-10 after the original report
was opened and was fixed for Disco. I'm adding this because this problem
is affecting the Bionic HWE Edge kernel this SRU cycle. -connork
[Impact]
- * The DKMS package fails to install on kernels based on 5.0;
+ * The DKMS package fails to install on kernels based on 5.0;
specifically noticed in the Bionic HWE Edge kernel.
[The Problem]
This module uses the "do_gettimeofday" API which has been deprecated and
removed from the 5.0 kernels. As a result, on a 5.0 kernel, the module will not
compile successfully during installation since it depends on symbols that are
no longer there.
[Proposed Fix]
Backport the following patch which has already landed in Disco's version of
this package to support the 5.0 kernels:
https://salsa.debian.org/jak/ndiswrapper/commit/f4502d63e8731b20b436a1266e96c5416e02a3af
[Test Case]
- * Install the ndiswrapper-dkms package with a 5.0 kernel. The package should
install without any errors.
+ * Install the ndiswrapper-dkms package with a 5.0 kernel. The package should
install without any errors.
[Testing]
+
+ These instructions were followed using the .debdiff in comment #5
- Create an Ubuntu 18.04 VM
- Install the HWE Edge kernel from -proposed (or one can find .debs here:
https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/ppa/+packages?field.name_filter=linux-hwe-edge_filter=published_filter=bionic)
- Install ndiswrapper; you can use apt ("sudo apt update" "sudo apt install
ndiswrapper-dkms") or you can use "pull-lp-source ndiswrapper bionic" to build
and install the .deb from that
- Confirm that installation fails
- Remove it "sudo apt remove ndiswrapper-dkms"
- If you haven't already: "pull-lp-source ndiswrapper bionic"
- Apply the debdiff ("debdiff-apply < ../ndiswrapper_1.60-6ubuntu0.1.debdiff")
- Build the package ("debuild -us -uc")
- Install the package
- Verify it installs successfully! ("sudo dkms status")
[Regression Potential]
- * Low. Changes are conditionally compiled based on the kernel being >=
+ * Low.
[Bug 1828639] Re: package libvlc-bin 3.0.6-1 failed to install/upgrade: 90.8592:triggers looping, abandoned
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1828639 Title: package libvlc-bin 3.0.6-1 failed to install/upgrade: 90.8592:triggers looping, abandoned To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vlc/+bug/1828639/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1828644] [NEW] /usr/bin/mc:11:display_mini_info:panel_callback:setup_panels:midnight_callback:send_message
Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding mc. This problem was most recently seen with package version 3:4.8.21-1, the problem page at https://errors.ubuntu.com/problem/e64af00a2e85e4cc01804ca4b41cea18270e4eab contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. ** Affects: mc (Ubuntu) Importance: Undecided Status: New ** Tags: artful bionic cosmic zesty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1828644 Title: /usr/bin/mc:11:display_mini_info:panel_callback:setup_panels:midnight_callback:send_message To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mc/+bug/1828644/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1828467] Re: [sru] remove juju-db stop/start service interactions
** Description changed: [Impact] The juju plugin will stop and start the juju-db service during data collection. sosreport should not impact running services, or attempt to recover them. This has been reported upstream[0] and will be fixed by the juju 2.x refactor[1] This is a stop-gap tracking the removal of the juju-db service restart code in existing sosreport releases. [0] - https://github.com/sosreport/sos/issues/1653 [1] - https://github.com/sosreport/sos/pull/1670 [Test Case] + * Make sure you are in the juju controller. * Install sosreport - * Look mongod PID before -** pidof mongod + * Look mongod PID before + ** $ pidof mongod * Run sosreport, ensuring that the juju plugin is exercised * Confirm the juju-db service was not restarted, and mongoexport data captured. * Look mongod PID after -** pidof mongod + ** $ pidof mongod + Check for errors while running, or in /tmp/sosreport-*/sos_logs/ - The offending function ensure_service_is_running() in theory doesn't create any harm unless juju plugin is exercised during a sosreport run from a juju controller where mongod and juju-db reside. - + The offending function ensure_service_is_running() in theory doesn't + create any harm unless juju plugin is exercised during a sosreport run + from a juju controller where mongod and/or juju-db resides. [Regression Potential] * Risk is low. * Change is limited in scope to the juju plugin. - * Worst-case scenario is that the mongoexport command will fail to collect - any data. + * Worst-case scenario is that the mongoexport command will fail to collect any data, which won't affect core functionality of sosreport itself nor impact other sosreport plugins. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1828467 Title: [sru] remove juju-db stop/start service interactions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sosreport/+bug/1828467/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1825206] Re: No wifi adapter present in Gnome after upgrade to 0.96-0ubuntu0.18.10.2
This is still verification-done; has not changed in releases: this SRU is a backport that includes the same upstream patch as what was previously cherry-picked in the previous round of SRUs; hence it appearing again in changelog. ** Tags removed: verification-needed verification-needed-bionic verification-needed-cosmic verification-needed-disco ** Tags added: verification-done-bionic verification-done-cosmic verification-done-disco -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1825206 Title: No wifi adapter present in Gnome after upgrade to 0.96-0ubuntu0.18.10.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/netcfg/+bug/1825206/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1823836] Re: dpdk app is reporting: net_mlx5: probe of PCI device xxxx aborted after encountering an error: Unknown error -95
tags adjusted - thx David -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1823836 Title: dpdk app is reporting: net_mlx5: probe of PCI device aborted after encountering an error: Unknown error -95 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1823836/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1826045] Re: Unsatisfiable recommended dependencies pacemaker >= 2.0, corosync >= 3.0
** Also affects: pcs (Ubuntu Disco) Importance: Undecided Status: New ** Changed in: pcs (Ubuntu Disco) Status: New => Confirmed ** Changed in: pcs (Ubuntu) Status: Confirmed => Fix Released ** Changed in: pcs (Ubuntu Disco) Importance: Undecided => High ** Changed in: pcs (Ubuntu Disco) Assignee: (unassigned) => Heitor Alves de Siqueira (halves) ** Tags added: sts -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1826045 Title: Unsatisfiable recommended dependencies pacemaker >= 2.0, corosync >= 3.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pcs/+bug/1826045/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1828609] Re: Cannot do updates, not even partial
Thanks Tom. I will check whether I have multiple Ubuntu releases on that computer and if so may submit a separate bug report as suggested. John Bell On 5/10/19 1:20 PM, Tom Reynolds wrote: > https://launchpadlibrarian.net/423140934/VarLogDistupgradeAptlog.txt > seems to suggest you have packages from multiple Ubuntu releases > installed. If this can be confirmed, then this is more of a support case > than a bug in the software. > > This said, more robust handling by the release upgrader (detecting this > situation - which is difficult to do -, and handling it, probably by > preventing a release upgrade to be initiated under these unsafe > conditions, and providing further suggestion) would be more than just > nice to have in general (and deserves its separate bug report). > > ** Changed in: ubuntu-release-upgrader (Ubuntu) > Status: New => Incomplete > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1828609 Title: Cannot do updates, not even partial To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1828609/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1322968] Re: Changing country leads to invalid locale
Unfortunately, this bug occurred to me again in Kubuntu 18.04 / KDE Plasma 5.12.7 when setting language to English and region to Netherlands. Locale is then set to en_NL.UTF-8 which is invalid, causing rendering issues in konsole, screen, for example. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1322968 Title: Changing country leads to invalid locale To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kde-runtime/+bug/1322968/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1828637] [NEW] sru cloud-init (18.5-45 to 19.1.1) Xenial, Bionic, Cosmic, Disco
Public bug reported: == Begin SRU Template == [Impact] This release sports both bug-fixes and new features and we would like to make sure all of our supported customers have access to these improvements. The notable ones are: - Azure: Return static fallback address as if failed to find endpoint [Jason Zions (MSFT)] - cc_mounts: check if mount -a on no-change fstab path [Jason Zions (MSFT)] - replace remaining occurrences of LOG.warn - DataSourceAzure: Adjust timeout for polling IMDS [Anh Vo] - Azure: Changes to the Hyper-V KVP Reporter [Anh Vo] - packages: update rpm specs for new bash completion path - setup.py: install bash completion script in new location - mount_cb: do not pass sync and rw options to mount [Gonéri Le Bouder] - cc_apt_configure: fix typo in apt documentation [Dominic Schlegel] - Revert "DataSource: move update_events from a class to an instance..." - Change DataSourceNoCloud to ignore file system label's case. [Risto Oikarinen] - cmd:main.py: Fix missing 'modules-init' key in modes dict [Antonio Romito] - ubuntu_advantage: rewrite cloud-config module - Azure: Treat _unset network configuration as if it were absent [Jason Zions (MSFT)] - DatasourceAzure: add additional logging for azure datasource [Anh Vo] - Azure: Ensure platform random_seed is always serializable as JSON. [Jason Zions (MSFT)] - net: Fix ipv6 static routes when using eni renderer [Raphael Glon] - Add ubuntu_drivers config module - DataSource: move update_events from a class to an instance attribute See the changelog entry below for a full list of changes and bugs. [Test Case] The following development and SRU process was followed: https://wiki.ubuntu.com/CloudinitUpdates The cloud-init team will be in charge of attaching the artifacts and console output of the appropriate run to the bug. cloud-init team members will not mark ‘verification-done’ until this has happened. * Automated Test Results TODO: attach automated cloud-init-proposed test artifacts sru-artifact-lxd-artful sru-artifact-lxc-xenial TODO: attach automated cloud-init-proposed test artifacts from tests for each release with kvm artifacts sru-artifact-kvm-artful sru-artifact-kvm-xenial TODO: attach Solutions Testing team test results for each LTS sru-artifact-solutions-qa-xenial TODO: attach MAAS Team test results for each LTS sru-artifact-maas-xenial * Manual Test Results TODO: attach manual cloud-init-proposed test artifacts from tests for each release on ec2 datasource sru-artifact-manual-ec2 TODO: attach manual cloud-init-proposed test artifacts from tests for each release on gce datasource sru-artifact-manual-gce TODO: attach manual cloud-init-proposed test artifacts from tests for each release on azure datasource sru-artifact-manual-azure [Regression Potential] In order to mitigate the regression potential, the results of the aforementioned integration tests are attached to this bug. [Discussion] == End SRU Template == == Changelog == - Azure: Return static fallback address as if failed to find endpoint [Jason Zions (MSFT)] - release 19.1 - freebsd: add chpasswd pkg in the image [Gonéri Le Bouder] - tests: add Eoan release [Paride Legovini] - cc_mounts: check if mount -a on no-change fstab path [Jason Zions (MSFT)] - replace remaining occurrences of LOG.warn - DataSourceAzure: Adjust timeout for polling IMDS [Anh Vo] - Azure: Changes to the Hyper-V KVP Reporter [Anh Vo] - git tests: no longer show warning about safe yaml. [Scott Moser] - tools/read-version: handle errors [Chad Miller] - net/sysconfig: only indicate available on known sysconfig distros - packages: update rpm specs for new bash completion path - test_azure: mock util.SeLinuxGuard where needed [Jason Zions (MSFT)] - setup.py: install bash completion script in new location - mount_cb: do not pass sync and rw options to mount [Gonéri Le Bouder] - cc_apt_configure: fix typo in apt documentation [Dominic Schlegel] - Revert "DataSource: move update_events from a class to an instance..." - Change DataSourceNoCloud to ignore file system label's case. [Risto Oikarinen] - cmd:main.py: Fix missing 'modules-init' key in modes dict [Antonio Romito] - ubuntu_advantage: rewrite cloud-config module - Azure: Treat _unset network configuration as if it were absent [Jason Zions (MSFT)] - DatasourceAzure: add additional logging for azure datasource [Anh Vo] - cloud_tests: fix apt_pipelining test-cases - Azure: Ensure platform random_seed is always serializable as JSON. [Jason Zions (MSFT)] - net/sysconfig: write out SUSE-compatible IPv6 config [Robert Schweikert] - tox: Update testenv for openSUSE Leap to 15.0 [Thomas Bechtold] - net: Fix ipv6 static routes when using eni renderer [Raphael Glon] - Add ubuntu_drivers config module - doc:
[Bug 1820212] Re: [MIR] python-aiosmtpd as dependency of mailman3
Eduardo is taking a look at this package for the security team and
pointed out that it is doing a setuid to user 'nobody'.
This isn't a safe design. User nobody is strictly for NFS's use and must
not be used by any running processes on the system.
This service probably needs its own user account.
I'm not sure what its goals are by changing to nobody, but we probably also
need to fix the setuid code. (Far better would be to strip the code out and use
systemd's facilities for setting user, group, groups, etc.)
The code currently looks like:
@public
def main(args=None):
parser, args = parseargs(args=args)
if args.setuid: # pragma: nomswin
if pwd is None:
print('Cannot import module "pwd"; try running with -n option.',
file=sys.stderr)
sys.exit(1)
nobody = pwd.getpwnam('nobody').pw_uid
try:
os.setuid(nobody)
except PermissionError:
print('Cannot setuid "nobody"; try running with -n option.',
file=sys.stderr)
sys.exit(1)
The usual practice with changing privs is to set groups, set group, and
then set the user.
I'm a bit curious what the usecase of this tool is -- it also appears to
start a mainloop that will break on keyboard interrupt -- is it meant to
be run in a shell session or something? Why wouldn't it be a daemon? (If
it *is* meant to be run from a terminal, then it also needs to prevent
TIOCSTI use by the processes running with lowered privileges, if that is
indeed why it changed to nobody.)
At a first glance this doesn't feel ready for prime-time.
Thanks
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1820212
Title:
[MIR] python-aiosmtpd as dependency of mailman3
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-aiosmtpd/+bug/1820212/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1828637] Re: sru cloud-init (18.5-45 to 19.1.1) Xenial, Bionic, Cosmic, Disco
** Merge proposal linked: https://code.launchpad.net/~chad.smith/cloud-init/+git/cloud-init/+merge/367301 ** Changed in: cloud-init (Ubuntu) Assignee: (unassigned) => Chad Smith (chad.smith) ** Changed in: cloud-init (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1828637 Title: sru cloud-init (18.5-45 to 19.1.1) Xenial, Bionic, Cosmic, Disco To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1828637/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
