0.13

[ddevault]

Over the next few weeks I'll start putting together 0.13 rc's and breaking ground on wlroots. Would appreciate some volunteers with nvidia hardware testing out wlc's new proprietary driver support in the meantime. If you have any new features to include in 0.13, now is the time.

[4e554c4c]

Will proprietary nvidia driver support be included in wlroots?

[ddevault]

Unlikely.

[WhyNotHugo]

I hope this helps; logs using 0.12 and the latest master (mislabeled 0.13 there, I just realized).

https://gist.github.com/hobarrera/c4b317677db8a8a07d31aea58163b1cc

I just used the same settings I use for testing on my other machine (Intel-based video).

[WhyNotHugo]

I updated the gist and also added the output of running latest master with the default config file, just in case.

[ddevault]

Logs aren't necessary, just tell us about your experience with the proprietary driver and sway. Did everything work as expected?

[WhyNotHugo]

Sorry, I should have clarified that: it did not start at all (exited immediately, no black screen or weird stuff). That's why I included the logs.

[4e554c4c]

@hobarrera See #1147. Nvidia support is not yet merged and in order to test it you will have to build from the nvidia-support branch. Other things may have to be done to make it work as well, such as enabling the experimental DRM KMS driver, see nvidia's release notes.

[WhyNotHugo]

Running the nvidia-support branch had similar results. I can't try enabling DRM/KMS, because linux 4.10 and nvidia-378.13 are known to crash with it enabled, so I'll have to wait until that clears.

Oddly, I'm seeing this in the logs, even though I ran sudo setcap cap_sys_ptrace=eip /usr/local/bin/sway (also ran it with -v to verify the caps were okay):

[main.c:174] !! DANGER !! Sway does not have CAP_SYS_PTRACE and cannot enforce security rules for processes running as other users.

Regrettably, until enabling DRM on nvidia actually works without crashing the kernel, I can't try much more. :(

[ddevault]

nvidia-support is not required, just an up to date wlc and the KMS drivers.

[WhyNotHugo]

My last test was done with wlc-ga7a3db8 and sway-179f6a5.

I'll try enabling KMS, but it's know to freeze/crash on the latest nvidia driver/kernel, so no promises.

[ddevault]

I'll try enabling KMS, but it's know to freeze/crash on the latest nvidia driver/kernel, so no promises.

Well, it's required to use wayland on nvidia, so

[WhyNotHugo]

It works, and I'm posting from firefox via sway on nvidia. Also watched a single youtube video on firefox.

I tested a few apps, and the only thing I noticed failing was mpv (which works under intel).

It just doesn't render anything (eg: the tile for it is transparent and I see my background), but it does have audio. The log just shows:

[vo/opengl] after rendering: OpenGL error INVALID_FRAMEBUFFER_OPERATION.

[DmitryHetman]

mpv supports wayland natively. If it doesn't work try to launch it with xwayland.

[ddevault]

0.13-rc1 has been released, please test it. Working on the changelog now.

[ddevault]

This release contains 102 changes from 12 contributors. New features include support for i3's marks feature, "immediate" criteria commands, and experimental support for the nvidia proprietary driver. Many small improvements to i3 compatibility and many bugfixes are also included.

For nvidia users, nouveau is still strongly recommended. The proprietary driver mostly works, but is unsupported - do not report bugs unless you attach a patch. Unless your hardware is unsupported by nouveau, you should continue using nouveau. Using sway with the proprietary drivers requires additional configuration - sway will output the necessary information if you attempt it without a correct configuration.

Package maintainers: please update your packages to use -DVERSION=major.minor.patch. Normally the version is sourced from git, but if you build from a tarball then you'll have to specify it manually.

Changes

• The new_window and new_float commands are deprecated in favor of default_border and default_floating_border. A similar change is expected from i3. (@zandrmartin - fix workspace output assignment #1105)
• 444 is now an acceptable file mode for security configs (@jnsaff - Allow also 444 for security file mode #1117)
• Any executable that is not owned by root will receive the default security policy regardless of any additional configured permissions (@JerziKaminsky)

New features

• i3-style marks are now supported (@4e554c4c - Impliment i3-style marks #1145 & Add -t get_marks and use more i3-like marks #1155)
• You may now configure the color of swaylock UI elements via the command line (@4e554c4c - Make colors for swaylock unlock indicator configurable #1078)
• Floating containers may now be moved with the move command (@4e554c4c - i3 feature support: Moving flotaing containers #1092)
• swaymsg pretty-prints its output if stdout is a tty (@SirCmpwn - Add pretty printing to swaymsg #1146)
• [criteria] command has been implemented (@4e554c4c - Improve criteria handling #1149)
• nvidia proprietary driver support has been implemented in wlc (@vially - Add EGL stream support Cloudef/wlc#245) and sway was updated as necessary (@SirCmpwn - Downgrade nvidia proprietary driver warning #1147)
• Security policies can now refer to symlinked executables (@JerziKaminsky - IPC security - Allow policy targets to be symlinks #1173)
• Version string can now be specified at build time (@snoack - Add -DVERSION flag for release version numbers #1194)

Bugs fixed

• Missing swaylock security settings were added (@SirCmpwn - 21ad45b)
• -Werror issues on the latest gcc have been corrected (@Fale - Ignore Wimplicit-fallthrough #1086)
• The codebase is more POSIXly correct and does not rely on GNUisms (@SirCmpwn - 9aed9d9)
• Issues building against a local copy of wlc has been fixed (@snoack - Superfluous include causes failures if WLC headers aren't installed globally #1115)
• A problem with keyboard code in sway's Wayland clients was fixed (@zandrmartin - add missing ! for wl seat keyboard caps #1121)
• Focus could be stolen from fullscreen windows under some conditions (@zandrmartin - prevent fullscreen focus thievery #1126)
• Spaces are now permitted in workspace names (@4e554c4c - Fix #1099: Allow spaces in worspace names #1101)
• Issues with workspace assignment have been corrected (@zandrmartin - fix workspace output assignment #1105)
• Man page typos fixed (@johnchen902 - Fix trivial typo in sway.5.txt (right_ -> _right_) #1113)
• Crashiness with move [next|prev] was fixed (@oranenj - Fix move next crash #1130)
• Regular expressions are now handled with PCRE for better i3 compatibility (@ascent12 - Change regex to use PCRE #1151)
• Dangling file descriptors on IPC client termination was fixed (@SirCmpwn, @ascent12 - Fix dangling file descriptors (fixes #1152) #1153)
• libcap is now explicitly required in our CMakeLists.txt (@JerziKaminsky - Add libcap check to CMake #1150)
• move [to] scratchpad did not support the "to" syntax (@wasamasa - Feature move to scratchpad #1180)
• Windows leaving the scratchpad are now sized to match i3 behavior (@wasamasa - Use i3's dimensions for initial scratchpad views #1181)
• Specifying fewer than 5 colors with client.* now matches i3 behavior (@SirCmpwn - Support specifying fewer than 5 colors #1201)

[JerziKaminsky]

@SirCmpwn , I'm about to submit an update to the policy validation thing as soon as #1184 is merged. I found an issue.

[4e554c4c]

Not to be picky, but shouldn't marks also be in the "New Features" section?

[ddevault]

Thanks for pointing that out, @4e554c4c.

[ddevault]

0.13-rc2 would be released today, but there are no changes. I don't feel comfortable releasing 0.13 yet so we're going to delay rc2 another week.

[ddevault]

0.13-rc3 is out, please test it: https://github.com/SirCmpwn/sway/releases/tag/0.13-rc3

[ddevault]

Changelog updated.

[ddevault]

0.13.0 has been released: https://github.com/SirCmpwn/sway/releases/tag/0.13.0