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

[Linux] Brackets depends on obsolete libgcrypt11 package which is no longer included by default #10255

Closed
Romane-T opened this Issue Dec 20, 2014 · 158 comments

Comments

Projects
None yet
@Romane-T

Romane-T commented Dec 20, 2014

Brackets not currently installable on Jessie. Brackets has dependency on libgcrypt11, which is not available in the Jessie repositories. Jessie repositories have libgcrypt20. Brackets can be installed if user locates a copy of libgcrypt11, which can be co-installed with libgryypt20, but considering Jessie in freeze to become stable, doing this this should be unnecessary. Removing libgcrypt11 from system removes Brackets at the same time.
Romane

@prksingh prksingh added the Linux only label Jan 21, 2015

@prksingh

This comment has been minimized.

Show comment
Hide comment
@prksingh

prksingh Jan 21, 2015

Contributor

@Romane-T Hey, could you try to build the appshell on your system.
The repo is located at: https://github.com/adobe/brackets-shell.
The build instructions are at: https://github.com/adobe/brackets-shell/wiki/Building-Brackets-Shell
This may help us locate if the error is with the installer.

You may want to check out this PR: adobe/brackets-shell#489
This may fix your issue but its not ready for testing yet.

Contributor

prksingh commented Jan 21, 2015

@Romane-T Hey, could you try to build the appshell on your system.
The repo is located at: https://github.com/adobe/brackets-shell.
The build instructions are at: https://github.com/adobe/brackets-shell/wiki/Building-Brackets-Shell
This may help us locate if the error is with the installer.

You may want to check out this PR: adobe/brackets-shell#489
This may fix your issue but its not ready for testing yet.

@Romane-T

This comment has been minimized.

Show comment
Hide comment
@Romane-T

Romane-T Jan 21, 2015

On 21/01/15 21:17, Prashant Kumar Singh wrote:

@Romane-T https://github.com/Romane-T Hey, could you try to build
the appshell on your system.
The repo is located at: https://github.com/adobe/brackets-shell.
The build instructions are at:
https://github.com/adobe/brackets-shell/wiki/Building-Brackets-Shell
This may help us locate if the error is with the installer.

You may want to check out this PR: adobe/brackets-shell#489
adobe/brackets-shell#489
This may fix your issue but its not ready for testing yet.


Reply to this email directly or view it on GitHub
#10255 (comment).

Good morning

Many thanks for your reply.

Sorry, but looked at the material at the links given, and too much over
my head. The build instructions, though they seemed sort of straight
forward, still left me confused. The last link to the "PR" - well,
first, I have utterly no idea what a "PR" is, and what was on that page
made absolutely zero sense to me.

I am not a programmer. All that I learned about programming was a bit
more than a quarter a century ago. Everything has dramatically since
then, and I have forgotten it all anyway. I use Brackets solely to write
my HTML pages, and even then fairly simple.

I have no idea what the difference between libgcrypt11 and libgcrypt20
is, and have no interest in finding out. That is a developer issue.

Perhaps I am being simplistic, but it strikes me as a case of Brackets
declaring a dependency for libgcrypt11, while Debian have updated in
Jessie to libgcrypt20. If I remove libgcrypt11, Brackets is removed -
that's the nature of a dependency. Debian does not carry Brackets in its
repositories, so the issue returns to Brackets keeping up to what the
distribution does.

Reason and logic thus tells me that attempting to do the build you
suggested is unlikely to fix the problem UNLESS this updates the
dependencies for libgcrypt. If it doesn't update that dependency, then
the problem still exists, and attempting to remove libgcrypt11 will
still remove Brackets. And if it is the fix to the problem, then I am
certain that at least one of your developers who knows something more
about building and deploying will be quite capable of testing it and
applying it for the next release, which I would assume they are doing
anyway.

And while it is not fixed, Jessie users, except the small minority who
keep a copy of libgcrypt11 on hand, will not be users of Brackets,
noting that Jessie is soon to go stable (172 bugs left to squash).

With greetings

Romane

Romane-T commented Jan 21, 2015

On 21/01/15 21:17, Prashant Kumar Singh wrote:

@Romane-T https://github.com/Romane-T Hey, could you try to build
the appshell on your system.
The repo is located at: https://github.com/adobe/brackets-shell.
The build instructions are at:
https://github.com/adobe/brackets-shell/wiki/Building-Brackets-Shell
This may help us locate if the error is with the installer.

You may want to check out this PR: adobe/brackets-shell#489
adobe/brackets-shell#489
This may fix your issue but its not ready for testing yet.


Reply to this email directly or view it on GitHub
#10255 (comment).

Good morning

Many thanks for your reply.

Sorry, but looked at the material at the links given, and too much over
my head. The build instructions, though they seemed sort of straight
forward, still left me confused. The last link to the "PR" - well,
first, I have utterly no idea what a "PR" is, and what was on that page
made absolutely zero sense to me.

I am not a programmer. All that I learned about programming was a bit
more than a quarter a century ago. Everything has dramatically since
then, and I have forgotten it all anyway. I use Brackets solely to write
my HTML pages, and even then fairly simple.

I have no idea what the difference between libgcrypt11 and libgcrypt20
is, and have no interest in finding out. That is a developer issue.

Perhaps I am being simplistic, but it strikes me as a case of Brackets
declaring a dependency for libgcrypt11, while Debian have updated in
Jessie to libgcrypt20. If I remove libgcrypt11, Brackets is removed -
that's the nature of a dependency. Debian does not carry Brackets in its
repositories, so the issue returns to Brackets keeping up to what the
distribution does.

Reason and logic thus tells me that attempting to do the build you
suggested is unlikely to fix the problem UNLESS this updates the
dependencies for libgcrypt. If it doesn't update that dependency, then
the problem still exists, and attempting to remove libgcrypt11 will
still remove Brackets. And if it is the fix to the problem, then I am
certain that at least one of your developers who knows something more
about building and deploying will be quite capable of testing it and
applying it for the next release, which I would assume they are doing
anyway.

And while it is not fixed, Jessie users, except the small minority who
keep a copy of libgcrypt11 on hand, will not be users of Brackets,
noting that Jessie is soon to go stable (172 bugs left to squash).

With greetings

Romane

@prksingh

This comment has been minimized.

Show comment
Hide comment
@prksingh

prksingh Jan 23, 2015

Contributor

I think libgcrypt11 is required for CEF(https://code.google.com/p/chromiumembedded/) that most brackets features run on. The link i had posted is a link to a pull request that upgrades to a more recent version of CEF (I think libcrypt20 will work with the new CEF)

Here is where you can download the build for linux: https://github.com/adobe/brackets/releases/tag/linux-cef-2171

I don't have access to a system with Debian so I can't be sure this build will fix your issue. There may be a few other small glitches as this build is still being tested. I will try to update the release with a more stable build once ready. Thanks!

Contributor

prksingh commented Jan 23, 2015

I think libgcrypt11 is required for CEF(https://code.google.com/p/chromiumembedded/) that most brackets features run on. The link i had posted is a link to a pull request that upgrades to a more recent version of CEF (I think libcrypt20 will work with the new CEF)

Here is where you can download the build for linux: https://github.com/adobe/brackets/releases/tag/linux-cef-2171

I don't have access to a system with Debian so I can't be sure this build will fix your issue. There may be a few other small glitches as this build is still being tested. I will try to update the release with a more stable build once ready. Thanks!

@Romane-T

This comment has been minimized.

Show comment
Hide comment
@Romane-T

Romane-T Jan 23, 2015

On 23/01/15 21:44, Prashant Kumar Singh wrote:

I think libgcrypt11 is required for
CEF(https://code.google.com/p/chromiumembedded/) that most brackets
features run on. The link i had posted is a link to a pull request
that upgrades to a more recent version of CEF (I think libcrypt20 will
work with the new CEF)

Here is where you can download the build for linux:
https://github.com/adobe/brackets/releases/tag/linux-cef-2171

I don't have access to a system with Debian so I can't be sure this
build will fix your issue. There may be a few other small glitches as
this build is still being tested. I will try to update the release
with a more stable build once ready. Thanks!


Reply to this email directly or view it on GitHub
#10255 (comment).

Good morning

Now this is something within my capacity, and my thanks for giving me
the opportunity.

Your first paragraph, I gather that whatever a CEF is, the new version
might work with libgcrypt20

Downloaded the build in the second link, and before installing it,
purged the version already installed. Once purged, tested to see if
removing libgcrypt11 would affect any other package. There were no other
dependencies.

Installed the version just downloaded from the link in your email. The
install went without a hitch - zero warnings or errors.

Opened the application to ensure that it ran fine. it did. Noticed (an
aside to the topic of this thread) on closing that, though still needing
two clicks on the x button, the first click greyed the entire
application window, then on the second click the window closed as
expected. Previously, the first click on the x button did not appear to
do anything, so it would appear that some progress has been made to
resolving this issue. Closing through the 'File' menu closed the
application normally.

After closing Brackets, attempted to remove libgcrypt11. Unfortunately,
removing libgcrypt11 will still remove Brackets with it, so this build
(Release 1.2 experimental build 1.2.0-15628 (master 5dddaa1) build
timestamp: Thu Jan 22 2015 03:59:17 GMT-0800.) still retains the issue.

I even tried a reboot, knowing with 99% certainty that it would make no
difference. It didn't.

With warm greetings

Romane

Romane-T commented Jan 23, 2015

On 23/01/15 21:44, Prashant Kumar Singh wrote:

I think libgcrypt11 is required for
CEF(https://code.google.com/p/chromiumembedded/) that most brackets
features run on. The link i had posted is a link to a pull request
that upgrades to a more recent version of CEF (I think libcrypt20 will
work with the new CEF)

Here is where you can download the build for linux:
https://github.com/adobe/brackets/releases/tag/linux-cef-2171

I don't have access to a system with Debian so I can't be sure this
build will fix your issue. There may be a few other small glitches as
this build is still being tested. I will try to update the release
with a more stable build once ready. Thanks!


Reply to this email directly or view it on GitHub
#10255 (comment).

Good morning

Now this is something within my capacity, and my thanks for giving me
the opportunity.

Your first paragraph, I gather that whatever a CEF is, the new version
might work with libgcrypt20

Downloaded the build in the second link, and before installing it,
purged the version already installed. Once purged, tested to see if
removing libgcrypt11 would affect any other package. There were no other
dependencies.

Installed the version just downloaded from the link in your email. The
install went without a hitch - zero warnings or errors.

Opened the application to ensure that it ran fine. it did. Noticed (an
aside to the topic of this thread) on closing that, though still needing
two clicks on the x button, the first click greyed the entire
application window, then on the second click the window closed as
expected. Previously, the first click on the x button did not appear to
do anything, so it would appear that some progress has been made to
resolving this issue. Closing through the 'File' menu closed the
application normally.

After closing Brackets, attempted to remove libgcrypt11. Unfortunately,
removing libgcrypt11 will still remove Brackets with it, so this build
(Release 1.2 experimental build 1.2.0-15628 (master 5dddaa1) build
timestamp: Thu Jan 22 2015 03:59:17 GMT-0800.) still retains the issue.

I even tried a reboot, knowing with 99% certainty that it would make no
difference. It didn't.

With warm greetings

Romane

@MarcelGerber

This comment has been minimized.

Show comment
Hide comment
@MarcelGerber

MarcelGerber Jan 23, 2015

Contributor

Some clarification here:
PR is short for "Pull Request" and it's when somebody proposes a change to the source code. It's pretty GitHub-specific, and as GitHub's all about social coding, it's a huge feature over here.

CEF is the "Chromium Embedded Framework", which is basically a configurable and embeddable version of the Chrome/Chromium browser. It's used in Brackets to render the UI, as Brackets is mostly written in HTML, CSS, and JavaScript - just like your website.

Contributor

MarcelGerber commented Jan 23, 2015

Some clarification here:
PR is short for "Pull Request" and it's when somebody proposes a change to the source code. It's pretty GitHub-specific, and as GitHub's all about social coding, it's a huge feature over here.

CEF is the "Chromium Embedded Framework", which is basically a configurable and embeddable version of the Chrome/Chromium browser. It's used in Brackets to render the UI, as Brackets is mostly written in HTML, CSS, and JavaScript - just like your website.

@Romane-T

This comment has been minimized.

Show comment
Hide comment
@Romane-T

Romane-T Jan 24, 2015

Good morning

This is, for a complete non-programmer as myself (I don't count the HTML
I do as programming), quite useful information. Not just for the
explanation of the acronyms - I feel a little less like an alien now in
a foreign environment - but for the clear fact, combining information in
both your and Prashant's posts, that the issue itself is not Brackets so
much as upstream. Till upstream provide an update that resolves the
issue, Brackets has its hands tied.

This is the only issue with Brackets and Jessie (Debian 8) that can
become a show-stopper. Not difficult to resolve if one knows where to
look. Have just checked to make sure, and Debian stable (Wheezy), due to
become old-stable when Jessie is declared stable, has libgcrypt11. It
will remain old-stable till the successor to Jessie goes stable and
Jessie becomes old-stable, which gives a fair window of time during
which the Chromium Embedded Framework can do the catchup. Perhaps just a
note in a relevant place for the unaware that this dependency exists for
Brackets at this time, and how they can obtain it - just a random
thought. Installing via dpkg is then a breeze.

In the interim, if you would like someone to provide any testing on
future development versions of Brackets to assess if this issue has been
resolved, feel free to ask. It will be my pleasure, even if it is only a
very tiny contribution back to the very excellent Brackets.

With greetings

Romane

On 24/01/15 00:11, Marcel Gerber wrote:

Some clarification here:
PR is short for "Pull Request" and it's when somebody proposes a
change to the source code. It's pretty GitHub-specific, and as
GitHub's all about social coding, it's a huge feature over here.

CEF is the "Chromium Embedded Framework", which is basically a
configurable and embeddable version of the Chrome/Chromium browser.
It's used in Brackets to render the UI, as Brackets is mostly written
in HTML, CSS, and JavaScript - just like your website.


Reply to this email directly or view it on GitHub
#10255 (comment).

Romane-T commented Jan 24, 2015

Good morning

This is, for a complete non-programmer as myself (I don't count the HTML
I do as programming), quite useful information. Not just for the
explanation of the acronyms - I feel a little less like an alien now in
a foreign environment - but for the clear fact, combining information in
both your and Prashant's posts, that the issue itself is not Brackets so
much as upstream. Till upstream provide an update that resolves the
issue, Brackets has its hands tied.

This is the only issue with Brackets and Jessie (Debian 8) that can
become a show-stopper. Not difficult to resolve if one knows where to
look. Have just checked to make sure, and Debian stable (Wheezy), due to
become old-stable when Jessie is declared stable, has libgcrypt11. It
will remain old-stable till the successor to Jessie goes stable and
Jessie becomes old-stable, which gives a fair window of time during
which the Chromium Embedded Framework can do the catchup. Perhaps just a
note in a relevant place for the unaware that this dependency exists for
Brackets at this time, and how they can obtain it - just a random
thought. Installing via dpkg is then a breeze.

In the interim, if you would like someone to provide any testing on
future development versions of Brackets to assess if this issue has been
resolved, feel free to ask. It will be my pleasure, even if it is only a
very tiny contribution back to the very excellent Brackets.

With greetings

Romane

On 24/01/15 00:11, Marcel Gerber wrote:

Some clarification here:
PR is short for "Pull Request" and it's when somebody proposes a
change to the source code. It's pretty GitHub-specific, and as
GitHub's all about social coding, it's a huge feature over here.

CEF is the "Chromium Embedded Framework", which is basically a
configurable and embeddable version of the Chrome/Chromium browser.
It's used in Brackets to render the UI, as Brackets is mostly written
in HTML, CSS, and JavaScript - just like your website.


Reply to this email directly or view it on GitHub
#10255 (comment).

@peterflynn

This comment has been minimized.

Show comment
Hide comment
@peterflynn

peterflynn Jan 27, 2015

Member

Note: the issue with the close button is tracked as #4611, and it is indeed expected to be slightly improved in the test build linked above

Member

peterflynn commented Jan 27, 2015

Note: the issue with the close button is tracked as #4611, and it is indeed expected to be slightly improved in the test build linked above

@peterflynn

This comment has been minimized.

Show comment
Hide comment
@peterflynn

peterflynn Jan 27, 2015

Member

I think to fully fix this we need to update the dependencies on our .deb build script to match the dependencies of the new CEF. @jasonsanjose said this is kind of a pain (manual process), but we've done it in the past for some earlier CEF updates, and it seems necessary this time.

Member

peterflynn commented Jan 27, 2015

I think to fully fix this we need to update the dependencies on our .deb build script to match the dependencies of the new CEF. @jasonsanjose said this is kind of a pain (manual process), but we've done it in the past for some earlier CEF updates, and it seems necessary this time.

@Romane-T

This comment has been minimized.

Show comment
Hide comment
@Romane-T

Romane-T Jan 28, 2015

Good morning

On 28/01/15 07:35, Peter Flynn wrote:

I think to fully fix this we need to update the dependencies on our
.deb build script to match the dependencies of the new CEF.
@jasonsanjose https://github.com/jasonsanjose said this is kind of a
pain (manual process), but we've done it in the past for some earlier
CEF updates, and it seems necessary this time.


Reply to this email directly or view it on GitHub
#10255 (comment).

Am I right in assuming that it is a tedious process rather than a
programming process? If not a programming process, for someone like
myself who would need perhaps some (or likely more) hand-holding as he

a) has no idea how to do a pull request and the associated return of
changed data
b) no idea of what actually needs to be changed

but is willing to learn provided there is someone with patience who can
answer sometimes (often?) silly questions (in other words, I can appear
really dumb sometimes), be of any use? Think of me as noob from core to
surface.

The doing will, in the final analysis, prove the best teacher.

Besides (Romane grinning), it would give me something to do every third
day. rather than my current cycle of every second day with existing
projects.

With greetings

Romane

Romane-T commented Jan 28, 2015

Good morning

On 28/01/15 07:35, Peter Flynn wrote:

I think to fully fix this we need to update the dependencies on our
.deb build script to match the dependencies of the new CEF.
@jasonsanjose https://github.com/jasonsanjose said this is kind of a
pain (manual process), but we've done it in the past for some earlier
CEF updates, and it seems necessary this time.


Reply to this email directly or view it on GitHub
#10255 (comment).

Am I right in assuming that it is a tedious process rather than a
programming process? If not a programming process, for someone like
myself who would need perhaps some (or likely more) hand-holding as he

a) has no idea how to do a pull request and the associated return of
changed data
b) no idea of what actually needs to be changed

but is willing to learn provided there is someone with patience who can
answer sometimes (often?) silly questions (in other words, I can appear
really dumb sometimes), be of any use? Think of me as noob from core to
surface.

The doing will, in the final analysis, prove the best teacher.

Besides (Romane grinning), it would give me something to do every third
day. rather than my current cycle of every second day with existing
projects.

With greetings

Romane

@MarcelGerber

This comment has been minimized.

Show comment
Hide comment
@MarcelGerber

MarcelGerber Jan 31, 2015

Contributor

The dependency originates from https://github.com/adobe/brackets-shell/blob/master/installer/linux/debian/control#L8.
Changing it to libgcrypt11 (>= 1.4.5) | libgcrypt20 should work, but I'm not sure if CEF/Chromium already support libgcrypt20.

@Romane-T Could you just test if apt-get install chromium works for you? (Of course in Jessie and without libgcrypt11 installed) If it doesn't work, you can be sure that Brackets currently can't do anything about this issue. If it works, we'd still have to test if CEF works with libgcrypt20.

Contributor

MarcelGerber commented Jan 31, 2015

The dependency originates from https://github.com/adobe/brackets-shell/blob/master/installer/linux/debian/control#L8.
Changing it to libgcrypt11 (>= 1.4.5) | libgcrypt20 should work, but I'm not sure if CEF/Chromium already support libgcrypt20.

@Romane-T Could you just test if apt-get install chromium works for you? (Of course in Jessie and without libgcrypt11 installed) If it doesn't work, you can be sure that Brackets currently can't do anything about this issue. If it works, we'd still have to test if CEF works with libgcrypt20.

@Romane-T

This comment has been minimized.

Show comment
Hide comment
@Romane-T

Romane-T Jan 31, 2015

Good morning

On 01/02/15 07:23, Marcel Gerber wrote:

The dependency originates from
https://github.com/adobe/brackets-shell/blob/master/installer/linux/debian/control#L8.
Changing it to |libgcrypt11 (>= 1.4.5) | libgcrypt20| should work, but
I'm not sure if CEF/Chromium already support |libgcrypt20|.

@Romane-T https://github.com/Romane-T Could you just test if
|apt-get install chromium| works for you? (Of course in Jessie and
without |libgcrypt11| installed) If it doesn't work, you can be sure
that Brackets currently can't do anything about this issue. If it
works, we'd still have to test if CEF works with |libgcrypt20|.


Reply to this email directly or view it on GitHub
#10255 (comment).

My current machine(s) are all running Jessie, bar one Windows machine
which is seldom used.

Began by purging libgcrypt11, which uninstalled Brackets as a consequence.

executed aptitude install chromium. The version installed is
chromium_40.0.2214.91-1 and install without errors.

Executed dpkg -i Brackets.Release.1.1.64-bit.deb

Errors reported - missing libgcrypt11. Transcript follows:

root@medion:/home/romane/software/linux/debs/Brackets# dpkg -i
Brackets.Release.1.1.64-bit.deb
Selecting previously unselected package brackets.
(Reading database ... 209202 files and directories currently installed.)
Preparing to unpack Brackets.Release.1.1.64-bit.deb ...
Unpacking brackets (1.1.0-15558) ...
dpkg: dependency problems prevent configuration of brackets:
brackets depends on libgcrypt11 (>= 1.4.5).

dpkg: error processing package brackets (--install):
dependency problems - leaving unconfigured
Processing triggers for hicolor-icon-theme (0.13-1) ...
Processing triggers for menu (2.1.47) ...
Errors were encountered while processing:
brackets

Going by your comment (above), looks like we are stuck at this for a bit
yet.

With greetings

Romane

Romane-T commented Jan 31, 2015

Good morning

On 01/02/15 07:23, Marcel Gerber wrote:

The dependency originates from
https://github.com/adobe/brackets-shell/blob/master/installer/linux/debian/control#L8.
Changing it to |libgcrypt11 (>= 1.4.5) | libgcrypt20| should work, but
I'm not sure if CEF/Chromium already support |libgcrypt20|.

@Romane-T https://github.com/Romane-T Could you just test if
|apt-get install chromium| works for you? (Of course in Jessie and
without |libgcrypt11| installed) If it doesn't work, you can be sure
that Brackets currently can't do anything about this issue. If it
works, we'd still have to test if CEF works with |libgcrypt20|.


Reply to this email directly or view it on GitHub
#10255 (comment).

My current machine(s) are all running Jessie, bar one Windows machine
which is seldom used.

Began by purging libgcrypt11, which uninstalled Brackets as a consequence.

executed aptitude install chromium. The version installed is
chromium_40.0.2214.91-1 and install without errors.

Executed dpkg -i Brackets.Release.1.1.64-bit.deb

Errors reported - missing libgcrypt11. Transcript follows:

root@medion:/home/romane/software/linux/debs/Brackets# dpkg -i
Brackets.Release.1.1.64-bit.deb
Selecting previously unselected package brackets.
(Reading database ... 209202 files and directories currently installed.)
Preparing to unpack Brackets.Release.1.1.64-bit.deb ...
Unpacking brackets (1.1.0-15558) ...
dpkg: dependency problems prevent configuration of brackets:
brackets depends on libgcrypt11 (>= 1.4.5).

dpkg: error processing package brackets (--install):
dependency problems - leaving unconfigured
Processing triggers for hicolor-icon-theme (0.13-1) ...
Processing triggers for menu (2.1.47) ...
Errors were encountered while processing:
brackets

Going by your comment (above), looks like we are stuck at this for a bit
yet.

With greetings

Romane

@sarathms

This comment has been minimized.

Show comment
Hide comment
@sarathms

sarathms Feb 5, 2015

So I tried what @MarcelGerber suggested above. But instead of changing it in the source, I changed it inside the distributed .deb file (Brackets.Release.1.2.64-bit.deb) and packaged it again. Brackets started working normally, so far. Not sure which feature in Brackets can trigger a possible crash.

Here's what I did:

  • Extract the .deb file manually from your file manager. It creates a folder named Brackets.Release.1.2.64-bit (Take a backup of the debfile to avoid overwriting when repackaged).
  • Edit the control file in the extracted package.
$ nano Brackets.Release.1.2.64-bit/DEBIAN/control
  • Look for libgcrypt11 (>= 1.4.5) and change it to libgcrypt20 (>= 1.5), save and exit.
  • Change the ownership of all files and folder to root (This is needed for deb packaging purposes).
$ sudo chown -R root:root Brackets.Release.1.2.64-bit/
  • Create the deb file again using the dpkg-deb command
$ sudo dpkg-deb --build Brackets.Release.1.2.64-bit/
  • Install again
$ sudo dpkg -i Brackets.Release.1.2.64-bit.deb

Is it good to send a PR with this? I know it should go to brackets-shell, are there any guidelines for debian packaging?

sarathms commented Feb 5, 2015

So I tried what @MarcelGerber suggested above. But instead of changing it in the source, I changed it inside the distributed .deb file (Brackets.Release.1.2.64-bit.deb) and packaged it again. Brackets started working normally, so far. Not sure which feature in Brackets can trigger a possible crash.

Here's what I did:

  • Extract the .deb file manually from your file manager. It creates a folder named Brackets.Release.1.2.64-bit (Take a backup of the debfile to avoid overwriting when repackaged).
  • Edit the control file in the extracted package.
$ nano Brackets.Release.1.2.64-bit/DEBIAN/control
  • Look for libgcrypt11 (>= 1.4.5) and change it to libgcrypt20 (>= 1.5), save and exit.
  • Change the ownership of all files and folder to root (This is needed for deb packaging purposes).
$ sudo chown -R root:root Brackets.Release.1.2.64-bit/
  • Create the deb file again using the dpkg-deb command
$ sudo dpkg-deb --build Brackets.Release.1.2.64-bit/
  • Install again
$ sudo dpkg -i Brackets.Release.1.2.64-bit.deb

Is it good to send a PR with this? I know it should go to brackets-shell, are there any guidelines for debian packaging?

@Romane-T

This comment has been minimized.

Show comment
Hide comment
@Romane-T

Romane-T Feb 5, 2015

Good morning

On 05/02/15 17:54, Sarath wrote:

So I tried what @MarcelGerber https://github.com/MarcelGerber
suggested above. But instead of changing it in the source, I changed
it inside the distributed .deb file
(|Brackets.Release.1.2.64-bit.deb|) and packaged it again. Brackets
started working normally, so far. Not sure which feature in Brackets
can trigger a possible crash.

Here's what I did:

  • Extract the .deb file manually from your file manager. It creates
    a folder named |Brackets.Release.1.2.64-bit| (Take a backup of the
    debfile to avoid overwriting when repackaged).
  • Edit the control file in the extracted package.

|$ nano Brackets.Release.1.2.64-bit/DEBIAN/control
|

  • Look for |libgcrypt11 (>= 1.4.5)| and change it to |libgcrypt20
    (>= 1.5)|, save and exit.
  • Change the ownership of all files and folder to root (This is
    needed for deb packaging purposes).

|$ sudo chown -R root:root Brackets.Release.1.2.64-bit/
|

  • Create the deb file again using the |dpkg-deb| command

|$ sudo dpkg-deb --build Brackets.Release.1.2.64-bit/
|

  • Install again

|$ sudo dpkg -i Brackets.Release.1.2.64-bit.deb
|

Is it good to send a PR with this? I know it should go to
brackets-shell, are there any guidelines for debian packaging?


Reply to this email directly or view it on GitHub
#10255 (comment).

My thanks to Sarath. Following much head-banging on the desktop, finally
succeeded in rebuilding the version 1.1 .deb with Sarath's instructions,
and some help from the man command to fill in some spaces. I can confirm
that the .deb installs fine, no error messages, and that removal of
libgcrypt11 went smoothly, leaving Brackets installed.

But....

Though Brackets installs fine without libgcrypt11, it does not run
without libgcrypt11. As soon as installed libgcrypt11 again, ran
perfectly again. Tested by multiple removals and installs of both
Brackets and libgcrypt11, together and separately.

Saranth, when you installed the modified .deb file, did you ensure that
libgcrypt11 was removed from the system? If it is still there, that may
account for it running for you. If you have no trace of libgcrypt11,
then what is different between your system and mine that allows Brackets
to run? Are you running Debian Jessie, or another version or another distro?

With greetings

Romane

Romane-T commented Feb 5, 2015

Good morning

On 05/02/15 17:54, Sarath wrote:

So I tried what @MarcelGerber https://github.com/MarcelGerber
suggested above. But instead of changing it in the source, I changed
it inside the distributed .deb file
(|Brackets.Release.1.2.64-bit.deb|) and packaged it again. Brackets
started working normally, so far. Not sure which feature in Brackets
can trigger a possible crash.

Here's what I did:

  • Extract the .deb file manually from your file manager. It creates
    a folder named |Brackets.Release.1.2.64-bit| (Take a backup of the
    debfile to avoid overwriting when repackaged).
  • Edit the control file in the extracted package.

|$ nano Brackets.Release.1.2.64-bit/DEBIAN/control
|

  • Look for |libgcrypt11 (>= 1.4.5)| and change it to |libgcrypt20
    (>= 1.5)|, save and exit.
  • Change the ownership of all files and folder to root (This is
    needed for deb packaging purposes).

|$ sudo chown -R root:root Brackets.Release.1.2.64-bit/
|

  • Create the deb file again using the |dpkg-deb| command

|$ sudo dpkg-deb --build Brackets.Release.1.2.64-bit/
|

  • Install again

|$ sudo dpkg -i Brackets.Release.1.2.64-bit.deb
|

Is it good to send a PR with this? I know it should go to
brackets-shell, are there any guidelines for debian packaging?


Reply to this email directly or view it on GitHub
#10255 (comment).

My thanks to Sarath. Following much head-banging on the desktop, finally
succeeded in rebuilding the version 1.1 .deb with Sarath's instructions,
and some help from the man command to fill in some spaces. I can confirm
that the .deb installs fine, no error messages, and that removal of
libgcrypt11 went smoothly, leaving Brackets installed.

But....

Though Brackets installs fine without libgcrypt11, it does not run
without libgcrypt11. As soon as installed libgcrypt11 again, ran
perfectly again. Tested by multiple removals and installs of both
Brackets and libgcrypt11, together and separately.

Saranth, when you installed the modified .deb file, did you ensure that
libgcrypt11 was removed from the system? If it is still there, that may
account for it running for you. If you have no trace of libgcrypt11,
then what is different between your system and mine that allows Brackets
to run? Are you running Debian Jessie, or another version or another distro?

With greetings

Romane

@sarathms

This comment has been minimized.

Show comment
Hide comment
@sarathms

sarathms Feb 5, 2015

@Romane-T,

Saranth, when you installed the modified .deb file, did you ensure that libgcrypt11 was removed from the system? If it is still there, that may account for it running for you. If you have no trace of libgcrypt11, then what is different between your system and mine that allows Brackets to run? Are you running Debian Jessie, or another version or another distro?

I'm running Debian Jessie a.k.a testing a.k.a 8.0. Yes, I had no trace of libgcrypt11 on my system. Instead I have libgcrypt20. Currently that is the only version of the package available in jessie. Its not possible for me to install libgcrypt11. Try apt-cache search libgcrypt and tell me if you still see libgcrypt11. However, you may find libgcrypt11-dev which has nothing to do with brackets.

Though Brackets installs fine without libgcrypt11, it does not run without libgcrypt11.

What do you mean? Does it not start? Does it crash?

As soon as installed libgcrypt11 again, ran perfectly again.

How did you install libgcrypt11 again? If you are still able to, that means your package list isn't updated. You can try doing a apt-get clean and then apt-get update and apt-get upgrade if you haven't done it in a few weeks now.

sarathms commented Feb 5, 2015

@Romane-T,

Saranth, when you installed the modified .deb file, did you ensure that libgcrypt11 was removed from the system? If it is still there, that may account for it running for you. If you have no trace of libgcrypt11, then what is different between your system and mine that allows Brackets to run? Are you running Debian Jessie, or another version or another distro?

I'm running Debian Jessie a.k.a testing a.k.a 8.0. Yes, I had no trace of libgcrypt11 on my system. Instead I have libgcrypt20. Currently that is the only version of the package available in jessie. Its not possible for me to install libgcrypt11. Try apt-cache search libgcrypt and tell me if you still see libgcrypt11. However, you may find libgcrypt11-dev which has nothing to do with brackets.

Though Brackets installs fine without libgcrypt11, it does not run without libgcrypt11.

What do you mean? Does it not start? Does it crash?

As soon as installed libgcrypt11 again, ran perfectly again.

How did you install libgcrypt11 again? If you are still able to, that means your package list isn't updated. You can try doing a apt-get clean and then apt-get update and apt-get upgrade if you haven't done it in a few weeks now.

@Romane-T

This comment has been minimized.

Show comment
Hide comment
@Romane-T

Romane-T Feb 5, 2015

Good morning

On 06/02/15 01:21, Sarath wrote:

@Romane-T https://github.com/Romane-T,

Saranth, when you installed the modified .deb file, did you ensure
that libgcrypt11 was removed from the system? If it is still
there, that may account for it running for you. If you have no
trace of libgcrypt11, then what is different between your system
and mine that allows Brackets to run? Are you running Debian
Jessie, or another version or another distro?

I'm running Debian Jessie a.k.a testing a.k.a 8.0. Yes, I had no trace
of |libgcrypt11| on my system. Instead I have |libgcrypt20|. Currently
that is the only version of the package available in jessie. Its not
possible for me to install |libgcrypt11|. Try |apt-cache search
libgcrypt| and tell me if you still see |libgcrypt11|. However, you
may find |libgcrypt11-dev| which has nothing to do with brackets.

Though Brackets installs fine without libgcrypt11, it does not run
without libgcrypt11.
What do you mean? Does it not start? Does it crash?

As soon as installed libgcrypt11 again, ran perfectly again.
How did you install libgcrypt11 again? If you are still able to,
that means your package list isn't updated. You can try doing a
|apt-get clean| and then |apt-get update| and |apt-get upgrade| if
you haven't done it in a few weeks now.


Reply to this email directly or view it on GitHub
#10255 (comment).

@saranth

First, re libcrypt11. My repositories are fine. I update and install
available updates every day. Am not installing libcrypt11 from
repositories, but from last copy of libcrypt11 left on my system when
Jessie went to libcrypt20 - I kept it aside. Same as I must use dpkg to
install Brackets, I use dpkg to install libcrypt11. Without that, would
have been without Brackets for quite some time. Plus, libcrypt11 can be
downloaded separately from repositories for Wheezy, but I never went
down that track. Having Brackets on my system is more important than
having a pristine Jessie.

But none of that is important to the issue at hand, it is a mere
sidetrack, though I thank you for your advice. What is important is that
for you, Brackets runs fine on libcrypt20. For me, it does not start and
i have to have libcrypt11 on board. Crash? No, not that I know of. Does
not start. Start-up indicator, but that stops at the default 30 seconds,
then nothing. There is likewise no trace showing in the System Monitor
during or after the start-up indicator showing. All of that says that
Brackets is recognised but not loading, but beyond that I have no
knowledge, and in this circumstance have no expertise in diagnosing.

Which leaves us with the important question - what is different between
our two systems? If we can work that out, then perhaps we can find a
solution that works for everyone, not just a few. So, can you or anyone
else tell me what I need to look at to try and resolve this system
difference? What sort of things can I try?, hopefully to duplicate the
experience of Saranth.

With greetings

Romane

Romane-T commented Feb 5, 2015

Good morning

On 06/02/15 01:21, Sarath wrote:

@Romane-T https://github.com/Romane-T,

Saranth, when you installed the modified .deb file, did you ensure
that libgcrypt11 was removed from the system? If it is still
there, that may account for it running for you. If you have no
trace of libgcrypt11, then what is different between your system
and mine that allows Brackets to run? Are you running Debian
Jessie, or another version or another distro?

I'm running Debian Jessie a.k.a testing a.k.a 8.0. Yes, I had no trace
of |libgcrypt11| on my system. Instead I have |libgcrypt20|. Currently
that is the only version of the package available in jessie. Its not
possible for me to install |libgcrypt11|. Try |apt-cache search
libgcrypt| and tell me if you still see |libgcrypt11|. However, you
may find |libgcrypt11-dev| which has nothing to do with brackets.

Though Brackets installs fine without libgcrypt11, it does not run
without libgcrypt11.
What do you mean? Does it not start? Does it crash?

As soon as installed libgcrypt11 again, ran perfectly again.
How did you install libgcrypt11 again? If you are still able to,
that means your package list isn't updated. You can try doing a
|apt-get clean| and then |apt-get update| and |apt-get upgrade| if
you haven't done it in a few weeks now.


Reply to this email directly or view it on GitHub
#10255 (comment).

@saranth

First, re libcrypt11. My repositories are fine. I update and install
available updates every day. Am not installing libcrypt11 from
repositories, but from last copy of libcrypt11 left on my system when
Jessie went to libcrypt20 - I kept it aside. Same as I must use dpkg to
install Brackets, I use dpkg to install libcrypt11. Without that, would
have been without Brackets for quite some time. Plus, libcrypt11 can be
downloaded separately from repositories for Wheezy, but I never went
down that track. Having Brackets on my system is more important than
having a pristine Jessie.

But none of that is important to the issue at hand, it is a mere
sidetrack, though I thank you for your advice. What is important is that
for you, Brackets runs fine on libcrypt20. For me, it does not start and
i have to have libcrypt11 on board. Crash? No, not that I know of. Does
not start. Start-up indicator, but that stops at the default 30 seconds,
then nothing. There is likewise no trace showing in the System Monitor
during or after the start-up indicator showing. All of that says that
Brackets is recognised but not loading, but beyond that I have no
knowledge, and in this circumstance have no expertise in diagnosing.

Which leaves us with the important question - what is different between
our two systems? If we can work that out, then perhaps we can find a
solution that works for everyone, not just a few. So, can you or anyone
else tell me what I need to look at to try and resolve this system
difference? What sort of things can I try?, hopefully to duplicate the
experience of Saranth.

With greetings

Romane

@lrebrown

This comment has been minimized.

Show comment
Hide comment
@lrebrown

lrebrown Feb 6, 2015

Which leaves us with the important question - what is different between our two systems?

@romane, sarathms was repacking a preview of Brackets v1.2, while you stated earlier that you are repacking v1.1. There is the problem. You cannot expect v1.1 to just work the same like that.

In v1.1 the Brackets team updated the version of the CEF component Brackets is built upon. The primary reason for doing this was to address some issues with using Brackets in Linux. Unfortunately other issues cropped up in Brackets when using this new version, so while they were able to ship v1.1 for Windows and Mac with the new CEF, v1.1 for Linux retained the previous version. For v1.2 they have been working on resolving those issues to now allow them to provide us with a Linux build built upon this new version of CEF. I expect that CEF has a dependency on libcrypt, with the older version of CEF working with and being built against libcrypt11, and the newer CEF, libcrypt20. If that is so, you cannot just repackage the Linux build of Brackets v1.1 with a libcrypt20 dependency, because the older version of CEF it uses is not necessarily compatible with the new version of libcrypt. This should explain this issues you are experiencing.

Try instead to repackage the Linux preview build of v1.2 with libcrypt20, as done by sarathms.

Hopefully if it is the case that v1.2 works with and requires libcrypt20, the Brackets team will package it with this updated dependency when they release it, otherwise we'll have an issue, requiring us to repackage with correct dependency ourselves, which would obviously not be ideal.

lrebrown commented Feb 6, 2015

Which leaves us with the important question - what is different between our two systems?

@romane, sarathms was repacking a preview of Brackets v1.2, while you stated earlier that you are repacking v1.1. There is the problem. You cannot expect v1.1 to just work the same like that.

In v1.1 the Brackets team updated the version of the CEF component Brackets is built upon. The primary reason for doing this was to address some issues with using Brackets in Linux. Unfortunately other issues cropped up in Brackets when using this new version, so while they were able to ship v1.1 for Windows and Mac with the new CEF, v1.1 for Linux retained the previous version. For v1.2 they have been working on resolving those issues to now allow them to provide us with a Linux build built upon this new version of CEF. I expect that CEF has a dependency on libcrypt, with the older version of CEF working with and being built against libcrypt11, and the newer CEF, libcrypt20. If that is so, you cannot just repackage the Linux build of Brackets v1.1 with a libcrypt20 dependency, because the older version of CEF it uses is not necessarily compatible with the new version of libcrypt. This should explain this issues you are experiencing.

Try instead to repackage the Linux preview build of v1.2 with libcrypt20, as done by sarathms.

Hopefully if it is the case that v1.2 works with and requires libcrypt20, the Brackets team will package it with this updated dependency when they release it, otherwise we'll have an issue, requiring us to repackage with correct dependency ourselves, which would obviously not be ideal.

@Romane-T

This comment has been minimized.

Show comment
Hide comment
@Romane-T

Romane-T Feb 6, 2015

Good morning

On 06/02/15 10:12, lrebrown wrote:

Which leaves us with the important question - what is different
between our two systems?

@romane https://github.com/Romane, sarathms was repacking a preview
of Brackets v1.2, while you stated earlier that you are repacking
v1.1. There is the problem. You cannot expect v1.1 to just work the
same like that.

In v1.1 the Brackets team updated the version of the CEF component
Brackets is built upon. The primary reason for doing this was to
address some issues with using Brackets in Linux. Unfortunately other
issues cropped up in Brackets when using this new version, so while
they were able to ship v1.1 for Windows and Mac with the new CEF, v1.1
for Linux retained the previous version. For v1.2 they have been
working on resolving those issues to now allow them to provide us with
a Linux build built upon this new version of CEF. I expect that CEF
has a dependency on libcrypt, with the older version of CEF working
with and being built against libcrypt11, and the newer CEF,
libcrypt20. If that is so, you cannot just repackage the Linux build
of Brackets v1.1 with a libcrypt20 dependency, because the older
version of CEF it uses is not necessarily compatible with the new
version of libcrypt. This should explain this issues you are experiencing.

Try instead to repackage the Linux preview build of v1.2 with
libcrypt20, as done by sarathms.

Hopefully if it is the case that v1.2 works with and requires
libcrypt20, the Brackets team will package it with this updated
dependency when they release it, otherwise we'll have an issue,
requiring us to repackage with correct dependency ourselves, which
would obviously not be ideal.


Reply to this email directly or view it on GitHub
#10255 (comment).

I sit here now giggling with glee. You have, @Irebrown, hit the nail on
the head. My faulty assumption, for which I paid the penalty.

Results achieved by Sarath now duplicated on my machine.

Just for the record:

Re-downloaded 1.2 from the link given earlier by Prashant on 23 Jan 15.
Rebuilt the .deb as per the directions from Sarath on 5 Feb 15 (didn't
take me three hours this time).
Removed libgcrypt11, which automatically removed Brackets.
Attempted to install the downloaded .deb of Brackets 1.2, to confirm
that would fail - no libgcrypt11. Confirmed.
Removed broken Brackets package.
installed rebuilt package - dpkg -i Brackets.Release.1.2.64-bit.deb - no
errors or warnings
Clicked on icon for Brackets in menu's - worked perfectly; no
hesitation, no stalling, no crashes.
Closed and restarted Brackets a number of times to confirm start-up
resolved. Is clear from the post by Sarath when posting the fix that
have now duplicated what is happening on (her? his?) computer.

With peoples permission, I would like to offer a commendation to those
here for dealing with my sometimes silliness with patience and
perseverance, and allowing my continued participation in the
conversation (i.e. not ignoring me) and providing me with opportunities
to contribute positively. I am no developer by any standard, but what I
have learned from the people here has been useful and gratifying. Thank you.

Now, if there is any further testing I can do in this or other areas, I
would be most happy to impose again on your patience and generosity
(Romane grinning).

With greetings

Romane

Romane-T commented Feb 6, 2015

Good morning

On 06/02/15 10:12, lrebrown wrote:

Which leaves us with the important question - what is different
between our two systems?

@romane https://github.com/Romane, sarathms was repacking a preview
of Brackets v1.2, while you stated earlier that you are repacking
v1.1. There is the problem. You cannot expect v1.1 to just work the
same like that.

In v1.1 the Brackets team updated the version of the CEF component
Brackets is built upon. The primary reason for doing this was to
address some issues with using Brackets in Linux. Unfortunately other
issues cropped up in Brackets when using this new version, so while
they were able to ship v1.1 for Windows and Mac with the new CEF, v1.1
for Linux retained the previous version. For v1.2 they have been
working on resolving those issues to now allow them to provide us with
a Linux build built upon this new version of CEF. I expect that CEF
has a dependency on libcrypt, with the older version of CEF working
with and being built against libcrypt11, and the newer CEF,
libcrypt20. If that is so, you cannot just repackage the Linux build
of Brackets v1.1 with a libcrypt20 dependency, because the older
version of CEF it uses is not necessarily compatible with the new
version of libcrypt. This should explain this issues you are experiencing.

Try instead to repackage the Linux preview build of v1.2 with
libcrypt20, as done by sarathms.

Hopefully if it is the case that v1.2 works with and requires
libcrypt20, the Brackets team will package it with this updated
dependency when they release it, otherwise we'll have an issue,
requiring us to repackage with correct dependency ourselves, which
would obviously not be ideal.


Reply to this email directly or view it on GitHub
#10255 (comment).

I sit here now giggling with glee. You have, @Irebrown, hit the nail on
the head. My faulty assumption, for which I paid the penalty.

Results achieved by Sarath now duplicated on my machine.

Just for the record:

Re-downloaded 1.2 from the link given earlier by Prashant on 23 Jan 15.
Rebuilt the .deb as per the directions from Sarath on 5 Feb 15 (didn't
take me three hours this time).
Removed libgcrypt11, which automatically removed Brackets.
Attempted to install the downloaded .deb of Brackets 1.2, to confirm
that would fail - no libgcrypt11. Confirmed.
Removed broken Brackets package.
installed rebuilt package - dpkg -i Brackets.Release.1.2.64-bit.deb - no
errors or warnings
Clicked on icon for Brackets in menu's - worked perfectly; no
hesitation, no stalling, no crashes.
Closed and restarted Brackets a number of times to confirm start-up
resolved. Is clear from the post by Sarath when posting the fix that
have now duplicated what is happening on (her? his?) computer.

With peoples permission, I would like to offer a commendation to those
here for dealing with my sometimes silliness with patience and
perseverance, and allowing my continued participation in the
conversation (i.e. not ignoring me) and providing me with opportunities
to contribute positively. I am no developer by any standard, but what I
have learned from the people here has been useful and gratifying. Thank you.

Now, if there is any further testing I can do in this or other areas, I
would be most happy to impose again on your patience and generosity
(Romane grinning).

With greetings

Romane

@redmunds

This comment has been minimized.

Show comment
Hide comment
@redmunds

redmunds Feb 6, 2015

Contributor

@Romane-T

Now, if there is any further testing I can do in this or other areas, I would be most happy to impose again on your patience and generosity (Romane grinning).

We will be posting Release 1.2 beta builds soon, so please help us test those. It will be announced on the brackets-dev forum.

Contributor

redmunds commented Feb 6, 2015

@Romane-T

Now, if there is any further testing I can do in this or other areas, I would be most happy to impose again on your patience and generosity (Romane grinning).

We will be posting Release 1.2 beta builds soon, so please help us test those. It will be announced on the brackets-dev forum.

@jasonsanjose

This comment has been minimized.

Show comment
Hide comment
@jasonsanjose

jasonsanjose Feb 9, 2015

Member

@MarcelGerber, this worked great:

Changing it to libgcrypt11 (>= 1.4.5) | libgcrypt20 should work, but I'm not sure if CEF/Chromium already support libgcrypt20.

Thanks for the tip! I created a PR adobe/brackets-shell#501.

Member

jasonsanjose commented Feb 9, 2015

@MarcelGerber, this worked great:

Changing it to libgcrypt11 (>= 1.4.5) | libgcrypt20 should work, but I'm not sure if CEF/Chromium already support libgcrypt20.

Thanks for the tip! I created a PR adobe/brackets-shell#501.

@jasonsanjose

This comment has been minimized.

Show comment
Hide comment
@jasonsanjose

jasonsanjose Feb 10, 2015

Member

@Romane-T @MarcelGerber I posted a new build here https://github.com/adobe/brackets/releases/download/linux-cef-2171/Brackets.Release.1.2.64-bit.deb that contains fix for this bug (see PR adobe/brackets-shell#501) as well as including the CEF 2171 (see adobe/brackets-shell#499).

I was able to install this on a clean (mostly) install of debian 8. I had installed the build-essential package early on. Upon install of Brackets, I was prompted to install libcurl3 which installed without issues.

If you get some time to try this new build, please let us know how it goes.

Member

jasonsanjose commented Feb 10, 2015

@Romane-T @MarcelGerber I posted a new build here https://github.com/adobe/brackets/releases/download/linux-cef-2171/Brackets.Release.1.2.64-bit.deb that contains fix for this bug (see PR adobe/brackets-shell#501) as well as including the CEF 2171 (see adobe/brackets-shell#499).

I was able to install this on a clean (mostly) install of debian 8. I had installed the build-essential package early on. Upon install of Brackets, I was prompted to install libcurl3 which installed without issues.

If you get some time to try this new build, please let us know how it goes.

@lrebrown

This comment has been minimized.

Show comment
Hide comment
@lrebrown

lrebrown Feb 10, 2015

@jasonsanjose

I posted a new build...

Played with it briefly in a Debian sid VM. It installed without issue (this VM has both libgcrypt20 and libgcrypt11 installed, the latter is still available and used by some things in sid). The window overlap issue is no more with the new CEF build - fantastic! Closing brackets both via the 'x' and via file > quit works. The only issue I've noticed is that the window doesn't remember the position or size I expand it to upon reopening - rather irritating.

I'm using gnome and I'm running this VM in virtualbox.

Oh, having said that, I just tried to close it via the 'x' (to see if it remembers position or not) and I'm left with an empty window which won't close :/ And now it's doing that every time. I'll mention it over in #499

lrebrown commented Feb 10, 2015

@jasonsanjose

I posted a new build...

Played with it briefly in a Debian sid VM. It installed without issue (this VM has both libgcrypt20 and libgcrypt11 installed, the latter is still available and used by some things in sid). The window overlap issue is no more with the new CEF build - fantastic! Closing brackets both via the 'x' and via file > quit works. The only issue I've noticed is that the window doesn't remember the position or size I expand it to upon reopening - rather irritating.

I'm using gnome and I'm running this VM in virtualbox.

Oh, having said that, I just tried to close it via the 'x' (to see if it remembers position or not) and I'm left with an empty window which won't close :/ And now it's doing that every time. I'll mention it over in #499

@Romane-T

This comment has been minimized.

Show comment
Hide comment
@Romane-T

Romane-T Feb 11, 2015

On 11/02/15 04:59, Jason San Jose wrote:

@Romane-T https://github.com/Romane-T @MarcelGerber
https://github.com/MarcelGerber I posted a new build here
https://github.com/adobe/brackets/releases/download/linux-cef-2171/Brackets.Release.1.2.64-bit.deb
that contains fix for this bug (see PR adobe/brackets-shell#501
adobe/brackets-shell#501) as well as
including the CEF 2171 (see adobe/brackets-shell#499
adobe/brackets-shell#499).

I was able to install this on a clean (mostly) install of debian 8. I
had installed the |build-essential| package early on. Upon install of
Brackets, I was prompted to install `libcurl3 which installed without
issues.

If you get some time to try this new build, please let us know how it
goes.


Reply to this email directly or view it on GitHub
#10255 (comment).

Good morning

System is Debian Jessie running KDE. This machine has been running
'testing' since Lenny was in 'testing', though full re-install at one
stage when I really messed something up while 'Wheezy' was in testing. I
did once contemplate (re)learning C, and installed the relevant
libraries, but do not think that these would have any effect.

For various purposes, had downgraded to Brackets version 1.0. I need the
functionality in the extension 'right-click-extended', which every
version of Brackets since version 1.0 has prevented from functioning -
has been reported appropriately for the extension.

Purged Brackets and libgcrypt11
libcurl3 is already installed on machine.
installed this build of Brackets. No errors, no warnings.
Opened Brackets:
1st test - close via 'x'. For the first time ever that have seen
since using Brackets, Brackets closed with only a single click. Yaaaay -
good step forward. Tested about five times, same each time.
2nd test - close via 'File->Quit'. as with closing via 'x',
immediate close. Again, tested about five times.

There was an update for one of the extensions available. Updated without
any problems - no warnings, no errors.

I had Chromium installed from a previous test for Brackets. Removed
Chromium. No change to above results.

Extension 'right-click-extended' still fails to work. Something changed,
obviously, in the code-base since version 1.0 which directly affects
this extension.

@Irebrown - regarding not remembering position, I have never known
Brackets to remember position, and must resize at every opening. Only a
minuscule irritation for self not affecting general satisfaction with
Brackets, but still, would be nice :)

Will leave this build installed to test functionality in my usage needs.
Should issues be reported to a certain thread, or simply reported in the
same manner as the stable builds?

I have an old and slow 32 bit machine running Jessie with lxqt for the
desktop environment, all freshly installed about two months ago. My out
and about machine. Looking forward to a 32 bit build to test on this
machine when such becomes available.

With greetings

Romane

Romane-T commented Feb 11, 2015

On 11/02/15 04:59, Jason San Jose wrote:

@Romane-T https://github.com/Romane-T @MarcelGerber
https://github.com/MarcelGerber I posted a new build here
https://github.com/adobe/brackets/releases/download/linux-cef-2171/Brackets.Release.1.2.64-bit.deb
that contains fix for this bug (see PR adobe/brackets-shell#501
adobe/brackets-shell#501) as well as
including the CEF 2171 (see adobe/brackets-shell#499
adobe/brackets-shell#499).

I was able to install this on a clean (mostly) install of debian 8. I
had installed the |build-essential| package early on. Upon install of
Brackets, I was prompted to install `libcurl3 which installed without
issues.

If you get some time to try this new build, please let us know how it
goes.


Reply to this email directly or view it on GitHub
#10255 (comment).

Good morning

System is Debian Jessie running KDE. This machine has been running
'testing' since Lenny was in 'testing', though full re-install at one
stage when I really messed something up while 'Wheezy' was in testing. I
did once contemplate (re)learning C, and installed the relevant
libraries, but do not think that these would have any effect.

For various purposes, had downgraded to Brackets version 1.0. I need the
functionality in the extension 'right-click-extended', which every
version of Brackets since version 1.0 has prevented from functioning -
has been reported appropriately for the extension.

Purged Brackets and libgcrypt11
libcurl3 is already installed on machine.
installed this build of Brackets. No errors, no warnings.
Opened Brackets:
1st test - close via 'x'. For the first time ever that have seen
since using Brackets, Brackets closed with only a single click. Yaaaay -
good step forward. Tested about five times, same each time.
2nd test - close via 'File->Quit'. as with closing via 'x',
immediate close. Again, tested about five times.

There was an update for one of the extensions available. Updated without
any problems - no warnings, no errors.

I had Chromium installed from a previous test for Brackets. Removed
Chromium. No change to above results.

Extension 'right-click-extended' still fails to work. Something changed,
obviously, in the code-base since version 1.0 which directly affects
this extension.

@Irebrown - regarding not remembering position, I have never known
Brackets to remember position, and must resize at every opening. Only a
minuscule irritation for self not affecting general satisfaction with
Brackets, but still, would be nice :)

Will leave this build installed to test functionality in my usage needs.
Should issues be reported to a certain thread, or simply reported in the
same manner as the stable builds?

I have an old and slow 32 bit machine running Jessie with lxqt for the
desktop environment, all freshly installed about two months ago. My out
and about machine. Looking forward to a 32 bit build to test on this
machine when such becomes available.

With greetings

Romane

@jasonsanjose

This comment has been minimized.

Show comment
Hide comment
@jasonsanjose

jasonsanjose Feb 13, 2015

Member

@Romane-T Here's a 32-bit installer https://github.com/adobe/brackets/releases/download/linux-cef-2171/Brackets.Release.1.2.32-bit.deb.

I tested this on a clean Debian 7 install. Looks like libcurl3 is the only missing package again.

@nethip On my 32-bit VM I'm running into the crash on quit more frequently.

Member

jasonsanjose commented Feb 13, 2015

@Romane-T Here's a 32-bit installer https://github.com/adobe/brackets/releases/download/linux-cef-2171/Brackets.Release.1.2.32-bit.deb.

I tested this on a clean Debian 7 install. Looks like libcurl3 is the only missing package again.

@nethip On my 32-bit VM I'm running into the crash on quit more frequently.

@Romane-T

This comment has been minimized.

Show comment
Hide comment
@Romane-T

Romane-T Feb 14, 2015

Good morning

On 14/02/15 09:17, Jason San Jose wrote:

@Romane-T https://github.com/Romane-T Here's a 32-bit installer
https://github.com/adobe/brackets/releases/download/linux-cef-2171/Brackets.Release.1.2.32-bit.deb.

I tested this on a clean Debian 7 install. Looks like |libcurl3| is
the only missing package again.

@nethip https://github.com/nethip On my 32-bit VM I'm running into
the crash on quit more frequently.


Reply to this email directly or view it on GitHub
#10255 (comment).

Became excited to see this. Many many thanks.

System is fully up-to-date Debian Jessie on a Samsung N120, with lxqt
version 9.0-1 as the desktop environment. This was a completely fresh
install at the time lxqt was in version 8 just a few months ago, and has
been put together considering the age and speed of the machine. libcurl3
is already installed in relation to other packages (dunno which ones,
it's just there).

Before installing, purged both the previous version of Brackets, and
also libgcrypt11.

First attempt at install (dpkg -i Brackets.Release.1.2.32-bit.deb)
failed - missing libgcrypt11. As per comment from @sarath on 5 February,
re-packaged deb. This machine is so slow, that the build itself took
about 10 minutes to complete :) :)

Second attempt at install successful - no errors, no warnings.

At start, Brackets presents a window almost instantly (for this computer

  • about three or so seconds), but the remainder slow due to the old
    hardware.

Tested closing, both by 'File->Quit' and by the 'x', multiple times. No
crashes at any attempt. Either way, Brackets closed quickly and cleanly.

There were 6 updates to extensions available (binawhile). Updates
installed and updated with no issues - no errors, no warnings.

Tomorrow will use this version of Brackets on the Samsung to do all my
HTML, to give it a good run (today is .pdf day). There is an issue with
the keyboard which have still to report for the 64 bit version
downloaded earlier via this thread (will do today) so will be
interesting to see if translates into this 32 bit version.

@jason - just an aside, and hopefully not trying to teach grandma to
suck eggs - thinking that the crash is to do with the VM rather than
Brackets, as there are no crashes on the packages running on my systems
(no VM), and @sarath noted in his contribution on 5 February that after
his repackaging, Brackets ran normally (but keywords are 'so far'). Have
a memory of mention of crashing in a VM before.

With greetings

Romane

Romane-T commented Feb 14, 2015

Good morning

On 14/02/15 09:17, Jason San Jose wrote:

@Romane-T https://github.com/Romane-T Here's a 32-bit installer
https://github.com/adobe/brackets/releases/download/linux-cef-2171/Brackets.Release.1.2.32-bit.deb.

I tested this on a clean Debian 7 install. Looks like |libcurl3| is
the only missing package again.

@nethip https://github.com/nethip On my 32-bit VM I'm running into
the crash on quit more frequently.


Reply to this email directly or view it on GitHub
#10255 (comment).

Became excited to see this. Many many thanks.

System is fully up-to-date Debian Jessie on a Samsung N120, with lxqt
version 9.0-1 as the desktop environment. This was a completely fresh
install at the time lxqt was in version 8 just a few months ago, and has
been put together considering the age and speed of the machine. libcurl3
is already installed in relation to other packages (dunno which ones,
it's just there).

Before installing, purged both the previous version of Brackets, and
also libgcrypt11.

First attempt at install (dpkg -i Brackets.Release.1.2.32-bit.deb)
failed - missing libgcrypt11. As per comment from @sarath on 5 February,
re-packaged deb. This machine is so slow, that the build itself took
about 10 minutes to complete :) :)

Second attempt at install successful - no errors, no warnings.

At start, Brackets presents a window almost instantly (for this computer

  • about three or so seconds), but the remainder slow due to the old
    hardware.

Tested closing, both by 'File->Quit' and by the 'x', multiple times. No
crashes at any attempt. Either way, Brackets closed quickly and cleanly.

There were 6 updates to extensions available (binawhile). Updates
installed and updated with no issues - no errors, no warnings.

Tomorrow will use this version of Brackets on the Samsung to do all my
HTML, to give it a good run (today is .pdf day). There is an issue with
the keyboard which have still to report for the 64 bit version
downloaded earlier via this thread (will do today) so will be
interesting to see if translates into this 32 bit version.

@jason - just an aside, and hopefully not trying to teach grandma to
suck eggs - thinking that the crash is to do with the VM rather than
Brackets, as there are no crashes on the packages running on my systems
(no VM), and @sarath noted in his contribution on 5 February that after
his repackaging, Brackets ran normally (but keywords are 'so far'). Have
a memory of mention of crashing in a VM before.

With greetings

Romane

@lrebrown

This comment has been minimized.

Show comment
Hide comment
@lrebrown

lrebrown Feb 14, 2015

@Romane-T, how many CPU cores do your systems have? All crashes so far I believe have been only happening in VMs with a single cpu core, and not with VMs with multiple cores (not tested a multi core VM myself). I do not know if anyone has yet tested it directly on a machine with only one CPU core. Assuming it's VM related is jumping the gun here. :)

lrebrown commented Feb 14, 2015

@Romane-T, how many CPU cores do your systems have? All crashes so far I believe have been only happening in VMs with a single cpu core, and not with VMs with multiple cores (not tested a multi core VM myself). I do not know if anyone has yet tested it directly on a machine with only one CPU core. Assuming it's VM related is jumping the gun here. :)

@Romane-T

This comment has been minimized.

Show comment
Hide comment
@Romane-T

Romane-T Feb 14, 2015

Good morning

On 14/02/15 13:33, lrebrown wrote:

@Romane-T https://github.com/Romane-T, how many CPU cores do your
systems have? All crashes so far I believe have been only happening in
VMs with a single cpu core, and not with VMs with multiple cores (not
tested a multi core VM myself). I do not know if anyone has yet tested
it directly on a machine with only one CPU core. Assuming it's VM
related is jumping the gun here. :)


Reply to this email directly or view it on GitHub
#10255 (comment).

Why I said about teaching grandma to suck eggs :) - that should tell
people not to take too much notice of that paragraph.

My machine is a Medion PC with four cores.

The Samsung has two cores.

Was hoping one of my other machines (quite old hardware) might be single
core, but both two core. So puts paid to that plan for testing.

Is it still possible to get single-core machines? Will see if can find
one that can test on.

With greetings

Romane

Romane-T commented Feb 14, 2015

Good morning

On 14/02/15 13:33, lrebrown wrote:

@Romane-T https://github.com/Romane-T, how many CPU cores do your
systems have? All crashes so far I believe have been only happening in
VMs with a single cpu core, and not with VMs with multiple cores (not
tested a multi core VM myself). I do not know if anyone has yet tested
it directly on a machine with only one CPU core. Assuming it's VM
related is jumping the gun here. :)


Reply to this email directly or view it on GitHub
#10255 (comment).

Why I said about teaching grandma to suck eggs :) - that should tell
people not to take too much notice of that paragraph.

My machine is a Medion PC with four cores.

The Samsung has two cores.

Was hoping one of my other machines (quite old hardware) might be single
core, but both two core. So puts paid to that plan for testing.

Is it still possible to get single-core machines? Will see if can find
one that can test on.

With greetings

Romane

@MarcelGerber

This comment has been minimized.

Show comment
Hide comment
@MarcelGerber

MarcelGerber Feb 14, 2015

Contributor

@Romane-T It's proably easier to test in a multi-core VM than using single-core hardware (even though that'd be helpful as well to confirm the suspicion).

Contributor

MarcelGerber commented Feb 14, 2015

@Romane-T It's proably easier to test in a multi-core VM than using single-core hardware (even though that'd be helpful as well to confirm the suspicion).

@Romane-T

This comment has been minimized.

Show comment
Hide comment
@Romane-T

Romane-T Feb 14, 2015

Good morning

On 14/02/15 09:17, Jason San Jose wrote:

@Romane-T https://github.com/Romane-T Here's a 32-bit installer
https://github.com/adobe/brackets/releases/download/linux-cef-2171/Brackets.Release.1.2.32-bit.deb.

I tested this on a clean Debian 7 install. Looks like |libcurl3| is
the only missing package again.

@nethip https://github.com/nethip On my 32-bit VM I'm running into
the crash on quit more frequently.


Reply to this email directly or view it on GitHub
#10255 (comment).

On my Samsung 32 bit machine, the keyboard fails completely - unable to
type anything or move curser with keys. Mouse works, however. Reloaded
without extensions, still the same. Will report via the usual
bug-reporting channel.

With greetings

Romane

Romane-T commented Feb 14, 2015

Good morning

On 14/02/15 09:17, Jason San Jose wrote:

@Romane-T https://github.com/Romane-T Here's a 32-bit installer
https://github.com/adobe/brackets/releases/download/linux-cef-2171/Brackets.Release.1.2.32-bit.deb.

I tested this on a clean Debian 7 install. Looks like |libcurl3| is
the only missing package again.

@nethip https://github.com/nethip On my 32-bit VM I'm running into
the crash on quit more frequently.


Reply to this email directly or view it on GitHub
#10255 (comment).

On my Samsung 32 bit machine, the keyboard fails completely - unable to
type anything or move curser with keys. Mouse works, however. Reloaded
without extensions, still the same. Will report via the usual
bug-reporting channel.

With greetings

Romane

@jasonsanjose

This comment has been minimized.

Show comment
Hide comment
@jasonsanjose

jasonsanjose Feb 17, 2015

Member

First attempt at install (dpkg -i Brackets.Release.1.2.32-bit.deb)
failed - missing libgcrypt11. As per comment from @sarath on 5 February,
re-packaged deb. This machine is so slow, that the build itself took
about 10 minutes to complete :) :)

Oops. Thanks, @Romane-T. I built the 32-bit build on a slightly different branch than the 64-bit one. It doesn't have the fix for libgcrypt11.

It looks like I missed the train for the 1.2 release. Hopefully this will all be settled for 1.3.

Member

jasonsanjose commented Feb 17, 2015

First attempt at install (dpkg -i Brackets.Release.1.2.32-bit.deb)
failed - missing libgcrypt11. As per comment from @sarath on 5 February,
re-packaged deb. This machine is so slow, that the build itself took
about 10 minutes to complete :) :)

Oops. Thanks, @Romane-T. I built the 32-bit build on a slightly different branch than the 64-bit one. It doesn't have the fix for libgcrypt11.

It looks like I missed the train for the 1.2 release. Hopefully this will all be settled for 1.3.

@a-moses

This comment has been minimized.

Show comment
Hide comment
@a-moses

a-moses Feb 21, 2015

Hello @jasonsanjose @Romane-T @MarcelGerber

look on github's Atom simple solution for this :

atom/atom#5605

just change file.deb /DEBIAN/control from:
' libgcrypt11 (>= 1.4.5) ' TO : ' libgcrypt11 (>= 1.4.5) | libgcrypt20 '

*libgcrypt20 come with backward compatibility to libgcrypt11

a-moses commented Feb 21, 2015

Hello @jasonsanjose @Romane-T @MarcelGerber

look on github's Atom simple solution for this :

atom/atom#5605

just change file.deb /DEBIAN/control from:
' libgcrypt11 (>= 1.4.5) ' TO : ' libgcrypt11 (>= 1.4.5) | libgcrypt20 '

*libgcrypt20 come with backward compatibility to libgcrypt11

@MarcelGerber

This comment has been minimized.

Show comment
Hide comment
@MarcelGerber

MarcelGerber Feb 22, 2015

Contributor

@a-moses Yeah, that's what we have in mind and what's already in PR adobe/brackets-shell#501.

Contributor

MarcelGerber commented Feb 22, 2015

@a-moses Yeah, that's what we have in mind and what's already in PR adobe/brackets-shell#501.

@ldez ldez referenced this issue Jun 11, 2016

Closed

libgcrypt11 #12503

@ldez

This comment has been minimized.

Show comment
Hide comment
@ldez

ldez Jun 11, 2016

@jasonsanjose @abose @nethip Can we expect a properly fix?
The issue with libgcrypt11 is critical on Debian/Ubuntu.

cat

ldez commented Jun 11, 2016

@jasonsanjose @abose @nethip Can we expect a properly fix?
The issue with libgcrypt11 is critical on Debian/Ubuntu.

cat

@piesha

This comment has been minimized.

Show comment
Hide comment
@piesha

piesha Jun 11, 2016

+1 from someone negatively impacted by this issue.

piesha commented Jun 11, 2016

+1 from someone negatively impacted by this issue.

@Romane-T

This comment has been minimized.

Show comment
Hide comment
@Romane-T

Romane-T Jun 11, 2016

+1 from another impacted

On 12/06/16 01:29, piesha wrote:

+1 from someone negatively impacted by this issue.


You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#10255 (comment),
or mute the thread
https://github.com/notifications/unsubscribe/AIf16I5LqwAu-n75EkKvjX68nI-N1UKUks5qKtQ-gaJpZM4DK7kj.

Romane-T commented Jun 11, 2016

+1 from another impacted

On 12/06/16 01:29, piesha wrote:

+1 from someone negatively impacted by this issue.


You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#10255 (comment),
or mute the thread
https://github.com/notifications/unsubscribe/AIf16I5LqwAu-n75EkKvjX68nI-N1UKUks5qKtQ-gaJpZM4DK7kj.

@nethip

This comment has been minimized.

Show comment
Hide comment
@nethip

nethip Jun 14, 2016

Contributor

@ldez Unfortunately we don't have adequate bandwidth to look at shell side of things. We were hoping to get some help from the community but we couldn't get any :(.

Contributor

nethip commented Jun 14, 2016

@ldez Unfortunately we don't have adequate bandwidth to look at shell side of things. We were hoping to get some help from the community but we couldn't get any :(.

@ficristo

This comment has been minimized.

Show comment
Hide comment
@ficristo

ficristo Jun 14, 2016

Collaborator

@nethip I'm (slowing) looking at updating the shell to match the cefclient example in the hope to help with this.
I need someone to review my PRs...

Collaborator

ficristo commented Jun 14, 2016

@nethip I'm (slowing) looking at updating the shell to match the cefclient example in the hope to help with this.
I need someone to review my PRs...

@ficristo

This comment has been minimized.

Show comment
Hide comment
@ficristo

ficristo Jun 14, 2016

Collaborator

I don't think is fair to say the community isn't helping: there are already some PR on the shell.
(They are not specific of this issue but still)
adobe/brackets-shell#351
adobe/brackets-shell#425
adobe/brackets-shell#511
adobe/brackets-shell#518
If you look at the first PR was opened in 10 Oct 2013, IMO is that is blocking contributors...

Collaborator

ficristo commented Jun 14, 2016

I don't think is fair to say the community isn't helping: there are already some PR on the shell.
(They are not specific of this issue but still)
adobe/brackets-shell#351
adobe/brackets-shell#425
adobe/brackets-shell#511
adobe/brackets-shell#518
If you look at the first PR was opened in 10 Oct 2013, IMO is that is blocking contributors...

@ldez

This comment has been minimized.

Show comment
Hide comment
@ldez

ldez Jun 14, 2016

@nethip The PR to fix the problem is here (I hope): adobe/brackets-shell#501

Before this PR, @brbsix have made another PR adobe/brackets-shell#541

ldez commented Jun 14, 2016

@nethip The PR to fix the problem is here (I hope): adobe/brackets-shell#501

Before this PR, @brbsix have made another PR adobe/brackets-shell#541

@nethip

This comment has been minimized.

Show comment
Hide comment
@nethip

nethip Jun 14, 2016

Contributor

@ficristo I was talking particularly about this issue itself. We are really appreciative of all the work the community is putting in to make this a great product. I respect that 👍 .

About your PRs, sorry that we are not able to have a look at your PRs. I can understand the frustration. But we are really squeezed between the upcoming releases of Dreamweaver Beta and Brackets. We are doing our best to be able to review all pending PRs(we are infact putting in extra efforts). Your PRs are my to-review list. I will find some time to review your PRs. Really appreciate all your efforts.

@ldez We were really hopeful about adobe/brackets-shell#541 but it got turned down because of the legal issues. However adobe/brackets-shell#501 looks promising. This is not tested yet. Will you help us in validating this fix?

Contributor

nethip commented Jun 14, 2016

@ficristo I was talking particularly about this issue itself. We are really appreciative of all the work the community is putting in to make this a great product. I respect that 👍 .

About your PRs, sorry that we are not able to have a look at your PRs. I can understand the frustration. But we are really squeezed between the upcoming releases of Dreamweaver Beta and Brackets. We are doing our best to be able to review all pending PRs(we are infact putting in extra efforts). Your PRs are my to-review list. I will find some time to review your PRs. Really appreciate all your efforts.

@ldez We were really hopeful about adobe/brackets-shell#541 but it got turned down because of the legal issues. However adobe/brackets-shell#501 looks promising. This is not tested yet. Will you help us in validating this fix?

@nethip

This comment has been minimized.

Show comment
Hide comment
@nethip

nethip Jun 14, 2016

Contributor

Please refer to this comment by @brbsix . Seems like we are out of luck again.

Contributor

nethip commented Jun 14, 2016

Please refer to this comment by @brbsix . Seems like we are out of luck again.

@nethip

This comment has been minimized.

Show comment
Hide comment
@nethip

nethip Jun 21, 2016

Contributor

@ficristo I am done reviewing your PRs that you had raised in the brackets-shell repo. Please address the code review comments.

Contributor

nethip commented Jun 21, 2016

@ficristo I am done reviewing your PRs that you had raised in the brackets-shell repo. Please address the code review comments.

@ficristo

This comment has been minimized.

Show comment
Hide comment
@ficristo

ficristo Jun 24, 2016

Collaborator

@nethip Thank you for the reviews!

Collaborator

ficristo commented Jun 24, 2016

@nethip Thank you for the reviews!

@ficristo ficristo removed this from the Release 1.6 milestone Aug 3, 2016

@ficristo

This comment has been minimized.

Show comment
Hide comment
@ficristo

ficristo Aug 3, 2016

Collaborator

For whoever wants to help, #12640 is related.

Collaborator

ficristo commented Aug 3, 2016

For whoever wants to help, #12640 is related.

@TimHandy

This comment has been minimized.

Show comment
Hide comment
@TimHandy

TimHandy Aug 17, 2016

+1 from another impacted. Linux Mint 18.

TimHandy commented Aug 17, 2016

+1 from another impacted. Linux Mint 18.

@rodya-mirov

This comment has been minimized.

Show comment
Hide comment
@rodya-mirov

rodya-mirov Aug 31, 2016

Can't install either (Ubuntu). This issue is 2 years old!

rodya-mirov commented Aug 31, 2016

Can't install either (Ubuntu). This issue is 2 years old!

@ficristo

This comment has been minimized.

Show comment
Hide comment
@ficristo

ficristo Aug 31, 2016

Collaborator

Given the current situation on Linux, and my doubts that anything will change anytime soon, I would like to suggest to use brackets-electron.
Basically it's Brackets but with Electron as the underline shell. I think it's worth a try.
Here a release: https://github.com/zaggino/brackets-electron/releases

Last year, electron was bring up as an alternative of our shell. @zaggino and some other put together a proof of concept, but the lack of a native dark theme was a blocker to continue the integration.
Lately @zaggino has put some effort to make brackets-electron more stable.

If you have more questions on this I suggest to ask them on Slack in the brackets-electron channel or on
brackets-electron issues or open a new issue here to discuss only this.

A warn: AFAIK there isn't any plan to switch to it.

We know the problem but there aren't many users on Linux to justify an effort here. Or at least, this what I hear everytime about Linux situation and personally I think is really bad. I would like to help more but I can't do much 😭

I lock this issue: more comments here will not increase the priority but only add noise.

Collaborator

ficristo commented Aug 31, 2016

Given the current situation on Linux, and my doubts that anything will change anytime soon, I would like to suggest to use brackets-electron.
Basically it's Brackets but with Electron as the underline shell. I think it's worth a try.
Here a release: https://github.com/zaggino/brackets-electron/releases

Last year, electron was bring up as an alternative of our shell. @zaggino and some other put together a proof of concept, but the lack of a native dark theme was a blocker to continue the integration.
Lately @zaggino has put some effort to make brackets-electron more stable.

If you have more questions on this I suggest to ask them on Slack in the brackets-electron channel or on
brackets-electron issues or open a new issue here to discuss only this.

A warn: AFAIK there isn't any plan to switch to it.

We know the problem but there aren't many users on Linux to justify an effort here. Or at least, this what I hear everytime about Linux situation and personally I think is really bad. I would like to help more but I can't do much 😭

I lock this issue: more comments here will not increase the priority but only add noise.

@adobe adobe locked and limited conversation to collaborators Aug 31, 2016

@zaggino zaggino referenced this issue Nov 24, 2016

Closed

libgcrypt11 #12941

@saurabh95

This comment has been minimized.

Show comment
Hide comment
@saurabh95
Collaborator

saurabh95 commented Aug 23, 2017

Fixed By: adobe/brackets-shell#619

@adobe adobe unlocked this conversation Sep 26, 2017

@ficristo ficristo closed this Sep 26, 2017

@noxxex

This comment has been minimized.

Show comment
Hide comment
@noxxex

noxxex Feb 5, 2018

try apt --fix broken install

noxxex commented Feb 5, 2018

try apt --fix broken install

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment