Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: libdrm (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libdrm in Ubuntu.
radeonsi_dri.so comes from mesa, so please try with
ppa:ubuntu-x-swat/updates, which has mesa 19.0.8
which one do you have currently installed? 'apt-cache policy libgl1
-mesa-dri' should tell.. I'm assuming it to be 19.0.2
** Changed in: libdrm (Ubuntu)
Status: Confirmed => Incomplete
**
also, this bug should happen with 19.04 too, but so far I haven't seen
anyone file it
just for reference, the downgrade of libdrm probably helps because the
new version enabled a new feature which the new mesa supports. With old
libdrm the new DRI driver probably can't trigger the failure path.
** Also affects: systemd (Ubuntu)
Importance: Undecided
Status: New
** Changed in: libinput (Ubuntu)
Status: Incomplete => Invalid
** Changed in: linux (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch
Hello Roman, or anyone else affected,
Accepted mesa into bionic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/mesa/19.0.2-1ubuntu1.1~18.04.2 in a
few hours, and then in the -proposed repository.
Please help us by testing this new package. See
The attachment "allow-local-save-more-aggressively.patch" seems to be a
debdiff. The ubuntu-sponsors team has been subscribed to the bug report
so that they can review and hopefully sponsor the debdiff. If the
attachment isn't a patch, please remove the "patch" flag from the
attachment, remove
another idea is to test the new kernel, linux-image-hwe-edge (should be
5.0 from disco)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libdrm in Ubuntu.
https://bugs.launchpad.net/bugs/1837170
Title:
Kodi package crash
Reported upstream as
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/issues/213
** Bug watch added: gitlab.freedesktop.org/NetworkManager/NetworkManager/issues
#213
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/issues/213
** Also affects: network-manager via
patch to enable this feature.
** Patch added: "gzip-as-save2dot-gz.patch"
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1837174/+attachment/5278019/+files/gzip-as-save2dot-gz.patch
** Also affects: oem-priority
Importance: Undecided
Status: New
** Tags added: oem-priority
btw, would be helpful to see if installing linux-image-hwe-edge together
with the bad mesa would still work.. so, ppa-purge the ppa, then install
the edge kernel, reboot
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in
** Also affects: oem-priority
Importance: Undecided
Status: New
** Tags added: oem-priority
** Changed in: oem-priority
Status: New => Confirmed
** Changed in: oem-priority
Importance: Undecided => High
** Changed in: oem-priority
Assignee: (unassigned) => Yuan-Chen
Could you do the logging like in your comment #4 of your question again
but in debug mode, as described on
https://wiki.ubuntu.com/DebuggingNetworkManager
** Changed in: network-manager (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of
** Changed in: network-manager (Ubuntu)
Status: New => Incomplete
** Changed in: linux (Ubuntu)
Status: Confirmed => Incomplete
** Changed in: ubuntu
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages,
Public bug reported:
Here documents from the command line with tabs are not handled
correctly. Here is a transcript showing the problem - there is a tab in
front of "This is indented" in the file:
dzu@zarniwoop:~$ cat tab-test
#!/bin/bash
cat < This is unindented
> This is indented
> STOP
This
Hello Lars, or anyone else affected,
Accepted libsoup2.4 into bionic-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/libsoup2.4/2.62.1-1ubuntu0.3 in a
few hours, and then in the -proposed repository.
Please help us by testing this new package. See
I have just updated mesa from bionic-proposed and now everything is fine
on i386 Ubuntu 18.04:
~# apt-cache policy libgl1-mesa-glx
libgl1-mesa-glx:
Встановлено: 19.0.2-1ubuntu1.1~18.04.2
Кандидат:19.0.2-1ubuntu1.1~18.04.2
Таблиця версій:
*** 19.0.2-1ubuntu1.1~18.04.2 500
500
Does this happen repeatedly since your update, for example at every
boot? If so, could you provide a log of network-manager in debugging
mode, as described on
https://wiki.ubuntu.com/DebuggingNetworkManager
** Changed in: network-manager (Ubuntu)
Status: New => Incomplete
--
You
** Changed in: systemd (Ubuntu Bionic)
Importance: Undecided => Medium
** Changed in: systemd (Ubuntu Bionic)
Assignee: (unassigned) => Louis Bouchard (louis)
** Changed in: systemd (Ubuntu Bionic)
Status: Confirmed => In Progress
--
You received this bug notification because
The attachment "gzip-as-save2dot-gz.patch" seems to be a patch. If it
isn't, please remove the "patch" flag from the attachment, remove the
"patch" tag, and if you are a member of the ~ubuntu-reviewers,
unsubscribe the team.
[This is an automated message performed by a Launchpad user owned by
The attachment "gzip-as-save2dot-gz.patch" seems to be a patch. If it
isn't, please remove the "patch" flag from the attachment, remove the
"patch" tag, and if you are a member of the ~ubuntu-reviewers,
unsubscribe the team.
[This is an automated message performed by a Launchpad user owned by
Please report this bug to Trisquel. Thanks.
** Changed in: network-manager (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
As manual setup of networking also does not work it looks more like a
kernel problem, moving ...
** Package changed: network-manager (Ubuntu) => linux (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager
Please follow the instructions of Thomas Haller in your upstream bug
report.
** Changed in: network-manager (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
Please provide a log of network-manager in debug mode, following the
instructions on
https://wiki.ubuntu.com/DebuggingNetworkManager
** Changed in: network-manager (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
** Changed in: network-manager (Ubuntu)
Status: New => Incomplete
--
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/1793763
Title:
NetworkManager interaction
No. This only happened the one time during the cosmic to disco upgrade.
** Changed in: network-manager (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
vorlon, as it only happens during the Cosmic -> Disco upgrade and Cosmic
is EOL, should we close this then?
** Changed in: network-manager (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
Hello yparitcher, or anyone else affected,
Accepted modemmanager into disco-proposed. The package will build now
and be available at
https://launchpad.net/ubuntu/+source/modemmanager/1.10.0-1ubuntu0.19.04.1
in a few hours, and then in the -proposed repository.
Please help us by testing this new
If mine is the only report of this problem, then yes, it should probably
be closed wontfix.
** Changed in: network-manager (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
excellent, thanks for confirming!
--
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/1836721
Title:
Black screen after updating mesa from 18.2 to 19.0 on i386 Ubuntu
18.04
Closing then. Thanks.
** Changed in: network-manager (Ubuntu)
Status: New => Won't Fix
--
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/1824425
Title:
Public bug reported:
In Ubuntu 18.04 at least, we sometimes get a random server in emergency
mode with a failed mount unit (ext4 file system), while the
corresponding file system is in fact correctly mounted. It happens
roughly once every 1000 reboots.
It seems to be related with this bug :
I wrote a comment on the upstream fixing commit asking if there are
other commits that are required to apply the fix on Poppler 0.62.0, no
answer yet, and I don't think upstream is interested in 0.62.0 any more.
--
You received this bug notification because you are a member of Ubuntu
Touch
Public bug reported:
I have a system connection like this:
-- /etc/NetworkManager/system-connections/eth2 ---
[connection]
id=eth2
uuid=c73fb4d2-8383-4d03-a87c-04c8251961bd
type=ethernet
gateway-ping-timeout=12
interface-name=eth2
permissions=
timestamp=1563551266
[ethernet]
Public bug reported:
Testing failed on:
i386:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/i386/s/systemd/20190719_14_3528c@/log.gz
The storage testcase is failing on i386. Running the testcase manually,
it hangs at:
I confirm that using a valid IP works better:
In the config:
route1=fe80:2::/60,fe80::99,42
# ip -6 route show dev eth2
fe80::/64 proto kernel metric 101 pref medium
fe80::/64 proto kernel metric 256 pref medium
fe80:2::/60 via fe80::99 proto static metric 42 pref medium
It's still missing the
The journal says why:
NetworkManager[1295]: [1563552648.1667] platform: route-sync: failure
to add IPv6 route: 1:2::/60 via 1:2::3 dev 6 metric 42 mss 0 rt-src user: No
route to host (113)
NetworkManager[1295]: [1563552648.1672] device (eth2): failed to apply
manual IPv6 configuration
Nevermind then, this is working well enough for a stable release.
** Changed in: network-manager (Ubuntu Bionic)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
This bug was fixed in the package mesa - 19.0.2-1ubuntu1.1~18.04.2
---
mesa (19.0.2-1ubuntu1.1~18.04.2) bionic; urgency=medium
* i965-revert-enabling-softpin.diff: Don't enable softpin, causes
issues on 32bit installs. (LP: #1836721)
-- Timo Aaltonen Thu, 18 Jul 2019
The verification of the Stable Release Update for mesa 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
I have just ried this again and it is now working.
No changes other than the normal updates.
--
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/1835647
Title:
Saned does not
** Also affects: systemd (Ubuntu Disco)
Importance: Undecided
Status: New
** Also affects: systemd (Ubuntu Eoan)
Importance: High
Assignee: Jorge Niedbalski (niedbalski)
Status: In Progress
** Also affects: systemd (Ubuntu Bionic)
Importance: Undecided
Status:
Thanks for providing a patch for apport. Could you explain to me the use
case for this change a bit more though? Usually apport crash files or
bug reports are sent to Launchpad and / or the Ubuntu Error Tracker.
--
You received this bug notification because you are a member of Ubuntu
Touch
** Also affects: systemd (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: systemd (Ubuntu Disco)
Assignee: (unassigned) => Jorge Niedbalski (niedbalski)
** Changed in: systemd (Ubuntu Bionic)
Assignee: (unassigned) => Jorge Niedbalski (niedbalski)
** Changed
** Changed in: apport (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1837174
Title:
auto compress if save filename ends with .gz
On Fri, Jul 19, 2019 at 04:46:08AM -, Yuan-Chen Cheng wrote:
> Public bug reported:
>
> For command, apport-cli -p PKG -f --save=local-save.log, if the PKG is a
> local test one, it won't save the log.
>
> Let's skip package check if --save option is used.
The check to see if the package is
This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:
apport-collect 1837235
and then change the status of the bug to 'Confirmed'.
If, due to the
Also, not only is "Discoverable" left on, "Discovery" is left on. If
someone goes to Bluetooth Settings, Discovery is turned on (started) and
can only be turned off (stopped) by disconnecting BT adapter or reseting
bluetooth.service. This leads to hundreds of detected devices per
minute in a
Public bug reported:
$ journalctl -b
[...]
[3.786804] systemd[1]: Failed to bump fs.file-max, ignoring: Invalid
argument
ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: systemd 240-6ubuntu9
ProcVersionSignature: Ubuntu 5.2.0-8.9-generic 5.2.0
Uname: Linux 5.2.0-8-generic x86_64
** Changed in: apport (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1837173
Title:
shall allow local save even it's neither
That's good news. :) sane-backends was updated yesterday for 18.04 (bug
#1728012). I didn't realize that that change applies to your problem
description, but apparently it does (somehow).
Closing this bug then.
** No longer affects: systemd (Ubuntu)
** Changed in: sane-backends (Ubuntu)
I've found a different problem situation:
I first applied the downgrade of libdrm-amdgpu1 2.4.97-1ubuntu1~18.04.1 to
2.4.95-1ubuntu1~18.04.1, on the first launch of a newly installed Ubuntu
18.04.2 without any of the 400 updates packages available.
This way I got package Kodi working.
Now,
Hi, I don't believe this is a cloud-init bug. Cloud-init wrote the two
certificate files requested.
2018-05-02 08:55:00,913 - stages.py[DEBUG]: Running module ca-certs () with
frequency once-per-instance
2018-05-02 08:55:00,914 - handlers.py[DEBUG]: start:
init-network/config-ca-certs:
I'm marking the cloud-init task invalid; I don't believe cloud-init did
anything wrong; but please set the task back to New if you have new
information showing that cloud-init didn't do something quite right.
** Changed in: cloud-init
Status: New => Invalid
--
You received this bug
does it work with linux-image-hwe-edge, which should pull the 5.0 based
kernel backported from disco?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libdrm in Ubuntu.
https://bugs.launchpad.net/bugs/1837170
Title:
Kodi
As I said, the closest package to linux-image-hwe-edge I found for
installation is:
sudo apt install --install-recommends linux-image-generic-hwe-18.04-edge
That gives me the Kernel version
uname -r 5.0.0-20-generic
Unfortunately kodi didn't work, only with the removal of mesa-vdpau-
drivers.
** Changed in: systemd (Ubuntu Disco)
Importance: Undecided => High
** Changed in: systemd (Ubuntu Bionic)
Importance: Undecided => High
** Changed in: systemd (Ubuntu Xenial)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Touch
** Patch added: "lp1668771-eoan.debdiff"
https://bugs.launchpad.net/systemd/+bug/1668771/+attachment/5278115/+files/lp1668771-eoan.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
--
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/1668771
Title:
systemd-resolved negative caching for extended period of time
Status in systemd:
New
Status in systemd
The attachment "lp1668771-eoan.debdiff" seems to be a debdiff. The
ubuntu-sponsors team has been subscribed to the bug report so that they
can review and hopefully sponsor the debdiff. If the attachment isn't a
patch, please remove the "patch" flag from the attachment, remove the
"patch" tag,
[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
Public bug reported:
I'm running Ubuntu 114.04 on a 32-bit Lenovo T61.
When I try to launch alacarte from the menus or from the command line I get
$ alacarte
Traceback (most recent call last):
File "/usr/bin/alacarte", line 23, in
from Alacarte.MainWindow import main
File
** Tags removed: need-duplicate-check
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pygobject in Ubuntu.
https://bugs.launchpad.net/bugs/1837266
Title:
package python-gi 3.12.0-1ubuntu1 failed to install/upgrade:
I've tested Ubuntu Studio Bionic Beaver 18.04, and since it receives all the
same updates from default Ubuntu, the results were identical.
As to disco dingo, I really prefer to go with the more polished LTS versions as
a personal choice of mine.
--
You received this bug notification because
64 matches
Mail list logo
