0

Complete emacs beginner here. Just installed emacs in my Manjaro (awesomewm edition) machine using pacman.

The emacs window is almost completely transparent, I can't read anything. If started from a terminal, it raises these errors:

(emacs:4193): Gtk-CRITICAL **: 23:20:57.211: _gtk_css_image_get_concrete_size: assertion 'default_width > 0' failed

(emacs:4193): Gtk-CRITICAL **: 23:20:57.211: _gtk_css_image_get_surface: assertion 'surface_width > 0' failed

(emacs:4193): Gtk-CRITICAL **: 23:20:57.211: _gtk_css_image_get_concrete_size: assertion 'default_width > 0' failed

(emacs:4193): Gtk-CRITICAL **: 23:20:57.211: _gtk_css_image_get_surface: assertion 'surface_width > 0' failed

(emacs:4193): Gtk-CRITICAL **: 23:20:57.211: _gtk_css_image_get_concrete_size: assertion 'default_width > 0' failed

(emacs:4193): Gtk-CRITICAL **: 23:20:57.211: _gtk_css_image_get_surface: assertion 'surface_width > 0' failed

Any clues on what's wrong?

Screenshot: enter image description here

Note: also tried installing emacs with another package manager (guix) as a foreign package manager. Still got the same problem.

  • 2
    Are you starting Emacs using emacs -Q (no init file)? If you do that, do you see the same problem? If not, bisect your init file to find the culprit. – Drew Oct 23 at 22:12
  • 2
    Those messages are GTK complaining about your theme, and may or may not be related to your problem. If they are related, perhaps trying a different theme would give you better results. – db48x Oct 23 at 23:54
  • 1
    @Drew The problem vanishes if I run emacs -Q. I'll try and debug the init file then. Note: I still get an error (emacs:3317): Gtk-CRITICAL though. – Soap Oct 24 at 8:14
  • @Drew For some reason the .emacs, .emacs.el or init.el files are nowhere to be found. So it seems emacs is running with the defaults? But then it shouldn't have a theme, I guess... – Soap Oct 24 at 10:16
  • emacs -Q doesn't load either your init file or the site-lisp.el file. emacs -q (lowercase) doesn't load your init file but still loads site-lisp.el. So maybe check both, and if you see a difference check what's in library site-lisp.el. – Drew Oct 24 at 17:40
1

Welcome Soap!

This seems unrelated to Emacs. I guess it could be related to your window manager (AwesomeWM), some kind of X11 compositor like Compton or the configuration files associated with those.

Try to add the following to your init.el.

(add-to-list 'default-frame-alist '(alpha 100))

| improve this answer | |
  • Killing compton did solve the issue, but I'd still like a permanent solution. It is still strange that compton only has issues with emacs though. – Soap Oct 28 at 15:04
  • Try to add the following to your init.el: (add-to-list 'default-frame-alist '(alpha 100)) – aadcg Oct 28 at 15:32
  • I do not have a init.el file. Shall I create one in .emacs.d/? – Soap Oct 28 at 16:05
  • 1
    Yes, just create it at ~/.emacs.d/init.el. – aadcg Oct 28 at 17:50
  • Working flawlessly now :D – Soap Oct 29 at 12:11

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.