Everything in emacs is fine but daemon doesn't work

I recently completed my emacs setup, everything works fine. but for some reason, the emacs daemon just freezes at startup when I run it outside emacs with emacs --daemon, so emacsclient doesn't work. But when started with server-start inside emacs, everything works fine Here's the output I'm getting, Did I do something wrong here? EDIT: It works now, it was selectric-mode that didn't work for the server for some reason. I'm so dumb https://preview.redd.it/0iayam2m4js91.png?width=737&format=png&auto=webp&s=b60cbf01c77df64877fedeb7a8a71ec18974fb9d

Did you try running it with the lucid toolkit, as stated in the error message?

Emacs clearly has not crashed, so that message (which is not an error message) is irrelevant. Edit in response to now-deleted reply: Switching to the lucid toolkit means building emacs from source, in case you didn't realise this. Not the "really simple command" you seem to believe -- certainly not when there's no reason to expect the OP had done that already.

Does `emacs -Q --daemon` work?

What's wrong with trying a really simple command that's right there in the error message, warning message, whatever? God save me from boring pedants...

Yes

[deleted]

yeah I tried it but same problem

Do you get an error message when you try to open a client?

Cool, so the problem is with your config, and you can start bisecting it to find out what causes it.

client does not open at all

Do you have any idea what can cause this, I can't figure it out :(

That's why you bisect -- it's a pretty efficient way to find out. (And no, I don't know what is causing it.)

Silently? Does the terminal hang or return without error? I recall that when clients initially failed to open on my own daemon setup there were error messages about sockets and such.

FOUND IT OUT!! i installed selectric-mode, maybe it crapped out for me :| Using my config works now :) Thanks for wasting time for me

The problem is fixed now, was just a simple package error

I had a similar problem yesterday and it was because of a recent bug in aggressive-indent-mode https://github.com/Malabarba/aggressive-indent-mode/pull/157 Maybe you also have aggressive-indent-mode activated (and open some file when in daemon mode that uses it but not when running normally)

> God save me from boring pedants... He is correct; even though he originally put in in an anal way; that is how he always approaches everyone, don't take it personally. Just ignore. He clarified in the edit. > What's wrong with trying a really simple command that's right there in the error message, warning message, whatever? No., you can not "try" that command. It is not a command; it is a tip to rebuild Emacs with different GUI toolkit (Lucid). That Emacs si build with Gtk, so that is why the warning is emitted. You can just ignore that; that bug is affecting normally very, very few, so most people can just ignore that.

I wish default Emacs builds would use Lucid by default. GTK's behavior (crashing out) with the Emacs daemon on X11 shutdown is more than a bit annoying. I have no idea if this persists with the Wayland crowd or what SystemD does here, but for my setup, I want my emacs client to survive my logging out in case I want to resume the next session.