-
Notifications
You must be signed in to change notification settings - Fork 7.6k
Brackets can't run on Debian 7 (Wheezy) #4816
Comments
This bug is also happend for me on Debian 7 64 bit. |
Try reinstalling libc6 on your system and see what happens. Also, please be sure you have the dev libraries also installed. If that doesn't work, just for kicks and giggles, try:
And please post the output of any errors thrown by Brackets afterwards? Of course, if the above doesn't work, delete the symlink (after letting me know what the output is). :) The libudev problem doesn't seem to pertain to this. |
Duplicate of #4720 |
Hi @DaBungalow for your suggestion. libc-2.17.so is only available in Debian Jessie and Sid, we are using Debian Wheezy. In Debian Wheezy libc6 package provides glibc 2.13 while Brackets requires 2.14. I guess this is the problem. I don't think this issue is duplicated with #4720, Ubuntu Raring have already had glibc 2.17 in their repository. Softwares in Ubuntu are newer than softwares in Debian. I will try Brackets on Debian Jessie with glib 2.17 to see how it goes. |
Ok, I can confirm that Brackets can run on Debian Jessie with no problem. This issue only exists in Debian Wheezy where the libc is "out-of-date". |
We get this dependency from Chromium and it appears they have the same issue https://code.google.com/p/chromium/issues/detail?id=222038 and they've marked it "won't fix". It's not likely that we would fix this on our own. Closing. |
I just ran into this error as well. After reviewing the issue you linked to, I'd like to quote from the person who marked that chromium issue as WontFix:
The particular issue is reported against the continuous chromium build. chromium from the Debian 7 repo uses the default glibc (2.13) as evidenced by the following terminal output:
So this error is not a hard limit of the chromium dependency, it is a result of inattention by the packager. It would be a shame for Brackets to support Windows XP but not Debian 7. Debian users kind of have a thing for open source software. |
I've just successfully built and run Brackets (and brackets-shell) on Debian 7 with the default libc6 and it works fine as far as I can tell.
I hope this issue will be fixed in the next sprint, as it is a fairly trivial fix. |
Thanks @kaen. Reopening to investigate. Are you running from a dev build or did you build an installer with We recently changed our Debian packaging to match chrome's. The libc6 dependency for Chrome lists libc6 >= 2.11 https://github.com/adobe/brackets-shell/blob/master/installer/linux/debian/control#L8. This is what will be released shortly for the sprint 30 build. I'd be curious if this fixes the problem or if we need to change our build environment. |
I was originally just using a dev build, but I just ran |
Ok great. Sounds like we can close this issue for real now. Thanks! |
Same issue here with Sprint 30 on Linux Mint Debian. |
Same problem here with sprint 30 and 31. Is there any documentation describing the steps to compile Brackets?, I tried cloning the git repo and doing |
@carragom https://github.com/adobe/brackets-shell/wiki/Building-Brackets-Shell. Make sure you've cloned |
@peterflynn No wonder it was not working for me, was missing a whole repo, thanks will give a try. |
Well I tried that and I got an error when running
Looks like libcef comes in binary form and linked against GLIBC_2.14 which is not available in Debian stable. Is there a target to build libcef from source or a branch where libcef.so works with GLIBC_2.13 ?. |
What is the status of this issue? I still cannot run it on sprint 31 or 30. Is the only fix to compile it yourself? It would be great if the 64bit debs were distributed with the fix. Does anyone have an unofficial deb that I could install? |
@Stacia I downloaded sprint 32 and the bug still exists. |
Is there any way to prioritize this bug? It shouldn't be hard to fix. This makes it unusable on my PC and an upcoming class I'm taking is using Brackets as part of the curriculum. I don't want to have to install a different OS to use it! |
@kaen what was involved in your fix? It sounds like it's just a build environment issue and not an issue with our packaging script? Do you think there's a workaround without changing the build environment? @Stacia we're near the end of Sprint 33, so it's likely not going to be fixed by this release. If you're able to build brackets-shell on your own like @kaen did, it may work. We're not 100% clear on the fix yet. I'm curious though, what's the class you're taking and how is Brackets involved? |
I get this error on Debian 7 32bit. Any updates on fixing this bug? |
I am facing the same problem, any fix of it? |
Same problem here, any fix of it? |
Hi guys, when I got brackets to run, all I had to do was build brackets-shell myself on Debian 7. I'm pretty positive the issue can be fixed by building the packaged executable on a Debian 7 machine instead of whatever it's built on now (apparently either Ubuntu or Debian Jessie). You could also probably just install the older glibc (2.13) on the build machine and build against that instead of the later glibc it has. This really shouldn't have been an issue for three months running ... |
Removed "64bit" from title since comments above indicate this affects 32-bit as well |
The same issue here with the Brackets.Release.0.44.64-bit.deb and Debian wheezy |
One month later, over a year after the issue was opened. Bracket does not run on Wheezy. WHAT!? |
👯 |
It is a pretty severe problem for a project this size to not have prioritized this issue in over a year. Node and Chromium works just fine on Debian Wheezy, using Brackets in Google Chrome as an extension also works (using Quickfire, which however is buggy for a whole slew of reasons I suspect are specific to the shaky territory of using Brackets in the browser). There is no reason Brackets should depend on glibc > 2.13 when the components it depends on verifiably work just fine with the 2.13 found in Wheezy. For that reason alone, this issue should have been resolved aeons ago. Debian isn't a small, unknown distribution, especially not to developers, even if Ubuntu is larger these days. I use Brackets on Windows and like it a lot, but it is an understatement that I find the longevity of this issue disappointing. |
+1 |
@sikker The problem is not Chromium, but rather the build packaging of the CEF library that wraps it (fallout from working around an older Chrome bug. See details in the thread above, starting here: #4816 (comment). We're in the process of moving to a newer CEF version now (finally), which may fix this problem entirely. However, we've been unable to build with the new CEF on Linux so far. If anyone is able to help us resolve the build problems and get this working with Linux, here are the details: https://groups.google.com/forum/#!topic/brackets-dev/0dXM-I3CzRk. |
Well given that Debian 8 is currently in soft freeze, and the final, hard freeze seems scheduled to happen sometime in February, it's likely that people will be upgrading their way out of the Debian 7 problem naturally in a few months. For this reason I certainly wouldn't allot time and resources to finding a specific fix for the Debian 7 version at this point. I'm merely expressing disappointment in how an issue of this severity hasn't been handled in the first place for a year and a half, and would like to encourage the team to prioritize these kinds of issues in the future. You do good work and you make a solid editor. I'm afraid solving the current general Linux build problems you mention is a bit outside my field of expertise (if it weren't I'd of course have put my money where my mouth is and submitted a fix myself for this issue), but I trust the Ubuntu community will deliver ample support for at least getting Brackets to build on that OS. |
@sikker I will not be upgrading to Debian 8. I am philosophocally opposed to systemd, and want to avoid systemd at all costs, and I'll stay with 7 as long as I can (I'm even considering moving to one of the BSDs like FreeBSD or OpenBSD), so I for one would love it if Brackets would work on Debian 7 - although, to be fair, I can't ever see that happening |
@sikker If you search for "CEF" in our issue database here, hopefully it's clear that we've actually poured a lot of effort into trying to upgrade to a newer Chromium build, which is really the only way to fix this (along with a number of other important issues). As I said above, we're finally now very close to getting it working. I'll post a note here once a build is available for testing, so everyone can test whether it does indeed resolve the issue as expected. |
@peterflynn - thanks for all your hard work. I really like Brackets and would love to use it |
Btw @sikker Can you suggest any place we could ask for help from the Ubuntu community? Several people have told us "oh, the community will definitely help you out" -- but despite our repeated pleas for help no one has ever stepped up to help us resolve Linux build issues :-/ |
Experiencing the same issue
I tried to install an older version of Brackets down to Sprint 32 but that did not help. I also tried to build Brackets from sources as described here https://github.com/adobe/brackets-shell/wiki/Building-Brackets-Shell but then also ran into some issues. WorkaroundI found a workaround http://stackoverflow.com/questions/10863613/how-to-upgrade-glibc-from-version-2-13-to-2-15-on-debian for Debian Wheezy. Upgrading glibc from 2.13 to 2.19 worked for me. Now Brackets starts up and I can use it.
Very likely that other applications that depend on glibc should run fine with its newer version but not sure about this, did not check it fully http://stackoverflow.com/questions/11107263/how-compatible-are-different-versions-of-glibc Steps I performed:
|
Thanks antivanov... that's worked just fine... brackets working now. |
Download libc6 :http://packages.ubuntu.com/precise-updates/libc6 then create a folder anywhere (ex:/home/newlib) $sudo dpkg -x libc6-dev_2.15-0ubuntu10.11_i386.deb /home/newlib Then vim /home/.bashrc if LD_LIBRARY_PATH value already written add :/home/newlib/lib/i386-linux-gnu end of line. else add fallowing value save/close. update source /home/.bashrc Start Brackets on console. |
this worked on my wheezy 64 bits |
Thanks antivanov , That's work |
Thank you antivanov : ) |
Thank you @antivanov : ) Happy Back To The Future / Flux Capacitor Day! eric@flux-capacitor:Desktop $ cat /etc/issue eric@flux-capacitor:Desktop $ uname -a |
Is there a way to run Brackets on centos6.5? I am getting the following errors when i run it: |
@thefirstofthe300 the trick with the symbolic links works like a charm 🥇 tnx a lot! Brackets finally working on Wheezy! |
Update from @jasonsanjose:
A fix for this issue requires an update to CEF https://code.google.com/p/chromiumembedded/ to fix the glib dependency. A story for this issue is logged here https://trello.com/c/CySUsuf4.
Original Message
The text was updated successfully, but these errors were encountered: