Gnome-Do not auto starting at login

Bug #488099 reported by Benjamin Humphrey on 2009-11-25
50
This bug affects 10 people
Affects Status Importance Assigned to Milestone
Do
Undecided
Unassigned
gnome-do (Ubuntu)
Low
Unassigned
Nominated for Lucid by Barry Warsaw

Bug Description

Binary package hint: gnome-do

For some reason Gnome Do won't auto start when I login, even though it has that option checked under its preferences, and an item listed under "Startup Applications."

Interestingly, Gnome Do will launch if I manually click it from the menu, and it runs fine after then.

When it's running, I have two processes for it, one of which is waiting. (see attachment)

Thanks

ProblemType: Bug
Architecture: amd64
Date: Wed Nov 25 22:42:57 2009
DistroRelease: Ubuntu 9.10
Package: gnome-do 0.8.2+dfsg-1
ProcEnviron:
 LANG=en_NZ.UTF-8
 SHELL=/bin/bash
SourcePackage: gnome-do
Uname: Linux 2.6.32-020632rc5-generic x86_64

Benjamin Humphrey (humphreybc) wrote :
Benjamin Humphrey (humphreybc) wrote :

Managed to fix it by having a 10 second delayed start thanks to a script. Script is attached.

but this means that you have to wait 15 seconds more to have all the desktop available right? when you start counting those 15 seconds, right after login?

regards.

Barry Warsaw (barry) wrote :

This has just started happening to me in Lucid. It's been working fine in Karmic.

Barry Warsaw (barry) wrote :

Here's an excerpt from my ~/.xsession-errors file that is probably relevant.

Exception in Gtk# callback delegate
  Note: Applications can use GLib.ExceptionManager.UnhandledException to handle the exception.
System.NullReferenceException: Object reference not set to an instance of an object
  at Do.Interface.PositionWindow.GetMonitor () [0x00000]
  at Do.Interface.PositionWindow+<UpdatePosition>c__AnonStorey3.<>m__8 (System.Object , System.EventArgs ) [0x00000]
  at Gtk.Application+InvokeCB.Invoke () [0x00000]
  at GLib.Timeout+TimeoutProxy.Handler () [0x00000]
   at GLib.ExceptionManager.RaiseUnhandledException(System.Exception e, Boolean is_terminal)
   at GLib.Timeout+TimeoutProxy.Handler()
   at Gtk.Application.gtk_main()
   at Gtk.Application.Run()
   at Do.Do.Main(System.String[] args)

Barry Warsaw (barry) wrote :

After today's Lucid update, Gnome Do started just fine at login.

Daniel Hahler (blueyed) wrote :

Benjamin, is this still a problem for you?
Have you added the 15 seconds delay to the existing start script, or a new/custom one?
Also, can you look at your ~/.xsession-errors file, if there is a hint (when having the extra delay removed)?

Changed in gnome-do (Ubuntu):
importance: Undecided → Low
status: New → Incomplete
Barry Warsaw (barry) wrote :

This is failing for me again. Here's an excerpt from my .xessions-errors fle.

(Do:2132): Gtk-CRITICAL **: gtk_window_get_position: assertion `GTK_IS_WINDOW (window)' failed

(Do:2132): Gtk-CRITICAL **: gtk_window_get_size: assertion `GTK_IS_WINDOW (window)' failed

(Do:2132): Gtk-CRITICAL **: gtk_window_get_screen: assertion `GTK_IS_WINDOW (window)' failed

(Do:2132): Gtk-CRITICAL **: gtk_window_get_screen: assertion `GTK_IS_WINDOW (window)' failed
Exception in Gtk# callback delegate
  Note: Applications can use GLib.ExceptionManager.UnhandledException to handle the exception.
System.NullReferenceException: Object reference not set to an instance of an object
  at Do.Interface.PositionWindow.GetMonitor () [0x00000]
  at Do.Interface.PositionWindow+<UpdatePosition>c__AnonStorey3.<>m__8 (System.Object , System.EventArgs ) [0x00000]
  at Gtk.Application+InvokeCB.Invoke () [0x00000]
  at GLib.Timeout+TimeoutProxy.Handler () [0x00000]
   at GLib.ExceptionManager.RaiseUnhandledException(System.Exception e, Boolean is_terminal)
   at GLib.Timeout+TimeoutProxy.Handler()
   at Gtk.Application.gtk_main()
   at Gtk.Application.Run()
   at Do.Do.Main(System.String[] args)

Neil_C (neil-chesh) wrote :

I have the same problem with the same error in my .xsessions-errors file. This is an upgraded 9.10 system which had gnome-do starting ok at login before the upgrade.

David Futcher (bobbo) on 2010-06-08
tags: added: patch-forwarded-upstream

Same here, just recently became a problem. xsession-errors:
(Do:1615): Gtk-CRITICAL **: gtk_window_get_position: assertion `GTK_IS_WINDOW (window)' failed
(Do:1615): Gtk-CRITICAL **: gtk_window_get_size: assertion `GTK_IS_WINDOW (window)' failed
(Do:1615): Gtk-CRITICAL **: gtk_window_get_screen: assertion `GTK_IS_WINDOW (window)' failed
(Do:1615): Gtk-CRITICAL **: gtk_window_get_screen: assertion `GTK_IS_WINDOW (window)' failed
  at Do.Interface.PositionWindow.GetMonitor () [0x00000]
  at Do.Interface.PositionWindow+<UpdatePosition>c__AnonStorey3.<>m__8 (System.Object , System.EventArgs ) [0x00000]

Interestingly, when I open a guest session, for the guest everything works fine.

The problem continues to exist for me. Any ideas?

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

Other bug subscribers