Hello
I've verified this -proposed pkg on my local.
#2 on description working fine.
xtrusia@ubuntu:~$ dpkg -l | grep network-manager
ii network-manager1.10.6-2ubuntu1.4
amd64network management framework (daemon and userspace
Merge Proposal review is complete, but waiting on some feedback that
helps to classify the severity and urgency correctly.
Depending on that the options will be:
- actually unimportant: don't SRU it at all
- some reasonable cases exists, but are very rare: SRU it but hold the release
in
** No longer affects: lubuntu-meta (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to software-properties in
Ubuntu.
https://bugs.launchpad.net/bugs/1865906
Title:
software-properties-* import key issue
Status in
@Chris Guiver (guiverc): After opening in the terminal (as root) the
given by you command, I had received a authorization link to Launchpad.
After opening it (I was already logged in into my account), I saw the
Launchpad page with following message:
The information on this page is private.
Please file an upstream bug at intel graphics upstream:
https://gitlab.freedesktop.org/drm/intel/wikis/How-to-file-i915-bugs
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
Also note, if you do test in Lubuntu 19.10, you should also please
execute the following command only once, as it will automatically gather
debugging information, in a terminal:
apport-collect 1865906
When reporting bugs in the future please use apport by using 'ubuntu-
bug' and the name of the
Thank you for reporting this bug to Ubuntu.
Ubuntu 19.04 (disco) and all flavors reached end-of-life on January 23,
2020.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old and you might not be interested
in
Thank you for taking the time to report this bug. It should be noted
that 19.04 is an EOL release for Lubuntu. I am however able to confirm
the same behavior in both Lubuntu 19.10 and 20.04 development release
installed from 20200303 daily media.
** Changed in: software-properties (Ubuntu
** Also affects: software-properties (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to software-properties in
Ubuntu.
https://bugs.launchpad.net/bugs/1865906
Title:
** Changed in: linux-meta-azure (Ubuntu)
Status: New => Fix Released
** Changed in: linux-meta-gcp (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
Symptom unreproducible after glib upgraded to proposed libglib2.0-0
/focal-proposed,now 2.64.0-1 amd64 [installed].
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to glib2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1865907
> It appears we would need a new upstream bug to track this because the
old one didn't go anywhere.
This is not true. The old one did go somewhere: It examined the behavior
and clearly concluded that upstream gnome-terminal is NOT buggy here, it
never was. It's one of the Ubuntu patches that
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: cups (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cups in Ubuntu.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: cups (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cups in Ubuntu.
I've now opened upstream issues about this on the OpenSSL bug tracker.
However, todoodle.com could refresh their certificate chain with an up
to date G2 godaddy SSL certificate chain, instead of the one that ends
on a CA Root certificate which is no longer trustworthy.
** Changed in: openssl
** Bug watch added: github.com/openssl/openssl/issues #11236
https://github.com/openssl/openssl/issues/11236
** Also affects: openssl via
https://github.com/openssl/openssl/issues/11236
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a
So, in their chain of certs that they present there is still an RSA-SHA1
certificate. It shouldn't affect validation, as the other certs in the
chain are sufficient (for example gnutls-cli toodledo.com connects fine)
but it does trip up openssl:
- Certificate[3] info:
- subject `OU=Go Daddy
Lifetimes of more than a year is only implemented by Apple on their
products. Longevity of the certifications do not matter on Ubuntu.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssl in Ubuntu.
I confirm the bug
The bug applies to all the distros I have tried:
Ubuntu; Linux Mint; Manjaro; Fedora; Opensuse etc.
I also tried various DEs: Kde, Gnome, Cinnamon, Xfce, Mate etc.
It's a general problem, not just of mutter and Gnome
The bug exists only with Mesa and Modesetting, if you install
Thanks for your report! I could reproduce the problem, which is a bit
weird because IBus was updated yesterday and the IBus input methods I
tested worked fine then...
Anyway, I see in the error message: "GLib version too old". So I
upgraded the libglib2.0-* packages to version 2.64.0-1 (from
** Description changed:
+ Regression issue caused by recent system updates on Ubuntu 20.04 Focal
+ Fossa (development branch)
+
Many(or to say, most) applications,like eclipse,lazarus,gnome-shell,gedit...
reported below error in syslog or console as,
...
(lazarus-ide:20387): Gtk-WARNING
Public bug reported:
Many(or to say, most) applications,like eclipse,lazarus,gnome-shell,gedit...
reported below error in syslog or console as,
...
(lazarus-ide:20387): Gtk-WARNING **: 00:11:55.562: Loading IM context type
'ibus' failed
(lazarus-ide:20387): Gtk-WARNING **: 00:11:55.566: GModule
For what it's worth, the versions of things in my test computers, all
servers, no GUI:
name: serv-ff (a 20.04 VM, that has not had an update since around February
12th):
initramfs-tools: 0.133ubuntu14
kmod; 26-3ubuntu1
name: s18 (a physical i5-9600K based computer, up to date as of a few days
** Changed in: linux-backports-modules-2.6.31 (Ubuntu)
Status: Confirmed => Won't Fix
--
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/461260
Title:
No sound was
@Marc: Please see my short conversation with Alex on IRC:
https://irclogs.ubuntu.com/2020/02/11/%23ubuntu-desktop.html
I will ask Laney about the current status.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ibus in
Is anyone actively working on the glib2.0 SRUs? We are blocked on them
for our ibus security update...
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ibus in Ubuntu.
https://bugs.launchpad.net/bugs/1844853
Title:
IBus no
All autopkgtests for the newly accepted network-manager (1.10.6-2ubuntu1.4) for
bionic have finished running.
The following regressions have been reported in tests triggered by the package:
systemd/237-3ubuntu10.39 (i386)
Please visit the excuses page listed below and investigate the failures,
All autopkgtests for the newly accepted network-manager (1.10.6-2ubuntu1.4) for
bionic have finished running.
The following regressions have been reported in tests triggered by the package:
systemd/237-3ubuntu10.39 (i386)
Please visit the excuses page listed below and investigate the failures,
All autopkgtests for the newly accepted network-manager (1.10.6-2ubuntu1.4) for
bionic have finished running.
The following regressions have been reported in tests triggered by the package:
systemd/237-3ubuntu10.39 (i386)
Please visit the excuses page listed below and investigate the failures,
It appears we would need a new upstream bug to track this because the
old one didn't go anywhere. Please create one in:
https://gitlab.gnome.org/GNOME/gnome-terminal/issues
or
https://gitlab.gnome.org/GNOME/gtk/issues
and then tell us the URL.
--
You received this bug notification
On 2020-03-03 14:33, Mel wrote:
> Hi Gunnar have updated and no further crash reports
> On ibis
Great! Closing then. Please feel free to submit a new bug report would
the issue re-appear.
** Changed in: ibus (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification
Hi Gunnar have updated and no further crash reports
On ibis
Still dealing with previous bug on dual monitor login
I had this problem on 18.04 and found no resolve
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ibus in
Please find some solution for this bug
** Changed in: alsa-driver (Ubuntu)
Status: Expired => Incomplete
** Changed in: linux (Ubuntu)
Status: Expired => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed
What's the current status of this bug? Where is the fix? One of my
report is made duplicate to this bug but I think this is much older. I'm
using 19.10
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu.
Autopkgtests are complete on the PPA at
https://bileto.ubuntu.com/#/ticket/3962
https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/3962/+packages
Tests all passed or are known force-badtest cases already.
Waiting for Kyle's response to properly handle the severity of this ...
--
You
** Changed in: pulseaudio (Ubuntu)
Status: Fix Released => New
--
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/1865499
Title:
pulseaudio doesn't detect (new) USB
IBus was recently upgraded to 1.5.22-1~exp1ubuntu1. Can you please
update the packages on your system (including IBus):
sudo apt update
sudo apt upgrade
and let us know if the issue is still present.
** Changed in: ibus (Ubuntu)
Status: New => Incomplete
--
You received this bug
Setting the bug as Invalid; temporary issue on mirrors as initially
suspected.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to util-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1863189
Title:
package libuuid1:amd64
Obrigado por confirmar.
** Changed in: util-linux (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to util-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1863189
Title:
package
I tested all versions since 18.04 up to 20.04, in no live session I
could reproduce this problem. Yet this problem occurs in our
installations. The youngest installation is about three weeks old and
has the same bug.
Is there a way to end pulseaudio and prevent it from auto-restarting, so
I can
https://bugzilla.kernel.org/show_bug.cgi?id=201787#c14
Bug is only "fixed" for Swanky and Gnawty chromebooks. They are marked
to use a quirk, as an update breaks sound. To get a fix you should
contact with Hans de Goede (you can in bugzilla) and ask for a fix.
--
You received this bug
Attached is the output of the crashlog from 20.04 after applying the git
settings as detailed in the OP and rebooting - Pulseaudio seems to be
crashing.
** Attachment added: "_usr_bin_pulseaudio.1000.crash"
At that time .. kmod was 26+20191223-1ubuntu1, now kmod is
27-1ubuntu1... Will check if something happened in that upgrade that
made the mkinitramfs change buggy OR its something that was never
covered.
** Changed in: kmod (Ubuntu)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu)
** Information type changed from Private to Public
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ibus in Ubuntu.
https://bugs.launchpad.net/bugs/1865857
Title:
ibus-x11 crashed with SIGABRT in __open_nocancel()
Status
*** This bug is a duplicate of bug 1864992 ***
https://bugs.launchpad.net/bugs/1864992
** This bug has been marked a duplicate of bug 1864992
depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could not open
builtin file '/lib/modules/5.4.0-14-generic/modules.builtin.bin'
--
@dsmythies, @kaihengfeng
you seem to be correct.
First time I saw that issue was in a kmod regression test iirc.
The fix was supposed to be in:
initramfs-tools (0.133ubuntu15) focal; urgency=medium
from:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1863261
but I see now
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1863261
--
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/1864992
Title:
depmod: ERROR: ../libkmod/libkmod.c:515
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1863261
--
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/1864436
Title:
depmod: ERROR: ../libkmod/libkmod.c:515
** Tags removed: hwcert-server
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to software-properties in
Ubuntu.
https://bugs.launchpad.net/bugs/1089389
Title:
juju bootstrap fail behind a proxy when a gpg key must be
Got feedback from one of my colleagues that running Ubuntu 18.04.4 with
Kernel 5.3.0-40, "pkill -U $USER pulseaudio" does not resolve the
problem, only a full restart of the system.
Is there anything I can do to provide additional logs? Running a
debugger when plugging in the headset, logfiles
Thanks. If you can then please also try Ubuntu 19.10
(https://ubuntu.com/download/desktop) so we can get a slightly better
idea of which PulseAudio version introduced the fix.
** Changed in: pulseaudio (Ubuntu)
Status: Incomplete => Fix Released
--
You received this bug notification
Just tested with Ubuntu 20.04, the problem does not occur in the live
session.
--
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/1865499
Title:
pulseaudio doesn't detect
Hello Dan, or anyone else affected,
Accepted network-manager into bionic-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/network-
manager/1.10.6-2ubuntu1.4 in a few hours, and then in the -proposed
repository.
Please help us by testing this new
Hello bugproxy, or anyone else affected,
Accepted network-manager into bionic-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/network-
manager/1.10.6-2ubuntu1.4 in a few hours, and then in the -proposed
repository.
Please help us by testing this new
Hello Dan, or anyone else affected,
Accepted network-manager into bionic-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/network-
manager/1.10.6-2ubuntu1.4 in a few hours, and then in the -proposed
repository.
Please help us by testing this new
Thank you for reporting this bug to Ubuntu.
Ubuntu 19.04 (disco) reached end-of-life on January 23, 2020.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old and you might not be interested
in discussing it any more.
Nothing but i misexplained, bug isn't related to the fact that account exists
or not.
Please try to enter in a tty that exact login :
'username.lastnamelastnamelastn...@domain.fr'
It reset without asking for password, and the error line is added to
auth.log
Then try :
All Ubuntu systems are affected.
That's not related to a personal configuration, booting live latest ubuntu let
me reproduce this.
Its more clear on tty, as you see username field resets, but it's the
same from ligthdm
So should i open a bug for agetty package instead ?
--
You received this
I think bug 1864992 and this one are duplicates.
--
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/1864436
Title:
depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file()
59 matches
Mail list logo
