from:"Denys Fedoryshchenko"

[Bug 1934221] Re: systemd-resolve segfault

2021-10-04 Thread Denys Fedoryshchenko

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   
MulticastDNS setting: no
  DNSOverTLS setting: no
  DNSSEC setting: no
DNSSEC supported: no
  Current DNS Server: 2a0d:e40:0:4000::1
 DNS Servers: 2a0d:e40:0:4000::1
  fd2c:bf12:1194::1 
  10.255.255.1  
  8.8.8.8   
  DNS Domain: ~.
  spinesystems.solutions

udp0  0 127.0.0.53:53   0.0.0.0:*   
4106635/systemd-res 
resolv.conf nameserver: nameserver 127.0.0.53

dig @127.0.0.53

; <<>> DiG 9.16.1-Ubuntu <<>> @127.0.0.53
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 4404
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 65494
;; QUESTION SECTION:
;.  IN  NS

;; Query time: 0 msec
;; SERVER: 127.0.0.53#53(127.0.0.53)
;; WHEN: Mon Oct 04 12:34:50 EEST 2021
;; MSG SIZE  rcvd: 28

dig +short @2a0d:e40:0:4000::1www.google.com
142.250.200.196

# systemd-resolve -4 www.google.com
www.google.com: resolve call failed: No appropriate name servers or networks 
for name found

But didnt rebooted yet after fetching new systemd.

-- 
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:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1934221/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1934221] Re: systemd-resolve segfault

2021-10-04 Thread Denys Fedoryshchenko

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 this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1934221/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1934221] Re: systemd-resolve segfault

2021-09-17 Thread Denys Fedoryshchenko

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 about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1934221/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1934221] Re: systemd-resolve segfault

2021-09-07 Thread Denys Fedoryshchenko

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 notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1934221/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1934221] Re: systemd-resolve segfault

2021-07-29 Thread Denys Fedoryshchenko

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 127.0.0.1.39766 > 127.0.0.1.53: 17063+ A? 
roxquromlpczqgh.spinesystems.solutions. (56)
02:16:36.658626 IP 127.0.0.1.31846 > 127.0.0.53.53: 54480+ A? 
roxquromlpczqgh.spinesystems.solutions. (56)
02:16:36.659106 IP 127.0.0.53.53 > 127.0.0.1.6126: 42840 NXDomain 0/0/0 (56)
02:16:36.659603 IP 127.0.0.53.53 > 127.0.0.1.31846: 54480 NXDomain 0/0/0 (56)
02:16:36.659644 IP 127.0.0.1.53 > 127.0.0.1.54315: 17063 NXDomain 0/0/0 (56)
02:16:36.659660 IP 127.0.0.1.53 > 127.0.0.1.39766: 17063 NXDomain 0/0/0 (56)
02:16:36.660099 IP 127.0.0.53.53 > 127.0.0.1.6126: 42840 NXDomain 0/0/0 (56)
02:16:36.660603 IP 127.0.0.53.53 > 127.0.0.1.6126: 42840 NXDomain 0/0/0 (56)
02:16:36.661082 IP 127.0.0.53.53 > 127.0.0.1.6126: 42840 NXDomain 0/0/0 (56)
02:16:36.661513 IP 127.0.0.53.53 > 127.0.0.1.25474: 60255 NXDomain 0/0/1 (67)
02:16:36.661898 IP 127.0.0.53.53 > 127.0.0.1.6126: 42840 NXDomain 0/0/0 (56)
02:16:36.662282 IP 127.0.0.53.53 > 127.0.0.1.6126: 42840 NXDomain 0/0/0 (56)
02:16:36.662778 IP 127.0.0.53.53 > 127.0.0.1.6126: 42840 NXDomain 0/0/0 (56)
02:16:36.663188 IP 127.0.0.1.60869 > 127.0.0.1.53: 47647+ ? 
xjstkkuhaqclygt.spinesystems.solutions. (56)
02:16:36.663259 IP 127.0.0.1.32600 > 127.0.0.53.53: 10939+ ? 
xjstkkuhaqclygt.spinesystems.solutions. (56)
02:16:36.663449 IP 127.0.0.1.36798 > 127.0.0.1.53: 30847+ ? 
roxquromlpczqgh.spinesystems.solutions. (56)
02:16:36.663481 IP 127.0.0.1.15565 > 127.0.0.53.53: 54137+ ? 
roxquromlpczqgh.spinesystems.solutions. (56)
02:16:36.664474 IP 127.0.0.1.47179 > 127.0.0.1.53: 3316+ A? 
roxquromlpczqgh.spinesystems.solutions. (56)
02:16:36.664563 IP 127.0.0.1.40056 > 127.0.0.53.53: 55684+ A? 
roxquromlpczqgh.spinesystems.solutions. (56)
02:16:36.664969 IP 10.255.255.225.55743 > 10.255.255.1.53: 60614+ [1au] A? 
roxquromlpczqgh.spinesystems.solutions. (67)
02:16:36.665503 IP 10.255.255.1.53 > 10.255.255.225.55743: 60614 NXDomain 0/1/1 
(140)
02:16:36.666994 IP 10.255.255.225.55743 > 10.255.255.1.53: 60614+ A? 
roxquromlpczqgh.spinesystems.solutions. (56)
02:16:36.667494 IP 10.255.255.1.53 > 10.255.255.225.55743: 60614 NXDomain 0/1/0 
(129)

Maybe because there is massive timeouts in query to nonexisting domain it 
triggers this bug like in original issue in systemd ( 
https://github.com/systemd/systemd/issues/18427 )?
In my ISP also all port 53 requests are force-redirected to their DNS, so they 
might timeout sometimes, instead of NXDomain.

-- 
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:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1934221/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1934221] Re: systemd-resolve segfault

2021-07-20 Thread Denys Fedoryshchenko

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 (power failures, packetloss) triggering this bug 
from time to time.
I run back now valgrind with timestamps and will record all port 53 traffic, 
maybe i can catch pattern.
If you want i can apply your patch and do the same.

To find the reason i just disabled systemd-resolved service and run manually 
valgrind -v /lib/systemd/systemd-resolved.
Probably other users complained about resolved segfault messages in dmesg and 
have it happening more often?

3. I was not able to find way to reproduce bug reliably.
And now it might take about a week to spot this remaining bug.

-- 
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:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1934221/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1934221] Re: systemd-resolve segfault

2021-07-05 Thread Denys Fedoryshchenko

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:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1934221/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1934221] Re: systemd-resolve segfault

2021-07-04 Thread Denys Fedoryshchenko

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"
   
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1934221/+attachment/5508948/+files/ubuntu-resolved-disable-event-sources-before-unreffing-them.patch

-- 
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:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1934221/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1934221] Re: systemd-resolve segfault

2021-07-04 Thread Denys Fedoryshchenko

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 added: github.com/systemd/systemd/issues #18427
   https://github.com/systemd/systemd/issues/18427

-- 
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:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1934221/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1934221] Re: systemd-resolve segfault

2021-06-30 Thread Denys Fedoryshchenko

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, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1934221

Title:
  systemd-resolve segfault

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1934221/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1934221] Re: systemd-resolve segfault

2021-06-30 Thread Denys Fedoryshchenko

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== Using Valgrind-3.15.0-608cb11914-20190413 and LibVEX; rerun with -h 
for copyright info
==1798854== Command: /lib/systemd/systemd-resolved
==1798854== 
--1798854-- Valgrind options:
--1798854---v
--1798854-- Contents of /proc/version:
--1798854--   Linux version 5.4.0-75-generic (buildd@lgw01-amd64-034) (gcc 
version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04)) #84-Ubuntu SMP Fri May 28 
16:28:37 UTC 2021
--1798854-- 
--1798854-- Arch and hwcaps: AMD64, LittleEndian, 
amd64-cx16-lzcnt-rdtscp-sse3-ssse3-avx-avx2-bmi-f16c-rdrand
--1798854-- Page sizes: currently 4096, max supported 4096
--1798854-- Valgrind library directory: /usr/lib/x86_64-linux-gnu/valgrind
--1798854-- Reading syms from /lib/systemd/systemd-resolved
--1798854--object doesn't have a symbol table
--1798854-- Reading syms from /lib/x86_64-linux-gnu/ld-2.31.so
--1798854--   Considering /lib/x86_64-linux-gnu/ld-2.31.so ..
--1798854--   .. CRC mismatch (computed b1e31cec wanted 7bd1f8ba)
--1798854--   Considering /lib/x86_64-linux-gnu/ld-2.31.so ..
--1798854--   .. CRC mismatch (computed b1e31cec wanted 7bd1f8ba)
--1798854--   Considering /usr/lib/debug/lib/x86_64-linux-gnu/ld-2.31.so ..
--1798854--   .. CRC is valid
--1798854-- Reading syms from 
/usr/lib/x86_64-linux-gnu/valgrind/memcheck-amd64-linux
--1798854--object doesn't have a symbol table
--1798854--object doesn't have a dynamic symbol table
--1798854-- Scheduler: using generic scheduler lock implementation.
--1798854-- Reading suppressions file: 
/usr/lib/x86_64-linux-gnu/valgrind/default.supp
==1798854== embedded gdbserver: reading from 
/tmp/vgdb-pipe-from-vgdb-to-1798854-by-root-on-???
==1798854== embedded gdbserver: writing to   
/tmp/vgdb-pipe-to-vgdb-from-1798854-by-root-on-???
==1798854== embedded gdbserver: shared mem   
/tmp/vgdb-pipe-shared-mem-vgdb-1798854-by-root-on-???
==1798854== 
==1798854== TO CONTROL THIS PROCESS USING vgdb (which you probably
==1798854== don't want to do, unless you know exactly what you're doing,
==1798854== or are doing some strange experiment):
==1798854==   /usr/lib/x86_64-linux-gnu/valgrind/../../bin/vgdb --pid=1798854 
...command...
==1798854== 
==1798854== TO DEBUG THIS PROCESS USING GDB: start GDB like this
==1798854==   /path/to/gdb /lib/systemd/systemd-resolved
==1798854== and then give GDB the following command
==1798854==   target remote | /usr/lib/x86_64-linux-gnu/valgrind/../../bin/vgdb 
--pid=1798854
==1798854== --pid is optional if only one valgrind process is running
==1798854== 
--1798854-- REDIR: 0x4022f60 (ld-linux-x86-64.so.2:strlen) redirected to 
0x580c9ce2 (???)
--1798854-- REDIR: 0x4022d30 (ld-linux-x86-64.so.2:index) redirected to 
0x580c9cfc (???)
--1798854-- Reading syms from 
/usr/lib/x86_64-linux-gnu/valgrind/vgpreload_core-amd64-linux.so
--1798854--object doesn't have a symbol table
--1798854-- Reading syms from 
/usr/lib/x86_64-linux-gnu/valgrind/vgpreload_memcheck-amd64-linux.so
--1798854--object doesn't have a symbol table
==1798854== WARNING: new redirection conflicts with existing -- ignoring it
--1798854-- old: 0x04022f60 (strlen  ) R-> (.0) 0x580c9ce2 
???
--1798854-- new: 0x04022f60 (strlen  ) R-> (2007.0) 0x0483f060 
strlen
--1798854-- REDIR: 0x401f740 (ld-linux-x86-64.so.2:strcmp) redirected to 
0x483ffd0 (strcmp)
--1798854-- REDIR: 0x40234c0 (ld-linux-x86-64.so.2:mempcpy) redirected to 
0x4843a20 (mempcpy)
--1798854-- Reading syms from /lib/x86_64-linux-gnu/libc-2.31.so
--1798854--   Considering /lib/x86_64-linux-gnu/libc-2.31.so ..
--1798854--   .. CRC mismatch (computed 11759501 wanted 88150686)
--1798854--   Considering /lib/x86_64-linux-gnu/libc-2.31.so ..
--1798854--   .. CRC mismatch (computed 11759501 wanted 88150686)
--1798854--   Considering /usr/lib/debug/lib/x86_64-linux-gnu/libc-2.31.so ..
--1798854--   .. CRC is valid
--1798854-- Reading syms from /lib/systemd/libsystemd-shared-245.so
--1798854--object doesn't have a symbol table
--1798854-- Reading syms from /lib/x86_64-linux-gnu/libgpg-error.so.0.28.0
--1798854--object doesn't have a symbol table
--1798854-- Reading syms from /lib/x86_64-linux-gnu/libm-2.31.so
--1798854--   Considering /lib/x86_64-linux-gnu/libm-2.31.so ..
--1798854--   .. CRC mismatch (computed 5f7b2a42 wanted ffb185de)
--1798854--   Considering /lib/x86_64-linux-gnu/libm-2.31.so ..
--1798854--   .. CRC mismatch (computed 5f7b2a42 wanted ffb185de)
--1798854--   Considering /usr/lib/debug/lib/x86_64-linux-gnu/libm-2.31.so ..
--1798854--   .. CRC is valid
--1798854-- Reading syms from /usr/lib/x86_64-linux-gnu/libidn2.so.0.3.6
--1798854--object doesn't have a symbol table
--1798854-- Reading syms from /usr/lib/x86_64-linu

[Bug 1934221] Re: systemd-resolve segfault

2021-06-30 Thread Denys Fedoryshchenko

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 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.

For help, type "help".
Type "apropos word" to search for commands related to "word".
Reading symbols from /lib/systemd/systemd-resolved...
(No debugging symbols found in /lib/systemd/systemd-resolved)
warning: core file may not match specified executable file.
[New LWP 1792202]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
Core was generated by `/lib/systemd/systemd-resolved'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0  0x564ff982f3e0 in ?? ()
(gdb) bt full
#0  0x564ff982f3e0 in ?? ()
No symbol table info available.
#1  0x564ff772a97f in ?? ()
No symbol table info available.
#2  0x7f3e903c2b96 in ?? () from /lib/systemd/libsystemd-shared-245.so
No symbol table info available.
#3  0x7f3e903c2f11 in sd_event_dispatch () from 
/lib/systemd/libsystemd-shared-245.so
No symbol table info available.
#4  0x7f3e903c4948 in sd_event_run () from 
/lib/systemd/libsystemd-shared-245.so
No symbol table info available.
#5  0x7f3e903c4b6f in sd_event_loop () from 
/lib/systemd/libsystemd-shared-245.so
No symbol table info available.
#6  0x564ff770522a in ?? ()
No symbol table info available.
#7  0x7f3e905cc0b3 in __libc_start_main (main=0x564ff7703e40, argc=1, 
argv=0x7ffe2fd0ba18, init=, fini=, 
rtld_fini=, stack_end=0x7ffe2fd0ba08)
at ../csu/libc-start.c:308
self = 
result = 
unwind_buf = {cancel_jmp_buf = {{jmp_buf = {94901453980416, 
-7807279351804040094, 94901453740880, 140729700629008, 0, 0, 
7807736978364591202, 7916158757757021282}, mask_was_saved = 0}}, priv = {pad = {
  0x0, 0x0, 0x1, 0x7ffe2fd0ba18}, data = {prev = 0x0, cleanup = 
0x0, canceltype = 1}}}
not_first_call = 
#8  0x564ff7705b7e in ?? ()
No symbol table info available.


** Attachment added: "bug.png"
   
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1934221/+attachment/5508351/+files/bug.png

-- 
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:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1934221/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1934221] [NEW] systemd-resolve segfault

2021-06-30 Thread Denys Fedoryshchenko

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 
7ffe2fd0b758 error 15

apport hints me that problem is related to mdns

#3  0x7f3e903c2f11 in sd_event_dispatch () from /lib/systemd
/libsystemd-shared-245.so

It might be (or not) related that some hosts with mdns in my network
have ipv6 enabled.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: systemd 245.4-4ubuntu3.7
ProcVersionSignature: Ubuntu 5.4.0-75.84-generic 5.4.119
Uname: Linux 5.4.0-75-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.18
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Thu Jul  1 08:22:51 2021
InstallationDate: Installed on 2018-12-05 (938 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3)
MachineType: System manufacturer System Product Name
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-75-generic 
root=UUID=54b80d5c-3d61-4919-873f-0d308083e3b9 ro quiet splash vt.handoff=7
SourcePackage: systemd
UpgradeStatus: Upgraded to focal on 2020-05-22 (405 days ago)
dmi.bios.date: 05/12/2020
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1205
dmi.board.asset.tag: Default string
dmi.board.name: ROG STRIX X399-E GAMING
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1205:bd05/12/2020:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXX399-EGAMING:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
dmi.product.sku: SKU
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer

** Affects: systemd (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug focal third-party-packages

** Attachment added: "attaching empty file, otherwise launchpad giving error"
   https://bugs.launchpad.net/bugs/1934221/+attachment/5508334/+files/x

-- 
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:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1934221/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1880654] Re: package python2-minimal 2.7.17-2ubuntu4 failed to install/upgrade: installed python2-minimal package post-installation script subprocess returned error exit status 1

2020-05-26 Thread Denys Fedoryshchenko

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.
https://bugs.launchpad.net/bugs/1880654

Title:
  package python2-minimal 2.7.17-2ubuntu4 failed to install/upgrade:
  installed python2-minimal package post-installation script subprocess
  returned error exit status 1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-defaults/+bug/1880654/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1880654] [NEW] package python2-minimal 2.7.17-2ubuntu4 failed to install/upgrade: installed python2-minimal package post-installation script subprocess returned error exit status 1

2020-05-26 Thread Denys Fedoryshchenko

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
Architecture: amd64
Date: Tue May 26 09:49:11 2020
ErrorMessage: installed python2-minimal package post-installation script 
subprocess returned error exit status 1
InstallationDate: Installed on 2015-03-15 (1899 days ago)
InstallationMedia: Ubuntu-Server 12.04.4 LTS "Precise Pangolin" - Release amd64 
(20140204)
Python3Details: /usr/bin/python3.6, Python 3.6.9, python3-minimal, 3.6.7-1~18.04
PythonDetails: /usr/bin/python2.7, Python 2.7.18rc1, python-is-python2, 2.7.17-4
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu2.3
 apt  1.6.12ubuntu0.1
SourcePackage: python-defaults
Title: package python2-minimal 2.7.17-2ubuntu4 failed to install/upgrade: 
installed python2-minimal package post-installation script subprocess returned 
error exit status 1
UpgradeStatus: Upgraded to focal on 2020-05-26 (0 days ago)

** Affects: python-defaults (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package focal third-party-packages

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1880654

Title:
  package python2-minimal 2.7.17-2ubuntu4 failed to install/upgrade:
  installed python2-minimal package post-installation script subprocess
  returned error exit status 1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-defaults/+bug/1880654/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1874569] Re: package collectd-core 5.9.2.g-1ubuntu5 failed to install/upgrade: installed collectd-core package post-installation script subprocess returned error exit status 1

2020-05-24 Thread Denys Fedoryshchenko

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 post-installation script subprocess
  returned error exit status 1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/collectd/+bug/1874569/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1739765] Re: xt_TCPMSS buffer overflow bug

2018-01-03 Thread Denys Fedoryshchenko

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1739765/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1740173] [NEW] package keyboard-configuration 1.108ubuntu15.3 failed to install/upgrade: subprocess installed post-installation script was killed by signal (Terminated)

2017-12-26 Thread Denys Fedoryshchenko

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
NonfreeKernelModules: xt_nat xt_multiport veth xt_CHECKSUM iptable_mangle 
ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_conntrack_ipv4 
nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack xt_tcpudp bridge stp llc 
ip6table_filter ip6_tables xt_set ip_set nfnetlink iptable_filter ip_tables 
x_tables intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel 
kvm irqbypass crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel 
aes_x86_64 lrw gf128mul glue_helper hci_uart btbcm ablk_helper btqca btintel 
input_leds cryptd bluetooth serio_raw 8250_fintek fujitsu_laptop mac_hid 
intel_lpss_acpi intel_lpss acpi_pad autofs4 btrfs raid10 raid456 
async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq 
libcrc32c raid0 multipath linear raid1 i915_bpo intel_ips i2c_algo_bit 
drm_kms_helper syscopyarea e1000e sysfillrect sysimgblt fb_sys_fops ptp ahci 
pps_core drm libahci wmi pinctrl_sunrisepoint i2c_hid video pinctrl_intel hid 
fjes
ApportVersion: 2.20.1-0ubuntu2.14
Architecture: amd64
Date: Tue Dec 26 21:40:45 2017
ErrorMessage: subprocess installed post-installation script was killed by 
signal (Terminated)
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.3
 apt  1.2.24
SourcePackage: console-setup
Title: package keyboard-configuration 1.108ubuntu15.3 failed to 
install/upgrade: subprocess installed post-installation script was killed by 
signal (Terminated)
UpgradeStatus: Upgraded to xenial on 2017-12-26 (0 days ago)

** Affects: console-setup (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package need-duplicate-check uec-images xenial

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1740173

Title:
  package keyboard-configuration 1.108ubuntu15.3 failed to
  install/upgrade: subprocess installed post-installation script was
  killed by signal (Terminated)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1740173/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1739765] Re: xt_TCPMSS buffer overflow bug

2017-12-23 Thread Denys Fedoryshchenko

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 at peak time on ISP, in specific network 
with many users, while exactly same setup on other locations didn't had this 
issue. That was reason to enable KASAN and to search for it.

No CVE as far as i know, i just don't know how to do that. Not sure if
Eric or netfilter developers (for example Pablo Neira Ayuso) filled
anything.

-- 
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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1739765/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 993605] [NEW] microcode update should be on by default

2012-05-02 Thread Denys Fedoryshchenko

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 way, offering
proprietary driver.

Long: I did installed for my girlfriend Ubuntu on Zotac Nettop, and she started 
to occure random crashes. Most difficult was, that it is kernel panic, and she 
is in another country. After digging 2 month, i noticed something about 
"hardware bug" workaround in kernel log and old revision of CPU, randomly i 
picked up microcode tool with updates, and that fixed the bug. Unfortunately 
her user experience was so bad, that she opposed and installed windows on her 
computer and started to hate linux. I didn't had a chance even to fill proper 
report to upstream vanilla.
I believe workaround in kernel was not enough, since vendor has more access to 
nature of the bug, and they didn't cooperate with kernel developers to fix bug 
properly, and preffered to issue microcode update.
If there was microcode update, this relatively old bug will be fixed 
"automagically", and i believe disappearance of such bugs will decrease amound 
of hassle of bugs that are triggered by hardware issues, and becoming pure 
waste of time for software developers.

** Affects: ubuntu
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/993605

Title:
  microcode update should be on by default

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/993605/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1934221] Re: systemd-resolve segfault

[Bug 1934221] Re: systemd-resolve segfault

[Bug 1934221] Re: systemd-resolve segfault

[Bug 1934221] Re: systemd-resolve segfault

[Bug 1934221] Re: systemd-resolve segfault

[Bug 1934221] Re: systemd-resolve segfault

[Bug 1934221] Re: systemd-resolve segfault

[Bug 1934221] Re: systemd-resolve segfault

[Bug 1934221] Re: systemd-resolve segfault

[Bug 1934221] Re: systemd-resolve segfault

[Bug 1934221] Re: systemd-resolve segfault

[Bug 1934221] Re: systemd-resolve segfault

[Bug 1934221] [NEW] systemd-resolve segfault

[Bug 1880654] Re: package python2-minimal 2.7.17-2ubuntu4 failed to install/upgrade: installed python2-minimal package post-installation script subprocess returned error exit status 1

[Bug 1880654] [NEW] package python2-minimal 2.7.17-2ubuntu4 failed to install/upgrade: installed python2-minimal package post-installation script subprocess returned error exit status 1

[Bug 1874569] Re: package collectd-core 5.9.2.g-1ubuntu5 failed to install/upgrade: installed collectd-core package post-installation script subprocess returned error exit status 1

[Bug 1739765] Re: xt_TCPMSS buffer overflow bug

[Bug 1740173] [NEW] package keyboard-configuration 1.108ubuntu15.3 failed to install/upgrade: subprocess installed post-installation script was killed by signal (Terminated)

[Bug 1739765] Re: xt_TCPMSS buffer overflow bug

[Bug 993605] [NEW] microcode update should be on by default

20 matches

Site Navigation

Mail list logo

Footer information