Can't click any categories or tags in overview totals #46

bendavis78 opened this Issue Nov 19, 2012 · 25 comments

7 participants


Previously, I was able to click a category or tag in the overview totals, which would hide other categories or tags and hilight the activities in that category or tag. Now, when mousing over any of the bars, they don't highlight and the mouse cursor doesn't change. Sometimes, I can click just one of the categories, and once I do that others become clickable.

My system is Ubuntu-Gnome 3.6.1 running under gnome-shell, and I'm using hamster git master @ d140d45


As an additional note, resizing the window also seems to make things un-clickable.


humm, can't reproduce. try this in a console in the checkout folder:

killall hamster-window-service

this way you will see any output in console. after that try running overview and see if perhaps there are any errors printed out in the console.

thank you!


I encounter the same problems. Additionally clicks on days do not work either.

I followed your suggestion and started "hamster-windows-service" manually, but unfortunately there was no output at all. Any other suggestions on how to debug this problem?

My System: Ubuntu 12.10, Gnome-Shell 3.6.1, Hamster @ c798fbc


try opening a console and run "hamster" - it will pop up the todays view. then pick "overview" from the menu.
thank you!


On running hamster:

$ hamster
/usr/lib/python2.7/dist-packages/hamster/ GtkWarning: _gtk_accel_group_attach: assertion `g_slist_find (accel_group->acceleratables, object) == NULL' failed

On opening "overview" from the menu

"overview" from the menu/usr/lib/python2.7/dist-packages/hamster/ GtkWarning: IA__gtk_accel_label_set_accel_closure: assertion `gtk_accel_group_from_accel_closure (accel_closure) != NULL' failed
  ui.add_from_file(os.path.join(runtime.data_dir, name))

No other outputs where generated.


ah sorry, i forgot to mention to try hovering over the non-clickables, but perhaps you did that, hmmmmm


same for me with gnome 3.4.1 and git checkout.


well we need somebody to track this down proper
@dreeh - could you perhaps check out hamster experiments ( and see if works for you? It should work as noted in the tutorial - see this screenshot

if it doesn't then there must be something going on with the underlying libs and lib/ would need adjustments


mhh. now, i've downgraded to gnome2 branch. there are the same error messages mentioned above, but its working (withing gnome 3.4.1).

@dreeh is working


good that is working - that means the problem is some place more easy to find.

re gnome2 branch - that would be rather random, i don't see anything that could have caused it breaking there
from the original report the bug seems to be erratic and not 100% reproducible, which would make me think that you perhaps just got lucky?

in any case i'm not sure what i can recommend doing from here except going into the code and digging out the issue (as i can't reproduce it myself i won't be able to track it). for any testing keep in mind that all windows are called indirectly via the dbus hamster-windows-service service. so for testing you will have to kill that and start it in the /src/ folder in checkout

killall hamster-windows-service

i'm happy that there is a workaround to access tracked data :-)

  • hamster-service is always started by hamster itself

  • the error messages are the same with master and gnome2 branch:

/usr/lib/python2.7/site-packages/hamster/ GtkWarning: _gtk_accel_group_attach: assertion g_slist_find (accel_group->acceleratables, object) == NULL' failed
/usr/lib/python2.7/site-packages/hamster/ GtkWarning: IA__gtk_accel_label_set_accel_closure: assertion
gtk_accel_group_from_accel_closure (accel_closure) != NULL' failed
ui.add_from_file(os.path.join(runtime.data_dir, name))

  • with master no tracked data are shown, no data in overview

  • some more error messages after minimize or resize window:

Traceback (most recent call last):
File "/usr/lib/python2.7/site-packages/hamster/", line 332, in on_show_overview_clicked
File "/usr/lib/python2.7/site-packages/hamster/", line 106, in show
dialog = self.get_dialog_class()(parent, **kwargs)
File "/usr/lib/python2.7/site-packages/hamster/", line 82, in init
File "/usr/lib/python2.7/site-packages/hamster/", line 114, in show
File "/usr/lib/python2.7/site-packages/hamster/", line 164, in search
self.facts =, self.end_date, search_terms)
File "/usr/lib/python2.7/site-packages/hamster/", line 130, in get_facts
File "/usr/lib/python2.7/site-packages/hamster/", line 43, in from_dbus_fact
id = fact[0]
File "/usr/lib/python2.7/site-packages/hamster/lib/", line 49, in init
if len(input_parts) > 1 and re.match('^-?\d', input_parts[0]): #look for time only if there is more
NameError: global name 're' is not defined
Traceback (most recent call last):
File "/usr/lib/python2.7/site-packages/hamster/widgets/", line 119, in on_mouse_enter
if (self.end_time - self.start_time) < dt.timedelta(days=356):
TypeError: unsupported operand type(s) for -: 'NoneType' and 'NoneType'


oh yay, looks like you found it! i'll take a look


@dreeh - looks like your bug is a separate one and rather introduced by me a few days ago. could you try pulling now? - fixed the missing imports. the rest was just a huge domino failure


btw those "GtkWarning: _gtk_accel_group_attach" are just warnings


great. its working with master now.


Thank you for the report @dreeh!

To summarize - this fix does not solve the original report by @bendavis78
Ben - would be awesome if you could try hamster experiments as per this comment #46 (comment)



Just tested Works as expected on my system.

I also updated hamster to the latest GIT version (59f643c). No change in behaviour. Most elements are still not clickable and do not respond to hover.

Additional information to the initial report:
I noticed that the clickable elements on a screen change. E.g. initially only one bar is responding to the hover and click events. Two cases:
1. Clicking on the element can remove this ability from the element and other elements are "suddenly" clickable. That way you can play hide and seek to extract the requested information.
2. After resizing the window, most of the times the contained elements do not respond to hover or click actions at all. I only had a few rare cases where a single element was clickable after resizing the window.



I have the very same issue and they manifest in the exact same way as @WBTMagnum described them.

Latest git version, just checked out. works fine.

If that matters at all I'm running lubuntu/openbox but a colleague next desk to me has it on ubuntu/gnome.

This is quite frustrating so I'm willing to spend time helping you figuring it out, just tell me what other information I can provide and so on.


would be awesome if you could try hamster experiments as per this comment #46


I'm also experiencing this issue. Will try "experiments" as described when I have a chance.


I'm seeing this problem on my work machine with ubuntu quantal; can't reproduce on my home machine (ubuntu precise), even with several different versions (going back to October 2012).

I will test the experiments / on quantal tomorrow or Friday.


On Quantal, experiments/ works as expected, but hamster is broken as described in the original report. I've tested latest master (fdc01fa), 1.02 (97f8e2c), and an early post-rename version (4222d81); all behave the same way. A fresh install of precise (in a VM) doesn't show the problem.

This suggests to me a library change or bug. Any hints on how to isolate the changes the introduced the problem?

My Quantal install has gnome 3.6.1-0ubuntu1 (as reported by aptitude); Precise has 3.0.2-2ubuntu7.

In addition to the problems described in the original report, the "[-]" button in the upper-right corner of the week calendar is affected: on quantal it appears when I hover over the calendar, but I don't see a finger icon when I hover on it and it doesn't respond to clicks.

Apologies for these piecemeal reports -- I'm reporting as I learn.


I have the same issue. Downgrading libcairo2 to the version in Precise (1.10.2) fixes it for me.

Upgrading libcairo to 1.12.12 (version from Raring) also fixes the issue. Seems like a bug in cairo that has already been fixed.


Same issue here, on Debian wheezy (libcairo 1.12.2 amd64). I compiled and installed libcairo 1.12.14 and the issue is fixed.


the switch to gtk3 should clean the slate for this guy. killing

@tstriker tstriker closed this Feb 9, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment