Gnome-text-editor vs Gedit on Silverblue
by Lukas Ruzicka
Hello,
we have realized that Gedit has been replaced with Gnome-Text-Editor in
Rawhide and what now becomes Fedora 36. However, the last version of
Silverblue still uses Gedit.
Is that on purpose or should we report a bug?
--
Lukáš Růžička
FEDORA QE, RHCE
Red Hat
<https://www.redhat.com>
Purkyňova 115
612 45 Brno - Královo Pole
lruzicka(a)redhat.com
TRIED AND PERSONALLY TESTED, ERGO TRUSTED. <https://redhat.com/trusted>
2 years, 2 months
Fedora Workstation WG minutes, 2022-02-08
by Chris Murphy
==============================================
#fedora-meeting-2: Workstation WG (2022-02-08)
==============================================
Meeting started by brainycmurf at 23:56:59 UTC. The full logs are
available at
https://meetbot.fedoraproject.org/fedora-meeting-2/2022-02-08/workstation...
.
Meeting summary
---------------
* Present members: Chris, Matthias, Michael, Neal, Owen, Tomas, Jens,
Allan (brainycmurf, 23:57:12)
* Present guests: Sally (brainycmurf, 23:57:12)
* Regrets: (brainycmurf, 23:57:12)
* Missing: (brainycmurf, 23:57:12)
* Secretary: Jens (brainycmurf, 23:57:12)
* Outstanding pending actions, leftover from last week (brainycmurf,
23:57:13)
* 2m shutdown timer is too long (brainycmurf, 23:57:15)
* LINK: https://pagure.io/fedora-workstation/issue/163 (Matthias)
(brainycmurf, 23:57:17)
* Fedora PRD (brainycmurf, 23:57:19)
* LINK: https://pagure.io/fedora-workstation/issue/262 (brainycmurf,
23:57:23)
* Orchestration API (brainycmurf, 23:57:29)
* LINK: https://pagure.io/fedora-workstation/issue/268 (brainycmurf,
23:57:31)
* LINK: https://osquery.io/ (brainycmurf, 23:57:35)
* Ship preinstalled apps as Flatpaks (brainycmurf, 23:57:43)
* LINK: https://pagure.io/fedora-workstation/issue/269 (brainycmurf,
23:57:45)
* Announcements, status updates (brainycmurf, 23:58:13)
* F36 branching is today! (brainycmurf, 23:58:15)
* The minutes from last week have been posted online. (brainycmurf,
23:58:17)
* LINK:
https://meetbot.fedoraproject.org/fedora-meeting-2/2022-02-01/workstation...
(brainycmurf, 23:58:19)
Meeting ended at 23:58:52 UTC.
Action Items
------------
Action Items, by person
-----------------------
* **UNASSIGNED**
* (none)
People Present (lines said)
---------------------------
* brainycmurf (40)
* zodbot (7)
* Allan (0)
Generated by `MeetBot`_ 0.4
.. _`MeetBot`: https://fedoraproject.org/wiki/Zodbot#Meeting_Functions
2 years, 2 months
troubleshooting mDNS on Workstation edition
by Chris Murphy
fovo.local client -> Fedora Workstation 35 and Rawhide
fnuc.local remote -> Fedora Server 3
I connect to the server using PKI
ssh chris(a)fnuc.local
And it just connects. Viola. But when I reboot to Rawhide...
$ ssh chris(a)fnuc.local
ssh: Could not resolve hostname fnuc.local: Temporary failure in name resolution
$ avahi-resolve -nv fnuc.local
Server version: avahi 0.8; Host name: fovo.local
fnuc.local 10.0.0.249
Also I can't connect to Samba services on the same server. I usually
connect by going to Files, Other Locations, FNUC appears in the list,
I double click on it. On Fedora 35, I get an authentication dialog,
following a list of shares. On Fedora 36, I get "Unable to access
location, Failed to retrieve share list from server: Connection
refused".
The server, fnuc.local, journalctl -f logs not a single message for
these failures. And on the client, only systemd-resolved logs
anything, unless it's not running. And the resolution failure happens
whether resolved is running or not, so I have very little to go on why
this isn't working.
I'm kinda suspicious of recent nsswitch changes, but the nsswitch.conf
files are identical between the two.
--
Chris Murphy
2 years, 2 months
new release criterion proposal: Graphical package managers
by Kamil Paral
In blocker discussions during the F35 cycle, there were multiple arguments
about what exactly is and is not the required functionality of a graphical
package manager, and it was decided that we'd like to have an explicit
criterion covering those apps in detail. You can find a proposal for this
criterion below, and I'd like to hear your thoughts/concerns. This proposal
was already discussed (and fine-tuned) on the test list, so you can read
the existing discussion there [1] (and even an older one from November as
well [2]).
Please note that we already have package management partly covered in the
Basic criteria [3] and Beta criteria [4]. Please read those first,
including footnotes. The following new criterion is proposed against the
Final milestone:
~~~~~~~~~~~~~~~~~~~~
The default graphical package manager for a given software type must
appropriately:
* Install, remove and update software
* List locally-installed software coming from the official Fedora
repositories
* List available software (possibly in categories, a curated list, etc)
* Display metadata relevant to the selected software (e.g. the description,
screenshots, the size)
* Start the selected installed software
* Configure software sources by enabling/disabling pre-defined official
repositories and then adjust the available software pool accordingly
* Notify the user when system updates are available (taking into account
the intended frequency of such notifications)
The following must hold true:
* When multiple operations (covered by this criterion) are requested, all
of them must finish correctly. (It's also valid to inform the user that a
certain operation is not available at that moment, see the "Supported
functionality and design decisions" note).
* The displayed state of software or software sources must not differ from
their actual state. (E.g. an RPM package must not be shown as installed
when it is not, a repository must not be shown as disabled or missing when
it is enabled, etc).
* Usual GUI interactivity must not break operations covered by this
criterion. (E.g. when the GUI allows the user to click some buttons while
an operation is running, it must not break that operation).
* The package manager must never make the system enter an inconsistent or
unbootable state. (E.g. damage the local software database, remove wrong
system files, break the bootloader, etc).
Note: Supported functionality and design decisions
All requirements apply only if such a functionality is supported by the
package manager; it does not imply that the package manager must support
all this functionality. The requirements don't apply if some functionality
is intentionally modified as a design decision (e.g. if some software
sources can't be disabled as an intentional precaution to users breaking
their system). If there is a bug violating the design decisions in one of
the covered areas (e.g. a software source which is supposed to be always
enabled can be disabled), it's up to the blocker review team to consider
whether this bug makes the user experience or system safety considerably
worse.
Note: Systems in an inconsistent state
While the package manager must not be the primary cause for breaking a
system (unbootable, invalid internal structures, etc), it doesn't have to
'''prevent''' these events from happening. So if there's e.g. a power
outage during its operation or a package with harmful scriptlets is
installed, which breaks the system, this is not the fault of the package
manager and the criteria above are not considered violated. Similarly, when
the package manager operates on an already broken system (e.g. with an
inconsistent rpm database), the correct behavior cannot be guaranteed, and
therefore the criteria also don't apply.
Note: Refer to Basic footnotes
The footnotes for the [similar Basic criterion covering console tools][3]
regarding software types, 'appropriate' behavior, scope and so on are all
generally applicable to this criterion also.
~~~~~~~~~~~~~~~~~~~~
Please tell me if this sounds reasonable to you. Thank you.
[1]
https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.or...
[2]
https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.or...
[3]
https://fedoraproject.org/wiki/Basic_Release_Criteria#software-install-re...
[4]
https://fedoraproject.org/wiki/Fedora_35_Beta_Release_Criteria#Installing...
2 years, 2 months
GNOME 42 builds for F36: use f36-gnome side tag
by David King
Hi all
I am looking after GNOME builds this release cycle, as Kalev is away,
and I have requested a side tag for building GNOME packages intended for
F36. Please build updates of GNOME packages in the 42 series into the
f36-gnome side tag, using "fedpkg build –target=f36-gnome", or let me
know so that I can do the builds. There have been several API and ABI
breakages this GNOME release cycle, with ongoing porting work to GTK 4,
and there are likely to be a few more for the 42.beta release on the
12th of February. The side tag will help to coordinate those into a
single Bodhi update, especially as the GNOME release date is close to
the F36 branch point of the 8th of February.
Looking forward to the GNOME 42.rc release on the 5th of March, there is
a Freeze Exception bug to get that into 36 Beta:
https://bugzilla.redhat.com/show_bug.cgi?id=2049147
Again, please use the side tag so that landing the rc builds into the
beta can go smoothly.
Cheers
David
--
https://amigadave.com/
2 years, 2 months
Fedora Workstation WG minutes, 2022-02-01
by Chris Murphy
==============================================
#fedora-meeting-2: Workstation WG (2022-02-01)
==============================================
Meeting started by brainycmurf at 21:06:08 UTC. The full logs are
available at
https://meetbot.fedoraproject.org/fedora-meeting-2/2022-02-01/workstation...
.
Meeting summary
---------------
* Present members: Allan, Michael, Owen, Chris, Neal (brainycmurf,
21:06:31)
* Present guests: (brainycmurf, 21:06:31)
* Regrets: Tomas, Matthias (brainycmurf, 21:06:31)
* Missing: Jens (brainycmurf, 21:06:31)
* Secretary: Chris (brainycmurf, 21:06:31)
* Outstanding pending actions (brainycmurf, 21:06:31)
* 2m shutdown timer is too long (brainycmurf, 21:06:33)
* LINK: https://pagure.io/fedora-workstation/issue/163 (Matthias)
(brainycmurf, 21:06:35)
* Improve Fedora interoperability between Ethernet and WiFi
(brainycmurf, 21:06:39)
* LINK: https://pagure.io/fedora-workstation/issue/198 (Neal)
(brainycmurf, 21:06:43)
* ACTION: Neal (brainycmurf, 21:06:47)
* Consider limiting journal size (brainycmurf, 21:06:49)
* LINK: https://pagure.io/fedora-workstation/issue/213 (Chris)
(brainycmurf, 21:06:51)
* Add NetworkManager (or NetworkManager-wiifi) to protected packages
for workstation? (brainycmurf, 21:07:09)
* LINK: https://pagure.io/fedora-workstation/issue/260 (Michael)
(brainycmurf, 21:07:13)
* ACTION: Michael will make the change and update the ticket
(brainycmurf, 21:07:15)
* LINK: https://pagure.io/fedora-workstation/issue/242 (Neal)
(brainycmurf, 21:07:25)
* ACTION: Neal will work it this soon (brainycmurf, 21:07:27)
* Fedora PRD (brainycmurf, 21:07:29)
* LINK: https://pagure.io/fedora-workstation/issue/262 (brainycmurf,
21:07:31)
* Orchestration API (brainycmurf, 21:07:36)
* LINK: https://pagure.io/fedora-workstation/issue/268 (brainycmurf,
21:07:38)
* Ship preinstalled apps as Flatpaks (brainycmurf, 21:07:44)
* LINK: https://pagure.io/fedora-workstation/issue/269 (brainycmurf,
21:07:46)
* Announcements, status updates (brainycmurf, 21:07:50)
* CentOS Dojo @ FOSDEM 2022 https://fosdem.org/2022/ (brainycmurf,
21:07:52)
* LINK: https://hopin.com/events/centos-dojo-fosdem-2022
(brainycmurf, 21:07:54)
* GNOME UI freeze, Feb 12 (brainycmurf, 21:07:56)
Meeting ended at 21:08:28 UTC.
Action Items
------------
* Neal
* Michael will make the change and update the ticket
* Neal will work it this soon
Action Items, by person
-----------------------
* **UNASSIGNED**
* Neal
* Michael will make the change and update the ticket
* Neal will work it this soon
People Present (lines said)
---------------------------
* brainycmurf (47)
* zodbot (7)
* Allan (0)
Generated by `MeetBot`_ 0.4
.. _`MeetBot`: https://fedoraproject.org/wiki/Zodbot#Meeting_Functions
2 years, 2 months