After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 438781 - sound-juicier audio profile prefereces is buggy
sound-juicier audio profile prefereces is buggy
Status: RESOLVED DUPLICATE of bug 406739
Product: gnome-media
Classification: Deprecated
Component: media profiles
2.18.x
Other All
: Normal major
: ---
Assigned To: Sound Juicer Maintainers
Sound Juicer Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-05-16 03:24 UTC by Irene Huang
Modified: 2007-05-17 08:05 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18

Attachments
patch (417 bytes, patch)
2007-05-16 07:15 UTC, Irene Huang 		none Details | Review
new patch with Change log (879 bytes, patch)
2007-05-16 07:21 UTC, Irene Huang 		none Details | Review

Description Irene Huang 2007-05-16 03:24:46 UTC 
Please describe the problem:
the Edit GNOME audio Profile dialog doesn't work

Steps to reproduce:
1. run sound-juicer
2. edit->preferences
3. in the dialog click "edit profile"
4. click the second button under "new"


Actual results:
result: cannot do anything with the dialog shown.

Expected results:
the dialog should be editable

Does this happen every time?
yes

Other information:
if you close the other window, then the dialog will be editable
Comment 1 Irene Huang 2007-05-16 07:15:47 UTC 
Created attachment 88261 [details] [review]
patch

run the dialog
Comment 2 Irene Huang 2007-05-16 07:21:24 UTC 
Created attachment 88262 [details] [review]
new patch with Change log
Comment 3 Irene Huang 2007-05-16 07:21:58 UTC 
obsoleting the first patch, please review. 

Thanks
Comment 4 Bastien Nocera 2007-05-16 08:31:07 UTC 
How is this bug different from bug 406739?
Comment 5 Irene Huang 2007-05-17 08:05:22 UTC 
So your patch went into trunk and the fix is available in 2.19.* right? 
And yes, I think this is a duplication of bug 406739. 
Thanks

*** This bug has been marked as a duplicate of 406739 ***