waiting for the reporter to add the name of package,
change the status to incomplete.
** Changed in: ubuntu
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1172494
Thank you for your suggestion. However, the changes you are requesting
aren't really a bug and require more discussion, which should be done on
an appropriate mailing list or forum.
http://www.ubuntu.com/support/community/mailinglists might be a good
start for determining which mailing list to
Bugs without a package
Sometimes bugs will be reported just using the "Ubuntu" package. This is not
the best place for the bug though and we should encourage bug reporters to
report the bug against the correct package by pointing them at some
documentation. Keep in mind PKGNAME is a
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This bug did not have a package associated with it, which
is important for ensuring that it gets looked at by the proper
developers. You can learn more about finding the right package at
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
** 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
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
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
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.
@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:
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.
@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
@Robert,
Is there any chance you can review this mp in #15? many thanks
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1853584
Title:
[18.04]Not able to adjust Audio input UI volume after
@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
** 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
** 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
@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
@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
@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
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
@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
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
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
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
** 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
** 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
** 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
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 Ubu
** 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
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.
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
** 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
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.
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.
** 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:
[ 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.
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.
** 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
** 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
** Tags added: oem-priority stella
--
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:
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
@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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1869819
Title:
[SRU] System can't detect external headset in the codec
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 Ubuntu
Bugs, which is subscribed
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
** Changed in: pulseaudio (Ubuntu Bionic)
Status: Triaged => 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/1869819
Title:
[SRU] System can't detect external headset in the codec
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
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
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
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
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
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.
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.
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.
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
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.
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
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.
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.
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
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
** 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
** 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.
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
** 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
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 Ubuntu
Bugs, 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 Ubuntu
Bugs, which is
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:
@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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1869819
Title:
[SRU] System can't detect external headset in the codec
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,
What do you think on #21, it's a regression or not?
--
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
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1869819
Title:
[SRU] System can't detect external
** Description changed:
+ [Impact]
+
Although live build has been used in both oem and foundation team, but
the main different is that:
- [Foundation]
+ --Foundation--
Only for squashfs, cd-image will be used after that, the image created by
live build will not be used directly.
-
upload debdiff for focal
** Summary changed:
- [live-build] can not customize the mkisoimage option
+ [SRU][live-build] can not customize the mkisoimage option
** Patch added: "3.0~a57-1ubuntu39.debdiff"
** Description changed:
[Impact]
Although live build has been used in both oem and foundation team, but
the main different is that:
--Foundation--
- Only for squashfs, cd-image will be used after that, the image created by
live build will not be used directly.
+ Only for squashfs,
Assignee: (unassigned) => hugh chao (hugh712)
** Changed in: oem-priority
Status: New => Confirmed
** Changed in: oem-priority/focal
Status: New => Confirmed
** Changed in: oem-priority/focal
Importance: Undecided => High
** Information type changed from
Public bug reported:
[Summary]
Before 20.04, when user finished the 1st stage of installation, the message
『please remove the installation medium then reboot』or 『please remove
installation medium then press enter』 will be shown on the screen.
But since 20.04, due to the using of
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1867909/+attachment/5338368/+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/1867909
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1867909/+attachment/5338366/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1867909
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1867909/+attachment/5338371/+files/UdevDb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1867909
Title:
apport information
** Tags added: apport-collected focal
** Description changed:
[Summary]
Before 20.04, when user finished the 1st stage of installation, the message
『please remove the installation medium then reboot』or 『please remove
installation medium then press enter』 will be shown
apport information
** Attachment added: "EtcDefaultGrub.txt"
https://bugs.launchpad.net/bugs/1867909/+attachment/5338361/+files/EtcDefaultGrub.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "Lsusb-v.txt"
https://bugs.launchpad.net/bugs/1867909/+attachment/5338365/+files/Lsusb-v.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1867909
Title:
apport information
** Attachment added: "Dependencies.txt"
https://bugs.launchpad.net/bugs/1867909/+attachment/5338360/+files/Dependencies.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1867909/+attachment/5338369/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1867909/+attachment/5338370/+files/ProcModules.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1867909
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1867909/+attachment/5338362/+files/Lspci.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1867909
Title:
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1867909/+attachment/5338363/+files/Lsusb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1867909
Title:
apport information
** Attachment added: "Lsusb-t.txt"
https://bugs.launchpad.net/bugs/1867909/+attachment/5338364/+files/Lsusb-t.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1867909
Title:
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1867909/+attachment/5338367/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Description changed:
[Summary]
Before 20.04, when user finished the 1st stage of installation, the message
『please remove the installation medium then reboot』or 『please remove
installation medium then press enter』 will be shown on the screen.
But since 20.04, due to the using of
** Description changed:
[Summary]
Before 20.04, when user finished the 1st stage of installation, the message
『please remove the installation medium then reboot』or 『please remove
installation medium then press enter』 will be shown on the screen.
But since 20.04, due to the using of
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)
https://code.launchpad.net/~hugh712/ubiquity/+git/ubiquity/+merge/380808
--
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
*** This bug is a duplicate of bug 1865161 ***
https://bugs.launchpad.net/bugs/1865161
** Description changed:
[Summary]
Before 20.04, when user finished the 1st stage of installation, the message
『please remove the installation medium then reboot』or 『please remove
installation medium
1 - 100 of 225 matches
Mail list logo
