maximus crashed with SIGSEGV in g_closure_invoke()

[StuJordan]

Binary package hint: maximus

Crash window appeared after loading remote desktop client and clicking File -> QuickConnect

ProblemType: Crash
Architecture: i386
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/maximus
Package: maximus 0.4.9-0ubuntu2
ProcCmdline: maximus
ProcEnviron:
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-8.28-generic
SegvAnalysis:
 Segfault happened at: 0x804bf8e <g_slist_free@plt+6082>: orl $0x2,(%eax)
 PC (0x0804bf8e) ok
 source "$0x2" ok
 destination "(%eax)" (0x0063710c) in non-writable VMA region: 0x00608000-0x0064c000 r-xp /usr/lib/libgobject-2.0.so.0.2105.0
SegvReason: writing VMA /usr/lib/libgobject-2.0.so.0.2105.0
Signal: 11
SourcePackage: maximus
StacktraceTop:
 ?? ()
 ?? () from /usr/lib/libwnck-1.so.22
 g_closure_invoke () from /usr/lib/libgobject-2.0.so.0
 ?? () from /usr/lib/libgobject-2.0.so.0
 g_signal_emit_valist () from /usr/lib/libgobject-2.0.so.0
Tags: ubuntu-unr
Title: maximus crashed with SIGSEGV in g_closure_invoke()
Uname: Linux 2.6.31-8-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

[Apport retracing service (apport)]

This crash has the same stack trace characteristics as bug #351527. However, the latter was already fixed in an earlier package version than the one in this report. This might be a regression or because the problem is in a dependent package.

[István Miklós Antal (djdarkmanx)]

Architecture: i386
DistroRelease: Ubuntu 9.10
Package: maximus 0.4.11-0ubuntu1
PackageArchitecture: i386
ProcEnviron:
 SHELL=/bin/bash
 LANG=en_US.UTF-8
ProcVersionSignature: Ubuntu 2.6.31-10.32-generic
Tags: ubuntu-unr
Uname: Linux 2.6.31-10-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

[macpablo (t-bordeleau)]

I just had this while changing my status in pidgin.

[Mark Cariaga (mzc)]

crash report just popped up while working on System Testing.

[Steve Gredell (steve-gredell)]

I received this crash report after using the Desktop Switcher program, which is usually a bad idea anyways. I'm not sure exactly what caused it...sorry

[David Barth (dbarth)]

We closed some crashers with maximus recently. Can you give a try to a newer version? The current version of maximus is: 0.4.14-0ubuntu1

Can you report whether the bug still occurs with the new version?

Thanks

[David Barth (dbarth)]

Can you try to reproduce with the latest maximus version? The report shows that it's an old version that was (indeed) affected. The fix that was made in maximus fixes different crashers.

[StuJordan (r-launchpad-stuartjordan-co-uk)]

Hi, I haven't seen this error for the last few weeks. I assume that either the problem was one-off or it is now fixed (for me at least).

[Steve Kowalik (stevenk)]

Due to the submitter reporting that they haven't seen this in some time, I am going to mark this bug as closed.