On 01/08/18, Andrey Vihrov via arch-general wrote:
> Hi,
>
> Recently the way kernel sources are retrieved was changed in the linux
> package [1]. Now the sources are fetched from
> https://github.com/archlinux/linux.
>
> I see a few problems with this:
>
> - Previously the list of applied patch
On 08/01, Andrey Vihrov via arch-general wrote:
> - Previously the list of applied patches was very transparent. You could
> immediately see that the kernel and kernel patch tarballs come from
> kernel.org, and view individual extra patches. Now the code comes from a
> non-kernel source, and cannot
Hi,
Recently the way kernel sources are retrieved was changed in the linux
package [1]. Now the sources are fetched from
https://github.com/archlinux/linux.
I see a few problems with this:
- Previously the list of applied patches was very transparent. You could
immediately see that the kernel an
On 2018-06-30 13:55:18 (+0200), Tinu Weber wrote:
> On Sat, Jun 30, 2018 at 13:34:11 +0200, Bjoern Franke wrote:
> > > Are you truly logged in as this second user for whom it does not work,
> > > or just su(1)'d, etc?
> >
> > Erm, just used "sudo -u user2 -s" to login as user2. I assumed spawning
> I was able to get that working using my numbers for the Dell 30" 3008WFP
>
> xrandr --dpi 220 --fb 8960x5360 \
> --output eDP1 --mode 3840x2160 --pos 5120x0 \
> --output DP1 --scale 2x2 --pos 0x0 --panning 5120x3200+3840+0
I made a mistake there that should have been:
xrandr --dpi 276
>> https://phabricator.kde.org/D12405#251159
>
>> graesslin.Apr 21 2018, 7:01 PM
>> I also cannot imagine this to work due to the fact how X11 works. There is
>> just no mapping from window to screen. No window can know on which screen it
>> is. Not even KWin knows that as the window manager (sc
Hi Tyler,
I did a lot of experimenting a while back to find something that works well
for me. I have a MacBook Pro with a HiDPI screen connected to two 1080p
external monitors via ThunderBolt-to-DisplayPort adapters. I place my
MacBook Pro to the right of the two external monitors. I also run i3.
Am 30.07.2018 um 18:51 schrieb srai...@delta-info.com:
Am 30.07.2018 um 15:36 schrieb Shawn Rainey:
Am 22.07.2018 um 11:27 schrieb Peter Nabbefeld:
Hello,
I've updated my installation yesterday, also doing an update of the
Linux kernel to 4.17.8. When starting this morning, kernel modules
rej
> https://phabricator.kde.org/D12405#251159
> graesslin.Apr 21 2018, 7:01 PM
> I also cannot imagine this to work due to the fact how X11 works. There is
> just no mapping from window to screen. No window can know on which screen it
> is. Not even KWin knows that as the window manager (screen is
Le 01/08/2018 à 14:27, Tyler a écrit :
>> The separator is a ; not a comma. ;) And it is likely {E,}DP-1, not
>> {E,}DP1. And you probably have to use quotes around the whole value,
>> like this:
>>
>> QT_SCREEN_SCALE_FACTORS="eDP-1=2;DP-1=1;HDMI-1=1;DP-2=1;HDMI-2=1;"
> Hmm sadly, it doesn't seem
Hi Tyler,
> $ export QT_SCREEN_SCALE_FACTORS=eDP1=2;DP1=1
> $ env |grep QT_SCREEN_SCALE_FACTOR
> QT_SCREEN_SCALE_FACTORS=eDP1=2
>
> seems DP1=1 lost it's setting.
Others have pointed out the flaw, but to investigate next time,
`set -x' is useful.
$ set -x
$ export QT_SCREEN_SCALE_FACTORS
> The separator is a ; not a comma. ;) And it is likely {E,}DP-1, not
> {E,}DP1. And you probably have to use quotes around the whole value,
> like this:
>
> QT_SCREEN_SCALE_FACTORS="eDP-1=2;DP-1=1;HDMI-1=1;DP-2=1;HDMI-2=1;"
Hmm sadly, it doesn't seem to help.
$ env |grep QT
QT_SCREEN_SCALE_FACT
Le 01/08/2018 à 14:11, Tyler a écrit :
>> On Wed, Aug 1, 2018 at 1:58 PM, Tyler wrote:
>>
Try setting the QT_SCREEN_SCALE_FACTORS per display like this for
>>> instance:
QT_SCREEN_SCALE_FACTORS=eDP-1=2;DP-1=1;HDMI-1=1;DP-2=1;HDMI-2=1;
>>> I didn't even know that was possible.
>>>
>>> I
>
> On Wed, Aug 1, 2018 at 1:58 PM, Tyler wrote:
>
>> > Try setting the QT_SCREEN_SCALE_FACTORS per display like this for
>> instance:
>> > QT_SCREEN_SCALE_FACTORS=eDP-1=2;DP-1=1;HDMI-1=1;DP-2=1;HDMI-2=1;
>>
>> I didn't even know that was possible.
>>
>> I tried with: QT_SCREEN_SCALE_FACTORS=eDP
Le 01/08/2018 à 13:58, Tyler a écrit :
>> Try setting the QT_SCREEN_SCALE_FACTORS per display like this for instance:
>> QT_SCREEN_SCALE_FACTORS=eDP-1=2;DP-1=1;HDMI-1=1;DP-2=1;HDMI-2=1;
> I didn't even know that was possible.
>
> I tried with: QT_SCREEN_SCALE_FACTORS=eDP1=2,DP1=1 to test but I am
Tyler,
On Wed, Aug 1, 2018 at 1:58 PM, Tyler wrote:
> > Try setting the QT_SCREEN_SCALE_FACTORS per display like this for
> instance:
> > QT_SCREEN_SCALE_FACTORS=eDP-1=2;DP-1=1;HDMI-1=1;DP-2=1;HDMI-2=1;
>
> I didn't even know that was possible.
>
> I tried with: QT_SCREEN_SCALE_FACTORS=eDP1=2,DP
> Try setting the QT_SCREEN_SCALE_FACTORS per display like this for instance:
> QT_SCREEN_SCALE_FACTORS=eDP-1=2;DP-1=1;HDMI-1=1;DP-2=1;HDMI-2=1;
I didn't even know that was possible.
I tried with: QT_SCREEN_SCALE_FACTORS=eDP1=2,DP1=1 to test but I am
noticing it seems to be truncating to when I l
Le 01/08/2018 à 12:00, Tyler a écrit :
>> Second, switching back and forth between dual monitors to one monitor lead
>> to interesting behaviour. For example, I kept losing the scale setting on
>> the lower DPI monitor.
> that's not exactly what is happening to me - because GTK2/3 works fine.
>
Am 01.08.2018 um 12:28 schrieb Khorne:
On Wed, 1 Aug 2018 12:15:46 +0200
Peter Nabbefeld wrote:
Hello,
I've got some pulseaudio problems which I'd like to solve.
Unfortunately, if I kill pulseaudio, it is sonn started again, so I
cannot give it a log level. :-/
Where do I find the "automati
On Wed, 1 Aug 2018 12:15:46 +0200
Peter Nabbefeld wrote:
> Hello,
>
> I've got some pulseaudio problems which I'd like to solve.
> Unfortunately, if I kill pulseaudio, it is sonn started again, so I
> cannot give it a log level. :-/
>
> Where do I find the "automatic restart", i.e. how can I
On 01-08-18 12:15:46 +0200, Peter Nabbefeld wrote:
Hello,
I've got some pulseaudio problems which I'd like to solve.
Unfortunately, if I kill pulseaudio, it is sonn started again, so I
cannot give it a log level. :-/
It is socket activated, so you have to disable “pulseaudio.socket” as
well
Hello,
I've got some pulseaudio problems which I'd like to solve.
Unfortunately, if I kill pulseaudio, it is sonn started again, so I
cannot give it a log level. :-/
Where do I find the "automatic restart", i.e. how can I stop it?
Kind regards
Peter
> I guess --right-of/--left-of don't take the scale into account.
> Try to position your monitors absolutely with --pos, probably 0x0 for
> DP1 and 5120x0 for eDP1.
xrandr --dpi 220 --output eDP1 --pos 5120x0 --auto \
--output DP1 --pos 0x0 --auto --scale 2x2
https://i.imgur.com/pwcGct2.j
I also tried doing
xrandr --dpi 220 --output eDP1 --auto --output DP1 --auto --scale 2x2
--right-of DP1
but it resulted in:
xrandr: loop in relative position specifications
what I am trying to achieve (produced in gimp):
https://i.imgur.com/J83Fplt.jpg
As for moving to sway, doesn't look lik
Am 01.08.2018 um 04:20 schrieb Tyler:
When I tried the reverse
xrandr --output eDP1 --auto --output DP1 --auto --scale 2x2 --left-of eDP1
I didn't just get a flipped result, I got my browser showing over the
middle https://i.imgur.com/QW0IHYw.jpg
I guess --right-of/--left-of don't take the s
25 matches
Mail list logo
