Sentences with phrase «about user error»

Not exact matches

I get about 3 - 4 shaves per blade, seldom any nicks or cuts and if I do it's «user error», not the blade, never any irritation.

I really think its all about trial and error per user.

GIS is able to store, manipulate, analyse and communicate between user and data, while mobile - based QR codes technology can be read by an imaging device (such as a camera) and processed using Reed - Solomon error correction until the image can be appropriately interpreted about the tree; data is then extracted from tree patterns present in both horizontal and vertical component of the image.

Couldn't seem to leave a comment — user error, I am sure — on your recent book review about the two girls, with the eerie blue cover, but I am going to save it to Goodreads.

Because of an editing error, an article in Sunday Business this week about coaching services for users of online dating sites misstated the Web address of one such service.

The eContent created with your tool should be capable of generating information about the actions taken by your users, e.g. the results obtained while solving interactive activities, number of attempts, errors made, or a course bounce rate.

By being able to confirm the cost prior to printing, our users think twice about what they're printing and it has also helped them to overcome errors and misprints.»

Users are getting fed up with poor quality and control with e-books and are getting angry about not being able to report errors to anybody.

Users also complain about poor customer service and technical errors in the automation system that can sometimes accidentally reject a loan application.

It seems to me, if you're asking about error checking with respect to an electronic system, either (a) you're asking about the benefits for the programmer of the system, or (b) you're asking on behalf of the user, so reporting actually could be relevant, because that's a way in which the user interacts with the system — the user can compare reports to other sources of information to check for errors.

So to those of you that talk about burns from these, I agree that it is user error, not the leash.

A quick scan for the error code online turned up a rash of users complaining about the same error, including this story by our own Japan - based Martyn Williams confirming that yes, indeed, there's Big Trouble in Not - So - Little Sony - land.

General fixes • Significant improvements to the Squad Join interface • Removed FIND ME A SQUAD option • Allow players to join empty Squads alone, thus having 1/4 Squad members • Change order of options to LEAVE SQUAD, INV A FRIEND, SWITCH TEAM • Disable Privacy flag when 1 man Squad • Reset Privacy flag from Private to Public when Squad drops to 1 player • All occupied Squads will now show up colored blue on the Squad selection screen • Players who choose not to join Squads will also show up as Blue in the «Not in a Squad» line • Squads that are currently empty will display as white — if you wish to join an empty Squad, you can choose the first one marked with white text • Added round duration and ticket summary at end of round screen • Fixed sound for when climbing ladders • Fixed and issue with some weapons» sounds in first person view • Fixed a swim sound loop error • You should no longer be able to damage a friendly vehicle when sitting in an open position • Grenades now drop to ground if you get killed while attempting to throw it • Spawn protection now should work in Conquest so you no longer should spawn too close to enemies • You should no longer spawn too close to enemies in TDM and SQDM • Fix for missing input restriction during intro movie, causing players to potentially fall and die while watching movie if moving controller (or having a controller with a bad stick zone) • Combat areas on Kharg Island in Rush mode tweaked in order to disallow defenders to access the carrier ship after first base is taken and being able to enter the AA gun • Fixed a problem with revived players not being able to get suppressed • Fixed a problem with the camera when being revived in co-op • Spotting VO now plays when spotting from MAV / EOD bot • Fixed several issues regarding the kill card, including showing wrong weapons used for the kill • Fixed that sometimes you would be stuck on a black screen when kicked from server • Fixed so when a team captures two flags at the same time, the UI does not show wrong owner of the flag • Fixed a problem where the capture progress bar was shown as friendly when the enemy was capturing • Fixed a problem with the bipod deploy sound • Fixed a problem that you could be spawned in with no weapons after being killed while using the EOD bot • Fixed problems with health bars not displaying health properly when using EOD bots • Fixed a problem with flickering name tags • Fixed a problem where you could damage friendly helicopters • Fixed a problem where you could get stuck in the co-op menu when attempting to join the session twice • You should now be able to spot explosives • You should no longer spawn in home base if your selected spawn point is disabled while waiting to spawn (e.g. if your teammate dies right before you are about to spawn) • Damage from bullets will now continue to cause damage even after the firing user is dead • Fixed several client crashes • Fixed a problem where players could get stuck in the join queue • Fixed the repair icon on the minimal • Fixed a problem with changing camera on certain vehicles • Fixed a problem with the grenade indicator when in guided missile mode • Fixed a problem where the machine could hard lock when joining a public coop game • Fixed a problem where the headset attached icon would not show up in the UI • Fixed a problem with the falling antenna on Caspian Border.

Sometimes users may get an error about missing DyingLight.exe when they try to run the game after installation.

This error reflects misplaced anxiety about users» ability to scan a page to find appropriate navigational choices.

Reports about these types of error messages first surfaced on Twitter earlier this month, when users reported that they were told by their Netflix app that Verizon's (S VZ) network was «crowded.»

And don't forget about all those iPhone users who got their screens replaced by an independent shop, only to receive the infamous Error 53 later on.

Alcatel One Touch might be shipping the new Idol smartphone in Virtual Reality packaging, iPhone error 53 is frustrating users who have had their home buttons repaired, and Tim Cook takes his ball and runs home after people tweet mean things about his Super Bowl photo.

Ugh... talk about computer woes; mine seem to be user - error woes!.