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

ERROR: Couldn't create $HOME/.irssi directory #910

Closed
joekendal opened this issue Aug 12, 2018 · 4 comments
Closed

ERROR: Couldn't create $HOME/.irssi directory #910

joekendal opened this issue Aug 12, 2018 · 4 comments
Milestone

Comments

@joekendal
Copy link

joekendal commented Aug 12, 2018

$ irssi
** (irssi:14528): ERROR **: <timestamp>: Couldn't create $HOME/.irssi directory
Trace/breakpoint trap (core dumped)

I can manually bypass this error however:

$ mkdir $HOME/.irssi
@dequis
Copy link
Member

dequis commented Aug 13, 2018

Why did you close this? Did you figure it out?

@joekendal
Copy link
Author

@dequis the SSL timeouts were caused by my firewall. The error creating the irssi directory was only resolved by manually creating the .irssi folder. But still this is strange that it cannot do so by the program itself, so is maybe a bug that should be looked into. For reference, I encountered this bug on Ubuntu 18.04 with the upstream irssi release

@bmeh
Copy link

bmeh commented Aug 25, 2018

The core dump file could be useful. To find out which directory it is being dumped to: cat /proc/sys/kernel/core_pattern.

@dequis
Copy link
Member

dequis commented Sep 4, 2018

Quoting myself on #925:

IMO we'll never know what happened there, and it's not very important either, but for the next time we can show the actual reason the mkdir failed.

The fact that it aborts and generates coredump is a bit awkward but g_error really is the handiest way to show this sort of thing and quit, so that's fine I think.

So, closing this. If it ever happens again we'll know why.

@dequis dequis closed this as completed Sep 4, 2018
@ailin-nemui ailin-nemui added this to the 1.2.0 milestone Jun 26, 2019
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

4 participants