One of my workflows has excessive delays and that too of a longer duration. For instance, one delay in my workflow is of three months and other is of a single month. Now the problem is that my SharePoint timer service gets stuck and its status is “Pausing”. Is it possible that the delays in workflows are causing the timer to be stuck? Has this happened to anyone before?
This article suggests that this problem can be caused by a bad workflow instance. Does my workflow come in that category?
I have used ubuntu 16.04 with two RTX1080 Ti for a month to do deep-learning, but yesterday I fond my Keras failed to run the program on GPU, so I change my driver to 430. But after I reboot it, the problem occurred. I can’t get into tty mode, adding nomodeset also failed to launch, does anyone know how to handle this problem?
My organization recently changed the user naming policy, removing spaces from user names replacing them with dots.
For the most part everything works fine with this change, however, the old user name appears to be “stuck” in the dropdown in the people-picker controls used in lists.
I’ve found that if I explicitly type in the proper name (with the dot) it works fine…but it still brings up the old name with the space between names as a possible selection.
When the name with the space is used it presents an error: “The user does not exist or is not unique.”
How can I make the old name go away?
Recently after updating the software on my Ubuntu 19.04 I got this error, as well as my Windows 10 dual boot, refuses to start up. Even trying to boot from a Ubuntu on a USB drive fails.
Following this suggestions I’ve went into Ubuntu recovery mode and set
GRUB_CMDLINE_LINUX_DEFAULT=nomodeset This allowed me to see what happens. Essentially during load up of Ubuntu, I get:
[ Ok ] Starting Network Manager Script dispatcher Service ... [ Ok ] Started Network Manager Script dispatcher Service. [44.077490] watchdog: BUG soft lockup - CPU#3 stuck for 23s! [Network Manager:1049] Started Tool to automatically collect and submit kernel crash signatures.
Strangely two things I noticed above these final lines are:
[3.517543] rtlwifi: RTl8XXX did not boot from eeprom, check it !! [4.363835] [drm:amdgpu_init [amdgpu]] *ERROR* VGACON disables amdgpu kernel modesetting.
I have Rizen CPU and AMD GPU hence why the suggestion online which are to edit the grub menu and disable the nvidia drivers via
nouveau.modeset=0 did not work. Does anyone know how to switch off the AMD drivers? Also, this seems to stem from the NetworkManager in the first place – is that correctly understood?
Any ideas on what to do (currently there is nothing I can to boot the PC except maybe wiping everything out.
Just made a rather fatal late night mistake. I booted into gparted live and shrunk my
/ partition, then enlarged my
/home partition to give myself some more space. After applying these changes and restarting, my computer was caught in a boot loop, displaying the following:
System BootOrder not found. Initializing defaults. Creating boot entry "Boot0000" with label "ubuntu" for file "\EFI\ubuntu\shiux64.efi" Reset System
After this, the computer shuts down, starts up, shows this message, and repeat.
All the information I’ve found on fixing this involves booting from a live USB, or messing around in BIOS, but it looks like I even get to my BIOS to try anything. The system doesn’t respond to any keystrokes, and shuts down immediately after displaying the above message. Does anyone have any suggestions?
The laptop I murdered is the HP Spectre 13-v110ca – i5 7200U
I’m stuck on SharePoint 2016 for the time being, and I know that means I’m stuck using SPFx v.1.1.0.
However, I’m not sure what that means in terms of what version of Node.js to use.
I have some notes from a conference that say to use Node LTS v.8, but my notes are not clear on whether that means it must be exactly v.8, or at a minimum v.8.
I’m asking because I have a non-SharePoint project that is requiring Node LTS v.10, and I’m trying to figure out if I can just upgrade to Node v.10, or if I’ll have to install NVM so I can switch between 8 and 10 depending on what I’m working on.
Will SPFx v.1.1.0 work with Node LTS v.10?
I recently installed Ubuntu 19.04 Disco Dingo on my old Dell studio 1569 laptop. The initial installation from the thumb drive went fine, so I proceeded to download and install the updates as prompted. The download and updating seemed to go fine, but when finished, the system asked me to restart the machine to finish the updates, and that is when the problems started. The machine comes on, goes to the Ubuntu logo screen with the flashing dots, and hangs there (I waited for about 15 minutes before I grew impatient and turned off the machine. What I don’t understand is how I was able to run a live sessions AND initial installation, seemingly with no problems, but the update results in an un-bootable Disco Dingo? I have the drive partitioned in two with one partition holding Ubuntu 18.03 and the other holding 19.04. Suggestions? Thank you, –Louis
I have a Lenovo ThinkCentre running Lubuntu and a Dell touchscreen monitor which has a USB for auxilliary USB ports on the monitor and the touchscreen itself. I have connected a mouse and a keyboard to the auxilliary ports.
When trying to boot up the PC with the USB cable plugged in, it will stay frozen on the Lenovo boot logo. The only way to boot it is to unplug the cable, wait for it to go past the boot phase and then plug it back.
The BIOS has the Lubuntu installation as its top priority.
I’m a new user to Ubuntu and this is my last resort to try and fix my computer. I hope someone can help me.
I have a Dell Inspiron 15 5000 , Intel core i3-1080p. Its brand new and it came with Windows but I have since installed Ubuntu and have been using it fine for I guess over a month. Everything worked fine, the installation went perfect.
I wanted to change the purple default login screen to a picture or a different color, so I looked up if you could do it. You could, but it had to be done through the terminal thing. This is the tutorial I followed to change it: https://vitux.com/how-to-change-login-lock-screen-background-in-ubuntu/
I followed the instructions precisely and everything looked exactly as they said it would, but I had to restart it for everything to take effect. This made sense, but when I restarted it, it blinked the desktop once and now I’m stuck with a black screen that says “/dev/nvme0n1p2: clean” etc at the top, along with a bunch of other things like “started user manager for UID 121” and “started session c1 of user gdm”. (I tried to add a photo of it to this post but it was too big apparently.)
The screen it’s stuck on normally shows up when I start the computer, and then it will go to the desktop and work fine, but now it just stays there. I can’t do anything with it. I’ve tried things like going through the GRUB menu, checking the boot menu, and nothing works. I’ve done so many different things I’ve lost count. I’ve called people, no one supports Ubuntu/Linux. I’m completely stuck. PLEASE HELP! I’m new to this and I leave for college tomorrow and this is my computer that i was going to use. I desperately need a solution.