Bug 14903 - RawTherapee crashes when changing the default 'save to' folder
Summary: RawTherapee crashes when changing the default 'save to' folder
Status: RESOLVED OLD
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 4
Hardware: x86_64 Linux
Priority: Normal critical
Target Milestone: ---
Assignee: Funda Wang
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-12-28 11:59 CET by Boyan Krachev
Modified: 2015-09-21 17:35 CEST (History)
1 user (show)

See Also:
Source RPM: rawtherapee-4.0.11-2.1.mga4.src.rpm
CVE:
Status comment:


Attachments

Description Boyan Krachev 2014-12-28 11:59:35 CET
Description of problem: Unable to change the Default Save to folder


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


How reproducible: Always


Steps to Reproduce:
1. Start Rawtherapee
2. Select "Queue" tab
3. Select "Save to folder:" radio button
4. Change the folder from the drop-down menu next to it.


Konsole output:

[@localhost ~]$ rawtherapee

(rawtherapee:20815): Gtk-CRITICAL **: gtk_tree_model_filter_get_value: assertion 'GTK_TREE_MODEL_FILTER (model)->priv->stamp == iter->stamp' failed

(rawtherapee:20815): GLib-GObject-WARNING **: gtype.c:4215: type id '0' is invalid

(rawtherapee:20815): GLib-GObject-WARNING **: can't peek value table for type '<invalid>' which is not currently referenced
Segmentation fault

Reproducible: 

Steps to Reproduce:
David Walser 2014-12-28 13:16:22 CET

Assignee: bugsquad => fundawang

Comment 1 marc fanjoux 2015-01-02 08:59:32 CET
Same here !
Rawtherappe crash when i change the Default folder

CC: (none) => marcounet

Comment 2 Samuel Verschelde 2015-09-21 10:21:46 CEST
Does this still happen in Mageia 5?
Comment 3 Samuel Verschelde 2015-09-21 13:18:47 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 marc fanjoux 2015-09-21 17:23:14 CEST
no crash in mageia5 ...
Comment 5 Rémi Verschelde 2015-09-21 17:35:14 CEST
Thanks, marking as OLD for Mageia 4 then.

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


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