Description of problem: I was adding fonts to local .fonts folder Version-Release number of selected component: mate-window-manager-1.6.2-6.fc20 Additional info: reporter: libreport-2.2.2 backtrace_rating: 4 cmdline: marco crash_function: __gconv_open executable: /usr/bin/marco kernel: 3.14.5-200.fc20.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #3 __gconv_open at gconv_open.c:282 #4 iconv_open at iconv_open.c:71 #5 try_conversion at gconvert.c:199 #6 g_iconv_open at gconvert.c:251 #7 open_converter at gconvert.c:338 #8 g_convert at gconvert.c:575 #9 make_list at gdkselection-x11.c:537 #10 gdk_text_property_to_utf8_list_for_display at gdkselection-x11.c:623 #11 gdk_text_property_to_utf8_list at gdkselection.c:96 #12 meta_text_property_to_utf8 at ui/ui.c:813
Created attachment 902974 [details] File: backtrace
Created attachment 902975 [details] File: cgroup
Created attachment 902976 [details] File: core_backtrace
Created attachment 902977 [details] File: dso_list
Created attachment 902978 [details] File: environ
Created attachment 902979 [details] File: exploitable
Created attachment 902980 [details] File: limits
Created attachment 902981 [details] File: maps
Created attachment 902982 [details] File: open_fds
Created attachment 902983 [details] File: proc_pid_status
Created attachment 902984 [details] File: var_log_messages
Does it happend everytime and marco is unusable now or was it only a one shot abrt alarm? Did marco crashed or was it only a abrt alarm?
It happened on more than one occasion for sure. I was updating fonts with rsync on a number of workstations and while all of the first hundred or so experienced weird and long -but temporary- lockups of the display (I suppose it was marco "hanging" while waiting for the fonts subsystem), a few had this marco crash. Since I had not planned any downtime and to avoid further problems, I opted to proceed upgrading fonts in a separate folder that would later be moved in place, once the sync was fully done. This way the remaining 600-something upgrades went smoothly. We're talking about the refresh of few hundred megs of already-existing fonts. The equivalent of the fonts normally shipped in windows7 or in office 2013 for the mac. Which where copied over older versions of themselves. Marco was still usable after any of those issues. Even when it outright crashed. In fact I believe the crash itself was due to the continuous "reloading or re-caching" of the fonts that happened every time a single font-file was touched by rsync during the "hot update" of the fonts.
forward to upstream https://github.com/mate-desktop/marco/issues/111 Pls answer there if upstream have a question.
will do. :)
closed, package are renamed to marco