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
[Bug]: cider fails to launch #789
Comments
@coredev-uk mind looking into this? |
Run cider with the |
Can reproduce.
This doesn't appear don't do anything on Xorg; even if I change I get this when using the yarn start script
|
Cider without args Cider with args If i delete the config directory cider run again until i reboot the pc |
I found the the bug in my case is the "XAUTHORITY" Variable in the cider-config.json. Dont know why but the variable need to change every-time i reboot. If i delete the variable, cider start and change the Arg in the variable Reboot 1 Reboot 2 In Wayland and X11 is the same, always need to change. |
Verified.
|
The flatpak version seems to work fine thankfully, but it would be nice to have the git version with all the latest patches. Can someone fix this bug? |
This obviously still needs resolution but just to comment I maintain the Flatpak/Flathub release and it automatically builds off the latest builds from git the only delay to release is a Flathub mandated delay, When a new version gets built it doesn't get published until a scheduled activity runs putting all unpublished apps in the queue live it's usually every 3 hours. You can watch the status here |
The flatpak version does not work for me. |
To not clog up this issue page with potentially unrelated info if you join the Discord I can help you troubleshoot the Flatpak if you want to get that working. Just ping me in the support channel @ seby#0101 |
hi, could just delete the "XAUTHORITY" line plz and tell me if cider work, not delete the al cider-config.json file. tell me if you have the same bug as i. i think its a electron bug, but dont know. Edit 1 : Well i see cider store the "XAUTHORITY" inside the cider-config.json when its a token-cache value and change every reboot/login. "(...)that the error is that the application is unable to contact your X11 display because it does not have permission to do so because it's running as a different user. Applications need a "magic cookie" (secret token) in order to talk to the X11 server so that other processes on the system running under other users cannot intrude on your display, create windows, and snoop your keystrokes." More info in: https://www.x.org/archive/X11R6.8.1/doc/xauth.1.html |
Follow-up The only thing that has consistently worked is deleting the file. However, I'm suspecting this is a change on Apple's side as my Followed Artists feed has also vanished again
|
you need delete the XAUTH line everytime you reboot, before open cider. The XUATH token change everytime you reboot the pc. If this dont work for you; Can you upload the cider-config.json before and after delete plz?. |
Deleting the XAUTH line after login and before launch does, indeed, work
|
Hi i see the commit 0eb59d1 start the bug in linux platform. dont know why cider config needs store the "ENV" params |
with the last merge patch, fixes the Cider bug on window. Plz Close it |
Awesome. |
... |
Delete all cider folder config and try again. For my side, the xauth bug not happen anymore. Update cider from last commit and try |
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 7 days. |
Apologies for the lack of my assistance with this, glad it managed to get resolved. |
Describe the Bug
Failed to load module "appmenu-gtk-module"
when using the cider release in the aur,
[12:19:24.079] [info] [AppEvents] App started [12:19:26.001] [info] [PluginHandler] Loaded plugins: [ 'chromecast.js', 'discordrpc.js', 'lastfm.js', 'menubar.js', 'mpris.js', 'thumbar.js', 'webNowPlaying.js' ] Authorization required, but no authorization protocol specified Trace/breakpoint trap (core dumped)
when using the git version in the aur,
Steps to Reproduce
launch inn terminal on wayland on kde plasma
watch as the segmentation fault comes in
Environment Information
Anything else?
No response
Code of Conduct
The text was updated successfully, but these errors were encountered: