On 05/10/2021 06:51, Adi Pircalabu wrote:
On 04/10/2021 09:43, Adi Pircalabu wrote:
Could you also post the output of "ps -Z" for each of the pipewire processes as
well as checking to see if these
match?
[egreshko@meimei ~]$ ls -Z /usr/bin/pipewire*
system_u:object_r:bin_t:s0 /usr/bin/pipewire
> On 04/10/2021 09:43, Adi Pircalabu wrote:
>
> Could you also post the output of "ps -Z" for each of the pipewire processes
> as
> well as checking to see if these
> match?
>
>
> [egreshko@meimei ~]$ ls -Z /usr/bin/pipewire*
> system_u:object_r:bin_t:s0 /usr/bin/pipewire
> system_u:object_r:bi
On 04/10/2021 09:43, Adi Pircalabu wrote:
$ ps auxww | egrep pipewire
adi 2655 0.2 0.0 349932 17768 ?S
Could you also post the output of "ps -Z" for each of the pipewire processes as
well as checking to see if these
match?
[egreshko@meimei ~]$ ls -Z /usr/bin/pipewire*
system
On 04/10/2021 09:43, Adi Pircalabu wrote:
Didn't have setroubleshoot-server, so I went and installed it. "sealert -b"
does nothing, or I don't know how to use it yet. Then I went and analyzed the
audit
log with "sealert -a /var/log/audit/audit.log" and here's the important
bit:
type=AVC msg=aud
> Didn't have setroubleshoot-server, so I went and installed it. "sealert -b"
> does nothing, or I don't know how to use it yet. Then I went and analyzed the
> audit
> log with "sealert -a /var/log/audit/audit.log" and here's the important
> bit:
>
> type=AVC msg=audit(1633309984.892:327): avc:
> On 04/10/2021 08:56, Adi Pircalabu wrote:
>
> If you run "sealert -b" what does it have for "troubleshooting"?
>
> I'm running KDE/F34 and not seeing any issues.
Didn't have setroubleshoot-server, so I went and installed it. "sealert -b"
does nothing, or I don't know how to use it yet. Then I
On 04/10/2021 08:56, Adi Pircalabu wrote:
ausearch -m AVC,USER_AVC
[...]
time->Sat Oct 2 13:35:30 2021
type=PROCTITLE msg=audit(1633145730.776:6604): proctitle="(systemd)"
type=SOCKADDR msg=audit(1633145730.776:6604): saddr=1000
type=SYSCALL msg=audit(1633145730.776:6604
ausearch -m AVC,USER_AVC
[...]
time->Sat Oct 2 13:35:30 2021
type=PROCTITLE msg=audit(1633145730.776:6604): proctitle="(systemd)"
type=SOCKADDR msg=audit(1633145730.776:6604): saddr=1000
type=SYSCALL msg=audit(1633145730.776:6604): arch=c03e syscall=46
success=yes exi
If I stop pipewire I lose sound, so if I run it in the foreground it ll be
closed if I close the terminal window before logout. It appears to be related
to selinux. If I boot the laptop with selinux=0 kernel argument sound works
fine. If I remove selinux=0 arg and reboot I lose sound again. It a
On 04/10/2021 08:08, Adi Pircalabu wrote:
$ systemctl --user status pipewire
Failed to get properties: Process org.freedesktop.systemd1 exited with status 1
$ systemctl --user status pipewire-pulse.socket
Failed to get properties: Process org.freedesktop.systemd1 exited with status 1
$ systemctl
$ systemctl --user status pipewire
Failed to get properties: Process org.freedesktop.systemd1 exited with status 1
$ systemctl --user status pipewire-pulse.socket
Failed to get properties: Process org.freedesktop.systemd1 exited with status 1
$ systemctl --user status pipewire-pulse.service
Failed
> On Sun, 03 Oct 2021 23:44:44 -
> Adi Pircalabu wrote:
>
>
> Check the dumb stuff first! I have forgotten I left mute on before :-).
> I've also had linux forget which sound device I told it to use.
> There's always booting off a live image and seeing if sound works
> there, if not, might be
On Sun, 03 Oct 2021 23:44:44 -
Adi Pircalabu wrote:
> I'm very confused at this point :)
Check the dumb stuff first! I have forgotten I left mute on before :-).
I've also had linux forget which sound device I told it to use.
There's always booting off a live image and seeing if sound works
th
Hi, been running a fresh install of f34 on my laptop for about a week or so
with no sound issues and this morning after booting (previous state was shut
down) I discovered there's no sound in gnome. Worked perfectly fine last week.
Where do I start with the debugging?
rpm -qa kernel-\* | sort
ke
On 04/02/12 10:25, Mark LaPierre wrote:
On 02/04/2012 03:42 AM, Bob Goodwin wrote:
On 03/02/12 23:11, Patrick O'Callaghan wrote:
On Fri, 2012-02-03 at 20:01 -0500, Mark LaPierre wrote:
On 02/03/2012 12:26 PM, Bob Goodwin wrote:
Sound stopped working after I tried a USB Sound Adapter,
On 02/04/2012 03:42 AM, Bob Goodwin wrote:
On 03/02/12 23:11, Patrick O'Callaghan wrote:
On Fri, 2012-02-03 at 20:01 -0500, Mark LaPierre wrote:
On 02/03/2012 12:26 PM, Bob Goodwin wrote:
Sound stopped working after I tried a USB Sound Adapter, which
only lit its indicator leds.
Als
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 02/04/2012 06:47 AM, Bob Goodwin wrote:
> On 04/02/12 05:21, T.C. Hollingsworth wrote:
>> Sorry I can't be of more help. If any of the above doesn't work,
you're probably right about it being a hardware issue. Everything
else in PA-land looks fine.
On 04/02/12 05:21, T.C. Hollingsworth wrote:
Sorry I can't be of more help. If any of the above doesn't work,
you're probably right about it being a hardware issue. Everything else
in PA-land looks fine. -T.C.
No, that's a lot of help, it gives me more insight into how to
troubl
> [bobg@box6 ~]$ pacmd info
> Welcome to PulseAudio! Use "help" for usage information.
Below is the part that lists devices that output sounds. It's only
showing one device, so theoretically the USB device isn't confusing
PulseAudio.
> 1 sink(s) available.
> * index: 0
> name:
> driver:
On 04/02/12 04:17, Frank Murphy wrote:
On 04/02/12 09:11, Bob Goodwin wrote:
Is "pacmd info" a command? I cant seem to do anything with it,
"locate" shows nothing?
rpm -q pulseaudio-utils
if not there:
yum install pulseaudio-utils
Thanks Frank, that is it.
Bob
--
users mailing list
use
On 04/02/12 03:51, T.C. Hollingsworth wrote:
On Feb 3, 2012 10:27 AM, "Bob Goodwin" wrote:
>
>
> Sound stopped working after I tried a USB Sound Adapter, which
> only lit its indicator leds.
> Bob
If aplay is working then something is probably screw
On 04/02/12 09:11, Bob Goodwin wrote:
Is "pacmd info" a command? I cant seem to do anything with it,
"locate" shows nothing?
rpm -q pulseaudio-utils
if not there:
yum install pulseaudio-utils
--
Regards,
Frank Murphy, friend of fedoraproject
UTF_8 Encoded
--
users mailing list
users@lists.
On 04/02/12 03:51, T.C. Hollingsworth wrote:
On Feb 3, 2012 10:27 AM, "Bob Goodwin" wrote:
>
>
> Sound stopped working after I tried a USB Sound Adapter, which
> only lit its indicator leds.
>
If aplay is working then something is probably screw
On Feb 3, 2012 10:27 AM, "Bob Goodwin" wrote:
>
>
> Sound stopped working after I tried a USB Sound Adapter, which
> only lit its indicator leds.
>
> Normally the following should produce sound from the loudspeaker.
> [root@box6 bobg]#
On 03/02/12 23:11, Patrick O'Callaghan wrote:
On Fri, 2012-02-03 at 20:01 -0500, Mark LaPierre wrote:
On 02/03/2012 12:26 PM, Bob Goodwin wrote:
Sound stopped working after I tried a USB Sound Adapter, which
only lit its indicator leds.
Also, it would be helpful if there was a way to gen
On Fri, 2012-02-03 at 20:01 -0500, Mark LaPierre wrote:
> On 02/03/2012 12:26 PM, Bob Goodwin wrote:
> >
> > Sound stopped working after I tried a USB Sound Adapter, which
> > only lit its indicator leds.
> >
> > Normally the following should produce sound from the
On 02/03/2012 12:26 PM, Bob Goodwin wrote:
Sound stopped working after I tried a USB Sound Adapter, which
only lit its indicator leds.
Normally the following should produce sound from the loudspeaker.
[root@box6 bobg]# aplay /usr/share/sounds/purple/login.wav
ALSA lib pcm_dmix.c:1018
Sound stopped working after I tried a USB Sound Adapter, which
only lit its indicator leds.
Normally the following should produce sound from the loudspeaker.
[root@box6 bobg]# aplay /usr/share/sounds/purple/login.wav
ALSA lib pcm_dmix.c:1018:(snd_pcm_dmix_open
28 matches
Mail list logo
