Re: [Fedora] Re: Skype rpms discontinued
On Tue, Jun 4, 2024 at 6:02 PM Walter Cazzola wrote: > > >> Recently, the linux rpm distribution of skype has been discontinued: > > >> https://forums.fedoraforum.org/showthread.php?332743-Updates-hang-on-skype&p=1883992 > > >> Is there some alternative to using snap or web-skype > > >> https://snapcraft.io/install/skype/fedora > > > Oh wow, efficient packaging tailored to work properly in your OS is > > being abandoned for a huge 2GB blob (referring to one of Paul's links) > > that will probably have problems with every distro (*). > > > * My experience with allegedly universal blobs is negative, you find > > things like you cannot print from the application. You have to save a > > PDF, then open it in a PDF viewer and print from there. Tedious > > backwards crappory. > > I agree in principle, especially for the waste of space and the duplication of > libraries but I'm using it and other application via snap without big issues. > > The only one, that I'm struggling to solve is the font of the buttons of file > listener that look as missing in any application from microsoft/meta (e.g., > teams, > skype and whatsapp) Thanks for all the replies. Currently, I am using web-skype, which works reasonably well, but it turns off the camera when one shares the screen -- that is very annoying. 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 Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Skype rpms discontinued
Dear All, Recently, the linux rpm distribution of skype has been discontinued: https://forums.fedoraforum.org/showthread.php?332743-Updates-hang-on-skype&p=1883992 Is there some alternative to using snap or web-skype https://snapcraft.io/install/skype/fedora ? Thanks in advance, 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 Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: After having updated nvidia drivers, cannot start obs
On Sat, Mar 30, 2024 at 4:43 PM wrote: > > Hi. > > On Sun, 24 Mar 2024 22:19:51 +0000 Paul Smith wrote: > > > This error began after: > > > Packages Altered: > ... > > @rpmfusion-nonfree-updates > > Upgraded akmod-nvidia-3:550.54.14-2.fc39.x86_64 > > @@System > ... > > @rpmfusion-nonfree-updates > > Upgraded xorg-x11-drv-nvidia-3:550.54.14-1.fc39.x86_64 > > @@System > > Have you wait for akmods to compile the nvidia kernel modules before > rebooting ? > > "lsmod | grep nvidia" should list the nvidia module (and some others) > loaded. Example: > > lsmod | grep nvidia > nvidia_drm 81920 5 > nvidia_modeset 1511424 3 nvidia_drm > nvidia_uvm 2760704 0 > nvidia 40706048 99 nvidia_uvm,nvidia_modeset > video 77824 2 dell_wmi,nvidia_modeset > > "modinfo nvidia | grep version" should give the same version as > xorg-x11-drv-nvidia, ie: 550.54.14 > > If this is not the case, try to rebuild the kernel modules with: > > sudo akmods --rebuild I thank all who have answered! By following Francis's advice of sudo akmods --rebuild I was able to fix the problem. 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 Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
After having updated nvidia drivers, cannot start obs
Dear All, I am getting the following error message when trying to start OBS Studio: info: Initializing OpenGL... libEGL warning: DRI2: failed to authenticate MESA: error: ZINK: failed to choose pdev libEGL warning: egl: failed to create dri2 screen error: Unable to create EGL context: EGL_BAD_ATTRIBUTE error: Failed to create context! error: device_create (GL) failed error: Failed to initialize video. Your GPU may not be supported, or your graphics drivers may need to be updated. This error began after: Packages Altered: Upgrade mplayer-1.5.1-0.12.20240317svn.fc39.x86_64 @rpmfusion-free-updates Upgraded mplayer-1.5.1-0.8.20230811svn.fc39.x86_64 @@System Upgrade mplayer-common-1.5.1-0.12.20240317svn.fc39.x86_64 @rpmfusion-free-updates Upgraded mplayer-common-1.5.1-0.8.20230811svn.fc39.x86_64@@System Upgrade akmod-nvidia-3:550.67-1.fc39.x86_64 @rpmfusion-nonfree-updates Upgraded akmod-nvidia-3:550.54.14-2.fc39.x86_64 @@System Upgrade nvidia-modprobe-3:550.67-1.fc39.x86_64 @rpmfusion-nonfree-updates Upgraded nvidia-modprobe-3:550.54.14-1.fc39.x86_64 @@System Upgrade nvidia-persistenced-3:550.67-1.fc39.x86_64 @rpmfusion-nonfree-updates Upgraded nvidia-persistenced-3:550.54.14-1.fc39.x86_64 @@System Upgrade nvidia-settings-3:550.67-1.fc39.x86_64 @rpmfusion-nonfree-updates Upgraded nvidia-settings-3:550.54.14-1.fc39.x86_64 @@System Upgrade xorg-x11-drv-nvidia-3:550.67-1.fc39.x86_64 @rpmfusion-nonfree-updates Upgraded xorg-x11-drv-nvidia-3:550.54.14-1.fc39.x86_64 @@System Upgrade xorg-x11-drv-nvidia-cuda-3:550.67-1.fc39.x86_64 @rpmfusion-nonfree-updates Upgraded xorg-x11-drv-nvidia-cuda-3:550.54.14-1.fc39.x86_64 @@System Upgrade xorg-x11-drv-nvidia-cuda-libs-3:550.67-1.fc39.x86_64 @rpmfusion-nonfree-updates Upgraded xorg-x11-drv-nvidia-cuda-libs-3:550.54.14-1.fc39.x86_64 @@System Upgrade xorg-x11-drv-nvidia-kmodsrc-3:550.67-1.fc39.x86_64 @rpmfusion-nonfree-updates Upgraded xorg-x11-drv-nvidia-kmodsrc-3:550.54.14-1.fc39.x86_64 @@System Upgrade xorg-x11-drv-nvidia-libs-3:550.67-1.fc39.x86_64 @rpmfusion-nonfree-updates Upgraded xorg-x11-drv-nvidia-libs-3:550.54.14-1.fc39.x86_64 @@System Upgrade xorg-x11-drv-nvidia-power-3:550.67-1.fc39.x86_64 @rpmfusion-nonfree-updates Upgraded xorg-x11-drv-nvidia-power-3:550.54.14-1.fc39.x86_64 @@System Could you please help me? Thanks in advance, 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 Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Upgrade to F39: Disk Requirements: At least 5633 MB more space needed on the / filesystem.
On Tue, Nov 7, 2023 at 7:19 PM Jeffrey Walton wrote: > > > > Thanks, Peter: > > > > > > # df -h > > > Filesystem Size Used Avail Use% Mounted on > > > devtmpfs 4.0M 0 4.0M 0% /dev > > > tmpfs 16G 194M 16G 2% /dev/shm > > > tmpfs6.3G 1.7M 6.3G 1% /run > > > /dev/mapper/fedora_localhost--live-root 69G 68G 0 100% / > > > tmpfs 16G 36M 16G 1% /tmp > > > /dev/sda1974M 280M 627M 31% /boot > > > /dev/mapper/fedora_localhost--live-home 794G 397G 357G 53% /home > > > /dev/loop0 128K 128K 0 100% > > > /var/lib/snapd/snap/bare/5 > > > /dev/loop256M 56M 0 100% > > > /var/lib/snapd/snap/core18/2284 > > > /dev/loop1 117M 117M 0 100% > > > /var/lib/snapd/snap/core/14946 > > > /dev/loop356M 56M 0 100% > > > /var/lib/snapd/snap/core18/2745 > > > /dev/loop4 165M 165M 0 100% > > > /var/lib/snapd/snap/gnome-3-28-1804/161 > > > /dev/loop5 165M 165M 0 100% > > > /var/lib/snapd/snap/gnome-3-28-1804/198 > > > /dev/loop666M 66M 0 100% > > > /var/lib/snapd/snap/gtk-common-themes/1519 > > > /dev/loop792M 92M 0 100% > > > /var/lib/snapd/snap/gtk-common-themes/1535 > > > /dev/loop8 128K 128K 0 100% > > > /var/lib/snapd/snap/hello-world/29 > > > /dev/loop9 141M 141M 0 100% > > > /var/lib/snapd/snap/mathpix-snipping-tool/155 > > > /dev/loop10 141M 141M 0 100% > > > /var/lib/snapd/snap/mathpix-snipping-tool/195 > > > /dev/loop11 92M 92M 0 100% > > > /var/lib/snapd/snap/p3x-onenote/136 > > > /dev/loop12 81M 81M 0 100% > > > /var/lib/snapd/snap/p3x-onenote/154 > > > /dev/loop13 33M 33M 0 100% > > > /var/lib/snapd/snap/snapd/11107 > > > /dev/loop14 33M 33M 0 100% > > > /var/lib/snapd/snap/snapd/12704 > > > tmpfs3.2G 108K 3.2G 1% > > > /run/user/1000 > > > # > > > > You’re using 68 out of 69GB of your “/“ filesystem. (i.e the root > > filesystem). Several people have suggested ways to save some space, but I > > notice you are also using snaps, and they’re well known for taking up a lot > > of space because they retain multiple revisions of each app and dependency. > > > > I avoid snaps like the plague so I can’t tell you how to clean up space > > used by snapd. But I’m sure there’s an Ubuntu wiki that’ll help somewhere. > > Hear, hear! Snaps are nothing but trouble. > > I've seen old snaps consume all space or a server that formerly had > about 240 GB of free space. Thanks, Jeff: I have just removed all snaps! 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 Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Upgrade to F39: Disk Requirements: At least 5633 MB more space needed on the / filesystem.
On Tue, Nov 7, 2023 at 5:48 PM Jonathan Billings wrote: > > > Thanks, Peter: > > > > # df -h > > Filesystem Size Used Avail Use% Mounted on > > devtmpfs 4.0M 0 4.0M 0% /dev > > tmpfs 16G 194M 16G 2% /dev/shm > > tmpfs6.3G 1.7M 6.3G 1% /run > > /dev/mapper/fedora_localhost--live-root 69G 68G 0 100% / > > tmpfs 16G 36M 16G 1% /tmp > > /dev/sda1974M 280M 627M 31% /boot > > /dev/mapper/fedora_localhost--live-home 794G 397G 357G 53% /home > > /dev/loop0 128K 128K 0 100% > > /var/lib/snapd/snap/bare/5 > > /dev/loop256M 56M 0 100% > > /var/lib/snapd/snap/core18/2284 > > /dev/loop1 117M 117M 0 100% > > /var/lib/snapd/snap/core/14946 > > /dev/loop356M 56M 0 100% > > /var/lib/snapd/snap/core18/2745 > > /dev/loop4 165M 165M 0 100% > > /var/lib/snapd/snap/gnome-3-28-1804/161 > > /dev/loop5 165M 165M 0 100% > > /var/lib/snapd/snap/gnome-3-28-1804/198 > > /dev/loop666M 66M 0 100% > > /var/lib/snapd/snap/gtk-common-themes/1519 > > /dev/loop792M 92M 0 100% > > /var/lib/snapd/snap/gtk-common-themes/1535 > > /dev/loop8 128K 128K 0 100% > > /var/lib/snapd/snap/hello-world/29 > > /dev/loop9 141M 141M 0 100% > > /var/lib/snapd/snap/mathpix-snipping-tool/155 > > /dev/loop10 141M 141M 0 100% > > /var/lib/snapd/snap/mathpix-snipping-tool/195 > > /dev/loop11 92M 92M 0 100% > > /var/lib/snapd/snap/p3x-onenote/136 > > /dev/loop12 81M 81M 0 100% > > /var/lib/snapd/snap/p3x-onenote/154 > > /dev/loop13 33M 33M 0 100% > > /var/lib/snapd/snap/snapd/11107 > > /dev/loop14 33M 33M 0 100% > > /var/lib/snapd/snap/snapd/12704 > > tmpfs3.2G 108K 3.2G 1% > > /run/user/1000 > > # > > You’re using 68 out of 69GB of your “/“ filesystem. (i.e the root > filesystem). Several people have suggested ways to save some space, but I > notice you are also using snaps, and they’re well known for taking up a lot > of space because they retain multiple revisions of each app and dependency. > > I avoid snaps like the plague so I can’t tell you how to clean up space used > by snapd. But I’m sure there’s an Ubuntu wiki that’ll help somewhere. Thanks to all who have answered. The command dnf autoremove did the trick. (I am sending this message from F39.) 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 Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Upgrade to F39: Disk Requirements: At least 5633 MB more space needed on the / filesystem.
On Tue, Nov 7, 2023 at 4:57 PM Peter Boy wrote: > > >> > >> While running > >> > >> dnf system-upgrade download --releasever=39 > >> > >> to upgrade Fedora, I get the following error: > >> > >> Error Summary - > >> Disk Requirements: At least 5633 MB more space needed on the / filesystem. > >> > >> Could you please help me? > > > > Maybe I can delete something from the following, to free up space? > > > > # dir /boot > > config-6.5.8-200.fc38.x86_64 > > config-6.5.9-200.fc38.x86_64 > > efi > > extlinux > > grub2 > > initramfs-0-rescue-5cbe81aa795444b29a47ec1bf2b6dca1.img > > initramfs-5.14.9-200.fc34.x86_64.img > > initramfs-5.8.11-200.fc32.x86_64.img > > initramfs-6.5.8-200.fc38.x86_64.img > > initramfs-6.5.9-200.fc38.x86_64.img > > loader > > lost+found > > memtest86+x64.bin > > symvers-6.5.8-200.fc38.x86_64.xz > > symvers-6.5.9-200.fc38.x86_64.xz > > System.map-6.5.8-200.fc38.x86_64 > > System.map-6.5.9-200.fc38.x86_64 > > vmlinuz-0-rescue-5cbe81aa795444b29a47ec1bf2b6dca1 > > vmlinuz-6.5.8-200.fc38.x86_64 > > vmlinuz-6.5.9-200.fc38.x86_64 > > # > > > > Paul > > That may not help a lot. You need more space in / > > I guess, we need more information, e.g. the output of "df -h“, which Edition > at least. Thanks, Peter: # df -h Filesystem Size Used Avail Use% Mounted on devtmpfs 4.0M 0 4.0M 0% /dev tmpfs 16G 194M 16G 2% /dev/shm tmpfs6.3G 1.7M 6.3G 1% /run /dev/mapper/fedora_localhost--live-root 69G 68G 0 100% / tmpfs 16G 36M 16G 1% /tmp /dev/sda1974M 280M 627M 31% /boot /dev/mapper/fedora_localhost--live-home 794G 397G 357G 53% /home /dev/loop0 128K 128K 0 100% /var/lib/snapd/snap/bare/5 /dev/loop256M 56M 0 100% /var/lib/snapd/snap/core18/2284 /dev/loop1 117M 117M 0 100% /var/lib/snapd/snap/core/14946 /dev/loop356M 56M 0 100% /var/lib/snapd/snap/core18/2745 /dev/loop4 165M 165M 0 100% /var/lib/snapd/snap/gnome-3-28-1804/161 /dev/loop5 165M 165M 0 100% /var/lib/snapd/snap/gnome-3-28-1804/198 /dev/loop666M 66M 0 100% /var/lib/snapd/snap/gtk-common-themes/1519 /dev/loop792M 92M 0 100% /var/lib/snapd/snap/gtk-common-themes/1535 /dev/loop8 128K 128K 0 100% /var/lib/snapd/snap/hello-world/29 /dev/loop9 141M 141M 0 100% /var/lib/snapd/snap/mathpix-snipping-tool/155 /dev/loop10 141M 141M 0 100% /var/lib/snapd/snap/mathpix-snipping-tool/195 /dev/loop11 92M 92M 0 100% /var/lib/snapd/snap/p3x-onenote/136 /dev/loop12 81M 81M 0 100% /var/lib/snapd/snap/p3x-onenote/154 /dev/loop13 33M 33M 0 100% /var/lib/snapd/snap/snapd/11107 /dev/loop14 33M 33M 0 100% /var/lib/snapd/snap/snapd/12704 tmpfs3.2G 108K 3.2G 1% /run/user/1000 # ___ 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, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Upgrade to F39: Disk Requirements: At least 5633 MB more space needed on the / filesystem.
On Tue, Nov 7, 2023 at 4:46 PM Paul Smith wrote: > > While running > > dnf system-upgrade download --releasever=39 > > to upgrade Fedora, I get the following error: > > Error Summary - > Disk Requirements: At least 5633 MB more space needed on the / filesystem. > > Could you please help me? Maybe I can delete something from the following, to free up space? # dir /boot config-6.5.8-200.fc38.x86_64 config-6.5.9-200.fc38.x86_64 efi extlinux grub2 initramfs-0-rescue-5cbe81aa795444b29a47ec1bf2b6dca1.img initramfs-5.14.9-200.fc34.x86_64.img initramfs-5.8.11-200.fc32.x86_64.img initramfs-6.5.8-200.fc38.x86_64.img initramfs-6.5.9-200.fc38.x86_64.img loader lost+found memtest86+x64.bin symvers-6.5.8-200.fc38.x86_64.xz symvers-6.5.9-200.fc38.x86_64.xz System.map-6.5.8-200.fc38.x86_64 System.map-6.5.9-200.fc38.x86_64 vmlinuz-0-rescue-5cbe81aa795444b29a47ec1bf2b6dca1 vmlinuz-6.5.8-200.fc38.x86_64 vmlinuz-6.5.9-200.fc38.x86_64 # 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 Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Upgrade to F39: Disk Requirements: At least 5633 MB more space needed on the / filesystem.
Dear All, While running dnf system-upgrade download --releasever=39 to upgrade Fedora, I get the following error: Error Summary - Disk Requirements: At least 5633 MB more space needed on the / filesystem. Could you please help me? Thanks in advance, 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 Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Duplicated start menu entries
Dear All, I was playing with menulibre and alacarte, and now I have some duplicated start menu entries. Could you please help me? I am using XFCE on Fedora 38. Thanks in advance, Paul PS: I posted this on the XFCE mailing list two days ago, but nobody has answered. That is why I am now using Fedora 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, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Last kernel update leads to emergency mode
On Thu, Aug 31, 2023 at 3:50 PM George N. White III wrote: > >> >[...] >> > Given the fact that an older kernel works, but a newer one doesn't, it >> > sure seems like it is somehow related to the kernel. Since the same >> > version of systemd works on an old kernel, it is unlikely to be >> > systemd. Maybe you should change the bugzilla to point to the >> > kernel. You could also look through the kernel updates at >> > https://lkml.org/ to see if there is one related to warm restarts. I >> > think that might also be called suspend. There are lot of updates, >> > though, so this is a significant task. >> >> Thanks, again, Stan. I will be paying attention to >> >> https://lkml.org/ > > Search for "site: lkml.org warm reboot restart" shows a lot of activity, > often related to > specific hardware, so it is most useful if you know low level details for > your hardware. > You may want to try running a stripped down configuration to see of some > add-on > card causing the issue. Thanks, George, for your suggestion! Fortunately, the bug report I have filed has recently had reasonable activity. 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 Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Last kernel update leads to emergency mode
On Wed, Aug 30, 2023 at 2:04 PM stan via users wrote: > > > Maybe the following is relevant: > > > > > > # dracut --force --kver 6.4.12-200.fc38.x86_64 --verbose > > dracut: Executing: /usr/bin/dracut --force --kver > > 6.4.12-200.fc38.x86_64 --verbose > > dracut: dracut module 'busybox' will not be installed, because command > > 'busybox' could not be found! > > dracut: dracut module 'connman' will not be installed, because command > > 'connmand' could not be found! > > dracut: dracut module 'connman' will not be installed, because command > > 'connmanctl' could not be found! > > dracut: dracut module 'connman' will not be installed, because command > > 'connmand-wait-online' could not be found! > I see the connman errors when I build the initramfs, but it works fine. > > dracut: dracut module 'network-wicked' will not be installed, because > > command 'wicked' could not be found! > > dracut: dracut module 'biosdevname' will not be installed, because > > command 'biosdevname' could not be found! > > dracut: dracut module 'busybox' will not be installed, because command > > 'busybox' could not be found! > > dracut: dracut module 'connman' will not be installed, because command > > 'connmand' could not be found! > > dracut: dracut module 'connman' will not be installed, because command > > 'connmanctl' could not be found! > > dracut: dracut module 'connman' will not be installed, because command > > 'connmand-wait-online' could not be found! > > dracut: dracut module 'network-wicked' will not be installed, because > > command 'wicked' could not be found! > I think these can be taken as warnings rather than errors, unless you > are using busybox or network-wicked in the suspended version. > > dracut: *** Including module: bash *** > > dracut: *** Including module: systemd *** > > dracut: *** Including module: systemd-initrd *** > > dracut: *** Including module: systemd-sysusers *** > > dracut: *** Including module: nss-softokn *** > > dracut: *** Including module: dbus-broker *** > > dracut: *** Including module: rngd *** > > dracut: *** Including module: dbus *** > > dracut: *** Including module: i18n *** > > dracut: *** Including module: network-manager *** > > dracut: *** Including module: network *** > > dracut: *** Including module: ifcfg *** > > dracut: *** Including module: drm *** > > dracut: *** Including module: plymouth *** > > dracut: *** Including module: dm *** > > dracut: Skipping udev rule: 64-device-mapper.rules > > dracut: Skipping udev rule: 60-persistent-storage-dm.rules > > dracut: Skipping udev rule: 55-dm.rules > > dracut: *** Including module: kernel-modules *** > > dracut: *** Including module: kernel-modules-extra *** > > dracut: *** Including module: kernel-network-modules *** > > dracut: *** Including module: lvm *** > > dracut: Skipping udev rule: 64-device-mapper.rules > > dracut: Skipping udev rule: 56-lvm.rules > > dracut: Skipping udev rule: 60-persistent-storage-lvm.rules > > dracut: *** Including module: resume *** > > dracut: *** Including module: rootfs-block *** > > dracut: *** Including module: terminfo *** > > dracut: *** Including module: udev-rules *** > > dracut: Skipping udev rule: 40-redhat.rules > > dracut: Skipping udev rule: 50-firmware.rules > > dracut: Skipping udev rule: 50-udev.rules > > dracut: Skipping udev rule: 91-permissions.rules > > dracut: Skipping udev rule: 80-drivers-modprobe.rules > > dracut: Skipping udev rule: 70-persistent-net.rules > > dracut: *** Including module: dracut-systemd *** > > dracut: *** Including module: usrmount *** > > dracut: *** Including module: base *** > > dracut: *** Including module: fs-lib *** > > dracut: *** Including module: memstrack *** > > dracut: *** Including module: shutdown *** > > dracut: *** Including modules done *** > > dracut: *** Installing kernel module dependencies *** > > dracut: *** Installing kernel module dependencies done *** > > dracut: *** Resolving executable dependencies *** > > dracut: *** Resolving executable dependencies done *** > > dracut: *** Hardlinking files *** > > dracut: Mode: real > > dracut: Method: sha256 > > dracut: Files:2153 > > dracut: Linked: 81 files > > dracut: Compared: 0 xattrs > > dracut: Compared: 974 files > > dracut: Saved:563.14 KiB > > dracut: Duration: 0.057574 seconds > > dracut: *** Hardlinking files done *** > > dracut: *** Generating early-microcode cpio image *** > > dracut: *** Constructing AuthenticAMD.bin *** > > dracut: *** Store current command line parameters *** > > dracut: *** Stripping files *** > > dracut: *** Stripping files done *** > > dracut: *** Creating image file > > '/boot/initramfs-6.4.12-200.fc38.x86_64.img' *** dracut: Using > > auto-determined compression method 'pigz' dracut: *** Creating > > initramfs image file '/boot/initramfs-6.4.12-200.fc38.x86_64.img' > > done
Re: Last kernel update leads to emergency mode
On Tue, Aug 29, 2023 at 11:41 PM Paul Smith wrote: > > > > > > Thanks, Stan. I guess the files are almost similar, since they > > > > > have almost the same size: > > > > > > > > I agree. Your issue isn't the issue I had. Debugging these early > > > > issues is hard, because it has to be done from the emergency > > > > console. But, I think I remember there being other consoles to > > > > switch to that had things like logs, and there are some commands > > > > available, if you do an > > > > ls /usr/bin > > > > or > > > > ls /usr/sbin > > > > you should be able to examine the system to some extent to find why > > > > it is failing. I remember using less and vi at least. Could you > > > > mount one of the partitions and save / cp or cat the logs to a file > > > > there, maybe in your home directory. Then you can examine them > > > > from a working system, and even attach them to a bugzilla or email. > > > > > > > > > # ls -n /boot/initramfs* > > > > > -rw---. 1 0 0 83396891 Jan 21 2020 > > > > > /boot/initramfs-0-rescue-5cbe81aa795444b29a47ec1bf2b6dca1.img > > > > > -rw---. 1 0 0 37876860 Aug 14 11:45 > > > > > /boot/initramfs-6.4.10-200.fc38.x86_64.img > > > > > -rw---. 1 0 0 37878341 Aug 26 12:28 > > > > > /boot/initramfs-6.4.12-200.fc38.x86_64.img > > > > > > Thanks, Stan. Finally, I was able to capture the log of > > > > > > journalctl -xb > > > > > > which is at: > > > > > > https://bugzilla-attachments.redhat.com/attachment.cgi?id=1985687 > > > > So, this seems to be the error: > > Aug 28 19:05:39 localhost @ystemctl[626]: Failed to switch root: > > Specified switch root path '/sysroot' does not seem to be an OS tree. > > os-release file is missing. > > > > And it looks like it was triggered by this: > > Aug 28 19:05:39 localhost systemd[1]: Received SIGRTMIN+20 from PID 569 > > (plymouthd). > > > > After that message, systemd starts shutting down instead of starting up. > > > > Do you have fedora-release for fc38 installed? I can't see how you > > wouldn't, but just confirming. It looks like there is a bug in the > > code that is determining whether os-release is present, but only for > > warm restarts, not for cold boots. That would be plymouthd. > > Or whatever is creating the warm restart isn't creating it properly, so > > that plymouthd can recognize it, I think that would be systemd. > > > > Were either of those in the large batch of updates you installed? If > > so, you could try downgrading them from koji to see if it fixes the > > error. > > https://koji.fedoraproject.org/koji/ > > Thanks, Stan. > > I do have: > > # rpm -q fedora-release-38 > fedora-release-38-36.noarch > # > > Moreover, both plytmouth and systemd that I have installed correspond > to versions dated earlier than the date of the first occurrence of the > reported issue. > > With the older > > kernel-6.4.10-200.fc38.x86_64 > > there is no issue. Maybe the following is relevant: # dracut --force --kver 6.4.12-200.fc38.x86_64 --verbose dracut: Executing: /usr/bin/dracut --force --kver 6.4.12-200.fc38.x86_64 --verbose dracut: dracut module 'busybox' will not be installed, because command 'busybox' could not be found! dracut: dracut module 'connman' will not be installed, because command 'connmand' could not be found! dracut: dracut module 'connman' will not be installed, because command 'connmanctl' could not be found! dracut: dracut module 'connman' will not be installed, because command 'connmand-wait-online' could not be found! dracut: dracut module 'network-wicked' will not be installed, because command 'wicked' could not be found! dracut: dracut module 'biosdevname' will not be installed, because command 'biosdevname' could not be found! dracut: dracut module 'busybox' will not be installed, because command 'busybox' could not be found! dracut: dracut module 'connman' will not be installed, because command 'connmand' could not be found! dracut: dracut module 'connman' will not be installed, because command 'connmanctl' could not be found! dracut: dracut module 'connman' will not be installed, because command 'connmand-wait-online' could not be found! dracut: dracut m
Re: Last kernel update leads to emergency mode
On Tue, Aug 29, 2023 at 6:15 PM stan via users wrote: > > > > > Thanks, Stan. I guess the files are almost similar, since they > > > > have almost the same size: > > > > > > I agree. Your issue isn't the issue I had. Debugging these early > > > issues is hard, because it has to be done from the emergency > > > console. But, I think I remember there being other consoles to > > > switch to that had things like logs, and there are some commands > > > available, if you do an > > > ls /usr/bin > > > or > > > ls /usr/sbin > > > you should be able to examine the system to some extent to find why > > > it is failing. I remember using less and vi at least. Could you > > > mount one of the partitions and save / cp or cat the logs to a file > > > there, maybe in your home directory. Then you can examine them > > > from a working system, and even attach them to a bugzilla or email. > > > > > > > # ls -n /boot/initramfs* > > > > -rw---. 1 0 0 83396891 Jan 21 2020 > > > > /boot/initramfs-0-rescue-5cbe81aa795444b29a47ec1bf2b6dca1.img > > > > -rw---. 1 0 0 37876860 Aug 14 11:45 > > > > /boot/initramfs-6.4.10-200.fc38.x86_64.img > > > > -rw---. 1 0 0 37878341 Aug 26 12:28 > > > > /boot/initramfs-6.4.12-200.fc38.x86_64.img > > > > Thanks, Stan. Finally, I was able to capture the log of > > > > journalctl -xb > > > > which is at: > > > > https://bugzilla-attachments.redhat.com/attachment.cgi?id=1985687 > > So, this seems to be the error: > Aug 28 19:05:39 localhost @ystemctl[626]: Failed to switch root: > Specified switch root path '/sysroot' does not seem to be an OS tree. > os-release file is missing. > > And it looks like it was triggered by this: > Aug 28 19:05:39 localhost systemd[1]: Received SIGRTMIN+20 from PID 569 > (plymouthd). > > After that message, systemd starts shutting down instead of starting up. > > Do you have fedora-release for fc38 installed? I can't see how you > wouldn't, but just confirming. It looks like there is a bug in the > code that is determining whether os-release is present, but only for > warm restarts, not for cold boots. That would be plymouthd. > Or whatever is creating the warm restart isn't creating it properly, so > that plymouthd can recognize it, I think that would be systemd. > > Were either of those in the large batch of updates you installed? If > so, you could try downgrading them from koji to see if it fixes the > error. > https://koji.fedoraproject.org/koji/ Thanks, Stan. I do have: # rpm -q fedora-release-38 fedora-release-38-36.noarch # Moreover, both plytmouth and systemd that I have installed correspond to versions dated earlier than the date of the first occurrence of the reported issue. With the older kernel-6.4.10-200.fc38.x86_64 there is no issue. 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 Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Last kernel update leads to emergency mode
On Mon, Aug 28, 2023 at 3:25 PM stan wrote: > > > Thanks, Stan. I guess the files are almost similar, since they have > > almost the same size: > > I agree. Your issue isn't the issue I had. Debugging these early > issues is hard, because it has to be done from the emergency console. > But, I think I remember there being other consoles to switch to that > had things like logs, and there are some commands available, if you do > an > ls /usr/bin > or > ls /usr/sbin > you should be able to examine the system to some extent to find why it > is failing. I remember using less and vi at least. Could you mount > one of the partitions and save / cp or cat the logs to a file there, > maybe in your home directory. Then you can examine them from a working > system, and even attach them to a bugzilla or email. > > > # ls -n /boot/initramfs* > > -rw---. 1 0 0 83396891 Jan 21 2020 > > /boot/initramfs-0-rescue-5cbe81aa795444b29a47ec1bf2b6dca1.img > > -rw---. 1 0 0 37876860 Aug 14 11:45 > > /boot/initramfs-6.4.10-200.fc38.x86_64.img > > -rw---. 1 0 0 37878341 Aug 26 12:28 > > /boot/initramfs-6.4.12-200.fc38.x86_64.img Thanks, Stan. Finally, I was able to capture the log of journalctl -xb which is at: https://bugzilla-attachments.redhat.com/attachment.cgi?id=1985687 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 Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Last kernel update leads to emergency mode
On Sat, Aug 26, 2023 at 3:30 PM stan via users wrote: > > > > > I have been able to take a screen-shot: > > > > > > > > https://i.imgur.com/nAsE6i6.jpg > > > > > > This means that dracut was unable to start systemd in order to > > > continue the boot once the initramfs was finished creating the > > > bootstrap. I have had this happen, but not with stock kernels. I > > > build custom kernels, and dracut was not building a complete > > > initramfs when they were installed. I had to write a script that > > > created a custom file that told dracut to include all missing > > > libraries, and run dracut again after install to fix the problem. > > > The missing libraries included some vital systemd libraries. > > > Because library versions change, I run the script to be sure that > > > the custom file includes the latest libraries. If this *is* the > > > cause, it will be obvious in /boot. The failing initramfs size will > > > be about half the size of an initramfs file that works. I could > > > not find any reason that dracut wasn't working properly when it > > > first installed the kernel; all the settings said it should have > > > put those libraries in, but I just could not get it to do so. > > > > > > If it is your issue, post back and I'll attach the file of > > > libraries and the directory to put it in, as well as the dracut > > > command to run. They might not work for you, since the version has > > > to be included. There is also a way to actually examine what is in > > > the initramfs, so you could see if the systemd libraries were > > > there. From the dracut man page, > > > > > > Inspecting the Contents > > >To see the contents of the image created by dracut, you can > > > use the lsinitrd tool. > > > > > ># lsinitrd | less > > > > > >To display the contents of a file in the initramfs also use > > > the lsinitrd tool: > > > > > ># lsinitrd -f /etc/ld.so.conf > > >include ld.so.conf.d/*.conf > > > > Thanks to all for your help! > > > > I have meanwhile been able to take photos from the > > > > journalctl -xb > > > > output, and I think that now the cause of the problem is isolated. > > > > I was hopeful that the new kernel update would fix the problem, but > > it did not. > > > > The photos of the journalctl logs are at: > > > > https://i.imgur.com/NJAjOmN.jpg > > You didn't show the listing of the /boot directory. > > ls -n /boot/ > or > ls -n /boot/initramfs* > > Is the initramfs for the failing kernel smaller than the initramfs for > the successful kernel? If you can still boot into an older kernel, you > can try rebuilding the initramfs manually, to see if it will fix any > problem. You have to run this within the /boot directory, as root or > sudo. Your command should be something like the following. > > # /usr/bin/dracut -f -v --no-compress --no-uefi > initramfs-6.4.11-200.fc38.x86_64.img --kver 6.4.11-200.fc38.x86_64 > > I use no compression and no uefi, but you can remove those if they don't fit > your system. > > Once you have a new initramfs, run lsinitrd on it and redirect it into > a file. Do the same for a working initramfs. Then run a diff on the > two with the output piped to less. For example, > > lsinitrd /boot/initramfs-6.4.11-200.fc38.x86_64.img > new_initramfs.txt > lsinitrd /boot/initramfs-6.4.8-200.fc38.x86_64.img > old_initramfs.txt > diff old_initramfs.txt new_initramfs.txt | less > > There should be almost no differences if the initramfs is OK. Thanks, Stan. I guess the files are almost similar, since they have almost the same size: # ls -n /boot/initramfs* -rw---. 1 0 0 83396891 Jan 21 2020 /boot/initramfs-0-rescue-5cbe81aa795444b29a47ec1bf2b6dca1.img -rw---. 1 0 0 37876860 Aug 14 11:45 /boot/initramfs-6.4.10-200.fc38.x86_64.img -rw---. 1 0 0 37878341 Aug 26 12:28 /boot/initramfs-6.4.12-200.fc38.x86_64.img # 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 Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Last kernel update leads to emergency mode
On Fri, Aug 25, 2023 at 4:23 PM stan via users wrote: > > > I have been able to take a screen-shot: > > > > https://i.imgur.com/nAsE6i6.jpg > > This means that dracut was unable to start systemd in order to continue > the boot once the initramfs was finished creating the bootstrap. I > have had this happen, but not with stock kernels. I build custom > kernels, and dracut was not building a complete initramfs when > they were installed. I had to write a script that created a custom file > that told dracut to include all missing libraries, and run dracut again > after install to fix the problem. The missing libraries included some > vital systemd libraries. Because library versions change, I run the > script to be sure that the custom file includes the latest libraries. > If this *is* the cause, it will be obvious in /boot. The failing > initramfs size will be about half the size of an initramfs file that > works. I could not find any reason that dracut wasn't working properly > when it first installed the kernel; all the settings said it should > have put those libraries in, but I just could not get it to do so. > > If it is your issue, post back and I'll attach the file of libraries and > the directory to put it in, as well as the dracut command to run. They > might not work for you, since the version has to be included. There is > also a way to actually examine what is in the initramfs, so you could > see if the systemd libraries were there. From the dracut man page, > > Inspecting the Contents >To see the contents of the image created by dracut, you can use > the lsinitrd tool. > ># lsinitrd | less > >To display the contents of a file in the initramfs also use the > lsinitrd tool: > ># lsinitrd -f /etc/ld.so.conf >include ld.so.conf.d/*.conf Thanks to all for your help! I have meanwhile been able to take photos from the journalctl -xb output, and I think that now the cause of the problem is isolated. I was hopeful that the new kernel update would fix the problem, but it did not. The photos of the journalctl logs are at: https://i.imgur.com/NJAjOmN.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 Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Last kernel update leads to emergency mode
On Thu, Aug 24, 2023 at 4:26 PM Ranjan Maitra wrote: > > > > > > > Are other also experience that with the new kernel: > > > > > > > > > > > > 6.4.10-200.fc38.x86_64 > > > > > > > > > > > > I have already file a bug but no answer: > > > > > > > > > > > > https://bugzilla.redhat.com/show_bug.cgi?id=2232838 > > > > > > > > > > I didn't have any problems, but I updated to 6.4.11 this morning so > > > > > maybe try that. > > > > > > > > Thanks, Patrick: My bad: the problematic kernel is: > > > > > > > > kernel-6.4.11-200.fc38.x86_64 > > > > > > Can you boot into the older kernel? > > > > Yes, Ranjan, I can boot into an older kernel. Thanks! > > > > When such a thing very rarely has happened to me, it usually means that grub > did not finish installing the new kernel update. Try reinstalling perhaps? > Or rebuild grub? Thanks, Rajan and old sixpack13. I have tried to remove and then install the problematic kernel, but that does not fix the problem, unfortunately. I have been able to take a screen-shot: https://i.imgur.com/nAsE6i6.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 Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Last kernel update leads to emergency mode
On Tue, Aug 22, 2023 at 6:21 PM Samuel Sieb wrote: > > >>> Are other also experience that with the new kernel: > >>> > >>> 6.4.10-200.fc38.x86_64 > >>> > >>> I have already file a bug but no answer: > >>> > >>> https://bugzilla.redhat.com/show_bug.cgi?id=2232838 > >> > >> You didn't really provide any info that would help. Can you get any > >> journal output or the sos file? Is there any indication of what is > >> going wrong? > > > > Thanks, Samuel and Geoffrey. > > > > I have meanwhile uploaded the log file corresponding to > > > > journalctl -xb > > That's not the log from the failed boot. It looks like you booted to > the previous kernel and ran that from the running system. The log won't > be written to disk, so you have to look at it right then and possibly > save it to some external storage if possible. Thanks, Samuel. The problem is that, apparently, it is not possible to mount a pendrive. Therefore, I do not know how to grab the log file. 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 Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Last kernel update leads to emergency mode
On Tue, Aug 22, 2023 at 2:26 PM Ranjan Maitra wrote: > > > > > Are other also experience that with the new kernel: > > > > > > > > 6.4.10-200.fc38.x86_64 > > > > > > > > I have already file a bug but no answer: > > > > > > > > https://bugzilla.redhat.com/show_bug.cgi?id=2232838 > > > > > > I didn't have any problems, but I updated to 6.4.11 this morning so > > > maybe try that. > > > > Thanks, Patrick: My bad: the problematic kernel is: > > > > kernel-6.4.11-200.fc38.x86_64 > > Can you boot into the older kernel? Yes, Ranjan, I can boot into an older kernel. Thanks! 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 Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Last kernel update leads to emergency mode
On Tue, Aug 22, 2023 at 4:31 AM Samuel Sieb wrote: > > > Are other also experience that with the new kernel: > > > > 6.4.10-200.fc38.x86_64 > > > > I have already file a bug but no answer: > > > > https://bugzilla.redhat.com/show_bug.cgi?id=2232838 > > You didn't really provide any info that would help. Can you get any > journal output or the sos file? Is there any indication of what is > going wrong? Thanks, Samuel and Geoffrey. I have meanwhile uploaded the log file corresponding to journalctl -xb at: https://bugzilla.redhat.com/attachment.cgi?id=1984571 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 Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Last kernel update leads to emergency mode
On Mon, Aug 21, 2023 at 5:10 PM Patrick O'Callaghan wrote: > > > Are other also experience that with the new kernel: > > > > 6.4.10-200.fc38.x86_64 > > > > I have already file a bug but no answer: > > > > https://bugzilla.redhat.com/show_bug.cgi?id=2232838 > > I didn't have any problems, but I updated to 6.4.11 this morning so > maybe try that. Thanks, Patrick: My bad: the problematic kernel is: kernel-6.4.11-200.fc38.x86_64 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 Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Last kernel update leads to emergency mode
Dear All, Are other also experience that with the new kernel: 6.4.10-200.fc38.x86_64 I have already file a bug but no answer: https://bugzilla.redhat.com/show_bug.cgi?id=2232838 Have a nice day, 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 Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Cannot update Edge
Thanks, for all your answers! Maybe, the best is to wait for a newer version. Paul On Mon, Jul 24, 2023 at 4:26 AM Tim via users wrote: > > On Sun, 2023-07-23 at 14:47 +0100, Paul Smith wrote: > > When trying to install Edge, I get the following error message: > > > > ...[snip]... > > Error: GPG check FAILED > > I had something similar with the Google Chrome browser, some error with > the GPG keys that I can't remember now (though there were numerous bug > reports about the same thing). In the end the only thing that got it > to install was to uninstall the old version, then install the new one > as a separate step. > > > -- > > uname -rsvp > Linux 3.10.0-1160.92.1.el7.x86_64 #1 SMP Tue Jun 20 11:48:01 UTC 2023 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, report it: > https://pagure.io/fedora-infrastructure/new_issue ___ 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, report it: https://pagure.io/fedora-infrastructure/new_issue
Cannot update Edge
Dear All, When trying to install Edge, I get the following error message: # dnf update Last metadata expiration check: 2:49:11 ago on Sun 23 Jul 2023 11:55:12 AM WEST. Dependencies resolved. Package Arch Version Repository Size Upgrading: microsoft-edge-stablex86_64115.0.1901.183-1microsoft-edge145 M Transaction Summary Upgrade 1 Package Total size: 145 M Is this ok [y/N]: y Downloading Packages: [SKIPPED] microsoft-edge-stable-115.0.1901.183-1.x86_64.rpm: Already downloaded Problem opening package microsoft-edge-stable-115.0.1901.183-1.x86_64.rpm The downloaded packages were saved in cache until the next successful transaction. You can remove cached packages by executing 'dnf clean packages'. Error: GPG check FAILED # Any ideas? Thanks in advance, 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 Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Issue with running DOSBox-X exe files from Thunar
On Sun, May 28, 2023 at 10:21 PM Samuel Sieb wrote: > > >>> I hope this message finds you well. I'm reaching out regarding an > >>> issue I encountered after upgrading to the latest version of Fedora > >>> (F38) with running DOSBox-X exe files directly from the Thunar file > >>> manager. > >>> > >>> Previously, on my previous version of Fedora (F37), I could simply > >>> double-click on the icon of an exe program in Thunar, and it would run > >>> seamlessly. However, since the upgrade, I have noticed that this > >>> functionality is no longer working as expected. > >> > >> I don't use that file manager, so this is a bit of a guess. You also > >> don't say what does happen. Assuming that running it from the command > >> line works, try right-clicking the file and see what is configured to > >> open it. > > > > Thanks, Samuel, for your answer. > > > > When I right-click, I get the option > > > > Open with "DOSBox-X", > > > > but after clicking on that, nothing happens. > > Did you try running it from the command line? Thanks, Samuel. By running the following from the terminal, it works fine: dosbox-x /home/x/dosbox/tristan/TRIST256.EXE 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 Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Issue with running DOSBox-X exe files from Thunar
On Sun, May 28, 2023 at 9:19 PM Samuel Sieb wrote: > > > I hope this message finds you well. I'm reaching out regarding an > > issue I encountered after upgrading to the latest version of Fedora > > (F38) with running DOSBox-X exe files directly from the Thunar file > > manager. > > > > Previously, on my previous version of Fedora (F37), I could simply > > double-click on the icon of an exe program in Thunar, and it would run > > seamlessly. However, since the upgrade, I have noticed that this > > functionality is no longer working as expected. > > I don't use that file manager, so this is a bit of a guess. You also > don't say what does happen. Assuming that running it from the command > line works, try right-clicking the file and see what is configured to > open it. Thanks, Samuel, for your answer. When I right-click, I get the option Open with "DOSBox-X", but after clicking on that, nothing happens. 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 Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Issue with running DOSBox-X exe files from Thunar
Dear All, I hope this message finds you well. I'm reaching out regarding an issue I encountered after upgrading to the latest version of Fedora (F38) with running DOSBox-X exe files directly from the Thunar file manager. Previously, on my previous version of Fedora (F37), I could simply double-click on the icon of an exe program in Thunar, and it would run seamlessly. However, since the upgrade, I have noticed that this functionality is no longer working as expected. I am reaching out to the Fedora Linux mailing list in hopes of receiving some guidance or assistance in resolving this matter. If anyone has experienced a similar issue or has any insights on how to rectify this problem, I would greatly appreciate your help. Thank you all in advance for your time and support. Best regards, 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 Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Cannot install skypeforlinux
On Wed, May 17, 2023 at 12:26 PM Neal Becker wrote: > > Are you sure you even need to install an app? > https://www.skype.com/en/features/skype-web/ Yes, Neal, as the web-version of Skype cannot blur the video background. 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 Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Cannot install skypeforlinux
On Tue, May 16, 2023 at 7:44 PM Todd Zullinger wrote: > > Paul Smith wrote: > > Thanks, Doug. I tried as you suggested, but again: > > > > > > [SKIPPED] skypeforlinux_8.97.0.404-1.x86_64.rpm: Already downloaded > > error: Verifying a signature using certificate > > D4040146BE3972509FD57FC71F3045A5DF7587C3 (Skype Linux Client > > Repository ): > > 1. Certificiate 1F3045A5DF7587C3 invalid: certificate is not alive > > because: The primary key is not live > > because: Expired on 2021-06-21T09:36:35Z > > 2. Key 1F3045A5DF7587C3 invalid: key is not alive > > because: The primary key is not live > > because: Expired on 2021-06-21T09:36:35Z > > error: Verifying a signature using certificate > > D4040146BE3972509FD57FC71F3045A5DF7587C3 (Skype Linux Client > > Repository ): > > 1. Certificiate 1F3045A5DF7587C3 invalid: certificate is not alive > > because: The primary key is not live > > because: Expired on 2021-06-21T09:36:35Z > > 2. Key 1F3045A5DF7587C3 invalid: key is not alive > > because: The primary key is not live > > because: Expired on 2021-06-21T09:36:35Z > > Skypeforlinux - stable 13 kB/s | 1.7 kB 00:00 > > GPG key at https://repo.skype.com/data/SKYPE-GPG-KEY (0xDF7587C3) is > > already installed > > AFAICT, you have the older key installed, which has expired. > You'll need to remove it first, and then run the update > again, allowing the updated key to be installed. > > You can confirm the right key before removing it with: > > rpm -qi gpg-pubkey-df7587c3 > > and then remove it with: > > rpm -e gpg-pubkey-df7587c3 > > (Notice the "version" is the lower-cased key id, listed in > the dnf output as 0xDF7587C3.) Thanks a lot, Todd: I could finally install skype! 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 Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Cannot install skypeforlinux
On Tue, May 16, 2023 at 5:38 PM Doug Herr wrote: > > >> When trying to install > >> > >> dnf install skypeforlinux > >> > >> I am getting the error below transcribed. > >> > >> Could you please help me with this? > >> > >> Thanks in advance, > >> > >> Paul > >> - > >> > >> Downloading Packages: > >> Running transaction check > >> Transaction check succeeded. > >> Running transaction test > >> RPM: error: Verifying a signature using certificate > > > > You can try: > > > > sudo dnf install --nogpgcheck ./skypeforlinux-64.rpm > > > Or, even better: > > First download their GPG key > > $ curl https://repo.skype.com/data/SKYPE-GPG-KEY > skype-gpg-key > > Then import it to RPM: > > #sudo rpm --import skype-gpg-key > > And then try your install. Thanks, Doug. I tried as you suggested, but again: [SKIPPED] skypeforlinux_8.97.0.404-1.x86_64.rpm: Already downloaded error: Verifying a signature using certificate D4040146BE3972509FD57FC71F3045A5DF7587C3 (Skype Linux Client Repository ): 1. Certificiate 1F3045A5DF7587C3 invalid: certificate is not alive because: The primary key is not live because: Expired on 2021-06-21T09:36:35Z 2. Key 1F3045A5DF7587C3 invalid: key is not alive because: The primary key is not live because: Expired on 2021-06-21T09:36:35Z error: Verifying a signature using certificate D4040146BE3972509FD57FC71F3045A5DF7587C3 (Skype Linux Client Repository ): 1. Certificiate 1F3045A5DF7587C3 invalid: certificate is not alive because: The primary key is not live because: Expired on 2021-06-21T09:36:35Z 2. Key 1F3045A5DF7587C3 invalid: key is not alive because: The primary key is not live because: Expired on 2021-06-21T09:36:35Z Skypeforlinux - stable 13 kB/s | 1.7 kB 00:00 GPG key at https://repo.skype.com/data/SKYPE-GPG-KEY (0xDF7587C3) is already installed The GPG keys listed for the "Skypeforlinux - stable" repository are already installed but they are not correct for this package. Check that the correct key URLs are configured for this repository.. Failing package is: skypeforlinux-8.97.0.404-1.x86_64 GPG Keys are configured as: https://repo.skype.com/data/SKYPE-GPG-KEY The downloaded packages were saved in cache until the next successful transaction. You can remove cached packages by executing 'dnf clean packages'. Error: GPG check FAILED 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 Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Cannot install skypeforlinux
On Sat, May 13, 2023 at 3:29 PM Tim via users wrote: > > > When trying to install > > > > dnf install skypeforlinux > > > > I am getting the error below transcribed. > > > > - > > > > Downloading Packages: > > Running transaction check > > Transaction check succeeded. > > Running transaction test > > RPM: error: Verifying a signature using certificate > > D4040146BE3972509FD57FC71F3045A5DF7587C3 (Skype Linux Client Repository > > ): > > RPM: 1. Certificiate 1F3045A5DF7587C3 invalid: certificate is not alive > > RPM: because: The primary key is not live > > RPM: because: Expired on 2021-06-21T09:36:35Z > > RPM: 2. Key 1F3045A5DF7587C3 invalid: key is not alive > > RPM: because: The primary key is not live > > RPM: because: Expired on 2021-06-21T09:36:35Z > > RPM: error: Verifying a signature using certificate > > D4040146BE3972509FD57FC71F3045A5DF7587C3 (Skype Linux Client Repository > > ): > > RPM: 1. Certificiate 1F3045A5DF7587C3 invalid: certificate is not alive > > RPM: because: The primary key is not live > > RPM: because: Expired on 2021-06-21T09:36:35Z > > RPM: 2. Key 1F3045A5DF7587C3 invalid: key is not alive > > RPM: because: The primary key is not live > > RPM: because: Expired on 2021-06-21T09:36:35Z > > Error: Transaction test error: > > package skypeforlinux-8.97.0.404-1.x86_64 does not verify: Header V4 > > RSA/SHA256 Signature, key ID df7587c3: NOTTRUSTED > > The errors tell you that the certificates are seriously out of date, > possibly the package you're trying to install is similarly out of date, > either of which could be big problem with something like Skype (not > compatible with the current things it needs to connect to, and all the > security problems it might have). > > You haven't said where you're trying to install it from. And, if > that's a local file (which is not what I meant by the prior question), > where did you get it from? Thanks, Tim and Doug, for your answers. I got the skype rpm from the skype web-site itself: https://www.skype.com/en/get-skype/ 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 Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Cannot install skypeforlinux
Dear All, When trying to install dnf install skypeforlinux I am getting the error below transcribed. Could you please help me with this? Thanks in advance, Paul - Downloading Packages: Running transaction check Transaction check succeeded. Running transaction test RPM: error: Verifying a signature using certificate D4040146BE3972509FD57FC71F3045A5DF7587C3 (Skype Linux Client Repository ): RPM: 1. Certificiate 1F3045A5DF7587C3 invalid: certificate is not alive RPM: because: The primary key is not live RPM: because: Expired on 2021-06-21T09:36:35Z RPM: 2. Key 1F3045A5DF7587C3 invalid: key is not alive RPM: because: The primary key is not live RPM: because: Expired on 2021-06-21T09:36:35Z RPM: error: Verifying a signature using certificate D4040146BE3972509FD57FC71F3045A5DF7587C3 (Skype Linux Client Repository ): RPM: 1. Certificiate 1F3045A5DF7587C3 invalid: certificate is not alive RPM: because: The primary key is not live RPM: because: Expired on 2021-06-21T09:36:35Z RPM: 2. Key 1F3045A5DF7587C3 invalid: key is not alive RPM: because: The primary key is not live RPM: because: Expired on 2021-06-21T09:36:35Z Error: Transaction test error: package skypeforlinux-8.97.0.404-1.x86_64 does not verify: Header V4 RSA/SHA256 Signature, key ID df7587c3: NOTTRUSTED ___ 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, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Converting ext4 to btrfs
Thanks, Alex, for your reply. It seems that the safest path is to go for a fresh install of Fedora. Paul On Tue, May 2, 2023 at 11:07 AM Alex Gurenko via users wrote: > > I've forgot to add, that for compression, this, again, works only for newly > created/accesses files only, so after adding compression to fstab (and > reboot), you might want to run a defragmentation `sudo btrfs filesystem > defragment -r `. > > There was a recent article about that too: > https://fedoramagazine.org/working-with-btrfs-compression/ > > --- > Best regards, Alex > > > --- Original Message --- > On Tuesday, May 2nd, 2023 at 12:04, Alex Gurenko > wrote: > > > > There was an article back in the days of btrfs introduction that described > > the process: https://fedoramagazine.org/convert-your-filesystem-to-btrfs/ > > > > I've used it myself without any issues back then, I would assume it's still > > safe to do so now. > > > > I ran it like this for a few more releases without issues, until I decided > > to re-install fresh. > > > > The only downside would probably be (please keep me honest here), the > > defaults might not apply. > > > > There are few things that are done on a fresh install, which will probably > > won't apply on a converted system: > > > > - COW (copy-on-write) disabled for /var/lib/libvirt/images > > - probably on other directories? > > - can be done manually with `chattr -R +C ` but it only works for new > > files in said path, so you might need to move things out and back in > > > > - enable compression by making sure fstab includes `,compress=zstd:1` > > - based on your position on async discard [0], you might want to add > > `nodiscard` to fstab as well, but it seems to be okay with latest fixes > > kernels 6.2.13+ or 6.3.0, at least on a desktop > > > > [0] > > https://discussion.fedoraproject.org/t/btrfs-discard-storm-on-fedora/79997/28 > > > > --- > > Best regards, Alex > > > > > > > > > > --- Original Message --- > > On Tuesday, May 2nd, 2023 at 11:29, Paul Smith phh...@gmail.com wrote: > > > > > > > > > Dear All, > > > > > > I have always upgraded Fedora from the previously installed version. > > > Consequently, I still have ext4. To have btrfs, is it needed to do a > > > Fedora clean install? > > > > > > Thanks in advance, > > > > > > 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 > > > Do not reply to spam, report it: > > > https://pagure.io/fedora-infrastructure/new_issue > ___ > 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, report it: > https://pagure.io/fedora-infrastructure/new_issue ___ 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, report it: https://pagure.io/fedora-infrastructure/new_issue
Converting ext4 to btrfs
Dear All, I have always upgraded Fedora from the previously installed version. Consequently, I still have ext4. To have btrfs, is it needed to do a Fedora clean install? Thanks in advance, 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 Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: More space needed on the / filesystem to upgrade from F37 to F38
On Sun, Apr 30, 2023 at 5:40 PM Mike Wright wrote: > > > > > I am trying to use > > > > dnf system-upgrade download --releasever=38 > > > > to upgrade from F37 to F38. However, I am getting this error: > > > > -- > > - > > Error Summary > > - > > Disk Requirements: > > At least 4020MB more space needed on the / filesystem. > > Why does it need more than 4 gigabytes to upgrade from f37 to f38? > That's just crazy. I'd look into that before I started trying to > stretch partitions. Thanks for all replies. I have meanwhile been able to do the upgrade, by removing cache files, old kernels, the files in the trash bin and also by running sudo journalctl --vacuum-size=50M 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 Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
More space needed on the / filesystem to upgrade from F37 to F38
Dear All, I am trying to use dnf system-upgrade download --releasever=38 to upgrade from F37 to F38. However, I am getting this error: -- - Error Summary - Disk Requirements: At least 4020MB more space needed on the / filesystem. --- Any ideas? Thanks in advance, 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 Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Tool to live duplicate a small area of the screen on a separate window
Thanks a lot, Roger and Slade! I have now been able to resize the preview window up to the size I want. Paul On Sun, Oct 16, 2022 at 9:48 PM Roger Heflin wrote: > > I have been able to resize the preview window to whatever size I wanted. > > In obs itself you can make the canvas size different and you can > resize the contents inside that canvas to whatever size you want. To > do you click on the contents in obs and it will highlight the border > and you can grab the border and resize what you have showing. > > On Sun, Oct 16, 2022 at 6:37 AM Paul Smith wrote: > > > > On Sun, Oct 16, 2022 at 1:10 AM Slade Watkins via users > > wrote: > > > > > > > It might be overkill for this but obs-studio will do it. You have to > > > > create/add a screen grab and pick a window or do screen capture and > > > > once picked and working in the preview window right click on the > > > > preview and click windowed preview and size and place it. > > > > > > +1 to this! > > > > Thanks, Roger and Felix. Roger's solution is a nice one! The only > > drawback is that I cannot zoom in the contents of the preview window. > > Is there some workaround for that? > > > > 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 > > Do not reply to spam, report it: > > https://pagure.io/fedora-infrastructure/new_issue > ___ > 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, report it: > https://pagure.io/fedora-infrastructure/new_issue ___ 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, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Tool to live duplicate a small area of the screen on a separate window
On Sun, Oct 16, 2022 at 1:10 AM Slade Watkins via users wrote: > > > It might be overkill for this but obs-studio will do it. You have to > > create/add a screen grab and pick a window or do screen capture and > > once picked and working in the preview window right click on the > > preview and click windowed preview and size and place it. > > +1 to this! Thanks, Roger and Felix. Roger's solution is a nice one! The only drawback is that I cannot zoom in the contents of the preview window. Is there some workaround for that? 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 Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Tool to live duplicate a small area of the screen on a separate window
On Thu, Oct 13, 2022 at 10:31 PM Felix Miata wrote: > > > I am trying to find a tool that live duplicates, on a separate window, > > a region of the screen. I have searched for that, but with no luck. > > KMag. Thanks, Felix, for the suggestion. Unfortunately, KMag shows the area where the mouse pointer is, and what I am looking for is a tool that shows on a window a *fixed* area, as if it were a small virtual monitor with a view confined to that fixed area. 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 Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Tool to live duplicate a small area of the screen on a separate window
Dear All, I am trying to find a tool that live duplicates, on a separate window, a region of the screen. I have searched for that, but with no luck. Thanks in advance, 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 Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Current Fedora version of ImageMagick is from 2017
Thanks to all who have answered! GraphicsMagick seems to be a good alternative to ImageMagick -- thanks for the suggestion. Paul On Wed, Aug 10, 2022 at 5:34 PM Andras Simon wrote: > > 2022-08-10 18:02 UTC+02:00, Terry Polzin : > > The package may have been depreciated in favor of something else, you'll > > have to review the release notes. > > > > On Wed, Aug 10, 2022 at 11:59 AM Andras Simon wrote: > > > >> 2022-08-10 17:42 UTC+02:00, Paul Smith : > >> > Dear All, > >> > > >> > I have just noticed that the current Fedora version of > >> > > >> > ImageMagick > >> > > >> > is from 2017. Why is that? > >> > >> I don't know. But have a look at GraphicsMagick, which is 'An > >> ImageMagick fork, offering faster image generation and better > >> quality'. > > You probably meant to answer to the OP, not me, and have ImageMagick, > not GraphicsMagick in mind. > ___ > 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, report it: > https://pagure.io/fedora-infrastructure/new_issue ___ 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, report it: https://pagure.io/fedora-infrastructure/new_issue
Current Fedora version of ImageMagick is from 2017
Dear All, I have just noticed that the current Fedora version of ImageMagick is from 2017. Why is that? Thanks in advance, 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 Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Installing cuda on Fedora 36
Nvidia repo for F36 does not have all needed packages, I guess, Neal. Paul On Mon, Jun 27, 2022 at 8:23 PM Neal Becker wrote: > > I was afraid of drivers from nvidia repo, so I enabled nvidia repo only to > install cuda tools, then disabled nvidia repo. > > I have noticed that F35 nvidia repo has a lot of "stuff" in it, which F36 > looks much cleaner. The one install I'm using cuda is still on F35 though, > haven't tried F36. > > On Mon, Jun 27, 2022 at 12:30 PM Steve Underwood wrote: >> >> On 27/06/2022 15:26, Neal Becker wrote: >> > I *did not *install driver from nvidia, I am using rpmfusion driver >> > nvidia's version of drivers conflict with rpmfusions versions >> >> I did that, but I hit problems multiple times with the driver version >> when there was a big update to the CUDA RPMs. I am now use the RPMs from >> nVidia. I'm hoping this will work out better. >> >> 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 >> 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 ___ 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: Installing cuda on Fedora 36
Thanks, Neal. I have the same install, which works. However, --- # dnf update Last metadata expiration check: 1:54:37 ago on Mon 27 Jun 2022 01:36:50 PM WEST. Dependencies resolved. Problem: package cuda-11-7-11.7.0-1.x86_64 requires cuda-runtime-11-7 >= 11.7.0, but none of the providers can be installed - package cuda-11.7.0-1.x86_64 requires cuda-11-7 >= 11.7.0, but none of the providers can be installed - package cuda-runtime-11-7-11.7.0-1.x86_64 requires cuda-drivers >= 515.43.04, but none of the providers can be installed - cannot install the best update candidate for package cuda-11.6.2-1.x86_64 - package cuda-drivers-515.43.04-1.x86_64 is filtered out by modular filtering - package cuda-drivers-515.48.07-1.x86_64 is filtered out by modular filtering --- Your install does not contain cuda-11-7 either! Paul On Mon, Jun 27, 2022 at 3:28 PM Neal Becker wrote: > > Did you add > https://developer.download.nvidia.com/compute/cuda/repos/fedora35/x86_64? > > I have a working install, which has > [nbecker@nbecker8 multicarrier-predistortion]$ rpm -qa *cuda* > cuda-toolkit-config-common-11.6.55-1.noarch > cuda-toolkit-11-config-common-11.6.55-1.noarch > cuda-toolkit-11-6-config-common-11.6.55-1.noarch > cuda-cudart-11-6-11.6.55-1.x86_64 > cuda-nvrtc-11-6-11.6.124-1.x86_64 > cuda-libraries-11-6-11.6.2-1.x86_64 > cuda-nvprof-11-6-11.6.124-1.x86_64 > cuda-nvml-devel-11-6-11.6.55-1.x86_64 > cuda-nvdisasm-11-6-11.6.124-1.x86_64 > cuda-cccl-11-6-11.6.55-1.x86_64 > cuda-cudart-devel-11-6-11.6.55-1.x86_64 > cuda-runtime-11-6-11.6.2-1.x86_64 > cuda-nvrtc-devel-11-6-11.6.124-1.x86_64 > cuda-nsight-11-6-11.6.124-1.x86_64 > cuda-nvvp-11-6-11.6.124-1.x86_64 > cuda-nsight-systems-11-6-11.6.2-1.x86_64 > cuda-nsight-compute-11-6-11.6.2-1.x86_64 > cuda-samples-11-6-11.6.101-1.x86_64 > cuda-nvtx-11-6-11.6.124-1.x86_64 > cuda-nvprune-11-6-11.6.124-1.x86_64 > cuda-nvcc-11-6-11.6.124-1.x86_64 > cuda-memcheck-11-6-11.6.124-1.x86_64 > cuda-gdb-11-6-11.6.124-1.x86_64 > cuda-driver-devel-11-6-11.6.55-1.x86_64 > cuda-libraries-devel-11-6-11.6.2-1.x86_64 > cuda-visual-tools-11-6-11.6.2-1.x86_64 > cuda-documentation-11-6-11.6.124-1.x86_64 > cuda-demo-suite-11-6-11.6.55-1.x86_64 > cuda-cuxxfilt-11-6-11.6.124-1.x86_64 > cuda-cupti-11-6-11.6.124-1.x86_64 > cuda-cuobjdump-11-6-11.6.124-1.x86_64 > cuda-compiler-11-6-11.6.2-1.x86_64 > cuda-sanitizer-11-6-11.6.124-1.x86_64 > cuda-command-line-tools-11-6-11.6.2-1.x86_64 > cuda-tools-11-6-11.6.2-1.x86_64 > cuda-toolkit-11-6-11.6.2-1.x86_64 > cuda-11-6-11.6.2-1.x86_64 > cuda-11.6.2-1.x86_64 > xorg-x11-drv-nvidia-cuda-libs-510.68.02-2.fc35.x86_64 > xorg-x11-drv-nvidia-cuda-510.68.02-2.fc35.x86_64 > > I did not install driver from nvidia, I am using rpmfusion driver > nvidia's version of drivers conflict with rpmfusions versions > > On Mon, Jun 27, 2022 at 10:06 AM Paul Smith wrote: >> >> > On Mon, 27 Jun 2022 14:05:55 +0100 Paul Smith wrote: >> > > - package cuda-drivers-515.48.07-1.x86_64 is filtered out by modular >> > > filtering >> > >> > Try perhaps: dnf module reset cuda-drivers >> > >> > Then retry to install cuda-11 >> >> Thanks, Francis. I have just tried your suggestion, but: >> >> # dnf module reset cuda-drivers >> Last metadata expiration check: 1:26:20 ago on Mon 27 Jun 2022 01:36:50 PM >> WEST. >> Unable to resolve argument cuda-drivers >> Error: Problems in request: >> missing groups or modules: cuda-drivers >> # >> >> 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 >> 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
Re: Installing cuda on Fedora 36
> On Mon, 27 Jun 2022 14:05:55 +0100 Paul Smith wrote: > > - package cuda-drivers-515.48.07-1.x86_64 is filtered out by modular > > filtering > > Try perhaps: dnf module reset cuda-drivers > > Then retry to install cuda-11 Thanks, Francis. I have just tried your suggestion, but: # dnf module reset cuda-drivers Last metadata expiration check: 1:26:20 ago on Mon 27 Jun 2022 01:36:50 PM WEST. Unable to resolve argument cuda-drivers Error: Problems in request: missing groups or modules: cuda-drivers # 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 Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: Installing cuda on Fedora 36
I have found a solution: Installing the Fedora 35 cuda repository: https://developer.download.nvidia.com/compute/cuda/repos/fedora35/x86_64/ The Fedora 36 repository https://developer.download.nvidia.com/compute/cuda/repos/fedora36/x86_64/ has missing packages, I suspect. It works fine, but --- Problem: package cuda-11-7-11.7.0-1.x86_64 requires cuda-runtime-11-7 >= 11.7.0, but none of the providers can be installed - package cuda-11.7.0-1.x86_64 requires cuda-11-7 >= 11.7.0, but none of the providers can be installed - package cuda-runtime-11-7-11.7.0-1.x86_64 requires cuda-drivers >= 515.43.04, but none of the providers can be installed - cannot install the best update candidate for package cuda-11.6.2-1.x86_64 - package cuda-drivers-515.43.04-1.x86_64 is filtered out by modular filtering - package cuda-drivers-515.48.07-1.x86_64 is filtered out by modular filtering --- Paul On Sun, Jun 26, 2022 at 11:21 PM Michael D. Setzer II wrote: > > https://docs.nvidia.com/cuda/cuda-compiler-driver-nvcc/in > dex.html > > Has a link for linux and commands. > dnf whatprovides */nvcc > didn't find anything, so looks like it has to be downloaded > from other site. > > > On 26 Jun 2022 at 23:03, Paul Smith wrote: > > From: Paul Smith > Date sent: Sun, 26 Jun 2022 23:03:34 +0100 > Subject:Re: Installing cuda on Fedora 36 > To: Community support for Fedora users > > Send reply to: Community support for Fedora > users > > > On Sun, Jun 26, 2022 at 10:10 PM Patrick O'Callaghan > > wrote: > > > > > > > > > Could someone please direct me in the process of installing cuda? > > > > > > > > > > Simplest way is probably via rpmfusion: > > > > > > > > > > https://rpmfusion.org/Howto/CUDA?highlight=%28%5CbCategoryHowto%5Cb%29 > > > > > > > > Thanks, Tom. I have followed all steps, but then I get the following > > > > error: > > > > > > > > --- > > > > # dnf -y install cuda > > > > Last metadata expiration check: 0:04:09 ago on Sun 26 Jun 2022 > > > > 09:34:42 PM WEST. > > > > No match for argument: cuda > > > > Error: Unable to find a match: cuda > > > > # > > > > > > $ dnf search cuda > > > Last metadata expiration check: 0:00:18 ago on Sun 26 Jun 2022 22:06:30 > > > BST. > > > === > > > Name & Summary Matched: cuda > > > === > > > xorg-x11-drv-nvidia-340xx-cuda.x86_64 : CUDA libraries for > > > xorg-x11-drv-nvidia-340xx > > > xorg-x11-drv-nvidia-390xx-cuda.x86_64 : CUDA driver for > > > xorg-x11-drv-nvidia-390xx > > > xorg-x11-drv-nvidia-390xx-cuda-libs.i686 : CUDA libraries for > > > xorg-x11-drv-nvidia-390xx > > > xorg-x11-drv-nvidia-390xx-cuda-libs.x86_64 : CUDA libraries for > > > xorg-x11-drv-nvidia-390xx > > > xorg-x11-drv-nvidia-470xx-cuda.x86_64 : CUDA driver for > > > xorg-x11-drv-nvidia-470xx > > > xorg-x11-drv-nvidia-470xx-cuda-libs.i686 : CUDA libraries for > > > xorg-x11-drv-nvidia-470xx > > > xorg-x11-drv-nvidia-470xx-cuda-libs.x86_64 : CUDA libraries for > > > xorg-x11-drv-nvidia-470xx > > > xorg-x11-drv-nvidia-cuda.x86_64 : CUDA driver for xorg-x11-drv-nvidia > > > xorg-x11-drv-nvidia-cuda-libs.x86_64 : CUDA libraries for > > > xorg-x11-drv-nvidia > > > xorg-x11-drv-nvidia-cuda-libs.i686 : CUDA libraries for > > > xorg-x11-drv-nvidia > > > > > > I'm guessing you need "dnf install xorg-x11-drv-nvidia-cuda" > > > > Thanks, Patrick. I have meanwhile done > > > > "dnf install xorg-x11-drv-nvidia-cuda" > > > > However, when I try to compile a .cu program, I get the following error: > > > > $ nvcc x.cu -o x > > bash: nvcc: command not found > > $ > > > > I did search for nvcc, but: > > > > # dnf search nvcc > > Last metadata expiration check: 1:18:55 ago on Sun 26 Jun 2022 09:34:42 PM > > WEST. > > No matches found. > > # > > > > Any ideas? > > > > Paul > > ___ > > users mailing list -- users@lists.fedoraproject.org > &
Re: Installing cuda on Fedora 36
On Sun, Jun 26, 2022 at 10:10 PM Patrick O'Callaghan wrote: > > > > > Could someone please direct me in the process of installing cuda? > > > > > > Simplest way is probably via rpmfusion: > > > > > > https://rpmfusion.org/Howto/CUDA?highlight=%28%5CbCategoryHowto%5Cb%29 > > > > Thanks, Tom. I have followed all steps, but then I get the following > > error: > > > > --- > > # dnf -y install cuda > > Last metadata expiration check: 0:04:09 ago on Sun 26 Jun 2022 > > 09:34:42 PM WEST. > > No match for argument: cuda > > Error: Unable to find a match: cuda > > # > > $ dnf search cuda > Last metadata expiration check: 0:00:18 ago on Sun 26 Jun 2022 22:06:30 BST. > === > Name & Summary Matched: cuda > === > xorg-x11-drv-nvidia-340xx-cuda.x86_64 : CUDA libraries for > xorg-x11-drv-nvidia-340xx > xorg-x11-drv-nvidia-390xx-cuda.x86_64 : CUDA driver for > xorg-x11-drv-nvidia-390xx > xorg-x11-drv-nvidia-390xx-cuda-libs.i686 : CUDA libraries for > xorg-x11-drv-nvidia-390xx > xorg-x11-drv-nvidia-390xx-cuda-libs.x86_64 : CUDA libraries for > xorg-x11-drv-nvidia-390xx > xorg-x11-drv-nvidia-470xx-cuda.x86_64 : CUDA driver for > xorg-x11-drv-nvidia-470xx > xorg-x11-drv-nvidia-470xx-cuda-libs.i686 : CUDA libraries for > xorg-x11-drv-nvidia-470xx > xorg-x11-drv-nvidia-470xx-cuda-libs.x86_64 : CUDA libraries for > xorg-x11-drv-nvidia-470xx > xorg-x11-drv-nvidia-cuda.x86_64 : CUDA driver for xorg-x11-drv-nvidia > xorg-x11-drv-nvidia-cuda-libs.x86_64 : CUDA libraries for xorg-x11-drv-nvidia > xorg-x11-drv-nvidia-cuda-libs.i686 : CUDA libraries for xorg-x11-drv-nvidia > > I'm guessing you need "dnf install xorg-x11-drv-nvidia-cuda" Thanks, Patrick. I have meanwhile done "dnf install xorg-x11-drv-nvidia-cuda" However, when I try to compile a .cu program, I get the following error: $ nvcc x.cu -o x bash: nvcc: command not found $ I did search for nvcc, but: # dnf search nvcc Last metadata expiration check: 1:18:55 ago on Sun 26 Jun 2022 09:34:42 PM WEST. No matches found. # Any ideas? 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 Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: Installing cuda on Fedora 36
On Sun, Jun 26, 2022 at 9:32 PM Tom Horsley wrote: > > > Could someone please direct me in the process of installing cuda? > > Simplest way is probably via rpmfusion: > > https://rpmfusion.org/Howto/CUDA?highlight=%28%5CbCategoryHowto%5Cb%29 Thanks, Tom. I have followed all steps, but then I get the following error: --- # dnf -y install cuda Last metadata expiration check: 0:04:09 ago on Sun 26 Jun 2022 09:34:42 PM WEST. No match for argument: cuda Error: Unable to find a match: cuda # --- Any ideas? 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 Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Installing cuda on Fedora 36
Dear All, Could someone please direct me in the process of installing cuda? Thanks in advance, 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 Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: Foliate does not work
On Sun, May 29, 2022 at 7:35 AM Samuel Sieb wrote: > > >>> I cannot be sure, but I suspect that after having upgraded to F36, > >>> Foliate no longer works. > >>> > >>> Any ideas? Do others experience the same problem? > >> > >> You need to provide more details about what "not working" means. I > >> just > >> installed it on F36 and opened an epub file with no problem. > > > > Thanks, Samuel. When I try to open whatever epub file, I get the > > following error message: > > > > "Could not open file > > Empty Response" > > "Empty Response" issues were discussed for multiple distros and install > methods > in foliate could not open file · Issue #401 · johnfactotum/foliate > (github.com). > It seems to stem from cross-origin protections: > > Quoting the wiki: By default, JavaScript and all external resources are > blocked in Foliate. > For additional safeguard against potential vulnerabilities it is > recommended to run Foliate > in a sandboxed environment, for example, by using the Flatpak package. > >>> > >>> Thanks, George. That is exactly the same problem I am having! > >> > >> That issue is all over the place. It mostly seemed to be referring to > >> the snap install, but then there were a couple of mentions of other > >> types. The rpm version works perfectly fine for me. Is that what you > >> are using? Where is the file you're trying to open? > > > > Thanks, Samuel. The reported error corresponds to the rpm version of > > foliate. The flatpak foliate package works perfectly. > > Did you see the comment about deleting the user local mime.cache file? > That might explain the difference. Mine is a new install and I've never > associated epub files with anything. If you don't want to delete it, > then try temporarily moving it somewhere else and see if that solves > your problem. Thanks, Samuel and George. By removing the file ~/.local/share/mime/mime.cache as suggested in the mentioned comment, the problem was fixed! 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 Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: Foliate does not work
On Sat, May 28, 2022 at 1:44 AM Samuel Sieb wrote: > > > I cannot be sure, but I suspect that after having upgraded to F36, > > Foliate no longer works. > > > > Any ideas? Do others experience the same problem? > > You need to provide more details about what "not working" means. I just > installed it on F36 and opened an epub file with no problem. > >>> > >>> Thanks, Samuel. When I try to open whatever epub file, I get the > >>> following error message: > >>> > >>> "Could not open file > >>> Empty Response" > >> > >> "Empty Response" issues were discussed for multiple distros and install > >> methods > >> in foliate could not open file · Issue #401 · johnfactotum/foliate > >> (github.com). > >> It seems to stem from cross-origin protections: > >> > >> Quoting the wiki: By default, JavaScript and all external resources are > >> blocked in Foliate. > >> For additional safeguard against potential vulnerabilities it is > >> recommended to run Foliate > >> in a sandboxed environment, for example, by using the Flatpak package. > > > > Thanks, George. That is exactly the same problem I am having! > > That issue is all over the place. It mostly seemed to be referring to > the snap install, but then there were a couple of mentions of other > types. The rpm version works perfectly fine for me. Is that what you > are using? Where is the file you're trying to open? Thanks, Samuel. The reported error corresponds to the rpm version of foliate. The flatpak foliate package works perfectly. 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 Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: Foliate does not work
On Sat, May 28, 2022 at 12:05 AM Paul Smith wrote: > > >> > > I cannot be sure, but I suspect that after having upgraded to F36, > >> > > Foliate no longer works. > >> > > > >> > > Any ideas? Do others experience the same problem? > >> > > >> > You need to provide more details about what "not working" means. I just > >> > installed it on F36 and opened an epub file with no problem. > >> > >> Thanks, Samuel. When I try to open whatever epub file, I get the > >> following error message: > >> > >> "Could not open file > >> Empty Response" > > > > "Empty Response" issues were discussed for multiple distros and install > > methods > > in foliate could not open file · Issue #401 · johnfactotum/foliate > > (github.com). > > It seems to stem from cross-origin protections: > > > > Quoting the wiki: By default, JavaScript and all external resources are > > blocked in Foliate. > > For additional safeguard against potential vulnerabilities it is > > recommended to run Foliate > > in a sandboxed environment, for example, by using the Flatpak package. > > Thanks, George. That is exactly the same problem I am having! Moreover, the flatpak foliate package works just fine! 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 Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: Foliate does not work
On Fri, May 27, 2022 at 10:37 PM George N. White III wrote: > >> > > I cannot be sure, but I suspect that after having upgraded to F36, >> > > Foliate no longer works. >> > > >> > > Any ideas? Do others experience the same problem? >> > >> > You need to provide more details about what "not working" means. I just >> > installed it on F36 and opened an epub file with no problem. >> >> Thanks, Samuel. When I try to open whatever epub file, I get the >> following error message: >> >> "Could not open file >> Empty Response" > > "Empty Response" issues were discussed for multiple distros and install > methods > in foliate could not open file · Issue #401 · johnfactotum/foliate > (github.com). > It seems to stem from cross-origin protections: > > Quoting the wiki: By default, JavaScript and all external resources are > blocked in Foliate. > For additional safeguard against potential vulnerabilities it is recommended > to run Foliate > in a sandboxed environment, for example, by using the Flatpak package. Thanks, George. That is exactly the same problem I am having! 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 Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: Foliate does not work
On Fri, May 27, 2022 at 9:17 PM Samuel Sieb wrote: > > >>> I cannot be sure, but I suspect that after having upgraded to F36, > >>> Foliate no longer works. > >>> > >>> Any ideas? Do others experience the same problem? > >> > >> You need to provide more details about what "not working" means. I just > >> installed it on F36 and opened an epub file with no problem. > > > > Thanks, Samuel. When I try to open whatever epub file, I get the > > following error message: > > > > "Could not open file > > Empty Response" > > That is a very strange error. Is that a local file? I also just tried > accessing an online file and that worked as well. Yes, Samuel, it is a local file. 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 Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: Foliate does not work
On Fri, May 27, 2022 at 8:56 PM Samuel Sieb wrote: > > > I cannot be sure, but I suspect that after having upgraded to F36, > > Foliate no longer works. > > > > Any ideas? Do others experience the same problem? > > You need to provide more details about what "not working" means. I just > installed it on F36 and opened an epub file with no problem. Thanks, Samuel. When I try to open whatever epub file, I get the following error message: "Could not open file Empty Response" 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 Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Foliate does not work
Dear All, I cannot be sure, but I suspect that after having upgraded to F36, Foliate no longer works. Any ideas? Do others experience the same problem? Thanks in advance, 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 Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: Incompatibility between webcam and drawing tablet
Thanks to all for your help. I have plug the webcam in a USB port behind the computer and the drawing tablet in the front of the computer, and now the two devices can work when both connected to the computer. Before, both were plugged in the front of the computer, in USB ports side by side. I guess the problem was related to the USB bus that may not have enough power budget for both devices, as Go Canes conjectured. Paul On Fri, Apr 15, 2022 at 7:01 PM Mauricio Tavares wrote: > > Does your computer have more than one USB chain, so you can see if the > problem follows the USB bus or the device(s)? > > On Fri, Apr 15, 2022 at 12:15 PM Paul Smith wrote: > > > > Dear All, > > > > When I plug in my drawing tablet, my webcam does not work; when I > > unplug the drawing tablet, the webcam starts to work. > > > > Both devices use USB to connect to the computer. > > > > Could you please direct me in the right direction to the cause of the > > problem? > > > > Thanks in advance, > > > > 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 > > 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 ___ 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
Incompatibility between webcam and drawing tablet
Dear All, When I plug in my drawing tablet, my webcam does not work; when I unplug the drawing tablet, the webcam starts to work. Both devices use USB to connect to the computer. Could you please direct me in the right direction to the cause of the problem? Thanks in advance, 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 Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: Window always on top of a specified program window
On Thu, Jan 27, 2022 at 4:04 PM Doug Herr wrote: > > > With XFCE, we can set a window to always be on top of all other > > windows. However, I am looking for a variant of such a feature: Always > > on top of the window I specify, say always on top of the Firefox > > window. > > > > Is such a tool available on Fedora? > > An alternate solution... > > Set the Firefox window to "Always Below Other Windows". If the thing you care > about is the only thing you place over Firefox then this might solve the > problem. Thanks, Doug, for your nice idea! The only inconvenience is that I have to minimize all windows to get Firefox, although there is a button to do that at once. 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 Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Window always on top of a specified program window
Dear All, With XFCE, we can set a window to always be on top of all other windows. However, I am looking for a variant of such a feature: Always on top of the window I specify, say always on top of the Firefox window. Is such a tool available on Fedora? Thanks in advance, 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 Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: Problem with script
Fixed now! I had to put the following line in the script: export DISPLAY=:0 Paul On Fri, Nov 19, 2021 at 8:30 PM Ulf Volmer wrote: > > On 19.11.21 20:54, Cameron Simpson wrote: > > On 19Nov2021 20:42, Ulf Volmer wrote: > >> gxmessage relays on an X11 display. You have none in a session started > >> via atd. > > > > You're confusing this with cron. At preserves your environment. If he's > > still logging into his X11 session this should work. > > Yes, agree, you are right. > > Best regards > Ulf > > ___ > 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 ___ 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: Problem with script
Thanks, Ulf and Garry. Ulf seems to be right, as the following echo "XAUTHORITY=/run/user/1000/gdm/Xauthority DISPLAY=:0 gxmessage \"hello\"" | at 7:52PM -M while echo "gxmessage \"hello\"" | at 7:52PM -M does not. Should I put XAUTHORITY=/run/user/1000/gdm/Xauthority DISPLAY=:0 in the script? The syntax is correct? Paul On Fri, Nov 19, 2021 at 7:45 PM Garry T. Williams wrote: > > On Friday, November 19, 2021 1:04:44 PM EST Paul Smith wrote: > > I am trying to run a script with the following command: > > > > echo "~/scripts/teste.sh" | at 5:59PM > > > > but nothing happens. > > That's because there is no tilde expansion inside of quotes. > > Lose the quotes and all will be well. > > -- > Garry T. Williams > > > ___ > 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 ___ 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: Problem with script
Thanks, Joe. I put echo xxx in the second line of the script and nothing was printed. The log mentions the creation of a new session, which is closed when (apparently) the execution of the script finishes. Paul On Fri, Nov 19, 2021 at 7:30 PM Joe Zeff wrote: > > Adding echo or print statements to a program or script for debugging is > such an old technique that most people have either forgotten it or never > learned it. > > On 11/19/21 12:11 PM, Paul Smith wrote: > > Nov 19 19:07:00 localhost atd[45263]: Exec failed for mail command: No > > such file or directory > > If you want, you can add -M to the at command to suppress all mail and > get rid of that. > ___ > 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 ___ 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: Problem with script
Thanks, Clifford. No, they are not scheduled to start later -- I have just checked that with atq. Moreover, the log tells that the script is run at the specified time. Paul On Fri, Nov 19, 2021 at 7:19 PM Clifford Snow wrote: > > Also check at -l, or atq to see if it is scheduled to run later. > >> > >> > > I am trying to run a script with the following command: >> > > >> > > echo "~/scripts/teste.sh" | at 5:59PM >> > > >> > > but nothing happens. >> > >> > Try putting some echo commands into the script, redirected to a file so >> > that you can see if the script runs at all, and if so, how far it gets. >> >> Thanks, Joe. I am going to try that, but the following log may help to >> trace down the problem: >> >> --- >> Nov 19 19:07:00 localhost atd[45259]: Starting job 110 >> (a0006e01a0663b) for user 'x' (1000) >> Nov 19 19:07:00 localhost audit[45259]: USER_ACCT pid=45259 uid=0 >> auid=4294967295 ses=4294967295 >> subj=system_u:system_r:crond_t:s0-s0:c0.c1023 msg='op=PAM:accounting >> grantors=pam_access,pam_unix,pam_localuser acct="x" >> exe="/usr/sbin/atd" hostname=? addr=? terminal=atd res=success' >> Nov 19 19:07:00 localhost systemd-logind[1147]: New session 17 of user x. >> Nov 19 19:07:00 localhost systemd[1]: Started Session 17 of User x. >> Nov 19 19:07:00 localhost atd[45259]: pam_unix(atd:session): session >> opened for user x(uid=1000) by (uid=0) >> Nov 19 19:07:00 localhost audit[45259]: USER_START pid=45259 uid=0 >> auid=1000 ses=17 subj=system_u:system_r:crond_t:s0-s0:c0.c1023 >> msg='op=PAM:session_open >> grantors=pam_loginuid,pam_keyinit,pam_limits,pam_systemd,pam_unix >> acct="x" exe="/usr/sbin/atd" hostname=? addr=? terminal=atd >> res=success' >> Nov 19 19:07:00 localhost audit[45259]: CRED_ACQ pid=45259 uid=0 >> auid=1000 ses=17 subj=system_u:system_r:crond_t:s0-s0:c0.c1023 >> msg='op=PAM:setcred grantors=pam_env,pam_env,pam_localuser,pam_unix >> acct="x" exe="/usr/sbin/atd" hostname=? addr=? terminal=atd >> res=success' >> Nov 19 19:07:00 localhost atd[45263]: Exec failed for mail command: No >> such file or directory >> Nov 19 19:07:00 localhost audit[45259]: CRED_DISP pid=45259 uid=0 >> auid=1000 ses=17 subj=system_u:system_r:crond_t:s0-s0:c0.c1023 >> msg='op=PAM:setcred grantors=pam_env,pam_env,pam_localuser,pam_unix >> acct="x" exe="/usr/sbin/atd" hostname=? addr=? terminal=atd >> res=success' >> Nov 19 19:07:00 localhost atd[45259]: pam_unix(atd:session): session >> closed for user x >> Nov 19 19:07:00 localhost audit[45259]: USER_END pid=45259 uid=0 >> auid=1000 ses=17 subj=system_u:system_r:crond_t:s0-s0:c0.c1023 >> msg='op=PAM:session_close >> grantors=pam_loginuid,pam_keyinit,pam_limits,pam_systemd,pam_unix >> acct="x" exe="/usr/sbin/atd" hostname=? addr=? terminal=atd >> res=success' >> Nov 19 19:07:00 localhost systemd[1]: session-17.scope: Deactivated >> successfully. >> --- >> >> 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 >> Do not reply to spam on the list, report it: >> https://pagure.io/fedora-infrastructure > > > > -- > @osm_washington > www.snowandsnow.us > OpenStreetMap: Maps with a human touch > ___ > 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 ___ 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: Problem with script
On Fri, Nov 19, 2021 at 7:09 PM Joe Zeff wrote: > > > I am trying to run a script with the following command: > > > > echo "~/scripts/teste.sh" | at 5:59PM > > > > but nothing happens. > > Try putting some echo commands into the script, redirected to a file so > that you can see if the script runs at all, and if so, how far it gets. Thanks, Joe. I am going to try that, but the following log may help to trace down the problem: --- Nov 19 19:07:00 localhost atd[45259]: Starting job 110 (a0006e01a0663b) for user 'x' (1000) Nov 19 19:07:00 localhost audit[45259]: USER_ACCT pid=45259 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:crond_t:s0-s0:c0.c1023 msg='op=PAM:accounting grantors=pam_access,pam_unix,pam_localuser acct="x" exe="/usr/sbin/atd" hostname=? addr=? terminal=atd res=success' Nov 19 19:07:00 localhost systemd-logind[1147]: New session 17 of user x. Nov 19 19:07:00 localhost systemd[1]: Started Session 17 of User x. Nov 19 19:07:00 localhost atd[45259]: pam_unix(atd:session): session opened for user x(uid=1000) by (uid=0) Nov 19 19:07:00 localhost audit[45259]: USER_START pid=45259 uid=0 auid=1000 ses=17 subj=system_u:system_r:crond_t:s0-s0:c0.c1023 msg='op=PAM:session_open grantors=pam_loginuid,pam_keyinit,pam_limits,pam_systemd,pam_unix acct="x" exe="/usr/sbin/atd" hostname=? addr=? terminal=atd res=success' Nov 19 19:07:00 localhost audit[45259]: CRED_ACQ pid=45259 uid=0 auid=1000 ses=17 subj=system_u:system_r:crond_t:s0-s0:c0.c1023 msg='op=PAM:setcred grantors=pam_env,pam_env,pam_localuser,pam_unix acct="x" exe="/usr/sbin/atd" hostname=? addr=? terminal=atd res=success' Nov 19 19:07:00 localhost atd[45263]: Exec failed for mail command: No such file or directory Nov 19 19:07:00 localhost audit[45259]: CRED_DISP pid=45259 uid=0 auid=1000 ses=17 subj=system_u:system_r:crond_t:s0-s0:c0.c1023 msg='op=PAM:setcred grantors=pam_env,pam_env,pam_localuser,pam_unix acct="x" exe="/usr/sbin/atd" hostname=? addr=? terminal=atd res=success' Nov 19 19:07:00 localhost atd[45259]: pam_unix(atd:session): session closed for user x Nov 19 19:07:00 localhost audit[45259]: USER_END pid=45259 uid=0 auid=1000 ses=17 subj=system_u:system_r:crond_t:s0-s0:c0.c1023 msg='op=PAM:session_close grantors=pam_loginuid,pam_keyinit,pam_limits,pam_systemd,pam_unix acct="x" exe="/usr/sbin/atd" hostname=? addr=? terminal=atd res=success' Nov 19 19:07:00 localhost systemd[1]: session-17.scope: Deactivated successfully. --- 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 Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: How to dnf clean all of a specific repo?
On Tue, Nov 9, 2021 at 2:27 PM Ed Greshko wrote: > > >>> What am I doing wrong? > >> Look inside that .repo file for the [name of repo] text at the > >> top. Use that name in the enablerepo argument. > > Thanks, Tom. Unfortunately, it cleans all not regarding the specific > > repo but all repos! > > Looking at the man page, it would seem that disabling repos would not be > effective. > > Clean Command > Command: clean > > Performs cleanup of temporary files kept for repositories. This > includes > any such data left behind from disabled or removed repositories as > well > as for different distribution release versions. I have meanwhile found a workaround: disabling and enabling again the desired repo. 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 Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Problem with script
Dear All, I am trying to run a script with the following command: echo "~/scripts/teste.sh" | at 5:59PM but nothing happens. My script is: --- #!/bin/bash gxmessage -center \ -buttons "Yes":1,"Of Course":2 \ -geometry 290x80 \ -title "Linux Journal Question" 'Does Shawn Powers ROCK?' answer=$? case "$answer" in 1) gxmessage -center "You said 'YES'" ;; *) gxmessage -center "I agree, Of Course." ;; esac --- If I run sh ~/scripts/teste.sh the script works as expected. Any ideas? Thanks in advance, 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 Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: How to dnf clean all of a specific repo?
On Tue, Nov 9, 2021 at 1:33 PM Tom Horsley wrote: > > > What am I doing wrong? > > Look inside that .repo file for the [name of repo] text at the > top. Use that name in the enablerepo argument. Thanks, Tom. Unfortunately, it cleans all not regarding the specific repo but all repos! 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 Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
How to dnf clean all of a specific repo?
Dear All, Suppose that one wants to dnf clean all of a specific repo. I have tried the following command: dnf clean all --enablerepo="_copr:copr.fedorainfracloud.org:mfabian:ibus-typing-booster" --disablerepo="*" but I get the following error: # dnf clean all --enablerepo="_copr:copr.fedorainfracloud.org:mfabian:ibus-typing-booster" --disablerepo="*" Error: Unknown repo: '_copr:copr.fedorainfracloud.org:mfabian:ibus-typing-booster' # But # ls /etc/yum.repos.d/ | grep ibus _copr:copr.fedorainfracloud.org:mfabian:ibus-typing-booster.repo # What am I doing wrong? Thanks in advance, 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 Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: F35 still running pulseaudio after upgrade
On Wed, Nov 3, 2021 at 3:48 PM Ian Pilcher wrote: > > Are there instructions anywhere for switching to pipewire? See the following, Ian: https://fedoraproject.org/wiki/Changes/WirePlumber and run dnf swap wireplumber pipewire-media-session 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 Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: No audio on F35
On Tue, Nov 2, 2021 at 5:28 PM Patrick O'Callaghan wrote: > > > I have just upgraded from F34 to F35, but on F35 I do not have any > > audio. > > > > Could someone please help me? > > Several recent posts have mentioned that you need to enable the > wireplumber session manager for PipeWire. Check the list archive. Thank you so much, Patrick! Problem fixed by having run the following command: dnf swap wireplumber pipewire-media-session More information at: https://fedoraproject.org/wiki/Changes/WirePlumber 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 Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: No audio on F35
On Tue, Nov 2, 2021 at 5:18 PM Paul Smith wrote: > > I have just upgraded from F34 to F35, but on F35 I do not have any audio. In the audio mixer panel, no input or output device is listed! That is very strange! 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 Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
No audio on F35
Dear All, I have just upgraded from F34 to F35, but on F35 I do not have any audio. Could someone please help me? Thanks in advance, 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 Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Playing audio simultaneously on a Bluetooth device and on computer
Dear All, I am wondering whether it is possible to listen to audio simultaneously on a Bluetooth device and on the computer (running Fedora 34). Thanks in advance, 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 Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: Setting the active area of drawing tablet
On Fri, Sep 17, 2021 at 11:45 AM Paul Smith wrote: > > > >>> While sliding the stylus horizontally from the left to the right, the > > >>> screen cursor moves accordingly, but the right border of the screen is > > >>> reached when the stylus is in the middle of the drawing tablet. Maybe, > > >>> for some strange reason, my drawing tablet considers there are two > > >>> screens and not a single one. How can we test that? > > >> > > >> The table knows nothing. :-) It has a certain range of values and the > > >> input layer takes that and the display size and should map the values > > >> accordingly. So something is going wrong and that's what I'm hoping to > > >> find out with the hidviz program. > > > > > > Thanks, Samuel. When the stylus is on the middle of my drawing tablet, > > > > > > ABS-X = 30693 (approximately). > > > > What happens as you move further to the right? Try moving slowly across > > the middle. > > Thanks, Samuel. Please, see below. > > > > When the stylus is on the lower right corner, hidviz padding input shows > > > > > > X = 2 and Y=2. > > > > > > From hiviz, I get yet the following: > > > > > > -- > > > Usage Page (Digitizer) > > > Usage (Pen) > > > Collection (Application) > > > > Is this the same section that you see active values in? For my tablet, > > the active values are in this section: > > Usage Page (Generic Desktop) > > Usage (Mouse) > > Collection (Application) > >Report ID (9) > >Usage (Pointer) > >Collection (Physical) > > > > Do you have that section? If so, what does it have in it? > > I have the following: > > - > Usage Page (Generic Desktop) > Usage (Mouse) > Collection (Application) > Report ID (1) > Usage (Pointer) > Collection (Physical) > Usage Page (Button) > Usage Minimum (Button 1) > Usage Maximum (Button 5) > Logical minimum (0) > Logical maximum (1) > Report count (5) > Report size (1) > Item > Report count (1) > Report size (3) > Item > Usage Page (Generic Desktop) > Usage (X) > Usage (Y) > Logical minimum (-2047) > Logical maximum (2047) > Report size (12) > Report count (2) > Item > Usage (Wheel) > Logical minimum (-127) > Logical maximum (127) > Report size (8) > Report count (1) > Item > Usage Page (Consumer) > Usage (AC Flip Vertical) > Report count (1) > Item > End Collection > End Collection > - > Event: time 1631875096.010113, type 3 (EV_ABS), code 0 (ABS_X), value 32767 > Event: time 1631875096.010113, type 3 (EV_ABS), code 1 (ABS_Y), value 22055 > Event: time 1631875096.010113, -- SYN_REPORT > Event: time 1631875096.110119, type 3 (EV_ABS), code 1 (ABS_Y), value 22037 > Event: time 1631875096.110119, -- SYN_REPORT > Event: time 1631875096.124127, type 3 (EV_ABS), code 1 (ABS_Y), value 22016 > Event: time 1631875096.124127, -- SYN_REPORT > Event: time 1631875096.136106, type 3 (EV_ABS), code 1 (ABS_Y), value 21999 > Event: time 1631875096.136106, -- SYN_REPORT > Event: time 1631875096.150107, type 3 (EV_ABS), code 1 (ABS_Y), value 21977 > Event: time 1631875096.150107, -- SYN_REPORT > [...] > Event: time 1631875100.124584, -- SYN_REPORT > Event: time 1631875100.130573, type 3 (EV_ABS), code 1 (ABS_Y), value 21562 > Event: time 1631875100.130573, -- SYN_REPORT > Event: time 1631875100.136587, type 3 (EV_ABS), code 1 (ABS_Y), value 21570 > Event: time 1631875100.136587, -- SYN_REPORT > Event: time 1631875100.194589, type 3 (EV_ABS), code 1 (ABS_Y), value 21587 I have meanwhile filed a bug regarding this issue: https://bugzilla.redhat.com/show_bug.cgi?id=2005575 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 Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: Setting the active area of drawing tablet
On Fri, Sep 17, 2021 at 8:34 AM Samuel Sieb wrote: > > >>> While sliding the stylus horizontally from the left to the right, the > >>> screen cursor moves accordingly, but the right border of the screen is > >>> reached when the stylus is in the middle of the drawing tablet. Maybe, > >>> for some strange reason, my drawing tablet considers there are two > >>> screens and not a single one. How can we test that? > >> > >> The table knows nothing. :-) It has a certain range of values and the > >> input layer takes that and the display size and should map the values > >> accordingly. So something is going wrong and that's what I'm hoping to > >> find out with the hidviz program. > > > > Thanks, Samuel. When the stylus is on the middle of my drawing tablet, > > > > ABS-X = 30693 (approximately). > > What happens as you move further to the right? Try moving slowly across > the middle. Thanks, Samuel. Please, see below. > > When the stylus is on the lower right corner, hidviz padding input shows > > > > X = 2 and Y=2. > > > > From hiviz, I get yet the following: > > > > -- > > Usage Page (Digitizer) > > Usage (Pen) > > Collection (Application) > > Is this the same section that you see active values in? For my tablet, > the active values are in this section: > Usage Page (Generic Desktop) > Usage (Mouse) > Collection (Application) >Report ID (9) >Usage (Pointer) >Collection (Physical) > > Do you have that section? If so, what does it have in it? I have the following: - Usage Page (Generic Desktop) Usage (Mouse) Collection (Application) Report ID (1) Usage (Pointer) Collection (Physical) Usage Page (Button) Usage Minimum (Button 1) Usage Maximum (Button 5) Logical minimum (0) Logical maximum (1) Report count (5) Report size (1) Item Report count (1) Report size (3) Item Usage Page (Generic Desktop) Usage (X) Usage (Y) Logical minimum (-2047) Logical maximum (2047) Report size (12) Report count (2) Item Usage (Wheel) Logical minimum (-127) Logical maximum (127) Report size (8) Report count (1) Item Usage Page (Consumer) Usage (AC Flip Vertical) Report count (1) Item End Collection End Collection - Event: time 1631875096.010113, type 3 (EV_ABS), code 0 (ABS_X), value 32767 Event: time 1631875096.010113, type 3 (EV_ABS), code 1 (ABS_Y), value 22055 Event: time 1631875096.010113, -- SYN_REPORT Event: time 1631875096.110119, type 3 (EV_ABS), code 1 (ABS_Y), value 22037 Event: time 1631875096.110119, -- SYN_REPORT Event: time 1631875096.124127, type 3 (EV_ABS), code 1 (ABS_Y), value 22016 Event: time 1631875096.124127, -- SYN_REPORT Event: time 1631875096.136106, type 3 (EV_ABS), code 1 (ABS_Y), value 21999 Event: time 1631875096.136106, -- SYN_REPORT Event: time 1631875096.150107, type 3 (EV_ABS), code 1 (ABS_Y), value 21977 Event: time 1631875096.150107, -- SYN_REPORT [...] Event: time 1631875100.124584, -- SYN_REPORT Event: time 1631875100.130573, type 3 (EV_ABS), code 1 (ABS_Y), value 21562 Event: time 1631875100.130573, -- SYN_REPORT Event: time 1631875100.136587, type 3 (EV_ABS), code 1 (ABS_Y), value 21570 Event: time 1631875100.136587, -- SYN_REPORT Event: time 1631875100.194589, type 3 (EV_ABS), code 1 (ABS_Y), value 21587 ___ 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: Setting the active area of drawing tablet
On Tue, Sep 14, 2021 at 2:34 PM Paul Smith wrote: > > > > While sliding the stylus horizontally from the left to the right, the > > > screen cursor moves accordingly, but the right border of the screen is > > > reached when the stylus is in the middle of the drawing tablet. Maybe, > > > for some strange reason, my drawing tablet considers there are two > > > screens and not a single one. How can we test that? > > > > The table knows nothing. :-) It has a certain range of values and the > > input layer takes that and the display size and should map the values > > accordingly. So something is going wrong and that's what I'm hoping to > > find out with the hidviz program. > > Thanks, Samuel. When the stylus is on the middle of my drawing tablet, > > ABS-X = 30693 (approximately). > > When the stylus is on the lower right corner, hidviz padding input shows > > X = 2 and Y=2. > > From hiviz, I get yet the following: > > -- > Usage Page (Digitizer) > Usage (Pen) > Collection (Application) > Report ID (10) > Usage (Stylus) > Collection (Physical) > Usage (Tip Switch) > Usage (Barrel Switch) > Usage (Eraser) > Usage (Invert) > Usage (Secondary Tip Switch) > Usage (Barrel Switch) > Logical minimum (0) > Logical maximum (1) > Report size (1) > Report count (6) > Item > Usage (In Range) > Report size (1) > Report count (1) > Item > Item > Usage Page (Generic Desktop) > Usage (X) > Usage (Y) > Unit exponent (-3) > Unit (51) > Logical maximum (32767) > Physical minimum (0) > Physical maximum (2048) > Report size (16) > Report count (2) > Item > Usage Page (Digitizer) > Usage (Tip Pressure) > Logical maximum (8191) > Report size (16) > Report count (1) > Item > End Collection > End Collection Does the above give you some clue, Samuel? 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 Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: Setting the active area of drawing tablet
On Tue, Sep 14, 2021 at 8:37 AM Samuel Sieb wrote: > > > While sliding the stylus horizontally from the left to the right, the > > screen cursor moves accordingly, but the right border of the screen is > > reached when the stylus is in the middle of the drawing tablet. Maybe, > > for some strange reason, my drawing tablet considers there are two > > screens and not a single one. How can we test that? > > The table knows nothing. :-) It has a certain range of values and the > input layer takes that and the display size and should map the values > accordingly. So something is going wrong and that's what I'm hoping to > find out with the hidviz program. Thanks, Samuel. When the stylus is on the middle of my drawing tablet, ABS-X = 30693 (approximately). When the stylus is on the lower right corner, hidviz padding input shows X = 2 and Y=2. From hiviz, I get yet the following: -- Usage Page (Digitizer) Usage (Pen) Collection (Application) Report ID (10) Usage (Stylus) Collection (Physical) Usage (Tip Switch) Usage (Barrel Switch) Usage (Eraser) Usage (Invert) Usage (Secondary Tip Switch) Usage (Barrel Switch) Logical minimum (0) Logical maximum (1) Report size (1) Report count (6) Item Usage (In Range) Report size (1) Report count (1) Item Item Usage Page (Generic Desktop) Usage (X) Usage (Y) Unit exponent (-3) Unit (51) Logical maximum (32767) Physical minimum (0) Physical maximum (2048) Report size (16) Report count (2) Item Usage Page (Digitizer) Usage (Tip Pressure) Logical maximum (8191) Report size (16) Report count (1) Item End Collection End Collection ___ 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: Setting the active area of drawing tablet
On Mon, Sep 13, 2021 at 11:44 PM Samuel Sieb wrote: > > >> Now if you move the stylus to all the corners, what range of values do > >> you get? > > > > Samuel: When I move the stylus on the right-hand side of the tablet no > > ABS-X coordinate is reported; only ABS-Y keeps changing. This may be > > the problem, but I do not know how to solve it. > > What is the maximum value it gets to? Also, do you mean that there's > only an ABS-Y in the packet? It sounds like either the tablet isn't > reporting correctly or the kernel hid driver is interpreting it > incorrectly. Are there any relevant messages in the journal. > > Something I just discovered is an application called "hidviz". It > directly talks to the device over the HID interface and shows what it > finds. Try running it and select the interface for the stylus. Copy > the output from the Descriptor View and then watch the values in the > Device View as you move the stylus around, particularly in the right side. Thanks, Samuel. I do not have the drawing tablet here where I am now, but later on I will report the results given by hidviz. While sliding the stylus horizontally from the left to the right, the screen cursor moves accordingly, but the right border of the screen is reached when the stylus is in the middle of the drawing tablet. Maybe, for some strange reason, my drawing tablet considers there are two screens and not a single one. How can we test that? 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 Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: Setting the active area of drawing tablet
On Mon, Sep 13, 2021 at 10:32 PM Samuel Sieb wrote: > > > Select the device event number [0-19]: 5 > > Input driver version is 1.0.1 > > Input device ID: bus 0x3 vendor 0x6161 product 0x4d15 version 0x111 > > Input device name: "LetSketch LetSketch" > > Supported events: > >Event type 0 (EV_SYN) > >Event type 1 (EV_KEY) > > Event code 320 (BTN_TOOL_PEN) > > Event code 321 (BTN_TOOL_RUBBER) > > Event code 330 (BTN_TOUCH) > > Event code 331 (BTN_STYLUS) > >Event type 3 (EV_ABS) > > Event code 0 (ABS_X) > >Value 0 > >Min0 > >Max32767 > >Resolution 152 > > Event code 1 (ABS_Y) > >Value 0 > >Min0 > >Max32767 > >Resolution 244 > > Now if you move the stylus to all the corners, what range of values do > you get? Samuel: When I move the stylus on the right-hand side of the tablet no ABS-X coordinate is reported; only ABS-Y keeps changing. This may be the problem, but I do not know how to solve it. When I move the stylus on the left-hand side of the tablet, both coordinates (ABS-X and ABS-Y) keep changing! 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 Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: Setting the active area of drawing tablet
On Mon, Sep 13, 2021 at 10:14 PM Samuel Sieb wrote: > > >> Check the min and max numbers for yours and then move the stylus to the > >> corners and see if the position matches. The input system should > >> automatically scale the resulting values to match your display. Do you > >> have more than one screen? > > > > Thanks, again, Samuel. I have only one screen. > > > > By sliding my hand with the pen on the tablet, I reach the right > > border of the screen when I am in the middle of my drawing tablet. > > Ideally, the screen border should be reached only when the pen gets > > close to the tablet border -- that is what I mean. > > Ok, then it sounds like something is getting the wrong dimensions. Are > you using Gnome? > > > My "evtest" does not report Event type 3 (EV_ABS). Please, see below > > what is reported: > > > > Select the device event number [0-19]: 18 > > There must be another device for it then. Maybe 19? Thanks, Samuel. My fault. The correct one reports the following: Select the device event number [0-19]: 5 Input driver version is 1.0.1 Input device ID: bus 0x3 vendor 0x6161 product 0x4d15 version 0x111 Input device name: "LetSketch LetSketch" Supported events: Event type 0 (EV_SYN) Event type 1 (EV_KEY) Event code 320 (BTN_TOOL_PEN) Event code 321 (BTN_TOOL_RUBBER) Event code 330 (BTN_TOUCH) Event code 331 (BTN_STYLUS) Event type 3 (EV_ABS) Event code 0 (ABS_X) Value 0 Min0 Max32767 Resolution 152 Event code 1 (ABS_Y) Value 0 Min0 Max32767 Resolution 244 Event code 24 (ABS_PRESSURE) Value 0 Min0 Max 8191 Event type 4 (EV_MSC) Event code 4 (MSC_SCAN) Properties: Property type 1 (INPUT_PROP_DIRECT) Testing ... (interrupt to exit) ___ 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: Setting the active area of drawing tablet
On Mon, Sep 13, 2021 at 8:27 PM Samuel Sieb wrote: > > > The active area of my new drawing tablet is half of the available one. > > How can one set the active area to full? > > Can you explain in more detail what you mean? > > Here's something to test. Run "evtest" and pick the tablet. Before you > do anything, there should be a list of what it supports. For example, > part of mine shows this: >Event type 3 (EV_ABS) > Event code 0 (ABS_X) >Value 13067 >Min0 >Max32767 >Resolution 323 > Event code 1 (ABS_Y) >Value 19156 >Min0 >Max32767 >Resolution 430 > > Check the min and max numbers for yours and then move the stylus to the > corners and see if the position matches. The input system should > automatically scale the resulting values to match your display. Do you > have more than one screen? Thanks, again, Samuel. I have only one screen. By sliding my hand with the pen on the tablet, I reach the right border of the screen when I am in the middle of my drawing tablet. Ideally, the screen border should be reached only when the pen gets close to the tablet border -- that is what I mean. My "evtest" does not report Event type 3 (EV_ABS). Please, see below what is reported: Select the device event number [0-19]: 18 Input driver version is 1.0.1 Input device ID: bus 0x3 vendor 0x6161 product 0x4d15 version 0x111 Input device name: "LetSketch LetSketch" Supported events: Event type 0 (EV_SYN) Event type 1 (EV_KEY) Event code 1 (KEY_ESC) Event code 2 (KEY_1) Event code 3 (KEY_2) Event code 4 (KEY_3) Event code 5 (KEY_4) Event code 6 (KEY_5) Event code 7 (KEY_6) Event code 8 (KEY_7) Event code 9 (KEY_8) Event code 10 (KEY_9) Event code 11 (KEY_0) Event code 12 (KEY_MINUS) Event code 13 (KEY_EQUAL) Event code 14 (KEY_BACKSPACE) Event code 15 (KEY_TAB) Event code 16 (KEY_Q) Event code 17 (KEY_W) Event code 18 (KEY_E) Event code 19 (KEY_R) Event code 20 (KEY_T) Event code 21 (KEY_Y) Event code 22 (KEY_U) Event code 23 (KEY_I) Event code 24 (KEY_O) Event code 25 (KEY_P) Event code 26 (KEY_LEFTBRACE) Event code 27 (KEY_RIGHTBRACE) Event code 28 (KEY_ENTER) Event code 29 (KEY_LEFTCTRL) Event code 30 (KEY_A) Event code 31 (KEY_S) Event code 32 (KEY_D) Event code 33 (KEY_F) Event code 34 (KEY_G) Event code 35 (KEY_H) Event code 36 (KEY_J) Event code 37 (KEY_K) Event code 38 (KEY_L) Event code 39 (KEY_SEMICOLON) Event code 40 (KEY_APOSTROPHE) Event code 41 (KEY_GRAVE) Event code 42 (KEY_LEFTSHIFT) Event code 43 (KEY_BACKSLASH) Event code 44 (KEY_Z) Event code 45 (KEY_X) Event code 46 (KEY_C) Event code 47 (KEY_V) Event code 48 (KEY_B) Event code 49 (KEY_N) Event code 50 (KEY_M) Event code 51 (KEY_COMMA) Event code 52 (KEY_DOT) Event code 53 (KEY_SLASH) Event code 54 (KEY_RIGHTSHIFT) Event code 55 (KEY_KPASTERISK) Event code 56 (KEY_LEFTALT) Event code 57 (KEY_SPACE) Event code 58 (KEY_CAPSLOCK) Event code 59 (KEY_F1) Event code 60 (KEY_F2) Event code 61 (KEY_F3) Event code 62 (KEY_F4) Event code 63 (KEY_F5) Event code 64 (KEY_F6) Event code 65 (KEY_F7) Event code 66 (KEY_F8) Event code 67 (KEY_F9) Event code 68 (KEY_F10) Event code 69 (KEY_NUMLOCK) Event code 70 (KEY_SCROLLLOCK) Event code 71 (KEY_KP7) Event code 72 (KEY_KP8) Event code 73 (KEY_KP9) Event code 74 (KEY_KPMINUS) Event code 75 (KEY_KP4) Event code 76 (KEY_KP5) Event code 77 (KEY_KP6) Event code 78 (KEY_KPPLUS) Event code 79 (KEY_KP1) Event code 80 (KEY_KP2) Event code 81 (KEY_KP3) Event code 82 (KEY_KP0) Event code 83 (KEY_KPDOT) Event code 86 (KEY_102ND) Event code 87 (KEY_F11) Event code 88 (KEY_F12) Event code 96 (KEY_KPENTER) Event code 97 (KEY_RIGHTCTRL) Event code 98 (KEY_KPSLASH) Event code 99 (KEY_SYSRQ) Event code 100 (KEY_RIGHTALT) Event code 102 (KEY_HOME) Event code 103 (KEY_UP) Event code 104 (KEY_PAGEUP) Event code 105 (KEY_LEFT) Event code 106 (KEY_RIGHT) Event code 107 (KEY_END) Event code 108 (KEY_DOWN) Event code 109 (KEY_PAGEDOWN) Event code 110 (KEY_INSERT) Event code 111 (KEY_DELETE) Event code 119 (KEY_PAUSE) Event code 125 (KEY_LEFTMETA) Event code 126 (KEY_RIGHTMETA) Event code 127 (KEY_COMPOSE) Event type 4 (EV_MSC) Event code 4 (MSC_SCAN) Event type 17 (EV_LED) Event code 0 (LED_NUML) state 1 Event code 1 (LED_CAPSL) state 0 Event code 2 (LED_SCROLLL) state 0 Event code 3 (LED_COMPOSE) state 0 Event code 4 (LED_KANA) state 0 Key repeat handling: Repeat type 20 (EV_REP) Repeat code 0 (REP_DELAY) Value250 Repeat code 1 (REP_PERIOD) Value 33 Prope
Re: Configuring drawing tablet
On Mon, Sep 13, 2021 at 8:11 PM Samuel Sieb wrote: > > On 2021-09-13 11:16 a.m., Paul Smith wrote: > > Thanks, Samuel. Yes, it causes mouse clicks. > > I assume you're happy with those. > > > "evtest" recognizes my drawing tablet, and when I successively hit the > > express keys I get the following: > > > > > > Event: time 1631556826.892457, type 4 (EV_MSC), code 4 (MSC_SCAN), value > > 700e0 > > So the buttons are sending key combinations. You probably don't want to > remap those globally, so I suggest using something like > https://github.com/kmonad/kmonad or https://github.com/rvaiya/keyd to > remap the keys. > keyd only remaps, but doesn't run scripts, so you would have to remap > the key to another one that you can use as a hotkey. > kmonad allows you to run scripts as well. Thanks, Samuel, it seems perfect! 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 Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Setting the active area of drawing tablet
Dear All, The active area of my new drawing tablet is half of the available one. How can one set the active area to full? Thanks in advance, 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 Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: Configuring drawing tablet
On Mon, Sep 13, 2021 at 7:08 PM Samuel Sieb wrote: > > > I have recently bought a drawing tablet, which does not come with any > > Linux device driver. > > > > It works perfectly even without any device driver. However, I would > > like to associate a script to each of the tablet buttons. I guess that > > whenever a button is pressed, a signal of such an occurrence can be > > captured by Fedora, but I do not know how. > > Does it cause mouse clicks? > > To find out what events are happening, you can install "evtest". If you > run "evtest" with no arguments, it will give you a list of available > devices. See which one(s) match your tablet and select it. Click the > buttons and see what happens. Thanks, Samuel. Yes, it causes mouse clicks. "evtest" recognizes my drawing tablet, and when I successively hit the express keys I get the following: Event: time 1631556826.892457, type 4 (EV_MSC), code 4 (MSC_SCAN), value 700e0 Event: time 1631556826.892457, type 1 (EV_KEY), code 29 (KEY_LEFTCTRL), value 1 Event: time 1631556826.892457, type 4 (EV_MSC), code 4 (MSC_SCAN), value 70013 Event: time 1631556826.892457, type 1 (EV_KEY), code 25 (KEY_P), value 1 Event: time 1631556826.892457, -- SYN_REPORT Event: time 1631556826.894445, type 4 (EV_MSC), code 4 (MSC_SCAN), value 700e0 Event: time 1631556826.894445, type 1 (EV_KEY), code 29 (KEY_LEFTCTRL), value 0 Event: time 1631556826.894445, type 4 (EV_MSC), code 4 (MSC_SCAN), value 70013 Event: time 1631556826.894445, type 1 (EV_KEY), code 25 (KEY_P), value 0 Event: time 1631556826.894445, -- SYN_REPORT ^PEvent: time 1631556828.294629, type 4 (EV_MSC), code 4 (MSC_SCAN), value 700e0 Event: time 1631556828.294629, type 1 (EV_KEY), code 29 (KEY_LEFTCTRL), value 1 Event: time 1631556828.294629, type 4 (EV_MSC), code 4 (MSC_SCAN), value 70008 Event: time 1631556828.294629, type 1 (EV_KEY), code 18 (KEY_E), value 1 Event: time 1631556828.294629, -- SYN_REPORT Event: time 1631556828.296599, type 4 (EV_MSC), code 4 (MSC_SCAN), value 700e0 Event: time 1631556828.296599, type 1 (EV_KEY), code 29 (KEY_LEFTCTRL), value 0 Event: time 1631556828.296599, type 4 (EV_MSC), code 4 (MSC_SCAN), value 70008 Event: time 1631556828.296599, type 1 (EV_KEY), code 18 (KEY_E), value 0 Event: time 1631556828.296599, -- SYN_REPORT ^EEvent: time 1631556829.256745, type 4 (EV_MSC), code 4 (MSC_SCAN), value 700e0 Event: time 1631556829.256745, type 1 (EV_KEY), code 29 (KEY_LEFTCTRL), value 1 Event: time 1631556829.256745, type 4 (EV_MSC), code 4 (MSC_SCAN), value 7000f Event: time 1631556829.256745, type 1 (EV_KEY), code 38 (KEY_L), value 1 Event: time 1631556829.256745, -- SYN_REPORT Event: time 1631556829.258738, type 4 (EV_MSC), code 4 (MSC_SCAN), value 700e0 Event: time 1631556829.258738, type 1 (EV_KEY), code 29 (KEY_LEFTCTRL), value 0 Event: time 1631556829.258738, type 4 (EV_MSC), code 4 (MSC_SCAN), value 7000f Event: time 1631556829.258738, type 1 (EV_KEY), code 38 (KEY_L), value 0 Event: time 1631556829.258738, -- SYN_REPORT ^LEvent: time 1631556830.196848, type 4 (EV_MSC), code 4 (MSC_SCAN), value 7004b Event: time 1631556830.196848, type 1 (EV_KEY), code 104 (KEY_PAGEUP), value 1 Event: time 1631556830.196848, -- SYN_REPORT Event: time 1631556830.198836, type 4 (EV_MSC), code 4 (MSC_SCAN), value 7004b Event: time 1631556830.198836, type 1 (EV_KEY), code 104 (KEY_PAGEUP), value 0 Event: time 1631556830.198836, -- SYN_REPORT ^[[5~Event: time 1631556831.106955, type 4 (EV_MSC), code 4 (MSC_SCAN), value 7004e Event: time 1631556831.106955, type 1 (EV_KEY), code 109 (KEY_PAGEDOWN), value 1 Event: time 1631556831.106955, -- SYN_REPORT ^[[6~Event: time 1631556831.108925, type 4 (EV_MSC), code 4 (MSC_SCAN), value 7004e Event: time 1631556831.108925, type 1 (EV_KEY), code 109 (KEY_PAGEDOWN), value 0 Event: time 1631556831.108925, -- SYN_REPORT ___ 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
Configuring drawing tablet
Dear All, I have recently bought a drawing tablet, which does not come with any Linux device driver. It works perfectly even without any device driver. However, I would like to associate a script to each of the tablet buttons. I guess that whenever a button is pressed, a signal of such an occurrence can be captured by Fedora, but I do not know how. Could someone please help me? Thanks in advance, 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 Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: Fedora 34 boot screen
On Thu, Jul 29, 2021 at 2:18 PM Paul Smith wrote: > > > There's a fix in the updates-testing repo: > > https://bodhi.fedoraproject.org/updates/FEDORA-2021-7b6767f8af > > > > It should land in the stable repo tonight. > > Unfortunately, that does not fix the problem, in my case: > > --- > $ systemd-analyze blame > 1min 31.106s dracut-initqueue.service > 6.914s NetworkManager-wait-online.service > 3.535s akmods.service > 3.283s firewalld.service > --- It was needed to regenerate the initrd with "sudo dracut -f": https://bugzilla.redhat.com/show_bug.cgi?id=1976653#c75 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 Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: Fedora 34 boot screen
On Thu, Jul 29, 2021 at 1:53 PM Ben Cotton wrote: > > Thanks, Barry, for the tip. I hope this bug is fixed soon! > > > There's a fix in the updates-testing repo: > https://bodhi.fedoraproject.org/updates/FEDORA-2021-7b6767f8af > > It should land in the stable repo tonight. Unfortunately, that does not fix the problem, in my case: --- $ systemd-analyze blame 1min 31.106s dracut-initqueue.service 6.914s NetworkManager-wait-online.service 3.535s akmods.service 3.283s firewalld.service --- 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 Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: Fedora 34 boot screen
On Thu, Jul 29, 2021 at 1:53 PM Ben Cotton wrote: > > > Thanks, Barry, for the tip. I hope this bug is fixed soon! > > > There's a fix in the updates-testing repo: > https://bodhi.fedoraproject.org/updates/FEDORA-2021-7b6767f8af > > It should land in the stable repo tonight. Great, Ben! Thanks! 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 Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: Fedora 34 boot screen
On Thu, Jul 29, 2021 at 8:23 AM Barry Scott wrote: > > >> Moreover, the booting duration seems to be longer than before. > >> > >> Any reason for that? > >> > > You can check what's causing the delay with: > >systemd-analyze blame > > > > I'm guessing it's probably going to show dracut-initqueue.service at > > the top, which is probably this bug: > > https://bugzilla.redhat.com/show_bug.cgi?id=1985205 > > I found this related ticket: > > https://bugzilla.redhat.com/show_bug.cgi?id=1976653 > > I followed the clue about resume= on the kernel command line. > > When I removed resume= the problem was fixed for the F34 that > had the 90 second pause. Thanks, Barry, for the tip. I hope this bug is fixed soon! 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 Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: Left-hand mouse click sometimes not recognized
On Wed, Jul 28, 2021 at 5:53 AM Tim via users wrote: > > Paul Smith, > >> From time to time, I have to click several times to get a left-hand > >> mouse click recognized. Any ideas? > > Tom Horsley: > > Busted moving parts in mouse would be my guess as most likely. > > I've come across many a mouse where the soldering of the switch to the > printed circuit board has mechanically failed, either through just the > normal use of the mouse, or when mice get dropped and land on a button. > > That's easily fixed by resoldering it. But if you don't have the > tools, and the particular mouse isn't worth the effort of trying to fix > it, it's usually far easier just to get a new one. Thanks to all who have answered! My surprise is that I bought my mouse not so long ago (less than one year). 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 Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: Left-hand mouse click sometimes not recognized
On Tue, Jul 27, 2021 at 8:38 PM Paul Smith wrote: > > From time to time, I have to click several times to get a left-hand > mouse click recognized. Any ideas? Let me add that my mouse is a wired USB one. 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 Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Left-hand mouse click sometimes not recognized
Dear All, From time to time, I have to click several times to get a left-hand mouse click recognized. Any ideas? Thanks in advance, 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 Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: Fedora 34 boot screen
On Tue, Jul 27, 2021 at 5:05 PM Patrick O'Callaghan wrote: > > > > Since a few weeks ago, when I boot my Fedora 34 machine, I get a > > > three > > > animated square dots as a boot screen like the following: > > > > > > https://i.stack.imgur.com/7hFp0.png > > > > > > Moreover, the booting duration seems to be longer than before. > > > > > > Any reason for that? > > > > Might be worth looking through the archives for a recent similar case: > > > > https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org/thread/B2WPG4R74ONUYVVWHXL4NGO5XSP7BD2W/ > > > > See if the solutions there help? > > This is what worked for me (from the same thread): > > https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org/message/XQQAI5XMPZQSAUVRNFQ5LQLV3LQV2ULD/ Thanks, Patrick. Let us see if meanwhile the bug that Ben Cotton mentions is fixed. 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 Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: Fedora 34 boot screen
On Tue, Jul 27, 2021 at 3:39 PM Ben Cotton wrote: > > > Moreover, the booting duration seems to be longer than before. > > > > Any reason for that? > > > You can check what's causing the delay with: > systemd-analyze blame > > I'm guessing it's probably going to show dracut-initqueue.service at > the top, which is probably this bug: > https://bugzilla.redhat.com/show_bug.cgi?id=1985205 Thanks, Ben. It seems you are right: --- $ systemd-analyze blame 1min 31.132s dracut-initqueue.service 12.693s dnf-makecache.service 6.748s NetworkManager-wait-online.service 3.166s akmods.service 2.896s firewalld.service ... --- ___ 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
Fedora 34 boot screen
Dear All, Since a few weeks ago, when I boot my Fedora 34 machine, I get a three animated square dots as a boot screen like the following: https://i.stack.imgur.com/7hFp0.png Moreover, the booting duration seems to be longer than before. Any reason for that? Thanks in advance, 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 Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Using the logs to detect a problem with webcam on OBS-Studio
Dear All, After having upgraded from F33 to F34, my webcam was still detected by OBS-Studio. However, it did not display any image -- only a black rectangle. It took me a lot of time to find out the cause: The resolution of my webcam on OBS-Studio was configured as "Leave unchanged" and it should be "1280x720". So my question is: Could this problem have been spotted in some logs? Thanks in advance, 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 Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: Virtual camera on OBS-Studio not working
On Thu, Apr 29, 2021 at 4:28 PM Paul Smith wrote: > > Solved! I will later describe the solution I found for my problem, as > I am now in a hurry. The problem appears to be related to OBS-Studio. After having run the following command, the reported problem disappeared: ffmpeg -i /dev/video1 -f v4l2 /dev/video0 Therefore, I suspect that OBS-Studio does not issue a command like the above -- one has to do that manually. 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 Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: Virtual camera on OBS-Studio not working
Solved! I will later describe the solution I found for my problem, as I am now in a hurry. Paul On Thu, Apr 29, 2021 at 4:18 PM Paul Smith wrote: > > On Thu, Apr 29, 2021 at 4:12 PM Paul Smith wrote: > > > > On Thu, Apr 29, 2021 at 3:59 PM Jonathan Billings > > wrote: > > > > > > > --- > > > > [ 263.923694] EDAC amd64: Node 0: DRAM ECC disabled. > > > > [ 265.686950] systemd-sysv-generator[37295]: SysV service > > > > '/etc/rc.d/init.d/livesys' lacks a native systemd unit file. > > > > Automatically generating a unit file for compatibility. Please update > > > > package to include a native systemd unit file, in order to make it > > > > more safe and robust. > > > > [ 265.686995] systemd-sysv-generator[37295]: SysV service > > > > '/etc/rc.d/init.d/livesys-late' lacks a native systemd unit file. > > > > Automatically generating a unit file for compatibility. Please update > > > > package to include a native systemd unit file, in order to make it > > > > more safe and robust. > > > > [ 366.970723] uvcvideo: Failed to query (SET_CUR) UVC control 10 on > > > > unit 2: -32 (exp. 2). > > > > [ 366.987741] uvcvideo: Failed to query (SET_CUR) UVC control 4 on > > > > unit 1: -32 (exp. 4). > > > > --- > > > > > > I don't see anything in particular wrong with that. The uvcvideo > > > output is probably for your real video device. > > > > > > Do you see the v4l2loopback device in v4l2-ctrl? For example, I > > > loaded the rpmfusion package 'akmod-v4l2loopback' and enabled the > > > akmods service, and now I see: > > > > > > $ v4l2-ctl --list-devices > > > OBS Virtual Camera (platform:v4l2loopback-000): > > > /dev/video0 > > > > Thanks, Jonathan. In my case, I get: > > > > $ v4l2-ctl --list-devices > > OBS Virtual Camera (platform:v4l2loopback-000): > > /dev/video0 > > > > EasyCamera 5M: EasyCamera 5M (usb-:01:00.0-7): > > /dev/video2 > > /dev/video3 > > $ > > This may be related: > > -- > $ ffmpeg -i /dev/video2 -f v4l2 /dev/video4 > ffmpeg version 4.4 Copyright (c) 2000-2021 the FFmpeg developers > built with gcc 11 (GCC) > configuration: --prefix=/usr --bindir=/usr/bin > --datadir=/usr/share/ffmpeg --docdir=/usr/share/doc/ffmpeg > --incdir=/usr/include/ffmpeg --libdir=/usr/lib64 > --mandir=/usr/share/man --arch=x86_64 --optflags='-O2 -flto=auto > -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall > -Werror=format-security -Wp,-D_FORTIFY_SOURCE=2 > -Wp,-D_GLIBCXX_ASSERTIONS > -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 > -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 > -m64 -mtune=generic -fasynchronous-unwind-tables > -fstack-clash-protection -fcf-protection' > --extra-ldflags='-Wl,-z,relro -Wl,--as-needed -Wl,-z,now > -specs=/usr/lib/rpm/redhat/redhat-hardened-ld ' --extra-cflags=' > -I/usr/include/rav1e' --enable-libopencore-amrnb > --enable-libopencore-amrwb --enable-libvo-amrwbenc --enable-version3 > --enable-bzlib --disable-crystalhd --enable-fontconfig --enable-frei0r > --enable-gcrypt --enable-gnutls --enable-ladspa --enable-libaom > --enable-libdav1d --enable-libass --enable-libbluray --enable-libcdio > --enable-libdrm --enable-libjack --enable-libfreetype > --enable-libfribidi --enable-libgsm --enable-libmp3lame > --enable-libmysofa --enable-nvenc --enable-openal --enable-opencl > --enable-opengl --enable-libopenjpeg --enable-libopenmpt > --enable-libopus --enable-libpulse --enable-librsvg --enable-librav1e > --enable-libsmbclient --enable-version3 --enable-libsoxr > --enable-libspeex --enable-libsrt --enable-libssh --enable-libsvtav1 > --enable-libtheora --enable-libvorbis --enable-libv4l2 > --enable-libvidstab --enable-libvmaf --enable-version3 > --enable-vapoursynth --enable-libvpx --enable-vulkan > --enable-libglslang --enable-libx264 --enable-libx265 --enable-libxvid > --enable-libxml2 --enable-libzimg --enable-libzvbi --enable-lv2 > --enable-avfilter --enable-avresample --enable-libmodplug > --enable-postproc --enable-pthreads --disable-static --enable-shared > --enable-gpl --disable-debug --disable-stripping --shlibdir=/usr/lib64 > --enable-lto --enable-libmfx --enable-runtime-cpudetect > libavutil 56. 70.100 / 56. 70.100 > libavcodec 58.134.100 / 58.134.100 > libavformat58. 76.100 / 58. 76.100 > libavdevice58. 13.10
