Bug 278677 - x11/mate-desktop: fail on start
Summary: x11/mate-desktop: fail on start
Status: Closed FIXED
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: arm64 Any
: --- Affects Only Me
Assignee: freebsd-gnome (Nobody)
URL:
Keywords:
: 278933 (view as bug list)
Depends on:
Blocks:
 
Reported: 2024-05-01 08:27 UTC by Martin Filla
Modified: 2024-05-12 16:07 UTC (History)
5 users (show)

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


Attachments
PATCH for mate-panel (842 bytes, patch)
2024-05-07 01:30 UTC, eusteuc
no flags Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Martin Filla 2024-05-01 08:27:46 UTC
Hello,
i have problem with mate-desktop and applications from mate.
For example mate-clock.
i have FreeBSD 13.3 and mate-desktop is from pkg

pid 1793 (mate-volume-control), jid 0, uid 1001: exited on signal 5 (core dumped)
pid 2101 (clock-applet), jid 0, uid 1001: exited on signal 5
pid 2103 (clock-applet), jid 0, uid 1001: exited on signal 5
pid 2105 (clock-applet), jid 0, uid 1001: exited on signal 5
pid 2107 (clock-applet), jid 0, uid 1001: exited on signal 5
pid 2109 (clock-applet), jid 0, uid 1001: exited on signal 5
pid 2111 (clock-applet), jid 0, uid 1001: exited on signal 5
pid 2113 (clock-applet), jid 0, uid 1001: exited on signal 5
pid 2115 (clock-applet), jid 0, uid 1001: exited on signal 5
pid 2117 (clock-applet), jid 0, uid 1001: exited on signal 5
pid 2119 (clock-applet), jid 0, uid 1001: exited on signal 5
pid 2121 (clock-applet), jid 0, uid 1001: exited on signal 5
pid 2096 (mate-panel), jid 0, uid 1001: exited on signal 5 (core dumped)
pid 2124 (clock-applet), jid 0, uid 1001: exited on signal 5
pid 2122 (mate-panel), jid 0, uid 1001: exited on signal 5 (core dumped)
..
Comment 1 Martin Filla 2024-05-01 08:55:46 UTC
I dont see more 

maxfx@hades ~> gdb /usr/local/bin/mate-panel ./mate-panel.core
GNU gdb (GDB) 14.1 [GDB v14.1 for FreeBSD]
Copyright (C) 2023 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "x86_64-portbld-freebsd13.2".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<https://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
    <http://www.gnu.org/software/gdb/documentation/>.

For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from /usr/local/bin/mate-panel...
[New LWP 107023]
[New LWP 107117]
[New LWP 107118]
[New LWP 107119]
[New LWP 107120]
[New LWP 107604]
[New LWP 107631]
Core was generated by `mate-panel --sm-client-id 10a1bc1c764532780163657014571136500000042360011'.
Program terminated with signal SIGTRAP, Trace/breakpoint trap.
Breakpoint.
#0  0x000000082dedbc8b in ?? ()
[Current thread is 1 (LWP 107023)]
(gdb) bt
#0  0x000000082dedbc8b in ?? ()
#1  0x0000000820dcab00 in ?? ()
#2  0x0000000000291cc0 in panel_frame_size_allocate (widget=0x82dedbc80, allocation=0x820dcaaf0) at panel-frame.c:152
#3  0x000000082dedb5b6 in ?? ()
#4  0x000000082de1fc5d in ?? ()
Comment 2 Martin Filla 2024-05-06 05:03:22 UTC
the same problem on 14.0-RELEASE
pid 1893 (wnck-applet), jid 0, uid 1001: exited on signal 5 (no core dump - other error)
pid 1902 (notification-area-a), jid 0, uid 1001: exited on signal 5 (no core dump - other error)
pid 1903 (clock-applet), jid 0, uid 1001: exited on signal 5 (no core dump - other error)
pid 1909 (clock-applet), jid 0, uid 1001: exited on signal 5 (no core dump - other error)
pid 1911 (clock-applet), jid 0, uid 1001: exited on signal 5 (no core dump - other error)
pid 1913 (clock-applet), jid 0, uid 1001: exited on signal 5 (no core dump - other error)
pid 1915 (clock-applet), jid 0, uid 1001: exited on signal 5 (no core dump - other error)
pid 1917 (clock-applet), jid 0, uid 1001: exited on signal 5 (no core dump - other error)
pid 1919 (clock-applet), jid 0, uid 1001: exited on signal 5 (no core dump - other error)
pid 64659 (conftest), jid 0, uid 0: exited on signal 11 (no core dump - too large)
Comment 3 Dag-Erling Smørgrav freebsd_committer freebsd_triage 2024-05-06 15:24:13 UTC
Can you please try installing devel/dconf-editor and let us know if it fixes your problem?
Comment 4 Martin Filla 2024-05-06 18:59:12 UTC
(In reply to Dag-Erling Smørgrav from comment #3)
thank you, it works. can be close this bug.
Comment 5 Martin Filla 2024-05-06 18:59:49 UTC
(In reply to Dag-Erling Smørgrav from comment #3)
you should add this program to mate-desktop as dependece
Comment 6 commit-hook freebsd_committer freebsd_triage 2024-05-07 01:03:09 UTC
A commit in branch main references this bug:

URL: https://cgit.FreeBSD.org/ports/commit/?id=d46112208bda3d4e3aba8303b3259c5cff5ee75e

commit d46112208bda3d4e3aba8303b3259c5cff5ee75e
Author:     Dag-Erling Smørgrav <des@FreeBSD.org>
AuthorDate: 2024-05-06 15:26:54 +0000
Commit:     Dag-Erling Smørgrav <des@FreeBSD.org>
CommitDate: 2024-05-07 01:02:43 +0000

    x11/mate-desktop: Add run-dep on devel/dconf-editor.

    PR:             278677

 x11/mate-desktop/Makefile | 2 ++
 1 file changed, 2 insertions(+)
Comment 7 eusteuc 2024-05-07 01:30:32 UTC
Created attachment 250497 [details]
PATCH for mate-panel

Hi, I fount it's actually a problem from mate-panel.
Comment 8 Dag-Erling Smørgrav freebsd_committer freebsd_triage 2024-05-07 11:49:44 UTC
It doesn't make much difference since nobody is going to use one without the other.  Eric can move it when he next updates both ports.
Comment 9 Eric Turgeon freebsd_committer freebsd_triage 2024-05-07 15:12:10 UTC
There is a new version of mate-desktop and mate-panel that might fix this issue. But having dconf editor install in the with mate-deskop is a great.
Comment 10 Dag-Erling Smørgrav freebsd_committer freebsd_triage 2024-05-12 16:07:15 UTC
*** Bug 278933 has been marked as a duplicate of this bug. ***