Re: Virtual background for Zoom video

[Tim via users]

On Tue, 2021-02-09 at 22:44 +1100, Stephen Morris wrote:
> Just one question, what do you mean by green screen? I use zoom on
> my work laptop in Windows 10 showing static and animated backgrounds
> behind the camera image so that people can't see anything in the room
> behind me, and I didn't think there was anything special in my zoom
> configuration.

There's a few ways a device could detect the foreground (you) from the
background (everything else) and use an alternative background image:

Detect a particular colour (like a green or blue background).

Detect a particular level (like a bright white or black background).

Something like MPEG compression.  Where any pixels that change due to
movement are foreground, anything that stays static would be the
background.  That has the potential for some very trippy effects when
it gets it wrong.

The same kind of thing could be done by storing a still image from the
camera before you step in front of it, and always comparing it with the
current live camera.
 
-- 
 
uname -rsvp
Linux 3.10.0-1160.15.2.el7.x86_64 #1 SMP Wed Feb 3 15:06:38 UTC 2021 x86_64
 
Boilerplate:  All unexpected mail to my mailbox is automatically deleted.
I will only get to see the messages that are posted to the mailing list.
 
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: Fedora 33 and HDMI KVM switch

[Paolo Galtieri]

What's interesting is when I plug the USB to HDMI dongle into my Fedora 
32 system a window pops up that allows me to install a driver for the 
dongle.  There are two options, one for the MAC and one for Windows.  
The Windows driver is dated 2017 the MAC driver is dated Jan 7 2020.  So 
a driver must exist for the dongle.  The dongle is a RayCue USB to HDMI.


Paolo

On 2/8/21 8:58 AM, D. Hugh Redelmeier wrote:

| From: Samuel Sieb 

| On 2/6/21 5:44 PM, Paolo Galtieri wrote:
| >  I'm having an issue running Fedora 33 and an external monitor connected to
| > an HDMI KVM switch.  Here is the way it's connected:
| >
| > Laptop thunderbolt 3 connector -> 4 port USB c to USB 3.0 hub -> USB to HDMI
| > adapter -> HDMI KVM switch.
|
| I don't think there are any USB3 video adapters that work with Linux.

The standards are quite confusing.

Among the USB standards, apparently USB4 (note the lack of space in the
name) is the first to (optionally) support HDMI.


On the other hand, a USB-c connector can support a whole bunch of
standards, only some of which are USB (!!!).


So: there is no way your setup would work.

You need to use a use a dongle to connect to your laptop port and output
HDMI.  Many of those dongles also break out USB 3 and ethernet.

I have a ThinkCentre Tiny that came with a USB-c to HDMI dongle.  It
works under Fedora 33 to drive an UltraHD TV.  I am having a problem with
the video, but surely it is unrelated to the dongle:
   

___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org


___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

[389-users] Re: Disable LDAPv2

[William Brown]

> On 10 Feb 2021, at 09:28, Mark Reynolds  wrote:
> 
> 
> On 2/8/21 6:45 PM, William Brown wrote:
>> 
>>> On 9 Feb 2021, at 08:39, Mark Reynolds  wrote:
>>> 
>>> 
>>> On 2/8/21 4:21 AM, Sahin, Erhan wrote:
 Hello everyone,
 
 is it possible to deactivate LDAPv2 completely on server side and only 
 allow LDAPv3?
>>> There is no way to do that at this time.  Just curious, what are your 
>>> reasons for wanting to deactivate it?
>> It's a reasonable point I guess, it's just more surface area that gets 
>> minimal testing. We should probably remove ldapv2 entirely TBH.
> 
> Apparently LDAP V2 was retried back in 2003 :-) 
> https://tools.ietf.org/html/rfc3494
> 
> If that's the case we could remove support for it (instead of adding a new 
> config setting).  We should open a ticket to investigate this...

https://github.com/389ds/389-ds-base/issues/4606




> 
> Mark
> 
>> 
>>> Mark
 Stay safe!
 
 Best regards
 
 
 ___
 389-users mailing list --
 389-users@lists.fedoraproject.org
 
 To unsubscribe send an email to
 389-users-le...@lists.fedoraproject.org
 
 Fedora Code of Conduct:
 https://docs.fedoraproject.org/en-US/project/code-of-conduct/
 
 List Guidelines:
 https://fedoraproject.org/wiki/Mailing_list_guidelines
 
 List Archives:
 https://lists.fedoraproject.org/archives/list/389-users@lists.fedoraproject.org
>>> -- 
>>> 
>>> 389 Directory Server Development Team
>>> 
>>> ___
>>> 389-users mailing list -- 389-users@lists.fedoraproject.org
>>> To unsubscribe send an email to 389-users-le...@lists.fedoraproject.org
>>> Fedora Code of Conduct: 
>>> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
>>> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
>>> List Archives: 
>>> https://lists.fedoraproject.org/archives/list/389-users@lists.fedoraproject.org
>> —
>> Sincerely,
>> 
>> William Brown
>> 
>> Senior Software Engineer, 389 Directory Server
>> SUSE Labs, Australia
>> ___
>> 389-users mailing list -- 389-users@lists.fedoraproject.org
>> To unsubscribe send an email to 389-users-le...@lists.fedoraproject.org
>> Fedora Code of Conduct: 
>> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
>> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
>> List Archives: 
>> https://lists.fedoraproject.org/archives/list/389-users@lists.fedoraproject.org
> 
> -- 
> 
> 389 Directory Server Development Team

—
Sincerely,

William Brown

Senior Software Engineer, 389 Directory Server
SUSE Labs, Australia
___
389-users mailing list -- 389-users@lists.fedoraproject.org
To unsubscribe send an email to 389-users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/389-users@lists.fedoraproject.org

[389-users] Re: Disable LDAPv2

[Mark Reynolds]

On 2/8/21 6:45 PM, William Brown wrote:



On 9 Feb 2021, at 08:39, Mark Reynolds  wrote:


On 2/8/21 4:21 AM, Sahin, Erhan wrote:

Hello everyone,

is it possible to deactivate LDAPv2 completely on server side and only allow 
LDAPv3?

There is no way to do that at this time.  Just curious, what are your reasons 
for wanting to deactivate it?

It's a reasonable point I guess, it's just more surface area that gets minimal 
testing. We should probably remove ldapv2 entirely TBH.


Apparently LDAP V2 was retried back in 2003 :-) 
https://tools.ietf.org/html/rfc3494


If that's the case we could remove support for it (instead of adding a 
new config setting).  We should open a ticket to investigate this...


Mark




Mark

Stay safe!

Best regards


___
389-users mailing list --
389-users@lists.fedoraproject.org

To unsubscribe send an email to
389-users-le...@lists.fedoraproject.org

Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/

List Guidelines:
https://fedoraproject.org/wiki/Mailing_list_guidelines

List Archives:
https://lists.fedoraproject.org/archives/list/389-users@lists.fedoraproject.org

--

389 Directory Server Development Team

___
389-users mailing list -- 389-users@lists.fedoraproject.org
To unsubscribe send an email to 389-users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/389-users@lists.fedoraproject.org

—
Sincerely,

William Brown

Senior Software Engineer, 389 Directory Server
SUSE Labs, Australia
___
389-users mailing list -- 389-users@lists.fedoraproject.org
To unsubscribe send an email to 389-users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/389-users@lists.fedoraproject.org


--

389 Directory Server Development Team
___
389-users mailing list -- 389-users@lists.fedoraproject.org
To unsubscribe send an email to 389-users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/389-users@lists.fedoraproject.org

Re: Networking issue in VMs

[Adam Mercer]

On Tue, Feb 9, 2021 at 4:38 AM Stephen Morris  wrote:

> I'm using Fedora 33 in a Vmware Player VM, and I haven't had any issues
> with networking failing. I have the Vmware network definition configured
> as NAT to share the hosts IP address (my Host is Windows 10), do you
> have you Vmware Workstation configured the same way? With this setup,
> irrespective of whether my host is using wifi or ethernet Fedora thinks
> it is using a wired connection. I'm also not migrating the network card
> into the VM I'm leaving it attached to the host system.

Thanks, that's exactly the same setup I have, I've also started
noticing weird network behaviour outside of the VM and on other
systems on my network and I'm starting to suspect a router issue.

Cheers

Adam
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: Can't reliably right click with mouse due to click interval... F33 Workstation, Plasma,

[linux guy]

On Sat, Feb 6, 2021 at 8:46 PM Tim via users 
wrote:

>
> I've had double-clicking problems with dicky mouse switches.  And
> although you can make adjustments for that, it's skirting around the
> real problem (bad mouse / bad mouse buttons).
>
>
I replaced the mouse.
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: Preventing display manager running on gpgpu

[Jonathan Billings]

On Tue, Feb 09, 2021 at 01:03:57PM -0500, Neal Becker wrote:
> Maybe not a bad idea.  Sometimes I might want a graphical interface on
> the built-in vga.

Well, if you want the graphical login, then you need to run a
graphical interface.  If you want to run it on a different card, set
up X11 to talk just to that video card.  Something like this if the
internal GPU is the Intel i915 (which I have in my servers).

Section "OutputClass"
Identifier "intel"
MatchDriver "i915"
Driver "modesetting"
Option "PrimaryGPU" "yes"
EndSection

-- 
Jonathan Billings 
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: Preventing display manager running on gpgpu

[Neal Becker]

Maybe not a bad idea.  Sometimes I might want a graphical interface on
the built-in vga.

On Tue, Feb 9, 2021 at 12:37 PM Jonathan Billings  wrote:
>
> On Tue, Feb 09, 2021 at 11:39:42AM -0500, Neal Becker wrote:
> > If I understand correctly, I will need the nvidia driver installed to
> > use the gpgpu for M/L.  I don't want/need to run a display on it
> > (wayland or X11).
>
> Why not set the default.target to multi-user.target instead of
> graphical.target?
>
> --
> Jonathan Billings 
> ___
> users mailing list -- users@lists.fedoraproject.org
> To unsubscribe send an email to users-le...@lists.fedoraproject.org
> Fedora Code of Conduct: 
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: 
> https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org



-- 
Those who don't understand recursion are doomed to repeat it
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: Preventing display manager running on gpgpu

[Jonathan Billings]

On Tue, Feb 09, 2021 at 11:39:42AM -0500, Neal Becker wrote:
> If I understand correctly, I will need the nvidia driver installed to
> use the gpgpu for M/L.  I don't want/need to run a display on it
> (wayland or X11).

Why not set the default.target to multi-user.target instead of
graphical.target? 

-- 
Jonathan Billings 
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: Preventing display manager running on gpgpu

[Neal Becker]

If I understand correctly, I will need the nvidia driver installed to
use the gpgpu for M/L.  I don't want/need to run a display on it
(wayland or X11).
Thanks,
Neal

On Tue, Feb 9, 2021 at 10:22 AM Patrick O'Callaghan
 wrote:
>
> On Tue, 2021-02-09 at 06:51 -0600, Richard Shaw wrote:
> > I'm not sure I have a 100% solution for you but you could start with
> > blacklisting the nouveau driver...
> >
> > /etc/default/grub:
> > GRUB_CMDLINE_LINUX=" rd.driver.blacklist=nouveau
> > modprobe.blacklist=nouveau"
> >
> > (assuming UEFI)
> > # grub2-mkconfig -o /boot/efi/EFI/fedora/grub.cfg
>
> Also blacklist the proprietary Nvidia driver if it's installed (or
> uninstall it of course).
>
> I was about to make the same suggestion since I do this myself in order
> to run GPU pass-through to a Windows VM guest, however the side-effect
> is that the GPU is no longer accessible from Linux, which may not be
> what the OP wanted.
>
> poc
> ___
> users mailing list -- users@lists.fedoraproject.org
> To unsubscribe send an email to users-le...@lists.fedoraproject.org
> Fedora Code of Conduct: 
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: 
> https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org



-- 
Those who don't understand recursion are doomed to repeat it
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: How to build rpm Krita from krita.spec ?

[Matthew Miller]

On Mon, Feb 08, 2021 at 07:37:28PM -, Cătălin George Feștilă wrote:
> Thanks to everyone for all the information. It is quite difficult to
> create packages from the source code for Fedora, I tried with this
> software. It seems that the Fedora team is keeping its distance in
> teaching users to create new packages.

Creating packages takes some skill, and particularly that skill builds on a
lot of other basic knowledge about building code in general. If you are
starting from scratch, yes, that's a daunting level of difficulty to dive
into.

As for keeping our distance — we certainly _want_ to help community members
learn skills, including packaging. We have a number of resources available
which I hope you've been able to find, starting from:

   https://docs.fedoraproject.org/en-US/quick-docs/creating-rpm-packages/

and 

   https://developer.fedoraproject.org/deployment/rpm/about.html

We've also run workshops on packaging, like

   https://www.youtube.com/watch?v=H4vxkuoimzc

and hope to be able to do in-person things like that again soon!




-- 
Matthew Miller

Fedora Project Leader
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: Preventing display manager running on gpgpu

[Patrick O'Callaghan]

On Tue, 2021-02-09 at 06:51 -0600, Richard Shaw wrote:
> I'm not sure I have a 100% solution for you but you could start with
> blacklisting the nouveau driver...
> 
> /etc/default/grub:
> GRUB_CMDLINE_LINUX=" rd.driver.blacklist=nouveau
> modprobe.blacklist=nouveau"
> 
> (assuming UEFI)
> # grub2-mkconfig -o /boot/efi/EFI/fedora/grub.cfg

Also blacklist the proprietary Nvidia driver if it's installed (or
uninstall it of course).

I was about to make the same suggestion since I do this myself in order
to run GPU pass-through to a Windows VM guest, however the side-effect
is that the GPU is no longer accessible from Linux, which may not be
what the OP wanted.

poc
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

[389-users] Re: Disable LDAPv2

[Sahin, Erhan]

Hello Mark,


from a security point of view it would be less attack surface and in my case, 
everything supports LDAPv3.


Best regards,


Erhan


Von: Mark Reynolds 
Gesendet: Montag, 8. Februar 2021 23:39:26
An: General discussion list for the 389 Directory server project.; Sahin, Erhan
Cc: Both, Leif
Betreff: Re: [389-users] Disable LDAPv2

EXTERNAL SENDER: Do not click any links or open any attachments unless you 
trust the sender and know the content is safe.
EXPÉDITEUR EXTERNE: Ne cliquez sur aucun lien et n’ouvrez aucune pièce jointe à 
moins qu’ils ne proviennent d’un expéditeur fiable, ou que vous ayez 
l'assurance que le contenu provient d'une source sûre.



On 2/8/21 4:21 AM, Sahin, Erhan wrote:

Hello everyone,


is it possible to deactivate LDAPv2 completely on server side and only allow 
LDAPv3?

There is no way to do that at this time.  Just curious, what are your reasons 
for wanting to deactivate it?


Mark


Stay safe!


Best regards



___
389-users mailing list -- 
389-users@lists.fedoraproject.org
To unsubscribe send an email to 
389-users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: 
https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/389-users@lists.fedoraproject.org


--

389 Directory Server Development Team
___
389-users mailing list -- 389-users@lists.fedoraproject.org
To unsubscribe send an email to 389-users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/389-users@lists.fedoraproject.org

Re: Preventing display manager running on gpgpu

[Richard Shaw]

I'm not sure I have a 100% solution for you but you could start with
blacklisting the nouveau driver...

/etc/default/grub:
GRUB_CMDLINE_LINUX=" rd.driver.blacklist=nouveau
modprobe.blacklist=nouveau"

(assuming UEFI)
# grub2-mkconfig -o /boot/efi/EFI/fedora/grub.cfg

HTH!

Richard
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Preventing display manager running on gpgpu

[Neal Becker]

After re-installing f33 following a disk crash, I was having problems
that I believe were caused by nouveau trying to run on my gpgpu nvidia
2080 ti.  I don't need or want a display manager running on it.  How
can I tell if wayland and/or X is configured to run on that card, and
how can I disable it for that card?  I also have a built-in vga that
runs a display.

Thanks,
Neal
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: Plasma on Xorg Fails to Start After Last System Update

[Ed Greshko]

On Tue, Feb 9, 2021, 19:50 Stephen Morris  wrote:

>
> Sorry, I meant gdm now runs, but plasma still fails under gdm.
> How do I access the KDE list?
>

kde mailing list -- k...@lists.fedoraproject.org
To unsubscribe send an email to kde-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/k...@lists.fedoraproject.or
g
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: Virtual background for Zoom video

[Paul Smith]

On Tue, Feb 9, 2021 at 11:44 AM Stephen Morris  wrote:
>
> >>> I would like to replace the background behind in my webcam video feed
> >>> with an image. However, that is not possible, as it requires a “green
> >>> screen”, which I do not have. So, my idea is to use a virtual camera
> >>> with a background image chosen by me and feed that into Zoom. Is that
> >>> possible on Fedora?
> >> You can use the v4l2loopback kernel module to create a virtual camera,
> >> and use one of the many tools to send video to the virtual video
> >> device.  However, that will just send a video or image to the video
> >> device, it won't get your webcam's picture and overlay it on top of
> >> it.  If you want that, you'll need to do what zoom is already trying
> >> to do, which requires a static background (a green screen).
> > Thanks, Jonathan, for your clarification. I am now thinking about an
> > alternative: blurring the background. Skype can do that, but not Zoom
> > -- unfortunately.
> Just one question, what do you mean by green screen? I use zoom on my
> work laptop in Windows 10 showing static and animated backgrounds behind
> the camera image so that people can't see anything in the room behind
> me, and I didn't think there was anything special in my zoom configuration.

A picture is worth a thousand words, Steve:

https://gadgetstouse.com/wp-content/uploads/2020/09/Green-Screen.jpg

Paul
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: Plasma on Xorg Fails to Start After Last System Update

[Stephen Morris]

On 9/2/21 22:40, Ed Greshko wrote:

On 09/02/2021 19:14, Stephen Morris wrote:

On 3/2/21 19:08, Ed Greshko wrote:

On 03/02/2021 14:09, Stephen Morris wrote:

For me systemctl status gdm gives:
gdm.service - GNOME Display Manager
 Loaded: loaded (/usr/lib/systemd/system/gdm.service; 
enabled; vendor preset: enabled)
 Active: active (running) since Wed 2021-02-03 13:37:47 
AEDT; 3h 27min ago

   Main PID: 1221 (gdm)
  Tasks: 3 (limit: 19120)
 Memory: 5.5M
CPU: 280ms
 CGroup: /system.slice/gdm.service
 └─1221 /usr/sbin/gdm

Feb 03 13:37:46 localhost.localdomain systemd[1]: Starting GNOME 
Display Manager...
Feb 03 13:37:47 localhost.localdomain systemd[1]: Started GNOME 
Display Manager.
Feb 03 13:38:34 localhost.localdomain gdm-password][1837]: gkr-pam: 
unable to locate daemon control file
Feb 03 13:38:34 localhost.localdomain gdm-password][1837]: gkr-pam: 
stashed password to try later in open session
Feb 03 13:38:54 localhost.localdomain gdm[1221]: Gdm: Child process 
-1267 was already dead.


What I'm not sure at the moment is how to find out what process -1267 is. 



The bugzillas referenced so far have been against sddm.  Your 
issues seem unrelated.


There have been fixes to sddm to address those issues.  You may 
wish to try sddm instead of gdm to
see if you still have issues.  The most current sddm is still in 
updates-testing. So, if you wan to give

it a try

dnf --enablerepo updates-testing update sddm
systemctl --now enable sddm

The reboot
Hi Ed, I issued the two commands and first one worked but the second 
one didn't. The second command said it couldn't create the 
display-manager symlink because it already existed and was linked to 
gdm.service.


Ooops  Sorry about that.  I forgot to add the -f or --force 
parameter


I then made the mistake of issuing the command systemctl disable gdm 
and that blew Fedora out of the water. I rebooted but the display 
manager wouldn't start.
I then used ctrl+alt+F2 to get a login prompt, logged in, and issued 
the command systemctl disable display-manager and then systemctl 
enable sddm and rebooted, but sddm would not start. I logged back in 
again at a login prompt and issued the command systemctl status 
display-manager and it said sddm was active but sddm-helper failed 
with exit-11.


That think that was one of the errors noted in one of the BZ's. Can't 
find it at the moment.


What version of sddm is now installed?

rpm -q sddm

sddm-0.19.0-6.fc33 is the latest.



I've checked the version of sddm and it is sddm-0.19.0-6.fc33.x86_64.

Hence at the moment I have switched back to gdm which runs fine.



So, you can run the KDE desktop using gdm as the display-manager? If 
that works, I suppose you can stay
with it.  Or, maybe bring up your issue on the KDE list would be a 
good idea.

Sorry, I meant gdm now runs, but plasma still fails under gdm.
How do I access the KDE list?

regards,
Steve






___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: Virtual background for Zoom video

[Stephen Morris]

On 5/2/21 06:37, Paul Smith wrote:

On Thu, Feb 4, 2021 at 7:16 PM Jonathan Billings  wrote:

I would like to replace the background behind in my webcam video feed
with an image. However, that is not possible, as it requires a “green
screen”, which I do not have. So, my idea is to use a virtual camera
with a background image chosen by me and feed that into Zoom. Is that
possible on Fedora?

You can use the v4l2loopback kernel module to create a virtual camera,
and use one of the many tools to send video to the virtual video
device.  However, that will just send a video or image to the video
device, it won't get your webcam's picture and overlay it on top of
it.  If you want that, you'll need to do what zoom is already trying
to do, which requires a static background (a green screen).

Thanks, Jonathan, for your clarification. I am now thinking about an
alternative: blurring the background. Skype can do that, but not Zoom
-- unfortunately.
Just one question, what do you mean by green screen? I use zoom on my 
work laptop in Windows 10 showing static and animated backgrounds behind 
the camera image so that people can't see anything in the room behind 
me, and I didn't think there was anything special in my zoom configuration.


regards,
Steve



Paul
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: Plasma on Xorg Fails to Start After Last System Update

[Ed Greshko]

On 09/02/2021 19:14, Stephen Morris wrote:

On 3/2/21 19:08, Ed Greshko wrote:

On 03/02/2021 14:09, Stephen Morris wrote:

For me systemctl status gdm gives:
gdm.service - GNOME Display Manager
 Loaded: loaded (/usr/lib/systemd/system/gdm.service; enabled; vendor 
preset: enabled)
 Active: active (running) since Wed 2021-02-03 13:37:47 AEDT; 3h 27min ago
   Main PID: 1221 (gdm)
  Tasks: 3 (limit: 19120)
 Memory: 5.5M
CPU: 280ms
 CGroup: /system.slice/gdm.service
 └─1221 /usr/sbin/gdm

Feb 03 13:37:46 localhost.localdomain systemd[1]: Starting GNOME Display 
Manager...
Feb 03 13:37:47 localhost.localdomain systemd[1]: Started GNOME Display Manager.
Feb 03 13:38:34 localhost.localdomain gdm-password][1837]: gkr-pam: unable to 
locate daemon control file
Feb 03 13:38:34 localhost.localdomain gdm-password][1837]: gkr-pam: stashed 
password to try later in open session
Feb 03 13:38:54 localhost.localdomain gdm[1221]: Gdm: Child process -1267 was 
already dead.

What I'm not sure at the moment is how to find out what process -1267 is.


The bugzillas referenced so far have been against sddm.  Your issues seem 
unrelated.

There have been fixes to sddm to address those issues.  You may wish to try 
sddm instead of gdm to
see if you still have issues.  The most current sddm is still in 
updates-testing. So, if you wan to give
it a try

dnf --enablerepo updates-testing update sddm
systemctl --now enable sddm

The reboot

Hi Ed, I issued the two commands and first one worked but the second one 
didn't. The second command said it couldn't create the display-manager symlink 
because it already existed and was linked to gdm.service.


Ooops  Sorry about that.  I forgot to add the -f or --force parameter


I then made the mistake of issuing the command systemctl disable gdm and that 
blew Fedora out of the water. I rebooted but the display manager wouldn't start.
I then used ctrl+alt+F2 to get a login prompt, logged in, and issued the 
command systemctl disable display-manager and then systemctl enable sddm and 
rebooted, but sddm would not start. I logged back in again at a login prompt 
and issued the command systemctl status display-manager and it said sddm was 
active but sddm-helper failed with exit-11.


That think that was one of the errors noted in one of the BZ's. Can't find it 
at the moment.

What version of sddm is now installed?

rpm -q sddm

sddm-0.19.0-6.fc33 is the latest.



Hence at the moment I have switched back to gdm which runs fine.



So, you can run the KDE desktop using gdm as the display-manager? If that 
works, I suppose you can stay
with it.  Or, maybe bring up your issue on the KDE list would be a good idea.



--
The key to getting good answers is to ask good questions.

___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: Networking issue in VMs

[Stephen Morris]

On 9/2/21 14:28, Adam Mercer wrote:

Hi

I've started having a strange problem the last couple of days with my
VMs, I use both VMWare Workstation and VirtualBox on my Fedora 33
system and recently the network connectivity inside my VMs stopped
working after some point.

I installed an Ubuntu VM, in VMWare. and was using it for several days
without issue and then yesterday I booted up the VM and I could not
access the outside work from within my VM. As far as the VM was
concerned everything seemed fine, it had an IP address in the expected
range there was just no connectivity. I needed to do some work in a
Debian based machine so just quickly stood up a new VM, this time
Debian Buster. As before it worked fine. However this morning I booted
up the VM and encountered the same problem. With this VM I had created
a snapshot shortly after standing it up when i knew it was working, so
I reverted the machine to the snapshot and again I had no connectivity
within the VM.

I then tried VirtualBox, I stood up a Debian Buster VM and booted into
it, it worked fine. At some point later network operations stopped
working like with VMWare.

Any idea what could cause networking to stop working within my VMs?
I'm using Fedora 33 in a Vmware Player VM, and I haven't had any issues 
with networking failing. I have the Vmware network definition configured 
as NAT to share the hosts IP address (my Host is Windows 10), do you 
have you Vmware Workstation configured the same way? With this setup, 
irrespective of whether my host is using wifi or ethernet Fedora thinks 
it is using a wired connection. I'm also not migrating the network card 
into the VM I'm leaving it attached to the host system.


regards,
Steve



Cheers

Adam
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: Plasma on Xorg Fails to Start After Last System Update

[Stephen Morris]

On 9/2/21 22:14, Stephen Morris wrote:

On 3/2/21 19:08, Ed Greshko wrote:

On 03/02/2021 14:09, Stephen Morris wrote:

For me systemctl status gdm gives:
gdm.service - GNOME Display Manager
 Loaded: loaded (/usr/lib/systemd/system/gdm.service; 
enabled; vendor preset: enabled)
 Active: active (running) since Wed 2021-02-03 13:37:47 
AEDT; 3h 27min ago

   Main PID: 1221 (gdm)
  Tasks: 3 (limit: 19120)
 Memory: 5.5M
CPU: 280ms
 CGroup: /system.slice/gdm.service
 └─1221 /usr/sbin/gdm

Feb 03 13:37:46 localhost.localdomain systemd[1]: Starting GNOME 
Display Manager...
Feb 03 13:37:47 localhost.localdomain systemd[1]: Started GNOME 
Display Manager.
Feb 03 13:38:34 localhost.localdomain gdm-password][1837]: gkr-pam: 
unable to locate daemon control file
Feb 03 13:38:34 localhost.localdomain gdm-password][1837]: gkr-pam: 
stashed password to try later in open session
Feb 03 13:38:54 localhost.localdomain gdm[1221]: Gdm: Child process 
-1267 was already dead.


What I'm not sure at the moment is how to find out what process -1267 is. 



The bugzillas referenced so far have been against sddm.  Your issues 
seem unrelated.


There have been fixes to sddm to address those issues.  You may wish 
to try sddm instead of gdm to
see if you still have issues.  The most current sddm is still in 
updates-testing. So, if you wan to give

it a try

dnf --enablerepo updates-testing update sddm
systemctl --now enable sddm

The reboot
Hi Ed, I issued the two commands and first one worked but the second 
one didn't. The second command said it couldn't create the 
display-manager symlink because it already existed and was linked to 
gdm.service.
I then made the mistake of issuing the command systemctl disable gdm 
and that blew Fedora out of the water. I rebooted but the display 
manager wouldn't start.
I then used ctrl+alt+F2 to get a login prompt, logged in, and issued 
the command systemctl disable display-manager and then systemctl 
enable sddm and rebooted, but sddm would not start. I logged back in 
again at a login prompt and issued the command systemctl status 
display-manager and it said sddm was active but sddm-helper failed 
with exit-11.

Hence at the moment I have switched back to gdm which runs fine.
I installed kdm to try that and the starting of plasma through kdm gets 
the same failures as it does when started through gdm.


regards,
Steve



regards,
Steve





___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/

List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: Plasma on Xorg Fails to Start After Last System Update

[Stephen Morris]

On 3/2/21 19:08, Ed Greshko wrote:

On 03/02/2021 14:09, Stephen Morris wrote:

For me systemctl status gdm gives:
gdm.service - GNOME Display Manager
 Loaded: loaded (/usr/lib/systemd/system/gdm.service; 
enabled; vendor preset: enabled)
 Active: active (running) since Wed 2021-02-03 13:37:47 AEDT; 
3h 27min ago

   Main PID: 1221 (gdm)
  Tasks: 3 (limit: 19120)
 Memory: 5.5M
CPU: 280ms
 CGroup: /system.slice/gdm.service
 └─1221 /usr/sbin/gdm

Feb 03 13:37:46 localhost.localdomain systemd[1]: Starting GNOME 
Display Manager...
Feb 03 13:37:47 localhost.localdomain systemd[1]: Started GNOME 
Display Manager.
Feb 03 13:38:34 localhost.localdomain gdm-password][1837]: gkr-pam: 
unable to locate daemon control file
Feb 03 13:38:34 localhost.localdomain gdm-password][1837]: gkr-pam: 
stashed password to try later in open session
Feb 03 13:38:54 localhost.localdomain gdm[1221]: Gdm: Child process 
-1267 was already dead.


What I'm not sure at the moment is how to find out what process -1267 is. 



The bugzillas referenced so far have been against sddm.  Your issues 
seem unrelated.


There have been fixes to sddm to address those issues.  You may wish 
to try sddm instead of gdm to
see if you still have issues.  The most current sddm is still in 
updates-testing. So, if you wan to give

it a try

dnf --enablerepo updates-testing update sddm
systemctl --now enable sddm

The reboot
Hi Ed, I issued the two commands and first one worked but the second one 
didn't. The second command said it couldn't create the display-manager 
symlink because it already existed and was linked to gdm.service.
I then made the mistake of issuing the command systemctl disable gdm and 
that blew Fedora out of the water. I rebooted but the display manager 
wouldn't start.
I then used ctrl+alt+F2 to get a login prompt, logged in, and issued the 
command systemctl disable display-manager and then systemctl enable sddm 
and rebooted, but sddm would not start. I logged back in again at a 
login prompt and issued the command systemctl status display-manager and 
it said sddm was active but sddm-helper failed with exit-11.

Hence at the moment I have switched back to gdm which runs fine.

regards,
Steve





___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: Plasma on Xorg Fails to Start After Last System Update

[Stephen Morris]

On 3/2/21 19:08, Ed Greshko wrote:

On 03/02/2021 14:09, Stephen Morris wrote:

For me systemctl status gdm gives:
gdm.service - GNOME Display Manager
 Loaded: loaded (/usr/lib/systemd/system/gdm.service; 
enabled; vendor preset: enabled)
 Active: active (running) since Wed 2021-02-03 13:37:47 AEDT; 
3h 27min ago

   Main PID: 1221 (gdm)
  Tasks: 3 (limit: 19120)
 Memory: 5.5M
CPU: 280ms
 CGroup: /system.slice/gdm.service
 └─1221 /usr/sbin/gdm

Feb 03 13:37:46 localhost.localdomain systemd[1]: Starting GNOME 
Display Manager...
Feb 03 13:37:47 localhost.localdomain systemd[1]: Started GNOME 
Display Manager.
Feb 03 13:38:34 localhost.localdomain gdm-password][1837]: gkr-pam: 
unable to locate daemon control file
Feb 03 13:38:34 localhost.localdomain gdm-password][1837]: gkr-pam: 
stashed password to try later in open session
Feb 03 13:38:54 localhost.localdomain gdm[1221]: Gdm: Child process 
-1267 was already dead.


What I'm not sure at the moment is how to find out what process -1267 is. 



The bugzillas referenced so far have been against sddm.  Your issues 
seem unrelated.


There have been fixes to sddm to address those issues.  You may wish 
to try sddm instead of gdm to
see if you still have issues.  The most current sddm is still in 
updates-testing. So, if you wan to give

it a try

dnf --enablerepo updates-testing update sddm
systemctl --now enable sddm

The reboot

Thanks Ed, I might try that. I don't like the sddm interface, but if it 
means plasma works properly then I might have to put up with it. I don't 
like the Gnome desktop interface, in my view it doesn't work properly.


regards,
Steve

___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: Tip: programs that over write links

[Patrick O'Callaghan]

On Mon, 2021-02-08 at 16:19 -0800, ToddAndMargo via users wrote:
> On 2/8/21 4:16 PM, Ed Greshko wrote:
> > On 09/02/2021 08:08, ToddAndMargo via users wrote:
> > > I was reporting a bug over there.  I was only
> > > giving a tip over here.
> > > 
> > > "Two programs that will over write your links with
> > > the actual file" is as clear as it gets!
> > 
> > Well, then why did poc write:
> > 
> > "By links do you mean URLs, hard links, symlinks, something else? By
> > "over write" do you mean replace? What is the context of this?"
> > 
> > Tips are only useful if fully explained.  Being vague isn't an attribute.
> 
> I am surprised he did not pick it up from context.

Because the context was insufficient. When posting about an issue (or
giving a tip) it's important to put yourself in the position of someone
who isn't immersed in your specific problem.

> And using 1000 words where 2 will do is also not
> an attribute.

And now several hundred words have been used to clear up the confusion
when a bit more clarity from the start would have been enough.

poc
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org