suzhe / google-gadgets-for-linux

Automatically exported from code.google.com/p/google-gadgets-for-linux
Apache License 2.0
0 stars 0 forks source link

ggl-gtk doesn't run #313

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. ggl-gtk

What is the expected output? What do you see instead?
I'm told to expect a notification area icon to appear, instead i get nothing.

What version of the product are you using? On what operating system?
0.11.0 on ubuntu 8.04.3.

Please provide any additional information below.
when I run it in terminal, I get a very long output, but here seems to be
where it goes 
wrong:
04:35.897: sidebar_gtk_host.cc:754: Set SideBar size: 200x1024

(ggl-gtk:9576): Gdk-CRITICAL **: gdk_x11_atom_to_xatom_for_display:
assertion `atom != GDK_NONE' failed

(ggl-gtk:9576): Gdk-CRITICAL **: gdk_x11_atom_to_xatom_for_display:
assertion `atom != GDK_NONE' failed

(ggl-gtk:9576): Gdk-CRITICAL **: gdk_x11_atom_to_xatom_for_display:
assertion `atom != GDK_NONE' failed
04:35.897: sidebar_gtk_host.cc:810: move sidebar to 1480x0

(ggl-gtk:9576): Gdk-CRITICAL **: gdk_x11_atom_to_xatom_for_display:
assertion `atom != GDK_NONE' failed
* Closing connection #0
The program 'ggl-gtk' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadAtom (invalid Atom parameter)'.
  (Details: serial 407 error_code 5 request_code 19 minor_code 0)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the --sync command line
   option to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)
04:35.939: extension_manager.cc:260: Destroy global extension manager.

...

properties registered in constructors: 205
total properties: 729 (if all obj reg: 1053, saved 30.769231%)

googling shows similar errors, which are unsolved, were solved by a patch
uploaded onto google code (this was for version 0.10) and a dependency issue.

Original issue reported on code.google.com by larsen...@gmail.com on 1 Jul 2009 at 12:12

Attachments:

GoogleCodeExporter commented 9 years ago

Original comment by james...@gmail.com on 1 Jul 2009 at 3:23