Docky.exe crashed with SIGSEGV

Bug #557460 reported by XFACT
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
docky (Ubuntu)
New
Undecided
Unassigned

Bug Description

Binary package hint: docky

This is first time I have noticed this kind of weird apport report in Ubuntu 10.04 Beta 1, even the "Doocky.exe" makes me confused, because EXE is not Ubuntu stuff. I am using Docky 2.0.1 from the Ubuntu software center.

Please help me to figure out whats the matter.

Thanks

ProblemType: Crash
DistroRelease: Ubuntu 10.04
Package: docky 2.0.1-1~ubuntu1
ProcVersionSignature: Ubuntu 2.6.32-19.28-generic 2.6.32.10+drm33.1
Uname: Linux 2.6.32-19-generic i686
NonfreeKernelModules: nvidia
Architecture: i386
Date: Wed Apr 7 22:56:23 2010
ExecutablePath: /usr/lib/docky/Docky.exe
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
InterpreterPath: /usr/bin/mono
PackageArchitecture: all
ProcCmdline: mono --debug /usr/lib/docky/Docky.exe
ProcEnviron:
 LANGUAGE=en_US:en
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x80c96b3: mov 0x58(%eax),%edx
 PC (0x080c96b3) ok
 source "0x58(%eax)" (0x00000058) not located in a known VMA region (needed readable region)!
 destination "%edx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: docky
StacktraceTop:
 ?? ()
 ?? ()
 ?? ()
 ?? ()
 ?? ()
Title: Docky.exe crashed with SIGSEGV
UserGroups:

Revision history for this message
XFACT (avinandan) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 ?? ()
 ?? ()
 ?? ()
 ?? ()
 ?? ()

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
tags: added: apport-failed-retrace
tags: removed: need-i386-retrace
Revision history for this message
XFACT (avinandan) wrote :
Download full text (9.0 KiB)

Several times docky crashes, with this same problem and I don't know why...

I have terminaled it and got this:

$ docky
[Info 13:58:35.175] Docky version: 2.0.1 Release
[Info 13:58:35.192] Kernel version: 2.6.32.19
[Info 13:58:35.195] CLR version: 2.0.50727.1433
**
ERROR:gkr-operation.c:169:gkr_operation_set_result: assertion failed: ((int) res != INCOMPLETE)
Stacktrace:

  at (wrapper managed-to-native) Gnome.Keyring.Ring.gnome_keyring_find_items_sync (Gnome.Keyring.ItemType,intptr,intptr&) <0x00004>
  at (wrapper managed-to-native) Gnome.Keyring.Ring.gnome_keyring_find_items_sync (Gnome.Keyring.ItemType,intptr,intptr&) <0xffffffff>
  at Gnome.Keyring.Ring.Find (Gnome.Keyring.ItemType,System.Collections.Hashtable) <0x00073>
  at Docky.Services.Preferences`1<object>.GetSecure<object> (string,object) <0x000ae>
  at (wrapper static-rgctx-invoke) Docky.Services.Preferences`1<GMail.GMailPreferences>.static_rgctx_invoke_string__this___string_string (string,string) <0xffffffff>
  at GMail.GMailPreferences.get_Password () <0x00033>
  at GMail.GMailAtom.<CheckGMail>m__8 () <0x0038f>
  at Docky.Services.SystemService/<RunOnThread>c__AnonStorey9.<>m__B () <0x0001c>
  at (wrapper runtime-invoke) object.runtime_invoke_void__this__ (object,intptr,intptr,intptr) <0xffffffff>

Native stacktrace:

 mono() [0x80ca6e4]
 [0x955410]
 /lib/tls/i686/cmov/libc.so.6(abort+0x182) [0xe4da72]
 /lib/libglib-2.0.so.0(g_assertion_message+0x163) [0x74edd3]
 /lib/libglib-2.0.so.0(+0x6342d) [0x74f42d]
 /usr/lib/libgnome-keyring.so.0(+0x7802) [0x944b802]
 /usr/lib/libgnome-keyring.so.0(+0x6b55) [0x944ab55]
 /usr/lib/libgnome-keyring.so.0(+0x78fc) [0x944b8fc]
 /usr/lib/libgnome-keyring.so.0(+0x85b1) [0x944c5b1]
 /usr/lib/libgnome-keyring.so.0(gnome_keyring_find_items_sync+0x45) [0x9455985]
 [0x18c3bc3]
 [0x18c3334]
 [0x18c3067]
 [0x18c2fa4]
 [0x18c2f7c]
 [0x18c60f8]
 [0x181acd5]
 [0x9dde59]
 mono(mono_runtime_delegate_invoke+0x34) [0x8110ef4]
 mono() [0x815285b]
 mono() [0x81c3062]
 mono() [0x81e1925]
 /lib/tls/i686/cmov/libpthread.so.0(+0x596e) [0xc5096e]
 /lib/tls/i686/cmov/libc.so.6(clone+0x5e) [0xeed9de]

Debug info from gdb:

[Thread debugging using libthread_db enabled]
[New Thread 0x1ca2b70 (LWP 2393)]
[New Thread 0x2becb70 (LWP 2392)]
[New Thread 0x1a3ab70 (LWP 2391)]
[New Thread 0x1334b70 (LWP 2386)]
[New Thread 0x4afb70 (LWP 2385)]
0x00e54942 in ?? () from /lib/tls/i686/cmov/libc.so.6
  6 Thread 0x4afb70 (LWP 2385) 0x00955422 in __kernel_vsyscall ()
  5 Thread 0x1334b70 (LWP 2386) 0x00955422 in __kernel_vsyscall ()
  4 Thread 0x1a3ab70 (LWP 2391) 0x00955422 in __kernel_vsyscall ()
  3 Thread 0x2becb70 (LWP 2392) 0x00955422 in __kernel_vsyscall ()
  2 Thread 0x1ca2b70 (LWP 2393) 0x00955422 in __kernel_vsyscall ()
* 1 Thread 0x1106f0 (LWP 2378) 0x00e54942 in ?? ()
   from /lib/tls/i686/cmov/libc.so.6

Thread 6 (Thread 0x4afb70 (LWP 2385)):
#0 0x00955422 in __kernel_vsyscall ()
#1 0x00c58736 in nanosleep () from /lib/tls/i686/cmov/libpthread.so.0
#2 0x081a6af8 in ?? ()
#3 0x00c5096e in start_thread () from /lib/tls/i686/cmov/libpthread.so.0
#4 0x00eed9de in clone () from /lib/tls/i686/cmov/libc.so.6

Thread 5 (Thread 0x1334b70 (LWP 2386)):
#0 0x00955422 ...

Read more...

Iain Lane (laney)
visibility: private → public
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.