On Thu, 2021-02-04 at 19:09 +, Paul Smith 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
On Thu, 4 Feb 2021 19:34:01 -0700
linux guy wrote:
> It worked fine up until I rebooted with a new kernel this afternoon.
Hardware is well known to wait for a software upgrade to break
in order to maximize confusion :-).
___
users mailing list --
On Thu, Feb 4, 2021 at 7:28 PM Tom Horsley wrote:
>
> That sounds a lot like the same hardware failure I have on my
> old P8H67-V (AUSTek) system. I just tested it again, and the USB3
> ports will work with a single simple device plugged in (like a
> USB keyboard, which is what I tried), but a
> On 5 Feb 2021, at 12:30, William Brown wrote:
>
>
>
>> On 4 Feb 2021, at 22:23, Pierre Rogier wrote:
>>
>> Hi Nicolas,
>>
>> The documentation does not say that wildcard is supported in groupdn
>> evaluation and I have not seen anything in the code that handles it.
>> IMHO The comment
> On 4 Feb 2021, at 22:23, Pierre Rogier wrote:
>
> Hi Nicolas,
>
> The documentation does not say that wildcard is supported in groupdn
> evaluation and I have not seen anything in the code that handles it.
> IMHO The comment about group dn filter is a bit confusing:
> the only place it is
On Thu, Feb 4, 2021 at 7:16 PM Samuel Sieb wrote:
> On 2/4/21 5:28 PM, linux guy wrote:
> >
> > Have you tried booting an earlier kernel?
> >
> >
> > Yes. The behavior was consistent across the 3 kernels I had installed.
> > uname -a
> > Linux bigboy 5.10.11-200.fc33.x86_64 #1 SMP Wed Jan
On Thu, 4 Feb 2021 18:56:27 -0700
linux guy wrote:
> I have a USB2 hub attached to my computer. It was connected to a USB3
> port. I moved it to a USB2 port and how all my USB devices work. None of
> them are connected to a USB3 port.
That sounds a lot like the same hardware failure I have
On 2/4/21 5:28 PM, linux guy wrote:
Have you tried booting an earlier kernel?
Yes. The behavior was consistent across the 3 kernels I had installed.
uname -a
Linux bigboy 5.10.11-200.fc33.x86_64 #1 SMP Wed Jan 27 20:21:22 UTC 2021
x86_64 x86_64 x86_64 GNU/Linux
If it's not working now
I have a USB2 hub attached to my computer. It was connected to a USB3
port. I moved it to a USB2 port and how all my USB devices work. None of
them are connected to a USB3 port.
$ lsusb
Bus 006 Device 004: ID 0951:1666 Kingston Technology DataTraveler 100
G3/G4/SE9 G2/50
Bus 006 Device 003:
> > I can't ssh into it. Connection refused. Looks like I closed port 22,
> > which is what I normally do.
>
> Workstation defaults to having ssh disabled.
>
I set ssh up on all my machines for various reasons. I keep the port
closed when I am not using it, as I had it today.
> Do you happen to have usbguard activated?
>
No I did not.
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct:
> did you check to ensure that any extension USB cable being used is rated
> for USB3?
>
A USB2 device was plugged directly into a USB3 port. It worked during boot
to edit the kernel boot line in the grub editor, but not after booting.
___
users
> Have you tried booting an earlier kernel?
>
Yes. The behavior was consistent across the 3 kernels I had installed.
uname -a
Linux bigboy 5.10.11-200.fc33.x86_64 #1 SMP Wed Jan 27 20:21:22 UTC 2021
x86_64 x86_64 x86_64 GNU/Linux
___
users mailing list
Do you happen to have usbguard activated?
If that is the case, you may need to grant the access all the
keyboards and mices you may need to plugin.
On Fri, Feb 5, 2021 at 8:33 AM Samuel Sieb wrote:
>
> On 2/4/21 12:58 PM, linux guy wrote:
> > I can ping the computer and it responds.
> >
> > I
> On 4 Feb 2021, at 19:52, ADELIN Arnaud wrote:
>
> Thank you for your quick reply.
>
> * You ran the wget on the CRL from on the LDAP server itself and confirmed it.
> Yes
>
> * Did you wget every CRL for the entire CA chain?
> In my setup, there is only one CRL url that is set in the LDAP
On 2/4/21 12:58 PM, linux guy wrote:
I can ping the computer and it responds.
I can't ssh into it. Connection refused. Looks like I closed port 22,
which is what I normally do.
Workstation defaults to having ssh disabled.
___
users mailing list
did you check to ensure that any extension USB cable being used is rated
for USB3?
On Thu, Feb 4, 2021 at 2:18 PM linux guy wrote:
> The only working USB devices on this computer are the wired USB keyboard
> and the wired USB mouse. Not sure which they are in the tree above, I
> don't want to
On 2/4/21 12:44 PM, linux guy wrote:
I just did an update to my F33 Workstation install and now I can log
in. I can't move the mouse pointer on the login screen. The keyboard
doesn't appear to work either. Both are USB devices.
Have you tried booting an earlier kernel?
The only working USB devices on this computer are the wired USB keyboard
and the wired USB mouse. Not sure which they are in the tree above, I
don't want to unplug anything at the moment as I'm getting work done.
___
users mailing list --
Ask and you shall receive.
$ lsusb -t
/: Bus 06.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 1M
/: Bus 05.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 480M
|__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid,
1.5M
|__ Port 2: Dev 3, If 0, Class=Human
On 2/4/21 2:00 PM, linux guy wrote:
One other symptom: the power lights on my USB wired keyboard did not
light up when I was plugging it into the USB3 ports. They now light
up when plugged into the USB2 port.
lsusb -t shows physical usb device hierarchy as a tree. this may
help to
One other symptom: the power lights on my USB wired keyboard did not light
up when I was plugging it into the USB3 ports. They now light up when
plugged into the USB2 port.
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an
> my initial thought was probably slow keys were enabled.
>
> https://forum.kde.org/viewtopic.php?f=66=36625
>
Slowkeys is not enabled. This is NOT keyboard specific. It is affecting a
USB hub, flash drive and USB IDE hard drive.
This issue seems to affect all devices connected
On 2/4/21 1:41 PM, linux guy wrote:
This is not a hardware issue. Something changes in the software
during the boot process.
my initial thought was probably slow keys were enabled.
https://forum.kde.org/viewtopic.php?f=66=36625
___
The USB hard drive that is on the other USB bus does not connect to my
computer. Nor does anything else connected to that bus. But a keyboard
connected to that bus works during boot up.
$ lsusb
Bus 006 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 005 Device 003: ID 04f2:0402
> On 2/4/21 1:30 PM, linux guy wrote:
> > I am now logged into my plasma session using a wired keyboard and a
> > wired mouse, using USB ports that were not previously used.
>
> sounds more of a usb port or bus issue.
>
The keyboard and USB port worked fine during boot up. I was able to
On 2/4/21 1:30 PM, linux guy wrote:
I am now logged into my plasma session using a wired keyboard and a
wired mouse, using USB ports that were not previously used.
sounds more of a usb port or bus issue.
___
users mailing list --
I am now logged into my plasma session using a wired keyboard and a wired
mouse, using USB ports that were not previously used.
I am available to troubleshoot anything the community wants. Fire away
with your questions.
___
users mailing list --
I'm logged into the console session. I am going to reboot to plasma, to
see what happens.
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct:
> > It points to
> > a local configuration change to me.
>
> I do remember seeing USB related BIOS settings on systems, maybe
> one of them got changed somehow.
>
No changes, hardware or BIOS, have been made to the computer. Uptime was
days to a week, can't remember the last time I rebooted.
> Maybe the USB hardware is dead. I have an old computer where none of
> the USB ports work (and the onboard video also doesn't work, I think
> perhaps they are on the same dead chipset).
>
The keyboard works fine during early boot. I can edit in the grub editor
just fine.
My *guess* is that
On Thu, 4 Feb 2021 16:15:39 -0500
Jonathan Billings wrote:
> It points to
> a local configuration change to me.
I do remember seeing USB related BIOS settings on systems, maybe
one of them got changed somehow.
___
users mailing list --
I got the wired USB keyboard working by plugging it straight into a USB2
port. Standby for more testing.
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct:
On Thu, 4 Feb 2021 14:13:15 -0700
linux guy wrote:
> I updated and rebooted my system in the first place because a USB hard
> drive I was using wasn't responding.
Maybe the USB hardware is dead. I have an old computer where none of
the USB ports work (and the onboard video also doesn't work, I
> That sounds like your USB bus might be having problems.
>
I agree, that is what it looks like. The physical USB bus seems to be
fine as the keyboard works in the grub editor. This appears to be a USB
bus software issue.
> Have you tried the keyboard in every USB port on your system?
>
I
On Thu, Feb 04, 2021 at 02:13:15PM -0700, linux guy wrote:
>
> I updated and rebooted my system in the first place because a USB hard
> drive I was using wasn't responding.
That sounds like your USB bus might be having problems.
Have you tried the keyboard in every USB port on your system?
--
On 2/4/21 12:44 PM, linux guy wrote:
I just did an update to my F33 Workstation install and now I can log
in. I can't move the mouse pointer on the login screen. The
keyboard doesn't appear to work either. Both are USB devices.
My login manager is GDM. I'm running Plasma as my desktop
On Thu, Feb 04, 2021 at 02:06:59PM -0700, linux guy wrote:
>
> I was able to edit the kernel boot line in the grub editor.
> My system booted to a system login prompt.
> My keyboard does not work. I cannot type a user name to log in.
So, since it seems to be OK during GRUB but not once the
My motherboard (Asus TUF Wifi X570) has a PS/2 connector on it. But I do
not have a PS/2 keyboard ! I used to... but I think it is long gone. I'll
check.
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to
I updated and rebooted my system in the first place because a USB hard
drive I was using wasn't responding.
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of
Sorry for top posting.
___
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:
I was able to edit the kernel boot line in the grub editor.
My system booted to a system login prompt.
My keyboard does not work. I cannot type a user name to log in.
On Thu, Feb 4, 2021 at 2:01 PM linux guy wrote:
>
> So the GRUB screen responds to key-presses, just not the fully booted
>>
>
> So the GRUB screen responds to key-presses, just not the fully booted
>
That is correct.
OS? Can you tell it to boot into text mode (adding
> systemd.unit=multi-user.target to the kernel line)?
I can.
Does the keyboard
> work then?
>
Standby wile I test that.
I can ping the computer and it responds.
I can't ssh into it. Connection refused. Looks like I closed port 22,
which is what I normally do.
Ideas ?
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to
On Thu, Feb 04, 2021 at 01:53:59PM -0700, linux guy wrote:
> I've done all those things. I also tried booting with every kernel that is
> installed on my computer.
So the GRUB screen responds to key-presses, just not the fully booted
OS? Can you tell it to boot into text mode (adding
On Thu, Feb 4, 2021 at 1:51 PM Tom Horsley wrote:
> On Thu, 4 Feb 2021 13:44:00 -0700
> linux guy wrote:
>
> > How do I resolve this ?
>
> First thing to try is unplugging and plugging back in the USB
> devices (or dongles if they are wireless).
>
> If that doesn't work, try plugging them into a
On Thu, 4 Feb 2021 13:44:00 -0700
linux guy wrote:
> How do I resolve this ?
First thing to try is unplugging and plugging back in the USB
devices (or dongles if they are wireless).
If that doesn't work, try plugging them into a different
USB port.
If that doesn't work, I guess power cycling
I just did an update to my F33 Workstation install and now I can log in. I
can't move the mouse pointer on the login screen. The keyboard doesn't
appear to work either. Both are USB devices.
My login manager is GDM. I'm running Plasma as my desktop manager.
I don't think I have ssh enabled
On 2/4/21 11:09 AM, Paul Smith 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
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
On Thu, Feb 04, 2021 at 07:09:03PM +, Paul Smith 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
Dear All,
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
Hi Nicolas,
The documentation does not say that wildcard is supported in groupdn
evaluation and I have not seen anything in the code that handles it.
IMHO The comment about group dn filter is a bit confusing:
the only place it is supported while evaluating groupdn is within the
(filter) part when
Hi Ludwig,
Thanks for your reply.
To clarify, when I say it's not working, it means that members of the
groups are not able to search the "cn=proxy" container's entries.
For example, I've set the following ACI on "cn=proxy":
(targetattr = "*") (target =
>
> On 2/4/21 12:25 AM, Patrick Dupre wrote:
> > It finally works with fedora32 by removing the lib/libcrypto libraries
>
>
> don't think its recommended removing those libraries. doing that may
> affect the program's functionality or cause other programs to misbehave.
I must have said
On 2/4/21 12:25 AM, Patrick Dupre wrote:
It finally works with fedora32 by removing the lib/libcrypto libraries
don't think its recommended removing those libraries. doing that may
affect the program's functionality or cause other programs to misbehave.
Thank you for your quick reply.
* You ran the wget on the CRL from on the LDAP server itself and confirmed it.
Yes
* Did you wget every CRL for the entire CA chain?
In my setup, there is only one CRL url that is set in the LDAP server
certificate.
This CRL is available thanks to wget.
For the
>
> On 2/2/21 9:05 AM, Patrick Dupre wrote:
> > To run XnView,
> > here is what it is recommended:
> >
> > you need to remove lib/libcrypto* from package
> > https://newsgroup.xnview.com/viewtopic.php?p=165437#p165437
> >
> > What do you think ?
> > libcrypto*
> > belong to openssl-libs
> >
> >
58 matches
Mail list logo
