[Bug 1850887] [NEW] Audio / Sound reverts to HDMI when power event occurs
Public bug reported: PulseAudio reverts the sound to HDMI all the time when a HDMI related power event occurs. That means, although I have set another USB sound device plugged in and set as default under sound settings, when an application like Kodi or the system shuts off the HDMI monitor and I reactivate the monitor, the sound is set to HDMI output again and again. That probably has to do with the fix to the reported Bug # 1711101 and definitely not happened at Ubuntu 19.04. I switched to Ubuntu 19.10 two days ago. Setting the USB device as default does not help, even when done by PulseAudio mixer (gui) and removing HDMI output from the alternatives option. Expected behavior: PulseAudio keeps the sound setting to the selected device Actual behavior: PulseAudio changes to HDMI at every HDMI power event Annoying manual workaround: Setting the desired Audio option on the control panel after every HDMI power event again ProblemType: Bug DistroRelease: Ubuntu 19.10 Component: pulseaudio Version: 1:13.0-1ubuntu1 ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: audio hdmi power pulseaudio sound -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1850887 Title: Audio / Sound reverts to HDMI when power event occurs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1850887/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1850886] [NEW] Auto-rotate is not working properly when system is booted up while not in its regular orientation
Public bug reported: [RELEASE VERSION] Description:Ubuntu 18.04.3 LTS Release:18.04 [PACKAGE VERSION] linux-oem: Installed: 4.15.0.1057.61 Candidate: 4.15.0.1057.61 Version table: *** 4.15.0.1057.61 500 500 http://jp.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 100 /var/lib/dpkg/status 4.15.0.1004.2 500 500 http://jp.archive.ubuntu.com/ubuntu bionic/main amd64 Packages [EXPECTED OUTPUT] Upon boot up with auto-rotation enabled, display should show the proper screen orientation of the system accordingly [ACTUAL OUTPUT] Auto-rotation is not working properly when system is booted up while not in its regular orientation [STEPS] 1. Make sure auto-rotation is enabled on the system 2. Before turning the system on, put it on tablet mode, with the inverted landscape rotation (the top part/the part with the camera is adjacent to the surface). The system should follow this orientation when the login screen appears. 3. Login to the system 4. Switch to the clam shell mode. The display suddenly becomes inverted/the opposite direction of the expected output. 5. Switch back to the tablet mode. The display also ends up being inverted/in the opposite direction of the expected output [REMARKS] *Using WHL *The system seems to be setting the orientation according to the orientation during boot up ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-oem 4.15.0.1057.61 ProcVersionSignature: Ubuntu 5.0.0-1024.27-oem-osp1 5.0.21 Uname: Linux 5.0.0-1024-oem-osp1 x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Nov 1 14:23:14 2019 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-sutton-bionic-amd64-20190722-12+sutton-dijkstra-bionic-amd64+iso InstallationDate: Installed on 2019-07-25 (98 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20190722-05:40 SourcePackage: linux-meta-oem UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-meta-oem (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic third-party-packages -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1850886 Title: Auto-rotate is not working properly when system is booted up while not in its regular orientation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta-oem/+bug/1850886/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1836858] Re: i915: Display flickers (monitor loses signal briefly) during "flickerfree" boot, while showing the BIOS logo on a black background
** Summary changed: - i915: Display flickers during "flickerfree" boot (BIOS logo on a black background) + i915: Display flickers (monitor loses signal briefly) during "flickerfree" boot, while showing the BIOS logo on a black background -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1836858 Title: i915: Display flickers (monitor loses signal briefly) during "flickerfree" boot, while showing the BIOS logo on a black background To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1836858/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1850535] Re: Ubuntu 19.10 gnome-shell crashes after changing keyboard
Uninstalling fcitx would solve the crashing issue, while _clutter_stage_queue_event: assertion 'CLUTTER_IS_STAGE (stage)' failed¨ still exists when switching keyboard. This means the crash is not wholly caused by gnome. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1850535 Title: Ubuntu 19.10 gnome-shell crashes after changing keyboard To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1850535/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1850874] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1850874/+attachment/5301937/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1850874 Title: gnome-shell 100% CPU usage on all cores when animated gif is displayed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1850874/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1850874] Re: gnome-shell 100% CPU usage on all cores when animated gif is displayed
apport information ** Tags added: apport-collected ** Description changed: This started to happen with Ubuntu 19.10. When an animated gif is displayed in a browser, gnome-shell begins using 100% CPU on all cores. To reproduce: 1) open Firefox, or Chromium 2) load an URL where an animated gif is displayed - you can also use this direct link to https://i.stack.imgur.com/h6viz.gif - 3) gnome-shell will start using 100% CPU on all cores (as long as - Firefox/Chromium window is in the foreground) + 3) gnome-shell will start using 100% CPU on all cores (as long as Firefox/Chromium window is in the foreground) + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu8.1 + Architecture: amd64 + DisplayManager: gdm3 + DistroRelease: Ubuntu 19.10 + GsettingsChanges: + + InstallationDate: Installed on 2019-05-12 (172 days ago) + InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) + Package: gnome-shell 3.34.1-1ubuntu1 + PackageArchitecture: amd64 + ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 + RelatedPackageVersions: mutter-common 3.34.1-1ubuntu1 + Tags: eoan + Uname: Linux 5.3.0-19-generic x86_64 + UpgradeStatus: Upgraded to eoan on 2019-10-16 (15 days ago) + UserGroups: + + _MarkForUpload: True ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1850874/+attachment/5301936/+files/Dependencies.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1850874 Title: gnome-shell 100% CPU usage on all cores when animated gif is displayed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1850874/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1850874] ShellJournal.txt
apport information ** Attachment added: "ShellJournal.txt" https://bugs.launchpad.net/bugs/1850874/+attachment/5301939/+files/ShellJournal.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1850874 Title: gnome-shell 100% CPU usage on all cores when animated gif is displayed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1850874/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1850874] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1850874/+attachment/5301938/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1850874 Title: gnome-shell 100% CPU usage on all cores when animated gif is displayed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1850874/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1850839] Re: mnemosyne chrashed when tried to start
Which version are you using? I think this should be fixed in the latest Mnemosyne release which you can download from Mnemosyne's website. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1850839 Title: mnemosyne chrashed when tried to start To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mnemosyne/+bug/1850839/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1850884] [NEW] My touchpad is not being detected at kernal level.
Public bug reported: I run the command- less /proc/bus/input/devices Nowhere in the output My touchpad was mentioned.Hence I am using mouse to click now and touchpad does not work. Here is the output of the above command look like this.This is a small piece of output. I: Bus=0011 Vendor=0001 Product=0001 Version=ab41 N: Name="AT Translated Set 2 keyboard" P: Phys=isa0060/serio0/input0 S: Sysfs=/devices/platform/i8042/serio0/input/input5 U: Uniq= H: Handlers=sysrq kbd event3 leds B: PROP=0 B: EV=120013 B: KEY=1100f02902000 8380307cf910f001 fedfffef fffe B: MSC=10 B: LED=7 I: Bus=0003 Vendor=3938 Product=1031 Version=0110 N: Name="MOSART Semi. 2.4G Wireless Mouse" P: Phys=usb-:00:14.0-2/input0 S: Sysfs=/devices/pci:00/:00:14.0/usb3/3-2/3-2:1.0/0003:3938:1031.0001/input/input6 U: Uniq= H: Handlers=mouse0 event4 B: PROP=0 B: EV=17 B: KEY=1f 0 0 0 0 B: REL=1943 B: MSC=10 This has happened after updating the ubuntu i suppose. Please fix this. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-5.0.0-32-generic 5.0.0-32.34~18.04.2 ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21 Uname: Linux 5.0.0-32-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.8 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Nov 1 10:20:53 2019 InstallationDate: Installed on 2019-04-26 (188 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) SourcePackage: linux-signed-hwe UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-signed-hwe (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/1850884 Title: My touchpad is not being detected at kernal level. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe/+bug/1850884/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1850535] Re: Ubuntu 19.10 gnome-shell crashes after changing keyboard
That crash is not related to this bug so should not be discussed here. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1850535 Title: Ubuntu 19.10 gnome-shell crashes after changing keyboard To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1850535/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1850833] Re: Changing text color in Thunderbird table will crash gnome desktop
*** This bug is a duplicate of bug 1849249 *** https://bugs.launchpad.net/bugs/1849249 Thanks. It seems to be bug 1849249 so let's track it there. ** This bug has been marked a duplicate of bug 1849249 gnome-shell crashed with SIGABRT: mutter:ERROR:../src/core/window.c:4841:set_workspace_state: assertion failed: (workspace == NULL) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1850833 Title: Changing text color in Thunderbird table will crash gnome desktop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1850833/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1850535] Re: Ubuntu 19.10 gnome-shell crashes after changing keyboard
Hi, I tried the given method (commenting things out), and the system captured a crash dump of fcitx. https://errors.ubuntu.com/oops/7ef8bffe-fc5f-11e9-b630-fa163e102db1 Some symptom showed that this has nothing to do with fcitx (Gnome dock and desktop is not displaying either), but I will try uninstalling fcitx and see if things work out. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1850535 Title: Ubuntu 19.10 gnome-shell crashes after changing keyboard To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1850535/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1850833] Re: Changing text color in Thunderbird table will crash gnome desktop
Hi: I had to use step 3 and the new bug report is here: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1850881 Now, there are a number of (IMHO) really weird things that also happened in this round of reproductions: After reproducing the crash, I had these crash files: -rw-r- 1 jagosta whoopsie 193242154 Oct 31 21:43 _opt_google_chrome_chrome.1000.crash -rw-r- 1 jagosta whoopsie 0 Oct 31 21:51 _usr_bin_gnome-shell.1000.crash So, the gnome crash file was empty this time, but there was also a chrome crash file, so I tried running `ubuntu-bug` on the chrome crash file. When I did this it stated that it failed to generate a report because google-chrome was out of date and needed to be updated. So, I updated `google-chrome-stable (78.0.3904.87-1) to (78.0.3904.70-1)`, and then I tried to reproduce the bug. This time, the gnome window manager appeared to crash and then reset -- so I did not lose the window manager. But, Chrome and Thunderbird both crashed. I was left with these crash files: -rw-r- 1 jagosta whoopsie 38273264 Oct 31 22:02 _usr_bin_gnome-shell.1000.crash -rw-r--r-- 1 jagosta whoopsie 0 Oct 31 22:02 _usr_bin_gnome-shell.1000.upload -rw--- 1 whoopsie whoopsie37 Oct 31 22:02 _usr_bin_gnome-shell.1000.uploaded Bug # 1850881 was submitted for this gnome-shell crash file. I am really curious how updating chrome is impactign the behavior of both Thunderbird and Gnome. ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1850833 Title: Changing text color in Thunderbird table will crash gnome desktop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1850833/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1842161] Re: Some code accessed the property 'discreteGpuAvailable' on the module 'appDisplay'.
[Expired for gnome-shell (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gnome-shell (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/1842161 Title: Some code accessed the property 'discreteGpuAvailable' on the module 'appDisplay'. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1842161/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1842213] Re: Unable to reinstall Ubuntu 19.04
[Expired for ubiquity (Ubuntu) because there has been no activity for 60 days.] ** Changed in: ubiquity (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/1842213 Title: Unable to reinstall Ubuntu 19.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1842213/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1835669] Re: OBS-studio returns OpenGL error with NVIDIA window capture mode
[Expired for mutter (Ubuntu) because there has been no activity for 60 days.] ** Changed in: mutter (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/1835669 Title: OBS-studio returns OpenGL error with NVIDIA window capture mode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1835669/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1309076] Re: Chromium-custom title bar corrupt after maximize
I'm still seeing this behaviour on 18.04 LTS in both chromium and google-chrome. To workaround the issue, visit chrome://flags/ and search for "partial". An option called "Partial swap" should appear, with a flag called "#ui- disable-partial-swap". Set the associated dropdown to say "Disabled". Then press "Restart" and let the browser restart itself. Then visit chrome://gpu/ and verify that the last item in the first table under "Version Information" is "Command Line", and than "--ui-disable-partial- swap" appears in the list of commandline options. For me this doesn't fix 100% of the problem, but makes it much better -- when maximizing the browser window, there isn't garbage at the top of the window. On restoring the window, the problem (or a similar problem) is still there, but simply mousing over it makes it go away; unlike before, I don't need to run the mouse over sections of the window trying to get it to repaint the whole width of the corrput area. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1309076 Title: Chromium-custom title bar corrupt after maximize To manage notifications about this bug go to: https://bugs.launchpad.net/chromium-browser/+bug/1309076/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1850881] Re: gnome-shell crashed with SIGABRT in __GI_raise()
*** This bug is a duplicate of bug 1849249 *** https://bugs.launchpad.net/bugs/1849249 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1849249, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1850881/+attachment/5301919/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1850881/+attachment/5301921/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1850881/+attachment/5301925/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1850881/+attachment/5301926/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1850881/+attachment/5301927/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1850881/+attachment/5301929/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1850881/+attachment/5301930/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1849249 gnome-shell crashed with SIGABRT: mutter:ERROR:../src/core/window.c:4841:set_workspace_state: assertion failed: (workspace == NULL) ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1850881 Title: gnome-shell crashed with SIGABRT in __GI_raise() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1850881/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849855] Re: bionic/linux: 4.15.0-68.77 -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 bugs-spammed: true packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Testing phase-changed: Tuesday, 29. October 2019 13:37 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress certification-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-aws: bug 1849016 bionic/linux-fips: bug 1849023 bionic/linux-gke-4.15: bug 1849018 bionic/linux-ibm-gt: bug 1849020 bionic/linux-kvm: bug 1849019 - bionic/linux-oem: bug 1849012, bug 1850799 + bionic/linux-oem: bug 1850799, bug 1849012 bionic/linux-oracle: bug 1849022 bionic/linux-raspi2: bug 1849008 bionic/linux-snapdragon: bug 1849011 bionic/linux/pc-kernel: bug 1849852 bionic/linux/pc-lowlatency-kernel: bug 1849853 unknown/unknown: bug 1849854 xenial/linux-azure: bug 1849027 xenial/linux-gcp: bug 1849031 xenial/linux-hwe: bug 1849854 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/1849855 Title: bionic/linux: 4.15.0-68.77 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1849855/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1835737] Autopkgtest regression report (python3-stdlib-extensions/3.6.9-1~18.04)
All autopkgtests for the newly accepted python3-stdlib-extensions (3.6.9-1~18.04) for bionic have finished running. The following regressions have been reported in tests triggered by the package: yapf/0.20.1-1ubuntu1 (ppc64el) python-virtualenv/unknown (armhf) python-future/unknown (armhf) pyfai/0.15.0+dfsg1-1 (i386) python-ltfatpy/1.0.12-1 (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/bionic/update_excuses.html#python3-stdlib-extensions [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions 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/1835737 Title: SRU: backport Python 3.8 to bionic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3-stdlib-extensions/+bug/1835737/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1805686] Re: maxima-doc broken in bionic
Confirmed fixed in eaon, and perhaps earlier. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1805686 Title: maxima-doc broken in bionic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maxima/+bug/1805686/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1816396] Re: Starting snap from the after-install notification fails
** Changed in: gnome-software (Ubuntu) Status: Triaged => Fix Committed ** Changed in: gnome-software (Ubuntu Disco) Status: Triaged => Won't Fix ** Also affects: gnome-software (Ubuntu Eoan) Importance: Undecided Status: New ** Changed in: gnome-software (Ubuntu Eoan) Status: New => Triaged ** Changed in: gnome-software (Ubuntu Eoan) 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/1816396 Title: Starting snap from the after-install notification fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1816396/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1815723] Re: Segmentation fault (core dumped)
*** This bug is a duplicate of bug 1814949 *** https://bugs.launchpad.net/bugs/1814949 I had the same issue. Following reset command solved the problem:- dconf reset -f /org/gnome/control-center/ Hope it helps someone looking for the solution. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1815723 Title: Segmentation fault (core dumped) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1815723/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1805686] Re: maxima-doc broken in bionic
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: maxima (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/1805686 Title: maxima-doc broken in bionic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maxima/+bug/1805686/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1850874] Re: gnome-shell 100% CPU usage on all cores when animated gif is displayed
Wow, yes. That is unusual. Multiple threads exist in gnome-shell but they're pretty well hidden from the main code, mostly handling asynchronous IO etc... Next we need to see more information about the machine. Please run this command to send it automatically: apport-collect 1850874 ** No longer affects: mutter (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1850874 Title: gnome-shell 100% CPU usage on all cores when animated gif is displayed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1850874/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1844799] Re: Use new snap banner format
** Changed in: gnome-software (Ubuntu) Status: Triaged => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1844799 Title: Use new snap banner format To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1844799/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1846940]
Seems to be special stuff with controls - sigh. When breaking in svx\source\sdr\contact\objectcontactofpageview.cxx:290 in line pProcessor2D->process(xPrimitiveSequence); it can be seen that the ViewInformation2D from *this and at the processor is the same, while later in LazyControlCreationPrimitive2D::get2DDecomposition it is *different*. This is because the processed SeqOfPrim modifies it - in VclProcessor2D::RenderTransformPrimitive2D. This means the ControlPrimitive itself contains the offset (in my local example '30' which leads to a pixel offset of 1.0889). Forcing this to zero silences the repaint. Thus the question is: Who and why does someone create a TransformPrimitive2D? There are probably good reasons, so maybe we get a principal problem here...? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1846940 Title: [upstream] Loop in libreoffice-calc when scrolling to top of spreadsheet To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1846940/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1846940]
In adjustControlGeometry_throw aViewTranslate is sometimes *not* zero, but has some values. Thi seems to be the reason for the offsets - tried to hunt down where this comes from, but hard to find - about 25 stack levels involved... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1846940 Title: [upstream] Loop in libreoffice-calc when scrolling to top of spreadsheet To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1846940/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1846940]
I think that's I have de same problem with this version : Version: 6.4.0.0.alpha1 Build ID: cc57df8f942f239d29cb575ea5a7cb01405db787 Threads CPU : 4; OS : Linux 5.3; UI Render : par défaut; VCL: gtk3; Locale : fr-FR (fr_FR.UTF-8); Langue IHM : fr-FR Calc: threaded I can use LibO 6.3 because the CPU up to 100% when I use my sheet with macro. LibO 6.4 have the same problem. The file Xray have this problem. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1846940 Title: [upstream] Loop in libreoffice-calc when scrolling to top of spreadsheet To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1846940/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1844799] Re: Use new snap banner format
** Changed in: gnome-software (Ubuntu Disco) Status: Triaged => Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1844799 Title: Use new snap banner format To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1844799/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1850874] Re: gnome-shell 100% CPU usage on all cores when animated gif is displayed
** Attachment added: "gnome-shell threads" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1850874/+attachment/5301916/+files/Screenshot_20191101_115659.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1850874 Title: gnome-shell 100% CPU usage on all cores when animated gif is displayed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1850874/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1850874] Re: gnome-shell 100% CPU usage on all cores when animated gif is displayed
In "ps -eLf": tomasz1410 1265 1410 1 10 Oct31 ?00:33:23 /usr/bin/gnome-shell tomasz1410 1265 1421 0 10 Oct31 ?00:00:00 /usr/bin/gnome-shell tomasz1410 1265 1423 0 10 Oct31 ?00:00:02 /usr/bin/gnome-shell tomasz1410 1265 1424 0 10 Oct31 ?00:00:00 /usr/bin/gnome-shell tomasz1410 1265 1425 7 10 Oct31 ?02:33:40 /usr/bin/gnome-shell tomasz1410 1265 1426 7 10 Oct31 ?02:32:22 /usr/bin/gnome-shell tomasz1410 1265 1427 7 10 Oct31 ?02:32:50 /usr/bin/gnome-shell tomasz1410 1265 1434 0 10 Oct31 ?00:00:02 /usr/bin/gnome-shell tomasz1410 1265 1435 0 10 Oct31 ?00:00:02 /usr/bin/gnome-shell tomasz1410 1265 1436 0 10 Oct31 ?00:00:02 /usr/bin/gnome-shell So it's definitely using multiple threads. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1850874 Title: gnome-shell 100% CPU usage on all cores when animated gif is displayed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1850874/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1850874] Re: gnome-shell 100% CPU usage on all cores when animated gif is displayed
Hmm, gnome-shell is mostly single threaded so it shouldn't be able to use "all cores". It should saturate only one core at most. Please provide a screenshot of 'top' running in a Terminal window, showing that gnome-shell (or anything) is using the CPU. ** Tags added: eoan performance ** Also affects: mutter (Ubuntu) Importance: Undecided Status: New ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete ** Changed in: mutter (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1850874 Title: gnome-shell 100% CPU usage on all cores when animated gif is displayed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1850874/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1850806] Re: Ubuntu Software Centre (gnome-software) search function semi-broken
** Package changed: pulseaudio (Ubuntu) => gnome-software (Ubuntu) ** 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/1850806 Title: Ubuntu Software Centre (gnome-software) search function semi-broken To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1850806/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1850766] Re: Bluetooth headset selected as default sound output, yet sound outputs to laptop speakers
This kind of problem is becoming common enough that we should also check if it's a GUI issue in gnome-control-center in how it communicates with PulseAudio. ** Also affects: gnome-control-center (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/1850766 Title: Bluetooth headset selected as default sound output, yet sound outputs to laptop speakers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1850766/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1850782] Re: Video display very slow, framerate dropped, slowing computer
** Package changed: xorg (Ubuntu) => ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1850782 Title: Video display very slow, framerate dropped, slowing computer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1850782/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1850805] Re: PulseAudio resets output device to RX 580 HDMI every reboot
*** This bug is a duplicate of bug 1847570 *** https://bugs.launchpad.net/bugs/1847570 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1847570, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** This bug has been marked a duplicate of bug 1847570 PulseAudio automatically switches to HDMI sound output on login -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1850805 Title: PulseAudio resets output device to RX 580 HDMI every reboot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1850805/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1850833] Re: Changing text color in Thunderbird table will crash gnome desktop
Thank you for taking the time to report this bug and helping to make Ubuntu better. It sounds like some part of the system has crashed. To help us find the cause of the crash please follow these steps: 1. Look in /var/crash for crash files and if found run: ubuntu-bug YOURFILE.crash Then tell us the ID of the newly-created bug. 2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us. 3. If step 2 also failed then apply the workaround from bug 994921, reboot, reproduce the crash, and retry step 1. Please take care to avoid attaching .crash files to bugs as we are unable to process them as file attachments. It would also be a security risk for yourself. ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1850833 Title: Changing text color in Thunderbird table will crash gnome desktop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1850833/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1850727] Re: [nvidia] Let GDM timeout and it changes to a blank screen where there is no way to recover
Thanks. Confirmed by bug 1841679. Also I too vaguely recall seeing similar problems in the past when testing Nvidia, that it didn't reliably recover from the screensaver. ** Summary changed: - Let GDM timeout and it changes to a blank screen where there is no way to recover + [nvidia] Let GDM timeout and it changes to a blank screen where there is no way to recover ** Changed in: gdm3 (Ubuntu) Status: Incomplete => Confirmed ** Tags added: bionic nvidia -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1850727 Title: [nvidia] Let GDM timeout and it changes to a blank screen where there is no way to recover To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1850727/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1850727] Re: [nvidia] Let GDM timeout and it changes to a blank screen where there is no way to recover
What version of the Nvidia driver are you using that has the problem? It might help if you just run this command to automatically attach more information: apport-collect 1850727 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1850727 Title: [nvidia] Let GDM timeout and it changes to a blank screen where there is no way to recover To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1850727/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849917] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1849917 Title: [iwlwifi] Repeated kernel crashes in iwl_mvm_async_handlers_wk cause GUI stuttering in kernel 5.3 (but 5.0 has no problem) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1849917/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1850668] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1850668 Title: Kernel repeatedly logs "ima: Error Communicating to TPM chip" and boots slowly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1850668/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1848703] Re: Raspberry Pi 4 - USB Bus not detecting any devices
*** This bug is a duplicate of bug 1848790 *** https://bugs.launchpad.net/bugs/1848790 We have a bug to track the enabling of v3d.ko https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1850876 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1848703 Title: Raspberry Pi 4 - USB Bus not detecting any devices To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1848703/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1850668] Re: Kernel repeatedly logs "ima: Error Communicating to TPM chip" and boots slowly
** Summary changed: - No conozco el error + Kernel repeatedly logs "ima: Error Communicating to TPM chip" and boots slowly ** Package changed: ubuntu => linux (Ubuntu) ** Changed in: linux (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1850668 Title: Kernel repeatedly logs "ima: Error Communicating to TPM chip" and boots slowly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1850668/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1850201] Re: Memory usage grows when locking/unlocking the screen
gnome-shell (via gjs and mozjs) actually doesn't free memory immediately when JavaScript objects get deleted. It defers the garbage collection until more stress (more memory use) is put on the system. What this means is even without any leaks it will appear to grow for some period of time before shrinking again. So you might have a leak here, but also it will look like it's leaking even when it's not in the long term :( -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1850201 Title: Memory usage grows when locking/unlocking the screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1850201/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1850876] [NEW] CONFIG_DRＭ_V3D is disabled for linux-raspi2 of eoan
Public bug reported: We enabled DRM_VC4 in the linux-raspi2 of eoan, but disabled the DRM_V3D. In fact the DRM_V3D is crucial for graphical applications (such as ubuntu-desktop :) as it removes the graphical overhead from the cpu to the gpu, making the applications work much faster. Please refer to https://bugs.launchpad.net/ubuntu/+source/linux- raspi2/+bug/1848703/comments/32 ** Affects: linux-raspi2 (Ubuntu) Importance: Critical Assignee: Hui Wang (hui.wang) Status: New ** Changed in: linux-raspi2 (Ubuntu) Assignee: (unassigned) => Hui Wang (hui.wang) ** Changed in: linux-raspi2 (Ubuntu) Importance: Undecided => Critical -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1850876 Title: CONFIG_DRＭ_V3D is disabled for linux-raspi2 of eoan To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1850876/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1850103] Re: gnome-tweak-tool window keeps flickering on cursor hovering [Intel Penryn: Core 2 T6600]
*** This bug is a duplicate of bug 1847524 *** https://bugs.launchpad.net/bugs/1847524 It looks like a couple of people have reported these issues already so let's use bug 1847524. ** No longer affects: mesa (Ubuntu) ** No longer affects: mutter (Ubuntu) ** Summary changed: - gnome-tweak-tool window keeps flickering on cursor hovering [Intel Penryn: Core 2 T6600] + gnome-tweak-tool window keeps flickering on cursor hovering ** Changed in: gnome-tweaks (Ubuntu) Status: New => Confirmed ** Changed in: gtk+3.0 (Ubuntu) Status: New => Confirmed ** This bug has been marked a duplicate of bug 1847524 Black titlebar (CSD) in Tweak Tool, flickering -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1850103 Title: gnome-tweak-tool window keeps flickering on cursor hovering To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-tweaks/+bug/1850103/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849662] Re: window title bar buttons randomly disappear
*** This bug is a duplicate of bug 1847524 *** https://bugs.launchpad.net/bugs/1847524 ** This bug has been marked a duplicate of bug 1847524 Black titlebar (CSD) in Tweak Tool, flickering -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1849662 Title: window title bar buttons randomly disappear To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-tweaks/+bug/1849662/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1850874] [NEW] gnome-shell 100% CPU usage on all cores when animated gif is displayed
Public bug reported: This started to happen with Ubuntu 19.10. When an animated gif is displayed in a browser, gnome-shell begins using 100% CPU on all cores. To reproduce: 1) open Firefox, or Chromium 2) load an URL where an animated gif is displayed - you can also use this direct link to https://i.stack.imgur.com/h6viz.gif 3) gnome-shell will start using 100% CPU on all cores (as long as Firefox/Chromium window is in the foreground) ** Affects: gnome-shell (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/1850874 Title: gnome-shell 100% CPU usage on all cores when animated gif is displayed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1850874/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1850775] Re: DNS info is not loaded by dhclient
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: network-manager (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/1850775 Title: DNS info is not loaded by dhclient To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1850775/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1783961] Re: CONFIG_KVM is disabled for linux-raspi2 (aarch64 and armhf)
** Summary changed: - CONFIG_KVM is disabled for linux-raspi2 (aarch64) + CONFIG_KVM is disabled for linux-raspi2 (aarch64 and armhf) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1783961 Title: CONFIG_KVM is disabled for linux-raspi2 (aarch64 and armhf) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1783961/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849965] Re: I got stuck in a Login-Loop. The solution with the .Xauthority permission would not fix it. Next i read about a lightdm bug. Since new ubuntu is using not lightdm but gdm3 i sudo apt
*** This bug is a duplicate of bug 1845801 *** https://bugs.launchpad.net/bugs/1845801 This sounds like bug 1845801 so we should probably treat it as a duplicate of that unless proven otherwise. ** This bug has been marked a duplicate of bug 1845801 [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1849965 Title: I got stuck in a Login-Loop. The solution with the .Xauthority permission would not fix it. Next i read about a lightdm bug. Since new ubuntu is using not lightdm but gdm3 i sudo apt-get purge gdm3 . Then reinstalled. After that i could login successfully. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1849965/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849917] Re: [iwlwifi] Repeated kernel crashes in iwl_mvm_async_handlers_wk cause GUI stuttering in kernel 5.3 (but 5.0 has no problem)
** Summary changed: - [iwlwifi] Repeated kernel crashes in iwl_mvm_async_handlers_wk cause GUI stuttering + [iwlwifi] Repeated kernel crashes in iwl_mvm_async_handlers_wk cause GUI stuttering in kernel 5.3 (but 5.0 has no problem) ** Changed in: linux (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1849917 Title: [iwlwifi] Repeated kernel crashes in iwl_mvm_async_handlers_wk cause GUI stuttering in kernel 5.3 (but 5.0 has no problem) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1849917/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849669] Re: do-release-upgrade (19.04 -> 19.10) aborts
apport-collect 1849669 says the below... "You are not the reported or subscriber of this problem report, or the report is a duplicate or already closed. Please create a new report using apport-bug" ** Attachment added: "Screenshot from 2019-11-01 07-26-19.png" https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1849669/+attachment/5301910/+files/Screenshot%20from%202019-11-01%2007-26-19.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1849669 Title: do-release-upgrade (19.04 -> 19.10) aborts To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1849669/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849669] Re: do-release-upgrade (19.04 -> 19.10) aborts
i some how upgraded with reinstalling all *ubuntu-desktop versions and reinstalling gdm3/lightdm/python3 etc.. which one exactly worked.. i did't know.. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1849669 Title: do-release-upgrade (19.04 -> 19.10) aborts To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1849669/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1681839] Re: libvirt: blockcommit fails - disk not ready for pivot yet
Attached is the debdiff for xenial to fix this issue. I was not sure if the patches in debian/patches should be placed in the debian/patches/ubuntu directory or not, so I left them outside. Feel free to move them if necessary. ** Patch added: "libvirt debdiff for xenial" https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1681839/+attachment/5301911/+files/lp1681839_xenial.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1681839 Title: libvirt: blockcommit fails - disk not ready for pivot yet To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1681839/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1850762] Re: stub-resolver no longer optional, systemd dns broken
On Thu, 31 Oct 2019 at 12:40, ts <1850...@bugs.launchpad.net> wrote: > > This was a problem before, I fixed it unlinking /run/systemd/stub- > resolv.conf and linking /run/systemd/resolv.conf to /etc/ > Neither of the paths mentioned are correct... did you mean one of: /run/systemd/resolve/stub-resolv.conf /run/systemd/resolve/resolv.conf Both files should still be available, and usable as providers of /etc/resolv.conf -- Regards, Dimitri. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1850762 Title: stub-resolver no longer optional, systemd dns broken To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1850762/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1850871] Re: Installation crashes
Thank you for taking the time to report this issue and helping to make Ubuntu better. This package failure looks like it was caused by corrupted install media, or device failure. eg. look in the logs and you'll see messages like these :- Nov 1 00:28:57 ubuntu kernel: [ 20.074008] SQUASHFS error: zlib decompression failed, data probably corrupt Nov 1 00:28:57 ubuntu kernel: [ 20.074011] SQUASHFS error: squashfs_read_data failed to read block 0x6cf7df72 Examining the information you have given us, this does not appear to be a useful bug report so I am closing it, as it appears to be a faulty device (or bad write-to-device). If you believe I'm in error, please leave a comment explaining why and change the status back to 'New'. I suggest you verify your ISO download, and use the 'check disc for defects' option to validate your media before install to ensure a good download & write. Possible useful : https://tutorials.ubuntu.com/tutorial/tutorial-how-to- verify-ubuntu#0 and https://help.ubuntu.com/community/Installation/CDIntegrityCheck ** Changed in: ubiquity (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1850871 Title: Installation crashes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1850871/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1850746] Re: mythtv-backend-setup fails to add user to group mythtv under XFCE
Hi @0123peter The `apt source` command I used is documented in `man apt-get`, ie. "source causes apt-get to fetch source packages. APT will examine the available packages to decide which source package to fetch. It will then find and download into the current directory the newest available version...". My fingers just typed `apt` that time instead of `apt-get` (`apt` knows how to deal with many `apt-get` commands). Your sources.list also need to have "deb-src" lines present so source can be found & downloaded. If you need help with it, I'd suggest looking at https://discourse.ubuntu.com/t/finding-help/712 which lists many support options. I'll also give the `mythtv` devs/maintainers time to deal with the issue first. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1850746 Title: mythtv-backend-setup fails to add user to group mythtv under XFCE To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mythtv/+bug/1850746/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1850872] [NEW] When upgrading from 19.04 to 19.10 with ZFS Root Pool, Upgrader removed zfsutils-linux
Public bug reported: I just upgraded from 18.10 to 19.04 and then to 19.10. I have had ZFS installed in this machine for years. My Root pool is on LUKS encrypted SSD's which are morrored by ZFS. The upgrade from 18.10 to 19.04 worked as expected with no errors. And I was able to reboot, unlock the disks and boot ubuntu 19.04 fine. When i then did the upgrade to 19.10 using do-release-upgrade, I got errors installing grub, the 5.3 kernel and friendly-recovery They reported that they could not find my root pool. I did not reboot after the upgrade, and tried to run zpool to see if there was any issue and found zpool was not installed after the do- release-upgrade. It WAS installed prior to running do-release-upgrade. So do-release-upgrade did not upgrade my previous zfsutils-linux package, it seems to have removed it. Without rebooting, i ran: sudo apt install zfsutils-linux zfs-initramfs zfs-zed All of these packages were missing, and they installed correctly. strangely however the zfs-dkms package was upgraded correctly and still installed. This caused the initramfs to be rebuilt, and grub to report no more errors, fixing the issue for me. ** Affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: New ** Tags: do-release-upgrade -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1850872 Title: When upgrading from 19.04 to 19.10 with ZFS Root Pool, Upgrader removed zfsutils-linux To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1850872/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1850871] [NEW] Installation crashes
Public bug reported: Don't know much, can't seem to install with live usb ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubiquity 18.04.14.6 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CasperVersion: 1.394 CurrentDesktop: ubuntu:GNOME Date: Fri Nov 1 01:03:58 2019 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed boot=casper only-ubiquity quiet splash --- LiveMediaBuild: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcEnviron: LANGUAGE=en_US.UTF-8 PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 LC_NUMERIC=C.UTF-8 SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ubiquity-18.04.14.6 ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1850871 Title: Installation crashes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1850871/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Mythbuntu-bugs] [Bug 1850746] Re: mythtv-backend-setup fails to add user to group mythtv under XFCE
Tickets for this should probably be forwarded upstream, hopefully with a patch. As it stands now, there aren't much eyes on this package and I don't have a way to test this anymore as I don't use MythTV nor Ubuntu. On Thu, Oct 31, 2019 at 4:55 PM Peter D. <1850...@bugs.launchpad.net> wrote: > Sorry if I got a bit excited. > > On a fresh install of Xubuntu, Mythtv backend setup does not work. > > If it worked, then when it was first run it would add the user to the > group "mythtv", something that requires root access. My guess is that > long ago a pop up box would prompt the user for their password before > continuing. > > The grep above revels multiple places where gksu is expected to exist. > Because gksu has been removed from the distribution each of these lines > is a bug that leaves a variable empty. I don't know what the correct > fix is. It seems a bit to demanding to expect the end user edit > /etc/group in a terminal. > > The man page for apt does not mention "source", is that documented > anywhere? I got a "permission denied". > > kdebase-bin seems to be an alternative to gksu it does not have an > installation candidate either. > > There is a way to do it, gpated has a pop up that prompts for a > password. > > -- > You received this bug notification because you are a member of Mythbuntu > Bug Team, which is subscribed to mythtv in Ubuntu. > https://bugs.launchpad.net/bugs/1850746 > > Title: > mythtv-backend-setup fails to add user to group mythtv under XFCE > > Status in mythtv package in Ubuntu: > New > > Bug description: > Running Mythtv-backend-setup from the XFCE menu looks like it is > adding the user to the group "mythtv", but does not. The user has to > add himself manually, either by editing /etc/groups or with adduser > `whoami` mythtv. > > The meta package is mythtv. > The package is mythtv-backend. > The file is called /usr/bin/mythtv-setup. > There is a call to check_groups, which is in > /usr/share/mythtv/dialogue_functions.sh > It has the line; > $SU_TYPE adduser ... > Su type seems to be "gksu" for XFCE and Gnome. > > psd@EE:/usr/share/mythtv$ sudo apt-get install gksu > Reading package lists... Done > Building dependency tree > Reading state information... Done > Package gksu is not available, but is referred to by another package. > This may mean that the package is missing, has been obsoleted, or > is only available from another source > > E: Package 'gksu' has no installation candidate > > The bug also exists in older versions of Xubuntu; bionic, disco, > probably more. I am not sure about other desktops. > > ProblemType: Bug > DistroRelease: Ubuntu 19.10 > Package: mythtv-backend 2:30.0+fixes.20190817.5cde0578d8-0ubuntu1 > ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 > Uname: Linux 5.3.0-19-generic x86_64 > ApportVersion: 2.20.11-0ubuntu8.1 > Architecture: amd64 > CurrentDesktop: XFCE > Date: Thu Oct 31 15:36:16 2019 > InstallationDate: Installed on 2019-10-21 (9 days ago) > InstallationMedia: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) > Installed_mythtv_dbg: 2:30.0+fixes.20190817.5cde0578d8-0ubuntu1 > SourcePackage: mythtv > UpgradeStatus: No upgrade log present (probably fresh install) > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/mythtv/+bug/1850746/+subscriptions > > ___ > Mailing list: https://launchpad.net/~mythbuntu-bugs > Post to : mythbuntu-b...@lists.launchpad.net > Unsubscribe : https://launchpad.net/~mythbuntu-bugs > More help : https://help.launchpad.net/ListHelp > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1850746 Title: mythtv-backend-setup fails to add user to group mythtv under XFCE To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mythtv/+bug/1850746/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1850752] Re: Update amd64-microcode to 20191022 for 17h family
This bug was fixed in the package amd64-microcode - 3.20191021.1ubuntu1 --- amd64-microcode (3.20191021.1ubuntu1) focal; urgency=low * Merge from Debian unstable (LP: #1850752). Remaining changes: - initramfs-tools hook (debian/initramfs.hook): + Default to 'early' instead of 'auto' when building with MODULES=most + Do not override preset defaults from auto-exported conf snippets loaded by initramfs-tools. amd64-microcode (3.20191021.1) unstable; urgency=medium * New microcode update packages from AMD upstream: + New Microcodes: sig 0x00830f10, patch id 0x08301025, 2019-07-11 + Updated Microcodes: sig 0x00800f12, patch id 0x08001250, 2019-04-16 sig 0x00800f82, patch id 0x0800820d, 2019-04-16 * README: update for new release -- Steve Beattie Thu, 31 Oct 2019 09:41:22 -0700 ** Changed in: amd64-microcode (Ubuntu Focal) 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/1850752 Title: Update amd64-microcode to 20191022 for 17h family To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/amd64-microcode/+bug/1850752/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1850851] Re: [SRU] ubuntu-release-upgrader no longer produces tarballs
This bug was fixed in the package ubuntu-release-upgrader - 1:20.04.2 --- ubuntu-release-upgrader (1:20.04.2) focal; urgency=medium * Fix binary and binary-indep targets to work as intended (LP: #1850851) -- Adam Conrad Thu, 31 Oct 2019 13:38:35 -0600 ** Changed in: ubuntu-release-upgrader (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1850851 Title: [SRU] ubuntu-release-upgrader no longer produces tarballs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1850851/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1850870] [NEW] Disco update: upstream stable patchset 2019-10-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-10-31 Ported from the following upstream stable releases: v4.19.79, v5.3.6 from git://git.kernel.org/ s390/process: avoid potential reading of freed stack KVM: s390: Test for bad access register and size at the start of S390_MEM_OP s390/topology: avoid firing events before kobjs are created s390/cio: exclude subchannels with no parent from pseudo check KVM: PPC: Book3S HV: Fix race in re-enabling XIVE escalation interrupts KVM: PPC: Book3S HV: Check for MMU ready on piggybacked virtual cores KVM: PPC: Book3S HV: Don't lose pending doorbell request on migration on P9 KVM: X86: Fix userspace set invalid CR4 nbd: fix max number of supported devs PM / devfreq: tegra: Fix kHz to Hz conversion ASoC: Define a set of DAPM pre/post-up events ASoC: sgtl5000: Improve VAG power and mute control powerpc/mce: Fix MCE handling for huge pages powerpc/mce: Schedule work from irq_work powerpc/powernv: Restrict OPAL symbol map to only be readable by root powerpc/powernv/ioda: Fix race in TCE level allocation powerpc/book3s64/mm: Don't do tlbie fixup for some hardware revisions can: mcp251x: mcp251x_hw_reset(): allow more time after a reset tools lib traceevent: Fix "robust" test of do_generate_dynamic_list_file crypto: qat - Silence smp_processor_id() warning crypto: skcipher - Unmap pages after an external error crypto: cavium/zip - Add missing single_release() crypto: caam - fix concurrency issue in givencrypt descriptor crypto: ccree - account for TEE not ready to report crypto: ccree - use the full crypt length value MIPS: Treat Loongson Extensions as ASEs power: supply: sbs-battery: use correct flags field power: supply: sbs-battery: only return health when battery present tracing: Make sure variable reference alias has correct var_ref_idx usercopy: Avoid HIGHMEM pfn warning timer: Read jiffies once when forwarding base clk PCI: vmd: Fix shadow offsets to reflect spec changes watchdog: imx2_wdt: fix min() calculation in imx2_wdt_set_timeout perf stat: Fix a segmentation fault when using repeat forever drm/omap: fix max fclk divider for omap36xx drm/msm/dsi: Fix return value check for clk_get_parent drm/nouveau/kms/nv50-: Don't create MSTMs for eDP connectors drm/i915/gvt: update vgpu workload head pointer correctly mmc: sdhci: improve ADMA error reporting mmc: sdhci-of-esdhc: set DMA snooping based on DMA coherence Revert "locking/pvqspinlock: Don't wait if vCPU is preempted" xen/xenbus: fix self-deadlock after killing user process ieee802154: atusb: fix use-after-free at disconnect s390/cio: avoid calling strlen on null pointer cfg80211: initialize on-stack chandefs ima: always return negative code for error ima: fix freeing ongoing ahash_request fs: nfs: Fix possible null-pointer dereferences in encode_attrs() 9p: Transport error uninitialized 9p: avoid attaching writeback_fid on mmap with type PRIVATE xen/pci: reserve MCFG areas earlier ceph: fix directories inode i_blkbits initialization ceph: reconnect connection if session hang in opening state watchdog: aspeed: Add support for AST2600 netfilter: nf_tables: allow lookups in dynamic sets drm/amdgpu: Fix KFD-related kernel oops on Hawaii drm/amdgpu: Check for valid number of registers to read pNFS: Ensure we do clear the return-on-close layout stateid on fatal errors pwm: stm32-lp: Add check in case requested period cannot be achieved x86/purgatory: Disable the stackleak GCC plugin for the purgatory ntb: point to right memory window index thermal: Fix use-after-free when unregistering thermal zone device thermal_hwmon: Sanitize thermal_zone type libnvdimm/region: Initialize bad block for volatile namespaces fuse: fix memleak in cuse_channel_open libnvdimm/nfit_test: Fix acpi_handle redefinition sched/membarrier: Call sync_core only before usermode for same mm sched/membarrier: Fix private expedited registration check sched/core: Fix migration to invalid CPU in __set_cpus_allowed_ptr() perf build: Add detection of java-11-openjdk-devel package kernel/elfcore.c: include proper prototypes perf unwind: Fix libunwind build failure on i386 systems nfp: flower: fix memory leak in nfp_flower_spawn_vnic_reprs drm/radeon: Bail earlier when radeon.cik_/si_support=0 is passed KVM: PPC: Book3S HV: XIVE: Free escalation interrupts before disabling the VP KVM: nVMX: Fix consistency check on injected exception error code nbd: fix crash when the blksize is zero powerpc/pseries: Fix cpu_hotplug_lock acquisition in resize_hpt()
[Bug 1835737] Re: SRU: backport Python 3.8 to bionic
Hello Matthias, or anyone else affected, Accepted python3-stdlib-extensions into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/python3-stdlib- extensions/3.6.9-1~18.04 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: python3-stdlib-extensions (Ubuntu Bionic) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1835737 Title: SRU: backport Python 3.8 to bionic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3-stdlib-extensions/+bug/1835737/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1850130] Re: zpools fail to import after reboot on fresh install of eoan
I have the same problem with my custom install, inherited and upgraded from my Ubuntu 19.04 system. After each boot I run a small script to export and import my three pools again. zsys is not installed anymore on this manual install from early 2019. The system worked without problems on Ubuntu 19.04. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1850130 Title: zpools fail to import after reboot on fresh install of eoan To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1850130/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1850480] Re: eoan/linux-azure: 5.3.0-1006.6 -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: 1850486 packages: lrm: linux-restricted-modules-azure main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Testing phase-changed: Thursday, 31. October 2019 12:06 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 - stakeholder-signoff: Pending -- waiting for signoff + stakeholder-signoff: Stalled -- waiting for signoff verification-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/1850480 Title: eoan/linux-azure: 5.3.0-1006.6 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1850480/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1850866] [NEW] Please sync amd64-microcode from debian bullseye
Public bug reported: The amd64-microcode version (3.20181128.1ubuntu2) is packaged in 2018, which is too old to support the latest AMD Ryzen 3000 series CPUs. In particular, it doesn't include the upstream microcode patch, without which the kernel cannot produce psuedorandom numbers. Instead, in its buggy state, when RDRAND is being asked, the CPU will always produce the same result, 0x. Full report: https://arstechnica.com/gadgets/2019/10/how-a-months-old-amd-microcode-bug-destroyed-my-weekend/ Please update the package for a version dated at the earliest 20191022. https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git ** Affects: amd64-microcode (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/1850866 Title: Please sync amd64-microcode from debian bullseye To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/amd64-microcode/+bug/1850866/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849374] Re: packages built for python3.8 with disabled tests, for a first binary
python-django_2.2.6-1.dsc tests fail in both debian and ubuntu, on both py3.7 and py3.8, but we need it so I guess disabling some tests. ** Also affects: python-django (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/1849374 Title: packages built for python3.8 with disabled tests, for a first binary To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/astropy/+bug/1849374/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1850184] Re: losetup -f broken in 2.0.6-1ubuntu2
Yeah, I saw the mail; much better. I fixed one of these in dietlibc the other day… -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1850184 Title: losetup -f broken in 2.0.6-1ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/klibc/+bug/1850184/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849855] Re: bionic/linux: 4.15.0-68.77 -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 bugs-spammed: true packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Testing phase-changed: Tuesday, 29. October 2019 13:37 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress certification-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-aws: bug 1849016 bionic/linux-fips: bug 1849023 bionic/linux-gke-4.15: bug 1849018 bionic/linux-ibm-gt: bug 1849020 bionic/linux-kvm: bug 1849019 - bionic/linux-oem: bug 1850799, bug 1849012 + bionic/linux-oem: bug 1849012, bug 1850799 bionic/linux-oracle: bug 1849022 bionic/linux-raspi2: bug 1849008 bionic/linux-snapdragon: bug 1849011 bionic/linux/pc-kernel: bug 1849852 bionic/linux/pc-lowlatency-kernel: bug 1849853 unknown/unknown: bug 1849854 xenial/linux-azure: bug 1849027 xenial/linux-gcp: bug 1849031 xenial/linux-hwe: bug 1849854 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/1849855 Title: bionic/linux: 4.15.0-68.77 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1849855/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1848200] Re: gdb not stopping on breakpoint in a 32-bit program
Fixed in 8.1.1 and later. https://sourceware.org/git/gitweb.cgi?p=binutils- gdb.git;a=commit;h=8679931c2c9f97ad182f8f0a9e8fab20305719b5 ** No longer affects: gdb (Ubuntu Disco) ** No longer affects: gdb (Ubuntu Eoan) ** No longer affects: gdb (Ubuntu Focal) ** Changed in: gdb (Ubuntu) Status: Invalid => 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/1848200 Title: gdb not stopping on breakpoint in a 32-bit program To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/1848200/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1681839] Re: libvirt: blockcommit fails - disk not ready for pivot yet
** Summary changed:
- libvirt - disk not ready for pivot yet
+ libvirt: blockcommit fails - disk not ready for pivot yet
** Description changed:
- root@thewind:/home/bestpa/scripts# virsh blockcommit mail vda --active
--verbose --pivot
- Block commit: [100 %]error: failed to pivot job for disk vda
+ [Impact]
+
+ On xenial, if you manually invoke blockcommit through virsh in libvirt,
+ the command immediately fails with blockcommit supposedly being 100%,
+ and that the disk is not ready for pivot yet:
+
+ root@xenial-apparmor:~# virsh blockcommit snapvm vda --active --verbose
--pivot --wait
+ Block commit: [100 %]
+ error: failed to pivot job for disk vda
error: block copy still active: disk 'vda' not ready for pivot yet
- found related bugfix at redhat... can i get 1.3.2 pushed into ubuntu
- 16.04 release?
-
- bestpa@thewind:~$ cat /etc/os-release
- NAME="Ubuntu"
- VERSION="16.04.2 LTS (Xenial Xerus)"
- ID=ubuntu
- ID_LIKE=debian
- PRETTY_NAME="Ubuntu 16.04.2 LTS"
-
- bestpa@thewind:~$ libvirtd --version
- libvirtd (libvirt) 1.3.1
+ However, if you look at the status of the active blockjob, we see that
+ the blockcommit is still active in the background:
+
+ root@xenial-apparmor:~# virsh blockjob snapvm vda --info
+ Active Block Commit: [0 %]
+
+ root@xenial-apparmor:~# virsh blockjob snapvm vda --info
+ Active Block Commit: [2 %]
+
+ root@xenial-apparmor:~# virsh blockjob snapvm vda --info
+ Active Block Commit: [6 %]
+
+ This happens until it reaches 100%, where it gets stuck. To un-stick
+ things, you must then manually --abort the blockjob.
+
+ root@xenial-apparmor:~# virsh blockjob snapvm vda --info
+ Active Block Commit: [100 %]
+
+ This happens in VMs which are experiencing load, and is caused by a race
+ condition in libvirt. Users are not able to commit their snapshots to
+ disk.
+
+ [Test Case]
+
+ Credit goes to Fabio Martins, who determined how to reproduce this
+ issue.
+
+ On a Ubuntu 16.04 host with libvirt 1.3.1-1ubuntu10.27:
+
+ 1) Create a VG and define a LVM pool:
+
+ root@xenial-apparmor:~# cat lvmpool.xml
+
+ LVMpool_vg
+
+
+
+
+ /dev/LVMpool_vg
+
+
+
+ # virsh pool-define lvmpool.xml
+ # virsh pool-start LVMpool_vg
+ # virsh pool-autostart LVMpool_vg
+
+ 2) Create a config file to use as a cdrom device with the new VM (will
+ be created in next steps), just to inject a password with cloud-init:
+
+ # cat > config < #cloud-config
+ > password: passw0rd
+ > chpasswd: { expire: False }
+ > ssh_pwauth: True
+ > EOF
+
+ # apt install cloud-image-utils
+
+ # cloud-localds config.img config
+
+ # mv config.img /var/lib/libvirt/images/
+ # chown libvirt-qemu:kvm /var/lib/libvirt/images/config.img
+ # chmod 664 /var/lib/libvirt/images/config.img
+
+ 3) Create one VM using this pool:
+
+ # virt-install --connect=qemu:///system --name snapvm --ram 2048
+ --vcpus=1 --os-type=linux --disk pool=LVMpool_vg,size=15,bus=virtio
+ --disk /var/lib/libvirt/images/config.img,device=cdrom --network network
+ =kvm-br0 --graphics none --import --noautoconsole
+
+ 4) Stop the VM
+
+ # virsh destroy snapvm
+
+ 5) Download a Ubuntu cloud image, convert to raw and restore it into the
+ LV used as a disk by our VM:
+
+ # wget
https://cloud-images.ubuntu.com/bionic/current/bionic-server-cloudimg-amd64.img
+ # qemu-img convert ./bionic-server-cloudimg-amd64.img
./bionic-server-cloudimg-amd64.raw
+ # dd if=./bionic-server-cloudimg-amd64.raw of=/dev/LVMpool_vg/snapvm bs=8M
conv=sparse
+
+ 6) Start the VM and connect to it in another window
+
+ # virsh start snapvm
+
+ 7) Check that the VM is using the LV as the disk:
+
+ root@xenial-apparmor:~# virsh domblklist snapvm
+ Target Source
+
+ vda /dev/LVMpool_vg/snapvm
+ hda /var/lib/libvirt/images/config.img
+
+ 8) Create a snapshot and check that the new domblklist points to the
+ snapshot file:
+
+ # virsh snapshot-create-as --domain snapvm --diskspec
+ vda,file=/var/lib/libvirt/images/xenial-snapvm.qcow2,snapshot=external
+ --disk-only --atomic
+
+ root@xenial-apparmor:~# virsh domblklist snapvm
+ Target Source
+
+ vda /var/lib/libvirt/images/xenial-snapvm.qcow2
+ hda /var/lib/libvirt/images/config.img
+
+ 9) Connect to your VM and start an I/O intensive job. In this case I'm
+ starting a 'dd' writing zeroes to a file until it gets to 10GBs:
+
+ ubuntu@ubuntu:~$ dd if=/dev/zero of=file.txt count=1024 bs=1024
+
+ 10) Back to the host, monitor the snapshot file and let it grow until at
+ list a bit more than 1GB, as in the example below (where we can see the
+ file with 3.9G):
+
+ root@xenial-apparmor:~# ls -lh /var/lib/libvirt/images/
+ total 5.2G
+ -rw-rw-r-- 1 libvirt-qemu kvm 329M Sep 3 03:18
bionic-server-cloudimg-amd64.img
+ -rw-r--r-- 1 root root 10G Sep 3 03:28 bionic-server-cloudimg-amd64.raw
+ -rw-rw-r-- 1 libvirt-qemu kvm 366K Sep 3 03:19 config.img
+ -rw--- 1 libvirt-qemu kvm 3.9G Sep 3 04:41
[Bug 1850746] Re: mythtv-backend-setup fails to add user to group mythtv under XFCE
Sorry if I got a bit excited. On a fresh install of Xubuntu, Mythtv backend setup does not work. If it worked, then when it was first run it would add the user to the group "mythtv", something that requires root access. My guess is that long ago a pop up box would prompt the user for their password before continuing. The grep above revels multiple places where gksu is expected to exist. Because gksu has been removed from the distribution each of these lines is a bug that leaves a variable empty. I don't know what the correct fix is. It seems a bit to demanding to expect the end user edit /etc/group in a terminal. The man page for apt does not mention "source", is that documented anywhere? I got a "permission denied". kdebase-bin seems to be an alternative to gksu it does not have an installation candidate either. There is a way to do it, gpated has a pop up that prompts for a password. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1850746 Title: mythtv-backend-setup fails to add user to group mythtv under XFCE To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mythtv/+bug/1850746/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1819890] Re: Restarting gnome-shell displays images of applications running on other workspaces
** Changed in: mutter Status: Unknown => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1819890 Title: Restarting gnome-shell displays images of applications running on other workspaces To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1819890/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1850184] Re: losetup -f broken in 2.0.6-1ubuntu2
We found the issue -- I think xnox is going to report it via proper channels. But basically it's this: sizeof(dev_t) = 4 sizeof(__kernel_old_dev_t) = 8 This makes the kernel's loop_info 8 bytes bigger than klibc's and so the kernel is writing past the end of the loopinfo on the stack, which until now has avoided causing problems by sheer luck. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1850184 Title: losetup -f broken in 2.0.6-1ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/klibc/+bug/1850184/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1839417] Re: Potentially existing (legitimate, root owned) lock file getting deleted by Apport daily cron(8) script
*** This bug is a duplicate of bug 1839415 *** https://bugs.launchpad.net/bugs/1839415 Yes - marking this as a duplicate against LP #1839415 as noted by Seth earlier too. ** This bug has been marked a duplicate of bug 1839415 Fully user controllable lock file due to lock file being located in world-writable directory -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1839417 Title: Potentially existing (legitimate, root owned) lock file getting deleted by Apport daily cron(8) script To manage notifications about this bug go to: https://bugs.launchpad.net/apport/+bug/1839417/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1843207] Re: Doesn't boot on Raspberry Pi 4
Hello, Apologies for a newbie question. Is there a scheduled release date for the upgrade/update at ubuntu-19.10-preinstalled-server-arm64+raspi3.img? Just need to get my ducks in a row by suspending work on the current image with respect to items other than the total_mem issue. Thanks. Kind regards. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1843207 Title: Doesn't boot on Raspberry Pi 4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1843207/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1848999] Re: disco/linux-snapdragon: 5.0.0-1025.26 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: Incomplete => 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: 1850574 packages: main: linux-snapdragon meta: linux-meta-snapdragon phase: Testing phase-changed: Wednesday, 23. October 2019 15:22 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - automated-testing: Stalled -- testing FAILED certification-testing: Ongoing -- testing in progress security-signoff: Stalled -- waiting for signoff verification-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/1848999 Title: disco/linux-snapdragon: 5.0.0-1025.26 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1848999/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849871] Re: Skip frame when buffer overflow on UVC camera
** Changed in: linux (Ubuntu Xenial) Status: New => In Progress ** Changed in: linux (Ubuntu Bionic) Status: New => In Progress ** Changed in: linux (Ubuntu Bionic) Assignee: (unassigned) => Kai-Heng Feng (kaihengfeng) ** Changed in: linux (Ubuntu Xenial) Assignee: (unassigned) => Kai-Heng Feng (kaihengfeng) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1849871 Title: Skip frame when buffer overflow on UVC camera To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1849871/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1690085]
Could this be related? [620533.9804061 RBP: R08: 0001 R09: 7f901480 [620533.981792] R10: 7f9014de0270 R11: 0206 R12: 7f90477fdlfe [620533.983039] R13: 7f90477fdlff R14: 7f901700 R15: 7f901fffe540 [620541.767819] watchdog: BUG: soft lockup - CPU#4 stuck for 220 Enc4:Eantoor:5552.1 [620541.769193] Modules linked in: tun ueth nf_conntrack_netlink nfnetlink xfrm_user xfrn_algo xt_addrtype iptable filter xt c, ntrack br_petfilter bridge stp 11c ouerlay xt_nat xt_tcpudp iptable_nat xt_MASQUERADE nf_nat nf_conntrack nf_defraliipu6 -n id.nfjlefrag_ipu4 nouueau snd_bda_codec_realtek snd_hda_codec_generic ledtrig_audio mxn_wmi i2c_algo_bit ttm edac_mCe_amd snd a_intel drmitms_helper snd_hda_codec eeepc_wmi kum_and snd_hda_core sparse_keymap drm rfkill snd_hudep joydeu inputied s snd, cm r8169 wml_trmof kum irgbypass realtek snd_timer libphy agpgart ccp snd syscopyarea sysfillrect sysimgblt sp5100_tco sou ndcore fb_sys_fops rng_core i2cpiix4 crctlOdif_pclmul klOtemp crc32_pclmul ghash_clmulni_inte1 aesni_intel aes_x86_64 crypto_si md crypt& glue helper pcspkr wmi pinctrl_and pcc_cpufreq eudeu gpio_andpt mac_hid acpi_cpufreq nfsd auth_rpcgss nfs_acl lockd gr ace sunrpc ip_tables x tables ext4 crc16 mbcache jbd2 raid456 libcrc32c crc32c_generic async_raid6_recou 1620541.7692211 async memcpy async_pq async_xor xor async_tx raid6_pq raidl md_mod hid_generic sd_mod usbhid hid ahci libahci 1 ibata crc32c_intel xhcipci xhci_bcd scsi_mod 1620541.7638311 CPU: 4 PID: 5552 Comm: nc4:Eantoor Tainted: G U L 5.2.11-archl-l-ARCH #1 [620541.765314] Hardware name: System manufacturer System Product Name/PRIME B450-PLUS, BIBS 1804 07/29/2019 [620541.766760] RIP: 0010:smp_call_function_many+Ox20b/Ox270 [620541.766216] Code: e6 8a ae 78 00 3b 05 f8 Od 21 01 89 c7 Of 83 7a fe ff ff 48 63 c7 48 8b Ob 48 03 Oc c5 60 ba d6 al 8b 41 1 6 a8 01 74 Oa f3 90 51 16 83 e2 01 75 f6 eb c9 48 c7 c2 c0 14 f4 al 4c 89 fe 89 df [620541.791144] RSP: 0016:aefd63e2bcd0 EFLAGS: 0202 ORIG_RAX: ffl3 [620541.7925011 RAX: 0003 RBX: 8fe6be72b440 RCX: 8fe6be7flle0 1620541.793697] RDX: 0001 BSI: RDI: 0007 [620541.795357] RBP: a0c7c7e0 R08: 8fe6be72b448 R09: 8fe6be72b470 1620541.796751] R10: 8fe6be72b448 R11: 0005 R12: 8febbe729d40 1620541:798198] R13: 8fe6be72b448 R14: 0001 R15: 0140 [620541.799600] FS: 7f9044d5c700() G3:8fe6be70() knlGS: [620541.800986] CS: 0010 DS: ES: CH0: 80050033 [620541.802414] CR2: 7f9062e8 f3b0 CR3: 0003ae65a000 CR4: 003406e0 [620541.803847] Call Trace: [629541.80-r 8] flush tlb mm_range+Oxe1/0x140 1620541.8065503 tlb_flush mmu+Ox72/0x140 [628541.807929] tlb_finish_mmu+Ox3d/Ox70 t62e541me92?el zap_page_range+Oxl4b/Oxia0 [620541.810589] se sys maduise+Ox613/0x890 [620541.811932] ? do syscall_64+0x5f/Ox1d0 [628541.813277] do syscall_64+0x5f/Ox1d0 [629541.8146481 ? page_fault+Ox8/0x30 [628541.815992] entry SYSCALL64afterbaframe+Ox44/0xa9 [620541i817395] RIP: 0833:0x7f9062dd7597 russdriAluffral Code: ff ff ff ff c3 48 8b 15 f7 f8 Oc 00 f7 d8 64 89 02 b8 ff ff ff ff eb be 66 2e Of if 84 00 00 00 00 00 90 b 8 lc ee ee ee Of 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b Od c9 f8 c 0 f7 dB 64 89 01 48 1.8Z1587.1 1SP: 082b:7f9044d5b478 EFLAGS: 0206 ORIG_ORAX:0 001c tfiZe541.13229471 RAX: ffda RBX. 7f904455c000 RCX: 7f9062dd7597 007fb000 RDI: 7f904455c000 E629541.8Z44311 RDX: 000 0004 BSI: [ 1.8258153] RBP: R08: 0001 R09: 7f902480 E 1.8M871 B1e: 7f90246af180R11: 0206 R12: 7f9047ffelfe I 1.8287181 R13: 7f9047ffelff R14: 7f9044d5c700 R15: 7f9044d5b540 ME, Sorry, no logging in syslog because the machine crashes hard. Optional picture of the output: https://iot.jcz.nl/soft_lockup.jpg -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1690085 Title: Ryzen 1800X freeze - rcu_sched detected stalls on CPUs/tasks To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1690085/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1850851] Re: [SRU] ubuntu-release-upgrader no longer produces tarballs
Verified in both eoan-proposed and focal-proposed that the tarball is built and published to the correct location, and the debs have no differences from their previous versions other than the version numbers. ** Tags removed: verification-needed verification-needed-eoan ** Tags added: verification-done verification-done-eoan -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1850851 Title: [SRU] ubuntu-release-upgrader no longer produces tarballs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1850851/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1850184] Re: losetup -f broken in 2.0.6-1ubuntu2
How is this even a fix? Also, does this affect other applications built against klibc? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1850184 Title: losetup -f broken in 2.0.6-1ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/klibc/+bug/1850184/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849930] Re: Additional L2TP VPN Breaks First VPN
I confirm that the packages provided by Douglas Kosovic's PPA work successfully: https://github.com/nm-l2tp/NetworkManager-l2tp/issues/112#issuecomment-548593238 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1849930 Title: Additional L2TP VPN Breaks First VPN To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1849930/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1850863] Re: execstack --set-execstack Aborted (core dump)
*** This bug is a duplicate of bug 1850861 *** https://bugs.launchpad.net/bugs/1850861 ** This bug has been marked a duplicate of bug 1850861 execstack --set-execstack Aborted (core dump) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1850863 Title: execstack --set-execstack Aborted (core dump) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/prelink/+bug/1850863/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1850184] Re: losetup -f broken in 2.0.6-1ubuntu2
** No longer affects: gcc-9 (Ubuntu) ** No longer affects: gcc-9 (Ubuntu Eoan) ** No longer affects: gcc-9 (Ubuntu Focal) ** No longer affects: linux (Ubuntu Focal) ** No longer affects: linux (Ubuntu Eoan) ** No longer affects: 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/1850184 Title: losetup -f broken in 2.0.6-1ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/klibc/+bug/1850184/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1850184] Re: losetup -f broken in 2.0.6-1ubuntu2
** Changed in: klibc (Ubuntu Focal) Status: Fix Released => Confirmed ** Changed in: klibc (Ubuntu Eoan) 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/1850184 Title: losetup -f broken in 2.0.6-1ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/klibc/+bug/1850184/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1817595] Re: [SRU] urdfdom-headers and urdfdom should not use locale dependent parsing for floating point numbers
** Tags removed: verification-needed 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/1817595 Title: [SRU] urdfdom-headers and urdfdom should not use locale dependent parsing for floating point numbers To manage notifications about this bug go to: https://bugs.launchpad.net/urdfdom-headers/+bug/1817595/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1839417] Re: Potentially existing (legitimate, root owned) lock file getting deleted by Apport daily cron(8) script
I believe this is moot given the following security change. * SECURITY UPDATE: fully user controllable lock file due to lock file being located in world-writable directory (LP: #1839415) - data/apport: create and use lock file from /var/lock/apport. - CVE-2019-11485 Is that correct Alex? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1839417 Title: Potentially existing (legitimate, root owned) lock file getting deleted by Apport daily cron(8) script To manage notifications about this bug go to: https://bugs.launchpad.net/apport/+bug/1839417/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1850861] Re: execstack --set-execstack Aborted (core dump)
$ hardening-check /tmp/ls /tmp/ls: Position Independent Executable: yes Stack protected: yes Fortify Source functions: yes (some protected functions found) Read-only relocations: yes Immediate binding: yes Stack clash protection: yes Control flow integrity: yes On older releases, we can use --set-execstack on /bin/ls. hardening- check is different: $ hardening-check /tmp/ls-bionic /tmp/ls-bionic: Position Independent Executable: yes Stack protected: yes Fortify Source functions: yes (some protected functions found) Read-only relocations: yes Immediate binding: yes Stack clash protection: unknown, no -fstack-clash-protection instructions found Control flow integrity: unknown, no -fcf-protection instructions found! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1850861 Title: execstack --set-execstack Aborted (core dump) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/prelink/+bug/1850861/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1848797] Re: After upgrading to 19.10, boot screen shows: "Error: symbol 'grub_file_filters' not found."
** Description changed: After upgrading to 19.10 the boot screen shows the following error: Error: symbol 'grub_file_filters' not found. Entering rescue mode... + I could fix it after i booted Ubuntu 19.10 live and used the chroot + repair method as described here + https://wiki.ubuntuusers.de/GRUB_2/Reparatur/#chroot-Methode (german) - I could fix it after i booted Ubuntu 19.10 live and used the chroot repair method as described here https://wiki.ubuntuusers.de/GRUB_2/Reparatur/#chroot-Methode (german) + Workaround + -- + From https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1848797/comments/18 + "In any case, right now the best thing to do to repair is to boot from a Live image (USB or CD-ROM), and follow the steps in https://help.ubuntu.com/community/Grub2/Installing#via_ChRoot to repair GRUB by hand, or reinstall." -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1848797 Title: After upgrading to 19.10, boot screen shows: "Error: symbol 'grub_file_filters' not found." To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1848797/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1840941] Re: kdump fails to start with secure boot enabled
Should be done very soon; we're waiting for the shim review board to review, then it can be submitted to Microsoft for signing. Expect about a week turnaround time. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1840941 Title: kdump fails to start with secure boot enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shim-signed/+bug/1840941/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1850863] [NEW] execstack --set-execstack Aborted (core dump)
Public bug reported: Reproducer: $ cp /bin/ls /tmp $ execstack --set-execstack /tmp/ls execstack: dso.c:877: reopen_dso: Assertion `dso->shdr[j].sh_size == 0' failed. Aborted (core dumped) [134] ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: execstack 0.0.20131005-1 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.1 Architecture: amd64 CurrentDesktop: GNOME Date: Thu Oct 31 16:49:20 2019 InstallationDate: Installed on 2016-10-01 (1125 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) ProcEnviron: SHELL=/bin/bash LANG=en_US.UTF-8 TERM=xterm-256color XDG_RUNTIME_DIR= PATH=(custom, user) SourcePackage: prelink UpgradeStatus: Upgraded to eoan on 2019-10-27 (4 days ago) ** Affects: prelink (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan wayland-session -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1850863 Title: execstack --set-execstack Aborted (core dump) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/prelink/+bug/1850863/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1841675] Re: do-release-upgrade crashed with AttributeError in tryMarkObsoleteForRemoval(): 'Package' object has no attribute 'section'
Hello Bart, or anyone else affected, Accepted ubuntu-release-upgrader into eoan-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source /ubuntu-release-upgrader/1:19.10.15.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-eoan to verification-done-eoan. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-eoan. 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: ubuntu-release-upgrader (Ubuntu Eoan) Status: Fix Released => Fix Committed ** Tags added: verification-needed verification-needed-eoan -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1841675 Title: do-release-upgrade crashed with AttributeError in tryMarkObsoleteForRemoval(): 'Package' object has no attribute 'section' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1841675/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1841675] Re: do-release-upgrade crashed with AttributeError in tryMarkObsoleteForRemoval(): 'Package' object has no attribute 'section'
The upload of ubuntu-release-upgrader 19.10.15.2 was about building the release upgrader tarball as that was broken. Given that the fix for this bug is not actually in code that runs in the release upgrader tarball I am setting this to verification-done. ** Tags removed: verification-needed verification-needed-eoan ** Tags added: verification-done verification-done-eoan -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1841675 Title: do-release-upgrade crashed with AttributeError in tryMarkObsoleteForRemoval(): 'Package' object has no attribute 'section' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1841675/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1850851] Re: [SRU] ubuntu-release-upgrader no longer produces tarballs
Hello Adam, or anyone else affected, Accepted ubuntu-release-upgrader into eoan-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source /ubuntu-release-upgrader/1:19.10.15.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-eoan to verification-done-eoan. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-eoan. 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: ubuntu-release-upgrader (Ubuntu Eoan) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-eoan -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1850851 Title: [SRU] ubuntu-release-upgrader no longer produces tarballs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1850851/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1844805] Please test proposed package
Hello Jonathan, or anyone else affected, Accepted ubuntu-release-upgrader into eoan-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source /ubuntu-release-upgrader/1:19.10.15.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-eoan to verification-done-eoan. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-eoan. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1844805 Title: virtualbox, virtualbox-dkms, virtualbox-qt fail during upgrade from 19.04 to 19.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1844805/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1825655] Re: do-release-upgrade fails with "Your python3 install is corrupted" if /usr/bin/python points to /etc/alternatives/python
Hello Dmitrii, or anyone else affected, Accepted ubuntu-release-upgrader into eoan-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source /ubuntu-release-upgrader/1:19.10.15.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-eoan to verification-done-eoan. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-eoan. 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: ubuntu-release-upgrader (Ubuntu Eoan) Status: New => Fix Committed ** Tags added: verification-needed verification-needed-eoan -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1825655 Title: do-release-upgrade fails with "Your python3 install is corrupted" if /usr/bin/python points to /etc/alternatives/python To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1825655/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
