Bug 2241741 - org.gnome.SettingsDaemon.PrintNotifications times out, probably delaying livecd welcome dialog
Summary: org.gnome.SettingsDaemon.PrintNotifications times out, probably delaying live...
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: cups
Version: 39
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Zdenek Dohnal
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-10-02 13:45 UTC by Kamil Páral
Modified: 2023-10-12 10:48 UTC (History)
14 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-10-12 10:48:48 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
journal (190.32 KB, text/plain)
2023-10-02 13:45 UTC, Kamil Páral
no flags Details
rpm -qa (66.05 KB, text/plain)
2023-10-02 13:46 UTC, Kamil Páral
no flags Details

Description Kamil Páral 2023-10-02 13:45:35 UTC
Description of problem:
In Fedora-Workstation-Live-x86_64-39_Beta-1.1.iso , the livecd welcome dialog appears in ~3 seconds after seeing the desktop. In Fedora-Workstation-Live-x86_64-39-20231002.n.0.iso this takes ~27 seconds. Looking at the journal, a likely cause seems to be a timeout in org.gnome.SettingsDaemon.PrintNotifications and xdg-desktop-portal.

From journal:

Oct 02 09:19:54 localhost-live systemd[1426]: org.gnome.SettingsDaemon.PrintNotifications.service: start operation timed out. Terminating.
Oct 02 09:19:58 localhost-live systemd[1426]: xdg-desktop-portal.service: start operation timed out. Terminating.
Oct 02 09:19:58 localhost-live systemd[1426]: xdg-desktop-portal.service: Failed with result 'timeout'.
Oct 02 09:19:58 localhost-live systemd[1426]: Failed to start xdg-desktop-portal.service - Portal service.
Oct 02 09:19:58 localhost-live systemd[1426]: Starting xdg-desktop-portal.service - Portal service...
Oct 02 09:19:59 localhost-live systemd[1426]: org.gnome.SettingsDaemon.PrintNotifications.service: State 'stop-sigterm' timed out. Aborting.
Oct 02 09:19:59 localhost-live systemd[1426]: org.gnome.SettingsDaemon.PrintNotifications.service: Killing process 1750 (gsd-print-notif) with signal SIGABRT.
...
Oct 02 09:19:59 localhost-live systemd-coredump[2605]: [🡕] Process 1750 (gsd-print-notif) of user 1000 dumped core.
...
Oct 02 09:19:59 localhost-live systemd[1426]: org.gnome.SettingsDaemon.PrintNotifications.service: Main process exited, code=dumped, status=6/ABRT
Oct 02 09:19:59 localhost-live systemd[1426]: org.gnome.SettingsDaemon.PrintNotifications.service: Failed with result 'timeout'.
Oct 02 09:19:59 localhost-live systemd[1426]: Failed to start org.gnome.SettingsDaemon.PrintNotifications.service - GNOME printer notifications service.
...
Oct 02 09:19:59 localhost-live systemd[1426]: org.gnome.SettingsDaemon.PrintNotifications.service: Scheduled restart job, restart counter is at 1.
Oct 02 09:19:59 localhost-live systemd[1426]: Starting org.gnome.SettingsDaemon.PrintNotifications.service - GNOME printer notifications service...
Oct 02 09:19:59 localhost-live systemd[1426]: Starting xdg-desktop-portal-gtk.service - Portal service (GTK/GNOME implementation)...
Oct 02 09:19:59 localhost-live systemd[1426]: Started xdg-desktop-portal-gtk.service - Portal service (GTK/GNOME implementation).
Oct 02 09:19:59 localhost-live systemd[1426]: Started xdg-desktop-portal.service - Portal service.


As you can see, the service start up successfully on a second attempt. But I believe the first crash causes a delay in the livecd welcome dialog, which is very inconvenient for the user.


Version-Release number of selected component (if applicable):
gnome-settings-daemon-45.0-1.fc39.x86_64
xdg-desktop-portal-1.18.0-2.fc39.x86_64
xdg-desktop-portal-gnome-45.0-1.fc39.x86_64
xdg-desktop-portal-gtk-1.14.1-3.fc39.x86_64


How reproducible:
always

Steps to Reproduce:
1. boot Fedora-Workstation-Live-x86_64-39-20231002.n.0.iso
2. the welcome dialog should appear in a few seconds, appears in half a minute

Comment 1 Kamil Páral 2023-10-02 13:45:56 UTC
Created attachment 1991618 [details]
journal

Comment 2 Kamil Páral 2023-10-02 13:46:05 UTC
Created attachment 1991619 [details]
rpm -qa

Comment 3 Kamil Páral 2023-10-02 13:48:38 UTC
The F39 Final freeze starts tomorrow, and I believe we definitely would like to see this fixed. Proposing for a freeze exception.

Comment 4 Kamil Páral 2023-10-02 14:35:59 UTC
Sigh. This seems to be a race condition. Originally I booted my VM several times and it happened every time, but when I tried it an hour later, the same ISO in the same VM booted just fine, no welcome dialog delay, no gsd/xdg-desktop-portal timeout. So this is going to be much harder to debug :-(

Comment 5 Marek Kašík 2023-10-03 09:27:51 UTC
I'll try to reproduce this today.

Comment 6 Marek Kašík 2023-10-03 16:50:51 UTC
I can not reproduce the issue on laptop, desktop or VM even with multiple attempts.

Comment 7 Marek Kašík 2023-10-04 10:19:32 UTC
I'm reassigning this to cups for consideration since the crash happens close to cups_dnssd_poll_cb() (see the journal, I still can not reproduce this).

Comment 8 Kamil Páral 2023-10-04 12:34:54 UTC
I've done ~20 reboots today, and the problem hasn't manifested a single time. So I can't even provide proper traceback/coredump, sorry :-/ Originally it seemed like a fully reproducible problem...

I withdraw the freeze exception proposal for the moment, because the impact seems much lower than initially.

Comment 9 Zdenek Dohnal 2023-10-12 10:48:48 UTC
Hi,

I've tried to reproduce the issue with image Fedora-Workstation-Live-x86_64-39-20231010.n.0.iso via VM - got the welcome dialog in approx 3s, and I don't see the crash in the journal.

The function which is reported to crash is callback for Avahi daemon which is used during polling for data from available services, but I'm not able to investigate more without reliable reproducer and full backtrace.


I'll close the issue for now, feel free to reopen if you are able to reproduce again.

Thank you!


Note You need to log in before you can comment on or make changes to this bug.