I'm going to make an educated guess that it is due to the lack of clockd on Zoom2 (check with dpkg -l)
/Carsten maemo.org distmaster 2010/2/24 John Beattie <[email protected]>: > > I'm learning about maemo using zoom2 hardware. I have a bug where worldclock > hangs when I make a certain sequence of user-input. I have used gdb to see > what is going on, but without source, since this is a closed package, the > clock-ui package. It looks as if the app spawns a thread to do something > and then starts pthread_cond_timedwait. And then the thread quits very > quickly and the originating thread never progresses. > > My question is whether it is worth raising this as an issue, since the zoom2 > is only for development hacking and, further, my build is not anything like > an official maemo release? > -- > View this message in context: > http://n2.nabble.com/maemo-zoom2-worldclock-tp4625849p4625849.html > Sent from the maemo-developers mailing list archive at Nabble.com. > _______________________________________________ > maemo-developers mailing list > [email protected] > https://lists.maemo.org/mailman/listinfo/maemo-developers > _______________________________________________ maemo-developers mailing list [email protected] https://lists.maemo.org/mailman/listinfo/maemo-developers
