This is essentially just about gitlab privileges. It seems like you’re making a big deal about nothing. Calling a particular category of privilege holders a “team” seems excessive, possibly even deluded. Likewise, describing the collection of different gitlab privilege roles as an “organisational structure” seems silly.
I recommend trying to use KDE Connect (or scp, rsync … another network based way) to send the screenshot from the phone to your other computer instead.
MTP/other file transfer protocols do not (yet?) work with mobile Linux, so this failure is to be expected. It only shows up for connection, because if your device ran Android, it would be an option — AFAIK, Plasma acts this way because of the USB ID of the device.
Also, regarding your main issue: While you can report this to Mozilla, please be aware that Firefox is being “patched” to better work on mobile by gitlab.com/postmarketOS/mobile-config-firefox. I suggest you to install the latest, not yet in postmarketOS 23.12 mobile-config-firefox package from edge first by running:
Thank you. I’ll use that information about the USB ID for my report to KDE. However, could you elaborate somewhat? That is, would it be correct to ask for Plasma to not merely utilize the USB ID to identify whether a device is accessible, but test whether it can be accessed by MTP first, before presenting that option to the user? Regardless, per what you’ve said, I’ve consolidated my previously disparate reports under bugs.kde.org/show_bug.cgi?id=486931.
Additionally, I’ll definitely mention on Bugzilla that incorporating some of the patches in that package would be a feasible implementation method. Relevantly, I’d like to use that package, but because I’m not using Edge, would adding that repository do any harm (for instance, would it be added with higher priority by default than existent repositories)?
I don’t think reporting the USB ID thing to Plasma is useful and will go far - for 99% of users (that use some kind of Android/AOSP) the modus operandi is fine and helpful. With many Android devices and OSes requiring you to do something on the device after plugging it in, testing does not seem to be feasible to me.
There’s no need to add the edge repo, as the latest release of mobile-config-firefox should be in v23.12 by now (it’s been updated there since my last post). The command I posted does not add the repo, but only uses it for the one package without adding the repo permanently.
I’d like it opened for new users to be able to participate there without a Lemmy account, but there’s a cost-benefit ratio to everything, and the additional moderation burden and potential fragmentation of the small community appears to outweigh the benefits. Additionally, a lack of choice paralysis can be quite a significant advantage.
So its essentially like this for two years now… all the apps hang in alpine testing and none make it to postmarketOS. Thats sad.
I filed a bunch of issues today and started testing with phoc and phosh on my pc to help speed this up a little but without a real process its slow and draining.
Its a great project but the wiki needs to be more detailed and honest. I requested an account to help with that.
The difference should be mostly the apps that have not made it beyond testing, yet.
Please note that you can also try installing testing apps on stable by apk add PKGNAME --repository=http://dl-cdn.alpinelinux.org/alpine/edge/testing, or, maybe as more safe way of doing this, use distrobox, install alpine:latest in it, and changing /etc/apk/repositories/ to make it edge instead of 3.19.
You can also try to build some software that’s not packaged by coming up with your own APKBUILDs, I did so a while ago on framagit.org/linmobapps/apkbuilds, maybe the notes I left there can be helpful to you.
Regarding Wikis: They always get stale, so clarifications and additions are surely welcome!
Thanks for the suggestions. Thats exactly the route I‘m taking. I made an account on alpines gitlab and also did a gnome app tutorial to make some rudimentary things for the phone.
While we‘re at it: do you know if there is any way to get alpine apk visible in gnome software? Its driving me nuts that flatpak is visible and apk which is a lot of stuff can only be installed through cli.
While we‘re at it: do you know if there is any way to get alpine apk visible in gnome software? Its driving me nuts that flatpak is visible and apk which is a lot of stuff can only be installed through cli.
Thanks a lot for mentioning this. In other words, this does work on edge. But it does not work for me on stable… the question being if its because stable or because of a bug…
It did work on edge at the time of that post (March 2023), and IIRC it may have worked in stable 23.06 (the release right after that post) - I don’t have a device still running that to confirm. It since broke again, and it’s currently broken in stable and testing (it’s definitely broken for me in edge in both Plasma Mobile (KDE Discover) and Phosh/GNOME Mobile (GNOME Software). So don’t go to edge because of this, especially not right now.
Wow! Now I‘m somehow more informed and confused at the same time which is on par for my experience with linux phones so far :D
Thank you very much for elaborating. This is really important info for me.
So, it might be my device on 23.12 stable that is having issues but it might also be 23.12 itself that is causing this. Please correct me if thats wrong.
As flatpak apps show (correct?) your situation is not different from what I would expect. I installed 23.12 on one of my devices and see a similar behavior. Generally, assuming you did start with a Phosh image or used pmbootstrap and chose phosh as UI (and did not, say, start out with Plasma Mobile and then switched over to Phosh, which can cause weirdness), I think we can safely say that this not just an issue on your end. This is very likely a general issue on 23.12 and edge currently.
Why isn’t it fixed already? It sure seems to be difficult, and most “long termers” (extrapolating from my own behavior) likely have given up on using front-ends like GNOME Software or KDE Discover and have become fluent enough with apk and flatpak on the terminal and thus don’t contribute to a solution.
Generally yes, but I am just a dumb tech blogger, so what do I know 😀 . I checked the issue tracker, and this issue seems related - I also see that crash, and it might extend beyond upgrades and thus be the source of what you are seeing. If you also see that crash of that service, maybe just upvote the existing issue first or if you can chime in/help out, do that before opening a potential duplicate :-)
Please don’t ever suggest this. That approach is prone to breakage and shouldn’t be used. You’re installing an app built against edge on a stable release which has different versions of libraries and might even be missing dependencies entirely. If you want something from testing, just switch to edge and enable the entire testing repo.
It is not a product as so much a project. I would recommend reading up on the goals and mission of postmarketos and instead support rather than point out shortcomings.
If you are a developer I’m sure the team would be happy to give write access but considering your novice experience your opinion is likely less important than actually improving things.
Testing out the x86 builds using qemu is typically the first step to understanding and if you want to make changes, opening a PR or demonstrating your value to the project would make it more worthwhile for them.
I’m am a follower of this project myself and have nothing to do with postmarketos or the wiki.
I would recommend reading up on the goals and mission of postmarketos and instead support rather than point out shortcomings.
Thats what I‘m doing. I‘m opening issues all over the place, using my laptop to debug stuff and will likely make PRs soon but as I said, it takes a long time to understand stuff because no process. I‘d suggest you take constructive criticism as a positive thing instead of undermining my effort.
There is a general misunderstanding between folks that posts like mine are anything but a way to both give feedback, point to onboarding issues and asking for direction. Pointing out that someone „demonstrate their value“ is one reason our world is so fucked. I dont need to demonstrate my value. I fix things and I help with things. If people dont see value in that, they can f off.
I know you likely mean good so I will just turn around now and read up on the qemu stuff and try to provide more help and fixes.
This is … a bit false. Flatpaks do show in GNOME Software on other distributions, and while not every app on Flathub supports aarch64, many do. I somehow managed to not have a with postmarketOS stable and Phosh here right now (I misplaced my PinePhone that runs that combination), so I can’t say if it would work for me. It definitely works on other distributions, though; but there’s always the added difficulty of imperfect app metadata making it a game of luck to recognise a mobile friendly app as such.
That said, you can always install packages from the terminal, flatpak (flatpak install …) or apk (apk add …) or otherwise. To find apps to look at, maybe LinuxPhoneApps.org can be useful.
My statement is true , that flatpak is arch agnostic but primarily supports x86.
I never said it didn’t or wouldn’t work; if you’re not seeing your apps it’s not because they don’t exist, they aren’t built for aarch64 and target x86
I was referring to “Flatpak […] is currently only working as expected on x86_64” is … if not false, then far too easy to misunderstand. Flatpak works just as well on aarch64 for (at least) hundreds of apps. The software that’s not available on, e.g., flathub for aarch64 (but is available for x86_64) in most cases is not available (in compiled form) for aarch64 at all — because it is proprietary with vendors not caring about aarch64, or … just is electron-based ;-}.
It’s not Flatpak, it’s the entire aarch64 software ecosystem that’s lacking here. Stating “Linux on aarch64 has less available software than x86_64, which is especially so for proprietary software” would have been a far better statement.
Without any further configuration, might as well as add that to your edited paraphrased quote.
Please correct me, but AFAIK, necessary configuration of flatpak (e.g., configuring remotes) depends more on the distribution than the architecture (as long as the architecture is supported at all, that is - so x86_64 or aarch64 AFAIK).
Your lengthy explanation of flatpak doesn’t seem to be postmarketos related.
Sure? gitlab.com/postmarketOS/pmaports/-/…/4820And does it hurt to mention differences in software support between x86_64 and aarch64? I would see your point if I had talked at length about Snaps. ;-)
got it, because the project supports flatpak, you feel like you need to explain it. yes, if the op configures flatpak to use a repo that has aarch software then flatpak works as expected. glad that could be cleared up.
This sounds more like a network problem, maybe something on your end or that one of the repos was temporarily unreachable (usually it’s the postmarketOS repo for me in such situations). I recommend running sudo apk update in situations like this and reading through the output. Depending on which repo is unreachable (= if it’s one of the alpine repos) it may be a better idea to delay upgrading.
It definitely has nothing to do with the device being dropped from main to community — both categories mean that the device is served by stable.
Well the great thing about PinePhone is that if you break it you can always reformat and start fresh. If it were my phone I would trust the command it tells me to run, assuming you have a backup I guess.
I love Open Collective and prefer it over any alternative. I will still try to support the individuals who use Liberapay but really like the transparancy of OC for supporting projects.
I for one ditched Reddit long ago and am never going back. Not for any project. If they want to have a sub reddit then fine but they better have FOSS options ike Lemmy as well.
The fact that PostmarketOS used anything other than SystemD was a selling point for me. That beign said it seems like it will be optional so at that point I see little reason to be angry.
postmarketos
Hot
This magazine is from a federated server and may be incomplete. Browse more on the original instance.