This bug was fixed in the package apport - 2.20.11-0ubuntu2
---
apport (2.20.11-0ubuntu2) eoan; urgency=medium
* test/test_backend_apt_dpkg.py: as of r3211 an error is not raised if the
binary is not found. Cherry picked from upstream r3248.
* backends/packaging-apt-dpkg.py:
Upstream bug was closed "VERIFIED FIXED" on 2015-04-06
No further comments re bug here or upstream for over four years, closing as
fixed.
** Changed in: firefox (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch
** Package changed: texinfo (Ubuntu) => apt (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1829735
Title:
Fresh install of 18.10 stuck at initializing ramdisk after
** Tags removed: need-duplicate-check
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1829747
Title:
package initramfs-tools 0.122ubuntu8.14 failed to
Thanks for sharing your findings. What you found out is indeed
interesting, however I'm not sure you can say the change happened in
modprobe, as you are using two different kernel versions. Perhaps insmod
and modprobe always behaved differently, and what changed is what the
kernel does.
Your
You have been subscribed to a public bug:
**Specs**
- Asus Zenbook 14 UX433FN (NVMe PCIe SSD)
- Ubuntu 18.10 and Windows 10 dual boot, Windows 10 working fine.
**Background**
After successful FRESH install of Ubuntu 18.10 desktop using LiveUSB, and
subsequent update using either command prompt
** Package changed: apt (Ubuntu) => ubuntu
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1829735
Title:
Fresh install of 18.10 stuck at initializing ramdisk after sudo apt
This is a question about unsigned software that PackageKit could not
ask.
** Package changed: software-properties (Ubuntu) => packagekit (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to packagekit in Ubuntu.
Here is better evidence.
Just now I ran the experiment using same kernel version, 4.19.42,
as in the xenial experiment reported above.
My conclusions are unchanged. The newly-introduced incompatible
and inconsistent behavior depends on the modprobe release, not
on the kernel release. I knew
Hi Andrea,
Do you have an ETA on verifying this SRU? I have a software-properties
SRU that is blocked from getting into bionic-proposed until this is
released. https://bugs.launchpad.net/bugs/1829017
Thanks,
Corey
--
You received this bug notification because you are a member of Ubuntu
Touch
Public bug reported:
Upgrading Ubuntu 16.04 server on raspberry pi 2 to ubuntu 18
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: initramfs-tools 0.122ubuntu8.14
ProcVersionSignature: Ubuntu 4.4.0-1065.73-raspi2 4.4.73
Uname: Linux 4.4.0-1065-raspi2 armv7l
ApportVersion:
Public bug reported:
When specifying "debug" on the kernel command line in order to catch
initramfs debug info, the init hangs. It's quite early in the boot
process (certainly before pre-mount is called, as I don't see anything
relating to btrfs scan and resuming from hibernation).
╰─▶ uname -a
There is some activity upstream on the 1.14 branches, so there might be a
1.14.5, but I'm not sure:
https://gitlab.freedesktop.org/gstreamer/gst-plugins-base/merge_requests/223
https://gitlab.freedesktop.org/gstreamer/gst-plugins-good/merge_requests/198
Should this SRU wait for a 1.14.5 release?
fixed in 19.4 update
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to upower in Ubuntu.
https://bugs.launchpad.net/bugs/1823134
Title:
Cannot change display brightness [HP ZBook 17 G5 with Nvidia Quadro
P1000 Mobile]
*** This bug is a duplicate of bug 1822026 ***
https://bugs.launchpad.net/bugs/1822026
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 1822026, so it is being marked as such. Please
** Changed in: upower (Ubuntu)
Status: New => Fix Released
** Changed in: gnome-shell (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to upower in Ubuntu.
Public bug reported:
Hi,
We have a cups server (ubuntu) that centralize all our network printers.
Each desktop users on Ubuntu (16.04, 18.04) are looking in that print
server to retrieve those printers. It works fine but...
# /etc/cups/cups-browsed.conf in a desktop user
...
Michael Gale, your issue is different to the OP's one. The routes the OP
has entered are all CIDR notable, he even uses CIDR when entering them
via command line.
So please report a new bug, showing which routes you have entered and
how they end up in /etc/NetworkManager/system-connections.
In
Public bug reported:
password character is typed after about 1s when key is pressed and mouse
stops for about one sec when hovering over buttons (including user
profile button) sometimes instead ubuntu logo is text ubuntu which fixes
itself after while.
ProblemType: Bug
DistroRelease: Ubuntu
Could anyone who still has this problem supply a list of the routes he
has entered and how he has entered them and also attach the
/etc/NetworkManager/system-connections file to this bug report? Thanks.
** Changed in: network-manager (Ubuntu)
Status: Confirmed => Incomplete
--
You
Public bug reported:
In recent versions of initramfs-tools-core, the hibernation resume
script (/usr/share/initramfs-tools/scripts/local-premount/resume) is no
longer +x, so it's silently skipped during boot, causing resume after
hibernation to fail.
I'm not sure when this change was introduced.
$ cat /boot/config-5.0.0-16-generic | grep LOG_BUF
CONFIG_LOG_BUF_SHIFT=18
CONFIG_PRINTK_SAFE_LOG_BUF_SHIFT=13
$ uname -a
Linux doerfel 5.0.0-16-generic #17-Ubuntu SMP Wed May 15 10:54:19 UTC 2019
aarch64 aarch64 aarch64 GNU/Linux
And journal shows complete kernel boot messages, thus this all
ubuntu@P8lpar2:~$ apt policy util-linux
util-linux:
Installed: 2.27.1-6ubuntu3.7
Candidate: 2.27.1-6ubuntu3.7
Version table:
*** 2.27.1-6ubuntu3.7 500
500 http://ports.ubuntu.com/ubuntu-ports xenial-proposed/main ppc64el
Packages
ubuntu@P8lpar2:~$ lscpu
Architecture:
I have hesitated about upgrading, since the problem seems to have been
present also with version 1.10 according to the crash reports.
However, in Ubuntu 19.04 ibus-libpinyin was upgraded to 1.11, and it
looks like there is a significant reduction of crashes in 19.04 compared
to 18.04 and 18.10.
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
Please see https://wiki.ubuntu.com/StableReleaseUpdates for details of
Ubuntu's stable release update process. Based on your report it sounds
like this patch would qualify, but please could you update us on the
I think it's fine. It sounds like there will just be no way to override
package-installed blacklists any more. That's unfortunate, but it's a
very rare situation.
** Changed in: systemd (Ubuntu)
Status: Incomplete => Won't Fix
** Changed in: linux (Ubuntu)
Status: Incomplete =>
@vanvugt Thank you for your answer.
I tried the kernel versions 5.0.0-13 and 4.3.0-04 as well. For the first one,
the same problem occured (sound only after a fresh boot) and the second one
couldn't be installed correctly because of missing libraries (a boot was
possible, but e.g. the mouse
I have a similar setup and am experiencing the same thing since the
update. Thanks for narrowing it down to network-manager!
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
Public bug reported:
If I install or update virtualbox-dkms, dpkg needs to ask me to
configure Secure Boot. This works fine using apt-get (or a GUI), but not
apt. When installing via apt, whiptail(1) doesn't show, and the
installation/upgrade process gets stuck, forcing me to kill dpkg then
run
** Attachment added: "Example process tree snippet"
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1829776/+attachment/5265107/+files/ps_auxf.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
> Wow! Approaching 13-years and counting on this bug. Neat.
What's your point in making this statement? A decision was made soon
after the bug has filed and that decision still stands today. What does
the age of the decision have to do with it?
> Why not just throw a simple toggle into the
This bug was fixed in the package apport - 2.20.11-0ubuntu2
---
apport (2.20.11-0ubuntu2) eoan; urgency=medium
* test/test_backend_apt_dpkg.py: as of r3211 an error is not raised if the
binary is not found. Cherry picked from upstream r3248.
* backends/packaging-apt-dpkg.py:
It also affects kernel version 5.0.0-16 (installed from disco-proposed)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1829621
Title:
[HP Laptop 14-ma0xxx] No sound
Is there any update on this?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1823516
Title:
Nvidia driver installed but X apps are using software rendering
(LLVMpipe) in
I added more info (edited the original description) hoping it covers
everything the SRU requires.
** Description changed:
Bash pre-4.4.20 has a bug in its PID hash table that causes spin-loops
when spawning sub processes and waiting for them. There is a fix:
Whoa...Robbie, I'm just looking out for all the new user's and admin's
that are coming in from other platforms that could reasonably be
surprised by this and not Unix/Linux veteran's who broke their teeth
with vi on Slackware, etc..
Believe it or not, with WSL-2 and other notable advancements of
Hi Łukasz, I'll take this for the security team. Thanks.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to binutils in Ubuntu.
https://bugs.launchpad.net/bugs/1828171
Title:
New toolchain updates need to be rebuilt against
** Changed in: binutils (Ubuntu)
Assignee: (unassigned) => Steve Beattie (sbeattie)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to binutils in Ubuntu.
https://bugs.launchpad.net/bugs/1828171
Title:
New toolchain
I've had 0.96.24.32.8 installed on bionic for some days, it works fine
and the livepatch tab matches the design and work as expected
(activate/desactivate the service, list applied changes, ...), I'm
marking the SRU as verified
** Tags removed: verification-needed verification-needed-bionic
**
As I stated in the Chinese Ubuntu forum, I almost always stick to only the
LTS versions of Ubuntu. I made an exception wrt 18.04 LTS and moved up to
19.04 and even 19.10 because ibus-libpinyin 1.11 is not available in
18.04. However, 19.04 and 19.10 have their own problems and are not
*** This bug is a duplicate of bug 48734 ***
https://bugs.launchpad.net/bugs/48734
** Information type changed from Private Security to Public
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to adduser in Ubuntu.
Looks like that the new version of network-manager is not working
correctly with the systemd-resolved of Bionic.
** Tags added: regression-update
** Also affects: network-manager (Ubuntu Bionic)
Importance: Undecided
Status: New
--
You received this bug notification because you are a
Public bug reported:
a) problem with login to user account. Keeps going back to login window
b) screen freeze after suspension. amdgup needs update
ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: xorg 1:7.7+19ubuntu12
ProcVersionSignature: Ubuntu 5.0.0-15.16-generic 5.0.6
Uname: Linux
Another reboot from Ubuntu back to Ubuntu and the Headset is still
silent, BUT now the speaker sound works. Connecting and disconnecting
the headset now has no effect on speaker sound except to mute when the
headset is plugged in. I apologize for scattershot troubleshooting.
--
You received
Update: The patches have been merged to drm-tip:
https://cgit.freedesktop.org/drm-
tip/commit/?id=1a74fc0b3f49a0603f230b6f087da33bda3d7c66.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
Correction. The sound through the speakers only lasts for about 10
seconds. When I plug the headset in there still no sound in the
headset, but when I unplug the headset the sound through the speakers
resumes but then quits after about 10 seconds.
--
You received this bug notification because
Thanks, but we will need more data points. We need to know at least one
kernel version which does not have the bug (if a version exists). And
then we need to know the earliest version where the bug was introduced.
--
You received this bug notification because you are a member of Ubuntu
Touch
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug. I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross
** Description changed:
+ [Impact]
+
+ ibus-libpinyin has proved to crash far too often. One or more files in
+ ~/.cache/ibus/libpinyin get corrupted somehow, and emptying that
+ directory allows the user to keep using ibus-libpinyin.
+
+ In disco (and eoan) ibus-libpinyin 1.11.0 and libpinyin
** Changed in: network-manager (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1829566
Title:
network-manager
** Changed in: gcc-4.8 (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gcc-4.8 in Ubuntu.
https://bugs.launchpad.net/bugs/1322784
Title:
Firefox crashes in flag_qsort during
Public bug reported:
Don't have details about the issue!
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.18.0-20.21~18.04.1-generic 4.18.20
Uname: Linux 4.18.0-20-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.6
Architecture: amd64
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
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Unfortunately, we cannot work on this bug because your
description didn't include enough information. You may find it helpful
to read "How to report bugs effectively"
Please be sure to only report one problem per bug. We will make this bug
about the first problem you report only.
** Summary changed:
- misc. problems
+ problem with login to user account. Keeps going back to login window
--
You received this bug notification because you are a member of Ubuntu
In theory, adding model=auto (comment #3) doesn't affect your sound
driver since even without model=auto, the audio driver doesn't apply any
fixup models to your machine.
Please do a test:
cd /sys/module/snd_hda_codec
sudo su
echo 1 > parameters/dump_coef
Then test your speaker, when the
In accordance with this: https://docs.slackware.com/howtos:hardware
:audio_and_snd-hda-intel#how_to_find_the_right_options
I ran this: sudo echo "options snd-hda-intel model=auto" >
/etc/modprobe.d/snd-hda-intel.conf and rebooted.
That resulted in both the speakers and headphones working. But
Someone probably needs to find a relevant upstream Xorg bug link to see
where/if it is being discussed there.
This is not the place where Xorg developers discuss such things.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
shut down windos and rebooted Ubuntu.
No Sound
As SU ran echo 1 > parameters/dump_coef
Speaker sound works for about 10 seconds.
The following is the report from alsa-info
!!
!!ALSA Information Script v 0.4.64
!!
!!Script ran
After the sound quit I ran Alsa-info and got the following:
!!
!!ALSA Information Script v 0.4.64
!!
!!Script ran on: Tue May 21 03:48:17 UTC 2019
!!Linux Distribution
!!--
Ubuntu 19.04 \n \l DISTRIB_ID=Ubuntu
60 matches
Mail list logo
