What is the difference between “application … closed unexpectedly” and “system program problem detected”?

I have two laptops, both with Ubuntu 19.04 installed. One of them is a couple of years older and has had the Ubuntu version upgraded a few times. The other one is newer and got 19.04 installed from the beginning, not upgraded from any previous Ubuntu version.

On my older laptop I sometimes get error messages looking like this:

Error message window on my old laptop

which is nice because it allows me to click the “Show details” button to see lots of details about what happened.

On the newer laptop there are sometimes messages looking like this:

enter image description here

I suspect that it may be the same kind of problem but for some reason handled differently by Ubuntu despite the fact that both are running Ubuntu 19.04.

Do these messages mean the same thing?

If not, what is the difference between “application … closed unexpectedly” and “system program problem detected” and how can I get more details in the latter case? (the “system program problem detected” leaves no file in /var/crash/ unfortunately)

One theory I have about this is that the older laptop, having originally run older Ubuntu versions and then been upgraded, has some settings in a config file somewhere left from a previous Ubuntu version telling it to use the older, more detailed (and in my opinion much better) way of showing errors. Could this theory be correct? If so, which config file would I need to modify in order to get the behavior I want, allowing me to show details about the error?

What happens if GSA-SER shuts down unexpectedly?

Good morning, GSA friends! :)
I was wondering how it affects everything if SER shuts down abruptly.
I have a keyboard with a shutdown key. I have to re-assign it, if possible, b/c it’s been pressed accidentally a few times.
I’ve noticed SER does not show the Submitted or Verified links when I restart the program.
Is it just the totals that are affected? Anything else?
Thanks, kindly….Deeeeeeee

SharePoint 2016: Users forced to re-authenticate unexpectedly

Users are being forced to reauthenticate. We have tried setting a few configurations via PowerShell that we read about online, but nothing seems to change this problem.

Any tips would be greatly appreciated. If anyone has their settings so that people stay logged on for 8 hours or even longer, it wold be great to see what you have set.

Here is a script that we ran:

if ((Get-PSSnapin “Microsoft.SharePoint.PowerShell” -ErrorAction SilentlyContinue) -eq $ null) { Add-PSSnapin “Microsoft.SharePoint.PowerShell” } Get-SPSecurityTokenServiceConfig $ mysts = Get-SPSecurityTokenServiceConfig

$ mysts.WindowsTokenLifetime = (New-TimeSpan -Minutes 20)

$ mysts.LogonTokenCacheExpirationWindow = (New-TimeSpan -Minutes 19)

$ mysts.Update()

Set-SPSecurityTokenServiceConfig -ServiceTokenLifetime 1000

SharePoint 2013 – One or more services have started or stopped unexpectedly – SPTimerV4

I’m getting this error message in CA. I checked the timer service and it is up and running. I tried with “Repair Automatically” but use.

ULS Error

The following services are managed by SharePoint, but their running state does not match what SharePoint expects: FIMSynchronizationService. This can happen if a service crashes or if an administrator starts or stops a service using a non-SharePoint interface. If SharePoint-managed services do not match their expected running state, SharePoint will be unable to correctly distribute work to the service.. Automatic repair is being attempted.

Thread 15: Fatal error: Unexpectedly found nil while unwrapping an Optional value

Mi app de Buscador cuando intento poner espacio entre palabras me da este error Que debo rectificar ????????

let urlCompleto = “https://es.wikipedia.org/w/api.php?action=query&prop=extracts&format=json&exintro=&titles=(palabra!.replacingOccurrences(of:” “, with:”%20″))”

Field Value of Loaded List Item is Unexpectedly Returning “NaN”

I’m trying to query the last item in the current list where status = New, so I can auto-populate one of the fields based on the previous item’s value. Executing “alert(collListItem);” displays “[object] [Object]”, and the onQuerySucceeded function is in fact firing, however, the value it’s inputing is “NaN” when it should be the previous number field value +1 (the previous value is 1).

var collListItem; function QueryLastNewItem() {     var clientContext = new SP.ClientContext();     var List = clientContext.get_web().get_lists().getByTitle('Tracker');     var query = new SP.CamlQuery();     query.set_viewXml("<View><RowLimit>1</RowLimit><Query><OrderBy><FieldRef Name='ID' Ascending='False' /></OrderBy><Where><Eq><FieldRef Name='Status' /><Value Type='Choice'>New</Value></Eq></Where></Query></View>");     collListItem = List.getItems(query);     clientContext.load(collListItem);     alert(collListItem);     clientContext.executeQueryAsync(Function.createDelegate(this,  this.onQuerySucceeded), Function.createDelegate(this, this.onQueryFailed));          }  function onQuerySucceeded(sender, args) {      //Once the list item is loaded, populate number field with the previous number field plus 1     if ($  ("select[id^='Is_x0020_this_x0020_item_x002']").val() == "New")          {         $  ("input[id^='Number']").val(collListItem.get_item("Number")+1);         } }   function onQueryFailed(sender, args) {     alert('Request failed. \nError: ' + args.get_message() + '\nStackTrace: ' + args.get_stackTrace()); } 

Since the query seems to be successful, I’m confused as to why the value isn’t being assigned appropriately. I thought it may be because “collListItem” could be considered a collection of objects, but I have set the row limit to 1 in the CAML query, so it should only contain 1 item.

Any help or suggestions are much appreciated.

PrimeNG – p-dropdown rendered unexpectedly

I’m using PrimeNG in my Angular application. I’m intending to use the p-dropdown component, but it is rendering very strangely in my components.

p-dropdown strange render

This looks nothing like what they demonstrate in their documentation.

Here is package.json:

{   "name": "soar",   "version": "0.0.0",   "scripts": {     "ng": "ng",     "start": "ng serve",     "build": "ng build",     "test": "ng test",     "lint": "ng lint",     "e2e": "ng e2e"   },   "private": true,   "dependencies": {     "@angular/animations": "^7.2.15",     "@angular/cdk": "^8.0.1",     "@angular/common": "~7.2.0",     "@angular/compiler": "~7.2.0",     "@angular/core": "^8.0.2",     "@angular/forms": "~7.2.0",     "@angular/material": "^8.0.1",     "@angular/platform-browser": "~7.2.0",     "@angular/platform-browser-dynamic": "~7.2.0",     "@angular/router": "~7.2.0",     "@ng-bootstrap/ng-bootstrap": "^4.1.3",     "@ngrx/effects": "^7.4.0",     "@ngrx/store": "^7.4.0",     "@ngrx/store-devtools": "^7.4.0",     "bootstrap": "^4.3.1",     "chart.js": "^2.8.0",     "core-js": "^2.5.4",     "font-awesome": "^4.7.0",     "primeng": "^8.0.0",     "quill": "^1.3.6",     "rxjs": "~6.3.3",     "tslib": "^1.9.0",     "zone.js": "~0.8.26"   },   "devDependencies": {     "@angular-devkit/build-angular": "~0.13.0",     "@angular/cli": "~7.3.9",     "@angular/compiler-cli": "~7.2.0",     "@angular/language-service": "~7.2.0",     "@ngrx/schematics": "^7.4.0",     "@types/jasmine": "~2.8.8",     "@types/jasminewd2": "~2.0.3",     "@types/node": "~8.9.4",     "codelyzer": "~4.5.0",     "jasmine-core": "~2.99.1",     "jasmine-spec-reporter": "~4.2.1",     "karma": "~4.0.0",     "karma-chrome-launcher": "~2.2.0",     "karma-coverage-istanbul-reporter": "~2.0.1",     "karma-jasmine": "~1.1.2",     "karma-jasmine-html-reporter": "^0.2.2",     "protractor": "~5.4.0",     "ts-node": "~7.0.0",     "tslint": "~5.11.0",     "typescript": "~3.2.2"   } } 

I am using Bootstrap app-wide, but I wouldn’t imagine that’d be a problem. Full-disclosure: I’m not a UI/UX person, but I think this should instead be rendered as some sort of select element. What may be causing this and how do I fix it?

Python quits unexpectedly

I am trying to run a python (2.7) script in Spyder 3.1.4 on Mojave 10.14.5, and python keeps quitting unexpectedly with the following error:

    Application Specific Information: crashed on child side of fork pre-exec  Thread 0 Crashed: 0   libdispatch.dylib               0x00007fff5afbf58a dispatch_apply_f + 754 1   cv2.so                          0x000000011d22f0de cv::parallel_for_(cv::Range const&, cv::ParallelLoopBody const&, double) + 622 2   cv2.so                          0x000000011d4d1bca cv::hal::resize(int, unsigned char const*, unsigned long, int, int, unsigned char*, unsigned long, int, int, double, double, int) + 1930 3   cv2.so                          0x000000011d4da731 cv::resize(cv::_InputArray const&, cv::_OutputArray const&, cv::Size_<int>, double, double, int) + 8417 4   cv2.so                          0x000000011cf27578 pyopencv_cv_resize(_object*, _object*, _object*) + 952 5   org.python.python               0x000000010b32aef3 PyEval_EvalFrameEx + 30323 6   org.python.python               0x000000010b323572 PyEval_EvalCodeEx + 1538 7   org.python.python               0x000000010b32fdb5 fast_function + 117 8   org.python.python               0x000000010b32aa74 PyEval_EvalFrameEx + 29172 9   org.python.python               0x000000010b323572 PyEval_EvalCodeEx + 1538 10  org.python.python               0x000000010b2ad9ac function_call + 364 11  org.python.python               0x000000010b2875c3 PyObject_Call + 99 12  org.python.python               0x000000010b32f51d PyEval_CallObjectWithKeywords + 93 13  org.python.python               0x000000010b3208fa builtin_map + 874 14  org.python.python               0x000000010b32b698 PyEval_EvalFrameEx + 32280 15  org.python.python               0x000000010b323572 PyEval_EvalCodeEx + 1538 16  org.python.python               0x000000010b2ad9ac function_call + 364 17  org.python.python               0x000000010b2875c3 PyObject_Call + 99 18  org.python.python               0x000000010b32b5c2 PyEval_EvalFrameEx + 32066 19  org.python.python               0x000000010b323572 PyEval_EvalCodeEx + 1538 20  org.python.python               0x000000010b2ad9ac function_call + 364 21  org.python.python               0x000000010b2875c3 PyObject_Call + 99 22  org.python.python               0x000000010b32b5c2 PyEval_EvalFrameEx + 32066 23  org.python.python               0x000000010b32fe52 fast_function + 274 24  org.python.python               0x000000010b32aa74 PyEval_EvalFrameEx + 29172 25  org.python.python               0x000000010b32fe52 fast_function + 274 26  org.python.python               0x000000010b32aa74 PyEval_EvalFrameEx + 29172 27  org.python.python               0x000000010b323572 PyEval_EvalCodeEx + 1538 28  org.python.python               0x000000010b2ad9ac function_call + 364 29  org.python.python               0x000000010b2875c3 PyObject_Call + 99 30  org.python.python               0x000000010b294986 instancemethod_call + 182 31  org.python.python               0x000000010b2875c3 PyObject_Call + 99 32  org.python.python               0x000000010b2e41bd slot_tp_init + 141 33  org.python.python               0x000000010b2e01b3 type_call + 339 34  org.python.python               0x000000010b2875c3 PyObject_Call + 99 35  org.python.python               0x000000010b32ab50 PyEval_EvalFrameEx + 29392 36  org.python.python               0x000000010b32fe52 fast_function + 274 37  org.python.python               0x000000010b32aa74 PyEval_EvalFrameEx + 29172 38  org.python.python               0x000000010b32fe52 fast_function + 274 39  org.python.python               0x000000010b32aa74 PyEval_EvalFrameEx + 29172 40  org.python.python               0x000000010b323572 PyEval_EvalCodeEx + 1538 41  org.python.python               0x000000010b2ad9ac function_call + 364 42  org.python.python               0x000000010b2875c3 PyObject_Call + 99 43  org.python.python               0x000000010b294986 instancemethod_call + 182 44  org.python.python               0x000000010b2875c3 PyObject_Call + 99 45  org.python.python               0x000000010b2e41bd slot_tp_init + 141 46  org.python.python               0x000000010b2e01b3 type_call + 339 47  org.python.python               0x000000010b2875c3 PyObject_Call + 99 48  org.python.python               0x000000010b32ab50 PyEval_EvalFrameEx + 29392 49  org.python.python               0x000000010b323572 PyEval_EvalCodeEx + 1538 50  org.python.python               0x000000010b32fdb5 fast_function + 117 51  org.python.python               0x000000010b32aa74 PyEval_EvalFrameEx + 29172 52  org.python.python               0x000000010b323572 PyEval_EvalCodeEx + 1538 53  org.python.python               0x000000010b2ad9ac function_call + 364 54  org.python.python               0x000000010b2875c3 PyObject_Call + 99 55  org.python.python               0x000000010b32b5c2 PyEval_EvalFrameEx + 32066 56  org.python.python               0x000000010b323572 PyEval_EvalCodeEx + 1538 57  org.python.python               0x000000010b322f66 PyEval_EvalCode + 54 58  org.python.python               0x000000010b351e64 PyRun_FileExFlags + 164 59  org.python.python               0x000000010b31f4ab builtin_execfile + 507 60  org.python.python               0x000000010b32b698 PyEval_EvalFrameEx + 32280 61  org.python.python               0x000000010b323572 PyEval_EvalCodeEx + 1538 62  org.python.python               0x000000010b32fdb5 fast_function + 117 63  org.python.python               0x000000010b32aa74 PyEval_EvalFrameEx + 29172 64  org.python.python               0x000000010b323572 PyEval_EvalCodeEx + 1538 65  org.python.python               0x000000010b32fdb5 fast_function + 117 66  org.python.python               0x000000010b32aa74 PyEval_EvalFrameEx + 29172 67  org.python.python               0x000000010b323572 PyEval_EvalCodeEx + 1538 68  org.python.python               0x000000010b322f66 PyEval_EvalCode + 54 69  org.python.python               0x000000010b351bdd PyRun_InteractiveOneFlags + 381 70  org.python.python               0x000000010b3516be PyRun_InteractiveLoopFlags + 206 71  org.python.python               0x000000010b351568 PyRun_AnyFileExFlags + 136 72  org.python.python               0x000000010b367668 Py_Main + 3096 73  libdyld.dylib                   0x00007fff5affc3d5 start + 1  Thread 0 crashed with X86 Thread State (64-bit):   rax: 0x0000001c5b80f480  rbx: 0x0000000000000100  rcx: 0x0000000000000000  rdx: 0x00007fff5afbeef8   rdi: 0x0000001c5b80e000  rsi: 0x00007fff9194d7c0  rbp: 0x00007ffee4982f30  rsp: 0x00007ffee4982ea0    r8: 0x0000001c5b80f480   r9: 0x000000000000000b  r10: 0x0000001c5b800000  r11: 0x0000000000000003   r12: 0x000000000000000b  r13: 0x0000001c5b80f480  r14: 0x00000000100020ff  r15: 0x0000001c5bc05d40   rip: 0x00007fff5afbf58a  rfl: 0x0000000000010206  cr2: 0x0000000000000110  Logical CPU:     6 Error Code:      0x00000006 

Trap Number: 14

Can anyone provide some suggestions or at least interpret message

lanmanserver service unexpectedly killing connections on Server 2016 for “DOS Protection”


Windows Server 2016 DataCenter instance is reporting an error EventID2025:

Event: ID2025 "The server has detected an attempted Denial-Of-Service attack from client \SERVERA, and has disconnected the connection." 

The server we are copying files to has accepted files via smbclient mput for eons, and is only recently failing after being cycled out.


  • TCP Offloading for large receives is ENABLED on the NIC, this hasn’t ever been an issue previously, and is the default for EC2 instances.
  • Quantity and size of files has not changed.
  • No observed network congestion.
  • Occurs about 85% of the time we try and run the copy.
  • Disabling DOS Protection via HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\LanManServer\Parameters resolves the issue, but seems hacky.
  • Problem Server: Windows Server 2016 DataCenter Ed. (with latest updates as of 6/11/2019)
  • Source Server: Docker instance, based off of ubuntu:trusty-20190122

We could mess with both *MaxMpxCt, and TCP offloading (as per. TechNet discussion and Rackspace Article) but it seems better to understand WHY windows is suddenly deeming this traffic problematic seemingly out of nowhere, before messing with performance settings.

What should we do/investigate to pin down why this is suddenly cropping up?

The AppFabric Caching Service service terminated unexpectedly

The event viewer of the WFE server recieves errors regarding the AppFabric Caching Service:

  1. AppFabric Caching service crashed with exception

  2. {6d304b9000000000000000000000000} failed to refresh lookup table, exception: {Microsoft.Fabric.Common.OperationCompletedException: Operation completed with an exception —> System.TimeoutException: The operation has timed out.

  3. Faulting application name: DistributedCacheService.exe, version