Bug 15775 - Thunar forgets chosen layout (list vs icons) for displaying files
Summary: Thunar forgets chosen layout (list vs icons) for displaying files
Status: RESOLVED WORKSFORME
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: i586 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Jani Välimaa
QA Contact:
URL:
Whiteboard: 5beta3
Keywords: Triaged
Depends on:
Blocks:
 
Reported: 2015-04-26 19:43 CEST by Citroen Zuur
Modified: 2015-04-27 15:42 CEST (History)
0 users

See Also:
Source RPM: thunar
CVE:
Status comment:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Citroen Zuur 2015-04-26 19:43:48 CEST 
Description of problem:

When launching Thunar the layout of persists to a detailed list, even after there has been chosen for icons.

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


How reproducible: everytime I open Thunar.


Steps to Reproduce:
1.Open Thunar, set layout to icons and close Thunar.
2.Open Thunar again and the list is back.


Reproducible: 

Steps to Reproduce:
Comment 1 Samuel Verschelde 2015-04-26 23:01:44 CEST 
Assigning to maintainer.

Keywords: (none) => Triaged
Assignee: bugsquad => jani.valimaa
Summary: Thunar. => Thunar forgets chosen layout (list vs icons) for displaying files
Source RPM: Mageia-5-beta3-i586-DVD => thunar
Whiteboard: (none) => 5beta3

Comment 2 Jani Välimaa 2015-04-27 14:36:59 CEST 
You'll have to change the default behavior via Edit -> Preferences -> Display tab -> "View new folders using". Select "Last active view" setting and Thunar acts like you expected.

The phrasing might be a bit confusing as it talks about new folders, but this is how Thunar currently works. Please file an upstream bug (https://bugzilla.xfce.org) if you think the phrasing and/or behavior should be improved.

I'm closing this as WORKSFORME, feel free to reopen if needed.

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

Comment 3 Citroen Zuur 2015-04-27 15:42:46 CEST 
This worked for me too.
Note You need to log in before you can comment on or make changes to this bug.