Bug in Genius

The new iTunes 11.0.0.163 hung when I was using the Genius feature. When I clicked the "bullets?" icon at right of current song display, a new panel displayed a scrolling list, about 10 songs high, of songs scrolling for 2-3 minutes. Eventually the scroll stopped, but weird segments of the iTunes window started showing in other applications including Task Manager and Firefox browser.
After forced-closing runaway iTunes, a small window appeared with a warning-twang sound, titled ""Microsoft Visual C++ Runtime Libr...", with a Red-Disc X in middle and a blank button on bottom. Clicking the button closed the window. Then a Windows System box reported that CyberMedia was restarting, though I wasn't running it before. Weird, huh?
Using Win 7/64 system.
And the new interface is quite confusing, for settings, sync, play selections, etc. Will I become accustomed to it before Apple fixes it?

P.S. The song stopped playing when the song-scroll started. And iTunes memory had soared to 500 MB, then 600 ... before I stopped the application.

Similar Messages

Genius On Ipod Bug

My genius mixes cover bug, they are all repetitive like this :

Why not? Are you getting any error messages while trying to activate it? Are you getting this in iTunes or on the iPod?
B-rock

Very annoying Genius sync or BUG

Hi, i originally posted this thread a month ago on the itunes forums, but since nobody even answered i'm copying the same here, hopefully someone will at least give me a clue.
This bug or issue is incredibely annoying considering that i NEVER even use or have used Genius.
here it is:
Hi,
Since i subscribed to iTunes Match, everytime i sync my iPad with itunes it "syncs data with Genius". This takes 20-30 minutes everytime. The worst thing is i DON'T EVER use Genius. Every single time i sync my ipad it syncs half of the songs i have on my ipad with genius (around 3000 songs). Before activating itunes match each sync used to take around 5 minutes, including the backup.
PLEASE someone tell me how do i disable this incredibely annoying issue ?? I just want to go back to the normal syncs i had before itunes match, i don't see the point in what's hapening right now...
Thanks

I got rid of it by turning off Genius.
Unfortunately, I love using Genius, and hate losing all my Genius info, especially since it always comes back incomplete when I first turn Genius back on.
There has got to be a better fix for this.

Missing genius button and artwork bug

I just updated my iPhone and I noticed somethings that annoy me. Firstly, the Genius button that used to be in the middle of the bar when a song was playing is now nowhere to be found. Second, now when I add artwork manually to my albums the artwork is misaligned with a little strip of the rightside of the cover art appearing at the beginning of the left side. Help?

I read some other posts and one guy said you have to create a playlist in the side bar, then open the play list. Once you do that the burn disc button will appear. If you are showing you entire library, the button will not show.
I just tried it and it works.

Genius and Disabling Itunes Store but allowing Itunes U Access bug?

If I disable the Itunes Store in Parental Settings but allow Itunes U access then Genius disappears and cannot be used. Does anyone else have this problem??
If I disable the Itunes Store in Parental Settings completely (and not allow Itunes U access) then Genius works fine.
Am using iTunes 9.

This is still not fixed in iTunes 9.01

IPad iTunes genius BUG

So, I clicked genius at iTunes music store app. I got message stating that I need to download favorites so that genius could recommendations. Fair enough, BUT I can't access music store main page anymore. There is no buttons visible anymore. I can click podcasts etc from below, but always clicking "music" brings this message.
Not to mention that "downloads" section has only text about agreements, informal message about " no active downloads" would be nice.

Been having the same problem. Read one of the above messages, it started for me too after clearing Safari history. Just figured it out (a workaround, anyway):
Open a program that will link you into the iTunes store, I used Shazam. Tag a song, then click the tab to 'purchase in itunes'. iTunes will open, you'll get your music selection window on top of iTunes (background may go grey for a moment). Close out the album or song selection, and all should be back to normal.

BUG: Categories callout box in Genius tab stacks up multiple times

http://i1050.photobucket.com/albums/s411/jmp909/69dcc613.jpg
Go to the genius tab in the app store and click the category button at the top left multiple times
Where is the best replace to report this?
Thanks
J

You report it here:
http://www.apple.com/feedback/ipad.html

Bug in app store, genius tab

Hello,
I've erased my iPad recently, a couple of times. I do initial configs, enable "genius" on the app store, and I can never scroll while on "genius". It works fine on featured, top chards, etc. Just on "genius" it gets locked and no scroll happens.
iPad 2, 16 wifi, iOS 6.1.3
Anyone get the same behaviour?
K

Find whatever apps your purchased under that Apple ID, and remove them from your system. Dragging to Trash is pretty much all you'll have to do.

Unable to activate Genius

I am unable to activate Genius since upgrading to Windows 7. Prior with Vista and iTunes 9 Genius worked fine. Upgrade to Win7 and I cannot activate Genius.
It goes through step 1 fine then goes into step 2. It pops up an error message after about a minute that says "We could not complete your iTunes store request. The network connection timed out. Make sure your network connections are correct and your network connection is active, then try again".
Well, I have been trying again later for about a month all with the same error.
I have rebuilt the library--no luck.
I CAN access and download new content from the iTunes store. I just cannot activate genius.
Options?
Here is the diagnostic test result:
Microsoft Windows 7 Business Edition (Build 7600)
HP-Pavilion GC676AA-ABA m8150n
iTunes 9.0.2.25
QuickTime 7.6.5
FairPlay 1.5.23
Apple Application Support 1.1.0
iPod Updater Library 9.0d11
CD Driver 2.2.0.1
CD Driver DLL 2.1.1.1
Apple Mobile Device 2.6.0.32
Apple Mobile Device Driver not found.
Bonjour 1.0.6.2 (118.5)
iTunes Serial Number ECBC09B56D49EBBB
Current user is not an administrator.
The current local date and time is 2010-01-30 15:14:02.
iTunes is not running in safe mode.
Video Display Information
NVIDIA, NVIDIA GeForce 8400 GS
** External Plug-ins Information **
No external plug-ins installed.
Genius ID: 1f7f9cc788585092f8a4d0207622ff5d
iPodService 9.0.2.25 is currently running.
iTunesHelper 9.0.2.25 is currently running.
Apple Mobile Device service 2.50.39.0 is currently running.
** Network Connectivity Tests **
Network Adapter Information
Adapter Name: {87E5ED95-1C2D-4E08-B471-2D2CAE68D47A}
Description: Microsoft Virtual WiFi Miniport Adapter
IP Address: 0.0.0.0
Subnet Mask: 0.0.0.0
Default Gateway: 0.0.0.0
DHCP Enabled: Yes
DHCP Server:
Lease Obtained: Wed Dec 31 19:00:00 1969
Lease Expires: Wed Dec 31 19:00:00 1969
DNS Servers:
Adapter Name: {EB040ABD-6DE1-4A0A-90EB-6B94ECB7CF48}
Description: Bluetooth Device (Personal Area Network)
IP Address: 0.0.0.0
Subnet Mask: 0.0.0.0
Default Gateway: 0.0.0.0
DHCP Enabled: Yes
DHCP Server:
Lease Obtained: Wed Dec 31 19:00:00 1969
Lease Expires: Wed Dec 31 19:00:00 1969
DNS Servers:
Adapter Name: {822D4B32-268D-4D10-9127-FC7AF814ABA3}
Description: USB Wireless 802.11 b/g Adaptor
IP Address: 0.0.0.0
Subnet Mask: 0.0.0.0
Default Gateway: 0.0.0.0
DHCP Enabled: Yes
DHCP Server:
Lease Obtained: Wed Dec 31 19:00:00 1969
Lease Expires: Wed Dec 31 19:00:00 1969
DNS Servers:
Adapter Name: {FBB54D1F-6C23-41DD-957F-C801A6EB801B}
Description: Intel(R) 82566DC Gigabit Network Connection
IP Address: 192.168.254.3
Subnet Mask: 255.255.255.0
Default Gateway: 192.168.254.254
DHCP Enabled: Yes
DHCP Server: 192.168.254.254
Lease Obtained: Sat Jan 30 14:43:12 2010
Lease Expires: Sat Jan 30 14:43:11 2010
DNS Servers: 192.168.254.254
192.168.254.254
Active Connection: LAN Connection
Connected: Yes
Online: Yes
Using Modem: No
Using LAN: Yes
Using Proxy: No
SSL 3.0 Support: Enabled
TLS 1.0 Support: Enabled
Firewall Information
Windows Firewall is on.
iTunes is enabled in Windows Firewall.
Connection attempt to Apple web site was successful.
Connection attempt to iTunes Store was successful.
Secure connection attempt to iTunes Store was successful.
Secure connection attempt to iPhone activation server was successful.
Last successful store access was 2010-01-30 15:12:04.

I finally managed to fix this problem by removing groups of songs from my library until Genius successfully started. I started removing artists beginning with A and by the time I got down to D Genius started to work. This made me think that it was related to a specific song. However, I gradually added all of the tracks back in to my library and Genius continued to update OK!! I now have all of the same songs in the library and Genius is working fine. I have over 12000 songs in my library so it may be a bug related to the number of tracks. The downside to removing the tracks (but keeping the files) is that you lose the playcount and you have to add them to your playlists again.
Hope this helps.

IOS6 WIFI bug, still not work now, exhausted,help...

Been like this a week now, tried every possiable way still not any help at all, it can connect the wifi, internet works for 1or 2 minuts then will faile again, changed one router and tried all different settings as still not work, someone told me they don't have this problem they are using different router,maybe it's because IOS6 have sort of confict with some brand router? I am using TPlink, should I keep invest different router and try? Or should I wait for bug fixed?
Apple didn't give any suggestion to customer and time schedule for bug fixed, this is really **** me off...
I will try to visit apple store to check if they can change a new one with IOS5 for me.

They will not change you back to iOS 5. I asked.
I spent almost 1 week trying to resolve this. Reboot the ipad, reboot my router, delete the network, rejoin the network. Nothing seems to work. I called the Apple support, spent 2 days. After trying every single solution (that I've already done before calling.. duhhh)..
They told me to:
- Go to iTunes.Back up all your data, transfer all purchases to your computer. Of course when I tried to transfer all my purchases, they stuck for hours, then crash everything. I had to redo this 3 times. HOURS!!!
- Restore your iPad from your iTunes. It will erase everything in your iPad, then start fresh as new
- Turn off your iPad
- Turn off your router, give it 10-15 minutes, turn on your router
- Turn on your iPad, join the network
Even though finally it looks ok. I am still going to return this iPad and get a replacement. I just don't feel confident with the device anymore. I just bought my iPad less than 3 months, still got the box. The support told me I could swap my iPad, all I need is to see the Apple Genius. So I made appointment, otherwise the Genius won't see you.
I got tons of questions again from the Genius. He said it is my router problem. Basically, I have a crappy router that came from my internet provider. He said that since they opened the store, he only knew TWO people came in with WIFI issue. I told him, all my other devices connect just fine... but of course, they're "oranges" not Apple.
I thought I'll be getting my replacement right away, but no.. Genius had to place an order first, and they will call me again, and I have to make another appointment to pick it up. I wonder why they don't have one in stock. It's the NEW iPad!!! I hope they're not getting my replacement from some kinda refurbished factory.
This is my first purchase with Apple. So far it is not a pleasant experience.

Ongoing fatal crash and security bug related to connecting external display

The infrastructures in OS X to resume from sleep, to authenticate, and to change displays is fundamentally not working.
The security bug I have encountered has to do with connecting a cinema display exclusively to a MacBook Pro. This is a specific situation, but please note that I have experienced the same problem on no fewer than three independent laptop. Plus, the Genius in the Apple Retail Store was convinced of the general instability of this infrastructure. The security problem is that hot corners no longer function if I transition between two states in the same reboot. The first state is where I have the laptop powered on and using its own internal display exclusively (when I'm on the road). The second state is when I have the laptop displaying its output exclusively on an external display (when I'm at home). What happens is that an attempt to use hot corners fails. There is no response. I even added configuration on all four corners (whereas I originally had settings only for the rightmost corners), and even then, the hot corner action (of sleeping the display or entering locked screen saver mode) does not commence. This prevents the user from being able to secure the display on demand using standard methods that are supposed to work.
The instability level related to connecting the external display exclusively is high. Again, I've experienced this on no fewer than three independent laptops, and the Apple Genius at the Retail Store confirmed that this aspect of OS X did not work consistently. When I want to connect the cinema display to the laptop in such a way that the laptop's own display is not part of the active screen, the process I use succeeds about half the time. Supposing I have been on the road, where I am using the laptop display exclusively. I then put the laptop to sleep. When I return home with the lid open, I connect first the USB (power) from the cinema display to the laptop, and then I connect the Mini DisplayPort. When that step works, what happens is that the login screen shows on the cinema display despite the fact that my laptop lid is closed. This is good, and is what I want. At that point, I open the laptop lid and quickly log in.
With Apple being a mobile device company, I rely on the laptop for tasks that one traditionally may use a desktop for. This simply points to the versatility of the laptop. But I'd like the bugs resolved, so that I do not have to hesitate to make use of the inherent flexibility possible with the MacBook Pro.
Here's what happens when the process (of connecting the external display in a way that establishes itself as the only screen in use by OS X) fails. Firstly, when I connect the external display via Mini DisplayPort, the laptop doesn't even respond. Instead, it remains asleep. So to work around it I have to repeatedly disconnect and reconnect the Mini DisplayPort so that the asleep MacBook Pro will see that there is a display connected to it. Also, sometimes that isn't even enough and I have to open the laptop lid, and put it to sleep again so as to trigger whatever actions are necessary to recognise the external display (presumably by having the laptop recently awake). Around half the time, I have to play this game of disconnecting and reconnecting until it actually works. This high level of reproducibility (confirmed by the Apple Genius representative's confidence that this part of the system doesn't actually work) should make it easy for an engineer to look into the problem.
Fatally, and recently, OS X has completely crashed when I have attempted to connect the external display. The external display has gone completely blue, and after a half a minute, it blanked out and my entire laptop became unresponsive. I called Apple Support and was given a case number. I also took the laptop into the retail store to see if I could recover my current session without rebooting. There was no process suggested to make that happen and I was told to reboot the machine. I've had this happen before on other laptops, and it is frustrating that the kernel reaches such a state that it cannot be used. As I see it, this problem is not too unrelated to the way that I need to play a game in order to get the external display connected exclusively. Here are some workarounds that could be added:
Firstly, whenever I connect an external display, I'd like the laptop to see that this has happened, and to take action accordingly (such as resuming from sleep). Secondly, If I connect an external keyboard, and press a key on it, I'd like this to wake the laptop too (in the event that the first method fails for some unforeseen reason). I'd also like the connection of the cinema display's USB power not to cause the laptop to enter into a confused state between asleep and awake. Sometimes I need to disconnect and reconnect USB power in order to trigger the laptop into waking, but that's only because it's not doing it on its own properly. On the other hand, I also ensure that the laptop doesn't have the Mini DisplayPort connected without also having the cinema display USB power connected, because that also is an unsupported configuration.
I've also gotten the laptop to become confused about whether it is asleep or awake. When I open the lid, it seems to enter into sleep mode, but closing it seems to bring it into an active state.
Also, I've successfully logged on and authenticated with the screen showing exclusively on the external display. But just ten seconds after I start using the system, the laptop falls asleep--with the lid open! Whatever triggers that action doesn't seem to be on track. The laptop is open, there are incoming events such as mouse movements and key presses, and the external display is on and is in use. And then the laptop falls asleep! This has happened numerous times. Not only should this not happen; the instances where it does happen can cause further instability and put my system at risk of fatally crashing.
Also, the authentication system itself is highly buggy--far more than it should be. At times I have opened the laptop lid and caught a glimpse of a window before I have begun the login process. Also, an external authentication application that asks for Kerberos/AFS login credentials has been able to overlay itself on top of the primary authentication (whereas I should only see a single login dialog when I need to authenticate to the system). Also, I've had several of these authentication screens overlay on top of one another, although it's been months since I've experienced that one (so it may have been fixed). Also, around a third of the time, the window that authenticates me (on the black background) somehow transfers itself into the background (even though there's only one window!). What that means is what I begin to type my password, and now the laptop starts beeping at me and I need to manually click on the password field and begin entering my password again. This really shouldn't happen, and indicates too much complexity in this authentication process (such as, more OS X code is involved than is strictly necessary, which is likely to make the authentication system more difficult to test). Also, at times, I have been using too much CPU, such that the authentication screen takes too long to emerge. That also means that I'm not able to logon until I uncleanly shutdown the laptop. If the laptop has been asleep, and is revived in preparation for login, then that login screen should be given highest priority, even if there are other heavy CPU or I/O intensive tasks running in the background. And maybe the login dialog shouldn't disappear when the user is legitimately attempting to log in. So even if there is a possibility that the system is under heavy resource use (or there is a stall or minor deadlock), it shouldn't prevent the user from logging in altogether.
At the moment, the very fact that the system shut down uncleanly means that the full disk encryption suite that I used has entered into an undetermined state, suggesting I may lose access to all my data. It's my hope that I can rely on Apple's products to interoperate in a way that won't cause me to be fearful and restrictive in my use, so that I can freely connect an external display at times, and at other times carry the laptop on the road.

Ive got the same problem with Samsung UE225010 monitor too, its full hd but it looks terrible, could it be Displayport adapter issue, because couple month ago Ive tryed with some IPS display, and it looked same bad.

Apparent kompare bug(s)

I apologise in advance for the length of this 1st-Arch-post-in-years. I value context more than brevity, I guess. Hopefully this is the longest post I'll throw at Arch for a long, long time.
I looked around (quite) a bit before filing this post. I've used Arch off-n-on since 0.4, know the Arch site, the basics about Arch, and most of the "gotcha's" farly well - but I'm no sysop, either.
I have a project I've been needing and meaning to work on for years (and which continues to compound itself while I don't); a huge set of backups on CD/DVD of all my data (my *life*, really) for well over a decade - letters, graphics, email, the first 40 pages of my book, you name it. Over the years this 'little' library has grown to over 10 GB compressed (30,000 files, *most* of them ARCHIVES). My guess is that 2-4 GB (compressed) of the data is important, some very much so.
My archive collection consists of many recursed archives themselves, and they're in about 8 or 10 different formats, to boot (even *.ice, LMAO). Many are further embedded several levels into the main archives (yes, I know that's a bad idea, but I didn't know that when I created them...). I BADLY need to unpack all this stuff, find and toss the duplicates, and truly organise (and efficiently backup) the remainder. This effort will obviously require a lot of automation (or else my heirs will either do it, or not).
I'd found a couple of useful tools in the Windows world years ago, but I don't buy software and the key piece of my suite was shareware that disabled itself after 30 days - not nearly enough time to plow through this boatload of bits.
A few months back I built a system with an Athlon XP 3500+ on an Asus A8N-E mobo w/512MB and 120 GB and 250 GB HD's. I'm hoping to go the RAID route soon - Linux software RAID, in fact. The 250 GB HD is running off an add-in PCI ATA card; both HD's have a UDMA channel all to themselves. The machine's got 4 extra fans, a nicely oversized 485W P/S, and the on-board sensors consistently show it running cool. I'm quite sure this isn't a H/W problem (I'm having no others; I built it myself...). This machine has been absolutely rock-solid in every other regard. I LOVE the system; now if I can simply use it for this one basically administrative project.
I finally have both the speed and the space required to tackle this now-monster project. When I "came home" to Arch a few months ago, I wanted to try several WMs/DMs; GNOME, KDE, E17, fluxbox and ratpoison (at least) are all loaded on my system, and I've booted most at least once. I'd assumed I'd have a LOT of options as to the tools to use.
I've been man-paging and googling and pacman -Q'ing (followed by more googling) for a couple of weeks through the course of my testing thus far, while trying various wrappers in various WMs. My concluson: Houston, we have a problem! <S>Maybe</S> Several.
In the past I've been partial to KDE (that's quickly changing), and it's what I started with this time around. As such, kompare seemed the obvious route to go, and had MOST (NOT all) of the functionality I needed (I also very much like it's GUI). Of course, kompare is simply a wrapper for diff (several diff variants, in fact, potentially). It's possible that diff is the problem. Hopefully further testing (and/or comments here) will make that determination more clearly.
Subsequent googling has revealed that the diff version shipped with Arch likely hasn't been completely functional at all levels in almost *5 YEARS* now. Diff's codefile timestamp is Sept. 3, *2002*! Version 2.8.1 (3.4 is current - just like *kompare*'s current version is 3.4). Additionally, directly below diff in that listing is diff3. Diff's codefile size is about 60K; diff3's is about 20K. *However*, they both have the same timestamp AND version # !!!
A *completely cosmetic* bug (http://bugs.kde.org/show_bug.cgi?id=138347) is fairly clearly the same bug as (https://bugs.launchpad.net/ubuntu/+source/kdesdk/+bug/45466 - 3-1/2 *YEARS* earlier!), and seemingly a trivial patch for a competent maintainer to create, at that. I've verified (w/o even trying) that this bug is resident in my system as we speak. Of course it is - the version of diff Arch is currently shipping was compiled almost a YEAR before the FIRST of the 2 bug reports above were filed! My Arch desktop O/S was installed less than a month ago using the 0.7.2 base ISO (kompare's timestamp is Jan. 20, 2007; version 3.4 - and it's a wrapper for a piece of code last compiled in 2002? What, the 2.0 kernel?). I've aggressively maintained my system current since my very recent install. See how well kompare/diff work on YOUR system...
Indeed, from the kompare bug page, it's hard to believe it's EVER been stable - or even used (see http://bugs.kde.org/simple_search.cgi?i … &offset=20 and just keep on clicking "View More Results" - or get yourself an energiser bunny to do it for you, maybe).
I copied the backups from CD's/DVD's to a clean, freshly-showered 64 GB (62.8, actually) ext3 partition (4K blocksize, defaults otherwise, journal included). I set up a top-level directory in this partition with 15 directories beneath it, one for each of my backup discs (whose contents range in size from 50 MB to 4.36 GB). I copied one archive to each directory, then unpacked them one at a time from the command line, removing the archive copy as I went. I ended up with about 15 GB of active data (25%).
I first configured kompare to use diff (w/no C/L options) running under KDE. As kdiff3 is kompare's preference, however, why is kdiff3 not already in the repos?
I'd not used it before, so I wasn't familiar with kompare's UI. I started out working with a few smaller subsets of the data I knew were near-perfect copies of each other and that wouldn't overload the filesystem. It seemed to act strangely; while I expected it to be well-optimised, both HD activity and CPU utilisation seemed extremely low for extended periods (and note my setup doesn't allow for a HDD LED for the HD on the controller card, where ALL the disk activity is going on).
After 3 runs in a row w/o a single errant file being found, I made a 2-byte mod to a small, non-critical text file that was part of the archive I was currently komparing, rebooting to make DAMNED sure cache was cleared, and reran kompare; identical results. The change STILL wasn't detected (the changed file still showed as being an exact copy of the original). The output I was getting was quite weird: usually, the 'kompare' would run at what seemed a rational speed; after a while a response screen would then open, *completely* devoid of data or messages. Immediately after that an odd dialogue box popped up; the title bar said "Error!", but the *message* was, basically, "No Duplicates Encountered." (or some such), or, more commonly, the same one I encountered repeatedly while searching the internet: "Could not parse diff output." (presumably because kompare still wasn't passing the proper parameters to diff). The program crashed about 1/2 the time (actually, give it a big enough block of data, and it'll crash every time). I was stunned 4 days later when ONE run (an exact duplicate of one I'd already attempted several times) resulted in "proper" output - *PERFECT*, with a complete and correct analysis - and completely unreproduceable, even after rebooting. It's ("It's" = proper analysis/output has) happened 3 times since, twice while working with data sets I would term 'trivial'.
So, in 2 weeks I got 3 runs w/o errors. I assure you I was trying at least 2 runs most days; a 1/2-dozen some days. By then, I also knew that kompare under KDE wasn't my only option - and I knew a bit more.
I use the "usual" repositories. When I finally checked diff's compile date, my jaw dropped: Sept. 3, *2002* !!! It's version 2.8.1; the current stable release is 3.4, and 3.5 is currently available for D/L (albeit not released). V. 2.8.1 works with the 2.6 kernel about as well as the original GWBasic compiler ('interpreter') does in WinXP...and may have been this way for a long time.
More research (difficult, given the age of what little kompare documentation is available on the web). The primary maintainer apparently got removed from maintaining the package in 2003 (and, I presume, other packages, as well) for what appeared to be 'apathy' (MY words). He 'forgot' to include an update after saying he would do so (a patch to pass the appropriate parameters to diff, hopefully fixing the "Could not parse diff output." message, and maybe even straighten out my anomolies, as well).
Kompare hasn't been updated since. Diff3 IS currently being maintained. Actually, even though diff3 has apparently replaced diff, *kompare* prefers kdiff3. For that matter, from my reading thus far, diff, diff3, vimdiff and cmp ALL may possibly be useable (the latter would require some scripting). Further, ALL the following may possibly be made able to work as wrappers (in decreasing order of likelihood, IMNSHO): kompare, krusader, meld, and emelFM2.
So, diff is broken, and it doesn't appear that it's going to be fixed...I personally was a bit consternated when I realised just how off-the-rails kompare was. I see a function such as that provided by kompare as both *critical* AND as a 'black box' function - it HAS to work. Just like the ALU MUST compute 2+2 = 4, or the 'computer' becomes a boat anchor...
So, I D/L'ed meld (for GNOME; it runs under KDE but no help is avalable), then emelFM2 (written for E17, I believe). I've spent the past week trying various combinations of (a) kompare, krusader, meld and emelFM2 as wrappers for diff under (b) KDE, GNOME, and E17. The results have been SO inconsistent it's scary. This includes both giving apparently proper results with a big job on rare occasion (but not consistently reproduceable), and VERY bizarrely, on one occasion, wiping a brand new, 64 *GB* ext3 partition CLEAN. I assure you the remainder of my testing will be on a dedicated partition! This HD is almost braad-new and has given me ZERO other trouble.
Meld was the most consistently performing diff setup I used (on any WM; it worked on them all).
I plan to spend the next 1-2 weeks doing some detailed and structured testing of all possible combos of wrapper/driver/WM, rather than just diff. I also plan to see if it's possible to pass command-line parameters to diff from kompare (if I have the time to spend ANY more w/kompare; kompare clearly isn't what I need - even though it had the . Yes, I *do* know how many combos of 4 wrappers, 4 drivers, and 3 WM's there are (48); my college major was statistics, LOL. And 48 test runs is adequate to test each combo, ONCE...
To me, this task is like big sort jobs were on mainframes a (human, not computer!) generation ago: potentially very large, critical tasks, the results of which aren't always easy to manually double-check. Surely many, if not most, users have a manner of doing this. Diff has apparently been broken for maybe 5 years and THAT wouldn't have gone unnoticed - am I one of the VERY few to even try to use kompare? What do the rest of you use?
Note that after locating and reading as much kompare documentation as possible (I read more BUG reports than anything), I made several important discoveries:
(a) kompare isn't really set up for binary files; it's intended for use with text files. You can specify an option to force a text-mode search, but you apparently canNOT do the reverse.
(b) It err'ed out comparing two M$ 'Word' files, stating they "were binary"...
(c) Worst of all, for me: These files have been archived to CD or DVD, usually repeatedly, and then copied back to disk (I've lost 3 good-sized archives this way - which does serve to somewhat justify my apparently obsessive need to backup files). Kompare does do individual file comparisons (ie, if you specify both files on the command line) byte-by-byte (block-by-block, whatever), but if you request that it compare *directories*, filename and size are all it considers (it appears from the sparse documentation I've seen that this is corrected in the *current* version, . The duplicate-file tool suite I used in Windows did an MD5 hash on *every* file, no matter the size; I *knew* when a bit error had creeped in, and usually knew fairly quickly. Not finding out you have a bad backup until it's the only copy of your data you have left is no good!
Anyone have any suggestions on doing this task efficiently and reliably in Arch?
Again, I believe this to be an upstream problem in a way, but my guess is that if we were using the *current* diffutils to match the KDE version (and a maintainer had done his job in a timely fashion) this bug would NOT exist. My advice, at least until Arch can get diff3 (or, preferably, kdiff3) packaged, STAY AWAY FROM kompare !!! At least with anything critical, at least until this issue is better understood.
Kompare (and diffutils, as well, IMO) needs to be removed from the 'public' repo's until it's close to fixed, at least. Just pkgbuild'ing the current diffutils version (or kdiff3!) is likely the easiest way out. Who knows, MAYBE I'll take a stab at that myself. No promises.
For ANYONE still reading, WOW! TIA. Really. Sorry for the tome.
Blue Skies...g
"It's a lot easier to throw grenades than it is to catch them!" -- Tim Russert

[intro, backups, bla...]I BADLY need to unpack all this stuff, find and toss the duplicates, and truly organise (and efficiently backup) the remainder.
Ok, that's what it's all about.
I'd found a couple of useful tools in the Windows world years ago, but I don't buy software and the key piece of my suite was shareware that disabled itself after 30 days - not nearly enough time to plow through this boatload of bits.
Total Commander rocks.
[killed half a dozen paragrahps or so] It's possible that diff is the problem.
Contratulations. You managed to post 3K of text but still failed to mention what the problem is.
Subsequent googling has revealed that the diff version shipped with Arch likely hasn't been completely functional at all levels in almost *5 YEARS* now. Diff's codefile timestamp is Sept. 3, *2002*! Version 2.8.1 (3.4 is current - just like *kompare*'s current version is 3.4).
http://www.archlinux.org/packages/search/?q=diffutils
You will notice that package isn't flagged out-of-date. That's because the (still current) upstream version is (tadaa!) 2.8.1. Please tell us where you found that 3.4 version.
Additionally, directly below diff in that listing is diff3. Diff's codefile size is about 60K; diff3's is about 20K. *However*, they both have the same timestamp AND version # !!!
WTF??? What listing? You know that diff and diff3 are different programs but still part of the same upstream sources, don't you?
[non-relevant nonsense...] See how well kompare/diff work on YOUR system...
They work fine.
[kompare bashing]
Take a look at the URL, bugs.kde.org, not bugs.archlinux.org. Got it?
I copied the backups from CD's/DVD's to a clean, freshly-showered 64 GB (62.8, actually) ext3 partition (4K blocksize, defaults otherwise, journal included). I set up a top-level directory in this partition with 15 directories beneath it, one for each of my backup discs (whose contents range in size from 50 MB to 4.36 GB). I copied one archive to each directory, then unpacked them one at a time from the command line, removing the archive copy as I went. I ended up with about 15 GB of active data (25%).
I think I could rest my case already at this point.
I first configured kompare to use diff (w/no C/L options) running under KDE. As kdiff3 is kompare's preference, however, why is kdiff3 not already in the repos?
It is: community/kdiff3 0.9.91-1
(I will skip some paragraphs about the actual kompare usage and come back to that at the very end.)
I use the "usual" repositories. When I finally checked diff's compile date, my jaw dropped: Sept. 3, *2002* !!! It's version 2.8.1; the current stable release is 3.4, and 3.5 is currently available for D/L (albeit not released). V. 2.8.1 works with the 2.6 kernel about as well as the original GWBasic compiler ('interpreter') does in WinXP...and may have been this way for a long time.
Please quit that bullshit and show us version 3.4 of the GNU diffutils.
Kompare hasn't been updated since. Diff3 IS currently being maintained. Actually, even though diff3 has apparently replaced diff, *kompare* prefers kdiff3. For that matter, from my reading thus far, diff, diff3, vimdiff and cmp ALL may possibly be useable (the latter would require some scripting). Further, ALL the following may possibly be made able to work as wrappers (in decreasing order of likelihood, IMNSHO): kompare, krusader, meld, and emelFM2.
Check http://websvn.kde.org/ to follow the development progress of kompare, it's part of kdesdk. diff3 is from diffutils 2.8.1 and I wouldn't call that "maintained", but you already know that. It is obviously not a replacement for diff, did you ever read the manpages? And wow, a KDE program prefers to use another KDE program!
[killed quite a bit]Diff has apparently been broken for maybe 5 years and THAT wouldn't have gone unnoticed - am I one of the VERY few to even try to use kompare? What do the rest of you use?
Again, diff is fine and I'm using kompare (or kdiff3?) almost daily, in krusader.
(a) kompare isn't really set up for binary files; it's intended for use with text files. You can specify an option to force a text-mode search, but you apparently canNOT do the reverse.
(b) It err'ed out comparing two M$ 'Word' files, stating they "were binary"...
Genius. Comparing binary files is useless. If you used MS Office you're hosed, that simple. More useful advice at the end.
Anyone have any suggestions on doing this task efficiently and reliably in Arch?
Yep.
Again, I believe this to be an upstream problem in a way, but my guess is that if we were using the *current* diffutils to match the KDE version (and a maintainer had done his job in a timely fashion) this bug would NOT exist. My advice, at least until Arch can get diff3 (or, preferably, kdiff3) packaged, STAY AWAY FROM kompare !!! At least with anything critical, at least until this issue is better understood.
Upstream, right... diffutils have nothing to do with KDE at all... Arch has diff3 and kdiff3 packaged ... it's no 'issue' at all.
Okay, I apologize for that 'tone' of mine but I get pissed easily when wasting so much time on something as this.
I know your problem very well as I'm constantly backing up stuff, comparing directories and hunting duplicates.
After unpacking everything the first step to take is to run a comprehensive check for binary duplicates. My tool of choice for that task is Total Commander (Win32 shareware, no timeout, just a minor nag screen on start, works fine with Wine). Just a few random keyboard shortcuts you might find handy (see the help file for explanations): ctrl-b, ctrl-f1(-f6), ctrl-c,y, alt-f7
After killing them, go on to compare ("synchronize") similar directories, either with Total Commander, Krusader, rsync, diff -R, whatever.
If you encounter similar named files, check the dates and kill the older ones, or compare them if they're not binary.
And so on... you know best what kind of data you got and how to split it up.
Throwing plain diff on a set of thousands of files, possibly gigabytes is a huge waste of time and computing/power resources. Adding a frontend will make it crash most of the time, especially with binary files. I think using kdiff3 to compare the Arch Linux 0.8 base beta1 iso to the beta2 one alone should suffice. A few more gigabytes of RAM might help though.

Still getting KP after replacing gfx card & having Genius Bar tests...

I've been getting kernel panics when waking the computer from sleep since 10.5.5 and rampantly since 10.5.6. Soon after my nVidia 6800 started displaying artifacts and would not boot unless under safe mode (in Leopard) or by removing the GeForce extensions all together (in Tiger).
I took it into an Apple store and the Genius desk pop in a new card and it booted fine so obviously that's the problem. Before I made a decision on replacing the card I wanted them to their thorough hardware check to make sure it was only the card and it came back clean.
Since Apple wanted $440 for a refurbished 6800 (that couldn't be found for a couple weeks) I got one off eBay for $300. Pop it in, looks good, reinstall Leopard, upgrade to 10.5.6 and start restoring my backups.
Everything was going fine until I put the computer to sleep last night and the next morning, once again, it fails to wake from sleep. Computer "breaths" to life, but the display is dark. Hard shutdown and I get my familiar kernel panics (this is copied from an old post of mine):
Unresolved kernel trap(cpu 0): 0x300 - Data access DAR=0x0000000000000020 PC=0x0000000000A4F4E0
Latest crash info for cpu 0:
Exception state (sv=0x60aba500)
PC=0x00A4F4E0; MSR=0x0000B030; DAR=0x00000020; DSISR=0x40000000; LR=0x00A4F4E0; R1=0x606E79E0; XCP=0x0000000C (0x300 - Data access)
Backtrace:
0x00A4F4E0 0x00A50034 0x00A55894 0x00A85DAC 0x00A33CF4 0x00376778
0x0037C1E0 0x0037C330 0x0008F804 0x0002C1C8 0x00024C94 0x000B2E4C 0x00008208
backtrace terminated - frame not mapped or invalid: 0xBFFF69F0
Kernel loadable modules in backtrace (with dependencies):
com.apple.GeForce(5.3.0)@0xa16000->0xab0fff
dependency: com.apple.NVDAResman(5.3.0)@0x795000
dependency: com.apple.iokit.IONDRVSupport(1.5.2)@0x77d000
dependency: com.apple.iokit.IOPCIFamily(2.4.1)@0x632000
dependency: com.apple.iokit.IOGraphicsFamily(1.5.2)@0x757000
Proceeding back via exception chain:
Exception state (sv=0x60aba500)
previously dumped as "Latest" state. skipping...
Exception state (sv=0x60aab780)
PC=0x906CF438; MSR=0x0200F030; DAR=0x5292F000; DSISR=0x42000000; LR=0x906D6360; R1=0xBFFF69F0; XCP=0x00000030 (0xC00 - System call)
BSD process name corresponding to current thread: WindowServer
Mac OS version:
9F33
Kernel version:
Darwin Kernel Version 9.5.0: Wed Sep 3 11:31:44 PDT 2008; root:xnu-1228.7.58~1/RELEASE_PPC
System model name: PowerMac7,3
panic(cpu 0 caller 0xFFFF0003): 0x300 - Data access
Latest stack backtrace for cpu 0:
Backtrace:
0x0009B518 0x0009BEBC 0x00029DD8 0x000AF290 0x000B2AF8
Proceeding back via exception chain:
Exception state (sv=0x60aba500)
PC=0x00A4F4E0; MSR=0x0000B030; DAR=0x00000020; DSISR=0x40000000; LR=0x00A4F4E0; R1=0x606E79E0; XCP=0x0000000C (0x300 - Data access)
Backtrace:
0x00A4F4E0 0x00A50034 0x00A55894 0x00A85DAC 0x00A33CF4 0x00376778
0x0037C1E0 0x0037C330 0x0008F804 0x0002C1C8 0x00024C94 0x000B2E4C 0x00008208
backtrace terminated - frame not mapped or invalid: 0xBFFF69F0
Kernel loadable modules in backtrace (with dependencies):
com.apple.GeForce(5.3.0)@0xa16000->0xab0fff
dependency: com.apple.NVDAResman(5.3.0)@0x795000
dependency: com.apple.iokit.IONDRVSupport(1.5.2)@0x77d000
After sending an obviously frustrated report to Apple I don't know where to go from here. I was dealing with a woman at Apple's customer satisfaction center. When she gets back to me to check in I'm going to relay this news to her. My initial feelings were this was a bug between Leopard and G5 hardware as others were experiencing it.
<Edited by Moderator>

Here is the actual log from the crash.
Tue Jan 13 05:58:33 2009
Unresolved kernel trap(cpu 1): 0x300 - Data access DAR=0x00000000B3780018 PC=0x0000000074044BA8
Latest crash info for cpu 1:
Exception state (sv=0x63654c80)
PC=0x74044BA8; MSR=0x00009030; DAR=0xB3780018; DSISR=0x00200000; LR=0x740446C4; R1=0x63673200; XCP=0x0000000C (0x300 - Data access)
Backtrace:
0x740446C4 0x73EA2C68 0x73E9D69C 0x73EA00B4 0x7407FE7C 0x74084ED4
0x73DD7E4C 0x73DC11AC 0x73DB1344 0x73FC8284 0x73FB99B8 0x73FB7570 0x73DA9928 0x6385C158
0x6385C510 0x6397A14C 0x6385C4E4 0x6397BA20 0x6397BC64 0x0003F9BC 0x000B0E54
Kernel loadable modules in backtrace (with dependencies):
com.apple.nvidia.nv40halppc(5.3.6)@0x74029000->0x7420efff
dependency: com.apple.iokit.IOPCIFamily(2.5)@0x5b2f5000
dependency: com.apple.NVDAResmanPPC(5.3.6)@0x73da8000
com.apple.NVDAResmanPPC(5.3.6)@0x73da8000->0x74028fff
dependency: com.apple.iokit.IONDRVSupport(1.7.1)@0x6384f000
dependency: com.apple.iokit.IOPCIFamily(2.5)@0x5b2f5000
dependency: com.apple.iokit.IOGraphicsFamily(1.7.1)@0x63962000
com.apple.iokit.IONDRVSupport(1.7.1)@0x6384f000->0x63866fff
dependency: com.apple.iokit.IOGraphicsFamily(1.7.1)@0x63962000
dependency: com.apple.iokit.IOPCIFamily(2.5)@0x5b2f5000
com.apple.iokit.IOGraphicsFamily(1.7.1)@0x63962000->0x63987fff
dependency: com.apple.iokit.IOPCIFamily(2.5)@0x5b2f5000
Proceeding back via exception chain:
Exception state (sv=0x63654c80)
previously dumped as "Latest" state. skipping...
Exception state (sv=0x63d01280)
PC=0x00000000; MSR=0x0000D030; DAR=0x00000000; DSISR=0x00000000; LR=0x00000000; R1=0x00000000; XCP=0x00000000 (Unknown)
BSD process name corresponding to current thread: kernel_task
Mac OS version:
9G55
Kernel version:
Darwin Kernel Version 9.6.0: Mon Nov 24 17:39:01 PST 2008; root:xnu-1228.9.59~1/RELEASE_PPC
System model name: PowerMac7,3
panic(cpu 1 caller 0xFFFF0003): 0x300 - Data access
Latest stack backtrace for cpu 1:
Backtrace:
0x0009BCF0 0x0009C694 0x00029EA0 0x000AFA90 0x000B32F8
Proceeding back via exception chain:
Exception state (sv=0x63654c80)
PC=0x74044BA8; MSR=0x00009030; DAR=0xB3780018; DSISR=0x00200000; LR=0x740446C4; R1=0x63673200; XCP=0x0000000@

I've been using my Air since Sept. 19th, but I seem to have some bugs...

But it SEEMS a little buggy to me—OS X itself; especially in comparison to Windows (please don't start a debate—I'm pro-Mac here, I much prefer it, please believe that. You'll see when you read further ahead). I adore the computer more than any I've ever used, since updating to Mavericks my battery lasts 16 hours long which is just UNBELIEVABLE. Yet then there are the annoyances that don't happen with Windows...
Safari really bugs up a lot. So do a few other of the apps. Yeah, Apple has apps that actually work, whereas most of Windows stuff is bloatware; but I do get bugs with Gmail on Mail, Safari slowing down and having other graphical problems where the bottom or top of the browser won't show completely, all of the wi-fi problems, and now with Mavericks there are more. The biggest one is Spotlight failing. Others, SOME fixed [partially] with workarounds, are the rainbow cursor showing up all the time on Safari causing force restarts [partially fixed; still have to force start sometimes but no more rainbow-freezing, just unable to two-finger scroll], Safari Web Content taking up 30-100% CPU [fixed with workaround and fixed completely since Mavericks], and the computer itself is, while charging (or plugged in via USB; haven't checked the other ways), actually seemingly giving off some type of static vibration.
I LOVE Spotlight and it not opening kills me. I didn't do a fresh install with Mavericks so I'm unsure what would've changed. I did the update it offered me from my computer.
I'm really new to Macs, having only received my very first on the 19th of September, but I just adore it. The trackpad is literally the best thing ever invented... ever. Coming from using an iPad for a couple hundred days without using a computer at all, the change to using the trackpad gestures and the OS X ecosystem was very, very easy for me. I'm truly amazed at how similar OS X is to iOS. How the heck did they manage that?
Anyway, realistically, the best bet is to change to Chrome or a different browser that may mess up and cause less bugs and memory leaks (or whatever it is that Safari was doing), but I actually like Safari and how it links up with my iPhone and iPad.
Mainly what I'm asking here is are you guys having these problems? Also, should I stick with Safari? Is there another way to use iCloud with a different browser? Everything I have is Apple, so it's just nice having that one nice, central, similar ecosystem, without annoying and time-consuming workarounds. I love how Apple is natively configured to work with SO much (it's notification center is absolutely amazing. I think it's so cool)
Should I really go into one of those "get to know your Mac" sessions at the Genius Bar? I'm not a computer moron entirely.
P.S. iTunes doesn't like to play iTunes Radio. It'll stop playing and just "load" a song continually. I'll have to skip the song for it to restart playing and eventually I'll have to use all the skips for my hour and then I'll have to switch to a new station and back to get it to start playing again. I actually use iTunes Radio for a good 14-15+ hours a day (I don't sleep very much) on the Air, so this gets rather annoying. I can't recall whether or not it does this on my iPhone, which I also always use whenever I go out the door.
Needless to say, I'm never going back to Windows; but are any of you having these same—the whole plethora of—problems that I am? It's certainly, hilariously, not enough to send me back to Windows, but... I'd prefer as "close to perfect" an experience as possible. Is this it? Thank you!
<Edited by Host>

Can you get an internet connection if you connect directly to the modem?

Drag and drop file to desktop bug

I have a new fusion drive 27" iMac with Thunderbolt Cinema Display.
When I drag a file, like an attachment from mail, onto the desktop it does not drop the file where the cursor indicates it will.
The same thing when dragging from the download folder or a finder window.
The file is randomly paced on the main iMac desktop in no particluar order, and you can't precisely drop a file where you want.
File can be dropped behind open windows, making them hard to find.
If the Thunderbolt display is unplugged, the issue goes away and drag and drop is precise.
This used to happen on my old iMac aswell, but i put it down to a bug with my system, however, it also happened out-of-the-box on the new fusion iMac before I installed any software or files, as I was specifically testing this - it's very annoying and disruptive to workflow.
Something with OSX doesn't like the external monitor when it comes to drag and drop to desktop.

The card reader is apparently stuck in write-locked mode. I don't generally advise do-it-yourself hardware repair, but one ASC poster managed to fix this problem. I haven't tried the fix myself and I can't offer any guidance beyond what's in that discussion. If you cause damage, don't expect your warranty to cover it. I suggest you instead make a "Genius" appointment at an Apple Store.

Bug in Genius

Similar Messages

Maybe you are looking for