[01:30] Hey [01:31] augustin: 👋 [01:40] Hey, I'm aware of two bug in the kinetic daily build. [01:41] 1. gnome-shell crash when you try open file with gnome-text-editor from nautilus context menu. === jamesh_ is now known as jamesh [01:43] What can I do to help debug? [01:43] ylwghst: Just knowing that the bugs are there and how to reproduce them will help immensely with resolving them. [01:44] ylwghst: As for debugging, that depends entirely on the nature of the bug itself :) [01:44] Maybe it's a coding error, in which case identifying the bad code is the solution. Or maybe a config file is messed up, or... [01:45] This first #1 is kinda critical it completely crashes back to GDm. Ig there should be logs to get using journactl rigt? [01:45] ylwghst: Yeah, there probably are. What you probably want to do is run "ubuntu-bug nautilus" in a terminal, that should help you get started bug reporting. [01:46] ylwghst: You'll have to make an account on Launchpad (really Ubuntu One, the single sign-on system). The command will upload critical debugging files to Launchpad, and ask you to make a bug report. [01:46] ylwghst: Then describe in detail the steps to reproduce the issue, the expected result, the actual result, and the hardware that you are able to reproduce the issue on. [01:53] Can someone try to reproduce? [01:53] https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1988234 [01:53] Launchpad bug 1988234 in nautilus (Ubuntu) "Shell crash after leting file to be opened with gnome-text-editor" [Undecided, New] [02:45] The second bug is that opening Settings at Appearance resets every time dark mode to light mode (gtk legacy theme). [02:46] Anyone experienced this? [02:47] ylwghst: I think I've seen something similar, but maybe not. You might try asking in #ubuntu-next (though it doesn't get a whole lot of activity). [02:47] ylwghst: Also, nice job on that first bug report, that looks great. [03:02] I probably know why this happen. [03:03] is the ubuntu control center being patched? [03:03] to enable the accent funcionality? [03:03] where fix can be provided? [03:11] ylwghst: Thanks for providing that bug report, but devs are volunteers and can't work 24/7. You'll have to have patience. Doing the bug report is the right thing, but posting in here won't get it fixed any faster. [03:12] Support help is in #ubuntu, not here. [03:12] ylwghst: (Also note that #ubuntu-next is the channel for support of the development release of Ubuntu, that's probably where you want to be.) [04:54] https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1988246 [04:54] Launchpad bug 1988246 in gnome-control-center (Ubuntu) "Keep reseting appearance to light mode theme every background-panel load" [Undecided, New] === Mirv__ is now known as Mirv [09:00] didrocks: hi! did you see gregoa's question in LP: #1980662 ? i was going to ask the same, but he beat me to it [09:00] Launchpad bug 1980662 in lintian (Ubuntu) "[MIR] lib*-perl for lintian 2.115" [Undecided, Confirmed] https://launchpad.net/bugs/1980662 [09:02] ginggs: hum, seems that my answer was not clear enough as I mentioned those tests [09:08] didrocks: my understanding is the autodep8-perl-recommends test does a full build (including build tests) before running the autopkgtest bit [09:09] if you scroll up a bit in the autopkgtest logs, you can see the same tests that are run during the build [09:12] ginggs: ah, you‘re right, as I was scrolling down too much (after the second package install), I only saw the syntax checkers, not the package build + test build itself [09:12] ok, answering on the bug then, thanks ginggs! [09:14] didrocks: thanks [09:15] i think it's actually autodep8-perl-build-deps that does the build test, not autodep8-perl-recommends as i wrote above [09:16] yeah, it looks like it [09:17] it’s nice to have this package rebuild tests automatically for nothing [09:19] yeah, Debian Perl Group have some nice tooling [10:47] vorlon: Hi! rs2009 asked me if I can be an official uploader for Ubuntu Unity flavor. I already upload unity, compiz and indicator-* packages quite frequently, so I agreed. [11:03] hey mitya57 :) ty for your help and support [11:03] would be great if you could also send your statement to the Technical Board mailing list at technical-board@lists.ubuntu.com [11:28] Done === dbungert1 is now known as dbungert [15:40] mitya57: ping [15:41] Hi [15:41] mitya57: remind me your upload privs? MOTU? Core Dev? I ask only because I can't access it easy here (still rebuilding all my links and util scripts) [15:41] Core Dev [18:30] Hi! After the latest update yesterday my gdm3 / gnome / wayland session is not starting anymore [18:30] Not sure if this here is the right place to discuss this, please feel free to redirect me in case it's not :) [18:36] nicolasbock: #ubuntu+1 if you're on the devel series, otherwise #ubuntu [18:37] This is on kientic [19:47] Eickmeyer[m]: FYI upgrades from Groovy and Impish to Jammy are now supported so I don't think your response in bug 1988109 is correct [19:47] Bug 1988109 in ubuntu-release-upgrader (Ubuntu) "cant upgrade from 20.10 i have kubuntu with ubuntu studio addon" [Undecided, Invalid] https://launchpad.net/bugs/1988109 [19:48] bdmurray: I was under the impression that the groovy repo had been moved to old-releases. [19:49] Eickmeyer: sure but it shouldn't matter [19:50] OK, then I'll retract my comment and set to New. :) [19:51] Though, it seems kind of odd that they installed groovy *that day*. [19:51] That's not what I see InstallationDate: Installed on 2021-03-24 (523 days ago) [19:52] Oh, I was looking at the installation media, and "Upgraded to groovy 0 days ago". [19:52] * Eickmeyer 's brain is all over the place today [19:52] You were caught by bug 1315559 then [19:52] Bug 1315559 in apport (Ubuntu Kinetic) "UpgradeStatus can be incorrect" [Medium, Triaged] https://launchpad.net/bugs/1315559 [19:53] Ha! Looks familiar.