Bug 275703 - sysutils/mate-settings-daemon crashed
Summary: sysutils/mate-settings-daemon crashed
Status: New
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: --- Affects Many People
Assignee: freebsd-gnome (Nobody)
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-12-11 18:57 UTC by Aminavy
Modified: 2024-01-02 19:02 UTC (History)
2 users (show)

See Also:
linimon: maintainer-feedback? (gnome)

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Aminavy 2023-12-11 18:57:30 UTC 
When I logout from session or reboot "mate-settings-daemo.core" appeared in my home directory.

% lldb --core mate-settings-daemo.core
(lldb) target create --core "mate-settings-daemo.core"
Core file '/home/aminavy/mate-settings-daemo.core' (x86_64) was loaded.
(lldb) thread backtrace all
* thread #1, name = 'mate-settings-daemo', stop reason = signal SIGBUS
  * frame #0: 0x000000082be7e023
    frame #1: 0x0000000820a93b70
  thread #2, name = 'pool-spawner', stop reason = signal SIGBUS
    frame #0: 0x000000082e206d2c
    frame #1: 0x000000082e216d72
  thread #3, name = 'gmain', stop reason = signal SIGBUS
    frame #0: 0x000000082f056c2a
    frame #1: 0x000000082e215691
  thread #4, name = 'dconf worker', stop reason = signal SIGBUS
    frame #0: 0x000000082f056c2a
    frame #1: 0x000000082e215691
  thread #5, name = 'gdbus', stop reason = signal SIGBUS
    frame #0: 0x000000082d6ef440
    frame #1: 0x000011c5ba6331d0
  thread #6, name = 'dconf worker', stop reason = signal SIGBUS
    frame #0: 0x000000082f056c2a
    frame #1: 0x000000082e215691
  thread #7, name = 'pool-mate-setti', stop reason = signal SIGBUS
    frame #0: 0x000000082e206d2c
    frame #1: 0x000000082e216d72
(lldb)
Comment 1 Taka 2023-12-29 08:41:45 UTC 
I have the same issue.
Now, I use mate-1.26.0_2 on 14R.
I think, I have been having this problem since the 13R days.
At every login I erase it by a command added in startup.
Comment 2 Aminavy 2023-12-31 16:37:31 UTC 
removing the core file after login doesn't prevent from writing to storage. because core created after logout.
Comment 3 Taka 2024-01-02 19:02:19 UTC 
Of course. I know.
That is just I don't want to delete the core file manually every time I login.