Bug 526366 - GNOME concatenates ISO-9660 and VFAT volume names
Summary: GNOME concatenates ISO-9660 and VFAT volume names
Status: RESOLVED FIXED
Alias: None
Product: openSUSE 11.2
Classification: openSUSE
Component: GNOME (show other bugs)
Version: Factory
Hardware: Other Other
: P5 - None : Minor with 1 vote (vote)
Target Milestone: ---
Assignee: E-mail List
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-07-29 13:37 UTC by Stanislav Brabec
Modified: 2012-07-31 20:06 UTC (History)
1 user (show)

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Stanislav Brabec 2009-07-29 13:37:44 UTC
GNOME volume management concatenates names of removable ISO-9660 volume names to 16 characters, both for desktop icons and /media/ directory name. If the name is shorter than 16 characters, then it fills volume name with spaces to 16 characters. It is a regression to previous version, where it worked without problems.

How to reproduce:

Burn a DVDs with names "My photo DVD volume 1", "My photo DVD volume 2" and "My photos", then insert them to drive. You will see first two as "My photo DVD vol" and "My photo DVD vol_" for the medium that was inserted as second, and the third as "My photos       ".

isoinfo -d -i /dev/sr0 shows the name correctly
Comment 1 Stanislav Brabec 2009-07-30 15:49:12 UTC
Very similar problem also affects VFAT volumes: volume names are concatenated to 11 characters and are uppercased.
Comment 2 Stanislav Brabec 2009-07-30 15:56:08 UTC
And just another surprise: Comparing VFAT medium written on Milestone 1 and Milestone 4, mtime written by Milestone 4 is higher by exactly two hours. My GMT offset is plus 2 hours from UTC.
Comment 3 Dominique Leuenberger 2012-07-31 20:06:45 UTC
Sorry, this bug did not get the attention it deserved.

Not likely, you have already upgraded to newer versions of openSUSE, which had
a lot more bug fixes.

As openSUSE 11.2 is no longer maintained (for a long time already) and I can't
seem to reproduce anything similar in openSUSE 12.1 / 12.2 RC, I close the bug
as 'FIXED'.

Should you be able to reproduce this issue on a newer openSUSE version, please
feel to report it again.