** Changed in: oem-priority
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1893899
Title:
update alsa/audio related infomation
** Tags added: fr-692
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1893899
Title:
update alsa/audio related infomation collection code in apport
Status in OEM Priority
This bug was fixed in the package apport - 2.20.11-0ubuntu47
---
apport (2.20.11-0ubuntu47) groovy; urgency=medium
[ Tiago Stürmer Daitx ]
* apport/ui.py: improve message when origin check fails as it can be
caused by empty apt list - candidate is limited to dpkg and we can't
** Branch linked: lp:~ubuntu-core-dev/ubuntu/groovy/apport/ubuntu
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1893899
Title:
update alsa/audio related infomation
I've gone ahead and uploaded this for Groovy but renamed the key pa-info
to PaInfo so that it is consistent with the naming of other keys.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
Reply #7, no, I don't know how to extract alsa-info from output of pa-
info.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1893899
Title:
update alsa/audio related
Is there a quick and clean way to extract alsa-info from output of pa-
info?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1893899
Title:
update alsa/audio related
the pa-info already includes calling the alsa-info.sh, it is ok to
remove the alsa-info.
But it is better to keep the alsa-info, since the log of alsa-info is
cleaner than the log of pa-info, pa-info includes many pulseaudio level
logs. And If we want to exchange the log with upstream developers,
By adding in a call to '/usr/bin/pa-info' in apport/hookutils.py there
ends up being duplicate information in the apport created report as
'/usr/bin/pa-info' calls 'alsa-info' which was already included in the
report. How do you feel about removing the calls to 'alsa-info' and just
using
** Tags removed: rls-gg-incoming
** Also affects: apport (Ubuntu Groovy)
Importance: Undecided
Status: Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: apport (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
** Summary changed:
- update alsa/audio realted infomation collection code in apport
+ update alsa/audio related infomation collection code in apport
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
12 matches
Mail list logo
