If you prefer a graphical tool, you can do the same thing with GNOME Disks, which also has options for disk benchmarking.
In the resulting report, the overall health state should be “PASSED”, the “Type” column should show “Pre-fail” and “Old age” values, and the “Media-Wearout-Indicator” should be close to 100. If the overall health state is “FAILED”, then you will want to back up your files immediately and consider getting a new SSD.
Not specifically. It’s probably actually a configuration problem though, for any other program I’d delete or default the settings. Not sure how to do that for flatpak itself as I won’t use it.
Definitely flatpak related then. Try running one of your flatpak apps from the terminal, and post the output here; might help pinpoint the issue. You can list the ones you have installed with flatpak list, then flatpak run <one of the listed apps, e.g. org.videolan.vlc>.
it took 30 seconds but this got outputted and then the file ran: dave@dog: ~$ flatpak run org.x.Warpinator Gtx-Message: 14:29:03.389: Failed to load module “xapp-gtk3-module” Using landlock for incoming file isolation
In a certain light, you could argue that Linus doesn’t really have any control at all. He doesn’t write any code for Linux (hasn’t in many years), doesn’t do any real planning or commanding or managing. “All” he does is coordinate merges and maintain his own personal git branch. (And he’s not alone in that: a lot of people maintain their own Linux branches). He has literally no formal authority at all in Linux development.
It just so happens that, by a very large margin, his own personal git branch is the most popular and trusted in the world. People trust his judgment for what goes in and doesn’t go in.
It’s not like Linux development is stopped because Linus goes offline (or goes on vacation or whatever). People keep writing code and discussing and testing and whatnot. It’s just that without Linus’s discerning eye casting judgment on their work, it doesn’t enter the mainstream.
Nothing will really get slowed down. Whether something officially gets labelled by Linus as “6.8” or “6.whatever” doesn’t really matter in the big picture of Linux development.
Yeah, it used to be just web servers in a data center. Bigger systems used mainframes. Consumer electronics used custom RTOSes or other custom boards. Now it’s everywhere. It’s used in the biggest systems, like the computers that power virtually every Google product, and the smallest systems. It’s almost not worth it not to use Linux when building a tiny device because it makes the dev cycle so much shorter.
Jesus I’ve been using Linux for years and your comment just made this really click for me. Do you think Linus is protected by governments and stuff? Like I know he didn’t make all of it, and there’s lots of forks, but he’s defacto in charge… That’s gotta be a lot of soft power
It’s because of the COVID vaccine mind control chips he put in everyone. If he wants to cause a storm, he just makes the entire population of Norway start flapping their arms in unison, which causes atmospheric disruption that leads to storms.
I got interested, so I spent some time looking into what’s going on here. I’m not intimately familiar with X11 or Wayland, but I figured out some stuff.
Why sudo ip netns exec protected sudo -u user -i doesn’t work for X11 apps
Short answer: file permissions and abstract unix sockets (which I didn’t know were a thing before now).
File permissions: when I start an X11 login session, the DISPLAY is :0 and /tmp/.X11-unix/ has only 1 file X0. This file has 777 access. When I start my wayland session with Xwayland, the DISPLAY is :1 and /tmp/.X11-unix/ has 2 files X0 (777) and X1 (755). I can’t figure out how to connect to display :0, so I guess I’m stuck with :1. When you change to a different (non-root) user, the user no longer has access to /tmp/.X11-unix/X1.
Abstract unix sockets: When I start my wayland/xwayland session, it creates abstract unix sockets with ids @/tmp/.X11-unix/X0 and @/tmp/.X11-unix/X1. See ss -lnp | grep Xwayland. The network namespace also sandboxes these abstract unix sockets. Compare socat ABSTRACT-CONNECT:/tmp/.X11-unix/X1 STDIN and sudo ip netns exec private socat ABSTRACT-CONNECT:/tmp/.X11-unix/X1 STDIN.
When you do sudo ip netns exec protected su - user, you loose access to both the filesystem unix socket /tmp/.X11-unix/X1 and the abstract unix socket @/tmp/.X11-unix/X1. You need access to one or the other for X11 applications to work.
I tried using socat to forward X1 such that it works in the network namespace… and it kinda works. sudo ip netns exec protected socat ABSTRACT-LISTEN:/tmp/.X11-unix/X1,fork UNIX-CONNECT:/tmp/.X11-unix/X1. It appears having ABSTRACT-LISTEN before UNIX-CONNECT is important, I guess it would be worth it to properly learn socat. With this sudo ip netns exec protected su - testuser -c ‘env DISPLAY=:1 xmessage hi’ works, but sudo ip netns exec protected su - testuser -c ‘env DISPLAY=:1 QT_QPA_PLATFORM=xcb kcalc’ does not work. 😞
Changing the file permissions on /tmp/.X11-unix/X1 to give the user access seems to work better.
Wayland waypipe
Waypipe works as advertised. But it’s still a little bit tricky because you need to have two separate processes for the waypipe client and server, wait for the waypipe socket to be created, adjust file permissions for the waypipe socket file, and set (and probably mkdir) XDG_RUNTIME_DIR.
Sir, you’re awesome! Thank you a lot for taking your time and explaining what you have found I will try these steps when I have some free time to tinker, and the info and script you have provided has cleared a lot of questions that I had
I had this problem with flatpaks, I changed the dbus implementation to dbus-broker (in endeavouros) and it fixed the issue. It may be the same problem.
I installed dbus-broker and the package manager checked the dependencies and removed the unnecessary stuff. After that I applied the dbus-broker services:
Yes, I remember reading about a gtk thing that interacts with flatpak, they said it should not give this error in April, but it seems to still be happening, idk.
Edit: I just saw that you deleted the gtk portal and it worked! So no need to install another dbus daemon.
Random shot, because it’s probably not an issue on Mint like it was on Arch a few months ago, but xdg-desktop-portal problems can cause apps to take forever to load, but run fine once loaded.
Portal basically is an interface/backend for flatpaks to interface with toolkits & DEs. If you don’t use flatpak, xdg-desktop-portal and associated backends should be removable. Even if you do, try removing the gtk and gnome backends w/apt. Hopefully it won’t try to remove a ton of stuff due to dependencies. Then, reboot and see if the slow loading problem goes away. If it does, you can try re-adding one or the other and see if it comes back.
Does logging in take forever as well?
Also after some cursory research, some people have had problems with portal on Mint after updates as well, just like on Arch. So… definitely try it.
wait hold on this is very likely holy shit, check my most recent post. the issue i have only impacts flatpaks. hold on what command do i run exactly and how dangerous is this. also tysm
this is a comment on my new post: it took 30 seconds but this got outputted and then the file ran: dave@dog: ~$ flatpak run org.x.Warpinator Gtx-Message: 14:29:03.389: Failed to load module “xapp-gtk3-module” Using landlock for incoming file isolation
what command would you use to trim on linux mint, the drive isnt dying to my knowledge. i just ran smartctl and it says i have 0 unallocated nvm capacity?
Indeed it won’t modify rar archives. What do you need those for?
The typical flow for rar archives is to unpack them and then either leave the files on disk as plain files or put them into a better archive format such as 7z.
My initial goal (before learning what a headache rar is) was to preserve the original file format. Now my plan is to convert them. I have to confer with my friend to see what format they’d prefer for the files. Probably end up using regular old zip.
[Mouseover text] Thomas Jefferson thought that every law and every constitution should be torn down and rewritten from scratch every nineteen years–which means X is overdue.
As somebody that first configured X back in 1991, I agree with this message.
To be fair though, with KMS, libdrm, and libinput, setting up X is 1000 times easier than it used to be. I suspect most users never even need to open Xorg.conf or even know it exists.
Ironically, all these technologies are also used by Wayland. A lot of what Wayland does not do, Xorg basically does not do either.
Those are just changes to the build system. The last upstream release was 7 years ago. Last commit to the main branch was 6 1/2 years ago. This project is unmaintained. It should be forked by someone who is passionate about it.
Can anyone give a layman an explanation as to what makes software like this unmaintained? It seems like it should be fine if it works and is still getting updates.
the package is maintained (will continue to install on modern ubuntu versions), but the software is unmaintained (no bug fixes, no new features, will stagnate and eventually become obselete as incompatible with future desktop standard modifications)
alright edit: I have a Flatpak issue, not an SSD issue. does anyone have any thoughts? this could be due to the new linux mint update. my pc is a samsung galaxy s2 (750XED P13CFG)
the linux mint discussion forum has a post about my model not being great but last update my system worked just fine. i actually think having a full ssd broke flatpak. otherwise ive hit a horrible regression issue github.com/orgs/linuxmint/discussions/277
linux
Active
This magazine is from a federated server and may be incomplete. Browse more on the original instance.