Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[CLOSED] File tree doesn't open #12121

Open
core-ai-bot opened this issue Aug 30, 2021 · 4 comments
Open

[CLOSED] File tree doesn't open #12121

core-ai-bot opened this issue Aug 30, 2021 · 4 comments

Comments

@core-ai-bot
Copy link
Member

Issue by stevejclay
Tuesday Apr 28, 2020 at 15:32 GMT
Originally opened as adobe/brackets#15135


Prerequisites

  • [Yes ] Can you reproduce the problem with Debug -> Reload Without Extensions?
  • [ Yes] Did you perform a cursory search to see if your bug or enhancement is already reported?
  • [Yes] Did you read the Troubleshooting guide?

For more information on how to write a good bug report read here
For more information on how to contribute read here

Description

Brand new system box, fresh install of Ubuntu 20.4, fresh install of Brackets 1.14 (build 1.14.1-17752 (release-1.14.1 959fed135) build timestamp: Thu Nov 28 2019 08:58:11 GMT+0000. If I load via Activities to start Brackets and then use File, Open Folder and select a folder containing development version of my website the name of the top level folder appears in the tree view at the left side of the screen. But, it cannot be expanded. I have used Brackets for a long time - my entire web site was developed on it! But now, when I click on the folder name in tree view I just get the 'Open Folder' option again.

Steps to Reproduce

  1. [Start Brackets]
  2. [Use File, Open Folder, select folder containing files to be edited]
  3. [Click on arrow by the name of the folder in the tree view.]

Expected behavior: [What you expected to happen]
The tree view should expand and show the sub folders and the individual files
Actual behavior: [What actually happened]Gtk: Locale not supported by C library.
Using the fallback 'C' locale.

You just get the "Open Folder" option

Versions

OS version: 20.04
Brackets version: 1.14

There is a clue perhaps in what happens if I run Brackets from a terminal:
There are long list of errors and other comments, the second of which is:
Failed to load module "canberra-gtk-module"
(The first is "Gtk: Locale not supported by C library. Using the fallback 'C' locale." which doesn't sound quite as serious.)
I would suspect missing dependencies on my machine but I installed by running:
sudo snap install brackets --classic
which I thought would include all needed dependencies?

Thanks for any help you can offer and I hope that it is of some help that I posted the issue.

@core-ai-bot
Copy link
Member Author

Comment by stevejclay
Tuesday Apr 28, 2020 at 15:42 GMT


I installed the library canberra-gtk-module manually and that error has disappeared.
The next error is "Failed to load module "atk-bridge".
I still have the issue described above and will try to download and install this module although I am not finding any information about it on the internet so far.

@core-ai-bot
Copy link
Member Author

Comment by stevejclay
Tuesday Apr 28, 2020 at 15:53 GMT


I tried using apt to install libatk-adaptor - supposed to contain above item but it said I already had the latest version (2.34.1-3). I even tried libatk-adaptor:i386 as a comment on a support forum mentioned it - but it makes no difference, in a terminal I still get the 'Failed to load module 'atk-bridge' error and in Brackets I still can't expand the file tree. Hope this all helps.

@core-ai-bot
Copy link
Member Author

Comment by stevejclay
Tuesday Apr 28, 2020 at 15:56 GMT


In the issue report itself, section "Actual Behaviour" please ignore the locale bit - the actual behaviour is, as mentioned, that you just get the Open Folder option. The locale is mentioned again in the section of errors that can be seen when starting Brackets from a terminal... where it is one of the more minor errors I think.

@core-ai-bot
Copy link
Member Author

Comment by stevejclay
Wednesday Apr 29, 2020 at 14:56 GMT


This turned out - on more investigation - to be about the libcurl3 versus libcurl4 issue discussed in #14171. I used the editing of .deb file workaround and it worked for me too.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant