Here's information about submitting alsa bugs:
http://alsa-project.org/main/index.php/Bug_Tracking
--
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/1773167
Title:
[Intel
[Expired for ubuntu-themes (Ubuntu) because there has been no activity
for 60 days.]
** Changed in: ubuntu-themes (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-themes in
Exact same problem here. I assume the quirk added was for the previous
version of headphone firmware.
--
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/1773697
Title:
This bug was fixed in the package llvm-toolchain-6.0 -
1:6.0-1ubuntu2~16.04.1
---
llvm-toolchain-6.0 (1:6.0-1ubuntu2~16.04.1) xenial; urgency=medium
* Backport to xenial. (LP: #1772632)
- Don't build the Fuzzer library on powerpc.
- set BINUTILS_GOLD_ARCHS to match 4.0,
The verification of the Stable Release Update for llvm-toolchain-6.0 has
completed successfully and the package has now been released to
-updates. Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you
This bug still exists on xubuntu 18.04 why not fixing this once and for
all after all the years ??? is this really important to show this
warning or only to warn people ??? what can they do to avoid this
message ? update database ? what command-line to do so ?. Though it's
just a warning message,
[Expired for xorg (Ubuntu) because there has been no activity for 60
days.]
** Changed in: xorg (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
Public bug reported:
Only Ubuntu Update
ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: python3 3.6.5-3ubuntu1
ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
Uname: Linux 4.15.0-22-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
Date: Thu Jun 28 22:51:28
Nothing was done. The comment:
Changed in systemd:
status: Unknown → Fix Released
is an unfortunate bug in Launchpad. It was briefly tracking:
https://github.com/systemd/systemd/issues/9431
which is now closed so Launchpad thought that means "fixed".
If you scroll up you will find
** Tags removed: need-duplicate-check
--
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/1779237
Title:
package python3 3.6.5-3ubuntu1 failed to install/upgrade:
Public bug reported:
Affected Ubuntu Release: Ubuntu 18.04 LTS
Installed Package Version: 0.96.24.32.3
Upon clicking on a trusted software provider in the Authentication tab,
and then clicking "Remove" will prompt for a password and do absolutely
nothing. I would expect this to remove a software
Public bug reported:
On a ThinkPad 470s it takes ~ 40 seconds to gain connectivity on wake or
startup.
The log seems to incidate that there is first a 10 second delay in the
kernel recognising the USB device and assigning a serial port to it, and
then it takes ModemManager 20 seconds to open the
Daniel - please explain what was done to resolve.
--
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/1745664
Title:
[regression] systemd-logind crashed with SIGABRT in
An approximation of the packages that need to be fixed individually are listed
here:
https://lintian.debian.org/tags/maintainer-script-calls-systemctl.html
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unattended-upgrades
Fix is pending: https://github.com/mvo5/unattended-upgrades/pull/131
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unattended-upgrades in
Ubuntu.
https://bugs.launchpad.net/bugs/1779157
Title:
Public bug reported:
Running 18.04, systemd 237-3ubuntu10, and all of my available disk space
on /var (4.3G) just got eaten up by systemd-journald.
/etc/systemd/journald.conf has all the default values (everything
commented out). Processes were starting to crash, and I only recovered
by running
Closing per reporter’s feedback; not a bug anymore.
** Changed in: bash (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bash in Ubuntu.
https://bugs.launchpad.net/bugs/455219
Title:
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
Reassigning to the kernel since rsync should never be able to crash the
system and if it crashes it's usually the kernel or bad hardware that's
responsible.
** Package changed: rsync (Ubuntu) => linux (Ubuntu)
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: mesa (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
Then I guess tis is fixed now.
** Changed in: amd64-microcode (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu.
https://bugs.launchpad.net/bugs/1386257
I have built a test ppa with the fix [1].
That fixes the issue for me, I'd need a review [2] to feel confident
going forward but it LGTM.
[1]: https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/3309
[2]:
** Merge proposal linked:
https://code.launchpad.net/~paelzer/ubuntu/+source/slang2/+git/slang2/+merge/348667
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to newt in Ubuntu.
https://bugs.launchpad.net/bugs/1537528
Title:
Sorry, few typos in the script
** Description changed:
[Impact]
System lock unrefing is broken, off-by-one error. Locking twice opens a
second fd for the lock file, and the old fd gets lost and remains open for the
remaining duration of the program
[Test case]
Executing the
If you can point to where upstream have fixed it please, then we would
have something to work on. Unfortunately I'm not sure we can make any
progress without that.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openldap in
It looks like this bug has gathered quite a bit of attention since it
was first filed, so let me set some expectations here.
The trouble with patching Ubuntu is that then we're on the hook for
maintaining those patches indefinitely. This can cause a great deal of
pain if future upstream
** Description changed:
+ [Impact]
+
+ * Backport Debian fix for a crash in byobu due to libslang2
+
+ [Test Case]
+
+ * byobu-screen
+ * in there hit F9 or start byobu-config
+ * without the fix this crashes
+
+ [Regression Potential]
+
+ * This is changing a libs implementation and
+
I don't think they have: my ticket is still open with them too. :(
--
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/1547927
Title:
LDAP_OPT_X_TLS_REQUIRE_CERT handling
Updated the Debian bug so they are aware as well.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to newt in Ubuntu.
https://bugs.launchpad.net/bugs/1537528
Title:
byobu-config segfault with screen backend
Status in byobu
I checked once more to be sure, artful (and later) is ok
** Changed in: slang2 (Ubuntu)
Status: New => Triaged
** Also affects: newt (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: slang2 (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also
Public bug reported:
It happened like this:
using kernel 3.13.0-144 (14.04) - ok
jun 9: installed kernel 3.13.0-149 and rebooted - ok
jun 21: installed some updates including update to the cpu microcode which was
set up to execute at the next boot
jun 28: rebooted to the same kernel 149 and the
Since Cosmic is still open and auto-syncing I prepared that as fix [1]
for Debian to sync it in.
[1]: https://salsa.debian.org/ssh-team/openssh/merge_requests/2
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in
I rolled back the amd64-microcode to the previous version
(3.20180524.1~ubuntu0.14.04.1 to 2.20131007.1+really20130710.1) and it
resolved the issue, I can now boot to 151, so it is definitely related
to amd64-microcode. I am using AMD Phenom(tm) II X4 975 Processor
** Package changed: xorg
thanks for testing, marking as verified
** Tags removed: verification-needed verification-needed-xenial
** Tags added: verification-done verification-done-xenial
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libdrm in
QA also tested Intel platform below:
CPU/GPU:
- Intel(R) Pentium(R) Silver J5005 CPU @ 1.50GHz
- Intel Corporation Device 3184 (rev 03)
Xorg:
ii python3-xkit 0.5.0ubuntu2
all library for the manipulation of xorg.conf files
Verified. The first dirmngr started by 1.6.1 stayed alive even after
1.6.2 finished executing; the dirmngr started by 1.6.2 was not alive
anymore.
+ lxc launch -e ubuntu:bionic lp1773992-bionic
Creating lp1773992-bionic
The verification of the Stable Release Update for rfkill has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a
** Also affects: slang2 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to newt in Ubuntu.
https://bugs.launchpad.net/bugs/1537528
Title:
byobu-config segfault with screen
This got fixed in the cosmic seeds in https://git.launchpad.net/~ubuntu-
core-dev/ubuntu-
seeds/+git/ubuntu/commit/?id=764ab69745c53d8009b7cf9317df1fd9e26bbca2
and in bionic with https://git.launchpad.net/~ubuntu-core-dev/ubuntu-
** Changed in: python3-defaults (Debian)
Status: New => Fix Released
--
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/1768379
Title:
python3-minimal should
=== bionic OK (1.6.1 -> 1.6.2) =
+ lxc launch -e ubuntu:bionic lp1778547-bionic
Creating lp1778547-bionic
Starting lp1778547-bionic
+ sleep 5
+ lxc exec lp1778547-bionic -- sh -c 'apt-cache policy libapt-pkg5.0 | grep
Inst ; python3 /home/jak/a.py'
Installed: 1.6.1
*** This bug is a duplicate of bug 1569522 ***
https://bugs.launchpad.net/bugs/1569522
Seems duplicate of non-private (public) bug #1099766:
https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1099766
--
You received this bug notification because you are a member of Ubuntu
Touch
Still happens on Ubuntu 18.04.
Maybe duplicate of bug #1099766 (and in turn of bug #1569522)?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to modemmanager in Ubuntu.
https://bugs.launchpad.net/bugs/1099766
Title:
Hello Timo,
QA tested A+A platforms below, and user can login to the system via Graphics
mode.
AMD CPU/GPU:
- AMD PRO A12-9800E R7, 12 COMPUTE CORES 4C+8G
- Advanced Micro Devices, Inc. [AMD/ATI] - 1002:9874
AMD CPU/GPU:
- AMD E2-9000 RADEON R2, 4 COMPUTE CORES 2C+2G
- Advanced Micro Devices,
** Changed in: xserver-xorg-video-amdgpu-hwe-16.04 (Ubuntu)
Status: New => Invalid
** No longer affects: xserver-xorg-video-amdgpu (Ubuntu)
** No longer affects: xserver-xorg-video-amdgpu (Ubuntu Xenial)
** No longer affects: xserver-xorg-video-ati (Ubuntu)
** No longer affects:
** Description changed:
- When "apt-get update" is run on a docker container running Ubuntu v16.04
- and containing an additional apt source repository hosted on an https
- webserver, the "apt-get update" command hangs.
+ [Impact]
+ Two or more sources with an unknown protocol cause apt update to
*** This bug is a duplicate of bug 1652282 ***
https://bugs.launchpad.net/bugs/1652282
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: gparted (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of
This bug was fixed in the package rfkill - 0.5-1ubuntu3.1
---
rfkill (0.5-1ubuntu3.1) xenial; urgency=medium
* postinst: do not fail in case udev is not available (e.g. chroot)
(LP: #1777476)
-- Gianfranco Costamagna Mon, 18 Jun 2018
17:53:33 +0200
** Changed in: rfkill
** Description changed:
+ [Impact]
+
+ * It should be possible to change DRM driver without rebooting.
+ * It should be possible to correctly suspend & resume, whilst preserving
driver state.
+ * This bug is for userspace/logind fixes, required to get above working.
+ * Related kernel
I had to tweak the time outs a bit, as I quickly get some errors from
the networking stack (like 7s or so), but I could successfully verify
the fix now, using a standard ubuntu:bionic lxd container, and modifying
the routes, and setting a lower timeout:
+ ip r del default
+ ip r add default via
** Tags added: upgrade-software-version
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python2.7 in Ubuntu.
https://bugs.launchpad.net/bugs/1778960
Title:
SRU: Update python 2.7 to the final 2.7.15 release
Status in
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: alsa-driver (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
Public bug reported:
package python3-dev 3.6.5-3ubuntu1 failed to install/upgrade: problemy z
zależnościami - pozostawianie nieskonfigurowanego
ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: python3-dev 3.6.5-3ubuntu1
ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18
Uname:
Public bug reported:
i was installing latex-maker and as it ended i got that error.
ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: libfdisk1:amd64 2.31.1-0.4ubuntu3 [modified:
lib/x86_64-linux-gnu/libfdisk.so.1.1.0]
ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
Uname:
Verified now, despite me not changing my verification script. Odd.
with 1.2.26, it times out:
+ lxc exec lp1762766-xenial -- sh -c 'apt-cache policy apt libapt-pkg5.0 | grep
Inst ; timeout 5s apt update'
Installed: 1.2.26
Installed: 1.2.26
0% [Working]+ lxc stop lp1762766-xenial
huh, why did it say backports? Me looks again, and sees the package.
--
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/1762766
Title:
apt-get update hangs when
No package in proposed yet.
curl http://archive.ubuntu.com/ubuntu/dists/xenial-backports/main
/binary-amd64/Packages.xz | xzcat | grep ^Package
does not show apt. odd.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in
Hello Seth, or anyone else affected,
Accepted python3-defaults into artful-proposed. The package will build
now and be available at
https://launchpad.net/ubuntu/+source/python3-defaults/3.6.3-0ubuntu3 in
a few hours, and then in the -proposed repository.
Please help us by testing this new
Hello Seth, or anyone else affected,
Accepted python3-defaults into bionic-proposed. The package will build
now and be available at
https://launchpad.net/ubuntu/+source/python3-defaults/3.6.5-3ubuntu1 in
a few hours, and then in the -proposed repository.
Please help us by testing this new
Last time I tried to reproduce this with a C program I was not
successful, hence why I haven't been able to work on this from the
upstream side. I will try again... Martin, it would be *very* helpful if
you could post code or a script that demonstrates the issue in an
automated way. I know you
** Description changed:
The Ubuntu Error Tracker has been receiving reports about a problem regarding
unattended-upgrades. This problem was most recently seen with package version
1.1ubuntu1.18.04.1, the problem page at
Public bug reported:
The Ubuntu Error Tracker has been receiving reports about a problem regarding
unattended-upgrades. This problem was most recently seen with package version
1.1ubuntu1.18.04.1, the problem page at
https://errors.ubuntu.com/problem/9b1b98279fa2b503abb1b1b69bec0cabf647be0c
I am having a similar problem after upgrading to 18.04 on a Dell
Precision M4600, with the following specs:
- Intel Core i7 2640M
- NVidia Quadro 2000M
I have disabled Bluetooth entirely, because I don't need it. But the
NVidia loading/unloading (add/remove) in udev keeps persisting. I can
62 matches
Mail list logo
