I purged both xfce4-screensaver and light-locker packages, restarted
lightdm and tested with x-p-m set to suspend on lid-close for battery
(and AC as I've had the battery exhaust several times due to the length
of these tests!)
In this case there is no password challenge dialog on resume.
It fail
** Changed in: gtk+3.0 (Ubuntu)
Importance: Undecided => Low
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1832632
Title:
building from source on Ubuntu 18.04 fails
S
** Changed in: gtk+3.0 (Ubuntu)
Status: New => Triaged
** Changed in: gtk+3.0 (Ubuntu)
Importance: Undecided => Low
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu.
https://bugs.launchpad.net/bugs/
Hi, I have encountered the same problem. Is there a solution?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gstreamer1.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1630137
Title:
gstreamer1.0-vaapi depends on libgstreamer
** Changed in: ubuntu-rtm
Status: New => Won't Fix
** Changed in: ubuntu-rtm
Status: Won't Fix => Opinion
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to adduser in Ubuntu.
https://bugs.launchpad.net/bugs/48734
huh, ok, so actually the cert team mentioned that when they removed the
redirect as well, it just all passed. So I guess the bug is invalid?
Thanks for looking into it Dimitri!
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to o
maxpus=1 still suffers the same issue.
I then disabled and stopped the upower daemon but the issue remains with
the only common factors being systemd-logind and lightdm.
I tried console-only tests with lightdm stopped and CANNOT reproduce the
issue.
I installed sddm and changed the default displ
I am using a bento/ubuntu18.04 box on vagrant/kitchen-ci with the
kitchen-ansible provisioner and can reproduce this bug.
Setting up python-idna (2.6-1) ...
Setting up python-yaml (3.12-1build2) ...
Setting up python-asn1crypto (0.24.0-1) ...
Setting up python-pyasn1 (
Something similar here too, with DBUS crashing out, and not generating a
complete core dump (though plenty of disk and RAM)
un 17 00:10:40 xps15 gjs[2607]: g_object_unref: assertion 'G_IS_OBJECT
(object)' failed
Jun 17 00:10:40 xps15 gjs[2607]: message repeated 8 times: [ g_object_unref:
assert
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: eglibc (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to eglibc in Ubuntu.
https://bugs.launchpad.net
It seems this is also applicable to ubuntu bionic since openssl 1.1.1
landed in bionic-updates. We have bionic clients that cannot connect to
the enterprise wifi because they attempt TLS 1.3. Recompiling openssl
with the "no-tls1_3" Configure option fixes the problem. See also
https://github.com/Fr
> Sadly, there are RADIUS servers which suffer from TLS version
intolerance and will refuse authentication when the client offers TLS
1.3
This statement is completely missing the point. There are *no standards
available* for using TLS 1.3 with *any* EAP method. The IETF is working
on them, but t
** Changed in: openssl (Ubuntu)
Status: Incomplete => Confirmed
--
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/1832919
Title:
installed libssl1.1:amd64 package post
heres btw the netplan config im using:
network:
version: 2
renderer: networkd
ethernets:
enp0s31f6:
addresses: [ 95.216.96.148/26 ]
gateway4: 95.216.96.129
nameservers:
addresses:
- "8.8.8.8"
- "1.1.1.1"
routes:
- to
Thanks for the quick response.
Yesterday to fix the issue, I uninstalled the resolvconf package. I
reinstalled it today, and now it is working with the correct "search"
domain.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
This affects each system where /tmp is *not* on tmpfs which affects a
lot of cloud-built servers and effectively prevents usage of systemd-
analyze verify in Ansible, Puppet etc.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
> Or, you can punt this to me to do and I'll apply these changes when I
have a chance.
Since this bug went to 'expired', I'll take this now, for the subset of
changes I agree are appropriate.
** Changed in: ubuntu-meta (Ubuntu)
Status: Expired => Triaged
** Changed in: ubuntu-meta (Ubuntu
** Changed in: network-manager (Ubuntu)
Status: Incomplete => 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/1790098
Title:
vlan created on bond f
Since our focus is on netplan only, I'm changing the status to Won't
Fix.
** Changed in: ubuntu-z-systems
Status: Incomplete => 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
** Summary changed:
- [Don't release SRU yet]Alt+KEY incorrectly behaves like Ctrl+Alt+KEY, and/or
unwanted VT switch from Alt+Left/Right
+ [SRU]Alt+KEY incorrectly behaves like Ctrl+Alt+KEY, and/or unwanted VT switch
from Alt+Left/Right
--
You received this bug notification because you are a
I've landed these blacklist changes now.
** Changed in: ubuntu-meta (Ubuntu)
Status: Triaged => 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/177079
Does anyone know where this bug is being tracked upstream now? GNOME has
migrated from Bugzilla to GitLab, and I haven't been able to find the
GitLab version of the Bugzilla bug.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
** Merge proposal linked:
https://code.launchpad.net/~smb/ubuntu/+source/iproute2/+git/iproute2/+merge/368924
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to iproute2 in Ubuntu.
https://bugs.launchpad.net/bugs/1831775
Tit
** Description changed:
+ [Impact]
+ motd-news timer is not properly configured and may not run regularly so long
running systems will not get an updated motd
+
+ [Test Case]
+ The system being tested must have curl installed - base-files does not depend
on it because reasons.
+ 1) Run 'systemc
Public bug reported:
chtmax98090 intel HD audio device doesn't work out of the box after
installing ubuntu (from 14.04 to 18.04). It shows "Dummy Output" on
audio devices.
Audio options shows device and it works if I do this:
git clone https://github.com/plbossart/UCM.git
cd UCM
cp -r chtmax9
Currently, the upstream issue has NOT been migrated to GNOME GitLab yet,
but is still being tracked at
https://bugzilla.gnome.org/show_bug.cgi?id=780622
** Bug watch added: bugzilla.gnome.org/ #780622
https://bugzilla.gnome.org/show_bug.cgi?id=780622
--
You received this bug notification bec
It is still an issue in Mint 19.1
--
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/269910
Title:
Netmask automatically changes to 24
Status in network-manager packa
Just got the same bug again in Disco Dingo.
Setting up systemd (240-6ubuntu5.1) ...
[/usr/lib/tmpfiles.d/speech-dispatcher.conf:1] Line references path below
legacy directory /var/run/, updating /var/run/speech-dis
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: openssl (Ubuntu)
Status: New => Confirmed
--
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.n
I can confirm this affects the bionic-updates 1.1.1-1ubuntu2.1~18.04.2
package, therefore a backport to bionic and other affected releases will
be required
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssl in Ubuntu.
htt
For those affected, you can run:
$ echo 'libssl1.1 libraries/restart-without-asking boolean true' |
debconf-set-selections
Previous to attempting to install the package
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ope
Ah, OK, thanks. No news since 2018-08 then - I was hoping the GNOME
GitLab would have something new :(
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dbus in Ubuntu.
https://bugs.launchpad.net/bugs/1685754
Title:
gnome-ter
A workaround seems to be to add two sets of addresses and then delete
the top one (which will have the erroneously saved mas address).
--
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.lau
Yet more results changing the target once again!
I was able to reproduce the issue whilst using sddm which tends to
suggest lightdm may not be the cause.
I also managed to prove (not sure why this did not occur to me before
now!) that the DPMS state is being set 'off' when switching to the GUI
tt
Public bug reported:
Hello to all,
My Ubuntu version is 18.04.02 LTS and I've setup a dual-boot with
windows 10. Speakers and audio jack work totally fine under Windows 10,
but they never work with Ubuntu.
List of some of the things I've tried:
1) I've tried all the steps from the "Sound Troubl
Please edit /etc/modprobe.d/alsa-base.conf and add:
options snd-hda-intel probe_mask=0x1
reboot and check if audio works.
If it works, please remove that line int the alsa-base.conf and install
5.0 kernel to test.
--
You received this bug notification because you are a member of Ubuntu
Touch s
[Expired for openssh (Ubuntu) because there has been no activity for 60
days.]
** Changed in: openssh (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
https://bu
[Expired for software-properties (Ubuntu) because there has been no
activity for 60 days.]
** Changed in: software-properties (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to softw
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]
** Changed in: linux (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in Ubuntu.
https://bugs.l
[Expired for lightdm (Ubuntu) because there has been no activity for 60
days.]
** Changed in: lightdm (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in Ubuntu.
https://bu
[Expired for python2.7 (Ubuntu) because there has been no activity for
60 days.]
** Changed in: python2.7 (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python2.7 in Ubuntu.
http
[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 Ubuntu
linux-oem-osp1 has backports in bionic-proposed
** Changed in: linux-oem-osp1 (Ubuntu Bionic)
Status: New => Fix Committed
** Tags added: verification-needed-bionic
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa
Will anything be done here? This basically breaks keepalived for bionic.
I.e, will keepalived >= 2.0.x be available for bionic?
--
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
44 matches
Mail list logo
