[Ubuntu-x-swat] [Bug 1627620] [NEW] single touch vertical scrolling failed

2016-09-26 Thread Alex Tu
Public bug reported: Single touch vertical scrolling on right edge failed but success in horizontal scrolling on bottom edge. The way to reproduce this issue is 1. un-click "two finger scroll" and "natural scrolling" in "Mouse & Touchpad" setting 2. open libreOffice Calc 3. touch the touchpad by

[Ubuntu-x-swat] [Bug 1627674] [NEW] single touch vertical scrolling failed

2016-09-26 Thread Alex Tu
Public bug reported: Single touch vertical scrolling on right edge failed but success in horizontal scrolling on bottom edge. The way to reproduce this issue is 1. un-click "two finger scroll" and "natural scrolling" in "Mouse & Touchpad" setting 2. open libreOffice Calc 3. touch the touchpad by

[Ubuntu-x-swat] [Bug 1627620] Re: single touch vertical scrolling failed

2016-09-26 Thread Alex Tu
*** This bug is a duplicate of bug 1627674 *** https://bugs.launchpad.net/bugs/1627674 ** This bug has been marked a duplicate of bug 1627674 single touch vertical scrolling failed -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-x

[Ubuntu-x-swat] [Bug 1890772] Re: No signal on 4K 60Hz DisplayPort monitor by default, until "max bpc" is lowered to 8

2020-08-11 Thread Alex Tu
** Tags added: oem-priority originate-from-1886778 somerville -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1890772 Title: No signal on 4K 60Hz DisplayPort monitor by default, until "max

[Ubuntu-x-swat] [Bug 1890772] Re: No signal on 4K 60Hz DisplayPort monitor by default, until "max bpc" is lowered to 8

2020-08-11 Thread Alex Tu
** Tags added: originate-from-1887915 -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1890772 Title: No signal on 4K 60Hz DisplayPort monitor by default, until "max bpc" is lowered to 8

[Ubuntu-x-swat] [Bug 1890772] Re: No signal on 4K 60Hz DisplayPort monitor by default, until "max bpc" is lowered to 8

2020-08-23 Thread Alex Tu
I think different from #32. To adding a GUI configure bpc is a long-term plan. Before that,the default behavior should be designed to get the best user experience. As we all know, there're lot of hardware components on the pipline of display path(e.g. socket, converter, dongle, cable, monitor)

[Ubuntu-x-swat] [Bug 1890772] Re: No signal on 4K 60Hz DisplayPort monitor by default, until "max bpc" is lowered to 8

2020-08-24 Thread Alex Tu
Thanks for understanding. There's an upstream bug discussing this similar issue, we can follow their effort there. https://gitlab.freedesktop.org/drm/intel/-/issues/1890 ** Bug watch added: gitlab.freedesktop.org/drm/intel/-/issues #1890 https://gitlab.freedesktop.org/drm/intel/-/issues/1890

[Ubuntu-x-swat] [Bug 1890772] Re: No signal on 4K 60Hz DisplayPort monitor by default, until "max bpc" is lowered to 8

2020-08-25 Thread Alex Tu
** Bug watch added: gitlab.gnome.org/GNOME/gnome-control-center/-/issues #1108 https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/1108 ** Also affects: xorg-server via https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/1108 Importance: Unknown Status: Unknown -

[Ubuntu-x-swat] [Bug 1890772] Re: No signal on 4K 60Hz DisplayPort monitor by default, until "max bpc" is lowered to 8

2020-08-25 Thread Alex Tu
** Bug watch added: gitlab.freedesktop.org/xorg/xserver/-/issues #1066 https://gitlab.freedesktop.org/xorg/xserver/-/issues/1066 ** Also affects: xorg-server via https://gitlab.freedesktop.org/xorg/xserver/-/issues/1066 Importance: Unknown Status: Unknown -- You received this bug

[Ubuntu-x-swat] [Bug 1890772] Re: No signal on 4K 60Hz DisplayPort monitor by default, until "max bpc" is lowered to 8

2020-08-25 Thread Alex Tu
I afraid we can not just trust (EDID_version >= 1.4 && EDID_supports_10bit). Because this issue caused by any problematic component in the middle of pipeline. To ensure the compatibility, better to just defautly set bpc=8. Think of one scenario, a speaker get his Ubuntu machine onto stage, plug th

[Ubuntu-x-swat] [Bug 1890772] Re: No signal on 4K 60Hz DisplayPort monitor by default, until "max bpc" is lowered to 8

2020-08-26 Thread Alex Tu
according to #40 and conversation on mattermost with Kai-Heng. HWE is planning to add quirk for the faulty dongles so that the dark screen during boot time[1] can be fixed. [1] https://gitlab.freedesktop.org/drm/intel/-/issues/1890 -- You received this bug notification because you are a member

[Ubuntu-x-swat] [Bug 1890772] Re: No signal on 4K 60Hz DisplayPort monitor by default, until "max bpc" is lowered to 8

2020-08-27 Thread Alex Tu
reply to #39, yes it's a trade off that we don't either want user get darkscreen when then randomly plug display port for case like #38 or user get lower bpc on their working display port. So far, there seems no solid way to make sure both requirement. -- You received this bug notification

[Ubuntu-x-swat] [Bug 1890772] Re: No signal on 4K 60Hz DisplayPort monitor by default, until "max bpc" is lowered to 8

2020-08-27 Thread Alex Tu
** Also affects: hwe-next Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1890772 Title: No signal on 4K 60Hz DisplayPort monitor by default, un

[Ubuntu-x-swat] [Bug 1890772] Re: No signal on 4K 60Hz DisplayPort monitor by default, until "max bpc" is lowered to 8

2020-09-02 Thread Alex Tu
** Changed in: oem-priority Importance: High => Critical -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1890772 Title: No signal on 4K 60Hz DisplayPort monitor by default, until "max b

[Ubuntu-x-swat] [Bug 1915003] Re: Always update the initramfs when changing power profile

2021-02-08 Thread Alex Tu
** Also affects: nvidia-drivers-ubuntu Importance: Undecided Status: New ** Also affects: oem-priority Importance: Undecided Status: New ** Changed in: oem-priority Assignee: (unassigned) => Alex Tu (alextu) ** Changed in: oem-priority Importance: Undeci

[Ubuntu-x-swat] [Bug 1915003] Re: SRU: Always update the initramfs when changing power profile

2021-02-21 Thread Alex Tu
# verified pass on focal: ## package version as expected. ubuntu@dell-bto-focal-fossa-nvstaging-202005-27873:~$ apt list ubuntu-drivers-common nvidia-prime Listing... Done nvidia-prime/focal-proposed,focal-proposed,now 0.8.16~0.20.04.1 all [installed,automatic] ubuntu-drivers-common/focal-update

[Ubuntu-x-swat] [Bug 1915003] Re: SRU: Always update the initramfs when changing power profile

2021-02-21 Thread Alex Tu
# suggestion: On nvidia settings UI, there's no message saying it's building initrd after user select on-demand mode. So, the nvidia settings looks like just hangs up when it's building initrd. If user have multiple kernel before selecting on-demand, user might be confused and treat it as nvidia

[Ubuntu-x-swat] [Bug 1715586] Re: Fix shrinking behavior in rrCheckPixmapBounding

2017-10-12 Thread Alex Tu
with AOC monitor, it issued an unexpected acpi event after external monitor be disabled, that caused mode switching. u@u-Vostro-7570:~$ sudo acpi_listen # now disable external screen by $DISPLAY=:0 xrandr --output HDMI-0 --off jack/lineout LINEOUT unplug jack/videoout VIDEOOUT unplug # wait

[Ubuntu-x-swat] [Bug 1714178] Re: Triple monitor display failed with Dell Dock (HiDPI) (modesetting)

2017-12-07 Thread Alex Tu
verified kernel 4.15-rc2 with this patch, 3 X 4K works well. https://patchwork.kernel.org/patch/10097883/ -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1714178 Title: Triple monitor disp

[Ubuntu-x-swat] [Bug 1918855] Re: Xorg xserver got signal 6 to abort

2021-06-22 Thread Alex Tu
** Changed in: oem-priority Assignee: Andy Chi (andch) => jeremyszu (os369510) -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1918855 Title: Xorg xserver got signal 6 to abort To manage no

[Ubuntu-x-swat] [Bug 1952083] Re: Add support for Beige Goby

2021-11-26 Thread Alex Tu
** Also affects: oem-priority Importance: Undecided Status: New ** Changed in: oem-priority Importance: Undecided => Critical ** Changed in: oem-priority Assignee: (unassigned) => Yuan-Chen Cheng (ycheng-twn) -- You received this bug notification because you are a member of Ub

[Ubuntu-x-swat] [Bug 1952083] Re: Add support for Beige Goby

2021-11-26 Thread Alex Tu
** Tags added: oem-priority originate-from-1947372 somerville ** Tags added: originate-from-1948411 -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1952083 Title: Add support for Beige Goby To

[Ubuntu-x-swat] [Bug 1837683] [NEW] Xorg freeze

2019-07-23 Thread Alex Tu
Public bug reported: environment: - XPS-13-938 - connect 5G ac wifi - disabled suspend in power setting - disabled blank screen in power setting steps: - play 4k video by chrome on youtube[1] overnight symptom: - after about 8 hours, the screen is black and keyboard and mouse can not wake

Re: [Ubuntu-x-swat] [Bug 1837683] Re: Screen stops updating after about 8 hours - (EE) modeset(0): present flip failed

2019-07-23 Thread Alex Tu
1. When the problem is happening, does the kernel log show any problems? (run: dmesg) When the problem is happening, the screen is black, so no easy to type command. I can try ssh before reproducing, but might not soon, I need to handover this machine to another guy today. Before that, can you ge

[Ubuntu-x-swat] [Bug 1837683] Re: Screen stops updating after about 8 hours - (EE) modeset(0): present flip failed

2019-07-23 Thread Alex Tu
** Attachment added: "syslog.no-screen-after-4k-overnight.tar.gz" https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1837683/+attachment/5278844/+files/syslog.no-screen-after-4k-overnight.tar.gz -- You received this bug notification because you are a member of Ubuntu-X, which is subsc

[Ubuntu-x-swat] [Bug 1837683] Re: Screen stops updating after about 8 hours - (EE) modeset(0): present flip failed

2019-07-23 Thread Alex Tu
not see much fishy message in kerne.log, the only message around the time of issue happened is: " Jul 24 01:25:24 u-XPS-13-9380 kernel: [ 2201.963876] [drm] Reducing the compressed framebuffer size. This may lead to less power savings than a non-reduced-size. Try to increase stolen memory size i

[Ubuntu-x-swat] [Bug 1837683] Re: Screen stops updating after about 8 hours - (EE) modeset(0): present flip failed

2019-07-23 Thread Alex Tu
collect some public bugs which look similar to this one: - https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1821059 - https://uwot.eu/blog/xorg-present-flip-failed/ -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu

Re: [Ubuntu-x-swat] [Bug 1837683] Re: Screen stops updating after about 8 hours - (EE) modeset(0): present flip failed

2019-07-24 Thread Alex Tu
The original 8 hour test without external monitor. I removed all wired connection before testing. Kai-Heng Feng 於 2019年7月24日 週三 下午4:00 寫道: > Please test latest mainline kernel: > https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.3-rc1/ > > -- > You received this bug notification because you are

[Ubuntu-x-swat] [Bug 1844933] [NEW] screen jitter after long idle

2019-09-22 Thread Alex Tu
Public bug reported: It's 1st time happens on my xps13 9380 with bionic + oem kernel 4.15.0-1056-oem. I have updated to 1056 from 1050 for several days, this issue not happens for these days and not experienced it on 1050 as well. So, looks it's just randomly happens or I can not find a static w

[Ubuntu-x-swat] [Bug 1844932] [NEW] screen jitter after long idle

2019-09-22 Thread Alex Tu
Public bug reported: It's 1st time happens on my xps13 9380 with bionic + oem kernel 4.15.0-1056-oem. I have updated to 1056 from 1050 for several days, this issue not happens for these days and not experienced it on 1050 as well. So, looks it's just randomly happens or I can not find a static w

[Ubuntu-x-swat] [Bug 1844934] [NEW] screen jitter after long idle

2019-09-22 Thread Alex Tu
Public bug reported: It's 1st time happens on my xps13 9380 with bionic + oem kernel 4.15.0-1056-oem. I have updated to 1056 from 1050 for several days, this issue not happens for these days and not experienced it on 1050 as well. So, looks it's just randomly happens or I can not find a static w

[Ubuntu-x-swat] [Bug 1844934] Re: screen jitter after long idle

2019-09-22 Thread Alex Tu
from journalctl , it keep print error message ** Tags added: ubuntu-certified ** Tags added: ce-qa-concern -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1844934 Title: screen jitter after lon

[Ubuntu-x-swat] [Bug 1844934] Re: screen jitter after long idle

2019-09-22 Thread Alex Tu
the video when issue happens ** Attachment added: "t_video6068977879478174032.mp4" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1844934/+attachment/5290451/+files/t_video6068977879478174032.mp4 -- You received this bug notification because you are a member of Ubuntu-X, which is subscr

[Ubuntu-x-swat] [Bug 1844934] Re: screen jitter after long idle

2019-09-22 Thread Alex Tu
Changed in: oem-priority Assignee: (unassigned) => Alex Tu (alextu) ** Changed in: oem-priority Importance: Undecided => High ** Changed in: oem-priority Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu-X, which is subscribe

[Ubuntu-x-swat] [Bug 1844934] Re: screen jitter after long idle

2019-09-22 Thread Alex Tu
from the apt history log, it looks not something fishy as well. BTW, the only package I installed these 2 days is multipass snap package. I use it to run a bionc VM to test TLP behavior. ** Attachment added: "history.log" https://bugs.launchpad.net/oem-priority/+bug/1844934/+attachment/529047

[Ubuntu-x-swat] [Bug 1844934] Re: screen jitter after long idle

2019-09-22 Thread Alex Tu
** Attachment added: "snap.list" https://bugs.launchpad.net/oem-priority/+bug/1844934/+attachment/5290476/+files/snap.list -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1844934 Title: scree

[Ubuntu-x-swat] [Bug 1844934] Re: screen jitter after long idle

2019-09-22 Thread Alex Tu
btw, as record. After reboot of this issue. I also updated BIOS by fwupd to make sure every thing is updated to date for following debugging. $ fwupdmgr get-updates No upgrades for XPS 13 9380 System Firmware, current is 0.1.7.0: 0.1.7.0=same, 0.1.6.0=older, 0.1.5.0=older, 0.1.4.0=older, 0.1.3.2=

[Ubuntu-x-swat] [Bug 1872788] Re: super key searching show incomplete icon

2020-04-14 Thread Alex Tu
** Attachment added: "2020-04-15_01-41.png" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1872788/+attachment/5354040/+files/2020-04-15_01-41.png -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net

[Ubuntu-x-swat] [Bug 1872788] [NEW] super key searching show incomplete icon

2020-04-14 Thread Alex Tu
Public bug reported: compare to bionic, bionic will show complete icon when I press super key and type prefix of application. But in Focal, the icon is incomplete as attache screenshot. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.6.0