Bug 1397699

Summary: Drop down Xfce terminal disapears
Product: [Fedora] Fedora Reporter: Miro Hrončok <mhroncok>
Component: xfce4-terminalAssignee: Kevin Fenzi <kevin>
Status: CLOSED CURRENTRELEASE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 25CC: christoph.wickert, f2404, kevin, nonamedotc
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-01-10 18:23:06 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:

Description Miro Hrončok 2016-11-23 08:29:25 UTC 
Description of problem:
Drop down terminal is sometimes not rendering and I have to kill it in order to start the new one.

Version-Release number of selected component (if applicable):
xfce4-terminal-0.8.0-1.fc25.x86_64

How reproducible:
Always

Steps to Reproduce (in Xfce):
1. Maximize a window (probably any, but tested with Chromium and Geany)
2. Run `xfce4-terminal --drop-down` so that the terminal is rendered over that maximized window
3. Switch to a different virtual desktop

Actual results:
Terminal disappears.
`xfce4-terminal --drop-down` does nothing.
There is no way to display the drop down terminal other than killing the process and running a new one. All work in killed terminal and bash history is lost.

Expected results:
Terminal stays open. When it is disappeared, running `xfce4-terminal --drop-down` shows it again.
Comment 1 Kevin Fenzi 2016-11-23 14:43:46 UTC 
I think this may well have been fixed in 0.8.1, which is in updates-testing. 

Can you try a: 

sudo dnf --enablerepo=updates-testing update xfce4-terminal 

and see if 0.8.1 fixes this?
Comment 2 Miro Hrončok 2016-11-23 15:46:35 UTC 
I had to download it manually but it fixes it, thanks.
Comment 3 Igor 2017-01-10 18:13:31 UTC 
I guess the bug can be closed?
Comment 4 Kevin Fenzi 2017-01-10 18:23:06 UTC 
Yep. ;)