Comments
-
Greg Hurrell
I suspect this is the same underlying issue as bug #192; basically a bug in Tiger. A bug report has been filed with Apple and marked as a duplicate, so this is evidently a known issue for them.
You may find that it goes away on the next reboot, or if you reinstall the app. You should take a look at bug #192 to see the kind of information that would need to be collected on the command line in order to develop a work around meanwhile we wait for Apple to fix the bug. That bug report actually applies to Synergy, not Synergy Advance, but the principles are the same.
-
Scott Melendez
I rebooted several times this AM on an unrelated issue, and I was able to duplicate it each time.
(In reply to comment #1)
I suspect this is the same underlying issue as bug #192; basically a bug in Tiger. A bug report has
been
filed with Apple and marked as a duplicate, so this is evidently a known issue for them.
You may find that it goes away on the next reboot, or if you reinstall the app. You should take a look
at
bug #192 to see the kind of information that would need to be collected on the command line in
order to
develop a work around meanwhile we wait for Apple to fix the bug. That bug report actually applies
to
Synergy, not Synergy Advance, but the principles are the same.
-
Greg Hurrell
(In reply to comment #2)
I rebooted several times this AM on an unrelated issue, and I was able to duplicate it each time.
Like I said, you *might* find that it goes away next reboot (evidently you didn't). If you reinstall the app as well, or move it, it *might* go away. The bug in Tiger is that the Launch Services database is not updating and these things which I am recommending *might* force it to update.
So basically, I am still waiting for someone to do some investigation on the command line as described in bug #192 so that I can figure out how to work around the bug (I'm actually a bit baffled as to why nobody wants to do this work seeing as the original bug was filed over three months ago and I posted detailed instructions on how to gather information on the command line over 10 weeks ago). Seeing as I am unable to reproduce this bug locally I am dependent on others to gather the required information. It's particularly frustrating because this is not a bug in Synergy Advance (or Synergy) but in Tiger; but more information is required.
-
Greg Hurrell
Making the summary a little more descriptive.
-
Luke Leidal
Having the same problem of "Don't show Synergy Advance icon in Dock" not working after system reboot. Running a dual 1gHz G4 with 1gHz RAM, OS 10.3.9. Problem still arises after several reboots.
-
Greg Hurrell
(In reply to comment #5)
Having the same problem of "Don't show Synergy Advance icon in Dock" not working after system reboot. Running a dual 1gHz G4 with 1gHz RAM, OS 10.3.9. Problem still arises after several reboots.
Still waiting for someone to provide information gathered on the command line, as described in bug #192. Even a million "me too" reports won't help to workaround this bug; the only thing which will solve it is information provided by users who can reproduce the problem.
-
Scott Melendez
Wincent,
I looked in my Synergy plist you suggested in 192, and LSUIElement is set to 1.
(In reply to comment #0)
I have Synergy Advance to start when iTunes starts, and I checked the "Don't show in Dock" option. However, when I rebooted my system, that preference was checked, but Synergy Advance was still in
the
Dock.
OS X 10.4.2, 1.67 GHz G4, 2 Gb RAM.
(In reply to comment #3)
(In reply to comment #2)
I rebooted several times this AM on an unrelated issue, and I was able to duplicate it each time.
Like I said, you *might* find that it goes away next reboot (evidently you didn't). If you reinstall the
app
as well, or move it, it *might* go away. The bug in Tiger is that the Launch Services database is not updating and these things which I am recommending *might* force it to update.
So basically, I am still waiting for someone to do some investigation on the command line as
described
in bug #192 so that I can figure out how to work around the bug (I'm actually a bit baffled as to why nobody wants to do this work seeing as the original bug was filed over three months ago and I
posted
detailed instructions on how to gather information on the command line over 10 weeks ago). Seeing
as
I am unable to reproduce this bug locally I am dependent on others to gather the required
information.
It's particularly frustrating because this is not a bug in Synergy Advance (or Synergy) but in Tiger; but more information is required.
-
Michael
Looking at the dump I noticed that the ui-element was missing for Synergy Advance. Running lsregister /Applications resolved this issue for me. I'm guessing it didn't get updated when I installed .2 over .1.2
before lsregister -kill -------------------------------------------------------------------------------- bundle id: 65808
path: /Volumes/Synergy Advance 0.1.2/Synergy Advance.app name: identifier: com.wincent.SynergyAdvance version: 0.1.2 mod date: 5/11/2005 10:35:12 type code: 'APPL' creator code: 'SAdv' sys version: 10.3 flags: relative-icon-path ppc item flags: container package application extension-hiddennative-app scriptable
icon: Contents/Resources/Synergy Advance.icns executable: Contents/MacOS/Synergy Advance inode: 20 exec inode: 280 container id: 1072 library: library items:--------------------------------------------------------------------------------
after lsregister -kill -------------------------------------------------------------------------------- bundle id: 34248
path: /Applications/Local/Synergy Advance.app name: identifier: com.wincent.SynergyAdvance version: 0.2 mod date: 7/26/2005 7:46:45 type code: 'APPL' creator code: 'SAdv' sys version: 10.3 flags: relative-icon-path ui-element launch-disabled ppc i386 item flags: container package application extension-hiddennative-app scriptable
icon: Contents/Resources/Synergy Advance.icns executable: Contents/MacOS/Synergy Advance inode: 1803126 exec inode: 1803386 container id: 32 library: library items:--------------------------------------------------------------------------------
-
Matthew Potter
After trying both what was in the bug #192 and what I understood of what was written here I haven't been able to solve the problem. There is something else too... When I check the plist for 'SA' I find:
NoIconInDock
something that to me would indicate that it shouldn't show in the dock (duh I know but wait!). I then quit the application and relaunch it, revert the plist file and this line remains the same. Even with the icon showing in the dock.
the "LSUIElement" element does not appear in the file and if I add it, it just removes it on next boot.
Running: 10.3.9, Dual 867MHz, 1GB 10.3.9, 600Mhz, 384MB
Whole plist: <?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE plist PUBLIC "-//Apple Computer//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/ PropertyList-1.0.dtd">
AnimateDockIcon AutoLaunchSynergyAdvanceWhenITunesIsLaunched HotKeyBackITunes HotKeyCode 123 HotKeyModifiers 10223616 HotKeyITunesDecreaseRating HotKeyCode 27 HotKeyModifiers 1835008 HotKeyITunesDecreaseVolume HotKeyCode 125 HotKeyModifiers 10223616 HotKeyITunesIncreaseRating HotKeyCode 24 HotKeyModifiers 1835008 HotKeyITunesIncreaseVolume HotKeyCode 126 HotKeyModifiers 10223616 HotKeyITunesRateFiveStars HotKeyCode 87 HotKeyModifiers 3932160 HotKeyITunesRateFourStars HotKeyCode 86 HotKeyModifiers 3932160 HotKeyITunesRateOneStar HotKeyCode 83 HotKeyModifiers 3932160 HotKeyITunesRateThreeStars HotKeyCode 85 HotKeyModifiers 3932160 HotKeyITunesRateTwoStars HotKeyCode 84 HotKeyModifiers 3932160 HotKeyITunesRateZeroStars HotKeyCode 82 HotKeyModifiers 3932160 HotKeyNextITunes HotKeyCode 124 HotKeyModifiers 10223616 HotKeyPauseITunes HotKeyPlayITunes HotKeyPlayPauseITunes HotKeyCode 49 HotKeyModifiers 1835008 HotKeyShowGrowlNotification HotKeyCode 44 HotKeyModifiers 1835008 LSUIElement 1 NSToolbar Configuration WOPreferencesWindow TB Display Mode 1 TB Icon Size Mode 1 TB Is Shown 1 TB Item Identifiers ShowAll NSToolbarSeparatorItem General Growl Hot Keys Instant Messaging Registration TB Size Mode 1 NSWindow Frame Preferences 32 1025 591 122 0 0 1600 1178 NewVersionCheckFrequency 1 NoIconInDock SendGrowlNotificationsWhenPlayerStateChanges ShowCoverArtInDockIcon ShowTrackProgressInDockIcon
-
Greg Hurrell
Woah, a bit of clarification here; there are TWO files we're talking about. The one you've pasted in your comment, Matthew, is the preferences file:
~/Library/Preferences/com.wincent.SynergyAdvance.plist
The entry in that file for "NoIconInDock" is just a record for the benefit of Synergy Advance so that it knows whether or not the corresponding checkbox in the preference pane should be checked. The default value for this setting is "false", so if you delete your preferences file the setting will revert to false. In fact, it won't even appear in the file because there's no point in recording settings that are just left at their default value; it only records deviations from the default. If you toggle the setting to "true" then and only then will Synergy Advance add it to the preferences file.
Now, the other file we're talking about here is:
SynergyAdvance.app/Contents/Info.plist
This file is the one which Mac OS X is supposed to read at launch time and figure out whether or not to show the dock icon. This file is the one where the setting of "LSUIElement" has effect. When you toggle the setting in the preference pane Synergy Advance actually modifies this file. The "LSUIElement" which is in your *preferences* file will have no effect at all.
Now, those who are having problems here are actually getting bitten by a bug in Tiger. As shown by Michael's contribution in comment #8 the Launch Services database is not getting updated as it should (basically, Tiger is completely ignoring the LSUIElement setting). The work around is to force the Launch Services database to update itself and re-read the Info.plist file. You can do this manually using the "lsregister" command line tool, or you can just wait until I release the next version of Synergy Advance (it now runs the lsregister tool at the appropriate times to correct any problems in the Launch Services database; basically this means that even if the database has stale entries in it, Synergy Advance will fix the appropriate entry and on the next launch the Dock icon will appear or not appear exactly as you would expect).
Adding "fixed-in-prerelease" keyword which I forgot to add last time.
-
Greg Hurrell
This fix is now available in the just-released version 0.4b. For more information:
https://wincent.dev/a/news/archives/2006/03/synergy_advance_4.php
Marking as FIXED/CLOSED.
Add a comment
Comments are now closed for this issue.