Mmh, strange behavior.
For the tomboy part, I cannot confirm it, since it works fine on my
ubuntu. Can anybody confirm?
For the hamster part, I do agree that a race condition can occur. It's simply
solved by removing the checking if hamster is active on plugin activation.
However, I don't think we should remove that. I'll wait for opinions from other
developers.
Anyway, if you're annoyed by it, just remove from
/usr/share/gtg/GTG/plugins/hamster.gtg-plugin the line
"Dbus-dependencies=org.gnome.Hamster:/org/gnome/Hamster". It's perfectly safe.
** Tags added: toreview
** Changed in: gtg
Importance: Undecided => Low
** Changed in: gtg
Milestone: None => 0.3
** Changed in: gtg
Status: New => Incomplete
--
Tomboy and Hamster plugin unchecked at startup
https://bugs.launchpad.net/bugs/562284
You received this bug notification because you are a member of Gtg
contributors, which is subscribed to Getting Things GNOME!.
Status in Getting Things GNOME!: Incomplete
Bug description:
GTG 0.2.4 from stable ppa
Ubuntu 9.10
With GTG unset to start on login, I have to activate Tomboy and Hamster plugins
every startup. Plugins remain activated if GTG is restarted on the same
session. If I restart the machine they became uncheked upon the next startup
(only these 2 plugins).
If "start on login" is activated, upon restart Tomboy plugin is unchecked as
above and Hamster is disabled. Most certainly this is because GTG is initiated
before Hamster on startup (Hamster gets enabled -- but unchecked -- after
restarting GTG), and this might be a different issue.
Thanks!
_______________________________________________
Mailing list: https://launchpad.net/~gtg
Post to : [email protected]
Unsubscribe : https://launchpad.net/~gtg
More help : https://help.launchpad.net/ListHelp
