Super User is a question and answer site for computer enthusiasts and power users. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I'm using awesome as window manager for a small surf&info terminal. Chromium is started directly after login on the first workspace and should be displayed fullscreen. I've set the layout of all workspaces to awful.layout.suit.max and followed Awesome FAQ so that Chromium and all other (automatically) started programs will be shown on the right workspace. All programs except Chromium will start correctly in fullscreen mode.

I tried

{ rule = { class = "chromium-browser" },  
    properties = {floating = false, tag = tags[1][1]}}


{ rule = { class = "chromium-browser" },  properties = {tag = tags[1][1]}}

but Chromium will always start in floating mode. This is a bit annoying as you still see awesome's panel at the top.

share|improve this question
up vote 5 down vote accepted

You want to run xprop | grep WM_CLASS and then click a chromium window. This will return the correct class string.

Don't forget to restart AwesomeWM after you make this change.

share|improve this answer
This reports WM_CLASS(STRING) = "chromium-browser", "Chromium-browser" on Gentoo (where I develop) and WM_CLASS(STRING) = "chromium", "Chromium" on Debian (which the destination machine runs). Adding the same rule with class="chromium" did help. A bit weird that the name differs between Linux distributions. – xhochy Oct 16 '12 at 11:48
@xhochy I believe that package builders of some distributions use chromium-browser to differentiate the executable from the one provided by the game Chromium BSU. I assume they changed the WM_CLASS appropriately. – zmode Oct 16 '12 at 12:01

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

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