pm-hibernate / gnome-mplayer process disappears after de-hibernation

[GoogleCodeExporter]

What steps will reproduce the problem?
1. start self-compiled gnome-mplayer with panscan option
2. exec /usr/sbin/pm-hibernate
3. press the start button on the desktop case

What is the expected output? What do you see instead?
gnome-mplayer should be still there and should be able to un-pause the movie...
but in fact the gnome-mplayer window is gone and
in syslog is a segfault message:
gnome-mplayer[2785]: segfault at 30 ip 000000000043ddd9 sp 00007fffc0cd6f90 
error 6 in gnome-mplayer[400000+4f000]

What version of the product are you using? On what operating system?
gnome-mplayer-1.0.2 (self compiled with "enable_panscan")
fedora core 14 fully updated

Please provide any additional information below.
it seems to be related to the amd/ati catalyst/radeon graphix driver, because: 
previously with the nvidia driver gnome-mplayer was still there...

Original issue reported on code.google.com by goo...@wgboome.org on 15 Apr 2011 at 12:47

[GoogleCodeExporter]

Can you compile gnome-mplayer with symbols so that a backtrace might be 
generated. Also, have you tried the system with the radeon free driver rather 
than the ATI driver.

If you said this works with the nvidia driver, then there is probably not much 
I can do about the problem.

Original comment by kdeko...@gmail.com on 15 Apr 2011 at 1:04

[GoogleCodeExporter]

thank u for ur reply...

it really looks like the amd/ati driver does something funny - i just thought a 
segfault might be an application bug...

i will first try a workaround:
before pm-hibernate i send gnome-mplayer a SIGSTOP and after power on i send a 
SIGCONT... so it cant crash, while the amd driver does funny things... :-)

if that fails, i will try ur debug symbols plan...

-arne

Original comment by goo...@wgboome.org on 15 Apr 2011 at 4:06

[GoogleCodeExporter]

the SIGSTOP-workaround failed...

after the next deep-sleep-phase i will save the core dump file and look at 
it... :-)

-arne

Original comment by goo...@wgboome.org on 16 Apr 2011 at 1:07

[GoogleCodeExporter]

now i tested it again:
1. a standalone mplayer instance survived the deep sleep...
2. a gnome-mplayer instance had a segfault:
Program terminated with signal 11, Segmentation fault.
#0  gm_audio_pa_sink_update_volume_cb (c=0x1b66540, i=0x0, eol=-1, data=0x0)
    at gm_audio.c:399
399             device->volume = 0.0;
Missing separate debuginfos, use: debuginfo-install 
gnome-mplayer-1.0.2-1.fc14.x86_64
(gdb) where
#0  gm_audio_pa_sink_update_volume_cb (c=0x1b66540, i=0x0, eol=-1, data=0x0)
    at gm_audio.c:399
#1  0x0000003087c15810 in ?? () from /usr/lib64/libpulse.so.0
#2  0x0000003087826e33 in ?? () from /usr/lib64/libpulsecommon-0.9.21.so
#3  0x0000003087827339 in pa_pdispatch_run ()
   from /usr/lib64/libpulsecommon-0.9.21.so
#4  0x0000003087c0eb6d in ?? () from /usr/lib64/libpulse.so.0
#5  0x000000308782ba04 in ?? () from /usr/lib64/libpulsecommon-0.9.21.so
#6  0x0000003087001c4a in ?? () from /usr/lib64/libpulse-mainloop-glib.so.0
#7  0x000000370b841e33 in g_main_context_dispatch ()
   from /lib64/libglib-2.0.so.0
#8  0x000000370b842610 in ?? () from /lib64/libglib-2.0.so.0
#9  0x000000370b842c82 in g_main_loop_run () from /lib64/libglib-2.0.so.0
#10 0x000000308594b0b7 in gtk_main () from /usr/lib64/libgtk-x11-2.0.so.0
#11 0x0000000000434159 in main (argc=2, argv=0x7fff65a6aaf8) at main.c:1245

the problem seems to come from this
    } else {
        // eol == -1 when the index requested is not found
        if (eol == -1)
            device->volume = 0.0;
    }
in
i added this " && device" to the "if condition"...

let's c if it works...
i dont like to power cycle so often, so i have to wait until tomorrow... :-)

-arne

Original comment by goo...@wgboome.org on 17 Apr 2011 at 9:53

[GoogleCodeExporter]

Yup, that is the change I would have made to that code as well, won't hurt 
anything to have it and it could stop the crash. Change committed.

Original comment by kdeko...@gmail.com on 17 Apr 2011 at 1:30

[GoogleCodeExporter]

works fine again now... -arne

Original comment by goo...@wgboome.org on 18 Apr 2011 at 7:50

[GoogleCodeExporter]

Original comment by kdeko...@gmail.com on 18 Apr 2011 at 12:40

• Changed state: Fixed