[arch-general] Problem with audio
Hi! I have configured MPD to start with systemd using: $ systemctl --user enable mpd.service and MPD works fine but when I try to use other programs like VLC, there is no sound but by restarting MPD's service sound works again. Any ideas how to fix this, so that I do not need to restart the service every time I start the system? Thanks! -- edson duarte GPG key ID: 0xDDFA2FE8
Re: [arch-general] Problem with audio
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hi, have you tried to run alsactl init alsactl store? Le 09/12/2014 11:11, edson duarte a écrit : Hi! I have configured MPD to start with systemd using: $ systemctl --user enable mpd.service and MPD works fine but when I try to use other programs like VLC, there is no sound but by restarting MPD's service sound works again. Any ideas how to fix this, so that I do not need to restart the service every time I start the system? Thanks! - -- Vincent Lequertier s...@riseup.net -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQEcBAEBCAAGBQJUhsOQAAoJEIDBfsllbxKAymwH/AuIviUuXtTbQctIZ+JUQRaF vwqv2y0PpLwlkpNLy5rE9ulkA1qAYxcEleF+Lc/Zubw9tlcIYUtod98kRD4Xz88C 7fDVACqt1MpRdCND4hIv2ykxFzGWFBfrUQtfMBy5MOqH0JySRM3jI6PuUb8e+5e6 9Y8Q0BEk8keNGgiBixIebde0iNC0ZfNNyZ63btDXA9iEwNOxioZkjtbN8y6DTq6g B1car1G1vjz3kut/5paazoX9qDh0/UgBW31a0hAaUMpYIdMxAYblyctyEyuzyM5L uFTHVexdthWN5BvnMeUQmtyCc/QFjnYQLLTwH5B5w+whkvkbhHFTxQjWRPq1U5E= =WRQy -END PGP SIGNATURE-
Re: [arch-general] Problem with audio
On Tue, Dec 9, 2014 at 3:11 AM, edson duarte edsonduarte1...@riseup.net wrote: and MPD works fine but when I try to use other programs like VLC, there is no sound but by restarting MPD's service sound works again. Are you using PulseAudio? It may be that MPD is starting PulseAudio, and because systemd --user daemons run outside the user session you can't access the running PulseAudio from within your session without restarting MPD. If this is the case, I recommend following the instructions at [1] to send the audio from MPD to your user session (ignore the fact that it's written to use different users; it will work fine without that). ~Celti [1]: https://wiki.archlinux.org/index.php/MPD/Tips_and_Tricks#Local_.28with_separate_mpd_user.29
Re: [arch-general] Problem with audio
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Vincent Lequertier wrote: Hi, have you tried to run alsactl init alsactl store? No... and after trying: alsactl: sysfs_init:48: sysfs path '/sys' is invalid Found hardware: HDA-Intel Intel PantherPoint HDMI HDA:10134213,10280553,00100100 HDA:80862806,80860101,0010 0x1028 0x0553 Hardware is initialized using a generic method - -- edson duarte GPG key ID: 0xDDFA2FE8 -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQIcBAEBCAAGBQJUhtYLAAoJEEuaWOJw2A3LxLcP/jtAyVgXdji/be3MYL1J/ERo TASQo7FHwCUUPUUmxlqCv9eF6Z7POJxNUfcCZiuEVtVdCLM70hT8ulLfOLzlxkUe 5PL/ogrw8FrNFabSr1xAhjAaGHqW1skS7sXU0pAtOQrFVGyla9R+4hVTbKXcHHKg /TqInU7qheDtqz4QkNaLECiE+cla/948IqRXcm+U23t4qhl9aw4oQyA+ehEENQT2 2cbjpxrEHth3aO7URgEajV40XGr/r1HR/FOqx/yCDy61lDFvA9GcSEzSUc98TzCG RJfsxjuljMx4ImayqKDXLYaHPi1iy0v2RjQUKu4NLqfu4cJLWqwk3C6ATkwX5gJH AlN2acMmCoK4UEMhZRbCKUIgQEcFxDUm2ohrt0a0uSSCnZn3MBgoXDOggin+smp5 hFH2L24sx0a5lPkCtf2rmYkcb8W3NMaOFGehMXpQ6oSxpZ3LrxiSz+Gy4TrF4WFe WSm1fbS7DIYiGMHmomJv7vG0r7TTckA+pCrjnn/PFNG0j7u/nl1MR2ENZTyxZcsv L6jgJiP/OLDTRdt0ylFNXwFLiEtYJW8WXQcmgUgTPbV86lrGmNFTgfIhlH3PV5sF OesTDKauv0S5Dtxj9Tvwyn/BOsWZ97qMacK8bZU2ySNyNjodb8IEQDqwHyJnvgll KhlfyyAgKe74lKU000HS =MH4k -END PGP SIGNATURE-
Re: [arch-general] Problem with audio
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Patrick Burroughs (Celti) wrote: Are you using PulseAudio? It may be that MPD is starting PulseAudio, and because systemd --user daemons run outside the user session you can't access the running PulseAudio from within your session without restarting MPD. If this is the case, I recommend following the instructions at [1] to send the audio from MPD to your user session (ignore the fact that it's written to use different users; it will work fine without that). I do not use PulseAudio. - -- edson duarte GPG key ID: 0xDDFA2FE8 -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQIcBAEBCAAGBQJUhtZZAAoJEEuaWOJw2A3LQaoP/RtKvqSBeh1v/iDwNPY1xGuc vYzOCz/GmDdKO+kOJI/zc45BAt8jKNsHgnenONd6mYY8HHV9qPbxf8XJW2x6vIr7 oDGl+vfTdflu8LpBe+jVzlKUmjzRpwn86jcFE4X+hJnDUkcD3aD3uRBvobNcJrnC McFNR5vobO0ru6ThH2HXympJ7VFctv4/AuB162XnZdUka7LCMmTJYVvh2kTtnvJc pq0wTECRo9q750kyB8tqdWa1zQmp0H5xcoRqsV8A22zvYfBjB0AJPFCNUgcQi4ys wOIlSM0zBtu86JrHjSBnF1Sy4625pKLTCTlqNAkVxgA2Syta5ZBjI/9gOgXPVIGG xQmrsWIH1aTlIQaSappl7EE5t4cM0XK0W5F7G0T2lZqVhEL4oFsF1EnbP5/7mxj1 M0l29h4LhZlHiQbAAed4SCnqV5D71eueRl9Txp6mNpMDfKjRDZsNqZLiac2w2xyv qwP86RygATz4GHJp1l8tWC5sJ6rKduASkd+djOKz8r7PwAGDtXIXJlfovt5Si+l3 zB1TftqYOXl4cuJh2OxitZSD4ZdvGvsCCOhO6+yVROWQaKgqSORYV43+ujX29Ysc nQJhiBKRabVuYxJNwDZXQc8TA7PE1bUYNQI9yeXlkCWr56tQAv2KTU+SBci4goTf mmkSQ3GcOv+wXFuHr5P3 =3ymm -END PGP SIGNATURE-
Re: [arch-general] Problem with audio
Am 09.12.2014 um 12:00 schrieb edson duarte: I do not use PulseAudio. Than you are probably in the audio group, this is not necessary anymore and has the drawback, that processes can claim the alsa device exclusively. If my assumption is correct, remove yourself from the audio group should solve the problem.
Re: [arch-general] Problem with audio
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Marcel Röthke wrote: Than you are probably in the audio group, this is not necessary anymore and has the drawback, that processes can claim the alsa device exclusively. If my assumption is correct, remove yourself from the audio group should solve the problem. Already tried that, I'm not in the audio group. - -- edson duarte GPG key ID: 0xDDFA2FE8 -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQIcBAEBCAAGBQJUhtz3AAoJEEuaWOJw2A3L788P/AlnLs+gKT9IrNO+eySal0TP vK5j7TxKRPAESqpAiqEU4S+OvxzpuwoAMZHKIPcrklh0F5AJjhlQykoVy6wbZwNE iCjjTumKx6fhWhTh/Wv9jTYfhmvlH6UNoWjr4oYbtzaZ3PG92Ad50/BMYYc7nwP4 FYqVqRAwUldu7e/tRBkW6Ipw8GuPj4ZOnicsjW+4bSbW2zfWqsmKJ55dpvVBaB0M KPt55O2TJdvsO0JzTcYgSoPkKx7OT6F+z2B6BIBO9NLmuWQ0uNrZz/ZhJVWqKOfZ gAqYD3KplNgUMSqD31f8LZexC7EqJUIvZ+Chf1QjsoBjhTh8CQg9Nrv3/C6YPvJj t89MrLSQ+v6tE6xhDh3wi8ooegcDjMVQbrveef8BVw6V6N61I3FRGLI8oFgrbx2T xKVgfXpAujZz4v8n7oolcmYFUyYJS8t1Avpv8IGRnquXATpgPSevofQ+fkC3/Ruk SfCxYma/WMjVb5hjWExeU7/d4+NE7WiF7965U9+ViaGpHkm0nGumwSbrZti7m+Ko NHhyRtTlDqogIq0JwINUM8myQQj6R0stZlOt3wa84b2pYdGy06P9tUrKaTLX0OL6 CGkJrxGJN16bdUvA331H7dE5whrkDL8yZmHNh3WPrNzVjEGZFTPzpp/0adzGfoD8 xYn+o+5u4GEkG9zkxVEZ =P+0c -END PGP SIGNATURE-
[arch-general] Strange issue
Hello, I used makepkg to build a package from /tmp. The package was then put to the designated directory and a symlink to pwd. When I try to install it with pacman -U /tmp/symlink-to-package, I get an error (permission denied) which I don't get when invoking pacman -U directly with the name of the file (not with the symbolic link). See, like this: [root@lnv64 tmp]# pacman -U /tmp/lomoco-1.0-9-x86_64.pkg.tar loading packages... error: '/tmp/lomoco-1.0-9-x86_64.pkg.tar': permission denied [root@lnv64 tmp]# ls -l /tmp/lomoco-1.0-9-x86_64.pkg.tar lrwxrwxrwx 1 nsajko nsajko 55 Dec 9 17:33 /tmp/lomoco-1.0-9-x86_64.pkg.tar - /home/nsajko/debug-packages/lomoco-1.0-9-x86_64.pkg.tar [root@lnv64 tmp]# pacman -U /home/nsajko/debug-packages/lomoco-1.0-9-x86_64.pkg.tar loading packages... warning: lomoco-1.0-9 is up to date -- reinstalling resolving dependencies... looking for inter-conflicts... Packages (1): lomoco-1.0-9 Total Installed Size: 0.19 MiB Net Upgrade Size: 0.00 MiB :: Proceed with installation? [Y/n] n # I ran strace to see what really happens: [root@lnv64 tmp]# strace pacman -U /tmp/lomoco-1.0-9-x86_64.pkg.tar # ... # Here comes the part that could be relevant: write(1, loading packages...\n, 20loading packages... ) = 20 access(/tmp/lomoco-1.0-9-x86_64.pkg.tar.sig, R_OK) = -1 ENOENT (No such file or directory) access(/tmp/lomoco-1.0-9-x86_64.pkg.tar, R_OK) = -1 EACCES (Permission denied) open(/usr/share/locale/en_US.UTF-8/LC_MESSAGES/libalpm.mo, O_RDONLY) = -1 ENOENT (No such file or directory) open(/usr/share/locale/en_US.utf8/LC_MESSAGES/libalpm.mo, O_RDONLY) = -1 ENOENT (No such file or directory) open(/usr/share/locale/en_US/LC_MESSAGES/libalpm.mo, O_RDONLY) = -1 ENOENT (No such file or directory) open(/usr/share/locale/en.UTF-8/LC_MESSAGES/libalpm.mo, O_RDONLY) = -1 ENOENT (No such file or directory) open(/usr/share/locale/en.utf8/LC_MESSAGES/libalpm.mo, O_RDONLY) = -1 ENOENT (No such file or directory) open(/usr/share/locale/en/LC_MESSAGES/libalpm.mo, O_RDONLY) = -1 ENOENT (No such file or directory) write(2, \33[1;31merror: \33[0m, 18error: ) = 18 write(2, '/tmp/lomoco-1.0-9-x86_64.pkg.ta..., 54'/tmp/lomoco-1.0-9-x86_64.pkg.tar': permission denied ) = 54 close(4)= 0 munmap(0x7f6e2c98, 4096)= 0 unlink(/var/lib/pacman/db.lck)= 0 close(3)= 0 munmap(0x7f6e2c981000, 4096)= 0 exit_group(1) = ? +++ exited with 1 +++ So from this line: access(/tmp/lomoco-1.0-9-x86_64.pkg.tar, R_OK) = -1 EACCES (Permission denied) we see that the kernel call access() reports that root doesn't have read access to a 777-permissible file?! Maybe it matters that it's on tmpfs and/or a symlink?
Re: [arch-general] don't casually do things in /tmp directly (was: Strange issue)
Neven Sajko wrote: I used makepkg to build a package from /tmp. The package was then put to the designated directory and a symlink to pwd. When I try to install it with pacman -U /tmp/symlink-to-package, I get an error (permission denied) which I don't get when invoking pacman -U directly with the name of the file (not with the symbolic link). See, like this: [root@lnv64 tmp]# pacman -U /tmp/lomoco-1.0-9-x86_64.pkg.tar loading packages... error: '/tmp/lomoco-1.0-9-x86_64.pkg.tar': permission denied [...] So from this line: access(/tmp/lomoco-1.0-9-x86_64.pkg.tar, R_OK) = -1 EACCES (Permission denied) we see that the kernel call access() reports that root doesn't have read access to a 777-permissible file?! Maybe it matters that it's on tmpfs and/or a symlink? This is probably due to the fs.protected_symlinks sysctl being turned on, which I believe it is by default in Arch. Most symlinks in world-writable sticky directories (like /tmp) are not followed except by processes running as the user that created them. This is to prevent common attacks where a privileged process tries to access what it thinks is not a symlink, but another process manages to insert a symlink to an unrelated file so that the privileged process performs the wrong access. It's not a good idea to build things directly in /tmp like that anyway, for more or less that reason. Creating a subdirectory of /tmp for each new action that needs temporary files is a better approach. --- Drake Wilson
Re: [arch-general] don't casually do things in /tmp directly (was: Strange issue)
Yeah, fs.protected_symlinks is it. Thank you. I usually copy the package dir from /var/abs to /tmp so I didn't notice before that reading symlinks from root of /tmp wasn't allowed.
[arch-general] Please help, after i686 install screen is unreadable blocky white squares.
Please help, after i686 install screen is unreadable blocky white squares.
