Bug 1181862 - Evince duplicated window border/buttons on xfce
Summary: Evince duplicated window border/buttons on xfce
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: xfwm4
Version: 21
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Kevin Fenzi
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-01-13 23:32 UTC by Raul Cheleguini
Modified: 2015-12-02 17:04 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2015-12-02 07:24:08 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
Screenshot (12.88 KB, image/png)
2015-01-13 23:32 UTC, Raul Cheleguini
no flags Details
xfwm4 (33.99 KB, image/png)
2015-01-25 20:06 UTC, Mukundan Ragavan
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Xfce 10631 0 None None None Never

Description Raul Cheleguini 2015-01-13 23:32:08 UTC
Created attachment 979778 [details]
Screenshot

Description of problem:

For some reason, Evince is showing double window borders and buttons as you can see in the attached screenshot.

Evince shows its own minimize/maximize/close buttons in addition to the ones provided by xfwm4.

Not sure if that is happening with all Gnome3 applications.


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

evince-3.14.1-7.fc21.x86_64

How reproducible:

Install Fedora 21 XFCE spin
Install package evince
Run evince
Notice the double window


Actual results:

Duplicated minimize/maximize/close buttons.

Expected results:

Normal window, no duplicated buttons.

Additional info:

In Fedora 20, evince behaves normal.

Comment 1 Marek Kašík 2015-01-14 10:27:26 UTC
This is a xfwm4 bug according to https://bugzilla.xfce.org/show_bug.cgi?id=10631.

Comment 2 Raul Cheleguini 2015-01-14 12:40:38 UTC
Thank you Marek.
As mentioned on project's bug report, the workaround is enable the window compositor at 'Window Manager Tweaks'.

Comment 3 Kevin Fenzi 2015-01-14 14:25:04 UTC
I don't want to pull that patch until upstream decides if they want to apply it... will keep an eye on the upstream bug though. ;)

Comment 4 Mukundan Ragavan 2015-01-25 20:06:30 UTC
Created attachment 984004 [details]
xfwm4

Kevin, I think this patch is upstreamed and is present in xfwm4-4.11.

$ rpm -qa xfwm* | sort
xfwm4-4.11.2-1.fc21.x86_64

I can see if I can port this specific patch - without pulling the entire 4.11 stack.

Comment 5 Fedora End Of Life 2015-11-04 15:42:37 UTC
This message is a reminder that Fedora 21 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 21. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '21'.

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 Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 21 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 Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

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 Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 6 Fedora End Of Life 2015-12-02 07:24:12 UTC
Fedora 21 changed to end-of-life (EOL) status on 2015-12-01. Fedora 21 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
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

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


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