Bug 153882

Summary:	A lot of information is reported on the command line, making it impossible to launch k3b from a terminal
Product:	[Applications] k3b	Reporter:	Francois Marier <francois>
Component:	general	Assignee:	K3b Bugs <k3b-bugs-null>
Status:	REPORTED ---
Severity:	wishlist	CC:	sergio.callegari
Priority:	NOR
Version First Reported In:	unspecified
Target Milestone:	---
Platform:	Debian testing
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description Francois Marier 2007-12-12 01:38:44 UTC

Version:           1.0.4 (using KDE KDE 3.5.8)
Installed from:    Debian testing/unstable Packages
OS:                Linux

Tomas Pospisek <tpo_deb@sourcepole.ch> reported on the Debian tracker that K3b outputs a lot of information to the command line.  While this is useful for debugging purposes, he notes that it makes it hard to continue using the terminal where k3b was started.  Of course, one could pipe the output to /dev/null, but he suggested instead that the default be mostly silent and that debugging output be shown only when a "--verbose" switch is used.

From http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=455815 :

"At startup k3b dumps several pages of debug info to STDOUT/STDERR.
That's not nice behaveour when started from withing of a console. If
needed that could be handled by a start option (f.ex. --verbose).ebug info to stdout/stderr"

Comment 1 Sebastian Trueg 2007-12-12 08:33:57 UTC

Isn't it up to the packager to enable or disable debugging in KDE apps?

Comment 2 Francois Marier 2007-12-13 02:04:52 UTC

So would that be a configure option for K3b or is it something that is more general and needs to be enabled/disabled for all of KDE ?

Comment 3 Sebastian Trueg 2007-12-13 11:04:02 UTC

try kdebugdialog.

Comment 4 John Kizer 2025-01-14 07:09:23 UTC

*** Bug 498467 has been marked as a duplicate of this bug. ***