Bug 7481

Summary: grilo-test-ui segfaults
Product: Mageia Reporter: Reinout van Schouwen <reinout>
Component: RPM PackagesAssignee: Funda Wang <fundawang>
Status: RESOLVED OLD QA Contact:
Severity: critical    
Priority: Normal CC: remco
Version: 2   
Target Milestone: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Source RPM: grilo CVE:
Status comment:

Description Reinout van Schouwen 2012-09-15 00:43:29 CEST
Description of problem:
According to the README, grilo-test-ui offers a GTK+ user interface to browse through media.
When started, it segfaults with the following stack trace:

Thread 1 (Thread 0x7ffff7fbf8a0 (LWP 25669)):
#0  0x00007ffff76696a8 in gtk_tree_model_get_valist (tree_model=0x86bac0, iter=0x7fffffffd6e0, var_args=0x7fffffffd5e8) at gtktreemodel.c:1766
#1  0x00007ffff766998c in gtk_tree_model_get (tree_model=0x86bac0, iter=0x7fffffffd6e0) at gtktreemodel.c:1728
#2  0x00000000004095a2 in browser_row_selected_cb (tree_view=<optimized out>, user_data=<optimized out>) at main.c:841
#3  0x00007ffff69d8ca2 in g_closure_invoke (closure=0x892f10, return_value=0x0, n_param_values=1, param_values=0x7fffffffd910, invocation_hint=<optimized out>)
    at gclosure.c:777
#4  0x00007ffff69e9d71 in signal_emit_unlocked_R (node=<optimized out>, detail=0, instance=<optimized out>, emission_return=0x0, instance_and_params=0x7fffffffd910)
    at gsignal.c:3547
#5  0x00007ffff69f2099 in g_signal_emit_valist (instance=0x896030, signal_id=<optimized out>, detail=0, var_args=<optimized out>) at gsignal.c:3296
#6  0x00007ffff69f2242 in g_signal_emit (instance=<optimized out>, signal_id=<optimized out>, detail=<optimized out>) at gsignal.c:3352
#7  0x00007ffff768a83f in gtk_tree_view_real_set_cursor (tree_view=0x896030 [GtkTreeView], path=0x0, flags=<optimized out>) at gtktreeview.c:13298
#8  0x00007ffff768cfd6 in gtk_tree_view_set_model (tree_view=0x896030 [GtkTreeView], model=<optimized out>) at gtktreeview.c:11514
#9  0x00000000004064af in ui_setup () at main.c:1725
#10 main (argc=1, argv=0x7fffffffde28) at main.c:2064

Version-Release number of selected component (if applicable):
0.1.18

How reproducible:
Always

Steps to Reproduce:
1. Run 'grilo-test-ui' from the command line
2.
3.
Comment 1 Remco Rijnders 2012-09-15 14:39:26 CEST
Assigning to maintainer.

@funda: I see version 0.1.19 in updates_testing for over a month now, but don't see an open bugreport for this package. For what it's worth, using the version of updates_testing, I can't reproduce Reinout's original issue.

Assignee: bugsquad => fundawang

Remco Rijnders 2012-09-15 14:39:40 CEST

CC: (none) => remco

Comment 2 Manuel Hiebel 2013-10-22 12:10:57 CEST
This message is a reminder that Mageia 2 is nearing its end of life.
Approximately one month from now Mageia will stop maintaining and issuing updates for Mageia 2. At that time this bug will be closed as WONTFIX (EOL) if it remains open with a Mageia 'version' of '2'.

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 prior to Mageia 2's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Mageia 2 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 Mageia, you are encouraged to click on "Version" and change it against that version of Mageia.

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.

-- 
The Mageia Bugsquad
Comment 3 Manuel Hiebel 2013-11-23 16:14:19 CET
Mageia 2 changed to end-of-life (EOL) status on ''22 November''. Mageia 2 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 Mageia
please feel free to click on "Version" change it against that version of Mageia
and reopen this bug.

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

--
The Mageia Bugsquad

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