Re: [Wengophone-devel] Bad interaction with Qt themes
Alec leamas a écrit : My configuration ;-) AMD-64, Fedora-7. Console: [EMAIL PROTECTED] wengophone-2.2-ci]$ wengophone [EMAIL PROTECTED] wengophone-2.2-ci]$ wengophone (process:10607): GLib-CRITICAL **: g_main_loop_unref: assertion `loop != NULL' failed I. e. it works first time, but not second. The logfile logs perfectly OK at a glance. This is a different issue caused by the way we stop the Glib event loop in Gaim. I am going to fix this today hopefully. Aurélien PS: Don't forget to reply-all! ___ Wengophone-devel mailing list Wengophone-devel@lists.openwengo.com http://dev.openwengo.com/mailman/listinfo/wengophone-devel
Re: [Wengophone-devel] Bad interaction with Qt themes
Dave Neary a écrit : Hi, Aurélien Gâteau wrote: More about this one: it seems to be caused by our sigchild catcher. If I comment out the line: signal(SIGCHLD, sigchild_catcher); in main.cpp, I don't get the delay or the error message. Unfortunately, I think this signal catcher is required by libgaim. The signal catcher isn't required - it was added to prevent error messages (glib fatal messages) from being printed due to uncaught sigchilds. I would have preferred preventing the child processes from terminating incorrectly. My mistake, libgaim requires the SIGPIPE catch, not the SIGCHLD. In the meantime, if people can live with 8 or 10 error messages in the console (even with debug tracing turned off) then removing the handler is of course a possibility. After running the WengoPhone without the catcher for a few days, I finally committed the change. I didn't get any glib message, is there any particular configuration which trigger them? Aurélien ___ Wengophone-devel mailing list Wengophone-devel@lists.openwengo.com http://dev.openwengo.com/mailman/listinfo/wengophone-devel
Re: [Wengophone-devel] Bad interaction with Qt themes
Hi, Aurélien Gâteau wrote: More about this one: it seems to be caused by our sigchild catcher. If I comment out the line: signal(SIGCHLD, sigchild_catcher); in main.cpp, I don't get the delay or the error message. Unfortunately, I think this signal catcher is required by libgaim. The signal catcher isn't required - it was added to prevent error messages (glib fatal messages) from being printed due to uncaught sigchilds. I would have preferred preventing the child processes from terminating incorrectly. In the meantime, if people can live with 8 or 10 error messages in the console (even with debug tracing turned off) then removing the handler is of course a possibility. Cheers, Dave. -- Dave Neary OpenWengo Community Development Manager Email: [EMAIL PROTECTED] Tel: +33 9 51 13 46 45 Mob: +33 6 28 09 73 11 ___ Wengophone-devel mailing list Wengophone-devel@lists.openwengo.com http://dev.openwengo.com/mailman/listinfo/wengophone-devel
Re: [Wengophone-devel] Bad interaction with Qt themes
Aurélien Gâteau wrote: I can reproduce the cleanlook bug (need to have a further look at it), but I never encountered the plastique one. I tried with KWin and Beryl on a Ubuntu Feisty. Is it 100% reproducible for you? I can reproduce both. I am under amd64 architecture, Ubuntu gutsy. Binaries from the openwengo website do not exhibit this problem (note that they are compiled for 32 bit arch). If I compile at 64 bit, I get the issue when start wengophone and compiz is running. Bye, Ludovico ___ Wengophone-devel mailing list Wengophone-devel@lists.openwengo.com http://dev.openwengo.com/mailman/listinfo/wengophone-devel
Re: [Wengophone-devel] Bad interaction with Qt themes
Ludovico Cavedon wrote: Aurélien Gâteau wrote: I can reproduce the cleanlook bug (need to have a further look at it), but I never encountered the plastique one. I tried with KWin and Beryl on a Ubuntu Feisty. Is it 100% reproducible for you? Hi, I can reproduce both. I am under amd64 architecture, Ubuntu gutsy. Binaries from the openwengo website do not exhibit this problem (note that they are compiled for 32 bit arch). Aurélien I told you about my problems with the configuration window being to huge. The height is about 2000px or much more. I think it is the same problem. If I compile at 64 bit, I get the issue when start wengophone and compiz is running. without compiz ... Bye, Ludovico -- andreas -- http://www.cynapses.org/ - cybernetic synapses signature.asc Description: OpenPGP digital signature ___ Wengophone-devel mailing list Wengophone-devel@lists.openwengo.com http://dev.openwengo.com/mailman/listinfo/wengophone-devel
[Wengophone-devel] Bad interaction with Qt themes
Hi all, I think there are some bugs in the interface that happen only with particular themes. In particular: 1) if using the pastique theme, the window size is huge and window borders are missing (see ticket #1851 [1]). This happens mostly (but not only) when using compiz under an amd64 arch. 2) if using the cleanlook theme, there is a 30 second delay after the QProcess: Destroyed while process is still running. message before the GUI is shown. I think this is a wengophone bug because all other qt4 applications are not affected. What could be the cause? Can you reproduce these problems? Thanks, Regards, Ludovico [1] http://dev.openwengo.com/trac/openwengo/trac.fcgi/ticket/1851 ___ Wengophone-devel mailing list Wengophone-devel@lists.openwengo.com http://dev.openwengo.com/mailman/listinfo/wengophone-devel
