2xsaiko

2xsaiko , 4 months ago

Check if one of your control keys got stuck by pressing them. (might also be one of the other modifiers that does this, not sure right now)

2xsaiko , 5 months ago

The majority of the issues stemmed from the fact that the relay software that I was using, relayd, doesn’t support ipv6. All the tests that I was conducting were defaulting to ipv6, so it was appearing like the bridge was failing unpredictably. Since that realization was made, and countermeasures were enacted, the problem was solved.

I hope this means you changed or fixed the software and not that you disabled IPv6.

2xsaiko , 6 months ago

I’m pretty sure it’s part of State under [MainWindow] in konsolerc.

2xsaiko , 6 months ago

Not for me. I don’t have a fresh install here right now, but if I move konsolerc and start Konsole, it comes up with the toolbars along with other default settings, if I move it back, the toolbars are gone again.

Here’s my konsolerc (trimmed out some settings):

<span style="color:#323232;">[General]
</span><span style="color:#323232;">ConfigVersion=1
</span><span style="color:#323232;">
</span><span style="color:#323232;">[KonsoleWindow]
</span><span style="color:#323232;">RememberWindowSize=false
</span><span style="color:#323232;">ShowMenuBarByDefault=false
</span><span style="color:#323232;">ShowWindowTitleOnTitleBar=true
</span><span style="color:#323232;">
</span><span style="color:#323232;">[MainWindow]
</span><span style="color:#323232;">MenuBar=Disabled
</span><span style="color:#323232;">State=AAAA/wAAAAD9AAAAAQAAAAAAAAAAAAAAAPwCAAAAAvsAAAAcAFMAUwBIAE0AYQBuAGEAZwBlAHIARABvAGMAawAAAAAA/////wAAAQABAAAD+wAAACIAUQB1AGkAYwBrAEMAbwBtAG0AYQBuAGQAcwBEAG8AYwBrAAAAAAD/////AAABbgEAAAMAAAQ+AAAC1AAAAAQAAAAEAAAACAAAAAj8AAAAAQAAAAIAAAACAAAAFgBtAGEAaQBuAFQAbwBvAGwAQgBhAHIAAAAAAP////8AAAAAAAAAAAAAABwAcwBlAHMAcwBpAG8AbgBUAG8AbwBsAGIAYQByAAAAAAD/////AAAAAAAAAAA=
</span><span style="color:#323232;">StatusBar=Disabled
</span><span style="color:#323232;">ToolBarsMovable=Disabled
</span>

2xsaiko , 6 months ago

Nice!

2xsaiko , 10 months ago

I’d love to see Sourcehut myself tbh. But yeah, Gitlab is so annoying to navigate plus the need to have a fork of a repo on their server just to submit a single change is so annoying and leads to thousands of duplicate inactive repos which clog up the search results.

2xsaiko , 10 months ago

It’s a set of components (projects “hub.sr.ht”, wiki “man.sr.ht”, git repos “git.sr.ht”, mercurial repos “hg.sr.ht”, build service “builds.sr.ht”, bug trackers “todo.sr.ht”, mailing lists “lists.sr.ht”, I think that’s the main ones at least) which can be installed separately as needed (though at least the wiki is powered by version control so I think it needs at least one of the repo services). Everything created in these components is also separate except for projects which tie together multiple repos, lists, issue trackers and so on (for example, see sr.ht/~sircmpwn/sourcehut/ which is the main sourcehut project), as opposed to a strict “1 issue tracker per git repo” as with gitlab and a lot of the other “all in one” services.

It also emphasizes the git send-email workflow as opposed to the (in my opinion, supremely convoluted and annoying) PR workflow, which means you can just clone the repo, make your changes locally, and send patches. (Though you can still fork, push and then submit patches from the web interface if you want to, to get something similar to PRs.)

So KDE at the minimum could just have hub + git + lists (for patches), and keep Bugzilla as the single bug tracker, for example.

The builds/CI service is also supposedly excellent, but I have to say I haven’t used it yet and KDE is already using Jenkins anyway. Though of course, it does integrate with the other parts, CI for each commit and incoming patch set which is still useful to have. I think KDE is currently using GitLab CI/CD also.

I think that’s the main big parts, there’s more info about its features on the main website: sourcehut.org.

2xsaiko , 10 months ago

Personally I think it’s so much better than PRs (not that I don’t think it can’t be improved), but to each their own I suppose. I’d also be happy if GitLab had an HTTP endpoint you could submit a single patch or an archive of patches to, or something like that.

(Apparently it does support submitting patch files directly. Via email, but not in the git send-email format. Weird. Will have to try it at some point.)

2xsaiko , 10 months ago

I’ll have to look into that. Thanks!

2xsaiko , 10 months ago

many services unfortunately go the route of trying to make an “everything app” which often leads to bloat

I wouldn’t necessarily say that, it does work well for a lot of projects when used as an all in one package to have all development on, especially when it’s a public instance for many different projects such as GitHub. There’s just a lot of unnecessary parts and duplicated parts they have when specifically hosted for a single project, especially if there’s other infrastructure already in place. It feels kinda like running an Active Directory domain for one user and one PC (which I’m ironically considering doing, except that I have three computers).

I will say that, compared to the usual git services (Gitlab, Github, Gitea, etc.) it is severely lacking polish.

I do agree. One thing I can think of is that it would be very nice to have a link back to the project from a linked repo. Currently something that’s sorely missing imo. But they do say it’s alpha quality though ;)

I personally despise bugzilla. It’s one of my least favorite parts about contributing to KDE. I personally find it very unintuitive, and messy. The UX of the service, on the whole, is not a pleasure.

I get what you mean. I don’t mind it since I understand how it works, but for example I’m always apprehensive about clicking the submit button since I think maybe I accidentally edited some field I didn’t want to edit. There’s also some strange restrictions such having to upload attached files one by one and having to make a new comment for each of them. It’s certainly got its flaws, but the nice thing about it is that it’s a central bug database, with a lot more detailed categorization (bug status, dependencies, platforms, affected versions, product component, etc.) than what GitLab provides, which is pretty much just tags for all of those afaik, which is very valuable for a huge project like KDE. I’m not sure whether any FOSS alternatives that provide all that exist honestly.

2xsaiko , 9 months ago

I’m honestly not sure that a central database for bugs is the best of ideas. The issues for a project should, ideally, be tied to, and integrated with that specific project.

It’s very very useful when looking for bugs to at the very least have a central search, I’ve encountered issues before which are filed against a completely different app than the one I’m encountering it in (usually because the issue is actually in a library that both use), which I would have missed otherwise. Having a single database also allows then moving bugs between projects in cases such as that without having to recreate it and linking the old one to the new one.

Also in case you haven’t seen it yet, here are KDE’s official reasons for sticking to Bugzilla: community.kde.org/…/Why_not_GitLab_Issues