Stalker Lost Alpha Upgrade Data

[Vennie Fireman]

Imounted a new hard disk drive in my Linux workstation. It looks like it is working well. I want to download some repository in the new disk. So I execute git clone XXX, and it works well. But when I cd in the folder, and execute git submodule update --init --recursive. It failed with

I thought maybe it's just a slight warning, so I just executed git config --global --add safe.directory /media/data/users/jhu3szh/serialize. However, when I execute the Git submodule again, more similar errors came out. There are many submodules in the repository.

1 - If this fails in your particular terminal program in Windows, try surrounding the wildcard with double quotes instead of single (Via this GitHub issue):git config --global --add safe.directory "*"

Make sure you are using the correct terminal user. For me, I had temporarily changed to the root user which would have caused issues. I changed back to the standard user with su git-user and the error went away.

It seems that two folders are being checked by Git: the .git folder and the folder containing it. Both must be owned by the current user. The other folders and files of the folder containing the .git folder can be owned by other users if there is a need. Therefore

Ensure that if you do change the owner of the folder containing the .git folder that permissions are still setup to work as you prefer, i.e. whether the previous owner retains the same read, write and execute permissions with the current group and everyone permissions. If they have lost permissions, either consider adjusting the group or other or revert the folder ownership change and use the git config --global --add safe.directory path/to/repository solution instead.

When the error "fatal: detected dubious ownership in repository" is returned from a command no directly executed by you but it is executed by some other program ie: PHP exec(). Adding the safe directory using --global won't work since the scope of --global is the current user.

Solution: I checked the permissions and ownership of directory /var/repo which was my current user. The Phabricator web server executes the commands using user "www-data".I then changed the ownership of the "/var/repo" directory to the following:

It happened to me after upgrading JetBrains' Rider code editor. Before the upgrade, Rider was launched by a shortcut as Administrator. The upgrade removed the shortcut's configuration of "Run as Administrator" which caused Rider's Terminal to start giving me this Git error. Running the application (Rider) as Administrator again solved the Git issue.

If you are using Sublime Merge on Windows and you just want to silence this warning, you need to edit the gitconfig file used by Sublime Merge, which is usually located in the installation directory in the Git\etc subdirectory (something like C:\Program Files\Sublime Merge\Git\etc\gitconfig).There you can add the [safe] section (if not already present) and either the suggested path, or the wildcard '*', as suggested by other answers.

I encountered fatal: detected dubious ownership in repository at using the Fork client on Windows against a repository in WSL.The solution was to open a Git console inside Fork (pointing at the Git Windows client used by Fork) and execute:

If you choose instead just git clone... then the ownership goes to the current username... One of them should work, likely you are mixing them up, and you need to type sudo git branch -a to avoid this error.

If you had set Notepad++ as your default Git editor during installation, then simply save the Notepad++ file you just edited. Else, if the editing stayed in the console, simply type :wq to save and close the file after editing.

If the command you are running already failed once or there was a previous version of the package in the install folder, try removing the corresponding package's folder before trying again or look for further solutions. Here, jhu3szh/serialize for example if it corresponds to your package name.

Wanted to report/discuss a possible privacy concern and image glitch, and understand it better for submission to Apple's feedback page: the iPad (and maybe iPhone) Photos app will consitently resurrect long-deleted photos in your Camera Roll, under certain circumstances. These are long-removed photos (as in removed many months ago, prior to the iOS 5 update), and possibly only the reduced-size thumbnail versions.

Note: as near as I can tell, the deleted photos were NOT originally from the camera roll! That's where they resurface, but I believe they are photos from other albums, maybe once which used to by synched to iPad but which I no longer synch. So "removed" might mean deleted or it might mean "no longer synched to iPad"... the images are so old I can't recall.

1) The Photos app (and/or iPhoto during wired synch?) is not fully removing photos (or at least, their thumbs). They're no longer visible in Photos app, but are being retained somewhere on the device.

2) A glitch in the Photos camera roll PNG handling (which I think may be new with iOS 5) causes those old images ro re-surface when you add a PNG to the camera roll. (The old photos were JPEG, but the image that triggers the bug must be a PNG with alpha channel)

1) Synch some photos to your iPad, then deselect them for synching and re-synch (so they're not there any more). Also, add some photos or screenshots to the camera roll and then delete them. I say to do both because I'm not 100% where the old photos come from, and I'm hoping this covers all bases! Actually, most people have already done these things in the past, and can probably skip this step.

2) Generate a transparent PNG using the art app Procreate (and probably any app that saves PNGs to the camera roll with alpha channel). All you have to do is scribble somethign into a blank Procreate canvas, then export it to your photo album. There is no need to do anything special to get an alpha channel or PNG format: you always get that. (Unless you used the Fill command to completely cover the canvas.) Now in the camera roll there should be your scribble on a transparent background. You can email it to yourself and see that clearly in Photoshop or Preview.

3) Here's the glitch: look at your camera roll (thumbnails view) and you'll see that the alpha-transparent background of the image has become one of your old removed photos! Tap it to enlarge and the alpha becomes black (which is fine, although it may seem odd if you intended to paint onto the default white canvas). But for just a moment, before you see the black, you will get a full-size glimpse of the old photo. (Or, maybe, an enlargement of the thumbnail?)

Yes, I can confirm this is happening on my iPad2 too. Most frustrating! It happens only in the thumbnail; once you open the photo (with the other photos as background...yes, there can be multiple images), then the background disappears. It looks to me that it's an enlargment of the thumbnail because it's very pixelated.

This has been happening for over a year. It was there in iOS5. I experienced it then, reported the issue to Apple and nothing has been done about it. I can confirm that it is still happening (albeit a bit differently) with the latest version of iOS. I am surprised that this hasn't gotten more attention in the media.

What has been fixed in the latest update is that the thumbnails now show a black background (tough luck if your image is black and alpha) however the cover of your library still exhibits these symptoms. If your alpha image is the last image in your library then it will show that image and a deleted image in the background as the 'image' for that library.

Deleted photos are being kept somewhere (possibly only at reduced size) and that's a MAJOR bug and privacy problem, even if the photos were never displayed. But to add insult to injury, they ARE unexpectedly displayed sometimes! And yes, this bug goes back a LONG time.

Does anyone ever take a photo that they don't want everyone to see? I think they do. A deleted photo (or screen snapshot) could give away everything from where you have been to what your religion, job, sexual orientation, or medical condition ius.

Does anyone ever use their iPad/iPhone to show photos? Do they ever let other people use their iPad? I think they do. And when they do, those deleted photos can be unexpectedly displayed (even if small)--or a savvy user could intentionally retrieve them in moments.

I'm running the latest iOS 6.0.1 on iPad 2. The problem still happens. Transparent PNGs and GIFs both let previously deleted photos show through (no improvement, no black background--maybe that's 6.1 which is iPhone-only). And I can find NO way to stop it.

All someone has to do to view your deleted photos, if they have your iPad in hand, is to save a transparent PNG or GIF from Safari. (Trivial: just Google for transparent gif, and pick a blank one from the image results.) Save the same image repeatedly, and in seconds you can see as many deleted photo thumbnails as you like. Even REALLY old ones that date back many months and have survived a wipe-and-restore-from-backup!

And realize that the Photo app's thumbnails, at retina resolution (on iPad anyway) are up to 216x216 pixels. Plenty of detail! And super easy to export: take a screen snapshot of the desired thumbnails and mail it to yourself.

This images should NOT be retained at all. Not just not displayed--they should not be retained in storage at all. When an image is deleted, delete the thumbnail too. Simple as that. Anything else is unacceptable.

You could imagine my surprise when I went back to my photo album to lift a gif for an em and saw another pic beneath it yet when I brought it to page from thumbnail the underlying pic disappeared! I immediately tested it by sending the gif to myself to verify it was traveling solo. It seemed kind of logical that the gif couldn't perform if it

I look forward to any ideas you all have. I intend to reread every entry in this section thoroughly so don't be irritated that I may have missed a point or suggestion from somebody already mentioned as I scanned them rather quickly so

3a8082e126