[Bug 1732999] Re: xrandr relative positioning does not take into account the --scale parameter
> xrandr --version xrandr program version 1.5.0 Server reports RandR version 1.5 ** Package changed: xorg-server (Ubuntu) => xrandr (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1732999 Title: xrandr relative positioning does not take into account the --scale parameter To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xrandr/+bug/1732999/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1732999] [NEW] xrandr relative positioning does not take into account the --scale parameter
Public bug reported: assuming I have 2 displays, eDP1(3840x2160) and DP1-1(1920x1200), and I want DP1-1 placed to the left of eDP1 while scaling it 2x2... xrandr --output eDP1 --auto --output DP1-1 --auto --scale 2x2 --left-of eDP1 after running the above command, eDP1 ends up having a pos of 1920x0 but DP1-1 ends up with a scaled resolution of 3840x2400, which causes half of it's screen area to be displayed on eDP1, overwriting half of eDP1's screen. I have also reproduced this behavior with --scale-from instead of --scale. I think that the pos of eDP1 in this case should end up at 3840x0, otherwise the utility of the ease of use operators like --right-of, --left-of, --above, etc is zero when used in conjunction with --scale or --scale-from. ** Affects: xorg-server (Ubuntu) Importance: Undecided Status: New ** Tags: xrandr -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1732999 Title: xrandr relative positioning does not take into account the --scale parameter To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1732999/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1365672] Re: A recent firmware update made ath9k_htc card cause kernel panic/freeze
FYI, a change was reverted in ath9k_htc and in 3.17 stable this issue no longer occurs. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1365672 Title: A recent firmware update made ath9k_htc card cause kernel panic/freeze To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1365672/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1365672] Re: A recent firmware update made ath9k_htc card cause kernel panic/freeze
I am also seeing this same issue with a TL-WN722N, it uses the same ath9k_htc driver. I am running ubuntu 14.04 with the 3.17-rc5 kernel and latest 14.10 firmware. Attached is my kern.log containing at least one instance of this crash from 3.17-rc4.(grep for oops =)). I've also seen this crash in rc5 but strangely it's not showing up in the kernel log. Most likely the watchdog didn't catch it in time. ** Attachment added: Kernel log from incidents on 3.17-rc4 https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1365672/+attachment/4204127/+files/kern.log.1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1365672 Title: A recent firmware update made ath9k_htc card cause kernel panic/freeze To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1365672/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
