[Bug 1885087] Re: Can't keep brightness value after reboot/poweroff in some nvidia gfx
tried nvidia-graphics-drivers-455 in focal which can fix this issue, I didn't observe any regression. ** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1885087 Title: Can't keep brightness value after reboot/poweroff in some nvidia gfx To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1885087/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1885087] Re: Can't keep brightness value after reboot/poweroff in some nvidia gfx
tried nvidia-graphics-drivers-455 in groovy which can fix this issue, I didn't observe any regression. ** Tags removed: verification-needed-groovy ** Tags added: verification-done-groovy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1885087 Title: Can't keep brightness value after reboot/poweroff in some nvidia gfx To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1885087/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1885087] Re: Can't keep brightness value after reboot/poweroff in some nvidia gfx
tried nvidia-graphics-drivers-455 in bionic which can fix this issue, I didn't observe any regression. ** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic ** Changed in: oem-priority Status: Confirmed => Fix Committed ** Changed in: oem-priority/focal Status: New => Fix Committed ** Also affects: oem-priority/bionic Importance: Undecided Status: New ** Changed in: oem-priority/bionic Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1885087 Title: Can't keep brightness value after reboot/poweroff in some nvidia gfx To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1885087/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1906653] [NEW] Backport systemd to make uevents "sticky"
Public bug reported: Base on lwn 837033 [0], Linux 4.12 introduced two new uevents "bind" and "unbind" to the Linux device model which resulted in a number of software issues. So in this PR [1] which minimize issues resulting from this kernel change (but not avoid them entirely) by make uevent "sticky", meaning that once a tag is assigned to a device it will not be removed from the device again until the device itself is removed (i.e. unplugged). [0] https://lwn.net/Articles/837033/ [1] https://github.com/systemd/systemd/pull/16853/files ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Description changed: Base on lwn 837033 [0], Linux 4.12 introduced two new uevents "bind" and "unbind" to the Linux device model which resulted in a number of software issues. - So in this PR [1] which minimize issues resulting from this kernel change (but not avoid them entirely) by make uevent "sticky", meaning that once a tag is assigned to a device it will not - be removed from the device again until the device itself is removed (i.e. unplugged). - + So in this PR [1] which minimize issues resulting from this kernel + change (but not avoid them entirely) by make uevent "sticky", meaning + that once a tag is assigned to a device it will not be removed from the + device again until the device itself is removed (i.e. unplugged). [0] https://lwn.net/Articles/837033/ [1] https://github.com/systemd/systemd/pull/16853/files -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1906653 Title: Backport systemd to make uevents "sticky" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1906653/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1906653] Re: Backport systemd to make uevents "sticky"
** Description changed: Base on lwn 837033 [0], Linux 4.12 introduced two new uevents "bind" and "unbind" to the Linux device model which resulted in a number of software issues. So in this PR [1] which minimize issues resulting from this kernel change (but not avoid them entirely) by make uevent "sticky", meaning that once a tag is assigned to a device it will not be removed from the device again until the device itself is removed (i.e. unplugged). + An example causing by this issue, I had a usb printer (non-ippusbxd) + which connected to my laptop, but after unplugging it from my laptop, + the .device unit were still present, if a different printer gets plugged + to the same USB port then, it won't be configured correctly. + [0] https://lwn.net/Articles/837033/ [1] https://github.com/systemd/systemd/pull/16853/files -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1906653 Title: Backport systemd to make uevents "sticky" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1906653/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1929260] Re: backport the ustreamer deb from impish to focal
** Description changed: [Impact] - Due to the target image for internal project(remote enhancement project) - - zapper[0] is 20.04, + Due to the target image for internal project(remote enhancement project) + - zapper[0] is 20.04, and currently the video stream package - ustreamer is only on hirsute and impish [1], this package is necessary for us to stream the remote video to local, so need to back the package into 20.04 [Test Plan] - - Install the package through - - sudo apt install ustreamer + - Install the package through + - sudo apt install ustreamer - Launch the application + - ustreamer --device=/dev/video<0-9> --host= --port=8080 + - try live stream on the webpage as :8080 [Where problems could occur] Seems we don't have this package in focal right now, - and it definitely an independence package, so I don't think there is any + and it definitely an independence package, so I don't think there is any problem. [Other Info] * PPA: https://launchpad.net/~hugh712/+archive/ubuntu/sru-1929260 [0] https://launchpad.net/zapper [1] https://packages.ubuntu.com/search?keywords=ustreamer ** Information type changed from Proprietary to Public ** Also affects: ustreamer (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1929260 Title: backport the ustreamer deb from impish to focal To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1929260/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1920107] Re: Failed messages of sd-umount shown with reboot/shutdown
I also can reproduce this issue in my amd64 machine. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1920107 Title: Failed messages of sd-umount shown with reboot/shutdown To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1920107/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1893300] Re: The status of cups still shows idle when the printer has been unplugged
@Łukasz, updated, please help to review again, thanks. ** Description changed: [ Impact ] After printers (non-ippusb protocal) have been disconnected, the status of cups still shows "idle" instead of "disabled", so seems the disconnected procedure hasn't worked well. [ Test Case ] 1. Connect the printer (non-ippusb protocal)(which isn't 070104) with any 20.04 machine 2. Wait for the status of cups became "Idle" (lpstat -p) 3. Unplug the cable of the printer 4. Check the status of cups again. (lpstat -p) [ Regression potential ] - Low, the change just makes "strcmp" to "srtsrt" and has more checks on the existing of device path. + Very Low, if something went wrong in the change, then this issue happened again, due to this snippet will only be called during printer removed event. [Expected result] The status should show disabled. [Actual result] The status shows idle. [info] Target: HP LaserJet Pro203dw HP Officejet 100 Mobile Printer HP Officeject 200 Mobile Printer Brother HL-2250DN Samsung ML-331x Upstream Bug: https://github.com/OpenPrinting/system-config- printer/issues/182 PPA: https://launchpad.net/~hugh712/+archive/ubuntu/sru-1893300 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1893300 Title: The status of cups still shows idle when the printer has been unplugged To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1893300/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1893300] Re: The status of cups still shows idle when the printer has been unplugged
verified the version 1.5.12-0ubuntu1.1 in focal-proposed, works well and didn't observe any potential regression. ** Tags removed: verification-needed-focal verification-needed-groovy ** Tags added: verification-done-focal verification-done-groovy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1893300 Title: The status of cups still shows idle when the printer has been unplugged To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1893300/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1893300] Re: The status of cups still shows idle when the printer has been unplugged
verified the version 1.5.12-0ubuntu3.1 in groovy-proposed, works well and didn't observe any potential regression. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1893300 Title: The status of cups still shows idle when the printer has been unplugged To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1893300/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-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 Bugs, which is subscribed to 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 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1893300] Re: The status of cups still shows idle when the printer has been unplugged
** Changed in: oem-priority/focal Status: New => Fix Released ** Changed in: oem-priority Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1893300 Title: The status of cups still shows idle when the printer has been unplugged To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1893300/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-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 Bugs, which is subscribed to 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 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-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 Bugs, which is subscribed to 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 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-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 Bugs, which is subscribed to 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 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1804786] [NEW] Garbage occurred when Playing the video in the Ubuntu Desktop Guide
Public bug reported: Garbage occurred when Playing the video in the Ubuntu Desktop Guide. Reproduce step 1. Ubuntu 18.04.1. 2. ubuntu-docs 18.04.4 3. Playing the video(Launch applications) from Help-->Getting started with GNOME. 4. Garbage occurred after the video repeat about 3 times==> issue. Expected results: The Video can be played normally no-matter how many times. Actual results: Garbage occurred after the video repeat about 3 times Note: 1. the video will show blank but still have the voice after the issue finish. 2. Right click the mouse and choice "save video as", this application will crashed ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubuntu-docs 18.04.4 ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18 Uname: Linux 4.15.0-39-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Nov 23 16:46:00 2018 InstallationDate: Installed on 2018-04-30 (206 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all SourcePackage: ubuntu-docs UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubuntu-docs (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ** Description changed: Garbage occurred when Playing the video in the Ubuntu Desktop Guide. - Reproduce step 1. Ubuntu 18.04.1. 2. ubuntu-docs 18.04.4 3. Playing the video(Launch applications) from Help-->Getting started with GNOME. 4. Garbage occurred after the video repeat about 3 times==> issue. Expected results: The Video can be played normally no-matter how many times. Actual results: Garbage occurred after the video repeat about 3 times Note: 1. the video will show blank but still have the voice after the issue finish. - 2. Zooming in and out of the app has garbage too. - 3. Right click the mouse and choice "save video as", this application will crashed + 2. Right click the mouse and choice "save video as", this application will crashed ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubuntu-docs 18.04.4 ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18 Uname: Linux 4.15.0-39-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Nov 23 16:46:00 2018 InstallationDate: Installed on 2018-04-30 (206 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all SourcePackage: ubuntu-docs UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1804786 Title: Garbage occurred when Playing the video in the Ubuntu Desktop Guide To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-docs/+bug/1804786/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1804786] Re: Garbage occurred when Playing the video in the Ubuntu Desktop Guide
upload video which this issue was happening ** Attachment added: "O1684740_Garbage.mp4" https://bugs.launchpad.net/ubuntu/+source/ubuntu-docs/+bug/1804786/+attachment/5215566/+files/O1684740_Garbage.mp4 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1804786 Title: Garbage occurred when Playing the video in the Ubuntu Desktop Guide To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-docs/+bug/1804786/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-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 Bugs, which is subscribed to 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 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-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 Bugs, which is subscribed to 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 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-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 Bugs, which is subscribed to 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 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-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 Bugs, which is subscribed to 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 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-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 Bugs, which is subscribed to 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 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-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 Bugs, which is subscribed to 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 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-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 Bugs, which is subscribed to 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 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-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 Bugs, which is subscribed to 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 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-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 Bugs, which is subscribed to 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 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-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 Bugs, which is subscribed to 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 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-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 Bugs, which is subscribed to 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 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-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 Bugs, which is subscribed to 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 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-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 Bugs, which is subscribed to 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 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-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 Bugs, which is subscribed to 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 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-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 Bugs, which is subscribed to 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 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-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 Bugs, which is subscribed to 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 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1851773] Re: [SRU] Need rtl8821ce in Bionic
tried "HP ProOne 400 G5 All-in-One Business PC"[0] with this 8821ce dkms, works well, there isn't any issue on this machine [0] https://support.hp.com/in-en/document/c06409794#AbT11 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1851773 Title: [SRU] Need rtl8821ce in Bionic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rtl8821ce/+bug/1851773/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-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 Bugs, which is subscribed to 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 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-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 Bugs, which is subscribed to 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 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-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 Bugs, which is subscribed to 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 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-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 Bugs, which is subscribed to 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 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1865161] Re: Written "press return to shutdown the computer" does not appear.
I tried to add systemd.debug-shell=1, and switched to tty9 when the installation was done and switched back to tty1, then the message "Please remove the installation medium,then reboot" shown up. Next step, I tried to send message via "plymouth message --text= ", but the messages didn't be updated. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1865161 Title: Written "press return to shutdown the computer" does not appear. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1865161/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1869331] [NEW] The background is black in whole ubiquity session
Public bug reported: [Summary] Since focal daily build - 3/25, the background in ubiquity become black + vendor+Ubuntu icons(same as plymouth spinner theme), and also I can reproduce this issue in 3/26 daily build. [Steps to reproduce] 1. Boot the installer with USB sticker 2. Select Install Ubuntu 3. Waiting for the interactive page shown up. [Expected result] The background with focal theme. [Actual result] The background is whole black. [Failure rate] 100% [Additional information] " lsb_release -rd Description: Ubuntu Focal Fossa (development branch) Release: 20.04 ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1869331 Title: The background is black in whole ubiquity session To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1869331/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1869331] Re: The background is black in whole ubiquity session
expected theme (3/24 daily build) ** Attachment added: "Screenshot from 2020-03-27 16-57-27.png" https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1869331/+attachment/5342065/+files/Screenshot%20from%202020-03-27%2016-57-27.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1869331 Title: The background is black in whole ubiquity session To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1869331/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1869331] Re: The background is black in whole ubiquity session
unexpected theme (since from 3/25 daily build) ** Attachment added: "Screenshot from 2020-03-27 17-00-03.png" https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1869331/+attachment/5342066/+files/Screenshot%20from%202020-03-27%2017-00-03.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1869331 Title: The background is black in whole ubiquity session To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1869331/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1869331] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1869331/+attachment/5342071/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1869331 Title: The background is black in whole ubiquity session To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1869331/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1869331] Re: The background is black in whole ubiquity session
apport information ** Tags added: apport-collected focal ubuntu ** Description changed: [Summary] Since focal daily build - 3/25, the background in ubiquity become black + vendor+Ubuntu icons(same as plymouth spinner theme), and also I can reproduce this issue in 3/26 daily build. [Steps to reproduce] 1. Boot the installer with USB sticker 2. Select Install Ubuntu 3. Waiting for the interactive page shown up. [Expected result] The background with focal theme. [Actual result] The background is whole black. [Failure rate] 100% [Additional information] " lsb_release -rd Description: Ubuntu Focal Fossa (development branch) Release: 20.04 + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu21 + Architecture: amd64 + CasperVersion: 1.441 + DistroRelease: Ubuntu 20.04 + InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed quiet splash --- + LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200325) + NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair + Package: ubiquity 20.04.6 + PackageArchitecture: amd64 + ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 + Tags: focal ubuntu + Uname: Linux 5.4.0-18-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: + + _MarkForUpload: True ** Attachment added: "Casper.txt" https://bugs.launchpad.net/bugs/1869331/+attachment/5342068/+files/Casper.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1869331 Title: The background is black in whole ubiquity session To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1869331/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1869331] Dependencies.txt
apport information ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1869331/+attachment/5342069/+files/Dependencies.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1869331 Title: The background is black in whole ubiquity session To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1869331/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1869331] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1869331/+attachment/5342070/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1869331 Title: The background is black in whole ubiquity session To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1869331/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1869331] UbiquitySyslog.txt
apport information ** Attachment added: "UbiquitySyslog.txt" https://bugs.launchpad.net/bugs/1869331/+attachment/5342072/+files/UbiquitySyslog.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1869331 Title: The background is black in whole ubiquity session To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1869331/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1865161] Re: Written "press return to shutdown the computer" does not appear.
plymouthd is in interruptible sleep state as: @sbin/plymouthd --mode=reboot --attach-to-session -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1865161 Title: Written "press return to shutdown the computer" does not appear. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1865161/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1865161] Re: Written "press return to shutdown the computer" does not appear.
upload casper-stop log ** Attachment added: "casper-stop.log" https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1865161/+attachment/5342111/+files/casper-stop.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1865161 Title: Written "press return to shutdown the computer" does not appear. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1865161/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1865161] Re: Written "press return to shutdown the computer" does not appear.
seems after the installation, still can't use "plymouth dispaly-message" to send the text in desktop environment, maybe we can just debug in desktop enviroment... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1865161 Title: Written "press return to shutdown the computer" does not appear. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1865161/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1868701] Re: need to implement a reboot mechanism before oobe
** Changed in: oem-priority Importance: Undecided => High ** Changed in: oem-priority Status: New => Confirmed ** Changed in: oem-priority Status: Confirmed => Triaged -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1868701 Title: need to implement a reboot mechanism before oobe To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1868701/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1869819] [NEW] System can't detect external headset in the codec of Conexant
Public bug reported:
[Impact]
In some hp's devices, there are two audio jacks(one headset and one headphone)
in the audio interface which is using the codec of Conexant, and apparently
it's not working, the system can't detect the headset in current codec.
[Test Case]
1. Insert 3-ring headset into front audio port (headset icon)
2. Check System Setting->Sound->Output
[Expected result]
Can detect external headset
[Actual result]
Only shows internal speaker.
External headset microphone was detected.
Another front audio port (earphone icon) works fine.
[Regression Potential]
[Failure rate]
100%
[Additional information]
system-product-name: HP EliteDesk 800 G5 SFF
CPU: Intel(R) Core(TM) i7-9700 CPU @ 3.00GHz (8x)
GPU: 00:02.0 VGA compatible controller [0300]: Intel Corporation Device
[8086:3e98] (rev 02)
OS-version: 18.04
kernel-version: 4.15.0-1065-oem
pulseaudio-version: 1:11.1-1ubuntu7.2
Upstream Bug:
https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/272
** Affects: oem-priority
Importance: Critical
Assignee: hugh chao (hugh712)
Status: Confirmed
** Affects: oem-priority/bionic
Importance: Undecided
Status: New
** Package changed: pulseaudio (Ubuntu) => oem-priority
** Changed in: oem-priority
Assignee: (unassigned) => hugh chao (hugh712)
** Also affects: oem-priority/bionic
Importance: Undecided
Status: New
** Changed in: oem-priority
Status: New => Confirmed
** Changed in: oem-priority
Importance: Undecided => Critical
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1869819
Title:
System can't detect external headset in the codec of Conexant
To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1869819/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1868701] Re: need to implement a reboot mechanism before oobe
Verified with newest ubiquity 20.04.7, system actually rebooted after OOBE and works well. ** Changed in: oem-priority Status: Triaged => Fix Committed ** Changed in: ubiquity (Ubuntu) Status: Triaged => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1868701 Title: need to implement a reboot mechanism before oobe To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1868701/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1869819] Re: [SRU] System can't detect external headset in the codec of Conexant
I think 3 stripes = 4 rings, and we are talking the same thing, I will make it more clear ** Description changed: [Impact] In some hp's devices, there are two audio jacks(one headset and one headphone) in the audio interface which is using the codec of Conexant, and apparently it's not working, the system can't detect the headset in current codec. [Test Case] - 1. Insert 3-ring headset into front audio port (headset icon) + 1. Insert 4 rings(3 stripes) headset into front audio port (headset icon) 2. Check System Setting->Sound->Output [Expected result] Can detect external headset [Actual result] Only shows internal speaker. External headset microphone was detected. Another front audio port (earphone icon) works fine. [Regression Potential] Low. [Failure rate] 100% [Additional information] system-product-name: HP EliteDesk 800 G5 SFF CPU: Intel(R) Core(TM) i7-9700 CPU @ 3.00GHz (8x) GPU: 00:02.0 VGA compatible controller [0300]: Intel Corporation Device [8086:3e98] (rev 02) OS-version: 18.04 kernel-version: 4.15.0-1065-oem pulseaudio-version: 1:11.1-1ubuntu7.2 Upstream issue: https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/272 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1869819 Title: [SRU] System can't detect external headset in the codec of Conexant To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1869819/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1869819] Re: [SRU] System can't detect external headset in the codec of Conexant
** Description changed: [Impact] In some hp's devices, there are two audio jacks(one headset and one headphone) in the audio interface which is using the codec of Conexant, and apparently it's not working, the system can't detect the headset in current codec. [Test Case] 1. Insert 4 rings(3 stripes) headset into front audio port (headset icon) 2. Check System Setting->Sound->Output [Expected result] Can detect external headset [Actual result] Only shows internal speaker. External headset microphone was detected. Another front audio port (earphone icon) works fine. [Regression Potential] Low. [Failure rate] 100% [Additional information] system-product-name: HP EliteDesk 800 G5 SFF CPU: Intel(R) Core(TM) i7-9700 CPU @ 3.00GHz (8x) GPU: 00:02.0 VGA compatible controller [0300]: Intel Corporation Device [8086:3e98] (rev 02) OS-version: 18.04 kernel-version: 4.15.0-1065-oem pulseaudio-version: 1:11.1-1ubuntu7.2 Upstream issue: https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/272 + + PPA: https://launchpad.net/~hugh712/+archive/ubuntu/sru-1869819 ** Description changed: [Impact] In some hp's devices, there are two audio jacks(one headset and one headphone) in the audio interface which is using the codec of Conexant, and apparently it's not working, the system can't detect the headset in current codec. [Test Case] 1. Insert 4 rings(3 stripes) headset into front audio port (headset icon) 2. Check System Setting->Sound->Output [Expected result] Can detect external headset [Actual result] Only shows internal speaker. External headset microphone was detected. Another front audio port (earphone icon) works fine. [Regression Potential] Low. [Failure rate] 100% [Additional information] system-product-name: HP EliteDesk 800 G5 SFF CPU: Intel(R) Core(TM) i7-9700 CPU @ 3.00GHz (8x) GPU: 00:02.0 VGA compatible controller [0300]: Intel Corporation Device [8086:3e98] (rev 02) OS-version: 18.04 kernel-version: 4.15.0-1065-oem pulseaudio-version: 1:11.1-1ubuntu7.2 Upstream issue: https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/272 + Ubuntu-Focal-Source: + https://code.launchpad.net/~hugh712/ubuntu/+source/pulseaudio/+git/pulseaudio/+ref/focal-1869819 + PPA: https://launchpad.net/~hugh712/+archive/ubuntu/sru-1869819 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1869819 Title: [SRU] System can't detect external headset in the codec of Conexant To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1869819/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1804786] Re: Garbage occurred when Playing the video in the Ubuntu Desktop Guide
@Daniel, Sure I will provide the log tomorrow -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1804786 Title: Garbage occurred when Playing the video in the Ubuntu Desktop Guide To manage notifications about this bug go to: https://bugs.launchpad.net/yelp/+bug/1804786/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1804786] Re: Garbage occurred when Playing the video in the Ubuntu Desktop Guide
@Doug, please find attached the "lspcik.txt", and I didn't see anything on terminal after running below command: yelp help:gnome-help -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1804786 Title: Garbage occurred when Playing the video in the Ubuntu Desktop Guide To manage notifications about this bug go to: https://bugs.launchpad.net/yelp/+bug/1804786/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1804786] Re: Garbage occurred when Playing the video in the Ubuntu Desktop Guide
sorry I forgot to attach the file... ** Attachment added: "lspcik.txt" https://bugs.launchpad.net/ubuntu/+source/webkit2gtk/+bug/1804786/+attachment/5267033/+files/lspcik.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1804786 Title: Garbage occurred when Playing the video in the Ubuntu Desktop Guide To manage notifications about this bug go to: https://bugs.launchpad.net/yelp/+bug/1804786/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-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 Bugs, which is subscribed to 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 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-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 Bugs, which is subscribed to 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 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-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 Bugs, which is subscribed to 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 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-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 Bugs, which is subscribed to 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 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-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 Bugs, which is subscribed to 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 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-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 Bugs, which is subscribed to 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 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-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 Bugs, which is subscribed to 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 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-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 Bugs, which is subscribed to 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 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-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 Bugs, which is subscribed to 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 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1888841] Re: [MIR] oem-stella.cmit-tangela-meta
** No longer affects: ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/141 Title: [MIR] oem-stella.cmit-tangela-meta To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/141/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1890368] Re: [MIR] oem-stella.cmit-jynx-meta
** No longer affects: ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1890368 Title: [MIR] oem-stella.cmit-jynx-meta To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1890368/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1888836] Re: [MIR] oem-stella.cmit-diglett-meta
** No longer affects: ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/136 Title: [MIR] oem-stella.cmit-diglett-meta To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/136/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1888835] Re: [MIR] oem-stella.cmit-rhyhorn-meta
** No longer affects: ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/135 Title: [MIR] oem-stella.cmit-rhyhorn-meta To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/135/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1888840] Re: [MIR] oem-stella.cmit-tentacool-meta
** No longer affects: ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/140 Title: [MIR] oem-stella.cmit-tentacool-meta To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/140/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1888834] Re: [MIR] oem-stella.cmit-butterfree-meta
** No longer affects: ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/134 Title: [MIR] oem-stella.cmit-butterfree-meta To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/134/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1888839] Re: [MIR] oem-stella.cmit-machop-meta
** No longer affects: ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/139 Title: [MIR] oem-stella.cmit-machop-meta To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/139/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1906653] Re: Backport systemd to make uevents "sticky"
@Dan I see, thank you anyway :) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1906653 Title: Backport systemd to make uevents "sticky" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1906653/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1893300] Re: The status of cups still shows idle when the printer has been unplugged
currently the syspath for udev-configure-printer is too specific level as: /devices/pci:00/:00:14.0/usb1/1-5 But current path can be as below for removing /devices/pci:00/:00:14.0/usb1/1-5:1.0 or /devices/pci:00/:00:14.0/usb1/1-5:1.0/usbmisc/lp0 so the printer can't be removed, I think the problem is this program - udev-configure-printer, so let me tried to make it more flexible... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1893300 Title: The status of cups still shows idle when the printer has been unplugged To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1893300/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1893300] Re: The status of cups still shows idle when the printer has been unplugged
** Description changed: [ Impact ] After printers (non-ippusb protocal) have been disconnected, the status of cups still shows "idle" instead of "disabled", so seems the disconnected procedure hasn't worked well. [ Test Case ] 1. Connect the printer (non-ippusb protocal)(which isn't 070104) with any 20.04 machine 2. Wait for the status of cups became "Idle" (lpstat -p) 3. Unplug the cable of the printer 4. Check the status of cups again. (lpstat -p) [Expected result] The status should show disabled. [Actual result] The status shows idle. [info] Target: HP LaserJet Pro203dw HP Officejet 100 Mobile Printer HP Officeject 200 Mobile Printer + Brother HL-2250DN + samsung ML-331x ** Description changed: [ Impact ] After printers (non-ippusb protocal) have been disconnected, the status of cups still shows "idle" instead of "disabled", so seems the disconnected procedure hasn't worked well. [ Test Case ] 1. Connect the printer (non-ippusb protocal)(which isn't 070104) with any 20.04 machine 2. Wait for the status of cups became "Idle" (lpstat -p) 3. Unplug the cable of the printer 4. Check the status of cups again. (lpstat -p) [Expected result] The status should show disabled. [Actual result] The status shows idle. [info] Target: HP LaserJet Pro203dw HP Officejet 100 Mobile Printer HP Officeject 200 Mobile Printer Brother HL-2250DN - samsung ML-331x + Samsung ML-331x -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1893300 Title: The status of cups still shows idle when the printer has been unplugged To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1893300/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1893300] Re: The status of cups still shows idle when the printer has been unplugged
** Changed in: oem-priority Status: Confirmed => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1893300 Title: The status of cups still shows idle when the printer has been unplugged To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1893300/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1893300] Re: The status of cups still shows idle when the printer has been unplugged
The idea is : 1. check if the path provided by map is a subset of removing device path eg. /devices/pci:00/:00:14.0/usb1/1-5 is a subset of /devices/pci:00/:00:14.0/usb1/1-5:1.0 2. check if the exist of this device eg. stat /sys/devices/pci:00/:00:14.0/usb1/1-5 3. if this device is not exist, then remove.. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1893300 Title: The status of cups still shows idle when the printer has been unplugged To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1893300/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1893300] Re: The status of cups still shows idle when the printer has been unplugged
** Description changed: [ Impact ] After printers (non-ippusb protocal) have been disconnected, the status of cups still shows "idle" instead of "disabled", so seems the disconnected procedure hasn't worked well. [ Test Case ] 1. Connect the printer (non-ippusb protocal)(which isn't 070104) with any 20.04 machine 2. Wait for the status of cups became "Idle" (lpstat -p) 3. Unplug the cable of the printer 4. Check the status of cups again. (lpstat -p) [Expected result] The status should show disabled. [Actual result] The status shows idle. [info] Target: HP LaserJet Pro203dw HP Officejet 100 Mobile Printer HP Officeject 200 Mobile Printer Brother HL-2250DN Samsung ML-331x + + Upstream Bug: https://github.com/OpenPrinting/system-config- + printer/issues/182 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1893300 Title: The status of cups still shows idle when the printer has been unplugged To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1893300/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-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 Bugs, which is subscribed to 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 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-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 Bugs, which is subscribed to 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 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1882347] Re: [needs-packaging] [MIR] oem-stella.cmit-abra-meta
** Changed in: oem-priority Status: Triaged => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1882347 Title: [needs-packaging] [MIR] oem-stella.cmit-abra-meta To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1882347/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1883846] Re: hwdb: Mask rfkill event from intel-hid on HP platforms
** Changed in: oem-priority Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1883846 Title: hwdb: Mask rfkill event from intel-hid on HP platforms To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1883846/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1883846] Re: hwdb: Mask rfkill event from intel-hid on HP platforms
** Changed in: oem-priority Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1883846 Title: hwdb: Mask rfkill event from intel-hid on HP platforms To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1883846/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1888845] Re: [MIR] oem-stella.cmit-eevee-meta
** Changed in: oem-priority Status: New => Confirmed ** Patch added: "oem-stella.cmit-pinsir-meta_20.04~ubuntu1.debdiff" https://bugs.launchpad.net/oem-priority/+bug/145/+attachment/5396485/+files/oem-stella.cmit-pinsir-meta_20.04~ubuntu1.debdiff ** Information type changed from Proprietary to Public ** Also affects: ubuntu Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/145 Title: [MIR] oem-stella.cmit-eevee-meta To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/145/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1888836] Re: [MIR] oem-stella.cmit-diglett-meta
** Information type changed from Proprietary to Public ** Also affects: ubuntu Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/136 Title: [MIR] oem-stella.cmit-diglett-meta To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/136/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1888841] Re: [MIR] oem-stella.cmit-tangela-meta
** Information type changed from Proprietary to Public ** Also affects: ubuntu Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/141 Title: [MIR] oem-stella.cmit-tangela-meta To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/141/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1888844] Re: [MIR] oem-stella.cmit-staryu-meta
** Changed in: oem-priority Status: New => Confirmed ** Patch added: "oem-stella.cmit-staryu-meta_20.04~ubuntu1.debdiff" https://bugs.launchpad.net/oem-priority/+bug/144/+attachment/5396486/+files/oem-stella.cmit-staryu-meta_20.04~ubuntu1.debdiff ** Information type changed from Proprietary to Public ** Also affects: ubuntu Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/144 Title: [MIR] oem-stella.cmit-staryu-meta To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/144/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1888840] Re: [MIR] oem-stella.cmit-tentacool-meta
** Information type changed from Proprietary to Public ** Also affects: ubuntu Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/140 Title: [MIR] oem-stella.cmit-tentacool-meta To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/140/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1888448] Re: [MIR] oem-stella.cmit-meowth-meta
** Information type changed from Proprietary to Public ** Also affects: ubuntu Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1888448 Title: [MIR] oem-stella.cmit-meowth-meta To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1888448/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1888835] Re: [MIR] oem-stella.cmit-rhyhorn-meta
** Information type changed from Proprietary to Public ** Also affects: ubuntu Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/135 Title: [MIR] oem-stella.cmit-rhyhorn-meta To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/135/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1888839] Re: [MIR] oem-stella.cmit-machop-meta
** Information type changed from Proprietary to Public ** Also affects: ubuntu Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/139 Title: [MIR] oem-stella.cmit-machop-meta To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/139/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1888843] Re: [MIR] oem-stella.cmit-pinsir-meta
** Changed in: oem-priority Status: New => Confirmed ** Patch added: "oem-stella.cmit-eevee-meta_20.04~ubuntu1.debdiff" https://bugs.launchpad.net/oem-priority/+bug/143/+attachment/5396487/+files/oem-stella.cmit-eevee-meta_20.04~ubuntu1.debdiff ** Information type changed from Proprietary to Public ** Also affects: ubuntu Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/143 Title: [MIR] oem-stella.cmit-pinsir-meta To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/143/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1888834] Re: [MIR] oem-stella.cmit-butterfree-meta
** Information type changed from Proprietary to Public ** Also affects: ubuntu Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/134 Title: [MIR] oem-stella.cmit-butterfree-meta To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/134/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1888843] Re: [MIR] oem-stella.cmit-pinsir-meta
** Patch added: "oem-stella.cmit-pinsir-meta_20.04_ubuntu1.debdiff" https://bugs.launchpad.net/ubuntu/+bug/143/+attachment/5396496/+files/oem-stella.cmit-pinsir-meta_20.04_ubuntu1.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/143 Title: [MIR] oem-stella.cmit-pinsir-meta To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/143/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1888845] Re: [MIR] oem-stella.cmit-eevee-meta
** Patch added: "oem-stella.cmit-eevee-meta_20.04_ubuntu1.debdiff" https://bugs.launchpad.net/ubuntu/+bug/145/+attachment/5396494/+files/oem-stella.cmit-eevee-meta_20.04_ubuntu1.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/145 Title: [MIR] oem-stella.cmit-eevee-meta To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/145/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1888845] Re: [MIR] oem-stella.cmit-eevee-meta
https://code.launchpad.net/~oem-solutions-engineers/pc-enablement/+git /oem-stella-projects-meta/+ref/cmit.eevee-focal-ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/145 Title: [MIR] oem-stella.cmit-eevee-meta To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/145/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1888844] Re: [MIR] oem-stella.cmit-staryu-meta
https://code.launchpad.net/~oem-solutions-engineers/pc-enablement/+git /oem-stella-projects-meta/+ref/cmit.staryu-focal-ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/144 Title: [MIR] oem-stella.cmit-staryu-meta To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/144/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1888843] Re: [MIR] oem-stella.cmit-pinsir-meta
https://code.launchpad.net/~oem-solutions-engineers/pc-enablement/+git /oem-stella-projects-meta/+ref/cmit.pinsir-focal-ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/143 Title: [MIR] oem-stella.cmit-pinsir-meta To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/143/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
