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
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
** 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
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
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.
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
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.
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
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:
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
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
*** 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:
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
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
[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.
[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.
[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
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".
*** 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.
** 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 --
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)
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:
** 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)
*** 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
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:
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
** 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
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
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
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
** 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
** 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.
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 ?
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
** 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
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
** 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 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
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
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
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.
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
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
*** 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
** 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
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
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
*** 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:
-
*** 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
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
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
** 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:
*** 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
** 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
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"
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.
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"
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:
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
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
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,
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
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:
>
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'
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:
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
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
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
** 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 --
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
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
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
** 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 --
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)
** 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
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
** 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
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
*** 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
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
** 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
** 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:
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:
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:
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
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.
*** 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
** 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
** 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
** 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
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
$ 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
** 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
+
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.
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:
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
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
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
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
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
1 - 100 of 508 matches
Mail list logo
