Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
Getting rid of GTK warnings in terminal
View unanswered posts
View posts from last 24 hours

 
Reply to topic    Gentoo Forums Forum Index Desktop Environments
View previous topic :: View next topic  
Author Message
stareagle
n00b
n00b


Joined: 04 Jul 2006
Posts: 26

PostPosted: Sun Oct 20, 2013 8:32 pm    Post subject: Getting rid of GTK warnings in terminal Reply with quote

Hello everyone,

when I start a GTKApplication from the terminal, like Gedit or Meld, the terminal is messed up with warnings. For example meld:

Code:

/usr/lib64/python2.7/site-packages/gobject/__init__.py:115: Warning: attempting to add an interface (GtkEditable) to class (HistoryFileEntry) after class_init
  type_register(cls, namespace.get('__gtype_name__'))
Traceback (most recent call last):
  File "/usr/lib64/meld/meld/ui/historyentry.py", line 277, in <lambda>
    entry.connect("changed", lambda *args: self.emit("changed"))
TypeError: <HistoryFileEntry object at 0x2209c30 (HistoryFileEntry at 0x2288010)>: unknown signal name: changed
Traceback (most recent call last):
  File "/usr/lib64/meld/meld/ui/historyentry.py", line 277, in <lambda>
    entry.connect("changed", lambda *args: self.emit("changed"))
TypeError: <HistoryFileEntry object at 0x2209f00 (HistoryFileEntry at 0x2288130)>: unknown signal name: changed
Traceback (most recent call last):
  File "/usr/lib64/meld/meld/ui/historyentry.py", line 277, in <lambda>
    entry.connect("changed", lambda *args: self.emit("changed"))
TypeError: <HistoryFileEntry object at 0x243f690 (HistoryFileEntry at 0x2586170)>: unknown signal name: changed
Traceback (most recent call last):
  File "/usr/lib64/meld/meld/ui/historyentry.py", line 277, in <lambda>
    entry.connect("changed", lambda *args: self.emit("changed"))
TypeError: <HistoryFileEntry object at 0x243f6e0 (HistoryFileEntry at 0x2586050)>: unknown signal name: changed
Traceback (most recent call last):
  File "/usr/lib64/meld/meld/ui/historyentry.py", line 277, in <lambda>
    entry.connect("changed", lambda *args: self.emit("changed"))
TypeError: <HistoryFileEntry object at 0x24597d0 (HistoryFileEntry at 0x25daa90)>: unknown signal name: changed
Traceback (most recent call last):
  File "/usr/lib64/meld/meld/ui/historyentry.py", line 277, in <lambda>
    entry.connect("changed", lambda *args: self.emit("changed"))
TypeError: <HistoryFileEntry object at 0x2456500 (HistoryFileEntry at 0x25da970)>: unknown signal name: changed
Traceback (most recent call last):
  File "/usr/lib64/meld/meld/ui/historyentry.py", line 277, in <lambda>
    entry.connect("changed", lambda *args: self.emit("changed"))
TypeError: <HistoryFileEntry object at 0x24600f0 (HistoryFileEntry at 0x23dc430)>: unknown signal name: changed
Traceback (most recent call last):
  File "/usr/lib64/meld/meld/ui/historyentry.py", line 277, in <lambda>
    entry.connect("changed", lambda *args: self.emit("changed"))
TypeError: <HistoryFileEntry object at 0x2460140 (HistoryFileEntry at 0x26e6a50)>: unknown signal name: changed
Traceback (most recent call last):
  File "/usr/lib64/meld/meld/ui/historyentry.py", line 277, in <lambda>
    entry.connect("changed", lambda *args: self.emit("changed"))
TypeError: <HistoryFileEntry object at 0x2468690 (HistoryFileEntry at 0x27f3040)>: unknown signal name: changed
Traceback (most recent call last):
  File "/usr/lib64/meld/meld/ui/historyentry.py", line 277, in <lambda>
    entry.connect("changed", lambda *args: self.emit("changed"))
TypeError: <HistoryFileEntry object at 0x2437e10 (HistoryFileEntry at 0x27baea0)>: unknown signal name: changed


This is quite annoying. Is there any way of gettings rid of these messages?

I'am using GTK+ 3.8.4 and 2.24.17, Gedit 3.8.3 and Meld 1.7.0.[/code]

Best regards,

Stareagle
Back to top
View user's profile Send private message
Jaglover
Watchman
Watchman


Joined: 29 May 2005
Posts: 5036
Location: Saint Amant, Acadiana

PostPosted: Sun Oct 20, 2013 9:32 pm    Post subject: Reply with quote

You need to be more descriptive, why redirecting it to /dev/null is not a solution for you?
_________________
Please learn how to denote units correctly!
Back to top
View user's profile Send private message
franzf
Advocate
Advocate


Joined: 29 Mar 2005
Posts: 4067
Location: Irgendwo im Nirgendwo

PostPosted: Mon Oct 21, 2013 7:07 am    Post subject: Reply with quote

I also wondered how to make GTK apps less noisy. KDE has kdebugdialog to adjust which apps should print debug output.

Why not pipe? That only helps when you run the app from within a terminal. If you use a launcher (Win+R, Alt+F2 or from desktop/panel icon) you would have to modify each .desktop-file to get rid of spamming into ~/.xsession-errors - you probably have to find REAL issues once in a while and having to deal with all those warnings can get hard.
It would be handy if it was possible to set something like "GTK_VERBOSE_LOGGING=0" in your .bashrc and simply set it to "1" if you need to debug your app :)
_________________
"der mac dennoch wesen geil"
Wolfram von Eschenbach, Parzival (Buch 1, Z. 7).
Ein frühes Statement gegen Windows.

My overlay
Back to top
View user's profile Send private message
salahx
Guru
Guru


Joined: 12 Mar 2005
Posts: 423

PostPosted: Mon Oct 21, 2013 7:26 am    Post subject: Reply with quote

It has something to do with PyGObject. See the gnome bug as well (Note: Gnome bugzilla not working for me at the time of this post)

Assuming the application starts, it seems to he harmless - pygobject shouldn't be adding interfaces after g_type_class_ref, but the added interface never get called anyway, so nothing bad happens. if you find it sufficently annoying try rebuilding pygobject (you may need rebuild goject-introspection and maybe even glib too).
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Desktop Environments All times are GMT
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum