Open HighCommander4 opened 6 years ago
Interestingly, until recently this used to work. I'm not sure how or why the behaviour changed.
In particular, I'm not seeing any recent updates to the Tomboy package in the Debian package tracker that might have brought this change of behaviour, making this all the more weird.
I wonder if rather than see Tomboy shut down, you are seeing a crash. Starting tomboy from the commandline may give you a hint. Either way, I'd consider upgrading tomboy. My Ubuntu 16.04 offers Tomboy 1.15.6 in its repo.
Starting tomboy from the commandline may give you a hint.
Curiously, when I start it from the command line, it doesn't open a window at all. It just hangs.
Either way, I'd consider upgrading tomboy. My Ubuntu 16.04 offers Tomboy 1.15.6 in its repo.
As mentioned, I'm running Debian 9, where the latest version offered is 1.14.1 (I checked the backports repository as well). Do you have a suggestion for where to obtain the newer version from?
I should note that this issue happens one of my machines running Debian 9, but not another. So I think it's indeed likely that it's just crashing on the one machine for some reason.
This just started happening on another one of my Debian 9 machines. I just upgraded the kernel from 4.9 to 4.14, I wonder if that is related...
I just upgraded the kernel from 4.9 to 4.14, I wonder if that is related...
Doesn't seem that way:
So... rebooting fixed the problem? But what caused it? Really weird...
I should clarify that when the problem occurs, Tomboy does not create a system tray icon at all. So I don't think the problem occurs when closing the window, I think it occurs on startup, when it fails to create the system tray icon for some reason.
Yep, that sounds likely. Did you try starting tomboy from the command line ? A possible explanation of why rebooting seemed to help, if there had been a previous crash with Tomboy, maybe, just maybe, some process was still running and that interfered with Tomboy's startup. Tomboy does check to ensure its not a second process although I don't know what mechanism is used. (For Tomboy-ng, I just grep for a running process called 'tomboy-ng' and it can suffer a fate as discussed.) I do think you need to start Tomboy from command line and add --debug Davo
Steps to reproduce:
Expected results:
Actual results:
Interestingly, until recently this used to work. I'm not sure how or why the behaviour changed.
Running Tomboy v1.14.1 on Debian 9.