Bug#965230: closed by Felipe Sateler (Re: Bug#965230: pulseaudio: writes to mount point prior to /tmp being mounted)
(Please keep the bug on CC). On Tue, Jul 28, 2020 at 11:27 AM Edmund H. Ramm wrote: > Estimado Felipe, > > Felipe Sateler writes: > > > [...] > > Anyway, those directories are created when there is no runtime directory > > for pulseaudio to use. That this is happening before /tmp is mounted, it > > means that something is trying to use pulseaudio that early during boot. > > That then it is created again, means some other user (or your own user, > but > > in an unclean environment) is trying to use pulseaudio. > > > > Who owns that directory? Do you have logs that may show who is creating > > that? > >if I had, I'd supplied them. The user is (was) root, and the temporary > directory is created from initramfs without leaving a trace in the journal. > The only hint that something went wrong is when /tmp gets mounted on a then > no longer clean mount point. > This is very weird. The initramfs should have an in-memory /tmp. Are you sure it is created in the intiramfs? -- Saludos, Felipe Sateler
Bug#965230: closed by Felipe Sateler (Re: Bug#965230: pulseaudio: writes to mount point prior to /tmp being mounted)
Control: reopen -1 On Sat, Jul 18, 2020 at 3:25 PM Edmund H. Ramm wrote: > Estimado Felipe, > >what further information apart from that provided by reportbug, the > questions I answered to reportbug, the subject "pulseaudio writes to > /tmp mount point prior to /tmp being mounted" and a name pattern > (pulse-PKdhtXMmr18n) of the directories pulseaudio writes to the > /tmp mount point prior to /tmp being mounted, do you require? Maybe > that, a few seconds later, after /tmp (sda9 in my case) finally has > been mounted, a directory with exactly the same name gets created > there? > Sorry. I didn't see the last part of the message (I saw the empty template questions). Sorry for the blunt message. >Please let me know what further information is needed. > Anyway, those directories are created when there is no runtime directory for pulseaudio to use. That this is happening before /tmp is mounted, it means that something is trying to use pulseaudio that early during boot. That then it is created again, means some other user (or your own user, but in an unclean environment) is trying to use pulseaudio. Who owns that directory? Do you have logs that may show who is creating that? -- Saludos, Felipe Sateler
