Processing Ajax...

Title
Close Dialog

Message

Confirm
Close Dialog

Confirm
Close Dialog

Confirm
Close Dialog

User Image
Bjørn Skarmark
9 discussion posts
After updating to DisplayFusion 9 (and the same with 9.1), the extended taskbar has some issues.

What causes it, I have yet to figure out but the symptoms are that the taskbar starts to flash once per second. When that happens, no new icons appear in the taskbar if I move a window to it. Both windows opened on the second screen, and windows moved to it.

Additionally, windows that were up on the second screen before the freeze which are closed afterwards, appear to stay in the taskbar. I can click the icon, but nothing more happens.

If I try to open settings and disable/enable the taskbars, it dissapeares from the second monitor but will not re-initialize.

I've tried shutting down DisplayFusion and opening it again (Windows Task/Processes) without any fix. The only thing that has solved it is a reboot.

Windows/Video-drivers and such are updated.
Nov 20, 2017 (modified Nov 20, 2017)  • #1
User Image
Josh Ellen
8 discussion posts
I also wanted to point out that I am having taskbar issues with the new Beta 9.1. The taskbar does not behave correctly when it comes to always on top. In fact, it behaves more like a window than anything.

The taskbar(s) should ALWAYS be on top unless there is a specific setting to override it (which I have not found).

One of the anomalies that I have seen is with hidden DF taskbar. If the start button is enabled, it is always on top but if the start menu is disabled the taskbar is allowed to be covered. This behavior is slightly different when the DF taskbar is not allowed to auto-hide.

EDIT: I attached a screenshot showing all 3 monitors. Left=Native taskbar, middle=DF Taskbar with Start Menu, right=DF Taskbar without Start menu.
• Attachment: 2017-11-20_094504.png [117,063 bytes]
2017-11-20_094504.png
2017-11-20_094504.png
Nov 20, 2017 (modified Nov 20, 2017)  • #2
User Image
Bjørn Skarmark
9 discussion posts
Noticed something new. When the freeze happens, the Ctrl+Shift+ESC hotkey to bring up Windows Task Manager doesn't work.

I can still access it both via the Right-click shortcut on the DisplayFusion taskbar, or via Windows Settings, but not with the key-combination.
Nov 21, 2017  • #3
User Image
Bjørn Skarmark
9 discussion posts
And now, I found a weird workaround; When leaving my desk I tried to use the hotkey WIN+L to lock the computer. But that didn't work, same as with Ctrl+Shift+ESC. So I did a Ctrl+Alt+Del to access the fullscreen menu in Windows7 where you can Lock, Change users, Logout and such.

When I did that, everything blinked a couple of times, and suddenly everything worked as it should.
Nov 21, 2017  • #4
Keith Lammers (BFS)'s profile on WallpaperFusion.com
Could you guys send me a debug log for this issue?
  • On the DisplayFusion Settings > Troubleshooting tab, change the Logging drop-down to "L1: Log Minimal" and click Apply
  • Reproduce the issue and note the time so we'll know where to check in the log file
  • Send us the DisplayFusion.log and DebugInfo.html files (can be found by clicking the Open Log button on the Troubleshooting tab)
  • Disable debug logging after sending the log

Thanks!
Nov 21, 2017  • #5
User Image
Bjørn Skarmark
9 discussion posts
Here's the debug info.
You can start at 2017/11/22 11:30:00 and look backwards. I came back to my desk after about 20 minutes away, and noticed the taskbar had frozen again.
At about 11:31 I attempted again the Ctrl+Shift+ESC and WIN+L hotkeys incase the log registered them. They did not work. Same as before.

I then did the Ctrl+Alt+Del, and like before it fixed the problem.
• Attachment [protected]: DebugInfo.html [234,803 bytes]
• Attachment [protected]: DisplayFusion.log [2,153,590 bytes]
Nov 22, 2017  • #6
Keith Lammers (BFS)'s profile on WallpaperFusion.com
Thanks! According to the log, DisplayFusion thinks the screen saver was still running. The next time this happens, can you check the Windows Task Manager > Processes tab to see if DisplayFusion.scr is listed? If it is, can you try killing it and see if that stops the taskbar flashing?
Nov 22, 2017  • #7
User Image
Bjørn Skarmark
9 discussion posts
You were correct. It was running DFSSaver.scr *32.
Killing it via Task Manager fixed the issue.

The error does not trigger with Preview Screensaver, both in DisplayFusion and the Windows screensaver settings, but will trigger with normal screensaver activation. Testet with a couple of different Timeout settings.
Nov 24, 2017  • #8
User Image
Bjørn Skarmark
9 discussion posts
Quote:
The error does not trigger with Preview Screensaver, both in DisplayFusion and the Windows screensaver settings, but will trigger with normal screensaver activation. Testet with a couple of different Timeout settings.


Actually, that's not correct.
If it matters for future bugfixing, I was using the Windows Ribbons screensaver.
I was thinking I could try one of the DisplayFusion screensavers to see if the same error occured, but while running through preview on those the error triggered again.

Killing the process still works fine to fix it.
Nov 24, 2017 (modified Nov 24, 2017)  • #9
Keith Lammers (BFS)'s profile on WallpaperFusion.com
Ok interesting! Good to know that it can happen when previewing, that might help us track it down faster.

I'll be sure to post an update when we've made some progress on this issue.

Thanks for your help so far!
Nov 24, 2017  • #10
Keith Lammers (BFS)'s profile on WallpaperFusion.com
We've just released a new DisplayFusion beta version and this issue should be all fixed up. Please let us know if you run into any trouble after updating.

Thanks!
Nov 26, 2019  • #11
Subscribe to this discussion topic using RSS
Was this helpful?  Login to Vote(1)  Login to Vote(-)