I can reproduce this in testdrive with today's quantal CD image:
- select Try Ubuntu
- open terminal with Ctrl+Alt+T (qemu tablet mouse doesn't work for me in
quantal)
- sudo software-properties-gtk: enable universe
- sudo apt-get update
- sudo apt-get install gtimelog
- gtimelog
It crashes on startup after printing a couple of error messages:
(gtimelog:9287): Gtk-CRITICAL **: gtk_style_context_get_property: assertion
`priv->widget != NULL || priv->widget_path != NULL' failed
/usr/lib/python2.7/dist-packages/gi/types.py:47: Warning:
/build/buildd/glib2.0-2.33.2/./gobject/gtype.c:4206: type id `0' is invalid
return info.invoke(*args, **kwargs)
/usr/lib/python2.7/dist-packages/gi/types.py:47: Warning: can't peek value
table for type `<invalid>' which is not currently referenced
return info.invoke(*args, **kwargs)
Segmentation fault (core dumped)
lp:gtimelog trunk crashes in the same way
Running gtimelog with python -m trace --trace ./gtimelog tells me that
the last line of code executed inside gtimelog itself is main.py:1116,
which reads
color = style.get_color(gtk.StateFlags.NORMAL)
Looks like my panel background color detection hack is broken.
I can reproduce the segfault by doing this:
$ python
>>> import gi
>>> from gi.repository import Gtk
>>> Gtk.MenuBar().get_style_context().get_color(Gtk.StateFlags.NORMAL)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1016212
Title:
gtimelog crashed with SIGSEGV in gtk_style_context_get_valist()
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtimelog/+bug/1016212/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
