Poweroff on Fedora 37

2023-05-04 Thread t_pol
Hi all.

Frequently "systemctl poweroff" does NOT really "power off" the machine but 
simply halts the system.

Reading manual I've also tried to add opttion -i (--check-inhibitors=no) but it 
happens anyway.

Is there any way to investigate the reason why this happens ?

Thanks in advance for any suggestion.

Angelo


Fedora: 37
Host:   HP Pavilion Laptop 15-cs0xxx
Kernel: 6.2.14-200.fc37.x86_64
DE: Xfce4 4.16.1
___
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: [solved] Re: Thunderbird black at first launch with F38

2023-05-04 Thread John Mellor

On 2023-05-04 02:01, Frederic Muller wrote:

On 04/05/2023 12:48, Samuel Sieb wrote:

On 5/3/23 21:07, Frederic Muller wrote:
Installed F38 about a week ago from scratch (wayland & GNOME). When 
I launch Thunderbird the first time at every session it starts as a 
black screen except for the title bar and then... I believe nothing 
happens but since I cannot see anything I close it. When I relaunch 
it everything works normally.


Not really a life threatening situation but I was wondering if it 
was possible to fix this. Any idea?


Are you running "Thunderbird" or "Thunderbird on Wayland"?
If you don't have the second one, try installing it.
"thunderbird-wayland" is the package.
___ 

Yes! That was exactly the problem. Thank you so much.


Excellent catch!  That fixed it for me too.  I upgraded from F37 to F38, 
and it did not require this extra package under F37.


There is probably a bug in the upgrade, as it should install the extra 
package to fix the problem.  However, I cannot find a bugzilla for 
reporting this 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: Thunderbird black at first launch with F38

2023-05-04 Thread Andre Robatino
After a clean F38 install, I use Thunderbird while in Wayland and it works 
normally, without the extra package. I only have thunderbird and 
thunderbird-librnp-rnp installed.
___
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: [solved] Re: Thunderbird black at first launch with F38

2023-05-04 Thread Samuel Sieb

On 5/4/23 05:53, John Mellor wrote:

On 2023-05-04 02:01, Frederic Muller wrote:

On 04/05/2023 12:48, Samuel Sieb wrote:

On 5/3/23 21:07, Frederic Muller wrote:
Installed F38 about a week ago from scratch (wayland & GNOME). When 
I launch Thunderbird the first time at every session it starts as a 
black screen except for the title bar and then... I believe nothing 
happens but since I cannot see anything I close it. When I relaunch 
it everything works normally.


Not really a life threatening situation but I was wondering if it 
was possible to fix this. Any idea?


Are you running "Thunderbird" or "Thunderbird on Wayland"?
If you don't have the second one, try installing it.
"thunderbird-wayland" is the package.
___ 

Yes! That was exactly the problem. Thank you so much.


Excellent catch!  That fixed it for me too.  I upgraded from F37 to F38, 
and it did not require this extra package under F37.


There is probably a bug in the upgrade, as it should install the extra 
package to fix the problem.  However, I cannot find a bugzilla for 
reporting this issue.


On F37, I can use either one, but I prefer to use the Wayland option so 
less things are using XWayland.  They both should work on F38 as well. 
You could file a bug in bugzilla if there isn't already one.

___
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


nvidia problem F37->F38 update

2023-05-04 Thread Neal Becker
Just updated my server F37->F38.  The display doesn't start (black screen
after boot).

journalctl shows many messages like:

May 04 14:32:00 nbecker8 kernel: nouveau :01:00.0: bus: MMIO read of
 FAULT at 616330 [ PRIVRING ]

nouveau?  This was running nvidia driver before the update (from rpmfusion).
Any ideas?

Thanks,
Neal
___
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: nvidia problem F37->F38 update

2023-05-04 Thread Jeffrey Walton
On Thu, May 4, 2023 at 2:38 PM Neal Becker  wrote:
>
> Just updated my server F37->F38.  The display doesn't start (black screen 
> after boot).
>
> journalctl shows many messages like:
>
> May 04 14:32:00 nbecker8 kernel: nouveau :01:00.0: bus: MMIO read of 
>  FAULT at 616330 [ PRIVRING ]
>
> nouveau?  This was running nvidia driver before the update (from rpmfusion).
> Any ideas?

I thought RPM Fusion released updates today. Have you updated today?

If not, then many folks are using `dnf update --allowerasing`.

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: nvidia problem F37->F38 update

2023-05-04 Thread Joe Zeff

On 05/04/2023 12:37 PM, Neal Becker wrote:


nouveau?  This was running nvidia driver before the update (from rpmfusion).
Any ideas?


Do you run kmod-nvidia or akmod?  If the former, the appropriate kmod 
might not be ready yet.  Just boot into the previous kernel, and stay 
there until the new kmod shows up.  If you're using the akmod, boot into 
a CLI so that neither Xorg or Wayland is running and as root run (I 
think) akmod --force and see what happens.  If it works, reboot; if 
there are errors, boot into the previous kernel and report this to the 
rpmfusion bugzilla.

___
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


display issue after f37 weekly patching.

2023-05-04 Thread home user

(f37)
I just finished doing my weekly "dnf upgrade" patches.  I then rebooted.

My workstation is acting like it has only 1 monitor (it has 2).
The display looks like a pixel is about twice as big as what it should be.  
That is, everything looks big.
The "NVIDIA X Server Settings" tool does not launch.

I don't know if this is related, but when I ran "rkhunter --check", it warned about several files.  
I then ran "rkhunter --propupd"; it seemed to run properly.  But then another run of "rkhunter 
--check" listed the same problems as the first run.

What's wrong?
What's the fix?

Bill.
___
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: nvidia problem F37->F38 update

2023-05-04 Thread Tim Evans

On 5/4/23 14:37, Neal Becker wrote:
Just updated my server F37->F38.  The display doesn't start (black 
screen after boot).


journalctl shows many messages like:

May 04 14:32:00 nbecker8 kernel: nouveau :01:00.0: bus: MMIO read of 
 FAULT at 616330 [ PRIVRING ]


nouveau?  This was running nvidia driver before the update (from rpmfusion).
Any ideas?


Had this happen to me as well.  Booted back to the last F37 kernel and 
problem went away.  Current F38 kernel (6.2.14-300.fc38.x86_64) works ok.

___
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: display issue after f37 weekly patching.

2023-05-04 Thread home user

On 5/4/23 12:59 PM, home user wrote:

(f37)
I just finished doing my weekly "dnf upgrade" patches.  I then rebooted.

My workstation is acting like it has only 1 monitor (it has 2).
The display looks like a pixel is about twice as big as what it should be.  
That is, everything looks big.
The "NVIDIA X Server Settings" tool does not launch.

I don't know if this is related, but when I ran "rkhunter --check", it warned about several files.  
I then ran "rkhunter --propupd"; it seemed to run properly.  But then another run of "rkhunter 
--check" listed the same problems as the first run.

What's wrong?
What's the fix?

Bill.


I just rebooted, this time watching for messages during boot.  There was one.  
It was too fast to catch the exact wording, but is was approximately
"NVIDIA kernel module missing.  falling back to nouveau".
With another reboot, this time using the next older kernel in the grub menu, 
has both displays up and looking fine.
___
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


Messages held for moderation.

2023-05-04 Thread Jonathan Ryshpan
I have two messages held for moderation, each reported with the
following message. One of them is 53,454 bytes, the other is  44,018
bytes. What's going on?

I would not normally trouble the list about this, but they have been
pending for two days and there seems to be no way to reach the
moderator.

 Forwarded Message 
From: users-boun...@lists.fedoraproject.org
To: jonr...@pacbell.net
Subject: Your message to users@lists.fedoraproject.org awaits moderator
approval
Date: 05/02/2023 12:08:56 PM

Your mail to 'users@lists.fedoraproject.org' with the subject
    Re: Systemd Unit Fails at Boot, but Succeeds when Started from the
Console
Is being held until the list moderator can review it for approval.
The message is being held because:
    The message is larger than the 60 KB maximum size

Either the message will get posted to the list, or you will receive 
notification of the moderator's decision.

-- 
Sincerely Jonathan Ryshpan 

 Necessity is the excuse for every infringement of 
 human freedom. It is the argument of the tyrant 
 and the creed of the slave. -- Wm. Pitt the Elder
___
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: nvidia problem F37->F38 update

2023-05-04 Thread Neal Becker
On Thu, May 4, 2023 at 3:09 PM Tim Evans  wrote:

> On 5/4/23 14:37, Neal Becker wrote:
> > Just updated my server F37->F38.  The display doesn't start (black
> > screen after boot).
> >
> > journalctl shows many messages like:
> >
> > May 04 14:32:00 nbecker8 kernel: nouveau :01:00.0: bus: MMIO read of
> >  FAULT at 616330 [ PRIVRING ]
> >
> > nouveau?  This was running nvidia driver before the update (from
> rpmfusion).
> > Any ideas?
>
> Had this happen to me as well.  Booted back to the last F37 kernel and
> problem went away.  Current F38 kernel (6.2.14-300.fc38.x86_64) works ok.
>

Well I did boot from previous kernel, in this case 6.2.14-200.fc37.x86_64
(don't have an older fc38 kernel, I wasn't able to update to F38 until
today), and display is working fine.  I may have another problem but time
will tell (running on the newer kernel connecting via ssh several times
I've walked away and then the machine is nonresponsive to ping, have to
force power cycle to recover.)
___
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: [solved] Re: Thunderbird black at first launch with F38

2023-05-04 Thread John Mellor

On 2023-05-04 12:11, Samuel Sieb wrote:

On 5/4/23 05:53, John Mellor wrote:

On 2023-05-04 02:01, Frederic Muller wrote:

On 04/05/2023 12:48, Samuel Sieb wrote:

On 5/3/23 21:07, Frederic Muller wrote:
Installed F38 about a week ago from scratch (wayland & GNOME). 
When I launch Thunderbird the first time at every session it 
starts as a black screen except for the title bar and then... I 
believe nothing happens but since I cannot see anything I close 
it. When I relaunch it everything works normally.


Not really a life threatening situation but I was wondering if it 
was possible to fix this. Any idea?


Are you running "Thunderbird" or "Thunderbird on Wayland"?
If you don't have the second one, try installing it.
"thunderbird-wayland" is the package.
___ 

Yes! That was exactly the problem. Thank you so much.


Excellent catch!  That fixed it for me too.  I upgraded from F37 to 
F38, and it did not require this extra package under F37.


There is probably a bug in the upgrade, as it should install the 
extra package to fix the problem.  However, I cannot find a bugzilla 
for reporting this issue.


On F37, I can use either one, but I prefer to use the Wayland option 
so less things are using XWayland.  They both should work on F38 as 
well. You could file a bug in bugzilla if there isn't already one.


Bug report filed: https://bugzilla.redhat.com/show_bug.cgi?id=2193245

___
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: Messages held for moderation.

2023-05-04 Thread Kevin Fenzi
On Thu, May 04, 2023 at 12:59:14PM -0700, Jonathan Ryshpan wrote:
> I have two messages held for moderation, each reported with the
> following message. One of them is 53,454 bytes, the other is  44,018
> bytes. What's going on?

With headers and overhead, mailman is seeing them as 60k which is the
limit. Can you resend them and instead of content, provide links to
large items?

> I would not normally trouble the list about this, but they have been
> pending for two days and there seems to be no way to reach the
> moderator.

You can reach the moderators at users-ow...@lists.fedoraproject.org.

I did mail some folks about large emails this morning, but I didn't get
to yours. 

kevin
--
>  Forwarded Message 
> From: users-boun...@lists.fedoraproject.org
> To: jonr...@pacbell.net
> Subject: Your message to users@lists.fedoraproject.org awaits moderator
> approval
> Date: 05/02/2023 12:08:56 PM
> 
> Your mail to 'users@lists.fedoraproject.org' with the subject
>     Re: Systemd Unit Fails at Boot, but Succeeds when Started from the
> Console
> Is being held until the list moderator can review it for approval.
> The message is being held because:
>     The message is larger than the 60 KB maximum size
> 
> Either the message will get posted to the list, or you will receive 
> notification of the moderator's decision.
> 
> -- 
> Sincerely Jonathan Ryshpan 
> 
>  Necessity is the excuse for every infringement of 
>  human freedom. It is the argument of the tyrant 
>  and the creed of the slave. -- Wm. Pitt the Elder

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



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


Re: nvidia problem F37->F38 update

2023-05-04 Thread Tim via users
On Thu, 2023-05-04 at 16:20 -0400, Neal Becker wrote:

> I may have another problem but time will tell (running on the newer
> kernel connecting via ssh several times I've walked away and then the
> machine is nonresponsive to ping, have to force power cycle to
> recover.)

Are you falling foul of the recent Gnome change that puts a machine to
sleep if it considers that it's been idle for about 15 minutes?

One of the all-time *DUMB* moves by Gnome.
 
-- 
 
NB:  All unexpected mail to my mailbox is automatically deleted.
I will only get to see the messages that are posted to the list.
 
The following system info data is generated fresh for each post:
 
uname -rsvp
Linux 6.2.14-100.fc36.x86_64 #1 SMP PREEMPT_DYNAMIC Mon May  1 00:54:35
UTC 2023 x86_64
___
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: Messages held for moderation.

2023-05-04 Thread Todd Zullinger
Jonathan Ryshpan wrote:
> I have two messages held for moderation, each reported with the
> following message. One of them is 53,454 bytes, the other is  44,018
> bytes. What's going on?
> 
> I would not normally trouble the list about this, but they have been
> pending for two days and there seems to be no way to reach the
> moderator.

Sorry for the delay.

If we could, we'd probably have the list reject instead of
hold, as there's generally not much chance we will approve
large messages.  But that's not something we can configure
at the list admin level in mailman (AFAIK).

It's better to trim the output than wait for the messages to
be approved or rejected.

The list owners / moderators can be reached via the
${list}-ow...@lists.fedoraproject.org.  The list info page
does include this information.

-- 
Todd


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


Re: nvidia problem F37->F38 update

2023-05-04 Thread Todd Zullinger
Tim via users wrote:
> On Thu, 2023-05-04 at 16:20 -0400, Neal Becker wrote:
> 
>> I may have another problem but time will tell (running on the newer
>> kernel connecting via ssh several times I've walked away and then the
>> machine is nonresponsive to ping, have to force power cycle to
>> recover.)
> 
> Are you falling foul of the recent Gnome change that puts a machine to
> sleep if it considers that it's been idle for about 15 minutes?
> 
> One of the all-time *DUMB* moves by Gnome.

And if so, this post in the Common Issues area should help
adjust the settings:

https://discussion.fedoraproject.org/t/gnome-suspends-after-15-minutes-of-user-inactivity-even-on-ac-power/79801

This doesn't affect Fedora Server, so if the system is only
used as a server, installing from the Server image instead
of Workstation might help avoid any future changes which are
aimed at laptop/desktop users. (I don't care for this change
either way -- but it's much easier to deal with on a local
system than a remote server.)

-- 
Todd


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


Re: nvidia problem F37->F38 update

2023-05-04 Thread Neal Becker
On Thu, May 4, 2023 at 5:50 PM Todd Zullinger  wrote:

> Tim via users wrote:
> > On Thu, 2023-05-04 at 16:20 -0400, Neal Becker wrote:
> >
> >> I may have another problem but time will tell (running on the newer
> >> kernel connecting via ssh several times I've walked away and then the
> >> machine is nonresponsive to ping, have to force power cycle to
> >> recover.)
> >
> > Are you falling foul of the recent Gnome change that puts a machine to
> > sleep if it considers that it's been idle for about 15 minutes?
> >
> > One of the all-time *DUMB* moves by Gnome.
>
> And if so, this post in the Common Issues area should help
> adjust the settings:
>
>
> https://discussion.fedoraproject.org/t/gnome-suspends-after-15-minutes-of-user-inactivity-even-on-ac-power/79801
>
> This doesn't affect Fedora Server, so if the system is only
> used as a server, installing from the Server image instead
> of Workstation might help avoid any future changes which are
> aimed at laptop/desktop users. (I don't care for this change
> either way -- but it's much easier to deal with on a local
> system than a remote server.)
>
> This is used as a server and only usually accessed remotely.  Would this
shutdown the machine even if nobody had logged in at the
console display?
___
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: nvidia problem F37->F38 update

2023-05-04 Thread Neal Becker
On Thu, May 4, 2023 at 6:13 PM Neal Becker  wrote:

>
>
> On Thu, May 4, 2023 at 5:50 PM Todd Zullinger  wrote:
>
>> Tim via users wrote:
>> > On Thu, 2023-05-04 at 16:20 -0400, Neal Becker wrote:
>> >
>> >> I may have another problem but time will tell (running on the newer
>> >> kernel connecting via ssh several times I've walked away and then the
>> >> machine is nonresponsive to ping, have to force power cycle to
>> >> recover.)
>> >
>> > Are you falling foul of the recent Gnome change that puts a machine to
>> > sleep if it considers that it's been idle for about 15 minutes?
>> >
>> > One of the all-time *DUMB* moves by Gnome.
>>
>> And if so, this post in the Common Issues area should help
>> adjust the settings:
>>
>>
>> https://discussion.fedoraproject.org/t/gnome-suspends-after-15-minutes-of-user-inactivity-even-on-ac-power/79801
>>
>> This doesn't affect Fedora Server, so if the system is only
>> used as a server, installing from the Server image instead
>> of Workstation might help avoid any future changes which are
>> aimed at laptop/desktop users. (I don't care for this change
>> either way -- but it's much easier to deal with on a local
>> system than a remote server.)
>>
>> This is used as a server and only usually accessed remotely.  Would this
> shutdown the machine even if nobody had logged in at the
> console display?
>

Just to clarify, it is used as a server but workstation edition is
installed on 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, report it: 
https://pagure.io/fedora-infrastructure/new_issue


Re: nvidia problem F37->F38 update

2023-05-04 Thread Samuel Sieb

On 5/4/23 15:14, Neal Becker wrote:


On Thu, May 4, 2023 at 6:13 PM Neal Becker > wrote:


On Thu, May 4, 2023 at 5:50 PM Todd Zullinger mailto:t...@pobox.com>> wrote:
This doesn't affect Fedora Server, so if the system is only
used as a server, installing from the Server image instead
of Workstation might help avoid any future changes which are
aimed at laptop/desktop users. (I don't care for this change
either way -- but it's much easier to deal with on a local
system than a remote server.)

This is used as a server and only usually accessed remotely.  Would
this shutdown the machine even if nobody had logged in at the
console display?


Just to clarify, it is used as a server but workstation edition is 
installed on it.


If it's sitting at the GDM login screen, then it will automatically 
suspend after 15 minutes.

___
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: nvidia problem F37->F38 update

2023-05-04 Thread Joe Zeff

On 05/04/2023 04:13 PM, Neal Becker wrote:


This is used as a server and only usually accessed remotely.


In that case, why have a GUI active at all unless you're on site? 
Having it boot to a CLI eliminates the problem, doesn't 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, report it: 
https://pagure.io/fedora-infrastructure/new_issue


Re: Messages held for moderation.

2023-05-04 Thread Jonathan Ryshpan
On Thu, 2023-05-04 at 17:42 -0400, Todd Zullinger wrote:
> Jonathan Ryshpan wrote:
> > I have two messages held for moderation, each reported with the
> > following message. One of them is 53,454 bytes, the other is  44,018
> > bytes. What's going on?
> > 
> > I would not normally trouble the list about this, but they have been
> > pending for two days and there seems to be no way to reach the
> > moderator.
> 
> Sorry for the delay.
> 
> If we could, we'd probably have the list reject instead of
> hold, as there's generally not much chance we will approve
> large messages.  But that's not something we can configure
> at the list admin level in mailman (AFAIK).
> 
> It's better to trim the output than wait for the messages to
> be approved or rejected.
> 
> The list owners / moderators can be reached via the
> ${list}-ow...@lists.fedoraproject.org.  The list info page
> does include this information.

I see; the headers to your last message amount to about 10 Kbytes. But I
would have expected that even with headers, a message of about 44 Kbytes
would be under 60 Kbytes. I already trimmed the text size down from
about 53 Kbytes to abpit 44 Kbytes.

I guess a message of more than about 30 Kbytes of text should not be
expected to go through. In the future I will save long files to Google
Docs and send a link. Bother!


-- 
Sincerely Jonathan Ryshpan 

Never attribute to malice that which is adequately explained by
stupidity.
 -- Hanlon's razor
___
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


F38 update, chrome display problem

2023-05-04 Thread Neal Becker
After updating f37->f38, now chrome-stable is unusable.  This is intel
graphics.
The displays of all web pages are unreadable.

I tried installing google-chrome-beta, and this seems to be working fine.

Any thoughts?

Thanks,
Neal
___
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: Messages held for moderation.

2023-05-04 Thread Todd Zullinger
Jonathan Ryshpan wrote:
> I see; the headers to your last message amount to about 10 Kbytes. But I
> would have expected that even with headers, a message of about 44 Kbytes
> would be under 60 Kbytes. I already trimmed the text size down from
> about 53 Kbytes to abpit 44 Kbytes.

If you're measuring the size of the file you're attaching,
you have to add ~33% for base64 encoding.  That bloats
things a bit.

I don't _think_ the headers are counted by the list
software, but I haven't confirmed that in the code.

At the same time, even 30kb of text is quite a bit of
output.  Usually, that's more than enough details.  Not
always, I'm sure. :)

-- 
Todd


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


Re: Request for recommendations on installing Viber and Signal

2023-05-04 Thread Samuel Sieb

On 4/30/23 05:55, Max Pyziur wrote:

Per the subject line any recommendations on F38 would be helpful.

I had both installed on my Dell XPS 13 L322 laptop, but bc the upgrade 
failed I've had to do a fresh install and restore my data.


Viber does provide an rpm:
rpm can be found here https://www.viber.com/en/download/ (look under the 
Windows & others section for the Fedora version)


Instructions here: 
https://help.viber.com/en/article/set-up-viber-on-your-desktop


However, it fails on my laptop with no clear guidance on why or what 
dependencies are missing.


How do you expect to get useful advice without describing what you tried 
and pasting the error message?

___
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


Kernel 6.3 Test Week 2023-05-07

2023-05-04 Thread Sumantro Mukherjee
Hey All,

I would like to invite all of you to participate in the Kernel 6.3
Test week is happening from 2023-05-07 to 2023-05-14. It's
fairly simple, head over to the wiki [0] and read in detail about the
test week and simply run the test case mentioned in[1] and enter your
results.

As usual, the Fedora QA team will hangout at #fedora-test-...@libera.chat
for question and discussion.

[0] http://fedoraproject.org/wiki/Test_Day:2023-05-07_Kernel_6.3_Test_Week
[1] https://testdays.fedoraproject.org/events/157


-- 
//sumantro
Fedora QE
TRIED AND PERSONALLY TESTED, ERGO TRUSTED
___
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: Kernel 6.3 Test Week 2023-05-07

2023-05-04 Thread Luna Jernberg
Just got a new old Thinkpad Edge from 2010 running Fedora 38 with
testing updates, so will help to do some testing on that :)

On Fri, May 5, 2023 at 8:45 AM Sumantro Mukherjee  wrote:
>
> Hey All,
>
> I would like to invite all of you to participate in the Kernel 6.3
> Test week is happening from 2023-05-07 to 2023-05-14. It's
> fairly simple, head over to the wiki [0] and read in detail about the
> test week and simply run the test case mentioned in[1] and enter your
> results.
>
> As usual, the Fedora QA team will hangout at #fedora-test-...@libera.chat
> for question and discussion.
>
> [0] http://fedoraproject.org/wiki/Test_Day:2023-05-07_Kernel_6.3_Test_Week
> [1] https://testdays.fedoraproject.org/events/157
>
>
> --
> //sumantro
> Fedora QE
> TRIED AND PERSONALLY TESTED, ERGO TRUSTED
> ___
> test mailing list -- t...@lists.fedoraproject.org
> To unsubscribe send an email to test-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/t...@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