Bug 248799 - Various messages on stdout/stderr when starting kaddressbook-mobile
Summary: Various messages on stdout/stderr when starting kaddressbook-mobile
Status: CLOSED INTENTIONAL
Alias: None
Product: KAddressbook Mobile
Classification: Unmaintained
Component: general (show other bugs)
Version: unspecified
Platform: Maemo 5 Linux
: VLO minor
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
: 248800 (view as bug list)
Depends on:
Blocks:
 
Reported: 2010-08-23 13:10 UTC by Felix Wolfsteller
Modified: 2010-08-25 13:17 UTC (History)
1 user (show)

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

Attachments
stdout and stderr when starting kaddressbook-mobile (24.38 KB, text/plain)
2010-08-23 13:10 UTC, Felix Wolfsteller 		Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Felix Wolfsteller 2010-08-23 13:10:08 UTC 
Version:           unspecified
OS:                Linux

When starting kaddressbook-mobile, i get to see a lot of messages.

It is unclear, whether these are debug output or should be alarming.

The meaning of some is especially difficult to sort out, like the lines "CH-440" or "CH-420".

Exemplary file is attached.

(Version 4:4.5~20100813.1163254-1maemo1.1164259 )

Reproducible: Always
Comment 1 Felix Wolfsteller 2010-08-23 13:10:53 UTC 
Created attachment 50859 [details]
stdout and stderr when starting kaddressbook-mobile
Comment 2 Felix Wolfsteller 2010-08-23 13:11:15 UTC 
Comment on attachment 50859 [details]
stdout and stderr when starting kaddressbook-mobile

(Version 4:4.5~20100813.1163254-1maemo1.1164259 )
Comment 3 Bernhard E. Reiter 2010-08-23 16:13:38 UTC 
Yes, when in doubt we want to have more output.
This is developers output, so it is not needed to have it interpretable
by users. (As users will not start applications on the command line. Or know how to switch debugging off by using kdebugdialog.)
Comment 4 Bernhard E. Reiter 2010-08-23 16:17:42 UTC 
*** Bug 248800 has been marked as a duplicate of this bug. ***