[Touch-packages] [Bug 1767784] Re: [regression] output device not recognized anymore since update 1:8.0-0ubuntu3.9
1:8.0-0ubuntu3.10 from proposed fixes the problem ** Tags removed: verification-needed verification-needed-xenial ** Tags added: verification-done verification-done-xenial -- 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/1767784 Title: [regression] output device not recognized anymore since update 1:8.0-0ubuntu3.9 Status in pulseaudio package in Ubuntu: Fix Committed Status in pulseaudio source package in Xenial: Fix Committed Bug description: SRU Document: [Impact] The 1:8.0-0ubuntu3.9 introduced a new problem on the machines which do not have internal speaker on them. With the 1:8.0-0ubuntu3.8, even there is no internal speaker and nothing plugged in the audio jack, the profile is still set available, then the active profile is analog- stereo; while with the 1:8.0-0ubuntu3.9, the profile is set to unavailable, and the active profile is off, after users plug sth in the audio jack, the active profile will not switch automatically, need users to switch manually, this change is unfriendly to users. [Test Case] On the machines without internal speaker, open sound-setting and check if there is some output devices in the UI, and play sound from the UI. Under 1:8.0-0ubuntu3.9 there is no output device, and can't play sound; under 1:8.0-0ubuntu3.8 there is output device, and can play sound. [Regression Potential] This is a revert, after reverting, the content of pulseaudio is exactly same as 1:8.0-0ubuntu3.8 [Other Info] none Since the update 1:8.0-0ubuntu3.8 to 1:8.0-0ubuntu3.9 , pulseaudio is not showing anymore my soundcard. https://launchpad.net/ubuntu/+source/pulseaudio/1:8.0-0ubuntu3.9 The command "pacmd list-sinks" only shows a dummy output When running on a fresh install of ubuntu 16.04, the sound is ok. When updating the install with locking the following files to version 1:8.0-0ubuntu3 the sound keeps working: libpulse0:amd64 libpulse-mainloop-glib0:amd64 libpulse-dev:amd64 pulseaudio-module-x11:amd64 pulseaudio-module-bluetooth:amd64 pulseaudio-utils:amd64 When updating to 1:8.0-0ubuntu3.9, I just get a "dummy output". I tried running the following versions of Ubuntu (live usb), and get the same issue (no need to update to get the problem) 17.04 17.10 18.04 I attached the result of command "pactl list" I have also generated logs during the boot but I don't know how to attach multiple files To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1767784/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1768411] Re: pulseaudio 8.0-0ubuntu3.9 update broke sound on certain hardware, the dummy output profile is selected by default
here is the text from running: apport-cli -f -p pulseaudio --save bug.apport ** Attachment added: "bug.apport" https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1768411/+attachment/5131795/+files/bug.apport -- 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/1768411 Title: pulseaudio 8.0-0ubuntu3.9 update broke sound on certain hardware, the dummy output profile is selected by default Status in pulseaudio package in Ubuntu: New Bug description: I help manage a few hundred computers and since the last pulseaudio update a few weeks ago ( xenial-updates ) from pulseaudio_1%3a8.0-0ubuntu3.8_amd64.deb to pulseaudio_1%3a8.0-0ubuntu3.9_amd64.deb ( and libpulse0 ) certain hardware including dell models 755, 390, and 3050 lost sound. They were working fine for years but now the dummy output profile is selected by default. What happened? This can be worked around by explicitly setting: set-card-profile 0 output:analog-stereo set-sink-port 1 analog-output-headphones or by reverting back to pulseaudio_1%3a8.0-0ubuntu3.8_amd64.deb ( along with libpulse0 ) . When I try to use apport it gets to the end and says "apport cannot connect to crash database" but I have included example system details in the attachment after the output of pacmd list sinks and default.pa. ( You can only attach one file ?!?) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1768411/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1768411] Re: pulseaudio 8.0-0ubuntu3.9 update broke sound on certain hardware, the dummy output profile is selected by default
here is the default.pa ** Attachment added: "default.pa" https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1768411/+attachment/5131794/+files/default.pa -- 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/1768411 Title: pulseaudio 8.0-0ubuntu3.9 update broke sound on certain hardware, the dummy output profile is selected by default Status in pulseaudio package in Ubuntu: New Bug description: I help manage a few hundred computers and since the last pulseaudio update a few weeks ago ( xenial-updates ) from pulseaudio_1%3a8.0-0ubuntu3.8_amd64.deb to pulseaudio_1%3a8.0-0ubuntu3.9_amd64.deb ( and libpulse0 ) certain hardware including dell models 755, 390, and 3050 lost sound. They were working fine for years but now the dummy output profile is selected by default. What happened? This can be worked around by explicitly setting: set-card-profile 0 output:analog-stereo set-sink-port 1 analog-output-headphones or by reverting back to pulseaudio_1%3a8.0-0ubuntu3.8_amd64.deb ( along with libpulse0 ) . When I try to use apport it gets to the end and says "apport cannot connect to crash database" but I have included example system details in the attachment after the output of pacmd list sinks and default.pa. ( You can only attach one file ?!?) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1768411/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1768411] Re: pulseaudio 8.0-0ubuntu3.9 update broke sound on certain hardware, the dummy output profile is selected by default
I see now there is an option for additional attachments (one per comment) so I'm going to attache the files separately, here is the output of pacmd list sinks ** Attachment added: "pacmd-list.log" https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1768411/+attachment/5131793/+files/pacmd-list.log -- 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/1768411 Title: pulseaudio 8.0-0ubuntu3.9 update broke sound on certain hardware, the dummy output profile is selected by default Status in pulseaudio package in Ubuntu: New Bug description: I help manage a few hundred computers and since the last pulseaudio update a few weeks ago ( xenial-updates ) from pulseaudio_1%3a8.0-0ubuntu3.8_amd64.deb to pulseaudio_1%3a8.0-0ubuntu3.9_amd64.deb ( and libpulse0 ) certain hardware including dell models 755, 390, and 3050 lost sound. They were working fine for years but now the dummy output profile is selected by default. What happened? This can be worked around by explicitly setting: set-card-profile 0 output:analog-stereo set-sink-port 1 analog-output-headphones or by reverting back to pulseaudio_1%3a8.0-0ubuntu3.8_amd64.deb ( along with libpulse0 ) . When I try to use apport it gets to the end and says "apport cannot connect to crash database" but I have included example system details in the attachment after the output of pacmd list sinks and default.pa. ( You can only attach one file ?!?) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1768411/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1768411] [NEW] pulseaudio 8.0-0ubuntu3.9 update broke sound on certain hardware, the dummy output profile is selected by default
Public bug reported: I help manage a few hundred computers and since the last pulseaudio update a few weeks ago ( xenial-updates ) from pulseaudio_1%3a8.0-0ubuntu3.8_amd64.deb to pulseaudio_1%3a8.0-0ubuntu3.9_amd64.deb ( and libpulse0 ) certain hardware including dell models 755, 390, and 3050 lost sound. They were working fine for years but now the dummy output profile is selected by default. What happened? This can be worked around by explicitly setting: set-card-profile 0 output:analog-stereo set-sink-port 1 analog-output-headphones or by reverting back to pulseaudio_1%3a8.0-0ubuntu3.8_amd64.deb ( along with libpulse0 ) . When I try to use apport it gets to the end and says "apport cannot connect to crash database" but I have included example system details in the attachment after the output of pacmd list sinks and default.pa. ( You can only attach one file ?!?) ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Attachment added: "pacmd list sinks and default.pa and apport bug text contents" https://bugs.launchpad.net/bugs/1768411/+attachment/5131792/+files/pacmd-list-and-default-pa-and-apport-bug.txt -- 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/1768411 Title: pulseaudio 8.0-0ubuntu3.9 update broke sound on certain hardware, the dummy output profile is selected by default Status in pulseaudio package in Ubuntu: New Bug description: I help manage a few hundred computers and since the last pulseaudio update a few weeks ago ( xenial-updates ) from pulseaudio_1%3a8.0-0ubuntu3.8_amd64.deb to pulseaudio_1%3a8.0-0ubuntu3.9_amd64.deb ( and libpulse0 ) certain hardware including dell models 755, 390, and 3050 lost sound. They were working fine for years but now the dummy output profile is selected by default. What happened? This can be worked around by explicitly setting: set-card-profile 0 output:analog-stereo set-sink-port 1 analog-output-headphones or by reverting back to pulseaudio_1%3a8.0-0ubuntu3.8_amd64.deb ( along with libpulse0 ) . When I try to use apport it gets to the end and says "apport cannot connect to crash database" but I have included example system details in the attachment after the output of pacmd list sinks and default.pa. ( You can only attach one file ?!?) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1768411/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1742912] Re: Please confine guest sessions again
I figured out why the simple test didn't work - when I first installed Ubuntu 18.04, gnome-terminal wouldn't accept any keyboard input, I assumed it was just a pre-alpha bug and installed terminator. Installing terminator switched itself to the default including launching with ctrl-alt-t , and terminator does get apparmor restricted.When I paste in "cat /proc/self/attr/current" into a gnome-terminal it shows unconfined. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1742912 Title: Please confine guest sessions again Status in lightdm package in Ubuntu: Confirmed Bug description: This is a continuation of LP: #1663157 where as a workaround for the guest session not being confined the session got disabled. This bug tracks the fix for proper confinement. Original bug report text: Processes launched under a lightdm guest session are not confined by the /usr/lib/lightdm/lightdm-guest-session AppArmor profile in Ubuntu 16.10, Ubuntu 17.04, and Ubuntu Artful (current dev release). The processes are unconfined. The simple test case is to log into a guest session, launch a terminal with ctrl-alt-t, and run the following command: $ cat /proc/self/attr/current Expected output, as seen in Ubuntu 16.04 LTS, is: /usr/lib/lightdm/lightdm-guest-session (enforce) Running the command inside of an Ubuntu 16.10 and newer guest session results in: unconfined To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1742912/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1742912] Re: Please confine guest sessions again
Please note that the simple test ( cat /proc/self/attr/current ) can be misleading. I tried that in Ubuntu 18.04 ( switched to lightdm ) and got "(enforce)" but some applications like the file manager could browse other user's home directories. Most applications including firefox and libreoffice are restricted. In Xubuntu the file manager is restricted as well as every other application I tried. Is it possible to just eliminate certain applications or prevent launching applications in specific ways to guarantee a restricted guest sessions? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1742912 Title: Please confine guest sessions again Status in lightdm package in Ubuntu: Confirmed Bug description: This is a continuation of LP: #1663157 where as a workaround for the guest session not being confined the session got disabled. This bug tracks the fix for proper confinement. Original bug report text: Processes launched under a lightdm guest session are not confined by the /usr/lib/lightdm/lightdm-guest-session AppArmor profile in Ubuntu 16.10, Ubuntu 17.04, and Ubuntu Artful (current dev release). The processes are unconfined. The simple test case is to log into a guest session, launch a terminal with ctrl-alt-t, and run the following command: $ cat /proc/self/attr/current Expected output, as seen in Ubuntu 16.04 LTS, is: /usr/lib/lightdm/lightdm-guest-session (enforce) Running the command inside of an Ubuntu 16.10 and newer guest session results in: unconfined To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1742912/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1598300] Re: CUPS web interface stops responding after a while
Johannes Martin (johannes-martin) wrote: Is CUPS some deprecated setting? Yes - "BrowseLocalProtocols CUPS" was valid in 12.04 ( what I upgraded from ) but not anymore. If you needed to add a BrowseLocalProtocols line as opposed to switching its value, it seems that this auto-shutdown feature is triggering off that option being present and assigned certain values. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1598300 Title: CUPS web interface stops responding after a while Status in cups package in Ubuntu: Fix Released Status in cups source package in Xenial: Fix Committed Bug description: after 6 minutes or so, cups is not responding. it do not produce error on the log, just stop working, worse, it exit with 0 ⌌—⌍ |root@cupsmachine :~# systemctl status cups | |● cups.service - CUPS Scheduler | | Loaded: loaded (/lib/systemd/system/cups.service; enabled; vendor preset: enabled)| | Active: inactive (dead) since ven. 2016-07-01 10:31:32 TAHT; 2min 16s ago | | Docs: man:cupsd(8) | | Process: 28686 ExecStart=/usr/sbin/cupsd -l (code=exited, status=0/SUCCESS)| | Main PID: 28686 (code=exited, status=0/SUCCESS) | | | |juil. 01 10:30:01 appli-client systemd[1]: Started CUPS Scheduler. | ⌎—⌏ I got to launch it again, so I have finish with a cron job like */10 * * * * systemctl status cups.service|grep -q 'inactive (dead)' && systemctl start cups but it is a dirty solution. I have no idea of what make it stop. NB: I have seen problems related to apparmor, this machine has no apparmor package. [Impact] If you want to use the CUPS web interface in Xenial and therefore set "WebInterface Yes" in /etc/cups/cupsd.conf, CUPS could auto-shutdown when it is idle and then an attempt to access http://localhost:631/ via a web browser fails. People get confused as other access to CUPS [Testcase] Take a CUPS setup on Xenial with no shared print queues and CUPS only listening on the domain socket. Activate the web interface via cupsctl WebInterface=Yes Now you are able to access the web interface via http://localhost:631/. Wait for some minutes without accessing CUPS until the CUPS daemon shuts down automatically. Try to open the web interface again and it will not work. With the fixed CUPS package CUPS will not auto-shutdown when the web interface is activated. [Regression Potential] Low, as we are removing a simple distro patch to get back to the original, upstream behavior. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1598300/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1598300] Re: CUPS web interface stops responding after a while
(iiro) "Did you look the cups log to make sure that it really is the same problem?" Without any fixes I get these messages about 2 minutes after restarting cups and cupsd is no longer running: I [09/Feb/2017:04:08:47 -0600] Printer sharing is off and there are no jobs pending, will restart on demand. I [09/Feb/2017:04:08:47 -0600] Scheduler shutting down normally. After installing the proposed updates or switching to BrowseLocalProtocols dnssd those messages go away and cupsd stays running and client print jobs don't fail with "Connection error: Transport endpoint is not connected." (iiro) "but it's now too late to do anything" Assuming there is absolutely no way to fix bug 1642966, why not switch "-l" to "-f" in /lib/systemd/system/cups.service as an official fix? Is that the only way to completely disable this buggy feature? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1598300 Title: CUPS web interface stops responding after a while Status in cups package in Ubuntu: Fix Released Status in cups source package in Xenial: Fix Committed Bug description: after 6 minutes or so, cups is not responding. it do not produce error on the log, just stop working, worse, it exit with 0 ⌌—⌍ |root@cupsmachine :~# systemctl status cups | |● cups.service - CUPS Scheduler | | Loaded: loaded (/lib/systemd/system/cups.service; enabled; vendor preset: enabled)| | Active: inactive (dead) since ven. 2016-07-01 10:31:32 TAHT; 2min 16s ago | | Docs: man:cupsd(8) | | Process: 28686 ExecStart=/usr/sbin/cupsd -l (code=exited, status=0/SUCCESS)| | Main PID: 28686 (code=exited, status=0/SUCCESS) | | | |juil. 01 10:30:01 appli-client systemd[1]: Started CUPS Scheduler. | ⌎—⌏ I got to launch it again, so I have finish with a cron job like */10 * * * * systemctl status cups.service|grep -q 'inactive (dead)' && systemctl start cups but it is a dirty solution. I have no idea of what make it stop. NB: I have seen problems related to apparmor, this machine has no apparmor package. [Impact] If you want to use the CUPS web interface in Xenial and therefore set "WebInterface Yes" in /etc/cups/cupsd.conf, CUPS could auto-shutdown when it is idle and then an attempt to access http://localhost:631/ via a web browser fails. People get confused as other access to CUPS [Testcase] Take a CUPS setup on Xenial with no shared print queues and CUPS only listening on the domain socket. Activate the web interface via cupsctl WebInterface=Yes Now you are able to access the web interface via http://localhost:631/. Wait for some minutes without accessing CUPS until the CUPS daemon shuts down automatically. Try to open the web interface again and it will not work. With the fixed CUPS package CUPS will not auto-shutdown when the web interface is activated. [Regression Potential] Low, as we are removing a simple distro patch to get back to the original, upstream behavior. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1598300/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1598300] Re: CUPS web interface stops responding after a while
This is a very serious bug that breaks network printing in certain configurations. To be clear: its not just that cups stops and the web interface is unavailable - it can lead to not being able to print as the print server looks like it is offline to the clients: D [09/Feb/2017:10:07:02 -0600] [Job 12] Connection error: Transport endpoint is not connected E [09/Feb/2017:10:07:02 -0600] [Job 12] The printer is not responding. I was running into this issue on some print servers but not others and in comparing the two cupsd.conf files I found out I can prevent the issue by changing BrowseLocalProtocols CUPS to BrowseLocalProtocols dnssd The real problem here is that a feature like this should have a clear and easy way to turn if off completely. I don't ever want cups on a print server stopping to save an insignificant amount of cpu cycles or memory or electricity! Applying the packages from xenial-proposed does fix it for me, but in my opinion this is a pretty serious issue that needs a quicker fix. I think the best fix at the moment is the suggestion from Andreas Krausz (kukorica) to change " the option "-l" to "-f" in /lib/systemd/system/cups.service." as it seems that is the only way to turn off this "feature". -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1598300 Title: CUPS web interface stops responding after a while Status in cups package in Ubuntu: Fix Released Status in cups source package in Xenial: Fix Committed Bug description: after 6 minutes or so, cups is not responding. it do not produce error on the log, just stop working, worse, it exit with 0 ⌌—⌍ |root@cupsmachine :~# systemctl status cups | |● cups.service - CUPS Scheduler | | Loaded: loaded (/lib/systemd/system/cups.service; enabled; vendor preset: enabled)| | Active: inactive (dead) since ven. 2016-07-01 10:31:32 TAHT; 2min 16s ago | | Docs: man:cupsd(8) | | Process: 28686 ExecStart=/usr/sbin/cupsd -l (code=exited, status=0/SUCCESS)| | Main PID: 28686 (code=exited, status=0/SUCCESS) | | | |juil. 01 10:30:01 appli-client systemd[1]: Started CUPS Scheduler. | ⌎—⌏ I got to launch it again, so I have finish with a cron job like */10 * * * * systemctl status cups.service|grep -q 'inactive (dead)' && systemctl start cups but it is a dirty solution. I have no idea of what make it stop. NB: I have seen problems related to apparmor, this machine has no apparmor package. [Impact] If you want to use the CUPS web interface in Xenial and therefore set "WebInterface Yes" in /etc/cups/cupsd.conf, CUPS could auto-shutdown when it is idle and then an attempt to access http://localhost:631/ via a web browser fails. People get confused as other access to CUPS [Testcase] Take a CUPS setup on Xenial with no shared print queues and CUPS only listening on the domain socket. Activate the web interface via cupsctl WebInterface=Yes Now you are able to access the web interface via http://localhost:631/. Wait for some minutes without accessing CUPS until the CUPS daemon shuts down automatically. Try to open the web interface again and it will not work. With the fixed CUPS package CUPS will not auto-shutdown when the web interface is activated. [Regression Potential] Low, as we are removing a simple distro patch to get back to the original, upstream behavior. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1598300/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1190344] Re: lightdm is leaking FDs -fix
I just want to confirm this bug affects precise and precise-updates
which is using lightdm 1.2.3
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1190344
Title:
lightdm is leaking FDs -fix
Status in Light Display Manager:
Fix Released
Status in Light Display Manager 1.10 series:
Fix Released
Status in Light Display Manager 1.12 series:
Fix Released
Status in Light Display Manager 1.2 series:
Fix Released
Status in lightdm package in Ubuntu:
Fix Released
Status in lightdm source package in Precise:
Triaged
Status in lightdm source package in Trusty:
Fix Committed
Status in lightdm source package in Utopic:
Fix Committed
Status in lightdm source package in Vivid:
Fix Released
Status in Fedora:
Unknown
Bug description:
[Impact]
LightDM doesn't close the server side end of the pipes used to communicate
with session processes. This means each session that is created leaks two file
descriptors eventually leading to the system stopping it from creating new
pipes.
[Test Case]
1. Start LightDM
2. Check how many pipes are open
# lsof -p {lightdm_pid} | grep FIFO | wc -l
3. Create sessions by either cycling between users in Unity Greeter or
logging in and out
4. Check how many pipes exist using step 2.
Expected result:
No more pipes should be open
Observed result:
Many pipes remain open
[Regression Potential]
Low. Fix is to close pipes when finished with them. Tested with regression
tests.
To manage notifications about this bug go to:
https://bugs.launchpad.net/lightdm/+bug/1190344/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
