Bug 287361 - devel/dbus After 6024c2a1b1f592e interactions with mate-session triggers poll loop
Summary: devel/dbus After 6024c2a1b1f592e interactions with mate-session triggers poll...
Status: Closed Overcome By Events
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: --- Affects Only Me
Assignee: freebsd-desktop (Team)
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2025-06-07 16:14 UTC by rkoberman
Modified: 2025-06-16 23:05 UTC (History)
1 user (show)

See Also:
arrowd: maintainer-feedback+


Attachments
kdump (default options plus time stamps) of the start of the problem (12.40 KB, text/plain)
2025-06-07 16:14 UTC, rkoberman
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description rkoberman 2025-06-07 16:14:07 UTC
Created attachment 261067 [details]
kdump (default options plus time stamps) of the start of the problem

After the May 16 commit, mate-session goes into a tight cycle of polls that consume one thread and leaves mate-session non-functional. This started after 6024c2a1b1f592e with no changes to mate-session-manager. Rebuild of mate-session-manager did not affect the problem. 

While many operations that involved the creation of a new gnome-based window seemed to trigger the problem, it is reliably triggered by running this command:
mate-terminal --geometry 80x30 --profile=Default -t server -x ssh -l USER SYSTEM
always triggered the problem. Use of ktrace to monitor mate-session process showed a failure in communication between mate-session and dbus. After the failure, mate-session attempts to open a new connection to dbus which results in continual attempts to poll dbus.

While this may involve a problem with mate-session, the issue only occurs after the update to dbus on May 16.

System notes: Alder Lake 12 thread CPU running 15-current most recently running ain-n277560-99976934274d
Comment 1 Gleb Popov freebsd_committer freebsd_triage 2025-06-07 18:11:00 UTC
Can you please check if the following patch fixes the problem for you?

https://github.com/arrowd/freebsd-ports/commit/76c1cb097d98d354fe4e0671e2c273458cacebe7
Comment 2 rkoberman 2025-06-16 23:05:07 UTC
The issue vanished after updating to 1500046.