Bug 1529897

Summary: [abrt] mate-panel: g_type_check_instance_is_fundamentally_a(): clock-applet killed by SIGSEGV
Product: [Fedora] Fedora Reporter: strasharo2000
Component: mate-panelAssignee: Wolfgang Ulbrich <fedora>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 27CC: contact.sdey, fedora, robert.evans, stefano, vedran
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/037909608ffedf19c4426388aba891fe52673e0b
Whiteboard: abrt_hash:e434da972efa7b39de8b83bcd6f923b32027a59c;
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-01-23 21:46:28 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace
none
File: cgroup
none
File: core_backtrace
none
File: cpuinfo
none
File: dso_list
none
File: environ
none
File: exploitable
none
File: limits
none
File: maps
none
File: mountinfo
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages none

Description strasharo2000 2017-12-30 23:34:36 UTC
Description of problem:
tried to add a new location

Version-Release number of selected component:
mate-panel-1.19.3-2.fc27

Additional info:
reporter:       libreport-2.9.3
backtrace_rating: 4
cmdline:        /usr/libexec/mate-panel/clock-applet
crash_function: g_type_check_instance_is_fundamentally_a
executable:     /usr/libexec/mate-panel/clock-applet
journald_cursor: s=5f5d109bfdee4201b5a08c3ea6af7c90;i=3f4d;b=475a3406e36043e78af6d973b6d68007;m=1465c63ef;t=56197212c3083;x=26602fe58c638973
kernel:         4.14.8-300.fc27.x86_64
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (7 frames)
 #0 g_type_check_instance_is_fundamentally_a at gtype.c:4025
 #1 g_object_ref at gobject.c:3196
 #2 gtk_widget_on_frame_clock_update at gtkwidget.c:5219
 #7 _gdk_frame_clock_emit_update at gdkframeclock.c:628
 #8 gdk_frame_clock_paint_idle at gdkframeclockidle.c:380
 #15 gtk_main at gtkmain.c:1322
 #16 _mate_panel_applet_factory_main_internal at mate-panel-applet.c:2349

Comment 1 strasharo2000 2017-12-30 23:34:43 UTC
Created attachment 1374702 [details]
File: backtrace

Comment 2 strasharo2000 2017-12-30 23:34:45 UTC
Created attachment 1374703 [details]
File: cgroup

Comment 3 strasharo2000 2017-12-30 23:34:47 UTC
Created attachment 1374704 [details]
File: core_backtrace

Comment 4 strasharo2000 2017-12-30 23:34:49 UTC
Created attachment 1374705 [details]
File: cpuinfo

Comment 5 strasharo2000 2017-12-30 23:34:51 UTC
Created attachment 1374706 [details]
File: dso_list

Comment 6 strasharo2000 2017-12-30 23:34:54 UTC
Created attachment 1374707 [details]
File: environ

Comment 7 strasharo2000 2017-12-30 23:34:56 UTC
Created attachment 1374708 [details]
File: exploitable

Comment 8 strasharo2000 2017-12-30 23:34:58 UTC
Created attachment 1374709 [details]
File: limits

Comment 9 strasharo2000 2017-12-30 23:35:01 UTC
Created attachment 1374710 [details]
File: maps

Comment 10 strasharo2000 2017-12-30 23:35:04 UTC
Created attachment 1374711 [details]
File: mountinfo

Comment 11 strasharo2000 2017-12-30 23:35:06 UTC
Created attachment 1374712 [details]
File: open_fds

Comment 12 strasharo2000 2017-12-30 23:35:07 UTC
Created attachment 1374713 [details]
File: proc_pid_status

Comment 13 strasharo2000 2017-12-30 23:35:09 UTC
Created attachment 1374714 [details]
File: var_log_messages

Comment 14 Vedran Miletić 2017-12-31 14:30:14 UTC
Similar problem has been detected:

I added the location "Rijeka, Hrvatska" to the list of Locations

reporter:       libreport-2.9.3
backtrace_rating: 4
cmdline:        /usr/libexec/mate-panel/clock-applet
crash_function: g_type_check_instance_is_fundamentally_a
executable:     /usr/libexec/mate-panel/clock-applet
journald_cursor: s=f51e63983cf64057a9b4387d5b8a470d;i=1c4e;b=27143ad4d9f84fbdbb62c404fd0f4bc3;m=13127b01f;t=561a39e1581b2;x=fd13c9b20bffe2ea
kernel:         4.14.8-300.fc27.x86_64
package:        mate-panel-1.19.3-2.fc27
reason:         clock-applet killed by SIGSEGV
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1000

Comment 15 Subhadeep Dey 2018-01-10 10:38:50 UTC
Similar problem has been detected:

It happened while I was setting the location to show weather in top-right panel.

reporter:       libreport-2.9.3
backtrace_rating: 4
cmdline:        /usr/libexec/mate-panel/clock-applet
crash_function: g_type_check_instance_is_fundamentally_a
executable:     /usr/libexec/mate-panel/clock-applet
journald_cursor: s=adfab55095a74de39185d1e666e38636;i=df7e;b=37652d91198b4476979a9f04d94ef936;m=31f2728c;t=5626992034625;x=7c95fa27544ce7bc
kernel:         4.14.11-300.fc27.x86_64
package:        mate-panel-1.19.4-1.fc27
reason:         clock-applet killed by SIGSEGV
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1000

Comment 16 Fedora Update System 2018-01-16 19:04:05 UTC
mate-applets-1.19.4-1.fc27 libmateweather-1.19.1-4.fc27 has been submitted as an update to Fedora 27. https://bodhi.fedoraproject.org/updates/FEDORA-2018-f143a850ec

Comment 17 Fedora Update System 2018-01-21 10:39:22 UTC
libmateweather-1.19.1-4.fc27, mate-applets-1.19.4-1.fc27 has been pushed to the Fedora 27 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2018-f143a850ec

Comment 18 Fedora Update System 2018-01-23 21:46:28 UTC
libmateweather-1.19.1-4.fc27, mate-applets-1.19.4-1.fc27 has been pushed to the Fedora 27 stable repository. If problems still persist, please make note of it in this bug report.

Comment 19 Wolfgang Ulbrich 2018-01-30 16:50:23 UTC
*** Bug 1540238 has been marked as a duplicate of this bug. ***

Comment 20 Wolfgang Ulbrich 2018-01-30 16:50:55 UTC
*** Bug 1540241 has been marked as a duplicate of this bug. ***