Thanks to all who have tried to help me.
Let me report the results of all experiments I have done up to now:
1. Tried with all kernels installed on my machine, but with no success;
2. Tried with GNOME instead of XFCE, but again with no success;
3. Tried the web camera plugged in another USB port, and all works fine;
4. Tried to use the "problematic" USB port for backuping on an
external disk, and all worked fine.
I believe that I had not run into the reported problem because only
recently I began to use the "problematic" USB port for connecting the
web camera.
It is probable that Roger is right!
Paul
On Mon, Oct 12, 2020 at 10:32 PM Roger Heflin <rogerheflin@xxxxxxxxx> wrote:
>
> Try disabling the mtp-probe udev, that has been causing others usb
> devices to act up.
>
> The mtp-probe rule is badly written, it has an explicit list of
> devices that are mtp-devices, but even if something is not in that
> list it still tries to probe certain devices and those devices do not
> support whatever is being used in the problem the device acts up
> and/or goes offline. And when it comes back online it gets probed
> again...
>
> in /etc/udev/rules.d this is the change I made:
> [root@roger2016-laptop rules.d]# diff 69-libmtp.rules /root/69-libmtp.rules
> 2537c2537
> < ENV{ID_MTP_DEVICE}!="1", ENV{MTP_NO_PROBE}!="1",
> ENV{COLOR_MEASUREMENT_DEVICE}!="1", ENV{libsane_matched}!="yes",
> ATTR{bDeviceClass}=="00|02|06|ef|ff", PROGRAM="/usr/lib/udev/mtp-probe
> /sys$env{DEVPATH} $attr{busnum} $attr{devnum}", RESULT=="1",
> SYMLINK+="libmtp-%k", ENV{ID_MTP_DEVICE}="1", ENV{ID_MEDIA_PLAYER}="1"
> ---
> > ENV{ID_MTP_DEVICE}!="1", ENV{MTP_NO_PROBE}=="1|0", ENV{COLOR_MEASUREMENT_DEVICE}!="1", ENV{libsane_matched}!="yes", ATTR{bDeviceClass}=="00|02|06|ef|ff", PROGRAM="/usr/lib/udev/mtp-probe /sys$env{DEVPATH} $attr{busnum} $attr{devnum}", RESULT=="1", SYMLINK+="libmtp-%k", ENV{ID_MTP_DEVICE}="1", ENV{ID_MEDIA_PLAYER}="1"
>
> Save the change, if an update updates this file then the change will
> need to be redone.
>
> My mouse ws a bDeviceClass of 00 so it was being probed and the
> problem was causing random disconnnects.
>
> Others on the last have had other devices broken.
>
> And the log file does say mtp-probe is being ran against it, likely
> sending it some commands that given device does not support so locks
> up.
>
> On Mon, Oct 12, 2020 at 1:44 PM ITwrx <info@xxxxxxxxx> wrote:
> >
> > On 10/12/20 1:40 PM, Samuel Sieb wrote:
> > > That's not the kernel causing the disconnect. This is a message from
> > > the kernel saying that the device disconnected and then reconnected.
> >
> > Right. Like when the cable is going bad, or the device itself is
> > failing. This exact thing happened to me (many disconnects in the log)
> > with a printer and it was just the USB cable.
> > _______________________________________________
> > users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
> > To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
> > 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@xxxxxxxxxxxxxxxxxxxxxxx
> _______________________________________________
> users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
> To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
> 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@xxxxxxxxxxxxxxxxxxxxxxx
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
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@xxxxxxxxxxxxxxxxxxxxxxx
