flathub.flatpakrepo
On Sat, Mar 01, 2025 at 04:42:22PM -0500, gene heskett wrote:
flathub.flatpakrepoNowhere.
On 3/2/25 01:40, [email protected] wrote:
On Sat, Mar 01, 2025 at 04:42:22PM -0500, gene heskett wrote:
flathub.flatpakrepoNowhere.
And this is to indicate that flatpaks will not be accepted by debian?
Installing that is one of the steps listed as a prerequisite to installing the flatpak version of PrusaSlicer-2.9.0 in a debian 12 system.� There are several flatpak utils available for debian 12 in the synaptic menu. So this is confusing.� Step 3 of the prerequisite setup for debian 12 assumes this file will be installed properly, but actually puts it wherever that shell is cd'd to.� Hence the subject line question as to where it actually belongs.
There is a manpage, says it could be in /home/$usr/.local/flatpak or in /var/lib/flatpak, and the rest of the stuff is in the /var/lib/flatpak tree. And its still not working correctly.
I'd post to the prusa forum but seem to have lost my pw there.
Tnx Tomas.
Cheers, Gene Heskett, CET.
And this is to indicate that flatpaks will not be accepted by debian?
Installing that is one of the steps listed as a prerequisite to installing the flatpak version of PrusaSlicer-2.9.0 in a debian 12 system.
Dies ist ein Opt-In Brandmal. Wenn sie keine weiteren Brandmale mehrbekommen m�chten, senden Sie bitte Ihren Fu� an uns zur�ck und
On 3/2/25 01:40, [email protected] wrote:
On Sat, Mar 01, 2025 at 04:42:22PM -0500, gene heskett wrote:
flathub.flatpakrepoNowhere.
And this is to indicate that flatpaks will not be accepted by debian?
And this is to indicate that flatpaks will not be accepted by debian? Installing that is one of the steps listed as a prerequisite to
installing the flatpak version of PrusaSlicer-2.9.0 in a debian 12
system.
On Sun, Mar 02, 2025 at 02:11:53AM -0500, gene heskett wrote:
On 3/2/25 01:40, [email protected] wrote:What do you mean by "accepted"?
On Sat, Mar 01, 2025 at 04:42:22PM -0500, gene heskett wrote:And this is to indicate that flatpaks will not be accepted by debian?
flathub.flatpakrepoNowhere.
Your box, your rules. There is no Debian police kicking down yourI didn't break this, the instructions for Debian pre-requisites setup
door if you *dare* to install something else on top (on the contrary,
Debian goes out of its way to make it possible for you to tinker.
That's why it imposes pretty restrictive rules on itself. That's
why there are so many derivatives of it.
But if you tinker, and break things in the way, then it's on you
to find out what went awry. Grown-ups and that.
You are welcome to ask help here, but then, again, it's on you toGoto the prusa site, select the prusaslicer as a Linux download, see a
try to wrap your brain a bit around those willing to help you,
instead of shooting out a question without the necessary context.
Otherwise... you might get useless answers.
Cheers
On Sun, Mar 02, 2025 at 10:01:17AM -0500, gene heskett wrote:Agreed. 2.8.1, the last AppImage, still runs just fine, after the
[...]
I lost track, with all those side tracks with ff and vpns and things,
but my tentative diagnosis is that prusa broke your Debian. But then
that's OK because you told it to do so.
Not nice of them, no.
Cheers
I just now installed PrusaSlicer by installing the Debian flatpak
package and following the instructions on the prusa site. The only perquisite I see is "sudo apt install flatpak"
.
I've done that. Where did you get the debian flatpak? Tn
gene writes:
I've done that. Where did you get the debian flatpak? TnDebian flatpak *package*. Type
apt-cache show flatpak
Flatpak is the tool that you use to install flatpaks. The flatpaks themselves do not come from the Debian archive. To install flatpak type
sudo apt install flatpak
and then read the man page. After that follow the instructions on the
Prusa site. Use sudo and do a "system" install, not a "personal"
one so that the flatpaks go in /var/lib/flatpak and not somewhere under
your home directory.
I assume that there is some reason why the version of PrusaSlicer that
is in the Debian archive is so unsuitable that you are willing to
tolerate the shambling horror that is the flatpak system.
There isn't any executable: that isn't how flatpak works. There's no
need for you to deal directly with anything under /var/lib/flatpak. To
run prusa-slicer type "flatpak run com.prusa3d.PrusaSlicer". I suggest making a script named prusa-slicer that executes that command and
putting it in /usr/local/bin.
An ls -lR of /var/lin/flatpack | wc -l shows:
gene@coyote:~$ ls -R /var/lib/flatpak|wc -l
44889
Nearly 45000 files for one app????
There isn't any executable: that isn't how flatpak works. There's no
need for you to deal directly with anything under /var/lib/flatpak. To
run prusa-slicer type "flatpak run com.prusa3d.PrusaSlicer". I suggest making a script named prusa-slicer that executes that command and
putting it in /usr/local/bin.
This is all documented on the prusa site and the flathub prusa page.
To remove a flathub package type "sudo flathub uninstall <packagename>".
John Hasler <[email protected]> writes:
There isn't any executable: that isn't how flatpak works. There's noMost users will launch GUI Flatpak programs from the desktop environment shell rather than the command line. For instance, in GNOME, you can
need for you to deal directly with anything under /var/lib/flatpak. To
run prusa-slicer type "flatpak run com.prusa3d.PrusaSlicer". I suggest
making a script named prusa-slicer that executes that command and
putting it in /usr/local/bin.
press the "Windows" key, type the program's name, and hit Enter. And
it's just the simple name (PrusaSlicer in this case, I suppose), not the
full FQDN package name.
.
Now I wait for trixie in thhe hope that I can convince it to NOT
install brltty and orca just because the ONLY usb socket is occupied
by a logitek wireless mouse button. They are not removable/purgeable
w/o screwing up the system, leaving a 30 second total freeze anytime I
want to open a file I own.
Hi,
On Mon, Mar 03, 2025 at 09:49:30AM -0500, gene heskett wrote:
Now I wait for trixie in thhe hope that I can convince it to NOTAs far as I'm aware no one has ever been able to replicate the problems
install brltty and orca just because the ONLY usb socket is occupied
by a logitek wireless mouse button. They are not removable/purgeable
w/o screwing up the system, leaving a 30 second total freeze anytime I
want to open a file I own.
you are having and we're not even sure if this is the root cause, so
it's fairly unlikely that any behaviour will change with the next
release except by chance.
It may be worth trying out a pre-release install of it to find out for
sure, before pinning a lot of hope on that.
Thanks,
Andy
| Sysop: | Keyop |
|---|---|
| Location: | Huddersfield, West Yorkshire, UK |
| Users: | 715 |
| Nodes: | 16 (3 / 13) |
| Uptime: | 42:23:35 |
| Calls: | 12,110 |
| Calls today: | 1 |
| Files: | 15,008 |
| Messages: | 6,518,427 |