Menu
▾
▴
[Ayttm-users] [ ayttm-Bugs-996947 ] mcop warning
|
From: SourceForge.net <no...@so...> - 2004-09-20 11:52:13
|
Bugs item #996947, was opened at 2004-07-23 21:50 Message generated for change (Comment added) made by elh You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=550744&aid=996947&group_id=77614 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Adam Butler (spacedoubtman) Assigned to: Nobody/Anonymous (nobody) Summary: mcop warning Initial Comment: Hi Ed. > Try using it with the the -D option. I get the same error: i@ii:~/.ayttm$ ayttm -D Disabling console message server. mcop warning: user defined signal handler found for SIG_PIPE, overriding i@ii:~/.ayttm$ > Also, please open a bug report so that I can try and > reproduce and fix. You mean open bug report on sourcefourge like this? I get no more messages after setting all ~/.ayttm/prefs debug options to 1. > Which 2.6 kernel are you using? 2.6.6 with debian patches - custom compile > Where did you get it from? Got ayttm-0.4.6-17.tar.bz2 from the sourcefourge download page - dont know which server - possibly an aussie one. Get the same problems with the latest source from cvs. Got my kernel source from dselect. I dont know if this is a bug or just a problem with my system config - might be both, might. Another odd thing (most likely unrelated) is that when I had the still working 0.4.6-2 installed from dselect. Its actually only 0.4.6-1. ---------------------------------------------------------------------- >Comment By: Edward L. Haletky (elh) Date: 2004-09-20 06:52 Message: Logged In: YES user_id=747074 Hello, PLease note that this is a GTK+ application. GTK2 will not work. Is there anything else for this report?1Z6R88V5DK41005456 ---------------------------------------------------------------------- Comment By: Edward L. Haletky (elh) Date: 2004-07-27 07:25 Message: Logged In: YES user_id=747074 mcop warning is normal. that is not what is causing the problem. Please run the program under the debugger and do a ctrl-C then a where and respond with the output. That will tell us where it is hanging. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=550744&aid=996947&group_id=77614 |