FS#10153 - [loudmouth] Compile with debugging support

Attached to Project: Arch Linux
Opened by Leslie Polzer (skypher) - Friday, 11 April 2008, 17:53 GMT
Last edited by Jan de Groot (JGC) - Tuesday, 20 July 2010, 13:08 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Jan de Groot (JGC)
Architecture All
Severity Low
Priority Normal
Reported Version 2007.08-2
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Loudmouth spews out a huge bunch of logging messages to the console, which is really annoying in GNU Freetalk. The only way to disable this is building LM with debugging support and setting the environment variable LM_DEBUG to be an empty string.

Without debugging support in LM it doesn't honour the variable at all.
This task depends upon

Closed by  Jan de Groot (JGC)
Tuesday, 20 July 2010, 13:08 GMT
Reason for closing:  Fixed
Additional comments about closing:  Fixed in 1.4.3-2.
Comment by Gavin Bisesi (Daenyth) - Wednesday, 04 June 2008, 18:51 GMT
This is easy enough to do with abs, either by using !strip or a configure flag. I don't think this needs to be in the official package, but then again I might be wrong.
Comment by Leslie Polzer (skypher) - Thursday, 05 June 2008, 07:20 GMT
Usage of Freetalk is seriously hampered without this change.
Comment by Jan de Groot (JGC) - Wednesday, 21 January 2009, 15:13 GMT
Is this still an issue with recent versions of loudmouth?
Comment by Leslie Polzer (skypher) - Wednesday, 21 January 2009, 16:23 GMT
Haven't experienced this in a while. Close and reopen later if necessary. :)
Comment by Ramil (gravicappa) - Wednesday, 04 February 2009, 19:51 GMT
  • Field changed: Percent Complete (100% → 0%)
There is still debug messages flood. (loudmouth 1.4.3-1, freetalk 3.2-1).
Comment by Laszlo Papp (djszapi) - Saturday, 07 November 2009, 07:32 GMT
Did you try Daenyth's idea ?
Comment by Leslie Polzer (skypher) - Monday, 07 December 2009, 15:11 GMT
  • Field changed: Percent Complete (100% → 0%)
I have seen this problem some weeks ago again.

Want me to submit a patch? This bug seems so obvious to reproduce and fix.
Comment by Roman Kyrylych (Romashka) - Monday, 07 December 2009, 15:12 GMT
sure if you have a patch please submit it.

Loading...