[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 Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1890772 Title: No signal on 4K 60Hz DisplayPort monitor by default, until

[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 Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1890772 Title: No signal on 4K 60Hz DisplayPort monitor by

[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

[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
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

[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

[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 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

[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

[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
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)

[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 Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1890772 Title: No signal on 4K 60Hz DisplayPort monitor by default, until "max bpc" is

[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 Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1890772 Title: No signal on 4K 60Hz DisplayPort monitor by default,

[Bug 1882885] Re: FP Auth enroll for Multi user Scenario

2020-07-13 Thread Alex Tu
I just follow your instructions on XPS 9300 with goodix fingerprint driver. `apt-get update; apt-get dist-upgrade -y; apt-get install -y  libfprint-2-tod1-goodix` (there's an online update is on-going, after that, libfprint-2-tod1-goodix will be installed automatically) But I can not reproduce

[Bug 1882885] Re: FP Auth enroll for Multi user Scenario

2020-07-13 Thread Alex Tu
also attached the logs from oem-getlogs from apport package. ** Attachment added: "oemlogs-u-XPS-13-9300-20200713183746+0800.apport.gz" https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1882885/+attachment/5392305/+files/oemlogs-u-XPS-13-9300-20200713183746+0800.apport.gz

[Bug 1882885] Re: FP Auth enroll for Multi user Scenario

2020-07-13 Thread Alex Tu
also attached the logs from oem-getlogs from apport package. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1882885 Title: FP Auth enroll for Multi user Scenario To

[Bug 1885673] [NEW] won't auto-select input when headset is plugged and selected in pop-up window

2020-06-30 Thread Alex Tu
Public bug reported: Step to reproduce: 1. plug-in headset 2. select headset in pop-up window. 3. check g-c-c Expected result: correct input is selected so that mic on the headset just works Actual result: The correct input is not selected. a patch is there waiting for upstream review :

[Bug 1865845] Re: No UI indication for more than 10 fingerprint enrolling progress

2020-06-10 Thread Alex Tu
** Changed in: oem-priority Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1865845 Title: No UI indication for more than 10

[Bug 1865838] Re: no error displayed on failed fingerprint authentification

2020-06-04 Thread Alex Tu
** Tags added: oem-priority originate-from-1880064 somerville -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1865838 Title: no error displayed on failed fingerprint authentification

[Bug 1865838] Re: no error displayed on failed fingerprint authentification

2020-06-04 Thread Alex Tu
** Changed in: oem-priority Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1865838 Title: no error displayed on failed fingerprint authentification

[Bug 1879247] [NEW] not yet support goodix fingerprint [27C6:538D]

2020-05-18 Thread Alex Tu
Public bug reported: it's waiting IHV driver ready. both proprietary driver and open-sourced driver not support this device yet. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libfprint-2-tod1 1:1.90.1+tod1-0ubuntu4 ProcVersionSignature: Ubuntu 5.6.0-1010.10+lp1876707-oem 5.6.10 Uname:

[Bug 1869571] Re: Vertical dual monitor setup with main monitor on bottom causes overview to only use one eighth of screen

2020-04-14 Thread Alex Tu
** Also affects: oem-priority Importance: Undecided Status: New ** Changed in: oem-priority Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.

[Bug 1865845] Re: No UI indication for fingerprint enrolling progress

2020-03-12 Thread Alex Tu
after IHV changed the driver, the UI indication shows during enrollment. It caused by the driver holding signals untile enrollment done. But there's still an issue that will confuse the user that IHV driver asks for 12 enrollments but the MAX_ENROLL_STAGES is 10. This means the UI indication of

[Bug 1865838] Re: no error displayed on failed fingerprint authentification

2020-03-10 Thread Alex Tu
This issue can also be reproduced on Lenovo X240 which is using open source FPT driver [1] for FP device 138a:0017 Validity VFS5011. [1] https://fprint.freedesktop.org/supported-devices.html -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is

[Bug 1865845] Re: No UI indication for fingerprint enrolling progress

2020-03-10 Thread Alex Tu
from the latest IHV driver, it seems the requested enroll stage (12) exceeds MAX_ENROLL_STAGES (10). I'm trying to extend MAX_ENROLL_STAGES but it seems still failed. It's puzzle to me for now that who provided the 12 times requesting and why it failed to exceed MAX_ENROLL_STAGES. ** Attachment

[Bug 1865845] Re: No UI indication for fingerprint enrolling progress

2020-03-10 Thread Alex Tu
** Attachment added: "journalctl.log" https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1865845/+attachment/5335240/+files/journalctl.log -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in

[Bug 1865838] Re: no error displayed on failed fingerprint authentification

2020-03-04 Thread Alex Tu
sorry, I wanted to track the progress by "OEM Priority Project" and assigned myself in the wrong series. ** Changed in: gdm3 (Ubuntu) Assignee: Alex Tu (alextu) => (unassigned) ** Changed in: oem-priority Assignee: (unassigned) => Alex Tu (alextu) -- You r

[Bug 1865845] Re: No UI indication for fingerprint enrolling progress

2020-03-04 Thread Alex Tu
I just also verified on Lenovo X230 with fingerprint device 147e:2020 the UI indication for fingerprint enrolling progress looks good. So, I'm wondering if the issue is caused by private built IHV proprietary driver + libfprintd pkgs. I will check it again while get the latest IHV driver which

[Bug 1865845] Re: no fingerprint enrolling progress information

2020-03-03 Thread Alex Tu
after user click 'Next', there is no message remind user the progress of fingerprint enrollment. And also no reminder for the necessary of 12 times finger pressing. ** Attachment added: "Screenshot from 2020-03-03 11-13-25.png"

[Bug 1865845] Re: no fingerprint enrolling progress information

2020-03-03 Thread Alex Tu
user page in setting failed forever after fingerprint enrolling time out. ** Attachment added: "Screenshot from 2020-03-03 16-49-54.png" https://bugs.launchpad.net/oem-priority/+bug/1865845/+attachment/5332968/+files/Screenshot%20from%202020-03-03%2016-49-54.png -- You received this bug

[Bug 1865845] [NEW] no fingerprint enrolling progress information

2020-03-03 Thread Alex Tu
LTS "Focal Fossa" - Alpha amd64 (20200301) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: oem-priority Importance: Undecided Assignee: Alex Tu (alextu) Status: New ** Affects: gnome-control-cent

[Bug 1865838] Re: no error popup while exceed maximal fingerprint retry during login

2020-03-03 Thread Alex Tu
the message in journalctl shows that fprintd and gdm-fingerprint know user is trying on incorrect finger. https://paste.ubuntu.com/p/QkySMYzVmC/ -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu.

[Bug 1865838] [NEW] no error popup while exceed maximal fingerprint retry during login

2020-03-03 Thread Alex Tu
Importance: Undecided Status: New ** Affects: gdm3 (Ubuntu) Importance: Undecided Assignee: Alex Tu (alextu) Status: New ** Tags: amd64 apport-bug focal third-party-packages ** Also affects: oem-priority Importance: Undecided Status: New ** Changed in: gd

[Bug 1844650] Re: No authentication window pops up if thunderbolt device be plugged before booting

2019-10-15 Thread Alex Tu
t.log" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1844650/+attachment/5297329/+files/journalctl-boot-with-tbt.log ** Changed in: oem-priority Assignee: Alex Tu (alextu) => Che Cheng (cktenn) -- You received this bug notification because you are a member of Ubuntu

[Bug 1844650] Re: No authentication window pops up if thunderbolt device be plugged before booting

2019-10-15 Thread Alex Tu
this is the correct behavior that plugs an unauthenticated TBT device after user logout (before login) The message I feel useful is: 十 15 18:07:55 u-Precision-7530 boltd[1198]: [00547989-414f-Thunderbolt Dock ] device added

[Bug 1821194] Re: [nvidia] Screen frozen after switch to other tty and do login & logout

2019-03-22 Thread Alex Tu
** Also affects: oem-priority Importance: Undecided Status: New ** Changed in: oem-priority Assignee: (unassigned) => Cyrus Lien (cyruslien) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.

[Bug 1772811] Re: different behaviors for switch display mode between xenial and bionic

2019-01-06 Thread Alex Tu
@Daniel, Because this issue is for bionic,do we have schedule to back port it to bionic? -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1772811 Title: different behaviors for

[Bug 1777099] [NEW] [backport] DRM devices opened by logind stay referenced indefinitely by PID 1

2018-06-15 Thread Alex Tu
Public bug reported: refer to https://github.com/systemd/systemd/issues/6908 we need that solution to make NVIDIA dGPU switching works. impacted issue: https://bugs.launchpad.net/somerville/+bug/1774326 ** Affects: oem-priority Importance: Undecided Status: New ** Affects:

[Bug 1582496] Re: GLib-GObject-CRITICAL failures during Ubuntu 16.04 bootup

2016-12-11 Thread Alex Tu
I get the similar message, but have different issue here. http://paste.ubuntu.com/23617526/ gnome-session-binary[9336]: GLib-GObject-CRITICAL: g_object_unref: assertion 'G_ IS_OBJECT (object)' failed The issue here is that it need to wait minutes after clicking "log out" on the menu panel. It's