[00:42] -ubottu:#ubuntu-news- ::omg!ubuntu:: Happy 19th Birthday, Ubuntu! @ https://www.omgubuntu.co.uk/2023/10/happy-19th-birthday-ubuntu
[02:25] <guiverc> Bashing-om, i created a few summaries & left a comment (hidden) on one (i didn't mention sponsors) ; any reaction? bad idea (hidden comments) etc?
[02:26] <Bashing-om> guiverc: Been a while since I updated 810 / did not notice at the time ... re-looking :D
[02:27] <guiverc> as it's within a <!--  --> it doesn't show to normal readers
[02:36] <Bashing-om> guiverc: Ack - lemme log in and see once more :D
[02:37] <guiverc> there is no hurry, it's not important.. just a thought & left that way as we can see if helpful or just annoying
[02:48] <Bashing-om> guiverc: See it :D Yeah we need a means to make comments, That is one way. I am trying to respond// seems my left mouse button has died on me :(
[02:50] <guiverc> :( @ pita mouse..
[02:56] <Bashing-om> guiverc: Just going to have to venture out in puplic - Walmart visit I guess is a must. // looks as if the Korea Busan article has been pulled - continuing to investigate // Then will follow your comment with my own.
[02:57] <guiverc> ack & thanks.
[02:58] <guiverc> dropping articles happens on occasion; on discourse that will get noticed where it never was before hidden away on gdoc
[03:04] <guiverc> Bashing-om, i don't see any reason to pull busan release party article.. i have noted that discourse can 'hide' awhile the summary for internal links... but they eventually return (I think it's generating that, maybe within our browser & reducing load on actual server & it can get behind on larger files)
[03:09] <Bashing-om> guiverc: Turned out was a invalid post number - corrected :)
[03:10] <guiverc> :)
[03:12] <Bashing-om> guiverc: I do believe Discourse as our development platform will work out nicely :D
[03:14] <guiverc> :)   i liked the comment capability on gdoc (on occasion used to for comments to myself. as i do bits here & there) but I probably overused it (with almost every thought)
[03:21] <Bashing-om> guiverc: Uh HUh - but we will develop a communications pattern for Discourse :)
[03:21] <guiverc> we will..
[03:22] -ubottu:#ubuntu-news- ::planet:: Podcast Ubuntu Portugal: E269 Bué De Makambas a Mbote @ https://podcastubuntuportugal.org/e269/
[03:22] -ubottu:#ubuntu-news- ::planet:: Ubuntu Blog: Ceph storage for Kubernetes @ https://ubuntu.com//blog/storage-for-kubernetes
[03:22] -ubottu:#ubuntu-news- ::planet:: The Fridge: Call for nominations for the Local Communities Council @ https://fridge.ubuntu.com/2023/10/19/call-for-nominations-for-the-local-communities-council-2/
[03:23] <Bashing-om> guiverc: Is is a possibility both of us can access the Discouse page and see the other's edits real time ?
[03:25] <guiverc> no idea how that would/will work, we'll have to find out in due course  (part of why I'm writing summaries earlier..)  I just added a COMMENT: on my comment; so I've something easy (i hope) I can search for
[03:25] <guiverc> i have 810 open currently; wanna try and open it?
[03:26] <guiverc> after banner I've added a "<!-- COMMENT  -->" at top; but I'm expecting you won't see that as I've not clicked SAVE EDIT & thus expect it's local only
[03:26] <Bashing-om> guiverc: 810 I too presently have open --- lemme look and see if your commented comment shows :)
[03:32] <guiverc> how long have you had page open? Bashing-om , the last summary added by me was LXD 5.19 release
[03:35] <Bashing-om> guiverc: I do see your "COMMENT" in history - that is not presently displayed . Also in "raw" the comment I fillowed yours does not appear. Lemme log off and nback on and see If then I see the changes. // Has not been real long since I last logged onto 810.
[03:38] <guiverc> the formatting discourse wants needs to be ~accurate; eg. the "->>" on skeleton that should have been "-->" resulted in lots of your adds being treated as comment only..
[03:38] <guiverc> I'd not expect you need to logout/login; may need to re-enter page I'd hope most that would be required.
[03:43] <Bashing-om> guiverc: I know that you added "COMMENT" yo your comment - however saving my edit and then re-entering edit mode still does not show "Comment" ! lemme log off completely and log back in see then If I see the change.
[03:45] <guiverc> No... I think because I've NOT clicked SAVE EDIT, it's only local on my browser & that why you're not seeing it.
[03:45] <guiverc> i added "<!-- COMMENT:  -->"  (first without COLON as mentioned ^ then added ":"  ater the top header.png line..  I don't believe it'll show on your screen until saved.
[03:46] <guiverc> if you add a line near the top (after header.png) ... I don't expect it to appear on my screen either.
[03:47] <Bashing-om> guiverc: I accept that - :D
[04:00] <guiverc> yeah.. bashing-om, please click & explore the history of the page.. your last saved erased 3 summaries    (which I bet you didn't do, but consequence of me editing whilst you had page open... & your browser saving based on what was there when it opened page)
[04:04] <Bashing-om> guiverc: Ouch ! So much for both working the issue at the same time !
[04:05] <guiverc> i suspect that would occur; part of why I'm doing it now... the text can be read via that history, copy/pasted & re-added, but yeah it's a pain; esp. given detail may not be noticed & thus lost!
[04:06] <guiverc> s/suspect/suspected..
[04:07] <Bashing-om> guiverc: I am going to get out of 810 amd allow you to catch back up with what was erased !~
[04:08] <guiverc> you can complete whatever you need to..
[04:08] <guiverc> i wrote summaries on mousepad; the just opened page (for edit), copy/pasted them into location & saved.. so i was in & out pretty quick.. adding the links takes far longer
[04:14] <Bashing-om> guiverc: I am caught up until my tomorrow updates.
[06:49] -ubottu:#ubuntu-news- ::security:: Episode 211 @ https://ubuntusecuritypodcast.org/episode-211/
[07:43] -ubottu:#ubuntu-news- ::fridge:: Call for nominations for the Local Communities Council @ https://fridge.ubuntu.com/2023/10/19/call-for-nominations-for-the-local-communities-council-2/
[14:39] -ubottu:#ubuntu-news- ::omg!ubuntu:: What’s Your Ubuntu 24.04 Codename Prediction? @ https://www.omgubuntu.co.uk/2023/10/guess-the-ubuntu-24-04-codename


[05:14] <JackFrost> ochosi: I'm not sure what to do with that statement.
[11:32] <knome> pleia2, jphilips, we should move to git with the website stuff, but i need to learn about submodules first and see if they work with lp
[11:33] <jphilips> knome: that would be great. wish we could use github as well, as that would lower the barrier of submitting patches from the community
[11:34] <jphilips> knome: when you get a chance - https://bugs.launchpad.net/xubuntu-website/+bug/1865627
[11:34] <knome> i guess, though moving to a corporate-owned thing is not what many people in the open source world want
[11:35] <knome> (not that LP isn't corporate owned, but it's owned by a company that directly supports this community)
[11:35] <jphilips> well gitlab then
[11:35] <jphilips> like gnome
[11:36] <knome> but that would still mean a huge migration
[11:36] <bluesabre> Yes. Even for smaller projects like Mugshot, moving to GitHub was a surprisingly tedious project
[11:39] <bluesabre> But yeah, after moving several bits to git in LP, I found the git support to be overall lacking, and several of the existing LP tools still don't know about git :(
[11:41] <bluesabre> I'm not opposed to moving, but I don't want to do all the work involved :D
[11:44] <knome> phew
[11:45] <knome> i went and wrote a novel in a google docs comment
[11:45] <knome> sorry
[11:45] <bluesabre> :D
[11:50] <knome> jphilips, went ahead and added another comment about gutenberg (which is a lot like what i said here already)
[12:31] <jphilips> knome: :D
[13:36] <jphilips> would be good to set 'sort folders before files' in the gtk3 file dialogs, so it is consistent with default behaviour of thunar
[14:09] <jphilips> ochosi: https://imgur.com/I1Fb1C2.png
[14:10] <jphilips> we dont have the right icons for 32 and above - https://bugs.launchpad.net/ubuntu/+source/xubuntu-artwork/+bug/1865562
[20:57] <ochosi> jphilips: interesting, the 48px user-desktop looks fine here
[20:58] <jphilips> are you using the default icon theme?
[20:58] <jphilips> i was on the xubuntu 20.04 daily
[20:58] <ochosi> well i am ofc
[20:58] <ochosi> oh
[20:58] <ochosi> i see, my thumbnail caches were old :/
[20:59] <ochosi> seems with the transition to the yellow folders we lost the desktop icons
[20:59] <ochosi> at least that means they should still exist in git history
[21:03] <jphilips> doubt you are running the iso :D
[21:04] <ochosi> that's unnecessary, i build the icons locally before i push them to git
[21:04] <ochosi> so i'm by definition on the latest version
[22:50] <JackFrost> Remember that feature freeze has passed, other freezes are coming up.
[23:17] <jphilips> think we should likely have hellotux have an 18.04 or 20.04 flash drive - https://www.hellotux.com/xubuntu


[08:43] <sakrecoer> zequence: excellent! i havn't been able to test the new release for logisitc reasons, and os i was a bit worried that scribus bug would have slipped in :)
[10:52] <sakrecoer> do you guys also have problems with gnome keyagent for ssh? i'm going crazy over it. over at #gnome, they find my problem intersting but have no sollution...
[10:53] <sakrecoer> i've deleted all my keys from the system, yet gnomekeyring finds it somewhere, stating it is in ~./ssh (where it is not) seahorse see no SSH keys, but my gpg keys are there... yet i can connect to my servers using the deleted keys (yes i have rebooted severeal times)
[10:54] <sakrecoer> sudo find / -iname '*rsa*' gives no return...
[10:56] <sakrecoer> btw, seahorse is not showing up in our menu...
[10:56] <sakrecoer> after install..
[11:08] <sakrecoer> ok... so gnome keyring is storing a copy of the secret ssh key in ~/.gnupg/private-keys-v1.d/
[11:09] <sakrecoer> but it seems to get coded as to claim that it is located in ~/.ssh/rsa_id
[12:30] <sakrecoer> ok... so it is gpg-agent that is sotring the key. seems we have 3 different agents: ssh-agent, gpg-agent, and  gnome-keyring-daemon
[17:37] <zequence> sakrecoer: I never bothered getting that to work. You might want to ask in #xubuntu how to get ssh paswords stored
[17:40] <sakrecoer> i asked all over freenode today, but i got an answer. its gpg-agent and it is stored in both ~/.gnupg/sshcontrol and in ~/.gnupg/private-keys-v1.d/<keygrip>.key
[17:41] <sakrecoer> i'm sure there is a good reason to have 3 different ssh agents... its just very confusing. When you add a key sith ssh-add, it gets copied by gpg-agent and encrypted behind a 2nd password...
[17:43] <sakrecoer> anyways, now that i understand howit works, i'm happy enough to let it go... :D
[21:43] <OvenWerks> sakrecoer: I don't use the keyring thing. I found it was asking me for a password in too many places it didn't need to.


[04:45] <yurtesen> I was told anybody can make debdiffs to help Ubuntu :)
[04:56] <yurtesen> but it seems quite hard to find sponsors :(
[04:57] <Unit193> yurtesen: Did you end up asking -server as requested?  Getting your bug on the sponsors dashboard also helps considerably.
[04:57] <Unit193> [10:19:48] < rbasak> yurtesen: could you try asking in #ubuntu-server please? I'm a bit tied up right now, but maybe one of my colleagues could take a look.
[04:57] <Unit193> In case you didn't see earlier.
[05:02] <yurtesen> Unit193: I asked in #ubuntu-server , #ubuntu-next and in #ubuntu-discuss (perhaps I should ask here again) . The bug-fix is just a small permissions change on a single file.
[05:02] <Unit193> -next is more of a support channel and -discuss is more of a chat channel, yeah.
[05:03] <yurtesen> Unit193: what can I say, I was getting desperate :)
[05:06] <yurtesen> Unit193: I feel something is wrong somewhere. Either I am doing something wrong, explaning my issue inadequately or this procedure is somewhat broken.
[05:07] <yurtesen> or maybe I am too impatient, but it is hard also not be with people breathing on my neck for fixes.
[05:10] <Unit193> Urgh, and http://reports.qa.ubuntu.com/reports/sponsoring/index.html isn't even loading for me...
[05:17] <yurtesen> Unit193: it woorks for me, but most of the stuff there are over 4 weeks old. The problem is that there is no feedback on the debdiff. If somebody said "we looked at it and it looks ok, but it might take 1-2 weeks to get it merged." That would be awesome. But now, after 4+ weeks patch might be rejected and waiting period starts again.
[05:21] <yurtesen> Today somebody asks me " Q: Did you hear anything? Will ubuntu incorporate a fix? " I have to answer " A: I am not sure I heard nothing yet ". It is hard to say the same thing meeting after meeting unfortunately.
[05:25] <Unit193> Sure I get the frustration, just not something I can exactly help with.
[05:25] <yurtesen> Who can help? or universe repository a lost cause?
[05:31] <yurtesen> Because I would like to give something back to Ubuntu by helping out some way.
[05:34] <yurtesen> and it is a chicken-egg problem. One needs to prove themselves to have access to pushing bugfixes directly (eg. become MOTU) but at the same time this does not seem to be possible if the packages these people are trying to support are somewhat ignored.