Brackets: Can't use brackets because of this strange menu bar bug

[surajmandalcell]

I did some research and found this to be a troublesome issue as it means there's something wrong with my systems text encoding but just to double check it i wanted to file a bug to see if its my OS (ubuntu 17.10 daily builds) or is it brackets on its own or conflicting with some other program.

A picture says a thousand words so here's the accurate representation of what the problem is

Please fix

[narayani28]

@surajmandalcell - Brackets works fine on Ubuntu 16.04.3 LTS and we have verified the working on the LTS with no issues. Kindly switch to 16.04.3 LTS for working with Brackets.

[mmmmmmbeer]

Experiencing the same issue here on Fedora 26. I suspect an invalid character set or language somewhere in the config, but haven't located anything yet.

[ycUygB1]

Same problem on Gentoo

[ficristo]

See also https://github.com/adobe/brackets/issues/13731

[kuboosoft]

The error persists! full log... Using Fedora 26...

[makerpm@localhost brackets]$ ./Brackets
../../sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf failure in syscall 0318
Received signal 11 SEGV_ACCERR 0000008d813e
#0 0x7ff5dabba7db base::debug::(anonymous namespace)::StackDumpSignalHandler()
#1 0x7ff5d7d993b0 <unknown>
#2 0x7ff5ddbd2db3 sandbox::CrashSIGSYS_Handler()
#3 0x7ff5ddbd19fb sandbox::Trap::SigSys()
#4 0x7ff5d7d993b0 <unknown>
#5 0x7ff5d79f21db getrandom
#6 0x7ff5d6e79b05 <unknown>
#7 0x7ff5d6e7b743 XML_ParseBuffer
#8 0x7ff5c210e6fd <unknown>
#9 0x7ff5c215069c <unknown>
#10 0x7ff5c210bbc7 <unknown>
#11 0x7ff5c3d8c52e <unknown>
#12 0x7ff5c3d5bcc9 <unknown>
#13 0x7ff5c3d8d2f8 <unknown>
#14 0x7ff5db44f6b1 gfx::GLContextGLX::Initialize()
#15 0x7ff5db43de67 gfx::GLContext::CreateGLContext()
#16 0x7ff5db84f95a gpu::GpuCommandBufferStub::OnInitialize()
#17 0x7ff5db84f33a _ZN3IPC8MessageTI35GpuCommandBufferMsg_Initialize_MetaSt5tupleIJN4base14FileDescriptorEEES2_IJbN3gpu12CapabilitiesEEEE18DispatchDelayReplyINS6_20GpuCommandBufferStubEvMSB_FvS4_PNS_7MessageEEEEbPKSC_PT_PT0_T1_
#18 0x7ff5db84eb63 gpu::GpuCommandBufferStub::OnMessageReceived()
#19 0x7ff5db840a48 IPC::MessageRouter::RouteMessage()
#20 0x7ff5db84c163 gpu::GpuChannel::HandleMessageHelper()
#21 0x7ff5db84c0e2 gpu::GpuChannel::HandleMessage()
#22 0x7ff5db84cbb3 _ZN4base8internal7InvokerINS_13IndexSequenceIJLm0ELm1EEEENS0_9BindStateINS0_15RunnableAdapterIMN3gpu10GpuChannelEFvRK13scoped_refptrINS6_22GpuChannelMessageQueueEEEEEFvPS7_SC_EJNS_7WeakPtrIS7_EESC_EEENS0_12InvokeHelperILb1EvSF_EEFvvEE3RunEPNS0_13BindStateBaseE
#23 0x7ff5dabbb9ec base::debug::TaskAnnotator::RunTask()
#24 0x7ff5dabd5355 base::MessageLoop::RunTask()
#25 0x7ff5dabd5678 base::MessageLoop::DeferOrRunPendingTask()
#26 0x7ff5dabd583b base::MessageLoop::DoWork()
#27 0x7ff5dabb0cfa base::(anonymous namespace)::WorkSourceDispatch()
#28 0x7ff5d88a6247 g_main_context_dispatch
#29 0x7ff5d88a65e8 <unknown>
#30 0x7ff5d88a667c g_main_context_iteration
#31 0x7ff5dabb0bd6 base::MessagePumpGlib::Run()
#32 0x7ff5dabec030 base::RunLoop::Run()
#33 0x7ff5dabd4b7a base::MessageLoop::Run()
#34 0x7ff5dd469b9d content::GpuMain()
#35 0x7ff5ddc9b257 content::ContentMainRunnerImpl::Run()
#36 0x7ff5ddc99d00 content::ContentMain()
#37 0x7ff5daac0b03 CefExecuteProcess()
#38 0x7ff5daa64ba7 cef_execute_process
#39 0x0000004925c2 CefExecuteProcess()
#40 0x0000004212dd client::(anonymous namespace)::RunMain()
#41 0x000000421c07 main
#42 0x7ff5d79d650a __libc_start_main
#43 0x00000040c849 <unknown>
  r8: 0000000000000000  r9: 0000000000000000 r10: 0000000000000000 r11: 0000000000000246
 r12: 0000000000000000 r13: 00007ff5de6b77d9 r14: 00000000000d813e r15: 00007fff90e849e0
  di: 0000000000000002  si: 00007ff5de6b77d8  bp: 000000000000013e  bx: 0000000000000000
  dx: 0000000000000001  ax: 00000000000d8000  cx: 00000000008d813e  sp: 00007fff90e849d0
  ip: 00007ff5ddbd2db3 efl: 0000000000010202 cgf: 002b000000000033 erf: 0000000000000006
 trp: 000000000000000e msk: 0000000000000000 cr2: 00000000008d813e
[end of stack trace]
[0927/200314:ERROR:command_buffer_proxy_impl.cc(194)] Could not send GpuCommandBufferMsg_Initialize.
[0927/200314:ERROR:webgraphicscontext3d_command_buffer_impl.cc(199)] CommandBufferProxy::Initialize failed.
[0927/200314:ERROR:webgraphicscontext3d_command_buffer_impl.cc(218)] Failed to initialize command buffer.
[0927/200314:ERROR:gpu_channel_host.cc(228)] Failed to send GpuChannelMsg_CreateCommandBuffer.
[0927/200314:ERROR:webgraphicscontext3d_command_buffer_impl.cc(218)] Failed to initialize command buffer.
../../sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf failure in syscall 0318
Received signal 11 SEGV_ACCERR 00000080813e
#0 0x7f61adbab7db base::debug::(anonymous namespace)::StackDumpSignalHandler()
#1 0x7f61aad8a3b0 <unknown>
#2 0x7f61b0bc3db3 sandbox::CrashSIGSYS_Handler()
#3 0x7f61b0bc29fb sandbox::Trap::SigSys()
#4 0x7f61aad8a3b0 <unknown>
#5 0x7f61aa9e31db getrandom
#6 0x7f61a9e6ab05 <unknown>
#7 0x7f61a9e6c743 XML_ParseBuffer
#8 0x7f61950ff6fd <unknown>
#9 0x7f619514169c <unknown>
#10 0x7f61950fcbc7 <unknown>
#11 0x7f6196d7d52e <unknown>
#12 0x7f6196d4ccc9 <unknown>
#13 0x7f6196d7e2f8 <unknown>
#14 0x7f61ae4406b1 gfx::GLContextGLX::Initialize()
#15 0x7f61ae42ee67 gfx::GLContext::CreateGLContext()
#16 0x7f61ae84095a gpu::GpuCommandBufferStub::OnInitialize()
#17 0x7f61ae84033a _ZN3IPC8MessageTI35GpuCommandBufferMsg_Initialize_MetaSt5tupleIJN4base14FileDescriptorEEES2_IJbN3gpu12CapabilitiesEEEE18DispatchDelayReplyINS6_20GpuCommandBufferStubEvMSB_FvS4_PNS_7MessageEEEEbPKSC_PT_PT0_T1_
#18 0x7f61ae83fb63 gpu::GpuCommandBufferStub::OnMessageReceived()
#19 0x7f61ae831a48 IPC::MessageRouter::RouteMessage()
#20 0x7f61ae83d163 gpu::GpuChannel::HandleMessageHelper()
#21 0x7f61ae83d0e2 gpu::GpuChannel::HandleMessage()
#22 0x7f61ae83dbb3 _ZN4base8internal7InvokerINS_13IndexSequenceIJLm0ELm1EEEENS0_9BindStateINS0_15RunnableAdapterIMN3gpu10GpuChannelEFvRK13scoped_refptrINS6_22GpuChannelMessageQueueEEEEEFvPS7_SC_EJNS_7WeakPtrIS7_EESC_EEENS0_12InvokeHelperILb1EvSF_EEFvvEE3RunEPNS0_13BindStateBaseE
#23 0x7f61adbac9ec base::debug::TaskAnnotator::RunTask()
#24 0x7f61adbc6355 base::MessageLoop::RunTask()
#25 0x7f61adbc6678 base::MessageLoop::DeferOrRunPendingTask()
#26 0x7f61adbc683b base::MessageLoop::DoWork()
#27 0x7f61adba1cfa base::(anonymous namespace)::WorkSourceDispatch()
#28 0x7f61ab897247 g_main_context_dispatch
#29 0x7f61ab8975e8 <unknown>
#30 0x7f61ab89767c g_main_context_iteration
#31 0x7f61adba1bd6 base::MessagePumpGlib::Run()
#32 0x7f61adbdd030 base::RunLoop::Run()
#33 0x7f61adbc5b7a base::MessageLoop::Run()
#34 0x7f61b045ab9d content::GpuMain()
#35 0x7f61b0c8c257 content::ContentMainRunnerImpl::Run()
#36 0x7f61b0c8ad00 content::ContentMain()
#37 0x7f61adab1b03 CefExecuteProcess()
#38 0x7f61ada55ba7 cef_execute_process
#39 0x0000004925c2 CefExecuteProcess()
#40 0x0000004212dd client::(anonymous namespace)::RunMain()
#41 0x000000421c07 main
#42 0x7f61aa9c750a __libc_start_main
#43 0x00000040c849 <unknown>
  r8: 0000000000000000  r9: 0000000000000000 r10: 0000000000000000 r11: 0000000000000246
 r12: 0000000000000000 r13: 00007f61b16a87d9 r14: 000000000000813e r15: 00007ffea8d71920
  di: 0000000000000002  si: 00007f61b16a87d8  bp: 000000000000013e  bx: 0000000000000000
  dx: 0000000000000001  ax: 0000000000008000  cx: 000000000080813e  sp: 00007ffea8d71910
  ip: 00007f61b0bc3db3 efl: 0000000000010202 cgf: 002b000000000033 erf: 0000000000000006
 trp: 000000000000000e msk: 0000000000000000 cr2: 000000000080813e
[end of stack trace]
[0927/200315:ERROR:command_buffer_proxy_impl.cc(194)] Could not send GpuCommandBufferMsg_Initialize.
[0927/200315:ERROR:webgraphicscontext3d_command_buffer_impl.cc(199)] CommandBufferProxy::Initialize failed.
[0927/200315:ERROR:webgraphicscontext3d_command_buffer_impl.cc(218)] Failed to initialize command buffer.
../../sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf failure in syscall 0318
Received signal 11 SEGV_ACCERR 00000082813e
#0 0x7f14613d97db base::debug::(anonymous namespace)::StackDumpSignalHandler()
#1 0x7f145e5b83b0 <unknown>
#2 0x7f14643f1db3 sandbox::CrashSIGSYS_Handler()
#3 0x7f14643f09fb sandbox::Trap::SigSys()
#4 0x7f145e5b83b0 <unknown>
#5 0x7f145e2111db getrandom
#6 0x7f145d698b05 <unknown>
#7 0x7f145d69a743 XML_ParseBuffer
#8 0x7f144892d6fd <unknown>
#9 0x7f144896f69c <unknown>
#10 0x7f144892abc7 <unknown>
#11 0x7f144a5ab52e <unknown>
#12 0x7f144a57acc9 <unknown>
#13 0x7f144a5ac2f8 <unknown>
#14 0x7f1461c6e6b1 gfx::GLContextGLX::Initialize()
#15 0x7f1461c5ce67 gfx::GLContext::CreateGLContext()
#16 0x7f146206e95a gpu::GpuCommandBufferStub::OnInitialize()
#17 0x7f146206e33a _ZN3IPC8MessageTI35GpuCommandBufferMsg_Initialize_MetaSt5tupleIJN4base14FileDescriptorEEES2_IJbN3gpu12CapabilitiesEEEE18DispatchDelayReplyINS6_20GpuCommandBufferStubEvMSB_FvS4_PNS_7MessageEEEEbPKSC_PT_PT0_T1_
#18 0x7f146206db63 gpu::GpuCommandBufferStub::OnMessageReceived()
#19 0x7f146205fa48 IPC::MessageRouter::RouteMessage()
#20 0x7f146206b163 gpu::GpuChannel::HandleMessageHelper()
#21 0x7f146206b0e2 gpu::GpuChannel::HandleMessage()
#22 0x7f146206bbb3 _ZN4base8internal7InvokerINS_13IndexSequenceIJLm0ELm1EEEENS0_9BindStateINS0_15RunnableAdapterIMN3gpu10GpuChannelEFvRK13scoped_refptrINS6_22GpuChannelMessageQueueEEEEEFvPS7_SC_EJNS_7WeakPtrIS7_EESC_EEENS0_12InvokeHelperILb1EvSF_EEFvvEE3RunEPNS0_13BindStateBaseE
#23 0x7f14613da9ec base::debug::TaskAnnotator::RunTask()
#24 0x7f14613f4355 base::MessageLoop::RunTask()
#25 0x7f14613f4678 base::MessageLoop::DeferOrRunPendingTask()
#26 0x7f14613f483b base::MessageLoop::DoWork()
#27 0x7f14613cfcfa base::(anonymous namespace)::WorkSourceDispatch()
#28 0x7f145f0c5247 g_main_context_dispatch
#29 0x7f145f0c55e8 <unknown>
#30 0x7f145f0c567c g_main_context_iteration
#31 0x7f14613cfbd6 base::MessagePumpGlib::Run()
#32 0x7f146140b030 base::RunLoop::Run()
#33 0x7f14613f3b7a base::MessageLoop::Run()
#34 0x7f1463c88b9d content::GpuMain()
#35 0x7f14644ba257 content::ContentMainRunnerImpl::Run()
#36 0x7f14644b8d00 content::ContentMain()
#37 0x7f14612dfb03 CefExecuteProcess()
#38 0x7f1461283ba7 cef_execute_process
#39 0x0000004925c2 CefExecuteProcess()
#40 0x0000004212dd client::(anonymous namespace)::RunMain()
#41 0x000000421c07 main
#42 0x7f145e1f550a __libc_start_main
#43 0x00000040c849 <unknown>
  r8: 0000000000000000  r9: 0000000000000000 r10: 0000000000000000 r11: 0000000000000246
 r12: 0000000000000000 r13: 00007f1464ed67d9 r14: 000000000002813e r15: 00007ffe83e82120
  di: 0000000000000002  si: 00007f1464ed67d8  bp: 000000000000013e  bx: 0000000000000000
  dx: 0000000000000001  ax: 0000000000028000  cx: 000000000082813e  sp: 00007ffe83e82110
  ip: 00007f14643f1db3 efl: 0000000000010202 cgf: 002b000000000033 erf: 0000000000000006
 trp: 000000000000000e msk: 0000000000000000 cr2: 000000000082813e
[end of stack trace]
[0927/200315:ERROR:command_buffer_proxy_impl.cc(194)] Could not send GpuCommandBufferMsg_Initialize.
[0927/200315:ERROR:webgraphicscontext3d_command_buffer_impl.cc(199)] CommandBufferProxy::Initialize failed.
[0927/200315:ERROR:webgraphicscontext3d_command_buffer_impl.cc(218)] Failed to initialize command buffer.
getrlimit(RLIMIT_NOFILE) failed

[saurabh95]

You can try to reinstall brackets using command sudo dpkg -i <PATH_OF_DEB_FILE>, it will list the dependencies which failed(there would probably be 1 or 2). You can then install those dependencies, and then launching Brackets should work fine.

[surajmandalcell]

@saurabh95 i did reinstall, i complete uninstalled brackets and reinstalled the most recent version but still persists.

[narayani28]

@mmmmmmbeer , @hnaparst , @kuboosoft - thanks for reporting this issue. In the current 1.11 release, we have started supporting Ubuntu(verified for version 16.04.3 LTS) and Debian(verified for version 9.1.0). In the future releases, we will add support and address the issues for other flavors of Linux.

[surajmandalcell]

@narayani28 i cant just switch operating system just for the sake of 1 text editor, no thanks please comment when the issue is fixed.

[narayani28]

@surajmandalcell - we will keep the community updated when the issue is fixed.

[Romane-T]

As per the first post with the images. Seeing as I do use the menu a bit, this makes using this latest version problematic. Reverting till fixed.
Debian Testing, fully up to date.
Previous version of Brackets works just fine.
Have purged Brackets from my system, deleted every reference could find in a search of the file system, then re-installed. No change.
Re-downloaded the .deb file, re-installed .deb, no change. Install messages the same as with install after purge (except for over-writing bit):

root@romane:/home/romane# dpkg -i /home/romane/downloads/Brackets.Release.1.11.64-bit.deb
(Reading database ... 197808 files and directories currently installed.)
Preparing to unpack .../Brackets.Release.1.11.64-bit.deb ...
Unpacking brackets (1.11.0-17524) over (1.11.0-17524) ...
Setting up brackets (1.11.0-17524) ...
xdg-icon-resource: size argument must be numeric
Try 'xdg-icon-resource --help' for more information.
Processing triggers for hicolor-icon-theme (0.17-1) ...

Have tried changing fonts via the preferences file. Unknown what font Brackets is using in the editor, as the system fonts I tried (about 6 or so) no change to the font in the editor. Previous version was fine.
Just guessing, looks like Brackets is not recognising system fonts, but what font is it recognising/using?
As per issue #13731, looked for libudev0 - not available in repositories. libudev1 is, however, and is installed.
On a whim, located a .deb for libudev0, which was last in Wheezy. Installed, zero affect. Still all squares in the menus.

[gacsnic]

the libjavascriptcoregtk-4.0-18 package
is being retained in debian just like ubuntu, I see it has to do with javascript and gtk, does brackets depend on that package?

[ghost]

Still same problem on Ubuntu 17.10 even if I use sudo dpkg -i <deb-package> and there is no dependencies problem.

[nethip]

Sorry for the inconvenience caused because of this bug. Our initial testing was restricted to 14 and 16 LTS versions. We will try to debug this issue on Ubuntu 17. I will update this thread once we have a solution.

[ghost]

Thank You very much @nethip, I'll be wait to can use this great editor in this Ubuntu version.

[blendsoft]

This bug appear in Debian testing too.

[abhih]

I am using brackets on Kali linux with updated version and this issue is present still. I tried re-installing but the issue persists as of today i.e Oct 4,2017.

[tiago4171]

Same here at Opensuse Tumbleweed

[kiroma]

Same here with Kubuntu 17.10.
What font is used for menu?

[Jeymz]

Ubuntu Variant, POP OS having the same issue.

[louis-irl]

Same issue in Pop!_OS

[surajmandalcell]

@Filthy-Commie is it just me or the characters(rectangle-ish ones) on your screenshot are different than mine?

[darekmeco]

Any progress on this ?

[louis-irl]

@surajmandalcell Does Brackets use the system font maybe?

[surajmandalcell]

@Filthy-Commie maybe brackets is asking system for different font from language pack not installed currently. Could be some typo in the font name for the menu bar. No idea i dont have much time to investigate sorry.

[bici-zizi]

Lighttable (another electron based text editor) has a similar issue:
https://github.com/LightTable/LightTable/issues/2343
It seems that they have already figured out the root cause.

[kiroma]

Does brackets use GTK3?

[kiroma]

I digged around and it seems to be a bug in either Chromium or GTK2.

[surajmandalcell]

@bici-zizi according your cause its a chromium problem. @kiroma yes its chromium, i think

[kiroma]

Unless I don't know how to use LD_PRELOAD properly, it's a bug in Chromium.
I compiled same version of libgtk as in xenial lts and loaded it with LD_PRELOAD to no avail.
Unless I actually preloaded the wrong file I'm not exactly sure.

Edit: Why is there a launch script? It doesn't seem necessary in .debs and it voided some possibly valuable data.
[1017/185343:ERROR:browser_main_loop.cc(249)] GTK theme error: Unable to locate theme engine in module_path: "pixmap",

[p0wnage]

Any update on a fix yet? Ubuntu 17.10 is out of Beta as of today Brackets is still having this issue. Sad that no one from the Adobe team seems to care too much about it.

Temporary Fix

I was able to install Brackets as a Snap package and then refresh the snap and now I have a working 1.11 build as shown in this screenshot. I'm running Ubuntu 17.10

[gacsnic]

las librerias, libwebkit2gtk-4.0-37 version 2.18.1-1 and libjavascriptcoregtk-4.0-18 version 2.18.1-1 corrigen la falla del menu de brackets en debian sid

libwebkit2gtk-4.0-37 version 2.18.1-1 and libjavascriptcoregtk-4.0-18 version 2.18.1-1 fix the brackets menu failure in debian sid

[gacsnic]

failure persists after update

[Ramboush]

Oh man, guess I will have to look for an alternative to Brackets, same problem here

[Romane-T]

First, I am not a developer, merely another user. Just to put my
comments into perspective.

There are a couple of alternatives (Atom, Code come to mind), but my
personal experience is that they don't quite come up to scratch in small
but, to me, quite irritating ways.

Easy solution - downgrade till this issue is fixed.

Just a personal opinion.

Romane

On 24/10/17 22:02, Ramboush wrote:
>

Oh man, guess I will have to look for an alternative to Brackets, same
problem here

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/adobe/brackets/issues/13738#issuecomment-338967084,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AIf16MsFMcFcboyfO-fgrt73gkQqd7ncks5svdHMgaJpZM4PlMiv.

[narayani28]

We are looking into this issue and will provide an update soon. We understand the seriousness of the issue and sorry for the inconvenience.

• Adobe Brackets team

[bici-zizi]

narayani28: Thanks for the feedback!

[FabioMojo]

Same problem with ubuntu 17.10 and gnome 3.26.1 ...
I guess I'll have to downgrade too. Brackets is the only software causing such problem on my system right now. Hope there will be a fix soon !

[PanadeEdu]

I confirm this issue as well with Ubuntu 17.10.

[itachikesh]

Same issue in latest kali distro, please fix it asap. I love brackets

[kiroma]

Thanks to @chsjr1996 we now know which package is responsible for the issue, I've pinpointed the commit to this: https://git.gnome.org/browse/pango/commit/?id=906509e22bf617d97a71f41d335d7a0dec344187
Which is slightly worrying for me, since it removes a deprecated way of displaying glyphs.
The PR made by @linxon works around the issue rather than resolving it by downloading an older version of libpangoft.

[mmmmmmbeer]

Thanks to @chsjr1996's detective work, I was able to implement a similar workaround on Fedora 27. Since I also had the problem on F26 a few weeks back, I grabbed the F25 pango from rpmfind (pango-1.40.3-1.fc25.x86_64.rpm), extracted libpang* to /opt/brackets/, and success!

I imagine a similar approach would work for those on other distros experiencing this issue - try finding the pango libraries for your distro prior to the problematic commit identified by @kiroma, and extract to /opt/brackets/. Certainly worth a shot!

[pauledd]

thanks @mmmmmmbeer , on gentoo I was able now to run brackets 1.11 from @hnaparst overlay by downgrading pango to 1.40.3. Now need to copy anything.

[MoonbiteAgency]

In debian based dists, you can get libpango and libpangoft2 from stable and put libs from them in /opt/brackets
https://packages.debian.org/search?keywords=libpango&searchon=names&suite=stable&section=all

#/opt/brackets$ ldd ./Brackets | grep pango
    libpangocairo-1.0.so.0 => /usr/lib/x86_64-linux-gnu/libpangocairo-1.0.so.0 (0x00007fad8727f000)
    libpango-1.0.so.0 => /opt/brackets/./libpango-1.0.so.0 (0x00007fad87033000)
    libpangoft2-1.0.so.0 => /opt/brackets/./libpangoft2-1.0.so.0 (0x00007fad83e5d000)

[Romane-T]

My sincere appreciation. This worked for me (Buster). Running 1.11 with
menu's at last.

On 07/11/17 16:26, Moonbite Agency wrote:
>

In debian based dists, you can get libpango and libpangoft2 from
stable ant put libs from them in /opt/brackets
https://packages.debian.org/search?keywords=libpango&searchon=names&suite=stable&section=all

|#/opt/brackets$ ldd ./Brackets | grep pango libpangocairo-1.0.so.0 =>
/usr/lib/x86_64-linux-gnu/libpangocairo-1.0.so.0 (0x00007fad8727f000)
libpango-1.0.so.0 => /opt/brackets/./libpango-1.0.so.0
(0x00007fad87033000) libpangoft2-1.0.so.0 =>
/opt/brackets/./libpangoft2-1.0.so.0 (0x00007fad83e5d000) |

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/adobe/brackets/issues/13738#issuecomment-342387848,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AIf16IPzM28L0d6zesjL9IPrzJNvO3Ksks5sz_gFgaJpZM4PlMiv.

[surajmandalcell]

can they update the actual package now please, adobe

[kiroma]

We're waiting for 1.12 to go live, it will contain the workaround, don't worry.

[p0wnage]

For anyone running Ubuntu 17.10 latest, I extracted the 4 files needed as a compressed tar file to make it easy for others. Just extract them and place them into your /opt/brackets directory.

I had 1.10 installed and placed the files in then upgraded and it works 100% menus and all. Thank's to all who helped solve this mystery!

Extracted Libpango downloads for Ubuntu 17.10

[nethip]

This is now fixed. The problem was with the version of CEF that we are using for the shell. We will update the S3 bucket with the updated CEF binary.

[kiroma]

There's been a merged PR which worked around the bug by installing older version of libpango, will it be reverted?

[nethip]

@kiroma I am not sure if we had any PR that targets reverting libpango to older version. AFAIK, it was just the workaround suggested by one of our community members.

[kiroma]

Oh, I'm sorry, I misunderstood one of the notesade by github, I didn't know you could reference an issue from another repository.

[Handwrit]

This is stupid. Why isn't there a 1.111 release, to fix this bug? It's a severe issue! It means it doesn't even work on Ubuntu.

[RustyRaptor]

Ok, the fix above fixed the issue. Bless you, guys. Saved my life.

[DevPre24]

Thanks for the fix above. Managed to make it work on Fedora 27.

[nethip]

Sorry for the inconvenience.

Update on the Linux build: We are targeting Linux patch for 2 critical bugs w.r.t IME and font corruption.

1) IME: This was really challenging as IME was not implemented in CEF, so we had to patch lot of code from Chromium. We somehow got this fixed and now testing it extensively.
2) Font Corruption: This is fixed now.

By next week we are planning to do a Linux refresh (if we don't find any more blockers in our testing).

[Romane-T]

Good morning Prashanth

Thank you for the update. It is very much appreciated.

With warm greetings

Romane

On 08/12/17 19:26, Prashanth Nethi wrote:
>

Sorry for the inconvenience.

Update on the Linux build: We are targeting Linux patch for 2 critical
bugs w.r.t IME and font corruption.

1. IME: This was really challenging as IME was not implemented in
   CEF, so we had to patch lot of code from Chromium. We somehow got
   this fixed and now testing it extensively.
2. Font Corruption: This is fixed now.

By next week we are planning to do a Linux refresh (if we don't find
any more blockers in our testing).

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/adobe/brackets/issues/13738#issuecomment-350215773,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AIf16IOb56-bvggtig6pwe_mW1CNlWdmks5s-QC2gaJpZM4PlMiv.

[warrior-of-light]

Same issue persists for Debian buster/sid also.

[kiroma]

A 1.12 prerelease for Linux is now live and it addresses this bug.

[nethip]

Thanks for updating the thread @kiroma. Please try out the pre-release build and give us the feedback!

[nethip]

We have uploaded a pre-release build (Linux 64 only) to address this issue. Please try the build and let us know your feedback. You can download the build from https://github.com/adobe/brackets/releases/tag/release-1.12-prerelease.

[nethip]

We now have updated the installers for Linux 32 and 64 bit. Please download the same from http://brackets.io. Thanks!