Description of problem: As I uninstalled rhythmbox to build a new version from git I saw that it demanded a newer version of glib & a newer version of gobject-introspection so this is a request-report. Steps to Reproduce: 1. Open a Terminal/Console/Shell an type as normal user git clone git://git.gnome.org/rhythmbox & let it download all. 2. Then try ./autogen.sh from the downloaded rhythmbox-dir & see that it wants a newer version of gobject-introspection. 3. Now do git clone git://git.gnome.org/gobject-introspection & download everything. 4. Try ./autogen.sh from the downloaded gobject-introspection-dir & see that it needs a newer version of glib. 5. Do git clone git://git.gnome.org/glib/ & download everything. 6. Do ./autogen.sh & then ./configure & then make & as root make install from the same glib-dir & everything is fine so far. 7. Now go to the downloaded introspection-dir again & try ./autogen.sh & then ./configure & notice that the config-file doesn't seem to see the new build of glib.
CC: (none) => kristoffer.grundstrom1983
Th reason for building a new version of Rhythmbox is to rule out why it's not working together with PulseAudio. I've already done rebuilds of pulseaudio & rhythmbox, but I don't know if rpm --rebuild rhythmbox.src.rpm installs the rebuilds to. If it does it partially fixed the issue, but still I get 68% volume when starting a radiochannel in Rhythmbox.
I tested starting pavucontrol from Terminal & under the meantime as Rhythmbox played the stream I got this error lots & lots of times: ** (pavucontrol:27606): DEBUG: Ignoring sink-input due to it being designated as an event and thus handled by the Event widget
You can see my pavucontrol here: http://www.geting.se/viewimage/image/315006-Pavucontrol.png
There's a related bug reported to RedHat here: https://bugzilla.redhat.com/show_bug.cgi?id=636983#c1 Here's a possible workaround that might be able to implement from Archlinux: https://wiki.archlinux.org/index.php/PulseAudio#Volume_gets_louder_every_time_a_new_application_is_started
I should mention that I saw this first when I ran pavucontrol from Terminal/Console/Shell: [kristoffer@localhost ~]$ pavucontrol ** (pavucontrol:27606): DEBUG: Error reading config file /home/kristoffer/.config/pavucontrol.ini: File or directory doesn't exist ** (pavucontrol:27606): DEBUG: Failed to initialize device manager extension: No such extension
As said already on one of your previous bug report, we're not going to provides a new glib or gobject-introspection for mageia 1 You should do the backport alone (& eventually break your mageia 1) or simply switch to cauldron instead.
Status: NEW => RESOLVEDCC: (none) => balcaen.johnResolution: (none) => WONTFIX
This is for the 2.6.38.8-desktop-4.mga-kernel.
I hope that someone is willing to help me complete this as I want to solve this issue & tell if it is into this bugreport.