Gtimelog on Fedora 17?
I’m busy getting a new laptop operational, with all the little tweaks that I’ve come to rely on over the years. One of those is Gtimelog. It’s a small and simple Python program that lets me track my working time. I’ve been using it pretty much every working day since 2006 or so. Over the years I’ve converted most of FSFE’s staff to the program. It lets us manage working hours much better than we could otherwise, and helps avoid burnouts.
Now, this new laptop is running Fedora 17. The OS is pretty delightful, but I can’t get Gtimelog to work. There’s no Fedora package, so I installed it according to instructions by Sam Tuke. Those worked fine for F16, but not for F17. Starting Gtimelog in a console gives me:
** (process:1748): WARNING **: Trying to register gtype ‘GMountMountFlags’ as enum when in fact it is of type ‘GFlags’
** (process:1748): WARNING **: Trying to register gtype ‘GDriveStartFlags’ as enum when in fact it is of type ‘GFlags’
** (process:1748): WARNING **: Trying to register gtype ‘GSocketMsgFlags’ as enum when in fact it is of type ‘GFlags’
Traceback (most recent call last):
File “/usr/bin/gtimelog”, line 9, in <module>
load_entry_point(‘gtimelog==0.7.1′, ‘gui_scripts’, ‘gtimelog’)()
File “/usr/lib/python2.7/site-packages/gtimelog-0.7.1-py2.7.egg/gtimelog/main.py”, line 2110, in main
tray_icon = icon_class(main_window)
File “/usr/lib/python2.7/site-packages/gtimelog-0.7.1-py2.7.egg/gtimelog/main.py”, line 1088, in __init__
‘style-updated’, self.on_style_set) # Gtk+ 3
TypeError: <gtk.Window object at 0×1103320 (GtkWindow at 0×1140060)>: unknown signal name: style-updated
Can anyone make sense of this?
And is there anyone out there who has successfully gotten Gtimelog to work on Fedora 17?
Comments
You’re looking for https://live.gnome.org/ProjectHamster
Thanks – I know Hamster, but prefer Gtimelog for two reasons.
First, I’m using KDE, so Hamster’s slick integration with Gnome3 (*shiver*) doesn’t help me.
Second, and more importantly, Hamster’s default approach is that I’d have to specify what I’m going to work on in the future. Gtimelog, on the other hand, defaults to me specifying what I’ve been doing for the last X minutes or hours. That fits much better with the way I work.
So, I already have the time tracker that suits me best. I just need to get the damn thing working again.
I would appreciate a bug report in the upstream bug tracker at https://bugs.launchpad.net/gtimelog, if it’s not too much trouble.
I haven’t seen this error before. It looks like at least one of the alternative tray icon cases has bitrotted, or at least not kept up with changes in Gtk+ or Python-GObject Introspection. You can probably get it to run if you edit ~/.gtimelog/gtimelogrc and set show_tray_icon to no.
I’d like to find a Fedora 17 virtual machine image somewhere, reproduce this bug, and fix it. I’d appreciate any helpful pointers regarding the first — a easy-to-use tool like Ubuntu’s TestDrive would be best.
@Marius,
thanks a lot for your reply! As you suggested, I set show_tray_icon = no in my gtimelogrc. And you know what? It works, and I have one of my most valuable tools back.
I would have filed a bug report, but wasn’t quite sure whom to bother – you, Fedora, Python, or any other potentially guilty party. Now that you’ve identified the likely cause of the problem (and I’ve confirmed it), that probably is no longer necessary.
Thanks a lot for your help! What a nice surprise on the first day after my vacation