Re: desktop power button

[ToddAndMargo via users]

On 11/17/23 19:53, Samuel Sieb wrote:

On 11/17/23 19:48, ToddAndMargo via users wrote:

I may have to compromise on gshutdown.  Be cool if I could locate
what MATE calls from the system menu.


Create a .desktop file that runs "poweroff" or "reboot" depending on 
what you're wanting to do.


Thank you!

That will work perfectly.

I was also thinking of substituting the desktop icon
for LibreOffice Writer and Calc with the M$ Word and
Excel icons.

A company once had me switch everyone over from Internet
Explorer to Firefox.  One of the users griped and griped
and griped. So I switched his Firefox icon over to the
Internet Explorer icon.   The next week he got in my
face and announced he could do everything with Internet
Explorer that could be done in Firefox.  He even
demonstrated it to me.  Uhhh ... that ain't Internet
Explorer, but he did not know the difference.  Yes,
I had a hard time not laughing.  And no, I never told him.
--
___
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: DNF Upgrade from F38 to F39 Issues

[Samuel Sieb]

On 11/17/23 19:08, Stephen Morris wrote:
     I reinstalled the nvidia drivers and a subsequent reboot then 
booted into KDE with any issues (which is where I'm sending this email 
from). Why did this freezing of the nvidia drivers happen, is it because 
the F39 nvidia drivers don't work properly with an update and have to be 
installed from scratch to work properly?


I think there was another thread about this.  The akmods didn't run 
properly during the update process.

--
___
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: desktop power button

[Samuel Sieb]

On 11/17/23 19:48, ToddAndMargo via users wrote:

I may have to compromise on gshutdown.  Be cool if I could locate
what MATE calls from the system menu.


Create a .desktop file that runs "poweroff" or "reboot" depending on 
what you're wanting to do.

--
___
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

desktop power button

[ToddAndMargo via users]

Hi All,

Fedora 39
MATE 1.26

I have been tasked to set up a kiosk at a cusomter's
site with Fedroa:  The users their are walk in customer's
wanting to pay bills, etc..  So Firefox, Brave, LibreOffice,
gcals, etc..  The users will be very, very, very low skill
users.

I was going to install MATE on it because it is danged simple
to operate.

The only issues is that the "system" shutdown/reboot is hard
to find for such a low skill user(s).

I would like a desktop icon to shutdown/reboot/sleep
their computer.  My own system is dual Xfce/MATE.  A
search of the MATE app installed does not show one
or I can not find it.

I see qshutdown on the web, but not in the Fedora repo.
And it is a bit too complicated for low skill users.

I do see kshutdown and gshutdown in the repo, but still a
bit too complicated.

Any ideas about a utility that would allow me to create
really, really low skill user shutdown icon for
their desktop?

I may have to compromise on gshutdown.  Be cool if I could locate
what MATE calls from the system menu.

Many thanks,
-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, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Starting Wayland FC39

[Dave Close]

I wrote:

>Until FC39, I had only run Wayland on one of my machines, not even
>trying to bring it up on the others. Since I intensely dislike the
>graphic login, I found a way to start it from a virtual terminal like
>I normally start X11. Instead of "startx", I have a short script I call
>"startw" that contains only the single line, "/usr/bin/dbus-run-session
>/usr/bin/startplasma-wayland". (Yes, I run KDE.) This worked on FC38.
>
>Now on the same machine with FC39 (upgraded with system-upgrade) this
>no longer works. Instead, it produces 248 lines of output and then
>terminates. Reviewing those lines, it appears that it is complaining
>about, 'failed to open drm device at "/dev/dri/card0"' and 'No suitable
>DRM devices have been found'.  I'm not sure what device that refers
>to but there seems to be some indication that it is my display. The
>display certainly works fine for the virtual terminal I use to run
>this script, and it also works fine for X11 if I run "startx".
>
>Ok, so as a fallback I tried a graphic login. This reaches a completely
>blank screen and goes no further. The machine is up as I can reach it
>with SSH but the display is useless. It responds to Ctrl-Alt-Delete
>but nothing else. I can't get it to switch to a different desktop. I
>noticed that SDDM defaults to Wayland so I changed "sddm.conf" to
>include "DisplayServer=x11". The allowed the graphic login to reach
>a login page but nothing I entered there was accepted even when I
>switched to specify starting an X11 session instead of Wayland.
>
>There are some online references to a problem with the /dev/dri/card0
>device but they are ancient and don't seem relevant.
>
>This machine is intended to run an application that only works on
>Wayland (Waydroid) so at this point I'm stimied. Any suggestions
>would be very helpful.

If it matters, this machine was never installed with the KDE spin. It
was installed before spins and with extensive editing of the packages to be
included. KDE was added to it. It's been working through several Fedora
releases for at least three years.
-- 
 Dave Close, Compata, Irvine CA   +1 714 434 7359
   d...@compata.com  dhcl...@alumni.caltech.edu
  "The problem with people who have no vices is that generally you can
   be pretty sure they're going to have some pretty annoying virtues."
  -- Elizabeth Taylor

--
___
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: DNF Upgrade from F38 to F39 Issues

[Jeffrey Walton]

On Fri, Nov 17, 2023 at 10:08 PM Stephen Morris
 wrote:
>
> Hi,
>  I used dnf system-upgrade to upgrade from F38 to F39. After the
> upgrade when I booted into gdm to login and start KDE, the machine hung
> on KDE startup into X11.
>  Thinking it might be an nvidia UEFI enrolment issue with the F39
> nvidia drivers, I reset the machine and booted back into gdm.
>  I then used ctrl+alt+F2 to start a terminal interface. In that
> terminal I went through the UEFI enrolment process but that said the
> drivers were already enrolled.
>  I issued dmesg to see if there were any nvidia failure messages, of
> which there none, but I did notice there were initialisation and what
> looked like failure messages from Nouveau, but I don't understand why
> there would be an Nouveau messages at all when Nouveau is blacklisted in
> the kernel parameters in grub.
>  I then uninstalled all the nvidia drivers that were present. I then
> used ctrl+alt+delete to reboot from the terminal. That process hung for
> 1.5 minutes waiting for a job stop (I don't remember what it was waiting
> on), and, when the 1.5 minute timer finished it then hung waiting for
> XWayland to shut down. Why was it waiting for XWayland to shut down when
> I don't use Wayland, I only use X11?
>  On reboot, I started up KDE under Nouveau, which doesn't work
> properly with my BENQ 4K monitor, it can't determine what the monitor
> is, so doesn't run in the right resolutions, although it does honour the
> display scaling specified when using the nvidia drivers (which do
> recognise the monitor and set things up properly).
>  I reinstalled the nvidia drivers and a subsequent reboot then
> booted into KDE with any issues (which is where I'm sending this email
> from). Why did this freezing of the nvidia drivers happen, is it because
> the F39 nvidia drivers don't work properly with an update and have to be
> installed from scratch to work properly?
>  Also, after reinstalling the nvidia drivers, at the gdm login
> screen the display manager selection options only showed "Gnome", "Gnome
> Classic" and "Plasma/X11", where are the options for all of those to
> swap them between Wayland and X11 if I want to, that were present in F38
> before the upgrade to F39?

A couple of thoughts in no particular order. I don't know how you
should move forward with your issues.

* The KDE spin uses Wayland, not X11.

* The KDE spin uses SDDM, not GDM.

* SecureBoot should be turned off if using tainted kernel drivers. Or,
you can cutover to driver signing. I usually turn off SecureBoot
because I don't like messing around with driver signing. In my case,
it usually is due to VirtualBox, not NVIDIA.

Jeff
--
___
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

LibreOffice Base to MariaDB?

[Greg Woods]

I remember setting this up quite some time ago, but now I have a new
machine running F38. I can find some documentation for the old very tedious
procedure to get this to work; it still does work on an older machine where
I had done this. But I notice now that Fedora might already have some of
the required packages, such as mariadb-connector-odbc-3.1.19-1.fc38.x86_64
and unixODBC-2.3.11-2.fc38.x86_64 . Would these packages work? Has anyone
here already gotten LibreOfficeBase to talk to a MariaDB database on Fedora
38? If so can you point me to a place that describes the process for
getting it working?

Thanks in advance,
--Greg
--
___
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: recommended practice for python 3.11 on F39

[Jeffrey Walton]

On Fri, Nov 17, 2023 at 9:30 PM Ranjan Maitra via users
 wrote:
>
> So, it turns out that there is no tensorflow for Python 3.12, which is
> what is shipped out with F39.
>
> I tried to downgrade my python using
>
> sudo dnf downgrade python --releasever=38
>
> that downgrades a huge bunch of things, including important components
> like rpm.
>
> However, dnf install/update pretty much anything gives a segmentation
> fault after that.
>
> $ sudo dnf update --exclude=python\*
> Last metadata expiration check: 2:37:29 ago on Fri 17 Nov 2023 05:50:32 PM 
> CST.
> Segmentation fault
>
> Staying within the dnf system, is there a better way to keep the older
> version of python around?

The Python folks recommend building from sources, but using a
different $prefix, and installing with `make altinstall`. See
.

Debian has a nice explanation of how to run different versions of
Python. It follows Python's recommendations. Once you download the
version you are interested in, upack it, run `./configure
--prefix=/opt && make && make test`. Follow it with a `make
altinstall`. Also see .

If you try Python's method, do not install into /usr/local. Pick a
location like /opt/python3.11. Unexpected versions of software in
/usr/local can cause quite a bit of pain since /usr/local is often
on-path.

Jeff
--
___
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: Tip: default printer

[Stephen Morris]

On 16/11/23 02:20, George N. White III wrote:
On Tue, Nov 14, 2023 at 5:58 PM Stephen Morris 
 wrote:


[...]

Hi George,
    I was pointing this out because I don't use the IPP Anywhere
interface, and cups has never supplied drivers for my printer,
I've had to always the Epson supplied driver to enable printing in
Linux. This was just an observation with, when adding a printer,
cups shows me two entries under the "Discovered Network Printer"
section, one for IPP Anywhere and one for the "Driverless" option,
where the IPP Anywhere shows two separate driver definitions for
cups drivers and the driverless option, whereas the "Driverless"
selection displays all drivers in the one list with the driverless
driver listed first and all the cups drivers then listed in
alphabetical order.


I wonder if we are in a transitional phase where legacy CUPS is mixing 
with IPP.   Some manufacturers may provide legacy support in their 
printers when they add IPP,
but (until Apple changes AirPrint), most manufacturers' networked 
printers will provide IPP because they want Apple AirPrint to work for 
customers using IOS.


I have never used IPP Anywhere with this printer, IPP Anywhere seems to 
be a relatively recent innovation in cups. It used to be just IPP among 
other options, which seem to have disappeared now, but I was never able 
to get IPP to work with my Epson printer.


regards,
Steve


--
George N. White III


___
users mailing list --users@lists.fedoraproject.org
To unsubscribe send an email tousers-le...@lists.fedoraproject.org
Fedora Code of 
Conduct:https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines:https://fedoraproject.org/wiki/Mailing_list_guidelines
List 
Archives:https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam, report 
it:https://pagure.io/fedora-infrastructure/new_issue




OpenPGP_0x594338B1DE179AB2.asc
Description: OpenPGP public key


OpenPGP_signature.asc
Description: OpenPGP digital 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, report it: 
https://pagure.io/fedora-infrastructure/new_issue

DNF Upgrade from F38 to F39 Issues

[Stephen Morris]

Hi,
    I used dnf system-upgrade to upgrade from F38 to F39. After the 
upgrade when I booted into gdm to login and start KDE, the machine hung 
on KDE startup into X11.
    Thinking it might be an nvidia UEFI enrolment issue with the F39 
nvidia drivers, I reset the machine and booted back into gdm.
    I then used ctrl+alt+F2 to start a terminal interface. In that 
terminal I went through the UEFI enrolment process but that said the 
drivers were already enrolled.
    I issued dmesg to see if there were any nvidia failure messages, of 
which there none, but I did notice there were initialisation and what 
looked like failure messages from Nouveau, but I don't understand why 
there would be an Nouveau messages at all when Nouveau is blacklisted in 
the kernel parameters in grub.
    I then uninstalled all the nvidia drivers that were present. I then 
used ctrl+alt+delete to reboot from the terminal. That process hung for 
1.5 minutes waiting for a job stop (I don't remember what it was waiting 
on), and, when the 1.5 minute timer finished it then hung waiting for 
XWayland to shut down. Why was it waiting for XWayland to shut down when 
I don't use Wayland, I only use X11?
    On reboot, I started up KDE under Nouveau, which doesn't work 
properly with my BENQ 4K monitor, it can't determine what the monitor 
is, so doesn't run in the right resolutions, although it does honour the 
display scaling specified when using the nvidia drivers (which do 
recognise the monitor and set things up properly).
    I reinstalled the nvidia drivers and a subsequent reboot then 
booted into KDE with any issues (which is where I'm sending this email 
from). Why did this freezing of the nvidia drivers happen, is it because 
the F39 nvidia drivers don't work properly with an update and have to be 
installed from scratch to work properly?
    Also, after reinstalling the nvidia drivers, at the gdm login 
screen the display manager selection options only showed "Gnome", "Gnome 
Classic" and "Plasma/X11", where are the options for all of those to 
swap them between Wayland and X11 if I want to, that were present in F38 
before the upgrade to F39?


regards,
Steve



OpenPGP_0x594338B1DE179AB2.asc
Description: OpenPGP public key


OpenPGP_signature.asc
Description: OpenPGP digital 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, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Starting Wayland FC39

[Dave Close]

Until FC39, I had only run Wayland on one of my machines, not even
trying to bring it up on the others. Since I intensely dislike the
graphic login, I found a way to start it from a virtual terminal like
I normally start X11. Instead of "startx", I have a short script I call
"startw" that contains only the single line, "/usr/bin/dbus-run-session
/usr/bin/startplasma-wayland". (Yes, I run KDE.) This worked on FC38.

Now on the same machine with FC39 (upgraded with system-upgrade) this
no longer works. Instead, it produces 248 lines of output and then
terminates. Reviewing those lines, it appears that it is complaining
about, 'failed to open drm device at "/dev/dri/card0"' and 'No suitable
DRM devices have been found'.  I'm not sure what device that refers
to but there seems to be some indication that it is my display. The
display certainly works fine for the virtual terminal I use to run
this script, and it also works fine for X11 if I run "startx".

Ok, so as a fallback I tried a graphic login. This reaches a completely
blank screen and goes no further. The machine is up as I can reach it
with SSH but the display is useless. It responds to Ctrl-Alt-Delete
but nothing else. I can't get it to switch to a different desktop. I
noticed that SDDM defaults to Wayland so I changed "sddm.conf" to
include "DisplayServer=x11". The allowed the graphic login to reach
a login page but nothing I entered there was accepted even when I
switched to specify starting an X11 session instead of Wayland.

There are some online references to a problem with the /dev/dri/card0
device but they are ancient and don't seem relevant.

This machine is intended to run an application that only works on
Wayland (Waydroid) so at this point I'm stimied. Any suggestions
would be very helpful.
-- 
 Dave Close, Compata, Irvine CA   +1 714 434 7359
   d...@compata.com  dhcl...@alumni.caltech.edu
"To copy the truth can be a good thing,
 but to invent the truth is better." -- Giuseppe Verdi

--
___
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: Desktop scaling not working on F39 + X1 Carbon 3rd gen

[Stephen Morris]

On 16/11/23 15:35, Frederic Muller wrote:

On 15/11/2023 09:55, Frederic Muller wrote:

On 15/11/2023 04:42, Stephen Morris wrote:

On 14/11/23 19:34, Frederic Muller wrote:


Hi!

Upgraded from F38 and trying to get 150% scaling as 100% is too 
small and 200% too big. Both


|gsettings reset org.gnome.mutter experimental-features or 
gsettings set org.gnome.mutter experimental-features 
"['scale-monitor-framebuffer']" and logging out do nothing. It used 
to work a few years ago. Any idea how to fix this?|
|I'm still on F38, so not sure how F39 works, but if it is the same 
as F38, in the gnome system settings for setting up the scaling 
there is a fractional scaling option, which if set allows you to set 
scaling 150%.
I don't use Gnome though, I use KDE, where you can set the 150% 
scaling without having to activate any other option.


regards,
Steve
|

|Thank you. Fred |

Actually it was under F38. I thought the upgrade was completed but I 
was wrong. Now that the update is completed I am having the same issue.


And I followed your tips but couldn' t find any area in GNOME 
settings with any related option. I'm probably going to burn a USB 
stick with the live ISO and see if that works out of the box. As I 
mentioned previously this feature has worked on this machine for many 
years.


Thank you for the heads up, at least I feel no so lonely anymore ;-)

Fred


___


Tried from the 'live CD' and it worked. So I guess I got something 
broken under F38, not fixed by upgrading and therefore I'll do a fresh 
install.


Thank you.

Fred


Hi Fred,
    A fresh install may not make any difference. With my 4K monitor a 
fresh install of F38 did not activate 150% scaling in the display 
settings, I had to use the slider to turn on fractional scaling to be 
able select 150% scaling from the scaling drop down. Without using the 
slider 150% scaling did not appear in the scaling dropdown.


regards,
Steve



___
users mailing list --users@lists.fedoraproject.org
To unsubscribe send an email tousers-le...@lists.fedoraproject.org
Fedora Code of 
Conduct:https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines:https://fedoraproject.org/wiki/Mailing_list_guidelines
List 
Archives:https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam, report 
it:https://pagure.io/fedora-infrastructure/new_issue




OpenPGP_0x594338B1DE179AB2.asc
Description: OpenPGP public key


OpenPGP_signature.asc
Description: OpenPGP digital 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, report it: 
https://pagure.io/fedora-infrastructure/new_issue

recommended practice for python 3.11 on F39

[Ranjan Maitra via users]

So, it turns out that there is no tensorflow for Python 3.12, which is
what is shipped out with F39.

I tried to downgrade my python using

sudo dnf downgrade python --releasever=38

that downgrades a huge bunch of things, including important components
like rpm.

However, dnf install/update pretty much anything gives a segmentation
fault after that.

$ sudo dnf update --exclude=python\*
Last metadata expiration check: 2:37:29 ago on Fri 17 Nov 2023 05:50:32 PM CST.
Segmentation fault

Staying within the dnf system, is there a better way to keep the older
version of python around?

Many thanks,
Ranjan
--
___
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: f39 emacs strange behavior?

[Ranjan Maitra via users]

On Thu Nov16'23 08:46:17PM, Ben Hancock wrote:
> From: Ben Hancock 
> Date: Thu, 16 Nov 2023 20:46:17 -0800
> To: users@lists.fedoraproject.org
> Reply-To: Community support for Fedora users 
> Subject: Re: f39 emacs strange behavior?
>
> On 11/12/23 08:12, Ranjan Maitra wrote:
> > Right, now, trying my luck with nvim for writing this email (because
> > mutt for me is linked to an editor, in my case, it was emacs).
>
> FWIW, you may want to try `mg` as a backup editor for Emacs. If you're used
> to Emacs key-bindings, it's sure to be more familiar. When I used mutt more
> regularly I set mg as my fallback for times when I hadn't yet fired up Emacs
> and done `M-x server-start`:
>
>   set editor = 'emacsclient --alternate-editor mg'
>
> Ben

Thanks, Ben! I am more or less finding my way around nvim, but I have
not yet figured out two things yet.

I loved the autoformatting feature of C, etc in emacs. Basically as I
typed, things would get formatted. And I have not really been able to
figure out if that is possible here (automagically, without pressing any
key combination).

The other thing I will look at more carefully this weekend is to figure
out a way to reliably highlight a area with my mouse left button and
then paste it with my second mouse button (the wheel). Inside nvim, it
is largely not reliable (with workarounds in many cases, but with key
combinations) and I can not quite figure out why it is not. In the old
days before DEs, the idea of highlight and paste (rather than use
whatever key combination) is something I really got used to.

Many thanks and best wishes,
Ranjan

--
___
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: Obscure rsyslog question on remote logging

[Chris Adams]

Once upon a time, Tom Horsley  said:
> I found some obscure text about needing to use a $ in front of
> system variables and since $myhostname is a system variable
> I need to type it as $$myhostname in the condition (I think :-)

So an alternate approach that might help... you can assign a ruleset to
an input, and the UDP input is separate from the local input.  I put
this in /etc/rsyslog.d/net.conf:


template(name="Remote" type="list") {
constant(value="/var/log/remote/")
property(name="hostname")
constant(value=".log")
}

module(load="imudp")

$umask 0022
ruleset(name="remote") {
*.* action(type="omfile" DynaFile="Remote" fileCreateMode="0644")
}
input(type="imudp" port="514" ruleset="remote")


My template is a simple /var/log/remote/.log (I use the really
redundant .log extension so I can have a logrotate config to get
/var/log/remote/*.log).  I set the umask to 0022 and the file create
mode to 0644 because I have the group permissions on the /var/log/remote
directory to allow certain non-root users to read these logs.

-- 
Chris Adams 
--
___
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: Obscure rsyslog question on remote logging

[Tom Horsley]

On Thu, 16 Nov 2023 20:46:33 -0500
Todd Zullinger wrote:

> if ($hostname != $myhostname) then {

I tried this just running it through the rsyslogd syntax check (-N1 opt)
and it complained about using "myhostname" and asked if I didn't
actually mean "$myhostname" :-).

The documentation on rsyslog.com is still incredibly skimpy, but
possibly I need to use $$myhostname (at least the syntax check likes
that).

I found some obscure text about needing to use a $ in front of
system variables and since $myhostname is a system variable
I need to type it as $$myhostname in the condition (I think :-)

I don't suppose there is a totally different alternative to
rsyslog out there with sensible syntax? (Something like postfix
instead of sendmail.)

I haven't yet worked up the courage to actually try this for
real...
--
___
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: emacs is hopeless

[stan via users]

On Wed, 15 Nov 2023 17:37:09 +
Barry Scott  wrote:

> > On 15 Nov 2023, at 17:21, stan via users
> >  wrote:
> > 
> > I work around that by configuring hh and uu as .  Since I
> > (almost) always finish input by pressing one of them, the command
> > mode is available, so I just hit
> > :w 
> > to save.  I guess it is a matter of taste, a trade off.  
> 
> I know few vi commands, one I do know is ZZ that saves the file and
> exits.
> 
> I only know enough vi to boot strap barry's emacs on a machine .

That would be me in emacs.  I used emacs at one point, and liked it.
Then I took a long hiatus, and when I used it again, it just didn't
click with me.  So, I learned vim, and I find it comfortable to use,
it fits my thinking process.  Just like perl and python.  I just
couldn't feel comfortable using perl, but python fits like a glove. To
each their own.
--
___
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 packages problem

[stan via users]

On Wed, 15 Nov 2023 18:32:07 +0100
GianPiero Puccioni  wrote:

> I didn't know that "err" didn't show on the terminal!

Probably to avoid huge amounts of messages.

> Apparently the problem was
> "qt5-qtwebengine-freeworld-5.15.12-4.fc38.x86_64" I removed that and
> everything is back to normal, should I file a bug in RPMFusion?

I'm not sure.  The rpmfusion package just needs a recompile to pick up
the new library.  So it isn't really a bug.  But it is a sure way to
flag the issue to the package maintainer, so maybe it is better than to
just send a message to their mailing list.

Yeah, file a bug, I convinced myself.
--
___
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

[389-users] Re: Documentation as to how replication works

[William Faulk]

> I noticed there is code to dump the changelog to a flat file, but
> it isn't clear to me how to call it

Aha! I poked through the code and figured it out:

Perform an ldapmodify against "cn=replica,cn=...,cn=mapping tree,cn=config" 
adding the attribute "nsds5Task" with the value "CL2LDIF". It then writes the 
LDIF file to the same directory that contains the changelog database files, 
which is defined in the "nsslapd-changelogdir" attribute of 
"cn=changelog5,cn=config", which, for me, is 
"/var/lib/dirsrv/slapd-/cldb".

To be clear, here's the ldapmodify LDIF that worked for me:

dn: cn=replica,cn=...,cn=mapping tree,cn=config
changetype: modify
add: nsds5Task
nsds5Task: CL2LDIF

The LDIF that's created shows the actual changed data and not just a blob, 
which certainly helps.
--
___
389-users mailing list -- 389-users@lists.fedoraproject.org
To unsubscribe send an email to 389-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/389-users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: How to force removal of protected package?

[Jeffrey Walton]

On Fri, Nov 17, 2023 at 3:54 AM Samuel Sieb  wrote:
>
> On 11/17/23 00:31, Jeffrey Walton wrote:
> > $ sudo dnf remove gnome*
> > Error:
> > Problem: The operation would result in removing the following protected 
> > package
> > s: gnome-shell
> > (try to add '--skip-broken' to skip uninstallable packages)
> >
> > I've read the dnf(8) man page, but I don't see how to remove a
> > protected package.
> >
> > How do I force the removal of a protected package?
>
> It's protected by fedora-release-identity-workstation
> You can either pick another specific identity or just run:
> dnf install fedora-release-identity-basic --allowerasing

Thanks. I did not know about fedora-release-identity-*. Or that there
were so many of them:

$ dnf search fedora-release-identity
...
fedora-release-identity-basic.noarch : Package providing the basic Fedora
: identity
fedora-release-identity-budgie.noarch : Package providing the identity for
 : Fedora Budgie Spin
fedora-release-identity-cinnamon.noarch : Package providing the identity for
   : Fedora Cinnamon Spin
fedora-release-identity-cloud.noarch : Package providing the identity for Fedora
: Cloud Edition
fedora-release-identity-compneuro.noarch : Package providing the identity for
: Fedora Comp Neuro Lab
fedora-release-identity-container.noarch : Package providing the identity for
: Fedora Container Base Image
fedora-release-identity-coreos.noarch : Package providing the identity for
 : Fedora CoreOS
fedora-release-identity-designsuite.noarch : Package providing the identity for
  : Fedora Design Suite Lab
fedora-release-identity-i3.noarch : Package providing the identity for Fedora i3
 : Spin
fedora-release-identity-iot.noarch : Package providing the identity for Fedora
  : IoT Edition
fedora-release-identity-kde.noarch : Package providing the identity for Fedora
  : KDE Plasma Spin
fedora-release-identity-kinoite.noarch : Package providing the identity for
  : Fedora Kinoite
fedora-release-identity-lxqt.noarch : Package providing the identity for Fedora
   : LXQt Spin
fedora-release-identity-matecompiz.noarch : Package providing the identity for
 : Fedora MATE-Compiz Spin
fedora-release-identity-mobility.noarch : Package providing the identity for
   : Fedora Mobility
fedora-release-identity-onyx.noarch : Package providing the identity for Fedora
   : Onyx
fedora-release-identity-sericea.noarch : Package providing the identity for
  : Fedora Sericea
fedora-release-identity-server.noarch : Package providing the identity for
 : Fedora Server Edition
fedora-release-identity-silverblue.noarch : Package providing the identity for
 : Fedora Silverblue
fedora-release-identity-snappy.noarch : Package providing the identity for
 : Fedora Snappy environments
fedora-release-identity-soas.noarch : Package providing the identity for Fedora
   : Sugar on a Stick
fedora-release-identity-sway.noarch : Package providing the identity for Fedora
   : Sway Spin
fedora-release-identity-workstation.noarch : Package providing the identity for
  : Fedora Workstation Edition
fedora-release-identity-xfce.noarch : Package providing the identity for Fedora
   : Xfce Spin

Jeff
--
___
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: libvirt-designer* ???

[ToddAndMargo via users]

On 11/16/23 20:49, Samuel Sieb wrote:

On 11/16/23 03:30, ToddAndMargo via users wrote:

I use qemu-kvm virtual machines all the time.

Do I need these fc38 (not 39) packages still?


Please don't ask for every F38 package you find.  If it's not something 
you're using and removing it doesn't take away something you're using, 
then remove it if it bothers you to have it installed.


I had a list of about 30 of them that I either removed or upgraded to 
39.  I only asked about three of them.  Then rest I could find with wev 
searches. etc..



# dnf reinstall libvirt-designer* --releasever=39


That command doesn't even make sense.  If the package is F38, then 
"reinstall" is clearly not going to work if you specify F39 as the 
release.  And if it worked, you would still have the same version 
anyway.   Use "upgrade" instead.


I used reinstall to force things to 39.  Sometimes I had to
use downgrade to get them into 39 as the 38 package was
a higher revision.

For example:
cups-1:2.4.7-2.fc38.x86_64
cups-1:2.4.7-1.fc39.x86_64

Last metadata expiration check: 3:41:31 ago on Wed 15 Nov 2023 
11:45:16 PM PST.
Installed package libvirt-designer-0.0.2-19.fc38.x86_64 (from fedora) 
not available.
Installed package libvirt-designer-devel-0.0.2-19.fc38.x86_64 (from 
fedora) not available.
Installed package libvirt-designer-devel-doc-0.0.2-19.fc38.x86_64 
(from fedora) not available.
Installed package libvirt-designer-libs-0.0.2-19.fc38.x86_64 (from 
fedora) not available.
Installed package libvirt-designer-vala-0.0.2-19.fc38.x86_64 (from 
fedora) not available.

Error: No packages marked for reinstall.


If you want more info, you can check koji:
https://koji.fedoraproject.org/koji/packageinfo?packageID=14881
This package hasn't even been attempted to be built for F39 yet.
And from there, you can find out why.
https://src.fedoraproject.org/rpms/libvirt-designer
"Package is no longer developed upstream and nothing uses it"

I don't think it's ever been a default package, so you must have 
installed it yourself at some point.


I agree.

Me thinks it may have been left over from when I
had to use "up stream's" packages to get past a bug.

$ rpm -ql libvirt-designer-0.0.2-19.fc38.x86_64
/usr/bin/virt-designer
/usr/lib/.build-id
/usr/lib/.build-id/80
/usr/lib/.build-id/80/8f73cfe1b564de469fecd723d23e764b206696
/usr/share/man/man1/virt-designer.1.gz

$ ls -al /usr/bin/virt-designer
-rwxr-xr-x. 1 root root 29512 Jan 18  2023 /usr/bin/virt-designer

And it has no been touched since "Jan 18  2023"


# dnf remove libvirt-designer*
Dependencies resolved.

 PackageArch   Version   Repository 
   Size


Removing:
 libvirt-designer   x86_64 0.0.2-19.fc38 @fedora 
   32 k
 libvirt-designer-devel x86_64 0.0.2-19.fc38 @fedora 
   56 k
 libvirt-designer-devel-doc x86_64 0.0.2-19.fc38 @fedora 
  130 k
 libvirt-designer-libs  x86_64 0.0.2-19.fc38 @fedora 
  113 k
 libvirt-designer-vala  x86_64 0.0.2-19.fc38 @fedora 
  3.8 k

Removing unused dependencies:
 libosinfo-develx86_64 1.11.0-1.fc39 @updates 
  2.1 M


Transaction Summary

Remove  6 Packages

Freed space: 2.4 M


Hm.  Me thinks I will remove them anyway and see who complains.
And I just removed the above and three (most important) of
my nine VM's are still working..

Progress so far:

$ rpm -qa | grep -v kernel | grep -i fc38
dejavu-sans-mono-fonts-2.37-20.fc38.noarch
dejavu-sans-fonts-2.37-20.fc38.noarch
bitstream-vera-sans-fonts-1.10-48.fc38.noarch
netcdf-4.9.0-5.fc38.x86_64
cabextract-1.9.1-5.fc38.x86_64
virglrenderer-0.10.4-2.20230104git88b9fe3b.fc38.x86_64

So I am pretty close to finished.  I reported the fonts
to bugzilla.

Thank you!

-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, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: redhat-lsb-submod-security ???

[ToddAndMargo via users]

On 11/16/23 20:39, Tim via users wrote:

On Thu, 2023-11-16 at 18:36 -0800, ToddAndMargo via users wrote:

$ dnf info redhat-lsb-submod-security

Last metadata expiration check: 3:57:51 ago on Thu 16 Nov 2023 02:37:19
PM PST.
Installed Packages
Name : redhat-lsb-submod-security
Version  : 4.1
Release  : 60.fc38
Architecture : x86_64
Size : 0.0
Source   : redhat-lsb-4.1-60.fc38.src.rpm
Repository   : @System
 From repo: fedora
Summary  : LSB Security submodule support
URL  : http://www.linuxfoundation.org/collaborate/workgroups/lsb
License  : GPLv2
Description  : The Linux Standard Base (LSB) Security submodule specifications
  : define components that are required to be present on an LSB
  : conforming system.


Huh   Flew right over my head.


Which bit?


The "Description"



The Linux Standards Base is a bunch of basic things expected to exist
on a system.  So software developers have some idea of what they'll
have to work with, what they're expected to support, etc, and try and
standardise things.  There's very basic things, such as the barebones
file system directories (/bin, /etc/ and so on) and what purposes
they're supposed to be used for, and there's binary constructs that
actually are the OS and expected support files (you expect to always
have the ls command, for instance).

And as a bit of a sideways example, CUPS was always expected to exist
on a system, even if you don't own a printer.  There's some logic to
that, also some illogic to it.  Everybody does not have a printer,
everything on a system ought to be able to deal with that, it shouldn't
require an idle printer driving system to be installed.

If you use "rpm -ql redhat-lsb-submod-security" you'll see that it only
contains two files.  If you actually look for those files on your
system, you'll may find they're zero byte files (they are on my CentOS
system) that aren't worth caring about.

The presence of those files satisfies some thing that looks for them,
and only cares that they exist.  Which, as far as I'm concerned, is a
bit of a dumb test for software to do, but there you are.

If you start up some software from the command line you'll see they
complain about various things not existing, but the program still
starts and runs (a better way to run things).  It's simply that those
features aren't available to it, it didn't actually *need* them.

Interestingly, there doesn't appear to be any LSB packages on my
Fedora 36 system:

[tim@fluffy ~]$ rpm -qa \*lsb\*
[tim@fluffy ~]$
  


What a wonderful write up.  Thank you!

Interesting:

$ rpm -ql redhat-lsb-submod-security
/usr/share/lsb/4.1/submodules/security-4.1-amd64
/usr/share/lsb/4.1/submodules/security-4.1-noarch

$ ls -al /usr/share/lsb/4.1/submodules/security-4.1-*
-rw-r--r--. 1 root root 0 Jan 19  2023 
/usr/share/lsb/4.1/submodules/security-4.1-amd64
-rw-r--r--. 1 root root 0 Jan 19  2023 
/usr/share/lsb/4.1/submodules/security-4.1-noarch


And they have not been touched since "Jan 19  2023".

Methinks I am just going to remove them and see if
anyone complains.

# dnf remove redhat-lsb-submod-security
Dependencies resolved.

 PackageArch   Version 
Repository   Size


Removing:
 redhat-lsb-submod-security x86_64 4.1-60.fc38@fedora 
0


Transaction Summary

Remove  1 Package


And there are no dependencies, so here goes.

-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, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: How to force removal of protected package?

[Samuel Sieb]

On 11/17/23 00:31, Jeffrey Walton wrote:

$ sudo dnf remove gnome*
Error:
Problem: The operation would result in removing the following protected package
s: gnome-shell
(try to add '--skip-broken' to skip uninstallable packages)

I've read the dnf(8) man page, but I don't see how to remove a
protected package.

How do I force the removal of a protected package?


It's protected by fedora-release-identity-workstation
You can either pick another specific identity or just run:
dnf install fedora-release-identity-basic --allowerasing
--
___
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

How to force removal of protected package?

[Jeffrey Walton]

Hi Everyone,

I had a dnf-system-upgrade go sideways. It was due, in part, due to a
Python3 install in /usr/local. The other part had to do with the
machine going to sleep while I was ssh'd into the machine. I now want
to get rid of GNOME and use the machine from the command line.

$ sudo dnf group remove gnome-desktop
Warning: Module or Group 'gnome-desktop' is not installed.
Dependencies resolved.
Nothing to do.
Complete!

$ sudo dnf group remove @gnome-desktop
Warning: Module or Group '@gnome-desktop' is not installed.
Dependencies resolved.
Nothing to do.
Complete!

$ sudo dnf group remove gnome-desktop-environment
Warning: Module or Group 'gnome-desktop-environment' is not installed.
Dependencies resolved.
Nothing to do.
Complete!

$ sudo dnf remove gnome*
Error:
Problem: The operation would result in removing the following protected package
s: gnome-shell
(try to add '--skip-broken' to skip uninstallable packages)

I've read the dnf(8) man page, but I don't see how to remove a
protected package.

How do I force the removal of a protected package?

Thanks in advance.
--
___
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: Strange daily reboot - SOLVED

[Patrick O'Callaghan]

On Fri, 2023-11-17 at 14:50 +1030, Tim via users wrote:
> Roger Heflin wrote:
> > > No, we both mean use the bios timed wake up to wake up your
> > > machine
> > > instead of the plug for anything.
> 
> Patrick O'Callaghan:
> > Ah, I misunderstood. I hadn't realised that was even possible.
> 
> Way back in the day of my brief torture of Win98SE, I used to explore
> the BIOS to see what options there were, and which stupid ones were
> preselected.  Wake on timer has been around for a very long time.
> 
> I haven't a use for it, but various businesses use it if they don't
> leave PCs on 24/7.  Have the main server wake up by itself before the
> staff lob in, then progressively booting up each client PC with a
> minutes delay stops having a sudden mains power load, and staggers
> things that poll the server for everything under the sun.

The logic is clear. I just hadn't ever been aware of it, thanks.

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, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Strange daily reboot - SOLVED

[Patrick O'Callaghan]

On Thu, 2023-11-16 at 17:47 -0600, Roger Heflin wrote:
> I checked a mb bios from 10 years ago and it is in it.
> 
> And I checked a 2 year old one and both have it.
> 

Yes, I just verified that mine has it (and it's around 10 years old).

> RTC Alarm Power On
> Allow the system to be waked up by the real time clock alarm. Set it
> to By OS to let
> it be handled by your operating system.
> 
> web page for setting the timer from linux:
> https://www.linux.com/training-tutorials/wake-linux-rtc-alarm-clock/

That's very helpful, thanks.

I may play with it, however the factory reset on the plug seems to have
worked. 8am came and went without incident, so it looks like I can use
the plug as intended. However the BIOS option is there if it proves
unreliable.

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, report it: 
https://pagure.io/fedora-infrastructure/new_issue