errors in directory listing prevents vfu from operating on affected directories

Bug #642688 reported by Mihail Tchetchelnitski
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
vfu (Debian)
Fix Released
Unknown
vfu (Ubuntu)
Fix Released
High
Unassigned

Bug Description

Binary package hint: vfu

Running a very recent almost completely clean install. Using Encrypted home directory.

uname -a
Linux xxxx 2.6.32-24-server #43-Ubuntu SMP Thu Sep 16 16:05:42 UTC 2010 x86_64 GNU/Linux

lsb_release -rd
Description: Ubuntu 10.04.1 LTS
Release: 10.04

apt-cache policy vfu
vfu:
  Installed: 4.10-1
  Candidate: 4.10-1
  Version table:
 *** 4.10-1 0
        500 http://fi.archive.ubuntu.com/ubuntu/ lucid/universe Packages
        100 /var/lib/dpkg/status

In the console all directory names display correctly, as in Midnight commander and other utilities. In vfu some random directory names have certain letters switched preventing any operations or manipulation of the dirs. If I try to enter such a dir i get an error that it does not exist, since vfu tries to use the incorrect name when entering it.

this bug happens every time I run vfu in "real" console and with SSH login as well

Example vfu output:

Path: /home/mtchetch/ (SORT:NAME+)
          SiZE TP #NAME 1 of 23
             0 <>>> .Privete ->
             0 [] .cache
            97 <> .ecryptfs -> /home/.ecryptfs/mtchetch/.ecryptfs
             0 [] .hsh
         3,718 [] .mc
             0 [] .mim
             0 [] .ufu
         7,420 -- .bash_history
           220 -- .bashologout
         3,103 -- .bashrc
         1,024 -- .dnd
            98 -- .lesstst
         2,489 -- .lfmrc
           675 -- .profele
        12,226 -- .vimiofo
         1,138 -- .vimrc
        92,238 -- .zshhistory
         5,160 -- .zshrc
            79 ** crypthsh
            94 ** decrypt.sh

The same dir listing with ls

ls -a
. .. .bash_history .bash_logout .bashrc .cache crypt.sh decrypt.sh .ecryptfs .lesshst .lfmrc .mc .Private .profile .rnd .ssh .vfu .vim .viminfo .vimrc .zshhistory .zshrc

Only some of the dirs seem to be affected.

locale
LANG=en_US.UTF-8
LC_CTYPE="en_US.UTF-8"
LC_NUMERIC="en_US.UTF-8"
LC_TIME="en_US.UTF-8"
LC_COLLATE="en_US.UTF-8"
LC_MONETARY="en_US.UTF-8"
LC_MESSAGES="en_US.UTF-8"
LC_PAPER="en_US.UTF-8"
LC_NAME="en_US.UTF-8"
LC_ADDRESS="en_US.UTF-8"
LC_TELEPHONE="en_US.UTF-8"
LC_MEASUREMENT="en_US.UTF-8"
LC_IDENTIFICATION="en_US.UTF-8"
LC_ALL=

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

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

Changed in vfu (Ubuntu):
status: New → Confirmed
Revision history for this message
Paul White (paulw2u) wrote :

I'm seeing this in two separate installations of 12.04, Ubuntu and Kubuntu.

Examples - .thunderbird appears as .thunrerbird and .gnomnecommander appears as .gnomeommanderer

tags: added: i386 precise
Revision history for this message
Paul White (paulw2u) wrote :

Also noted in Kubuntu 12.10 although the problem is very much reduced.

tags: added: quantal
tags: added: amd64
Paul White (paulw2u)
tags: added: raring
Revision history for this message
Paul White (paulw2u) wrote :

Compiling the latest 4.12 sources available from sourceforge.net produces an executable that doesn't display corrupted file and directory names.

My knowledge of compiling sources doesn't extend to knowing whether the fix is associated with compiling in a local 12.10 environment or the upgrading of the source files to version 4.12.

This bug can be fixed, so I am asking for someone with a little more knowledge about these matters to please fix it. :o)

Revision history for this message
Paul White (paulw2u) wrote :

According to the linked Debian bug report, version 4.12 fixes this bug. Please can someone update.

Changed in vfu (Debian):
status: Unknown → New
Paul White (paulw2u)
summary: - directory names contain errors, prevents operations
+ errors in directory listing prevents vfu from operating on affected
+ directories
tags: added: saucy
Changed in vfu (Debian):
status: New → Confirmed
Revision history for this message
Alberto Salvia Novella (es20490446e) wrote :

Priority set to 'High' because the bug renders essential features or functionality of the application or dependencies broken or ineffective.

Changed in vfu (Ubuntu):
importance: Undecided → High
Revision history for this message
Alberto Salvia Novella (es20490446e) wrote :

Status changed to 'Triaged' because the bug is:

- Valid.
- Well described.
- Reported in the upstream project (Debian).
- Ready to be worked on by a developer.

Changed in vfu (Ubuntu):
status: Confirmed → Triaged
Changed in vfu (Debian):
status: Confirmed → Fix Released
Revision history for this message
Paul White (paulw2u) wrote :

From changelog of vfu 4.16+repack-1 in Ubuntu 18.04

vfu (4.16+repack-1) unstable; urgency=medium

  * QA upload.
  * Set maintainer to Debian QA Group. (see #847513)
  * New upstream release.
    - Repack without the vfu/vfu-yas binary.
    - Fixes wrong listing of filenames. (Closes: #666150)
    - Fixes FTBFS with clang. (Closes: #756330)
  * Apply patch from Jari Aalto:
    - Remove deprecated dpatch and upgrade to packaging format "3.0 quilt".
    - Update to Standards-Version to 3.9.3 and debhelper to 9.
    (Closes: #664402)

 -- Adrian Bunk <email address hidden> Sun, 27 Aug 2017 12:31:40 +0300

Confirmed as fixed so marking as Fix Released

Changed in vfu (Ubuntu):
status: Triaged → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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