search

keithfancher / todo-indicator

Ubuntu app indicator for todo.txt-style todo lists
GNU General Public License v3.0
48 stars 8 forks source link

Only worked once! #7

Closed vexillia closed 2 months ago

vexillia commented 2 months ago

Installed as instructed. Launched OK but closed after a closed my terminal session. AFter that it wouldn't open.

Running xubuntu 22.04.

keithfancher commented 2 months ago

Hello, and thanks for filing this!

Launched OK but closed after a closed my terminal session.

This is actually "normal" behavior for starting applications from the terminal -- if you close the terminal, by default, it'll kill processes started by that terminal. There are a handful of ways to deal with this:

1. You can use & disown when you start an application from the terminal if you know you want to close that terminal session (and leave the app running), e.g.:

$ todo-indicator ~/todo.txt & disown

Now you can close your terminal and the indicator will stick around until you explicitly exit it.

2. You can also launch it with the "Run a command" dialog, rather than the terminal. This is usually Alt+F2. (I'm pretty sure it's the same in Xubuntu, though I haven't used Xubuntu in quite some time!)

3. A more long-term solution might be to stick the todo-indicator call in your "Startup Applications", assuming you want it to automatically start. (Depending on your $PATH setup, you might need to use the full path to todo-indicator in this or the above "Run a command" case.)

After that it wouldn't open.

This part's strange. If the application is closed, it should start again no problem. You might try checking your "System monitor" to see if it's lingering, and manually kill it. Alternatively, if you're comfortable with the command-line approach, something like:

$ ps x | grep todo-indicator
 207255 pts/1    SNl    0:00 /usr/local/bin/python ./todo-indicator sample-todo.txt
# And now you can kill the process with the above PID ^
$ kill 207255

Let me know if you run into issues! And thanks again for filing -- I think the docs could definitely be more clear about this. Will update!

vexillia commented 2 months ago

Thanks. Tried again and got this:

(todo-indicator:592082): dbind-WARNING **: 09:10:36.165: Couldn't connect to accessibility bus: Failed to connect to socket /root/.cache/at-spi/bus_0.0: Permission denied

keithfancher commented 2 months ago

That's just a warning from GTK (the underlying graphical toolkit for the app). It doesn't indicate a real problem ... for better or worse :D ... their messaging tends to be pretty annoying. (See this StackOverflow thread for a bit more info, if you're interested. But it's nothing to be concerned by.)

Is the application still not starting? Or is it starting, but just showing the above GTK warning?

If something is in a funky state with the desktop environment, the sledgehammer approach would be just to log out and log back in, or even to restart your computer.

vexillia commented 2 months ago

Blizted everything now working.

keithfancher commented 2 months ago

Awesome! Glad to hear it :tada: