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
got it, thank you.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ubuntu-meta in Ubuntu.
https://bugs.launchpad.net/bugs/1981109
Title:
server image pulls in ModemManager via fwupd, consumes 25MiB RAM in
every container
Status in
Is this means fwupd will also be removed from stock server image?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ubuntu-meta in Ubuntu.
https://bugs.launchpad.net/bugs/1981109
Title:
server image pulls in ModemManager via fwupd,
** 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 Desktop
Packages, which is subscribed to system-config-printer in Ubuntu.
** Tags removed: verification-needed
--
You received this bug notification because you are a member of Desktop
Packages, 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
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 Desktop
Packages, which is subscribed to system-config-printer in Ubuntu.
https://bugs.launchpad.net/bugs/1893300
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
@Ł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 ]
** Changed in: oem-priority
Status: In Progress => Triaged
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to system-config-printer in Ubuntu.
https://bugs.launchpad.net/bugs/1893300
Title:
The status of cups still shows idle when
** Tags added: verification-needed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to system-config-printer in Ubuntu.
https://bugs.launchpad.net/bugs/1893300
Title:
The status of cups still shows idle when the printer has been
And this is the package diff for focal
** Patch added: "system-config-printer-focal.diff"
https://bugs.launchpad.net/oem-priority/+bug/1893300/+attachment/5430871/+files/system-config-printer-focal.diff
--
You received this bug notification because you are a member of Desktop
Packages,
Here is the package diff for groovy
** Patch added: "system-config-printer-groovy.diff"
https://bugs.launchpad.net/oem-priority/+bug/1893300/+attachment/5430870/+files/system-config-printer-groovy.diff
--
You received this bug notification because you are a member of Desktop
Packages, which
** 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
** 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
Hi Till,
The PR is already there as
https://github.com/OpenPrinting/system-config-printer/pull/183
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to system-config-printer in Ubuntu.
https://bugs.launchpad.net/bugs/1893300
Title:
The
** 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
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
** Changed in: oem-priority
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to system-config-printer in Ubuntu.
https://bugs.launchpad.net/bugs/1893300
Title:
The status of cups still shows idle
** 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
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
** 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 Desktop
Packages, which is subscribed to gnome-session in Ubuntu.
https://bugs.launchpad.net/bugs/1845801
** Also affects: system-config-printer (Ubuntu)
Importance: Undecided
Status: New
** 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
can't not reproduce this issue in 20.04,
but I did observe this issue in 14.04
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to system-config-printer in Ubuntu.
https://bugs.launchpad.net/bugs/1739417
Title:
Failed to add HP203dw
** Changed in: oem-priority
Assignee: hugh chao (hugh712) => jeremyszu (os369510)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-session in Ubuntu.
https://bugs.launchpad.net/bugs/1845801
Title:
[nvidia] Automatic lo
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 Desktop
Packages, which is subscribed to
** Changed in: oem-priority
Status: In Progress => Triaged
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-session in Ubuntu.
https://bugs.launchpad.net/bugs/1845801
Title:
[nvidia] Automatic login fails and then all
** 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
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"
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.
'''
** 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 Desktop
Packages, which is
I'll start the SRU for this issue soon
--
You received this bug notification because you are a member of Desktop
Packages, 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.
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
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 Desktop
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 Desktop
** 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 Desktop
Packages, which is subscribed to
** Tags added: sutton
--
You received this bug notification because you are a member of Desktop
Packages, 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
** Tags added: oem-priority stella
--
You received this bug notification because you are a member of Desktop
Packages, 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
sorry, I shouldn't use such unclear word,
I did check the version with Danny yesterday,
pulseaudio version 1:11.1-1ubuntu7.8 works well at the same machine.
** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic
--
You received this bug notification because you are
it's 1:11.1-1ubuntu7.8 in #40, I think it's a typo
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1869819
Title:
[SRU] System can't detect external headset in the codec of
need to finish this one[0] first
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1876065
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1869819
Title:
[SRU] System
currently, @kai is working on the new patch..
** Changed in: pulseaudio (Ubuntu Bionic)
Status: Fix Committed => In Progress
** Tags added: regression-proposed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in
@Kai,
What do you think on #21, it's a regression or not?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1869819
Title:
[SRU] System can't detect external headset in the codec of
For what I observed (both focal and bionic), I'm not sure (and I think
it's not) it's a regression, due the the bug it's already there before
this patch. And I tried one hp dm, one hp sff, one hp laptop and one
dell laptop, only can be reproduced in Dell laptop.
For what I observed:
@Kai,
Please help to take a look on #18,
then let's decide next step, thanks.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1869819
Title:
[SRU] System can't detect external
verified pulseaudio version - 1:11.1-1ubuntu7.6 in a dell laptop[0]
which only has one headset jack, works well, didn't find any Regression
potential.
[0] https://www.dell.com/en-us/work/shop/dell-laptops-and-
notebooks/latitude-5501-business-laptop/spd/latitude-15-5501-laptop
** Tags removed:
verified pulseaudio version - 1:11.1-1ubuntu7.6 in a hp dm[0] which has
dual front jacks, works well, didn't find any Regression potential.
[0]https://www8.hp.com/h20195/v2/GetPDF.aspx/4AA7-5436EEAP.pdf
--
You received this bug notification because you are a member of Desktop
Packages, which is
verified pulseaudio version - 1:11.1-1ubuntu7.6 in a hp sff[0] which has
dual front jacks, works well, didn't find any Regression potential.
[0]https://www8.hp.com/h20195/v2/GetPDF.aspx/4AA7-5395EEAP.pdf
--
You received this bug notification because you are a member of Desktop
Packages, which
@Seb
Sorry for the inconvenience, I will be more careful next time,
thank you!
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1869819
Title:
[SRU] System can't detect external
here you go,
upload patch for bionic again in debian/patches
** Patch added: "dual-jacks.patch"
https://bugs.launchpad.net/oem-priority/+bug/1869819/+attachment/5350081/+files/dual-jacks.patch
--
You received this bug notification because you are a member of Desktop
Packages, which is
upload patch for bionic
** Patch added: "dual-jacks-bionic.patch"
https://bugs.launchpad.net/oem-priority/+bug/1869819/+attachment/5349710/+files/dual-jacks-bionic.patch
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in
** Changed in: pulseaudio (Ubuntu Bionic)
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1869819
Title:
[SRU] System can't detect external
upload patch for focal
** Patch added: "dual-jacks.patch"
https://bugs.launchpad.net/oem-priority/+bug/1869819/+attachment/5348635/+files/dual-jacks.patch
** Tags added: verification-needed
** Changed in: pulseaudio (Ubuntu Focal)
Status: Triaged => In Progress
--
You received this
** 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
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
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
Statu
** Changed in: oem-priority
Status: New => Won't Fix
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/1868260
Title:
Change sleep-inactive-ac-timeout to 1200 to
Ok, I will override the setting in oem base image, thanks
--
You received this bug notification because you are a member of Desktop
Packages, 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
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):
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):
" 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
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)
** 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 Desktop
Packages, which is subscribed to gnome-control-center in Ubuntu.
** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1853584
Title:
[SRU]Not able to adjust
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 Desktop
Packages, which is subscribed to
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 Desktop
Packages, which is subscribed to
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 Desktop
Packages, which is subscribed to
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 Desktop
Packages, which
** 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
hanged 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 Desktop
** 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
** 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
** 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
** 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
** Tags added: bionic
--
You received this bug notification because you are a member of Desktop
Packages, 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
Status in
** 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.
** 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
** 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
** Tags added: originate-from-1806835
** Tags added: stella
--
You received this bug notification because you are a member of Desktop
Packages, 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
@Sebastien,
Would you please help to backport there two commits in #15, thanks.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1853584
Title:
[18.04]Not able to adjust
@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 Desktop
Packages, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1853584
Title:
[18.04]Not able to adjust Audio
https://gitlab.gnome.org/GNOME/gnome-control-center/merge_requests/641
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1853584
Title:
[18.04]Not able to adjust Audio
@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 Desktop
Packages, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1853584
@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
@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 Desktop
Packages,
@Sebastien
Yes, What I meant was gnome-control-center
--
You received this bug notification because you are a member of Desktop
Packages, 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
pavucontrol works good, I will try to backport this package to bionic,
thanks.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1853584
Title:
[18.04]Not able to adjust
** 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 Desktop
Packages, which is subscribed to
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 Desktop
Packages, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1853584
Title:
[18.04]Not
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
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 Desktop
Packages, which is subscribed to
@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 Desktop
Packages, which is subscribed to webkit2gtk in Ubuntu.
@Daniel,
Sure I will provide the log tomorrow
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to webkit2gtk in Ubuntu.
https://bugs.launchpad.net/bugs/1804786
Title:
Garbage occurred when Playing the video in the Ubuntu Desktop Guide
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 Desktop
Packages, which is subscribed to gnome-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/1772811
Title:
different behaviors for switch
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 Desktop
Packages, which is subscribed to gnome-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/1772811
Title:
different behaviors for switch
** Tags added: stella
--
You received this bug notification because you are a member of Desktop
Packages, 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
Status in OEM
95 matches
Mail list logo
