| lotuspsychje | mort: we reccomend to ask about your bug first, maybe other volunteers know what its about before you file a new !bug | 07:39 |
|---|---|---|
| mort | Alright | 07:40 |
| mort | so, there's two things: 1) the CUPS daemon seems to be unable to exit, blocking shutdown for the entire 90 seconds (systemd's default timeout); and 2) apport-autoreport enters an infinite restart loop and causes PID 1 to use 100% CPU in a busy loop | 07:41 |
| mort | https://p.mort.coffee/PLs is a log for #2, "Process error reports when automatic reporting is enabled" is the description for apport-autoreport and its log lines are prefixed with whoopsie-upload-all | 07:44 |
| lotuspsychje | mort: for cups, i dont see new bugs right away related to your issue: https://launchpad.net/ubuntu/+source/cups/+bugs?orderby=importance&start=0 | 07:46 |
| mort | it seems to be cups-browsed.service according to my logs | 07:47 |
| lotuspsychje | mort: what you can try to do, is install stacer, and try to off/on cups, see if this influences? | 07:48 |
| mort | alright | 07:49 |
| mort | the good news is that `sudo systemctl stop cups-browsed` also hangs, so it's not some super weird shutdown-only bug | 07:49 |
| lotuspsychje | mort: for your apport, i think it might be bug #1894369 | 07:51 |
| ubottu | bug 1894369 in apport (Ubuntu) "apport-autoreport.service fails to start in groovy after upgrading from focal" [Undecided,Confirmed] https://launchpad.net/bugs/1894369 | 07:51 |
| mort | ubottu: thanks, yeah that looks like it | 07:52 |
| ubottu | mort: I am only a bot, please don't think I'm intelligent :) | 07:52 |
| mort | :D | 07:52 |
| mort | meant to prefix with lotuspsychje not ubottu | 07:52 |
| lotuspsychje | mort: cool, affect yourself to the bug if you think it suits you | 07:54 |
| mort | I did | 07:54 |
| lotuspsychje | and thanks for the report and make ubuntu better | 07:54 |
| mort | I'll add some logs and such too I think | 07:54 |
| lotuspsychje | cool | 07:55 |
| lotuspsychje | i had some apport issues in the past, sometimes it also helps reinstalling apport | 07:55 |
| mort | stacer just freezes when I try to flip the "running now" switch, presumably because it waits for the service to shut down which never happens | 07:55 |
| mort | oh, it actually eventually shut down, just after a really really long time | 07:56 |
| lotuspsychje | mort: allright that might be worth to file a new bug for | 07:57 |
| mort | ah no that's just systemd killing it with SIGKILL | 07:57 |
| mort | Alright, bug #1895265 is a thing now | 08:27 |
| ubottu | bug 1895265 in cups (Ubuntu) "cups-browsed fails to exit when systemd tries to shut it down (SIGTERM)" [Undecided,New] https://launchpad.net/bugs/1895265 | 08:27 |
| mort | lotuspsychje: though, I feel like it's fairly likely for what looks like a minor bug in cups-browsed to go overlooked. Is there something I can do to make it obvious that this bug actually affects Ubuntu as a whole, even for users who never touch cups, because it hangs boot? | 08:29 |
| mort | hangs shutdown* | 08:32 |
| === guiverc2 is now known as guiverc | ||
| lotuspsychje | mort: hmm, think we would have to find us more users affected first to prove it, then we maybe can see to add a package like systemd or linux | 08:57 |
| lotuspsychje | mort: could you also apport-collect 1895265 please, so relevant info about your system gets dragged into the bug? | 09:00 |
| mort | done | 09:02 |
| lotuspsychje | thank you mort | 09:03 |
| mort | hey look at that, apport created an apport_dump_acpi_tables.py.1000.crash in /var/crash so that other bug triggered | 09:04 |
| mort | haha | 09:04 |
| lotuspsychje | lol | 09:04 |
| lotuspsychje | !info linux-image-generic | 09:05 |
| ubottu | linux-image-generic (source: linux-meta): Generic Linux kernel image. In component main, is optional. Version 5.4.0.26.32 (groovy), package size 2 kB, installed size 17 kB | 09:05 |
| lotuspsychje | hmm | 09:05 |
| lotuspsychje | is this current groovy kernel? | 09:05 |
| mort | I'm on groovy, `uname -a` says Linux ubun 5.4.0-42-generic #46-Ubuntu SMP Fri Jul 10 00:24:02 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux | 09:06 |
| lotuspsychje | seems to differ with your dmesg yeah | 09:06 |
| mort | or does it; 5.4.0.26.32 is a 5.4.0 kernel | 09:07 |
| lotuspsychje | guiverc: what gives your uname -a on groovy plz? | 09:08 |
| mort | `apt-cache policy linux-image-generic` says 5.8.0.18.22 is installed, huh | 09:08 |
| mort | maybe I selected this kernel manually in grub once and it's just been like that since | 09:08 |
| guiverc | my current (primary) box reports 5.8.0-18; I've shutdown the system I tested on though | 09:09 |
| lotuspsychje | tnx guiverc | 09:09 |
| lotuspsychje | so mort better test all your bugs again on 5.8 now | 09:09 |
| mort | yea | 09:09 |
| mort | none of the bugs seem immediately related to the kernel, but it could make a difference | 09:10 |
| guiverc | 5.8.0-18-generic | 09:10 |
| lotuspsychje | so the bot needs an update eh | 09:10 |
| guiverc | that's not on today's lubuntu daily; it won't boot on some boxes again today :( | 09:12 |
| lotuspsychje | aw | 09:13 |
| lotuspsychje | mort: the cups one surely boot into 5.8 and update your bug mentioning it happens also there | 09:13 |
| lotuspsychje | and apport too :p | 09:14 |
| mort | I'm on 5.8.0-18-generic now, doesn't seem to have affected cups at all | 09:14 |
| mort | it still fails to shut down | 09:14 |
| lotuspsychje | allright, tnx for testing, but do describe it anyway, so the devs dont get confused about your currentdmesg | 09:15 |
| mort | just triggered the apport bug too (by running a segfaulting program in valgrind, which makes valgrind put a .crash file in /var/crash) | 09:16 |
| mort | should I apport-collect again or just add a comment saying it also happens on 5.8? | 09:17 |
| lotuspsychje | mort: just add a comment you tested it on 5.8 current kernels where it happens the same yeah | 09:18 |
| mort | alright, done | 09:19 |
| lotuspsychje | mort: great, thank you! | 09:20 |
| alichtman | Hey, so I've recently run an update and rebooted later, only to find an issue with libffi. Terminal fails to open with the error "ImportError: libffi.so.7: cannot open shared object file: No such file or directory | 23:19 |
| alichtman | /usr/lib.x86_64-linux-gnu/libffi.so is linked to libffi.so.8.1.0 | 23:20 |
| alichtman | and I can't just hotswap in 8.1.0 for 7 | 23:23 |
| alichtman | I have semi-recent backups I can restore to but I'd rather fix this | 23:27 |
| alichtman | It seems fixable | 23:27 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!