Skip to content

[Cherry 5.0.x]: fix: Prevent segfault by correctly handling dbus restarts in mender-update and mender-auth#1889

Open
mender-test-bot wants to merge 2 commits into
5.0.xfrom
cherry-5.0.x-MEN-9144-mender-client-segfaults-upon-dbus-shutdown
Open

[Cherry 5.0.x]: fix: Prevent segfault by correctly handling dbus restarts in mender-update and mender-auth#1889
mender-test-bot wants to merge 2 commits into
5.0.xfrom
cherry-5.0.x-MEN-9144-mender-client-segfaults-upon-dbus-shutdown

Conversation

@mender-test-bot

Copy link
Copy Markdown

Cherry pick of PR: #1880
For you :)

…pdate and mender-auth

Ticket: MEN-9144
Changelog: Prevent segfault by correctly handling dbus restarts in mender-update and mender-auth.
Previously when systemctl stop dbus.socket or systemctl stop dbus was called, it resulted in mender-update segfault.

Signed-off-by: Michal Kopczan <michal.kopczan@northern.tech>
(cherry picked from commit 43dd888)
…g no handler to be called

Ticket: MEN-9144
Changelog: Fix a hang when polling for deployment failed early causing no handler of API response
to be called. Added handler call for this case, causing the deployment polling
to continue.

Signed-off-by: Michal Kopczan <michal.kopczan@northern.tech>
(cherry picked from commit 6aa4c77)
@mender-test-bot

mender-test-bot commented Jan 26, 2026

Copy link
Copy Markdown
Author

Merging these commits will result in the following changelog entries:

Changelogs

mender (cherry-5.0.x-MEN-9144-mender-client-segfaults-upon-dbus-shutdown)

New changes in mender since 5.0.x:

Bug Fixes
  • Fix a hang when polling for deployment failed early causing no handler of API response
    to be called. Added handler call for this case, causing the deployment polling
    to continue.
    (MEN-9144)
  • Prevent segfault by correctly handling dbus restarts in mender-update and mender-auth.
    Previously when systemctl stop dbus.socket or systemctl stop dbus was called, it resulted in mender-update segfault.
    (MEN-9144)

@mender-test-bot

Copy link
Copy Markdown
Author

@mender-test-bot, start a full client pipeline with:

  • mentioning me and start client pipeline

my commands and options

You can prevent me from automatically starting CI pipelines:

  • if your pull request title starts with "[NoCI] ..."

You can trigger a client pipeline on multiple prs with:

  • mentioning me and start client pipeline --pr mender/127 --pr mender-connect/255

You can trigger GitHub->GitLab branch sync with:

  • mentioning me and sync

You can cherry pick to a given branch or branches with:

  • mentioning me and:
 cherry-pick to:
 * 1.0.x
 * 2.0.x

@pasinskim

Copy link
Copy Markdown
Member

@mender-test-bot print fast pr stats

@mender-test-bot

Copy link
Copy Markdown
Author

PR Metrics for Client Team (Fast Mode) (Last 30 Days)

Team Activity

User Opened (30d) Closed (30d) Median TTC Open Now Assigned/Reviewing
danielskinstad 11 11 20h 48m 1 1
vpodzime 10 9 2h 45m 1 0
lluiscampos 6 5 2h 6m 1 2
oldgiova 7 7 15h 44m 0 0
elkoniu 4 3 4d 23h 38m 2 0
michalkopczan 3 3 1d 21h 18m 0 0
nt-alan 0 0 None 0 1
TheYoctoJester 0 0 None 2 0
mzedel 0 0 None 1 0

Report generated on 2026-03-11 17:34:49 UTC

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants