Untracked Bug reports
Was the last one resolved?Community meeting on IRC 17th August 2023 - #2 by pherjung
Untracked Bug reports
Was the last one resolved?Community meeting on IRC 17th August 2023 - #2 by pherjung
I need to check again, but none of the last provided list has been resolved.
Is there any chance to ever get this one tracked, PLEASE?
I think that’s correct. We’ll check the last list first (if time permits then we’ll check both). So for @thigg, let’s just use the last again for now. Thank you both!
linux/membarrier.h
header (specifically __NR_membarrier
) which was introduced in kernel headers 4.3. Gecko checks at runtime that the capabilities are available before using them. With thanks to @mal for his help with this.These are all Gecko ESR 91 related. These aren’t stuck, I’m just raising them in case there’s any need to discuss them.
ICU 70.1 (thanks for looking at this already)
GCC backported patch (special thanks to @direct85 for this)
cbindgen 0.19.0 (thanks for all the useful feedback on this as well)
Just a quick note about bug 11 - its title has been changed to [4.5.0.19] Forwarding email can insert extra \r\n in header data
as the headers are in place, but possibly just formatted wrong.
Nope, I am not interested in participating at Jolla’s “IRC community meetings” at all:
As stated in the issue thread, this issue is at least 7 years old, was reported multiple times at TJC, has been silently addressed by Jolla at least once (which alleviated it a bit, but never really resolved it), while never acknowledging it.
Jolla’s policy always was and still is to be absolutely closed up and to stay mum (contentually, for both technical as well as business aspects), plus I see no indication for this to change. If Jolla would, e.g., allow read access to their internal bug tracker, or report openly that they recently have been becoming bankrupt (or close to that) another time and how this was resolved, then I will believe that Jolla is trying to do better; until then all these efforts are more or less futile.
P.S.: In the light of Jolla’s recurring economic (close) failures, I also expect Jolla to commit themselves legally binding and publicly to release all proprietary components which comprise SailfishOS (i.e., all but Alien Dalvik aka “AAS”: Silica, Lipstick, etc.), in order to enable the community to continue development of SailfishOS, in case Jolla ultimately fails economically; until then it makes more sense for community developers to spend efforts and time on FLOSS software which runs independently of SailfishOS, because such work is implicitly sustainable.
I mostly agree; there are a lot of questions which have not been returned to although they are quite old. It would be nice to have some kind of recap of the queued questions. GPS, X10III battery consumption and echo cancellation issues come to mind first. Some/many of the issues are to be fixed by Sony (unfortunately) and as long as Jolla doesn’t update the supported firmware (which is a massive undertaking), these will not change… If that’s the case, it would be fair to just state that, instead of leaving the community with assumptions and read-between-the-lines. It’s frustrating to everyone.
The issue linked (issues with Android text input) is indeed several years old. I guess because it works on WhatsApp and some other apps, it’s good enough for the paid partners, because it’s not fixed after all this time. Fennec (Firefox) is one that hits me the most - some sites just don’t work with Jolla Browser, so I’m forced to use something else. I have to work around it on daily basis. I don’t even think about it any more, I do the same tricks with Jolla Browser too…!
I’d love to participate to the IRC meetings, but for the second company in a row there’s a mandatory meeting for me on every other Thursday at 10 o’clock, and I can’t expect either company to change their schedule. What are the odds…
Minutes: #sailfishos-meeting: Sailfish OS, open source, collaboration -- 14th Sep 2023
Minutes (text): https://irclogs.sailfishos.org/meetings/sailfishos-meeting/2023/sailfishos-meeting.2023-09-14-07.00.txt
Log: #sailfishos-meeting log
Thank you for the responses and discussion, the log was an interesting read!
About the PR: I agree with @flypig that it makes no sense to merge it before it has been tested. Thank you for all participants already in the process, things have moved a lot faster than what I expected, to be honest!
About the build: I’m getting more familiar with Platform SDK, and I’m at the point that I’m quite confident the missing packages are preventing my builds - I’ll list the missing deps later today. Thanks for @flypig, @rainemak and @mal for help, I wouldn’t have gotten this far alone!
About the docs: Thank you for the lively discussion, all the suggestions and clarifying the PageStack usage! As a developer who writes docblocks too, I understand the trouble and work of improving such documentation. (Let’s just say there are pros and cons…) One motivation to this was simply having more eyes on the documentation with some known method would help the quality and completeness of the docs - that would benefit everyone. At this point I second the dedicated forum section, since separating the documentation can be quite a large task. That way we could at least gather related information in one place, which is a great step forward already!
About Gecko: I could try to replicate the build and the GCC bug, and then see if the OBS packages are any good. I don’t mind messing around in my Platform SDK setup, since it’s there because of the GCC bug in the first place!
I’m also a bit hyped about the PinePhone discussion, and happy to hear xulrunner build was also fixed!
It’s great to see so much going on after the quiet summer! Welcome back everyone!
Thanks for the answer. I hope the forum thread helps you with investigation and it makes it easier to fix
I wrote the (incomplete for sure but well close enough) journey of running into the missing packages on the dedicated thread and that’s as far as I can go with current knowledge