Docky crashes when runing update manager

Bug #1036671 reported by AD5XJ
88
This bug affects 19 people
Affects Status Importance Assigned to Milestone
Docky
Incomplete
Medium
Unassigned

Bug Description

Docky consistently crashes when running Update Manager.

The problem seems to be with the Qt QMF framework dying during the update process.

It can be restarted. No particular error is emitted or displayed by error notification. Does not produce a stack trace - none available through apport. No error report menu selection in Docky available.

This has been a problem since v2.0 came out but not resolved on 32 bit or 64 bit.

Environment:
AMD Athlon 64 3800+ 1Gb ram 30 Gb free disk

Ubuntu 12.04 precise 64 bit (last update 08/14/2012)
Kernel 3.2.0-29-generic
GNOME 3.4.2
NVidia GForce video
Qt v4.8 Framework native to Ubuntu 12.04

Docky 2.2.0
Mono 2.10.8-1ubuntu2.2

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

Docky does not use QT. It uses GTK.

Revision history for this message
AD5XJ (ad5xj) wrote :

OK well I do not know the internals of Docky but that does not degate the fact that it crashes frequently during the update process and as far as I can tell no other time.

security vulnerability: no → yes
security vulnerability: yes → no
Revision history for this message
AD5XJ (ad5xj) wrote :

Ok, I was hoping a fix would come with 12.10. However, while testing 12.10 I find no difference in Docky. Crashes still occur during the configuration / installation phase of most updates from the Update Manager. This is an irratating problem and has been around for several versions of Docky and Ubuntu. It is time to fix it.

Revision history for this message
AD5XJ (ad5xj) wrote :

P.S. I even downloaded and installed the 32 bit version of 12.10 and the problem appears there as well. With this string of events, I am convinced the problem is with Docky and not the underlying support structures.

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

You just reported this a month ago... calm down.

You haven't given us a single stack trace from your crashes. If it is so reproducible, you should be able to get a stack trace.

Changed in docky:
status: New → Incomplete
importance: Undecided → Medium
Revision history for this message
AD5XJ (ad5xj) wrote :

I AM calm. As you can read above...this is not a new subject. Just one I bring up again in this version.

While we are on the subject - I suggested when 11 came out that the report a bug / apport hooks be added to Docky and as yet it does not appear on the menu nor is there an indication apport is gathering information to report.

It would probably be much easier to report a stack trace if one were produced. So far nothing is produced just the disappearance of the application. No stack trace no error file no nothing!

If it were available I would gladly provide it.

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

Mono always dumps a stack trace when it crashes. The trace is dumped to the console that started the process, so depending on how you start Docky that may mean it is in your ~/.xsession-errors file or you may need to just open a terminal, start Docky (with the -d flag) and wait for it to crash.

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

Where is the bug report requesting apport support for Docky?

Marking this bug duplicate of bug 1005946.

Revision history for this message
AD5XJ (ad5xj) wrote :

Well it will take some time searching through my past posts to find the request. But, I would think that given the current trend of Ubuntu supported apps all providing this feature in non-ubuntu supported apps would be a logical expectation. Maybe that is just me.

The app has not failed on the last couple updates but it did render this non-fatal error running in debug mode.-
[Fatal 18:18:07.411] [GLib-GObject] g_object_ref: assertion `G_IS_OBJECT (object)' failed
several times during the debug session.

If I did not mention it before I am on the Unity windows manager and compiz is updated to the latest. The Unity launcher panel does not crash at all and performs all the compositing (and more) demonstrated in Docky.

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

I doubt Docky 2.x will have apport support. Plank already does, so Docky 3 will.

Revision history for this message
AD5XJ (ad5xj) wrote :

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

Revision history for this message
Nicolas Krzywinski (nsk7even) wrote :

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.

Revision history for this message
Ray Bond (rbond87) wrote :
Download full text (5.1 KiB)

This also happens to me on all machines that I use. This machine is a Dell E6510 with a Core i7 620M, kernel 3.8-rc4, ubuntu 12.04-based distribution using gnome-shell, using NVIDIA graphics, version 310.32. During this morning's update, this is the related part of my .xsession-errors file:

06:13:37.787 DEBUG MainWindow:1122 position 60 scrobble point 125 status 0
06:13:47.788 DEBUG MainWindow:1122 position 70 scrobble point 125 status 0
06:13:57.787 DEBUG MainWindow:1122 position 80 scrobble point 125 status 0
06:14:07.787 DEBUG MainWindow:1122 position 90 scrobble point 125 status 0
06:14:17.787 DEBUG MainWindow:1122 position 100 scrobble point 125 status 0
06:14:27.787 DEBUG MainWindow:1122 position 110 scrobble point 125 status 0
[Fatal 06:14:34.017] [GLib-GObject] g_object_ref: assertion `G_IS_OBJECT (object)' failed
Stacktrace:

Native stacktrace:

06:14:37.787 DEBUG MainWindow:1122 position 120 scrobble point 125 status 0
[Info 06:14:40.646] Docky version: 2.1.4 Release
[Info 06:14:40.663] Kernel version: 3.8.0.43
[Info 06:14:40.664] CLR version: 4.0.30319.1
[Info 06:14:41.100] [ThemeService] Setting theme: LuninuXOS
[Warn 06:14:41.121] [DesktopItemService] Could not find remap file '/home/ray/.local/share/docky/remaps.ini'!
[Info 06:14:41.370] [DockServices] Dock services initialized.
[Info 06:14:42.019] [PluginManager] Loaded "Trash".
Window manager warning: Log level 8: _shell_embedded_window_unrealize: assertion `SHELL_IS_EMBEDDED_WINDOW (window)' failed
[Info 06:14:43.106] [Helper] Starting banshee_control.py
[Info 06:14:43.125] [Helper] Starting liferea_badge.py
[Info 06:14:43.130] [Helper] Starting mpd_control.py
[Info 06:14:43.134] [Helper] Starting open_terminal_here.py
[Info 06:14:43.141] [Helper] Starting skype_control.py
[Info 06:14:43.165] [HelperService] Helper added: /usr/share/dockmanager/scripts/banshee_control.py
[Info 06:14:43.173] [HelperService] Helper added: /usr/share/dockmanager/scripts/deluge_badge.py
[Info 06:14:43.173] [HelperService] Helper added: /usr/share/dockmanager/scripts/emesene_control.py
[Info 06:14:43.173] [HelperService] Helper added: /usr/share/dockmanager/scripts/gajim_badge.py
[Info 06:14:43.173] [HelperService] Helper added: /usr/share/dockmanager/scripts/gtg_menus.py
[Info 06:14:43.173] [HelperService] Helper added: /usr/share/dockmanager/scripts/liferea_badge.py
[Info 06:14:43.173] [HelperService] Helper added: /usr/share/dockmanager/scripts/mpd_control.py
[Info 06:14:43.173] [HelperService] Helper added: /usr/share/dockmanager/scripts/open_terminal_here.py
[Info 06:14:43.173] [HelperService] Helper added: /usr/share/dockmanager/scripts/pidgin_control.py
[Info 06:14:43.173] [HelperService] Helper added: /usr/share/dockmanager/scripts/pithos_control.py
[Info 06:14:43.174] [HelperService] Helper added: /usr/share/dockmanager/scripts/rhythmbox_control.py
[Info 06:14:43.174] [HelperService] Helper added: /usr/share/dockmanager/scripts/skype_control.py
[Info 06:14:43.174] [HelperService] Helper added: /usr/share/dockmanager/scripts/tomboy_menus.p...

Read more...

Revision history for this message
Felix Moreno (felix-justdust) wrote :

It's still present in 13.04 bunt it seems it crash more often in 13.04... no errors just it dissapear and you have to run it again...

Revision history for this message
Evgeny Shpilevsky (ftdebugger) wrote :

uname -a
Linux laptop 3.8.0-25-generic #37-Ubuntu SMP Thu Jun 6 20:47:07 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux

[Info 16:53:42.609] Docky version: 2.1.4 Release
[Info 16:53:42.613] Kernel version: 3.8.0.25
[Info 16:53:42.614] CLR version: 4.0.30319.1

[Fatal 16:45:01.479] [GLib-GObject] g_object_ref: assertion `G_IS_OBJECT (object)' failed
Stacktrace:

Native stacktrace:

Segmentation fault

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

Other bug subscribers

Remote bug watches

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