[Bug 2084015] Re: gnome-shell has no response when plug-in unauthorized thunderbolt devices

2024-10-10 Thread hugh chao
even enabled gnome verbose log, there is not much hint, but I do observe there is a gdbug segfault as below: Oct 10 18:09:08 u kernel: thunderbolt 1-0:1.1: new retimer found, vendor=0x8087 device=0xd9c Oct 10 18:09:08 u kernel: usb 3-1: new high-speed USB device number 10 using xhci_hcd Oct 10 1

[Bug 2084015] Re: gnome-shell has no response when plug-in unauthorized thunderbolt devices

2024-10-10 Thread hugh chao
upload the log as #17 ** Attachment added: "gslog.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2084015/+attachment/5826690/+files/gslog.txt -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.

[Bug 2084015] Re: gnome-shell has no response when plug-in unauthorized thunderbolt devices

2024-10-10 Thread hugh chao
For #16 Yes as below steps 1. u@u:~$ gnome-extensions list d...@rastersoft.com tiling-assist...@ubuntu.com ubuntu-appindicat...@ubuntu.com ubuntu-d...@ubuntu.com u@u:~$ gnome-extensions disable d...@rastersoft.com u@u:~$ gnome-extensions disable tiling-assist...@ubuntu.com u@u:~$ gnome-extensions

[Bug 2084015] Re: gnome-shell has no response when plug-in unauthorized thunderbolt devices

2024-10-10 Thread hugh chao
You mean only the laptop screen is attached? > Yes. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2084015 Title: gnome-shell has no response when plug-in unauthorized thunderb

[Bug 2084015] Re: gnome-shell has no response when plug-in unauthorized thunderbolt devices

2024-10-09 Thread hugh chao
and not sure this is helping, since I still have the images of 23.04 and 23.10, 23.04 is ok, exp 23.10 in June,2023 is also ok but failed from 23.10.01 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bu

[Bug 2084015] Re: gnome-shell has no response when plug-in unauthorized thunderbolt devices

2024-10-09 Thread hugh chao
@vanvugt This issue still can be reproduced after 1. Only edp monitor attached 2. gnome-extensions disable ubuntu-d...@ubuntu.com 3. Forget all devices 4. logout 5. login 6. plugin again -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed

[Bug 2084015] Re: gnome-shell has no response when plug-in unauthorized thunderbolt devices

2024-10-09 Thread hugh chao
my thunderbolt storage + Dell thunderbolt Dock (WD22TB4) can reproduce this issue, and as #7, there is no nvidia GFX on XPS series, and seems install thunderbolt-tools can WA this issue, but I think it's because it installed it's own udev rule, so the rules are different -- You received this bu

[Bug 2084015] Re: gnome-shell has no response when plug-in unauthorized thunderbolt devices

2024-10-09 Thread hugh chao
and I also try LXDE, which can not reproduce this issue -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2084015 Title: gnome-shell has no response when plug-in unauthorized thun

[Bug 2007742] Re: Can't update stage views actor (regarding MetaWindowGroup, MetaWindowActorX11, MetaSurfaceActorX11)

2023-04-18 Thread hugh chao
In my case it's not only on Chrome, resizing and moving any application can reproduce this issue in Ubuntu 23.04 GFX Card: NVIDIA Corporation TU116 [GeForce GTX 1660 SUPER] GFX driver: nvidia-driver-525 gnome-shell: 44.0-2ubuntu3 Kernel: 6.2.0-19-generic -- You received this bug notification bec

[Bug 1853584] Re: [SRU]Not able to adjust Audio input UI volume after connecting headset

2020-11-08 Thread hugh chao
** Tags removed: verification-needed -- 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/1853584 Title: [SRU]Not able to adjust Audio input UI volume after connecting heads

[Bug 1845801] Re: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login.

2020-09-10 Thread hugh chao
** Tags removed: verification-needed verification-needed-focal ** Tags added: verification-done verification-done-focal -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1845801 T

[Bug 1845801] Re: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login.

2020-08-17 Thread hugh chao
** Changed in: oem-priority Assignee: hugh chao (hugh712) => jeremyszu (os369510) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1845801 Title: [nvidia] Automatic lo

[Bug 1845801] Re: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login.

2020-07-23 Thread hugh chao
Hi all, Currently grub is frozen in all series for point releases. So I will start the SRU after focal point release, please just use #105 with a "sudo update-grub" as a workaround. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnom

[Bug 1845801] Re: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login.

2020-07-23 Thread hugh chao
** Changed in: oem-priority Status: In Progress => Triaged -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1845801 Title: [nvidia] Automatic login fails and then all su

[Bug 1845801] Re: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login.

2020-07-22 Thread hugh chao
** Description changed: + [ Impact ] + In some platforms with specific Nvidia drivers, auto-login will fail due to the old vt-handoff patch in grub2. + + [ Test Case ] + 1. Boot ubuntu into desktop environment. + 2. Enabled auto login in System->Users + 3. Reboot the system + + [Expected resul

[Bug 1845801] Re: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login.

2020-07-20 Thread hugh chao
Upload debdiff for groovy, please help to review this patch, in the meantime, I'm running the stress test with this package in a nvidia platform, let's see how it goes. ** Patch added: "grub2_2.04-1ubuntu26_2.04-1ubuntu27.debdiff" https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/

[Bug 1845801] Re: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login.

2020-07-13 Thread hugh chao
the origin change was in ''' commit 9dadfd82504afa114b39e508e4580cb0212468ea (tag: pkg/import/2.00-20) Author: Colin Watson Date: Thu Nov 14 10:49:31 2013 + + Set vt.handoff=7 for smooth handoff to kernel graphical mode. ''' https://git.launchpad.net/~hugh712/ubuntu/+source/grub2/commit/?

[Bug 1845801] Re: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login.

2020-07-13 Thread hugh chao
** Also affects: grub2 (Ubuntu) Importance: Undecided Status: New ** Changed in: grub2 (Ubuntu) Status: New => Confirmed ** Changed in: oem-priority Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is s

[Bug 1845801] Re: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login.

2020-07-13 Thread hugh chao
I'll start the SRU for this issue soon -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1845801 Title: [nvidia] Automatic login fails and then all subsequent logins fail. Kil

[Bug 1845801] Re: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login.

2020-07-12 Thread hugh chao
if the result in #101 is positive for everyone, then I think it's because of this missed patch since from cosmic ** Patch added: "vt_handoff.patch" https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1845801/+attachment/5391915/+files/vt_handoff.patch -- You received this bug notif

[Bug 1845801] Re: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login.

2020-07-12 Thread hugh chao
Hi Guys, Help me to test this, this works for me, please find this line "set vt_handoff=vt.handoff=7" in /boot/grub/grub.cfg, and change it to "set vt_handoff=vt.handoff=1", then reboot let's see how it go, thanks. -- You received this bug notification because you are a member of Ubuntu Desktop

[Bug 1845801] Re: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login.

2020-07-12 Thread hugh chao
Hi Guys, Help me to test this, this works for me, please find this line "set vt_handoff=vt.handoff=7" in /boot/grub/grub.cfg, and change it to "set vt_handoff=vt.handoff=1", then reboot let's see how it goes, thanks. -- You received this bug notification because you are a member of Ubuntu Deskt

[Bug 1845801] Re: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login.

2020-06-25 Thread hugh chao
** Also affects: nvidia-graphics-drivers-440 (Ubuntu) Importance: Undecided Status: New ** Changed in: nvidia-graphics-drivers-440 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnom

[Bug 1845801] Re: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login.

2020-06-04 Thread hugh chao
** Tags added: sutton -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1845801 Title: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-sessio

[Bug 1845801] Re: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login.

2020-06-03 Thread hugh chao
** Tags added: oem-priority stella -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1845801 Title: [nvidia] Automatic login fails and then all subsequent logins fail. Killing

[Bug 1868260] Re: Change sleep-inactive-ac-timeout to 1200 to meet eStar 8 requirement

2020-03-26 Thread hugh chao
** Changed in: oem-priority Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1868260 Title: Change sleep-inactive-ac-timeout to 1200 to

[Bug 1868260] Re: Change sleep-inactive-ac-timeout to 1200 to meet eStar 8 requirement

2020-03-24 Thread hugh chao
Ok, I will override the setting in oem base image, thanks -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1868260 Title: Change sleep-inactive-ac-timeout to 1200 to me

[Bug 1867766] Re: Namespace prefix sodipodi on namedview is not defined

2020-03-17 Thread hugh chao
even in build ubiquity it will failed in : (run:75635): Gtk-WARNING **: 23:32:02.334: Could not load a pixbuf from icon theme. This may indicate that pixbuf loaders or the mime database could not be found. Exception in GTK frontend (invoking crash handler): Traceback (most recent call last): Fi

[Bug 1867766] Re: Namespace prefix sodipodi on namedview is not defined

2020-03-17 Thread hugh chao
even in building ubiquity it will fail in : (run:75635): Gtk-WARNING **: 23:32:02.334: Could not load a pixbuf from icon theme. This may indicate that pixbuf loaders or the mime database could not be found. Exception in GTK frontend (invoking crash handler): Traceback (most recent call last): F

[Bug 1867766] Re: Namespace prefix sodipodi on namedview is not defined

2020-03-17 Thread hugh chao
" lsb_release -rd Description:Ubuntu Focal Fossa (development branch) Release:20.04 "apt-cache policy gir1.2-rsvg-2.0 gir1.2-rsvg-2.0: Installed: 2.48.0-1 Candidate: 2.48.0-1 Version table: *** 2.48.0-1 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages

[Bug 1867766] [NEW] Namespace prefix sodipodi on namedview is not defined

2020-03-17 Thread hugh chao
Public bug reported: [Summary] Since the package "gir1.2-rsvg-2.0:amd64" been upgraded from 2.46.4-1ubuntu1 to 2.48.0-1 in Focal's daily build, ubiquity will crash as attached crash log. [Steps to reproduce] 1. Boot with OEM mode, 2. Finish the 1st stage 3. Reboot 4. Boot into OOBE(oem-config)

[Bug 1853584] Re: [SRU]Not able to adjust Audio input UI volume after connecting headset

2020-02-02 Thread hugh chao
** Changed in: oem-priority Status: Triaged => Fix Released ** Changed in: oem-priority/bionic Status: Triaged => 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.

[Bug 1853584] Re: [SRU]Not able to adjust Audio input UI volume after connecting headset

2020-01-13 Thread hugh chao
** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic -- 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/1853584 Title: [SRU]Not able to adju

[Bug 1853584] Re: [SRU]Not able to adjust Audio input UI volume after connecting headset

2020-01-13 Thread hugh chao
tried gnome-control-center 1:3.28.2-0ubuntu0.18.04.6 in a LG Thin Client[0], can fix this issue [0] https://www.lg.com/global/business/monitor/monitor-products/lg- CK500W -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-c

[Bug 1853584] Re: [SRU]Not able to adjust Audio input UI volume after connecting headset

2020-01-13 Thread hugh chao
tried gnome-control-center 1:3.28.2-0ubuntu0.18.04.6 in a hp Small Form Factor PC[0], can fix this issue [0] https://www8.hp.com/us/en/desktops/product-details/21353680 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-cen

[Bug 1853584] Re: [SRU]Not able to adjust Audio input UI volume after connecting headset

2020-01-13 Thread hugh chao
tried gnome-control-center 1:3.28.2-0ubuntu0.18.04.6 in a hp desktop mini machine[0], can fix this issue [0] http://h20195.www2.hp.com/v2/GetDocument.aspx?docname=c06339658 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control

[Bug 1853584] Re: [SRU]Not able to adjust Audio input UI volume after connecting headset

2020-01-13 Thread hugh chao
tried gnome-control-center 1:3.28.2-0ubuntu0.18.04.6 in a built-in speaker/microphone laptop[0], still works well, didn't find any Regression potential. [0] https://support.hp.com/ro-en/document/c05994943 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, whic

[Bug 1853584] Re: [SRU]Not able to adjust Audio input UI volume after connecting headset

2020-01-13 Thread hugh chao
** Description changed: [ Impact ] Not able to adjust Audio input UI volume if this device doesn't have a internal mic, the volume bar will be gray. [ Test Case ] 1. Boot ubuntu without any external headset connected. 2. Launch gnome-control-center and switch to Sound->Input t

[Bug 1853584] Re: [SRU]Not able to adjust Audio input UI volume after connecting headset

2020-01-13 Thread hugh chao
ged in: oem-priority/bionic Importance: Undecided => Critical ** Changed in: oem-priority/bionic Status: New => Triaged ** Changed in: oem-priority/bionic Assignee: (unassigned) => hugh chao (hugh712) -- You received this bug notification because you are a member of Ubun

[Bug 1853584] Re: [SRU]Not able to adjust Audio input UI volume after connecting headset

2020-01-12 Thread hugh chao
** Description changed: [ Impact ] Not able to adjust Audio input UI volume if this device doesn't have a internal mic, the volume bar will be gray. [ Test Case ] 1. Boot ubuntu without any external headset connected. 2. Launch gnome-control-center and switch to Sound->Input t

[Bug 1853584] Re: [SRU]Not able to adjust Audio input UI volume after connecting headset

2020-01-12 Thread hugh chao
** Description changed: [ Impact ] Not able to adjust Audio input UI volume if this device doesn't have a internal mic, the volume bar will be gray. [ Test Case ] 1. Boot ubuntu without any external headset connected. 2. Launch gnome-control-center and switch to Sound->Input t

[Bug 1853584] Re: [18.04]Not able to adjust Audio input UI volume after connecting headset

2019-12-25 Thread hugh chao
** Patch added: "check_input_treeview.patch" https://bugs.launchpad.net/gnome-control-center/+bug/1853584/+attachment/5315268/+files/check_input_treeview.patch ** Summary changed: - [18.04]Not able to adjust Audio input UI volume after connecting headset + [SRU]Not able to adjust Audio input

[Bug 1853584] Re: [18.04]Not able to adjust Audio input UI volume after connecting headset

2019-12-25 Thread hugh chao
** Description changed: [ Impact ] Not able to adjust Audio input UI volume if this device doesn't have a internal mic, the volume bar will be gray. [ Test Case ] 1. Boot ubuntu without any external headset connected. 2. Launch gnome-control-center and switch to Sound->Input t

[Bug 1853584] Re: [18.04]Not able to adjust Audio input UI volume after connecting headset

2019-12-24 Thread hugh chao
** Tags added: bionic -- 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/1853584 Title: [18.04]Not able to adjust Audio input UI volume after connecting headset To mana

[Bug 1853584] Re: [18.04]Not able to adjust Audio input UI volume after connecting headset

2019-12-24 Thread hugh chao
** Description changed: [ Impact ] Not able to adjust Audio input UI volume if this device doesn't have a internal mic, the volume bar will be gray. [ Test Case ] - 1. Boot ubuntu without any external microphone connected. + 1. Boot ubuntu without any external headset connected.

[Bug 1853584] Re: [18.04]Not able to adjust Audio input UI volume after connecting headset

2019-12-24 Thread hugh chao
** Description changed: + [ Impact ] + + Not able to adjust Audio input UI volume if this device doesn't have a + internal mic, the volume bar will be gray. + + [ Test Case ] + + 1. Boot ubuntu without any external microphone connected. + 2. Launch gnome-control-center and switch to Sound->Inpu

[Bug 1853584] Re: [18.04]Not able to adjust Audio input UI volume after connecting headset

2019-12-17 Thread hugh chao
** Description changed: Summary:Not able to adjust Audio input UI volume, it's gray Steps to reproduce: 1. Plug 3 ring earphone with mic to appropriate jack Expected result: System can be recording audio from external mic Actual result: Not able to adjust Audio input UI volu

[Bug 1853584] Re: [18.04]Not able to adjust Audio input UI volume after connecting headset

2019-12-17 Thread hugh chao
** Tags added: originate-from-1806835 ** Tags added: stella -- 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/1853584 Title: [18.04]Not able to adjust Audio input UI vol

[Bug 1853584] Re: [18.04]Not able to adjust Audio input UI volume after connecting headset

2019-12-10 Thread hugh chao
@Sebastien, Would you please help to backport there two commits in #15, thanks. -- 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/1853584 Title: [18.04]Not able to adjus

[Bug 1853584] Re: [18.04]Not able to adjust Audio input UI volume after connecting headset

2019-12-04 Thread hugh chao
@Robert, Is there any chance you can review this mp in #15? many thanks -- 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/1853584 Title: [18.04]Not able to adjust Audio

[Bug 1853584] Re: [18.04]Not able to adjust Audio input UI volume after connecting headset

2019-11-28 Thread hugh chao
https://gitlab.gnome.org/GNOME/gnome-control-center/merge_requests/641 -- 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/1853584 Title: [18.04]Not able to adjust Audio in

[Bug 1853584] Re: [18.04]Not able to adjust Audio input UI volume after connecting headset

2019-11-27 Thread hugh chao
@Robert, Is this the right branch? https://gitlab.gnome.org/GNOME/gnome-control-center/tree/gnome-3-28/panels/sound -- 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/185358

[Bug 1853584] Re: [18.04]Not able to adjust Audio input UI volume after connecting headset

2019-11-26 Thread hugh chao
@Sebastien, No, it's not from upstream, due to the code is quite different from upstream. If there is only one input device with only one input port, and this input port is active_port, e.g. there is no internal mic, just a mic jack on the machine, this issue will happen. For this kind of machin

[Bug 1853584] Re: [18.04]Not able to adjust Audio input UI volume after connecting headset

2019-11-26 Thread hugh chao
@Sebastien, please take a look of this patch ** Patch added: "check_input_treeview.patch" https://bugs.launchpad.net/gnome-control-center/+bug/1853584/+attachment/5307971/+files/check_input_treeview.patch -- You received this bug notification because you are a member of Ubuntu Desktop Bugs,

[Bug 1853584] Re: [18.04]Not able to adjust Audio input UI volume after connecting headset

2019-11-26 Thread hugh chao
@Sebastien Yes, What I meant was gnome-control-center -- 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/1853584 Title: [18.04]Not able to adjust Audio input UI volume af

[Bug 1853584] Re: [18.04]Not able to adjust Audio input UI volume after connecting headset

2019-11-25 Thread hugh chao
pavucontrol works good, I will try to backport this package to bionic, thanks. -- 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/1853584 Title: [18.04]Not able to adjust

[Bug 1853584] Re: [18.04]Not able to adjust Audio input UI volume after connecting headset

2019-11-22 Thread hugh chao
** Summary changed: - [18.04]Not able to adjust Audio input UI volume after connecting headset in "input tab" + [18.04]Not able to adjust Audio input UI volume after connecting headset -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to

[Bug 1853584] Re: [18.04]Not able to adjust Audio input UI volume after connecting headset in "input tab"

2019-11-22 Thread hugh chao
1. Still can reproduce this issue in 18.04.3 2. can not reproduce this issue in 19.04 and 19.10 -- 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/1853584 Title: [18.04]No

[Bug 1853584] [NEW] [18.04]Not able to adjust Audio input UI volume after connecting headset in "input tab"

2019-11-22 Thread hugh chao
Public bug reported: Summary:Not able to adjust Audio input UI volume, it's gray Steps to reproduce: 1. Plug 3 ring earphone with mic to appropriate jack Expected result: System can be recording audio from external mic Actual result: Not able to adjust Audio input UI volume, it's gray, and no v

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

2018-12-05 Thread hugh chao
haven't tried cosmic but I did try disco, still can reproduce this issue -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1772811 Title: different behaviors for switch

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

2018-12-04 Thread hugh chao
seems not only one oem platform can reproduced this issue due to Bug 539477 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1772811 Title: different behaviors for swit

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

2018-12-04 Thread hugh chao
** Tags added: stella -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1772811 Title: different behaviors for switch display mode between xenial and bionic To manage n