Linux - I cannot see the names of the files properly

[ghost]

Version 0.8.1 when I open a file I see this

[sbauer322]

That certainly is an odd one. Can you provide details about your operating system, and OS language settings (if applicable)? Also, does this happen anywhere else in Light Table, or it is just in the open dialog?

[ghost]

Arch Linux: https://aur.archlinux.org/packages/lighttable-bin/ In which commit did you fix it? Perhaps in lighttable-git is fixed.

[ghost]

In lighttable-git we have the same issue. Confirmed as I installed

[MarcusE1W]

I am using Archlinux as well and experience the same issue. However, I am pretty sure it has worked before and as the Lighttable binary package has not changed for a while I suspect it might have to do with Archlinux ?

[pitalig]

Same issue here in Manjaro Linux.

[celliern]

Same error. Trying to evaluate inline python code leads to unicode error.

I highly suspect that lighttable is built with py2 and has a conflict with ArchLinux default python env (which is py3).

I will try to force py2 use with the instruction on the Arch Wiki

[noxecane]

Anyone with a fix for this, was trying this for the first time and this is what I faced(also using arch linux). Perharp @cldwalker could help with some advise

[celliern]

I'm sure it is caused by lighttable asking for py2 and archlinux giving py3 as default. Did not achieve to fix it to... Maybe the devs can do something...

Le 17 juil. 2017 21:27, à 21:27, Arewa Olakunle [email protected] a écrit:

Anyone with a fix for this, was trying this for the first time and this is what I faced

-- You are receiving this because you commented. Reply to this email directly or view it on GitHub: https://github.com/LightTable/LightTable/issues/2343#issuecomment-315931430

[noxecane]

I have given up already, gone back to emacs... Hope it gets fixed regardless

[ghost]

Same issue here - has rendered LightTable unusable for me. I have tried both pre-built and own-built binaries, to no avail. Running Fedora 26 - Gnome.

[rundis]

Ouch. Well LT has changed for a quite a while, so it must be something platform/os related. I'll have a go at a few distros to see if I can reproduce.

[rundis]

Just installed fedora 24. Worked as expected. Same with ubuntu (14 though).

[rundis]

@celliern how is this the same issue. Evaluating python code is surely not the same as the file dialog not working (as in not showing file names properly) ? That sounds like a problem with the LT python plugin... which btw has several reported issues related to problems with python support (and which is lacking a maintainer btw !).

[mwooller]

I have a workaround which is to start lighttable from a cli and supply a directory path as an argument, that means I don't need to go near the file dialog. Thank you for looking into this.

[celliern]

Just a guess based on the fact that all the issues seems to happen with archlinux based distribution which has python3 default and one of the notable differences between py2 and py3 is how it deal with Unicode.

It's a clue, nothing more..

⁣Envoyé par TypeApp ​

Le 22 juil. 2017 16:27, à 16:27, Magnus Rundberget [email protected] a écrit:

@celliern how is this the same issue. Evaluating python code is surely not the same as the file dialog not working (as in not showing file names properly) ? That sounds like a problem with the LT python plugin... which btw has several reported issues related to problems with python support (and which is lacking a maintainer btw !).

-- You are receiving this because you were mentioned. Reply to this email directly or view it on GitHub: https://github.com/LightTable/LightTable/issues/2343#issuecomment-317208404

[sbauer322]

I would concur that this is likely an issue with some combination of py2/py3/the python plugin/ArchLinux.

[sbauer322]

Happens on ParrotOS as well https://github.com/LightTable/LightTable/issues/2349

[sbauer322]

Potentially a problem with our (rather old) electron version given that the character encoding issue is limited to the file chooser, which comes from electron.

[ghost]

Happens the same on Fedora 26. Tell me if I can do further research that can help fixing this issue. Thanks for the fix in advance.

[ghost]

Interestingly the self same problem can be seen with another Electron based project, GitKraken. It is certainly electron related and I am wondering if I should raise the issue with them...

[sbauer322]

I've only used GitKraken on Windows 8.1, Windows 10, and Ubuntu so I cannot confirm if they have a problem but Electron would indeed be the common thread between the two.

[nurizzahudin]

same issue here (on antergos) and i agree with @sbauer322, i also suspect electron that caused this problem. i experienced the same bug with pingendo, which as far as i know is another electron based apps

[pacuna]

same issue with Fedora 26 and Gnome

[sirolf2009]

Just bumped into the same issue on debian It's strange though, because I don't think I had this issue a few days ago. I think it came after installing some themes, but after playing around a bit in tweak tool I didn't manage to revert it.

$ uname -a
Linux northpool2 3.16.0-4-amd64 #1 SMP Debian 3.16.43-2+deb8u2 (2017-06-26) x86_64 GNU/Linux
$ lsb_release -a
No LSB modules are available.
Distributor ID:	Debian
Description:	Debian GNU/Linux testing (buster)
Release:	testing
Codename:	buster
$ python3 --version
Python 3.4.2
$ python --version
Python 2.7.13

[greyhands2]

so am assuming there is not any solution to this problem??

[MarcusE1W]

So, I have digged a bit. To start, the Save dialoge shows the same behaviour. LightTable uses the Electron function showOpenDialog and showSaveDialog in file dialogs.cljs. The Electron function description can be found here: https://xwartz.gitbooks.io/electron-gitbook/content/en/api/dialog.html

As far as I understand Electron uses GTK+ on linux for the native system dialogs. From there I have found this issue on GitKraken with a solution suggestion: https://github.com/Azd325/gitkraken/issues/45

The described solution looks like a bit of an hack and I have not tried it yet. It also indicates that pango, a framework that is mostly used by GTK might be the main culprit for what has changed. A quick look into their bug tracker has nothing unearthed yet...

[PigeonEngineer]

Issue still persists in lighttable-bin 0.8.1-1

Anybody know of a workaround?

Linux patriks-pc 4.9.50-1-MANJARO #1 SMP PREEMPT Thu Sep 14 09:07:15 UTC 2017 x86_64 GNU/Linux [patriks@patriks-pc ~]$ lsb_release -a LSB Version: n/a Distributor ID: ManjaroLinux Description: Manjaro Linux Release: 17.0.5 Codename: Gellivara [patriks@patriks-pc ~]$ python3 --version Python 3.6.2 [patriks@patriks-pc ~]$ python --version Python 3.6.2

[ferdavid1]

Same issue on ArchLinux, tried both the lighttable-bin and lighttable-git packages.

[tdan]

Follow @MarcusE1W comment, downgrading pango does solve it for now.

In my case, pango-1.40.9 was the version that caused the problem

$ ls /usr/lib64/ | grep pango
libpango-1.0.so
libpango-1.0.so.0
libpango-1.0.so.0.4000.9
libpangocairo-1.0.so
libpangocairo-1.0.so.0
libpangocairo-1.0.so.0.4000.9
libpangoft2-1.0.so
libpangoft2-1.0.so.0
libpangoft2-1.0.so.0.4000.9
libpangomm-1.4.so.1
libpangomm-1.4.so.1.0.30
libpangoxft-1.0.so
libpangoxft-1.0.so.0
libpangoxft-1.0.so.0.4000.9

Downgrading was easy and straight forward on Fedora 25: sudo dnf install pango-1.40.3-1.fc25.x86_64 pango-1.40.3-1.fc25.i686 --allowerasing

[ArchI3Chris]

Same problem. Again on Arch. And I don't think downgrading is an easy or useful solution. I have like 15 packages depending on pango. So, I have to expect downgrading to mess up my whole system. No thanks. I guess that means, back to Sublime Text 3 and the annoying "purchase me". I most certainly don't start downgrading my whole system (and manually!) to get one editor working. Ain't gonna happen.