Re: Gigabyte: "we cannot offer full support on Linux"
On Mon, 2022-05-16 at 19:02 -0400, Sam Varshavchik wrote: > One of their motherboards keeps locking up on me. After some back and > forth their last reply ended the discussion thread with a: > > # Since we do not fully support and validate Linux, we cannot offer full > # support on Linux. Please try a Windows base OS to check if you are still > # experiencing the same instability issue. I take issue with this on a customer service stand point. As the customer, it is NOT YOUR JOB to diagnose faulty hardware. Probably most of their customers would be unable to do that. You should be able to return non-working equipment and THEY should assess it. You should also be able to return it to the vendor without being hassled about it, nor being told to go back to the manufacturer instead (in my country, that's actually illegal to be fobbed off that way). Of course you mightn't trust them, and it's in your interests to do your own tests, first. But the obligation should be on THEM. When I've dealt with good companies, I've asked them about non-working equipment, they've given me a few simple to do "have you tried this?" questions, and when I confirmed I'd done what I could, they simply told me to bring it back. If they'd asked me to jump through hoops I would have given them a serve over it, but they didn't. I delightedly name one, Jaycar, as a company that will try their level best to get out of warranties, and act illegally about it. -- uname -rsvp Linux 3.10.0-1160.62.1.el7.x86_64 #1 SMP Tue Apr 5 16:57:59 UTC 2022 x86_64 Boilerplate: All unexpected mail to my mailbox is automatically deleted. I will only get to see the messages that are posted to the mailing list. ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: LibreOffice Base?
On Sun, 2022-05-15 at 10:30 -0800, Fred wrote: > I had to manually install the optional packages Likewise. The ones people commonly want, and are required for them to run are a basic installation. It will probably change depending on which spin you install. One might use the basic defaults, another might include more things for you. -- uname -rsvp Linux 3.10.0-1160.62.1.el7.x86_64 #1 SMP Tue Apr 5 16:57:59 UTC 2022 x86_64 Boilerplate: All unexpected mail to my mailbox is automatically deleted. I will only get to see the messages that are posted to the mailing list. ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: Gigabyte: "we cannot offer full support on Linux"
On 5/16/22 20:57, ToddAndMargo via users wrote: I almost forgot. When you freeze up, can you do a ? To get back out, do a At least for Gnome, the first terminal is F3 and back to your session is F2. F1 goes to the login screen. ___ 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: Shift+PrintScreen gone with F36?
On 5/16/22 22:07, stan via users wrote: On Mon, 16 May 2022 13:17:28 +0700 Frederic Muller wrote: Thank you, didn't see that link. Now that doesn't really fit my needs as I liked the (partial) screenshot saved automatically, avoiding to open a imaging application to get back the clipboard. I'll spare everyone the rant over great simple things going away... Who knows maybe we'll get back a way to have SHIFT+PrintScreen in GNOME 48, who knows? There is an application called spectacle that takes screenshots. In the configuration, there is a way to set keyboard shortcuts. Perhaps you can adapt it to do what you want? ___ Thank you. Wasn't aware of that, will install and play with it then. Fred ___ 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: Gigabyte: "we cannot offer full support on Linux"
On 5/16/22 18:30, ToddAndMargo via users wrote: On 5/16/22 18:17, ToddAndMargo via users wrote: On 5/16/22 16:02, Sam Varshavchik wrote: It's been a long time since I've encountered this kind of obtuseness. This is not new, but I thought that this kind of blindness was in the rear-view mirror. I guess not. One of their motherboards keeps locking up on me. After some back and forth their last reply ended the discussion thread with a: # Since we do not fully support and validate Linux, we cannot offer full # support on Linux. Please try a Windows base OS to check if you are still # experiencing the same instability issue. Just thought I'd mention it here, so that other DIYers might take this into consideration. Looking at their support page, it's listing new BIOS updates every month. Hi Sam V., If a motherboard can run Windows, it can run Linux. Not necessarily the other way around though. Windows has artificial blocks (8 & 9 gen processors and TPM modules). What you are experiencing is the atrocious customer service since the work-at-home started. Gigabyte and Intel a YUGE offenders. You got a "blow off" response. Anything to NOT answer and NOT help. What is unusual is that GIGABYTE actually answered back. I have a question into them as to the replacement for their W480M, which is no longer produced. The lazy so-and-so sent me back the advertising brochure for the W480M. When I called him on it, he would not budge. I did figure it out (C246M-WU4). When I asked Intel which processors supported on that motherboard supported ECC, they sent me all the processors. When I called him on it, he also would not budge. Ya, i3 and ECC, my aunt fanny. (I did eventually figure it out: it is their new "e" series xeon processors.) Business rule: relationships outlive transactions. These zero and blow off customer service companies better be darned careful or they will not have businesses after too long. So anyway, as a occasional system builder, I have found Gigabyte's motherboards to be of pretty good overall quality. Now providing you did not populate your motherboard with cheap memory, used processors, bargain SSD drives, here are some things to try. 1) download any of the Fedora Live Spins and dd them to a a 8+ GB flash drive. Boot off it. And torture the thing. If it does not freeze up, your hardware is okay, except for your hard drive. Then you dnf gsmartcontrol and test your hard drive with it. https://spins.fedoraproject.org/ # dd if=spin.iso of=/dev/sd[x] Sub appropriate names in the above. 2) if you are feeling really adventurous and have a spare hard drive kicking around, you could download and install Windows 10 (no TPM hassle) https://www.microsoft.com/en-us/software-download/windows10ISO and cut it to and 8+ GB flash drive with woeusb (Internet connection required): # dnf install WoeUSB # dd bs=4096 if=/dev/zero of=/dev/sd[x] # woeusb --device Win10_21H2_English_x64.iso /dev/sd[x] --target-filesystem NTFS or whatever the iso is called. You do not need a license for this. Windows will just not let you set a wall paper. Woopie-do. If you do not feel like installing Windows on a spare hard drive, disconnect your Linux drive, fire up the Windows installer and jet let it sit there. See if you freeze up. If it is your hardware, try substituting Kingston memory. Crucial if you absolutely you have to. For SSD Drive, I only recommend Samsung. They just work. No drama. And remember. You pay for what you get. Well, except for my advice! :-) HTH, -T Are all your fans working? Frozen fans on video cards are a YUGE cause of freeze ups. I almost forgot. When you freeze up, can you do a ? To get back out, do a ___ 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: Gigabyte: "we cannot offer full support on Linux"
On 5/16/22 18:43, Tom Horsley wrote: On Mon, 16 May 2022 18:30:10 -0700 ToddAndMargo via users wrote: Are all your fans working? Frozen fans on video cards are a YUGE cause of freeze ups. So is the nouveau driver :-(. I run nouveau on every new fedora install until the video and/or system locks up, then I install nvidia drivers from rpmfusion and never have any additional video problems. (In the latest install nouveau can't run X at all and picks the wrong resolution under wayland, so I didn't run it very long :-). Good point. A live of Xfce or MATE would be a great test as neither uses Wayland ___ 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: Gigabyte: "we cannot offer full support on Linux"
On Mon, 16 May 2022 18:32:29 -0700 ToddAndMargo via users wrote: > I have a bootable flash drive with DOS 6.22 on it > for upgrading bios'es Supermicro's motherboards. At least with motherboards all the ones I've had in the last few years can update directly from a usb stick with no dos/windows/anything required. ___ 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: Gigabyte: "we cannot offer full support on Linux"
On Mon, 16 May 2022 18:30:10 -0700 ToddAndMargo via users wrote: > Are all your fans working? Frozen fans on video > cards are a YUGE cause of freeze ups. So is the nouveau driver :-(. I run nouveau on every new fedora install until the video and/or system locks up, then I install nvidia drivers from rpmfusion and never have any additional video problems. (In the latest install nouveau can't run X at all and picks the wrong resolution under wayland, so I didn't run it very long :-). ___ 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: Gigabyte: "we cannot offer full support on Linux"
On 5/16/22 18:27, Tom Horsley wrote: On Mon, 16 May 2022 18:17:53 -0700 ToddAndMargo via users wrote: For SSD Drive, I only recommend Samsung. They just work. No drama. But if you need to update firmware on a samsung ssd you have to run their windows only utility (at least the last time I looked). I busted their chops on that one already. On the other hand, I have never had to upgrade their firmware. I have a bootable flash drive with DOS 6.22 on it for upgrading bios'es Supermicro's motherboards. These guys can be rather shortsighted. ___ 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: Gigabyte: "we cannot offer full support on Linux"
On 5/16/22 18:17, ToddAndMargo via users wrote: On 5/16/22 16:02, Sam Varshavchik wrote: It's been a long time since I've encountered this kind of obtuseness. This is not new, but I thought that this kind of blindness was in the rear-view mirror. I guess not. One of their motherboards keeps locking up on me. After some back and forth their last reply ended the discussion thread with a: # Since we do not fully support and validate Linux, we cannot offer full # support on Linux. Please try a Windows base OS to check if you are still # experiencing the same instability issue. Just thought I'd mention it here, so that other DIYers might take this into consideration. Looking at their support page, it's listing new BIOS updates every month. Hi Sam V., If a motherboard can run Windows, it can run Linux. Not necessarily the other way around though. Windows has artificial blocks (8 & 9 gen processors and TPM modules). What you are experiencing is the atrocious customer service since the work-at-home started. Gigabyte and Intel a YUGE offenders. You got a "blow off" response. Anything to NOT answer and NOT help. What is unusual is that GIGABYTE actually answered back. I have a question into them as to the replacement for their W480M, which is no longer produced. The lazy so-and-so sent me back the advertising brochure for the W480M. When I called him on it, he would not budge. I did figure it out (C246M-WU4). When I asked Intel which processors supported on that motherboard supported ECC, they sent me all the processors. When I called him on it, he also would not budge. Ya, i3 and ECC, my aunt fanny. (I did eventually figure it out: it is their new "e" series xeon processors.) Business rule: relationships outlive transactions. These zero and blow off customer service companies better be darned careful or they will not have businesses after too long. So anyway, as a occasional system builder, I have found Gigabyte's motherboards to be of pretty good overall quality. Now providing you did not populate your motherboard with cheap memory, used processors, bargain SSD drives, here are some things to try. 1) download any of the Fedora Live Spins and dd them to a a 8+ GB flash drive. Boot off it. And torture the thing. If it does not freeze up, your hardware is okay, except for your hard drive. Then you dnf gsmartcontrol and test your hard drive with it. https://spins.fedoraproject.org/ # dd if=spin.iso of=/dev/sd[x] Sub appropriate names in the above. 2) if you are feeling really adventurous and have a spare hard drive kicking around, you could download and install Windows 10 (no TPM hassle) https://www.microsoft.com/en-us/software-download/windows10ISO and cut it to and 8+ GB flash drive with woeusb (Internet connection required): # dnf install WoeUSB # dd bs=4096 if=/dev/zero of=/dev/sd[x] # woeusb --device Win10_21H2_English_x64.iso /dev/sd[x] --target-filesystem NTFS or whatever the iso is called. You do not need a license for this. Windows will just not let you set a wall paper. Woopie-do. If you do not feel like installing Windows on a spare hard drive, disconnect your Linux drive, fire up the Windows installer and jet let it sit there. See if you freeze up. If it is your hardware, try substituting Kingston memory. Crucial if you absolutely you have to. For SSD Drive, I only recommend Samsung. They just work. No drama. And remember. You pay for what you get. Well, except for my advice! :-) HTH, -T Are all your fans working? Frozen fans on video cards are a YUGE cause of freeze ups. ___ 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: Gigabyte: "we cannot offer full support on Linux"
On Mon, 16 May 2022 18:17:53 -0700 ToddAndMargo via users wrote: > For SSD Drive, I only recommend Samsung. They just > work. No drama. But if you need to update firmware on a samsung ssd you have to run their windows only utility (at least the last time I looked). ___ 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: Gigabyte: "we cannot offer full support on Linux"
On 5/16/22 16:02, Sam Varshavchik wrote: It's been a long time since I've encountered this kind of obtuseness. This is not new, but I thought that this kind of blindness was in the rear-view mirror. I guess not. One of their motherboards keeps locking up on me. After some back and forth their last reply ended the discussion thread with a: # Since we do not fully support and validate Linux, we cannot offer full # support on Linux. Please try a Windows base OS to check if you are still # experiencing the same instability issue. Just thought I'd mention it here, so that other DIYers might take this into consideration. Looking at their support page, it's listing new BIOS updates every month. Hi Sam V., If a motherboard can run Windows, it can run Linux. Not necessarily the other way around though. Windows has artificial blocks (8 & 9 gen processors and TPM modules). What you are experiencing is the atrocious customer service since the work-at-home started. Gigabyte and Intel a YUGE offenders. You got a "blow off" response. Anything to NOT answer and NOT help. What is unusual is that GIGABYTE actually answered back. I have a question into them as to the replacement for their W480M, which is no longer produced. The lazy so-and-so sent me back the advertising brochure for the W480M. When I called him on it, he would not budge. I did figure it out (C246M-WU4). When I asked Intel which processors supported on that motherboard supported ECC, they sent me all the processors. When I called him on it, he also would not budge. Ya, i3 and ECC, my aunt fanny. (I did eventually figure it out: it is their new "e" series xeon processors.) Business rule: relationships outlive transactions. These zero and blow off customer service companies better be darned careful or they will not have businesses after too long. So anyway, as a occasional system builder, I have found Gigabyte's motherboards to be of pretty good overall quality. Now providing you did not populate your motherboard with cheap memory, used processors, bargain SSD drives, here are some things to try. 1) download any of the Fedora Live Spins and dd them to a a 8+ GB flash drive. Boot off it. And torture the thing. If it does not freeze up, your hardware is okay, except for your hard drive. Then you dnf gsmartcontrol and test your hard drive with it. https://spins.fedoraproject.org/ # dd if=spin.iso of=/dev/sd[x] Sub appropriate names in the above. 2) if you are feeling really adventurous and have a spare hard drive kicking around, you could download and install Windows 10 (no TPM hassle) https://www.microsoft.com/en-us/software-download/windows10ISO and cut it to and 8+ GB flash drive with woeusb (Internet connection required): # dnf install WoeUSB # dd bs=4096 if=/dev/zero of=/dev/sd[x] # woeusb --device Win10_21H2_English_x64.iso /dev/sd[x] --target-filesystem NTFS or whatever the iso is called. You do not need a license for this. Windows will just not let you set a wall paper. Woopie-do. If you do not feel like installing Windows on a spare hard drive, disconnect your Linux drive, fire up the Windows installer and jet let it sit there. See if you freeze up. If it is your hardware, try substituting Kingston memory. Crucial if you absolutely you have to. For SSD Drive, I only recommend Samsung. They just work. No drama. And remember. You pay for what you get. Well, except for my advice! :-) HTH, -T ___ 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
Gigabyte: "we cannot offer full support on Linux"
It's been a long time since I've encountered this kind of obtuseness. This is not new, but I thought that this kind of blindness was in the rear-view mirror. I guess not. One of their motherboards keeps locking up on me. After some back and forth their last reply ended the discussion thread with a: # Since we do not fully support and validate Linux, we cannot offer full # support on Linux. Please try a Windows base OS to check if you are still # experiencing the same instability issue. Just thought I'd mention it here, so that other DIYers might take this into consideration. Looking at their support page, it's listing new BIOS updates every month. pgprtulLUgEvI.pgp Description: PGP signature ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: Problems with Borg backup on F36
On Mon, 16 May 2022 20:56:10 +0100 Patrick O'Callaghan wrote: > On Mon, 2022-05-16 at 18:20 +0200, Markus Schönhaber wrote: > > 16.05.22, 17:45 +0200, Patrick O'Callaghan: > > > > > I updated to F36 a few days ago and everything seemed to go > > > smoothly > > > until I noticed my regular nightly backups were failing. I use > > > Borgbackup and the configuration has been stable for a long time > > > with > > > no problems. The actual backup does seem to succeed, but Borg runs > > > a > > > post-backup repository check that is now failing, even for backups > > > taken before the system upgrade. > > I upgraded a laptop to F36 few days ago and borgmatic runs without error, including the check. I suspect something else is happening. Try increasing borgmatic’s verbosity to see the borg error message. borgmatic-1.6.0 does have some breaking changes, but that is the current version for both 35 and 36. Also, my systems are using borgbackup-1.1.17-1.fc35 and borgbackup-1.2.0-1.fc36. How did you get 1.2.0 on F35? Jim > > Could be caused by the update to borg 1.2. You might want to take a > > look > > at this bug report: > > https://github.com/borgbackup/borg/issues/6687 > > > > I did consider that. However the upgrade to Borg 1.2 happened on April > 12, weeks before the system upgrade to Fedora 36, and there were no > errors in the intervening time. Also, the built-in validation check on > the config file says it's all fine. > > > > I've reported this: > > > https://mail.google.com/mail/u/1/?zx=60aw7rldu1gf&pli=1#inbox > > > > I don't get where this link is supposed to lead to. > > Sorry, that should have been: > > https://bugzilla.redhat.com/show_bug.cgi?id=2086497 > > poc > ___ > users mailing list -- users@lists.fedoraproject.org > To unsubscribe send an email to users-le...@lists.fedoraproject.org > Fedora Code of Conduct: > https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List > Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: > https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org > 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: Problems with Borg backup on F36
On Mon, 2022-05-16 at 18:20 +0200, Markus Schönhaber wrote: > 16.05.22, 17:45 +0200, Patrick O'Callaghan: > > > I updated to F36 a few days ago and everything seemed to go > > smoothly > > until I noticed my regular nightly backups were failing. I use > > Borgbackup and the configuration has been stable for a long time > > with > > no problems. The actual backup does seem to succeed, but Borg runs > > a > > post-backup repository check that is now failing, even for backups > > taken before the system upgrade. > > Could be caused by the update to borg 1.2. You might want to take a > look > at this bug report: > https://github.com/borgbackup/borg/issues/6687 > I did consider that. However the upgrade to Borg 1.2 happened on April 12, weeks before the system upgrade to Fedora 36, and there were no errors in the intervening time. Also, the built-in validation check on the config file says it's all fine. > > I've reported this: > > https://mail.google.com/mail/u/1/?zx=60aw7rldu1gf&pli=1#inbox > > I don't get where this link is supposed to lead to. Sorry, that should have been: https://bugzilla.redhat.com/show_bug.cgi?id=2086497 poc ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: Problems with Borg backup on F36
16.05.22, 17:45 +0200, Patrick O'Callaghan: I updated to F36 a few days ago and everything seemed to go smoothly until I noticed my regular nightly backups were failing. I use Borgbackup and the configuration has been stable for a long time with no problems. The actual backup does seem to succeed, but Borg runs a post-backup repository check that is now failing, even for backups taken before the system upgrade. Could be caused by the update to borg 1.2. You might want to take a look at this bug report: https://github.com/borgbackup/borg/issues/6687 I've reported this: https://mail.google.com/mail/u/1/?zx=60aw7rldu1gf&pli=1#inbox I don't get where this link is supposed to lead to. -- Regards mks ___ 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
Problems with Borg backup on F36
I updated to F36 a few days ago and everything seemed to go smoothly until I noticed my regular nightly backups were failing. I use Borgbackup and the configuration has been stable for a long time with no problems. The actual backup does seem to succeed, but Borg runs a post-backup repository check that is now failing, even for backups taken before the system upgrade. I've reported this: https://mail.google.com/mail/u/1/?zx=60aw7rldu1gf&pli=1#inbox poc ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: Shift+PrintScreen gone with F36?
On Mon, 16 May 2022 13:17:28 +0700 Frederic Muller wrote: > Thank you, didn't see that link. Now that doesn't really fit my needs > as I liked the (partial) screenshot saved automatically, avoiding to > open a imaging application to get back the clipboard. I'll spare > everyone the rant over great simple things going away... > > Who knows maybe we'll get back a way to have SHIFT+PrintScreen in > GNOME 48, who knows? There is an application called spectacle that takes screenshots. In the configuration, there is a way to set keyboard shortcuts. Perhaps you can adapt it to do what you want? ___ 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
OT : systemd-udev issue in CentOS 8.5 / Rocky Linux 8.5 / RHEL 8.5
Sorry for being a bit off topic here but I'm hoping some of the clever
people on this
list can help me out with a systemd-udev issue here.I'm hoping this is a solved
issue in
fedora that maybe hasn't made its way upstream yet.
I have a custom usb devive that I want a certain group of users to have full
access to when
it is plugged in . For CentOS 6 & 7 I just add a rule to /etc/udev/rules.d
like
SUBSYSTEM=="usb", ATTR{idVendor}=="03eb", ATTR{idProduct}=="2017",
GROUP="atmel", MODE="666"
and Bob is your uncle. The created usb device ( /dev/bus/usb/.../... gets
permissions 666 as
user root and group atmel .
However, I cannot get this to work the same way with CentOS 8 / Rocky Linux 8
/ ( RHEL 8 )
and I cannot figure out why not. The device in /dev/bus/usb is being created
but only root
can access it as the ownersip is set to root:root and the mode to 664 . The
logs report an :
unhandled action 'bind' on /sys/devices/pci:00/:00:14.0/usb1/1-1 ( or
similar depending
on the port used ) and systemd-udev retuns : invalid SUBSYSTEM operation
which doesn't
tell me a lot.
Removing the MODE and GROUP from the rule makes the error messages go away but
ownership and
permissions are set to the default root and 664
Trying to replace MODE and GROUP ith a RUN=+some_script also fails ( with or
without
including the ACTION=="add" keyword. The script never starts as far as I can
tell.
Anybody knows what is going on here ? Does systemd-udevd not have root
permissions ?
I can of course set the mode as user root or use sudo but really ?
systemd is version 239 which is probably outdated by fedora standards but it
is what comes
with RHEL 8.5 clones.
peter
___
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
