Any fellow Linux users on here?

[Judge]

I'll be moving from a Win 10 temporary setup into a bare-bone fanless box I like.

Fanless?

One of Noctua's enormous but fanless heatsinks? I'd love to hear from anyone using such things. Thermodynamics are always a major concern of mine, countered by the noise fans make.

 

[Princess Viola]

I think the latest Wine update broke something because now Civilization IV won't even launch (nor will my other Windows programs that I used through Wine, which is like...just one thing but still - I'm not counting my other games since I don't use those through vanilla Wine)

But then I decided, just for the hell of it, to try and launch it through Lutris (game manager that can handle all of the setting up of Wine, Wine configs, etc. for Windows games and other Windows programs so you don't have to deal with it all yourself - including giving you the option to choose different compatibility layers because sometimes you might need to use a specific one to get a game working or whatever), even though it previously wouldn't launch at all through Lutris (which I assumed was because my Civ IV install is on my 2 TB NTFS storage drive (which is NTFS because I would use it when I was still dual-booting Windows)

And it just launched and worked. Honestly, I wasn't even in the mood to play the game (mostly because it was like 1am and Civ IV is not a game you play at 1am unless you don't wanna sleep), I just updated a couple of my mods and wanted to make sure I did it correctly. The first mod loaded just fine (albeit this was the mod that takes like 5 minutes to load up because it's a big mod) and the second mod...well it loaded but I got some Python errors during the loading process, so I might try to delete and completely reinstall that mod.

Still no idea why the game didn't launch before through Lutris, but I'm glad it does now. Even if Wine hadn't broken, just being able to launch Civ IV through Lutris is a lot easier than going to media/viola/Storage/HP 1 TB Backup/Civ 4 Backup/2K Games/Firaxis Games/Sid Meier's Civilization 4 Complete/Beyond the Sword and clicking Civ4BeyondSword.exe lol

 

[Princess Viola]

Update: Wine released a new update and I got an error. Specifically:

E: /tmp/apt-dpkg-install-nokSBo/03-wine-devel-amd64_10.2~noble-2_amd64.deb: trying to overwrite '/opt/wine-devel/bin/wine', which is also in package wine-devel-i386:i386 10.2~noble-2

Luckily I did a search and found the solution on the r/linuxmint subreddit.

If you're trying to update Wine to 10.2~noble-2 and it doesn't work, just do sudo dpkg -i --force-overwrite /var/cache/apt/archives/wine-devel-amd64_10.2~noble-2_amd64.deb followed by sudo apt -f install

 

[Judge]

Update: Wine released a new update and I got an error. Specifically:


Luckily I did a search and found the solution on the r/linuxmint subreddit.

If you're trying to update Wine to 10.2~noble-2 and it doesn't work, just do sudo dpkg -i --force-overwrite /var/cache/apt/archives/wine-devel-amd64_10.2~noble-2_amd64.deb followed by sudo apt -f install

Interesting. I updated to 10.0 a while back and had no hiccups with Photoshop.

But geez, I've tried all kinds of games with Wine and none of them ever worked. Nothing prompted yet for version 10.2, but maybe I might just avoid it. Just wondering if using Timeshift can reverse it back to 10.0 if it doesn't work.....<?>

Did you originally install Wine using the repository, or did you install it manually? I've always done manual installs, but they can be problematic if you don't do it correctly...syntax issues and all. Guess it doesn't matter though since you found a solution.

On this drive I'm running Mint 22.1. Then again I'm also using an Intel CPU and Nvidia GPU. Hmmm....looks like that update was just released a few days ago. Though today I got a kernel update...no issues so far. Went back to my other drive using version 22.0....a few updates to do, but none of them involved Wine.

Wine 10.2 Released

 

[Princess Viola]

Did you originally install Wine using the repository, or did you install it manually? I've always done manual installs, but they can be problematic if you don't do it correctly...syntax issues and all. Guess it doesn't matter though since you found a solution.

Yeah, I installed it manually.

 

[Judge]

Yeah, I installed it manually.

Just found something very interesting. If you go to WineHQ's website, you'll see that version (10.2) is shown as a "development" version. Not a "stable" version (10.0).

Using a development version of Wine might not be in your best interest in the long run. My suggestion under such circumstances? To delete all references to this version of Wine (10.2) and all Windows programs, then reinstall the stable version of Wine (10.0).

I've found it most effective when having to purge Wine to first use the "wine uninstaller" in the terminal to first purge all the windows apps you are running in accordance with windows uninstallers. After that, then to purge Wine altogether I use both the Synaptic Package Manager first to delete all installed Wine files, and then go into your file manager and show all hidden files, to delete the Wine folder and everything within it. Then to reboot, and reinstall Wine, making sure to download only the stable version only.

This may well also explain why I haven't gotten any updates from Wine from either version 22.0 or 22.1. (I never use any of Wine's versions other than their existing "stable" version.)

WineHQ - Run Windows applications on Linux, BSD, Solaris and macOS

 

[Princess Viola]

Another Wine update today THE SAME ERROR.

Looking it up, apparently it is specifically the Debian/Ubuntu build of Wine 10.2.2 that's broken, which means it's broken on Mint too. So I gotta downgrade to 10.1, which works.

 

[Outdated]

I've found it most effective when having to purge Wine to first use the "wine uninstaller" in the terminal to first purge all the windows apps....

No! No no no.

Your Wine Prefix (fake windows drive) is completely independent from Wine itself. You don't need to create that new when installing or upgrading Wine. My wine prefixes have followed me for years now across many different computers and many different versions of Wine.

If the wine prefix ain't broke don't fix it.

 

[Judge]

No! No no no.

Your Wine Prefix (fake windows drive) is completely independent from Wine itself. You don't need to create that new when installing or upgrading Wine. My wine prefixes have followed me for years now across many different computers and many different versions of Wine.

If the wine prefix ain't broke don't fix it.

I've used the Wine uninstaller countless times without incident. But it doesn't matter given how thorough I go about purging a Wine install if it goes wrong for some reason. A safety precaution to make sure I don't contaminate one version with another. But I'm talking about only using it to purge applications. Not Wine itself.

I've also used the most conventional methods of uninstalling a Windows app clicking the icon pertinent to the file. In most cases it works identically to what the wine uninstaller can do for individual Windows applications running inside Wine.

For purging Wine in its entirety, yes I used the Synaptic Package Manager. Never had a problem doing that either.

As for updating Wine, that's an automatic process with Linux Mint, done through the update manager. I just select whether or not to upgrade. Nothing more.

 

[Outdated]

I've also used the most conventional methods of uninstalling a Windows app clicking the icon pertinent to the file. In most cases it works identically to what the wine uninstaller can do for individual Windows applications running inside Wine.

Yes, it works very similarly to how it would in Windows except that it usually leaves you with a dead desktop link and icon. But you only need to do that if you want to get rid of a specific program.

Install Wine, or upgrade it or downgrade it, but you don't have to do anything to the Wine Prefix. The two are completely independent from each other. So when you try a new operating system you don't have to reinstall your Phtoshop 5.5 all over again, you simply copy and paste your .wine folder from the old drive in to the new new drive and create desktop links for the programs you want to access.

 

[Judge]

Yes, it works very similarly to how it would in Windows except that it usually leaves you with a dead desktop link and icon. But you only need to do that if you want to get rid of a specific program.

That's what you got wrong. I only use the Wine Uninstaller to delete Windows programs (Photoshop 5.5, Photo Tools, Xenofex 1.0). Not Wine itself. Though when I did purge it through the Synaptic Package Manager, reinstalling it has never been a problem either.

Install Wine, or upgrade it or downgrade it, but you don't have to do anything to the Wine Prefix. The two are completely independent from each other. So when you try a new operating system you don't have to reinstall your Phtoshop 5.5 all over again, you simply copy and paste your .wine folder from the old drive in to the new new drive and create desktop links for the programs you want to access.

After so much grief with Wine and Photoshop, I finally came to understand why at times installing Photoshop 5.5 wouldn't function after installing Wine.

It has nothing to do with Wine, and everything to do with the options I chose in installing Photoshop, apart from the need to preinstall ICC profiles for Linux and configure it to my monitor. And to skip the option of installing ICC profiles using Photoshop altogether.

Without a monitor pre-configured with a Linux ICC profile, it just causes installing Photoshop to either hang, or be unable to utilize color profiles which makes Photoshop worthless with inaccurate colors translated.

 

[Outdated]

It has nothing to do with Wine, and everything to do with the options I chose in installing Photoshop, apart from the need to preinstall ICC profiles for Linux and configure it to my monitor. And to skip the option of installing ICC profiles using Photoshop altogether.

This is why you don't uninstall and reinstall every time. Once you've got a profile set up that works the way you like it you don't change that profile, you make a copy of it in a safe place and every time you reinstall Wine or try out a new OS you just copy that profile in to your home folder and you're back in business.

The colour profiles will need to be installed in Linux again but you don't need to mess with your Photoshop installation.

I play a lot of Windows games, spread across 4 different profiles customised differently for different use scenarios. All up I probably have more than 30 games installed but rarely put in desktop links to them unless I'm going to play all the time. Having to reinstall all of them from scratch every time there was a Wine update would be ridiculous.

Every time I set up a new system those wine profiles get copied across to my new home folder and I'm immediately back playing my games again. You do not need to uninstall and reinstall everything, you just copy the old profile in and go back to using it.

 

[Judge]

This is why you don't uninstall and reinstall every time. Once you've got a profile set up that works the way you like it you don't change that profile, you make a copy of it in a safe place and every time you reinstall Wine or try out a new OS you just copy that profile in to your home folder and you're back in business.

The colour profiles will need to be installed in Linux again but you don't need to mess with your Photoshop installation.

You're preaching to the choir.

But some of what I posted is not just a matter of installing Wine or Photoshop, but when I also had to reinstall the entire OS for unrelated reasons. Something I did many times in pursuit of why the system was randomly freezing.

Sure, once I get a profile set up correctly, any modifications can screw it all up. Forcing me not to reinstall the ICC profiles, but rather to reinstall Photoshop alone. I figured that out some time back...

The real key is simply never to change an ICC profile configured for your monitor, as well as the color profile initially created in Photoshop. When that used to happen, I mistakenly thought it was a Wine issue when it wasn't.

No need to save the profile. Stuff I committed to memory long ago. (Adobe RGB 1998) Besides, it's easy enough to configure, as long as you download all the ICC profiles through Linux first, and then configure them for your monitor.

Making it all about the sequence of installing it- not the data itself. Once I figured that out, I was good to go.

Though as a former printer, I can see the value you place in saving a profile, given you may use several as opposed to just one that I need. That I get.

 

[Outdated]

I've found it most effective when having to purge Wine to first use the "wine uninstaller" in the terminal to first purge all the windows apps you are running in accordance with windows uninstallers.

This is the specific part of your post I was saying is not correct. You do not "uninstall" your windows programs and then reinstall them. It's a pointless exercise that will not provide any benefits and often just creates more frustration when things don't work as they should.

Upgrading or downgrading your Wine installation does not make any alterations to your .wine folder in any way shape or form. One of my profiles (.winewin98) has been in continuous use across many Linux installations and many different Wine versions since 2014.

 

[Judge]

This is the specific part of your post I was saying is not correct. You do not "uninstall" your windows programs and then reinstall them. It's a pointless exercise that will not provide any benefits and often just creates more frustration when things don't work as they should.

You misunderstood me. I didn't use the Wine Uninstaller only to uninstall and reinstall a Windows program. I just did that as part of the process of uninstalling everything including Wine. In the event of a "total" uninstall. But I made a point of uninstalling the applications first, before uninstalling Wine. Just a matter of sequence.

Then I would reinstall Wine, and once it was up and running I would install the three Windows programs I use. But as I said in the course of doing all this, I came to realize that it wasn't Wine in the first place, but rather an ICC profile issue between Linux and Photoshop.

Having figured all this out, there's not much likelihood of having to reinstall Photoshop or Wine at this point in time. Not unless there's evidence of file corruption...which in the event a total uninstall might be warranted.

 

[Outdated]

Then I would reinstall Wine, and once it was up and running I would install the three Windows programs I use.

That's the part I'm saying is pointless and wasted effort.

Reinstall Wine, then simply copy your .wine folder from your other drive in to the new one. Or simply continue using the old one. You have no need to uninstall then reinstall photoshop ever once it's set up and running correctly.

There is no information stored inside the wine profile that is pertinent or relevant to any particular version of Wine. Uninstalling and reinstalling Wine does not touch or even look at that folder in any way shape or form. The two operate completely independently from each other.

 

[Judge]

That's the part I'm saying is pointless and wasted effort.

Reinstall Wine, then simply copy your .wine folder from your other drive in to the new one. Or simply continue using the old one. You have no need to uninstall then reinstall photoshop ever once it's set up and running correctly.

Yes, I already know that.

It works fine assuming you are absolutely certain that there's nothing wrong with Wine or Photoshop. A method I used early into my Linux and Wine days with great success. (LOL..I think I still have an Adobe folder archived for just that purpose.) Something I discovered by accident, in desperation in my early days of Linux!

However it's another matter when I'm completely uncertain of what are the problems and where they reside. When I feel a need to install all of it in a prudent manner, taking no unnecessary shortcuts. Especially if it involves troubleshooting on a much broader perspective than just a case of Wine or Photoshop.

Particularly in the case of discovering that a major problem started with configuring my monitor with the right ICC profile. In which case transplanting a correctly configured Wine or Adobe subdirectory would not have solved the problem. When I could have cut and pasted such subdirectories into my home directory over and over and Photoshop still would not have worked.

That said, I don't think of myself in terms of doing things the right way or the wrong way.

I have only one choice in the matter- the OCD way. It permeates all my thought processes.

 

[Princess Viola]

I just want to make note that, for some reason, the update worked again later.

So.

Yeah.

I didn't even do any fixes, but it just installed fine.

 

[Judge]

Decided to migrate my hardware back to my preferred PC case with better airflow and dust filtering.

The only difference being the smaller case required an mATX motherboard. Same manufacturer, same chipset, though I got a little bonus in the form of an updated BIOS. More current than on my ATX board that had my "Sleeper" PC. Though I had to learn a somewhat different BIOS setup with the mATX motherboard. I survived...

Great to be able to use my exact same removable drives with three versions of Linux. With no software modifications required. Linux Mint 22.0, 22.1 and Pop!OS22.04 all running fine. My "Icy Dock" removable SSD tray is at the bottom of the case.

Note the enormous frontal fan is 180mm while the rear exhaust fan is 120mm. -Positive airflow. Unfortunately the fan is DC and not PWM. I think I'm going to buy the PWM counterpart that Silverstone makes. Note as well the side of frontal case grill. A mesh filter covering the grill slides out for easy cleaning. (On the other case I had to remove the entire front of the case just to clean a 120mm frontal fan.)

And no, you aren't hallucinating. The motherboard is in fact, inverted in this case.

 

[Judge]

Decided to migrate my hardware back to my preferred PC case with better airflow and dust filtering.

The only difference being the smaller case required an mATX motherboard. Same manufacturer, same chipset, though I got a little bonus in the form of an updated BIOS. More current than on my ATX board that had my "Sleeper" PC. Though I had to learn a somewhat different BIOS setup with the mATX motherboard. I survived...

Great to be able to use my exact same removable drives with three versions of Linux. With no software modifications required. Linux Mint 22.0, 22.1 and Pop!OS22.04 all running fine. My "Icy Dock" removable SSD tray is at the bottom of the case.

Note the enormous frontal fan is 180mm while the rear exhaust fan is 120mm. -Positive airflow. Unfortunately the fan is DC and not PWM. I think I'm going to buy the PWM counterpart that Silverstone makes. Note as well the side of frontal case grill. A mesh filter covering the grill slides out for easy cleaning. (On the other case I had to remove the entire front of the case just to clean a 120mm frontal fan.)

And no, you aren't hallucinating. The motherboard is in fact, inverted in this case.

Initially I successfully booted up three existing SSDs with three different distros, all originally created on my other "Sleeper" system with a similar motherboard of the same make and chipset. As was suggested in a few articles I read online. Most definitely NOT something you could ever do with Windows. However while everything appeared to run quite well, after a series of Linux Mint updates I elected to examine both my log file, and system reports just to see if there were any irregularities in transferring hard drives to a different motherboard.

Oops! Tilt! Saw a whole lot of comments all implying inconsistencies of one kind or another. Not knowing whether they were pedantic and pissy developer comments, I elected to stop and simply restore my beloved smaller case to a perfectly running LGA 1155 Intel i5-3570 system.

Clearly the prudent thing was to have reinstalled Linux Mint 22.0 from scratch. Which obviously I elected not to do at this time. Easier just to undo everything I did in a few hours than rebuild another OS I have done so many times that usually takes me a day+ to conclude in not only installing the OS itself, but to install and optimally set up so many applications.

I should have listened to my gut, considering the two motherboards had different version dates of their respective BIOS. Which might have explained how the OS didn't like an SSD created on one motherboard, to be used on another motherboard.

So...."back to the drawing board". However I learned other stuff along the way, so such an experience was not a total loss of time or effort.

I will probably rebuild my smaller case with the new motherboard, but do so completely independently of my primary "Sleeper" computer. Requiring in the future to purchase DDR4 memory, a CPU and CPU Heatsink rather than to poach them from my other computer.

Lesson to be learned: Don't transfer so many main components from one mother board to another unless you have to. Otherwise during the process, you suddenly realize if something terrible goes wrong, you have no functional computers, let alone access to the Internet.