overview for Samueru

I don't use gearlever, as far as I know gearlever doesn't even let you sandbox the appimage like AM does. I don't think any of those forces signature verification besides AppImageUpdateTool and that's because that's part of the zsync update process.

Inkscape Flatpak is looking for a maintainer! in c/linux@lemmy.ml

[-] Samueru@lemmy.ml 1 points 3 days ago

Running things from random directories (like ~/Applications which AppimagePool uses) destroys that.

~/Applications is no a random place, it comes from macos. And what is appimagepool?

You mean appimagetool? that's used to turn the AppDir into an appimage.

If you meant appimagelauncher, ~/Applications is the default location but it can be changed to any location.

(including appimages which are nearly impossible to sandbox)

See that lock next to some appimages? Yes that's aisap sandbox..

It isn't perfect though, right now its biggest limitation is that a sandboxed appimage can't launch another sandboxed appimage. But dbus, pipewire, vulkan, themes, etc works.

The “open with” and “create new” things. Actually,

You can totally do that with appimages once they are integrated into the system by the previously mentioned tools, those menus rely on desktop entries in $XDG_DATA_HOME/Applications.

That concept is so broken that it needs to go.

Good thing we have choices on linux, you can make your entire home not executable if you want to.

I like to keep all the software that I need in my home, because that way I don't depend on what my distro provides. I can just drop my home anywhere (besides a musl distro) and I'm ready to go, I even have my window manager as an appimage because I couldn't compile it statically.

But the issue is that they were just thrown out there, “here devs, do the same shit you do on Windows, it is totally normal for people to double click an executable, not have any sandboxing, deal with updates on their own, dont have any cryptographic verification, …”.

AppImage is just a format, same as a deb or rpm, you decide how you handle it afterwards.

doing the actual update process (instead of deleting a file and placing a new one)

Same link again: https://github.com/AppImageCommunity/AppImageUpdate

Many of the appimage devs actually worked on making zsync2 for this: https://github.com/AppImageCommunity/zsync2

On Android you still have a package manager but the APKs are signed individually, updates just allowed if the signatures match. So you can sideload how you want, it is still secure.

You mean the APK itself does the signature verification or what? With appimage it is AppImageUpdateTool that does the verification.

(appimages are impossible to sandbox with bubblewrap, and hard with firejail (which is a setuid binary and had security issues), dont know about nsjail, crabjail, minijail or others)

Again this nonsense.

Regarding what?

You still have that github repo saying that appimages bloat the system when that is a total lie. they can even use less storage than native packages let alone comparing it to flatpak...

Inkscape Flatpak is looking for a maintainer! in c/linux@lemmy.ml

[-] Samueru@lemmy.ml 1 points 3 days ago* (last edited 3 days ago)

But they dont have installers, so no verification

https://lemmy.ml/post/17283790/11897811

on Linux the entire home is executable which is a huge security issue

You still have to give the exec permission to the appimage.

no desktop integration, no context menu, no file associations.

Maybe no context menu depending on what you mean exactly, but the rest are fully possible and I do it on a regular basics with my appimages...

edit: Omg you are the guy from don't use appimages, I see you haven't changed one bit.

Inkscape Flatpak is looking for a maintainer! in c/linux@lemmy.ml

[-] Samueru@lemmy.ml 3 points 4 days ago* (last edited 3 days ago)

And Windows executables have some weird signature verification which Appimages dont have at all.

...

EDIT:

Appimages have no install wizard.

Appimagelauncher, gearlever, AM, etc. Which is the same as a install wizard since it integrates the appimage into the system. AppImages do not need to be extracted into the system which is what windows install wizards do.

Inkscape Flatpak is looking for a maintainer! in c/linux@lemmy.ml

[-] Samueru@lemmy.ml 7 points 4 days ago

What happened to just donwload the app from it’s own creator and install on your machine?

You have that option with the appimage, inkscape releases it themselves.

40 years later, X Window System is far more relevant than anyone could guess in c/linux@lemmy.ml

[-] Samueru@lemmy.ml 1 points 4 days ago

Oh it's done by assigning the same keybind to each action.

That will likeky make my config 1000 lines long 😅

40 years later, X Window System is far more relevant than anyone could guess in c/linux@lemmy.ml

[-] Samueru@lemmy.ml 36 points 6 days ago* (last edited 6 days ago)

Yes, I spent a while reading the documentation on how to pin workspaces to certain monitors only for hyprland to tell me that it is deprecated.

Also an issue I noticed is that you can't move floating windows between displays with the move left/right commands, move left/right moves the floating window to the left or right of the display and no more, meaning that the window gets stuck at the border of the display and doesn't move more.

Also I couldn't figure out how to make hyperland run several commands in a row with one keybind, or how to filter windows with expressions, something that I do a lot on my i3config .

And my biggest issue, and this one seems to be with wayland in general is that it seems that it is impossible to set my displays to extended more, that is turn the 3 displays that I have into a single display which I use with some games.

i3 isn't perfect either, I actually had to fork it and apply a patch that fixes and issue that I have that hasn't been merged yet either.

I will list all my issues with sway anyway, hopefully somebody out there notices it and fixes them:

https://github.com/swaywm/sway/issues/8000

https://github.com/swaywm/sway/issues/8001

https://github.com/swaywm/sway/issues/8002

https://github.com/swaywm/sway/issues/8191

And all these bugs are the result of less than 2 days in total of use of sway, there is likely more that I haven't run into.

I also had an issue that affected xfce4 apps, but that issue ended up being a dbus-broker issue that only happens on wayland for some reason lol

40 years later, X Window System is far more relevant than anyone could guess in c/linux@lemmy.ml

[-] Samueru@lemmy.ml 29 points 6 days ago

I have a feeling I will be on i3 for many many years given all the issues that I've had with sway.

21

Anyone using wayland with $XDG_CACHE_HOME set? (lemmy.ml)

submitted 1 month ago* (last edited 1 month ago) by Samueru@lemmy.ml to c/linux@lemmy.ml

23 comments fedilink

I'm a i3 user that has been trying to migrate to sway.

I use it with these environment variables:

export XDG_DATA_HOME="$HOME/.local/share"
export XDG_STATE_HOME="$HOME/.local/var/state"
export XDG_CONFIG_HOME="$HOME/.local/config"
export XDG_CACHE_HOME="$HOME/.local/var/cache"

Which gives me a clean home with only ~/.local for my dotfiles.

And issue that I've noticed that I haven't been able to fix is that every time that I start sway, hyprland and also the alpha of cosmic is that I get a new ~/.cache directory created in my home that contains a mesa_shader_cache directory.

Btw in the middle of writing this post I just ran into another bug, thunar for some reason decided to steal my key presses from the web browser, and even though I had the browser window focused as I have sway configured to change the border color of the window with focus, thunar was like nope wtf.

Thank you all for the help, ended up opening a bug report at sway: https://github.com/swaywm/sway/issues/8191

183

Vim Lands XDG Base Directory Specification Support (www.phoronix.com)

submitted 2 months ago by Samueru@lemmy.ml to c/linux@lemmy.ml

21 comments fedilink

-9

Couldn't resist (lemmy.ml)

submitted 6 months ago by Samueru@lemmy.ml to c/archlinux@lemmy.ml

0 comments fedilink

4

How to undo xrandr --setmonitor extended? (lemmy.ml)

submitted 7 months ago* (last edited 6 months ago) by Samueru@lemmy.ml to c/archlinux@lemmy.ml

1 comments fedilink

I have this command on my i3wm configuration, which extends the 3 displays that I have into a single one for games.

bindsym $mod+Shift+k exec "xrandr --setmonitor extended auto DP-1,DP-2,DP-3"

The only issue that I have is, once I'm done, how do I revert back to having the displays individually? This has been driving me crazy.

Searching on internet all that I've managed to find is using xrandr -s 0, which actually just turns off my other displays.

And what is worse is that if I then manually turn the displays back on, THEY ARE STILL EXTENDED "xrandr -s 0" does not even reset that lol.

So far what I have to do to revert the changes is to log out of my current session.

SOLUTION: THE COMMAND IS: xrandr --delmonitor extended

5

How can I turn this shell script into a single line command? (lemmy.ml)

submitted 7 months ago by Samueru@lemmy.ml to c/linux4noobs@lemmy.world

3 comments fedilink

Here is the script, which is a hack that I use with i3wm, I already converted most of it to a single line and it still works:

#!/usr/bin/env bash

is-leaf-node() { i3-msg -t get_tree | jq 'recurse(.nodes[]?, .floating_nodes[]?) | select(.type == "con" or .type == "floating_con") | select(.focused == true) | .nodes == []';}; parent-type() { i3-msg -t get_tree | jq -r 'recurse(.nodes[]?, .floating_nodes[]?) | select(.nodes[]?.focused == true) | .type' ;}; if [ "$(is-leaf-node)" == "true" ]; then i3-msg focus parent, focus parent; else i3-msg focus child, focus child; fi

Here is where I'm stuck:

The script needs the #!/usr/bin/env bash to work, it is the only script that I have that needs it.

Changing it to #!/usr/bin/env bash; does not work, it has have a second line for it to work.

7

Theme issues when starting i3 session with startx instead of lightdm. (lemmy.ml)

submitted 7 months ago by Samueru@lemmy.ml to c/archlinux@lemmy.ml

4 comments fedilink

I'm trying to migrate from lightdm to just using startx to start my i3 session.

First I had issues with kdeconnect working which were fixed by replacing exec i3 with exec dbus-launch --exit-with-session i3 in the xinitrc.

Now even though the apps works it is not following the system theme, I checked qt5ct and it is telling me that QT_QPA_PLATFORMTHEME is not set to qt5ct.

But I do have export QT_QPA_PLATFORMTHEME=qt5ct on my ~/.profile it seems the file is not being read but I have no idea on how to fix it.