On Sun, 2025-02-09 at 10:52 +0100, François Patte wrote:
> Since I solved this problem, rkhunter bores me with "Suspicious file
> types found in /dev:"
>
> /dev/shm/lttng-ust-wait-8
>
> If I ask lsof to see what uses this "suspicious" file, I get :
> COMMANDPID USER FD TYPE DEVICE SIZE/OF
Le 2025-01-30 23:20, Tim via users a écrit :
On Thu, 2025-01-30 at 11:18 +0100, François Patte wrote:
So I tried to install pipewire-pulseaudio but dnf answered that
pipewire-pulseaudio conflicted with pulseaudio. Since I had nothing to
lose I added --allowerasing and pipewire-pulseaudio was ins
On Thu, 2025-01-30 at 11:18 +0100, François Patte wrote:
> So I tried to install pipewire-pulseaudio but dnf answered that
> pipewire-pulseaudio conflicted with pulseaudio. Since I had nothing to
> lose I added --allowerasing and pipewire-pulseaudio was installed and...
> the problem was solved.
> On 30 Jan 2025, at 10:19, François Patte
> wrote:
>
> Who can understand this!
The service name is wrong.
Here are the pipewire services I see running.
pipewire-pulse.service
loaded active running PipeWire PulseAudio
pipew
Le 2025-01-29 00:46, Tim via users a écrit :
On Tue, 2025-01-28 at 12:18 +0100, François Patte wrote:
I have some sound problems on my f40:
1- sound works with some applications like audacious or vlc or
kaffeine
but it does not work from sources via firefox or chromium
2- I have an usb camer
On Tue, 2025-01-28 at 12:18 +0100, François Patte wrote:
> I have some sound problems on my f40:
>
> 1- sound works with some applications like audacious or vlc or kaffeine
> but it does not work from sources via firefox or chromium
>
> 2- I have an usb camera with a mic and this mic is not dete
On Tue, 20 Mar 2018 00:54:33 +0100
Wolfgang Pfeiffer wrote:
> On Sat, 17 Mar 2018 11:08:46 +0100
> François Patte wrote:
>
> >
> > In ~/.config/pulse I have:
> > bd9a117e29a44dd4b335896e866a41d2-default-sink
> > bd9a117e29a44dd4b335896e866a41d2-default-source
> >
> > Which are empty when I lo
On Sat, 17 Mar 2018 11:08:46 +0100
François Patte wrote:
>
> In ~/.config/pulse I have:
> bd9a117e29a44dd4b335896e866a41d2-default-sink
> bd9a117e29a44dd4b335896e866a41d2-default-source
>
> Which are empty when I log-in (in that case the config is: "sortie
> stéréo numérique (iec958) + entrée s
Le 18/03/2018 à 23:27, stan a écrit :
> On Sun, 18 Mar 2018 11:33:36 +0100
> François Patte wrote:
>
Googleing a lot, I tried some configuration "by hand" and reach a state
that I cannot understand.
I used: pacmd list-cards in order to identify my cards:
-
On 19/3/18 9:55 am, Ed Greshko wrote:
On 03/19/18 06:44, Ed Greshko wrote:
FWIW, I have a ~/.pulse directory. Within it there is a file called
741a5ee204e44a41982409c7e07d04de-default-sink which contains
Oh, strangely?, I found that on one system the directory was ~/.pulse while
another
has
On 03/19/18 06:44, Ed Greshko wrote:
> FWIW, I have a ~/.pulse directory. Within it there is a file called
> 741a5ee204e44a41982409c7e07d04de-default-sink which contains
Oh, strangely?, I found that on one system the directory was ~/.pulse while
another
has a set of files in ~/.config/pulse
I
On 03/19/18 06:27, stan wrote:
> It was a guess, using alsa conventions. I couldn't find any pulse
> examples that set the sink so I could see what convention they use.
FWIW, I have a ~/.pulse directory. Within it there is a file called
741a5ee204e44a41982409c7e07d04de-default-sink which conta
On Sun, 18 Mar 2018 11:33:36 +0100
François Patte wrote:
> > You must have run alsainfo.sh after you corrected your system
> > because this is not what it showed. It showed that the default was
> > pcm (analog). For some reason, at start up, your system is
> > defaulting to the iec958 (digital)
Le 17/03/2018 à 17:32, stan a écrit :
> On Sat, 17 Mar 2018 11:08:46 +0100
> François Patte wrote:
>
>> But in /usr/lib/modprobe.d/ I have a dist-alsa.conf file with:
>>
>> # ALSA Sound Support
>> #
>> # We want to ensure that snd-seq is always loaded for those who want
>> to use # the sequencer
On Sat, 17 Mar 2018 11:08:46 +0100
François Patte wrote:
> But in /usr/lib/modprobe.d/ I have a dist-alsa.conf file with:
>
> # ALSA Sound Support
> #
> # We want to ensure that snd-seq is always loaded for those who want
> to use # the sequencer interface, but we can't do this automatically
> t
Le 16/03/2018 à 20:52, stan a écrit :
> On Fri, 16 Mar 2018 18:50:20 +0100
> François Patte wrote:
>
>> Here is the link:
>>
>> http://www.alsa-project.org/db/?f=5ebae0714f190eceb8b6ff7ceb435f434d48ad85
>
>>From that output, you should have sound. Your system put the PCM
> (analog) card in the
On Fri, 16 Mar 2018 18:50:20 +0100
François Patte wrote:
> Here is the link:
>
> http://www.alsa-project.org/db/?f=5ebae0714f190eceb8b6ff7ceb435f434d48ad85
From that output, you should have sound. Your system put the PCM
(analog) card in the 0 slot, and that is the default location for sound
t
Le 16/03/2018 à 18:19, stan a écrit :
> On Fri, 16 Mar 2018 09:06:12 +0100
> François Patte wrote:
>
>> journactl -u pulseaudio (or alsa*) returns nothing
>>
>>> How about problems during
>>> discovery at boot in recognizing the sound devices?
>>
>> How can I check that?
>
> It sounds like you
On Fri, 16 Mar 2018 09:06:12 +0100
François Patte wrote:
> journactl -u pulseaudio (or alsa*) returns nothing
>
> > How about problems during
> > discovery at boot in recognizing the sound devices?
>
> How can I check that?
It sounds like you need a stronger approach. Can you go here
https:
On 03/16/18 16:06, François Patte wrote:
> Le 15/03/2018 à 22:05, stan a écrit :
>> On Thu, 15 Mar 2018 11:03:32 +0100
>> François Patte wrote:
>>
After 3, when sound is working, open pavucontrol, go to the output
devices tab, and click the green checkmark on the device that you
w
Le 15/03/2018 à 22:05, stan a écrit :
> On Thu, 15 Mar 2018 11:03:32 +0100
> François Patte wrote:
>
>>> After 3, when sound is working, open pavucontrol, go to the output
>>> devices tab, and click the green checkmark on the device that you
>>> want pulseaudio to start with.
>>
>> That is wha
On Thu, 15 Mar 2018 11:03:32 +0100
François Patte wrote:
> > After 3, when sound is working, open pavucontrol, go to the output
> > devices tab, and click the green checkmark on the device that you
> > want pulseaudio to start with.
>
> That is what I do evetime I lo-in but this does not surv
Le 14/03/2018 à 19:36, stan a écrit :
> On Wed, 14 Mar 2018 10:36:33 +0100
> François Patte wrote:
>
>> When I log-in, sound is deactivated and I have to manually start it,
>> doing:
>
> Are you sure sound is deactivated? Is it possible it is trying to use
> the digital output associated with y
On Wed, 14 Mar 2018 10:36:33 +0100
François Patte wrote:
> When I log-in, sound is deactivated and I have to manually start it,
> doing:
Are you sure sound is deactivated? Is it possible it is trying to use
the digital output associated with your video card? It is usually
found first because v
On 06/02/2015 11:37 PM, dwoody5654 wrote:
On 06/02/2015 03:03 PM, Steven Stern wrote:
On 06/02/2015 01:52 PM, dwoody5654 wrote:
Posted here and on alsa mailing list some time ago - many comments but
none fixed the problem.
This is the link to bug report:
https://bugzilla.redhat.com/show_bug.cgi
On 06/02/2015 03:03 PM, Steven Stern wrote:
On 06/02/2015 01:52 PM, dwoody5654 wrote:
Posted here and on alsa mailing list some time ago - many comments but
none fixed the problem.
This is the link to bug report:
https://bugzilla.redhat.com/show_bug.cgi?id=1101278
And now I am officially confus
On Tue, 02 Jun 2015 15:03:34 -0500
Steven Stern wrote:
> On 06/02/2015 01:52 PM, dwoody5654 wrote:
> > Posted here and on alsa mailing list some time ago - many comments
> > but none fixed the problem.
> > This is the link to bug report:
> > https://bugzilla.redhat.com/show_bug.cgi?id=1101278
> >
On 06/02/2015 01:52 PM, dwoody5654 wrote:
> Posted here and on alsa mailing list some time ago - many comments but
> none fixed the problem.
> This is the link to bug report:
> https://bugzilla.redhat.com/show_bug.cgi?id=1101278
>
> And now I am officially confused.
> To recap:
> This computer is
On Thu, 15 Aug 2013 13:44:10 -0400
"William W. Austin" wrote:
> Last weekend I did a clean install of Fedora 19 on my main
> workstation replacing fc17 which had been there. (As I usually do, I
> pulled the drive containing /, /tmp, /var, and swap and replaced it
> there. That drive is in anoth
On 03/29/2012 09:55 PM, Richard Shaw wrote:
On Thu, Mar 29, 2012 at 10:50 AM, Junayeed Ahnaf Nirjhor
wrote:
Hello,
I'm running 64 bit Fedora 16 (All up to date) and gstreamer backend. Now the
problem is:
I was having no issues with sound whatsoever. But few days back I plugged in
an USB head
On Thu, Mar 29, 2012 at 10:50 AM, Junayeed Ahnaf Nirjhor
wrote:
> Hello,
>
> I'm running 64 bit Fedora 16 (All up to date) and gstreamer backend. Now the
> problem is:
>
> I was having no issues with sound whatsoever. But few days back I plugged in
> an USB headphone. That thing got proper sound a
On 6/19/11 8:50 AM, François Patte wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Bonjour,
>
> I have a problem with my sound card on my laptop (Dell latitude E6400).
Get in contact with Dell and ask that they replace the Laptop Speaker
panel part. This is a known problem with Dell
On 06/15/2011 03:23 PM, Richard Shaw wrote:
> While diagnosing my sound issues which I at first attributed to my new
> Creative T6100 speakers (yeah, they're pretty low end for surround
> systems), I found that the sound quality was still poor when I plugged
> in my headphones to the front audio po
> Mar 24 15:50:09 localhost pulseaudio[21192]: main.c: Daemon startup failed.
>
> *But I don't know what to do!!!
>
> any help please.
I don't have a solution to your problem, but you might want to check out
the archives of this site:
http://ccrma-mail.stanford.edu/mailman/listinfo/planetccr
Hi
I found these messages in /var/log/messages
*Mar 24 15:50:09 localhost pulseaudio[21197]: module-alsa-sink.c: Failed to
parse module arguments
Mar 24 15:50:09 localhost pulseaudio[21197]: module.c: Failed to load
module "module-alsa-sink" (argument: "sink_name=M1010LT_Analog_Out
device=hw:M1010L
Hello,
It is me again
[adel@localhost deveuropar]$ pulseaudio --start
E: main.c: Daemon startup failed.
I followed this link to configure my pulseaudio but when starting pulseaudio
I get this problem.
Can pulseaudio tell me why the daemon does not start?
http://www.fedoraforum.org/forum/showthr
Hello,
In fact, I have search the web for the problem. I found that there are
somes posts that talk about sound problem with F14.
However, My probleme is that the loose of the sound take place 3 days after
the installation.
Initially, I had sound.
I tried also with kde desktop; but with no resul
Hello
I think that the gnome version that I have have a problem with sound.
I restarted pulseaudio but there is no sound.
I tried to play something in konsole but with no result.
regards
Adel
Le 24 mars 2011 10:24, François Patte
a écrit :
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Le 24/03/2011 09:35, Adel ESSAFI a écrit :
>
> Hello,
> I have a sound problem with my new F14 installed on dell laptop.
>
> I want to know if it is possible to restart the sound server without
> restarting Fedora.
pulseaudio -k
pulseaudio --start
39 matches
Mail list logo