Seems resolved.
** Changed in: file (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to file in Ubuntu.
https://bugs.launchpad.net/bugs/2059723
Title:
Please delete libmagic1
Same problem is back now that 1:5.45-3build1 is uploaded and 1:5.45-2
still isn’t deleted.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to file in Ubuntu.
https://bugs.launchpad.net/bugs/2059723
Title:
Please delete
It seems like 1:5.45-3 was deleted instead of 1:5.45-2? That resolves
the immediate issue, I guess, but it’s probably not the intended
resolution.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to file in Ubuntu.
Public bug reported:
As part of the 64-bit time_t transition, libmagic1 was renamed to
libmagic1t64 in https://bugs.debian.org/1063113. However, libmagic1
1:5.45-2 is still in the archive, despite being non-installable:
# apt-get install libmagic1
Reading package lists... Done
Building
Hi,
error message in picture attached.
Best regards,
Anders bodin
On Wed, 4 Oct 2023 at 07:40, Daniel van Vugt <2038...@bugs.launchpad.net>
wrote:
> I don't know if this counts as "do not work", but it seems clear that
> Mesa's Vulkan driver for Haswell is incomplet
Public bug reported:
upscayl software do not work
BACKEND REPORTED: Selected File Path:
/home/anders/Downloads/1695568515335.png
Selected Image Path: /home/anders/Downloads/1695568515335.png
Selected Image Directory: /home/anders/Downloads
imagePath: /home/anders/Downloads
There also needs to be a default.conf, to avoid having to set QT_SELECT
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to qtchooser in Ubuntu.
https://bugs.launchpad.net/bugs/1964763
Title:
QtChooser doesn't support qt6
This new sysconfig-debian-schemes.diff has broken virtual environments
(venv and virtualenv). Please take a look at the fix in
https://bugs.launchpad.net/ubuntu/+source/python3.10/+bug/1962791.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which
*** This bug is a duplicate of bug 1951279 ***
https://bugs.launchpad.net/bugs/1951279
** This bug has been marked a duplicate of bug 1951279
OpenSSL 1.1.1f raise a segmentation faults on Arm64 builds
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
** Changed in: openssh (Ubuntu)
Status: Fix Released => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/47958
Title:
ssh-agent clobbers LD_LIBRARY_PATH
Thank you Brian for getting back.
The problem was indeed that /boot was full - after cleaning it up
manually the upgrade went through. Since I know that /boot is a problem
with updates, I did clean it before doing the upgrade, but apparently
not enough.
The installation was done long ago (7
Public bug reported:
Happened during do-release-upgrade.
ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: initramfs-tools 0.136ubuntu6.6
ProcVersionSignature: Ubuntu 4.15.0-166.174-generic 4.15.18
Uname: Linux 4.15.0-166-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.21
Architecture:
6 years later, I'm encountering the same issue in Ubuntu 18.04.
sudo apt install libfreetype6-dev:i386
[...]
The following packages have unmet dependencies:
libfreetype6-dev:i386 : Depends: libc6-dev:i386 but it is not going to be
installed or
libc-dev:i386
This is the only way i managed to speed up my "Trackpoint" on HP ZBOOK
15u G6 to a acceptable level.
user1@lab1-w:~$ xinput --list
⎡ Virtual core pointer id=2[master pointer (3)]
⎜ ↳ Virtual core XTEST pointerid=4[slave pointer (2)]
⎜ ↳
20.04 still has this problem.
I'm on a HP Zbook 15u G6.
It seems that xinput only can handle values of max 1, which in my case
is all to slow.
user1@lab1-w:~$ xinput --list-props 11
Device 'ALP0017:00 044E:121C Mouse':
Device Enabled (180): 1
Coordinate Transformation Matrix
Public bug reported:
It looks an awful lot like this issue :
https://gitlab.freedesktop.org/drm/amd/-/issues/1427.
I'm hitting these:
[11596.268677] [drm:dce112_get_pix_clk_dividers [amdgpu]] *ERROR*
dce112_get_pix_clk_dividers: Invalid parameters!!
[11596.269781]
** Bug watch added: Debian Bug tracker #977930
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977930
** Also affects: apt (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977930
Importance: Unknown
Status: Unknown
--
You received this bug notification because
Public bug reported:
do-rleasae-upgrade from 18.04 to 20.04 today.
upgrade from 16.04 to 18.04 performed last Sunday on 5 machines.
ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: initramfs-tools 0.136ubuntu6.3
ProcVersionSignature: Ubuntu 4.15.0-118.119-generic 4.15.18
Uname: Linux
Public bug reported:
i dont fucking nknow
** 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.
I have seen this in about 20 Lubuntu/Ubuntu 16.04 installations dist upgraded
to 18.04
Also it works in some others..
I did NOT see this prior to avahi-daemon version 0.70
No idea what breaks it, however avahi-browse seams to work.
Can it be something related with the support for "binary
** Bug watch added: Debian Bug tracker #929417
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=929417
** Also affects: debconf (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=929417
Importance: Unknown
Status: Unknown
** Also affects: debconf (Ubuntu)
Public bug reported:
Seems to be impossible to get this running properly
ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: unattended-upgrades 1.1ubuntu1.18.04.11 [modified:
lib/systemd/system/unattended-upgrades.service]
ProcVersionSignature: Ubuntu 4.15.0-1036.41-oem 4.15.18
Uname:
The situation with apache2 is what I documented in
https://bugs.launchpad.net/ubuntu/+source/pcre3/+bug/1792544/comments/9:
“But since we’re apparently gathering information here: although Apache
2.4.x does not support PCRE2, Apache trunk does support PCRE2 as of
r1773454. (As you can see, this
** Changed in: network-manager (Ubuntu)
Status: Fix Committed => Fix Released
--
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/1792745
Title:
NetworkManager
Also getting these messages (trying to find useful information in syslog
due to other issues, found these messages spamming).
NVme as well.
uname -a
Linux computer 4.15.0-36-generic #39-Ubuntu SMP Mon Sep 24 16:19:09 UTC 2018
x86_64 x86_64 x86_64 GNU/Linux
#journalctl -m | grep ureadahead | wc
There's something wrong going on here. I first reported this issue as a
'linux' bug, based on a hasty reading of documentation. I never
finished that report, so I expect that to be incomplete.
Shortly afterwards I re-reported it as a probable NetworkManager issue.
It seems that these two issues
I may have misidentified the affected package.
Further testing indicates that while the USB adapter works fine in all
three USB-C ports under Windows, the connection problem I've reported
above appears only when I use either of the two USB-C ports (described
as USB Type-C/Thunderbolt 3/Power (DC)
Public bug reported:
The adapter I'm trying to use using is a 'Valueline' USB-C adapter, with
no external identifying information. lsusb lists it as
Bus 004 Device 022: ID 0bda:8153 Realtek Semiconductor Corp.
It works fine on a Windows 10 system (same hardware platform), where
it's identified
1.12.4 is in cosmic-proposed now with the upstream fix.
** Changed in: network-manager (Ubuntu)
Status: In Progress => Fix Committed
** Changed in: network-manager (Ubuntu)
Assignee: Anders Kaseorg (andersk) => (unassigned)
--
You received this bug notification becau
(Still waiting on sponsorship, but apparently “In Progress” is the right
status for that.)
** Changed in: network-manager (Ubuntu)
Status: Confirmed => In Progress
** Changed in: network-manager (Ubuntu)
Assignee: (unassigned) => Anders Kaseorg (andersk)
** Tags added: patch
** Patch added: "rebased on 1.12.2-0ubuntu5"
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1792745/+attachment/5192582/+files/network-manager_1.12.2-0ubuntu5_lp1792745.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages,
--
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/1792745
Title:
NetworkManager crashed with SIGSEGV in _int_malloc()
Status in NetworkManager:
Unknown
Status in
** Patch added: "debdiff adding upstream patch"
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1792745/+attachment/5191867/+files/network-manager_1.12.2-0ubuntu4_lp1792745.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages,
Thanks, workaround in #19 seem to have removed (thousands of) these
messages.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ureadahead in Ubuntu.
https://bugs.launchpad.net/bugs/1579580
Title:
ureadahead reports relative
** Bug watch added: GNOME Bug Tracker #797136
https://bugzilla.gnome.org/show_bug.cgi?id=797136
** Also affects: network-manager via
https://bugzilla.gnome.org/show_bug.cgi?id=797136
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a
Likewise, nginx does not support PCRE2:
https://trac.nginx.org/nginx/ticket/720
** Bug watch added: trac.nginx.org/nginx/ #720
http://trac.nginx.org/nginx/ticket/720
** Changed in: nginx (Ubuntu)
Status: Triaged => Incomplete
--
You received this bug notification because you are a
Note to those filing upstream bugs: probably don’t call the old library
“pcre3” since that’s not a thing outside Debian/Ubuntu.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to grep in Ubuntu.
I think that completes the analysis of the current state of things.
Although it seems infeasible to demote PCRE at this time, there’s no
reason that should block the promotion of PCRE2, especially seeing as a
bundled copy of PCRE2 is already in main (18.04 and 18.10) via
libqt5core5a.
** Changed
• Quagga: no PCRE2 support
• Rasqal: no PCRE2 support
• S-Lang: no PCRE2 support
** Changed in: quagga (Ubuntu)
Status: New => Incomplete
** Changed in: rasqal (Ubuntu)
Status: New => Incomplete
** Changed in: slang2 (Ubuntu)
Status: New => Incomplete
--
You received this
• pam_mount: no PCRE2 support
• nmap: no PCRE2 support
• postfix: no PCRE2 support,
http://postfix.1071664.n5.nabble.com/Plans-for-using-PCRE-v2-in-Postfix-td83200.html
• pyScss: no PCRE2 support
** Changed in: libpam-mount (Ubuntu)
Status: New => Incomplete
** Changed in: nmap (Ubuntu)
• Aide: no PCRE2 support
• Exim: no PCRE2 support, upstream bug:
https://bugs.exim.org/show_bug.cgi?id=1878
• FreeRADIUS: no PCRE2 support, mentioned in passing:
https://github.com/FreeRADIUS/freeradius-server/issues/1865
• GLib: no PCRE2 support
• grep: no PCRE2 support
** Bug watch added:
Copying from
https://bugs.launchpad.net/ubuntu/+source/pcre2/+bug/163/comments/20,
HAProxy and SELinux upstream support PCRE2.
https://git.haproxy.org/?p=haproxy.git;a=commitdiff;h=f2592b29f13907ddf2bba42d00bc41cb8ee5b69b
Andreas: No, it’s not a bug. PCRE2 is a new project that’s not intended
to be compatible with the older PCRE (i.e. what Debian misnamed
“pcre3”). The API is completely different and this is expected. See
bug 163 for context, and specifically the PCRE2 release announcement
linked in the bug
apr-util has a false Build-Depends on libpcre3-dev; it should simply be
dropped. A corresponding Depends was already dropped in
https://bugs.debian.org/757140.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to grep in Ubuntu.
It seems suspicious that cb_data->concheck.curl_ehandle is cleaned up
here despite the comment a few lines above warning that it’s unsafe to
do so.
https://github.com/NetworkManager/NetworkManager/blob/1.12.2/src/nm-
connectivity.c#L190-L213
/* Contrary to what cURL manual claim
Here’s a valgrlind log showing many invalid writes to freed addresses in
cb_data_free → curl_multi_remove_handle and nm_connectivity_check_start
→ curl_multi_add_handle, which could explain the heap corruption.
** Attachment added: "nm.19802.log"
** 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 network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1792745
Title:
NetworkManager crashed with SIGSEGV in
Lots of errors etc in syslog, added some notes on top of the obvious
errors.
Kernel keeps spamming syslog with these
(https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1748565):
kernel: [15621.044566] Bluetooth: hci0: last event is not cmd complete (0x0f)
Note: this kernel message disappears
Ubuntu 18.04.1. Jabra Elite Sport v2. Impossible to get A2DP to stick.
Have to go through multiple jumps to get it to work. E.g.,
1) Shut down and start bluetooth a few times after suspend or reboot.
Sometimes i try to shutdown the Jabra device as well.
2) Then connect to the device, which
Older versions in bionic than in xenial, as of now:
fuse-umfuse-ext2 0.4-1.1ubuntu0.1 < 0.4-1.1ubuntu0.16.04.1
linux-meta-azure 4.15.0.1021.21 < 4.15.0.1021.27
linux-meta-gcp 4.15.0.1017.19 < 4.15.0.1017.29
** Summary changed:
- Older version in artful than in xenial
+ Older version in bionic
Kubuntu 18.04 on Zenbook Pro UX550VE. Also doesn't work. Tried all the
suggestions like installing pm-utils and modifying logind.conf. Nothing
has helped.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
** Description changed:
These packages have an older version in artful than in xenial.
fuse-umfuse-ext2 0.4-1.1ubuntu0.1 < 0.4-1.1ubuntu0.16.04.1
libclc 0.2.0+git20170330-3 < 0.2.0+git20180312-1~16.04.1
libdrm 2.4.83-1 < 2.4.91-2~16.04.1
mesa 17.2.8-0ubuntu0~17.10.1 <
Until this is uploaded to bionic, the version in bionic is older than in
xenial (bug 1780680), which is going to interfere with upgrades.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
Public bug reported:
These packages have an older version in artful than in xenial.
fuse-umfuse-ext2 0.4-1.1ubuntu0.1 < 0.4-1.1ubuntu0.16.04.1
libclc 0.2.0+git20170330-3 < 0.2.0+git20180312-1~16.04.1
libdrm 2.4.83-1 < 2.4.91-2~16.04.1
mesa 17.2.8-0ubuntu0~17.10.1 < 18.0.5-0ubuntu0~16.04.1
patch
Sorry, small adjustment. I use wayland as default since 17.10 with gdm
(works well in general for me):
loginctl show-session c1 -p Type
Type=wayland
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in Ubuntu.
Confirm (Super - L) not working on Ubuntu 18.04, switching keyboard
language does not work either most of the time (Super + Space). Those I
use the most. Extremely annoying after some time, especially when using
dual screens (since the Gnome top bar is only on one monitor which is
even more
** Changed in: console-setup (Ubuntu)
Status: Invalid => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to console-setup in Ubuntu.
https://bugs.launchpad.net/bugs/520546
Title:
Alt-f2 switches to virtual
Just because DISPLAY isn’t set for the current process doesn’t mean X or
Wayland aren’t running. For example:
pkexec env DEBIAN_FRONTEND=noninteractive dpkg-reconfigure keyboard-
configuration
still triggers this bug (because pkexec does not propagate environment
variables), and you can imagine
On my bionic system, I had to manually remove resolvconf on account of
bug 1713457. I think it was not being autoremoved because other
packages like isc-dhcp-client, pppconfig, vpnc-scripts have Suggests:
resolvconf.
So I don’t think I’m seeing this particular issue. However, the lack of
The problem went away in 17.10. Cheers.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to indicator-datetime in
Ubuntu.
https://bugs.launchpad.net/bugs/774071
Title:
Indicator-datetime-service renders 100% CPU usage
Status
*** This bug is a duplicate of bug 774071 ***
https://bugs.launchpad.net/bugs/774071
The problem went away in 17.10. Cheers.
** This bug has been marked a duplicate of bug 774071
Indicator-datetime-service renders 100% CPU usage
--
You received this bug notification because you are a
Last work-around didn't stick. Don't think this bug or #1731939 is about
indicator-datetime-service. It seems to be evolution calendar that is
the problem. See comment below:
https://bugs.launchpad.net/ubuntu/+source/indicator-
datetime/+bug/1731939/comments/4
Will test 17.10 now.
--
You
Last work-around didn't stick. Did some test and can reproduce the error
now easily in 17.04. Ubuntu reports it is the Indicator-datetime-service
that crashes when its the evolution calendar that is the problem. During
the system overload the problem can be fixed by killing all evolution
processes
(#51 was a mistake)
Sorry, wrote incorrect. Reported for 17.04 LTS above.
Work-around (I cant upgrade to 17.10 due to KVM bug): Turn of the "Show
a clock in the menu bar" in System Settings for Time & Date. Worked
after cold reboot.
--
You received this bug notification because you are a
Sorry, wrote incorrect. Reported for 17.04 LTS above.
Work-around (I cant upgrade to 17.10 due to KVM bug): Turn of the t
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to indicator-datetime in
Ubuntu.
Work-around (I cant upgrade to 17.10 due to KVM bug): Turn of the "Show
a clock in the menu bar" in System Settings for Time & Date. Worked
after cold reboot.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to indicator-datetime
Seeing this on 17.10 as well. Battery indicator says ("estimating,
100%) and indicator-datetime-service uses between 2.4 GiB and (mostly)
~14.5 GiB RAM. CPU usage stays at 25% all the time. The indicator-
datetime-service crashes after reaching all available RAM, then restarts
with new PID.
I
Public bug reported:
Same as Bug #774071 but with 100% RAM instead. Collected info while the
Indicator-datetime-service was acting up. I.e., writing this with a few
hundred megabytes RAM available..
ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: indicator-datetime
PID changes after crash when RAM is depleted. Sceenshoot of RAM usage
attached.
** Attachment added: "Exampel of memory usage"
https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1731939/+attachment/5008303/+files/Screenshot%20from%202017-11-13%2015-29-41.png
--
You received
** Tags removed: verification-needed-artful
** Tags added: verification-done-artful
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1729910
Title:
lp ignores
I confirm that the problem is fixed in version 2.2.4-7ubuntu3.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1729910
Title:
lp ignores ~/.cups/lpoptions in 17.10
Status in
Verified using ubuntu-17.04-desktop-amd64.iso.
** Tags removed: verification-needed verification-needed-zesty
** Tags added: verification-done verification-done-zesty
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd
Addition/correction to my above comment, window buttons are actually
added to the right of the top bar, fairly closely mimicking the 17.04
approach. Attaching a screenshot.
** Attachment added: "Screenshot from 2017-09-14 08-33-05.png"
I found the extension https://extensions.gnome.org/extension/723/pixel-
saver/ which brings a behavior much closer to that of 17.04 -- however,
with this solution the window buttons are missing once a window has been
maximized and merged with the top bar. Perhaps the extension could still
serve as
Public bug reported:
Description:Ubuntu Artful Aardvark (development branch)
Release:17.10
light-themes:
Installed: 16.10+17.10.20170817-0ubuntu1
Candidate: 16.10+17.10.20170817-0ubuntu1
Since windows no longer merge with the top panel when maximized in
17.10, a jarring double
Public bug reported:
When I connect to a wireless network that sets a DNS search domain name
via DHCP, the line 'search ' is added to /etc/resolv.conf as
expected. But if I then disconnect and connect to a different network,
it is not removed from resolv.conf. If the second network also sets a
** Also affects: systemd (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=761658
Importance: Unknown
Status: Unknown
** Changed in: systemd
Importance: Unknown => Undecided
** Changed in: systemd
Status: Fix Released => New
** Changed in: systemd
Remote
Ping? It’s still really frustrating to have the entire system go
unresponsive for a minute just because gnome-shell crashed and apport
won’t let it restart until it’s finished compressing the core dump.
If you’re not willing to go all the way to zlib level 1, can we at least
proceed with going
In fact, having recently disabled FallbackDNS for myself, I find that I
get no DNS at all maybe a quarter of the time I reboot my system. This
suggests that systemd-resolved might be silently relying on the 8.8.8.8
fallback much more often than even I suggested above.
Can we try disabling
How do i get a stack trace from pulseaudio?
I can't find it in /var/log/* nor in /var/crash/*.
--
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/1689555
Title:
Scrolling
Dimitri: It is not merely difficult, but in fact fundamentally
impossible, to make everyone use nss_resolve for DNS resolution. Many
programs cannot use nsswitch for DNS at all. This includes anything
that needs to lookup record types other than A and (e.g. SRV, TXT,
MX, SSHFP, AFSDB),
Martin, was the DNSSEC=allow-downgrade default not switched off for the
17.04 stable release like you said it would?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
Ah, zesty still has 232-19 but this is presumably fixed in zesty-
proposed’s 232-21ubuntu1.
** Changed in: systemd (Ubuntu)
Status: Incomplete => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd
Public bug reported:
If you are running ‘journalctl -f’ to try to debug some other problem,
you are constantly interrupted by zillions of these messages from
systemd-resolved:
Mar 26 00:53:27 change-mode systemd-resolved[1391]: Processing query...
Mar 26 00:53:27 change-mode
Carl: I’m not sure whether that “@Andres” was directed at Andreas or me
(I’m Anders), but I still believe the situation is explained by my
comments #31 and #33; it is not a mystery why this is seen only
occasionally. The bug is triggered every time the console-setup package
is installed
I don't think I've seen this since this update over a month ago:
xserver-xorg-video-intel:amd64 (2:2.99.917+git20160325-1ubuntu1.2)
So it may have been fixed.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
Steve: I didn’t test yakkety since I thought it had gone back to the
configuration with dnsmasq on 127.0.0.1 rather than systemd-resolved on
127.0.0.53. If that’s not the case, then yeah, it would be affected
too.
--
You received this bug notification because you are a member of Ubuntu
Touch
Ognjen, Vincent: This bug is marked with the “resolved” _tag_, as in
“systemd-resolved”, not as in “fixed”. The bug _status_ is still open
(Confirmed).
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
Or virtual machines: a VM running in virt-manager on a zesty host can’t
resolve CNAMEs (not even a zesty VM with libnss-resolve inside!).
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
Another case that now necessarily relies on 127.0.0.53 is anything
inside a chroot (e.g. sbuild). libnss-resolve can’t help there: you
can’t talk to the host D-Bus from inside, and also you might want to
chroot a distro that’s too old for libnss-resolve anyway.
--
You received this bug
Public bug reported:
# grep hosts /etc/nsswitch.conf
hosts: files myhostname dns
# apt install libnss-resolve
# grep hosts /etc/nsswitch.conf
hosts: files myhostname resolve [!UNAVAIL=return] dns
# apt remove libnss-resolve
# grep hosts /etc/nsswitch.conf
hosts: files
Whether or not it’s enabled, it is started automatically via D-BUS
activation (/lib/systemd/system/dbus-org.freedesktop.resolve1.service ->
systemd-resolved.service).
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in
Firefox, wget, ping, and Chrome do not work unless libnss-resolve is
installed. (Perhaps Chrome recently started using NSS in some cases?)
Maybe this isn’t quite as critical as I thought given that ubuntu-
standard Recommends libnss-resolve. Still, it’s not just an
“implementation detail”. DNS
Martin: I still wonder what the point of having resolvconf is, if it’s
only ever supposed to be used to manage 127.0.0.53, and every other use
of resolvconf will lead to this bug resurfacing. I still propose that
systemd-resolved should read from /run/resolvconf/resolv.conf without
adding
Possible duplicate of bug 1647031.
--
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/1647178
Title:
systemd-resolved unable to resolve certain subdomains
Status in systemd
For example, I see
$ dig +no{cmd,comments,stats} mail.google.com @8.8.8.8
;mail.google.com. IN A
mail.google.com.86312 IN CNAME googlemail.l.google.com.
googlemail.l.google.com. 212IN A 216.58.219.229
$ dig +no{cmd,comments,stats} mail.google.com
Possible duplicate of bug 1647031. For example, I see
$ dig +no{cmd,comments,stats} buy.ubuntu.com @8.8.8.8
;buy.ubuntu.com.IN A
buy.ubuntu.com. 599 IN CNAME
ubuntu-advantage-cloud-guest.myshopify.com.
ubuntu-advantage-cloud-guest.myshopify.com.
@fourdollars, I installed your ppa in #120 above. Unfortunately I could
not detect any significant change compared to the latest released
versions. Following are my notes from my tests. The test PC has a fresh
Ubuntu 16.04 install with all updates. The wifi interface name is wlp1s0
and there is no
** Patch added: "Debdiff from vim 2:8.0.0095-1 in Debian testing/unstable"
https://bugs.launchpad.net/ubuntu/+source/vim/+bug/1647105/+attachment/4787466/+files/vim_8.0.0095-1_1ubuntu1.debdiff
** Patch removed: "Debdiff from vim 2:8.0.0095-1 in Debian testing/unstable"
*** This bug is a duplicate of bug 1647105 ***
https://bugs.launchpad.net/bugs/1647105
** This bug has been marked a duplicate of bug 1647105
Merge vim 2:8.0.0095-1 from Debian testing/unstable
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
1 - 100 of 225 matches
Mail list logo
