Bug 3496 - Phonon Speaker Setup shows blank entries when viewed for the second time
Summary: Phonon Speaker Setup shows blank entries when viewed for the second time
Status: RESOLVED WONTFIX
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 1
Hardware: i586 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: John Balcaen
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-11-27 13:07 CET by John Roblin
Modified: 2012-12-02 14:32 CET (History)
2 users (show)

See Also:
Source RPM:
CVE:
Status comment:


Attachments
Build log of kdebase4-runtime (104.56 KB, text/plain)
2012-01-03 15:30 CET, John Balcaen
Details

Description John Roblin 2011-11-27 13:07:24 CET
Description of problem:
See summary.

Version-Release number of selected component (if applicable):
Latest as of 27/11/11

How reproducible:
This has happened since install

Steps to Reproduce:
1) Launch Multimedia from System Settings
2) Click Phonon
3) Speaker Setup tab
4) Back to Overview
5) User is prompted to save changes even if no changes have been made (possibly a bug in itself)
6) Repeat steps 1-3
7) Entries on my system are now blank
Comment 1 John Roblin 2011-11-27 13:08:27 CET
I have a Creative Audigy Player (first release I think).
Comment 2 Manuel Hiebel 2011-11-27 17:02:44 CET
Hello, thanks for the bug report.

I guess the desktop is KDE.

So it's for mikala, sorry I don't know what to ask :/

Assignee: bugsquad => balcaen.john

Comment 3 John Balcaen 2011-11-27 17:57:29 CET
Phonon stuff is for coling ;o)

CC: (none) => balcaen.john
Assignee: balcaen.john => mageia

Comment 4 Colin Guthrie 2011-11-27 18:05:12 CET
ACK, I can reproduce here... that's what I get for testing via "kcmshell4 kcm_phonon" I guess!

Status: NEW => ASSIGNED

Comment 5 Colin Guthrie 2011-11-27 19:14:44 CET
OK, I've fixed this in Cauldron, but not pushed. I'll leave that to mikala so I don't break any cycles or pending fixes he's got :)

mikala, let me know if you want this fix also for mga1 (depends on whether you want to push an update for just this issue or if you have other fixes pending). The patch in the mga1 version should be pretty similar but I did rename the file so it won't be an identical fix for 4.6.x tree (tho' it'll be very similar, so feel free to fix it up yourself... the file in 4.6.x is speakersetup.cpp rather than audiosetup.cpp)

Assignee: mageia => balcaen.john

Comment 6 Colin Guthrie 2011-11-27 19:15:14 CET
(NB, also pushed to KDE/4.7 branch upstream so it'll be in 4.7.4 when it rolls around).

CC: (none) => mageia

Comment 7 John Balcaen 2012-01-03 13:33:07 CET
(In reply to comment #5)
> OK, I've fixed this in Cauldron, but not pushed. I'll leave that to mikala so I
> don't break any cycles or pending fixes he's got :)
> 
> mikala, let me know if you want this fix also for mga1 (depends on whether you
> want to push an update for just this issue or if you have other fixes pending).
Hum i guess i forgot this bug :/
Where can i find this fix please or did you eventually commit it already in mga1 branch ?
Comment 8 Colin Guthrie 2012-01-03 13:39:46 CET
I didn't push it to mga1, but the fix for cauldron was originally committed here:

------------------------------------------------------------------------
r173017 | colin | 2011-11-27 18:10:55 +0000 (Sun, 27 Nov 2011) | 1 line

Fix error on 2nd viewing of the Audio Device Setup tab (mga#3496)


It's probably been removed now as it'll be included with upstream commits.

I can probably backport the fix to mga1 if you like, but the code will be slightly different there as it's an older version.... (file names changed, but the core fix is likely similar).
Comment 9 John Balcaen 2012-01-03 14:07:28 CET
Since this bug is against mga1, it would be nice if you could backport it ;o)
Comment 10 Colin Guthrie 2012-01-03 14:11:38 CET
Knew you'd say that :D

OK, if I do the code, will you do the tests (don't have any handy mga1 installs)?
Comment 11 Colin Guthrie 2012-01-03 14:22:07 CET
OK, patch ported in SVN. All ready to go, but not submitted. Over to you :D
Comment 12 John Balcaen 2012-01-03 15:05:43 CET
ok i'll check it :)
Comment 13 John Balcaen 2012-01-03 15:30:27 CET
Created attachment 1326 [details]
Build log of kdebase4-runtime

Hello coling,
While the patch seems to apply cleany it does not build here in a iurt chroot :/
you can find attached the build log
Comment 14 Manuel Hiebel 2012-11-05 16:52:37 CET
This message is a reminder that Mageia 1 is nearing its end of life. 
In approximately 25 days from now, Mageia will stop maintaining and issuing 
updates for Mageia 1. At that time this bug will be closed as WONTFIX (EOL) if it 
remains open with a Mageia 'version' of '1'.

Package Maintainer: If you wish for this bug to remain open because you plan to 
fix it in a currently maintained version, simply change the 'version' to a later 
Mageia version prior to Mageia 1's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that we may not 
be able to fix it before Mageia 1 is end of life.  If you would still like to see 
this bug fixed and are able to reproduce it against a later version of Mageia, 
you are encouraged to click on "Version" and change it against that version 
of Mageia.

Although we aim to fix as many bugs as possible during every release's lifetime, 
sometimes those efforts are overtaken by events. Often a more recent Mageia 
release includes newer upstream software that fixes bugs or makes them obsolete.

--
Mageia Bugsquad
Comment 15 Manuel Hiebel 2012-12-02 14:32:07 CET
Mageia 1 changed to end-of-life (EOL) status on ''1st December''. Mageia 1 is no 
longer maintained, which means that it will not receive any further security or 
bug fix updates. As a result we are closing this bug. 

If you can reproduce this bug against a currently maintained version of Mageia 
please feel free to click on "Version" change it against that version of Mageia and reopen this bug.

Thank you for reporting this bug and we are sorry it could not be fixed.

--
Mageia Bugsquad

Status: ASSIGNED => RESOLVED
Resolution: (none) => WONTFIX


Note You need to log in before you can comment on or make changes to this bug.