[Bug 2007742] Re: Can't update stage views actor (regarding MetaWindowGroup, MetaWindowActorX11, MetaSurfaceActorX11)
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 because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2007742 Title: Can't update stage views actor (regarding MetaWindowGroup, MetaWindowActorX11, MetaSurfaceActorX11) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/2007742/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1853584] Re: [SRU]Not able to adjust Audio input UI volume after connecting headset
** 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 headset To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1853584/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[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.
** 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 Title: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1845801/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[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.
** 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 login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1845801/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[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.
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 gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1845801 Title: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1845801/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[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.
** 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 subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1845801/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[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.
** 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 result] + System will boot into desktop environment without the login page. + + [Actual result] + System boots to login page, and can't login to desktop environment with the correct password. + + [ Regression potential ] + Low, the patch just removes vt.handoff part in grub2 package, and I can't find any regression in several runs of stress tests. + + --- + I just updated to the Ubuntu 19.10 beta. After boot, I'm shown the GDM login screen (which I shouldn't; I have auto login enabled), and logging in just takes me back to the same user selection screen even though the password is correct. If I switch to a TTY and run `sudo pkill gnome-session-binary`, logging in through GDM starts working again. I should add that the do-release-upgrade was rocky; I did it in a terminal from within gnome, went away for a while, and when I returned, I just saw an Ubuntu 19.10 in a TTY. I was able to do `sudo dpkg --configure -a` and complete the upgrade, but I don't know if something's still messed up due to that. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0 Uname: Linux 5.3.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 435.21 Sun Aug 25 08:17:57 CDT 2019 GCC version: gcc version 9.2.1 20190909 (Ubuntu 9.2.1-8ubuntu1) ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Sep 28 19:55:42 2019 DistUpgraded: 2019-09-28 18:35:15,142 INFO cache.commit() DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: nvidia, 435.21, 5.3.0-13-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] [10de:1b06] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GP102 [GeForce GTX 1080 Ti] [1043:85e4] InstallationDate: Installed on 2019-09-14 (13 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: MSI MS-7A67 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-13-generic root=UUID=04974c80-e732-49b6-8148-c3dce7c02a25 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: Upgraded to eoan on 2019-09-28 (0 days ago) dmi.bios.date: 01/25/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.60 dmi.board.asset.tag: Default string dmi.board.name: H270I GAMING PRO AC (MS-7A67) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.60:bd01/25/2018:svnMSI:pnMS-7A67:pvr1.0:rvnMSI:rnH270IGAMINGPROAC(MS-7A67):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.family: Default string dmi.product.name: MS-7A67 dmi.product.sku: Default string dmi.product.version: 1.0 dmi.sys.vendor: MSI version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.1.6-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20190820-0ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 PPA: https://launchpad.net/~hugh712/+archive/ubuntu/sru-1845801 ** Description changed: [ Impact ] - In some platforms with specific Nvidia drivers, auto-login will fail due to the old vt-handoff patch in grub2. + 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 result] System will boot into desktop environment without the login page. [Actual result] System boots to login page, and can't login to desktop environment with the correct password.
[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.
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/1845801/+attachment/5394535/+files/grub2_2.04-1ubuntu26_2.04-1ubuntu27.debdiff ** Description changed: I just updated to the Ubuntu 19.10 beta. After boot, I'm shown the GDM login screen (which I shouldn't; I have auto login enabled), and logging in just takes me back to the same user selection screen even though the password is correct. If I switch to a TTY and run `sudo pkill gnome-session-binary`, logging in through GDM starts working again. I should add that the do-release-upgrade was rocky; I did it in a terminal from within gnome, went away for a while, and when I returned, I just saw an Ubuntu 19.10 in a TTY. I was able to do `sudo dpkg --configure -a` and complete the upgrade, but I don't know if something's still messed up due to that. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0 Uname: Linux 5.3.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: - NVRM version: NVIDIA UNIX x86_64 Kernel Module 435.21 Sun Aug 25 08:17:57 CDT 2019 - GCC version: gcc version 9.2.1 20190909 (Ubuntu 9.2.1-8ubuntu1) + NVRM version: NVIDIA UNIX x86_64 Kernel Module 435.21 Sun Aug 25 08:17:57 CDT 2019 + GCC version: gcc version 9.2.1 20190909 (Ubuntu 9.2.1-8ubuntu1) ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Sep 28 19:55:42 2019 DistUpgraded: 2019-09-28 18:35:15,142 INFO cache.commit() DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: nvidia, 435.21, 5.3.0-13-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: - NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] [10de:1b06] (rev a1) (prog-if 00 [VGA controller]) -Subsystem: ASUSTeK Computer Inc. GP102 [GeForce GTX 1080 Ti] [1043:85e4] + NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] [10de:1b06] (rev a1) (prog-if 00 [VGA controller]) + Subsystem: ASUSTeK Computer Inc. GP102 [GeForce GTX 1080 Ti] [1043:85e4] InstallationDate: Installed on 2019-09-14 (13 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: MSI MS-7A67 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-13-generic root=UUID=04974c80-e732-49b6-8148-c3dce7c02a25 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: Upgraded to eoan on 2019-09-28 (0 days ago) dmi.bios.date: 01/25/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.60 dmi.board.asset.tag: Default string dmi.board.name: H270I GAMING PRO AC (MS-7A67) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.60:bd01/25/2018:svnMSI:pnMS-7A67:pvr1.0:rvnMSI:rnH270IGAMINGPROAC(MS-7A67):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.family: Default string dmi.product.name: MS-7A67 dmi.product.sku: Default string dmi.product.version: 1.0 dmi.sys.vendor: MSI version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.1.6-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20190820-0ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 + + PPA: https://launchpad.net/~hugh712/+archive/ubuntu/sru-1845801 -- 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-session-binary fixes it, or just not using automatic login. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1845801/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com
[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.
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/?h=ubuntu/devel=9dadfd82504afa114b39e508e4580cb0212468ea then it's been changed in bionic as: ''' commit db84c3cc6faa4750d12c451f7a0c20560d0893bd Author: Mathieu Trudel-Lapierre Date: Fri Feb 9 16:30:45 2018 -0500 Add configure option to use vt.handoff=1 ''' https://git.launchpad.net/~hugh712/ubuntu/+source/grub2/commit/?h=bionic=c9b225dd94935e17dc8196dcaea524d4897bef4d -- 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-session-binary fixes it, or just not using automatic login. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1845801/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[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.
** 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 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-session-binary fixes it, or just not using automatic login. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1845801/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[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.
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. Killing gnome-session-binary fixes it, or just not using automatic login. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1845801/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[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.
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 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-session-binary fixes it, or just not using automatic login. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1845801/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[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.
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 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-session-binary fixes it, or just not using automatic login. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1845801/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[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.
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 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-session-binary fixes it, or just not using automatic login. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1845801/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[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.
** 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 gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1845801 Title: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1845801/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[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.
** 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-session-binary fixes it, or just not using automatic login. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1845801/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[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.
** 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 gnome-session-binary fixes it, or just not using automatic login. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1845801/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1868260] Re: Change sleep-inactive-ac-timeout to 1200 to meet eStar 8 requirement
** 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 meet eStar 8 requirement To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1868260/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1868260] Re: Change sleep-inactive-ac-timeout to 1200 to meet eStar 8 requirement
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 meet eStar 8 requirement To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1868260/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1867766] Re: Namespace prefix sodipodi on namedview is not defined
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): File "./ubiquity/frontend/gtk_components/nmwidgets.py", line 330, in __init__ self.view = NetworkManagerTreeView(self.state_changed) File "./ubiquity/frontend/gtk_components/nmwidgets.py", line 96, in __init__ self.configure_icons() File "./ubiquity/frontend/gtk_components/nmwidgets.py", line 196, in configure_icons ico = ico.load_icon() gi.repository.GLib.GError: rsvg-error-quark: XML parse error: error code=201 (3) in (null):40:466: Namespace prefix sodipodi on namedview is not defined (0) Traceback (most recent call last): File "./ubiquity/frontend/gtk_components/nmwidgets.py", line 330, in __init__ self.view = NetworkManagerTreeView(self.state_changed) File "./ubiquity/frontend/gtk_components/nmwidgets.py", line 96, in __init__ self.configure_icons() File "./ubiquity/frontend/gtk_components/nmwidgets.py", line 196, in configure_icons ico = ico.load_icon() gi.repository.GLib.Error: rsvg-error-quark: XML parse error: error code=201 (3) in (null):40:466: Namespace prefix sodipodi on namedview is not defined (0) xauth/Xrdb output: -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to librsvg in Ubuntu. https://bugs.launchpad.net/bugs/1867766 Title: Namespace prefix sodipodi on namedview is not defined To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/librsvg/+bug/1867766/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1867766] Re: Namespace prefix sodipodi on namedview is not defined
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): File "./ubiquity/frontend/gtk_components/nmwidgets.py", line 330, in __init__ self.view = NetworkManagerTreeView(self.state_changed) File "./ubiquity/frontend/gtk_components/nmwidgets.py", line 96, in __init__ self.configure_icons() File "./ubiquity/frontend/gtk_components/nmwidgets.py", line 196, in configure_icons ico = ico.load_icon() gi.repository.GLib.GError: rsvg-error-quark: XML parse error: error code=201 (3) in (null):40:466: Namespace prefix sodipodi on namedview is not defined (0) Traceback (most recent call last): File "./ubiquity/frontend/gtk_components/nmwidgets.py", line 330, in __init__ self.view = NetworkManagerTreeView(self.state_changed) File "./ubiquity/frontend/gtk_components/nmwidgets.py", line 96, in __init__ self.configure_icons() File "./ubiquity/frontend/gtk_components/nmwidgets.py", line 196, in configure_icons ico = ico.load_icon() gi.repository.GLib.Error: rsvg-error-quark: XML parse error: error code=201 (3) in (null):40:466: Namespace prefix sodipodi on namedview is not defined (0) xauth/Xrdb output: -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to librsvg in Ubuntu. https://bugs.launchpad.net/bugs/1867766 Title: Namespace prefix sodipodi on namedview is not defined To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/librsvg/+bug/1867766/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1867766] Re: Namespace prefix sodipodi on namedview is not defined
" 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 500 file: Packages 500 file: Packages 500 file: Packages 500 file: Packages 500 file: Packages 500 file: Packages 500 file: Packages 100 /var/lib/dpkg/status 2.46.4-1ubuntu1 500 500 file: Packages 500 file: Packages 500 file: Packages 500 file: Packages 500 file: Packages 500 file: Packages 500 file: Packages ** Tags added: oem-priority -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to librsvg in Ubuntu. https://bugs.launchpad.net/bugs/1867766 Title: Namespace prefix sodipodi on namedview is not defined To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/librsvg/+bug/1867766/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1867766] [NEW] Namespace prefix sodipodi on namedview is not defined
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) [Expected result] Should start oobe without any error. [Actual result] The error message 『The installer encountered an unrecoverable error. A desktop session will now be run so that you may investigate the problem or try installing again.』shown on the screen. [Failure rate] 100% [Additional information] No idea why, but some "nm-signal-*-secure" images will fail in Gtk.IconTheme().lookup_icon(n, 22, 0).load_icon(), and below error message will show: " Gtk-WARNING **: 18:23:31.380: Could not load a pixbuf from icon theme. This may indicate that pixbuf loaders or the mime database could not be found. gi.repository.GLib.GError: rsvg-error-quark: XML parse error: error code=201 (3) in (null):40:466: Namespace prefix sodipodi on namedview is not defined " ** Affects: librsvg (Ubuntu) Importance: Undecided Status: New ** Attachment added: "_usr_lib_ubiquity_bin_ubiquity.0.crash" https://bugs.launchpad.net/bugs/1867766/+attachment/5337963/+files/_usr_lib_ubiquity_bin_ubiquity.0.crash ** Summary changed: - gi.repository.GLib.GError: rsvg-error-quark: XML parse error: error code=201 (3) in (null):40:466: Namespace prefix sodipodi on namedview is not defined + Namespace prefix sodipodi on namedview is not defined -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to librsvg in Ubuntu. https://bugs.launchpad.net/bugs/1867766 Title: Namespace prefix sodipodi on namedview is not defined To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/librsvg/+bug/1867766/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1853584] Re: [SRU]Not able to adjust Audio input UI volume after connecting headset
** 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.launchpad.net/bugs/1853584 Title: [SRU]Not able to adjust Audio input UI volume after connecting headset To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1853584/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1853584] Re: [SRU]Not able to adjust Audio input UI volume after connecting headset
** 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 adjust Audio input UI volume after connecting headset To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1853584/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1853584] Re: [SRU]Not able to adjust Audio input UI volume after connecting headset
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-center in Ubuntu. https://bugs.launchpad.net/bugs/1853584 Title: [SRU]Not able to adjust Audio input UI volume after connecting headset To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1853584/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1853584] Re: [SRU]Not able to adjust Audio input UI volume after connecting headset
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-center in Ubuntu. https://bugs.launchpad.net/bugs/1853584 Title: [SRU]Not able to adjust Audio input UI volume after connecting headset To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1853584/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1853584] Re: [SRU]Not able to adjust Audio input UI volume after connecting headset
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-center in Ubuntu. https://bugs.launchpad.net/bugs/1853584 Title: [SRU]Not able to adjust Audio input UI volume after connecting headset To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1853584/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1853584] Re: [SRU]Not able to adjust Audio input UI volume after connecting headset
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, 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 headset To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1853584/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1853584] Re: [SRU]Not able to adjust Audio input UI volume after connecting headset
** 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 tab. 3. Connect external headset, then you will find the input show up but can not adjust the volume. [ Regression potential ] - Low. + Low. change is the workaround to active/deactivate some bugs which + didn't report things in the right order. It will just have extra + active/deactiveate actions in normal situation(which the machines don't + have this issue). + + Verified on built-in and non built-in input device machines , no + regression found yet. Package in this PPA: https://launchpad.net/~hugh712/+archive/ubuntu/mysru/+packages 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 volume detected in UI, but I can recording the input audio by checkbox Failure rate:100% Note. 1. There is no internal mic, just a mic jack on the machine, this issue will happen 2. gnome-control-center version : 1:3.28.2-0ubuntu0.18.04.2 Note:20.04, 19.10, 19.04 are immune on the bug -- 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 headset To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1853584/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1853584] Re: [SRU]Not able to adjust Audio input UI volume after connecting headset
** Also affects: oem-priority Importance: Undecided Status: New ** Changed in: oem-priority Importance: Undecided => Critical ** Changed in: oem-priority Status: New => Triaged ** Also affects: oem-priority/bionic Importance: Undecided Status: New ** Changed 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 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 headset To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1853584/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1853584] Re: [SRU]Not able to adjust Audio input UI volume after connecting headset
** 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 tab. 3. Connect external headset, then you will find the input show up but can not adjust the volume. [ Regression potential ] - Low, The first part of the patch is a workaround for a bug elsewhere - which is reporting things in the wrong order. The second part is a fix - for a case that wasn't being handled correctly. + Low. - - Package in this PPA: https://launchpad.net/~hugh712/+archive/ubuntu/mysru/+packages + Package in this PPA: + https://launchpad.net/~hugh712/+archive/ubuntu/mysru/+packages 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 volume detected in UI, but I can recording the input audio by checkbox Failure rate:100% Note. 1. There is no internal mic, just a mic jack on the machine, this issue will happen 2. gnome-control-center version : 1:3.28.2-0ubuntu0.18.04.2 Note:20.04, 19.10, 19.04 are immune on the bug -- 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 headset To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1853584/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1853584] Re: [SRU]Not able to adjust Audio input UI volume after connecting headset
** 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 tab. 3. Connect external headset, then you will find the input show up but can not adjust the volume. [ Regression potential ] + + Low, The first part of the patch is a workaround for a bug elsewhere + which is reporting things in the wrong order. The second part is a fix + for a case that wasn't being handled correctly. Package in this PPA: https://launchpad.net/~hugh712/+archive/ubuntu/mysru/+packages 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 volume detected in UI, but I can recording the input audio by checkbox Failure rate:100% Note. 1. There is no internal mic, just a mic jack on the machine, this issue will happen 2. gnome-control-center version : 1:3.28.2-0ubuntu0.18.04.2 Note:20.04, 19.10, 19.04 are immune on the bug -- 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 headset To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1853584/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1853584] Re: [18.04]Not able to adjust Audio input UI volume after connecting headset
** 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 UI volume after connecting headset -- 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 headset To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1853584/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1853584] Re: [18.04]Not able to adjust Audio input UI volume after connecting headset
** 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 tab. 3. Connect external headset, then you will find the input show up but can not adjust the volume. [ Regression potential ] + + + Package in this PPA: https://launchpad.net/~hugh712/+archive/ubuntu/mysru/+packages 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 volume detected in UI, but I can recording the input audio by checkbox Failure rate:100% Note. 1. There is no internal mic, just a mic jack on the machine, this issue will happen 2. gnome-control-center version : 1:3.28.2-0ubuntu0.18.04.2 Note:20.04, 19.10, 19.04 are immune on the bug -- 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 headset To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1853584/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1853584] Re: [18.04]Not able to adjust Audio input UI volume after connecting headset
** 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 manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1853584/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1853584] Re: [18.04]Not able to adjust Audio input UI volume after connecting headset
** 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. 2. Launch gnome-control-center and switch to Sound->Input tab. 3. Connect external headset, then you will find the input show up but can not adjust the volume. [ Regression potential ] - 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 volume detected in UI, but I can recording the input audio by checkbox Failure rate:100% Note. 1. There is no internal mic, just a mic jack on the machine, this issue will happen 2. gnome-control-center version : 1:3.28.2-0ubuntu0.18.04.2 Note:20.04, 19.10, 19.04 are immune on the bug -- 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 manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1853584/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1853584] Re: [18.04]Not able to adjust Audio input UI volume after connecting headset
** 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->Input tab. + 3. Connect external headset, then you will find the input show up but can not adjust the volume. + + [ Regression potential ] + + + + 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 volume detected in UI, but I can recording the input audio by checkbox Failure rate:100% Note. 1. There is no internal mic, just a mic jack on the machine, this issue will happen 2. gnome-control-center version : 1:3.28.2-0ubuntu0.18.04.2 - Note:20.04, 19.10, 19.04 are immune on the bug -- 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 manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1853584/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1853584] Re: [18.04]Not able to adjust Audio input UI volume after connecting headset
** 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 volume, it's gray, and no volume detected in UI, but I can recording the input audio by checkbox Failure rate:100% Note. 1. There is no internal mic, just a mic jack on the machine, this issue will happen 2. gnome-control-center version : 1:3.28.2-0ubuntu0.18.04.2 + + + Note:20.04, 19.10, 19.04 are immune on the bug -- 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 manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1853584/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1853584] Re: [18.04]Not able to adjust Audio input UI volume after connecting headset
** 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 volume after connecting headset To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1853584/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1853584] Re: [18.04]Not able to adjust Audio input UI volume after connecting headset
@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 adjust Audio input UI volume after connecting headset To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1853584/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1853584] Re: [18.04]Not able to adjust Audio input UI volume after connecting headset
@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 input UI volume after connecting headset To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1853584/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1853584] Re: [18.04]Not able to adjust Audio input UI volume after connecting headset
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 input UI volume after connecting headset To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1853584/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1853584] Re: [18.04]Not able to adjust Audio input UI volume after connecting headset
@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/1853584 Title: [18.04]Not able to adjust Audio input UI volume after connecting headset To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1853584/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1853584] Re: [18.04]Not able to adjust Audio input UI volume after connecting headset
@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 machines, if users plug mic in the jack, the function active_input_update() is called ahead of the function add_input_ui_entry(), then we will see "No devices in the tree, so cannot set the active output" from syslog, this issue will be reproduced. On other machines, the add_input_ui_entry() is called ahead of active_input_update(), then there is no problem. So for this patch, just checking if there is only one input item in the treeview, call active_input_update(). And call gtk_widget_set_sensitive() to gray out the input volume bar if there isn't any input item in the treeview. -- 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 manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1853584/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1853584] Re: [18.04]Not able to adjust Audio input UI volume after connecting headset
@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, 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 manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1853584/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1853584] Re: [18.04]Not able to adjust Audio input UI volume after connecting headset
@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 after connecting headset To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1853584/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1853584] Re: [18.04]Not able to adjust Audio input UI volume after connecting headset
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 Audio input UI volume after connecting headset To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1853584/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1853584] Re: [18.04]Not able to adjust Audio input UI volume after connecting headset
** 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 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 manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1853584/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1853584] Re: [18.04]Not able to adjust Audio input UI volume after connecting headset in "input tab"
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]Not able to adjust Audio input UI volume after connecting headset in "input tab" To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1853584/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1853584] [NEW] [18.04]Not able to adjust Audio input UI volume after connecting headset in "input tab"
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 volume detected in UI, but I can recording the input audio by checkbox Failure rate:100% Note. 1. There is no internal mic, just a mic jack on the machine, this issue will happen 2. gnome-control-center version : 1:3.28.2-0ubuntu0.18.04.2 ** Affects: gnome-control-center Importance: Unknown Status: Unknown ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: oem-priority ** Bug watch added: gitlab.gnome.org/GNOME/gnome-control-center/issues #324 https://gitlab.gnome.org/GNOME/gnome-control-center/issues/324 ** Also affects: gnome-control-center via https://gitlab.gnome.org/GNOME/gnome-control-center/issues/324 Importance: Unknown Status: Unknown ** Tags added: oem-priority ** Summary changed: - 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 in "input tab" -- 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 in "input tab" To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1853584/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1772811] Re: different behaviors for switch display mode between xenial and bionic
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 display mode between xenial and bionic To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1772811/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1772811] Re: different behaviors for switch display mode between xenial and bionic
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 switch display mode between xenial and bionic To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1772811/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1772811] Re: different behaviors for switch display mode between xenial and bionic
** 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 notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1772811/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
