Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Import failure #2904

Closed
longoka opened this issue Apr 3, 2024 · 1 comment
Closed

Import failure #2904

longoka opened this issue Apr 3, 2024 · 1 comment

Comments

@longoka
Copy link

longoka commented Apr 3, 2024

Expected Behavior

I am working an a new M2 Mac running Gephi v0.10.1 (more details on my set-up below). I am attempting to open a *.gephi file that I created on my previous Mac (Intel chip) that was also running Gephi v 0.10.1. I expect this to render the network as before.

Current Behavior

Upon trying to open the Gephi file I receive this error:
gephi_fail_screen

Possible Solution

This is the first time I have attempted running Gephi on my new M2 Mac. System re-start did not work. I'm wondering if this can be resolved in the gephi.conf file. The file is store in a OneDrive directory, and I'm wondering if it is a permission issue (i.e., OneDrive is denying access to the file).

Long-time (and enthusiastic!) Gephi user and this is the first time I've ever encountered this error.

SOLVED: the issue was OneDrive; I'm embarrassed to admit that I'd neglected to confirm that my OneDrive files had all synced to my machine (they had not). Consequently, I was opening nothing when attempting to open the .gephi file. Once I downloaded the OneDrive file from the cloud to my machine, Gephi worked like a charm. Apologies for consuming any cycles.

Steps to Reproduce

Context

Your Environment

Product Version: Gephi 0.10.1 202301172018
Java: 11.0.17; OpenJDK 64-Bit Server VM 11.0.17+8
Runtime: OpenJDK Runtime Environment 11.0.17+8
System: Mac OS X version 13.6.4 running on aarch64; UTF-8; en_US (gephi)

@longoka
Copy link
Author

longoka commented Apr 4, 2024

See my 'SOLVED' comment above for the cause behind the issue and how I resolved it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant