steel wigeon
I was following this guide:
and right at the end of step 1, after hitting ctrl+alt+backspace and logging in again, I noticed that there are GUI elements missing from Nemo replaced with grey ⚠️ signs (see attached image)
in the end I couldn't achieve what I wanted by following the guide and I am giving up on it for now.
I would like help to undo the effects of the steps I took in the guide to restore the GUI elements.
west sail
I would suggest to first get knowledge of all the dependencies nemo uses.
then boot the Mint live USB, with the ISO you used to install linux mint.
then copy the nemo binary from it to where it belongs on your actual install, replacing the bad one you recompiled from source.
then do the same for any dependencies you may also have altered in that rebuild thing.
https://youtu.be/qxnM0rvVbDc?t=304 (5:04) how to use Synaptic, thorough and simple. Shown there how to look at all deps' for a given package.
Lastly, to sort stuff at top, add it as a favourite in the file manager, and it will show at top.
steel wigeon
@west sail Much as I dislike referring to LLMs, Google's AI said Nemo's binary is located at /usr/bin/nemo, but also referred to the locations of a few other related files, like the desktop launcher and libraries/extensions. It suggested running which nemo to verify the binary location, and sure enough it returned /usr/bin/nemo
This is definitely the binary, right?
Aside from dependencies, are there any other files associated with Nemo that I should replace, or will it suffice to replace /usr/bin/nemo?
I have installed Synaptic and found a list of Nemo's dependencies, how would you suggest I determine which ones were altered?
I have the feeling that I probably shouldn't replace all of them unless it turns out that all of them were altered.
I also find the dependencies/dependent terminology a bit confusing, I would like to be certain that I am dealing with the correct set of files.
west sail
<https://youtu.be/qxnM0rvVbDc?t=304> (5:04) how to use Synaptic, thorough and si...
see this vide from timecue for about 10 minutes. shows how to see all the dependencies. look up nemo on it.
might be able to just replace the binary in usr/bin
steel wigeon
Yes, I have already found the list of Nemo's dependencies. However I can only filter search for "nemo" under dependencies, not dependents
If I go to the properties of Nemo, then dependencies, it lists items as "Depends:", if I look at dependants, it lists "Dependency of", this is unclear to me as to what is dependent on what.
If I search for "nemo" in dependencies, the results include items from the second list, not the first, though I think I need the first list.
steel wigeon
I have been able to set up a custom filter for "nemo" in dependent packages, however just like the main search function it includes items that contain nemo rather than matching the exact phrase. Enclosing search terms in quote marks doesn't do anything. If I also only include installed packages in the filter, it seems to mostly match the list of dependencies in Nemo's properties, but it still contains items that are not included.
In any case all I am trying to achieve at this point is find out which of these packages were altered, I can't see any way that searching, filtering or viewing properties does that
west sail
the pic u shows that lists 'depends:' - those are are the things nemo needs to works
probably only ones with nemo in the name were altered. so swap those back, from live CD
steel wigeon
Thank you for clarifying
steel wigeon
then do the same for any dependencies you may also have altered in that rebuild ...
Of these packages, only which nemo returns an output when running, does that seem right? Or were you referring to files other than binaries?
