Closed Bug 674338 Opened 13 years ago Closed 13 years ago

Impossible to correctly pin several Thunderbird 7 shortcuts into Windows 7 task bar

Categories

(Thunderbird :: OS Integration, defect)

7 Branch
x86
Windows 7
defect
Not set
minor

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 577867

People

(Reporter: david.pate, Unassigned)

Details

I try to attach/pin several thunderbird shortcuts to winsows 7 task bar. I use several shortcuts as I launch different profils thru those shortcuts.

Only the first shortcut is attached. The second one stays over the task bar, but when I release the mouse button, nothing happens on the task bar.

A second icon of thunderbird should have been pinned to the windows task bar.
Multiple profiles work but aren't really supported, and supporting jumplists seems way more important than multiple profiles. As I understand it, because app model IDs are unique per application version and you can only have one shortcut per app model ID in the taskbar, you can only have one or the other. Probably WONTFIX unless Firefox has somehow worked around the same issue.

Workarounds include launching from the command-line and adding shortcuts to the desktop or start menu instead.
Severity: normal → minor
i.e. David, could you please check whether Firefox has the same issue? If it does, then this should be WONTFIXed.
Firefox has NOT the same issue. I can pin twice Firefox 5 to the task bar. But only one Thunderbird.
The bug still exists in TB 6.
Version: 5.0 → 6
I seem to be able to pin multiple Tb shortcuts just fine, actually, as long as the target is different. Could you try creating a shortcut in a temporary directory, adding -P <profilename> to the target, then dragging it to the taskbar?
The two TB I try to pin have the following targets:
"C:\Program Files\Mozilla Thunderbird\thunderbird.exe" -p "Marie"
and
"C:\Program Files\Mozilla Thunderbird\thunderbird.exe" -p "David"
But it doesn't work.
If I right click on the first shortcut, I can select "Pin to TaskBar", I select it. But when I right click on the second shortcut, the only option is "Unpin from the taskbar". Sorry if the words are not exactly the good ones as I use a French version. I have to translate it with my words in English with my best guess of how it is in the English version.
When i drag the first shortcut to the task bar it is OK, but when I drag the second shortcut, I have a ban sign.
Summary: Impossible to pin several Thunderbird 5 shortcuts into Windows 7 task bar → Impossible to pin several Thunderbird 7 shortcuts into Windows 7 task bar
Version: 6 → 7
TB 7.0.1 behavior has changed on this issue compared to TB 6: I still cannot
Summary: Impossible to pin several Thunderbird 7 shortcuts into Windows 7 task bar → Impossible to correctly pin several Thunderbird 7 shortcuts into Windows 7 task bar
TB 7.0.1 behavior has changed on this issue compared to TB 6: I still cannot pin the 2 TB profiles as I used to do it in TB 3. But, I can now pin one TB profile, launch the application and pin the application I've launched also. Indeed, when I launch the TB profile, it is not detected as the same application in the Windows 7 taskbar and consequently, there are 2 TB icons in the bar and I'm allowed to pin the second icon as well. But this icon cannot be linked to the TB profile, it is only the generic TB shortcut. So when I click that pinned icon, it always asks me which profile I want to launch.
So, I think the problem is now different: when one lauches TB shortcut with a profile, it is detected as a generic TB shortcut and not as a TB profile.

Is there anybody who could works on that issue as it becomes more and more annoying and that is a real regression compared to TB 3.x?
I'am available to discuss that issue and I can share my screen with whoever would like to see what happens on my computer.
I believe bug 577867 should fix this.
I confirm the issue really looks like the one described in bug 577867.
Status: UNCONFIRMED → RESOLVED
Closed: 13 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.