LWN.net's Journal
[Most Recent Entries]
[Calendar View]
Thursday, October 8th, 2015
| Time |
Event |
| 1:03a |
[$] LWN.net Weekly Edition for October 8, 2015
The LWN.net Weekly Edition for October 8, 2015 is available. | | 7:15a |
Bottomley: Respect and the Linux Kernel Mailing Lists SCSI subsystem maintainer James Bottomley has posted a
different view on the issue of civility on the kernel's mailing lists. " So, by and large, I’m proud of the achievements we’ve made in
civility and the way we have improved over the years. Are we perfect? by
no means (but then perfection in such a large community isn’t a realistic
goal). However, we have passed our stress test: that an individual with
bad patches to several mailing lists was met with courtesy and helpful
advice, in spite of serially repeating the behaviour." | | 3:05p |
Security advisories for Thursday Arch Linux has updated bugzilla
(privilege escalation).
openSUSE has updated IPython,
(cross-site scripting).
SUSE has updated php5 (SLE11SP2:
three vulnerabilities). | | 9:17p |
Gräßlin: September update for Plasma’s Wayland porting On his blog, Martin Gräßlin has posted an update on porting KDE's Plasma desktop to Wayland. There has been progress in various areas, including transient window positioning (which makes menus appear at the right location), Plasma/KWin specific extensions, support for multiple X servers, and support for "KWin in the cloud": " So on Friday I decided to dedicate my development time on a virtual framebuffer backend. This backend (to start use kwin_wayland --xwayland --virtual) doesn’t render to any device, but only “simulates” rendering by using a QImage which then isn’t used at all. Well not completely true: there is an environment variable to force the backend to store each rendered frame into a temporary directory.
Why is such a virtual backend so exiting? Well it means we can run KWin anywhere. We are not bound to any hardware restrictions like screen attached or screen resolution. With other words we can run it on servers – in the cloud. The first such instance runs on our CI [continuous integration] servers in the form of an automated integration test. And in future there will be much more such tests." |
|