-
Notifications
You must be signed in to change notification settings - Fork 259
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
module 'command_notify' has no attribute 'AVAILABLE' #375
Comments
This should be fixed in the latest version 2.1.0. I don't think Arch has updated it's repositories yet. It's a harmless message. If you want a really long story I can explain why. |
Ok, maybe I failed to identify the exact error message. Here's the full output of running terminator:
It exits with 0 almost immediately (0.57s) after launching. Is that caused by the same issue? |
Neither message should be fatal. What happens when you run This was all fixed in #264. Can you bug the arch linux maintainer to update to 2.1.0 if you're not running that? |
the process still exits with 0 right after. I'm running 2.0.1 though. |
Yeah, the fixes for those issues are all in 2.1.0 and it may require the fixes from #264 to work with the latest vte. I don't think so, but something seems to be shutting down the terminal right after it starts. can you maybe try running with an empty config and see if that fixes it: |
Yes, using an empty config file fixes it, but as stated earlier in the issue, I'm just very confused by why that's relevant as I have nothing special in my config file.
|
Your config is telling terminator to run I'm going to check this out further. |
for now you can remove the lines |
Honestly, I've gone back to the first version that worked on python3 and have confirmed that your config doesn't work on that one either. What version did you upgrade from? |
The customary way to start terminal in a specific directory is with the |
Describe the bug
After doing a system-wide update (
pacaur -Syyu
), terminator stops to function. Namely, it doesn't open anymore. When trying to launch from a console, the following error was produced:I have tried to load with an empty config file and it worked, but since I have no plugin turned on currently, I'm not sure how these are related.
To Reproduce
Steps to reproduce the behavior:
I'm not exactly sure.
Expected behavior
The program starts up normally.
Desktop (please complete the following information):
Additional context
Config file
The text was updated successfully, but these errors were encountered: