Bl-places pipemenu issues "solve"

wagmic · 2018-12-17 20:04:51

Hi i can't use bl-places pipemnu
when i use this pipemnu i have an error (in french) : sortie du pipemenus invalide <<bl-places pipemenu>>
I copy on github the text of the pipemenu and change it in my computer but the issue is still there.
If somebody can explain me what to do it will great.
Merci

─╼ wagmic ╺─╸ bunsenwag [~]
└────╼ inxi -F
System:    Host: bunsenwag Kernel: 4.9.0-8-amd64 x86_64 (64 bit)
           Desktop: Openbox 3.6.1 Distro: BunsenLabs GNU/Linux 9.6 (Helium)
Machine:   Device: laptop System: Sony product: VGN-FW11L v: C600GV11
           Mobo: Sony model: VAIO
           BIOS: American Megatrends v: R0270Y0 date: 10/07/2009
Battery    BAT0: charge: 34.5 Wh 100.1% condition: 34.5/50.6 Wh (68%)
CPU:       Dual core Intel Core2 Duo P8400 (-MCP-) cache: 3072 KB 
           clock speeds: max: 2267 MHz 1: 1600 MHz 2: 1600 MHz
Graphics:  Card: Advanced Micro Devices [AMD/ATI] RV620/M82 [Mobility Radeon HD 3450/3470]
           Display Server: X.Org 1.19.2 drivers: ati,radeon (unloaded: modesetting,fbdev,vesa)
           Resolution: 1600x900@59.95hz
           GLX Renderer: Gallium 0.4 on AMD RV620 (DRM 2.49.0 / 4.9.0-8-amd64, LLVM 3.9.1)
           GLX Version: 3.0 Mesa 13.0.6
Audio:     Card-1 Advanced Micro Devices [AMD/ATI] RV620 HDMI Audio [Radeon HD 3450/3470/3550/3570]
           driver: snd_hda_intel
           Card-2 Intel 82801I (ICH9 Family) HD Audio Controller
           driver: snd_hda_intel
           Sound: Advanced Linux Sound Architecture v: k4.9.0-8-amd64
Network:   Card-1: Intel WiFi Link 5100 driver: iwlwifi
           IF: wlan0 state: up mac: 00:16:ea:26:c9:f4
           Card-2: Marvell 88E8055 PCI-E Gigabit Ethernet Controller
           driver: sky2
           IF: eth0 state: down mac: 00:1d:ba:1a:8f:33
Drives:    HDD Total Size: 500.1GB (20.1% used)
           ID-1: /dev/sda model: ST500LM000 size: 500.1GB
Partition: ID-1: / size: 11G used: 3.3G (34%) fs: ext4 dev: /dev/sda5
           ID-2: /var size: 3.7G used: 2.0G (58%) fs: ext4 dev: /dev/sda6
           ID-3: /home size: 38G used: 8.3G (23%) fs: ext4 dev: /dev/sda9
           ID-4: /tmp size: 706M used: 1.5M (1%) fs: ext4 dev: /dev/sda8
           ID-5: swap-1 size: 4.29GB used: 0.00GB (0%) fs: swap dev: /dev/sda7
Sensors:   System Temperatures: cpu: 56.0C mobo: 56.0C
           Fan Speeds (in rpm): cpu: N/A
Info:      Processes: 159 Uptime: 2:11 Memory: 898.9/3954.1MB
           Client: Shell (bash) inxi: 2.3.5

Last edited by wagmic (2018-12-20 20:54:05)

damo · 2018-12-17 21:23:03

Have you made any changes to your system, configs, upgrades etc?

Please post the (English) output with

LC_ALL=C bl-places-pipemenu

Last edited by damo (2018-12-17 21:24:26)

malm · 2018-12-17 22:40:26

Did you put a dash between places and pipemenu?

wagmic · 2018-12-18 20:20:41

hi i haven't made any change to my system exept normal upgrade
the output:

ezszd&apos;
        </command>
    </action>
</item>
<item label="default__dual.wav">
    <action name="Execute">
        <command>
        &apos;/usr/bin/bl-places-pipemenu&apos; --open &apos;/home/wagmic/default_dual.wav&apos;
        </command>
    </action>
</item>
<item label="default__mono.wav">
    <action name="Execute">
        <command>
        &apos;/usr/bin/bl-places-pipemenu&apos; --open &apos;/home/wagmic/default_mono.wav&apos;
        </command>
    </action>
</item>
<item label="hardinfo__report.html">
    <action name="Execute">
        <command>
        &apos;/usr/bin/bl-places-pipemenu&apos; --open &apos;/home/wagmic/hardinfo_report.html&apos;
        </command>
    </action>
</item>
<item label=".Xresources">
    <action name="Execute">
        <command>
        &apos;/usr/bin/bl-places-pipemenu&apos; --open &apos;/home/wagmic/.Xresources&apos;
        </command>
    </action>
</item>
<item label=".bash__aliases">
    <action name="Execute">
        <command>
        &apos;/usr/bin/bl-places-pipemenu&apos; --open &apos;/home/wagmic/.bash_aliases&apos;
        </command>
    </action>
</item>
<item label=".bashrc">
    <action name="Execute">
        <command>
        &apos;/usr/bin/bl-places-pipemenu&apos; --open &apos;/home/wagmic/.bashrc&apos;
        </command>
    </action>
</item>
<item label=".inputrc">
    <action name="Execute">
        <command>
        &apos;/usr/bin/bl-places-pipemenu&apos; --open &apos;/home/wagmic/.inputrc&apos;
        </command>
    </action>
</item>
<item label=".gtkrc-2.0.mine">
    <action name="Execute">
        <command>
        &apos;/usr/bin/bl-places-pipemenu&apos; --open &apos;/home/wagmic/.gtkrc-2.0.mine&apos;
        </command>
    </action>
</item>
<item label=".profile">
    <action name="Execute">
        <command>
        &apos;/usr/bin/bl-places-pipemenu&apos; --open &apos;/home/wagmic/.profile&apos;
        </command>
    </action>
</item>
<item label=".xsessionrc">
    <action name="Execute">
        <command>
        &apos;/usr/bin/bl-places-pipemenu&apos; --open &apos;/home/wagmic/.xsessionrc&apos;
        </command>
    </action>
</item>
<item label=".xsession-errors">
    <action name="Execute">
        <command>
        &apos;/usr/bin/bl-places-pipemenu&apos; --open &apos;/home/wagmic/.xsession-errors&apos;
        </command>
    </action>
</item>
</openbox_pipe_menu>

@malm my entry menu is : bl-places-pipemenu

this is the entry in the menu :

</menu>
		<separator/>
		<menu execute="bl-places-pipemenu" id="pipe-placesmenu" label="Places"/>
		<menu execute="bl-recent-files-pipemenu -rl15" id="pipe-recentfilesmenu" label="Recent Files"/>
		<separator/>

thanks

Last edited by wagmic (2018-12-18 20:21:22)

damo · 2018-12-18 20:51:41

^ Is that the full output of the command? The beginning is missing.

malm · 2018-12-19 06:15:52

It might be struggling to handle one of your files.

Have you got anything unusual in your $HOME directory? For example anything from Windows or anything Unicode.

What’s the file before default_dual.wav?
Is ‘ezszd’ a clue (might be mangled).

You could move those files to a sub directory. Then move them back one at a time to catch the culprit (if indeed this is the problem)

Just a thought.

Last edited by malm (2018-12-19 06:17:19)

ohnonot · 2018-12-19 07:12:49

wagmic wrote:

ezszd&apos;
        </command>
    </action>
</item>
<item label="default__dual.wav">
... etc. ...

this can't be right.

johnraff · 2018-12-19 07:19:47

malm wrote:

It might be struggling to handle one of your files.

Eager to hear about it if that's the case. The places pipemenu is supposed to be able to handle any Unix-permitted file names...

wagmic · 2018-12-20 20:52:52

Solve thanks you
I was having a strange unicode file with a very long name in my home , i just deleted it and now all is good.
Thanks for your efforts and merry chrismas

Last edited by wagmic (2018-12-20 20:55:36)

johnraff · 2018-12-21 02:46:14

Hi wagmic, glad to hear the issue went away!

Could you possibly post here the long unicode filename that broke the menu? I'd like to see if the script can be tweaked to handle it.

wagmic · 2018-12-21 17:35:52

HI johnraff this is the name : /home/wagmic/dddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddxcezszd

out of subject
i'am one of your twitter follower

damo · 2018-12-21 18:46:14

^

/home/damo/fffffffffffffffffffffffffffffffffffffff**kme.txt

johnraff · 2018-12-22 01:25:23

wagmic wrote:

HI johnraff this is the name : /home/wagmic/dddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddxcezszd

So just a long line of d's, no funny unicode characters? I'll give it a try - maybe there's a string length limit somewhere.

i'am one of your twitter follower

Cool! Same name? I'll follow you back. (My Twitter feed is mostly politics these days though.)

DeepDayze · 2018-12-22 02:37:39

damo wrote:

^
/home/damo/fffffffffffffffffffffffffffffffffffffff**kme.txt

Getting snarky I see ]:D

On topic, most likely really long filenames or paths could cause this, even if composed of standard characters. So I can believe there's some sort of length limit.

Last edited by DeepDayze (2018-12-22 02:39:09)

johnraff · 2018-12-23 02:58:19

wagmic wrote:

HI johnraff this is the name : /home/wagmic/dddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddxcezszd

I created a file with that name and the "places" pipemenu works OK with it. So it's not the length.

DeepDayze · 2018-12-23 03:42:41

johnraff wrote:

wagmic wrote:
HI johnraff this is the name : /home/wagmic/dddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddxcezszd
I created a file with that name and the "places" pipemenu works OK with it. So it's not the length.

There may well be some characters hidden and not displayed that could been causing the havoc. Should be a way to display any hidden characters though.

malm · 2018-12-23 07:15:54

@wagmic

May we assume that the file came from Windows? How did you move it across. Was it in a zip file which you then unzipped on Linux?

On Linux, filenames should just be a NUL-terminated series of bytes. UTF-8 works with this, as it doesn't contain NUL-bytes (except at the end). Unicode sometimes contains NUL-bytes which is why it creates problems.

Have you still got the file? What do you get from the following command?

file -i ddddddddddddddddddd<whatever>

Not sure if 'file' only checks the contents rather than the filename though.

@johnraff - how do you feel? Is it an edgecase we want to handle? I suspect that checking files individually would be rather expensive. Ideally we'd want something that checks a whole directory for Unicode filenames, but not sure if that exists, nor would I know how to write one.

johnraff · 2018-12-24 03:56:38

@malm UTF8 names should work right?
The script is supposed to accept any UNIX filename, so as you say names containing nul-bytes are no good. I didn't know such names were even possible!

Let's have a think about it - and a bit of web-searching. Maybe there is a lightweight utility that can check the directory before going over the files individually.

If it's too hard we could maybe consider ignoring the issue.

johnraff · 2018-12-26 08:25:05

^^On second thoughts, it seems to me that any Linux app is likely to choke on non-Unix filenames, so I don't think there's much point in putting effort into letting our places menu handle them.

malm · 2018-12-26 22:14:06

^^ Yes, UTF-8 will work.

We could consider at least 'gracefully surviving' other encodings.

As I'm sure many know, Linux treats filenames as a sequence of bytes, terminated by a NUL-byte. The file system is agnostic to encondings, leaving the handling of these to user applications.

One of the reasons for choosing UTF-8 as the encoding for Unicode characters on Linux, was the backward compatibility and absence of NUL-bytes.

The problem isn't just NUL-bytes though. Depending on the extent to which applications 'validate', issues could be experienced with control characters and other things.

I had a quick play with the filename converter tool 'convmv'. When converting to UTF-16LE (which contains NUL-bytes), convmv complains that the filename contains characters that do not conform to POSIX filesystem requirements. I'm sure that warning refers to NUL-bytes, because other encodings work fine.

$ convmv -r --notest -f UTF-8 -t UTF-16LE abc

I have written a quick directory validation program, based on CCAN's charset.c

It is fast and could easily be incorporated into the bl-places-pipemenu script if you fancy it.

I have tried it with the following:

$ convmv -r --notest -f UTF-8 -t latin-1 åäö
mv "./åäö"	"./"
Ready! I converted 1 files in 0 seconds.

$ ./bl-utf8-validate-dir .
fatal: file '' is not UTF-8 compatible

I'm not bothered though if you want to leave it (possibly in the interest of avoiding complexity). I enjoyed having a play with encoding/decoding.

The following man pages are quite helpful:

charsets(7)
stat(2)
readdir(3)
convmv(1)

Last edited by malm (2018-12-26 22:18:57)

#1 2018-12-17 20:04:51

Bl-places pipemenu issues "solve"

#2 2018-12-17 21:23:03

Re: Bl-places pipemenu issues "solve"

#3 2018-12-17 22:40:26

Re: Bl-places pipemenu issues "solve"

#4 2018-12-18 20:20:41

Re: Bl-places pipemenu issues "solve"

#5 2018-12-18 20:51:41

Re: Bl-places pipemenu issues "solve"

#6 2018-12-19 06:15:52

Re: Bl-places pipemenu issues "solve"

#7 2018-12-19 07:12:49

Re: Bl-places pipemenu issues "solve"

#8 2018-12-19 07:19:47

Re: Bl-places pipemenu issues "solve"

#9 2018-12-20 20:52:52

Re: Bl-places pipemenu issues "solve"

#10 2018-12-21 02:46:14

Re: Bl-places pipemenu issues "solve"

#11 2018-12-21 17:35:52

Re: Bl-places pipemenu issues "solve"

#12 2018-12-21 18:46:14

Re: Bl-places pipemenu issues "solve"

#13 2018-12-22 01:25:23

Re: Bl-places pipemenu issues "solve"

#14 2018-12-22 02:37:39

Re: Bl-places pipemenu issues "solve"

#15 2018-12-23 02:58:19

Re: Bl-places pipemenu issues "solve"

#16 2018-12-23 03:42:41

Re: Bl-places pipemenu issues "solve"

#17 2018-12-23 07:15:54

Re: Bl-places pipemenu issues "solve"

#18 2018-12-24 03:56:38

Re: Bl-places pipemenu issues "solve"

#19 2018-12-26 08:25:05

Re: Bl-places pipemenu issues "solve"

#20 2018-12-26 22:14:06

Re: Bl-places pipemenu issues "solve"

Board footer