docky crashes when opening a recent document

Bug #645864 reported by marbertone
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Docky
Fix Released
Low
Robert Dyer

Bug Description

docky crashes when opening a recent document. Some times it does, some times not. With a 50% probability.
I attach the ENTIRE output from running docky in the terminal with the -d (or --debug) flag when the error is triggered. (ex: $ docky -d) [file called "post.txt"]
Distro in use: Karmic
X Version: Karmic native
Video Card: Nvidia
GNOME Version: latest one
Mono version: latest one

Revision history for this message
marbertone (marbertone-deactivatedaccount) wrote :
Revision history for this message
marbertone (marbertone-deactivatedaccount) wrote :

some relevant informations:
errors not written in post.txt:

** (rhythmbox:9504): CRITICAL **: atk_object_set_name: assertion `name != NULL' failed

** (rhythmbox:9504): CRITICAL **: atk_object_set_name: assertion `name != NULL' 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 Docky.Services.SystemService.Open (AppInfo app, IEnumerable`1 files) [0x00046] in /build/buildd/docky-2.1.0~bzr1620/Docky.Services/Docky.Services/SystemService.cs:342
  at Docky.Services.SystemService.Open (IEnumerable`1 files) [0x00000] in /build/buildd/docky-2.1.0~bzr1620/Docky.Services/Docky.Services/SystemService.cs:330
  at Docky.Services.SystemService.Open (File file) [0x00000] in /build/buildd/docky-2.1.0~bzr1620/Docky.Services/AssemblyInfo.cs:1
  at RecentDocuments.RecentDocumentsItem+<OnGetMenuItems>c__AnonStorey1.<>m__6 (System.Object o, System.EventArgs a) [0x00000] in /build/buildd/docky-2.1.0~bzr1620/StandardPlugins/RecentDocuments/src/RecentDocumentsItem.cs:186
  at Docky.Menus.MenuItem.SendClick () [0x0000b] in /build/buildd/docky-2.1.0~bzr1620/Docky.Items/Docky.Menus/MenuItem.cs:133
  at Docky.Menus.MenuItemWidget.OnButtonReleaseEvent (Gdk.EventButton evnt) [0x00010] in /build/buildd/docky-2.1.0~bzr1620/Docky/Docky/Menus/MenuItemWidget.cs:141
  at Gtk.Widget.buttonreleaseevent_cb (IntPtr widget, IntPtr evnt) [0x00000]
   at GLib.ExceptionManager.RaiseUnhandledException(System.Exception e, Boolean is_terminal)
   at Gtk.Widget.buttonreleaseevent_cb(IntPtr widget, IntPtr evnt)
   at Gtk.Application.gtk_main()
   at Gtk.Application.Run()
   at Docky.Docky.Main(System.String[] args) in /build/buildd/docky-2.1.0~bzr1620/Docky/Docky/Docky.cs:line 95

(of fact, Docky crashed after I minimised all the windows and run Rhythmbox).

Best regards,
Mario Alberto

p.s.
why should I remove Docky PPA from my repositories just because every time it tells me about doing an upgrade? I don't want to leave my Karmic at all ! It runs flawlessly!!!

Cheers

Revision history for this message
Robert Dyer (psybers) wrote :

First off, it looks like your dbus is not properly configured. Do the following:

1) verify dbus is running, and if it make sure it does run
2) make sure you are using our PPA version of ndesk-dbus

Revision history for this message
Robert Dyer (psybers) wrote :

Also please update your docky package. You appear to be using our development PPA and are about 20 revisions behind.

Changed in docky:
assignee: nobody → Rico Tzschichholz (ricotz)
importance: Undecided → Low
Revision history for this message
Robert Dyer (psybers) wrote :

Should be fixed in rev 1644.

Changed in docky:
assignee: Rico Tzschichholz (ricotz) → Robert Dyer (psybers)
milestone: none → 2.0.7
status: New → Fix Committed
Revision history for this message
Rico Tzschichholz (ricotz) wrote :

@Robert: This commit doesnt look nice. I might noticed a similar problem trying to fix the GLib.File leak and creating duplicates works around it. So to create a duplicate please use the "Dup ()" method of GLib.File

Revision history for this message
marbertone (marbertone-deactivatedaccount) wrote : Re: [Bug 645864] Re: docky crashes when opening a recent document

  It seems I can't update Docky anymore (I'm using Karmic and I don't
want to upgrade it).
Cheers,
M.A.

Il 23/09/2010 17:06, Robert Dyer ha scritto:
> Also please update your docky package. You appear to be using our
> development PPA and are about 20 revisions behind.
>
> ** Changed in: docky
> Assignee: (unassigned) => Rico Tzschichholz (ricotz)
>
> ** Changed in: docky
> Importance: Undecided => Low
>

Revision history for this message
Rico Tzschichholz (ricotz) wrote :

@marbertone: you should do this: "sudo apt-get update" and "sudo apt-get dist-upgrade"

Revision history for this message
marbertone (marbertone-deactivatedaccount) wrote :

  Dear Rico,
I know how to do an update, thanks!
I don't wont to upgrade my distro actually!
Cheers!
M.A.

Il 23/09/2010 18:17, Rico Tzschichholz ha scritto:
> @marbertone: you should do this: "sudo apt-get update" and "sudo apt-get
> dist-upgrade"
>

Revision history for this message
Rico Tzschichholz (ricotz) wrote :

@marbertone: i understood that you want to keep karmic, but "apt-get dist-upgrade" doesnt upgrade to lucid if you dont change your software sources. Actually it will try to resolve the package dependency issues you are having. Also using "aptitude" would make you able to fix it.

Changed in docky:
status: Fix Committed → Fix Released
Revision history for this message
marbertone (marbertone-deactivatedaccount) wrote :

Hi guys!
I updated to Maverick and Docky PPA development still gives me the same problem. I attach everything has to be attached: docky -d output as docky.txt and this is the std.err. It's such a pity that such a nice program fails this way.

here comes std.err:

 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 RecentDocuments.RecentDocumentsItem+<OnGetMenuItems>c__AnonStorey1.<>m__6 (System.Object o, System.EventArgs a) [0x00000] in /build/buildd/docky-2.1.0~bzr1672/StandardPlugins/RecentDocuments/src/RecentDocumentsItem.cs:186
  at Docky.Menus.MenuItem.SendClick () [0x0000b] in /build/buildd/docky-2.1.0~bzr1672/Docky.Items/Docky.Menus/MenuItem.cs:133
  at Docky.Menus.MenuItemWidget.OnButtonReleaseEvent (Gdk.EventButton evnt) [0x00010] in /build/buildd/docky-2.1.0~bzr1672/Docky/Docky/Menus/MenuItemWidget.cs:138
  at Gtk.Widget.buttonreleaseevent_cb (IntPtr widget, IntPtr evnt) [0x00000] in <filename unknown>:0
   at GLib.ExceptionManager.RaiseUnhandledException(System.Exception e, Boolean is_terminal)
   at Gtk.Widget.buttonreleaseevent_cb(IntPtr widget, IntPtr evnt)
   at Gtk.Application.gtk_main()
   at Gtk.Application.Run()
   at Docky.Docky.Main(System.String[] args) in /build/buildd/docky-2.1.0~bzr1672/Docky/Docky/Docky.cs:line 103
Cairo.Context: called from finalization thread, programmer is missing a call to Dispose
Cairo.Context: called from finalization thread, programmer is missing a call to Dispose
Cairo.Context: called from finalization thread, programmer is missing a call to Dispose
Cairo.Context: called from finalization thread, programmer is missing a call to Dispose
Cairo.Context: called from finalization thread, programmer is missing a call to Dispose
Cairo.Context: called from finalization thread, programmer is missing a call to Dispose
Cairo.Context: called from finalization thread, programmer is missing a call to Dispose
Cairo.Context: called from finalization thread, programmer is missing a call to Dispose
Cairo.Context: called from finalization thread, programmer is missing a call to Dispose
Cairo.Context: called from finalization thread, programmer is missing a call to Dispose
Cairo.Context: called from finalization thread, programmer is missing a call to Dispose

Revision history for this message
Robert Dyer (psybers) wrote :

That is a different crash. Please file a NEW bug.

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

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.