[Bug 1838604] Re: cannot close nautilus windows
I opened other windows: total 4 I right click quit 4 windows only the 2 most recently opened windows close. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1838604 Title: cannot close nautilus windows To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1838604/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1838604] Re: cannot close nautilus windows
Nautilus UI artifacts visible in other applications :( ** Attachment added: "screengrab of nautilus artifact" https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1838604/+attachment/5280288/+files/nautilusUIartifacts.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1838604 Title: cannot close nautilus windows To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1838604/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1838604] [NEW] cannot close nautilus windows
Public bug reported: lsb_release -rd Description:Ubuntu 19.04 Release:19.04 apt-cache policy nautilus nautilus: Installed: 1:3.32.1-0ubuntu0.19.04.0 Candidate: 1:3.32.1-0ubuntu0.19.04.0 Version table: *** 1:3.32.1-0ubuntu0.19.04.0 500 500 http://us.archive.ubuntu.com/ubuntu disco-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:3.32.0-0ubuntu2 500 500 http://us.archive.ubuntu.com/ubuntu disco/main amd64 Packages Right click quit 2 windows = windows remain open click on close individual window = window remains open WORSE, none of the contents in the folders are available. Mouse clicks do NOT respond in any of the open Nautilus windows. I can open other windows but if directory Z is not responding then I cannot open another instance of directory Z! ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: nautilus 1:3.32.1-0ubuntu0.19.04.0 ProcVersionSignature: Ubuntu 5.0.0-23.24-generic 5.0.15 Uname: Linux 5.0.0-23-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Aug 1 08:30:38 2019 InstallationDate: Installed on 2015-08-23 (1438 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) SourcePackage: nautilus UpgradeStatus: Upgraded to disco on 2019-04-24 (98 days ago) usr_lib_nautilus: dropbox 2019.02.14 ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco ** Attachment added: "UI artifacts in Nautilus" https://bugs.launchpad.net/bugs/1838604/+attachment/5280282/+files/UIartifacts.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1838604 Title: cannot close nautilus windows To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1838604/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1838601] Re: kernel update 5.0.0-23 breaks scroll mouse in xorg
Please test latest mainline kernel: https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.3-rc2/ ** Package changed: linux-hwe (Ubuntu) => linux (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1838601 Title: kernel update 5.0.0-23 breaks scroll mouse in xorg To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1838601/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1580308] Re: update-initramfs cryptsetup must correctly take into account PARTLABEL inside /etc/fstab
cryptsetup: WARNING: failed to detect canonical device is fixed in cryptsetup/2:2.0.3-2 - https://bugs.debian.org/cgi- bin/bugreport.cgi?bug=784881 The version is not available in Ubuntu 18.10 - https://packages.ubuntu.com/bionic-updates/cryptsetup - which means initramfs update fail for encrypted disks. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1580308 Title: update-initramfs cryptsetup must correctly take into account PARTLABEL inside /etc/fstab To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/1580308/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1580308] Re: update-initramfs cryptsetup must correctly take into account PARTLABEL inside /etc/fstab
Not included in 18.04 LTS. This causes servers to hang after update and reboot - https://community.scaleway.com/t/arm64-hangs-with-ubuntu-18-04 -fully-updated/7681 ** Also affects: cryptsetup (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/1580308 Title: update-initramfs cryptsetup must correctly take into account PARTLABEL inside /etc/fstab To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/1580308/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1838601] Re: kernel update 5.0.0-23 breaks scroll mouse in xorg
** Package changed: xorg (Ubuntu) => linux (Ubuntu) ** Package changed: linux (Ubuntu) => linux-hwe (Ubuntu) ** Tags added: regression-update -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1838601 Title: kernel update 5.0.0-23 breaks scroll mouse in xorg To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe/+bug/1838601/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1838133] Re: realtek r8822be kernel module fails after update to linux kernel-headers 5.0.0-21
Hi Jun: "journalctl -b0" will be better than dmesg -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1838133 Title: realtek r8822be kernel module fails after update to linux kernel- headers 5.0.0-21 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1838133/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1837700] Re: Dell system takes a long time to connect network with external dock
** Changed in: systemd (Ubuntu) Importance: Undecided => Medium ** Changed in: systemd (Ubuntu Bionic) Importance: Undecided => Medium ** Changed in: systemd (Ubuntu Disco) Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1837700 Title: Dell system takes a long time to connect network with external dock To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1837700/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1838358] Re: Ibus causes gnome-shell to freeze when password fields are selected in Firefox
** Changed in: ibus (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1838358 Title: Ibus causes gnome-shell to freeze when password fields are selected in Firefox To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1838358/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1837869] Re: Cannot complete snapshot if read-only backing store is opened by another VM
Ok this set of patches would be enough to fix it. @Louis / Clement - would you have some time to help to break these into smaller chunks trying to identify how much smaller we could make the patch set? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1837869 Title: Cannot complete snapshot if read-only backing store is opened by another VM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1837869/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1838514] Re: Suspend failure with kernel 4.15.0-56-generic
Thanks for the bug-report and the remarks Aldric! I think we can forgo the apport data from the -56 kernel for now. I'd prefer to do a bisect if possible. Would you be willing to help bisect the issue to narrow down the root cause of the problem? Your assessment seems very plausible so we may only need to do 2 test runs to confirm (one kernel just before that patch and one with the patch), but worst-case scenario, we may need to do 12 tests (to bisect ~2800 patches). I'm thinking we start bisecting right around the suspected patch to confirm your theory, and if it's not the cause we'll take it from there. Please confirm if you can help with testing the bisected kernels, and if so I will provide instructions and the first kernel. Thanks @Aldric! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1838514 Title: Suspend failure with kernel 4.15.0-56-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1838514/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1838358] Re: Ibus causes gnome-shell to freeze when password fields are selected in Firefox
Revised debdiff for bionic which enables the environment variables IBUS_DISCARD_PASSWORD and IBUS_DISCARD_PASSWORD_APPS ** Patch added: "revised debdiff for bionic" https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1838358/+attachment/5280261/+files/lp1838358_bionic_revised.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1838358 Title: Ibus causes gnome-shell to freeze when password fields are selected in Firefox To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1838358/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1835968] Re: Regression in backported patch for openssl 1.1
Hello Unit, or anyone else affected, Accepted ruby2.5 into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/ruby2.5/2.5.1-1ubuntu1.5 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: ruby2.5 (Ubuntu Bionic) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1835968 Title: Regression in backported patch for openssl 1.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ruby2.5/+bug/1835968/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1838601] [NEW] kernel update 5.0.0-23 breaks scroll mouse in xorg
Public bug reported: Just updated 18.04 to kernel 5.0.0-23 and scrolling with mouse wheel does not work or works very slowly. Mouse is Microsoft Wireless Optical Mouse 3000 connected via USB to wireless receiver. Rebooting system into kernel 4.18.0-25 and everything works correctly. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.0.0-23.24~18.04.1-generic 5.0.15 Uname: Linux 5.0.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 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: MATE Date: Wed Jul 31 22:53:44 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: virtualbox, 5.2.18, 4.18.0-24-generic, x86_64: installed virtualbox, 5.2.18, 4.18.0-25-generic, x86_64: installed ExtraDebuggingInterest: Yes 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:21f3] InstallationDate: Installed on 2019-04-05 (118 days ago) InstallationMedia: Ubuntu-MATE 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: LENOVO 2347GBU ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-23-generic root=UUID=c840a596-f648-4a82-98f4-70137859c633 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/19/2012 dmi.bios.vendor: LENOVO dmi.bios.version: G1ET73WW (2.09 ) dmi.board.asset.tag: Not Available dmi.board.name: 2347GBU 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:bvrG1ET73WW(2.09):bd10/19/2012:svnLENOVO:pn2347GBU:pvrThinkPadT430:rvnLENOVO:rn2347GBU:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T430 dmi.product.name: 2347GBU dmi.product.sku: LENOVO_MT_2347 dmi.product.version: ThinkPad T430 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1.1~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.2-1ubuntu1.1~18.04.2 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1838601 Title: kernel update 5.0.0-23 breaks scroll mouse in xorg To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1838601/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1838477] Re: [regression] r8169 network device unable to detect link on x86 arch
Please test latest mainline kernel: https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.3-rc2/ It contains several fixes for r8169. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1838477 Title: [regression] r8169 network device unable to detect link on x86 arch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1838477/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1838358] Re: Ibus causes gnome-shell to freeze when password fields are selected in Firefox
Hi Oliver, Full details from the environment which has the problem: Affected machines are all running Bionic and are fully patched. firefox: 68.0.1+build1-0ubuntu0.18.04.1 gnome-shell: 3.28.4-0ubuntu18.04.1 ibus: 1.5.17-3ubuntu4 Machines are accessed as a VDI through VMware Horizon 7.9.0, and users who have problems are using Gnome 3. After discussing this with Eric D, we agreed that it might be a better idea to not restore the old ibus-xx-f19-password.patch and instead go with the upstream solution of https://github.com/ibus/ibus/commit/f328fd67f479faa46ca87bf3c85eed7080ec5ec0 which implements the same functionality, but hides it behind two environment variables, IBUS_DISCARD_PASSWORD and IBUS_DISCARD_PASSWORD_APPS. To be honest, I think this approach is better since it doesn't change any default behaviour and the fix is opt in for environments which need it. Plus this is present in cosmic, disco and eoan, and will be available in the future 20.04 LTS. I have tried my best to reproduce this, but I have not had any luck. I think this solution is probably the best for all parties, and this has been tested successfully in the affected environment, so I have made a new debdiff with the above patch. I would like to determine and fix the root cause, but that might be a little challenging, and this is a sufficient workaround. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1838358 Title: Ibus causes gnome-shell to freeze when password fields are selected in Firefox To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1838358/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1838533] Re: Bionic linux 4.15.0-56.62 fails to build with CONFIG_NVM disabled
** Changed in: linux (Ubuntu Bionic) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1838533 Title: Bionic linux 4.15.0-56.62 fails to build with CONFIG_NVM disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1838533/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1821927] Re: Systemd do not respawn sssd on failure
In this case Robie we are following upstream where we suggested it due to this bug. And while I agree to making things consistent across packages we have talked about it before and nothing happened yet. IMHO: It is correct to say "let us use this as a reminder to reconsider an effort across packages" but not "hold this one back as it might make it different (others are already)". -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1821927 Title: Systemd do not respawn sssd on failure To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/1821927/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1838576] Re: Bionic update: upstream stable patchset 2019-07-31
** Changed in: linux (Ubuntu Bionic) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1838576 Title: Bionic update: upstream stable patchset 2019-07-31 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1838576/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1838358] Re: Ibus causes gnome-shell to freeze when password fields are selected in Firefox
** Description changed: [Impact] The following has been seen in a VMware Horizon VDI. I cannot reproduce this issue myself. When a user interacts with any password field in Firefox, gnome-shell and Firefox both freeze and the system becomes unusable. If you ssh into the system and terminate Firefox, gnome-shell unfreezes. - This only happens when the environment variable GTK_IM_MODULE is set to "ibus". If you unset the variable, or change it to + This only happens when the environment variable GTK_IM_MODULE is set to "ibus". If you unset the variable, or change it to GTK_IM_MODULE=gtk-im-context-simple and then start Firefox, everything works as intended. This has been seen before with gnome-shell 3.28.4-0ubuntu18.04.1, ibus 1.5.17-3ubuntu4 and Firefox versions starting with 68.0+build3-0ubuntu0.18.04.1 Note: Chrome[ium] and other applications do not trigger it, and it cannot be reproduced in other desktop environments. This seems to be an interaction issue between ibus and gnome-shell. [Fix] When ibus is built with the patch ibus-xx-f19-password.patch which was dropped in ibus-1.5.17-2, the problem is solved. - ibus-xx-f19-password.patch checks to see if the GTK version is at or - above 3.6, and if it is, checks to see if the input purpose is for a - password field. If it is, then no further action is taken by ibus. + Instead of using ibus-xx-f19-password.patch, we will instead fix it with + upstream commit f328fd67f479faa46ca87bf3c85eed7080ec5ec0: + + https://github.com/ibus/ibus/commit/f328fd67f479faa46ca87bf3c85eed7080ec5ec0 + + Subject: client/gtk2: Add IBUS_DISCARD_PASSWORD for firefox and chrome + Author: fujiwarat + + This implements the password discard functionality found in + ibus-xx-f19-password.patch and places it behind two environment variables, + IBUS_DISCARD_PASSWORD and IBUS_DISCARD_PASSWORD_APPS. + + IBUS_DISCARD_PASSWORD is for a single process, and IBUS_DISCARD_PASSWORD_APPS + lets you set a regex of process names to filter and enable the fix for. + + If IBUS_DISCARD_PASSWORD is set or IBUS_DISCARD_PASSWORD_APPS is set with the + process name which input is being placed into password fields, ibus will pass + through the input to the application without any processing. [Testcase] Launch firefox from within a gnome-session, making sure the GTK_IM_MODULE is set to "ibus". Note, this is the default value. $ env GTK_IM_MODULE="ibus" firefox Navigate to any website which has a password field. Wikipedia or Reddit will do. Click a password field and attempt to enter text. Firefox and gnome- shell both lock up and stay frozen for an extended period of time. - With the test package which includes ibus-xx-f19-password.patch, gnome-shell - and Firefox do not lock up and everything works as intended. + Now, try it with the fix by enabling: + + $ env IBUS_DISCARD_PASSWORD=1 firefox + + When you enter text into a password field, ibus should directly pass through + the text and the problem will be solved. + + We can also ask it to always apply for a specific application with: + + $ export IBUS_DISCARD_PASSWORD_APPS="firefox" + $ firefox + + Again, when you enter text into a password input field, the problem will be + solved. Test package is available here: https://launchpad.net/~mruffell/+archive/ubuntu/sf235370-test + Please test with the revised version, + 1.5.17-3ubuntu4+sf235370v20190731b1. + [Regression Potential] - This has a low to medium risk of regression, and is limited to inputs to - password fields in all applications, including the gnome-shell lock screen. + This change has a low risk of regression, because the default behaviour is + unchanged. To be able to use the password input field discard functionality, + a user has to explicitly set an environment variable for the specific process, or set a regex that matches a process name. - This patch has been extensively tested and it is present in the - following Ubuntu releases: + This means the fix is not enabled by default on any machines, and will + only be utilised by those suffering problems and go and manually set + environment variables or have their system administrator enable the + environment variables permanently. - artful: 1.5.14-2ubuntu1 - zesty: 1.5.14-2ubuntu1 - yakkety: 1.5.11-1ubuntu3 - xenial: 1.5.11-1ubuntu2 - wily: 1.5.10-1ubuntu1 - vivid: 1.5.9-1ubuntu3 - utopic: 1.5.8-2ubuntu2 - trusty: 1.5.5-1ubuntu3.2 + This commit is present in upstream ibus from version ibus-1.5.19 onward, and + is currently present in cosmic, disco and eoan. - The patch was introduced in trusty, and removed in bionic. I feel that the risk of reintroducing the patch is low, since the use case of the software is the same as previous releases in regards to input software and input language - selection. - - I still acknowledge a potential risk of regression when users change their - input engines to non
[Bug 1834603] Re: SRU request: Include the 430 driver in Ubuntu 18.04
Tried version 430.26-0ubuntu0.18.04.2, it works great. ** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1834603 Title: SRU request: Include the 430 driver in Ubuntu 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1834603/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1041861] Re: gnote crashed with SIGSEGV in g_action_muxer_insert()
[Expired for gnote (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gnote (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1041861 Title: gnote crashed with SIGSEGV in g_action_muxer_insert() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnote/+bug/1041861/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1132070] Re: Gnote removes bottom half of text in the note when searching
[Expired for gnote (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gnote (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1132070 Title: Gnote removes bottom half of text in the note when searching To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnote/+bug/1132070/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 626057] Re: links go wrong if only some of the pre-made notes is translated
[Expired for gnote (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gnote (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/626057 Title: links go wrong if only some of the pre-made notes is translated To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnote/+bug/626057/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1831357] Re: linux kernel
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1831357 Title: linux kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1831357/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1830481] Re: VLC cause the DE freeze up when open AVCHD BDMV folder
[Expired for vlc (Ubuntu) because there has been no activity for 60 days.] ** Changed in: vlc (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1830481 Title: VLC cause the DE freeze up when open AVCHD BDMV folder To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vlc/+bug/1830481/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1831482] Re: VIMC module not available (CONFIG_VIDEO_VIMC not set)
Hi Kieran, Thanks for checking, I have this sent to the mailing list: https://lists.ubuntu.com/archives/kernel-team/2019-August/102713.html ** Tags added: eoan -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1831482 Title: VIMC module not available (CONFIG_VIDEO_VIMC not set) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1831482/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1831482] Re: VIMC module not available (CONFIG_VIDEO_VIMC not set)
This is the test result for 4.15 kernel. ubuntu@curly:~$ uname -a Linux curly 4.15.0-56-generic #62 SMP Thu Aug 1 02:58:31 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux ubuntu@curly:~$ grep VIMC /boot/config-4.15.0-56-generic CONFIG_VIDEO_VIMC=m ubuntu@curly:~$ lsmod | grep vimc vimc_capture 16384 0 vimc_streamer 16384 1 vimc_capture videobuf2_vmalloc 16384 1 vimc_capture videobuf2_v4l2 24576 1 vimc_capture vimc_debayer 16384 0 vimc_scaler16384 0 videobuf2_core 40960 2 videobuf2_v4l2,vimc_capture vimc_sensor16384 0 v4l2_tpg 65536 1 vimc_sensor vimc_common16384 10 vimc_scaler,vimc_debayer,vimc_sensor,vimc_capture vimc 16384 0 videodev 184320 5 vimc_common,videobuf2_core,videobuf2_v4l2,vimc,vimc_capture media 40960 5 vimc_common,videodev,vimc_streamer,vimc,vimc_capture ** Description changed: - The Multimedia VIMC module provides a test interface for the linux-media - media controller framework. + == SRU Justification == + VIMC is a virtual media controller that can emulate a real media device. + This is useful for automated tests, and development of multimedia frameworks. + + == Fix == + Enable VIMC as a module in B/D/E kernel configs. + + == Test == + Test kernels could be found here: + https://people.canonical.com/~phlin/kernel/lp-1831482-cfg-vimc/ + + User has reported that the Eoan kernel works as expected. + I have also smoke tested the B/D kernel to make sure the VIMC modules + can be loaded properly. + + == Regression Potential == + Low, this patchset just enable the VIMC module support. + + + == Original Bug report == + The Multimedia VIMC module provides a test interface for the linux-media media controller framework. This is useful for automated tests, and development of multimedia frameworks. Other components similar to this such as VIVID (CONFIG_VIDEO_VIVID=m) are enabled, but VIMC is missing from the linux-modules packages: $ grep VIMC /boot/config-* /boot/config-4.15.0-32-generic:# CONFIG_VIDEO_VIMC is not set /boot/config-4.17.9-041709-generic:# CONFIG_VIDEO_VIMC is not set /boot/config-4.18.4-041804-generic:# CONFIG_VIDEO_VIMC is not set /boot/config-4.18.7-041807-generic:# CONFIG_VIDEO_VIMC is not set /boot/config-5.0.0-13-generic:# CONFIG_VIDEO_VIMC is not set /boot/config-5.0.0-15-generic:# CONFIG_VIDEO_VIMC is not set - Could this be enabled in future releases as a module please? I'm running Ubuntu 19.04, with Ubuntu 5.0.0-13.14-generic 5.0.6, however I believe this issue affects all current Ubuntu kernel releases. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1831482 Title: VIMC module not available (CONFIG_VIDEO_VIMC not set) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1831482/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1838245] Re: dkms script is missing function find_module
the case I tested:
install the dkms which already patched (also can be found in my ppa[1])
1. install a dkms which for a kernel module system already installed.
e.g. ath10k of my testing ppa : [1]
1.1. the dkms can be installed well.
2. install a dkms which has OBSOLETE_BY and FORCE
e.g.ath10k of my testing ppa : [1] (source code in [2])
+ the target dkms defined OBSOLETE_BY and FORCE
- OBSOLETE_BY="4.15.0-1033":
https://git.launchpad.net/~alextu/+git/oem-wifi-qualcomm-ath10k-lp1803647-4.15-dkms/tree/oem-wifi-qualcomm-ath10k-lp1803647-4.15/dkms.conf?h=lp1838245#n8
-
https://git.launchpad.net/~alextu/+git/oem-wifi-qualcomm-ath10k-lp1803647-4.15-dkms/tree/oem-wifi-qualcomm-ath10k-lp1803647-4.15.force?h=lp1838245
+ user install dkms on a system which installed kernel version less than
OBSOLETE_BY and another kernel higher than OBSOLETE_BY
- in my system there're 2 kernels 4.15.0-1030 and 4.15.0-1045
+ the dkms can be installed well with kernel 4.15.0-1030, and not be installed
with 4.15.0-1045
also attached the log came from patched dkms script during install dkms
[2]
[1]:https://code.launchpad.net/~alextu/+archive/ubuntu/dkms-2.3-lp1838245
[2]:https://code.launchpad.net/~alextu/+git/oem-wifi-qualcomm-ath10k-lp1803647-4.15-dkms/+ref/lp1838245
** Description changed:
- Building a kernel module using dkms in Linux Mint 19.1 shows the
- following error:
+
+ update for SRU process:
+ [Impact]
+ 1. dkms script is missing function find_module
+ 2. priority of OBSOLETE_BY should higher than "force". #89
https://github.com/dell/dkms/issues/89
+
+ [Test case]
+ install the dkms which already patched (also can be found in my ppa[1])
+ 1. install a dkms which for a kernel module system already installed.
+ e.g. ath10k of my testing ppa : [1]
+ 1.1. the dkms can be installed well.
+
+ 2. install a dkms which has OBSOLETE_BY and FORCE
+ e.g.ath10k of my testing ppa : [1] (source code in [2])
+ - the target dkms defined OBSOLETE_BY and FORCE
+ - user install dkms on a system which installed kernel version less than
OBSOLETE_BY and another kernel higher than OBSOLETE_BY
+ - the dkms can be installed well.
+
+ [Regression potential]
+ medium as it touched the version sanity. This change correct the code logic
and land one more change from upstream as well.
+ The logic has been verified by #5 and me.
+
+
+ Building a kernel module using dkms in Linux Mint 19.1 shows the following
error:
Running module version sanity check.
/usr/sbin/dkms: Zeile 784: find_module: Befehl nicht gefunden
modinfo: ERROR: missing module or filename.
Checking the file the function is indeed missing and another user
confirmed, that it was removed at some point:
https://github.com/linuxmint/linuxmint/issues/142
Possible solution: Readd
find_module()
{
- # tree = $1
- # module = $2
- find "$1" -name "$2$module_uncompressed_suffix" -o -name
"$2$module_suffix" -type f
- return $?
+ # tree = $1
+ # module = $2
+ find "$1" -name "$2$module_uncompressed_suffix" -o -name
"$2$module_suffix" -type f
+ return $?
}
as found in https://github.com/dell/dkms/blob/master/dkms
** Attachment added: "install-ath10k.log"
https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/1838245/+attachment/5280259/+files/install-ath10k.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1838245
Title:
dkms script is missing function find_module
To manage notifications about this bug go to:
https://bugs.launchpad.net/dkms/+bug/1838245/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1836608] Re: [19.10 FEAT] Splitting DIF and DIX boot time controls - s390tools part
** Information type changed from Private to Public -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1836608 Title: [19.10 FEAT] Splitting DIF and DIX boot time controls - s390tools part To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1836608/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1836862] Re: [18.04 FEAT] Enhanced CPU-MF hardware counters - s390tools part
** Information type changed from Private to Public ** Also affects: s390-tools (Ubuntu Bionic) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1836862 Title: [18.04 FEAT] Enhanced CPU-MF hardware counters - s390tools part To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1836862/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1794349] Re: fix bugs and test zkey udeb (missing directories, permissions, etc)
** Changed in: s390-tools (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/1794349 Title: fix bugs and test zkey udeb (missing directories, permissions, etc) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/s390-tools/+bug/1794349/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1838599] [NEW] alsa/sof: need to update the firmware of sound sof driver
Public bug reported: This bug is for tracking purpose. ** Affects: hwe-next Importance: Undecided Status: New ** Affects: linux-firmware (Ubuntu) Importance: Undecided Assignee: Hui Wang (hui.wang) Status: New ** Tags: originate-from-1837853 somerville ** Package changed: pulseaudio (Ubuntu) => linux-firmware (Ubuntu) ** Tags added: originate-from-1837853 somerville -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1838599 Title: alsa/sof: need to update the firmware of sound sof driver To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1838599/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1837834] Re: Add support for Linux 5.0-5.2
I installed the new proposed 340.107-0ubuntu0.18.04.3 version, and now nvidia-340 properly builds and works for me on kernel 5.0.0 in Ubuntu 18.04. Thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1837834 Title: Add support for Linux 5.0-5.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1837834/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1838590] Re: Update thermald to 1.9 release
** Changed in: dptfxtract (Ubuntu) Assignee: (unassigned) => Anthony Wong (anthonywong) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1838590 Title: Update thermald to 1.9 release To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dptfxtract/+bug/1838590/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1389582] Re: software-center misses a dependency on libgtk2-perl
This bug has been reported on the Ubuntu ISO testing tracker. A list of all reports related to this bug can be found here: http://iso.qa.ubuntu.com/qatracker/reports/bugs/1389582 ** Tags added: iso-testing -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1389582 Title: software-center misses a dependency on libgtk2-perl To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1389582/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1820477] Re: 软件中心搜狗输入法无法启动
搜狗输入法已跟吴孝夷确认，desktop运行启动不会有界面效果，是正常现象。 ** Changed in: ubuntukylin Status: New => Fix Committed ** Changed in: ubuntu-kylin-software-center (Ubuntu) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1820477 Title: 软件中心搜狗输入法无法启动 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntukylin/+bug/1820477/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1579185] Re: imagej won't start (xenial)
*** This bug is a duplicate of bug 1556997 *** https://bugs.launchpad.net/bugs/1556997 It still happens on Bionic. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1579185 Title: imagej won't start (xenial) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/imagej/+bug/1579185/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1837617] Re: bionic/linux-fips: 4.15.0-1013.15 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: In Progress => Fix Released ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1837626 packages: main: linux-fips meta: linux-meta-fips signed: linux-signed-fips - phase: Packaging - phase-changed: Wednesday, 31. July 2019 19:10 UTC + phase: Holding before Promote to Proposed + phase-changed: Thursday, 01. August 2019 02:15 UTC reason: - prepare-package: Stalled -- package tag not yet published promote-to-proposed: Pending -- builds not complete in ppa main:failed,meta:depwait,signed:depwait variant: debs -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1837617 Title: bionic/linux-fips: 4.15.0-1013.15 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1837617/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1820471] Re: 优麒麟软件商店没有快捷启动选项
优客助手的desktop名字与包名不同，已经进行处理可进行启动了，优客天气不提供启动项启动，另外不能直接启动的软件已处理为不会显示启动按钮。 ** Changed in: ubuntukylin Status: New => Fix Committed ** Changed in: ubuntu-kylin-software-center (Ubuntu) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1820471 Title: 优麒麟软件商店没有快捷启动选项 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntukylin/+bug/1820471/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1710278] Re: [2.3a1] named stuck on reload, DNS broken
Am I reading this bug correctly, that MAAS currently asks BIND to reload its entire configure file on every machine provision and removal? This seems like a problem worth solving rather than trying to work around. At least PowerDNS provides several mechanisms for dynamically adding and removing records from a zone: - dnsupdate: https://doc.powerdns.com/authoritative/dnsupdate.html - REST api: https://doc.powerdns.com/authoritative/http-api/index.html - direct SQL to a backing database: https://doc.powerdns.com/authoritative/migration.html Since dnsupdate is an RFC-standardized protocol there's a pretty good shot BIND supports it as well. Was this tried and found lacking? The API and SQL approaches are likely to not have equivalents in BIND. I'm not sure what your DNSSEC goals are, but PowerDNS's documentation describes choices, including pkcs#11 in case that's important: https://doc.powerdns.com/authoritative/dnssec/index.html Thanks -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1710278 Title: [2.3a1] named stuck on reload, DNS broken To manage notifications about this bug go to: https://bugs.launchpad.net/bind/+bug/1710278/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1838591] [NEW] sbuild fails to install build-essential in debian unstable chroot
Public bug reported: Trying to build a package in a debian unstable chroot using Bionic sbuild fails due to missing dpkg-scanpackage: $ sudo sbuild -d unstable -A -s +--+ | Install build-essential | +--+ Setup apt archive - Merged Build-Depends: build-essential, fakeroot Filtered Build-Depends: build-essential, fakeroot dpkg-deb: building package 'sbuild-build-depends-core-dummy' in '/<>/resolver-8rjiMc/apt_archive/sbuild-build-depends-core-dummy.deb'. Can't exec "dpkg-scanpackages": No such file or directory at -e line 23. system dpkg-scanpackages . /dev/null failed: -1 at -e line 23. E: cannot create dummy archive Failed to run apt-ftparchive. E: Setting up apt archive failed Setup apt archive - Merged Build-Depends: dose-distcheck Filtered Build-Depends: dose-distcheck dpkg-deb: building package 'sbuild-build-depends-dose3-dummy' in '/<>/resolver-8rjiMc/apt_archive/sbuild-build-depends-dose3-dummy.deb'. Can't exec "dpkg-scanpackages": No such file or directory at -e line 23. system dpkg-scanpackages . /dev/null failed: -1 at -e line 23. E: cannot create dummy archive Failed to run apt-ftparchive. E: Setting up apt archive failed E: Failed to explain bd-uninstallable This looks like dpkg-scanpackages is needed to create the dummy package, but that's in dpkg-dev which is what it should be installing at this point. This used to work before the buster release. If I pre-install dpkg-dev in the chroot then it works fine. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: sbuild 0.75.0-1ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18 Uname: Linux 4.15.0-46-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: XFCE Date: Thu Aug 1 02:24:01 2019 PackageArchitecture: all SourcePackage: sbuild UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: sbuild (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/1838591 Title: sbuild fails to install build-essential in debian unstable chroot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sbuild/+bug/1838591/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1838577] Re: Default audio device changes on reboot; audio still outputs using my previously-selected device
** Changed in: pulseaudio (Ubuntu) Importance: Undecided => Medium ** Changed in: pulseaudio (Ubuntu) Status: New => Triaged -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1838577 Title: Default audio device changes on reboot; audio still outputs using my previously-selected device To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1838577/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1838590] Re: Update thermald to 1.9 release
dptfxtract should be upgraded to 1.4.2 at the same time. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1838590 Title: Update thermald to 1.9 release To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dptfxtract/+bug/1838590/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1838590] [NEW] Update thermald to 1.9 release
Public bug reported: The thermald 1.9 release was just tagged, and has potential to help quite a bit with platform performance on some newer platforms when run with kernel 5.3. It would be nice to update eoan to this new release. > - The major change in this version is the active power limits adjustment. This will be useful to improve performance on some newer platform. But this will will lead to increase in CPU and other temperatures. Hence this is important to run dptfxtract version 1.4.1 tool to get performance sensitive thermal limits (https://github.com/intel/dptfxtract/commits/v1.4.1). If the default configuration picked up by thermald is not optimal, user can select other less aggressive configuration. Refer to the README here https://github.com/intel/dptfxtract/blob/master/README.txt ** Affects: dptfxtract (Ubuntu) Importance: Wishlist Status: New ** Affects: thermald (Ubuntu) Importance: Wishlist Status: New ** Changed in: thermald (Ubuntu) Importance: Undecided => Wishlist ** Description changed: The thermald 1.9 release was just tagged, and has potential to help quite a bit with platform performance on some newer platforms when run - with kernel 5.3. It would be nice to update disco to this new release. + with kernel 5.3. It would be nice to update eoan to this new release. > - The major change in this version is the active power limits adjustment. This will be useful to improve performance on some newer platform. But this will will lead to increase in CPU and other temperatures. Hence this is important to run dptfxtract version 1.4.1 tool to get performance sensitive thermal limits (https://github.com/intel/dptfxtract/commits/v1.4.1). If the default configuration picked up by thermald is not optimal, user can select other less aggressive configuration. Refer to the README here https://github.com/intel/dptfxtract/blob/master/README.txt ** Also affects: dptfxtract (Ubuntu) Importance: Undecided Status: New ** Changed in: dptfxtract (Ubuntu) Importance: Undecided => Wishlist -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1838590 Title: Update thermald to 1.9 release To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dptfxtract/+bug/1838590/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1838133] Re: realtek r8822be kernel module fails after update to linux kernel-headers 5.0.0-21
Hi Aaron~ For #10 and #11, I removed r8822be from /etc/modprobe.d/blacklist.conf and added rtwpci to blacklist, rebuilt the initial ramdisk with sudo update-initramfs -u -k 5.0.0-21-generic and rebooted; Now my realtek wifi card is operational with this workaround! For the next test to help you debug the rtw88 realtek driver I will do the following: (1) re-add r8822be to blacklist.conf (2) remove rtwpci from blacklist.conf (3) rebuild initrd (4) reboot (5) add rtw88.debug_mask=0x3ff in kernel cmdline in GRUB (6) boot (7) send you the output of dmesg Thanks for your help! Jun -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1838133 Title: realtek r8822be kernel module fails after update to linux kernel- headers 5.0.0-21 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1838133/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1837155] Re: xenial/linux-fips: 4.4.0-1015.20 -proposed tracker
** Tags added: regression-testing-passed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1837155 Title: xenial/linux-fips: 4.4.0-1015.20 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1837155/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1837155] Re: xenial/linux-fips: 4.4.0-1015.20 -proposed tracker
** Changed in: kernel-sru-workflow/regression-testing Status: Confirmed => Fix Released ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1837476 packages: main: linux-fips meta: linux-meta-fips signed: linux-signed-fips phase: Ready for Testing phase-changed: Tuesday, 23. July 2019 22:41 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress - regression-testing: Ongoing -- testing in progress variant: debs -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1837155 Title: xenial/linux-fips: 4.4.0-1015.20 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1837155/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1837617] Re: bionic/linux-fips: 4.15.0-1013.15 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package-signed Status: In Progress => Fix Released ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1837626 packages: main: linux-fips meta: linux-meta-fips signed: linux-signed-fips phase: Packaging phase-changed: Wednesday, 31. July 2019 19:10 UTC reason: prepare-package: Stalled -- package tag not yet published - prepare-package-signed: Stalled -- package tag not yet published promote-to-proposed: Pending -- builds not complete in ppa main:failed,meta:depwait,signed:depwait variant: debs -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1837617 Title: bionic/linux-fips: 4.15.0-1013.15 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1837617/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1838115] Re: linux hwe i386 kernel 5.0.0-21.22~18.04.1 crashes on Lenovo x220
I've read Juerg's explanation [1]. I guess this commit will appear in xenial repos automatically. Thank you. [1] https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1827884 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1838115 Title: linux hwe i386 kernel 5.0.0-21.22~18.04.1 crashes on Lenovo x220 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1838115/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1827884] Re: x86: mm: early boot problem on i386 with KPTI enabled
*** This bug is a duplicate of bug 1838115 *** https://bugs.launchpad.net/bugs/1838115 I didn't know it. Thank you. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1827884 Title: x86: mm: early boot problem on i386 with KPTI enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1827884/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1838588] [NEW] scilab Xcos does not show graphical window upon simulation
Public bug reported: When I launch Xcos from scilab and perform a simulation, no graphical window shows up after the simulation is complete. May I suggest an update to 6.0.2? ** Affects: scilab (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/1838588 Title: scilab Xcos does not show graphical window upon simulation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/scilab/+bug/1838588/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1838115] Re: linux hwe i386 kernel 5.0.0-21.22~18.04.1 crashes on Lenovo x220
Xenial hwe kernels is affected. Non-hwe isn't affected indeed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1838115 Title: linux hwe i386 kernel 5.0.0-21.22~18.04.1 crashes on Lenovo x220 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1838115/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1838586] [NEW] xfce4-appmenu-plugin using high CPU
Public bug reported: Description:Ubuntu Eoan Ermine (development branch) Release:19.10 xfce4-appmenu-plugin: Installed: 0.7.1+dfsg1-1 Candidate: 0.7.1+dfsg1-1 Version table: *** 0.7.1+dfsg1-1 500 500 http://us.archive.ubuntu.com/ubuntu eoan/universe amd64 Packages 100 /var/lib/dpkg/status When using xfce4-appmenu-plugin on Ubuntu Studio 19.10 in xfce4, I noticed it was using at or near 100% of one processor in my quad-core system (amounting to 25% total CPU usage). Not sure why that is, but that seems to be out of the ordinary. I would expect something to not use such high CPU, especially in such a lightweight desktop environment. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xfce4-appmenu-plugin 0.7.1+dfsg1-1 ProcVersionSignature: Ubuntu 5.2.0-8.9-lowlatency 5.2.0 Uname: Linux 5.2.0-8-lowlatency x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: XFCE Date: Wed Jul 31 17:42:49 2019 InstallationDate: Installed on 2019-02-12 (170 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190203) SourcePackage: vala-panel-appmenu UpgradeStatus: Upgraded to eoan on 2019-06-11 (50 days ago) ** Affects: vala-panel-appmenu (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1838586 Title: xfce4-appmenu-plugin using high CPU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vala-panel-appmenu/+bug/1838586/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1837397] Re: Make possible to load Mellanox OFED modules
** Changed in: linux-azure (Ubuntu Xenial) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1837397 Title: Make possible to load Mellanox OFED modules To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1837397/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1838584] [NEW] /usr/bin/gspiceui:5:__GI_raise:wxTrap:wxGUIAppTraits::ShowAssertDialog:ShowAssertDialog:wxAppConsoleBase::OnAssertFailure
Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding gspiceui. This problem was most recently seen with package version 1.1.00+dfsg-2, the problem page at https://errors.ubuntu.com/problem/f5689290d32217c923b65549a083fba094ef4f55 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: gspiceui (Ubuntu) Importance: Undecided Status: New ** Tags: artful bionic cosmic disco wily 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/1838584 Title: /usr/bin/gspiceui:5:__GI_raise:wxTrap:wxGUIAppTraits::ShowAssertDialog:ShowAssertDialog:wxAppConsoleBase::OnAssertFailure To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gspiceui/+bug/1838584/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1838113] Re: eoan/linux: 5.2.0-10.11 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1838112 (bionic/linux-hwe-edge) -- swm properties -- boot-testing-requested: true packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Promote to Proposed phase-changed: Wednesday, 31. July 2019 20:56 UTC reason: - promote-to-proposed: Ongoing -- package copied to Proposed signed:depwait + promote-to-proposed: Pending -- package copied to Proposed signed:retry-needed trackers: bionic/linux-hwe-edge: bug 1838112 variant: debs -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1838113 Title: eoan/linux: 5.2.0-10.11 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1838113/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1835279] Re: 4.15.0-54.58-generic 4.15.18: oops/BUG on LUKS open
Thanks Connor. My test configuration is a custom core system using the official core18 kernel snap on a KVM-based virtual machine. The kernel snap is installed from channel 18 (snap download --channel 18 pc-kernel) and my current revision is 240. That said, it's easy to test new kernels as long as I can convert them to a snap package. Foundations is currently preparing a kernel snap based on eoan so I can check with this newer kernel if the problems persist (it could be a first check for a bisect), but I could also boot an instrumented kernel that would give us a better insight on what could be happening. So, to summarize: we can use either approach, but my feeling is that the debug kernel and the eoan kernel could be a good start to help us to gather more data points. Ideally I could start testing that next week after returning from Toronto. Would that work for you? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1835279 Title: 4.15.0-54.58-generic 4.15.18: oops/BUG on LUKS open To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1835279/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1836816] Re: Fix nf_conntrack races when dealing with same origin requests in NAT environments
I installed 4.15.0-56-generic #62~16.04.1-Ubuntu xenial HWE kernel, and I followed the reproducer instructions at https://github.com/brb/conntrack-race, specifically loading in the NAT iptables rules, enabling debug output of the conntrack file and running the programs server and client. Looking at dmesg output, I see that conntrack collisions are found and resolved, and duplicate conntrack entries are de-allocated and returned to the slab. This kernel is also being tested in a kubernetes test cluster and I will update this bug if any problems arise. At the moment there isn't any. Since one of the patches are from upstream -stable, and I have spent some time validating, I am happy to mark this as verified. ** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1836816 Title: Fix nf_conntrack races when dealing with same origin requests in NAT environments To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1836816/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1837605] Re: xenial/linux-gcp: 4.15.0-1038.40~16.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: In Progress => Fix Released ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow derivatives: bug 1837603 (gcp-kernel), bug 1837604 (gke-kernel) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1837608 packages: main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp - phase: Testing - phase-changed: Wednesday, 31. July 2019 22:26 UTC + phase: Signoff + phase-changed: Wednesday, 31. July 2019 22:45 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - automated-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: xenial/linux-gcp/gcp-kernel: bug 1837603 xenial/linux-gcp/gke-kernel: bug 1837604 variant: debs -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1837605 Title: xenial/linux-gcp: 4.15.0-1038.40~16.04.1 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1837605/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1838271] Re: disco/linux: 5.0.0-23.24 -proposed tracker
All tasks have been completed and the bug is being set to Fix Released ** Changed in: kernel-sru-workflow Status: In Progress => Fix Released ** Tags removed: kernel-release-tracking-bug-live -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1838271 Title: disco/linux: 5.0.0-23.24 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1838271/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1835279] Re: 4.15.0-54.58-generic 4.15.18: oops/BUG on LUKS open
Hey Claudio, Did you experience this only after upgrading from a previous kernel? If so, what was the kernel that you upgraded from? I've been trying to reproduce this issue locally in a VM but haven't had any luck so far. So, I've been working from the kernel Oops in comment #1 and I am pretty sure I see where the NULL pointer is coming from but I am not sure yet where it's being to NULL. Since this smells a little bit like a race condition (unconfirmed) I'm trying to find ways to narrow down the search radius. I have a couple of options in mind for moving forward: 1. We can have you try out a few mainline kernels. If you experience the bug in one of the kernels but not another, we can "bisect" between mainline kernels to zero in on the culpable patch. I would be very interested to see if you experience the same regression on the latest mainline kernel, as that may indicate that the regression also exists in mainline. 2. I can continue reading through the code and prepare a debug kernel that will hopefully give us more information when the bug is triggered. My goal behind this would be to narrow down precisely where/how that NULL pointer is being set. Let me know if either of those options sound feasible to you. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1835279 Title: 4.15.0-54.58-generic 4.15.18: oops/BUG on LUKS open To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1835279/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1837605] Re: xenial/linux-gcp: 4.15.0-1038.40~16.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/promote-to-proposed Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/regression-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/security-signoff Status: New => In Progress ** Changed in: kernel-sru-workflow/verification-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/automated-testing Status: Confirmed => In Progress ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow derivatives: bug 1837603 (gcp-kernel), bug 1837604 (gke-kernel) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1837608 packages: main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp - phase: Promote to Proposed - phase-changed: Wednesday, 31. July 2019 15:55 UTC + phase: Testing + phase-changed: Wednesday, 31. July 2019 22:26 UTC + proposed-announcement-sent: true + proposed-testing-requested: true reason: - promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror sync + automated-testing: Ongoing -- testing in progress + regression-testing: Ongoing -- testing in progress + security-signoff: Pending -- waiting for signoff + verification-testing: Ongoing -- testing in progress trackers: xenial/linux-gcp/gcp-kernel: bug 1837603 xenial/linux-gcp/gke-kernel: bug 1837604 variant: debs -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1837605 Title: xenial/linux-gcp: 4.15.0-1038.40~16.04.1 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1837605/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1838575] Re: passthrough devices cause >17min boot delay
Attached file is already the stdio, sorry for prev message. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1838575 Title: passthrough devices cause >17min boot delay To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1838575/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1838576] Re: Bionic update: upstream stable patchset 2019-07-31
** Description changed: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: upstream stable patchset 2019-07-31 - Ported from the following upstream stable releases: - v4.14.120, v4.19.44, - v4.14.121, v4.19.45, - v4.14.122, v4.19.46 + Ported from the following upstream stable releases: + v4.14.120, v4.19.44, + v4.14.121, v4.19.45, + v4.14.122, v4.19.46 from git://git.kernel.org/ + + netfilter: compat: initialize all fields in xt_init + platform/x86: sony-laptop: Fix unintentional fall-through + platform/x86: thinkpad_acpi: Disable Bluetooth for some machines + hwmon: (pwm-fan) Disable PWM if fetching cooling data fails + kernfs: fix barrier usage in __kernfs_new_node() + USB: serial: fix unthrottle races + iio: adc: xilinx: fix potential use-after-free on remove + libnvdimm/namespace: Fix a potential NULL pointer dereference + HID: input: add mapping for Expose/Overview key + HID: input: add mapping for keyboard Brightness Up/Down/Toggle keys + HID: input: add mapping for "Toggle Display" key + libnvdimm/btt: Fix a kmemdup failure check + s390/dasd: Fix capacity calculation for large volumes + mac80211: fix unaligned access in mesh table hash function + mac80211: Increase MAX_MSG_LEN + mac80211: fix memory accounting with A-MSDU aggregation + nl80211: Add NL80211_FLAG_CLEAR_SKB flag for other NL commands + s390/3270: fix lockdep false positive on view->lock + clocksource/drivers/oxnas: Fix OX820 compatible + mISDN: Check address length before reading address family + s390/pkey: add one more argument space for debug feature entry + x86/reboot, efi: Use EFI reboot for Acer TravelMate X514-51T + KVM: fix spectrev1 gadgets + KVM: x86: avoid misreporting level-triggered irqs as edge-triggered in tracing + tools lib traceevent: Fix missing equality check for strcmp + mm: fix inactive list balancing between NUMA nodes and cgroups + init: initialize jump labels before command line option parsing + selftests: netfilter: check icmp pkttoobig errors are set as related + ipvs: do not schedule icmp errors from tunnels + netfilter: ctnetlink: don't use conntrack/expect object addresses as id + s390: ctcm: fix ctcm_new_device error return code + drm/sun4i: Set device driver data at bind time for use in unbind + gpu: ipu-v3: dp: fix CSC handling + drm/imx: don't skip DP channel disable for background plane + spi: Micrel eth switch: declare missing of table + spi: ST ST95HF NFC: declare missing of table + Input: synaptics-rmi4 - fix possible double free + MIPS: VDSO: Reduce VDSO_RANDOMIZE_SIZE to 64MB for 64bit + ima: open a new file instance if no read permissions + drm/i915: Disable LP3 watermarks on all SNB machines + net: stmmac: Move debugfs init/exit to ->probe()/->remove() + x86/vdso: Pass --eh-frame-hdr to the linker + mm/memory.c: fix modifying of page protection by insert_pfn() + net: fec: manage ahb clock in runtime pm + mlxsw: spectrum_switchdev: Add MDB entries in prepare phase + mlxsw: core: Do not use WQ_MEM_RECLAIM for EMAD workqueue + mlxsw: core: Do not use WQ_MEM_RECLAIM for mlxsw ordered workqueue + mlxsw: core: Do not use WQ_MEM_RECLAIM for mlxsw workqueue + NFC: nci: Add some bounds checking in nci_hci_cmd_received() + nfc: nci: Potential off by one in ->pipes[] array + x86/kprobes: Avoid kretprobe recursion bug + cw1200: fix missing unlock on error in cw1200_hw_scan() + mwl8k: Fix rate_idx underflow + rtlwifi: rtl8723ae: Fix missing break in switch statement + bonding: fix arp_validate toggling in active-backup mode + bridge: Fix error path for kobject_init_and_add() + dpaa_eth: fix SG frame cleanup + ipv4: Fix raw socket lookup for local traffic + net: dsa: Fix error cleanup path in dsa_init_module + net: ethernet: stmmac: dwmac-sun8i: enable support of unicast filtering + net: seeq: fix crash caused by not set dev.parent + net: ucc_geth - fix Oops when changing number of buffers in the ring + packet: Fix error path in packet_init + vlan: disable SIOCSHWTSTAMP in container + vrf: sit mtu should not be updated when vrf netdev is the link + tipc: fix hanging clients using poll with EPOLLOUT flag + drivers/virt/fsl_hypervisor.c: dereferencing error pointers in ioctl + drivers/virt/fsl_hypervisor.c: prevent integer overflow in ioctl + powerpc/powernv/idle: Restore IAMR after idle + powerpc/booke64: set RI in default MSR + platform/x86: dell-laptop: fix rfkill functionality + iio: adc: xilinx: fix potential use-after-free on probe + iio: adc: xilinx:
[Bug 1838575] Re: passthrough devices cause >17min boot delay
> > sudo perf record -a -F $((250*100)) -e cycles:u -- > > /usr/bin/qemu-system-x86_64 -name guest="guest" > > I instead attached perf to the qemu process after it was spawned by > libvirt so I didn't have to worry about producing a working qemu > cmdline. I let it run for several seconds while still in the paused > state. Sure! > > And check where we're spending so much time for the boot to happen. > > Note I'm using "cycles:u", getting only userland stack trace probes > > every (HZ*100),. > > This showed no samples - apparently all samples were kernel side. Either kernel or VMX/SVM mode. > > That might give us enough information. > > > > Would you mind opening a launchpad bug (can be private if you prefer) > > so Christian and I can take a look ? > > Sure: > https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1838575 Err, sorry to ask you this, but I'm getting magic/endian check errors on perf report, maybe something related to the arch and perf. Would you mind reporting to stdio and pasting into the case ? Are you using fully updated Eoan (userland/kernel) for everything ? (c)inaddy@temp:~/temp$ sudo /usr/lib/linux-tools/5.2.0-8-generic/perf report -f -v magic/endian check failed Tks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1838575 Title: passthrough devices cause >17min boot delay To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1838575/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1838575] Re: passthrough devices cause >17min boot delay
** Changed in: qemu (Ubuntu) Importance: Undecided => Medium ** Changed in: qemu (Ubuntu) Assignee: (unassigned) => Rafael David Tinoco (rafaeldtinoco) ** 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/1838575 Title: passthrough devices cause >17min boot delay To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1838575/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1835387] Re: bionic/linux-hwe-edge: 5.0.0-23.24~18.04.1 -proposed tracker
All tasks have been completed and the bug is being set to Fix Released ** Changed in: kernel-sru-workflow Status: In Progress => Fix Released ** Tags removed: kernel-release-tracking-bug-live -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1835387 Title: bionic/linux-hwe-edge: 5.0.0-23.24~18.04.1 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1835387/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1838577] [NEW] Default audio device changes on reboot; audio still outputs using my previously-selected device
Public bug reported: This is present in Ubuntu 18.04, 18.10, 19.04, and 19.10 daily build. It was not present in Ubuntu 16.04. I have a USB microphone which also appears to pulse as a speaker. Pulse keeps picking it as the default audio device. I can switch audio devices to my analog line out, which works as expected until I reboot. After reboot, my audio device switches back to the USB "speaker", and Gnome shell / Gnome settings volume control adjusts the USB speaker volume. Despite seeing the USB device as the current output device, I still hear sound from my line-out. In the interest of narrowing down this bug, I have found that disabling "module-switch-on-connect" fixes the problem (my line-out stays as the default audio device and I hear sound). ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: pulseaudio 1:12.2-2ubuntu3 ProcVersionSignature: Ubuntu 5.0.0-21.22-generic 5.0.15 Uname: Linux 5.0.0-21-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Jul 31 17:39:38 2019 InstallationDate: Installed on 2019-07-31 (0 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/07/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4207 dmi.board.asset.tag: Default string dmi.board.name: PRIME B350M-A dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4207:bd12/07/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEB350M-A:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic cosmic disco eoan ** Description changed: This is present in Ubuntu 18.04, 18.10, 19.04, and 19.10 daily build. It was not present in Ubuntu 16.04. I have a USB microphone which also appears to pulse as a speaker. Pulse keeps picking it as the default audio device. I can switch audio devices to my analog line out, which works as expected until I reboot. After reboot, my audio device switches back to the USB "speaker", and - volume control adjusts the USB speaker volume. Despite pulse seeing the - USB device as the current output device, I still hear sound from my - line-out. + Gnome shell / Gnome settings volume control adjusts the USB speaker + volume. Despite seeing the USB device as the current output device, I + still hear sound from my line-out. In the interest of narrowing down this bug, I have found that disabling "module-switch-on-connect" fixes the problem (my line-out stays as the default audio device and I hear sound). ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: pulseaudio 1:12.2-2ubuntu3 ProcVersionSignature: Ubuntu 5.0.0-21.22-generic 5.0.15 Uname: Linux 5.0.0-21-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Jul 31 17:39:38 2019 InstallationDate: Installed on 2019-07-31 (0 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) ProcEnviron: - TERM=xterm-256color - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=en_US.UTF-8 - SHELL=/bin/bash + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/07/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4207 dmi.board.asset.tag: Default string dmi.board.name: PRIME B350M-A dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4207:bd12/07/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEB350M-A:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1838577 Title: Default audio device changes on reboot; audio still outputs using my
[Bug 1838393] Re: bionic/linux-hwe: 5.0.0-24.25~18.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: New => Confirmed ** Tags added: block-proposed-bionic ** Tags added: block-proposed ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1838395 packages: main: linux-hwe meta: linux-meta-hwe signed: linux-signed-hwe - phase: Holding before Promote to Proposed - phase-changed: Tuesday, 30. July 2019 15:08 UTC + phase: Ready for Promote to Proposed + phase-changed: Wednesday, 31. July 2019 21:39 UTC reason: - promote-to-proposed: Holding -- master bug not ready for proposed + promote-to-proposed: Pending -- ready for review variant: debs -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1838393 Title: bionic/linux-hwe: 5.0.0-24.25~18.04.1 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1838393/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1838271] Re: disco/linux: 5.0.0-23.24 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-updates Status: In Progress => Fix Released ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1836856 (bionic/linux-oem-osp1), bug 1838270 (bionic/linux-hwe) derivatives: bug 1834884 (linux-raspi2), bug 1834891 (linux-gcp), bug 1834892 (linux-kvm), bug 1834894 (linux-snapdragon), bug 1835434 (linux-azure), bug 1837728 (linux-aws) -- swm properties -- boot-testing-requested: true bugs-spammed: true packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed - phase: Release - phase-changed: Wednesday, 31. July 2019 21:25 UTC + phase: Complete + phase-changed: Wednesday, 31. July 2019 21:36 UTC proposed-announcement-sent: true proposed-testing-requested: true - reason: - promote-to-updates: Ongoing -- packages not yet published trackers: bionic/linux-hwe: bug 1838270 disco/linux-aws: bug 1837728 variant: debs -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1838271 Title: disco/linux: 5.0.0-23.24 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1838271/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1838395] Re: disco/linux: 5.0.0-24.25 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: New => Confirmed ** Tags added: block-proposed-disco ** Tags added: block-proposed ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1838393 (bionic/linux-hwe), bug 1838398 (bionic/linux-oem-osp1) derivatives: bug 1837563 (linux-raspi2), bug 1837565 (linux-aws), bug 1837567 (linux-azure), bug 1837571 (linux-gcp), bug 1837572 (linux-kvm), bug 1837573 (linux-snapdragon) -- swm properties -- boot-testing-requested: true packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed - phase: Holding before Promote to Proposed - phase-changed: Tuesday, 30. July 2019 14:06 UTC + phase: Ready for Promote to Proposed + phase-changed: Wednesday, 31. July 2019 21:36 UTC reason: - promote-to-proposed: Holding -- another kernel is currently pending in Proposed + promote-to-proposed: Pending -- ready for review trackers: bionic/linux-hwe: bug 1838393 bionic/linux-oem-osp1: bug 1838398 disco/linux-aws: bug 1837565 disco/linux-azure: bug 1837567 disco/linux-gcp: bug 1837571 disco/linux-kvm: bug 1837572 disco/linux-raspi2: bug 1837563 disco/linux-snapdragon: bug 1837573 variant: debs -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1838395 Title: disco/linux: 5.0.0-24.25 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1838395/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1837563] Re: disco/linux-raspi2: 5.0.0-1014.14 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: New => Confirmed ** Tags added: block-proposed-disco ** Tags added: block-proposed ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1838395 packages: main: linux-raspi2 meta: linux-meta-raspi2 - phase: Holding before Promote to Proposed - phase-changed: Wednesday, 31. July 2019 04:30 UTC + phase: Ready for Promote to Proposed + phase-changed: Wednesday, 31. July 2019 21:37 UTC reason: - promote-to-proposed: Holding -- master bug not ready for proposed + promote-to-proposed: Pending -- ready for review variant: debs -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1837563 Title: disco/linux-raspi2: 5.0.0-1014.14 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1837563/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1838398] Re: bionic/linux-oem-osp1: 5.0.0-1017.19 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: New => Confirmed ** Tags added: block-proposed-bionic ** Tags added: block-proposed ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1838395 packages: main: linux-oem-osp1 meta: linux-meta-oem-osp1 signed: linux-signed-oem-osp1 - phase: Holding before Promote to Proposed - phase-changed: Wednesday, 31. July 2019 08:08 UTC + phase: Ready for Promote to Proposed + phase-changed: Wednesday, 31. July 2019 21:40 UTC reason: - promote-to-proposed: Holding -- master bug not ready for proposed + promote-to-proposed: Pending -- ready for review variant: debs -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1838398 Title: bionic/linux-oem-osp1: 5.0.0-1017.19 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1838398/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1838575] Re: passthrough devices cause >17min boot delay
** Attachment added: "sample xml w/ devices passed through" https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1838575/+attachment/5280232/+files/config5-new.xml -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1838575 Title: passthrough devices cause >17min boot delay To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1838575/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1838575] Re: passthrough devices cause >17min boot delay
Here's a perf report of a 'sudo perf record -p 6949 -a -F 25000 -e cycles', after libvirt spawned qemu w/ pid 6949. ** Attachment added: "perf.report" https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1838575/+attachment/5280233/+files/perf.report -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1838575 Title: passthrough devices cause >17min boot delay To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1838575/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1838575] [NEW] passthrough devices cause >17min boot delay
Public bug reported: Adding passthrough devices to a guest introduces a boot delay of > 17 minutes. During this time libvirt reports the guest to be "paused". The delay does not seem to scale with the # of hostdevs - that is, 1 hostdev causes about a 17min delay, while 16 only bumps that up to ~18min. Removing all hostdevs avoids the delay. ** Affects: qemu (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/1838575 Title: passthrough devices cause >17min boot delay To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1838575/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1838576] [NEW] Bionic update: upstream stable patchset 2019-07-31
Public bug reported: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: upstream stable patchset 2019-07-31 Ported from the following upstream stable releases: v4.14.120, v4.19.44, v4.14.121, v4.19.45, v4.14.122, v4.19.46 from git://git.kernel.org/ ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Affects: linux (Ubuntu Bionic) Importance: Undecided Assignee: Kamal Mostafa (kamalmostafa) Status: In Progress ** Tags: kernel-stable-tracking-bug ** Changed in: linux (Ubuntu) Status: New => Confirmed ** Tags added: kernel-stable-tracking-bug ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Description changed: + SRU Justification - SRU Justification + Impact: + The upstream process for stable tree updates is quite similar + in scope to the Ubuntu SRU process, e.g., each patch has to + demonstrably fix a bug, and each patch is vetted by upstream + by originating either directly from a mainline/stable Linux tree or + a minimally backported form of that patch. The following upstream + stable patches should be included in the Ubuntu kernel: - Impact: -The upstream process for stable tree updates is quite similar -in scope to the Ubuntu SRU process, e.g., each patch has to -demonstrably fix a bug, and each patch is vetted by upstream -by originating either directly from a mainline/stable Linux tree or -a minimally backported form of that patch. The following upstream -stable patches should be included in the Ubuntu kernel: + upstream stable patchset 2019-07-31 -upstream stable patchset 2019-07-31 -from git://git.kernel.org/ + Ported from the following upstream stable releases: + v4.14.120, v4.19.44, + v4.14.121, v4.19.45, + v4.14.122, v4.19.46 + + from git://git.kernel.org/ ** Changed in: linux (Ubuntu Bionic) Status: New => In Progress ** Changed in: linux (Ubuntu Bionic) Assignee: (unassigned) => Kamal Mostafa (kamalmostafa) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1838576 Title: Bionic update: upstream stable patchset 2019-07-31 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1838576/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1838271] Re: disco/linux: 5.0.0-23.24 -proposed tracker
This bug was fixed in the package linux - 5.0.0-23.24 --- linux (5.0.0-23.24) disco; urgency=medium * disco/linux: 5.0.0-23.24 -proposed tracker (LP: #1838271) * linux hwe i386 kernel 5.0.0-21.22~18.04.1 crashes on Lenovo x220 (LP: #1838115) - x86/mm: Check for pfn instead of page in vmalloc_sync_one() - x86/mm: Sync also unmappings in vmalloc_sync_all() - mm/vmalloc.c: add priority threshold to __purge_vmap_area_lazy() - mm/vmalloc: Sync unmappings in __purge_vmap_area_lazy() -- Stefan Bader Mon, 29 Jul 2019 16:49:23 +0200 ** Changed in: linux (Ubuntu Disco) 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/1838271 Title: disco/linux: 5.0.0-23.24 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1838271/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1838115] Re: linux hwe i386 kernel 5.0.0-21.22~18.04.1 crashes on Lenovo x220
This bug was fixed in the package linux - 5.0.0-23.24 --- linux (5.0.0-23.24) disco; urgency=medium * disco/linux: 5.0.0-23.24 -proposed tracker (LP: #1838271) * linux hwe i386 kernel 5.0.0-21.22~18.04.1 crashes on Lenovo x220 (LP: #1838115) - x86/mm: Check for pfn instead of page in vmalloc_sync_one() - x86/mm: Sync also unmappings in vmalloc_sync_all() - mm/vmalloc.c: add priority threshold to __purge_vmap_area_lazy() - mm/vmalloc: Sync unmappings in __purge_vmap_area_lazy() -- Stefan Bader Mon, 29 Jul 2019 16:49:23 +0200 ** Changed in: linux (Ubuntu Disco) 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/1838115 Title: linux hwe i386 kernel 5.0.0-21.22~18.04.1 crashes on Lenovo x220 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1838115/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1838271] Re: disco/linux: 5.0.0-23.24 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1836856 (bionic/linux-oem-osp1), bug 1838270 (bionic/linux-hwe) derivatives: bug 1834884 (linux-raspi2), bug 1834891 (linux-gcp), bug 1834892 (linux-kvm), bug 1834894 (linux-snapdragon), bug 1835434 (linux-azure), bug 1837728 (linux-aws) -- swm properties -- boot-testing-requested: true bugs-spammed: true packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed - phase: Ready for Release - phase-changed: Wednesday, 31. July 2019 17:30 UTC + phase: Release + phase-changed: Wednesday, 31. July 2019 21:25 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - promote-to-updates: Pending -- ready to copy + promote-to-updates: Ongoing -- packages not yet published trackers: bionic/linux-hwe: bug 1838270 disco/linux-aws: bug 1837728 variant: debs -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1838271 Title: disco/linux: 5.0.0-23.24 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1838271/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1838271] Re: disco/linux: 5.0.0-23.24 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-updates Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/promote-to-updates Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Andy Whitcroft (apw) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1838271 Title: disco/linux: 5.0.0-23.24 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1838271/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1835091] Re: subiquity crashes upon reusing failed to assemble raid member partition
** Merge proposal linked: https://code.launchpad.net/~raharper/curtin/+git/curtin/+merge/370843 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1835091 Title: subiquity crashes upon reusing failed to assemble raid member partition To manage notifications about this bug go to: https://bugs.launchpad.net/curtin/+bug/1835091/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1838370] Re: slapd segfault on filter parse error
** Tags added: bitesize -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to openldap in Ubuntu. https://bugs.launchpad.net/bugs/1838370 Title: slapd segfault on filter parse error To manage notifications about this bug go to: https://bugs.launchpad.net/openldap/+bug/1838370/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1838370] Re: slapd segfault on filter parse error
** Tags added: bitesize -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1838370 Title: slapd segfault on filter parse error To manage notifications about this bug go to: https://bugs.launchpad.net/openldap/+bug/1838370/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1815607] Re: lorder reports errors; for example, from mktemp
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: bsdmainutils (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/1815607 Title: lorder reports errors; for example, from mktemp To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bsdmainutils/+bug/1815607/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1838570] [NEW] [needs-packaging] ibus-avro
Public bug reported: ibus-avro is a port of the popular Avro Phonetic Bangla typing method to Linux. This software works as an Engine (plugin) of IBus and lets users type in English and on-the-fly transliterate them phonetically to Bangla. The package is proposed for Debian simultaneously wnpp bug: https://bugs.debian.org/931527 (in the NEW queue currently) The reason for proposing it here directly too is that I want to backport the package to the stable releases, and hope to be able to start that earlier this way. Once approved in Debian, autosync will be enabled. ** Affects: ubuntu Importance: Wishlist Assignee: Gunnar Hjalmarsson (gunnarhj) Status: In Progress ** Tags: needs-packaging -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1838570 Title: [needs-packaging] ibus-avro To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1838570/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1838113] Re: eoan/linux: 5.2.0-10.11 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: New => Fix Committed ** Tags added: block-proposed-eoan ** Tags added: block-proposed ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1838112 (bionic/linux-hwe-edge) -- swm properties -- boot-testing-requested: true packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed - phase: Holding before Promote to Proposed - phase-changed: Tuesday, 30. July 2019 19:46 UTC + phase: Promote to Proposed + phase-changed: Wednesday, 31. July 2019 20:56 UTC reason: - promote-to-proposed: Holding -- another kernel is currently pending in Proposed + promote-to-proposed: Ongoing -- package copied to Proposed signed:depwait trackers: bionic/linux-hwe-edge: bug 1838112 variant: debs -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1838113 Title: eoan/linux: 5.2.0-10.11 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1838113/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1837605] Re: xenial/linux-gcp: 4.15.0-1038.40~16.04.1 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow derivatives: bug 1837603 (gcp-kernel), bug 1837604 (gke-kernel) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1837608 packages: main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp phase: Promote to Proposed phase-changed: Wednesday, 31. July 2019 15:55 UTC reason: - promote-to-proposed: Pending -- package copied to Proposed signed:queued + promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror sync trackers: xenial/linux-gcp/gcp-kernel: bug 1837603 xenial/linux-gcp/gke-kernel: bug 1837604 variant: debs -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1837605 Title: xenial/linux-gcp: 4.15.0-1038.40~16.04.1 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1837605/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1838567] [NEW] GIMP crashes when showing and hiding a layer several times quickly
Public bug reported: Guidelines: - lubuntu 19.04 amd64 - GIMP 2.10.8-2 - I expect no crashes by these simple operation. - It freezes and crash GIMP Crash Bug Information: ``` GNU Image Manipulation Program version 2.10.8 git-describe: GIMP_2_10_6-294-ga967e8d2c2 C compiler: Using built-in specs. COLLECT_GCC=gcc COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/8/lto-wrapper OFFLOAD_TARGET_NAMES=nvptx-none OFFLOAD_TARGET_DEFAULT=1 Target: x86_64-linux-gnu Configured with: ../src/configure -v --with-pkgversion='Ubuntu 8.2.0-13ubuntu1' --with-bugurl=file:///usr/share/doc/gcc-8/README.Bugs --enable-languages=c,ada,c++,go,brig,d,fortran,objc,obj-c++ --prefix=/usr --with-gcc-major-version-only --program-suffix=-8 --program-prefix=x86_64-linux-gnu- --enable-shared --enable-linker-build-id --libexecdir=/usr/lib --without-included-gettext --enable-threads=posix --libdir=/usr/lib --enable-nls --enable-clocale=gnu --enable-libstdcxx-debug --enable-libstdcxx-time=yes --with-default-libstdcxx-abi=new --enable-gnu-unique-object --disable-vtable-verify --enable-libmpx --enable-plugin --enable-default-pie --with-system-zlib --with-target-system-zlib --enable-objc-gc=auto --enable-multiarch --disable-werror --with-arch-32=i686 --with-abi=m64 --with-multilib-list=m32,m64,mx32 --enable-multilib --with-tune=generic --enable-offload-targets=nvptx-none --without-cuda-driver --enable-checking=release --build=x86_64-linux-gnu --host=x86_64-linux-gnu --target=x86_64-linux-gnu Thread model: posix gcc version 8.2.0 (Ubuntu 8.2.0-13ubuntu1) using GEGL version 0.4.14 (compiled against version 0.4.12) using GLib version 2.60.4 (compiled against version 2.58.1) using GdkPixbuf version 2.38.1 (compiled against version 2.38.0) using GTK+ version 2.24.32 (compiled against version 2.24.32) using Pango version 1.42.3 (compiled against version 1.42.3) using Fontconfig version 2.13.1 (compiled against version 2.13.0) using Cairo version 1.16.0 (compiled against version 1.16.0) ``` > fatal error: Aborted Stack trace: ``` /lib/libgimpbase-2.0.so.0(gimp_stack_trace_print+0x397)[0x7f19648b48c7] gimp-2.10(+0xd14a0)[0x561d3c8444a0] gimp-2.10(+0xd18d8)[0x561d3c8448d8] gimp-2.10(+0xd2037)[0x561d3c845037] /lib/x86_64-linux-gnu/libpthread.so.0(+0x13f40)[0x7f1963de1f40] /lib/x86_64-linux-gnu/libc.so.6(gsignal+0xc7)[0x7f1963c24ed7] /lib/x86_64-linux-gnu/libc.so.6(abort+0x121)[0x7f1963c06535] /lib/x86_64-linux-gnu/libc.so.6(+0x2540f)[0x7f1963c0640f] /lib/x86_64-linux-gnu/libc.so.6(+0x35012)[0x7f1963c16012] /lib/x86_64-linux-gnu/libX11.so.6(+0x3d5db)[0x7f1963ade5db] /lib/x86_64-linux-gnu/libX11.so.6(+0x3d680)[0x7f1963ade680] /lib/x86_64-linux-gnu/libX11.so.6(_XEventsQueued+0x5d)[0x7f1963ade97d] /lib/x86_64-linux-gnu/libX11.so.6(XPending+0x57)[0x7f1963ad06d7] /lib/x86_64-linux-gnu/libgdk-x11-2.0.so.0(+0x589f5)[0x7f19649719f5] /lib/x86_64-linux-gnu/libglib-2.0.so.0(g_main_context_check+0x1d1)[0x7f1963f915d1] /lib/x86_64-linux-gnu/libglib-2.0.so.0(+0x4eba0)[0x7f1963f91ba0] /lib/x86_64-linux-gnu/libglib-2.0.so.0(g_main_loop_run+0xb2)[0x7f1963f91f82] gimp-2.10(app_run+0x357)[0x561d3c843cb7] gimp-2.10(main+0x395)[0x561d3c8435b5] /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xeb)[0x7f1963c07b6b] gimp-2.10(_start+0x2a)[0x561d3c84373a] ``` ** Affects: gimp (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1838567 Title: GIMP crashes when showing and hiding a layer several times quickly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gimp/+bug/1838567/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1838270] Re: bionic/linux-hwe: 5.0.0-23.24~18.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-updates Status: In Progress => Fix Released ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow derivatives: bug 1835387 (linux-hwe-edge) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1838271 packages: main: linux-hwe meta: linux-meta-hwe signed: linux-signed-hwe phase: Release phase-changed: Wednesday, 31. July 2019 20:20 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - promote-to-updates: Ongoing -- packages not yet published + kernel-sru-workflow: Stalled -- package promote-to-security status (Invalid) does + not match security-signoff status (Fix Released) trackers: bionic/linux-hwe-edge: bug 1835387 variant: debs -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1838270 Title: bionic/linux-hwe: 5.0.0-23.24~18.04.1 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1838270/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1838133] Re: realtek r8822be kernel module fails after update to linux kernel-headers 5.0.0-21
I have the same issue with 5.0.0-21 kernel update. Wireless card rtl8822be, this is bluetooth combo m.2 card. In Lenovo E585 laptop. I do not see any obvious errors, I can load rtwpci kernel modules, interface wlp4s0 is created, I scan with iw dev or iwlist and no networks are found. In Windows, the card works fine. I imagine rolling back to 5.0.0-20 will fix it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1838133 Title: realtek r8822be kernel module fails after update to linux kernel- headers 5.0.0-21 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1838133/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1835387] Re: bionic/linux-hwe-edge: 5.0.0-23.24~18.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-updates Status: In Progress => Fix Released ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1838270 packages: meta: linux-meta-hwe-edge - phase: Release - phase-changed: Wednesday, 31. July 2019 20:35 UTC + phase: Complete + phase-changed: Wednesday, 31. July 2019 20:42 UTC proposed-announcement-sent: true proposed-testing-requested: true - reason: - promote-to-updates: Ongoing -- packages not yet published variant: debs -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1835387 Title: bionic/linux-hwe-edge: 5.0.0-23.24~18.04.1 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1835387/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1818680] Re: booting should succeed even if vault is unavailable
** Tags added: uosci -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1818680 Title: booting should succeed even if vault is unavailable To manage notifications about this bug go to: https://bugs.launchpad.net/bionic-backports/+bug/1818680/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 395767] Re: Lyx does not support dark themes
In Ubuntu 18.04LTS you can install the "arc-theme" package that contains arc-dark theme, then you will have to install "qt5-style-plugins" and set Qt5 applications to use the Gtk+ 2 style by adding: echo "export QT_QPA_PLATFORMTHEME=gtk2" >> ~/.profile After that you have to logout and install a dark theme for LyX: https://github.com/joonro/LyX-Color-Schemes/blob/master/monokai Source: https://www.linuxuprising.com/2018/05/get-qt5-apps-to-use-native-gtk-style-in.html ** Attachment added: "LyX dark" https://bugs.launchpad.net/ubuntu/+source/lyx/+bug/395767/+attachment/5280231/+files/Captura%20de%202019-07-31%2022-32-38.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/395767 Title: Lyx does not support dark themes To manage notifications about this bug go to: https://bugs.launchpad.net/lyx/+bug/395767/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1835387] Re: bionic/linux-hwe-edge: 5.0.0-23.24~18.04.1 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1838270 packages: meta: linux-meta-hwe-edge - phase: Ready for Release - phase-changed: Wednesday, 31. July 2019 17:32 UTC + phase: Release + phase-changed: Wednesday, 31. July 2019 20:35 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - promote-to-updates: Pending -- ready to copy + promote-to-updates: Ongoing -- packages not yet published variant: debs -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1835387 Title: bionic/linux-hwe-edge: 5.0.0-23.24~18.04.1 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1835387/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1835387] Re: bionic/linux-hwe-edge: 5.0.0-23.24~18.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-updates Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/promote-to-updates Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Andy Whitcroft (apw) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1835387 Title: bionic/linux-hwe-edge: 5.0.0-23.24~18.04.1 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1835387/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1821927] Re: Systemd do not respawn sssd on failure
** Merge proposal linked: https://code.launchpad.net/~ahasenack/ubuntu/+source/sssd/+git/sssd/+merge/370825 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1821927 Title: Systemd do not respawn sssd on failure To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/1821927/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1775636] Re: sss_ssh_authorizedkeys fails with: Error looking up public keys when client cert present in IPA
Only xenial affected, adjusting bug tasks ** Also affects: sssd (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: sssd (Ubuntu Xenial) Status: New => Triaged ** Changed in: sssd (Ubuntu Xenial) Importance: Undecided => Low ** Changed in: sssd (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1775636 Title: sss_ssh_authorizedkeys fails with: Error looking up public keys when client cert present in IPA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/1775636/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
