Bug#426477: tasks: segfaults when I select a Priority

2007-05-29 Thread Ross Burton
On Tue, 2007-05-29 at 04:16 +0300, Eddy Petrişor wrote: I start tasks, select a task to edit, select a prio, tasks segfaults: $ LANG=C tasks /home/eddy/.gtkrc-2.0:3: error: invalid identifier `color', expected valid identifier Whoops, typo in your theme. (tasks:19504): Gtk-CRITICAL **:

Bug#426477: tasks: segfaults when I select a Priority

2007-05-29 Thread Eddy Petrișor
Ross Burton wrote: On Tue, 2007-05-29 at 04:16 +0300, Eddy Petrişor wrote: I start tasks, select a task to edit, select a prio, tasks segfaults: $ LANG=C tasks /home/eddy/.gtkrc-2.0:3: error: invalid identifier `color', expected valid identifier Whoops, typo in your theme. nah, is gtk

Bug#426477: tasks: segfaults when I select a Priority

2007-05-29 Thread Ross Burton
On Tue, 2007-05-29 at 15:31 +0300, Eddy Petrișor wrote: Not sure if this is good enough; as you can see, I didn't knew where to put the breakpoint (g_assert was not useful): The trick to break on glib assertions is to break on g_logv, which is the lowest message output function. The svn

Bug#426477: tasks: segfaults when I select a Priority

2007-05-29 Thread Eddy Petrișor
Ross Burton wrote: On Tue, 2007-05-29 at 15:31 +0300, Eddy Petrișor wrote: Not sure if this is good enough; as you can see, I didn't knew where to put the breakpoint (g_assert was not useful): The trick to break on glib assertions is to break on g_logv, which is the lowest message output

Bug#426477: tasks: segfaults when I select a Priority

2007-05-28 Thread Eddy Petrişor
Package: tasks Version: 0.7-1 Severity: grave Justification: renders package unusable I start tasks, select a task to edit, select a prio, tasks segfaults: $ LANG=C tasks /home/eddy/.gtkrc-2.0:3: error: invalid identifier `color', expected valid identifier (tasks:19504): Gtk-WARNING **: Unable