I am trying to run to test but every time I run a command that is related to the vendor folder, it shows the following error
'vendor' is not recognized or extend command operable program or batch file in Magento
I do not know what I must do in the next step
Has anyone can help me a hand, please!
After having problem with my motherboard sound card, which worked capriciously, I added
Asus Xonar DG but still can not get any sound out of my ubuntu 18.04 machine.
alsamixer does not show the card as it should.
#lsmod | grep snd snd_hda_codec_hdmi 49152 2 snd_hda_codec_ca0132 90112 1 snd_seq_midi 16384 0 snd_seq_midi_event 16384 1 snd_seq_midi snd_rawmidi 32768 1 snd_seq_midi snd_hda_intel 40960 15 snd_seq 65536 2 snd_seq_midi,snd_seq_midi_event snd_hda_codec 126976 3 snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec_ca0132 snd_hda_core 81920 4 snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec,snd_hda_codec_ca0132 snd_hwdep 20480 1 snd_hda_codec snd_pcm 98304 7 snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec,snd_hda_core,snd_hda_codec_ca0132 snd_seq_device 16384 3 snd_seq,snd_seq_midi,snd_rawmidi snd_timer 32768 2 snd_seq,snd_pcm snd 81920 38 snd_seq,snd_seq_device,snd_hda_codec_hdmi,snd_hwdep,snd_hda_intel,snd_hda_codec,snd_timer,snd_pcm,snd_hda_codec_ca0132,snd_rawmidi soundcore 16384 1 snd
And I can not find any driver to install.
I have also tweaked
Sound > Settings but to no avail.
So left clueless. Any help is much appreciated.
Samsung Galaxy S5, Android 6.0.1 — All individual or unique ringtones not working. Plays the main set ringtone for all calls. Also, when Do Not Disturb is on, does not recognize exceptions for Favorites. I’ve tried resetting all of the above and it does not fix the problem. I recently installed an app called Talking Clock, which I never got working. After I noticed the problems, I uninstalled the app. That didn’t help. Verizon store said I may have to do a complete factory data reset to solve the problem.
I am currently using a ROOTED “Huawei MediaPad 7 Lite” tablet and am having issues entering the bootloader. When powered on and connected to a PC, the device is seen in adb using the command
adb devices (driver is working). However, when I try to enter the bootloader,
adb reboot bootloader, the device malfunctions in windows:
The same occurs when the tablet is powered off, and the power and volume up keys are held down (entering bootloader manually). In ‘Device Manager’, there are NO ‘Unknown Devices’ missing drivers. Instead, there is an issue with the USB controller:
Due to this malfunction, I cannot install a driver for the tablet when in bootloader mode. To clarify, the tablet works OK when powered on and connected to a PC, but malfunctions when in bootloader mode. I have tried this on 3 different computers with 4 different MicroUSB cables with no success.
I also have a second identical MediaPad 7 Lite, and in trying the above steps also has the same problems. It seems Huawei have done this as a preventative measure (meaning it is a device specific issue), but does anyone know how to make the PC recognise this device properly when in bootloader?
EDIT: The bootloader screen is unusual. Without the cable connected, when the bootloader is entered (by pressing power with volume up & down), the following options exist:
- continuing to hold volume up brings up a screen which is used to update the tablet software from a file on the external MicroSD card
- continuing to hold volume down initiates an automatic recovery process
- releasing all buttons reboots the tablet automatically after a few seconds
With all of the above options, I tried plugging the tablet into my PC. However, Windows does not recognize the tablet at all (nothing pops up).
When a disk (out of 8 disk Raid 10 array) was physically removed, Ubuntu 16.04 recognized the the remaining disk as Raid 0.
Why is that? Restarting the machine doesn’t help. It still recognizes it as Raid 0.
Where is the configuration to tell mdadm that the array is a raid 10 instead of 0?
To make it quick, I have a Corsair M65 Pro mouse with CKB-daemon installed. When running some Steam games that use Unity they will crash whenever the mouse is plugged in because it thinks the mouse is a joystick, as far as I can tell. I’ve found this as an issue on a Github discussion which I’ll link below, I tried some of the things they mentioned but don’t know much about udev and had trouble following along.
So basically, I think what I have to do is blacklist the mouse so that it isn’t recognized as a joystick, but I can’t figure out how to do that. I’m running Ubuntu 18.04.2.
Here’s the link to the Github discussion that went over the issue, I read through it all but either didn’t know what to do or it didn’t work. https://github.com/ValveSoftware/steam-for-linux/issues/6253
I have Lenovo Edge e420s with a fingerprint:
Bus 001 Device 003: ID 147e:1002 Upek Biometric Touchchip/Touchstrip Fingerprint Sensor
Unfortunately, Ubuntu (or Gnome Users settings) does not recongized the device using fprint_demo or the Users settings.
Funny is that Fingerprint GUI, recognizes and works.
My real problem is that I want to login with my fingerprint. Fingerprint GUI does not support it and Gnome-Users/fprint_demo doesn’t recognize the device.
Any idea how it can be fixed?
Looked everywhere around the net, followed any guide I was able to find, and now my last hope is here. As the title say I’m unable to successfully connect my device to any PC. What I already did ?
Tested connection on Windows 10, Windows 7 and Kali. Windows not show any device connected, same for kali, using lsusb command.
On the device, in Developers menu I’ve turned ON/OFF settings related to usb, changed the usb mode from Charge Only to any other option, but as soon as I exit the menu the settings change back to Charge Only, Debug USB OFF.
I’ve also changed USB Port Settings in the ProjectMenu to Manufacture Mode/Google Mode.
Removed, installed and updated to latest version HiSuite.
I’ve tested with 6 different cables.
What I can think is the EMUI 9 update I did few days ago broke something or the connector is half dead and can only charge(weird). Any idea about any possible solution?
I had a cheap bar (USB, NOT HDMI) working earlier today, but now it does not. It does not seem to even be being recognized, e.g. as an output device in Settings/sound/Output.
I have spent a couple of hours hunting, and found articles for older versions of Ubuntu.
If a clear set of diagnostic / fix instructions for U18.04 (on a lenovo x230) exists, I’d love a link.
Ubuntu isn’t recognizing any use of the super key(s). Keyboard works 100% otherwise, just not registering at all when I press it. Happens with two different keyboards…
It’s been working perfectly fine for a few months, I haven’t consciously messed with the bindings or keyboard config. Just has completely stopped being recognized as of today. Tried restarting computer, resetting settings… nothing.
Even when I open keyboard layout under Settings > Region & Language > keyboard icon, where the layout can be seen and the keys light up on the screen when you press them, both super keys don’t register.