Christoph Egger christ...@debian.org writes:
Neil Williams codeh...@debian.org writes:
On Sun, 15 Aug 2010 02:23:32 +
brian m. carlson sand...@crustytoothpaste.net wrote:
On Sun, Aug 15, 2010 at 12:09:42AM +0100, Neil Williams wrote:
Redirect stderr when opening the file or work out why
Hello,
Lars Wirzenius l...@liw.fi writes:
On su, 2010-08-15 at 14:19 +0200, Tollef Fog Heen wrote:
I would guess they still fill up the .xsession-errors file, though? At
least for me, that file is mostly useless due to:
« ...Too much output, ignoring rest... »
as the last line.
It's
Ben Hutchings b...@decadent.org.uk writes:
On Sun, 2010-08-15 at 17:02 +0100, Neil Williams wrote:
[...]
Most of the stuff in ~/.xsession-errors which has been mentioned here,
are exactly these kind of assertion failure errors:
(gnome-power-manager:2346): GLib-GObject-WARNING **: value
On 18/08/10 11:15, Goswin von Brederlow wrote:
The checks
in glib seem good enough to handle such cases sanely so maybe the glib
could be shut up about them for stable releases (or where users just
don't care). Maybe something like setting GLIB_BE_SILENT or so if
recompiling the lib silent is
On Wed, 2010-08-18 at 13:38 +0200, Emilio Pozuelo Monfort wrote:
those are not stupid debug output, but real problems, and should
be fixed. We're not going to hide them.
So have gtk_assert (or whatever it is) actually call abort() and make
the offending applications crash, so the offending
Emilio Pozuelo Monfort po...@debian.org writes:
On 18/08/10 11:15, Goswin von Brederlow wrote:
The checks
in glib seem good enough to handle such cases sanely so maybe the glib
could be shut up about them for stable releases (or where users just
don't care). Maybe something like setting
On 18/08/10 14:53, Peter Miller wrote:
So have gtk_assert (or whatever it is) actually call abort() and make
the offending applications crash, so the offending developers *have* to
fix them. But until you do that, give me a way to Shut Them Off, and
without silencing *real* error messages,
Le mercredi 18 août 2010 à 22:53 +1000, Peter Miller a écrit :
On Wed, 2010-08-18 at 13:38 +0200, Emilio Pozuelo Monfort wrote:
those are not stupid debug output, but real problems, and should
be fixed. We're not going to hide them.
So have gtk_assert (or whatever it is) actually call
In data mercoledì, 18. di agosto 2010 11:00:04, Goswin von Brederlow ha
scritto:
Those are DEBUG messages. They are not relevant or usefull for 99.9% of
all users and the only thing they do is annoy. Some of them have been
around for years so clearly they are not something anyone is working
Good morning (at least in my time zone ;)),
Christian PERRIER bubu...@debian.org writes:
Quoting Michael Welle (mwe012...@gmx.net):
Hello,
what is the reason that many applications clutter the terminal with
output that is obvisously debug output? Lets take digikam as an
example:
(I
]] Lars Wirzenius
| On su, 2010-08-15 at 14:19 +0200, Tollef Fog Heen wrote:
| I would guess they still fill up the .xsession-errors file, though? At
| least for me, that file is mostly useless due to:
|
| « ...Too much output, ignoring rest... »
|
| as the last line.
|
| It's pretty
On Sun, 2010-08-15 at 17:02 +0100, Neil Williams wrote:
[...]
Most of the stuff in ~/.xsession-errors which has been mentioned here,
are exactly these kind of assertion failure errors:
(gnome-power-manager:2346): GLib-GObject-WARNING **: value -nan of
type `gdouble' is invalid or out of
On 16/08/10 02:01, Russ Allbery wrote:
gregor herrmann gre...@debian.org writes:
Among the contents are e.g. ~20.000 lines saying:
(firefox-bin:28026): Gdk-WARNING **: XID collision, trouble ahead
I tracked this down at one point and decided that this was the fault of
Adobe's Flash
Hello,
Neil Williams codeh...@debian.org writes:
On Sat, 14 Aug 2010 19:59:50 +0200
Michael Welle mwe012...@gmx.net wrote:
what is the reason that many applications clutter the terminal with
output that is obvisously debug output?
It's debug output, it is useful when debugging and you
Hello,
Paul Wise p...@debian.org writes:
[...]
debug output should certainly not be output by default in released
versions without a command-line or configuration option turning it on.
l for one don't want ls doing something like this:
ls: starting up
ls: checking for bad filesystems
ls:
Hello,
brian m. carlson sand...@crustytoothpaste.net writes:
On Sun, Aug 15, 2010 at 12:09:42AM +0100, Neil Williams wrote:
It's debug output, it is useful when debugging and you need the output,
e.g. when fixing bugs and the user can just be asked to run the command
from the terminal and
On Sun, 15 Aug 2010 08:51:21 +0200
Michael Welle mwe012...@gmx.net wrote:
It's debug output, it is useful when debugging and you need the
output, e.g. when fixing bugs and the user can just be asked to run
the command from the terminal and post the output to help in
debugging the bug
On Sun, 15 Aug 2010 12:44:59 +0800
Paul Wise p...@debian.org wrote:
On Sun, Aug 15, 2010 at 7:09 AM, Neil Williams codeh...@debian.org
wrote:
It's not clutter. If you don't want to see it, run the command and
redirect stderr.
debug output should certainly not be output by default in
On Sun, 15 Aug 2010 08:57:56 +0200
Michael Welle mwe012...@gmx.net wrote:
Paul Wise p...@debian.org writes:
[...]
debug output should certainly not be output by default in released
versions without a command-line or configuration option turning it
on.
l for one don't want ls doing
On Sun, 15 Aug 2010 02:23:32 +
brian m. carlson sand...@crustytoothpaste.net wrote:
On Sun, Aug 15, 2010 at 12:09:42AM +0100, Neil Williams wrote:
It's debug output, it is useful when debugging and you need the
output, e.g. when fixing bugs and the user can just be asked to run
the
* Neil Williams codeh...@debian.org [100815 10:55]:
When bugs are hard to reproduce, having debug output on by default is
extremely important for many mature packages.
Which does not change the fact that a graphical program which outputs
stuff to the terminal is very annoying and looks very
Am Samstag, 14. August 2010, 19:59:50 schrieb Michael Welle:
Hello,
what is the reason that many applications clutter the terminal with
output that is obvisously debug output? Lets take digikam as an
example:
In the specific case of Digikam and other KDE applications, you can run
Hi,
On Sonntag, 15. August 2010, brian m. carlson wrote:
The Unix tradition is for programs to run silently unless there's a
problem. [...]
I have no problem with programs taking an environment variable or a
command line option in order to produce debugging output, but it
shouldn't be the
On Sun, Aug 15, 2010 at 10:02:15AM +0100, Neil Williams wrote:
On Sun, 15 Aug 2010 12:44:59 +0800
Paul Wise p...@debian.org wrote:
On Sun, Aug 15, 2010 at 7:09 AM, Neil Williams codeh...@debian.org
wrote:
It's not clutter. If you don't want to see it, run the command and
redirect
Hello,
Neil Williams codeh...@debian.org writes:
On Sun, 15 Aug 2010 08:51:21 +0200
Michael Welle mwe012...@gmx.net wrote:
It's debug output, it is useful when debugging and you need the
output, e.g. when fixing bugs and the user can just be asked to run
the command from the terminal
Neil Williams codeh...@debian.org writes:
On Sun, 15 Aug 2010 02:23:32 +
brian m. carlson sand...@crustytoothpaste.net wrote:
On Sun, Aug 15, 2010 at 12:09:42AM +0100, Neil Williams wrote:
Redirect stderr when opening the file or work out why okular was
selected in the first place.
Hello,
Neil Williams codeh...@debian.org writes:
On Sun, 15 Aug 2010 08:57:56 +0200
Michael Welle mwe012...@gmx.net wrote:
[...]
My feeling is that many developers
^^
don't care because most users might not be aware of what is happening.
That is a very cavalier attitude to how
Hello,
Josef Spillner 2...@kuarepoti-dju.net writes:
Am Samstag, 14. August 2010, 19:59:50 schrieb Michael Welle:
Hello,
what is the reason that many applications clutter the terminal with
output that is obvisously debug output? Lets take digikam as an
example:
In the specific case of
]] Josef Spillner
| When KDE applications are run in a KDE environment, the debug output is
| normally not an issue because even terminal-using people prefer KRunner's
| autocompletion over bash's and hence don't see the debug messages. However,
it
| is certainly an upstream goal to make KDE
On Sun, Aug 15, 2010 at 10:05:17AM +0100, Neil Williams wrote:
Users may but developers will be looking for that debug output and
starting the program from the command line explicitly to be able to
collect it. (Filing a bug will usually result in the user being asked
to start the program from
Am Sonntag, 15. August 2010, 14:19:05 schrieb Tollef Fog Heen:
I would guess they still fill up the .xsession-errors file, though? At
least for me, that file is mostly useless due to:
« ...Too much output, ignoring rest... »
as the last line.
Yes they would, because the applications
On su, 2010-08-15 at 14:19 +0200, Tollef Fog Heen wrote:
I would guess they still fill up the .xsession-errors file, though? At
least for me, that file is mostly useless due to:
« ...Too much output, ignoring rest... »
as the last line.
It's pretty clear to me that both .xsession-errors
On Sun, 15 Aug 2010 08:08:57 -0700
Wouter Verhelst wou...@debian.org wrote:
On Sun, Aug 15, 2010 at 10:05:17AM +0100, Neil Williams wrote:
Users may but developers will be looking for that debug output and
starting the program from the command line explicitly to be able to
collect it.
Wouter Verhelst wou...@debian.org writes:
gets rather large), it generates huge .xsession-errors files that can
cause problems for people with low quotas or for people who actually
Indeed. I often find the SD card of my PDA (openmoko) filled with
a useless .xsession-errors.
--
To
Quoting Michael Welle (mwe012...@gmx.net):
Hello,
what is the reason that many applications clutter the terminal with
output that is obvisously debug output? Lets take digikam as an
example:
(I read most other comments in this thread before writing this)
I have to concur to everything
On Sun, 15 Aug 2010 18:34:56 -0400, Christian PERRIER wrote:
Here's mine, started yesterday morningand I barely did nothing
since then as I'm more travelling around Vermont that playing with my
KDE apps:
bubu...@mykerinos:~/travail/debian/translation/po-debconf/gitolite ls -l
gregor herrmann gre...@debian.org writes:
Among the contents are e.g. ~20.000 lines saying:
(firefox-bin:28026): Gdk-WARNING **: XID collision, trouble ahead
I tracked this down at one point and decided that this was the fault of
Adobe's Flash player rather than anything the Mozilla folks
Hello,
what is the reason that many applications clutter the terminal with
output that is obvisously debug output? Lets take digikam as an
example:
kdeinit4: preparing to launch /usr/lib/kde4/libkdeinit/libkdeinit4_klauncher.so
Connecting to deprecated signal
On Sat, 14 Aug 2010 19:59:50 +0200
Michael Welle mwe012...@gmx.net wrote:
what is the reason that many applications clutter the terminal with
output that is obvisously debug output?
It's debug output, it is useful when debugging and you need the output,
e.g. when fixing bugs and the user can
On Sun, Aug 15, 2010 at 12:09:42AM +0100, Neil Williams wrote:
It's debug output, it is useful when debugging and you need the output,
e.g. when fixing bugs and the user can just be asked to run the command
from the terminal and post the output to help in debugging the bug
report. Generally,
On Sun, Aug 15, 2010 at 7:09 AM, Neil Williams codeh...@debian.org wrote:
It's debug output, it is useful when debugging and you need the output,
e.g. when fixing bugs and the user can just be asked to run the command
from the terminal and post the output to help in debugging the bug
report.
41 matches
Mail list logo
