Bug 2185438 - [abrt] setroubleshoot: _close_notifications(): seapplet:110:_close_notifications:gi.repository.GLib.GError: g-io-error-quark: Timeout was reached (24)
Summary: [abrt] setroubleshoot: _close_notifications(): seapplet:110:_close_notificati...
Keywords:
Status: NEW
Alias: None
Product: Fedora
Classification: Fedora
Component: setroubleshoot
Version: 39
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Petr Lautrbach
QA Contact: Fedora Extras Quality Assurance
URL: https://retrace.fedoraproject.org/faf...
Whiteboard: abrt_hash:9e42cd6827bfe356a95bd87ed0d...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-04-09 11:13 UTC by Mikhail
Modified: 2023-08-16 07:13 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: ---
Doc Text:
Clone Of:
Environment:
Last Closed:
Type: ---
Embargoed:


Attachments (Terms of Use)
File: os_info (770 bytes, text/plain)
2023-04-09 11:13 UTC, Mikhail
no flags Details
File: environ (1.31 KB, text/plain)
2023-04-09 11:14 UTC, Mikhail
no flags Details
File: mountinfo (3.68 KB, text/plain)
2023-04-09 11:14 UTC, Mikhail
no flags Details
File: open_fds (2.65 KB, text/plain)
2023-04-09 11:14 UTC, Mikhail
no flags Details
File: namespaces (171 bytes, text/plain)
2023-04-09 11:14 UTC, Mikhail
no flags Details
File: backtrace (980 bytes, text/plain)
2023-04-09 11:14 UTC, Mikhail
no flags Details
File: cpuinfo (2.96 KB, text/plain)
2023-04-09 11:14 UTC, Mikhail
no flags Details

Description Mikhail 2023-04-09 11:13:55 UTC
Version-Release number of selected component:
setroubleshoot-3.3.32-1.fc39

Additional info:
reporter:       libreport-2.17.9
kernel:         6.3.0-0.rc5.20230407gitf2afccfefe7b.46.fc39.x86_64+debug
cmdline:        /usr/bin/python3 -Es /usr/bin/seapplet
cgroup:         0::/user.slice/user-1000.slice/session-8.scope
uid:            1000
reason:         seapplet:110:_close_notifications:gi.repository.GLib.GError: g-io-error-quark: Timeout was reached (24)
executable:     /usr/bin/seapplet
type:           Python3
package:        setroubleshoot-3.3.32-1.fc39
runlevel:       N 5
exception_type: gi.repository.GLib.GError
crash_function: _close_notifications
interpreter:    python3-3.11.3-1.fc39.x86_64

Truncated backtrace:
seapplet:110:_close_notifications:gi.repository.GLib.GError: g-io-error-quark: Timeout was reached (24)

Traceback (most recent call last):
  File "/usr/lib/python3.11/site-packages/dasbus/client/handler.py", line 133, in _signal_callback
    callback(parameters, *callback_args)
  File "/usr/lib/python3.11/site-packages/dasbus/client/handler.py", line 365, in _signal_callback
    callback(*unwrap_variant(parameters))
  File "/usr/lib/python3.11/site-packages/dasbus/signal.py", line 53, in emit
    callback(*args, **kwargs)
  File "/usr/bin/seapplet", line 138, in send_notification
    self._close_notifications()
  File "/usr/bin/seapplet", line 110, in _close_notifications
    n.close()
gi.repository.GLib.GError: g-io-error-quark: Timeout was reached (24)

Local variables in innermost frame:
self: <__main__.SEApplet object at 0x7fb977b29b40 (__main__+SEApplet at 0x55ae68fe91d0)>
n: <Notify.Notification object at 0x7fb977b603c0 (NotifyNotification at 0x55ae692737c0)>

Comment 1 Mikhail 2023-04-09 11:13:58 UTC
Created attachment 1956431 [details]
File: os_info

Comment 2 Mikhail 2023-04-09 11:14:00 UTC
Created attachment 1956432 [details]
File: environ

Comment 3 Mikhail 2023-04-09 11:14:01 UTC
Created attachment 1956433 [details]
File: mountinfo

Comment 4 Mikhail 2023-04-09 11:14:03 UTC
Created attachment 1956434 [details]
File: open_fds

Comment 5 Mikhail 2023-04-09 11:14:05 UTC
Created attachment 1956435 [details]
File: namespaces

Comment 6 Mikhail 2023-04-09 11:14:06 UTC
Created attachment 1956436 [details]
File: backtrace

Comment 7 Mikhail 2023-04-09 11:14:08 UTC
Created attachment 1956437 [details]
File: cpuinfo

Comment 8 Fedora Release Engineering 2023-08-16 07:13:16 UTC
This bug appears to have been reported against 'rawhide' during the Fedora Linux 39 development cycle.
Changing version to 39.


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