Re: openvpn-client@nbecker8 won't start
Well as to how the file had the wrong context, after re-installing F35
on the new SSD, I copied the /etc/openvpn directory from my borg
backup of the old one. On the old machine I was running with selinux
disabled, so maybe it was wrong there also.
/etc/openvpn/client/nbecker8.conf is a hand-edited file. When first
created with e.g., emacs, is there a mechanism to ensure it got the
correct context?
On Thu, Dec 23, 2021 at 2:11 AM Ed Greshko wrote:
>
> On 23/12/2021 13:08, Todd Zullinger wrote:
> > Ed Greshko wrote:
> >> On 22/12/2021 21:26, Neal Becker wrote:
> >>> sudo ls -lZ /etc/openvpn/client
> >>> total 4
> >>> -rw-r--r--. 1 root openvpn system_u:object_r:openvpn_etc_t:s0 3533 Jan
> >>> 27 2021 nbecker8.conf
> >>>
> >>> This looks the same as other objects in /etc/openvpn/, so I'm guessing
> >>> it's correctly labeled?
> >>>sudo ls -lZ /etc/openvpn/
> >>> total 16
> >>> drwxr-x---. 1 root openvpn system_u:object_r:openvpn_etc_t:s0 26
> >>> Dec 15 14:14 client
> >>> drwxr-x---. 1 root openvpn system_u:object_r:openvpn_etc_t:s00
> >>> Dec 15 14:14 server
> >> Yes, this actually looks OK.
> >>
> >> You can run
> >>
> >> restorecon -n -v /etc/openvpn/client/nbecker8.conf
> >>
> >> -n don't change any file labels (passive check). To dis‐
> >>play the files whose labels would be changed, add -v.
> >>
> >> It will probably tell you that the selinux context won't be changed.
> >>
> >> So, the question then becomes why the special module is needed.
> > It seems that the selinux context is correct now, but the
> > AVC from Neal's earlier message showed the target file
> > context was fu./sefs_t (lightly re-formatted for clarity):
> >
> >> time->Tue Dec 21 14:10:56 2021 type=AVC ...
> >> avc: denied { open } for pid=120287 comm="openvpn"
> >> path="/etc/openvpn/client/nbecker8.conf" dev="nvme0n1p3" ino=167775
> >> scontext=system_u:system_r:openvpn_t:s0
> >> tcontext=system_u:object_r:fusefs_t:s0 tclass=file permissive=0
> > At that time, /etc/openvpn/client/nbecker8.conf had the
> > wrong selinux context (tcontext) which would explain why the
> > openvpn process (scontext) was not allowed to access it.
> >
> >> That would require a bit more troubleshooting. But, it is
> >> too late in my day to advise what that would entail. :-(
> > With luck, that infomation is accurate and useful in:
> > satiating your boundless curiosity, Ed (letting you get on
> > with your day/night); and making selinux ever-so-slightly
> > less random-feeling and vexing for you, Neal. Slightly is
> > all I can manage, as I would never call myself an expert at
> > it. :)
>
> LOL...
>
> I believe you are quite correct when you note the content of the AVC has the
> selinux context for the target to be
>
> tcontext=system_u:object_r:fusefs_t:s0
>
> which would be problematic. And, I admit that I really didn't look at the
> AVC.
>
> But, now I'm even more confused by this thread.
>
> I raised the question about the output of "ls -Z" on the target file in
> response
> to the question "would be the restorecon command to use". So, unless someone
> responded
> off-list and Neal ran restorecon against the file how did the context change?
>
> --
> Did 황준호 die?;
> ___
> 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
> Do not reply to spam on the list, report it:
> https://pagure.io/fedora-infrastructure
--
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
Do not reply to spam on the list, report it:
https://pagure.io/fedora-infrastructure
Re: F35 digikam
thanks for the response. I found an old version of libgeos_c.so.1 in a directory under home that was included in $.LD_LIBRARY_PATH. Your response triggered the idea to search for possibilities along that line. thanks again, sorry for the noise. On 12/22/21 16:59, Fulko Hew wrote: On Wed, Dec 22, 2021 at 4:11 PM Roger Wells wrote: upgraded F34 -> F35 & digikam no longer runs. From the CL: digikam: symbol lookup error: /lib64/libspatialite.so.7: undefined symbol: GEOSFrechetDistanceDensify I just upgraded from F33->F34->F35 and my digikam runs with no complaints like you are getting. ___ users mailing list --users@lists.fedoraproject.org To unsubscribe send an email tousers-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 Do not reply to spam on the list, report it:https://pagure.io/fedora-infrastructure___ 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 Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: F35 digikam
On Thu, 23 Dec 2021 at 09:50, Roger Wells wrote: > thanks for the response. > I found an old version of libgeos_c.so.1 in a directory under home that > was included in $.LD_LIBRARY_PATH. > Your response triggered the idea to search for possibilities along that > line. > thanks again, sorry for the noise. > You needn't be sorry about falling into one of the most common pitfalls in POSIX-style systems. There are under-used tools for managing environment variables so LD_LIBRARY_PATH can be adjusted as needed (and preferably not set until a specific environment is loaded). I learned to use environment modules on SGI IRIX64. It is still a thing, the current incarnation is Lmod,and seems well-supported. Fedora already uses environment modules to manage switching between mpich and openmpi, see "/usr/share/moduiles/mpi". > On 12/22/21 16:59, Fulko Hew wrote: > > > > On Wed, Dec 22, 2021 at 4:11 PM Roger Wells > wrote: > >> upgraded F34 -> F35 & digikam no longer runs. >> From the CL: >> digikam: symbol lookup error: /lib64/libspatialite.so.7: undefined >> symbol: GEOSFrechetDistanceDensify >> > > I just upgraded from F33->F34->F35 and my digikam runs > with no complaints like you are getting. > > > -- George N. White III ___ 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 Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Pan updates
Pan 0.149 is just out; but I get $ rpm -q pan pan-0.147-1.fc35.x86_64 -- Beartooth Staffwright, Not Quite Clueless Power User Remember I know little (precious little!) of where up is. ___ 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 Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
tiigervnc: Attempted to configure an invalid screen layout
Hello, I've problems to connect to an vnc server. Tigervnc dies with the message Attempted to configure an invalid screen layout The log reads: | $ vncviewer -Log *:stderr:100 hansipv4.in-ulm.de | | TigerVNC Viewer 64-bit v1.11.0 | Built on: 2021-06-16 00:00 | Copyright (C) 1999-2020 TigerVNC Team and many others (see README.rst) | See https://www.tigervnc.org for information on TigerVNC. | | Thu Dec 23 19:42:57 2021 | DecodeManager: Detected 8 CPU core(s) | DecodeManager: Creating 4 decoder thread(s) | TcpSocket: Connecting to hansipv4.in-ulm.de [217.10.9.184] port 5900 | CConn: Connected to host hansipv4.in-ulm.de port 5900 | CConnection: reading protocol version | CConnection: Server supports RFB protocol version 3.8 | CConnection: Using RFB protocol version 3.8 | CConnection: processing security types message | CConnection: Server offers security type [unknown secType](17) | CConnection: Server offers security type VncAuth(2) | CConnection: Choosing security type VncAuth(2) | CConnection: processing security message | | Thu Dec 23 19:43:06 2021 | CConnection: processing security result message | CConnection: processing security result message | CConnection: Authentication success! | | Thu Dec 23 19:43:07 2021 | CConnection: reading server initialisation | CConnection: initialisation done | Viewport:No key mapping for key LVL3 | Viewport:No key mapping for key HNGL | Viewport:No key mapping for key MDSW | Viewport:No key mapping for key ALT | Viewport:No key mapping for key META | Viewport:No key mapping for key SUPR | Viewport:No key mapping for key HYPR | Viewport:No key mapping for key I248 | Viewport:No key mapping for key I249 | Viewport:No key mapping for key I250 | Viewport:No key mapping for key I251 | Viewport:No key mapping for key I252 | Viewport:No key mapping for key I253 | Viewport:No key mapping for key I254 | PlatformPixelBuffer: Using shared memory XImage | CConn: Using pixel format depth 24 (32bpp) little-endian rgb888 | CConn: Attempted to configure an invalid screen layout | PlatformPixelBuffer: Freeing shared memory XImage Any help to solve the problem appreciated Greetings, Frank Elsner ___ 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 Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: Pan updates
On 24/12/2021 01:48, Beartooth wrote: Pan 0.149 is just out; but I get $ rpm -q pan pan-0.147-1.fc35.x86_64 It may be "out", but certainly it hasn't been built for Fedora. https://koji.fedoraproject.org/koji/packageinfo?packageID=2724 -- Did 황준호 die? ___ 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 Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: tiigervnc: Attempted to configure an invalid screen layout
On Thu, 23 Dec 2021 at 14:51, Frank Elsner via users < users@lists.fedoraproject.org> wrote: > Hello, > > I've problems to connect to an vnc server. Tigervnc dies with the message > > Attempted to configure an invalid screen layout > > You should mention the server you are using. This looks like https://github.com/TigerVNC/tigervnc/issues/1143, where an UltraVNC server was blamed -- George N. White III ___ 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 Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: Pan updates
On Thu, Dec 23, 2021 at 12:49 PM Beartooth wrote: > Pan 0.149 is just out; but I get $ rpm -q pan > pan-0.147-1.fc35.x86_64 > -- Beartooth: You can look up packages at https://packages.fedoraproject.org/ and https://packages.fedoraproject.org/pkgs/pan/pan/ shows you the current state of things. Perhaps you can get in touch with the maintainers of the Fedora package (linked on that page) if you are very desperate for the new version and make your case, or perhaps volunteer to help out. ___ 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 Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Webcam not recognized
I have an HD Pro Webcam C920 which has stopped working on my main system (amito), which doesn't recognize it and disconnects. I have another system (oaklandweather), which does recognize it and remains connected. Attached are the relevant extracts from the two system logs, starting at the time the camera was plugged into a USB socket; each extract is preceded by system info. Can anyone tell me what is going on and how to get the camera working? The most important difference between the two systems is that amito runs X11 but oaklandweather runs Wayland. Otherwise they look very similar, except for the hardware. -- Many Thanks - Jonathan Ryshpan This sentence have three erors. THIS DOESN'T WORK Operating System: Fedora 34 KDE Plasma Version: 5.22.5 KDE Frameworks Version: 5.85.0 Qt Version: 5.15.2 Kernel Version: 5.15.10-100.fc34.x86_64 (64-bit) Graphics Platform: X11 Processors: 8 × Intel® Core™ i7-4790K CPU @ 4.00GHz Memory: 15.5 GiB of RAM Graphics Processor: Mesa DRI Intel® HD Graphics 4600 Dec 23 14:28:09 amito kernel: usb 3-5: new high-speed USB device number 27 using xhci_hcd Dec 23 14:28:12 amito kernel: usb 3-5: New USB device found, idVendor=046d, idProduct=082d, bcdDevice= 0.11 Dec 23 14:28:12 amito kernel: usb 3-5: New USB device strings: Mfr=0, Product=2, SerialNumber=1 Dec 23 14:28:12 amito kernel: usb 3-5: Product: HD Pro Webcam C920 Dec 23 14:28:12 amito kernel: usb 3-5: SerialNumber: 0A6F9F5F Dec 23 14:28:12 amito kernel: usb 3-5: Found UVC 1.00 device HD Pro Webcam C920 (046d:082d) Dec 23 14:28:12 amito kernel: input: HD Pro Webcam C920 as /devices/pci:00/:00:14.0/usb3/3-5/3-5:1.0/input/input99 Dec 23 14:28:12 amito mtp-probe[1]: checking bus 3, device 27: "/sys/devices/pci:00/:00:14.0/usb3/3-5" Dec 23 14:28:12 amito mtp-probe[1]: bus: 3, device: 27 was not an MTP device Dec 23 14:28:12 amito mtp-probe[55591]: checking bus 3, device 27: "/sys/devices/pci:00/:00:14.0/usb3/3-5" Dec 23 14:28:12 amito mtp-probe[55591]: bus: 3, device: 27 was not an MTP device Dec 23 14:28:12 amito kdeconnectd[2925]: org.kde.pulseaudio: No object for name "alsa_output.pci-_00_1b.0.analog-stereo.monitor" Dec 23 14:28:12 amito plasmashell[2778]: org.kde.plasma.pulseaudio: No object for name "alsa_output.pci-_00_1b.0.analog-stereo.monitor" Dec 23 14:28:14 amito kernel: usb 3-5: USB disconnect, device number 27 Dec 23 14:28:14 amito kdeconnectd[2925]: org.kde.pulseaudio: No object for name "alsa_input.usb-046d_HD_Pro_Webcam_C920_0A6F9F5F-02.analog-stereo" Dec 23 14:28:14 amito kdeconnectd[2925]: org.kde.pulseaudio: No object for name "alsa_output.pci-_00_1b.0.analog-stereo.monitor" Dec 23 14:28:14 amito plasmashell[2778]: org.kde.plasma.pulseaudio: No object for name "alsa_input.usb-046d_HD_Pro_Webcam_C920_0A6F9F5F-02.analog-stereo" Dec 23 14:28:14 amito plasmashell[2778]: org.kde.plasma.pulseaudio: No object for name "alsa_output.pci-_00_1b.0.analog-stereo.monitor" THIS DOES WORK Operating System: Fedora 34 KDE Plasma Version: 5.22.5 KDE Frameworks Version: 5.85.0 Qt Version: 5.15.2 Kernel Version: 5.15.10-100.fc34.x86_64 (64-bit) Graphics Platform: Wayland Processors: 2 × Intel® Pentium® CPU G2030 @ 3.00GHz Memory: 7.6 GiB of RAM Graphics Processor: Mesa DRI Intel® HD Graphics 2500 Dec 23 14:16:59 OaklandWeather.localdomain kernel: usb 1-1.3: new high-speed USB device number 6 using ehci-pci Dec 23 14:17:01 OaklandWeather.localdomain kernel: usb 1-1.3: New USB device found, idVendor=046d, idProduct=082d, bcdDevice= 0.11 Dec 23 14:17:01 OaklandWeather.localdomain kernel: usb 1-1.3: New USB device strings: Mfr=0, Product=2, SerialNumber=1 Dec 23 14:17:01 OaklandWeather.localdomain kernel: usb 1-1.3: Product: HD Pro Webcam C920 Dec 23 14:17:01 OaklandWeather.localdomain kernel: usb 1-1.3: SerialNumber: 0A6F9F5F Dec 23 14:17:01 OaklandWeather.localdomain mtp-probe[49306]: checking bus 1, device 6: "/sys/devices/pci:00/:00:1a.0/usb1/1-1/1-1.3" Dec 23 14:17:01 OaklandWeather.localdomain mtp-probe[49306]: bus: 1, device: 6 was not an MTP device Dec 23 14:17:01 OaklandWeather.localdomain kernel: mc: Linux media interface: v0.10 Dec 23 14:17:01 OaklandWeather.localdomain kernel: videodev: Linux video capture interface: v2.00 Dec 23 14:17:01 OaklandWeather.localdomain kernel: usb 1-1.3: Found UVC 1.00 device HD Pro Webcam C920 (046d:082d) Dec 23 14:17:01 OaklandWeather.localdomain kernel: input: HD Pro Webcam C920 as /devices/pci:00/:00:1a.0/usb1/1-1/1-1.3/1-1.3:1.0/input/input29 Dec 23 14:17:01 OaklandWeather.localdomain kernel: usbcore: registered new interface driver uvcvideo Dec 23 14:17:01 OaklandWeather.localdomain kernel: usbcore: registered new interface driver snd-usb-audio Dec 23 14:17:01 OaklandWeather.localdomain mtp-probe[49329]: checking bus 1, device 6: "/sys/devices/pci:00/:00:1a.0/usb1/1-1/1-1.3" Dec 23 14:17:01 OaklandWeather.localdomain mtp-probe[49329]: bus: 1, device: 6 was not an MTP devi
Re: Webcam not recognized
On Thu, 23 Dec 2021 15:10:38 -0800 Jonathan Ryshpan wrote: > I have an HD Pro Webcam C920 which has stopped working on my main > system I have a system at home in which almost all the USB ports stopped working, so maybe it isn't the camera. You might want to try every USB port and see if one works. ___ 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 Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: Webcam not recognized
On Thu, 2021-12-23 at 18:32 -0500, Tom Horsley wrote: > On Thu, 23 Dec 2021 15:10:38 -0800 > Jonathan Ryshpan wrote: > > > I have an HD Pro Webcam C920 which has stopped working on my main > > system > > I have a system at home in which almost all the USB ports stopped > working, so maybe it isn't the camera. You might want to try every > USB port and see if one works. A very good suggestion. I switched the camera with a bluetooth dongle: the dongle works on both ports but the camera only works on one. Go figure... -- Sincerely Jonathan Ryshpan Vegetarians eat vegetables -- Beware of humanitarians. ___ 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 Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: openvpn-client@nbecker8 won't start
Neal Becker wrote: > Well as to how the file had the wrong context, after re-installing F35 > on the new SSD, I copied the /etc/openvpn directory from my borg > backup of the old one. On the old machine I was running with selinux > disabled, so maybe it was wrong there also. > > /etc/openvpn/client/nbecker8.conf is a hand-edited file. When first > created with e.g., emacs, is there a mechanism to ensure it got the > correct context? There is. SELinux policy defines the defaults for paths. The `semanage fcontext --list` command will output all of them (this is from an f34 host, in case it differs): $ sudo semanage fcontext --list | grep /etc/openvpn /etc/openvpn(/.*)? all files system_u:object_r:openvpn_etc_t:s0 /etc/openvpn/ipp\.txt regular file system_u:object_r:openvpn_etc_rw_t:s0 /etc/openvpn/scripts(/.*)? all files system_u:object_r:openvpn_unconfined_script_exec_t:s0 If I create a file in the openvpn client directory, it gets the desired labeling: $ sudo ls -Z /etc/openvpn/client/ $ sudo touch /etc/openvpn/client/test $ sudo ls -Z /etc/openvpn/client/test unconfined_u:object_r:openvpn_etc_t:s0 test If I create a file elsewhere and move or copy into the location, it's label is not changed (I'd need to use restorecon or another tool to change it): $ touch /tmp/test $ sudo mv /tmp/test /etc/openvpn/client/ $ sudo ls -Z /etc/openvpn/client/test unconfined_u:object_r:user_tmp_t:s0 test In the process of debugging this, did you perhaps recreate the file? Editing it could potentially do that, if your editor overwrites the existing file on save -- vim does not do that and I don't know that emacs would differ, but I didn't test with emacs. It's fixed now, so that's just a curiosity. But obviously, many of us here are very curious by nature. :) -- Todd signature.asc Description: PGP signature ___ 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 Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: openvpn-client@nbecker8 won't start
On Thu, 2021-12-23 at 20:48 -0500, Todd Zullinger wrote: > If I create a file elsewhere and move or copy into the > location, it's label is not changed (I'd need to use > restorecon or another tool to change it): The behaviour always was: If you move a file, it's existing SELinux contexts go with it. If you copy or create a file, SELinux creates the default contexts for the location it's writing the file to. I don't quite see why "moving" behaves the way it does, other than perhaps the simplicity of just rearranging the directory indexes. I don't recall any definition for what happens when changing between different mount points versus shifting files around within the same mount. -- uname -rsvp Linux 3.10.0-1160.49.1.el7.x86_64 #1 SMP Tue Nov 30 15:51:32 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 Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: Webcam not recognized
Tom Horsley >> I have a system at home in which almost all the USB ports stopped >> working, so maybe it isn't the camera. You might want to try every >> USB port and see if one works. Jonathan Ryshpan: > A very good suggestion. I switched the camera with a bluetooth > dongle: the dongle works on both ports but the camera only works on > one. Go figure... If any motherboard components have aged badly, it may not be able to supply power well enough on one of the ports. And it's likely your camera uses more power than the bluetooth dongle. The camera may not be fully initialising itself. A quick look at your log files looks like the failing one is trying to use it as a sound device (which is sensible if it has a microphone built in), and failing on that half. That could be a system recognition problem, or still a power problem (if the camera uses independent chips for sound and vision, it's easy enough that one part will fail differently than the other). If I try plugging two USB webcams into my computer (experimenting with basic webcams and OBS Studio), everything USB-related on my PC goes haywire. They do have different chipsets, so it shouldn't be a software clash. -- uname -rsvp Linux 3.10.0-1160.49.1.el7.x86_64 #1 SMP Tue Nov 30 15:51:32 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 Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
