Bug 907539

Summary:	Thunar crashes when going Back to non-exisitng directory
Product:	[Fedora] Fedora	Reporter:	Miro Hrončok <mhroncok>
Component:	Thunar	Assignee:	Kevin Fenzi <kevin>
Status:	CLOSED ERRATA	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	18	CC:	admiller, christoph.wickert, kevin, pertusus
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-05-19 18:57:52 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Miro Hrončok 2013-02-04 16:35:18 UTC

Description of problem:
When gong Back in Thunar, but the directory in history doesn't exist anymore, Thunar crashes.

Version-Release number of selected component (if applicable):
1.6.2-1.fc18

How reproducible:
Always.

Steps to Reproduce:
1. Create a directory, let's say ~/testdir
2. Navigate Thunar to that directory
3. Go up in directory structure (in example case to ~)
4. Either rename or delete ~/testdir
5. Go back in history (use toolbar icon or hit [Backspace])
  
Actual results:
Thunar crashes

Expected results:
Thunar raises error saying the directory in history no longer exists and asks the user if he wants to go directly to last existing directory in history. The error dialog provides a checkbox to prevent this dialog to show again next time.

Or simply perform the action above without any dialog.

Additional info: ABRT catches this, but the retrace server is overloaded

Should I report this upstream?

Comment 1 Kevin Fenzi 2013-02-04 18:52:44 UTC

Yes, upstream report would be great. ;)

Comment 2 Miro Hrončok 2013-02-04 19:56:31 UTC

ABRT marks this as a duplicite of #891332

Comment 3 Christoph Wickert 2013-02-04 23:39:33 UTC

Thanks for filing the bug report upsream. Jannis is currently on side at a customer, not sure when he has time to look at it.

Comment 4 Fedora Update System 2013-05-05 23:14:37 UTC

tumbler-0.1.29-1.fc18,Thunar-1.6.3-1.fc18,garcon-0.2.1-1.fc18,xfce4-settings-4.10.1-1.fc18,xfwm4-4.10.1-1.fc18,xfce4-panel-4.10.1-1.fc18,xfce4-session-4.10.1-1.fc18,xfce4-appfinder-4.10.1-1.fc18,libxfce4util-4.10.1-1.fc18 has been submitted as an update for Fedora 18.
https://admin.fedoraproject.org/updates/tumbler-0.1.29-1.fc18,Thunar-1.6.3-1.fc18,garcon-0.2.1-1.fc18,xfce4-settings-4.10.1-1.fc18,xfwm4-4.10.1-1.fc18,xfce4-panel-4.10.1-1.fc18,xfce4-session-4.10.1-1.fc18,xfce4-appfinder-4.10.1-1.fc18,libxfce4util-4.10.1-1.fc18

Comment 5 Fedora Update System 2013-05-07 18:30:12 UTC

Package tumbler-0.1.29-1.fc18, Thunar-1.6.3-1.fc18, garcon-0.2.1-1.fc18, xfce4-settings-4.10.1-1.fc18, xfwm4-4.10.1-1.fc18, xfce4-panel-4.10.1-1.fc18, xfce4-session-4.10.1-1.fc18, xfce4-appfinder-4.10.1-1.fc18, libxfce4util-4.10.1-1.fc18:
* should fix your issue,
* was pushed to the Fedora 18 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing tumbler-0.1.29-1.fc18 Thunar-1.6.3-1.fc18 garcon-0.2.1-1.fc18 xfce4-settings-4.10.1-1.fc18 xfwm4-4.10.1-1.fc18 xfce4-panel-4.10.1-1.fc18 xfce4-session-4.10.1-1.fc18 xfce4-appfinder-4.10.1-1.fc18 libxfce4util-4.10.1-1.fc18'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2013-7532/tumbler-0.1.29-1.fc18,Thunar-1.6.3-1.fc18,garcon-0.2.1-1.fc18,xfce4-settings-4.10.1-1.fc18,xfwm4-4.10.1-1.fc18,xfce4-panel-4.10.1-1.fc18,xfce4-session-4.10.1-1.fc18,xfce4-appfinder-4.10.1-1.fc18,libxfce4util-4.10.1-1.fc18
then log in and leave karma (feedback).

Comment 6 Kevin Fenzi 2013-05-19 18:57:52 UTC

This update was pushed stable.