Ubuntu
easytag package

Easytag not able to see CIFS mounts

Bug #485980 reported by Paillomams
62
This bug affects 12 people
Affects Status Importance Assigned to Milestone
easytag (Fedora)
Won't Fix
Medium
easytag (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

Binary package hint: easytag

I use a samba share to store my music collection, the share is mounted with the following command and options:

gksudo 'mount -t cifs -o file_mode=0777,dir_mode=0777,mapchars,noatime,iocharset=utf8,credentials=/home/credentials //samba_share /media/samba_share'

The samba shares are mounted and available in r/w on the desktop and in nautilus but Easytag doesn't show them.
I have tried with different mount options and starting easytag as root but I still can't access the mounted shares.

This was working Ubuntu 9.04.

ProblemType: Bug
Architecture: i386
CheckboxSubmission: ac2eef9580bdd7643aa545a3cd46482d
CheckboxSystem: 16fd6ca6b51e65003d658ad584009cf7
Date: Fri Nov 20 18:21:03 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/easytag
Package: easytag 2.1.6-1
ProcEnviron:
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
SourcePackage: easytag
Uname: Linux 2.6.31-14-generic i686

Revision history for this message
Paillomams (aymeric-pallottini) wrote :
Revision history for this message
lsd2000 (parasha) wrote :

I can confirm this. I've upgraded 9.04 to 9.10 and smbfs or cifs does not show in tree.

Revision history for this message
Andreas Brudin (andreas-brudin) wrote :

I can confirm this too. All mounted directories show as empty.

Revision history for this message
BigPincer (grande-cornholio) wrote :

I've the same issue... EasyTag 2.1.6 on Ubuntu Lucid Lynx.

Revision history for this message
Keith Allcock (keith-allcock) wrote :

I have this issue and have found that tagtool also has the same problem, so I guess there is a shared library somewhere his has an issue!

Revision history for this message
In , Christian (christian-redhat-bugs) wrote :

Description of problem:
some directories are not displayed in the directory tree when browsing on a CIFS share

Version-Release number of selected component (if applicable):
easytag-2.1.6-5.fc12.i686

How reproducible:
100%

The reason is that sometimes the CIFS server provides very large inode numbers like:
stat /my/cifs/store
  File: `/my/cifs/store'
  Size: 0 Blocks: 0 IO Block: 16384 directory
Device: 1ch/28d Inode: 278185041108994 Links: 1
Access: (0755/drwxr-xr-x) Uid: ( 500/ chkr) Gid: ( 0/ root)
Access: 2010-08-31 20:38:47.000000000 +0200
Modify: 2010-04-24 17:10:15.000000000 +0200
Change: 2010-04-24 17:10:15.000000000 +0200

If easytag uses then "stat" on this directory, stat will return with -1 and the following errno: 75, Value too large for defined data type. As a result this directory will be ignored in src/browser.c in expand_cb() (there it is even worse: the return value of stat is not checked at all and so the data in statbuf may be just random).

Other programs suffer from the problem as well:
http://www.musicpd.org/mantis/view.php?id=2665

The best solution seems to be to compile the program with -D_FILE_OFFSET_BITS=64.

Revision history for this message
Christian Krause (chkr) wrote :

I've just reported the same bug in Fedora:

The reason is that sometimes the CIFS server provides very large inode numbers
like:
stat /my/cifs/store
  File: `/my/cifs/store'
  Size: 0 Blocks: 0 IO Block: 16384 directory
Device: 1ch/28d Inode: 278185041108994 Links: 1

If easytag uses then "stat" on this directory, stat will return with -1 and the
following errno: 75, Value too large for defined data type. As a result this
directory will be ignored in src/browser.c in expand_cb() (there it is even
worse: the return value of stat is not checked at all and so the data in
statbuf may be just random).

Other programs suffer from the problem as well:
http://www.musicpd.org/mantis/view.php?id=2665

The best solution seems to be to compile the program with
-D_FILE_OFFSET_BITS=64.

As a workaround it is possible to mount the CIFS share with the option "noserverino".

Revision history for this message
In , Bug (bug-redhat-bugs) wrote :

This message is a reminder that Fedora 12 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 12. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora
'version' of '12'.

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 Fedora version prior to Fedora 12'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 Fedora 12 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 Fedora please change the 'version' of this
bug to the applicable version. If you are unable to change the version,
please add a comment here and someone will do it for you.

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 Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

The process we are following is described here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Revision history for this message
In , Christian (christian-redhat-bugs) wrote :

The issue is still present in F13 and F14.

Revision history for this message
Paillomams (aymeric-pallottini) wrote :

I have checked the work around and it works for me. Although now I am using Ubuntu 10.10 but the bug was still present without this change in the mount options.

Revision history for this message
Eric from Onekama MI (ebeeman) wrote :

I can confirm this problem as well. I will attempt the workaround to mount with "noserverino". Using Ubuntu 10.04LTS

I was able to find support for Christian Krause diagnosis as well - when you attempt to reset the easytag default directory in "preferences", you get an error message stating "the selected path '....' isn't valid '.... ' (Value too large for defined data type)"

Revision history for this message
Eric from Onekama MI (ebeeman) wrote :

The noserverino option added to the line in my fstab file definitely addresses the issue for me as well.

Revision history for this message
Ari (a-r-i) wrote :

I can't delete folders (sometimes...) by using noserverino-flag, without the flag I can't use easytag. Any other workaround for this problem?

Revision history for this message
In , Bug (bug-redhat-bugs) wrote :

This message is a reminder that Fedora 13 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 13. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora
'version' of '13'.

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 Fedora version prior to Fedora 13'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 Fedora 13 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 Fedora please change the 'version' of this
bug to the applicable version. If you are unable to change the version,
please add a comment here and someone will do it for you.

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 Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

The process we are following is described here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Revision history for this message
In , Bug (bug-redhat-bugs) wrote :

Fedora 13 changed to end-of-life (EOL) status on 2011-06-25. Fedora 13 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
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in easytag (Ubuntu):
status: New → Confirmed
Revision history for this message
venik212 (venik212) wrote :

I may have found another, simpler workaround-- go to your file manager, which should be able to access folders on the network. Right click on the music folders, and select: "Open with" Easytag.
This seems to work OK.

Revision history for this message
venik212 (venik212) wrote :

Alternatively, one can select Show Hidden Folders in the Browser menu of Easytag. This shows .gvfs, which shows the Samba shares. I am using Lubuntu 12.04.

Bug Watch Updater (bug-watch-updater)
Changed in easytag (Fedora):
importance: Unknown → Medium
status: Unknown → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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