sddm-greeter pss > 2GB
by Adrian Sevcenco
Hi! I just upgraded a station from f29->f32->f35. this is a dual nvidia graphics card
with 3 monitors each.
I had to switch from kdm to sddm as i had some strange error in initialization of xorg,
now this seems ok but sddm-greeter pss is more than 2 GB ram!!!!
I think this is insane, does anyone seen this?
Thanks a lot!
Adrian
2 years
KDE manual session saving seems to be missing
by George R Goffe
Hi,
I haven't used KDE in some time and am trying it again now.
I can't seem to find where sessions can be saved.
Am I missing something? Doing something wrong?
Any/all hints tips suggestions would be greatly appreciated.
Best regards and STAY SAFE!
George...
2 years
Re: KDE manual session saving seems to be missing
by George R Goffe
Patrick,
Thank you for responding.
I think I'm using X11 since I manually issue a "startx" command and am using my ".xinitrc" file.
How do you start Wayland? How do you tell if you're running Wayland
Best regards,
George...
By the way, one of "our" other mailing list viewers (Sérgio Basto <sergio(a)serjux.com>) pointed me to this solution and it's working GREAT. Thanks to him AND you for your help!
On Tuesday, March 1, 2022, 08:04:35 PM PST, <kde-request(a)lists.fedoraproject.org> wrote:
2 years
Re: KDE manual session saving seems to be missing
by George R Goffe
Sergio,
Thanks for your help. I'll test it later today.
Regards,
George...
On Tuesday, March 1, 2022, 02:26:07 PM PST, Sérgio Basto <sergio(a)serjux.com> wrote:
On Tue, 2022-03-01 at 21:46 +0000, George R Goffe wrote:
> Sergio,
>
> Thanks for responding.
>
> I have set "restore manually saved session " in system settings and
> have logged out/rebooted several times... without success. As I seem
> to recall, the manually save session was in system settings also but
> do not see it.
system settings -> startup and shutdown -> desktop session
> Am I looking in the "right" area? You mention "the menu" but didn't
> say which menu. Could you be more explicit please?
>
I use the widget "Application launcher", see in attach
> Best regards,
>
> George...
>
>
>
>
>
>
>
> On Tuesday, March 1, 2022, 01:38:56 PM PST, Sérgio Basto
> <sergio(a)serjux.com> wrote:
>
>
>
>
>
> On Tue, 2022-03-01 at 21:28 +0000, George R Goffe wrote:
> > Hi,
> >
> > I haven't used KDE in some time and am trying it again now.
> >
> > I can't seem to find where sessions can be saved.
> >
> > Am I missing something? Doing something wrong?
> >
> > Any/all hints tips suggestions would be greatly appreciated.
>
> I found, after set "restore manually saved session " in system
> settings
> -> startupp and shutdown -> desktop session . we need logout and
> login
> again to appear "save manual session" in menu
>
>
> > Best regards and STAY SAFE!
> >
> > George...
>
> > _______________________________________________
> > kde mailing list -- kde(a)lists.fedoraproject.org
> > To unsubscribe send an email to kde-leave(a)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/kde@lists.fedoraproject.org
> > Do not reply to spam on the list, report it:
> > https://pagure.io/fedora-infrastructure
>
--
Sérgio M. B.
2 years
Release criteria proposal: networking requirements
by Adam Williamson
Hi folks!
So at this week's blocker review meeting, the fact that we don't have
explicit networking requirements in the release criteria really started
to bite us. In the past we have squeezed networking-related issues in
under other criteria, but for some issues that's really difficult,
notably VPN issues. So, we agreed we should draft some explicit
networking criteria.
This turns out to be a big area and quite hard to cover (who'd've
thought!), but here is at least a first draft for us to start from. My
proposal would be to add this to the Basic criteria. I have left out
some wikitext stuff from the proposal for clarity; I'd add it back in
on actually applying the proposed changes. It's just formatting stuff,
nothing that'd change the meaning. Anyone have thoughts, complaints,
alternative approaches, supplements? Thanks!
=== Network requirements ===
Each of these requirements apply to both installer and installed system
environments. For any given installer environment, the 'default network
configuration tools' are considered to be those the installer documents
as supported ways to configure networking (e.g. for anaconda-based
environments, configuration via kernel command line options, a
kickstart, or interactively in anaconda itself are included).
==== Basic networking ====
It must be possible to establish both IPv4 and IPv6 network connections
using DHCP and static addressing. The default network configuration
tools for the console and for release-blocking desktops must work well
enough to allow typical network connection configuration operations
without major workarounds. Standard network functions such as address
resolution and connections with common protocols such as ping, HTTP and
ssh must work as expected.
Footnote titled "Supported hardware": Supported network hardware is
hardware for which the Fedora kernel includes drivers and, where
necessary, for which a firmware package is available. If support for a
commonly-used piece or type of network hardware that would usually be
present is omitted, that may constitute a violation of this criterion,
after consideration of the [[Blocker_Bug_FAQ|hardware-dependent-
issues|normal factors for hardware-dependent issues]]. Similarly,
violations of this criteria that are hardware or configuration
dependent are, as usual, subject to consideration of those factors when
determining whether they are release-blocking
==== VPN connections ====
Using the default network configuration tools for the console and for
release-blocking desktops, it must be possible to establish a working
connection to common OpenVPN, openconnect-supported and vpnc-supported
VNC servers with typical configurations.
Footnote title "Supported servers and configurations": As there are
many different VPN server applications and configurations, blocker
reviewers must use their best judgment in determining whether
violations of this criterion are likely to be encountered commonly
enough to block a release, and if so, at which milestone. As a general
principle, the more people are likely to use affected servers and the
less complicated the configuration required to hit the bug, the more
likely it is to be a blocker.
--
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
http://www.happyassassin.net
2 years