Bug 285970 - .xsession-errors flooded by online... messages
Summary: .xsession-errors flooded by online... messages
Status: RESOLVED FIXED
Alias: None
Product: telepathy
Classification: Unmaintained
Component: presence-dataengine (show other bugs)
Version: git-latest
Platform: openSUSE Linux
: NOR normal
Target Milestone: 0.4.0
Assignee: Telepathy Bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-11-07 09:48 UTC by Alin M Elena
Modified: 2012-07-06 12:47 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Alin M Elena 2011-11-07 09:48:03 UTC
Version:           git-latest (using Devel) 
OS:                Linux

.xsession-errors flooded by online... messages I suspect other combination are possible too...

nwoki suggested that the data engine may be the guilty one.



Reproducible: Didn't try

Steps to Reproduce:
......

Actual Results:  
.....

Expected Results:  
.....

OS: Linux (x86_64) release 3.1.0-2-desktop
Compiler: gcc.
Comment 1 David Edmundson 2011-11-07 11:39:41 UTC
Check what kdebugdialog is set to do with plasma/telepathy/telepathy-qt4 stuff

~/.xsession-errors is filled with any debug that don't have anywhere to display their output. I would be surprised if it's something actually doing anything 'wrong'.

Though some of our stuff is very heavy on debug prints. I doubt all of it is really needed.
Could you print the full line that's being printed then I can search through the code.
Comment 2 Alin M Elena 2011-11-07 12:18:58 UTC
in my case is just online
I have disable all debug output set in kdebugdialog
Comment 3 Igor Poboiko 2011-11-07 12:44:31 UTC
There's just a one word "online" which duplicates lots of times. It doesn't seem to be KDebug messages, because they look like "appname(pid)/module Function: message"
Comment 4 David Edmundson 2011-12-09 17:13:45 UTC
This was the plasmoid having many console.log messages, I think I fixed this before 0.2.

Re-open if still apparent.