On Sat, Mar 28, 2009 at 7:47 AM, sabby7890 <email address hidden> wrote:
> Regarding Sander Stuurwold's response:
>
> After clicking "OK" Alarm Clock initializes Python's threading system by
> calling:
>
> gtk.gdk.threads_init()
>
> And it seems this is where the crash occurs. I really can't do anything
> about that, since this function is required for AC to work and seems
> broken on Ubuntu (since it crashes on Ubuntu only).
>
> Please verify if C version of Alarm Clock (Alarm-Clock-1.0a1) have this
> problem too.
>
> --
> [Jaunty] alarm-clock causes screen to freeze
> https://bugs.launchpad.net/bugs/321176
> You received this bug notification because you are a direct subscriber
> of the bug.
>
I can confirm that the C version works.
On Sat, Mar 28, 2009 at 7:47 AM, sabby7890 <email address hidden> wrote:
> Regarding Sander Stuurwold's response: threads_ init() /bugs.launchpad .net/bugs/ 321176
>
> After clicking "OK" Alarm Clock initializes Python's threading system by
> calling:
>
> gtk.gdk.
>
> And it seems this is where the crash occurs. I really can't do anything
> about that, since this function is required for AC to work and seems
> broken on Ubuntu (since it crashes on Ubuntu only).
>
> Please verify if C version of Alarm Clock (Alarm-Clock-1.0a1) have this
> problem too.
>
> --
> [Jaunty] alarm-clock causes screen to freeze
> https:/
> You received this bug notification because you are a direct subscriber
> of the bug.
>