Port bug 768378 - Updates create a new Windows 7 taskbar icon instead of using the already pinned one
Categories
(Thunderbird :: Upstream Synchronization, defect)
Tracking
(thunderbird17-, thunderbird18+, thunderbird19+)
People
(Reporter: standard8, Unassigned)
References
Details
+++ This bug was initially created as a clone of Bug #768378 +++ Afer updating Aurora using the built-in updater, a new Windows 7 taskbar icon is shown (with the same icon), instead of using the icon I already pinned. This happens for every update, not just upgrading from one branch to another. This also happens on Thunderbird Beta builds.
Reporter | ||
Updated•12 years ago
|
Reporter | ||
Comment 2•12 years ago
|
||
The core bugs are landing for 18, so we'll look at doing the same.
Updated•4 years ago
|
Comment 3•2 years ago
|
||
Newer bug 1197577 is very similar, but was incomplete.
I have seen this, too.
(In reply to Thomas D. (:thomas8) from bug 1197577 comment #6)
I have been affected by this bug for a long time, and it has been extremely annoying.
Unfortunately it'll be impossible to reconstruct the exact circumstances.
I may have changed the application path or command line switches on the pinned shortcut over time.
But the net result was a pinned link without switches nor profile switches (application path wasC:\Program Files\Thunderbird Daily\thunderbird.exe
, I guess that's a non-default path, and it does have its own auto-associated profile).
Every time when clicking the pinned shortcut, it would open a new icon at the end of the taskbar instead of highlighting the already pinned icon.I succeeded to fix it for now by pinning the secondary icon instead, which now works correctly.
Updated•2 years ago
|
Comment 4•2 years ago
|
||
I'm not 100% sure if this is the same as my issue. Every few days (when thunderbird updates?) my pinned taskbar shortcut dies. (It's replaced by a useless white page icon). Pinning thunderbird again removes this icon, and then pinning it yet again finally restores the functional pinned icon (for a few more days.)
Comment 5•10 months ago
•
|
||
Upstream bug 768378 has been fixed.
Description
•