Bug 113017 - "could not determine size of resulting image file" -> error renaming.
Summary: "could not determine size of resulting image file" -> error renaming.
Status: RESOLVED FIXED
Alias: None
Product: k3b
Classification: Applications
Component: general (other bugs)
Version First Reported In: unspecified
Platform: Compiled Sources Linux
: NOR normal
Target Milestone: ---
Assignee: Sebastian Trueg
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-09-21 19:25 UTC by Pietro Franchi
Modified: 2007-02-28 13:54 UTC (History)
0 users

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


Attachments
screenshot of k3b error. (76.74 KB, image/png)
2007-02-25 22:57 UTC, Anthony Ettinger
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Pietro Franchi 2005-09-21 19:25:32 UTC
Version:           0.12.4a (using KDE KDE 3.4.2)
Installed from:    Compiled From Sources
OS:                Linux

Hi!
It happened to me that a message "could not determine size of resulting image file" popped out when I try to start burning a dvd. When I clicked on "Debugging info" I saw that actually it was because mkisofs wasn't able to burn two files with the same name in the same directory. Well, I renamed it manually and all worked fine.

Why the two names were the same? Because they were two files with a name longer than 64 characters, but equal for the first 64, and beeing trunked to 64 looked the same to mkisofs (version 2.1).

So I think that would be better: 

1) to change that message in something more specific, or, if this is not possible due to mkisofs, then change it to "mkisofs error: please check debugging info", or something like that. :-)

2) to do something in the "renaming policy" of k3b to be able to deal with long similar file names

cheers,
Pietro (sorry for my english)
Comment 1 Sebastian Trueg 2006-06-24 08:54:30 UTC
Is this reproducale with k3b 0.12.16?
Comment 2 Sebastian Trueg 2006-08-07 16:58:43 UTC
There has been no information in a long time. I cannot reproduce the bug so I 
will close it.
Comment 3 Anthony Ettinger 2007-02-25 22:53:44 UTC
I am still seeing this error.

Comment 4 Anthony Ettinger 2007-02-25 22:57:17 UTC
Created attachment 19822 [details]
screenshot of k3b error.
Comment 5 Sebastian Trueg 2007-02-28 13:54:16 UTC
it is solved in svn, i.e. k3b 1.0