cannot write converted files to home directory

Bug #273350 reported by Amran
38
This bug affects 3 people
Affects Status Importance Assigned to Milestone
soundconverter (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

Binary package hint: soundconverter

Release info:
Description: Ubuntu intrepid (development branch)
Release: 8.10

Package version:
soundconverter:
  Installed: 1.3.2-0ubuntu1
  Candidate: 1.3.2-0ubuntu1
  Version table:
 *** 1.3.2-0ubuntu1 0
        500 http://gb.archive.ubuntu.com intrepid/universe Packages
        100 /var/lib/dpkg/status

Output at terminal:
SoundConverter 1.3.2
  using Gstreamer version: 0.10.20, Python binding version: 0.10.12
  using gio
  'faac' element not found, disabling AAC.
  using 2 thread(s)
error: could not parse URI ()
Queue done in 0s
Queue done in 0s
error: Could not open resource for reading. (07 - Immigrant.flac)
Cannot set permission on '/home/amran/Nitin Sawhney-Immigrant.mp3'
Queue done in 0s

i added a flac file, set conversion to MP3 and set it on its merry way. seems it doesnt like outputting the file to my home dir

if i tell it to save the file in /home/amran/Desktop it works correctly

Revision history for this message
Tan Kah Ping (kahping) wrote :

I can confirm this. Converting audio files when the destination folder is your home folder, soundconverter will just happily run as if nothing's wrong except that the conversion doesn't output anything (except in terminal)

Revision history for this message
Eric Krieger (grammatoncleric) wrote :

I also can confirm this. Bug still exists in the final release of Intrepid Ibex.

Jeldert (jeldert)
Changed in soundconverter:
status: New → Confirmed
Revision history for this message
Jeldert (jeldert) wrote :

When manually setting the home dorectory as output folder SoundConverter is able to create the files there.

Revision history for this message
GautierPortet (kassoulet) wrote :

Cannot reproduce... Still there in 1.4.2 ?

Revision history for this message
Amran (amx109) wrote : Re: [Bug 273350] Re: cannot write converted files to home directory

im afraid im still using 1.3.2 on ubuntu 8.10

i think 1.4.1 is in jaunty universe. i'll upgrade once its released; if the
bug exists in jaunty i'll file another bug report under that distribution

hope that helps?

ta

amran

On Mon, Mar 2, 2009 at 10:19 PM, GautierPortet <email address hidden> wrote:

> Cannot reproduce... Still there in 1.4.2 ?
>
> --
> cannot write converted files to home directory
> https://bugs.launchpad.net/bugs/273350
> You received this bug notification because you are a direct subscriber
> of the bug.
>

Revision history for this message
Janne (jjohanss) wrote :

Jaunty still has this bug.

Revision history for this message
GautierPortet (kassoulet) wrote :

Pfff I'm afraid I'm really lost here... Just impossible to reproduce.

I managed to fix a minor issue: I will now display an error dialog when something bad like this happen. But impossible to reproduce this behavior.

Can somebody reproduce this while running with --debug option and paste here the resulting output please?

Revision history for this message
Laurent Dinclaux (dreadlox) wrote :

I use soundconvert 1.3.2 on Intrepid 64bit

debug.txt is attached, unfortunately, some messages are in French....

It can be traduced like this:

launching: 'giosrc location="file:///home/lox/Musique/JVDK/Best%20of/05%20-%20JVDK.mp3" name=src ! decodebin name=decoder ! audioconvert ! vorbisenc quality=0.6 ! oggmux ! giosink location=/home/lox/05%20-%20JVDK.ogg'
error: Can't read from ressource. (05 - JVDK.mp3)
Can't change permissions of '/home/lox/05 - JVDK.ogg'
Queue done in 0s

The file I am trying to convert is in folder /home/user/Musique/JVDK/Best of

$ ls -lah | grep JVDK
-rw-r--r-- 1 user user 4,3M 2008-11-04 09:27 05 - JVDK.mp3

I also tried without any space character in path and file name: same behavior.

Revision history for this message
Matthew Woerly (nattgew) wrote :

I'm using 1.3.2 on Intrepid 64-bit and was able to write both files and directories to my home directory...

Revision history for this message
GautierPortet (kassoulet) wrote :

So my progress so far: this is caused by the destination location, as you can see it's an absolute path name instead of an URI. Now I have to find why :)

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Bug attachments

Remote bug watches

Bug watches keep track of this bug in other bug trackers.