Skip to content
This repository has been archived by the owner on Sep 6, 2021. It is now read-only.

Tabs on top of editor are unreadable #13927

Closed
3 tasks done
0xjmux opened this issue Nov 27, 2017 · 4 comments
Closed
3 tasks done

Tabs on top of editor are unreadable #13927

0xjmux opened this issue Nov 27, 2017 · 4 comments

Comments

@0xjmux
Copy link

0xjmux commented Nov 27, 2017

Prerequisites

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

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

Description

First of all, I'm trying to use the stable version, 1.11.6, downloaded both from github and the big button of brackets.io. The top of the editor (where tabs like file, edit, help, etc go) is instead replaced by black squares. All sub buttons are also black squares. This is a new, unmodified release, I just downloaded. I've downloaded 3 separate times, same issue. I'm running a freshly updated version of kubuntu 17.10. I attached a screenshot.

Steps to Reproduce

  1. Open Brackets
  2. Look at top bar
  3. Can't read top bar
  4. Profit???
    screenshot_20171126_195504

Expected behavior:
Be able to read top buttons

Actual behavior:
Unable to read top buttons

Versions

Please include the OS and what version of the OS you're running.
Kubuntu 17.10
Please include the version of Brackets. You can find it under Help -> About Brackets (Windows and Linux) or Brackets -> About Brackets (macOS)
1.11.6

@ParadauxDev
Copy link

Running on Linux just fine, Ubuntu 16.04 no missing tabs

@mrVragec
Copy link

mrVragec commented Dec 1, 2017

Same issue here.
Working on Ubuntu 17.10.
Tried Reload Without Extensions but same issue persist.
Previous version (1.10 and 1.9) working without issues.

screenshot from 2017-12-01 22-16-29

screenshot from 2017-12-01 22-17-34

screenshot from 2017-12-01 22-18-40

@kenstuddy
Copy link

kenstuddy commented Dec 4, 2017

This appears to be a duplicate of #13738.

@0xjmux
Copy link
Author

0xjmux commented Feb 1, 2018

This issue was fixed in the latest early/developer release for me. I'm closing the issue now.

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

No branches or pull requests

5 participants