Docky 2.2 terminates with updates of any kind

[AD5XJ]

Any time the updater is run and dpkg updates precise, Docky will terminate - sometimes with an error in Qt about the message handler. Error report from apport has been forwarded previously.

Environment:
Ubuntu 12.04 (precise) 64 bit
Kernel 3.2.0-24-generic
GNOME 3.4.1

Hardware:
  memory 930 Mb
  processor AMD Athlon(tm) 64 Processor 3800+
  nvidia GeForce 6150 LE (latest nvidia release driver)

Disk
  Available disk space: 32.0 GiB

[AD5XJ (ad5xj)]

Does better after several updates to Ubuntu. But still crashes occasionally.
This mornings update did cause Docky to abort. Luckily, I was in debug mode so I captured the dump from mono:

[Fatal 08:58:01.057] [GLib-GObject] g_object_ref: assertion `G_IS_OBJECT (object)' failed
Stacktrace:

  at (wrapper managed-to-native) object.__icall_wrapper_mono_array_new_specific (intptr,int) <0xffffffff>
  at GLib.Marshaller.Utf8PtrToString (intptr) <0x0005b>
  at GLib.Marshaller.PtrToStringGFree (intptr) <0x00013>
  at GLib.FileAdapter.get_Path () <0x0002b>
  at Docky.Services.DesktopItemService/<UpdateDesktopItemsList>c__AnonStorey17/<UpdateDesktopItemsList>c__AnonStorey18.<>m__2E (Docky.Services.Applications.DesktopItem) <0x00035>
  at System.Linq.Enumerable.Any<TSource> (System.Collections.Generic.IEnumerable`1<TSource>,System.Func`2<TSource, bool>) <0x00093>
  at Docky.Services.DesktopItemService/<UpdateDesktopItemsList>c__AnonStorey17.<>m__21 (GLib.File) <0x00077>
  at System.Linq.Enumerable/<CreateWhereIterator>c__Iterator35`1.MoveNext () <0x000ff>
  at System.Linq.Enumerable/<CreateSelectIterator>c__Iterator27`2.MoveNext () <0x00125>
  at System.Collections.Generic.List`1.AddEnumerable (System.Collections.Generic.IEnumerable`1<T>) <0x0008f>
  at System.Collections.Generic.List`1..ctor (System.Collections.Generic.IEnumerable`1<T>) <0x00087>
  at System.Linq.Enumerable.ToList<TSource> (System.Collections.Generic.IEnumerable`1<TSource>) <0x0005b>
  at Docky.Services.DesktopItemService.UpdateDesktopItemsList () <0x00237>
  at Docky.Services.DesktopItemService/<MonitorDesktopFileDirs>c__AnonStorey1B.<>m__2C () <0x000a3>
  at Docky.Services.SystemService/<RunOnThread>c__AnonStorey38.<>m__60 () <0x0001c>
  at System.Threading.Thread.StartInternal () <0x00057>
  at (wrapper runtime-invoke) object.runtime_invoke_void__this__ (object,intptr,intptr,intptr) <0xffffffff>

Native stacktrace:

 mono() [0x80e6431]
 mono() [0x812697c]
 mono() [0x8062aff]
 [0xb77a940c]
 mono() [0x822633f]
 mono() [0x8229bb7]
 mono() [0x8226ad6]
 mono() [0x821fb98]
 mono() [0x8220250]
 mono() [0x8220c66]
 mono() [0x8220e85]
 mono() [0x822382f]
 mono() [0x82245c9]
 mono() [0x822a513]
 mono(mono_array_new_specific+0xa3) [0x81aae23]
 [0xb70826f0]
 [0xb5ac77dc]
 [0xb47729cc]
 [0xb4772924]
 [0xb217a176]
 [0xb47486c4]
 [0xb217a120]
 [0xb47e1a68]
 [0xb47479c6]
 [0xb47e1830]
 [0xb47e16c0]
 [0xb47e1624]
 [0xb2179d30]
 [0xb217b27c]
 [0xb2cfd895]
 [0xb2cfd830]
 [0xb51433a1]
 mono() [0x8066dcc]

Debug info from gdb:

Could not attach to process. If your uid matches the uid of the target
process, check the setting of /proc/sys/kernel/yama/ptrace_scope, or try
again as the root user. For more details, see /etc/sysctl.d/10-ptrace.conf
ptrace: Operation not permitted.
No threads.

=================================================================
Got a SIGSEGV while executing native code. This usually indicates
a fatal error in the mono runtime or one of the native libraries
used by your application.
=================================================================

Aborted (core dumped)
Note: video is nvidia GeForce but not using the -nv option

Also posted on the duplicate

[bwat47 (bwat47)]

Same here with latest dockt in quantal repos. Every computer I've used docky on has this issue, whenever there is an update or new software installed it immediately crashes, makes it pretty unusable...

[Robert Dyer (psybers)]

@bwat47: can you verify the crash's stack trace matches this one?

[AD5XJ (ad5xj)]

Well I can tell you that this is what was in the xsession file when it failed today...

Docky: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.

** (zeitgeist-datahub:2409): WARNING **: zeitgeist-datahub.vala:227: Unable to get name "org.gnome.zeitgeist.datahub" on the bus!
nautilus: ../../src/xcb_io.c:528: _XAllocID: Assertion `ret != inval_id' failed.

I will try to run it in debug mode the next time I update and post the dump from mono.

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Nicolas Krzywinski (nsk7even)]

This happens to me to _all_ machines, regardless their upgrade history (most of them have none) on Ubuntu 12.04 LTS and is quite annoying as there often updates come in!

So, everyone should be able to easily reproduce this with a fresh install that - naturally - needs a lot of updates.

[bwat47 (bwat47)]

I can reproduce this 100% of the time by opening synaptic and reinstalling the cinnamon package, docky will crash every time. I'm not sure how to generate a stack trace though, since this crash doesn't seem to trigger apport (and I do have apport enabled)

[bwat47 (bwat47)]

The crash seems to happen during this step in the installation process:

Processing triggers for bamfdaemon ...
Rebuilding /usr/share/applications/bamf.index...

[bwat47 (bwat47)]

ok, I hope this is helpful. I recently switched to xubuntu, and am getting the same crash there but now it seems to pop up with apport. I managed to reproduce it twice by instaling a few packages from synaptic, and I used the apport "examine locally" button to get a retrace:

his GDB was configured as "x86_64-linux-gnu".
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Reading symbols from /tmp/tmpZ28nKv/usr/bin/mono...Reading symbols from /tmp/tmpZ28nKv/usr/lib/debug/usr/bin/mono...done.
done.
warning: core file may not match specified executable file.
[New LWP 9026]
[New LWP 10235]
[New LWP 9027]
[New LWP 10214]
[New LWP 9025]
[New LWP 9024]
[New LWP 9020]
[New LWP 9023]
warning: Can't read pathname for load map: Input/output error.
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
Core was generated by `mono /usr/lib/docky/Docky.exe -d'.
Program terminated with signal 11, Segmentation fault.
#0 0x00007fbf18d079f2 in _IO_vfprintf_internal (s=0x7fbf19b484e0,
    format=0x60288a "\t%s\n", ap=0x7fbf19b48ca8) at vfprintf.c:246
246 vfprintf.c: No such file or directory.
(gdb)

[Rico Tzschichholz (ricotz)]

Is this still happening with the current trunk? (at least r1832)

[Nicolas Krzywinski (nsk7even)]

I am sorry to report that Docky just crashed at update of other software with version 2.2.0~bzr1835-0ubuntu1~12.04-dockycore1 from LP-PPA-docky-core

The "sorry docky crashed" window is still open and I will try to find out how to get those debug data into a text file. Sadly there is no "save this data" button...

[Nicolas Krzywinski (nsk7even)]

I found the apport crash dump and will attach it here if this works.... the file is 8 mb :/

[Felix Moreno (felix-justdust)]

it affects me too, it failed in 12.04, 12.10 and in 13.04 it closes itself even without any upgrade, every 5 minutes ys closed and you have to open it again.

[bwat47 (bwat47)]

@felix, strangly enough for me 13.04 is the first release where docky *doesn't* seem to randomly crash on me (although I'm using xubuntu). With my luck as soon as I post this it will decide to crash, but so far its been stable even after I ran a few updates and installed things from synaptic.

[bwat47 (bwat47)]

Nope, crashed when I installed steam from USC, same crash I had been getting before. I'm using 2.1.4 though I haven't tried trunk yet.

[Akoi Meexx (akoimeexx)]

Crashes in Crunchbang/Debian as well, attached output from stderr.