| feoh | Evening all | 03:56 |
|---|---|---|
| feoh | Anyone else seeing: dpkg: error processing archive /var/cache/apt/archives/libdleyna-core-1.0-5_0.6.0-3_amd64.deb (--unpack): in their apt dist-upgrade on 20.04? | 03:57 |
| lotuspsychje | lets see | 03:58 |
| lotuspsychje | feoh: i dont have that package installed, can you tell us wich package that it depens on? | 03:59 |
| feoh | Good question let me look up the apt syntax for that. | 04:00 |
| prologic | [13:57:24] <prologic>Is there a problem with the flocal-security repo on 20.04 right now? | 04:03 |
| prologic | [13:57:25] <prologic>E: The repository 'http://security.ubuntu.com/ubuntu focal-security InRelease' is not signed. | 04:03 |
| Bashing-om | !info libdleyna-core focal | 04:03 |
| ubottu | Package libdleyna-core does not exist in focal | 04:03 |
| lotuspsychje | prologic: can you pastebin the whole output plz? | 04:04 |
| prologic | Sure can | 04:04 |
| lotuspsychje | prologic: i just updated to latest, no issues with apt here | 04:04 |
| tomreyn | sudo /bin/true && cat &>/tmp/aptlog < <(sudo apt-get -y update 2>&1; apt-cache policy 2>&1; sudo apt-get -syV full-upgrade 2>&1;); nc termbin.com 9999 </tmp/aptlog && rm /tmp/aptlog | 04:04 |
| tomreyn | ^ can help diagnosing apt issues | 04:04 |
| feoh | tttThanks | 04:05 |
| prologic | https://gist.github.com/prologic/987a2084ef3b6fa6dc708b494c045248 | 04:05 |
| feoh | I'll give that a shot | 04:05 |
| feoh | I wonder if it got brought in when I installed krita | 04:06 |
| lotuspsychje | feoh: if you doublecheck, i can install & test if you want | 04:07 |
| tomreyn | prologic: are you using a proxy? | 04:07 |
| prologic | no | 04:07 |
| lotuspsychje | prologic: and for wich reason are you using backports on 20.04? | 04:07 |
| prologic | some packages I can't get on 20.04 | 04:08 |
| prologic | Also FWIW I'm using the upstream ubuntu:20.04 docker image as a base here | 04:08 |
| tomreyn | is this a regular ubuntu installation you did yourself? | 04:09 |
| feoh | lotuspsychje: No worries. I can't get any of the depends or rdepends or anything to leak what might have brought this package in. | 04:09 |
| tomreyn | where is the docker image from exactly? | 04:09 |
| feoh | DockerHub I'd wager :) | 04:09 |
| prologic | here https://hub.docker.com/layers/ubuntu/library/ubuntu/20.04/images/sha256-7345a0001b12b9d537ae2936205827ddd6a9aac6616943e67f9623d2ef338c52 | 04:09 |
| prologic | Anyway if there are no KP I'll carry on and figure this out on my own | 04:10 |
| prologic | it was working upuntil recently so I don't htink it was something I did necessarily :) | 04:11 |
| prologic | And the base image itself hasn't been updated in over a month | 04:11 |
| prologic | so 🤷♂️ | 04:11 |
| tomreyn | i assume 'KP' doesn't stand for 'kommunist party' but 'known problems' there? | 04:12 |
| prologic | D'oh I think I suspect whats happenning | 04:14 |
| tomreyn | i don't know who the publisher of this image is https://hub.docker.com/u/doijanky - or whether you should trust them. but i assume you researched this already. | 04:14 |
| prologic | Running out of disk space can cause this :) | 04:14 |
| prologic | stupid symptoms of a different underlying problem you can't see | 04:14 |
| tomreyn | oh interesting effect | 04:14 |
| prologic | indeed | 04:14 |
| prologic | Just confimring it now | 04:14 |
| prologic | Also I assume the publishers of the image are you guys :) | 04:15 |
| prologic | By "you guys" I mean someone in the Ubuntu development community/team :) | 04:15 |
| prologic | it is part of the Docker Hub "official images" afterall :) | 04:15 |
| prologic | Confirmed | 04:16 |
| tomreyn | could be, i don't know, but i'm not official ubuntu either. ;) | 04:16 |
| prologic | running out of disk space maeks apt go crazy with gpg signed repos | 04:16 |
| tomreyn | or i'm not anyways ;) | 04:17 |
| prologic | TIL | 04:17 |
| tomreyn | it's a rare result of running out of disk space, but obviously you shouldn't do that ni the first place. | 04:17 |
| prologic | obviously :) | 04:18 |
| prologic | but who monitors the disk space of ephemeral vms used for dev :) | 04:18 |
| tomreyn | not you ;-) | 04:18 |
| prologic | not anyone I suspect :D | 04:18 |
| prologic | Unless you're Fb and your dev machine is an ex production machine | 04:19 |
| lotuspsychje | prologic: does apt spit out same errors when disabling backports? | 04:19 |
| prologic | I didn't try sorry | 04:20 |
| prologic | it was Disk Space that caused this | 04:20 |
| tomreyn | the gist showed the error for multiple repositories, so i assume it would have | 04:20 |
| feoh | lotuspsychje: Wherever it came from I fixed the problem. The install was whining about failing to overwrite is an old version of the same package, so I just removed that, ran the apt --fix-broken install and everything worked. | 04:21 |
| feoh | Thank you for helping me prod at this and get it going ultimately :) | 04:21 |
| lotuspsychje | ok | 04:21 |
| lotuspsychje | feoh: so wich package was this about exactly? | 04:21 |
| feoh | libdleyna-core-1.0-3 | 04:22 |
| lotuspsychje | i know but was there a main package this depended on? | 04:22 |
| feoh | Depends: libgupnp-1.2-0 (>= 0.20.7) | 04:23 |
| feoh | That, libc, and glib2 | 04:23 |
| lotuspsychje | prologic feoh you guys have a launchpad account? | 04:25 |
| feoh | I do | 04:25 |
| lotuspsychje | feoh: wanna test an easy qbittorrent bug? | 04:25 |
| feoh | Absolutely! | 04:26 |
| feoh | Provided said testing is short-ish, I've gotta get sleep at some point along the curve :) | 04:26 |
| lotuspsychje | feoh: sudo apt install qbitorrent, and launch please | 04:26 |
| lotuspsychje | if it crashes for you, please affect bug #1862016 | 04:27 |
| ubottu | bug 1862016 in qbittorrent (Ubuntu) "qbittorrent crashed with SIGABRT in raise()" [Medium,Confirmed] https://launchpad.net/bugs/1862016 | 04:27 |
| feoh | installing | 04:27 |
| feoh | UI comes up just fine | 04:28 |
| feoh | Anything you need me to do further to validate other than just bringing up the GUI? | 04:28 |
| lotuspsychje | feoh: try to search function or adding a torrent | 04:28 |
| feoh | k | 04:28 |
| lotuspsychje | mine crashes after 3sec | 04:29 |
| lotuspsychje | doing nothing | 04:29 |
| feoh | Search works great | 04:31 |
| lotuspsychje | weird | 04:31 |
| feoh | Bummer. | 04:31 |
| feoh | I'm running stock Gnome | 04:31 |
| lotuspsychje | same | 04:31 |
| feoh | dunno if that has anything to do with it | 04:31 |
| feoh | huh | 04:31 |
| feoh | Anything else you'd like me to try? | 04:31 |
| lotuspsychje | feoh: try adding something after searching a keyword | 04:31 |
| feoh | Yup, attempting to download crashed it | 04:35 |
| feoh | Caught signal: SIGSEGV | 04:35 |
| lotuspsychje | yeah | 04:35 |
| lotuspsychje | affect yourself plz? | 04:36 |
| feoh | Pardon me? | 04:36 |
| feoh | Ah, twiddle the bug. Gotcha. | 04:36 |
| lotuspsychje | tnx for your time feoh | 04:37 |
| tomreyn | "This bug affects 1 person. Does this bug affect you?" | 04:37 |
| feoh | My pleasure happy to help | 04:38 |
| feoh | It's a nice client | 04:39 |
| lotuspsychje | feoh: here's another eay test if youre up to it, bug #1849787 | 05:26 |
| ubottu | bug 1849787 in gnome-shell-extension-ubuntu-dock (Ubuntu) "The dock is shown in front of full screen windows since 19.10" [Undecided,Confirmed] https://launchpad.net/bugs/1849787 | 05:26 |
| === cpaelzer__ is now known as cpaelzer | ||
| === cpaelzer__ is now known as cpaelzer | ||
| feoh | lotuspsychje: There's that sleep thing, but I just got paged out of bed again so. Yay? :) | 11:16 |
| feoh | I've also got a few of my own reported bugs in LP that I can validate as no longer being a thing in 20.04 | 11:17 |
| lotuspsychje | feoh: feel free to share, always glad to test things | 11:22 |
| user14 | Good day, anyone here tried to install 20.04 dev on a Hyper-V VM? | 11:50 |
| user14 | Well yes, 20.04 installs fine in Hyper-V, there seems to be no package for the 5.4 kernel specific for azure yet, so Enhanced session will not ben working. | 12:17 |
| arif-ali | what's the current state of focal for raspberry pi, I ran the daily from iso.qa.u.c, and setting up a bridge using netplan doesn't seem to be working after reboot, is that a known issue? Is this the best channel for this? | 13:51 |
| lotuspsychje | arif-ali: i did not test the iso for PI myself yet, but at this stage a lot is still changing, like the server installer is being worked on etc | 14:02 |
| lotuspsychje | there's still alot of breakage and bugs currently that need revision | 14:03 |
| arif-ali | lotuspsychje: no worries, I was able to boot it, and get an ip on it without a problem. doing a netplan try/apply works, and the bridge gets an IP. But the bridge doesn't come up with ipv4 on startup. | 14:04 |
| lotuspsychje | arif-ali: do you suspect a specific package? | 14:05 |
| lotuspsychje | we could check the packagename's recent bugs for example on fossa | 14:06 |
| arif-ali | will have to dig deep on where specifically the issue is that is causing it, may have to do that after EOD | 14:07 |
| lotuspsychje | arif-ali: this user for example filed one against systemd: bug #1860926 | 14:08 |
| ubottu | bug 1860926 in systemd (Ubuntu) "Ubuntu 20.04 Systemd fails to configure bridged network" [Undecided,New] https://launchpad.net/bugs/1860926 | 14:08 |
| arif-ali | ok, that could be it, thanks | 14:10 |
| lotuspsychje | if you suspect its the same, please affect yourself to the bug, this helps the community to solve | 14:10 |
| arif-ali | I was searching specifically for rpi, and not more generally | 14:10 |
| arif-ali | yeah, will do | 14:10 |
| lotuspsychje | tnx | 14:10 |
| lotuspsychje | arif-ali: did you find it similar? | 14:36 |
| lotuspsychje | feoh: did you report bug #1862782 ? | 15:08 |
| ubottu | bug 1862782 in dleyna-core (Ubuntu) "package libdleyna-core-1.0-5 (not installed) failed to install/upgrade: poging tot overschrijven van '/usr/lib/x86_64-linux-gnu/libdleyna-core-1.0.so.5.0.0', wat ook in pakket libdleyna-core-1.0-3:amd64 0.6.0-1 zit" [Undecided,New] https://launchpad.net/bugs/1862782 | 15:08 |
| feoh | I didn't | 15:30 |
| lotuspsychje | feoh: then can you doublecheck if that was your issue yesterday? | 15:31 |
| arif-ali | lotuspsychje: it does look similar, but I will double check later, when I can verify and test the particular scenario. I want to start from a fresh flash of the image, and ensure I follow the same steps as that bug | 15:46 |
| lotuspsychje | great, tnx for taking your time for it arif-ali | 15:46 |
| lotuspsychje | in this stage, we can use all the help :p | 15:46 |
| arif-ali | :) no worries | 15:48 |
| feoh | lotuspsychjesure | 15:49 |
| lotuspsychje | tnx feoh that looks like the same package of your issue right? | 15:49 |
| feoh | yes. marked it as affecting me and posted my successful work-around. | 15:54 |
| lotuspsychje | +1 for your work feoh ; ) | 15:54 |
| feoh | Pleasure. | 15:57 |
| feoh | lotuspsychje: I have a couple of bugs I reported in prior releases that are fixed in 20.04 - what's the appropriate step for me to take to mark them as such? It's not clear to me from Launchpad's web UI. | 16:08 |
| feoh | I don't see a "Resolve as fixed" button :) | 16:08 |
| lotuspsychje | feoh: well normal case scenario's we let the devs decide when a bug is fixxed | 16:09 |
| lotuspsychje | but more expert users playing well with launchpad can do it themselfs too | 16:09 |
| lotuspsychje | depending on your skills | 16:09 |
| lotuspsychje | personally, i dont touch it myself | 16:10 |
| feoh | OK so I'll just comment that as a the reporter I can vouch for it as being fixed | 16:10 |
| feoh | Thanks! | 16:10 |
| lotuspsychje | feoh: yes, a user can always add a comment, its fixxed on his side | 16:10 |
| lotuspsychje | feoh: other users and devs will read & test if they can also fix the same way | 16:13 |
| feoh | Great. Did that. Thanks. | 16:13 |
| lotuspsychje | feoh: oh well, a bug created on 18.04 and got marked fixed, should not be a bug anymore in higher ubuntu releases, so you should not specific mark it solved anymore | 16:17 |
| lotuspsychje | feoh: the way around is possible, if the bug would still be there in 20.04 you can add a comment | 16:18 |
| feoh | OK so was I wrong to comment about it being fixed in 20.04? | 16:18 |
| lotuspsychje | yeah reading your 18.04 bug made me realize | 16:19 |
| feoh | How can I know whether or not that's the case? | 16:21 |
| feoh | Gonna chalk it up to "I don't think my comments did any harm" and just not do that next time if the bugs are old :) | 16:35 |
| lotuspsychje | !bug | feoh the official etiquette | 16:42 |
| ubottu | feoh the official etiquette: If you find a bug in Ubuntu or any of its official !flavors, please report it using the command « ubuntu-bug <package> » - See https://help.ubuntu.com/community/ReportingBugs for other ways to report bugs. | 16:42 |
| feoh | Thanks. FWIW the devs closed 2/3 of the bugs I commented on so I think that was the right call. | 20:51 |
| feoh | But I'll also read that :) | 20:52 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!