Debian/Ubuntu 10.3 packages are broken; do not install

[mainliner]

It pains me to report that Debian's 10.3 packages appear to be broken.

I couldn't even run winecfg, I tried to remove and reinstall but wine would not work at all. I downgraded to 10.1 and winecfg and all apps worked perfectly again. For those coming here to see if this is a problem for others this is the command line I used to roll back:

Code: Select all

sudo apt install wine{hq,}-staging=10.1* wine-staging-{amd64,i386}=10.1*

[dimesio]

I tested the packages myself in Debian 12 and Ubuntu 20.04 and they worked, but those were clean installs. Some users have reported problems upgrading from 10.1 to 10.3; running --fix-broken install, or uninstalling the old version before installing the new one, should fix that.

If that doesn't work, post terminal output from trying to run winecfg.

[mainliner]

I hope I'm doing this correctly:

Code: Select all

sudo apt --purge remove wine*

Code: Select all

rm -r .wine
rm .config/menus/applications-merged/wine*
rm -r .local/share/applications/wine
rm .local/share/icons/????_*.xpm

The last one was not found (antiX Linux, based on Debian nosytemd)

Code: Select all

sudo apt update
sudo apt autoclean
sudo apt clean
sudo apt autoremove

Finally, because I've used Windows, I rebooted.

Code: Select all

sudo apt install winehq-staging

Which installed wine-staging-amd64 amd64 10.3~bookworm-1

Code: Select all

$ winecfg
winecfg
wine: created the configuration directory '/home/spaceman/.wine'

That's it. No more. Nothing else.

I then killed the winecfg, wine-staging/lib/wine/i386-unix/wine winecfg and wineserver processes and downgraded to 10.1 again...et voila all working.

[mainliner]

I tried a fresh install on freshly deployed distro with the same result. This is difficult to troubleshoot as there is no terminal output whatsoever, winecfg simply does not launch...

10.1 is fine.

[dimesio]

Code: Select all

sudo apt install winehq-staging

Which installed wine-staging-amd64 amd64 10.3~bookworm-1

It should have also installed wine-staging_10.3~bookworm-1_amd64.deb and wine-staging-i386_10.3~bookworm-1_i386.deb. Are they installed?

[mainliner]

Yes, to wine-staging_10.3~bookworm-1_amd64.deb

Code: Select all

Preparing to unpack .../wine-staging-amd64_10.4~bookworm-1_amd64.deb ...
Unpacking wine-staging-amd64 (10.4~bookworm-1) ...
Selecting previously unselected package wine-staging.
Preparing to unpack .../wine-staging_10.4~bookworm-1_amd64.deb ...
Unpacking wine-staging (10.4~bookworm-1) ...
Selecting previously unselected package winehq-staging.
Preparing to unpack .../winehq-staging_10.4~bookworm-1_amd64.deb ...
Unpacking winehq-staging (10.4~bookworm-1) ...
Setting up wine-staging-amd64 (10.4~bookworm-1) ...
Setting up wine-staging (10.4~bookworm-1) ...
Setting up winehq-staging (10.4~bookworm-1) ...

Er...

Code: Select all

sudo apt install wine-staging-i386_10.4~bookworm-1_i386.deb
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
E: Unable to locate package wine-staging-i386_10.4~bookworm-1_i386.deb

Do we have a candidate for cause? As you can see about the problem is present with 10.4 too. I stress that rolling back to 10.1 is a workaround.

[mainliner]

Ah...

Code: Select all

Preparing to unpack .../wine-staging-i386_10.1~bookworm-1_i386.deb ...
Unpacking wine-staging-i386:i386 (10.1~bookworm-1) over (10.4~bookworm-1) ...
Selecting previously unselected package wine-staging-amd64.
Preparing to unpack .../wine-staging-amd64_10.1~bookworm-1_amd64.deb ...
Unpacking wine-staging-amd64 (10.1~bookworm-1) ...
Selecting previously unselected package wine-staging.
Preparing to unpack .../wine-staging_10.1~bookworm-1_amd64.deb ...
Unpacking wine-staging (10.1~bookworm-1) ...
Selecting previously unselected package winehq-staging.
Preparing to unpack .../winehq-staging_10.1~bookworm-1_amd64.deb ...
Unpacking winehq-staging (10.1~bookworm-1) ...
Setting up wine-staging-amd64 (10.1~bookworm-1) ...
Setting up wine-staging-i386:i386 (10.1~bookworm-1) ...
Setting up wine-staging (10.1~bookworm-1) ...
Setting up winehq-staging (10.1~bookworm-1) ...

Crap, I've broken 10.1 now.

[dimesio]

Code: Select all

E: Unable to locate package wine-staging-i386_10.4~bookworm-1_i386.deb

That package is definitely in our repository: https://dl.winehq.org/wine-builds/debia ... 1_i386.deb

Did you follow the instructions on https://gitlab.winehq.org/wine/wine/-/w ... ian-Ubuntu to enable i386 architecture and add the repository?

[mainliner]

Did you follow the instructions on https://gitlab.winehq.org/wine/wine/-/w ... ian-Ubuntu to enable i386 architecture and add the repository?

Possibly...since it works flawlessly with 10.1...
and of course:

Code: Select all

Preparing to unpack .../winehq-staging_10.4~bookworm-1_amd64.deb ...
Unpacking winehq-staging (10.4~bookworm-1) ...

Seems to suggest the repo is installed correctly...

[mainliner]

Something has changed though...

Code: Select all

$ sudo apt install winehq-staging 
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
winehq-staging is already the newest version (10.4~bookworm-1).
You might want to run 'apt --fix-broken install' to correct these.
The following packages have unmet dependencies:
 wine-staging : Depends: wine-staging-i386 (= 10.1~bookworm-1)
                Depends: wine-staging-amd64 (= 10.1~bookworm-1) but 10.4~bookworm-1 is to be installed
 winehq-staging : Depends: wine-staging (= 10.4~bookworm-1)
E: Unmet dependencies. Try 'apt --fix-broken install' with no packages (or specify a solution).

So I fixed the broken packages:

Code: Select all

$ sudo apt --fix-broken install
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Correcting dependencies... Done
The following additional packages will be installed:
  wine-staging
The following packages will be upgraded:
  wine-staging
1 upgraded, 0 newly installed, 0 to remove and 4 not upgraded.
3 not fully installed or removed.
Need to get 0 B/3,887 kB of archives.
After this operation, 37.9 kB of additional disk space will be used.
Do you want to continue? [Y/n] Y
(Reading database ... 130076 files and directories currently installed.)
Preparing to unpack .../wine-staging_10.4~bookworm-1_amd64.deb ...
Unpacking wine-staging (10.4~bookworm-1) over (10.1~bookworm-1) ...
Setting up wine-staging-amd64 (10.4~bookworm-1) ...
Setting up wine-staging-i386:i386 (10.4~bookworm-1) ...
Setting up wine-staging (10.4~bookworm-1) ...
Setting up winehq-staging (10.4~bookworm-1) ...
Processing triggers for man-db (2.11.2-2) ...
Processing triggers for desktop-file-utils (0.26-1) ...

I tried this to confirm:

Code: Select all

$ sudo apt install wine-staging-i386
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
wine-staging-i386:i386 is already the newest version (10.4~bookworm-1).
0 upgraded, 0 newly installed, 0 to remove and 4 not upgraded.

But sadly this how wine operates currently (except for pre-10.2 version ofc):
https://e.pcloud.link/publink/show?code ... Cps4SdhurV

[dimesio]

Due to changes to wine in 10.2, the structure of the packages had to be changed, and trying to upgrade directly from 10.1 to a later version fails. The solution is to either remove 10.1 before installing the new version, or run apt --fix-broken install. https://bugs.winehq.org/show_bug.cgi?id=57859

Not installing the i386 package will definitely cause a broken install. From your last post, it appears that all four 10.4 packages were installed, but you are saying 10.4 still does not work at all for you, not even in a clean wineprefix. Is that correct?

Going back over this thread, I did notice this:

The last one was not found (antiX Linux, based on Debian nosytemd)

Our packages are built on and for the specific version of the target distro, and while they may work on derivative distros, are not guaranteed to do so. Please test on Debian.

[mainliner]

OK, give me a few hours and I'll run up a Debian installation and test install 10.4 out of the box. I did do this on an antiX install (I will also repeat this) with 10.3, but as reported this didn't work.

you are saying 10.4 still does not work at all for you, not even in a clean wineprefix. Is that correct?

Yes, simply running winecfg after (completely removing 10.1 and) freshly installing 10.4 running winecfg (with no existing ~/.wine) just halts with no terminal output. Also, i386 staging is installed:

Code: Select all

Setting up wine-staging-i386:i386 (10.4~bookworm-1) ...

Essentially antix Core is a GUI-less, stripped back Debian with no systemd. I haven't encountered an issue with wine thus far, but I'm certainly not ruling it out.

Thanks for your input mate.

If Debian works and antiX will not, I'll drag my sorry behind over to the antiX forum and see what those guys have to say. They're damn good and friendly lot.