Please ask other than "reported bug"-related questions on IRC, Forums or ML's, or add a separate bug report about your another problem.

Now it's high chance that your off-topic questions get lost because they're at the end of long bug report and they're not related to bug in summary (can't see from summary that there's another problem described at the end of report).

CC: (none) => jani.valimaa

Sorry for that. I wish I could delete that part.

Please, don't forget my rpm request.

No need to be sorry. Also, I'm working on your request..

Status: NEW => ASSIGNED
Assignee: bugsquad => jani.valimaa

Actually radiotray is already imported to Cauldron. Will push it to stable release when backports policy is decided.

Pushed radiotray to core/updates_testing and tainted/updates_testing for mga1, please test.

I was using radiotray in Cauldron, for quite some time now, and worked fine.

Today I installed it -as you suggested- in Mageia 1 (with KDE 4.6.5) from tainted_testing repos.

Worked -also- fine, as expected. Also entered a couple of new web-radio stations,
corrected the URL of one of the default stations that were included with the program.
It sounds OK.

Some stations that I selected, gave a connection error, but I suppose that has nothing to do with your work, probably a wrong URL.
I'll try and fix it. No big problem.
As long as "Radio Paradise" works fine, I'm OK!
Hopefully tonight I'll try it for a longer period, maybe several hours.
If you want something else -in particular- to test, just ask me.
 
Thanks, again, for your work.

Ouch!  Sore ears :-).

For some reason, when I left click on the systray icon, and select
a station, it changes the volume from 20% to 100%.

Repeatable.

CC: (none) => davidwhodgins

I don't have the problem in comment#7.
I can't reproduce it.
Everything sounds fine here.

> PS. An off- topic question:
> Since everyone is using his/her full name here, in bugs.mageia.org, I thought
> it was proper that I also do so. So, I went in user preferences  and changed
> it, but it worked only for one day, "John V" came back, yesterday and today.
> Before sending this bug report, changed it again, changes accepted, but it
> didn't change. To whom, or where should I post about fixing that "problem"?

You must change it on http://identity.mageia.org, not in bugzilla itself, so that your name appears in the various websites of the mageia project (bugzilla, forums, etc.).

CC: (none) => stormi

I can't reproduce the bug from comment 7 either on my i586 system. Everything seems to work well (apart from the fact that there's a radio that doesn't answer, "Onda Tropical". Maybe the list needs a refresh ?)

Works well on x86_64.  No problem with volume. Adding stations works OK.

CC: (none) => derekjenn

Try moving the panel from the bottom, to the left side.  Once I found out
you can use the mouse scroll wheel, to adjust the volume, I realized the
panel location might have an impact, and it does.

With the panel on the left side, the process of selecting a station increases
the volume to 100% (No scroll wheel usage), just single left left click,
move the mouse cursor down to the genre, wait for it to expand, then select
the station.

With the panel on the bottom, same procedure, except moving the mouse cursor
up to the genre, instead of down, and the volume is left alone.

I don't think this should be considered a show stopper, as there is a workaround
(keep the panel on the bottom), but should be reported upstream, if anyone
else can reproduce.

(In reply to comment #12)
> Try moving the panel from the bottom, to the left side.  Once I found out
> you can use the mouse scroll wheel, to adjust the volume, I realized the
> panel location might have an impact, and it does.
> 
> With the panel on the left side, the process of selecting a station increases
> the volume to 100% (No scroll wheel usage), just single left left click,
> move the mouse cursor down to the genre, wait for it to expand, then select
> the station.
> 
> With the panel on the bottom, same procedure, except moving the mouse cursor
> up to the genre, instead of down, and the volume is left alone.
> 
> I don't think this should be considered a show stopper, as there is a
> workaround
> (keep the panel on the bottom), but should be reported upstream, if anyone
> else can reproduce.

I tried to follow your steps but couldn't reproduce. I hadn't noticed that I can use the mouse scroll wheel to adjust the volume. It works but the volume level is weird. 20% is very loud, and adjusting the volume changes that of the system but with different values.

However, I think that this doesn't block the update.

(In reply to comment #7)
> Ouch!  Sore ears :-).
> 
> For some reason, when I left click on the systray icon, and select
> a station, it changes the volume from 20% to 100%.
> 
> Repeatable.

Hello,

So,tested on Mageia release 1 (Official) for x86_64 and I have the same problem
with the volume.
When I use the mouse scroll wheel to adjust the volume on Radio Tray ,the system volume goes wrong impossible to leave a 75% for example.it goes to 100%.
It should be possible to adjust the volume of Radio Tray without it adjusts the system.

I have also three radio that doesn't answer:

"Cool Jazz" : Connection Error
"Trumpet Jazz" Connection Error
"Enjoy Station" Connection Error

CC: (none) => geiger.david68210

(in reply to comment #7)
Still can't reproduce it.

(In reply to comment #12)
Moved panel to the left side. Nothing happened, no problem.

(In reply to comments #13 & #14)
Volume levels, from radiotray & system volume, are independent. If system volume
is in 100% and you change the radiotray volume from 20%, to 60%, the overall volume increase is about +50% (equal to 150% of system volume

Mageia 1 x86_64 KDE

(In reply to comment #14)
Stations that give the message "Connection Error":
Cool Jazz
Trumpet Jazz
Onda Tropical
Enjoy Station
181.FM

All of them, are (or were) stations from shoutcast directory. Couldn't find them in http://www.shoutcast.com/, maybe the stations don't exist anymore. Except 181.FM, but at their site, M$ silverlight is required (very-very funny).

The "Connection Error" for some stations, IMHO, it's not a problem of packaging or the program itself. Radiotray works OK.
There are thousands of stations out there, to add .

Testing i586 Gnome. I was able to add radio stations without any problems and start/stop them. Its a useful app.

There does appear to be something strange going on with the volume control though.

When first installed, it had set the system volume to 100%.

If I start with system volume set to 35% and Radiotray volume at 10% and then increase Radiotray volume to 22% the system volume has increased to 60%. RT first appeared to dip to 7% before increasing.

If, with 22% & 60%, I then reduce system volume to 10% and use the scroll wheel on RT to increase it, it instantly changed to 5% and the system volume is now 37%.

There does seem to be something weird going on there.

Pulseaudio volume control shows RT playing at 37%

CC: (none) => eeeemail

Looking at and adjusting it in Sound Preferences it appears to function correctly. Proportionally to the system volume. Could it just be a problem with the applet, or perhaps just a problem with the scroll wheel?

In reply to comment #16 (and other comments about radiotray's volume level).

I did a more thorough tests (than in my previous comment).
In Mageia Cauldron & Mageia 1 (KDE 4.7.0 & 4.6.5, both x86_64).
I reproduced -more or less- what's described above.
I came in three conclusions:

1. Increasing the radiotray volume, increases also the system volume.
So, system volume follows the increment of radiotray volume.
That happens only when radiotray is "playing" (a radio station), not when it's idle in "system tray".

2. The opposite doesn't happen. For example:
Both volume levels are up (let's say 75%) and I turn down the volume level in radiotray, the system volume does not follow, it stays at 75%. 

3. If the radiotay volume is in a level and I only change the system volume level, both ways (up or down), the radiotray volume does not change.

Well, imagine the radiotray volume adjustment as a "pre-amplification", and the system volume adjustment as the "main" (or "master") amplification (actually, this is not completely true, because you have another volume level adjustment, above everything else: the volume control knob on your speakers... but let's leave that outside the equation).

Here's another thing I noticed, that goes along the finding No1, above:
For example, your system volume is set to 50% and you open radiotray. Radiotray's volume level is at 40% (from the previous time you quitted the application). The system volume doesn't change, as long as radiotray stays idle.
If you select a station and it starts playing, then the system volume goes up about 40% (radiotray's volume level) and shows now at least 70% (50+40%=70).
Well, the odd thing here is that the increment is not always accurate.
A lot of times, the system volume goes higher (but not lower) than it should, according to the percentage shown in radiotray's volume level.

So, the finding No1 it's the "problem" here.
The volume controls should be independent, like what happens, for example, with audacious, vlc, clementine, or smplayer (I tested them too).
But...
I also tested amarok. It "behaves" exactly as radiotray does. 
Then, I tested Dragon Player. In No1, acts like radiotray, but in No2 & No3 quite the opposite. So, whichever volume level turns up (or down), the other one follows (that's the equal of not having an application volume control).

I don't know if it's an application, or a Mageia, or a KDE, or a pulseaudio server "strange behaviour".
It could just be a new feature...
Maybe someone of the devs could give more information? (Colin Guthrie comes in mind, could the packagers talk to him?).

What I haven't done yet:
a. Test the above in my Mageia 1 clean installation (KDE 4.6.3).
b  Test with Mandriva 2010.2 (IIRC, the volume controls were independent).
c. What happens if, in "system tray", I go to: KMix >> Mixer >> Settings >> Configure KMix >> and uncheck the selection: "Enable system tray volume control".
...I don't know if it's important anymore. I don't consider, that "volume level problem", as a real problem.

(In reply to comment #17)
When you say "in Sound Preferences", where do you mean exactly.

Thanks for your further testing John. That sounds much like what I was experiencing. The Sound Preferences, under Gnome are under a right click on the volume icon or System/Preferences/Sound.

I'm not sure that this, fairly minor, issue should stop the update being validated. It could be handled as a normal bug report. It'd be interesting to hear the thoughts of the packager, Jani.

Agreed.

Can someone from the sysadmin team push the srpm
radiotray-0.6.4-1.0.mga1.src.rpm
from Core Updates Testing to Core Updates, and the srpm
radiotray-0.6.4-1.0.mga1.tainted.src.rpm
from Tainted Updates Testing to Tainted Updates.

Advisory:
This updates adds the online radio streaming player radiotray,
that was present in Mandriva 2010.2, but missing from Mageia 1.
See https://bugs.mageia.org/show_bug.cgi?id=1896 for handling
possible volume control problems.

Keywords: (none) => validated_update
CC: (none) => sysadmin-bugs

Could someone create the bug report for the sound problem, and give the number in a comment ?

(In reply to comment #21)
> Could someone create the bug report for the sound problem, and give the number
> in a comment ?

Maybe this should also be reported to upstream bug tracker?

(In reply to comment #22)
> (In reply to comment #21)
> > Could someone create the bug report for the sound problem, and give the number
> > in a comment ?
> 
> Maybe this should also be reported to upstream bug tracker?

Yes I think we should, but maybe after having asked to Colin what he thinks of comment #18 ?

I have created bug 2575 regarding the volume issue

I've replied to the volume issue in another bug (tl;dr: it's a feature, not a bug. You can turn it off if you like)

CC: (none) => mageia

Thankyou Colin :)

Are we ready to push this one now then?

(In reply to comment #26)
> Thankyou Colin :)
> 
> Are we ready to push this one now then?

Of course, it's already validated since comment #20 :)

Also, I think there should be a bug report (upstream and here to follow the upstream one) concerning non-working streams.

update pushed

Status: ASSIGNED => RESOLVED
CC: (none) => dmorganec
Resolution: (none) => FIXED