kwrite spams stderr with debug on warning box

Bug #1044296 reported by Stephen Baynes
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
kate (Ubuntu)
New
Undecided
Unassigned

Bug Description

When kwrite puts up a warning box then the following appears on stderr

Setting new source
New source: QUrl( "file:///usr/share/sounds/KDE-Sys-Warning.ogg" )
Transitioning to state "playing"
State change
Moving from "ready" 1 to "paused" 4
Stream changed to file:///usr/share/sounds/KDE-Sys-Warning.ogg
State change
Moving from "paused" 4 to "playing" 2
About to finish
Got next source. Waiting for end of current.
New source: QUrl( "" )
Finally got a source
About to finish
Got next source. Waiting for end of current.
New source: QUrl( "" )
Finally got a source
Transitioning to state "ready"
State change
Moving from "playing" 2 to "paused" 4
State change
Moving from "paused" 4 to "ready" 1

Makes a mess of the terminal in which it was started. If this must be output it should go to some sort of log file.

A way to get a suitable warning box is to try and open a directory, eg the command:

kwrite .

(Note if kwrite has already been started elsewhere then it will be the stderr of the original invocation, not the stderr of the invocation that triggers the warning).

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: kwrite 4:4.8.4-0ubuntu0.1
ProcVersionSignature: Ubuntu 3.2.0-29.46-generic 3.2.24
Uname: Linux 3.2.0-29-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.0.1-0ubuntu11
Architecture: amd64
Date: Fri Aug 31 10:45:00 2012
ExecutablePath: /usr/bin/kwrite
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425)
ProcEnviron:
 TERM=xterm
 SHELL=/bin/bash
 PATH=(custom, no user)
 LANG=en_GB.UTF-8
 LANGUAGE=en_GB:en
SourcePackage: kate
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
Stephen Baynes (stephen-baynes) wrote :
Revision history for this message
Stephen Baynes (stephen-baynes) wrote :

Looks as if changes to kwrite's error handling have now fixed this.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.