GTG

GTG crash in startup

Bug #1069963 reported by Firas Ghanim
26
This bug affects 6 people
Affects Status Importance Assigned to Milestone
GTG
Fix Released
Critical
Unassigned

Bug Description

After updating liblarch to latest version (0.2.5.r135~precise1) today, gtg wouldn't start. It crashes immediately after start without displaying the tasks list window.

GTG: 0.2.9.r1234~precise1
Ubuntu: 12.04
Gnome: 3.4.2
Kernel: 3.2.0-32

gtg -d:

2012-10-22 19:54:41,981 - DEBUG - gtg:core_main_init:139 - Debug output enabled.
2012-10-22 19:54:42,027 - DEBUG - __init__:__init__:68 - Backends found: ['backend_localfile', 'backend_mantis', 'backend_identica', 'backend_tomboy', 'backend_gnote', 'backend_rtm', 'backend_launchpad', 'backend_twitter', 'backend_evolution']
2012-10-22 19:54:42,060 - WARNING - __init__:__init__:77 - Backend backend_mantis could not be loaded: No module named suds.client
2012-10-22 19:54:42,170 - WARNING - __init__:__init__:77 - Backend backend_twitter could not be loaded: No module named tweepy.models
2012-10-22 19:54:42,170 - WARNING - __init__:__init__:77 - Backend backend_evolution could not be loaded: No module named evolution
Traceback (most recent call last):
  File "/usr/bin/gtg", line 85, in <module>
    main()
  File "/usr/bin/gtg", line 81, in main
    sys.exit(gtg.main(options, args))
  File "/usr/share/gtg/GTG/gtg.py", line 118, in main
    ds, req = core_main_init(options, args)
  File "/usr/share/gtg/GTG/gtg.py", line 147, in core_main_init
    ds = DataStore(config)
  File "/usr/share/gtg/GTG/core/datastore.py", line 64, in __init__
    self.__tagstore = self.treefactory.get_tags_tree(self.requester)
  File "/usr/share/gtg/GTG/core/treefactory.py", line 77, in get_tags_tree
    alltag.set_attribute("special", "all")
  File "/usr/share/gtg/GTG/core/tag.py", line 103, in set_attribute
    self.notify_related_tasks()
  File "/usr/share/gtg/GTG/core/tag.py", line 204, in notify_related_tasks
    for task_id in self.get_related_tasks():
  File "/usr/share/gtg/GTG/core/tag.py", line 190, in get_related_tasks
    withfilters=['active'], include_transparent=False)
TypeError: get_nodes() got an unexpected keyword argument 'include_transparent'

Related branches

Revision history for this message
Izidor Matušov (izidor) wrote :

I am sorry. There is a major change in liblarch and the needed code in GTG is not merged yet. Please, downgrade liblarch. Sorry for inconvenience.

Changed in gtg:
assignee: nobody → Lionel Dricot (ploum)
milestone: none → 0.3
importance: Undecided → Critical
status: New → In Progress
Revision history for this message
Paul Gear (paulgear) wrote :

I got hit by this one today, too. It would be a good idea to get the new liblarch removed from the gtg PPA.

Revision history for this message
Matt Lavin (matt-lavin) wrote :

I hit this today and it look me some time to figure out the right version of larch to revert to. The latest version that worked for me was 0.2.5.r134

Revision history for this message
sergio (serge-simon) wrote :

Same problem for me.
Is liblarch used by any other programs (in order to know if i can downgrade without any risks) ?
(moreover, if liblarch is specific to gtg, then it's weird to have this dependency problem)

Revision history for this message
sergio (serge-simon) wrote :

Ok, was unaware that liblarch is probably anyway only used by GTG.
So it's quite weird to have such a broken dependency in the PPA !

As a side note, after a few tries, the easiest thing to do right now in order to have GTG working again at this time :
- grab the sourcecode of liblarch from this commit (newer ones doesn't work) : https://github.com/liblarch/liblarch/tree/d4df5ab970745dc1372fcdeec5648c9232c89cb1
- uncompress it in /usr/share/liblarch/
- run GTG with something like "cd /usr/share/gtg/ ; ./gtg -l"

Changed in gtg:
status: In Progress → Fix Committed
Changed in gtg:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.