Custom Query (16363 matches)
Results (2302 - 2304 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #15865 | fixed | Failed to load unit 'lsilogicscsi' (VERR_SSM_LOADED_TOO_MUCH) 5.2.4 & 5.0.26 | ||
| Description |
Updated to the above releases couldn't restore my VMs. I reverted back to 5.0.6 and was able to work again. /\/\ |
|||
| #14914 | worksforme | Insertion of 'l' char into editor when using Win+L | ||
| Description |
When locking my computer with the Windows+L key, the char l is inserted into the text of any editor I'm using (I've experienced this with NetBeans, Notepad++ and PHPStorm). It's annoying to have this char inserted and break code. Can I have the char prevented from being inserted? I typically hit Windows first and then L, so it shouldn't be inserting the l key. If I'm in a bash console, this sends a command that displays all the known hosts (from /etc/hosts I presume) and then sl which I then have to erase on the command line as well. Preventing this as well would be great. This has something to do with my environment. I run Windows 7 host with all the above apps in a Fedora 21 VirtualBox. The problem only occurs in that environment (it does not occur in the Windows side). It occurs on a co-workers similar environment, which rules out hardware or something unique about my computer. SuperUser question |
|||
| #14335 | fixed | Symbolic link issue on Windows host | ||
| Description |
I installed a virtual box using a Vagrant script which we have been using successfully with VirtualBox 4.3. This is with Windows 7 64-bit host and Centos 7 64-bit guest. Part of the provisioning creates a symbolic link within an area which is a shared folder: cd /opt/sufia ln -s /tmp/fcrepo4-data jetty/ The target /tmp/fcrepo4-data is on the virtual machine's disc image, not the Windows host file system. After this command has been run, the symbolic link exists on the Linux guest, but "ln -s" reveals that it is targetted at \tmp\fcrepo4-data (i.e. the slashes have changed to backslashes) and the symbolic link fails to work under Linux. I reverted to VirtualBox 4.3 and everything is functioning properly after recreating the symbolic link. Sorry: I do not have the VBox.log file as I uninstalled everything. |
|||

