Brackets can't run on Debian 7 (Wheezy)

[tranduyhung]

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

Hi,

I get the following error when run Brackets sprint 29 on my Debian 64bit:

/opt/brackets/Brackets: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.14' not found (required by /opt/brackets/Brackets).

I have tried to applied the solutions in #4720 ln -s libudev.so.1 libudev.so.0, however libudev.so.0 has already existed in my system.

$ ls -al libudev.*
lrwxrwxrwx 1 root root 17 Jul 20 11:38 libudev.so.0 -> libudev.so.0.13.0
-rw-r--r-- 1 root root 59992 Apr 29 05:36 libudev.so.0.13.0

[favadi]

This bug is also happend for me on Debian 7 64 bit.

[thefirstofthe300]

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:

sudo ln -s /lib/x86_64-linux-gnu/libc.so.6 /lib/x86_64-linux-gnu/libc-2.17.so

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.

[larsemil]

Duplicate of #4720

[tranduyhung]

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.

[tranduyhung]

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".

[jasonsanjose]

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.

[bkconrad]

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:

Who build your copy of Chromium? The ones from chromium.org's continuous build recently switched from Lucid to Precise. Thus it is built against Ubuntu Precise's glibc (2.15) whereas Debian 7 has glibc 2.13.

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:

kaen@debian ~ $ ldd /usr/lib/chromium/chromium | grep libc.so
    libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007fbb950ae000)
kaen@debian ~ $ /lib/x86_64-linux-gnu/libc.so.6
GNU C Library (Debian EGLIBC 2.13-38) stable release version 2.13, by Roland McGrath et al.

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.

[bkconrad]

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.

sprint 30 development build 0.30.0-0 (master 60dc6b7)

I hope this issue will be fixed in the next sprint, as it is a fairly trivial fix.

[jasonsanjose]

Thanks @kaen. Reopening to investigate. Are you running from a dev build or did you build an installer with grunt installer?

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.

[bkconrad]

I was originally just using a dev build, but I just ran grunt installer and the generated .deb file installed happily on my system.

[jasonsanjose]

Ok great. Sounds like we can close this issue for real now. Thanks!