Ubuntu
indicator-sound package

should not use gconf to build

Bug #656405 reported by Sebastien Bacher
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
The Sound Menu
Fix Released
Low
Conor Curran
The Sound Menu 0.5.3
indicator-sound (Ubuntu)
Fix Released
Low
Unassigned

Bug Description

Binary package hint: indicator-sound

It seems indicator-sound is not using gconf but the configure check for it anyway, is that really required?

Revision history for this message
Sebastien Bacher (seb128) wrote :

the makefiles seem also to list gconf use for no reason since there is no schemas or gconf use in the code either

Changed in indicator-sound (Ubuntu):
importance: Undecided → Low
tags: added: gnome3-gsettings
Conor Curran (cjcurran)
Changed in indicator-sound:
assignee: nobody → Conor Curran (cjcurran)
status: New → In Progress
importance: Undecided → Low
Conor Curran (cjcurran)
Changed in indicator-sound:
milestone: none → 0.5.3
status: In Progress → Fix Committed
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package indicator-sound - 0.5.3-0ubuntu1

---------------
indicator-sound (0.5.3-0ubuntu1) natty; urgency=low

  * New upstream release.
    - Libindicate removed from registration process (LP: #691189)
    - Vala code now using Gdbus exclusively for mpris interaction
    - Fixed memory leak with album art resizing (LP: #689686)
    - Gconf removed and Gsettings schema added (LP: #656405)
    - registration process now uses gsettings
 -- Ken VanDine <email address hidden> Thu, 16 Dec 2010 15:03:15 -0500

Changed in indicator-sound (Ubuntu):
status: New → Fix Released
Conor Curran (cjcurran)
Changed in indicator-sound:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.