Wow, that reply was super fast. That was my first thought, but my friend doesn’t know how to solder and doesn’t own a soldering iron. Is it possible it was like this from the factory?
Was it new or brought used? Either way probably not the best for it so maybe get your friend to return it (unless they lied and did it themselves, haha)
New. He bought it last summer in August, so it should still be under warranty. Yeah, my thoughts exactly. I’ve never seen this, so I kind of don’t want to put it back in the motherboard for fear of causing further damage.
That is sooo weird. Unless that thing shorted and heated up so much that it melted the solder, in this case I’m not sure there’s any extra harm in putting it back in the socket. I usually wouldn’t advise this but if it was gonna cause damage it’s probably already done.
At this point I think there is a definite possibility that this solder blob has always been there and that we may be barking up the wrong tree.
Unless that thing shorted and heated up so much that it melted the solder, in this case I’m not sure there’s any extra harm in putting it back in the socket. I usually wouldn’t advise this but if it was gonna cause extra damage it’s probably already done.
Fair point. I’m probably not going to experiment too much. I was just curious about the silver blob, because I’ve never seen this before. If I can’t find any obvious faults, I’ll just advise my friend to take his PC to a repair shop or something.
Alright, well if you want you can let me know what actually happens when you push the power button. Any beeps, lights, fan spins, clicking, demonic apparitions, just completely dead, etc.
Sometimes just reseating everything is the fix too.
Unfortunately nothing changed even after reassembling the PC. We’re just going to take it to a local PC shop since they have more tools on hand to diagnose the problem. Thanks for your help, though!
Yeah figures. As another user mentioned, this could very well be the issue that Gamers Nexus exposed a while back. That CPU might still be under warranty. Hopefully the PC shop will be able to sort this out for you.
Hmm I had something different in mind. More along the lines of getting freaky with demons but hey inhaling the magic blue smoke is 100% valid too. I’m down.
With a bit there the cooler probably isn’t making good contact with the CPU, but if that was the case I wouldn’t expect it to just die if it was working before. Though the higher heat may have caused permanent issues too, hard to say.
I have an all in one CPU liquid cooler that had a bracket on incorrectly but it still worked fine until I played with overclocking so that’s all I base this comment on.
Then I got a lot of duplicate files. For example in subfolders relating to my mp3 player I even discovered my whole NextCloud ‘drive’ is there again: /run/user/1000/doc/by-app/org.strawberrymusicplayer.strawberry/51b78f5c/N
In Linux a file can show up several times in the filesystem without being duplicated. Symbolic links and hard links will cause this to happen, and they’re a normal part of organizing the filesystem. Just because you see a file in several places, that doesn’t mean disk space is wasted with duplicates. There may be only one physical copy of the file, appearing in multiple places. With hard links you need to be especially careful about deleting, since you’ll think you’re deleting one of several duplicates but you’ll in fact delete the only copy of the file.
I think others have answered what the folder should do.
FSearch is great, but I wouldn’t index the entire file system. There isn’t much point in indexing things you won’t be using such as all the system files and the representations of hardware processes. It’s a bit like on Windows indexing c:\windows - you just don’t need all that clogging up your search results. But the Linux filesystem encompasses much more so you’d get even more stuff.
On my system I index my home folder (where all your own files will be kept) and my mount points (for me a series of drives I mount under /mnt/). You could also index /media (or variants) as that is where USB drives, and CDs etc would mount to - but I don’t tend to index USB sticks etc.
I can see circumstances where you might want to index other locations depending on how you use fsearch and Linux, but I think for most users it’d just be unnecessary indexing and results.
Edit: I saw someone else mention /etc too. That can be useful if you want to find system config files. They also mentioned /usr/share/docs which contains a lot of the Linux manual/distro docs amongst others. If you want to access that then it’s not a bad idea to index it, although most people are online all the time now on multiple devices so it may be a bit redundant for most users day to day; I tend to just search online documentation.
You’re using flatpak, right? Flatpak uses “portals” to provide access to other parts of your system. When you open files in flatpak apps, you’ll see this folder used for those.
These shouldn’t actually take up any meaningful space, and I wouldn’t delete anything unless you’re experiencing an issue.
It is most likely another filesystem mounted where the flatpak can see it. A terminal tool like ncdu or even du will take an -x option to not cross file-system boundaries. That will show the true usage of everything bellow where you call it (even though it is a ramfs so not persisted across reboots).
Nice that you are using FSearch :) I would put more excludes in it when you really want to index / In fact, apart from /home I would not index anything else than /etc /usr/share/doc and maybe /var/run/media or /media (depending on which Linux distribution you are using, for example Arch Linux will use /var/run/media and Ubuntu will use /media for removable devices).
Only thing i saw here are general answers. /run/user/1000 resp. $XDG_RUNTIME_DIR is a tmpfs (somt. like a ramdisk) created by PAM (pluggable authentication module) on login, 1000 being your user id. It is more restricted in security and size than cache and should be used for small files where quick access or security matters. A common example are sockets.
You can delete it, it will just be regenerated next log in, but your very session will run into trouble, you should log out after (if you don’t just get booted out, that is).
And yeah, like others said; this is not Windows, you don’t have to, and shouldn’t, clean up anything outside your home dir.
/etc - Et cetera. The name is inherited from the earliest Unixes, which is when it became the spot to put config-files.
/home - Where home directories are kept.
/lib - Where code libraries are kept.
/media - A more modern directory, but where removable media gets mounted.
/mnt - Where temporary file-systems are mounted.
/opt - Where optional add-on software is installed. This is discrete from /usr/local/ for reasons I’ll get to later.
/run - Where runtime variable data is kept.
/sbin - Where super-binaries are stored. These usually only work with root.
/srv - Stands for “serve”. This directory is intended for static files that are served out. /srv/http would be for static websites, /srv/ftp for an FTP server.
/tmp - Where temporary files may be stored.
/usr - Another directory inherited from the Unixes of old, it stands for “UNIX System Resources”. It does not stand for “user” (see the Debian Wiki). This directory should be sharable between hosts, and can be NFS mounted to multiple hosts safely. It can be mounted read-only safely.
/var - Another directory inherited from the Unixes of old, it stands for “variable”. This is where system data that varies may be stored. Such things as spool and cache directories may be located here. If a program needs to write to the local file-system and isn’t serving that data to someone directly, it’ll go here.
Don’t delete it. It’s an area of the filesystem where the current user session data is kept. This includes things like sockets to communicate with other session components and lock files. It’s usually hosted on a ram disk so takes up no space in the system and goes away when you shutdown your machine.
Files in /run will be (re)created (and removed) at runtime if/when needed by programs that need them. They pose no problems and don’t persist between reboots.
The most important thing to realize about the “file system” in Linux is it does a lot more than just persist your documents and app data. You shouldn’t index your root directory because almost everything other than your home directory is some kind of Linux distro/application-specific directory that is often not a normal directory stored on a storage device. If you run the mount command with no arguments, every line of output is a separate file system, mounted at some specific directory of the current “mount namespace”. Kinda confusing, but every process in Linux has a mount namespace that has a list of mounted file systems, often that namespace is shared between many/most processes, such as your terminal shell. Most of the file systems will be virtual i.e. not representing anything in storage. For example sysfs (always mounted at /sys), proc (always mounted at /proc), devtmpfs (mounted at /dev), etc. are all completely virtual and are ways for system services and applications to access state and devices exposed by the Linux kernel. They should never be indexed, treated as normal files, or modified by the user.
That’s probably even more confusing, sorry. But the gist of it is, the only directory on your system you can really count on actually being stored on disk and always available to you is your home directory. Basically everything else exists as an implementation detail of the operating system and software applications.
If I were you, I’d stick to only indexing your user home directory. Indexing /usr or /tmp or /etc or whatever is like indexing C:\Windows and C:\Program Files, except even weirder since at least on Windows those are actually files stored on disk whereas in Linux they may not even be actual files (although most of them in /usr and /etc are actual files on disk).
There is a simple trick, as a basic user, do not ever run your (gnome) file explorer as root and if a permission error (requiring “escalation”) pops up you shoud double check what you are doing.
I think most graphical f.mangers also keep most of the weird/important/system folders away from user and you have to directly navigate to them.
You may also encounter some contradictory information out there too. For example, I said don’t modify stuff outside of your user home directory, but some people will advise to modify stuff in /etc. Although I would never do this on a desktop distro (usually /etc is set up the way the distro maintainers want it, and anything you need to modify will have another more user-friendly way to modify it), especially one where you’re mostly just trying to run desktop applications. It might make sense to modify stuff in /etc on a server installation since that’s where a lot of configuration for different daemon processes (i.e. system services but also server applications) and even software libraries goes.
That’s one of the good and bad things about linux. There is some information about all this stuff on the internet if you can find it, but it is also an information overload and you’re basically learning about the internals of the operating system with all the associated complexity. That’s one thing that threw me off about linux initially (I started getting into this stuff only a couple years ago), almost everything you learn about linux is basically an implementation detail. There are Windows equivalents to most things in linux, but when you use Windows as a desktop user you don’t really think about them unless you’re developing an application using Windows-specific APIs.
Windows has things like COM (linux equivalent is gobject and dbus), Services (linux equivalent is systemd services), Win32 API (this is a million things in Linux like glibc and a bunch of other system libraries, just check out how many files are in /usr/lib or /usr/lib64), Registry (dconf/gsettings) and so on.
There’s also unfortunately no real clean break between “stuff anyone should know” and “stuff programmers and linux distro developers should know”. A lot messier than something like iOS or Android where if you’re a normal user you basically don’t see the OS implementation or hints of it at all.
Trying to hide the implementation details is also why the GNOME Files app shows you some documents folders on the left but makes it more difficult to view the root directory or even the current file path. Which was very frustrating and confusing for me, coming from Windows.
So what, give the CEO half and pay the rest to the mods? Like 1300 bucks per year without tax and fees. What would be left? 50 bucks per month? Reddit has like 75000 moderators. Some for huge Subreddits, some for small ones. Equal pay? Or what?
Someone has to organize all that paying, many are in different countries, different tax laws. In the end, there would be like 20 bucks per month for each. You then would also require extra heavy checks for moderation quality to ensure they are worth their pay. You’d need systems to prevent abuse. If there’s money involved, people become extra greedy. Just pay some of them? Only the ones working a few hours per day? Pay per moderating action? What?
Or you just do double pay for the CEO. Seems like a no-brainer.
“Our business model sucks and we don’t want to do the work to pay the people who perform labor for us. Therefore, our CEO deserves a hundred million dollars.”
We’re high IQ tech bros who deserve to be paid millions, but you can’t expect us to work out basic management and payroll techniques literally every industry has implemented!
…or you invest the money in actually making your platform decent and adding features mods have been asking for years. But then big number doesn’t go up so it’s a bad idea I guess.
I guess I would also answer that with controversial opinion.
They don’t want a better platform. Reddit does exactly what they want it to do. To generate tons of discussions about the same things, over and over again. To generate loads of different feelings and situations. To create a very diverse pool of data.
They might have started out with a good ideology, but then success came.
I like to compare it with Quora. It could have been the best site of its kind. But it served its purpose, being a feed-bucket for an AI, and now it’s not even moderated anymore. And they did pay their users and mods, but it didn’t work out, too many tiny transactions, only like a handful of people got anything, and those abused it like crazy.
Just my take on it. Such payment models won’t work. A few giants will earn the majority, and they will cheat and fight for it, the rest will still get nothing. They could have taken three thirds of that CEO money to create a few resident jobs. But why bother, Reddit is exactly how they want it to be. Most users just don’t realize the pseudo-scam, believing it’s their favorite discussion platform that they can influence, while the creators have a content-generator with free labor in mind.
Looks like solder. Soldering irons are pretty cheap. You could try getting a cheap one and melting it off; but if you’ve never soldered before I’d recommend watching some videos on how to handle it so you don’t just make things worse.
lemmy.ml
Active