2023-03-20 @ **16:00** UTC - Fedora 38 Blocker Review Meeting
by Adam Williamson
# F37 Blocker Review meeting
# Date: 2023-03-20
# Time: **16:00** UTC
# Location: #fedora-blocker-review on irc.libera.chat
Hi folks! We have 5 proposed Final blockers to review, so let's have a
review meeting.
Remember that clocks went forward in North America last weekend, so
the meeting time in UTC is an hour earlier than before. If you do not
observe daylight savings time, or your clocks did not yet go forward,
the meeting will be an hour earlier in your local time. Please double
check!
If you have time this weekend, you can take a look at the proposed or
accepted blockers before the meeting - the full lists can be found
here: https://qa.fedoraproject.org/blockerbugs/ .
Remember, you can also now vote on bugs outside of review meetings! If
you look at the bug list in the blockerbugs app, you'll see links
labeled "Vote!" next to all proposed blockers and freeze exceptions.
Those links take you to tickets where you can vote.
https://pagure.io/fedora-qa/blocker-review has instructions on how
exactly you do it. We usually go through the tickets shortly before the
meeting and apply any clear votes, so the meeting will just cover bugs
where there wasn't a clear outcome in the ticket voting yet. **THIS
MEANS IF YOU VOTE NOW, THE MEETING WILL BE SHORTER!**
We'll be evaluating these bugs to see if they violate any of the
Release Criteria and warrant the blocking of a release if they're not
fixed. Information on the release criteria for F38 can be found on the
wiki [0].
For more information about the Blocker and Freeze exception process,
check out these links:
- https://fedoraproject.org/wiki/QA:SOP_blocker_bug_process
- https://fedoraproject.org/wiki/QA:SOP_freeze_exception_bug_process
And for those of you who are curious how a Blocker Review Meeting
works - or how it's supposed to go and you want to run one - check out
the SOP on the wiki:
- https://fedoraproject.org/wiki/QA:SOP_Blocker_Bug_Meeting
Have a good day and see you tomorrow!
[0] https://fedoraproject.org/wiki/Fedora_Release_Criteria
--
Adam Williamson (he/him/his)
Fedora QA
Fedora Chat: @adamwill:fedora.im | Mastodon: @adamw(a)fosstodon.org
https://www.happyassassin.net
5 days, 6 hours
Mount filesystem
by Mark ＠ GMail
What's the best way to mount remote filesystems?
I'm using nfs but it seems really slow and when I mentioned it (here?
somewhere else?) there was a quite negative response about nfs itself.
It's possible I'm just seeing the difference between my local (solid
state) disk on a fast machine and the remote (spinny disk) filesystem
on a slower remote machine (they're only about six inches apart on a
1Gb network connection, so it's not *very* remote). However, with
"remote" website directories mounted locally they're much slower with
my local webserver than with the one on that slower machine, so I'm
inclined to suspect nfs... is that unfair?
(I know this isn't a particularly KDE related issue. Please don't make
me rejoin the Fedora list, they're really mean!)
Both machines are running F37, both updated every week.
5 days, 18 hours
konq clumsiness on startup as file manager
by John Pilkington
I have 'always' used konq for file management and viewing. Currently
with the SL7 el7 clone and Fedora 36. At least since the move to kde5,
IIRC, on startup konq has not gone to the expected folder, but Bookmarks
have worked and it has remained usable.
Since the massive F36 kde updates on 26 Feb this year I have had
problems with occasional system freezes, covered here in other threads,
but also in konq, which now starts, after a pause, in a duckduckgo
screen about inodes. I've been getting more familiar with journalctl;
here's an annotated log of konq startup, going to a bookmark, and
quitting. Perhaps it will reveal something useful.
John P
{{{
[john@HPFed ~]$ sudo SYSTEMD_COLORS=false journalctl -f
Mar 16 11:01:51 HPFed sudo[42990]: pam_unix(sudo:session): session
opened for user root(uid=0) by john(uid=1000)
Mar 16 11:02:15 HPFed sudo[42990]: pam_unix(sudo:session): session
closed for user root
Mar 16 11:02:15 HPFed audit[42990]: USER_END pid=42990 uid=1000
auid=1000 ses=3 subj=kernel msg='op=PAM:session_close
grantors=pam_keyinit,pam_limits,pam_keyinit,pam_limits,pam_systemd,pam_unix
acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/5
res=success'
Mar 16 11:02:15 HPFed audit[42990]: CRED_DISP pid=42990 uid=1000
auid=1000 ses=3 subj=kernel msg='op=PAM:setcred grantors=pam_unix
acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/5
res=success'
### Start response to keyboard command
Mar 16 11:02:30 HPFed audit[43015]: USER_ACCT pid=43015 uid=1000
auid=1000 ses=3 subj=kernel msg='op=PAM:accounting
grantors=pam_unix,pam_localuser acct="john" exe="/usr/bin/sudo"
hostname=? addr=? terminal=/dev/pts/5 res=success'
Mar 16 11:02:30 HPFed audit[43015]: USER_CMD pid=43015 uid=1000
auid=1000 ses=3 subj=kernel msg='cwd="/home/john"
cmd=6A6F75726E616C63746C202D66 exe="/usr/bin/sudo" terminal=pts/5
res=success'
Mar 16 11:02:30 HPFed sudo[43015]: john : TTY=pts/5 ; PWD=/home/john
; USER=root ; ENV=SYSTEMD_COLORS=false ; COMMAND=/bin/journalctl -f
Mar 16 11:02:30 HPFed audit[43015]: CRED_REFR pid=43015 uid=1000
auid=1000 ses=3 subj=kernel msg='op=PAM:setcred
grantors=pam_env,pam_unix acct="root" exe="/usr/bin/sudo" hostname=?
addr=? terminal=/dev/pts/5 res=success'
Mar 16 11:02:30 HPFed sudo[43015]: pam_unix(sudo:session): session
opened for user root(uid=0) by john(uid=1000)
Mar 16 11:02:30 HPFed audit[43015]: USER_START pid=43015 uid=1000
auid=1000 ses=3 subj=kernel msg='op=PAM:session_open
grantors=pam_keyinit,pam_limits,pam_keyinit,pam_limits,pam_systemd,pam_unix
acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/5
res=success'
### Click on konq ikon in taskbar
### konq starts, pauses, and displays
https://duckduckgo.com/?q=inode%2Fdirectory&t=kde&ia=web
### Select local folder from Bookmarks. Display is as expected
Mar 16 11:03:47 HPFed plasmashell[1642]:
file:///usr/share/plasma/plasmoids/org.kde.plasma.taskmanager/contents/ui/Task.qml:286:
Unable to assign [undefined] to QString
Mar 16 11:03:47 HPFed systemd[1499]: Started
app-kfmclient_dir-2cebe43f8e634c9e9acbefb9265f51ef.scope - Konqueror.
Mar 16 11:03:47 HPFed plasmashell[1642]:
file:///usr/share/plasma/plasmoids/org.kde.plasma.taskmanager/contents/ui/Task.qml:286:
Unable to assign [undefined] to QString
Mar 16 11:03:47 HPFed plasmashell[43060]: Launched ok, pid = 43062
Mar 16 11:03:54 HPFed konqueror[43062]: kf.service.services:
KApplicationTrader: mimeType "x-scheme-handler/konq" not found
Mar 16 11:04:12 HPFed konqueror[43062]: QFSFileEngine::open: No file
name specified
Mar 16 11:04:23 HPFed konqueror[43062]: QWidget::insertAction: Attempt
to insert null action
Mar 16 11:04:23 HPFed konqueror[43062]: QWidget::insertAction: Attempt
to insert null action
Mar 16 11:04:23 HPFed konqueror[43062]: QWidget::insertAction: Attempt
to insert null action
Mar 16 11:04:23 HPFed konqueror[43062]: kf.kio.core: Url
QUrl("file:///var/RSG4/TScut_work") already represents a local file,
cancelling job.
#### konq File -> Quit
Mar 16 11:05:16 HPFed konqueror[43062]: QDBusConnection: error: could
not send signal to service "" path "//tmp/closeditems/_1.225" interface
"org.kde.kconfig.notify" member "ConfigChanged": Invalid object path:
//tmp/closeditems/_1.225
Mar 16 11:05:16 HPFed konqueror[43062]: QDBusConnection: error: could
not send signal to service "" path
"//home/john/.local/share/konqueror/closeditems_saved" interface
"org.kde.kconfig.notify" member "ConfigChanged": Invalid object path:
//home/john/.local/share/konqueror/closeditems_saved
Mar 16 11:05:16 HPFed konqueror[43062]: QDBusConnection: error: could
not send signal to service "" path
"//home/john/.local/share/konqueror/closeditems_saved" interface
"org.kde.kconfig.notify" member "ConfigChanged": Invalid object path:
//home/john/.local/share/konqueror/closeditems_saved
Mar 16 11:05:16 HPFed konqueror[43062]: QDBusConnection: error: could
not send signal to service "" path "//tmp/closeditems/_1.225" interface
"org.kde.kconfig.notify" member "ConfigChanged": Invalid object path:
//tmp/closeditems/_1.225
^C
[john@HPFed ~]$
}}}
6 days, 21 hours
Re: System going unresponsive after ... updates
by John Pilkington
On 15/03/2023 12:41, John Pilkington wrote:
> On 15/03/2023 11:31, Marc Deop i Argemí wrote:
>> On Wednesday, 15 March 2023 11:06:32 CET John Pilkington wrote:
>>> The freezes are still happening,
>>
>> Seems like some process is asking for real time priority and causing
>> freezes.
>>
>> mythbackend perhaps?
Resending this to the list, with addition
Looking more closely at the timestamps, I suppose the anacron and dnf
items probably show just because they happen, rather than because they
cause the problem. I suppose it might be mythtv deleting an old
recording to make space. Whatever it is, it's only a few weeks old.
>>
> It looks more related to anacron or dnf-makecache to me. Looking
> before the canary and ignoring dvb-firmware servicing shows this
>
>
> {{{
> [john@HPFed ~]$ sudo SYSTEMD_COLORS=false journalctl --since -10d | grep
> -v tda1004 | grep -B 6 canary
> Mar 07 18:09:19 HPFed systemd[1]: Starting dnf-makecache.service - dnf
> makecache...
> Mar 07 18:09:31 HPFed dnf[59527]: Metadata cache refreshed recently.
> Mar 07 18:09:31 HPFed systemd[1]: dnf-makecache.service: Deactivated
> successfully.
> Mar 07 18:09:31 HPFed audit[1]: SERVICE_START pid=1 uid=0
> auid=4294967295 ses=4294967295 subj=kernel msg='unit=dnf-makecache
> comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=?
> terminal=? res=success'
> Mar 07 18:09:31 HPFed audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295
> ses=4294967295 subj=kernel msg='unit=dnf-makecache comm="systemd"
> exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
> Mar 07 18:09:31 HPFed systemd[1]: Finished dnf-makecache.service - dnf
> makecache.
> Mar 07 18:54:38 HPFed rtkit-daemon[903]: The canary thread is apparently
> starving. Taking action.
> --
> Mar 10 01:01:03 HPFed run-parts[71108]: (/etc/cron.hourly) starting
> 0anacron
> Mar 10 01:01:04 HPFed run-parts[71118]: (/etc/cron.hourly) finished
> 0anacron
> Mar 10 01:01:04 HPFed CROND[71104]: (root) CMDEND (run-parts
> /etc/cron.hourly)
> Mar 10 01:01:04 HPFed anacron[71116]: Anacron started on 2023-03-10
> Mar 10 01:01:04 HPFed anacron[71116]: Normal exit (0 jobs run)
> Mar 10 01:25:08 HPFed cupsd[1118]: REQUEST localhost - - "POST /
> HTTP/1.1" 200 183 Renew-Subscription successful-ok
> Mar 10 01:58:04 HPFed rtkit-daemon[909]: The canary thread is apparently
> starving. Taking action.
> --
> Mar 13 01:01:03 HPFed CROND[68649]: (root) CMD (run-parts /etc/cron.hourly)
> Mar 13 01:01:08 HPFed run-parts[68652]: (/etc/cron.hourly) starting
> 0anacron
> Mar 13 01:01:09 HPFed anacron[68662]: Anacron started on 2023-03-13
> Mar 13 01:01:09 HPFed run-parts[68664]: (/etc/cron.hourly) finished
> 0anacron
> Mar 13 01:01:09 HPFed CROND[68648]: (root) CMDEND (run-parts
> /etc/cron.hourly)
> Mar 13 01:01:09 HPFed anacron[68662]: Normal exit (0 jobs run)
> Mar 13 01:19:45 HPFed rtkit-daemon[887]: The canary thread is apparently
> starving. Taking action.
> --
> Mar 15 02:01:02 HPFed run-parts[56951]: (/etc/cron.hourly) starting
> 0anacron
> Mar 15 02:01:03 HPFed anacron[56959]: Anacron started on 2023-03-15
> Mar 15 02:01:03 HPFed run-parts[56961]: (/etc/cron.hourly) finished
> 0anacron
> Mar 15 02:01:03 HPFed CROND[56947]: (root) CMDEND (run-parts
> /etc/cron.hourly)
> Mar 15 02:01:03 HPFed anacron[56959]: Normal exit (0 jobs run)
> Mar 15 02:09:32 HPFed kioslave5[57197]: kf.coreaddons: Expected a
> KPluginFactory, got a KIOPluginForMetaData
> Mar 15 02:18:06 HPFed rtkit-daemon[891]: The canary thread is apparently
> starving. Taking action.
> [john@HPFed ~]$
>
>
> }}}
>
1 week
System going unresponsive after this week's updates
by John Pilkington
I posted earlier about this, hoping that it had been solved. But it has
happened again. Keyboard unresponsive, and ssh. Disc access light on.
Here's some journalctl output covering the interval before the reboot
done at 10:05. The vga monitor and HDMI tv had been turned off earlier,
but were on-power at reboot.
John P
{{{
[john@HPFed ~]$ cd /var/RSG4
[john@HPFed RSG4]$ SYSTEMD_COLORS=false journalctl -S -14h | tee JCTL.txt
Hint: You are currently not seeing messages from other users and the system.
Users in groups 'adm', 'systemd-journal', 'wheel' can see all
messages.
Pass -q to turn off this notice.
Mar 03 22:24:26 HPFed plasmashell[1637]: org.kde.plasma.pulseaudio: No
object for name "alsa_output.pci-0000_01_00.1.hdmi-stereo"
Mar 03 22:24:30 HPFed kwin_x11[1622]: kwin_core: XCB error: 152
(BadDamage), sequence: 36375, resource id: 20998986, major code: 143
(DAMAGE), minor code: 3 (Subtract)
Mar 03 22:42:25 HPFed wireplumber[1868]: <WpNode:0x562e9d9e9b40>
ignoring set_param on already destroyed objects
Mar 03 22:42:59 HPFed kioslave5[20835]: kf.coreaddons: Expected a
KPluginFactory, got a KIOPluginForMetaData
Mar 03 22:43:42 HPFed plasmashell[17524]: [2023-03-03T22:43:42Z ERROR
viaduct::backend::ffi] Missing HTTP status
Mar 03 22:43:42 HPFed plasmashell[17524]: [2023-03-03T22:43:42Z ERROR
viaduct::backend::ffi] Missing HTTP status
Mar 03 22:43:42 HPFed plasmashell[17524]: [2023-03-03T22:43:42Z ERROR
viaduct::backend::ffi] Missing HTTP status
Mar 03 22:43:46 HPFed systemd[1496]:
app-firefox-fbfe013bdb56404c81208bb0ed223452.scope: Consumed 1min
37.193s CPU time.
Mar 03 22:43:59 HPFed systemd[1496]:
app-org.kde.okular-fd1a2e22a80b42df8f9697704917d3e9.scope: Consumed
23.530s CPU time.
Mar 03 22:54:16 HPFed kwin_x11[1622]: kwin_core: XCB error: 152
(BadDamage), sequence: 14691, resource id: 21002865, major code: 143
(DAMAGE), minor code: 3 (Subtract)
Mar 03 23:01:48 HPFed kioslave5[21728]: kf.coreaddons: Expected a
KPluginFactory, got a KIOPluginForMetaData
Mar 03 23:06:20 HPFed kwin_x11[1622]: kwin_core: XCB error: 152
(BadDamage), sequence: 33759, resource id: 21026563, major code: 143
(DAMAGE), minor code: 3 (Subtract)
Mar 03 23:16:34 HPFed kioslave5[22864]: kf.coreaddons: Expected a
KPluginFactory, got a KIOPluginForMetaData
Mar 03 23:21:53 HPFed kwin_x11[1622]: kwin_core: XCB error: 152
(BadDamage), sequence: 63090, resource id: 21058462, major code: 143
(DAMAGE), minor code: 3 (Subtract)
Mar 03 23:22:04 HPFed kwin_x11[1622]: kwin_core: XCB error: 152
(BadDamage), sequence: 67, resource id: 21058650, major code: 143
(DAMAGE), minor code: 3 (Subtract)
Mar 03 23:31:07 HPFed kioslave5[24268]: kf.coreaddons: Expected a
KPluginFactory, got a KIOPluginForMetaData
Mar 03 23:34:18 HPFed kwin_x11[1622]: kwin_core: XCB error: 152
(BadDamage), sequence: 25764, resource id: 21075409, major code: 143
(DAMAGE), minor code: 3 (Subtract)
Mar 03 23:34:28 HPFed kwin_x11[1622]: kwin_core: XCB error: 152
(BadDamage), sequence: 28192, resource id: 21075576, major code: 143
(DAMAGE), minor code: 3 (Subtract)
Mar 03 23:41:36 HPFed kwin_x11[1622]: kwin_core: Parse error in tiles
configuration for monitor "5b7a5ba4-43cc-5910-8e98-f358f9d54b43" :
"illegal value" Creating default setup
Mar 03 23:41:36 HPFed kded5[1621]: colord: Failed to register device:
"device id 'xrandr-Dell Inc.-DELL 2009W-G449H96P823L' already exists"
Mar 03 23:41:36 HPFed kded5[1621]: colord: EDID ICC Profile already
exists
"/home/john/.local/share/icc/edid-fdc2b57df97806a59aa00e978c8035f3.icc"
Mar 03 23:41:36 HPFed plasmashell[1637]:
file:///usr/share/plasma/wallpapers/org.kde.image/contents/ui/main.qml:20:
TypeError: Cannot read property 'pluginName' of null
Mar 03 23:41:36 HPFed plasmashell[1637]:
file:///usr/share/plasma/wallpapers/org.kde.image/contents/ui/main.qml:75:
TypeError: Cannot read property 'configuration' of null
Mar 03 23:41:36 HPFed plasmashell[1637]:
file:///usr/share/plasma/wallpapers/org.kde.image/contents/ui/main.qml:78:
TypeError: Cannot read property 'pluginName' of null
Mar 03 23:41:36 HPFed plasmashell[1637]:
file:///usr/share/plasma/wallpapers/org.kde.image/contents/ui/main.qml:80:
TypeError: Cannot read property 'configuration' of null
Mar 03 23:41:36 HPFed plasmashell[1637]:
file:///usr/share/plasma/wallpapers/org.kde.image/contents/ui/main.qml:81:
TypeError: Cannot read property 'configuration' of null
Mar 03 23:41:36 HPFed plasmashell[1637]:
file:///usr/share/plasma/wallpapers/org.kde.image/contents/ui/main.qml:82:
TypeError: Cannot read property 'configuration' of null
Mar 03 23:41:36 HPFed plasmashell[1637]:
file:///usr/share/plasma/wallpapers/org.kde.image/contents/ui/main.qml:83:
TypeError: Cannot read property 'configuration' of null
Mar 03 23:41:36 HPFed plasmashell[1637]:
file:///usr/share/plasma/wallpapers/org.kde.image/contents/ui/main.qml:84:
TypeError: Cannot read property 'configuration' of null
Mar 03 23:41:36 HPFed plasmashell[1637]:
file:///usr/share/plasma/wallpapers/org.kde.image/contents/ui/main.qml:16:
TypeError: Cannot read property 'configuration' of null
Mar 03 23:41:36 HPFed plasmashell[1637]:
file:///usr/share/plasma/wallpapers/org.kde.image/contents/ui/main.qml:17:
TypeError: Cannot read property 'configuration' of null
Mar 03 23:41:36 HPFed plasmashell[1637]:
file:///usr/share/plasma/wallpapers/org.kde.image/contents/ui/main.qml:18:
TypeError: Cannot read property 'configuration' of null
Mar 03 23:41:37 HPFed plasmashell[1637]: org.kde.plasma.pulseaudio: No
object for name "alsa_output.pci-0000_01_00.1.hdmi-stereo"
Mar 03 23:41:37 HPFed kded5[1621]: colord: Failed to register device:
"device id 'xrandr-Dell Inc.-DELL 2009W-G449H96P823L' already exists"
Mar 03 23:41:37 HPFed kded5[1621]: colord: Failed to register device:
"device id 'xrandr-Dell Inc.-DELL 2009W-G449H96P823L' already exists"
Mar 03 23:41:37 HPFed kded5[1621]: colord: EDID ICC Profile already
exists
"/home/john/.local/share/icc/edid-fdc2b57df97806a59aa00e978c8035f3.icc"
Mar 03 23:41:37 HPFed kded5[1621]: colord: EDID ICC Profile already
exists
"/home/john/.local/share/icc/edid-fdc2b57df97806a59aa00e978c8035f3.icc"
Mar 03 23:42:03 HPFed kded5[1621]: colord: Failed to register device:
"device id 'xrandr-Dell Inc.-DELL 2009W-G449H96P823L' already exists"
Mar 03 23:42:03 HPFed kded5[1621]: colord: EDID ICC Profile already
exists
"/home/john/.local/share/icc/edid-fdc2b57df97806a59aa00e978c8035f3.icc"
Mar 03 23:42:04 HPFed kded5[1621]: colord: Failed to register device:
"device id 'xrandr-Dell Inc.-DELL 2009W-G449H96P823L' already exists"
Mar 03 23:42:04 HPFed kded5[1621]: colord: EDID ICC Profile already
exists
"/home/john/.local/share/icc/edid-fdc2b57df97806a59aa00e978c8035f3.icc"
(gap inserted for clarity)
-- Boot f59d73dfe51d4dceaba4762fafcf4d94 --
Mar 04 10:05:58 HPFed systemd-xdg-autostart-generator[1516]:
/etc/xdg/autostart/org.kde.plasma-welcome.desktop:90: Unknown key name
'SingleMainWindow' in section 'Desktop Entry', ignoring.
Mar 04 10:05:58 HPFed systemd[1510]: Queued start job for default target
default.target.
Mar 04 10:05:58 HPFed systemd[1510]: Created slice app.slice - User
Application Slice.
Mar 04 10:05:58 HPFed systemd[1510]: Started grub-boot-success.timer -
Mark boot as successful after the user session has run 2 minutes.
Mar 04 10:05:59 HPFed sddm-helper[1520]: pam_kwallet5: final socket
path: /run/user/1000/kwallet5.socket
Mar 04 10:05:58 HPFed systemd[1510]: Reached target paths.target - Paths.
Mar 04 10:05:58 HPFed systemd[1510]: Reached target timers.target - Timers.
Mar 04 10:05:58 HPFed systemd[1510]: Starting dbus.socket - D-Bus User
Message Bus Socket...
Mar 04 10:05:58 HPFed systemd[1510]: Listening on pipewire-pulse.socket
- PipeWire PulseAudio.
Mar 04 10:05:58 HPFed systemd[1510]: Listening on pipewire.socket -
PipeWire Multimedia System Socket.
Mar 04 10:05:58 HPFed systemd[1510]: Listening on dbus.socket - D-Bus
User Message Bus Socket.
Mar 04 10:05:58 HPFed systemd[1510]: Reached target sockets.target -
Sockets.
Mar 04 10:05:58 HPFed systemd[1510]: Reached target basic.target - Basic
System.
Mar 04 10:05:58 HPFed systemd[1510]: Reached target default.target -
Main User Target.
Mar 04 10:05:58 HPFed systemd[1510]: Startup finished in 367ms.
}}}
1 week
How to See Google Contacts in Kmail
by Garry T. Williams
I see no way to retrieve Google contacts in Mail or Contacts in the
Kontact application.
In the Contact tab (Kontact application), I ask for a new address book
and get the choice of many services and local "books" including Google
Groupware, which is labeled "Access your Google Calendars, Contacts
and Tasks from KDE". If I choose that, after allowing all access
through a Web page, I get the choice of all the different Google
Calendars and Task list. But there is no choice enabling Google
Contacts. The dialog ends and there is no address book added to
Contact.
Anyone have any idea what I am doing wrong?
--
Garry T. Williams
1 week, 1 day
2023-03-13 @ **16:00** UTC - Fedora 38 Blocker Review Meeting
by Adam Williamson
# F37 Blocker Review meeting
# Date: 2023-03-13
# Time: **16:00** UTC
# Location: #fedora-blocker-review on irc.libera.chat
Hi folks! We have 11 proposed Final blockers to review, so let's have a
review meeting.
Note that clocks went forward in North America this weekend, so the
meeting time in UTC is an hour earlier than before. If you do not
observe daylight savings time, or your clocks did not yet go forward,
the meeting will be an hour earlier in your local time. Please double
check!
If you have time this weekend, you can take a look at the proposed or
accepted blockers before the meeting - the full lists can be found
here: https://qa.fedoraproject.org/blockerbugs/ .
Remember, you can also now vote on bugs outside of review meetings! If
you look at the bug list in the blockerbugs app, you'll see links
labeled "Vote!" next to all proposed blockers and freeze exceptions.
Those links take you to tickets where you can vote.
https://pagure.io/fedora-qa/blocker-review has instructions on how
exactly you do it. We usually go through the tickets shortly before the
meeting and apply any clear votes, so the meeting will just cover bugs
where there wasn't a clear outcome in the ticket voting yet. **THIS
MEANS IF YOU VOTE NOW, THE MEETING WILL BE SHORTER!**
We'll be evaluating these bugs to see if they violate any of the
Release Criteria and warrant the blocking of a release if they're not
fixed. Information on the release criteria for F38 can be found on the
wiki [0].
For more information about the Blocker and Freeze exception process,
check out these links:
- https://fedoraproject.org/wiki/QA:SOP_blocker_bug_process
- https://fedoraproject.org/wiki/QA:SOP_freeze_exception_bug_process
And for those of you who are curious how a Blocker Review Meeting
works - or how it's supposed to go and you want to run one - check out
the SOP on the wiki:
- https://fedoraproject.org/wiki/QA:SOP_Blocker_Bug_Meeting
Have a good day and see you tomorrow!
[0] https://fedoraproject.org/wiki/Fedora_Release_Criteria
--
Adam Williamson (he/him/his)
Fedora QA
Fedora Chat: @adamwill:fedora.im | Mastodon: @adamw(a)fosstodon.org
https://www.happyassassin.net
1 week, 3 days
2023-03-06 @ 17:00 UTC - Fedora 38 Blocker Review Meeting
by Adam Williamson
# F37 Blocker Review meeting
# Date: 2023-03-06
# Time: 17:00 UTC
# Location: #fedora-blocker-review on irc.libera.chat
Hi folks! We have 4 proposed Beta blockers, 10 proposed Beta freeze
exceptions and 7 proposed Final blockers to review, so let's have a
review meeting.
If you have time this weekend, you can take a look at the proposed or
accepted blockers before the meeting - the full lists can be found
here: https://qa.fedoraproject.org/blockerbugs/ .
Remember, you can also now vote on bugs outside of review meetings! If
you look at the bug list in the blockerbugs app, you'll see links
labeled "Vote!" next to all proposed blockers and freeze exceptions.
Those links take you to tickets where you can vote.
https://pagure.io/fedora-qa/blocker-review has instructions on how
exactly you do it. We usually go through the tickets shortly before the
meeting and apply any clear votes, so the meeting will just cover bugs
where there wasn't a clear outcome in the ticket voting yet. **THIS
MEANS IF YOU VOTE NOW, THE MEETING WILL BE SHORTER!**
We'll be evaluating these bugs to see if they violate any of the
Release Criteria and warrant the blocking of a release if they're not
fixed. Information on the release criteria for F38 can be found on the
wiki [0].
For more information about the Blocker and Freeze exception process,
check out these links:
- https://fedoraproject.org/wiki/QA:SOP_blocker_bug_process
- https://fedoraproject.org/wiki/QA:SOP_freeze_exception_bug_process
And for those of you who are curious how a Blocker Review Meeting
works - or how it's supposed to go and you want to run one - check out
the SOP on the wiki:
- https://fedoraproject.org/wiki/QA:SOP_Blocker_Bug_Meeting
Have a good day and see you tomorrow!
[0] https://fedoraproject.org/wiki/Fedora_Release_Criteria
--
Adam Williamson (he/him/his)
Fedora QA
Fedora Chat: @adamwill:fedora.im | Mastodon: @adamw(a)fosstodon.org
https://www.happyassassin.net
2 weeks, 3 days
