Crawl distributed file system error: The object was not found

SharePoint 2013 Standard server.

We have a a distributed file system (DFS) which I want to crawl.

I use a UNC path like:

\machine1234\Departments\HR 

The account that runs the crawler can access it. I tested by logging in with that account and pasting the above path into explorer.

I run the a full crawl and get the following error message:

The object was not found

I run with and without proxy, same difference. Any ideas?

command not found: sudo

After reading about the lately discovered vulnerability with sudo, I decided to update to 1.8.28 manually. I downloaded deb file from sudo.ws and used dpkg to install it, and it failed due to lack of dependencies.

sudo dpkg -i debs/sudo_1.8.28-1_ubu1804_i386.deb  (Reading database ... 232031 files and directories currently installed.) Preparing to unpack .../sudo_1.8.28-1_ubu1804_i386.deb ... Unpacking sudo:i386 (1.8.28-1) over (1.8.27-1ubuntu1.1) ... dpkg: dependency problems prevent configuration of sudo:i386: sudo:i386 depends on libc6. sudo:i386 depends on libpam0g. sudo:i386 depends on libpam-modules. sudo:i386 depends on zlib1g. sudo:i386 depends on libselinux1. sudo:i386 depends on libaudit1.  dpkg: error processing package sudo:i386 (--install): dependency problems - leaving unconfigured Processing triggers for man-db (2.8.5-2) ... Errors were encountered while processing: sudo:i386 

After that I can’t call sudo any more and it seems to be damaged cause I can locate it in /usr/bin/sudo:

l /usr/bin/sudo -rwsr-xr-x 1 root root 479K Oct 10 20:15 /usr/bin/sudo 

Since there is no Root user available on Ubuntu I was wondering if there is any solution other than rebooting as root in recovery mode?

No Bluetooth Adapter found Ubuntu 19.04

My Bluetooth adapter suddenly disappeared, and I have been trying to fix it but no luck.

I have tried to enable or start it again but its status is still inactive.

~$   sudo systemctl enable bluetooth Synchronizing state of bluetooth.service with SysV service script with /lib/systemd/systemd-sysv-install. Executing: /lib/systemd/systemd-sysv-install enable bluetooth  ~$   sudo systemctl status bluetooth ● bluetooth.service - Bluetooth service   Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor preset: enabled)   Active: inactive (dead)     Docs: man:bluetoothd(8)  Oct 14 00:33:19 lau-desktop systemd[1]: Condition check resulted in Bluetooth service being skipped. Oct 14 00:34:27 lau-desktop systemd[1]: Condition check resulted in Bluetooth service being skipped. Oct 14 00:34:43 lau-desktop systemd[1]: Condition check resulted in Bluetooth service being skipped. Oct 14 00:37:36 lau-desktop systemd[1]: Condition check resulted in Bluetooth service being skipped. 

What else can I do?

“NSPR headers not found” error while building evolution using cmake

I am installing Evolution from source using cmake by following command:

cmake -G "Unix Makefiles" -DCMAKE_BUILD_TYPE=Release -DWITH_OPENLDAP=OFF .. 

But it result in following error message:

-- Looking for include files nspr.h, prio.h -- Looking for include files nspr.h, prio.h - not found CMake Error at cmake/modules/FindSMIME.cmake:80 (message):   NSPR headers not found.  Use -DWITH_NSPR_INCLUDES=/path/to/nspr to specify the include dir of NSPR. 

Any one could help me to solve this problem?

NOTE: -DWITH_OPENLDAP=OFF is because cmake gives me an error if I do not use this phrase.

Ubuntu 18 WiFi adapater not found in HP laptop

I just installed Ubuntu 18 my Laptop and I am facing issue with WiFi adapater not found and I approached lot of blogs but still not resolved my issue.

I approached below link WiFi works fine after installing but if I restarting my system then it issue again repeating with WiFi adapater not found.

http://ubuntuhandbook.org/index.php/2018/08/no-wifi-adapter-found-hp-laptops-ubuntu-18-04/

Please provide the solution for this issue

USB Type-C to HDMI adapter does not work on Ubuntu – no driver found

I bought a USB Type-C to HDMI adapter from ELECOM (the brand name written in the adapter)

The monitor does not detect/work with this adapter.

I have tested the monitor (HDMI cable only) with a different laptop and it is working.

I conclude that the problem is the USB t-C to HDMI adapter is the one to blame.

By checking the dmesg, I get this when I plug in the device:

[ 296.081961] usb 1-1: USB disconnect, device number 5 [ 311.731196] usb 1-1: new low-speed USB device number 6 using xhci_hcd [ 311.885375] usb 1-1: New USB device found, idVendor=1f29, idProduct=0000, bcdDevice= 0.00 [ 311.885377] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 311.885378] usb 1-1: Product: ANALOGIXSEMI COM [ 311.885380] usb 1-1: Manufacturer: BILLBOARD CLASS [ 311.885381] usb 1-1: SerialNumber: 201501ANX001 

I also tried in Windows 10 system, and it does not work as well, my laptop is dual-boot.

My OS info is this:

UBUNTU 10.04 LTS Linux 5.0.0-31-generic #33~18.04.1-Ubuntu SMP Tue Oct 1 10:20:39 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux 

By checking on Windows 10, the USB in the device manager shows a warning with the Invalid Device Descriptor as the warning message.

By checking in Linux, with the lsusb I see this for this adapter:

Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0489:e0a2 Foxconn / Hon Hai Bus 001 Device 003: ID 0bda:58f4 Realtek Semiconductor Corp. Bus 001 Device 005: ID 27c6:5385 Bus 001 Device 008: ID 1f29:0000 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub 

Where this line is the one that is related to the USB adapter (the before last):

Bus 001 Device 008: ID 1f29:0000 

By checking it using lsusb -t I get this:

/:  Bus 04.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/2p, 5000M /:  Bus 03.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/2p, 480M     |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M     |__ Port 1: Dev 2, If 1, Class=Human Interface Device, Driver=usbhid, 12M     |__ Port 1: Dev 2, If 2, Class=Human Interface Device, Driver=usbhid, 12M /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 5000M /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M     |__ Port 1: Dev 10, If 0, Class=Application Specific Interface, Driver=, 1.5M     |__ Port 5: Dev 3, If 3, Class=Video, Driver=uvcvideo, 480M     |__ Port 5: Dev 3, If 1, Class=Video, Driver=uvcvideo, 480M     |__ Port 5: Dev 3, If 2, Class=Video, Driver=uvcvideo, 480M     |__ Port 5: Dev 3, If 0, Class=Video, Driver=uvcvideo, 480M     |__ Port 7: Dev 4, If 0, Class=Wireless, Driver=btusb, 12M     |__ Port 7: Dev 4, If 1, Class=Wireless, Driver=btusb, 12M     |__ Port 10: Dev 5, If 0, Class=Communications, Driver=cdc_acm, 12M     |__ Port 10: Dev 5, If 1, Class=CDC Data, Driver=cdc_acm, 12M 

Above, the line that is regarding to the adatar is this one:

    |__ Port 1: Dev 10, If 0, Class=Application Specific Interface, Driver=, 1.5M 

So, as we can see, the speed is only 1.5M, and there is no driver for this as shown.

Port 1: Dev 10, If 0, Class=Application Specific Interface, Driver=, 1.5M I guess there is no driver for this device, as indicated above.

REST API: No route was found matching the URL and request method

I’m having issues adding a custom REST API route to WordPress. Using my own plugin, i’ve registered the route as followed:

add_action( 'rest_api_init', function() {   register_rest_route( $  namespace, 'handler_mijnenergie', array(     'methods'   => '\WP_REST_Server::CREATABLE ',     'callback'  => [ $  this, 'handle_energie_data' ]   ), false ); } ); 

When calling the namespace “/wp-json/watz/v1” I get a correct response in Postman that the route is shown. enter image description here

However, when i try to access the route request directly, i get thrown a 404 error. So far I’ve tried:

  • Rewriting the permalinks
  • Using standard WordPress .htaccess
  • Disabling plugins
  • Changing method/namespace & request
  • Testing other plugin routes like Yoast or Contact Form 7 (they work)

Any idea what could be causing the issue here and what I need to alter to get this working?

MarketplaceDiscoveryStrategy failed with an error Node not found

Cuando intento acceder en Eclipse a los plugins y componentes instalados, mediante Help–> Eclipse MarketPlace y una vez ahí clico en la pestaña Installed, me salta el siguiente error:

MarketplaceDiscoveryStrategy failed with an error Node not found

Os adjunto una imagen, aunque sé que no somos muy fans de ellas y por eso he puesto antes el error en texto para facilitar su copia

introducir la descripción de la imagen aquí

Necesito actualizar el plugin de maven para solucionar unos errores Desconocidos (Unknown) que he visto en esta página que se deben a la versión de este.

¿Alguien podria ayudarme que no encuentro solución?