CrossOver Support - Community Forums

Important Information These are community forums and not official technical support. If you need official support: Contact Us

CrossOver Linux
Discussion about CrossOver Linux

The following comments are owned by whoever posted them. We are not responsible for them in any way.

Back to Threads Reply to Thread

Arch Linux segmentation fault glibc 2.24-2

Hello! I use crossover at Arch. And today I've found I have a segfault on running crossover.

It's similar to https://www.codeweavers.com/support/forums/general/?t=26;mhl=143686;msg=143686#msg143686
I still can use installed software, but I can't run crossover.

I tried to find the reason for segfault:


define@cinder  ~  gdb python
GNU gdb (GDB) 7.12.1
Copyright (C) 2017 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-pc-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from python...(no debugging symbols found)...done.
(gdb) 
(gdb) set args /usr/bin/crossover 
(gdb) 
(gdb) 
(gdb) run
Starting program: /usr/bin/python /usr/bin/crossover 
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/usr/lib/libthread_db.so.1".
process 4858 is executing new program: /usr/bin/python2.7
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/usr/lib/libthread_db.so.1".
[New Thread 0x7fffe6eea700 (LWP 4865)]

Thread 1 "python2" received signal SIGSEGV, Segmentation fault.
0x00007ffff74b5446 in strlen () from /usr/lib/libc.so.6
(gdb) 
(gdb) 
(gdb) 
(gdb) bt
#0  0x00007ffff74b5446 in strlen () at /usr/lib/libc.so.6
#1  0x00007ffff7a871b9 in PyString_FromFormatV () at /usr/lib/libpython2.7.so.1.0
#2  0x00007ffff7ae7a08 in PyErr_Format () at /usr/lib/libpython2.7.so.1.0
#3  0x00007fffe43b0ee7 in  () at /usr/lib/python2.7/site-packages/sip.so
#4  0x00007fffd77c39a6 in initkdecore () at /usr/lib/python2.7/site-packages/PyKDE4/kdecore.so
#5  0x00007ffff7af203c in _PyImport_LoadDynamicModule () at /usr/lib/libpython2.7.so.1.0
#6  0x00007ffff7aeff81 in import_submodule () at /usr/lib/libpython2.7.so.1.0
#7  0x00007ffff7af0209 in load_next () at /usr/lib/libpython2.7.so.1.0
#8  0x00007ffff7af0ca8 in PyImport_ImportModuleLevel () at /usr/lib/libpython2.7.so.1.0
#9  0x00007ffff7ad2907 in builtin___import__ () at /usr/lib/libpython2.7.so.1.0
#10 0x00007ffff7a3c692 in PyObject_Call () at /usr/lib/libpython2.7.so.1.0
#11 0x00007ffff7ad4716 in PyEval_CallObjectWithKeywords () at /usr/lib/libpython2.7.so.1.0
#12 0x00007ffff7ad7552 in PyEval_EvalFrameEx () at /usr/lib/libpython2.7.so.1.0
#13 0x00007ffff7adae38 in PyEval_EvalFrameEx () at /usr/lib/libpython2.7.so.1.0
#14 0x00007ffff7adae38 in PyEval_EvalFrameEx () at /usr/lib/libpython2.7.so.1.0
---Type <return> to continue, or q <return> to quit---
#15 0x00007ffff7ade8dc in PyEval_EvalCodeEx () at /usr/lib/libpython2.7.so.1.0
#16 0x00007ffff7ade9e8 in PyEval_EvalCode () at /usr/lib/libpython2.7.so.1.0
#17 0x00007ffff7aeefc7 in PyImport_ExecCodeModuleEx () at /usr/lib/libpython2.7.so.1.0
#18 0x00007ffff7aef25e in load_source_module () at /usr/lib/libpython2.7.so.1.0
#19 0x00007ffff7aeff81 in import_submodule () at /usr/lib/libpython2.7.so.1.0
#20 0x00007ffff7af0209 in load_next () at /usr/lib/libpython2.7.so.1.0
#21 0x00007ffff7af0c63 in PyImport_ImportModuleLevel () at /usr/lib/libpython2.7.so.1.0
#22 0x00007ffff7ad2907 in builtin___import__ () at /usr/lib/libpython2.7.so.1.0
#23 0x00007ffff7a3c692 in PyObject_Call () at /usr/lib/libpython2.7.so.1.0
#24 0x00007ffff7ad4716 in PyEval_CallObjectWithKeywords () at /usr/lib/libpython2.7.so.1.0
#25 0x00007ffff7ad7552 in PyEval_EvalFrameEx () at /usr/lib/libpython2.7.so.1.0
#26 0x00007ffff7ade8dc in PyEval_EvalCodeEx () at /usr/lib/libpython2.7.so.1.0
#27 0x00007ffff7ade9e8 in PyEval_EvalCode () at /usr/lib/libpython2.7.so.1.0
#28 0x00007ffff7aeefc7 in PyImport_ExecCodeModuleEx () at /usr/lib/libpython2.7.so.1.0
#29 0x00007ffff7aef25e in load_source_module () at /usr/lib/libpython2.7.so.1.0
---Type <return> to continue, or q <return> to quit---
#30 0x00007ffff7aeff81 in import_submodule () at /usr/lib/libpython2.7.so.1.0
#31 0x00007ffff7af0209 in load_next () at /usr/lib/libpython2.7.so.1.0
#32 0x00007ffff7af0c63 in PyImport_ImportModuleLevel () at /usr/lib/libpython2.7.so.1.0
#33 0x00007ffff7ad2907 in builtin___import__ () at /usr/lib/libpython2.7.so.1.0
#34 0x00007ffff7a3c692 in PyObject_Call () at /usr/lib/libpython2.7.so.1.0
#35 0x00007ffff7ad4716 in PyEval_CallObjectWithKeywords () at /usr/lib/libpython2.7.so.1.0
#36 0x00007ffff7ad7552 in PyEval_EvalFrameEx () at /usr/lib/libpython2.7.so.1.0
#37 0x00007ffff7ade8dc in PyEval_EvalCodeEx () at /usr/lib/libpython2.7.so.1.0
#38 0x00007ffff7ade9e8 in PyEval_EvalCode () at /usr/lib/libpython2.7.so.1.0
#39 0x00007ffff7aeefc7 in PyImport_ExecCodeModuleEx () at /usr/lib/libpython2.7.so.1.0
#40 0x00007ffff7aef25e in load_source_module () at /usr/lib/libpython2.7.so.1.0
#41 0x00007ffff7aeff81 in import_submodule () at /usr/lib/libpython2.7.so.1.0
#42 0x00007ffff7af0209 in load_next () at /usr/lib/libpython2.7.so.1.0
#43 0x00007ffff7af0c63 in PyImport_ImportModuleLevel () at /usr/lib/libpython2.7.so.1.0
#44 0x00007ffff7ad2907 in builtin___import__ () at /usr/lib/libpython2.7.so.1.0
---Type <return> to continue, or q <return> to quit---
#45 0x00007ffff7a3c692 in PyObject_Call () at /usr/lib/libpython2.7.so.1.0
#46 0x00007ffff7ad4716 in PyEval_CallObjectWithKeywords () at /usr/lib/libpython2.7.so.1.0
#47 0x00007ffff7ad7552 in PyEval_EvalFrameEx () at /usr/lib/libpython2.7.so.1.0
#48 0x00007ffff7adae38 in PyEval_EvalFrameEx () at /usr/lib/libpython2.7.so.1.0
#49 0x00007ffff7ade8dc in PyEval_EvalCodeEx () at /usr/lib/libpython2.7.so.1.0
#50 0x00007ffff7ade9e8 in PyEval_EvalCode () at /usr/lib/libpython2.7.so.1.0
#51 0x00007ffff7af8efe in run_mod () at /usr/lib/libpython2.7.so.1.0
#52 0x00007ffff7afa1c1 in PyRun_FileExFlags () at /usr/lib/libpython2.7.so.1.0
#53 0x00007ffff7afb4e4 in PyRun_SimpleFileExFlags () at /usr/lib/libpython2.7.so.1.0
#54 0x00007ffff7b0dca0 in Py_Main () at /usr/lib/libpython2.7.so.1.0
#55 0x00007ffff7455291 in __libc_start_main () at /usr/lib/libc.so.6
#56 0x00005555555547ea in _start ()
(gdb) 
(gdb) 
 define@cinder  ~  ls -la  /usr/lib/libc.so.6                          
lrwxrwxrwx 1 root root 12 авг  6  2016 /usr/lib/libc.so.6 -> libc-2.24.so

I tried to downgrade glibc to glibc-2.23-5-x86_64, but the problem didn't resolve.

If I run crossover under root user it works fine.

I'm also running Arch, but Crossover launches just fine.

So if I were in your situation, I would:

1) Make sure your system is fully updated.

2) Make a temporary user to test Crossover with. If Crossover runs with root, but not with your user, there might be something in your user's config files that is screwing with things.

Testing with a new, clean and unprivileged user will tell you for sure if the problem lies in your account. I've had that happen with different software where the problem was strictly in for my user, but ran fine with root and a test user. If Crossover runs on my machine just fine, runs on your machine with root, I'm thinking this problem might be restricted to your user account.

I tried with the other user and I have the same segfault. The system is up to date.

Appreciate your help.

Well then, I'm confused...

The only thing I've seen suggested elsewhere that has solved weird problems is to remove Crossover (while leaving the bottles - you might want to archive them), and then reinstall. Somehow, reinstalling "solves" problems...

At this point, I'm curious if you used the AUR or the bin installer? Not that I know for a fact that that it makes the slightest bit of difference, but you never know.

Just one thing, I don't think running CrossOver as root is a good idea. CrossOver runs Windows programs that may be infected. I know it is rather unlikely that a Windows virus could do anything to your Linux system, but I would never take that risk...

A good testing would be if you have some free space to create a partition, or if not, using an old hard drive or even an external hard drive with a fresh new OS installation, just to test if a clean installation would solve the problem.

Hope this helps

Yeah running with root is not good, but he's not running Windows software with root, just Crossover itself.

J-P Simard wrote:

Well then, I'm confused...

The only thing I've seen suggested elsewhere that has solved weird
problems is to remove Crossover (while leaving the bottles - you
might want to archive them), and then reinstall. Somehow,
reinstalling "solves" problems...

At this point, I'm curious if you used the AUR or the bin installer?
Not that I know for a fact that that it makes the slightest bit of
difference, but you never know.

It was installed from aur. I removed it and tried the binary installation. The problem persists.

Silvio M Kozasa wrote:

Just one thing, I don't think running CrossOver as root is a good
idea. CrossOver runs Windows programs that may be infected. I know
it is rather unlikely that a Windows virus could do anything to your
Linux system, but I would never take that risk...

A good testing would be if you have some free space to create a
partition, or if not, using an old hard drive or even an external
hard drive with a fresh new OS installation, just to test if a clean
installation would solve the problem.

Hope this helps

As it's quite time consuming, I can't try it right now. And I tried to run crossover as root just in test cases. I don't do it during everyday use.

You keep screwing up my wonderful suggestions! 😅

Well, I don't know what's going on. I'll let this sit in my brain for a while, maybe I'll think of something else.

Right now, the last thought I have is about permissions. Maybe there's something on your system with funny file permissions, set in such a way that only root can access all necessary file and/or libraries. It's just a brain fart, and I'm not too sure where the problem could be exactly, but I'm thinking that such a thing could happen.

J-P Simard wrote:

You keep screwing up my wonderful suggestions! 😅

Well, I don't know what's going on. I'll let this sit in my brain
for a while, maybe I'll think of something else.

Right now, the last thought I have is about permissions. Maybe
there's something on your system with funny file permissions, set in
such a way that only root can access all necessary file and/or
libraries. It's just a brain fart, and I'm not too sure where the
problem could be exactly, but I'm thinking that such a thing could
happen.

I thought about permissions issue and I can't find anything unussual. I checked the permissions of libc:

 define@cinder  ~  ls -la /usr/lib/ | grep libc-2.24   
-rwxr-xr-x 1 root root  1951744 авг  6  2016 libc-2.24.so
lrwxrwxrwx 1 root root       12 авг  6  2016 libc.so.6 -> libc-2.24.so

Maybe with some python files, like /usr/lib/libpython2.7.so.1.0, which comes up often if the log above. Damn it, there has to be a way to get this to run...

what I have for libpython is:

lrwxrwxrwx   1 root root       19 21 déc 02:23 libpython2.7.so -> libpython2.7.so.1.0
-r-xr-xr-x   1 root root  2091000 21 déc 02:23 libpython2.7.so.1.0
lrwxrwxrwx   1 root root       20 16 jan 06:14 libpython3.6m.so -> libpython3.6m.so.1.0
-rwxr-xr-x   1 root root  3339080 16 jan 06:14 libpython3.6m.so.1.0
-rwxr-xr-x   1 root root     5888 16 jan 06:14 libpython3.so

I have the same permissions.

I'm stumped...

Sorry, but I really don't have anything else. My laptop, that does run Arch, didn't have Crossover on it so I installed it, and it runs. I don't even come close to reproducing the problem, so I would be hard pressed to find a solution.

Good luck!

I too am seeing a segfault while trying to install 16.1. In either an install or an upgrade case, there is a segfault at the end when cxtie is invoked, after which the install/upgrade is rolled back.

I am on gentoo with glibc-2.24-r1.

Edit - Upon further investigation it appears that the installation completes successfully if it is run as root. However running any installed apps (e.g. /opt/cxoffice/bin/crossover) as a non root user does fail with another segfault.

What if it is a permission problem, but with Crossover itself. Maybe some things don't get set properly on install.

I use the bin to install, as a user (not root, no system wide install) and for cxoffice my permissions are - drwxrwxrwx. Most of the files in ~/cxoffice/bin are set at -rwxr-xr-x. If the software runs under root, it has to be permissions. If it were a bigger problem it shouldn't run at all, root or not.

I too attempted install as a non root user, and upon completion the install tries to run cxtie right away, which immediately segfaults. Installation only completed as root.

Because it's a segfault I think it has to be a python lib, probably gtk, but I don't understand the significance of the root vs non root user.

I know none of us are on a supported distro, but maybe a support ticket would reveal something useful. Maybe the devs have seen this before and could tell where to look, short of an actual solution.

Ticket opened, Katie helping!

After upgrading to 16.1 and encountering the problem I do think I've managed to draw a boundary around the actual problem scope, and also get to a ~functional state.

Essentially this problem affects all of the Crossover apps and UIs when running as a non-root user. All the of the wine functions continue to work. So if you have established bottles things should continue to work within those bottles as they always have. But if for instance you want to create a new bottle or adjust the config of an existing bottle, you may run afoul of this segfault.

That said I was able to run the registration UI as root and get my registration credentials applied to my upgrade. After that all my bottles run as they should. So if others were having similar difficulty this might be a way to at least bypass that part of the problem.

You know, this sort of rings a bell. It really sounds like something that happened around CX14 or 15 for Ubuntu users. I know there were some forum questions about that... It might be worth looking for that.

Finally Crossover Support Team helped me with the following sollution:
"Based on the gdb stacktrace from your forum post, it does appear to be failing while trying to load kde libraries.

We only use kde libraries to detect proxy information. There is an option in CrossOver that can disable automatic proxy detection, and this would eliminate the use of kde libraries.

Please try adding this line to ~/.cxoffice/cxoffice.conf under the [CrossOver] section:

"ManualProxySettings" = "1"

You can then run this command to verify that the setting is being correctly picked up by CrossOver:

$ python2 -v /opt/cxoffice/lib/python/proxyinfo.py

It should print a bunch of import statements and then "Desktop environment: config". If it segfaults, the output may provide some hints."

1 to 21 of 21

Please Note: This Forum is for non-application specific questions relating to installation/configuration of CrossOver. All application-specific posts to this Forum will be moved to their appropriate Compatibility Center Forum.

CrossOver Forums: the place to discuss running Windows applications on Mac and Linux

CodeWeavers or its third-party tools process personal data (e.g. browsing data or IP addresses) and use cookies or other identifiers, which are necessary for its functioning and required to achieve the purposes illustrated in our Privacy Policy. You accept the use of cookies or other identifiers by clicking the Acknowledge button.
Please Wait...
eyJjb3VudHJ5IjoiVVMiLCJsYW5nIjoiZW4iLCJjYXJ0IjowLCJ0enMiOi01LCJjZG4iOiJodHRwczpcL1wvbWVkaWEuY29kZXdlYXZlcnMuY29tXC9wdWJcL2Nyb3Nzb3Zlclwvd2Vic2l0ZSIsImNkbnRzIjoxNzE1NzkzNDc5LCJjc3JmX3Rva2VuIjoiZFJVYmtzYjJUdXNyeEpyZSIsImdkcHIiOjB9