Bug 495819 - Disabling Launch Feedback in Display settings have no effect on taskbar.
Disabling Launch Feedback in Display settings have no effect on taskbar.
Status: CLOSED UPSTREAM
Product: Fedora
Classification: Fedora
Component: kdebase-workspace (Show other bugs)
10
All Linux
low Severity medium
: ---
: ---
Assigned To: Ngo Than
Fedora Extras Quality Assurance
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2009-04-14 19:26 EDT by Mustafa Qasim
Modified: 2009-04-15 09:03 EDT (History)
9 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2009-04-15 09:03:10 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
It shows that launch feedback is disabled but still new instance of real player is appeared on taskbar on playing a new audio file. (171.54 KB, image/png)
2009-04-14 19:26 EDT, Mustafa Qasim
no flags Details


External Trackers
Tracker ID Priority Status Summary Last Updated
KDE Software Compilation 189715 None None None Never

  None (edit)
Description Mustafa Qasim 2009-04-14 19:26:34 EDT
Created attachment 339596 [details]
It shows that launch feedback is disabled but still new instance of real player is appeared on taskbar on playing a new audio file.

Description of problem:

Disabling the "Launch Feedback" option has no effect in taskbar. 

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.Go to System >> System Settings >> Display >> Launch Feedback
2.Uncheck the "Enable Taskbar Notification"
3.Save the settings.
  
Actual results:
Disabling the "Taskbar Notifications" have no effect on taskbar and still temporary new instances of programs e.g. Firefox, Amarok etc appears on taskbar.

Expected results:
There should be no more the appearance of temporary instances of running programs on taskbar.

Additional info:
New Instance means that if you play a different audio file while running an existing one you will see a new instance of Amarok in taskbar for some seconds.

Same while using firefox when you open another html file on ur computer you will see a new instance of firefox for some seconds in ur taskbar.
Comment 1 Martin Klapetek 2009-04-14 19:30:23 EDT
Confirming on F10 x86_64, KDE 4.2.2 from kdeforge and Qt 4.5. The setting has no effect, KDE devs says it's Fedora bug.
Comment 2 Rex Dieter 2009-04-14 20:49:51 EDT
which KDE devs?  upstream mailing list or bugreport?
Comment 3 Kevin Kofler 2009-04-15 02:24:47 EDT
> KDE devs says it's Fedora bug.

This sounds like unsubstantiated fingerpointing to me, I don't see how any of our patches would be causing this. Can you please ask them why they think that? I'd really like to see a link to an upstream bug report (and yes, one should be filed, as I strongly doubt it's our fault).


Of course, the real bug here is that Real Player:
1. does not disable startup notification in its .desktop file but
2. does not actually support it,
but that's just the (lack of) quality we've gotten used to from proprietary software. :-/ That bug should be reported to Real, they're the only ones who can fix it.


Still, this bug (the taskbar ignoring the setting to disable the taskbar startup notifications) should be fixed, too.
Comment 4 Martin Klapetek 2009-04-15 07:16:56 EDT
Well I talked to them on irc, it surely is possible that they were wrong, sorry for the "fingerpoinintg", didn't mean it bad. I'll try to find out more from them and eventually fill a bug in their bugzilla.

But it's not only with Real Player, it does not work with other software too.
Comment 5 Rex Dieter 2009-04-15 07:23:36 EDT
kde-sig folk are usually in #fedora-kde (with some of us also in #kde and #kde-devel), so please drop by and let us know when you're going to chat again with the kde folk.
Comment 6 Martin Klapetek 2009-04-15 08:58:38 EDT
Ok, so they were wrong :) After additional testing it was found out, that it really is an upstream bug, so I reported it here https://bugs.kde.org/show_bug.cgi?id=189715

This can be closed.
Comment 7 Kevin Kofler 2009-04-15 09:03:10 EDT
OK, thanks, we'll track this upstream.

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