libqtk3-nocsd.so.0 Error message & No networking

Open forum for end-user questions about Wine. Before asking questions, check out the Wiki as a first step.
Forum Rules
Locked
MythX
Level 1
Level 1
Posts: 8
Joined: Sun Dec 30, 2018 10:31 am

libqtk3-nocsd.so.0 Error message & No networking

Post by MythX » Mon Dec 31, 2018 9:52 am

OK, so thought I had this problem solved, but apparently I was wrong.

My setup:
Ubuntu 18.04 x64
Wine 3.0.4
Winetricks 20181203-next
WinePrefix is x86

The error shows up repeatedly, here's an example that also shows the networking problems I'm having. I don't know if the two are related, but they show up together.

Code: Select all

user@mycomp ~/winmor/drive_c $ WINEPREFIX=~/winmor wine ~/winmor/drive_c/windows/system32/cmd.exe 
ERROR: ld.so: object '/usr/lib/x86_64-linux-gnu/libgtk3-nocsd.so.0' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS64): ignored.
ERROR: ld.so: object '/usr/lib/x86_64-linux-gnu/libgtk3-nocsd.so.0' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS64): ignored.
Microsoft Windows 5.0.2195 (3.0.4)

C:\>ipconfig /all
ERROR: ld.so: object '/usr/lib/x86_64-linux-gnu/libgtk3-nocsd.so.0' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS64): ignored.
    Hostname. . . . . . . . . . . . . : mycomp
    Node type . . . . . . . . . . . . : Hybrid
    IP routing enabled. . . . . . . . : No

Ethernet adapter lo

    Connection-specific DNS suffix. . : 
    Description . . . . . . . . . . . : lo
    Physical address. . . . . . . . . : 
    DHCP enabled. . . . . . . . . . . : No
    IPv4 address. . . . . . . . . . . : 127.0.0.1
    IPv6 address. . . . . . . . . . . : ::1
    Default gateway . . . . . . . . . : 

Ethernet adapter eth0

    Connection-specific DNS suffix. . : mydomain.net
    Description . . . . . . . . . . . : eth0
    Physical address. . . . . . . . . : 00-21-9B-EE-80-A3
    DHCP enabled. . . . . . . . . . . : No
    IPv4 address. . . . . . . . . . . : 192.168.1.100
    Default gateway . . . . . . . . . : 

Ethernet adapter wlan0

    Connection-specific DNS suffix. . : mydomain.net
    Description . . . . . . . . . . . : wlan0
    Physical address. . . . . . . . . : 00-23-4D-B3-3B-8E
    DHCP enabled. . . . . . . . . . . : No
    IPv4 address. . . . . . . . . . . : 192.168.0.81
    IPv6 address. . . . . . . . . . . : fe80::223:4dff:feb3:3b8e%3
    Default gateway . . . . . . . . . : 192.168.0.101


C:\>ping 192.168.0.81
ERROR: ld.so: object '/usr/lib/x86_64-linux-gnu/libgtk3-nocsd.so.0' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS64): ignored.
00ae:fixme:ping:main this command currently just sleeps based on -n parameter

C:\>
Most commands execute just fine without error (internal and external alike). It's these networking commands that seem to trigger the error.

Below you can see the library in question. What I'm not clear on is the permissions of this file. I thought the uppercase "S" was for directories, not files.

Code: Select all

user@mycomp /usr/lib/x86_64-linux-gnu $ ls -la | grep libgtk3-nocsd.so.0
-rwSr--r--   1 root root    26616 Mar  2  2018 libgtk3-nocsd.so.0
user@mycomp /usr/lib/x86_64-linux-gnu $ 
I'm not sure what else I could add to help. Ultimately, it's the networking I'm trying to fix. The application I'm having troubles with is WinLink Express: https://winlink.org/WinlinkExpress. It appears to work fine, with the exception of the network issue and a single oddly placed dropdown list.

Any suggestions?

Thanks

MythX
Level 1
Level 1
Posts: 8
Joined: Sun Dec 30, 2018 10:31 am

Re: libqtk3-nocsd.so.0 Error message & No networking

Post by MythX » Mon Dec 31, 2018 2:31 pm

OK, so I think I've determined that the ld.so error is unrelated to my networking troubles. I rebuilt my wineprefix and now networking is mostly working. I still get the ld.so error, but I don't think its causing me any problems.

Now, networking is mostly working because the WinLink application that I'm using can connect to the internet via telnet and transfer data no problem. It also connects to another process (also Wine) via a TCP listener, this works fine as well.
There is another feature where WinLink needs to fetch data (probably, just a port 80 fetch). That's not working. At this point, I can't tell if I'm looking at a Wine or WinLink issue though.

Thanks

Locked