Now checking out [Wayland compositors][1]. Thing is that on different
virtual desktops I need different resolution, and I was told that
Wayland would handle resolution changes better than X.
[1]: http://en.wikipedia.org/wiki/List_of_display_servers#Wayland
For example, I want to specify that the title bar should be 5mm tall.
On 2015-03-30 13:08:11, Alfredo Palhares wrote:
Any ideas how can I debug this problem further ?
Have a look at X's logfile, /var/log/Xorg.log. There should be messages that
say the modes
are being removed, and why (not enough Vram, some parameter out of range,
etc.). It's likely
warning or
Hello fellow Arch users,
Suddenly I cannot use my external monitor in the 1920x1080 mode, I add
the following script that run every time I connect my thinkpad to the
base:
```
#!/bin/bash
set -x
xrandr --output DP2-3 --mode 1920x1080 --right-of eDP1
xset m 1/2 1
```
And after a update (I
On Mon, Mar 30, 2015 at 3:29 PM, Felix E. Klee felix.k...@inka.de wrote:
Wayland would handle resolution changes better than X.
Or rather the compositor could zoom the entire desktop.
I' ve tried downgrade gcc, gcc-libs to version 4.9.2, but a new error
occurred:
/usr/include/boost/python/proxy.hpp:94:36: internal compiler error:
Segmentation fault
inline void proxyPolicies::del() const
Is this another bug of boost?
On Sat, Mar 28, 2015 at 6:18 AM Zander B lez...@gmail.com
On 30/03/15 10:54 PM, 施不二 wrote:
I' ve tried downgrade gcc, gcc-libs to version 4.9.2, but a new error
occurred:
/usr/include/boost/python/proxy.hpp:94:36: internal compiler error:
Segmentation fault
inline void proxyPolicies::del() const
Is this another bug of boost?
An ICE (internal
7 matches
Mail list logo
