Bug 2331 - xbmc can't open files with spaces in their name (eg. xbmc -fs "file with spaces.mp4")
Summary: xbmc can't open files with spaces in their name (eg. xbmc -fs "file with spac...
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Anssi Hannula
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-07-29 20:49 CEST by Florian Hubold
Modified: 2013-09-11 22:45 CEST (History)
4 users (show)

See Also:
Source RPM: xbmc-10.1-1.pvr.2.mga1.src.rpm
CVE:
Status comment:


Attachments

Description Florian Hubold 2011-07-29 20:49:03 CEST
Description of problem:

Currently, the Exec line for xmbc.desktop looks like that:

Exec=xbmc

It should be changed to 

Exec=%_libdir/xbmc/xbmc.bin

to be able to open files with XBMC.
So from a file manager, you can Open With -> choose XBMC and the file is played. Does not work currently with the original /usr/bin/xbmc wrapper script.
Manuel Hiebel 2011-07-29 21:32:48 CEST

CC: (none) => anssi.hannula

Anssi Hannula 2011-09-01 14:46:13 CEST

Assignee: bugsquad => anssi.hannula

Samuel Verschelde 2011-10-01 17:01:26 CEST

Keywords: (none) => Junior_job, PATCH
CC: (none) => stormi

Comment 1 Anssi Hannula 2011-12-16 05:25:28 CET
Hm, strange, this works fine for me in Cauldron, and there has been no changes regarding this in xbmc.spec from what I can see.

Could be something else has changed, can you reproduce this on mga1 and/or cauldron?
Comment 2 Florian Hubold 2011-12-16 13:52:48 CET
Strange, xbmc.desktop still contains "Exec=xbmc" after reinstallation, but when adding xbmc via Open with -> and select XBMC (in KDE, dolphin) the command shows "/usr/lib64/xbmc/xbmc.bin".

Will try again with xguest for mga1 and on a untouched cauldron installation.
Comment 3 Florian Hubold 2011-12-21 22:06:29 CET
Checked again with up-to-date cauldron and KDE4, when adding xbmc via Open with -> and select XBMC (in KDE, dolphin) the command
shows just "xbmc" int contrary to above.

So it's as described, you can use it to open xbmc that way, it's just that xbmc doesn't open the video.
Comment 4 Anssi Hannula 2011-12-21 22:20:23 CET
What do you mean by "the command shows just xbmc"?

Exec is supposed to be "xbmc", and it works fine for me.

What do you see in "ps faux" after trying to start the video?
Comment 5 Florian Hubold 2011-12-22 15:41:27 CET
(In reply to comment #4)
> What do you mean by "the command shows just xbmc"?

Arrhg, sorry, was unclear. The KDE applet started by Open with -> shows the Exec key value from the .desktop file. ps faux shows /usr/lib64/xbmc/xbmc.bin /path/to/video.

After trying to reproduce, maybe i've hit that problem because XBMC wasn't able to play that particular file, short test played a .divx file properly, but silently stalled on an .mpeg video, meaning xbmc opens and you get no error message like "file couldn't be played/is not supported" it only drops you into the main menu.

Opening that .mpeg file from inside xbmc also plays it just fine. Maybe it's due to spaces in the filename (which the .divx video doesn't have)?
Comment 6 Anssi Hannula 2011-12-22 17:05:18 CET
Yeah, spaces are an issue.

This particular issue is fixed by adding "" around $SAVED_ARGS in /usr/bin/xbmc line 133.

However, specifying e.g.
  xbmc -fs "file with spaces.mp4"
still fails, I'll have to look more closely into this (probably won't be until next week).
Comment 7 Marja Van Waes 2012-04-23 16:48:25 CEST
3-monthly ping

CC: (none) => marja11

Comment 8 Marja Van Waes 2012-07-06 15:04:48 CEST
Please look at the bottom of this mail to see whether you're the assignee of this  bug, if you don't already know whether you are.


If you're the assignee:

We'd like to know for sure whether this bug was assigned correctly. Please change status to ASSIGNED if it is, or put OK on the whiteboard instead.

If you don't have a clue and don't see a way to find out, then please put NEEDHELP on the whiteboard.

Please assign back to Bug Squad or to the correct person to solve this bug if we were wrong to assign it to you, and explain why.

Thanks :)

**************************** 

@ the reporter and persons in the cc of this bug:

If you have any new information that wasn't given before (like this bug being valid for another version of Mageia, too, or it being solved) please tell us.

@ the reporter of this bug

If you didn't reply yet to a request for more information, please do so within two weeks from now.

Thanks all :-D
Comment 9 Manuel Hiebel 2012-11-05 16:52:40 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 10 Manuel Hiebel 2012-12-02 14:32:09 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: NEW => RESOLVED
Resolution: (none) => WONTFIX

Comment 11 Anssi Hannula 2012-12-02 15:06:43 CET
AFAIK this issue is still present in cauldron, reopening until confirmed otherwise.

Status: RESOLVED => REOPENED
Version: 1 => Cauldron
Resolution: WONTFIX => (none)

Comment 12 Rémi Verschelde 2013-07-02 16:04:16 CEST
Hi Anssi, what's the status on this bug?

According to the comments, it seems the fix described in the summary is not wanted. Could you change the summary to describe which bug you are willing to work on, or close this one?

Thanks.

CC: (none) => remi

Comment 13 Samuel Verschelde 2013-08-26 18:11:40 CEST
Relevant comment seems to be comment #6 from Anssi Hannula : xbmc has trouble opening files with spaces in their name.

I'm updating the summary.

Keywords: Junior_job, PATCH => (none)
Summary: change Exec entry in xbmc.desktop file to be able to open files with xbmc => xbmc can't open files with spaces in their name (eg. xbmc -fs "file with spaces.mp4")

Comment 14 Anssi Hannula 2013-09-11 22:45:29 CEST
Fixed in xbmc-12.2-3.mga4, and will be pushed to Mageia 3 as an update.

Thanks for the report and sorry for the delay.

Status: REOPENED => RESOLVED
Resolution: (none) => FIXED


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