maximus crashed with SIGSEGV in IA__g_closure_invoke()

[Perfecto]

Binary package hint: maximus

I don't know why it has crashed

ProblemType: Crash
Architecture: amd64
DistroRelease: Ubuntu 9.04
ExecutablePath: /usr/bin/maximus
Package: maximus 0.4.3-0ubuntu1
ProcCmdline: maximus
ProcEnviron:
 PATH=(custom, user)
 LANG=es_ES.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: maximus
StacktraceTop:
 ?? ()
 ?? ()
 IA__g_closure_invoke (closure=0x1891780,
 signal_emit_unlocked_R (node=0x183c400, detail=0,
 IA__g_signal_emit_valist (instance=0x188c800,
Title: maximus crashed with SIGSEGV in IA__g_closure_invoke()
Uname: Linux 2.6.28-5-generic x86_64
UserGroups: adm admin audio cdrom clamav dialout dip fax floppy flumotion fuse gnokii lpadmin netdev plugdev pulse pulse-access pulse-rt sambashare saned scanner tape users vdr video

[Apport retracing service (apport)]

StacktraceTop:?? ()
?? ()
IA__g_closure_invoke (closure=0x1891780,
signal_emit_unlocked_R (node=0x183c400, detail=0,
IA__g_signal_emit_valist (instance=0x188c800,

[Bart Samwel (bart-samwel)]

Same problem here; x86 architecture. I was exiting a bunch of programs in a row, and then navigating to the quit button in the big on-desktop menu provided by the netbook remix. It crashed when I had the quit menu open, or just before.

[Paul Hirst (paul-hirst)]

This is affecting me too. I had just installed and configured evolution and since then upon loading firefox and the mouse preferences maximum crashed.

[Yannick Defais (sevmek)]

Same problem on my MSI wind, it appears to be somewhat random...

[Neil J. Patel (njpatel)]

Thanks everyone for reporting this bug. I'm currently working on it to see if I can reproduce the error in an environment with debugging symbols installed.

[Yannick Defais (sevmek)]

@Neil J. Patel,

I got crashes from time to time as I run the computer 24/24. If you tell me what -dbg packs i need to install i could probably provide a better trace.

[Gustavo Sverzut Barbieri (barbieri-profusion)]

@Yannick, since you're willing to install debug packages, please install at least libglib2.0-0-dbg libgtk2.0-0-dbg, also if you can deal with terminal/command line please install valgrind as well and run it like:

    valgrind --trace-children=yes --log-file=maximus-valgrind.log maximus

it should print out a log with invalid memory access and all, please attach it here. Also, I guess maximus should be printing some errors before crashing, would be good to send those as well (you can check ~/.xsession-errors).

[PirBoazo (pierre-boizot-name)]

Probleme on my acer aspire one ..;

[Yannick Defais (sevmek)]

@Gustavo,

Valgrind segfault each time i put VLC in full screen. I attach one log of valgring.

e.g.:
% valgrind --trace-children=yes --log-file=maximus-valgrind3.log maximus
no maximize: false
** (maximus:4327): DEBUG: Window opened: res_name=Xchat -- class_name=xchat
** (maximus:4327): DEBUG: Window opened: res_name=Gnome-terminal -- class_name=gnome-terminal
** (maximus:4327): DEBUG: Window opened: res_name=Thunderbird-bin -- class_name=gecko
** (maximus:4327): DEBUG: Window opened: res_name=Firefox -- class_name=Navigator
** (maximus:4327): DEBUG: Window opened: res_name=Thunderbird-bin -- class_name=gecko
** (maximus:4327): DEBUG: Window opened: res_name= -- class_name=
** (maximus:4327): DEBUG: Window opened: res_name= -- class_name=
** (maximus:4327): DEBUG: Window opened: res_name=(null) -- class_name=(null)
zsh: segmentation fault (core dumped) valgrind --trace-children=yes --log-file=maximus-valgrind3.log maximus

[Yannick Defais (sevmek)]

@Gustavo,

I hope there is a better trace here:
https://bugs.launchpad.net/ubuntu/+source/maximus/+bug/351216

[Harald Schilly (harald-schilly)]

crashed for me when opening screen resolution settings in preferences

[Gustavo Sverzut Barbieri (barbieri-profusion)]

@Yannick, I cannot open that bug, permission denied. Could you attach it here?

I'm trying to reproduce it here, but no luck so far. Could you please update to newest packages and try again and report exactly what you did to reproduce it? Is it just playing a random movie in fullscreen with VLC? I did that and nothing, also tried "Screen Resolution" and no problem. Bad thing is that we lack libwnck-dbg :-(

[Yannick Defais (sevmek)]

@Gustavo,

Sorry, I just release the bug was tagged private, I changed it to public, thus you should have access to it now. I hope the bug contains a procedure which will help you reproduce.

Best regards,
Yannick

[Gustavo Sverzut Barbieri (barbieri-profusion)]

@Yannick, which VLC are you using? I'm testing it on Dell Mini 9 (hardy) with latest packages, VLC from that repository and it works. That is vlc version is 0.8.6.release.e+x264svn20071224+faad2.6.1-0ubuntu3.1, I'll test with Jaunty in few minutes.

My machine is running Jaunty, Intel 965 graphics driver and it does not happen here. VLC 0.9.8a-1ubuntu4.

Since I see you're experienced (never saw a newbie using zsh), could you compile maximus with debug symbols? Should be as easy as:

   apt-get build-dep maximus
   bzr lp:maximus
   cd maximus && ./autogen.sh --prefix=/usr CFLAGS="-O0 -g" && make all install

If you have some kind of local/user tree (/usr/local, ~/usr) with environment variables all set (PATH, LD_LIBRARY_PATH...), then it would be better as you'd not damage your system. If you need more help let me know.

With that build, run valgrind+maximus again, it should report meaningful information, even if it crashes.

Thanks for your time!

[Yannick Defais (sevmek)]

Gustavo Sverzut Barbieri a écrit :
> @Yannick, which VLC are you using? I'm testing it on Dell Mini 9 (hardy)
> with latest packages, VLC from that repository and it works. That is vlc
> version is 0.8.6.release.e+x264svn20071224+faad2.6.1-0ubuntu3.1, I'll
> test with Jaunty in few minutes.

I'm running Jaunty, VLC is 0.9.8a-1ubuntu4

>
> My machine is running Jaunty, Intel 965 graphics driver and it does not
> happen here. VLC 0.9.8a-1ubuntu4.

It's not a 100%, play with it more longer... I also have some switch
between windows for no reasons sometimes.

>
> Since I see you're experienced (never saw a newbie using zsh), could you
> compile maximus with debug symbols? Should be as easy as:
>
> apt-get build-dep maximus
> bzr lp:maximus
> cd maximus && ./autogen.sh --prefix=/usr CFLAGS="-O0 -g" && make all install

I do not have much time, i'll give a try ASAP...

>
> If you have some kind of local/user tree (/usr/local, ~/usr) with
> environment variables all set (PATH, LD_LIBRARY_PATH...), then it would
> be better as you'd not damage your system. If you need more help let me
> know.
>
> With that build, run valgrind+maximus again, it should report meaningful
> information, even if it crashes.
>
> Thanks for your time!
>

[Paul Larson (pwlars)]

stacktrace looks slightly different, but I'm betting this is a dup of bug 330397
Could someone who was able to reproduce this check?

[andrew brown (arnie-geek)]

Saw that this was updated recently, just added in case there's some difference before/after.

[macpablo (t-bordeleau)]

Acer aspire one, netbook remix, -- crashed while closing Evolution

[albert fishnets (mateolingerhaus)]

Acer Aspire One Karmic NBR Beta crashed while closing F-spot.

[aecabo (aecabo)]

Happens in my Eee 701 4gb Karmic NBR, It crash when it want, not for some reason.

[Paul Larson (pwlars)]

This looks somewhat similar to bug 421019, but I'd like to leave it separate for now just in case. To mirror the request made in that bug, which I think is also valid here:
"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."
Please make sure to fully update the system first. Also, if someone has a reliable way to reproduce it, that would be extremely helpful. I've been trying for a good portion of the morning to reproduce this with no luck so far. Hopefully that's a good thing :)
Thanks!

[Mark Cariaga (mzc)]

hi,

so far I cannot reproduce this bug anymore after the update. I have been installing/unstalling software, multi- tasking, etc but still unable to reproduce the bug.

On Oct 9, 2009, at 9:11 AM, Paul Larson <email address hidden> wrote:

This looks somewhat similar to bug 421019, but I'd like to leave it separate for now just in case. To mirror the request made in that bug, which I think is also valid here:
"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."
Please make sure to fully update the system first. Also, if someone has a reliable way to reproduce it, that would be extremely helpful. I've been trying for a good portion of the morning to reproduce this with no luck so far. Hopefully that's a good thing :)
Thanks!

** Changed in: maximus (Ubuntu)
  Importance: Undecided => High

** Changed in: maximus (Ubuntu)
      Status: In Progress => Incomplete

--
maximus crashed with SIGSEGV in IA__g_closure_invoke()
https://bugs.launchpad.net/bugs/321957
You received this bug notification because you are a direct subscriber
of the bug.

Status in “maximus” package in Ubuntu: Incomplete

Bug description:
Binary package hint: maximus

I don't know why it has crashed

ProblemType: Crash
Architecture: amd64
DistroRelease: Ubuntu 9.04
ExecutablePath: /usr/bin/maximus
Package: maximus 0.4.3-0ubuntu1
ProcCmdline: maximus
ProcEnviron:
PATH=(custom, user)
LANG=es_ES.UTF-8
SHELL=/bin/bash
Signal: 11
SourcePackage: maximus
StacktraceTop:
?? ()
?? ()
IA__g_closure_invoke (closure=0x1891780,
signal_emit_unlocked_R (node=0x183c400, detail=0,
IA__g_signal_emit_valist (instance=0x188c800,
Title: maximus crashed with SIGSEGV in IA__g_closure_invoke()
Uname: Linux 2.6.28-5-generic x86_64
UserGroups: adm admin audio cdrom clamav dialout dip fax floppy flumotion fuse gnokii lpadmin netdev plugdev pulse pulse-access pulse-rt sambashare saned scanner tape users vdr video

      __________________________________________________________________
Looking for the perfect gift? Give the gift of Flickr!

http://www.flickr.com/gift/

[Paul Larson (pwlars)]

Ok, going to close this then since you are no longer able to reproduce it. If you encounter this again, please feel free to open a new bug on it with updated debug information from apport. Thanks!