[Touch-packages] [Bug 1898753] Re: Non-existent home directory entry in /etc/passwd
** Description changed: This bug applies to both Ubuntu 18.04 and Ubuntu 20.04, the two distros I've checked. This is likely a packaging error. The syslog user appears in /etc/passwd as: - syslog:x:102:106::/home/syslog:/usr/sbin/nologin + syslog:x:102:106::/home/syslog:/usr/sbin/nologin Of course there is no directory /home/syslog. This appears innocuous, but can cause problems for users that have, say autofs mounted home - directories. To cite one example, the python virtual envionment - anaconda trolls through /etc/passw looking for environments in + directories. To cite one example, the python virtual environment + anaconda trolls through /etc/passwd looking for environments in /home/USER. This triggers autofs to try and mount /home/syslog, which - doesn't existing, causing the automounter to hang under certain + doesn't exist, causing the automounter to hang under certain circumstances. In, for example, Arch linux, this entry would appear as the considerably more sensible - syslog:x:102:106::/:/usr/sbin/nologin + syslog:x:102:106::/:/usr/sbin/nologin While an edge case in the current compute environment, this is also a very easy fix. Don't reference non-existent directories. Many Ubuntu packages make this packaging error when creating local users with non- existent home directories; e.g. cups-pk-helper, which I'm filing a bug report for next. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsyslog in Ubuntu. https://bugs.launchpad.net/bugs/1898753 Title: Non-existent home directory entry in /etc/passwd Status in rsyslog package in Ubuntu: New Bug description: This bug applies to both Ubuntu 18.04 and Ubuntu 20.04, the two distros I've checked. This is likely a packaging error. The syslog user appears in /etc/passwd as: syslog:x:102:106::/home/syslog:/usr/sbin/nologin Of course there is no directory /home/syslog. This appears innocuous, but can cause problems for users that have, say autofs mounted home directories. To cite one example, the python virtual environment anaconda trolls through /etc/passwd looking for environments in /home/USER. This triggers autofs to try and mount /home/syslog, which doesn't exist, causing the automounter to hang under certain circumstances. In, for example, Arch linux, this entry would appear as the considerably more sensible syslog:x:102:106::/:/usr/sbin/nologin While an edge case in the current compute environment, this is also a very easy fix. Don't reference non-existent directories. Many Ubuntu packages make this packaging error when creating local users with non- existent home directories; e.g. cups-pk-helper, which I'm filing a bug report for next. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1898753/+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 1898753] [NEW] Non-existent home directory entry in /etc/passwd
Public bug reported: This bug applies to both Ubuntu 18.04 and Ubuntu 20.04, the two distros I've checked. This is likely a packaging error. The syslog user appears in /etc/passwd as: syslog:x:102:106::/home/syslog:/usr/sbin/nologin Of course there is no directory /home/syslog. This appears innocuous, but can cause problems for users that have, say autofs mounted home directories. To cite one example, the python virtual envionment anaconda trolls through /etc/passw looking for environments in /home/USER. This triggers autofs to try and mount /home/syslog, which doesn't existing, causing the automounter to hang under certain circumstances. In, for example, Arch linux, this entry would appear as the considerably more sensible syslog:x:102:106::/:/usr/sbin/nologin While an edge case in the current compute environment, this is also a very easy fix. Don't reference non-existent directories. Many Ubuntu packages make this packaging error when creating local users with non- existent home directories; e.g. cups-pk-helper, which I'm filing a bug report for next. ** Affects: rsyslog (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsyslog in Ubuntu. https://bugs.launchpad.net/bugs/1898753 Title: Non-existent home directory entry in /etc/passwd Status in rsyslog package in Ubuntu: New Bug description: This bug applies to both Ubuntu 18.04 and Ubuntu 20.04, the two distros I've checked. This is likely a packaging error. The syslog user appears in /etc/passwd as: syslog:x:102:106::/home/syslog:/usr/sbin/nologin Of course there is no directory /home/syslog. This appears innocuous, but can cause problems for users that have, say autofs mounted home directories. To cite one example, the python virtual envionment anaconda trolls through /etc/passw looking for environments in /home/USER. This triggers autofs to try and mount /home/syslog, which doesn't existing, causing the automounter to hang under certain circumstances. In, for example, Arch linux, this entry would appear as the considerably more sensible syslog:x:102:106::/:/usr/sbin/nologin While an edge case in the current compute environment, this is also a very easy fix. Don't reference non-existent directories. Many Ubuntu packages make this packaging error when creating local users with non- existent home directories; e.g. cups-pk-helper, which I'm filing a bug report for next. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1898753/+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 1444562] Re: [Z97X-SLI, Realtek ALC1150, Green Line Out, Rear] No sound at all (analog audio not working)
I'm having exactly the same problem with a Gigabyte Z97 MB which has the Realtek ALC1150 audio chip. Howver, in my case, I'm trying to run a current version of Arch linux, meaning that the linux kernel, sound drivers, and pulseaudio are maximally up to date as of August 17, 2015. So in particular, this is not an Ubuntu-specific problem at all, but rather appears to have something to so with the audio device driver and/or pulseaudio. -- 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/1444562 Title: [Z97X-SLI, Realtek ALC1150, Green Line Out, Rear] No sound at all (analog audio not working) Status in alsa-driver package in Ubuntu: Confirmed Bug description: USB headphones are working but the colored line-outs do not work. I just replaced win10 where it worked just fine. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.16.0-34.47-generic 3.16.7-ckt8 Uname: Linux 3.16.0-34-generic x86_64 ApportVersion: 2.14.7-0ubuntu8.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: ake1 1770 F pulseaudio /dev/snd/controlC2: ake1 1770 F pulseaudio /dev/snd/controlC0: ake1 1770 F pulseaudio /dev/snd/controlC1: ake1 1770 F pulseaudio CurrentDesktop: GNOME Date: Wed Apr 15 18:12:02 2015 InstallationDate: Installed on 2015-04-15 (0 days ago) InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: ake1 1770 F pulseaudio /dev/snd/controlC2: ake1 1770 F pulseaudio /dev/snd/controlC0: ake1 1770 F pulseaudio /dev/snd/controlC1: ake1 1770 F pulseaudio Symptom_Jack: Green Line Out, Rear Symptom_Type: No sound at all Title: [Z97X-SLI, Realtek ALC1150, Green Line Out, Rear] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/25/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F3 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z97X-SLI-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF3:bd04/25/2014:svnGigabyteTechnologyCo.,Ltd.:pnZ97X-SLI:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ97X-SLI-CF:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: Z97X-SLI dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1444562/+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
