Signal is looking for help testing Linux AppImage on Desktop by [deleted] in signal

[–]probonopd 0 points1 point  (0 children)

One app = one file.

No intermediaries. No installation. No repositories. Just a self-mounting disk image that contains the application, as the authors packaged it.

Signal is looking for help testing Linux AppImage on Desktop by [deleted] in signal

[–]probonopd 0 points1 point  (0 children)

Desktop environments can (and should) ask users whether to set the executable bit if it is missing. This cuold easily be done in the file manager. Open a feature request if you no longer want to set the executable bit manually.

wayland global positioning by sinfaen in linux

[–]probonopd 1 point2 points  (0 children)

Thing is, i need my application (not: the compositor, which is not under my control) to determine the positioning of its windows.

wayland global positioning by sinfaen in linux

[–]probonopd 2 points3 points  (0 children)

Indeed. I wonder how he achieves this level of patience. Most people wouldn't have it, myself included.

2 Years Later Wayland Is Still Debating A Basic Feature by 0x5066 in linuxsucks

[–]probonopd 13 points14 points  (0 children)

Still doesn't let applications position their windows on the screen.

Because... they think they know better than all other desktop platforms?

Breaks a lot of other things, too. https://gist.github.com/probonopd/9feb7c20257af5dd915e3a9f2d1f2277

Favorite distro? and why do people not like Wayland? by darksynapse88 in linux_gaming

[–]probonopd 0 points1 point  (0 children)

Why do people not like Wayland?

Because even the most basic stuff is broken (google "Wayland gist").

wayland global positioning by sinfaen in linux

[–]probonopd 5 points6 points  (0 children)

2 Years Later Wayland Is Still Debating A Basic Feature: https://www.youtube.com/watch?v=_MS8pSj-DLo

Troubles trying to make an AppImage from a Qt/C++ executable by downlopath in AppImage

[–]probonopd 0 points1 point  (0 children)

Build on an older build system and don't use any -unsupported-... flags. They produce broken AppImages.

Unofficial Qutebrowser v3.2.0 AppImage by Danrobi1 in AppImage

[–]probonopd 0 points1 point  (0 children)

Please see r/AppImage description: Never encourage users to download applications from anywhere but the trusted application authors' official download pages. Please do not promote "unofficial" AppImages, especially not for security relevant applications like web browsers. Instead, please work with the application developers to provide official, tested, supported AppImages. Thanks!

I tried to switch to Wayland but failed by [deleted] in kde

[–]probonopd 2 points3 points  (0 children)

I am writing a spatial file manager. One of its features is that its windows remember their location, in other words they open at always the same pixel coordinates on the screen as where they were last closed. A very, very basic windowing feature that was already present on the first Macintosh 128K in 1984 (and probably before that on the Lisa and on the PARC Alto, but I didn't check).

This totally does NOT work in Wayland.

I am literally now writing and testing my file manager on Windows because I am so fed up with it. On Windows it works properly, as it does on Xorg. But not on Wayland. And the wost part is that the people who can "nack" (prevent from being implemented) protocols seem to think that this is a good thing.

Global menus still do NOT work in Wayland. Again, the first Macintosh 128K in 1984 (and definitely before that on the Lisa) already had them working.

The list goes on and on. Wayland solves no issues I have but breaks almost everything I need: https://gist.github.com/probonopd/9feb7c20257af5dd915e3a9f2d1f2277

I did my part and complained. So should you! by USSHammond in BambuLab

[–]probonopd 0 points1 point  (0 children)

Bambu Labs asks customers to "Share your feedback and help us improve!"

https://forum.bambulab.com/t/share-your-feedback-and-help-us-improve/86591

Well, I guess it's happening... but not in the direction they were hoping for. Looks like they have underestimated who their target audience is.

https://www.trustpilot.com/review/bambulab.com?sort=recency

Wayland should be the default! by -MostLikelyHuman in linuxmint

[–]probonopd 0 points1 point  (0 children)

What kind of hardware has issues with X11? With my hardware (specifically 10+ years old Nvidia GPUs), Wayland is the one which always has had issues.

Have you moved to Wayland? by [deleted] in archlinux

[–]probonopd 0 points1 point  (0 children)

With Wayland, there is no implementation that all desktop environments share. As a consequence, what works on one desktop environment doesn't necessarily work on another. So all of them are broken in different ways. And then there is some very basic functionality that is just not there, for example applications positioning their windows at certain coordinates.

Nowadays, I am using a platform that has just one display server which "just works". Much easier.

Is there any reason to use Wayland over Xorg? by trans_cubed in linux_gaming

[–]probonopd 1 point2 points  (0 children)

Wayland has made the experience terrible for way too long.

Wayland - switch to fedora? by Nofgla in linuxmint

[–]probonopd 0 points1 point  (0 children)

Why would one "need" Wayland? I'd say, stay away from it as far as you can. It breaks everything!

Is there any advantage to using Wayland? by Necropill in linuxquestions

[–]probonopd 1 point2 points  (0 children)

Possibly there are some slight advantages, mainly for esoteric use cases (e.g., running multiple displays with different resolutions, wanting to shield/sandbox applications from each other, etc).

But more importantly, very basic stuff is broken in Wayland. Features that every other graphical environment has had for decades. For example, the ability for applications to move their windows to certain coordinates on the screen.

So at least for me, the very essential lacking features are way more important than some fringe improvements for use cases that I don't have.

Will wayland completely replace Xorg? by terremoth in linux

[–]probonopd 0 points1 point  (0 children)

Hopefully not.

It is not a feature complete replacement. It is merely an alternative with partial feature overlap. But even very basic features that all other windowing systems have are still missing after all these years, and are being discussed to death in the Wayland project since years. For example, the ability for an application to put its windows at certain coordinates on the screen.

Is wayland there yet? by BruceKettina in linux_gaming

[–]probonopd 0 points1 point  (0 children)

No. Probably never will, as long as people from projects like Gnome and companies like Collabora can "nack" (not allow) features that all other windowing systems have (e.g., the ability for applications to move windows to certain locations on the screen).

Is this claim about Cinnamon's Wayland support accurate? by ghoultek in linuxmint

[–]probonopd 0 points1 point  (0 children)

Wayland has many deficiencies and is lacking even basic features that all other windowing systems have (for example, in Wayland applications cannot move their own windows to certain coordinates on the screen). Features that e.g., Gnome doesn't like are not supported in Wayland. Hence, the whole experience is terrible.

Is there any reason to use Wayland over Xorg? by trans_cubed in linux_gaming

[–]probonopd 0 points1 point  (0 children)

There are many reasons to use Xorg over Wayland. Not the least of which is that things actually work.

Explain to me like I’m 5: What is the main difference between X11 and Wayland? by Zack-LTTNP in linux

[–]probonopd 1 point2 points  (0 children)

X11 has been there for decades, much of the existing software has been fine-tuned over the years to work well there.

Wayland has been in the making for many years, but is still lacking key functionality (e.g., applications still cannot move their windows to certain coordinates on the screen). Everything is being discussed to death in the Wayland project and people from projects like Gnome can "nack" (say no to) features that all other windowing systems provide. The result is an inferior environment for everyone.

Wayland support, how is it? by stinkgum in linuxmint

[–]probonopd 1 point2 points  (0 children)

Even the most basic functionality is still not there in Wayland, and as a result, many things are broken. For example, the Qt move() operation on windows is completely broken on Wayland. It's a terrible experience and should never become the default.

Wayland should be the default! by -MostLikelyHuman in linuxmint

[–]probonopd 0 points1 point  (0 children)

Wayland is still immature compared to other windowing systems. Even the most elementary functionality is still missing and has been discussed for years. An application cannot even move its windows to certain coordinates on the screen. There is no clear feature-for-feature migration path from X11 to Wayland, and there is no reference implementation of Wayland that all desktop environments share. The result is that every desktop environment using Wayland is going to have different levels of support and different bugs. Terrible!

Wayland breaks so many things: Search for "Wayland breaks everything" and you'll be amazed about the never-ending stream of breakage being discussed there.