Bug 114083 - rtsp protocol handler erroneously set to audio/x-pn-realaudio
Summary: rtsp protocol handler erroneously set to audio/x-pn-realaudio
Status: RESOLVED WORKSFORME
Alias: None
Product: kdelibs
Classification: Unmaintained
Component: general (other bugs)
Version First Reported In: unspecified
Platform: Debian testing Linux
: NOR normal
Target Milestone: ---
Assignee: Stephan Kulow
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-10-09 00:16 UTC by kiriuja
Modified: 2023-01-02 05:27 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description kiriuja 2005-10-09 00:16:52 UTC
Version:            (using KDE KDE 3.4.2)
Installed from:    Debian testing/unstable Packages
OS:                Linux

The rtsp.protocol file that comes with KDE 3.4.2 says

defaultMimetype=audio/x-pn-realaudio

As a result, the rtsp protocol does not show up under uri subtree in file associations, and instead uses settings configured for audio/x-pn-realaudio. This was done for backwards compatibility reasons in KDE 3.x, see case 84664.

This is a bug because there are tons of rtsp:// URLs out there that refer to standard RTSP streams, both audio and video, as opposed to RealNetworks' proprietary and incompatible version of the RTSP protocol.

RealAudio MIME types should only be used for files that are known to be RealNetworks files. File Associations dialog should have an rtsp entry in its uri subtree, and RTSP URLs should use handlers configured under that entry.

The rtsp.protocol file should be changed to say

defaultMimetype=uri/rtsp

Since KDE 4.0 will surely break some backwards compatibility, it would be a good chance to fix this bug as well.
Comment 1 Andrew Crouthamel 2018-11-02 04:24:29 UTC
Dear Bug Submitter,

This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond.

Thank you for helping us make KDE software even better for everyone!
Comment 2 Andrew Crouthamel 2018-11-16 02:35:49 UTC
Dear Bug Submitter,

This is a reminder that this bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version?

Thank you for helping us make KDE software even better for everyone!
Comment 3 Justin Zobel 2022-12-03 09:01:45 UTC
Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version?

If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
Comment 4 Bug Janitor Service 2022-12-18 05:13:57 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 5 Bug Janitor Service 2023-01-02 05:27:49 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!