Swipe gestures stop working intermittently

I've noticed since iOS 8.1 on my iPad mini that swipe gesture to close an app stops working intermittently. I've found some workarounds (Settings > turn multitasking gestures off, then back on and swiping the notification screen down then back up) that will 'reset' the fault, but its getting VERY frustrating. Anyone got the definitive answer?

Similar Messages

Why do gestures stop working after Mountain Lion update?

I've just installed Mountain Lion on my MBP, and soon after a reboot, gestures stop working.
Rebooting fixes this, at least temporarily. But soon afterwards I can't switch between screens with three finger swipe etc.
Yes, gestures are enabled in preferences.
Any clues?

Having same issue with iMac and Magic Mouse.
I found that Mission Control stopped working as well (even with the App shortcut in Applications) and as such found a quicker workaround than login / logout. Open Terminal and type:
killall Dock
This will restart the Dock and Mission Control etc and seems to restore the gestures.
Cheers
Phil

Trackpad Gestures stop working after screen sleep on OS 10.9.2 update

Trackpad Gestures stop working after screen sleep after OS 10.9.2 update. Anybody know why? Is there a process I can stop or reboot in the Activity monitor to refresh this? These gestures include launch pad, mission control and full screen swipes. Annoying.

Same problem same version. On a MB Air. I have every gesture turned on. When this happens I have same problem on Magic Trackpad and my MB Trackpad. If I quit the app part of the gestures come back but then stop again. The worst is scrolling. This one is a show stopper and always require quit and relaunch.

Track pad Gestures stops working after upgrading to mountain lion osx

I upgraded to Mountain Lion Osx from Snow Leopard on my Macbook pro (Mid 2011 model) last month. However, it happens so that sudden;y all kind of trackpad gestures stops working. I have tried to find options on System preferences but nothing really works. i have tried unticking and then ticking again all the options to no avail. Even though restarting machine sometimes help but not always. Are their anyone with similar problems and if it is did you manage to come out with possible soutions?? If you did please kindly share as it is quite annoying to use machine without those gestures
Thanks in advance

Launch Terminal, type or copy/paste the following:
killall Dock
Hit enter.

Multi-touch gestures stop working?

Apple, there is an annoying bug in Mountain Lion that needs to be fixed. Sometimes when we wake our computers from sleep, multi-touch gestures stop working. The problem is related to the Dock. Restarting the dock by typing "killall Dock" into Terminal and hitting return provides a temporary resolution, but the problem will eventually return. There are several other posts in this forum and others. Seems like there should be an easy fix to what is the only complaint I currently have with your new operating system.
Thanks.

We are not Apple. We are users like you who help each other. If you have something to say to apple, contact them here.

Zoom-in, zoom-out pinch gesture stopped working a few days ago for no apparent reason.

Zoom-in, zoom-out pinch gesture stopped working a few days ago for no apparent reason. I went to Preferences>Gestures, turned off the selection, turned it on again, rebooted, etc. HELP. Any suggestions?

Try Settings>General>Siri>Off. Restart the phone then go back and turn Siri on again. It can take a few minutes for Siri to totally activate again.

HT1338 has anyone else had problems with their mail not loading properly and the multi gestures stopped working on their mac pro after new updates?

has anyone else had problems with their mail not loading properly and the multi gestures stopped working on their mac pro after new updates?

Have you tried calling Apple tech support?
http://www.apple.com/contact/

Bonjour Stops Working Intermittently After 7.3.1 Firmware Update

After updating the firmware on my Airport Extreme to 7.3.1, Bonjour seems to stop working intermittently. This affects both the 802.11N (MacBook, white Intel iMac, and aluminum Intel iMac) and 802.11G (MacBook) clients on my WLAN. I also connect to the AP with an iPod touch and a Wii. All the Macs are running 10.5.2.
Cycling the power on the router seems to fix the problem for a while.
Here's a snippet that might be related from my system log:
Apr 15 18:56:25 Jiminy mDNSResponder[16]: SetupAddr invalid sa_family 0
Apr 15 18:56:26: --- last message repeated 1 time ---
The only other network-related change that I have made recently is playing WoW.
Anyone have any ideas?

I have the same problem, btw. My AEBS 7.3.1 routinely loses all Bonjour support. Restarting the base station or power-cycling are the only fixes. I don't think the issue is on the Leopard side, but I'll reboot my laptop the next time it happens just to be sure.
Bonjour for Windows creates a JetDirect-style printer connection if I recall correctly. So after using it to discover and setup a new printer, it wouldn't really matter anymore if it suddenly disappeared. I'd have to double-check this to be sure, though.
On that note, I would recommend using JetDirect-style connections on your Mac, too, since bonjour connections are notoriously flaky for large print jobs like printing 8x10 photos.

Four-finger swipe constantly stops working

I'm running Snow Leopard on my 27" iMac with a Magic Trackpad, and the four-finger swipe Expose gesture regularly stops working, which two and three-finger gestures continue to work fine.
Sometimes a reboot will fix the problem, other times I can reboot two or three times before four-finger swipe works again. I've used the trackpad since it was released with no issues until a month or two ago when the problem started.
I've installed the latest combo update, repaired disk permissions many times over, reset PRAM and SMC, deleted a plist file pertaining to Expose which someone on the forum recommended. Nothing has helped as of yet.
When 10.7 Lion is released I'll do a full and fresh install which should finally take care of things, but until then I'd love to get this working without having to reinstall 10.6.
Thanks for any help.

Intel-based Apple Portables: Troubleshooting unresponsive trackpad issues
Portables and Magic Trackpad: Jumpy or erratic trackpad operation

Multitouch Gestures Stop working after some time in Mountain Lion

I have a problem with Multitouch Gestures on Macbook Pro, using Mountain Lion. After some time 3 thinger swipe to left/right stops working. The only thing that helps to solve this problem is making a restart. Are there any other ways to get rid of this problem?

Me too. My iMac and MBP same here. Having graphics glitches when playing games neither in Mac or Bootcamp with Windows. Sometimes screen even slashed into half and freezed. Wake up from sleep also have graphics issues, like I need to use the crusor to oaint out the grey login screen, if not, it will stay white. Slowly moving the crusor will paint back the grey background.

Swipe gesture not working in safari

After upgrading to Mavericks the swipe gesture (previous page) in safari is not working and if I swipe ( i am so used to it now), it causes the safari to freeze.
Anybody else have same problem

Go to System Preferences
Mouse
More Gestures
Enable Side Swipe
Shutdown Mac
Reboot
Before Grey screen appears press the folloing button simultaneously...
OPTION+COMMAND+P+R
When Grey screen appear, release and let to continue to boot cycle.

Gestures stopped working

I am using both magic mouse and trackpad. (still trying to decide if I like the trackpad.) I have been using both for about a month, but just in the last few days pretty much all of the multi-touch gestures have quit working on both. They will not scroll or swipe.

This may work... I have a similiar problem, it happens every few days, but if I go in and deselct all the gestures in system preferences, and then re-check them all and restart my coputer, they all start working again.
This started happening on my Mac Mini after I upgraded recently, still searching for a permanent solution.

Exchange 2013- Outlook will stop working intermittently but OWA works that time

Hello everyone. Hope someone can help me with this issue. We are experiencing a strange issue with our exchange 2013 server. We only have one exchange 2013 server and it is up to the CU2 level. The issue is sometimes the outlook clients
will stop working and the only way to fix this issue is by restarting the server . I tried restarting the exchange services but it didn't fix the issue. The outlook web access will work without any issue during this time. My research indicates
that the exchange server is getting some kind of disconnection/timeout from the Active directory. I can see the following event logs on the exchange server:
Log Name:      Microsoft-Exchange-MailboxDatabaseFailureItems/Operational
Source:        Microsoft-Exchange-MailboxDatabaseFailureItems
Date:          13/03/2014 1:12:20 PM
Event ID:      1
Task Category: Store
Level:         Information
Keywords:
User:          SYSTEM
Computer:      xxEXCHSVR.xxxx.local
Description:
Failure Item (Namespace=Store, Tag=HungStoreWorker, Database=CN=Mailbox Database 0572517180,CN=Databases,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=xxxxxxxxx,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=xx,DC=local,
Instance=Mailbox Database 0572517180)
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
    <Provider Name="Microsoft-Exchange-MailboxDatabaseFailureItems" Guid="{08E893EA-4C11-4FFF-A737-99B9EEDEE4F4}" />
    <EventID>1</EventID>
    <Version>0</Version>
    <Level>4</Level>
    <Task>1</Task>
    <Opcode>0</Opcode>
    <Keywords>0x8000000000000000</Keywords>
    <TimeCreated SystemTime="2014-03-13T02:42:20.026303800Z" />
    <EventRecordID>8180</EventRecordID>
    <Correlation />
    <Execution ProcessID="5980" ThreadID="14380" />
    <Channel>Microsoft-Exchange-MailboxDatabaseFailureItems/Operational</Channel>
    <Computer>xxEXCHSVR.xxxxxx.local</Computer>
    <Security UserID="S-1-5-18" />
</System>
<UserData>
    <EventXML xmlns:auto-ns2="http://schemas.microsoft.com/win/2004/08/events" xmlns="myNs">
      <Version>1</Version>
      <Namespace>1</Namespace>
      <Tag>38</Tag>
      <DatabaseGuid>{D789BB55-9D2A-445C-B29E-E7EA510E89D6}</DatabaseGuid>
      <DatabaseInstanceName>Mailbox Database 0572517180</DatabaseInstanceName>
      <Component>StoreService</Component>
      <IOErrorIsSpecified>false</IOErrorIsSpecified>
      <NotificationEventIsSpecified>false</NotificationEventIsSpecified>
      <IOError>
        <Category>0</Category>
        <FileName>
        </FileName>
        <Offset>0</Offset>
        <Size>0</Size>
      </IOError>
      <NotificationEvent>
        <EventID>0</EventID>
        <ParameterBufferSize>0</ParameterBufferSize>
        <ParameterBuffer>
        </ParameterBuffer>
      </NotificationEvent>
    </EventXML>
</UserData>
</Event>
Log Name:      Microsoft-Exchange-HighAvailability/Operational
Source:        Microsoft-Exchange-HighAvailability
Date:          3/03/2014 1:43:53 PM
Event ID:      841
Task Category: Database Action
Level:         Error
Keywords:
User:          SYSTEM
Computer:      xxEXCHSVR.xxxx.local
Description:
ListMdbStatus failed to server 'xxexchsvr': Microsoft.Mapi.MapiExceptionTimeout: MapiExceptionTimeout: RPC operation (ExRpcAdmin.Create) to the Microsoft Exchange Information Store service timed out. Operation did not complete within the given timeout of 00:00:05.
(hr=0x80040401, ec=0) ---> System.TimeoutException: Operation did not complete within the given timeout of 00:00:05.
   at Microsoft.Exchange.Data.Storage.Cluster.InvokeWithTimeout.InternalInvoke(Action invokableAction, Action foregroundAction, TimeSpan invokeTimeout, Boolean sendWatsonReportNoThrow, Object cancelEvent)
   at Microsoft.Exchange.Data.Storage.Cluster.InvokeWithTimeout.Invoke(Action invokableAction, Action foregroundAction, TimeSpan invokeTimeout, Boolean sendWatsonReportNoThrow, Object cancelEvent)
   at Microsoft.Exchange.Cluster.Replay.SafeRefCountedTimeoutWrapper.ProtectedCallWithTimeout(String operationName, TimeSpan timeout, Action operation)
   --- End of inner exception stack trace ---
Server stack trace:
   at Microsoft.Exchange.Cluster.Replay.SafeRefCountedTimeoutWrapper.ProtectedCallWithTimeout(String operationName, TimeSpan timeout, Action operation)
   at Microsoft.Exchange.Cluster.Replay.StoreRpcController.get_ExRpcAdmin()
   at Microsoft.Exchange.Cluster.Replay.StoreRpcController.<>c__DisplayClass19.<ListMdbStatus>b__18()
   at Microsoft.Exchange.Cluster.Replay.SafeRefCountedTimeoutWrapper.<>c__DisplayClass2.<ProtectedCallWithTimeout>b__0()
   at System.Runtime.Remoting.Messaging.StackBuilderSink._PrivateProcessMessage(IntPtr md, Object[] args, Object server, Object[]& outArgs)
   at System.Runtime.Remoting.Messaging.StackBuilderSink.AsyncProcessMessage(IMessage msg, IMessageSink replySink)
Exception rethrown at [0]:
   at System.Runtime.Remoting.Proxies.RealProxy.EndInvokeHelper(Message reqMsg, Boolean bProxyCase)
   at System.Runtime.Remoting.Proxies.RemotingProxy.Invoke(Object NotUsed, MessageData& msgData)
   at System.Action.EndInvoke(IAsyncResult result)
   at Microsoft.Exchange.Data.Storage.Cluster.InvokeWithTimeout.InternalInvoke(Action invokableAction, Action foregroundAction, TimeSpan invokeTimeout, Boolean sendWatsonReportNoThrow, Object cancelEvent)
   at Microsoft.Exchange.Data.Storage.Cluster.InvokeWithTimeout.Invoke(Action invokableAction, Action foregroundAction, TimeSpan invokeTimeout, Boolean sendWatsonReportNoThrow, Object cancelEvent)
   at Microsoft.Exchange.Cluster.Replay.SafeRefCountedTimeoutWrapper.ProtectedCallWithTimeout(String operationName, TimeSpan timeout, Action operation)
   at Microsoft.Exchange.Cluster.Replay.StoreRpcController.ListMdbStatus(Boolean isBasicInformation)
   at Microsoft.Exchange.Cluster.ActiveManagerServer.AmStoreHelper.GetAllDatabaseStatuses(AmServerName serverName, Boolean isBasicInformation, MdbStatus[]& mdbStatuses, Exception& exception)
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
    <Provider Name="Microsoft-Exchange-HighAvailability" Guid="{455E3D31-77EF-4853-94A1-032A399567EC}" />
    <EventID>841</EventID>
    <Version>0</Version>
    <Level>2</Level>
    <Task>1</Task>
    <Opcode>0</Opcode>
    <Keywords>0x8000000000000000</Keywords>
    <TimeCreated SystemTime="2014-03-03T03:13:53.421449100Z" />
    <EventRecordID>15370</EventRecordID>
    <Correlation />
    <Execution ProcessID="7264" ThreadID="5188" />
    <Channel>Microsoft-Exchange-HighAvailability/Operational</Channel>
    <Computer>xxEXCHSVR.xxxxx.local</Computer>
    <Security UserID="S-1-5-18" />
</System>
<UserData>
    <EventXML xmlns:auto-ns2="http://schemas.microsoft.com/win/2004/08/events" xmlns="myNs">
      <NodeName>xxexchsvr</NodeName>
      <Message>Microsoft.Mapi.MapiExceptionTimeout: MapiExceptionTimeout: RPC operation (ExRpcAdmin.Create) to the Microsoft Exchange Information Store service timed out. Operation did not complete within the given timeout of
00:00:05. (hr=0x80040401, ec=0) ---> System.TimeoutException: Operation did not complete within the given timeout of 00:00:05.
   at Microsoft.Exchange.Data.Storage.Cluster.InvokeWithTimeout.InternalInvoke(Action invokableAction, Action foregroundAction, TimeSpan invokeTimeout, Boolean sendWatsonReportNoThrow, Object cancelEvent)
   at Microsoft.Exchange.Data.Storage.Cluster.InvokeWithTimeout.Invoke(Action invokableAction, Action foregroundAction, TimeSpan invokeTimeout, Boolean sendWatsonReportNoThrow, Object cancelEvent)
   at Microsoft.Exchange.Cluster.Replay.SafeRefCountedTimeoutWrapper.ProtectedCallWithTimeout(String operationName, TimeSpan timeout, Action operation)
   --- End of inner exception stack trace ---
Server stack trace:
   at Microsoft.Exchange.Cluster.Replay.SafeRefCountedTimeoutWrapper.ProtectedCallWithTimeout(String operationName, TimeSpan timeout, Action operation)
   at Microsoft.Exchange.Cluster.Replay.StoreRpcController.get_ExRpcAdmin()
   at Microsoft.Exchange.Cluster.Replay.StoreRpcController.<>c__DisplayClass19.<ListMdbStatus>b__18()
   at Microsoft.Exchange.Cluster.Replay.SafeRefCountedTimeoutWrapper.<>c__DisplayClass2.<ProtectedCallWithTimeout>b__0()
   at System.Runtime.Remoting.Messaging.StackBuilderSink._PrivateProcessMessage(IntPtr md, Object[] args, Object server, Object[]& outArgs)
   at System.Runtime.Remoting.Messaging.StackBuilderSink.AsyncProcessMessage(IMessage msg, IMessageSink replySink)
Exception rethrown at [0]:
   at System.Runtime.Remoting.Proxies.RealProxy.EndInvokeHelper(Message reqMsg, Boolean bProxyCase)
   at System.Runtime.Remoting.Proxies.RemotingProxy.Invoke(Object NotUsed, MessageData& msgData)
   at System.Action.EndInvoke(IAsyncResult result)
   at Microsoft.Exchange.Data.Storage.Cluster.InvokeWithTimeout.InternalInvoke(Action invokableAction, Action foregroundAction, TimeSpan invokeTimeout, Boolean sendWatsonReportNoThrow, Object cancelEvent)
   at Microsoft.Exchange.Data.Storage.Cluster.InvokeWithTimeout.Invoke(Action invokableAction, Action foregroundAction, TimeSpan invokeTimeout, Boolean sendWatsonReportNoThrow, Object cancelEvent)
   at Microsoft.Exchange.Cluster.Replay.SafeRefCountedTimeoutWrapper.ProtectedCallWithTimeout(String operationName, TimeSpan timeout, Action operation)
   at Microsoft.Exchange.Cluster.Replay.StoreRpcController.ListMdbStatus(Boolean isBasicInformation)
   at Microsoft.Exchange.Cluster.ActiveManagerServer.AmStoreHelper.GetAllDatabaseStatuses(AmServerName serverName, Boolean isBasicInformation, MdbStatus[]& mdbStatuses, Exception& exception)</Message>
    </EventXML>
</UserData>
</Event>
Can anyone please tell me what causing this issue?
Thanks in advance.

Hi,
According to your description, your Outlook client intermittently cannot work. I recommend you try to use RPC trace log to find the root cause.
Additionally, I recommend you update to Exchange 2013 sp1 and then check if the issue still can be reproduced.
http://blogs.technet.com/b/rmilne/archive/2014/02/25/exchange-2013-sp1-released.aspx
If you have any question, please feel free to let me know.
Thanks,
Angela Shi
TechNet Community Support

X230, All touch/pen input functions stop working intermittently

Hello,
Ever since I got my x230 tablet (used), the pen/touch input intermittently stops working. It never happens when I'm using it, but when I either power down the tablet or resume from sleep, the touch and the pen will not function. The rotate button also doesn't work when the issue occurs, but the power button on the screen still functions. The fingerprint reader always works.
Once it stops working, there's no way for me to get the touch/pen input back. If I reboot, usually it remains not working. Pulling the battery out and waiting doesn't have any effect either; when I turn it back on it still doesn't work. The only thing that works is to wait...sometimes a day, sometimes an hour, and eventually the touch/pen starts working again after a reboot (or resume from standby).
I thought it might be a driver issue, but the issue is independent of operating system. When it works, it works in Windows 7, 8.1 and Linux Mint. When it doesn't work, it doesn't work across all three.
I've read of others having similiar issues, but every other occurence that I saw was fixed by a reboot...my problem isn't consistently.
Any help would be appreciated, as I love this machine when it works, but it's really useless when it doesn't (as I have another Lenovo laptop that has better specs than the tablet)
Kyle
Solved!
Go to Solution.

I have a bit more information which really makes the problem seem odd. There seem to be a few more things that stop functioning along with pen/touch. Here is a list of what functions and what doesn't when the issue arises.
Not working:
- All pen/touch input
- Screen rotate button
- "circular arrow" button beside screen rotate
- the sensor that senses the closing of the lid (the display stays lit when lid is closed and doesn't sleep automatically)
- rear-facing (battery and sleep) LEDs.
- front-facing WIFI LED
Things that continue to function:
- The display itself
- fingerprint reader
- webcam, microphone and speakers
- on-display power button
- front-facing HDD access light
The last two are very peculiar since they are on the same physical board as the two non-functioning buttons and the rear and WIFI LEDS which don't work. I have no idea what is wrong. It can't be a connection issue as starting and stopping of the problem coincides with power-ons/offs.
Please help me!

I'm having huge problems with my MBP (2010). Exposé just stopped working, both the key on the keyboard and the multitouch gesture stopped working. Does anyone have any idea why, or how to solve it?

Exposé just stopped working, both the key on the keyboard and the multitouch gesture gets no response. Does anyone have any idea why, or how to solve it?

I found a way to fix it. Simply restart the dock by using "killall Dock" in the terminal.
Cheers!

Swipe gestures stop working intermittently

Similar Messages

Maybe you are looking for