** Description changed:
chtmax98090 intel HD audio device doesn't work out of the box after
installing ubuntu (from 14.04 to 18.04). It shows "Dummy Output" on
audio devices.
Audio options shows device and it works if I do this:
- git clone https://github.com/plbossart/UCM.git
-
I am running Ubunti 18.04.2 in an Enhanced Hyper-V session -
https://www.zdnet.com/article/windows-10-tip-run-ubuntu-linux-in-an-
enhanced-hyper-v-session/.
I am facing the same problem.
Tried
Switching input method between xim and ibus
Changing theme to Adwaita
Nothing works for me.
Given
Internal audio is disabled in the BIOS.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1833652
Title:
[SB-XFi - Creative X-Fi, playback] No sound at all
Status in
Public bug reported:
Installed a new X-Fi sound card, but no audio is being heard during
playback on Ubuntu 18.04.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 4.18.0-22.23~18.04.1-generic 4.18.20
Uname: Linux 4.18.0-22-generic
Please reproduce the freeze again, then reboot and run:
journalctl -b-1 > prevboot.txt
and send us the file 'prevboot.txt'.
** Tags added: amdgpu
** Summary changed:
- screen freeze after suspend
+ [amdgpu] screen freeze after suspend
** Package changed: xorg (Ubuntu) =>
*** This bug is a duplicate of bug 1833527 ***
https://bugs.launchpad.net/bugs/1833527
** This bug has been marked a duplicate of bug 1833527
in gnome settings audio section does not see any sound card
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
It's good if you can't reproduce a bug any more. Although your
AlsaInfo.txt shows the main problem was that pulseaudio wasn't running
at all:
Pulseaudio:
Installed - Yes (/usr/bin/pulseaudio)
Running - No
Let us know if you wish to investigate that problem again.
** Changed in:
*** This bug is a duplicate of bug 1793640 ***
https://bugs.launchpad.net/bugs/1793640
** This bug has been marked a duplicate of bug 1793640
Pulseaudio fails to detect sound card, while timidity is installed
--
You received this bug notification because you are a member of Ubuntu
Touch
@ahasenack, I found this post (took plenty of Google foo) but it was
helpful.
For anyone else, 18.04 LTS STILL has this issue. The following fixed
it:
After=network-online.target
Wants=network-online.target
These are in my [Unit] section at the top of
/etc/systemd/system/sshd.service
[Unit]
I did not do anything special outside of the steps in my repro to
specifically enable SSL in the nginx configs, but should that matter in
terms of running these SSL tests? With the Dockerfile in the description
as it is, I can already see in the test output that SSL tests are
running and
** Also affects: lxc (Ubuntu)
Importance: Undecided
Status: New
** Changed in: systemd (Ubuntu Bionic)
Status: In Progress => Invalid
** Changed in: systemd (Ubuntu Eoan)
Status: In Progress => Invalid
** Changed in: lxc (Ubuntu Bionic)
Status: New => Incomplete
This bug was fixed in the package systemd - 237-3ubuntu10.23
---
systemd (237-3ubuntu10.23) bionic; urgency=medium
* d/p/resolved-do-not-hit-CNAME-in-NODATA.patch:
- fix stub resolver cache (LP: #1818527)
-- Heitor Alves de Siqueira Tue, 04 Jun 2019
15:54:24 -0300
**
The verification of the Stable Release Update for systemd has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a
This bug was fixed in the package python-tornado - 4.5.3-1ubuntu0.1
---
python-tornado (4.5.3-1ubuntu0.1) bionic; urgency=medium
* Cherrypick patches from python-tornado4 4.5.3-2 package, to
enable OpenSSL 1.1.1 support LP: #1797386:
- New_test_crt.patch regenerate stronger
Public bug reported:
Ubuntu 19.04
Processor Intel® Core™ i5-3337U CPU @ 1.80GHz × 4
Gnome 3.32.1
OS: 64-bit
My speakers are recognized by the system however no sound comes out of them.
This happens wither plugging them to my laptop or to my projector which is
connected via HDMI. This is how
Looking at autopkgtest regressions for python-tornado
http://autopkgtest.ubuntu.com/packages/b/bdfproxy/bionic/ppc64el has
never passed on bionic.
Can sru team please commit badtest hint for bdfproxy and release python-
tarnado?
--
You received this bug notification because you are a member of
** Description changed:
After upgrading to Ubuntu 19.04, I started experiencing sporadic crashes
in kodi when turning my AV receiver on. Ubuntu 19.04 upgraded alsa-
- plugins to 1.1.8. For alsa-plugins >= 1.1.8, the ALSA jack plugin is
+ plugins to 1.1.8. For alsa-plugins >= 1.1.7, the ALSA
Hello Amine, or anyone else affected,
Accepted openssl into disco-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/openssl/1.1.1b-
1ubuntu2.4 in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
Public bug reported:
It's most likely amdgup driver needs an upgrade. Problem occurs since
kernel upgrade to 5.0
ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: xorg 1:7.7+19ubuntu12
ProcVersionSignature: Ubuntu 5.0.0-18.19-generic 5.0.12
Uname: Linux 5.0.0-18-generic x86_64
ApportVersion:
Hello Amine, or anyone else affected,
Accepted openssl into cosmic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/openssl/1.1.1-1ubuntu2.5 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
Hello Amine, or anyone else affected,
Accepted openssl into bionic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/openssl/1.1.1-1ubuntu2.1~18.04.4 in
a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
downgraded bionic lxd container to bionic release / security packages only.
installing libssl1.1 from -updates fails with:
dpkg: error processing package libssl1.1:amd64 (--configure):
installed libssl1.1:amd64 package post-installation script subprocess returned
error exit status 10
Processing
Removing packages from eoan:
gnome-vfs 1:2.24.4-6.1ubuntu2 in eoan
libgnomevfs2-0 1:2.24.4-6.1ubuntu2 in eoan amd64
libgnomevfs2-0 1:2.24.4-6.1ubuntu2 in eoan arm64
libgnomevfs2-0 1:2.24.4-6.1ubuntu2 in eoan armhf
Removing packages from eoan:
libgnome 2.32.1-6 in eoan
libgnome-2-0 2.32.1-6 in eoan amd64
libgnome-2-0 2.32.1-6 in eoan arm64
libgnome-2-0 2.32.1-6 in eoan armhf
libgnome-2-0 2.32.1-6 in eoan i386
libgnome-2-0
Removing packages from eoan:
orbit2 1:2.14.19-4 in eoan
liborbit-2-0 1:2.14.19-4 in eoan amd64
liborbit-2-0 1:2.14.19-4 in eoan arm64
liborbit-2-0 1:2.14.19-4 in eoan armhf
liborbit-2-0 1:2.14.19-4 in eoan i386
Removing packages from eoan:
libbonobo 2.32.1-3 in eoan
libbonobo2-0 2.32.1-3 in eoan amd64
libbonobo2-0 2.32.1-3 in eoan arm64
libbonobo2-0 2.32.1-3 in eoan armhf
libbonobo2-0 2.32.1-3 in eoan i386
Removing packages from eoan:
libbonoboui 2.24.5-4 in eoan
libbonoboui2-0 2.24.5-4 in eoan amd64
libbonoboui2-0 2.24.5-4 in eoan arm64
libbonoboui2-0 2.24.5-4 in eoan armhf
libbonoboui2-0 2.24.5-4 in eoan i386
Removing packages from eoan:
libgnome-keyring 3.12.0-1build1 in eoan
gir1.2-gnomekeyring-1.0 3.12.0-1build1 in eoan amd64
gir1.2-gnomekeyring-1.0 3.12.0-1build1 in eoan arm64
gir1.2-gnomekeyring-1.0 3.12.0-1build1 in eoan armhf
For initramfs-tools... please provide steps to reproduce the issue of
when initrds are expected to be created and are not, with steps how to
get in such situation (e.g. rm /boot/initrd*; update-initramfs...)
*without* requiring to use calamares, or specific images. ie. from any
regular normal
This bug was fixed in the package openssl - 1.1.1-1ubuntu2.1~18.04.3
---
openssl (1.1.1-1ubuntu2.1~18.04.3) bionic; urgency=medium
* Fix path to Xorg for reboot notifications on desktop. LP: #1832421
* Cherrypick upstream fix to allow succesful init of libssl and
libcrypto
Ok I managed to fix it
rm -rf ~/.config/chrome-remote-desktop/pulse*
Looks like chrome remote desktop app (which i was using) took over my
sound card in gnome settings, weird :/
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed
The verification of the Stable Release Update for openssl has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a
Ok I managed to fix it
rm -rf ~/.config/chrome-remote-desktop/pulse*
Looks like chrome remote desktop app (which i was using) took over my
sound card in gnome settings, weird :/
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed
The verification of the Stable Release Update for openssl has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a
This bug was fixed in the package openssl - 1.1.1-1ubuntu2.1~18.04.3
---
openssl (1.1.1-1ubuntu2.1~18.04.3) bionic; urgency=medium
* Fix path to Xorg for reboot notifications on desktop. LP: #1832421
* Cherrypick upstream fix to allow succesful init of libssl and
libcrypto
The bug was only fixed in our Calamares configuration and still needs to
be fixed in initramfs-tools.
Adjusting bug statuses appropriately and adding the release tag. I'll
ping vorlon and xnox on IRC to get their take.
** Also affects: calamares-settings-ubuntu (Ubuntu)
Importance: Undecided
** Changed in: lvm2 (Ubuntu Eoan)
Milestone: ubuntu-16.03 => None
** Changed in: lvm2 (Ubuntu Eoan)
Assignee: Andy Whitcroft (apw) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lvm2 in Ubuntu.
Public bug reported:
fstrim.timer always triggers at 00:00:
$ systemctl list-timers fstrim.timer
NEXT LEFTLAST PASSED
UNIT ACTIVATES
Mon 2019-06-24 00:00:00 CEST 3 days left Mon 2019-06-17 00:00:06 CEST 3 days
ago
** Description changed:
+ [Impact]
+
+ * Systems that have in error removed debconf database fail to upgrade
+ libssl1.1 (as e.g. is known to be done in some vagrant boxes)
+
+ * libssl1.1 tries to use debconf template from libc6 package, but
+ doesn't ship one by itself as it should for
** Tags added: server-next
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1819074
Title:
Keepalived < 2.0.x in Ubuntu 18.04 LTS not compatible with systemd-
networkd
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: openssl (Ubuntu Disco)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssl in Ubuntu.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: openssl (Ubuntu Cosmic)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssl in Ubuntu.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: openssl (Ubuntu Bionic)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssl in Ubuntu.
*** This bug is a duplicate of bug 1832919 ***
https://bugs.launchpad.net/bugs/1832919
Thank you for the recommendation Dimitri, I think I understand the
implications, just wanted to share a way to keep a non interactive
installation for those affected, however indeed I think that's a better
This sounds more like an OpenSSL issue than an NGINX one. Until such
investigations are complete to confirm this and rule out NGINX as the
problem, I am marking this as 'Incomplete' in NGINX in Ubuntu.
** Changed in: nginx (Ubuntu)
Status: New => Incomplete
--
You received this bug
I finally posted on the pulseaudio list and someone referred me to this
bug:
https://bugs.launchpad.net/ubuntu/+source/timidity/+bug/1793640
I uninstalled timidity and that seems to have fixed the problem.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
Default nginx configurations **in Ubuntu** do not enable SSL by default.
Have you passed an SSL enabled config to your docker container first?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssl in Ubuntu.
** Tags removed: rls-bb-incoming
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lvm2 in Ubuntu.
https://bugs.launchpad.net/bugs/1509717
Title:
Wily LVM-RAID1 – md: personality for level 1 is not loaded
Status in linux
** Also affects: openssl (Ubuntu Eoan)
Importance: Undecided
Status: Confirmed
** Also affects: openssl (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: openssl (Ubuntu Disco)
Importance: Undecided
Status: New
** Also affects: openssl (Ubuntu
I'd add that it seems to me the "upstream" mode of Ubuntu CI doesn't
seem to be actively maintained because unlike the other CI systems used
upstream (which are usually fixed almost immediately), it can be broken
for weeks (or sometimes even months) which isn't suitable for CI. In
principle, if
*** This bug is a duplicate of bug 1832919 ***
https://bugs.launchpad.net/bugs/1832919
@javier
I recommend instead:
dpkg-reconfigure libc6
dpkg --configure -a
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssl in
*** This bug is a duplicate of bug 1832919 ***
https://bugs.launchpad.net/bugs/1832919
Because your solution, answers the template without showing it to the
user without the appropriate warning as to what the implications of
setting it to true are.
** This bug has been marked a duplicate of
** Also affects: nginx (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssl in Ubuntu.
https://bugs.launchpad.net/bugs/1833476
Title:
libssl1.1 version
** Also affects: lvm2 (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: initramfs-tools (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: lvm2 (Ubuntu Eoan)
** Also affects: whoopsie (Ubuntu Eoan)
Importance: Undecided
Status: New
** Changed in: whoopsie (Ubuntu Eoan)
Importance: Undecided => High
** Tags removed: rls-ee-incoming
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
** Tags removed: rls-ee-incoming
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to jackd2 in Ubuntu.
https://bugs.launchpad.net/bugs/1832651
Title:
jackdbus fails to start: cannot allocate memory
Status in systemd:
Fix
** Also affects: systemd (Ubuntu Eoan)
Importance: High
Status: Confirmed
** Also affects: jackd2 (Ubuntu Eoan)
Importance: Undecided
Status: Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to jackd2
** Also affects: binutils (Ubuntu Eoan)
Importance: High
Status: Confirmed
** Also affects: skiboot (Ubuntu Eoan)
Importance: High
Status: Confirmed
** Tags removed: rls-ee-incoming
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
That's correct. The assertion is at https://salsa.debian.org/systemd-
team/systemd/blob/master/debian/tests/boot-and-services#L421.
Regarding which release of Ubuntu is affected, I have to say I don't
know. The issue is mostly about "upstream" mode of Ubuntu CI, which can
be detected by checking
Since https://github.com/systemd/systemd/pull/12430 isn't in any current
Ubuntu systemd, I don't believe the test case needs to be fixed in any
releases besides Eoan (so the test will already be corrected once Ubuntu
systemd is updated to include pull 12430). Right?
And it should be corrected
** Also affects: systemd (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: systemd (Ubuntu Eoan)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd
** Changed in: checkbox-support
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1830146
Title:
Checkbox detect an extra webcam
** Changed in: binutils
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to binutils in Ubuntu.
https://bugs.launchpad.net/bugs/1833237
Title:
skiboot ftbfs in eoan
Status in binutils:
This is due to a horrible linker script breaking a new GOT indirect to
GOT relative optimisation (git commit 066f4018ae78).
ld does a preliminary layout to see whether various optimisations can be
done. In this case the preliminary layout indicates that code using a
GOT indirect address can be
** Project changed: plainbox-provider-checkbox => checkbox-support
** Changed in: checkbox-support
Milestone: 0.49.0 => None
** Changed in: checkbox-support
Milestone: None => 0.42.0
** Merge proposal linked:
Apologies for the delay, was busy with college work. I recall having
this bug on Ubuntu 16.04 and 17.04 too. I will have to install and see.
Also, this bug exists on Kubuntu (not surprising) Fedora, Manjaro (both
latest kernels and updates) . I tried digging up more info on hp-wmi
etc. but nothing
I installed bash from 'proposed' on a test server, and am running some
tests on it, and parallel also on normal 18.04 servers. I'll expand this
soon, and report back with the results.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
--- Comment From bssrika...@in.ibm.com 2019-06-20 07:09 EDT---
Verified with `util-linux
2.31.1-0.4ubuntu3.3`
Issue is fixed.
Inside compat guest:
# lscpu
Architecture:ppc64le
Byte Order: Little Endian
CPU(s): 16
Public bug reported:
After opening QuiteRSS it will run until crash happens. This happens
intermittently within the hour usually.
(gdb) bt
#0 QHttpNetworkConnectionChannel::sendRequest (this=)
at access/qhttpnetworkconnectionchannel.cpp:238
#1 0x730deca2 in
Public bug reported:
in gnome settings audio section does not see any sound card. if i run
alsamixer it can detect the sound card and all works fine. in gnome
sound settings everything seems to be disabled.
I have excatly same problem on PC where configuration is completely
different than my
i only see chrome device as output device after manually running
pulseaudio -D and pulseaudio --check
** Attachment added: "Screenshot from 2019-06-20 12-58-29.png"
** Attachment added: "after run pulseaudio -D and pulseaudio --check"
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1833527/+attachment/5271788/+files/Screenshot%20from%202019-06-20%2012-58-29.png
--
You received this bug notification because you are a member of Ubuntu
Touch
Thanks @Gene, for this system I think it's a combo color + IR webcam for
windows hello compatibility.
See https://www.dell.com/en-
us/work/shop/cty/pdp/spd/latitude-15-5501-laptop/s009l550115us
"Bypass passwords: Start the workday faster by signing on with an
optional fingerprint reader
More info after i run pulseaudio --check i can see an output device but
its not my sound card, another screenshot attached
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
** Attachment added: "Screenshot from 2019-06-20 12-46-32.png"
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1833527/+attachment/5271783/+files/Screenshot%20from%202019-06-20%2012-46-32.png
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
Public bug reported:
As the title says, on this laptop the brightness controls are NOT saved
after reboot.
What is saved instead, is only the keyboard brightness.
I have tested two distros, Ubuntu 18.04.2 LTS and 19.04, happens on both
systems. But there is a difference
On 19.04, "systemctl
Public bug reported:
in gnome settings audio section does not see any sound card. if i run
alsamixer it can detect the sound card and all works fine. in gnome
sound settings everything seems to be disabled.
I have excatly same problem on PC where configuration is completely
different than my
** Attachment added: "201903-26914_videos_info.txt"
https://bugs.launchpad.net/plainbox-provider-checkbox/+bug/1830146/+attachment/5271762/+files/201903-26914_videos_info.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed
Please:
1. Wait till the problem happens again and let the system shut down.
2. Power up the system and then run:
journalctl -b-1 > prevboot.txt
3. Attach the file 'prevboot.txt' to this bug.
** Package changed: xorg (Ubuntu) => linux (Ubuntu)
** Changed in: linux (Ubuntu)
This bug was fixed in the package glib2.0 - 2.60.4-1
---
glib2.0 (2.60.4-1) experimental; urgency=medium
* New upstream release (LP: #1832457)
+ Fixes to improved network status detection with NetworkManager (#1788)
+ Leak fixes to some `glib-genmarshal` generated code
+
Public bug reported:
the system shuts down automatically withouot any warnings. using sony
vaio laptop with only ubuntu installed on it.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.18.0-21.22~18.04.1-generic 4.18.20
Uname: Linux
** Changed in: oem-priority
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to kmod in Ubuntu.
https://bugs.launchpad.net/bugs/1786574
Title:
remove i2c-i801 from blacklist
Status in HWE
Hi,
I use Linux from about 1996 and Windows from the very first version 2.x
Both OS have become more reliable and powerfull.
For Ubuntu the worst weaknesses are related to multimedia and conflicts
between devs : Graphics cards, sound issues and many other boring things
are really where Canonical
Public bug reported:
The max pass-phrase length for a WPA2-PSK, has a limit of 63 ASCII-
encoded characters
The password fields, in the dialog to write the pass-phrase for the Wifi
network you are connecting to, is limiting this to 20 characters.
ProblemType: Bug
DistroRelease: Ubuntu 19.04
Yeah it doesn't matter it comment #8 is wrong here. I was going to wait
till the commit is released and then confirm the crash has stopped
happening.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
@Daniel, unsure that commit fixes it?
(https://gitlab.freedesktop.org/pulseaudio/pulseaudio/commit/4762aa45 for
reference/easier browsing)
The commit message states
'The bug had no impact because there is only one caller of pa_make_fd_block()
in poll-win32.c'
Also the code bt here indicagtes
Public bug reported:
i have ubuntu 19.04
** Affects: systemd (Ubuntu)
Importance: Undecided
Status: New
** Attachment added: "Screenshot from 2019-06-20 10-22-40.png"
** Changed in: plainbox-provider-checkbox
Importance: High => Critical
** Changed in: plainbox-provider-checkbox
Milestone: None => 0.49.0
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
** Changed in: pulseaudio
Status: Unknown => New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1720519
Title:
KDE/Kubuntu: Module "module-switch-on-connect"
89 matches
Mail list logo
