My system is focal. Can't try Hirsute yet, dont have any systems with
such error appearing.
It doesnt work at all for me, fail to resolve anything
Link 2 (enp3s0)
Current Scopes: DNS
DefaultRoute setting: yes
LLMNR setting: yes
Sorry for very long delay, many bad events in life. I will give it a try
now.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1934221
Title:
systemd-resolve segfault
To manage notifications about
Yes it seems i am still seeing crashes too. They are more rare, but
still appearing.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1934221
Title:
systemd-resolve segfault
To manage notifications
Started testing on my PC.
Ubuntu Hiruste will be a bit difficult to run, but i will try.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1934221
Title:
systemd-resolve segfault
To manage
I recorded pcap and captured moment just before crash. It doesnt looks
like there was any MDNS at all at this moment, only suspicious is many
weird DNS requests. (spinesystems.solutions is my local domain set on
pc). Not sure what generated them.
Small snap of these:
02:16:36.658522 IP
1. No, my skills are just not enough to spot it.
I noticed warning in valgrind (but it was once only and not crash), but was not
able to trace back reason. Very likely your patch fix that.
2. In my network i have some MDNS devices, and probably some combination of
them and their connectivity
As far as i can see - no crashes anymore.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1934221
Title:
systemd-resolve segfault
To manage notifications about this bug go to:
Not sure if i backported patch correctly, some functions is missing in 245.4
Build is OK, testing it, no crashes yet, but will have conclusive results in
~24h.
** Patch added: "Backported bugfix"
Most likely i found patch that fix this problem:
https://github.com/systemd/systemd/commit/97935302283729c9206b84f5e00b1aff0f78ad19
And associated issue have striking similarity
https://github.com/systemd/systemd/issues/18427
Will try to test it today if it fixes my issue as well.
** Bug watch
Here is more meaningful result from valgrind with dbgsym present
** Attachment added: "vagrind output"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1934221/+attachment/5508373/+files/valgrind-bug.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs,
I run it with valgrind and here is what i got:
(not sure yet how to add debug symbols, will try it too)
root@threadpc:~# valgrind -v /lib/systemd/systemd-resolved
==1798854== Memcheck, a memory error detector
==1798854== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al.
==1798854==
Here is backtrace, as i am unable to attach crash report (launchpad gives error)
apport-retrace -g _lib_systemd_systemd-resolved.102.crash
GNU gdb (Ubuntu 9.2-0ubuntu1~20.04) 9.2
Copyright (C) 2020 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later
Public bug reported:
systemd-resolve keep crashing and it is very annoying as sometimes it
severely interrupt normal dns resolving.
Last uploaded report is 2d9e7378-d89b-11eb-9e14-fa163ee63de6
Typical error in dmesg:
systemd-resolve[1792202]: segfault at 564ff982f3e0 ip 564ff982f3e0 sp
It seems problem was in custom installed python-2.7 in /usr/local/bin.
Not really "vanilla" ubuntu and not ubuntu fault, but maybe should be checked
properly (if that possible).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
During upgrade from 18 to 20 it spit this error.
ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: python2-minimal 2.7.17-2ubuntu4
ProcVersionSignature: Ubuntu 4.15.0-101.102-generic 4.15.18
Uname: Linux 4.15.0-101-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.14
Happened same for me during upgrade
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1874569
Title:
package collectd-core 5.9.2.g-1ubuntu5 failed to install/upgrade:
installed collectd-core package
Perfect! Thanks a lot, now i have big reason to ask some sysadmins and
vendors to upgrade their kernels.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1739765
Title:
xt_TCPMSS buffer overflow bug
Public bug reported:
This was lxc upgrade, probably i installed non-cloud version there by
mistake
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: keyboard-configuration 1.108ubuntu15.3
ProcVersionSignature: Ubuntu 4.4.0-104.127-generic 4.4.98
Uname: Linux 4.4.0-104-generic x86_64
Yes, already queued by Eric Dumazet in all stable since report in April
http://patchwork.ozlabs.org/patch/746618/
Yes, i did, but troubleshooting done and fix issued by Eric Dumazet.
Also there is chance exist that someone used it for malicious purposes "in
wild" at that moment, as it appeared
Public bug reported:
This is more wish, than a bug. Very important for typical new user
experience.
Short: Due nature of hardware bugs(vendor fixes more efficiently than
workaround on kernel), it is highly prefferable to install microcode
update, to improve user experience. It can be done usual
20 matches
Mail list logo
