Bug 95310

Summary: pavucontrol fails to start up, connect to pulseaudio
Product: PulseAudio Reporter: Alex <alupu01>
Component: pavucontrolAssignee: pulseaudio-bugs
Status: RESOLVED MOVED QA Contact: pulseaudio-bugs
Severity: normal    
Priority: medium CC: lennart
Version: unspecified   
Hardware: x86 (IA32)   
OS: Linux (All)   
Whiteboard:
i915 platform: i915 features:
Attachments: 'make install' log of pavucontrol-3.0 build/install

Description Alex 2016-05-06 23:03:19 UTC
System: 32-bit BeyondLinuxFromScratch (i686-pc-linux-gnu)
Machine:  ASUS P8H77-I, i7-3770 3.4GHz, 16G
pulseaudio v8.0 (compiled from sources)
pavucontrol v3.0 (compiled from sources)
Linux kernel v4.4.5 (compiled from sources)
X.Org X Server v1.18.2 (compiled from sources)
xterm v324 (compiled from sources)

In an Xterm:
% pulseaudio --start --daemonize=no
% pavucontrol
Gtk:ERROR:gtkiconhelper.c:491:ensure_surface_for_gicon: assertion failed: (destination)
Aborted

Note:  64-bit Arch Linux, same machine (hardware), similar software and
sound configuration (/etc/asound.conf, /etc/pulse/*)
does NOT exhibit this problem.

Thank you,
-- Alex
Comment 1 Arun Raghavan 2016-05-07 03:22:14 UTC
Have you done a make install for pavucontrol?
Comment 2 Alex 2016-05-07 16:06:59 UTC
Created attachment 123536 [details]
'make install' log of pavucontrol-3.0 build/install
Comment 3 Alex 2016-05-07 16:08:33 UTC
(In reply to Arun Raghavan from comment #1)
> Have you done a make install for pavucontrol?

Hi Arun,
Yes (pavucontrol is sitting in /usr/bin/ quietly now:)
Comment 4 GitLab Migration User 2018-07-30 09:31:11 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/44.

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.