Bug 48928

Summary: pavucontrol 1.0 segfault on start, related to the pulsecore/pdispatch.c?
Product: PulseAudio Reporter: Rafał Miłecki <zajec5>
Component: pavucontrolAssignee: pulseaudio-bugs
Status: RESOLVED MOVED QA Contact: pulseaudio-bugs
Severity: normal    
Priority: medium CC: lennart
Version: unspecified   
Hardware: Other   
OS: All   
Whiteboard:
i915 platform: i915 features:

Description Rafał Miłecki 2012-04-19 12:43:53 UTC
I use pulseaudio provided with openSUSE 12.1: pulseaudio-1.1-1.2.i586 package.

However starting pavucontrol (any: system-supplied or self-compiled) results in blinking "Volume Control" window and segmentation fault.

I'm assigning this report to "pavucontrol", please re-assing if this should be "core" or sth else.
Comment 1 Rafał Miłecki 2012-04-19 12:52:34 UTC
(gdb) backtrace
#0  0xb6b4796c in pa_pdispatch_register_reply (pd=0x806df80, tag=3, timeout=30, cb=0xb75048c0 <context_get_server_info_callback>, userdata=
    0x8203b70, free_cb=0xb7510ec0 <pa_operation_unref>) at pulsecore/pdispatch.c:379
#1  0xb74fb0dd in pa_context_send_simple_command (c=0x8203b70, command=20, internal_cb=0xb75048c0 <context_get_server_info_callback>, cb=
    0x806df80, userdata=0x81f3a60) at pulse/context.c:1191
#2  0xb750639d in pa_context_get_server_info (c=0x8203b70, cb=0x806df80, userdata=0x81f3a60) at pulse/introspect.c:132
#3  0x0806d7b4 in ?? ()
#4  0xb74f83a8 in pa_context_set_state (st=PA_CONTEXT_READY, c=0x8203b70) at pulse/context.c:291
#5  pa_context_set_state (c=0x8203b70, st=PA_CONTEXT_READY) at pulse/context.c:279
#6  0xb74fbb08 in setup_complete_callback (pd=0x824bcb0, command=2, tag=1, t=0x825a900, userdata=0x8203b70) at pulse/context.c:497
#7  0xb6b4813d in run_action (pd=0x824bcb0, r=0x824d500, command=2, ts=0x825a900) at pulsecore/pdispatch.c:274
#8  0xb6b48540 in pa_pdispatch_run (pd=0x824bcb0, packet=0x81eae60, creds=0x0, userdata=0x8203b70) at pulsecore/pdispatch.c:326
#9  0xb74f955d in pstream_packet_callback (p=0x825e500, packet=0x81eae60, creds=0x0, userdata=0x8203b70) at pulse/context.c:335
#10 0xb6b4daf6 in do_read (p=0x825e500) at pulsecore/pstream.c:816
#11 do_something (p=0x825e500) at pulsecore/pstream.c:184
#12 0xb6b37fc2 in callback (m=0x81cfc4c, e=0x82492e8, fd=10, f=PA_IO_EVENT_INPUT, userdata=0x8206a00) at pulsecore/iochannel.c:119
#13 0xb753cb7a in dispatch_func (source=0x81cfc18, callback=0, userdata=0x0) at pulse/glib-mainloop.c:585
#14 0xb7586e2f in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#15 0xb7587560 in ?? () from /usr/lib/libglib-2.0.so.0
#16 0xb7587b6b in g_main_loop_run () from /usr/lib/libglib-2.0.so.0
#17 0xb77f0235 in gtk_main () from /usr/lib/libgtk-3.so.0
#18 0xb7e336d4 in Gtk::Main::run_impl() () from /usr/lib/libgtkmm-3.0.so.1
#19 0xb7e33f18 in Gtk::Main::run(Gtk::Window&) () from /usr/lib/libgtkmm-3.0.so.1
#20 0x08054307 in ?? ()
#21 0xb726f003 in __libc_start_main () from /lib/libc.so.6
#22 0x080546c9 in ?? ()
Backtrace stopped: Not enough registers or memory available to unwind further

The #0 line is not fully printed above, so I've checked pdispatch.c for the source. It looks like that:
pa_assert_se(r->time_event = pd->mainloop->time_new(pd->mainloop, &tv, timeout_callback, r));
Comment 2 Rafał Miłecki 2012-04-19 12:55:34 UTC
(gdb) frame 0
#0  0xb6b4796c in pa_pdispatch_register_reply (pd=0x806df80, tag=3, timeout=30, cb=0xb75048c0 <context_get_server_info_callback>, userdata=
    0x8203b70, free_cb=0xb7510ec0 <pa_operation_unref>) at pulsecore/pdispatch.c:379
379         pa_assert_se(r->time_event = pd->mainloop->time_new(pd->mainloop,
(gdb) print r->time_event
$1 = (pa_time_event *) 0x81048f0
(gdb) print pd->mainloop
$2 = (pa_mainloop_api *) 0x2424548b
(gdb) print pd->mainloop->time_new
Cannot access memory at address 0x2424549f
(gdb) print tv
$3 = {tv_sec = 134542509, tv_usec = -1219425075}
(gdb) print timeout_callback
$4 = {void (pa_mainloop_api *, pa_time_event *, const struct timeval *, void *)} 0xb6b481e0 <timeout_callback>
(gdb) print r
$5 = (struct reply_info *) 0x8258628

So it seems that the pd->mainloop->time_new pointer is lacking.

Is there any other additional info I can provide?
Comment 3 GitLab Migration User 2018-07-30 09:30:41 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/pulseaudio/pavucontrol/issues/36.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.