Currently Being ModeratedDec 13, 2011 8:19 AM (in response to Skiziks)
I think I have the culprit!
I'm a big fan of resetting Safari to keep those cookies off my trail and there seems to be a connection with this and the incredibly irritating iTunes pop-up.
Try unchecking the 'Remove all website data' box in the Safari/Reset Safari options and see if that helps you too.MacBookPro 4,1 - 2.6 Intel Core 2 Duo, Mac OS X (10.7.2), 4GB RAM - GeForce 8600M (512MB) GT
Currently Being ModeratedDec 13, 2011 1:02 PM (in response to Skiziks)
In light of your response I've checked and checked again and, for me at least, this is most definitely the connection.
If I reset Safari with 'Remove all website data' checked I get the nag screen when I open iTunes.
If I reset Safari with 'Remove all website data' unchecked I do not get the nag screen when I open iTunes.
May I suggest you try the following: close iTunes, reset Safari with 'Rawd' checked, close Safari, open iTunes and do whatever it asks, close iTunes, open Safari, reset Safari with 'Rawd' unchecked, close Safari, and (finally!) open iTunes and see what happens? I would be interested to know your findings.
BTW: This is all on the latest 10.5.2 update which, of itself, did not fix the problem as hoped.MacBookPro 4,1 - 2.6 Intel Core 2 Duo, Mac OS X (10.7.2), 4GB RAM - GeForce 8600M (512MB) GT
Currently Being ModeratedDec 13, 2011 1:25 PM (in response to Livebox)
With "Rawd" checked, did the reset and closed Safari.
Opened iTunes, no pop-up, but had to Force Quit to close it.
Reopened iTunes, two pop-ups, signed in.
Unchecked "Rawd", did the reset and closed Safari.
Opened iTunes, two pop-ups again.
Opened Safari, left box unchecked, opened iTunes, two pop-ups once again.
Currently Being ModeratedDec 13, 2011 1:43 PM (in response to Livebox)
Resetting Safari will not fix the problem.
I am on Win7 and don't have Safari installed and got the popups with 10.5.1. So the problem is in iTunes itself, both Windows and Mac versions.
Currently Being ModeratedDec 14, 2011 2:11 AM (in response to CharlesDayton)
I agree. The culprit is really iTunes' inability to heed the user's preference to disable Automatic Downloads, and therefore stop requesting authorization to perform such downloads.
Though iTunes and Safari both make use of the WebKit framework, it makes no logical or technical sense for the preferences used by one application to affect another, either intentionally or unintentionally.
Currently Being ModeratedDec 14, 2011 10:08 AM (in response to Skiziks)
I'm sorry that didn't work for you. I was keen to hear back from you either way because I really want to understand what's going on. I was hoping it would work: a) so that you and others can stop gnashing your teeth at pop-ups, and b) so that I can reassure myself that it is not just my system that has a weird glitch.
That's definitely interesting to hear and makes me all the more curious. I already understand that resetting Safari will not fix the problem. In my case it is resetting Safari that apparently causes the problem (dependent on whether a certain action is checked or not) and that just doesn't sit right with me.
Apple ][ Forever:
I really don't understand this either and totally agree that it makes no logical sense. This is why I'm so keen to find out more. I can only reconfirm that I can replicate this anomaly again and again with the method I previously described. I am able to open iTunes without pop-ups 100% of the time now.
It concerns me that this connection manifests itself in my case, and not for Skiziks for example. It concerns me that actions in one application can apparently have an impact on what I consider to be an entirely unconnected application.
Perhaps there is an answer lurking in the Webkit framework you mentioned.
Ultimately, I want to be able to 'Remove all website data' when I quit Safari, but I also want to not have annoying pop-ups when opening iTunes.
My apologies for hijacking your thread Skiziks.
Let's hope that Apple come up with a swift and effective fix.MacBookPro 4,1 - 2.6 Intel Core 2 Duo, Mac OS X (10.7.2), 4GB RAM - GeForce 8600M (512MB) GT
Currently Being ModeratedDec 19, 2011 7:29 PM (in response to Skiziks)
see this post i created
i am having the same issue and updating itunes did not fix the issue
Currently Being ModeratedDec 27, 2011 11:36 AM (in response to avnyc11)
I guess the problem is still continuing for everyone as I still have the problem with no fixes in sight! As I stated in a different discussion, with the introduction of iMatch and iCloud and the old Mobile Me, it seems that all this 'i" stuff has brought on problems! The worst part of the whole mess is the arrogance that Apple has that they won't even come forward and admit there is something going on. I think I put my eggs in one basket with this iTunes store. Think I'll be starting to look elsewhere.
Currently Being ModeratedDec 28, 2011 12:03 AM (in response to rfa5)
A little perspective, please.
The manner in which this bug manfests itself is annoying, and an irritant. But nothing more.
It does not affect iTunes' functionality. It does not cause data loss. In terms of severity, it is minor, and affects only a particular subset of users.
No piece of software is perfect. All software has bugs. A complex piece of software like iTunes is likely to have hundreds, if not thousands, most of them unbeknownst to the majority of users.
With the exception of the most severe, or those requiring immediate action to prevent the loss of functionality or data, bugs are rarely noted or discussed outside of development channels, nor are the timetables to squash them laid out for public scruitiny. This applies not only for Apple, but for the vast majority of software developers.
I'd like to see this issue resolved as quickly as the next person. But I can see the forest for the trees, and reasonably expect that it will be addressed in a future release.
Currently Being ModeratedJan 3, 2012 1:17 AM (in response to Skiziks)
try this: start iTunes by right-click, and "Run as administrator", then enter your password when it asks, close iTunes, start it again (normally, as usual, this time), and voilá!
i had the same problem on my new notebook (Win7, 64 bit), but this method eliminated the problem today morning.
please let me now, if it worked for you, too! ;-)