[01:11] -lugito:#lubuntu-devel- [rMANUALf0d1f8f6ea0f: Spellcheck firefox] lynorian (Lyn Perrine) committed: https://phab.lubuntu.me/rMANUALf0d1f8f6ea0f [01:15] -lugito:#lubuntu-devel- [rMANUAL5d5d1c2e8afa: Fix grammar in Quassel summary] lynorian (Lyn Perrine) committed: https://phab.lubuntu.me/rMANUAL5d5d1c2e8afa [01:18] -lugito:#lubuntu-devel- [rMANUAL1ec9671ad612: Improve wording on hiding events making not notice things easier] lynorian (Lyn Perrine) committed: https://phab.lubuntu.me/rMANUAL1ec9671ad612 [01:26] -lugito:#lubuntu-devel- [rMANUAL67883125a7a7: Improve wording of connecting to an irc network] lynorian (Lyn Perrine) committed: https://phab.lubuntu.me/rMANUAL67883125a7a7 [01:30] -lugito:#lubuntu-devel- [rMANUAL67773907b50c: Add Rename button in quassel irc] lynorian (Lyn Perrine) committed: https://phab.lubuntu.me/rMANUAL67773907b50c [01:37] -lugito:#lubuntu-devel- [rMANUALe185269ddf9c: Add /part to quit an irc channel] lynorian (Lyn Perrine) committed: https://phab.lubuntu.me/rMANUALe185269ddf9c [02:03] -lugito:#lubuntu-devel- [rMANUALfe6bae5b7c81: Add /nick to change nickname] lynorian (Lyn Perrine) committed: https://phab.lubuntu.me/rMANUALfe6bae5b7c81 [10:38] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_liblxqt just failed after succeeding: https://ci.lubuntu.me/job/focal_stable_liblxqt/554/ [10:38] -lugito:#lubuntu-devel- [Lubuntu CI] groovy_stable_libfm-qt FAILURE: https://ci.lubuntu.me/job/groovy_stable_libfm-qt/447/ [10:38] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_lxqt-config just failed after succeeding: https://ci.lubuntu.me/job/focal_stable_lxqt-config/637/ [10:39] -lugito:#lubuntu-devel- [Lubuntu CI] hirsute_stable_libfm-qt FAILURE: https://ci.lubuntu.me/job/hirsute_stable_libfm-qt/105/ [10:39] -lugito:#lubuntu-devel- [Lubuntu CI] groovy_stable_libfm-qt FAILURE: https://ci.lubuntu.me/job/groovy_stable_libfm-qt/447/ [10:49] -lugito:#lubuntu-devel- [Lubuntu CI] hirsute_stable_libfm-qt FAILURE: https://ci.lubuntu.me/job/hirsute_stable_libfm-qt/106/ [11:30] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_lxqt-config just failed after succeeding: https://ci.lubuntu.me/job/focal_stable_lxqt-config/637/ [12:01] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_lxqt-archiver UNSTABLE: https://ci.lubuntu.me/job/focal_stable_lxqt-archiver/313/ [12:15] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_lxqt-runner just failed after succeeding: https://ci.lubuntu.me/job/focal_stable_lxqt-runner/551/ [12:26] -lugito:#lubuntu-devel- [Lubuntu CI] groovy_stable_lxqt-archiver FAILURE: https://ci.lubuntu.me/job/groovy_stable_lxqt-archiver/457/ [12:42] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_lxqt-runner just failed after succeeding: https://ci.lubuntu.me/job/focal_stable_lxqt-runner/551/ [13:03] -lugito:#lubuntu-devel- [Lubuntu CI] hirsute_stable_lxqt-archiver FAILURE: https://ci.lubuntu.me/job/hirsute_stable_lxqt-archiver/108/ [13:18] -lugito:#lubuntu-devel- [Lubuntu CI] hirsute_stable_lxqt-archiver FAILURE: https://ci.lubuntu.me/job/hirsute_stable_lxqt-archiver/109/ [13:50] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_lxqt-archiver UNSTABLE: https://ci.lubuntu.me/job/focal_stable_lxqt-archiver/314/ [14:04] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_lxqt-runner just failed after succeeding: https://ci.lubuntu.me/job/focal_stable_lxqt-runner/551/ [14:06] -lugito:#lubuntu-devel- [Lubuntu CI] hirsute_stable_lxqt-openssh-askpass just failed after succeeding: https://ci.lubuntu.me/job/hirsute_stable_lxqt-openssh-askpass/58/ [14:15] -lugito:#lubuntu-devel- [Lubuntu CI] groovy_stable_lxqt-archiver FAILURE: https://ci.lubuntu.me/job/groovy_stable_lxqt-archiver/457/ === KGIII1 is now known as KGIII [15:12] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_qterminal just succeeded after failing: https://ci.lubuntu.me/job/focal_stable_qterminal/834/ [17:13] -lugito:#lubuntu-devel- [T109: Manual as PDF] apt-ghetto (apt-ghetto) commented on the task: https://phab.lubuntu.me/T109#3976 [17:15] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_sddm FAILURE: https://ci.lubuntu.me/job/focal_stable_sddm/583/ [17:16] -lugito:#lubuntu-devel- [Lubuntu CI] hirsute_stable_sddm just became unstable after failing: https://ci.lubuntu.me/job/hirsute_stable_sddm/88/ [17:16] -lugito:#lubuntu-devel- [Lubuntu CI] groovy_stable_sddm UNSTABLE: https://ci.lubuntu.me/job/groovy_stable_sddm/341/ [17:52] -lugito:#lubuntu-devel- [Lubuntu CI] hirsute_stable_sddm UNSTABLE: https://ci.lubuntu.me/job/hirsute_stable_sddm/89/ [17:52] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_sddm just became unstable after failing: https://ci.lubuntu.me/job/focal_stable_sddm/584/ [17:53] -lugito:#lubuntu-devel- [Lubuntu CI] groovy_stable_sddm UNSTABLE: https://ci.lubuntu.me/job/groovy_stable_sddm/342/ [18:06] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_liblxqt FAILURE: https://ci.lubuntu.me/job/focal_stable_liblxqt/554/ [18:20] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_liblxqt just succeeded after failing: https://ci.lubuntu.me/job/focal_stable_liblxqt/555/ [18:21] -lugito:#lubuntu-devel- [Lubuntu CI] groovy_stable_libfm-qt FAILURE: https://ci.lubuntu.me/job/groovy_stable_libfm-qt/448/ [18:22] -lugito:#lubuntu-devel- [Lubuntu CI] hirsute_stable_libfm-qt FAILURE: https://ci.lubuntu.me/job/hirsute_stable_libfm-qt/107/ [18:36] -lugito:#lubuntu-devel- [T109: Manual as PDF] wxl (Walter Lapchynski) commented on the task: https://phab.lubuntu.me/T109#3978 [18:41] -lugito:#lubuntu-devel- [Lubuntu CI] hirsute_stable_lxqt-archiver FAILURE: https://ci.lubuntu.me/job/hirsute_stable_lxqt-archiver/110/ [18:41] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_sddm just became unstable after failing: https://ci.lubuntu.me/job/focal_stable_sddm/584/ [18:41] -lugito:#lubuntu-devel- [Lubuntu CI] hirsute_stable_sddm UNSTABLE: https://ci.lubuntu.me/job/hirsute_stable_sddm/89/ [18:41] -lugito:#lubuntu-devel- [Lubuntu CI] groovy_stable_sddm UNSTABLE: https://ci.lubuntu.me/job/groovy_stable_sddm/342/ [18:42] -lugito:#lubuntu-devel- [Lubuntu CI] hirsute_stable_lxqt-openssh-askpass FAILURE: https://ci.lubuntu.me/job/hirsute_stable_lxqt-openssh-askpass/59/ [18:45] -lugito:#lubuntu-devel- [Lubuntu CI] groovy_stable_lxqt-archiver FAILURE: https://ci.lubuntu.me/job/groovy_stable_lxqt-archiver/458/ [18:47] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_lxqt-config just succeeded after failing: https://ci.lubuntu.me/job/focal_stable_lxqt-config/638/ [18:47] -lugito:#lubuntu-devel- [Lubuntu CI] hirsute_stable_libfm-qt FAILURE: https://ci.lubuntu.me/job/hirsute_stable_libfm-qt/107/ [18:48] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_lxqt-runner just succeeded after failing: https://ci.lubuntu.me/job/focal_stable_lxqt-runner/552/ [18:56] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_sddm just became unstable after failing: https://ci.lubuntu.me/job/focal_stable_sddm/584/ [18:56] -lugito:#lubuntu-devel- [Lubuntu CI] hirsute_stable_sddm UNSTABLE: https://ci.lubuntu.me/job/hirsute_stable_sddm/89/ [18:56] -lugito:#lubuntu-devel- [Lubuntu CI] groovy_stable_sddm UNSTABLE: https://ci.lubuntu.me/job/groovy_stable_sddm/342/ [18:57] -lugito:#lubuntu-devel- [Lubuntu CI] groovy_stable_libfm-qt FAILURE: https://ci.lubuntu.me/job/groovy_stable_libfm-qt/449/ [18:58] -lugito:#lubuntu-devel- [Lubuntu CI] hirsute_stable_libfm-qt FAILURE: https://ci.lubuntu.me/job/hirsute_stable_libfm-qt/108/ [19:11] -lugito:#lubuntu-devel- [Lubuntu CI] groovy_stable_lxqt-archiver FAILURE: https://ci.lubuntu.me/job/groovy_stable_lxqt-archiver/459/ [19:12] -lugito:#lubuntu-devel- [Lubuntu CI] hirsute_stable_lxqt-archiver FAILURE: https://ci.lubuntu.me/job/hirsute_stable_lxqt-archiver/111/ [19:23] -lugito:#lubuntu-devel- [Lubuntu CI] hirsute_stable_lxqt-openssh-askpass just succeeded after failing: https://ci.lubuntu.me/job/hirsute_stable_lxqt-openssh-askpass/60/ [19:59] is there a problem with github login on discourse? [20:00] I don't think so but let me try in a private window. [20:01] Oh, there might be. It seems to be taking a bit. [20:03] @teward001 ^^^ any ideas? [20:05] [telegram] same here w7 username+password (re @lubuntu_bot: (irc) is there a problem with github login on discourse?) [20:07] huh even a normal password login isn't working [20:08] @kc2bez could you make a ticket for teward? [20:08] [telegram] will do [20:08] [telegram] FYI [20:09] [telegram] that's all because of the single host node discourse runs on [20:09] [telegram] so that could be a factor if DO is taking a shit. [20:09] [telegram] also sorry been dealing with a work security issue that's angering me, the accidental slip there is not normal [20:09] !language | @teward001 [20:09] @teward001: Please avoid any language that may be considered offensive, including acronyms and obfuscation of such - also see https://wiki.ubuntu.com/IRC/Guidelines || The main channels are English only, for other languages, see https://wiki.ubuntu.com/IRC/ChannelList [20:09] :P [20:09] [telegram] *smacks kc2bez between here and the void and back* [20:11] [telegram] XD [20:14] [telegram] it may be necessary to reboot the DO node [20:14] [telegram] because this is a docker container [20:14] [telegram] not much I can do in terms of *debugging* [20:16] [telegram] oh this might be an easy fix [20:16] [telegram] stdby [20:19] [telegram] kc2bez: wxl: I think it was the CSP - again - this time with certain sandboxing restrictions. allow-forms was not on and should've been (I'm an idiot) [20:19] [telegram] try again. [20:19] [telegram] note though that even if the form never moves it DOES actually log you in heh [20:21] [telegram] I was able to login [20:21] [telegram] from scratch? [20:21] [telegram] wxl: you reported it so test it :P [20:22] [telegram] test the GH login option too [20:22] [telegram] if it's working again then I can mark the ticket resolved [20:22] [telegram] Same here .. (re @kc2bez: I was able to login) [20:26] [telegram] I think it is safe to close it up, I used the GH login in a private window. [20:30] [telegram] 👍 [20:34] [telegram] is kgiii around? [20:34] [telegram] somewhere? [20:35] paging KGIII to the devel channel XD [20:35] [telegram] lol [20:35] [telegram] kc2bez: I can poke em elsewhere [20:35] works thx [20:36] [telegram] kc2bez: you'll know why if you check the ticket changes :P [20:36] I show them idle here in IRC @teward001 [20:43] Yes? [20:43] [telegram] KGIII see incoming PMs [21:01] !standup [21:02] i'm here but i need to go last [21:02] ok [21:02] what happened to the bot? [21:02] it's there [21:02] * wxl kicks ubot93 [21:03] [telegram] Here but house full of guests - Happy new year [21:03] Happy New Year @Leokolb [21:04] Happy New Year. [21:04] Since the bot is sleeping. I'll fire it off manually. [21:04] @tsimonq2 @lynorian @HMollerCl @aptghetto @teward001 @kc2bez @The_LoudSpeaker wxl[m] guiverc @N0um3n0 @leokolb @KGIII — It's 2100 UTC Thursday which means it's time for the Lubuntu Development standup meeting. Please announce yourself for roll call! Then, in order of announcement, post your items, and be sure to mention when you're done. [21:05] I am here. [21:05] ack [21:05] [telegram] /o [21:05] * guiverc physically present [21:05] [telegram] *drops a grenade on kc2bez* IT'S NEW YEARS EVE WE CAN DO WITHOUT THE CHECKIN! *salts the meeting* [21:06] :P [21:06] * guiverc escaped from 2020 already :) [21:06] This should be relatively short [21:06] [telegram] *condemns guiverc to the salt mine which isn't in 2021 yet* [21:06] [telegram] :P [21:07] [telegram] i can go first because i have to go make food shortly [21:07] [telegram] BUT [21:07] go ahead [21:07] [telegram] fixed some issues with CI, including latest updates to the CI system (enjoy it, because Simon didn't break it this time!) [21:07] [telegram] Stabilized CI because it was using way too many concurrent processes and that caused things to be chaotic. [21:07] [telegram] Discourse works again after more ongoing issues enjoy that everyone [21:08] [telegram] and y'all have a good new years :) [21:08] [telegram] *goes to cook a huge hunk of ham* [21:08] Thanks for everything @teward001 [21:08] Enjoy the ham [21:08] [telegram] that's dinner round 1 xD [21:08] [telegram] dinner round 2 is later (chinese!) [21:08] [telegram] [21:09] guiverc: we will work from the bottom up so go ahead [21:09] thanks thomas [21:09] - re-opening more autoclosed discourse threads, marking others solved when I can find suitable answer [21:09] - intermittent EFI error message on BIOS box; tested for what I thought was cause; nope.. [21:09] - general support [21:10] * guiverc all I remember, done [21:10] Thanks as always for all your help. [21:10] thanks for all of that [21:10] * guiverc EFI message is during installs; ie. calamares [21:11] Ok [21:11] [telegram] guiverc: which categories were the autoclosed threads in [21:11] I saw one of your bugs re: install via the menu. [21:11] [telegram] if they're global i can fix the autoclose periods [21:12] it should be support [21:12] @teward001 support [21:12] sorry, as wxl said... (not very awaake) [21:13] we autoclose at a month out [21:13] that seems pretty generous all things considered [21:13] it would be nice if we could do a two-stage thing [21:14] like 15 days out there's a message that the topic will close in 15 days with no activity [21:14] and then it closes 15 days after [21:14] but whatever [21:15] [telegram] wxl: the autoclose is actually 720 hours from last post on the category itself [21:15] right [21:15] [telegram] that doesn't seem long enough [21:15] [telegram] and that's 30 days [21:15] that's [21:16] 30 [21:16] days [21:16] [telegram] i mean :P [21:16] that's also referred to commonly as "a month" XD [21:16] back to the install from the menu, one of the icons should be hidden but this bug exists https://github.com/lxqt/lxqt/issues/1743 [21:16] Issue 1743 in lxqt/lxqt "Desktop files with NotShowIn=LXQt are still displayed in the menu" [Open] [21:16] shooot wtf [21:17] bang [21:17] [telegram] wxl: maybe we should do 45 days then for support but that's your call :) [21:17] [telegram] you all can just enjoy the rest of your bugs ;) [21:18] anything else guiverc ? [21:18] thank you wxl, kc2bez, @teward [21:19] Most welcome and thank you. [21:19] * guiverc lifts head, nah, head back down on bench [21:19] *picks up guiverc, puts guiverc on a bed and puts blankets over them* go rest noob [21:19] ;) [21:20] [telegram] o/ [21:20] :) [21:20] ack lynorian [21:20] nite nite guiverc [21:20] @Leokolb did you have anything else [21:20] added you a comment on your bug kc2bez [21:21] ok, thanks I think [21:22] Ah, yes [21:22] Thanks for the backup [21:23] I think Leó is enjoying his house guests. [21:24] KGIII: over to you [21:24] Ham sounds delicious, but I digress. Testing is going well, though I noticed you can't install with just a keyboard. At least not with my setup. You can tab to the buttons, but the enter button on the keyboard doesn't do a darned thing. I just noticed this today, so I plan on checking future builds. I do some support here and there and will continue with that. That is everything. [21:24] Thanks! [21:25] And, thanks to y'all for being so friendly and informative. [21:25] I don't know that I have tried a KB install recently. [21:25] I may need to test that too. [21:26] I VNC into a remote computer and do it all there, so it could be something there. I'll get off my butt and go into the other room tomorrow. [21:26] sounds good [21:26] I doubt it's VNC related, but I'll eliminate that. [21:26] Well, maybe on the 2nd - I may drink some wine tonight. [21:26] Thank you KGIII ! [21:27] @lynorian over to you [21:27] KGIII: space instead of enter? [21:27] Lemme check. One sec. [21:28] Space does indeed work - but that's definitely not intuitive. (At least it wasn't to me.) [21:28] [telegram] I checked discourse and found ubun-ie had found an typo and then fixed that and put in all version of manual with cherry pick [21:29] [telegram] I found a typo in firefox and brightness and fixed [21:29] [telegram] I improved wording on quassel as well [21:29] KGIII: that said, a little wishlist bug on the cala github might be a worthwhile addition. you want to throw that in? [21:29] [telegram] also added /part and /nick to quassel [21:31] great work lyn! did you see the manual pdf project btw?????????????? [21:31] [telegram] that is all I have [21:32] thank you @lynorian, the manual is a great ref to link to in support! You've done great work [21:32] [telegram] I actualy haven't done much of that [21:32] That is great lyn! [21:32] I'll make a note of it and grab it later tonight or tomorrow. I also can't seem to find a keyboard method to select 'erase disk' 'replace a partition' etc... I'll start writing it up now. [21:32] well it all happened iwithout you :) [21:32] [telegram] xelatex use actually fixed that and someone else had that Idea I just apporved it [21:33] well it makes me happy, i'll tell you that [21:33] i love our team :) [21:33] +100000 [21:34] I will go [21:34] Last meeting for the year :P [21:34] * Worked with teward to help get the manual building as a pdf in CI. More to do there but I think we have a good start on something very useful. Thanks to everyone involved on that. [21:34] * Also worked with teward on getting some of the builds more stable in CI [21:34] * We have some packaging fixups to happen over there. [21:34] * Worked with teward to setup incoming mail to Discourse. wxl chime in with your thoughts. Here is what is setup so far: [21:34] * lubuntu-feedback@ (selfexplanatory). support@ goes to discourse site support category. lubuntu-feedback@ goes to the Lubuntu Feedback category, feedback@ goes to the discourse site feedback category [21:35] ^^ my goal here is to have a mailing-list like interface to Discourse, so among other things, i can send announcements by email to both the email list and Discourse [21:36] [telegram] sorry ..back again [21:36] OK, makes sense wxl, We should add announcements then [21:36] yeah [21:37] If you have anything @Leokolb jump in [21:37] devel probably too [21:37] ok [21:38] [telegram] Testing - Samba - playing with swap partitions and Rasp pi4 not much new here [21:38] Thanks for continuing to work on those [21:38] @KGIII: just a little context here's a bug that discusses keyboard navigation and it seems to suggest that space is the right key for activation. so it may be good in that bug to acknowledge that this is expected behavior, albeit not necessarily intuitive. perhaps we could have both space AND enter? [21:38] @leokolb sorry i haven't got back to you on all that [21:39] LOL That's almost verbatim of my rough-draft write-up that I'm working on. [21:39] [telegram] no problem - more time after the holidays [21:39] @KGIII: oops forgot the link https://github.com/calamares/calamares/issues/1213 [21:39] Issue 1213 in calamares/calamares "v2 slideshow API loading breaks keyboard navigation in the mainwindow" [Closed] [21:39] @leokolb totes. holidays have been nuts over here. [21:40] Same here. [21:40] [telegram] called away again - Thanks all for a great year [21:40] I have that it's the expected behavior but not intuitive and that the enter key should be also able to work. [21:40] Oh, and I noticed something else. Whoever came up with the idea of multiple languages for support in Discourse, that's a brilliant choice. I see quite a few posts there and it hasn't even existed for very long. [21:41] Thank you @Leokolb [21:41] be well @leokolb and thank you very much [21:41] [telegram] For my part, nothing more than do support, it seems that the German and Italian groups are moving a bit. people start to enter the groups from the irc too [21:41] @KGIII: that is all @N0um3n0's doing, really. i helped implement it (and the IRC channels) but it's not really my baby. [21:41] It warms my heart to see the activity [21:42] ^^^ agreed [21:42] like that's the best Lubuntu news all year, IMHO [21:42] It really is good stuff [21:42] I don't have much else. Spent some time poking at some support things on Discourse and ask Ubuntu. [21:43] It's starting off very, very well. [21:43] speaking of @N0um3n0 i see that @guiverc opened up this can of worms again https://discourse.lubuntu.me/t/cant-change-keyboard-locale-on-logon-screen-with-lxqt-lubuntu-19-04-19-10-and-20-04/1377 but i'm struggling to make sense of all this. can you help? mostly the question i have is this: how can we or the software we use (calamares?) do better to ensure this is not a probelm? [21:44] [telegram] you did almost all the work! now it seems that everything is starting to work;) thank you very much everyone! [21:45] @N0um3n0 any more ideas you have with regards to helping improve non-English language support, please let me know. i think we're all very excited about it. [21:46] Thank you @N0um3n0 [21:46] wxl: I wonder if we are not running into issues with fcitx https://github.com/lxqt/lxqt/issues/1858 [21:46] Issue 1858 in lxqt/lxqt "Global keyboard layout doesn't work" [Closed] [21:46] [telegram] the problem is that sddm takes the locale configuration, if you install in Russian you cannot put a password in English. solution, install in English and add keyboard in Russian, tested and working perfect [21:47] maybe we should add a warning or something about that [21:47] [telegram] Ok, perfect! (re @lubuntu_bot: (irc) @N0um3n0 any more ideas you have with regards to helping improve non-English language support, please let me know. i think we're all very excited about it.) [21:47] [telegram] I am not the best person for locale stuff [21:48] is the issue really here that sddm doesn't deal right with locales? or can calamares somehow do better? [21:48] me either [21:48] I can barely handle one language [21:48] indeed [21:49] Hey now, you weren't supposed to be so agreeable. :P [21:49] I think you are all that is left wxl [21:49] ok [21:50] well like i said things have been nuts so i'm struggling to recount all the things i did do XD [21:50] mostly i think it was support and stuff [21:50] * guiverc raises head, nothing to say, so head returns to bench [21:50] i continue to foolishly assist fritz in his attempt to unravel why he's got an old kernel XD [21:50] same here XD [21:51] [telegram] plasma have the same problem with Russian users ... (re @lubuntu_bot: (irc) is the issue really here that sddm doesn't deal right with locales? or can calamares somehow do better?) [21:51] had someone who wanted their discourse account deleted and that's a contentious subject in discourse so i made a definitive document about it https://discourse.lubuntu.me/t/how-to-delete-your-account/2007 [21:51] [telegram] In sddm [21:51] I thought you said it well wxl (anonimized account) [21:51] That is good to know @N0um3n0 [21:52] @N0um3n0 i might go ask the kubuntu folks what their feelings are about it [21:52] i think it was after the last meeting i did this https://discourse.lubuntu.me/t/sambashare-fixes/1980/3 [21:52] Speaking of the Discourse account deletion, there's a lovely rule at HN and we might want to consider borrowing it. "Please respond to the strongest plausible interpretation of what someone says, not a weaker one that's easier to criticize. Assume good faith." I love that rule - it's so elegant but spot-on. [21:52] which is a proposed solution for currently installed systems for the sambashare group issue [21:53] if anyone wants to play with testing that, it might be good [21:53] it would be good for known issues and such [21:54] I don't use samba so can't test it sorry (use NFS) [21:54] guiverc: samba's not required [21:55] it's essentially just testing if GID/UID stuff behaves correctly [21:55] i think that's all i got [21:55] okay then.. yes I can.. [21:55] Thanks wxl [21:55] It relates to this task https://phab.lubuntu.me/T181 [21:55] -lugito:#lubuntu-devel- [Medium, Open] GID/UID mismatch for users.: https://phab.lubuntu.me/T181 [21:56] Thanks for everything wxl ! [21:56] -lugito:#lubuntu-devel- [T181: GID/UID mismatch for users.] wxl (Walter Lapchynski) commented on the task: https://phab.lubuntu.me/T181#3980 [21:57] thank you all [21:57] keep up the good work [21:57] see you next year [21:57] Happy New Year everyone! [21:57] ack kc2bez, yeah recall the bug.. [21:57] Same and same. Stay safe on this holiday night. [21:57] Happy New (this 2021) Year folks [22:01] [telegram] Same!!!! [22:27] [telegram] same++