[Expired for alsa-driver (Ubuntu) because there has been no activity for
60 days.]
** Changed in: alsa-driver (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in
[Expired for network-manager (Ubuntu) because there has been no activity
for 60 days.]
** Changed in: network-manager (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
This may fix the issue:
https://lore.kernel.org/lkml/20191002121808.59376-1-c...@endlessm.com/
--
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/1846140
Title:
Please describe the kind of problem you are experiencing.
** Package changed: xorg (Ubuntu) => ubuntu
** Changed in: ubuntu
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
If we use 5.0 generic kernel, the kernel should load the legacy hda
driver because there is no sof driver in the 5.0 generic kernel.
For this problem, the legacy hda driver is not loaded, maybe users
forget to install linux-modules-extra-
--
You received this bug notification because you are a
Public bug reported:
Sorry I don't understand
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18
Uname: Linux 4.15.0-38-generic x86_64
.tmp.unity_support_test.0:
ApportVersion: 2.20.9-0ubuntu7.4
Architecture:
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
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/1846140
Title:
Realtek RTL8723BU doesn't work
xenial version working fine.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to freetype in Ubuntu.
https://bugs.launchpad.net/bugs/1769132
Title:
ubuntu18.04's libfreetype6 2.8.1 has a bug of rendering bitmap font
Status in
the latest autopkgtest retries show that the problem is present in the
release pocket, so I have hinted away the failure and am closing the
tasks on the reverse-dependencies, since they will no longer be blocked.
** Changed in: python-cryptography (Ubuntu)
Status: New => Invalid
**
Hello Christopher, thank you for opening this bug and helping make
Ubuntu (and coreutils!) better.
I am somewhat confused here. Are you suggesting a change in wording?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
It's still broken, even though I haven't received any suggestions on what to
try.
Sometimes the network is lost when resuming after suspend, sometimes, just
because it feels like it.
** Changed in: network-manager (Ubuntu)
Status: Expired => New
--
You received this bug notification
Network shutdown still happens in Ubuntu 19.10.
--
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/1838836
Title:
network-manager needs to be restarted frequently
@gunnarl, did your audio work correctly in kernel 5.0.0-29, and broke when you
updated to 5.0.0-31?
If you boot 5.0.0-29 by selecting it in grub when you turn your computer on,
does your audio work?
Might this be related to Bug 1846991?
--
You received this bug notification because you are a
This bug was fixed in the package binutils - 2.33-1ubuntu1
---
binutils (2.33-1ubuntu1) eoan; urgency=medium
* Don't generate control file entries for any native mips* packages.
binutils (2.33-1) unstable; urgency=medium
* Binutils 2.33 release (taken from the binutils-2_33
Given the tests pass locally in a container (autopkgtest ... -- lxd
ubuntu-daily;eoan), I'm trying a bileto run
(https://bileto.ubuntu.com/#/ticket/3818) to see if that reproduces the
test failure. If yes, then I can use that platform for troubleshooting.
--
You received this bug notification
** Tags added: bionic-openssl-1.1
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssl in Ubuntu.
https://bugs.launchpad.net/bugs/1835464
Title:
nginx service fails after libssl update due to low entropy at boot
Status
Public bug reported:
At my company we prepare system disk images which start from deboostrap
pointing at an internal mirror containing packages from xenial, xenial-
updates, and elsewhere. As of September 30, our image preparation begun
failing during the initial debootstrap.
We narrowed it down
> During the upgrade which was done using Wi-Fi, the connection went
down but it was after the download completed so the upgrade ended.
sorry, it's not clear to me, are you saying the upgrade completed
successfully?
And do you mean that currently, your dns does not work?
--
You received this
On a prior OS (16.04 or 18.04, cannot remember which) the following
rsync -v -a -r -W -p -o -g -t --delete --stats ~/Pictures /media/$USER
/USB-128GB-1/ >bkp_log
would only send differences on subsequent runs with a fat32 USB key.
Your test above seems to indicate that subsequent runs on 19.04
Thanks @cktenn - I commented there and also opened
https://salsa.debian.org/systemd-team/systemd/merge_requests/56, but I
have not tested with that, can you see if that fixes this problem?
Assuming I'm understanding the problem correctly, that you just want 73
-special-net-names.rules to ignore
Reported upstream on https://github.com/FFTW/fftw3/issues/182 , with
some luck they have an idea about the bug
** Bug watch added: github.com/FFTW/fftw3/issues #182
https://github.com/FFTW/fftw3/issues/182
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
@Dan
I've submitted a merge request to Debian that only applies to Dell
system the idea mentioned in comment #4, it modifies the rule 73
-special-net-names.rules.
https://salsa.debian.org/systemd-team/systemd/merge_requests/55
Please help to review this.
--
You received this bug notification
I have run 2 test scenarios.
A trivial folder containing 3 text files as source.
A real world case of ~/ as source.
Both cases work as expected on an LUKS encrypted ext4 USB key.
I will do some more testing on fat32 and report back.
--
You received this bug notification because you are a
The fix for this bug has been awaiting testing feedback in the -proposed
repository for disco for more than 90 days. Please test this fix and
update the bug appropriately with the results. In the event that the
fix for this bug is still not verified 15 days from now, the package
will be removed
Trying to debug a bit on a canonistack instance
==5906== Command: ./bench --verify ofr108*118
==5906==
==5906== Invalid write of size 8
==5906==at 0x49174A8: vst1_f32 (arm_neon.h:10876)
==5906==by 0x49174A8: ST (simd-neon.h:119)
==5906==by 0x49174A8: n1fv_9 (n1fv_9.c:230)
==5906==
The fix is included in Qt 5.11, so I am marking it as affecting only
Bionic.
** Also affects: qtbase-opensource-src (Ubuntu Bionic)
Importance: Undecided
Status: New
** Changed in: qtbase-opensource-src (Ubuntu)
Status: New => Fix Released
--
You received this bug notification
@cktenn that could work (using special-net-names), however I'm concerned
that the rule should not apply to all r8152 devices, everywhere, on
everyone's systems. It should apply *only* on Dell systems where this
magical MAC passthrough is enabled. What can be checked to see if the
system is a
Verified with systemd/237-3ubuntu10.31:
ubuntu@ubuntu-Standard-PC-i440FX-PIIX-1996:~$ sudo vi /etc/crypttab
ubuntu@ubuntu-Standard-PC-i440FX-PIIX-1996:~$ sudo systemctl daemon-reload
ubuntu@ubuntu-Standard-PC-i440FX-PIIX-1996:~$ sudo service
systemd-cryptsetup@vdb_crypt start
Please enter
Yes, based on the analysis that the failure is caused by buggy *rm
scripts in an obsolete and already-uninstalled version of the systemd-
shim package, I expected to still see failures with the new version.
But this should not block the SRU, even though the Conflicts is not
actually doing
Newer firmwares [1] may be required.
[1] https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-
firmware.git/
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1823076
** Also affects: kmod (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to kmod in Ubuntu.
https://bugs.launchpad.net/bugs/1722478
Title:
Two-finger scrolling and
This isn't "just" a bug, it's a roadmap item in my view, as many
products are affected. It needs a spec, like in the fedora case. I agree
that it would be awesome to have this.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
Verified with systemd/237-3ubuntu10.31:
root@x-lp1773859:~# systemctl show systemd-journald.service | grep Watch
WatchdogUSec=0
WatchdogTimestamp=Tue 2019-10-08 16:06:56 UTC
WatchdogTimestampMonotonic=176241732389
root@x-lp1773859:~# dpkg -l systemd
Desired=Unknown/Install/Remove/Purge/Hold
|
https://errors.ubuntu.com/?release=Ubuntu%2018.04=systemd=month=237-3ubuntu10.31
For the record the 16.04 -> 18.04 upgrade issue is still seen:
https://errors.ubuntu.com/?release=Ubuntu%2018.04=systemd=month=237-3ubuntu10.31
While the added Conflicts does work in the test case it does not seem
*** This bug is a duplicate of bug 1778946 ***
https://bugs.launchpad.net/bugs/1778946
This is happening for me as well.
Distributor ID: Ubuntu
Description:Ubuntu 18.04.3 LTS
Release:18.04
Codename: bionic
--
You received this bug notification because you are a member of
Verified with systemd 237-3ubuntu10.31:
root@x-lp1773859:~# apt install ./systemd-shim_10-3_amd64.deb
Reading package lists... Done
Building dependency tree
Reading state information... Done
Note, selecting 'systemd-shim' instead of './systemd-shim_10-3_amd64.deb'
The following package
Thank you Jan!
--
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/1843394
Title:
FTBFS in Eoan - Error: operand type mismatch for `push' - gcc 9.2.1 /
binutils
** Changed in: canonical-identity-provider
Status: New => Won't Fix
** Changed in: ubuntuone-servers
Status: New => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntuone-credentials in
Ubuntu.
no-one knows what to backport
--
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/1837170
Title:
Kodi package crash after the update of libdrm-amdgpu1
Status in mesa package in
When using vfat and running rsync twice, this is the diff in the stats output:
--- log1.vfat 2019-10-08 11:43:04.381667860 -0300
+++ log2.vfat 2019-10-08 11:43:17.609728451 -0300
@@ -1,5 +1,5 @@
Number of files: 78 (reg: 77, dir: 1)
-Number of created files: 77 (reg: 77)
+Number of created
To ellaborate, this is used by initramfs-tools-ubuntu-core as needed by
snapd for the Ubuntu Core product.
If that is all true, imho snappy team should be the bug subscriber and
drive the MIR to completion.
If it doesn't use/need abootimg the dependency should be dropped.
--
You received this
According to the logs in the #1, there is no obvious errors.
Please open the gnome-sound-setting, then plug a headphone, does the
headphone shows up in the UI after you plug the headphone.
If a headphone shows up, then select that headphone from UI, and play
some sound to headphone, if there is
** Tags added: disco eoan
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1597415
Title:
systemd-udevd: Error calling EVIOCSKEYCODE on device node
'/dev/input/event9'
** Tags added: eoan
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to wpa in Ubuntu.
https://bugs.launchpad.net/bugs/1826639
Title:
wpasupplicant: unknown keys in no-mac-addr-change.conf
Status in wpa package in Ubuntu:
** Changed in: base-files (Ubuntu)
Status: New => Triaged
** Changed in: base-files (Ubuntu)
Importance: Undecided => Low
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to base-files in Ubuntu.
verified with 237-3ubuntu10.31:
root@bb-lp1670291:~# dpkg -l systemd
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version
I also set verification-done, since it is verified that the bug does not
occur with .31 .
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1784454
Title:
kernel panic on
@frank-heimes, thank you for the testing and also for your additional comments.
This fix was once accepted to bionic-proposed, while it does not have a test
case in the bug description nor the description follows the SRU template:
https://wiki.ubuntu.com/StableReleaseUpdates#SRU_Bug_Template .
there's a lot of people subscribed to this bug, and presumably
interested in seeing it fixed on Bionic; can any of you please test with
the package from bionic-proposed and report the results? Until you do,
it's unlikely this fix will be released into bionic-updates.
See
** Changed in: openldap (Debian)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openldap in Ubuntu.
https://bugs.launchpad.net/bugs/1821343
Title:
slapd process failure is not detected
The fix is trivial, so this should be fine.
But I'm just back from PTO and a bit swamped by TODOs right now, so bear with
me as I'll need some time :-)
** Also affects: rsyslog (Ubuntu Disco)
Importance: Undecided
Status: New
** Also affects: rsyslog (Ubuntu Bionic)
Importance:
*** This bug is a duplicate of bug 1734290 ***
https://bugs.launchpad.net/bugs/1734290
** This bug has been marked a duplicate of bug 1734290
ecryptfs decrypts home AFTER systemd user daemon is loaded. trouble ensues…
--
You received this bug notification because you are a member of
** Changed in: debian-installer (Ubuntu)
Status: In Progress => Invalid
** Changed in: lvm2 (Ubuntu)
Status: In Progress => Invalid
** Changed in: debian-installer (Ubuntu)
Assignee: Rafael David Tinoco (rafaeldtinoco) => (unassigned)
** Changed in: lvm2 (Ubuntu)
Now after we have understood it we know the fix is actually in binutils.
Furthermore any other third party code (or even a few other FTBFS in Eoan)
could be due to that.
IMHO that is a high prio to fix before Eoan as it would not be a new bug bur a
regression.
I'll set it as critical, but it is
persists:
https://launchpad.net/ubuntu/+archive/test-rebuild-20190906/+build/17546506
** Changed in: fftw3 (Ubuntu Eoan)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to fftw3 in
None of them, I cannot also record anything, the alc662 rev 2 analog realtek
audio device does not work at all
Il lunedì 7 ottobre 2019, 06:25:41 CEST, Hui Wang
ha scritto:
Do you mean the you can't hear sound from headphone or lineout jack?
--
You received this bug notification
I'm experiencing this issue with Ubuntu 19.04
resolvconf version: 1.79ubuntu13
Oct 6 21:30:19 miranda systemd[1]: Failed to start
resolvconf-pull-resolved.service.
Oct 6 21:30:19 miranda systemd[1]: resolvconf-pull-resolved.service: Start
request repeated too quickly.
Oct 6 21:30:19 miranda
** Changed in: grub2 (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lvm2 in Ubuntu.
https://bugs.launchpad.net/bugs/1838525
Title:
LVM setup fails to install grub on
Pushed to
https://git.launchpad.net/~ubuntu-core-
dev/grub/+git/ubuntu/commit/?id=ef72a249cac219fee2ce5dec9648bb9717b16b30
Test-buiding, and uploading.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lvm2 in Ubuntu.
** Also affects: python3-defaults (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python3-defaults in
Ubuntu.
https://bugs.launchpad.net/bugs/1846506
Title:
autopkgtest
Thanks Rafael, Andreas and everybody for the great work done here! I
successfully tested your fix as follows:
1. Followed the steps in the original description of this
bug up the point where the installer tries to install
grub to /dev/mapper and fails.
2. Replaced
Public bug reported:
The motd-news script etc/update-motd/50-motd-news
the following section
```
# Loop over any configured URLs
for u in $URLS; do
# Ensure https:// protocol, for security reasons
case $u in
https://*)
true
Those fixes are in 1.20.4 which has been uploaded/is in the review
queue, unsubscribing sponsors
** Changed in: network-manager (Ubuntu)
Status: Confirmed => Fix Committed
** Changed in: network-manager (Ubuntu)
Importance: Undecided => Wishlist
--
You received this bug notification
Each time I am upgrading Xenial to Bionic I'm getting exactly the same
message after few minutes:
"*** ntp.conf (Y/I/N/O/D/Z) [default=N] ? "
Can this fix get delivered to Ubuntu Xenial?
ubuntu-release-upgrader-core 1:16.04.26
--
You received this bug notification because you are a member of
** Summary changed:
- package bluez 5.50-0ubuntu2.1 failed to install/upgrade: installed bluez
package post-installation script subprocess returned error exit status 1
+ package bluez 5.50-0ubuntu2.1 failed to install/upgrade: installed bluez
package post-installation script subprocess returned
** Tags removed: need-duplicate-check
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1847201
Title:
package bluez 5.50-0ubuntu2.1 failed to install/upgrade: installed
Public bug reported:
made upgrade using update-manager
ProblemType: Package
DistroRelease: Ubuntu 19.04
Package: bluez 5.50-0ubuntu2.1
ProcVersionSignature: Ubuntu 5.0.0-31.33-generic 5.0.21
Uname: Linux 5.0.0-31-generic x86_64
ApportVersion: 2.20.10-0ubuntu27.1
Architecture: amd64
Date: Tue Oct
When can we expect any update on this issue?
--
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/1837170
Title:
Kodi package crash after the update of libdrm-amdgpu1
Status in
Please test latest mainline kernel:
https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.4-rc2/
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1847176
Title:
[HP ENVY
Added gnome-shell task to reflect the fact that GUI support was (will
be) added in gnome-shell 3.34.1
** Also affects: gnome-shell (Ubuntu)
Importance: Undecided
Status: New
** Changed in: gnome-shell (Ubuntu)
Importance: Undecided => Medium
** Changed in: gnome-shell (Ubuntu)
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1847176
Title:
[HP ENVY Laptop 13-ad1xx, Realtek
apport information
** Attachment added: "PulseList.txt"
https://bugs.launchpad.net/bugs/1847176/+attachment/5295296/+files/PulseList.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
apport information
** Attachment added: "RfKill.txt"
https://bugs.launchpad.net/bugs/1847176/+attachment/5295297/+files/RfKill.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1847176/+attachment/5295295/+files/ProcModules.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1847176/+attachment/5295292/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1847176/+attachment/5295291/+files/Lspci.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1847176/+attachment/5295293/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1847176/+attachment/5295294/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
apport information
** Attachment added: "IwConfig.txt"
https://bugs.launchpad.net/bugs/1847176/+attachment/5295290/+files/IwConfig.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
apport information
** Tags added: apport-collected
** Description changed:
No Sound on laptop speaker after upgrading ubuntu 19.04 a few days ago.
Soundcard is found in alsamixer but only "dummy" is available in gnome
settings.
ProblemType: Bug
DistroRelease: Ubuntu 19.04
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1847176/+attachment/5295289/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
apport information
** Attachment added: "CRDA.txt"
https://bugs.launchpad.net/bugs/1847176/+attachment/5295288/+files/CRDA.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
82 matches
Mail list logo
