XGL causes corrupted images

I'm working on trying to get XGL working, and I followed the wiki. However, when i boot up (either method one or two), everything gets corrupted and slanty. Except for the terminal area of a konsole i happened to have open. X sort of runs (slowly, and crashes after a little bit).
I have a thinkpad t60p with ati Mobility FireGL V 5250, and am using fglrx version 8.40.something (i tried 8.41, but X would refuse to start) and kernel version 2.6.23.
EDIT: I just noticed a line about startxgl.
This, however, does not work either. I try running startxgl 0 kde ati, and it attempts to start gnome-session.
Last edited by likpok (2007-10-23 04:52:30)

Similar Messages

Content Aware tool causing corrupt images

As the title states, I went to use my content aware tool to expand a rather simple background texture and it went completely haywire!
This is what it gave me! I tried to undo it, thinking it had grabbed from all the layers, but going back in the history didn't fix it. So I closed the file (I didn't save it like this) and reopened it only to see the same thing! This was a project for a client so I was more than a little angry that some how the tool had corrupted my entire file and then saved it without me knowing! So I took this screenshot, only to try and open up a New Document and have it too look corrupted. At this point, I closed photoshop completely, making sure any services that started up with it was shut down as well and restarted it and opened my TIF file to find it perfectly fine.
Again I tried to use the Content Aware tool (with all my layers shut off, minus the one I needed extended) to only have it do the same thing to all the layers again!
Needless to say I closed photoshop, made sure my video drivers were up to date and reopened, pasted my screenshot and came here. So the obvious thing is, is that my Content Aware tool is causing a problem, but what in the world is going on? How do I fix this?

Yes; it will always depend on the individual image.
Don't expect miracles. The feature is OK but—despite all the hype—is not ground-breaking, in my opinion. It has been available for quite some time in Alien Skin's Image Doctor set of plug-ins and in the GIMP (this latter one free) in ways I find a bit better.
Wo Tai Lao Le
我太老了

Corrupt image files cause upgraded iPhoto to crash

I have been spending some time trying to find and remove corrupt image files from my iPhoto library. These are not just scrambled images when viewed they crash any and every program you view them with. Including Finder. I accidentally put one on my desktop and finder went into a auto restart cycle I could not stop. until I removed the file with pathfinder. I have found about 30 of these so far (my library is about 25,000) Many of these are in the data file but some are not. They are of all types (jpg,tiff,psd) Thorsten Lemke, (Lemke Software) tells me it is a quicktime issue.
Here is a link to one of these files. Warning it will crash safari if you try o view it.
http://vincentdavis.net/try/try.jpg
Here are my questions.
1. is there some way to fix these
2. is there some efficient way to find and remove/fix them?
3. how did this happen? I had no problem before update (that I knew of)
Thanks
Vincent

I did try the link, and as you said - it crashed Safari. However, I have google searched and also searched the Apple Support sites for 'fix corrupt images' with no luck. I'm sorry but I think the only way of knowing is to try and open each of them.
However, I did read on Macworld's site once that sometimes photoshop or other image editing programs can open the corrupt files.
Sorry for not being much help here - I hoped that my first suggestion would have done the trick.
Sam

Corrupted images captured by new 5D Mark III

Hi,
I got two corrupted images while shooting with my new 5D Mark III..I was using 45mbps sandisk extreme SD card and the mode was only JPEG(fine). After getting two corrupted images I shoot 1k images but no problem there after..Later I copied those images in my HDD except two corrupted images all are looked nice.. My y question is what was the actual problem?Thank you in advance..
Solved!
Go to Solution.

I'd advise at least doing a quick in-camera format each time you insert a memory card (or right after downloading, if you use the USB cable to transfer your images).
The in-camera format preps the memory card for use, configuring it with some needed file structures and writing over old files.
If you ever format in computer, always re-format it in your camera before shooting. It's possible that the computer won't configure the card in a way that will work properly in the camera.
Usually corrupt images are due to card issue or connectivity when downloading. If you are seeing the corruption in the camera, then I'd first suspect the card (either it's faulty, or it's configured incorrectly, or something on there is causing a conflict).
I once corrupted a number of images on a Compact Flash by opening the memory card door and pulling the card out too quickly, while the last image or two were still being written. It corrupted about 1/3 of the images on the card, not just the last one taken. Initially all the images on the card were unreadable, until I ran a recovery program. That was able to repair about 2/3 of the images... roughly 200 out of 300 images, if I recall correctly.
The worst corruption issue I've had (in ten years shooting digital almost exclusively, nearly 20 years shooting some digital), was due to connectivity issues. I had a card reader connected to a USB hub. Took it off the hub and connected it directly to the computer's USB port and the problem was solved.
It's possible, but pretty rare that the camera itself causes occasional corrupt files. Usually if the camera starts throwing off corrupted files, it's most or all images... not just an occasional one. I'd keep an eye on it and if it continues happening, try a different memory card first. If it continues to happen with a different card, have the camera looked at.
Alan Myers
San Jose, Calif., USA
"Walk softly and carry a big lens."
GEAR: 5DII, 7D(x2), 50D(x3), some other cameras, various lenses & accessories
FLICKR & PRINTROOM

Any new fixes for corrupt images in Lightroom 4.4?

I have seen many threads on this and tried a lot of the tings people say to try. But I do get corrupt images in Lightroom. I currently have an AMD FX-8150, 32GB ram, 2 SSD Raid0 + USB3.0 drives as backup.
Drive and Memory:
Note, I only keep up to the last 3 shoots on my SSD, the rest are stored on my USB3 drives. Any time I import files to the USB drive I get no corruption. Now that would imply that I have bad drives, I have run diskcheck and contacted Muskin and they had me run some disk checks, speed tests, +other things and identified that the drives are running fine with no issues and this has to be a software issue.
I have run memtest86+ with no errors, also ran memtest86+ with my memory in another machine with no errors.
To rule out the card reader:
When I just copy files from my CF Card to a folder using explorer all images import fine and you can even open every image in photoshop with no issues. As soon as you add those files already copied to the HD to lightroom, they start to corrupt. I just recently used the windows explorer method and added ~400 images to lightroom, all images imported fine, when I later accessed lightroom(Today), about 10% of those images are not corrupt.
Does anyone have any suggestions? Could it be because I use Raid0? Or even SSD drives?
This is quite annoying and I would like to get things fixed.

jproductions111 wrote:
Usually when Lr renames the photos as you saw kianjillwedding-19, Lr changed the name from IMG_1968. Thats may have something to do with the corruption.
I don't see how. Renaming shouldn't change anything on disk except, well, the name - and of course update a bunch of things in the catalog.
jproductions111 wrote:
I will get back to you if the problem continues but everything still seems to be fine in Lr5, even after letting Lr rename all the photos with my current(today's) import of 700 images.
OK - thanks.
jproductions111 wrote:
I know you don't believe its software
~impossible it's Lr4 software. Theoretically possible, but highly unlikely. As I said, Lr4 should never be rewriting those files, and therefore essentially can not corrupt them. I mean, its possible that it got it's brains scrambled, and went ahead and rewrote them, for god-knows why or just for the he|| of it - because some bits seemed to be set wrong..., thus invalidating the assumption that it's not rewriting them. It's just that this scenario is the least likely. I mean, Jeff Schewe has given me spankings more than once before, for even bringing it up, since it's so unlikely...
jproductions111 wrote:
maybe Lr 4 was causing some sort of bug to make the hardware malfunction
Although theoretically possible, I'd still venture to guess that's not what happened.
jproductions111 wrote:
this is not happening to my in Lr5.
Didn't you also change your disk drive situation around just before you started using Lr5?
jproductions111 wrote:
But I am keeping my fingers crossed.
Me too - please keep us posted...
R

Hdiutil: verify failed - corrupt image

problem: sparseimage is not mountable and verify ends with a "hdiutil: verify failed - corrupt image".
cause: tiger crashed and the image was mounted. the only way to boot was power down the machine. after the reboot the image was not mountable anymore.
thats the verbose output:
hdiutil verify -verbose conti.sparseimage
hdiutil: verify: processing "conti.sparseimage"
DIBackingStoreInstantiatorProbe: interface 0, score 100, CBSDBackingStore
DIBackingStoreInstantiatorProbe: interface 1, score -1000, CRAMBackingStore
DIBackingStoreInstantiatorProbe: interface 2, score 100, CCarbonBackingStore
DIBackingStoreInstantiatorProbe: interface 3, score -1000, CDevBackingStore
DIBackingStoreInstantiatorProbe: interface 4, score -1000, CCURLBackingStore
DIBackingStoreInstantiatorProbe: interface 5, score -1000, CVectoredBackingStore
DIBackingStoreInstantiatorProbe: selecting CBSDBackingStore
DIFileEncodingInstantiatorProbe: interface 0, score -1000, CMacBinaryEncoding
DIFileEncodingInstantiatorProbe: interface 1, score -1000, CAppleSingleEncoding
DIFileEncodingInstantiatorProbe: interface 2, score -1000, CEncryptedEncoding
DIFileEncodingInstantiatorProbe: nothing to select.
DIFileEncodingInstantiatorProbe: interface 0, score -1000, CUDIFEncoding
DIFileEncodingInstantiatorProbe: nothing to select.
DIFileEncodingInstantiatorProbe: interface 0, score -1000, CSegmentedNDIFEncoding
DIFileEncodingInstantiatorProbe: interface 1, score -1000, CSegmentedUDIFEncoding
DIFileEncodingInstantiatorProbe: interface 2, score -1000, CSegmentedUDIFRawEncoding
DIFileEncodingInstantiatorProbe: nothing to select.
DIDiskImageInstantiatorProbe: interface 0, score 0, CDARTDiskImage
DIDiskImageInstantiatorProbe: interface 1, score 0, CDiskCopy42DiskImage
DIDiskImageInstantiatorProbe: interface 2, score -1000, CNDIFDiskImage
DIDiskImageInstantiatorProbe: interface 3, score -1000, CUDIFDiskImage
DIDiskImageInstantiatorProbe: interface 5, score -100, CRawDiskImage
DIDiskImageInstantiatorProbe: interface 6, score -100, CShadowedDiskImage
DIDiskImageInstantiatorProbe: interface 7, score 1000, CSparseDiskImage
DIDiskImageInstantiatorProbe: interface 8, score -1000, CCFPlugInDiskImage
DIDiskImageInstantiatorProbe: interface 9, score -100, CWrappedDiskImage
DIDiskImageInstantiatorProbe: selecting CSparseDiskImage
DIDiskImageNewWithBackingStore: CSparseDiskImage
DIDiskImageNewWithBackingStore: instantiator returned 103
hdiutil: verify: unable to recognize "conti.sparseimage" as a disk image. (corrupt image)
hdiutil: verify: result: 103
hdiutil: verify failed - corrupt image
the problem is not that i dont have a backup of tha date within this 7GIG imagefile. the problem is now that i dont trust this format anymore. i do have a couple of AES-secured sparesimages FOR backup-reason (including one on my iPod) and if something happens to them i might be in serious trouble.
so now my question: is it possible to rescue this AES-secured spareseimage or is this kind of methos unsafe for important data?
thanks
klaus

Regular tools like Disk Utility and DiskWarrior
didn't solve anything. I was wondering if it is
possible to rescue some files by manually decrypting
the image with some low-level tool.
Did you have any succes? Given all reports on the
web, it seems a bit hopeless, but I like to give it a
chance.
no success at all, sorry.
i dumped the images now and also went back to some backups.
but i definitly don't use filevault anymore
cu

CS3 corrupting images

I am using CS3 in OS X 10.5. All of a sudden my photos are getting corrupted. I can see an image in Bridge, but when I click on it the image becomes completely distorted. It becomes colorful horizontal lines. I tried removing CS3 and re-installing it, and the corrupted images looked ok after this, but again when I clicked on them, they would get distorted again. I have no idea what's causing this, but I'm hoping someone can tell me, so I know how to fix it and avoid it in the future.
Thank you!
Tom

Thanks for the reply Chris! That was one of my guesses. I ran disk repair on the drive and it didn't come up with any errors, is there a test for the RAM? I've called Apple before with photoshop issues and they've said they can't really help with 3rd party apps, but this is a fairly new iMac. I will be sure apple care is extended for it and work with them. In the meantime, I deleted all the files that seemed to be having issues and will watch to see if any others have problems, but it seems to be limited to one folder so far.
Thanks,
Tom

Corrupted image shown when horizontal elasticity set to "contract"

Hello.
Using Forms and Reports 10.1.2.3.0
I have a report where I try to show images horizontally centered in their surrounding frame.
For this I created an image-item inside the frame (a repeating-frame, because the images are fetched from the DB), manually centered it inside the frame, attached it with an anchor to its surrounding frame, and set its horizontal elasticity to "contract" (vertical elasticity is set to "fixed"). This is actually the preferred method for doing this and a few threads in this forum recommend it.
What I got in the resulting PDF was a corrupted image under certain circumstances.
To narrow this down I created three different images (width*height)
1. 1000*666
2. 1000*750
3. 1000*800
loaded them into the DB, and tried to run the PDF. You can see the result in the following screenshot:
When I set the horizontal elasticity to "fixed", the image is not corrupted (this is not a solution since the image gets left-aligned then).
Setting the OUTPUTIMAGEFORMAT to something different than the default (JPEG) didn't change anything.
Interestingly enough the Foxit PDF-Reader shows it correctly, while both AdobeReader X and XI and even Inkscape show the image corrupted (not only on my PC).
We tried this with several images/photos, and the only ones being shown correctly seem to be images with an aspect-ratio of 4:3 or higher. I was not able to pinpoint exactly at which ratio this behaviour manifests itself.
Anyone got an idea what may have caused this?
Thanks in advance
Markus

Addendum:
Setting the vertical elasticity to "expand" fixes it too, but since we often have images with an aspect-ratio of 3:4 or even higher I can't use this, since they would use way too much vertical space (and would negatively impact our layout).

Corrupted image files in Lightroom?

I opened up Lightroom this morning and noticed that some of my files from a recent shoot look like this:
Are they corrupted?
If so, how does that happen? I've never seen this before and I have thousands of images in LR.

Thanks. I read through a few of the other threads. I found one comment that might be applicable to my situation:
Good - most often this tell-tale/signature-looking corruption is due to hardware - transfer hardware if corrupt upon first rendering (true raw rendering, not initial preview display), hard disk if corrupt after first rendering. And sometimes ram.
I think this may have had something to do with how I got these files onto my computer. I shot the pictures while visiting family. I had my Macbook Pro with me, which is not my main image editing machine. I imported the files into LR4 on the MPB from the 5D3 using the USB cable.
When I returned home, I moved the files from their location on the MBP to a USB flash drive, and then imported them from the flash drive to LR4 on my Mac Pro (which is my main image editing machine).
The corrupted images are only from this group. So I'm hoping that it was the transfer to and from the flash drive that caused this, especially since I've never experienced it before and don't see it in any of my other images.
Fingers crossed!

Aperture corrupting images during editing

Hello,
Starting a few days ago, aperture started corrupting images during editing. This was normally at the time of my fist cut, going through doing simple straighten and croping. Sometimes it would happen when doing a small lighten or darken of the exposure. I purchased a new MacBook Pro about a month ago but this only started happening this week. No OS or Aperture upgrades this week. I did have a crash earlier this week and after the crash my Spotlight re-indexed my computer. I updated QuickSilver this week and Awaken. I tried quiting both QS and Awaken but problem still happens. The real scary thing is I usally have to go back and re-import the raw CR2 image to fix the problem, doing an update from master or resetting all adjustments does not fix the problem. Below is an example of an image with the problem. This is a Version Export of a corrupted image, as you can see the cor Can I get any help?

Ernie Stamper:
The Aperture Libraries are on the local drive. I do have an external Firewire drive I can use to test your theory but since I recently replaced the whole laptop at the Apple store so I am thinking it is not hardware related but one of three things: an Aperture bug, my configuration, or memory (see more on memory below).
leonieDF:
I don't think it is related to a hardware issue unless it is memory. I took the laptop into the mac store because I was having a hardware issue not discussed in this thread. The laptop was completely replaced except for the memory since I purchased 8GB of memory after the computer was purchased. I put the 8GB memory back into the new laptop. If this is a memory problem it is not showing up in diagnostics. I am planning on doing two things this weekend. First thing is putting back in the original apply memory and testing. If I still get the issue I am going to do a complete uninstall of Aperture and re-install maybe something in my settings/libaries are corrupted. I am reaching for straws at this point. I might also try a complete reformat and only install Aperture and test to see if something else installed might be causing this, but I can't think of what it would be.

Performing any adjustments in Aperture corrupts image/viewer..HELP

I did an update on my mac today and Aperture was one of the programs receiving an update. This update brought me to 2.1.2.
Since the update I'm unable to perform any kind of "adjustments" on my photos. Moving any slider or making ANY change causes the image to go strait to black, or the image "breaks" and just turns into garbled noise. A quick "undo" with bring the photo back, but of course I lose any changes I just made.
Please, can someone help? I haven't had this problem at all until I did the update earlier. Very weird.
Here's my specs...
MacBook Pro
Intel Core 2 Duo, 2.4 GHz
4GB Memory
GeForce 8600M GT
Message was edited by: ericwebb

Eric
try trashing the preferences, could be that in the update process something has corrupted.
users/user/library/preferences/com.apple.Aperture.plist
Tony

6233: Corrupted images

Hello,
I have Nokia 6233 v5.10 with 1GB Lexar microSD card. I've noticed that some of the images I've taken(and maybe this applies to all kinds of files) get corrupted after some time(it's not in the moment of shooting but at a later time). What's causing the problem and what's the solution?
Here's one corrupted image from the phone:
http://img512.imageshack.us/img512/719/corruptedmt0.jpg

It is always advisable to keep your phone's firmware up to date. Click here to see whether a software/ firmware update is available for your Nokia device.
Mobile Royale - Latest News, Reviews and Software for Mobiles
Aero Everyday - Aviation News and Insights
GoMobile Forums-The best mobile technology discussions
Please visit http://alifeofmisery.blogspot.com or www.miserylife.tk and help someone smile.
Dreaming of a 5320XpressMusic - 128MB RAM makes up for the 2MP cam !

Corrupted image(s)

Hello,
Hello, Since upgrading to 1.4.1 I have noticed that on rare occasion a corrupted image. So to test, I recently manually down loaded a photo shoot to my hard drive and inspected the images (Canon 5D cr2 RAW) with Canon DPP (in the mode equivalent to LR develop). All the images were fine. They were then imported in LR. All the images were viewed in the library module and all looked fine. Then the images were examined in the develop module which when I noticed a corrupted image. The corruption takes the form of where a portion of the image contains rectangle with one color channel missing. That is about the best I can describe it.
As further testing, I examined the corrupted image with DPP again. DPP now reports the image is corrupted which it did not before. I believe this is NOT file system corruption as is appears that windows is not reporting a file system problem to the applications.

I thought they would have fixed this. This is an ongoing issue from the early days of LR2 (maybe before). In my case, I had imported several hundred images without knowing that the D80 had a bad SD card. About 40% of the images were corrupted.. but they looked fine on the back of the camera because the imbedded JPEG (I shoot RAW) was fine. Lightroom on the other hand crashed every single time I tried to load the catalog and it hit one of these images. I ended spending hours going in and manually deleting the offending images. I would load the catalog and note the file name of the image that caused it to crash. I would then go to the folder and delete it and try again. I also make a bit copy of the SD card so if something went really wrong, I could work on a new set of files.
Also, I dont know if you have a friend with a Mac, but a tool called "Filejuicer" can pull the embedded JPEGs out of the RAW file even when it's corrupted. I was able to recover almost 100% of the bad files this way. I did give up alot of adjustment in post but at least I had something to work with.

When I submitted my iPhoto book to Apple, an error caused the image file to be unreadable or unprintable,why can anyone help me please

when I submitted my iPhoto book to Apple, an error caused the image file to be unreadable or unprintable,why can anyone help me please:)
what I did with my system was following:
1. Update your software.
2. Restart your computer.
3. Make sure all applications are closed.
4. Open iPhoto or Aperture.
5. While all other applications are closed, preview your print product as a
PDF.
6. Resubmit your order.
and still my PDF ibook file looked like my photos were scratched across the photos. Please help:)
Thank you
CJ

Yes me too!!
I thought that I had done someting wrong. The first time it was my first attempt so I did not preview the photobok (did not know this trick). When I did the cover photos were completely ruined with lines and code.
The second time I changed everything and even made a different sized book - thinking my photo files were too big. I dutifully previewed before buying the book and everything was fine. Then a few days later got the usual e-mail message from Apple. When I previewed the project again ALL of the photos were corrupted.
What to do - I need to get the photobook to friends to celebrate their engagement!
If I saved the pdf then submitted this would that work??
Any thoughts - I am working on a large project and do not want to go any further if all the work will be ruined on buying the book.

Frustration - Iphoto corrupting image files during import (?)

To begin with, I'm a recent convert from Windows to the Mac. I'm running a mac mini at home, and a Macbook with Boot Camp at work (in addition to my desktop pc). All of my software is up to date...
I take alot of pictures with my digital camera (canon powershot). Saturday I took about 300 pictures, took the SD card out of the camera, put it into my Sandisk card reader, imported the pictures into iphoto and everything worked great. I chose to not delete the pictures after the import as I wanted to bring the card into work and upload the pictures on my pc.
The next day (Sunday) I took another 70 or so pictures. I was able to view all of the pictures on my camera that I had taken over the past two days.
I go to do an import , taking the exact same procedures that I took on Saturday (and that I always do). The first thing it does is identifies that there are duplicate pictures. I choose the option of "don't import duplicates" and apply this to all of the other duplicate pictures.
At the end of the import, I got an error message saying that some of the files were corrupt. Now, there were pictures from Saturday that were still on there (and readable/viewable). However, every picture that I took on Sunday was "unreadable" and did not show up in iphoto. I put the card back into the camera, and now I can't view the pictures (they show as "corrupted data".
I then pulled the SD card details up in Finder, and the "corrupt" files still show sizes of 2.4mb to 2.8mb, consistant with the good pictures. It shows the file's "Kind" as JPG Image... I double clicked on them and Preview comes up saying something to the extent that the file is corrupt,
I've taken the Sandisk card reader, plugged it into my Macbook (using iphoto in osx) and was able to view one or two of the pictures from Sunday.
Once I got to work this morning, I plugged the sd card into my Windows machine and it too says the files are corrupt. It shows them being on the card, it shows the file sizes, but I can't open the pictures in anything...
If this was a one time deal, I'd be thinking it may be something I've done to cause the problem. However, this is the third instance I've "lost" all of my photos because of them becoming corrupt during an import into iphoto. There definately appears to be a pattern.
I have somewhere around 8,000 pictures inside iphoto that I've taken and had no problems with. I mention this to illustrate that I'm not doing anything differently than I've done before. I have another 14,000 on my old Dell that I need to move over, but I'm questioning if I should do that now.
Does anyone have any ideas on what the problem might be? Is anyone else experiencing (present or past tense) this problem? Where I'm new to the mac, I understand that I might be doing something wrong. However, I've imported photos to the software (what seems like) hundreds of times, the same way each time. This makes me want to rule out user error...
One other question, I'm saving the "corrupt files" with the hope that there's a software program which will "fix" the files. Do you happen to know of such a piece of software? I'm hoping that I can get them fixed at some point.
Where I'm taking pictures of my kids, its extremely frustrating to find out that the pictures (memories) I was hoping to make prints of are now "gone". Its almost like rolling the dice when doing a photo import any more. Most all of the time it takes, but every now and then the pics are lost...
I'm hoping to identify the problem (either user error, procedure or software issue) and fix it as I really like the mac.
Any help/suggestions you might have for me would greatly be appreciated!
Mac Mini Mac OS X (10.4.10) Also running Macbook 10.4.10

The Chainsaw
Welcome to the Apple Discussions.
First: the corrupt files: download Graphic Coverter, a shareware which is often successful where other software isn't. But first, if the Mac will let you, copy the files off the card to the Mac.
I'm in this board a while now, and I can't recall an issue of iPhoto corrupting images on import. After all, it's just a simple file copy, at heart. I would be more inclined to suspect the card. DO you have more than one? Does the problem also occur with the other cards?
Try use Image Capture to download the pics to the Mac first, then import them, see does that help. Image Capture is in your Applications folder.
Regards
TD

XGL causes corrupted images

Similar Messages

Maybe you are looking for