Created attachment 744791 [details] potential patch from Debian to resolve the issue Description of problem: The title bar of windows is not displayed when using some more complex themes where a xpm file is used for color definition. This affects e. g. the icedesert theme and the clearlooks theme, so that the icewm-cleearlooks package is not usable. Because the title bar is not displayed one can not grab the window to move it around. Version-Release number of selected component (if applicable): icewm-1.3.7-7 xorg-x11-server-Xorg-1.13.3-3 How reproducible: Use icewm with icedesert or clearlooks theme from package icewm-cleearlooks Actual results: title bar is not displayed Expected results: title bar is displayed Additional info: As a workaround it helps to delete title*.xpm files from /usr/share/icewm/themes/*/* - of course the title bar is then displayed in different colors It seems to be the same bug as Debian #688908 at http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=688908 The path Debian used to resolve the issue is attached
Hi Henry. Is the patch directly applicable on the f18 sources? Guys, is anybody willing to look at this annoying issue? As all the good looking themes are affected and somebody could have bad luck when trying to select different themes, I consider this issue a serious one. The system becomes unusable for less experienced users. I could test/modify/commit the patch if needed. Just let me know if you're ok with that. Thanks, Jaromir.
Hi Jaromir, yes, the patch is directly applicable on the f18 sources (tested on xorg-x11-server-1.13.3-3.fc18.src.rpm). Regards, Henry
Hi Henry. I just discussed the issue with Adam Jackson and he believes it isn't safe to revert crash prevention commits for suid root stuff. The issue needs a proper solution and that can take some time, since the fbBresSolid function isn't well documented and somebody needs to dig deeper in order to find out, how it is intended to work. I can't promise anything, but I'll try to look at that this or the next week. Regards, Jaromir.
Fedora 19 still affected
I'd mark it as dupe of http://bugzilla.redhat.com/show_bug.cgi?id=981758 Essentially, 1-pixel XPM images from IceWM themes are incorrectly rendered on nvidia drivers.
Henry, Please attach nvidia bug report by running nvidia-bug-report.sh as root user.
I don't use the proprietary NVidia driver and thus I don't have nvidia-bug-report.sh. Besides, the bug occurs on non-NVidia cards as well, e.g. in VirtualBox using VESA driver.
*** Bug 981758 has been marked as a duplicate of this bug. ***
Henry, Thus far I never managed to reproduce this issue on non-nVidia drivers. Please post your complete VirtualBox configuration so I can try and reproduce it. - Gilboa
Gilboa, please find the config file below. To what nVidia driver are you referring? The proprietary driver, nouveau or both? <?xml version="1.0"?> <!-- ** DO NOT EDIT THIS FILE. ** If you make changes to this file while any VirtualBox related application ** is running, your changes will be overwritten later, without taking effect. ** Use VBoxManage or the VirtualBox Manager GUI to make changes. --> <VirtualBox xmlns="http://www.innotek.de/VirtualBox-settings" version="1.7-linux"> <Machine uuid="{c8d6b594-5585-4d9f-b10e-bd893e27de9f}" name="Fedora" OSType="Fedora" snapshotFolder="Snapshots" lastStateChange="2013-12-11T09:39:58Z"> <ExtraData> <ExtraDataItem name="GUI/LastCloseAction" value="powerOff"/> <ExtraDataItem name="GUI/LastGuestSizeHint" value="720,400"/> <ExtraDataItem name="GUI/LastNormalWindowPosition" value="0,15,640,409,max"/> <ExtraDataItem name="GUI/LastWindowPostion" value="187,162,1024,815"/> <ExtraDataItem name="GUI/MiniToolBarAlignment" value="bottom"/> <ExtraDataItem name="GUI/SaveMountedAtRuntime" value="yes"/> <ExtraDataItem name="GUI/ShowMiniToolBar" value="yes"/> </ExtraData> <Hardware version="2"> <CPU count="1"> <HardwareVirtEx enabled="true"/> <HardwareVirtExNestedPaging enabled="false"/> <HardwareVirtExVPID enabled="false"/> <PAE enabled="false"/> <HardwareVirtExLargePages enabled="false"/> </CPU> <Memory RAMSize="1024"/> <Boot> <Order position="1" device="Floppy"/> <Order position="2" device="DVD"/> <Order position="3" device="HardDisk"/> <Order position="4" device="None"/> </Boot> <Display VRAMSize="24" monitorCount="1" accelerate3D="true"/> <VideoRecording/> <RemoteDisplay enabled="true" port="3389" authType="Null" authTimeout="5000"/> <BIOS> <ACPI enabled="true"/> <IOAPIC enabled="false"/> <Logo fadeIn="true" fadeOut="true" displayTime="0"/> <BootMenu mode="MessageAndMenu"/> <TimeOffset value="0"/> <PXEDebug enabled="false"/> </BIOS> <DVDDrive passthrough="false"> <Image uuid="{9ed1547f-2ef5-4e05-983c-4901791def9c}"/> </DVDDrive> <FloppyDrive enabled="true"/> <USBController enabled="false" enabledEhci="false"/> <Network> <Adapter slot="0" enabled="true" MACAddress="08002715E953" cable="true" speed="0" type="Am79C973"> <NAT/> </Adapter> <Adapter slot="1" enabled="false" MACAddress="080027B36EE1" cable="true" speed="0" type="Am79C973"/> <Adapter slot="2" enabled="false" MACAddress="080027802B05" cable="true" speed="0" type="Am79C973"/> <Adapter slot="3" enabled="false" MACAddress="080027CD1C71" cable="true" speed="0" type="Am79C973"/> <Adapter slot="4" enabled="false" MACAddress="0800274EE051" cable="true" speed="0" type="Am79C973"/> <Adapter slot="5" enabled="false" MACAddress="08002737E84E" cable="true" speed="0" type="Am79C973"/> <Adapter slot="6" enabled="false" MACAddress="080027267590" cable="true" speed="0" type="Am79C973"/> <Adapter slot="7" enabled="false" MACAddress="08002755CF56" cable="true" speed="0" type="Am79C973"/> </Network> <UART> <Port slot="0" enabled="false" IOBase="0x3f8" IRQ="4" hostMode="Disconnected"/> <Port slot="1" enabled="false" IOBase="0x3f8" IRQ="4" hostMode="Disconnected"/> </UART> <LPT> <Port slot="0" enabled="false" IOBase="0x378" IRQ="4"/> <Port slot="1" enabled="false" IOBase="0x378" IRQ="4"/> </LPT> <AudioAdapter controller="AC97" driver="ALSA" enabled="true"/> <SharedFolders/> <Clipboard mode="Bidirectional"/> <DragAndDrop mode="Disabled"/> <Guest memoryBalloonSize="0"/> <GuestProperties> <GuestProperty name="/VirtualBox/GuestAdd/HostVerLastChecked" value="4.2.12" timestamp="1367936932994598000" flags=""/> <GuestProperty name="/VirtualBox/GuestAdd/Revision" value="84980" timestamp="1367936791898771000" flags=""/> <GuestProperty name="/VirtualBox/GuestAdd/Vbgl/Video/SavedMode" value="1280x963x32" timestamp="1367937231429644000" flags=""/> <GuestProperty name="/VirtualBox/GuestAdd/Version" value="4.2.12" timestamp="1367936791898291000" flags=""/> <GuestProperty name="/VirtualBox/GuestInfo/OS/Product" value="Linux" timestamp="1367936791897040000" flags=""/> <GuestProperty name="/VirtualBox/GuestInfo/OS/Release" value="3.8.11-200.fc18.i686" timestamp="1367936791897522000" flags=""/> <GuestProperty name="/VirtualBox/GuestInfo/OS/Version" value="#1 SMP Wed May 1 20:39:37 UTC 2013" timestamp="1367936791897808000" flags=""/> <GuestProperty name="/VirtualBox/HostInfo/GUI/LanguageID" value="de_DE" timestamp="1373276980950486000" flags=""/> </GuestProperties> </Hardware> <StorageControllers> <StorageController name="IDE Controller" type="PIIX4" PortCount="2"> <AttachedDevice type="HardDisk" port="0" device="0"> <Image uuid="{4d3bcdb9-9ec9-4fcc-ba6a-bf2b2a450c7a}"/> </AttachedDevice> </StorageController> </StorageControllers> </Machine> </VirtualBox>
Henry, Thus far I only managed to reproduce this issue when using the nVidia binary driver. Are you using the VirtualBox guest tools on the guest? - Gilboa
FWIW 1.3.8 package will include a second clearlooks-2px that, as the name suggests, uses a 2-pixel wide borders. - Gilboa
Gilboa, that is interesting, because I do use nouveau driver only on two different machines with nVidia graphics and not the proprietary nVidia driver. I don't use the guest tools on the guest.
Hi Gilboa. The issue is well reproducible even in VNC sessions with virtual displays not bound to any video driver. Try this: 1.) install tigervnc-server as root yum install tigervnc-server 2.) start the vncserver as a regular user vncserver :11 3.) enter your favorite password :] 4.) kill the vnc session vncserver -kill :11 5.) open the VNC xstartup script newly created in your home dir with your favorite editor vim ~/.vnc/xstartup 6.) ... and keep just the following content in the file #!/bin/sh unset SESSION_MANAGER unset DBUS_SESSION_BUS_ADDRESS exec icewm-session 7.) start the vncserver again vncvserver :11 8.) connect to the virtual session and enter the previously chosen password vncviewer :11 The issue *IS* reproducible with the following themes: infadel2 clearlooks icedesert The issue *IS NOT* reproducible with the following themes: gtk2 metal2 motif nice nice2 warp3 warp4 win95 yellowmotif
Fedora 20 still affected
This message is a reminder that Fedora 18 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 18. 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 WONTFIX if it remains open with a Fedora 'version' of '18'. 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 prior to Fedora 18's end of life. Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 18 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 to Fedora 18's end of life. 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.
I can reproduce this issue in multiple environments under F20. - Gilboa
This message is a notice that Fedora 19 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 19. It is Fedora's policy to close all bug reports from releases that are no longer maintained. Approximately 4 (four) weeks from now this bug will be closed as EOL if it remains open with a Fedora 'version' of '19'. 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 19 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.
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 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.
I can't reproduce this issue with Fedora 22.