Description of problem: When windows are marked urgent (for example: when you're being pinged on irc) the window title will flash, but the button on the panel (on the window button widget) will not blink as it did in past fedora releases. Version-Release number of selected component (if applicable): xfce4-panel-4.10.0-2.fc18.x86_64 How reproducible: Everytime Steps to Reproduce: 1. Open xchat, minimize, have someone send you a private message Actual results: xchat icon does not blink Expected results: xchat icon should blink
This is configurable... Go to xfce window manager tweaks. Go to the accessability tab. check 'keep urgent windows blinking' Does that get you what you seek?
I have that turned on, but it only blinks the title bar of the window, it doesn't blink it in the panel (with the window buttons widget). So if the window is minimized, I can see it in the panel, but I have no way of seeing when a window is marked as urgent.
Re-reading this, perhaps check xchat settings? settings->Chatting->Alerts then check the blink task bar checkboxes?
I do have that checked, and when the checkbox is checked, it just marks the window as urgent (so the title bar will blink), but for some reason in F18 the window buttons in the panel won't blink.
I can confirm the bug is present in F19. My setup: 1) xchat: Settings -> Preferences -> Chatting -> alerts -> "Blink task bar on:" enabled everywhere 2) xfce: Window Manager Tweeks -> Accessability -> "Notify of urgency .." and also "Keep urgent .." check enabled When one mentions my name on IRC, the channel name color gets blue (i.e. xchat alert works) but the window button in the panel does not blink. This seems to be a regression since F16 that I used previously (not sure of F17 status).
Odd. Does the behavior persist with hexchat? (I can't duplicate it with hexchat here).
Yes, when I use hexchat I get the same behavior. The title bar with flash with hexchat, but the pager won't flash at the bottom of the screen. So if I minimize hexchat and someone private messages me I don't get any notification.
Odd. So, f18 never worked? Or it did for you on initial install, but not after updates? Can you confirm the behavior with a newly created user? (That will tell us if it's system wide, or per user settings somehow).
(In reply to Kevin Fenzi from comment #8) > Odd. > > So, f18 never worked? Or it did for you on initial install, but not after > updates? > > Can you confirm the behavior with a newly created user? (That will tell us > if it's system wide, or per user settings somehow). FYI I noticed that misbehaviour on a freshly new installation of F19 (no upgrade but install).
Fresh install with no updates? Or all updates applied when you installed?
(In reply to Kevin Fenzi from comment #10) > Fresh install with no updates? Or all updates applied when you installed? I *think* I noticed it immediately after installing fresh F19 before updating it. But definitely the problem persists after all updates.
What do you have the window buttons prefs set to? Anything non default there? Grouping? Do you have multiple xchat/hexchat windows open?
(In reply to Kevin Fenzi from comment #12) > What do you have the window buttons prefs set to? > > Anything non default there? Grouping? > > Do you have multiple xchat/hexchat windows open? Show button labels: checked Show flat buttons: not checked Show handle: checked Sorting order: "None, allow drag-and-drop Window grouping: Never Restore minimized windows to current workspace: not checked Draw window frame when hovering a button: not checked Switch windows using the mouse wheel: checked Show windows from all workspaces or viewports: not checked Show windows from all monitors: checked Show only minimized windows: not checked Just one instance of xchat running.
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.
(In reply to Fedora End Of Life from comment #14) > 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. Seen in F19 (xfce4-panel-4.10.1-3.fc19.x86_64), hence Version changed.
Seen in F20 as well, and also seen on Suse: https://bugzilla.novell.com/show_bug.cgi?id=809766 Switching theme from Adwaita to Clearlooks indeed "fixes" it.
So, I guess this is a adwaita bug?
I've a feeling this is one of those things that are "nobodys fault": If its legal for a theme to use a background image in place of color, its kinda hard to claim the theme is buggy because it does that. Yet it clearly breaks functionality that some people rely on. Dunno...
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. 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 '20'. 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 20 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 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 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.