Bug 14870 - Gnome-Shell terminates with SIGABORT on Exposé
Summary: Gnome-Shell terminates with SIGABORT on Exposé
Status: RESOLVED OLD
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 4
Hardware: x86_64 Linux
Priority: Normal major
Target Milestone: ---
Assignee: Olav Vitters
QA Contact:
URL:
Whiteboard:
Keywords: NEEDINFO
Depends on:
Blocks:
 
Reported: 2014-12-22 15:08 CET by Herbert Poetzl
Modified: 2015-10-27 06:56 CET (History)
1 user (show)

See Also:
Source RPM:
CVE:
Status comment:


Attachments

Description Herbert Poetzl 2014-12-22 15:08:58 CET
Description of problem:
Gnome-Shell terminates with SIGABORT when entering Expose (or selecting Activities) after upgrade from Mageia 3 to Mageia 4

Version-Release number of selected component (if applicable):
gnome-shell-3.10.2.1-7.1.mga4.x86_64


How reproducible:


Steps to Reproduce:
1. login as user or guest
2. enter Exposé mode
3.


    Program received signal SIGABRT, Aborted.
    0x00007f272af61969 in raise () from /lib64/libc.so.6
    (gdb) where
    #0  0x00007f272af61969 in raise () from /lib64/libc.so.6
    #1  0x00007f272af62f98 in abort () from /lib64/libc.so.6
    #2  0x00007f272b54dd3d in _g_log_abort () from /lib64/libglib-2.0.so.0
    #3  0x00007f272b56b127 in g_assertion_message () from /lib64/libglib-2.0.so.0
    #4  0x00007f272b56b18a in g_assertion_message_expr () from /lib64/libglib-2.0.so.0
    #5  0x00007f272c6881ae in gtk_icon_info_load_icon_finish () from /lib64/libgtk-3.so.0
    #6  0x00007f272dc518fe in on_icon_loaded (source=0x257ca50, result=0x6af4e00, user_data=0x670b6b0) at st/st-texture-cache.c:657
    #7  0x00007f272bcd5c9b in g_task_return_now () from /lib64/libgio-2.0.so.0
    #8  0x00007f272bcd5cb9 in complete_in_idle_cb () from /lib64/libgio-2.0.so.0
    #9  0x00007f272b547146 in g_main_context_dispatch () from /lib64/libglib-2.0.so.0
    #10 0x00007f272b547498 in g_main_context_iterate.isra.24 () from /lib64/libglib-2.0.so.0
    #11 0x00007f272b54789a in g_main_loop_run () from /lib64/libglib-2.0.so.0
    #12 0x00007f272cc7fb61 in meta_run () from /lib64/libmutter.so.0
    #13 0x0000000000401d9c in main (argc=1, argv=0x7fff696abff8) at main.c:439



Reproducible: 

Steps to Reproduce:
David Walser 2014-12-22 19:56:51 CET

Assignee: bugsquad => olav

Comment 1 Olav Vitters 2015-02-05 12:43:53 CET
I'd really like to see the assertion message. Is there anything from journalctl?

Sorry for being so slow with responding.

Keywords: (none) => NEEDINFO
Status: NEW => ASSIGNED

Comment 2 Herbert Poetzl 2015-02-08 07:38:27 CET
Maybe this one:

Dec 22 07:15:50 aquinas gnome-session[11327]: (gnome-shell:12041): GLib-GIO-CRITICAL **: g_file_new_for_path: assertion 'path != NULL' failed
Dec 22 07:15:50 aquinas gnome-session[11327]: (gnome-shell:12041): GLib-GIO-CRITICAL **: g_loadable_icon_load: assertion 'G_IS_LOADABLE_ICON (icon)' failed
Dec 22 07:15:50 aquinas gnome-session[11327]: (gnome-shell:12041): GLib-GIO-CRITICAL **: g_file_new_for_path: assertion 'path != NULL' failed
Dec 22 07:15:50 aquinas gnome-session[11327]: (gnome-shell:12041): GLib-GIO-CRITICAL **: g_loadable_icon_load: assertion 'G_IS_LOADABLE_ICON (icon)' failed
Dec 22 07:15:50 aquinas gnome-session[11327]: Gtk:ERROR:gtkicontheme.c:4078:gtk_icon_info_load_icon_finish: assertion failed: (icon_info_get_pixbuf_ready (icon_info))

CC: (none) => herbert

Comment 3 Samuel Verschelde 2015-09-21 13:18:58 CEST
Mageia 4 changed to end-of-life (EOL) status on 2015-09-19. It is is no longer 
maintained, which means that it will not receive any further security or bug 
fix updates.

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 
Mageia version.

Bug Reporter: Thank you for reporting this issue and we are sorry that we weren't 
able to fix it before Mageia 4's end of life. If you are able to reproduce it 
against a later version of Mageia, you are encouraged to click on "Version" and 
change it against that version of Mageia. If it's valid in several versions, 
select the highest and add MGAxTOO in whiteboard for each other valid release.
Example: it's valid in cauldron and Mageia 5, set to cauldron and add MGA5TOO.

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 Mageia 
release includes newer upstream software that fixes bugs or makes them obsolete.

If you would like to help fixing bugs in the future, don't hesitate to join the
packager team via our mentoring program [1] or join the teams that fit you 
most [2].

[1] https://wiki.mageia.org/en/Becoming_a_Mageia_Packager
[2] http://www.mageia.org/contribute/
Comment 4 Marja Van Waes 2015-10-27 06:56:25 CET
As announced over a month ago, Mageia 4 changed to end-of-life (EOL) status on 2015-09-19. It is is no longer maintained, which means that it will not receive any further security or bug fix updates.

This issue may have been fixed in a later Mageia release, so, if you still see it and didn't already do so: please upgrade to Mageia 5 (or, if you read this much later than this is written: make sure you run a currently maintained Mageia version)

If you are able to reproduce it against a maintained version of Mageia, you are encouraged to 
1. reopen this bug report, by changing the "Status" from "RESOLVED - OLD" to "REOPENED"
2. click on "Version" and change it against that version of Mageia. If you know it's valid in several versions, select the highest and add MGAxTOO in whiteboard for each other valid release.
Example: it's valid in cauldron and Mageia 5, set to cauldron and add MGA5TOO.
3. give as much relevant information as possible. If you're not an experienced bug reporter and have some time: please read this page:
https://wiki.mageia.org/en/How_to_report_a_bug_properly

If you see a similar issue, but are _not_sure_ it is the same, with the same cause, then please file a new bug report and mention this one in it (please include the bug number, too). 


If you would like to help fixing bugs in the future, don't hesitate to join the
packager team via our mentoring program [1] or join the teams that fit you 
most [2].
[1] https://wiki.mageia.org/en/Becoming_a_Mageia_Packager
[2] http://www.mageia.org/contribute/

Status: ASSIGNED => RESOLVED
Resolution: (none) => OLD


Note You need to log in before you can comment on or make changes to this bug.