** Package changed: alsa-driver (Ubuntu) => linux (Ubuntu)
--
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/1818025
Title:
ethernet card not detected
Status in linux
Public bug reported:
When trying to start cinnamon-session, gnome-session or mate-session
got the following error in dmesg and system comes back to login screen.
Feb 25 12:21:57 vdc008es kernel: [ 4152.156085] mate-session[9280]: segfault at
7ffec6653f50 ip 7fcc7192f544 sp 7ffec6653f40
Public bug reported:
06:00.0 Network controller: Intel Corporation Wireless 3160 (rev 83)
07:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8101/2/6E PCI
Express Fast/Gigabit Ethernet controller (rev 07) Device: eth0
Device: eth0 -
Type: Wired
Driver:r8169
State: unavailable
Default: no
HW Address:28:F1:0E:27:81:D1
Capabilities:
Carrier Detect: yes
Speed: 100
lucian@lucian-Inspiron-5558:~$ ubuntu-bug
2202
lucian@lucian-Inspiron-5558:~$
[1:1:0228/084403.819496:ERROR:chrome_content_client.cc(325)] Failed to locate
and load the component updated flash plugin.
[3460:3460:0228/084404.655923:ERROR:browser_dm_token_storage_linux.cc(101)]
Error:
On Thu, Feb 28, 2019 at 04:08:09AM -, Edson José dos Santos wrote:
> edson@edson-p6540br:~$ dmesg | grep DENIED
> [ 58.334359] audit: type=1400 audit(1551326278.953:59): apparmor="DENIED"
> operation="open" profile="/usr/lib/snapd/snap-confine"
> name="/opt/eset/esets/lib/libesets_pac.so"
Hi Arnold
The apparmour error message at startup of the ubuntu disk has
disappeared.
The only messages that appear in Eset's event log are these lines below:
28/02/2019 00:57:54 Media control access Unable to unlock removable media
(org.freedesktop.udisks2.filesystem-mount)
28/02/2019 00:56:39
Hi Arnold
It looks like this:
/tmp/esets.sock rw,
/etc/opt/eset/ r,
/etc/opt/eset/** r,
/opt/eset/esets/lib/** mr,
unix,
Ao tentar salvar apareceu a mensage abaixo:
dson@edson-p6540br:~$ sudo su
[sudo] senha para edson:
root@edson-p6540br:/home/edson# gedit
malloc_consolidate(): invalid
** Attachment added: "01-netcfg.yaml.bridge"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1817998/+attachment/5242201/+files/01-netcfg.yaml.bridge
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in
On Thu, Feb 28, 2019 at 03:04:00AM -, Edson José dos Santos wrote:
> Hello Arnold
> unix, (connect, send, receive) peer =
(addr="@2F746D702F65736574732E736F636B00*"),
Excellent, here's the mistake. Remove everything after the comma:
unix,
Then try the reboot again.
--
You received
Public bug reported:
On Nvidia DGX2 system, we configured linux bridge (br0) using host
physical NIC interface and it is using static IP (see below netplan
file). BTW, we are using 18.04.2 based BaseOS and Guest images.
- All KVM guests are being launched using virtual network interface
Hello Arnold
As requested:
# Workaround https://launchpad.net/bugs/359338 until upstream handles stacked
# filesystems generally. This does not appreciably decrease security with
# Ubuntu profiles because the user is expected to have access to files owned
# by him/her. Exceptions to
Any five second delay in name resolution is most likely caused by this
open bug in systemd-resolved:
https://github.com/systemd/systemd/issues/11849
The root cause is a delay when resolved has to downgrade the feature set
of its requests to upstream DNS servers. It correctly discovers a
On Wed, Feb 27, 2019 at 12:59:14PM -, Edson José dos Santos wrote:
> Hi, Arnold
>
> At startup the error message is appearing in apparmor and I would like
> to know how to generate a log to introduce them to you or just the boot
> boot log. In the absence of this I got this other log, where
** Also affects: pulseaudio (Ubuntu)
Importance: Undecided
Status: New
** Changed in: pulseaudio (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
Uploaded for Bionic and Cosmic.
** Description changed:
[Impact]
- * Kernel keystroke auditing via pam_tty_audit.so not working
-
- * When Using the pam_tty_audit with other pam modules(ex, pam_ldap), it
failed in pam_open_session.
-It was triggared by use uninitialized variable in
Don,
I'll take care of patching Bionic and Cosmic, and I will let you handle
Xenial, if you don't mind through the Ubuntu sponsorship.
I have reviewed your Xenial debdiff, and it will need some rework.
The patch requires to be in quilt (debian/patches-applied), and not file
manipulate directly
** Changed in: pam (Ubuntu Bionic)
Assignee: Don van der Haghen (donvdh) => Eric Desrochers (slashd)
** Changed in: pam (Ubuntu Bionic)
Importance: High => Medium
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pam
I have provided a test package to an impacted user for Bionic/18.04LTS.
Here's what has been brought to my attention after this user tried the test
package:
"Test results look good. Keystroke logging audit messages are coming through."
--
You received this bug notification because you are a
Dimitri, if you can have a package for cosmic with the fix built in a
PPA, I would be glad to try it.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to qtbase-opensource-src in
Ubuntu.
https://bugs.launchpad.net/bugs/1776173
@xnox adding you to this bug fyi.
--
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/1817903
Title:
systemd-resolve appends "options edns0" to resolv.conf
Status in systemd
@brian-murray since you commented in comment 3 and thus are familiar
with this bug, and I don't have disco upload rights, please give my MP a
look and merge into disco if you have a chance. I'll SRU to B/C once
it's in D. Thanks.
--
You received this bug notification because you are a member
@drgrumpy can you test the resolvconf package from this ppa to see if it
correctly fixes the problem for you (on a system where you haven't
worked around this by disabling the 'resolvconf-pull-resolved'
service/path, of course):
https://launchpad.net/~ddstreet/+archive/ubuntu/lp1817903
**
** Also affects: systemd (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: systemd (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: systemd (Ubuntu Disco)
Importance: Critical
Assignee: Dan Streetman (ddstreet)
Status: In
** Description changed:
+ [impact]
+
+ systems upgraded from pre-Bionic releases to Bionic or later will
+ continue to use ifupdown/resolvconf for network conf and management, but
+ resolvconf has a new systemd service in Bionic and later that pulls
+ systemd-resolved stub-resolv.conf into its
** Changed in: qtbase-opensource-src (Ubuntu Cosmic)
Status: New => Incomplete
** Changed in: qtbase-opensource-src (Ubuntu Bionic)
Status: New => In Progress
** Changed in: qtbase-opensource-src (Ubuntu Bionic)
Importance: Undecided => Medium
--
You received this bug
It's a shot in the dark, but in my case, pulse sound server (atop of
alsa) seems to have gotten into a mess with an upgrade between 16.04 and
18.04. Post login, removing old / session start user config fixed my
dodgy channel mappings (but not quite the same as crackling, etc):
pulseaudio --kill \
> But in the long term I guess I should move to systemd-networkd as the
> preferred way to set static ip?
that is entirely up to your preferences; ifupdown and resolvconf are
still supported, and included, and you can continue to use them. They
are still the default way to configure the network
Public bug reported:
Many servers are set up to simplify and centralize ssh key management
within a single directory.
This is typically done with the line "AuthorizedKeysFile /somedir/%u".
Much online discussion suggests placing the destination in
/etc/ssh/authorized_keys/%u with 0700 on the
Wish there was a "needs more info" tag or a way to tag bug reports like
this. There's no context as to exactly what the problem is despite the
alsa-info script output being supplied.
It's unfair to maintainers to expect them to fish out the problem.
"Sound bug ubuntu 18.04" is way too generic.
See
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1774904/comments/4.
gnome-control-center should rather add libcanberra-pulse to depends
rather than just recommends.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed
Hi, in my case, I think it was simply a missing package dependency.
Installing the libcanberra-pulse package fixed it for me.
gnome-control should probably add libcanberra-pulse to a proper
dependency rather than just recommends since it's likely common that
people would want to test speakers and
** Merge proposal linked:
https://code.launchpad.net/~ddstreet/ubuntu/+source/resolvconf/+git/resolvconf/+merge/363748
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: pulseaudio (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
Well, if you're a LVM user i recommend to leave ubuntu/debian. I know this
sounds somewhat hard, but this nasty bug inside the ramdisk mouning script
exist now more or less since a year! I can't accept a 30 seconds delay on boot
for nothing and moved on to other distros.
Yes you can fix it
--- Comment From pedro...@br.ibm.com 2019-02-27 16:10 EDT---
I checked this source package:
https://launchpad.net/ubuntu/+source/gdb/8.2.50.20190214-0ubuntu1
If that is indeed the one to be used for 19.04, the patches for this
feature are already included there.
--
You received this
I do not think so, but I may not fully understand what "subtree"
implies.
The realm was initially created with a command equivalent to:
kdb5_ldap_util -D cn=admin,dc=example,dc=com create -subtrees
dc=example,dc=com -r TEST.EXAMPLE.COM -s -H
ldap://ldapserver.example.com
with user entries like:
Yes, it is because of that change.
is the dn outside of the subtree?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to krb5 in Ubuntu.
https://bugs.launchpad.net/bugs/1817955
Title:
Getting new "DN is out of the realm
Hello Christian, or anyone else affected,
Accepted libseccomp into bionic-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/libseccomp/2.3.1-2.1ubuntu4.1 in a
few hours, and then in the -proposed repository.
Please help us by testing this new package.
Hello xantares, or anyone else affected,
Accepted libseccomp into bionic-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/libseccomp/2.3.1-2.1ubuntu4.1 in a
few hours, and then in the -proposed repository.
Please help us by testing this new package.
Public bug reported:
Recently applied security update to 14.04.5 LTS kerberos (1.12+dfsg-
2ubuntu5.4), and started getting errors when adding new principals to
LDAP.
Obfuscated example:
kadmin.local -q "ank -x dn=\"uid=testuser,ou=People,dc=example,dc=com\"
-pw \"dummypass\" testuser"
now
Yes that works, and many thanks for the explanation.
/etc/resolv.conf is now linked to /run/resolvconf/resolv.conf
and contains only the local proxy dns:
$ cat /etc/resolv.conf
# Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
# DO NOT EDIT THIS FILE BY HAND --
Hello Steve,
> * still showing WARNING:Failed to connect to lvmetad. Falling back to
device scanning.
> That is NOT the defining symptom of the bug. This message would always
be shown. The question is whether there is an unreasonable and
unnecessary boot delay after the message is displayed.
I
This is still an issue for me on Ubuntu 18.04. Can mount iPhone 5 via
Nautilus but it doesn't show on Rhythmbox or Banshee.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libimobiledevice in
Ubuntu.
> I do not use NetworkManager as I use fixed ip, so the ip, etc. and dns is/was
> specified in /etc/network/interfaces
ah, ok, so you are not using systemd-networkd then, ok that makes sense
since you upgraded from pre-bionic where ifupdown/resolvconf are the
default. In bionic they have been
** Description changed:
network-manager has a facility to automatically pop up a Captive Portal
of a Wi-Fi network if required for access to the internet through that
network. It does test accesses and on failure it triggers the pop-up.
Unfortunately, this does not work in Cosmic due
** Tags removed: need-duplicate-check
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1817946
Title:
package linux-image-4.15.0-45-generic 4.15.0-45.48 failed to
I'm having similar problems with DNS resolution in Bionic Ubuntu-Server.
After configuring the netplan file, with the "local" search suffix, name
resolution works, but I see a 5 second delay for any DNS name ending in
.local.
When watching wireshark during the DIG request, the local system makes
Public bug reported:
network-manager has a facility to automatically pop up a Captive Portal
of a Wi-Fi network if required for access to the internet through that
network. It does test accesses and on failure it triggers the pop-up.
Unfortunately, this does not work in Cosmic due to an upstream
Public bug reported:
package linus-image-4.15.0-45-generic 4.15.0-45.48 failed to
install/upgrade
ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-45-generic 4.15.0-45.48
ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18
Uname: Linux 4.15.0-45-generic x86_64
As far as I can tell, the BIOS is able to see the fingerprint reader --
I just booted into the BIOS and told it to reset the fingerprint data,
and it said that it had done so successfully -- so this appears to be a
Linux-specific issue.
--
You received this bug notification because you are a
Hello Agustin, or anyone else affected,
Accepted gnome-control-center into bionic-proposed. The package will
build now and be available at https://launchpad.net/ubuntu/+source
/gnome-control-center/1:3.28.2-0ubuntu0.18.04.3 in a few hours, and then
in the -proposed repository.
Please help us by
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: systemd (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
Thanks again for the help
Removed resolvconf:
sudo apt remove resolvconf
reboot
as expected now /etc/resolv.conf is linked to run/systemd/sub-resolv.conf
and contains only:
nameserver 127.0.0.53
options edns0
BUT now I cannot connect to anything, nslookup, ping fails, etc.
$ ping
** Changed in: ubuntu-z-systems
Status: Confirmed => Fix Released
--
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/1775018
Title:
Fix for openssl 1.0.2 backport
I have a new Thinkpad X1 Carbon 6th generation. I can see the
fingerprint reader right next to the trackpad, and the specs say that it
has one, but I don't see it showing up in the output of lspci or lsusb.
Maybe I'm missing it? Maybe it's not supported? Or maybe there's a
hardware issue? I'm not
This bug was fixed in the package openssl1.0 - 1.0.2n-1ubuntu6.2
---
openssl1.0 (1.0.2n-1ubuntu6.2) cosmic-security; urgency=medium
* SECURITY UPDATE: 0-byte record padding oracle
- debian/patches/CVE-2019-1559.patch: go into the error state if a
fatal alert is sent or
This bug was fixed in the package openssl1.0 - 1.0.2n-1ubuntu5.3
---
openssl1.0 (1.0.2n-1ubuntu5.3) bionic-security; urgency=medium
* SECURITY UPDATE: 0-byte record padding oracle
- debian/patches/CVE-2019-1559.patch: go into the error state if a
fatal alert is sent or
Thanks for the attention to this:
DNS servers: 208.67.220.220 (opend dns) and 212.159.6.10 (recommended by
isp)
typical sites: planthealth.co.uk, plus random others...
nslookup and dig ok
ping domain_name gives "Name or service not known"
ping ip ok
FF: Hmmm problem etc...
So this is my
You are right that pam shouldn't lead to gdm not working in any case.
Knowing the context help to define the priority of the issue though.
The initial report/tools indicate that you are on 19.04, fingerprint
authentification should work out of the box there (if you have a
supported reader, which
Ok I have found what the problem is, I think; I suspect that you have
resolvconf installed on your system, which is taking over the
/etc/resolv.conf file, and I think that resolvconf is pulling the edns0
option, but also including external nameserver(s), which is an incorrect
configuration, since
@downgrade, basically
$ dpkg -l | grep 237-3ubuntu10
-> that should give you the list of systemd debs installed
download those from https://bugs.launchpad.net/~ubuntu-security-
proposed/+archive/ubuntu/ppa/+build/16258134
and use 'sudo dpkg -i *.deb'
--
You received this bug notification
*** This bug is a duplicate of bug 1813873 ***
https://bugs.launchpad.net/bugs/1813873
** This bug has been marked a duplicate of bug 1813873
Userspace break as a result of missing patch backport
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
(In reply to Kees Cook from comment #14)
> So I'd like to bring this back up and reiterate the issue: there is no
> benefit to the early truncation, and it actively breaks lots of existing
> software (which is why Debian and Ubuntu have had this fix for 10 years now).
>
> What is the _benefit_ of
> in /run/resolvconf/resolv.conf (link to by /etc/resolv.conf)
in Bionic, resolv.conf links (by default) to /run/systemd/resolve/stub-
resolv.conf; is that what you meant?
Can you paste the contents of your /etc/resolv.conf file here?
--
You received this bug notification because you are a
The patch was merged to master.
I've performed piglit-test and run check totem-app functionality - all looks
good.
I close the card.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
** Changed in: mesa
Status: Confirmed => Fix Released
--
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/1815236
Title:
totem assert failure: totem:
The mentioned patch has landed in master and 19.0 (presumably it is or
will be in 18.3 shortly), is this okay to close?
--
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/1815236
Could you give some examples of DNS lookups that fail for you so we can
try and recreate the issue? Additionally, do you know what DNS servers
you are using?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
** Changed in: pam (Ubuntu Cosmic)
Status: New => In Progress
** Changed in: pam (Ubuntu Cosmic)
Importance: Undecided => Medium
** Changed in: pam (Ubuntu Cosmic)
Assignee: (unassigned) => Eric Desrochers (slashd)
--
You received this bug notification because you are a member
** Also affects: jcommander (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gettext in Ubuntu.
https://bugs.launchpad.net/bugs/1814133
Title:
update to openjdk 11 in
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1817912/+attachment/5242071/+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: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1817912/+attachment/5242072/+files/ProcEnviron.txt
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
** Changed in: alsa-utils (Ubuntu)
Status: New => Confirmed
** Changed
My update was from 237-3ubuntu10.11, which didn't have the problem (12
was never installed)
It seems I cannot easily downgrade via apt or synaptic, as the previous
versions do not seem to be in the repos, can you advise how to do so?
On a different machine on the same network I still have
apport information
** Attachment added: "Dependencies.txt"
https://bugs.launchpad.net/bugs/1817912/+attachment/5242070/+files/Dependencies.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: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1817912/+attachment/5242069/+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
** Also affects: alsa-driver (Ubuntu)
Importance: Undecided
Status: New
** Also affects: alsa-utils (Ubuntu)
Importance: Undecided
Status: New
** Tags added: apport-collected xenial
** Description changed:
An old issue with ALSA is still present in
** Also affects: apache-directory-server (Ubuntu)
Importance: Undecided
Status: New
** Also affects: mavibot (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
So, whether or not I needed to run pam-auth-update, doing so and
enabling fingerprint authentication there should not cause GDM to break,
nor should the other weird behavior I described above be happening.
Having said that, yes, I was trying to enable login with fingerprint. I
googled how to do
An issuue still present in Ubuntu 16.04.5.
```
[15:38:51]
[root@ThinkPad/var/log]#grep "alsa-sink-CX20751/2 Analog" syslog
Feb 27 14:58:50 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog]
alsa-util.c: Function snd_pcm_avail() returns a value that is extraordinarily
large: 370196 байтів
** Description changed:
+ [Impact]
+
+ * Kernel keystroke auditing via pam_tty_audit.so not working
+
+ * When Using the pam_tty_audit with other pam modules(ex, pam_ldap), it
failed in pam_open_session.
+It was triggared by use uninitialized variable in
** Also affects: jackson-dataformat-xml (Ubuntu)
Importance: Undecided
Status: New
** Also affects: jackson-databind (Ubuntu)
Importance: Undecided
Status: New
** Also affects: jackson-core (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug
** Also affects: afterburner.fx (Ubuntu)
Importance: Undecided
Status: New
** Also affects: annotation-indexer (Ubuntu)
Importance: Undecided
Status: New
** Also affects: bridge-method-injector (Ubuntu)
Importance: Undecided
Status: New
** Also affects: elki
Thank you for your bug report, did you try to downgrading the system packages
to see if that resolves the issue?
The previous update has change in dns queries
https://bugs.launchpad.net/ubuntu/+source/systemd/237-3ubuntu10.12
Would be interesting to know if that version already had the problem?
Hi Arnold
I got the apparmor log showing boot error.
Wed Feb 27 09:24:41 -03 2019
[[0;32m OK [0m] Started [0;1;39mShow Plymouth Boot Screen[0m.
[[0;32m OK [0m] Started [0;1;39mForward Password R…s to Plymouth Directory
Watch[0m.
[[0;32m OK [0m] Reached
** Also affects: plexus-io (Ubuntu)
Importance: Undecided
Status: New
** Also affects: fontawesomefx (Ubuntu)
Importance: Undecided
Status: New
** Also affects: libpdfbox2-java (Ubuntu)
Importance: Undecided
Status: New
** Also affects: libsambox-java (Ubuntu)
It seems this breaks dns lookups on some system, see #1817903
--
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/1811471
Title:
local resolver stub fails to handle multiple
Public bug reported:
Mint 19 (Ubuntu 18.04)
Following latest mint update done on 24/02/2019, DNS is broken
nslookup and dig of certain domain names work as expected, ping does not
(ip works but not domain name)
After a day of trial and error, testing I found that the problem lies
with the
** Also affects: jboss-classfilewriter (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gettext in Ubuntu.
https://bugs.launchpad.net/bugs/1814133
Title:
update to
Thanks for your bug report, what do you need pam-auth-update? What are
you trying to configure? Enabling log-in with fingerprint shouldn't
requiring having to fiddle with pam tools on a command line if that's
what you are trying to enable
--
You received this bug notification because you are a
Actually, it's even weirder than that.
I went through all this several times while trying to narrow down the
repro steps, and it's all very bizarre. Somehow I managed to get gdm
working again, and then in a logged in gdm session, I enabled
fingerprint, and exited from pam-auth-update, then ran
Public bug reported:
I ran sudo pam-auth-update, enabled "Fingerprint authentication",
selected "OK", and then rebooted.
GDM wouldn't start after the reboot:
Feb 27 06:29:41 jik-x1 /usr/lib/gdm3/gdm-wayland-session[1551]:
dbus-daemon[1553]: [session uid=121 pid=1553] Activating service
** Changed in: hwe-next
Status: Fix Released => In Progress
--
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/1786574
Title:
remove i2c-i801 from blacklist
Status in
linux/Cosmic should be Fix Released as the fix is already in 4.18 from
upstream.
** Changed in: linux (Ubuntu Cosmic)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to kmod in
@midnightflash
Please provide more details on the issues you see so that we can help you. As
Aaron said, please upload the dmesg from both your X11e and X250.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to kmod in Ubuntu.
Change linux to Fix Released for the same reason.
** Changed in: linux (Ubuntu)
Status: Confirmed => Fix Released
--
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/1802135
Public bug reported:
Description:Ubuntu 16.04.6 LTS
Release:16.04
i had 14.04 LTS and upgraded to this version but this happened which is the
upgrade is not complete and i can't open it normally...i am a newbie to linux
BTW
ProblemType:
** Tags removed: need-duplicate-check
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1817883
Title:
package linux-image-extra-4.4.0-142-generic 4.4.0-142.168
Public bug reported:
The Ubuntu Error Tracker has been receiving reports about a problem regarding
software-properties. This problem was most recently seen with package version
0.97.6, the problem page at
https://errors.ubuntu.com/problem/565df6cdd7ae9481d0e747341deebb7e568cb912
contains
Public bug reported:
The Ubuntu Error Tracker has been receiving reports about a problem regarding
packagekit. This problem was most recently seen with package version
1.1.12-1ubuntu1, the problem page at
https://errors.ubuntu.com/problem/1bdc3e539949aa164d276979f62ca0282a54fcbd
contains
1 - 100 of 101 matches
Mail list logo
