Ask Your Question

wingpro8_8.0.2-0_amd64.deb does not install on Debian 10

asked 2021-08-08 05:44:20 -0600

pymike gravatar image

updated 2021-08-08 06:55:20 -0600

mike@t430sDebianBackup:~/Downloads/Wing8$ wing8
<output deleted>
OSError: cannot open shared object file: No such file or directory

mike@t430sDebianBackup:~/Downloads/Wing8$ uname -a
Linux t430sDebianBackup 4.9.0-8-amd64 #1 SMP Debian 4.9.144-3.1 (2019-02-19) x86_64 GNU/Linux

mike@t430sDebianBackup:~/Downloads/Wing8$ cat /etc/debian_version 
edit retag flag offensive close merge delete


Is the libxcb package installed? It's actually split into many sub-packages and I'm not sure off-hand which you need (see for example ). I think this is a package that is renamed on different Linux distributions and we may have removed our dependency for it to solve problems installing on other systems. 'm guessing that it'll work if you install the package that provides libcxb-util and any others Wing uses.

Wingware Support gravatar image Wingware Support  ( 2021-08-08 07:11:17 -0600 )edit

mike@t430sDebianBackup:~/.local/share$ sudo apt list --installed |grep libxcb |grep util

libxcb-render-util0/stable,now 0.3.9-1+b1 amd64 [installed,automatic]
libxcb-util0/stable,now 0.3.8-3+b2 amd64 [installed]
pymike gravatar image pymike  ( 2021-08-08 07:13:48 -0600 )edit

mike@t430sDebianBackup:~/.local/share$ sudo apt install libxcb-util Reading package lists Done Building dependency tree
Reading state information Done E: Unable to locate package libxcb-util

pymike gravatar image pymike  ( 2021-08-08 07:14:46 -0600 )edit

Yes, the package is not called libcxb-util. See for all the packages associated with libcxb. I'm not sure which you need or why it's spilt up like this. There does seem to be one called libcxb-util1 that I see mentioned in a few places so maybe that is it.

Wingware Support gravatar image Wingware Support  ( 2021-08-08 07:25:03 -0600 )edit

libxcb-dri2-0:amd64 1.13.1-2
libxcb-dri2-0-dev:amd64 1.13.1-2
libxcb-dri3-0:amd64 1.13.1-2
libxcb-dri3-dev:amd64 1.13.1-2
libxcb-glx0:amd64 1.13.1-2
libxcb-glx0-dev:amd64 1.13.1-2
libxcb-icccm4:amd64 0.4.1-1.1 libxcb-image0:amd64 0.4.0-1+b2 libxcb-keysyms1:amd64 0.4.0-1+b2 libxcb-present-dev:amd64 1.13.1-2
libxcb-present0:amd64 1.13.1-2
libxcb-randr0:amd64 1.13.1-2
libxcb-randr0-dev:amd64 1.13.1-2
libxcb-render-util0:amd64 0.3.9-1+b1 libxcb-render0:amd64 1.13.1-2
libxcb-render0-dev:amd64 1.13.1-2
libxcb-shape0:amd64 1.13.1-2
libxcb-shape0-dev:amd64 1.13.1-2
libxcb-shm0:amd64 1.13.1-2
libxcb-shm0-dev:amd64 1.13.1-2
libxcb-sync-dev:amd64 1.13.1-2
libxcb-sync1:amd64 1.13.1-2
libxcb-util0:amd64 0.3.8-3+b2 libxcb-xfixes0:amd64 1.13.1-2
libxcb-xfixes0-dev:amd64 1.13.1-2
libxcb-xinerama0:amd64 1.13.1-2
libxcb-xinput0:amd64 1.13.1-2
libxcb-xkb1:amd64 1.13.1-2
libxcb-xtest0:amd64 1.13.1-2 ...(more)

pymike gravatar image pymike  ( 2021-08-08 09:11:37 -0600 )edit

1 Answer

Sort by ยป oldest newest most voted

answered 2021-08-08 20:04:10 -0600

For the record for others that run into this: As noted in above comments, installing all the libxcb* packages solves it. Most likely not all are needed, but it's unclear which of those packages provides the libraries that Wing needs and may just be easier to install them all.

edit flag offensive delete link more


Also, I should note that the root problem here is that our .deb cannot depend on libxcb packages because different debian-based Linux distributions name those packages differently. Fixing it for this case would break it for others. This is unfortunately a lack of standardization where distributions essentially assume that everything is repackaged for each dist and version, something that isn't really possible for us to do.

Wingware Support gravatar image Wingware Support  ( 2021-08-08 20:07:54 -0600 )edit

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Question Tools



Asked: 2021-08-08 05:44:20 -0600

Seen: 912 times

Last updated: Aug 09