[Mageia-dev] Disable GTK/GLIB error messages - .xsession-errors overflooded

Sat Sep 3 10:58:59 CEST 2011

Hello,
+
+just recently i noticed that my .xsession-errors on Mageia 1 has grown quite a bit:
+
+    [doktor5000 at mageia1 ~]$ ls -lah .xsession-errors
+    -rw------- 1 doktor5000 doktor5000 1,2G Sep  3 10:46 .xsession-errors
+
+I already disabled all KDE debug information via kdebugdialog, which i needed 
+earlier,
+but GTK/GLIB seems to give a flood of messages like the ones below:
+
+    (transmission-gtk:16147): GLib-GObject-WARNING **: invalid cast from
+    `GtkTreeView' to `GtkProgress'
+
+    (transmission-gtk:16147): Gtk-CRITICAL **:
+    IA__gtk_progress_get_current_percentage: assertion `GTK_IS_PROGRESS
+    (progress)' failed
+
+    (transmission-gtk:16147): GLib-GObject-WARNING **: invalid cast from
+    `GtkTreeView' to `GtkProgress'
+
+    (transmission-gtk:16147): GLib-GObject-WARNING **: invalid cast from
+    `GtkTreeView' to `GtkProgress'
+
+    (transmission-gtk:16147): GLib-GObject-WARNING **: invalid cast from
+    `GtkTreeView' to `GtkProgressBar'
+
+    (transmission-gtk:16147): Gtk-CRITICAL **:
+    IA__gtk_progress_bar_get_orientation: assertion `GTK_IS_PROGRESS_BAR
+    (pbar)' failed
+
+    [doktor5000 at mageia1 ~]$ grep GLib-GObject-WARNING .xsession-errors | wc -l
+    166425
+    [doktor5000 at mageia1 ~]$ grep Gtk-CRITICAL .xsession-errors | wc -l
+    83470
+
+
+Can anyone give me a hint how to disable those, please? And how to proceed with
+the cause, those messages should clearly be suppressed, as transmission works 
+correct
+and such a growth of .xsession-error is totally wrong. It also makes it really hard
+to find real, legitimate error messages in .xsession-errors.
+Also this can lead to real problems, like in: 
+http://lists.gnu.org/archive/html/emacs-devel/2010-10/msg00927.html
+filling up the root partition, which can cause quite some problems to normal users,
+if they have no seperate /home partition. The only workarounds i have found so far
+suggest removing .xsession-errors and linking it to /dev/null after each X login,
+but this seems really ugly to me.
+
+Regards
+