Download and install qprompt-v1.1.6-51788eb-arm64-Linux.deb. That gives dependency issues.
The following packages have unmet dependencies:
qprompt:arm64 : Depends: libqt5svg5:arm64 (>= 5.15.2) but it is not installable
Depends: libqt5x11extras5:arm64 (>= 5.15.2) but it is not installable
Depends: qml-module-qt-labs-platform:arm64 (>= 5.15.2) but it is not installable
Depends: qml-module-qtqml:arm64 (>= 5.15.2) but it is not installable
Depends: qml-module-qtqml-models2:arm64 (>= 5.15.2) but it is not installable
Depends: qml-module-qtqml-statemachine:arm64 (>= 5.15.2) but it is not installable
Depends: qml-module-qtquick-controls:arm64 (>= 5.15.2) but it is not installable
Depends: qml-module-qtquick-controls2:arm64 (>= 5.15.2) but it is not installable
Depends: qml-module-qtquick-dialogs:arm64 (>= 5.15.2) but it is not installable
Depends: qml-module-qtquick-shapes:arm64 (>= 5.15.2) but it is not installable
Depends: qml-module-org-kde-kirigami2:arm64 (>= 5.78.0) but it is not installable
Depends: libkf5i18n5:arm64 (>= 5.78.0) but it is not installable
Depends: libkf5coreaddons5:arm64 (>= 5.78.0) but it is not installable
Depends: libkf5crash5:arm64 (>= 5.78.0) but it is not installable
Install by Flatpak.
flatpak run com.cuperino.qprompt
error: app/com.cuperino.qprompt/arm/master not installed
Install by Snap.
sudo snap install qprompt
error: snap āqpromptā is not available on stable for this architecture (armhf) but exists on other architectures (amd64, arm64).
Has anyone been able to get this to work on the latest Raspberry Pi OS (Bullseye)?
Raspberry Pi OS Bullseye is too old to work with QPrompt. You need Bookworm for QPrompt 1.1.6 to install from the Deb package. For QPrompt 1.1.6 and for 1.2, use of the Deb package is recommended over other installation methods. That may change in the future.
QPrompt 2.0 will not be compatible with Bookworm either. For that you will need either the version that follows Bookworm, said to be released later in 2025 or Ubuntu 24.10 or later for the Raspberry Pi, which does not perform as well as the older versions of QPrompt with Raspberry Pi OS.
I downloaded your qprompt-v1.1.6-51788eb-amd64-Linux.deb and installed it in a new Bookworm build. This is the result:
sudo apt install ./qprompt-v1.1.6-51788eb-amd64-Linux.deb
Reading package listsā¦ Done
Building dependency treeā¦ Done
Reading state informationā¦ Done
Note, selecting āqprompt:amd64ā instead of ā./qprompt-v1.1.6-51788eb-amd64-Linux.debā
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:
The following packages have unmet dependencies:
qprompt:amd64 : Depends: libqt5svg5:amd64 (>= 5.15.2) but it is not installable
Depends: libqt5x11extras5:amd64 (>= 5.15.2) but it is not installable
Depends: qml-module-qt-labs-platform:amd64 (>= 5.15.2) but it is not installable
Depends: qml-module-qtqml:amd64 (>= 5.15.2) but it is not installable
Depends: qml-module-qtqml-models2:amd64 (>= 5.15.2) but it is not installable
Depends: qml-module-qtqml-statemachine:amd64 (>= 5.15.2) but it is not installable
Depends: qml-module-qtquick-controls:amd64 (>= 5.15.2) but it is not installable
Depends: qml-module-qtquick-controls2:amd64 (>= 5.15.2) but it is not installable
Depends: qml-module-qtquick-dialogs:amd64 (>= 5.15.2) but it is not installable
Depends: qml-module-qtquick-shapes:amd64 (>= 5.15.2) but it is not installable
Depends: qml-module-org-kde-kirigami2:amd64 (>= 5.78.0) but it is not installable
Depends: libkf5i18n5:amd64 (>= 5.78.0) but it is not installable
Depends: libkf5coreaddons5:amd64 (>= 5.78.0) but it is not installable
Depends: libkf5crash5:amd64 (>= 5.78.0) but it is not installable
E: Unable to correct problems, you have held broken packages.
Never mind. It turns out that I got confused at your web page for downloads and chose the wrong one. arm64 was right next to amd64. Thought they were the same. Got qprompt-v1.1.6-51788eb-arm64-Linux.deb from the other post. Installing this one worked.
You got very close. Instead of using the amd64 deb package you must use the arm64 one instead. This naming difference refers to the CPU architectures. The Raspberry Pi uses a mobile CPU of the ARM family, while regular PCs use descendants of the Intel 8086 CPU, which covers the AMD 64 architecture introduced in the 2000s. For the Raspberry Pi you need the ARM 64 build for it to install and be able to run.
Yep, knew that. Should have paid closer attention. I will say though that it would have been easier to figure out if there was a download page for just the most recent, with each one clearly marked as to its target platform.
For instance, āif you have Raspberry Pi 4, you need Bookworm version OS and this deb fileā. That is so much easier than trial and error with unsupported and mismatched versions. The expectation is that flatpak and snap and appimage should always work, but that didnāt either.
There is too much text on the page without clear instructions.
I agree. We currently rely on SourceForge and a bit of JavaScript to auto detect whether a system is Linux, Windows or MacOS, and offer a download for each system, but that doesnāt cover the ARM platforms. The reason itās done that way is because I tend to forget to update the website, so having something automated that can take care if linking users to the correct version is one of the best ways to go about itā¦
Iāve been wanting to re-do that part of the site for a while, but development and tech support takes priority, so thatās a bit lacking. Iāve filed a ticket to not forget about it. This goes to my queue of things that need to be done after the next release is out or ready. Contributions are welcome.
I can tell you that the fundamental issue of most importance is not to auto detect the target system. Rather, the visitor to the site should be able to select which ever is desired.
Doing it this way reduces your overhead. All you have to do is upload the latest version of each type and leave it at that. There are just too many possible combinations of processors and OS versions out there.
A simple statement that your software has been tested on a given platform and OS combination should suffice. Anything else is simply not supported. You need not over-think the project.
I would be willing to help if I can. What do you need?
I know you mean well, but this would not reduce overhead. All links (in the case of the user navigating) and redirects (in the case of automatic detection) would have to be updated with every build revision. With the current approach, no links need to be manually updated.
All OS and processor combinations that I provide are officially supported and tested to fully work on a system with a single screen, and at least one build per OS is tested in a setup with multiple screens.
The Raspberry Pi is a bit of an edge case because although it uses an arm64 CPU not all arm64 builds will deliver the same performance on it; thatās because of differences between how that OS is made and other Linux distributions supporting ARM.
In an earlier project of mine called Imaginary Teleprompter, I would list all OSs and people would have to choose the architecture after. However I would sometimes forget to update some OSs and not others, as a result of not everything getting released in the same day. htttps://imaginary.tech/teleprompter
Users would also not know about CPU differences and sometimes ask for help. Hence, some amount of automatic guidance is needed to direct a person to the correct download. In QPromptās website, only OS the is detected and an amr64 build is always provided, which is the first point of confusion.
From my perspective, what should be done is to:
Have automatic detection consider not only the OS, but the CPU architecture as well.
Provide an organized downloads section on the page, similar to how Imaginary Teleprompter did it.
However, I havenāt done either of those things because I donāt want to spend time maintaining links and redirects. What I need is a way for the website to update its own links and redirects when new releases are made.
I think I understand your position. Evidently, when you compile a new build, you have a built-in mechanism that allows an automatic upload and user link creation.
I also agree that if the auto detect is only for OS, then missing the CPU is a serious problem.
But rather than worrying about all that, just redesign the page layout to be more intuitive for visitors. No need to reinvent the wheel, but there is always room for improvement.
By the way, you are not responsible for performance since the various platforms have various amounts of power and memory. That is always the usersā responsibility. You would only need to specify what each build was test upon and leave it at that.
Something like that. Itās simpler even. When I make a release in GitHub, the builds are copied automatically to SourceForge.com. Then I go to SourceForge and tell it which file it should provide Windows, MacOS, Linux, Android, and other OS users. SourceForge then takes care of the OS detection.
On our website we also do OS detection, but only to show the corresponding OS icon and to show/hide links to the Flatpak and Snap builds on Linux. I should be able to expand this detection to provide a link to the corresponding Deb file in the case of arm64 Linux systems.
Thanks. Back during my childhood software used to specify PC spec requirements. That feel out of favor as more PCs became capable of running everything. Many users will convert old, cheap, and embeddedable hardware into dedicated teleprompters. I find providing minimum requirements useful, as it can help save peopleās time and keep computers off the landfill.
Iāve set the Raspberry Pi 4 as my baseline when ti comes to performance, because itās the oldest Raspberry Pi board that will run QPrompt comfortably in a 720 HD screen. Older models can also run it, but the experience isnāt great.
Yep, the Raspberry Pi 3B is really borderline for Zoom performance, for instance. But everything should run fine on 4. (The idea of a 720 HD screen is a little hard to figure for me. My desktop screen is usually 1280x800, so you do the calculation. Anything higher than that creates items too tiny to read, and I use a 40 inch display.)
That should work. Itās around 1280Ć720, which is the smallest HD standard, and 1366x768, the most common display resolution around those resolutions.
I agree. But what about just the downloads section?
Yes, that was exactly to what I was referring. The other site did not have a listing; just a download button. I assume it is the system you described as trying to determine oneās OS. (Hardly useful, since one might download on one computer and install on another.)
It is all very confusing because you have too many places to download files. That is at least three, if not four, sites now. Youāve got to keep it simple.
There are only two sites that host most downloads. We need redundancy in case one of them goes down. Lastly thereās only one site that presents the project and guides you towards the downloads: https://qprompt.app
We have to make the software available where people will be at. Thatās why I use SourceForge as it provides exposure. If people use Flathub on Linux, it must appear on Flathub.com. Then I present that option to Linux users visiting qprompt.app. The same goes for Snaps. Some users only have access to one or the other, so both links must be provided.
BTW, your viewpoint of redundancy is not the correct way to reduce down time. It is to have more than one server mirroring the same web site.
There are two ways that things can happen with a web server. The first is a failure of the hardware itself. The second is a failure to have backup power in case of grid failure. The first one is stopped by having more than one server; in other words, a mirror. The second is stopped by having a trusted service provider who had proper backup in place. These issues have been solved decades ago by server experts. We do not need to worry about them but just use trusted methodologies.
