Anno domini 2021 Mon, 31 May 00:43:45 -0500 J Leslie Turriff scripsit:
On 2021-05-30 12:10:34 Dr. Nikolaus Klepp wrote:
Things might be different with pulseaudio, but that thing never worked for me, probably the bad carma of it's creator still sticks on it.
Nik
My experience with pulseaudio is the same; I have learned to forbid its installation, and I stick with ALSA. BTW, when I right-click on the KMix applet and choose Select Master Channel, I just get a radio-button list, no way to choose an underlying device. (?)
Interesting. In your screenshot the dropdownlist with the selectable soundcards is missing. Here's what I get on my system.
Nik
Leslie
Operating System: Linux Distribution: openSUSE Leap 15.2 x86_64 Desktop Environment: Trinity Qt: 3.5.0 TDE: R14.0.10 tde-config: 1.0
On 2021-05-31 02:32:12 Dr. Nikolaus Klepp wrote:
Things might be different with pulseaudio, but that thing never worked for me, probably the bad carma of it's creator still sticks on it.
Nik
My experience with pulseaudio is the same; I have learned to forbid its installation, and I stick with ALSA. BTW, when I right-click on the KMix applet and choose Select Master Channel, I just get a radio-button list, no way to choose an underlying device. (?)
Interesting. In your screenshot the dropdownlist with the selectable soundcards is missing. Here's what I get on my system.
Nik
Is it not? I have to wonder if the fellow who packages Trinity for OpenSuSE has disabled that, since in OpenSuSE it's controlled by a YaST module.
Leslie
On Monday 31 May 2021 00:32:12 Dr. Nikolaus Klepp wrote:
Anno domini 2021 Mon, 31 May 00:43:45 -0500
J Leslie Turriff scripsit:
On 2021-05-30 12:10:34 Dr. Nikolaus Klepp wrote:
Things might be different with pulseaudio, but that thing never worked for me, probably the bad carma of it's creator still sticks on it.
Nik
My experience with pulseaudio is the same; I have learned to forbid its installation, and I stick with ALSA. BTW, when I right-click on the KMix applet and choose Select Master Channel, I just get a radio-button list, no way to choose an underlying device. (?)
Interesting. In your screenshot the dropdownlist with the selectable soundcards is missing. Here's what I get on my system.
Nik
Leslie
Operating System: Linux Distribution: openSUSE Leap 15.2 x86_64 Desktop Environment: Trinity Qt: 3.5.0 TDE: R14.0.10 tde-config: 1.0
We both share a dislike of pulseaudio crap (if I recall aright), and prefer alsa. But are you quite sure that no pulseaudio leftovers remain in your system?
After I purge everything connected to pulseaudio, the only choice that remains, or the only one that my system recognizes, is alsa. Then it is automatically chosen as default.
Make sure you purge not only pulseaudio* but also pavucontrol, and similar packages. You probably already know this, I imagine, so this is just a reminder.
That pulseaudio stuff somehow gets into my system through other packages that usually don't mention it.
Also you recommended alsamixer to me a few months ago (thanks much!), wherein you can choose your soundcard. I'm not sure if your choice in alsamixer affects kmix; but I know that I don't have this problem any more.
Bill
William Morder via tde-users wrote:
That pulseaudio stuff somehow gets into my system through other packages that usually don't mention it.
IMO using pulseaudio if you already have dbus is perfectly OK. In the past 2-3 years pulseaudio has become very good and safe to use.
watch out that you do not become a victim of the purists.
On Monday 31 May 2021 04:22:39 pm deloptes wrote:
William Morder via tde-users wrote:
That pulseaudio stuff somehow gets into my system through other packages that usually don't mention it.
IMO using pulseaudio if you already have dbus is perfectly OK. In the past 2-3 years pulseaudio has become very good and safe to use.
watch out that you do not become a victim of the purists.
Agreed, now that PA is stable I use it in concert with alsa. Once you learn all the tricks and oddities. It's easy to use and control. Just pay close attention to the defaults in PA. Also make sure to set your default soundcard.
Kate
On Monday 31 May 2021 13:22:39 deloptes wrote:
William Morder via tde-users wrote:
That pulseaudio stuff somehow gets into my system through other packages that usually don't mention it.
IMO using pulseaudio if you already have dbus is perfectly OK. In the past 2-3 years pulseaudio has become very good and safe to use.
watch out that you do not become a victim of the purists.
No purist here, good sir! I like whatever works; whatever works better, that will do. But I also like to feel that I am in control of my own system. Whenever pulseaudio no longer bothers me by taking over my sound system, then I might leave it there.
If everything just worked, and I felt in control of my own system, then I would probably still be running Windoze or the rotten Apple. It isn't that I set out to be "pure" with some preconceived notion; it just turns out that the things that bother me tend to fall predictably into the same few categories.
At some point in the future, I may change my mind on this or that; otherwise, I will die and at last be freed from these infernal machines.
Bill
William Morder via tde-users wrote:
No purist here, good sir! I like whatever works; whatever works better, that will do. But I also like to feel that I am in control of my own system. Whenever pulseaudio no longer bothers me by taking over my sound system, then I might leave it there.
If everything just worked, and I felt in control of my own system, then I would probably still be running Windoze or the rotten Apple. It isn't that I set out to be "pure" with some preconceived notion; it just turns out that the things that bother me tend to fall predictably into the same few categories.
At some point in the future, I may change my mind on this or that; otherwise, I will die and at last be freed from these infernal machines.
IMO it is much harder to make things work without pulseaudio than with. I have the same mindset as you do and I found out that reading pulseaudio documentation and finding out why things do not work helped me a lot. Few years ago I cam to the conclusion (it was PA 10 or 11) that the version was very buggy, but developers fixed the issues in v12. I compiled v12 myself and see all my problems were gone. Meanwhile with buster and PA v12 all is fine (Except some minors around bluetooth). Now I hear v15 is on the horizon, so you can imagine developers are not sleeping.
Regarding PA taking control over your sound system. This is exactly how it should work to benefit from PA. Let it go and enjoy. I am not advocating for PA. I simply know it works just fine.
We had also few discussions on the dev list with Michele regarding kmix. It needs some adjustments, but it is not possible to do them right now. Michele did some improvements based on the patches one other guy (I am sorry I forgot the name) proposed. So for myself I found out the best is to use the custom setting for the master channel on the pulseaudio mixer set as default (sorry for the cyrillic) and for the fine tunning I use the ALSA mixer and pavucontrol. pavucontrol can control the individual volume of specific application (firefox, audio player etc), which kimix still can not. pavucontrol can also control how Bluetooth (mobile phone) is handled by the audio system.
It indeed depends on the use cases, but more complex use cases require more complex tools and I do not see a chance a purist can do them. In fact what I see are advises based on 5y old experience with PA (perhaps version 10 or earlier), which lead to even bigger issues and end up in loop of errors.
Of course the machine and the choice is yours.
I know that you guys are not the youngest and hope I could help with sharing my experience.
On Tuesday 01 June 2021 01:08:15 deloptes wrote:
William Morder via tde-users wrote:
No purist here, good sir! I like whatever works; whatever works better, that will do. But I also like to feel that I am in control of my own system. Whenever pulseaudio no longer bothers me by taking over my sound system, then I might leave it there.
If everything just worked, and I felt in control of my own system, then I would probably still be running Windoze or the rotten Apple. It isn't that I set out to be "pure" with some preconceived notion; it just turns out that the things that bother me tend to fall predictably into the same few categories.
At some point in the future, I may change my mind on this or that; otherwise, I will die and at last be freed from these infernal machines.
IMO it is much harder to make things work without pulseaudio than with. I have the same mindset as you do and I found out that reading pulseaudio documentation and finding out why things do not work helped me a lot. Few years ago I cam to the conclusion (it was PA 10 or 11) that the version was very buggy, but developers fixed the issues in v12. I compiled v12 myself and see all my problems were gone. Meanwhile with buster and PA v12 all is fine (Except some minors around bluetooth). Now I hear v15 is on the horizon, so you can imagine developers are not sleeping.
Regarding PA taking control over your sound system. This is exactly how it should work to benefit from PA. Let it go and enjoy. I am not advocating for PA. I simply know it works just fine.
We had also few discussions on the dev list with Michele regarding kmix. It needs some adjustments, but it is not possible to do them right now. Michele did some improvements based on the patches one other guy (I am sorry I forgot the name) proposed. So for myself I found out the best is to use the custom setting for the master channel on the pulseaudio mixer set as default (sorry for the cyrillic) and for the fine tunning I use the ALSA mixer and pavucontrol. pavucontrol can control the individual volume of specific application (firefox, audio player etc), which kimix still can not. pavucontrol can also control how Bluetooth (mobile phone) is handled by the audio system.
I don't use sound in any browser, ever. If I want music or a video, I download it, and listen/watch it on a media player. Also I do not use Bluetooth for anything at all.
It indeed depends on the use cases, but more complex use cases require more complex tools and I do not see a chance a purist can do them. In fact what I see are advises based on 5y old experience with PA (perhaps version 10 or earlier), which lead to even bigger issues and end up in loop of errors.
You seem to allude to "problems" (I don't know if that's the right word) that are not obvious, or which I haven't yet experienced. I would be interested to know more, for future reference. As I say, alsa serves my needs at the moment, but I could change my mind. I am open to being convinced.
Of course the machine and the choice is yours.
I know that you guys are not the youngest and hope I could help with sharing my experience.
Well, just from the glance at your screenshot, that is basically what I see in Kmix with pulseaudio as the soundcard. And if that's what you want, it's fine, but I like to see all the controls available.
As an occasional working musician, I like to play around with all the possibilities of channels; for me, Kmix and alsamixer show me the information that I want.
And for recording, of course, I use audacity, which again I find (for my own needs) works best with alsa.
I do not cling to fixed opinions, nor am I fearful of change; but I do want my machines to do what I want. Otherwise, it gets in the way of what I really want to be doing. My machine is supposed to be a tool that facilitates what I am doing. Ideally I would like to just have various presets already configured, so that I can just push a button and start recording - sort of like it used to be back in the good old days.
And while I may be an oldster, it's true, I am a young oldster. Most people my age, and many who are 20 years younger, would have a hard time keeping up with me. (But only if I have had my sleep, and some coffee, and a few hours to ease into the day, which usually begins sometime in the afternoon. And then, once I get myself together ... we're off!)
;-)
Bill
William Morder via tde-users wrote:
I don't use sound in any browser, ever. If I want music or a video, I download it, and listen/watch it on a media player. Also I do not use Bluetooth for anything at all.
OK - it seems we have no common use case here - forget this part then.
It indeed depends on the use cases, but more complex use cases require more complex tools and I do not see a chance a purist can do them. In fact what I see are advises based on 5y old experience with PA (perhaps version 10 or earlier), which lead to even bigger issues and end up in loop of errors.
You seem to allude to "problems" (I don't know if that's the right word) that are not obvious, or which I haven't yet experienced. I would be interested to know more, for future reference. As I say, alsa serves my needs at the moment, but I could change my mind. I am open to being convinced.
forget also the alluded problems
Of course the machine and the choice is yours.
I know that you guys are not the youngest and hope I could help with sharing my experience.
Well, just from the glance at your screenshot, that is basically what I see in Kmix with pulseaudio as the soundcard. And if that's what you want, it's fine, but I like to see all the controls available.
As an occasional working musician, I like to play around with all the possibilities of channels; for me, Kmix and alsamixer show me the information that I want.
this is where it starts getting interested. You ignored completely pavucontrol.
And for recording, of course, I use audacity, which again I find (for my own needs) works best with alsa.
I have not used it that often - I am also interested in music, but I have no time at all. From what I remember jack was a must in combination with several audio cards. But it is also irrelevant to the original problem
Now if you open pavucontrol you should see your multiple sound cards. is the one you want to use as default set as "fall back"?
Otherwise it seems it is indeed a problem with kmix and should be handled as a bug or you try to index the cards and the one becomes 1st from the OS perspective.
cat /etc/modprobe.d/alsa-base.conf options snd_hda_intel index=0 options snd-usb-audio index=1
regards
On 2021-05-31 15:22:39 deloptes wrote:
William Morder via tde-users wrote:
That pulseaudio stuff somehow gets into my system through other packages that usually don't mention it.
IMO using pulseaudio if you already have dbus is perfectly OK. In the past 2-3 years pulseaudio has become very good and safe to use.
watch out that you do not become a victim of the purists.
tde-users mailing list -- users@trinitydesktop.org To unsubscribe send an email to users-leave@trinitydesktop.org Web mail archive available at https://mail.trinitydesktop.org/mailman3/hyperkitty/list/users@trinitydeskt op.org
pulseaudio has never worked for me; I used to try to get it to work after every upgrade, but finally I have just told YaST to Forbid installation of its components.
Leslie -- openSUSE Leap 15.2 x86_64 Qt: 3.5.0 TDE: R14.0.9 tde-config: 1.0
J Leslie Turriff wrote:
pulseaudio has never worked for me; I used to try to get it to work after every upgrade, but finally I have just told YaST to Forbid installation of its components.
Don't know about SuSE or your setup. It works great here since version 12.2.
regards
On Monday 31 May 2021 10:54:18 am William Morder via tde-users wrote:
On Monday 31 May 2021 00:32:12 Dr. Nikolaus Klepp wrote:
Anno domini 2021 Mon, 31 May 00:43:45 -0500
J Leslie Turriff scripsit:
On 2021-05-30 12:10:34 Dr. Nikolaus Klepp wrote:
Things might be different with pulseaudio, but that thing never worked for me, probably the bad carma of it's creator still sticks on it.
Nik
My experience with pulseaudio is the same; I have learned to forbid its installation, and I stick with ALSA. BTW, when I right-click on the KMix applet and choose Select Master Channel, I just get a radio-button list, no way to choose an underlying device. (?)
Interesting. In your screenshot the dropdownlist with the selectable soundcards is missing. Here's what I get on my system.
Nik
Leslie
Operating System: Linux Distribution: openSUSE Leap 15.2 x86_64 Desktop Environment: Trinity Qt: 3.5.0 TDE: R14.0.10 tde-config: 1.0
We both share a dislike of pulseaudio crap (if I recall aright), and prefer alsa. But are you quite sure that no pulseaudio leftovers remain in your system?
After I purge everything connected to pulseaudio, the only choice that remains, or the only one that my system recognizes, is alsa. Then it is automatically chosen as default.
Make sure you purge not only pulseaudio* but also pavucontrol, and similar packages. You probably already know this, I imagine, so this is just a reminder.
That pulseaudio stuff somehow gets into my system through other packages that usually don't mention it.
Also you recommended alsamixer to me a few months ago (thanks much!), wherein you can choose your soundcard. I'm not sure if your choice in alsamixer affects kmix; but I know that I don't have this problem any more.
Bill ____________________________________________________
There is also a program called "default sound card" which will set it for you. The package name for pclo is "asoundconf & asoundconf-gtk"
Kate
Hi Kate!
Anno domini 2021 Mon, 31 May 16:56:43 -0400 Borg Labs scripsit:
[...] There is also a program called "default sound card" which will set it for you. The package name for pclo is "asoundconf & asoundconf-gtk"
asoundconf-gtk requires GTK2, which is gone on chimera/debian11.
BTW, anybody using WebRTC be preapared for a nasty surprise with chromium_90: The only working mic is on your default soundcard aka #0. USB mics don't work. You might want to keep chromium_89 till this is fixed.
Nik
Kate ____________________________________________________ tde-users mailing list -- users@trinitydesktop.org To unsubscribe send an email to users-leave@trinitydesktop.org Web mail archive available at https://mail.trinitydesktop.org/mailman3/hyperkitty/list/users@trinitydeskto...
On Friday 04 June 2021 03:06:43 pm Dr. Nikolaus Klepp wrote:
Borg Labs scripsit:
[...] There is also a program called "default sound card" which will set it for you. The package name for pclo is "asoundconf & asoundconf-gtk"
asoundconf-gtk requires GTK2, which is gone on chimera/debian11.
BTW, anybody using WebRTC be preapared for a nasty surprise with chromium_90: The only working mic is on your default soundcard aka #0. USB mics don't work. You might want to keep chromium_89 till this is fixed.
Huh, I thought WebRTC was a security hole and should be completely turned off? Here's the bit I've seen:
"WebRTC allows websites to view your unique IP address and expose your identifying details, even if you are using a VPN."
I guess if you don't care, but I'm a bit tired of G, FB, and the rest tracking everything everyone does...
Best, Michael
Anno domini 2021 Fri, 4 Jun 15:55:44 -0500 Michael scripsit:
On Friday 04 June 2021 03:06:43 pm Dr. Nikolaus Klepp wrote:
Borg Labs scripsit:
[...] There is also a program called "default sound card" which will set it for you. The package name for pclo is "asoundconf & asoundconf-gtk"
asoundconf-gtk requires GTK2, which is gone on chimera/debian11.
BTW, anybody using WebRTC be preapared for a nasty surprise with chromium_90: The only working mic is on your default soundcard aka #0. USB mics don't work. You might want to keep chromium_89 till this is fixed.
Huh, I thought WebRTC was a security hole and should be completely turned off? Here's the bit I've seen:
"WebRTC allows websites to view your unique IP address and expose your identifying details, even if you are using a VPN."
I guess if you don't care, but I'm a bit tired of G, FB, and the rest tracking everything everyone does...
Sure. Problem is, I need jitsi working. Big surprise after todays update: chromium is not able to select any mic but the one on card #0. All other devices get a "resource busy" error - which is absolutely useless. BTW. chromium_89 shows the same problem with kernel 5.10.40. But audacity works like a charm :(
Nik
Best, Michael ____________________________________________________ tde-users mailing list -- users@trinitydesktop.org To unsubscribe send an email to users-leave@trinitydesktop.org Web mail archive available at https://mail.trinitydesktop.org/mailman3/hyperkitty/list/users@trinitydeskto...
"WebRTC allows websites to view your unique IP address and expose your identifying details, even if you are using a VPN."
I guess if you don't care, but I'm a bit tired of G, FB, and the rest tracking everything everyone does...
Sure. Problem is, I need jitsi working. Big surprise after todays update: chromium is not able to select any mic but the one on card #0. All other devices get a "resource busy" error - which is absolutely useless. BTW. chromium_89 shows the same problem with kernel 5.10.40. But audacity works like a charm :(
Try Palemoon and/or Waterfox? That'd at least get you out of some of the Google hell Chromium is...
PaleMoon has no WebRTC BTW...
-- Mavridis Philippe
Icecat, but you either have to compile from source, or use a third-party deb installer (if you are running a Debian-type system).
I did check out the deb; there is a checksum to verify its authenticity. And I install it using sudo torify dpkg, works just fine.
But I would still avoid that WebRTC stuff. I don't hear good things about it except from the people pushing it.
Bill
On Friday 04 June 2021 14:47:01 Mavridis Philippe wrote:
PaleMoon has no WebRTC BTW...
-- Mavridis Philippe ____________________________________________________ tde-users mailing list -- users@trinitydesktop.org To unsubscribe send an email to users-leave@trinitydesktop.org Web mail archive available at https://mail.trinitydesktop.org/mailman3/hyperkitty/list/users@trinitydeskt op.org
said William Morder via tde-users:
| But I would still avoid that WebRTC stuff. I don't hear good things | about it except from the people pushing it.
Go here and see what you think:
https://ipleak.net/ -- dep
Pictures: http://www.ipernity.com/doc/depscribe/album Column: https://www.athensnews.com/opinion/columns/the_view_from_mudsock_heights/
On Friday 04 June 2021 19:19:22 dep wrote:
said William Morder via tde-users: | But I would still avoid that WebRTC stuff. I don't hear good things | about it except from the people pushing it.
Go here and see what you think:
https://ipleak.net/
dep
Yup, I use that site every single day, also this site:
http://jlve2y45zacpbz6s.onion/ http://t3qi4hdmvqo752lhyglhyb5ysoutggsdocmkxhuojfn62ntpcyydwmqd.onion/
Use over Tor! There are also https pages, and a non-onion page.
Bill
P.S. Sorry about top-posting earlier. I had just come home, and was a little out of it.
Hi all!
This is in answer to all the postings in this thread.
Anno domini 2021 Fri, 4 Jun 16:44:40 -0500 Michael scripsit:
"WebRTC allows websites to view your unique IP address and expose your identifying details, even if you are using a VPN."
I guess if you don't care, but I'm a bit tired of G, FB, and the rest tracking everything everyone does...
Sure. Problem is, I need jitsi working. Big surprise after todays update: chromium is not able to select any mic but the one on card #0. All other devices get a "resource busy" error - which is absolutely useless. BTW. chromium_89 shows the same problem with kernel 5.10.40. But audacity works like a charm :(
Try Palemoon and/or Waterfox? That'd at least get you out of some of the Google hell Chromium is...
Firefox and all its decendents use the first input source als mic and you cannot select any other. That is true for firfox, waterfox, icecat ... whatever. As the first input source may aor may not be anything real, it renders firefox quite useless for any browserbased (video)conference.
It's in the very nature of WebRTC to expose your address, as it's using p2p for 2 client conversation. If that's a problem, don't use it. I myself use tox for secure conferences, but that does not allow videochat for more than 2 parties (well, you can work around that ...).
So chrome/chromium is/was the only browser capable of selecting the correct input source. With kernel 5.10.40-1 chromium is not able to so any more for input source served by snd_usb_audio. I do not think it's directly related to snd_usb_audio but to all devices that only present input sources without output sinks like webcams, usb-mics etc., as multiple onboard soundcards and PCI soundcards on the same system are selectable within chromium and they all have source+sink. Looks like a classic "intelligent programmer made a sesible choice" problem to me :/
My workaround is for now: attach a analog mic to the onboard soundcard aka card#0. That mic is then used by firefox and chromium alike. Well, take what you get and run like hell ... aint there a config option for alsa to build assign the default/sysdefault mic to device and the output to an other?
Niki
In answer to myself - and so that it's not lost:
Reserve card#0 for the 4th soundcard or snd_usb_audio - whatever comes first:
# /etc/modprobe.d/alsa-base.conf options snd_usb_audio index=0 options snd_hda_intel index=1,2,3
Now chromium still uses mic#0 of card#0 - which may or may not be the working virtual mic of the usb mic. In my case it's not a working mic, I have to select mic#1 of card#0. Anyway, it is fairly persistent and at least works across reboots in a consistent way - that is, till you have 2 snd_usb_audio devices or ... *sigh*
And for the record: I even tried pulsaudio - but as my workaround does not mention it you can safely assume that I did not have great success with that thingie.
Nik
Anno domini 2021 Sat, 5 Jun 14:02:23 +0200 Dr. Nikolaus Klepp scripsit:
Hi all!
This is in answer to all the postings in this thread.
Anno domini 2021 Fri, 4 Jun 16:44:40 -0500 Michael scripsit:
"WebRTC allows websites to view your unique IP address and expose your identifying details, even if you are using a VPN."
I guess if you don't care, but I'm a bit tired of G, FB, and the rest tracking everything everyone does...
Sure. Problem is, I need jitsi working. Big surprise after todays update: chromium is not able to select any mic but the one on card #0. All other devices get a "resource busy" error - which is absolutely useless. BTW. chromium_89 shows the same problem with kernel 5.10.40. But audacity works like a charm :(
Try Palemoon and/or Waterfox? That'd at least get you out of some of the Google hell Chromium is...
Firefox and all its decendents use the first input source als mic and you cannot select any other. That is true for firfox, waterfox, icecat ... whatever. As the first input source may aor may not be anything real, it renders firefox quite useless for any browserbased (video)conference.
It's in the very nature of WebRTC to expose your address, as it's using p2p for 2 client conversation. If that's a problem, don't use it. I myself use tox for secure conferences, but that does not allow videochat for more than 2 parties (well, you can work around that ...).
So chrome/chromium is/was the only browser capable of selecting the correct input source. With kernel 5.10.40-1 chromium is not able to so any more for input source served by snd_usb_audio. I do not think it's directly related to snd_usb_audio but to all devices that only present input sources without output sinks like webcams, usb-mics etc., as multiple onboard soundcards and PCI soundcards on the same system are selectable within chromium and they all have source+sink. Looks like a classic "intelligent programmer made a sesible choice" problem to me :/
My workaround is for now: attach a analog mic to the onboard soundcard aka card#0. That mic is then used by firefox and chromium alike. Well, take what you get and run like hell ... aint there a config option for alsa to build assign the default/sysdefault mic to device and the output to an other?
Niki
Dr. Nikolaus Klepp wrote:
And for the record: I even tried pulsaudio - but as my workaround does not mention it you can safely assume that I did not have great success with that thingie.
that is strange because PA shows up usually as card0/mic0
Dr. Nikolaus Klepp wrote:
BTW, anybody using WebRTC be preapared for a nasty surprise with chromium_90: The only working mic is on your default soundcard aka #0. USB mics don't work. You might want to keep chromium_89 till this is fixed.
why WebRTC and why Chromium?!
I am not sure if skype is using ... as it uses chromium code in the background but this is a different topic.
What about Firefox - I know microphone and camera access there are disabled by default.
-
Borg Labs -
deloptes -
dep -
Dr. Nikolaus Klepp -
J Leslie Turriff -
Mavridis Philippe -
Michael -
William Morder