[Bug 1217629] New: [abrt] gpick: g_malloc(): gpick killed by SIGABRT

[Red Hat Bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=1217629

Bug ID: 1217629
           Summary: [abrt] gpick: g_malloc(): gpick killed by SIGABRT
           Product: Fedora
           Version: 21
         Component: gpick
          Assignee: [e-mail]
          Reporter: [e-mail]
        QA Contact: [e-mail]
                CC: [e-mail],
                    [e-mail]

Version-Release number of selected component:
gpick-0.2.5-6.fc21

Additional info:
reporter:       libreport-2.3.0
backtrace_rating: 4
cmdline:        gpick
crash_function: g_malloc
executable:     /usr/bin/gpick
kernel:         3.18.7-200.fc21.x86_64
runlevel:       N 5
type:           CCpp
uid:            1000
var_log_messages: [System Logs]:\n-- Logs begin at Пт 2015-02-20 20:22:11 MSK,
end at Пт 2015-05-01 00:22:42 MSK. --

Truncated backtrace:
Thread no. 1 (10 frames)
 #6 g_malloc at gmem.c:97
 #7 g_strdup at gstrfuncs.c:356
 #8 g_signal_newv at gsignal.c:1600
 #9 g_signal_new_valist at gsignal.c:1840
 #10 g_signal_new at gsignal.c:1395
 #11 g_file_monitor_class_init at gfilemonitor.c:241
 #12 g_file_monitor_class_intern_init at gfilemonitor.c:97
 #13 type_class_init_Wm at gtype.c:2217
 #14 g_type_class_ref at gtype.c:2932
 #17 try_class at giomodule.c:638

[Bug 1217629] [abrt] gpick: g_malloc(): gpick killed by SIGABRT

[Red Hat Bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=1217629

--- Comment #10 from Fedora End Of Life  ---
This message is a reminder that Fedora 21 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 21. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '21'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 21 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

[Bug 1217629] [abrt] gpick: g_malloc(): gpick killed by SIGABRT

[Red Hat Bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=1217629

Luya Tshimbalanga  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]

--- Comment #11 from Luya Tshimbalanga  ---
Does the bug happen when running on Gnome session rather than Wayland?

[Bug 1217629] [abrt] gpick: g_malloc(): gpick killed by SIGABRT

[Red Hat Bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=1217629

Jan Kurik  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |CLOSED
         Resolution|---                         |EOL
        Last Closed|                            |2015-12-02 14:48:40

[Bug 1217629] [abrt] gpick: g_malloc(): gpick killed by SIGABRT

[Red Hat Bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=1217629

--- Comment #12 from Jan Kurik  ---
Fedora 21 changed to end-of-life (EOL) status on 2015-12-01. Fedora 21 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.