Ticket #432 (closed defect: invalid)

Opened 3 years ago

Last modified 3 years ago

Opening Pulse Audio crashes

Reported by: nicholas Owned by: lennart
Milestone: Component: pavucontrol
Keywords: Cc:

Description (last modified by lennart) (diff)

System: Linux 2.6.26.6-49.fc8 #1 SMP Fri Oct 17 15:59:36 EDT 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Permissive
Accessibility: Disabled
GTK+ Theme: Glossy
Icon Theme: gnome
Memory status: size: 0 vsize: 0 resident: 0 share: 0 rss: 0 rss_rlim: 0
CPU usage: start_time: 0 rtime: 0 utime: 0 stime: 0 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 0
----------- .xsession-errors ---------------------
pulsesink.c(399): gst_pulsesink_prepare (): /playbin0/abin/audiosink/audiosink-actual-sink-pulse
ERROR: pipeline doesn't want to preroll.
Setting pipeline to NULL ...
FREEING pipeline ...
** Message: Error: Failed to connect stream: Invalid argument
pulsesink.c(399): gst_pulsesink_prepare (): /play/visbin/abin/audiosinkbin/audio-sink/bin6/autoaudiosink1/autoaudiosink1-actual-sink-pulse
Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x3e00020 (After you')
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
(muine:6754): GStreamer-CRITICAL **: 
Trying to dispose element play, but it is not in the NULL state.
You need to explicitly set elements to the NULL state before
dropping the final reference, to allow them to clean up.

Change History

Changed 3 years ago by coling

Not really sure what you are trying to report here...

This bug is certainly not in pavucontrol as you've reported it but I also do not see what the problem is.

The error would appear to indicate that someting is trying to use gstreamer to play to pulseaudio before the pulseaudio daemon itself is started.

This is almost certainly due to a startup sound or similar and will be due to how your distro starts pulseaudio at session initialisation.

It seems you are using fc8 as well which is pretty old. I'd upgrade to fc10 before reporting upstream bugs here or perhaps try and get support from a fedora support channel if you cannot upgrade.

Sorry I can't be more helpful, but hopefully I've pointed you in the right direction :)

Changed 3 years ago by lennart

  • description modified (diff)

Changed 3 years ago by lennart

  • status changed from new to closed
  • resolution set to invalid

Sorry, I see no bug here. Closing now. Feel free to reopen if you can provide a more elaborate explanation what goes wrong.

Note: See TracTickets for help on using tickets.